\nThis patch is being released to correct problems with YS*5.01*30.\n\n
\nAdd Personal Health Inventory (PHI) as a new mental health instrument.\n\n
\nBackup of YS*5.01*173 on Apr 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis build inactivates the "I9" instruments, as they have been superseded \nby the C-SSRS screener. The C-SSRS has been set so that it must be \ncompleted in one session. New versions of the PROMIS29 are added.\n\n
\nBackup of YS*5.01*175 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee FORUM Patch Description.\n\n
\nBackup of YS*5.01*171 on Apr 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issues:\n \n1. If a user elects to produce an XML Export by location, validation is\n not referencing the correct location file.\n2. The user is not allowed to gracefully exit various prompts by entering \n "^" or return.\n\n
\nBackup of YS*5.01*158 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nMental Health web application support\n\n
\nBackup of YS*5.01*174 on Jun 10, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis enhancement patch will introduce the Global Assessment of Functioning \n(GAF) to the Mental Health software. This patch introduces two alternate \nways of entering a GAF score (Axis 5) and two new reports. The existing\nDiagnostic software has been modified to now accept the GAF score from 100-1.\n\n
\nAdd Case Mix Index as an instrument.\n\n
\nSee the patch description for more detailed information. This build \nupdates the DLL version for the YS BROKER1 option.\n\n
\nBackup of YS*5.01*177 on Jul 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nNew Instruments: SRCS, NPO-Q, B-IPF\n\n
\nMHA WEB STAFF ENTRY UDPATE\n\n
\nAdds Computer Adaptive Testing (CAT) capability to MHA-Web.\n\n
\nMHA WEB STAFF ENTRY UDPATE\nFeatures added include:\n- Improved Consult UI on the front end\n- VistA RPCs to Save and Get User Instrument Battery definitions\n- VistA RPCs to Save MH Administration Comments\n- Update to C-SSRS to not allow partial completion\n- 508 Defect fixes\n- Backwards compatibility patch for YS*5.01*182\n\n
\nMHA WEB PATIENT ENTRY UDPATE\n\n
\nThis patch resolves the following issue: \n \n1) INC19506614 - Cannot create Lab test using YSCL TEST LINK--Clozapine \n Test Link. Every time you try to add the Neutrophil Count it gives a Z\n error.\n\n
\nUpdate for MHA Web\nWHODAS2.0-12\nBarthel Index changed to Staff Entry Only\nInstrument Authors updated for:\nBASIS-24 PSYCHOSIS\nBBHI-2\nC-SSRS\nI9+C-SSRS\nPSS-3\nPSS-3 2ND\n\n
\nThe Mental Health protocol YS PATIENT MOVEMENT, which is part of the DGPM \nMOVEMENT EVENTS protocol, has been modified to run silent when invoked by \nOrder Entry/Results Reporting.\n\n
\nEmergency patch to YS*5.01*199\nany progress notes aggregated in that data entry session was lost.\nUpdate NUDESC instrument in MH TEST/SURVEY SPEC file\n - Instrument Name changes from NuDESC to NUDESC\n \nFix bug where if the last instrument in an Assignment is a Restricted \nInstrument, then any progress notes aggregated in that data entry session \nwas lost.\n \nFix bug where if the last instrument in an Assignment is Deleted, then \n\n
\nPlease see the patch description for the full information regarding this \npatch/build.\n\n
\nMHA Web update\n Version.\n-Update BASIS-24 instrument for blank fields.\n-Update FAST instrument scoring.\n-Update FOCI skip logic.\n-Update MCMI4 to allow skipped questions and not allow >13 skipped.\n-Update SLUMS and GDS DEMENTIA to add story text to JSON in the\n MH TEST/SURVEY SPEC file.\n-Add Instrument Interpretive Text data to MH TESTS AND SURVEYS file.\n-Add RPC to get Interpretive Text for instruments.\n-Update Instrument Exchange to transport INTERPRETIVE TEXT for \n-Add Print Title to individual instruments for printing.\n instruments, ROUTINE FOR SUICIDE RISK and TAG FOR SUICIDE RISK.\n-Update PHI question text.\n-Update Location input box to search for both clinics and wards.\n-Update Location input to allow locations starting with numbers and if \n entered text is exact match to a location.\n-Update Ordered By, Interviewer, and Location input box to allow / and ~\n-Add CAT-PSYCHOSIS, EHS-14, PEBS-20, PEBS-27, WBS, ASRS, and DAR-5 \n instruments.\n-Update Print Title for PCL-5, PCL-5 Weekly, CAD-PTSD-DX, and CSI Partner\n\n
\nNEW AND UPDATES TO INSTRUMENTS\nAdd Elapsed Time to CAT/CAD.\nSave active user with and administration.\nUpdate MCMI4 to fix negative and >115 Adjusted Base Rate scores.\nAdd EDE-Q and CIA instruments.\nUpdate CESD graph scale.\nUpdate instrument categories for instruments.\nChange Pain instrument category to Pain/Health.\nChange Instrument name from ASRS to ASRS-6.\nUse incremental locks to save responses and results.\nRaise limit of administrations and result records allowed.\nAdd answer and result records to Administration Detail option.\n\n
\nMHA Web integration with MHC.\n SIP-AD-START - Addiction-SUD\n SWEMWBS - Cognitive\nUpdate instrument name of ASRS to ASRS-6\nAdd new instruments for MHA:\n EDE-Q\n CIA\nUpdate locking of answer and result files.\nAdd answer and result display to YTQR ADMINISTRATION DETAIL.\nInstrument Categories added for:\n NUDESC - Cognitive\n SIP-AD-30 - Addiction-SUD\n\n
\nNew instruments: PROMIS10, SBAF, SBAF-PTSD, MIOS+B-IPF, MIDAS, HIT6\nUpdated instruments: PCL-5, PCL-5 Weekly, Morse Falls Scale\nReports changed to use self-identified gender\nSet instruments to staff-entry only: CASE MIX, PSS-3 2ND, AD8\nSet instrument to patient-entry and staff-entry: COPD\nFix bug with Instrument Exchange when using HTTPS\n\n
\nPatch to update non-legacy instrument score retrieval for graphing \nresults.\n\n
\nMHA Web Updates\nNew Instruments: GASS\nUpdated Instruments: FAST\nAdd RPC for Patient Entry Cosigner validation\nUpdate Dashboard High Risk with error trap\nUpdate MHA Web user name lookup to handle exact matches\n\n
\nFix locking issue that was allowing responses from one administration to\noccasionally overwrite responses from another administration.\n\n
\nMHA Web Updates\n-MHC integration\n-Overdue Assignment functionality\n-Scheduled Assignment Edit functionality\n \nInstrument updates\n-MHLA, MHLB, MHLC-C non-restricted\n-MCMI4 Fix scale graphing results 99+\n\n
\nThis patch has all changes for Mental Health V. 5.01 to be Year 2000 compliant.\n\n
\nThe patch releases new instruments used with long COVID.\n\n
\nEmergency patch for WBS_V2.\n\n
\nBack-end updates to support using web-based staff-entry of MHA inside \nthe CPRS Mental Health DLL.\n \nThe older Windows-based DLL is called YS_MHA_A_XE10.dll\nThe newer Web-based version is called YS_MHA_A_WEB.dll\n\n
\nNew Instruments and Instrument Updates.\nPEG\nLVVFQ\nMINICOG\nPSEQ-2\nNPI-Q\nEAT-26\nAUDC\nD.ERS - Fix IMPULSE scale, remove Complex Instrument from report.\nMCMI4 - Fix spelling Childhood Abuse.\nBSI18 - Fix to use biological sex for scoring.\nMDQ\nBAM-C-CBT-SUD\nBAM-R-CSG-SUD\nBAM-IOP-CSG-SUD\nCMAI\n\n
\nInstrument patch\nFix error in legacy instrument scoring with self-identified gender \n \n \nR PRIV report update.\nAdditional check for instruments that have an administration ID is\nadded before allowing an assignment to be edited.\nAddition of Time/Timezone information to patient identifier RPC.\nModify user timeout to check user level first.\nBBGS, SODU, SDSQ, G-SAS\nUpdate COVID category to Long COVID\nUpdate Print Title to add acronym for BAM-C-CBT-SUD, BAM-IOP-CSG-SUD,\nBAM-R-CSG-SUD\nDeactivate MIOS+B-IPF and add MIOS+B-IPF V2\nUpdate Case Mix scoring.\nFix spelling error in PAI instrument\nFix spelling error in GDS instrument\n\n
\nSee patch description.\n\n
\nAdd RPC calls for cloud database.\nUpdate BAM-R-CSG-SUD, BAM-IOP-CSG-SUD, BAM-C-CBT-SUD for date picker \nfield.\nNew instruments.\nCDSS\nPCL-5 DAILY\nWURS-25\nASRS\nLEC\nUpdate instrument ASRS-6\nUpdate WHYMPI instrument\n\n
\nUpdates to MHA Web including enhanced backend database functionality.\nFix IJSS instrument scoring routine for compatibility.\nFix MH TEST/SURVEY SPEC for EDE-Q to fix blank instrument print.\nFix scale group name for MBMD.\nAdd SIP-AD-START_V2 and SIP-AD-30_V2\nDeactivate SIP-AD-START and SIP-AD-30\nDeactivate SCL90R\n\n
\nUpdate instrument PEBS-20.\nAdd new instrument YMRS\nAdd new instruments MOCA_8.1, MOCA_8.2, MOCA_8.3, MOCA BLIND\nDrop instruments CEMI, GPCOG, ISMI, COPD, STAI, STMS, ATQ, IJSS, BBHI-2, \nMOCA, MOCA ALT 1, MOCA ALT 2, and CESD.\nAdd unlocking to MH ADMINISTRATIONS file in YTQAPI1.\nAdd new RPC for Reviewed Administration status. This will remain dormant \nuntil patch YS*5.01*250 is released.\nUpdate instrument MH REPORT for BRADEN SCALE.\nUpdate MINICOG scoring.\nUpdate BOMC scoring.\nUpdate MIDAS instrument to add Long COVID category.\nUpdate instrument Q-LES-Q-SF scoring routine to fix display.\nAdd field 19, REVIEWED, to MH ADMINISTRATIONS.\nAdd call to update instrument High Risk/Positive response in GET \nassignment list.\n\n
\nThis patch will introduce the following changes to the Addiction Survey Index\nsoftware. Three new options have been included: ASI Case Finder [YSAS CASE \nFINDER], ASI Followup Finder [YSAS FOLLOWUP FINDER] and Site Report by Date\n[YSAS MANAGEMENT REPORT]. The ASI software will now produce a narrative report \nfor the followup ASI. The addition of a signature block has been added to the\nnarrative reports. Also included in this patch are numerous NOIS fixes. See\npatch description for a complete list.\n\n
\nPlease see the patch description for complete details.\n\n
\nSee patch description.\n\n
\nThis patch adds protocol event points to MHA to allow subscribers to \nreceive events when MHA administrations change.\n\n
\nUpdates to MHA Functionality.\nFix YMRS response item number.\n \nAdd AAQ-II-7\nAdd ALSFRS-R\nAdd ALSSQOL-SF\nReactivate BBHI-2\n \nAdd Parameter YS MHA LOG APPLICATION ERRORS to control error trapping for\nadministrations. It is implemented turned off by default, deactivating \nerror trapping for administration double click errors. Double clicking is \nUpdate for User Preference Parameters to validate Last Assignment.\ndeactivated in the web application itself.\nUpdate MH REPORT to have new message if restricted instrument.\nUpdate Instrument Exchange to handle Orlando progress note titles of\nMH DIAGNOSTIC STUDY NOTE and MH CONSULT NOTE\nUpdate BOMC report.\nUpdate PSS-3-2ND report.\nFix EAT-26 scoring for zero height.\nFix CCSA-DSM5 skipped question error in scoring.\n\n
\nDeactivate HIT-6.\n\n
\nEmergency patch to fix MH REPORT for SRCS.\nUpdate User Preference RPC to find matches by NAME and by ID.\n\n
\nReactivate COPD instrument\nUpdate spelling in COWS instrument\nNew MAHC-10 instrument\nNew NSI for TBI instrument\nCerner integration mock/cert update\n\n
\nFix PSS-3 Report\n scale.\nFix IADL Interpretive text\nFix CCSA-DSM5\n - Add space in report after 11/suicidal ideation\nFix GAD-7\n - Interpretive text line breaks to match cloud format.\nFix ZBI SHORT and ZBI SCREEN\n - Change Interpretive text from "followup" to "follow up."\nFix SF36\n - Add missing scale Reported Health Transition to MH SCALES.\n - Fix line breaks in disclaimer\nFix CES\n - Add missing note titles\n \nFix User preference Parameter to find exact IEN if two names are the same.\nAdded keep-alive RPC in Patient Entry.\n \nUpdate the data dictionary for MH ADMINISTRATIONS to add the boolean \nfield, PROGRESS NOTE GENERATED. 1=Yes, 0/null=No.\nUpdate the RPC GET /api/mha/instrument/list/:dfn to return this property.\nFix legacy instrument scoring to save MH RESULTS.\nFix PSS-3-2ND Report\nUpdate the RPC POST /api/mha/cdb/instrument/admin to handle tscores.\nUpdate the RPC for user assignment preferences to quit with no action if \nerror in incoming data detected.\nUpdate user timeout RPC to return correct user level timeout.\nUpdate the scoring routine to handle non-unique scale sequence \nidentifiers.\n \nCreate MENTAL HEALTH ASSISTANT Remote Application entry.\n - Answer_7778 was capitalized, causing it to not translate in the report.\n - Fix line breaks in disclaimer\nFix EPDS Report\n - Interpretive text "mothers who score 10" instead of 13.\nFix PROMIS10\n - The last question was not being translated correctly into the pain \n\n
\nSee National Patch Module YS*5.01*40 for details of this patch.\n\n\n
\nSee National Patch Module YS*5.01*41 for details of this patch.\n\n\n\n
\nSee National Patch Module patch YS*5.01*44 for details.\n\n
\nThe new Case Finder routine ^YSASCF introduced by patch YS*5.01*38 obtains\nOP diagnosis information from the Outpatient Diagnosis file (#409.43).\nScheduling patch SD*5.3*132, released shortly after the Mental Health patch,\nbegins storing this data in the V POV file (#9000010.07). Therefore, after\nsites install SD*5.3*132, the case finder (^YSASCF) will no longer find\noutpatients because file #409.43 is no longer being updated. Routine\nYSASCF as released with patch YS*5.01*38 will be modified in this patch to\npull the information from the new file.\n\n
\n Some sites are getting errors while trying to install Mental Health patches\n \n This is caused by old entries in the PACKAGE (#9.4) file confusing the install.\n During installation of a Mental Health patch, the install looks at the\n PREFIX field (#1) of the PACAKAGE file (#9.4). If it contains "YS", it\n then refers to the history for that package to verify that the required\n patches have been installed. Any entries that contain the "YS" prefix but\n do not contain "Version 5.01 of Mental Health" in the SHORT DESCRIPTION\n field (#2), cause the install to look at the wrong history. The install\n aborts because it does not find the required patches.\n \n when required mental health builds exist in the REQUIRED BUILDS field (#11) of\n This patch corrects the problem by executing routine YSPOS46 to "clean up"\n the PACKAGE file. This routine is included as a post installation routine\n for this patch. During the installation, the user is asked if they would\n like to 'Delete old package file entries?' If the user says 'Yes', all but\n the current version 5.01 Mental Health entry is deleted. If the user\n answers 'No', the old "YS" prefix entries in the "C" cross reference of the\n PACKAGE file (^DIC(9.4,"C","YS",0)) are renamed to YS1, YS2, YS3, etc. Only\n the current version 5.01 entry is left unchanged.\n \n PLEASE NOTE THAT NOTHING IS INSTALLED WITH THIS PATCH. IT CONSISTS ONLY OF\n the Kids BUILD file (#9.6). The install will abort stating that a required\n THE USER QUESTION DURING INSTALLATION AND EXECUTION OF POST INSTALLATION\n ROUTINE YSPOS46.\n \n patch is missing. However, when the site checks on the missing patch, they\n discover that the patch IS installed. This became evident when test sites\n were attempting to install YS*5.01*44 which required patch YS*5.01*38 to be\n installed. The install would abort saying that patch 38 is not installed\n even though it was. (This same error occurred when test sites were\n attempting to install YS*5.01*45.)\n\n
\n VHA Directive, 97-059, dated November 25, 1997, "Instituting Global\n of GAF score data in the DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8).\n The API's are described as follows:\n \n API entry point RET^YSGAF(YSX) retrieves GAF score information from the\n DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8). It returns the latest GAF\n score and diagnosis date/time for the patient based on the internal entry\n number (variable YSX) passed into the API. The score/date is returned in the\n form of a concatenated string. If no GAF data is found, -1 is returned.\n \n API entry point UPD^YSGAF(YSPN,YSGN,YSGD,YSGC,YSPT) is designed to store\n Assessment of Function (GAF) Scores in Axis V Mental Health Patients", has\n patient GAF score information in the DIAGNOSTIC RESULTS - MENTAL HEALTH\n file (#627.8). The following information is passed into this call:\n \n YSPN Patient name - Pointer to the PATIENT file (#2)\n YSGN GAF score (Axis 5)\n YSGD Date/Time of diagnosis\n YSGC Diagnosis by - Pointer to the NEW PERSON file (#200)\n YSPT Patient type - 'I'npatient or 'O'utpatient\n \n This API updates new field PATIENT TYPE (#66) in the DIAGNOSTIC RESULTS -\n been released. This directive provides guidelines for collection of GAF\n MENTAL HEALTH file (#627.8) which was created to store the patient type of\n the GAF record. It is a set of codes consisting of 'I' for inpatient and 'O'\n for outpatient.\n \n This API routine call creates a new record with the above information in the\n DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8) in order to maintain a\n historical record of GAF scores for an individual patient.\n \n Associated NOIS: None\n \n Scores for outpatients and inpatients. Inpatient Axis V (GAF) scores have\n Test Site(s): Canandaigua, NY\n Tuscaloosa, AL\n \n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n been collected for several years, but up to now there has been no provision\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YS42ENV N/A 2916949 42\n YSGAF 12321822 13001186 33,37,40,42\n \n \n \n Installation Instructions:\n ==========================\n for collection of GAF Scores for outpatients. Storage will be in the VISTA\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto your\n system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Mental Health software package.\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Users may remain on the system, but installation should be done at\n off peak hours.\n \n 4. Installation will take less than five minutes.\n \n \n 5. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*42' and proceed\n with install.\n \n 6. Delete routine YS42ENV.\n \n This patch contains two new API's that are used for the storage/retrieval\n\n
\nVHA Directive, 97-059, dated November 25, 1997, "Instituting Global \nThe GAF initiative is using the VISTA HL7 software to transport the GAF \n YSDX3B 11950549 11117228 33,43\n YSGAF 13001186 13161211 33,37,40,42,43\n YSGAFHL7 N/A 5831582 43\n YSGAFOBX N/A 3398570 43\n YSGAFTR N/A 2685760 43\n \n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your\nscore data onto the Austin Automation Center (AAC) system. An A08 HL7 \n system.\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\nmessage will be used to transmit GAF Scores to the National Patient\n \n 3. Installation of this patch should be at off peak hours.\n 4. Users may remain on the system.\n 5. Installation will take less than five minutes. Installation of\n this patch requires no additional memory space.\n 6. From the 'Installation Menu' of the KIDS menu, run the option \n 'Install Package(s)' Select the package 'YS*5.01*43' and proceed\n with install.\n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond NO.\nCare Database (NPCD). This message contains the MSH, EVN, PID and OBX\n 8. Follow the HL LOGICAL LINK [YS GAF-SND] set up example below.\n 9. WARNING!!! This part should be done at off peak hours. \n Execute the call point EN^YSGAFTR. An example of the running \n the call point is below.\n 10. Delete YS43POST. \n \n \nExample of the HL Logical Link [YS GAF-SND] set up \n--------------------------------------------------\nVAH,DEV>D ^XUP\nsegments.\n \nSetting up programmer environment\nTerminal Type set to: C-VT320\n \nSelect OPTION NAME: EVE\n ---\n 1 EVE Systems Manager Menu\n 2 EVENT CAPTURE DATA ENTRY ECENTER Event Capture Data Entry\n 3 EVENT CAPTURE EXTRACT ECXEC Event Capture Extract\n 4 EVENT CAPTURE MANAGEMENT MENU ECMGR Event Capture \n \n Management Menu\n 5 EVENT CAPTURE MENU ECMENU Event Capture Menu\nCHOOSE 1-5: EVE Systems Manager Menu\n ---\n \n Core Applications ...\n Device Management ...\n FM VA FileMan ...\n Manage Mailman ...\n Menu Management ...\nThis patch will allow the sites to transmit GAF scores to the National \n Programmer Options ...\n Operations Management ...\n Spool Management ...\n System Security ...\n Taskman Management ...\n User Management ...\n Application Utilities ...\n Capacity Management ...\n HL7 Main Menu ...\n \nPatient Care Database (NPCD) at the AAC. Sites will be able to transmit GAF\nSelect Systems Manager Menu Option: HL7 Main Menu\n -------------\n \n 1 V1.5 OPTIONS ...\n 2 V1.6 OPTIONS ...\n 3 Activate/Inactivate Application\n 4 Print/Display Menu ...\n 5 Purge Message Text File Entries\n \nSelect HL7 Main Menu Option: 2 V1.6 OPTIONS\nscores in a batch mode using the call point EN^YSGAFTR. EN^YSGAFTR will\n - \n \n 1 Communications Server ...\n 2 Interface Workbench\n 3 Message Requeuer\n \nSelect V1.6 OPTIONS Option: 1 Communications Server\n -\n \n 1 Edit Communication Server parameters\nprompt the user for a date range, this date range will be the selection\n 2 Manage incoming & outgoing filers ...\n 3 Monitor incoming & outgoing filers\n 4 Start LLP\n 5 Stop LLP\n 6 Systems Link Monitor\n 7 Logical Link Queue Management ...\n 8 Report\n \nSelect Communications Server Option: 4 Start LLP\n -\nAssessment of Function (GAF) Scores in Axis V Mental Health Patients", has \ncriteria that is used when determining the GAF scores to be transmitted to \nThis option is used to launch the lower level protocol for the\nappropriate device. Please select the node with which you want\nto communicate\n \nSelect HL LOGICAL LINK NODE: YS GAF-SND \n ----------\n \n Select one of the following:\n \n F FOREGROUND\nthe NPCD at the AAC. The batch processing will allow sites to initially \n B BACKGROUND\n Q QUIT\n \nMethod for running the receiver: B// ACKGROUND\n ---------\nJob was queued as 229301.\n \n \nSelect Communications Server Option: <CR> \n --\npopulate GAF Scores at the NPCD.\n \nExample of GAF Batch Transmission\n---------------------------------\n >D EN^YSGAFTR\n \n [At the prompt, enter the start date, this] \n [date will be the beginning date range ] \n [used in the selection criteria. ]\n \n >Enter start date : (10/1/97 - 12/31/99): 10/1/97 (OCT 01, 1997)\n \n -------\n \n [At the prompt, enter the stop date, this ]\n [date will be the ending date range ] \n [used in the selection criteria. ]\n \n >Enter stop date : (10/1/97 - 12/31/99): 12/31/99 (DEC 31, 1999)\nAfter the running of the batch transmission of GAF scores, all GAF scores \nentered will be dynamically sent to the NPCD at the AAC.\n\nThe new Q-NPT.DOMAIN.EXT domain, which receives the HL7 messages,\nimplementation instructions are released by MailMan XM*DBA*119 informational\npatch. \nbeen released. This directive provides guidelines for collection of GAF \n \nThe (G)lobal (A)ssessment of (F)unction Transmission patch components are:\n - 4 New routines, YS43POST, YSGAFHL7, YSGAFOBX, YSGAFTR\n - 2 Patched routines, YSDX3B, YSGAF\n - 2 New mail groups, YS GAF TO NPCD, YS GAF TRANSMISSION ACK\n - 2 New Protocols, YS GAF, YS GAF A08 CLIENT\n - 1 New HL7 Application Parameter, YS GAF\n - 1 New HL Lower Level Protocol Parameter, YS GAF SEND\n - 1 New HL Logical Link, YS GAF-SND\n \nScores for outpatients and inpatients. Inpatient Axis V (GAF) scores have \nGAF Mail Groups\n---------------\nYS GAF TO NPCD: This mail group is used for transmission of HL7 messages \nderived from the parameters defined in the DIAGNOSTIC RESULTS - MENTAL \nHEALTH file (#627.8) to the AAC.\n \nYS GAF TRANSMISSION ACK: This mail group is used to receive Confirmation \nand Processing Report Messages from Austin. \n \nProtocols\nbeen collected for several years, but up to now there has been no provision \n---------\nYS GAF: This event driver protocol defines the associated parameters needed \nto build the HL7 message used to send the GAF data to Austin.\n \nYS GAF A08 CLIENT: This subscriber protocol defines the parameter needed by \nHL7 package to determine where to send the HL7 formatted message \ncontaining the GAF information.\n \nChanges to routine YSGAF (YS*5.01*42)\n-------------------------------------\nfor collection of GAF Scores for outpatients. Storage and collection of GAF\nThe API RET^YSGAF was changed to use the DIAGNOSTIC RESULTS - MENTAL\nHEALTH file (#627.8) "C" cross-reference to look up the latest patient GAF\nscore. This corrected performance issues that were reported after the\nloading of SD*5.3*149 and YS*5.01*42.\n (WPB-1298-31096 BAY-1298-30934 CHS-1298-40830 \n EKH-1298-40379 NTH-1198-72024)\n\nThe API UPD^YSGAF was changed to kill all necessary variables set within the\nAPI upon exiting. (BHH-1298-41082)\n \nscores will be in the VISTA Mental Health software package file\n \n Associated NOIS: WPB-1298-31096\n BAY-1298-30934\n CHS-1298-40830 \n EKH-1298-40379 \n NTH-1198-72024 \n BHH-1298-41082\n \n \n Test Site(s): Canandaigua, NY\nDIAGNOSTIC RESULTS - MENTAL HEALTH (#627.8). \n Chicago HCS, IL\n Dallas, TX\n Miami, FL\n Salt Lake City, UT\n Tuscaloosa, AL\n \n \n \n ROUTINE SUMMARY:\n ================\n \n \n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YS43POST N/A 237811 43\n\n
\nThis patch updates the Clozapine reporting software as required by the\n 2. Update Site Number reporting to comply with integrated site\n requirements. \n References to the DEFAULT INSTITUTION (#217) field in the KERNEL\n SITE PARAMETERS (#4.3) are no longer supported. These references\n were changed to the supported call $$SITE^VASITE referenced in\n DBIA#10112.\n 3. Extend reporting time for White Blood Count to six months. Changes are\n also included to improve the reporting of the White Blood Count.\n The CLOZAPINE LAB TEST (#603.02) file has been created to facilitate\n this report. The White Blood Count (#.01) field in the CLOZAPINE\nCLOZAPINE PATIENT MANAGEMENT PROTOCOL (CPMP).\n LAB TEST (#603.02) file indicates the proper White Blood Count test\n to be used.\n These changes include:\n 1. Reporting Absolute Neutrophil Count (Calculated from percentage\n reported at the site). \n The CLOZAPINE LAB TEST (#603.02) file has been created to facilitate\n this report. The Neutrophil Count (#1) field in the CLOZAPINE LAB\n TEST (#603.02) file indicates the proper Neutrophil Count test to be\n used.\n\n
\nThis patch will now allow a progress note to be built using TIU V. 1.0. This\npatch can only be installed if TIU V. 1.0 has been installed at your site.\n\n
\nThis patch enhances the management report, Global Assessment of Functioning\n \nThe following is an example of the generated report:\n \n GAF Case Finder\nBegining Date: DEC 1,1998\n Ending Date: MAR 18,1999\n Facility: Dallas CIOFO\n \nThe following is a list of all patients who had a Mental Health Outpatient\nEncounter between the above dates but do not have a GAF score WITHIN 90\n(GAF). The new option GAF Case Finder [YSGAF CASE FINDER] has been added as\nDAYS. Last MH (non-telephonic) Outpatient Encounter in date range is listed.\n \nName SSN Date Location Provider\n \n0 MH patients without a GAF.\n0 MH patients had a GAF.\n \n NOIS calls: none\n Test Site(s): Dallas, TX\n Salt Lake City, UT\nan item to the MENU Global Assessment of Functioning [YSGAF MAIN].\n \n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YSGAF3 N/A 12209534 48\n \n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto your\n system.\n \nThe GAF report now lists all patients that have not been given a GAF score\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. The transport global will remain on the system until\n installed or manually deleted.\n \n 3. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n Print Transport Global\n Compare Transport Global to Current System\nwithin the last 90 days. The user is given the option to sort the report\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. Installation of this patch should be at off peak hours.\n \n 5. Users may remain on the system.\n \n 6. Installation will take less than five minutes and requires no\n additional memory space.\n \nby patient name or by provider. The results of this report are sent to the\n 7. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*48' and\n proceed with install.\n \n 8. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES//', respond NO. However, it is advised that menus\n be rebuilt at a later time.\n \n 9. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond NO.\nMAILMAN system and are returned the user as a MAILMAN message. It is also\nrecommended to queue the report during non-peak or after-hours.\n\n
\n1. Patch YS*5.01*31 releases several new psychological tests/interviews to \n \n \n IRM FIELD OFFICE FTP ADDRESS DIRECTORY\n ================ =========== =========\n ALBANY 152.127.1.5 [ANONYMOUS.SOFTWARE]\n HINES 152.129.1.110 [ANONYMOUS.SOFTWARE]\n SALT LAKE 152.131.2.1 [ANONYMOUS.SOFTWARE]\n \n The software can be found in a file named MH_501_31.KID.\n \n Installation Instructions:\n b. Test Name: AUDIT\n ==========================\n This patch should be installed during 'OFF PEAK' hours when few or no users\n are on the system. Installation of the patch will take less than 5 minutes.\n \n 1. START UP KIDS\n From the KERNEL Installation and Distribution Systems (KIDS)\n Menu, select the Installation menu [XPD INSTALLATION MENU]: \n Installation\n Edits and Distribution ...\n Utilities ...\n Description: Alcohol Use Disorders Identification Test\n Installation ...\n \n 2. SELECT INSTALLATION OPTION\n Select Installation Option: Load a Distribution\n Enter a Host File: MH_501_31.KID\n \n This Distribution contains Transport Globals for the following\n Package(s):\n YS*5.01*31\n Use INSTALL NAME: YS*5.01*31 to install the Distribution.\n Number of Questions: 10\n \n NOTE: The following are OPTIONAL:\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes, such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n Number of Scales: 1\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n 3. SELECT INSTALLATION OPTION: Install Package(s)\n \n Select KIDS OPTION: INSTALL PACKAGE(S)\n Select INSTALL NAME: YS*5.01*31\n \n 4. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n \n Protocols? YES//, respond NO\n \n 5. Delete routines YS31POST and YS31ENV.\n c. Test Name: SMAST\n Description: Short Michigan Alcoholism Screening Test\n Number of Questions: 13\n Number of Scales: 1\n the Mental Health package. These tests are accessed via menu item \n \n d. Test Name: DOM80\n Description: Depression Outcome Module: Patient Screen 8.0 \n Number of Questions: 4\n \n e. Test Name: DOM81\n Description: Depression Outcome Module: Patient Baseline 8.1\n Number of Questions: 69\n \n f. Test Name: DOM82\n 'Psychological tests/interviews (administer) [YSADMTEST].' The new \n Description: Depression Outcome Module: Clinician Baseline 8.2\n Number of Questions: 23\n \n g. Test Name: DOMG\n Description: Depression Outcome Module: Geriatric Screen\n Number of Questions: 5\n Number of Scales: 1\n \n h. Test Name: SAI\n Description: Spiritual Assessment Inventory\n tests are as follows:\n Number of Questions: 14\n \nThese tests are stored as new entries in the MH INSTRUMENT FILE (#601).\n \n2. Patch YS*5.01*31 also includes six additional scales added to the test\n MMPI2 - Minnesota Multiphasic Personality Inventory-2. The new scales\n are as follows:\n \n MDS - Marital Distress Scale\n APS - Addiction Potential Scale\n \n AAS - Addiction Admission Scale\n S - Superlative Self-Presentation\n Fp - Infrequency-Psychopathology\n Ho - Hostility\n\n3. Five new routines are included in patch YS*5.01*31. They are:\n \n YS31ENV - YS*5.01*31 Patch Environment Check Routine\n YS31POST - YS*5.01*31 Patch Post Routine\n YTALUSE - Test-Audit Alcohol Screen\n a. Test Name: CAGE\n YTDOMR - Depression Outcome Module Report\n YTDOMR1 - Extended Interview Reporter\n\n4. One edited routine:\n\n YTMMPI2B - MMPI2 Harris:Lingos,Crit,OS\n \n Test Site(s): Dallas, TX\n Cleveland, OH\n Minneapolis, MN\n Description: A quick alcohol screening measure.\n Asheville, NC\n Portland, OR\n Canadaigua, NY\n Little Rock, AR \n \n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\n \n Number of Questions: 4\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YS31ENV N/A 2399932 31\n YS31POST N/A 133706 31\n YTALUSE N/A 744349 31\n YTDOMR N/A 11177067 31\n Number of Scales: 1\n YTDOMR1 N/A 4728910 31\n YTMMPI2B 14737364 15991750 10,31\n \n SOFTWARE RETRIEVAL:\n ===================\n The software files are available on one of the following CIO Field Offices'\n ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these \n files.\n\n
\nPatch YS*5.01*49 has been created to perform the following functions:\n4) Correct problem with the PATSTAT^YSDX3B call that returns the patient\n status (In-patient or Out-patient.)\n5) Correct an undefined error occurring in menu option GAF CASE FINDER [YSGAF\n CASE FINDER].\n \n1) Evaluate all Global Assessment of Functioning (GAF) data for fiscal\n years 1998 & 1999, and verify that all necessary pieces of information\n exist for each record.\n2) Retransmit all GAF scores for Fiscal Years 1998 & 1999 to the National\n Patient Care Database (NPCD) at the Austin Automated Center (AAC).\n3) Correct a filing error in the Mental Health ENTER DIAGNOSE [YSDIAGE]\n menu option.\n\n
\nSeven new Psychological Testing APIs/RPCs have been developed to allow reading \n one new file MH MULTIPLE SCORING (#601.6). This file allows the\nArray(6)=S1^Scale Name^Raw Score^Transformed Score\nArray(7)=S2^ Scale Name^Raw Score^Transformed Score\nAnd onward as needed.\n\nExample: \nInput\n-----\nYS("DFN")=83\nYS("CODE")=MMPI2\nYS("ADATE")=05/09/1994\n user to score multiple instruments.\n\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=CAPP,ANDY W^MMPI2^--- Minnesota Multiphasic Personality Inventory-2 --\n-^2940509^05/09/1994^CAULFIELD,MARY A\nYSDATA(3)=R1^TTTFTTFTTTFTTFFFFFFTTFFFFFFFTFFFFFFFFFFFFFFFFFFFFFFTFFFFFFFFFFFFFFF\nFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFTTTTTTFFFFFFFFFFFFFFFFFFFFFFFFFFFFFTTTTFFFTTFFFFFF\nFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF\nYSDATA(4)=R2^FFFFFFFFFFFFFFFFFFFFFFFFFTTTTTTTTTTTTTTTTFFFFFFFFFFFFFFFFFFFFFFFFFF\n\nFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF\nFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFTTT\nYSDATA(5)=R3^TTTTTTTTTTTTTTTTTTTTTTTFFFFFFFFFFFFFFFFFFFFTTFFFTFTFTFTFTFTFTFTFTFF\nFTFTFTFTFTFTFTFTFTFTFTFTTFTFTFTFFFFTFFTFTFTFTFTFTFFTFTFTFTFTFFFFFFFFFFFFFFFFFFFF\nFFFFFFFFFFFFFFFFFFFF\nYSDATA(6)=S1^L Lie^12^87\nYSDATA(7)=S2^F Infrequency^19^95\n.\n.\n.\n eleven new routines YSGAFAPI, YSMTI, YSMTI0, YSMTI1, YSMTI3\nYSDATA(89)=S84^Ma-S Hypomania, Subtle^10^50\n\n\n4. SAVEIT\n RPC: YTAPI SAVEIT\n M: SAVEIT^YTAPI1\nThis API allows saving of patient responses to a test or interview in the\nPSYCH INSTRUMENT PATIENT file (#601.2). The patient ien, the test code,\nand administration date is required along with the responses. All responses\nare checked for validity. No scoring is returned but successful addition\n YSMTI4, YSMTI5, YTAPI, YTAPI1, YTAPI2 and YTAPI3.\nto the PSYCH INSTRUMENT PATIENT file (#601.2) is indicated.\n \nInput: \n DFN : Patient internal identifier\n CODE: Test code from file 601 or "ASI" e.g. "CAGE", "BDI"\n ADATE: Inclusive administration date in %DT acceptable format (11/11/2011)\n Staff: DUZ of professional ordering the test\n R1: String of patient responses 1-200\n R2: String of patient responses 201-400 [as needed]\n R3: String of patient responses 401-600 [as needed]\n\n\nOutput:\nArray(1)=[DATA] indicates successful call\n\nExample:\nInput\n-----\nYS("DFN")=6\nYS("ADATE")="T"\nYS("CODE")="ZUNG"\n one new option Multiple Psych Testing [YT MTI] displays history of\nYS("STAFF")=67\nYS("R1")="12121212121212121212"\n\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=saved \n\n\n5. SHOWIT\n psychological testing for an individual patient.\n RPC: YTAPI SHOWIT\n M: SHOWIT^YTAPI3\n\nThis API returns the text, bottom, introduction and possible correct \nresponses for a specified test item in MH INSTRUMENT file (#601). It will\nwork only for tests as opposed to interviews or batteries. The ASI is\nnot supported.\n \nInput: \n CODE: Test code from in the MH INSTRUMENT file (#601) e.g. "CAGE", "BDI"\n\n ITEM: A positive whole number between 1 and the highest item number\n for the specified test.\n\nOutput:\nArray(1)=[DATA] ;indicates successful call\nArray(2)=MMPI2 item: 1 ;SECOND LINE IS TEST CODE AND ITEM NUMBER\nArray(3)=[BEGIN ITEM]; BEGINS EACH ITEM\nArray(4)=MMPI2^1 ;CODE^ITEM NUMBER\nArray(5)=[INTRO];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT\nArray(12)=[TEXT];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT\n\nArray(14)=[BOTTOM];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT\nArray(18)=[RESPONSE];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT\nArray(21)=[END ITEM]; ENDS EACH ITEM\n\nExample:\nInput\n-----\nYS("CODE")="MMPI2"\nYS("ITEM")=1\n\nand saving of psychological testing data. This data normally resides in the \nDocumentation for APIs and RPCs\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=[BEGIN ITEM]\nYSDATA(3)=MMPI2^1\nYSDATA(4)=[INTRO]\nYSDATA(5)=Please read each statement carefully and decide whether it is true\nYSDATA(6)=as applied to you or false as applied to you.\nYSDATA(7)= \nYSDATA(8)=If a statement is true or mostly true, as applied to you, answer 'T'.\n-------------------------------\nYSDATA(9)=If a statement is false or not usually true, as applied to you, \nanswer\nYSDATA(10)='F'.\nYSDATA(11)= \nYSDATA(12)=Remember to give your own opinion of yourself.\nYSDATA(13)=[TEXT]\nYSDATA(14)=I like mechanics magazines.\nYSDATA(15)=[BOTTOM]\nYSDATA(16)=T= True\nYSDATA(17)=F= False\n1. LISTALL\nYSDATA(18)=Answer= \nYSDATA(19)=[RESPONSE]\nYSDATA(20)=TFX\nYSDATA(21)=[END ITEM]\n\n\n6. SHOWALL\n RPC: YTAPI SHOWALL\n M: SHOWALL^YTAPI3\n\n RPC: YTAPI LISTALL\nThis API returns the text, bottom, introduction and possible correct \nresponses for all items in a test in the MH INSTRUMENT file (#601). It\nwill work only for tests as opposed to interviews or batteries.\nThe ASI is not supported.\n \nInput: \n CODE: Test code from the MH INSTRUMENT file (#601). e.g. "CAGE", "BDI"\n\nOutput:\nArray(1)=[DATA] ;indicates successful call\n M: LISTALL^YTAPI\nArray(2)=MMPI2 item: 1 ;SECOND LINE IS TEST CODE AND ITEM NUMBER\nArray(3)=[BEGIN ITEM]; BEGINS EACH ITEM\nArray(4)=MMPI2^1 ;CODE^ITEM NUMBER\nArray(5)=[INTRO];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT\nArray(12)=[TEXT];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT\nArray(14)=[BOTTOM];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT\nArray(18)=[RESPONSE];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT\nArray(21)=[END ITEM]; ENDS EACH ITEM\n.\n.\nThis API returns all psychological test administrations for a specified \n.\nArray(1003)=[BEGIN ITEM]; BEGINS EACH ITEM\nArray(1004)=MMPI2^567 ;CODE^ITEM NUMBER\nArray(1005)=[INTRO];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT\nArray(1012)=[TEXT];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT\nArray(1014)=[BOTTOM];HEADER ALWAYS PRESENT OPTIONALY FOLLOWED BY TEXT\nArray(1018)=[RESPONSE];HEADER ALWAYS PRESENT ALWAYS FOLLOWED BY TEXT\nArray(1021)=[END ITEM];ENDS EACH ITEM\n\nExample:\npatient during a specified time period. No scoring is returned.\nInput\n-----\nYS("CODE")="MMPI2"\nYS("ITEM")=1\n\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=[BEGIN ITEM]\nYSDATA(3)=MMPI2^1\n \nYSDATA(4)=[INTRO]\nYSDATA(5)=Please read each statement carefully and decide whether it is true\nYSDATA(6)=as applied to you or false as applied to you.\nYSDATA(7)= \nYSDATA(8)=If a statement is true or mostly true, as applied to you, answer \n'T'.\nYSDATA(9)=If a statement is false or not usually true, as applied to you, \nanswer\nYSDATA(10)='F'.\nYSDATA(11)= \nInput: \nYSDATA(12)=Remember to give your own opinion of yourself.\nYSDATA(13)=[TEXT]\nYSDATA(14)=I like mechanics magazines.\nYSDATA(15)=[BOTTOM]\nYSDATA(16)=T= True\nYSDATA(17)=F= False\nYSDATA(18)=Answer= \nYSDATA(19)=[RESPONSE]\nYSDATA(20)=TFX\nYSDATA(21)=[END ITEM]\n DFN : Patient internal identifier\n.\n.\n.\nYSDATA(6950)=[BEGIN ITEM]\nYSDATA(6951)=MMPI2^567\nYSDATA(6952)=[INTRO]\nYSDATA(6953)=[TEXT]\nYSDATA(6954)=Most married couples don't show much affection for each other.\nYSDATA(6955)=[BOTTOM]\nYSDATA(6956)=T= True\nPSYCH INSTRUMENT PATIENT file (#601.2) for patient responses and the\n BEGIN: Inclusive date in %DT acceptable format (11/11/2011) \nYSDATA(6957)=F= False\nYSDATA(6958)=Answer= \nYSDATA(6959)=[RESPONSE]\nYSDATA(6960)=TFX\nYSDATA(6961)=[END ITEM]\n\n\n7. GAFHX\n RPC: YS GAF API\n M: GAFHX^YSGAFAPI\n to begin search [optional]\n\nThis API returns the GAF scores for a specified patient. It can be \nconstrained by both date range and occurrence limit. Please note that data \nfor this API comes from the DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8).\n\nInput: \n DFN: Patient internal identifier\n BEGIN: Inclusive date in %DT acceptable format (11/11/2011) \n to begin search [optional]\n END: Inclusive date in %DT acceptable format (11/11/2011) \n END: Inclusive date in %DT acceptable format (11/11/2011) \n to end search [optional]\n LIMIT: Constrains to the last N diagnoses [optional]\n\nOutput:\nArray(1)=[DATA] ;indicates successful call\nArray(1)=GAF Score^Internal Date^External Date^Provider^Comment\n.\n.\nArray(N)=GAF Score^Internal Date^External Date^Provider^Comment\n\n to end search [optional]\nExample:\nInput\n-----\nYS("DFN")=29601\nYS("LIMIT")=3\n\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=100^2981209.1105^12/09/1998@11:05^DEVLIN,MARK^\n\nYSDATA(3)=99^2981209.092^12/09/1998@09:20^DEVLIN,MARK^\nYSDATA(4)=66^2981124.1406^11/24/1998@14:06^DEVLIN,MARK^\n\n\n Associated NOIS: None\n \n Test Site(s): Bay Pines Test LAB\n Tuscaloosa, AL\n West Palm Beach, FL\n \nOutput:\n \n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\nArray= internal administration date^external administration date^test code \n ------------ ------------ ----------- ----------\n YSGAFAPI N/A 1326501 53\n YSMTI N/A 9401597 53\n YSMTI0 N/A 3775566 53\n YSMTI1 N/A 8825610 53\n YSMTI3 N/A 6387181 53\n YSMTI4 N/A 13759340 53\n YSMTI5 N/A 8420657 53\n YTAPI N/A 9153058 53\n YTAPI1 N/A 3410744 53\nData is sorted in order of most recent administration to the oldest\n YTAPI2 N/A 6279046 53\n YTAPI3 N/A 4047466 53\n \n \n \n Installation Instructions:\n ==========================\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto your\nadministration. If no administrations are f,ound Array(2) will not be \n system.\n\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\nreturned. If patient has no PSYCH INSTRUMENT PATIENT file (#601.2) data,\n Backup a Transport Global\n \n 3. Users may remain on the system, but installation should be done at\n off peak hours.\n \n 4. Installation will take less than five minutes. \n \n 5. From the 'Installation Menu' of the KIDS menu, run the option \n 'Install Package(s)' Select the package 'YS*5.01*53' and proceed\n with install.\nMH INSTRUMENT file (#601) for test and interviews. In addition, the\nan error will be returned.\n\n 6. If you do not intend to queue the installation to run after normal\n business hours, then answer "NO" to the following prompt:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n If you answer "YES", then the installation will require much more \n than 5 minutes to run due to the menu rebuild process.\n\n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n\n and Protocols? YES//', respond NO.\nExample:\nInput\n-----\nYS("DFN")=6\nYS("BEGIN")="10/01/89"\nYS("END")="06/08/1999"\n\nOutput\nAPIs/RPCs retrieve ADDICTION SEVERITY INDEX data found in the ADDICTION\n------\nYSDATA(1)=[DATA] \nYSDATA(2)=2901120^11/20/1990^AOR\nYSDATA(3)=2900730^07/30/1990^ALCO\nYSDATA(4)=2900730^07/30/1990^HX2\nYSDATA(5)=2900730^07/30/1990^MROS\nYSDATA(6)=2900730^07/30/1990^PSOC\nYSDATA(7)=2900730^07/30/1990^TRMT\n\n\nSEVERITY INDEX file (#604) and Global Assessment of Functioning (GAF) data\n2. LISTONE\n RPC: YTAPI LISTONE\n M: LISTONE^YTAPI\nan error will be returned.\n\nExample: \nInput\n-----\nYS("DFN")=83\nYS("CODE")=MMPI2\nfound in the DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8).\nYS("SCALE")=2\n\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=2940509^05/09/1994^MMPI2^F Infrequency^19^95\nYSDATA(3)=2920925^09/25/1992^MMPI2^F Infrequency^26^116\nYSDATA(4)=2920924^09/24/1992^MMPI2^F Infrequency^25^113\n\n\n\n3. SCOREIT\n RPC: YTAPI SCOREIT\n M: SCOREIT^YTAPI2\nThis API returns all scoring information for a specified patient given a \nspecified administration date for a specified test or instrument. User \nmust have adequate privileges to receive this information (i.e. often the \nYSP KEY).\n \nInput: \n DFN : Patient internal identifier\nThis patch contains:\n CODE: Test code from MH INSTRUMENT file (#601) or "ASI"\n e.g. "CAGE", "BDI"\n ADATE: Inclusive administration date in %DT acceptable format (11/11/2011)\n\nOutput:\nArray(2)= Patient Name^Test Code^Test Title^Internal Admin date^External \nAdmin Date ^Ordered by\nArray(3)=R1^Responses 1-200 undelimited\nArray(4)=R2^ Responses 201-400 undelimited (even if less than 200)\nArray(5)=R3^ Responses 401-600 undelimited\n\n\nThis patch corrects an error that occurs in menu option "Identify Potential\nMerge Problems [XDR VALID CHECK]". Although it originally appeared to be a\nFILEMAN error, it was later determined to be a data dictionary problem with\nthe MEDICAL RECORDS file (#90) of the MENTAL HEALTH Version 5.01 software\napplication.\n\n
\nThe following items are addressed in patch YS*5.01*54:\n Number of Questions: 12\n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond NO.\n\n 7. Routine YS54POST will be deleted by KIDS after successful patch\n installation.\n Number of Scales: 1\n \n b. Test Name: AUDC\n Description: Alcohol Use Disorders Identification Test Condensed\n Number of Questions: 3\n Number of Scales: 1\n \n These tests are stored as new entries in the MH INSTRUMENT FILE (#601).\n \n\n 2. Two new routines are included in patch YS*5.01*54. They are:\n YTAIMS - Abnormal Involuntary Movement Scale\n YTALUSEC - Test-Audit Alcohol Screen Condensed\n\n 3. When the user selects option Psychological tests/interviews\n (administer) [YSADMTEST] and chooses the instrument "MMPI" a message\n is displayed on the screen "You have selected the "MMPI" instrument, \n the "MMPI2" instrument will be administered in its place.". Routines\n YTAR and YTS have been modified to display this message.\n\n 1. Patch YS*5.01*54 releases two new psychological tests/interviews to \n 4. The file MH INSTRUMENT (#601) field OPERATIONAL (#32) will be populated\n with a value of "N" for the instrument MMPI when the post routine YS54POST\n is executed.\n\n 5. Patch YS*5.01*54 also includes updates to the instruments AUDIT, \n CAGE, DOM80, DOM81, DOM82, DOMG, and the SMAST. These instruments were \n sent out in patch YS*5.01*31 as NON-EXEMPT, when they should have been \n sent out as EXEMPT. The file MH INSTRUMENT (#601) field EXEMPT TEST (#21)\n for the instruments mentioned will be populated with a value of "Y"\n when the post routine YS54POST is executed.\n the Mental Health package. These tests are accessed via menu item \n\n 6. Patch YS*5.01*54 also includes 2 additional entries in the MH INSTRUMENT \n FILE (#601). The Addiction Survey Index (ASI) and the Global \n Assessment of Functioning (GAF) are placeholders to be used in retrieving\n ASI and GAF data used by APIs and RPCs released in patch YS*5.01*53.\n These entries are non operational when accessed via menu item \n Psychological tests/interviews (administer) [YSADMTEST].\n \n Test Site(s): North Texas HCS, TX\n Palo Alto HCS, CA\n Psychological tests/interviews (administer) [YSADMTEST]. The new \n Puget Sound HCS, WA\n Salt Lake City, NV\n \n \n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n tests are as follows:\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YS54POST N/A 183160 54\n YTAIMS N/A 3709923 54\n YTALUSEC N/A 2558679 54\n YTAR 16901184 17157520 37,54\n YTDP 13752098 13773021 37,41,54\n \n YTS 9209637 9650076 37,54\n \n \n \n Installation Instructions:\n ==========================\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto your\n system.\n a. Test Name: AIMS\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Description: Abnormal Involuntary Movement Scale \n \n 3. Users may remain on the system, but installation should be done at\n off peak hours.\n \n 4. Installation will take less than five minutes.\n \n 5. From the 'Installation Menu' of the KIDS menu, run the option five\n 'Install Package(s)' Select the package 'YS*5.01*54' and proceed\n with install.\n\n\n
\nThis patch addresses the following problems associated with the Mental \n2. Problem: $ZE= PTFLP+4^YSASCF:1, %DSM-E-UNDEF, undefined variable.\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- --------------------\n YSASCF 16798624 15199657 38,45,55\n YSASFM 4829194 4829236 24,30,32,37,38,55\n YSASFUR 14346228 14504166 38,55\n YSASNAR 11476987 11561066 24,30,37,38,44,55\n YSASRU 11199368 11203518 24,30,32,38,55\n \n Installation Instructions:\n ==========================\n The option ASI Case finder [YSAS CASE FINDER] will error out at\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \n your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n PTFLP+4^YSASCF when it encounters A missing node in the PTF file (#45) \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\n multiple field 501 (#50). The code in routine YSASCF has been \n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*55' and\n proceed with install.\n \n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n\n 8. When prompted 'Want to DISABLE Scheduled Options, Menu\n corrected.\n Options, and Protocols? YES//', respond NO.\n \n3. Problem: $ZE= OE+3^YSASCF:1, %DSM-E-UNDEF, undefined variable\n The option ASI Case Finder [YSAS CASE FINDER] will error out at \n OE+3^YSASCF when the "B" cross reference was created for The Outpatient \n Encounter file (#409.68) but did not contain the zero node for that \nHealth ADDICTION SURVEY INDEX software.\n entry. The routine YSASCF has been modified to check if the entry\n exists.\n \n4. The option ASI Follow-up Finder [YSAS FOLLOWUP FINDER] generates a\n mail message that splits the results into separate mail messages for\n every 1000 lines. The subject of each mail message displays which\n page of how many pages there are for the report generated.\n Such as below:\n \n ASI Follow-up Reminder (1 OF 2),(2 of 2) etc. \n \n \n The page counter in the subject of the mail message created in routine \n YSASFUR has been corrected.\n\n5. The routine YSASCF has been corrected to retrieve the correct \n institution station number. This error would only occur at Anchorage,\n Honolulu, Las Vegas, San Juan and West Palm Beach.\n\n6. The option Activate/Inactivate ASI Program Types [YSAS ASI PROGRAM\n ACTIVATION] allows the user to edit the TITLE field (#1) instead of\n1. Problem: $ZE= <UNDEFINED>PUTWP+9^DIEFW.\n the ACTIVE field (#3) in the ASI PROGRAM TYPE file (#604.26). This\n has been corrected in routine YSASFM.\n\n7. When the narrative report prints, the employee who administers\n (interviewer) the Addiction Severity Index has a title that contains\n Roman Numerals. When converting the text from upper case to lower\n case the second Roman numeral in the interviewers title is printed\n in lower case. This has been corrected in routine YSASNAR. \n \nNOIS List: HON-0200-62334\n The option ASI National Roll Up [YSAS NATIONAL ROLL UP] gets the\n HOU-0100-70481\n FAV-1299-70811\n OKL-1199-72479\n BHH-1199-40801\n CMO-1099-41317\n NCH-1099-41338\n WIM-1099-20530\n BRX-1099-11552\n BUT-0999-22160\n MUS-0999-70276\n undefined error because of the change to the temporary data gathering \n ELP-0999-70673\n CON-0999-10634\n GNH-0999-40125\n WRJ-0999-11438\n DUB-0999-31427\n TAM-0899-32628\n FNC-0899-32323\n ALX-0899-71889\n MON-0899-50727\n MAD-0799-40048\n global structure after the installation of Mailman Patch 50 & FILEMAN \n WNY-0299-12238\n BRK-0299-11957\n NCH-0199-41750\n PAL-0199-61534\n LAS-1198-60407\n BRK-0798-11348\n LAS-0798-62572\n MAD-1097-40552\n STL-0797-41652\n \n V. 22. The code in routine ^YSASRU has been corrected.\n \nTest Site(s): Albany, NY\n Ann Arbor, MI\n Charleston, SC\n Honolulu, HI\n Madison, WI\n Montana HCS, MT\n Salt Lake City, UT\n VA Palo Alto HCS, CA\n \n \n \n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n\n
\nPatch YS*5.01*63 corrects the print problem in option "Graph of Patients\n\nNOIS call(s): DAY-0300-40087\n\nTest Site(s): Dayton, OH\n \n\n \n\n ROUTINE SUMMARY:\n ================\nRemaining" [YSCENREM]. Date entry is limited to month and year and results\n The second line of the routine now looks like:\n\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n\n Checksum Values\n\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n YSCEN81 10985668 10940348 63\n \nare graphed for each day in the month. Each day of the month's data is\n\n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \n your system.\n\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\ncalculated from the CENSUS file (#41.9) for the specified ward. \n the following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\nThis file contains the statistical data necessary for each ward\n \n 5. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*63' and\n proceed with install.\n\n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\nto create the daily G&L and bed status reports. The report did not work,\n \n 8. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO.\nwhen the month/year entered are greater than 12/99.\n\n\n\n
\nThis patch adds the NDC (National Drug Code) from the NDC field (#27) in\n ALT-0799-21661\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n \n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport \n CHS-1099-40369\n global.\n \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n These NOIS calls reported an undefined variable (YSCLR) that was\n 4. Users may remain on the system, installation may be done at\n any time except during the time scheduled for the Clozapine\n roll-up.\n \n 5. No options need to be placed out of service.\n \n 6. Installation time is less than 2 minutes during off peak hours\n and less than 5 minutes during peak hours.\n \n 7. Installation of this patch requires no additional memory\n causing problems with the weekly transmissions, measures have\n space.\n \n 8. From the 'Installation Menu' of the KIDS menu, run the option \n 'Install Package(s)' Select the package 'YS*5.01*61' and\n proceed with the install.\n \n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run to\n completion.\n \n been taken to prevent this error.\n 10. The routine YSCLPRE will be automatically deleted after the\n installation has run to completion.\n \n 2. PRO-0399-12547\n CLE-0799-41665\n PRO-0799-12531\n These NOIS calls reported a problem with the confirmation message\nthe PRESCRIPTION file (#52) to the Clozapine reporting software and clears\n that is sent to the site to report the number of patient data\n records transmitted to the national database and any errors.\n Errors were being reported in these messages, but the details were\n omitted. A sequence was established to ensure that the details\n will be included.\n \n 3. SYR-0799-10193\n LEX-0899-41770\n These NOIS calls reported a problem with the patients registration\n in the CLOZAPINE PATIENT LIST file (#603.01). Patients were being\nthe problems listed in the associated NOIS's.\n dropped from the file and could not be reregistered. Changes were\n made to allow the NCCC to reregister the patients.\n \n 4. SUX-0899-41033\n PRO-1099-11959\n ALN-0300-10936\n These NOIS calls reported a problem with the patients status\n changing from "Active" to "discontinued" each week. A more\n accurate method of determining active prescriptions has been\n implemented.\n \n \n \n Requesting Site: Washington, DC\n \n Test Site(s): Sioux Falls\n Chicago\n Lexington \n Biloxi\n \n Reference NOIS: BIL-0299-32473\n 1. BIL-0299-32473\n PUG-0399-52312\n PRO-0399-12547\n GNH-0699-42000\n SYR-0799-10193\n BOS-0799-10563\n CLE-0799-41665\n PRO-0799-12531\n SUX-0899-41033\n LEX-0899-41770\n PRO-1099-11959\n PUG-0399-52312\n ALT-1099-22157\n ALT-0799-21661\n CHS-1099-40369\n ALN-0300-10936\n \n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\n \n GNH-0699-42000\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30,1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \n YSCLPRE NEW 4869409 61\n YSCLSERV 27353057 33969291 18,22,26,47,61\n YSCLSRV1 NEW 1286296 61\n BOS-0799-10563\n YSCLTEST 8757130 9052437 18,22,26,47,61\n YSCLTST1 12256509 12553719 18,22,25,26,47,61\n YSCLTST2 11047742 11500297 18,22,26,47,61\n YSCLTST3 11776458 12171877 18,22,25,26,47,61\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n ALT-1099-22157\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO"\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n\n
\nTwo new Psychological Testing APIs/RPCs have been developed to allow reading\n Four new fields have been added to file MH MULTIPLE SCORING (#601.6).\nArray(5)=R3^ Responses 401-600 undelimited\nArray(6)=S1^Scale Name^Raw Score^Transformed Score\nArray(7)=S2^ Scale Name^Raw Score^Transformed Score\n .\n .\n And onward as needed\nArray("ON")= output text\n\nExample:\n--------\n The new fields are OUTCOMES (#5) and RESULTS (#6) a multiple containing\nInput\n-----\nYSDATA(1)=[DATA]\nYSDATA(2)=CAPP,ANDY W^MMPI2^--- ZUNG ---^2940509^05/09/1994^CAULFIELD,MARY A\nYSDATA(3)="12121212121212121212"\nYSDATA(4)=R2^\nYSDATA(5)=R3^\nYSDATA(6)=S1^Total^12^\nYSDATA("ON")= A mood disorder screening test (ZUNG) was in the low range \n(score = 12).\n sub-fields RESULTS NUMBER (#.01), RESULTS DESCRIPTION (#1) and RESULTS\n\nThe text and decision criteria is stored in MH MULTIPLE SCORING file (#601.6)\nfield RESULTS (#6), sub-field RESULTS TEXT (#2).\nExample of text to be stored:\nTest Code Score Text\n--------- ----- -----\nAUDIT <8 An alcohol screening test (AUDIT) was negative\n (score =|SCORE|).\n >7 An alcohol screening test (AUDIT) was positive\n (score =|SCORE|).\n TEXT (#2).\nAUDC <4 An alcohol screening test (AUDIT-C) was negative\n (score =|SCORE|).\n >3 An alcohol screening test (AUDIT-C) was positive\n (score =|SCORE|).\nBDI <10 The Beck Depression Inventory suggests minimal mood disorder\n (score =|SCORE|).\n 10-16 The Beck Depression Inventory suggests mild mood disorder\n (score =|SCORE|).\n 17-29 The Beck Depression Inventory suggests moderate mood disorder\n (score =|SCORE|).\n Four new routines YSMTI2, YSMTI6, YTAPI4 and YTAPI5.\n >29 The Beck Depression Inventory suggests severe mood disorder\n (score =|SCORE|).\nCAGE <2 An alcohol screening test (CAGE) was negative \n (score =|SCORE|).\n >1 An alcohol screening test (CAGE) was positive\n (score =|SCORE|).\nDOM80 A mood disorder screening test (DOM80) was negative.\n A mood disorder screening test (DOM80) was positive.\n 1. The DOM80 does not have a cut-off score. Rather, the\n algorithm is:\n One modified routine YTAPI2.\n a. If Q1 returned = Y, then the test is positive.\n b. If Q2 returned = Y and Q3 = Y and Q4 > 1, then the test\n is positive.\n c. If neither a nor b (above) is true, then the test is\n negative.\nDOMG <4 A mood disorder screening test (DOMG) was negative\n (score =|SCORE|).\n >3 A mood disorder screening test (DOMG) was positive\n (score =|SCORE|).\nMISS <107 This patient endorsed a significant number of items\n Two new APIs and Remote Procedures YTAPI PREVIEW and YTAPI OUTNOTE.\n associated with PTSD (MISS score =|SCORE|).\n >106 This patient endorsed fewer items associated with PTSD\n than is commonly found in Vietnam veterans diagnosed with\n PTSD (MISS score =|SCORE|).\nSMAST >2 Positive screen for alcoholism.\n 6 or 10 or 11 Previous treatment for alcoholism reported.\n <3 Negative screen for alcoholism.\nZUNG <33 A mood disorder screening test (ZUNG) was in the low range\n (score =|SCORE|).\n 33-50 A mood disorder screening test (ZUNG) was in the medium range\n\n (score =|SCORE|).\n >50 A mood disorder screening test (ZUNG) was in the high range\n (score =|SCORE|).\n\nAdditional Information\n----------------------\n1. The AIMS progress note should have each item and each item response \nincluded in the progress note. Below is an example progress note created\nusing an AIMS test from file MH INSTRUMENTS (#601). Note that the items are\nseparated by headings that are not in the item text, and that the first \nDocumentation for APIs and RPCs\n5 lines contain the total score and the number of items rated mild, moderate\nand severe.\n\nExample of an AIMS note\n-----------------------\nThe patient was evaluated for symptoms of tardive dyskinesia using the \nAIMS.\n Total score for items 1-7: 8\n Number of items 1-7 rated "mild": 1\n Number of items 1-7 rated "moderate": 1\n-------------------------------\n Number of items 1-7 rated "severe": 1\n \nFacial and oral movements:\n Muscles of facial expression Minimal\n Lips and perioral area Minimal\n Jaw None\n Tongue Moderate\n \nExtremity movements:\n Upper (arms, wrists, hands, fingers) Mild\nand saving of psychological testing data. This data normally resides in the \n1. PREVIEW\n Lower (legs, knees, ankles, toes) None\n \nTrunk movements:\n Neck, shoulders, hips Minimal\n \nGlobal judgments:\n Severity of abnormal movements Mild\n\n\n\n RPC: YTAPI PREVIEW\n NOIS Call(s): AMA-0200-70550\n \n Test Site(s): Amarillo, TX\n El Paso, TX\n Fargo, ND\n Grand Junction, CO\n Huntington, WV\n Miami, FL\n Sheridan, WY\n South Texas HCS\n M: PREVIEW^YTAPI4\n ST Louis, MO\n Tampa, FL\n West Palm Beach, FL\n White River Junction, VT \n\n \n\n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\nThis API allows scoring of patient responses to a test or interview without \n\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n\n Checksum Values\n\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n YSMTI2 N/A 7197346 62\n YSMTI6 N/A 550933 62\n YTAPI2 6279046 6291220 53,62\nmaking changes in the M database. The patient ien, the test code, and \n YTAPI4 N/A 2425764 62\n YTAPI5 N/A 3665995 62\n \n\n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \n your system.\n\nadministration date is required along with the responses. All responses are \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \nchecked for validity. Scoring is returned in the output documented in the \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*62' and\n proceed with install.\nSCOREIT API.\n \n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n\n 8. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO.\n\nInput: \nPSYCH INSTRUMENT PATIENT file (#601.2) for patient responses and the\n------\nDFN: patient internal identifier\nCODE: Test code from file 601 or "ASI" e.g. "CAGE", "BDI"\nADATE: inclusive administration date in %DT acceptable format (11/11/2011)\nStaff: DUZ of professional ordering the test\nR1: string of patient responses 1-200\nR2: string of patient responses 201-400 [as needed]\nR3: string of patient responses 401-600 [as needed]\n\nOutput:\nMH INSTRUMENT file (#601) for test and interviews. In addition, the\n-------\nArray(2)= Patient Name^Test Code^Test Title^Internal Admin date^External \nAdmin Date ^Ordered by\nArray(3)=R1^Responses 1-200 undelimited\nArray(4)=R2^ Responses 201-400 undelimited (even if less than 200)\nArray(5)=R3^ Responses 401-600 undelimited\nArray(6)=S1^Scale Name^Raw Score^Transformed Score\nArray(7)=S2^ Scale Name^Raw Score^Transformed Score\n .\n .\nAPIs/RPCs retrieve ADDICTION SEVERITY INDEX data found in the ADDICTION\n And onward as needed\n\n\nExample:\n--------\nInput\n-----\nYS("DFN")=6\nYS("ADATE")="T"\nYS("CODE")="ZUNG"\nSEVERITY INDEX file (#604) and Global Assessment of Functioning (GAF) data\nYS("STAFF")=67\nYS("R1")="12121212121212121212"\n\nOutput\n------\nYSDATA(1)=[DATA]\nYSDATA(2)=CAPP,ANDY W^MMPI2^--- ZUNG ---^2940509^05/09/1994^CAULFIELD,MARY A\nYSDATA(3)="12121212121212121212"\nYSDATA(4)=R2^\nYSDATA(5)=R3^\nfound in the DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8).\nYSDATA(6)=S1^Total^12^\n\n\n2. OUTNOTE\n RPC: YTAPI OUTNOTE\n M: OUTNOTE^YTAPI5\n\nThis API returns text to be entered in a progress note based on the outcome \nof a test administration. Input is the output of SCOREIT or PREVIEW API. \nOutput adds this text to the output YSDATA.\n\n\nInput:\n------ \nArray(2)= Patient Name^Test Code^Test Title^Internal Admin date^External \nAdmin Date ^Ordered by\nArray(3)=R1^Responses 1-200 undelimited\nArray(4)=R2^ Responses 201-400 undelimited (even if less than 200)\nArray(5)=R3^ Responses 401-600 undelimited\nArray(6)=S1^Scale Name^Raw Score^Transformed Score\nArray(7)=S2^ Scale Name^Raw Score^Transformed Score\nThis patch contains:\n .\n .\n And onward as needed\n\nOutput:\n-------\nArray(2)= Patient Name^Test Code^Test Title^Internal Admin date^External \nAdmin Date ^Ordered by\nArray(3)=R1^Responses 1-200 undelimited\nArray(4)=R2^ Responses 201-400 undelimited (even if less than 200)\n\n\nThis patch releases a new Mental Health API named YSGAFAP1. This API will \n Fargo, ND\n Grand Junction, CO\n Huntington, WV\n Miami, FL\n Sheridan, WY\n South Texas HCS\n ST Louis, MO\n Tampa, FL\n West Palm Beach, FL\n White River Junction, VT\nallow the calling routine to store the Global Assessment of Functioning (GAF) \n \n\n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n\n Checksum Values\ndata in the DIAGNOSTIC RESULTS - MENTAL HEALTH file (#627.8). The fields \n\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YSGAFAP1 N/A 1639398 64\n \n\n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \nthat will store the GAF data are PATIENT NAME (#.02), DATE/TIME OF \n your system.\n\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\nDIAGNOSIS (#.03), DIAGNOSIS BY (#.04), TRANSCRIBER (#.05), AXIS 5 (#65)\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\nand PATIENT TYPE (#66).\n 'Install Package(s)' Select the package 'YS*5.01*64' and\n proceed with install.\n\n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n \n 8. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO.\n\n\n Test Site(s): El Paso, TX\n\n
\nThis patch addresses the following issues in the Mental Health GAF software. \n subject 'NPT/XXX #XXXXXXXXXXXX' from the NPCD at the AAC. The 'XXXs'\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n in the subject are random alphanumerics produced by the AAC system. The\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*59' and\n proceed with install.\n\n 7. When prompted 'Enter the Coordinator for Mail Group 'YS\n GAF TRANSMISSION ACK':', respond with the name of the user\n responsible for monitoring the GAF performance measure.\n \n 8. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\n report will contain the number of messages received, number of messages\n of Install? YES//', respond YES.\n\n 9. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n\n 10. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO.\n processed and number of messages processed in error. The report will\n also contain a detail line for each type of error. The detail error line\n of the report will contain the reject message ID number, Error Code,\n Event Date-Time, Social Security Number, Last Name of Patient, Date\n of Birth and the Inpatient/Outpatient Status. A document, YS_501_59.PDF,\n describing the error codes provided by NPCD is available on one of the\n following OI Field Offices' ANONYMOUS.SOFTWARE directories in Albany,\n\n Hines or Salt Lake City.\n\n2. The routine YSGAFOBX was setting the Mail Group to use 'YS GAF TO NPCD',\n therefore sending a MAILMAN message containing text to be processed by \n NPCD at the AAC. These messages should have been sent locally to the\n members of Mail Group 'YS GAF TRANSMISSION ACK' who are responsible for\n the Global Assessment of Function monitoring. The subjects of these\n messages are 'GAF Score Sent' and 'GAF Score Transmission Problem'.\n The message 'GAF Score Sent' contains the patients name, date of\n observation the GAF score was assessed and the HL7 message number\n1. The description of Mail Group 'YS GAF TRANSMISSION ACK' has been edited.\n transmitted to NPCD at the AAC. The message 'GAF Score Transmission\n Problem' contains the reason why the message was not transmitted, user\n who entered the GAF score, patient name, observation date and file entry\n date.\n\n3. A new option 'GAF Transmission' [YS GAF TRANSMISSION] will be used to\n retransmit GAF data for a given date range to the National Patient Care\n Database at the Austin Automated Center in Austin, TX. \n\n\n This mail group will receive a message with the subject of 'GAF Score\nNOIS call(s): BOS-0399-12563\n TUA-0199-31948\n \n\nTest Site(s): Connecticut HCS, CT\n Gulf Coast HCS, MS\n Iowa City, IA\n Muskogee, OK\n Tampa, FL\n Portland, OR\n Sent' when a GAF score is transmitted to the National Patient Care\n West Palm Beach, FL \n\n DOCUMENTATION RETRIEVAL:\n ========================\n The documentation file is available on one of the following OI Field \n Offices' ANONYMOUS.SOFTWARE directories.\n All sites are encouraged to use their FTP capability to obtain this \n file.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n Database (NPCD) at the Austin Automation Center (AAC) in Austin, Texas.\n ================ =========== =========\n ALBANY 152.127.1.5 [ANONYMOUS.SOFTWARE]\n HINES 152.129.1.110 [ANONYMOUS.SOFTWARE]\n SALT LAKE 152.131.2.1 [ANONYMOUS.SOFTWARE]\n \n The documentation can be found in a file named YS_501_59_EC.PDF. \n\n \n\n ROUTINE SUMMARY:\n If an error in the transmission has occurred the subject of the message\n ================\n The second line of the routine now looks like:\n\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n\n Checksum Values\n\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n YSGAFOBX 3380035 3468829 43,50,59\n will be 'GAF Score Transmission Problem'. This mail group will also be\n YSGAFTR 5664313 4952427 43,49,59\n\n *** PLEASE NOTE THAT ROUTINE YSGAFOBX BEFORE PATCH CHECKSUM ***\n *** IS DIFFERENT FROM THE AFTER PATCH CHECKSUM IN THE ***\n *** RELEASED PATCH YS*5.01*50. ***\n \n\n Installation Instructions:\n\n ==========================\n used to receive a transmission report, GAF Facility Report, with the\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \n your system.\n\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n Print Transport Global\n\n
\nThe following items are addressed in patch YS*5.01*66:\n DAY-0200-42682\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Users may remain on the system, but installation should be done at\n off peak hours.\n \n 4. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n\n \n 5. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*66' and\n proceed with install.\n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO. \n2. The test (STAI), 'STATE-TRAIT ANXIETY SCALE', a general test of anxiety \n as a mood (state) and as a personality characteristic (trait) was scored\n directly. The Scale #2 Trait Anxiety (Item #34) has been changed to score\n indirectly.\n\n3. The test 'Personality Assessment Inventory' (PAI) scoring routine YTPAI\n has been edited to correct an indexing problem at ADDIT+5^YTPAI.\n\n\n4. The RESPONSE PROMPT field (#4), of the multiple ITEM NUMBER field (#1),\n of the MH INSTRUMENT file (#601) for the entry 'Personality Assessment\n Inventory' (PAI) has been changed to a semicolon following the word \n "false" so parsing of the response can be done.\n\n5. The RESPONSE PROMPT field (#4), of the multiple ITEM NUMBER field (#1),\n of the MH INSTRUMENT file (#601) for the entry 'Beck Anxiety Index' (BAI)\n has been changed to a semicolon following the word "unpleasant" so \n parsing of the response can be done.\n\n1. When selecting the option 'Psychological tests/interviews (administer)'\n6. The test 'Depression Outcomes Module' (DOM) scoring routine YSMTI1 was\n modified to allow multiple test scoring.\n\n7. The following fields were found setting %DT(0) to some value, with no\n corresponding Kill of %DT(0) in the Input Transform. Leaving %DT(0) \n defined can have an adverse impact on the end user. This patch places\n the KILL of %DT(0) after the call of ^%DT in the Input transform.\n ISF-1100-60368\n\n The following PSYCH INSTRUMENT PATIENT (#601.2) and SECLUSION/RESTRAINT \n [YSADMTEST] to administer the instrument 'Abnormal Involuntary Movement \n (#615.2) file/subfile fields Input Transforms have been edited:\n\n File/Sub-file# Field# Field Name\n 601.2/601.22 .01 COMPLETION DATE\n 4 ADMINISTRATION DATE\n 14 DATE BEGUN\n 601.2/601.2213 1 DATE OF COMMENT\n 5 DATE/TIME SIGNED\n 8 DATE/TIME COSIGNED\n 615.2 .01 FILE ENTRY DATE\n Scale' (AIMS) the user is instructed to enter the key letter "E" to view\n .03 DATE/TIME APPLIED\n 42 TIME REMOVED\n 54 REVIEW FILED\n 615.2/615.3 .01 CHECK TIME\n\n\n\n NOIS Call(s): ISF-1100-60368\n DAY-0200-42682\n\n examination procedures and then to enter any key in order to progress.\n\n Test Site(s): Dayton, OH\n Eastern Kansas HCS, KA\n Little Rock, AR\n Salt Lake City, UT\n VA Health Care Network Upstate New York System, NY\n \n \n ROUTINE SUMMARY:\n ================\n At the end of the instructions, any key will not work. The user has to\n \n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YSMTI1 8825610 8854657 53,66\n use the ENTER key to exit the instructions. This has been corrected to\n YTAIMS 3709923 3711230 54,66\n YTALUSR N/A 2954815 66\n YTPAI 7779058 7863323 10,66\n YTPCL N/A 4037903 66\n \n \n \n \n Installation Instructions:\n ==========================\n accept any key entered as instructed. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto your\n system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n\n
\n1. The YSCL WEEKLY TRANSMISSION [Weekly Clozapine Report] option should\nis no longer necessary and its associated task should be deleted (see item\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n \n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global.\n10 in the installation instructions below). The demographics data will\n \n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. Users may remain on the system, installation may be done at\n any time except during the time scheduled for the Clozapine\nnow be collected during the regular roll-up. No error will occur and no\n roll-up.\n \n 5. No options need to be placed out of service.\n \n 6. Installation time is less than 2 minutes during off peak hours\n and less than 5 minutes during peak hours.\n \n 7. Installation of this patch requires no additional memory\n space.\n \nharm will be done if this task remains active.\n 8. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*69 and\n proceed with the install.\n \n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run to\n completion.\n \n 10. Historically, the option YSCL TRANSMIT DEMOGRAPHICS\n [Transmit Clozapine Demographics] had been queued to run\n \n before the start of business every Tuesday. This function\n has been incorporated into the Clozapine Data Collection\n and this option is no longer used. This task should be\n deleted. This is accomplished using the XUTM SCHEDULE\n [Schedule/Unschedule Options] option. The following screen\n capture will closely resemble the display from your system.\n To delete the task, enter the @ sign in the Option Name field\n and press the Enter key. You will then be asked if you want\n to delete this record. Answer YES and press the Enter key.\n \n3. The CLOZAPINE LAB TEST file (#603.02) is no longer used for the\n Schedule/Unschedule Options\n \n Select OPTION to schedule or reschedule: YSCL TRANSMIT DEMOGRAPHICS (R)\n \n Edit Option Schedule\n Option Name: YSCL TRANSMIT DEMOGRAPHICS\n Menu Text: Transmit Clozapine Demographics TASK ID: 526664\n ____________________________________________________________________\n \n QUEUED TO RUN AT WHAT TIME: DEC 19,2000@02:00\nroll-up. The roll-up software will now use the CLOZAPINE LAB TEST field\n \n DEVICE FOR QUEUED JOB OUTPUT:\n \n QUEUED TO RUN ON VOLUME SET:\n \n RESCHEDULING FREQUENCY: 7D\n \n TASK PARAMETERS:\n \n SPECIAL QUEUEING:\n(#17.7) in the DRUG file (#50) to determine the WBC and ANC tests used for\n \n ______________________________________________________________________\n \n \n 11. The YSCL WEEKLY TRANSMISSION [Weekly Clozapine Report]\n option has been queued to run prior to the start of business\n one day a week. It has been recommended that the\n transmission occur on Tuesday, but transmission dates vary.\n The software has been modified to determine the correct day\n of the week to run. The option should now be tasked to run\neach drug. Using this method will ensure a common element between the\n daily prior to the start of business. The XUTM SCHEDULE\n [Schedule/Unschedule Options] option should be used to set\n the QUEUED TO RUN AT WHAT TIME: entry to tomorrows date at a\n time prior to the start of business and the RESCHEDULING\n FREQUENCY entry to "1D" (once daily). The following is an\n example of the display from the XUTM SCHEDULE option.\n \n Edit Option Schedule\n Option Name: YSCL WEEKLY TRANSMISSION\n Menu Text: Weekly Clozapine Report TASK ID: 518605\ndispensing and tracking of the prescription.\n ____________________________________________________________________\n \n QUEUED TO RUN AT WHAT TIME: T+1@0200\n \n DEVICE FOR QUEUED JOB OUTPUT:\n \n QUEUED TO RUN ON VOLUME SET:\n \n RESCHEDULING FREQUENCY: 1D\n \nnow be queued to run daily instead of weekly (see item 11 in the\n \n TASK PARAMETERS:\n \n SPECIAL QUEUEING:\n \n ______________________________________________________________________\n4. The Weekly Clozapine Report [YSCL WEEKLY TRANSMISSION] option has been\nmodified to respond to the Kernel Stop Task Manager [XUTM STOP] option.\nThis provides a graceful way to terminate processing of the roll-up.\n \n Requesting Site: National Clozapine Coordinating Center\n \n Test Site(s): Battle Creek\n Canandaigua\n Western New York\ninstallation instructions below). A new file CLOZAPINE PARAMETERS\n Pittsburgh\n \n Reference NOIS: BHS-0900-11492 CLOZAPINE DEMOGRAPHICS MESSAGE\n The message generated for the transmission of data\n to the national database indicates certain\n demographic data is missing for a patient,\n including the patient's name.\n \n STC-0500-40272 CLOZAPINE MONITOR shows No RX for\n several pts\n(#603.03) has been created to maintain site configuration and transmission\n ALN-0400-11672 CLOZAPINE MONITOR MESSAGE INCORRECT\n The message generated for the transmission of\n patient data to the national database incorrectly\n reported that some patients' had no prescription\n data. This was due to the method used to collect\n and compare the date of the prescription to the\n current date.\n \n \n SDC-0896-62071 CLOZAPINE MONITOR ILLEGALLY WANTS\ndata to be reported back to the National Clozapine Coordinating Center\n RACE\n Some sites were concerned because the Clozapine\n roll-up software requires that the patient's race\n be entered into the database. This is clinically\n relevant data and is required by both the\n manufacturer and the Food and Drug Administration\n (FDA). Race may be entered as long as permission\n to report this data is obtained on the consent to\n release document. See VHA Directive 99-035.\n \nNCCC in Dallas. This file also contains an entry indicating the day of\n \n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30,1994\n \n Checksum Values\n \nthe week the roll-up should occur.\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \n YSCLSERV 33969291 24479509 18,22,26,47,61,69\n YSCLSRV1 1286296 1579043 61,69\n YSCLSRV2 NEW 16840829 69\n YSCLTEST 9052437 12420746 18,22,26,47,61,69\n YSCLTST1 12553719 15378976 18,22,25,26,47,\n 61,69\n YSCLTST2 11500297 11122299 18,22,26,47,61,69\n \n YSCLTST3 12171877 13878933 18,22,25,26,47,\n 61,69\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n \n The site should answer "NO" to all three questions.\n2. The YSCL TRANSMIT DEMOGRAPHICS [Transmit Clozapine Demographics] option\n Note: You may not receive all three prompts at your site.\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n \n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n \n "Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO"\n \n\n
\nThis patch addresses the following issue in the Mental Health software. \n\n 5. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//, respond "NO".\n Test Site(s): Salt Lake City, UT \n \n\n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n\n\n Checksum Values\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n NO ROUTINES EXPORTED WITH THIS PATCH \n\n\n \n SOFTWARE RETRIEVAL:\n ===================\n \n 1. In the MH INSTRUMENT file (#601) field OPERATIONAL (#32), data value\n The following software and documentation files are exported as part of\n this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n YS_501_72.KID YS*5.01*72 KIDS build ASCII\n\n The software files are available on one of the following OI Field\n Offices' ANONYMOUS.SOFTWARE directories.\n \n has been changed from null to "N" in the following instruments CES,\n All sites are encouraged to use their FTP capability to obtain these \n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n\n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n FES, GES, WES, CPI, FIRO, SII, MYER, MCMI, MMPR and the M168. This\n \n \n Installation Instructions:\n ==========================\n This patch should be installed during 'OFF PEAK' hours when few or no \n users are on the system. Installation of the patch will take less than\n 5 minutes.\n \n 1. START UP KIDS\n From the KERNEL Installation and Distribution Systems (KIDS)\n field when SET to "N" indicates that the instrument is NOT operational.\n Menu, select the Installation menu [XPD INSTALLATION MENU]: \n\n Edits and Distribution ...\n Utilities ...\n Installation ...\n \n 2. SELECT INSTALLATION OPTION\n Select Installation Option: Load a Distribution\n Enter a Host File: YS_501_72.KID\n \n This allows the instrument to remain in the data base but can NOT be\n This Distribution contains Transport Globals for the following\n Package(s): YS*5.01*72\n\n Use INSTALL NAME: YS*5.01*72 to install the Distribution.\n \n NOTE: The following are OPTIONAL:\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes, such as DDs or templates.\n USED.\n b. Compare Transport Global to Current System - This option will\n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes, such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n\n transport global.\n \n 3. SELECT INSTALLATION OPTION: Install Package(s)\n \n Select KIDS OPTION: INSTALL PACKAGE(S)\n Select INSTALL NAME: YS*5.01*72\n \n 4. When asked "Want KIDS to INHIBIT LOGONS during the install? Yes//",\n respond "NO".\n\n\n
\nPatch YS*5.01*67 COTS ASI-MV introduces the required components necessary to\nand the patient interact with the ASI-MV. The clinician logs on to VistA,\n\n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \n Installation Instructions:\n ==========================\ninitializes program parameters, and enters patient demographic info. The\n This patch should be installed during 'OFF PEAK' hours when few or no users\n are on the system. Installation of the patch will take less than 5 minutes.\n \n 1. START UP KIDS\n From the KERNEL Installation and Distribution Systems (KIDS)\n Menu, select the Installation menu [XPD INSTALLATION MENU]: \n Installation\n Edits and Distribution ...\n Utilities ...\n Installation ...\npatient then responds to questions presented by the multimedia interface.\n \n 2. SELECT INSTALLATION OPTION\n Select Installation Option: Load a Distribution\n Enter a Host File: YS_501_67.KID\n \n This Distribution contains Transport Globals for the following\n Package(s): YS*5.01*67\n\n Use INSTALL NAME: YS*5.01*67 to install the Distribution.\n \nThe clinician needs not be present during the time when the patient is\n NOTE: The following are OPTIONAL:\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes, such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\nresponding to questions. After the patient completes the interview, the\n you to ensure the integrity of the routines that are in the\n transport global.\n \n 3. SELECT INSTALLATION OPTION: Install Package(s)\n \n Select KIDS OPTION: INSTALL PACKAGE(S)\n Select INSTALL NAME: YS*5.01*67\n \n 4. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? Yes//", respond "NO".\nclinician starts the interface (YSASIMV) again, to upload the interview\n \n 5. When asked "Want KIDS to INHIBIT LOGONS during the install? Yes//",\n respond "NO".\n\n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//, respond YES. When prompted to select the options\n you would like to place out of order, enter the following:\n\n Addiction Severity Index [YSAS ASI USER MENU]\n\ndata to VistA.\n 7. Retrieve and open the file: YS_501_67.ZIP\n \n 8. Place the MENTAL HEALTH ADDICTION SEVERITY INDEX MULTIMEDIA VERSION\n (ASI-MV) INSTALLATION AND USER GUIDE in a location that can be\n accessed by ASI-MV users.\n \n 9. Please refer to the POST INSTALLATION INSTRUCTIONS section of the\n MENTAL HEALTH ADDICTION SEVERITY INDEX MULTIMEDIA VERSION (ASI-MV)\n INSTALLATION AND USER GUIDE to install the COTS ASI-MV software,\n YS50167_ASIMV.EXE, YS50167_SecureDesktop.EXE and\n\n YS50167_KeyboardHook.DLL.\n\n 10. Place the option YS BROKER [YS BROKER] on the Mental Health users\n secondary menu.\n \n 11. Routine YS67 will be deleted after successful patch installation.\nSecureDesktop is a software module that restricts user (patient) access to \nthe Windows desktop, to task-switching functions, and to other programs on\ninstall and run the Commercial Off the Shelf (COTS) Addiction Severity Index\nthe workstation, while the patient responds to the interview. This module \nimplements the bulk of security countermeasures for the ASI-MV system.\n\nThe patch contains the following additions and modifications to the VistA\nMental Health software:\n\nData in the ASI QUICK FORM file (#604.66), REQUIRED field (#11) has been\nchanged from '1' to a Null value making the following questions to be \nnon-required for scoring the ASI: M10, M11, E23, E24, L31, L32, F37, F38,\nP21 and P22. This process will be performed by the post routine YS67.\nMultimedia Version (ASI-MV) software product.\n\nThe ADDICTION SEVERITY INDEX file (#604) fields CLASS (#.04) and CONTACT CODE \n(#.07) have a new selection code, "For ASI-MV".\n\nThe ADDICTION SEVERITY INDEX file (#604) fields ELECTRONICALLY SIGNED \n(#.51) and E SIGNATURE INTERVIEWER (#.52) data attributes have been changed\nto allow these fields data to be edited.\n\nTwo new entries have been added to the ASI NARRATIVE file (#604.68). \nThe two new narrative reports are the ASI-MV ITEM REPORT and the ASI-MV\n\nNARRATIVE.\n\nThe routine YSASNAR has been modified to produce the ASI-MV ITEM REPORT and \nthe ASI-MV NARRATIVE.\n\nThe new option YS BROKER [YS BROKER] contains the context necessary\nto interface the ASI-MV to VistA.\n\nA Remote Procedure YTAPI NEW ASI has been created.\n\nThe Mental Health ASI-MV, Vista version, is a software product that is the\nThe new routine YTAPI8 allows silent additions to the ADDICTION SEVERITY INDEX \nfile (#604).\n\n\n Test Site(s): Boston Health Care System, MA\n Puget Sound Health Care System, WA\n Salt Lake City, UT\n VA Health Care Network Upstate New York System, NY\n White City, OR\n\nresult of the combination of a commercial (COTS) multimedia application\n\n Routine Summary\n ===============\n\n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n(ASIMV) and a VA-developed interface to the VistA database (YSASIMV). The\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YS67 N/A 182239 67 (Deleted by Kids)\n YSASNAR 11561066 11815417 24,30,37,38,44\n 55,67\n YTAPI8 N/A 3139609 67\n\n SOFTWARE RETRIEVAL:\n ===================\n \nASI-MV is a patient self-administered psychological instrument that can be\n The following software and documentation files are exported as part of\n this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n YS_501_67.KID YS*5.01*67 KIDS build ASCII\n YS_501_67.ZIP BINARY\n - YS50167_ASIMV.EXE ASI-MV Interface Executable\n - YS50167_SecureDesktop.EXE Secure Desktop Executable\n - YS50167_KeyboardHook.DLL Keyboard Hook DLL used by Secure Desktop\nused to gather patient data directly from the patient. Both the clinician\n - YSASIMV_IGUM.PDF YS*5.01*67 ASI-MV Installation Guide\n User Manual\n\n The software files are available on one of the following OI Field\n Offices' ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these \n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n\n
\nAssociated patches: (v)SD*5.3*262 install with patch `YS*5.01*71'\nviz., psychological testing, the Addiction Severity Index (ASI), and\n SOFTWARE RETRIEVAL:\n ===================\n \n The following software and documentation files are exported as part\n of this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n YS_501_71.KID DG*5.3*447 ASCII\n SD*5.3*262\nthe Global Assessment of Functioning (GAF).\n XU*8*234\n YS*5.01*71\n \n Note: Please refer to the DG, SD, and XU informational patch\n descriptions for details on second line, checksums, and patch\n information.\n \n YS50171_Setup_123.EXE Mental Health Assistant BINARY\n This file is the complete install\n for the Mental Health Assistant\n \n GUI client.\n \n YS50171_MHA_IG.PDF YS*5.01*71 MHA Installation Guide\n YS50171_MHA_IG.DOC YS*5.01*71 MHA Installation Guide\n YS50171_MHA_UM.PDF YS*5.01*71 MHA User Manual\n YS50171_MHA_UM.DOC YS*5.01*71 MHA User Manual\n \n The software files are available on the following OI Field Offices'\n ANONYMOUS.SOFTWARE directories.\n \nAll previous tests completed by the selected patient are listed on the\n All sites are encouraged to use their FTP capability to obtain these\n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\nTest Results tab. A text report is shown for the selected test, and\n \n \n Installation Instructions:\n ==========================\n 1. Use the 'LOAD A DISTRIBUTION' option on the PackMan menu. The\n Host File name is YS_501_71.KID. Answer YES to the question:\n "Want to Continue with Load? YES//"\n \n \n 2. The patch has now been loaded into a Transport global on your\ngraphs of numeric scores are available across all instances of a given\n system. You now need to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n \ntest.\n 3. Users may remain on the system, but installation should be done \n at off peak hours.\n \n \n 4. Installation will take less than five minutes. \n \n \n 5. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'MHA GUI YS*5.01*71'\n and proceed with install.\n \n \n \n 6. If you do not intend to queue the installation to run after \n normal business hours, then answer "NO" to the following prompt:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n If you answer "YES", then the installation will require much more \n than 5 minutes to run due to the menu rebuild process.\n \nThe Order Tests tab enables the user to specify the staff person\n \n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install//', respond NO.\n When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? YES//', respond NO.\n \n \n 8. Retrieve and execute the file YS50171_Setup_123.EXE\n \n \nordering the test and to select from among the tests available to the\n 9. Place the MENTAL HEALTH ASSISTANT USER MANUAL in a location that \n can be accessed by MHA users.\n \n \n 10. Please refer to the POST INSTALLATION INSTRUCTIONS section of the \n MENTAL HEALTH ASSISTANT INSTALLATION GUIDE to install the MHA \n software.\n \n 11. Place the option YS BROKER1 [YS BROKER1] on the Mental Health \n users secondary menu.\n (v)XU*8*234 install with patch `YS*5.01*71'\nperson who ordered the test. Three data entry modes are available:\n(1) Staff entry is optimized for the entry of staff rating data (e.g.,\n the AIMS), which requires the user to see the test questions and\n answers.\n(2) Clerk entry is optimized for transcribing test data from paper\n answer sheets.\n(3) Patient entry is optimized for on-line testing of patients. The\n patient entry option contains security features to prevent\n unattended patients from using the PC in unauthorized ways.\n \n (v)DG*5.3*447 install with patch `YS*5.01*71'\nThe ASI tab lists all previous ASI interviews and makes it easy to view\neither the item report or narrative report for a selected interview.\nTo help with ASI performance measure compliance, the interval since the\nlast interview is displayed. New views of ASI data are the "Domain\nScores" and "Item Trends" buttons, which present graphical and tabular\ndata across multiple interviews. The Domain Scores button gives the\nuser the opportunity to see either problem severity ratings or\nevaluation factor scores. The Item Trends button displays responses to\nselected individual items. It is hoped that these data views will help\nwith treatment planning and treatment outcome monitoring. A user-\n \nfriendly interface for entering interview data is provided. This tab\nenables staff to quickly enter data, to easily jump from one item to\nanother, and to enter free text comments at any time. This tab should\ngreatly reduce data entry time, whether transcribing interview results\nfrom a paper form or entering them on-line during an interview.\n \nThe GAF tab affords the user an easy way to enter GAF ratings and to\nsee previous ratings, which are graphed to indicate trends. When\nentering a new rating, the rating is associated with the GAF rating\ncriteria. It is hoped this association will increase the reliability\nPatch YS*5.01*71 introduces the Mental Health Assistant Graphical User\nof ratings and reduce inter-rater variability in the assignment of GAF\nratings.\n \nThe patch contains one option, a data change to the PAI entry in the MH\nMULTIPLE SCORING (#601.6) file, a data change to the MMPI2, AUDC and\nthe DOMG entries in the MH INSTRUMENT (#601) file, 16 routines and 28\nRemote Procedures.\n \nThe new non-menu option YS BROKER1 [YS BROKER1] contains the context\nnecessary to interface the MHA GUI to VistA.\nInterface to VISTA.\n \n E3R#: 16712\n \n Associated NOIS: None\n Test Site(s): Minneapolis VAMC, MN\n Salt Lake City HCS, UT\n VA Health Care Network Upstate New York\n VA N. Florida/S. Georgia Veterans HCS\n VA North Texas HCS\n \n \n \n \n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \nThe Mental Health Assistant (MHA) is a graphical user interface for the\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YSASFS N/A 7192558 71\n YSASFS1 N/A 5234287 71\n YSASRPWP N/A 1197798 71\n YSGAFAPI 1326501 1400361 53,71\n YSMTI1 8854657 9272666 53,66,71\n YSMTI3 6387181 7243669 53,71\n YSMTI6 550933 3259607 62,71\n YSMTI7 N/A 1484572 71\nmost frequently used options within the VistA Mental Health Package,\n YTAPI 9153058 9597980 53,71\n YTAPI1 3410744 3829862 53,71\n YTAPI6 N/A 4909093 71\n YTAPI7 N/A 6440201 71\n YTAPI8 3139609 6353687 67,71\n YTAPI9 N/A 4471729 71\n YTRPEXT N/A 3203374 71\n YTRPWRP N/A 3186347 71\n \n \n\n
\n The Clozapine reporting software will automatically discontinue a \n \n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n \n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n \n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols?\n YES// NO"\n \n Clozapine data is transmitted to the field offices in Hines and Dallas. \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n \n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n \n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\nThe domain names have been changed from ISC-DALLAS.DOMAIN.EXT and \n \n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. Users may remain on the system, installation may be done at\n any time except during the time scheduled for the Clozapine\nISC-CHICAGO.DOMAIN.EXT to FO-DALLAS.DOMAIN.EXT and FO-HINES.DOMAIN.EXT.\n roll-up.\n \n 5. No options need to be placed out of service.\n \n 6. Installation time is less than 2 minutes during off peak\n hours and less than 5 minutes during peak hours.\n \n 7. Installation of this patch requires no additional memory\n space.\n \n \n 8. From the 'Installation Menu' of the KIDS menu, run the\n option:\n 'Install Package(s)' Select the package 'YS*5.01*74 and\n proceed with the install.\n \n 9. If any routines were unmapped as part of step 2, they\n should be returned to the mapped set once the installation\n has run to completion.\nTHIS PATCH WILL REPORT THE NEW RACE AND ETHNICITY ENTRIES TO THE NATIONAL \nCLOZAPINE DATABASE.\n \nINSTALLATION TIME FRAME : VA DIRECTIVE 2001-023 REQUIRES INSTALLATION OF \nTHIS PATCH WITHIN 30 DAYS FROM THE TIME OF INITIAL RELEASE.\npatient if the patient's prescription is over 28 days old. This prevents \n \n Requesting Site: National Clozapine Coordinating Center\n \n Test Site(s): Coatesville\n Boston\n Madison\n Portland\n \nReference NOIS: COA-0901-21209 CLOZAPINE PATIENTS INACTIVATED\n I've been informed by Pharmacy service that we\na patient from being issued medication on an expired prescription. The \n continue to have Clozapine patients being\n automatically inactivated (details can be\n provided). We have previously worked with\n Stephanie Todd from Dallas on specific problems,\n however, NOIS BAC-0701-40194 notes in response\n #22 that a patch is forthcoming.\n \n BAC-0701-40194 Random inactivation of clozapine\n pts\n Our pharmacy ADPAC has been reporting for awhile\nClozapine protocol requires a new prescription each time the medication \n about Clozapine patients being inactivated.\n I initially held off reporting this via NOIS\n because I knew that PSO*7*56 was going to\n address these problem previously reported by\n other sites. We installed it in March, but it's\n happened again randomly. This time I had the\n adpac report the patients name to me so that I\n can begin to look at it.\n \n BHS-0302-12595 Cloz trans failed\nis dispensed. Clozapine patients are being discontinued whose \n MAD-0402-41028 Clozapine transmission failed\n Both NOIS calls report an undefined error during\n data transmission. The reporting mechanism has\n been modified to prevent this error.\n UNY-0402-11524 CLOZARIL PATIENTS STILL BEING\n INACTIVATED\n I still have complaints of patients being\n inactivated for some reason and the pharmacy\n needs to activate each time before entering\n clozaril scripts. The local site has contacted\nprescriptions are current. This happens when the roll-up occurs between \n the NCCC and they just tell them to re-activate\n and there is nothing wrong on their end.\n \n \n ROUTINE SUMMARY:\n ================\n \n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30,1994\nthe time when the prescription is entered into the system and when it is \n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \n YSCLSERV 24479509 25083145 18,22,26,47,\n 61,69,74\n YSCLSRV1 1579043 1605367 61,69,74\n YSCLSRV3 N/A 7345805 74\ndispensed. This patch will prevent the patient from being discontinued \n YSCLTEST 12420746 12047382 18,22,26,47,\n 61,69,74\n YSCLTST1 15378976 15450428 18,22,25,26,\n 47,61,69,74\n YSCLTST2 11122299 11178871 18,22,26,47,\n 61,69,74\n YSCLTST3 13878933 15031797 18,22,25,26,\n 47,61,69,74\n \nList of preceding patches: 18,22,25,26,47,61,69\nuntil the prescription is 28 days past the fill date.\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site.\n\n
\nThis patch addresses the following issues in the Mental Health software. \n properly. This has been corrected in MHA 1.0.2.10.\n ISM-0702-90939\n EKH-0698-41771\n \n \n \n Test Site(s): Battle Creek VAMC, MI\n Miami VAMC, FL\n Minneapolis VAMC, MN\n Portland VAMC, OR\n VA Central Texas HCS\n CLE-0303-41699\n VA Health Care Network Upstate New York\n VA N. Florida/S. Georgia Veterans HCS\n VA NORTHERN CALIFORNIA HCS\n \n \n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n \n Checksum Values\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n YSPOS70 N/A 137198 70\n YSPRE70 N/A 401194 70\n YSLOCN 1357796 1317415 70\n YSMTI3 7694272 7918553 53,71,76,70\n YTALUSEC 2558679 3281368 54,70\n YTCESD N/A 2054143 70\n 2. New scales have been added to the Minnesota Multiphasic Personality \n YTLCTD 2849688 2159359 70\n YTMMPI2B 17200069 18391657 10,31,76,70\n YTPHQ9 N/A 2995455 70\n \n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n SOFTWARE RETRIEVAL:\n ===================\n \n The following software and documentation files are exported as part\n Inventory-2 (MMPI2). The new scales are the Restructured Clinical\n of this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n YS_501_70.KID YS*5.01*70 ASCII\n \n YS_501_70.ZIP Mental Health Assistant BINARY\n This file is the complete install\n for the Mental Health Assistant\n GUI version 1.0.2.10 client.\n (RC) Scales for the MMPI2. The RC scales are based on recent factor\n \n - YS_MHA.EXE MHA2 Executable\n \n YS50170_Setup_125.EXE Mental Health Assistant BINARY\n This file is the complete install\n for the Mental Health Assistant\n GUI version 1.0.2.10 client.\n \n - YS_MHA.exe MHA2 Executable\n - YS_MHA_SD.exe Secure Desktop Executable\n analyses of the existing Clinical Scales, and are intended to be used\n - YS_MHA_KH.DLL Keyboard Hook DLL used by Secure Desktop\n - YS_MHA.Hlp Online Help file\n - YS_MHA.GID Online Help configuration file\n \n \n The software files are available on the following OI Field Offices'\n ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these\n files. Use the FTP address "download.vista.domain.ext" (without the\n as aids in the interpretation of the Clinical Scale profile. The names\n quotes) to connect to the first available FTP server where the files\n are located.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \n of the 9 RC scales are as follows (note that there is no RC5 scale):\n Installation Instructions:\n ==========================\n 1. Use the 'LOAD A DISTRIBUTION' option on the Installation menu of the\n KIDS menu. The Host File name is YS_501_70.KID. Answer YES to the\n question: "Want to Continue with Load? YES//"\n \n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the \n RCd: Demoralization\n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n\n 3. Users may remain on the system, but installation should be done \n at off peak hours.\n \n RC1: Somatic Complaints\n \n \n 4. Installation will take less than five minutes. \n \n \n 5. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*70'\n and proceed with install.\n \n \n RC2: Low Positive Emotions\n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install//', respond NO.\n When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? YES//', respond NO \n\n 7. Routines YSPRE70 and YSPOS70 are deleted after the installation has\n successfully completed.\n RC3: Cynicism\n RC4: Antisocial Behavior\n RC6: Ideas of Persecution\n RC7: Dysfunctional Negative Emotions\n RC8: Aberrant Experiences\n RC9: Hypomanic Activation\n \n Note:\n 1. Patients who take the BECK SCALE FOR SUICIDAL IDEATION (BSI) test on\n The set of MMPI2 scales that are scored and the order in which they are \n presented has been changed to be consistent with the recommendations of \n the test authors and publisher. \n \n The PTSD-Schlenger scale is no longer scored.\n \n \n 3. Three new psychological tests have been added to the MH INSTRUMENT \n (#601) file. The new depression measures include the 20-item version\n Center for Epidemiologic Studies Depression Scale (CESD), the Center \n the Mental Health Assistant are presented with questions that do not \n For Epidemiological Studies Depression Scale 5 Items (CESD5) and the \n Prime-MD Patient Health Questionnaire (PHQ9). The PHQ9 is based on \n the 9 DSM-IV criteria for Major Depressive Episode, and test results\n include both the number of criteria met as well as indication of \n whether the criteria for MDE are met. All can now be administered \n using the Mental Health Assistant.\n \n 4. The Alcohol Use Disorders Identification Test Condensed (AUDC) has been\n revised to meet the new Alcohol Screening Performance Measure issued by\n the Office of Quality and Performance.\n make sense when compared to their previous answers. For example, the \n \n 5. The Alcohol Use Disorders Identification Test Condensed Revised (AUDCR)\n has been made non-operational by setting the value to "N" in the \n MH INSTRUMENT file (#601) OPERATIONAL field (#32).\n \n 6. An entry to the COPYRIGHT HOLDER file (#601.3) has been made for the new\n psychological test PHQ9.\n \n 7. The instrument Revised NEO Personality Inventory (NEOPI) in the MH\n MULTIPLE SCORING file (#601.6), which allows the user to score\n patient says that he/she is not suicidal but the test asks him/her \n multiple instruments, has been edited to correctly return scale \n scores to be displayed on the Test Results in the Mental Health\n Assistant (MHA).\n \n Also corrected within the NEOPI is item #86 which read "When I'm under \n a great deal of stress, sometimes I fell like I'm going to pieces.". \n Item #86 now reads as "When I'm under a great deal of stress, sometimes\n I feel like I'm going to pieces." \n \n \n detailed questions about the last attempt and possible future attempts\n 8. When running option List Test and Interviews [YSMLST] from programmer\n prompt...%DSM-E-ENDOFILE, end of file encountered. This error has been \n corrected.\n EKH-0698-41771\n \n\n 9. The instrument Millon Clinical Multiaxial Inventory-III (MCMI3) in the \n MH INSTRUMENT file (#601) ITEM NUMBER field (#1) entry #41 which read\n "I've done a number of stupid things on impulse that needed up causing \n me great trouble.". Item Number #41 now reads as "I've done a number of\n at suicide. The skip logic for the BSI was not included in MHA.\n stupid things on impulse that ended up causing me great trouble."\n CTX-1003-71717\n\n Also within the MCMI3 the TEST SCALE NUMBER field (#16) SCALE NAME\n sub-field (#.05) for entries 12, 14 and 15 which read:\n\n 6B Aggressive/Sadistic\n 8A Passive-Aggressive\n 8B Self-Defeating\n\n The skip logic for the BSI using the List Manager software worked\n SCALE NAME entries 12, 14 and 15 now read as:\n\n 6B Sadistic\n 8A Negativistic\n 8B Masochistic\n \n \n \n NOIS call(s): CTX-1003-71717\n CLE-0303-41699\n\n
\nThis patch fixes problems with scoring of the MBMD instrument.\n\n
\nThis patch contains routine YSGAFHL7 which has been modified to send the\n Test Site(s): HEARTLAND-WEST HCS\n Miami VAMC, FL\n Minneapolis VAMC, MN\n New York HCS, NY\n \n\n ROUTINE SUMMARY:\n ================\n \n The second line of the routine now looks like:\nnew race and ethnicity data to the National Patient Care Database (NPCD) in\n \n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YSGAFHL7 5831582 5842715 43,81\n\n\nAustin, TX.\n\n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your\n system.\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n 4. Users may remain on the system.\n 5. Installation will take less than five minutes.\n this patch requires no additional memory space.\n\n 6. From the 'Installation Menu' of the KIDS menu, run the option \n 'Install Package(s)' Select the package 'YS*5.01*81' and proceed\n with install.\n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n YES//', respond NO.\n 8. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond NO.\n Associated E3R: N/A\n\n Associated NOIS: N/A\n\n\n
\nThis patch replaces the Mental Health option Usage Statistics [YSMUSE] with \n\n \n Checksum Values\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n YSTUSE N/A 1776923 87\n YTSTAT 5120372 N/A - Deleted during the install\n\n\n Installation Instructions:\n ==========================\nThe server option Mental Health Test Usage Server [YS TEST USAGE] is \n\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \n your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \nactivated by a mail message. The mail message invokes the routine YSTUSE \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\nwhich returns the results of the psychological test instrument usage at the \n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*87' and\n proceed with install.\n \n 7. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\n of Install? YES//', respond YES. Responding with a yes, will\n add considerable time to the installation.\n \nsite the mail message is sent to. \n 8. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n \n 9. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO.\n \n NOTE: Routine YTSTAT is deleted during the patch installation.\n\n\nThis is an example to invoke the server to create the mail message.\n\nSelect OPTION NAME: XMUSER MailMan Menu\n\na new Mental Health option Mental Health Test Usage Server [YS TEST USAGE].\nVA MailMan 8.0 service for XXXX.XXXX_X@MHCVSS.FO-ALBANY.DOMAIN.EXT\nYou last used MailMan: 09/14/04@17:01\nYou have 2 new messages.\n\n\n NML New Messages and Responses\n RML Read/Manage Messages\n SML Send a Message\n Query/Search for Messages\n AML Become a Surrogate (SHARED,MAIL or Other)\nThis is a server option to be used only by the members of the National Mental \n Personal Preferences ...\n Other MailMan Functions ...\n Help (User/Group Info., etc.) ...\n\nSelect MailMan Menu Option: S Send a Message\n\nSubject: YS TEST USAGE\nYou may enter the text of the message...\nInput file does not exist\n[EOB]\nHealth Strategic Healthcare Group (MHSHG) to determine the annual \n*C\n\n\n\n3031001^3040930 <--------- The dates requested to do the search \n must be in VA FILEMAN's conventional\n[EOB] internal format. The first date is the\n start date and the second date is the \n end date for the request.\n\npsychological test instrument usage at a site.\n*EX\nUSER$:[XXXXXXX]DIWE$545444715.TMP;1 1 line\n\nSend mail to: XXXXXX,XXXX X// S.YS TEST USAGE Mental Health Test \nUsage Server --------------- \nAnd Send to: The form of the mail message is identical to \n any other mail message except that it is \n addressed to S.<option name>. The "S." routes \n the message to the server request software.\n\n\n\nThe output from the server request is returned in the form of a MAILMAN \nmessage. This is an example of the server request to S.YS TEST USAGE.\n ---------------\n\nSubj: MH testing Statictics: YS TEST USAGE [#79130] 09/15/04@14:39\n14 lines\nFrom: MH AUTOMATED TESTING REPLY In 'IN' basket. Page 1 *New*\n-------------------------------------------------------------------------------\n377^Dallas OIFO^377\nThis patch contains one new server option Mental Health Test Usage Server [YS \nFrom: 3031001 To: 3040930\n \nAUIR^7^2\nCRS^19^3\nZUNG^87^1\nMMPI2^202^1\nMISS^205^3\nPAI^216^1\nBDI^223^1\nCAGE^226^2\nTEST USAGE] and one new routine YSTUSE. Option Usage Statistics [YSMUSE] \nAIMS^234^1\nBDI2^245^4\nMCMI3^246^1\n\n\n\n Nois call(s): None\n \n \n Test Site(s): Minneapolis VAMC, MN\nand routine YTSTAT are deleted during installation of the patch.\n Salt Lake City VAMC, UT\n VA Health Care Network Upstate New York, NY\n\n E3Rs: None \n\n\n ROUTINE SUMMARY\n ===============\n The second line of the routine now looks like:\n <tab> ;;5.01;MENTAL HEALTH;**[Patch List]**;Dec 30, 1994\n\n
\n****************************************************************************\nProfessional Version 2002 Service Pack 1. \n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n\n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*78' and\n proceed with install.\n \n 7. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\nThis patch also deletes option YS BROKER [YS BROKER] from the OPTION file\n of Install? YES//', respond YES. Responding with a yes, will\n add considerable time to the installation.\n \n 8. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n \n 9. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO. \n\n 10. Retrieve and open the file: YS_501_78.ZIP\n(#19).\n \n 11. Place the MENTAL HEALTH ADDICTION SEVERITY INDEX MULTIMEDIA VERSION\n (ASI-MV) INSTALLATION AND USER GUIDE in a location that can be\n accessed by ASI-MV users.\n \n 12. Please refer to the POST INSTALLATION INSTRUCTIONS section of the\n MENTAL HEALTH ADDICTION SEVERITY INDEX MULTIMEDIA VERSION (ASI-MV)\n INSTALLATION AND USER GUIDE to install the COTS ASI-MV software,\n YS_ASIMV.EXE, YS_ASIMV_SD.EXE and YS_ASIMV_KH.DLL.\n \n\n 13. Place the option YS BROKER1 [YS BROKER1] on the Mental Health users\n secondary menu if it does not already exist.\n\n Nois call(s): PRO-1103-12097\n LIT-1103-71512\n GRJ-1103-51290\n ANC-1003-52367\n*IMPORTANT NOTE TO IRM THIS PATCH MUST BE INSTALLED. ALTHOUGH NO ROUTINES *\n SBY-1003-32313\n FGH-1003-31033\n MAC-1003-60102\n CHY-0903-52052\n NOL-0903-71215\n NTH-0903-71179\n HWH-0903-41110\n ALT-0402-20514\n BHS-0102-11169 \n \n*ARE INCLUDED IN THIS PATCH KIDS DELETES THE OPTION YS BROKER [YS BROKER] *\n \n Test Site(s): Atlanta VAMC, GA\n Cheyenne VAMC, WY\n Grand Junction VAMC, CO\n Little Rock VAMC, AR\n Houston VAMC, TX\n New Orleans VAMC, LA\n Oklahoma City VAMC\n Salisbury VAMC, NC\n Salt Lake City, UT\n*WHEN THE PATCH IS INSTALLED. *\n Topeka VAMC, KA\n VA Health Care Network Upstate New York System, NY\n VA Puget Sound Healthcare System, WA\n\n ROUTINE SUMMARY\n ===============\n The second line of the routine now looks like:\n <tab> ;;5.01;MENTAL HEALTH;**[Patch List]**;Dec 30, 1994\n \n Checksum Values\n****************************************************************************\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n N/A\n\n\n The following software and documentation files are exported as part of \n - YSASIMV_IGUM.PDF YS*5.01*78 ASI-MV Installation Guide\n this patch:\n \n File Name Contents Retrieval Format\n\n --------- -------- ----------------\n YS_501_78.ZIP BINARY\n - YS_501_78_SETUP_1_0_3_10.EXE ASI-MV complete install for version\n 1.0.3.10 of the ASI-MV\n - YS_ASIMV.EXE ASI-MV Interface Executable\n - YS_ASIMV_SD.EXE Secure Desktop Executable\n - YS_ASIMV_KH.DLL Keyboard Hook DLL used by Secure Desktop\n - YS_ASIMV.EXE ASI-MV Interface Executable\n - YS_ASIMV_SD.EXE Secure Desktop Executable\n - YS_ASIMV_KH.DLL Keyboard Hook DLL used by Secure Desktop\nPatch YS*5.01*78 updates the file YS_ASIMV.EXE to be invoked from the \n - YSASIMV_IGUM.PDF YS*5.01*78 ASI-MV Installation Guide\n User Manual\n - YSASIMV_IGUM.DOC YS*5.01*78 ASI-MV Installation Guide\n User Manual\n \n The software files are available on one of the following OI Field\n Offices' ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these \n files. Use the FTP address "download.vista.domain.ext" (without the\nComputerized Patient Record System (CPRS) GUI Tool Bar. YS_ASIMV.EXE now\n quotes) to connect to the first available FTP server where the files\n are located.\n\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \nsupports Windows 2000 (W2K) operating system and Microsoft Windows XP \n\n Installation Instructions:\n ==========================\n\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \n your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n\n
\n=============================================================================\n(#2) for the entry the Beck Depression Inventory-II (BDI2) a period has \n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n\n Installation Instructions:\n ==========================\n\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto \nbeen added to the end of each response number. This will allow a reminder\n your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global. On the KIDS menu, under the 'Installation' menu, use\n the following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\nto be built by the Clinical Reminder software. Here is an example of the\n Backup a Transport Global\n \n 3. Installation of this patch should be at off peak hours.\n \n 4. Users may remain on the system.\n \n 5. Installation will take less than five minutes. Installation\n of this patch requires no additional memory space.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\nedit made to ITEM NUMBER 2 of the BDI2 instrument using a FILEMAN inquiry:\n 'Install Package(s)' Select the package 'YS*5.01*84' and\n proceed with install.\n \n 7. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\n of Install? YES//', respond NO. Responding with a yes, will\n add considerable time to the installation.\n \n 8. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//', respond NO.\n \n\n 9. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//', respond NO. \n\n 10. Please refer to the POST INSTALLATION INSTRUCTIONS section of the \n MENTAL HEALTH ASSISTANT VERSION 2 INSTALLATION GUIDE to install the \n MHA software.\nBefore patch:\n\nITEM NUMBER: 2 VALID RESPONSE SET: 0123X\n TEXT: PESSIMISM\n \n*IMPORTANT NOTE TO IRM THIS PATCH MUST BE INSTALLED. ALTHOUGH NO ROUTINES *\n 0 I am not discouraged about my future.\n 1 I feel more discouraged about my future than I used to be.\n 2 I do not expect things to work out for me.\n 3 I feel my future is hopeless and will only get worse.\n\nAfter patch:\n\nITEM NUMBER: 2 VALID RESPONSE SET: 0123X\n TEXT: PESSIMISM\n \n*ARE INCLUDED IN THIS PATCH KIDS UPDATES THE MH INSTRUMENT file (#601) WITH *\n 0. I am not discouraged about my future.\n 1. I feel more discouraged about my future than I used to be.\n 2. I do not expect things to work out for me.\n 3. I feel my future is hopeless and will only get worse.\n\n\n2. In the Mental Health Assistant GUI version 1.0.2.9 when using the mouse \nscroll button in the left-hand pane, the pane freezes at times. Returning \nto the desktop the mouse arrow suddenly becomes unresponsive to mouse \nmovements and begins performing the movements that should have occurred in \n*DATA WHEN THE PATCH IS INSTALLED. *\nthe Mental Health Assistant - in the same area of the screen where the lists \nof tests was. This has been corrected in MHA 1.0.2.10 to properly navigate \nthe large amounts of patient psychological test data users may have.\n\n3. The instrument ANALYSIS OF RELATIONSHIPS (AOR) has been made\nnon-operational by setting the value to "N" in the MH INSTRUMENT file\n(#601) OPERATIONAL field (#32).\n\n\n Nois call(s): None\n=============================================================================\n \n \n Test Site(s): New Orleans VAMC, LA \n Portland VAMC, OR\n Salt Lake City VAMC, UT\n VA Health Care Network Upstate New York\n \n\n\n ROUTINE SUMMARY\n\n ===============\n The second line of the routine now looks like:\n <tab> ;;5.01;MENTAL HEALTH;**[Patch List]**;Dec 30, 1994\n \n Checksum Values\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n N/A\n\n\nPatch YS*5.01*84 addresses three issues within the Mental Health software.\n The following software and documentation files are exported as part of \n this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n YS_MHA.exe Mental Health Assistant Binary\n Executable GUI version 1.0.2.10\n client.\n YS50184_Setup_123.EXE Mental Health Assistant BINARY\n This file is the complete install\n\n for the Mental Health Assistant\n GUI version 1.0.2.10 client.\n \n - YS_MHA.exe MHA Executable\n - YS_MHA_SD.exe Secure Desktop Executable\n - YS_MHA_KH.DLL Keyboard Hook DLL used by Secure Desktop\n - YS_MHA.Hlp Online Help file\n - YS_MHA.GID Online Help configuration file\n \n The software files are available on one of the following OI Field\n1. In the MH INSTRUMENT file (#601), ITEM NUMBER field (#1), TEXT sub-field \n Offices' ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these \n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n\n
\nUnder certain coditions when entering an Outpatient ASI the message \nProgress Note Created will display when it has not been created.\n\n
\nRecent changes in the Clozapine protocol require changes to the Clozapine \nin the past.\n \nEnter the type of the test for Clozapine: WHITE BLOOD COUNT\nEnter the reporting method of the test for Clozapine: ?\n \nEnter a code from the list.\n \n Select one of the following:\n \n 0 uL\n 1 K/uL\n \n 2 Percent\n \nEnter the reporting method of the test for Clozapine: 2 Percent\n \nEnter the name of the test for Clozapine:\n \nThe FDA (Food and Drug Administration) uses White Blood Cell Count and \nAbsolute Neutrophil Count as the definitive tests to verify for Clozapine \nuse, however your lab may report your data under any of the names you \nenter into these lists. If the WBC and ANC are not directly available, \nThe weekly roll-up creates a report that is sent to the local G.PSOCLOZ \nANC will be calculated from the other data available and presented to \nPharmacy (and CPRS (Computerized Patient Record System) during a later \nrevision) at the time of dispense and used to evaluate the safety under \nFDA limits. Only the most recent WBC will be accepted, and the date and \ntime stamp of the Neutrophil count must match the date and time stamp of \nthe WBC.\n \n \nWHITE BLOOD CELL (WBC)\n \nmail group. This report lists the patients reported to the national \nFor reference "White Blood Cell Count" is a portion of the total blood \ncontent and the sum total of two different kinds of cells - \n \n AGRANULOCYTES - those cells which do not have granules\n that absorb a stain. These cells are subdivided\n into Lymphocytes and Monocytes. \n \n GRANULOCYTES -- those cells which contain granules\n that absorb a stain. These cells are subdivided\n into Neutrophils, Basophils, and Eosinophils. \ndatabase along with an indicator showing whether or not Lab and RX data \n \nBoth Agranulocytes and Granulocytes are part of the Total White Blood \nCell Count. Therefore, the total WBC is the sum of five different types \nof cells. \n \nWBC as well as its five components are usually expressed as the total \nnumber of cells in a cubic centimeter of blood (cc) or cubic millimeter \n(cu mm or mm-3)or milliliters (mL). \n \nWBC usually falls with a range between 4000 and 11,000 but fluctuates for \nwere transmitted. This report has been updated to show the date of the \na number of medical reasons. For brevity, WBC results may be divided by \n1000 and presented as K/cc or K/cu mm or K/mm-3 or K/mL\n \n \nThe five components are similarly expressed as number of the same type OR \nas a percentage of the total WBC. \n \nThe sum of counts of the five components of should equal the total WBC OR \nthe sum of the percentages of the five components should equal 100%\n \nmost recent WBC (White Blood Count) and Neutrophil Count along with the \nThis test is sometimes also referred to as "Leukocyte Count" \n \n \nAbsolute Neutrophil Count (ANC)\n \nThe Absolute Neutrophil Count is the total number of Neutrophil cells in \nthe total WBC count. The other GRANULOCYTE cells - Basophils and \nEosinophils (see White Blood Cell Count above) - are not included in this \nnumber. Therefore - a test titled GRANULOCYTES - may not produce the \ndesired result as it may include Basophils and Eosinophils.\ndate of the most recent Clozapine prescription. Mental Health and \n \nSince the ANC is a portion of the WBC, it is only valid if it is \ntraceable to the WBC sample drawn at the same date and time. \n \nANC is a count and not a percentage - expressed as WBC with the total \nnumber of cells in a cubic centimeter of blood (cc) or cubic millimeter \n(cu mm or mm-3)or milliliters (mL). Again, this number may be divided by \na thousand for brevity. \n \nThe Absolute Neutrophil Count generally ranges from 1600 to 7700 / but it \nPharmacy personnel responsible for prescribing and dispensing Clozapine \ncan ever exceed the WBC count. \n \nThis test can also be knows as polymorphonuclear cells or PMN's. \n \n \nNeutrophil Percent (Neut%)\n \nThe Neutrophil Percent is the portion of the total WBC and that is \ncomposed of Neutrophil cells, excluding all agranulocytes and other \ngranulocytes. This number is usually between 40% and 70%, but fluctuates \nshould be made aware of this mail group and given the opportunity to join.\nfor many medical reasons. \n \nSince it is reported as a portion of the total WBC, it is only valid if \nit is traceable to the WBC sample drawn at the same date and time. \n \nNeut% is commonly obtained by automatic testing equipment to represent \nthe Neutrophil content in the blood. \n \nNeut% is a percentage and not a count - reported in the portion of the \nWBC. It can be converted into an Absolute Neutrophil Count in the \nRoll Up software. Originally, all Clozapine prescriptions were limited \n \nfollowing formula (Neutrophil% / 100) X WBC count). \n \nThe Neutrophil Percent generally ranges from 37% to 80% and should never \nexceed 90% of the total WBC count unless special medical conditions are \npresent. \n \n \nSEGS & BANDS \n \nThe WBC/Granulocyte/Neutrophil cell type can be further subdivided into \nNEW OPTION:\ntwo types. Mature neutrophils are called SEGS. Immature neutrophils \ncalled BANDS also circulate in the blood until they mature into SEGS. \nThe sum of SEGS and BANDS is equal to the ANC of a give WBC count. \n \nSEGS and BANDS may be reported as a count, expressed in cc, mm-3, cu mm, \nor mL. A preceding K indicates the number has been divided by 1000. \n \nWhen SEGS and BANDS are reported as a number, the sum total of SEGS and \nBANDS equals the total Neutrophil Count (ANC) NOTE that the program \nneeds an identifying test for both SEGS and BANDS. Reporting SEGS \n==========\nwithout a parallel result from BANDS will result in an error condition \nthat may prevent Pharmacy dispense. \n \nThis number generally ranges between 1600 and 7700 / cu mm. It should \nnever exceed 90% of the total WBC except under special circumstances. \n \nSEGS and BANDS may be reported as a PERCENTAGE of the total WBC. \nTherefore the total number of neutrophils (ANC) in a give WBC is = total \nWBC X (% Segs + % Bands). This calculation will be performed by the \nPharmacy patch to obtain and ANC when necessary\nThe Link Multiple Tests to Clozapine [CLOZAPINE MULTI TEST LINK] option \n \nThe sum total of SEGS% and BANDS% can never exceed 100.\n \nDATA DICTIONARY:\n===============\nCLOZAPINE PATIENT LIST File (#603.01), OVERRIDE DATE field (#3) - This \nfield was added to allow the NCCC more control over the overrides \nperformed at the site.\n \nCLOZAPINE PARAMETERS File (#603.03), LOCK DOWN field (#7) - This field \nmust be assigned to the person or persons responsible for ensuring that \nwas added to allow the NCCC to prevent the dispensing of any Clozapine \nprescription at a site.\n \n \nCLOZAPINE TESTS file (#603.04) - This file was added to allow the sites \nto select multiple tests for the WBC and Neutrophil count.\n \nField Field Name Description\n603.04,.01 NAME 0;1 FREE TEXT (Required)\n603.04,1 TEST NAME 1;0 POINTER Multiple #603.41\nthe appropriate data is in place to validate Clozapine testing data. \n603.41,.01 TEST NAME 0;1 POINTER TO LABORATORY TEST FILE (#60)\n603.41,1 TEST TYPE 0;2 SET (Required)\n \n 'W' FOR WHITE BLOOD COUNT; \n 'A' FOR ABSOLUTE NEUTROPHIL COUNT; \n 'N' FOR NEUTROPHIL PERCENT; \n 'S' FOR SEGS %; \n 'B' FOR BANDS %; \n 'T' FOR BANDS ABSOLUTE; \n 'C' FOR SEGS ABSOLUTE; \nThis is usually the Laboratory ADPAC.\n603.41,2 REPORTING FORMAT 0;3 SET (Required)\n \n '0' FOR Units; \n '1' FOR K/units; \n '2' FOR Percentage; \n \nINSTALLATION TIME FRAME:\n=======================\nVA DIRECTIVE 2001-023 REQUIRES INSTALLATION OF THIS PATCH WITHIN 30 DAYS \nFROM THE TIME OF INITIAL RELEASE.\n \n \nREQUESTING SITE:\n===============\nNational Clozapine Coordinating Center\n \nTest Site(s):\n============\nWest LA\nOklahoma\nLouisville\nThis option will ask for the local laboratory name that equates to the \n \nReference NOIS:\n==============\nNA\na\nASSOCIATED E3Rs:\n===============\nNA\n \nASSOCIATED REMEDY TICKETS:\nfollowing seven common test names\n=========================\nNA\n \n ROUTINE SUMMARY:\n ================\n \n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.01;MENTAL HEALTH;**[patch list]**;Dec 30,1994\n \nto 7 days. Renewals and refills were not allowed. In addition, the \n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \n YSCLSERV 25083145 25564583 18,22,26,47,\n 61,69,74,90\n YSCLSRV1 1605367 1606233 61,69,74,90\n YSCLSRV2 16840829 24723007 69,90\n YSCLSRV3 7345805 24872037 74,90\nWhite Blood Cell Count\n YSCLTEST 12047382 12378003 18,22,26,47,\n 61,69,74,90\n YSCLTST1 15450428 11839450 18,22,25,26,\n 47,61,69,74,90\n YSCLTST2 11178871 32098862 18,22,26,47\n 61,69,74,90\n YSCLTST3 15031797 25645207 18,22,25,26\n 47,61,69,74,90\n \n \nAbsolute Neutrophil Count\nList of preceding patches: 18,22,25,26,47,61,69,74\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no existing user options are affected.\n \n The site should answer "NO" to all three questions.\nNeutrophil %\n Note: You may not receive all three prompts at your site.\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n \n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n \n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols?\n YES// NO"\nSegs (Percent)\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n \n 2. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the\nBands (Percent)\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 3. Users may remain on the system, installation may be done at\n any time except during the time scheduled for the Clozapine\n roll-up.\n \nSegs (Absolute Count)\n 4. No options need to be placed out of service.\n \n 5. Installation time is less than 2 minutes during off peak\n hours and less than 5 minutes during peak hours.\n \n 6. Installation of this patch requires no additional memory\n space.\n \n 7. From the 'Installation Menu' of the KIDS menu, run the\n option:\nBands (Absolute Count)\n 'Install Package(s)' Select the package 'YS*5.01*90 and\n proceed with the install.\n \nYou will also be asked to fill in the reporting format for each test. \nClozapine reporting software automatically discontinued any patient if \nMost sites report WBC and Neutrophil results in K/unit format (K/cc or \nK/cu mm or K/mm-3 or K/mL). For example, WBC equals 5.1. However, some \nreport results as discrete units. For example, WBC equals 5100. This \nfield will allow the site to specify how results are reported. Entries \nthat report in a percentage (such as Neutrophil %, Segs %, and Bands %) \nshould use "Percentage".\n \nYou may input as many names from the local laboratory definition for each \nof these tests as needed. Remember that the laboratory may have designed \nspecial names for specific test equipment, specific test locations, or \nthe patient's prescription was over 28 days old. This was to prevent a \nspecific test conditions, such as manual counts. \n \nIn fact, if your facility has Clozapine patients with blood samples drawn \nand tested on a fee-basis at other CLIA (Clinical Laboratory Improvement \nAmendments) approved labs, it is extremely important for your Laboratory \nhave tests to accept manual input of these tests. \n \nTherefore, you should involve laboratory managers or ADPAC (Automated \nData Processing Application Coordinator) in selection of these names - \nboth to define the test names currently in use and to create the \npatient from being issued medication on an expired prescription. The \nprovision for manual entry of data. Please be certain every possible \nlocal laboratory name that represents these tests is entered that relates \nto each of the seven test names above. Pharmacy dispense will be \nprevented unless the program can find the needed test results under one \nof names you identify as an equivalent for each of the seven tests.\n \nSecurity Key: The YSCL AUTHORIZED Security Key is new with this patch. \n This key must be assigned to each provider authorized to dispense \n Clozapine.\n \nrevised Clozapine protocol allows for a monthly prescription as well as \nEXAMPLE: CLOZAPINE MULTI TEST LINK [Link Multiple Tests to Clozapine] \noption\n \nSelect OPTION NAME: CLOZ\n 1 CLOZAPINE MULTI TEST LINK Link Multiple Tests to Clozapine\n 2 CLOZAPINE DATA SERVER YSCLSERVER Clozapine Data Server\n 3 CLOZAPINE PHARMACY MANAGER PSOL MANAGER Clozapine Pharmacy \nManager\n 4 CLOZAPINE TEST LINK YSCL TEST LINK Clozapine Test Link\nCHOOSE 1-4: 1 CLOZAPINE MULTI TEST LINK Link Multiple Tests to \nweekly and bi-weekly. The patient is now automatically discontinued if \nClozapine \nLink Multiple Tests to Clozapine\nCurrently linked Tests:\nNEUTROPHIL MATURITY, MEAN represents WHITE BLOOD COUNT\nSEGS represents BANDS %\n \nEnter the name of the test for Clozapine: WBC WBC\nEnter the type of the test for Clozapine: ?\n \nEnter a code from the list.\nthe issue date for the most recent prescription is greater than 56 days \n \n Select one of the following:\n \n W WHITE BLOOD COUNT\n A ABSOLUTE NEUTROPHIL COUNT\n N NEUTROPHIL PERCENT\n S SEGS %\n B BANDS %\n T BANDS ABSOLUTE\n C SEGS ABSOLUTE\n\n
\nThis patch fixes the problem with undefined errors occurring when\ndisplaying incomplete Seclusion/Restraint (S/R) record\nInformation via YSSR ENTRY and YSSR RELEASE options and removes \nleftover nodes from a previous restructuring of file 604.\nIt also corrects a problem whereby GAF scores are not always\nseen in the Encounter dialogue of CPRS.\n\n
\n \nFurther, the integration should make appropriate Mental Health assessment \n target populations, normative samples and copyright information. Actions\n available including privileging, reporting of full item content and\n transmission to the Mental Health National Database are also specified. \n \n Entries may be made through the provided Mental Health Authoring software. \n Direct entry through Fileman or the programmer prompt is prohibited.\n \n MH QUESTIONS file (#601.72)\n ---------------------------\n This file contains a listing of all questions for all Psychological \ntools available to clinicians outside Mental Health (e.g., depression and \n Interviews, Surveys and Tests. This allows usage of questions by multiple \n instruments. Each question can also linked to an entry in the MH \n INTRODUCTIONS file (#601.73), the MH CHOICES file (#601.75), the MH \n CHOICETYPES file (#601.751) and the Hint field (#8) in the MH QUESTIONS \n file (#601.72). \n \n MH INTRODUCTIONS file (#601.73)\n -------------------------------\n This file contains the introductory information given at the beginning of \n each instrument or at the beginning of a new section of an instrument. The \nalcohol screening instruments should be made available to primary care \n introduction text motivates, gives instructions and sets the frame for the \n task the patient must complete. The same introduction text can be used by \n multiple instruments.\n \n MH RESPONSE TYPES file (#601.74)\n --------------------------------\n This file contains what type of response from the user is required for a \n question. Response types contained in the file include MCHOICE (multiple \n choice), Integers, Strings, Dates, Memos and Currency. These entries are \n pointed to the MH QUESTIONS file (#601.72).\nclinicians)."\n \n MH CHOICES file (#601.75)\n -------------------------\n This file contains the individual selections possible in a multiple choice \n question. Examples are Yes or No, True or False, 1. Abraham Lincoln, 2.\n George Washington, 3. George W. Bush or 4. Richard Nixon. For instruments \n first defined in the legacy system MH INSTRUMENT file (#601), a single \n character is specified for a multiple choice answer. If George Washington \n was the choice selected the legacy value would be 2. \n \n \n Choices are pointed to by the MH CHOICETYPES file (#601.751) which is a \n collection of choices. Choices are referenced in the MH ANSWERS file \n (#601.85) as a pointer to the full response.\n \n MH CHOICETYPES file (#601.751)\n ------------------------------\n This file contains a collection of choices from MH CHOICES file (#601.75) \n and their display sequence. This allows sets of choices to be specified by \n the MH QUESTIONS file (#601.72). An example of an entry would be: 1. True \n 2. False 3. Undecided Each multiple choice question must specify a \nThis revision of MHA creates a closer integration with CPRS, by placing the MHA\n ChoiceType. In this way a ChoiceType can be used by multiple instruments \n and multiple questions.\n \n MH INSTRUMENT CONTENT file (#601.76)\n ------------------------------------\n This file specifies which entries from the MH QUESTIONS file (#601.72) are \n parts of which instrument in the MH TESTS AND SURVEYS file (#601.71). It is \n the "table of contents" for an interview, survey or test. Also specified are \n the sequence of questions and display attributes for the introductions, \n questions and choices. Display attributes can be bold, underlined and font\nGUI on the CPRS Tools Menu. Additionally, functionality was created to allow \n size for the introductions, questions and choices.\n \n MH BATTERIES file (#601.77)\n ---------------------------\n This file contains a list of interview, survey and test order sets.\n \n MH BATTERY CONTENTS file (#601.78)\n ----------------------------------\n Ties the entries in the MH BATTERY CONTENTS file (#601.78) to the \n instruments in the MH TESTS AND SURVEYS file (#601.71). \na site to place an individual instrument on the Tools menu, allowing widespread\n \n MH BATTERY USERS file (#601.781)\n --------------------------------\n This file contains a list of all interviews, surveys and tests associated \n with an entry in the MH BATTERIES file (#601.77). The order of presentation \n of the interviews, surveys and tests within a battery and which battery \n belongs to which user in the NEW PERSON file (#200) is also specified.\n \n MH SKIPPED QUESTIONS file (#601.79)\n -----------------------------------\naccess to that specific instrument without having to issue the menu for the MHP\n This file specifies the questions to be skipped (by question IEN) if a rule \n is met for a given question in a given instrument.\n \n MH SECTIONS file (#601.81)\n --------------------------\n This file specifies sections within an interview, survey and test. The first \n MH QUESTIONS file (#601.72) is specified along with captions (tab and \n overall). Display characteristics can also be set.\n \n MH RULES file (#601.82)\nto all clinicians.\n -----------------------\n This file contains the rules used in administering an interview, survey or \n test. A rule is an action that is performed when a specified question is \n answered in a specified manner. An example of a rule would be to enter 'Not\n applicable' to the Question, "Are you pregnant?" if the patient has had a\n hysterectomy. Rules are complex logic based entries that enables the user to\n create complex scripts.\n \n MH INSTRUMENTRULES file (#601.83)\n ---------------------------------\nThe Veterans Health Administration (VHA) Action Agenda for implementing the \n \n This file ties together an instrument in the MH TESTS AND SURVEYS file \n (#601.71), a question in the MH QUESTIONS file (#601.72) and a rule in the \n MH RULES file (#601.82). This allows a rule to be used in multiple \n instruments and for different questions.\n \n MH ADMINISTRATIONS file (#601.84)\n ---------------------------------\n The MH ADMINISTRATIONS file (#601.84) contains the data collected during \n the administration of a specified instrument from the MH TESTS AND SURVEYS \n file (#601.71) given to a patient at a specific date and time. For each \nAdditional functionality that strengthens the tie to the patient's medical \n administration of a specified instrument from the MH TESTS AND SURVEYS file \n (#601.71) there will be an entry in this file. \n \n An entry in this file does not store the results of the instrument's \n administration but is an index to the instrument's administration. The entry \n indicates whether the instrument has been completed, who ordered the \n instrument, how many questions were answered and if the test has been \n electronically signed.\n \n MH ANSWERS file (#601.85)\nrecord is the creation of a progress note in CPRS when an instrument is \n -------------------------\n When a patient answers a question, the results are stored in this file. An \n entry for each question answered, in each administration is stored. Each \n entry has an MH ADMINISTRATON ID field(#.01) of the MH ADMINISTRATION file \n (#601.84), a Question NUMBER field (#.01) of the MH QUESTIONS file (601.72) \n and the response.\n \n MH SCALEGROUPS file (#601.86)\n -----------------------------\n ScaleGroups are collections of MH SCALES file (#601.87) that are logically \ncompleted through MHA.\n displayed together. Information needed to graph the scales are stored here.\n This includes the ordinate title, minimum and maximum values, graph \n increments and grid lines. \n \n All scales need to be associated with a MH SCALEGROUP to be displayed. MH \n SCALEGROUPS file (#601.86) and MH SCALES file (#601.87) allow multiple \n scoring possibilities within a single instrument.\n \n MH SCALES file (#601.87)\n ------------------------\n \n A MH SCALE is one dimension of measurement in an instrument. An example may \n simply be a TOTAL as in a spelling test or multiple scales in a personality \n disorder instrument (depression, anxiety, thought disorder etc.). Each scale \n has at least one associated entry in the MH SCALEGROUP file (#601.86) and an \n entry in the MH SCORING KEYS file (#601.91).\n \n MH DISPLAY file (#601.88)\n -------------------------\n This file contains the entries to set the Windows display attributes for \n the MH QUESTIONS file (#601.72), MH INTRODUCTIONS file (#601.73) and the \nFurthermore, MHA maintains and strengthens its ties to the Clinical Reminders \n MH RESPONSE TYPES file (#601.74). Windows display attributes include fonts, \n bolding, underline, colors and columns.\n \n MH CHOICEIDENTIFIERS file (#601.89)\n -----------------------------------\n This file specifies the displayed numeric options that go along with a \n multiple choice item. Choice type identifiers can be numbered starting from \n one, from zero or remain unnumbered.\n \n MH SCORING KEYS file (#601.91)\nprogram, which allows for the presentation of specific instruments through \n ------------------------------\n This file contains the scoring keys. The scoring keys are the "answer \n sheet" for the specified scale entry in the MH SCALES file (#601.87). When \n an answer the matches the Target value (ie, is correct) a specified value is \n added to the score. An example would be: if the question is "How much is 5 \n plus 3", the target value would be 8 and 10 points would be added to the \n total score (grade) in a ten question test to make a possible score of 1\n \n MH RESULTS file(#601.92)\n ______________________________\nreminder dialogs to all clinicians who resolve reminders.\n This file contains results of the scored output of completed\n instruments.\n \n MH REPORT file (#601.93)\n ------------------------------\n This file contains the reporting format for a specified instrument. Input\n into this file must be entered only through the Mental Health Editor software.\n \n \n E3R#: None \n \n \n Associated NOIS: HD68109/BAC-0704-40498 ASI e-sign while editing \n HD68006/CLE-0504-40649 Interviewer cannot sign ASI in \n GUI \n HD67955/COA-0404-20702 Cannot sign ASI using MHA \n HD67709/BHS-0304-10794 Error - Null subscript at \n QTEP+6^YSASNAR \n HD67885/MAC-0204-61794 Mental Health Assistant - \n can't get to old tests \n HD67881/COA-0204-21407 MHA freezes during cross checks \nClinical reminders has also developed a new patch, PXRM*2.0*6 that allows \n HD67870/TNV-0204-30263 Co-signer ignored within ASI \n HD67841/OKL-0104-71087 MH Assistant accessible w/o keys \n \n Test Site(s): \nUpstate New York HCS, NY\nVA Pacific Island HCS, HI\nNorthern California HCS, CA\nPuget Sound HSC, WA\nAtlanta VAMC, GA\n \nPresident's New Freedom Commission on Mental Health recommendations regarding \nreminders to work with the new MHA file structure. YS*5.01*85 should be \nRoutine Summary\nChecksums shown are NEW Checksums\nThe following routines are included in this patch. The second line of \neach\nof these routines now looks like:\n ;;5.01;MENTAL HEALTH;**[Patch List]**;Dec 30, 1994\n \n Checksums\nRoutine Old New Patch List\nYS85POST 2059692 2059560 **85**\ninstalled just before PXRM*2*6. If YS*5.01*85 is installed without \nYS85PRE 813879 813879 **85**\nYTAPI5 n/a 12417658 **62,85**\nYTAUIRR n/a 14880327 **37,85**\nYTDOMR n/a 26438095 **31,85**\nYTKIL n/a 8970368 **37,85**\nYTPCL n/a 7363737 **66,85**\nYTQAPI 15475641 15475641 **85**\nYTQAPI1 27189337 27189337 **85**\nYTQAPI10 24613112 24613112 **85**\nYTQAPI11 22157825 22157825 **85**\nPXRM*2*6, reminders will not be able to recognize MHA instruments \nYTQAPI12 20141561 20141561 **85**\nYTQAPI13 19997427 19997427 **85**\nYTQAPI14 6830812 6830812 **85**\nYTQAPI15 25671527 25671527 **85**\nYTQAPI16 13185422 13185422 **85**\nYTQAPI2 21244483 21244483 **85**\nYTQAPI3 23768089 23768089 **85**\nYTQAPI4 28692651 28692651 **85**\nYTQAPI5 23263110 23263110 **85**\nYTQAPI6 5268725 5268725 **85**\nadministered after the file structure changes with YS*5.01*85.\nYTQAPI7 18902958 18902958 **85**\nYTQAPI8 32413314 32771511 **85**\nYTQAPI9 22741073 22741073 **85**\nYTQHL7 31149138 31149138 **85**\nYTQKIL n/a 5269849 **85**\nYTQLIB 8410129 8410129 **85**\nYTQPRT 25124936 25124936 **85**\nYTQPXRM 4498627 4498627 **85**\nYTQPXRM1 12743110 12743110 **85**\nYTQPXRM2 14658221 14658221 **85**\n \nYTQPXRM3 16585590 16585590 **85**\nYTQPXRM4 21974840 21974840 **85**\nYTQPXRM5 19969917 19969917 **85**\nYTQPXRM6 16689405 17034666 **85**\nYTQPXRM7 21919160 21919160 **85**\nYTQQI001 16371213 16371213 **85**\nYTQQI002 110963388 110963388 **85**\nYTQQI003 107420027 107420027 **85**\nYTQQI004 105189787 105189787 **85**\nYTQQI005 104556455 104556455 **85**\nAdditionally, the files of the MHP have been restructured to initiate the \nYTQQI006 104012683 104012683 **85**\nYTQQI007 103468973 103468973 **85**\nYTQQI008 100582283 100582283 **85**\nYTQQI009 99865202 99888363 **85**\nYTQQI00A 99888363 99132958 **85**\nYTQQI00B 101279645 101279645 **85**\nYTQQI00C 102188832 102188832 **85**\nYTQQI00D 98549063 98549063 **85**\nYTQQI00E 96890307 96890307 **85**\nYTQQI00F 97231174 97231174 **85**\nmigration toward re-engineering and placing MHA as a component of HealtheVet \nYTQQI00G 96151494 96151494 **85**\nYTQQI00H 96468871 96468871 **85**\nYTQQI00I 100432284 100432284 **85**\nYTQQI00J 95575288 95575288 **85**\nYTQQI00K 25448044 25448044 **85**\nYTQTIU 11026585 11026585 **85**\n \nList of preceding patches: 31, 37, 62, 66\nSites should use CHECK1^XTSUMBLD to verify checksums.\n \nDesktop when it is implemented.\n SOFTWARE RETRIEVAL:\n ===================\n \n The following software and documentation files are exported as part\n of this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n YS_501_85.KID MHA Server Components ASCII\n \n \n YS50185_SETUP_1_0_3_1.exe Mental Health Assistant BINARY\n This file is the complete \n install for the Mental Health\n Assistant GUI Version 1.0.3.1, client.\n \n - YS_MHA.exe MHA 3 Executable\n - YS_MHA_SD_INSTALLGINA.exe Activate Secure Desktop Executable\n - dwlGina2.dll DLL used by Secure Desktop\n - YS_MHA_SD_UNINSTALLGINA.exe Deactivate Secure Desktop Executable\n - YS_MHA_VASD.exe Secure Desktop's main executable\nTo better meet the needs of clinicians and patients in different programs, \n - YS_MHA.HLP Online help file for the ASI\n - ANSWER file folder Offline records that have not been uploaded\n - INSTRUMENT file folder MH Instruments for Offline administration\n \n YS50185_MHA 3_IG.PDF YS_MHA 3 Installation Guide BINARY\n YS50185_MHA 3_IG.DOC YS_MHA 3 Installation Guide BINARY\n \n YS50185_MHA 3_UM.PDF YS_MHA 3 User Manual BINARY\n YS50185_MHA 3_UM.DOC YS_MHA 3 User Manual BINARY\n \nthe use of information technology to enhance the care of Mental Health patients\nparticularly non-traditional settings, MHA can now run in a standalone mode to\n The software files are available on the following OI Field Offices'\n ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these\n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\nadminister instruments offline for later uploading to VistA.\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \n Installation Instructions:\n ==========================\n 1. Use the 'LOAD A DISTRIBUTION' option on the PackMan menu. The\n Host File name is YS_501_85.KID. Answer YES to the question:\n "Want to Continue with Load? YES//"\n \n \n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\nVistA Mental Health Assistant NEW features in MHA3:\n Backup a Transport Global\n \n \n 3. Users may remain on the system, but installation should be done \n at off peak hours. During testing, it was noted that if a user had \n a reminder dialog open when the install took place, the reminder\n dialog would not load and work properly until CPRS was rebooted.\n \n 4. Installation will take less than five minutes. \n \n---------------------------------------------------\n 5. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*85'\n and proceed with install.\n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install//', respond NO.\n When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? YES//', respond NO\n \n 7. Place the MENTAL HEALTH ASSISTANT VERSION 3 USER MANUAL in a\n1. M: Completely re-organized VistA Mental Health database files to \n location that can be accessed by MHA users.\n \n 8. Please refer to the POST INSTALLATION INSTRUCTIONS section of the \n MENTAL HEALTH ASSISTANT VERSION 3 INSTALLATION GUIDE to install\n the MHA software.\n 9. The Secure Desktop feature in the MHA software is a security \n feature that locks down computers when patients are completing \n assessments directly in MHA. Because it locks down all other \n applications on the computer when activated, it must be loaded\n directly on the PC where it will be used. It should only be loaded\n simplify migration to HDR. \n on machines that will be used for patient administered\n assessments. It should not be pushed out to all machines on the\n network. More detailed information is found in the MHA VERSION 3\n INSTALLATION GUIDE.\n \n 10. Place the option YS BROKER1 [YS BROKER1] on the Mental Health \n users secondary menu.\n \n 11. Enter appropriate members into the Mail Group YS MHA-MHNDB to\n the system, but installation should be done at off peak hours.\n \n \n 12. Place the MHA application on the CPRS Tools menu.\n \n 13. Create progress note title of "Mental Health Diagnostic Study \n Note" in the progress note hierarchy. This is needed for MHA to \n automatically pass a note to CPRS from instrument administrations \n completed within MHA.\n \n 14. A new entry is created in File 771, the HL7 Application Parameter\n File: YS MHA. It is exported as Inactive and should be set to\n2. GUI: MHA3 must be invoked from the CPRS Tools menu, for interaction with \n Active after install.\n \n 15. A new entry is also created in File 870, the HL Logical Link file.\n This entry is YS MHAT. The logical link named YS MHAT is used by\n the HL7 package to send VistA ADT HL7 messages containing patient\n demographics, patient administration and patient answers.\n secondary menu. \n VistA and patient selection. Patient-selection is done entirely by\nstates, "VHA should make the integration of MHA and HealtheVet Desktop (HeVD) \n interaction with CPRS. \n \n3. GUI: MHA3 can run in standalone mode, but only for administering offline \n tests-which later must be uploaded to VistA.\n \n4. GUI: MHA3 allows the CPRS Tools menu to invoke any number of single types \n of instruments, without the need to go directly to the MHA3 Main form. For \n instance, a CAGE menu item can be added to the Tools menu, which would \n invoke only a CAGE data entry form. \n \nan explicit goal and should provide the OI with sufficient resources to \n5. GUI: Major functionality (GAF, ASI, Results, etc.) is now presented on \n individual forms, as opposed to as tabs on one main form. \n \n6. GUI: MHA3 now provides a new Battery Wizard form to simplify creating \n batteries of instruments.\n \n7. There is a new & improved SecureDesktop component that now uses stronger \n code to prevent hacking. \n \n8. "Clerk entry" data-entry-mode form for psych tests has been removed. \naccomplish this goal in collaboration with the Mental Health Strategic \n \n9. All completed administrations now automatically generate a progress note \n for review in CPRS.\n \n10. All test scores are now saved in VistA, instead of calculated on-the-fly. \n \n11. There is now a hospital Location associated with an administered \n instrument, for progress notes purposes. \n \n12. The accompanying MHA3 help file is supplied only for describing the \nHealthcare Group (MHSHG) Informatics Section. The integration should \n functions of the ASI Manager forms. All other tests and interview have \n built-in help that is retrieved directly from the MHP when using the \n "Description" pop-up menu function in the Instrument Manager. \n \n13. MHA3 now recreates a debug log file named "mha3_debug.log" for each MHA3 \n session. This file can be emailed to developers to assist in remote \n debugging. No patient-identifying data is collected in this file. \n \n \nThis patch contains 23 new Mental Health files, 58 new Mental Health\neliminate the need for Mental Health clinicians to change applications. \nRemote Procedures, 57 new Mental Health routines, 1 option, 2 Protocols, \n1 HL7 application parameter and 1 HL logical link.\n \n \n 23 New Mental Health files to be released in this patch:\n --------------------------------------------------------\n MH TESTS AND SURVEYS file (#601.71)\n -----------------------------------\n This file defines the interviews, surveys and tests available in the Mental\n Health Assistant. Attributes of the instruments include authoring credits,\n\n
\nThis patch is intended to stop HL7 message generation. With the release \nof YS*5.01*85, HL7 errors are occurring because it was the intent of the \ndevelopment team to release that patch with messaging turned off. \nUnfortunately, this was not the case.\n\n
\nA problem was found with one of the Clozapine API's during the testing of \n % Neutrophil\n \n \nASSOCIATED TEST SITES:\n======================\nAlexandria, VA\nCharleston, WV\nCleveland, OH\nHudson Valley HCS\nLoma Linda, CA\nComputerized Patient Record System (CPRS V27) patch OR*3*243. The\nPalo Alto HCS\nPhiladelphia, PA\nSan Diego, CA\nPuget Sound HCS\nTampa, FL\n \n \nREMEDY TICKET OVERIVEW:\n=======================\n \nroutines in this patch have been modified to correctly handle the\n Problem:\n --------\n A problem was found with one of the Clozapine API's during the testing \n of Computerized Patient Record System (CPRS V27) patch OR*3*243.\n \n Solution:\n --------- \n Modified routines to correctly handle the situation.\n \n Routines:\nsituation.\n ---------\n YSCLSERV, YSCLSRV2,YSCLSRV3, YSCLTST2, YSCLTST4 (new)\n \n \nINSTALLATION INSTRUCTIONS:\n==========================\nThe install time for this patch is less than 2 minutes. This patch can be\ninstalled with users on the system. Installation may be done at any time\nexcept during the time scheduled for the Clozapine roll-up.\n \n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this \nASSOCIATED REMEDY TICKET:\n patch prior to installation, you should use the 'Backup a Transport\n Global' option at this time. You may also compare the routines in\n your production account to the routines in the patch by using the\n 'Compare a Transport Global to Current System' option.\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'YS*5.01*92'.\n \n If prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//,\n choose 'NO'.\n=========================\n \n If prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', choose 'NO'.\nHD195784 - Clozapine--Incorrect Value for OC calculation for ANC from\n\n
\n When multiple instruments are administered for the same encounter through\n CPRS GUI Clinical Reminders, only the results of the last instrument \n display in the Mental Health Assistant 3 GUI. This patch will correct \n this defect.\n\n
\nThis patch removes some cross-references to field .53 (Progress\nNote Pointer) of file # 604 (Addiction Severity Index) that remained\nafter the elimination of field .53 due to file restructuring. A post-init\nroutine (YS501P99) is used to remove these cross-references. This patch\nalso replaces the term MHA3 in some prompts with the phrase \n"MH administration/test".\n\n
\nThis patch corrects a defect in the Mental Health Assistant, Dynamic-Link\nnot aware of this new storage arrangement while using CPRS and the MHA DLL.\n2. The patch has now been loaded into a Transport global on your\n system. You now need to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n \n3. Users may remain on the system, but installation should be done\n at off peak hours.\n \n4. Installation will take less than five minutes.\n \n5. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'YS*5.01*98'\n and proceed with install.\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the\nThere are no changes to existing files and no changes from the user's \n install//', respond NO.\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond NO\n \n8. Download YS_501_98_Setup.exe in binary mode and run the YS_501_98_Setup.\n exe file to install Clinical Reminders MHA DLL. Please install the DLL\n in the default folders. The install program requires two dialogs of the\n user (to start and to signify finished). To avoid the user/install\n interaction, the file YS_MHA_A.dll can be copied directly to the\nperspective.\n C:\\Programs Files\\Vista\\Common Files directory. This may be the more\n desirable way to push the dll to many workstations.\n \n \nThis patch contains three new Remote Procedure Calls (RPCs):\n \n 1) YTQ GET SCRATCH: Returns data from the scratch file for the MHA DLL.\n Input: DFN, test CODE and GIU HANDLE.\n \nLibrary, (MHA DLL). The MHA DLL is called from Computerized Patient Records\n 2) YTQ KILL SCRATCH: Delete entries from the scratch file when a clinical\n reminder is saved. Input: DFN, test CODE and GIU HANDLE.\n \n 3) YTQ SET SCRATCH: API is designed to set data to a scratch file for the\n MHA DLL. Input: DFN, test CODE and GIU HANDLE.\n \nThis patch introduces a new file called, MH CR SCRATCH FILE (#601.94). This\nfile is used as temporary storage space for the interface between the MHA \nDLL and Clinical Reminders.\n \nSystem (CPRS) version 27N when a Clinical Reminder note is filled in by the\nA new routine, YTQPXRM8, is also included.\n \nAssociated Remedy Tickets:\n=============================\n \nHD0000000233026, HD0000000240965, HD0000000232542, HD0000000247135,\nHD0000000240965, HD0000000232427, and HD0000000233367.\nClinical reminders: Completed mental health instruments are incorrectly\nidentified as having missing answers.\n \nuser.\nAssociated E3R:\n===============\nN/A\n \nTest Site List:\n===============\nLoma Linda, CA - Large\nPalo Alto, CA - Integrated, Large\nPhiladelphia, PA - Large\n \n \nThis is a sub set of sites used by CPRS GUI v27.n (OR*3*296) and were\ndetermined by that team. (The CPRS test sites do not include any medium or\nsmall sites.)\n \nRoutine Summary:\n================\nChecksums shown are NEW Checksums\n \nThe following routine is included in this patch. The second line \nof this routine now looks like:\nThe essential problem concerned the use a temporary file on the user's hard\n ;;5.01;MENTAL HEALTH;**[Patch List]**;Dec 30, 1994\n \n Checksums\nRoutine Old New Patch List\nYTQPXRM8 n/a 15837966 **98**\n \nSites should use CHECK1^XTSUMBLD to verify checksums. \n \nSOFTWARE RETRIEVAL:\n===================\ndrive to store user's responses before saving to Veterans Health Information\n \nThe following software and documentation files are exported as \npart of this patch:\n \nFile Name Contents Retrieval Format\n--------- -------- ----------------\nYS_501_98.KID MHA Clinical Reminders APIs ASCII\nYS_501_98_SETUP.EXE Installs DLL Binary\nYS_MHA_A.dll DLL support for Clinical Reminders Binary\n \nSystems and Technology Architecture (VistA). This patch provides the means\nThe software files are available on the following OI Field Offices'\nANONYMOUS.SOFTWARE directories.\n \nAll sites are encouraged to use their FTP capability to obtain these\nfiles. Use the FTP address "download.vista.domain.ext" (without the\nquotes) to connect to the first available FTP server where the files\nare located.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\nfor that temporary information to be stored in VistA instead. The user is\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \nInstallation Instructions:\n==========================\n1. Use the 'LOAD A DISTRIBUTION' option on the PackMan menu. The\n Host File name is YS_501_98.KID. Answer YES to the question:\n "Want to Continue with Load? YES//"\n \n\n
\nPlease refer to YS*5.01*97 in the National Patch Module for a description \nof this patch.\n\n
\nPlease refer to YS*5.01*96 in the National Patch Module for a description \nof this patch.\n\n
\nPlease refer to YS*5.01*103 in the National Patch Module for a description\nof this patch.\n\n
\nPlease refer to YS*5.01*106 in the National Patch Module for a description\nof this patch.\n\n
\nPatch YS*5.01*60 addresses the retirement of Mental Health Options, Files,\nData Dictionaries, patient data associated with these files, and\nassociated templates determined by the Mental Health Strategic Healthcare\nGroup to be obsolete and are no longer supported by Health Systems Design\nand Development. All the software, files, options, and templates were\ndesignated as obsolete in 2004 or earlier.\n \nA complete description of this patch can be found on Forum.\n\n
\nPlease refer to YS*5.01*105 in the National Patch Module for a description\nof this patch.\n\n
\nThis patch will address the following issues:\n1. Two of the Barthel Index MH SCORING KEYS have incorrect score values.\n2. Scoring issues with AAQ-2\n\n
\nThis patch will modify some of the prompts in the PCL-5 instrument to be \nscores in Clinical Reminders and Health Summary. A filter is added that \nFile Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at \nthe following OI Field Offices:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext \nSalt Lake City: fo-slc.domain.ext\n \nThe Install Guide is also available on the above servers. It is \navailable as .PDF format. This file should be downloaded in BINARY \nformat. \nwill prevent selection of these instruments in Clinical Reminders and \n \n File Name: Description: Protocol\n ========== ============ =========\n YS_PCL5_UPDATE.PDF PCL-5 Update Install Guide BINARY\n YS_PCL5_UPDATE.KID PCL-5 Update Host File ASCII\n \nDocumentation can also be found on the VA Software Documentation \nLibrary at: http://www4.domain.ext/vdl/\n \nInstallation:\nHealth Summary until a VistA based scoring algorithm can be deployed.\n=============\nThis patch can be loaded with users on the system. Installation will \ntake five minutes. Refer to the Install Guide, YS_PCL5_UPDATE.PDF, \nfor complete details.\n \n1. Use the "Load a Distribution" option on the KIDS installation menu. \n \n When prompted to enter a host file, type in YS_PCL5_UPDATE.KID\n \n2. On the KIDS menu under the 'INSTALLATION' menu, use the following \n \n options, as desired:\n Print Transport Global\n Compare Transport Global to Current System\n Verify checksums in Transport Global\n Backup a Transport Global\n \n3. On the KIDS menu under the 'INSTALLATION' menu, use the following \n option to install the patch:\n Install Package(s)\n When prompted for INSTALL NAME, use YS_PCL5_UPDATE\n \n \n4. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' enter NO. \n \n5. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//' enter NO.\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' enter NO. \n \nPatch Components:\n7. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \nPost-Installation Instructions:\n-------------------------------\nN/A\n-----------------\n \nFiles & Fields Associated:\n \nconsistent with the current wording of PCL-5. The PCL-5 instrument will \nFile Name (Number) Field Name (Number) New/Mod/Del\n------------------ ------------------- ---\n \nMH TESTS AND SURVEYS (#601.71) TAG FOR SCORING (#91) NEW\nMH TESTS AND SURVEYS (#601.71) ROUTINE FOR SCORING (#92) NEW\n \nForms Associated: N/A\n \nMail Groups Associated: N/A\n \nbe activated so that it is available for selection in the Mental Health \nOptions Associated: N/A\n \nProtocols Associated: N/A\n \nSecurity Keys Associated: N/A\n \nTemplates Associated: N/A\n \nNew Service Requests (NSRs):\n----------------------------\nAssistant (MHA). Also, possible scoring errors for the following \nNSR #20150509: Posttraumatic Stress Disorder (PTSD) Checklist 5 (PCL-5) \nand Mental Health Assistant Stabilization (MHAS) \n \nPatient Safety Issues (PSIs):\n-----------------------------\nPSPO 2497: Mental health instruments that use a complex scoring algorithm \ndisplay an incorrect score when used in Health Summary and Clinical \nReminders. \n \nRemedy Ticket(s) & Overview:\ninstruments have been corrected: MMCI3, MMPI-2-RF, MOCA, MOCA Alt 1, and \n----------------------------\nHD0000000391317 - Error Evaluating Clinical Reminder - local GAF reminder\nProblem: In some instances, a utility in the YTQPXRM2 routine errors out\nwhen evaluating a GAF clinical reminder because the time portion of the\ndate/time lookup value has trailing zeros.\nSolution: The patch modifies the routine to strip off the trailing zeros .\n \nHD0000000807935 - Mental Health - MH Tests (excluding ASI) \nProblem: The scoring criteria for the MCMI3 instrument changed since it \nwas first released.\nMOCA Alt 2. NEOPI is inactivated.\nSolution: The scoring criteria are updated.\n \nHD0000000922629 - Mental Health - Mental Health Assistant: scoring error \nMoCA, MoCA Alt1, and MoCA Alt2\nHD0000000938421 - Mental Health - Mental Health Assistant\nHD0000000964555 - MOCA calculation is off\nProblem: There is an error in the way three instruments, MOCA, MOCA ALT1 \nand MOCA ALT 2 are scored.\nSolution: The scoring error is fixed for all three instruments . \n \n \nHD0000000939794 - Mental Health - Mental Health Assistant\nProblem: There is a scoring error in the BAI instrument. There is a MH \nSCALES (#601.87) file entry associated with this instrument that should\nnot be.\nSolution: That entry is no longer associated with the instrument.\n \nINC000000616128 - Mental Health - Error Generating Report\nProblem: There is an error when generating a report for an administration \nthat doesn't exist.\nSolution: Quit before generating the report if an instrument \nAdditionally, the patch provides an interim solution for the problem \nadministration is not found.\n \nTest Sites:\n----------\nTBD\n \nSoftware and Documentation Retrieval Instructions:\n---------------------------------------------------- \nThis patch is being distributed as a host file. The name of the host \nfile is YS_PCL5_UPDATE.KID. This file should be downloaded in ASCII \nwhere instruments with complex scoring algorithms display inaccurate \nformat.\n \nThe preferred method is to retrieve files from:\n \n download.vista.domain.ext.\n \nThis transmits the files from the first available server. Sites may\nalso elect to retrieve files directly from a specific server.\n \nSites may retrieve the software and install guide directly using Secure\n\n
\nPATCH YS*5.01*131 ADDRESSES THE FOLLOWING:\n1. R14616270FY17 - CIWA question number 11 for headache not totaling.\n\n
\nSee the patch description for more detailed information. This build \n \nASSIST is renamed to ASSIST-WHOv3.\nINDEX OF ASL is renamed to KATZ-ADL-18pt.\n \nPHQ9 has an updated report.\nWAI-SR has corrections to scoring.\nmakes the following changes for Mental Health Assistant.\n \nThe following new tests are added: ASSIST-NIDA, BRS, CCSA-DSM5, CEMI, \nCIWA-AR-, CSI, CSI-4, CSI PARTNER VERSION, CSI-4 PARTNER VERSION, GAI,\nISI, KTAZ-ADL-6pt, PSOCQ, PSS, RLS, SMEQ, SNQ, STOP.\n \nThe following tests are retired: CIWA-AR, AUIR, CESD5, DOM80, DOMG, ERS, \nHLOC, IEQ, RLOC, SAI, SDES, SMAST, VALD, WAS.\n\n
\nSee the patch description for more detailed information. This build\nto XE8.\n \nThe following tests were retired: AUIR, CESD5, DOM80, DOMG, ERS, HLOC,\nIEQ, RLOC, SAI, SDES, SMAST, VALD, WAS.\n \nData validation was implemented for the Instrument Date of Administration \nto prevent dates more than 1 year in the past from being entered.\n \nThe PCL-5 was modified so that it can be used on the Special Results tab \nin the Instrument Results module.\nmakes the following changes for the Mental Health Assistant (MHA).\n \nSeveral deficiencies and Remedy tickets were addressed.\n \nThe Two Factor Authentication is implemented.\n \nThe Global Assessment of Functioning Manager (GAF) functionality is \nremoved.\n \nModifications were made to the Delphi code to migrate MHA from Delphi 7 \n\n
\nSee the patch description for more detailed information. This build \nmakes the following changes for Mental Health Assistant.\n\n
\nMental Health Treatment Planner\n\n
\nSee the patch description for more detailed information. This build \nMHRM\nmakes the following changes for Mental Health Assistant.\nThis patch contains 6 new instruments:\n \nBPRS-A\nPSS-3 2ND\nPCL-5 Weekly\nWEMWBS\nHSI\n\n
\nSee the patch description for more detailed information. This build \nMHA now stores scale scores for all instruments in the MH RESULTS file. \nAdditionally, should an instrument need to be rescored for any reason, \nthere has been functionality added to maintain an audit for previous \nscores.\n \nThe BSI was renamed to the BSS. Additional modifications were made\nand can be found in the patch.\n \nThe responses for Question 7 in the VR-12 were corrected.\n \nmakes the following changes for Mental Health Assistant (MHA).\nThe Progress Note was modified to remove extra linefeeds when multiple\ninstruments were administered.\n \nThe "skip" question logic in the Administer one item at a time for an\ninstrument was corrected.\n \nMHA is moving the scoring logic for instruments from the YS_MHA_AUX.dll \nto the M server side. This patch converts the following instruments \nfrom scoring in the DLL to M: AUDC, BAI, BAM-C, BAM-R, BASIS-24, BDI2, \nBHS, BSS (formerly BSI), CDR, CEMI, FAST, ISMI, MINICOG, MMPI-2-RF,\nNEOP-I-3, PC PTSD, PHQ-2, POQ, QOLI, STMS, VR-12, WHODAS 2, and WHYMPI.\n \n\n
\nSee the patch description for more detailed information. This build \nmakes changes to the Mental Health Assistant.\n\n
\nThe patch addresses one (1) issues:\n \n1. When using the SCL9R instrument in the Mental Health Assistant,\n only four (4) answer choices are offered when there should be \n five (5). \n\n
\nThis patch will rebuild the "AC" indexes in the MH RESULTS (601.92) file\nand in the MH ANSWERS (601.85) file.\n\n
\nSee the patch description for more detailed information. This build \nmakes changes to the Mental Health Assistant.\n\n
\nThis patch will add 8 new instruments.\n\n
\nThis patch will address the following issues 8 new instruments.\n\n
\nMENTAL HEALTH NCC PROJECT 5.01\n\n
\nThis patch will add 8 new instruments.\n\n
\nThis patch addresses issues with the Addiction Severity Index software.\n\n
\nThis patch updates the following Mental Health instruments:\n T-Score now calculates correctly for the EID scale.\n Score for PSYC-r is now correct when question 216 is true.\n \nQOLI\n A scoring error introduced by YS*5.01*139 has been corrected.\n \nIf an instrument with many scales preceded and instrument with a few \nscales during a session, some additional scales were carried over to the \ninstrument with fewer scales. This was visible in the Health Summary\ncomponent and TIU objects. It also sometimes affected the display in the\n \nSpecial Reports Wizard. This is corrected with this patch. Additionally,\nthe patch checks previous administrations to make sure each administration\nhas only the correct scales associated.\n \nAdditional record locks were added to reduce the likelihood of errors when\ngenerating a report for a legacy instrument.\nAIMS\n The disclaimer is no longer added to the progress note text.\n \nC-SSRS\n A Key Indicator is now added if Question 3 response is 'Yes'.\n \nMMPI-2-RF\n\n
\nAdd assignment capablity to MHA and calls for MHA Web app that allows \npatient entry.\n\n
\nThis patch will address the following issues 11 new instruments:\nSHORT INVENTORY OF PROBLEMS - AD (SIP-AD-30)\nSHORT INVENTORY OF PROBLEMS - AD (SIP-AD-Start)\nShort Warwick-Edinburgh Mental Well-being Scale(SWEMWBS)\nAscertain Dementia 8 -item Informant Questionnair(AD8)\nAdverse Childhood Experiences (ACE)\nBorderline Symptom List 23 - (BSL-23)\nComposite Morningness Questionnaire (CMQ)\nEating Attitudes Test- 26 Item (EAT-26)\nThe Florida Obsessive Compulsive Inventory (FOCI\nMental Health Recovery Measure-10 (MHRM-10)\nNursing Delirium Screening Scale - (NuDESC)\n\n
\nThe MENTAL HEALTH NCC WARRANTY RELEASE 5.01 multi-build is a warranty \nRisk Evaluation and Mitigation Strategy (REMS), which is mandated by the \nA server command being sent from Forum to the YSCLSERVER MailMan server \nat the sites wasn't being handled correctly by the server routines.\n \nResolution:\n-----------\nRoutine YSCLSERV was modified to put the correct DISPENSE FREQUENCY \n(field #2) in the CLOZAPINE PATIENT LIST file (#603.01); this routine was \nalso modified for defect 1132342 (see below). Routine YSCLTST5 was \nchanged to remove code that was overwriting data written in ^XTMP.\n \nFood and Drug Administration (FDA) for tracking clozapine patients. \n4. Nightly transmission missing required data.\nDefect 1132355\n \nProblem:\n--------\nThe YSCL DAILY TRANSMISSION option may not have sent all the necessary \ndata to the Forum Mail Group.\n \nResolution:\n-----------\n \nRoutines YSCLSERV, YSCLSRV1, YSCLSRV2, and YSCLSRV3 were modified to \nensure that all the needed data are returned. The call to the MailMan \nApplication Programmer Interface (API) was updated.\n \n5. Discontinue Message not sent\nDefect 1132342\n \nProblem:\n--------\nPatients are discontinued without a message being sent to the NCCC \nThe multi-build contains the Mental Health patch YS*5.01*154 and the \nalerting them that a patient was discontinued.\n \nResolution:\n-----------\nRoutine YSCLSERV was modified to ensure that the discontinue message is \nsent); this routine was also modified for defect 1132355 (see above).\n \n6. The option Daily Clozapine Transmission [YSCL DAILY TRANSMISSION] was \nnot always sending demographic data to the RUCL files in Hines.\nDefect 1155009.\nOutpatient Pharmacy patch PSO*7.0*574. The list of defects and their \n \nProblem:\n--------\nThe Daily Clozapine Transmission option was not sending demographic data \nto the CLOZARIL REPORTS file (#1900) in the FOURWORD server that resides \nin the Hines data center.\n \nResolution:\n-----------\nThis is not directly testable at sites.\nresolution is below.\nData are now sent to the FOURWORD server which contains the legacy \nClozapine registration database.\n \nRoutines YSCLDIS, YSCLSERV, and YSCLTST5 were modified. Routine YSCLTST9 \nwas created.\n \n * * * * * *\n \nTest Sites:\n----------\n \n - West Los Angeles VAMC (691)\n - N. Florida /S. Georgia VAMC (573)\n - VA Connecticut Healthcare System - West Haven Division (689)\n \nThere are no documentation updates associated with this patch.\n \nPatch Installation:\n \nPre/Post Installation Overview:\n-------------------------------\nDefect Tracking System Ticket(s) & Overview:\nThere are no tasks to be performed before the installation of this \nmulti-build. Note that the routines should be backed up to a PackMan \nmessage before installing the build.\n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 minutes\nto install. It should not be installed when the YSCL DAILY TRANSMISION \n--------------------------------------------\noption is running. If unsure when that is check the OPTION SCHEDULING \nfile (#19.2) using FileMan:\n \nSelect VA FileMan Option: Inquire to File Entries\n \nOutput from what File: OPTION SCHEDULING// (17 entries)\nSelect OPTION SCHEDULING NAME: YSCL DAILY TRANSMISSION\nAnother one: \nStandard Captioned Output? Yes// (Yes)\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \n \nComputed Fields\n \nNAME: YSCL DAILY TRANSMISSION\n QUEUED TO RUN AT WHAT TIME: OCT 05, 2019@01:30\n RESCHEDULING FREQUENCY: 1D TASK ID: 2577736\n \nInstallation Instructions:\n--------------------------\n1. The KIDS multi-build can be found in the VistA software repository at \ndownload.vista.domain.ext\nrelease for the National Clozapine Registry (NCR) software. This release \n * * * * * *\n \n ANON$:[ANONYMOUS.ANONYMOUS]MH_NCC_WARRANTY_5_01_T06.KID\n \nPlace the KIDS multi-build file into a local directory and use the KIDS \noption Load a Distribution option to load it into the transport global.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option.\n \n3. From the Kernel Installation and Distribution System Menu, select the\nInstallation Menu. From this menu, you may elect to use the following\n \noptions. When prompted for the INSTALL NAME enter:\n MENTAL HEALTH NCC WARRANTY RELEASE 5.01\n \na. Backup a Transport Global - This option will create a backup message\nof any routines exported with this patch.\n \nb. Compare Transport Global to Current System - This option will (allow\nyou to view all changes that will be made when this patch is installed. \nIt compares all components of this patch routines, DDs, templates, etc.).\n \nPatch YS*5.01*154 contains the following fixes:\nc. Verify Checksums in Transport Global - This option will allow you to\nensure the integrity of the routines that are in the transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\nchoose the patch to install (MENTAL HEALTH NCC WARRANTY RELEASE 5.01).\n \n5. Accept the default when prompted 'Want KIDS to Rebuild Menu Trees Upon \nCompletion of Install? NO//'\n \n6. Accept the default when prompted 'Want KIDS to INHIBIT LOGONs during \n \nthe install? NO//'\n \n7. Accept the default when prompted 'Want to DISABLE Scheduled Options, \nMenu Options, and Protocols? NO//'\n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0// enter 0 (zero).\n \nBackout /Rollback Strategy:\n---------------------------\nBackout will be done only with the concurrence and participation of\n1. Patients who are actively receiving clozapine (e.g. had a prescription \ndevelopment team and appropriate VA site/region personnel. The decision to\nbackout the software will be a joint decision between development\nteam, VA site and regional personnel, and other appropriate VA \npersonnel. Rollback applies to data only and is not applicable to this \nmulti-build.\n \nPrior to installing the KIDS multi-build, the site/region should have\nsaved a backup of the routines in a PackMan message using the Backup a\nTransport Global [XPD BACKUP] menu option (this is done at time of\ninstall). The message containing the backed-up routines can be loaded with\nlast month) are discontinued.\nthe "Xtract PackMan" function at the Message Action prompt. The PackMan\nfunction "INSTALL/CHECK MESSAGE" is then used to install the backed up\nroutines onto the VistA System.\n \nValidation of Backout Procedure\n-------------------------------\nThe backout Procedure can be verified by printing the first 2 lines of\nthe PSO* and YS* Routines contained in the MENTAL HEALTH NCC WARRANTY \nRELEASE 5.01 multi-build using the option First Line Routine Print [XU \nFIRST LINE PRINT]. Once the old routines listed in the multi-build patch \nDefect 1132329\nhave been restored, the first two lines of the Routines will no longer \ncontain the designation of patch 574 (for Outpatient Pharmacy PSO* \nroutines) and patch 154 (for Mental Health YS* routines) in the patch \nlist section on line 2 of the routines.\n \nProblem:\n--------\nwill fix the defects and incidents reported by the sites to the \nThe YSCL DAILY TRANSMISSION option checks for clozapine patients who \nshould be discontinued. The logic was erroneously discontinuing patients.\n \nResolution:\n-----------\nThe YSCLDIS and YSCLTST5 routines were modified to correct issues with \nclozapine patients being discontinued erroneously when the YSCL DAILY \nTRANSMISSION runs at the site. The fixes also ensure that information \nabout patients that were discontinued is stored in ^XTMP("YSCLDIS") as a \nlog. A discontinued patient is one who has the CLOZAPINE STATUS field \ndevelopers of the National Clozapine Coordination (NCC) Project. The \n(#54) in the PHARMACY PATIENT FILE (#55) set to "DISCONTINUED".\n \nThe YSCL154P pre-init routine was created to ensure that the YSCL DAILY \nTRANSMISSION option is scheduled in the OPTION SCHEDULING FILE (#19.2). \nIf the option is scheduled the installer will see a message like this:\n \nYSCL DAILY TRANSMISSION information in file #19.2:\n QUEUED TO RUN AT WHAT TIME: OCT 02, 2019@01:30\n RESCHEDULING FREQUENCY: 1D\n TASK ID: 2576362\nproject is also referred to as the Clozapine Modernization (ClozMod) \nNo issues found for the YSCL DAILY TRANSMISSION option.\n \nIf the YSCL154P routine detects an issue the installer will see messages \nthat look like the two examples shown below. If a message like this is \nshown then the site will need to take corrective action to schedule the \nYSCL DAILY TRANSMISSION using TaskMan options. If there are any \nquestions about how to schedule the option please contact the ClozMod \nteam.\n \nError message example 1 from the YSCL154P routine:\nProject.\n \nYSCL DAILY TRANSMISSION information in file #19.2:\n*** WARNING *** The option is NOT scheduled.\n \nThe YSCL DAILY TRANSMISSION Option should be scheduled to be run daily,\n in the early AM hours with no DEVICE.\n \nError message example 2 from the YSCL154P routine:\n \nYSCL DAILY TRANSMISSION information in file #19.2:\n \n QUEUED TO RUN AT WHAT TIME: * Time not found! *\n RESCHEDULING FREQUENCY: 1D\n TASK ID: * Task not found! *\n \nThe YSCL DAILY TRANSMISSION Option should be scheduled to be run daily,\n in the early AM hours with no DEVICE.\n \nNote: There are routines in the PSO*7.0*574 patch that also address this \ndefect.\n \nThe NCR is maintained by the National Clozapine Coordinating Center \n \n2. Registered clozapine patients who have not received a clozapine \nprescription in more than 56 days may not be discontinued.\nDefect 1132404\n \nProblem:\n--------\nA patient who had not received Clozapine for more than 56 days did not \nhave their status changed to DSCONTINUED during the nightly scan.\n \n(NCCC). The NCCC is responsible for VA's compliance with the clozapine \nResolution:\n-----------\nLogic in routine YSCLDIS was changed to fix the problem.\n \n3. Newly Registered clozapine patients were only getting a dispense \nfrequency of WEEKLY in file #603.01.\nDefect 1132352\n \nProblem:\n--------\n\n\nThe Mobile Application Phase 2 (MAP2) Mental Health Checkup project \nrequires access to certain Remote Procedure Calls (RPCs) that are part of \nthe MENTAL HEALTH package. The purpose of this patch is to publish those \nRPCs allowing access for use by Mental Health Checkup by setting the \nfield APP PROXY ALLOWED field (#.11) of the REMOTE PROCEDURE file (#8994) \nto YES.\n\n
\nThis patch addresses the following issue:\n \n1. When adding new entries to the CLOZAPINE PATIENT LIST (#603.01)\nfile patient lookups running in the background can return erroneous\nresults, which in turn leads to incorrect entries in the file.\n \nThis issue is being tracked in SNOW on INC10558263 and is also being\ntracked on Rational Defect #1263669.\n\n
\n The Health Integration & Modernization (HI&M) CLOZAPINE NCCC OVRD \n \n patient's prescription limited to 4 days.\n \n Problem:\n --------\n A Patient initially receives a 4-day emergency authorization, and \n later an NCCC Authorization and an NCCC Override Date. While the NCCC \n Override Date is still active, the Day Supply (for Outpatient Pharmacy) \n or Order Duration (for Inpatient Medications) continues to be limited to \n 4 days. Inpatient Medications Order Duration is defined as the number of \n days between the order's Start Date/Time and Stop Date/Time.\n The multi-build contains the Mental Health patch YS*5.01*166 and the \n \n Resolution:\n -----------\n If a NCCC Authorized National Override Date is in effect following \n an initial local override, the system shall process an active clozapine \n patient's clozapine prescription under national override processes \n allowing the patient to be provided with the approved quantity associated\n with their individual dispensing frequency from the DISPENSE FREQUENCY \n field (#2) in the CLOZAPINE PATIENT LIST file (#603.01). The approved \n quantity is determined by the order's Days Supply for Outpatient Pharmacy\n Outpatient Pharmacy patch PSO*7.0*612. The list of defects and their \n orders, and the Order Duration (days between Start Date/Time and Stop \n Date/Time) for Inpatient Medications orders.\n \n Technical Resolution:\n ---------------------\n The correct patient dispense frequency is now retrieved by changing\n CL1^YSCLTST4 to find the dispense frequency associated with the patient's\n registered clozapine authorization number.\n \n \n resolution is below.\n 4. Requirement 2 Defect 2 - Patient with NCCC Authorization receives a\n Special Condition Fill, and later an NCCC Authorization and Override\n Date, but day supply limited to 4.\n \n INC9951972: COVID-19 VistA PSO defect - Clozapine National Override \n patient's prescription limited to 4 days \n \n Problem:\n --------\n A patient with an initial NCCC Authorization receives a Special Condition\n \n override, followed by an NCCC override, is limited to a Day Supply\n (Outpatient Pharmacy orders) or an Order Duration (Inpatient Medications\n orders) limited to 4 for clozapine orders. The NCCC national clozapine\n override and the patient's regular clozapine dispense frequency\n are ignored.\n \n Resolution:\n -----------\n A patient with an initial NCCC clozapine authorization receiving a \n Special Condition override, followed by an NCCC override, shall be\n This patch is also being released with informational patch PSJ*5*403 that\n processed under national override rules allowing the patient to be\n provided with the approved quantity associated with their individual\n dispensing frequency from the DISPENSE FREQUENCY field (#2) in the\n CLOZAPINE PATIENT LIST file (#603.01). The approved quantity is reflected\n in the order's Days Supply for Outpatient Pharmacy orders, and the Order\n Duration (days between Start Date/Time and Stop Date/Time) for Inpatient\n Medications orders.\n \n Technical Resolution:\n ---------------------\n documents changes to Inpatient Medications' processing of clozapine\n Routine OVRRID^YSCLTST2 changed to kill ^XTMP("PSJ4D-"_DFN) and \n ^XTMP("PSO4D-"_DFN) after an NCCC override is successfully filed. This \n removes a patient's local clozapine override information when it is \n replaced by an NCCC override.\n \n \n Patch Components\n ================\n Files & Fields Associated:\n \n overrides that are a result of the defect fixes in PSO*7.0*612 and\n File Name (Number) Field Name (Number) New/Modified/Deleted \n ------------------ ---------------------- -------------------- \n CLOZAPINE PATIENT CLOZAPINE REGISTRATION Modified* (Mumps X-Ref) \n LIST (#603.01) NUMBER (#.01)\n CLOZAPINE PATIEN T(#1) Modified* (Mumps X-Ref)\n \n *New style "AC" mumps cross reference added to these two fields in file \n 603.01. New routine TRGR^PSOCLADD(DFN,PSOCLZNW) is invoked when a new\n entry is filed. New Integration Control Registration (ICR) #7175 has\n been created to document the new cross application interaction.\n YS*5.01*166.\n \n Forms Associated:\n Form Name File # New/Modified/Deleted\n --------- ------ --------------------\n N/A\n \n Mail Groups Associated:\n Mail Group Name New/Modified/Deleted\n --------------- --------------------\n N/A\n \n \n Options Associated:\n Option Name Type New/Modified/Deleted\n ----------- ---- --------------------\n N/A\n \n Protocols Associated:\n Protocol Name New/Modified/Deleted\n ------------- --------------------\n N/A\n COVID-19 multi-build is an emergency patch to the National Clozapine \n \n \n Security Keys Associated:\n Security Key Name New/Modified/Deleted\n ---------------------- --------------------\n N/A\n \n Templates Associated:\n Template Name Type File Name (Number) New/Modified/Deleted\n ------------- ---- ------------------ --------------------\n N/A\n Defect Tracking System Ticket(s) & Overview: \n \n * * * * * *\n \n Test Sites: \n ----------\n New Jersey Health Care System (561)\n VA Connecticut Health Care System (689)\n Boise VA Medication Center (531)\n \n \n --------------------------------------------\n Software and Documentation Retrieval Instructions:\n --------------------------------------------------\n The software for this patch is being released as a host file.\n \n The host file is available at the following location: \n /srv/vista/patches/SOFTWARE/PSO_YS_CLOZ_COVID.KID \n \n Documentation describing the new functionality is included in this\n release. Documentation can be found on the VA Software Documentation \n Library at: https://www.domain.ext/vdl/\n * Defect and Enhancement ID's listed below are internal identifiers and \n \n -------------------------------------------------------------------------\n Title File Name \n -------------------------------------------------------------------------\n MHA Security Technical YS_MHS_TM.pdf\n Manual/Guide\n \n Deployment Installation Back-Out pso_7_p612_ys_501_p166_dibr.docx\n and Rollback Guide - HI&M pso_7_p612_ys_501_p166_dibr.pdf\n Clozapine Overrides \n do not map to any external system.\n \n Release Notes - HI&M Clozapine pso_7_p612_ys_501_p166_rn.docx\n Overrides pso_7_p612_ys_501_p166_rn.pdf\n \n \n \n Patch Installation: \n \n Pre/Post Installation Overview: \n -------------------------------\n \n There are no tasks to be performed before the installation of this \n multi-build. Note that the routines should be backed up to a PackMan\n message before installing the build.\n \n Pre-Installation Instructions: \n ------------------------------\n This patch may be installed with users on the system although it is \n recommended that it be installed during non-peak hours to minimize\n potential disruption to users. This patch should take less than 5 \n minutes to install. It should not be installed when the YSCL DAILY\n Patch YS*5.01*166 contains the following changes: \n TRANSMISION option is running. If unsure when that is check the OPTION\n SCHEDULING file (#19.2) using FileMan:\n \n Select VA FileMan Option: Inquire to File Entries \n \n Output from what File: OPTION SCHEDULING// (17 entries) Select OPTION\n SCHEDULING NAME: YSCL DAILY TRANSMISSION Another one: Standard Captioned\n Output? Yes// (Yes) Include COMPUTED fields: (N/Y/R/B): NO// - No \n record\n number (IEN), no Computed Fields \n \n \n NAME: YSCL DAILY TRANSMISSION \n QUEUED TO RUN AT WHAT TIME: OCT 05, 2019@01:30 \n RESCHEDULING FREQUENCY: 1D TASK ID: 2577736 \n \n Installation Instructions: \n --------------------------\n1. Place the KIDS multi-build file PSO_YS_CLOZ_COVID.KID into a \nlocal directory and use the KIDS option Load a Distribution option to \nload it into the transport global.\n 1. Requirement 1 Enhancement - Automate the Pharmacy \n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select \nthe Installation Menu. From this menu, you may elect to use the \nfollowing options. When prompted for the INSTALL NAME enter:\n PSO*7.0*612\n \n a. Backup a Transport Global - This option will create a backup message\n of any routines exported with this patch.\n Registration of NCCC Clozapine Authorizations.\n \n b. Compare Transport Global to Current System - This option will (allow \n you to view all changes that will be made when this patch \n is installed. It compares all components of this patch \n (routines, DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - This option allows you to \n ensure the integrity of the routines that are in the transport \n global.\n \n Registry (NCR) software to correct defects to Clozapine National \n \n 4. From the Installation Menu, select the Install Package(s) option and \n choose the patch to install (PSO*7*612).\n \n 5. Accept the default when prompted 'Want KIDS to Rebuild Menu Trees \n Upon Completion of Install? NO//'\n \n 6. Accept the default when prompted 'Want KIDS to INHIBIT LOGONs during \n the install? NO//'\n \n 7. Accept the default when prompted 'Want to DISABLE Scheduled Options, \n Problem:\n Menu Options, and Protocols? NO//'\n \n 8. If prompted 'Delay Install (Minutes): (0 - 60): 0// enter 0 (zero). \n \n Backout/Rollback Strategy: \n ---------------------------\n Backout will be done only with the concurrence and participation of \n development team and appropriate VA site/region personnel. The decision \n to backout the software will be a joint decision between development\n team, VA site and regional personnel, and other appropriate VA personnel.\n --------\n Rollback applies to data only and is not applicable to this multi-build.\n \n Prior to installing the KIDS multi-build, the site/region should have \n saved a backup of the routines in a PackMan message using the Backup a\n Transport Global [XPD BACKUP] menu option (this is done at time of\n install). The message containing the backed-up routines can be loaded \n with the "Xtract PackMan" function at the Message Action prompt. The\n PackMan function "INSTALL/CHECK MESSAGE" is then used to install the\n backed up routines onto the VistA System.\n \n Currently, national clozapine authorization numbers are sent by the \n The new "AC" mumps cross reference for the CLOZAPINE PATIENT LIST file \n (#603.01) must be manually deleted via FileMan prior to restoring the \n backed up routines. \n \n The steps to delete the cross reference:\n 1. Access VA FileMan option Cross-Reference A Field via the VA FileMan \n Utility Functions [DIUTILITY] menu.\n 2. At the prompt, "What type of cross-reference (Traditional or New)?" \n enter NEW.\n 3. At the prompt, "Modify What File:" enter 603.01.\n National Clozapine Coordinating Center (NCCC) and filed into the \n 4. The new "AC" cross reference should be selected by default.\n 5. At the prompt "Choose E (Edit)/D (Delete)/C (Create):" enter DELETE.\n 6. At the prompt "Are you sure you want to delete the index \n definition? NO// YES"\n \n Example deletion of new "AC" index if backout is required:\n \n VA FileMan 22.2 \n \n Select OPTION: UTILITY FUNCTIONS \n CLOZAPINE PATIENT LIST file (#603.01). Later, a pharmacy user \n Select UTILITY OPTION: CROSS-REFERENCE A FIELD OR FILE \n What type of cross-reference (Traditional or New)? Traditional// NEW\n Modify what File: REMOTE PROCEDURE// 603.01 CLOZAPINE PATIENT LIST\n (74 entries)\n Current Indexes on file #603.01:\n 1589 'AC' index\n Choose E (Edit)/D (Delete)/C (Create): DELETE \n \n Which Index do you wish to delete? 1589// AC\n Are you sure you want to delete the index definition? NO// YES \n must manually execute Vista option Register Clozapine Patient [PSOL \n \n Index definition deleted.\n \n \n \n \n Validation of Backout Procedure \n -------------------------------\n The backout Procedure can be verified by printing the first 2 lines of \n the PSO* routines contained in the PSO*7*612 build using the option\n REGISTER PATIENT] (for new patients), or Edit Data for a Patient in the \n First Line Routine Print [XU FIRST LINE PRINT]. Once the old routines\n listed in the multi-build patch have been restored, the first two lines \n of the Routines will no longer contain the designation of patch 612 in\n the patch list section on line 2 of the routines.\n \n The backout of the new "AC" cross reference on the CLOZAPINE PATIENT \n LIST file (#603.01) can be verified by repeating the backout steps and \n verifying that there is no longer a selectable "AC" cross reference to \n delete.\n Clozapine Program PSOL [EDIT] (for previously registered patients). \n \n Clozapine Coordinating Center (NCCC) Override functionality.\n Resolution:\n ---------- \n Automate the clozapine registration process by automatically updating the\n patient's clozapine registration number and status when a new National \n Clozapine number is received from the NCCC, \n \n Technical Resolution:\n ---------------------\n A new Pharmacy API has been created that accepts Patient DFN and \n NCCC Clozapine Authorization number as input and files the number into \n \n the CLOZAPINE REGISTRATION NUMBER field (#53) in the PHARAMCY PATIENT \n file (#55), and updates the CLOZAPINE STATUS field (#54) to 'A' for \n Active. This API is executed when a new clozapine authorization is filed \n into the CLOZAPINE PATIENT LIST (#603.01) file via a mumps action cross \n reference.\n \n \n 2. Requirement 1 Defect 2 - National Override Date update fails \n for patient with more than one clozapine authorization.\n \n The NCR is maintained by the NCCC. The NCCC is responsible for VA's \n Problem:\n ----------- \n When a National Override is requested for a patient that has more \n than one entry in 603.01, the YSCL Server code performs a defective \n lookup into 603.01. If the patient has more than one entry in 603.01, the\n server code retrieves the older clozapine number and compares it to the \n clozapine number in the incoming override. Since the override is usually \n (if not always) performed on the most recent clozapine number, the \n override fails and generates the error message, "SSN (PATIENT,NAME) has \n multiple Clozapine Numbers at nnn". \n compliance with the clozapine Risk Evaluation and Mitigation Strategy \n \n Resolution:\n -----------\n The Mental Health Clozapine Server's NCCC Override patient lookup \n into file 603.01 shall be corrected when processing an incoming NCCC \n Override so that it looks in file 603.01 for the specific patient and \n NCCC Clozapine number from the incoming message. Only the file 603.01 \n entry matching the incoming NCCC clozapine number and patient shall be \n updated with the incoming NCCC Override Date.\n \n (REMS), which is mandated by the Food and Drug Administration (FDA) for \n Technical Resolution:\n ---------------------\n Correct routine YSCLSRV2 from failing to find a match in the \n CLOZAPINE PATIENT LIST file (#603.01) for the incoming clozapine \n authorization number and patient when attempting to file an NCCC Override\n Date in the OVERRIDE field (#3). Prior to the patch, the code compared \n clozapine number associated with the incoming NCCC override with the \n first (earliest) clozapine authorization number on file for the patient. \n If the patient had only one clozapine number on file, the match was \n successful. If the patient had more than one clozapine number on file, \n tracking clozapine patients.\n the match failed as the most recent clozapine number was ignored. Routine\n OVVRID^YSCLSRV2 was changed to look through all clozapine authorization \n numbers associated with the patient to find a match for the clozapine \n number associated with the incoming NCCC override. \n \n \n 3. Requirement 2 Defect 1 - Patient with Temp Registration and an \n NCCC Authorization and NCCC Override Date, but day supply limited to 4.\n \n INC9951972: COVID-19 VistA PSO defect - Clozapine National Override \n\n\nThe purpose of this patch is to add updates and correct defects in both \nthe MHA Windows executable and in the web-based MHA Patient Entry \napplication.\n\n
\n \nInformation Systems and Technology Architecture (VistA) side software for \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\n N/A \n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\n N/A\n \nthis effort. The other components are web-based and will be installed on \nParameter Definitions Associated:\n \nParameter Name New/Modified/Deleted\n-------------- --------------------\n N/A\n \nAdditional Information:\n-----------------------\n \nNew Service Requests (NSRs):\nservers outside of VistA and in the VA cloud services. The purpose of \n N/A\n \nPatient Safety Issues (PSIs):\n N/A \n \nDefect Tracking System Ticket(s) & Overview:\n \n 1. Rational ID Defect 1262531\n Sites Not Able to Transmit Clozapine Prescription Data\n \nPhase 2 is to provide enhancements for the National Clozapine Registry \n Problem:\n --------\nSome sites were not transmitting data via the OPTION Daily Clozapine \nTransmission [YSCL DAILY TRANSMISSION]. The cause was a missing FileMan \ndate in the log that is stored in the zero node of ^XTMP("YSCLTRN").\n \n \n Resolution:\n -----------\nThe YSCLTST5 routine was modified to prevent this problem. The code now \n(NCR).\nforces the initial loop value to zero and the logic proceeds.\n \n \nTest Sites:\n-----------\nN. FLORIDA/S. GEORGIA VHS (573)\n VA NORTH FLORIDA/SOUTH GEORGIA HEALTH SYSTEM - GAINESVILLE \nDIVISION \n Gainesville, FL \n \n \nWEST LA VAMC (691)\n VA GREATER LOS ANGELES HEALTHCARE SYSTEM - WEST LOS ANGELES\n Los Angeles, CA\n \nCONNECTICUT HCS (689)\n CONNECTICUT HEALTH CARE SYSTEM - WEST HAVEN DIVISION\n West Haven, CT \n \nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\nYS*5.01*149 will add new VistA options and a new file, CLOZAPINE HL7 \nThe software for this patch is being released in a PackMan \nmessage.\n \n \nDocumentation describing the new functionality is included in \nthis release. Documentation can be found on the VA Software \nDocumentation Library at: https://www.domain.ext/vdl/\n Clinical >> Mental Health\n \nDocumentation Title File \nTRANSMISSION (#603.05) to track the Health Level 7 (HL7) messages. This \nName \nNational Clozapine Coordination Project VistA User Guide\n VistA Clozapine User Guide YS149 Updates.docx\n \n \nPatch Installation:\n-------------------\n \nPre/Post-Installation Overview:\n \nfile can be read by users who have FileMan access and a "Y" in their FILE \nAfter the patch is installed the new option Transmit Clozapine Rx HL7 \nMessages [YSCL HL7 CLOZ TRANSMISSION] needs to be scheduled in TaskMan. \nInstructions are listed below.\n \nAlso, after installing the patch the coordinator for the YSCLHL7 LOGS \nMail Group should be notified that the patch was installed and that users \ncan be added to the Mail Group. MailMan messages with information about \nthe HL7 message transmissions will be sent to that group.\n \nThis is an example:\nMANAGER ACCESS CODE, which is field #3 in the NEW PERSON file (#200). \n \nSubj: Clozapine HL7 report ST ELIGIUS HOSPITAL (999) [#30896] \n11/29/19@16:42\n22 lines\nFrom: HRUBOVCAK,JC In 'IN' basket. Page 1\n--------------------------------------------------------------\n HL7 transmission report Nov 29, 2019@16:42:04\n Site: ST ELIGIUS HOSPITAL (999)\n \n Total messages sent: 12\nThe purpose of this software package is for the Department of Veterans \nThis patch also contains HL7 message components and their associated \n \n Message ID Type Prescription\n \n 999 550 ADT^A28 900042\n 999 551 RDE^O11 900042\n 999 552 ADT^A28 900218\n 999 553 RDE^O11 900218\n 999 554 ADT^A28 900285\n 999 555 RDE^O11 900285\n 999 556 ADT^A28 900217\nsubscriptions, plus a logical link to VistA. Most of these components \n 999 557 RDE^O11 900217\n 999 558 ADT^A28 900281\n 999 559 RDE^O11 900281\n 999 560 ADT^A28 900223\n 999 561 RDE^O11 900223\n \n Sent to: G.YSCLHL7 LOGS\n *** END OF REPORT ***\n \n \nwill not be visible to VistA users. The HL7 messages will be sent as a \nPre-Installation Instructions:\n \nThe only pre-installation step is to decide who will be the coordinator \nfor the new YSCLHL7 LOGS Mail Group; the installer will be prompted for \nthat name during the installation.\n \nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 3\nminutes to install. \nbatch to track specific VistA activities such as registering a new \n \nThe menu rebuild may take a few minutes after the patch is installed.\n \nNo options or protocols need to be disabled before installation.\n \nInstallation Instructions:\n \n1. Choose the PackMan message containing this build. Then select \n the INSTALL/CHECK MESSAGE PackMan option to load the build.\n \nclozapine patient for treatment. HL7 messages will be sent to an \n2. From the Kernel Installation and Distribution System Menu, \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter YS*5.01*149.\n \n B. Select the Backup a Transport Global option to create a \n backup message of any routines exported with this patch. \nexternal system and VistA will receive HL7 acknowledgements, where needed.\n It will not backup any other changes such as DDs or \n templates.\n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n all of the components of this patch, such as \n \n routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the \n patch to install. \n \n i. When prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//' answer <YES>.\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \n install? NO//' answer <NO>. \nA new HL LOGICAL ENTRY is named YSCL-NCCC and will connect to the NCR \n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//' answer <NO>.\n \n iv. When prompted 'Enter options you wish to mark as \n 'Out Of Order':' press <ENTER>.\n \n v. When prompted 'Enter protocols you wish to mark as \n 'Out Of Order':' press <ENTER>.\n \nservers.\n vi. When prompted 'Delay Install (Minutes): (0 - 60): 0//',\n press <ENTER> for zero seconds.\n \n \nPost-Installation Instructions:\n \nAfter the patch is installed the installer should notify the coordinator \nof the YSCLHL7 LOGS mail group (see notes above) and schedule the new \ntransmission option.\n \n \nThe new option Transmit Clozapine Rx HL7 Messages [YSCL HL7 CLOZ \nTRANSMISSION] should be scheduled in TaskMan to run daily in off-hours, \ntypically between 10:00 PM and 2:00 AM. The option can be scheduled \nusing the TaskMan option Schedule/Unschedule Options [XUTM SCHEDULE]. \nThe option will not have a DEVICE FOR QUEUED JOB OUTPUT. That is, the \ndevice field should be null.\n \nThis is an example:\n \n * * * * * * * * * * * * * *\nAffairs (VA) to maintain compliance with federal mandates for tracking \nA complete list of the patch components can be generated using KIDS \n \n Edit Option Schedule\n Option Name: YSCL HL7 CLOZ TRANSMISSION \n Menu Text: Transmit Clozapine Rx HL7 Messag \n TASK ID: 8798880\n ___________________________________________________________\n QUEUED TO RUN AT WHAT TIME: DEC 5,2019@23:00 \n \nDEVICE FOR QUEUED JOB OUTPUT: \n \noptions.\n QUEUED TO RUN ON VOLUME SET: \n \n RESCHEDULING FREQUENCY: 1D \n \n TASK \nPARAMETERS: \n \n SPECIAL QUEUEING: \n \n______________________________________________________________\n \n \nExit Save Next Page Refresh Quit\n \n \n \n * * * * * * * * * * * * * *\n \nBack-Out/Roll Back Plan:\n------------------------\nThe routines can be restored from the backup message created in \nExcept for routine YSCLTST5, the VistA components in this patch are all \ninstallation step B above. The new options can be placed out-of-order or \ndeleted. The new routines can be deleted manually without affecting \nother VistA packages. No data will need conversion to restore the \nsystem. The data dictionary components of this patch can be removed \nusing standard VA FileMan options.\nnew and do not modify existing software.\n \nThe types of HL7 messages to be transmitted:\n ADT^A05 (Pre-admit a Patient)\n RDE^O11 (Pharmacy/Treatment Encoded Order)\n \nClozapine prescriptions and dispensing.\nPatch Components:\n-----------------\nFile #603.03 was already at sites; it has two new fields.\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nThis is an existing file.\nCLOZAPINE PARAMETERS (#603.03) Modified\n \n (#603.03) HL7 TRANSMISSION START (#20.01) New\n (#603.03) HL7 TRANSMISSION END (#20.02) New\n \nThis is a new file.\nCLOZAPINE HL7 TRANSMISSION (#603.05) New\n (#603.05) POINTER TO PATIENT FILE (#2) (#.01) New\n (#603.05) RX TRANSMISSION (#1, sub-file #603.51) New\n (#603.51) DATE/TIME OF TRANSMISSION (#.01) New\n (#603.51) HLO MESSAGE (#.02) New\n (#603.51) MESSAGE TYPE (#.03) New\nThis patch will add enhancements to the Mental Health package for the \n (#603.51) PRESCRIPTION # (#.04) New\n \nForms Associated:\n \nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\n N/A\n \nMail Groups Associated:\n \nNational Clozapine Coordination (NCC) Project. It is also referred to as \nMail Group Name New/Modified/Deleted\n--------------- --------------------\n YSCLHL7 LOGS New\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nYSCL HL7 CLOZ RETRANSMIT run routine New\nYSCL HL7 CLOZ TRANSMISSION run routine New\nthe Clozapine Modernization (ClozMod) Project. YS*5.01*149 is part of \nYSCL HL7 LIST CLOZAPINE RXS run routine New\nYSCL HL7 MAIN menu New\nYSCL HL7 QUEUE TRANSMISSION run routine New\nYSCL HL7 REPORT BY DATE run routine New\nYSCL HL7 STATUS REPORT run routine New\n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nPhase 2 of the MENTAL HEALTH NCC PROJECT and is the Veterans Health \n N/A\n \nSecurity Keys Associated: \n \nSecurity Key Name\n-----------------\n N/A\n \nTemplates Associated:\n \n\n\nBackup of YS*5.01*172 on Apr 05, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nMental Health belongs to the CORE+8 group of DHCP packages. This package\nincludes modules to assist Psychologists, Psychiatrists, Nurses, Social\nWorkers, and other health-care professionals in the care of Mental\nHealth patients. Major clinical entities include various clinical\nmodules and options, an inpatient module, a psychologic testing\nmodule, and various supervisory options.\n\n
\n- This message contains modified routines:\n- Also a bulletin will be sent to G.PAD to inform them of a needed update\n from routine PRSRUTL.\n\n PRSRAU1, PRSREX1, PRSRTLPR, PRSRL4, PRSRLSOR, PRSRUTL.\n- PRSRAU1 and PRSREX1 save the SW variable before queueing the reports.\n- PRSRTLPR adds three $GET's at line label HDR to protect against the\n case in which there are no Supervisors, Timekeepers or OT/CT sups for a \n T&L unit.\n- PRSRL4, PRSRLSOR are modified to bullet proof the display of an employee\n cost center/organization. If the pointer in the PAID codes file to\n 454.1 is missing the code will be displayed instead of the description.\n\n
\n o Modify OT/CT Report to only include the specified year. Also, allow\n users to select a range of pay periods.\n o Modify Display Pay Period output to pause during screen display.\n o Add text to download statistics message concerning SSN corrections.\n\n
\nSUPPORT FOR NON-PATIENT IDENTITY MANAGMENT\nRefer to patch PRS*4.0*128 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch addresses one issue. The Central Business Office (CBO) \nrequested additions and deletions to the ETA list of hybrids to mirror \nthe current valid list of hybrid Occupation Series & Title codes.\n\n
\nThis patch addresses 2 issues:\n1. Employees are able to certify own timecard without security key\n2. Site is unable to change an intermittent employee's time card\n\n
\nThis patch addresses 3 issues:\n1. Undefined error in option 'Display Employee Tour Hours'\n2. Undefined error in option 'Find Mismatched Normal and Tour Hours'\n3. Overtime/Compensatory (OT/CT) requests are erroneously approved when\n user enters '^' at selective disapproval.\n\n
\nThis patch contains a report for sites to identify Comp Time to\nbe reinstated to RN's covered by the National Nursing Union (NNU)\nas dictated by the NNU/VA Settlement ruling.\n\n
\nThis patch primarily implements new functionality within VistA's\nNursing \nservice patch also supports the collection of data for the VANOD. Patch \nNUR*4.\n0*43 must be installed prior to patch PRS*4.0*126.\n \nThe patch implements functionality to gather and store information related\nto nurses providing direct patient care (as well as indirect care). It\nprovides functionality to enter, edit, update, review, certify and store\nthis information. The system provides the ability for a point to point \ntransfer of this information from each VistA instance to the VANOD.\nPersonnel and Accounting Integrated Data/ Enhanced Time and Attendance\n(PAID/ETA) software version 4.0 to provides appropriate\ndata to VANOD (Veterans Affairs Nursing Outcomes Database) in accordance\nwith Public Law 107-135 and the OIG Recommendation 4a (annual reporting\nrequirement). The patch also includes minor modifications to existing ETA\nfunctionality to support the collection of data for the VANOD.\n \nThis patch is dependent on the Nursing Service patch-NUR*4.0*43. The \n\n
\nThis patch addresses one issue:\n1. The employee Social Security Number is displayed in full \n when accessing the 'List Leave Requests' report.\n\n
\nEffective June 17, 2012, occuation series code 0679 (Medical Support \nAssistant) will be converted to Hybrid status per Public Law 111-163,\nthe Omnibus Health Services Act.\n\n
\nPresident Clinton made December 26th, 1997 a Holiday. This was granted since\n\nthe Christmas Holiday falls on a Thursday in 1997. This patch enhances the\nPAID ETA v4.0 software to add December 26,1997 as a Holiday. The Holiday\nwill be used by the PAID software in functions such as opening Pay Period\n97-26 and setting tours of duty to Holiday Excused in Time Cards.\nThe only routine modification necessary to facilitate this is to routine\nPRS8HD which is a procedure that is called by other PAID options to determine\na singular holiday or to determine holidays for a year or to determine all the\nholidays within a year of a particular date.\n\n
\nPay period calculation does not extend past 2012 pay periods.\n\n
\nPresidential Executive Order declares December 24, 2012 as an official \nfederal holiday. PAID ETA must be updated to reflect this additional\nholiday.\n\n
\nThis patch corrects two issues:\n1.Intermittant nurse entitled to but not able to post on call.\n2.PRS MONTH CALENDAR option does not include pay periods past 2012 or\nholidays past 2013.\n\n
\nOccupation Series/Title codes 010106-Marriage Family Therapist and\n010117-Licensed Mental Health Provider need to be given hybrid status. \nAlso, the Central Business Office (CBO) submitted a list of Occupation \nSeries/Title codes and have requested those be given Hybrid status \nso that they will now receive Saturday Premium Pay.\n\n
\nTitle 5 part time employees are eligible for Sunday premium\npay just like the full time employees. VistA ETA has to be\nchanged to allow the part time employees to be paid Sunday\npremium pay.\n\n
\nPresidential Executive Order declares December 26, 2014 as an official \nfederal holiday. PAID ETA must be updated to reflect this additional \nholiday.\n\n
\nThis patch addresses two issues: \n1.Part time Physician Memorandums have incorrect pay period \n designations after 2012.\n2.Two new codes need to be added to the Telework Code file.\n\n
\nThis patch addresses three issues:\n1. Additional Occupation Series & Title codes to be added to hybrid table.\n2. Healthcare worker codes should not be included in hybrid table.\n3. Spelling error will be corrected.\n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\nThe following 3 items are included in this patch.\n3. Fix for undefined error at CCORG+15^PRSRUTL when an employee is\nassociated with a deleted cost center/organization in the PAID CODES\nfile (#454). The error occurs while running the Employee Leave Pattern\n[PRSRSU-LEV-PATR] report. \n\n\n1. The 8B Edit Checks, [PRSA EDIT], option is updated to stop\nreporting errors when wage grade employees earn and use compensatory time. \n\n2. On the Timekeeper Main Menu, [PRSA TK MENU], the option menu text for \nthe Cancel OT Request [PRSA OT CAN] option has been edited to Cancel \nOT/CT Request.\n\n\n
\nPAID ANNUITANT INDICATOR (#454.0126) SUB FILE UPDATE\n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\nPatch PRS*4.0*142 addresses four issues:\n3. The Mismatch Report by T&L Unit [PRSNR MISMATCHES BY T&L] option will \n produce an undefined error when an employee has work hours associated \n with a non-regular tour of duty. \n \n4. The All Non Direct Activity at a Nurse Location [PRSNR NURLOC NONDIR -\n COORD] option will produce a subscript error if an employee who worked \n as a nurse during the date range of the report is not currently a \n nurse.\n \n1. PAID options that use PRIMLOC^PRSNUT03 to return a nurses primary \n assignment will return an incorrect location if that location has a \n similar string to another.\n \n2. The Mismatch Report by T&L Unit [PRSNR MISMATCHES BY T&L] option will \n not display the first entry in a report. \n \n\n
\nPatch PRS*4.0*146 addresses two issues:\n (#451.7) file is storing information incorrectly.\n \n1. A DD(Data Dictionary) change is needed for the UNIFORM ALLOWANCE AMT \n CPPD (#536) field of the PAID EMPLOYEE (#450) file. The same change\n is also needed for the UNIFORM ALLOWANCE AMT CPPD (#109) field of the \n of the EMPLOYEE (#459.01) sub-file of the PAID PAYRUN DATA (#459)\n file.\n \n2. The NURSE T&L UNIT (#15) field of the POC DAILY TIME EXTRACTION \n\n
\nThis patch will address three issues:\n3. The Monthly Calendar [PRS MONTH CALENDAR] is only coded to\n calculate pay periods through 2017, and holidays through 2018.\n \n1. A subscript error occurs in the Memoranda Report [PRSP PS MR] \n option after a site converts to the Veterans Affairs Time and \n Attendance System (VATAS).\n \n2. The Memoranda Report [PRSP PS MR] option does not display \n 2018 pay periods.\n \n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\n This patch will address two issues:\n \n 1. An Electronic Subsidiary Record (ESR) cannot be approved for\n an employee name with multiple Internal Entry Numbers (IENs)\n in the PAID EMPLOYEE (#450) file.\n \n 2. Timekeepers cannot ENTER Overtime for a T&L when an inactive\n T&L shares the same number.\n\n
\nThis patch corrects one issue:\n \n1. The PAID - Expenditure Report will not work after a\n site moves to the Veterans Affairs Time and Attendance \n System (VATAS).\n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\n1. Fix 8B string for code CA (Calendar Year Adjustment):\n a. Don't send CA when value is 0000 because it will reject at AAC.\n2. Fix 8B string for code CY (SF 2806 Adjustment):\n a. Revise 8B Edit Check from\n 'If Normal Hours are 00 or 01, then CY cannot exceed 13.0; otherwise,\n CY cannot exceed Normal Hours + (UN + US) - (NO + NP)'\n to\n 'If Normal Hours are 01, then CY cannot exceed 13.0; otherwise, CY\n cannot exceed Normal Hours + (UN + US) - (NO + NP)'\n\n
\nThis patch contains updates to the Hybrid table for Occupation\nSeries/Title Codes converting to Hybrid status.\n\n
\n o When a tour of duty is edited and the next pay period is selected, the\n is generated for a single employee and the output is queued.\n default value for the compressed tour indicator was occassionally\n different than the actual value of the employees' compressed tour\n indicator. After the patch is installed, an appropriate default value\n will be presented.\n o The Decomposition of Time output for the Pay Period Certification and\n Decompose Time options will note when the Compressed Tour Indicator has\n been changed since the previous pay period.\n o Corrects undefined error when the Employee Overtime/Comptime Report\n\n
\n1. This patch updates the PAID download server to accept and store year\n2000 dates.\n \n2. The date selection function (DATSEL^PRSEUTL) has been modified to\nhandle year 2000 dates. Users must enter 4 digit years.\n\n
\nUpdate the PAID CODE FILES for the performance/proficiency rating entry.\n\n\n
\nYear 2000 updates to routines, data dictionaries, options, etc.\n\n
\nCorrects problems with the "ASX" cross-reference (T&L WHICH CERTIFIES\nSUPERVISOR) in the T&L UNIT file.\n\n
\n o Fix Employee Leave Used report.\n o Fix Employee Leave Requested report.\n\n
\n1. Add warning messages to certification of timecards option when the \n decomp calculates more overtime than what is approved.\n2. Add same warning to Payroll option "Pay Period exceptions".\n3. Update Armitage reversal, removing types of time as payable for Sunday\n premiums. Types of time removed are COP, Hol Excused, Comp Used.\n\n
\nThis KIDS build modifies the PAID 4.0 decomposition routines in order to\ncorrect a bug in the software. The bug occurs when a part time employee\nworks a full 40 hour week. In addition the employee works compensatory\ntime at some point in the week, thereby working over 40 hours during the \nweek. When the decomposition calculates the segments of time at the end\nof the week after the total time has reached 40 hours, the employee is\nincorrectly credited with overtime pay. This patch corrects this anomoly.\n\n
\n Fix Education Tracking Reports\n 1. Fix several reports so classes that occur on last day of reporting\n period (CY or FY) and have both a date and time specified will be\n included in the output.\n 2. Modify PRSE-MI-LIST option so Service prompt is obtained by DIC call\n instead of DIE call.\n\n
\nFix decomposition problems with night (shift and tour) differentials.\n\n
\nPatch makes three basic changes to the package:\npatch adds a new file to store overtime warnings. When the supervisor \napproves a time card without resolving the descrepancy between approved \novertime for a week of the pay period and overtime calculated in the 8B \nstring, then a warning will be filed in the new OVERTIME WARNINGS file. \nA new option that uses List Manager will be available to Payroll so that \nthey can view these warnings. Prior to this patch the warnings appeared \non the Pay Period Exceptions option on the payroll main menu. Since \neven when a corrected time card was done no change is made to the 8B \nstring these warnings continue to appear on the exceptions report. \nAfter the patch the exceptions report will first check to see if payroll \n\nhas cleared the warning (via the new list manager option) before \ndisplaying it on the exceptions report.\n\n 1. Supervisor's choice of canceling a leave request is removed.\n 2. ListManager options to manage overtime (OT) warnings that appear \n on Pay Period Exceptions report are added to the package.\n 3. Payroll Main Menu is reorganized by moving several options\n into a submenu on the Main Menu.\n\nAs item 2 above states, functionality to handle OT warnings is added. The\n\n
\n Fix Education Tracking Module problems:\n 1. Inaccurate and Inconsistent Report Results.\n 2. Class Registration Calendar Report ILLEGAL NUMBER error.\n 3. Student Registration and Class Limit.\n 4. Enter/Edit Ward/Unit-Location Training UNDEF error.\n 5. Fix Mandatory Deficiency reports so 13th month not displayed.\n\n
\nFix decompsition problems related to:\n o Sunday premium: Wage grade 2-day tour that crosses pay periods.\n o Sunday premium: GS with 'pre-scheduled' OT.\n o Sunday premium: Nurse with premium OT/CT that extends into weekend.\n o Part-Time hours when >80 hours in pay period and on compressed tour.\n\n
\nThis patch contains a post installation routine (PRSXP47) that will set\nDecember 24, 1998 as a Holiday Benefit day for employees who are\nscheduled to work on that day. Special instruction from VACO Payroll\nPolicy will be necessary in conjuction with this patch. These\ninstruction will direct timekeepers to post the second half of these \nemployee's tours as Holiday excused. Nothing should be posted for the \nfirst half of the tour.\n\n\n
\n1. Fix Expenditures report to include employees with only benefits.\n2. Fix 8B Edit Checks to check appropriate employees.\n3. Correct second line in routines with invalid formats or release dates.\n\n
\nFEGLI PROGRAM AND RATE STRUCTURE CHANGES\n\n
\nIt has been decided that the way Alternate Work Schedule Credit\nIn order to distinguish between comp time and credit hours new \n"time remarks" will be added to the TIME REMARKS file (# 457.4). \nThe new remarks will be applicable to the type of time formerly \nknown as comptime, but now known as comptime/credit hours. The \nnew remarks will consist of "comp time - no remarks" and "credit \nhours". When posting comp/credit hours the timekeeper will now be \nrequired to enter one of the valid remarks.\n\nHours will be handled will be through the use of the Compensatory\nTime field. All rules governing Comp Time will be applied to Credit\nHours, e.g., pre approval and expiration after 7 pay periods, etc. \nTo make the dual use of this field more clear to employees, \nsupervisors and Payroll/HR, the displayed name of the field should \nbe changed to reflect the actual contents of the field, Compensatory \nTime and Credit Hours.\n\n\n
\nREQUIRE TIME REMARK CODE WHEN CU IS POSTED FOR ENTIRE DAY\n\n
\nFix Education Tracking problems related to:\n\n\no Attendance when the class name is 53 characters long.\n\no Fix undefined variable when using the Enter/Edit Ward/Unit-Location\n Training [PRSE-W.I.] menu.\n\no Use the appropriate variable for FileMan call.\n\n\n
\nThis build modifies PAID version 4.0 to allow three types of firefighters. \n 2. Add new type of time, Additional Firefighter Hours.\n 3. Report new type of time--Base Tour Non Pay Hours--for non pay during a \n firefighters regularly scheduled hours.\n 4. Calculate overtime and unscheduled time for all firefighters.\n 5. Add new TT8B edits for the new types of firefighters.\n\nPrior to this software enhancement the software treats all firefighters \nas a single type. Two new types of firefighters will be created with \nnew entitlements and new time and attendance processing. The third type \nof fire fighter is the fire fighter type that exists before this \nsoftware enhancement.\n\nThis patch provides software changes for the following:\n 1. Update entitlements entries and modify the entitlement lookup routine.\n\n
\nFirefighter fixes.\n firefighters.\n error #55 Sum of RA + RB + RC or RE + RF + RG cannot exceed 20.0\no Modify Pay Period Exceptions so firefighters with premium pay code R or\n C do not need approved overtime requests for RA/RE (regular hours at OT\n rate) in the 8B string.\no Fix decomp so NT/NH not counted for code R firefighters.\no Fix decomp so code R and C firefighter overtime and/or unschedule\n regular is not undercounted when comptime used has been posted.\no Fix 8B Edit Checks so the following checks are only made for code R or C\n firefighters.\n error #175 RA hours may not exceed PT hours minus 53.\n error #176 RE hours may not exceed PH hours minus 53.\no Fix 8B Edit Checkks so the follow check is not made for code R or C\n\n
\nThis enhancement will add a 30 day prior window lookup to the Leave Request \n[PRSA LV REQ] menu option.\n\n
\nUpdate Class Registration Enter/Delete to use $$ADD^XUSERNEW instead of\nFILE^DICN to add entries to the NEW PERSON file. Require programmer\naccess or security key PRSE CORD in addition to the package parameter\nbefore allowing entries to be added to the NEW PERSON file. Improve how\nlocks are managed.\n\n
\n 1. Fix supervisor disapproval of a tour change to the next pay period.\n 2. Don't ask for confirmation when selecting a tour of duty.\n\n
\n Fixes for Post Employee Time [PRSA TK POST] option.\n o Allow the OT/CT on Premium T&L remark to be used with RG (regular time)\n so weekend premiums can be paid without also paying night differential.\n o Exit the alphabetical employee loop if timekeeper enters '^' at prompt\n when an employee's pay period record is locked.\n o Modify screen edit validation so posting of NOON as a time does not\n result in some validation checks being skipped.\n\n
\nUpdate Post Miscellaneous Data option to not allow a request for a\nRecord of Salary Payments on an employee with pay plan F (Fee Basis).\nAlso correct descriptions of Followup codes 04 and 20 in PAID\nCODE FILE #454.\n\n
\nEducation Tracking Report fixes.\n\n
\nThis patch corrects several problems with the PAID decomposition for\npart-time employees who have Overtime (OT), Comptime (CT), Regular\nTime (RG), Leave Without Pay (WP) or Non-Pay (NP).\n\nThis patch addresses the following NOIS message: VAC-0998-21654\n\n \n\n
\nThe Set Holiday Benefit Day incorrectly calculates the 5 day future window\nwhen the option is run withing 5 days of the end of the month.\n\nThis patch will correct this calculation.\n\nThis patch addresses the problem reported on NOIS ISW-0100-20373.\n\n
\nEMPLOYEE PPA REPORT NOT DISPLAYING DATA CORRECTLY\n\n
\nThis patch will address several NOIS that have been reported dealing with how\nthe software automatically posts various types of leave for Full Time Doctors\n(title 38).\n\n
\nThis patch corrects a few minor problems with leave used reports and the\nvalidation of leave requests.\n\n
\nPPA PROCESSING PROBLEM AND %DT(0) LEAKAGE\n\n
\nThis patch stops SSN's from being printed on the Class Roster. It also\nprevents an undefined error that can occur when class names are edited.\n\n
\nThis patch adds additional logic to the Sunday Premium pay calculation and will\nallow the software to correctly differentiate between work performed on shift\n1, 2 or 3.\n\n
\nThis patch will address several NOIS that have been reported dealing with how\nthe PAID software posts callback Overtime (OA/OE) and Comp Time Earned (CE/CT)\nwhile On-Call.\n\n
\nEMPLOYEE CREDITED WITH EXTRA HOLIDAYS\n\n
\nEducation Tracking Patch <PRS*4*23>\n\n
\nWith the passing of Public Law 106-554 most employee who are elgible to take\n3. Updating the Leave Request and Edit Leave Request portion of the software.\n4. Updating the Supervisory Approvals.\n5. Updating the Timekeeper postings.\n6. Updating the Decomposition.\n7. Updating the various reporting programs that display Military Leave.\nMilitary Leave (ML) will now be elgible to take this type of leave in hours\ninstead of days.\n \nThis patch updates the Vista PAID software to be compliant with this Public\nLaw. Changes will include:\n\n1. Updates to the Data Dictionary.\n2. Updating the interface between Central PAID and Vista PAID.\n\n
\nThis patch will correct a problem that went out in patch PRS*4.0*69.\n\nIt consists of one routine PRSATIM.\n\n
\nOn 12/6/2001 President Bush signed an executive order that excuses\n\nThe only routine modification necessary to facilitate this is\nto routine PRS8HD.\nexecutive branch employees from duty on the Monday before Christmas Day\n(12/24/2001) except where agency officials decide they must remain open\nbecause of national security or defense or other public reasons.\n\nThis patch enhances the PAID/ETA v4.0 software to add December 24,2001 as\na holiday. The holiday will be used by the PAID/ETA software during the\nopening of Pay Period 01-25 at which time the tours of duty for Monday\n12/24/2001 will be set to Holiday Excused (HX).\n\n
\nThis patch will address a problem that has been reported dealing with the\n8B edit for Full Time doctors taking Military Leave (ML).\n \nThe patch will also remove the code that was added to routine PRSATIM by\npatch PRS*4*69. These modifications were intended to force users to\nrequest at least one hour when entering a leave request for Military\nLeave (ML). This restraint was later modified and the appropriate\nchecks were added to the Pay Period Certification portion of the software.\n \n\n
\nOn January 23, 2002, the President signed into law H.R. 3447, becoming\n\nFor a full description of the patch please refer to patch PRS*4*74 on Forum.\nP.L. 107-135. Section 121 of the bill modifies 38 USC 7454(b) to provide\nweekend (i.e., Saturday and Sunday) premium pay for certain "health care\nprofessionals". In VA terms, "hybrid employees" MUST now receive\nSaturday and Sunday premium pay under title 38 rules. This change\n"appl(ies) with respect to pay periods beginning on or after the date of\nenactment of this Act".\n\nThis patch updates the PAID/ETA v4.0 software to ecomply with this Public Law.\n\n
\nOn January 23, 2002, the President signed into law H.R. 3447, becoming\nP.L 107-135.\n\nSee the patch descriptions of PRS*4.0*74 and PRS*4.0*75 on Forum for full \ndetails of what these two patches added to the VistA PAID/ETA software.\nP.L. 107-135. Section 121 of the bill modifies 38 USC 7454(b) to provide\nweekend (i.e., Saturday and Sunday) premium pay for certain "health care\nprofessionals". In VA terms, "hybrid employees" MUST now receive\nSaturday and Sunday premium pay under title 38 rules. This change\n"appl(ies) with respect to pay periods beginning on or after the date of\nenactment of this Act".\n\nThis patch adds the remainder of the functionality to comply with Public Law\n\n
\nThis patch will address OCCUPATION SERIES & TITLE codes ending in an Alpha\n\nThe OCCUPATION SERIES & TITLE (#16) field is stored in the PAID EMPLOYEE\n(#450) file.\n\nSee the patch description of PRS*4*76 on Forum for full details on the\nadditions and changes this patch made to the VistA PAID/ETA software.\ncharacter for the Hybrid employees defined in Public Law 107-134.\n\nBeginning in fiscal year 2002 some of the OCCUPATION SERIES & TITLE\ncodes end in an Alpha character. These Alpha characters correspond to an\nexisting numeric code. The $$HYBRID^PRSAENT extrinsic function was\nmodified to convert OCCUPATION SERIES & TITLE codes ending in an Alpha\ncharacter into its numeric equivalent before determining if the employee\nis a Hybrid as described by Public Law 107-134.\n\n
\nThis patch will compile information on the hours worked by nurses for the\nyears 1997 through 2001.\n\nFor a complete description of the report see the patch description on Forum.\n\n
\nThis patch will address several NOIS related to how leave is credited and\ncharged. The first NOIS addresses a problem with how Full Time doctors\nare charged Non Duty days for weeks where they only work 2 days. The\nsecond NOIS addresses a problem with how General Schedule employees are\ncredited for Holiday Worked time. The final NOIS describes a problem\nwhere a menu option's description does not accurately reflect the output\nof its report.\n\n
\nThis patch will update the input transform for the CODE (#.01) field of the\nOCCUPATION SERIES/TITLE (#454.01) multiple in the PAID CODE FILES (#454) file.\n\n\n
\nThis is a patch to the education tracking module of the PAID 4.0 package.\nIt is an enhancement that allows holders of the PRSE CORD key to report\nindividual training by one, many or all services. \n\n
\nThis patch will update the logic that determines whether or not to pay the 2\nhour minimum for work performed on a holiday.\n\n
\nThis patch adds all of the necessary changes to the VistA PAID/ETA software to\nbe in compliance with Central PAID Service Request 02-436. Please see the\npatch description for complete details of these changes.\n\n
\nSee the patch description on FORUM for a complete description of this patch.\n\n
\nSee the patch description on Forum for a complete description of this patch.\n\n
\nThis patch adds all of the necessary changes to the VistA PAID/ETA software to\nbe in compliance with Central PAID Service Request 02-485 PAID LABOR\nDISTRIBUTION AND ACCOUNTING CHANGES and Service Request 03-623 VistA/DHCP ETA\nDOWNLOAD CONSOLIDATION. Please see the patch description on FORUM for complete\ndetails of these changes.\n\n
\nSee the patch description on Forum for complete details of this patch.\n\n
\nSee Forum for a complete description of this patch.\n\n
\nSee the patch description on Forum for complete description of this patch.\n\n
\nSee the patch description on FORUM for a complete description of this patch.\n\n
\nSee the patch description on Forum for complete details on this patch.\n\n
\nFixes for PAID reports.\n 1. Employee Leave Requested report\n - Include multiple requests by employee with same From Date.\n - Include all requests the overlap the report's date range.\n 2. Expenditures report\n - Replace 'Total Earnings' by 'Gross Pay'. Fix Benefits calculation.\n 3. Reports that show payperiod exceptions (e.g. List Daily Exceptions)\n - Improve identification of OT/CT exceptions when multiple requests.\n\n
\nSee the patch description on Forum for complete details on this patch.\n\n
\nThis patch will set the extra memorial day holiday for the passing of former\nPresident Ronald Reagan. See Forum for additional information.\n\n\n
\nSee the patch description on Forum for details on this patch.\n\n
\nSNT AND PREMIUM PAY UPDATES\n\n
\nSet January 20, 2005 as a holiday for selected sites in the DC area.\n\n
\nThis patch contains the fix necessary to correct the queuing of the reports\nfrom the Employee Inquiry [PRSD 04 EMPLOYEE INQUIRY] option and the reports\nfrom the Payrun Data Inquiry [PRSD 04 PAYRUN DATA INQUIRY] option. After this\npatch is installed, the queued reports will include all applicable data\ninstead of just the header without data.\n\n
\nThis patch contains the fix necessary to remove the \nsupervisor/lead indicator if necessary based on the Employee\nOccupation Series & Title code that is downloaded from Central\nPAID. After this patch is installed, the supervisor/lead indicator\nfield in file #450, field #41, will not be populated if the\nemployee is no longer in a supervisory position.\n\n
\nSee patch description on Forum for complete details of this patch.\n\n
\nThis patch addresses one issues:\nThe Employee Leave Pattern Report does not include all \ntypes of leave that are available for a leave request. A\nrequest was made to include all types of time that are\navailable for a leave request on this report.\n\n
\nThis patch will address the following:\nThe employee count numbers on the Strength Report are not \ntotaling up correctly and report is not balancing.\n\n
\nThis patch addresses three issues:\n1. The VCS Allotments field in files #450 and #459 are not\n formatted correctly.\n2. Fields 758, 759, 760, 761 in file #450 are not available to\n print using the PRSD 04 PRINT EMPLOYEE FILES option.\n3. The description of field 7 of file #458.5 has a typographical error.\n\n
\n \nPresident Ford Funeral (01/02/07) - Government closing\n\n
\nThis patch addresses four issues:\n1. Labor Distribution Audit report errors out\n2. Error received when payroll processes automatically \n after system shutdown\n3. Employee not charged with enough Military Leave\n4. Meal time incorrectly being deducted from Annual Leave\n\n
\nPublic Law 108-445 modified the pay policies for VHA Physicians and \nDentists effective January 8, 2006. This patch modifies VistA PAID/ETA in\naccordance with the new pay policies for leave accrual and charging of\nleave.\n\n
\nThis patch will modify the display of VA employee social security numbers.\n\n
\nNurse Alternative Work Schedules\n\n
\nSee the patch description on Forum for complete details concerning this \npatch.\n\n
\nPatch to update PAID ETA to conform to new public law which revokes premium pay\nfor employees in a leave status. \n\n
\nThis patch addresses three issues:\n1. A Cache error is generated when a number greater than\n 142 characters is entered into the time fields on the \n Leave Request screen.\n2. HRIS Bulletin 07-08 has mandated an increase in the \n length of the Duty Station field.\n3. An electronic signature is not recognized.\n\n
\nThis patch will set Friday December 26, 2008 as an extra Christmas\nholiday.\n\n
\nThis patch will set Inauguration Day, Tuesday January 20, 2009 as a \nholiday for stations 101 and 688.\n\n
\nThis patch addresses three issues:\n1. Erroneous data entries in file #458\n2. The E node in file #458 is not setting \n correctly sometimes\n3. Part time MD's (Pay Plan Q) are getting paid more than\n 80 hours. \n\n
\nTOUR CHANGE PROBLEM;LD DISPLAY ERROR;LEAVE USED REPORT CORRECTION\n\n
\nThis patch addresses 3 issues:\n1. Error <UNDEFINED>FX1+8^PRSATE in 'Enter/Edit Emp Tour of Duty'\n2. Overlapping tour error appears in 'Enter/Edit Emp Tour of Duty' \n when the tours do not overlap\n3. Incorrect 8b edit error\n\n
\nThis patch addresses three issues:\n1. Saturday premium pay incorrect when holiday pay involved\n2. Part time employee pay incorrect when 2 holidays fall together\n3. Part time and nurse holiday pay incorrect when it \n includes a two-day tour.\n\n
\nThis patch addresses one issue: the Uniform allowance hourly rate is\ndifferent in the Central PAID system than in the VistA system.\n\n
\nThis patch addresses 2 issues:\n1. Leave Without Pay (LWOP) is not being counted in the Night Differential\n calculation\n2. Hard error occurs in Approve Signed ESRs [PRSP ESR SAP] option when\n the Time & Leave (T & L) unit begins with an alpha character\n\n
\nThis build contains the routine for patch GMRY*3*2.\n\n
\nPlease see the patch description for GMRY*4*2 on Forum for an explanation of\nthis patch.\n\n
\nPlease see the patch description for GMRY*4*3 on FORUM for an\nexplanation of this patch.\n\n
\nPlease read the GMRY*4*5 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nThis patch will correct tWo problem within the \nINTAKE/OUTPUT application as reported.\n\n
\n \n \n \n \n \nThis patch fixes problems with displaying output.\n\n
\nThis patch corrects the following issue:\n \nIf a nurse has changed service positions (for example: from Licensed \nPractical Nurse (LPN) to Registered Nurse (RN), the former service \nposition might be listed on the Intake/Output 24 Hours Itemized \nShift Report. This issue will occur when the previous service position \nfor a nurse is filed at a lower internal entry number (IEN) than the \ncurrent service position's IEN in the Nurs Position Control (#211.8) file.\n\n
\nThis KIDS Build contains the Intake/Output package v4.0.\n\n
\nThis package contains Intake/Output module which tracks patient\nIntake/Output measurements.\n\n
\nThis build will export patch GMRV*3*3.\n\n
\nThis build contains a patch which corrects a bug reported in the NOIS\nmessage MAD-0896-40098. Please see the GMRV*3*4 entry on the Patch\nModule of FORUM for more details about this patch.\n\n
\nThis patch fixes a problem reported in E3R #8958. The Create Vital\nMeasurement Quick Order Protocol [GMRVORQUICK] option limits the creation\nof quick orders to one quick order per vital measurement. This is wrong.\nIt should allow any number of quick orders per vital measurement.\n\n
\nPlease see the patch description for GMRV*4*1 on FORUM for an explanation\nof this patch.\n\n
\nRefer to the patch description.\n\n
\nPlease read the GMRV*4*13 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the GMRV*4*14 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the GMRV*4*16 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease see the GMRV*4*3 patch entry in the FORUM patch module for an\ndescription of this patch.\n\n
\nPlease see the GMRV*4*5 patch entry in the FORUM patch module for an\ndescription of this patch.\n\n
\nPlease check the patch description on FORUM for GMRV*4*2 for an\nexplanation of this patch.\n\n
\nRefer to the patch for the patch description.\n\n
\nVitals/Measurements patch GMRV*4.0*7\n\n
\nRefer to the patch description.\n\n
\nVitals/Measurements patch GMRV*4.0*10\n\n
\nRefer to the patch description.\n\n
\nThis KIDS Build contans the Vitals Measurements package v4.0\n\n
\nPlease read the GMRV*5*1 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the GMRV*5*3 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nHL7 MESSAGE CHANGES\n\n
\nVITALS GUI ERROR UPON CVP DATA ENTRY & GRID/GRAPH BLANKING ISSUE\n\n
\nPlease read the GMRV*5.0*11 patch description on FORUM for an explanation\nof what this patch does.\n\n
\nPlease read the GMRV*5.0*19 patch description on FORUM for an explanation\nof what this patch does.\n\n
\nVitals Measurement GUI Updates\nMISCELLANEOUS MAINTENANCE ISSUES\n\n
\nPlease read the GMRV*5*25 patch description on FORUM for an explanation\nof what this patch does.\n\n
\nPlease read the GMRV*5*23 patch description on FORUM for an explanation\nof what this patch does.\n\n
\nThis patch will correct the hospital location pointers in the GMRV VITAL \nMEASUREMENT file (#120.5) by making a call to the Registration package to \nget the hospital location pointer the patient was checked in to.\n\n
\nVARIOUS GUI CORRECTIONS\n\n
\nPlease read the GMRV*5*6 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nADD VHIC API CALL FOR PATIENT LOOKUP\n\n
\nThis patch will include the creation of a new field that will incorporate \nVitals Type File (#120.51): This file contains a list of vital \nsign types, for example, height, weight, and temperature\nVitals Qualifier File (#120.52): Description of how the patient \nvital signs and measurements were taken. Categorized by location (e.g., \nright arm, left leg), position (e.g., lying, sitting, standing), method \n(e.g., cuff, Doppler, assisted ventilator, etc.), site (e.g., right, \nleft), quality (e.g., actual, estimated), and cuff size (e.g., adult, \nsmall adult, pediatric).\nVitals Category File (#120.53): This file contains the cuff size, \nlocation, method, position, quality, and site of the vitals which are \ndata from the respective Standards Development Organization (SDO) to the \nsimply ways of grouping qualifiers which store the important data.\nGMRV VITAL TYPE (#120.51) file shall be updated to include a new field to \nstore LOINC code field from the respective SDO. The new field s shall be \nset as a multiple in order to accommodate the potential future need to \nutilize an additional or different code type, such as CPT, for \nassociation with a given Vital Type term. The data gathered from the \nneeded LOINC CT mapping effort will be used to populate this field.\nGMRV VITAL QUALIFIER (#120.52) file shall be updated to include a new \nfield to store the SNOMED CT code from the respective SDO. The new field \nshall be set as a multiple in order to accommodate multiple SNOMED CT \nVitals Type (#120.51), Vitals Qualifier (#120.52) and Vitals Category \ncodes per term within file 120.52, since there may be one-to-many \nrelationships in addition to one-to-one relationships when the active \nterms in files 120.52 are associated to SNOMED CT codes. The data \ngathered from the needed SNOMED CT mapping effort will be used to \npopulate this field.\nGMRV VITAL CATEGORY (#120.53) file shall be updated to include a new \nfield to store the SNOMED CT code from the respective SDO. The new field \nshall be set as a multiple in order to accommodate multiple SNOMED CT \ncodes per term within file 120.53 since there may be one to many \nrelationships in addition to one to one when the active terms in files \n(#120.53) files. \n120.53 are associated to SNOMED CT codes. The data gathered from the \nneeded SNOMED CT mapping effort will be used to populate this field.\nThe Vital Type, Vital Qualifier, and Vital Category files will be \naddressed during this effort due to the nature of the data within these \nfiles that are necessary for referencing, reporting, and interoperability \npurposes. \nThe following three files are associated with the Vital Signs Domain:\n\n
\nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the Vitals User and Vitals Manager Graphical User \nInterface (GUI) requires an upgrade to Delphi version XE8 in order to \nimplement the new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nCHANGE LB TO KG CONVERSION FACTOR IN CUMULATIVE REPORT\n\n
\nFIX LOADING HELP VIA NETWORK INSTALL\n\n
\nThis patch will resolve the following issues in the Vitals Lite DLL\n- Prevent entering Vitals for a future date\n\n
\nPlease read the GMRV*5*2 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nBuild for patch GMRV*5.0*38 - Post install to update version paramaters\n\n
\nGMRV*5.0*39 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\nUpdate maximum flow rate for supplemental oxygen.\n\n
\nThe purpose of this build is to export a Vitals DLL with no more broker \ndependency with CPRS.\n\n
\nPlease read the GMRV*5*5 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the GMRV*5*8 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the GMRV*5*12 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nENTRY OF MIDNIGHT AND MULTIPLE ENTRY SECONDS ISSUES\n\n
\nNON-CLINICS ALLOWED FOR SELECTION AND OUT OF BOUNDS HEIGHT ISSUE\n\n
\nERROR NOT TRAPPED IN GMRVPCE1\n\n
\nThis software is used to track patient vital signs and measurements.\n\n
\nThis is only a part of the General Medical Record Package. This part \ncontains the vitals/measurements module which tracks patient vital signs\nand physical measurements.\n\n
\nThis build contains NUR*3*8. Please see the patch module for more\ndetailed information about this patch.\n\n
\n The education tracking reporting module has been modified to interface\nwith the education tracking module in version 3.5 of PAID. All editing\nof education data must be done via the PAID 3.5 education tracking module.\n\n
\nThis build contains NUR*4*4. Please see the patch description on FORUM for\nan explanation of this patch.\n\n
\n \n \nPlease see the patch description for NUR*4*13 on FORUM for an\nexplanation of this patch.\n\n
\n \n \nPlease see the patch description for NUR*4*14 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*16 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*17 on FORUM for an\nexplanation of this patch.\n\n
\n \n \nPlease see the patch description for NUR*4*18 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*20 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*21 on FORUM for an\nexplanation of this patch.\n\n
\nRefer to patch NUR*4*23 for the description.\n\n
\nPlease see the patch description for NUR*4*22 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the NUR*4*5 patch entry in the FORUM patch module for an\ndescription of this patch.\n\n
\nRefer to the patch NUR*4*25 for the patch description.\n\n
\nPlease see the patch description for NUR*4*24 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*26 on Forum for an\nexplanation of this build.\n\n
\nPlease see the patch description for NUR*4*28 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*29 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*30 on FORUM for an\nexplanation of this patch.\n\n
\nPatch NUR*4.0*31\nSee Patch for Description.\n\n
\n \nPlease see the patch description for NUR*4*32 on FORUM for an\nexplanation of this patch.\n\n
\n \nPlease see the patch description for NUR*4*33 on FORUM for an\nexplanation of this patch.\n\n
\nPlease read the NUR*4*34 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease see the patch description for NUR*4*2 on FORUM for an explanation\nof this patch.\n\n
\nPlease see NUR*4.0*35 on the FORUM Patch Module for a description of this\npatch.\n\n
\nPlease see NUR*4.0*36 on the FORUM Patch Module for a description of this\npatch.\n\n
\nPlease read the NUR*4*37 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nThis is a maintenance patch that fixes known problems in the Nursing \npackage as identified by NOISes SAJ-0301-71155, HIN-0601-40523, \nFGH-0402-32096, UNY-1202-11134 and ANN-0203-41275.\n\n
\nThis patches modifies the Employee Activation/Separation \nReport to show start/vacancy dates entered in the past.\n\n
\nOption NURAFL-SPO SERVICE POSITION FILE, EDIT will delete existing \nentries that are missing data even if Exit is selected from the form.\n\n
\nPlease read the NUR*4*40 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nThere is code in routine NURCES1 that does a Direct Global Read (via \nIA1381). This code is not executed. Since the Vitals package is going to \nretire IA1381 the code will be removed. The Nursing End of Shift which \nis the option that executes NURCES1 is using the Vitals API (IA1446) to \nget Vitals data.\n\n
\nThis patch supports patch PRS*4.0*126--PAID ENHANCEMENTS FOR VANOD. This\npatch--NUR*4.0*43--must be installed prior to patch PRS*4.0*126. This \npatch provides for the ability to enter and store additional information\nfor Nursing Locations that is required by the VANOD (Veterans Affairs\nNursing Outcomes Database) in accordance with Public Law 107-135 and the\nOIG Recommendation 4a (annual reporting requirement).\n\n
\nIntake Product 8\n\n
\nPlease see the patch description for NUR*4*3 on FORUM for an\nexplanation of this patch.\n\n
\nThe patch addresses two (2) issues:\n If the abbreviation is re-entered with a value with a length\n greater than 10 characters, a program error occurs (UNDEFINED)\n and the typical user VistA session is terminated.\n \n2. When a patient is admitted/transferred to a new ward and there\n is no corresponding entry in the NURS LOCATION file (#211.4),\n the user gets an erroneous message that Queueing is not allowed\n that is displayed after the "Patient Transferred" message.\n \n1. When using the Service Position File, Edit option [NURAFL-SPO]\n in the Administrative Site File Functions option [NURSFL-MENU];\n the prompt for the Service Position abbreviation requires an\n entry of 10 characters or less. When a new abbreviation is\n correctly entered, the application adds it as a new NURS SERVICE\n POSITION. After entering the abbreviation, the application pops\n a ScreenMan Form that allows the abbreviation to be re-entered.\n\n
\n20170309 Enhancements to Nursing Patient Assignment Worksheet\n Only display last 4 of SSN\n Display diagnosis as "ON FILE"\n \n20170316 Enhancements to Nursing End of Shift Report\n Various enhances to EOS report\n\n
\nThis patch addresses one issue:\n \n1. VistA crashes when a "?" is entered at the Military Status query.\n\n
\nPlease see the patch description for NUR*4*8 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*6 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*10 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*7 on FORUM for an\nexplanation of this patch.\n\n
\nPlease see the patch description for NUR*4*12 on FORUM for an\nexplanation of this patch.\n\n
\nThis Build contains the Nursing Service package v4.0. Also, it contains\nNUR*4*1 changes.\n\n
\nThis entry exists to allow all NURSING patches (e.g., NURA, NURC, NURQ and NURS) to be linked to this one PACKAGE file entry which has a namespace of NUR.\n\n
\nThis build contains the routines and data dictionary changes for patch\nGMRG*3.0*1.\n\n
\nThe Text Generator allows for the codifying/boilerplating of clinical\ndevelopment of treatment plans, and as a front end to generate progress\nnotes for patients.\nforms. Patient data for these forms are then collected via a menu driven\ndata entry system. Output is generated from this collection in an\noutline or paragraph format. There are two major components to the Text\nGenerator: 1) Content Building, and 2) Patient Data Enter/Edit. The\ndata reporting mechanism is currently a part of the Patient Data\nEnter/Edit, but will become its own component in the future. The Text\nGenerator is currently used by the Nursing Package to generate Nursing\nCare Plans. Future plans include the use by Mental Health for the\n\n
\nPatch 5 provides the following:\nQAPPTUSR LEX-1195-42218 Prevent users from printing hard copy of\n surveys while the survey is still under\n development.\n \nQAPSCRN1 DAY-0496-40265 Eliminate undefined variable QAPCNT that\n occurred at SUSPEND^QAPSCRN1 when the user\n timed out on the first question in the\n survey.\nQAPUTIL2 ---- TRAP^QAPUTIL2 errored with UNDEFined\n variable, FILEDA, when testing UNDEFined\n \n variable, QAPCNT, error in QAPSCRN1.\n \nNew Checksums:\n \nQAPCOPY value = 8115210\nQAPPTUSR value = 6033850\nQAPSCRN1 value = 19389275\nQAPUTIL2 value = 13751688\n \n \nRoutine: NOIS: Fix:\nRequirements: \n \nThere are no special requirements for installation. However, it is\nrecommended that options QAP PARTICIPANT MENU and QAP SURVEY \nMANAGEMENT MENU be disabled for the few moments needed to run\nthe KIDS install of this distribution.\n \n \nUser Impact:\n \n \nUsers may be affected if they are in the process of responding to a survey\nor printing hard copy or copying a survey. The impact is from the old\nversion of the routine not being found since the new version is now\npresent (after the users process looked up the old version directory\nlocation). The likelihood of this occurrance is quite small. The user\nwill need to restart their survey and should be able to pick up where they\nleft off.\nQAPCOPY DAY-0496-41627 Recreate 'AB' (full file) index on field\n within multiple (authorized editors). Failure\n to recreate 'AB' index prevented authorized\n editors from editing the copied survey.\n \n\n
\nThis is Patch 6 to Survey Generator v 2.0. It provides:\n pointer to a file that pointed to another\n file and the application lookup routine was \n on the first file.\n \n BRX-1195-11059 Demographic questions in free text format \n were supposed to be limited to a length of\n from 1 to 40 characters; not 3 to 40. The \n DIR(0) was set to a limit of 3 to 40; even\n though the DD is set to handle 1 to 40.\n \n \nQAPPT1 DAY-1195-40313 Users were unable to print a copy of the\n incomplete survey with their answers, as \n documented on page 63 of the Users Guide.\n This fix allows the intended use of the\n "Print A Copy For Yourself" option.\nRoutine: NOIS: Fix:\n \nQAPDEM1 DAY-0796-40387 Prevent UNDEF error in a case where an \n application lookup routine is invoked in\n place of DIC lookup and Y is not set to\n -1 when an error occurred in the lookup.\n This occurred when the demographic was a \n\n
\nDISABLING SURVEY GENERATOR PACKAGE\n\n
\nThis package will completely generate a survey with information provided\nby the survey author, then allow participation of designated audiences.\nOnce the participation is finished, the author may generate statistics.\n\n
\n Fixes null subscript errors in LAGEN after patch LA*5.2*17.\n\n
\n This patch will prevent a null subscript error from occurring when using\n Solution: The code has been changed to use a FileMan DIC call to\n and select the package 'LA*5.2*44'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'. KIDS will disable the appropriate option during the\n install (see note above).\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LA44 can be deleted after successful patch installation.\n \n \n perform the lookup of an entry in this file.\n *****************************************************************************\n Below is an example of the dialogue seen during the KIDS install:\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*44 Loaded from Distribution 10/7/98@13:20\n:18\n => LA*5.2*44\n \nThis Distribution was loaded on Oct 07, 1998@13:20:18 with header of\nLA*5.2*44\n\nIt consisted of the following Install(s):\nLA*5.2*44\n \n LA*5.2*44\nWill first run the Environment Check Routine, LA44\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*44\n \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n Associated NOIS\n \nDEVICE: HOME// VIRTUAL TERMINAL\n \n \n Install Started for LA*5.2*44 :\n Oct 07, 1998@13:20:32\n \n Installing Routines:\n Oct 07, 1998@13:20:33\n \n ---------------\n Running Pre-Install Routine: PRE^LA44\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n BAY-0798-32112\n Installing OPTION\n LA*5.2*44\n \n Oct 07, 1998@13:20:33\n \n Running Post-Install Routine: POST^LA44\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n \n *** Post install completed ***\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LA*5.2*44 Installed.\n Oct 07, 1998@13:20:34.\n \n \n Install Message sent #103009\n \n \n \nInstall Completed\n \n \n \nSelect Installation Option:\n \n Routine Summary\n End of example\n *****************************************************************************\n option LEDI Setup [LA7V SETUP] after the installation of the HL7 patch\n ---------------\n \n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD Results\n \n Routine Before Patch After Patch Patch List\n HL*1.6*14.\n ------ ------------ ----------- ----------\n \n LA44 NA 2463527 44\n LA7VSTP 25404911 24725864 27,44\n \n \n INSTALLATION INSTRUCTIONS\n -------------------------\n The patch is distributed in KIDS format in a PackMan message.\n \n \n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n However the following conditions apply:\n \n -Users should not be using option LEDI Setup [LA7V SETUP].\n The LEDI Setup [LA7V SETUP] option will be placed out of service\n during this install.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n 1. Problem: A null subscript error was occurring at VER+3 in routine\n \n If the routine LA7VSTP is a mapped routine, appropriate action should be\n taken to disable the mapped routine at the beginning of the patch\n installation process and to insure proper updating of mapped routines\n afterward. Also, if the routine LA7VSTP resides in multiple locations\n within the system configuration, all routine directories should be updated\n appropriately.\n \n NOTE: MailMan and KERNEL patches must be current on the target system to\n avoid problems loading and/or installing this patch.\n LA7VSTP because the software was not properly quitting when\n\n NOTE: This KIDS install places the option LEDI Setup [LA7V SETUP]\n out of service during the install. The option is not added or\n changed by this patch. If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n \n The site can answer "NO" if they choose since the option\n is unchanged.\n checking for the existence of an entry in HL7 MESSAGE TYPE\n \n Additionally, if performing the KIDS Compare option, KIDS will\n report that this option is being changed. This is a false\n message since the option is only being disabled during the\n install by KIDS. It is included in the KIDS build only for the\n purpose of being disabled during the install by KIDS.\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n file (#771.2).\n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n \n all routines have the correct checksums.\n \n 6. If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routine in your\n production account to the routine in the patch by using the 'Compare\n a Transport Global to Current System' option (see note above).\n These options can both be found under the 'Installation' menu.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n\n
\n This patch will address a fix to printing of Lab shipping manifests.\n Solution: When there is a change in shipping condition or container then\n \n \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*45 Loaded from Distribution 10/16/98@13:0\n0:43\n => LA*5.2*45\n \nThis Distribution was loaded on Oct 16, 1998@13:00:43 with header of\nLA*5.2*45\n force the printing of the patient demographics.\nIt consisted of the following Install(s):\nLA*5.2*45\n \n LA*5.2*45\nWill first run the Environment Check Routine, LA45\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*45\n \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES//\n \n \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*45 :\n Oct 16, 1998@13:03:28\n \n Installing Routines:\n Oct 16, 1998@13:03:28\n \n \n Running Pre-Install Routine: PRE^LA45\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n \n Installing OPTION\n Oct 16, 1998@13:03:29\n \n Running Post-Install Routine: POST^LA45\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n Associated NOIS\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LA*5.2*45 Installed.\n Oct 16, 1998@13:03:30.\n \n Install Message sent #11240689\n \n --------------\nStarting Menu Rebuild: Oct 16, 1998@13:03:30\n \nCollecting primary menus in the New Person file...\n \n Primary menus found in the New Person file\n ------------------------------------------\n \nOPTION NAME MENU TEXT # OF LAST LAST\n USERS USED BUILT\n \n \nXMUSER MailMan Menu 293 10/16/98 10/16/98\nXUPROG Programmer Options 2 02/19/97 10/16/98\n\n <******* items removed for brevity *******>\n\nDVBA VARO REMOTE VA Regional Office Remote... 250 10/16/98 10/16/98\n \nBuilding secondary menu trees....\n \nMenu Rebuild Complete: Oct 16, 1998@13:27:04\n TOG-0898-12117\n \n \n \nInstall Completed\n \n \n \nSelect Installation Option:\n\n End of install example\n\n WRJ-0998-10878 \n *****************************************************************************\n \n Test Sites\n ----------\n \n Milwaukee VAMC\n Togus VAMC\n White River Junction VAMC\n \n ----------------------------\n Problem: The patient demographics were not printing under certain\n \n ROUTINE SUMMARY\n ---------------\n \n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[patch list]**; Sep 27, 1994\n \n CHECK^XTSUMBLD results\n conditions on the manifest when a new page was started.\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- --------------\n LA45 N/A 2463531 45\n LA7SMP 15780871 15792287 27,45\n \n INSTALLATION INSTRUCTIONS\n -------------------------\n The install time for this patch is less than 2 minutes if menus are not\n rebuilt. If menus are rebuilt then install time on a heavily used system\n If a new page is started because of a change in shipping\n will be approximately 25 minutes. This patch can be installed when\n Laboratory users are on the system.\n\n However the following conditions apply:\n \n - Printing of a Laboratory shipping manifest should not be occurring.\n The option Print Shipping Manifest [LA7S MANIFEST PRINT] will be\n disabled during the install by the KIDS build.\n \n Patch installation needs to be coordinated with the Laboratory\n condition or container and the last patient on the previous\n Information Manager (LIM/ADPAC).\n \n NOTE: MailMan and KERNEL patches must be current on the target system to\n avoid problems loading and/or installing this patch.\n \n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n and current page are the same, the patient demographics would\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n not print on the current page.\n \n 6. If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routine in your\n production account to the routine in the patch by using the 'Compare\n a Transport Global to Current System' option. These options can\n both be found under the 'Installation' menu.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*45'. When prompted 'Want to\n \n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LA45 can be deleted after successful patch installation.\n \n \n *****************************************************************************\n Below is an example of the dialogue seen during the KIDS install:\n\n
\nFixes Date problems occurring after installation of Vitek's Y2K software. \n\n
\nPatch LA*5.2*47 VISTA BLOOD BANK SOFTWARE V5.2 \nAll changes have been reviewed by the VISTA Blood Bank Developer and found\n \nThis patch is compatible with OERR 2.5 and both versions of CPRS ,GUI and\nList Manager.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan \n menu. This option will load the KIDS package onto your system.\n 2. Review your mapped set. If the routines are mapped,\n they should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global \n on your system. You now need to use KIDS to install the \nto have no impact on the VISTA BLOOD BANK SOFTWARE version 5.2 control\n Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation \n should be done during off peak hours and when the Laboratory \nfunctions.\n computer users are idle.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off \n peak hours, and less than 5 minutes during peak hours\n which is NOT RECOMMENDED.\n 7. Installation of this patch does not require any additional \n memory space.\n 8. From the 'Installation Menu' of the KIDS menu, run the \n option 'Install Package(s)'. Select the package \n 'LA*5.2*47' and proceed with the install.\n \n 9. If any routines were unmapped as part of step 2, they \n should be returned to the mapped set once the \n installation has run to completion.\n \n======================\nTest Sites:\n \nLong Beach, CA\nMilwaukee, WI\nLoma Linda, CA\nRISK ANALYSIS: Changes made by patch LA*5.2*47 have no effect on Blood\nNorth Chicago, IL\nWest Palm Beach, FL\n=====================\n \nDD Changes:\nNone\n=====================\n \nRoutine Listing:\nThe second line of the routine now looks like:\nBank software functionality, therefore RISK is none.\n<TAB> ;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994\n \nRoutines: Before After Patch\n Check Check List\nLA47 N/A 2222265 47\nLAGEN 8395369 9445120 1,17,22,27,47\n \n===================\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*47 does not\nalter or modify any software design safeguards or safety critical element\nfunctions.\nDEVICE PRODUCT LABELING STATEMENT\n \nPOTENTIAL IMPACT ON SITES: This patch contains no changes to files and\nroutines identified in Veterans Health Administration (VHA) Directive\n97-033. The changes that are made have no effect to Blood Bank\nfunctionality or medical device control functions. There is no adverse\npotential to sites.\n \nVALIDATION REQUIREMENTS BY OPTION: There are no required validation\nscenarios to be completed by sites after installing this patch.\n \n \n========================================\n \nPatch Description: \nThis is the companion patch for LR*5.2*221. Full description of ALL\nenhancements are given in LR*5.2*221. \n \nThis patch support the ability to purge Automated Instrument data based on\n \ndate range or inactivity range. This enhancement is to support Laboratory \nElectronic Data Interchange (LEDI) sites ability to purge automated\nMay 10, 1999\ninstrument data based on user's supplied parameters. \n \nThe functionality of this patch is coupled with the features and function\nof patch LR*5.2*221. LA*5.2*47 is required for LR*5.2*221 installation.\nThe functionality of the patch is expressed after patch LR*5.2*221 has\nbeen installed.\n \nONLY THE ROUTINE 'LAGEN' IS CONTAINED IN THIS PATCH. All other LR*\nassociated name spaced routines and options are contained in LR*5.2*221.\nThe following options are transported and installed by LR*5.2*221.\n \n \nThe 'Clear instrument/worklist data' [LRINSTCLR] option has been enhanced.\nThe changes to this option implements selective clearing of instrument\ndata from the ^LAH global. When entries are made in the ^LAH global to\nstore instrument data pending verification, the date/time stamp of\ncreation and result updating is now recorded. This date will be used to\nselectively remove data from the ^LAH global based on the date original\nresult was received or last updated.\n If during the clearing process an entry in ^LAH global is found with\nno date/time in the creation/update field, the current date/time is\nVISTA Laboratory Package patch LA*5.2*47 contains no changes to software\nentered into the entry. This entry is then eligible for clearing the next\ntime the option is ran.\n \n \n The 'Clear instrument/worklist data' option will allow clearing by either\nof the following ways. Data received before the selected date (optional\ntime) is purged. If you enter a date only then data received before that\ndate is cleared. If you enter a date/time then data received before that\ndate/time is cleared.\n \ncontrolled by VHA DIRECTIVE 97-033, titled VISTA BLOOD BANK SOFTWARE\n Example:\nIf you enter Sept 4, 1998 then data received through Sept 3, 1998 is\ncleared. If you enter Sept 4, 1998 @1200 then data through Sept 4, 1998 is\ncleared.\n \n The following routines support purge enhancement:\n LAGEN [LA*5.2*47]- Changes were made to set date/time of entry creation\nand last update. Last update can be different than creation date if data\nis retransmitted (overlay data = yes) or additional results received.\n \nVERSION 5.2.\n LRLLS [LR*5.2*221]- Clear instrument data option that does actual\nclearing based on user's parameters. User can purge by date/time or\nblanket purge when using Clear instrument/worklist data [LRINSTCLR]\noption.\n \n LRVR1 [LR*5.2*221]- Verifying routine with changes to setup date/time\ninformation when manual data entry is used during Enter/Verify Automated\nInstrument [LRVR] option.\n \n LRVRW [LR*5.2*221]- Verifying routine with changes to setup date/time\n \ninformation when load/work list data entry is used during the Enter/verify\ndata (Work list) [LRVRW] option.\n \n \n \nInstallation Instructions:\n==========================\n \nRequired Patch Installation List:\nLA*5.2*27\n\n
\nVISTA Laboratory Package patch LA*5.2*51 contains no changes to software\n \n - All Lab LEDI (LA7V*) related HL v1.6 LLPs should be shutdown.\n These LLPs are name spaced LA7V* when viewed in the HL package\n Systems Link Monitor [HL MESSAGE MONITOR] option.\n \n \nNOTE: Kernel, MailMan and HL patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\nWith the release of patch HL*1.6*57 several changes need to be made to the\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \nLab LEDI Setup [LA7V SETUP] option. Patch LA*5.2*51 will make the following\n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\nchanges to allow Lab LEDI HL7 interfaces to continue to function.\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. Perform the following step if applicable:\n \n \n All Lab LEDI (LA7V*) related HL v1.6 LLPs should be shutdown.\n Use Start/Stop Links [HL START] option to shutdown these LLPs if\n they are running.\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*51'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'YES'.\n \n Disable the LEDI Setup [LA7V LEDI] option by having KIDS mark the\n 1. The patch removes references to HL LOWER LEVEL PROTOCOL PARAMETER file\n option 'Out Of Order'.\n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LA51 will be deleted after successful patch installation.\n\n\nPost-Installation Instructions:\n \n \n (#869.2) by the LEDI Setup [LA7V SETUP] option.\n1. Restart any LA7V* LLPs that were shutdown before patch installation.\n Use Start/Stop Links [HL START] option.\n \n \n\n************************************************************************ \n \nInstallation example: \n \nSelect Installation Option: 6 Install Package(s)\n \nSelect INSTALL NAME: LA*5.2*51 Loaded from Distribution 3/3/00@14:53:29\n => LA*5.2*51\n \nThis Distribution was loaded on Mar 03, 2000@14:53:29 with header of\n LA*5.2*51\n It consisted of the following Install(s):\n LA*5.2*51\nChecking Install for Package LA*5.2*51\nWill first run the Environment Check Routine, LA51\n \n 2. The post-install deletes entries with the LA7V* namespace from the\n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*51\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n HL LOWER LEVEL PROTOCOL PARAMETER file (#869.2). This file is no longer\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES//\n \nEnter options you wish to mark as 'Out Of Order': LA7V SETUP LEDI Setup\n \nEnter options you wish to mark as 'Out Of Order':\n \nEnter protocols you wish to mark as 'Out Of Order':\n \nDelay Install (Minutes): (0-60): 0//\n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n used by the Health Level Seven (HL) software to store communication\nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*51 :\n Mar 03, 2000@15:18:43\n \n parameters. This data has been moved to the HL LOGICAL LINK file (#870)\nBuild Distribution Date: Mar 03, 2000\n \n Installing Routines:\n Mar 03, 2000@15:18:44\n \n Running Pre-Install Routine: PRE^LA51\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n by patch HL*1.6*57.\n \n --- No actions required for pre install ---\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION\n Mar 03, 2000@15:18:46\n \n \n Running Post-Install Routine: POST^LA51\n \n *** Post install started ***\n \n *** Checking PROTOCOL file #101 ***\n \n *** for incorrectly named protocols LA7V Order from XXX. ***\n \n *** Changing these to LA7V Order to XXX when appropriate. ***\n \n 3. The post-install changes the name of protocol LA7V Order from xxx to\n *** Also deleting unused LA7V protocols. ***\n \n --- Updated 53 entries in PROTOCOL file #101 ---\n \n *** Checking HL LOWER LEVEL PROTOCOL PARAMETER file #869.2 ***\n \n *** for LA7V* entries that are no longer used. ***\n \n --- Deleted 9 entries in HL LOWER LEVEL PROTOCOL PARAMETER file #869.2 ---\n \n LA7V Order to xxx in the PROTOCOL file (#101), where xxx is the VA\n *** Converting and updating existing LA7V* protocols ***\n \n Updating/converting protocol LA7V Order to 535\n \n Updating/converting protocol LA7V Order to 578\n \n Updating/converting protocol LA7V Order to 607\n \n Updating/converting protocol LA7V Process Order from 535\n \n station number that an order message (ORM) is being sent to.\n Updating/converting protocol LA7V Process Order from 556\n \n Updating/converting protocol LA7V Process Order from 578\n \n Updating/converting protocol LA7V Process Order from 585\n \n Updating/converting protocol LA7V Process Order from 607\n \n Updating/converting protocol LA7V Process Order from 676\n \n The protocol was incorrectly named which could be confusing.\n Updating/converting protocol LA7V Process Order from 695BY\n \n Updating/converting protocol LA7V Process Results from 535\n \n Updating/converting protocol LA7V Process Results from 578\n \n Updating/converting protocol LA7V Process Results from 607\n \n Updating/converting protocol LA7V Receive Order from 556\n \n \n Updating/converting protocol LA7V Receive Order from 578\n \n Updating/converting protocol LA7V Receive Order from 585\n \n Updating/converting protocol LA7V Receive Order from 607\n \n Updating/converting protocol LA7V Receive Order from 676\n \n Updating/converting protocol LA7V Receive Order from 695BY\n \n 4. The post-install deletes protocols that were previously setup by the\n Updating/converting protocol LA7V Receive Results from 535\n \n Updating/converting protocol LA7V Receive Results from 578\n \n Updating/converting protocol LA7V Receive Results from 607\n \n Updating/converting protocol LA7V Results Reporting to 556\n \n Updating/converting protocol LA7V Results Reporting to 578\n \n \n LEDI Setup option but which are presently not being used.\n Updating/converting protocol LA7V Results Reporting to 585\n \n Updating/converting protocol LA7V Results Reporting to 607\n \n Updating/converting protocol LA7V Results Reporting to 676\n \n Updating/converting protocol LA7V Results Reporting to 695BY\n \n Updating/converting protocol LA7V Send Order to 535\n \n If protocols are found with the following names they will be deleted:\n Updating/converting protocol LA7V Send Order to 578\n \n Updating/converting protocol LA7V Send Order to 607\n \n Updating/converting protocol LA7V Send Results to 535\n \n Updating/converting protocol LA7V Send Results to 556\n \n Updating/converting protocol LA7V Send Results to 578\n \n LA7V Query Response to xxx\n Updating/converting protocol LA7V Send Results to 585\n \n Updating/converting protocol LA7V Send Results to 607\n \n Updating/converting protocol LA7V Send Results to 676\n \n Updating/converting protocol LA7V Send Results to 695BY\n \n --- Converted and updated 38 LA7V* entries in PROTOCOL file #101 ---\n \n LA7V Query for Results from xxx\n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LA*5.2*51 Installed.\n Mar 03, 2000@15:18:53\n LA7V Receive Query from xxx\n \n Install Message sent #18145\n \n \n \nInstall Completed\n LA7V Send Query to xxx\n LA7V Send Response to xxx\n LA7V Order Response to xxx\n (where xxx is the VA station number)\n \n \n 5. The post-install converts and updates existing LA7V* protocols to\n conform to the new rules introduced by patch HL*1.6*57.\n \n 6. The patch changes the LEDI Setup option to create protocols based on\n the rules implemented with patch HL*1.6*57.\n \n \n \nASSOCIATED NOIS\n---------------\nNOTE: PATCH HL*1.6*57 MUST BE INSTALLED PRIOR TO INSTALLATION OF THIS PATCH.\n DUB-0300-30697 \n MUS-0200-71248\n PRE-0200-61136\n \n \nTEST SITES\n----------\n Battle Creek VAMC\n Dublin VAMC\n Indianapolis VAMC\n LA*5.2*51 SHOULD BE INSTALLED IMMEDIATELY FOLLOWING INSTALLATION OF\n Milwaukee VAMC\n Muskogee VAMC\n Prescott VAMC\n West Palm Beach VAMC\n \n \nROUTINE SUMMARY\n===============\n \n The following is a list of routines included in this patch.\n PATCH HL*1.6*57 TO AVOID INTERRUPTION OF LABORATORY ELECTRONIC DATA\n The second line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA51 N/A 16393090 **51**\n INTERCHANGE (LEDI) HL7 MESSAGE TRANSMISSION.\n LA7VLL 14468424 4967061 **27,51**\n LA7VORM1 20938223 20868841 **27,51**\n LA7VSET 29695063 19562009 **27,51**\n LA7VSET1 19867155 12823333 **27,51**\n LA7VSTP 24725864 6154318 **27,44,51**\n \n \n \n************************************************************************ \n \n \nInstallation Instructions\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed with Laboratory users on the system. Recommend\n that the patch be installed during a period of minimum Laboratory\n package activity.\n \n However, the following conditions apply:\n \n\n
\nVISTA Laboratory Package patch LA*5.2*50 contains no changes to software\nfail at the host laboratory facility causing the collecting facility not\n Enter/verify data (auto instrument) [LRVR]\n Enter/verify data (Work list) [LRVRW]\n Enter/verify data (Load list) [LRVRW2]\n Batch data entry (chem, hem, tox, etc.) [LRSTUF]\n Group verify (EA, EL, EW) [LRGV]\n \n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*50'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\nto receive a result message. This problem occurs when the host lab's entry\n choose 'NO'.\n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LA50 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS: NONE\n \n \nfor the collecting facility in the INSTITUTION file (#4) has an internal\n \n \n************************************************************************\nInstallation example:\n\nSelect INSTALL NAME: LA*5.2*50 Loaded from Distribution 1/31/00@15:21:58\n => LA*5.2*50 \n \nThis Distribution was loaded on Jan 31, 2000@15:21:58 with header of \n LA*5.2*50 \nentry number which is different from the VA Station Number. The software\n It consisted of the following Install(s): \n LA*5.2*50 \nChecking Install for Package LA*5.2*50 \nWill first run the Environment Check Routine, LA50 \n \n \n --- Environment Check is Ok --- \n \nInstall Questions for LA*5.2*50 \n \nis assuming that the station number and the internal entry are the same.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? NO// \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO \n \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO \n \n Install Started for LA*5.2*50 : \n Jan 31, 2000@15:25:13 \n \n \nBuild Distribution Date: Jan 31, 2000 \n \n Installing Routines: \n Jan 31, 2000@15:25:14 \n \n Running Pre-Install Routine: PRE^LA50 \n \n Sending install started alert to mail group G.LMI \n \nRoutine LA7VMSG has been changed to retrieve the VA Station Number from\n *** Pre install started *** \n \n --- No actions required for pre install --- \n \n *** Pre install completed *** \n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION \n Jan 31, 2000@15:25:14 \nthe INSTITUTION file for the collecting facility's entry when the station\n \n Running Post-Install Routine: POST^LA50 \n \n *** Post install started *** \n \n --- No actions required for post install --- \n \n *** Post install completed *** \n \n Sending install completion alert to mail group G.LMI \nnumber is used in building the result (ORU) message.\n \n Updating Routine file... \n \n Updating KIDS files... \n \n LA*5.2*50 Installed. \n Jan 31, 2000@15:25:16 \n \n \n \n \nInstall Completed \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n \n\nASSOCIATED NOIS\n---------------\n WPB-1199-31232\n \n \nTEST SITES\n----------\n West Palm Beach VAMC\n \n Miami VAMC\n \n \nROUTINE SUMMARY\n===============\n \n The following is a list of routines included in this patch.\n The second line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994\n \n \n CHECK^XTSUMBLD results\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA50 N/A 4543400 **50**\n LA7VMSG 22591788 22442510 **27,50**\n \n \nDESCRIPTION\n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n However the following conditions apply:\n \n===========\n - All Laboratory test verification should be suspended. The install\n will disable lab verifying options during installation.\n \n \nNOTE: Kernel, MailMan and HL7 patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n\n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\nWhen the Lab LEDI software needs to build a HL7 message to return lab \n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\ntest results (ORU) to the collecting facility, the message building could\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab verifying options during\n patch installation.\n \n\n
\nThis patch to the Laboratory package does not contain any changes to the\n Solution: The code has been validated, brought up to national\n============================\nVAMC's are encouraged to use their FTP capability to obtain the\nDocumentation PDF files from one of the following OI Field Office's\nANONYMOUS directories. \n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== ==========\n HINES 152.129.1.110 [ANONYMOUS.SOFTWARE]\n SALT LAKE CITY 152.131.2.1 [ANONYMOUS.SOFTWARE]\n ALBANY 152.127.1.5 [ANONYMOUS.SOFTWARE]\n standard and released as a Class I national patch.\n \n File names are: \n \n BINARY FILES\n LA7DIG.PDF -- CareVue Installation Guide\n LA7DIS.PDF -- CareVue Interface Specifications\n LA7DTP.PDF -- CareVue Interface Test Plan\n \nThe CareVue interface utilizes VISTA'S Laboratory Test Result system to\nsend Observation Request Unsolicited (ORU) messages to the CareVue system.\n \nThe interface messages are based on ward location and passed to an\ninterface engine. When Lab results are verified and the requesting ward\nis identified as having a supported entry in the new CareVue Foreign\nInterface file #62.487, the lab results are forwarded, via HL7, to the\ninterface engine and then on to the CareVue Clinical Information\nManagement System.\n \nEach facility will need to refer to the CareVue Interface Specifications\nmanual LA7DIS.PDF as noted above for further requirements regarding\ninterface engines.\nThis patch REQUIRES that patch LR*5.2*254 be installed in order for the\n \nINSTALLATION INSTRUCTIONS\n==========================\nThe patch is distributed in KIDS format in a PackMan message.\nIt is recommended that this patch be installed in a test environment first\nbefore installing into production. Each environment (test and production)\nuses a separate database and a separate integration interface. Because of\nthis the data that is communicated from VistA may not always be consistent\nwith the data that will be communicated from the production environment.\nAnother impact is that patient data may have to be manually entered into\nCareVue interface to work properly.\nthe VistA test environment in order to test the proper handling of\nmessages going to VistA.\n \nThe install time for this patch is less than 2 minutes. This patch can be\ninstalled when Laboratory users are on the system.\n \n1. All routines installed with this patch are new to the system and \n mapping is not recommended.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. \n \n This option will load the KIDS patch onto your system.\n \n3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the transport \n global.\n \n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\nAn interface engine must exist to connect CareVue (or other clinical\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n4. Use the 'Install Package(s)' option under the 'Installation' men\n and select the package 'LA*5.2*53'. When prompted 'Want to \n DISABLE Scheduled Options, Menu Options, and Protocols? YES//', \n choose 'NO'.\n \n5. At the DEVICE prompt, you can send your output to any printer of\n HFS file, display it on the terminal screen, or queue it to run \nsystem) and Vista using TCP/IP and HL7 messages. Three possible contacts\n at a scheduled time.\n \n6. No options need to be placed out of service.\n \n7. This installation automatically adds the two new protocols to \n the PROTOCOL file (#101). They are: LA7D CARELIFE RESULTS\n LA7D CARELIFE SERVER\n \n8. User will need to enter your facility name in the HL7 \n APPPLICATION PARAMETER file (#771).\nfor this interface engine are STC, Inc. MSI Solutions Inc. and Agilent\n \nNOTE: Fields marked with <-- below need to have information entered.\n \nSelect OPTION: ENTER OR EDIT FILE ENTRIES <-- \nINPUT TO WHAT FILE: FOREIGN INTERFACE// HL7 APPLICATION PARAMETER <-- \n (34 entries)\nEDIT WHICH FIELD: ALL// FACILITY NAME <-- \nTHEN EDIT FIELD: <RET>\nSelect HL7 APPLICATION PARAMETER NAME: DHCP CARELIFE ACTIVE <--\nFACILITY NAME: 428// 428 enter your facility name here <--\nTechnologies.\nSelect HL7 APPLICATION PARAMETER NAME: MRTS CARELIFE ACTIVE <--\nFACILITY NAME: 642// 428 enter your facility name here <--\nSelect HL7 APPLICATION PARAMETER NAME: <RET>\n \n9. The new mail group CARELIFE RESULT ERROR was created as part of \n the installation. However the entry in the MAIL GROUP file (3.8)\n is only a stub and requires the site to perform the following edit:\n \nNOTE: Fields marked with <-- below need to have information entered.\n \nVISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled VISTA\n \nSelect MAIL GROUP NAME: CARELIFE RESULT ERROR <-- \nNAME: CARELIFE RESULT ERROR Replace \nSelect MEMBER: CROSS,PAM <--\n Are you adding 'CROSS,PAM' as a new MEMBER (the 1ST for this MAIL\nGROUP)\n? No// Y (Yes) <--\n TYPE: \nSelect MEMBER: <RET>\nDESCRIPTION:\n No existing text\nSTC, Inc. can be contacted at:\n Edit? NO// YES <--\n All error report for CAREVUE ORU Messages <--\n \nTYPE: public// PUBLIC <--\nORGANIZER: CROSS,PAM <--\nCOORDINATOR: CROSS,PAM <--\nSelect AUTHORIZED SENDER: \nALLOW SELF ENROLLMENT?: NO// NO <--\nREFERENCE COUNT: <RET>\nLAST REFERENCED: <RET>\n Richard Garcia\nRESTRICTIONS: INDIV/LOCAL/ORGANIZER// <RET>\nSelect MEMBER GROUP NAME: <RET>\nSelect REMOTE MEMBER: <RET>\nSelect DISTRIBUTION LIST: <RET>\nSelect FAX RECIPIENT: <RET>\nSelect FAX GROUP: <RET>\n \nSelect MAIL GROUP NAME: <RET>\n \n10. The FOREIGN INTERFACE file (#62.487) was put on the system during\n voice: 626.471.6000 x6755\n the installation process but it does not contain any data. You\n must enter your site's data concerning your CareVue wards. This\n option will need to be added to users secondary menus under the\n namespace LA7D.\n \nNOTE: Fields marked with <-- below need to have information entered.\n \nSelect MailMan Menu Option: Edit Foreign Interface Parameters \nEnter BEDSIDE MONITOR INTERFACE NAME: CAREVUE <-- \nEnter CAREVUE WARD: ICU <-- enter your CareVue wards here\n fax: 626.471.6104\nEnter CAREVUE WARD: ADMISSIONS <-- \nEnter CAREVUE WARD: ^\n \n **NOTE** \n All wards in the hospital location file (#44) that will be\n used for the CareVue interface must have a UNIQUE abbreviation for\n each ward (Inactive and Active)\n \n11. Set up Logical Link for HL7 parameters. This will need to contain\n the outgoing device name used from VistA to the interface engine.\n email: rmg@stc.com\n Sites should ensure that entries corresponding to their unique\n system requirements be input at the recommended places.\n \nNOTE: Fields marked with <-- below need to have information entered.\n \nSelect Systems Manager Menu Option: HL7 Main Menu\n \nSelect HL7 Main Menu Option: V1.6 OPTIONS\n \nSlect V1.6 OPTIONS Option: Interface Workbench\n \nAt the bottom of the screen you will see:\n \nSelect Tool: Jump to Next App// SL Show Logical Links\nSelect Tool: Jump to Next Link// CL Create Logical Link\n \nSelect HL LOGICAL LINK NODE: VOICE1 <--\n \nLogical Link information\n------------------------\nQueue Size: 245 <--\nMSI Solutions, Inc. can be contacted at:\nLLP Parameter: HLLP <--\n \nLLP Parameters\n--------------\nLLP Type: HLLP <--\nDevice: OG_LAB_PROD <-- this will be your device name\nVersion ID: 2.3 <--\nBlock Size: 245 <--\nRead Timeout: 30 <--\nACK Timeout: 2 <--\n Bob Kelliher\nRe-transmission Attempts: 3 <--\nStart Block Character: <RET>\nEnd Block Character: <RET>\n \nSelect Tool: Jump to Next Link// ^\n \nNOTE: Add the Logical Link just created to the LA7D CARELIFE\n RESULTS protocol.\n \nNOTE: Fields marked with <-- below need to have information entered.\n voice: 678.256.4505\n \nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n \nINPUT TO WHAT FILE: PROTOCOL// PROTOCOL <-- (3569 entries)\nEDIT WHICH FIELD: ALL// NAME <--\nTHEN EDIT FIELD: LOGICAL LINK <--\nTHEN EDIT FIELD: \n \nSelect PROTOCOL NAME: LA7D CARELIFE RESULTS <--\n This client is tied to the MRTS CARELIFE entry\nBLOOD BANK SOFTWARE.\n fax: 678.256.4677\nNAME: LA7D CARELIFE RESULTS Replace <RET>\nLOGICAL LINK: OG_LAB_PROD <-- Enter your Logical Link that was set up\n \n12. Follow the Interface Specifications Manual LA7DIS.PDF for\n interface engine requirements.\n \n13. Follow the CareVue Test Plan Manual LA7DTP.PDF to test the CareVue\n package.\n email: bob.kelliher@msi-solutions.com\n \nAgilent Technologies can be contacted at:\n Linda Vanderhulst\n voice: 847.342.2521\n email: linda_vanderhulst@agilent.com\n \nAbout this software:\n====================\n \n1. An option to enter/delete supported wards for the FOREIGN \n INTERFACE file (#62.487) is exported with this version of the patch.\n \n **NOTE** \n All wards in the hospital location file (#44) that will be\n used for the CareVue interface must have a UNIQUE abbreviation for\n each ward (Inactive and Active)\n \n2. Resulting from this installation, the entries DHCP CARELIFE and\n MRTS CARELIFE will automatically be added to the HL7 APPLICATION \nThis patch will install the CareVue interface package under the Namespace\n PARAMETER file (#771). These entries will be used to send HL7\n messages to the CareVue system. These parameters also need to be\n edited to enter your facility name.\n \n3. The following file is included in this release. It is in the LA7D\n namespace, also listed in the main installation procedure:\n \n File #62.487 File name FOREIGN INTERFACE\n \n4. The following mail group will be automatically added to the MAIL\nLA7D as a Class I national patch.\n GROUP file (#3.8) during this installation: CARELIFE RESULT ERROR\n \n5. This installation automatically adds the two new protocols to the\n PROTOCOL file (#101). They are: LA7D CARELIFE RESULTS\n LA7D CARELIFE SERVER\n \n6. Sites will need to set up a Logical Link for HL7 parameters.\n \n7. The routines exported with this release, listed in the Routines \n section of this document, are customized to send verified \n \n Laboratory data to CareVue for all patients located on a CareVue \n ward.\n \n \n Associated NOIS\n ===============\n None\n \n Test Sites\n =============== \n1. Problem: Current CareVue interface is Class III software.\n Philadelphia, PA\n Martinsburg, WVA\n \n ROUTINE SUMMARY\n =================\n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n \n CHECK^XTSUMBLD Results\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA7DVC NEW 7338732 53\n LA7DVEXT NEW 5483063 53\n LA7DVM NEW 6983644 53\n LA7DEDT NEW 3756680 53\n \n \nCareVue installation manuals\n\n
\nVISTA Laboratory Package patch LA*5.2*55 contains no changes to software\nvia the MailMan transmission protocol. This occurs when the entry in the\n patch installation.\n \n LEDI Setup [LA7V SETUP]\n \n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*55'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \nINSTITUTION file (#4) has an internal entry number which is different\n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LA55 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS: NONE\n \n \n \n \nfrom the VA Station Number. The software is assuming that the station\n************************************************************************\nInstallation example: \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*55 Loaded from Distribution 4/13/00@10:16:44\n => LA*5.2*55\n \nThis Distribution was loaded on Apr 13, 2000@10:16:44 with header of\n LA*5.2*55\n It consisted of the following Install(s):\nnumber and the internal entry are the same.\n LA*5.2*55\nChecking Install for Package LA*5.2*55\nWill first run the Environment Check Routine, LA55\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*55\n \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nRoutines LA7VLL, LA7VSET, and LA7VSET1 have been changed to use the\nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*55 :\n Apr 13, 2000@10:17:32\n \nBuild Distribution Date: Apr 13, 2000\n \n Installing Routines:\n Apr 13, 2000@10:17:32\ninternal entry number from the INSTITUTION file when retrieving the DOMAIN\n \n Running Pre-Install Routine: PRE^LA55\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n *** Pre install completed ***\nfield from the INSTITUTION file.\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION\n Apr 13, 2000@10:17:32\n \n LA*5.2*55\n \n Running Post-Install Routine: POST^LA55\n \n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \nThe patch also corrects the misspelling of the word "transmissions" in \n Updating KIDS files...\n \n LA*5.2*55 Installed.\n Apr 13, 2000@10:17:34\n \n Install Message sent #21510\n \n \nInstall Completed\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nroutines LA7VSET and LA7VSET1.\n \n \nASSOCIATED NOIS\n---------------\n CHA-0300-32805 \n \nTEST SITES\n----------\n \n \n Charleston VAMC \n \n \nROUTINE SUMMARY\n===============\n \n The following is a list of routines included in this patch.\n The second line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994\n \n \n CHECK^XTSUMBLD results\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA55 N/A 4557897 **55**(deleted by KIDS)\n LA7VLL 4967061 5170411 **27,51,55**\n LA7VSET 19562009 19500034 **27,51,55**\n LA7VSET1 12823333 12858976 **27,51,55**\nDESCRIPTION\n \n\n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n===========\n Suggested time to install: non-peak requirement hours.\n However the following conditions apply:\n \n - The install will disable LEDI Setup option during installation.\n \n \nNOTE: Kernel and MailMan patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n \n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\nThe LEDI Setup option [LA7V SETUP] fails to add the member S.HL V16\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\nSERVER@remote mail domain to the mail group used to transmit HL7 messages\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab verifying options during\n\n
\nVISTA Laboratory Package patch LA*5.2*56 contains no changes to software\nfail at the host laboratory facility with the error undefined variable\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \nLA("I") in routine PID+4^LA7VORU causing the collecting facility not\n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\nto receive a result message. This problem occurs when the host lab's entry\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab verifying options during\n patch installation.\n \n Enter/verify data (auto instrument) [LRVR]\n Enter/verify data (Work list) [LRVRW]\nfor the collecting facility in the INSTITUTION file (#4) has an internal\n Enter/verify data (Load list) [LRVRW2]\n Batch data entry (chem, hem, tox, etc.) [LRSTUF]\n Group verify (EA, EL, EW) [LRGV]\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*56'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 9. On a mapped system, rebuild your map set.\nentry number which is different from the VA Station Number and the \n \n 10. Routine LA56 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS: NONE\n \n \n \n \n************************************************************************\ncollecting facility is a division of an integrated facility. The software\nInstallation example: \n \nSelect INSTALL NAME: LA*5.2*56 Loaded from Distribution 4/10/00@14:57:02\n => LA*5.2*56\n \nThis Distribution was loaded on Apr 10, 2000@14:57:02 with header of \n LA*5.2*56\n It consisted of the following Install(s): \n LA*5.2*56 \nChecking Install for Package LA*5.2*56 \nis attempting to return the results to the collecting facility instead of\nWill first run the Environment Check Routine, LA56 \n \n \n --- Environment Check is Ok --- \n \nInstall Questions for LA*5.2*56 \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO \n \nthe primary facility's computer system. If no associated HL7 protocol was\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO \n \nEnter the Device you want to print the Install messages. \nYou can queue the install by enter a 'Q' at the device prompt. \nEnter a '^' to abort the install. \n \nDEVICE: HOME// TELNET VIRTUAL \n \nidentified message building was continuing with the HL7 and Lab environment\n \n \n Install Started for LA*5.2*56 : \n Apr 10, 2000@14:57:45 \n \nBuild Distribution Date: Apr 10, 2000 \n \n Installing Routines: \n Apr 10, 2000@14:57:45 \n \nnot properly initialized. The software would error when it referenced \n Running Pre-Install Routine: PRE^LA56 \n \n Sending install started alert to mail group G.LMI \n \n *** Pre install started *** \n \n --- No actions required for pre install --- \n \n *** Pre install completed *** \n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nvariable LA("I") that was not defined during this initialization.\n Installing PACKAGE COMPONENTS: \n \n Installing OPTION \n Apr 10, 2000@14:57:45 \n \n Running Post-Install Routine: POST^LA56 \n \n *** Post install started *** \n \n --- No actions required for post install --- \n \n \n *** Post install completed *** \n \n Sending install completion alert to mail group G.LMI \n \n Updating Routine file... \n \n Updating KIDS files... \n \n LA*5.2*56 Installed. \nRoutine LA7VMSG has been changed to retrieve the VA Station Number from\n Apr 10, 2000@14:57:46 \n \n \n \n \nInstall Completed \nthe INSTITUTION file for an integrated collecting facility's primary\nsystem entry when the station number is used in building the result (ORU)\nmessage.\n \n2. Routine LA7VMSG has been changed to determine if a link back to the \nintegrated facility's primary system does not exist. If a link does not\nexist, the results are returned via the collecting facility.\n \n \n3. Routine LA7VMSG has been split into two routines (LA7VMSG and LA7VMSG1)\nbecause it exceeded the maximum routine size of 10k as specified by the SAC. \n \n4. Recording of an error condition in the Lab Messaging Error Log has been \nadded when the software is unable to find the appropriate entry in the\nPROTOCOL file (#101) to use in building the HL7 message. This can occur\nwhen no entry is found in the PROTOCOL file or the HL7 package is unable to\ninitialize the HL7 message environment for message building. The error that\nwill be recorded is #28 in LA7 MESSAGE LOG BULLETINS file (#62.485).\n \nThe error text will be:\n Msg # |1| encountered the following HL7 generation error: |2|.\n\n where |1| is the LA7 MESSAGE QUEUE file (#62.49) entry number\n |2| is the conditions:\n 1. Invalid/undefined protocol xxx\n 2. Call to INIT^HLFNC2 failed for protocol xxx\n xxx - being the name of the protocol in the PROTOCOL file.\n \n \nDESCRIPTION\n\nASSOCIATED NOIS\n---------------\n CON-0400-10572\n \n \nTEST SITES\n----------\n Connecticut HCS\n Boston HCS \n===========\n \n \nROUTINE SUMMARY\n===============\n \n The following is a list of routines included in this patch.\n The second line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994\n \n \n CHECK^XTSUMBLD results\n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA56 N/A 4543424 **56**(Deleted by KIDS)\n LA7VMSG 22442510 16357149 **27,50,56**\n LA7VMSG1 N/A 3358807 **56**\n \n \n \n1. When the Lab LEDI software needs to build a HL7 message to return lab\n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours. Verification\n of lab test results should be suspended. The install will disable\n several Lab verifying options as specified in #7 below.\ntest results (ORU) to the collecting facility, the message building could\n \n \nNOTE: Kernel, MailMan and HL7 patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n\n\nVISTA Laboratory Package patch LA*5.2*52 contains no changes to software\nRoutine LAKDIFF3 was changed to kill variable LRORD before calling\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA52 N/A 4557885 **52**(Deleted by KIDS)\n LAKDIFF 9922081 7244730 **13,52**\n LAKDIFF1 8917764 5795474 **52**\n LAKDIFF2 9640378 2778086 **52**\n LAKDIFF3 2515859 1523847 **52**\n \nEXPLODE^LRGP2 to build the list of tests on the work list. Users would\n************************************************************************\n \nInstallation Instructions\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed with Laboratory users on the system.\n \n Suggested time to install: non-peak requirement hours.\n Recommend that the patch be installed when option Keypad differential\nencounter an undefined error when attempting to select a second or\n for CRT's [LA KB DIFF] is not being used.\n \nNOTE: Kernel, MailMan and HL patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC). Patch will send patch installation\n alerts to Lab mail group LMI.\n \n \nsubsequent accession because the array LRORD was not cleaned up after\n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\nprocessing the first accession.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nNOIS: CON-0899-12137, FAV-0899-71050, FRE-1099-60326, HAM-0899-20524,\n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab option during patch\n installation.\n \n Keypad differential for CRT's [LA KB DIFF]\n SLC-0999-50329, WAS-1299-21602\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*52'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LA52 will be deleted after successful patch installation.\n \n \n \n \nPost-Installation Instructions: NONE\n \n************************************************************************\n \nInstallation example:\n \n \nSelect Installation Option: 6 Install Package(s)\n2. This patch fixes a reported illegal number error at WLN^LAKDIFF.\nSelect INSTALL NAME: LA*5.2*52 Loaded from Distribution 8/1/00@16:13:41\n => LA*5.2*52\n \nThis Distribution was loaded on Aug 01, 2000@16:13:41 with header of\n LA*5.2*52\n It consisted of the following Install(s):\n LA*5.2*52\nChecking Install for Package LA*5.2*52\nWill first run the Environment Check Routine, LA52\n \n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*52\n \nIncoming Files:\n \n \n 8989.51 PARAMETER DEFINITION (including data)\nNote: You already have the 'PARAMETER DEFINITION' File.\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nRoutine LAKDIFF was changed to use a DIR call to allow the user to\nI will OVERWRITE your data with mine.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nselect the accession number. This call will prevent the user from\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*52 :\n Aug 01, 2000@16:15:36\n \nBuild Distribution Date: Aug 01, 2000\n \nentering a number that is outside the range of possible accession\n Installing Routines:......\n Aug 01, 2000@16:15:36\n \n Running Pre-Install Routine: PRE^LA52.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\nnumbers (1-9999999) or contains a decimal.\n \n *** Pre install completed ***\n \n Installing Data Dictionaries: ..\n Aug 01, 2000@16:15:36\n \n Installing Data: ..\n Aug 01, 2000@16:15:40\n \n Installing PACKAGE COMPONENTS:\nNOIS: MAD-1295-40263, SLC-0696-50890\n \n Installing OPTION..\n Aug 01, 2000@16:15:41\n \n Running Post-Install Routine: POST^LA52.\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*52 Installed.\n Aug 01, 2000@16:15:50\n3. It corrects the following Vista Programming Standards and Conventions\n \n Install Message sent #28235\nviolations that were observed in routines LAKDIFF, LAKDIFF1, LAKDIFF2,\nand LAKDIFF3 during a software review as part of patch development:\n \n \n a. Removed direct global read of global ^%ZIS(2) which contains the\n TERMINAL TYPE file. Routine LAKDIFF was retrieving code to set\n cursor positioning. Call changed to use Kernel supplied supported\n references PREP^XGF.\n \n b. Removed user input READS which were not terminated by a carriage\n return. These were converted to use the Kernel supplied supported\n references READ^XGF.\n \n c. Removed direct global references to the DD global. These were\nThis patch fixes several reported errors and corrects several Vista\n converted to FileMan supplied supported references ^DI\n \n d. Variable DTIME was being set but was not documented in Technical\n manual. Changed setting of DTIME to Kernel supported reference\n $$DTIME^XUP.\n \n4. Users are now allowed to select the accession date. Previously the\nsoftware defaulted to the current date.\n \n5. When displaying the CBC profile the software previously only displayed\nProgramming Standards and Conventions (SAC) violations.\nverified results from FILE LAB DATA (#63). The software will now display\nany unverified results that have been entered on the work list.\nThese results are preceded with an "*" to denote the status of unverified.\n \n6. When determining the number of days back for delta checking the \nsoftware was using 60 days. This patch changes the logic to calculate the\nnumber of days back for delta checks by using the value the site specifies\nin FILE LABORATORY SITE (#69.9), FIELD DAYS BACK FOR DELTA CHECKS (#20).\n \n7. The user can now select if the cell differential and RBC morphology\n \ndisplay updates on each key press. The user is prompted if they want the\ndisplay updated with each key press upon entering the option. If the user\nselects NO then the display can be updated by entering a "?" during cell\ndifferential and RBC morphology entry. Selecting YES provides a continuously\nupdating display. On systems with slow response times, selecting NO may\nimprove performance. User's preferences for this function will be saved\nusing Kernel's generic parameter utility. The parameter definition is named\nLA KDIFF DISPLAY UPDATE which will be added to the PARAMETER DEFINITION\nfile (#8989.51) by the KIDS install.\n \n1. This patch fixes a reported undefined variable error occurring at\n\nASSOCIATED NOIS\n---------------\n CON-0899-12137\n FAV-0899-71050\n FRE-1099-60326\n HAM-0899-20524\n MAD-1295-40263\n PHI-0300-21262\n SLC-0696-50890\nLAKDIFF3+10^LAKDIFF3.\n SLC-0999-50329\n WAS-1299-21602\n \nTEST SITES\n----------\n Connecticut HCS\n Fresno VAMC\n Hampton VAMC\n Philadelphia VAMC\n \n \n \nROUTINE SUMMARY\n===============\n \n The following is a list of routines included in this patch.\n The second line of each routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n\n
\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patches LA*5.2*58 and\n RISK ANALYSIS: Changes made by patches LA*5.2*58 and LR*5.2*266 have no\n \nAssociated NOIS\n===============\nMIA-0600-30434\nMWV-0900-21094\n \nTest Sites\n==========\nMartinsburg, West Virginia\n \neffect on Blood Bank software functionality, therefore RISK is none.\n \nROUTINE SUMMARY\n=================\nThe following is a list of routines included in patch LA*5.2*58. The\nsecond line of each routine now looks like:\n \n<tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD Results\n Routine Name Before Patch After Patch Patch List\n \n ------------ ------------ ----------- ------------\n LA7DEDT 3765930 5836716 53,58\n LA7DLOC NEW 553499 58\n LA7DVM 6983644 6949969 53,58\n \n \nThe following is a list of routines included in patch LR*5.2*266. The\nsecond line of each routine now looks like:\n \n<tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n**NOTE**\n CHECK^XTSUMBLD Results\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR266 NEW 1529899 266\n LRMIUT 3673249 3951633 254,266\n LRVER3A 10780812 10508599 1,5,42,100,121\n 153,190,221,254,\n 263,266\n \n \n \nThe documentation and distribution files for patches LA*5.2*58 and\nLR*5.2*266 may be obtained using FTP from the appropriate National VistA\nSupport directory:\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== ==========\n HINES 152.129.1.110 [ANONYMOUS.SOFTWARE]\n SALT LAKE CITY 152.131.2.1 [ANONYMOUS.SOFTWARE]\n ALBANY 152.127.1.5 [ANONYMOUS.SOFTWARE]\n \nPatches LA*5.2*58 and LR*5.2*266 are being released in a single\nFile names are:\n \n ASCII FILE\n LA_52_P58.KID - KIDS distribution for LA*5.2*58 and LR*5.2*266\n \n BINARY FILE\n LA7DIG.PDF - CareVue Installation Guide\n \nINSTALLATION INSTRUCTIONS\n=========================\ndistribution. Because of this, patch descriptions for LA*5.2*58 and\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\nLR*5.2*266 are identical and contain routine summaries for both sets of\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n 1. Review your mapped set. If any of the routines listed in\n patches LA*5.2*58 or LR*5.2*266 are mapped, they should be\n removed from the mapped set at this time.\n \n 2. From the Kernel Installation & Distribution System menu (XPD\n MAIN), select the Installation menu option, then the option,\nroutines.\n Load a Distribution. Enter your directory name and\n LA_52_P58.KID at the Host File prompt.\n \n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the \n Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n \n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. It is recommended that this release be installed during off\n peak hours. To prevent a possible problem with the tasking\n of the next days laboratory orders, do not install this package\n at the same time as the following nightly tasked jobs:\n \n LRTASK ROLLOVER\nLR*5.2*266 do not contain any changes to the VISTA BLOOD BANK Software as\n**NOTE**\n LRTASK NIGHTLY\n LRTASK CONJAM\n LRTASK CUM\n \n 5. No options need to be placed out of service.\n \n 6. Installation time is less than 2 minutes during off peak \n hours and less than 5 minutes during peak hours\n \n 7. From the 'Installation Menu' of the KIDS menu, run the \n \n option 'Install Package(s)' Select the package 'LA*5.2*58'\n and proceed with the install. When prompted 'Want to \n DISABLE Scheduled Options, Menu Options, and Protocols? \n YES//', choose 'NO'.\n \n 8. This patch updates the Processing RTN field (#771) and the\n Response Processing RTN field (#772) of the Protocol file\n (#101) for the LA7D CARELIFE RESULTS and LA7D CARELIFE SERVER\n entries. The letter "Q" will be entered by the post-init\n routine LR266 if no entry exists. The LR266 routine will\nThe laboratory routines LRVER3A and LRMIUT are being modified by this\n automatically be deleted after the patch is installed.\n \n 9. If any routines were unmapped as part of step 2, they \n should be returned to the mapped set once the installation \n has run to completion.\npatch. These routines may have been locally modified at the sites. The\nsites must ensure that precautions are taken to prevent loss of local\nmodifications when patches to Laboratory are installed.\n \n**NOTE**\n \nWhen initially setting up the FOREIGN INTERFACE file (#62.487), the\ndefined by VHA DIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION\nFOREIGN COMPUTER INTERFACE NAME field (#.01) should ALWAYS be set to\n"CAREVUE" (all caps, no leading or trailing spaces, and no quotes). The\nroutines that access this file are looking specifically for CAREVUE. The\nroutines will not be able to process the results for CareVue ward patients\nif this is not done.\n \nThis patch contains changes to Class I CareVue code and requires that\npatch LA*5.2*53 and LR*5.2*263 be installed before LA*5.2*58. Patches\nLA*5.2*58 and LR*5.2*266 are contained in the same KID file\n(LA_52_P58.KID) and will be installed together.\n5.2.\n \nThis patch includes the following changes:\n \n1. This patch updates the documentation released with the CareVue\nInterface patch (LA*5.2*53).\n \n2. This patch makes changes to the routines LRVER3A and LRMIUT, and will\ncreate a new routine (LA7DLOC). Currently, two routines (LRVER3A and\nLRMIUT) contain the Class I software for the CareVue interface. This patch\nwill modify these routines to call the new routine (LA7DLOC). LA7DLOC\n \ncontains the Class I code for determining if a patient is located in a\nCareVue ward. The current condition of the Class I code checks the CHEM,\nHEM, TOX, RIA, SER, etc. field (#4) and the Microbiology field (#5) of the\nLab Data file (#63), but the updated routines will call LA7DLOC and will\nlook in the Ward Location field (#.1) of the Patient file (#2). This\nshows the current location of the patient. There were problems with\npatients that were not transferred to the CareVue ward until after the lab\norder was taken. The old routine was checking where the patient was\nlocated when the order was taken, and not the current location of the\npatient.\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patches LA*5.2*58 and\n \n3. Updates to the HL/7 date conversion routines. The previous standard\nfor HL/7 dates listed the date in YYYYMMDDHHMMSS format. The degree of\nprecision was listed as a separate parameter. The new standard format is\n[YYYY[MM[DD[HH[MM[SS]]]]]-zzzz] where the bracketed sections are optional\ndepending on the existence of the subsequent set. Also, if either the\nseconds or the minutes/seconds combination consist only of zeroes, the\nminutes (if zeroes) and seconds will be omitted. The length of the\ndate/time string specifies the degree of precision. In addition, a ZULU\ntime offset (-zzzz) is also included. This is the number of hours between\nLR*5.2*266 do not alter or modify any software design safeguards or safety\nGreenwich Mean Time and the local time where the date/time string was\ncreated. Routines LA7DVM and LA7DVEXT have been modified to use the\nKernel function ($$FMTHL7^XLFDT) to convert dates from FileMan to HL7\ninstead of the HL/7 date conversion utility ($$HDATE^HLFNC).\n \n4. This patch will use TaskMan to transfer data to the CareVue system.\nCurrently, TaskMan is not invoked. This could cause a problem verifying a\nresult if an error was encountered in the CareVue routines.\n \n5. This patch changes the LA7D EDIT FOREIGN INTERFACE (Edit Foreign\ncritical elements functions.\nInterface Parameters) option. It is now easier to add a Ward to a Foreign\nComputer System Name.\n \n6. This patch updates the Processing RTN field (#771) and the Response\nProcessing RTN field (#772) of the Protocol file (#101) for the LA7D\nCARELIFE RESULTS and LA7D CARELIFE SERVER entries. The letter "Q" will be\nentered by the post-init routine LR266 if no entry exists.\n \nNOIS - MIA-0600-30434\n Reported an error, MISSING PROCESSING ROUTINE, when sending the HL7\n \n message from VistA to CareVue. The letter "Q" will be entered by\n the post-init routine LR266 if no entry exists.\nNOIS - MWV-0900-21094\n Reported that all CareVue ward patients tests were not being sent to\n the CareVue system. It was discovered that these patients were ones\n who were transferred from a non-CareVue ward to a CareVue ward after\n the tests were ordered. The patient was bypassed since the location\n at time of order was not a CareVue ward. This patch will correct\n this by looking at the Ward Location field (#.1) in the Patient file\n (#2) for the current location of the patient.\n\n
\nVISTA Laboratory Package patch LA*5.2*57 contains no changes to software\n\n process will use INCLUDE UNCOLLECTED ACCESSIONS (#.1) in the LOAD/WORK\n LIST file (#68.2) to determine if a specimen should be downloaded to\n an instrument. Each entry in the AUTO INSTRUMENT file has a related\n LOAD/WORK LIST entry. Setting the INCLUDE UNCOLLECTED ACCESSIONS field\n to NO or blank (no value) will prevent the specimen/test downloading to\n the instrument. If the field is set to YES then uncollected specimens\n will be downloaded to an instrument. An accession is considered as\n being "collected" when the LAB ARRIVAL TIME field (#12) within the\n ACCESSION NUMBER multiple field (#68.02) within the DATE multiple\n field (#68.01) of ACCESSION file (#68) has a date/time.\n \n \n \n5. The patch introduces the ability to have a test generate more\n than one test order. If an ordered test actually requires two or more\n tests to be performed on an instrument, then enter the test multiple\n times and associate the appropriate UI TEST CODE with the test to be\n ordered. \n \n For result processing purposes the test may need to be entered\n separately if the result test is associated with a different file\n *****************************************************************\n #60 test or uses a different result code (UI TEST CODE). If the\n ordered and result test are the same and use the same UI TEST CODE\n then the same entry can be used for both purposes.\n\n An example would be an order for ionized and normalized calcium.\n To perform this test on the instrument it may need to perform both\n a pH and ionized calcium. In the AUTO INSTRUMENT file the test\n ionized calcium would be entered twice for ordering purposes. The\n first entry would be associated with ordering the ionized calcium\n while the second entry could be used to order the pH. \n * PLEASE NOTE: To utilize the functionality added by this patch *\n \n TEST: IONIZED CALCIUM\n UI TEST CODE: mCa++ ROUTINE STORAGE: TV(695837,1)\n ACCEPT RESULTS FOR THIS TEST: YES DOWNLOAD TO INSTRUMENT: YES\n (Note - this entry is used both to order the test and process the\n results since it uses the same UI TEST CODE for both purposes.)\n \n TEST: IONIZED CALCIUM\n UI TEST CODE: mpH ROUTINE STORAGE: TV(695837,1)\n ACCEPT RESULTS FOR THIS TEST: NO DOWNLOAD TO INSTRUMENT: YES\n * to control auto downloading of uncollected specimens install *\n (Note - this entry is only used to order the pH and is not used to\n accept results.)\n\n TEST: NORMALIZED CALCIUM\n UI TEST CODE: cCa++ ROUTINE STORAGE: TV(695838,1)\n ACCEPT RESULTS FOR THIS TEST: YES DOWNLOAD TO INSTRUMENT: NO\n (Note - this entry is not used for ordering purposes but instead is\n used to process the result from the instrument.)\n \n \n * patch LR*5.2*262 before implementing this functionality. *\n A second example would be bicarbonate. To perform this test on the\n instrument it may need to perform both a pH and pCO2. In the AUTO\n INSTRUMENT file the test HCO3 would be entered twice for ordering\n purposes. The first entry would be associated with ordering the\n pCO2 while the second entry could be used to order the pH. This\n same test would be added a third time. This entry handles the result\n being transmitted by the instrument which uses a different UI TEST\n CODE for result purposes.\n\n TEST: HCO3\n *****************************************************************\n UI TEST CODE: mPCO2 ROUTINE STORAGE: TV(8,1)\n ACCEPT RESULTS FOR THIS TEST: NO DOWNLOAD TO INSTRUMENT: YES\n (Note - this entry is only used to order the pCO2 and is not used to\n accept results.)\n \n TEST: HCO3\n UI TEST CODE: mpH ROUTINE STORAGE: TV(8,1)\n ACCEPT RESULTS FOR THIS TEST: NO DOWNLOAD TO INSTRUMENT: YES\n (Note - this entry is only used to order the pH and is not used to\n accept results.)\n \n\n TEST: HCO3\n UI TEST CODE: cHCO3act ROUTINE STORAGE: TV(8,1)\n ACCEPT RESULTS FOR THIS TEST: YES DOWNLOAD TO INSTRUMENT: NO \n (Note - this entry is not used for ordering purposes but instead is\n used to process the result from the instrument.)\n\n \n \n6. NOIS IND-0699-40171 reported that an invalid HL7 time value was being\n \n downloaded to an instrument.\n \n When building a HL7 message the software will now check time values.\n If the time is found to not conform to HL7 specifications for a time\n value it will adjusted as follows:\n \n If hours are greater than 24, hours will be reported as 24 with no\n minutes/seconds.\n If minutes are greater than 59, minutes will be reported as 59\n If seconds are greater than 59, seconds will be reported as 59\n1. NOIS CHA-1199-31572 reported that when a site entered an invalid\n \n \n7. NOIS WPB-0997-31750 reported an "undefined variable X in routine DIM"\n when the input transform for PARAM 1 (#2) within CHEM TESTS multiple\n field (#30) of the AUTO INSTRUMENT file (#62.4) kills the variable X.\n The input transform will call DIM only if X is defined.\n \n \n8. This patch also corrects the following Vista Programming Standards\n and Conventions (SAC) violations that were observed during software\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n label^routine name in FILE BUILD ENTRY field (#93) and FILE BUILD\n review as part of patch development:\n \n a. Removed direct global read of global ^VA(200) which contains the\n NEW PERSON file. Routines LA7ADL1 and LA7UID2 were retrieving\n user's name. Call changed to Kernel supported reference\n (DBIA # 10060) using FileMan DBS call $$GET1^DIQ.\n \n b. Removed several naked indicator references in routine LADOWN that\n were not documented. Routine changed to use full global reference.\n \n ROUTINE field (#94) in the AUTO INSTRUMENT file (#62.4), the auto\n c. Changed FileMan security on several fields in AUTO INSTRUMENT file\n (#62.4) per SAC section 3.2.6. See section "FILE SECURITY" below for\n additional information.\n \n \n9. Corrects an "undefined variable ^(2)" error in routine LADOWN that\n was detected by laboratory development during the software review for\n the patch. This error would occur if an attempt to download a load/work\n list was initiated which have no specimens on the list.\n \n download process would error with the following message:\n \n10. Removed software checks that would only allow downloading of entries\n in file #62.4 when the internal entry number was less than 100.\n \n \n11. A misspelling of the DOWNLOAD PROTOCOL ROUTINE (#92) field in the\n AUTO INSTRUMENT file (#62.4) is corrected. The word PROTOCOL in the\n field name was misspelled.\n \n \n $ZE= UID+28^LA7ADL:3, %DSM-E-PNAME, bad routine name\n12. The Download a load list to an Instrument option [LA DOWN] sets up the\n ^LA global for downloading records to an instrument that are direct\n connects or interfaced via the Lab LSI. The Lab Universal Interface\n does not use the LA global for this purpose. This option will only\n setup the ^LA global when the MESSAGE CONFIGURATION field (#8) in AUTO\n INSTRUMENT file is empty, indicating that this entry is not using the\n Lab Universal Interface.\n \n \n13. During patch development it was found that processing of the HL7\n \n specimen source from sequence 15 of the OBR segment of a HL7 Result\n (ORU) message was checking the entire first component of this field.\n This checking should occur using the first sub-component of the first\n component of sequence 15. Routine LA7UIIN1 has been changed to\n correctly check the specimen source.\n \n \n14. Functionality that was tested by the test sites:\n \n Site \n The auto download process will check for valid routine and label\nFunction | ASH | BHS | CPL | IND | MIW | STX | TVH | UNY\n-----------------------------------------------------------------------------\nUsed auto download? | YES | YES | YES | YES | YES | YES | YES | YES\n \nUsed download via loadlist? | YES | NO | YES | NO | NO | NO | NO | YES\n \nTested screening capabilities | YES | YES | YES | NO | YES | YES | YES | YES\nbased on accession area?\n \nTested screening capabilities | YES | YES | NO | YES | YES | NO | NO | YES\n entry points. If an invalid/missing routine/label is found then the\nbased on specimen type?\n \nTested screening capabilities | YES | NO | NO | NO | NO | NO | NO | YES\nbased on urgency?\n \nUsed combination of the above | YES | YES | NO | NO | NO | NO | NO | YES\ntest screening capabilities?\n \nScreened on collection status | YES | YES | YES | YES | YES | YES | NO | YES\nbased on the associated\n auto download process will ignore that entry in file #62.4 and send\nloadlist setting? \n \nUsed capability to generate | YES | NO | NO | NO | YES | NO | NO | NO\nadditional tests in the order\nmessage?\n\n Legend: ASH = Asheville VAMC\n BHS = Boston HCS\n CPL = Central Plains HCS\n IND = Indianapolis VAMC\n an alert to the mail group LAB MESSAGING with one of the following\n MIW = Milwaukee VAMC\n STX = South Texas HCS \n TVH = Tennessee Valley HCS\n UNY = Upstate New York HCS (VISN 2)\n \n YES = tested functionality\n NO = did not test functionality\n \n \n \n messages:\nASSOCIATED NOIS\n---------------\n BIL-0700-31662 \n CHA-1199-31572\n CPH-1000-41040 \n IND-0699-40171\n IND-0200-41054 \n LAH-0299-62613\n SAJ-0997-70774 \n UNY-0700-10460 \n \n \n WPB-0997-31750 \n \n\nASSOCIATED E3R'S\n----------------\n #13785 - LRPHMAN & LRPHEXCPT BOTH SENDING HL7 MESSAGE\n \n \nTEST SITES\n----------\n a. When no routine is entered in field #94.\n Asheville VAMC\n Boston HCS\n Central Plains HCS\n Indianapolis VAMC\n Milwaukee VAMC \n South Texas HCS \n Tennessee Valley HCS\n Upstate New York HCS (VISN 2)\n \n \n "No download routine (field #94) specified for AUTO INSTRUMENT: xxx"\nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA57 N/A 5998709 **57** (Deleted by KIDS)\n \n LA7ADL 10978189 5237792 **17,25,23,57**\n LA7ADL1 7046668 4892374 **17,23,57**\n LA7UID 2037413 2071504 **17,57**\n LA7UID1 5866288 2775829 **17,57**\n LA7UID2 9041764 8668527 **17,27,57**\n LA7UIIN1 10176639 5544723 **17,23,27,57**\n LADOWN 9641097 5592262 **17,57**\n LADOWN1 1620875 814617 **17,42,57**\n \n \n b. When the routine referenced in field #94 does not exist.\nList of preceding patches: 27, 42\nSites should use CHECK^XTSUMBLD to verify checksums. \n \n \nFILE SECURITY\n============= \n \n There are six existing fields which have FileMan Write Access changed to\n "@". This is required for security purposes. To edit these fields requires\n the user to have FileMan Programmer's Access. The fields affected are:\n "Invalid download routine (field #94) specified for AUTO\n \n - PROGRAM (#2), DOWNLOAD ENTRY (#91), DOWNLOAD PROTOCOL ROUTINE (#92),\n FILE BUILD ENTRY (#93) and FILE BUILD ROUTINE (#94) of the\n AUTO INSTRUMENT file (#62.4).\n \n - PARAM 1 (#2) within CHEM TESTS multiple field (#30) of the AUTO\n INSTRUMENT file (#62.4).\n \n************************************************************************\n \n INSTRUMENT: xxx"\nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak hours. \n The install will disable option Download a load list to an Instrument\n [LA DOWN] as specified in #7 below and turn off Lab Universal Interface\n Auto Download. Accessioning should not be occurring within the\n Laboratory package during the installation of this patch.\n \n \n \nNOTE: Kernel, MailMan and HL7 patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n c. When the routine label referenced in field #93 does not exist.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n "Invalid download routine label (field #93) specified for AUTO\n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\nThis patch addresses fixes/enhancements to the Lab Universal Interface\n in the AUTO INSTRUMENT file (#62.4) INSTRUMENT: xxx"\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab option during patch\n installation.\n \n Download a load list to an Instrument [LA DOWN]\n \n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*57'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LA57 will be deleted after successful patch installation.\n \n \n where "xxx" is the value of the NAME field (#.01) in AUTO INSTRUMENT \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \nThe Lab ADPAC/LIM should review the AUTO INSTRUMENT and LOAD/WORK LIST\nfiles to adjust any field settings based on the corrections/enhancements \nintroduced by this patch.\n \nNote: Use FileMan Enter/Edit option to edit LOAD/WORK LIST file (#68.2)\n and AUTO INSTRUMENT file (#62.4).\n \n file (#62.4).\n1. If using the auto download feature of the Lab Universal Interface then\nshutdown the auto download process first before making changes. This can\nbe performed by using the Start/Stop Auto Download Background Job\n[LA7 ADL START/STOP] option and selecting action: 2 Shutdown Auto Download\nJob.\n \n2. To prevent uncollected accessions from being downloaded via the\nUniversal Interface, use FileMan Enter/Edit to set INCLUDE UNCOLLECTED\nACCESSIONS (#.1) field in the LOAD/WORK LIST file (#68.2) to NO for the\nload/work list that is associated with an instrument in the AUTO INSTRUMENT\n \nfile via LOAD/WORK LIST field (#3).\n \n3. Configure those tests that will require download eligibility screening.\nUsing FileMan Enter/Edit, edit these tests in the AUTO INSTRUMENT file that\nshould be screened by editing the fields ACCESSION AREA (#7), SPECIMEN (#8)\nand URGENCY (#9) within CHEM TESTS multiple field (#30) of the AUTO\nINSTRUMENT file (#62.4).\n \nIf the same test requires different screening criteria, the test can be\nentered multiple times and configured appropriately.\n \n \n4. Restart the auto download if stopped in number #1 above using the same\noption and selecting action: 1 Start/Restart Auto Download Job.\n \n \n \n************************************************************************\nInstallation example: \n \nSelect Installation Option: 6 Install Package(s)\n2. NOIS CHA-1199-31572 reported an inaccurate comment in the routine\nSelect INSTALL NAME: LA*5.2*57 Loaded from Distribution 5/11/00@15:44:21\n => LA*5.2*57\n \nThis Distribution was loaded on May 11, 2000@15:44:21 with header of\n LA*5.2*57\n It consisted of the following Install(s):\n LA*5.2*57\nChecking Install for Package LA*5.2*57\nWill first run the Environment Check Routine, LA57\n \n LA7ADL. Comment "File build (entry^routine) from fields #92 and #93 in\n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*57\n \nIncoming Files:\n \n \n 62.4 AUTO INSTRUMENT (Partial Definition)\nNote: You already have the 'AUTO INSTRUMENT' File.\n file 62.4". The reference to field numbers is incorrect. Comment has\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n been corrected to reflect fields #93 and #94.\nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*57 :\n May 11, 2000@16:24:51\n \nBuild Distribution Date: May 11, 2000\n \n Installing Routines:.........\n May 11, 2000@16:24:51\nAuto Download requested in several NOIS's and E3R's. It allows the auto\n \n \n Running Pre-Install Routine: PRE^LA57.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n Shutting down Lab Universal Interface Auto Download Job\n \n *** Pre install completed ***\n \n \n Installing Data Dictionaries: ..\n May 11, 2000@16:24:52\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION..\n May 11, 2000@16:24:52\n \n Running Post-Install Routine: POST^LA57.\n3. NOIS IND-0200-41054 requested the ability to screen on an accession's\n \n *** Post install started ***\n \n Restarting Lab Universal Interface Auto Download Job\n \n Updating package revision data for file #62.4\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n specimen type to determine if an order should be downloaded to the\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*57 Installed.\n May 11, 2000@16:24:52\n \n Install Message sent #23893\n instrument. In addition to screening by specimen type, tests can also\n be screened by accession area and urgency.\n \n This patch adds three new fields to support this functionality.\n The fields are:\n \ndownload to be configured to only transmit orders for collected specimens.\n ACCESSION AREA (#7), SPECIMEN (#8) and URGENCY (#9) within CHEM TESTS\n multiple field (#30) of the AUTO INSTRUMENT file (#62.4).\n \n When these fields are valued for a test in the CHEM TESTS multiple,\n an order for the test on the accession will only be transmitted to\n the instrument if it matches this criteria. Any field that is blank\n (no value) will match on any value for the field.\n \n If the same test requires different screening criteria, the test can\n be entered multiple times and configured appropriately.\nIt enhances the auto download to determine if a test order is transmitted\n \n Example:\n Accession CH 0510 20 has a specimen type = plasma with the following\n tests: GLUCOSE (routine)\n BUN (routine)\n CALCIUM (stat)\n \n AUTO INSTRUMENT file is configured with entries that have the following\n tests: \n Test Accession Area Specimen Urgency\nto an automated instrument based on the accession area, specimen type and\n ---- -------------- -------- -------\n GLUCOSE CH <blank> routine\n BUN CH serum <blank>\n CALCIUM <blank> <blank> stat\n \n This would create an order for GLUCOSE since it matched on the\n accession area, urgency and any specimen.\n \n The BUN would not be sent to this instrument because it did not match\n on the specimen type while matching on the accession area and any\ntest urgency of each test on the accession.\n urgency.\n \n The CALCIUM would be sent because it matched on the urgency and any\n accession area and specimen type.\n \n \n4. E3R #13785 - LRPHMAN & LRPHEXCPT BOTH SENDING HL7 MESSAGE requested the\n ability for the auto download to ignore specimens that have not been\n collected. This patch adds functionality to have the auto download only\n download specimens that are marked as collected. The auto download\n\n
\nVISTA Laboratory Package patch LA*5.2*59 contains no changes to software\nresults for accessions that are not in the "CH" or "MI" subscripts if the\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*59'. When prompted 'Want KIDS to\nsite is a test site for under development patch LA*5.2*41. Patch LA*5.2*41\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LA59 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\nadds support for microbiology instruments results that are processed within\n===============================\n\nNone\n \n \n************************************************************************\nInstallation example:\n\nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*59 Loaded from Distribution 4/24/01@13:29:16\nthe "MI" subscript.\n => LA*5.2*59\n \nThis Distribution was loaded on Apr 24, 2001@13:29:16 with header of\n LA*5.2*59\n It consisted of the following Install(s):\n LA*5.2*59\nChecking Install for Package LA*5.2*59\nWill first run the Environment Check Routine, LA59\n \n \n\n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*59\n \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nAs part of the install of this patch, the post-install routine performs\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*59 :\n Apr 24, 2001@13:34:05\n \nBuild Distribution Date: Apr 24, 2001\na check to determine if under development patch LA*5.2*41 has been\n \n Installing Routines:...\n Apr 24, 2001@13:34:05\n \n Running Pre-Install Routine: PRE^LA59.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \ninstalled. If patch LA*5.2*41 is detected a mail message will be\n --- No action required ---\n \n *** Pre install completed ***\n \n Running Post-Install Routine: POST^LA59.\n \n *** Post install started ***\n \n --- No action required ---\n \ntriggered to the Lab Development team at the Dallas OI Field Office.\n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*59 Installed.\n Apr 24, 2001@13:34:05\nThe message will contain information concerning patch routine checksums,\n \n Install Message sent #52035\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nstatus of patch installation from the PACKAGE file (#9.4) and a copy\nof the patch routines.\n\n\nASSOCIATED NOIS\n---------------\n BAC-0501-41085\n CTX-0601-71333\n HEH-0401-42541\n KAN-0401-41472 \n \n LAH-0401-62030\n LAS-0601-60733 \n MEM-0501-70993\n MRN-0401-41875\n \n\nTEST SITES\n----------\n Battle Creek VAMC\n Central Texas HCS\nPatch LA*5.2*59 addresses a fix to the Lab Universal Interface (UI)\n Heartland-East HCS\n Heartland-West HCS\n Las Vegas VAMC \n Memphis VAMC\n Milwaukee VAMC\n VA Greater Los Angeles HCS\n\n\nROUTINE SUMMARY\n===============\nincoming message processing. Released patch LA*5.2*57 introduced changes\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA59 N/A 7061351 **59** (Deleted by KIDS)\n LA7UIIN1 5544723 5541384 **17,23,27,57,59**\n \nto the processing of HL7 result (ORU) messages that can result in the\n List of preceding patches: 57\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 2 minutes. This patch\nprocessing routine LA7UIIN1 entering an endless loop. This occurs when the\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak hours.\n \n \nNOTE: Kernel, MailMan and HL7 patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \nUI processes a message that is for an accession area that is not associated\n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\nwith the "CH" subscript. Patch LA*5.2*59 changes routine LA7UIIN1 to ignore\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n
\nVISTA Laboratory Package patch LA*5.2*60 contains no changes to software\nto transmit the test results to the requesting facility. Patch LA*5.2*60\n\n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LA60 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \nNone\nchanges routine LAKDIFF3 to set the variable LRORU3 based on the current\n \n \n************************************************************************\nInstallation example: \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*60 Loaded from Distribution 1/30/02@15:07:57\n => LA*5.2*60\n \nThis Distribution was loaded on Jan 30, 2002@15:07:57 with header of\naccession before calling the lab verifying process.\n LA*5.2*60 \n It consisted of the following Install(s):\n LA*5.2*60\nChecking Install for Package LA*5.2*60\nWill first run the Environment Check Routine, LA60\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*60\n \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nThe "Heads-Up on Patient Safety Alert" issued on 18 January 2002 regarding\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*60 :\n Jan 30, 2002@15:10:22\n \nBuild Distribution Date: Jan 30, 2002\n \nthe electronic transmission of an incorrect result from a LEDI Host\n Installing Routines:...\n Jan 30, 2002@15:10:22\n \n Running Pre-Install Routine: PRE^LA60.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n *** No action required ***\nlaboratory to a Collecting Laboratory is resolved by patch LA*5.2*60.\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION..\n Jan 30, 2002@15:10:22\n \n Running Post-Install Routine: POST^LA60.\n \n \n *** Post install started ***\n \n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n\n Updating KIDS files.......\n \n LA*5.2*60 Installed.\n Jan 30, 2002@15:10:22\n \n Install Message sent #xxxxx\n \n \nSelect Installation Option:\nASSOCIATED NOIS\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n---------------\n NONE\n \n \nTEST SITES\n----------\n Milwaukee VAMC\n \n \nROUTINE SUMMARY\n \n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA60 N/A 4331834 **60** (Deleted by KIDS)\n LAKDIFF3 1523847 1615579 **52,60**\nPatch LA*5.2*60 addresses a fix to the option Keypad differential for\n \n List of preceding patches: 52\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \nCRT's [LA KB DIFF]. It was determined, during testing of another patch,\n The install time for this patch is less than 1 minute. This patch\n can be installed when Laboratory users are on the system. Users should\n not be using option Keypad differential for CRT's [LA KB DIFF] during\n patch installation. The KIDS install will disable this option during\n installation. Suggested time to install: anytime the option LA KB DIFF\n is not being used.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\nthat the lab verifying process would trigger the transmission of the\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \nwrong patient's results when verifying an accession received via Laboratory\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\nElectronic Data Interchange (LEDI). The variable LRORU3 is used by the\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\nlab verifying process to trigger the building of a HL7 result (ORU) message\n \n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*60'. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n \n Note: Option Keypad differential for CRT's [LA KB DIFF] will be\n disabled during installation by KIDS.\n\n
\nVISTA Laboratory Package patch LA*5.2*46 contains no changes to software\n\n REQUIRE PATIENT HEIGHT\n PATIENT HEIGHT\n PATIENT HEIGHT UNITS\n PATIENT HEIGHT LOINC CODE\n REQUIRE PATIENT WEIGHT\n PATIENT WEIGHT\n PATIENT WEIGHT UNITS\n PATIENT WEIGHT LOINC CODE\n REQUIRE COLLECTION VOLUME\n COLLECTION VOLUME\nAs of the release date of this software, there is no national solution to\n COLLECTION VOLUME UNITS\n COLLECTION VOLUME LOINC CODE\n REQUIRE COLLECTION END D/T\n \nThe process of building a shipping manifest now allows the user to\nspecify the starting and ending accession numbers to check within an\naccession area. This feature can shorten manifest building time when\nsearching a yearly accession area with a large number of accessions.\nIt allows the site to skip the accession numbers that have been\ncompleted earlier in a year and no longer need to be checked to\nimplement a laboratory electronic HL7 standard interface to a facility or\ndetermine it any of the tests meet the criteria for building to a\nmanifest.\n \n \nThe process of closing a shipping manifest now performs a check of\ncertain required information. The required information check is for:\n 1. Each test has an order NLT code assigned.\n 2. If shipping to a facility that does not use VA NLT codes for\n test ordering, the appropriate non-VA test codes/names\n have been designated for all tests on the manifest.\nother entity outside the VA wide area network. National communication\n 3. Site-specified required patient/specimen information has been\n entered.\n \n \nThe process of building orders in the file LAB PENDING ORDER (#69.6)\nhas been enhanced to use information from the file LAB SHIPPING\nCONFIGURATION (#62.9) to create orders based on the host facilities\nspecified collection sample and urgency.\n \n \nsecurity concerns are still being debated by the Department of Veterans\nThe LEDI result (ORU) messages will now include the test interpretation\nfound in LABORATORY TEST file (#60) as a comment (NTE segment) following\nthe test results. Test results to be stored will be checked against the\nFileMan input transform for the data name used to store the results in\nfile LAB DATA (#63). If the results do not pass the FileMan input\ntransform then an error message will be generated via the Lab\nUniversal Interface error reporting process. Results values that are\n"canc", "pending" or "comment" will be stored.\n \n \nAffairs (VA) and are awaiting resolution. At present, a VA medical center,\nThe option Display Lab Universal Interface Message [LA7 PRINT LAB UI\nMESSAGE] has been modified to prompt the user if the Kernel Browser\nshould be used to display a message. If the browser is not selected then\na standard "scroll and roll" display of the selected message(s) is\nproduced.\n\nOption Retransmit LEDI Lab Results [LA7S RESULTS RETRANSMIT] will allow\na user to retransmit the laboratory test results for selected accession(s)\nto the collecting/submitting facility.\n \nwhich intends to utilize this software in conjunction with an interface to\nThe install will update several files during the post-install as necessary:\n - It was found that the original release of LEDI failed to update the\n field SHIP VIA #.04 in file LAB SHIPPING MANIFEST (#62.8) when a manifest\n is created. This information will update existing manifests with\n information from the related file LAB SHIPPING CONFIGURATION (#62.9)\n entry.\n \n - The processing routine specified in file LA7 MESSAGE PARAMETER (#62.48)\n for entries related to LEDI has been changed. Existing entries will be\n updated as appropriate.\na commercial reference laboratory or other non-VA information system entity,\n \n NOIS HIN-0998-40287 corrected an undefined variable error when building a\n result message.\n \n NOIS BOS-0498-10163 reported an undefined error when attempting to lock\n LAB SHIPPING MANIFEST file (#62.8). Due to a typographically error the\n character "$" was omitted from a $DATA intrinsic function.\n \n NOIS TAM-0401-31867 reported that option Lab Messaging File Integrity\n Checker [LA7 CHECK FILES] option allowed queuing the report to the\nwill need to coordinate with the vendor an acceptable communication method.\n "HOME" device. The option will now prevent queuing to the HOME device.\n It also removes "HOME" as the device default value.\n \n\nASSOCIATED E3R\n--------------\nE3R #15348, RETRANSMIT FUNCTION FOR LEDI\n \nASSOCIATED NOIS\n---------------\nAny implementation will need to be approved by the facility and VISN\n ALB-1099-51591\n ALB-0100-50284\n BOS-0498-10163\n HIN-0998-40287\n HUN-1100-21862\n MIW-1197-41082\n TAM-0401-31867\n \n \nTEST SITES\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nInformation Security Officer (ISO) and meet current VA security requirements\n----------\n Alexandria VAMC\n Biloxi VAMC\n Birmingham VAMC\n Fayetteville VAMC\n Hines VAMC\n Houston VAMC\n Jackson VAMC\n Little Rock VAMC\n Madison VAMC\nfor external electronic connections. See VHA Directive 6212, Security of\n Milwaukee VAMC\n Muskogee VAMC\n New Orleans VAMC\n Oklahoma City VAMC\n Shreveport VAMC\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\nExternal Electronic Connections and VHA Directive 6210, Automated Information\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA46 N/A 9520365 **46** (Deleted by KIDS)\n LA7CHKF 10597193 11028299 **27,46**\n LA7QRY N/A 1084520 **46**\n LA7QRY1 N/A 3509927 **46**\nSystems (AIS) Security for additional information and guidance. Additional\n LA7QRY2 N/A 4552927 **46**\n LA7SBCR 1495927 653666 **27,46**\n LA7SBCR1 7086650 4924406 **27,46**\n LA7SBCR2 3323374 2564479 **27,46**\n LA7SCE 10260809 11402708 **27,46**\n LA7SM 16316313 10277989 **27,46**\n LA7SM1 2146828 8553973 **27,46**\n LA7SM2 N/A 12143125 **46**\n LA7SMB 17707549 14649107 **27,46**\n LA7SMP 15792287 11746903 **27,45,46**\nsecurity information may be obtained from the Health Information Security\n LA7SMP0 N/A 9303222 **46**\n LA7SMPXL 5400542 3215234 **27,42,46**\n LA7SMU 11040439 7104257 **27,46**\n LA7SMU1 5335635 6241668 **27,46**\n LA7SMU2 N/A 5290542 **46**\n LA7SRR N/A 6233015 **46**\n LA7UIIN2 9850298 12296505 **17,23,27,46**\n LA7UTILA 11812487 10237097 **23,27,46**\n LA7VHL 8527903 4500486 **27,46**\n LA7VHLU N/A 4469720 **46**\nService (HISS) web page at http://vaww.domain.ext/miss.\n LA7VHLU1 N/A 2011157 **46**\n LA7VHLU2 N/A 3873916 **46**\n LA7VHLU3 N/A 2007360 **46**\n LA7VHLU4 N/A 5424804 **46**\n LA7VHLU5 N/A 5541950 **46**\n LA7VIN N/A 1398763 **46**\n LA7VIN1 N/A 5261630 **46**\n LA7VIN2 N/A 5808892 **46**\n LA7VIN3 N/A 2061956 **46**\n LA7VIN4 N/A 7936019 **46**\n\n LA7VIN5 N/A 5205707 **46**\n LA7VIN5A N/A 5039195 **46**\n LA7VMSG 16357149 3253314 **27,50,56,46**\n LA7VMSG1 3358807 8200340 **56,46**\n LA7VOBR N/A 2129056 **46**\n LA7VOBRA N/A 5326634 **46**\n LA7VOBX N/A 2088674 **46**\n LA7VOBX1 N/A 3799868 **46**\n LA7VOBX2 N/A 4350324 **46**\n LA7VOBX3 N/A 5240738 **46**\nImplementation of a HL7 messaging interface between the VA VistA Laboratory\n LA7VOBXA N/A 6232009 **46**\n LA7VORC N/A 1565653 **46**\n LA7VORM 17384019 6471896 **27,42,46**\n LA7VORM1 20868841 7601990 **27,51,46**\n LA7VORM2 N/A 3426954 **46**\n LA7VORM3 N/A 6787219 **46**\n LA7VORU 10077624 8070282 **27,46**\n LA7VORU1 N/A 4734718 **46**\n LA7VORU2 N/A 1962290 **46**\n LA7VPID N/A 4123683 **46**\npackage and a non-VA information system consists basically of three parts:\n LA7VSET 19500034 15979413 **27,51,55,46**\n LA7VSET1 12858976 9065449 **27,51,55,46**\n LA7VSTP 6154318 6079680 **27,44,51,46**\n LA7VSTP1 8332246 3317926 **27,46**\n LAGEN 9445120 8522786 **1,17,22,27,47,46**\n LASET 6644420 6955342 **27,42,46**\n \n List of preceding patches: 42, 45, 47, 51, 55, 56\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n - VistA Laboratory LEDI II software.\n \nSOFTWARE RETRIEVAL:\n===================\n \n The following software and documentation files are exported as part of\n this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n LAB_LEDI_II.KID LA*5.2*46 KIDS build ASCII\n \n - certified communication software and hardware\n LR*5.2*222 KIDS build\n \n LAB_LEDI_II_IG.PDF LABORATORY ELECTRONIC DATA BINARY\n LAB_LEDI_II_IG.DOC INTERCHANGE PHASE II (LEDI II)\n INSTALLATION GUIDE\n \n LAB_LEDI_II_UM.PDF LABORATORY ELECTRONIC DATA BINARY\n LAB_LEDI_II_UM.DOC INTERCHANGE PHASE II (LEDI II)\n USER MANUAL\n \n - non-VA information system capable of sending and receiving laboratory HL7\n The software files are available on one of the following OI Field\n Offices' ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these \n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n order and result messages.\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n\n\nINSTALLATION INSTRUCTIONS\n-------------------------\n The instructions for installation of the software are included in the\n installation guide.\nAll three must be functional to utilize the capabilities of this LEDI II\n\n\nPOST-INSTALLATION INSTRUCTIONS\n------------------------------\n \n \n The post-instructions for installation of the software are included in\n the installation guide.\n \n \nsoftware patch. The implementation,setup, and configuration of vendor provided\nINSTALLATION EXAMPLE\n====================\n \n An installation example is included in the installation guide.\nhardware and software is NOT addressed by this documentation. Consult the\nvendor provided documentation and instructions to interface to the VistA\nLaboratory package.\n \n \n========================================\nAdditionally support is added for TCP/IP protocol as a communication\nprotocol for the transmission of LEDI HL7 messages. This requires\npatch HL*1.6*19 to have been successfully installed. The implementation\nof this protocol in place of the current MailMan protocol will\nsignificantly increase transmission speed of messages and reduce system\noverhead/storage. Both systems that will be exchanging HL7 messages,\nusing the TCP/IP protocol will need to coordinate the switch to this\nnew transmission method. There will be two logical links established\nto exchange messages a server (listener) logical link to receive and\nprocess messages and a client link to transmit messages.\n \n \nA new shipping code SM40 - Required Shipping Info Updated has been added\nto file LAB ELECTRONIC CODES (#64.061). This code is used when recording\nthis event in file LAB SHIPPING EVENT (#62.85)\n \n \nComments can now contain ";"character. Previously the ";" character was\nused to parse comments into multiple lines and filed in the database using\na classical FileMan DIE call. FileMan parsed the fields to edit using\nthe ";" character in the DR string. The new call uses a FileMan database\nThis patch adds support for sending/receiving Laboratory Electronic\nserver call, which does not have this restriction.\n \n \nNew fields have been added and existing fields modified within the\nCHEM TEST subfile of file AUTO INSTRUMENT (#62.4) to support the\nfollowing features when processing result messages. These features\nare site-selectable. See data dictionary field description for each\nfield for further information. Using option LEDI Setup [LA7V SETUP],\nthe section on Auto Instrument settings will prompt for these additional\nfields.\nData Interchange (LEDI) orders/results with non-VA facilities\n \n1. Process NTE segments following OBX segments. Comments found attached\n to specific test results are stored as comments. The field REMARK PREFIX\n #18 in CHEM TEST subfile can be used to specify a comment prefix that\n will be made part of the comment.\n2. Store test reference ranges, abnormal flags and name of performing\n laboratory. This patch stores these parameters as comments with the\n results. This information is prefixed with the field REMARK PREFIX.\n3. Specify whether final or incomplete results are processed.\n \n(commercial reference laboratories).\nThe fields that are new/modified are:\n ACCEPT RESULTS FOR THIS TEST\n STORE REMARKS\n REMARK PREFIX\n STORE PRODUCER'S ID\n STORE REFERENCE RANGE\n STORE ABNORMAL FLAGS\n \nNew fields have been added to the LAB SHIPPING CONFIGURATION file (#62.9)\nto allow collecting facilities to specify required patient/specimen\n \ninformation to be sent with shipping manifest. This can include specimen\nvolume, weight, collection end date/time (collection duration),\npatient height and weight (NOIS ALB-1099-51591). LOINC codes are used to\nidentify patient height, weight and specimen weight when appropriate.\nEditing these fields is performed using option Edit Shipping Configuration\n[LA7S EDIT 62.9]. The fields are:\n \n USE NON-VA CODES\n TEST/PROFILE sub-file\n DIVISION\n\n
\nVISTA Laboratory Package patch LA*5.2*61 contains no changes to software\n * patch, the HL7 Result (ORU) message will no longer contain the *\nproblem the software will no longer generate a performing laboratory\ncomment. \n\nCollecting facilities wanting a comment indicating the name of the\nperforming laboratory should turn on the generation of the performing\nlaboratory comment when processing the results at the collecting facility.\nTo turn on the generation of the performing laboratory comment use the\noption LEDI Setup [LA7V SETUP]. Under the host facility automated\ninstrument section for each test, enter a remark prefix in field REMARK\nPREFIX (#19) and "YES" at the field STORE PRODUCER'S ID (#20). The\n * performing laboratory comment. See item #7 for instructions. *\nperforming laboratory comment can then be generated based on field OBX-15\nProducer's ID in the OBX segment for each test result found in the HL7\nResult (ORU) message. The comment generated by the software will be \nremark prefix_"results from "_name of performing institution from \nINSTITUTION file (#4). If the REMARK PREFIX field is blank then the test\nname of the corresponding test from LABORATORY TEST file (#60) is used.\n \nExample:\n remark prefix="Theophylline "\n institution="REGION 7 ISC,TX (DEMO)"\n * *\n generated comment="Theophylline results from REGION 7 ISC,TX (DEMO)"\n\n8. NOIS IND-0402-42261 reported a problem with building and sending HL7\nResult (ORU) messages to the collecting facility. Accessions with UID's\nthat are alphanumeric were skipped during message building due to code\nthat was treating the UID as numeric. Routine LA7VMSG1 will now handle\nalphanumeric UID's and return results to the collecting facility.\n \n9. Due to changes to routine LA7VORU, which resulted in the routine size \nexceeding the VA Vista Programming Standards and Conventions (SAC) of\n * Host facilities: Notify your collection facilities of scheduled *\n10,000 characters, the routine was split into two routines, LA7VORU\nand LA7VORUA.\n \n \nASSOCIATED NOIS\n---------------\n BHS-0302-10236\n CON-0302-10181\n HWH-0202-42779\n IND-0402-42261\n * patch installation. *\n LAS-0402-61457\n LON-0402-60012\n PHI-0302-20433\n \n \nTEST SITES\n----------\n Boston HCS\n Indianapolis VAMC\n Lexington VAMC\n * *\n Long Beach HCS\n Louisville VAMC\n Milwaukee VAMC\n Philadelphia VAMC\n Southern Nevada HCS\n VA Heartland - East, VISN 15\n VA Heartland - West, VISN 15 \n \n \nROUTINE SUMMARY\n ********************************************************************\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA61 N/A 9395003 **61** (Deleted by KIDS)\n LA7QRY1 3509927 3555910 **46,61**\n \n LA7SCE 11402708 11501726 **27,46,61**\n LA7SM1 8553973 8587872 **27,46,61**\n LA7VHLU1 2011157 2323481 **46,61**\n LA7VHLU2 3873916 4100825 **46,61**\n LA7VMSG1 8200340 8227296 **56,46,61**\n LA7VOBX1 3799868 3981059 **46,61**\n LA7VORM1 7601990 7594289 **27,51,46,61**\n LA7VORU 8070282 6241961 **27,46,61**\n LA7VORUA N/A 2199285 **61**\n \n1. NOIS HWH-0202-42779 and LAS-0402-61457 reported a problem in the\n List of preceding patches: 46\n Sites should use CHECK^XTSUMBLD to verify checksums. \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 10 minute. This patch\n can be installed when Laboratory users are on the system.\nbuilding of a HL7 Order (ORM) message. Under certain circumstances, the\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nsoftware was passing the collecting facility station number instead of\n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\nan INSTITUTION file (#4) internal entry number to a Lab HL7 field building\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. Perform the following steps if applicable: \n All Lab LEDI (LA7V*) related HL v1.6 LLPs should be shutdown.\n Use the HL menu option Start/Stop Links [HL START] to shutdown\nroutine. Construction of the collecting facility's HL7 Order (ORM) message\n these LLPs if they are running.\n\n\n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*61'. When prompted "Want KIDS to\n Rebuild Menu Trees Upon Completion of Install? YES//', choose 'NO'\n When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES//', choose 'NO'. When prompted 'Want to DISABLE Scheduled\n Options, Menu Options, and Protocols? YES//', choose 'YES'.\n\nORC segment's field ENTERING ORGANIZATION (ORC-17) placed the VA station\n All LA7V* protocols should be placed out of service during the install.\n This can be accomplished by answering the KIDS install questions:\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'YES'.\n \n Enter options you wish to mark as 'Out Of Order': <RET>\n \n Enter protocols you wish to mark as 'Out Of Order': LA7V*\n\nnumber in the field's second sub-component instead of the first\n \n Note: KIDS will disable the following options during installation.\n Edit Shipping Configuration [LA7S EDIT 62.9]\n Enter/verify/modify data (manual) [LRENTER]\n Enter/verify data (auto instrument) [LRVR]\n Enter/verify data (Work list) [LRVRW]\n Enter/verify data (Load list) [LRVRW2]\n Referral Patient Multi-purpose Accession [LRLEDI]\n \n 8. On a mapped system, rebuild your map set.\nsub-component. This occurs when the collecting facility's VA station\n \n Note: Routine LA61 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \n1. Restart any LA7V* HL v1.6 LLP's shutdown as part of the patch\ninstallation process. Use the Start LLP [HL START] option to restart\nLA7V* HL v1.6 LLP's.\nnumber is alphanumeric. When processing the ORM message at the host\n \n2. LEDI Host laboratories should notify their LEDI collecting facilities\nof removal of performing laboratory comment from HL7 Result (ORU) messages.\nSee item #7 in patch description above for actions collecting facilities\nshould take.\n \n \n************************************************************************\nInstallation example:\n \nfacility the building of the LAB PENDING ORDERS ENTRY file (#69.6)\nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*61 Loaded from Distribution 4/23/02@10:39:43\n => LA*5.2*61\n \nThis Distribution was loaded on Apr 23, 2002@10:39:43 with header of\n LA*5.2*61\n It consisted of the following Install(s):\n LA*5.2*61\nChecking Install for Package LA*5.2*61\nWill first run the Environment Check Routine, LA61\neither identified the wrong collecting facility or was unable to identify\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*61\n \nIncoming Files:\n \n \n 62.49 LA7 MESSAGE QUEUE (Partial Definition)\na collecting facility. Option Referral Patient Multi-purpose Accession\nNote: You already have the 'LA7 MESSAGE QUEUE' File.\n \n \n 62.9 LAB SHIPPING CONFIGURATION (Partial Definition)\nNote: You already have the 'LAB SHIPPING CONFIGURATION' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n \n[LRLEDI] is unable to extract the test orders from file #69.6 when the\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES//\n \nEnter options you wish to mark as 'Out Of Order':\n \nEnter protocols you wish to mark as 'Out Of Order': LA7V*\n \nEnter protocols you wish to mark as 'Out Of Order':\n \nDelay Install (Minutes): (0-60): 0//\n \nhost facility attempts to process the shipping manifest. Routine LA7VORM1\nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*61 :\n Apr 23, 2002@10:44:07\n \nhas been changed to pass a pointer for file #4 instead of the VA station\nBuild Distribution Date: Apr 23, 2002\n \n Installing Routines:...........\n Apr 23, 2002@10:44:07\n \n Running Pre-Install Routine: PRE^LA61.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\nnumber to the ORC-17 field building routine.\n \n *** Removing COLLECTING FACILITY (#.02), HOST FACILITY (#.03), ***\n \n *** and LAB MESSAGING LINK (#.07) fields ***\n \n *** from LAB SHIPPING CONFIGURATION file (#62.9) ***\n \n *** These fields will be reinstalled by this patch ***\n \n *** Removing STATUS (#2) field from LA7 MESSAGE QUEUE file (#62.49) ***\n \n \n *** This field will be reinstalled by this patch ***\n \n *** Pre install completed ***\n \n Installing Data Dictionaries: ...\n Apr 23, 2002@10:44:09\n \n Installing PACKAGE COMPONENTS:\n \n2. During review of NOIS HWH-0202-42779 a problem with the "CH" and\n Installing OPTION.......\n Apr 23, 2002@10:44:09\n \n Running Post-Install Routine: POST^LA61.\n \n *** Post install started ***\n \n*** Deleting "ASC" cross-reference on LAB SHIPPING CONFIGURATION file (#62.9) ***\n \n*** Deleting "CH" cross-reference on LAB SHIPPING CONFIGURATION file (#62.9) ***\n"CH1" MUMPS cross-references on COLLECTING FACILITY (#.02) and HOST\n \n*** Building "CH" cross-reference on LAB SHIPPING CONFIGURATION file (#62.9) ***\n \n *** Completed reindexing ***\n \n *** Deleting "ORU" cross-reference on LA7 MESSAGE QUEUE file (#62.49) ***\n \n *** Building "AC" cross-reference on LA7 MESSAGE QUEUE file (#62.49) ***\n \n *** Completed reindexing ***\nFACILITY (#.03) fields respectively of the LAB SHIPPING CONFIGURATION\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*61 Installed.\nfile (#62.9) was identified. Multiple entries in this cross-reference\n Apr 23, 2002@10:44:10\n \n Install Message sent #XXXXX \n \nSelect Installation Option: \npointed to the same entry in the file. The "KILL" logic for these cross-\nPatch LA*5.2*61 addresses several NOIS'es involving the Laboratory\nreferences does not perform correctly, leaving incorrect entries in\nthe "CH" cross-reference. These two MUMPS cross-references are replaced\nby a single new style FileMan Regular INDEX file cross-reference named\n"CH". The cross-reference "ASC" on LAB MESSAGING LINK field (#.07) will\nbe removed due to its lack of use by the laboratory software.\nThe KIDS pre-install will delete these fields and cross-references\nduring patch installation. Patch LA*5.2*61 will install these fields with\nthe new cross-reference "CH" and re-index the "CH" cross-reference.\n \n3. NOIS CON-0302-10181 reported the option Edit Shipping Configuration\nElectronic Data Interchange (LEDI) software. \n[LA7S EDIT 62.9] was prompting the user to edit unexpected fields\nwithin the TEST/PROFILE (#60) subfile, specifically fields ACCESSION\nAREA (#.02) and SPECIMEN (#.03), when a host facility configures a\nshipping configuration to receive specimens from a collecting facility.\nIt was determined that variables setup for a FileMan DIC API call to\nselect an entry in file #62.9 were later interacting with a FileMan DIE\nAPI call to edit the selected entry. The routine LA7SCE has been modified\nto kill required FileMan DIC input variables before making the FileMan\nDIE call.\n \n\n4. NOIS PHI-0302-20433 reported a problem with the setting of the "Q"\ncross-reference on field STATUS (#2) in LA7 MESSAGE QUEUE file (#62.49).\nThe setting of the cross-reference could fail when other fields that the\ncross-reference is dependent on have not been valued. A previous patch\nchanged lab code to use FileMan DBS calls instead of classic FileMan\ncalls. These DBS calls file data by field number. Previously FileMan\nfiled the fields in the order specified in the DR variable. This causes\nthe MUMPS cross-references to fail at times when the other fields the\ncross-reference is dependent on, have not been filed or updated.\nA similar problem potentially exists for the ORU cross-reference on this\n ********************************************************************\nsame field. These two MUMPS cross-references are replaced by new style\nFileMan Regular INDEX file cross-reference named "Q" and "AC" respectively.\nThe KIDS pre-install will delete these fields and cross-references during\npatch installation. Patch LA*5.2*61 will install this field with the new\ncross-references.\n \n5. NOIS BHS-0302-10236 reported a problem with an accession/test building\nmultiples times on a shipping manifest. This was caused when a test is\nspecified multiple times on the shipping configuration but with different\nspecimen types. The logic to build the test onto the manifest was not\n * *\nclearing a flag to indicate that a test should be added to the manifest\nwhen checking the test for each of the possible specimens to build.\nRoutine LA7SM1 will now set and clear the flag to add a test when the\nconfiguration specifies the same test for multiple specimens. \n \n6. NOIS LON-0402-60012 reported a problem when a host facility uses "dummy"\ntests to report patient results. These "dummy" results along with the \npatient's actual test results were transmitted in an HL7 ORU Result message\nto the collecting facility. These test results were encoded with the parent\ntest's result NLT and LOINC codes due to lack of proper result code mapping.\n * Collecting facilities: Upon host laboratory installation of this *\nRoutines LA7VOBX1 and LA7VHLU1 will now attempt to identify test results\nwhich are associated with LABORATORY TEST file (#60) tests that are TYPE =\nBOTH or OUTPUT to determine if a specific test result is returned to the\ncollecting facility. \n\n7. NOIS BHS-0302-10236 reported a problem with the generation of the\nperforming laboratory comment that is automatically added to the HL7\nResult (ORU) message. The name of the performing laboratory was based\non the name of the primary facility. This name is incorrect when testing\nis performed by a division of an integrated facility. To correct this \n\n
\nVISTA Laboratory Package patch LA*5.2*62 contains no changes to software\nHLRESLT, returned by various HL package APIs, misspelled in routines\n \n Enter options you wish to mark as 'Out Of Order': <RET>\n Enter protocols you wish to mark as 'Out Of Order': LA7V*\n Enter protocols you wish to mark as 'Out Of Order': LA7D*\n \n \n \n 8. On a mapped system, rebuild your map set.\n \n Note: Routine LA62 will be deleted after successful patch installation.\nLA7DVC and LA7DVM. The patch corrects the spelling of this variable.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \n1. Restart any LA7V* and CareVue HL v1.6 LLP's shutdown as part of the\npatch installation process. Use the Start LLP [HL START] option to\nrestart LA7V* and CareVue HL v1.6 LLP's.\n \n \nAdditionally, these two routines referenced the variable VAIN(4) before\n************************************************************************\nInstallation example:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: LA*5.2*62 Loaded from Distribution 6/10/02@16:05:04\n => LA*5.2*62\n \nThis Distribution was loaded on Jun 10, 2002@16:05:04 with header of\n LA*5.2*62\n It consisted of the following Install(s):\nthe variable was initialized. This patch calls supported API INP^VADPT\n LA*5.2*62\nChecking Install for Package LA*5.2*62\nWill first run the Environment Check Routine, LA62\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*62\n \n \nto initialize VAIN(4). \n \nWant KIDS to INHIBIT LOGONs during the install? NO//\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES//\n \nEnter options you wish to mark as 'Out Of Order':\n \nEnter protocols you wish to mark as 'Out Of Order': LA7V*\n \nEnter protocols you wish to mark as 'Out Of Order': LA7D*\n \n \nEnter protocols you wish to mark as 'Out Of Order':\n \nDelay Install (Minutes): (0-60): 0//\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n\n \n Install Started for LA*5.2*62 :\n Jun 10, 2002@16:10:21\n \nBuild Distribution Date: Jun 10, 2002\n \n Installing Routines:......\n Jun 10, 2002@16:10:21\n \n Running Pre-Install Routine: PRE^LA62.\nASSOCIATED NOIS\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n *** Pre install completed ***\n \n Running Post-Install Routine: POST^LA62.\n---------------\n \n *** Post install started ***\n \n *** Post install completed ***\n \n --- No actions required for post install ---\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n NONE\n \n Updating KIDS files.......\n \n LA*5.2*62 Installed.\n Jun 10, 2002@16:10:22\n \n Install Message sent #xxxxx\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n \n \nTEST SITES\n----------\n Durham VAMC\n Milwaukee VAMC\n \n \nROUTINE SUMMARY\n===============\n \n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA62 N/A 4560523 **62** (Deleted by KIDS)\n LA7DVC 7338732 7449294 **53,62**\n LA7DVM 6949969 7061863 **53,58,62**\nPatch LA*5.2*62 implements support for patch HL*1.6*91 NAMESPACE field\n LA7VHL 4500486 4568355 **27,46,62**\n LA7VHLU 4469720 4487468 **46,62**\n \n List of preceding patches: 46, 58\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n(#16) in HL7 MESSAGE TEXT file (#772). The Laboratory HL7 clients\n=========================\n \n The install time for this patch is less than 10 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \nLaboratory Electronic Data Interchange (LEDI) and CareVue will pass the\n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\nnamespace "LA" in the HL7 APIs that create messages or acknowledgements.\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n 6. Perform the following steps if applicable:\n All Lab LEDI (LA7V*) related HL v1.6 LLPs should be shutdown.\n All CareVue related LLPs should be shutdown.\n Use the HL menu option Start/Stop Links [HL START] to shutdown\n these LLPs if they are running.\n \n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*62'. When prompted 'Want KIDS to\nDuring patch development, a software review identified the variable\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'YES'.\n \n All LA7V* and LA7D* protocols should be placed out of service during\n the install. This can be accomplished by answering the KIDS install\n questions:\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'YES'.\n\n
\nVISTA Laboratory Package patch LA*5.2*65 contains no changes to software\n \nInstallation example: \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LA*5.2*65 Loaded from Distribution 6/12/02@14:13:22\n => LA*5.2*65\n \nThis Distribution was loaded on Jun 12, 2002@14:13:22 with header of\n LA*5.2*65\n It consisted of the following Install(s):\n LA*5.2*65\n \nChecking Install for Package LA*5.2*65\nWill first run the Environment Check Routine, LA65\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*65\n \n \n \nASSOCIATED NOIS\nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// UCX/TELNET\n \n \n---------------\n Install Started for LA*5.2*65 :\n Jun 12, 2002@14:14:05\n \nBuild Distribution Date: Jun 12, 2002\n \n Installing Routines:...\n Jun 12, 2002@14:14:05\n \n Running Pre-Install Routine: PRE^LA65.\n \n ALB-0602-51133\n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No action required---\n \n *** Pre install completed ***\n \n Running Post-Install Routine: POST^LA65.\n \n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n \n Updating KIDS files.......\n \n LA*5.2*65 Installed.\n Jun 12, 2002@14:14:05\n \n Install Message sent #XXXXX\nTEST SITES\n----------\n Albuquerque VAMC\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n Milwaukee VAMC\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA65 N/A 4454886 **65** (Deleted by KIDS)\n LA7SMU1 6241668 6300206 **27,46,65** \n\n List of preceding patches: 46\n Sites should use CHECK^XTSUMBLD to verify checksums. \n \n \n************************************************************************\nPatch LA*5.2*65 corrects a null subscript error in routine LA7SMU1. The\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\nerror occurs when processing a HL7 Result (ORU) message that contains\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\nan invalid shipping manifest number. The routine will check for a valid\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\npointer to file LAB SHIPPING MANIFEST (#62.8) before attempting to\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. Perform the following steps if applicable:\n All Lab LEDI (LA7V*) related HL v1.6 LLPs should be shutdown.\n Use the HL menu option Start/Stop Links [HL START] to shutdown\n these LLPs if they are running.\n \n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\nassociate a test result with it's associated test on a shipping manifest.\n and select the package 'LA*5.2*65'. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n\n \n 8. On a mapped system, rebuild your map set.\n \n Note: Routine LA65 will be deleted after successful patch installation.\n \n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \n1. Restart any LA7V* HL v1.6 LLP's shutdown as part of the patch\ninstallation process. Use the Start LLP [HL START] option to restart\nLA7V* HL v1.6 LLP's.\n \n \n************************************************************************\n\n
\nVISTA Laboratory Package patch LA*5.2*63 contains no changes to software\n \n Select Installation Option: 6 Install Package(s)\n Select INSTALL NAME: LA*5.2*63 Loaded from Distribution 6/13/02@10:59:27\n => LA*5.2*63\n \nThis Distribution was loaded on Jun 13, 2002@10:59:27 with header of\n LA*5.2*63\n It consisted of the following Install(s):\n LA*5.2*63\nChecking Install for Package LA*5.2*63\nWill first run the Environment Check Routine, LA63\n \n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*63\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nASSOCIATED NOIS\nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n---------------\n Install Started for LA*5.2*63 :\n Jun 13, 2002@10:59:49\n \nBuild Distribution Date: Jun 13, 2002\n \n Installing Routines:...\n Jun 13, 2002@10:59:49\n \n Running Pre-Install Routine: PRE^LA63.\n \n ISD-0602-71432\n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No action required---\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n \n Installing OPTION........\n Jun 13, 2002@10:59:49\n \n Running Post-Install Routine: POST^LA63.\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*63 Installed.\n Jun 13, 2002@10:59:50\n \nTEST SITES\n Install Message sent #xxxxx\n----------\n Milwaukee VAMC\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n \n ------------ ------------ ----------- ------------\n LA63 N/A 4454878 **63** (Deleted by KIDS)\n LA7VOBX1 3981059 4057776 **46,61,63**\n \n List of preceding patches: 61\n Sites should use CHECK^XTSUMBLD to verify checksums. \n \n \n************************************************************************\n \nPatch LA*5.2*63 corrects a defect in LOINC encoding of test results in\nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system. Laboratory\n users should not use the lab verification options during patch\n installation. KIDS will disable the Laboratory test verification options.\n Patch installation should not occur during execution of the Clinical\n Case Registries scheduled task option Registry Update & Data Extraction\n [ROR TASK]. Suggested time to install: non-peak requirement hours.\nthe OBX segment of a Lab HL7 Result (ORU) message. The segment building \n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\nroutine LA7VOBX1 was failing to check and use a default LOINC code when\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \navailable if the test results have not been LOINC mapped. The software\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*63'. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\nwill check and use the default LOINC code when results are not LOINC\n YES//', choose 'NO'.\n \n KIDS will disable the following options:\n Enter/verify data (auto instrument) [LRVR]\n Enter/verify data (Work list) [LRVRW]\n Enter/verify data (Load list) [LRVRW2]\n Enter/verify/modify data (manual) [LRENTER]\n Group verify (EA, EL, EW) [LRGV]\n Bypass normal data entry [LRFAST]\n Fast Bypass Data Entry/Verify [LRFASTS]\nmapped.\n \n 7. On a mapped system, rebuild your map set.\n \n Note: Routine LA63 will be deleted after successful patch installation.\n \n \n \n************************************************************************\nInstallation example: \n \n\n
\nLab API's for extracting Chemistry, Cytopathology, Surgical Pathology\nand Microbiology data.\n\n
\nAssociated patches: (v)LA*5.2*17 <<= must be installed BEFORE `LA*5.2*23'\n \nThe INSTRUMENT NAME field is constructed as follows:\n 1. Instrument name from the #.01 Name field of the Auto Instrument file #62.4\n 2. Message type - "I" for Incoming, "O" for Outgoing\n 3. Lab Unique Id or Accession number\n - Outgoing messages always use the UID when building this name.\n - Incoming messages are based on what is found in the message.\n \n Examples: CX7-I-2061020105\n H747-O-3163120010\n MLA-I-45\nB: Sources for Patch\n \n Messages with no instrument name will use "UNKNOWN".\n Messages with no/unknown UID/accession number will use 0 (zero).\n Example: UNKNOWN-I-0\n \nUses the Kernel Browser if displayed on a CRT that supports the Browser,\notherwise uses FileMan captioned display.\n \n \nD. Problem: No option to start/stop the automatic download feature of the\n--------------------\nUniversal Interface if a site is using this capability.\n \n Resolution: Option LA7 ADL START/STOP added to LA7 MAIN MENU option.\nThis option can be used by sites utilizing the automatic download feature\nto start/restart/stop the automatic download process. When a site makes\nchanges to an auto instrument entry in the AUTO INSTRUMENT file (#62.4),\nand the entry is used for automatic downloading, the automatic download\nprocess needs to be restarted. If a site wishes to stop the automatic\ndownload process then it can be shutdown using this option.\n \n \n \nE. Problem: No option to send/resend an existing accession when using the\nautomatic download feature of the Universal Interface.\n \n Resolution: Option LA7 ADL SEND added to LA7 MAIN MENU option. This\noption allows for the manual selection of accession(s) for downloading to\nan instrument for those instruments utilizing automatic downloading. It\nwill place the selected accessions in the queue to be checked for\ndownloading to those instruments designated for automatic downloading.\n \n1. Summary of E3R\nF. Problem: When processing an incoming result message that had a specimen\nid that is an accession number, the accession date was being set to the\ncurrent date (DT). This caused results to be stored in LAH under the\nwrong accession when the default accession area for the instrument was\nnon-daily, i.e. monthly, quarterly, yearly.\n \n Resolution: Determine the current accession date when processing by\naccession number based on the accession transform (field # .05 in\nAccession file #68). Routine LA7UIIN1 modified.\n \n-----------------\nTEST SITES OPERATING SYSTEM UNIVERSAL INTERFACE PRODUCT\n---------- ---------------- ---------------------------\nBath VAMC MSM system Dawning ResultNet\nCentral Texas HCS DSM system Data Innovations Instrument Manager\nLebanon VAMC DSM system Data Innovations Instrument Manager\nLong Beach VAMC DSM system Dawning ResultNet\nMilwaukee VAMC DSM system Data Innovations Instrument Manager\n \n \nROUTINE SUMMARY\n None\n---------------\n \n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\n \n <tab>;;5.2;LAB MESSAGING;**[patch list]**;Feb 29, 1996\n \n CHECK^XTSUMBLD results\n \n Routine Name Before Patch After Patch Patch List\n \n ------------ ------------ ----------- ----------\n LA23 NA 3777015 23\n LA7ADL 9628408 10978189 17,25,23\n LA7ADL1 4708581 7046668 17,23\n LA7ADL2 NA 4107162 23\n LA7ADLS NA 2840510 23\n LA7UIIN 3932211 5181875 17,23\n LA7UIIN1 5975112 7157740 17,23\n LA7UIIN2 9803192 9927050 17,23\n LA7UTILA NA 11405877 23\n2. Summary of NOIS\n \n \n INSTALLATION INSTRUCTIONS\n -------------------------\n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n However the following conditions apply:\n 1. Accessioning should not be occurring,\n 2. The HL7 background job (HLLP) for the Lab Universal Interface should\n be stopped.\n------------------\n 3. The routine LA7UIIN to process incoming HL7 messages should not\n be running.\n 4. If using auto download, the routine LA7ADL should not be running.\n \n NOTE: MailMan and Kernel patches must be current on the target system to\n avoid problems loading and/or installing this patch.\n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\nAssociated patches: (v)LA*5.2*25 <<= must be installed BEFORE `LA*5.2*23'\n \n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n BRK-0696-11519\n \n 6. If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routine in your\n production account to the routine in the patch by using the 'Compare\n a Transport Global to Current System' option. These options can\n both be found under the 'Installation' menu.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*23'. When prompted 'Want to\n SDC-1296-60042\n DISABLE Scheduled Options, Menu Options, and Protocols? NO//',\n choose 'NO'.\n \n 8. MSM sites: You should respond 'YES' to 'Want to MOVE routines to\n other CPUs?' and specify CPUs. Alternatively, you may move the\n routines to your other systems after KIDS has finished the\n installation.\n \n 9. On a mapped system, rebuild your map set.\n \n LEB-1296-20455\n 10. Restart the HL7 background job(s) for the Lab Universal Interface if\n previously stopped.\n \n 11. Routine LA23 can be deleted after successful patch installation.\n **************************************************************************** \nBelow is an example of the dialogue seen during the KIDS install:\n \n \nSelect Installation Option: INstall Package(s)\nSelect INSTALL NAME: LA*5.2*23 Loaded from Distribution 12/13/96@15:50:40\n VDA-1296-N0470\n => LA*5.2*23 TEST V1\n \nThis Distribution was loaded on Dec 13, 1996@15:50:40 with header of\nLA*5.2*23 TEST V1\nIt consisted of the following Install(s):\nLA*5.2*23\n \n LA*5.2*23\nWill first run the Environment Check Routine, LA23\n \n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*23\n \n \n \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nC. Patch Description Detail\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// VIRTUAL TERMINAL\n \n \n Install Started for LA*5.2*23 :\n Dec 13, 1996@15:51:51\n \n Installing Routines:\n---------------------------\n Dec 13, 1996@15:52\n LA*5.2*23\n \n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION\n Dec 13, 1996@15:52:35\n \n Running Post-Install Routine: POST^LA23\n \n \nOption [LA7 MAIN MENU] was added to [LA INTERFACE] MENU\n \nMoving entries in global ^LA("ADL",uid) to ^LA("ADL","Q",uid)\n \n Post install completed\n \n Updating Routine file...\n \n Updating KIDS files...\n1. NOIS BRK-0696-11519\n \n LA*5.2*23 Installed.\n Dec 13, 1996@15:52:56\n \n \nInstall Completed\n \n \n \nSelect Installation Option:\n \n -------------------\n \nEnd of example install\n ****************************************************************************\nA. Problem: With consolidation of sites, laboratories are operating with\nmore than 99 accession areas. This has necessitated changes to the\nconstruction of the UID, (See related patch LR*5.2*129).\n\nPreviously this was a 10 character numeric string. To handle sites with\ngreater than 99 accession areas, the format has been changed to allow\nalphanumeric when designating the accession area identifier. This patch\nincorporates changes to the Lab UI to properly handle this new format.\n \n\n 1. Auto download process was performing a numeric check of UID which is no\n longer valid in routine LA7ADL.\n \n 2. Test result process was performing a numeric check of UID which is no\n longer valid in routine LA7UIIN1.\n \n Resolution: Altered check of UID to accept alphanumeric characters.\n \n \n2. NOIS SDC-1296-60042\nA: Patch Description Summary\n NOIS LEB-1296-20455\n -------------------\nA. Problem: When processing test result messages, if site set flag to only\nprocess tests that were ordered, it was possible for a result to not be\nprocessed when it was ordered. This would occur if variable LA7TREE was\ndefined and contained a value greater than 999.\n \n Resolution: Kill variable LA7TREE in routine LA7UIIN2 before call to\nroutine UNWIND^LA7UTIL which determine if test results are for a test that\nwas ordered.\n----------------------------\n \n \n3. NOIS VDA-1296-N0470\n -------------------\nA. Problem: When processing incoming HL7 messages to the Lab UI, the\nroutine LA7UIIN1 was setting up the call to LAGEN to create an entry in the\nLAH global using the default accession area defined in the auto instrument\nfile. With the introduction of the UID, the lab package is implementing the\nability to run multiple accession areas on one instrument. The call to\nLAGEN should build the accession area from the UID if available and use the\nThis patch will address nine issues that have been reported on NOIS or\ndefault accession area only when an accession number is passed.\n \n Resolution: Modified routine LA7UIIN1 to build the accession area from\nthe UID when available before making call to LAGEN to create entry in LAH\nglobal.\n \n \n4. Developer Identified\n --------------------\nA. Problem: Option LA7 PRINT LAB UI ERROR contained a misspelling in the\ndeveloper identified.\nmenu text.\n \n Resolution: Menu text changed from "Print Lab Universal Inteface Log" to\n"Print Lab Universal Interface Log".\n \n \nB. Problem: Option LA7 MAIN MENU was released in patch LA*5.2*17 but not\nattached to the normal Lab menu system.\n \n Resolution: Option LA7 MAIN MENU is added to the option LA INTERFACE.\n \n \n \nC. Problem: When troubleshooting a problem with the Universal Interface,\nthere was no option to display a message.\n \n Resolution: Option LA7 PRINT UI MESSAGE added to LA7 MAIN MENU option to\nallow user to display/print Universal Interface messages from file #62.49,\nLA7 MESSAGE QUEUE. User can select 1-20 messages. Messages can be selected by\nusing either the #.01 field - MESSAGE NUMBER or #5 field - INSTRUMENT NAME.\n \n\n\nRefer to the National Patch Module\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*64 does not\nsoftware functionality, therefore RISK is none.\n \n d. Mail bulletin: LA7 ORDER STATUS CHANGED\n Mail bulletin created by Laboratory package when processing a LEDI\n interface type HL7 message.\n\n Bulletin will be generated for the following conditions:\n \n - When an order acknowledgment (ORR) message contains laboratory\n test order status changes that indicate the order is not correct or\n cannot be performed/completed. Currently only supported on LEDI\n\n interfaces with DoD facilities.\n \n - When an order result (ORU) message indicates that a laboratory\n test has been added by the reference laboratory to the original order.\n \n12. Corrected a spelling error in set of codes for LAB SHIPPING\nCONFIGURATION file (#62.9), COLLECTING FACILITY'S SPEC ID field (#.05).\n \n13. Internal review determined that the specimen container was not printing\non working copies of shipping manifests. When printing working versions\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\nof a shipping manifest the specimen container will be printed.\n \n14. A new error bulletin #47 has been added to LA7 MESSAGE LOG BULLETINS\nfile (#62.485). When processing LEDI orders if any of the following are\nincomplete - local test, local urgency, local topography or local collection\nsample then the bulletin will be triggered. This is to insure that orders\nsent by the collecting facility are not missed when processed during LEDI\nReferral Patient Accessioning. If this bulletin is triggered it indicates\nthat the host site's shipping configuration is not properly configured to\nprocess orders from it's collecting site.\nmade, no specific validation requirements exist as a result of installation\n \n \nASSOCIATED E3R\n--------------\n E3R #17914, PROVIDER CONTACT NUMBERS ON MANIFEST\n E3R #17904, LEDI BETWEEN VA AND DOD SITES\n E3R #18036, UNABLE TO PURGE SHIPPING MANIFESTS\n \nASSOCIATED NOIS\n---------------\nof this patch.\n ISA-0398-10075 \n \n \nTEST SITES\n----------\n Albuquerque VAMC - VMS/DSM and VMS/Cache\n Boston HCS - VMS/DSM and VMS/Cache\n El Paso HCS - NT/Cache and VMS/Cache\n Hines VAMC - VMS/DSM and VMS/Cache\n Honolulu VAMC - NT/Cache\n\n Manchester VAMC - NT/Cache and VMS/Cache\n Milwaukee VAMC - VMS/DSM\n North Chicago VAMC - VMS/DSM\n Salt Lake City VAMC - VMS/DSM\n San Diego VAMC - VMS/DSM and VMS/Cache\n Upstate New York HCS - VMS/DSM and VMS/Cache\n\n\n INSTALLATION FILES:\n ==================\n=======================================================================\n The following software and documentation files are exported as part of\n this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n \nLAB_LEDI_III.KID LA*5.2*64 KIDS build ASCII\n LR*5.2*286 KIDS build\n\n\nThis patch adds support for sending/receiving Laboratory Electronic\nLAB_LEDI_III_IG.PDF LABORATORY ELECTRONIC DATA BINARY\n INSTALLATION GUIDE \n\nLAB_LEDI_III_IMP_UG.PDF LABORATORY ELECTRONIC DATA BINARY\n IMPLEMENTATION AND USER GUIDE \n\n The files listed above may be obtained via FTP. The preferred method is\n to FTP the files from:\n \n download.vista.domain.ext\nData Interchange (LEDI) orders/results with Department of Defense (DoD)\n \n This transmits the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as\n follows:\n \n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\nfacilities and implements enhancements to general LEDI functionality.\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n \n ------------ ------------ ----------- ------------\n LA64 N/A 5936440 **64** (Deleted by KIDS)\n LA7PURG 3834284 4599657 **27,64**\n LA7SBCR1 4924406 5434157 **27,46,64**\n LA7SBCR2 2564479 2593598 **27,46,64**\n LA7SCE 11501726 13339015 **27,46,61,64**\n LA7SM2 12143125 16026225 **46,64**\n LA7SMB 14649107 12799432 **27,46,64**\n LA7SMP 11746903 12373162 **27,45,46,64**\n LA7SMP0 9303222 10961615 **46,64**\n \n LA7SMPXL 3215234 4682314 **27,42,46,64**\n LA7SMU 7104257 7255424 **27,46,64**\n LA7SMU1 6300206 6311796 **27,46,65,64**\n LA7SMU2 5290542 7549846 **46,64**\n LA7SRR 6233015 7637904 **46,64**\n LA7UTILA 10237097 10662046 **23,27,46,64**\n LA7VHL 4568355 5811383 **27,46,62,64**\n LA7VHLU 4487468 5914870 **46,62,64**\n LA7VHLU1 2323481 3267492 **46,61,64**\n LA7VHLU2 4100825 4356637 **46,61,64**\n1. The process of building orders in the LAB PENDING ORDERS ENTRY file\n LA7VHLU3 2007360 2799232 **46,64**\n LA7VHLU4 5424804 4836094 **46,64**\n LA7VHLU5 5541950 7828952 **46,64**\n LA7VIN1 5261630 5855016 **46,64**\n LA7VIN1A N/A 13987419 **64**\n LA7VIN2 5808892 8339412 **46,64**\n LA7VIN3 2061956 3081309 **46,64**\n LA7VIN4 7936019 12162627 **46,64**\n LA7VIN5 5205707 10570600 **46,64**\n LA7VIN5A 5039195 8695039 **46,64**\n(#69.6) has been enhanced to use additional information from the HL7 Order\n LA7VLL 5170411 6390054 **27,51,55,64**\n LA7VMSG 3253314 5080421 **27,50,56,46,64**\n LA7VMSG1 8227296 8679432 **56,46,61,64**\n LA7VOBR 2129056 2455598 **46,64**\n LA7VOBRA 5326634 8044290 **46,64**\n LA7VOBX 2088674 2633711 **46,64**\n LA7VOBX1 4057776 4535705 **46,61,63,64**\n LA7VOBX2 4350324 4309250 **46,64**\n LA7VOBX3 5240738 6460347 **46,64**\n LA7VOBXA 6416931 6372995 **46,70,64**\n(ORM) message. It will store the following information when available in the\n LA7VORC 1565653 1713732 **46,64**\n LA7VORM 6471896 12116142 **27,42,46,64**\n LA7VORM1 7594289 9199759 **27,51,46,61,64**\n LA7VORM3 6787219 7257153 **46,64**\n LA7VORU 6241961 8366274 **27,46,61,64**\n LA7VORU1 4734718 4842743 **46,64**\n LA7VORU2 1962290 2531397 **46,64**\n LA7VORUA 2199285 2385822 **61,64**\n LA7VPID 4123683 4823699 **46,64**\n LA7VSET 15979413 14514051 **27,51,55,46,64**\nLAB PENDING ORDERS ENTRY file (#69.6):\n LA7VSET1 9065449 7835525 **27,51,55,46,64**\n LA7VSTP 6079680 4597827 **27,44,51,46,64**\n LA7VSTP1 3317926 3042573 **27,46,64**\n LAGEN 8522786 8715369 **1,17,22,27,47,46,64**\n \n List of preceding patches: 46, 61, 62, 63, 65, 70\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n - patient's race\n=========================\n \nSee LABORATORY ELECTRONIC DATA INTERCHANGE III (LEDI III) INSTALLATION GUIDE\n LA*5.2*64/LR*5.2*286\n - order comments\n - test results that accompany an order \n\nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n2. The new option Start a Shipping Manifest [LA7S MANIFEST START] will\nallow a manifest to be started without performing a manifest build.\nSpecimens can then be added manually, instead of automatically, using\noption Add/Remove a Shipping Manifest Test [LA7S MANIFEST TEST ADD/REMOVE].\n\n3. The new option Edit Relevant Clinical Information [LA7S MANIFEST\nCLINICAL INFO] is used to enter relevant clinical information that\nshould accompany a test order on a manifest.\n \n4. Converted supported API calls $$FMDATE^HLFNC and $$HLDATE^HLFNC to\n\nrecommended Kernel supported API's $$HL7TFM^XLFDT and $$FMTHL7^XLFDT\nrespectively.\n \n5. Routine LA7VHL changed to call HL7 supported API RSPINIT^HLFNC2 to\nobtain message delimiters that HL7 package will use when building MSH\nheader of application acknowledgement message. Previous call to\nINIT^HLFNC would return incorrect headers under certain conditions.\nSee patch HL*1.6*101 for additional information.\n \n6. Routine LA7VMSG1 changed to check if $QUERY of ^TMP global has\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*64 does not\nreturned a null value. Under certain conditions an illegal function call\nerror could be observed.\n \n7. Changed routines LA7VLL, LA7VSTP, and LA7VSTP1 to setup LA7V* logical\nlinks without <space> between "LA7V" and station number. Allows HL7 package\nto display logical links for DoD sites which utilize DoD DMIS ID codes as\nfacility identifiers similar to VA station numbers. HL7 package only\ndisplays first 8 characters of logical link name. Option LEDI Setup\n[LA7V SETUP] will only support creation of TCP logical links.\n \nalter or modify any software design safeguards or safety critical elements\n8. Routine LA7PURG is changed to purge shipping manifests from LAB\nSHIPPING MANIFEST file (#62.8) when all related accessions have been\npurged from ACCESSION file (#68) (E3R #18036). Orders in the LAB PENDING\nORDERS ENTRY file (#69.6) are purged when the date completed is >365\ndays, when the order transmitted date is >720 days or when the order\ntransmitted date is >360 and the order status is Results/data Received.\n \n9. When selecting a shipping manifest the list of entries to select\nfrom will list the manifests in inverse order with the most recent\nbeing displayed first. (E3R #18036)\nfunctions.\n \n10. Requesting provider's office phone, voice and digital pager numbers\nwill be printed on working copies of shipping manifest. (E3R #17914)\n \n11. Four new alerts/mail bulletins are generated when processing LEDI\nHL7 messages. These alerts and corresponding bulletins are addressed to\nthe mail group designated to receive the NEW RESULTS alert specified\nby the site in LA7 MESSAGE PARAMETER file (#62.48) for LEDI type\ninterfaces.\n \n\n a. Mail bulletin: LA7 ABNORMAL RESULTS RECEIVED\n Mail bulletin created by Laboratory package when processing a LEDI\n interface type HL7 result (ORU) message which contains laboratory\n testing results that are flagged as critical or abnormal. Values\n that are critical will always trigger the alert and bulletin. Values\n that are abnormal low or high will be triggered when site has flagged\n the corresponding test in AUTO INSTRUMENT file (#62.4), NOTIFY ABNORMAL\n FLAGS field (#22) within the CHEM TEST multiple (#30) for the interface.\n \n b. Mail bulletin: LA7 AMENDED RESULTS RECEIVED\nRISK ANALYSIS: Changes made by patch LA*5.2*64 have no effect on Blood Bank\n Mail bulletin created by Laboratory package when processing a LEDI\n interface type HL7 result (ORU) message which contains laboratory\n testing results that are flagged as amended.\n \n c. Mail bulletin: LA7 UNITS/NORMALS CHANGED\n Mail bulletin created by Laboratory package when processing a LEDI\n interface type HL7 result (ORU) message which contains laboratory\n test result units and/or normals different from values specified for\n test in LABORATORY TEST file (#60) and which are flagged to be used\n for reference testing purposes.\n\n
\nBlood Bank Clearance\n\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n \n The install will automatically disable the following options:\n \n Accession order then immediately enter data LR ACC THEN DATA\n Batch data entry (chem, hem, tox, etc.) [LRSTUF]\n Bypass normal data entry [LRFAST]\n Enter/verify data (Load list) [LRVRW2]\nRISK ANALYSIS: Changes made by patch LA*5.2*71 have no effect on Blood\n Enter/verify data (Work list) [LRVRW]\n Enter/verify data (auto instrument) [LRVR]\n Enter/verify/modify data (manual) [LRENTER]\n Fast Bypass Data Entry/Verify [LRFASTS]\n Group verify (EA, EL, EW)[ LRGV]\n Special test accessioning [LRNONCOM]\n \n 6. On a mapped system, rebuild your map set.\n \n Note: Routine LA71 will be deleted after successful patch installation.\nBank software functionality, therefore RISK is none.\n \n \nINSTALLATION EXAMPLE\n====================\n \nSelect Installation Option:\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: Install Package(s)\n\nSelect INSTALL NAME: LA*5.2*71 Loaded from Distribution 1/31/05@14:21:40\n => LA*5.2*71\n \nThis Distribution was loaded on Jan 31, 2005@14:21:40 with header of\n LA*5.2*71\n It consisted of the following Install(s):\n LA*5.2*71\nChecking Install for Package LA*5.2*71\nWill first run the Environment Check Routine, LA71\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*71\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nmade, no specific validation requirements exist as a result of installation\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*71 :\nof this patch.\n Jan 31, 2005@14:22:11\n \nBuild Distribution Date: Jan 31, 2005\n \n Installing Routines:...\n Jan 31, 2005@14:22:11\n \n Running Pre-Install Routine: PRE^LA71.\n \n Sending install started alert to mail group G.LMI\n \n \n *** Pre install started ***\n \n --- No action required---\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION...........\n \n Jan 31, 2005@14:22:11\n \n Running Post-Install Routine: POST^LA71.\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \nNOIS NCH-0105-417985 reported the inability to verify corrected \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*71 Installed.\n Jan 31, 2005@14:22:11\n \n Install Message sent #xxxx\n====================\nLaboratory Electronic Data Interchange (LEDI) results when the reference\n(host) laboratory removes the previously reported result and changes the\nresult to 'pending'. The result of 'pending' was not being sent to the\ncollecting facility via LEDI HL7 messaging.\n \nThis patch allows users at the collecting facility who are verifying\nreference laboratory results to release amended (corrected) results\nthat are 'pending'.\n \n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*71 does not\n \n ASSOCIATED E3R\n --------------\n None\n \n ASSOCIATED NOIS\n ---------------\n NCH-0105-417985/Remedy ticket HD0000000071220\n \n \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n TEST SITES\n ----------\n Boston HCS\n Durham VAMC\n Hines VAMC\n Milwaukee VAMC\n North Chicago VAMC\n \n \nROUTINE SUMMARY\nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA71 N/A 4588676 **71** (Deleted by KIDS)\n LA7VOBX1 4535705 4442510 **46,61,63,64,71**\n\n LA7VORU 8366274 8469558 **27,46,61,64,71**\n \n List of preceding patches: 64\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*71 does not\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \nalter or modify any software design safeguards or safety critical elements\n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LA*5.2*71):\nfunctions.\n a. Print Transport Global\n b. Backup a Transport Global\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*71'. When prompted 'Want KIDS to\n\n
\nBlood Bank Clearance\n \n LA7PCFG N/A 16069384 **67**\n LA7POC N/A 3454800 **67**\n LA7UXQA 7260762 5623537 **27,67**\n LA7VHL 5811383 6113752 **27,46,62,64,67**\n LA7VIN 1398763 3056962 **46,67**\n LA7VIN1A 13987419 14019173 **64,67**\n LA7VIN4 12162627 12188308 **46,64,67**\n LA7VIN5A 8695039 9628469 **46,64,67**\n LAGEN 8715369 8613602 **1,17,22,27,47,46,64,67**\n \nRISK ANALYSIS: Changes made by patch LA*5.2*67 have no effect on Blood Bank\n List of preceding patches: 64\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\nSee LABORATORY POINT OF CARE (POC) INTERFACE INSTALLATION AND USER GUIDE\n PATCH LA*5.2*67 AND PATCH LR*5.2*290 Version 5.2 JUNE 2005\n \nSoftware and Documentation Retrieval Locations\nsoftware functionality, therefore RISK is none.\n==============================================\n \nNOTE: All sites are encouraged to use the File Transfer Protocol (FTP)\ncapability. Use the FTP address "download.vista.domain.ext" (without the\nquotes) to connect to the first available FTP server where the files are\nlocated.\n \n \nVistA Point of Care (POC) Interface Patches LR*5.2*290 and LA*5.2*67\nsoftware and Installation and User Guide are available at the following\n \nOffice of Information Field Offices (OIFOs) ANONYMOUS.SOFTWARE directories:\n \n \nOI FIELD OFFICE FTP ADDRESS DIRECTORY\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \nSoftware and Documentation Retrieval Format\n========================================\n===========================================\n \nVistA Laboratory Point of Care (POC) Interface Patches LR*5.2*290 and\nLA*5.2*67 software and documentation files are exported in the following\nretrieval formats:\n \n \nFile Names Contents Retrieval Formats\n========== ======== =================\n \n \nLAB_POC.KID KIDS build ASCII\n \nLAB_52_LR290_LA67_POC_IUG.pdf Laboratory Point of Care BINARY\n (POC) Interface Patches\n LR*5.2*290 and LA*5.2*67\n Installation and User Guide\n \nLAB _52_LR290_LA67_POC_IUG.doc Laboratory Point of Care BINARY\n (POC) Interface Patches\n LR*5.2*290 and LA*5.2*67\nThis patch adds support for Laboratory Point of Care (POC) interfaces.\n Installation and User Guide\n \nLAB_52_POC_HL7_SPEC.doc Laboratory HL7 Interface BINARY\n Specification for Point of\n Care (POC)\n \nLAB_52_POC_HL7_SPEC.pdf Laboratory HL7 Interface BINARY\n Specification for Point of\n Care (POC)\n \nIt utilizes existing functionality provided by Laboratory Universal\n \nPOST-INSTALLATION INSTRUCTIONS\n------------------------------\n\nSee LABORATORY POINT OF CARE (POC) INTERFACE INSTALLATION AND USER GUIDE\n PATCH LA*5.2*67 AND PATCH LR*5.2*290 Version 5.2 JUNE 2005\n \n \nINSTALLATION EXAMPLE\n====================\nInterface (UI) and Laboratory Electronic Data Interchange (LEDI) software.\n \nSee LABORATORY POINT OF CARE (POC) INTERFACE INSTALLATION AND USER GUIDE\n PATCH LA*5.2*67 AND PATCH LR*5.2*290 Version 5.2 JUNE 2005\nIt supports the transmission, processing and storing of POC test results\n====================\nin the VistA Laboratory package. The ability of POC interfaces to subscribe\nto VistA HL7 ADT messages for patient demographics and location information\nis provided as needed. Support for 5 separate POC interfaces is provided.\n \n \nNOTE: THIS PATCH WILL BE INSTALLED WITH PATCH LR*5.2*290\n \n \n1. NOIS DAN-0105-41616/Remedy HD0000000071211 reported undefined DUZ("AG") \nvariable when processing Lab HL7 messages. The following new 'non-human'\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*67 does not\nentries will be installed in NEW PERSON file (#200). These entries have\nthe approval of VA VistA Data Base Administrator.\n \n NAME: LRLAB,HL NAME COMPONENTS: 200\n SIGNATURE BLOCK PRINTED NAME: HL LRLAB\n \n NAME: LRLAB,POC NAME COMPONENTS: 200\n SIGNATURE BLOCK PRINTED NAME: POC LRLAB\n \nUser LRLAB,HL will be used by Laboratory when processing HL7 messages \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\nto insure a consistent Kernel environment with respect to the system-wide\nDUZ variable array.\n \nUser LRLAB,POC will be used by Laboratory when creating POC orders and\naccessions to indicate that these orders and accessions were created by\nthe POC interface background process. Sites should assign to the user\nLRLAB,POC those divisions that will be used by POC interfaces to accession\nPOC results into VistA Laboratory package.\n \n \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nAdditionally, the following changes have been made:\n \n2. Removed prompt to save alert when viewing lab messaging alert in routine\nLA7UXQA. This functionality is now part of Kernel Alert processing.\n \n3. When logging lab messaging processing errors, FileMan DIE call in\nroutine LA7LOG was converted to FileMan DBS call.\n \n4. Lab messaging will now check that LA7TASK NIGHTY option is scheduled\nin TaskMan. If not scheduled then an alert notifying members of mail group\n \nLAB MESSAGING will be generated. The alert message will read "Lab Messaging\n- Option LA7TASK NIGHTY is not scheduled in TaskMan". Documentation\nregarding tasking can be found in the VistA Laboratory LEDI User Guide and\non-line via the DESCRIPTION field of the OPTION file (#19) for this entry.\n \n5. Result of 'canc' was not being processed if the test was configured to\nonly accept 'final' type results (HL7 Table 0085 - Observation result\nstatus codes interpretation codes C, F, or U. Changed routine LA7VIN5A to\naccept and process "canc' result with status code X.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*67 does not\n \nASSOCIATED E3R\n--------------\n \nASSOCIATED NOIS/Remedy\n------------------------------\nDAN-0105-41616/HD0000000071211 \n \n \nTEST SITES\nalter or modify any software design safeguards or safety critical elements\n----------\n \n Madison VAMC\n New Jersey HCS\n Salt Lake City VAMC\n Shreveport VAMC\n Upstate New York System HCS\n \n \nROUTINE SUMMARY\nfunctions.\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LA67 N/A 8196499 **67** (Deleted by KIDS)\n LA7LOG 9009311 8393092 **17,27,67**\n\n\nBlood Bank Team Coordination\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 3. Use the 'Verify Checksum in Transport Global' option and verify\n that all routines have the correct checksums.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\nRISK ANALYSIS: Changes made by patch LA*5.2*72 have no effect on Blood \n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*72'\n \n When prompted\n 'Want KIDS to Rebuild Menu Trees Upon Completion of Install?' \nBank software functionality, therefore RISK is none.\n choose 'NO'. Note: Responding "Yes" to the prompt for rebuilding\n menu trees can significantly increase install time.\n \n When prompted \n 'Want KIDS to INHIBIT LOGONs during the install? \n choose 'NO'.\n \n When prompted \n 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//'\n \n choose 'NO' unless site has additional local laboratory \n options that should be disabled during install.\n \n \n \nINSTALLATION EXAMPLE\n====================\n \nSelect KIDS OPTION: INSTALL PACKAGE(S) \nSelect INSTALL NAME: LA*5.2*72 Loaded from Distribution \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n7/12/05@14:19:30\n => LA*5.2*72 v1\n \nThis Distribution was loaded on Jul 12, 2005@14:19:30 with header of \n LA*5.2*72 v1\n It consisted of the following Install(s):\n LA*5.2*72\nChecking Install for Package LA*5.2*72\nWill first run the Environment Check Routine, LA72\n \nmade, no specific validation requirements exist as a result of \n \n --- Environment Check is Ok --- \n \nInstall Questions for LA*5.2*72\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n \n Install Started for LA*5.2*72 : \ninstallation of this patch. \n Jul 12, 2005@14:20\n \nBuild Distribution Date: Jul 11, 2005\n \n Installing Routines:\n Jul 12, 2005@14:20\n \n Running Pre-Install Routine: PRE^LA72\n \n Sending install started alert to mail group G.LMI \n************************************************************************\n \n *** Pre install started *** \n \n --- No actions required for pre install --- \n \n LA*5.2*72 \n-------------------------------------------------------------------------\n *** Pre install completed *** \n \n Running Post-Install Routine: POST^LA72\n \n \n *** Post install started *** \n \n *** Post install completed *** \n \n Sending install completion alert to mail group G.LMI \n \n Updating Routine file...\n \n Updating KIDS files...\nSites reported errors logged in the error trap when receiving lab results \n \n LA*5.2*72 Installed. \n Jul 12, 2005@14:20\n \n Install Message sent #80481\n-------------------------------------------------------------------------\n +------------------------------------------------------------+\n 100% I 25 50 75 I\nComplete +------------------------------------------------------------+\n \n============================\nback from another VA host lab via Lab Electronic Data Interchange (LEDI):\n \nInstall Completed\n \n \n$ZE= <UNDEFINED>PRDID+11^LA7VIN5A\n \n . I $P(LA7PRDID,LA7CS,LA7I+2)="99VA4" S \nLA74=$$LKUP^XUAF4($P(LA7PRDID,LA7CS,I))\n \n \nThe following portion of code in PRDID^LA7VIN5A has been changed to \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*72 does not \nreference the correct variable (LA7I instead of I): \n \n**PREVIOUS CODE**\nF LA7I=1,4 D Q:LA74 \n. I $P(LA7PRDID,LA7CS,LA7I+2)="99VA4" S \nLA74=$$LKUP^XUAF4($P(LA7PRDID,LA7CS,I))\n. I 'LA74 S LA74=$$LKUP^XUAF4($P(LA7PRDID,LA7CS,I+1)) \n. I 'LA74 S LA74=$$FINDSITE^LA7VHLU2($P(LA7PRDID,LA7CS),1,1) \n. I 'LA74 S LA74=$$FINDSITE^LA7VHLU2($P(LA7SFAC,LA7CS),1,1)\n \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \n \n**NEW CODE**\nF LA7I=1,4 D Q:LA74\n. I $P(LA7PRDID,LA7CS,LA7I+2)="99VA4" S \nLA74=$$LKUP^XUAF4($P(LA7PRDID,LA7CS,LA7I))\n. I 'LA74 S LA74=$$LKUP^XUAF4($P(LA7PRDID,LA7CS,LA7I+1))\n. I 'LA74 S LA74=$$FINDSITE^LA7VHLU2($P(LA7PRDID,LA7CS),1,1)\n. I 'LA74 S LA74=$$FINDSITE^LA7VHLU2($P(LA7SFAC,LA7CS),1,1)\n \n \nDIRECTIVE 2004-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nAssociated Remedy:\n===============\nHD0000000099666\nHD0000000102341 (duplicate)\n \n \nAssociated E3R:\n===============\nN/A\n \n \n \nTest Sites\n==========\nFayetteville, NC (565) (medium)\nHines (578) (large)\nNorth Chicago (556) (medium)\nNorthern Indiana HCS (610) (medium) (integrated) \n \n \nROUTINE SUMMARY\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*72 does not \n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;AUTOMATED LAB INSTRUMENTS;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n LA7VIN5A 9628469 9655113 46,64,67,72\n LA72 N/A 4388949 72 (D)\n \nalter or modify any software design safeguards or safety critical \n (D) -- Routine deleted by KIDS after installation\n List of preceding patches: 67\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 2 minutes. This patch\n should be installed when Laboratory users are off the system.\nelements functions.\n \n Suggested time to install: non-peak requirement hours.\n The installation should NOT be queued.\n \n NOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n\n
\n Blood Bank Team Coordination\n RISK ANALYSIS: Changes made by patch LA*5.2*66 have no effect on Blood Bank\n \n \n 5) For Lab UI messages, any units/reference ranges received from an instrument\n are discarded as the units/reference ranges from the associated LABORATORY TEST\n file (#60) are used.\n \n \n 6) For Lab UI messages, abnormal flags received from an instrument are not\n stored.\n \n software functionality, therefore RISK is none.\n 7) The Lab UI Auto Download process (routine LA7ADL) is changed to support the\n FileMan system wide lock timeout via supported API LOCK^DILF.\n \n 8. To provide for data entry consistency, results received via this\n interface are validated against the input transform for the data field\n used to store the test results. Test results received from an instrument\n that do not conform to the input transform for the related Lab Data Name\n will be rejected.\n \n If SET OF CODES is utilized as the data type for a particular interfaced\n \n test, the internally stored code needs to be brought into alignment with\n what the instrument is reporting. If the instrument sends a result that\n does not match what is entered in the SET OF CODES that result is\n considered not to be verifiable data.\n \n \n \n Associated Remedy:\n ===============\n HD0000000192820 lab DI at Lyons is not working Resolution:\n VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made,\n Resolved by site.\n thru UI No software changes required.\n HD0000000069104 NETWORKING DATA INNOVATIONS INSTRUMENT MGR\n HD0000000069215 LAB DI - migrate from v1.5 to v1.6 TCP\n HD0000000069217 Slow DHCP processing of lab instrument data\n \n Associated E3R:\n ===============\n N/A\n \n no specific validation requirements exist as a result of installation of this\n \n Test Sites\n ==========\n MILWAUKEE, WI -VAMC (large)\n NEW JERSEY HCS (large, integrated)\n TUCSON, AZ -VAMC (large)\n \n \n NEW OPTION:\n ========\n patch.\n \n [LA7 UI SETUP] Lab Universal Interface Setup\n Allows configuring Lab Universal Interface entries (LA7UI*) in the\n LAB MESSAGE PARAMETER file (#62.48) and corresponding entries in the\n AUTO INSTRUMENT file (#62.4) which use the Lab Universal Interface.\n \n This option is attached to menu option Lab Universal Interface Menu\n [LA7 MAIN MENU].\n \n \n \n PROTOCOLS:\n ==========\n The following protocols are new:\n \n LA7UI ORM-O01 EVENT 2.2\n ORM event driver for Lab Universal Interface (HL7 v1.6 upgrade)\n using HL7 messaging v2.2\n \n LA7UI ORM-O01 SUBS 2.2\n ORM subscriber for Lab Universal Interface (HL7 v1.6 upgrade) using\n ************************************************************************\n HL7 messaging v2.2\n \n LA7UI ORU-R01 SUBS 2.2\n ORU subscriber for Lab Universal Interface (HL7 v1.6 upgrade) using\n HL7 messaging v2.2\n \n The following are ORU event drivers for Lab Universal Interface (HL7\n v1.6 upgrade) using HL7 messaging v2.2 :\n LA7UI1 ORU-R01 EVENT 2.2\n LA7UI2 ORU-R01 EVENT 2.2\n \n LA7UI3 ORU-R01 EVENT 2.2\n LA7UI4 ORU-R01 EVENT 2.2\n LA7UI5 ORU-R01 EVENT 2.2\n LA7UI6 ORU-R01 EVENT 2.2\n LA7UI7 ORU-R01 EVENT 2.2\n LA7UI8 ORU-R01 EVENT 2.2\n LA7UI9 ORU-R01 EVENT 2.2\n LA7UI10 ORU-R01 EVENT 2.2\n \n \n This patch upgrades the Lab Universal Interface (UI) from VistA's Health Level\n \n Documentation Retrieval:\n ========================\n Documentation is available on the ANONYMOUS.SOFTWARE directory at one of\n the following Office of Information (OI) Field Offices. Sites may\n retrieve documentation in one of the following ways:\n \n 1. The preferred method is to FTP the files from:\n download.vista.domain.ext\n which will transmit the files from the first available FTP server.\n ============================\n Seven (HL) v1.5 to HL v1.6 including the use of v1.6 TCP/IP functionality. It\n \n 2. Sites may also elect to retrieve documentation directly from a\n specific server as follows:\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n \n The documentation distribution includes:\n \n supports the current Lab UI HL7 Interface Specifications based on the HL7\n File Name Contents Retrieval Formats\n --------- -------- -----------------\n LAB_52_LA66_INSTALL_USER_GUIDE.doc\n Laboratory UI HL V1.6 Upgrade\n Installation and User Guide\n Patch LA*5.2*66 BINARY\n \n LAB_52_LA66_INSTALL_USER_GUIDE.pdf\n Laboratory UI HL V1.6 Upgrade\n Installation and User Guide\n Standard V2.2.\n Patch LA*5.2*66 BINARY\n \n LAB_52_LA66_HL7_SPECIFICATIONS.doc\n Laboratory UI HL V1.6 Upgrade\n Installation and User Guide\n Patch LA*5.2*66 BINARY\n \n LAB_52_LA66_HL7_SPECIFICATIONS.pdf\n Laboratory UI HL V1.6 Upgrade\n Installation and User Guide\n \n Patch LA*5.2*66 BINARY\n \n \n 3. Documentation can also be retrieved from the VistA Documentation\n Library (VDL) at http://www.domain.ext/vdl/\n \n \n \n INSTALLATION INSTRUCTIONS\n =========================\n The current UI interface using the HL v1.5 interface will continue to function\n \n The install time for this patch is less than 2 minutes. This patch\n should be installed when Laboratory users are off the system.\n \n The Lab Universal Interface Auto Download should be shutdown before\n installing this patch. This can be done via the Start/Stop Auto\n Download Background Job [LA7 ADL START/STOP] menu option.\n \n The KIDS environment check determines if the Lab UI Auto Download\n process is currently running:\n after patch installation. The transition to the HL V1.6 interface can be\n \n If it is running it will be automatically shutdown during patch\n installation and automatically restarted after patch installation.\n \n If the Lab UI Auto Download process is not running at patch\n installation time then KIDS will take no action with the Lab UI Auto\n download process.\n \n After patch installation is complete, check the status of the Lab UI\n Auto Download process using the option Start/Stop Auto Download\n accomplished after patch installation on a connection by connection basis.\n Background Job [LA7 ADL START/STOP] and configure to normal\n operational setting (see step 6 below).\n \n \n Suggested time to install: non-peak requirement hours.\n The installation should NOT be queued.\n \n Note: Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n When possible, switching from the old interface to the new interface should be\n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 3. Use the 'Verify Checksum in Transport Global' option and verify\n that all routines have the correct checksums.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n done on a per instrument basis instead of all instruments at once. Follow the\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LA*5.2*66'.\n \n When prompted\n 'Want KIDS to Rebuild Menu Trees Upon Completion of Install?'\n post installation instructions to convert an interface to the HL V1.6\n choose 'NO'. Note: Responding "Yes" to the prompt for rebuilding\n menu trees can significantly increase install time.\n \n When prompted\n 'Want KIDS to INHIBIT LOGONs during the install?\n choose 'NO'.\n \n When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//'\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*66 does not contain\n interface.\n choose 'NO' unless the site has additional laboratory options that\n should be disabled during install.\n \n 6. If the Lab Universal Interface Auto Download process was stopped\n manually, restart it via the Start/Stop Auto Download Background\n Job [LA7 ADL START/STOP] menu option.\n \n If the process was stopped by the KIDS install itself, the process\n will restart automatically.\n \n \n \n Note: Routine LA66 will be deleted after successful patch installation.\n \n \n IMPLEMENTATION INSTRUCTIONS\n ------------------------------\n See LABORATORY UNIVERSAL INTERFACE (UI) HEALTH LEVEL (HL) V1.6 UPGRADE\n INSTALLATION AND USER GUIDE PATCH LA*5.2*66\n \n \n Note: New Generic Instrument Manager (GIM) software must be obtained\n INSTALLATION EXAMPLE\n ====================\n \n Select Installation Option: Install Package(s) Select INSTALL NAME: LA*5.2*66\n Loaded from Distribution 9/13/07@15:03:06\n => LA*5.2*66 ;Created on Sep 13, 2007@13:07:05\n \n This Distribution was loaded on Sep 13, 2007@15:03:06 with header of\n LA*5.2*66 ;Created on Sep 13, 2007@13:07:05\n It consisted of the following Install(s):\n from the vendor in order for this new interface to work.\n LA*5.2*66 Checking Install for Package LA*5.2*66 Will first run the\n Environment Check Routine, LA66\n \n Sending install started alert to mail group G.LMI\n Shutting down Lab Universal Interface Auto Download Job\n ..........\n N O T E: If you abort this installation\n restart the Lab Universal Interface background job.\n \n --- Environment is okay ---\n \n \n Install Questions for LA*5.2*66\n \n Incoming Files:\n \n \n 62.48 LA7 MESSAGE PARAMETER (including data) Note: You already have\n the 'LA7 MESSAGE PARAMETER' File. I will OVERWRITE your data with mine.\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// n NO\n Before the release of this patch lab instruments interfaced through TCP/IP were\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// n NO Want to DISABLE\n Scheduled Options, Menu Options, and Protocols? NO// n NO\n \n Enter the Device you want to print the Install messages. Enter a '^' to abort\n the install.\n \n DEVICE: HOME// TELNET\n \n using a non-supported modification of an HL7 routine. This patch will allow\n \n Install Started for LA*5.2*66 :\n Sep 13, 2007@15:03:27\n \n Build Distribution Date: Sep 13, 2007\n \n Installing Routines:\n Sep 13, 2007@15:03:28\n \n Running Pre-Install Routine: PRE^LA66\n sites to interface their automated testing devices via supported TCP/IP\n *** Pre install started ***\n *** Pre install completed ***\n \n Installing Data Dictionaries:\n Sep 13, 2007@15:03:28\n \n Installing Data:\n Sep 13, 2007@15:03:28\n \n Installing PACKAGE COMPONENTS:\n functionality and will allow the sites to manage these interfaces using the HL7\n \n Installing HL LOGICAL LINK\n \n Installing HL7 APPLICATION PARAMETER\n \n Installing PROTOCOL\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n v1.6 package's tools.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n Located in the LA7 (LAB MESSAGING) namespace.\n \n any changes to the VISTA BLOOD BANK Software as defined by VHA DIRECTIVE\n \n Installing OPTION\n Sep 13, 2007@15:03:29\n \n LA*5.2*66\n ------------------------------------------------------------------------\n Running Post-Install Routine: POST^LA66\n *** Post install started ***\n *** Updating facility name for LA7UI* entries in file #771 ***\n *** Updating facility name completed ***\n --- No actions required for post install ---\n HL7 messages are HL7 version 2.2 and the messaging is composed of ORM~O01 and\n Restarting Lab Universal Interface Auto Download Job\n *** Post install completed ***\n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LA*5.2*66 Installed.\n Sep 13, 2007@15:03:32\n ORU~R01 messages. Messaging uses original acknowledgement mode. ORM messages\n \n Install Message sent #nnnnn\n ------------------------------------------------------------------------\n --------------------------------------------------------------\n 100% | 25 50 75 |\n Complete --------------------------------------------------------------\n \n \n Install Completed\n use "LA7LAB" as the Sending Application and "LA7UIx" as the Receiving\n Application. ORU messages use "LA7UIx" as the Sending Application and "LA7LAB"\n as the Receiving Application.\n \n The PROTOCOL (#101), HL7 APPLICATION PARAMETER (#771), HL LOGICAL LINK (#870)\n and LA7 MESSAGE PARAMETER (#62.48) files each have ten entries using a naming\n convention that contains "LA7UIx" (where "x" is an integer) such as "LA7UI1\n 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n ORU-R01 EVENT 2.2" and "LA7UI1." This convention allows the site to interface\n with multiple generic instrument managers.\n \n To setup an auto-instrument, the MESSAGE CONFIGURATION field (#8) of the AUTO\n INSTRUMENT file (#62.4) must be set to the appropriate LA7 MESSAGE PARAMETER\n file (#62.48) entry (ie LA7UI1). Also, the FILE BUILD ENTRY field (#93) should\n equal "EN" and the FILE BUILD ROUTINE field (#94) should equal "LA7UID".\n \n In order to send/receive messages the configuration needs to be set ACTIVE via\n its STATUS field (#2) of LA7 MESSAGE PARAMETER file (#62.48). The\n \n configuration must also specify which routine is used to process messages in\n LA7 MESSAGE PARAMETER file (#62.48) PROCESS DOWNLOAD field (#6) which should be\n set to "D EN^LA7UIO" for Lab Universal Interfaces.\n \n AUTO INSTRUMENT (#62.4)\n MESSAGE CONFIGURATION (#8) = LA7 MESSAGE PARAMETER entry (ie LA7UI1)\n FILE BUILD ENTRY (#93) = EN\n FILE BUILD ROUTINE (#94) = LA7UID\n \n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*66 does not alter or\n LA7 MESSAGE PARAMETER (#62.48)\n STATUS (#2) = ACTIVE\n PROCESS DOWNLOAD (#6) = D EN^LA7UIO\n \n \n 1) The v1.5 interface constructed ORM message segments that were not in\n compliance with the HL7 standard. Previously an ORC segment was followed by\n one or more OBR segments. The HL7 standard specifies that ORC/OBR segments\n should exist as a pair so in this interface each ordered test will be sent in\n the ORM message as an ORC/OBR segment pair. Example:\n modify any software design safeguards or safety critical elements functions.\n PID...\n PV1...\n ORC...\n OBR...\n ORC...\n OBR...\n \n \n 2) HL7 message data is now checked for conflicts with HL7 delimiters. If data\n conflicts with the message's delimiters then the data with be escape encoded\n \n according to HL7 rules.\n \n \n 3) In an ORM message, OBR-18 is constructed as an HL7 string data type. The\n HL7 v1.5 interface constructed it as a coded element (CE) data type.\n \n \n 4) For Lab UI messages, if the specimen received does not match the HL7 0070\n table, an interface error message will be created unless the specimen is\n related to the LAB CONTROL NAME file (#62.3).\n\n
\nBlood Bank Clearance\n CYTOPATHOLOGY (#63.09)\n "CH", "MI", "SP", "CY", "EM".\n \n TIMESTAMP: 59725,36770 SENDING APPLICATION: LA7LAB\n TRANSACTION MESSAGE TYPE: ORU EVENT TYPE: R01\n MESSAGE STRUCTURE: ORU_R01 ACCEPT ACK CODE: AL\n APPLICATION ACK TYPE: NE VERSION ID: 2.4\n RESPONSE PROCESSING ROUTINE: D ACK^LA7VHL\nSUBSCRIBERS: LA7 LAB RESULTS TO HDR (SUB)\n \n \n \nNAME: LA7 LAB RESULTS TO HDR (SUB) ITEM TEXT: Send Lab Results to HDR\n TYPE: subscriber \n DESCRIPTION: This protocol should be attached to the HL7 event protocol\n LA7 LAB RESULTS AVAILABLE (EVN). See this protocol for further information.\n \n This subscriber protocol is used by the Laboratory package to indicate to\n the HL package to send laboratory results to the VA Health Data Repository\n (HDR).\n \n It utilizes the "Router" Subscriber Protocol supported by the VistA HL\nAll of the above changes have been reviewed by the VISTA Blood Bank\n package. The routing logic uses the value of the parameter passed into the\n router to determine which Laboratory package subscript should be sent to\n the HDR.\n \n Examples:\n \n ROUTING LOGIC: D RTR^LA7HDR("CH;") will only send to HDR-IMS results\n associated with Laboratory "CH" subscript.\n \n ROUTING LOGIC: D RTR^LA7HDR("MI;") will only send to HDR-IMS results\nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE\n associated with Laboratory "MI" subscript.\n \n ROUTING LOGIC: D RTR^LA7HDR("CH;MI;SP;") will only send to HDR-IMS results\n associated with Laboratory "CH", "MI", and "SP" subscripts.\n \n TIMESTAMP: 59056,40125 RECEIVING APPLICATION: LA7HDR\n EVENT TYPE: R01 LOGICAL LINK: VDEFVIE4\n RESPONSE MESSAGE TYPE: ACK SENDING FACILITY REQUIRED?: YES\n RECEIVING FACILITY REQUIRED?: YES ROUTING LOGIC: D RTR^LA7HDR("CH;")\n \ncontrol functions.\n NOTE: This subscriber protocol is distributed with the ROUTING LOGIC\n disabled. See post-installation instructions for guidance to\n enable the protocol.\n \n2. The following option is added to the OPTION file (#19)\n \nNAME: LA7 HDR RECOVER MENU TEXT: Recover/Transmit Lab HDR Result\nMessages\n TYPE: run routine \n PACKAGE: AUTOMATED LAB INSTRUMENTS\n \n DESCRIPTION: Option to recover from failed Lab HDR ORU Result message \ngeneration and/or transmission failure. This option allows the user to\nselect those VistA Laboratory accessions that need to be transmitted to\nthe VA HDR and other subscribers of the VistA Laboratory Result Available\nHL7 message capability via the protocol Lab Results Available Event [LA7\nLAB RESULTS AVAILABLE (EVN)].\n \nIf the original message generation/transmission failed due to system or \ncommunication problems then using this option will allow the generation of\nnew HL7 messages with the results associated with the selected \nRISK ANALYSIS: Changes made by patch LA*5.2*68 have no effect on Blood\naccessions. Accessions can be selected using the human-readable accession\ndesignation (area abbreviation modified date accession number - "CH 1225\n100") or the accession's associated 10 character unique identifier (UID).\n \n ROUTINE: RECOVER^LA7HDR \n UPPERCASE MENU TEXT: RECOVER/TRANSMIT LAB HDR RESUL\n \nThis option is assigned to the Lab liaison menu option [LRLIAISON] and\ncan be assigned to other uses as needed that support/monitor message \ntransmission to the VA HDR and other subscribers.\nBank software functionality, therefore RISK is none.\n \n3. The LA7HDR routine, if the configuration LA7HDR in LA7 MESSAGE\nPARAMETER file (#62.48) has an active status, queues the record for\ntransmission to the HDR via a HL7 ORU result message which is transmitted\nby the HL package to any subscribers of event protocol LA7 LAB RESULTS\nAVAILABLE (EVN) in addition to the HDR subscriber LA7 LAB RESULTS TO HDR\n(SUB).\n \n The LA7 LAB RESULTS TO HDR (SUB) subscriber protocol uses the logical\nlink VDEFVIE4. This is a router subscriber protocol which determines\n \nwhich Lab HL7 messages are sent to the HDR. See protocol description\nfor further information.\n \n \n4. Anatomic Pathology is not "CPRS-aware" and is unable to notify CPRS of\nrelease of anatomic pathology results. HDR will be notified of \navailability of anatomic pathology results via three new-style\ncross-references in LAB DATA file (#63). These indexes will also trigger\ngeneration of the Lab HL7 ORU message if this capability has been enabled.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*68 does not\n The three new cross-references are:\n \nSubfile #63.02\n \n New-Style Indexes:\n \n AC (#98) FIELD MUMPS ACTION\n Short Descr: Notify HDR and others that this report is available.\n Description: This MUMPS cross-reference triggers the sending of this\n report to the Health Data Repository (HDR) and other\n====================\nalter or modify any software design safeguards or safety critical elements\n subscribers when electron microscopy results are \n released.\n Set Logic: D APQ^LA7HDR(DA(1),"EM",DA)\n Kill Logic: Q\n X(1): REPORT RELEASE DATE (63.02,.11) (Subscr 1) (forwards)\n \nSubfile #63.08\n \n New-Style Indexes:\n \nfunctions.\n AD (#95) FIELD MUMPS ACTION\n Short Descr: Notify HDR and others that this report is available.\n Description: This MUMPS cross-reference triggers the sending of this\n report to the Health Data Repository (HDR) and other\n subscribers when surgical pathology results are \n released.\n Set Logic: D APQ^LA7HDR(DA(1),"SP",DA)\n Kill Logic: Q\n X(1): REPORT RELEASE DATE/TIME (63.08,.11) (Subscr 1)\n (forwards)\n \n \nSubfile #63.09\n \n New-Style Indexes:\n \n AD (#96) FIELD MUMPS ACTION\n Short Descr: Notify HDR and others that this report is available.\n Description: This MUMPS cross-reference triggers the sending of this\n report to the Health Data Repository (HDR) and other\n subscribers when cytology results are released.\nPOTENTIAL IMPACT ON SITES: This patch contains changes to 0 routines and\n Set Logic: D APQ^LA7HDR(DA(1),"CY",DA)\n Kill Logic: Q\n X(1): REPORT RELEASE DATE/TIME (63.09,.11) (Subscr 1)\n (forwards) \n \n \n5. Microbiology results. The current Laboratory package does not support\nLOINC encoding of microbiology results. A default encoding is enabled\nto LOINC encode standard microbiology tests and antibiotics.\nLOINC codes valid as of version 2.14.\n1 file identified in Veterans Health Administration (VHA) Directive 99-053,\n \nDefault mapping of NLT/LOINC codes to standard fields within the \nMICROBIOLOGY (#5) multiple of LAB DATA file (#63):\n \n \n Test Order NLT Result NLT LOINC Code\n Bacteriology report (#11) 87993.0000\n Gram stain (#11.6) 87993.0000 87754.0000 664-3\n Bacteriology organism (#12) 87993.0000 87570.0000 11475-1\n Bacteria colony count (#12,1) 87719.0000 564-5\ngroup B listing. The changes have no effect on Blood Bank functionality or\n Parasite report (#14) 87505.0000\n Parasite organism (#16) 87505.0000 87576.0000 17784-0\n Mycology report (#18) 87994.0000\n Fungal organism (#20) 87994.0000 87578.0000 580-1\n Fungal colony count (#20,1) 87994.0000 87723.0000 19101-5\n Mycobacterium report (#22) 87995.0000\n Acid Fast stain (#24) 87995.0000 87756.0000 11545-1\n Acid Fast stain quantity (#25) 87995.0000 87583.0000 11545-1\n Mycobacterium organism (#26) 87995.0000 87589.0000 543-9\n Mycobacterium colony count (#26,1) 87995.0000 87719.0000 564-5\nmedical device control functions. There is no adverse potential to sites.\n Virology report (#33) 87996.0000\n Viral agent (#36) 87996.0000 87590.0000 6584-7\n \n Bacteriology or mycobacterium (TB) organism's susceptibilities -\n is based on local site's mapping of NATIONAL VA LAB CODE field (#64)\n in ANTIMICROBIAL SUSCEPTIBILITY file (#62.06) and the related default\n LOINC code associated with this VA NLT code. Use option Map/Unmap \n Antimicrobial Default LOINC Code [LR LOINC MAP ANTIMICROBIAL] to\n configure the default LOINC code for each antibiotic.\n \n \n6. Surgical Pathology results. The current Laboratory package does not\nsupport LOINC encoding of surgical pathology results.\nLOINC codes valid as of version 2.14.\n \nDefault mapping of NLT/LOINC codes to standard fields within the \nSURGICAL PATHOLOGY (#8) multiple of LAB DATA file (#63):\n \n Test Order NLT Result NLT LOINC Code\n Specimen (#.012) 88515.0000 88539.0000 22633-2\n Brief clinical history (#.013) 88515.0000 88542.0000 22636-5\n========================================\n Preoperative diagnosis (#.014) 88515.0000 88544.0000 10219-4\n Operative findings (#.015) 88515.0000 88546.0000 10215-2\n Postoperative diagnosis (#.016) 88515.0000 88547.0000 10218-6\n Gross description (#1) 88515.0000 88549.0000 22634-0\n Microscopic description (#1.1) 88515.0000 88563.0000 22635-7\n Frozen section (#1.3) 88515.0000 88569.0000 22635-7\n Surgical path diagnosis (#1.4) 88515.0000 88571.0000 22637-3\n Supplementary report (#1.2) 88515.0000 88589.0000 22639-9\n Specimen weight (#2) 88515.0000 81233.0000 3154-2\n \n \n \n7. Cytology results. The current Laboratory package does not support\nLOINC encoding of cytology results.\nLOINC codes valid as of version 2.14.\n \nDefault mapping of NLT/LOINC codes to standard fields within the \nCYTOPATHOLOGY (#9) multiple of LAB DATA file (#63):\n \n Test Order NLT Result NLT LOINC Code\n Specimens (#.012) 88593.0000 88539.0000 22633-2\nVISTA Laboratory Package patch LA*5.2*68 contains changes to software\nThis patch supports the VA Health Data Repository (HDR) effort,\n Brief clinical history (#.013) 88593.0000 88542.0000 22636-5\n Preoperative diagnosis (#.014) 88593.0000 88544.0000 10219-4\n Operative findings (#.015) 88593.0000 88542.0000 10215-2\n Postoperative diagnosis (#.016) 88593.0000 88547.0000 10218-6\n Gross description (#1) 88593.0000 88549.0000 22634-0\n Microscopic examination (#1.1) 88593.0000 88563.0000 22635-7\n Supplementary report (#1.2) 88593.0000 88589.0000 22639-9\n Cytopathlogy diagnosis (#1.4) 88593.0000 88571.0000 22637-3\n \n \nallowing changes to LAB DATA file (#63) to be transmitted to the HDR \n8. Electron microscopy results. The current Laboratory package does not\nsupport LOINC encoding of electron microscopy.\n \nDefault mapping of NLT/LOINC codes to standard fields within the \nEM (#2) multiple of LAB DATA file (#63):\n \n Test Order NLT Result NLT LOINC Code\n Specimens (#.012) 88597.0000 88057.0000 22633-2\n Brief clinical history (#.013) 88597.0000 88542.0000 22636-5\n Preoperative diagnosis (#.014) 88597.0000 88544.0000 10219-4\nvia a VistA Laboratory HL7 Result (ORU) message.\n Operative findings (#.015) 88597.0000 88542.0000 10215-2\n Postoperative diagnosis (#.016) 88597.0000 88547.0000 10218-6\n Gross description (#1) 88597.0000 88549.0000 22634-0\n Microscopic examination (#1.1) 88597.0000 88563.0000 22635-7\n Supplementary report (#1.2) 88597.0000 88589.0000 22639-9\n EM diagnosis (#1.4) 88597.0000 88571.0000 22637-3\n \n \n9. It corrects a defect identified during patch development with\nprocessing input parameters for the GCPR^LA7QRY API. If the input\n \nparameter LA7SC specified specific subscripts to search then the API\nwould search those subscripts for any search code even when specific \nsearch codes were passed to the API in the LA7SC array.\n \n10. Converts several FileMan DBS calls on INSTITUTION file (#4) to using\nsupported API's $$NS^XUAF4 and $$STA^XUAF4.\n \n11. It corrects a defect identified during patch development with\nprocessing input parameters for the GCPR^LA7QRY API. If the input\nparameters LA7SDT and LA7EDT specified specific results available date\nAdditionally, it provides the capability for the transmission of the HL7\nrange the API could return anatomic pathology results which have not\nbeen released. This API has been corrected to check the REPORT RELEASE\nDATE field (#.11) for subscripts "CY", EM", "SP".\n \n12. Remedy ticket HD0000000096207 reported a problem with the error code\nreturned by the Lab API LA7QRY. A FileMan DBS error code was erroroneously\nbeing returned to the calling application. Routines LA7QRY, LA7QRY1, and \nLA7QRY2 has been modified to use a different name spaced variable LA7QERR\nto return to the calling application any error conditions. Additionally,\nroutine LA7VOBX1 has been modified to use another name spaced variable\nORU message containing patient laboratory results to subscribers of the HL7\nLA7DDERR to handle FileMan DBS error conditions related to FileMan data\ndictionary calls.\n \n13. It corrects a defect identified by MyHeatheVet regarding encoding of \nthe following fields in the OBR segment relating to anatomic pathology \nreports:\n OBR-32 - Principal result interpreter\n OBR-33 - Assistant result interpreter\n OBR-34 - Technician\n OBR-35 - Transcriptionist\nevent protocol LA7 LAB RESULTS AVAILABLE (EVN) as these results are made\n \nThe name component of these fields was being encoded with the wrong HL7\ndelimiter (component separator). The name component will be encoded with \nthe subcomponent separator per the HL7 standard.\n \n14. To integrate the VistA-Office EHR with the regular VistA system as\n well as adding functionality also available in the Indian Health Services\n system, the GQPR^LA7QRY API has been modified to allow for VistA-Office\n EHR to use data specifically geared toward clinical operations, whether\n in a hospital or a standalone clinic. The use of an Electronic\navailable within the Laboratory package. The following subscripts are\n Health Record number as opposed to a SSN for patient identification is\n supported as an identifier accepted as input to this API.\n \n The entry point GCPR^LA7QRY remains unchanged. However, the parameter\n used to pass the patient identifier should contain a 2nd piece indicating\n the type of identifier contained in the 1st piece.\n \n It supports the following types of patient identifiers\n SS = Social Security number\n PI = VA MPI Integration Control Number\nsupported by the event: "CH", "MI", "SP", "CY", "EM". See post-install\n MR = medical record number of patient in file PATIENT/IHS (#9000001)\n \n To regular VistA users this modification will not be seen.\n \n15. To support HDR-Historical which uses the GRPR^LA7QRY API to extract\nhistorical laboratory test results, the input parameter LA7SC to GCPR^LA7QRY\nsupports a 2nd piece. When the 2nd piece of input parameter LA7SC equals\n1 the API will return results encoded using VUID's when available.\n \n16. Remedy tickets HD0000000141922/HD0000000148089 reported a problem with\ninstructions for enabling this capability.\nfailure of generation of MailMan bulletin LA7 ORDER STATUS CHANGED at\ncollection laboratory facility. Routine LA7VMSG1 changed to set interface\ntype to set flag in Lab HL7 ORU message indicating an order status change\nto trigger bulletin generation at collecting site.\n \n \nASSOCIATED E3R\n--------------\n None\n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n \n \nASSOCIATED REMEDY\n-----------------\n HD0000000096207\n HD0000000141922\n HD0000000148089\n \nTEST SITES\n----------\n Atlanta VAMC\n \n Biloxi VAMC\n Boston HCS\n El Paso VAMC\n Houston VAMC\n Milwaukee VAMC\n North CHhicago VAMC\n Northhampton VAMC\n Palo Alto HCS\n Philadelphia VAMC\n Pittsburgh HCS\n****************************************************************************\n Puget Sound HCS\n Salt Lake City VAMC\n South Texas HCS\n VA Greater Los Angeles HCS\n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minute. This patch\n \n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \nPatch LA*5.2*68 allows the HL7 ORU message containing patient laboratory \n 1. LOAD TRANSPORT GLOBAL\n ---------------------------------------\n Choose the PackMan message containing this patch and invoke the\n INSTALL/CHECK MESSAGE PackMan option. \n \n \n 2. START UP KIDS\n Start up the Kernel Installation and distribution System\n Menu [XPD MAIN]:\n Edits and Distribution ...\nresults to be transmitted to the subscriber, LA7 LAB RESULTS TO HDR \n Utilities ...\n Installation ...\n \n Select Kernel Installation & Distribution System Option: Installation\n ----\n 1 Load a Distribution\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n(SUB). This subscriber protocol is used to transmit laboratory results to \n 6 Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n \n Select Installation Option:\n \n 3. Select Installation Option:\n -------------------------------\n NOTE: The following are OPTIONAL - (When prompted for the\n INSTALL NAME, enter LA*5.2*68):\nthe VA HDR.\n a. Backup a Transport Global - This option will create a\n backup message of any routines exported with this patch.\n It will not backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option\n will allow you to view all changes that will be made when this\n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will\n allow you to ensure the integrity of the routines that are in\n the transport global.\n \n \n 4. Select Installation Option: Install Package(s)\n ------------------\n **This is the step to start the installation of this KIDS patch:\n \n a. Choose the Install Package(s) option to start the patch install.\n (When prompted for the INSTALL NAME, enter LA*5.2*68.)\n b. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//' answer NO (unless otherwise indicated)\n c. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\nThe HDR Team will contact the Chief of IRM at each site to set up the \n and Protocols? NO//' answer NO (unless otherwise indicated)\n \n \n \n Note: Routine LA68 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \nChanges include: \ncoordination of lab extraction (LA*5.2*68) and the activation of the \n***************************************************************************\n \nAfter the installation of Patch LA*5.2*68, do not activate the LA7 LAB \nRESULTS TO HDR (SUB) subscriber protocol until contacted by the HDR team\n \n***************************************************************************\n \n \nNOTE: Use the following steps only when activating the transmission of\nlaboratory data to the VA HDR and/or interfacing to a Commercial Off the \nsubscriber (HDR).\nShelf System (COTS) or other VistA subscriber. No further action is\nrequired, if there is no requirement to activate this interface.\n \n To activate messaging to the VA HDR perform steps 1, 2, and 3.\n To activate messaging to COTS and other VistA subscribers\n perform steps 1 and 4.\n \n1. To utilize the building and transmission of HL7 Lab ORU result messages.\n \n Enable the configuration 'LA7HDR' in LA7 MESSAGE PARAMETER file\n \n (#62.48). This is accomplished by setting the field STATUS (#2) to\n 'ACTIVE' using VA File Manager. Setting this field to 'INACTIVE' will\n turn off generation of this Lab HL7 message.\n \n Select VA FileMan Option: Enter or Edit File Entries\n \n INPUT TO WHAT FILE: LA7 MESSAGE PARAMETER// 62.48 LA7 MESSAGE PARAMETER\n EDIT WHICH FIELD: ALL// STATUS\n THEN EDIT FIELD:\n \nThe coordination of extracting existing laboratory data (HDR historical) \n Select LA7 MESSAGE PARAMETER CONFIGURATION: LA7HDR\n STATUS: INACTIVE// ACTIVE ACTIVE\n \n \n2. Activation of transmission to HDR requires coordination with your\n assigned HDR Implementation Manager (IM). Sites should not activate the\n LA7 LAB RESULTS TO HDR (SUB) subscriber until notified by the HDR\n team. The coordination of extractions of existing laboratory data will\n be started at the same time the configuration of the LA7 LAB RESULTS TO\n HDR (SUB) subscriber to ensure that there is an overlap of laboratory\nand the configuration of the LA7 LAB RESULTS TO HDR (SUB) subscriber will \n results. This overlap is done to ensure all laboratory results are in\n the HDR.\n \n a. Set up VDEFVIE4 link for Laboratory data transmission\n \n Use the HL7 Main Menu, Filers option to look at the setup for \n VDEFVIE3. \n \n Copy down the IP and port number used for VDEFVIE3.\n \nbe started at the same time. This will ensure that there is an overlap of \n Use the HL7 Main Menu, Filers option to edit VDEFVIE4. \n \n Enable auto startup and add the same IP and port numbers used for\n VDEFVIE3.\n \n Use the HL7 Main Menu, Start/Stop Links option to start the VDEFVIE4\n link.\n \n Use the HL7 Main Menu, Site Parameters option to select VDEF view\n and add VDEFVIE4 to the view.\nlaboratory results between the real time extraction of lab data and the \n \n \n b. To activate the interface to the VA HDR use Protocol Edit option\n [HL EDIT INTERFACE] on the HL package Interface Developer Options\n [HL MENU INTERFACE TK] menu option and edit protocol LA7 LAB RESULTS\n TO HDR (SUB). Go to the second ScreenMan screen and edit the field\n ROUTING LOGIC and remove the leading ";" character and enter the\n 'save' command to save the changes to the protocol.\n \n HL7 SUBSCRIBER PAGE 2 OF 2\nhistorical extraction of lab data.\n LA7 LAB RESULTS TO HDR (SUB)\n---------------------------------------------------------------------------\n \n RECEIVING APPLICATION: LA7HDR\n \n RESPONSE MESSAGE TYPE: ACK EVENT TYPE: R01\n \n SENDING FACILITY REQUIRED?: YES RECEIVING FACILITY REQUIRED?: YES\n \n SECURITY REQUIRED?:\n \n \n LOGICAL LINK: VDEFVIE4\n \n PROCESSING RTN:\n \n ROUTING LOGIC: ;D RTR^LA7HDR("CH;") <-- remove leading ";" character\n____________________________________________________________________________\n \nCOMMAND: Press <PF1>H for help Insert\n \nIf a VA site activates the LA7 LAB RESULTS TO HDR (SUB) subscriber before \nAfter the change the field should look like:\n ROUTING LOGIC: D RTR^LA7HDR("CH;")\n \n3. To transmit Lab HL7 ORU result messages to another system, i.e.\n Commercial Off the Shelf System (COTS).\n \n a. Create a HL7 subscriber protocol as documented in HL7 Site Manager &\n Developer Manual version 1.6*56\n \n b. Attach this protocol as a subscriber to HL7 event protocol LA7 LAB\n New style indexes have been created for the following sub-files\nthe historical extraction of existing laboratory data, the real time \n RESULTS AVAILABLE (EVN). Use Protocol Edit option [HL EDIT INTERFACE]\n on the HL package Interface Developer Options [HL MENU INTERFACE TK]\n menu option to add this subscriber.\n \n \n4. Controlling message generation and transmission.\n \n Notify the HDR Project Office in the event that this interface is\n deactivated and the interface to the HDR was previously activated\n \nextraction of lab data at the VA site may not be synchronized with the \n a. To turn off message building and transmission to ALL subscribers\n of event protocol LA7 LAB RESULTS AVAILABLE (EVN).\n Disable the configuration 'LA7HDR' in LA7 MESSAGE PARAMETER file\n (#62.48). This is accomplished by setting the field STATUS (#2) to\n 'INACTIVE' using VA File Manager Enter or Edit File Entries [DIEDIT].\n Setting this field to 'INACTIVE' will turn off generation of this Lab\n HL7 message.\n \n b. To turn off message transmission to a specific subscriber.\n On the HL package, Interface Developer Options [HL MENU INTERFACE\nHDR data.\n TK] menu option, use the Protocol Edit [HL EDIT INTERFACE] option to\n remove the related subscriber protocol from the event protocol LA7\n LAB RESULTS AVAILABLE (EVN).\n \n For the VA HDR, remove subscriber protocol LA7 LAB RESULTS TO HDR\n (SUB).\n \n \n \n \n \nINSTALLATION EXAMPLE\n====================\n \nSelect Installation Option: 6 Install Package(s) \nSelect INSTALL NAME: LA*5.2*68 Loaded from Distribution 2/4/05@10:21\n => LA*5.2*68\n \nThis Distribution was loaded on Feb 04, 2005@10:21 with header of\n LA*5.2*68\n It consisted of the following Install(s):\nIf you have questions regarding installation or implementation,\n LA*5.2*68\nChecking Install for Package LA*5.2*68\nWill first run the Environment Check Routine, LA68\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LA*5.2*68\n \nIncoming Files:\ncontact the HDR Project Office.\n \n \n 62.48 LA7 MESSAGE PARAMETER (including data)\nNote: You already have the 'LA7 MESSAGE PARAMETER' File.\nI will OVERWRITE your data with mine.\n \n \n 63 LAB DATA (Partial Definition)\nNote: You already have the 'LAB DATA' File.\n \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES//\n \n \nWant KIDS to INHIBIT LOGONs during the install? NO// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? NO// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\nOnce the HDR Project Office confirms that installation and implementation \n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LA*5.2*68 :\n Feb 04, 2005@10:21:55\n \nBuild Distribution Date: Feb 04, 2005\n \n Installing Routines:.............\nwas accomplished successfully, you must log a Remedy ticket for any\n Feb 04, 2005@10:21:55\n \n Running Pre-Install Routine: PRE^LA68.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No action required---\n \nsubsequent problems encountered.\n *** Pre install completed ***\n \n Installing Data Dictionaries: ...\n Feb 04, 2005@10:21:55\n \n Installing Data:\n Feb 04, 2005@10:21:55\n \n Installing PACKAGE COMPONENTS:\n \n of the LAB DATA file (#63):\n \n Installing HL7 APPLICATION PARAMETER...\n \n Installing PROTOCOL..\n Located in the LA7 (LAB MESSAGING) namespace..\n Located in the LA7 (LAB MESSAGING) namespace..\n Located in the LA7 (LAB MESSAGING) namespace..\n Feb 04, 2005@10:21:55\n \n Running Post-Install Routine: POST^LA68.\n \n*****************************************************************************\n *** Post install started ***\n \n *** Clearing facility name for LA7LAB entry in file #771 ***\n \n *** Clearing facility name completed ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LA*5.2*68 Installed.\n Feb 04, 2005@10:21:55\n \n Install Message sent #xxxx\n \n1. The following protocols are added to the PROTOCOL file (#101)\n \nNAME: LA7 LAB RESULTS ACTION\n ITEM TEXT: Lab process results for HL7 messaging\n TYPE: action \n PACKAGE: AUTOMATED LAB INSTRUMENTS\n ELECTRON MICROSCOPY (#63.02)\n DESCRIPTION: Action protocol to setup sending lab results to HL7 message\n subscribers via protocol LA7 LAB RESULTS AVAILABLE (EVN) - Lab Results\n Available Event. This protocol should be attached to protocol LAB RESULTS\n => EXTERNAL PACKAGE [LR7O ALL EVSEND RESULTS] which is an extended action\n protocol triggered by the lab result verification process.\n ENTRY ACTION: D QUEUE^LA7HDR TIMESTAMP: 59056,40855\n \n \nNAME: LA7 LAB RESULTS AVAILABLE (EVN) ITEM TEXT: Lab Results Available Event\n TYPE: event driver \n SURGICAL PATHOLOGY (#63.08)\n DESCRIPTION: A VistA Laboratory package HL7 ORU result message is created\n and sent by the HL package for transmission to any subscribers of event\n protocol LA7 LAB RESULTS AVAILABLE (EVN).\n \n It provides the capability for the generation of a Laboratory HL7 ORU\n message containing patient laboratory results to subscribers of the HL7\n event protocol LA7 LAB RESULTS AVAILABLE (EVN) as these results are made\n available within the Laboratory package.\n \n The following subscripts are supported by the event:\n\n\nRefer to National Patch Module.\n\n
\n1. Erroneous nodes created in File 68 for MICRO with VITEK result \n interface.\n\n
\nResolves zero isolate problem on Vitek Literal Interface.\n\n
\n1) TICKET 965986 LRMIEDZ Subscript Error\n \nThe patch modifies code in VITEK LITERAL routine LAMIVTL4 that uses \nimproper subscripting in a $O to set a variable. As a consequence, the \nvariable is set to null. This null value later causes a Subscript Errror \nwhen LAMIVTL4 calls UNDO^LRMIEDZ and an attempt is made to access the \nACCESSION FILE (#68) using it.\n\n
\nThe patch modifies code in two (2) routines to correct HL7 escape \ncharacters in OBX result segments and properly handle pipe "|" characters \nin remarks from lab instruments. \n\n
\nThis patch addresses three (3) issues of Laboratory Electronic Data \n \n \nRoutine LA7VOBRB is modified to send back the collecting site's override \nSNOMED code in the result transaction.\n \nRoutine: LA7VOBRB\n \nComponents:\n===========\nN/A\n \n3. Override SNOMED codes are not sent with results.\n ==================== Installation Instructions ====================\n This patch may be loaded with users on the system. You may wish to \n install it during non-peak hours. Installation will take less than 1 \n minute. \n \n NOTE: Kernel patches must be current on the target system to avoid \n problems loading and/or installing this patch.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify\n that all routines have the correct checksums.\n \nAssociated NSR(s):\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a Transport\n Global' option at this time. You may also compare the routines in\n your production account to the routines in the patch by using the\n==================\n 'Compare a Transport Global to Current System' option.\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu \n and select the package 'LA*5.2*85.\n \n If prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//, \n choose 'NO'. \n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? NO//', choose 'NO'.\nN/A\n \nAssociated Remedy ticket(s):\n==========================\n \nInterchange (LEDI) HL7 interfaces:\n1. INC000000900556 - Result transaction SNOMED code application errors\n2. INC000000917708 - Override SNOMED code issue on incoming orders\n3. INC000001080712 - Override SNOMED code issue on outgoing results\n \nBlood Bank Review:\n==================\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nRemedy Overview:\n================\n \n1. INC000000900556 - Result transaction SNOMED code application errors\n \nProblem:\n--------\n \n1. An application error occurs when processing results if a Systematized\nAn application error is generated by a collecting site during processing \nof incoming result transactions if the collecting site does not have a \nSNOMED code on file for the topography and the host site sends a SNOMED \ncode. Because of the application error, the HL7 table 0070 is not being\nchecked to determine if the topography sent by the host site is valid.\n \nResolution:\n-----------\n \nRoutine LA7VIN4 is modified to not generate an application error if the \n Nomenclature of Medicine (SNOMED) code is not defined on the\ncollecting site has no SNOMED code on file but the host site is sending \none. Specimen validation then proceeds to the HL70070 table.\n \nRoutine: LA7VIN4\n \n2. INC000000917708 - Override SNOMED code issue on incoming orders\n \nProblem:\n--------\n \n collecting site for the specimen.\nA collecting site may be a non-VA facility which does not have the same \nSNOMED codes on file as a VA facility. This presents a problem when a \nVA facility (the host site) receives orders from the non-VA facility (the \ncollecting site). An application error is generated at the host site \nbecause of the discrepancy.\n \nLEDI software had developed an option (LA7S MAP NON-VA SNOMED CODES) to \nallow for this situation. The intent was that a specimen type / \ncollection sample could have an "override" SNOMED code defined on the \nhost site system. \n \n \nHowever, the code on the host site which deformats the HL7 order \ntransactions does not reference the file set by the option LA7S MAP \nNON-VA SNOMED CODES. Therefore, an application error is generated that \nthe order cannot be filed due to the SNOMED code discrepancy.\n \nResolution:\n-----------\n \nRoutine LA7SMU2 is modified to check the LA7S MAP NON-VA SNOMED CODES \n2. Override SNOMED codes are not referenced when processing incoming \nconfiguration on the host site for override SNOMED codes when processing\norders from a collecting site.\n \nRoutine: LA7SMU2\n \n3. INC000001080712 - Override SNOMED code issue on outgoing results\n \nProblem:\n--------\n \n orders.\nLEDI code was corrected under ticket INC000000917708 so that the host\nfacility will reference override SNOMED code and file the order.\n \n \nHowever, when the order is resulted, an application error will occur on \nthe collecting site because the host is not sending back the collecting \nsite's override SNOMED code.\n \nResolution:\n----------- \n\n
\n \n interface situations which occur simultaneously.\nThis patch addresses two (2) Laboratory Electronic Data Interchange (LEDI)\nissues:\n \n1. A test already built to a shipping manifest can be built to another\n shipping manifest for a different date. A test should be built to\n only one shipping manifest.\n \n2. A null subscript software error may occur which is caused by several\n\n
\nAssociated Patches: (v)LA*5.2*80 <<= must be installed BEFORE `LA*5.2*88'\n \n TEXT: Msg #|1|, Auto Release not allowed for accession UID |2|. Results \nhave previously been released. \nSEND ALERT: YES\n \nNew Service Requests (NSRs):\n==============================\nNSR# 20131009: Employ laboratory autoverification in the Veterans Health \nAdministration. \n \nTest Sites:\nDescription:\n===========\nKansas City VAMC (Alpha)\nTucson (Beta)\nTampa (Beta)\nIowa City (Beta)\nFresno (Beta)\n \n \nSoftware and Documentation Retrieval Information\n ==============================\n===========\nVistA Laboratory patch LR*5.2*458 software is distributed by Host File, \nalong with LA*5.2*88. Software is available on the ANONYMOUS.SOFTWARE \ndirectory at one of the following Office of Information (OI) Field \nOffices. The preferred is to retrieve the file using Secure File Transfer\nProtocol (SFTP) from download.vista.domain.ext, which transmits files from\nthe first available FTP server. Sites may also select to retrieve\ndocumentation directly from a specific server as follows: \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\nThe build for this patch is distributed as part of a multi-package build \n \nFile Name Contents Retrieval Format\n------------------ -------------------- ----------------\nLAB_AUTORELEASE_1_0.KID Host File containing ASCII\n KIDS software distribution\n \nThe VistA Documentation Library (VDL) web site will also contain \n \nLR_52_458_LA_52_88 Release Notes Binary\n for LR*5.2*458 and LA*5.2*88\nthat contains LR*5.2*458 and LA*5.2*88. This contains functionality to \n \nLab AutoRelease 1.0 User Guide Binary\n \nLab AutoRelease 1.0 Technical Manual Binary\n \nLab UI HL V1.6 Upgrade Installation Binary\n and User Guide\n \nLab UI HL V1.6 Upgrade Interface Binary\n Specifications Document \nenable Auto Verification and Auto Release of lab normal lab results and \n \nThis website is usually updated within 1-3 days of the patch release date.\nThe VDL web address for Laboratory Universal Interface user documentation\nis: http://www.domain.ext/vdl/application.asp?appid=120\n \nInstallation Instructions\n=========================\nThis patch, LA*5.2*88, is part of a combined build for Laboratory \nAutoverification. \n \nwas initially developed at the Kansas City VAMC. This new process \nPlease refer to patch LR*5.2*458 for installation instructions.\n \nRoutine Information:\n====================\n \n \nThe second line of each of these routines now looks like:\n;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994;Build 10\n \nThe checksums below are new checksums, and\ninvolves automatic review and release of test results based on a \n can be checked with CHECK1^XTSUMBLD.\n \nRoutine Name: LA7UCFG\n Before: B4239468 After: B137316017 **66,88**\nRoutine Name: LA7UCFG1\n Before: n/a After: B29526912 **88**\nRoutine Name: LA7UIO1\n Before: B66837499 After: B75417661 **66,74,88**\nRoutine Name: LA7UTILB\n Before: B12063183 After: B23365722 **74,88**\nlab-established set of boundaries, also referred as rules, rule sets, and \nRoutine Name: LA7VHL\n Before: B32679919 After: B38289473 **27,46,62,64,67,74,88**\nRoutine Name: LA7VHLU8\n Before: B10483894 After: 60447079 **74,88**\nRoutine Name: LA7VHLU9\n Before: B19044226 After: B33364706 **68,74,88**\nRoutine Name: LA7VIN\n Before: B29668237 After: B31997123 **46,67,74,88**\nRoutine Name: LA7VIN1\n Before: B53484134 After: B65233143 **46,64,74,88**\nalgorithms. Lab results that are in a "normal" range, as pre-determined \nRoutine Name: LA7VIN2\n Before: B44814406 After: B46992282 **46,64,74,88**\nRoutine Name: LA7VIN2A\n Before: B32994528 After: B34119950 **74,88**\nRoutine Name: LA7VIN4\n Before: B77376354 After: B81803911 **46,64,67,66,74,85,88**\nRoutine Name: LA7VIN4A\n Before: B19473776 After: B23154184 **74,80,88**\nRoutine Name: LA7VIN5\n Before: B69080940 After: B85555425 **46,64,68,74,84,88**\n (v)LA*5.2*84 <<= must be installed BEFORE `LA*5.2*88'\nby the laboratory, will transmit directly from the middleware to VistA \nRoutine Name: LA7VIN5A\n Before: B32697215 After: B34608326 **46,64,67,72,66,74,88**\nRoutine Name: LA7VORC\n Before: B18625097 After: B22779822 **46,64,68,88**\nRoutine Name: LA88\n Before: n/a After: B37005513 **88** DELETED AFTER INSTALL\nRoutine Name: LA88A\n Before: n/a After: B100793409 **88** DELETED AFTER INSTALL\n \nRoutine list of preceding patches: 80, 84, 85\nlab files and on to Computerized Patient Record System (CPRS) without the \nintermediate step of requiring a lab technologist to manually review and \nsign off on these normal lab results. This process will eliminate the \nneed for a qualified technologist to manually approve all "normal" \nresults before those results are filed in VistA Lab files and available \nfor clinicians to view in CPRS. \n \nEach VAMC site will determine which instruments will use this \nfunctionality as it can set up on an instrument by instrument basis. \n (v)LA*5.2*85 <<= must be installed BEFORE `LA*5.2*88'\nEssentially VistA Lab instruments are set up as either being available \nfor auto verification or not available for auto verification. If an \ninstrument is set up for auto verification, then a lab result passing the \nrule set will be filed by the middleware in VistA lab files and available \nin CPRS and a lab result that cannot pass the rule set will be held in \nthe middleware system for review by a lab technologist. \n \nIn support of this auto verification and auto release functionality, this \npatch will add two new application proxy users. LRLAB AUTO RELEASE is \nused to indicate that the results in VistA Lab were released by an \n \nautomated Lab process without human interventions. LRLAB, AUTO VERIFY is \nused to indicate that the results were "approved" by an automated process \nusing a rules based system.\n \n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nSubject: AUTOVERIFICATION\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nAUTO INSTRUMENT (#62.4) AUTO RELEASE (#99) New\n \nLA7 MESSAGE LOG BULLETINS (#62.485)\n \nParameter Definitions Associated:\n \nParameter Definition Name New/Modified/Deleted\n------------------------- --------------------\n \nLA UI AUTO RELEASE MASTER New\nLA UI PROVIDER CONTACT INFO New \n \n \nThe following are new entries new entry in the file LA7 MESSAGE LOG \nBULLETINS (#62.485):\n \nCODE: 301\nTEXT: Msg #|1|, User |2| [DUZ: |3|] does not own the LRVERIFY security \nkey. Auto Release not allowed for accession UID |4|.\nCategory: ROUTINE\nSEND ALERT: YES\n \nCODE: 302\nTEXT: Msg #|1|, User |2| [DUZ: |3|] is not an active user on the system. \nAuto Release not allowed for accession UID |4|.\nSEND ALERT: YES \n \nCODE: 303\nTEXT: Msg #|1|, No verifying user or application proxy found. Auto \nRelease not allowed for accession UID |2|.\n ENHANCEMENT\nSEND ALERT: YES \n \nCODE: 304\nTEXT: Msg #|1|, User |2| [DUZ: |3|] is not a valid user to verify \nresults. Auto Release not allowed for accession UID |4|.\nSEND ALERT: YES \n \nCODE: 305\nTEXT: Msg #|1|, User |2| [DUZ: |3|] is not allowed to verify. Only auto \nverification enabled for this instrument. Auto Release not allowed for \n DATA DICTIONARY\naccession UID |4|.\nSEND ALERT: YES \n \nCODE: 306\nTEXT: Msg #|1|, User |2| [DUZ: |3|] is not allowed to verify. Only tech \nverification enabled for this instrument. Auto Release not allowed for \naccession UID |4|.\nSEND ALERT: YES \n \nCODE: 307\n\n
\nThe build for this patch is distributed as part of a multi-package build \nresult processing and verify/release functions (see LR*5.2*474 patch\nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \nN/A\ndescriptions for additional details).\n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \n \nSecurity Key Name\n-----------------\nN/A\n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nThis patch is distributed in support of the VistA Laboratory Enhancement\nN/A\n \n \n \nBelow shows the Data Dictionary as modified with the installation of this\nPatch for the Auto Instrument File. \n \nSTANDARD DATA DICTIONARY #62.41 -- LABORATORY TESTS SUB-FILE \n JUN 8,2016@12:37:17 PAGE 1\nSTORED IN ^LAB(62.4,D0,3, SITE: TEST.CHEYENNE.DOMAIN.EXT UCI: \n(VLE) Microbiology/Data Innovations interface utilizing the Laboratory\nVISTA,ROU\n \nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n \n62.41,.01 TEST 0;1 POINTER TO LABORATORY TEST FILE (\n #60) (Required) (Multiply asked)\n \n INPUT TRANSFORM: S DIC("S")="I $D(^LAB(60,Y,.2))!(""MI""[$P\nUniversal Interface.\n (^LAB(60,Y,0),U,4))" D ^DIC K DIC S DIC=DI\n E,X=+Y K:Y<0 X\n LAST EDITED: JUN 07, 2016 \n HELP-PROMPT: Enter the name of a test for which the \n instrument will send data. \n DESCRIPTION: This contains the test names for this\n instrument. \n \n SCREEN: S DIC("S")="I $D(^LAB(60,Y,.2))!(""MI""[$P\n (^LAB(60,Y,0),U,4))"\n \n EXPLANATION: Allow CH atomic test or Microbiology subsc\n ript test\n FIELD INDEX: AD (#867) MUMPS IR ACTION\n Short Descr: Set "ROUTINE STORAGE" field with CH\n subscripted test data name number\n Description: This trigger cross reference will only\n populate the "ROUTINE STORAGE" field with\n 63.04 data location file number for CH\n (Chemistry) atomic subscripted test having\n data name field populated. See example\nThe patch contains a modification to the AUTO INSTRUMENT (#62.4) file \n below. MI (Microbiology) subscripted test\n have no data name, therefore the "AUTO \n INSTRUMENT" file # 62.4, "TEST" field #30,\n (#62.41), subfile #62.41, "ROUTINE\n STORAGE" file #11 will NOT be set. \n \n EXAMPLE: CH subscripted test having DATA\n NAME will populate the ROUTINE STORAGE \n field with: TV(#,1) MI subscripted test\n will NOT set the ROUTINE STORAGE field. \nthat will change the name of the "CHEM TESTS" (#30) field to "LABORATORY\n Set Logic: S $P(^LAB(62.4,DA(1),3,DA,1),U)="TV("_X2(3\n )_",1)"\n Set Cond: S X=(X2(2)="CH")&(X2(3)'="")\n Kill Logic: S $P(^LAB(62.4,DA(1),3,DA,1),U)=""\n X(1): TEST (62.41,.01) (Subscr 1) (Len 10)\n (forwards)\n Transform (Display): \n X(2): Computed Code: S X=$P($G(^LAB(60,X(1),0)),\n U,4)\n (Subscr 2)\nTESTS" and modify the input screen to allow "MI" subscripted tests to be\n X(3): Computed Code: S X=$P($G(^LAB(60,X(1),.2))\n ,U)\n (Subscr 3)\n \n \n \n FILES POINTED TO FIELDS\n \nLABORATORY TEST (#60) TEST (#.01)\n \nthat contains LR*5.2*474 and LA*5.2*90 and contains functionality that \nadded to an Auto Instrument entry. The trigger on the TEST (#.01) field\nNew Service Requests (NSRs):\n---------------------------- \nNSR #20131213\nCarbapenem Resistant Enterobacteriaceae (CRE) Naming Conventions\nElectronic Interfacing of Automated Identification and Susceptibility \nTesting Instruments\n \nNSR #20140801\nTracking Multi-Drug Resistant Organisms\n \nwas also modified so that only tests with a value in the LOCATION (DATA\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nRemedy Ticket(s) & Overview:\n----------------------------\n \nN/A\nNAME) (#5) will set the ROUTINE STORAGE (#11) field.\n \nProblem:\n-------\nN/A\n \nResolution:\n----------\nN/A\n \nTest Sites:\n \n----------\nJames A. Haley Veterans Hospital\nIowa City VA Healthcare System\nLexington VA Medical Center\n \nSoftware and Documentation Retrieval Information \n================================================\nVistA Laboratory patch LR*5.2*474 software is distributed by Host File,\nalong with LA*5.2*90. Software is available on the SOFTWARE.DIR directory\nat one of the following Office of Information (OI) Field Offices. The\nAdditional Information:\npreferred method is to retrieve the file using Secure File Transfer\nProtocol (SFTP) from download.vista.domain.ext, which transmits files from\nthe first available SFTP server.\n Albany ftp.fo-albany.domain.ext \n Hines ftp.fo-hines.domain.ext \n Salt Lake City ftp.fo-slc.domain.ext \n \nFile Name Contents Retrieval Format \n------------------ -------------------- ----------------\nLAB_MICRO_INTERFACE_ Host File containing ASCII\n-----------------------\nRELEASE_1_0.KID KIDS software distribution \n \nLAB_MICRO_INTERFACE_RELEASE_1_0_DOCS.ZIP, which contains both .pdf and \n.docx formatted files of the following documents. Retrieval format is \nBINARY:\n \n VLE Micro_Lab_Micro_Interface_Release_1.0_Technical_Manual\n VLE Micro_Lab_Micro_Interface_Release_1.0_User_Guide\n VLE Micro_Deployment_Installation_Roll Back_Back Out_Guide\n \nThis patch contains an enhancement to the antibiotic susceptibility \n \nThe VistA Documentation Library (VDL) web site will also contain the \nabove referenced documents. This website is usually updated within 1-3\ndays of the patch release date. The VDL web address for Laboratory\nUniversal Interface user documentation is:\nhttp://www.domain.ext/vdl/application.asp?appid=120\n \nNote: These previously released documents contain configuration and\nmapping information that is useful to the implementation of the Universal\nInterface for Microbiology tests.\nresult processing to accommodate the need for laboratories to \n------------------------------------------------------------------------\nLEDI IV Installation Guide LAB_LEDI_IV_IG.PDF binary\nLEDI IV User Manual LAB_LEDI_IV_UM.PDF binary\nLEDI IV Update AP/MICRO LEDI_IV__AP__MICRO_ binary\nConfiguration Guide CONFIGURATION_GUIDE.PDF binary\n \nPatch Installation:\n \n \nPre/Post Installation Overview:\nreport/document variations in susceptibility testing related to \n-------------------------------\nThis patch install must be coordinated with the Laboratory ADPAC to \nensure that all Lab Interface related activities are halted.\n His \n \nPre-Installation Instructions: \n------------------------------\nEnsure that all Lab Interface activity has been halted !!\n \nThis would include:\ndifferences between in vitro susceptibility testing and in vivo action. \n-Editing of an Auto Instrument file entry, \n-Turn off the Auto Downloading process to prevent the building and \ndownloading of a Load/Worklist to the Instrument Manager.\n-Shut down all LA7UI logical links and any other HL7 process (HLZTCP or \nHLLP processes) to prevent the processing of result messages from the IM.\n \nThis patch may be installed with users on the system as long as the above \nprocess controls have been followed.\n \n \nwill allow Microbiology instrumentation to utilize the Lab Universal\nAn example is extended-spectrum_Beta-lactamases (ESBL).\nInstallation Instructions:\n--------------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \n \nThis installation will modify the CHEM TESTS field (#30) in the AUTO \nINSTRUMENT file (#62.4) by changing the following:\n \n \n The name of the field will be changed to LABORATORY TESTS\n The screen on the field will now allow "MI" subscripted tests\n The ROUTINE STORAGE (#11) value set by the trigger on the TESTS \n (#.01) field will not happen for "MI" subscripted tests\n The original ROUTINE STORAGE trigger code has been replace with a new \n style AD cross-reference.\n \n1. DOWNLOAD HOST KIDS FILE \n ----------------------\nSusceptibility results received as coded entries can be from the SNOMED \n Download the KIDS file LAB_MICRO_INTERFACE_RELEASE_1_0.KID from \n the ANONYMOUS.SOFTWARE directory of Albany, Hines, or the Salt\n Lake OIFO to the appropriate directory on your system.\n \n2. LOAD DISTRIBUTION \n -----------------\n Use the 'LOAD A DISTRIBUTION' option on the KIDS \n INSTALLATION menu, and enter: the directory onto which you \n have downloaded the host file, followed by \n LAB_MICRO_INTERFACE_RELEASE_1_0.KID, the host file name. \nCT code system or a site-designated local code (L).\n \n3. START UP KIDS \n -------------\n Start up the Kernel Installation and Distribution System Menu \n [XPD MAIN]:\n Edits and Distribution ... \n Utilities ... \n Installation ... \n \n Select Kernel Installation & Distribution System Option: \n \n Installation \n -------------\n \n Load a Distribution \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Install Package(s) \n Restart Install of Package(s) \n Unload a Distribution \nThe interface supports the following SNOMED CT codes to report \n Backup a Transport Global \n \n4. Select Installation Option: \n ---------------------------\n \n a. Use the Load a Distribution and select Host File: \n LAB_MICRO_INTERFACE_RELEASE_1_0.KID\n b. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates.\nsusceptibility to antimicrobial agents.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n d. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n \n Install? NO//' \n Respond: NO\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n Respond: NO\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \n Respond: NO\n131196009 susceptible\n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' \n Respond: 0.\n \n \nPost-Installation Instructions:\n-------------------------------\nBelow is an example of how an micro instrument might be defined in the \nAuto Instrument file. Refer to the Install. We recommend that the Install \nand User manuals be followed for more completely documented \n260357007 moderately susceptible\ninstructions. \n \nAUTO INSTRUMENT (#62.4:\n \nNUMBER: 3 NAME: BAC-TEC\n LOAD/WORK LIST: BAC-TEC\n ENTRY for LAGEN ROUTINE: Accession cross-reference\n CROSS LINKED BY: IDE MESSAGE CONFIGURATION: LA7UI2\n METHOD: BACTEC DEFAULT ACCESSION AREA: BLOOD \nCULTURE\nInterface. \n264841006 intermediately susceptible\n OVERLAY DATA: YES STORE REMARKS: YES\nNUMBER: 1 TEST: BLOOD CULTURE\n UI TEST CODE: BLD CX ACCESSION AREA: MICROBIOLOGY\n FILE BUILD ENTRY: EN FILE BUILD ROUTINE: LA7UID\n AUTO DOWNLOAD: NO WKLD METHOD: BACT/ALERT\n WKLD CODE METHOD NAME: BACT/ALERT WKLD CODE SUFFIX: .7086\n30714006 resistant\n10828004 positive\n260385009 negative\n \nLocal codes in the role of answers can be entered on an interface \nspecific basis using the option Add/Edit Local Identifier [LA7V 62.47 \nLOCAL IDENTIFIER]\n \nAn example of reporting ESBL status is the following HL7 OBX segment \n \nfragment.\n \nOBX|1|CWE|6984-9^ESBL:SUSC:PT:ISLT:ORDQN:AGAR \nDIFFUSION^LN^^^^2.19^^ESBL||ESBL^ESBL^L^^^^20160721^^+|||+\n \nRoutines related to this enhancement are:\nLA7VIN2A\nLA7VIN7\nLA7VIN7A\nLA7VIN7B\nBy utilizing the Universal interface and middleware sites will be able to \nLA7VHLU6\n \nBlood Bank Review:\n==================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*90 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by ProPath\nstandard titled: BBM Team Review of VistA Patches.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LA*5.2*90 does not \nalter or modify any software design safeguards or safety critical elements\ninterface microbiology devices to a UI standard interface. New\nfunctions.\n \nRISK ANALYSIS: Changes made by patch LA*5.2*90 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nmade, no specific validation requirements exist as a result of\ninstallation of this patch.\n \n \nfunctionality will be applied that will allow for a "MI" subscripted test\nPatch Components:\n-----------------\nNone\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nAUTO INSTRUMENT (#62.4) LABORATORY TESTS (#30 Modified\n \nto be added to the Auto Instrument file. There will also be enhanced\n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nMail Groups Associated:\n \n\n\nSee National Patch Module for details.\n\n
\nThis patch addresses one (1) Laboratory Electronic Data Interchange (LEDI)\n \nI9858894FY16 : LEDI Mycology Organism Comment Issue\nissue:\n \nMycology organism comments are stored under the "Bacteriology Report \nComment" section of VistA Lab reports rather than with each Mycology \norganism's section.\n \nAssociated CA-SDM ticket:\n==========================\n\n
\nThe Vitek Literal Interface parser routine loops infinitely when\nextra large data streams are encountered. The LAMIVTLP routine was modified \nto fix this problem.\n \n\n
\nThis patch is a VM patch that addresses 1 issue in the Lab package:\n \n1. Modify lab Automated Instrument routines to allow for the\n use of the VIC 4.0 card number as a patient identifier in the\n PID segment for POC (Point of Care) processing.\n\n
\nThe patch addresses one (1) issue: \n \n1. When a result returns from a send-out laboratory containing \nresults with a reference range with a negative value, VistA Lab parses \nthe values erroneously and renders the range as a positive value.\n\n
\nThis patch addresses one issue:\n \nThe Incomplete Test Status Report (LWRKINC) sometimes does not display a \nstatus of "Results Available" for Laboratory Electronic Data Interchange \n(LEDI) tests when results are available for review from a host site.\n\n
\nThis patch addresses one issue:\n \nThe Incomplete Test Status Report (LRWRKINC) sometimes does not display a \nstatus of "Results Available" for Laboratory Electronic Data Interchange \n(LEDI) tests when results are available for review from a non-VistA host \nsite (such as Quest).\n\n
\nThis patch along with LR*5.2*568 addresses one issue:\n \nVistA Laboratory (POC) Point of Care interface logic might incorrectly \ndetermine the reporting facility for POC results.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n \nPlease note that LR*5.2*580 is a companion patch to this patch.\n\n
\nEliminates the undefined from LAMIVTL0 when a deleted accession\nnumber is sent across the Vitek Literal Interface. \n\n
\n The 63.3 and 63.31 nodes in the LAB DATA file (#63) are\n not incremented properly when multiple organisms are\n found using the Vitek Literal Interface. The routines LAMIVTL3\n and LAMIVTL4 have been edited to resolve the problem.\n\n\n
\nSee LABORATORY ELECTRONIC DATA INTERCHANGE (LEDI) PATCH LA*5.2*27 and PATCH\nLR*5.2*153 INSTALLATION GUIDE.\n\n
\n AUTOMATED LAB INSTRUMENTS (LA) Y2K PATCH\n in other laboratory routines where space was available.\n current accession date and call to $$FMTE^XLFDT\n to display FileMan date in external format.\n Display accession date with 4-digit year.\n Added "P" to %DT variable, assumes past dates.\n \nLAMIAUT7 CLEAR+7 Added "P" to %DT variable.\n \nLAMIVT5 LA3+2 Change 2-digit year default accession date to\n current accession date based on accession area\n transform. Display accession date with 4-digit\n \n year.\n \nLAMIVT6 LA3+2 Change 2-digit year default accession date to\n current accession date based on accession area\n transform. Display accession date with 4-digit\n year.\n \nLAMIVTL0 LRAD+1 Added "P" to %DT variable. \n \nLAMIVTL0 LRAD+3 Call to $$CADT^LA7UTIL to determine current\n With the upcoming turn of the century (Y2K) the Office of the\n accession date and call to $$FMTE^XLFDT to\n display FileMan date in external format.\n Display accession date with 4-digit year.\n \nLAMIVTKD SAMPLE+10 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \nLAMIVTKD SAMPLE+12 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \n Chief Information Office Technical Services has issued a guidelines\nLAMIVTKD PNM+3 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \nLAMIVTKD PNM+6 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \nLAMIVTLD SAMPLE+37 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \nLAMIVTLD SAMPLE+41 Change building date with 2-digit year to call\n document for VISTA Software Y2K requirements. This guideline lays out\n to $$Y2K^LRX which returns 4-digit year.\n \nLAMIVTLD PNM+6 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \nLAMIVTLD PNM+16 Change building date with 2-digit year to call\n to $$Y2K^LRX which returns 4-digit year.\n \nLAPFICH EN+4 Added "P" to %DT variable.\n \n the core essentials to meet or exceed OMB, GAO and congressional\n \nDuring initial evaluation of LA namespaced routines it was reported\nthat 20 routines would need renovation to be Y2K compliant. After\nfurther evaluation, it was determined the only 11 LA namespaced\nroutines would need to be modified. The routines originally reported\nbut not modified are:\n \nRoutine Line Tag Non-Renovation Reason\n------- -------- ------------------------------------------------\n \n requirements for Year 2000 requirements. Laboratory software has been\nLABCX4D SAMPLE+10 Changing date format will violate vendor's\n instrument interface specification.\n \nLAEKT4 LA2+2 Code is checking if test result is less than\n 999999. Not a Y2K date issue.\n \nLAGEN CONTROL+2 Code is calculating inverse FileMan date from\n specimen collection date/time in FileMan date\n format.\n \n modified to meet or exceed these guidelines.\nLAHTCCAD SAMPLE+1 Changing date format will violate vendor's\n instrument interface specification.\n \nLAKDIFF WLN+1 Code is calculating inverse FileMan date from\n specimen collection date/time in FileMan date\n format.\n \nLAKDIFF3 LAKDIFF3+13 Code is calculating inverse FileMan date from\n specimen collection date/time in FileMan date\n format.\n \n \nLAKUR WLN+1 Code is calculating inverse FileMan date from\n specimen collection date/time in FileMan date\n format.\n \nLAMIVTLG CONTROL+2 Code is calculating inverse FileMan date from\n specimen collection date/time in FileMan date\n format.\n \nLAMSD PT+9 Changing date format will violate vendor's\n Reference NOIS: None\n instrument interface specification.\n \nLAMSD SPEC+4 Changing date format will violate vendor's\n instrument interface specification.\n \n \n \n \nROUTINE SUMMARY:\n=================\n \n \n \nThe second line of the routine now looks like:\n \n <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[patch list]**; Sep 27, 1994\n \n \n CHECK^XTSUMBLD results\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n Reporting Site: N/A\n \n LA42 N/A 2382684 42\n LA7SMPXL 5134195 5400542 27,42\n LA7UTIL 4911757 5680457 17,42\n LA7VORM 17385553 17384019 27,42\n LABALARM 1650198 1640267 42\n LABERR 6644019 6638122 42\n LADOWN1 1617991 1620875 17,42\n LAMIAUT0 16381256 16551460 42\n LAMIAUT7 13571379 13798654 42\n \n LAMIVT5 6911163 6841547 42\n LAMIVT6 6905221 6835605 42\n LAMIVTKD 12903215 12408562 26,42\n LAMIVTL0 6434514 4704096 12,37,42\n LAMIVTLD 8214698 7932859 12,33,42\n LAPFICH 4040500 4046314 42\n LASET 6671014 6644420 27,42\n \n \n \n Test Site(s)--Alpha Platform w/ DSM OS: Brockton VAMC, Milwaukee VAMC\nInstallation Instructions:\n==========================\n \n1. Using the KIDS\n From the Kernel Installation and Distribution Systems (KIDS)\n Menu, select the Installation Menu [XPD INSTALLATION MENU]:\n Select Installation Option: Load a Distribution\n Enter a Host File: LAB_Y2K.KID\n \n KIDS Distribution saved on Mar 23, 1998@13:22:30\n North Chicago VAMC\n Comment: LR*5.2*203 LR*5.2*201 LA*5.2*42 Y2K Enhancements 3-23-98\n \n This Distribution contains Transport Globals for the following\n Package(s):\n LR*5.2*203\n LR*5.2*201\n LA*5.2*42\n \n Use INSTALL NAME: LR*5.2*203 to install this distribution\n \n \n \n2. Review your mapped set. If the routines are mapped, they should be\n removed from the mapped set at this time.\n \n3. The patch has now been loaded into a Transport global on your system.\n You now need to use KIDS to install the Transport global.\n \n4. On the KIDS menu, under the 'Installation' menu,\n use the following options:\n Print Transport Global\n \n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n **** It is strongly recommended to do a KIDS Backup ****\n **** before installing the build. ****\n **** The PRINT, COMPARE and VERIFY functions ****\n **** should be performed for each of the patches ****\n **** included in this distribution. ****\n \n -----------------------------------------------\n5. Primary Laboratory Options should be placed out of service\n and Laboratory Users should be off the system.\n Menu option Laboratory [LRMENU] or the local equivalent.\n \n Routine LAB for lab automated instruments interfaced thru\n a LSI should not be running.\n \n If site has direct-connected interfaces for lab automated\n instruments these should not be running.\n \n Software Availability:\n The HL7 background job (HLLP) for the Lab Universal Interface\n should be stopped.\n \n The routine LA7UIIN to process incoming HL7 messages should not\n be running. It will shutdown automatically after 5 minutes if\n no messages have been received.\n \n If using auto download, the routine LA7ADL should not be running.\n Use option Start/Stop Auto Download Background Job\n [LA7 ADL START/STOP].\n \n \n6. Installation time is less than 10 minutes during off peak hours.\n \n7. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'LR*5.2*203' and\n proceed with the install.\n \n8. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\n \n This patch is available from one of the CIO Field Offices listed below.\n \n9. If installation is successful, delete routine LA42 and LR201.\n All VAMC's are encouraged to use their FTP capability to obtain the\n software from the appropriate directory\n \n CIO Field Office FTP Address Directory\n ---------------- ------------- -----------------\n Hines 152.129.1.110 anonymous.software\n Albany 152.127.1.5 anonymous.software\n Salt Lake 152.131.2.1 anonymous.software\n \n Description:\n File Name: LAB_Y2K.KID\n Note: This patch is issued as part of a KIDS Distribution in which\n the Transport Globals contains three Laboratory patches. The patches\n are LR*5.2*203, LR*5.2*201 and LA*5.2*42.\n \n \n----------------------------\nOptions affected by changes:\n \nAP Microfiche Archive [LA AP FICHE]\n \nLab Error Trap Listing [LA ERR PRINT]\nVitek Load Worklist (Build) [LA MI VITEK L/W BUILD]\nVerify Micro Auto Data [LA MI VERIFY AUTO]\nVITEK LITERAL [LA VITEK LITERAL]\n \n---------------\n \nRoutine changes:\n \nRoutine Line Tag Description of Change\n This is the Year 2000 (Y2K) compliance patch containing the changes\n------- -------- ------------------------------------------------\nLABALARM LABALARM+2 Changed call to %DT with X="NOW" to Kernel\n $$HTE^XLFDT to determine current system time.\n \nLADOWN1 TREE+4 Code was taking entire node of panel test multiple\n in file LABORATORY TEST (#60) as pointer to entry\n in file LABORATORY TEST (#60). Since other data is\n stored on this node the pointer to file #60 was\n incorrectly constructed. Code now "+" variable to\n determine value of first piece.\n necessary to accommodate the year 2000. 2 digit (YY) year dates are\n \nLABERR EN1+1 Changed save error code to Kernel call $$EC^%ZOSV.\n \nLABERR EN1+5 Set Kernel variable DT using approved call\n $$DT^XLFDT, variable SY using call to $$NOW^XLFDT.\n \nLA7SMPXL PD+1 Fixed printing incorrect collecting site on report.\n \nLA7SMPXL SITE+1 Fixed printing incorrect collecting site on report.\n \n replaced with 4 digit (CCYY) century year dates in laboratory routines\nLASET LA1+7 Changed call to %DT with X="NOW" to Kernel\n $$HTE^XLFDT to determine current system time.\n \nLA7UTIL CADT+0 Extrinsic function to calculate current accession\n - CADT+6 date based on accession area transform.\n \nLA7VORM OBR+39 Corrected storing incorrect collecting site when\n building file LAB PENDING ORDERS ENTRY (#69.6).\n \nLAMIAUT0 ACCESS+2 Change default 2-digit year accession date to\n for patients' permanent clinical record. 2 digit year dates are replaced\n - ACCESS+6 current accession date based on accession area\n transform. Call to $$CADT^LA7UTIL to determine\n current accession date and call to $$FMTE^XLFDT\n to display FileMan date in external format.\n Display accession date with 4-digit year.\n Added "P" to %DT variable, assumes past dates.\n \nLAMIAUT0 DATE+4 Change default 2-digit year accession date to\n - DATE+7 current accession date based on accession area\n transform. Call to $$CADT^LA7UTIL to determine\n\n
\n This version is co-released with LAB SERVICE V5.2. It contains patches\nupto and including #.\n AUTOMATED LAB INSTRUMENTS (LA) future releases maybe independent of the\nLABORATORY SERVICE package. However in this version all LAB routines\nhave the same version number (V5.2).\n\n
\nThis a is list of routines and files needed for\nwith the method of data transmission protocols. You can usually\ntell a direct connect instrument by the routine name being LAnnnnXX\nwhere the XX will need to be changed before running and the nnnn will\nidentify the instrument.\n \nWith this release there is also a new error trap for auto instruments.\nThis trap does not use the system error trap and therefore does not\ncreate any special system problems.\nLAB auto instruments. This release has routines for\nmicrobiology instruments along with attendant verify routines.\nThe release also carries with it routines for some instruments to be\nrun in a bidirectional mode.\n \nIn some cases we have added some routines which will run an instrument\ndirectly connected to the CPU instead of going through the LSI. This\nhas been done because of problems with timing, and/or problems\n\n
\nVSIT*2.0*1 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nVSIT*2.0*2 See National Patch Module for a description of the\nchangesincorporated in this patch. \n\n
\nSEE NATIONAL PATCH MODULE\n\n
\nVHA Directive 98-058, "Sexual Trauma Counseling Care and Services"\nrequires that VHA provide care and counseling to veterans determined to\nhave been a victim of sexual trauma while the veteran was serving on\nactive duty. This patch will focus on the data collection for this\ndirective.\n \nThis is the VSIT portion of the overall patch. See DG*5.3*195\n\n
\nVisit Tracking 2.0\n\n
\nPX*1.0*1\nPatch 1 for PCE Patient Care Encounter 1.0\nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nPX*1.0*11 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nThis patch will modify PCE so that it will create a visit with the progress\nnote associated with a disposition location in the same way like with\nother locations.\n\n\n
\nCreate 132 column version of HEALTH FACTOR LIST report.\n\n
\nCurrently if a CPT code is part of a subset of E & M codes the user is \nallowed to enter that CPT code only once per encounter and with a \nquantity of only 1. There are 2 problems being addressed with this logic.\n1) If a CPT code begins with a letter it is being identified as an E & M \ncode whether or not it truly is. \n2) Certain E & M codes need to allow a quantity of more than 1 to be \nordered.\n\n
\nPROBLEM 1:\n In the Check Out function of PCE the user is asked to enter an ICD9 \ncode. If the user enters a partial CPT code then the Check Out procedure \nwill generate a list of codes that match. However, if one of the matching \nICD9 codes has a blank Description field the program will error.\n In PCE, while running the CP (CPT Procedure) Protocol, the code does \nnot check to see if the CPT code is an E&M code in file 357.69 (Type of \nVisit). An E&M code may only be placed on an encounter once with the\n"Quantity" field only allowing a "1" unless the "Type of Visit" file is\nset up to allow more than one. This business rule is, therefore, not \nbeing enforced.\n \nPROBLEM 2:\n\n
\nFix error in PCE Encounter Summary when clinic is null. \n\n
\nFixing a problem where the checkout process errors when bad data is \npassed to a fileman call while looking up and displaying ICD9 codes \nalready on the encounter.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nFIX V FILE INTEGRITY CHECKER PROMPTING.\n\n
\nFix three problems. 1) Editing provider information for an encounter is \nnot triggering a re-transmission to the NPCDB. 2) The prompts under the CP\nprotocol work incorrectly when editing a CPT code that begins with a \nletter. 3) Editing the Provider does not update the User Class when \nchanging an existing provider to a different provider.\n\n
\nProvider coming up as invalid provider\n\n
\nPatch 10 for PCE Patient Care Encounter 1.0\n \nPCE Reports\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nThis will address the CASELOAD PROFILE BY CLINIC [PXRR CASELOAD\nPROFILE BY CL] option of the PATIENT CARE ENCOUNTER (PCE) package.\nThe report did not correctly display unscheduled encounters.\n\n
\nPX*1.0*123\nPatch 123 for PCE Patient Care Encounter 1.0\nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nDate of death display warning. Addresses the selecting of deceased \npatients, within PCE, that currently does not check and display for date \nof death.\n \nAlso, addresses [PXRR PROVIDER ENCOUNTER COUNTS] where the prompt for \nselection by Person Class was limited to 30 characters.\n\n
\nThe description of the patch can be found in the National Patch Tracking \nmodule.\n\n
\nFix IO variables when PCE reports are queued.\n\n
\nScrolling past enrollment information in PCE.\n\n
\nPCE/SD DEBUGGER DISPLAY WITH 3M BATCH/RECORD\n\n
\nRemove line 1, the encounter itself, from the delete list in Delete Item \nunder the Update Encounter protocol.\n\n
\nPatch 4 for PCE Patient Care Encounter 1.0\n \nPCE/SD Debugging Utilities\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nErrors on print from Patient Activity List\n\n
\nChange Date action gives wrong century with future 2 digit year entry.\n \nUparrowing at patient expired prompt causes indefined error.\n\n
\n<UNDEFINED> error when deleting Encounters\n\n
\nUnable to Check out Encounters\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nUnable to complete check out. IHS file index problem.\n\n
\n \n \nNotes on cancelled appts not creating entry in file #409.68\n\n
\nIncrease limit to QUANTITY field in the V-CPT file to 3 digits and fix \nthe provider prompting for the CPT code in the check-out interview.\n\n
\nPX*1.0*14 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nUndefined when deleting Skin Test\n\n
\nPPD RULES ARE INCORRECT.\n\n
\nFix problem that allows users to look at their own medical records.\n\n
\nPATIENT FINANCIAL SERVICES SYSTEM(PFSS) 1B - PCE\n\n
\nCONSULT/SCHEDULING APPOINTMENT LINK INTERFACE\n\n
\n1. Text editing/alignment in PXTT EDIT EDUCATION TOPICS not displaying\n correctly when using PXTT INQUIRE EDUC TOPIC \n \n \n2.Screen editor for GOALS and STANDARDS not displaying properly during \n [PXTT INQUIRE EDUC TOPIC].\n\n
\nAllow entry of duplicate Health Factors per encounter.\n\n
\nDefault DX during Appt Check Out. Also, invalid code when entering \ndiagnosis for PCE procedures. Also, if no procedure, only option is to \ndelete encounter.\n\n
\nThis patch addresses four issues related to the Patient Care Encounter \n PXCE Data entry functionality\n(PCE) module that were reported on the Remedy tickets listed below:\n \n 1) HD123432 - IBDF UTIL MAINT UTILITY PROBLEM\n 2) HD135534 - IB MT NIGHT COMP erroring out with \n <SUBSCRIPT>ENCEVENT+10~PXKENC\n 3) HD136528 - Warning on Patient Death - warning displayed with not \n a related patient\n 4) HD173398 - Event Capture Issue - update to the User Manual regarding\n\n
\nThis patch fixes problems with keep patient data after not selecting a \nnew patient.\n\n
\nThis is a coordinated patch with Health Summary's, GMTS*2.7*10\nwhich addresses issues described in that patch.\n\n
\nPlease refer to patch PX*1.0*186 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nPlease refer to patch PX*1.0*184 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nThis patch will fix an undefined variable error which occurs when the \nenough to fill up about a screen, then hit <ENTER> key.\nFileMan ENTER OR EDIT FILE ENTRIES option is used to edit a POV (Problem \nof Visit used by VA or Purpose of Visit used by IHS) code.\n \nThis patch will also fix a subscript error which occurs when the CPT Code \ncontains very lengthy ASCII control characters. User was in Appointment \nManagement [SDAM APPT MGT] going through the checkout process and was \nbeing prompted for a CPT code. At the 'Enter PROCEDURE (CPT CODE): ' \nprompt, the user input 99456 but then pressed and hold the <TAB> key long\n\n
\nChange field #.08 in the Health Factors file (9999999.64) to a required \nfield. Also, add a warning message for PCE Health Factors to let users \nknow when a Health Factor is not set up to display on a Health Summary\nreport.\n\n
\nThis patch fixes the sequence numbers of the Education Subtopic out of \norder and word wrapping problems for the Goals and Standards of the\nEducation Topics.\n\n
\nThis patch addresses the problem where a date and time is missing when \nvalidates the status of the Diagnosis Code.\n \nThis patch will also update the CREATED BY USER (#.23) field description \nof the Visit (#9000010) file to reflect the current functionality.\n\n
\nThis patch will change the existing code for the Caseload Profile by \nEncounters occurred at Non-VA sites will be included in the report as \nwell.\n \nThe last item this patch will fix is an 'O' displayed after accepting the \ndefault value N from a prompt when running the Provider Encounter Counts \nreport.\nClinic [PXRR CASELOAD PROFILE BY CL] report to remove the existing direct\nglobal read, so data is now pulled from the PXRMINDX index.\n \nThe second item this patch will modify is the report logic to display\nhistorical encounters that with no Loc. of Encounter (#.06) field\npopulated in the Visit (#9000010) file when running the report Provider\nEncounter Counts [PXRR PROVIDER ENCOUNTER COUNTS] and selecting Service\nCategory "EVENT (HISTORICAL)", it returns very few or no encounters. \n\n
\nThis patch addresses the upcoming deletion of unsupported fields in the\nICD Diagnosis File, #80, and the CPT File, #81. Modifications are being\nmade to affected Patient Care Encounter routines to replace unsupported\ncalls to the deleted data fields with the appropriate supported API.\n\n
\n This patch will prevent the credit stop visit entry from being \ndeleted when the primary visit receives a request to delete "ALL"\nentries while the visit is associated with an appointment.\n\n
\nPX*1.0*23 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\nICD-10 REMEDIATION \nThis patch distributes the necessary components of PCE to allow\nfor the transition to the ICD-10-CM diagnosis coding system.\n\n
\nSee patch description.\n\n
\nThe Veterans Health Information Systems and Technology Architecture\nresulting in improved health status as well as public health monitoring.\n \nThe goals for the VIMM 1.0 project are to deliver an Initial Operating\nCapability comprised of standard, interoperable immunization data for\nexchange with external trading partners based on the modernization of\nthe VistA Patient Care Encounter (PCE) package.\n(VistA) Immunizations Enhancements (VIMM) 1.0 project modifies existing\nimmunization files and adds additional files to enable VA to quickly and\nreliably document and exchange standardized immunization information on\nbeneficiaries across services and departments. Additionally, modifications\nsupport Certification for Meaningful Use as well as VistA Evolution\nrequirements. This provides a Veteran patient-centric vaccine record\nexchangeable with the external community. Clinicians will have access to a\nmore complete medical history in the VistA electronic medical record\n\n
\nPatch PX*1*204 addresses the following Patient Care Encounter issues:\n \n 1. ADD+3^AUPNVSIT errors.\n 2. EVISITDT+23^PXCEVSIT error.\n\n
\nPatch PX*1.0*208 addresses the following issue:\n \n- Series, reaction, and contraindicated values may not get filed into a\npatient's immunization record.\n\n
\nPatch PX*1*205 addresses the following Patient Care Encounter issues:\n \n 1. AUDIT+9^PXQFV errors\n 2. OCC+40^PXBGPRV errors\n 3. No CHECK for non-unique names on editing Health Factors\n\n
\nThe Veterans Health Information Systems and Technology Architecture\nhealth status as well as public health monitoring.\n \nThe goals for the VIMM 2.0 project are to deliver an Initial Operating\nCapability comprised of standard, interoperable skin test and immunization\ndata for exchange with external trading partners based on the\nmodernization of the VistA Patient Care Encounter (PCE) package.\n(VistA) Immunizations Enhancements (VIMM) 2.0 project modifies existing\nSkin Test files and adds additional files to enable VA to quickly and\nreliably document and exchange standardized skin test and immunization\ninformation on beneficiaries across services and departments.\nAdditionally, modifications support VistA Evolution requirements. This\nprovides a Veteran patient-centric vaccine record exchangeable with the\nexternal community. Clinicians will have access to a more complete medical\nhistory in the VistA electronic medical record resulting in improved\n\n
\nThe Veterans Health Information Systems and Technology Architecture\n(VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 2, \nbuilds upon the file structures and standardized data introduced by \nIncrement 1 by adding functional enhancements to the existing VistA \nPatient Care Encounter (PCE) package.\n \nSee the National Patch Module for a more detailed description.\n\n
\nPX*1.0*19 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nPatch PX*1.0*212 addresses the following issues:\n \n- Data Dictionary technical description misspells classification in\nthe VISIT file [#9000010]\n- References to SHORT NAME field [#2] of the CPT file [#81] need to be \nremoved.\n\n
\nThe Veterans Health Information Systems and Technology Architecture\n(VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 3, builds\nupon the file structures and standardized data introduced in Increments 1\nand 2 by adding functional enhancements to the existing VistA Patient Care\nEncounter (PCE) package.\n\n
\nThe Veterans Health Information Systems and Technology Architecture\n(VistA) Immunizations Enhancements (VIMM) 2.0 project, Increment 4, builds\nupon the file structures and standardized data introduced in Increments 1,\n2 and 3 by adding functional enhancements to the existing VistA Patient\nCare Encounter (PCE) package.\n\n
\nThis patch will fix 2 issues:\nand the application will switch the dates to make logical sense but gives\nno indication to the user. \n \n2. User requests to have the user manual updated for the Patient Care \nEncounter (PCE) VistA application to add the option PCE\\SD Debugging\nUtilities [PXQ PCE/SD DEBUGGING UTILITIES] back into the document.\n \n1. A user can select an end date prior to a start date within the PXCE\nOptions:\n PCE Encounter Data Entry [PXCE ENCOUNTER DATA ENTRY]\n PCE Encounter Data Entry and Delete [PXCE ENCOUNTER ENTRY & DELETE]\n PCE Encounter Data Entry without Delete [PXCE ENCOUNTER ENTRY NO DELETE]\n PCE Encounter Data Entry - Supervisor [PXCE ENCOUNTER ENTRY SUPER]\n PCE Encounter Viewer [PXCE ENCOUNTER VIEWER]\n\n
\nThis patch resolves potential runtime errors when $$OCCUP^PXBGPRV is run \nwith an invalid provider passed in.\n\n
\nThis patch prevents an <UNDEFINED> error from occurring when PXRRECSE \nattempts to sort corrupt data identified by an invalid x-ref.\n\n
\nThis patch updates local entries that have no Vaccine Administered (CVX) \ncode mapped in the IMMUNIZATION file (#9999999.14).\n\n
\nPCE data standardization, for detailed information and installation\ndistributed in a multi-package build named PCE STANDARDIZATION 1.0.\n\ninstructions, please see the PCE Standardization 1.0 Installation Guide.\n\nTo take full advantage of the PCE standardization work, changes to VistA\napplications that use PCE data are required. These applications include\nClinical Reminders, Health Summary, Problem List, and Order Entry/Results\nReporting. To make it easier for sites, the builds for PCE (PX*1.0*211),\nClinical Reminders (PXRM*2.0*42), Health Summary (GMTS*2.7*122), Problem List\n(GMPL*2.0*53), and Order Entry/Results Reporting (OR*3.0*501) are being\n\n
\nBackup of SD*5.3*777, PX*1.0*227 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatient Care Encounter (PCE) patch PX*1.0*227 modifies the software to\naccount for Blue Water Navy changes introduced in patch DG*5.3*1018.\n\n
\nPX*1.0*24 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\nThe documentation for DATA2PCE describes two ways to mark a diagnosis as \n"P"::=Primary\n"S"::=Secondary\nAlternatively\n1::=Primary\n0::=Secondary\n \nThere was a bug that prevented the "P" from working, patch PX*1*228 fixes \nthat bug.\nprimary:\n \n("DX/PL",i,"PRIMARY")\n \nCode that specifies that the diagnosis is the "primary" diagnosis for \nthis encounter. Only one "primary" diagnosis is\nrecorded for each encounter\n \n\n\nThis patch fixes a CPT code incorrect display issue.\n\n
\nPatient Care Encounter (PCE) patch PX*1.0*230 corrects an issue\nwith duplicate CPT code entries for encounters.\n\n
\nPX ICE WEB (RPC, ROUTINES, FILE and XPAR)\n\n
\nPatch PX*1.0*232 addresses an issue where the CPT code is being displayed\nin internal format and causing an error message to display making it\nunselectable.\n\n
\nThe purpose of this patch is to repair corrupted V HEALTH FACTORS \nmeasurements. A complete description can be found in the Forum patch \nmodule entry of this patch.\n\n
\nRefer to the patch description for an explanation of the changes included \nin this patch.\n\n
\nPX*1.0*27 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\n\nPatch 12 for PCE Patient Care Encounter 1.0\n \nPCE Reports\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nPX*1.0*5 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nPX*1.0*26 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\nPX*1.0*30 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\nSee the National patch module for description of patch PX*1*29.\n\n
\nSee National Patch Module for Description of this Build.\n\n
\nPX*1.0*22 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nPCE patch 16 clinical reminders.\n\n
\nPX*1.0*25 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\nSee PATCH PX *1*28 in the National Patch Module for descripition of this \nbuild.\n\n
\nPCE patch 36 clinical reminders.\n\n
\nPatch 3 for PCE Patient Care Encounter 1.0\n \nPCE Reports\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nPX*1.0*37 See National Patch Module for a description of the changes\nincorporated in this patch. \n\n
\n\nPatch 18 for PCE Patient Care Encounter 1.0\n \nPCE Reports\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nPCE patch 38 clinical reminders, flag historical encounters.\n\n
\nPCE patch 40, PX*1.0*40, clinical reminders. This patch changes the\nbehavior of the INACTIVE FLAG so it inactivates the reminder. See the\nNational Patch Module for a complete description.\n\n
\nThis build contains a change to two routines. It will cause the\nexecution of a Scheduling entry point to run the workload validator. The\npatch is being distributed as part of Scheduling patch SD*5.3*66.\n\n
\nPCE patch 42, PX*1.0*42, clinical reminders. This patch adds a new\nHealth Summary component PCE CLINICAL REMINDERS SUMMARY, CRS. See the\nNational Patch Module for a full description.\n\n
\nPCE patch 44, PX*1.0*44, clinical reminders. This patch prevents\n"ReMoved" problems being used by a clinical reminder.\n\n
\nThis build contains the PCE APIs required by the ACRP Interface Toolkit\n(Build SD*5.3*131).\n\nThis build provides ACRP access to procedure, diagnosis and provider\ninformation for an outpatient encounter.\n\nRefer to National Patch Module for more details on patch SD*5.3*131.\n\n\n
\n\nPatch 20 for PCE Patient Care Encounter 1.0\n \nThis is a new PCE report called PCE Encounter Summary. It replaces the\nPCE Workload Report.\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\n\nPatch 31 for PCE Patient Care Encounter 1.0\n \nPCE Reports, improvements to the Frequency of Diagnosis Report.\n \nSee National Patch Module for a complete description of the changes\nincorporated in this patch.\n\n
\nPatch 8 for PCE Patient Care Encounter 1.0\n \nPCE Reports\n \nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nPatch 49, PX*1.0*49 for PCE Patient Care Encounter 1.0.\n \nSee the National Patch Module for a complete description of the changes\nincorporated in this patch.\n\n
\nY2K updates for PCE. See National Patch Module for description.\n\n
\nPX*1.0*45 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nPatch 48 for PCE Patient Care Encounter 1.0\n \nPCE Reports, print facility on detailed provider report.\n \nSee National Patch Module for a complete description of the changes\nincorporated in this patch.\n\n
\nPCE patch 50, PX*1.0*50, clinical reminders. This patch allows information\nabout deceased patients to be displayed in the Clinical Maintenance and\nClinical Reminders Summary components. See the National Patch Module for a\ncomplete description.\n\n
\nPCE patch 51, PX*1.0*51, clinical reminders. This patch adds a screen\nto the APPLY LOGIC field to check for valid entries.\nSee the National Patch Module for a complete description.\n\n
\nPX*1.0*54 PCE patch 54.\n \nSee National Patch Module for a complete description of this patch.\n\n
\nThis build is part of the overall patch SD*5.3*149, and provides the\ncapability to display and capture Global Assessment of Function (GAF)\nscores and related data during appointment check out.\n\n
\n A single VISIT (#9000010) is pointed to by two main OUTPATIENT\n ENCOUNTERs (#409.68), when there should only be one. This is now\n addressed using LOCK. This problem was noted in NOIS message\n HUN-0598-22218. Some of the most important discussions of this\n problem occurred in FORUM mail message #27819009 : "Huntington\n problem with dup. Outpatient Encounters". The routine PXKMAIN has\n been modified to fix this defect. \n\n
\nPX*1.0*7 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nPCE patch 55, PX*1.0*55, clinical reminders. This patch adds a wildcard\nto the IGNORE ON N/A field. See the National Patch Module for a complete\ndescription.\n\n
\n PCE Help Text says "Provider" when it should say "Diagnosis" or\n "Procedure". This problem was noted in NOIS message PUG-1098-51770. \n It affects the protocols Check Out Interview [PXCE ADD/EDIT\n INTERVIEW], Check Out Interview [PXCE INTERVIEW] and Check Out\n Interview [PXCE SDAM INTERVIEW]. The routines PXBHLP3 and PXBHLP4\n have been modified to fix this defect. \n\n
\nSee National Patch Module for description.\n\n
\nPCE Code mapping and immunization fix for the 1999 COPT code update\n\n
\n 1. PCE sometimes crashes when editing cancelled appointments for\n \n 2. It has been pointed out that PCE should not allow the user to\n edit an encounter that has been cancelled, in cases where the\n visit no longer exists. This problem was noted in NOIS message\n TAM-0397-32584. It affects the options PCE Encounter Data Entry\n [PXCE ENCOUNTER DATA ENTRY], PCE Encounter Data Entry and Delete\n [PXCE ENCOUNTER ENTRY & DELETE], PCE Encounter Data Entry\n without Delete [PXCE ENCOUNTER ENTRY NO DELETE] and PCE\n Encounter Data Entry - Supervisor [PXCE ENCOUNTER ENTRY SUPER]. \n It also affects the protocols MCCR SITE PARAMETER EDIT [MAF MCCR\n which a visit still exists. This problem was noted in NOIS\n SITE PARM PROTOCOL], Group 1 Edit [MAF IB SITE PARM GROUP 1] and\n Group 2 Edit [MAF IB SITE PARM GROUP 2]. The routine PXCESDAM\n has been modified to fix this defect. \n messages BOS-0397-11896, PRO-0397-10568, HOU-0998-71834 and\n DAY-0898-41893. It affects the options PCE Encounter Data Entry\n - Supervisor [PXCE ENCOUNTER ENTRY SUPER], PCE Encounter Data\n Entry and Delete [PXCE ENCOUNTER ENTRY & DELETE], PCE Encounter\n Data Entry [PXCE ENCOUNTER DATA ENTRY] and PCE Encounter Data\n Entry without Delete [PXCE ENCOUNTER ENTRY NO DELETE]. The\n routine PXCESDAM has been modified to fix this defect. \n\n
\nOpen 90 day GAF score window to allow entry of new GAF scores within the\nwindow. This patchis carried as part of the SD*5.3*175 KID's\ndistribution.\n\n
\nPCE patch 46, PX*1.0*46, clinical reminders. This patch adds a new\noption that lets sites share reminder definitions. See the National\nPatch Module for a complete description.\n\n
\nVHA Directive 98-058, "Sexual Trauma Counseling Care and Services"\nrequires that VHA provide care and counseling to veterans determined to\nhave been a victim of sexual trauma while the veteran was serving on\nactive duty. This patch will focus on the data collection for this\ndirective.\n \nThis is the PCE portion of the overall patch. See DG*5.3*195\n\n
\n 1. Some sites have reported 'subscript too long' errors when\n PROVIDER ENCOUNTER COUNTS]. The routines PXRRFDD, PXRRLCD,\n PXRRPRD, PXRRWLD and PXRRPAD have been modified to fix this\n defect. \n \n 2. The PCE Encounter Summary report does not properly handle\n encounters having multiple providers. This problem was noted in\n NOIS messages PRO-0898-10847 and MIN-1198-41070. It affects the\n option PCE Encounter Summary [PXRR PCE ENCOUNTER SUMMARY]. The\n routines PXRRWLD, PXRRWLPR, PXRRWLS2, PXRRWLSA and PXRRWLSE have\n been modified to fix this defect. \n running PCE reports, even though the reports meet standards. \n The subscripts have been shortened to make this less likely. \n This problem was noted in NOIS messages BYN-0998-10088 and\n ISA-1098-11607. It affects the options PCE Encounter Summary\n [PXRR PCE ENCOUNTER SUMMARY], Diagnosis Ranked by Frequency\n [PXRR MOST FREQUENT DIAGNOSES], Location Encounter Counts [PXRR\n LOCATION ENCOUNTER COUNTS], Patient Activity by Location [PXRR\n PATIENT ACTIVITY BY LOC] and Provider Encounter Counts [PXRR\n\n
\nPCE patch 53, PX*1.0*53, clinical reminders. This patch adds data caching\nto improve performance. See the National Patch Module for a complete\ndescription.\n\n
\nPX*1.0*9 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nPCE DATABASE API'S -V CPT ONLY\n\n
\nPCE patch 63, PX*1.0*63, clinical reminders. This patch adds a new report \nfunction REMINDERS DUE REPORT.\nSee the National Patch Module for a complete description.\n\n
\nWhile Visit Tracking, namespace VSIT, went out as a distinct package, it is\nnow consolidated with PX and should have as its Parent Package, PCE \nPATIENT CARE ENCOUNTER. That means future patches to routines in the \nVSIT namespace should be sent out under PX* and the second line for any \npatched VSIT routines will now reflect the new ownership. \n\n
\nCPT MODIFIERS\n\n
\nChanges for the MST field in PCE for the DATA2PCE, PXCA API's and the Data\nentry option.\n\n
\nPCE file allows LAYGO to file 200\n\n
\nPCE Report does not recognize events which occurred at non-VA sites.\nAlso, this patch addresses the issue of when a user sends a PCE Report\nto the printer queue, the user's default editor type reverts to a\nline editor.\n\n
\nPCE ENCOUNTER MISSING\n\n
\nPatch 2 for PCE Patient Care Encounter 1.0\nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n \nEfficiency improvments in PCE's Clinical Reminders.\n \nChanges to the logic to allow taxonomy findings be used in the date due\ncalculation. The logic for computed findings, health factors, and taxonomies\nwas changed so that a frequency must be specified in order to use anyone of\nthese findings to change minimum age and maximum age.\n\n\n
\nVisit File Creation\n\n
\nPCE Encounter Lock\n\n
\nSuppress GAF score for collateral patients\n\n
\nREPORT BY DIAGNOSIS\n \nA description for this build can be found on the National Patch Module\nunder Patch PX*1*94.\n\n
\nThis is a one-time PATIENT/IHS file clean up. \n\n
\nDATA2PCE API Errors.\n \nA description for this build can be found on the National Patch Module\nunder Patch PX*1*69.\n\n
\nPCE Cross Reference Cleanup Error.\n \nA description for this build can be found on the National Patch Module\nunder Patch PX*1*100.\n\n
\nPX*1.0*15 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nDATA2PCE API Provider Primary/Secondary status check.\n \nA description for this build can be found on the National Patch Module\nunder Patch PX*1*102.\n\n
\nThis patch addresses the PCE provider selection and lookup issue, as\n-DSM-I-ECODE, MUMPS error code: M7\n%DSM-I-ATLABEL, RELOOK+7^PXBGPRV2:1 S\nTOTAL=$P(^TMP("PXBTOTAL",$J,"DILIST",0\n),"^",1)\n \n \nThe second subscript of the global-variable ^TMP would contain a "$J"\nvalue. The problem seems to have been caused by errant data in a\n"person/provider's record" . \n \nfollows:\nDuring a lookup, LIST^DIC (by default) retrieves a record's "WRITE"\nfields; the "TITLE" field of a person's record is such a field. The WRITE\nfields may vary per source file. The TITLE field is a non-\nrequired ("null" is not invalid), pointer field. When LIST^DIC \nencounters a "broken pointer"/invalid data in any person's TITLE \nfield while attempting to create a PCE provider selection list, \nLIST^DIC immediately generates an error, discontinues the lookup \nprocess, and does not return any list of provider choices [i.e. \n^TMP(..."DILIST")]. The standard LIST^DIC call does not account \nfor errant data in fields that should have been validated early \n \nduring person record processing. The errant data in a person \nrecord's TITLE field and the standard LIST^DIC call in the PCE \nroutine PXBGPRV2 caused provider lookups to fail when processing\nin PCE.\n \nAddressing the "RELOOK+7^PXBGPRV2" error, patch PX*1*105 redesigns the\nLIST^DIC call in PXBGPRV2 suppressing LIST^DIC 's need of valid TITLE\ndata. The standard PCE LIST^DIC call explicitly requests "NAME" as a\nresult of a lookup and implicitly requests default WRITE fields such as\nthe TITLE field. The redesigned call in PXBGPRV2 will force LIST^DIC to\nSeveral NOIS calls have reported an error while processing provider data\n"ignore" WRITE fields and return only NAME data, therefore complete\nprovider lookup processing within PCE and avoid fields unneeded by PCE\nthat may contain errant data. PX*1*105 will resolve this issue in PCE.\nspecifically provider lookups in different PCE modules. The error\npresented itself at the RELOOK+7 label in routine\nPXBGPRV2. The exact error displayed as follows:\n \n%DSM-E-UNDEF, undefined variable ^TMP("PXBTOTAL",557880418,"DILIST",0)\n\n\nThis patch enables adding/editing CPT Procedures to an Encounter that is not\nan Appointment and which was created with a Credit Stop Code.\n\n\n
\nPRACTICE PROFILING/PCE PHASE II\nThe Under Secretary for Health chartered a Steering Committee to develop\na national strategy and plan for implementing Practice Profiling\nnationwide.\nThis patch implements the PCE requirements for Practice Profiling\n\n
\nPatch PX*1.0*92 has been created in response to several NOIS's -\nBAY-1100-31050 and its duplicates. The error <SUBSCRIPT>LI1+19^PXBPPOV\nre-occurred and was caused by a ^DIC Lookup that, in some cases, is\nunable to return a selected, listed value. ^DIC is not able to\nchoose between values that are interpreted as "identical." As an example\n^DIC considers "94.0" and "94." identical; so if the user selected\n"94." , ^DIC needs to know the user means exactly "94." PX*1*92\nresolves this issue by redesigning the ^DIC Lookup and allows the\nretrieval of "exact" user selections.\n\n
\nThis Patch makes modification to DBIA #2348: 'SERVICE CONNECTED CONDITIONS'\ncall.\n\n\n
\nThe changes included in this patch are described in the description of\npatch PX*1*111 (Mill Bill - LTC/Visit/Medication Co-Pay) in the National\nPatch Module.\n\n
\nThis patch corrects the following problems related to the PXTT EDIT HEALTH\nsetting/editing a national package.\n \n\nFACTORS option:\n- users could exit before filling in all required fields and that could have\n contributed to the further syntax errors.\n- validation of a duplicate name was not working correctly when an originally\n entered factor, displayed as default, was changed into an already existing\n one.\n\nAdditionally the patch introduced PXNAT varable to be set to 1 for\n\n
\nThis patch adresses multiple NOIS, related to missing fields in V CPT records,\nstarting from PROVIDER NARRATIVE. That missing field was causing errors that\noriginated the NOIS(es).\n\n\n
\nPX*1.0*17 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nThis patch is in response to Item #22 in the Rossio Report. In the area\nof Means Test (MT) Deficiencies, Item #22 required that the Veterans\nHealth Administration (VHA) identify best practices for means testing and\nacquiring veterans' signatures at the local level and explore the\npromulgation of these best practices throughout the system. This patch\nincorporates into the Patient Care Encounter software an Enrollment\nApplication Systems (EAS) API which will inidcate whether to block the\ncheckout of an existing appointment through the PCE menu or not. This\nblocking is based on the veterans current means test status.\n\n
\nThis is a clean up patch of V CPT records, following already released \nPX*1.0*117 that prevents future occurrences of filing incomplete V CPT records.\nAdditionally a correction is made to VSIT routine to return a correct\ninformation, related to entered either Visit IEN or Visit's ID.\n\n\n
\nThe changes included in this patch are described in the description\nsection of patch PX*1*115 in the National Patch Module.\n\n
\nCorrectly evaluate and display different formats of CPT codes when entered\nseparately or as multiple. Additionally prompts for the provider and other\nentries, related to the selected procedure, when procedures are entered as\nmultiple.\nCalls for a list of providers for an encounter were redesigned to return\nthe correct list without duplicates, if any. Also, the PCE will not change\nthe primary provider if not requested.\n\n\n\n
\nIn response to Policy Board (NLB) comment on the VHA Veterans Equitable\nupdating.\n \nCurrent policy establishes a requirement to block transmission of \noutpatient encounters (ACRP) to the National Patient Care Database if the\npatient's current Means Test status equals "Required." This leads to\nunder-reported workload and inaccurate information in national\ndatabases. \n \nSoftware has been implemented which blocks the ability to schedule future \nappointments for veterans whose financial assessment needs updating. VHA \nResource Allocation (VERA) process, the CBO requests the removal of:\nDirective 2002-019, dated April 4, 2002, provided guidance to facilities \non the implementation of the appointment blocking software. If a \nveteran's financial assessment needs updating, the software prevents the \nability to make future appointments for the veteran. This restriction \nshall also be removed at the request of the CBO. \n \n(1) the current restriction that blocks transmission of outpatient \nencounters (ACRP) to the National Patient Care Database (NPCD) if a\nveteran's updated financial assessment (Means Test) information is not\ncomplete, and \n(2) the restriction that blocks the ability to schedule\nfuture appointments for veterans whose financial assessments need\n\n
\nThis patch addresses the following issues:\n- modifies DATA2PCE^PXAPI to support the entry of the Outside Location and\n properly determines the TYPE of the encounter.\n- the problem to delete completely a visit and its corresponding outpatient\n encounter, as well a credit stop visit if applicable.\n- acceptance and a proper filing of the INSITUTION if passed to PCE and it \n is different than a pointer from the Division filed of the Hospital Location.\n \n\n
\nThis patch addresses the following issues:\n- allows to enter only one primary diagnosis and not allows for duplicates\n- only one E&M procedure code may be accepted and with quantity=1 only\n- fix a misspelling in a called label to address MIW-0503-41153.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPCE Patient Care Encounter 1.0\n\n
\nFee Basis patch FB*3.5*5. This patch contains the output \ntransform on three fields, PLACE OF SERVICE (162.03,30), HCFA\nTYPE OF SERVICE (162.03,31) and DISCHARGE TYPE (162.7,29). Also \nincluded in this patch are two routines; FBPAID and FBAACCB0.\n\n
\nState Home Program Enhancement\n 1. State Home Main Menu added.\n 2. Four options added for entry/edit of State Home authorizations.\n 3. Active Authorization Report option added.\n 4. The sort order of authorizations listed to the screen for all FEE\n programs has been changed to list the later From Dates first.\n 5. Veteran MRA modified to support State Home authorizations and multiple\n MRAs for veteran.\n\n
\nThis patch enhances VistA Fee Basis to enforce segregation of duties when\npayments are certified. This patch also adds the new FB SEG DUTY RPT\noption and modifies the batch purge functionality to require the date to\nbe at least 18 months ago.\n\n
\nFB*3.5*118 does the following:\n -Updates the Resource Based Relative Value Schedule (RBRVS) fee schedule \n with changes for October 2010. \n -Updates the Resource Based Relative Value Schedule (RBRVS) fee schedule\n with changes for Calendar Year (CY) 2011. \n -Updates the modifiers to be more compliant with medicare rules.\n\n
\nARCH project for Fee Basis\n\n
\nThis patch is part of the VistA Fee and IFCAP Automation Enhancements\nproject (aka Duplicate Payments). This patch will enable Fee Basis to\nreceive three new types of messages from Central Fee. However the data in\nthese message will ignored by this patch. A subsequent patch, FB*3.5*132,\nwill contain the functionality to process the data sent by Central Fee.\n\n
\nAdd new API for determining if patient has any FEE authorizations.\n\n
\nThis patch will enhance Fee Basis to capture additional data associated \nVA to review and report on purchased care.\nwith non-VA care. Contracts can be specified for Medical Fee and Civil\nHospital authorizations and payments. Civil hospital invoices will allow \nentry of larger dollar amounts, additional diagnosis codes, present on\nadmission indicators for diagnosis codes, the admitting diagnosis code,\nand additional procedure codes. The existing transmissions to NVH Pricer\nand Central Fee will be modified to include additional data elements. The\ntransmission of these additional data elements will make it possible to\ncomply with inpatient pricing requirements and improve the ability of the\n\n
\nThis patch addresses the following:\n -Updates the Resource Based Relative Value Scale (RBRVS) fee schedule\n with changes for Calendar Year (CY) 2012.\n -Updates some Relative Value Units (RVUs) for the RBRVS for CY 2011. \n\n
\nVISTA FINANCIALS ANNUAL ENHANCEMENT 7 - FEE INVOICE DATE CONTROLS\nUPDATED TO INCLUDE PATCH 108 BUILD USER$:[THAYERC]FEE3_5P108T0307A.KID\nAlso add 2 new routines (FBAACO1 and FBCHEP) for INPATIENT invoice \ndate validation.\n\n
\nFIRST BUILD OF FEE BASIS v3.5 PATCH 135 being created for phase two of \nthe VistA 5010 Fee Basis project. This build only contains data \ndictionary updates\n\n
\nThis patch is part of the VistA Fee and IFCAP Automation Enhancements\n o Rejection of payment line items by Central Fee will be transmitted to\n VistA Fee Basis via new transactions that update the VistA database. \n Users will no longer manually record such rejects in VistA.\n o Completion of a payment batch using the Finalize a Batch option in\n VistA Fee Basis will automatically generate a new transaction that is\n sent to Central Fee. This new transaction will instruct Central Fee of\n any payment line items that must be deleted (i.e. local rejects) and\n instruct Central Fee to release the remainder of the batch to\n downstream payment systems such as FMS. This new transaction will\n replace all use of 994 code sheets in IFCAP.\nproject (aka Duplicate Payments).\n \nThis patch also resolves three existing software faults that were \ndiscovered during analysis and design of the patch.\n \nThis patch will enhance the interface between VistA Fee Basis and Central\nFee to improve the consistency of payment line item data between the\nsystems. This will prevent duplicate ICN payments by ensuring that a \npayment line cannot be reprocessed in VistA Fee Basis unless it has been \nremoved from Central Fee. The primary interface enhancements consist of \nthe following:\n\n
\nThis patch addresses the following:\n- Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule \n with changes for Calendar Year (CY) 2013.\n- Stops the payout of Mental Health Services at 105% after March 1st, 2012\n as per the Middle Class Tax Relief and Job Creation Act of 2012.\n\n
\nThis patch adds two new Purpose Of Visit (POV) codes to the Fee Basis \nPurpose of Visit (#161.82) file for Newborn care, and updates the name of \none existing POV code.\n\n
\nThis patch addresses the following:\n- Modifies the logic when determining the symbols used for payments \n in the Payment History Display.\n- Resolves an undefined error in routine FBPHON from variable DFN.\n- Resolves an undefined error within the [TRAVEL PAYMENT] option due to \n batch files missing a status.\n\n
\n ***NOTICE***\n Registration system (DG), Fee Basis System (FB), and Integrated Billing\n \n \n File Name (#) Field Name (#) New/Modified/Deleted\n ------------- -------------- -----------------\n TYPE OF PATIENT (#391) NAME (#.01) New Data content\n (Single new record added "NEWBORN OF VETERAN") No Data Dictionary\n changes\n \n VA ADMITTING REGULATION (#43.4) NAME (#.01) New Data content\n (Single new record added "NON-VA FOR FEMALE VET+NEWBORN")\n (IB).\n No Data Dictionary\n changes\n \n INCONSISTENT DATA ELEMENTS (#38.6) New Data content\n Two new records added:\n 313 NEWBORN REQUIRES SPONSOR\n 314 NEWBORN NEEDS ELIGIBLE SPONSOR.) No Data Dictionary\n changes\n \n \n \n Forms Associated:\n \n Form Name File # New/Modified/Deleted\n --------- ------ --------------------\n N/A\n \n Mail Groups Associated:\n \n Mail Group Name New/Modified/Deleted\n --------------- --------------------\n Below is a list of all the applications involved in this project along with\n N/A\n \n Options Associated:\n \n Option Name Type New/Modified/Deleted\n ----------- ---- --------------------\n N/A\n \n Protocols Associated:\n \n their patch number:\n Protocol Name New/Modified/Deleted\n ------------- --------------------\n N/A\n \n Security Keys Associated:\n \n Security Key Name\n -----------------\n N/A\n \n \n Templates Associated:\n \n Template Name Type File Name (#) New/Modified/Deleted\n ------------- ---- ------------- --------------------\n \n \n Additional Information:\n \n \n New Service Requests (NSRs):\n APPLICATION/VERSION PATCH\n -----------------------------\n NSR 20100901\n \n Patient Safety Issues (PSIs):\n ------------------------------\n N/A\n \n Remedy Ticket(s) & Overviews:\n -----------------------------\n N/A\n ---------------------------------------------------------------\n \n \n Test Sites:\n -----------\n \n LEXINGTON\n PUGET SOUND\n \n \n Documentation Retrieval Instructions:\n PATIENT REGISTRATION (DG) V 5.3 DG*5.3*867\n -------------------------------------\n Updated documentation describing the new functionality introduced by this\n patch is available.\n \n The preferred method is to FTP the files from ftp://download.vista.domain.ext/\n This transmits the files from the first available FTP server. Sites may also\n elect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n FEE BASIS (FB) V 3.5 FB*3.5*146\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \n The documentation will be in the form of Adobe Acrobat files.\n \n Documentation can also be found on the VA Software Documentation Library\n at: http://www4.domain.ext/vdl/\n \n File Description File Name FTP Mode\n --------------------------------------------------------------------------\n Fee Basis User Manual fb3_5um.pdf Binary\n Users should be made aware that processing of Newborn claims must ONLY be\n INTEGRATED BILLING (IB) 2.0 IB*2.0*499\n PIMS v5.3 ADT User Manual Registration dg_5_3_reg_um.pdf Binary\n \n The procedure guide, Care for Newborn of Women Veterans, located at\n http://nonvacare.hac.domain.ext/policy-programs/procedure-guides.asp,\n should be distributed to those personnel registering newborns and/or\n processing newborn claims.\n \n \n Patch Installation:\n \n \n \n Pre/Post Installation Overview\n ------------------------------\n There are three post installation routines associated with this patch DG867PO,\n FB146PO, and IB499PO. These routines primarily serve as filters for the data\n transmitted to the appropriate files listed above, so that only the intended\n data is delivered. The only exception is the IB499PO routine which\n programmatically makes an addition to the help text of the FAMILY PREFIX field\n (#.03) in the SPONSOR RELATIONSHIP file (#355.81). These post installation\n routines may be deleted after successful installation of the NEWBORN DG FB IB\n The patches (DG*5.3*867, FB*3.5*146, and IB*2.0*499) are being released in the\n BUNDLE 1.0\n \n Installation Instructions\n -------------------------\n This patch may be installed with users on the system although it is\n recommended that it be installed during non-peak hours to minimize potential\n disruption to users. This patch should take less than 5 minutes to install.\n \n FB*3.5*147 is a required patch and must be installed before DG*5.3*867.\n \n Kernel Installation and Distribution System (KIDS) multi-build distribution\n DG*5.3*867 is one of three patches for this release (including FB*3.5*146 and\n IB*2.0*499). The patches will be installed as a bundle in the following order:\n \n \n 1) DG*5.3*867\n 2) FB*3.5*146\n 3) IB*2.0*499\n \n \n Pre-Installation Instructions\n NEWBORN DG FB IB BUNDLE 1.0\n -----------------------------\n 1. OBTAIN PATCHES\n --------------\n Obtain the host file NEWBORN_1_2_DG_FB_IB.KID which contains the following\n patches:\n \n DG*5.3*867\n FB*3.5*146\n IB*2.0*499\n \n \n Sites can retrieve VistA software from the following FTP addresses. The\n preferred method is to FTP the files from:\n \n download.vista.domain.ext\n \n This will transmit the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n The purpose of the Caregivers: Newborn Claims Processing Enhancement Project\n Salt Lake City ftp.fo-slc.domain.ext\n \n The NEWBORN_1_2_DG_FB_IB.KID host file is located in the anonymous.software\n directory. Use ASCII Mode when downloading the file.\n \n 2. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu option\n [XPD MAIN]:\n \n is to enhance VistA Fee Basis application in support of compliance with\n Edits and Distribution ...\n Utilities ...\n Installation ...\n \n Select Kernel Installation & Distribution System Option: Installation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Public Law 111-163, the Caregiver and Veterans Omnibus Health Services Act\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\n \n Select Installation Option:\n \n 3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD\n -------------------------------------\n From the Installation menu, select the Load a Distribution option.\n of 2010. This law makes changes to sections of Title 38, United States Code\n \n When prompted for "Enter a Host File:" Enter the full directory path\n where you saved the host file NEWBORN_1_2_DG_FB_IB.KID\n (e.g., SYS$SYSDEVICE:[ANONYMOUS]NEWBORN_1_2_DG_FB_IB.KID)\n \n When prompted for "OK to continue with Load? NO//", Enter "YES."\n \n The following will display:\n \n Loading Distribution...\n entered in VistA. No entry in FBCS should be performed.\n to furnish health care services to a newborn child of a Woman Veteran who\n \n NEWBORN DG FB IB BUNDLE 1.0\n DG*5.3*867\n FB*3.5*146\n IB*2.0*499\n Use INSTALL NAME: NEWBORN DG FB IB BUNDLE 1.0 to install this\n distribution.\n \n 4. RUN OPTIONAL INSTALLATION OPTIONS FOR MULTI-BUILD\n -------------------------------------------------\n is receiving maternity care furnished by the Department of Veterans Affairs\n From the Installation menu, you may select to use the following options\n (when prompted for the INSTALL NAME, enter NEWBORN DG FB IB BUNDLE 1.0\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as data dictionaries or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, data dictionaries, templates, etc.).\n (VA) for not more than seven days after the birth of the child.\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n 5. INSTALL MULTI-BUILD\n -------------------\n This is the step to start the installation of this KIDS patch. This will\n need to be run for the NEWBORN DG FB IB BUNDLE 1.0\n \n a. Choose the Install Package(s) option to start the patch\n \n install.\n b. When prompted for the "Select INSTALL NAME:" enter\n NEWBORN DG FB IB BUNDLE 1.0\n c. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//", answer NO\n d. When prompted "Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? NO//", answer NO\n e. When prompted "Device: HOME//", enter HOME\n to display the Install message on the screen (or enter the device\n you want to print the Install message). You may queue the\n The scope of these enhancements is to capture information on healthcare\n install if you wish.\n \n \n Post-Installation Instructions\n ------------------------------\n \n *** IMPORTANT NOTE ***\n Please note there are three post installation routines that may be deleted\n after successful installation of the NEWBORN DG FB IB BUNDLE 1.0. These are:\n \n services provided to newborn children of Women Veterans. Affected functions\n DG867PO\n FB146PO\n IB499PO\n include eligibility determination, enrollment and registration, documentation\n of referrals and authorization for care, claims processing, and payment. Only\n modification to the Fee Basis (FB) and the Registration (DG) packages are\n necessary to meet the requirements of this enhancement. The Integrated\n ***********\n Billing (IB) Patch is included to provide required data for the Fee Basis\n install to reference.\n \n \n The primary purpose of this enhancement is to allow the Electronic Filing of\n Newborn claims.\n \n Functional Description\n ------------------------------\n The following features and functions have been added to the Fee Basis workflow\n This patch, along with FB*3.5*146 and IB*2.0*499, is being released as a\n process applying to both Civil Hospital and Medical Fee:\n \n 1. A new Patient Type of NEWBORN OF VETERAN has been added to the TYPE OF\n PATIENT file (#391). This new selection will be available on Registration\n Screen <7>.\n \n 2. A sponsor is required for all Newborns determined by having the DOB less\n than one (1) year from the present date. An inconsistency check has been added\n to check the presence of a sponsor. If an inconsistency is found the\n inconsistency check will prompt the user to return to Screen <15> in\n bundle, and all three will be automatically installed in the correct order.\n registration to enter a Sponsor.\n \n 3. All Sponsors for Newborns must be listed as eligible for care. An\n inconsistency check will check the status of the Sponsors Eligibility. The\n check will trigger if the Sponsor has no Eligibility status.\n \n All other statuses (i.e. Pending Verification, Verified, and Pending\n Re-verification) are acceptable.\n \n 4. Fee Authorization dates associated with Newborns have checks in place to\n \n not allow Authorization dates that fall outside the accepted range of Newborn\n Authorization. The range is DOB to DOB+7. The system will warn the user and\n not accept an Authorization date that falls outside the appropriate range for\n a Newborn.\n \n 5. When a Veteran Mother of a Sponsored Newborn is reviewed in the\n Registration screens, Screen <15> will display the Newborn(s), with the\n additional header of "Sponsored Newborn".\n \n 6. The FAMILY PREFIX "NB Newborn of Vet" has been added to the Help text in\n This patch has enhancements that extend the capabilities of the Veterans\n the FAMILY PREFIX field (#.03) in the SPONSOR RELATIONSHIP file (#355.81)\n \n 7. "NON-VA FOR FEMALE VET+NEWBORN 17.38" was added to the VA ADMITTING\n REGULATION file (#43.4). This new Admitting Regulation is available when\n editing the 7078.\n \n 8. The following default values were added when entering a Newborn with a\n date of birth of less than one (1) year from present date. Defaults will only\n be assigned when specified screens are accessed during the registration\n process: PATIENT DATA, SCREEN <2> Marital field is defaulted to NEVER MARRIED.\n Health Information Systems and Technology Architecture (VistA) Patient\n APPLICANT/SPOUSE EMPLOYMENT DATA, SCREEN <4> Status field is defaulted to NOT\n EMPLOYED. FAMILY DEMOGRAPHIC DATA, SCREEN <8> Married Last Year field is\n defaulted to NO.\n \n \n Patch Components\n ================\n \n \n Files & Fields Associated:\n\n
\nThis Patch Addresses 1 issue:\n \n1. The error "<UNDEFINED>ANC+8^FBPCR67" occurs when running \n the Potential Cost Recovery Report [FB PRC].\n\n
\nFix Enter CNH Payment to prevent an undefined variable error that can\noccur after FileMan v22 is installed.\n\n
\nThis patch addresses the following:\n \n- Blank MRAs are being transmitted to Central Fee\n- The low batch warning message is being triggered too late.\n- The calculation for batches remaining is incorrect.\n\n
\nThis patch addresses the following:\n- Modifies logic when applying the "Mill-Bill" claims 70% reduction when \n local fee schedule (75th percentile) rates are used.\n- Changes the fee program for ancillary payments entered using [FBCH\n MULTIPLE PAYMENTS] option from "outpatient" to "civil hospital"\n- Modifies the sort and print routines for Veteran Payment History report\n to display the '#' symbol for voided payments.\n- Modifies the Fee Basis payment system to allow users holding the \n "FBAASUPERVISOR" key to exceed the amount of billed charges.\n\n
\nDescription:\ncodes to more than 68,000. Procedure Coding System (ICD-10-PCS) procedure \ncodes increase from about 3,800 ICD-9 codes to nearly 87,000. Both \nsystems also expand the number of characters allotted to seven \nalpha-numeric characters. This value does not include the decimal point, \nwhich follows the third character for the ICD-10-CM code set. There is no \ndecimal point in the ICD-10-PCS code set.\n \nThese code sets have the potential to reveal more about quality of care, \nso that data can be used in a more meaningful way to better understand \ncomplications, better design clinically robust algorithms, and better \n===========\ntrack the outcomes of care. ICD-10-CM also incorporates greater \nspecificity and clinical detail to provide information for clinical \ndecision making and outcomes research.\n \nThis patch is to implement ICD-10 Remediation for Fee Basis.\n \nThe International Classification of Diseases, Tenth Revision (ICD-10) \nClass 1 Software Remediation project replaces the 30-year-old set of \ndiagnosis and procedure codes (ICD-9-CM) that medical personnel use. \nDates of service, or dates of discharge for inpatients, that occur on or \nafter the implementation date will use the ICD-10 code set. Clinical \nModification (ICD-10-CM) diagnosis codes increase from about 13,000 ICD-9 \n\n
\nThis patch addresses the following:\n- Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule \n with changes for Calendar Year (CY) 2014.\n\n
\nThis patch is the first of two patches that enhance the Fee Basis package\nper the requirements of the VistA Fee Separation of Duties project. This\npatch makes the following changes to Fee Basis:\n o Retain historical data for unauthorized claims\n o Retain historical data for authorizations\n\n
\nVA/DoD VistA Fee-IPAC Interface Enhancement\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch. \n\n
\n1. Patient MRA rejections from FMS\n4. Patient MRA transmissions are not being sent due to deleted patient\n authorizations.\n \n2. For option 'Enter Unauthorized Claim' the response to query Mill Bill\n Claim indicator is not always stored when 'NO'.\n \n3. Authorization that are entered for Contract Nursing Home obligations \n are hitting every station's obligations for integrated sites when\n posted.\n \n\n
\nThis patch addresses the following:\n \n- Adds four new Purpose of Visit (POV) codes to the FEE BASIS PURPOSE OF \n VISIT (#161.82) file.\n\n
\n1. Error when queuing Post Commitments option for Contract Nursing\n Home (CNH) obligations. \n\n
\nFixes MRA purge options so veteran MRAs in PENDING status are not\ninappropriately deleted.\n\n
\nPatient MRA delete from FEE BASIS PATIENT MRA file when linked patient \nauthorization is deleted.\n\n
\nThis patch addresses the following 2 issues:\n (#161) file.\n \n1. The Enter Unauthorized Claim [FBUC ENTER] option is failing when \n attempting to store data in the ICD DIAGNOSIS (#.087) field in the\n AUTHORIZATION (#161.01) sub-file of the FEE BASIS PATIENT (#161) file.\n \n2. The Modify Unauthorized Claim [FBUC MODIFY UNAUTHORIZED CLAIM] option\n is failing when attempting to store data in the ICD DIAGNOSIS (#.087) \n field in the AUTHORIZATION (#161.01) sub-file of the FEE BASIS PATIENT\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2015.\n\n
\nPatch FB*3.5*172 is a Fee Basis patch for the VistA Fee Separation of\nDuties project.\n \nPatch FB*3.5*172 creates three new security keys which will be referenced\nin software exported by subsequent patch FB*3.5*154.\n\n
\nDuring installation of patch FB*3.5*165, the post-init routine performs \nto exclude payments transmitted prior to a user-specified date. The\nreport line which prints the batch number, the voucher date and the\nvoucherer is also modified to accommodate a 7-digit batch number.\na one-time (Delete Reject Flag) task that deletes the inappropriate \nreject flag from old payment line items which have payment confirmation \nor payment cancellation data. Installation of patch FB*3.5*165 also \nperforms a one-time (Remove Payment from Batch) task that removes old \npayments with payment confirmation/cancellation data from in-process \nbatches. \n \nThe Print Rejected Payment Items report [FBAA REJECT PRINT] is enhanced \n\n
\nThis patch addresses the following 3 issues:\n release of IPCT*4.0*46.\n \n3. The ANESTHESIA MINUTES (#43) field in the FEE BASIS PAYMENT (#162) \n file needs to be expanded from 3 to 4 digits to properly process \n anesthesia for labor and delivery.\n \n1. Items are missing from the Potential Cost Recovery (PCR) report when a\n patient has multiple authorizations on the same day.\n \n2. The direct global read of the SHORT NAME (#2) field in the CPT (#81)\n file must be updated to the current Application Programming \n Interface (API) for the short name to continue to display on the Fee\n Basis Patch 135 Unique Claim Identifier Display report after the \n\n
\nThis patch addresses the following issue: \n \n 1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule \n with changes for Calendar Year (CY) 2016.\n\n
\nThis patch will enhance the Fee Basis package per the requirements of the\n o Add reports to display users that entered or edited authorizations.\n o Correct an existing issue with the identification of the associated\n authorization for outpatient and ancillary payments.\n o Prevent an undefined error when a prescription is deleted.\n o Prevent an undefined error when rejected payments are re-initiated.\nVistA Fee Separation of Duties project. The patch will make the \nfollowing changes to Fee Basis:\n o Add new security keys.\n o Revise locks on menu options to enhance separation of duty controls.\n o Attach menu options to additional menus.\n o Revise locks on functionality within menu options.\n o Add the Security Key Report for Fee Basis\n o Prevent entry of payment or pricing if user entered the authorization.\n\n
\nThis patch updates the following:\n- The REMITTANCE REMARK (#161.93) file.\n- The ADJUSTMENT REASON (#161.91) file.\n\n
\nFEE BASIS ENHANCEMENT TO SUPPORT MASTER VETERAN INDEX DATE OF DEATH (DOD) \nRefer to patch FB*3.5*173 in the FORUM Patch Module for a complete\ndescription.\n\n
\n o Use Medicare's RBRVS fee schedule for outpatient and ancillary payment.\n\n
\nThis National Patch consists of FEE BASIS enhancements related to the \nreceived from Non-Department of Veterans Affairs (VA) providers which \nare necessary for third party billing.\n \nThe proposed enhancement seeks modifications the FB application's \nPotential Cost Recovery Report (PCRR) to ensure that all Non-VA Care \nbilled line item charges are included, regardless of responses entered\nin the FB software by Fee Clerks." By removing the report filtering\nthat pertains to the SC Condition and Potential Cost Recovery data \nvalues, line item charges previously excluded based on responses to \nPOTENTIAL COST RECOVERY and SC CONDITION prompts in FB all Non-VA \nfollowing NSRs:\ncare billed line item charges will appear on the PCRR, enabling the \nRevenue Staff to optimize cost recovery. \n \nNSR #20081010 - Billing Precertification Enhancements\n \nTypically, Department of Veterans Affairs (VA) facilities are able to \nprovide all of the necessary medical care and services required by its\npatients. However, there are times when the Veteran is not able to \naccess VA health care facilities based on geographic constraints, due \nto medical emergencies, or because it is economically advantageous to \n \nprovide treatment in the community. In these cases, the VA may \nauthorize medical care at private-sector facilities for those Veterans\nwho meet the eligibility requirements. This concept is referred to as\nFEE BASIS (FB) (or Non-VA) care.\n \nRegardless of where the care is provided, precertification is often a \nprerequisite for certain services before payment is issued by insurance\ncompanies. Precertification is the process of obtaining approval from\nthe Veteran's private insurance health plan for routine hospital \ninpatient admissions or outpatient visits prior to the delivery of \nNSR ##20110304 - Service Connected Decision\nhealth care. Currently, Medical Care Collections Fund (MCCF) Staff is \nnot notified of scheduled VA-provided outpatient services requiring \nprecertification. Notification regarding authorized \nnonservice-connected FB care is received after treatment has been \nrendered. As a result, VA Medical Centers (VAMCs) often miss \nopportunities to be reimbursed by insurance companies for care due to \nthe lack of obtaining timely precertification.\n \nThe goal of this project is to assist the VAMCs in obtaining timely p\nrecertification from third party payers before care is rendered by \n \nnotifying the appropriate staff as soon as VA-provided outpatient \nservices requiring precertification are scheduled and authorizations \nare created in the Veterans Health Information Systems and Technology \nArchitecture (VistA) Fee Package for inpatient or outpatient care. This\nwould also provide an opportunity for insurance identification/ \nverification processes (either internally or externally/outsourced) to \nbe completed prior to treatment.\nThe Fee-Revenue Service Connected (SC) Condition Decision project will \nenhance the interface between the Integrated Billing (IB) and Fee Basis\n(FB) Veterans Health Information Systems and Technology Architecture \n(VistA) applications by automating the transfer of data elements \n\n
\nThis patch adds six new Purpose of Visit (POV) codes to the FEE BASIS\nPURPOSE OF VISIT (#161.82) file.\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2017.\n\n
\nThis patch addresses the following issue:\n \nA syntax error occurs when using a custom menu option which contains \neither the Re-open Unauthorized Claim [FBUC REOPEN] or the Modify \nUnauthorized Claim [FBUC MODIFY UNAUTHORIZED CLAIM], and Fee Patient \nInquiry [FBAA PATIENT INQUIRY] options.\n\n
\nHAC EDI Purchase Care ERA Inc. 2 Development\n\n
\nThis patch updates the FEE BASIS CPT RVU (#162.97) file for codes\n77065-77067.\n\n
\nThis effort is focused on providing Other Health Insurance (OHI) to users \nscreens.\n \nThis patch implements the MUMPS database portion of the project.\nof VistA Fee. This will be facilitated through a collaboration with DSS, \nInc. to transmit data from the central server located at the Health \nAdministration Center (HAC) through Fee Basis Claims System (FBCS) and \ninto the local facility VistA Fee.\n \nThe new database fields introduced by the patch are going to be used by \nFBCS application that will be modified by DSS. New FBCS functionality will\nmake OHI data available for VA users on its Graphical User Interface (GUI)\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2018.\n\n
\nThis patch addresses the following issue:\n \n1. An undefined error occurs when a user fills out a prescription\n reimbursement for a patient.\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2019.\n\n
\nAdd RBRVS physician fee schedule for calendar year 2000 to the software.\n\n
\nHAC EDI CLAIMS ATTACHMENTS\n\n
\nPlease refer to Patch description for installation instructions.\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2020.\n\n
\nBackup of FB*3.5*184 on Jul 08, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2021.\n\n
\n Patch FB*3.5*185 will update 619 entries in the FEE BASIS CPT\n RVU (#162.97) which are either missing data or have a null\n value where a zero should be. \n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2022.\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2023.\n\n
\nUpdate the CPT codes with RVU values of zero for CY2023\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2024.\n\n
\n o Improve validation checks for the Multiple Payment Entry option.\n o Fix several options to show the description of a CPT Modifier even when\n the modifier value can have more than one meaning.\n\n
\nThis patch addresses the following issue:\n \n1. Updates the Resource Based Relative Value Scale (RBRVS) Fee Schedule\n with changes for Calendar Year (CY) 2025.\n\n
\nThis patch will address two separate issues.\n on letters that could go outside of the VHA.\n\n\n\n1. It will add the Mail Code (#5.5) field to the FEE BASIS SITE PARAMETERS \n (#161.4) file. This will allow the sites to edit and update this field\n to insure that the correct Mail Code appears in the upper right hand\n corner of their Unauthorized Claim letters.\n\n2. Several of the Fee Basis letters will be updated to use the Name\n Standardization API to insure that the veteran's name appears correctly\n\n
\nThis patch adds the following codes to the software:\n o New Purpose of Visit Code: CHIROPRACTIC CARE (75)\n o New Participation Code: DOCTOR OF CHIROPRACTIC (15)\n o New Specialty Code: CHIROPRACTIC (53)\n\n
\nEnhancement patch to add 12 purpose of visit codes for use with the\nMedical Fee (Outpatient) program.\n\n
\nFee Basis patch seven.\n\n
\nCORRECT %DT, %DT(0) ERRORS AND PRINTING PROBLEMS\n\n
\nAdd RBRVS physician fee schedule for calendar year 2001 to the software.\n\n
\nModifications to Fee Basis to handle merge of entries in PATIENT (#2).\n 1. Update cross-references that depend on a patient ien, so they will be\n updated when the patient is changed.\n 2. Add a special patient merge routine for FEE BASIS to handle files that\n are dinumed with the PATIENT file, free-text pointers, and internal\n entry numbers (iens) sent to the AAC.\n 3. Update the FBAA PAID SERVER to check for merged patients.\n 4. Perform a one-time task to identify previously merged patients and\n update FEE Basis data accordingly.\n\n
\nREMOVE OBSOLETE FEE BASIS MENU OPTIONS, ROUTINES, AND INPUT TEMPLATE\n\n
\nPhase 1 enhancements to support processing of Mill Bill Emergency Care\n(38 U.S.C. 1725) claims.\n\n
\nADD LONG TERM CARE PURPOSE OF VISIT CODES\n\n
\nFPDS SOCIO-ECONOMIC CODES CHANGES\nThis patch addresses modifications related to FPDS codes changes\nintroduced by IFCAP patch (PRC*5.1*16).\n\n
\nPROBLEM WITH LOOK-UP IN SERVICE PROVIDED MULTIPLE\n \nThis patch addresses the NOIS call PRE-1199-60596. \nPlease look at patch description on Forum for details.\n\n
\nPUBLIC HOSPITAL ACTIVITY REPORT INCORRECT\n\n
\nUPDATE TO RBRVS 2001 PHYSICIAN FEE SCHEDULE\n\n
\nUNAUTHORIZED CLAIM UPDATE STATUS/YR 2000\n\n
\nLTC RESPITE POV CODE UPDATE\n\n
\nMill Bill Military Sexual Trauma (MST) Enhancement\n o Add purpose of visit "Military Sexual Trauma Services" (55).\n o Add MST Report option.\n\n
\n UPDATES FOR UNAUTHORIZED CLAIMS\nThis patch addresses the following NOIS messages:\n BAY-0600-31908\n MUS-0100-70289\nPlease look at patch description on Forum for details.\n\n
\nEmergency Care phase 2 enhancements.\n\n
\nFPDS Reporting Phase II\n\n
\nAdd RBRVS physician fee schedule for calendar year 2002 to the software.\n\n
\nERROR DURING MERGE\n\n
\nUPDATE POV CODE 43\n\n
\n7078 AUTHORIZATION OVERWRITTEN\n\n
\nDISPOSITION LETTER ADMISSION DATE ERROR\n\n
\nEnhancement to maintain socio-economic characteristics of vendors for\nFederal Procurement Data System (FPDS) reporting.\n o BUSINESS TYPE (FPDS) and SOCIOECONOMIC GROUP (FPDS) fields added to\n FEE BASIS VENDOR file.\n o Existing vendor edit options modified to include the new fields.\n o New vendor edit option to just update the new fields for existing\n vendors.\n o New List Vendors Without FPDS Data option to report vendors with a\n blank BUSINESS TYPE (FPDS).\n\n
\nPotential Cost Recovery Report modification for LTC Copay Phase 3\n\n
\nLTC Fee Basis Workload Capture\n\n
\nData in the local Vendor file will be lost if the FBAA FMS UPDATE process \nis activated when no changes to the local Vendor file have occurred.\n\n
\nSHOW 4 DIGIT YEAR IN AUTHORIZATION EDIT\n\n
\nHIPAA Confidential Communications Phase 1\n\n
\nGENERIC PRICER: LETTER USED IN PRIMARY DIAGNOSTIC CODE\n\n
\nCorrect MUMPS M7 error. \n\n
\nGMT2 MODIFICATIONS FOR FEE BASIS\n\n
\nHIPAA CC PHASE 2\n\n
\nRBRVS- FEE BASIS SCHEDULE UPDATE\n\n
\nEnhancement to include socio-economic data in Vendor MRA messages.\n o Modified C1 and C4 Batch Types to include data elements.\n o Added new action 'F' (FPDS-Only) for Vendor MRA messages.\n o Post-Init queues MRA messages for vendors with data.\n\n
\nCNH STRING ERROR\n\n
\nPlease reference the patch description for this patch in the National \nPatch Module.\n\n
\nCODE SET VERSIONING\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nUPDATE TO RBRVS 2003 PHYSICIAN FEE SCHEDULE\n\n
\nThis patch contains enhancements for Fee Basis related to VA compliance\nwith the HIPAA transaction and code set final rule. This patch will\nsupport the new Fee Payment Processing System (FPPS) located at the Health\nAdministration Center (HAC) in Denver.\n\n
\nA FEE BASIS ROUTINE WAS MODIFIED TO CORRECTLY TEST FOR PREVIOUS PAYMENTS \nBEFORE ALLOWING THE CANCELLING OF AUTHORIZATIONS.\n\n
\nRESOLVE FEE BASIS ID CARD IN PATIENT MERGE AND CORRECT DD DECRIPTION\n\n
\nPROBLEM WITH MULTIPLE PAYMENT ENTRY\n\n
\nThis patch addresses the following NOIS.\n ISW-1103-20349 Adjustment data not sent to FPPS when amount is negative.\n MIN-1103-40659 Undefined variable FBFPPSC when prescription added to\n previously entered pharmacy invoice.\n\n
\nCORRECT THE THE STATISTICAL ROUTINE FBUCSTAT TO NOT COUNT REJECTED \nPAYMENTS.\n\n
\nExamines and corrects FEE BASIS ID CARD AUDIT (#161.83) file data.\n\n
\nIf a "?" is entered at the Enter Nursing Home Rate: prompt while using \nthe Update Vendor Contract/Rates - CNH [FBCNH UPDATE VENDOR CONTRACT]\noption, an undefined error for variable DIR(0) may occur or DIR gets lost\nand displays number select display of rates.\n\n
\nEnhancement patch to\n1. Enhance selected existing reports to include new data captured since\n patch FB*3.5*61.\n2. Add new report to list unauthorized EDI claims that were disapproved.\n3. Update VA fee schedule compilation to consider units for claims with a\n date of service in FY 2004.\n4. Modify Selection Capability for Suspension Letters Module.\n\n
\nMODIFY POTENTIAL COST RECOVERY REPORT\n\n
\nThis patch will prevent the canceling of a Fee Basis Authorization with \nno vendor specified that has payments associated to it.\n\n
\nThis Patch addresses two issues: The first, Allow the sites to suspend \npayment for a prescription that is not covered. The second, To correct \nthe "AF" X-ref by using FileMan call to populate the field AUTHORIZATION.\n\n
\nHIPAA CC PHASE III\n\n
\n \nThis patch adds the RBRVS fee schedule for calendar year 2004 to the FEE\nBASIS software.\n\n
\nFee Basis Encapsulation API enhancement.\n Add API $$RXSUM^FBRXUTL()\n Add API $$AUTHL^FBUTL()\n Modify API EN^FBHLZFE()\n\n
\nThis patch addresses the problem encountered when the DATE OF SERVICE is \nentered for an outpatient or ancillary payment(FEE BASIS PAYMENT #162 \nfile), the software will inappropriately skip the validation checks when \nthere is already data on file for the same PATIENT, VENDOR, and INITIAL \nTREATMENT DATE (date of service).\n\n
\nYEAR 2000 Renovations.\n\n
\nCODE TEXT DESCRIPTORS\n\n
\nThis patch addresses two issues; one involving the assigning of FEE \nBASIS BATCH numbers and the second involving the assignment of FB INVOICE \nnumbers.\n\n
\nThis modification is to have the software skip the RBRVS fee\n schedule when modifier SG (ASC FACILITY SERVICE) has been entered. The\n software would still check the VA Fee Schedule (75th percentile). If\n the CPT and modifiers were not found on the VA Fee Schedule then it\n would return a message - "Unable to determine a FEE schedule amount.". \n In that case, the fee clerk could enter a usual & customary amount.\n\n
\nThis patch makes the following changes:\n o Use new PTF APIs to create or delete a PTF record.\n o Correct a fault that prevents deletion of a PTF record for community \n nursing home.\n\n
\nCorrect the initialization of the variable that hold the out put text for \nthe Detail Description.\n\n
\nThis patch addresses the problem encountered when the pharmacist is \nreviewing Fee Basis Prescriptions.\n\n
\nThis patch replaces a direct global read of the PSDRUG global by a VA \nFileman call in support of the Pharmacy Encapsulation project. It also\nfixes a bug that prevented display of the generic drug equivalent during\ncompletion of a fee pharmacy invoice. It also fixes problems with the \nedit after review functionality of the Review Fee Prescription option.\n\n
\nThe patch enhances all four payment batch formats (B3, B5, B9, and BT) \nthat are transmitted from VistA Fee Basis to Central FEE (AAC) to include\nadditional data elements.\n\n
\nThis patch adds the RBRVS fee schedule for calendar year 2005 to the FEE\nBASIS software.\n\n
\nPatient lookup warnings scroll too fast to be noticed [FBAA ENTER \nAUTHORIZATION].\n\n
\nFEE BASIS Extract for the Health Eligibility Center (HEC-Atlanta).\n 1) New routine to build HL7 ZFE segments for FEE authorization data.\n 2) New mumps cross-references to call IVMPLOG when File 161 edited.\n 3) Post-Install to log existing FEE BASIS PATIENTS in daily transmission.\n\n
\nAdding ALABAMA zip codes.\n\n
\nThis patch fixes the Millennium Act Emergency Care Summary Report [FBUC \nMILL ACT SUMMARY].\n\n
\nRVU API AND RELATED MODIFICATIONS\n\n
\nIncorrect date used to validate the DRG and/or ICD effective date.\n\n
\nANNUAL UPDATE FOR RBRVS FEE SCHEDULE\n\n
\n \n \nThis patch is issued to compensate for the longer MRA message to be \nreceived from Austin Central Fee. Central fee will begin sending MRA \nmessages containing spaced for the NPI number before the NPI enhancement\npatch (FB*3.5*98) is released.\n\n
\n2006 RBRVS Conversion Factor update\n\n
\n \n \nNPI Modifications for the Fee Basis package\n\n
\nThe VistA Fee Basis application provides forms, letters and reports that \nare sent between VHA, vendors and veterans. This patch modifies VistA \nFee Basis by replacing the full SSN on those forms, letters and reports \nwith X's for the first 5 digits and only printing the last 4 digits in \nthe following format: \n XXX-XX-#### or XXXXX####\n \n **Note that X represents an actual X and # represents the actual SSN\n digit. Pseudo SSN will be changed as above with passed "P" at end.\n\n
\n2007 RBRVS ANNUAL UPDATE\n\n
\nValidate CNH 0168 Code Sheets to ensure that the required Data of Last\nAssessment field has been populated for applicable vendors.\n\n
\nCorrect Fee Basis RVU values for two CPT codes.\n\n
\n2008 RBRVS UPDATE\n\n
\nAdd the Referring Provider NPI Information to 10-7078 and 10-7079\nFee Authorization Forms.\n\n
\nFB*3.5*109 has the following changes:\n-Adds the Resource Based Relative Value Schedule (RBRVS) fee schedule\n for the calendar year 2009. \n-Adds Purpose of Visit 56, 67, 68, and 69. \n-Inactivates Purpose of Visit 20 effective January 01, 2009. \n\n
\nFB*3.5*110 does the following: \n- modifies the payments for Psychiatry CPT codes.\n- modifies Relative Value Units for CPT 67113. \n- adds additional information to the POV codes 56, 67, 68, and 69.\n\n
\nFirst patch of Fee Data & HERO enhancement:\n o Increase maximum size of disbursed amount in FEE BASIS INVOICE file.\n o Update S.FBAA PAID SERVER to process either old or new format of the\n payment confirmation message.\n\n
\nFB*3.5*111 does the following:\n- Corrects a problem with a warning message displaying inappropriately \n when using the Enter Authorization [FBAA ENTER AUTHORIZATION] option. \n- Corrects an erroneous message that a vendor is pending Austin \n Automation Center (AAC) approval when they aren't. \n- Corrects a problem where the FEE ID REPORT is missing patients.\n- Removes the SSN/Claim # from the NON-VA AUTHORIZATION FORM\n- Corrects a problem with the AMIS 349 report. \n- Corrects several locking problems. \n- Updates the Resource Based Relative Value Schedule (RBRVS) fee schedule \n with changes made in January, April and July 2009. \n- Updates the Department of Labor OWCP Modifier data to the 2009 values. \n- Corrects a problem when attempting to add multiple rates to a \n contract. \n- Corrects a problem when entering Current Procedural Terminology (CPT) \n code 0159T for payment. \n- Corrects the calculation for CPT code 0073T.\n\n
\nFB*3.5*112 does the following:\n -Updates the Resource Based Relative Value Schedule (RBRVS) fee schedule \n with changes for October 2009. \n -updates the Resource Based Relative Value Schedule (RBRVS) fee schedule\n with changes for Calendar Year (CY) 2010. \n\n
\nThis patch does the following:\n- corrects a problem with two Fee Basis routines that aren't updating \n data properly. \n- corrects the wrong data displaying when using the Enter Unauthorized \n Claim [FBUC UNAUTHORIZED] option. \n- corrects a warning that is not displayed when running low on available \n batches.\n\n
\nThis patch updates the following:\n- Place of Service Codes\n- Adjustment Reasons\n\n
\nSystem used by Medical Administration service to process and pay \ninvoices from private vendors for authorized procedures provided\nto veterans. Initial version will include the the processing of\nHometown Pharmacy, Patient Travel, and Outpatient Medical claims.\nVersion 2 includes Contract Hospital and Community Nursing Home.\nUnauthorized claims has been added in version 3. Also in this\nversion is an update to the vendor file for the conversion of\nCALM to FMS in Austin. The Community Nursing Home has been\nmodified to handle multiple rates.\n\n
\nPatch three for the Radiology/Nuclear Medicine 4.5 software. Please\nreview the Description and Installation Instructions for RA*4.5*3 before\ninstalling this patch.\n\n
\nPatch thirteen for the Radiology/Nuclear Medicine 4.5 software. Please\nreview the Description and Installation Instructions for RA*4.5*13 before\ninstalling this patch.\n\n
\nPatch five for the Radiology/Nuclear Medicine 4.5 software. Please review\nthe Description and Installation Instructions for RA*4.5*5 before\ninstalling this patch.\n\n
\nThis is the fourth patch for Radiology/Nuclear Medicine. Most of the\nchanges allow Radiology/Nuclear Medicine 4.5 to interface with the Patient\nCare Encounter (PCE) software. Please review the Description and\nInstallation Instructions for RA*4.5*4 before installing this patch.\n\n
\nPatch six for the Radiology/Nuclear Medicine 4.5 software. Please review\nthe Description and Installation Instructions for RA*4.5*6 before\ninstalling this patch.\n\n
\nPatch eight for the Radiology/Nuclear Medicine 4.5 software. Please\nreview the Description and Installation Instruction for RA*4.5*8 before\ninstalling this patch.\n\n
\nPatch nine for the Radiology/Nuclear Medicine 4.5 software. Please\nreview the Description and Installation Instruction for RA*4.5*9 before\ninstalling this patch.\n\n
\nPatch 10 for the Radiology/Nuclear Medicine 4.5 software. Please review\nthe Description and Installation Instruction for RA*4.5*10 before\ninstalling this patch.\n\n
\nPatch twelve for the Radiology/Nuclear Medicine 4.5 software. This patch\ncorrects <UNDEF>DOWN+1^RAHLRPC caused by patch ten (RA*4.5*10). Please\nreview the Description and Installation Instruction for RA*4.5*12 before\ninstalling this patch.\n\n
\nPatch eleven for the Radiology/Nuclear Medicine 4.5 software. Please\nreview the Description and Installation Instructions for RA*4.5*11 before\ninstalling this patch.\n\n
\n Radiology/Nuclear Medicine 4.5 to be exported from the Hines IRMFO.\nThis final version will be released to the field for installation.\n\n
\nPatch one for the Radiology/Nuclear Medicine 5.0 software. Please review\nthe Description and Installation Instructions for RA*5.0*1 before\ninstalling this patch.\n\n
\nService Patch Release\n\n
\nICD API CALLS \n\n
\n2013 UPDATES TO THE RADIOLOGY CPT BY PROCEDURE TYPE FILE (#73.2)\n\n
\nPatch one hundred fourteen for the VistA Radiology/Nuclear Medicine 5.0 \napplication. Please review FORUM's Patch Module description and \ninstallation instructions for RA*5.0*114 before installing this patch.\n\n
\nPatch one hundred and sixteen for the VistA Radiology/Nuclear Medicine \n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*116 before installing this patch.\n\n
\n \n2014 UPDATES TO THE RADIOLOGY CPT BY PROCEDURE TYPE FILE (#73.2)\n\n
\nPatch one hundred and thirteen for the VistA Radiology/Nuclear Medicine \n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*113 before installing this patch.\n\n
\nCORRECT ABNORMAL NOTATION IN CPRS REPORT LIST\n\n
\n2015 UPDATES TO THE RADIOLOGY CPT BY PROCEDURE TYPE FILE (#73.2)\nREQUESTED FILE UPDATES TO THE 78.3 DIAGNOSIS CODE FILE\n\n
\nRA*5*123 ADD PATIENT WEIGHT TO ORDER & EMAIL REPORT TO PRIMARY CARE\nPHYSICIAN\n\n
\nThis is the KIDS build for Radiology 5.0 patch 8.\n\n
\n2016 UPDATES TO THE RADIOLOGY CPT BY PROCEDURE TYPE FILE (#73.2)\n\n
\nPatch one hundred and twenty-five for the VistA Radiology/Nuclear \nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*125 before installing this patch.\n\n
\nPatch one hundred and twenty-nine for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*129 before installing this patch.\n\n
\nRadiology requests have functionality added to update hold reasons for \nrequests in a HOLD status. Please review FORUM's Patch Module description \nand installation instructions for RA*5.0*133 before installing this patch.\n\n
\nPatch RA*5.0*130 addresses the following Radiology/Nuclear Medicine \nissues:\n \n 1. The RAD/NUC MED ORDERS file (#75.1) AS and AP cross references do not \nmerge during a patient merge.\n\n
\nPatch RA*5.0*138 corrects defects introduced by patch RA*5.0*127.\n \nPlease see FORUM for full patch description and installation instructions.\n\n
\nPatch one hundred and nineteen for the VistA Radiology/Nuclear Medicine \n5.0 application. Please review FORUM's Patch Module description and \ninstallation instructions for RA*5.0*119 before installing this patch.\n\n
\n2017 Maintenance of Radiology File #73.2 (Radiology CPT by Procedure Type\n\n
\nThis patch will address the following SDM Tickets:\n1. I14066990FY17 - <UNDEFINED>PRT+13^RARTE5\n2. I14376092FY17 - New: SBY-Error Message: Report Designer HL7 Logs are \n not updating to Vista\n\n
\nFull TCP/IP support for HL7 messaging is available with patch HL*1.6*19.\nMedicine to communicate with COTS systems using HL7 v2.3 messages over\nTCP/IP. The original release of Rad/Nuc Med v5.0 supports HL7 v2.1\nmessages. Patch RA*5*12 also supports the VISTA HL7 v2.3 Interface to the\nPowerScribe for Radiology COTS voice recognition system. Any one of\nthe following events generate VISTA HL7 messages:\n1) Registration\n2) Cancellation\n3) Examined (i.e., images collected, usually set up in sites using the\nVISTA Imaging package and/or a PACS system)\n \nTwo links are required for message transactions. One link is used by\nThis patch also includes an exceptions file and a ListMan option to view\nor print the HL7 exceptions and take appropriate action to resolve the\nproblem.\n \nPlease consult the Radiology/Nuclear Medicine Technical Manual for further\ninformation concerning TCP/IP messaging.\nVISTA to send messages and receive acknowledgements to those messages.\nThe other link is used by a commercial off the shelf (COTS) voice\nrecognition unit to send messages and receive acknowledgments to those\nmessages. (The message sent and the acknowledgement to that message\ncomprise a full transaction.)\n \nPatch RA*5*12 includes protocols that now enable Radiology/Nuclear\n\n
\nThis patch addresses the following issues:\n \nHistoric radiolgy patient demographic updates to PACS.\n'Mass Override to Complete' option removal.\nStatus Tracking of Exams addition of pregnancy screen prompt.\nOutside Report Entry/Edit bypass of pregnancy screen requirement. \nStatus tracking display of printsets with SSANs enabled.\nRegistered Request Printer.\nImages Acquired indicator on radiology reports. \n\n
\nThis adds height and weight to Radiology exam registration demograhics.\n\n
\nPatch one hundred and thirty-five for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and \ninstallation instructions for RA*5.0*135 before installing this patch.\n\n
\nThis patch will resolve the following issues in the RADIOLOGY/NUCLEAR \nMEDICINE (RA) package:\n \n1) RA REPORTS SHOW INCORRECT COMMENTS\n\n
\n2018 MAINT OF RADIOLOGY FILE #73.2 (RADIOLOGY CPT BY PROCEDURE TYPE)\n\n
\nThis patch will address the following issue:\nRA18589477FY18 - Multiple errors in error trap. <UNDEFINED>EN1+63^RAO7RO\n\n
\nNTP release report (VAQ) message sent to PACS.\n \nRegistered request printer pulled from exam's imaging location (previously\npulled from the order's imaging location).\n \nRemove RAPX var check from printer logic.\n \nRemove conditions for duplicate procedure to print exam information on \nthe registered request\n \nStrip site prefix from accession number received in ORU if SSAN is \n \ndisabled.\nRemove old HLO query code for previous NTP vendor. \n \n'Add Exam to Last Visit' erroneous report\n \nReject HL7 report (ORU) with inactive DX codes passed.\n \nRemove redundant GENERATE^HLMA call.\n\n
\nThe purpose of this patch is to address the issue of the Weight Date not \nproperly displaying. Currently, it is using he same information as the \nHeight Date.\n\n
\nRadiopharmaceutical Usage Report is not displaying correct \nLong-Case@Time values after turning on Site Specific Accession Numbers\n\n
\nPatch one hundred and twenty-four for the VistA Radiology/Nuclear \nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*124 before installing this patch.\n\n
\nRA PROC OPTION SEMI-COLON ISSUE AND OUTSIDE RPT ENT OBSERVATION DT/TM\n\n
\nThis patch allows the user to select an imaging order that has been \nsigned, create a consult order from that imaging order, automatically sign\nthe consult order which creates a consult, and the consult is submitted to\ncommunity care. Seven consult new services are created for use in this \nprocess.\n\n
\nPatch one hundred and fifty-three for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*153 before installing this patch.\n\n
\nRegistration fine tuning\nUndefined error\n\n
\nPatch one hundred and fifty-six for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*156 before installing this patch.\n\n
\n2019 MAINT OF RADIOLOGY FILE #73.2 (RADIOLOGY CPT BY PROCEDURE TYPE)\n\n
\nPatch one hundred and fifty-eight for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*158 before installing this patch.\n\n
\nAbnormal report formatting and subscript error on #67 alerts.\nPrimary Designation DX Codes\nSwitch Location key/update\n\n
\nPatch one hundred and sixty-three for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*163 before installing this patch.\n\n
\nPatch one hundred and sixty-two for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*162 before installing this patch.\n\n
\nRad/Nuc Med - CPRS API\n\n
\nPatch one hundred and sixty-one for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*161 before installing this patch.\n\n
\nPatch one hundred and sixty-seven for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*167 before installing this patch.\n\n
\nPatch one hundred and sixty-eight for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description.\n\n
\nPatch one hundred and sixty-six for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*166 before installing this patch.\n\n
\nPatch one hundred and seventy-one for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*171 before installing this patch.\n\n
\nPatch one hundred and sixty-five for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*165 before installing this patch.\n\n
\nPatch one hundred and seventy-two for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*172 before installing this patch.\n\n
\nPatch one hundred and sixty-nine for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*169 before installing this patch.\n\n
\nPatch one hundred and sixty for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*160 before installing this patch.\n\n
\nPatch one hundred and seventy-three for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*173 before installing this patch.\n\n
\nPatch 10 for the Radiology/Nuclear Medicine 5.0 software.\n \nPlease review the Description and Installation Instructions for\nRA*5.0*10 before installing this patch.\n\n
\nPatch one hundred and seventy-four for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*174 before installing this patch.\n\n
\nPatch one hundred and seventy for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*170 before installing.\n\n
\nPatch one hundred and seventy-eight for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*178 before installing this patch.\n\n
\nBackup of RA*5.0*175 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch one hundred and seventy-five for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*175 before installing this patch.\n\n
\nBackup of RA*5.0*177 on Apr 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of RA*5.0*179 on Jun 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch one hundred and seventy-nine for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*179 before installing this patch.\n\n
\nBackup of RA*5.0*181 on Jul 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch one hundred and eighty-one for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*181 before installing this patch.\n\n
\nBackup of RA*5.0*182 on Aug 24, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch one hundred and eighty-two for the VistA Radiology/Nuclear Medicine \n5.0 application. Please review FORUM's Patch Module description and \ninstallation instructions for RA*5.0*182 before installing this patch.\n\n
\nPatch one hundred and eighty-three for the VistA Radiology/Nuclear \n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*183 before installing this patch.\n\n
\nPatch one hundred and eighty-four for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*184 before installing this patch.\n\n
\nPatch one hundred and eighty-six for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*186 before installing this patch.\n\n
\nPatch one hundred and eighty-five for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*185 before installing this patch.\n\n
\nPatch one hundred and eighty-seven for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*187 before installing this patch.\n\n
\nPatch one hundred and ninety-one for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*191 before installing this patch.\n\n
\nPatch one hundred and eighty-nine for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*189 before installing this patch.\n\n
\nPatch 19 for the Radiology/Nuclear Medicine 5.0 software.\n \nPlease review the Description and Installation Instructions for\nRA*5.0*19 before installing this patch.\n\n
\nPatch one hundred and eighty-eight for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*188 before installing this patch.\n\n
\nPatch one hundred and ninety for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*190 before installing this patch.\n\n
\nPatch one hundred and ninety-two for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*192 before installing this patch.\n\n
\nPatch one hundred and ninety-three for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*193 before installing this patch.\n\n
\nPatch one hundred and ninety-four for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*194 before installing this patch.\n\n
\nPatch one hundred and ninety-six for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*196 before installing this patch.\n\n
\nPatch one hundred and ninety-five for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*195 before installing this patch.\n\n
\nPatch one hundred and ninety-seven for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*197 before installing this patch.\n\n
\nPatch two hundred and one for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*201 before installing this patch.\n\n
\nPatch two hundred for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*200 before installing this patch.\n\n
\nPatch twenty for the Radiology/Nuclear Medicine 5.0 software. Please\nreview the Description and Installation Instructions for RA*5.0*20 before\ninstalling this patch.\n\n
\nPatch one hundred and ninety-eight for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*198 before installing this patch.\n\n
\nPatch two hundred and two for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*202 before installing this patch.\n\n
\nPatch two hundred and three for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*203 before installing this patch.\n\n
\nPatch two hundred and five for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*205 before installing this patch.\n\n
\nPatch two hundred and four for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*204 before installing this patch.\n\n
\nPatch two hundred and seven for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*207 before installing this patch.\n\n
\nPatch two hundred and six for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*206 before installing this patch.\n\n
\nPatch two hundred and nine for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*209 before installing this patch.\n\n
\nPatch two hundred and ten for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*210 before installing this patch.\n\n
\nPatch two hundred and eleven for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*211 before installing.\n\n
\n \nRad/Nuc Med HL7 Voice Reporting Patch\n\n
\nPatch two hundred and eight for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*208 before installing this patch.\n\n
\nPatch two hundred and twelve for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*212 before installing this patch.\n\n
\nPatch two hundred and thirteen for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*213 before installing this patch.\n\n
\nPatch two hundred and fifteen for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*215 before installing this patch.\n\n
\nPatch two hundred and sixteen for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*216 before installing this patch.\n\n
\nPatch two hundred and fourteen for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*214 before installing this patch.\n\n
\nPatch two hundred and nineteen for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*219 before installing this patch.\n\n
\nPatch two hundred and eighteen for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*218 before installing this patch.\n\n
\nPatch two hundred and twenty-one for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*221 before installing this patch.\n\n
\nPatch two hundred and seventeen for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*217 before installing this patch.\n\n
\nPatch two for the Radiology/Nuclear Medicine 5.0 software. Please review\nthe Description and Installation Instructions for RA*5.0*2 before\ninstalling this patch.\n\n
\nPatch two hundred and twenty for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*220 before installing this patch.\n\n
\nPatch two hundred and twenty-two for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*222 before installing this patch.\n\n
\nPatch two hundred and twenty-four for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*224 before installing this patch.\n\n
\nPatch two hundred and twenty-three for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*223 before installing this patch.\n\n
\nPatch two hundred and twenty-five for the VistA Radiology/Nuclear Medicine\n5.0 application. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*225 before installing this patch.\n\n
\nPatch two hundred and twenty-seven for the VistA Radiology/Nuclear\nMedicine 5.0 application. Please review FORUM's Patch Module description\nand installation instructions for RA*5.0*227 before installing this patch.\n\n
\nThis is a patch for a patch. CLIN^RAO7PC2 needs to be changed after\nproblems found when a case number of 0 exists.\n\n
\nPatch 21 for the Radiology/Nuclear Medicine 5.0 software.\n \nPlease review the Description and Installation Instructions for\nRA*5.0*21 before installing this patch.\n\n
\nPatch 18 for the Radiology/Nuclear Medicine 5.0 software\n\n
\nPatch 23 for the Radiology/Nuclear Medicine 5.0 software.\n \nPlease review the Description and Installation Instructions for\nRA*5.0*23 before installing this patch.\n\n
\nPlease see patch description for this patch.\n\n
\nPlease see patch description for details.\n\n
\nPlease see patch description for this patch.\n\n
\nRadiology Enhancements\n\n
\nPatch six for the Radiology/Nuclear Medicine 5.0 software. Please review\nthe Description and Installation Instructions for RA*5.0*6 before\ninstalling this patch.\n\n
\nRADIOLOGY/NUCLEAR MEDICINE V5.0 PATCH # 25\n \nRADIOLOGY HL7 INTERFACES ENHANCEMENTS.\n\n
\nPlease see patch description for this patch.\n\n
\nSee patch description for this patch.\n\n
\nPlease refer to the patch description in FORUM regarding the installation \nof RA*5.0*40.\n\n
\nPlease see patch description for this patch.\n\n
\nPlease see patch description of this patch for details.\n\n
\nPlease see patch description for this patch.\n\n
\nPlease see patch description of this patch for details.\n\n
\nPlese refer the patch description on FORUM for a detailed account of the \nchanges exported with this patch.\n\n
\n Please see the National Patch Module for details of the \n enhancements included in this patch.\n\n
\nThe fourth patch intended for the Radiology/Nuclear Medicine 5.0 software.\nPlease review the Description and Installation Instructions for RA*5.0*4\nbefore installing this patch.\n\n
\nPlease see patch description for details.\n\n
\nSee patch description for this patch for details.\n\n
\nNOTE: This patch addresses a Patient Safety Issue\n \nThis patch addresses the problem where an edit to an entry in the RAD/NUC\nMED PROCEDURE MESSAGE file (# 71.4) with the menu Procedure Message\nEntry/Edit [RA PROCMSGEDIT] does not update the content of the\nrelated entries of the ORDERABLE ITEMS file (# 101.43).\n\n
\nPlease see Patch Description for details.\n\n
\nThis patch will be sent in a multi-build patch from PX*1.5*12.\n\n
\nFix to add Addendums via VR Sysytems.\n\n
\nThis patch address two problems:\n1) A RAD/NUC MED PROCEDURE MESSAGE file (#71.4) entry may be edited \nby more than one user at a time with the option Procedure Message \nEntry/Edit [RA PROCMSGEDIT].\n2) The menu option Resend Radiology HL7 Message [RA HL7 MESSAGE \nRESEND] communication is missing the 'exam registered' HL7 messages in \nsubsequent cases after the first case.\n\n
\nPlease refer to the patch description on FORUM for additional information \nregarding patch RA*5.0*45.\n\n
\nThis patch corrects an HL7 message generation error caused by patch \nRA*5.0*54.\n\n
\nPatch seven for the Radiology/Nuclear Medicine 5.0 software. Please\nreview the Description and Installation Instructions for RA*5.0*7 before\ninstalling this patch.\n\n
\nPERFORMANCE MEASURE CALC CORRECTION\n\n
\nBilling Awareness - Radiology\n\n
\nPlease see NPM patch for a description of this patch.\n\n
\nUNDEFINED ERROR FROM THE RADIOPHARM USAGE/RA PROC EDIT BUSINESS RULE \nCHANGE\n\n
\nALLOW RADIOLOGY TO ACCEPT DIAGNOSIS CODE CHANGES FROM TALK TECHNOLOGY\n\n
\nPlease see patch description on FORUM\n\n
\nRADIOLOGY REJECTS ORDER FROM CPRS/CPT CODE DISPLAY ISSUE ON PROC-CPT \nREPORT\n\n
\nCORRECT UNKNOWN USER ON ACT LOG/REMOVE EXTRA DASH LINES\n\n
\nOutpatient Procedure Wait Time Report. \n \nThe .01 field of subfile 79.0175 is included in this KIDS build so to \ncorrect a spelling error in the help prompt.\n \nPlease see Forum's patch description for details.\n\n
\nPlease refer to the patch description in FORUM regarding the installation\nof RA*5.0*64.\n\n
\nPlease refer to patch description for this patch.\n\n
\nCORRECT UNDEF ERROR DURING RAD PATIENT REG\n\n
\nPlease see Patch Description for details to the "Scheduling Replacement - \nRadiology" patch.\n\n
\nPlease refer to the patch description in FORUM regarding the installation\nof RA*5.0*76.\n\n
\nADD ABILITY TO UPDATE EXAM DATA TO V/R AND CORRECT PROC CODE ENTRY\n\n
\nPATIENT AGE REPORTING ISSUE FOR VISTARAD\n\n
\nRA*5.0*79 OUTPATIENT PROCEDURE WAIT TIME BY PROCEDURE TYPE\n \nThis patch exports a new file, #73.2, RADIOLOGY CPT BY PROCEDURE TYPE, \nwith data. This file is a standalone file, it isn't pointed to by any \nfile, and it doesn't point to any file.\n \nThis patch also exports revised routines RAPMW*.\n \nPlease see the NPM patch description for further details of this patch.\n\n
\nPatch eighty-two for the Radiology/Nuclear Medicine 5.0 software. Please\nreview the Description and Installation Instructions for RA*5.0*82 before\ninstalling this patch.\n\n
\nSUBSCRIPT ERROR, RVU REPORTING ISSUE, SCROLLING ISSUE\n\n
\nPatch seventy-five for the Radiology/Nuclear Medicine 5.0 software. \nPlease review the Description and Installation Instructions for RA*5.0*75\nbefore installing this patch.\n\n
\nPlease refer to the patch description in FORUM regarding the installation\nof RA*5.0*81.\n\n
\nPlease refer to the Forum NPM patch description for details to this patch.\n\n
\nThis patch adds a menu option to the Radiology HL7 menu that resends HL7 \nmessages by date range.\n\n
\nEXAM BACKDATING AND CANCELLING EXAMS WITH IMAGES\n\n
\nPROC MOD OPTION ISSUE, UNDEF DURING V/R UPLOAD AND INCOMPLETE\nREPORT LAST 4 SSN\n\n
\nPatch eighty-six for the Radiology/Nuclear Medicine 5.0 software. Please\nreview the Description and Installation Instructions for RA*5.0*86 before\ninstalling this patch.\n\n
\nPatch eighty-four for the Radiology/Nuclear Medicine 5.0 software. \nPlease review the Description and Installation Instructions for RA*5.0*84\nbefore installing this patch.\n\n
\nPatch ninety-two for the Radiology/Nuclear Medicine 5.0 software. \n \nPlease review the Description and Installation Instructions for RA*5.0*92\nbefore installing this patch.\n\n
\nPlease see the description in FORUM's national patch module for this \npatch.\n\n
\nRadiology Incorporates Pharmacy APIs. Please see the patch description \nof this patch on FORUM for details.\n\n
\nRVU Reports showing some incorrect RVU values\n\n
\nPatch 5 for the Radiology/Nuclear Medicine 5.0 software.\n \nPlease review the Description and Installation Instructions for RA*5.0*5\nbefore installing this patch.\n\n
\nRADIOLOGY ORDER FILE CLEANUP\n\n
\n The installation of the Project 112/Shipboard Hazard and Defense (SHAD) \n modifications made for this project. New prompts will be displayed and \n screen/report formatting will occur. The new PRIMARY DX RELATED TO \n SHAD field (#100) of the RAD/NUC MED ORDERS file (#75.1) will appear\n on Radiology Reports. No additional processing time should be noticed as\n a result of these modifications. The Southwest Asia Condition label will \n appear on reports and screen prompts in place of the Environmental \n Contaminants label.\n clinical application enhancements will provide sites of the ability to \n collect and store SHAD exposure information related to provided medical \n care, and to share that information with PCE. Further modifications will \n include a change of the Environmental Contaminants (EC) label to be \n Southwest Asia Condition (SWAC). All internal values for "EC" will remain\n and only external values will be modified to SWAC.\n \n Some changes will be noticeable to the user community due to the \n\n
\nPatch seventy-eight for the Radiology/Nuclear Medicine 5.0 software.\nPlease review the Description and Installation Instructions for RA*5.0*78\nbefore installing this patch.\n\n
\nMAINTENANCE OF FILE 73.2 CPT BY PROCEDURE TYPE\n\n
\nPlease see the patch description in FORUM for details regarding this KIDS \nbuild.\n\n
\nINCOMPLETE EXM REP PRT ISSUE, ALERT TEXT CHG, DIK CALL CHG\n\n
\nPlease refer to the Patch Description on FORUM for this build. \n\n
\nPatch ninety-four for the Radiology/Nuclear Medicine 5.0 software. Please\nreview the Description and Installation Instructions for RA*5.0*94 before\ninstalling this patch.\n\n
\nPatch ninety-nine for the Radiology/Nuclear Medicine 5.0 software. \nPlease review the Description and Installation Instructions for RA*5.0*99\nbefore installing this patch.\n\n
\nREPORT INPUT TEMPLATE CORRECTION\n\n
\nCORRECT ASTF/ARES X-REF ISSUE\n\n
\n2010 UPDATE OF FILE 73.2 RADIOLOGY CPT BY PROCEDURE CODE\n\n
\nThis build contains a Radiology Order and Exam API for the DICOM Importer\napplication (patch MAG*3*53) and some internal Radiology APIs.\n\n
\nPatch one hundred-one for the Radiology/Nuclear Medicine 5.0 software. \nPlease review the Description and Installation Instructions for RA*5.0*101\nbefore installing this patch.\n\n
\nPatch one hundred and six for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*106 before installing this patch.\n\n
\nCPT DISPLAY ISSUE, OUTSIDE REPORT ALERT ISSUE, OUTSIDE REPORT STATUS ISSUE\n\n
\n2011 UPDATES TO THE RADIOLOGY CPT BY PROCEDURE TYPE FILE (#73.2)\n\n
\nPlease refer to the patch description in FORUM regarding the installation\nof RA*5.0*47.\n\n
\nPatch one hundred and seven for the VistA Radiology/Nuclear Medicine 5.0\napplication. Please review FORUM's Patch Module description and\ninstallation instructions for RA*5.0*107 before installing this patch.\n\n
\n2012 file update of 73.2 CPT BY PROCEDURE TYPE\n\n
\nRadiology/Nuclear Medicine v5.0 from our gold account to the field. This\nis the final release of the package.\n\n
\n \n \n\n
\nThis patch removes an inactive option in the Utilization Management Rollup\npackage and addresses the problem of sites not receiving data in their IBQ\nSite File after running the National Rollup report.\n\n
\nThis package is used at the local facility for rollup of Utilization \nManagement Rollup data to the National Database.\n\n
\nThe purpose of DHCP Interim Management Support is to provide\naccessible, reliable, and useful information to management within\nthe VAMC. Information pertains to the center, its workload, and its\nresources. The primary source of data for the module is the hospital's\nDHCP applications/packages and associated files.\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*5 in the National Patch Module.\n\n
\nSee the National Patch Module on Forum for a complete description of this patch.\n\n\n
\nPlease refer to the National Patch Module for details of the changes\ncontained in this build.\n\n
\nThis patch takes out the check for field #5 CHECK/DON'T CHECK, in file #38.6\nINCONSISTENT DATA ELEMENTS when sending data in a Z07.\nThis patch also changes the call from $$DT^XLFDT\nto $$NOW^XLFDT in routine IVMZ7CR to pass the inconsistency check for Z07. \n\n
\nThis patch removes code in IVMZ07C that makes reference to field (#5)\nCHECK/DON'T CHECK in the INCONSITENCY DATA file (38.6)\nin preventing the transmission of a Z07.\n\n
\nSee the Patch Description for IVM*2*115 as generated out of the Forum \nPatch Module.\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*16 in the National Patch Module.\n\n
\nThis patch corrects the bulletin sent as a result of an HL7 message 'AE'\nerror being received in VistA. Please refer to the National Patch Module\n(NPM) for a full description of the contents of this patch.\n\n
\nThis patch is being implemented in support of the Insurance Capture Buffer\nAPI as follows:\n UPDATE(DFN,IVMINSST,IVMID,IVMREPTR,IVMSUPPR)\n \nThe IVMREPTR variable is an input variable to pass the IVM REASONS FOR NOT\nUPLOADING (#301.91) Internal Entry Number into this application. This\nvariable will be optional. When an Insurance Segment is rejected based on\nthe ICB application rejecting an IVM Insurance entry from the IVM\napplication, the pointer value for the reason it isn't uploaded will be\npass and store in the REASON NOT UPLOADING INSURANCE (#.08) field of the\nIVM PATIENT (#301.5) file.\n(ICB) application which will provide a GUI front end to the Integrated\n \nThe IVMSUPPR variable is an input variable which when passed will suppress\nwhat is written to the screen and the interactive read of the IVM REASON\nFOR NOT UPLOADING (#301.91) file within the UPDATE API.\nBilling (IB) insurance update/editing functionality. The ICB application\nrequires that there be no write statements or interactive reads when using\nthe existing IB ACCEPT/REJECT Insurance Buffer logic. Currently, there is\nICR 2530 is the supported interface between IB and IVM. The\nUPDATE^IVMLINS4 API needs to be updated to comply with ICBs requirements.\n \nThis patch will add two additional input parameters to the UPDATE^IVMLINS4\n\n
\nThis patch fixes a hard error when uploading a means test from a\nZ10 message. Please refer to the National Patch Module for a full\ndescription of the contents of this patch.\n\n
\nThis patch prevents test patients from sending Z07 transmissions.\n\n
\nFix problem w/ IVM BACKGROUND JOB not sending RX Copay Exemption tests.\n\n
\n <ftp://ftp.fo-slc.domain.ext>\n \n \nBelow is a list of the files related to this patch that will be needed\nand available via the FTP sites listed above.\n \nFile Description File Name FTP Mode\n--------------------------------------------------------------------------\nRevised IVM V2.0 User Manual IVM_2_P148_UM.PDF Binary\n \n \n \nAssociated Test Sites:\n----------------------\nPuget Sound Health Care Center\nVA Heartland West\nVA Maryland Health Care System\n \n \nINSTALLATION INSTRUCTIONS:\n==========================\nThis patch may be installed during normal working hours; however,\n \nthis patch should NOT be installed while the IVM BACKGROUND JOB [IVM\nBACKGROUND JOB] is running. VISTA users will not be affected.\n \nInstall Time - less than 5 minutes\n \n1. LOAD TRANSPORT GLOBAL\n ---------------------\n Choose the PackMan message containing this patch and invoke the\n INSTALL/CHECK MESSAGE PackMan option.\n \n \n2. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu\n [XPD MAIN]:\n \n Edits and Distribution ...\n Utilities ...\n Installation ...\n \nSelect Kernel Installation & Distribution System Option: INStallation\nThe documentation will be in the form of Adobe Acrobat files.\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\n \n \nSelect Installation Option:\n \n3. Select Installation Option:\n ---------------------------\n NOTE: The following are OPTIONAL - (When prompted for the INSTALL\n NAME, enter IVM*2.0*148):\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n \n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. Select Installation Option: Install Package(s)\n ------------------\nDocumentation can also be found on the System Design and Development Web\n **This is the step to start the installation of this KIDS patch:\n \n a. Choose the Install Package(s) option to start the patch\n install. When prompted for INSTALL NAME, enter IVM*2.0*148.\n b. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES//' answer NO\n c. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? NO//' answer NO\npage at: http://www.domain.ext/vdl/\n\n
\nThis patch adds the HL7 ZFE segment (Fee Basis) to the ORF~Z11 and ORU~Z11\nmessages. Please see the National Patch Module for a description.\n\n
\nThis patch contains VistA changes to support technology and business\nchanges that are occurring with the implementation of Public Law 111-163.\n\n
\nMILITARY SERVICE DATA SHARING (MSDS) PROJECT\n\n
\nPermanent Address Verification\n\n
\nThis patch contains VistA changes to support technology and\nbusiness changes that are occurring with the implementation of\nDiscontinue Annual Means Test Renewal.\n\n
\nThis patch corrects a problem where an ORU-Z05 message uploaded from ESR \nthat were inadvertently left behind. This will NOT cause problems in \nproduction accounts, as there is a check in place to verify that the \naccount is not a test account.\nto VistA is not processed in the IVM Demographic Upload screen because an\n'Invalid Date of Death' error is generated. This problem occurs when a \nDate of Death message containing a time value, which is sent in the \nORU-Z05, is uploaded on the SAME DAY that the death occurred. \n \nThis patch also removes an API call to a non-existent routine, DGPFSS2. \nThis call was inserted for the PFSS Project, but the project was later \ncancelled and the routine was removed after the cleanup of old routines \n\n
\nThis patch will make changes to the IVM routines that will check and verify\nthe HL7 is active before creating and transmitting the HL7 data. Patch\nEAS*1*96 will disable the HL7 protocols to prevent data from being sent to the\nHEC system. Prior to the installation of this patch, the IVM routines did\nnot check for the protocols to see if they are disabled. Once this patch is\ninstalled, the routines will make the check and stop the transmission of data\nif the protocol is disabled.\n\n
\nThis patch modifies the Income Verification Match v2.0 application as \n(#2) file equals "Y" and new CD STATUS DESCRIPTORS are on File, CD \nDESCRIPTORS in lieu of CD STATUS DIAGNOSES, CD STATUS PROCEDURES and CD \nSTATUS CONDITIONS will be sent on the HL7 Z07 message.\n \n3. If the VETERAN CATASTROPHICALLY DISABLED? (#.39) field of the PATIENT \n(#2) file equals "N", it will not send anything.\ndescribed below:\n \n1. If the VETERAN CATASTROPHICALLY DISABLED? (#.39) field of the \nPATIENT (#2) file equals "Y" and no CD DESCRIPTORS are on file, CD \nSTATUS DIAGNOSES, CD STATUS PROCEDURES and CD STATUS CONDITIONS will be \nsent on the HL7 Z07 message.\n \n2. If the VETERAN CATASTROPHICALLY DISABLED? (#.39) field of the PATIENT \n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*14 in the National Patch Module.\n\n
\nPatch IVM*2*159 addresses one issue:\n \n 1. MPI/IVM process is not dinuming patients ethnicities and \n mulitple races correctly.\n\n
\n The Health Eligibility Center (HEC) requested modifications to the \n ----------------------------------------------------------\n This patch supports HL7 enhancements that sends Contributed To \n Spouse and Contributed to Child Z10 ZIR-15 and stores them in the \n database. Patch DG*5.3*890 will be released in conjunction with\n this EAS patch.\n \n This patch also adds the Beneficiary Travel Financial Indicator (BTFI) \n to the Z07 ZMT-31 to send the BTFI back to the Enrollment System.\n Enrollment System Redesign (ESR) and VistA Registration, Enrollment \n and Eligibility (Vista REE) software to support the requirements of \n the Veterans Financial Assessment (VFA) projects.\n \n This patch modifies the Enrollment Application System V2.0 application\n as described below:\n \n HL7 Changes\n\n
\nRelated to DG*5.3*909\nIVM*2.0*161 will update the Registration application to allow for the\nentering and maintenance of the Camp Lejeune Eligibility related data.\n\n
\nPatch DG*5.3*797 added the new MILITARY SERVICE EPISODE sub-file #2.3216 \nthe MSE data in the old location is being checked instead of the MSEs in \nthe new location. This is causing invalid inconsistency errors to be \nfiled in the INCONSISTENT DATA file (#38.5), and preventing the \ntransmission of the Z07 messages for those patients. \n \nThe wrong MSE data is being checked for the following inconsistencies:\n \n 83 MERCH SEA OR FILIPINO VET BOS REQUIRES SERVICE DATES DURING WWII\n 85 VERIFIED FILIPINO VETERAN SHOULD HAVE A VETERAN STATUS OF 'YES'\n 86 INELIGIBLE FILIPINO VETERAN SHOULD HAVE A VETERAN STATUS OF 'NO'\nin the PATIENT (#2) file to store Military Service Episode (MSE) data.\nChanges in that patch included modifications to several consistency \nchecks that used MSE data. The checks for data inconsistencies should \nonly be checking the MSEs in the new MILITARY SERVICE EPISODE sub-file \n(#2.3216) in PATIENT (#2)file. \n \nHowever, during the check for inconsistencies that would prevent the \ntransmission of a Z07 HL7 message to the Health Eligibility Center (HEC), \n\n
\nThis patch will resolve the following issue:\n \n1. The Z05 Enrollment/Eligibility upload transmission is incorrectly \n quitting if the Patient does not have an entry in the IVM PATIENT\n (#301.5) file.\n\n
\nThis patch will allow for processing of an imprecise retirement date being\npassed back to the Enrollment System (ES) now that the ES is capable of\naccepting this value. It will also improve formatting for the \npatients cell phone and pager numbers stored when processing a Z05.\n\n
\nENROLLMENT SYSTEM COMMUNITY CARE (ESCC) HOME PHONE AND FUTURE DISCHARGE \nDATE UPDATES\n\n
\nPlease see the IVM*2.0*171 patch description for detailed information\nregarding this patch.\n\n
\nPlease see the IVM*2.0*164 patch description for detailed information\nregarding this patch. \n\n
\nPlease refer to the Patch Description in FORUM for patch IVM*2.0*174\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nPlease see the IVM*2.0*172 patch description for detailed information \nregarding this patch.\n\n
\nPlease refer to the Patch Description in FORUM for patch IVM*2.0*177\n\n
\nThe business owners have requested 'VET360' be added as a selection to \nthe ADDRESS CHANGE SOURCE (#3) Field in the IVM ADDRESS CHANGE LOG\n(#301.7) File. This field should match the values available in ADDRESS\nCHANGE SOURCE (#.119) Field in the PATIENT (#2) File. Otherwise there may\nbe issues utilizing FileMan utilities in the future.\n\n
\nPlease see the IVM*2.0*180 patch description for detailed information \nregarding this patch.\n\n
\nPatch IVM*2.0*179 fixes an issue where the DHCP OUTPUT LOGIC (#20) field\nof the IVM DEMOGRAPHIC UPLOAD FIELDS (#301.92) file does not show a string\nfor 3 entries (70-72),Temporary Address Zip, Temporary Address Country, \nTemporary Address County and has an incorrect string for 2 entries\n(73 & 74),Temporary Address Province and Temporary Address Postal Code.\nIt also modifies the TRANSFORM DHCP DATA (.07) field to equal 1 for\nrecords 71 and 72.\n\n
\nPlease see the IVM*2.0*183 patch description for detailed information \nregarding this patch.\n\n
\nThis patch will address a request to sync the SOURCE OF INCOME TEST\n(#408.34) file with the Standard Data Service (SDS) database. Two new\nentries will be added to the SOURCE OF INCOME TEST (#408.34) file.\n\n
\nPlease see the IVM*2.0*188 patch description for detailed information\nregarding this patch.\n\n
\nThe patch is delivered in a bundle with DG*5.3*952 to support \n \nThis patch also supports the new a sub-eligibility, which is implemented \nby DG*5.3*952 as a new "EXPANDED MH CARE TYPE" field in VistA PATIENT \nfile (#2), for EMERGENT MH OTH type that supports providing mental health \ncare in one or more 90-day\nperiods (additional periods require authorization) for eligible patients.\n \nHL7 messaging has been updated in this patch to ensure VistA Registration \nchanges are communicated to the Enrollment System (ES). OTH patient data\nwill be shared with ES and if a patient record is updated in ES, it will \nimplementation of EXPANDED MH CARE NON-VETERANS as a primary eligibility \ncontinue to be updated in VistA.\ncode (and a Medical Administration Service (MAS) eligibility code) in \nVistA Registration to identify and support Other Than Honorably (OTH) \ndischarged patients who need mental healthcare services, in order to help \nreduce the number of Veteran suicides. These patients are awaiting \nadjudication and are entitled to receiving mental health treatment during \nthat timeframe from the VA either for 90-day episodes of care for service \nrelated emergent mental health issues. \n\n
\nPlease see the IVM*2*190 patch description for detailed information \nregarding this patch.\n\n
\nSee the National Patch Module for a complete description of this patch.\n\n
\nPlease see the IVM*2*192 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2*193 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*162 patch description for detailed information \nregarding this patch\n\n
\nThis patch corrects the following issue:\n \nAn Undefined error occurs in tag SRCOFMT of routine IVMCM3\nwhen the SOURCE OF INCOME TEST (#.23) field in the ANNUAL\nMEANS TEST (#408.31) file is equal to 5 (HEC-Old) or 6 (VOA).\n\n
\nPlease see the IVM*2*194 patch description for detailed information \nregarding this patch.\n\n
\nBackup of IVM*2.0*187 on Apr 27, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch IVM*2.0*187 addresses 2 issues:\n \n 2.Site receives an <UNDEFINED>SET+16^DGMTAUD error when\n processing an incoming HL7 Z10 (Income Test Transmission)\n message.\n \n 1.Multiple sites reported an issue when trying to update a\n patients address in Vista. When the code is processing the PID\n segment, which contains the address information of an HL7 Z05\n message, it sets variable FORADDR equal to 1 if the residential\n address is a foreign address. When evaluating the permanent\n county address, FORADDR still equals 1 because it never gets\n reset.\n\n
\nPlease see the IVM*2.0*196 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*201 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*204 patch description for detailed information \nregarding this patch.\n\n
\nSee National Patch Module for description of changes included in this patch.\n\n
\nPlease see the IVM*2.0*203 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*208 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*210 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*211 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*212 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*214 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*215 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the IVM*2.0*216 patch description for detailed information \nregarding this patch.\n\n
\nSee the National Patch Module for a complete description of patch\nIVM*2*22.\n\n
\nSee National Patch Module for details.\n\n
\nSee Patch IVM*2.0*31 in Forum for description of this Build.\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*6 in the National Patch Module.\n\n
\nSee National Patch Module for details.\n\n
\nSee Patch IVM*2*26 in the National Patch Module for a description of this\nbuild.\n\n
\nPlease see patch IVM*2*28 in FORUM for description of this Build.\n\n
\nPlease see the patch description for patch number IVM*2*30 in the National\nPatch Module.\n\n
\nThis patch addresses a number of issues, in association with patch\nDG*5.3*285, that are described in the following NOIS tickets:\n \n WCO-1199-51890 HOW TO DEACTIVATE MEANS TEST MSGS \n BHS-0100-11797 MEANS TEST REQUIRED DATE QUESTION\n CMO-1199-40912 MULTIPLE PRINTING OF RX COPAY EXEMPTION LETTER\n\n
\nPurple Heart\n\n
\nSee patch IVM*2.0*39 in the National Patch Module for description of this\nbuild.\n\n
\nPlease see National Patch Module in FORUM for description of this Patch.\n\n
\nSee national patch module for description.\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*7 in the National Patch Module.\n\n
\nSee national patch module for description.\n\n
\nMaster Patient Index integration into HEC.\n\n
\nKIDS build for IVM*2.0*48\n\n
\nMST DATA SHARING\n\n
\nSee national patch module for description.\n\n
\nThis patch (IVM*2.0*50) will implement the business rules for creating,\ndeleting, and sharing of Hardship information.\n\n
\nPlease see Patch IVM*2.0*53 in the National Patch Module for description \nof this Build.\n\n
\nUpgrade from VistA HL7 v1.5 to VistA HL7 v1.6\nIVM routines for VAMC site.\n\n
\nSee FORUM patch module for full description.\n\n
\nZ06 Transmission problem:\nORF+^IVMPRECZ Undefined variable UPMTS\n\n
\nWithin several HL7 messaging programs there is a call to invoke the \nprocess to send an acknowledgment back to the HEC that is using the \nwrong variable. Also several programs do not clean up the temporary \nglobal -^TMP prior to and/or after the creation of a query.\n \nPatch DG*5.3*472 is a required build for IVM*2.0*63 and needs to be \ninstalled first.\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nADDITIONAL ENHANCEMENTS REQUIRED TO HANDLE SENDING AND RECEIVING OF OTHER\nHL7 MESSAGES BASED UPON RECEIPT OF A Z06 MESSAGE.\n\n
\nIVM*2.0*73 Kids Build\n\n
\nTHIS IS AN EMERGENCY FIX TO PATCH IVM*2*77\n \nTHE IP ADDRESS FOR THE Z09 SERVER PRTOTCOL WILL BE CHANGED\n \nTHE SENDING OF Z09 TO THE APPROPRIATE HEC (LEGACY VS. EDB) WILL BE\nCORRECTED.\n\n
\nThe problem is that when the Means Test Signature (Z06) is transmitted to \n ID: XXX-XX-XXXX\n ERROR: Means Test of NOV 28,2002 not in DHCP.\nthe site that performed the Means Test, and the test did not upload for \nany reason, the "IVM - MEANS TEST UPLOAD" Bulletin gives the following \nmessage:\n \nThe following error occured when an Income Verification Match\nverified Means Test was being uploaded for the following patient:\n \n NAME: Xxxxxxx,Xxxxxxx\n\n
\nSee the National Patch Module for details.\n\n
\nGEOGRAPHIC MEANS TESTING - PHASE II\n\n
\nFix an undefined error received while trying to upload a LTC test from am\nincoming ORU Z10 message.\n\n
\nInpatient/Outpatient Visit Discrepancy\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*13 in the National Patch Module.\n\n
\nStop uploading of LTC tests with a date and an invalid Status code.\n\n
\nFix Z09 issue pertaining to Income Year for multiple years.\n\n
\nChanges to support new ZPD segment builder fo Z07 message.\n\n
\nCorrect Z07 process to now send a llinked RX Copay along with the MT to \nthe HEC.\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*15 in the National Patch Module.\n\n
\nDate of Death Enhancements\n\n
\nThis patch adds a line to call a Registration procedure, DBIA#4780, to \nprocess any patient registration updates received from the HEC to the PFSS\nCOTS billing application\n\n
\nThe changes included in this patch are described in the description\nof patch IVM*2.0*10 in the National Patch Module.\n\n
\nIVM Address Update Project\n\n
\nThis patch updates an earlier single-message link to process batch\nmessages and initiate the generation of A31 Update Person messages.\n\n
\nPlease refer to patch IVM*2*114 in the National Patch Module for a \ncomplete description of this patch.\n\n
\nAUTO-FILE INSURANCE DATA INTO THE INSURANCE BUFFER FILE.\n\n
\nSee the patch description for IVM*2*101 in the FORUM patch module.\n\n
\nIVM*2*120\n\n
\n \ninformation as well as demographic and income data for the patient's\nspouse.\n \nChanges to the patient's name, SSN, DOB, sex, address, phone number, or\nmeans test are transmitted for patients being reviewed by the IVM Center.\nThe IVM package will transmit information to the IVM Center for patients\nwhose means tests meet the following criteria:\n \n Means test is Category A, but neither hardship or adjudicated\n OR\n Means test is Category C, but patient has no active insurance\n \nInformation transmitted includes demographics, income and next-of-kin\n\n
\nPatch to version 2.5 to fix program mistakenly deleted.\n\n
\nDISABLE COREFLS SOFTWARE\n\n
\nCannot print from LBRY SERIALS CHECK-IN\n\n
\nThis patch will fix an undefined error created when subsequently \naccessing certain reports from the 'Serials Titles Reports...' or the \n'Other Serials Reports...' menu and then using a caret to exit.\n\n
\nThis patch will retire the Library package by removing all associated \ncomponents.\n\n
\nPatch to version 2.5 which allows for Primary Stations and Legacy Stations\non one system.\n\n
\nPatch to version 2.5 which allows for Primary Stations and Legacy Stations\non one system. Will merge data from a Legacy Station into a Primary Station's\ndatabase.\n\n
\nThis patch makes the VistA portion of the Library Package Year 2000\ncompliant.\n\n
\nPatch LBR*2.5*8 will replace the need for the VA Integration Team to \nRE-install patch LBR*2.5*3 to integrate Library databases. After \nLBR*2.5*8 installation, Integration Team will be able to run the \ninstallation from the new assigned menu options. Patch 8 is for use at \nmulti-divisional sites. For stations not integrating data, Patch 8 \ninstallation should only take a short time. \n\n
\nThis patch provides Library with the interface capabilities to the Core\n \nA new field is added to the Library Site Parameters that will be used to\nactivate the coreFLS interface:\nFinancial Logististics System (CoreFLS). coreFLS will replace the\nIntegrated Funds Distribution, Control Point Activity, and Procurement\n(IFCAP) package.\n \nVendor information for coreFLS will be remotely held on a national\ndatabase. To aliviate traffic over a network system, a local vendor file,\nLOCAL VENDOR (#392.31) will be accessed to retrieve frequently used\nvendors.\n\n
\nThis patch addresses the prompts displayed in the 'Missing Issues List'\n[LBRY MISSING ISSUE] report. It also removes the option [LBRY ASSIGN\nCOPY] 'no descriptive title' from the 'Library Management' [LBRY MANAGER]\nmenu.\n\n
\nReceiving undefined error at option [LBRY PATRONS REPORTS].\n\n
\nLibrary server messages are not being removed from postmaster (S.LBRYSRV) \nmailbox.\n \nInput template LBRY BIBLIOGRAPHIC 2 ENTRY in LOCAL SERIALS (#680) file is \nchanged to allow skipping over MICROFILM COREFLS VENDOR, rather than \nmaking it a required selection. This template is executed during the \nHOLDING SETUP if the site is running CoreFLS.\n\n
\nThe first module to be developed in an intergrated library system is the\nCheck-in by number of copies ordered or copy by copy, automatic routing,\ntitle entry/edit, claims list, inquire to holdings, automatic prediction\nof next issue for check-in, issue history and various other reports.\nSerials Management Module. It automates the tedious manual serial title\ncheck-in and distribution. It integrates previously scattered data (check-in\nhistory, local holdings, subscription data, and bibliographic data) into\na single title record. It provides many outputs previously unavailable\nwithout hours of manual assembly and repetitive typing. It extends online\nhospital staff access to library holdings and services.\n \nBasic functions to be included in the first version of the package are:\n\n
\nThis is patch 2 of Medicine Version 2.3.\n\n
\nMedicine patch MC*2.3*12\n\n
\nThis patch will enhance the Generalized Procedure module.\n\n
\nPATCH 5 AND 6 SHOULD BE INSTALLED BEFORE PATCH 14. \n [MCFPEP] is used and the report is printed or queued to a printer.\n \n2) NOIS NCH-1197-41215 Pulmonary Function formula (BSA) Body surface\n ROUTINE: MCBPFTP1, MCPFTP1, and MCPFTP1A \n OPTION: PFT Report [MCFPPFT], and Brief PFT Report [MCBPPFT]\n \n An undefined variable BSA would occur when the user selects the PFT Report\n and Brief PFT Report. This only happens if the site used the variable\n BSA in a formula in both the PFT Formula file (#700.2) and in PFT Predicted\n Values file (#700.1). \n \n \nTEST SITES \n========== \nBaltimore, MD \nNorth Chicago, IL \n \n\nROUTINE SUMMARY \n=============== \n \nThis patch will fix the following:\nThe following is a list of the routines included in this patch. The \nsecond line of each of these routines now looks like: \n \n<tab>;;2.3;Medicine;**[PATCH LIST]**;09/13/1996 \n \n CHECK^XTSUMBLD results \n \nRoutine Name Before Patch After Patch Patch List \n------------ ------------ ----------- ---------- \nMCARP 12018137 12045381 **6,14** \n \nMCARP1 6483686 6459372 **14**\nMCBPFTP1 12943531 12985595 **5,14**\nMCPFTP1 12497840 12617605 **14** \nMCPFTP1A 1637882 1597526 **14** \n \nGENERAL INFORMATION \n=================== \nThis patch should be installed into your production UCI. It can be \ninstalled at anytime. Install time is less than 10 minutes. \nThis patch has 1 other patch dependency, patch 6. No options need to be \n1) NOIS # MAR-0697-22511 WHEN PRINTING EP REPORT \ndisabled. Users do not need to be logged off the system. If there are \nany questions, your supporting CIOFO Customer Service Clinical 2\nteam will address them. \n \n This Patch is created with Kernel V8 KIDS. Follow these instructions: \n 1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build \n onto your system. \n 2) On the KIDS menu, under the 'Installation' menu, use the \n option 'Verify Checksum in Transport Global' and verify that all \nroutines have the correct checksums. \n ROUTINE: MCARP and MCARP1 \n 3) From the 'Installation' Menu of KIDS, use the option \n 'Install Package(s)'. Select the package 'MC*2.3*14' and proceed \n with install. \n 4) If you are a MSM site move the routines to the other servers. \n 5) On a mapped system, rebuild your map set.\n OPTION: Results of EP Tests [MCFPEP]\n \n An undefined variable MCY error occurs when the option Results of EP Tests\n\n
\nDescription:\nreport at the time the patch is installed, the process could bomb out, but\nno data base corruption will occur.\n \nSince this patch only installs eight routines installation time is minimal.\n \nRoutine Summary\n===============\n The following is a list of the routines included in this patch. The\n second line of each of these routines now looks like: \n \n===========\n <tab>;;2.3;Medicine;**[PATCH LIST]**;09/13/1996 \n \n CHECK^XTSUMBLD results\n \n Routine Before Patch After Patch Patch List \n ~~~~~~~ ~~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~ \n MCARGES 9410672 9448408 **8,15** \n MCARGP 8855698 8952109 **15** \n MCARHP 9526217 9614292 **15** \n MCARP 12045381 12141792 **6,14,15** \n \n MCARPAC 4176211 4322890 **15**\n MCARP1 6459372 6499295 **14,15** \n MCARPS2 (new rtn) 8362955 **15** \n MCEF 2896312 2900389 **8,15** \n \nInstallation\n============\n This Patch is created with Kernel V8 KIDS.\n \n 1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build onto\nThe purpose of this patch is to modify the Medicine reports so that they\n your system.\n \n 2) On the KIDS menu, under the 'Installation' menu, use the option\n 'Verify Checksum in Transport Global' and verify that all routines\n have the correct checksums.\n \n 3) From the 'Installation' Menu of KIDS, use the option 'Install\n Package(s)'. Select the package 'MC*2.3*15' and proceed with install.\n \n 4) If you are a MSM site move the routines to the other servers.\ncan be added to the CPRS List Manager / GUI reports tab. This patch also\n \n 5) On a mapped system, rebuild your map set.\ncontains the fix to NOIS PUG-1297-51119 DIC('S') left defined. \n \nMedicine users may remain on-line during the installation of this patch.\nNo menu options need to be disabled. If a user is printing a summary\n\n\nRefer to the patch for the patch description.\n\n
\nRefer to the Patch Description of the patch.\n\n
\nRefer to patch Descripton.\n\n
\nPlease see the patch description on FORUM for MC*2.3*19.\n\n
\nThis patch changes the resting blood pressure high/low limits in the the\nLine Entry/Edit of ECHO test [MCFLECHO] options.\n \nThis change was requested in E3R report number 11833.\n \n Installation Instructions: \n ==========================\nThis patch may be installed with users on the system. Installation of\nthis patch will take less than 5 minutes.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu, to\nECHO file (#691).\n load the KIDS Transport Distribution global.\n \n 2. From the Kernel Installation and Distribution System (KIDS) Menu,\n select the Installation menu.\n \n 3. From the Install menu, you may elect to use the following\n options (when prompted for INSTALL NAME, enter MC*2.3*20):\n \n a. Print Transport Global\n b. Compare Transport Global to Current System\n \n \n 4. Use the Install Package(s) option and select the package\n MC*2.3*20.\n \n 5. When prompted "Want to DISABLE Scheduled Options,\n Menu Options, and Protocols? YES//", respond "NO"\n Field # & Name Old Limits New Limits\n =====================================================\n 3 RESTING SYSTOLIC BP 90 - 220 0 - 300\n 4 RESTING DIASTOLIC BP 50 - 150 0 - 300\n \nThese fields may be edited via the Enter/Edit Echo (Screen) [MCFSECHO] and\n\n
\nThis Patch 3 of Medicine 2.3 which will resolve NOIS FAR-1196-42036\nand E3R #9097 and 9144.\n\n
\nMedicine patch MC*2.3*22\n\n
\nMedicine patch MC*2.3*23\n\n
\nSee patch MC*2.3*25 patch description.\n\n
\nSee patch MC*2.3*26 patch description.\n\n
\nPlease refer to the patch description for MC*2.3*27 on Forum for an\nexplanation of this patch.\n\n
\nPlease refer to the patch description for MC*2.3*28 on Forum for an\nexplanation of this patch.\n\n
\nRefer to Patch Description.\n\n
\nRefer to Patch Description.\n\n
\nSee the Patch MC*2.3*30 Description on FORUM for Details.\n\n
\nSee patch Description MC*2.3*32 for a detailed description of this KIDS\nBuild.\n\n
\nThis is patch 5 of Medicine Version 2.3. This patch is the final clean\nup of file 3, 6, and 16.\n\n
\nSee patch Description MC*2.3*33 for a detailed description of this KIDS\nBuild.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nFix to remove Released Not Verified (RNV) from list of choices for the \nRelease Status of a medical procedure when RNV STATUS ON field (#14)\nis set to "NO" in the PROCEDURE/SUBSPECIALTY file (#697.2) for that \nprocedure.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this patch\nbuild.\n\n
\nSee FORUM for detailed descrption on MC*2.3*44.\n\n
\nThis is patch 4 of Medicine Version 2.3. This patch resolves the issue\non E3R #9114 CATH LAB.\n\n
\nSee FORUM for detailed descrption on MC*2.3*43.\n\n
\nAfter the release of VistA patch MC*2.3*25, diffusion calculations were \nno longer valid on the Pulmonary Function Test Report, giving an inflated \ncalculation of the % of predicted. OI&T developed code to fix this and \ngave it to some sites. This code was supposed to be released in a patch \nto correct the calculation, however the patch was not released since the \nMedicine package was subsequently placed in Maintenance. This is needed \nfor VistA Std.\n\n
\nThis patch is to fix the allocation failure error on the ECHO report.\n \nA new routine MCRPEC is going to replace the routines MCAROE* which are\ncompiled from the print templates [MCARECHO1] and [MCARECHO2] for the ECHO\nfile #691. \n \nSince the routine MCARP which is a driver of the print options has been\nchanged, you should install this patch with Medicine users off-line.\nInstallation time for this patch is minimal. \nPlease refer to the NOIS's PHI-1296-20456, PHI-0197-20732, PHI-0297-20499\nand TUC-0297-61746. It also changes the report format which was requested\nin E3R #9458.\n \nThis patch also addresses two issues discovered by the Imaging package.\nThe MCMAGDSP routine would error out with an undefined error for\nHematology reports. Also, this routine would issue a 'Press return to\ncontinue' message at inappropriate times.\n\n
\nMedicine patch MC*2.3*9\n\n
\nMedicine patch MC*2.3*7\n\n
\nMedicine patch MC*2.3*10\n\n
\nMedicine patch MC*2.3*11\n\n
\nMedicine 2.3\n \nand fixes for NOISes:\n POR-0496-50937 WPB-0696-30917 FAR-0496-41748 CLA-1295-21830\n SFC-0296-61898 LEX-0296-40682 CTX-0496-70134 NYN-0696-10330\n NCH-0794-40611 GAI-0596-31465 TUC-0596-60896 PRO-0596-10681\n WPB-0596-30187 NYN-0496-12113 WAS-0396-21347 ALT-0396-21236\n LOU-0796-42170\n \nand enhancements for E3Rs:\n 6984, 8219\n \nThis is a maintenance release.\n \nIt includes Medicine 2.2,\n \nand patches:\n MC*2.2* 1, 2, 3, 4, 5, 6, 7, 8, 10, 13, 14, 15, 16, 17, 18, 19, 20, 21,\n 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35\n\n
\nMedicine 2.2 patch 35\n\n
\nCurrent Version includes Cardiology,GI,Pulmonary Endoscopy, Hematology\nBone Marrow Aspirates and Biopsies, Pacemaker, and Rheumatology\n \nINITS FOR THIS PACKAGE ARE CONTINUED IN 'MC2' MEDICINE-2 PACKAGE\n\n
\nSurgery patch SR*3*58, SURGERY INTERFACE TO PCE.\n\n
\nSurgery patch SR*3*66 includes modifications specifically for Imaging.\n\n
\n1. The Surgery-Tracking Prosthesis Items project enhances the Surgery\n \n2. Unrelated to the Prosthesis features, the trigger event for\n discontinuing orders will be moved from the TIME PAT OUT OR field\n (#.232) of the SURGERY file (#130) to the TIME PAT IN OR field (#.205)\n of the SURGERY file (#130). This enhancement is required as part of\n the Documenting Preoperative Antibiotics (Gainesville Solution)\n project.\n \n3. On the Nurse Intraoperative Report, replace references to CORRECT\n SURGERY COMMENTS to TIME OUT VERIFIED COMMENTS, IMAGING CONFIRMED\n software, adding new fields to the PROSTHESIS INSTALLED sub-file\n COMMENTS, and MARKED SITE COMMENTS, as appropriate.\n (#130.01) in the SURGERY file (#130). These new fields will\n function to mark the prosthesis item as sterile and record the\n expiration date of the sterile implant. The information entered into\n these fields will display on the Nurse Intraoperative Report. As an\n added safety/quality measure, the new fields will be mandatory for\n signing the Nurse Intraoperative Report. The report cannot be signed\n until all documentation is completed.\n\n
\nThis patch updates the Surgery Risk Assessment software of the Veterans\n \nCardiac Risk Assessment Modifications\n-------------------------------------\n- The software is modified to expand the answer options of the PREOP\n CIRCULATORY DEVICE field (#474) to include "ARTIFICIAL HEART" and to \n transmit "A" to CICSP for new raw value of this answer option.\n \n- This patch modifies all Lab fields under the Laboratory Test Results\n (Enter/Edit) [SROA LAB-CARDIAC] option to assume a past date if the user\n enters a date without a year.\n \nNon-Cardiac Assessment Modifications\n- Reinstitute the default functionality of the CARDIAC SURG PERFORMED \n NON-VA field (#472) in the SURGERY file (#130), so that it defaults to\n "NO". \n \n- The description is updated and/or other data dictionary changes are made\n for the following items:\n o CONGESTIVE HEART FAILURE field (#207)\n o ON VENTILATOR >48 HOURS field (#285)\n o PERIOPERATIVE MI field (#385)\n o PREOP CIRCULATORY DEVICE field (#474)\n------------------------------------\n o AORTIC STENOSIS field (#477)\n \n- Data Quality Queries\n The data entry that does not meet the criteria is permitted, but would \n cause a warning message to check the data for accuracy.\n o The D/T PATIENT EXTUBATED field (#470) should be later than the TIME\n PAT OUT OR field (#.232).\n o The D/T PATIENT EXTUBATED field (#470) should be earlier than the D/T\n PATIENT DISCH FROM ICU field (#471).\n o The D/T PATIENT DISCH FROM ICU field (#471) should be later than the\n * Note: All fields named below are in the SURGERY file (#130) unless \n D/T PATIENT EXTUBATED field (#470).\n o D/T PATIENT DISCH FROM ICU field (#471) be equal to or earlier than\n the HOSPITAL DISCHARGE DATE field (#419).\n o The SURGICAL PRIORITY, DATE field (#414.1) should be earlier than\n the TIME PAT IN OR field (#.205).\n o The ESTIMATE OF MORTALITY, DATE field (#364.1) should be earlier than\n the TIME PAT IN OR field (#.205).\n o If TOTAL CPB TIME field (#451) > 0, the CONVERT FROM OFF PUMP TO CPB\n field (#469) should not be answered "NO, began off/stayed off".\n \n otherwise indicated.\n \nGeneral Surgery Items\n---------------------\n- Remedy Ticket #HD0000000152814\n This patch addresses two issues related to the Update Assessment Status\n to 'COMPLETE' [SROA COMPLETE ASSESSMENT] option missing items list:\n (1) For the NUM OF PRIOR HEART SURGERIES field (#352) in the SURGERY\n file (#130), the field is corrected to display "Number of Prior\n Heart Surgeries" instead of "Prior Heart Surgery (Y/N)".\n (2) For the field "PRIOR HEART SURGERIES" field (#485) in the SURGERY \n \n file (#130), the data input functionality is modified to use the\n same controlled data input functionality used by the Clinical\n Information (Enter/Edit) [SROA CLINICAL INFORMATION] option. \n \n- Remedy Ticket #HD0000000177807\n After installing this patch, if procedure and diagnosis coding is not\n complete at the time the Update Assessment Status to 'COMPLETE' [SROA\n COMPLETE ASSESSMENT] option is run, the software will display "The\n coding for Procedure and Diagnosis is not complete" immediately before\n asking, "Are you sure you want to complete this assessment ?".\n- These updates include functionality for selecting cases for risk\n \n- Remedy Ticket #HD0000000185045\n When using the Outcome Information (Enter/Edit) [SROA CARDIAC-OUTCOMES] \n option to edit the OPERATIVE DEATH field (#384), entering YES or NO \n causes the NEW MECHANICAL CIRCULATORY field (#467) to be changed to the \n same value. Editing the NEW MECHANICAL CIRCULATORY field (#467) field \n does not change the OPERATIVE DEATH field (#384).\n \n- Short LOCK Timeouts\n This patch updates the 1 second LOCK timeouts in the routine SROUTL to \n assessment based upon case Current Procedural Terminology (CPT) codes,\n use the VA FileMan variable DILOCKTM if it exists.\n replacing the use of the Major or Minor surgery definition.\n o When selecting a case to be assessed, the software will check the \nHealth Information Systems and Technology Architecture (VistA) Surgery\n case CPT codes and display an informational statement if no CPT codes\n have been assigned to the case or if the case should be excluded from\n assessment.\n o A new report called "List of Eligible Cases" is added to the reports \n contained in the List of Surgery Risk Assessments [SROA ASSESSMENT \n LIST] option.\n o The MAJOR/MINOR field (#.03) is removed from NSQIP input options and \n from the Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] \n option.\n \napplication as requested by the Executive Board of the National Surgical\n- A new field called INTRAOPERATIVE ASCITES (#446) is created:\n o Added to the Operation Information (Enter/Edit) [SROA OPERATION DATA]\n option\n o Added to the Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] \n option\n o Added to data set transmitted to the national database\n \n- A new field called CLOSTRIDIUM DIFFICILE COLITIS (#447) is created:\n o Added to the Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] \n option\nQuality Improvement Program (NSQIP) and by the Cardiac Surgery Consultants\n o Added to the PERIOPERATIVE OCCURRENCE CATEGORIES section of the \n Surgery Quarterly Report\n o CLOSTRIDIUM DIFFICILE COLITIS is added as a new occurrence category \n to the PERIOPERATIVE OCCURRENCE CATEGORY file (#136.5)\n \n- The description is updated and/or other data dictionary changes are made\n for the following items:\n o SURGERY SPECIALTY field (#.04)\n o WOUND CLASSIFICATION field (#1.09)\n o REASON FOR NO ASSESSMENT field (#102)\nBoard of the Continuous Improvement in Cardiac Surgery Program (CICSP).\n o HISTORY OF COPD field (#203)\n o WEIGHT LOSS > 10% field (#215)\n o BLEEDING DISORDERS field (#216)\n o OPEN WOUND field (#218)\n o PREOPERATIVE SEPSIS field (#218.1)\n o PREVIOUS PCI field (#220)\n o SYSTEMIC SEPSIS field (#250) and the SYSTEMIC SEPSIS occurrence \n category in the PERIOPERATIVE OCCURRENCE CATEGORY file (#136.5)\n o PNEUMONIA field (#251) and the PNEUMONIA occurrence category in the \n PERIOPERATIVE OCCURRENCE CATEGORY file (#136.5)\nThe updates include the addition of new data fields, changes to existing \n o PULMONARY EMBOLISM field (#252) and the PULMONARY EMBOLISM occurrence\n category in file (#136.5)\n o ACUTE RENAL FAILURE field (#254) and the ACUTE RENAL FAILURE\n occurrence category in file (#136.5)\n o PREGNANCY field (#269)\n o PERIPHERAL NERVE INJURY field (#287) and the PERIPHERAL NERVE INJURY \n occurrence category in the PERIOPERATIVE OCCURRENCE CATEGORY file \n (#136.5)\n o DYSPNEA field (#325)\n o CURRENT PNEUMONIA field (#326)\ndata fields, changes to data entry screens, changes to reports used in \n o REST PAIN/GANGRENE (Y/N) field (#330)\n o CHEMOTHERAPY IN LAST 30 DAYS field (#338.1)\n o QUADRIPLEGIA (Y/N) field (#398)\n o TUMOR INVOLVING CNS (Y/N) field (#401)\n o INTRAOP DISSEMINATED CANCER field (#443)\n o DATE COMP NOTED field (#2, sub-file #130.22)\n o SEPSIS CATEGORY field (#7, sub-file #130.22)\n \n- Hemoglobin A1c is added to the set of preoperative lab test results.\n \nSurgery Risk Assessment management process and changes to the Surgery Risk\n- This patch modifies all Lab fields under the Laboratory Test Results\n (Enter/Edit) [SROA LAB] option to assume a past date if the user enters\n a date without a year.\n \n- The DATE OF DEATH field (#342) is modified to allow the entry of time as\n well as date and is added to the Patient Demographics (Enter/Edit) [SROA\n DEMOGRAPHICS] option.\n \n- Airway Trauma, Mallampati Scale and Airway Index are removed from the\n set of information collected and transmitted to NSQIP.\nAssessment transmissions.\n \n- The letter produced by the Print 30 Day Follow-up Letters [SROA REPRINT \n LETTERS] option is modified to display the date of operation and the \n local surgical specialty.\n \n- The Monthly Surgical Case Workload Report [SROA MONTHLY WORKLOAD REPORT]\n option is modified to replace references to major/minor with eligible or\n excluded.\n \n \n\n
\nThis patch addresses the following problems:\na RESIDNET\n \n2. HD175983 SROCON Error - <UNDEFINED>HELP+1^SROCON\nWhen entering Anesthesia data for a surgical case, ^SROCON routine errors \nat the\n"Do you want to store this information in the concurrent case ? YES//" \nprompt if \na "?" is entered and concurrent cases exist.\n \n3. HD177449 SROREQ4 UNDEF ERROR\n \nWhen running the : Operation Requests for a Day [SROP REQ] option the \nreport \ngenerates an error <UNDEFINED>PRINT+2^SROREQ4\n S S(0)=^SRF(SRTN,0),DFN=$P(S(0),"^"),CNT=CNT+1\n \n4. HD153358 SROCDX1 Error - <UNDEFINED>PADD1+4^SROCDX1\nAn <UNDEFINDED> error was encountered when trying to verify some ICD-9 \ncodes or Procedure codes.\n1. HD136616 SROPCEP Primary and Secondary Provider incorrect from \nSurgery pkg\nThe information passed from the surgical package to PCE when received in \nPCE the \nSURGEON is listed as the PRIAMRY PROVIDER and the ATTENDING is listed as \nthe \nSECONDARY PROVIDER. Claims are being rejected if the PRIMARY PROVIDER is \n\n
\n1. This patch changes the Environmental Indicator ENVIRONMENTAL \n ENVIRONMENTAL CONTAMINANTS the mnemonic "SWAC:" will be displayed. The \n user dialog "Treatment related to Environmental Contaminants (Y/N)" \n will be changed to "Treatment related to SW Asia (Y/N)".\n \n2. This patch modifies the Surgery software to always use a YES default \nwhen initially prompting for "Treatment related to Combat (Y/N)".\n \n3. This patch modifies the Surgery software so that when entering or \nediting a waiting list entry, service connected and environmental \nindicator questions will be asked if appropriate for the patient \nCONTAMINANTS name to SOUTHWEST ASIA CONDITIONS.\nregardless of the patient's admission status.\n \n - The Surgery package data dictionaries for ENVIRONMENTAL CONTAMINANTS \n will be changed to SOUTHWEST ASIA CONDITIONS. The field help text will \n be updated with the new name. Other field cross references will be\n updated with the new name.\n \n - In user dialog where the mnemonic "EC:" is used to display the \n\n
\nThis patch makes changes to the Surgery software following the \nassessment information when entering or updating a surgery request if the \nASK FOR RISK PREOP INFO field (#17) in the SURGERY SITE PARAMETERS file \n(#133) is set to YES is updated so that this functionality works \ncorrectly with the updated code for CARDIAC SURGERY in the SURGICAL \nSPECIALTY FILE (#45.3).\n \n3. The logic executed when editing the CASE SCHEDULE TYPE field (#.035) \nin the SURGERY file (#130) is updated so that this logic works correctly \nwith the updated code for CARDIAC SURGERY in the SURGICAL SPECIALTY file \n(#45.3) to populate the CARDIAC SURGICAL PRIORITY field (#414) in the \ninstallation of patch DG*5.3*757 (SURGICAL SPECIALTY FILE CHANGES) for \nSURGERY file (#130).\nthe PTF Fields No Longer Needed Project:\n \n1. The Quarterly Report - Surgical Service [SRO QUARTERLY REPORT] option \nis updated to correspond with the codes and specialties that exist in the \nupdated SURGICAL SPECIALTY file (#45.3).\n \n2. The functionality that allows the input of preoperative risk \n\n
\n1. This patch adds the SURGERY CONSULT DATE field (#513) to the SURGERY \nupdated to display the SURGERY CONSULT DATE field (#513) when printing a \ncardiac risk assessment.\n \n4. The missing information functionality for cardiac risk assessments is \nupdated to include the SURGERY CONSULT DATE field (#513) for surgical\ncases after September 30, 2007. This functionality is used by the Update\nAssessment Status to 'COMPLETE' [SROA COMPLETE ASSESSMENT] option and the\nList of Surgery Risk Assessments [SROA ASSESSMENT LIST] option.\n \n5. The SURGERY CONSULT DATE field (#513) is added to the cardiac risk \nfile (#130) for use by the Cardiac Risk Assessment module to document the \nassessment transmission data set.\n \n6. This patch adds the WAIT TIME START field (#21) to the SURGERY file \n(#130). This field will be auto-populated when the SURGERY CONSULT DATE \nfield (#513) is entered. There are no plans to build additional functions \nfor this field at this time. \ndate that the patient was notified that Surgery was needed, effectively \ndocumenting the start of the patient's wait time. \n \n2. The Resource Data [SROA CARDIAC RESOURCE] option is updated to include \nthe SURGERY CONSULT DATE field (#513) for input.\n \n3. The Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] option is \n\n
\nCorrect multiple Surgery tickets\n\n
\nThis patch updates the Surgery Risk Assessment software of the Veterans\n \n enhancement to this option shall list missing items in the same order as\n the standard assessment screens.\n \n- Cardiac Procedures Operative Data (Enter/Edit) [SROA CARDIAC PROCEDURES]\n The system is modified to initially prompts user to "Select Operative \n Information to Edit." A new entry of "N" shall allow the user to "Set\n All to No" for the 22 Cardiac Procedures fields. A verification prompt\n will follow to ensure that user understands entry.\n \n Fields that do not have YES/NO responses will be updated as follows:\nNon-Cardiac Assessment Modifications\n Items #1-#5 are numeric and their values will be set to 0.\n #9 Valve Repair will be set to NONE\n #13 Maze Procedure will be set to NO MAZE PERFORMED\n \n- Laboratory Test Results (Enter/Edit) [SROA LAB-CARDIAC]\n If the lab values entered into the screen are out of range, they will be\n flagged as high or low during data entry.\n \n- Resource Data [SROA CARDIAC RESOURCE]\n o When editing the D/T PATIENT DISCH FROM ICU field (#471), the software\n------------------------------------\n is modified to provide the user with a select option to allow user to\n pull date/time from existing list of possible entries or manually\n enter a date/time\n \n o Postop Extubation Hours\n If the extubation time is entered, the software will display the \n number of hours between the time the patient left the operating room \n and the time the patient was extubated.\n \n o PRIMARY CAUSE FOR DELAY field (#515)\n- List of Surgery Risk Assessment [SROA ASSESSMENT LIST] option\n If a Cardiac patient's surgery is greater than 30 days from initial VA\n Cardiothoracic Surgery Consultation (as calculated between the CT\n CONSULT DATE to DATE OF SURGERY), user is requested to enter cause as\n defined in the field. If date is less than or equal to 30 days, system\n shall automatically default entry to NONE.\n \n \nGeneral Surgery Items\n---------------------\n1. The following fields in the SURGERY file (#130) are updated to utilize \n o When printing the List of Transmitted Assessments to screen or\n VistA Pharmacy supported API's in reference to the DRUG file (#50):\n - MEDICATIONS field (#.01, sub-file #130.33)\n - ANESTHESIA AGENTS field (#.01, sub-file #130.47 of sub-file #130.06)\n - TEST DOSE field (#.01, sub-file #130.48 of sub-file #130.06)\n \n2. Remedy Ticket #HD0000000203815\n When making an operation request, a site parameter controls whether \n preoperative risk assessment information can be entered. If set to YES,\n there are occasions within two screens delete variables causing an\n undefined error. This patch fixes this problem.\n printer, the user is prompted to view/print assessed cases only,\n \n3. Remedy Ticket #HD0000000231157 \n The problem reported in this Remedy ticket is corrected by this patch.\n In the SURGERY file (#130), lookups on the DRUG file (#50) are modified\n to use only the GENERIC NAME field (#.01) and the SYNONYM field (#9).\n \n4. The following date/time fields in the SURGERY file (#130) are modified \n to assume a past date if the user enters a date without a year:\n SURGICAL PRIORITY, DATE field (#414.1)\n HOSPITAL ADMISSION DATE field (#418)\n excluded cases only or both. Additionally, the user is prompted to\n HOSPITAL DISCHARGE DATE field (#419) \n ADMISSION/TRANSFER DATE field (#420)\n DISCHARGE/TRANSFER DATE field (#421)\n OBSERVATION ADMISSION DATE field (#452)\n OBSERVATION DISCHARGE DATE field (#453)\n view/print the list by date of operation or by date of transmission.\n o When printing the List of Eligible Cases to screen or printer, the \n user is prompted to view/print assessed cases only, excluded cases \nHealth Information Systems and Technology Architecture (VistA) Surgery\n only, non-assessed cases only or all cases.\n o A new list, the List of Cases With No CPT Codes is added. This list \n displays all completed cases that have not been coded with CPT codes.\n o A new list, the Summary List of Assessed Cases is added. This report \n displays the total count of incomplete, complete and transmitted risk\n assessments and the count of excluded cases. This report may be \n printed for all or for selected surgical specialties and for all \n divisions or for a selected division.\n \n- M&M Verification Report [SRO M&M VERIFICATION REPORT] option\napplication as requested by the Executive Board of the National Surgical\n This report is modified to display additional information as available,\n including the case number, final CPT codes and review of death comments.\n \n- Clostridium Difficile Colitis (C. difficile) definition updated\n o In the SURGERY file (#130), the description for the CLOSTRIDIUM\n DIFFICILE COLITIS field (#446) is updated.\n o In the PERIOPERATIVE OCCURRENCE CATEGORY file (#136.5), the \n description for the CLOSTRIDIUM DIFFICILE COLITIS (C-DIFFICILE)\n category is updated.\n \nQuality Improvement Program (NSQIP) and by the Cardiac Surgery Consultants\n- In the SURGERY file (#130), the description for the PREOP FUNCT. HEALTH\n STATUS field (#492) is updated.\n \n- Risk Model Lab Test (Enter/Edit) [SROA LAB TEST EDIT] option\n This new option is added to the Surgery Risk Assessment Menu [SROA RISK\n ASSESSMENT] to assist the nurse reviewers in mapping entries in the \n RISK MODEL LAB TEST file (#139.2) to the LAB DATA file (#63).\n \n- REGIONAL Anesthesia Technique added\n o REGIONAL is added to the list of choices when entering the ANESTHESIA\nBoard of the Continuous Improvement in Cardiac Surgery Program (CICSP).\n TECHNIQUE field (#.37) in the SURGERY file (#130).\n o The Anesthesia AMIS [SROAMIS] option is inactivated and removed from\n the Anesthesia Menu [SROANES1] and from the Anesthesia Reports [SR\n ANESTH REPORTS] menu options.\n \n- Preoperative Information (Enter/Edit) [SROA PREOP DATA] option updated\n o The following items are no longer required and are removed from the\n input screens:\n > On Page 1, under GENERAL\n E. Pack/Years\nThe updates include the addition of new data fields, changes to existing \n I. Pre-illness Funct Status\n > On Page 2, under CENTRAL NERVOUS SYSTEM\n H. Paraplegia \n I. Quadriplegia\n o The following changes are made relating to the capture of height from\n the Vitals software:\n > The 1 year date range limitation is removed from the height capture \n process so that the most recent height measurement is returned \n regardless of when it was taken.\n > If the height capture process returns a height measurement from the \ndata fields, changes to data entry screens, changes to reports used in \n Vitals software, the date of the measurement will be stored and \n displayed on the data input screen.\n \n- Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] option\n If the user responds YES to batch printing for a specific date range,\n the user will be allowed to print for a single surgical specialty or for\n all surgical specialties.\n \n- Surgery Consult Dates added\n The Patient Demographics (Enter/Edit) [SROA DEMOGRAPHICS] option is \nSurgery Risk Assessment management process and changes to the Surgery Risk\n updated to include 2 additional date fields:\n o Surgery Consult Date\n o Date Surgery Consult Requested\n \nCardiac Assessment Modifications\n------------------------------------\n- Clinical Information (Enter/Edit) [SROA CLINICAL INFORMATION]\n The HEIGHT field (#236) and the WEIGHT field (#237) will no longer \n accept an entry of NS for "No Study". System will only accept numeric\n values in the field.\nAssessment transmissions.\n \n- Operative Risk Summary Data (Enter/Edit) [SROA CARDIAC OPERATIVE RISK]\n This option is modified to allow users to enter a value of NS (No Study)\n into the Physician's Preoperative Estimate of Operative Mortality field.\n Upon entry of NS, the system will automatically populate the Date/Time\n of Estimate of Operative Mortality field with a value of NS (No Study).\n \n- Update Assessment Status to 'COMPLETE' [SROA COMPLETE ASSESSMENT] \n This option is modified to list items missing from the assessment based \n upon the order in the field number in SURGERY file (#130). An\n\n
\nThe CPT EXCLUSIONS file (#137) stores CPT codes that have been identified\nby the National Surgical Quality Improvement Program (NSQIP) as procedures\nthat should not be risk assessed. This patch updates this file with data\nfor fiscal year 2008.\n\n
\nThis patch modifies the Blood Product Verification [SR BLOOD PRODUCT \nNew Service Request (NSR):\n==========================\nN/A\n \nTest Sites:\n===========\nHEARTLAND-EAST HCS\nPHILADELPHIA, PA\nSAN DIEGO, CA\n \nVERIFICATION] option to accept the manually entered eye-readable code as \n \nDocumentation Retrieval:\n========================\nNo new documents or changes to existing documents are included in this \npatch.\n \n \nInstallation Instructions:\n==========================\nThis patch can be installed at any time with users on the system.\nwell as the scanned bar code for Codabar labels.\nInstallation should take less than two minutes.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. From this menu, you may elect to use the following options (when\n prompted for the INSTALL NAME, enter SR*3.0*168):\n \n \n (a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n \n (b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch is\n installed. It compares all components of the patch (routines,\n DDs, templates, etc.).\n \n (c) Verify Checksums in Transport Global - this option will allow you\n \n to ensure the integrity of the routines that are in the transport\n global.\n \n (d) Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n \n 4. Use the Install Package(s) option and select the package SR*3.0*168.\n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//"\n respond NO.\nAssociated Remedy Ticket(s):\n \n 6. When prompted "Want to DISABLE Scheduled options, Menu options, and\n Protocols? NO//" respond NO.\n \n \nRoutine Summary:\n================\nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n \n============================\n <TAB>;;3.0; Surgery ;**[patch list]**;24 Jun 93;Build 2\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n SRBL 8388831 8708447 148,168\nN/A\n \n\n
\nSurgery patch SR*3*69 - Surgery/PCE/NPCD Reporting\n\n
\nThis patch adds the Transplant Assessment module to the Surgery software.\n This option is used to enter and update the information required for\n the transplant assessments. This option also allows the assessment\n to be completed and transmitted.\n \n (2) Print Transplant Assessment [SRTP PRINT ASSESSMENT]\n This option is used to print a single Surgery Transplant Assessment.\n \n (3) List of Transplant Assessments [SRTP ASSESSMENT LIST]\n This option is used to print the List of Transplant Assessments. It\n provides summary information for assessments within the sort\nThis enhancement provides the ability to create assessments for lung,\n parameters selected.\n \n (4) Transplant Assessment Parameters (Enter/Edit) [SR TRANSPLANT\n PARAMETER]\n This option is used to update local site parameters for the Surgery\n Transplants Assessment module. Sites that are transplant centers must\n designate the types of organ transplants performed or assessed in\n order to streamline the transplant selection process when entering\n data.\n \nliver, kidney and heart transplants.\n- The collected transplant assessments data will be stored in the SURGERY\n TRANSPLANT ASSESSMENTS file (#139.5).\n \n- Transplant Assessments Transmissions\n When editing an individual transplant assessment, upon leaving the\n final page, the software allows the user to transmit the assessment to\n the national database.\n \n o The data of the non-cardiac transplant assessments (lung, liver, and\n kidney) will be transmitted to national NSQIP database in Chicago,\n \n Illinois.\n \n o The data of the heart transplant assessments (cardiac) will be\n transmitted to national NSQIP database in Chicago, Illinois, as well\n as to national CICSP database in Denver, Colorado.\n \n- Followup to patch SR*3*169\n This patch includes a pre-installation process that removes the\n following CPT codes from the CPT EXCLUSIONS file (#137) that were\n overlooked in the NSQIP - CPT EXCLUSION update patch for fiscal year\nA new menu, Transplant Assessment Menu [SR TRANSPLANT ASSESSMENT], is\n 2008 (SR*3*169).\n \n 33945 TRANSPLANTATION OF HEART \n 47135 TRANSPLANTATION OF LIVER\n 47136 TRANSPLANTATION OF LIVER\nadded to the Surgery Menu [SROMENU] option. This new menu includes the\nfollowing four options:\n \n (1) Enter/Edit Transplant Assessments [SR TRANSPLANT ENTER/EDIT]\n\n
\nThis patch addresses one minor issue, updates the CPT Exclusion List for \nIn October 2003, under the Code Set Versioning Project, the code names,\ndescriptions, inactive flags and dates were replaced by versioned data\nelements, each with an effective date of use. Additionally, VA software\npackages who utilize the ICD/CPT files were provided with Code Set\nApplication Programmer Interfaces (APIs) to retrieve the new data and\ninstructed to discontinue the use of the old un-versioned data elements.\n \nThis patch modifies the routine SROCMPED to make use of one of the Code \nSet APIs to retrieve and display versioned data.\n \nNSQIP, and modifies a data element collected by NSQIP and CICSP. Each is \n2. The CPT EXCLUSIONS file (#137) stores CPT codes that have been \nidentified by the National Surgical Quality Improvement Program (NSQIP) as\nprocedures that should not be risk assessed. This patch updates this file\nwith data for fiscal year 2009.\n \n3. The lower range for HEIGHT field (#236) in the SURGERY file (#130)\ncollected by the National Surgical Quality Improvement Program (NSQIP) and\nContinuous Improvement in Cardiac Surgery Program (CICSP) has been lowered\nto account for post amputation height of patients with both legs\namputated.\nexplained in more detail.\n \n1. The Health Insurance Portability and Accessibility Act (HIPAA) \nstipulated that diagnostic and procedure codes and terms used for billing \npurposes must be the codes and terms that were applicable at the time the \nservice was provided.\n \n\n
\nThere are two fixes in this patch: The first issue concerns an\na PRINC. ANESTHESIA TECHNIQUE for their patients.\nUNDEFINED error occurring when trying to enter a DISCHARGE\nFROM PACU (DPACU) time that is earlier than the PATIENT IN ROOM\n(PIR) time even though the date is for the next day under the\nOPERATION INFORMATION option of the NON-CARDIAC ASSESSMENT\nINFORMATION. The second issue is under the same NON-CARDIAC \nASSESSMENT INFORMATION option OPERATION INFORMATION and an \nUNDEFINED error is being generated due to an expected variable\nDA(1) not being set. This prevents users from being able to enter \n\n
\nThis patch provides the annual updates to the Veterans Health Information \n- The frequency of transmission of 1-liner cases is changed from the 45th \n o PREOP CIRCULATORY DEVICE field (#474)\n o ENDOVASCULAR REPAIR field (#505)\n o D/T PATIENT DISCH FROM ICU field (#471)\n \n- Corrections are made to the list of missing items functionality for the\n following fields in the SURGERY file (#130):\n o ANGINA field (#267)\n o CONVERT FROM OFF PUMP TO CPB field (#469)\n \n- TIME OPERATION BEGAN field (#.22) and TIME OPERATION ENDS field (#.23) \n day past the end of the quarter to the 45th day past the end of the\n are moved from the Operative Risk Summary Data (Enter/Edit) [SROA \n CARDIAC OPERATIVE RISK] option to the Resource Data [SROA CARDIAC\n RESOURCE] option.\n \n- The list of missing items functionality is updated to remove deleted \n variables and to include the new variables.\n \n- The SURGERY CONSULT DATE field (#513) and the PRIMARY CAUSE FOR\n DELAY field (#515) are removed from the Resource Data [SROA CARDIAC \n RESOURCE] option.\n month.\n \n- Patient gender is added to the information transmitted on 1-liner cases.\n \n- New fields added to SURGERY file (#130):\n o ASSESSMENT COMPLETED BY field (#272.1)\n When a non-cardiac assessment is completed, the user who completed the\n assessment will be identified in this field and the name of the user \nSystems and Technology Architecture (VistA) Surgery package in support of\n will be transmitted with the assessment.\n o PREOPERATIVE SLEEP APNEA field (#237.1)\n This field is added to the Preoperative Information (Enter/Edit) [SROA\n PREOP DATA] option, the assessment printout, assessment transmission\n and the list of missing items functionality.\n \n- The SURGERY CONSULT DATE field (#513) and the SURGERY CONSULT REQUESTED \n field (#516) are eliminated as non-cardiac assessment variables.\n \n- This patch updates the CPT EXCLUSIONS file (#137) with data for fiscal \nthe VA Surgery Quality Improvement Program (VASQIP). The updates include\n year 2010.\n \n- Field descriptions are modified in the following fields in SURGERY file \n (#130):\n o HEIGHT field (#236)\n The description and the input transform are modified.\n o WEIGHT field (#237)\n The description and the input transform are modified.\n o HISTORY OF COPD field (#203)\n o ASCITES field (#212)\nthe addition of new data fields, changes to existing fields, changes to \n o DISSEMINATED CANCER (Y/N) field (#338)\n o INTRAOP DISSEMINATED CANCER field (#443)\n o BLEEDING DISORDERS field (#216)\n o OTHER PROCEDURE field (#.01 of OTHER PROCEDURES multiple field #.42)\n o INTRAOPERATIVE ASCITES field (#446)\n o DVT/THROMBOPHLEBITIS field (#263)\n Note: The description of DVT/THROMBOPHLEBITIS in the PERIOPERATIVE \n OCCURRENCE CATEGORY file (#136.5) is updated as well.\n \n- On the Operation Information (Enter/Edit) [SROA OPERATION DATA] option:\ndata entry screens, changes to reports, and changes to the Surgery Risk \n o When selecting item #3, CPT Codes (view only), the following note is \n added to the screen:\n CPT Codes should be verified. If need be, report discrepancies to\n the official CPT coder for surgery.\n o When selecting item #5, Concurrent Procedure, the following note is \n added to the screen:\n Concurrent Procedure: An additional operative procedure performed\n by different surgical team (i.e., a different specialty/service)\n under the same anesthetic which has a CPT code different from that\n of the Principal Operative Procedure (e.g., fixation of a femur\nAssessment transmissions.\n fracture in a patient undergoing a laparotomy for trauma). This\n field should be verified and, if need be, report discrepancies to\n the official CPT coder for surgery.\n \n- A new entry, N - NONE ASSIGNED, is added to the ASA CLASS file (#132.8).\n The output transform on ASA CLASS field (#1.13) in SURGERY file (#130)\n is modified to allow the display of the new entry.\n \n- The list of missing items functionality is updated to remove deleted \n variables and to include the new variables.\n \n \nCardiac Assessment Modifications:\n---------------------------------\n- The SURGERY CONSULT DATE field (#513) and the PRIMARY CAUSE FOR DELAY \n field (#515) are eliminated as cardiac assessment variables.\n \n- New fields added to SURGERY file (#130) as new cardiac variables:\n o PREOP ATRIAL FIBRILLATION field (#509)\n This field is added to the Clinical Information (Enter/Edit) [SROA \n CLINICAL INFORMATION] option.\nNon-Cardiac Assessment Modifications:\n o PULMONARY VALVE PROCEDURE field (#493)\n This field is added to the Cardiac Procedures Operative Data \n (Enter/Edit) [SROA CARDIAC PROCEDURES] option.\n o BNP field (#507)\n This field is added to the Laboratory Test Results (Enter/Edit) [SROA \n LAB-CARDIAC] option.\n o BNP DATE field (#507.1)\n This field is added to the Laboratory Test Results (Enter/Edit) [SROA \n LAB-CARDIAC] option.\n o POSTOP ATRIAL FIBRILLATION field (#448)\n-------------------------------------\n This field is added to the Outcome Information (Enter/Edit) [SROA \n CARDIAC-OUTCOMES] option. Associated with this yes/no field is a new \n entry, POSTOPERATIVE ATRIAL FIBRILLATION, in the PERIOPERATIVE \n OCCURRENCE CATEGORY file (#136.5).\n \n- The following fields in SURGERY file (#130) are modified:\n o AORTIC VALVE PROCEDURE field (#367)\n o MITRAL VALVE PROCEDURE field (#368)\n o TRICUSPID VALVE PROCEDURE field (#369)\n o FUNCTIONAL HEALTH STATUS field (#240)\n\n
\nThis patch addresses the following problems:\n \n2. HD238998 - FGH - service block issue on 5th week of month\nWhen a monthly service block is set for a day in the 4th week, users are\nunable to set a service block for that day in the 5th week of a month.\n \n1. HD194156 - Input transform for CPT Modifier 51 in Surgery\nThe Lexicon package has been working to update the CPT code ranges for \nthe CPT Modifier 51. Part of this update is to include all Surgical \nProcedures with the exception of those listed in Appendix E of the CPT\nManual. During the analysis phase for this project, it was discovered \nthat this unique CPT Modifier carries with it the stipulation that it \ncan not be used in conjunction with the principal procedure.\n\n
\nThis patch provides the VASQIP 2011 Increment 1 to the Veterans Health\nI. General Surgery Updates:\n ANESTHESIA AGENTS Multiple (#130.47) of the ANESTHESIA TECHNIQUE\n Multiple (#130.06)\n - DOSE field (#.1) of the TEST DOSE Multiple (#130.48) of the\n ANESTHESIA TECHNIQUE Multiple (#130.06)\n \n9. The Clean Wound Infection Summary Report is updated to include\n the ORGAN/SPACE SSI field (#488) in the algorithm for calculating the\n clean wound infection rates. For cardiac assessed cases, \n ENDOCARDITIS field (#386) and MEDIASTINITIS field (#388) will be\n included in the algorithm for calculating the clean wound infection\n--------------------------\n rates.\n \n10. The Perioperative Occurrences Report, under the Morbidity & Mortality \n Reports [SROMM] option, will be modified to allow three selections as \n follows:\n 1-Intraoperative Occurrences\n 2-Postoperative Occurrences \n 3-Intraoperative and Postoperative Occurrences \n \n \n1. All options under the Quarterly Report Menu [SROQ MENU] are retired\nII. Non-Cardiac Module Updates:\n--------------------------------\n1. A new 30 DAY DEATH field (#342.1) has been added to the\n SURGERY file (#130). This field is added to the Patient \n Demographics (Enter/Edit) [SROA DEMOGRAPHICS] option and it will \n indicate operative death has occurred within 30 days of surgery. This\n field will be auto populated based on an entry into the DATE OF DEATH \n field (#342). If Date of Death occurs within 30 days or less of\n the date in the DATE OF OPERATION field (#.09), then this field is\n automatically updated to "Yes" when the Date of Death is saved. If the\n except the Admissions Within 14 Days of Outpatient Surgery [SROQADM]\n Date of Death is greater than 30 days from the Date of Operation then\n this field is automatically updated to "No" when the Date of Death is\n saved.\n \n2. The data dictionary of the PREOPERATIVE SLEEP APNEA field (#237.1)\n of the SURGERY file (#130) has been changed to allow for an entry of\n "N" for "NONE" on the Preoperative Information (Enter/Edit)\n [SROA PREOP DATA] option. \n \n3. Update the printed Assessment to now include the field ASSESSMENT\n option, the Report of Missing Quarterly Report Data [SROQ MISSING DATA]\n COMPLETED BY field (#272.1) of the SURGERY file (#130).\n \n \nIII. Cardiac Module Updates:\n---------------------------\n1. The field name "Myectomy for IHSS" is changed to "Myectomy" in the\n option for the Cardiac Procedures Operative Data (Enter/Edit)\n [SROA CARDIAC PROCEDURES] option and the the Print Assessment Report.\n \n2. The data dictionary of the BRIDGE TO TRANSPLANT/DEVICE field\n option and Deaths Within 30 Days of Surgery [SROQD], which are\n (#481) is modified from the current values of "Yes" and "No" to "None",\n "Bridge to Transplant", and "Destination Therapy"\n \n3. The existing field, WOUND CLASSIFICATION (#1.09), is added to the\n Operative Risk Summary Data (Enter/Edit) [SROA CARDIAC OPERATIVE RISK] \n option. This field has been added to the Cardiac Print Assessment\n Report.\n \n4. The current WOUND DISRUPTION field (#404) of the Surgery file (#130)\n is added to the Outcome Information (Enter/Edit)[SROA CARDIAC-OUTCOMES]\n relocated under the Management Reports [SRO-CHIEF REPORTS] menu.\n option. This information will appear on the Printed Assessment\n Report and added to the Cardiac Transmission.\n \n5. The Clinical Information (Enter/Edit)[SROA CLINICAL INFORMATION] option\n is updated to allow a response of "N" or "NO" at the prompt to update\n all the fields to a negative value except Height, Weight, FEV1, \n Functional Status, Angina, and CHF.\n \n \nIV. Transplant Module Updates:\n \n-------------------------------\n1. HLA Typing fields in the SURGERY TRANSPLANT ASSESSMENTS file (#139.5)\n across all four organ types are updated to allow entry of 4 digits \n (#,#,#,#). The Transplant Transmission is also updated.\n \n2. The C-PEPTIDE AT TIME OF LISTING field (#136) of the SURGERY \n TRANSPLANT ASSESSMENTS file (#139.5) has been changed to allow for a\n value less than 1. When the value is less than 1, it will be displayed\n with a leading zero (i.e., 0.6). \n \n2. Remove references to "NSQIP" and "CICSP" in field labels and field \n3. The POST-TX PROPHYLAXIS - TB field (#92) of the SURGERY TRANSPLANT\n ASSESSMENTS file (#139.5) has been updated to allow a value to be\n entered of "N/A". This information is added to the Transmission.\n \n4. The COLD ISCHEMIA TIME FOR ORGAN field (#87) and WARM ISCHEMIA TIME FOR\n ORGAN field (#85) of the SURGERY TRANSPLANT ASSESSMENTS file (#139.5)\n has been added to page #1 of the Enter/Edit Transplant Assessments [SR\n TRANSPLANT ENTER/EDIT] option and to the Print Transplant Assessment\n [SRTP PRINT ASSESSMENT] option for VA and Non-VA heart transplants.\n definitions. When the text is not in the header of a definition, the \nInformation Systems and Technology Architecture (VistA) Surgery package in\n terms "NSQIP" and "CICSP" are replaced with "VASQIP".\n \n The complete list of these fields is listed in the Release Notes \n manual.\n \n3. Addition of Scheduling Date fields\n The following new fields are added to the SURGERY file (#130):\n - ORIGINAL DESIRED PROCEDURE DATE field (#612)\n - D/T OF DESIRED PROCEDURE DATE ENTRY field (#613)\n - ORIGINAL SCHEDULED DATE field (#614)\nsupport of the VA Surgery Quality Improvement Program (VASQIP). The\n - D/T OF SCHEDULED DATE ENTRY field (#615)\n - DESIRED PROCEDURE DATE field (#616)\n - SCHEDULED DATE field (#617)\n \n4. Add Time Out Verified Utilizing Checklist\n (a) The following new fields are added to the SURGERY file (#130):\n - CONFIRM PATIENT IDENTITY field (#600)\n - PROCEDURE TO BE PERFORMED field (#601)\n - SITE OF PROCEDURE field (#602)\n - VALID CONSENT FORM field (#603)\nupdates include the addition of new data fields, changes to existing\n - CONFIRM PATIENT POSITION field (#604)\n - MARKED SITE CONFIRMED field (#605)\n - PREOPERATIVE IMAGES CONFIRMED field (#606)\n - CORRECT MEDICAL IMPLANTS field (#607)\n - ANTIBIOTIC PROPHYLAXIS field (#608)\n - APPROPRIATE DVT PROPHYLAXIS field (#609)\n - BLOOD AVAILABILITY field (#610)\n - AVAILABILITY OF SPECIAL EQUIP field (#611)\n - CHECKLIST COMMENT field (#85)\n \nfields, changes to data entry screens, changes to reports, changes to the\n (b) The VALID ID/CONSENT CONFIRMED BY field (#.69) has been renamed to\n CHECKLIST CONFIRMED BY.\n \n (c) All the above new fields are added to the new Time Out Verified\n Utilizing Checklist option [SROMEN-VERF], which has been added to the\n Operation Menu [SROPER].\n \n (d) The existing ensuring correct surgery fields (MARKED SITE CONFIRMED\n field (#73), PREOPERATIVE IMAGING CONFIRMED field (#72), TIME OUT\n VERIFIED field (#71), MARKED SITE COMMENTS field (#84), IMAGING\nSurgery Risk Assessment transmissions, and changes to Transplant\n CONFIRMED COMMENTS field (#83), TIME OUT VERIFIED COMMENTS field \n (#82), and VALID ID/CONSENT CONFIRMED BY field (#.69)) will be\n removed from the following Operation Menu options:\n \n - Operation Startup [SROMEN-START]\n - Operation [SROMEN-OP]\n - Operation (Short Screen) [SROMEN-OUT]\n - Nurse Intraoperative Report [SRONRPT]\n \n (e) The existing ensuring correct surgery fields in the Nurse\ncomponents of the VistA Surgery application.\n Intraoperative Report are replaced with the new Time Out Verified\n Utilizing Checklist fields (the fields listed in item "a" and "b" of\n this section are added).\n \n5. OR Cancellation Report\n - The pre-existing reasons have been inactivated and will not be \n editable but can be viewed.\n - A new selection list for Cancellation Reasons has been added.\n - The SURGERY CANCELLATION REASON file (#135) will be locked with \n this patch so it will no longer be editable at sites.\n \n - The Update Site Configurable Files [SR UPDATE FILES] option has been \n updated to remove the Surgery Cancellation Reasons from the Site \n Configurable Files.\n \n6. The CPT Code Exclusion list for 2011 has been updated so that the\n surgical package can accurately calculate the VASQIP eligible list\n (affecting the CPT EXCLUSIONS file (#137) and the Workload Report/List\n #9).\n \n7. Two pre-existing fields for the SURGERY file (#130), PRINC\n \n ANESTHETIST field (#.31) and ANESTHESIOLOGIST SUPVR field (#.34), have\n been added to the Non-OR Procedure report.\n \n8. This patch updates the Anesthesia Report and the Nurse Intraoperative\n Report to display values of less than 1 for the fields below with a\n leading zero in reports they are displayed.\n \n - DOSE field (#1) of the MEDICATIONS multiple (#130.33)\n - TIME ADM field (#1) of the TIME ADM multiple (#130.34)\n - DOSE field (#1) and the ANESTHESIA AGENTS field (#.01) of the\n\n
\nIn support of the VA Surgery Quality Improvement Program (VASQIP), this \n a. Surgery cancellation functionality is modified so that any surgery \n References to ICD9 are replaced with ICD in the following menu \n options:\n - CPT/ICD9 Coding Menu [SRCODING MENU]\n - CPT/ICD9 Update/Verify Menu [SRCODING UPDATE/VERIFY MENU]\n - Update/verify Procedure/Diagnosis Codes [SRCODING EDIT]\n \n 9. Remove Quarterly Report References\n a. References to "Quarterly Report" are removed from the Deaths Within\n 30 Days of Surgery [SROQD] option.\n \n case that is placed on the surgery schedule and then cancelled will \n b. The routines that provided the Surgery Quarterly Report\n functionality are removed. Those routines are SROQ1, SROQ1A, SROQ2,\n SROQM, SROQM0, SROQM1 and SROQT.\n \n10. Add Superficial Incisional SSI to Cardiac Outcomes\n The SUPERFICIAL INCISIONAL SSI field (#248) in the SURGERY file \n (#130) is added to the Outcome Information (Enter/Edit) [SROA \n CARDIAC-OUTCOMES] option, the cardiac assessment transmission and to \n the cardiac assessment printout.\n \n be retained in the SURGERY file (#130) as a cancelled case\n11. The following routines associated with obsolete functionality are \n removed: SROAC, SROAC1, SROAC2, SROACCR, SROACRC, SROACS, SROASWAP,\n SROASWP, SROASWP0, SROASWP1, SROASWP2, SROAWSP3, SROASWPD, SRSLOOK,\n and SRSLOOK1.\n \n12. This patch fixes the issue reported by Remedy ticket #528445, where \n the PREOPERATIVE IMAGES CONFIRMED field (#606) displays the same data\n as MARKED SITE CONFIRMED field (#605).\n \n13. This patch updates the CPT EXCLUSIONS file (#137) with data for \n regardless of when the case is cancelled. Also, a cancellation\n fiscal year 2012.\n reason is required for every cancellation. Any scheduled case that\n is cancelled will be counted as a cancellation on the Report of\n Cancellations generated by the Report of Cancellations [SROCAN]\n option.\n \n b. The Report of Cancellations, generated by the Report of \npatch provides the VASQIP Increment 2 update to the Veterans Health \n Cancellations [SROCAN] option, is modified to group patient data \n together within specialty so that all cases for a single patient\n will be shown together. The report will also order based on \n operations so the same operation descriptions will show next to each\n other for the same patient. \n \n 2. Miscellaneous Additions to Risk Assessment Transmissions\n a. The name of the operating room as defined in the HOSPITAL LOCATION \n file (#44) is added to each cardiac and non-cardiac risk assessment \n transmission and to each 1-liner case transmission.\nInformation Systems and Technology Architecture (VistA) Surgery package.\n \n b. The following four fields in the SURGERY file (#130) are added to\n each 1-liner case transmission and to the list of items checked for\n by the List of 1-Liner Cases Missing Information which is one of the\n reports generated by the List of Surgery Risk Assessments [SROA\n ASSESSMENT LIST] option:\n - TIME OPERATION BEGAN (#.22)\n - TIME OPERATION ENDS (#.23)\n - TIME PAT IN OR (#.205)\n - TIME PAT OUT OR (#.232)\nThe updates include the addition of new data fields, changes to existing\n \n 3. Positive Drug Screening\n A new POSITIVE DRUG SCREENING field (#618) is added to the SURGERY \n file (#130). This field is added to the Preoperative Information \n (Enter/Edit)[SROA PREOP DATA] option, the Clinical Information \n (Enter/Edit)[SROA CLINICAL INFORMATION] option and the Print a Surgery\n Risk Assessment [SROA PRINT ASSESSMENT] option. This field is also\n added to the cardiac and non-cardiac risk assessment transmissions and\n is added to the list of missing items functionality.\n \nfields, changes to data entry screens, changes to reports, changes to the\n 4. Consolidation of Shared Cardiac, Non-Cardiac and Transplant Fields\n This patch updates various fields in the SURGERY file (#130) and in\n the SURGERY TRANSPLANT ASSESSMENTS file (#139.5) as well as various\n occurrence category descriptions in the PERIOPERATIVE OCCURRENCE\n CATEGORY file (#136.5) so that common items share common definitions.\n This patch also replaces various fields with new fields in order to\n enhance and refine certain data elements that are in common with\n cardiac and non-cardiac risk assessments and transplant assessments.\n All the associated data input options, assessment printouts and\n transmissions are updated accordingly.\nSurgery Risk Assessment transmissions, and changes to transplant\n \n The complete list of updated fields, new fields and replaced \n fields is in the patch release notes.\n \n 5. Add Serial Number for Prosthesis Items\n - Two new fields, LOT NUMBER (#11) and SERIAL NUMBER (#12) are \n added to the PROSTHESIS INSTALLED multiple field (#.47, sub-file \n #130.01) to replace the existing LOT/SERIAL NO field (#2.5). The \n Operation [SROMEN-OP] option and the Nurse Intraoperative Report \n [SRONRPT] option are updated to allow editing and display of these\ncomponents of the VistA Surgery application.\n two new fields.\n - LOT NUMBER field (#8) and SERIAL NUMBER field (#9) are added to\n the PROSTHESIS file (#131.9). The Update Site Configurable Files\n [SR UPDATE FILES] option is modified to allow editing of these new\n fields and to disallow editing of the LOT/SERIAL NO field (#4) and\n the STERILE CODE field (#3).\n \n 6. Flash Sterilization\n Six new fields are added to the SURGERY file (#130) to document the\n number of episodes of each type of flash sterilization that happened\n \n for an operation:\n - FLASH-CONTAMINATION (#619)\n - FLASH-SPD/OR MGT ISSUE (#620)\n - FLASH-EMERGENCY CASE (#621)\n - FLASH-NO BETTER OPTION (#622)\n - FLASH-LOANER INSTRUMENT (#623)\n - FLASH-DECONTAMINATION (#624)\n \n The Post Operation [SROMEN-POST] option and the Nurse Intraoperative\n Report [SRONRPT] option are updated to allow editing and display of\n 1. Surgery Cancellation Modifications\n these two new fields.\n \n 7. 30-Day Readmission\n This patch creates a transmission report that lists inpatient \n surgery cases which were followed by the patient being readmitted \n within 30 days of discharge. This report is run by the Surgery \n Nightly Cleanup and Updates [SRTASK-NIGHT] option and will transmit to\n the VASQIP database automatically each quarter.\n \n 8. Update ICD9 to ICD\n\n
\n \nThis patch addresses the following issues:\n \n(1) Users are receiving an UNDEFINED error at SRHLXTMP+7^SRHLXTMP when\ntheir system runs the nightly task SRTASK-NIGHT option. (2) A user \nreported that addendums created in VistA are not always being \ntransmitted to CPRS. The reason being it appears that TIU BUSINESS RULES\nfor certain document types or user classes are being created which can\ncause unforeseen issues.\n\n
\nThe International Classification of Diseases, Tenth Revision (ICD-10) \ncharacters. This value does not include the decimal point, which follows \nthe third character for the ICD-10-CM code set. There is no decimal point \nin the ICD-10-PCS code set. \nThese code sets have the potential to reveal more about quality of care, \nso that data can be used in a more meaningful way to better understand \ncomplications, better design clinically robust algorithms, and better \ntrack the outcomes of care. ICD-10-CM also incorporates greater \nspecificity and clinical detail to provide information for clinical \ndecision making and outcomes research.\n \nClass 1 Software Remediation project replaces the 30-year-old set of \nThe only noticeable difference users may see will occur when a specific \nICD diagnosis code descriptor changes based on the date of operation for \nthe case.\ndiagnosis and procedure codes (ICD-9-CM) that medical personnel use. \nDates of service, or dates of discharge for inpatients, that occur on or \nafter October 10, 2013 will use the ICD-10 code set. Clinical Modification\n(ICD-10-CM) diagnosis codes increase from about 13,000 ICD-9 codes to \nmore than 68,000. Procedure Coding System (ICD-10-PCS) procedure codes \nincrease from about 3,800 ICD-9 codes to nearly 87,000. Both systems also \nexpand the number of characters allotted to seven alpha-numeric \n\n
\n This patch will correct the following issues currently occurring in\n Next, the FIELD field (#2) for the ATTENDING CODE entry of the Surgery\n Interface Parameter file (#133.2) points to the ATTENDING CODE field\n (#.165) of the SURGERY file (#130) which is no longer used. It should\n point to ATTENDING CODE field (#.166) of the SURGERY file.\n \n \n Finally, when printing the 'LONG' form version of an operation request\n for a particular surgical specialty in the Operation Requests for a\n Day [SROP REQ] option in the Surgery Menu, a site noticed the Case\n Order number is not displaying correctly.\n the VistA Surgery application:\n \n In the Surgery option Exclusion Criteria (Enter/Edit) [SR NO\n ASSESSMENT REASON] when users try to enter exclusion criteria\n beginning with 'EXCEEDS' at the 'Reason an Assessment was not\n Created:' prompt, the response 'EXCEEDS MAX ASSMNTS' is always\n always displaying no matter what the user has entered/selected.\n \n\n
\nSurgery patch SR*3*68 - July 97 Fixes and Updates\n\n
\nThe description of this build can be found in the National Patch Module \nunder SR*3*182.\n\n
\nThe description of this build can be found in the National Patch Module \nunder SR*3*184.\n\n
\nThe patch addresses two (2) issues:\n values have been added to the SET of allowable choices ("1" FOR \n SAME DAY, "2" FOR ADMISSION, "3" FOR HOSPITALIZED).\n \n1. During transmission of Surgery Risk Assessments, an UNDEF error \n occurs when routine SROATMNO calls routine ADM1^SROAPIMS without\n initializing the needed local variable SRSOUT.\n \n2. Routines that generate the Report of Non-O.R. Procedures [SRONOR]\n need to be modified to recognize recent modifications to the \n IN/OUT-PATIENT field (#.011) in the SURGERY FILE (#130): three (3)\n\n\nThe patch addresses two (2) issues:\n caret ("^") to escape the edit session prior to completion, the\n application erroneously adds a field delimiter to the selected\n category record in the SURGERY INTERFACE PARAMETER File (#133.2).\n \n1. When a user edits the PROSTHESIS INSTALLED data for a completed\n surgery case using the Operation option [SROMEN-OP] of the\n Operation Menu option [SROPER] of the Surgery Menu option\n [SROMENU] and answers "NO" when prompted to create an addendum,\n an application error occurs.\n \n2. When a user edits Surgery Flag Interface Fields and enters a\n\n\nThe patch addresses three (3) issues:\n3. Users are unable to enter a D Code (Dental) in the PLANNED \n PRINCIPAL PROCEDURE field (#27) of the SURGERY file (#130) using\n the Non-O.R. Procedure option [SRONOP] in the Surgery package.\n \n1. Cases aborted prior to the release of SR*3.0*184 are displayed as \n "CANCELLED" in the Operation Menu option [SROPER].\n \n2. Nurses are unable to sign their Nurse Intraoperative Report (NIR) \n in the Surgical Package when the case has been aborted using the \n Abort/Cancel Operation option [SROABRT].\n \n\n
\nThe patch addresses four (4) issues:\n3. Surgery Post Operation and CPT/ICD Update/Verify options incorrectly\n allow CPT Modifier 51 to be entered on the Principle Procedure.\n4. The Surgery Schedule of Operations report truncates the patient \n name inappropriately when its length is great than 23 characters.\n \n1. When Surgery sends HL7 (Health Level-7) DG1 (Diagnosis) Segments to\n Ancillary systems, messages with other preoperative diagnoses have\n an incorrect value for the ICD diagnosis code.\n2. When a Wound Classification Report is generated at an institution \n that has only one (1) Active surgery site and the Active site isn't \n the installation's default institution, the report displays no data \n regardless of the date range selected.\n\n
\nPatch SR*3.0*189 addresses the following Surgery issue:\n \n 1. The SURGERY file (#130) ADT and ARS cross references do not merge \nduring a patient merge.\n\n
\nThe patch addresses one (1) issues:\n \n1. Under certain conditions, the transplant/donor section is not\n displayed on the Nurse Intraoperative Report (NIR)\n\n
\nPreoperative CVD data fields assigned invalid values\n\n
\nHOSPITAL ADMISSION STATUS field defaults to an inactive code\n\n
\nNational Surgical Quality Improvement Program (NSQIP) enhancements patch.\n\n
\nThe description of this build can be found in the National Patch Module \nunder SR*3*195.\n\n
\nThe patch addresses one (1) issue:\n \n1. When the MAKE OPERATION REQUEST [SROOPREQ] option is used to \n delete an outstanding surgery request with a concurrent case \n request, the user is asked if they want to delete the concurrent\n case and defaults to "yes". If the user accepts the default the\n outstanding request AND concurrent cases are deleted regardless\n whether the concurrent case is completed case.\n\n
\nThe patch addresses two (2) issue:\n schedule the same case for different times or rooms and block \n those resources from other users.\n \n1. When a POSTOP OCCURRENCE for "OUT-OF-OR UNPLANNED INTUBATION \n W/IN 30 DAYS" is entered and then deleted, the printed risk \n assessment improperly displays "NO DATE" rather than "NO" for\n the occurrence.\n \n2. When two (2) users accidently attempt to schedule or reschedule\n an operation for the same patient, they can inadvertently \n\n
\nBackup of SR*3.0*202 on Jun 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe patch will address the following issue: \n \nThe CPT EXCLUSIONS file (#137) needs to be updated for fiscal year 2021 \n(FY21).\n\n
\nThis enhancement to the VISTA Surgery package includes a new field \n(137.45). If defined for a local specialty, the software will\nautomatically enter NO in the ROBOTIC ASSISTANCE (Y/N) field when\na surgery case is created for the selected specialty.\n \nUpdate to transmission code to restrict date/time field 613 to 12 \ncharacters.\n \nUpdate to Nurse Intraoperative report to have Laser Duration notes as \nseconds (not minutes). Update to file #130.11, field #14 to reflect this \nchange.\nROBOTIC ASSISTANCE (Y/N) for tracking whether robotic assistance was used \n \nUpdate to include a search for any height for the patient, not just a \nheight in the past year.\nwhen completing a surgery procedure. The new field is included on the \nOperation, Operation Short Screen, and Nurse Intraoperative Report \noptions within the Operation Menu and is required to be entered prior to \nsigning the Nurse Intraoperative Report. The field is also included on \nNon-Cardiac and Cardiac Risk Assessment data entry options. This \nindicator is transmitted to VASQIP for all cases. A new field, ROBOTIC \nDEFAULT (#12) has been added to the LOCAL SURGICAL SPECIALTY file\n\n
\nThe patch addresses two (2) issues: \n DELIVERED field (#9) in the LASER PERFORMED multiple (#135) in the \n SURGERY FILE (#130). Specifically: the request is to increase the \n largest allowable value to 99999.9.\n \n1. One Liner (1-Liner) cases are not transmitting to the National Risk\n Assessment database because the SURGERY FILE (#130) AQ XREF is being \n killed and not reset when the TIME PAT OUT OR field (#.232) in the \n SURGERY FILE (#130) is edited for a surgery case with a signed Nurse\n Intraoperative Report with coding complete.\n \n2. A request is to increase the numeric upper limit of the TOTAL JOULES\n\n
\nThe patch addresses one (1) issue: \n \nThe patch will address the following issue: the CPT EXCLUSIONS file (#137)\nneeds to be updated for fiscal year 2022 (FY22).\n\n
\nThe patch addresses three (3) issue: \n Abnormally terminated, the Operating Room schedule is blocked. If \n the VistA session times out at the same prompt, the Operating Room\n schedule is not blocked.\n \n3. The Cardiac Assessment option only captures the height if entered \n into the Vitals package in the past year instead of capturing height \n regardless of when the measurement was taken like the Non-Cardiac \n Assessment option.\n \n1. When using the "Scheduled Unrequested Operations" [SROSRES] option\n at the PRIMARY SURGEON prompt and the VistA session is terminated,\n the Operating Room schedule is blocked. If the VistA session times\n out at the same prompt, the Operating Room schedule is not blocked.\n \n2. When using the "Schedule Unrequested Concurrent Cases" [SRSCHDC] \n Option at the PRIMARY SURGEON prompt and the VistA session is\n\n
\nThe patch addresses one (1) issue: \n \n1. Under certain circumstance, completed concurrent surgical cases (the \nTIME PAT OUT OR field {#.232} in the SURGERY FILE {#130} is entered) are \nallowed to be deleted from the VistA Surgery package.\n\n\nSurgery patch SR*3*70 - September 97 Fixes\n\n
\nThe patch addresses one (1) issue: \n \n1. The National Surgery Office requests that the help text for wound \nclassification information in VistA Surgery be updated so that 2018 CDC \nWound Classification definitions are displayed rather than the current \ndefinitions (2007).\n\n
\nThe patch addresses one (1) issue: \n \nThe patch will address the following issue: the CPT EXCLUSIONS file (#137)\nneeds to be updated for fiscal year 2023 (FY23).\n\n
\nThe patch addresses one (1) issue: \n \nThe CONCURRENT CASE field (#35) in the SURGERY FILE (#130) in a completed \nconcurrent case is cleared however the CONCURRENT CASE field is not \ncleared in a cancelled concurrent case.\n\n
\nThe patch addresses one (1) issue: \n \nUnder certain circumstances, the CULTURES title/data does not display on \nthe Nurse Intraoperative Report using the VistA Nurse Intraoperative \nReport display/print option or on the SURGERY tab in CPRS. This occurs \nwhen the NURSE INTRAOP REPORT field (#29) in the SURGERY SITE PARAMETERS \nFILE (#133) is set to "PRINT TITLES WITH INFO ONLY" and the CULTURES \nfield (#64) in the SURGERY FILE (#130) contains data and the SPECIMENS \nfield (#49) does not.\n\n
\nThe patch addresses one (1) issue: \n \nUnder certain circumstances, the CVD REPAIR/OBSTRUCT field (#521) value \nin the SURGERY File (#130) is not displaying/printing for a NON-CARDIAC \nRISK ASSESSMENT using the "Print a Surgery Risk Assessment" [SROA PRINT \nASSESSMENT] option.\n\n
\nThe patch addresses one (2) issues: \nerroneously instead of the field name/title when adding a new entry to \nseveral multiples in the SURGERY file (#130) when entering a new surgery \ncase using the "Operation Menu". The multiples are: OTHER PROCEDURES \n(#.42), OTHER PREOP DIAGNOISIS (#.72)\nSURGERY POSITION (#65), REQ BLOOD KIND (#1.05), SPECIAL EQUIPMENT (#680), \nPLANNED IMPLANTS (#681), SPECIAL SUPPLIES (#682), SPECIAL INSTRUMENTS \n(#683), PHARMACY ITEMS (#684), and REFERRING PHYSICIAN (#23).\n \n1. In certain circumstances if a value is entered in the REFERRING\nPHYSICIAN field (#23) of the SURGERY FILE (#130) in a surgery case the\nvalue is carried over and DISPLAYS in the SPECIAL EQUIPMENT (#680),\nPLANNED IMPLANTS (#681), SPECIAL SUPPLIES (#682), SPECIAL INSTRUMENTS\n(#683) or PHARMACY ITEMS (#684) fields.\n \n2. In certain circumstances "Select Surgical Specialty:" displays \n\n
\nThis enhancement to the VistA Surgery package includes:\n \nSTORED IN ^SRF( (XX ENTRIES) SITE: XXXXXXX UCI: XXXXXXX\n (VERSION 3)\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n-------------------------------------------------------------------------\n \n130,665 DONOR VESSEL DISPOSITION VER1;16 SET\n \n Donor Vessel Disposition if not used \n \n 'N' FOR NO DONOR VESSELS RECEIVED; \n 'D' FOR DISCARDED; \n 'R' FOR RETURNED TO OPO; \n 'S' FOR STORED; \n *'NA' FOR NOT APPLICABLE; <--\n LAST EDITED: MAY 18, 2022 \n HELP-PROMPT: Enter disposition of donor vessels. \n DESCRIPTION:\n Document disposition of donor vessels.\n \n1. An update to the SET OF CODES for the DONOR VESSEL DISPOSITION (#665)\n2. Input template (order of menu options) realignment\n \nThe SRONRPT, SRONRPT1, and SRONRPT2 input templates that are executed when\nthe Nurse Intraoperative Report [SRONRPT] option is selected have been\nupdated to follow the order of menu options requested by the National\nSurgery Office (NSO).\n \n3. Deactivation of the POSSIBLE ITEM RETENTION (#630) field in the SURGERY\n(#130) file\n \nfield in the SURGERY (#130) file\nThe POSSIBLE ITEM RETENTION (#630) field has been marked as \nUNEDITABLE in the SURGERY (#130) file and will no longer be included in\nany VistA Surgery input templates for entry or editing. This field will\nalso no longer be required to electronically sign the Nurse Intraoperative\nreport. It will, however, continue to display in completed Nurse\nIntraoperative Reports for historical cases.\n \n4. Correction of spelling for GLASSES/GOOGLES to GLASSES/GOGGLES in the \nPATIENT PRECAUTIONS (#15) subfield of the LASER PERFORMED (#130.11)\nmultiple in the SURGERY (#130) file for display/print in the Nurse\n \nIntraoperative Report.\n'NA - NOT APPLICABLE' has been added to the set of codes that can be\nselected for the DONOR VESSEL DISPOSITION (#665) field in the SURGERY \n(#130) file. Surgery Risk Assessment transmissions have been modified to\naccommodate the new 2 character code.\n\n
\nThe patch addresses one (1) issue: \n \nThe patch will address the following issue: the CPT EXCLUSIONS file (#137)\nneeds to be updated for fiscal year 2024 (FY24).\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nThis patch removes the SURGEON'S OPERATION TIMES file (#131.2) from your\nsystem. This file has been obsolete since the release of Surgery V. 3.0 in\n1993.\n\n
\nThis patch modifies the routine ^SROCODE used for flagging anesthesia\nenhanced to create a background task for performing this function.\nagents. With the release of Pharmacy Data Management V. 1.0, existing\ncalls to the Inpatient Medications routine ^PSGIU will be replaced by\nthe Pharmacy Data Management routine ^PSSGIU. This modification allows\nthe function to work with or without the installation of Pharmacy\nData Management V. 1.0.\n \nThis patch also modifies the routine ^SROXR1 which is used for canceling\nIV orders upon start of a surgical procedure. This routine has been\n\n
\nThis patch contains modifications to routines used to file information to\nbetween Surgery and Order Entry/Results Reporting will be reestablished. A\nfuture patch will be necessary when that time comes.\nOE/RR. Changes will allow the software to function in it's current form\nwhen using Order Entry/Results Reporting V2.5, but will inactivate the\ninterface for sites using CPRS and Order Entry/Results Reporting V3.0. The\ninterface for Surgery used within Order Entry/Results Reporting V2.5 is\nnot supported with CPRS and Order Entry/Results Reporting V3.0, causing\nerrors when using the Surgery software.\n \nAt the time of release of this patch, it is unclear when the interface\n\n
\nSurgery patch SR*3*75 - DELAYED OP REPORT COMMENTS ERROR\n\n
\nThis patch modifies the routines SROCON and SROCON1 used in creating the\ndata to be stored in Concurrent Cases. A problem was discovered when a\nfree text field contained a semi colon (;). The patch resolves this\nproblem.\n\n
\nPatch SR*3*77 provides software renovations related to Y2K (Year 2000)\ncompliance.\n\n
\n This patch contains a new option [SR BLOOD PRODUCT VERIFICATION] within\n selected product is not associated with the patient identified, the\n warning message will be displayed.\n \n A new option called [SR BLOOD PRODUCT VERIFY AUDIT] is included to allow\n auditing of the option above. It has been placed on the "Chief of Surgery\n Menu" on the "Management Reports Menu".\n \n After installing this patch, IRM needs to turn on the KERNEL Audit Option\n by invoking the option, [XUAUDIT] for the new option exported with this\n patch [SR BLOOD PRODUCT VERIFICATION]. The expiration date for the audit\n the VistA Surgery package which will be used for transfusion error risk\n should be set to a date 100 years into the future.\n management. The new option is contained on the Surgery "Operations Menu".\n The option performs the following function; after scanning the blood unit\n ID, the software will check for an association with the patient\n identified. If there are multiple entries with the Unit ID scanned, these\n entries will be listed along with the Blood Component, Patient\n Associated, and Expiration Date. The user will then be prompted to select\n the one that matches the blood product about to be administered. If the\n\n
\nThe Surgery Interface is a generic interface that sends and receives\nSurgery and Patient information by way of the VistA HL7 package. The\ninterface consists of QRY (Query), ORU (Observation Results Unsolicited),\nand ZIU (Scheduling Information Unsolicited) messages. Certain specified\ninformation is sent from the interface based on trigger events in the\nVistA Surgery package.\n\n
\n This patch adds "ORAL" as a medications route to the set of codes within\n This patch modifies the routine SROXR1 to correct a problem at entry\n point IV with an undefined variable 'Y' and converts a read/write at\n entry point IV1 to a FileMan call.\n Surgery file (#130) and modifies the routine SROMED to reflect this\n addition.\n \n This patch also changes the definition of the field Major/Minor\n per Dr. Gerald McDonald, Acting Director, Surgical Service, VACO and the \n National Surgical Quality Improvement Program (NSQIP) Executive\n Committee.\n \n\n
\nThis is Surgery patch SR*3*83.\n\n
\nThis patch modifies one Surgery routine, SROQM, which is used to transmit\nmail messages related to the Quarterly Report. Current code, while it\nworks properly, needs to be updated based on guidance received from the\nMailMan development team. The changes included in this patch should be\ntransparent.\n\n
\nThis patch corrects an undefined variable condition when the OERR Task\nOrder Purge option [ORTASK PURGE] runs after installing patch SR*3*41.\nThis patch also reinstalls the protocols included in patch SR*3*41. The\ninstall process for SR*3*41 did not properly update HL7 related fields for\nthese protocols in virgin installs.\n\n
\nThis is Surgery patch SR*3*50, REPORTS BY DIVISION & OTHER FIXES.\n\n
\nSurgery Patch SR*3*84 - XQUIT Processing\n\n
\nSurgery patch SR*3*81 - NSQIP/VHA Directive 98-025\n\n
\nThis patch modifies one Surgery routine, SRBLOOD. This routine is used by\nthe Blood Product Verification option [SR BLOOD PRODUCT VERIFICATION].\nIt is possible, but rare, that this routine could result in a software\nerror when reading the Blood Unit ID. This patch eliminates the potential\nhole in the logic.\n\n
\nThis is Surgery patch SR*3*86.\n\n
\nThe changes included in this patch are described in the description\nof patch SR*3*87 in the National Patch Module.\n\n
\nThis patch enhances the API written for the Imaging software. It updates\nthe data to use a 4-digit year format when sending the DATE OF OPERATION\nfield (#.09) from the SURGERY file (#130). Changes have also been made to\nprovide the total number of images associated with the surgery case.\n\n
\n Under some circumstances, incorrect nursing personnel were appearing on\n the Operation Report when using the option Batch Print Transcripted\n Operation Notes [SRSTRANS PRINT]. The problem occurs when a previous case\n in the batch has more entries for the fields OR SCRUB SUPPORT (#.112) or\n OR CIRC SUPPORT (#.111) of the SURGERY file (#130).\n\n
\n1. Information from the STROKE/CVA field (#256) of the SURGERY file (#130)\n$J.\n \n3. The list of station numbers that identify medical centers that perform\ncardiac surgery is updated in the routine SROAUTLC, replacing 525\n(Brockton/West Roxbury) with 523 (Boston). This routine is further\nmodified updating several reads and writes with calls to ^DIR and\nEN^DDIOL.\nwas not correctly extracted for cardiac risk assessments. This patch\ncorrects the problem. The patch also provides a post-installation routine\nto retransmit missing information for all surgical cases in which the\nSTROKE/CVA field (#256) was answered "YES".\n \n2. This patch updates the cardiac assessment transmission routines\n(SROATCM, SROATCM1 and SROATCM2) so that in references to the global ^TMP\nthe first two subscripts are a package namespaced subscript followed by\n\n
\nSurgery patch SR*3*88 provides the ability to enter CPT modifiers and\nprovides for displaying these CPT modifiers on screens and reports that\ndisplay CPT codes within the Surgery package. The patch also includes\nseveral software updates related to NSQIP and multi-division facilities.\n\n
\n1. The cardiac risk assessment transmission routines SROATCM, SROATCM1 and\n \nThis patch includes a post-install process that will transmit the added\npieces of information for all cardiac assessments that have already\ntransmitted.\n \n2. For cardiac assessments, when using the Resource Data [SROA CARDIAC\nRESOURCE] option or the Update Assessment Status to 'COMPLETE' [SROA\nCOMPLETE ASSESSMENT] option, if the admission date is later than the\ndischarge date, the following message will be displayed on the screen:\n \nSROATCM2 are modified by this patch to do the following:\n *** NOTE: Discharge Date precedes Admission Date!! Please check. ***\n \nSimilarly, when using the Cardiac Procedures Requiring CPB (Enter/Edit)\n[SROA CARDIAC PROCEDURES] option or the Update Assessment Status to\n'COMPLETE' [SROA COMPLETE ASSESSMENT] option, if the ischemic time is\ngreater than the CPB (cardiopulmonary bypass) time, the following message\nwill be displayed on the screen:\n \n *** NOTE: Ischemic Time is greater than CPB Time!! Please check. ***\n \n \nThese changes require modifications to the routines SROACAR, SROACPM,\nSROACR1 and SROACOM.\n \n3. The non-cardiac transmission routines SROATM1 and SROATMNO are modified\nby this patch to add to the transmissions the entry in the INTUBATED ?\n(Y/N) field (#42) for the principal anesthesia technique defined in the\nANESTHESIA TECHNIQUE multiple field (#.37) in SURGERY file (#130).\n \nThis patch includes a post-install process that will transmit this added\npiece of information for all FY2000 cases that have already transmitted.\n a. For both the admission and the discharge movements associated with\n \n4. The routine SRSUP1 is modified to correct the problem described in NOIS\nDAY-0200-41350.\n the assessed operation, the entry in the TRANSFER FACILITY field (#.05)\n in the PATIENT MOVEMENT file (#405) is added to the transmission.\n \n b. The patient's address, including street address, city and state, and\n the patient's phone number are added to the transmission.\n\n
\n1. When using the option Print Surgery Waiting List [SRSWL2] to print the\n \n3. The options Operation Requests for a Day [SROP REQ] and Report of Missing\nQuarterly Report Data [SROQ MISSING DATA] are updated to make the reports\nprint by division. This change requires that the following routines be\nmodified: SROPREQ, SROQN, SROREQ, SROREQ1, SROREQ2, SROREQ3 and SROREQ4.\n \n4. When entering a request for an operation, if the normal request deadline\nfalls on a holiday, the method used by the software to recalculate the\ndeadline to allow for the holiday is problematic. (See NOIS BAY-0100-31625.)\nThis patch modifies the routines SRSCAN2 and SRSREQ. After installing this\nbrief form by tentative date of operation, entering "^" to quit may not work.\npatch, if the normal request deadline falls on a holiday, the software will\nuse the deadline for the closest valid scheduling date prior to the operation\nrequest date.\n(See NOIS ALB-1199-52220.) This patch modifies the routines SRSWL12 and\nSRSWL14 to correct the problem.\n \n2. The Monthly Surgical Case Workload Report [SROA MONTHLY WORKLOAD REPORT]\noption may generate an error if the report is run for a month prior to\nOctober 1995. (See NOIS TAM-1299-31004.) The routine SROAWL1 is modified to\ncorrect the problem.\n\n
\n1. This patch modifies the routine SROASSP adding the call to %ZISC to close\n3. The routines SROREST and SROIRR are modified to correct the problem\ndescribed in NOIS V02-0400-N0176. When using the option Enter Irrigation and\nRestraints [SROMEN-REST], if the number of active entries in the IRRIGATION\nfile (#133.6) or in the RESTRAINTS AND POSITIONAL AIDS file (#132.05) is\ngreater than 36, items will be displayed on multiple screen pages with no\nmore than 36 items per page. \n \n4. Before installing this patch, if the nurse reviewer used the option\nNon-Cardiac Assessment Information (Enter/Edit) [SROA ENTER/EDIT] or the\noption Cardiac Risk Assessment Information (Enter/Edit) [SROA CARDIAC\nthe printer device. This change fixes the problem described by NOIS\nENTER/EDIT] to update a risk assessment that was already transmitted, the\nsoftware required the nurse reviewer to go to the option Update Assessment\nCompleted/Transmitted in Error [SROA TRANSMITTED IN ERROR] to change the\nassessment status to incomplete before updating was allowed. After installing\nthis patch, if the nurse reviewer attempts to update a risk assessment using\nthe option Non-Cardiac Assessment Information (Enter/Edit) [SROA ENTER/EDIT]\nor the option Cardiac Risk Assessment Information (Enter/Edit) [SROA CARDIAC\nENTER/EDIT], the option will allow the nurse reviewer to change the assessment\nstatus to incomplete without having to go to another option first. The\nroutine SROASS is modified to provide this change.\nTAM-0300-32135 and NOIS ALB-0200-51214.\n \n5. Obsolete code used originally to check for old Surgery Risk Assessment data\nwas removed from the routine SROASS. This code was called by the entry action\nof 6 options whose entry actions are also updated by this patch. Those 6\noptions are listed below.\n \n Exclusion Criteria (Enter/Edit) [SR NO ASSESSMENT REASON]\n List of Surgery Risk Assessments [SROA ASSESSMENT LIST]\n Non-Cardiac Assessment Information (Enter/Edit) [SROA ENTER/EDIT]\n Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT]\n \n Print 30 Day Follow-up Letters [SROA REPRINT LETTERS]\n Update Assessment Completed/Transmitted in Error [SROA TRANSMITTED IN ERROR]\n \n6. This patch modifies the routines SRODLAY, SRODLA1, SRODLA2, SROREAS,\nSROREA1, SROREA2, SRODLT, SRODLT0, SROCAN, SROCAN0, SROCRAT, SRORAT1 and\nSRORAT2 allowing the following report options to print reports for all\ndivisions or for a selected division:\n Report of Delayed Operations [SRODELA]\n Report of Delay Reasons [SROREAS]\n Report of Delay Time [SRO DELAY TIME]\n2. The routine SRSDISP is modified to allow the display of the first 8\n Report of Cancellations [SROCAN]\n Report of Cancellation Rates [SROCRAT]\n \n7. This patch updates the data dictionary for the following fields in\nSURGERY file (#130) to require the inclusion of at least one space in\nevery 31 characters of input. See NOIS HVH-0500-10303. \n \n OTHER PREOP DIAGNOSIS multiple field (#.72, sub-file #130.17)\n OTHER PREOP DIAGNOSIS field (#.01)\n OTHER POSTOP DIAGS multiple field (#.74, sub-file #130.18)\ncharacters of the name of the operating room on the operating room\n OTHER POSTOP DIAGS field (#.01)\n PRINCIPAL PRE-OP DIAGNOSIS field (#32)\n PRINCIPAL DIAGNOSIS field (#33)\n PRINCIPAL POST-OP DIAGNOSIS field (#34)\navailability display graph. This change is made in response to NOIS\nGNH-0300-42659\n \n\n
\nThis patch installs the SURGERY DISPOSITION file (#131.6), converts the\nthree disposition fields to point to this file and updates reports that\naccess disposition data.\n\n
\nThis patch provides enhancements in support of the Continuous Improvement\nin Cardiac Surgery Program Expansion (CICSP-X). \nSee Patch SR*3*95 in the National Patch Module for description of the\nBuild.\n\n
\nSee Patch SR*3*97 in the National Patch Module for description of the\nBuild.\n\n
\nSee patch SR*3*98 in the National Patch Module for description of this\nbuild.\n\n
\n1. The input screen of the Cardiac Procedures Requiring CPB (Enter/Edit)\n expands to "RI-Remains in ICU at 30 days" when entered for D/T PATIENT\n EXTUBATED field (#470) in the SURGERY file (#130). Actually, it should\n expand to "RI-Remains intubated at 30 days". This patch fixes this\n problem.\n [SROA CARDIAC PROCEDURES] option, for the BATISTA PROCEDURE USED field\n (#439) the screen displays what is in the MISC. CARDIAC PROCEDURES\n field (#375) of the SURGERY file (#130). This patch fixes this problem.\n \n2. The cardiac assessment transmission is modified to include the\n patient's date of birth.\n \n3. On the Resource Data [SROA CARDIAC RESOURCE] option, the code "RI"\n\n
\n1. On the Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] option,\n this patch rewords the message to read "Today's date exceeds the blood\n product expiration date.".\n the code "RI" expands to "RI-Remains in ICU at 30 days" when entered\n for D/T PATIENT EXTUBATED field (#470) in the SURGERY file (#130).\n Actually, it should expand to "RI-Remains intubated at 30 days". This\n patch fixes this problem.\n \n2. On the Blood Product Verification [SR BLOOD PRODUCT VERIFICATION]\n option, if the blood unit is expired the system displays the worning\n message "Blood Product Expiration Date is later than today's date.",\n\n
\n1. This patch modifies the RISK ASSESSMENT IN USE (Y/N) field (#15) in the\n controls access based upon the sites default institution station number.\n \n2. This patch fixes the problem reported in NOIS SDC-0301-62902 to prevent\n the undefined variable error that may occur when completing a\n non-cardiac risk assessment.\n SURGERY SITE PARAMETERS file (#133), changing the name of the field to\n CARDIAC RISK ASSESSMENT IN USE(Y/N). After installing this patch, the\n entry action on the Cardiac Risk Assessment Information (Enter/Edit)\n [SROA CARDIAC ENTER/EDIT] menu will check this parameter field to\n determine if menu access is allowed. This parameter may be edited using\n the Surgery Site Parameters (Enter/Edit) [SROPARAM] option on the Surgery \n Package Management Menu [SRO PACKAGE MANAGEMENT]. This change enables\n local control of menu access and replaces the current function that \n\n
\n1. As reported in NOIS DUR-0501-32617, the value in the DATE/TIME OR\n2. NOIS CPH-0601-41315 reported that the Surgery Quarterly Report is\ncontinuing to use inactive CPT codes in the Index Procedures section of\nthe report. This patch modifies the routine SROQ0A, replacing the 3\ninactive CPT codes (56340, 56341 and 56342) with the 3 replacement codes\n(47562, 47563 and 47564). The post-install process will task the\nQuarterly Reports for the past reporting periods of FY 2001 to transmit\nagain.\nREQUEST MADE field (#1.098) in SURGERY file (#130) occasionally includes\ntrailing zeros that cause the exclusion of such values when sorting by a\ndate range. This patch modifies the routines SRSCAN0, SRSCAN2, SRSCHUN,\nSRSDT and SRSRQST so that trailing zeros will be removed before the value\nis stored. A post-install process will loop through SURGERY file (#130)\nand remove any trailing zeros in the DATE/TIME OR REQUEST MADE field\n(#1.098).\n \n\n
\n1. This patch modifies routine SROPRPT, adding the call to HOME^%ZIS to\n fix the error "DEVICE OR FILE NOT OPEN" that occurs occasionally due to\n the printer device not being closed prior to running the Operation\n Report [SROSRPT] option.\n \n2. This patch fixes the problem reported in NOIS PUG-0701-50135, of an\n extrinsic function call in routine SROAUTLC which quits without a\n value.\n\n
\n1. This patch fixes the Undefined Error reported on NOIS LAH-0901-60445.\n The error is generated as a result of not killing variable DR before\n calling Surgery screen server routine SRCUSS.\n \n2. When using the Delete Service Blockout [SRSBDEL] option at a\n multi-division facility, it was reported that this option displays all\n operations, where as it should display only those operations for the\n selected division. This patch fixes this problem.\n\n
\n1. This patch corrects the problem described in NOIS UNY-1101-11002 and NOIS \n \nThis patch adds the following new fields to store responses to the MST and \nHNC classification questions that will be passed to PCE with the other \nsurgical encounter information:\n - File: SURGERY (#130)\n Field: MILITARY SEXUAL TRAUMA (#.022) SET\n Description: This field will be used to indicate if this surgery or non-OR\n procedure is treating a VA patient for a problem that is\n related to Military Sexual Trauma. This information may be \n passed to the VISIT file (#9000010) for use by PCE.\nHAM-1101-21180.\n \n Field: HEAD AND/OR NECK CANCER (#.023) SET\n Description: This field will be used to indicate if this surgery or non-OR\n procedure is treating a VA patient for a problem that is \n related to Head and/or Neck Cancer. This information may be \n passed to the VISIT file (#9000010) for use by PCE.\n \n - File: SURGERY WAITING LIST (#133.8)\n Field: PATIENT (#1) (Multiple, sub-file #133.801)\n Sub-Field: MILITARY SEXUAL TRAUMA (#21) SET\n \n Description: This field will be used to indicate if this surgery is \n treating a VA patient for a problem related to military \n sexual trauma. This information may be passed to the VISIT\n file (#9000010) to be used by PCE.\n \n Sub-Field: HEAD AND/OR NECK CANCER (#22) SET\n Description: This field will be used to indicate if this surgery is \n treating a VA patient for a problem related to Head and/or\n Neck Cancer. This information may be passed to the VISIT\n file (#9000010) to be used by PCE.\n2. This patch modifies the Surgery software to include the Military Sexual \nTrauma (MST) classification question and the Head and/or Neck Cancer (HNC) \nclassification question on the list of potential classification questions \nthat must be answered on ambulatory surgeries that are passed to PCE if the \nSurgery interface to PCE is turned on and the ASK CLASSIFICATION QUESTIONS \nfield (#19) in SURGERY SITE PARAMETERS file (#133) is set to YES.\n\n
\nSurgery Patch SR*3*62.\n\n
\n1. It was reported that, when using the Report of Unscheduled Admissions\n characters, but no spaces in the next 80 or more characters after the\n last space, the software would loop, causing the job to hang. This\n patch fixes this problem.\n to ICU [SROICU] option, if the site is a multi-division facility, this\n report populates the data from all the divisions. This patch modifies\n the routines SROICU, SROICU1, and SROICU2 to enhance printing of this\n report to be a division specific.\n \n2. When using the Nurse Intraoperative Reprot [SRONRPT] option, there is a\n problem which causes the job to hang. If the NURSING CARE COMMENTS\n field (#.29) of the SURGERY file (#130) contains spaces in the first 78\n\n
\n1. The calls to the Imaging (MAG) V 1.0 package software that are in the\n patch fixes this problem.\n \n3. It was observed that when editing any multiple fields via the Surgery\n Screen Server Utility it's currently not allow editing of any multiple\n fields if those fields have only the top level field (.01) in the Input\n Template. This patch will ensure that such fields are editable.\n Surgery routines were added to those routines by patch SR*3*66 to\n facilitate the use of the Imaging software. These calls are obsolete,\n any reference to those calls will cause the software to generate an\n error. This patch removes all of these references.\n \n2. It was reported that the REQ FROZ SECT field (#1.02) in the SURGERY\n file (#130) is not printed when generating the Operating Room\n Schedule report using the Schedule of Operations [SROSCH] option. This\n\n
\nThis patch exports a new "AOE" cross-reference to the TIME PAT OUT OR\nfield (#.232) in the SURGERY file (#130). The new cross-reference will\nallow the Computerized Patient Record System (CPRS) to automatically\ndiscontinue or release orders when patient leaves the Operating Room.\n\n
\nIn preparation for the VistA Blood Establishment Computer Software \npost-install routine. A mail message will be sent to the person who \nstarted the installation to let them know the conversion is complete and \nany problems that were encountered. The subject of the message will be: \nSURGERY POINTER CONVERSION COMPLETED. Please note: if problems were \nencountered, the message will contain information on correcting the \nproblems and re-running the conversion. However, it is not required to do \nthis. Just be aware that these entries will now simply display as a \nnumber.\n(VBECS), changes are necessary in the Surgery V. 3.0 package. Any \nreference to the blood bank information needs to be modified to prepare \nfor the VBECS release. This patch makes these modifications.\n \nAs a part of these changes, it is necessary to convert the existing data. \nPointers from the SURGERY SITE PARAMETERS file (#133) and the SURGERY \nfile (#130) that reference the BLOOD PRODUCT file (#66) will be changed \nto actually contain the name of the product. This process will run as a \n\n
\nThis patch contains modifications to the Surgery package to include new\n Ethnicity and multiple Races display on the report. These fields are \n not editable through the Surgery package options.\n \n3. Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT]. Ethnicity \n and multiple races appear on the report.\n \n4. Queue Assessment Transmissions [SROA TRANSMIT ASSESSMENTS].\n a. Non-Cardiac Risk Assessment transmission. Old Race \n information is retained on node 7. New Ethnicity and multiple\n Races are transmitted on node 13.\nEthnicity and multiple Race fields in four Surgery options as listed \n b. Cardiac Risk Assessment transmission. Old Race information is\n retained on node 24. New Ethnicity and multiple Races \n are transmitted on node 6.\nbelow. The new fields comply with the new Race and Ethnicity Standards as\nset forth by the Office of Management and Budget.\n \n1. Tissue Examination Report [SROTRPT]. Ethnicity and multiple Races \n appear in the report footer.\n \n2. Non-Cardiac Assessment Information (Enter/Edit) [SROA ENTER/EDIT].\n\n
\nThis is an enhancement patch to the Surgery V. 3.0 software. It will\n \n1. The new SPD COMMENTS field (#80) of the SURGERY file (#130) is added to\n the following options:\n \n - Make Operation Requests [SROOPREQ]\n - Delete or Update Operation Requests [SRSUPRQ]\n - Make a Request from the Waiting List [SRSWREQ]\n - Make a Request for Concurrent Cases [SRSREQCC]\n - Schedule Unrequested Operations [SROSRES]\n - Schedule Unrequested Concurrent Cases [SRSCHDC]\nreplace the existing Surgery interface with the Integrated Funds\n - Reschedule or Update a Scheduled Operation [SRSCHUP]\n \n2. The new AUTOMATED CASE CART ORDERING field (#37) will be added to the\n SURGERY SITE PARAMETERS file (#133) input template SRPARAM so that\n this field may be edited using the Surgery Site Parameters (Enter/Edit)\n [SROPARAM] option. This field will be checked to determine if the\n CoreFLS interface for Surgery is in use at the facility before sending\n the Surgery data to the CoreFLS package.\n \n3. This patch modifies all options used to create or schedule a Surgery\nDistribution, Control Point Activity, Accounting, and Procurement (IFCAP)\n case so that information can be provided to SPD for the creation of\n Surgery case carts.\n \n4. This patch modifies the Surgery software to send updates to SPD\n whenever any of the information provided on the messages has been\n modified using any data entry option.\n \n5. This patch enhances the following options to initiate HL7 update\n messages if the Surgery Health Level 7 (HL7) interface is in use at\n the facility for the following options:\nwith a new interface to the Core Financial and Logistics System (CoreFLS).\n \n - Enter PAC(U) Information [SROMEN-PACU]\n - Patient Demographics (Enter/Edit) [SROA DEMOGRAPHICS]\n - Operative Risk Summary Data (Enter/Edit) [SROA CARDIAC OPERATIVE\n RISK]\n - Exclusion Criteria (Enter/Edit) [SR NO ASSESSMENT REASON]\n - Update 1-Liner Case [SROA ONE-LINER UPDATE]\nFunctionally, the new interface expands the features provided in the\nexisting interface. The interface will provide Surgery case information to\nSupply Processing and Distribution (SPD) so that the specific Surgery\ncase carts needed for the case can be created. The modifications include\nthe following items:\n\n
\nThis patch provides the ability to display a new confidential \ncommunication address when using the Print 30 Day Follow-up Letters [SROA \nREPRINT LETTERS] option within VISTA Surgery if the Confidential \nCommunication Types contain "All Others".\n\n
\nThis patch is created in support of directive 2002-070, ENSURING CORRECT\nSURGERY.\n \nThe patch adds two new fields in the SURGERY file (#130). They are\nneeded to document that the operating room team performed a "time out" to\nensure that the correct surgery is being done. The new fields are:\n 1. TIME OUT VERIFIED (#71)\n 2. IMAGING CONFIRMED (#72)\n\n
\n1. This patch fixes the "NULLSUBSCR" error generated when using the PRINT\n2. This patch adds the description to the Data Dictionary of the\n DEFAULT BLOOD COMPONENT field (#41) in the SURGERY SITE PARAMETERS file\n (#133).\n \n3. When updating a Risk Assessment Status to "COMPLETE", the software\n checks for missing information and provides the ability to update it.\n This option was overlooked when doing the Race & Ethnicity changes\n (patch SR*3*111). This patch removes the current checking for the RACE \n field (#417) in the SURGERY file (#130).\n \n FILE ENTRIES FileMan option to print one or more of the following\n4. When using the Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT]\n option, there is a possibility of getting an undefined error if the\n length of the race data is found to be more than forty characters.\n This patch fixes this problem.\n fields in the SURGERY file (#130) if these fields contain no data:\n \n - OTHER RESPIRATORY OCCURRENCE field (#253)\n - OTHER URINARY TRACT OCCURRENCE field (#286)\n - OTHER CNS OCCURRENCE field (#343)\n - OTHER CARDIAC OCCURRENCE field (#344)\n \n\n
\n1. Surgery is using the Flag Drugs for Use as Anesthesia Agents [SROCODE] \n If the user quits using the up-arrow ("^"), the software does not\n respond correctly and subsequently errors out. This patch fixes this\n problem.\n \n3. It was reported that if the Surgery case was in a requested state \n and if an entry is made in the TIME PAT IN OR field (#.205) of the \n SURGERY file (#130), it is found that the time gets appended to the\n DATE OF OPERATION field (#.09) of the SURGERY file (#130). This is\n causing the time to appear in the scheduling grid and prevents the case\n scheduling. This entry should be made only if the case is in a\n option to flag drugs in the DRUG file (#50) for use as anesthesia \n scheduled state or entered via the Operation Menu [SROPER] option. This\n patch provides the user the option to delete any of the following\n entered date fields as a pre-condition for scheduling such cases:\n \n - ANES CARE START TIME field (#.21), TIME OPERATION BEGAN \n field (#.22), TIME OPERATION ENDS field (#.23), ANES CARE END TIME\n field (#.24), TIME PAT IN OR field (#.205), and TIME PAT OUT OR\n field (#.232)\n \n This functionality is added to the following options:\n agents. This patch modifies this option to call Pharmacy Data\n - Delete or Update Operation Requests [SRSUPRQ] option\n - Schedule Requested Operations [SRSCHD1] option\n - Reschedule or Update a Scheduled Operation [SRSCHUP] option\n Management V. 1.0 (PDM) package so that PDM possibly generates an HL7\n outgoing drug message.\n \n2. When canceling a concurrent case using the Cancel Scheduled Operation \n [SRSCAN] option, the software prompts, "There is a concurrent case \n associated with this operation. Do you want to cancel it also? YES//".\n\n\nSurgery patch SR*3*63, Fixes and Enhancements.\n\n
\nAs a follow-up enhancement to Surgery patch SR*3*115, this patch adds a \nCONFIRMED field (#72). A surgical case is counted as compliant with the \ndocumentation process for ensuring correct surgery if the TIME OUT \nVERIFIED field (#71) is YES and if the IMAGING CONFIRMED field (#72) is \neither YES or NOT APPLICABLE.\n \nThis report includes two parts, either of which may be printed separately \nor combined: \n 1. Compliance Summary - This part shows the number of cases with each of\n the possible data scenarios for the two fields in question and their\n percentage of the total cases performed.\nnew report option to assist in reviewing compliance with the process \n 2. List of Non-Compliant Cases - This part provides a list of surgical\n cases that are not compliant (as defined above).\ndefined by directive 2002-070, ENSURING CORRECT SURGERY. Ensuring Correct \nSurgery Compliance Report [SRO ECS COMPLIANCE] option is added to the \nManagement Reports [SRO-CHIEF REPORTS] menu on the Chief of Surgery Menu\n[SROCHIEF] option. \n \nThis report checks the two fields added to SURGERY file (#130) by Surgery \npatch SR*3*115, the TIME OUT VERIFIED field (#71) and the IMAGING \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nAs a follow-up enhancement to Surgery patch SR*3*115 (released April 8, \nafter November 13, 2003, the Quarterly Report for the fourth quarter of\nFiscal Year 2003 will also be automatically transmitted by a post-install\nprocess.\n2003), this patch updates the Quarterly Report by adding the Compliance \nSummary portion of the Ensuring Correct Surgery Compliance Report (made \navailable by patch SR*3*120) to the end of the existing Quarterly Report.\nThis additional information will be transmitted as part of the Quarterly\nReport that goes to Surgical Service, Central Office.\n \nA post-install process will automatically transmit the Quarterly Report \nfor the third quarter of Fiscal Year 2003. If this patch is installed\n\n
\nThis is an enhancement patch to the Surgery V. 3.0 software. It will\n - Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT]\n - Update Assessment Completed/Transmitted in Error\n [SROA TRANSMITTED IN ERROR]\n - Print 30 Day Follow-up Letters [SROA REPRINT LETTERS]\n - Exclusion Criteria (Enter/Edit) [SR NO ASSESSMENT REASON]\n - Update 1-Liner Case [SROA ONE-LINER UPDATE]\nallow assessment lookups by assessment (case) number, in addition to the\nlookups by patient. The following options under the Surgery Risk\nAssessment Menu [SROA RISK ASSESSMENT] option has this functionality\nincorporated:\n \n - Non-Cardiac Assessment Information (Enter/Edit) [SROA ENTER/EDIT]\n - Cardiac Risk Assessment Information (Enter/Edit)\n [SROA CARDIAC ENTER/EDIT]\n\n
\nThis patch corrects two problems. It corrects the problem in the \ndisplay when entering "Other Procedures" in the Operation [SROMEN-OP]\nOption. The display is limited to 15 entries, and sometimes more\nthan 15 "Other Procedures" entries are needed. The patch also corrects\na problem that occurs when printing the PCE Filing Status report. \nLong names should list the initial for the patient's first name. \nCurrently, the report drops the first name completely.\n\n
\nThis patch corrects the null subscript error in SROPRPT routine.\n\n
\nThis patch updates the PROTOCOL file(#101) and HL LOGICAL LINK file(#870) \nfor the Surgery interface. HL LOGICAL LINK file(#870) does not contain \nany site specific data.\n\n
\nThis patch is an enhancement to the Surgery software providing additional\n type field.\n \nThis patch modifies the following four existing fields in the SURGERY\nfile (#130):\n - A minor change is made to the description of the "NO" choice in\n the TIME OUT VERIFIED field (#71).\n \n - The PREOPERATIVE IMAGING CONFIRMED field (#72) will have three\n choices: "Y, YES", "I, IMAGING NOT REQUIRED FOR THIS PROCEDURE" and\n "N, NO - IMAGING REQUIRED BUT NOT VIEWED (see CORRECT SURGERY\nchanges related to Ensuring Correct Surgery. This patch is Phase I of the\n COMMENTS)"\n \n - The description of the different choices of the ATTENDING CODE\n field (#.165) is modified.\n \n - The maximum number of years of surgical residency (post graduate)\n of the PGY OF PRIMARY SURGEON field (#214) is changed from 10 to 12.\n \nThis patch also exports the following new date/time fields that will be\nused to time-stamp when the three correct Surgery fields (TIME OUT\nenhancement.\nVERIFIED (#71), PREOPERATIVE IMAGING CONFIRMED (#72), and MARKED SITE\nCONFIRMED (#73)) of the SURGERY file (#130) are entered or edited, and\nthey are not editable fields:\n - TOV TIMESTAMP field (#75)\n - IMAG TIMESTAMP field (#76)\n - SITE MARK TIMESTAMP field (#77)\n \nThese fields MARKED SITE CONFIRMED (#73), PREOPERATIVE IMAGING CONFIRMED\n(#72), and CORRECT SURGERY COMMENTS (#74) are found under the following\nmenu options:\n \n - Operation [SROMEN-OP] option\n - Operation (Short Screen) [SROMEN-OUT] option\n - Operation Startup [SROMEN-START] option\n \nThis patch will disable the Ensuring Correct Surgery Compliance Report\n[SRO ECS COMPLIANCE] option. Also, the compliance section of the\nQuarterly Report - Surgical Service [SRO QUARTERLY REPORT] option will be\ndisabled until Correct Surgery Enhancements 2004 Phase II is released,\ntargeted date is June 2004.\nThis patch exports the following new fields in the SURGERY file (#130):\n - The MARKED SITE CONFIRMED field (#73) will have three choices:\n "Y, YES", "M, MARKING NOT REQUIRED FOR THIS PROCEDURE" and "N, NO -\n MARKING REQUIRED BUT NOT DONE (see CORRECT SURGERY COMMENTS)".\n - The CORRECT SURGERY COMMENTS field (#74) which is a word processing\n\n
\nThis patch provides the ability to electronically sign operative reports \nFeatures provided by this patch are described in the Surgery Electronic \nSignature for Operative Reports Release Notes and in the Surgery \nElectronic Signature for Operative Reports Implementation Guide.\ncontained within the VISTA Surgery V. 3.0 application. These reports\ninclude the Operation Report, the Nurse Intraoperative Report, the\nAnesthesia Report and the Procedure Report (Non-O.R.). This patch provides\nthe ability to view these signed reports through the Computerized Patient\nRecord System (CPRS) by storing them in the Text Integration Utilities\n(TIU) V. 1.0 application. Tools provided by the TIU software will be used\nto sign and manage the electronic documents.\n \n\n
\nThis patch addresses follow-up issues related to the Surgery Electronic \n**DRAFT COPY - DRAFT COPY -- ABOVE NOTE IS UNSIGNED-- DRAFT COPY - DRAFT COPY**\n \n This patch modifies the routine SROESPR1 to prevent the display of this\n line if the document has a status of COMPLETED. See NOIS\n FAR-0104-40622.\n \n2. The input template SROARPT is used by the Anesthesia Report [SROARPT] \n option to edit fields that are part of the Anesthesia Report. This \n patch modifies this input template to remove the INTRAOPERATIVE\n OCCURRENCES field (#1.14) and the POSTOP OCCURRENCE field (#1.16) since\nSignature for Operative Reports patch (SR*3*100).\n these two fields do not appear on the Anesthesia Report.\n \n1. Converted documents for historical surgical/non-OR cases are stored in \n the TIU DOCUMENT file (#8925) with a status of COMPLETED, but they \n have no signature date. Therefore, when one of these converted\n documents is printed, the following line is printed at the end of the\n document text:\n \n\n
\nThe information contained in this KIDS Build relates to the Surgery patch\nSR*3*64.\n\n
\n******************************* N O T E **********************************\n procedures. This patch implements the new levels of resident \n comment field.\n At the end of the conversion process, this patch will delete the data\n dictionary of the CORRECT SURGERY COMMENTS field (#74) in the SURGERY\n file (#130), which was exported in phase I of the Ensuring Correct\n Surgery patch SR*3.0*126.\n \n3. SURGEON PRESENT TIME ON NURSE INTRAOPERATIVE REPORT\n Patch SR*3*25 modified the Nurse Intraoperative Report so that it \n displayed the SURG PRESENT TIME field (#.206) only if data was entered.\n This functionality, omitted unintentionally by patch SR*3*100, is\n supervision in the Surgery software and includes the following\n restored by this patch.\n \n4. DOCUMENTS PRINTED FROM TIU\n This patch modifies the routine SROESPR to correct a possible problem \n if no print group is defined when a document is printed.\n features:\n \n (a) A new file, ATTENDING CODES file (#132.9), is created to store all \n attending codes used by the Surgery software. These codes include \n both sets of Levels 0 to 3 (before and after patch SR*3*126, all\n flagged as inactive codes) and the latest codes for Levels A to F\n (active codes).\n \nThere is no conflict between this patch and the CoreFLS software.\n (b) The name of the existing ATTENDING CODE field (#.165) in the SURGERY\n file (#130) is changed to *ATTENDING CODE - NOT USED and a new\n ATTENDING CODE field (#.166) is created that points to the ATTENDING\n CODES file (#132.9).\n \n (c) The patch includes a post-install conversion that loops through all \n the cases in the SURGERY file (#130) and matches the attending code\n in the old field (#.165) with the equivalent code in the new\n ATTENDING CODE field (#.166), storing the equivalent code in the new\n field. The content of the old field is not changed by the conversion.\nInstallation of this patch by the CoreFLS sites will not cause any \n \n (d) The following data entry options are updated to use the new ATTENDING\n CODE field (#.166): \n - Post Operation [SROMEN-POST] \n - Operation (Short Screen) [SROMEN-OUT] \n - Surgical Staff [SROMEN-STAFF] \n - Edit Non-O.R. Procedure [SRONOP-EDIT] \n - Update 1-Liner Case [SROA ONE-LINER UPDATE]\n \n (e) The following report and display options are updated to use the new \nproblems.\n ATTENDING CODE field (#.166): \n - Attending Surgeon Reports [SROATT] \n - View Patient Perioperative Occurrences [SROMEN-M&M] \n - Operation Information [SROMEN-OPINFO] \n - Quarterly Report - Surgical Service [SRO QUARTERLY REPORT] \n Note: The Perioperative Occurrence Categories on this report are\n updated to reflect the categories used by the National Surgical\n Quality Improvement Program (NSQIP) and the Continuous Improvement\n in Cardiac Surgery Program (CICSP). Some of these categories may\n not be immediately available for selection, but will be included\n**************************************************************************\n later in the NSQIP/CICSP ENHANCEMENTS 2004 patch (SR*3*125).\n - List of Operations Included on Quarterly Report [SROQ LIST OPS] \n - Report of Missing Quarterly Report Data [SROQ MISSING DATA]\n \n (f) The patch updates the transmission of Quarterly Report data to the \n national database to use the new ATTENDING CODE field (#.166). \n \n2. ENSURING CORRECT SURGERY PHASE II\n Phase II of the Ensuring Correct Surgery Enhancement Project provides\n the following enhancements:\n \n \n (a) The following new fields are added to the SURGERY file (#130):\n - TIME OUT VERIFIED COMMENTS field (#82)\n - IMAGING CONFIRMED COMMENTS field (#83)\n - MARKED SITE COMMENTS field (#84)\n \n These fields are added to capture the comments corresponding to the\n following:\n - TIME OUT VERIFIED field (#71)\n - PREOPERATIVE IMAGING CONFIRMED field (#72)\n1. RESIDENT SUPERVISION\n - MARKED SITE CONFIRMED field (#73)\n \n (b) The following data entry options will be modified to include\n the new comment fields noted in item (a):\n - Operation [SROMEN-OP]\n - Operation (Short Screen) [SROMEN-OUT]\n - Nurse Intraoperative Report [SRONRPT]\n \n Entry of "NO" in any of the three Correct Surgery fields will prompt\n the user to enter the associated comment field. Entry of "NO" in\n The Veterans Health Administration (VHA) Handbook 1400.1, dated May 3, \n any of the three Correct Surgery fields will not automatically force\n entry into the respective comment field.\n \n (c) Nurse Intraoperative Report Changes\n If any of the three Correct Surgery fields are not answered, the\n nurse will not be able to electronically sign the Nurse\n Intraoperative Report. If any of the three Correct Surgery fields is\n answered "NO" but does not have information in the corresponding\n comments field, the nurse will not be able to electronically sign the\n Nurse Intraoperative Report. The nurse will be able to update this\n 2004, changed the levels of resident supervision for operating room \n information at time of signature without leaving the option.\n \n (d) The compliance reports, which were disabled in phase I are \n reactivated and are modified to display the new formats for the three\n Correct Surgery fields.\n \n (e) Convert Existing Comments\n For each of the three Correct Surgery fields answered with a "NO" \n response, the information in the CORRECT SURGERY COMMENTS field (#27)\n of the SURGERY file (#130) will be replicated in the corresponding\n\n
\n******************************* N O T E *********************************\ndictated summary, if present. After patch SR*3*100, the Procedure Report \n(Non-OR) includes only the provider's dictated summary since only the \nprovider's dictated summary is electronically signed. The only way to \nreview the information entered into the data fields documenting the \nprocedure in the SURGERY file (#130) is by way of the data entry options \non the Non-O.R. Procedures (Enter/Edit) [SRONOP-ENTER] menu.\n \nThis patch adds the Non-OR Procedure Information [SR NON-OR INFO] option, \nto the Non-O.R. Procedures (Enter/Edit) [SRONOP-ENTER] menu and to the \nCPT/ICD9 Update/Verify Menu [SRCODING UPDATE/VERIFY MENU]. This option \nThere is no conflict between this patch and the CoreFLS software.\nwill display the "op-top" information that formerly was part of the \nProcedure Report (Non-OR). The output from this option may be viewed on \nthe user's screen or may be printed. \n \nA future enhancement is planned that will incorporate the "op-top"\ninformation into an electronically signed document and thus be viewable in\nthe Computerized Patient Record System (CPRS). At this time, the details\nof this enhancement and schedule for release are not known.\nInstallation of this patch by the CoreFLS sites will not cause any \nproblems.\n*************************************************************************\n \nPrior to patch SR*3*100, the Procedure Report (Non-OR) included an \n"op-top" section that included many of the data fields documenting the \nprocedure in the SURGERY file (#130) in addition to the provider's \n\n
\n******************************* N O T E **********************************\n VA's NSQIP module more in line with the data collected in the private\n sector. This patch also include updates to the Continuous Improvement\n in Cardiac Surgery Program (CICSP) module. \n \n Modifications to the Surgery V. 3.0 software include:\n - the addition of 22 new fields to SURGERY file (#130)\n - the update of approximately 120 field descriptions for NSQIP and \n CICSP data elements in the SURGERY file (#130)\n - the update of data input screens to allow the input of additional\n data elements as well as to delete some data elements no longer \nThere is no conflict between this patch and the CoreFLS software.\n needed\n - the addition of two new data input options, Laboratory Test Results \n (Enter/Edit) [SROA LAB-CARDIAC] and Outcome Information (Enter/Edit) \n [SROA CARDIAC-OUTCOMES], on the Cardiac Risk Assessment Information \n (Enter/Edit) [SROA CARDIAC ENTER/EDIT] menu\n - the removal of the option Update Operations as Unrelated/Related to \n Death [SRO DEATH RELATED] from Surgery Risk Assessment Menu [SROA\n RISK ASSESSMENT]\n - the update of assessment transmissions to reflect the current \n set of NSQIP and CICSP data elements\nInstallation of this patch by the CoreFLS sites will not cause any \n - the update of occurrence categories in the PERIOPERATIVE OCCURRENCE\n CATEGORY file (#136.5)\n \n2. This patch will enhance the lookup by case/assessment number feature\n introduced in patch SR*3*121. Within the Surgery Risk Assessment Menu \n [SROA RISK ASSESSMENT] option, at the "Select Patient" prompt, lookup\n by case/assessment number is allowed by entering the case number\n preceded by #, e.g., enter #6785 to go to case #6785.\nproblems.\n**************************************************************************\n \n1. This patch updates the Surgery Risk Assessment software of the VISTA \n Surgery V. 3.0 application as requested by the National Surgical\n Quality Improvement Program (NSQIP) Executive Committee to bring the\n\n
\n1. NON-CARDIAC PREOP INFORMATION SCREEN, PAGE 1\n in the SURGERY file (#130), the word aneurysectomy is changed to\n aneurysmectomy.\n \n3. REPEAT VENTILATOR W/IN 30 DAYS\n This patch modifies the cardiac assessment creation process to set the \n default value of the REPEAT VENTILATOR W/IN 30 DAYS field (#490) in \n the SURGERY file (#130) to NO if null.\n \n4. CPB STATUS\n This patch updates how the cardiopulmonary bypass status associated \n When editing all the GENERAL items on the first page of the\n with a repeat cardiac surgical procedure outcome is updated and\n transmitted for cardiac assessments.\n Preoperative Information (Enter/Edit) [SROA PREOP DATA] option, the\n last two items are not presented for editing in the same order they\n appear on the main screen. This patch changes the order of presentation\n for editing to match the order on the main screen.\n \n2. SPELLING CORRECTION\n In the field description of the PREVIOUS CARDIAC SURGERY field (#266)\n\n
\nOffice of Information Assurance, Office of Information, Veterans Health\ntime service was provided. Four code sets, (ICD-9-CM, CPT, CPT modifiers,\nDRG) for this project were modified as required under HIPAA legislation to\nbe date-sensitive under the first phase of the project.\n \nAt the time that CSV was developed, a request was made to defer\napplicable text versioning to the next iteration. This deferment of the\nshort and long-text versions from the CSV project makes up the scope of\nthis Code Text Descriptor (CTD) project. This follow-up project, CTD,\nintends to add the functionality of date-sensitive versioning\nfor all applicable code text descriptors for the four code sets, effective\nAdministration (VHA), requested modifications to the VHA Information\nwith all textual changes occurring since October 1, 2002.\n \nThis patch addresses the changes done within the Surgery V. 3.0 software\nin compliance with the CTD project.\n \nThe only noticeable difference users may see will occur when a specific\nCPT, CPT modifier or ICD9 code descriptor changes base on the date of\noperation for the case.\nSystems and Technical Architecture (VistA) Patient Information Management\nSystem (PIMS) package that would allow for the use of multiple versions of\nthe code sets employed in financial transactions. This work was completed\nin 2003 in the Code Set Versioning (CSV) project that was deployed in\nOctober of 2003. CSV included the Health Information Portability and\nAccessibility Act (HIPAA) stipulation that diagnosis and procedure codes\nused for billing purposes must be the codes that were applicable at the\n\n
\nTHIS PATCH WILL ALLOW SURGERY USERS TO ENTER MORE THEN 15 LINE ITEMS FOR\nALL MULTIPLE FIELDS.\n\n
\nThis patch prevents the infinite loop condition described in NOIS \nISW-0904-20140 when the Imaging software attempts to display an Operation\nReport that is not complete.\n\n
\nThis patch corrects the problem reported in NOIS WRJ-1004-10891 in which \nORGAN/SPACE SSI occurrence categories were not appearing on the \nnon-cardiac assessment printout.\n\n
\nThis patch will clean up old variables after the call to EN^DIQ1.\nIt will also replace the Anesthesia Agent Dose that was removed during \nthe install of SR*3*100.\n\n
\n1. LOCKING OF SURGICAL CASES FOR EDITING\n signed while the case or a concurrent case is open for editing. If a\n case is locked and another user attempts to open the same case for\n editing, a message will appear on the screen indicating the name of the\n user that has the case locked. Likewise, if a user attempts to sign \n the Nurse Intraoperative Report or the Anesthesia Report while the \n case is open for editing, a message will appear on the screen \n indicating the name of the user that has the case open for editing.\n \n2. ALLOW CHART PRINT OUTSIDE MAS\n This patch modifies the software responsible for printing\n Patch SR*3*100 introduced locking of a surgical case when a user opens\n electronically signed surgery reports to honor the ALLOW CHART PRINT\n OUTSIDE MAS parameter defined in the TIU DOCUMENT PARAMETERS file\n (#8925.95). If this parameter is set to YES or is null, users will be\n allowed to choose between printing a work copy or a chart copy. If this\n parameter is set to NO, only users in MAS will be allowed to print a\n chart copy and all other users will be allowed to print a work copy\n only.\n \n3. QUARTERLY REPORT ARRAY CLEANUP\n This patch updates the software that generates the Surgery Quarterly \n the case for editing, allowing only one user at a time to edit the same\n Report to kill a variable array that may cause problems when the\n Surgery Quarterly Report is transmitted from multidivisional\n facilities.\n \n4. DATE/TIME OUTPUT TRANSFORM CORRECTION\n This patch corrects the output transform used to display the external \n format of several date/time fields modified by patch SR*3*125. Also, an\n update is made to the way admission, transfer and discharge date/times \n are retrieved and stored for Surgery Risk Assessment.\n \n case. This patch alters how surgical cases are locked and allows\n5. DOCUMENTATION ERROR CORRECTION\n The patch SR*3*100 documentation problem described in NOIS\n PUG-0604-51225 is corrected in documentation distributed with this\n patch.\n \n6. FIELD DESCRIPTION UPDATE\n In the SURGERY file (#130), the CONGESTIVE HEART FAILURE field (#207) \n field description is updated with the 2004 definition.\n \n7. PATIENT NAME/ID ON CARDIAC ASSESSMENT PRINTOUT\n multiple users to open the same case for editing up until the time that\n This patch corrects a problem with the cardiac assessment printout in \n which the patient ID is truncated if the patient's name is more than \n 16 characters in length.\n \n8. NOIS SHR-0904-71756\n This patch corrects the problem described in NOIS SHR-0904-71756 so\n that the printer is closed after printing the assessment upon\n assessment completion.\n \n9. CARDIAC TRANSMISSION UPDATE\n either the Nurse Intraoperative Report or the Anesthesia Report is\n The cardiac assessment transmission is modified by this patch to \n update the formatting of the date of death, if present.\n \n10. NOIS SBY-0904-31547\n Application of this patch prevents the problem described in NOIS\n SBY-0904-31547.\n \n11. ATTENDING REQUIRED BEFORE COMPLETING CASE\n To prevent possible cosigner problems with the Operation Report and \n the Procedure Report (Non-OR), this patch will require the attending \n signed. When a user enters the function to sign either report and after\n surgeon/provider to be entered before the case can be completed. \n \n When a user enters the TIME PAT OUT OR field (#.232) in the SURGERY \n file (#130), to complete a surgical case, if the ATTEND SURGEON field \n (#.164) is blank, the software will prompt the user to enter the \n attending surgeon. For non-OR procedures, when a user enters the TIME \n PROCEDURE ENDED field (#122), if the ATTEND PROVIDER field (#124) is \n blank, the software will prompt the user to enter the attending \n provider.\n \n either report is signed, the software will again allow only one user at\n If the SURGICAL RESIDENTS (Y/N) field (#33) in the SURGERY SITE \n PARAMETERS file (#133) is set to NO, when a surgeon is entered in the \n SURGEON field (#.14) in the SURGERY file (#130), the software will \n enter the surgeon in the ATTEND SURGEON field (#.164). For non-OR \n procedures, when the provider is entered in the PROVIDER field (#123), \n the software will enter the provider in the ATTEND PROVIDER field \n (#124).\n a time to open the case for editing. Neither report for a case can be\n\n
\nVariables not printing correctly in Risk Assessment report\n\n
\n1. This patch fixes the problem reported in NOIS BAY-0105-30051. The \n PREOP DATA] on the menu Non-Cardiac Assessment Information \n (Enter/Edit) [SROA ENTER/EDIT] on the menu Surgery Risk Assessment \n Menu [SROA RISK ASSESSMENT] to edit items under GENERAL on page 1, \n entering a caret (^) to exit at one of the sub-item prompts does \n not work correctly. This patch corrects this problem.\n problem was introduced by patch SR*3*134.\n \n2. This patch fixes the problem reported in NOIS CLA-0105-20215. This \n problem occurs only at facilities with multiple divisions defined in\n the SURGERY SITE PARAMETERS file (#133) with all but one division \n flagged as inactive.\n \n3. When using the option Preoperative Information (Enter/Edit) [SROA \n\n
\nThis patch enables the user to delete surgery images.\n\n
\n1. In support of the Surgical Infection Project (SIP), this patch \n Medication Comments\n \n2. The Morbidity & Mortality Reports [SROMM] option and the M&M \n Verification Report [SRO M&M VERIFICATION REPORT] option are \n modified to display the sepsis category for SYSTEMIC SEPSIS\n occurrences.\n \n3. This patch modifies the DYSPNEA field (#325) in the SURGERY file \n (#130) changing MINIMAL EXERTION in the set of choices to MODERATE \n EXERTION. This change makes the set of codes agree with the field \n modifies the Nurse Intraoperative Report [SRONRPT] option to display\n description.\n and to allow editing of the following additional information related\n to medications:\n Time Administered\n Route\n Dosage\n Ordered By\n Administered By\n\n
\nCLINICAL INDICATOR DATA CAPTURE - SURGERY\n\n
\nIn Remedy HD 94190, when using the Patient Demographics (Enter/Edit) [SROA\nDEMOGRAPHICS] option, an undefined error occurs if the length of the race\ndata is found to be more than 72 characters.\n\n
\n1. For CPRS-R (ReHosting), a cache of patient data will be maintained for\n (#.12) in the SURGERY file (#130). The field is renamed "PREOP HAIR\n CLIPPING BY" and the title and description of this field are updated.\n The field titles on the Nurse Intraoperative Report are changed as\n well.\n the duration of his/her inpatient stay (or outpatient visit) for ease\n of searching and sorting within the new Java client; rather than making\n frequent calls back to each application's database. To this end, this\n patch contains modifications that will allow the Surgery software to\n update the CPRS-R (ReHosting) cache of patient data when a case is\n created or edited.\n \n2. This patch updates the data dictionary of the PREOP SHAVE BY field\n\n
\nTHIS PATCH WILL INSERT "N SRX" TO THE BEGINNING OF SEVERAL SURGERY\nFILE (#130) INPUT TRANSFORMS.\n\n
\nTHIS PATCH CORRECTS FOUR ISSUES RELATED TO CIDC.\n\n
\nThis patch modifies the Blood Product Verification [SR BLOOD PRODUCT \nVERIFICATION] option to reference the VistA Blood Establishment Computer \nSoftware (VBECS) if installed. This change allows the option to maintain \nits current functionality before and after VBECS is installed.\n\n
\nThis is Surgery patch SR*3*67.\n\n
\nAs existing pharmacy software modules are being re-engineered through\n'behind-the-scenes' process to enable exchange of medication data.\nnew development and the purchase of commercial off-the-shelf products\n(COTS). Transition to the new Pharmacy Re-Engineered system eliminates the\nVistA Pharmacy files currently referenced. Therefore, all Surgery existing\nreferences (direct global reads/writes, VA FileMan reads/writes) to all\npharmacy application files must be replaced with Application Programmer\nInterfaces (APIs).\n \nThis enhancement does not entail any user functionality change, only a\n\n
\nThis patch is a follow up patch for SR*3*151. It fixes the undefined\nerror reported by Dublin when using the Anesthesia Provider Report\n[SROADOC] option.\n\n
\nThis patch is part of the Patient Financial Services System (PFSS) project.\nsystem. The project consists of the implementation of the billing\n o Quarterly Report - Surgical Service [SRO QUARTERLY REPORT] option\n o Report of Missing Quarterly Report Data [SROQ MISSING DATA] option\n Note: The Other CPT Codes no longer affect this report and \n references to Other CPT Codes are removed. The display of "I" in \n the footer of this report is removed.\n o Annual Report of Non-O.R. Procedures [SRONOP-ANNUAL] option\n o List of Invasive Diagnostic Procedures [SROQIDP] option\n - The following Surgery reports and options are modified to remove CPT \n and/or ICD codes from the display.\n o Update Status of Returns within 30 Days [SRO UPDATE RETURNS] option\nreplacement system, business process improvements, and enhancements to\n o Update Operations as Unrelated/Related to Death [SRO DEATH RELATED]\n option\n o Non-OR Procedure Information [SR NON-OR INFO] option\n o Deaths Within 30 Days of Surgery [SROQD] option\n o Admissions Within 14 Days of Outpatient Surgery [SROQADM] option\n o List of Operations Included on Quarterly Report [SROQ LIST OPS]\n option\n \n3. Modified Risk Assessment Options\n - Surgery case CPT and/or ICD codes used in the following options are \nVistA to support integration with the COTS billing replacement system.\n displayed from the SURGERY PROCEDURE/DIAGNOSIS CODES file (#136):\n o Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] option\n o List of Surgery Risk Assessments [SROA ASSESSMENT LIST] option \n o Exclusion Criteria (Enter/Edit) [SR NO ASSESSMENT REASON] option\n Note: The new CPT code fields will not be editable from this\n option.\n o Update 1-Liner Case [SROA ONE-LINER UPDATE] option\n Note: The new CPT code fields will not be editable from this\n option.\n o Queue Assessment Transmissions [SROA TRANSMIT ASSESSMENTS] option\nSignificant changes to VistA legacy systems and ancillary packages are\n - In the following options CPT codes are removed from the screen\n headings:\n o Preoperative Information (Enter/Edit) [SROA PREOP DATA] option \n o Laboratory Test Results (Enter/Edit) [SROA LAB] option\n o Operation Information (Enter/Edit) [SROA OPERATION DATA] option\n Note: The CPT code and Postoperative Diagnosis fields will not be \n editable from this option. \n o Patient Demographics (Enter/Edit) [SROA DEMOGRAPHICS] option\n o Intraoperative Occurrences (Enter/Edit) [SRO INTRAOP COMP] option\n o Postoperative Occurrences (Enter/Edit) [SRO POSTOP COMP] option\nnecessary.\n o Clinical Information (Enter/Edit) [SROA CLINICAL INFORMATION]\n option\n o Laboratory Test Results (Enter/Edit) [SROA LAB-CARDIAC] option\n o Enter Cardiac Catheterization & Angiographic Data [SROA \n CATHETERIZATION] option \n o Operative Risk Summary Data (Enter/Edit) [SROA CARDIAC OPERATIVE \n RISK] option\n Note: The CPT code fields will not be editable from this option.\n o Cardiac Procedures Operative Data (Enter/Edit) [SROA CARDIAC \n PROCEDURES] option\n \n o Outcome Information (Enter/Edit) [SROA CARDIAC-OUTCOMES] option\n o Resource Data [SROA CARDIAC RESOURCE] option\n - The Update Assessment Status to 'COMPLETE' [SROA COMPLETE ASSESSMENT]\n option is modified to remove the ability to edit CPT and ICD codes \n from this option.\n \n4. Functions that are currently part of the Surgery Nightly Cleanup and \n Updates [SRTASK-NIGHT] option are modified as follows:\n - Store Operation Times function uses the CPT code fields in the \n SURGERY PROCEDURE/DIAGNOSIS CODES file (#136).\nSome of the PFSS software components are not operational until the PFSS \n - File Surgery Data in PCE function is removed.\n \n5. The Surgery to PCE interface is modified to send coding data from the \n SURGERY PROCEDURE/DIAGNOSIS CODES file (#136). The interface now passes\n data to PCE in real time when the coder completes the coding process\n for a case. After a case is filed with PCE, if certain data passed to \n PCE is changed within the Surgery software, the Surgery to PCE\n interface sends an update to PCE immediately. ICD coding related data \n is updated through the Update/Verify Procedure/Diagnosis Codes\n [SRCODING EDIT] option.\nOn/Off Switch, distributed with patch IB*2*260, is set to "ON". The ability\nfor the local site to set the switch to "ON" will be provided at the\nappropriate time with the release of a subsequent Integrated Billing patch.\nPFSS patches are being released on various schedules. Some patch\n \nFor more information about the PFSS project, review the documentation \naccompanying this patch and refer to the following website: \nhttp://vista.domain.ext/billreplace/\n \nFeatures of patch SR*3*142 are listed below:\n \n1. Modified Surgery Coding Option\n Coders currently use the Update/Verify Procedure/Diagnosis Codes \n [SRCODING EDIT] option, which updates coded data directly in the \nfunctionality will not be active until a new PFSS switch is activated\n SURGERY file (#130). However, the SURGERY file (#130) does not\n currently make a distinction between procedure and diagnosis data\n entered by clinicians and that entered by coders. Today, coding a\n surgical case impacts the clinical data for the patient and causes an\n addendum to be generated because each code is directly associated with\n a free-text procedure or diagnosis entry. This patch separates final\n coded procedures and diagnoses from the clinically captured procedures\n and diagnoses.\n \n A new file, the SURGERY PROCEDURE/DIAGNOSIS CODES file (#136), is\nduring final implementation. PFSS will initially be implemented at select\n created to store coded procedure and coded diagnosis data for a Surgery\n case. Data entered into this file will be the new source coding data\n sent by the Surgery package to PCE. In the SURGERY file (#130), the\n existing PRINCIPAL CPT Code field (#27), PRIN DIAGNOSIS CODE field \n (#66), OTHER PROCEDURE CPT CODE field (#3 of sub-file #130.16) and ICD\n DIAGNOSIS CODE field (#3 of sub-file #130.18) are modified to include\n the word "PLANNED" in the field labels and titles.\n \n The Update/Verify Procedure/Diagnosis Codes [SRCODING EDIT] option is \n modified to allow entry of final billing Current Procedural \npilot sites ONLY.\n Terminology (CPT) codes for surgical procedures and International\n Classification of Disease (ICD) diagnosis codes in the SURGERY\n PROCEDURE/DIAGNOSIS CODES file (#136).\n \n Modified features of the Update/Verify Procedure/Diagnosis Codes\n [SRCODING EDIT] option are listed below:\n - Upon record creation for a case in the SURGERY PROCEDURE/DIAGNOSIS\n CODES file (#136), the record will be auto-populated with clinician\n entered coding data, if any, from the SURGERY file (#130).\n - A principal ICD code and a principal CPT code are initial\n \n requirements for coding a surgical case. \n - An unlimited number of ICD codes may be entered for other diagnoses\n and an unlimited number of CPT codes may be entered for other\n procedures performed.\n - Each CPT code entered must be assigned the associated ICD code(s)\n related to the procedure performed.\n - An unlimited number of CPT modifiers may be entered for each CPT code\n entered.\n - For every ICD code entered, the following questions must be answered\n as appropriate for the patient based upon enrollment indicators:\nThe purpose of the PFSS project is to prepare the Veterans Health \n o Treatment related to Service Connected condition?\n o Treatment related to Agent Orange Exposure?\n o Treatment related to Ionizing Radiation Exposure?\n o Treatment related to Environmental Contaminant Exposure?\n o Treatment related to Military Sexual Trauma?\n o Treatment related to Head and/or Neck Cancer?\n o Treatment related to Combat?\n - Upon completion of coding for a case, the coder is allowed to mark\n the record as complete and to send the record immediately to PCE.\n - Before allowing the record to be marked as complete, the option\nInformation Systems and Technology Architecture (VistA) environment for the\n checks to see if a specific code, 065.0 CRIMEAN HEMORRHAGIC FEV, is\n entered as a diagnosis code. If it is entered, the software prompts\n the user to make sure that the code is correct for the case. This\n check is added to prevent the inadvertent assignment of code 065.0\n when "CHF" is entered for the Principal or Other ICD Diagnosis\n codes.\n \n2. Modified Surgery Reports and Other Options\n - The following Surgery reports and options as modified to use the\n coder entered CPT and/or ICD codes from the SURGERY \nimplementation of a commercial off-the-shelf (COTS) billing replacement\n PROCEDURE/DIAGNOSIS CODES file (#136):\n o Cumulative Report of CPT Codes [SROACCT] option\n o Report of CPT Coding Accuracy [SR CPT ACCURACY] option\n o List Completed Cases Missing CPT Codes [SRSCPT] option\n Note: The option descriptions are updated to read "The List\n Completed Cases Missing CPT Codes option generates a report of\n completed cases that are missing the Principal CPT code for a\n specified date range."\n o Annual Report of Surgical Procedures [SROARSP] option\n o PCE Filing Status Report [SRO PCE STATUS] option\n\n
\n1. At many sites the Risk Assessment Nurse Reviewers are involved with the\n [SROA ENTER/EDIT] and Cardiac Risk Assessment Information (Enter/Edit) \n [SROA CARDIAC ENTER/EDIT] menus.\n o The Alert Coder Regarding Coding Issues [SROA CODE ISSUE] option will\n not check the PFSS On/Off switch.\n o The Alert Coder Regarding Coding Issues [SROA CODE ISSUE] option will\n display basic surgery case information including Patient, Case Number,\n Surgery Date, and Procedure.\n o The Alert Coder Regarding Coding Issues [SROA CODE ISSUE] option will\n display the following coded information: the PRINCIPAL CPT CODE, OTHER\n CPT CODE, and PRINCIPAL DIAGNOSIS CODE.\nHealth Information Management Systems (HIMS) staff in determining the\n o The Alert Coder Regarding Coding Issues [SROA CODE ISSUE] option will\n allow the Reviewer to enter a free text comment field to send coding\n concerns to the coder, as well as to members of a predefined mail group\n identified in the CODE ISSUE MAIL GROUP parameter.\n o Values for the CODING COMPLETED BY field (#.01) of the CODING \n COMPLETED BY multiple (#136.011) of the SURGERY PROCEDURE/DIAGNOSIS\n CODES file (#136) or the CODE ISSUE MAIL GROUP will be present when the\n user selects the Alert Coder Regarding Coding Issues [SROA CODE ISSUE]\n option. If neither are valued, the user will be notified that the\n message cannot be sent without one of these two items defined.\nfinal codes for a Surgery case. An Alert Coder Option will allow the Risk\n o The CODE ISSUE MAIL GROUP field (#43) is added in the SURGERY SITE\n PARAMETERS file (#133) to allow the site to create a designated mail\n group for the Alert Coder Regarding Coding Issues [SROA CODE ISSUE]\n option.\n o The Surgery Site Parameters (Enter/Edit) [SROPARAM] option within\n the Surgery Package Management Menu [SRO PACKAGE MANAGEMENT] option is \n modified to allow entry and editing of the new CODE ISSUE MAIL GROUP.\n \n2. When creating a request from a waiting list entry, the Surgery screen \nserver incorrectly displays "SCHEDULING" in the screen header. This patch \nAssessment Nurse Reviewer to alert the coder if there is a question on the\nmakes a modification to display "REQUEST" instead.\n \n3. This patch corrects problems with the two trigger cross references that\nwere added to the SITE field (#.01) of the SURGERY SITE PARAMETERS file\n(#133) by patch SR*3*150.\n \nNote: This patch includes a post-installation process that updates each\nentry in the SURGERY SITE PARAMETERS file (#133) as follows:\n - UPDATES TO PCE field (#18) is set to ALL CASES.\n - ASK CLASSIFICATION QUESTIONS field (#19) is set to YES. \nCurrent Procedural Terminology (CPT) or International Classification of\nDiseases (ICD) codes on a Surgery case.\n \n o The new Alert Coder Regarding Coding Issues [SROA CODE ISSUE] option\n will appear on both the Non-Cardiac Assessment Information (Enter/Edit)\n\n
\nProject 112/SHAD (Shipboard Hazard and Defense) is a new environmental \n \n The Project 112/SHAD information will be forwarded to Patient Care \n Encounter (PCE) as part of the normal case coding activities.\n \n2. This patch will prevent the PRIN PRE-OP ICD DIAGNOSIS CODE field\n (#32.5) of the SURGERY file (#130) from being sent to PCE.\n \n3. This patch adds the Alert Coder Regarding Coding Issues [SROA CODE \n ISSUE] option to the Surgery Risk Assessment Menu [SROA RISK \n ASSESSMENT] option.\nindicator added to VistA as part of the Enrollment System Redesign (ESR) \nproject.\n \n1. This patch provides the ability to enter and edit Project 112/SHAD\n Environmental Indicator information in the Surgery package. The \n patient's Project 112/SHAD enrollment status is displayed when creating\n or editing a surgical case, and the user will be prompted to answer the\n Project 112/SHAD questions with "yes" or "no".\n\n
\nThis patch is part of the Patient Financial Services System (PFSS) \nreplacement system. The project consists of the implementation of the \nbilling replacement system, business process improvements, and \nenhancements to VistA to support integration with the COTS billing \nreplacement system. Significant changes to VistA legacy systems and \nancillary packages are necessary.\n \nSome of the PFSS software components are not operational until the PFSS \nOn/Off Switch, distributed with patch IB*2*260, is set to "ON". The \nability for the local site to set the switch to "ON" will be provided at \nthe appropriate time with the release of a subsequent Integrated Billing \nproject. PFSS patches are being released on various schedules. Some patch\npatch.\n \nFor more information about the PFSS project, review the documentation \naccompanying this patch and refer to the following website: \nhttp://vista.domain.ext/billreplace/\n \nFeatures of patch SR*3*144 are listed below:\n \n1. The VistA Surgery software will be enhanced to request an account\n number for every Surgery Request Consult. This activity will support\nfunctionality will not be active until a new PFSS switch is activated\n the Revenue Office's need to pre-certify with insurance companies the\n requested Surgery. A national guideline will be issued defining the\n minimum format for creating a Surgery Request Consult within the VistA\n Consults package that will collect the data required by PFSS. The\n Surgery Request Consult will not create a Surgery case. This guideline\n does not require that sites use the Consults package for creating\n Surgery requests. Sites using VistA Surgery Request options can\n continue to use that approach.\n \n VistA Surgery will be enhanced to also request a PFSS ACCOUNT\nduring final implementation. PFSS will initially be implemented at select\n REFERENCE, and it will be stored in the PFSS ACCOUNT REFERENCE field\n (#500) of the SURGERY file (#130). The association to a PFSS ACCOUNT\n REFERENCE is obtained when the Surgery case is created and is sent to\n the PATIENT CARE ENCOUNTER (PCE) application upon completion of coding.\n \n2. This patch changes the List Completed Cases Missing CPT Codes [SRSCPT]\n option to list only those completed cases that do not have a final CPT \n code entered in the PRINCIPAL PROCEDURE CODE field (#.02) of the\n SURGERY PROCEDURE/DIAGNOSIS CODES file (#136).\npilot sites ONLY.\n \nThe purpose of the PFSS project is to prepare the Veterans Health \nInformation Systems and Technology Architecture (VistA) environment for \nthe implementation of a Commercial Off-The-Shelf (COTS) billing \n\n
\n1. The Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] option for\n Non-Cardiac assessments is corrected to display the PRIN POSTOP\n DIAGNOSIS CODE field (#.03) stored in the SURGERY PROCEDURE/DIAGNOSIS\n CODES file (#136).\n \n2. The Print a Surgery Risk Assessment [SROA PRINT ASSESSMENT] option for\n Non-Cardiac assessments is corrected to display the PRINCIPAL PROCEDURE\n CODE field (#.02) stored in the SURGERY PROCEDURE/DIAGNOSIS CODES file\n (#136) when referencing CPT Codes for Returns within 30 Days.\n\n
\nAn undefined error occurs when two users attempt to access the \nsame record at the same time. One user is creating a surgery request and \nthe other is attempting to delete that same user request.\n\n
\nAfter installing patch SR*3*144, if the SURGICAL RESIDENTS (Y/N) field \ncorrectly. This patch includes a post-installation process that will check\neach surgical case and correct any textual entries that may exist in the\nATTEND SURG field (#.164) in the SURGERY file (#130).\n(#33) in the SURGERY SITE PARAMETERS file (#133) is NO, surgical cases for\nthat division created using the Schedule Unrequested Operations [SROSRES]\noption will contain the textual name of the attending surgeon instead of \nthe pointer value in the ATTEND SURG field (#.164) in the SURGERY file\n(#130).\n \nThis patch modifies the Schedule Unrequested Operations [SROSRES] option \nso that the ATTEND SURG field (#.164) in the SURGERY file (#130) is set\n\n
\nhis patch updates the Surgery Risk Assessment software of the Veterans\n \n o Modification to some of the user entries of fields that allow text to\n be entered to accept lower case or all CAPS\n - The NUM OF PRIOR HEART SURGERIES field (#352) is modified to allow the\n entry of lowercase letter "N" to represent "0 - NONE". Any existing\n N's will be converted to '0' for NONE by he post install routine.\n - The ESTIMATE OF MORTALITY field (#364) is modified to allow the entry\n of lowercase letter "ns" to represent "NO STUDY".\n \n o Modifications to the List of Surgery Risk Assessments [SROA ASSESSMENT\n LIST] option\nNOTE: All fields listed below are in the SURGERY file (#130) unless\n - Each report is modified to display the final CPT codes from the case\n coding record in the SURGERY PROCEDURE/DIAGNOSIS CODES file (#136).\n - List of 1-Liner Cases Missing Information (list #8) is added.\n \nGeneral Surgery Items\n---------------------\n o The PREOP HAIR CLIPPING BY field (#.12) is renamed HAIR REMOVAL BY.\n \n o The HAIR REMOVAL METHOD field (#506) and the HAIR REMOVAL COMMENTS\n field (#508) are added to the Operation Startup [SROMEN-START] option\notherwise indicated.\n and the Operation (Short Screen) [SROMEN-OUT] option. Those two fields\n and the HAIR REMOVAL BY field (#.12) are added to the Nurse\n Intraoperative Report and became a mandatory documentation field to\n satisfy the record review process for quality measurement purposes.\n \nCardiac Risk Assessment Modifications\n-------------------------------------\n o Modifications to the Clinical Information (Enter/Edit) [SROA CLINICAL\n INFORMATION] option\n - The software is modified to auto-populate the HEIGHT field (#236) and\n the WEIGHT field (#237) as documented in the Vitals software.\nHealth Information Systems and Technology Architecture (VistA)\n - The Current Smoker item under this option is modified to reference to\n the new CURRENT SMOKER (CARDIAC) field (#510) instead of the old field\n CURRENT SMOKER field (#202), which will be utilized by the NSQIP\n options.\n \n o Modifications to the Laboratory Test Results (Enter/Edit) [SROA\n LAB-CARDIAC] option\n - The HEMOGLOBIN A1C field (#504) and the HEMOGLOBIN A1C, DATE field\n (#504.1) are added to the list of preoperative lab results.\n - The software is modified to use a date range of 1000 days prior to the\nSurgery application as requested by the Executive Board of the National\n date of operation when searching for the most recent preoperative lab\n test result for the HDL (CARDIAC) field (#457), the LDL (CARDIAC)\n field (#461), the TOTAL CHOLESTEROL (CARDIAC) field (#462), the SERUM\n TRIGLYCERIDE (CARDIAC) field (#458), and the HEMOGLOBIN A1C field\n (#504).\n \n o The Enter Cardiac Catheterization & Angiographic Data [SROA CARDIAC\n PROCEDURES] option is modified to allow all fields to be\n auto-populated with 'NS' (NO STUDY) when 'NS' is entered in the\n PROCEDURE TYPE field (#476).\nSurgical Quality Improvement Program (NSQIP) and by the Cardiac Surgery\n \n o Modifications to the Cardiac Procedures Operative Data (Enter/Edit)\n [SROA CARDIAC PROCEDURES] option\n - The GREAT VESSEL REPAIR (Y/N) field (#372) is moved to screen #1 under\n this option as item #20.\n - The ENDOVASCULAR REPAIR field (#505) is added in screen #1 as item\n #21.\n - The OTHER CT PROCEDURE field (#484) in the first screen is now\n replaced by the OTHER CARDIAC PROCEDURES (Y/N) field (#502). If this\n field value is "YES" the software will prompt the user for the OTHER\nConsultants Board of the Continuous Improvement in Cardiac Surgery\n CARDIAC PROCEDURES-LIST field (#484).\n - The OTHER NON-CT PROCEDURES field (#491) is removed from the second\n screen and a blank line is added before "Other Operative Data\n details" header.\n - The software is modified so that entering "N" for the VALVE REPAIR\n field (#370) shall result in "5. None". The existing N's will be\n converted to '5' upon patch installation.\n - This option is updated to reference the new MAZE PROCEDURE field\n (#512) as item 13 in the first data entry screen.\n \nProgram (CICSP). These updates include the addition of new data fields,\n o A new occurrence category REPEAT VENTILATOR SUPPORT W/IN 30 DAYS is\n created in the PERIOPERATIVE OCCURRENCE CATEGORY file (#136.5). This\n occurrence category will be selectable only for cardiac assessed cases.\n \n o The following fields on the Resource Data [SROA CARDIAC RESOURCE]\n option are modified to assume a default of "past date" when no year is\n specified:\n - ESTIMATE OF MORTALITY, DATE field (#364.1)\n - D/T PATIENT EXTUBATED field (#470)\n - D/T PATIENT DISCH FROM ICU field (#471)\nchanges to existing data fields, changes to data entry screens, changes\n \n o This patch will allow the retransmission of a cardiac risk assessment.\n \nNon-Cardiac Assessment Modifications\n------------------------------------\n o Modifications to the Preoperative Information (Enter/Edit) [SROA PREOP\n DATA] option\n - The software is modified to auto-populate the HEIGHT field (#236) and\n the WEIGHT field (#237) as documented in the Vitals software.\n - The PREGNANCY field (#269) is added to the NUTRITIONAL/IMMUNE/OTHER\nto reports used in Surgery Risk Assessment management process and changes\n section.\n \n o Modifications to the Laboratory Test Results (Enter/Edit) [SROA LAB]\n option\n - The PREOPERATIVE ANION GAP field (#444) and the PREOP ANION GAP, DATE\n field (#444.1) are added to the list of preoperative lab results.\n - The HIGHEST ANION GAP field (#445) and the HIGH ANION GAP, DATE field\n (445.1) are added to the list of postoperative lab results.\n \n o The Operation Information (Enter/Edit) [SROA OPERATION DATA] option is\nto the Surgery Risk Assessment transmissions.\n modified to add the INTRAOP DISSEMINATED CANCER field (#443).\n \nOther Risk Assessment Modifications\n-----------------------------------\n o The Print a Surgery Risk Assessment [SROA Print Assessment] option is\n modified to include the new data elements.\n \n o The transmissions to the national databases are modified to include the\n new fields.\n \n\n
\nThe DHCP Surgery package is used to enter/edit and display information\nrelated to the Surgical Service. It will track surgical cases, provide\nuseful management reports, and produce the necessary documentation for\nall surgical cases.\n \n\n
\nDependency:\n1996 for the National Cancer Database. The Annual Call for Data extract\nfor 1996 will also include the Soft Tissue Sarcoma and Thyroid Patient\nCare Evaluations (PCE)s.\nThe following modifications have been made.\n \n 1) This option has been enhanced to include the 1996 \n Soft Tissue Sarcoma and Thyroid PCEs.\n 2) The patch includes an update to the data dictionary and data for\n file ONCOLOGY DATA EXTRACT FORMAT (#160.16).\n 3) The patch includes a new data dictionary and data for file\n===========\n ONCOLOGY PCE EXTRACT FORMAT (#160.17).\n 4) File FORMS/INSTRUCTIONS (#160.2) has been modified \n to reflect the new data help instructions displayed/printed\n when creating the ACoS data disk.\n \nTest Sites\n==========\n \nAlpha: \nWashington D. C.\n PATCH ONC*2.11*13 MUST BE INSTALLED PRIOR TO INSTALLING THIS PATCH.\n \nBeta:\nBoston, MA\nBuffalo, NY\nWashington D. C.\n \nRoutine\nSummary:\n================\nThe following routines are included in this patch. The second line of \n \nthese routines should look like:\n \n <tab>;;2.11;ONCOLOGY;**[patch list]**;Mar 07, 1995\n \n CHECK^XTSUMBLD results:\n \nRoutine Name Before Patch After Patch Patch List\n============ ============ =========== ==========\n ONCACD1 3718409 6115810 9,12,14\n ONCACDU1 3701766 4046936 12,14\nDescription:\n ONCODIS 1041660 1041724 6,7,9,10,11,12,13,14\n ONCPRE14 N/A 24247 14\n \n \nInstallation Instruction:\n=========================\nThis Patch is created with Kernel V8 KIDS. Follow these instructions:\n \n1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build \n onto your system.\n===========\n \n2) On the KIDS menu, under the 'Installation' menu, use the \n option 'Verify Checksum in Transport Global' and verify that all \n routines have the correct checksums.\n \n3) From the 'Installation' Menu of KIDS, use the option\n \n 'Install Package(s)'. Select the package 'ONC*2.11*14' and proceed\n with install.\n \n \n4) If you are a NON-DSM site, move the routines to the other servers.\n \n5) On a mapped system, rebuild your map set.\n \n6) Delete the pre-init routine ONCPRE14. \nThis patch will enhance Oncology 2.11 to support the Commission on\nCancers 1996 Annual Call for Data extract for the years 1986, 1991 and\n\n
\nYK2 patch for ONCOLOGY 2.11\n\n
\nNAACR Annual Call for Data for the years 1985, 1990, 1995. This patch is\nto update the NAACR Annual Call for Data to the 1995 Data extract. \n\n
\nCorrection to laterality field. Laterality will except 9 as valid input.\n\n
\nNorth American Association of Central Cancer Registries (NAACCR) Annual\nCall for Data and State Data for the years 1985, 1990, 1995. This patch\nis to update the NAACCR Annual Call for Data and the State Data to the\n1995 Data extract.\n\n
\nThis is a maintenance release that adds updated SEER codes effective 1/1/94.\n\n
\nOncology version 2.2 and other fixes.\n\n
\nAddress-Country/State extract and other fixes.\n\n
\nEmergency patch for TNM Clinical and Pathologic data fields. Primaries \nwith a BLANK TNM data fields are included in RQRS Extract.\n\n
\nENTERING BUILD IN PACKAGE FILE WITHOUT INSTALLING\n\n
\nThe Oncology package, which is known as the Tumor Registry Automation\nand decoding ICD-O and SNOMED nomenclatures. \nProgram (TRAP), is a comprehensive program for automating the hospital\ntumor registry. It is unique among tumor registry programs in supporting\nall requirements of the American College of Surgeons and the National\nCancer Institute's Surveillance, Epidemiology, and End Results (SEER) \nProgram and providing interactive edits for all data elements. It features \nflexibility in accommodating expanded data sets for medical oncology,\nradiation therapy, and surgery, and for satisfying local needs and special\nresearch studies. It also features a transparent approach for encoding\n\n
\nThis patch fixes several problems: \nstuffed in the field. This was reported in the FB VENDOR UPDATE template\nhaving users on the system while installing this patch are that users\nediting records will get a 'source routine edited' error, the edits will\nbe lost and records may be left in an inconsistent state. Note that most\nof these routines are heavily used in DHCP applications.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \nin file 161.2. This template needs to be recompiled after this patch is\n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*19 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to \nother CPUs?'. \n Then enter the names of your other Compute and Print server(s). \ninstalled. (DIEZ2) \n NOTE: You will then see the following message: \n TASKMAN is not running. You must run the routine XPDCPU in the \nproduction UCI for each of the VOLUME SETS you have listed once the \ninstallation starts!! \n \n 9. MSM Sites - After the installation begins, you will be prompted to\nenter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\neach one, you do the following:\n \n a) >D ^XUP This will set up the programming environment. \n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*19 \n ==========\nThe installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your map \nset. \n3. On a range read, an input that is totally outside of the range is \n \n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 12. Enable user's login. \naccepted. For example, using a DIR call like this, S DIR(0)="L^1:4", if\nthe user typed in 5-6, Y comes back as 4. (DIR3)\n \n4. With the release of V21, set-of-code processing within ^DIE was\nenhanced to make input to set-of-code single-valued-fields case\n \ninsensitive. This change however caused the syntax\n'field///external_code' to fail when the 'external_code' is an exact match\nto a code but is also a partial match to another code. Prior to V21, the\nfirst match to 'external_code' was selected. This patch fixes this\nproblem. The related nois is ISW-0895-21058. There are no known\ntemplates that needed to be recompiled at this time. (DIED, DIEZ1, DIR1)\n \n5. This patch will make set-of-code ^DIR calls case insensitive unless an\n'X' flag is passed. Prior to the patch, an 'M' flag was required to be \npassed to allow case insensitivity. This patch will no longer require an\n1. When an audit flag on a field is EDITED OR DELETED, the field gets \n'M' flag to be passed. (DIR1)\n \n6. Suppose a DIE call is made with DIE("NO^")="", and the template\nspecified in DR is compiled.\n \n a. If the user timed out, FileMan behaved as if an "^" was entered, \n printed the message 'EXIT NOT ALLOWED ??' and reprompted. In \n effect, then, the process would never timeout. This change makes \n FileMan exit on timeout. \n \naudited when there is no pre-existing data and the field is being stuffed \n b. If the compiled template contained the .01 field of a multiple, \n and that .01 field was the first field in the multiple defined in the \n template, if the user entered an ^, FileMan would correctly print the \n message 'EXIT NOT ALLOWED ??' but would take the user to the next \n field defined in the template. This change makes FileMan reprompt for\n a value for the .01 field.\n \n The related NOIS is BRK-0796-10872.\n (DIE17)\n \nusing /// or //// syntax. This patch corrects the problem by not auditing \n7. Back out change to DICN made in patch DI*21*12 (described as item #2\n in that patch). That change inadvertently made a response in a\n YN^DICN call required. (DICN)\n \nRoutine Summary: \n================\n \nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \nfields with no pre-existing data and the audit flag is EDITED OR DELETED.\n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DICN 7484792 7476631 12,19\n DIE 9505864 9523669 19\n DIE17 6822014 6896286 19\n DIED 6344409 6449521 1,13,19\nThis problem was reported by nois ISA-0593-10022. (DIE, DIEZ2) \n DIEZ1 7657833 7774560 1,13,19\n DIEZ2 7389106 7311012 19\n DIR1 7726690 7765832 6,13,19\n DIR3 3582829 3670507 19\n \nInstallation Instructions: \n==========================\n \n 1. The routines DICN, DIE, DIED, DIE17, DIR1, DIR3 are usually mapped\non systems that allow mapping, AXP sites will need to disable mapping for\n \nthese routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system. The environment check\nroutine DIENV will run automatically.\n \n DIENV is sent in order to prevent the inadvertent queueing of the\ninstallation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\n2. When a compiled input template contains the syntax '////@', the '@' is\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users from login into the system. The consequence of\n\n\nThis patch makes the following changes: \n If you Enter/Edit the entries in this file and enter ^LOOP at the\n S:'$D(var) var=... or\n D:'... or\n X:'...\n \nand in the file, there was a field with a name that started with the\nletter before the colon (:), an infinite loop would occur. This patch\ncorrects this problem. (DICOMPX)\n \n6. If the cross references on a file are compiled, and the file contains\ntrigger-type cross references, FileMan could break the routine within a do\n'Select NAME:' prompt you can get a hard error.\nblock structure, so that the first line of the next routine starts with a\n.line. For example, the last few lines of one routine could be:\n \n I X'="" D\n .N DIK,DIV,DIU,DIN\n END G ^zzzz2\n \nand the first few lines of the next routine could be:\n \n zzzz2 ; COMPILED XREF FOR FILE #xxxxx ; 10/30/96\n \n ; \n .K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(1)=$S($D(^DIZ(xxxxx,D0,3)):\n ^(3),1:"")S X=$P(Y(1),U,2),X=X S DIU=X K Y X ^DD(xxxxx,2,1,\n 12,2.1) X ^DD(xxxxx,2,1,12,2.4)\n ...\n \nThis patch ensure that routines are not broken within do block structures.\n(DIKZ)\n \n7. This patch also fixes several problems with %DT and time input:\n NOIS: KAN-0396-41540\n \n a. If only numbers are entered in the date and/or time position, like\n 9999999999999999999999999999999, an illegal number error could\n result.\n \n b. Even with %DT["N", %DT was accepting noncanonic numbers (numbers\n with a leading 0). So, 090196 was accepted, but 100196 was not.\n \n c. If only a time is input, and the AM/PM designation on the time\n contained punctuation (like 2:00 A.M.), the input was rejected.\n (DIA2)\n \n d. A single 0 in the minutes or seconds position of the time, could\n cause the time to be interpreted incorrectly. For example, 01:0\n was interpreted as 10:00 am, and T@01:01:0 was interpreted as\n 10:00:10 am. With this fix, time with a single 0 in the minutes or\n seconds position is rejected.\n \n e. Time with hours of 0 or 00 were not getting interpreted\n correctly. For example:\n Intepreted as\n \n =============\n Input Before fix After fix\n ===== ========== =========\n %DT'["S" [0]0:01:03 => 01:03 rejected\n [0]0:01:03 AM => 01:03 rejected\n [0]0:01:03 PM => 13:03 rejected\n \n 0:01 => 13:00 00:01\n [0]0:01 AM => 01:00 00:01\n [0]0:01 PM => 13:00 rejected\n2. For set of codes ^DIR Reader calls, adds a new input array: \n \n %DT["S" 0:01:03 => 13:00:03 00:01:03\n [0]0:01:03 AM => 01:00:03 00:01:03\n [0]0:01:03 PM => 13:00:03 rejected\n \n 0:01 => 13:00:00 00:01:00\n [0]0:01 AM => 01:00:00 00:01:00\n [0]0:01 PM => 13:00:00 rejected\n \n f. T@14AM translated to 00:14. After this fix, T@14AM is rejected.\n \n \n g. If %DT["S" and the time contained seconds, and there was at least\n one space between the time and the AM/PM designator, the time was\n rejected. For example, T@1:00:00 PM was rejected, T@1:00:00PM was\n accepted. (This bug fix applies to DSM, not MSM, sites.)\n \n h. If only a year and a time is entered, %DT was accepting the input\n and echoing back a time without hours or minutes:\n \n >S %DT="AEST"\n DIR("L",#) Only applies to set of codes. Replaces the standard \n >D ^%DT\n \n DATE: 1995@9 (1995@::00)\n \n >ZW Y\n Y=2950000.09\n \n This change makes %DT reject this input.\n \n NOIS: MAR-0996-21548\n vertical listing of codes that the Reader displays. It is \n (DIDT)\n \n8. If the user enters something like P at the THEN PRINT FIELDS prompt, and\nthere are no fields that begin with P, DICOMP was looking at the "PT"\nnodes to find all backpointing files that begin with P. This could lead\nto confusing messages like 'such and such pointer is not cross\nreferenced', or 'by ... do you mean... '.\n \n NOIS: ISH-1194-40032\n (DICOMP0)\n \n up to the programmer to ensure that the contents of the \n \n9. If a line in a word processing field sent to ^DIWP contains a vertical\nbar, followed by alphanumerics, followed by punctuation, followed by more\nalphanumerics, an undefined J(0) error can occur at DD^DICOMPV, if there\nis at least one file on the system whose name starts with the characters\nbetween the vertical bar and the punctuation. For example, the following\ncode produces the error:\n \n S X="A line of text <vertical bar>A:B"\n S DIWF="N",DIWL=10,DIWR=68\n DIR("L") array matches the codes in the second ^-piece of \n D ^DIWP\n \nif there are any files on the system that start with 'A'.\n \n NOIS: BRX-1196-11544\n DES-1096-41943\n DES-1296-40431\n HAM-1096-20548\n HIN-1196-41175\n KNX-1196-40451\n DIR(0). \n (DICOMP0)\n \nRoutine Summary: \n===============\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIA2 4082017 4038834 24\n DIAU 6095280 6112601 24\n DICOMP0 9824026 9896481 24\n \n DICOMPX 3752529 3767023 24\n DID 9150099 9151079 24\n DIDT 6692350 6401681 18,24\n DIKZ 9722237 9897922 6,24\n DIQGDD 7426471 6585703 24\n DIQGDDF N/A 1999058 24\n DIQGDDU 1298733 1578963 24\n DIR 8215233 8414467 13,24\n \nInstallation Instructions: \n The format of the DIR("L") array is similar to DIR("A") \n=========================\n \n 1. AXP Sites - The routines %DT and DIR are usually mapped on\nsystems that allow mapping, so you will need to disable mapping for these\nroutines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. The environment\ncheck routine, DIENV, will run automatically.\n \n and DIR("?"). The #'s must be numeric starting from 1. The\n DIENV is sent to prevent the inadvertent queuing of the installation\nof this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n Print Transport Global\n numbered lines are written first and the DIR("L") is \n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 5. Inhibit users from login into the system. Some of the routines in\nthis patch are used heavily in DHCP applications, most notably %DT and\nDIR. The consequences of installing this patch while users are on the\nsystem are that users may get a 'source routine edited' error. Due to the\nhigh usage of these routines in all of DHCP code, it is highly recommended\nthat users be off the system when installing this patch.\n written last.\n \n 6. AXP Sites - Place Taskman in a WAIT State.\n MSM Sites - STOP Taskman.\n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*24\n ==========\n \n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n \n Then enter the names of your other Compute and Print server(s).\n \n NOTE: You will then see the following message:\n Example:\n \n TASKMAN is not running. You must run the routine XPDCPU in the\nproduction UCI for each of the VOLUME SETS you have listed once the\ninstallation starts!!\n \n 9. MSM Sites - After the installation begins, you will be prompted\nto enter a DEVICE. After the device has been entered, KIDS will pause.\nAt this time, you need to go to each of the CPUs that were entered in\nstep 8, and start a job that will allow them to receive the patched\nroutines. On each one, you do the following:\n1. Given the following: \n \n \n a) >D ^XUP This will set up the programming environment.\n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*24\n ==========\nThe installation will then continue.\n \n 10. After installing this patch, you need to move routine DIDT\n >S DIR(0)="SO^1:ONE;2:TWO;3:THREE;4:FOUR;5:FIVE;6:SIX;7:SEVEN"\nfrom your production account to the manager account. Then, in the manager\naccount, rename:\n \n DIDT to %DT\n \n Example: ZL DIDT ZS %DT\n \n 11. AXP Sites - After the patch has been installed, rebuild your map\nset.\n \n >S DIR("L",1)="Select one of the following:"\n 12. AXP Sites - Remove Taskman from WAIT State.\n MSM Sites - Restart Taskman.\n \n 13. Enable users' login.\n >S DIR("L",2)=""\n >S DIR("L",3)=" 1 ONE 5 FIVE"\n >S DIR("L",4)=" 2 TWO 6 SIX"\n >S DIR("L",5)=" 3 THREE 7 SEVEN"\n >S DIR("L")=" 4 FOUR"\n >D ^DIR\n \n \n Select one of the following:\n \n 1 ONE 5 FIVE\n 2 TWO 6 SIX\n 3 THREE 7 SEVEN\n 4 FOUR\n \n Enter response: ?\n \n Enter a code from the list.\n a. You have a file with a pointer-type .01 field called NAME.\n \n Select one of the following:\n \n 1 ONE 5 FIVE\n 2 TWO 6 SIX\n 3 THREE 7 SEVEN\n 4 FOUR\n \n Enter response: \n \n b. NAME points to a file that has a free text field called SHORT\nAlso, for set of codes ^DIR Reader calls, this patch removes unnecessary\nblank lines that appeared before and after the vertical list of codes.\n \nAlso, when using DIR("?") - one line help - this patch makes sure a period\n(.) terminates DIR("?").\n \nAlso, this patch makes sure that DIR("?") is not overwritten by the\nReader's default help prompt.\n \n(DIR)\n DESCRIPTION. \n \n3. Two problems with the FIELD^DID are corrected with this patch:\n \n a. If the FIELD^DID call was used to retrieve field level attributes\nof a file with a file number less than or equal to 1, error code 200 would\nbe returned: "An input variable or parameter is missing or invalid". This\npatch makes FIELD^DID work for fields in files numbered 1 or less.\n \n b. FIELD^DID returned erroneous values for FIELD LENGTH for fields\nwith data types of MUMPS, SET OF CODES, VARIABLE POINTER, and DATE/TIME.\n c. NAME has NAME:SHORT DESCRIPTION as an output transform. \nThis patch makes FIELD^DID return more accurate values for FIELD LENGTH\nfor these types of fields.\n \n (DID, DIQGDD, DIQGDDF, DIQGDDU)\n \n4. This patch corrects the problem which can be reproduced by doing the\nfollowing:\n \n (1) On the FileMan menu, select OTHER OPTIONS -> AUDITING\n (2) Select Audit Option #1, FIELDS BEING AUDITED.\n \n (2) Pick a file that has no fields being audited.\n (3) Select Audit Option #2, DATA DICTIONARIES BEING AUDTED.\n \n An undefined variable DFF error would occur.\n \n NOIS: ISB-1096-30117\n (DIAU)\n \n5. If on a field you tried to put an output transform that looked like\n \n\n\nThis patch fixes 4 problems: \n2. When the DIFROM Server installs Data Dictionaries, it's possible that\n \n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 12. Enable user's login. \nthe 'I' specifier on the file's data global 0 node could be deleted. This\nprevents 'Identifiers' from getting displayed. This was reported on NOIS\nSTC-0596-40915. (DIFROMSS) \n \n3. When a word processing window can't be resolved by FileMan during any\nFM output, a hard error occurs. This patch fixes this problem. This was\nreported on NOIS SFC-0395-60476. (DIWW)\n \n4. When FileMan tries to resolve a word processing window with multiple \n \narguments via a call to ^DIWP, a hard error occurs. (DICOMP) \n \n Routine Summary: \n ================\n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n CHECK^XTSUMBLD results: \n1. In a KIDS build entry, one can send data with a file. The field 'Data\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DICOMP 5808899 5821767 15 \n DIFROMSS 3496020 3490849 15 \n DIFROMSU 5182472 5222720 10,15 \n DIWW 5725412 5618941 15 \n \n Installation Instructions: \n ==========================\nList' may contain the name of a Search or Inquire Template. If several\n \n 1. The routine DIWW is usually mapped on systems that allow mapping,\nso you will need to disable mapping for this routine.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. Say 'No' to 'Want to\nRUN the Environment Check routine?.\n \n The Environment Check routine, DIENV, is sent in order to prevent the\ninadvertent queueing of the installation of this patch.\nfiles in a BUILD entry use the same template name the DIFROM Server\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \ncorrectly processes only the first file's template. The subsequent\n \n 5. Inhibit users from login into the system. If users stay on the\nsystem while installing this patch, a hard error may occur while word\nprocessing fields are printed.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \nfiles' templates are processed incorrectly and it could abort the building\n Install Package(s): \n INSTALL NAME: DI*21.0*15 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n Then enter the names of your other Compute and Print server(s). \nof a transport global. (DIFROMSU)\n NOTE: You will then see the following message: \n TASKMAN is not running. You must run the routine XPDCPU in the \nproduction UCI for each of the VOLUME SETS you have listed once the \ninstallation starts!! \n \n 9. MSM Sites - After the installation begins, you will be prompted to\nenter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\neach one, you do the following:\n \n a) >D ^XUP This will set up the programming environment. \n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*15 \n ==========\nThe installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your map\nset. \n\n
\nPrerequisites:\nIf FileMan patch DI*21*29 is installed without installing patch\nthe second file pointed-to by the variable pointer. Found by Tom\nAckerman.\n \n \nLOOKUPS USING POINTER FIELDS:\n \n a) Fixed a lookup problem in Social Work Case File (650) reported by\nKevin McGee, San Francisco VAMC. Lookup with lower case letter + last 4\ndigits SSN was very slow, and could potentially fail to find a valid match\nas well.\nGMRP*2.5*46, and if the site has the 'ASK TITLE OK?' parameter in file\n \n \nLOOKUPS WHERE DIC(0)["N":\n \n a) When FileMan does a lookup by IEN because DIC(0)["N" and it can find\nno other matches, make it ask OK?... Reported by Clayton Curtis as a\nMailMan bug when he accidently entered a number at the recipient prompt\n(in an attempt to edit a line number of the message.).\n \n \n121.99 (field 3.5) turned on and the user does the lookup on the title\nVARIABLE PRESERVATION,CLEANUP,OUTPUT:\n \n a) Users lookup value X wasn't being protected while executing\nIDENTIFIER logic. Reported by George Huggins, Indian Health Service.\n \n b) When user was entering a new entry with DIC(0)'["A", and up-arrowed\nout either during the entry of a required IDENTIFIER, or at the 'Are you\nAdding...' message, FileMan wasn't setting output variable DUOUT. Reported\nby Robert Whelan, Albany IRMFO.\n \nfile by Internal Entry Number (IEN) the '...OK? YES//' prompt will be\n c) UTILITY option to EDIT a file wasn't cleaning up the DR variable at\nthe end. If the PRINT option was run immediately afterwards, it tried to\nuse DR as an input variable with unexpected results. Reported by Skip\nOrmsby, Clarksburg VAMC.\n \n \nMIX^DIC1 AND IX^DIC CALLS:\n \n a) Honor cross-reference list D in an MIX^DIC1 call, when FileMan goes\noff to look on cross-references for pointer, date, set and variable\ndisplayed twice.\npointer fields on the home file, transforms lookup value from lower to\nupper case, and other types of transforms. Previously FileMan was looking\nat all x-refs during this part of the logic. Reported by Greg Kreis.\n \n b) Using the MIX^DIC1 call, if one of the x-refs in input variable "D"\nis on a pointer field, we do a lookup in the pointed-to file. FileMan was\nstill using the list of indexes in "D" on the pointed-to file, even though\nthey only had meaning in the original home file. Reported by Tom Love\n(Indian Health Service).\n \n \n c) If developer did an MIX^DIC1 or IX^DIC call with D containing a\ncross-reference before "B" (ex. "AC"), and lookup value was a pointer,\nset, variable pointer or date, then lookup could only find the entry by\nits internal value. Reported by Greg Kreis.\n \n \nPROBLEMS WITH PARTIAL MATCHING:\n \n a) Problem stuffing the .01 field of a multiple with "///" in an input\ntemplate, when field is defined as a date with time. When user enters a\nAfter GMRP*2.5*46 has been installed, the user will only be prompted once\ndate with time as a lookup value, FileMan converts it to its FileMan\ninternal value, then if it finds a partial match to that date/time,\nconsiders that to be a match. If there is just one partial match, this\nentry is selected. This was a problem when user was trying to stuff a\ndate/time entry into a multiple with the 3 slash syntax. The fix is for\nFileMan to automatically put an X into DIC(0), thus forcing exact matches\nonly, when the 3 slash syntax is used in an input template. Found by\nCindy Heuer (Hines IRMFO) in Radiology.\n \n b) FileMan did not properly find partial matches to a numeric lookup\nunder those conditions.\nvalue, if the value in the index was alpha-numeric, but started with a\nnumber containing decimals. This was found at Tucson VAMC by Jim Orrey.\nThey had a file where entries contained rational numbers, but they had\ncreated an index with a trailing blank, in order to force string\ncollation.\n \n c) If .01 field is longer than 30 characters, user enters a lookup value\ngreater than 30 characters in lower or mixed case, FileMan failed to find\nvalid matches to the lookup value. Reported by Dave Bolduc (AIMC\nprogrammer)\n \n \n \nPROBLEMS ADDING NEW RECORDS:\n \n a) If a process held onto a LOCK on what would have been the next record\nto be added to a file before incrementing the next record number count in \nthe header node, any other process trying to add an entry to that file\nwould get stuck in an infinite loop (unless/until the first process\nreleased its lock).\n \n \n b) If, contrary to the instruction on page 65 of the FileMan version 21 \nProgrammers Reference Manual, a routine called FILE^DICN with the local \nvariable DD set equal to "B", or the name of some other index in the data \nfile, or the record number of an existing record, or 0, that routine would\nget stuck in an infinite loop.\n \n c) If a routine called FILE^DICN with DD set to some other value, the\nnew record would be added to the file with that as its record number, even\nif DD's value was not a legal record number. This erroneous behavior even\noverrode the use of DINUM.\n==============\n \n \n \n \nIn addition, a new flag DIC(0)["B" was added. The purpose of the flag is\nto restrict FileMan to looking only on the "B" index of any files\npointed-to by the file in which you're doing the lookup. The complete API\ndescription is available in HTML format at:\n \n http:\n //www.vista.domain.ext/softserv/infrastr.uct/fileman/docs/pm/cl-dic-f.htm\nPatch Description\n \n \n \n \n \n Routine Summary: \n ================\n \n The following routines are included in this patch. The second line of\nthese routines now look like:\n=================\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\nDIA 6481291 7724491 29\nDIC 9887383 10229217 8,29\nDIC1 7157061 7440729 29\n \nDIC2 3386307 3335934 29\nDICM 8204058 9718946 29\nDICM0 4918663 4859257 6,29\nDICM2 6920486 7132763 29\nDICM3 4620259 5089665 29\nDICN 7476631 7973339 12,19,29\nDICN1 7148963 5825723 29\nDICQ 8535882 9280954 29\nDICQ1 5481016 5602061 29\nDIE1 6179725 6188430 29\nThis patch fixes many bugs and makes some minor enhancements in the\nDIE17 6896286 6919106 19,29\nDIE3 4863655 4850886 29\nDIOU 4914520 5001668 8,29\nDIU 4034034 4050319 29\n \n \n \n Installation Instructions: \n ==========================\n \nFileMan lookup (^DIC, IX^DIC and MIX^DIC1) entry points.\n 1. The routines DIC, DIC1, DIC2, DICM, DICM0, DICM2, DICM3, DICN,\nDICN1, DICQ, DICQ1, DIE1, DIE17 and DIOU are usually mapped on systems\nthat allow mapping, AXP sites will need to disable mapping for these\nroutines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. (The environment\ncheck routine DIENV will run automatically. DIENV is sent in order to\nprevent the inadvertent queueing of the installation of this patch.)\n \n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \nThe patch addresses the following NOIS and E3R:\n 5. Inhibit users from login into the system. The consequence of\nhaving users on the system while installing this patch are that users\nadding or editing records will get a 'source routine edited' error, the\nedits will be lost and records may be left in an inconsistent state. Note\nthat most of these routines are heavily used in DHCP applications.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\n \nfollowing option:\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*29 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Then enter the names of your other Compute and Print\nNOIS: E3R:\nserver(s). NOTE: You will then see the following message:\n TASKMAN is not running. You must run the routine XPDCPU in the\nproduction UCI for each of the VOLUME SETS you have listed once the\ninstallation starts!!\n \n 9. MSM Sites - After the installation begins, you will be prompted\nto enter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\neach one, you do the following:\n \n======== =======\n \n a) >D ^XUP This will set up the programming environment. \n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines\n =========\n c) Select INSTALL NAME: DI*21.0*29\n ==========\nThe installation will then continue.\n \n 10. AXP Sites - After the patch has been installed, rebuild your map\nANN-0496-42241 7556\nset. \n \n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 12. Enable user's login. \nBIR93-2-2097\nCLE-1295-41595\nCLL94-3-0077\nDAY-0895-42009 \nDUB-0696-30598 \nHUN-0896-21930\nISL-0794-50399\nKNX-0396-41289\nProgress Notes patch GMRP*2.5*46 should be installed at the same time as\nLEA-0496-41204\nLON-0296-62113\nMAD-0694-40057\nMWV-1295-21154\nNOL-0896-71128\nOKL-0396-70731\nPAL-1096-60467\nREN93-4-0762\nSFC-0696-61382\nTUC-0295-60054\nthis FileMan patch. Below is a brief description of that patch. If the\nWCO-0195-50090\n \n \nIn addition, the patch fixes the following bugs/shortcomings reported in\nmail messages and not through the NOIS or E3R system.:\n \nONLINE HELP/PROMPTS:\n \n a) Question mark help on a set of codes wasn't right aligning the\nexternal value of the possible choices in the display. Reported by Cathy\nProgress Notes patch is not installed, it will result only in a minor\nWilliamson (Hines IRMFO).\n \n b) If adding a new entry failed due to failure during execution of a\nLAYGO node on the file, or because the file is restricted from editing\n(such as an archive file), FileMan quit without giving any indication. Now\nit will question mark beep so user knows something went wrong. Reported\nlocally by Don Creaven.\n \n c) When doing a lookup on a multiple field with a whole-file\ncross-reference (like a SYNONYM multiple), the entry from the x-ref was\nannoyance as described, but will not affect any data.\nbeing displayed, but not the .01 at the top level of the selected entry.\nReported by Robert Melmoth (Hines IFMRO).\n \n d) When doing a lookup on some index other than the .01, only the value\nfrom the index is displayed, and not the value of the .01 field itself.\nReported by Tom Ash (Montgomery)\n \n e) A new field SHORT DESCRIPTION was added to the DIALOG file. A WRITE\nidentifier was added to display this field on lookup. Suggested by Mike\nKilmade.\n \n \n \nHARD ERRORS:\n \n a) Bad variable name error at NAME+1^DICM2, when displaying DIC("B")\ndefault value when following a pointer to a variable pointer. Reported by\nMary Ann Ferrarese in Record Tracking.\n \n b) NOPEN error when job is queued with no device, DIC(0)["Q" and lookup\nfails. It tried to write #7,??. Reported by Skip Ormsby (Clarksburg\n \nVAMC).\n \n c) UNDEF error at R+1^DIC2 when a cross-reference entry exists but no\ncorresponding entry exists in the data. Found during testing of FileMan\n21 at Oklahoma City VAMC.\n \n d) UNDEF error in ALL^DICM2 was caused when we had a file with the .01\nfield a variable pointer, the .01 field of the first pointed-to file is a\npointer, user selects the value on the pointed-to file, presses return\nwhen matches on the home file are selected, then FileMan starts to look at\n\n\n Patch Description: \nqueued print job. This patch corrects the problem.\n \n \n \n Routine Summary: \n ================\n \n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n ============\n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994\n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIC 10229217 10080729 8,29,40 \n \n \n \n This patch fixes a rare bug. An UNDEF error can occur if user does a\n Installation Instructions: \n ==========================\n \n 1. The routine DIC is usually mapped on systems that allow mapping,\nAXP sites will need to disable mapping for this routine.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. (The environment\ncheck routine DIENV will run automatically. DIENV is sent in order to\nprevent the inadvertent queueing of the installation of this patch.)\nqueued print of a JOIN EXTENDED POINTER computed field in a file. Patch\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \nDI*21*29 killed Y in ^DIC, before resetting Y to the documented output\n \n 5. Inhibit users from login into the system. The consequence of\nhaving users on the system while installing this patch are that users\nadding or editing records will get a 'source routine edited' error, the\nedits will be lost and records may be left in an inconsistent state. Note\nthat this routine is heavily used in DHCP applications.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \nvalue. This happens only when ^DIC was called from a queued job. In most\n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*40 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\ncases this causes no problems, however, subscripted values of the variable\nother CPUs?'. Then enter the names of your other Compute and Print\nserver(s). NOTE: You will then see the following message: TASKMAN is not\nrunning. You must run the routine XPDCPU in the production UCI for each of\nthe VOLUME SETS you have listed once the installation starts!!\n \n 9. MSM Sites - After the installation begins, you will be prompted\nto enter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routine. On\neach one, you do the following:\nY are used in the computed field logic of JOIN EXTENDED POINTER type\n \n a) >D ^XUP This will set up the programming environment. \n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*40 \n ==========\n The installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your\ncomputed fields, causing an UNDEF error when these fields are printed in a\nmap set.\n \n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 12. Enable user's login. \n\n
\n Description:\n \n \n Most cross-reference are not sensitive to the order in which they \n are fired. For example, a regular cross-reference simply creates \n an index entry based on the current field value, and has no effect \n on other field values or other indexes. However, a trigger does \n affect other fields, and will affect other indexes if those fields \n are cross-referenced. For example, if an entire record is being \n reindexed, a cross-reference on the .01 field might trigger a new \n value into field 1. If field 1 is cross-referenced before field \n .01, field 1's indexes will use the old value instead of the new \n For a complete explanation, please read this description\n one that the .01 trigger will put there.\n \n When you create a new entry, you enter the values for the .01 \n field before any other fields (generally speaking), so the cross-\n references on the .01 field fire first. However, before this \n patch, when reindexing a record FileMan always saves the cross-\n references on the .01 field for last. Using our previous example \n of the trigger on the .01, this means when adding an entry the \n cross-references on field 1 use the new value triggered by the .01 \n but when reindexing field 1's cross-references fire first, using \n carefully. Because these changes are not backward-compatible, we\n the old value, and then cross-references on field .01 fire, \n triggering the new value into field 1 but not affecting its cross-\n references.\n \n This effectively prevents you from writing code sensitive to fire \n order that will work when reindexed. After a great deal of \n consideration, we have decided that the fire order for the Set \n Logic should always fire as if a new entry were being added; that \n is, the .01 cross-references always fire first even when \n reindexing. We decide the Kill Logic is firing in the correct \n have taken time to explain the reasons and effects in detail. For\n order already; that is, the kill logic for the .01 should fire \n last so that FileMan-compatibility is preserved by keeping a B \n cross-reference on any record for as long as possible.\n \n The Merge package uses extensive reindexing when merging two \n records together, and requested this change. This change made the \n package easier to code, and has produced no visible side effects \n at the test sites.\n \n Test Sites :\n more information on these changes, send email to\n ============\n \n Finder and Comma-Piecing Change:\n --------------------------------\n Houston VAMC\n The Imaging Project Team\n \n Reindexing Fire Order Change:\n -----------------------------\n Columbia VAMC\n G.FMTEAM@DOMAIN.EXT, or call Rick Marshall at 206-764-2283.\n Tucson VAMC\n \n Routine Summary :\n =================\n \n The following is a list of the routines included in this patch.\n The second line of each of these routines now looks like:\n \n <tab>;;21.0;VA FileMan;**patch list**;Dec 28, 1994\n \n Please notify us immediately if you experience any ill effects\n Checksums According to CHECK^XTSUMBLD:\n ======================================\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n DICF 7072808 7066780 17,27,42\n DICF1 5555141 5908138 42\n DICF3 6296720 9189474 17,42\n DIK 7325945 7352303 42\n DIK1 5820262 5943602 42\n from either of these changes.\n \n To test if the transport has been corrupted, you can use the\n "Verify Package Integrity" option. This option is under Utilities\n under the KIDS menu. It will compare the checksums in the build\n with the current checksums and list any that differ.\n \n Installation Instructions:\n ==========================\n \n NOTE any instructions that are different for 486 or Alpha sites.\n \n \n 1. Users ARE NOT allowed to be on the system during the\n installation.\n \n 2. DO place TaskMan in a WAIT state.\n \n 3. These routines are not usually mapped on systems that allow\n it so you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n Change 1: Finder and Comma-Piecing\n This option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n ============\n ----------------------------------\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n INSTALL NAME: DI*21.0*42\n ==========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE\n routines to other CPUs?'. Enter the names of your Compute and\n Print server(s).\n \n The Finder, like the classic DIC Lookup call, processes lookup\n AXP Sites - Answer NO to this question.\n \n 8. Rebuild your mapped set if necessary.\n \n 9. DO remove TaskMan from a WAIT state.\n values that contain commas specially. We have reduced the power of \n the Finder's algorithm in order to buy a substantial performance \n gain, and have introduced a new "C" flag to allow callers to get \n the full power of the original algorithm when they need it. DIC's \n algorithm has not been changed, which means DIC and the Finder do \n not handle commas the same way unless you include the "C" flag in \n your Finder call.\n \n \n The need to make this backward-incompatible change arises from \n another difference between the classic DIC lookup and the Finder: \n short-circuiting. In general, the Finder call was designed to \n emulate the DIC lookup, but one feature of DIC caused a great deal \n of confusion: the way DIC short-circuits its lookup whenever it \n has possible matches. DIC rarely presents all of the matches \n available, but instead at fixed points during the lookup will quit \n early if it has any matches. This feature is designed to focus the \n lookup on what DIC considers the most likely matches, but many \n users report they find the behavior counter-intuitive.\n This patch changes two different features of FileMan in important\n \n For this reason, the Finder was designed to always locate all \n possible matches, to avoid short-circuiting out of the lookup \n early. Since the Finder always runs all relevant parts of the \n lookup algorithm, it always pays the performance costs of those \n parts. Comma-piecing, a powerful but expensive part of DIC's \n lookup, was usually short-circuited out of DIC's main lookup, but \n in the Finder, of course, is always run on lookup values \n containing commas. Thus, with values containing commas, the Finder \n is usually much slower than DIC.\n ways. The changes are to 1) how the Finder DBS call processes\n \n The Imaging project, in particular, discovered that the \n performance cost was too much to pay, and asked the FileMan team \n to change the Finder's behavior. Although comma-piecing is \n documented (FileMan 21 Programmer Manual, pages 208-209, and \n FileMan 21 User Manual, page 12 ("^ST,ADD" in part 3)), most users \n polled do not realize the full power of this feature, but believe \n it has a limited capability specific to names. Although the \n FileMan team rarely considers making backward-incompatible \n changes, in this case most experts were unaware of and therefore \n commas in lookup values, and 2) the order in which cross-\n not relying on the parts of this algorithm that made it expensive. \n In return for making this change, lookups at Houston VAMC \n involving values containing commas passed to the Finder that used \n to take 90 seconds now take 4. The sheer magnitude of the trade-\n off led us to reduce the power of comma-piecing Finder lookups to \n what people have known about, while adding the "C" flag for those \n who know about and need the full power.\n \n Most users and developers believe comma piecing is specifically \n used with names, so that a lookup values like "DI,MI" will match \n references fire during reindexing. Although these changes are NOT\n "DISTASO,MICHAEL" and "DISNEY,MICHELLE". In other words, the comma \n in the lookup value stands for a real comma in the index value, \n and a partial match is run on both the first and last names. This \n is what the Finder has been changed to do.\n \n What comma-piecing does in DIC, what it did in the Finder before \n this patch, and what the Finder does after this patch if the "C" \n flag is passed is far more powerful. The comma stands for any \n arbitrary string of characters followed by any punctuation \n character. "DI,MI" then will match not just the values most users \n backward-compatible, they have not disrupted sites we've tested\n expect, but also "DISTASO,XACHARY MICHAEL" and "DINNER WITH \n MICHAEL". This is the principle behind the "^ST,ADD" example in \n the FileMan 21 User Manual. This feature requires a tremendous \n amount of processing, but yields far more flexible results, and \n programmers are encouraged to use the Finder's new "C" flag when \n appropriate.\n \n Change 2: Reindexing Fire Order Change\n --------------------------------------\n The order in which cross-references fire can be crucial. We have \n at, and provide a great deal of benefit in return.\n changed this order to correct what we perceive to be a flaw in the \n algorithm. By its nature, this can affect the integrity of the \n database. We believe the new order is the correct one, but if \n there is code in VistA that relies on the old order this change \n has the capability of introducing database corruption. We did not \n make this change lightly. Not only do we believe the new fire \n order is correct, but it is likely that code that relied upon the \n old fire order was already introducing database corruption. We \n have found no evidence yet of code that relied on the old fire \n order, but in a system this complex we can never be sure.\n\n\nDescription:\n Houston VAMC\n White City VAMC\n George Timson\n Michael Ogi\n \nRoutine Summary :\n=================\n \n The following is a list of the routines included in this patch. The\n second line of each of these routines now looks like:\n============\n \n <tab>;;21.0;VA FileMan;**28**;Dec 28, 1994\n \nChecksums According to CHECK^XTSUMBLD:\n======================================\n \n Rtn Nm Chksum Before Chksum After\n ------ ------------- ------------\n DIM 2096545 2236006\n DIM1 7391479 6135531\n \n DIM2 4847408 4186487\n DIM3 4724114 4265731\n DIM4 3593321 3292224\n \n To test if the transport has been corrupted, you can use the \n "Verify Package Integrity" option. This option is under Utilities \n under the KIDS menu. It will compare the checksums in the build \n with the current checksums and list any that differ.\n \nInstallation Instructions:\n This patch changes FileMan's DIM (MUMPS Code Validation) entry point\n==========================\n \nNOTE the instructions that are different for DSM sites.\n \n 1. Users ARE NOT allowed to be on the system during the \n installation.\n \n 2. DO place TaskMan in a WAIT state.\n \n 3. DSM Sites: These routines are not usually mapped so you will\n to validate against the 1995 ANSI Standard and the new VA SAC.\n probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \n This option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options: \n \n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: DI*21.0*28\n ==========\n \n 8. DSM Sites: Rebuild your mapped set if necessary.\nTest Sites :\n \n 9. DO remove TaskMan from a WAIT state.\n============\n \n\n
\nDescription:\nfile is installed, too.\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*30 \n ==========\n \nAnswer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, and \nProtocols?' question. \n \n7. MSM Sites - Answer YES to the question 'Want to MOVE routines to \nother CPUs?'. Then enter the names of your other Compute and Print \nserver(s).\n \n \n8. KIDS will load the patch without further intervention. During the\nKIDS install, KIDS will produce the following messages:\n \n Data Dictionary for File #.403 not installed.\n \n Data Dictionary for File #.404 not installed.\n \nThese message do NOT indicate an error condition. They are reporting that\nnew Data Dictionaries for the Form and Block files are not being installed\nA. Import Data option\nalthough data for those files is being updated. This is correct.\n \nThe new option is the Import Data option found on the Other Options \nsubmenu (DIOTHER) on the VA FileMan menu. This option invokes a \nScreenMan form used to define the import. In addition to moving data \nfrom a host file into a VA FileMan file, the Import Tool produces a \nreport of the import activity.\n \n============\nDocumentation of the Import Tool is located in a revised Chapter 18 of \nthe VA FileMan User Manual. Previously, that chapter documented the \nData Export Tool. Now, Chapter 18 documents both the Import and Export \nTools. The National Center for Documentation will be distributing this \nrevised chapter. Acrobat versions of both the change pages, and the \nUser Manual updated with the change pages, are available at\n \n http://www.vista.domain.ext/softserv/infrastr.uct/fileman/docs/\n \nThe new chapter is also available in HTML format at:\n \n \n http://www.vista.domain.ext/softserv/infrastr.uct/fileman/docs/u2/\n (access the Import/Export Tools chapter)\n \nB. FILE^DDMP API\n \nThe programmer API consists of a single call: FILE^DDMP. Functionally, \nit is equivalent to the user option. The API allows the programmer to \nspecify the parameters of the data import.\n \nThis patch implements new VA FileMan functionality: the Import Tool. \nDocumentation in HTML format for the API can be found at:\n \n http://www.vista.domain.ext/softserv/infrastr.uct/fileman/docs/\n pm/ft_ddmpf.htm\n \nC. Import Template file\n \nA new file is added by this patch: the Import Template file (#.46). The \nfile's data is stored in an existing global -- root: ^DIST(.46. No data \nfor the file is contained in this patch. \nThe Import Tool will move data from an ASCII host file into a VA FileMan \n \nRoutine Summary:\n================\n \nThe following routines are included in this patch. Checksums are \nCHECK^XTSUMBLD results.\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n DDMP <NEW> 11685139 30\nfile. The uses and limitations of the Import Tool are described in the \n DDMP1 <NEW> 9723042 30\n DDMP2 <NEW> 9285380 30\n DDMPSM <NEW> 7179788 30\n DDMPSM1 <NEW> 3485759 30\n DDMPU <NEW> 8199841 30\n DII1 455555 468832 30\n DINIT6 3176942 3570355 30\n \n \nThe DDMP* routines contain the Import Tool. DII1 is included to add the \ndocumentation. The location of the documentation is given below.\nImport Data option to the Other menu when VA FileMan is accessed from \nProgrammer mode. DINIT6 assures that the Data Import option will not be \nremoved from the Kernel menus if ^DINIT is rerun. It is NOT necessary \nto rerun ^DINIT to implement this patch.\n \nInstallation Instructions: \n==========================\n \n1. Neither of the pre-existing routines in this patch are typically \nmapped. It is NOT recommended that any of the DDMP* routines be mapped.\n \n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system.\n \n3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \n4. On the KIDS menu, under the 'Installation' menu, use the following \noptions: \n \nThe Import Tool consists of a new option and a programmer API. A new \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n5. Users may remain on the system when this patch is installed. \nTaskMan should remain running.\n \n6. On the KIDS menu, under the 'Installation' menu, use the following \noption: \n\n
\nVA FileMan SQLI Interface (SQLI) \ndata. After installing this patch, note that the DMSQ MENU will not be\n <tab>;;21.0;VA FileMan;**38**;July 28, 1997 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DMSQ new routine 10102863 38 \n DMSQD new routine 8773388 38 \n DMSQE new routine 843826 38 \n DMSQF new routine 9792265 38 \nattached to any other existing menu; it is stand-alone, to be assigned as\n DMSQF1 new routine 8310046 38 \n DMSQF2 new routine 8370804 38 \n DMSQP new routine 2371815 38 \n DMSQP1 new routine 3565656 38 \n DMSQP2 new routine 6721470 38 \n DMSQP3 new routine 11874271 38 \n DMSQP4 new routine 2151271 38 \n DMSQP5 new routine 5423594 38 \n DMSQP6 new routine 10074783 38 \n DMSQS new routine 3197279 38 \nneeded.\n DMSQT new routine 11672859 38 \n DMSQT1 new routine 1181888 38 \n DMSQU new routine 10589283 38\n \nInstallation Instructions: \n==========================\n \nBefore starting: Place and protect ^DMSQ\n \nThis patch brings in a new global, ^DMSQ. As usual with new globals,\n \nplace it before running the install (the default location of the install\nwill otherwise be used). You can translate it for ease of access.\nJournaling is unnecessary.\n \nFor global protection, a standard approach can be used, such as the\nfollowing:\n \n DSM for OpenVMS - System (RWD), World (RW), Group (RW), and User (RW)\n OpenM - Owner (RWD), Network (RWD), Group (N), World (N)\n MSM-DOS - System (RWD), World (RWD), Group (RWD), User (RWD)\nThe installation of this patch is mandatory because the software includes\n \nNOTE: Users may remain on the system during this installation. There's no\nneed to disable logons either.\n \n1. There's no need to disable mapping (these routines won't need to be\n mapped).\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n \nsupported references (entry points and DD structures) that may be called\n3. The patch has now been loaded into a Transport global on your system.\n You now need to use KIDS to install the Transport global. \n \n4. On the KIDS menu, under the 'Installation' menu, use the following\n options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \nby application code. So, even if you don't plan to implement\n(5. Users don't need to logoff. They may remain on the system while this\n patch is installed.) \n \n(6. There isn't any need to place TaskMan in a WAIT state.) \n \n7. On the KIDS menu, under the 'Installation' menu, use the following\n option: \n \n Install Package(s): \n INSTALL NAME: DI*21.0*38 \nSQLI as a basis for a vendor SQL product, you still should install this\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols?' \n \n8. MSM Sites - Answer YES to the question 'Want to MOVE routines to other\n CPUs?'. Enter the names of your Compute and Print server(s). \n \n9. MSM Sites - After the installation begins, you will be prompted to\n enter a DEVICE. After the device has been entered, KIDS will pause.\npatch. \n At this time, you need to go to each of the CPUs that were identified\n in the previous step and start a job that will allow them to receive\n the routines included in the patch. On each CPU, do the following:\n \n a) >D ^XUP - to set up the programming environment \n ======\n b) >D ^XPDCPU - to start the job that receives the routines \n =========\n c) Select INSTALL NAME: DI*21.0*38 \n ==========\n \n \nThis completes the installation instructions.\n \nThe installation instructions for loading this patch are entirely\ncontained below. You don't need to get the SQLI documentation for this\npurpose. (The SQLI documentation doesn't include installation\ninstructions for loading this patch.)\n \n \nDocumentation for Implementing SQLI\n===================================\nImplementing SQLI is optional. See the VA FileMan SQLI Site Manual for\nmore information about populating the SQLI files and, furthermore,\nThis patch installs the foundation for building an interface between VA\nincorporating vendor SQL products and building an SQL system. This manual\nis to be reproduced and distributed by the National Center for\nDocumetation (NCD). This manual will also be available in Acrobat PDF\nformat from the SQLI home page:\n \n http://www.vista.domain.ext/softserv/infrastr.uct/sqli\n \nThe SQLI home page will be a source of current information, including case\nstudies of how sites have chosen to implement SQL access to their systems.\n \nFileMan's data dictionaries and a vendor's M-based SQL data dictionaries.\n \nTest Sites \n==========\nTwo test sites have loaded this SQLI patch and have implemented a full SQL\nsystem (with the additional vendor software that's needed). These are the\nVA medical facilities at San Francisco (VISN 21) and Brooklyn (VISN 3). \n \nFour additional test sites are in the process of establishing a system\nthat is based on SQLI: VA medical facilities at Seattle (VISN 20),\nPhoenix (VISN 18), West Haven (VISN 3), and Palo Alto (VISN 21). \nThis patch will bring in a new global, ^DMSQ, and several new routines and\n \n \nSupported References\n====================\n \nDATA DICTIONARIES \nAll the files, fields, and cross-references included in this patch can be\nreferenced directly without integration agreements. This enables vendors\nto create mapping utilities using the SQLI structures. Specifically,\nthese are the files in the 1.52 to 1.53 number range, all stored in ^DMSQ.\noptions in the DMSQ namespace.\nSee the SQLI Vendor Manual on the SQLI home page for more specific\ninformation.\n \nCALLABLE ENTRY POINTS\nThe following routine entry points may be called in application code.\nThey are primarily designed for use in vendor mapping code. See the SQLI\nSite Manual and SQLI Vendor manual for more information.\n \nPopulating SQLI files (Projecting the Interface)\n ALLF^DMSQF - non-interactive call\n \n SETUP^DMSQ - interactive call (used in the DMSQ PROJECT option)\n \nPopulating the SQLI_KEY_WORD file (with the SQL vendor's keywords)\n KW^DMSQD - loads keywords from a specified global\n \nPopulate the SQLI_TABLE and SQLI_PRIMARY_KEY row counts (to accumulate\nstatistics that vendors may want to use to optimize queries)\n ALLS^DMSQS - all tables\n STATS^DMSQS - one table \n \nThe new files (in ^DMSQ) are in the 1.52 to 1.53 number range. Each one\nNaming algorithms to generate SQL-compatible names\n $$SQLI^DMSQU - general check\n $$SQLK^DMSQU - general check including keyword check\n $$FNB^DMSQU - specific check for table names\n $$CN^DMSQU - specific check for column names\n \nDIRECT MODE UTILITIES (also available via the DMSQ MENU option)\nThese calls are for direct mode use only (issued interactively at the\nprogrammer prompt). They are not supported for use in application code.\nSee the SQLI Site Manual for more information.\nbegins with SQLI, e.g. the SQLI_TABLE file. None of the files includes\n \n MAIN^DMSQE - lists files/fields that couldn't be projected\n RUNONE^DMSQ - re-run projection for one file (for testing only)\n \n \nRoutine Summary: \n================\nThe following routines are included in this patch. The second line of\nthese routines will look like: \n \n\n
\nThis patch fixes the following problems: \n 2. The DBS calls FILE^DID and $$GET1^DID return an incorrect value for a\nfile's READ ACCESS.\n \nRoutine Summary: \n================\n \n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIQGDDT 7439422 7439520 25\n DITR 5710355 5514796 6,25\n \nInstallation Instructions: \n==========================\n 1. When merging data using KIDS, there is a case where existing data at\n \n 1. Routine mapping is NOT recommended for these routines. If you are\nusing routine mapping, ensure that these routines are NOT in your mapped\nroutine set before proceeding.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system. The environment check\nroutine DIENV will run automatically. \n \n DIENV is sent in order to prevent the inadvertent queueing of the \nthe target site gets overwritten by incoming data. When a file being\n installation of this patch. \n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \nexported contains pointers, and the pointed-to-file is being exported\n Backup a Transport Global \n \n 5. Inhibit users from login into the system. Any user who is logged\nin and using an application which uses the DBS calls $$GET1^DID and\nFILE^DID run the risk of getting <CLOBBER> errors. Any user using\nFileMan's 'Transfer File Entries' option run the risk of getting an error\nin the midst of a transfer. A database record may be left in a corrupted\nstate. Any init that may be running or any KIDS installation that brings\nin data may leave the records in a corrupted state.\n \nas well, MERGING and RESOLVING POINTERS will cause the existing pointer\n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*25\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nvalues on the first file to get overwritten by the incoming data. This\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n Then enter the names of your other Compute and Print server(s). \n NOTE: You will then see the following message: \n TASKMAN is not running. You must run the routine XPDCPU in the \n production UCI for each of the VOLUME SETS you have listed once the \n installation starts!! \n \npatch fixes this problem by not overwriting existing data.\n 9. MSM Sites - After the installation begins, you will be prompted\nto enter a DEVICE. After the device has been entered, KIDS will pause.\nAt this time, you need to go to each of the CPUs that were entered in step\n8, and start a job that will allow them to receive the patched routines.\nOn each one, you do the following:\n a) >D ^XUP This will set up the programming environment. \n ======\n b) >D ^XPDCPU This starts the job that receives the patched\nroutines. \n =========\n \n c) Select INSTALL NAME: DI*21.0*25\n ==========\nThe installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your map\nset. \n \n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n\n
\n This patch makes a few minor bug fixes and contains some enhancements to\n \n \n Format: NUMYEAR4(datexp)\n Where: datexp is an expression with a date/time value\n Use: This function returns the 4 digit year in datexp as a \n number.\n \n Example: NUMYEAR4(DATE OF BIRTH)==> 1949\n \n \nRoutine Summary: \n DIDT (%DT) Two minor bugs were corrected. \n================\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DDMP2 9285380 9295425 30,44 \n DIDT (%DT) 6367783 6481242 18,24,37,44 \n DIDTC (%DTC) 7334026 7099203 18,44 \n DIEH1 1151210 1201975 44 \n DIENV (env.check) 129370 129370 44\n DILIBF 6348908 6194115 44 \n One is that before, if %DT input variable contained "X", and if user\n DINVMSM 8405664 8320664 44 \n DIP12 4793451 4793661 2,9,16,44 \n DIQGU 4937798 4828002 8,44 \n \n To test if the transport has been corrupted, you can use the "Verify\nPackage Integrity" option. This option is under Utilities under the KIDS\nmenu. It will compare the checksums in the build with the current\nchecksums and list any that differ. \n \n \n entered a date like MMDDYY where the year was "00", the date was\n \n Installation Instructions: \n ==========================\n \n NOTE the instructions that are different for your M implementation. \n \n 1. NOTE: Users ARE NOT allowed to be on the system during the \ninstallation. \n \n --- Pre Installation steps --- \n rejected. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\nThis option will load the KIDS package onto your system. The environment\ncheck routine DIENV will run automatically.\n \n DIENV is sent to prevent the inadvertent queuing of the installation\nof this patch.\n \n 3. The patch has now been loaded into a Transport global on your \nsystem. You now need to use KIDS to install the Transport global. \n The other is that one of the algorithms was incorrectly treating the\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n --- Actual Installation --- \n \n year 2100 as a leap year.\n 5. Users ARE NOT allowed to be on the system during the\ninstallation. Inhibit users from login into the system. %DT, %DTC, DILIBF\nand DIP12 in particular are used heavily in VISTA applications. The\nconsequences of installing this patch while users are on the system are\nthat users may get a 'source routine edited' error.\n \n 6. DO place TaskMan in a WAIT state. \n \n 7. DSM Sites: The routines %DT, %DTC and DILIBF are usually mapped\non systems that allow mapping, so you will need to disable mapping for\n \nthese routines.\n \n 8. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Install Package(s) \n \n INSTALL NAME: DI*21.0*44 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n In addition, an enhancement was made that will change the current\nand Protocols?'\n \n 9. DSM and MSM sites: After installing this patch, you need to move\nthe routines DIDT and DIDTC from your production account into your manager\naccount. Then, in the manager account, rename:\n \n DIDT to %DT \n DIDTC to %DTC \n \n Example: ZL DIDT ZS %DT \n behavior. Currently, as documented, if a user enters only 2 digits of\n \n 10. Open M sites: Rename: \n \n DIDT to %DT \n DIDTC to %DTC \n \n Example: ZL DIDT ZS %DT \n \n 11. DSM Sites: Rebuild your mapped set if necessary. \n \n ensure compliance with year 2000 issues. The changes are as follows:\n the year and if %DT is not set up by the developer to contain either\n 12. DO remove TaskMan from a WAIT state. \n \n 13. Enable users' login. \n an "F" (future) or "P" (past), then FileMan assumes the current\n century. Thus in 1997, if a user enters 01/01/00, FileMan assumes\n 01/01/1900.\n \n NEW BEHAVIOR for DIDT (%DT):\n note that this new behavior only applies when the user enters\n a 2-digit year, causing FileMan to guess the century. Note\n also that the "F" and "P" flags will behave as they always have--this\n new behavior is only used when neither of those flags is set.\n \n \n If using the current century causes the date to be more than 80 years\n in the past, then FileMan will assume the next century. Thus in 1997\n if a user enters a year of 0 through 16, FileMan will assume the\n years 2000 through 2016, because 1900 through 1916 are more than 80\n years in the past.\n \n If using the current century causes the date to be more than 20 years\n in the future, then FileMan will assume the previous century. Thus\n in the year 2000, if the user enters 21 through 99, FileMan will\n \n assume the years 1921 through 1999, because 2021 through 2099 are\n more than 20 years in the future.\n \n \n DIDTC (%DTC) Although all of the code properly handled dates up to 2100,\n the code was treating 2100 as a leap year. This has been corrected.\n Also, online help for dates (HELP^%DTC) was changed to reflect the\n change in functionality described in ^%DT above.\n \n \n \n DIEH1 Online help for dates used by the DataBase Server calls (DT^DIEH1)\n was changed to reflect the change in functionality described in\n ^%DT above. In support of this routine change is a change to entry\n #9110 in the DIALOG file.\n \n \n DILIBF Old algorithms were treating the year 2100 as a leap year. This\n has been corrected.\n \n \n DDMP2 Changed to call internal FileMan date formatting routines (DILIBF)\n DINVMSM This routine contains operating system-specific code and is used\n by stand-alone FileMan sites only. Routine SET was setting DT using\n an MSM-specific call that would not have worked properly in the year\n 2000. This has been corrected.\n \n \n DIP12 In the PRINT option, if the user chose to print the sort criteria\n in the header of the report, and if any of the sort fields were\n dates, the date was previously printed with a 2-digit year. That is\n changed so that the date is now printed with a 4-digit year for\n rather than Kernel date formatting routines (XLFDT) to take\n clarity.\n \n \n DIQGU Old algorithms were treating the year 2100 as a leap year. This\n has been corrected.\n \n \n \n CHANGE TO ENTRY IN DIALOG FILE: In support of new online help for dates\n to reflect the new behavior of ^%DT, entry number 9110 has been\n advantage of changes made to DILIBF (described below).\n changed. This entry is called from routine DIEH1.\n \n \n \n NEW FILEMAN FUNCTIONS: NUMDATE4 and NUMYEAR4\n The new FileMan Functions NUMDATE4 and NUMYEAR4 have been added to\n the list of FileMan Functions that are available for use within\n FileMan. They behave as follows:\n \n NUMDATE4\n \n \n Format: NUMDATE4(datexp)\n Where: datexp is an expression with a date/time value\n Use: This function returns the date in datexp, in MM/DD/YYYY\n format.\n \n Example: NUMDATE4(DATE OF BIRTH)==> 03/07/1949\n \n \n NUMYEAR4\n\n
\n Description:\n ============\n \n Albany ISC\n \n Routine Summary :\n =================\n \n The following is a list of the routines included in this patch.\n The second line of each of these routines now looks like:\n \n ============\n <tab>;;21.0;VA FileMan;**patch list**;Dec 28, 1994\n \n Checksums According to CHECK^XTSUMBLD:\n ======================================\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n DICF 7724491 7752413 29,43\n \n To test if the transport has been corrupted, you can use the\n \n "Verify Package Integrity" option. This option is under Utilities\n under the KIDS menu. It will compare the checksums in the build\n with the current checksums and list any that differ.\n \n Installation Instructions:\n ==========================\n \n NOTE any instructions that are different for 486 or Alpha sites.\n \n 1. Users ARE NOT allowed to be on the system during the\n This patch fixes a problem introduced by patch DI*21*29,\n installation.\n \n 2. DO place TaskMan in a WAIT state.\n \n 3. This routine is not usually mapped on systems that allow\n it so you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package onto your system.\n \n an invalid subscript error that could occur when editing\n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n a long line of M code in an input template. This problem\n Install Package(s)\n INSTALL NAME: DI*21.0*43\n ==========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE\n routines to other CPUs?'. Enter the names of your Compute and\n Print server(s).\n \n AXP Sites - Answer NO to this question.\n \n was reported as NOIS ISW-0497-21817.\n 8. Rebuild your mapped set if necessary.\n \n 9. DO remove TaskMan from a WAIT state.\n \n Test Sites :\n\n
\nDescription:\n Mike Hendry). Mr. Hendry reported that uncompiling cross-\n Danila Manapsal). This change is also for the FileMan \n Components.\n \n 14. Updater: allow deletion of fields: DICA1 (for Michael \n Ogi). Mr. Ogi reported that the Updater is needlessly blocking \n the ability to delete fields, something the Filer (which it \n calls) allows. This was changed. Reported in phone \n conversation with Mr. Ogi.\n \n 15. Updater: subentry problem: DICA1 (for Mike Kilmade). Mr. \n references didn't work if the file had whole file-cross-\n Kilmade reported during development of PCMM that the Updater \n was preventing deletion of subfile entries if the same FDA \n added another subentry. This was fixed. Reported in Forum msg \n # 19707244.\n \n 16. Updater: process LAYGO Finding nodes before Adding nodes: \n DICA2 (for Michael Ogi). Mr. Ogi reported during testing of \n the Udpater that a bug prevented it from processing FDA nodes \n in the order specified, which occasionally caused undefined \n errors. The documented order was reestablished. Reported in \n references on one of its subfiles. Reported in NOIS ISL-0897-\n phone conversation with Mr. Ogi.\n \n 17. Updater: return 0 nodes for LAYGO Finding nodes: DICA (for \n Michael Ogi). Mr. Ogi reported during testing of the Updater \n that it was not returning 0 nodes for LAYGO Finding nodes as \n documented. The documented order was reestablished. Reported \n in phone conversation with Mr. Ogi.\n \n 18. Updater: stop errors with LAYGO Finding nodes: DICA1 (for \n Alan Chan). Mr. Chan reported that under some circumstances \n 51962.\n LAYGO Finding nodes were reporting errors instead of finding \n existing entries. The errors were stopped, and LAYGO Finding \n nodes now properly find existing entries. Reported in ISC-SF \n msg # 1170164.\n \n 19. Updater: stop multiple Updaters interference: DICA1 (for \n Travis Torres). Mr. Torres reported that Updaters running \n simultaneously in different processes on the same machine \n could occasionally process each other's FDAs. The code was \n changed to better segregate their data structures. Reported in \n \n phone conversation with Mr. Torres.\n \n Output\n ------\n 20. Sort: remove duplicates from prints: DIO0 (for David \n Alexander, John Harvey, Nancy Nagle, Dan Petit, Daniel \n Schramm, Ellen Zufall, Fil Beza). Many sites reported problems \n with prints in which mnemonic cross-reference entries in the B \n index were creating false positives in reports. Ms. Zufall and \n Mr. Beza identified the problem as introduced by patch \n 2. Compiled Routines: problem uncompiling input templates: \n DI*21*35, and Ms. Zufall fixed it. Reported in ISC-SF msg # \n 1198710, FORUM msg #s 25464901 and 25149562, and NOIS #s SFC-\n 0198-60115, TOP-0198-40108, & WBP-1297-21797.\n \n 21. Transfer: improve performance: DITR, and DITR1 (for Dave \n Bolduc). Mr. Bolduc reported slow performance on large \n transfers, and identified a fix to the problem that was \n gratefully accepted. Reported in NOIS # AIM-0797-N2065.\n \n Special thanks go to Dave Alexander, whose keen eye for bugs\n DIEZ (for Cindy Heuer). Ms. Heuer reported that uncompiled \n saved the rest of the VA a lot of grief with this patch. :)\n \nTest Sites :\n============\n AIM Center\n Boston VAMC\n Bronx VAMC\n Dublin VAMC\n Huntington VAMC\n Oklahoma City VAMC\n input templates would recompile themselves when the \n Prescott VAMC\n Puget Sound HCS\n San Francisco VAMC\n Tuscaloosa VAMC\n Washington VAMC\n West Palm Beach VAMC\n Birmingham CIOFO\n Hines CIOFO\n Salt Lake City CIOFO\n San Francisco CIOFO\n definitions of fields within those templates were changed. \n \nRoutine Summary :\n=================\n The following is a list of the routines included in this\n patch.\n \n The second line of each of these routines now looks like:\n \n <tab>;;21.0;VA FileMan;**patch list**;Dec 28, 1994\n \n Reported in FORUM msg # 23842872.\n (Checksums According to CHECK^XTSUMBLD)\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n DIC1 7440729 7448670 29,41\n DICA 5157184 5237530 6,17,8,41\n DICA1 4597954 5338649 17,41\n DICA2 3685071 3688712 41\n DICF1 5555141 5923519 42,41\n DICF2 5355774 5392088 27,41\n============\n \n DICF3 9189474 9003959 17,42,41\n DICF5 3301437 3486879 17,27,41\n DICL1 2778676 2538541 17,41\n DIEF 6851994 6413098 41\n DIEFU 4587189 4602560 41\n DIEZ 8995968 9310202 41\n DIO0 9392292 9418825 9,21,35,41\n DIPZ0 2495452 2524580 41\n DIR 8414467 8809710 13,24,41\n DIR1 7765832 7982983 6,13,19,41\n Reader\n DIR2 8922361 9053765 41\n DIR3 3670507 2913754 19,41\n DITR 5514796 5528738 6,25,41\n DITR1 6414011 6525800 41\n \n To test if the transport has been corrupted, you can use the\n "Verify Package Integrity" option. This option is under\n Utilities under the KIDS menu. It will compare the checksums\n in the build with the current checksums and list any that\n differ.\n ------\n \nInstallation Instructions:\n==========================\nNOTE any instructions that are different for DSM sites.\n \n 1. Users ARE NOT allowed to be on the system during the\n installation.\n \n 2. Place TaskMan in a WAIT state.\n \n 3. Reader: case sensitivity with codes: DIR1 (for Marcia\n 3. DSM sites: Disable routine mapping (DIC1, DIR, DIR1, &\n DIR2 are usually mapped).\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan\n menu. This option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the Transport\n global.\n \n Insley). Ms. Insley reported that the Reader converted the\n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n INSTALL NAME: DI*21.0*41\n ==========\n case of the user's input for the external form of the codes,\n \n 7. DSM sites: Rebuild your mapped routine set.\n \n 8. Remove TaskMan from its WAIT state.\n but not for the internal. Reported in Forum msg # 23931868.\n \n 4. Reader: list and range problems: DIR3 (for Gary Beuschel).\n Mr. Beuschel reported problem was that the Reader rejects\n This patch contains critical bug fixes requested by package \n lists that contain consecutive numbers out of order, such as\n 50,49; I found that it also rejected a number followed by a\n range ending in that number, such as 50,40-50. Reported in\n ISC-SF msg #s 1190657, 1193613, and 1193773.\n \n 5. Reader: problems with help for dates: DIR, DIR2 (for Gary \n Beuschel). Mr. Beuschel reported that the help for dates is \n scanty compared to what the %DT utility provides. It has been \n brought in line with %DT's, and also made responsive to the \n date parameters passed in the second ^-piece of DIR(0). \n developers in need of the fixes for their own patches or \n Reported by phone.\n \n 6. Reader: DIR("PRE") parameter: DIR (for Gary Beuschel). Mr.\n Beuschel needed a programming hook to let him intercept the\n user's input before the Reader begins its data type\n validation. The new supported input parameter DIR("PRE") is a\n pre-validation transform that can either change X, in which\n case the Reader will proceed as though the new value is what\n the user entered, or can kill X, in which case the Reader will\n behave as though the user entered an illegal value. DIR("PRE")\n package releases.\n executes almost immediately after the READ takes place, just\n after DTOUT is set and before any other checking is done. The\n only inputs are X and DTOUT, and the only outputs are X and\n DTOUT. Reported in phone conversation with Mr. Beuschel.\n \n Lookup\n ------\n 7. Classic Lookup: echo & match lists: DIC1 (for Marcia \n Insley, Tana Defa, and Melissa Hughes). Ms. Insley reported \n during testing of CPRS that Puget Sound needed a change to how \n \n DIC's E flag works. The E flag, which normally ensures a \n user's response is echoed back, did not do so when the user \n picked from a match list, a time when typos are therefore \n difficult to notice but easy to make. This was changed to \n make E work with match list selections. Reported in Forum msg \n # 24573804.\n \n 8. Finder: `IEN lookup problem: DICF1 (for Gary Beuschel). Mr. \n Beuschel reported that the Finder's `IEN lookup is only \n allowing IENs that are integers, disallowing such IENs as the \n Compiled Routines\n Postmaster's (.5). This was fixed. Reported in phone \n conversation with Mr. Beuschel.\n \n 9. Finder: illegal number error: DICF3 (for Bob Fuller). Mr. \n Fuller reported an illegal number error caused by the Finder's \n vulnerability to input that looks like an exponential. The \n Finder has been bullet-proofed. Reported in NOIS # BRX-0397-\n 12605.\n \n 10. Finder & Lister: tolerate empty indexes: DICF2, DICF3, \n -----------------\n DICF5, DICL1 (for Rob Whelan, Deborah Gorman, Diane McCance, \n and Gary Beuschel). Reported in NOIS #s BHH-0897-41483 and \n CLE-0797-42276, and in phone conversations with Mr. Whelan and \n Mr. Beuschel. \n \n Enter & Edit\n ------------\n 11. Filer: prevent variable problem: DIEFU (for Joel Ivey). \n Mr. Joel reported that during testing of Patient Merge, the \n Filer did not adequately protect its own variables from deeply \n 1. Compiled Routines: problem uncompiling xrefs: DIPZ0 (for \n recursive calls, playing havoc during Merge. This was fixed. \n Reported in phone conversation with Mr. Ivey.\n \n 12. Filer: allow deletion of top-level records: DIEF (for & by \n Danila Manapsal). Ms. Manapsal reported that the FileMan \n Components need the ability to delete records through the \n Filer. She corrected the Filer to allow this. Reported in \n phone conversation with Ms. Manapsal.\n \n 13. Updater: allow deletion of top-level records: DICA1 (for \n\n\n Description:\n ============\n \n Albany ISC\n \n Routine Summary :\n =================\n \n The following is a list of the routines included in this patch.\n The second line of each of these routines now looks like:\n \n ============\n <tab>;;21.0;VA FileMan;**patch list**;Dec 28, 1994\n \n Checksums According to CHECK^XTSUMBLD:\n ======================================\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n DICF 7724491 7752413 29,43\n \n To test if the transport has been corrupted, you can use the\n \n "Verify Package Integrity" option. This option is under Utilities\n under the KIDS menu. It will compare the checksums in the build\n with the current checksums and list any that differ.\n \n Installation Instructions:\n ==========================\n \n NOTE any instructions that are different for 486 or Alpha sites.\n \n 1. Users ARE NOT allowed to be on the system during the\n This patch fixes a problem introduced by patch DI*21*29,\n installation.\n \n 2. DO place TaskMan in a WAIT state.\n \n 3. This routine is not usually mapped on systems that allow\n it so you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package onto your system.\n \n an invalid subscript error that could occur when editing\n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n a long line of M code in an input template. This problem\n Install Package(s)\n INSTALL NAME: DI*21.0*43\n ==========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE\n routines to other CPUs?'. Enter the names of your Compute and\n Print server(s).\n \n AXP Sites - Answer NO to this question.\n \n was reported as NOIS ISW-0497-21817.\n 8. Rebuild your mapped set if necessary.\n \n 9. DO remove TaskMan from a WAIT state.\n \n Test Sites :\n\n
\nDescription:\n Mike Hendry). Mr. Hendry reported that uncompiling cross-\n Danila Manapsal). This change is also for the FileMan \n Components.\n \n 14. Updater: allow deletion of fields: DICA1 (for Michael \n Ogi). Mr. Ogi reported that the Updater is needlessly blocking \n the ability to delete fields, something the Filer (which it \n calls) allows. This was changed. Reported in phone \n conversation with Mr. Ogi.\n \n 15. Updater: subentry problem: DICA1 (for Mike Kilmade). Mr. \n references didn't work if the file had whole file-cross-\n Kilmade reported during development of PCMM that the Updater \n was preventing deletion of subfile entries if the same FDA \n added another subentry. This was fixed. Reported in Forum msg \n # 19707244.\n \n 16. Updater: process LAYGO Finding nodes before Adding nodes: \n DICA2 (for Michael Ogi). Mr. Ogi reported during testing of \n the Udpater that a bug prevented it from processing FDA nodes \n in the order specified, which occasionally caused undefined \n errors. The documented order was reestablished. Reported in \n references on one of its subfiles. Reported in NOIS ISL-0897-\n phone conversation with Mr. Ogi.\n \n 17. Updater: return 0 nodes for LAYGO Finding nodes: DICA (for \n Michael Ogi). Mr. Ogi reported during testing of the Updater \n that it was not returning 0 nodes for LAYGO Finding nodes as \n documented. The documented order was reestablished. Reported \n in phone conversation with Mr. Ogi.\n \n 18. Updater: stop errors with LAYGO Finding nodes: DICA1 (for \n Alan Chan). Mr. Chan reported that under some circumstances \n 51962.\n LAYGO Finding nodes were reporting errors instead of finding \n existing entries. The errors were stopped, and LAYGO Finding \n nodes now properly find existing entries. Reported in ISC-SF \n msg # 1170164.\n \n 19. Updater: stop multiple Updaters interference: DICA1 (for \n Travis Torres). Mr. Torres reported that Updaters running \n simultaneously in different processes on the same machine \n could occasionally process each other's FDAs. The code was \n changed to better segregate their data structures. Reported in \n \n phone conversation with Mr. Torres.\n \n Output\n ------\n 20. Sort: remove duplicates from prints: DIO0 (for David \n Alexander, John Harvey, Nancy Nagle, Dan Petit, Daniel \n Schramm, Ellen Zufall, Fil Beza). Many sites reported problems \n with prints in which mnemonic cross-reference entries in the B \n index were creating false positives in reports. Ms. Zufall and \n Mr. Beza identified the problem as introduced by patch \n 2. Compiled Routines: problem uncompiling input templates: \n DI*21*35, and Ms. Zufall fixed it. Reported in ISC-SF msg # \n 1198710, FORUM msg #s 25464901 and 25149562, and NOIS #s SFC-\n 0198-60115, TOP-0198-40108, & WBP-1297-21797.\n \n 21. Transfer: improve performance: DITR, and DITR1 (for Dave \n Bolduc). Mr. Bolduc reported slow performance on large \n transfers, and identified a fix to the problem that was \n gratefully accepted. Reported in NOIS # AIM-0797-N2065.\n \n Special thanks go to Dave Alexander, whose keen eye for bugs\n DIEZ (for Cindy Heuer). Ms. Heuer reported that uncompiled \n saved the rest of the VA a lot of grief with this patch. :)\n \nTest Sites :\n============\n AIM Center\n Boston VAMC\n Bronx VAMC\n Dublin VAMC\n Huntington VAMC\n Oklahoma City VAMC\n input templates would recompile themselves when the \n Prescott VAMC\n Puget Sound HCS\n San Francisco VAMC\n Tuscaloosa VAMC\n Washington VAMC\n West Palm Beach VAMC\n Birmingham CIOFO\n Hines CIOFO\n Salt Lake City CIOFO\n San Francisco CIOFO\n definitions of fields within those templates were changed. \n \nRoutine Summary :\n=================\n The following is a list of the routines included in this\n patch.\n \n The second line of each of these routines now looks like:\n \n <tab>;;21.0;VA FileMan;**patch list**;Dec 28, 1994\n \n Reported in FORUM msg # 23842872.\n (Checksums According to CHECK^XTSUMBLD)\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n DIC1 7440729 7448670 29,41\n DICA 5157184 5237530 6,17,8,41\n DICA1 4597954 5338649 17,41\n DICA2 3685071 3688712 41\n DICF1 5555141 5923519 42,41\n DICF2 5355774 5392088 27,41\n============\n \n DICF3 9189474 9003959 17,42,41\n DICF5 3301437 3486879 17,27,41\n DICL1 2778676 2538541 17,41\n DIEF 6851994 6413098 41\n DIEFU 4587189 4602560 41\n DIEZ 8995968 9310202 41\n DIO0 9392292 9418825 9,21,35,41\n DIPZ0 2495452 2524580 41\n DIR 8414467 8809710 13,24,41\n DIR1 7765832 7982983 6,13,19,41\n Reader\n DIR2 8922361 9053765 41\n DIR3 3670507 2913754 19,41\n DITR 5514796 5528738 6,25,41\n DITR1 6414011 6525800 41\n \n To test if the transport has been corrupted, you can use the\n "Verify Package Integrity" option. This option is under\n Utilities under the KIDS menu. It will compare the checksums\n in the build with the current checksums and list any that\n differ.\n ------\n \nInstallation Instructions:\n==========================\nNOTE any instructions that are different for DSM sites.\n \n 1. Users ARE NOT allowed to be on the system during the\n installation.\n \n 2. Place TaskMan in a WAIT state.\n \n 3. Reader: case sensitivity with codes: DIR1 (for Marcia\n 3. DSM sites: Disable routine mapping (DIC1, DIR, DIR1, &\n DIR2 are usually mapped).\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan\n menu. This option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the Transport\n global.\n \n Insley). Ms. Insley reported that the Reader converted the\n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n INSTALL NAME: DI*21.0*41\n ==========\n case of the user's input for the external form of the codes,\n \n 7. DSM sites: Rebuild your mapped routine set.\n \n 8. Remove TaskMan from its WAIT state.\n but not for the internal. Reported in Forum msg # 23931868.\n \n 4. Reader: list and range problems: DIR3 (for Gary Beuschel).\n Mr. Beuschel reported problem was that the Reader rejects\n This patch contains critical bug fixes requested by package \n lists that contain consecutive numbers out of order, such as\n 50,49; I found that it also rejected a number followed by a\n range ending in that number, such as 50,40-50. Reported in\n ISC-SF msg #s 1190657, 1193613, and 1193773.\n \n 5. Reader: problems with help for dates: DIR, DIR2 (for Gary \n Beuschel). Mr. Beuschel reported that the help for dates is \n scanty compared to what the %DT utility provides. It has been \n brought in line with %DT's, and also made responsive to the \n date parameters passed in the second ^-piece of DIR(0). \n developers in need of the fixes for their own patches or \n Reported by phone.\n \n 6. Reader: DIR("PRE") parameter: DIR (for Gary Beuschel). Mr.\n Beuschel needed a programming hook to let him intercept the\n user's input before the Reader begins its data type\n validation. The new supported input parameter DIR("PRE") is a\n pre-validation transform that can either change X, in which\n case the Reader will proceed as though the new value is what\n the user entered, or can kill X, in which case the Reader will\n behave as though the user entered an illegal value. DIR("PRE")\n package releases.\n executes almost immediately after the READ takes place, just\n after DTOUT is set and before any other checking is done. The\n only inputs are X and DTOUT, and the only outputs are X and\n DTOUT. Reported in phone conversation with Mr. Beuschel.\n \n Lookup\n ------\n 7. Classic Lookup: echo & match lists: DIC1 (for Marcia \n Insley, Tana Defa, and Melissa Hughes). Ms. Insley reported \n during testing of CPRS that Puget Sound needed a change to how \n \n DIC's E flag works. The E flag, which normally ensures a \n user's response is echoed back, did not do so when the user \n picked from a match list, a time when typos are therefore \n difficult to notice but easy to make. This was changed to \n make E work with match list selections. Reported in Forum msg \n # 24573804.\n \n 8. Finder: `IEN lookup problem: DICF1 (for Gary Beuschel). Mr. \n Beuschel reported that the Finder's `IEN lookup is only \n allowing IENs that are integers, disallowing such IENs as the \n Compiled Routines\n Postmaster's (.5). This was fixed. Reported in phone \n conversation with Mr. Beuschel.\n \n 9. Finder: illegal number error: DICF3 (for Bob Fuller). Mr. \n Fuller reported an illegal number error caused by the Finder's \n vulnerability to input that looks like an exponential. The \n Finder has been bullet-proofed. Reported in NOIS # BRX-0397-\n 12605.\n \n 10. Finder & Lister: tolerate empty indexes: DICF2, DICF3, \n -----------------\n DICF5, DICL1 (for Rob Whelan, Deborah Gorman, Diane McCance, \n and Gary Beuschel). Reported in NOIS #s BHH-0897-41483 and \n CLE-0797-42276, and in phone conversations with Mr. Whelan and \n Mr. Beuschel. \n \n Enter & Edit\n ------------\n 11. Filer: prevent variable problem: DIEFU (for Joel Ivey). \n Mr. Joel reported that during testing of Patient Merge, the \n Filer did not adequately protect its own variables from deeply \n 1. Compiled Routines: problem uncompiling xrefs: DIPZ0 (for \n recursive calls, playing havoc during Merge. This was fixed. \n Reported in phone conversation with Mr. Ivey.\n \n 12. Filer: allow deletion of top-level records: DIEF (for & by \n Danila Manapsal). Ms. Manapsal reported that the FileMan \n Components need the ability to delete records through the \n Filer. She corrected the Filer to allow this. Reported in \n phone conversation with Ms. Manapsal.\n \n 13. Updater: allow deletion of top-level records: DICA1 (for \n\n\nThis patch contains routines and Remote Procedures to support the VA\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**34**;Feb 28, 1998\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DDR n/a 7267978 34 \n DDR0 n/a 4956773 34 \nFileMan Delphi Components (FMDC). FMDC provides data controls and data\n DDR1 n/a 1043214 34 \n DDR2 n/a 7680688 34 \n DDR3 n/a 3479219 34 \n \nInstallation Instructions: \n==========================\n \n1. DSM sites: There is no need to map these routines at this time. \n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\naccess components that make it easy to work with VA FileMan data in Delphi\noption will load the KIDS packages onto your system.\n \n3. The patch has now been loaded into a transport global on your system.\nYou now need to use KIDS to install the transport global. \n \n4. On the KIDS menu, under the 'Installation' menu, use the following \noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \napplications.\n Backup a Transport Global \n \n5. Users do not need to logoff. They may remain on the system while\nthis patch is installed.\n \n6. There is no need to place Taskman in a WAIT state.\n \n7. On the KIDS menu, under the 'Installation' menu, use the following \noption: \n Install Package(s): \n \n INSTALL NAME: DI*21.0*34 \n ==========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\nand Protocols?\nRoutine Summary: \n================\n \nThe following routines are included in this patch. The second line of\n\n
\nDescription:\nfields. Patch 42 changed it so that the kill logic on the .01 field fired\n DIK 7352303 7563710 42,47\n DIK1 5943602 6293657 42,47\n DIU0 6188632 6215777 47\n \n \nInstallation Instructions:\n=========================\n \n 1. Users ARE NOT allowed to be on the system during the installation.\n \nfirst.\n 2. Place TaskMan in a WAIT state. \n \n 3. These routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping. If any of the routines\n in this patch are mapped, disable mapping before proceeding. \n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS (Kernel Installation and Distribution System)\n package onto your system.\n \n \n 5. The patch has now been loaded into a transport global on your\n system. On the KIDS menu, select the 'Installation' menu and use the\n following options: \n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s) \n \nThis caused a problem for IFCAP. Cross references on File #421 are defined\n INSTALL NAME: DI*21.0*47\n ==========\n \n 6. MSM-DOS Sites - Answer YES to the question 'Want to MOVE routines\n to other CPUs?'. Enter the names of your Compute and Print server(s).\n \n AXP Sites - Answer NO to this question.\n \n 7. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion.\nin such a way that when a record is deleted, if the kill logic for the .01\n \n 8. Remove TaskMan from a WAIT state. \nfield is fired before the kill logic on other fields, an erroneous "AL"\ncross reference remains on the file. Erroneous "AL" cross references can\ncause subsequent errors when attempts are made to release transactions.\n \nThis patch restores the pre-Patch 42 behavior, so that the kill logic on\n===========\nthe .01 field fires last when a record is deleted.\n \n NOIS: ALT-0698-21639\n SAM-0698-20488\n SAJ-0698-70174\n CIH-0598-41816\n NYN-0598-11513\n MEM-0598-71203\n LOU-0598-40986\n SAM-0498-22344\nThis patch corrects some problems with record and file deletion.\n EKH-0498-41197\n SBY-0498-31176\n MAC-0498-61095\n PRE-0498-61070\n SFC-0498-60956\n MEM-0498-70661\n ELP-0398-72724\n GAI-0398-32657\n LAK-0398-32457\n SFC-0398-62414\n \n NYN-0398-10170\n MWV-0298-21129\n BRX-0298-10388\n WAS-0198-22126\n BYN-0198-11150\n PUG-0198-51131\n MCM-0198-51046\n HAC-0198-51043\n SFC-0198-60783\n GAI-0198-30228\nDIK,DIK1\n CLA-0198-20132\n MIN-1297-41083\n HVH-0997-11397\n TUC-0997-61281\n \n \nDIK,DIK1\n--------\nWhen many fields in a file are being audited, and ^DIK is used to delete\nentries in file, or the entry points to ^DIK are used to reindex entries,\n--------\nthe DIAU array could get very large and cause an allocation error when the\nlocal symbol table fills up.\n \n NOIS: ISB-0397-32129\n TAM-0896-30558\n \n \nDIU0\n----\nIf EN^DIU2 is used to delete a file that has a global root of\nThe patch to these two routines backs out a change made by Patch DI*21*42.\n^DIC(FileNumber), and the DIU input variable contains the global root\nwithout a trailing comma (e.g., "^DIC(81.2" ), EN^DIU2 proceeded to delete\nFile #1. This patch makes EN^DIU2 check that the global root passed in DIU\nends in either a comma or a close parenthesis.\n \n NOIS: ISA-0497-11765\n \n \nTest Sites:\n==========\nPrior to patch 42, when a record is deleted with ^DIK, the kill logic on\n Salem, VA\n Central Iowa\n Memphis, TN\n Tuscaloosa, AL\n \n \nRoutine Summary:\n===============\nThe following routines are included in this patch. The second\nline of each of these routines now looks like:\nthe .01 field of the record fired last, after the kill logic on other\n \n <tab>;;21.0;VA FileMan;**patch list**;Dec 28, 1994\n \n \nChecksums\n=========\nChecksums obtained using CHECK^XTSUMBLD.\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n\n
\n \n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIPRE 969775 46\n \n Installation Instructions: \n ==========================\n \n The pre-install routine DIPRE moves the two Y2K functions NUMDATE4 and\n 1. Mapping need not be disabled, users need not log off, and TaskMan\n need not be in a WAIT state.\n \n --- Pre-Installation Steps ---\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n NUMYEAR4 into the protected FileMan numberspace of the FUNCTION file.\n \n 4. On the KIDS menu, under the 'Installation' menu, optionally use the\n following options: Print Transport Global Compare Transport Global to\n Current System Verify Checksums in Transport Global Backup a Transport\n Global \n \n --- Actual Installation ---\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option: \n \n \n Install Package(s): \n INSTALL NAME: DI*21.0*46 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols?' \n \n **Please Note: At the DEVICE prompt, this install may be\n Queued to a print device.\n Routine Summary: \n \n This completes the installation instructions.\n ================\n The following routine is included in this patch. Its second line \n will look like: \n <tab>;;21.0;VA FileMan;**46**;Dec 28, 1994 \n\n
\nDescription:\n \nNOIS:\n=====\nDAY-0697-42372\n \nThanks to Test Sites:\n=====================\nDayton, OH\nClarksburg, WV\nMuskogee, OK\n============\n \nRoutine Summary: \n================\n \nThe following routine is included in this patch. The second line of the\nroutine now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \nIf a programmer sets ^UTILITY($J,"W") but there are no descendants, DIWW\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIWW 5618941 5644162 15,51\n \nInstallation Instructions: \n==========================\n \n This patch may be installed anytime during non-peak activity and\nmay be Queued to install during non-peak hours. The installation time will\nwould go into a self-contained loop. The FileMan Programmer Manual states\nonly take a couple of minutes.\n \n 1. Routine mapping is NOT recommended for this routine. If you are\nusing routine mapping, ensure that this routine is NOT in your mapped\nroutine set before proceeding.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a transport global on your\non page 138, when talking about DIWP, that the programmer should Kill\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n^UTILITY($J,"W") prior to calling DIWP and DIWW. However, it was\n 5. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*51\n ==========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nrecognized that the Kill may not always take place and, therefore, there\nother CPUs?'. Then enter the names of your other Compute and Print\nserver(s).\nwas a possibility of an internal loop. A check is now made that if\n^UTILITY($J,"W") exists and there are no descendants, DIWW Quits.\n\n
\nDescription: \nrecursion until it ran out of stack space. \ninstallation starts!! \n \n 9. MSM Sites - After the installation begins, you will be prompted \nto enter a DEVICE. After the device has been entered, KIDS will pause. \nAt this time, you need to go to each of the CPUs that were entered in \nstep 8, and start a job that will allow them to receive the patched \nroutines. On each one, you do the following: \n \n a) >D ^XUP This will set up the programming environment. \n ====== \n \n b) >D ^XPDCPU This starts the job that receives the patched routines. \n ========= \n c) Select INSTALL NAME: DI*21.0*27 \n ========== \nThe installation will then continue. \n \n 10. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 11. Enable users' login.\nThere are two other independent problems at these sites that this patch \ndoes not fix: the problem with WRITE commands in the data dictionaries of \nsome of the files involved, which must be manually replaced by the \napplication or local developers; and a PCMM bug that caused allocation \nerrors when a patient lookup value produced too many possible matches, \nwhich is fixed by an upcoming PCMM patch. These problems were reported by \nthe following NOISes: SPO-0896-50876, POR-0896-50871, IND-0796-40935, \nALB-0796-51236, and MGY-0796-30889. (DICF, DICF2, DICF5) \n============ \n \n2. It makes the Finder tolerate being called by the FileMan Database \nServer (DBS) when DIERR is already defined. This change is needed by \npatch DI*21*8, which is simultaneously under development. Because this \nfix changed the routine DICF, also changed by the fix to the problem \ndescribed above, it was moved out of DI*21*8 and into DI*21*27 to make \nthe simultaneous development of these two patches easier to coordinate. \n(DICF) \n \nRoutine Summary: \n \n================ \n \nThe following routines are included in this patch. The second line of \nthese routines now looks like: \n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \nThis patch fixes two problems: \n ============ ============ =========== ========== \n DICF 6981054 7062808 17,27 \n DICF2 5350507 5355774 27 \n DICF5 2906278 3301437 17,27 \n \nInstallation Instructions: \n========================== \n \n 1. Although routine mapping is NOT recommended for these routines, \nyour mapped set may include routines not usually recommended for mapping. \n \nIf these routines are in your local map set, disable mapping for them \nbefore proceeding with the installation, and rebuild your map set \nafterward before reactivating TaskMan.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system. The environment \ncheck routine, DIENV, will run automatically.\n \n DIENV is sent to prevent the inadvertent queuing of the installation \nof this patch. \n1. It prevents the allocation errors that have plagued PCMM sites. These \n \n 3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the \nfollowing options:\n \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \nFinder errors arose from stack overflow caused when using PCMM to lookup \n Backup a Transport Global \n \n 5. Inhibit users from login into the system. The consequence of \nhaving users on the system while installing this patch are that users \nlooking up records will get a 'source routine edited' error. Although \nthese routines are not heavily used in DHCP applications yet, they are \nused increasingly in new application such as PCMM. \n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \nPatients. The Finder was not detecting and protecting itself from pointer \n \n 7. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*27\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \nOptions, and Protocols?\nchains that loop back on themselves, causing the Finder to go into \n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to \nother CPUs?'.\n \n Then enter the names of your other Compute and Print server(s).\n \n NOTE: You will then see the following message:\n \n TASKMAN is not running. You must run the routine XPDCPU in the \nproduction UCI for each of the VOLUME SETS you have listed once the \n\n
\nWhen a user is using FileMan's Search option and uses a Condition of\ncausing a <syntax> error. The invalid code looks like the following\nexample:\n \nI $S($D(^DIZ(640999,D0,1)):$P(^(1),U,1),1:"")?300.4\n \nThis patch prevents the user from entering an invalid pattern matching\ncode.\n \nRelated NOIS: \n=============\nMATCHES and enters an invalid 'M' pattern match the report will error out.\nCHY-0498-50998\n \nThanks to Test Sites: \n=====================\nCheyene, WY\nClarksburg, WV\nDayton, OH\n \nRoutine Summary: \n================\nFor example:\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIM2 4186487 4310650 28,48\n \n DIS 8071449 8038501 48\n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is\nrecommended that it be Queued for a time of generally least activity.\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutines listed in the ROUTINE SUMMARY section are mapped, they should be\nremoved from the mapped set at this time.\n -A- SEARCH FOR MYFILE FIELD: NUMBER CODE\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \n -A- CONDITION: MATCHES\n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n \n 5. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*48\n ==========\n \n -A- MATCHES: 300.4\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Then enter the names of your other Compute and Print\nserver(s).\n \n 7. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \nWith the result that invalide 'M' pattern matching code was generated,\n\n
\nThis patch fixes a bug and contains information and examples on how to\n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is\nrecommended that it be Queued for a time of generally least activity.\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nbe removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \nIn the following example, a user whose DUZ(0)'["@" would see the SSN\noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \nprinted twice, whereas the user whose DUZ(0)["@" would see the Patient's\n Backup a Transport Global\n \n 5. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*53 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\nSSN printed once.\n \n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Then enter the names of your other Compute and Print\nserver(s).\n \n 7. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n S FLDS=".01;C1;L22;""PATIENT"",D SSN^MYPROG;C24;R4;""SSN"""\n \n Routine called:\n MYPROG ;SFCIOFO/S0 TEST ROUTINE ; 21 Aug 98 2:06 PM\n SSN ;\ncall an 'M' routine from a print template or the FLDS input variable to\n K VA,VADM S DFN=D0 D ^VADPT\n S X=$P(VA("PID"),"-",3)\n W X\n Q\n \nInformation:\n-----------\nIf you use the FLDS input variable to EN1^DIP or a print template to call\nan 'M' routine to evaluate and print a value, you must WRITE the value you\nwant printed. Examples 1 and 2 below illustrate how this is done.\nEN1^DIP.\n \nExample #1: The routine is called from a Print Template\n=======================================================\n \nPrint Template:\nNAME: ZZ640A DATE CREATED: AUG 13, 1998@10:21\n READ ACCESS: @ FILE: MY PATIENT\n USER #: 133 WRITE ACCESS: @\n DATE LAST USED: AUG 14, 1998\nHEADER (c): MY PATIENT LIST\n \nFIRST PRINT FIELD: NAME;C1;L22;"PATIENT"//\nTHEN PRINT FIELD: D SSN^MYPROG;X\nTHEN PRINT FIELD: W X;C24;R4;"SSN"//\nCOMPILED (c): NO\n \nRoutine Called:\nMYPROG ;SFCIOFO/S0 TEST ROUTINE ; 21 Aug 98 2:06 PM\nSSN ;\n K VA,VADM S DFN=D0 D ^VADPT\n S X=$P(VA("PID"),"-",3)\nBug fixed:\n Q\n \nExample of Usage:\nZZ640A ;SFCIOFO/S0 TEST FILEMAN PRINT ; 19 Aug 98 4:03 PM\n S DIC="^DIZ(640001,",BY=".01",L=0,FR=""\n S FLDS="[ZZ640A]"\n D EN1^DIP\n Q\n \nExample #2: The routine is called from the FLDS input variable\n---------\n==============================================================\n \nRoutine Called:\nMYPROG ;SFCIOFO/S0 TEST ROUTINE ; 21 Aug 98 2:06 PM\nSSN ;\n K VA,VADM S DFN=D0 D ^VADPT\n S X=$P(VA("PID"),"-",3)\n Q\n \nExample of Usage:\nIf the FLDS input variable to EN1^DIP contains a call to an 'M' routine,\nZZ640A ;SFCIOFO/S0 TEST FILEMAN PRINT ; 19 Aug 98 4:03 PM\n S DIC="^DIZ(640001,",BY=".01",L=0,FR=""\n S FLDS=".01;C1;L22;""PATIENT"",D SSN^MYPROG;X,W X;C24;""SSN"""\n D EN1^DIP\n Q\n \nNOIS: \n=====\nISB-0898-30889\n \nthe resulting report may differ depending on whether or not the user's\nThanks to Test Sites: \n=====================\nDayton, OH\nClarksburg, WV\nCIOFO-Birmingham \n \nRoutine Summary: \n================\n \nThe following routines are included in this patch. The second line of\nDUZ(0) contains an at-sign (@).\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIP22 6639498 6717942 53 \n \n\n\nThis patch corrects a problem when using FileMan Sort/Print functions that\nNAME\n--------------------------------------------------------------\n \n *** NO RECORDS TO PRINT ***\n \n \nIt will now look like:\n \nMY REPORT Aug. 28, 1998 PAGE 1\nNAME\nhave statistical operations within Sort/Print logic and there were NO\n--------------------------------------------------------------\n \n *** NO RECORDS TO PRINT ***\n \nNOIS: \n=====\nAUG-0695-30662\nISW-0197-21444\nISW-0798-22049\n \nRECORDS TO PRINT. The problem was the statistical line(s) would print\n \nThanks to Test Sites: \n=====================\nDayton, OH\nClarksburg, WV\nCIOFO-Washington\nCIOFO-Albany\n \n \nRoutine Summary:\nbefore the header and the No Records To Print message. For Example:\n================\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n \n DIO4 5969086 6003254 54\n \n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is \nrecommended that it be Queued for a time of generally least activity.\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nTOTAL 0.0\nbe removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n ------\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n \n 5. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*54\n ==========\n \n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Then enter the names of your other Compute and Print \nserver(s).\n \n 7. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\nMY REPORT Aug. 28, 1998 PAGE 1\n\n
\n \nonto your system. The problem was that if a developer changed the name of \na file or subfile the INIT would add another 'NM' node, instead of \nremoving the old 'NM' node and then adding the new node. \n \nThis patch corrects these duplicate "NM" nodes located in: \n^DD(<file/subfile#>,0,"NM",<file name>)="" \nusing the same logic that FileMan Option: \nCheck/Fix DD Structure [DI DDUCHK] uses when Fix is specified. \n \nThe routine DIPR50 loops through all of the DHCP files, looking for \n Notice:\nduplicate "NM" nodes and corrects any duplicates that are found. The\nfollowing is a sample dialog when a duplicate 'NM' node is encountered:\n \nFile/Subfile: 662001 has duplicate 'NM' nodes.\n Duplicate 'NM' node(s) were deleted and fixed.\n 'NM' node will be set to: ZZTAMI TEST\n \n \nRelated NOIS: \n=============\n ** This patch should be installed with NO users online ** \nCTX-0397-71390 \nTUA-0798-31699 \n \nThanks to Test Sites: \n=====================\nClarksburg, WV\nTuscaloosa, AL \nCentral Texas HCS \nDayton, OH\nSeveral CIOFOs\n \n \nRoutine Summary: \n================\nThe following routine is included in this patch. The second line of \nthis routine looks like: \n<tab>;;21.0;VA FileMan;[patch list];Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \nRoutine Name Before Patch After Patch Patch List \nBackground: PreKIDS - when packages were installed, a set of routines were\n============ ============ =========== ==========\nDIPR50 N/A 982490 50 \n \nInstallation Instructions: \n==========================\n \n 1. There is no routine mapping involved. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nThis option will load the KIDS package onto your system. \ncreated by the developer(s) to export Data Dictionary changes.\n \n 3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to finish the preperation for \ninstallation. \n \n 4. Optionally on the KIDS menu, under the 'Installation menu', \nuse the following options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global. \n \n \n 5. Inhibit users' login into the system. The consequence of having \nusers on the system while installing this patch are that users editing \nrecords will get an Undefined error, the edits will be lost and records \nmay be left in an inconsistent state. Note that most of these \nDD's are heavily used in DHCP applications. \n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \nThese were in the form of <nmsp>INIT. From the programmer prompt you \n 7. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*50 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \nOptions, and Protocols? \nNote to MSM Sites - Answer NO to the question 'Want to MOVE routines to \nother CPUs?'. \nwould D ^<nmsp>INIT, i.e. D ^ABCINIT, and the package would be installed \n \n 8. Restart TaskMan, any background filers, and reenable user \nlogons. \n \n 9. You may now delete DIPR50. \n\n
\nBug Fixes\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 6. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\nSelect OPTION: PRINT FILE ENTRIES \n \nOUTPUT FROM WHAT FILE: PATIENT// \nSORT BY: NAME// RAD/NUC MED PATIENT:\n By 'RAD', do you mean the RAD/NUC MED PATIENT File,\n pointing via its 'NAME' Field? Yes// (Yes)??\nSORT BY: NAME// \n \nThis problem is fixed with this patch.\n=========\n \n3. When 2 separate fields are defined as Pointer to a File and they point\nto the same file and they are printed one after each other, an error would\noccur. For example:\n \nSelect OPTION: PRINT FILE ENTRIES\nOUTPUT FROM WHAT FILE: S0 TEST #1// \nSORT BY: NAME// \nSTART WITH NAME: FIRST// \nFIRST PRINT FIELD: PT200A:\n1. If a computed field expression was too complex for DICOMP to interpret,\n THEN PRINT NEW PERSON FIELD: SSN \n THEN PRINT NEW PERSON FIELD: \nTHEN PRINT FIELD: PT200B:\n THEN PRINT NEW PERSON FIELD: SSN \n THEN PRINT NEW PERSON FIELD: \nTHEN PRINT FIELD: \n \nNOISes\n======\nBRX-1297-10331\nan error would result. With this patch, if an expression that is too\nBRX-0397-12607\nWRJ-0497-10294\nDAY-0997-40744\nREN-1097-61379\nWBP-0196-21370\nBRX-0995-11874\nFNC-0494-30103\n \n \nThanks to Test Sites\ncomplex is entered, a beep and '??' will be displayed.\n====================\nWhite River Junction, VT\nBronx, NY\nDayton, OH\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DICOMP1 6095234 6197157 52\n DICOMPV 7196555 7170031 13,52\n DICOMPW 8864346 8886232 52\n DICOMPX 3767023 3939321 24,52\n2. If a backward extended pointer was used, and the name of the file\n DIL1 6752508 6849303 52 \n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is \nrecommended that it be Queued for a time of generally least activity.\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nbe removed from the mapped set at this time.\ncontained a '/', the expression was rejected with a beep and '??'.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \nFor example:\n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n \n 5. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*52\n ==========\n \n\n
\n Description:\n \n \n 8. AXP Sites - After the patch has been installed, rebuild your map\n set, if necessary. \n \n 9. AXP Sites - Remove Taskman from WAIT State. \n OpenM/Cache Sites - Restart Taskman. \n \n 10. Enable users' login.\n For example, if the codes are:\n \n & AND\n &' AND NOT\n ! OR\n !' OR NOT\n \n and the value 'AND' is passed to the Updater with "E" flag, the message:\n \n ============\n The value 'AND' for field xxxxx in file xxxxx is not valid.\n \n With this change, if the external code is ambiguous but exact, the value\n is accepted. Also, display a 4-digit year in the prompt for a Date read,\n when an earliest and latest date are specified or in the error message\n when the date entered is out of the specified range.\n \n NOIS:\n =====\n DAY-0698-41519\n ** NOTICE: It is HIGHLY recommended that all users be logged off the\n ISL-1297-50203\n MIA-0698-31649\n \n Thanks to Test Sites:\n =====================\n Dayton, OH\n Salt Lake City CIOFO\n Fargo, ND\n Clarksburg, WV\n \n VistA system. **\n Routine Summary: \n ================\n \n The following routines are included in this patch. The second line of\n these routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n CHECK^XTSUMBLD results: \n \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIR1 7982983 8449705 6,13,19,41,49\n DIR2 9053765 9159183 41,49\n \n Installation Instructions: \n ==========================\n ** It is HIGHLY recommended that ALL Users and VISTA Background jobs to\n be STOPPED. Failure to do so may result in a 'source routine edited'\n error, the edits will be lost and records may be left in an inconsistent\n Prior to this change, VAL^DIE and the DBS calls that use it, like\n state. **\n \n 1. AXP sites: Review your mapped routine set. If any of the\n routine(s) listed in the ROUTINE SUMMARY section are mapped, they should \n be removed from the mapped set at this time. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n \n The environment check routine DIENVWRN will run automatically. Routine\n UPDATE^DIE and FILE^DIE, were returning Dialog Error message #701 when an\n DIENVWRN is sent in order to prevent the inadvertent queuing during the \n installation of this patch. \n \n 3. The patch has now been loaded into a transport global on your\n system. You now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the\n following options: \n Print Transport Global \n Compare Transport Global to Current System \n external form of a set of codes field was passed in, but the external\n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of having\n users on the system while installing this patch are that users editing\n records will get a 'source routine edited' error, the edits will be lost\n and records may be left in an inconsistent state. Note that most of\n these routines are heavily used in DHCP applications. \n \n 6. AXP Sites - Place Taskman in a WAIT State. \n code was ambiguous.\n OpenM/Cache Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\n following option:\n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*49\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? \n\n
\n ** NOTICE: It is HIGHLY recommended that all users be logged off\nproblem.\n \nNOIS\n====\nCLA-1298-20489\nMUS-1298-70900\n \nThanks to Test Sites\n====================\nMartinez, CA\n the VistA system. **\n \n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIR1 8449705 8500908 6,13,19,41,49,57 \n \nInstallation Instructions: \n==========================\n \n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to be\n STOPPED. Failure to do so may result in a 'source routine edited'\nBug Fix\n error, the edits will be lost and records may be left in an\n inconsistent state. **\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nbe removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system.\n \n=======\nThe environment check routine DIENVWRN will run automatically. Routine\nDIENVWRN is sent in order to prevent the inadvertent queueing during the\ninstallation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n Print Transport Global \nThis patch fixes the following problem: \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n \n 5. Inhibit users' login into the system. The consequence of having\nusers on the system while installing this patch are that users editing\nrecords will get a 'source routine edited' error, the edits will be lost\nand records may be left in an inconsistent state. Note that most of these\nroutines are heavily used in DHCP applications.\n \n When a user answered the Alert prompt for what action to take, they\n 6. AXP Sites - Place Taskman in a WAIT State. \n OpenM/Cache Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*57\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\ncould inadvertenly enter a control character (i.e. BackSpace, Tab) which\nOptions, and Protocols?\n \n \n 8. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary. \n \n 9. AXP Sites - Remove Taskman from WAIT State. \n OpenM/Cache Sites - Restart Taskman. \n \n 10. Enable users' login.\nwould cause a looping within the DIR* routines. This patch corrects that\n\n
\nBug Fix\nremove any of the erroneous entries.\n \nNOIS: \n=====\nCHA-0299-32411\nDAY-0399-42742\n \nThanks to Test Sites: \n=====================\nDallas CIOF\n=======\nDayton, OH\n \nRoutine Summary:\n================\n \nThe following routine is included in this patch. The second line of\nthe routine now look like: \n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIPR58 N/A 1686734 58\n \nInstallation Instructions: \n==========================\n \n This patch may be installed anytime during non-peak activity\nFile #1 has a multiple called APPLICATION GROUP (Field #10) and on this\nand may be Queued to install during non-peak hours. The installation\ntime will only take a couple of minutes. \n \n 1. Routine mapping is NOT recommended for this routine. If you\nare using routine mapping, ensure that this routine is NOT in your\nmapped routine set before proceeding. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\nThis option will load the KIDS package onto your system. \n \nmultiple there is a whole file cross reference - "AC". It was\n 3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the \nfollowing options: \n \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \nrecently discovered that at some time in a past version that this cross\n \n 5. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option: \n \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*21.0*58 \n ==========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \nOptions, and Protocols? \n \nreference was not being properly killed off. This patch will go through\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines\nto other CPUs?'. Then enter the names of your other Compute and Print \nserver(s). \n \n 7. You may now delete DIPR58. \nthis cross reference and remove any of the erroneous entries. The routine\nwill also check the APPLICATION GROUP multiple's "B" cross reference and\n\n
\n1. Most of the routines included in this patch support Laboratory's\npoint. \noption will load the KIDS package onto your system. The environment check\nroutine DIENV will run automatically.\n \n DIENV is sent in order to prevent the inadvertent queueing of the\ninstallation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n \noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users from login into the system. Some of the routines\nbeing patched are used all over FileMan. Having users on the system\nduring installation could result in incomplete records or CLOBBER errors.\n \nThe complete API description is available on the Software Service web page\n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*8 \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nat URL:\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n Then enter the names of your other Compute and Print server(s).\n NOTE: You will see the following message:\n TASKMAN is not running. You must run the routine XPDCPU in the\nproduction UCI for each of the VOLUME SETS you have listed once the\ninstallation starts!!\n \nhttp://www.vista.domain.ext/softserv/infrastr.uct/fileman/docs/pm/ft_diaxu\n 9. MSM Sites - After the installation begins, you will be prompted to\nenter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\neach one, you do the following:\n a) >D ^XUP This will set up the programming environment.\n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*8 \n.htm\n =========\nThe installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your map\nset. \n \n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 12. Enable user's login. \n \n B. New API: EXTRACT^DIAXU: \n \nEXTRACT^DIAXU is a new entry point, introduced by patch DI*21*8. The main\narchiving functions described in patch LR*5.2*59.\nnew features introduced with this entry point for extracting data are:\n \n * More than one record can be extracted in a call. \n * Subrecords can be extracted as individual transactions. Previously,\n an entire record including all subrecords had to be extracted as a \n single entity. \n * DBS-style error reporting is used. \n \nThe complete API description is available on the Software Service web page\nat URL:\n \nhttp://www.vista.domain.ext/softserv/infrastr.uct/fileman/docs/pm/ft_diax2\n.htm\n \n2. This patch also contains a fix for the DIVR routine. When you use the\n'Utility Functions/Verify Fields' option to check a date/time field that\ncan contain seconds, if the data has a time between 1 and 59 seconds after\nmidnight (nnnnnnn.000001 through nnnnnnn.000059) the data was flagged as\nnot valid.\n \n3. The DIV routine in this patch has been modified to provide a way for\n A. Changes to EN^DIAXU API: \ncustomized input transforms to skip certain checks when the 'Verify\nFields' Utility Function is used. The variable to check is DIUTIL. It is\nset equal to the string "VERIFY FIELDS" when the 'Verify Fields' option is\nrunning. (DIV)\n \n4. The changes made by some of the init routines in this patch are\nnecessary to make some corrections to FM's files. The new post-install\nroutine, DIPOST, will make these corrections automatically. IT IS NOT\nNECESSARY TO REINITIALIZE FILEMAN.\n \n \nRoutine Summary: \n================\n \nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \nCHECK^XTSUMBLD results: \n \nWith patch DI*21*8, the extract tool has been enhanced to use FileMan's\n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIARA 14770992 14013708 8 \n DIARB 7839337 6210401 8 \n DIAX 7377151 11305747 8 \n DIAXD N/A 11580617 8 \n DIAXERR 2053556 600222 8 \n DIAXF N/A 373535 8 \n DIAXM1 4345149 4416751 8 \n DIAXP N/A 2094474 8\ndatabase server calls (DBS) in order to take advantage of the more\n DIAXT N/A 1965631 8 \n DIAXU 4749815 7159038 8 \n DIC 9799355 9887383 8 \n DICA 5077499 5157184 6,17,8 \n DICL 4552973 4619639 17,8 \n DICU 2626995 3150917 8 \n DICU1 5290202 5260389 17,8 \n DIDU 5942346 6142297 6,17,8 \n DIFGB 7763085 7602021 8 \n DIFROM11 8986254 9004800 8 \nintelligent error handling in the DBS calls. This change has resulted in a\n DIFROMS5 3330062 3339695 6,8 \n DINIT 14307293 14339269 8 \n DINIT13 10341008 9427999 8 \n DINIT3 9096420 9152081 8 \n DIOU 4893133 4914520 8 \n DIPOST N/A 159247 8 \n DIQGU 4906837 4937798 8 \n DIV 3715836 3841210 8 \n DIVR 6095014 6153747 8 \n DIVR1 N/A 10768511 8 \nnumber of changes to the input and output variables of the EN^DIAXU entry\n DIVU N/A 3100544 8 \n \nInstallation Instructions: \n==========================\n \n 1. Two of the routines in this patch, DIC and DIOU, are usually\nmapped on systems that allow mapping, AXP sites will need to disable\nmapping for these routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n\n
\nThis patch fixes the following problem:\n \n MSM Sites - Restart Taskman.\n \n 12. Enable users' login.\nRoutine Summary:\n================\n \nThe following routine is included in this patch. The second line of\nthis routines now looks like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994\n \nCHECK^XTSUMBLD results:\n \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n DICU1 5260389 5299469 17,8,31\n \nInstallation Instructions:\n==========================\n \n 1. AXP Sites - Although routine mapping is NOT recommended for this\nroutine, your mapped set may include routines not usually recommended for\n1. PCE sites have reported sluggish performance. Skip Ormsby at \nmapping. If this routine is in your local map set, disable mapping for it\nbefore proceeding with the installation, and rebuild your map set\nafterward before reactivating TaskMan.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. The environment\ncheck routine, DIENV, will run automatically.\n \n DIENV is sent to prevent the inadvertent queuing of the installation\nof this patch.\nClarksburg has tracked this to the activities of the FileMan Lister when \n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\nit is used on the ICD9 file. The ICD9 file lacks a B index, and the \n Backup a Transport Global\n \n 5. Inhibit users from login into the system. The consequence of\nhaving users on the system while installing this patch is that users\nlooking up records will get a 'source routine edited' error. Although\nthis routine is not heavily used in DHCP applications yet, it is\nused increasingly in new application such as PCE.\n \n 6. AXP Sites - Place Taskman in a WAIT State.\n MSM Sites - STOP Taskman.\nLister recreates and later deletes a temporary B index before each call \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*31\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\nfor that file. The Lister should only do that when asked to use the \n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n \n Then enter the names of your other Compute and Print server(s).\n \n NOTE: You will then see the following message:\n \n TASKMAN is not running. You must run the routine XPDCPU in the\nproduction UCI for each of the VOLUME SETS you have listed once the\nmissing B index, but always does due to a bug introduced by DI*21*8. \ninstallation starts!!\n \n 9. MSM Sites - After the installation begins, you will be prompted\nto enter a DEVICE. After the device has been entered, KIDS will pause.\nAt this time, you need to go to each of the CPUs that were entered in\nstep 8, and start a job that will allow them to receive the patched\nroutines. On each one, you do the following:\n \n a) >D ^XUP This will set up the programming environment.\n ======\nAfter installing this patch, PCE's performance should noticeably improve.\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*31\n ==========\nThe installation will then continue.\n \n 10. AXP Sites - After the patch has been installed and IF you\ndisabled your map set (step 1 above), rebuild your map set.\n \n 11. AXP Sites - Remove Taskman from WAIT State.\n\n
\nThis patch fixes 2 problems:\nare KNX-0396-41289 and WCO-0195-50090. (DIDT)\nset. \n \n 12. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman.\n \n 13. Enable users' login. \n \nRoutine Summary:\n================\n \nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIDT 6670456 6692350 18\n DIDTC 7237147 7334026 18\n \nInstallation Instructions: \n==========================\n \n1. This patch fixes a very specific problem with converting time at \n 1. The routines %DT and %DTC are usually mapped on systems that allow\nmapping. AXP sites will need to disable mapping for these routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system. The environment check\nroutine DIENV will run automatically.\n \n DIENV is sent in order to prevent the inadvertent queueing of the\ninstallation of this patch.\n \nmidnight. The related NOIS is BTM-1095-13315. (DIDTC)\n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n \n 5. Inhibit users' login into the system. If users are on the\nsystem, you run the risk of getting incorrect 'date with time'\nvalues and/or CLOBBER errors. Due to the high usage of these routines in\nall of DHCP code, it is highly recommended that users get off the system\nwhen installing this patch.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\n2. Before this patch, %DT was accepting input that consisted of 8 or more\noption: \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*18\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\nnumerics as long as the first 7 digits formed a valid date in FM internal\n Then enter the names of your other Compute and Print server(s). \n NOTE: You will then see the following message: \n TASKMAN is not running. You must run the routine XPDCPU in the \nproduction UCI for each of the VOLUME SETS you have listed once the \ninstallation starts!! \n \n 9. MSM Sites - After the installation begins, you will be prompted to\nenter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\nformat and %DT contained a "T". For example, %DT interpreted 604011422 as\neach one, you do the following:\n a) >D ^XUP This will set up the programming environment. \n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*18\n ==========\nThe installation will then continue. \n \n 10. After installing this patch, you need to move these routines\nJan 14, 2304. This patch makes %DT reject such input. The related NOIS's\nfrom your production account to the manager account:\n DIDT, DIDTC\n and in the manager account rename\n DIDT to %DT\n DIDTC to %DTC\n \n Example: ZL DIDT ZS %DT\n ZL DIDTC ZS %DTC\n \n 11. AXP Sites - After the patch has been installed, rebuild your map\n\n
\nThis patch fixes a few bugs related to word-processing fields:\nNOWRAP function is used. (DIWP, TUA-1094-30461)\n 11. AXP Sites - Remove Taskman from WAIT State. \n MSM Sites - Restart Taskman. \n \n 12. Enable users' login. \n \n4. This patch prevents an infinite loop from happening when DIWL=0 and a\ncall to ^DIWW is made. (DIWP, NOIS BRX-0995-11453)\n \n5. This patch allows the 'Transfer Text' Edit option from an EN^DIWE\ncall provided that the text being edited is a FM word-processing field.\n(DIWE)\n \n Routine Summary: \n \n ================\n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n1. This patch fixes problems with the 'Transfer Text' Edit option.\n DIWE 6067379 5827467 33\n DIWE3 8633894 12713274 33\n DIWE4 9748975 9685833 33\n DIWE5 8399507 7891987 33\n DIWP 5103576 5150036 33\n \n Installation Instructions: \n ==========================\n \n 1. The routines DIW* are usually mapped on systems that allow\n(DIWE3,DIWE5, NOIS BRX-0495-10374))\nmapping. Alpha sites that use routine mapping will need to disable\nmapping for these routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. The environment check\nroutine DIENV will run automatically.\n \n The Environment Check routine, DIENV, is sent in order to prevent the\ninadvertent queueing of the installation of this patch.\n \n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n2. This patch fixes the header that gets printed when using the Print\n 5. Inhibit users from login into the system. If users stay on the\nsystem while installing this patch, a hard error may occur while word\nprocessing fields are printed or edited.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n Select Installation Option: Install Package(s)\noption from the Line Editor. (DIWE4)\n Select INSTALL NAME: DI*21.0*33\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n Then enter the names of your other Compute and Print server(s). \n NOTE: You will then see the following message: \n \n TASKMAN is not running. You must run the routine XPDCPU in the \nproduction UCI for each of the VOLUME SETS you have listed once the \ninstallation starts!! \n \n 9. MSM Sites - After the installation begins, you will be prompted to\nenter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\neach one, you do the following:\n a) >D ^XUP This will set up the programming environment. \n3. This patch prevents the printing of duplicate last lines when the\n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*33\n ==========\nThe installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your map\nset. \n \n\n
\nThis patch fixes the following problems:\nwere a lookup cross reference, and could pick up the wrong field. (DDS0)\n string 18 string 18a \n string 19 string 19a \n Enter RETURN to continue or '^' to exit: \n -------------------------------------------------------------------------\n \nString 15a should have printed next to string 15, but instead printed on\nthe subsequent screen on a line by itself. \n \nThis change fixes this problem. (DDSMSG)\n \n \n12. This patch fixes and enhances the POINTER LINK property of blocks.\nSuppose you want to display, in a repeating block, entries in a file\nreached via a backward pointer and then from one of those entries,\nyou want to follow a forward pointer and branch to a page to display\nentries from the pointed-to file. No POINTER LINK syntax would allow you\nto define this relationship. The reference point for the POINTER LINK\nneeded to be the Primary File of the form, and the syntax didn't allow for\nnavigation via a backward pointer.\n \nThis patch introduces the syntax: \n3. If the last field on a block is uneditable, and you pressed <Up> or\n \n DD(file#,pfield#) or [DD(file#,pfield#1):pfield#2...] \n or DD(file#,field#) \n \nto the POINTER LINK, where file# is the point of reference to start the\nnavigation, pfield# is the pointer field that points to the file defined\nby the block's DD#, and field# is the field used as a lookup value in the\nfile defined by the blocks DD#. \n \nThis patch also allows for navigation via a variable pointer:\n<PF4> from another block or from the Command Line to this field, the\n \n vpfield#:file# \n or vpfield#:file#:pfield:pfield#... \n \nwhere vpfield# is a the number of a variable pointer field. The key \ndifference is that you can specify the file# to which to navigate.\n(DDSPTR)\n \n13. If DDSBR was set to "fieldId^blockId^pageId", and blockId was the\nBlock Name rather than the Block Order number, ScreenMan disregarded the\ncursor would appear to be stuck, and would remain in its current location.\nblockId and automatically assumed the first block on the page. (DDS2)\n \n \nRoutine Summary: \n===============\n \nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n(DDS01)\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DDS0 3530371 3556700 4,11,20\n DDS01 6353532 6466228 4,13,14,20\n DDS02 3319070 3361580 20\n DDS1 4939831 4949444 4,13,20\n DDS2 8724593 7821612 20\n \n DDS41 6131012 6283323 4,20\n DDS7 4229219 3559395 13,20\n DDSCAP 862095 860878 13,20\n DDSM 4593795 4923688 6,13,14,20\n DDSMSG 2481467 2834198 20\n DDSPTR 5051244 5419548 20\n DDSR 7814012 7813886 14,20\n \nInstallation Instructions: \n=========================\n4. Suppose on a form you have a form-only field that is defined as\n \n 1. AXP Sites - The routines DDS0, DDS01, DDS1, and DDSR are\nusually mapped on systems that allow mapping, so you will need to disable\nmapping for these routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. The environment\ncheck routine, DIENV, will run automatically.\n \n DIENV is sent to prevent the inadvertent queuing of the installation\n'Reachable', which means the user can navigate to the field but can't\nof this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n Print Transport Global\n Compare Transport Global to Current System\nchange its value. If the user tried to change the value, ScreenMan would \n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 5. Inhibit users from login into the system. The consequences of\ninstalling this patch while users are on the system are that users editing\ndata via ScreenMan forms will get a 'source routine edited' error, and\ntheir edits will be lost, and the data may be left in an inconsistent\nstate. Note that PAID is an application that uses ScreenMan.\n \n 6. AXP Sites - Place Taskman in a WAIT State.\n \ncorrectly display a message that editing was not allowed. But instead of \n MSM Sites - STOP Taskman.\n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*20\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nrestoring the original value in the editing window, ScreenMan would\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n \n Then enter the names of your other Compute and Print server(s).\n \n NOTE: You will then see the following message:\n \n TASKMAN is not running. You must run the routine XPDCPU in the\ndisplay the new value entered by the user. (DDS02)\nproduction UCI for each of the VOLUME SETS you have listed once the\ninstallation starts!!\n \n 9. MSM Sites - After the installation begins, you will be prompted\nto enter a DEVICE. After the device has been entered, KIDS will pause.\nAt this time, you need to go to each of the CPUs that were entered in\nstep 8, and start a job that will allow them to receive the patched\nroutines. On each one, you do the following:\n \n a) >D ^XUP This will set up the programming environment.\n \n ======\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*20\n ==========\nThe installation will then continue.\n \n 10. AXP Sites - After the patch has been installed and IF you\ndisabled your map set (step 1 above), rebuild your map set.\n \n5. Suppose you have a repeating block that displays pointer-type .01\n 11. AXP Sites - Remove Taskman from WAIT State.\n MSM Sites - Restart Taskman.\n \n 12. Enable users' login.\nfields, and connected to that .01 field you have a pop-up page that\ndisplays fields in the pointed-to entry. If one of the .01 field values\nin the repeating block is a dangling pointer, when we pressed return at\nthat record, the pop-up page would open up and display the data for the\nrecord we last selected. This patch prevents the pop-up page from opening\n1. If a form has no data dictionary fields, but DA happens to be set\nup when we press return at the dangling pointer. (DDS1)\n \n6. Before this patch, users were not able to jump to fields with\nexecutable captions. This patch allows users to jumps to fields with\nexecutable captions that are on the current page. (DDS2, DDSR)\n \n7. Print message 'Please wait. Loading all pages ...' in the command\narea right after the user issues a 'Save' command. If there are a lot\npages on the form, the loading process could take a while before the\n'Verifying ...' message appears. (DDS41)\nbefore the ^DDS call, the caller could get the message 'Entry does not\n \n8. If we deleted an entry pointed to by a .01 field, we ended up with a\ndangling pointer. This patch makes ScreenMan display the internal form of\nthe dangling .01 field pointer, so that the user can subsequently delete\nthat .01, if it's on the form. (DDS7)\n \n9. In the Form Editor, if you're editing the properties of a field on the\nform, at the Caption prompt, you should be able to enter the following\nshortcuts: \n \nexist', and the form would fail to run. (DDS0)\n Shortcut To define the caption as \n -------- ------------------------\n !L The Label of the field \n !T The Title of the field \n !U The Unique name of the field \n \nPrior to this patch, these shortcuts weren't working. (DDSCAP)\n \n10. If a repeating block is used to display records in a multiple, and an\nIndex is specified for the repeating block, FileMan loads only those\n \nentries that are in the index. Prior to this patch, a hard error would\nresult if the user selected an entry that was in the multiple but wasn't\nin the index, because ScreenMan hadn't loaded the data for that entry.\nThis patch allows the user to select only those entries that have already \nbeen loaded by ScreenMan. (DDSM)\n \n11. Suppose you have a field with executable that calls EN^DDIOL. It\npasses a global to EN^DDIOL with formatting nodes so that the text appears\nin two columns. For example:\n \n2. If in the Form Editor, you add a data dictionary field to the\n ^TMP($J,1)=string 1 \n ^TMP($J,2)=string 1a \n ^TMP($J,2,"F")="?40" \n ^TMP($J,3)=string 2 \n ^TMP($J,4)=string 2a \n ^TMP($J,4,"F")="?40" \n \n etc. \n \n D EN^DDIOL("","^TMP($J)") \nform, but at the Field property, you enter a field number that doesn't\n \nWhen you enter a ? at the field, ScreenMan displays in the help area the \nfirst 14 lines correctly, but the fifteenth line is incorrect. The third \nscreen looks like this: \n \n -------------------------------------------------------------------------\n string 11 string 11a \n string 12 string 12a \n string 13 string 13a \n string 14 string 14a \nexist, the Form Editor went on to use the "GL" nodes in the DD as if they\n string 15 \n Enter RETURN to continue or '^' to exit: \n -------------------------------------------------------------------------\n \nand the fourth screen looks like this: \n \n -------------------------------------------------------------------------\n string 15a \n string 16 string 16a \n string 17 string 17a \n\n\nThis patch fixes a bug in ^DIWP that started after patch DI*21*33: \n \n MSM Sites - Restart Taskman. \n \n 12. Enable users' login. \nThe related NOIS Calls are: WPB-1296-31219 and NOP-1296-11296.\n \nThis patch reverses the fix sent by patch 33.\n \n Routine Summary: \n ================\n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n \n <tab>;;21.0;VA FileMan;**\n \n Routine Summary: \n ================\n The following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;21.0;VA FileMan;**[patch list]**;Dec 28, 1994 \n \n CHECK^XTSUMBLD results: \nApplications doing the following are affected by this bug::\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIWP 5150036 5103576 33,36\n \n Installation Instructions: \n ==========================\n \n 1. The routines DIW* are usually mapped on systems that allow\nmapping. Alpha sites that use routine mapping will need to disable\n \nmapping for these routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. The environment check\nroutine DIENV will run automatically.\n \n The Environment Check routine, DIENV, is sent in order to prevent the\ninadvertent queueing of the installation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\n 1. Application calls ^DIWP with DIWL=0.\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users from login into the system. If users stay on the\n \nsystem while installing this patch, a hard error may occur while word\nprocessing fields are printed or edited.\n \n 6. AXP Sites - Place Taskman in a WAIT State. \n MSM Sites - STOP Taskman. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*21.0*36\n 2. After the call to ^DIWP, application resets DIWL=0 and then\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'.\n Then enter the names of your other Compute and Print server(s). \n NOTE: You will then see the following message: \n TASKMAN is not running. You must run the routine XPDCPU in the \naccesses the ^UTILITY global. No text is found when referencing\nproduction UCI for each of the VOLUME SETS you have listed once the \ninstallation starts!! \n \n 9. MSM Sites - After the installation begins, you will be prompted to\nenter a DEVICE. After the device has been entered, KIDS will pause. At\nthis time, you need to go to each of the CPUs that were entered in step 8,\nand start a job that will allow them to receive the patched routines. On\neach one, you do the following:\n a) >D ^XUP This will set up the programming environment. \n ======\n^UTILITY($J,"W",DIWL.\n b) >D ^XPDCPU This starts the job that receives the patched routines.\n =========\n c) Select INSTALL NAME: DI*21.0*36\n ==========\nThe installation will then continue. \n \n 10. AXP Sites - After the patch has been installed, rebuild your map\nset. \n \n 11. AXP Sites - Remove Taskman from WAIT State. \n\n
\nAfter V22 of VA FileMan was released to National VistA Support (NVS) for\n \n set logic are executed, the X1(order#) array contains the old field\n values, and the X2(order#) array contains the new field values. If a\n record is being added, and there is an X1(order#) array element that\n corresponds to the .01 field, it is set to null. When a record is\n deleted, all X2(order#) array elements are null.\n \nSince the KIDS build for this patch brings in these fields automatically,\nthere is no need to rerun DINIT after installing this patch.\n \n \nRoutine: DICOMPV \nNOIS \n====\n HAM-0499-21392\n PHO-1198-62053\n FNC-0599-30750\n \nThanks to Test Sites \n====================\n Hampton, VA\n White City, OR\nBug: It was discovered that when using a Backward Extended Pointer and the\n Fayetteville, NC\n White River Junction, VT\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of \nthese routines now look like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nfile that was being jumped to had a DINUMed .01 field back to the\nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIC1 7920273 8396997 1\n DIC11 3133605 3318576 1\n DIC3 8044472 8138582 1\n DICA 8337676 8300985 1\n DICA1 7134262 7156598 1\n DICATTD 9780938 9786273 1\noriginating file, a jump was not being allowed. \n DICOMPV 8888896 8426523 1\n DIE 10522278 10606815 1\n DIE1 10102666 10290843 1\n DIEF 11594187 11950704 1\n DIEFW 3026875 3026694 1\n DIEZ 9351704 9378294 1\n DIFROMSX 3683091 3497120 1\n DIFROMSY 3656754 3974102 1\n DIK1 6155873 6302851 1\n DIKC 11169535 11836728 1\n \n DIKZ1 9229373 9451304 1\n DINIT2A1 13956613 14321834 1\n DINIT2A2 12584241 14203695 1\n DINIT2A3 14285423 13176711 1\n DINIT2A4 2212843 9326344 1\n DIR1 11551993 11554966 1\n \n \nInstallation Instructions: \n==========================\nRoutine: DIC3\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to\nbe STOPPED. Failure to do so may result in a 'source routine edited'\nerror, the edits will be lost and records may be left in an\ninconsistent state. \n** \n \n 1. AXP sites: Review your mapped routine set. If any of the \nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they \nshould be removed from the mapped set at this time. \n \nBug: Input variable DIC("S") to the ^DIC routine altered local variable Y.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nThis option will load the KIDS package onto your system. \n \nThe environment check routine DIENVWRN will run automatically. Routine\nDIENVWRN is sent in order to prevent the inadvertent queuing during the\ninstallation of this patch. \n \n 3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \nFileMan was not protecting Y and expected it to contain the record number\n 4. On the KIDS menu, under the 'Installation' menu, use the \nfollowing options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of \nhaving users on the system while installing this patch are that users \nediting records will get a 'source routine edited' error, the edits \njust looked-up, so the wrong value was displayed for the .01 field when\nwill be lost and records may be left in an inconsistent state. Note \nthat most of these routines are heavily used in DHCP applications. \n \n 6. AXP Sites - Place TaskMan in a WAIT State. \n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*1 \nfield distribution several bugs were discovered at the test sites that\nentries were presented to the end-user.\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \nOptions, and Protocols? \n \n \n 8. AXP Sites - After the patch has been installed, rebuild your \nmap set, if necessary. \n \n 9. AXP Sites - Remove TaskMan from WAIT State. \n \n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login.\nRoutines: DIC1, DIC11\nBug: When the internal value of a date, pointer or variable pointer is\npassed as a default lookup value in input variable DIC("B") to the ^DIC\nroutine, it should be displayed to the end-user in external format. This\nworked in V21 but didn't in V22.\n \nRoutine: DIE\nBug: After a call to ^DIE with DR="[template name]", a ^TMP("DIE",number)\ncould affect various packages. The following is list of the routine(s)\nnode was not being killed.\n \nRoutine: DIEZ\nBug: An undefined X variable error could occur during a KIDS installation,\nwhen KIDS called FileMan to uncompile an input template.\n \nRoutines: DICA, DICA1\nBug: If an UPDATE^DIE call is made from within another UPDATE^DIE call\n(for example, when the Updater executes a cross-reference that makes\nanother Updater call), the call could fail and Dialog file error messages\nand the problem that was corrected: \ngenerated. Also the variable D was leaking out of UPDATE^DIE.\n \nRoutine: DIEFW\nBug: An undefined DIEFLOCK could occur if the Filer was called with the\n"K" flag to do locking, and within that Filer call, a call was made to\nWP^DIE (from within a cross-reference, for example) without the "K" flag.\n \nRoutines: DIFROMSX, DIFROMXY\nChange: Before, if a partial DD was sent with KIDS and the file had KEYs,\nall of the field definitions for the KEY fields had to be sent. We\n \ndecided that wasn't necessary, so after this patch, the field definition\nfor a key field must be sent only if the key is compound and other\nfield(s) in the key are being sent.\n \nRoutines: DIK1, DIKZ1\nBug: The ^DIK entry points did not have time-outs on the Lock commands\nthey issued.\n \nRoutine: DIR1\nBug: MAS patch DG*5.3*149 brought new code into routine DGREG. The old\nRoutine: DICATTD\ncode directly executed the input transform from subfile 2.101, field .01\nto check the validity of a value entered by the user (in X). The new code\ninstead calls CHK^DIE (which also executes the input transform) to check\nthe validity of the value. The input transform code for this field sets\nthe variable DINUM. The MAS code at REG+2^DGREG then uses DINUM. In\nversion 22, FileMan NEWs DINUM in the CHK^DIE call before executing the\ninput transform, because DINUM is not a documented output variable, and\nbecause it is a dangerous variable to leave around. MAS does not have\ntime to patch their code before the planned release of version 22, so\nFileMan will temporarily 'leak' DINUM in order to avoid a hard error.\nBug: When using the option Modify File Attributes AND used the\nAfter MAS patches their code, FileMan will issue another patch to restore\nthe NEW DINUM.\n \nRoutines: DIE1, DIEF, DIKC\nBug: If there is an X1 array element corresponding to the .01 field in the\nnew-style Index logic or condition, make sure it is set to null if the\nrecord is being added.\n \nRoutines: DINIT2A1, DINIT2A2, DINIT2A3, DINIT2A4\nBug: These DINIT routines fix a typo on the description of the following\nScreen-Mode version AND were adding a Free Text multiple, the 2nd piece of\nfield in the Cross-Reference Values multiple of the Index file (#.11):\n \n 11.1 Cross-Reference Values (Multiple-.114)\n 4.5 Computed Code\n \n was: "Answer with M code that set X..."\n should be: "Answer with M code that sets X..."\n \nThe DINIT routines also add information about the X1 and X2 arrays to the\ndescriptions of the following fields in the Index file (#.11):\nthe 0 node of the DD would be corrupted.\n \n 1.1 Set Logic\n 1.4 Set Condition Code\n 2.1 Kill Logic\n 2.4 Kill Condition Code\n \n For each of the above fields, the following paragraph was appended to the\n description:\n \n When fields that make up a cross-reference are edited and the kill and\n\n\nY2K Waiver ID#: Y2KW0001 Y2K Waiver Status: Approved\n========\n CLA-0197-20856\n PHI-0694-20785\n MEM-0997-70237\n \nThanks to Test Sites \n====================\n White River Junction, VT \n Hampton, VA \n \nRoutine Summary: \n1. If a user specified a print field whose data type definition is a\n================\n The following routines are included in this patch. The second line of \nthese routines now look like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\nDate/Time and they used a date Function along with the Count(!) operator,\n DIG 6293627 9213962 2\n DIH 4688941 4441871 2\n DIL1 6856617 4879469 2\n DIO 7212010 7253177 2\n DIO0 9418636 9464280 2\n DIO1 6789778 6980951 2\n DIO3 4969134 4961669 2\n DIO4 6003254 5849805 2\n DIOS1 1190642 1071375 2\n DIP 12986358 13075099 2\nthe FileMan internal representation would be printed. For example,\n DIP0 10722447 10870128 2\n DIP1 9773580 10046865 2\n DIP10 5293036 5158897 2\n DIP22 6717942 6867188 2\n DIP31 1504438 1478503 2\n DIXC 4724715 5003894 2\n \n \nInstallation Instructions: \n==========================\n!MONTH(DATE FIELD)\nThis patch can be installed with VISTA users online. However, it is \nrecommended that it be Queued for a time of generally least activity. \n \n 1. AXP sites: Review your mapped routine set. If any of the \nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they \nshould be removed from the mapped set at this time. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nThis option will load the KIDS package onto your system. \n \n (NOIS: SAJ-1198-72266)\n 3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the \nfollowing options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n \n 5. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*2\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \nOptions, and Protocols? \n \n 6. AXP Sites - After the patch has been installed, rebuild your \n2. Previous to this patch FileMan Sorts were limited to 7 levels.\nmap set, if necessary. \nWith this patch the maximum number of Sort levels has been increased to\n15. \n \n (NOIS: WBP-0795-21830; DAY-0297-41337)\n \n3. When computing global length and comparing it to what was set in the\nMUMPS OPERATING SYSTEM file, Global Subscript truncation would begin\nbefore it was necessary.\n (NOIS: IOW-0998-40306)\n \n4. When a Sort contain a Boolean expression, for example, MY FIELD["A",\nthe Boolean operator was getting concatenated with the field name such\nthat a user could not edit the Sort template.\n>> This patch may be installed during the Y2K Moratorium,\n (NOIS: ISA-0395-10001)\n \n5. Improvement to Descriptive Statistics and correction to Histogram\nreport header.\n \n6. If a user used the dot syntax for a date and the field is a DATE type\nand the TIME can be entered, an "????Invalid Entry" error message would be\ndisplayed or the data would not be displayed even though there was data\nthat should have been displayed. For example:\n \neither BEFORE 12/15/99 or AFTER 1/15/2000.\n GO TO FOIA REQUESTED DATE: LAST// 1.MAR.97\n \n (NOIS: CLA-0197-20856, VAC-1197-21817)\n \n7. If a user was using the "!" in a print field and printed the same\nfield again, an erroneous Count was reported which was twice the number of\ncounted items.\n \n Example #1: In this example the output is correct as documentated the\n v22 Getting Started Manual, Section: Printing Statistics Only.\n \n \n Select OPTION: PRINT FILE ENTRIES\n \n OUTPUT FROM WHAT FILE: NUMBER AND KIDS// \n SORT BY: NAME// \n START WITH NAME: FIRST// \n FIRST PRINT FIELD: !NAME \n THEN PRINT FIELD: \n Heading (S/C): NUMBER AND KIDS STATISTICS Replace \n DEVICE: Telnet terminal\n>> This patch MAY NOT be installed between 12/15/1999 and\n NUMBER AND KIDS STATISTICS JUL 23,1999 13:34 PAGE 1\n NAME\n -------------------------------------------------------------------------\n \n COUNT 3\n \n Example #2: This is an example of the fixed output. Please note the\n PRINT FIELD entry order does not matter.\n \n OUTPUT FROM WHAT FILE: MUMPS OPERATING SYSTEM// \n1/15/2000 (the Y2K Lockdown Period).\n SORT BY: NAME// \n START WITH NAME: FIRST// \n FIRST PRINT FIELD: !NAME \n THEN PRINT FIELD: NAME \n THEN PRINT FIELD: \n Heading (S/C): MUMPS OPERATING SYSTEM STATISTICS Replace \n DEVICE: SYSTEM\n MUMPS OPERATING SYSTEM STATISTICS SEP 14,1999 07:06 PAGE 1\n NAME NAME\n -------------------------------------------------------------------------\n \n \n CACHE/OpenM CACHE/OpenM\n DSM for OpenVMS DSM for OpenVMS\n DTM-PC DTM-PC\n GT.M(VAX) GT.M(VAX)\n MSM MSM\n OTHER OTHER\n ------------------------------\n COUNT 6\n \nBug Fix: \n (NOIS: PHI-0694-20785, MEM-0997-70237)\n \nNOISes \n======\n SAJ-1198-72266\n WBP-0795-21830\n IOW-0998-40306\n ISA-0395-10001\n DAY-0297-41377\n VAC-1197-21817\n\n
\nSee patch DI*22*111 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*71 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*116 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*76 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*112 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*117 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*106 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*70 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*95 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*120 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nMiscellaneous bug fixes in the FileMan lookup ^DIC routines\nby Gary Beuschel on a local message at the San Francisco ISC.\nroutines are heavily used in DHCP applications.\n \n 6. AXP Sites - Place TaskMan in a WAIT State. \n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*17\n \n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \nand Protocols? \n \n \n 8. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n 9. AXP Sites - Remove TaskMan from WAIT State. \nRoutines: DIC, DIC1\n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login. \n===================\nMake the "Y" flag in DIC(0) work the same as it did in version 21. This\nundocumented flag is supposed to make ^DIC return a list of entry numbers\nthat match the lookup value in Y(n) where 'n' is an IEN. The FIND^DIC call\nis now a better way to do the same thing. Reported by Lucille Barrios on a\nFORUM mail message.\n \n \nRoutines: DICLIX1, DICU11\n=========================\nI found during my testing that in cases where the Lister decides to build\na temporary index on a pointer or variable pointer because it's the\nfastest way to return the list in order, I needed to save the internal\npointer or variable pointer on the temporary list, in case the user asked\nto have it returned in the output.\n \nRoutine: DICA\n=============\nRoutines: DIC1, DIC2, DIC3\nWith the "E" flag, UPDATE^DIE assumes that the values passed in the FDA\nare in external form. Also, for LAYGO/Finding (?+) nodes, the value of the\n.01 field is used as a lookup value to see if an existing record should be\nedited, or a new record added. Prior to this change, the Updater used the\ninternal form of the .01 as a lookup value, rather than the external form.\nIf the .01 is a pointer or variable, this meant the lookup would fail. For\nDINUM'd pointers, this resulted in the Dialog error message #302, "Entry\n'xxx' already exists" to be returned.\n \n \n==========================\nNOIS \n====\nDAY-1099-42880\n \nThanks to Test Sites \n====================\n \nRoutine Summary: \n================\nThe following routines are included in this patch. The second line of\nSupport the undocumented "U" flag so that MailMan can get the same display\nthese routines now looks like:\n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIC 9848200 9925689 4,17\n DIC1 8559944 8596617 1,4,17\non one of their lookups as they did in V21. This supports a lookup on the\n DIC2 4974600 5005952 4,17\n DIC3 7291022 7365376 1,16,4,17\n DICA 8533062 8533782 1,4,17\n DICLIX1 2988293 3152916 17\n DICU11 3617845 3663044 17\n \n \nInstallation Instructions: \n==========================\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to be\nindex with no transforms. I.e., the code expects the lookup value to be an\nSTOPPED. Failure to do so may result in a 'source routine edited' error,\nthe edits will be lost and records may be left in an inconsistent state.\n** \n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nbe removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\ninternal format (of a pointer, date, etc.), and will look on the index for\n \n The environment check routine DIENVWRN will run automatically.\nRoutine DIENVWRN is sent in order to prevent the inadvertent queuing\nduring the installation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\na match, and will not try to convert the lookup value in any way. Reported\n \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of having\nusers on the system while installing this patch are that users editing\nrecords will get a 'source routine edited' error, the edits will be lost\nand records may be left in an inconsistent state. Note that most of these\n\n
\nSee patch DI*22*105 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*114 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*119 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*122 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*110 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*118 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*128 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*131 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*123 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*129 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nY2K Waiver Exemption ID#: Y2KWE0031\nvalid list of index names.\n \nThe problem can manifest itself as bad variable name errors at S+2^DIQ:1\nor null subscript errors at N5+16^DICN0 when the DEBTOR field (#9) of the\nACCOUNTS RECEIVABLE file (#430) is edited.\n \nNOIS\n====\nALX-1299-70504\nBAC-1299-40203\n This patch may be installed at any time during the Y2K Moratorium\nDUR-1299-30293\nNCH-1199-42549\nNCH-1299-40048\nOKL-1199-72669\nREN-1199-62529\n \nRoutine Summary:\n===============\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n (including the 12/15/1999 thru 1/15/2000 Y2K lockdown).\n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999\n \nCHECK^XTSUMBLD results:\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIED 10169985 10197675 4,21\n \n \n \nInstallation Instructions:\n==========================\n ***********************************************************************\n * It is HIGHLY recommended that ALL Users and VISTA Background jobs *\n * be STOPPED. Failure to do so may result in a 'source routine *\n * edited' error. Edits will be lost and records may be left in an *\n * inconsistent state. *\n ***********************************************************************\n \n 1. AXP sites: Review your mapped routine set. If any of the\nThis patch fixes a problem that occurs when you edit a pointer field that\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nbe removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n The Environment Check Routine DIENVWRN will run automatically.\nRoutine DIENVWRN is sent in order to prevent inadvertent queuing during\nthe installation of this patch.\n \nhas a screen and allows LAYGO into the pointed-to file. If the variable D\n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options: \n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\nhappens to be set when the input transform of the pointer field is\n \n 5. Inhibit users from login into the system. DIED and is used\nheavily in VISTA applications. A consequence of installing this patch\nwhile users are on the system is that users editing records may get a\n'source routine edited' error, edits will be lost, and records may be left\nin an inconsistent state.\n \n 6. AXP Sites - Place TaskMan in a WAIT State.\n OpenM/Cache Sites - STOP TaskMan. \n \nexecuted and isn't changed by the input transform, ^DIE is passing it to\n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*22.0*21\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\nand Protocols?\n \nMIX^DIC1 to do the lookup on the pointed-to file, even though D isn't a\n 8. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n 9. AXP Sites - Remove TaskMan from WAIT State.\n OpenM/Cache Sites - Restart TaskMan.\n \n 10. Enable users' login.\n\n
\nSee patch DI*22*136 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*138 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*133 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*135 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*140 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*130 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*143 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPlease see complete description in the Forum patch description.\n\n
\nSee patch DI*22*146 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*148 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis patch fixes the following problem: If a new-style cross-reference is\nfollows:\n \n Select MFIELD: ENTRY 1// <RET>\n MFIELD1: TEST 1// <RET>\n Select MFIELD: <RET>\n FIELD1: first// second\n \nWhen the new-style cross reference on FIELD1 is executed, X1 and X1(1)\ncontain 'second' instead of 'first'.\n \ndefined on a field, ^DIE or FileMan's 'ENTER OR EDIT FILE ENTRIES' is\nY2K Waiver ID#: Y2KW0001\nY2K Waiver Status: Approved\n===========================\n * This patch may be installed during the Y2K Moratorium, either\n BEFORE 12/15/99 or AFTER 1/15/2000.\n * This patch MAY NOT be installed between 12/15/1999 and 1/15/2000\n (the Y2K Lockdown Period).\n \nNOIS\n====\nused to edit a multiple field and the field with the new-style\nISA-1199-12633\n \nRoutine Summary:\n===============\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999\n \nCHECK^XTSUMBLD results:\ncross-reference, then the X1 array (which contains the old values of the\n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIKC 11836728 11879894 1,22\n \n \nInstallation Instructions:\n==========================\n ***********************************************************************\n * It is HIGHLY recommended that ALL Users and VISTA Background jobs *\nfields in the cross-references) may be set incorrectly after the user\n * be STOPPED. Failure to do so may result in a 'source routine *\n * edited' error. Edits will be lost and records may be left in an *\n * inconsistent state. *\n ***********************************************************************\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they should\nbe removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\ndescends into and back out of the multiple.\noption will load the KIDS package onto your system.\n \n The Environment Check Routine DIENVWRN will run automatically.\nRoutine DIENVWRN is sent in order to prevent inadvertent queuing during\nthe installation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\n \nfollowing options: \n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 5. Inhibit users from login into the system.\n \n 6. AXP Sites - Place TaskMan in a WAIT State.\nFor example, suppose MFIELD is a multiple field, a new-style\n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*22.0*22\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\ncross-reference contains field MFIELD1, and you edit the fields as\nand Protocols?\n \n 8. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n 9. AXP Sites - Remove TaskMan from WAIT State.\n OpenM/Cache Sites - Restart TaskMan.\n \n 10. Enable users' login.\n\n
\nSee patch DI*22*147 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*150 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*144 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*153 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*149 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*156 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*151 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*152 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*159 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*157 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nBug Fixes\n Nois: SPO-1299-50519; BRX-1299-10679; SUX-1299-40851; DUB-1299-31316\n Routine: DIO0\n \n2. During SQA it was also found that If you answer:\n HEADING: TEST LIST // [<sp>\n where you are telling FileMan to use the space-bar retrieval of the\nTemplate previously named, FileMan would use the "[" as the header.\n Routine: DIP3\n \n \n=========\nNOISes \n======\n SPO-1299-50519\n BRX-1299-10679\n SUX-1299-40851\n DUB-1299-31316\n \nThanks to Test Sites \n====================\n Spokane, WA\n \n Bronx, NY\n Sioux Falls, SD\n Dublin, GA\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of \nthese routines now look like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n1. An error of <SUBSCRIPT>HDR^DIO4:3 would occurr if the following\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIO0 9464280 9610303 2,23\n DIP3 10828796 10830710 23\n \nInstallation Instructions: \n==========================\nconditions were true:\nThis patch can be installed with VISTA users online. However, it is \nrecommended that it be Queued for a time of generally least activity. \n \n 1. AXP sites: Review your mapped routine set. If any of the \nroutine(s) listed in the ROUTINE SUMMARY section are mapped, they \nshould be removed from the mapped set at this time. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nThis option will load the KIDS package onto your system. \n \n A. After Sorting there were No Records To Be Printed.\n 3. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the \nfollowing options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n and\n 5. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*23\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu \nOptions, and Protocols? \n \n 6. AXP Sites - After the patch has been installed, rebuild your \n B. If the Header was a Print Template that contained Fields that were to\nmap set, if necessary. \nbe printed.\n\n
\nSee patch DI*22*160 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*161 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*162 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*163 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*161 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*165 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*168 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee the Patch Module on FORUM for complete information.\n\n
\nSee the Patch Module on FORUM for complete information.\n\n
\nSee the Patch Module on FORUM for complete information.\n\n
\nSee patch DI*22*27 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*24 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*25 in the National Patch Module for complete information\non this patch.\n\n
\nFixes several bugs in the FileMan lookup ^DIC routines and the finder\n \nno need to re-run DINIT to get the new field installed.\n \nRoutines: DINIT0FA, DINIT0FB\n============================\nWhen a new-style cross-reference is edited, provide a default for\nSubscript Number only for Regular-type indexes, not MUMPS-type indexes.\nAlso, set the Subscript Length to 30 for Free Text and MUMPS fields only\nif the the field is used as a subscript. Note that these changes to the\nScreenMan form for editing new-style cross-references is transported as\npart of the KIDS build for this patch, so there is no need to re-run DINIT\nRoutines: DIC1, DIC2, DIC5 \nto get these changes.\n \nRoutine: DIKCP1\n===============\nInclude the new field TRANSFORM FOR LOOKUP (#5.3) in Data Dictionary\nListings.\n \n \nNOIS \n====\n==========================\nBIL-1299-32021\nISD-1199-72724\nISL-1299-51117\nSLC-1299-51331 \n \n \nThanks to Test Sites \n====================\n \nRoutine Summary: \nWhen the "T" flag in DIC(0) is used, FileMan displays the field on which a \n================\nThe following routines are included in this patch. The second line of these\nroutines now looks like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\nmatch is made, as it presents the entries. This was happening even when DIC(0)\n DIC 9925689 9515778 4,17,20\n DIC0 4839635 5249546 4,20\n DIC1 8596617 8701710 1,4,17,20 \n DIC2 5005952 5078251 4,17,20\n DIC3 7365376 7735073 1,16,4,17,20\n DIC4 5435232 5480003 4,20\n DIC5 1959090 1889906 4,20\n DICF 8504495 8884337 20\n DICF2 8940451 9016160 4,20\n DICL2 4796448 4973816 20\ndid not contain "E". This patch prevents the display unless DIC(0) contains\n DICM 8330209 8458025 4,20\n DICM0 9037748 9043441 16,4,20\n DICM1 6170473 6277445 20\n DICM3 4576635 4769867 16,4,20\n DICUIX 7050873 7091249 20\n DIKCFORM 10827227 10615684 20\n DIKCP1 7463319 7673038 20\n DINIT0F1 5527731 5526766 20\n DINIT0FA 7807085 9430600 20\n DINIT0FB 9020615 10086109 20\n"E". (Found by Gary Beuschel, MailMan developer).\n DINIT2A3 13176711 14045038 1,20\n DINIT2A4 9326344 10531062 1,20\n \n \nInstallation Instructions: \n==========================\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to be \nSTOPPED. Failure to do so may result in a 'source routine edited' error, the\nedits will be lost and records may be left in an inconsistent state. \n** \n \n \n 1. AXP sites: Review your mapped routine set. If any of the routine(s)\nlisted in the ROUTINE SUMMARY section are mapped, they should be removed from\nthe mapped set at this time. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system. \n \n The environment check routine DIENVWRN will run automatically. \nRoutine DIENVWRN is sent in order to prevent the inadvertent queuing during the\nRoutines: DIC3, DICF, DICF2, DICL2\ninstallation of this patch. \n \n 3. The patch has now been loaded into a transport global on your system. \nYou now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n \n Print Transport Global \n Compare Transport Global to Current System \n===========================\n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of having users\non the system while installing this patch are that users editing records will\nget a 'source routine edited' error, the edits will be lost and records may be\nleft in an inconsistent state. Note that most of these routines are heavily\nused in DHCP applications. \n \n 6. AXP Sites - Place TaskMan in a WAIT State. \nFIND^DIC.\nA .01 field that was 240 characters long caused a SUBSCRIPT error to occur\n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*20\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, and\nin the Finder FIND^DIC calls. I also found a similar problem in ^DIC if\nProtocols? \n \n \n 8. AXP Sites - After the patch has been installed, rebuild your map set,\nif necessary. \n \n 9. AXP Sites - Remove TaskMan from WAIT State. \n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login. \nthe lookup value was very long. This patch corrects both problems.\n(Reported by Hellevi, Ruonamaa of Finland.)\n \nRoutines: DICM3\n===============\nWhen doing a lookup on an indexed variable pointer field where the pointer\nhad a screen, the screen logic wasn't being honored during lookup on the\npointed-to file. Found by Frank Stalling and Paul Sharp. NOIS:\n \nISD-1199-72724, SLC-1299-51331.\n \nRoutines: DICM0\n===============\nIf a New Style index on the .01 field has a TRANSFORM FOR STORAGE on it,\nthen don't allow LAYGO to the file while the value is in it's format after\ngoing through the transform, as it may not be proper internal storage\nformat. An example is a date transformed to backwards collating sequence,\n9999999-2991214. Found by developer.\n \nY2K Waiver ID#: Y2KW0001 Y2K Waiver Status: Approved\nRoutines: DIC, DIC0\n===================\nThe new feature that makes ^DIC set DIC("P") so that it doesn't have to be\nset as an input variable by the developer when allowing LAYGO to\nmultiples, wasn't working correctly. Found by Jerald F Rutherford. NOIS:\nISL-1299-51117.\n \nRoutines: DIC1, DIC2, DICM, DICM1\n=================================\nIn the process of testing the Name Standardization project for the New\n => This patch MAY NOT be installed between 12/15/1999 and 1/15/2000\nPerson file, it was discovered that when there was a transform on the "B"\nindex, the index value wasn't being displayed correctly during lookup.\n \nRoutines: DIC4\n==============\nWhen the new "T" flag was used in DIC(0), developer discovered that a hard\nerror could occur if one of the indexes was a new style index with\nTRANSFORM FOR STORAGE code. The error happened during the code that\nexecutes the transform against the lookup value, then does a second lookup\non the index looking for a match to the transformed lookup value.\n (the Y2K Lockdown Period).\n \nRoutines: DIC3\n==============\nEntries were not being found doing lookup when DIC(0) contained the\nundocumented flag "U", as it is when doing a relational jump using a\nbackwards pointer. NOIS: BIL-1299-32021\n \nRoutine: DICUIX\n===============\nLook for the new field 'TRANSFORM FOR LOOKUP' in the INDEX file.\n => This patch may be installed during the Y2K Moratorium\nPreviously during lookup, if FileMan failed to find a match to the lookup\nvalue, and if a lookup index had TRANSFORM FOR STORAGE code, FileMan\nexecuted that against the lookup value and tried to find a match with the\nnew transformed value. Now it uses the TRANSFORM FOR LOOKUP code instead.\nThe TRANSFORM FOR STORAGE code is used only to transform an entries field\nvalue before storing it in the index for that entry.\n \nRoutines: DIC3, DIC5, DICM\n===========================\nBecause of the place where the DICR array was being NEWed when DIC(0)\n - AFTER 1/15/2000.\ncontained the new "T" flag, I was losing a flag that told me I asked the\nuser whether they wanted to add a new entry while I had an internal,\ntransformed lookup value to stuff in the .01 field. This was causing me to\nask again whether they wanted to add a new entry, after all the transforms\nwere done. Found by developer.\n \nRoutine: DIKCFORM\n=================\nWhen a new-style index is created and a TRANSFORM FOR STORAGE code was\ndefined on one of the cross-reference values, the TRANSFORM FOR DISPLAY\n \nfield was made required. This change makes the TRANSFORM FOR DISPLAY\noptional, even if a TRANSFORM FOR STORAGE is defined, since the internal\nform of the index value may already be readable to the user.\n \nRoutines: DINIT2A3, DINIT2A4, DINIT0FA, DINIT0FB\n================================================\nAdd a new field to the Index file (#.11), Cross-References Values multiple\n(#.114). The field is TRANSFORM FOR LOOKUP (#5.3) and is used by FileMan's\nlookup utilities (see change to routine DICUIX above). Note that this new\nfield is transported as part of the KIDS build for this patch, so there is\n\n\nSee patch DI*22*29 in the National Patch Module for complete information\non this patch.\n\n
\nRoutine: DIC11\ndevelopers had used DIC("V") to limit the lookup to only one of the\npointed-to files. This patch makes the lookup work on variable pointers\nas well as pointers.\n \nNOIS \n====\n BAY-0899-31670\n PAL-0899-62585\n \nThanks to Test Site\n--------------\n====================\n Bay Pines, FL\n Palo Alto HCS, CA\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of these \nroutines now look like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \nIn version 21 of FileMan, if lookup value is accent grave followed by a\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIC11 3318576 3304157 1,13\n \nInstallation Instructions: \n==========================\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to be \nnumber, FileMan first looks on the current file for a matching IEN. If\nSTOPPED. Failure to do so may result in a 'source routine edited' error, the \nedits will be lost and records may be left in an inconsistent state. \n** \n \n 1. AXP sites: Review your mapped routine set. If DIC11 is mapped on\nyour system, it should be removed from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption will load the KIDS package onto your system. \n \nnone is found, but we can add records to the file, and if the .01 field is\nThe environment check routine DIENVWRN will run automatically. Routine \nDIENVWRN is sent in order to prevent the inadvertent queuing during the \ninstallation of this patch. \n \n 3. The patch has now been loaded into a transport global on your system. \nYou now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the following \noptions: \n Print Transport Global \na pointer or variable pointer, FileMan looks on the pointed-to file for a\n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of having\nusers on the system while installing this patch are that users editing\nrecords will get a 'source routine edited' error, the edits will be lost\nand records may be left in an inconsistent state. Note that DIC11 is\nheavily used in DHCP applications. \n \nmatching IEN. This did not work for variable pointers in version 22\n 6. AXP Sites - Place TaskMan in a WAIT State. \n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following \noption: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*13\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \nbecause it was felt that the user had no control over which of the\nand Protocols? \n \n \n 8. AXP Sites - After the patch has been installed, rebuild your map set, \nif necessary. \n \n 9. AXP Sites - Remove TaskMan from WAIT State. \n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login. \npointed-to files might be used for the match. However, on the NOIS, the\n\n\nSee patch DI*22*8 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*9 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*26 in the National Patch Module for complete information\non this patch.\n\n
\nSee DI*22*30 of the National Patch Module for full documentation.\n\n
\nSee patch DI*22*32 in the National Patch module on FORUM for a full\ndescription.\n\n
\nSee patch DI*22*28 in the National Patch Module for complete information\non this patch.\n\n
\nPlease see the National Patch Module for details to patch DI*22*33.\n\n
\nPlease see DI*22*36 in FORUM's National Patch Module for details \n\n
\nSee patch DI*22*39 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*11 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis patch introduces two new APIs in VA FileMan, DELIX^DDMOD and\n \n \n MYOUT("DDAUD")=1\n MYOUT("DIEZ",100)=ZZTEST EDIT^16200^ZZIT\n MYOUT("DIKZ")=ZZCR\n \n The MYOUT output array indicates that the deletion was recorded in\n the DD Audit file (#.6). Field #12 is included in the compiled\n input template ZZTEST EDIT (#100), which is compiled into the ZZIT\n namespaced routines. Cross-references on file #16200 are compiled\n under the ZZCR namespace.\n \n \n 2. In this example, the whole-file regular cross-reference #7 (the "N"\n index), defined on field #15 within subfile #16200.075, is deleted.\n The "K" flag indicates that the entire ^DIZ(16200,"N") index should\n be removed, and the "W" flag indicates that messages should be\n printed to the current device.\n \n >D DELIX(16200.075,15,7,"KW")\n \n Removing index ...\nDocumentation:\n Deleting cross-reference definition ...\n \n \n Compiling ZZ TEST CR Input Template of File 16200...\n 'ZZIT1' ROUTINE FILED..\n 'ZZIT' ROUTINE FILED....\n 'ZZIT2' ROUTINE FILED.\n \n Compiling Cross-Reference(s) 16200 of File 16200.\n \n=============\n ...SORRY, HOLD ON...\n \n 'ZZCR1' ROUTINE FILED.\n 'ZZCR2' ROUTINE FILED.\n 'ZZCR3' ROUTINE FILED.\n 'ZZCR4' ROUTINE FILED.\n 'ZZCR5' ROUTINE FILED.\n 'ZZCR' ROUTINE FILED.\n \n Error Codes Returned\n \n --------------------\n 202 The specified parameter is missing or invalid.\n 301 The passed flags are incorrect.\n 401 The file does not exist.\n 406 The file has no .01 definition.\n 407 A word-processing field is not a file.\n 501 The file does not contain the specified field.\n \n \n DELIXN^DDMOD: New-Style Index Deleter\n DELIX^DDMOD: Traditional Cross-Reference Deleter\n =====================================\n This procedure deletes a New-Style Index definition from the Index file.\n Optionally, it deletes the data in the index or executes the kill logic\n for all entries in the file. Compiled input templates that contain one\n or more of the fields defined in the index are recompiled. If\n cross-references on the file are compiled, they are recompiled.\n \n Format\n ------\n DELIXN^DDMOD(FILE,INDEX,FLAGS,OUTPUT_ROOT,MSG_ROOT)\n ================================================\n \n Input Parameters\n ----------------\n FILE (Required) File or subfile number. For whole-file indexes,\n this is the number of the file at the upper level where\n the data in the index resides.\n \n INDEX (Required) Index name.\n \n FLAGS (Optional)\n This procedure deletes a Traditional Cross-Reference definition from the\n Flags to control processing. The possible values are:\n \n K For Regular indexes, delete the data in the index.\n For MUMPS indexes, execute the kill logic for all\n entries in the file.\n \n W Write messages to the current device as the index\n is deleted and cross-references and input\n templates are recompiled.\n \n data dictionary. Optionally, it deletes the data in the index or\n OUTPUT_ROOT (Optional) The name of the array that should receive\n information about input templates and cross-references\n that may have been recompiled. See Output below. This must\n be a closed root, either local or global.\n \n MSG_ROOT (Optional) The name of the array that should receive any\n error messages. This must be a closed root, either local\n or global. If not passed, errors are returned descendent\n from ^TMP("DIERR",$J).\n \n executes the kill logic for all entries in the file. Compiled input\n Output\n ------\n OUTPUT_ROOT See OUTPUT_ROOT under Input Parameters. If a field used in\n the index is used in any compiled input templates, those\n input templates are recompiled. Information about the\n recompiled input templates is stored descendant from\n OUTPUT_ROOT("DIEZ"):\n \n OUTPUT_ROOT("DIEZ",input template #) =\n input template name ^ file # ^ compiled routine name\nDELIXN^DDMOD. DELIX^DDMOD can be used to delete a Traditional\n templates that contain the field on which the cross-reference is defined\n \n If cross-references for the file are compiled, they are\n recompiled, and the compiled routine name is stored in\n OUTPUT_ROOT("DIKZ"):\n \n OUTPUT_ROOT("DIKZ") = compiled routine name\n \n Example\n -------\n 1. In this example, the new-style "G" index defined on file #16200 is\n are recompiled. If cross-references on the file are compiled, they are\n deleted. The "K" flag indicates that the entire ^DIZ(16200,"G")\n index should be removed from the file.\n \n >D DELIXN^DDMOD(16200,"G","K","MYOUT")\n \n >ZW MYOUT\n MYOUT("DIEZ",94)=ZZ TEST^16200^ZZIT\n MYOUT("DIEZ",100)=ZZ TEST A^16200^ZZITA\n MYOUT("DIKZ")=ZZCR\n \n recompiled.\n The MYOUT output array indicates that a field or fields defined in\n the deleted index are used in the compiled input templates ZZ TEST\n (#94) and ZZ TEST 2 (#100). Those two input templates were\n recompiled. Cross-references on file #16200 were also recompiled\n under the ZZCR namespace.\n \n 2. In this example, the whole-file regular index (the "J" index) is\n deleted. The fields in the index come from fields in a multiple,\n subfile #16200.075, but the whole-file index resides at the\n top-level file #16200. The "K" flag indicates that the entire\n \n ^DIZ(16200,"J") index should be removed, and the "W" flag indicates\n that messages should be printed to the current device.\n \n >D DELIXN^DDMOD(16200,"J","KW","MYOUT")\n \n Removing index ...\n Deleting index definition ...\n \n \n Compiling ZZ TEST Input Template of File 16200....\n Format\n 'ZZIT' ROUTINE FILED....\n 'ZZIT1' ROUTINE FILED.\n \n \n Compiling ZZ TEST A Input Template of File 16200....\n 'ZZITA' ROUTINE FILED....\n 'ZZITA' ROUTINE FILED.\n \n Compiling Cross-Reference(s) 16200 of File 16200.\n \n ------\n ...SORRY, JUST A MOMENT PLEASE...\n \n 'ZZCR1' ROUTINE FILED.\n 'ZZCR2' ROUTINE FILED.\n 'ZZCR3' ROUTINE FILED.\n 'ZZCR4' ROUTINE FILED.\n 'ZZCR5' ROUTINE FILED.\n 'ZZCR6' ROUTINE FILED.\n 'ZZCR7' ROUTINE FILED.\n 'ZZCR8' ROUTINE FILED.\n DELIX^DDMOD(FILE,FIELD,CROSS_REF,FLAGS,OUTPUT_ROOT,MSG_ROOT)\n 'ZZCR9' ROUTINE FILED.\n 'ZZCR10' ROUTINE FILED.\n 'ZZCR' ROUTINE FILED.\n \n Error Codes Returned\n --------------------\n 202 The specified parameter is missing or invalid.\n 301 The passed flags are incorrect.\n \n \n \nNOISes\n======\nISW-0799-22411\nBRX-0297-10955\n \nThanks to Test Sites\n====================\nBRONX, NY\n \nRoutine Summary:\n Input Parameters\n================\nThe following routines are included in this patch. The second line\nof these routines now looks like:\n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n ----------------\n DDMOD N/A 147228 12\n DIKCU1 3879444 3896028 12\n DIKD N/A 3683869 12\n DIKD1 N/A 2907868 12\n DIKD2 N/A 2009556 12\n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is\nrecommended that it be Queued for a time of generally least activity.\nCross-Reference definition from the data dictionary. DELIXN^DDMOD can be\n FILE (Required) File or subfile number.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 3. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*22.0*12\n FIELD (Required) Field number.\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 5. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n CROSS_REF (Required) Cross-reference number. Traditional\n cross-references are defined in the data dictionary\n under ^DD(file#,field#,1,cross reference number).\n \n FLAGS (Optional) Flags to control processing. The possible\n values are:\nused to delete a New-Style Index definition from the Index file (#.11).\n \n K For Regular, KWIC, Mnemonic, and Soundex-type\n cross-references, delete the data in the index.\n For MUMPS and Trigger-type cross-references,\n execute the kill logic of the cross-reference for\n all entries in the file. For Bulletin-type\n cross-references, the "K" flag is ignored; the\n kill logic for Bulletin-type cross-references is\n never executed by this procedure.\n \nOptionally, depending on the type of cross-reference deleted, the APIs\n W Write messages to the current device as the index\n is deleted and cross-references and input\n templates are recompiled.\n \n OUTPUT_ROOT (Optional) The name of the array that should receive\n information about input templates and cross-references\n that may have been recompiled and a flag to indicate that\n the deletion was audited in the DD Audit file (#.6). See\n Output below. This must be a closed root, either local or\n global.\nwill also delete the data in the index or execute the kill logic for all\n \n MSG_ROOT (Optional) The name of the array that should receive any\n error messages. This must be a closed root, either local\n or global. If not passed, errors are returned descendent\n from ^TMP("DIERR",$J).\n \n Output\n ------\n OUTPUT_ROOT See OUTPUT_ROOT under Input Parameters.\n \nentries in the file. Compiled input templates that contain the field on\n If the field on which the deleted cross-reference was\n defined is used in any compiled input templates, those\n input templates are recompiled. Information about the\n recompiled input templates is stored descendant from\n OUTPUT_ROOT("DIEZ"):\n \n OUTPUT_ROOT("DIEZ",input template #) = \n input template name ^ file # ^ compiled routine name\n \n If cross-references for the file are compiled, they are\nwhich the cross-reference is defined are recompiled. If cross-references\n recompiled, and the compiled routine name is stored in\n OUTPUT_ROOT("DIKZ"):\n \n OUTPUT_ROOT("DIKZ") = compiled routine name\n \n If the data dictionary for the file is audited, an entry\n is made in the DD Audit file (#.6) and\n OUTPUT_ROOT("DDAUD") is set to 1:\n \n OUTPUT_ROOT("DDAUD") = 1\non the file are compiled, they are also recompiled.\n \n Example\n -------\n 1. In this example, regular cross-reference #4 (the "C" index), defined\n on field #12 in file #16200, is deleted. The "K" flag indicates that\n the entire ^DIZ(16200,"C") index is removed from the file.\n \n >D DELIX^DDMOD(16200,12,4,"K","MYOUT")\n \n >ZW MYOUT\n\n\nSee patch DI*22*31 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*6 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*34 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*19 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*37 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*5 in the National Patch Module for complete information on\nthis patch.\n\n
\nSee patch DI*22*35 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*3 in the National Patch Module for complete information on\nthis patch.\n\n
\nSee patch DI*22*40 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*48 in the National Patch Module for complete information\non this patch.\n\n
\nThis patch fixes some bugs, and contains an enhancement to address a Y2K\nWith this patch, if %%DT'["X" the above inputs are interpreted as July\nRoutine DIENVWRN is sent in order to prevent the inadvertent queuing\nduring the installation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options: \n \n Print Transport Global\n2000.\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 5. Inhibit users from login into the system. %DT and %DTC are used\nheavily in VISTA applications. The consequences of installing this patch\nwhile users are on the system are that users may get a 'source routine\nedited' error.\n \n 6. AXP Sites - Place TaskMan in a WAIT State.\n \n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*22.0*14\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\n2. Input such as "0700", where the input is exactly 4 numerics with "00"\nOptions, and Protocols? \n \n 8. After installing this patch, you need to move the routines DIDT\nand DIDTC from your production account into your manager account. Then, in\nthe manager account, rename:\n \n DIDT to %DT \n DIDTC to %DTC \n \n Example: ZL DIDT ZS %DT \nas the last to digits, was interpreted as July of the current year (if the\n \n 9. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n 10. AXP Sites - Remove TaskMan from WAIT State.\n OpenM/Cache Sites - Restart TaskMan.\n \n 11. Enable users' login.\n"P" and "F" flags weren't used). With this patch, if %DT'["X", "0700" is\ninterpreted as July 2000; if %DT["X", it is rejected.\n \n3. Input such as "070", where the input is exactly 3 numerics, and the\nfirst two numbers are a valid month and the third number is a 0, was\nissue.\ninterpreted as July of the current year (if the "P" and "F" flags weren't\nused). With this patch, "070" is rejected.\n \nEnhancement:\n-----------\nIntroduce a new "M" flag for %DT. This flag allows input such as "0701",\n"07/01", "JUL 01", "01 JUL" to be interpreted as July 2001, instead of\nJuly 1st.\n \n M Only Month and year input is allowed (example 1). If only a month\n \n and two digits are entered, interpret the two digits as a year\n instead of a day (example 2).\n \n If the M flag is used with the X flag, a month must be specified;\n otherwise, the input can be just a year (example 3).\n \n M Flag\n ================================================\n Date Date Returned\n Ex. Input Returned Without M\nRoutine: DIDT (%DT), DIDTC (%DTC)\n ------------------------------------------------\n 1) 7-05-2005 --invalid-- July 5, 2005\n 2) 7-05 July 2005 July 5, 2000*\n ================================================\n * Assumes the current year is 2000 and the P and F flags aren't used.\n \n M Flag with X\n ================================================\n Date Returned Date Returned\n Ex. Input With X Without X\n---------------------------------\n ------------------------------------------------\n 3) 05 or 2005 --invalid-- 2005\n ================================================\n \n \nNOISs:\n=====\nISP-0899-N2311\nISP-0899-N2314\nISP-0899-N2322\nBug fixes:\n \n \nThanks to Test Sites:\n====================\nWhite City, OR\nBay Pines CIOFO\n \n \nRoutine Summary: \n===============\n---------\nThe following routines are included in this patch. The second line of \nthese routines now look like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIDT (%DT) 6481242 6856270 14\n1. Input such as such as "07/00", "JUL 00", and "00 JUL", where the\n DIDTC (%DTC) 7099203 7770956 14\n \n \nInstallation Instructions: \n==========================\n ***********************************************************************\n * It is HIGHLY recommended that ALL Users and VISTA Background jobs *\n * be STOPPED. Failure to do so may result in a 'source routine *\n * edited' error. Edits will be lost and records may be left in an *\n * inconsistent state. *\ntwo-digit year is "00", was rejected even if inexact dates are allowed.\n ***********************************************************************\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, the should be\nremoved from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n The Environment Check Routine DIENVWRN will run automatically.\n\n
\nFixes "bad syntax at end of command or Xecute string" error in S2+7^DICL2.\n \nSee patch DI*22*51 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*38 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*43 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*44 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*45 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*47 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*50 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*46 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*54 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*56 in the National Patch Module for complete information\non this patch.\n\n
\nRoutines: DID1, DID2\n \n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 5. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\nRoutine: DID1\n Select INSTALL NAME: DI*22.0*7\n =========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 6. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n 7. You may optionally delete the pre-installation routine DIPR7.\n-------------\nBug: In a Standard DD Listing, the Descriptions of cross-references\nweren't formatted correctly within the margins of the report.\n(NOIS: ISW-1198-21324)\n \nRoutines: DIV, DIVR\n-------------------\nBug: If the UTILITY FUNCTIONS/VERIFY FIELDS option is used, the generated\n--------------------\nreport could scroll off the screen. This patch makes the option prompt for\ndevice, and if the report is printed to the screen, makes it issue the\n"Enter RETURN to continue or '^' to exit:" prompt at the end of each page.\n \nRoutines: DIVR, DIVR1\n---------------------\nBug: When the UTILITY FUNCTIONS/VERIFY FIELDS option is used, and if a\nrequired or key field equals only one or more spaces, the message\n"Missing" would be printed. This patch changes the message to "Equals only\n1 or more spaces" to more accurately reflect the reason an entry is\nBug: When running the List File Attributes option on a file that has\nflagged as having a possible problem.\n(NOIS: ISL-0499-51116)\n \nRoutine: DICATT\n---------------\nBug: The prompt after option 4, Modify File Attributes, had a typo:\nthe word "USER" should be "USE":\n \n DO YOU WANT TO USER THE SCREEN-MODE VERSION? Yes//\n ====\nextensive M code for Cross References, Input Transforms and the like, if\n \nRoutines: DIPR7, DINIT11B\n-------------------------\nBug: Change field 20 DEVELOPER in file 1 (FILE) so that LAYGO is not\nallowed to file 200 (NEW PERSON file). This should have never been\nallowed and was an oversite. DIPR7 is a pre-init routine that changes the\nsecond piece of the field from 200P to 200P'. DINIT11B is the routine\nthat is the part of the initialization of FileMan that brings in field 20.\n \n **NOTE** You may safely delete routine DIPR7 after installing this patch.\nthe Right Margin was small enough, it was possible to go into an endless\n \nNOIS\n====\n BRX-1295-10591\n ISL-0499-51116\n ISW-1198-21324\n \nThanks to Test Sites \n====================\n Bronx, NY\nloop. This was noticed when trying to List File Attributes for file #63\n White River Junction, VT\n Hampton, VA\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of \nthese routines now look like: \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999\n \nand sending the output to the Browser with a right margin less than 132.\nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DICATT 8217226 7872715 7\n DID1 10810057 10875512 7\n DID2 10525120 10677478 7\n DINIT11B 3195420 3197349 7\n DIPR7 n/a 27289 7\n DIV 3841210 6086701 7\nThe result was a "disk full" error.\n DIVR 8571704 10083576 7\n DIVR1 10947202 10953209 7\n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is\nrecommended that it be Queued for a time of generally least activity.\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, the should be\n(NOIS: BRX-1295-10591)\nremoved from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n\n
\nSee patch DI*22*53 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*57 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*61 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*55 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*58 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*60 in the National Patch Module for complete \ninformationon this patch.\n\n
\nSee patch DI*22*62 in the National Patch Module for complete \ninformationon this patch.\n\n
\nSee patch DI*22*65 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*69 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*63 in the National Patch Module for complete \ninformationon this patch.\n\n
\nThis patch repairs allocation errors when doing a call to the FileMan\nerror would only happen on a real file if it had several thousand\n \n 9. AXP Sites - Remove TaskMan from WAIT State. \n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login. \nindividual cross-references (which would not be likely to happen). Nois:\nKAN-0999-40493.\n \nRoutines: DICM0,DICM3\n=====================\nRepairs allocation error at S+14^DIC3. This would only happen when a\ncross-reference was on a pointer or variable pointer field, there were\nmany (over 1000) entries that pointed to an entry whose .01 field matched\nthe value being looked-up, but a screen made it so that most of the\nlookup routine ^DIC.\nentries with the pointer were not selected. Noises: HIN-0999-42903,\nATG-0999-32715, SLC-0999-52640, DAY-0899-41847.\n \n \nNOIS \n====\n ATG-0999-32715\n DAY-0899-41847\n HIN-0999-42903\n KAN-0999-40493\n \n SLC-0999-52640\n \nThanks to Test Sites \n====================\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of these\nroutines now look like: \n \n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DIC3 8138582 8139369 1,16\n DICM0 6941241 8997983 16\n DICM3 3812212 4576635 16\n \nRoutine: DIC3\n \nInstallation Instructions: \n==========================\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to be\nSTOPPED. Failure to do so may result in a 'source routine edited' error, the\nedits will be lost and records may be left in an inconsistent state. \n** \n \n 1. AXP sites: Review your mapped routine set. If any of the routine(s)\nlisted in the ROUTINE SUMMARY section are mapped, they should be removed from\n=============\nthe mapped set at this time. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system. \n \nThe environment check routine DIENVWRN will run automatically. Routine \nDIENVWRN is sent in order to prevent the inadvertent queuing during the \ninstallation of this patch. \n \n 3. The patch has now been loaded into a transport global on your system.\nRepairs allocation error at C4+2^DICUIX2. This happened because one of the\nYou now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\noptions: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of having users\nMailman files had some invalid nodes that looked like cross-references.\non the system while installing this patch are that users editing records will\nget a 'source routine edited' error, the edits will be lost and records may be\nleft in an inconsistent state. Note that most of these routines are heavily\nused in DHCP applications. \n \n 6. AXP Sites - Place TaskMan in a WAIT State. \n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \nEach node had a subscript that contained an "R" followed by a number. This\n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*16\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\nand Protocols? \n \n \n 8. AXP Sites - After the patch has been installed, rebuild your map set,\nif necessary. \n\n
\nSee patch DI*22*64 in the National Patch Module for complete \ninformationon this patch.\n\n
\nSee patch DI*22*70 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch DI*22*67 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*81 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*72 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nWhen a file or subfile is deleted, clean up "PT" nodes on pointed to \nfiles, "TRB" node on fields triggered in other other files, and "IX" nodes\nfor whole file cross-references. Also clean up "PT" nodes when a variable\npointer field is created, and then made into a multiple.\n \nSee patch DI*22*52 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*79 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*42 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*75 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*85 in the National Patch Module on FORUM for complete \ninformation on this patch.\n\n
\nRoutine: DICF1 \n \nThanks to Test Site \n====================\n Dayton, OH\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of\nthese routines now look like: \n \n--------------\n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DICF1 6446378 6462834 15 \n \nInstallation Instructions: \n==========================\nA problem was reported when using $$FIND1^DIC and the first\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to\nbe STOPPED. Failure to do so may result in a 'source routine edited'\nerror, the edits will be lost and records may be left in an\ninconsistent state. \n** \n \n 1. AXP sites: Review your mapped routine set. If DICF1 is mapped\non your system, it should be removed from the mapped set at this time. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nposition of the [.]VALUE was equal to a Comma, a Null Subscript error\nThis option will load the KIDS package onto your system. \n \nThe environment check routine DIENVWRN will run automatically. Routine \nDIENVWRN is sent in order to prevent the inadvertent queuing during the \ninstallation of this patch. \n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global. \n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nwould occurr at LOOP+3^DICFIX. For example, VALUE=",DOE,JANE"\nfollowing options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n 5. Inhibit users' login into the system. The consequence of\nhaving users on the system while installing this patch are that users\nediting records will get a 'source routine edited' error, the edits\nwill be lost and records may be left in an inconsistent state. Note\n \nthat DIC11 is heavily used in DHCP applications. \n \n 6. AXP Sites - Place TaskMan in a WAIT State. \n OpenM/Cache Sites - STOP TaskMan. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*15 \n ==========\nNOIS \n \n Answer 'YES' to 'Want KIDS to INHIBIT LOGONs during the\ninstall?\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols? \n \n \n 8. AXP Sites - After the patch has been installed, rebuild your\nmap set, if necessary. \n \n====\n 9. AXP Sites - Remove TaskMan from WAIT State. \n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login. \n DAY-0999-41729\n\n
\nSee patch DI*22*88 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*73 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*77 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*78 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*87 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*86 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*18 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*59 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*82 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*41 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nRoutine: ^DIK1\n \n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu\nOptions, and Protocols?\n \n 8. AXP Sites - After the patch has been installed, rebuild your map\nset, if necessary.\n \n 9. AXP Sites - Remove TaskMan from WAIT State.\n OpenM/Cache Sites - Restart TaskMan.\n \n - the difference between X and the ien of the next record is large\n 10. Enable users' login.\n \n^DIK could go into an extremely time-consuming loop as it attempts to find\nthe ien of the last (or next) record in the file.\n \nFor example, file 16010 has the following header node and entries:\n \n ^DIZ(16010,0) = TEST^16010^xxx^3\n ^------- 3rd piece of header node\n--------------\n ^DIZ(16010,1,0) = FIRST\n ^DIZ(16010,10,0) = SECOND\n ^DIZ(16010,12345678901234,0) = THIRD\n \nIf you use ^DIK to delete entry #10 (and xxx = 10) or entry\n#12345678901234 (and xxx = 12345678901234), ^DIK could go into a\ntime-consuming loop.\n(NOIS: IVM-1099-31783)\n \nY2K Waiver Exemption Number:\nBug: Suppose ^DIK is used to delete a record with an internal entry number\n============================\nY2KWE0005\n \nNOIS:\n=====\nIVM-1099-31783\n \nThanks to Test Sites:\n=====================\nHEC-ATLANTA\n(ien) of X in a file, X equals what's in the 3rd piece of the header node\n \nRoutine Summary:\n================\nThe following routine is included in this patch. The second line of the\nroutine now looks like:\n \n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999\n \nCHECK^XTSUMBLD results:\n \nof the file, and there is no record in the file with an ien of X-1. If\n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n DIK1 6302851 6092464 1,10\n \nInstallation Instructions:\n==========================\n *************************************************************************\n * It is HIGHLY recommended that ALL Users and VISTA Background jobs *\n * to be STOPPED. Failure to do so may result in a 'source routine *\n * edited' error, the edits will be lost and records may be left in an *\neither of the following is true:\n * inconsistent state. *\n *************************************************************************\n \n 1. AXP sites: Review your mapped routine set. If any of the\nroutine(s) listed in the ROUTINE SUMMARY section are mapped, the should be\nremoved from the mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n \n The environment check routine DIENVWRN will run automatically.\nRoutine DIENVWRN is sent in order to prevent the inadvertent queuing\nduring the installation of this patch.\n \n 3. The patch has now been loaded into a transport global on your\nsystem. You now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n - X is the last ien used in the file, and the difference between X and\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 5. Inhibit users' login into the system. The consequence of having\nusers on the system while installing this patch are that users editing\nrecords will get a 'source routine edited' error, the edits will be lost\nand records may be left in an inconsistent state. Note that most of these\nroutines are heavily used in DHCP applications.\n the ien of the preceding record is large; or\n \n 6. AXP Sites - Place TaskMan in a WAIT State.\n OpenM/Cache Sites - STOP TaskMan.\n \n 7. On the KIDS menu, under the 'Installation' menu, use the\nfollowing option:\n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: DI*22.0*10\n ==========\n\n
\nSee patch DI*22*68 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*49 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*90 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*94 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*92 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*83 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*91 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*89 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*103 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*99 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis patch fixed a few minor bugs and adds some enhancements to correct\nin the ^DIC lookup. This will get them clear out of the lookup.\ninstead $O through the index on the pointer, so records will not be in\nalphabetic sequence. This sequence was always used on pointers in V21.\nNOIS: MAC-0999-63042\n \nRoutine: DIC5\n-------------\nWhen a numeric lookup value is entered and indexed field is a pointer,\nmake lookup by IEN work the way it did in version 21. NOIS:\nFGH-1099-30988, PTH-1099-21795, BHH-1099-41454\n \nPreviously, users wre able to enter a single up-arrow ^ but this only took\nRoutine: DIC3\n-------------\nLookups on the DRUG file by synonym were selecting the right drug, but\ndisplaying the wrong .01 field value. This happened when DIC(0) contained\nan "O", there was more than one exact match on the SYNONYM index to the\nlookup value, but all but one match were screened out by a DIC("S")\nscreen. NOIS: BHH-1099-40749, CAH-1099-31208, ISB-1099-33134,\nIOW-1099-42292, POP-1099-42462, TUC-1099-61597\n \nRoutine: DIC\nthem out of the search through the current index. If there were many\n------------\nDIC("W") was being set earlier in a call to ^DIC in Version 22 than it was\nin Version 21. This caused an UNDEF error to occur in some files with a\nuser-defined lookup. This change restores backwards compatibility in this\narea to V21. NOIS: MUR-0999-31608\n \nRoutine: DICF4\n--------------\nWhen a call to FIND^DIC was made with the "M" flag, and an entry was found\non an index other than the first one in the list, an extra node was\nindexes being searched, the search could continue for a long time with no\nreturned containing the external index value, even if the FIELDS parameter\ndid not contain "IXE". This caused the Finder Delphi Component to display\nthe wrong values. NOIS: BAY-1199-30365\n \nRoutine: DICA\n-------------\nIf an UPDATE^DIE call is made and the FDA uses a LAYGO/Finding node to\nlookup or add an entry at the top level of a file, and an Adding node is\nused to add an entry into a multiple within that record, and the top level\nrecord is added because it was not found, a null subscript error would\nway to exit. NOIS: NTH-0399-71535.\noccur. For example, if the FDA is:\n \n FDA(1000,"?+1,",.01)="TEST ENTRY"\n FDA(1000.02,"+2,?+1,",.01)="TEST SUBENTRY"\n \nand the Updater has to add TEST ENTRY to file #1000, a null subscript\nerror will occur.\n \n \nRoutines: DIE1,DIE2\n \n-------------------\nIf ^DIE was used to edit a subfile directly, and that subfile was at least\ntwo levels down from the top, ^DIE was not updating the DA array correctly\nwhen the user went down into and back out of multiples within that\nsubfile. NOIS: ISW-0599-20886\n \nRoutine: DIEQ\n-------------\nSet the DA array to the subfile level if the user enters ? or ?? at the\nSelect prompt of a multiple. This ensures that xecutable help, screens on\nRoutines: DDSU,DICQ,DICQ1,DICLIX\npointer or sets, and input transforms on the .01 field of the multiple can\nrely on the DA array to be at the subfile level, whether ? or ?? is\nentered at the Select prompt or at the .01 field of the multiple.\n \nNOIS \n====\n ATG-0397-30298\n ATG-1199-31667\n BAY-1199-30365\n BHH-1099-40749\n--------------------------------\n BHH-1099-41454\n BRX-0197-11979\n BRX-0699-11412\n CAH-1099-31208\n CHA-1099-30189\n FGH-1099-30988\n IOW-1099-42292\n ISB-1099-33134\n ISL-0699-52609\n ISW-0199-21924\nControl number of entries displayed in "?" help. Developers needed a way\n ISW-0599-20886\n LAH-1099-60966\n MAC-0999-63042\n MAD-0394-40135\n MUR-0999-31608\n NHM-1199-10884\n NTH-0399-71535\n PAL-1099-60334\n POP-1099-42462\n POR-1199-51265\nto control question mark help in the ^DIC lookup so that the output didn't\n PTH-1099-21795\n TUC-1099-61597\n \nThanks to Test Sites \n====================\nFort-Meade\nWashington\nPortland\nPoplar-Bluff\nDavid Alexander - Birmingham CIOFO\ndeficiencies in the FileMan Lookup routines ^DIC*, Finder routines ^DICF*,\nscroll off the screen. New input variable\nLucille Barrios - Washington ISC\n \nThanks to anyone I may have missed on this list. Your help in testing is\ninvaluable to us.\n \nRoutine Summary: \n================\n The following routines are included in this patch. The second line of these\nroutines now look like: \n \nDIC("?N",file#)=number_of_entries_to_display can be set to the number of\n <tab>;;22.0;VA FileMan;**[patch list]**;Mar 30, 1999 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n DDSU 4516702 4589256 4\n DIC 10513568 9848200 4\n DIC0 4489087 4839635 4\n DIC1 8396997 8559944 1,4\nentries to be displayed at any one time in question mark help. NOIS:\n DIC2 2989510 4974600 4\n DIC3 8139369 7291022 1,16,4\n DIC4 4973984 5435232 4\n DIC5 new 1959090 4\n DICA 8300985 8533062 1,4\n DICF2 8772057 8940451 4\n DICF3 3363767 3125335 4\n DICF4 7990992 7644291 4\n DICF5 2319707 3414721 4\n DICFIX 6867704 6906289 4\nISW-0199-21924.\n DICLIX 6388314 6415652 4\n DICM 8046960 8330209 4\n DICM0 8997983 9037748 16,4\n DICM2 5782025 6032022 4\n DICM3 4576635 4576635 16,4\n DICN 6535731 6787162 4\n DICN1 7864160 7828348 4\n DICQ 6248469 6387812 4\n DICQ1 7645506 7976918 4\n DICUIX1 3761139 3826551 4\n \n DICUIX2 7134369 7214869 4\n DIE 10606815 10620115 1,4\n DIE1 10290843 10471504 1,4\n DIE17 9556587 9659127 4\n DIE2 8785703 8634855 4\n DIE3 4915247 5222949 4\n DIED 8319960 10169985 4\n DIEQ 5540099 5793825 4\n DIEZ1 8970637 9131334 4\n \nRoutines: DIC4,DICF4,DICM0,DICM3,DICN,DICQ1,DIE,DIE1,DIE17,DIE3,DIED,DIEZ1\n \nInstallation Instructions: \n==========================\n** It is HIGHLY recommended that ALL Users and VISTA Background jobs to be\n STOPPED. Failure to do so may result in a 'source routine edited'\n error, the edits will be lost and records may be left in an\n inconsistent state.\n**\n \n 1. AXP sites: Review your mapped routine set. If any of the routine(s)\n--------------------------------------------------------------------------\nlisted in the ROUTINE SUMMARY section are mapped, they should be removed from\nthe mapped set at this time.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \nThe environment check routine DIENVWRN will run automatically. Routine \nDIENVWRN is sent in order to prevent the inadvertent queuing during the \ninstallation of this patch.\n \nControl lookup to pointed-to files. During lookups on files with\n 3. The patch has now been loaded into a transport global on your system.\nYou now need to use KIDS to install the transport global.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the\nfollowing options:\n \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \neither indexed pointer or variable pointer fields, FileMan does a lookup\n \n 5. Inhibit users' login into the system. The consequence of having\nusers on the system while installing this patch are that users editing\nrecords will get a 'source routine edited' error, the edits will be lost\nand records may be left in an inconsistent state. Note that most of these\nroutines are heavily used in DHCP applications.\n \n 6. AXP Sites - Place TaskMan in a WAIT State. \n OpenM/Cache Sites - STOP TaskMan. \n \non the pointed-to file, lookup for a match to the lookup value entered by\n 7. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: DI*22.0*4\n ==========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\nand Protocols? \n \n \nand Editing routines ^DIE*.\nthe user. FileMan always looked on either the "B" index only on the\n 8. AXP Sites - After the patch has been installed, rebuild your map set,\nif necessary. \n \n 9. AXP Sites - Remove TaskMan from WAIT State. \n OpenM/Cache Sites - Restart TaskMan. \n \n 10. Enable users' login. \npointed-to file (if DIC(0) did not contain "M"), or else on all lookup\nindexes. A new input array to the interactive lookup ^DIC or to the\nsilent data base server lookup routine FIND^DIC, allows the developer to\nspecify what indexes are to be used during lookup on a pointed-to file.\nThe array for ^DIC looks like\n DIC("PTRIX",from_file#,pointer_field#,to_file#)=list_of_indexes.\nFor the Finder, it looks like\n DINDEX(("PTRIX",from_file#,pointer_field#,to_file#)=list_of_indexes\nFor ^DIE, it looks like:\n \n DIE("PTRIX",from_file#,pointer_field#,to_file#)=list_of_indexes\n \nRoutines: DIC,DIC0,DIC1,DIC2,DIC3,DIC5,DICFIX,DICM,DICM0,DICM3 \n--------------------------------------------------------------\nConTinue looking through all indexes. ^DIC lookup does an initial pass\nthrough the list of indexes, looking for matches to the lookup value as it\nwas entered by the user. If any are found, they are presented to the\nuser, and whether or not any are accepted, FileMan gets out. Only if it\nfinds no matches, does it attempt transforms on the lookup, such as\nconverting pointers, variable pointers, sets or dates to their internal\n***** Y2K Waiver Exemption ID#: Y2KWE0015 *****\nformat, or converting the lookup value to upper case. This can cause the\nlookup to miss some of the matching values. A new flag "T" can be put\ninto DIC(0) that will cause FileMan to keep looking until it has either\ntried everything, or until the user selects an entry. In addition, the\ntransforms for pointers, variable pointers, dates or sets are done during\nthe first pass, so indexes are truly searched in the order requested by\nthe user. NOIS: ATG-0397-30298, BRX-0197-11979, MAD-0394-40135.\n \nRoutines: DICF2,DICF3,DICF4,DICF5 \n---------------------------------\n \n"O" flag in Finder call. It was discovered here that the "O" flag in the\nfinder didn't work the same in version 22 as it did in version 21. With\nthis patch, the behavior is the same as version 21, in that an entire pass\nthrough all indexes is made to find any exact matches, before doing a\nsecond pass to find partial matches. NOIS: PAL-1099-60334, LAH-1099-60966\n \nRoutine: DICN1\n-------------- \n'Before' values in SET/KILL logic. It was discovered here that when a new\nentry was added using the classic interactive lookup ^DIC, the X1 and X2\nRoutines: DIC,DIC1,DICM,DICM0,DICM3\narray entries for the "BEFORE" values for use in the SET and KILL logic of\nnew style indexes were not always reliable. This corrects that bug.\n \nRoutine: DICM\n-------------\n'Missing Right Parenthesis' error in Print. When doing a print, at the\nPRINT FIELD prompt, if a field name greater than 30 characters long was\nentered, along with a header qualifier in mixed case, a 'missing right\nparenthesis' error occurred. This error was actually happening during the\nlookup for field name on the DD. NOIS: BRX-0699-11412.\n-----------------------------------\n \nRoutine: DICM2\n--------------\nVariable pointer prefix in lower case. When doing a lookup on an indexed\nvariable pointer field, if the user entered the prefix in lower case or\nmixed case, but the prefix was in upper case on the file, the lookup\nfailed. NOIS: ISL-0699-52609.\n \nRoutine: DICUIX2\n----------------\n"^^" OUT. Users will be allowed to enter a double up-arrow ^^ at a prompt\nUNDEF error in lookup. It was discovered here that an UNDEF error could\noccur if the code used to build index information for the classic lookup\n^DIC or the Finder FIND^DIC could not determine what field was indexed.\n \nRoutines: DICQ, DICQ1, DICUIX1\n------------------------------\nQuestion mark help was very slow when a fairly large file pointed to a\nvery large file like the PATIENT file. We were building a temporary index.\nThe algorithm that decides when to build an index was changed. Also, in\nquestion mark help, we won't ever build a temporary index, but will\n\n\nSee patch DI*22*100 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*107 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*102 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*108 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*109 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*104 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*96 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*97 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*113 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch DI*22*101 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis Build file entry contains the Options, Security Keys, and Remote\nProcedures used by VA FILEMAN.\n\n
\nPatch DI*22.2*1 will repair VA FileMan 22.2 defects.\n\n
\nThis patch provides an option to map a VistA resource to a \nFile Name (#) Field Name (#) New/Modified/Deleted\n \n \nInstallation Instructions:\n--------------------------\n 1. From the Kernel Installation and Distribution System (KIDS) Menu,\n select the Installation menu. \n 2. Use Load a Distribution. You may need to precede the host file name\n with a directory name.\n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n------------- -------------- -------------\n following options. When prompted for the INSTALL NAME, enter DI*22.2*9.\n a. Backup a Transport Global - This option will create a backup message\n of any routines exported with this patch. It will not backup any other\n changes such as DDs or templates.\n b. Compare Transport Global to Current System - This option will allow\n you to view all changes that will be made when this patch is installed.\n It compares all components of this patch.\n c. Verify Checksums in Transport Global - This option will allow you to\n ensure the integrity of the routines that are in the transport global.\n 4. From the Installation Menu, select the Install Package(s) option and\nEntity (#1.5) New\n when prompted for the INSTALL NAME, enter DI*22.2*9.\n 5. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//" enter NO.\n 6. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//"\n enter NO.\n 7. When prompted "Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? NO//" enter NO.\n 8. If prompted "Delay Install (Minutes): (0 60): 0//" enter 0.\n \n \n \nExample Install:\n \nSelect OPTION NAME: XPD MAIN Kernel Installation & Distribution System\n \n Edits and Distribution ...\n Utilities ...\n Installation ...\n \nSelect Kernel Installation & Distribution System <TEST> Option: INstallation\n \nForm Name File # New/Modified/Deleted\n 1 Load a Distribution\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n \nSelect Installation <TEST> Option: 1 Load a Distribution\n--------- ------ --------------------\nEnter a Host File: /srv/vista/oak/user/hfs/DI_222_9_VPR_1_8.KID\n \nKIDS Distribution saved on Oct 02, 2018@10:54:44\nComment: Combined patches DI*22.2*9 and VPR*1*8\n \nThis Distribution contains Transport Globals for the following Package(s):\n DI*22.2*9\n VPR*1.0*8\nDistribution OK!\n \nDDE ENTITY ENTER/EDIT 1.5 New\nWant to Continue with Load? YES// \nLoading Distribution...\n \n DI*22.2*9\n VPR*1.0*8\nUse INSTALL NAME: DI*22.2*9 to install this Distribution.\n \n 1 Load a Distribution\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n \n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n \n \nSelect Installation <TEST> Option: 6 Install Package(s)\nSelect INSTALL NAME: DI*22.2*9 Loaded from Distribution 10/2/18@12:43:4\nOption Name Type New/Modified/Deleted\n => Combined patches DI*22.2*9 and VPR*1*8 ;Created on Oct 02, 2018@10:54\n \nThis Distribution was loaded on Oct 02, 2018@12:43:47 with header of \n Combined patches DI*22.2*9 and VPR*1*8 ;Created on Oct 02, 2018@10:54:44\n It consisted of the following Install(s):\n DI*22.2*9 VPR*1.0*8\nChecking Install for Package DI*22.2*9\n \nInstall Questions for DI*22.2*9\n \n----------- ---- --------------------\nIncoming Files:\n \n \n 1.5 ENTITY\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? NO// \n \nChecking Install for Package VPR*1.0*8\n \nInstall Questions for VPR*1.0*8\nrepresentation of a Summary Document Architecture (SDA) data type.\nEntity Enter/Edit \n \nIncoming Files:\n \n \n 560 VPR SUBSCRIPTION\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? NO// \n \n \nWant KIDS to INHIBIT LOGONs during the install? NO// \n[DDE ENTITY ENTER/EDIT] run routine New\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? NO// \n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// NETWORK\n \n \n \nEntity Mapping \nPost-Installation Instructions:\n-------------------------------\nNone\n \n \nBackout and Rollback Procedure:\n-------------------------------\nDuring the VistA Installation Procedure of the KIDS build, the \ninstaller should back up the modified routines by the use of the\n'Backup a Transport Global' action (step 3a in the Installations \n[DDE ENTITY MAPPING] menu New\nInstructions below).\n \nIf rollback/backout is required, the installer can use the MailMan\nmessage to restore the routines to previous state. \n \nTo backout the ENTITY (#1.5) file and DDE EDIT ENTITY input template, use \nthe EN^DIU2 API. Caution should be taken when using this API. For more \ninformation on usage of this API see FileMan 22.2 Developer Guide. The\nfollowing is an example execution to remove files and input template:\n \nOther Options[DIOTHER] menu Modified\nS DIU=1.5,DIU(0)="DT" D EN^DIU2\n \nTo rollback/backout DDE options exported with this patch, may be disabled\nby using VA FileMan to assign an Out of Order message as follows:\n \nVA FileMan 22.2\n \n \nSelect OPTION: 1 ENTER OR EDIT FILE ENTRIES\n \n \n \nInput to what File: OPTION// (11330 entries)\nEDIT WHICH FIELD: ALL// OUT OF ORDER MESSAGE \nTHEN EDIT FIELD: \n \n \nSelect OPTION NAME: Entity Mapping DDE ENTITY MAPPING\nOUT OF ORDER MESSAGE: ROLLBACK PATCH DI*22.2*9\n \nSelect OPTION NAME: \n \n \nTo rollback/backout DDE form exported with this patch, use VA FileMan\n[DDS DELETE A FORM] option as follows:\n \nVA FileMan 22.2\n \n \nSelect OPTION: OTHER OPTIONS \nSelect OTHER OPTION: SCREENMAN \nSelect SCREENMAN OPTION: DELETE A FORM \nInput Template File # New/Modified/Deleted\n \nDelete Form for what File: OPTION// ENTITY (2 entries)\n \nSelect FORM to delete: DDE ENTITY ENTER/EDIT DDE ENTITY ENTER/EDIT\n #165 3/6/18 File #1.5\n \n \n BLOCKS USED ON FORM "DDE ENTITY ENTER/EDIT" (IEN #165)\n \n Internal Used on\n-------------- ------ --------------------\n Entry Number Block Name Other Forms? Deletable?\n ------------ ------------- ------------ ----------\n 602 DDE ENTITY HEADER NO YES\n 603 DDE ENTITY 1 NO YES\n 604 DDE ITEMS NO YES\n 605 DDE ENTITY 2 NO YES\n 606 DDE ENTITY 3 NO YES\n 607 DDE ITEM FIXED NO YES\n 608 DDE ITEM ID NO YES\n 609 DDE ITEM SIMPLE NO YES\nDDE EDIT ENITY 1.5 New\n 610 DDE ITEM WORD PROC NO YES\n 611 DDE ITEM COMPLEX NO YES\n 612 DDE ITEM ENTITY NO YES\n 613 DDE ITEM LIST NO YES\n 614 DDE COMPLEX LIST NO YES\n 615 DDE LIST FILE NO YES\n 616 DDE LIST COMPLEX NO YES\n 617 DDE LIST COMPLEX ITEMS NO YES\n \n \n \n \nDelete all deletable blocks used on form DDE ENTITY ENTER/EDIT\nfrom the BLOCK file (Y/N)? YES// \n \n \nDelete blocks without prompting (Y/N)? NO// y YES\n \nContinue (Y/N)? NO// YES\n \nDeleting form DDE ENTITY ENTER/EDIT (IEN #165) ...\n \n \nDeleting block DDE ENTITY HEADER (IEN #602) ...\nDeleting block DDE ENTITY 1 (IEN #603) ...\nDeleting block DDE ITEMS (IEN #604) ...\nDeleting block DDE ENTITY 2 (IEN #605) ...\nDeleting block DDE ENTITY 3 (IEN #606) ...\nDeleting block DDE ITEM FIXED (IEN #607) ...\nDeleting block DDE ITEM ID (IEN #608) ...\nDeleting block DDE ITEM SIMPLE (IEN #609) ...\nDeleting block DDE ITEM WORD PROC (IEN #610) ...\nDeleting block DDE ITEM COMPLEX (IEN #611) ...\nBlood Bank Clearance:\nDeleting block DDE ITEM ENTITY (IEN #612) ...\nDeleting block DDE ITEM LIST (IEN #613) ...\nDeleting block DDE COMPLEX LIST (IEN #614) ...\nDeleting block DDE LIST FILE (IEN #615) ...\nDeleting block DDE LIST COMPLEX (IEN #616) ...\nDeleting block DDE LIST COMPLEX ITEMS (IEN #617) ...\n \nDONE!\n \n \n---------------------\nRoutine Information:\n====================\n \nThe second line of each of these routines now looks like:\n ;;22.2;VA FileMan;**[Patch List]**;Jan 05, 2016;Build 46\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \nRoutine Name: DDE\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*9 contains\n Before: n/a After: B4683326 **9**\nRoutine Name: DDE1A\n Before: n/a After: B737990 **9**\nRoutine Name: DDEG\n Before: n/a After:B122631592 **9**\nRoutine Name: DDEGET\n Before: n/a After: B10359109 **9**\nRoutine Name: DDEMAP\n Before: n/a After: B44771305 **9**\nRoutine Name: DDEOPT\nchanges to a package referenced in ProPath standard titled: BBM Team\n Before: n/a After: B794105 **9**\nRoutine Name: DDERR\n Before: n/a After: B683652 **9**\nRoutine Name: DDEX\n Before: n/a After: B1026050 **9**\nRoutine Name: DII1\n Before: B2240976 After: B2361298 **8,10,9**\n \nRoutine list of preceding patches: 10\nReview of VistA Patches. This patch does not alter or modify any VistA\nBlood Bank software design safeguards or safety critical elements\nfunctions.\n \nThe patch includes a new ENTITY (#1.5) file. The ENTITY file defines \nRISK ANALYSIS: Changes made by patch DI*22.2*9 have no effect on Blood\nBank software functionality, therefore RISK's none. \n \n \nTest Sites:\n-----------\nCharleston, SC\nNorth Chicago, IL\n \nSoftware and Documentation Retrieval Instructions:\nthe VistA resource being mapped to an SDA type.\n-------------------------------------------------- \nSoftware is being released as a host file and documentation describing\nthe new functionality introduced by this patch is available.\n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may \nalso elect to retrieve files directly from a specific server. \nSites may retrieve the software and/or documentation directly using \nSecure Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory \nat the following OI Field Offices:\n \n \nHines: fo-hines.domain.ext \nSalt Lake City: fo-slc.domain.ext\n \nSoftware File Name SFTP Mode\n----------------------------------------------------------------------\nVPR*1*8 & DI*22.2*9 DI_222_9_VPR_1_8.KID ASCII\n \n \nDocumentation can also be found on the VA Software Documentation Library \nPatch Components:\nat: http://www.domain.ext/vdl/ \n \nTitle File Name SFTP Mode\n-----------------------------------------------------------------------\nFileMan 22.2 Technical Manual FM22_2TM.PDF Binary\n \n \nPatch Installation:\n-------------------\nSoftware is being released as a host file, DI_222_9_VPR_1_8.KID. The host\n-----------------\nfile contains two patches; DI*22.2*9 and VPR*1*8.\n \nPatches DI*22.2*9 and VPR*1*8 are scheduled to be released nationally as a\nbundle. Installation of these patches into Production within the first 15\ndays from the National Release date is requested. The VA leadership has asked\nfor an expedited release to comply with the schedule for the high profile\nMission Act. Certain functionality has to be loaded into production in 130\nVA Medical Centers within a short timeframe. We appreciate your cooperation.\n \n \n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than\n2 minutes to install.\n \nNOTE: This patch was created with VA FileMan 22.2, so please ensure\nthe target system has also been upgraded to this version, otherwise\ninstallation will fail.\n\n
\n \n===========\n results\n Resolution:\n Change to DICOMP0 to handle variable pointers correctly\n \n10. Ticket: I16902120FY18\n Problem:\n If the variable %DT(0) is defined when an Input Transform is executed,\n it causes incorrect information\n Resolution:\n Change DICN to new the variable before executing the Input Transform\n This patch corrects twelve issues with VA FileMan 22.2. These issues where\n \n11. Ticket: I17417683FY18, I10449501FY16\n Problem:\n Audit is not recording changes if it happens during a trigger to another\n file\n Resolution:\n The problem is the DA variable is changed. Change DICR to save the DA\n array and other variables before auditing and then restore the variables\n \n12. Ticket: R15604177FY17\n discovered at sites that have installed VA FileMan 22.2 and DI*22.2*10.\n Problem:\n If the records being transferred is in a file that contain a multiple field\n that uses DINUM in the Input Transform, then FileMan stacks the DA array,\n but never unstacks it when it tries to delete the record\n Resolution:\n Change DIT0 to reset DA to the correct record before deleting\n \n \nTest Sites:\n-----------\n \n \n \n \nSoftware and Documentation Retrieval Instructions:\n-------------------------------------------------- \nSoftware is being released as a host file and documentation describing\nthe new functionality introduced by this patch is available.\n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may \n \nalso elect to retrieve files directly from a specific server. \nSites may retrieve the software and/or documentation directly using \nSecure Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory \nat the following OI Field Offices:\n \nHines: fo-hines.domain.ext \nSalt Lake City: fo-slc.domain.ext\n \n \nDocumentation can also be found on the VA Software Documentation Library \nPatch Components:\nat: http://www.domain.ext/vdl/ \n \nTitle File Name SFTP Mode\n-----------------------------------------------------------------------\nFileMan 22.2 Technical Manual FM22_2TM.PDF Binary\n \n \nPatch Installation:\n \nPre-Installation Instructions:\n-----------------\n------------------------------\nThis patch can be queued for installation. TaskMan does not have to be\nstopped, Health Level 7 (HL7) filers do not need to be stopped, and\nusers may be on the system. The patch should be installed during\nnon-peak hours to minimize potential for disruption to users. This\npatch should take less than 1 minute to install.\n \n \nInstallation Instructions:\n--------------------------\n \n1. Choose the MailMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter\n DI*22.2*10.\n a. Print Transport Global - This option lets you print the contents\n of a Transport Global that is currently loaded in the ^XTMP\nFile Name (#) Field Name (#) New/Modified/Deleted\n global.\n b. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as functions.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n d. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n------------- -------------- -------------\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option\n and when prompted for the INSTALL NAME, enter DI*22.2*14.\n \n5. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' respond NO.\n \n7. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//" respond NO.\nAssociated patches: DI*22.2*13\nAUDIT (#1.1) OLD VALUE (2) Modified\n \n8. If prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//" respond NO. \n \n9. If prompted "Delay Install (Minutes): (0 - 60): 0//" respond 0.\n \n \nPost-Installation Instructions:\n-------------------------------\nYou need to run EN^DI14POST to check for bad nodes on multiples. This\n NEW VALUE (3)\nis issue #8. The routine will find all bad nodes and prompt you to fix\nthem. The results will be kept in the ^XTMP("DI14") global for 30 days,\nunless you run the report again, and can be reversed by using the \nRESTORE^DI14POST call.\n \n \nBackout and Rollback Procedure:\n-------------------------------\nThis patch consists of routines and a fix to the AUDIT file. During the VistA\nInstallation Procedure of the KIDS build, the installer should back up the\n \nmodified routines by the use of the 'Backup a Transport Global' action\n(step 3b in the Installations Instructions below).\n \nIf rollback/backout is required, the installer can restore the routines\nusing the MailMan message that were saved prior to installing the\npatch. The changes to the two fields in the AUDIT file can remain.\n \n \nRoutine Information:\n====================\n \nThe second line of each of these routines now looks like:\n ;;22.2;VA FileMan;**[Patch List]**;Jan 05, 2016;Build 2\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \nRoutine Name: DI14POST\n Before: n/a After: B9063359 **14**\nRoutine Name: DICN\n Before: B21480119 After: B21929121 **2,5,13,14**\n \nRoutine Name: DICOMP0\n Before: B23489999 After: B27698020 **2,14**\nRoutine Name: DICR\n Before: B25667667 After: B26163162 **14**\nRoutine Name: DIDH1\n Before: B22350242 After: B23605706 **14**\nRoutine Name: DIDT\n Before: B25746733 After: B26129943 **14**\nRoutine Name: DIEZ\n Before: B23918443 After: B24336790 **14**\nBlood Bank Clearance:\nRoutine Name: DIFROMS2\n Before: B45453261 After: B51495195 **3,5,14**\nRoutine Name: DINIT20\n Before: B30255167 After: B30371045 **2,14**\nRoutine Name: DINIT2A4\n Before: B37901832 After: B37907044 **14**\nRoutine Name: DIP1\n Before: B36571552 After: B36617181 **14**\nRoutine Name: DIQ1\n Before: B9302112 After: B9407505 **14**\n---------------------\nRoutine Name: DIT0\n Before: B5572177 After: B5692057 **14**\n \nRoutine list of preceding patches: 13\n \nPlease see the description on Forum\n2/5/2019\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*14 contains\nchanges to a package referenced in ProPath standard titled: BBM Team\n \nReview of VistA Patches. This patch does not alter or modify any VistA\nBlood Bank software design safeguards or safety critical elements\nfunctions.\n \nRISK ANALYSIS: Changes made by patch DI*22.2*14 have no adverse effect on\nBlood Bank software functionality, therefore RISK is none. \n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nSubject: BUG FIXES TO VA FILEMAN\n1. Ticket: I12133765FY17\n Problem:\n Sort templates don't show previous values when editing the template\n Resolution:\n Change DIP1 to display previous value\n \n2. Ticket: I10027710FY16\n Problem:\n Date utility, %DT, allows incorrect time. Calling %DT with X=3160707.8\n should return Y=-1\n \n Resolution:\n Change DIDT to return Y=-1 if X contains an incorrect time. Post install\n routine DI14POST will resave DIDT as %DT.\n \n3. Ticket: R13378947FY17\n Problem:\n Can't print OLD VALUE (#2) and NEW VALUE (#3) fields from AUDIT (#1.1) file\n Resolution:\n Change the logic in the computed fields #2 and #3. Replace If statement\n with $Select. Also, change DINIT20, which sets the logic when FileMan\nCategory: ROUTINE\n is initialized.\n \n4. Ticket: INC3327007\n Problem:\n Add APPLICATION GROUP to Data Dictionary List File Attributes option\n Resolution:\n Change DIDH1 to display APPLICATION GROUP\n \n5. Ticket: INC1570061\n Problem:\n DATA DICTIONARY\n Maximum length of new style cross reference is too short\n Resolution:\n Change MAXIMUM LENGTH (#6) field in INDEX (#.11) file from 240 to 999.\n Add change to DI14POST and DINIT2A4\n \n6. Ticket: INC1550303\n Problem:\n Undefined error when doing an Inquire to a file that has a computed field\n that calls EN^DIQ1\n Resolution:\n \n Change DIQ1 to new the variables C and DI at tag EN\n \n7. Ticket: I16938507FY18\n Problem:\n The variable DISYS is undefined when calling EN^DIEZ in background\n Resolution:\n Move the call to DT^DICRW to earlier in the routine. It sets DISYS.\n \n8. Ticket: I17087603FY18\n Problem:\nDescription:\n When a partial Data Dictionary containing a multiple is distributed using\n KIDS, the zero node of sub dictionary has the wrong first piece\n Resolution:\n Change DIFROMS2; comment out line that was setting the sub dictionary zero\n node incorrectly to fix the bug. Post Install EN^DI14POST will check and\n correct any corrupted sub dictionaries.\n \n9. Ticket: INC0105488\n Problem:\n Queries for data that utilizes a variable pointer field could be missing\n\n\nDescription:\n \n \nPost-Installation Instructions:\n-------------------------------\nnone\n \n \nBackout and Rollback Procedure:\n------------------------------- \nIf rollback/backout is required, the installer can restore the routines\nusing the MailMan message that were saved prior to installing the\nnone\npatch.\n \n \nRoutine Information:\n====================\nThe second line of each of these routines now looks like:\n ;;22.2;VA FileMan;**[Patch List]**;Jan 05, 2016;Build 1\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \n \nRoutine Name: DDEG\n Before:B128480515 After:B129431147 **9,16,17**\nRoutine Name: DDEPRT\n Before: B48500922 After: B48600939 **16,17**\n \nRoutine list of preceding patches: 16\n \n \nBlood Bank Clearance:\n---------------------\n?/??/2019\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*17 contains\nchanges to a package referenced in ProPath standard titled: BBM Team\nReview of VistA Patches. This patch does not alter or modify any VistA\n===========\nBlood Bank software design safeguards or safety critical elements\nfunctions.\n \nRISK ANALYSIS: Changes made by patch DI*22.2*17 have no adverse effect on\nBlood Bank software functionality, therefore RISK is none. \n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. Problem:\nPatch 17 correct 2 issues that were discovered during pre-load\n Word processing and free text fields can contain control characters from\n the extended character set ($C values of 127 to 159)\n Resolution:\n Change DDEG to remove control characters\n \n2. Problem:\n Inquire to ENTITY file option doesn't display GROUP AS A LIST items.\n Resolution:\n Change DDEPRT to display GROUP AS A LIST items\n \nof the Veteran's Data Integration & Federation (VDIF) Qualifying\n \nTest Sites:\n-----------\nTBD\n \n \nSoftware and Documentation Retrieval Instructions:\n-------------------------------------------------- \nSoftware is being released as a KIDS Build on Forum.\n \nPatient Query (QPQ) endeavor.\n \nPatch Installation:\n \nPre-Installation Instructions:\n------------------------------\nThis patch can be queued for installation. TaskMan does not have to be\nstopped, Health Level 7 (HL7) filers do not need to be stopped, and\nusers may be on the system. The patch should be installed during\nnon-peak hours to minimize potential for disruption to users. This\npatch should take less than 1 minute to install.\n \n \n \nInstallation Instructions:\n--------------------------\n1. Choose the MailMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n \n following options. When prompted for the INSTALL NAME enter\n DI*22.2*17.\n a. Print Transport Global - This option lets you print the contents\n of a Transport Global that is currently loaded in the ^XTMP\n global.\n b. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as functions.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\nPatch Components:\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n d. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option\n and when prompted for the INSTALL NAME, enter DI*22.2*17.\n \n5. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n-----------------\n Install? NO//' respond NO.\n \n6. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//" respond NO.\n \n7. If prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//" respond NO. \n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0//" respond 0.\n \n\n
\nPlease see the description on Forum\n\n
\nBackup of DI*22.2*19 on May 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the description on Forum\n\n
\nPlease see Patch Description on Forum\n\n
\nPlease see Patch Description on Forum\n\n
\nPatch DI*22.2*3 will repair VA FileMan 22.2 defects.\n\n
\nPlease see Patch Description on Forum\n\n
\nPlease see Patch Description on Forum\n\n
\nPlease see Patch Description on Forum.\n\n
\nBackup of DI*22.2*25 on Oct 16, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see Patch Description on Forum.\n\n
\nPlease see Patch Description on Forum.\n\n
\nPlease see Patch Description on Forum.\n\n
\nPatch DI*22.2*29 adds additional security constraints to the Audit Purge \noptions. It restricts access to privileged users with DUZ(0) of "@".\n\n
\nPatch DI*22.2*4 will repair VA FileMan 22.2 defects.\n\n
\nExtensible Data Types and Meta Data Dictionary enhancements\n\n
\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nCorrections for three defects in VA FileMan 22.2.\n\n
\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSeven routines with corrections to five defects in VA FileMan 22.2\n\n
\nPatch DI*22.2*10 repairs the following defects:\nPatch Components:\n Modified DIEQ and added DO to kill statement at line Q\n \n 4. Ticket R13102022FY17\n Problem:\n --------\n Need API to repoint a deleted value in a record, similar to what happens\n when a pointer field value is deleted.\n \n Resolution:\n ----------\n----------------- \n Modified DITP and added tag EN(file, list) where file=file number,\n list= array containing list of entries to be repointed(Passed by Reference)\n \n 5. Ticket R14175506FY17\n Problem:\n --------\n New options that were for adding new data types and released as part of\n patch DI*22.2*2 had no parent menu. These option were not meant for\n general distribution. The options are: DI DATA TYPE OPTIONS,\n DI DATA TYPE FILE, DI DATA TYPE METHOD FILE, and\n Files & Fields Associated:\n DI DATA TYPE PROPERTY FILE.\n \n Resolution:\n ----------\n All four options will be deleted from the OPTION file and added to the\n hard coded options in the DII routine. Modified DII1 and DIFMEDT1\n routines.\n\n 6. No ticket\n Problem:\n New/Modified/\n --------\n Developer needs API to check what entries points to a particular record\n in a file.\n\n Resolution:\n ----------\n CHKPT^DIUTL(file, ien, message).\n ;INPUT: DIFILE=file number, DA=ien of record, DIMSG=closed global root\n or local array\n ;OUTPUT: DIMSG(0)=line count, DISMG(#)="Entry ien in FILE (file #)\nFile Name (#) Field Name (#) Deleted\n refers to record DA" \n\n Blood Bank Clearance:\n ---------------------\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch DI*22.2*10 contains\n changes to a package referenced in ProPath standard titled: BBM Team Review\n of VistA Patches. This patch does not alter or modify any VistA Blood Bank\n software design safeguards or safety critical elements functions.\n\n RISK ANALYSIS: Changes made by patch DI*22.2*10 have no effect on Blood Bank\n------------- -------------- -------------\n software functionality, therefore RISK is none.\n\n\nTest Sites:\n-----------\n Charleston\n West Palm Beach\n \n \nSoftware and Documentation Retrieval Instructions:\n N/A\n-------------------------------------------------- \nDocumentation describing the new api, EN^DITP, can be found in the\nFM 22.2 Developer's Guide\n \nCurrent documentation is on the VA Software Documentation Library \nat: http://www.domain.ext/vdl/ \n \nTitle File Name SFTP Mode\n-----------------------------------------------------------------\nFM 22.2 Developer's Guide fm22_2dg.PDF Binary\n \nFM 22.2 User Manual fm22_2um1.PDF Binary\nFM 22.2 Advanced User Manual fm22_2um2.PDF Binary\nFM 22.2 Technical Manual fm22_2tm.PDF Binary\n \n \nBackout and Rollback Procedure:\n-------------------------------\nThis patch only consists of routines. During the VistA Installation\nProcedure of the KIDS build, the installer should back up the modified routines by the use of the 'Backup a Transport Global' action\n(step 3b in the Installations Instructions below).\nForms Associated:\n \nIf rollback/backout is required, the installer can restore the routines\nusing the MailMan message that were saved prior to installing the\npatch.\n \n \nPatch Installation:\n \n \nPre-Installation Instructions:\n \n------------------------------\nThis patch can be queued for installation. TaskMan does not have to be \nstopped, HL7 filers do not need to be stopped, and users may be on the \nsystem. The patch should be installed during non-peak hours to minimize\npotential for disruption to users. This patch should take less than 1 \nminute to install.\n \n \nInstallation Instructions:\n--------------------------\n 1. DIWP only supports strings up to 999 characters\nForm Name File # New/Modified/Deleted\n1. Choose the MailMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter DI*22.2*10.\n a. Print Transport Global - This option lets you print the contents\n of a Transport Global that is currently loaded in the ^XTMP\n global.\n--------- ------ --------------------\n b. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as functions.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n d. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n N/A\n \n4. From the Installation Menu, select the Install Package(s) option and\n When prompted for the INSTALL NAME, enter DI*22.2*10.\n \n5. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' respond NO.\n \n7. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//" respond NO.\n \n \n8. If prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//" respond NO. \n \n9. If prompted "Delay Install (Minutes): (0 - 60): 0//" respond 0.\n \n \nPost-Installation Instructions:\n-------------------------------\nnone\n \nMail Groups Associated:\n \n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\n N/A \n \n 2. NUMDATE fix in patch 7 was not added to DINIT\nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \n DI DATA TYPE OPTIONS Menu Deleted\n DI DATA TYPE FILE Run Routine Deleted\n DI DATA TYPE METHOD FILE Run Routine Deleted\n DI DATA TYPE PROPERTY FILE Run Routine Deleted\n \n \n 3. The variable DO is not killed after call to DIE\nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \n N/A\n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\n 4. New api EN^DITP for repointing deleted records\n N/A\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------------- --------------------\n N/A\n \nAdditional Information:\n-----------------------\n 5. New options for editing Data Types in patch 2 have no parent\n N/A\n \nNew Service Requests (NSRs):\n---------------------------- \n N/A\n \nPatient Safety Issues (PSIs):\n-----------------------------\n N/A\n \n 6. New API CHKPT^DIUTL(file, ien, message)\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n 1. Ticket I13413576FY17\n Problem:\n --------\n Word Processing cannot parse a string greater than 999 and the FM 22.2\n allows strings up to 4K characters.\n \n Resolution:\n ----------\n\n Modified DIWP and changed 999 to 9999\n \n 2. Ticket I15917948FY17\n Problem:\n --------\n Patch DI*22.2*7 fixed the NUMDATE function in the FUNCTION file #.5,\n but DINIT restored the old function.\n \n Resolution:\n ----------\n \n Modified DINIT4 and added fix to NUMDATE\n \n 3. Ticket I16009474FY17\n Problem:\n --------\n The variable DO is not killed after a call to DIE if a user asked for\n help in a multiple Date field.\n\n Resolution:\n ----------\n\n
\nThis Build file entry contains the Options, Security Keys, and Remote\nProcedures used by VA FILEMAN 22.2.\n\n
\nSee National Patch Module (NPM) for a description of the changes included\nin this patch.\n\n
\nIncrease felony theft threshold from $100 to $1000.\n\n
\n This patch changes the Daily Operations Journal [ESP DAILY OPERATIONS \n JOURNAL]. In a NOIS message IND-1098-40335 it was reported that a blank\n page is always sent to the printer at the start of the report. The\n routine ESPJOU has been modified to repair this defect.\n\n
\nThis patch correct the problem that was created by patch ES*1*22. The\nproblem that occurred was that the user was unable to press the "^" key\nto exit the Print Conversion Report. This patch also corrected a problem\nthat was reported by the test where if the report was sent to a slave\nprinter the screen would remain hung.\nThe related NOIS to this patch is NYN-0898-11176.\n\n
\nThe purpose of this patch is to correct the problem where the process\nseems to hang after a Quick Name Check [ESP QUICK NAME] report is sent\nto a slave printer. Though the process is not truly hung, the slave printer,\nbecause it is not closed properly, continues to control the process after\nthe report is finished. This patch properly closes the output device and\nreturns control to the main routine upon the report having completed.\n\n
\nTest build to make the Police Journal multidivsional for the NDBI software\n\n
\nOpen evidence report printing out of sequence\n\n
\nProblem with external to internal date conversion.\n\n
\nThis patch will correct the problem of allowing incorrect journal dates \nto be entered.\n\n
\nThis patch corrects 4 input templates related to the Uniform Offense\nReport. See NPM for complete description.\n\n
\nWhen going back and printing old journal entries and offense reports the \nofficers badges/rank are not correct for the timeframe. Any officer that \nhas had a badge/rank change is causing the old reports to reflect their \ncurrent badge/rank and not the badge/rank at time of journal/offense data \nentry. This has raised concerns about legal issues for court/fraud \npurposes.\n\n
\nTIME entry default not correct.\n\n
\nSites are getting an undefined error when generating ESP FACILITY REPORTS.\n\n
\nThis build will prevent the ability to delete open status Uniform Offense\nReports.\n\n
\nSystem skipping journal entries (time default)\n\n
\nPolice and Security Key violation + indentifying officers with same name\n\n
\nModify software to include 1st letter of first name and middle name\nof officer of officer on the Daily Operations Journal, Case Assignment \nRegister and Offense Match Report.\n \nAlso, remove the on screen initial page feeds from FOLLOW-UP ENTRY \nADD/EDIT, PRINT ANY FOLLOW UP NOTE, PRINT ANY OFFENSE REPORT and REVIEW \nCOMPLETED OFFENSE REPORT.\n\n
\n1. Modify Violation Number field (.05) in file #914 from 6 to 7 digits.\n \n2. Conflict between Category and Status under Complainant portion of\n Offense Report. \n \n3. ERROR - <UNDEFINED>S+14^DIC3\n\n
\nMODIFY ESPQNC TO QUIT WHEN AN ENTRY CONTAINS A "^" CHARACTER. PREVENTING \nAN UNDEFINED ERROR FROM OCCURING. \n\n
\nThis patch corrects several problems, mostly with the Daily Operations\nJournal, reported via NOIS since patch 17. See NPM for complete\ndescription.\n\n
\nES*1.0*20\nY2K Revisions - age calculation.\n\n
\nES*1*23\nFix TIME2 variable in ESPAJE.\n\n
\nClean up NOIS issues.\n\n
\nPrevent negative time display for journal entry.\n\n
\nPatch to patch ES*1*21.\n\n
\nThis package supports the role of the VA police officer.\nFunctions include Offense Reports, Violations, Quick Name Check,\nWants & Warrants, and Vehicle Registration.\n\n
\nSee Description in NPM.\n\n
\nThis patch does a rollup of data from local sites into a mailmessage,\nand sends it to the national database.\n\n
\nThis patch creates an option that can be used to transmit data from\none month to the national database. The name of the option is Manual\nRollup.\n\n
\nThis patch is an enhancement project that will make major changes to the \nsame way in existing reports. Each has a suffix of Non-CSS to \ndistinguish it from the original ten Customer Service Standards. The \nCustomer Service Standard field in the CONTACT ISSUE CODE file (#745.2) \nhas been populated and is being exported with the patch.\n \nThis patch changes the input transform of the Division field (#37) of the \nCONSUMER CONTACT file (#745.1). Currently, only integrated sites \nreceived a prompt for Division, and the choices were limited to those \nMedical Centers making up the integrate group. Now, all sites will get \nthe prompt and choices are amongst those MEDICAL CENTER DIVISION file \nCONTACT ISSUE CODE file (#745.2). Existing codes will be inactivated, \n(#40.8) entries which point to the INSTITUTION file (#4). The Division \nfield remains a pointer to the INSTITUTION file (#4).\n \nA new field, Internal Appeal (#43) has been added to the CONSUMER CONTACT \nfile (#745.1). This field will store whether or not a Report of Contact \nwill go through the Internal Appeal process. The Ad Hoc Report has been \nupdated to include this new field. Internal Appeal will take the place \nof the Refer to SEAT field.\n \nThe user will no longer be prompted for the Level of Satisfaction field \nand new codes will be exported, resulting in a smaller list of active \n(#36 of the CONSUMER CONTACT file (#745.1)).\n \nThe second problem was that the division field pointed to the INSTITUTION\nfile (#4) and only legacy sites were to be available as choices. With\nthis patch any entry in the site's MEDICAL CENTER DIVISION file (#40.8)\nthat points to the INSTITUTION file will be available. Both integrated and\nnon-integrated sites will be able to enter the division. \n \nThis patch will also correct two problems with the Patient Representative\nRoll-up. \ncodes. Only these nationally exported codes will be in use.\n \nThe first problem dealt with the fact that once a record was transmitted,\nit would be evaluated for re-transmission only when it was closed. Also,\nthe roll-up did not take into account the fact that records can be\nre-opened and edited after closing. Any record that was re-opened was not\nbeing evaluated for re-transmission. With this patch any record edited\nwill be evaluated for transmission regardless of whether or not it was\npreviously transmitted, independent of record status.\n \nThis patch will export seven new entires in the CUSTOME SERVICE STANDARD \nfile (#745.6). These codes will be added in order to bring the Customer \nService Standards field better match the Customer Satisfaction survey. \nThese codes are not Customer Service Standards, but can be tracked in the \n\n
\nA problem was discovered with the Service/Discipline Issue Totals [QAC \nSERV/DISC ISSUE TOT] report - it would not report results when just one \nDivision was selected. The same code is used for the Discipline Issue \nTotals [QAC DISC ISSUE TOT] report, and the fix made with this patch \naddresses both reports.\n\n
\nSites are seeing Contact Numbers that do not follow the\nproper format. The sites are not able to enter new contact\nnumbers because of the incorrect contact numbers.\nThis patch will correct the bad contact numbers when the\npost install routine is run.\n\n
\nThis patch contains the VistA objects to run PATS (Patient Advocate\nTracking System), the application that replaces the legacy Patient\nRepresentative system.\n \nIt includes both objects used to retrieve VistA data while the PATS\napplication is running, and objects used to migrate the legacy data from\nthe FileMan files to the new PATS Oracle tables on a central server.\n\n
\nAssociated patches: (v)QAC*2*19 <<= must be installed BEFORE \nThe Patient Advocate Tracking System (PATS) has two remote procedure calls\noption will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your system. \nFrom the KIDS menu, you can use the following options:\n \n Verify Checksums in Transport Global (optional)\n Print Transport Global (optional)\n Compare Transport Global to Current System (optional)\n Backup a Transport Global (optional)\n \n(RPC) that return data from the NEW PERSON file. The RPC names are QACV\n 5. From the KIDS menu, under the 'Installation' menu, use the following\noption to install the patch:\n \n Install Package(s) QAC*2.0*21\n .\n .\n .\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nKEY HOLDERS VLH and QACV PERSON LOOKUP VLH. Both RPCs execute the same\n \n \nDOCUMENTATION:\n================= \nDocuments for the PATS system can be obtained by using FTP from the\nappropriate Customer Service directory:\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== ==================\n download.vista.domain.ext\ncode in routine QACVEMPX. The RPCs return NAME, TITLE and MAIL CODE for\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext \n Salt Lake City ftp.fo-slc.domain.ext\n \n Document can also be downloaded from the VistA Documentation Library\n(VDL) Web page:\n \n <http://www.domain.ext/vdl/section.asp?secid=4>\n \n \nselected employees.\n ROUTINE SUMMARY - CHECK^XTSUMBLD results\n ========================================\n The second line of the routines will look like:\n \n ;;2.0;Patient Representative;**19,21**;07/25/1995\n \n Routine Name Before Patch After Patch Patch list\n ========== ========= ======== =======\n QACVEMPX 6135557 9113636 **19,21**\n \n \n \nRoutine Information:\n====================\n \n \nThe second line of each of these routines now looks like:\n ;;2.0;Patient Representative;**[Patch List]**;07/25/1995;Build 4\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\nProblem #1\n \nRoutine Name: QACVEMPX\n Before: B18632980 After: B39562803 **19,21**\n \nRoutine list of preceding patches: 19\n----------\nCurrently, if the TITLE or MAIL CODE contain an ampersand character (&), \nthe PATS java code interprets this as a reserved xml character and fails.\n`QAC*2*21'\nThis is experienced in 4 places in PATS.\n \n1. Adding a New Report of Contact (ROC), Cover Sheet tab, the system\nshould display a drop-down list of Information Takers. Without the patch,\nthe drop-down list of Info Takers is not present.\n \n2. Edit a ROC, search by Information Taker option, should display a \ndrop-down list of Information Takers. Without the patch, the drop-down\nlist of Info Takers is not present.\n \n \n3. Edit a ROC, Resolution tab, adding a new Issue Code, when user tries to\nlook up an Employee Involved. Without the patch, the users receive the \nerror: "A problem was encountered while attempting to communicate with \nVistA. This problem appears to be related with VistALink. Try again. If\nthis problem persists contact the support desk for further assistance."\n \n4. Edit a ROC, Notification tab, when user tries to look up an Employee \nto send a notification. Without the patch, the users receive the \nerror: "A problem was encountered while attempting to communicate with \nVistA. This problem appears to be related with VistALink. Try again. If\nSubject: Employee Lookup Bugs in PATS\nthis problem persists contact the support desk for further assistance."\n \nThe fix is to use the Kernel routine $$SYMENC^MXMLUTL in routine QACVEMPX\nto replace reserved xml symbols in the TITLE and MAIL CODE output with\ntheir coded values.\n \nProblem #2\n----------\nThe NEW PERSON file may contain last names standardized under an old \nformat that removed all punctuation except for hyphens, and last names \n \nstandardized under a newer format that also leaves spaces and apostrophes \nin the last name. Thus you may find names like O'BRIEN as well as OBRIEN.\n \nWhen a user enters O'Brien as a lookup value, PATS was only using the old \nname standardization, so was only finding matches to the last name \nOBRIEN, but was not finding O'BRIEN.\n \nThis occurs in two different places in PATS.\n \n1. Edit a ROC, Resolution tab, adding a new Issue Code, when user tries to\nCategory: ROUTINE\nlook up an Employee Involved.\n \n2. Edit a ROC, Notification tab, when user tries to look up an Employee \nto send a notification.\n \nAfter the patch is installed, if a user enters a last name containing\neither an apostrophe or a space, PATS will look for matches to the name\nboth with and without the apostrophe or space. Thus, if a user enters\nO'Brien, PATS will find names matching both O'BRIEN and OBRIEN, if there\nare any.\n \n \nASSOCIATED NOIS:\n ===============\n Remedy: HD0000000200638\n Remedy: HD0000000202881\n Remedy: HD0000000204329\n Remedy: HD0000000207038\n Remedy: HD0000000207041\n \n ASSOCIATED E3R:\nDescription:\n ==============\n n/a\n \n TEST SITES:\n ===========\nPORTLAND (OR) VAMC - 648\nPHOENIX VAMC - 644\nLONG BEACH,CA VAMC - 600\nCHEYENNE VAMC - 442\nUPSTATE NEW YORK HCS- 528\n===========\nCENTRAL TEXAS HCS - 674\n \n \n INSTALLATION INSTRUCTIONS:\n ==========================\n >>> Users may remain on the system\n >>> TaskMan does NOT need to be stopped\n >>> Time to install patch is less than 2 minutes\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n\n
\nThis patch will retire the Patient Representative (QAC) version 2.0 \npackage. All national components associated with the Patient\nRepresentative and Veterans Health Information Systems and Technology \nArchitecture (VistA) Patient Advocate Tracking System (PATS) packages\nwill be removed. Every site may not have all the listed components.\n \nAll scheduled Patient Representative options must be unscheduled before \ninstalling this patch.\n\n
\nThis package supports the work of the Patient Representative by\ncollecting data on patient and non-patient contacts.\n\n
\nThis patch changes the namespace and global reference from the Clinical Lexicon\nUtility v 1.0 (GMPT) to the Lexicon Utility v 2.0 (LEX).\n\n
\nBuild can be found on the National Patch Module under Patch GMPL*2.0*18.\n\n
\nBuild can be found on the National Patch Module under Patch GMPL*2.0*17\n\n
\nBuild can be found on the National Patch Module under Patch GMPL*2.0*19.\n\n
\nThis patch will correct the Problem in LM of Problem List comments not being \ndisplayed for all Divisions.\n\nBuild can be found on the National Patch Module under Patch GMPL*2.0*21.\n\n
\nPatient Problem description in Health Summary does not match the description\nin Problem List. This patch will modify routine GMPLHS to include the \nfield (1.01), "POINTER TO EXPRESSIONS FILE (#757.01)" in the API to aid HS \nin correcting this discrepancy. \n\nBuild can be found on the National Patch Module under Patch GMPL*2.0*22.\n\n
\nSee the Build description in the National Patch module under patch \nGMPL*2*23.\n\n
\nThis patch was developed to make the Clinician more aware of the ICD \ncode of 799.9 being assigned to patient problems when no match is found in \nLexicon.\n\nBuild can be found on the National Patch Module under Patch GMPL*2.0*20.\n\n
\nSee the National Patch Module for description of patch GMPL*2*25.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMPL*2*26.\n\n
\nSee the National Patch Module for a complete list of enhancements included\nin this patch.\n\n
\nSee Patch Module for GMP*2*9\n\n
\nSee description in the Nationl Patch module.\n\n
\nThis patch will correct the problem of invalid characters (~) appearing \nin the DIAGNOSIS (pointer to the ICD DIAGNOSIS file #80) in the PROBLEM \nFILE (9000011). This modification will also add a check for the ICD code \nnot being found. (-1 being returned instead of pointer from ICD #80 file \nsearch)\n \nIt will also add audit trail processing for changes to Problem comments.\n\n
\nThis Patch addresses where users are unable to modify the \ncurrent Problem Category Lists to make it assignable to users.\n\n
\nThis patch contains a fix to an invalid values being set in file 9000011.\n\n
\nThis patch contains a fix to an invalid values being set in file 9000011.\n\n
\nThis patch corrects the printing of inaccurate division information in the\nPatient Problem List report printed in the Problems Tab of CPRS GUI.\n\n
\nFIX FOR UNDEFINED VARIABLE ERROR IN GMPLUTL1\n\n
\nThe description of this patch may be found in the National Patch Module \nunder GMPL*2.0*43.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMPL*2.0*36.\n\n
\nThis build makes the ICD-10 changes to Problem List for the Clinical\nReminders Index.\n\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMPL*2.0*42.\n\n
\nRESOLVES <UNDEFINED>DT+37^GMPLHIST SERVER ERROR\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMPL*2.0*47.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMPL*2.0*45.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMPL*2.0*40.\n\n
\nThis patch will address a problem with an improperly altered SNOMED \nnarrative causing the routine GMPLSAVE to error out and fail to save a\nnew diagnosis to the Problem List from PCE and the PCE is lost.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMPL*2.0*49.\n\n
\nSee patch description on Forum for installation instructions.\n\n
\nThis patch adds support for CPRS.\n\n
\nCORRECT URL IN OR PROBLEM NTRT BULLETIN\n\n
\nBackup of PCE STANDARDIZATION 1.0, PX*1.0*211, PXRM*2.0*42, GMT\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch supports PCE standardization.\n \nFor detailed information and installation instructions, please see the PCE\nStandardization 1.0 Installation Guide.\n\n\nTo take full advantage of the PCE standardization work, changes to VistA\napplications that use PCE data are required. These applications include\nClinical Reminders, Health Summary, Problem List, and Order Entry/Results\nReporting. To make it easier for sites, the builds for PCE (PX*1.0*211),\nClinical Reminders (PXRM*2.0*42), Health Summary (GMTS*2.7*122), Problem List\n(GMPL*2.0*53), and Order Entry/Results Reporting (OR*3.0*501) are being\ndistributed in a multi-package build named PCE STANDARDIZATION 1.0.\n\n
\nThe patch addresses one (1) request: \n \n1. Update the text in the MESSAGE and DESCRIPTION fields for two (2) \n BULLETIN FILE (#3.6) entries: OR PROBLEM NTRT BULLETIN and GMPL\n PROBLEM NTRT BULLETIN. Also, enable the GMPL PROBLEM NTRT BULLETIN to\n be send to FORUM to the Problem List NTRT MAIL GROUP.\n\n
\nSee the National Patch Module for the description of patch GMRA*2*13.\n\n
\nDescription of this Build can be found on National Patch Module under Patch \nGMPL*2.0*14.\n\n
\nDescription of this Build can be found on National Patch Module under Patch \nGMPL*2.0*15.\n\n
\nDescription of this Build can be found on National Patch Module under Patch \nGMPL*2.0*12.\n\n
\nDescription of the build can be found on the National Patch Module under Patch \nGMPL*2.0*16.\n\n
\nThis package allows for entry and tracking of a patient's problems\nwithin DHCP. Other components of the clinical record may be linked\nto a problem, such as orders, procedures, and progress notes.\n\n
\nThis patch corrects the date on the Referral report and the line\ncount on the RCH address labels.\n\n
\nThis patch contains changes to the option Summary Open Cases -\nWorkers Patient Registry [SOWKPS]. It will move the column containing the\npatient ID from column 25 to column 32, allowing more space for the\npatient's name on the report.\n\n
\nThis patch will delete the obsolete NURSING HOME PROFILE file (#658). It\nwas never used in Social Work V. 3.0. A decision was made to delete\nthis file because it contains references to the USER file (#3) which is\nslated for removal. In addition to deleting the file, associated templates\nare also deleted. This includes the input templates SWNHADD and SWNHEDIT,\nsort template SWNH PRINT, and print template SWNH PRINT. All locally\ncreated templates for this file will also be deleted.\n\n
\n1. This patch will delete the CNHC COST CONTROL file (#657). It\n SWASIH\n SWNRC \n \n \n2. This patch removes the Automatic Reporting System [SOWKIPD] menu and\nthe options included within it. This includes the options Compile AMIS\nData [SOWKARS], Print Patient and AMIS Segments Data (132 COLUMNS)\n[SOWKARSP], and Transmit AMIS Data Via MailMan [SOWKARSE]. It will also\ndelete associated routines.\nwas never used in Social Work V. 3.0. Associate templates are also\nremoved. They are as follows:\n \n INPUT TEMPLATE(S) PRINT TEMPLATE(S) SORT TEMPLATE\n ================= ===================== =======================\n SOWKASIH SOWKCNHC COST BREAKDOWN SOWKCNHC COST BREAKDOWN\n SOWKCNHEDT\n SOWKRC\n\n
\nWhen a file lookup is performed a $TEST check after the call, no longer\nfunctions properly. The solution for this is to remove the $TEST checks.\n\n
\nThis patch inserts a line between "FO will stand for FOOD" and\n"HE will stand for HEALTH" when using the Print SWS Agency [SOWKBHPR]\noption.\n\n
\nSee Patch SOW*3*62 in the National Patch Module for description of the\nBuild.\n\n
\nThe Assessment Profile [SOWKDBP] option will reflect the New Race and \nEthnicity Standards enhancements. The modified routine will \ndisplay/print, in the demographic section, the Veteran's Ethnicity in\nsequence 9 and the Veteran's Race(s) in sequence 10. The Veteran's \nReligious preference will shifted to sequence 11.\n\n
\nThe Scheduling V. 5.3 package is moving the patient appointment information\nMonitor V [SOWKQAMONV] option, with the new APIs. \nstored in the APPOINTMENT sub-file (#2.98) of the PATIENT file (#2) and the\nAPPOINTMENT sub-file (#44.001) of the HOSPITAL LOCATION file (#44) to the\nGovernment Off-the-Shelf (GOTS) database. Eventually, these sub-files will\nbe deleted from the Scheduling files. As part of the Scheduling Replacement\nProject, Scheduling V. 5.3 package is providing a series of Application\nProgrammer Interface calls (APIs) that will be used to get the patient\nappointment information from the new GOTS database. This patch replaces all\ndirect references to the patient appointment information in the Management\n\n
\nThis patch will retire the Social Work package by removing all associated \ncomponents.\n\n
\nThis build contains modified routines (SOWKND, SOWKOPT, SOWKPREI) for\npatch SOW*3*49. Changes were required to eliminate parts of the\npre-initialization and post-initialization conversion which referenced the\nPERSON file (16). The PERSON file (16), along with the USER file (3) and\nPROVIDER file (6), will be eliminated in the future and the previous\nconversion process for Social Work will be rendered inoperable.\n\n
\nThis build merges the Event Capture data entry and report menus with the\nSocial Work menus.\n\n
\nThis KIDS build contains the routine SOWKOPEN, which has been modified\nfor patch SOW*3.0*52, to resolve a problem causing corruption on the zero\nnodes of entries in the SOCIAL WORK PATIENT file (655).\n\n
\nThis patch updates the RCS 10-0173 (80 COLUMNS) Report to only report\ninformation as it pertains to the open date to the home and close date to\nthe home. After the patch is installed the open and close dates to the\nprogram will will no longer be used to determine any of the information\nreported on the RCS 10-0173. The report will now display an accurate\nnumber for veterans remaining at the end of the quarter as well as the\ntotal bed days of care regardless of case openings, case closings,\nprograms opening, and program closing.\n\n
\n This patch addresses NOIS CLE-0597-42170 regarding the request made by\n Mental Health VACO (FORUM msg #1107156) to set up the CDR Accounts.\n Three of the CDC Codes, (2312.00, 2314.00 and 2315.00) were previously\n marked for deletion by patch SOW*3*36 in December of 1994.\n\n
\n This patch makes the following changes to address Year 2000 compliance \n \n \n Routine: SOWKDBPN \n Line Tag: SOWKDBPN+17 \n Exception : The statement "OPEN DATE:" and "CLOSE DATE:" was marked \n because of the word DATE. \n Resolution: (Later determined no action necessary) \n \n Routine: SOWKDBSR \n Line Tag: SOWKDBSR+7 \n Line Tag: SOWKDBSR+8 \n Routine: SOWKARS \n Exception : The variable SOWKNEW is flagged as a possible variable that \n may contain a date. \n Resolution: (Later determined no action necessary) \n \n Routine: SOWKDSC \n Line Tag: SOWKDSC+2 \n Line Tag: SOWKDSC+3 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n Line Tag: SOWKARS+3 \n \n Routine: SOWKHR \n Line Tag: SOWKHR+3 \n Exception : The code %DT="" does not have any parameter setting. \n Resolution: (Later determined no action necessary) \n \n Routine: SOWKHR1 \n Line Tag: SOWKHR1+36 \n Exception : The results of D DD^%DT will return a FileMan formatted date.\n Resolution: (Later determined no action necessary) \n Line Tag: SOWKARS+4 \n \n Routine: SOWKHRM \n Line Tag: SOWKHRM+5 \n Exception : The code %DT is set to null. No change is needed. \n Resolution: (Later determined no action necessary) \n Line Tag: SOWKHRM+6 \n Exception : Failure to include "P" in %DT parameter string. \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string.\n \n Exception : Failure to include "P" in %DT parameter string \n Routine: SOWKHRM1\n Line Tag: SOWKHRM1+4\n Exception : The variable DAT contains a VA FileMan date. \n Resolution: (Later determined no action necessary)\n \n Routine: SOWKLC \n Line Tag: SOWKLC+3 \n Line Tag: SOWKLC+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKLCD \n Line Tag: SOWKLCD+5 \n Line Tag: SOWKLCD+6 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKPAO \n parameter string. \n Line Tag: SOWKPAO+3 \n Line Tag: SOWKPAO+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKPAOD \n Line Tag: SOWKPAOD+3 \n Line Tag: SOWKPAOD+4 \n Exception : Failure to include "P" in %DT parameter string \n \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKPAOQ \n Line Tag: SOWKPAOQ+3 \n Line Tag: SOWKPAOQ+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKAWB \n Routine: SOWKPLC \n Line Tag: SOWKPLC+3 \n Line Tag: SOWKPLC+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKPNTF \n Line Tag: SOWKPNTF+7 \n Exception : The results of D DD^%DT will return a FileMan formatted date.\n Line Tag: SOWKAWB+3 \n Resolution: (Later determined no action necessary) \n \n Routine: SOWKQAM1 \n Line Tag: SOWKQAM1+3\n Line Tag: SOWKQAM1+4\n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKQAM3 \n issues in the Social Work package. \n Line Tag: SOWKAWB+4 \n Line Tag: SOWKQAM3+3 \n Line Tag: SOWKQAM3+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKQAM4 \n Line Tag: SOWKQAM4+3 \n Line Tag: SOWKQAM4+4 \n Exception : Failure to include "P" in %DT parameter string \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKQAM5 \n Line Tag: SOWKQAM5+3 \n Line Tag: SOWKQAM5+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n Routine: SOWKQAMN \n Line Tag: SOWKQAMN+3 \n Line Tag: SOWKQAMN+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKQAMR \n Line Tag: SOWKQAMR+3 \n Line Tag: SOWKQAMR+4 \n parameter string. \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKQAR2 \n Line Tag: SOWKQAR2+3 \n Line Tag: SOWKQAR2+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n \n Routine: SOWKQAR4 \n Line Tag: SOWKQAR4+2 \n Line Tag: SOWKQAR4+3 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKQARI \n Line Tag: SOWKQARI+3 \n Routine: SOWKAWI \n Line Tag: SOWKQARI+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKRCH \n Line Tag: SOWKRCH+3 \n Line Tag: SOWKRCH+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n Line Tag: SOWKAWI+3 \n parameter string. \n \n Routine: SOWKRCS \n Line Tag: SOWKRCS+2 \n Line Tag: SOWKRCS+3 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKRF \n Line Tag: SOWKAWI+4 \n Line Tag: SOWKRF+3 \n Line Tag: SOWKRF+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKRFD \n Line Tag: SOWKRFD+5 \n Line Tag: SOWKRFD+6 \n Exception : Failure to include "P" in %DT parameter string \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n \n parameter string. \n \n Routine: SOWKAWS \n Line Tag: SOWKAWS+3 \n Line Tag: SOWKAWS+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKAWU \n Routine: SOWKAI \n Line Tag: SOWKAWU+3 \n Line Tag: SOWKAWU+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCLCR \n Line Tag: SOWKCLCR+3 \n Line Tag: SOWKCLCR+4 \n Exception : Failure to include "P" in %DT parameter string \n Line Tag: SOWKAI+3 \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCLEA \n Line Tag: SOWKCLEA+2 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCLIS \n Line Tag: SOWKAI+4 \n Line Tag: SOWKCLIS+3 \n Line Tag: SOWKCLIS+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCLIW \n Line Tag: SOWKCLIW+3 \n Line Tag: SOWKCLIW+4 \n Exception : Failure to include "P" in %DT parameter string \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCLSP \n Line Tag: SOWKCLSP+3 \n Line Tag: SOWKCLSP+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n Routine: SOWKCLSS \n Line Tag: SOWKCLSS+3 \n Line Tag: SOWKCLSS+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCLSW \n Line Tag: SOWKCLSW+3 \n Line Tag: SOWKCLSW+4 \n parameter string. \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n \n Routine: SOWKCP \n Line Tag: SOWKCP+3 \n Line Tag: SOWKCP+4 \n Exception : Failure to include "P" in %DT parameter string \n Resolution: Replaces call to %DT with call that includes "P" in %DT \n parameter string. \n\n
\nThe routine SOWKQAMN contained in patch SOW*3*53 contained erroneous\npatch tracking information on the second line. This patch updates that\nroutine to provide accurate patch tracking information within the routine.\nThe version of SOWKQAMN contained in SOW*3*53 is functionally correct.\n\n
\nThis patch contains a routine, executed as a post installation routine,\nto ensure that the prefix SOW is entered for the SOCIAL WORK entry in the\nPACKAGE file (9.4).\n \nDuring the process the entry SOCIAL WORK PATCH in the PACKAGE file (9.4)\nwill also be updated. The prefix for SOCIAL WORK PATCH will be changed to\nZZSW. It is no longer used.\n\n
\nTHE FILE AND OPTIONS ASSOCIATED WITH THIS PACKAGE WAS DEVELOPED\nAT THE ISC REGION-3, BY STANLEY A. BROWN.\n\n
\nThis is patch LR*5.2*105 which will transport menus, data dictionary\nchanges, load modified routines and edit templates.\n\n
\n \n VSIT*2*1 (Visit Tracking)\n=================\n Routine Name Before Patch After Patch Patch List\nLR138 NA 3411930 138\nLR138P NA 2851115 138\nLR138PO NA 4890675 138\nLRCAPPH 10492287 9623897 1,19,127,136,138\nLRCAPPH1 3477475 7546206 127,136,138\nLRCAPPH2 NA 6972273 138\nLRWU 11418768 10739890 42,138\n=========================================\n PX*1*9 (PCE)\nInstallation Instructions:\nNOTE: SD*5.3*63 patch MUST be installed before this patch WILL install\nsuccessfully.\n \n1. All users may remain on the system.\n2. No options need be placed out of order.\n3. Install patch during non-peak hours.\n4. Laboratory specimens should not be accessioned or verified during\n installation of the patch.\n5. The Auto-Instruments 'LAB' job does not have to be stopped.\n \n6. Installation time of this patch is less than ten minutes.\n7. Journaling requires no special attention.\n \nNOIS List\n===========================\nRefer to SD*5.3*63 patch\n \n===========================\nTest Sites:\nDevelopmental Test Site: Long Beach\nPatch SD*5.3*63 must be installed before the installation LR*5.2*138.\nAlpha Test Sites : Reno, Tucson and Oklahoma City\n \n===========================\nTechnical Information:\nOccasion of Service (OOS)\nAll valid LAB OOS LOCATIONS follow this format:\nEach LAB OOS LOCATION begins with 'LAB DIV'.\nFollowed by the STATION NUMBER. (Field #99 of the INSTITUTION (#4) file)\nFollowed by 'OOS ID'.\nFollowed by the STOP CODE number.\nThe sequence of patch installs for either RA*4.5*8 or LR*5.2*138 is not\n \nList of selectable OOS Stop Codes:\n PULMONARY FUNCTION 104\n X-RAY 105\n EEG 106\n EKG 107\n LABORATORY 108\n NUCLEAR MEDICINE 109\n CARDIOVASCULAR NUCLEAR MED 110\n ONCOLOGICAL NUCLEAR MED 111\nimportant. The RA*4.5*8 and LR*5.2*138 can be installed in reverse order.\n INFECTIOUS DISEASE NUCLEAR MED 112\n RADIONUCLIDE TREATMENT 113\n SING PHOTON EMISS TOMOGRAPHY 114\n ULTRASOUND 115\n HBHC - PHYSICIAN 170\n CLINICAL PHARMACY 160\n BEREAVEMENT COUNSELING 165\n VASCULAR LABORATORY 421\n EMPLOYEE HEALTH 999\n EVOKED POTENTIAL 126\n \n TOPOGRAPHICAL BRAIN MONITORING 127\n PROLONGED VIDEO-EEG MONITORING 128\n MAMMOGRAM 703\n RADIONUCLIDE THERAPY 144\n PHARM/PHYSIO NMP STUDIES 145\n PET 146\n \n \nNo LAB OOS LOCATIONS can have appointments.\nNo patients can be scheduled to LAB OOS LOCATIONS.\nThe Laboratory Information Manager (LIM) should be notified of the patch\nLAB OOS LOCATIONS can not be selected as the ordering locations.\nAll locations are created by the Scheduling API.\nName Length is less than 31 characters.\nLAB OOS LOCATION can not be deleted with FileMan.\n \nExample LAB OOS LOCATION name = LAB DIV 647 OOS ID 108\nWhere 647 = Poplar Bluff, MO\nWhere 108 = Laboratory Stop Code\n===========================================\nThis patch contains two (2) new options which will be added to the LIM\ninstallation schedule and the date/time of the actual LR*5.2*138\nworkload menu [LR LIM/WKLD MENU].\n1) Create Laboratory OOS Locations [LR WKLD LOCATION] provides a software\ncontrolled creation of LAB OOS HOSPITAL LOCATIONS.\n2) Edit ACC Area OOS Location [LR WKLD ACC AREA LOCATION] allows the LIM\nto modify individual accession areas LAB OOS LOCATIONS to adjust NPCDB\nworkload credit.\n \n=============================\nFields included in LR*5.2*138\n \ninstallation.\nWKLD CODE (#64) File\n DSS Feeder Key (#14) field\nACCESSION (#68) File\n LAB OOS LOCATION (#.8) field\nLAB ORDER ENTRY (#69) File\n TEST (#69.03) subfile\n PCE VISIT # (#12) field\nLABORATORY SITE (#69.9) File\n DEFAULT LAB OOS LOCATION (#.8) field\n \nThis is a joint Radiology, PIMS, PCE, VSIT, National Patient Care Database\n \n \nField Notes:\nA new field DEFAULT LAB OOS LOCATION (#.8) has been added to the\nLABORATORY SITE file (#69.9). It is used when ACCESSION AREAS does not\nhave a LAB OOS LOCATION defined.\nA new field LAB OOS LOCATION (#.8) has been added to the ACCESSION (#68)\nfile. This field is used to adjust NPCDB workload reporting.\n* An existing field is renamed, DSS Feeder Key (#14) in the WKLD CODE\n(#64) file. This field was altered by an earlier patch.\n \nSite Preparation notice:\nRoutine Notes:\nThis patch contains three (3) modified routines LRCAPPH, LRCAPPH1, LRWU\nand one (1) new routine LRCAPPH2. These routines control the reporting of\nNPCDB workload data and the screening of hospital OOS locations.\n There are several additional non laboratory routines that will control\nthe user's HOSPITAL LOCATION selections.\n \n==============================\nExample of option use after Post Installation failure\n \nThis patch and LMIP workload reporting rely on the STATION NUMBER (#99) in\nSelect OPTION NAME: LR WKLD LOCATION\n Create Laboratory OOS Locations\n \n List of already defined Laboratory OOS Locations\n \n \n NONE ARE CURRENTLY DEFINED\n \n \n INSTALL PATCH LR*5.2*138\nthe INSTITUTION file (#4) being correctly defined. New OOS HOSPITAL\n \n=================================\nExample of a defined OOS location display\nSelect OPTION NAME: LR WKLD LOCATION\nCreate Laboratory OOS Locations\n \n List of already defined Laboratory OOS Locations\n \n \nLAB DIV 170 OOS ID 108 170 108\nLOCATION names will be based on this field. The user can not control how a\n \nWould you like a detail display ?No// YES\n \nSelect Laboratory OOS Location : LAB DIV 170 OOS ID 108 \n \nNAME: LAB DIV 170 OOS ID 108 TYPE: CLINIC\n INSTITUTION: 170 STATION 170 STOP CODE NUMBER: LABORATORY\n SERVICE: NONE NON-COUNT CLINIC? (Y OR N): NO\n CLINIC MEETS AT THIS FACILITY?: YES INCLUDE ON FILE ROOM LISTS?: NO\n TYPE EXTENSION: CLINIC ASK PROVIDER AT CHECK OUT:\nnew LAB OOS LOCATIONS will be named. The name will be based on the\nYES/REQUIRED\n ASK DIAGNOSIS AT CHECK OUT: NO\n==================================\nExample of attempted duplicate LAB OOS LOCATION entry\n \nSelect Laboratory OOS Location : \n List of already defined Laboratory OOS Locations\n \nLAB DIV 647 OOS ID 108 647 108\n \nINSTITUTION file setup.\nWould you like a detail display ?No// \n \n You may define a new Laboratory OOS Location\n \n \nEnter New Division : POPLAR BLUFF, MO 647\nSelect Stop Code Service : 108 LABORATORY 108\n ONCE DEFINED - IT CAN NOT BE DELETED\n \n \n===============================\n [LAB DIV 647 OOS ID 108] Is this the correct new name ? No// YES\n \n LAB DIV 647 OOS ID 108\n This location is already defined \n=======================================\nExample of creating a non Laboratory OOS location\n List of already defined Laboratory OOS Locations\n \n \nLAB DIV 647 OOS ID 108 647 108\nPurpose of the patch:\nWould you like a detail display ?No// \n You may define a new Laboratory OOS Location\n \n \nEnter New Division : POPLAR BLUFF, MO 647\nSelect Stop Code Service : \n \n 1 PULMONARY FUNCTION 104\n 2 X-RAY 105\n 3 EEG 106\n1. Correct collection of NPCDB laboratory workload.\n 4 EKG 107\n \nCHOOSE 1-4: 1 \n ONCE DEFINED - IT CAN NOT BE DELETED\n \n \n [LAB DIV 647 OOS ID 104] Is this the correct new name ? No// YES\n \nNAME: LAB DIV 647 OOS ID 104 TYPE: CLINIC\n INSTITUTION: POPLAR BLUFF, MO STOP CODE NUMBER: PULMONARY\n(NPCDB) and Laboratory patch. This patch will not successfully install if\n2. Create LAB Occasion of Service (OOS) LOCATIONS for the purpose of PCE\nFUNCTION\n SERVICE: NONE NON-COUNT CLINIC? (Y OR N): NO\n CLINIC MEETS AT THIS FACILITY?: YES INCLUDE ON FILE ROOM LISTS?: NO\n TYPE EXTENSION: CLINIC ASK PROVIDER AT CHECK OUT:\nYES/REQUIRED\n ASK DIAGNOSIS AT CHECK OUT: NO\n \n LAB Location Added\n \n You may define a new Laboratory OOS Location\n reporting.\n \nEnter New Division : \n=====================================\nExample of changing ACCESSION AREA LAB OOS LOCATION\n \nSelect OPTION NAME: LR WKLD ACC AREA LOCATION\n \nSelect Accession Area : GAS \nSelect OOS Location for [GAS] Acc Area : LAB DIV 7000BY OOS ID 108\n Replace ... With LAB DIV 647 Replace \n3. Provide immediate functionality without LIM intervention.\n LAB DIV 647\n 1 LAB DIV 647 OOS ID 108 \n 2 LAB DIV 647 OOS ID 104 \nCHOOSE 1-2: 2 \n DONE\n \nSelect Accession Area : \n=======================================\n=======================================\n \n4. Provide data clean up of previously reported NPCDB workload (PX*1*9).\nExample of the Build Install\n \nSelect OPTION NAME: XPD MAIN Kernel Installation & Distribution System\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: Install Package(s)\nSelect INSTALL NAME: LR*5.2*138 Loaded from Distribution\n10/21/96@12:12:25\n =>LR*5.2*138 3k LINES ;Created on Oct 21, 1996@13:48:57\n5. Provide utilities to manage multi-divisional NPCDB workload.\n \nThis Distribution was loaded on Oct 21, 1996@12:12:25 with header of \nLR*5.2*138 3k LINES ;Created on Oct 21, 1996@13:48:57\nIt consisted of the following Install(s):\nLR*5.2*138\nWill first run the Environment Check Routine, LR138\n Environment Check is Ok ---\n \nInstall Questions for LR*5.2*138\n 64 WKLD CODE (Partial Definition)\n6. Provide capabilities to support non Pathology & Laboratory Medicine\nNote: You already have the 'WKLD CODE' File.\n 68 ACCESSION (Partial Definition)\nNote: You already have the 'ACCESSION' File.\n 69 LAB ORDER ENTRY (Partial Definition)\nNote: You already have the 'LAB ORDER ENTRY' File.\n 69.9 LABORATORY SITE (Partial Definition)\nNote: You already have the 'LABORATORY SITE' File.\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\n services to receive proper NPCDB workload credit.\nDEVICE: HOME// HOME\nLR*5.2*138 \n Install Started for LR*5.2*138 : \n Oct 21, 1996@12:16:32\n Installing Routines: \n Oct 21, 1996@12:16:33\n Running Pre-Install Routine: ^LR138P\n LOCKING THE ^LRO(69,AA) GLOBAL\n \n Pre Install Step Complete\n7. Enhancement of the Laboratory NPCDB reporting capabilities.\n \n Installing Data Dictionaries: \n Oct 21, 1996@12:16:51\n Installing PACKAGE COMPONENTS: \n Installing OPTION\n Oct 21, 1996@12:16:53\n Running Post-Install Routine: ^LR138PO \n Starting Post Install Process\n \nOption [LR WKLD LOCATIONS] was Added to [LR LIM/WKLD] MENU \n \nOption [LR WKLD ACC AREA LOCATIONS] was Added to [LR LIM/WKLD] MENU \n Creating Laboratory OOS Workload Locations\n \nNUMBER: 657 NAME: LAB DIV 600 OOS ID 108\n TYPE: CLINIC INSTITUTION: LONG BEACH, CA\n STOP CODE NUMBER: LABORATORY SERVICE: NONE\n DIVISION: VA MEDICAL CENTER, LONG BEACH\n NON-COUNT CLINIC? (Y OR N): NO CLINIC MEETS AT THIS FACILITY?:\nYES\n INCLUDE ON FILE ROOM LISTS?: NO TYPE EXTENSION: CLINIC\nThis patch will not effect LMIP workload capture or DSS Laboratory\n ASK PROVIDER AT CHECK OUT: YES/REQUIRED\n ASK DIAGNOSIS AT CHECK OUT: NO\n LAB Location Added\n \n Database Upgrade Completed Successfully\n \n DEFAULT LAB OOS LOCATION IS\n \nNUMBER: 657 NAME: LAB DIV 600 OOS ID 108\n TYPE: CLINIC INSTITUTION: LONG BEACH, CA\nthe Scheduling Package SD*5.3*63 patch has not been installed.\nworkload data extraction. There are no CPT code updates contained in this\n STOP CODE NUMBER: LABORATORY SERVICE: NONE\n DIVISION: VA MEDICAL CENTER, LONG BEACH\n NON-COUNT CLINIC? (Y OR N): NO CLINIC MEETS AT THIS FACILITY?:\nYES\n INCLUDE ON FILE ROOM LISTS?: NO TYPE EXTENSION: CLINIC\n ASK PROVIDER AT CHECK OUT: YES/REQUIRED\n ASK DIAGNOSIS AT CHECK OUT: NO\n \n PCE/VSIT ON (#615) field in LABORATORY SITE (#69.9) file\n \npatch.\n \n has been set to BOTH PCE/VSIT AND STOP CODES\n==============================\nProblem:\nScheduling software determines if a particular procedure requires patient\ndiagnosis based on the HOSPITAL LOCATION file setup. The Laboratory was\npassing the ordering location without patient diagnosis. This produced\nNPCDB workload recording errors because of no diagnosis being passed.\n Some packages still use Clinic Stop codes to identify certain kinds of\ndata. The Stop Codes were determined based on the HOSPITAL LOCATION file\n \nsetup. The Stop Code passed by Laboratory to the PCE API was not being\nused.\n============================\nProblem Solution\nNew OOS HOSPITAL LOCATIONS will be created solely for Laboratory NPCDB\nWorkload reporting. These new locations can not be used for appointments\nor as test ordering locations. These special OOS locations will be\nconfigured to not require diagnosis, eliminating the current errors.\n The Scheduling software will use these special hospital (non diagnosis\nrequiring) locations when passing workload to NPCDB. Upon initial install\n Patches should be installed in the following order:\nall workload will be reported as laboratory Stop Code 108 for the Primary\nInstitution as defined by LMIP Workload Collection file (#67.9). Options\nare provided to allow the LIM to create additional OOS Hospital Locations.\nThe naming of the OOS locations is controlled by the a option included in\nthis patch.\n \nNOTE: The LIM can not edit the Hospital Location file directly. They can\nonly do so via a special option. LAB OOS LOCATIONS should not be created\nthrough VA FileMan.\n \n SD*5.3*63 (Scheduling)\n==============================\nWorkload Reporting Logic:\n1. Only collected specimens will be processed by the software.\n2. Only laboratory specimens having a collection type of Immediate \nCollect, Send Patient or Lab Collect will receive phlebotomy Workload\ncredit.\n3. Only those specimens with a HOSPITAL LOCATION type of Clinic, Module or\nOther will be passed to PCE API. This is not dependent on specimen\ncollection type\n4. No new WKLD CODE CPT codes are included in this patch. Those linked\n RA*4.5*8 (Radiology/Nuclear Med)\nLABORATORY TESTS without CPT codes will not be passed to PCE API. Another\nLaboratory patch will fully populate the WKLD CODE file with CPT codes.\n \nNOTE: The DEFAULT LAB OOS LOCATION field is populated during the post\ninstall. This field is used by NPCDB Laboratory workload reporting\nsoftware if a specific ACCESSION AREA does not have a LAB OOS LOCATION\nassigned.\n \n A tasked routine will inspect the LAB ORDER ENTRY (#69) file for\ncollected specimens. When it finds a patient with collected specimen(s)\n LR*5.2*138 (Laboratory ** this patch **)\nthe software will use the above logic steps to determine if the specimen\nmeets criteria. If the specimens meets criteria, the software checks the\nACCESSION AREA where the specimen was accessioned. The accessioned test(s)\ndoes not need to be verified in order to trigger NPCDB or LMIP Phlebotomy\nworkload reporting. If the ACCESSION AREA has a LAB OOS LOCATION defined\nthe API will pass that location. If the ACCESSION AREA does not have a LAB\nOOS LOCATION defined, the DEFAULT LAB OOS LOCATION will be passed.\n \n=======================================\nROUTINE SUMMARY:\n\n
\nThis patch adds two new segments to the HL7 transmissions generated by\n ABBREVIATED NAME: DSP FULL NAME: Display Data\nLREPIPH NEW 5818757 260\nLREPIRP 6008472 5973015 132,157,175,260\nLREPISRV NEW 12552990 260\n \n \nInstallation Instructions:\n==========================\n \n \n NOTE: This KIDS install does not place any options out of service\n This segment will report Clinical Reminders Hepatitis\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO"\n \n The site should answer "NO" to all three questions.\n C Risk Assessment Data.\n Note: You may not receive all three prompts at your site. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n \n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n \n 3. The patch has now been loaded into a Transport global on\n \n your system. You now need to use KIDS to install the\n Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\nThis patch also includes the new LREPI REMINDER LINK file (#69.51).\n \n 4. Users may remain on the system, installation may be done at\n any time.\n \n 5. No options need to be placed out of service.\n \n 6. Installation time is less than 2 minutes during off peak\n hours and less than 5 minutes during peak hours.\n \n 7. Installation of this patch requires no additional memory\n This file points to the REMINDER DEFINITION (#811.9) used by the \n space.\n \n 8. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)' Select the package 'LR*5.2*260'\n and proceed with the install.\n \n 9. The post-init routine, LR260, will perform the three final\n automated functions in the installation. These steps are:\n \n A. Three entries will be added to the LREPI REMINDER\n Emerging Pathogens Initiative (EPI). Entries in the new LREPI REMINDER\n LINK (#69.51) file. These are "VA-NATIONAL EPI DB\n UPDATE", "VA-HEP C RISK ASSESSMENT", and \n "VA-NATIONAL EPI RX EXTRACT".\n B. Three entries will be added to the LAB \n SEARCH/EXTRACT (#69.5) file. These are "HEPATITIS C\n ANTIBODY NEG", "HEPATITIS A ANTIBODY POS", and\n "HEPATITIS B POS". Please refer to the\n LR*5.2*260 TECHNICAL/USERS MANUAL for instructions\n on adding tests to these entries.\n C. The NCH CHOLESTEROL and NCH PAP SMEAR entries will\n LINK file are used to determine which Clinical Reminders will be used to\n be inactivated in the LAB SEARCH/EXTRACT (#69.5)\n file.\n \n You will be notified after each step if any problems were\n encountered.\n \n 10. The post-init routine, LR260, will be automatically deleted\n when the installation has completed.\n \n 12. If any routines were unmapped as part of step 2, they should\n generate data for the Hepatitis C database.\n be returned to the mapped set once the installation has run\n to completion.\n \n 13. LABORATORY SEARCH/EXTRACT PATCH LR*5.2*260 HEPATITIS EMERGING\n PATHOGENS INITIATIVE (EPI) TECHNICAL AND USER GUIDE in\n Portable Document Format (LR_260TUG.PDF) is provided with\n this patch. Please refer to this documentation for details\n and specific instructions. The patch description does not\n include ALL implementation considerations or complete setup\n instructions.\n \n \nThis document is available on the following Office of Information Field\n Offices' ANONYMOUS.SOFTWARE directories.\n \n OI Field Office FTP Address Directory\n ================================================================\n Albany 152.127.1.5 ANONYMOUS.SOFTWARE\n Hines 152.129.1.110 ANONYMOUS.SOFTWARE\n Salt Lake City 152.131.2.1 ANONYMOUS.SOFTWARE\n \n the Emerging Pathogens Initiative (EPI) software, clears fifteen \n The NOIS calls addressed are:\n \n 14. Please do not do this until specifically requested to do so.\n After the patch installation and set up has been completed,\n the data for your site will be validated by the EPI program\n office. At this time you will be asked to add \n XXX@Q-EPI.DOMAIN.EXT to the MEMBERS - REMOTE field (#12) of the\n MAIL GROUP file (#3.8) for the EPI mail group.\n \n VA FileMan 22.0\n \n 1. ALX-0400-71108\n \n Select OPTION: 1 ENTER OR EDIT FILE ENTRIES\n \n \n \n INPUT TO WHAT FILE: MAIL GROUP// \n EDIT WHICH FIELD: ALL// MEMBERS - REMOTE (multiple)\n EDIT WHICH MEMBERS - REMOTE SUB-FIELD: ALL// \n THEN EDIT FIELD: \n \n ALB-0100-52818\n \n Select MAIL GROUP NAME: EPI\n 1 EPI \n 2 EPI-REPORT \n CHOOSE 1-2: 1 EPI\n Select REMOTE MEMBER: S.HL V16 SERVER@DEV// XXX@Q-EPI.DOMAIN.EXT\n Are you adding 'XXX@Q-EPI.DOMAIN.EXT' as a new REMOTE MEMBER (the\n 2ND for this MAIL GROUP)? No// Y\n (Yes)\n Select REMOTE MEMBER: \n BHH-0999-40058\n \n \n Select MAIL GROUP NAME: \n NCH-0599-42202\n WAS-0499-21751\n MRN-0299-40846\n CIN-0199-42742\n ALB-1198-50947\n BRK-1198-10546\n NOIS calls, and eliminates the National Center for Health Promotion\n SUX-0599-40961\n PUG-0399-52619\n MEM-0199-72168\n Several sites have reported receiving a \n SEARCH+3^LREPI4 error during the nightly runs. This\n is due to an incomplete PTF record. The software now\n checks the validity of the reference before attempting\n to access the record.\n 2. LAS-1199-61337\n WPB-1298-30488\n (NCH) data transmissions.\n These NOIS calls report an error in the way the site \n number is obtained. An older method of gathering the\n site number was used. This has been replaced with a\n FileMan reference as allowed in DBIA #10090.\n 3. STC-1098-41570\n The NCH transmissions will be eliminated with the\n release of this patch.\n \n Requesting Site: Washington, DC\n Cincinnati, OH\n \n \n Test Site(s): Cincinnati, OH\n West Palm Beach, FL\n \n Reference NOIS: ALX-0400-71108\n ALB-0100-52818\n BHH-0999-40058\n NCH-0599-42202\n WAS-0499-21751\n MRN-0299-40846\n The new segments are:\n CIN-0199-42742\n ALB-1198-50947\n BRK-1198-10546\n SUX-0599-40961\n PUG-0399-52619\n MEM-0199-72168\n LAS-1199-61337\n WPB-1298-30488\n STC-1098-41570\n \n ABBREVIATED NAME: ZXE FULL NAME: Pharmacy Prescription Order\nThe daily National Center for Health Promotion (NCH) data transmissions\n are no longer necessary and the NCHP program office has requested that\n we terminate the transmissions. This will be done during the post-init\n phase and does not require any user intervention.\n \n This patch to the Laboratory package does not contain any changes to the\n VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled VISTA\n BLOOD BANK SOFTWARE.\n \n \n This segment will report Pharmacy data consisting of\nROUTINE SUMMARY\n ===============\n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;;Sep 27, 1994\n \n CHECK^XTSUMBLD Results\n \n Routine Name Before Patch After Patch Patch List\n the Drug Name, NDC, and Days Supply.\n ------------ ------------ ----------- ----------\n \nLR260 NEW 10238627 260\nLREPI 11741568 14217525 132,175,260\nLREPI1 10215540 10654552 132,157,175,260\nLREPI1A 5536163 5834647 175,260\nLREPI2 5729687 7199135 132,157,175,242,260\nLREPI3 3617464 5462995 132,175,260\nLREPI4 1715994 1903453 132,175,260\nLREPIAK 2866307 3640656 175,260\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\n \n All changes have been reviewed by the VISTA Blood Bank Developer and\n WHITE RIVER JUNCTION, VT\n SAINT LOUIS, MO\n ALBUQUERQUE, NM\n MUSKOGEE, OK\n \n ROUTINE SUMMARY:\n ================\n The following is a list of the routine(s) included in this patch. The\n second line of each of these routine(s) will look like:\n \n found to have no impact on the VISTA BLOOD BANK SOFTWARE control\n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n Routine name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n \n LR264 NONE 2442347 264\n LRCAPPH 11522455 11647574 1,19,127,136,138,153\n 158,263,264\n LRCAPPH1 7745000 11010117 127,136,138,158,263,264\n functions. \n LRCAPPNP 1653480 2930814 263,264\n LRCAPR2 8701428 8898011 88,105,263,264\n LRMISTF1 14019130 13608455 121,128,202,263,264\n \n Installation Instructions:\n ==========================\n \n \nAll users may remain on the system. However Laboratory Users should be\nidle during installation.\n \n \nNo laboratory background jobs need to be stopped. No options need to be\nplaced out of service.\n \nInstallation time of this patch is less than 5 minutes.\n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan\n menu. This option will load the KIDS package in this \n message onto your system.\n RISK ANALYSIS: Changes made by patch LR*5.2*264 have no effect on Blood\n 2. The patch has now been loaded into a Transport global \n on your system. You now need to use KIDS to install \n the Transport global.\n On the KIDS menu, under the 'Installation' menu, use \n the following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 3. Users may remain on the system, but installation \n Bank software functionality, therefore RISK is none.\n should be done at off peak hours.\n 4. No options need to be placed out of service.\n 5. Installation time is less than 5 minutes during off \n peak hours and less than 15 minutes during peak hours.\n 6. Installation of this patch requires no additional \n memory space.\n 7. From the 'Installation Menu' of the KIDS menu, run the \n option\n 'Install Package(s)' Select the package 'LR*5.2*264' \n and proceed with the install.\n \n 8. When prompted 'Want KIDS to INHIBIT LOGONS during the\n install? YES//' respond NO.\n 9. When prompted 'Want to DISABLE scheduled Options, Menu\n Options, and Protocols? YES//' respond NO.\n \nAfter the install has been completed. All users can now resume normal\nactivities.\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*264 does not\n alter or modify any software design safeguards or safety critical element\n functions. \n VISTA BLOOD BANK SOFTWARE V5.2 DEVICE PRODUCT LABELING STATEMENT\n \n POTENTIAL IMPACT ON SITES: This patch contains no changes to files and \n routines identified in Veterans Health Administration (VHA) Directive\n 99-053. The changes that are made have no effect to Blood Bank\n functionality or medical device control functions. There is no adverse\n potential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation\n scenarios to be completed by sites after installing this patch.\n \n=============================\nPatch Description:\n===========================\n \n1) There is a unique set of circumstances that will cause the PCE workload\nupdate background software program (LRCAPPH1) to produce a software error.\nThe error situation is created when an orderable test has no accession\narea assigned and is ordered from an outpatient location. \n When the laboratory accessions the specimen, the appropriate accession\narea is selected. The selected accession area is not updated in the LAB\nORDER ENTRY file (#69). PCE workload data has been credited for that\n \norder/accession. The test is then subsequently Not Performed(NP) and PCE\nworkload has already been credited, the PCE workload update background\nsoftware will error for a lack of accession area definition in the LAB\nORDER ENTRY file. This patch will correct this situation by using the\ndefault DSS Location value instead of attempting to determine the specific\naccession area used to accession the test. This error is only manifested\nunder these sequence of events. If the order/accession is NP before PCE\nworkload is credited, no error will occur.\n \nThe software will remove PCE encounters that do not have CPT workload\n June 10, 1999 \nbecause all of the CPT Codes for the order have been Not Performed (NP).\nOrder Status screen will display the encounter number with appended text\nto explain CPT workload transactions.\n \nExample: XXX indicates the encounter number.\n -CPT CANC indicates at least one of the CPT workload credits have been\nremoved.\n-ENC DEL indicates that all CPT workload has been removed and the\nencounter has been deleted.\n \n \nVisit Number(s): XXX-CPT CANC-ENC DEL;\n \n2) The option Results entry (batch) [LRMISTUF] allows for three methods of\ninput batch data. Patch LR*5.2*263 disabled the third option of 'Just\nPrompt'. Patch LR*5.2*264 restores this functionality.\n \n3) The option Workload Report [LRCAPR1] allows for the reporting of\nquality control in the report. If the QC specimens are accessioned\nautomatically by the nightly background job, there is no ward location\ndefined. The report would not report any of these specimens on the report.\n VISTA Laboratory Package patch LR*5.2*264 contains no changes to software\nThe routine LRCAPR2 corrects this problem.\n \n4) In certain situations, Laboratory was passing to the PCE API incorrect\ndate/time, which resulted in corrupted date/time fields in PCE. This patch\ncorrects this problem. Laboratory will no longer pass time that includes\nseconds to the PCE API. This will reduce the number of visit numbers\ngenerated per order.\n \nNOTE: Scheduling patch SD*5.3*227 will provide the functionality to\ncorrect previous PCE data containing the erroneous date/time values.\n controlled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \n \n Related NOIS: CON-0600-12803 SDC-0700-62722 HVH-0700-11960\n WRJ-0600-12784 SDC-0700-62542 SAG-0700-41748\n NIN-0800-41201 ATG-0700-32318 BUT-0700-21675\n BHS-0800-11092 ATG-0700-32273 NOP-0700-10942\n STL-0800-40946 FAV-0700-72129 ALB-0700-50782\n MAN-0800-10125 REN-0700-62117 FRE-0700-60219\n IND-0600-42277 HAM-0900-22088 BHS-0900-12254\n SAJ-1000-71270 SDC-1000-60114 LEX-1000-40050\n FTL-1000-50009 MAD-0900-42468 PHO-0900-62454\n \n MEM-0900-72282 BHS-0900-12254 HAM-0900-71979\n SHR-0900-71979 MIN-0900-41468 WIN-0900-40871\n LEB-0900-20354 DAY-0900-40304 NJH-0900-20290\n JAC-0900-70076 IOW-0800-42214 FGH-0800-31826\n SJA-0800-31826\n \n \n \n Test site(s): LONG BEACH,CA\n CONNECTICUT HCS\n\n
\nVISTA BLOOD BANK SOFTWARE V5.2 DEVICE PRODUCT LABELING STATEMENT\nfound to have no impact on the VISTA BLOOD BANK SOFTWARE control\nfunctions. \n \n RISK ANALYSIS: Changes made by patch LR*5.2*265 have no effect on Blood\nBank software functionality, therefore RISK is none.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*265 does not\nalter or modify any software design safeguards or safety critical element\nfunctions. \n \n=============================\n POTENTIAL IMPACT ON SITES: This patch contains no changes to files and\nroutines identified in Veterans Health Administration (VHA) Directive\n99-053. The changes that are made have no effect to Blood Bank\nfunctionality or medical device control functions. There is no adverse\npotential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation\nscenarios to be completed by sites after installing this patch.\n \n This patch is informational only. The routines referenced in this patch\n \nare distributed and installed with OERR V3.0 patch OR*3*97.\n \n DESCRIPTION\n \n This project consists of five patches that bring all HL/7 date\nconversions, both to and from VA FileMan format, into compliance with the\ncurrent HL/7 standard. The previous standard for HL/7 dates (V2.2) listed\nthe date in YYYYMMDDHHMMSS format. The degree of precision was listed as\na separate parameter. The new standard format (V2.3) is\n[YYYY[MM[DD[HH[MM[SS]]]]]-zzzz] where the bracketed sections are optional\n June 10, 1999 \ndepending on the existence of the subsequent set. Also, if either the\nseconds or the minutes/seconds combination consist only of zeroes, the\nminutes (if zeroes) and seconds will be omitted. The length of the\ndate/time string specifies the degree of precision. In addition, a ZULU\ntime offset (-zzzz)is also included. This is the number of hours between\nGreenwich Mean Time and the local time where the date/time string was\ncreated.\n \nThese patches are combined into a single build for ease of\n installation at VHA facilities: OR_3_97.KID\n \n \n \nThe build is available at the following locations:\n \n OI Field Office FTP Address Directory\n ================================================================\n Albany 152.127.1.5 ANONYMOUS.SOFTWARE\n Hines 152.129.1.110 ANONYMOUS.SOFTWARE\n Salt Lake City 152.131.2.1 ANONYMOUS.SOFTWARE\n \n VISTA Laboratory Package patch LR*5.2*265 contains no changes to software\nThe NOIS calls addressed are:\n Refer to OR*3*97\n \n Requesting Site: Central Office, Washington, DC\n \n \n Test Site(s): \n Refer to OR*3*97\n \n Reference NOIS: \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \n Refer to OR*3*97\n \nROUTINE SUMMARY\n ===============\n The following Laboratory package routines are distributed and installed\nwith CPRS patch OR*3*97.\n \n The second line of each routine now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;;Sep 27, 1994\n \n \n CHECK^XTSUMBLD Results\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \nLR7OU0 7183809 6871123 121,187,265\n All changes have been reviewed by the VISTA Blood Bank Developer and\n\n
\nVISTA BLOOD BANK SOFTWARE V5.2 DEVICE PRODUCT LABELING STATEMENT\nfound to have no impact on the VISTA BLOOD BANK SOFTWARE control\nfunctions. \n \n RISK ANALYSIS: Changes made by patch LR*5.2*265 have no effect on Blood\nBank software functionality, therefore RISK is none.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*265 does not\nalter or modify any software design safeguards or safety critical element\nfunctions. \n \n=============================\n POTENTIAL IMPACT ON SITES: This patch contains no changes to files and\nroutines identified in Veterans Health Administration (VHA) Directive\n99-053. The changes that are made have no effect to Blood Bank\nfunctionality or medical device control functions. There is no adverse\npotential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation\nscenarios to be completed by sites after installing this patch.\n \n This patch is informational only. The routines referenced in this patch\n \nare distributed and installed with OERR V3.0 patch OR*3*97.\n \n DESCRIPTION\n \n This project consists of five patches that bring all HL/7 date\nconversions, both to and from VA FileMan format, into compliance with the\ncurrent HL/7 standard. The previous standard for HL/7 dates (V2.2) listed\nthe date in YYYYMMDDHHMMSS format. The degree of precision was listed as\na separate parameter. The new standard format (V2.3) is\n[YYYY[MM[DD[HH[MM[SS]]]]]-zzzz] where the bracketed sections are optional\n June 10, 1999 \ndepending on the existence of the subsequent set. Also, if either the\nseconds or the minutes/seconds combination consist only of zeroes, the\nminutes (if zeroes) and seconds will be omitted. The length of the\ndate/time string specifies the degree of precision. In addition, a ZULU\ntime offset (-zzzz)is also included. This is the number of hours between\nGreenwich Mean Time and the local time where the date/time string was\ncreated.\n \nThese patches are combined into a single build for ease of\n installation at VHA facilities: OR_3_97.KID\n \n \n \nThe build is available at the following locations:\n \n OI Field Office FTP Address Directory\n ================================================================\n Albany 152.127.1.5 ANONYMOUS.SOFTWARE\n Hines 152.129.1.110 ANONYMOUS.SOFTWARE\n Salt Lake City 152.131.2.1 ANONYMOUS.SOFTWARE\n \n VISTA Laboratory Package patch LR*5.2*265 contains no changes to software\nThe NOIS calls addressed are:\n Refer to OR*3*97\n \n Requesting Site: Central Office, Washington, DC\n \n \n Test Site(s): \n Refer to OR*3*97\n \n Reference NOIS: \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \n Refer to OR*3*97\n \nROUTINE SUMMARY\n ===============\n The following Laboratory package routines are distributed and installed\nwith CPRS patch OR*3*97.\n \n The second line of each routine now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;;Sep 27, 1994\n \n \n CHECK^XTSUMBLD Results\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \nLR7OU0 7183809 6871123 121,187,265\n All changes have been reviewed by the VISTA Blood Bank Developer and\n\n
\nLR*5.2*261\nJob hangs in LRWLST1\n\n
\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patches LA*5.2*58 and\n RISK ANALYSIS: Changes made by patches LA*5.2*58 and LR*5.2*266 have no\n \nAssociated NOIS\n===============\nMIA-0600-30434\nMWV-0900-21094\n \nTest Sites\n==========\nMartinsburg, West Virginia\n \neffect on Blood Bank software functionality, therefore RISK is none.\n \nROUTINE SUMMARY\n=================\nThe following is a list of routines included in patch LA*5.2*58. The\nsecond line of each routine now looks like:\n \n<tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD Results\n Routine Name Before Patch After Patch Patch List\n \n ------------ ------------ ----------- ------------\n LA7DEDT 3765930 5836716 53,58\n LA7DLOC NEW 553499 58\n LA7DVM 6983644 6949969 53,58\n \n \nThe following is a list of routines included in patch LR*5.2*266. The\nsecond line of each routine now looks like:\n \n<tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n**NOTE**\n CHECK^XTSUMBLD Results\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR266 NEW 1529899 266\n LRMIUT 3673249 3951633 254,266\n LRVER3A 10780812 10508599 1,5,42,100,121\n 153,190,221,254,\n 263,266\n \n \n \nThe documentation and distribution files for patches LA*5.2*58 and\nLR*5.2*266 may be obtained using FTP from the appropriate National VistA\nSupport directory:\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== ==========\n HINES 152.129.1.110 [ANONYMOUS.SOFTWARE]\n SALT LAKE CITY 152.131.2.1 [ANONYMOUS.SOFTWARE]\n ALBANY 152.127.1.5 [ANONYMOUS.SOFTWARE]\n \nPatches LA*5.2*58 and LR*5.2*266 are being released in a single\nFile names are:\n \n ASCII FILE\n LA_52_P58.KID - KIDS distribution for LA*5.2*58 and LR*5.2*266\n \n BINARY FILE\n LA7DIG.PDF - CareVue Installation Guide\n \nINSTALLATION INSTRUCTIONS\n=========================\ndistribution. Because of this, patch descriptions for LA*5.2*58 and\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\nLR*5.2*266 are identical and contain routine summaries for both sets of\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n 1. Review your mapped set. If any of the routines listed in\n patches LA*5.2*58 or LR*5.2*266 are mapped, they should be\n removed from the mapped set at this time.\n \n 2. From the Kernel Installation & Distribution System menu (XPD\n MAIN), select the Installation menu option, then the option,\nroutines.\n Load a Distribution. Enter your directory name and\n LA_52_P58.KID at the Host File prompt.\n \n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the \n Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n \n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. It is recommended that this release be installed during off\n peak hours. To prevent a possible problem with the tasking\n of the next days laboratory orders, do not install this package\n at the same time as the following nightly tasked jobs:\n \n LRTASK ROLLOVER\nLR*5.2*266 do not contain any changes to the VISTA BLOOD BANK Software as\n**NOTE**\n LRTASK NIGHTLY\n LRTASK CONJAM\n LRTASK CUM\n \n 5. No options need to be placed out of service.\n \n 6. Installation time is less than 2 minutes during off peak \n hours and less than 5 minutes during peak hours\n \n 7. From the 'Installation Menu' of the KIDS menu, run the \n \n option 'Install Package(s)' Select the package 'LA*5.2*58'\n and proceed with the install. When prompted 'Want to \n DISABLE Scheduled Options, Menu Options, and Protocols? \n YES//', choose 'NO'.\n \n 8. This patch updates the Processing RTN field (#771) and the\n Response Processing RTN field (#772) of the Protocol file\n (#101) for the LA7D CARELIFE RESULTS and LA7D CARELIFE SERVER\n entries. The letter "Q" will be entered by the post-init\n routine LR266 if no entry exists. The LR266 routine will\nThe laboratory routines LRVER3A and LRMIUT are being modified by this\n automatically be deleted after the patch is installed.\n \n 9. If any routines were unmapped as part of step 2, they \n should be returned to the mapped set once the installation \n has run to completion.\npatch. These routines may have been locally modified at the sites. The\nsites must ensure that precautions are taken to prevent loss of local\nmodifications when patches to Laboratory are installed.\n \n**NOTE**\n \nWhen initially setting up the FOREIGN INTERFACE file (#62.487), the\ndefined by VHA DIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION\nFOREIGN COMPUTER INTERFACE NAME field (#.01) should ALWAYS be set to\n"CAREVUE" (all caps, no leading or trailing spaces, and no quotes). The\nroutines that access this file are looking specifically for CAREVUE. The\nroutines will not be able to process the results for CareVue ward patients\nif this is not done.\n \nThis patch contains changes to Class I CareVue code and requires that\npatch LA*5.2*53 and LR*5.2*263 be installed before LA*5.2*58. Patches\nLA*5.2*58 and LR*5.2*266 are contained in the same KID file\n(LA_52_P58.KID) and will be installed together.\n5.2.\n \nThis patch includes the following changes:\n \n1. This patch updates the documentation released with the CareVue\nInterface patch (LA*5.2*53).\n \n2. This patch makes changes to the routines LRVER3A and LRMIUT, and will\ncreate a new routine (LA7DLOC). Currently, two routines (LRVER3A and\nLRMIUT) contain the Class I software for the CareVue interface. This patch\nwill modify these routines to call the new routine (LA7DLOC). LA7DLOC\n \ncontains the Class I code for determining if a patient is located in a\nCareVue ward. The current condition of the Class I code checks the CHEM,\nHEM, TOX, RIA, SER, etc. field (#4) and the Microbiology field (#5) of the\nLab Data file (#63), but the updated routines will call LA7DLOC and will\nlook in the Ward Location field (#.1) of the Patient file (#2). This\nshows the current location of the patient. There were problems with\npatients that were not transferred to the CareVue ward until after the lab\norder was taken. The old routine was checking where the patient was\nlocated when the order was taken, and not the current location of the\npatient.\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patches LA*5.2*58 and\n \n3. Updates to the HL/7 date conversion routines. The previous standard\nfor HL/7 dates listed the date in YYYYMMDDHHMMSS format. The degree of\nprecision was listed as a separate parameter. The new standard format is\n[YYYY[MM[DD[HH[MM[SS]]]]]-zzzz] where the bracketed sections are optional\ndepending on the existence of the subsequent set. Also, if either the\nseconds or the minutes/seconds combination consist only of zeroes, the\nminutes (if zeroes) and seconds will be omitted. The length of the\ndate/time string specifies the degree of precision. In addition, a ZULU\ntime offset (-zzzz) is also included. This is the number of hours between\nLR*5.2*266 do not alter or modify any software design safeguards or safety\nGreenwich Mean Time and the local time where the date/time string was\ncreated. Routines LA7DVM and LA7DVEXT have been modified to use the\nKernel function ($$FMTHL7^XLFDT) to convert dates from FileMan to HL7\ninstead of the HL/7 date conversion utility ($$HDATE^HLFNC).\n \n4. This patch will use TaskMan to transfer data to the CareVue system.\nCurrently, TaskMan is not invoked. This could cause a problem verifying a\nresult if an error was encountered in the CareVue routines.\n \n5. This patch changes the LA7D EDIT FOREIGN INTERFACE (Edit Foreign\ncritical elements functions.\nInterface Parameters) option. It is now easier to add a Ward to a Foreign\nComputer System Name.\n \n6. This patch updates the Processing RTN field (#771) and the Response\nProcessing RTN field (#772) of the Protocol file (#101) for the LA7D\nCARELIFE RESULTS and LA7D CARELIFE SERVER entries. The letter "Q" will be\nentered by the post-init routine LR266 if no entry exists.\n \nNOIS - MIA-0600-30434\n Reported an error, MISSING PROCESSING ROUTINE, when sending the HL7\n \n message from VistA to CareVue. The letter "Q" will be entered by\n the post-init routine LR266 if no entry exists.\nNOIS - MWV-0900-21094\n Reported that all CareVue ward patients tests were not being sent to\n the CareVue system. It was discovered that these patients were ones\n who were transferred from a non-CareVue ward to a CareVue ward after\n the tests were ordered. The patient was bypassed since the location\n at time of order was not a CareVue ward. This patch will correct\n this by looking at the Ward Location field (#.1) in the Patient file\n (#2) for the current location of the patient.\n\n
\nSubject: RESOLVE ANATOMIC PATHOLOGY LOGIN/REPORT PROBLEMS\nThis patch is to resolve a number of Anatomic Pathology problems related to\n FS/Gross/Micro/Dx/ICD9CM Coding [LRAPDGI]\n Spec Studies-EM;Immuno;Consult;Pic, Anat Path [LRAPDSS]\n Provisional anatomic diagnoses [LRAPAUPAD]\n Autopsy protocol [LRAPAUDAP]\n Autopsy protocol & ICD9CM coding [LRAPAUDAA]\n Final autopsy diagnoses date [LRAPAUFAD]\n Special studies, autopsy [LRAPAUDAS]\n SNOMED coding, anat path [LRAPX]\n ICD9CM coding, anat path [LRAPICD]\n Supplementary report release, anat path [LRAPRS]\nlog-in and reporting.\n \nPatch LR*5.2*248 adds the following new fields:\n \nLAB DATA file (#63)\n AUTOPSY SUPPLEMENTARY REPORT (field #32.4, sub-file 63.324)\n SUPPLEMENTARY REPORT MODIFIED multiple (field #2, sub-file 63.3242) (New)\n SUPPLEMENTARY REPORT MODIFIED (field #.01) (New)\n PERSON MODIFYING TEXT (field #.02) (New)\n PREMODIFICATION TEXT (field #1, sub-file 63.32421) (New)\n \n \n SURGICAL PATHOLOGY(field #8, sub-file 63.08)\n SUPPLEMENTARY REPORT (field #1.2, sub-file 63.817)\n SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.8172) (New)\n SUPPLEMENTARY REPORT MODIFIED (field #.01) (New)\n PERSON MODIFYING TEXT (field #.02) (New)\n PREMODIFICATION TEXT (field #1, sub-file 63.81721) (New)\n \n EM (Electron Microscopy)(field #2, sub-file 63.02)\n SUPPLEMENTARY REPORT (field #1.2, sub-file 63.207)\n SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.2072) (New)\n******************************************************************************\n SUPPLEMENTARY REPORT MODIFIED (field #.01) (New)\n PERSON MODIFYING TEXT (field #.02) (New)\n PREMODIFICATION TEXT (field #1, sub-file 63.20721) (New)\n \n CYTOPATHOLOGY (field #9, sub-file 63.09)\n SUPPLEMENTARY REPORT (field #1.2, sub-file 63.907)\n SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.9072) (New)\n SUPPLEMENTARY REPORT MODIFIED (field #.01) (New)\n PERSON MODIFYING TEXT (field #.02) (New)\n PREMODIFICATION TEXT (field #1, sub-file 63.90721) (New)\nPatch LR*5.2*248 VISTA BLOOD BANK SOFTWARE \n \nThe Anatomic Pathology problems addressed by this patch are as follows:\n \nA. ANATOMIC PATHOLOGY LOGIN/DATA ENTRY\n \n1. SYSTEM HANGS DURING LOG-IN, ANAT PATH [LRAPLG] OPTION\n \nWhen two or more users are trying to login in patients using the Log-in, anat\npath [LRAPLG] option the system hangs after the patient location is entered\nbecause the record in the ACCESSION file (#68) is locked. The solution is to\nDEVICE PRODUCT LABELING STATEMENT\nput a five second time out on the lock with the message "Someone else is\nlogging in specimens. Please wait and try again." For example:\n \nSelect Patient Name: DOE,JOHN 01-01-69 511111211 YES\n \nPATIENT LOCATION: BON-DOM CLINIC//\n \nSomeone else is logging in specimens. Please wait and try again.\n \nNOIS: MUS-0395-70386, SHR-0595-70238\n \n \n2. CONTINUOUS LOOP OCCURS IN LOG-IN, ANAT PATH [LRAPLG] OPTION\n \nIf a user is entering data using the option Log-in, anat path [LRAPLG] and the\nuser does not have the LRLAB, LRSUPER, LRVERIFY, or LRLIASON security keys,\nthe patient location prompt does not appear. If the patient is a new patient\nwith no data in the LAB DATA file (#63), the code tries to file '???' as the\npatient location. The Fileman DIE call does not accept '???' for patient\nlocation so it attempts to retrieve the patient location again. The result is\nan endless loop which prints "This is the requesting location." For example:\nAugust 23, 2000\n \nAssign SURGICAL PATHOLOGY accession #: 2 ? YES// (YES)\nDate/time Specimen taken: TODAY// (DEC 11, 1995)\n This is the requesting location.\n This is the requesting location.\n This is the requesting location.\n \nThe fix to the problem is to replace the '???' with 'UNKNOWN' which is\naccepted by Fileman. NOIS: DUB-0895-32241, LEB-0899-22335, SAM-0499-22281,\nWRJ-0298-11480, SAM-0598-20421\n \n \n3. ERROR OCCURS WHEN USING ENTER OLD ANAT PATH RECORDS [LRAPOLD] OPTION\n \nWhen using the Enter old anat path records [LRAPOLD] option, the variable LRA\nis not defined causing an undefined variable error while attempting to send\nfemale patient data to Women's Health. For example:\n \nEnter Accession number: 377\nDATE REPORT COMPLETED: Mar 06, 1984// (MAR 06, 1984)\nPATHOLOGIST: LAB STAFF LAB STAFF LS -- \nVISTA Laboratory Package patch LR*5.2*248 contains changes to software \n \nRECORDING THAT AN ERROR OCCURRED ---\n \n Sorry 'bout that\n \n $STACK=8 $ECODE=,M6,\n $ZERROR=ADD+6^LRWOMEN:1, %DSM-E-UNDEF, undefined variable LRA,\n-DSM-I-ECODE, MUMPS error code: M6\n \nTo correct this error, the code now checks the LRA variable before \n\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \nproceeding. NOIS: OKL-0799-72578, FAV-0999-71182, AUG-1299-32707,\nANN-0200-42620, WRJ-0500-10974.\n \n4. ACCESSION NUMBER/PATIENT NAME PROMPT DOES NOT FUNCTION PROPERLY\n \nA number of Anatomic Pathology data entry options use a common prompt to \nrequest accession lookup by number or patient name. The prompt is:\n \n Select Accession Number/Pt name:\n \n \nThe options are:\n \n Clinical Hx/Gross Description/FS [LRAPDGD]\n FS/Gross/Micro/Dx [LRAPDGM]\n FS/Gross/Micro/Dx/SNOMED Coding [LRAPDGS]\n FS/Gross/Micro/Dx/ICD9CM Coding [LRAPDGI]\n Supplementary Report, Anat Path [LRAPDSR]\n Spec Studies-EM;Immuno;Consult;Pic, Anat Path [LRAPDSS]\n Provisional anatomic diagnoses [LRAPAUPAD]\n Autopsy protocol [LRAPAUDAP]\nThe changes have been reviewed by the VISTA Blood Bank Developer and found to\n Autopsy protocol & SNOMED coding [LRAPAUDAB]\n Autopsy protocol & ICD9CM coding [LRAPAUDAA]\n Final autopsy diagnoses date [LRAPAUFAD]\n Autopsy supplementary report [LRAPAUSR]\n Special studies, autopsy [LRAPAUDAS]\n SNOMED coding, anat path [LRAPX]\n ICD9CM coding, anat path [LRAPICD]\n Modify anat path gross/micro/dx/frozen section [LRAPM]\n Verify/release reports, anat path [LRAPR]\n Supplementary report release, anat path [LRAPRS]\nhave no impact on the VISTA BLOOD BANK SOFTWARE control functions.\n \nWhen an accession number is entered at this prompt, data is retrieved \nproperly. However, when a patient name is entered another patient name\nprompt appears requiring the user to re-enter the patient name. A\ndifferent name can even be used at the second prompt. For example:\n \nSelect Accession Number/Pt name: JONES\n \nSelect Patient Name: SMITH\n \n \nA second problem also occurs at this prompt. In most data entry options, the\ndata entry year prompt appears just before the accession number/patient name\nprompt. For example:\n \nData entry for 2000 ? YES// (YES)\n \nSelect Accession Number/Pt name: 1 for 2000\n \nIf the accession number is used for lookup, only accessions for the year \nchosen are allowed to be entered. However, if patient name is used for \nPROBLEM: \nlookup, all accessions found for the patient are presented to the user. If \nthe user chooses an accession for a year that is not the same as the year \nentered at the original prompt, it is possible that accession data for the \nwrong patient is presented to the user. This occurs because the lookup \nuses the year entered at the original prompt, not the actual year of the\naccession when locating the data in the ACCESSION file (#68). \n \nThese problems have been resolved by modifying the prompt to perform lookup \nfor both accession number and patient name, eliminating the second prompt.\nThe prompt has also been modified to present only accessions for the chosen\n# 1. Changes have been made to routines LRU and LRUPA to eliminate \nyear when looking up the accession by patient name. Help text has been added\nto the prompt as well. NOIS: HAM-1199-22006, HAM-1100-21233, BOI-0400-52235\n \nB. ANATOMIC PATHOLOGY REPORTS\n \n1. UNNECESSARY FORM FEEDS OCCUR WHILE PRINTING ANATOMIC PATHOLOGY REPORTS\n \nSeveral Anatomic Pathology reports are violating the DHCP Programming\nStandards and Conventions (SAC) by starting with a forum feed before printing\nthe report and printing two form feeds at the end of the report. These \n unnecessary form feeds seen in some Anatomic Pathology reports.\nreports, the Surgical Pathology, Cytopathology and Electron Microscopy\nPreliminary, Final and Supplementary Reports, the Autopsy Protocol and\nSupplementary reports, and the Final Pathology Report by Accession Number have\nbeen corrected by removing the unnecessary form feeds so that the reports now\nconform to standards. The related options for these reports are:\n \n Print all reports on queue [LRAP PRINT ALL ON QUEUE]\n Print single report only [LRAP PRINT SINGLE]\n Print final path reports by accession # [LRAPFICH]\n Autopsy protocol/supplementary report [LRAPAUPT]\n Blood Bank reports are unaffected. \n Print path modifications [LRAPMOD]\n Print path gross/micr/dx/fr.sect modifications [LRAPQAM]\n \nNOIS: WPB-0696-30073, IND-1097-41646\n \n2. NOT ABLE TO DISTINGUISH BETWEEN THE PATIENT AND THE PHYSICIAN\n ON THE FOOTER OF THE AUTOPSY PROTOCOL REPORT.\n \nThe autopsy protocol report is generated by the Print all reports on queue\n[LRAP PRINT ALL ON QUEUE], Print single report only [LRAP PRINT SINGLE], and\n \nAutopsy protocol/supplementary report [LRAPAUPT] options. The footer of the\nautopsy protocol report has been modified to distinguish the patient's name\nfrom the physician's name because it is easy for those reading the report to\nconfuse the two names. Labels "Patient:" and "Physician:" were added in front\nof the names so that they are now easy to identify. The spacing of the other\nfields has been adjusted to allow for better readability. For example:\n \nPathologist: DOE,JOHN wty| Date Nov 24, 1999|\n------------------------------------------------------------------------------\nDallas CIOFO AUTOPSY PROTOCOL\nCategory: ROUTINE\n# 2. Changes have been made to routine LRUPT to include the Autopsy\nPatient: SMITH,JOHN 567-44-5533 SEX:M DOB:Sep 09, 1979\nMEDICINE Physician: DOE,JANE AGE AT DEATH:\n \nAlso, the field spacing of the header for the weights, measures, and coding\nsection of the report has been redesigned for better readability. For \nexample:\n \nJan 10, 2000 11:08 Dallas CIOFO Pg: 9\nANATOMIC PATHOLOGY\n------------------------------------------------------------------------------\n accessions number on the report produced by the Show list \nSMITH,JOHN 567-44-5533 DOB:Sep 09, 1979\nAcc #: AU 99 2 AUTOPSY DATA Age:\nDate/time Died Date/time of Autopsy\nMay 07, 1999 FULL AUTOPSY Oct 14, 1999 17:19\n \nNOIS: None\n \n3. CREATE AN AUDIT TRAIL FOR THE SUPPLEMENTARY ANATOMIC PATHOLOGY REPORTS\n \nIt is possible to edit a supplementary report with no audit trail after the \n of accessions for a patient [LRUPT] option. Changes have also been \nreport has been released. This patch will create an audit trail when a\nreleased supplementary report is edited or when the entire pathology report \nis edited. The audit trail information such as who modified the report, the\ndate/time the modification was made, and the original text before the\nmodification occurred will appear on the supplementary report. New fields have\nbeen created to store this data. The fields are:\n \na.) SUPPLEMENTARY REPORT MODIFIED\n \nWhen a user modifies an existing report, the date/time of the modification is\n made to this routine to fix a problem that occurs when an accession\nstored in this field. If the user creates a new supplementary report for a \nreleased pathology report, this audit information is also stored.\n \nb.) PERSON MODIFYING TEXT\n \nThe DUZ of the user who created or modified the report is stored in this\nfield.\n \nc.) PREMODIFICATION TEXT\n \n is collected in one year but tests are performed in the next year. \nThis is the original text, as it existed before the modification occurred.\nThis is for existing reports only.\n \nSince supplementary reports are included in the autopsy, surgical pathology,\nelectron microscopy, and cytopathology sections, these three fields were \nadded for each section in the LAB DATA file (#63) as follows:\n \nLAB DATA file (#63)\n \nAUTOPSY SUPPLEMENTARY REPORT (field #32.4, sub-file 63.324)\n In this case, some of these tests are omitted from the report created\n \nNew fields:\n \n Multiple field SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.3242)\n \n Consisting of:\n \n SUPPLEMENTARY REPORT MODIFIED (field #.01)\n PERSON MODIFYING TEXT (field #.02)\n PREMODIFICATION TEXT (field #1, sub-file 63.32421)\n by the Show list of accessions for a patient [LRUPT] option. The\n \nSURGICAL PATHOLOGY(field #8, sub-file 63.08)\n SUPPLEMENTARY REPORT (field #1.2, sub-file 63.817)\n \nNew fields:\n \n Multiple field SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.8172)\n \n Consisting of:\n \n option now displays the previously omitted tests.\n SUPPLEMENTARY REPORT MODIFIED (field #.01)\n PERSON MODIFYING TEXT (field #.02)\n PREMODIFICATION TEXT (field #1, sub-file 63.81721)\n \nEM (Electron Microscopy)(field #2, sub-file 63.02)\n SUPPLEMENTARY REPORT (field #1.2, sub-file 63.207)\n \nNew fields:\n \n Multiple field SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.2072)\n \n \n Consisting of:\n \n SUPPLEMENTARY REPORT MODIFIED (field #.01)\n PERSON MODIFYING TEXT (field #.02)\n PREMODIFICATION TEXT (field #1, sub-file 63.20721)\n \nCYTOPATHOLOGY (field #9, sub-file 63.09)\n SUPPLEMENTARY REPORT (field #1.2, sub-file 63.907)\n \nRISK ANALYSIS: Changes made by patch LR*5.2*248 have no effect on Blood \nNew fields:\n \n Multiple field SUPPLEMENTARY REPORT MODIFIED (field #2, sub-file 63.9072)\n \n Consisting of:\n \n SUPPLEMENTARY REPORT MODIFIED (field #.01)\n PERSON MODIFYING TEXT (field #.02)\n PREMODIFICATION TEXT (field #1, sub-file 63.90721)\n \n DATA DICTIONARY\nBank software functionality, therefore RISK is none.\nAny option that allows the input of supplementary reports has been modified\nto store these three pieces of information multiple times for each \nmodification to a supplementary report. This is not visible to the user. \nThese options include Supplementary Report, Anat Path [LRAPDSR] and Autopsy\nsupplementary report [LRAPAUSR].\n \nAll options that print supplementary report information have been modified \nto display the audit information as well. These options include:\n \n Print all reports on queue [LRAP PRINT ALL ON QUEUE]\n \n Print single report only [LRAP PRINT SINGLE]\n Print final path reports by accession # [LRAPFICH]\n Print path modifications [LRAPMOD]\n Autopsy Protocol/Supplementary Report [LRAPAUPT]\n Print path gross/micr/dx/fr.sect modifications [LRAPQAM]\n \nThis information is displayed for preliminary reports, final reports, autopsy\nprotocol, and autopsy supplementary reports.\nE3R: 3687 NOIS: SAM-0599-21489, DAY-0499-40904, SLC-1199-52531,\nSLC-1199-51746\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*248 does not \n \n4. THE DUZ OF THE TECHNOLOGIST, RATHER THAN THE INITIALS, APPEARS ON\n THE 'TECH' COLUMN OF THE ACCESSION LIST BY DATE [LRUPAD] OPTION REPORT.\n \nThe Accession List by Date [LRUPAD] option report is incorrectly displaying a\nnumeric value that has no meaning to the user in the 'Tech' column. The\nsoftware has been modified to print the initials of the technologist who\nverified the report. For example:\n \nJan 10, 2000 11:20 Dallas CIOFO Pg: 1\nalter or modify any software design safeguards or safety critical elements \nCHEMISTRY (Jan 01, 1999-Jan 10, 2000)\n# = Not VA patient %=Test not verified\nAcc # Date Patient ID Loc Spec/sample Test Tech\n------------------------------------------------------------------------------\n 1 01/04 STAHLMAN,ALBERTA 1263 W3E SERUM %LYTES FS\n 2 01/04 STAHLMAN,ALBERTA 1263 W3E SERUM %CALCIUM FS\n \nNOIS: ALN-0395-10067\n \n5. A PATHOLOGIST IS ABLE TO ENTER A FUTURE DATE/TIME WHEN USING\nfunctions.\n VERIFY/RELEASE REPORTS, ANAT PATH [LRAPR] OPTION TO RELEASE A\n PATHOLOGY REPORT.\n \nWhen using option Verify/release reports, anat path [LRAPR] to release a\npathology report, the pathologist may enter a future date/time at the\n'Report Release Date/Time' prompt. Only current date/time should be\nallowed. The prompt has been replaced with a yes/no question as follows:\n \nRelease report? No//\n \n \n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n! PLEASE NOTE: With the old prompt, the user was able to enter an !\n! 'N' for NOW to store the current date/time. A response of 'N' !\n! at the new prompt will result in a 'No' which will leave the !\n! report unreleased. !\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n \nIf the user answers 'Yes', the current date/time is stored in the REPORT\nRELEASE DATE/TIME field (#.11) of the SURGICAL PATHOLOGY sub-file (#63.08),\nfield (#8) of the LAB DATA file (#63) for the SURGICAL PATHOLOGY section. \nPOTENTIAL IMPACT ON SITES: This patch contains changes to a file \nFor the CYTOPATHOLOGY section, the current date/time is stored in the REPORT\nRELEASE DATE/TIME field (#.11) of the CYTOPATHOLOGY sub-file (#63.09), \nsub-field (#9). For the ELECTRON MICROSCOPY (EM) section, the current \ndate/time is stored in the REPORT RELEASE DATE/TIME field (#.11) of the EM \nsub-file (#63.02),sub-field (#2). For the AUTOPSY section, the current \ndate/time is stored in the AUTOPSY RELEASE DATE/TIME field (#14.7) of the \nLAB DATA file (#63). If the report has already been released, the following \ntext will appear:\n \n Report released JAN 06, 2000@16:47:32 by YOUNG,TIM\nidentified in Veterans Health Administration (VHA) Directive 99-053, group \n \nThe user will then be prompted for another accession number or patient \nname.\n \nThe "@" sign response to unrelease Provisional Anatomical Diagnosis reports\nawaiting Final Anatomical Diagnosis has been changed to a YES/NO response \n(i.e.,Unrelease report? NO//YES). NOIS: REN-0197-61357\n \n6. WEIGHTS, MEASURES, AND CODING PRINT ON AUTOPSY REPORT REGARDLESS OF\n ANSWER TO YES/NO QUESTION ON AUTOPSY PROTOCOL REPORT.\nB listing. The changes have no effect in Blood Bank functionality or \n \nWhen option Print all reports on queue [LRAP PRINT ALL ON QUEUE] or option\nPrint single report only [LRAP PRINT SINGLE] is used for the AUTOPSY section\nto create the Autopsy Protocol Report, the question 'Print weights, measures\nand coding (if present): ? YES// ' is asked. Regardless of the user's\nresponse to this question (Yes or No), the weights, measures, and coding\ninformation is printed on the report. The Autopsy Protocol report has been\ncorrected so that if the user answers 'No' to this question, the weights,\nmeasures, and coding information will not print on the report. \nNOIS: DAY-0595-40195\nmedical device control functions. There is no adverse potential to sites.\n \n7. ACCESSION NUMBER WRAPS ON SURGICAL PATHOLOGY REPORTS\n \nWhen using option Print single report only [LRAP PRINT SINGLE] or option \nPrint all reports on queue [LRAP PRINT ALL ON QUEUE]to print pathology \nreports, if the accession number is too large, it wraps to the next line \nwhen the report prints. This problem was resolved by adjusting the print \nposition of the accession number so that no wrapping will occur.\nNOIS: MAR-0398-22377\n \n ENHANCEMENT\n \n8. SYNONYMS MAY CAUSE INCORRECT TESTS TO BE DISPLAYED ON THE LAB ORDERS BY \n COLLECTION TYPE [LRRP5] OPTION REPORT\n \nThe Lab Orders by Collection Type [LRRP5] report may indicate incorrect\ntests as being ordered if a particular test has a SYNONYM (field #2, \nsub-file #60.1) of the LABORATORY TEST file (#60) that is identical to the \ninternal entry number (IEN) of the look-up test. For example, suppose \nGLUCOSE has an IEN of 175 in the LABORATORY TEST file (#60) and FERRITIN \nhas a SYNONYM (#2) of 175 in file #60. When the code is executed, the return\nvalue is Ferritin and not Glucose. The fix to this problem is to concatenate\nVALIDATION REQUIREMENTS BY OPTION: There are no required validation \nan accent/grave (`)character to the beginning of the lookup value before\nperforming a lookup with DIC(0). When the accent grave (`) character is \nused, the lookup is limited to the internal entry numbers only and thus\nignoring the SYNONYM (#2). NOIS: IND-0797-40657.\n \n9. PROBLEMS WITH SHOW LIST OF ACCESSIONS FOR A PATIENT [LRUPT] OPTION\n \nTwo different problems were reported with this option. They are:\n \n(A) When running the Show list of accessions for a patient [LRUPT] option,\nscenarios to be completed by sites after installing this patch.\n'??' displays where the accession should be when using the Autopsy section.\nThis option will now display the accession number on the report for the\nAutopsy section. NOIS: AUG-0398-32638\n \n(B) There is also a problem with certain tests not appearing when this option\nis run, even though the missing tests do appear on other accession list\nreports. For example:\n \nCHEMISTRY DANGERFIELD,RODNEY ID: 222-33-4444 TESTS ORDERED\nSpec Date/time Acc # Site/specimen Tests\n******************************************************************************\n01/15/93 10:11 CH 0115 9 SERUM 1)CALCIUM\n12/26/92 11:00 CH 0115 8 SERUM \n11/13/92 16:14 CH 1113 6 SERUM 1)GLUCOSE\n \nNotice that the test is missing on the second line. It was discovered that \nthis occurred on accessions in which the user enters a collection date for\nthe previous year but the order date is in the current year. For example:\n \nACCESSION: CH 0115 8 ORDER #: 183 PATIENT: DANGERFIELD,RODNEY\n 222-33-4444\n \n LOCATION:GEN MED DATE ORDERED: 01/15/93\n ** COLLECTED: 12/26/92 11:00 **\n PRACTITIONER: BABCOCK,LISA LAB ARRIVAL: 01/15/93 08:23\n \nThis scenario occurred because routine ^LRUPT was using the wrong year when \nlooking for information in the ACCESSION file (#68.) LRUPT has now been \ncorrected to use the correct year. NOIS: SYR-0193-10004\n \n10. TYPO IN CODE EXECUTED WITH THE DISPLAY STAINS/BLOCKS FOR A PATIENT \n [LRAPST] OPTION\nDocumentation Retrieval\n \nThe carat (^) is missing from the global entry in routine AU^LRAPST1 which\ncauses an error that no autopsy accession exists for this patient even if one\ndoes exist. The carat has now been added and the routine will now properly\nindicate whether an autopsy accession number exists for the patient.\nNOIS: AUG-0398-32638\n \n11. REPORTS NOT QUEUED TO THE COMPLETED REPORT QUEUE\n \nA modification to routine LRAPM, released in patch LR*5.2*231, inadvertently\n=======================\nprevents reports generated by the [LRAPM] Modify anat path\ngross/micro/dx/frozen section option, from being queued to the completed\nreports print queue if the patient is male. The code has now been corrected.\nNOIS: There is no NOIS associated with this item.\n \n12. ANATOMIC PATHOLOGY REPORTS BECOME UNRELEASED WHEN NO CHANGES ARE MADE \n USING THE MODIFY ANAT PATH GROSS/MICRO/DX/FROZEN SECTION [LRAPM] OPTION\n \nA problem was reported regarding the use of the Modify anat path\ngross/micro/dx/frozen section [LRAPM] option to modify the gross description\n \nof a released/verified report. Even though the user returned through all the\nprompts without making changes and the report is tagged as not modified, the\nreport became "UNRELEASED" making it unavailable for providers to view. This\nerror has now been corrected so that if no changes are made to the report, the\nrelease date/time remains in place. NOIS: BHS-0600-12155\n \nReference NOIS list: LEB-0899-22335\n DAY-0499-40904\n SAM-0599-21489\n MAR-0398-22377\nThe VISTA Laboratory Anatomic Pathology User Manual V. 5.2 released in \n IND-1097-41646\n REN-0197-61357\n WPB-0696-30073\n DUB-0895-32241\n SHR-0595-70238\n DAY-0595-40195\n MUS-0395-70386\n ALN-0395-10067\n SAM-0598-20421\n SAM-0499-22281\nOctober 1994, has been revised to include an Appendix B section and is \n WRJ-0298-11480\n OKL-0799-72578\n FAV-0999-71182\n SLC-1199-52531\n SLC-1199-51746\n IND-0797-40657\n AUG-0398-32638\n SYR-0193-10004\n AUG-1299-32707\n ANN-0200-42620\n\ndistributed with the release of this patch. Appendix B consists of file \n WRJ-0500-10974\n HAM-1199-22006\n BHS-0600-12155\n BOI-0400-52235\n HAM-1100-21233\n E3R 3687\n \n Test Site(s): Salt Lake City, UT\n Indianapolis, IN\n Long Beach, CA\nchanges, newly created fields, option modifications, and examples of \n Boston HCS, MA\n \nRoutine Summary:\n===============\n \n The second line of the routine now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Values\nreformatted reports.\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------------\n LR248 N/A 3570608 248\n LRAP 8960424 6775842 72,248\n LRAPA 5518427 5022677 72,248\n LRAPAUPT 363769 334176 72,248\n LRAPAUSR 13001981 7330790 1,173,248\n LRAPCUM 13885153 11172316 34,72,173,248\n LRAPD1 12517156 10636533 41,91,248\n \n LRAPDA 15350791 8740574 72,73,91,121,248\n LRAPDSR N/A 3990550 248\n LRAPF 2521051 1475553 173,201,248\n LRAPFICH 4228420 3308525 72,173,248\n LRAPLG1 8045741 5113296 72,121,248\n LRAPM 12219262 10603100 72,91,130,231,248\n LRAPMOD 1323197 1033623 72,248\n LRAPQAM 1890936 1547830 58,72,248\n LRAPR 10330077 8948563 72,248\n LRAPST1 3294764 2795806 72,248\nThe revised AP User Manual is available in the Portable Document Format \n LRAPT 6949633 4005558 72,173,248\n LRAPT2 13264635 7303166 1,248\n LRAUDA 2289072 2236387 72,248\n LRAURPT 15587538 9211437 1,72,173,248\n LRDPA 9160462 7837880 137,121,153,202,211,248\n LRRP5 5707864 5885743 121,201,248\n LRSPRPT 14718178 12472946 1,72,248\n LRSPRPTM 3560888 1356491 1,248\n LRSPT 5816607 5396521 1,72,248\n LRU 18425779 13660500 1,72,201,248\n(PDF) file (i.e., LR5_2APUM.PDF) at the following Office of Information \n LRUPA 8236266 8345323 72,248\n LRUPA2 10757832 9659310 72,248\n LRUPAD 7596723 7616356 72,248\n LRUPAD1 7381083 3450917 248\n LRUPAD2 8939713 5347530 72,248\n LRUPS 6061957 4571479 72,248\n LRUPT 10235244 9461906 1,153,201,248\n LRWOMEN 944687 953781 231,248\n \nInstallation Instructions:\nField Office (OIFO) ANONYMOUS.SOFTWARE account directories and VA Intranet \n=========================\n \nThis patch can be installed with users on the system. However, it is \nrecommended that installation occur when there is no Anatomic Pathology\nactivity or activity is at a minimum. This will prevent 'Cannot return to \nsource routine' errors. The Anatomic Pathology menu will be disabled \nautomatically by this patch and re-enable after installation.\n \nInstall Time - approximately 1 minute\n \nweb site location:\n 1. LOAD TRANSPORT GLOBAL\n ---------------------\n Choose the PackMan message containing this patch and invoke the\n INSTALL/CHECK MESSAGE PackMan option.\n \n 2. DISABLE ROUTINE MAPPING (DSM for Open VMS sites only)\n -----------------------\n Disable routine mapping on all systems for the routines listed\n in the Routine Summary above.\n \n \n NOTE: If the routines included in this patch are not currently\n in your mapped routine set, please skip this step.\n \n 3. START KIDS\n ----------\n Start up the Kernel Installation and Distribution System Menu\n [XPD MAIN]:\n \n Edits and Distribution ...\n Utilities ...\nAll sites are encouraged to use their FTP capability to obtain the PDF file.\n Installation ...\n \n Select Kernel Installation & Distribution System Option: INStallation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\nDescription:\n \n Unload a Distribution\n Backup a Transport Global\n \n Select Installation Option:\n \n 4. Select Installation Option\n --------------------------\n NOTE: The following are OPTIONAL:\n \n a. Backup a Transport Global - This option will create a backup\nAnonymous Software Accounts:\n message of any routines exported with this patch. It will\n not backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option\n will allow you to view all changes that will be made when\n this patch is installed. It compares all components of this\n patch (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will\n allow you to ensure the integrity of the routines that are\n in the transport global.\n \n \n 5. Select Installation Option: Install Package(s) \n ----------------------------------------------\n **This is the step to start the installation of this KIDS patch:\n \n a. Choose the Install Package(s) option to start the patch\n install. When prompted for the INSTALL NAME, enter LR*5.2*248.\n b. There is no need to rebuild the menus.\n c. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//' answer NO\n d. Option Anatomic Pathology [LRAP] will be disabled by PRE^LR248\n IRM FIELD OFFICE FTP ADDRESS DIRECTORY\n before the install begins. POST^LR248 will re-enable the option\n after installation is complete.\n \n 6. REBUILD MAPPED ROUTINE(S) (DSM for Open VMS sites only)\n -------------------------\n Optional - Include the routines distributed with this patch in\n the mapped routine set.\n \n ================ =========== =========\n ALBANY 152.127.1.5 [ANONYMOUS.SOFTWARE]\n HINES 152.129.1.110 [ANONYMOUS.SOFTWARE]\n SALT LAKE 152.131.2.1 [ANONYMOUS.SOFTWARE]\n \nThe following options have been modified with the release of this patch:\n===========\n \n Supplementary Report, Anat Path [LRAPDSR]\n Autopsy supplementary report [LRAPAUSR]\n Accession list by date [LRUPAD]\n Show List of Accessions for a Patient [LRUPT]\n Modify anat path gross/micro/dx/frozen section [LRAPM]\n Lab orders by collection type [LRRP5] \n Verify/Release Reports, Anat Path [LRAPR]\n Enter old anat path records [LRAPOLD]\n Log-in, anat path [LRAPLG]\n \n Autopsy Protocol and SNOMED Coding [LRAPAUDAB]\n Autopsy Protocol/Supplementary Report [LRAPAUPT]\n Print path gross/micr/dx/fr.sect modifications [LRAPQAM]\n Print path modifications [LRAPMOD]\n Print final path reports by accession # [LRAPFICH]\n Print all reports on queue [LRAP PRINT ALL ON QUEUE]\n Print single report only [LRAP PRINT SINGLE]\n Clinical Hx/Gross Description/FS [LRAPDGD]\n FS/Gross/Micro/Dx [LRAPDGM]\n FS/Gross/Micro/Dx/SNOMED Coding [LRAPDGS]\n\n
\nVISTA BLOOD BANK SOFTWARE V5.2 DEVICE PRODUCT LABELING STATEMENT\nto have no impact on the VISTA BLOOD BANK SOFTWARE control functions. \nlocal 'LMI' mailman mail group.\n If there were no install error during the update process and the update\nwas successful, all LAB NLT/CPT CODES file entries will be deleted and the\nfile will only contain one entry, NLT CODE 2000, after the install.\n \n \nNOTE: Additional workload codes added to the WKLD CODE file are populated\nwith CPT codes. Before the added codes are linked to LABORATORY TEST\nprocedures, the CPT coding should be reviewed to ensure it is appropriate\nfor the laboratory test it is being linked with.\n \nIf the CPT code requires changing, use the 'Edit or Print WKLD CODES' [LR\nWKLD CODE EDIT PRINT] option. Enter an INACTIVE DATE for the incorrect CPT\ncode. Then enter the correct CPT code and enter a RELEASE DATE of 'NOW'.\n \nExample:\n \nSupervisor menu\n \nSelect Supervisor menu Option: Lab liaison menu\n \nRISK ANALYSIS: Changes made by patch LR*5.2*258 have no effect on Blood\nSelect Lab liaison menu Option: LIM workload menu\n \nSelect LIM workload menu Option: Edit or Print WKLD CODES\n \nDo you want to edit ALL WKLD CODES ? NO//\n This option will allow you to Edit or Print WKLD CODES that have been\nactivated on your system. Only activated WKLD CODES will be displayed\n \n \nDo you want to select a specific WKLD CODE LAB SECTION? Y// ES\nBank software functionality, therefore RISK is none.\nSelect WKLD CODE LAB SECT NAME: chem Chemistry\n \n Select one of the following:\n \n E EDIT\n P PRINT\n \nWould you like to: EDIT EDITING\n \n Select one of the following:\n \n \n 1 ALL\n .02 DESCRIPT\n 4 BILLABLE PROCEDURE\n 7 COST\n 8 PRICE\n 9 SORTING GROUP\n 13 WKLD CODE LAB SECTION\n 14 DSS Feeder\n 18 CODE\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*258 does not\n 19 SYNONYM\n 20 SPECIMEN\n 21 LOCAL ACC AREA\n \nSelect a field you want to edit : 18 CODE\n \n [The previous display is repeat after each field selection.]\n \n \nUse mixed case Characters e.g. Chloride \nalter or modify any software design safeguards or safety critical element\nStart with what WKLD CODE name: Chloride\nSTARTING LOOP \n \nPROCEDURE: Chloride WKLD CODE: 82435.0000 UNIT FOR COUNT: TEST\n \nMANUFACTURER: NOT SPECIFIED \nWKLD CODE LAB SECTION: Chemistry \n \nSelect CODE: 89399// \n CODE: 89399 PATHOLOGY LAB PROCEDURE// \nfunctions. \n RELEASE DATE: DEC 17,1999// \n INACTIVE DATE: T-1 (DEC 10, 2000)\n REPLACEMENT CODE: 82435\n CODE NOTES:\n No existing text\n Edit? NO// YES\n \nChange from Pathology Procedure to Chloride\n \nSelect CODE: CPT.82435\n \n \n Searching for a active CPT code., (pointed-to by CODE)\n \n \n Searching for a active CPT code.\n 82435 ASSAY OF BLOOD CHLORIDE \n ...OK? Yes// (Yes)\n RELEASE DATE: T (DEC 11, 2000)\n INACTIVE DATE: \n REPLACEMENT CODE: \nPOTENTIAL IMPACT ON SITES: This patch contains no changes to files and\n CODE NOTES:\n No existing text\n Edit? NO// \nSelect CODE: \n \nPROCEDURE: Chloride Sweat Test Quant WKLD CODE: 89360.0000\n \nOptions:\n===================\n \n=============================\nroutines identified in Veterans Health Administration (VHA) Directive\nThis patch will install a new option 'NLT Mapped Code Search' [LRCAP64S]\nThis option is designed to assist in management of national codes linked\nto WKLD CODE (#64) file entries.\n \nNAME: LRCAP64S MENU TEXT: NLT Mapped Code Search\n TYPE: run routine CREATOR: STALLING,FRANK\n PACKAGE: LAB SERVICE\n DESCRIPTION: This option is useful when determining what codes are\nlinked to what entry in the WKLD CODE (#64) file. Several national coding\nschemes (i.e. CPT, LOINC, MORPHOLOGY) can be linked to the WKLD CODE file.\n99-053. The changes that are made have no effect to Blood Bank\nThis option will search the entire WKLD CODE file to determine if specific\nnational codes are linked. \n \nThe search can be done for as many codes of the same set as required. The\nreport will list the national code(s) and any WKLD CODE(s) linked. \n \nThis option can be used to assist when a particular national code should\nbe changed or deleted.\n \n LRMENU Laboratory DHCP Menu\nfunctionality or medical device control functions. There is no adverse\n \nSelect Laboratory DHCP Menu Option: Supervisor menu\n \nSelect Supervisor menu Option: Lab liaison menu\n \nSelect Lab liaison menu Option: LIM workload menu\n \nSelect LIM workload menu Option: NLT Mapped Code Search\n \n Select one of the following:\npotential to sites.\n \n 1 CPT\n 2 SNOMED\n 3 ICD9\n 4 LOINC\n \nSelect the code type: 1 CPT\nSelect CPT Code: ASSAY FOR ETHANOL ??\n Answer with CPT NUMBER, or CPT CODE, or CPT CATEGORY, or DESCRIPTION\n Do you want the entire 14963-Entry CPT List? \n \nSelect CPT Code: 82055 ASSAY OF ETHANOL \n Select another CPT code : 82060 ASSAY BLOOD ETHANOL INACTIVE CODE\n Select another CPT code : 82065 ASSAY URINE ETHANOL INACTIVE CODE\n Select another CPT code : \nDEVICE: HOME//\n CPT Listing Dec 31, 2000 2:18:30 am Page: 1\n \n 82055 ICPT - CPT [ASSAY OF ETHANOL] linked to:\n 694 81506.0000 Alcohol Ethyl\n 2020 81236.0000 Ethanol\nVALIDATION REQUIREMENTS BY OPTION: There are no required validations\n \n 82060 ICPT CPT [ASSAY BLOOD ETHANOL]\n [ IS NOT LINKED ]\n \n 82065 ICPT CPT [ASSAY URINE ETHANOL]\n [ IS NOT LINKED ]\n Finished\n \nRelated NOIS:\n=================================\nscenarios to be completed by sites after installing this patch.\n \n \nTest Site(s):\n=================================\n LONG BEACH, CA\n MUSKOGEE, OK\n MILWAUKEE, WI\n \nRoutine Summary:\n==================================\n \n \nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD Results\n \nRoutine Name Before Patch After Patch Patch List\n============ ============ =========== ===========\nPatch Description:\n \nLR258 N/A 4256733 258\nLR258PO N/A 12054813 258\nLRCAP64S N/A 4824368 258\nLRCAPDAR 7026344 8070808 143,169,258\n \n \n Installation Instructions:\n ==========================\nThe Host File for this patch can be obtained from the ANONYMOUS.SOFTWARE\n===========================\ndirectory at one of the following OI Field Offices:\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n Albany 152.127.1.5 anonymous.software\n Hines 152.129.1.110 anonymous.software\n Salt Lake 152.131.2.1 anonymous.software\n \nThe file name is LR52_258.KID \n \n \n \nPathology and Laboratory Medicine Service Central Office authorizes all\n 1. From the Kernel Installation & Distribution System\n select the 'Installation Menu'. Select the option\n Load a distribution.\n Select [disk storage location]LR52_258.KID\n 2. The patch has now been loaded into a Transport global \n on your system. You now need to use KIDS to install \n the Transport global.\n On the KIDS menu, under the 'Installation' menu, use \n the following options:\n Print Transport Global (Patch size is very large)\nentries in the National Laboratory Test files. This patch adds or updates\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 3. Users may remain on the system however Laboratory \n users must be idle. This to say the laboratory users should\n not accessioning, instrument downloads or test verification\n during the install. Installation should be done during off\n peak hours.\n 4. No options need to be placed out of service. No\n laboratory background jobs have to be stopped.\nNational Laboratory Test (NLT) codes.\n 5. Installation time is less than 15 minutes during off \n peak hours and less than 35 minutes during peak hours.\n 6. Installation of this patch requires minimal additional \n disk space. Review your map set for the routine\n LRCAPDAR. The routine LRCAPDAR should not be\n currently mapped. If LRCAPDAR is mapped you must\n rebuild map sets after installation.\n 7. From the 'Installation Menu' of the KIDS menu, run the \n option\n 'Install Package(s)' Select the package 'LR*5.2*258' \n \n and proceed with the install.\n 8. When prompted 'Want KIDS to INHIBIT LOGONS during the\n install? YES//' respond NO.\n 9. When prompted 'Want to DISABLE scheduled Options, Menu\n Options, and Protocols? YES//' respond NO. Respond to Rebuild\n Menu Trees? YES// YES\n 10. After successful installation, routines LR258 and\n LR258PO should be removed from the system.\nAfter the install has been completed. All users can now resume normal\nactivities of accessioning and test verfications.\nThis patch updates the WKLD CODE (#64) file with additional workload\n \nLaboratory Information Manager (LIM) should review the mail message\ncontaining the workload codes additions to determine if there is a need to\nlink or re-link laboratory tests. Before linking any workload code the CPT\ncoding should be reviewed for appropriateness.\ncodes. These workload codes are sometimes referred to as (NLT) codes. New\nentries to the WKLD CODE files should never be added using FileMan Enter\nEdit option. Use instead the option 'Add a new WKLD code to File' [LRCAP\nCODE ADD].\n \n June 10, 1999 \nThe Laboratory Management Index Program (LMIP) workload collection\nsoftware will automatically make additions to the WKLD CODE as required.\n \n DO NOT USE FileMan ENTER EDIT option TO MAKE ADDITIONS TO THE WKLD\nCODE (#64) file.\n \nNOTE: The WKLD CODE (#64) file is not replaced. The file will be checked\nfor name spelling errors and entries changed if required. If names are\nchanged, they will be reported via mail message to the local mail group\nLMI. In previous releases, some names were exported with trailing spaces.\n \nThis will be corrected with this patch install.\n \nThis patch will replace the LAB NLT/CPT CODES (#64.81) file during\ninstallation:\n \nThis patch also updates the LAB DSS LAR EXTRACT (#64.036) file data\ndictionary to include two new fields. SPECIMEN COLLECTION DATE (#10) and\nSPECIMEN COLLECTION TIME (#11). The routine LRCAPDAR has been enhanced to\npopulate the new fields.\n \nVISTA Laboratory Package patch LR*5.2*258 contains no changes to software\nNOTE: LAB DSS LAR EXTRACT file is used exclusively by the laboratory DSS\nAPI for collecting clinical data. This file is not used or managed by the\nLab Service software.\n \nThis patch includes a new (3rd) cross reference in the WKLD CODE (#64)\nfile on the CODE (#18) subfile, CODE (.01) field. The entire file is cross\nreferenced using the "AB" subscript.\n Cross Reference description:\n ^LAM("AB",VARIABLE POINTER,IEN,MULTIPLE LOCATION NUMBER)=""\n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \nThe WKLD SUFFIX CODES (#64.2) file contains a new field VENDOR (#19). This\nfield is used to describe the original manufacturer for this suffix.\n \nUpdate Logic:\n \nThe KIDS install populates National Laboratory Tests (NLT) with a\ncomplete listing of new and previously released codes if they are missing.\nThese files are:\n \n WKLD CODE (#64)\n \n WKLD SUFFIX CODES (#64.2)\n WKLD CODE LAB SECT (#64.21)\n WKLD ITEM FOR COUNT (#64.22)\n WKLD INSTRUMENT MANUFACTURER (#64.3)\n LAB NLT/CPT CODES (#64.81) Only used during patch installation.\n \nNOTE: WKLD CODE (#64) file or any entries in the file are never deleted.\nOnce an entry has been added to the WKLD CODE file, it remains for the\nlife of the file.\n \nAll changes have been reviewed by the VISTA Blood Bank Developer and found\nThe LAB NLT/CPT CODES (#64.81) file is populated with a complete list of\nall released WKLD CODE procedures.\n The post install routine reads entries from the LAB NLT/CPT CODES file.\nThe install software first determines if the WKLD CODE number already\nexist in WKLD CODE. If the WKLD CODE number exists, the spelling is\nchecked and changed if required.\n If the WKLD CODE does not already exist, the new WKLD CODE is added to\nthe WKLD CODE file.\n If a spelling change was required or a new WKLD CODE is added to the\nWKLD CODE file, this information is included in a mail message sent to the\n\n\nVISTA Laboratory Package patch LR*5.2*268 contains no changes to software\nthe corrective actions.\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak hours.\n The install will disable several Lab options as specified in #7 below.\n \n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n1. NOIS CIN-0299-41416 reported that when using the combination of\n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\nlisting by date and NOT wanting only incomplete entries, the report\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab options during patch\n installation.\ndid not print all entries (completed and incomplete accessions). \n \n Long form accession list [LRACC1]\n Long form accession list for microbiology [LRMIACC1]\n Lookup accession [LR LOOKUP ACCESSION]\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*268'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LR268 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\nNone\n \n \nThe reports have been corrected to print completed accessions when the\n************************************************************************\nInstallation example:\n\nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*268 Loaded from Distribution 12/8/00@11:51:43\n => LR*5.2*268\n \nThis Distribution was loaded on Dec 08, 2000@11:51:43 with header of\n LR*5.2*268\n It consisted of the following Install(s):\nuser answers "NO" to the prompt "Do you want only incomplete entries?".\n LR*5.2*268\nChecking Install for Package LR*5.2*268\nWill first run the Environment Check Routine, LR268\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*268\n \n \n\nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \n2. At the prompt "Do you want only incomplete entries?" if the user\nDEVICE: HOME//\n \n \n Install Started for LR*5.2*268 :\n Dec 08, 2000@11:52:44\n \nBuild Distribution Date: Dec 08, 2000\n \n Installing Routines:....\n Dec 08, 2000@11:52:44\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nentered a "?" the software would bypass the prompt and proceed to the \n \n Running Pre-Install Routine: PRE^LR268.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\nnext prompt for device selection. Entering a "?" will now present the\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION...\n Dec 08, 2000@11:52:44\n \n Running Post-Install Routine: POST^LR268.\n \n *** Post install started ***\n \nuser with a help message and return to the prompt. This defect was\n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \nidentified during software review.\n LR*5.2*268 Installed.\n Dec 08, 2000@11:52:45\n \n Install Message sent #113161\n \nSelect Installation Option:\n \n3. Printing of the lab order number and the patient name could print\ntogether when the order number exceeds five digits. Also patients with \nlong names could cause the printing of the patient's identifier (SSN)\nto wrap to the next line of the display. The printing of accession and\npatient information on the report has been adjusted to provide sufficient\n \nspace to avoid this information printing together. This defect was \nidentified during software review.\n \n4. The patch corrects a Vista Programming Standards and Conventions\n(SAC) violation that was identified during software review as part of\npatch development. The patch removes direct global read of global ^VA(200)\nwhich contains the NEW PERSON (#200) file. Routine LRWRKLS1 was\nretrieving user's name. Call to the file has been changed to Kernel\nsupported reference (DBIA # 10060) using FileMan DBS call $$GET1^DIQ.\nThis defect was identified during software review.\nThis patch will addresses a fix to the options Long form accession list\n \n5. The patch converts a call to routine LRAFUNC1 to display date/time\nvalues. This routine is being phased out. Call has been replaced with\ncalls to Kernel supported XLFDT date/time function.\n \n6. Various non-interactive calls to %DT in routines LRWRKLST and LRWRKLS1\nhave been replaced with calls to corresponding Kernel supported XLFDT\ndate/time functions to determine current date/time and display other\ndate/time values associated with the accession.\n \n[LRACC1] and Long form accession list for microbiology [LRMIACC1]\n7. When selecting a listing for a specific test and incompletes only\ncriteria the report would print information for some accessions before\napplying the selection criteria. The report has been changed to print\npatient and accession information when the accession meets the specified\nselection criteria. This defect was identified during software review.\n \n8. The options Long form accession list [LRACC1] and Long form accession\nlist for microbiology [LRMIACC1] will now honor stop requests when tasked.\nUsers can call the TaskMan User [XUTM USER] option to stop tasks that they\nstarted.\nregarding the printing of completed accessions from non-daily accession\n \n \nASSOCIATED NOIS\n---------------\n CIN-0299-41416 \n \n \nASSOCIATED E3R'S\n----------------\n None\nareas. The problem was reported in NOIS CIN-0299-41416. Additional\n \n \nTEST SITES\n----------\n Cincinnati VAMC\n Milwaukee VAMC\n \n \nROUTINE SUMMARY\n===============\nproblems (item 2-8) were identified for these two options during the\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR268 N/A 4332160 **268** (Deleted by KIDS)\n LRWRKLS1 6588663 4126947 **121,153,185,268**\n LRWRKLST 9455120 6742016 **1,17,38,153,185,221,268**\nsoftware review for patch development. Listed below are the problems and\n \nList of preceding patches: 221\nSites should use CHECK^XTSUMBLD to verify checksums. \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n\n
\nThis is a Patch for a Patch.\n1. The routine LRAUSTA which was supposed to be part of patch LR*5.2*72\nwas never exported with the patch. Since this report is rarely run by the\nsites, this was never noticed during the testing of the patch\n \n2. During the LRAPFIX data conversion, the ^LR("AAUA", node was rebuilt\nusing the new accession # format, however the old ^LR(AAUA", node was not\ndeleted. This is why the routine was picking up the Autopsies logged in\nprevious to the loading of the patch.\n \nThe other problem was reported by the Bronx. A null subscript error would\n \noccur during the option Malignancy review [LRAPQAMR] if the following\nconditions were met:\n \n 1. There were reports positive for malignancy during the time period\nthe report was requested for.\n \n 2. The user responds "YES" to the prompt:\n Do you want corresponding permanent pathology reports to print\nfollowing search ? NO// Y (YES)\n \nIt was discovered that 2 separate AP reports were not functioning\nThe null subscript error would occur because the routine LRAPQAMR was\nattempting to get a patient's LRDFN from the ^LR(LRXREF,LRY,LRAN,0)\nreference when in fact this reference should have been updated to reflect\nthe new format of this node after the data conversion of LR*5.2*72. The\ncorrect reference should have been ^LR(LRXREF,LRY,LRABV,LRAN,0). The code\nwas changed to this new reference as well as inserting Quit statements for\nthe $O command.\n \n \n \ncorrectly after installation of LR*5.2*72\nBoth of these issues will be resolved with this patch.\n \nFirst--It was discovered after patch LR*5.2*72 was released that the\nAutopsy Status Report did not capture Autopsies done after the load date\nof the patch. This actually is the symptom of two separate problems:\n \n\n\nVISTA Laboratory Package patch LR*5.2*262 contains no changes to software\nlogic in the collection list receipt process was not submitting all\n \n Receipt of routine lab collection from wards [LRPHEXCPT]\n Itemized routine lab collection [LRPHITEM]\n Add to collection list [LRPHMAN]\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*262'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \naccessions on a lab order to the Lab Universal Interface Auto Download.\n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LR262 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\n \nNONE\n \nRoutine LRPHITEM was only submitting the accession associated with the \n \n************************************************************************\nInstallation example:\n \nSelect INSTALL NAME: LR*5.2*262 Loaded from Distribution 6/8/00@11:32:29\n => LR*5.2*262\n \nThis Distribution was loaded on Jun 08, 2000@11:32:29 with header of\n LR*5.2*262\n It consisted of the following Install(s):\nlast test on a Lab order to the auto download process. This patch corrects\n LR*5.2*262\nChecking Install for Package LR*5.2*262\nWill first run the Environment Check Routine, LR262\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*262\n \n \nthis logic error. It will now scan all tests on a given order and submit\nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nto the auto download process those accessions associated with the lab order.\nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LR*5.2*262 :\n Jun 08, 2000@11:35:10\n \nBuild Distribution Date: Jun 08, 2000\n \n Installing Routines:...\n Jun 08, 2000@11:35:10\n \n \n Running Pre-Install Routine: PRE^LR262.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\n \n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION....\n Jun 08, 2000@11:35:10\n \n Running Post-Install Routine: POST^LR262.\n \n *** Post install started ***\n \n \n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \nASSOCIATED E3R'S\n LR*5.2*262 Installed.\n Jun 08, 2000@11:35:10\n \n Install Message sent #25038\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n----------------\n#13785 - LRPHMAN & LRPHEXCPT BOTH SENDING HL7 MESSAGE\n \n \nTEST SITES\n----------\n Asheville VAMC\n Boston HCS\n Central Plains HCS\n Indianapolis VAMC\n \n Milwaukee VAMC\n San Antonio VAMC\n San Diego VAMC\n Tennessee Valley HCS\n Upstate New York HCS \n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n \n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR262 N/A 4332130 **262**(deleted by Kernel)\n LRPHITEM 14270617 12142394 **121,198,208,202,221,262**\n \nList of preceding patches: 221\nDESCRIPTION\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n===========\n The install will disable several Lab option as specified in #7 below.\n Building and receipting of collection lists should not be occurring\n within the Laboratory package.\n \n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\nThis patch will address a fix to the Lab Universal Interface Auto Download\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \nrequested in E3R #13785 - LRPHMAN & LRPHEXCPT BOTH SENDING HL7 MESSAGE.\n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\nDuring development of patch LA*5.2*57, it was determined that the software\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab options during patch\n installation.\n\n
\nThis patch provides the VistA Blood Bank Software the ability to read and\ninterpret blood product barcode labels using the ISBT 128 system. The\nability to read and interpret blood product labels using the Codabar\nsystem is unaffected. \n \nA full description of this patch can be found in the Forum Patch Module\nlisting for patch LR*5.2*267.\n\n
\nThis patch allows you to map Lab tests to a default LOINC code.\nNational training will be provided to aid sites in mapping the sites' tests\nto LOINC codes.\n \nThe LAB LOINC (95.3) file is updated to LOINC (R) version 1.0N.\n\n
\nVISTA Laboratory Package patch LR*5.2*269 contains no changes to software\n \n \n \nTEST SITES\n----------\n Durham VAMC\n Lexington VAMC\n Philadelphia VAMC\n \n \nROUTINE SUMMARY\n1. When using option Group verify (EA, EL, EW) [LRGV] that the warning\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR269 N/A 4831472 **269** (Deleted by KIDS)\n LRGP 6947313 5798854 **153,269**\nmessage "THIS DATA APPEARS TO BELONG TO SOMEONE ELSE" was displayed on\n LRGP1 8924262 3988622 **112,269**\n LRGV 13358239 7051872 **269**\n LRGV1 5973234 3094124 **112,153,269**\n LRGV2 11151687 3432003 **121,153,269**\n \nList of preceding patches: 153\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n************************************************************************\n \neach accession to be verified. This defect was caused by the inappropriate\nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n The install will disable several Lab options as specified in #7 below.\n \n \nNOTE: Kernel patches must be current on the target system\nuse of the $TEST function. Routine LRGV1 will now skip result data in\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\nthe ^LAH global if the data does not belong to the same accession area,\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \naccession date and accession number. NOIS LEX-1098-42357 and PHI-0201-21212\n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routines in your\n production account to the routines in the patch by using the 'Compare\n \n a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab options during patch\n installation.\n \n Group verify (EA, EL, EW) [LRGV]\n Group unverified review (EA, EL, EW) [LRGP]\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*269'. When prompted 'Want to\n2. During patch development software review the following SAC violations\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LR269 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\nwere identified.\nNone\n \n \n************************************************************************\nInstallation example:\n \nSelect Installation Option: 6 Install Package(s)\n \nSelect INSTALL NAME: LR*5.2*269 Loaded from Distribution 10/31/01@14:08:53\n => LR*5.2*269 TEST v6\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n \n \nThis Distribution was loaded on Oct 31, 2001@14:08:53 with header of\n LR*5.2*269 TEST v6\n It consisted of the following Install(s):\n LR*5.2*269\nChecking Install for Package LR*5.2*269\nWill first run the Environment Check Routine, LR269\n \n \n Sending install started alert to mail group G.LMI\n a. Routine LRGV2 contained a direct global read of the ^DD global to\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*269\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? NO//\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n retrieve the name of the corresponding dataname from LAB DATA file\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// 0;P-OTHER;80;99999999 TELNET VIRTUAL\n \n \n Install Started for LR*5.2*269 :\n (#63), CHEM, HEM, TOX, RIA, SER, etc. subfile (#4). Defect corrected\n Oct 31, 2001@14:20:51\n \nBuild Distribution Date: Mar 29, 2001\n \n Installing Routines:.......\n Oct 31, 2001@14:20:52\n \n Running Pre-Install Routine: PRE^LR269.\n \n *** Pre install started ***\n with change to Kernel supported reference (DBIA # 2052) using\n \n *** No action required ***\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION...\n Oct 31, 2001@14:20:52\n \n FileMan DBS call $$GET1^DID.\n Running Post-Install Routine: POST^LR269.\n \n *** Post install started ***\n \n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LR*5.2*269 Installed.\n Oct 31, 2001@14:20:52\n \n Install Message sent #xxxxx\n b. Routine LRGV1 contained locks on ^LAH global without timeouts.\n Defect corrected by adding timeouts to locking of ^LAH global.\n \n \n c. Routine LRGV contained code to set variables IO and IOSL. Defect\n corrected by removing code.\n \n3. During patch development software review the following defects were\n identified and corrected.\n \n a. Comments associated with results could possibly be duplicated\n when moved from the ^LAH global to the LAB DATA file (#63), CHEM,\n HEM, TOX, RIA, SER, etc. subfile (#4), COMMENT field (#.99).\n Defect corrected in routine LRGV2.\n \n \n b. Monthly accession areas would not be processed. Routine LRGP1\n was not calculating accession date correctly for monthly accession\n areas. The defect was reported by Lloyd Milligan of Sea Island\n Systems, Inc.\n \n c. When processing/verifying by tray/cup and a corresponding entry in\n the ^LAH global did not exist for the tray/cup combination then\n processing would stop and leave remaining entries unprocessed.\n Routine LRGV will now continue to process remaining entries.\nDESCRIPTION\n \n d. If results exist for different accession areas but the same\n accession numbers then routine LRGP was not handling these results\n properly and keeping them separate. Routine has been corrected to\n keep results for different accessions but the same accession number\n separate based on accession area and accession date.\n \n e. Option Group unverified review (EA, EL, EW) [LRGP] could print\n results for accessions that are not for the same accession area,\n accession date and accession number. Routine LRGP will now skip result\n===========\n data in the ^LAH global if the data does not belong to the same accession\n area, accession date and accession number.\n \n f. Option Group unverified review (EA, EL, EW) [LRGP] could print\n the wrong date/time on the printed report if the reported was queued\n via TaskMan. Option was printing the date/time that the user originally\n setup the report. Report will now print the date/time that the report\n actually starts to print.\n \n g. Option Group verify (EA, EL, EW) [LRGV] would verify flagged results\nThis patch will address fixes to defects reported in NOIS LEX-1098-42357\n which contained critical results and or a delta check when the user\n indicated that these results should not be group verified. The option\n will now only verify results that are critical or have a delta check\n when the user indicates that flagged results should be verified.\n \n h. Option Group verify (EA, EL, EW) [LRGV] was storing verified results\n in LAB DATA file (#63) without NLT order and result codes, test units,\n performing facility, and results flags. The option will now store these\n result parameters.\n \nand PHI-0201-21212 and compliance changes for Standards and Conventions\n i. Option Group verify (EA, EL, EW) [LRGV] will now allow the user to\n abort from a verifying session and will pause when the display screen\n is filled. The test results being verified will print on the report.\n \n \n4. The options Group verify (EA, EL, EW) [LRGV] and Group unverified\nreview (EA, EL, EW) [LRGP] will now honor stop requests when tasked.\nUsers can call the TaskMan User [XUTM USER] option to stop tasks that\nthey started.\n \nProgramming Standards (SAC) violations for the group verify process.\n\nASSOCIATED NOIS\n---------------\n LEX-1098-42357\n PHI-0201-21212\n \n \nASSOCIATED E3R'S\n----------------\n None\n\n
\nThis patch to the Laboratory package does not contain any changes to the \nassociated with LOINC mapping. In addition there is new functionality\n2) Unmap/Delete Lab Tests to Default LOINC Code\n [LR LOINC UNMAP/DELETE DEFAULT]\n3) Validate LOINC Mapping [LR LOINC VALIDATE]\n \n10. Where appropriate, FileMan lookup and options will now display the \nLOINC code plus the check digit. In the past only the LOINC code was \nshown (i.e. 1-8). This will provide required data for entry into RELMA \nLOINC lookup window.\n \n11. The National Laboratory File [LR7O 60-64] option will be added to the\nprovided for re-transmitting PCE CPT workload.\nLOINC Main Menu [LRLOINC] option.\n \n \nData Dictionary Changes:\n=================\n62.06 ANTIMICROBIAL SUSCEPTIBILITY\n Screen removed from NATIONAL VA LAB CODE #64\n \n64 WKLD CODE\nPartial DD: DEFAULT LOINC CODE #25\n \n Trigger to remove data from field when DEFAULT LOINC CODE is deleted.\nPartial DD: subDD: SPECIMEN #64.01\n subDD: TIME ASPECT #64.02 fld: TEST #3\n Creates and populates the ^LAM("AL") cross reference\n \n68.2 LOAD/WORK LIST \nPartial DD: fld: WKLK METHOD #.14\n Modifies the triggers use to populate fields:\n WKLD CODE METHOD NAME #.15\n WKLD CODE SUFFIX #.16\nObsolete Options:\n \n95.3 LAB LOINC\n CHECK DIGIT (#15) has been made an identifier to improve display and\nlookup.\n \n \nTest Sites:\n=================\n Long Beach, CA\n Muskogee, OK\n===========\n Durham, NC\n \n \nRoutines Summary:\n==================\nThe second line of the routines now looks like:\n<tab> ;;5.2; LAB SERVICE;**[patch list]**; Sep 27,1994\n Checksum values\n \nRoutine Before Patch After Patch Patch list.\nThe Print Default LOINC/LOINC Code by Lab Tests [LR LOINC PRINT\nLR278 NA 5505096 278 (deleted by KIDS)\nLR7OU641 12240284 12410597 153,201,278\nLRCAPD 9261934 9516457 105,163,153,278\nLRCAPPHX NA 5799903 278\nLRLNC0 11822735 14797379 215,232,278\nLRLNC1 3760103 2227160 215,278\nLRLNC1A NA 750293 278\nLRLNCDEL 5416724 6004798 232,278\nLRLNCLK 2054143 2106203 232,278\nLRLNCMD 8362694 6826367 232,278\nDEFAULT/LOINC] option is obsolete and will be placed out of order.\nLRLNCNLT 6478052 6013193 215,278\nLRLNCPMP 4831240 7461913 215,232,278\nLRLNCPRT 4848636 4889813 215,278\nLRLNCV 4009739 3900781 232,278\nLRLNCX 6971341 7117683 232,278\n \nInstallation Instructions:\n=========================\nInstallation should be done during off peak hours.\nLaboratory personnel may be on the system during install but should\n \nnot be active.\n \nInstallation time is less than 2 minutes during off peak hours \nand less than 5 minutes during peak hours.\n \nInstallation of this patch requires no additional memory space.\n \nThis patch is released as a KERNEL Installation and Distribution Systems\n(KIDS) MailMan message.\n \nNew Options:\n 1. START FROM KERNEL \n From the KERNEL Installation and Distribution Systems (KIDS)\n Menu, select the Installation menu [XPD INSTALLATION MENU]: \n Edits and Distribution ... \n Utilities ... \n Installation ... \n \n 2. SELECT INSTALLATION OPTION \n NOTE: The following are OPTIONAL:\n \n===========\n a. Backup a Transport Global - This option will create a backup \n message of any routines exported with this patch. It will not \n backup any other changes, such as DDs or templates. \n b. Compare Transport Global to Current System. NOTE: This option \n will produce a long report due to new files and is not \n recommended.\n c. Verify Checksums in Transport Global - This option will allow \n you to ensure the integrity of the routines that are in the \n transport global. \n 3. SELECT INSTALLATION OPTION: Install Package(s)\nVISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled VISTA\n1. The PCE Retransmit [LRCAPCEX] option is new with this patch. \n Select INSTALL NAME: LR*5.2*278\n 4. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of\n install? Yes//" respond "NO".\n 5. When asked "Want KIDS to INHIBIT LOGONS during the install? YES//",\n respond "NO"\n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//, respond "NO".\n 7. Lab users may resume their normal activities.\n 8. Routine LR278 will be deleted after successful patch installation.\nThis option will reset entries in the LAB ORDER ENTRY (#69) file to allow\nresending of PCE workload for a given date range. This option is useful if\nWKLD CODE did not have CPT code assigned when PCE workload reporting\nsoftware initially ran. \n***CAUTION*** \nThis option will only attempt to resend PCE workload if NO PCE workload\nwas reported FOR THE ENTIRE SPECIMEN ORDER NUMBER during the initial scan\nof collected orders. All original requirements for PCE workload reporting\nare enforced. \nBLOOD BANK SOFTWARE.\n \nThis option maybe useful if linked CPT codes were inactivated during the \nyearly upgrade of the CPT (#81) file. The LIM can edit the WKLD CODE (#64)\nfile with current valid CPT codes and run this option. \n \nThis option cannot be run while the normal PCE workload reporting\nbackground software is running. \n \nThe option will scan the date range entered, printing a dot (".") for\nevery 20th. order processed. Then the option will determine if the order\n \nshould be reported to PCE. As the data is processed, every 20th. order\nnumber is printed.\n \nThis option cannot be queued. Option invokes the routine LRCAPPHX\n \nModified Options:\n================\n1. Map/Unmap Antimicrobial Default LOINC Code [LR LOINC MAP ANTIMICROBIAL\n] option was modified to correct problems with unmapping a LOINC\ncode from several different WKLD CODEs.\nCopyright 1995, 1996, 1997, Regenstrief Institute and the Logical \n \n2. Print Lab Tests Mapped/Not Mapped to LOINC Codes [LR LOINC PRINT 60/LO\nINC MAP] option has been enhanced to provide the following three methods\nto print LOINC mapped data:\n 1) Print all unmapped tests\n 2) Print all mapped tests\n 3) Print individual tests.\n \nThe option functionality was improved by the creation of an additional\ncross-reference ^LAM("AL".\nObservation Identifier Names and Codes (LOINC) Committee. All rights \n \n3. Link Result NLT Manual [LR7O MAN RESULT NLT] option was generating an\nundefined error if the default WKLD CODE was accepted. This problem has\nbeen corrected. The option now properly honors '^' when entered. The \noption will allow any WKLD CODE to be selected.\n \n4. Map/Unmap Antimicrobial Default LOINC Code [LR LOINC MAP ANTIMICROBIAL\n] option has been modified to have the look and feel of other LOINC\nmapping options. Note this option only sets the DEFAULT LOINC CODE (#25)\nof the WKLD CODE (#64) file.\nreserved. LOINC is a trademark of the Regenstrief Institute.\n[It is highly recommended that a different suffixed WKLD CODE be created\nto be used for antimicrobial drug mapping. The WKLD CODE selected must be\ndifferent than the WKLD CODE used for blood analysis.]\n \n5. Extract VistA Lab Test Names [LR LOINC EXTRACT LAB NAMES] options has\nbeen modified to replace '*' or '?' with spaces that occur in test names.\nThis is to prevent RELMA mapping program errors. The extraction logic has\nbeen enhanced to find duplicate laboratory test and synonym names.\n \n6. National Laboratory File [LR7O 60-64] menu was exported with an\n \nerroneous routine attached. The entire menu option is deleted and rebuilt\nwith this install. The menu contains the following options:\n1) Semi-automatic Linking of file 60 to 64 [LR7O 60-64 AUTO]\n2) Manual Linking of file 60 to 64 [LR7O 60-64 MANUAL]\n3) Result NLT Auto Linker [LR7O AUTO RESULT NLT]\n4) Link Result NLT Manual [LR7O MAN RESULT NLT]\nThe routine PSDNDES has been removed.\n \n7. Map Lab Tests to LOINC Codes [LR LOINC MAP] option has been enhanced to\nallow mapping of all laboratory test. In the initial release, only 'CH'\nThis patch contains enhancements that improve several reports\nsubscripted tests were selectable. This restriction has been removed. Only\n'CH' subscripted tests are mapped to TIME ASPECT LOINC codes. Other type\ntests (i.e. Microbiology, Anatomic Pathology) are only mapped to DEFAULT\nLOINC CODE.\n \n8. Print a Single LOINC CODE [LR LOINC PRINT LOINC CODE] option has been\nmodified to display the LOINC CODE check digit beside the LOINC CODE.\n \n9. The following options will now allow selection of any subscript.\n1) Find LOINC for Vista Lab Test [LR LOINC LOOKUP]\n\n\nThis patch was developed to fix defects in the VistA Blood Bank Software v\n5.2 that have been discovered to cause chronic user and database integrity\nproblems.\n \nA full description of this patch can be found in the Forum Patch Module\nlisting for patch LR*5.2*275.\n\n
\n \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: Off peak hours.\n The install will disable a Lab option as specified in #7 below.\n \n1. When using the option Link Result NLT Manual [LR7O MAN RESULT NLT] the\n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \noption was exiting the user to the Kernel menu system after mapping a\n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\nsingle test. This resulted in a user answering the option prompts for\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a Transport\neach test to be mapped. This patch will change the option dialog to\n Global' option at this time. You may also compare the routines in\n your production account to the routines in the patch by using the\n 'Compare a Transport Global to Current System' option.\n \n 7. The install will disable the following Lab option during patch\n installation.\n \n Link Result NLT Manual [LR7O MAN RESULT NLT]\n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\nallow the user to select and map multiple tests after answering the\n and select the package 'LR*5.2*280'.\n \n When prompted ' Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//' choose 'NO'.\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\n \noption prompts. To exit or abort from the option the user should enter\n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LR280 will be deleted after successful patch installation.\n \n \nPOST-INSTALLATION INSTRUCTIONS:\n===============================\nNone\n \n \na "^" which will return the user to the Kernel menu system.\n************************************************************************\nInstallation example:\n \nSelect Installation Option: INStall Package(s)\nSelect INSTALL NAME: LR*5.2*280 \nLoaded from Distribution 12/20/01@10:27:28\n => LR*5.2*280\n \nThis Distribution was loaded on Dec 20, 2001@10:27:28 with header of \n LR*5.2*280\nNOIS DAY-1101-42242 and HWH-1101-42338\n It consisted of the following Install(s):\n LR*5.2*280\nChecking Install for Package LR*5.2*280\nWill first run the Environment Check Routine, LR280\n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \n \nInstall Questions for LR*5.2*280\n \nIncoming Files:\n \n \n 60 LABORATORY TEST (Partial Definition)\nNote: You already have the 'LABORATORY TEST' File.\n \n \n 64 WKLD CODE (Partial Definition)\nVISTA Laboratory Package patch LR*5.2*280 contains no changes to software\n2. FileMan inquires in to files LABORATORY TEST (#60) and WKLD CODE (#64)\nNote: You already have the 'WKLD CODE' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nwas not displaying the check sum digit for all LOINC codes. An output\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET\n \n \n \n Install Started for LR*5.2*280 :\n Dec 20, 2001@11:45:16\n \nBuild Distribution Date: Dec 12, 2001\ntransform has been added to include the check digit with the LOINC code.\n \n Installing Routines:\n Dec 20, 2001@11:45:16\n \n Running Pre-Install Routine: PRE^LR280\n \n *** Pre install started ***\n \n *** No action required ***\n \n \n *** Pre install completed ***\n \n Installing Data Dictionaries: \n Dec 20, 2001@11:45:17\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n Dec 20, 2001@11:45:17\n \n3. In the LABORATORY TEST (#60) file, subfile SITE/SPECIMEN (#100), LOINC\n \nLR*5.2*280 \n \n Running Post-Install Routine: POST^LR280\n \n *** Post install started ***\n \n *** No action required ***\n \n *** Post install completed ***\nCODE (#95.3) field was not being updated for atomic 'CH' subscript tests.\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*280 Installed. \n Dec 20, 2001@11:45:17\n \nThis has been corrected. It has been reported that the zero node of\n Install Message sent #XXXXX\n \n \nInstall Completed\nSITE/SPECIMEN field do not exist. This patch will create the zero node if\nrequired during mapping.\n SPO-120-50468 \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n \n4. During patch development/software review the following defects were\n identified and corrected.\n \n A. In the option Result NLT Auto Linker [LR7O AUTO RESULT NLT] if\n a user requested printing of a List of Result NLT Linked Codes\n and device selection was unsuccessful or aborted then the Kernel IO*\n variables were not being restored to the user's home device. This\n patch will now call HOME^%ZIS when device selection is unsuccessful\n or aborted by the user to restore the user's home device settings.\n \n \n B. If a user selects the semi-auto method of linking, the option was\n exiting the user from the option when a Result NLT was not selected\n and mapped to an entry in the LABORATORY TEST file (#60). This patch\n will allow the user to continue mapping tests. To exit or abort from\n the option the user should enter a "^" which will return the user to\n the Kernel menu system.\n \n C. The entry in LABORATORY TEST file (#60) was only being locked \n when using the manual method of linking. The Semi-auto method was\n \n not locking the file. This patch will lock the entry being edited\n in LABORATORY TEST file (#60) when either method is selected.\n \n5. When mapping certain LOINC codes a FileMan error of 'undefined \n variable ^(4) is' generated because of the lookup screen. This error\n has been corrected.\n SHR-1201-70505\n \n \nASSOCIATED NOIS\nThis patch will address fixes to defects reported in NOIS DAY-1101-42242\n---------------\n DAY-1101-42242\n HWH-1101-42338\n SHR-1201-70505\n SPO-1201-50468 \n MAR-1201-21794\n \nASSOCIATED E3R'S\n----------------\n None\nand HWH-1101-42338 when using the option Link Result NLT Manual [LR7O MAN\n \n \nTEST SITES\n----------\n Dayton VAMC\n Heartland-West HCS\n Milwaukee VAMC\n Shreveport VAMC\n Durham VAMC\n Long Beach VAMC \nRESULT NLT] to map result NLT codes to a site's LABORATORY TEST file\n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n(#60).\n LR280 N/A 4831435 280 (Deleted by KIDS)\n LR7OU641 12410597 12157260 153,201,278,280\n LRLNC0 14797379 15016901 215,232,278,280\n LRLNCC 2637694 2634007 232,280\n LRLNCMD 6826367 6815286 232,278,280\n \n List of preceding patches: 232,278\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \n\n
\nVISTA Laboratory Package patch LR*5.2*222 contains no changes to software\nMulti-purpose Accession [LRLEDI] to accession specimens thru the Laboratory\n --------- -------- ----------------\n LAB_LEDI_II.KID LA*5.2*46 KIDS build ASCII\n LR*5.2*222 KIDS build\n \n LAB_LEDI_II_IG.PDF LABORATORY ELECTRONIC DATA BINARY\n LAB_LEDI_II_IG.DOC INTERCHANGE PHASE II (LEDI II)\n INSTALLATION GUIDE\n \n LAB_LEDI_II_UM.PDF LABORATORY ELECTRONIC DATA BINARY\n LAB_LEDI_II_UM.DOC INTERCHANGE PHASE II (LEDI II)\nElectronic Data Interface (LEDI). The changes contained in this patch are\n USER MANUAL\n \n The software files are available on one of the following OI Field\n Offices' ANONYMOUS.SOFTWARE directories.\n \n All sites are encouraged to use their FTP capability to obtain these\n files. Use the FTP address "download.vista.domain.ext" (without the\n quotes) to connect to the first available FTP server where the files\n are located.\n \nimplemented in conjunction with patch LA*5.2*46. Patch LA*5.2*46 now builds\n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\nthe file LAB PENDING ORDERS ENTRY (#69.6) with additional information\n The instructions for installation of the software are included in the\n installation guide.\n \n \nPOST-INSTALLATION INSTRUCTIONS\n------------------------------\n \n \n The post-instructions for installation of the software are included in\n the installation guide.\nconcerning mapping to local test urgency. This patch introduces changes\n \n \nINSTALLATION EXAMPLE\n====================\n \n An installation example is included in the installation guide.\nthat utilize the local urgency information stored in file #69.6 when\naccessioning LEDI specimens at the host laboratory.\n \nAs of the release date of this software, there is no national solution to\nimplement a laboratory electronic HL7 standard interface to a facility or\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nother entity outside the VA wide area network. National communication\nsecurity concerns are still being debated by the Department of Veterans\nAffairs (VA) and are awaiting resolution. At present, a VA medical center,\nwhich intends to utilize this software in conjunction with an interface to\na commercial reference laboratory or other non-VA information system entity,\nwill need to coordinate with the vendor an acceptable communication method.\nAny implementation will need to be approved by the facility and VISN\nInformation Security Officer (ISO) and meet current VA security requirements\nfor external electronic connections. See VHA Directive 6212, Security of\nExternal Electronic Connections and VHA Directive 6210, Automated Information\n \nSystems (AIS) Security for additional information and guidance. Additional\nsecurity information may be obtained from the Health Information Security\nService (HISS) web page at http://vaww.domain.ext/miss.\n\nImplementation of a HL7 messaging interface between the VA VistA Laboratory\npackage and a non-VA information system consists basically of three parts:\n - VistA Laboratory LEDI II software.\n - certified communication software and hardware\n - non-VA information system capable of sending and receiving laboratory HL7\n order and result messages.\n========================================\nAll three must be functional to utilize the capabilities of this LEDI II\nsoftware patch. The implementation,setup, and configuration of vendor provided\nhardware and software is NOT addressed by this documentation. Consult the\nvendor provided documentation and instructions to interface to the VistA\nLaboratory package.\n \n \nNOIS HUN-1100-21862 reported discrepancies in patient names due to Network\nHealth Exchange not maintaining name changes. This patch removes the use\nof the Network Health Exchange package to lookup patient information\n\n(patient name, patient identifier and date of birth). The link in file\nREFERRAL PATIENT (#67), field Patient Name (#3) to file VAMC NETWORK\nPATIENT (#537010) is removed as a variable pointer.\n\n\nNOIS\n====\nHUN-1100-21862\n\nROUTINE SUMMARY\nPatch LR*5.2*222 will be distributed and installed with patch LA*5.2*46\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR222 N/A 6987123 **222** (Deleted by KIDS)\n LRDPAREF 6854898 5111405 **153,222**\nLEDI INTERFACE TO NON-VA SYSTEM (LEDI II).\n LRORDB 3786248 3782224 **153,222**\n \n List of preceding patches: 153\n Sites should use CHECK^XTSUMBLD to verify checksums. \n \n \nTEST SITES\n----------\n Alexandria VAMC\n Biloxi VAMC\n \n Birmingham VAMC\n Fayetteville VAMC\n Hines VAMC\n Houston VAMC\n Jackson VAMC\n Little Rock VAMC\n Madison VAMC\n Milwaukee VAMC\n Muskogee VAMC\n Oklahoma City VAMC\nThis patch adds additional support when using the option Referral Patient\n Shreveport VAMC\n \n \nSOFTWARE RETRIEVAL:\n===================\n \n The following software and documentation files are exported as part of\n this patch:\n \n File Name Contents Retrieval Format\n\n
\nVISTA Laboratory Package patch LR*5.2*279 contains no changes to \nLOINC mapping of CH subscripted verified results. The software will use \nis terminated by the user. If the process runs successfully to \ncompletion, there will be an END alert for each START alert for each \nbatch sequence number.\n \nIt has been seen at some test sites that the LRDFN may not be in the \nproper form. Test sites have seen the LRDFN set to an inverse date/time \n(LRIDT) value, and in some cases the LRDFN contained a decimal \n(ex.123.5). If such a situation is discovered during the LOINC mapping \nprocess, a properly formatted LRDFN will be created in the ^LR(0) global\nas the next available LRDFN.\nthe existing LOINC mapping configuration defined in WKLD CODE (#64) file. \nThere is a special sequence number (9999999) assigned to those LRDFNs\nhaving LRIDT like format. This sequence will only be established if\nrequired. \n \nMost sites will not have a 9999999 batch sequence number.\n \n NEW OPTIONS:\n ============\n \nThe following options are provided to manage the LOINC mapping processes. \nThis file's definition will be used to determine the LOINC code to be \nThey are contained on the LOINC Historical Mapping Menu [LR LOINC \nHISTORICAL MAP MENU]. This menu is locked with the XUPROGMODE security \nkey and located under the LOINC Mapping Utility Menu [LR LOINC UTILITY].\n \nIt is highly recommend that options provided by this patch be run during \na 24 hour period of low system usage. Normally this would be during the \nweek end. \n \n \nA. LAB DATA LOINC Mapping [LR LOINC HISTORICAL MAPPER 63] option\nassigned to a given result. The historical mapping process extends to the \n \nThis is the primary historical LOINC mapping option that must be run at \nleast once to update ^LR with appropriate LOINC mapping codes. This \noption can be run multiple times if required. This option will initiate \nthe required number of background tasks to inspect the entire LAB DATA \nfile and map verified CH subscripted tests with LOINC codes. This option \nshould only be run during a 24-hour period when the system has low user \nactivity. Note: This option is used also to restart the mapping process \nfrom the point of interruption. The mapping process will continue until \nall LRDFNs have been inspected.\npast 5-6 years of verified 'CH' subscripted data.\n \nThe option is Locked by the XUPROGMODE security key.\n \nExample of the option: User's responce inclosed in < >\n \nSelect LOINC Mapping Utility Menu Option:\n LOINC Historical Mapping Menu\n \n Select LOINC Historical Mapping Menu Option: ?\n \n \n 1 LAB DATA LOINC Mapping\n 2 Restart LOINC Historical Mapping\n 3 STOP LOINC Mapping\n 4 Modify LOINC Historical Mapping\n \n Select LOINC Historical Mapping Menu Option: <1> \n D STOP^LRLNC63 to stop all background historical mapping. \n \n This option should be run during 24 hour off peak time frame!!\n \n Information on the historical LOINC mapping process:\n This option will queue multiple tasks to LOINC map \n historical data in the LAB DATA (#63). \n \n Are you certain you wish to proceed? <YES>\n \n LRDFN Conversion Sequence 1-20001 Task number is 8718\n LRDFN Conversion Sequence 20001-40001 Task number is 8719\n \nEnd of Option example:\n==========\n \n \nAfter successful completion of LOINC mapping for all tasks, the members \nof the G.LMI mail group will receive two types of notifications:\n \n1. MailMan message containing all tests that were not LOINC mapped\n2. Mailman message containing all tests that were mapped. This message is \ndesigned to be imported into a non VistA spread sheet program.\n \nUsing these two reports, the LIM will be able to determine mapping \ncompleteness and identify systematic mapping errors.\nThe historical mapping is an option that cannot be queued. Installation \n \nHere is an example of each.\n \nSubj: LOINC Historical Mapping Exception Report [#89761] 15 Feb 02 10:29\nFrom: POSTMASTER (Sender: ) In 'IN' basket. Page 1 *New*\n--------------------------------------------------------------------------\nList of tests missing RNLT codes in LABORTORY TEST (#60) file,\nfound during LOINC Historical Mapping process.\nThese test(s) will have no historical LOINC mapping performed.\n \nof this patch provides options to perform historical mapping of verified \n[Test IEN] Test Name Type \n \n[37] BLEEDING TIME -- Type: BOTH\n[353] SPHEROCYTES -- Type: OUTPUT (CAN BE DISPLAYED)\n[356] HYPERSEGMENTED NEUTROPHILS -- Type: BOTH\n[357] SMUDGE CELLS -- Type: BOTH\n[137] RPR -- Type: BOTH\n \n \nSubj: LOINC Historical Mapped LOINC tests [#89762] 15 Feb 02 10:29\nsoftware controlled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK \n'CH' subscripted tests.\nFrom: POSTMASTER (Sender:) In 'IN' basket. Page 1 *New*\n--------------------------------------------------------------------------\nList of test mapped to LOINC codes formatted with '^' as field delimiter.\n \nDataName#^Test Name^Specimen^Specimen IEN^RNLT^NLT suffix^LOINC Code\n2^GLUCOSE^PHARYNX^60^84330.0000^0^2339-0\n2^GLUCOSE^BLOOD^70^84330.0000^0^2339-0\n2^GLUCOSE^BLOOD^70^84330.0000^8638^2339-0\n2^GLUCOSE^SERUM^72^84330.0000^0^2342-4\n2^GLUCOSE^SERUM^72^84330.0000^3035^2342-4\n \n2^GLUCOSE^SERUM^72^84330.0000^3103^2342-4\n2^GLUCOSE^SERUM^72^84330.0000^8638^2342-4\n3^UREA NITROGEN^RIGHT KIDNEY^11^84520.0000^0^3097-3\n3^UREA NITROGEN^SERUM^72^84520.0000^0^6299-2\n3^UREA NITROGEN^SERUM^72^84520.0000^3035^6299-2\n3^UREA NITROGEN^SERUM^72^84520.0000^3103^6299-2\n4^CREATININE^Missing^.8^82565.0000^0^2160-0\n4^CREATININE^Missing^.9^82565.0000^0^2160-0\n4^CREATININE^SERUM^72^82565.0000^0^2160-0\n4^CREATININE^SERUM^72^82565.0000^3103^2160-0\nHistorical LOINC mapping is a disk and system intensive process.\n \nB. STOP LOINC Mapping [LR LOINC HISTORICAL STOP 63] option\n \nThis option will stop all background LOINC historical mapping tasks. If \nfor some reason the user wishes to stop/suspend LOINC mapping, this \noption will stop all background tasks. To continue the mapping process \nfrom the last LRDFN, use the primary option, LAB DATA LOINC mapping \nOption.\n \nExample of the option:\n \n \nSelect LOINC Historical Mapping Menu Option: STOP LOINC Mapping\n Stopping all background LOINC historical mapping jobs\n \nAre you certain you want to continue? <YES>\n \nEnd of example\n===========\n \nC. Restart LOINC Historical Mapping [LR LOINC HISTORICAL RESTART 63]\nJournaling has not been a problem at test sites, but with any conversion \n \nThis option will restart the mapping process from the very beginning. \nThis option will reset all counters and reinitiate the ^XTMP("LRLNC63") \nglobal. After the temporary mapping globals have been reset, a call is \nmade to the LAB DATA LOINC Mapping entry point. Rerunning this option is \nnot harmful but the same 24 hours of low system usage considerations \nshould be honored. \n \nOption is locked with the XUPROGMODE security key.\n \nprocess, journal files should be monitored. Temporary data is stored in \n Example of the option:\n \nRestart LOINC Historical Mapping\n This will re-run LOINC Historical Mapping from the beginning\n resetting all globals to zero.\n To restart from a stopping point use the\n LAB DATA LOINC Mapping Option.\n \n \nAre you certain you want to proceed? <YES>\nthe ^XTMP Global. A significant amount of LOINC code related data will be \n \n D STOP^LRLNC63 to stop all background historical mapping tasks.\n \n This option should be run during 24 hour off peak time frame!!\n \n \n This option will queue multiple tasks to LOINC map\n historical data in the LAB DATA (#63).\nAre you certain you wish to proceed? <YES> \n \nset into the ^LR( global.\nEnd of option example.\n \n=================\n \nD. Modify LOINC Historical Mapping [LR LOINC HISTORICAL MODIFY]\n \nThis is a very powerful utility option to be used to reconcile previous \nLOINC historical mapping. A knowledgeable LOINC mapper (Laboratory \nInformation Manager) is required to properly implement this functionality.\n \n \nAfter the initial historical mapping has been completed, adjustments \nmaybe required to modify the LOINC code lookup parameters to properly map \npast results. Careful review of current LOINC mapping should be done to \nestablish IF there is a systematic error in LOINC code assignments. File \ndefinition corrections should be done to prevent future LOINC mapping \nerrors. Re-running LAB DATA LOINC Mapping [LR LOINC HISTORICAL MAPPER 63] \noption will correct incorrectly assigned LOINC code problems. \n \nIn those situations when editing LOINC mapping definition is not \ndesirable, this option provides a method for the user to intervene in the \nThe Historical Mapper functions should be run during a 24 hour period of \nmapping lookup logic for specific tests.\n \nThe user is able to select a lab test(s) [Atomic or Panel], then assign a \nspecific suffix code to be used during LOINC mapping logic. In addition \nthe user is able to force the Result NLT CODE (#64.1) of LABORATORY TEST \n(#60) for the test and the designated suffix code pair to override \nprevious LOINC mapping. \n \nThis is a very powerful feature, great care and study of systematic \nerrors should be used before attempting correct past LOINC mapping \nSOFTWARE.\nlow system demand. Typically this would be during a week end.\nsystematic errors.\n \nAfter the user has completed the modify LOINC mapping procedures, the LAB \nDATA LOINC Mapping option is called. All considerations of this option \nstill apply. Most notably, only performing this mapping exercise during \nweek ends or in a 24 period of lowest system activity. Even with the \nincreased logic iterations, the process should complete within the 24 hr \nwindow of time. \n \nThis option will allow the user to manage how a specific data name (test) \n \nwill be mapped to LOINC Codes for historical data. The user is able to \noverride file definitions to correct past LOINC mappings.\n \n 1. Select the CH subscripted test\n 2. Indicate the suffix to be used.\n 3. The user can indicate if this suffix should override previous LOINC \n Mapping. \n \n Example of the option:\n \n2. Installs 'LRRESOURCE' Resource Device\nThis option will REMAP your entire database using the parameters defined \nby this option. \n \nThis option should only be run on week ends or after hours. \n \n Do you wish to continue ? <YES> \n \n Selection can be a 'CH' Atomic or Panel test . \n \n Select test you want to modify mapping: <CBC> \n \n Select Suffix Code: <.4322> COULTER ELECTRONICS \n Override previous LOINC mapping? <YES> \n \n Selection can be a 'CH' Atomic or Panel test. \n \n Select test you want to modify mapping: <CALCIUM> \n Select Suffix Code: <AA DIRECT> .3901 NOT SPECIFIED\n \n Override previous LOINC mapping? <ret>\n \nThis patch will install a new resource device called 'LRRESOURCE'. This \n Selection can be a 'CH' Atomic or Panel test \n \n Select test you want to modify mapping: <ret>\n \n Here is a list of what you have selected. \n [O] indicates override current mapping\n . DEVICE: HOME// Right Margin:80//\n \n 1 [0] WBC COULTER A /.4322\n 2 [0] MCV COULTER A /.4322\ndevice is installed with eight slots. The number of slots determines the \n 3 [0] MCH COULTER A /.4322\n 4 [0] MCHC COULTER A /.4322\n 5 [0] RDW COULTER A /.4322\n 6 CALCIUM AA DIRECT /. 3901 \n \n You wish to add more? <ret>\n \n Do you want to delete an entry? <ret>\n \n[NOTE: Those tests in the panel or atomic test that do not have a RESULT \nnumber of active LOINC mapping background tasks. The maximum number of \nNLT CODE (RNLT) assigned will be omitted. If this is the case, abort and \nattend to the missing tests RNLT codes.] \n \n3. Resolving the $SELECT statements for normal ranges\n \nThis functionality provided by this patch is to resolve the normal \nrange data stored in a $SELECT format in the LAB DATA file (63). This \npatch will determine the appropriate normal range for the result by \nresolving the $S( statement using the age of the patient at the time the \nspecimen was collected. The $SELECT statement will be replaced with the \nconcurrently running background tasks is eight, the number of slots \nappropriate numerical value.\n \n \nThe routines LRVER4 and LRVR4 are installed with this patch to prevent \nthe storage of the $S statement in ^LR(LRDFN,"CH",LRIDT,LRSB) for future \nresults.\n \nThe routine LRDAGE provides the patient's age at the time when the \nspecimen was collected. The resulting age is used to determine normal \nrange values for historical data.\ndefined in LRRESOURCE. If the user adjusts the number slots of the \n \n \n NEW FILES OR FIELDS:\n ===================\n Two new fields are added during installation of this patch.\n \n In the LABORATORY SITE (#69.9) file the following fields have been added.\n \n LOINC HISTORICAL MAPPING DATE (#95.3) field. \n This is the date that the LOINC Historical mapping was completed. The \nresource device, it must have at least one slot to initiate the mapping \n LAB DATA LOINC Mapping [LR LOINC HISTORICAL MAPPER 63] option populates\n this field after it has successfully completed all mapping.\n \n LOINC HISTORICAL LAST LRDFN (#95.31) field.\n This field is populated by the primary LOINC mapping option if all batch \n (sequences) successfully run to completion.\n This field contains the last LRDFN that was mapped by the LAB DATA LOINC \n Mapping [LR LOINC HISTORICAL MAPPER 63] option.\n \n ASSOCIATED NOIS\n \nprocess. Reducing the number of slots will increase the total mapping \n ===============\n NONE\n \n \n TEST SITES\n ==========\n Minneapolis, MN\n North Chicago, Il\n Milwaukee, WI\n Salem, NC\nprocessing time. Increasing the number of resource slots may NOT reduce \n Martinez, CA\n Palo Alto, CA\n Durham, NC\n Long Beach, CA\n Muskogee, OK\n Fargo, ND\n Cincinnati, OH\n \n ROUTINE SUMMARY \n ===============\nthe total mapping processing time.\n The following routines are included in this patch. The second line of \n these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patch list>;Sep 27, 1994\n \n Routine Checksum Checksum\n Name Before Patch After Patch Patch List\n LR279 N/A 6316492 279 (Deleted\n by KIDS)\n LRDAGE N/A 1480375 279\n LRLNC63 N/A 14818231 279\n \n LRLNC63A N/A 9008516 279\n LRLNC63B N/A 7526980 279\n LRVER4 19181995 18527473 14,42,112,121,140\n 171,153,188,279\n LRVR4 8661306 8664360 14,42,121,153,221\n 263,279\n \n List of preceding required patches:\n LR*5.2*188, LR*5.2*232, LR*5.2*263, LR*5.2*278\n \n The Mapping Process in Detail\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \n INSTALLATION INSTRUCTIONS\n =========================\n \nThe install time for this patch is less than 5 minutes. Laboratory users \nshould be off the system during installation. All other user may remain \non the system.\n \n \nPatch installation should be coordinated with the Laboratory Information \nManager (LIM).\n \n 1. If any of the above routines are mapped, disable mapping for those \n routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan Menu. This \n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your system. \nThe LOINC mapping processes are divided in to batches of 20,000 LRDFN \n You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System's Menu (KIDS) \n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in transport Global' option and verify that \n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following \n options:\nrecords each. The number of batches are determined by the number of \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this patch \n prior to installation, you should use the 'Backup a Transport Global' \n option. You may also compare the routines on your system to the routines \n in the patch by using the 'Compare a Transport Global to your Current \n System' option.\n \nrecords found in the LAB DATA (#63) file. One could estimate the number \n 7. Use the 'Install Package(s)' option under the 'Installation' menu and \n select the package 'LR*5.2*279'.\n \n When prompted 'Want KIDS to INHIBIT LOGONs during install? YES// choose\n'NO'.\n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'\n \n 8. On mapped system, rebuild map set\nof batches by dividing the number of LRDFN records by 20,000. If more \n \n 9. Routine LR279 will be deleted after successful patch installation.\n \n POST-INSTALLTION INSTRUCTIONS:\n =============================\n \n Perform LOINC historical mapping functions.\n \n \n ******************************************\nThe patch provides the following:\nthan eight mapping tasks are required, the remainder tasks will \n Installation Example:\n \n \nSelect INSTALL NAME: LR*5.2*279 Loaded from Distribution \n2/26/02@17:15:29\n => LR*5.2*279\n \nThis Distribution was loaded on Feb 26, 2002@17:15:29 with header of \n LR*5.2*279\n It consisted of the following Install(s):\nautomatically start when a resource slot becomes available. Resource \n LR*5.2*279\nChecking Install for Package LR*5.2*279\nWill first run the Environment Check Routine, LR279\n \n Sending install started alert to mail group G.LMI \n \n --- Environment Check is Ok --- \n \nInstall Questions for LR*5.2*279\n \nslots become available when a mapping sequence batch runs to completion.\nIncoming Files:\n \n 69.9 LABORATORY SITE (Partial Definition)\nNote: You already have the 'LABORATORY SITE' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET\n \n Install Started for LR*5.2*279 : \n Feb 26, 2002@17:18:32\n \nThe objective of the mapping batch size and number is to ensure mapping \nBuild Distribution Date: Feb 25, 2002\n \n Installing Routines:\n Feb 26, 2002@17:18:32\n \n Running Pre-Install Routine: PRE^LR279\n \n *** Pre install started *** \n \n *** No action required *** \nis completed within twenty-four (24) hours. After benchmarking timing \n \n *** Pre install completed *** \n \n Installing Data Dictionaries:\n Feb 26, 2002@17:18:33\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n Feb 26, 2002@17:18:33\nexercises, it has been determined that eight batch jobs of 20,000 records \n \n Running Post-Install Routine: POST^LR279\n \n *** Post install started *** \n \n Adding 'LRRESOURCE' to the Device (#3.5) file \n \n *** Post install completed *** \n \n Sending install completion alert to mail group G.LMI \neach would achieve the mapping time goal.\n \n Updating Routine file\n \n Updating KIDS files\n \n LR*5.2*279 Installed. \n Feb 26, 2002@17:18:34\n \n Install Message sent #XXXXX\n \n \nInstall Completed\n \n End of example\nEach LRDFN in a batch that is not from LAB CONTROL NAME (#62.3) file, is \n \nchecked to determine if NEW PERSON CONVERSION (.12) field of sub-multiple \nCHEM, HEM, TOX, RIA, SER, etc. (#4) of the LAB DATA (#63) file has a \ndesignation of 2. If the check is satisfied the process continues for \nthat LRDFN's inverse date time sub-file.\n \nEach data name (test) of the CH subscript is subjected to a lookup \nprocess to determine the RESULT NLT CODE (#64.1) field of the LABORATORY \nTEST (#60) file.\nThis value is stored in the \n ^XTMP("LRLNC63",1,DATANAME IEN)=Result NLT Code.\n 1. Historical LOINC mapping\n ^XTMP("LRLNC63",1,2) = 84330.0000\n ^XTMP("LRLNC63",1,3) = 84520.0000\n ^XTMP("LRLNC63",1,4) = 82565.0000\n ^XTMP("LRLNC63",1,5) = 84295.0000\n \nThe software then performs a LOINC lookup using the data from the \nDATANAME subscripted node [^XTMP("LRLNC63", 1,DATANAME)] global and the \nfile definitions of WKLD CODE file to determine the LOINC code for the \nresult. If a LOINC code is found the value is stored in the third '^' \npiece in the third piece of '!' delimited field.\n \n \n ^LR(713,"CH",6979880.8746,357)=75^^84009.0000!84009.0000!\n [27057]!3103!1^104^72!50!220!!!!UG/ML!!!75^^^^170^1 \n \n Where [27057] is the LOINC code.\n \nThe last LRDFN processed record for each batch (sequence) is stored in \nthe ^XTMP("LRLNC63","SEQ",#). Where '#' is the batch sequence number in \nincrements of 20,000.\n \nThis patch contains options and software required to perform historical \nOther information stored in the ^XTMP global are:\n ^XTMP("LRLNC63","SEQ",#,"START")=FileMan date/time\n ^XTMP("LRLNC63","SEQ",#,"END")=FileMan date/time\n \nThe time difference between the START and END nodes represent the lapse \ntime for that batch's LOINC mapping.\n \nStatus activity of the mapping process is reported to the LMI mail group \nvia VistA Alerts. An alert is generated when each batch process is \nstarted. An alert is also generated when each batch reaches completion or \n\n\nVISTA Laboratory Package patch LR*5.2*271 contains no changes to software\nmonthly accessions that the software was defaulting to the wrong year.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nRoutine LRWU4 has been corrected to default to the current year when a\n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*271'. \n\n When prompted "Want KIDS to Rebuild Menu Trees Upon Completion\n of Install? //YES", respond NO.\n \n When prompted "Want KIDS to INHIBIT LOGONs during the install?\n YES//", respond NO.\n \n When prompted "Want to DISABLE Scheduled Options and Menu Options?\nuser enters the accession date in the format MM00.\n YES//", respond YES. When prompted "Enter options you wish to mark\n as 'Out of Order':", enter the following to disable all Laboratory\n options:\n \n LR*\n \n \n 7. On a mapped system, rebuild your map set.\n \n NOTE: Routine LR271 will be deleted after successful patch installation.\n \n2. The following defects were identified during the software review as\npart of patch development.\n \n a. When a user enters a partial accession and is prompted for an\naccession date the software was not defaulting to past dates. Defect\ncorrected by including "P" in the variable %DT when calling FileMan's\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n%DT date processing routine.\n \n b. Routine LRFASTS called by option Fast Bypass Data Entry/Verify\n[LRFASTS] does not handle non-daily accession areas correctly. The routine\nwas using the order date as the accession date which is only correct when\nthe accession area associated with a test is daily. LRFASTS has been\ncorrected to retrieve the accession area, date and number for a test from\nLAB ORDER ENTRY file (#69). It will now function correctly when processing\nacccessions from non-daily acession areas, i.e. monthly, quarterly and\nyearly.\n \n \n c. Routine LRVERA was handling accession selection similiar to LRWU4.\nThis routine has been changed to call LRWU4.\n \n d. The entry for Quarterly accession transform in the EXECUTE CODE file\n(#62.07) contains code that creates an invalid FileMan date for the \naccession date. The post install for this patch will check the EXECUTE\nCODE file (#62.07) and ACCESSION file (#68) for entries using the\nQuarterly accession transform and correct the code.\n \nThis patch addresses a fix to defects reported in NOIS BAF-0101-N2560\n \nASSOCIATED NOIS\n---------------\n BAF-0101-N2560 \n BED-0201-12399\n \n \nASSOCIATED E3R'S\n----------------\n None\nand BED-0201-12399. Additional problems (item 2) were identified during\n \n \nTEST SITES\n----------\n Ann Arbor VAMC\n Ashville VAMC\n Bedford VAMC\n Boston HCS\n Detroit VAMC\n Milwaukee VAMC\nsoftware review for patch development. Listed below are the problems and\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\nthe corrective actions.\n ------------ ------------ ----------- ------------\n LR271 N/A 8038072 **271** (Deleted by KIDS)\n LRFASTS 8519940 6423167 **30,95,121,271**\n LRVERA 8140275 690805 **153,271**\n LRWU4 8927540 5815129 **128,153,201,271**\n \n \n************************************************************************\n \nINSTALLATION INSTRUCTIONS\n \n=========================\n \n The install time for this patch is less than 5 minutes.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n1. NOIS'es BAF-0101-N2560 and BED-0201-12399 reported when looking up\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n\n
\nFIX FOR LRDPA\n\n
\n This patch resolves the following problem:\n This patch to the Laboratory package does not contain any changes to the\n VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 97-033 titled VISTA\n BLOOD BANK SOFTWARE VERSION 5.2.\n \n PROBLEM: CPRS calls a Lab API [INTERIM^LR7OGM] that extracts and formats\n lab data for reports on the LAB tab. For results longer than\n 7 characters, the data is being truncated and formatted incorrectly.\n \n RISK ANALYSIS: Changes made by patch LR*5.2*282 have no effect on Blood\n Bank software functionality, therefore RISK is none.\n \n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*282 does not\n alter or modify any software design safeguards or safety critical elements\n functions.\n \n POTENTIAL IMPACT ON SITES: Patch LR*5.2*282 contains no changes to\n routines identified in Veterans Health Administration (VHA) Directive\n 97-033. There is no adverse potential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation\n CPRS calls a Lab API [INTERIM^LR7OGM] that extracts and formats\n scenarios to be completed by sites after installing LR*5.2*282.\n \n TEST SITES FOR THIS PATCH:\n ==========================\n North Texas HCS\n Denver\n Tennessee Valley HCS\n \n RELATED NOIS:\n =============\n lab data for reports on the LAB tab. For results longer than\n TNV-0801-30277\n NTH-0202-72720\n DEN-1298-51612\n \n ROUTINE SUMMARY:\n ================\n The following is a list of the routine(s) included in this patch. The\n second line of each of these routine(s) will look like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n 7 characters, the data is being truncated and formatted incorrectly.\n \n CHECK^XTSUMBLD results\n Routine name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n LR7OGMP 5364802 5548341 187,246,282\n \n INSTALLATION INSTRUCTIONS:\n ==========================\n This patch should be loaded during non-peak hours to minimize disruption\n to users. Installation will take less than 1 minute. Users may remain\n This patch will correct the formatting of long results, by not\n on the system.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. Review your mapped set. If any of the routines listed in the\n ROUTINE SUMMARY section are mapped, they should be removed\n from the mapped set at this time.\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n truncating the results and breaking the line so that units and\n \n 4. From this menu, you may elect to use the following options\n (when prompted for INSTALL NAME, enter LR*5.2*282):\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 5. Use the Install Package(s) option and select the package LR*5.2*282.\n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//'\n reference ranges continue on the next line.\n respond NO.\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond NO.\n \n 8. If routines were unmapped as part of step 2, they should be returned\n to the mapped set once the installation has run to completion.\n \n\n
\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*272 does not \nBank software functionality, therefore RISK is none.\n \n AMA-0695-70804 - E VARIABLE FOR %DT NOT WORKING\n The date/time stamp printed to screen, but not to a printer.\n The reports were using the string 'S X="N",%DT="ET" D ^%DT"\n to print date/time. The call has been updated to use\n '$$FMTE^XLFDT($$NOW^XLFDT,"").' The call to STAMP^LRX is no\n longer used.\n \n HUN-0501-21203 - INCORRECT SPELLING IN LOADLIST.\n An incorrect spelling in the EXPAND PANELS ON PRINT field \n \n (#.06) Of the LOAD/WORK LIST file (#68.2) has been corrected.\n \n LEX-0201-41741 - IMMEDIATE COLLECT SETTINGS BEING OVERRIDDEN\n Immediate collect times are being rejected if seconds are\n entered. Label VALID+10 in routine LR7OV4 has been modified\n to allow the entry\n of seconds in the collect time.\n \n HIN-0701-42680 - QUESTION RE: Y2K DATE FORMAT\n The Y2K conversions changed the format of the date generated\n \n by PRTEST+5^LRSORA2 from MMM DD 'YY to MMM DD 'YYYY. The\n apostrophe in the new format is not necessary. The routine\n has been modified to eliminate the extraneous data.\n \n \n Reference NOIS: LAH-0301-61651\n HIN-0301-40344\n ALB-1099-52504\n ISF-0899-61570\n PHO-0699-61637\n Nineteen NOIS calls are addressed in this patch. These are:\n NTH-0399-71865\n FRE-0599-60964\n CHY-0798-52175\n MOU-0498-32262\n PUG-1297-50924\n MUS-0996-71712\n ALN-0496-10819\n TEM-0895-72227\n BUF-0895-11662\n SAM-0895-20499\n \n AMA-0695-70804\n HIN-0701-42680\n HUN-0501-21203\n LEX-0201-41741\n \n \n Reporting Site: Salem\n Upstate New York HCS\n Muskogee\n Puget Sound HCS\n LAH-0301-61651 - LAB RESULTS FOR URINE NOT TRIGGERING ALERT\n Central Plains HCS\n OIFO San Francisco\n Mountain Home\n Fresno\n VA Greater Los Angeles HCS\n North Texas HCS\n Central Texas HCS\n Hines\n Albuquerque\n Phoenix\n Providers who had notification for lab results enabled were not\n Amarillo\n \n \n Test Site(s): Mountain Home\n Fresno\n VA Greater Los Angeles HCS\n Hines\n Phoenix\n Milwaukee\n \n receiving alerts for urinalysis. A line of code has been added at\n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n label SNEAK+39 in routine LR7OB3 to correct this problem.\n LR7OB3 12268913 12535845 **121,187,272**\n LR7OU4 11991663 12012587 **127,163,272**\n LR7OU5 12940594 13182116 **127,201,272**\n LR7OV4 5864196 5923833 **187,256,272**\n LRAC14 NEW 3263466 **272**\n LRACKL 13626594 13895634 **272**\n LRACKL1 2455270 2474094 **272**\n LRCKF 4058690 11756610 **272**\n LRCKF60 11681052 36215686 **272**\n LRCKF62 1728069 5812635 **272**\n \n LRCKF64 NEW 18720941 **272**\n LRCKF68 14560856 32159749 **272**\n LRCKF68A NEW 25765404 **272**\n LRCKF69 4913799 18312081 **272**\n LRCKFLA 9589815 39228904 **272**\n LRCKFLAA NEW 38310091 **272**\n LRCKPTR 10069312 15162494 **272**\n LRDIST1 14640547 15053872 **108,126,272**\n LRDRAW 8422619 8812401 **121,190,272**\n LRHDR 2828970 3185180 **272**\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \n HIN-0301-40344 - SPELLING NOTED\n LRMIHDR 7371024 7468554 **45,272**\n LRSORA2 3589912 3614713 **2,62,201,272**\n LRSORB 5246084 5387827 **272**\n LRWU1 3871530 4042564 **153,272**\n \nList of preceding patches: 45, 126, 153, 163, 187, 190, 201, 256\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n NOTE: The "before" checksums may not match for the LRAC14,\n LRACKL, and LARACKL1 routines if your site was a test\n The word "Finished" was misspelled in routine LRDRAW. The word\n site for the unreleased patch LR*5.2*170.\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n "Report Completed" has replaced "Finished". A report\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n header has been expanded to include the date and time.\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n \n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation should be\n done at off peak hours.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n ISF-0899-61570 - LAB FILES ALLOWING LAYGO TO FILE 200\n option 'Install Package(s)' Select the package 'LR*5.2*272'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\n The following fields were modified to not allow LAYGO in the\n NEW PERSON file (#200).\n \n LAB DATA (file #63)\nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n CHEM,HEM,TOX,RIA,SER,etc.(mult) (field #4)\n VERIFY PERSON (field #.04)\n \n LAB ORDER ENTRY (file #69)\n SPECIMEN (mult) (field #1)\n ENTERING PERSON (field #1)\n COLLECTOR (field #12)\n \n PHO-0699-61637 - QMONTH GIVING ORDER FOR EVERY DAY, NOT EVERY\n MONTH\n \n NTH-0399-71865 - QMONTHLY DOESN'T WORK WHEN ORDERING LABS IN CPRS\n The 30 day limit imposed by the MAX DAYS FOR CONTINUOUS ORDERS\n sub-field (#6) in the HOSPITAL SITE FIELD (#9) of the LABORATORY\n SITE file (#69.9) has been changed to allow up to 370 days.\n \n FRE-0599-60964 - IMMEDIATE COLLECT ALWAYS ON\n The IMMED COLLECT ON sub field (#8) of the IMMED LAB COLLECT DIV.\n multiple (#5.1) in the LABORATORY SITE file (#69.9) was not\n properly checked. The logic in the $$ON^LR7OV4 API has been\n changed to properly determine the status of this field.\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*272 does not \n \n CHY-0798-52175 - GRAPH RESULTS\n MOU-0498-32262 - PROBLEM WITH 0.0 VALUES ON QC DISPLAY\n Values such as 0.0 are not displaying using the Quality control\n display (Levey-Jennings) option. If the techs manually edit\n these values to 0, they will display on the graph. Changes have\n been made to allow 0.0 and 0 to display correctly.\n \n PUG-1297-50924 - OPTION REQUIRES LOWER CASE.\n The Fast Lab Test Order (Routine) [LROW ROUTINE] will not accept\nalter or modify any software design safeguards or safety critical \n lowercase answers. Changes have been made to line label % in\n routine LRORD1 to remove case sensitivity from this option.\n \n MUS-0996-71712 - NAT'L LAB TEST FILE LINKING SUBSCRIPT ERROR\n A Logic flaw in the lab code caused a National Lab Test file\n linking subscript error. All instances of the flawed code have\n been corrected.\n \n ALN-0496-10819 - SERUM ANTIBIOTIC LEVELS LESS THAN 1\n Sites were having problems putting in antibiotic levels in the\nelements functions.\n micro package that were less than 1.0. Results of .75 etc would\n echo question marks back to the user. Input transform located\n in the ANTIBIOTIC LEVEL field (#2)of sub-field of file (#63.42)\n located in the LAB DATA file (#63) has been corrected to allow\n results with 2 decimal places to be entered.\n \n TEM-0895-72227 - SEPARATE REPORT LOCATIONS NOT WORKING\n The site was instructed to put a prefix on their HOSPITAL\n LOCATION file (#44), so that they could differentiate after\n the integration. A problem arose when the cumulative used the\n \n abbreviation that was active at the time of the order. After\n integration the location names and abbreviations contained\n the prefix, which caused the names in the Lab globals to no\n longer match file (#44). This patch enables the printing of\n cumulative reports when multiple same name abbreviations have\n been detected in the LAB REPORTS file (#64.5).\n \n BUF-0895-11662 - USERS CHOOSE DEAD PROVIDER\n ALB-1099-52504 - LAB PACKAGE ALLOWS SELECTION OF TERMINATED USERS\n Users are able to choose a provider that recently died as the\n RISK ANALYSIS: Changes made by patch LR*5.2*272 have no effect on Blood \n person ordering the lab tests. Label P in routine LRWU1 has \n been modified to use the DISUSER flag to check for terminated\n users.\n \n SAM-0895-20499 - CHECK FILES FOR INCONSISTENCIES\n Warnings were printed even though the "DO YOU WANT WARNINGS\n REPORTED? No//" prompt was answered with NO. Extensive\n modifications have been made to the routines called by the\n Check files for inconsistencies [LRCHKFILES] option to correct\n this problem.\n\n
\nSee patch description for details.\n\n
\nThis patch is being released in support of the VBECS (Vista Blood \n exists (XTRCT^GMTSLRTE). The new API will pass\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n the DFN, the TMP subscript location, the inverse\n option 'Install Package(s)' Select the package 'LR*5.2*288'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\n end and inverse beginning date of search in a\n call to the existing routine.\n \n Get All Available Units\n AVUNIT^VBECA4 This API will be a shell to an API that already\n exists (XTRCT^GMTSLRBE). The new API will pass\n the DFN, the TMP subscript location, the inverse\n end and beginning date, and the max number of\nEstablishment Computer Software) Blood Bank Modernization Project. In \n records in a call to the existing routine.\n \n Blood Product Lookup for Surgery\n ^VBECA5A The VBECA5A API has been created to allow the\n Surgery package to convert the existing pointer\n fields used to list available Blood Products\n contained in the Blood Product file (#66), with a\n free text field. The transition of the Blood\n Bank system from the existing M based system to a\n .NET/SQL based system will eliminate the ability\nthe future, data will be transitioned from the existing M database to a \n of the Surgery package to access the Blood Product\n data using the current method.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*288 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*288 does not \nalter or modify any software design safeguards or safety critical \nelements functions.\nMicrosoft SQL database. The API's release in this patch will allow the \n \n RISK ANALYSIS: Changes made by patch LR*5.2*288 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \n DBIA: 3176-A\n 3176-B\n 3631\n \n Reference NOIS: None\n \nHealth Summary and Surgery packages to transition to the new database \n Reporting Site: None\n \n Test Site(s): Beckley, WV\n Durham, NC\n Puget Sound HCS\n San Diego, CA\n \n \nROUTINE SUMMARY\n===============\nwhen it is released.\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;0.5;VBECS;<patchlist>;APR 26, 2002\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n VBECA4 NEW 4083168 288\n VBECA5A NEW 790890 288\n \n \nList of preceding patches: None\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n Get Transfusion Data\n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n TRAN^VBECA4 This API will be a shell to an API that already\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n\n
\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*292 does not \nBank software functionality, therefore RISK is none.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)' Select the package 'LR*5.2*292'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\n \n \n The Blood Bank Report under the Reports tab in CPRS was hard coded to \ndisplay "Blood Bank" as the location of the unit if the unit has been \ncrossmatched and not dispositioned. \n \n Old Format:\n ---- BLOOD BANK ----\nABO Rh: O POS\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \n Antibodies identified: ANTI E; \n \n \n Unit assigned/xmatched: Exp date Loc\n 1) 04ABC CPDA-1 RED BLOOD CE O POS Apr 25, 2002 Blood Bank\n 2) 04ABC2 CPDA-1 RED BLOOD CE O POS Apr 25, 2002 5 DALLAS\n \n The report has been changed to display "BB-" and the institution that \nlogged the unit.\n \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n New Format:\n ---- BLOOD BANK ----\nABO Rh: O POS\n Antibodies identified: ANTI E; \n \n \n Unit assigned/xmatched: Exp date Loc\n 1) 04ABC CPDA-1 RED BLOOD CE O POS Apr 25, 2002 BB-Dallas CIOFO\n 2) 04ABC2 CPDA-1 RED BLOOD CE O POS Apr 25, 2002 5 DALLAS\n \n \n \n Reference NOIS: HEH-0702-41979\n \n \n Reporting Site: HEARTLAND-EAST HCS\n \n \n Test Site(s): HEARTLAND-EAST HEALTH CARE SYSTEM\n \n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*292 does not \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n \nalter or modify any software design safeguards or safety critical \n LR7OSBR1 22601409 22738094 121,201,228,\n 230,292\n \nList of preceding patches: 121,201,228,230\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \n Installation Instructions:\n ==========================\n \nelements functions.\n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n RISK ANALYSIS: Changes made by patch LR*5.2*292 have no effect on Blood \n Transport global.\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation should be\n done at off peak hours.\n 5. No options need to be placed out of service.\n\n
\nLAB RESULTS REPORTING LR*5.2*283\n ENHANCEMENT\nreport which lists the performing lab name, address and site code. This option \nwill print interim reports for a selected patient within a given time period. \nThe printout will go inverse date order. This report will output all tests \nfor the time period specified. This option will only print verified results. \n ROUTINE: CUM^LRRP2\n \n \nNAME: LRAC PT MENU TEXT: Reprint cumulative on a given patient\n TYPE: run routine\n DESCRIPTION: THIS OPTION PRINTS IN THE INTERIM REPORT FORMAT. The report \n\nprints site codes for tests and prints a separate page(s) at the end of the \nreport which lists the performing lab name, address and site code. This option \nwill print interim reports for a selected patient within a given time period. \nThe printout will go inverse date order. This report will output all tests \nfor the time period specified. This option will only print verified results.\n ROUTINE: CUM^LRRP2\n \n \nNAME: LRAC LOC MENU TEXT: Reprint cumulative on a given location\n TYPE: run routine \nDescription:\n DESCRIPTION: THIS OPTION NOW PRINTS IN THE INTERIM FORMAT. The report \nprints site codes for tests and prints a separate page(s) at the end of the \nreport which lists the performing lab name, address and site code.\n This option reports all verified results from one location for one day.\n ROUTINE: CUMSGLE^LRRS \n \n \nNAME: LRAC LOC-LOC MENU TEXT: Reprint cumulative from location to \nlocation\n TYPE: run routine \n===========\n DESCRIPTION: THIS OPTION PRINTS IN THE INTERIM REPORT FORMAT. The report\nprints site codes for tests and prints a separate page(s) at the end of the\nreport which lists the performing lab name, address and site code.\nDetailed report format for all data for one day sorted by location. This option\nwill only print verified results. The date chosen for this report is the\ncollection date. If a test is ordered on one day and verified on the next \nday,you must select the order date to see the report with this option.\n ROUTINE: CUM^LRRS\n \n \n\nNAME: LRAC 1 PAGE MENU TEXT: Reprint a permanent page from cumulative\n TYPE: run routine \n DESCRIPTION: THIS OPTION PRINTS IN THE INTERIM REPORT FORMAT. The report\nprints site codes for tests and prints a separate page(s) at the end of the\nreport which lists the performing lab name, address and site code.\nThis option will print interim reports for a selected patient within a \ngiven time period. The printout will go inverse date order. This report will \noutput all tests for the time period specified. This option will only print \nverified results. \n ROUTINE: CUM^LRRP2 \n *************************************************************************\n \nNAME: LRAC MANUAL MENU TEXT: Manual queuing of cumulative\n TYPE: run routine \n DESCRIPTION: THIS OPTION PRINTS IN THE INTERIM REPORT FORMAT. The \nreport prints site codes for tests and prints a separate page(s) at the end\nof the report which lists the performing lab name, address and site code.\nThis option will print interim reports for a selected patient within a \ngiven time period. The printout will go inverse date order. This report will \noutput all tests for the time period specified. This option will only print \nverified results. \n KERNEL PATCH XU*8*217 MUST BE INSTALLED BEFORE LR*5.2*283\n ROUTINE: CUM^LRRP2\n \nNAME: LRAC FULL PATIENT SUMMARY MENU TEXT: Print a full patient summary\nTYPE: run routine \nDESCRIPTION: Prints a full patient summary using the interim report \nformat. It simply captures all lab data on a patient and prints the performing\nlab sites and addresses on a separate page(s). \nROUTINE: SUM^LRACM2\n \n \n *************************************************************************\nNAME: LRRD MENU TEXT: Interim report by provider\nTYPE: run routine \nDESCRIPTION: This option is used to obtain all data on one day for \nselected providers. All providers may be selected or a range of providers \n(this may be helpful if obtaining reports for all providers but you wish to \nsplit the load between multiple printers). Multiple selections are allowed for\nselecting specific providers. All reports are sorted by provider name. If no \nresults are available for a provider, the option will print the provider's name\nfollowed by the next provider's name. This option is an alternative to \nhaving the Interim report tasked to the taskmanager. Only verified results will\n \nbe printed. This option is not part of the cumulative report and should not \nbe charted. The date chosen for this report is the collection date. If a \ntest is ordered on one day and verified on the next, you have to select the \norder date to see the report. The report prints site codes for tests. \nYou will be asked if you would like to print an address page. The address page\nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code. \nROUTINE: LRRD\n \n \nThis patch to the Laboratory package does not contain any changes to the \nNAME: LRRD BY MD MENU TEXT: Interim reports for 1 provider (manual queue)\nTYPE: run routine \nDESCRIPTION: This option reports all verified results for one day for \none provider. The user will request the date and provider. This option will \nonly print verified results. The date requested should be the date the lab \nwork was collected. This option is to be used for information only and should \nnot be charted. The report prints site codes for tests. \nYou will be asked if you would like to print an address page. The address page\nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code. \n\nVISTA BLOOD BANK Software as defined by the VHA DIRECTIVE 99-053 titled \nROUTINE: SINGLE^LRRD\n \n \nNAME: LRRP3 MENU TEXT: Interim report for chosen tests\nTYPE: run routine \nDESCRIPTION: This report will display results in inverse date order. \nThe option allows the user to select a specific test or panel of tests for a\n specified time period. Regardless of whether the orders have been purged, \nthe results may be displayed. The report should not be charted. The report\nprints site codes for tests. \nVISTA BLOOD BANK SOFTWARE VERSION 5.2.\nYou will be asked if you would like to print an address page. The address page\nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code. \nROUTINE: LRRP3\n \n \nNAME: LRRP2 MENU TEXT: Interim report \nTYPE: run routine \nDESCRIPTION: This option will print or display interim reports for a\nselected patient, within a given time period. The printout will go in \n \ninverse date order. This report will output all tests for the time period \nspecified. If no results are available, the option will ask for another \npatient. This option will only print verified results. The report prints\nsite codes for tests. \nYou will be asked if you would like to print an address page. The address page\nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code. \nROUTINE: LRRP2 \n \n \nThe purpose of the LAB RESULTS REPORTING patch, LR*5.2*283, is to enhance\nNAME: LRRS MENU TEXT: Interim reports by location (manual queue)\nTYPE: run routine \nDESCRIPTION: Detailed report format for all data for one day sorted by\nlocation. This option is an alternative to having the Interim report \ntasked to the taskmanager. For tasking, see option LRTASK DAILY INTERIM 1. If \nno results are available for a location, the option will print out the \nlocation heading followed by the next location heading. This option will only \nprint verified results, is not part of the cumulative report and should not be\n charted. The date chosen for this report is the collection date. If a \ntest is ordered on one day and verified on the next day, you must select the \nthe VistA Laboratory software to print the name and address of the laboratory\norder date to see the report with this option. The report prints site codes\nfor tests. \nYou will be asked if you would like to print an address page. The address page\nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code.\nROUTINE: LRRS12\n \n \nNAME: LRRSP MENU TEXT: Interim report for selected tests as ordered\nTYPE: run routine \nthat performed a test procedure on patients' laboratory reports. Currently\nDESCRIPTION: Detailed report format for an individual patient. Report \nis done for selected tests as they are ordered. If the orders have been \npurged, the results will not be found because the result look-up is dependent \non the orders. This option allows the user to select a specific test or panel, \nor select the "ANY" test default which will output all the verified tests for\nthat patient during the time period specified. If no results are available,\nthe option will ask for another patient. This option will only print \nverified results and should be used for information only. The option should\nnot be charted. The report prints site codes for tests. \nYou will be asked if you would like to print an address page. The address page\nthe physical address of the laboratory where the test is performed is not \nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code.\nROUTINE: LRRSP \n \n \nNAME: LRRS BY LOC MENU TEXT: Interim reports for 1 location (manual queue)\nTYPE: run routine \nDESCRIPTION: This option reports all verified results from one location \nfor one day. The user will request the date and location. This option will \nonly print verified results. This option is to be used for information only \nprovided on laboratory reports, which is a Joint Commission on \nand should not be charted. The report prints site codes for tests. \nYou will be asked if you would like to print an address page. The address page\nprints on a separate page(s) at the end of the report and lists the performing\nlab name, address and site code.\nROUTINE: SINGLE^LRRS\n \nNAME: LRTASK CUM MENU TEXT: TASK THE CUMULATIVE TO RUN EACH NITE\n TYPE: run routine \n DESCRIPTION: THIS OPTION NOW PRINTS IN THE INTERIM REPORT FORMAT. The\n report prints site codes for tests and prints a separate page(s) at the \nAccreditation of Healthcare Organizations (JCAHO) and College of American \nend of the report which lists the performing lab name, address and site code. \nThis function is automatically run by the TaskManager. This is the daily \ninterim cumulative report. \n ROUTINE: AIDQ^LRRP2 \n SCHEDULING RECOMMENDED: YES\n \n \nTesting Sites:\n==============\nDetroit VAMC\nPathologists (CAP) deficiency. This patch will resolve any existing data\nLittle Rock VAMC\nAsheville VAMC\nBay Pines VAMC\nMuskogee VAMC\nVISN 2\n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\nAssociated patches: (v)LR*5.2*201 <<= must be installed BEFORE `LR*5.2*283'\nquality issues concerning the lack of the performing laboratory name and\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n \n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR283 N/A 4564779 283 (Deleted by KIDS)\n LRACM2 9935205 10300781 201,283 \n LRMIPC 4251892 4206392 121,283\naddress on patient's reports therefore bringing VA laboratories\n LRMIPSZ1 12406819 12393254 283 \n LRRD 8518201 8109636 221,283\n LRRK 5712336 5740293 283\n LRRP 11856365 11838355 195,221,283\n LRRP1 7638502 8015031 153,221,283\n LRRP2 14561533 15278779 106,121,221,283\n LRRP3 8171424 8443889 283\n LRRS 8707990 8838761 283\n LRRS12 3898956 3814610 1,283\n LRRSP 3969248 4067808 121,283\ninto compliance with JCAHO and CAP standards.\n LRVER4 18527473 19639169 14,42,112,121,140,171,\n 153,188,279,283\n LRVER5 14580554 14564045 42,153,283\n LRVR4 8664360 8885386 14,42,121,153,221,263,279,283\n LRVR5 11729747 11950773 1,42,153,263,283\n \n Sites should use CHECK^XTSUMBLD to verify checksums.\n \nASSOCIATED NOIS:\n================\n\n \nTUC-1101-60420\nFGH-0401-32373\nVAC-0401-21831\nALB-1298-50579\nAMA-1198-70074\nGNH-0298-42213\nHVH-1097-11793 \nSTX-1101-70707\n \nAll Cumulative and Interim Reports are modified to include the\n When users select the Interim report for selected tests as ordered\n [LRRSP] option and enters a patient who requires a means test an undefined \n variable error occurred. This undefined variable I at BEGIN in routine LRRSP\n has been fixed. \n \nASSOCIATED NOIS:\n================\n \nSBY-0301-31020\nTOG-0101-12404\nperforming lab site (PLS) name and address information in the body of the\nMOU-0101-30818\nDAY-1197-40980\nASH-1100-30244\n \nThe Interim reports by location (manual queue) [LRRS] option does not \noperate properly when "Selected Locations" are selected. No output is \nproduced. This problem is fixed.\n \nASSOCIATED NOIS:\n================\nreport. The performing lab site for each test is noted by the internal\n \nWPB-0100-32328\nSLC-1299-51576\nSFC-1299-60391\n \n A problem with Interim report by provider [LRRD] option which prints numerous\n provider name pages equal to the number of days the report is queued to\n print when printing a hard copy is fixed. The provider name in large \n letters pages are no longer printed.\n \n entry number of the performing lab site in the INSTITUTION file (#4).\nASSOCIATED NOIS:\n================\n \nIOW-0897-20334\nPUG-0198-52088\n \n**********************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\nAll Cumulative Report options are modified to the interim report format and\n \n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: Off peak hours when cumulative and interim \n reports are not running.\n \n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n\nwill include the address page(s) which will be printed at the end of the\n ***** Kernel patch XU*8.0*217 must be installed prior to this patch.*****\n This patch contains the physical location address fields and an\n option to edit these fields. Each site must assign the \n responsibility of data entry for the lab sites/institutions.\n The person(s) responsible should be assigned the Kernel \n IMF address edit [XUMF IMF ADD EDIT] option to edit the physical address.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n (v)LR*5.2*279 <<= must be installed BEFORE `LR*5.2*283'\nreport. Site codes are available for chemistry tests only. There will be\n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\nno site codes printed for microbiology or anatomic pathology tests at this\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\ntime because they are unavailable.\n \n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a Transport\n Global' option at this time. You may also compare the routines in\n your production account to the routines in the patch by using the\n 'Compare a Transport Global to Current System' option.\n \n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*283'.\n \n \n If prompted ' Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//' choose 'NO'.\n \n If prompted ' Want KIDS to INHIBIT LOGONs during the install? YES// '\n choose 'NO'.\n \n If prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\n \n********************\n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LR283 will be deleted after successful patch installation.\n \n \nBelow is an example of modified interim report format with the performing \nlab site names, addresses and site codes printed on a separate page:\n \nPrinted at: \n page 1\n (v)XU*8*217 <<= must be installed BEFORE `LR*5.2*283' \nDallas Medical Center (428) 123 Lancaster Dallas, TX 75050\n \nBLOW,BILLIE Report date: 04/25/2002 2:49 pm\n SSN: 213-12-5823 SEX: F DOB: 12/29/1956 LOC: 5N\n \n Provider: BEAR,GUMMY O\n Specimen: SERUM\nAccession [UID]: CH 0425 1 [0421150001]\n \n Specimen Collection date: 04/25/2002 14:48\n\n Test Name Result Units Ref. Range Site Code\n ANION GAP 9 L meq/L 10 - 22 [123]\n CAL OSM 276 mOsm/L 275 - 300 [428]\n CREATININE 1.1 mg/dL .8 - 1.2 [456]\n UREA NITROGEN 8 L mg/dL 11 - 24 [456]\n GLUCOSE 104 mg/dL 60 - 123 [428]\n Eval: This one has an interpretation.\n SODIUM 144 meq/L 135 - 145 [987]\n POTASSIUM 4.5 meq/L 3.8 - 5.3 [428]\n CHLORIDE 105 meq/L 100 - 108 [428]\nSubject: LAB RESULTS REPORTING\n CO2 30 meq/L 23 - 31 [428]\n CALCIUM 8.5 L mg/dL 9 - 11 [428]\n AMYLASE 65 IU/L 14 - 110 [428]\nComment: Demonstration purposes \n============================================================================\n KEY: "L"=Abnormal low, "H"=Abnormal high, "*"=Critical value\n \nBLOW,BILLIE 213-12-5823 04/25/2002 2:49 pm\n \n \n\n page 2\nBLOW,BILLIE 213-12-5823 04/25/2002 2:49 pm\n \nPERFORMING LAB SITES\n[123] Oklahoma City 713 East 13 OKC, OK 73113\n \n[456] Muskogee 500 Honor Heights Drive Muskogee, OK 74401\n \n[987] Lab Quest 624 Downtown Ave Somewhere, USA\n \nCategory: ROUTINE\n \n \nMODIFIED OPTIONS:\n================\n \nNAME: LRAC DISCHARGE MENU TEXT: Patient Lab Discharge Summary \n(Manual)\n TYPE: run routine \n DESCRIPTION: THIS OPTION PRINTS IN THE INTERIM FORMAT. The report \nprints site codes for tests and prints a separate page(s) at the end of the \n\n
\nVISTA Laboratory Package patch LR*5.2*274 contains no changes to software \n \n \nBelow is a listing of files exported by this patch, indicating if the \nimported file will contain additional data.\n \nFILE # NAME With Data \n----------------------------------------------\n \n64 WKLD CODE NO \n64.036 LAB DSS LAR EXTRACT NO\n64.2 WKLD SUFFIX CODES YES\n(2) This patch allows the user to manually encode CPT codes for a given \n64.21 WKLD CODE LAB SECT YES\n64.22 WKLD ITEM FOR COUNT YES\n64.3 WKLD INSTRUMENT MANUFACTURER YES\n64.81 LAB NLT/CPT CODES YES\n68 ACCESSION NO \n \n \nNote:\nThe LAB NLT/CPT CODES (#64.81) file is purged during the pre-installation \nphase. This file is only used to update THE WKLD CODE (#64) file and has \naccession. This method of CPT coding does not use the CPT codes \nno other purpose or function. This file will have no data after the post \ninstallation routine has successfully run to completion.\n \n====================== \nNew Fields:\n \nES DISPLAY ORDER(#26) field has been added to the WKLD CODE (#64) file. \nThis field is used by the LAB CPT BILLING option to display a pick list \nof those CPT codes defined by the NLT code. CPT codes can be selected by \nusing this number.\nassociated by the mapping of LABORATORY TEST file (#60) entries to WKLD \n \nPCE ENC # (#30) of ACCESSION NUMBER SUB-FIELD (#1) of ACCESSION (#68) \nfile has been added. This free text field contains a list of PCE Visit \nnumbers generated for this accession. If there are multiple visit numbers \nfor this accession they are separated by ';'. This field is only \npopulated if professional service PCE workload is generated. This is \nusually the type of PCE workload generated by the Pathologist reporting \nanatomic pathology services. PCE workload is only generated for those \nhospital locations with the type of clinic, module or other. \n \nCODE file (#64).\nNote:\nNo PCE workload is generated for inpatient locations.\n \n========================= \nModified Print Template:\n \nElectronic Catalog Print [LA7S PRINT CATALOG] option LA7S PRINT template \nhas been changed to display the LEDI HL7 (#.09) field instead of SNOMED \nCODE (#2) in TOPOGRAPHY FIELD (#61) field. The LEDI HL7 field is required \nby LEDI collecting sites when defining tests to be sent to the Host \n The user can select any appropriate CPT code(s) to identify the \nlaboratory and shipping manifest. The LEDI HL7 specimen must match the \nspecimen the HOST laboratory requires.\n \n==========================\nInput Template:\n Input Template [LR WKLD EDIT ALL] has been modified to allow editing of \nall user definable fields in the WKLD CODE (#64) file. Most notable is \nthat the LOINC CODE (#4) field of the TIME ASPECT (#30) sub-file of the \nWKLD CODE (#64) file. This template is very useful to delete or correct \nLOINC CODE entry in the WKLD CODE (#64) file.\nprofessional service(s) rendered during this particular tissue exam. The \n Input Template [LR WKLD ES CPT] is designed to allow quick editing of \nthe ES DISPLAY ORDER (#26) field and to edit all CODE (#18) sub-file \nentries. The CODE sub-file is where CPT CODE assignments are entered. \n \n=========================\n \nTest Sites: Muskogee, OK\n Long Beach, CA\n Durham, NC\n Lake City, FL\nuser can select from a pre-defined pick list or enter CPT codes \n Central Texas\n Gainesville, FL\n Boston, HCS\n St. Louis, MO\n \n \n========================= \nRoutine Summary:\n \n The following is a list of the routine(s) included in this patch. The\nindividually separated by commas ",".\n second line of each of these routine(s) will look like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \nRoutine Before After Patch\nName Patch Patch List\nLR274 N/A 6102494 274 (Deleted by KIDS)\nLR274PO N/A 9865530 274 (Deleted by KIDS)\n The pick list can be defined by editing the ES DISPLAY ORDER field \nLR274POA N/A 4193520 274 (Deleted after install)\nLRAPBK 12411722 13558720 51,72,201,274\nLRCAPES N/A 12983418 274\nLRCAPES1 N/A 8132160 274\nLRCAPFDS 9495229 9744247 105,119,127,163,274\nLRCAPPH1 11010117 11352750 127,136,138,158,263,264,274\nLRTT5P1 12439150 12768427 153,221,263,274\nLRTT5R1 6009458 6020078 153,201,274\nLRVER3A 10508599 10313641 1,5,42,100,121,153,190\n 221,254,263,266,274\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \n(#26) of the WKLD CODE file (#64). The number entered in the ES DISPLAY \n \n===========================\nRequired Patches:\nLR*5.2*163\nLR*5.2*201\nLR*5.2*263\nLR*5.2*264\nLR*5.2*266\nLR*5.2*258\n \nORDER field controls the order of CPT codes in the pick list. The \n========================= \nInstallation Instructions:\n \nThe patch LR*5.2*274 KIDS build file named LR52_274.KID stored in the \nASCII format can be obtained from the following Office of Information \nField Offices(OIFOs) ANONYMOUS SOFTWARE directories\nOIFO FTP Address Directory\nAlbany ftp.fo-albany.domain.ext anonymous.software \nHines ftp.fo-hines.domain.ext anonymous.software\nSalt Lake ftp.fo-slc.domain.ext anonymous.software\nnumerical order of the pick list uses the number entered in ES DISPLAY \n \n \nAll users may remain on the system.\n \nNote: The patch should be installed during off peak hours.\n \nNo laboratory background jobs need to be stopped. No options need to be\nplaced out of service.\n \nFrom the Kernel Installation & Distribution System (KIDS) menu \nORDER field for each WKLD CODE defined.\n \n 1. Use the 'Load a Distribution' option to load the \n LR52_274.KIDS file onto your system.\n 2. The patch has now been loaded into a Transport global\n on your system. You now need to use KIDS to install\n the Transport global.\n On the KIDS menu, under the 'Installation' menu, use \n the following options:\n Print Transport Global\n Compare Transport Global to Current System\n \n Verify Checksums in Transport Global\n Backup a Transport Global\n 3. Users may remain on the system, but installation \n should be done at off peak hours.\n 4. Installation time is less than 5 minutes during off \n peak hours and less than 15 minutes during peak hours.\n 5. Installation of this patch requires no additional \n memory space.\n 6. From the 'Installation Menu' of the KIDS menu, run the \n option\n(3) The NLT Mapped Code Search [LRCAP64S] option has been changed to \n 'Install Package(s)' Select the package 'LR*5.2*274' \n and proceed with the install.\n 7. When prompted 'Want KIDS to INHIBIT LOGONS during the\n install? YES//' respond NO.\n 8. When prompted 'Want to DISABLE scheduled Options, Menu\n Options, and Protocols? YES//' respond NO.\n \n \n======================\nExample of install:\ncorrectly respond to the following prompt at the end of each page:\n \nSelect Installation Option: INSTAll Package(s) \nSelect INSTALL NAME: LR*5.2*274 Loaded from Distribution \n7/11/02@09:42:27\n => LR*5.2*274 \n \nThis Distribution was loaded on Jul 11, 2002@09:42:27 with header of \n LR*5.2*274 \n It consisted of the following Install(s): \n LR*5.2*274 \n"Enter RETURN to continue or '^' to exit:"\nChecking Install for Package LR*5.2*274 \nWill first run the Environment Check Routine, LR274 \n \n \n Sending install started alert to mail group G.LMI \n \n --- Environment Check is Ok --- \n \nInstall Questions for LR*5.2*274 \n \n \nIncoming Files: \n \n 64 WKLD CODE \nNote: You already have the 'WKLD CODE' File. \n \n 64.036 LAB DSS LAR EXTRACT\nNote: You already have the 'LAB DSS LAR EXTRACT' File.\n \n 64.2 WKLD SUFFIX CODES (including data) \nNote: You already have the 'WKLD SUFFIX CODES' File. \n======================= \nI will OVERWRITE your data with mine. \n \n 64.21 WKLD CODE LAB SECT (including data) \nNote: You already have the 'WKLD CODE LAB SECT' File. \nI will OVERWRITE your data with mine. \n \n 64.22 WKLD ITEM FOR COUNT (including data) \nNote: You already have the 'WKLD ITEM FOR COUNT' File. \nI will OVERWRITE your data with mine. \n \n \nNew/Enhanced Options:\n 64.3 WKLD INSTRUMENT MANUFACTURER (including data) \nNote: You already have the 'WKLD INSTRUMENT MANUFACTURER' File. \nI will OVERWRITE your data with mine. \n \n 64.81 LAB NLT/CPT CODES (including data) \nNote: You already have the 'LAB NLT/CPT CODES' File. \nI will OVERWRITE your data with mine. \n \n 68 ACCESSION \nNote: You already have the 'ACCESSION' File. \n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES//NO\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO \n \nEnter the Device you want to print the Install messages. \nYou can queue the install by enter a 'Q' at the device prompt. \nEnter a '^' to abort the install. \n \n1. Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] option has been \nDEVICE: HOME// TELNET TO ALPHAS \n \n--------------------------------------------------------- \n Install Started for LR*5.2*274 : \n Jul 11, 2002@09:57:20 \n \nBuild Distribution Date: Jul 11, 2002 \n \n Installing Routines: \n Jul 11, 2002@09:57:20 \nenhanced to include the new field ES DISPLAY ORDER (#26) of WKLD CODE \n \n Running Pre-Install Routine: PRE^LR274PO \n \n Installing Data Dictionaries: \n Jul 11, 2002@09:57:26 \n \n Installing Data: \n Jul 11, 2002@10:01:18 \n \n Installing PACKAGE COMPONENTS: \n(#64) file. This option is used to print or edit fields in the WKLD CODE \n \n Installing PRINT TEMPLATE \n \n Installing INPUT TEMPLATE \n \n Installing OPTION \n Jul 11, 2002@10:01:19 \n \n Running Post-Install Routine: POST^LR274PO. . . . . . . . . . . . . . \n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . \n(#64) file. \n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . \n \n Building List Of Added WKLD CODEs \n \n List Of Added WKLD CODEs Complete \n \n Sending message to LMI Mail Group. \n \n Sending install completion alert to mail group G.LMI \n \n2. The new option LAB CPT BILLING [LRCAPES] has been created to provide \n Updating Routine file... \n \n Updating KIDS files... \n \n LR*5.2*274 Installed. \n Jul 11, 2002@10:05:28 \n \n LR*5.2*274 \n \n \nmanual CPT billing and laboratory workload capture. The LAB CPT BILLING \nInstall Completed \n \n \n \nInstallation of patch LR*5.2*274 started on Jul 11, 2002@09:56:20 \nInstallation of patch LR*5.2*274 completed on Jul 11, 2002@10:05:27 \n \nLIM:\n Review description for LR*5.2*274 use KIDS Utilities Build File Print \n \noption has no security key restriction. The option has been added to the \n \n End of installation example. \n ===============================================\n \n \nPost Install instruction:\n \nThe Laboratory Information Manager (LIM) should obtain from the Anatomic \nPathology department, a list containing CPT codes for the procedures most \nfrequently performed. The entries on this list need to be ranked by \nVerify/release menu, anat path [LRAPVR] option.\nfrequency (i.e. most frequently used procedure is #1, next frequently \nused procedure is #2, etc.) This list will provide a template for the \ndisplay listing. Next, the LIM need to select a NLT code from the WKLD \nCODE (#64) file with the corresponding CPT code. Next, using the option \nEdit or Print WKLD CODES[LR WKLD CODE EDIT PRINT] option, edit the ES \nDISPLAY ORDER (#26) field by entering the sequence number from the \nfrequency list and edit the CODE (#18) field multiple with the \nappropriate CPT Code(s). \nEditing of the WKLD CODE file can be done with the Edit or Print WKLD \nCODES [LR WKLD CODE EDIT PRINT] option.\n==================== \n The LAB CPT BILLING option can be used anytime after the accession \n \n================================================\nUser Information: \nThe user performing the CPT coding for tissue exam using the LAB CPT \nBILLING [LRCAPES] option can enter the ES DISPLAY ORDER number (the \nsequence number from the frequency list) to select CPT codes. The user \ncan enter double question marks '??' to see a list of CPT codes \nselectable by entering the ES DISPLAY ORDER numbers. If the appropriate \ncode does not appear on the list, the user can enter the individual CPT \ncode number(s) separated by commas.\nhas been created. If the accession has been purged, the option cannot be \n \nThe coding software ensures that all CPT codes selected are active. If \nthe user does not have the PROVIDER security key, a valid active provider \nmust be entered. The user reviews the accessioned test(s) and the CPT \ncodes selected. The user is prompted to accept or reject the information.\n \nAfter accepting the previous information the software will determine, \nusing the TYPE (#2) field of the HOSPITAL LOCATION (#44) file, if the \nlocation entered is an outpatient location. Those locations with the type \nof clinic, module or other are considered to be out patient location. CPT \nused. The LAB CPT BILLING option has two functions:\ncoding is ONLY PASSED FOR OUT PATIENT LOCATION TYPES. If the specimen is \nassigned to a Patient as defined by an entry in the PATIENT (#2) file, \nthe specified CPT codes are passed immediately to the Laboratory/PCE API. \nThe date/time of the visit is set to specimen collection date/time. If \nthe time is not specified, a default of 12:01 is used. The PCE API \nreturns the visit number which is stored in the PCE ENC (#30) field of \nthe ACCESSION NUMBER (#1) sub-file of the DATE (#.01) sub-file of the \nACCESSION (#68) file.\n \nThe software will also store the WKLD CODES associated with the CPT codes \n \nselected. These WKLD CODE are added to the Laboratory LMIP workload for \nthat accession. This is done regardless of the location type.\n \nExample of File setup\n===============================================================\n The example does not represent true clinical situation, it is used only \nfor demonstration purposes.\n \nLRMENU Laboratory DHCP Menu\nSelect Laboratory DHCP Menu Option: SUPervisor menu\n A. If the procedure was ordered on a patient from PATIENT (#2) file, \nSelect Supervisor menu Option: LAB LIaison menu\nSelect Lab liaison menu Option: LIM workload menu\nSelect LIM workload menu Option: EDIT\n 1 Edit ACC Area OOS Locations \n 2 Edit or Print WKLD CODES \nCHOOSE 1-2: 2 Edit or Print WKLD CODES\n \nDo you want to edit specific WKLD CODES/ALL fields? ? N// YES\n \nSelect WKLD CODE PROCEDURE: 88551.0000 Surgical Pathology Level I\nfrom a location that has TYPE (#2) of CLINIC, MODULE or OTHER as defined \n88551.0000\nPROCEDURE: Surgical Pathology Level I// (No Editing)\nDESCRIPTION:\n No existing text\n Edit? NO// \nPRINT NAME: ^CODE \nSelect CODE: CPT.88300\n \n Searching for a active CPT code., (pointed-to by CODE)\n Searching for a active CPT code.\nin the HOSPITAL LOCATION (#44) file, the user identified CPT codes will \n 88300 SURGICAL PATH, GROSS \n ...OK? Yes// (Yes)\n RELEASE DATE: T-1 (JUN 24, 2001)\n INACTIVE DATE: \n REPLACEMENT CODE: \n CODE NOTES:\n No existing text\n Edit? NO// \nSelect CODE: ^ES DISPLAY ORDER \nES DISPLAY ORDER: // 1\nbe passed to the Laboratory PCE API. If the PCE API accepts the passed \nSelect OPTION NAME: LRMENU Laboratory DHCP Menu\nSelect Laboratory DHCP Menu Option: Anatomic pathology\n ANATOMIC PATHOLOGY MENU\nSelect Anatomic pathology Option: Verify/release menu, anat path\nSelect Verify/release menu, anat path Option: ?\n RR Verify/release reports, anat path\n RS Supplementary report release, anat path\n LU List of unverified pathology reports\n CPT LAB CPT BILLING\n \ndata, the PCE ENC # (30) field of the ACCESSION NUMBER SUB-FIELD (#68.02 \n \nExample of CPT code capture.\n=============================================================\n \nSelect Verify/release menu, anat path Option: CPT LAB CPT BILLING\n \nSelect Accession: SURG\nSURGICAL PATHOLOGY \nSURGICAL PATHOLOGY\n Accession Date: TODAY// (NOV 06, 2002)\nof the DATE SUB-FIELD (68.01) of the ACCESSION (#68) file will be \n Number part of Accession: (1-999999): 3\n \n BRADY,MOM 389-24-0000 DOB: May 02, 1955\n Collection Date: Apr 17, 2002\n Acc #: NSP 02 3 UID: \n PCE ENC # 314;\n Specimen: \n Tissue Specimens: \n VAGINAL CANAL\n Test(s); SURGICAL PATHOLOGY LOG-IN/ \nPatch Description:\npopulated with the PCE visit number. CPT billing can be done multiple \n Releasing Pathologist\nPROVIDER: REV. GINSBURG,RONALD\n Ordering Location: : RED CLINIC \nWould you like to see PCE CPT Information? No// \nSelect CPT codes: ??\n \n List or range e.g., 1,3,5-7,88300.\n Select from the following or enter CPT separated by a comma\n \n 1 = 88300 LEVEL I - SURGICAL PATHOLOGY, GROSS EXAMINATION ONLY\ntimes for the same accession. \n Surgical Pathology Level I { NLT = 88551.0000 }\n \n 2 = 88302 LEVEL II - SURGICAL PATHOLOGY, GROSS AND MICROSCOPIC EX\n Surgical Pathology Level II { NLT = 88518.0000 }\n \n 3 = 88304 LEVEL III - SURGICAL PATHOLOGY, GROSS AND MICROSCOPIC E\n Surgical Pathology Level III { NLT = 88553.0000 }\n \n 4 = 88305 LEVEL IV - SURGICAL PATHOLOGY, GROSS AND MICROSCOPIC EX\n Surgical Pathology Level IV { NLT = 88555.0000 }\n \n \n 5 = 88307 LEVEL V - SURGICAL PATHOLOGY, GROSS AND MICROSCOPIC EXA\n Surgical Pathology Level V { NLT = 88557.0000 }\n \n 6 = 88309 LEVEL VI - SURGICAL PATHOLOGY, GROSS AND MICROSCOPIC EX\n Surgical Pathology Level VI { NLT = 88559.0000 }\n \n 7 = 88329 PATHOLOGY CONSULTATION DURING SURGERY;\n Frozen Section Add Cut { NLT = 88360.0000 }\nWould you like to see PCE CPT Information? YES\n B. The software will also capture the WKLD CODE(s) associated with the \n \nCPT: 88300 PATIENT NAME: BRADY,MOM\n VISIT: APR 17, 2002@12:01 PROVIDER NARRATIVE: SURGICAL \nPATH, GROSS\n QUANTITY: 1 ENCOUNTER PROVIDER: \nREV. GINSBURG,RONALD\n \nCPT: 88302 PATIENT NAME: BRADY,MOM\n VISIT: APR 17, 2002@12:01\n PROVIDER NARRATIVE: TISSUE EXAM BY PATHOLOGIST\nES DISPLAY ORDER number. This data will be captured as laboratory \n QUANTITY: 1 ENCOUNTER PROVIDER: \nREV. GINSBURG,RONALD\n \n \nSelect CPT codes: 1,2\n \n BRADY,MOM 389-24-0000 DOB: May 02, 1955\n Collection Date: Apr 17, 2002\n Acc #: NSP 02 3 UID: \n PCE ENC # 314;\nworkload. It will be reported based on the current LMIP workload \n Specimen: \n Tissue Specimens: \n VAGINAL CANAL\n Test(s); SURGICAL PATHOLOGY LOG-IN/ \n Selected CPT Codes\n (1) 88300 LEVEL I - SURGICAL PATHOLOGY, GROSS EXAMINATION ON\n Surgical Pathology Level I {88551.0000}\n (2) 88302 LEVEL II - SURGICAL PATHOLOGY, GROSS AND MICROSCOP\n Surgical Pathology Level II {88518.0000}\n \nreporting protocol.\nIs this correct ? Yes// YES\n Sending PCE Workload\n Visit # 314\n Storing LMIP Workload \n \nEnd of examples:\n \n======================================\n \n3. Electronic Catalog Print [LA7S PRINT CATALOG] option [LA7S PRINT] \ntemplate has been modified to display the LEDI HL7 (#.09) field of the \n \nTOPOGRAPHY FIELD (#61) file instead of the SNOMED CODE (#2) field. This \nis to assist LEDI collection sites with defining the LAB SHIPPING \nCONFIGURATION (#62.9) file.\n \n4. Print log book [LRAPBK] option has been enhanced to display a list of \nCPT codes passed to PCE for outpatients. This option can also be used to \nprovide a partial audit of CPT coding practices.\n \n=================\nRequired Patch List: LR*5.2*163\n(1) WKLD CODE (#64) file is updated with the latest released National \n LR*5.2*264\n LR*5.2*258\n LR*5.2*266\n=================\nNOIS: SAM-1102-20599\n BHS-0990-11616 \n \n=================\nFiles:\nThere are no new files contained in this patch. However the following \nLaboratory Test (NLT) codes.\nfiles will be updated with additional data.\n(1) WKLD CODE (#64) file will be updated with any missing National \nLaboratory Test (NLT) codes during the post installation phase. LAB \nNLT/CPT CODES (#64.81) contains a complete listing of NLT codes. WKLD \nCODE (#64) file is checked to determine if an NLT code should be added. \nIf the new NLT code is successfully added to WKLD CODE (#64) file or the \nNLT code already exists, the entry in LAB NLT/CPT CODES (#64.81) file is \ndeleted.\n \n \n \n(2) The TEST/PROCEDURE (#.01) field of the SPECIMEN # (#1) subfile of LAB \nORDER ENTRY (#69) file, input screen has been changed to allow the entry \nof LABORATORY TEST (#60) that have the TYPE (#3) field set to OUPUT. This \nscreen was changed in the software of an earlier released patch. The user \nshould see no difference in software behavior.\n \n \n(3) The DSS TEST NUMBER (#.01) field of the RESULT (#8) subfile of LAR \nDSS LAR EXTRACT (#64.036) file has been increased from 50 to 300 to \naccommodate patch ECX*3*47 number of tests to be extract.\n\n\nVISTA Laboratory Package patch LR*5.2*300 contains no changes to software\n \n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n2. NOIS MAN-1202-11246, PHI-1202-21644 reported an undefined variable\n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\nPNM in routine LRRP2 when printing laboratory cumulative reports via\n Backup a Transport Global\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*300. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES//', choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n \n Note: KIDS will disable the following options during patch\n installation:\noption TASK THE CUMULATIVE TO RUN EACH NITE [LRTASK CUM]. The undefined\n Interim report [LRRP2]\n Interim report by provider [LRRD]\n Interim report for chosen tests [LRRP3]\n Interim report for selected tests as ordered [LRRSP]\n Interim reports by location (manual queue) [LRRS]\n Interim reports for 1 location (manual queue) [LRRS BY LOC]\n Interim reports for 1 provider (manual queue) [LRRD BY MD]\n Reprint cumulative on a given patient [LRAC PT]\n Reprint a permanent page from cumulative [LRAC 1 PAGE]\n Manual queuing of cumulative [LRAC MANUAL]\nvariable is caused by the software attempting to print the list of\n TASK THE CUMULATIVE TO RUN EACH NITE [LRTASK CUM]\n \n \n 7. On a mapped system, rebuild your map set.\n \nNOTE: Routine LR300 will be deleted after successful patch installation.\n \n \n ************************************************************************\n Installation example:\nperforming laboratories after the reports had completed. The logic has\n \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*300 Loaded from Distribution 12/19/02@16:50:38\n => LR*5.2*300\n \nThis Distribution was loaded on Dec 19, 2002@16:50:38 with header of\n LR*5.2*300 \n It consisted of the following Install(s):\n LR*5.2*300\nbeen corrected to print the list with each interim report.\nChecking Install for Package LR*5.2*300\nWill first run the Environment Check Routine, LR300\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*300\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n3. NOIS SFC-1202-61678 reported an undefined variable LRIDT in routine\n \n \n Install Started for LR*5.2*300 :\n Dec 19, 2002@16:52:29\n \nBuild Distribution Date: Dec 19, 2002\n \n Installing Routines:...\n Dec 19, 2002@16:52:30\n \nLRRP2 when printing interim reports via option Interim Report [LRRP2].\n Running Pre-Install Routine: PRE^LR300.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No action required---\n \n *** Pre install completed ***\n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\nThe undefined variable is caused by the user aborting printing when\n Installing PACKAGE COMPONENTS:\n \n Installing OPTION............\n Dec 19, 2002@16:52:30\n \n Running Post-Install Routine: POST^LR300.\n \n *** Post install started ***\n \n --- No actions required for post install ---\nselecting starting and ending date ranges for the report. The software\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LR*5.2*300 Installed.\nwas not detecting user aborting. The logic has been corrected to return\n Dec 19, 2002@16:52:30\n \n Install Message sent #XXXXX\n \nSelect Installation Option:\nthe user to the select patient prompt when aborting from date range\nselection.\n \n \nASSOCIATED NOIS\n---------------\n BAY-1202-31189\n \n BUT-1202-21395\n CHA-1202-32023 \n CLL-1202-42133 \n COS-0103-40211 \n HOU-1202-72266 \n JAC-0103-70260 \n MAN-1202-11246\n MIW-0103-40485\n MON-1202-52048\n PHI-1202-21644\nPatch LR*5.2*300 corrects the following defects:\n PHO-1202-62145 \n PRO-1202-11453\n PUG-1202-51880\n SFC-1202-61678\n SPO-1202-51904\n TUA-0103-30226\n WIM-1202-21873\n \n\nTEST SITES\n \n----------\n Battle Creek VAMC\n Bay Pines VAMC\n Charleston VAMC\n Chillicothe VAMC\n Columbus OPC\n Heartland-West HCS\n Houston VAMC\n Indianapolis VAMC\n Jackson VAMC\n1. NOIS BAY-1202-31189, PRO-1202-11453, SFC-1202-61678 reported an\n Madison VAMC\n Manchester VAMC\n Milwaukee VAMC\n Philadelphia VAMC\n Phoenix VAMC\n Puget Sound HSC \n San Francisco VAMC\n Shreveport VAMC\n Spokane VAMC\n Wilmington VAMC\nundefined variable LRPRTPG in routine LRRP2 when printing laboratory\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\ninterim reports via CPRS. The variable LRPRTPG is now defined when a\n ------------ ------------ ----------- ------------\n LR300 N/A 4452251 **300** (Deleted by KIDS)\n LRRP2 15278779 13459970 **106,121,221,283,300**\n \n List of preceding patches: 283\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n************************************************************************\n \n \nuser selects to print interim reports via CPRS.\nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n\n
\nThis patch to the Laboratory package does not contain any changes to the \nTesting Sites:\n==============\n Long Beach VAMC\n\n \n ROUTINE SUMMARY\n ===============\n\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\nVISTA BLOOD BANK Software as defined by the VHA DIRECTIVE 99-053 titled \n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n \n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR298 N/A 2559378 298 (Deleted by KIDS)\n LRMIHDR 7468554 10376465 45,272,298\n\nVISTA BLOOD BANK SOFTWARE VERSION 5.2.\n ASSOCIATED NOIS:\n ================\n \n NONE\n \n**********************************************************************\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n\n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\nThis patch updates the Health Department Report to print the new Ethnicity \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \nand Race field. The routine LRMIHDR is modified to display or print the \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a Transport\n Global' option at this time. You may also compare the routines in\n your production account to the routines in the patch by using the\nnew ethnicity and race fields with the release of the scheduling patch, \n 'Compare a Transport Global to Current System' option.\n \n \n 8. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*298'.\n \n If prompted ' Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//' choose 'NO'.\n \n If prompted ' Want KIDS to INHIBIT LOGONs during the install? YES// '\nSD*5.3*254, and registration patch, DG*5.3*415\n choose 'NO'.\n \n If prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\n \n 9. On a mapped system, rebuild your map set.\n \n 10. Routine LR298 will be deleted after successful patch installation.\n\n\n
\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*293 does not \nBank software functionality, therefore RISK is none.\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation should be\n done at off peak hours.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\n \n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)' Select the package 'LR*5.2*293'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\n \n \n Some problems with the Check Files for Inconsistencies [LRCHKFILES] \noption were reported after the release of patch LR*5.2*272. This patch \nLR*5.2*293 will return the routines associated with this option to their \noriginal state with one exception. The call to the Blood Bank Inventory \nIntegrity Report [LRCKF^LRBLJI] has been removed from routine LRCKF.\n \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \n The call to the Blood bank inventory integrity report [LRBLII] option is \nbeing removed from the Check Files for Inconsistencies [LRCHKFILES] \noption. This is being done to further encapsulate the existing VistA \nBlood Bank system.\n \nNOTE: The Check Files for Inconsistencies [LRCHKFILES] option will no \nlonger run an integrity check on the Blood Bank files. You must manually \nrun the Blood bank inventory integrity report [LRBLII] option once this \npatch LR*5.2*293 has been installed.\n \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n Reference NOIS: ASH-0802-32526\n AUG-0802-32924\n HAM-0802-22943\n SDC-0802-62650\n FAV-0802-72445\n UNY-0502-12522\n \n \n Reporting Site: Ashevile, NC\n Augusta, GA\n \n Hampton, VA\n San Diego, CA\n \n \n Test Site(s): ASHEVILLE, NC\n AUGUSTA, GA (C)\n FAYETTEVILLE, AR\n HAMPTON, VA\n MADISON, WI\n SAN DIEGO, CA\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*293 does not \n \n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\nalter or modify any software design safeguards or safety critical \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LRCKF 11756610 4420888 **272,293**\n LRCKF60 36215686 11681052 **272,293**\n LRCKF62 5812635 1728069 **272,293**\n LRCKF68 32159749 14560856 **272,293**\n LRCKF69 18312081 4913799 **272,293**\n LRCKFLA 39228904 9589815 **272,293**\n LRCKPTR 15162494 10343721 **272,293**\n \nelements functions.\nList of preceding patches: 272\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n RISK ANALYSIS: Changes made by patch LR*5.2*293 have no effect on Blood \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n\n
\nUNDEF IN WORKLOAD ROUTINE\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*289 does not\nto be setup in the same panel, which can be in either a new panel or, an\nabout $55,000 per year per patient for preventing or delaying dialysis. This\ndoes not take into account the morbidity associated with dialysis that will\nbe prevented.\n \nRaye-Anne Dorn, National Tumor Registry Coordinator, has submitted a New\nService Request for the creation of a laboratory test, the estimated\nGlomerular Filtration Rate, eGFR. Thakor G. Patel, MD, Chief of Renal\nDiseases at Veterans Administration Central Office, endorses the request. The\nendorser is seeking an alternative to the creatinine clearance test, a\nlaboratory test that measures renal function and requires all urine collected\nexisting panel.\nover a 24-hour period. The request cites the difficulty of collecting such a\nspecimen, particularly from elderly patients. Additionally, the Veterans\nHealth Administration (VHA) Renal Program Office has recommended a standard\nprocess throughout VHA for performing and reporting the eGFR. The request is\nto release this locally created delta check as Class 1 software.\n \nThe four-variable MDRD Study equation is recommended. Although it has\nshort-comings, it has been more rigorously evaluated than the Cockcroft and\nGault equation, and performs better in patients with kidney disease, gives\nresults in units of ml/min/1.73 m^2, and does not require measurement of\n \nweight. Performance can be improved by calibration of the VA lab results\nwith the MDRD Study lab (Cleveland Clinic). Is there a VA "central lab,"\nthat other labs relate to? If so, it should be possible to "calibrate" that\nlab to the MDRD Study lab. (Of course, there is no Cockcroft Gault central\nlab, so calibration is an uncorrectable error with the use of the Cockcroft\nand Gault equation.)\n \nThe view is that it is difficult to interpret GFR values above about 60\nml/min/1.73 m^2, due to differences in creatinine calibration among labs, and\nuncertainty in the measurement of GFR in that range. This is the reason\n-----------------------------\nthat the NKF defined CKD Stage 3 as GFR <60, and that there are few\ndifferences in the action plan for CKD stages 1 and 2 (kidney damage and\nGFR either greater than or less than 90). It is important to instruct\npractitioners about the limitations of GFR estimates above 60.\n \nStages of chronic kidney disease (R, O). Among individuals with chronic kidney\ndisease, the stage is defined by the level of GFR, with higher stages\nrepresenting lower GFR levels.\n \n Table 12. Definition and Stages of Chronic Kidney Disease\nBackground\n \n GFR With Kidney Damage* Without Kidney Damage*\n __________________________ __________________________\nStages (mL/min/1.73^2) With HBP** Without HBP** With HBP** Without HBP**\n______________________________________________________________________________\n \n 1 >=90 1*** 1*** "High blood "Normal"\n pressure"\n------------------------------------------------------------------------------\n 2 60-89 2*** 2*** "High blood "eGFR"\n \n pressure with\n eGFR"\n------------------------------------------------------------------------------\n 3 30-59 3*** 3*** 3*** 3***\n------------------------------------------------------------------------------\n 4 15-29 4*** 4*** 4*** 4***\n------------------------------------------------------------------------------\n 5 <15(or 5*** 5*** 5*** 5***\n dialysis)\n______________________________________________________________________________\nChronic kidney disease is a major public health problem. Adverse outcomes of\n \n* Kidney damage is defined as pathologic abnormalities or markers of\n damage, including abnormalities in blood or urine tests or imaging\n studies.\n** High blood pressure is defined as >= 140/90 in adults and >90th\n percentile for height and gender in children.\n*** Represent chronic kidney disease; numbers designate stage of chronic\n kidney disease.\n \n May be normal in infants and in the elderly.\nchronic kidney disease can be prevented through early detection and treatment.\n \n \nTable 12 illustrates the classification of individuals based on the presence\nor absence of markers of kidney disease and level of GFR, according to \ndefinition and staging of chronic kidney disease proposed by this guideline.\nIn addition, it includes columns for the presence or absence of high blood\npressure, because of the complex relationship of high blood pressure and \nchronic kidney disease.\n \nAll individuals with GFR <60 mL/min/1.73 m2 for 3 months are classified as\nEarlier stages of chronic kidney disease can be detected through routine\nhaving chronic kidney disease, irrespective of the presence or absence of\nkidney damage. The rationale for including these individuals is that reduction\nin kidney function to this level or lower represents loss of half or more of\nthe adult level of normal kidney function, which may be associated with a\nnumber of complications (Part 6).\n \nAll individuals with kidney damage are classified as having chronic kidney\ndisease, irrespective of the level of GFR. The rationale for including\nindividuals with GFR 60 mL/min/1.73 m2 is that GFR may be sustained at normal\nor increased levels despite substantial kidney damage and that patients with\nlaboratory measurements.\nkidney damage is at increased risk of the two major outcomes of chronic kidney\ndisease: loss of kidney function and development of cardiovascular disease\n(Part 7).\n \n-----------------------------\nThe four-variable MDRD Study equation\n \nEstimated GFR (ml/min/1.73m^2)\n = 186 x (Scr)^-1.154 x (Age)^-0.203 x (0.742 if female) x (1.210 if\n African - American)\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n \n \n where:\n Scr = serum creatinine in mg/dL\n Age = age, in years\n \n("four-variable" (abbreviated) equation in Levey AS, JASN vol. 11:2000;\n abstract - A0828) (see below)\n \nA0828 F138 (PS)\n \nThe USRDS provides reliable nationwide data regarding the incidence, \nA. Simplified Equation To Predict Glomerular Filtration Rate from Serum\nCreatinine, Andrew S. Levey,(1) Tom Greene,(2) John W. Kusek,(3) Gerald J.\nBeck,(2) MDRD Study Group. (1) Boston, MA, (2) Cleveland, OH, (3) Bethesda,\nMD.\n \nWe recently developed and validated an equation to predict GFR from serum \ncreatinine (Pcr), which is more accurate than creatinine clearance measured\nfrom 24-hour urine samples or predicted from the Cockcroft-Gault (CG) equation\n(Levey AS, Ann Intern Med 1999; l30:877-884). GFR is expressed as ml/min/l.73\nm^2. Required variables include Pcr (mg/dl), age (y), race (black vs.\nprevalence, treatment patterns, outcomes, and cost of kidney failure treated \nnon-black), gender, serum urea nitrogen (SUN, mg/dl), and albumin (alb.g/dl).\nIn clinical practice and in retrospective studies, measurements of SUN and \nalb may not be available. Below, we list the full MDRD Study prediction\nequation (6 variables), as well as alternative prediction equations including\nfewer variables derived from measurements in the same 1628 patients.\n \n GFR = 170 x Pcr-0.999 x age -0.176 x 1.180 (if black)\n x 0.762 (if female) x SUN-0.170 x alb+0.318\n GFR = 270 x Pcr-l.007 x age -0.180 x 1.178 (if black)\n x 0.755 (if female) x SUN-0.169\nby dialysis and transplantation, the most severe stage of chronic kidney \n GFR = 186 x Pcr-l.154 x age -0.203 x 1.212 (if black)\n x 0.742 (if female)\n \nThe table below compares the performance of these equations and the CG\nequation.\n \n R 2 median A 75th % A 90th % A\n 6 variable .903 11.3 19.8% 28.4%\n 5 variables .899 11.6% 19.9% 29.4%\n 4 variable .892 12.1% 20.5% 29.7%\ndisease. This guideline provides a definition of chronic kidney disease as\n CG .842 13.8% 26.4% 40.5%\n \nA=absolute value of the median (50th), 75th and 90th percentiles of the\ndistribution of the differences between measured GFR and predicted GFR or Ccr\nfor each equation (includes bias correction for CG equation). We conclude\nthat simplified versions of the MDRD Study prediction equation provide more\naccurate estimates of GFR than measured or estimated creatinine clearance.\n \nExample of Screen:\n \nwell as definitions and estimates of prevalence of earlier stages of kidney\nACCESSION: CH 0205 3 CH 0205 4\n 2/5 12:01d 2/5 12:50d\nCREATININE //1.2\n \n (MISSING PARAMETER)\n \n ** eGFR: 74.6 \nVOLUME //932 \nELAPSED TIME //5.5 \nCOMPUTED CREATININE CLEARANCE //23 L\ndisease.\nCREATININE EGFR 74.6// \nSelect COMMENT: MISSING PARAMETER // \n COMMENT: MISSING PARAMETER // \nSelect COMMENT: \n \n ***************************************************************************\n * NOTE: *\n * If the patients race is 'Undeclared' or 'Unanswered', the COMMENT field *\n * will be populated with 'MISSING PARAMETER' text. The doctor will be able*\n * view this information within CPRS. The delta check will calculate the *\n \n * formula without the race variable. The doctor will need to evaluate this*\n * when viewing the reports in CPRS. *\n ***************************************************************************\n \n-----------------------------\nNew Fields\n \n There are four new fields: three TEST NAME FOR INPUT VALUEs (#60.1, #60.2,\n #60.3) and one TEST NAME FOR TEST OUTPUT VALUE (#61.1), which are stored in \n the file DELTA CHECKS (#62.1). The new fields are pointers to file LABORATORY\nChronic kidney disease is defined according to the presence or absence of \n TEST (#60). The new fields will be used by the delta check routine to get \n the DATA NAME (#400) field, which is a pointer to CHEM, HEM, TOX, RIA, SER, \n etc. DD File SUB-FIELD (#63.04). When the delta check routine is invoked, the \n routine calculates the eGFR from the test result, age, gender, and race. \n The results of the calculation are stored in the local array LRSB(DATA NAME).\n \n \n \nFile/Field Field Name Node;Piece Field Type\n-------------------------------------------------------------------------------\nkidney damage and level of kidney function-irrespective of the type of kidney \n62.1,60.1 TEST NAME FOR INPUT VALUE 1 5;1 POINTER TO LABORATORY TEST FILE\n (#60)\n \n LAST EDITED: SEP 24, 2002 \n DESCRIPTION: This field is a pointer to a test that will\n contain the result value of the first incoming\n test. The result value should be stored in the \n variable LRSB(X) - where X is the data name IEN\n from ^DD(63.04. \n \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\ndisease (diagnosis). Among individuals with chronic kidney disease, the stages\n \n62.1,60.2 TEST NAME FOR INPUT VALUE 2 5;2 POINTER TO LABORATORY TEST FILE\n (#60)\n \n LAST EDITED: SEP 24, 2002 \n DESCRIPTION: This field is a pointer to a test that will\n contain the result value of the second incoming\n test. The result value should be stored in the \n variable LRSB(X) - where X is the data name IEN\n from ^DD(63.04. \nare defined based on the level of kidney function. Identifying the presence\n \n \n62.1,60.3 TEST NAME FOR INPUT VALUE 3 5;3 POINTER TO LABORATORY TEST FILE\n (#60)\n \n LAST EDITED: SEP 24, 2002 \n DESCRIPTION: This field is a pointer to a test that will\n contain the result value of the third incoming\n test. The result value should be stored in the \n variable LRSB(X) - where X is the data name IEN\nand stage of chronic kidney disease in an individual is not a substitute for \n from ^DD(63.04. \n \n \n62.1,61.1 TEST NAME FOR OUTPUT VALUE 1 5;4 POINTER TO LABORATORY TEST FILE \n (#60)\n \n LAST EDITED: SEP 24, 2002 \n DESCRIPTION: This field is a pointer to a test that will\n contain the calculated value of the first\n outgoing test. The calculated value should be\naccurate assessment of the cause of kidney disease, extent of kidney damage, \n stored in the variable LRSB(X) - where X is the\n data name IEN from ^DD(63.04. \n \n-----------------------------\nThe eGFR delta check will need to be associated a new or existing Serum\nCreatinine test. The tests called EGFR and CREATININE (INCLUDES EGFR) will \nneed to be setup and then associated with the Serum Creatinine. \n \nExample of Laboratory Test Setup: (THIS IS A DISPLAY OF ENTRIES IN THE FILE,\nNOT A CAPTURED EXAMPLE OF A SETUP USING FILEMAN)\nlevel of kidney function, comorbid conditions, complications of decreased \n \nNAME: CREATININE,SERUM TYPE: OUTPUT (CAN BE DISPLAYED)\n SUBSCRIPT: CHEM, HEM, TOX, SER, RIA, ETC.\n LOCATION (DATA NAME): CH;689024;1 FIELD: DD(63.04,689024,\n HIGHEST URGENCY ALLOWED: ROUTINE COMBINE TEST DURING ORDER: YES\n PRINT NAME: CREAT DATA NAME: CREATININE-EGFR\nSITE/SPECIMEN: SERUM REFERENCE LOW: 0.7\n REFERENCE HIGH: 1.5 UNITS: mg/dl\n TYPE OF DELTA CHECK: EGFR LOINC CODE: 2160-0\nCOLLECTION SAMPLE: BLOOD MIN VOL (in mls.): .2\nkidney function, or risks for loss of kidney function or cardiovascular\n SINGLE DAY MAX ORDER FREQ: 1\nINSTITUTION: WASHINGTON ACCESSION AREA: CHEMISTRY\nVERIFY WKLD CODE: Creatinine VERIFY WKLD CODE #: 82565.0000\n CIS TEST CODE: CH017\nSITE NOTES DATE: JAN 17, 2002\n NOTE: Created per Raye-Ann Dorn. Part of Creatinine (Includes EGFR) panel.\n NATIONAL VA LAB CODE: Creatinine RESULT NLT CODE: Creatinine\n \n \nNAME: EGFR TYPE: OUTPUT (CAN BE DISPLAYED)\ndisease in that patient. Defining stages of chronic kidney disease requires \n SUBSCRIPT: CHEM, HEM, TOX, SER, RIA, ETC.\n LOCATION (DATA NAME): CH;689023;1 FIELD: DD(63.04,689023,\n HIGHEST URGENCY ALLOWED: ROUTINE PRINT NAME: EGFR\n DATA NAME: EGFR\nSITE/SPECIMEN: SERUM\nSYNONYM: ESTIMATED GLOMERULAR FILTRATION RATE\nSYNONYM: GLOMERULAR FILTRATION RATE\nINSTITUTION: WASHINGTON ACCESSION AREA: CHEMISTRY\nSITE NOTES DATE: JAN 17, 2002\n NOTE: Per Raye-Ann Dorn. Part of Creatinine (Includes EGFR) panel.\n"categorization" of continuous measures of kidney function, and the "cut-off \n \n \nNAME: CREATININE (INCLUDES EGFR) TYPE: BOTH\n SUBSCRIPT: CHEM, HEM, TOX, SER, RIA, ETC.\n LAB COLLECTION SAMPLE: BLOOD HIGHEST URGENCY ALLOWED: ROUTINE\n PRINT NAME: CR EGFR\nNUMBER: 1 LAB TEST: CREATININE,SERUM\nNUMBER: 2 LAB TEST: EGFR\nCOLLECTION SAMPLE: BLOOD\nINSTITUTION: WASHINGTON ACCESSION AREA: CHEMISTRY\nlevels" between stages are inherently arbitrary. Nonetheless, staging of \nSITE NOTES DATE: JAN 17, 2002\n NOTE: Per Raye-Ann Dorn. Includes CREATININE EGFR and EGFR with a delta\n check of EGFR.\n \n-----------------------------\nIf setting up the eGFR delta check, use FILEMAN to setup the new DELTA CHECK\nfields. The TEST NAME FOR INPUT VALUE 1 field (#60.1) and TEST NAME FOR OUTPUT\nVALUE 1 field (#61.1) are pointers to DATA NAME field (#400) of the LABORATORY\nTEST (#60) files. These fields will be needed to run the delta check.\n \nchronic kidney disease will facilitate application of clinical practice \nExample of Delta Check Setup: (THIS IS A DISPLAY OF ENTRIES IN THE FILE,\nNOT A CAPTURED EXAMPLE OF A SETUP USING FILEMAN)\n \nNAME: EGFR XECUTABLE CODE: D STRT^LREGFR(DFN,X)\n DESCRIPTION: Created 10/17/01 by SDV for Dr. TG Patel and Raye-Ann Dorn.\n Test is CREATININE-EGFR and its delta test is EGFR which Lon Paredes set and\n tested. On 08/01/2002, JAH modified and sent out as Class I software. \nSITE NOTES DATE: AUG 01, 2002\n TEST NAME FOR INPUT VALUE 1: CREATININE,SERUM\n TEST NAME FOR OUTPUT VALUE 1: EGFR\n \nguidelines, clinical performance measures and quality improvement efforts to \n \n-----------------------------\nSetting Up INPUT and OUTPUT VALUE\n \nUse FILEMAN to enter the INPUT and OUTPUT VALUE(s). These two pointers will\nstore the file LABORATORY TEST (#60) IEN in the file DELTA CHECKS (#62.1). \nThis information will be used to acquire the field DATA NAME (#400) for \nthe Laboratory test, which was setup to call the delta check routine. Below\nis an example of a session:\n \nthe evaluation, and management of chronic kidney disease.\n \nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n \nINPUT TO WHAT FILE: DISABILITY CONDITION// DELTA CHECKS\nEDIT WHICH FIELD: ALL// ??\n \n Choose from:\n .01 NAME\n 10 XECUTABLE CODE\n 20 OVERFLOW 1\n \n 30 DESCRIPTION (word-processing)\n 31 SITE NOTES DATE (multiple)\n 60.1 TEST NAME FOR INPUT VALUE 1\n 60.2 TEST NAME FOR INPUT VALUE 2\n 60.3 TEST NAME FOR INPUT VALUE 3\n 61.1 TEST NAME FOR OUTPUT VALUE 1\n FOLLOW A FIELD NAME WITH ';"CAPTION"' TO HAVE THE FIELD ASKED AS 'CAPTION:'\n OR WITH ';T' TO USE THE FIELD 'TITLE' AS CAPTION\nEDIT WHICH FIELD: ALL// 60.1 TEST NAME FOR INPUT VALUE 1\nTHEN EDIT FIELD: 61.1 TEST NAME FOR OUTPUT VALUE 1\n-----------------------------\nTHEN EDIT FIELD:\n \n \nSelect DELTA CHECKS NAME: EGFR \nTEST NAME FOR INPUT VALUE 1: CREATININE,SERUM//\nTEST NAME FOR OUTPUT VALUE 1: EGFR//\n \n \nASSOCIATED NOIS\n===============\nReasons for estimated Glomerular Filtration Rate (eGFR)\nN/A\n \n \nTEST SITES\n===============\nWashington D.C.\nVA Wilmington\nLong Beach VAMC Laboratory\nVAMHCS, PERRY POINT DIVISION\n \n \nROUTINE SUMMARY\n===============\n \nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n \n ;;5.2;LAB SERVICES;<patchlist>;Sep 27, 1994\n \n Checksum\nRoutine Old New 2nd Line\nIn February 2002, the National Kidney Foundation recognized the Glomerular\n-----------------------------------------------\nLREGFR n/a 2309496 **289**\n \n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n************************************************************************\n \n \nINSTALLATION INSTRUCTIONS\n=========================\nFiltration Rate as an indicator of renal function. The eGFR is calculated\n \nThe install time for this patch is less than five minutes. This patch can be\ninstalled when Laboratory users are on the system. Suggested time to install:\nnon-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid problems\nloading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\nrather than measured, and the Washington, DC Medical Center has developed a\n Information Manager (LIM/ADPAC).\n \n1. If any of the above routines are mapped, disable mapping for them.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n3. On the 'Kernel Installation & Distribution System' Menu (KIDS), select\n the 'Installation' menu.\n \nroutine known as a delta check that performs the calculation. The Washington\n4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nLR*5.2*289 is a mandated installation of the estimated Glomerular Filtration\ndelta check uses the serum creatinine result, age, and sex from the local\n6. Use the 'Install Package(s)' option under the 'Installation' menu and\n select the package LR*5.2*289. When prompted 'Want KIDS to INHIBIT\n LOGONs during the install? YES//' choose 'NO'. When prompted 'Want to\n DISABLE Scheduled Options, Menu Options, and Protocols?\n \n YES//', choose 'NO'.\n \n7. On a mapped system, rebuild your map set.\n \n*****************************************************************************\nVISTA Laboratory package. The new program will calculate the eGFR for African-\nAmericans and others according to the accepted calculation.\n \nIt is important to note that National Kidney Foundation's "Kidney Disease\nOutcomes Quality Initiative (K/DOQI) Clinical Practice Guidelines for Chronic\nKidney Disease: Evaluation, Classification, and Stratification" has stages of\nkidney disease based on eGFR and also action plan as per Guidelines 1 & 2.\nThese guidelines are published in the American Journal of Kidney Diseases Vol.\n39, No 2, supplement 1, February 2002.\nRate (eGFR) delta check routine. Site(s) can setup the two new laboratory\n \nAdverse outcomes of chronic kidney disease can often be prevented or delayed \nthrough early detection and treatment. Earlier stages of chronic kidney \ndisease can be detected through routine laboratory measurements. \n \n * The presence of chronic kidney disease should be established, based on \n presence of kidney damage and level of kidney function (glomerular \n filtration rate [GFR]), irrespective of diagnosis.\n \n * Among patients with chronic kidney disease, the stage of disease should \ntests, Creatinine (including eGFR) and eGFR, in either a new or an existing\n be assigned based on the level of kidney function, irrespective of \n diagnosis, according to the K/DOQI CKD classification Table 10. \n \n \n Table 10: Stages of Chronic Kidney Disease\n \n GFR\n Stage Description (mL/min/1.73m^2)\n_____________________________________________________________________\n 1 Kidney damage with >=90\nSerum Creatinine test. One of the new tests holds the input value (test \n normal or increasing GFR\n---------------------------------------------------------------------\n 2 Kidney damage with 60-89\n mild decreasing GFR\n---------------------------------------------------------------------\n 3 Moderate decreasing GFR 30-59\n---------------------------------------------------------------------\n 4 Severe decreasing GFR 15-29\n---------------------------------------------------------------------\n 5 Kidney failure <15(or dialysis)\nresult) and the other test holds the calculated output value. Both tests need\n_____________________________________________________________________\n \n Notes: Chronic kidney disease is defined as either kidney damage \n or GFR <60 mL/min/1.73m^2 for >=3 months. Kidney damage is defined \n as pathologic abnormalities or markers of damage, including \n abnormalities in blood or urine tests or imaging studies.\n \nVHA is probably one of the few organizations nationwide that has the potential\nto report eGFR whenever serum creatinine is done. This will help us identify\npatients with kidney disease early and take preventive action. We will save\n\n\nVISTA Laboratory Package patch LR*5.2*287 contains no changes to software\nA new field STORE DUPLICATE COMMENTS (#2.2) in PROFILE multiple (#68.23)\n\nNOTE: Routine LR287 will be deleted after successful patch installation.\n \n \n ************************************************************************\n Installation example:\n \n\n Select Installation Option: 6 Install Package(s)\n Select INSTALL NAME: LR*5.2*287 Loaded from Distribution 7/10/02@09:45:39\nof file LOAD/WORK LIST (#68.2) will determine if duplicate comments are\n => LR*5.2*287\n \n This Distribution was loaded on Jul 10, 2002@09:45:39 with header of\n LR*5.2*287\n It consisted of the following Install(s):\n LR*5.2*287\n Checking Install for Package LR*5.2*287\n Will first run the Environment Check Routine, LR287\n \n \nstored when processing results from a load/work list. When the Laboratory\n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*287\n \nIncoming Files:\n \n \n 68.2 LOAD/WORK LIST (Partial Definition)\nNote: You already have the 'LOAD/WORK LIST' File.\n \nresult verifying software is processing comments associated with a\nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nload/work list result, this field determines how duplicate comments are\nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LR*5.2*287 :\n Jul 10, 2002@10:08:09\n \nBuild Distribution Date: Jul 10, 2002\n \n Installing Routines:...\n Jul 10, 2002@10:08:09\nprocessed. If set to "NO" (default if no value) then a comment that\n \n Running Pre-Install Routine: PRE^LR287.\n \n Sending install started alert to mail group G.LMI\n \n *** Pre install started ***\n \n --- No action required---\n \n *** Pre install completed ***\nmatches a previously stored comment will not be stored with the result.\n \n Installing Data Dictionaries: ..\n Jul 10, 2002@10:08:09\n \n Installing PACKAGE COMPONENTS:\n \n Installing INPUT TEMPLATE..\n \n Installing OPTION.....\n Jul 10, 2002@10:08:09\nIf set to "YES" then the duplicate check is not performed and the comment\n \n Running Post-Install Routine: POST^LR287.\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\nis stored with the results irregardless if the comment already exists.\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LR*5.2*287 Installed.\n Jul 10, 2002@10:08:10\n \n Install Message sent #xxxxxx\nSetting it to "YES" will allow the handling of multiple line comments which\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\ncontain the same comment more than once and are still clinically significant.\n \nEdit the default parameters Load/Work list. [LRLLE DFT] option has been\nmodified to allow configuring this field.\n \n \nASSOCIATED NOIS\n---------------\n ALB-0602-52815 \n \n \n \nTEST SITES\n----------\n Albuquerque VAMC\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\nPatch LR*5.2*287 corrects a defect reported in NOIS ALB-0602-52815.\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR287 N/A 5220883 **287** (Deleted by KIDS)\n LRVR4 8885386 8885642 **14,42,121,153,221,263,279,283,287**\n \n List of preceding patches: 283\n Sites should use CHECK^XTSUMBLD to verify checksums. \nDuplicate comments were not being stored with results when verifying \n \n************************************************************************\n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\nautomated instrument or load work list data. This patch will allow the\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\nsite to specify on a load/work list basis whether duplicate comments\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \nwill be stored with lab results when verifying the accession.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*287. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n \n YES//', choose 'NO'.\n \n Note: KIDS will disable the following options during patch\n installation:\n Enter/verify data (auto instrument) [LRVR]\n Enter/verify data (Work list) [LRVRW]\n Enter/verify data (Load list) [LRVRW2]\n Edit the default parameters Load/Work list. [LRLLE DFT]\n \n 7. On a mapped system, rebuild your map set.\n\n
\nThis patch is being released in support of the VBECS (Vista Blood \n If none is on file, return NULL\nelements functions.\n \n RISK ANALYSIS: Changes made by patch LR*5.2*294 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \n DBIA: 3879-A\n 3879-B\n 3879-C 3181-A, 3181-D, and 3181-G\n 3181-A\n 3181-D\n \n 3181-G\n \n Reference NOIS: None\n \n Reporting Site: None\n \n Test Site(s): \n \n \nROUTINE SUMMARY\n Get ABO\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;0.5;VBECS;<patchlist>;APR 26, 2002\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n VBECA1 NEW 7650459 294\n VBECA1A NEW 1999149 294\n ABO^VBECA1 Retrieve the ABO for a patient DFN.\n VBECA3A NEW 6174129 294\n VBECA3B NEW 7215596 294\n \nList of preceding patches: None\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n If none is on file, return NULL\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n The site should answer "NO" to all three questions.\n \n Note: You may not receive all three prompts at your site. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n Get Rh\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n RH^VBECA1 Retrieve the Rh for a patient DFN.\n 7. Installation of this patch requires no additional memory\n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)' Select the package 'LR*5.2*294'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\n If none is on file, return NULL\n \nEstablishment Computer Software) Blood Bank Modernization Project. In \n Get RBC Antigens Present\n AGPRES^VBECA1 Retrieve the antigens previously found\n for the patient. If none are found,\n return empty array.\n \n Get Antibodies Identified\n ABID^VBECA1 Retrieve the antibodies previously found\n for the patient. If none are found,\n return empty array.\n \nthe future, data will be transitioned from the existing M database to a \n Get RBC Antigens Absent\n AGAB^VBECA1 Retrieve the absent antigens previously\n recorded. If none are on record, return\n empty array.\n \n Get Transfusion Reactions\n TRRX^VBECA1 Retrieve any previously recorded transfusion\n reactions. If none are on record, return\n empty array.\n \nMicrosoft SQL database. The API's release in this patch will allow CPRS \n Get Blood Bank Comments\n BBCMT^VBECA1 Retrieve blood bank comments on the patient.\n If none are on record, return empty array.\n \n Get Available Autologous Units\n AUTO^VBECA1 Return quantity and component class of units\n available. If none are on record return\n empty array.\n \n Get CPRS Report Data\nand the Lab packages to transition to the new database when it is \n DFN^VBECA3A The following fields are retrieved in\n support of the CPRS Blood Bank reports.\n CPRS^VBECA3B This API converts the arrays produced in\n VBECA3A into a single cohesive array for\n use by CPRS.\n \n Component Request\n 63.084,.01 (Blood Component Request)\n 63.084,.04 (Number of Units)\n 63.084,.03 (Request Date/Time)\nreleased.\n 63.084,.05 (Date/Time Units Wanted)\n 63.084,.09 (Requesting Person)\n 63,.084,.08 (Entering Person DUZ)\n \n Crossmatch Data\n 65,.01 (Unit ID)\n 65,.04 (Component)\n 65,.07 (ABO Group)\n 65,.08 (RH Type)\n 65,.06 (Expiration Date/Time)\n \n 65,.16 (Division)\n 65.03,.04 (Location) (Note: Most recent entry is\n reported here)\n \n Specimen Data\n 63.01,.01 (Date/Time Specimen Taken)\n 63.01,.03 (Date Report Completed)\n 63.01,.01 (Date/Time Specimen Taken)\n 63.01,10 (ABO Interpretation)\n 63.01,2.9 (DIRECT AHG INTERPRETATION)\n Get ABORh\n 63.01,2.1 (DIRECT AHG(POLYSPECIFIC))\n 63.01,2.4 (Anti-IgC)\n 63.01,2.6 (ANTI-COMPLEMENT)\n 63.01,11 (RH Interpretation)\n 63.01,6 (Antibody Screen Interpretation)\n 63.199,.01 (Specimen Comment)\n 63.01,2.91 (DIRECT AHG TEST COMMENT)\n 63.012,.01 (ELUATE ANTIBODY)\n 63.46,.01 (SERUM ANTIBODY)\n 63.46,.02 (ANTIBODY COMMENT)\n ABORH^VBECA1 Retrieve the ABO & Rh for a patient DFN.\n 63.48,.01 (ANTIBODY SCREEN COMMENT)\n \n \n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*294 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*294 does not \nalter or modify any software design safeguards or safety critical \n\n
\nThis patch is being released in support of the VBECS (Vista Blood \n LR7OR1 This routine provides an API for the retrieval of Lab\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n results for a patient. All references to the BB subscript\n 4. Users may remain on the system.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)' Select the package 'LR*5.2*301'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n (BLOOD BANK subfile #63.01) of the LAB DATA file (#63)\n be returned to the mapped set once the installation has run\n to completion.\n have been removed.\n \n LRDPA1 The retrieval of ABO data for a patient has been\n transitioned from direct global reads to the ABO^VBECA1\n API (DBIA 3181-B).\n The retrieval of RH factor data for a patient has been\n transitioned from direct global reads to the RH^VBECA1\nEstablishment Computer Software) Blood Bank Modernization Project. In \n API. (DBIA 3181-C)\n \n LRDPA2 The retrieval of Blood Bank Comments for a patient has\n been transitioned from direct global reads to the\n BBCMT^VBECA1 API (DBIA 3181-H).\n The retrieval of Antibodies Identified for a patient has\n been transitioned from direct global reads to the\n ABID^VBECA1 API (DBIA 3181-D).\n The retrieval of Transfusion Reactions for a patient has\n been transitioned from direct global reads to the\nthe future, data will be transitioned from the existing M database to a \n TRRX^VBECA1 API (DBIA 3181-G).\n \n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*301 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*301 does not \nalter or modify any software design safeguards or safety critical \nelements functions.\nMicrosoft SQL database. This patch will begin the Lab packages \n \n RISK ANALYSIS: Changes made by patch LR*5.2*301 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \n DBIA: 3181-B\n 3181-C\n 3181-D\n 3181-H\n 3181-G\n \ntransition to the new database.\n Reference NOIS: None\n \n Reporting Site: None\n \n Test Site(s): Durham VA Medical Center\n VA Long Beach Health Care System\n VA Boston Healthcare System\n Fayetteville, AR\n Fayetteville, NC\n Puget Sound HCS\n \n \n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;0.5;VBECS;<patchlist>;APR 26, 2002\n \n Checksum Checksum\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\nLR7OR1 13239118 13188168 121,187,219\n 230,256,301\nLRDPA1 6551829 6578701 1,153,201,301\nLRDPA2 5207196 7419799 301\n \nList of preceding patches: 1,121,153,187,201,219,230,256\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n Routine Area Affected\n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n \n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n\n
\nHIPAA Code Set Versioning project.\n \nSee patch LR*5.2*297 in the National Patch Module for complete \ninformation on this patch.\n\n
\nSee patch description for details.\n\n
\nInstallation of LR*5.2*301 (Released 9/15/03) has created a potential \npatient processing, this should initiate each facility's own internal \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the\n Transport global.\n On the KIDS menu, under the 'Installation' menu, use the \nprocesses for performing the actual antigen typing on all units. The \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\n hours and less the 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\npotential for patient harm is possible but the likelihood that such an \n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)' Select the package 'LR*5.2*310'\n and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\nevent actually occurred is low. As a precaution, a facility should \nreview transfusion records of any patients with an antibody that occurred \nsince the installation of LR*5.2*301 to ensure that proper antigen \ntesting did get performed.\n \n \nEmergency patch LR*5.2*310 is being released to restore the routines, \npatient safety issue. \nLR7OR1, LRDPA1 and LRDPA2 to their pre-patch LR*5.2*301 state. If you \nhave installed patch LR*5.2*301, because of the potential patient safety \nissues, is it recommended that you immediately install patch LR*5.2*310. \nDirective 2001-023 dictates it be installed within 24 hours for an \nEmergency patch.\n \nFor those sites that did NOT install LR*5.2*301, since it has now been \nmarked as "Entered In Error" in the Patch Module, LR*5.2*301 should not \nbe installed and is no longer available in the patch module. The sites \nthat did not install LR*5.2*301, MUST still install LR*5.2*310 even \n \nthough the routines before and after install remain the same. This is \nrequired because LR*5.2*310 will make a change to the 2nd line, adding \n310 to the patch list, which will be required in future patches.\n \n \n****************************************************************\n \nThe following checksums are for those sites that have installed \npatch LR*5.2*301. The Checksums Before Patch for sites that have not \ninstalled patch LR*5.2*301 will match the After Patch checksums listed \nAfter installation of patch LR*5.2*301, Blood Bank units that are \nbelow.\n \n****************************************************************\n \nROUTINE SUMMARY FOR SITES THAT HAVE NOT INSTALLED LR*5.2*301\n============================================================\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \npositive for an antigen that corresponds to a patient's antibody are not \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\nLR7OR1 13239118 13239118 121,187,219\n 230,256,310\nLRDPA1 6551829 6551829 1,153,201,310\nLRDPA2 5207196 5207196 310\n \n \nList of preceding patches: 1,121,153,187,201,219,230,256\ndetected by the Blood Bank Software during unit selection, unit \nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \nROUTINE SUMMARY FOR SITES THAT HAVE INSTALLED LR*5.2*301\n========================================================\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\ncrossmatch or unit issue. \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\nLR7OR1 13188168 13239118 121,187,219\n 230,256,310\nLRDPA1 6578701 6551829 1,153,201,310\nLRDPA2 7419799 5207196 310\n \n \nList of preceding patches: 1,121,153,187,201,219,230,256,301\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \n \nPatch LR*5.2*301 will no longer be listed in the second line of these \nroutines.\n \n Installation Instructions:\n ==========================\n \n NOTE: This KIDS install does not place any options out of service\n during the install and no user options are affected.\nBecause the patient's antibody is displayed on the screen during the \n If KIDS prompts:\n \n "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES// NO"\n "Want KIDS to INHIBIT LOGONs during the install? YES// NO"\n "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES// NO"\n \n The site should answer "NO" to all three questions.\n Note: You may not receive all three prompts at your site. \n\n
\nThis patch implements a request from DSS to expand the lab results \nsite/specimen entries to include feces as an additional choice. At \npresent the only two choices are blood and urine. The test "Occult \nBlood" is almost always performed on stool (i.e. feces) samples, \ntherefore feces is needed as a possible choice.\n\n
\nDescription:\nwithin the Autopsy, Cytology, Electron Microscopy, and Surgical Pathology \nThe following software and documentation files are exported as part of\nthis patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n LR_52_259.KID LR*5.2*259 KIDS build ASCII\n \nThe software files are available on one of the following OI Field Offices'\nANONYMOUS.SOFTWARE directories.\n \nsections for the Autopsy protocol, Standard Form 515 (SF 515), and \nAll sites are encouraged to use their FTP capability to obtain these files.\nUse the FTP address "download.vista.domain.ext" (without the quotes) to\nconnect to the first available FTP server where the files are located.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n ALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\n HINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\n SALT LAKE ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \nsupplementary reports. This new electronic signature functionality can be \n\n\n\nto activated or deactivated by the discretion of the site. The new Turn \nElectronic Signature On/Off [LRAP ESIG SWITCH] option is used to activate \nor deactivate the new electronic signature functionality. The electronic \nsignature functionality is activated during the verification/release \nprocess of the Autopsy and AP reports. \n\nPathologists may now view and electronically sign reports rather than \n===========\nprinting a paper copy for viewing and signature. The electronic signature \nname is obtained from the NEW PERSON file (#200), ELECTRONIC SIGNATURE CODE \nfield (#20.4). All electronically signed released reports are stored in TIU \ncontaining the electronic signature name, date, and time displayed on the \nlast page of the reports (near the bottom). Only authorized users are \nallowed to electronically sign reports. Non-authorized users will receive a \nmessage indicating that they are not authorized to electronically sign \nreports.\n\n \n\nASSOCIATED NOIS\n===============\nALB-0501-50221 e-sig for Surgical Pathology Report\nANN-1195-41047 Can release anatomic report without pathologist's \n name\nASH-0400-31745 CONFLICT LAB VS PATCH XU*8*134\nCHA-0601-30916 Anatomic Path result alerts\nDAY-0201-40571 LR*5.2*248 - Verification of AP Supplemental\nDET-0301-42098 Installed patch LR*5.2*248\nFTL-1000-52712 QUESTION \nThis patch to the Laboratory package does not contain any changes to the \nIND-0501-42474 Error when trying to delete supplemental report \n date\nJAC-0302-70436 Autopsy Reports\nLOU-0400-42255 Modified Report not showing \nMAN-0100-11108 Supplemental report changes completion date in AP\nMAN-0301-10830 MD DISPLAY ON PATH REPORTS \nMIN-0500-41991 PAP test limitations\nMIW-0497-40185 PROVIDER NAME OVER 30 CHARACTERS\nMOU-1101-32590 Autopsy type OTHER LIMITATIONS causes print problem\nMUS-0997-70156 Need to edit path date \nVISTA BLOOD BANK Software as defined by the VHA DIRECTIVE 99-053 titled \nPHI-0601-20384 Undefined variable [LRAPR\nPUG-0700-52652 Need view alert for anatomic path result\nSAM-0301-22193 SP REPORT FOOTER CONTAINS ADM: AND DX: TEXT FOR \n INPATIENTS\nSDC-1101-61043 AP Reports - MODIFIED report\nSHE-0499-50108 CPRS Interface with Anat Pathology for \n Notifications?\nSPO-0701-50733 Alert for pathology \nWIC-0899-42604 REVERIFY RE'D AFTER VIEWING ANAT'L REPORT\nWIC-1298-42147 Autopsy verification needs locked\nVISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \nE3R: 4892 NO SUPPLEMENTARY REPORT TO RELEASE' PROMPT\n 5572 ELECTRONIC SIGNATURE FOR AP\n 5995 SPECIMEN/DX FOR PATHOLOGIST VERIFICATION\n 5592 RELEASE DATE ADDED TO ANATOMIC PATHOLOGY REPORTS\n 6208 TECH TITLES\n 6566 ANATOMIC PATH VIEW ALERT\n 7059 CODING DOES NOT PRINT\n 7536 CHANGE PATHOLOGIST AFTER REPORT VERIFIED\n 9245 AUTOPSY RELEASE PROBLEM\n\n 9447 ANATOMICAL PATH ALERT IS NOT FUNCTION\n 9592 RELEASE DATE ADDED TO ANATOMIC PATHOLOGY REPORTS\n 12872 ELECTRONIC SIGNING ANATOMIC PATH RPT\n 14775 PATHOLOGY REPORT LOCK\n 15456 NEED ELECTRONIC SIGNATURE\n 15643 REQUEST CHANGES AFTER PATCH 248 \n 17034 AP REPORT FORMAT IGNORED BY CERTAIN CPRS DISPLAYS\n \n \nTEST SITES\nVISTA Laboratory Anatomic Pathology Electronic Signature (Patch LR*5.2*259) \n==========\n Bay Pines VAMC\n Boston HCS\n Desert Pacific Healthcare Network\n Durham VAMC\n Eastern Colorado HCS\n Jackson VAMC\n Milwaukee VAMC\n Muskogee VAMC\n North Chicago VAMC\nsoftware release implements the new electronic signature functionality \n North Florida/South Georgia HCS\n Roudebush VAMC\n San Francisco VAMC\n VA Heartland East HCS\n VA Western New York HCS\n \n \nSOFTWARE RETRIEVAL:\n===================\n \n\n
\nCurrently, the Laboratory application contains functionality that will \n \nThe new patient name NEWPATIENT,JANE is not accepted.\n \nVISTA Laboratory Package patch LR*5.2*305 contains changes to software \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE. \nChanges include: NOT ALLOWING LAB TO ADD PATIENTS TO PATIENT FILE\n \nAll of the above changes have been reviewed by the VISTA Blood Bank \nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE \ncontrol functions.\n \nMost, if not all, sites are not using the functionality that allows a patient \nRISK ANALYSIS: Changes made by patch LR*5.2*305 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*305 does not \nalter or modify any software design safeguards or safety critical elements \nfunctions.\n \nPOTENTIAL IMPACT ON SITES: This patch contains changes to one routine and \none file identified in Veterans Health Administration (VHA) Directive \n99-053, group B listing. The changes have no effect in Blood Bank \nname to be added to the PATIENT (#2) file from the patient name prompt \nfunctionality or medical device control functions. There is no adverse \npotential to sites.\n \nSoftware Updates:\n----------------\nThe following code has been changed in routine ^LRDPA. Added Quit at the end\nof the first line in subroutine LAYG.\n \nFrom: \nLAYG ;Determine if DLAYGO is allowed on second pass.\nwithin Lab menu options. However, the functionality is in place and may be \n K DLAYGO S DIC(0)="EQMZ"\n Q:'$P($G(LRPARAM),"^",6)\n Q:'$D(LRLABKY)\n S DLAYGO=2 S DIC(0)="EQMZL"\n Q\nTo:\nLAYG ;Don't allow DLAYGO on second pass.\n K DLAYGO S DIC(0)="EQMZ" Q\n Q:'$P($G(LRPARAM),"^",6)\n Q:'$D(LRLABKY)\nused if the site has the ALLOW LAB TO ADD PATIENTS (#13) field of the\n S DLAYGO=2 S DIC(0)="EQMZL"\n Q\n \nDD Updates:\n-----------\nThe description of ALLOW LAB TO ADD PATIENTS field (#13) in the LABORATORY\nSITE file (#69.9) has been changed to indicate that field #13 is no longer\nfunctional, and the set code value '1' has been removed as a valid entry.\n \nFrom:\nLABORATORY SITE (#69.9) file set to 'Yes.' If this field is set to 'Yes',\n69.9,13 ALLOW LAB TO ADD PATIENTS 0;6 SET (Required)\n \n '1' FOR YES;\n '0' FOR NO; \n LAST EDITED: MAY 01, 1984 \n DESCRIPTION: If the Lab is allowed to enter patients into\n the system, this field must contain a 'Yes' entry. Only \n lab users with the LRLAB key will make the changes and \n only when using lab options. \n \nany patient name prompt will accept a new patient name, one that does not\nTo:\n69.9,13 ALLOW LAB TO ADD PATIENTS 0;6 SET (Required)\n \n '0' FOR NO; \n LAST EDITED: SEP 02, 2003 \n DESCRIPTION: This field is not functional. It is no longer \n used to allow Lab to add patients to the Patient file. \n \nTest Sites \n---------- \ncurrently exist in the PATIENT(#2) file, if the new patient name is entered\nMuskogee, OK\nBoston HCS\nCheyenne VAMC\nColumbus VAMC\n \n ROUTINE SUMMARY: \n =================\n The following routine(s) are included in this patch. The second line\n of each routine now looks like: \n \ntwice. See the example below:\n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n LR305 N/A 5010875 **305** (Deleted by KIDS)\n LRDPA 7837880 7840899 **137,121,153,202,211,248,305** \n \n Installation Instructions: \n ==========================\n \n Users may remain on the system, but installation should be done at off\n peak hours. No options need to be placed out of service. Installation \n time is less than 1 minute during off peak hours and less than 5 minutes\n during peak hours. Installation of this patch requires no additional \n memory space.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n \n 2. Review your mapped set. If the routines are mapped, they \nallow the user to add a new patient to the PATIENT (#2) file from within \nSelect Laboratory DHCP Menu Option: 1 Phlebotomy menu\n should be removed from the mapped set at this time\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n 4. On the Kernel Installation and Distribution System (KIDS) menu, select\n the 'Installation' menu. You may elect to use the following options:\n a. Print Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n d. Backup a Transport Global\n \n 5. When ready, select the Install Packages option (when prompted for the\n INSTALL NAME, enter 'LR*5.2*305'. \n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//',\n respond "NO".\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//', respond "NO".\n Add tests to a given accession.\n \n 8. If any routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\n \n 9. Using Fileman, verify that the ALLOW LAB TO ADD PATIENTS (#13) field \n of the LABORATORY SITE file (#69.9) is set to 'No.' If not, set it to\n 'No.' 'No' is the only setting allowed after patch installation.\n Add tests to an already existing order number.\n Delete entire order or individual tests\n Itemized routine lab collection\n Lab orders by collection type\n Lab test order\n List of lab orders not collected\n List of orders not collected (Long form)\nthe Laboratory Application. However, due to IT Service Request 20030306 \n Order/test status\n Print collection list/labels\n Print future collection labels\n Print single future collection label\n Receipt of routine lab collection from wards\n Test description information\n Ward lab menu ...\n \nSelect Phlebotomy menu Option: LAB TEST order\n \nPatient Identity Management Services and HDR (Health Data Repository) Pilot,\nSelect Patient Name: NEWPATIENT,JANE ?? <-- 1st try - Name does not exist so \n '??' displays\nSelect Patient Name: NEWPATIENT,JANE <-- 2nd try - Name is accepted as a \n new entry to the PATIENT(#2)\nfile.\n ARE YOU ADDING 'NEWPATIENT,JANE' AS A NEW PATIENT (THE 239TH)? No// Y \n(Yes)\n PATIENT SEX: F FEMALE\n PATIENT DATE OF BIRTH: 03121975 (MAR 12, 1975)\n PATIENT SOCIAL SECURITY NUMBER: 111223333\nit has been requested that all ancillary applications, including Laboratory\n PATIENT TYPE: ?\n PATIENT TYPE: TRICARE \n PATIENT VETERAN (Y/N)?: Y YES\n .\n .\n .\n \nA number of patient demographic fields are prompted before resuming the \nprompting of fields required for the LAB TEST ORDER [LROW] option. Most \noptions in Laboratory Service permit new patient names to be entered in the \nService, remove such functionality. For more information on this service\nformat shown above. Patch LR*5.2*305 was created to remove this \nfunctionality from within the Laboratory Service application. \n \nThe following two changes to existing functionality are included in this \npatch:\n \n 1. The ALLOW LAB TO ADD PATIENTS (#13) field of the LABORATORY SITE \n (#69.9) file has been modified so that it can no longer be set to\n 'Yes.' 'No' is now the only answer allowed.\n \nrequest, view the following link:\n 2. The patient name prompt in menu options within Laboratory Service, \n has been modified to no longer allow a new patient to be added to the \n PATIENT (#2) file from within Lab. See the example below:\n \nSelect Laboratory DHCP Menu Option: 1 Phlebotomy menu\n \n Add tests to a given accession.\n Add tests to an already existing order number.\n Add to collection list\n Delete entire order or individual tests\n \n Itemized routine lab collection\n Lab orders by collection type\n Lab test order\n List of lab orders not collected\n List of orders not collected (Long form)\n Order/test status\n Print collection list/labels\n Print future collection labels\n Print single future collection label\n Receipt of routine lab collection from wards\nhttp://vista.domain.ext/pas/ViewTrackingRecord.asp?RequestID=20030306\n Test description information\n Ward lab menu ...\n \nSelect Phlebotomy menu Option: LAB TEST order\n \nSelect Patient Name: NEWPATIENT,JANE ??\nSelect Patient Name: NEWPATIENT,JANE ??\nSelect Patient Name: NEWPATIENT,JANE ??\nSelect Patient Name:\n \n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*281 does not \nBank software functionality, therefore RISK is none. \nautomatically generated when your site does an automated or manual run and data is sent to Austin Automation Center. Six months of previous reports are kept as well as the current mo\n\n3) Sites now have the ability to capture and manipulate EPI data into a \nreport or spreadsheet-delimited format. A site can also add pathogens for local use and generate reports or capture data in a spreadsheet format for local use.\n\n4) Additional data will be sent to Austin. Including:\n LOINC codes\n Master Patient Index\n County and State for patient demographics\n MIC values\n \n The new Race and Ethnicity fields\n\n5) Provide the ability to capture 6 new pathogens:\n All Staphylococcus aureus (Reference #18)\n Methicillin-Resistant Staphylococcus aureus (MRSA)\n (Reference #19)\n Vancomycin-Resistant Staphylococcus aureus (VRSA)\n (Reference #20)\n Vancomycin-Resistant Coagulase Negative Staphylococci/Staph epi \n (VRSE)(Reference #21)\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made,\n All Streptococcus pneumoniae (Reference #22)\n All Enterococci (Reference #23)\n\n6) EPI is also enhanced to capture the approved newer Legionella Urinary Antigen test.\n\n7) A bug is fixed with the date handling for start and stop date.\n\n8) The new field PREVIOUS CYCLE (#19) in the Lab Search/Extract file(#69.5) contains a numeric entry which defines the number of previous cycles to search. These findings will be rep\n \nNEW OPTIONS:\nno specific validation requirements exist as a result of installation of this\nNAME: LREPI DELETE LOCAL PATHOGEN MENU TEXT: Delete Local Pathogen\n TYPE: run routine\nDESCRIPTION: This option allows deletion of local pathogens ONLY. \nNational pathogens CAN NOT be deleted.\n ROUTINE: DELETE^LREPIPI\n \nNAME: LREPI DELETE LOCAL REPORT\n MENU TEXT: Delete Local Report or Spreadsheet\n TYPE: run routine\n DESCRIPTION: This option allows you to delete local reports or local\npatch.\n spreadsheets. \n ROUTINE: DELETE^LREPIRS2\n \nNAME: LREPI ENTER/EDIT LOCAL PATH MENU TEXT: Enter/Edit Local \nPathogens\n TYPE: run routine\n DESCRIPTION: This option allows you to enter or edit local pathogens \ninto the LAB SEARCH/EXTRACT FILE (#69.5) These pathogens can be selected for the report/spreadsheet option. Local pathogens WILL NOT be transmitted to Austin.\n ROUTINE: LREPIPI\n \n***********************************************************************\nNAME: LREPI GENERATE REPORT/SP\n MENU TEXT: Lab EPI Generate Local Report/Spreadsheet\n TYPE: run routine\n DESCRIPTION: This new option is used to generate reports or spreadsheets for national EPI and local pathogen data. The job is automatically tasked after selecting the national EPI\nor spreadsheet. The report or spreadsheet can then be viewed on the screen or printed using the new LAB EPI Print Local Report/Spreadsheet option. Note: NO data is transmitted to Au\n ROUTINE: LREPIRS\n \nNAME: LREPI LOCAL PATHOGEN MENU MENU TEXT: Local Pathogen Menu\n TYPE: menu\n DESCRIPTION: This menu contains options to enter/edit and delete local pathogens. Also, it contains options to generate and print the local report/spreadsheet. \nDue to extensive historical data transmission requirements and mandated setups\nITEM: LREPI ENTER/EDIT LOCAL PATH\nITEM: LREPI DELETE LOCAL PATHOGEN\nITEM: LREPI GENERATE REPORT/SP SYNONYM: GEN\nITEM: LREPI PRINT REPORT/SPSHT SYNONYM: PRT\n \n \nNAME: LREPI PATHOGEN INQUIRY MENU TEXT: Pathogen Inquiry\n TYPE: run routine\n DESCRIPTION: This new option is used to inquire into the LAB\nSEARCH/EXTRACT file (#69.5) parameter description fields (i.e. INACTIVE:NO, LAG DAYS: 15, RUN DATE:ICT 07,2003, CYCLE:MONTHLY, PROTOCOL:LREPI, FOLLOW PTF:YES, REFERENCE NUMBER:23, and\nrequired for such, a phased installation and implementation of this patch will\n ROUTINE: INQUIRY^LREPIPI\n \nNAME: LREPI PRINT REPORT/SPSHT\n MENU TEXT: Lab EPI Print Local Report/Spreadsheet\n TYPE: run routine\n DESCRIPTION: This option allows you to print a report or spreadsheet \nthat was generated with the Lab EPI Generate Local Report/Spreadsheet. \n ROUTINE: LREPIRS2\n \nNAME: LREPI VERIFICATION REPORT\nbe utilized for release of this patch. The software download information will\n MENU TEXT: Print Detailed Verification Report\n TYPE: run routine\n DESCRIPTION: This option prints the Detailed Verification Report. This \nreport is automatically generated when your site does an automated or \nmanual run and data is sent to Austin Automation Center. Six months of \nprevious reports are kept as well as the current month for printing. \n ROUTINE: LREPIRP7\n\nMODIFIED OPTIONS:\nNAME: LREPI ENHANCE MANUAL RUN MENU TEXT: Lab EPI Manual Run (Enhanced)\nbe made available to sites attending one of the following national\n TYPE: run routine\nDESCRIPTION: This option is used ONLY to manually extract national EPI data\n and transmit to the Austin Automation Center (AAC). When this option is run,\n an EPI Summary Verification Report is generated and automatically sent to the\n EPI-Report mail group. Also, a Detailed Verification Report is generated and\n can be printed using the new Print Detailed Verification Report [LREPI\n VERIFICATION REPORT] option. This option has been RENAMED from Lab\n Search/Extract Manual Run (Enhanced) [LREPI SEARCH/EXTRACT ENHANCED MANUAL\n RUN] to EPI Manual Run (Enhanced) [LREPI ENHANCE MANUAL RUN] option. \n ROUTINE: LREPIRM\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \naudioconference calls:\n\nNAME: LREPI NIGHTLY TASK MENU TEXT: Lab EPI Nightly Task\n TYPE: run routine\n DESCRIPTION: The Lab Search/Extract Nightly Task option must be scheduled to\n run each night by TaskMan. This option will build a HL7 Message and send it\n the defined location specified in the EPI Protocols. \n ROUTINE: AUTO^LREPIRM SCHEDULING RECOMMENDED: YES\n\nNAME: LREPI PARAMETER SETUP MENU TEXT: Lab EPI Parameter Setup\n TYPE: ScreenMan\n \nDESCRIPTION: This option is used to define the search criteria along with\n additional information associated with the EPI extracts. This option only\n allows editing. You are not allowed to add local pathogens with this option. \n DIC {DIC}: LAB(69.5, DIC(0): AEMQ\n DR{DDS}: [LREPI9] DDSFILE: 69.5\n\nMODIFIED FILE:\n UP SEND DATA USER\n DATE SEC. COMES SITE RSLV OVER\n FILE # NAME DD CODE W/FILE DATA PTS RIDE\nTuesday, June 8 at 1:00 - 3:00 PM EST for VISNs 1-2-3-4-5-6 \n -------------------------------------------------------------------------------\n \n 69.5 LAB SEARCH/EXTRACT YES NO YES MERG YES NO\n \nThe VistA Laboratory EPI Rollup Modifications Technical and User Manual \n(i.e., LR_52_281_EPI_TUM.PDF) is available on the following Office of \nInformation Field Offices (OIFOs) ANONYMOUS SOFTWARE directories: \n \nOIFOs FTP ADDRESS DIRECTORY\nAlbany ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nThursday, June 10 at 3:00 - 5:00 PM EST for VISNs 7-8-9-10-11 \nHines ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSalt Lake City ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \nVistA Laboratory EPI Rollup Modifications Technical and User Manual is \nexported as part of Patch LR*5.2*281 in the following formats:\n \nFILE NAME CONTENTS FORMAT RETRIEVAL\n\nLR_52_281_EPI_TUM.PDF LR EPI Technical and User Manual BINARY\n \nTuesday, June 15 at 4:00 - 6:00 PM EST for VISNs 12-15-16-17-23 \nTesting Sites:\n==============\n Boston HCS\n Cincinnati VAMC\n Detroit VAMC\n Durham VAMC\n Manchester VAMC\n Togus VAMC\n \n ROUTINE SUMMARY\nWednesday, June 16 at 2:00 - 4:00 PM EST for VISNs 18-19-20-21-22 \n ===============\n \n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n \n \n Routine Name Before Patch After Patch Patch List\nThursday, June 17 at 2:00 - 4:00 PM EST for those unable to attend the other\n ------------ ------------ ----------- ------------\n LR281 N/A 4418686 281(Deleted by KIDS)\n LREPI 14217525 14182167 132,175,260,281\n LREPI1 10654552 11822436 132,157,175,260,281\n LREPI2 7199135 8491199 132,157,175,242,260,281\n LREPI2A NEW 7574864 281\n LREPI3 5462995 9184652 132,175,260,281\n LREPI5 NEW 2408593 281\n LREPIPH 5818757 6144410 260,281\n LREPIPI NEW 5220624 281\ncalls. \n LREPIRM 5260075 7566388 175,281\n LREPIRP 5973015 20442264 132,157,175,260,281\n LREPIRP1 NEW 15133552 281\n LREPIRP2 NEW 3729823 281\n LREPIRP3 NEW 29061422 281\n LREPIRP4 NEW 1812384 281\n LREPIRP5 NEW 11788836 281\n LREPIRP6 NEW 25502070 281\n LREPIRP7 NEW 17171829 281\n LREPIRP8 NEW 8376752 281\n\n LREPIRP9 NEW 4718 281\n LREPIRS NEW 8576522 281\n LREPIRS1 NEW 16664999 281\n LREPIRS2 NEW 22133542 281\n LREPIRS3 NEW 16290972 281\n LREPISRV 12552990 15211664 260,281 \n LREPISV1 NEW 4805594 281\n \n ASSOCIATED NOIS:\n ================\nThe VANTS telephone number is 1 800 767-1750 and the access code for all calls\n \n NONE\n \n E3Rs:\n =====\n \n N/A\n \n**********************************************************************\n \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nis 13143.\n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n \n\n 1. If any of the above routines are mapped, disable mapping for\n them.\n \n 2. Use the 'Load a Distribution" option to load the Host file on to your\n system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport \n global.\n \nThis patch will involve reseeding of the EPI databases for each site to allow\n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify \n that all routines have the correct checksums.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\nthe new data created by this patch to be captured. It is imperative each site \n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a \n Transport Global' option at this time. You may also compare the \n routines in your production account to the routines in the patch \n by using the 'Compare a Transport Global to Current System' \n option.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\nattend an audioconference prior to installation and implementation of\n and select the package 'LR*5.2*281'.\n \n If prompted ' Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//' choose 'NO'.\n \n If prompted ' Want KIDS to INHIBIT LOGONs during the install? \n YES// ' choose 'NO'.\n \n If prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\nLR*5.2*281.\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LR281 will be deleted after successful patch installation.\n\nINSTRUCTIONS FOR SEEDING THE HISTORICAL DATA:\n \nHistorical data must be gathered from October 1, 2000 through June 14, 2004. \n \nUse the Lab EPI Manual Run (Enhanced) [LREPI ENHANCE MANUAL RUN] option to run/\ngather and transmit 6 manual runs (consecutive runs) at a time.\n \n** Sites DO NOT transmit on June 16 or July 4 to avoid Austin Automation Center\n (AAC) capacity limitations. **\n \nBatch #1: October 1, 2000 -March 31, 2001\nBatch #2: April 1, 2001 - September 30, 2001\nBatch #3: October 1, 2001 - March 31, 2002\nBatch #4: April 1, 2002 - September 30, 2002\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*281 does not \nBatch #5: October 1, 2002 - March 31, 2003\nBatch #6: April 1, 2003 - September 30, 2003\nBatch #7: October 1, 2003 - March 31, 2004\nBatch #8: April 1, 2004 - June 14, 2004 \n \nSites will run 8 batches of reports. Each batch should contain 6 separate\nmonthly extracts which are tasked separately by month, i.e., OCT 2000, NOV\n2000, DEC 2000, JAN 2001, FEB 2001, MAR 2001 = 1 batch and will generate six\nseparate processing reports back to the station and transmit them over a five\nweek period June 10, 2004 - July 12, 2004.\nalter or modify any software design safeguards or safety critical\nYou do not have to wait for one monthly extract to run before starting the next\nin a batch.\nYou do not have to wait for one batch to complete running before queuing the\nnext batch.\nIf you receive any fatal errors and the monthly extract is rejected, you will\nneed to fix the error and retransmit that month. \n \nSites may transmit reports to AAC on evenings and weekends following this\nschedule:\n1. VISNs with odd numbers are asked to transmit batches on Tuesday & Thursday\nelements functions.\n during the PM hours and Saturdays.\n2. VISNs with even numbers are asked to transmit on Monday & Friday during the\n PM hours and Sundays.\n \n** NO Sites may transmit on June 16 or July 4 due to AAC limitations. **\n\n\nThe EPI Enhancement patch, LR*5.2*281, contains enhancements and \nmodifications to the Emerging Pathogens Initiative (EPI) software.\nThe enhancements and modifications included in this patch are:\n \n\n1) New EPI Summary Verification Report of EPI Extracted Data from Site:\n The new Verification Summary Report of EPI Extracted Data from Site \n replaces the existing Emerging Pathogens Verification Report. This \n new summary report consists of the following functionality:\n 1) Summary report automatically generated at the sites and sent \n to the EPI-REPORT mail group on the 15th day of each month\n 2) Summary pages are displayed in a human readable format used \n for quick viewing\n 3) Displays reporting site name and station number\nRISK ANALYSIS: Changes made by patch LR*5.2*281 have no effect on Blood \n 4) Summary report is only 1-2 pages long\n 5) Summary report displays emerging pathogens total number of\n occurrences during the monthly processing cycle\n 6) Summary report displays emerging pathogens total number of\n persons with occurrences during the monthly processing cycle\n 7) Displays Resolution of Risk Assessment number of persons \n with the nationally rolled-up resolution Hepatitis C that \n occurred during monthly processing cycle\n\n2) New Detailed Verification Report is a detailed pathogen-specific report for validation purposes. The Print Detailed Verification Report [LREPI VERIFICATION REPORT] option prints t\n\n\nDescription\nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n \nASSOCIATED NOIS\n---------------\nDUR-0803-30566\nFGH-0304-32518\nNYH-1203-10526 \n \n \nTEST SITES\n \n----------\nAlbuquerque VAMC - VMS/DSM\nDurham VAMC - VMS/DSM\nIron Mountain VAMC - VMS/Cache \nMaryland HCS - VMS/DSM\nMilwaukee VAMC - VMS/DSM\nNorth Florida/South Georgia HCS - VMS/DSM\nShreveport VAMC - VMS/DSM\nTomah VAMC - VMS/Cache\nUpstate New York HCS - VMS/DSM\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*313 does not\n \n\nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\nalter or modify any software design safeguards or safety critical elements\n ------------ ------------ ----------- ------------\n LR313 N/A 4332118 **313** (Deleted by KIDS)\n LREGFR 2490467 3964631 **289,313**\n \n List of preceding patches: 289\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\nfunctions.\n \n The install time for this patch is less than 5 minute. This patch can be\n installed when Laboratory users are on the system. However these users\n should not be using any of the Laboratory's package verifying options.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\nRISK ANALYSIS: Changes made by patch LR*5.2*313 have no effect on Blood\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nBank software functionality, therefore RISK is none.\n \n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*313'.\n \n When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//\n choose 'NO'.\n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO' unless site has additional local\n \n laboratory verifying options that should be disabled during install.\n \n The install will automatically disable the following options:\n Accession order then immediately enter data LR ACC THEN DATA\n Batch data entry (chem, hem, tox, etc.) LRSTUF\n Bypass normal data entry LRFAST\n Enter/verify data (Load list) LRVRW2\n Enter/verify data (Work list) LRVRW\n Enter/verify data (auto instrument) LRVR\n Enter/verify/modify data (manual) LRENTER\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\n Fast Bypass Data Entry/Verify LRFASTS\n Group data review (verified & EM) LRGVP\n Group verify (EA, EL, EW) LRGV\n \n \n 7. On a mapped system, rebuild your map set.\n \n Note: Routine LR313 will be deleted after successful patch installation. \n \n \n===========\nmade, no specific validation requirements exist as a result of installation\n \nINSTALLATION EXAMPLE\n====================\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*313 Loaded from Distribution 1/26/04@11:22:51\n => LR*5.2*313\n \nThis Distribution was loaded on Jan 26, 2004@11:22:51 with header of\n LR*5.2*313 \nof this patch.\n It consisted of the following Install(s):\n LR*5.2*313\nChecking Install for Package LR*5.2*313\nWill first run the Environment Check Routine, LR313\n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \n \nInstall Questions for LR*5.2*313\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\n1. NOIS DUR-0803-30566 and NYH-1203-10526 reported the eGFR calculation\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LR*5.2*313 :\n Jan 26, 2004@11:26:28\n \nBuild Distribution Date: Jan 26, 2004\ndelta check was not triggered when processing creatinine results via\n \n Installing Routines:...\n Jan 26, 2004@11:26:28\n \n Running Pre-Install Routine: PRE^LR313.\n \n *** Pre install started ***\n \n *** No action required ***\n \noption Enter/verify data (autoinstrument) [LRVR]. The delta check will be\n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION...........\n Jan 26, 2004@11:26:28\n \n Running Post-Install Routine: POST^LR313.\n \n *** Post install started ***\ntriggered when the creatinine value is entered and/or changed or when the\n \n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\neGFR has not been calculated. If the eGFR is a required test and the result\n \n LR*5.2*313 Installed.\n Jan 26, 2004@11:26:28\n \n Install Message sent #xxxxx\nis 'pending' then the delta check will attempt to calculate the eGFR.\n \n\n2. The comment "MISSING PARAMETER" generated when the patient's race is\n'Undeclared' or 'Unanswered' is changed to "For eGFR: Race unknown, if\nAfrican American multiply result by 1.210".\n \n3. The delta check will determine the patient's race using the following\ncriteria:\n a. If specimen for a PATIENT file (#2) patient, the race is determine \n using supported API VADPT.\n b. If specimen for a REFERRAL PATIENT file (#67) patient, the race is\n determined based on RACE field (#.06) in REFERRAL PATIENT file.\nThis patch corrects several defects reported with the eGFR delta check\n c. All other patient types will not use race as a parameter in the\n calculation. These patient types will generate the 'race unknown'\n comment.\n \n4. During patch development it was determined that the lock placed on the\naccession being verified could be prematurely released. This defect could\nallow two or more users to edit the accession concurrently. The delta check\nhas been changed to eliminate the releasing of the lock. The lock will now\nbe released by the lab verifying options.\n \nreleased in patch LR*5.2*289 DELTA CHECK FOR EGFR TEST.\n5. During patch testing a potential safety issue was identified with the\ndelta check with regards to display of abnormal/critical creatinine values.\nThe delta check displayed eGFR exception messages as part of the display\nof creatinine abnormal/critical flags. These eGFR exception messages will\nbe added as accession comments and not displayed as part of the creatinine\nresult display.\n \nThe eGFR exception messages that will be added as comments are.\n Condition Comment\n --------- -------\n \n no patient age - "For eGFR: **eGFR not Calculated - No Age Recorded**"\n no patient sex - "For eGFR: **eGFR not Calculated - No Sex Recorded**"\n race unknown - "For eGFR: Race unknown, if African American multiply\n result by 1.210"\n delta check\n incorrectly\n configured - "For eGFR: **eGFR not Calculated - Delta check not\n configured**"\n Note: this comment generated when field TEST NAME FOR\n OUTPUT VALUE 1 (#61.1) is blank for the eGFR\n \n delta check entry in DELTA CHECKS file (#62.1).\n creatinine\n changed and eGFR\n not in editing\n profile - "For eGFR: **eGFR not in test editing profile -\n Creatinine Changed**"\n\nWhen no patient age or sex is identified, "canc" will be entered as the\neGFR test result.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*313 does not\n6. NOIS FGH-0304-32518 reported the eGFR calculation was being performed\nand the result added to the accession when there was no ordered test for\nthe eGFR. This prevents user from verifying and releasing test results.\nThe eGFR delta check will check for the eGFR test in the test editing\nprofile selected by the user. If the eGFR test is not in the editing\nprofile then it will not be calculated. If the creatinine value is\nchanged, the eGFR test is not in the editing profile and there is a\nprevious eGFR result then the exception message "For eGFR: **eGFR not in\ntest editing profile - Creatinine Changed**" will be generated\n \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n7. When the eGFR delta check is called by option Group data review\n(verified & EM) [LRGVP] the delta check will quit with no action taken.\n \n8. See patch LR*5.2*289 DELTA CHECK FOR EGFR TEST for instructions on\nsetting up and configuring the eGFR delta check.\n \n\nASSOCIATED E3R\n--------------\n None\n\n
\nSee patch description for details.\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*320 does not \nBank software functionality, therefore RISK is none. \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport \n global.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n \n 4. Use the 'Verify Checksum in Transport Global' option and verify \n that all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made,\n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a \n Transport Global' option at this time. You may also compare the \n routines in your production account to the routines in the patch \n by using the 'Compare a Transport Global to Current System' \n option.\n \n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*320'.\nno specific validation requirements exist as a result of installation of this\n \n If prompted ' Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//' choose 'NO'.\n \n If prompted ' Want KIDS to INHIBIT LOGONs during the install? \n YES// ' choose 'NO'.\n \n If prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\n \npatch.\n 7. Routine LR320 will be deleted after successful patch installation.\n\n***********************************************************************\n\nThe EPI Historical Reseeding patch, LR*5.2*320, contains modifications to the\nEmerging Pathogens Initiative (EPI) software that corrects fata errors received\nduring the historical reseeding of the EPI data. Sites were receiving fatal\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nerrors from Austin that caused their data to be rejected.\nThe modifications included in this patch are:\n\n1) Test patients are not included in the EPI data sent to Austin.\n\n2) A string length error was fixed, MERGEOUT+34^HLTF2:1,%DSM-E-STRLEN. This\n error was due to PID segments that were over 245 characters long.\n\n3) The 410 errors, discharge date after processing date, was corrected. This\n problem was due to patients with a future discharge date. This patch resolves\nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n this problem by not sending the discharge date to Austin if the discharge date\n is greater than the last day of the month of the extracted data.\n\n4) An undefined error is fixed. In the Print Detailed Verification Report \n[LREPI VERIFICATION REPORT] option an undefined error occurs when an "^" is \nentered at the "Select Pathogen: " prompt. Also, when selecting the Detailed\nVerification Report, the processing period is now displayed for easier\nselection.\n\n5) The 605 errors are corrected. This problem was due to a missing date in the\n \n BACT RPT DATE APPROVED (#11 ) field of MICROBIOLOGY (#63.05) subfile of LAB \n DATA (#63) file for organism IDs and a "0" was being sent to Austin. This\n patch resolves this problem by sending a blank field when the completed date\n is missing instead of "0".\n\n6) A processing routine is added to the LREPI CLIENT protocol. This resolves\nmissing processing routine HL7 errors.\n\n \nTest Sites:\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*320 does not \n==============\n Phoenix, AZ VAMC\n Boston, MA HCS\n Cincinnati, OH VAMC\n Durham, NC VAMC\n\n ROUTINE SUMMARY\n ===============\n \n The following routines are included in this patch. The second line\nalter or modify any software design safeguards or safety critical\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n \n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR320 N/A 2912182 320(Deleted by KIDS)\n LREPI1 11822436 11922889 132,157,175,260,281,320\nelements functions.\n LREPI2 8491199 8531292 132,157,175,242,260,281,320\n LREPI3 9184652 9874365 132,175,260,281,320\n LREPIRP 20442264 20526099 132,157,175,260,281,320\n LREPIRP5 11788836 11827526 281,320\n LREPIRP7 17171829 17482896 281,320\n\n ASSOCIATED NOIS:\n ================\n \n PHO-0604-62256\n \n DUR-0604-31907\n CTX-0604-71980\n DAY-0704-40732\n\n E3Rs:\n =====\n \n N/A\n \n**********************************************************************\nRISK ANALYSIS: Changes made by patch LR*5.2*320 have no effect on Blood \n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n \nNOTE: Kernel patches must be current on the target system\n to avoid problems loading and/or installing this patch.\n\n
\nThis patch will prevent a user from entering the ; and : characters when\ndefining or modifying a data name using menu options Add a new data name\n[LRWU5] and Modify an existing data name [LRWU6].\n\n
\nThis patch addresses 2 NOIS calls:\n \n1) BRK-1095-12897 PROBLEMS WITH SUMMARY LIST (SUPERVISORS')\n2) ECH-0404-50682 ERROR AT P1+10^LRLISTE\n\n
\n \n ------- -----\n LRAPDA 8740574 11974055 72,73,91,121,248.259,295\n LRAPDSR 3990550 4820936 248.259,295\n LRLOG n/a 305911 295\n LRMIEDZ 5380499 5420375 295\n LRMIEDZ2 12271075 12684281 23,104,242,295\n LRMINEW1 5165056 5204932 295\n LRMISTF1 13608455 13918017 121,128,202,263,264,295\n LRMIV 5001526 5041402 295\n LRMIV1 12023776 12570260 295\n LRMIV2 15031478 15300044 242,295\n Clinical Reminders PXRM*1.5*12\n LRMIVER1 9809595 9849471 295\n LROC 9187454 9241387 121,295\n LRPX n/a 1901323 295\n LRPXAPI n/a 6978402 295\n LRPXAPI1 n/a 9229397 295\n LRPXAPI2 n/a 9408086 295\n LRPXAPI3 n/a 10777199 295\n LRPXAPI4 n/a 9871300 295\n LRPXAPI5 n/a 7476080 295\n LRPXAPI6 n/a 2460984 295\n Inpatient Pharmacy PSJ*5*90\n LRPXAPIU n/a 3414289 295\n LRPXAPP n/a 6489777 295\n LRPXAPPU n/a 3123020 295\n LRPXCHK n/a 8866448 295\n LRPXCHKA n/a 7391720 295\n LRPXCHKM n/a 3210671 295\n LRPXRM n/a 9609565 295\n LRPXSXRA n/a 8089677 295\n LRPXSXRB n/a 5387076 295\n LRPXSXRL n/a 4335783 295\n Laboratory LR*5.2*295\n LRVER3A 10313641 10338465 1,5,42,100,121,153,190,\n 221,254,263,266,274,295\n \n Host File:\n ==========\n Because this is part of a multi-package build this patch will be available\n only as a host file. The name of the file is\n CLINICAL_REMINDERS_INDEX.KID.\n \n Sites will retrieve VistA software from the following FTP addresses. The\n Mental Health YS*5.01*77\n preferred method is to FTP the files from download.vista.domain.ext. This\n transmits the files from the first available FTP server. Sites may also\n elect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \n \n Installation:\n Order Entry/Results Reporting (OE/RR) OR*3*157\n =============\n 1. Detailed installation instructions may be found in the Installation\n Guide, PXRMIG-P12.PDF.\n \n 2. After successful installation, the init routine GMPLP27I may be\n deleted.\n \n Outpatient Pharmacy PSO*7*118\n Patient Care Encounter (PCE) PX*1.0*119\n Pharmacy Data Management PSS*1*62\n PIMS/Scheduling DG*5.3*478\n This project consists of 12 patches that work together to create a new\n Problem List GMPL*2*27\n Radiology RA*5*33\n Vitals GMRV*4*15\n \n This patch (LR*5.2*295) provides the description of the Lab\n routines, but not the Lab routines themselves, which must be loaded\n from the main multi-build host file. PXRM*1.5*12 distributes these Lab\n routines. This patch provides a new global ^PXRMINDX where Lab data\n are indexed in ^PXRMINDX(63, for fast retrieval. Lab APIs are provided\n to provide easy access. APIs are documented in DBIAs 4245 and 4246.\n Clinical Reminders index global. The purpose of this index is to provide\n Changes were made to existing Lab routines that update the indexes\n whenever Lab data is added, edited, or deleted.\n \n Note: This patch is informational; the build (LR*5.2*295) will be\n distributed as part of a multi-package build,\n CLINICAL_REMINDERS_INDEX.KID.\n \n Blood Bank Clearance:\n =====================\n \n rapid access to clinical data. All of the standard Clinical Reminders\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*295 does not \n contain any changes to the VISTA BLOOD BANK Software as defined by VHA \n DIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*295 does not \n alter or modify any software design safeguards or safety critical \n elements functions.\n \n RISK ANALYSIS: Changes made by patch LR*5.2*295 have no effect on \n Blood Bank software functionality, therefore RISK is none.\n finding types are included in the index.\n \n VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the \n changes made, no specific validation requirements exist as a result of \n installation of this patch.\n \n Documentation:\n ==============\n An installation guide, PXRMIG-P12.PDF, and a technical manual,\n PXRMTM-P12.PDF, are available. This documentation will be in the form\n of Adobe Acrobat files. The documentation can also be found on the\n \n Health System Design and Development Web page: (http://vista.domain.ext/vdl/).\n \n The preferred method is to FTP the files from download.vista.domain.ext.\n This transmits the files from the first available FTP server. Sites\n may also elect to retrieve documents directly from a specific server as\n follows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n The 12 patches that comprise this project are:\n \n Test Sites:\n ===========\n Anchorage\n Augusta\n Birmingham\n Bronx\n Chicago\n Dayton\n Loma Linda\n \n Martinez\n Montana\n Puget Sound\n Salt Lake City\n San Francisco\n Tampa\n Washington DC\n White River Junction\n \n Routine Summary:\n Package Patch\n ===============\n The following is a list of the routines included in this patch. The \n second line of each routine looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n Name Before Patch After Patch Patch List\n ----------------------------------------------------------------\n \n\n
\nVISTA Laboratory Package patch LR*5.2*286 contains changes to software\nfound to have no impact on the VISTA BLOOD BANK SOFTWARE version 5.2\n \n12. Enter/verify data (auto instrument) [LRVR] and Enter/verify/modify\ndata (manual) [LRENTER] options will display patient information from\nPAT. INFO. field (#.091) in LAB DATA file (#63) during result verification.\n(E3R #13408)\n \n13. Alignment of test results during verification process has been adjusted\nto avoid display of previous and current test results together. Results\nwill be displayed right-justified under the date/time of each specimen. \n \ncontrol functions.\n14. NOIS ALB-0100-50284, FAV-1103-70892 reported a failure of UID creation\nand storage when creating a non-daily accession that is in common with\nanother accession area. The failure occurs on the creation of the first\naccession for a given accession area and date. After the first accession\nfor an accession date is created and stored in ACCESSION file (#68)\nsubsequent accessions have the UID stored properly. Failure was due to\nmissing subfile zeroth nodes for the ACCESSION DATE multiple (#68.01) and\nACCESSION NUMBER multiple (#68.02) of the ACCESSION file (#68) when calling\nFileMan to store the UID. Routine LRWLST1 will now check and set the\nsubfile's zeroth nodes before calling FileMan.\n\n \n FileMan calls have been converted from classic FileMan DIE calls to\nFileMan Database Server calls (DBS). When an error condition is\nencountered during a FileMan DBS call, the Laboratory package will\ngenerate a mail message with the subject "FileMan DBS call failed during\naccessioning in routine LRWLST1". This message will be sent to the local\nmail group "LMI". It will contain debugging information to assist site\nand National VistA Support in resolving the condition that produced the\nerror.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*286 have no effect on Blood\n15. NOIS BON-0196-71728 reported a problem with storing the appropriate\ntreating specialty associated with an accession. A bad or incorrect\npointer to FACILITY TREATING SPECIALTY file (#45.7) could be stored in\nthe TREATING SPECIALTY (#6.6) field within the ACCESSION NUMBER field\n(#68.02) multiple within the ACCESSION DATE field (#68.01) multiple of\nthe ACCESSION file (#68). When a specimen is accessioned for a\nnon-inpatient and the user selects an inpatient ordering location the\nsoftware would use the specialty from SPECIALITY file (#42.4) that\nis associated with the WARD LOCATION file (#42) entry linked to the\nHOSPITAL LOCATION file (#44).\nBank software functionality, therefore RISK is none.\n \n Routine LRWLST1 will determine treating specialty based on the\nassociated TREATING SPECIALTY field (#9.5) in the HOSPITAL LOCATION file\n(#44) when the patient is not an inpatient. When a patient is an inpatient\nthen treating specialty will be determined from the PATIENT file (#2),\nTREATING SPECIALTY field (.103). Treating specialty will only be stored\nin ACCESSION file (#68) when the patient is from PATIENT file (#2).\n \n16. The following defects were identified during the software review as\npart of patch development.\n\n \n a. Ordering location and ordering provider will not be stored on\naccessions that are related to LAB CONTROL NAME file (#62.3) entries.\n \n b. During accessioning if accession area is locked by another process,\nthe message displayed to user was "Accession area is locked by another\nuser." Message will now include the name of the accession area that\nthe software is waiting on lock.\n\n c. Interim report options and displays will display month portion of\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*286 does not\ndate/times using the three letter abbreviation instead of the two number\ndesignation to eliminate potential confusion with day portion of dates.\nTime is displayed using 24 hour time format.\n \n d. Interim report could display the wrong ordering and collecting site\nwhen the specimen was received from an integrated facility. Report will\ndisplay the correct ordering and collecting site.\n \n e. Referral Patient Multi-purpose Accession option [LR LEDI] was\nprompting the user for CPRS Nature of Order which is not used during\nalter or modify any software design safeguards or safety critical elements\naccessioning of non-PATIENT file (#2) patients. Routine LROW3 is\nmodified to only prompt the user for CPRS Nature of Order when\naccessioning a patient from the PATIENT file (#2).\n \n f. Previous test versions of previous LEDI versions may have installed \ntwo versions of the "D" cross reference in LAB PENDING ORDERS ENTRY file\n(#69.6). The post-install will delete and reindex the "D" cross reference\non file #69.6.\n \n g. Entering of accession number during lab results verification will \nfunctions.\ncheck for invalid values or numbers out of range (1-999999).\n \n17. Referral Patient Multi-purpose Accession option [LR LEDI] will check\nfor pending orders when performing accessioning without a bar code scanner.\nIt will display to the user and store order comments that accompanies\nelectronic orders with order in LAB ORDER ENTRY file (#69).\n \n18. When using the Enter/verify/modify data (manual) option [LRENTER] to\namend previously released results user can now enter their verifying\ninitials in mixed case. \n\n \n19. NOIS CHS-0303-40534 reported a defect which prevented results for\nreflex tests added to a LEDI order at the host laboratory being returned\nelectronically to the collecting laboratory. Routine LRWLST11 was storing\nthe collecting site as both the collecting site and ordering site in the\norder created in LAB ORDER ENTRY file (#69). When a collecting site is a\nmember of an integrated facility the collecting site is the site collecting\nthe specimen and the ordering site is the primary facility of the\nintegrated institution. Reflex test added by the host site would have the\nincorrect ordering site assigned which prevents the LEDI software from\ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE\nPOTENTIAL IMPACT ON SITES: This patch contains changes to a Data\nreturning the results of the reflex test to the collecting facility. Defect\nhas been corrected to store the correct ordering and collecting sites on\nLEDI accessions.\n \n20. NOIS BRK-0499-10720, MAR-0603-21152 reported a defect during lab\nresult verification using option Enter/verify/modify data (manual)\n[LRENTER] which caused the previous patient demographics to be displayed\nwhen entering results on an accession. If the previous selected accession\nwas in an uncollected state, the option was skipping the uncollected\naccession and incrementing the default accession number to the next\nDictionary identified in Veterans Health Administration (VHA) Directive\navailable accession. If the user selects this or another accession, the\npatient demographics of the selected accession were not being displayed.\nInstead, the patient demographics of the uncollected accession were\ndisplayed. Routine LRVER will now display the patient demographics of the\ncurrently selected accession.\n\n21. NOIS SFC-1103-60132 reported a defect during display of lab results\nin the CPRS GUI. When a critical flag becomes part of the data for a\npatient in CPRS, the line of data containing the flag becomes split\nafter the * following the high or low flag, and the units along with\n99-053. The changes have no effect in Blood Bank functionality or medical\nthe reference range gets bumped to the next line down. Routine LR7OGMP\nincreases the space allocated to display this information from 37 to 38\ncharacters to display units/normals on same line.\n \n22. When displaying results that are a Set of Codes data type, the result\nwill be displayed using the external value for the set of codes.\n \n23. NOIS NYH-0700-11942 reported a defect with critical value flag not\nbeing triggered when entering a value of 0. Value of 0 will be evaluated\nwhen performing high/low/critical value checks.\ndevice control functions. There is no adverse potential to sites.\n \n24. When verifying results from a reference laboratory using Enter/verify\ndata (auto instrument) option [LRVR], any test results that have not\nbeen verified will be displayed to the user after verification. The display\nwill list the test names, results, abnormal flags and units if available. \nThis display will list the test(s) as not reviewed. This may indicate that\nadditional or reflex testing has been added by the reference laboratory.\nThese additional tests may need to be added to the accession to process\nthese results.\n \n \n25. During verification of laboratory results, comments for a previous\nresult are displayed along with the previous result when entering\nresults manually or by automated instrument for user selected tests\n(E3R #18490). Users can indicate which tests should have previous\ntest comments displayed during verification by flagging the test using\nGeneral Lab User Parameters option [LR USER PARAM] located on the\nInformation-help menu [LRHELP].\n\n26. NOIS SDC-0904-61304 Reported a defect with the display of text\nresults in CPRS when using the Laboratory Results-All Test By Date and\nVALIDATION REQUIREMENTS BY OPTION: There are no required validation\nLaboratory Results-Selected Tests By Date. When a text result was\ndisplayed that exceeded 10 characters and the test has no units or\nnormals specified, the display of the result was corrupted with <spaces>\ninserted into the text. Test results will be displayed without corruption.\nUnits, reference ranges, and site codes will be displayed on the following\nline when test results print in area usually reserved for these parameters.\n \n27. NOIS IND-0498-42538 reported a defect in display of test comments during\nlab test result verification when encountering an 'end-of-page' condition.\nAll test comments will now be displayed.\nscenarios to be completed by sites after installing LR*5.2*286.\n \n\n PATIENT SAFETY ISSUES RESOLVED IN THIS PATCH:\n ============================================\n \n PSI-040260/NOIS HVH-0604-10572 - "Not Performed test Resulted\n - No Alert Generated"\n \nThis patch corrects defects in software used to set laboratory tests\nto a Not-Performed (NP) state. The NP state was introduced by patch\n \nLR*5.2*221 in 1999. The functionality introduced by this patch replaced\nthe "delete-a-test" functionality. Instead of deleting tests, tests are\nnow set to a not-performed state.\n \nHowever, tests in the NP state could still be edited such that the NP\nstate is replaced with an actual result. Results entered into NP tests\nwere not treated in the same manner as results entered through the normal\nresults entry pathways. File updates to ACCESSION file (#68), LAB ORDER\nENTRY file (#69), and ORDER file (#100) as well as alerts were not\ngenerated. This situation was documented in NOIS HVH-0604-10572\n========================================\n- "Not Performed test Resulted - No Alert Generated". This was identified\nas a potential patient safety risk. With concurrence from the Pathology\n& Laboratory Medicine Program Office, the appropriate mechanism for\nhandling the situation is to disable editing of NP tests. If the test is\ndesignated as NP and the user wants to edit the test result, they will\nnow have to order the test(s) in a new accession.\n \n \nASSOCIATED E3R\n--------------\n \n E3R #13408, ADDING INFECTION WARNING TO PROCESS DATA OPTIONS\n E3R #16060, CORRECT ALIGNMENT PROBLEM\n E3R #17904, LEDI BETWEEN VA AND DOD SITES\n E3R #18490, COMMENTS DISPLAY FORPRVIOUS RESULTS\n \n \nASSOCIATED NOIS\n---------------\n ALB-0100-50284\n BRK-0499-10720\nVERSION 5.2. Change includes:\nPatch LR*5.2*286 VA/DOD LAB INTEROPERABILITY will be distributed and\n BON-0196-71728\n CHS-0303-40534\n DAY-0303-40775\n DEN-1299-52099\n FAV-1103-70892\n HVH-0604-10572\n IND-0498-42538\n MAR-0603-21152\n NYH-0700-11942\n PHI-0803-21507\ninstalled with patch LA*5.2*64 VA/DOD LAB INTEROPERABILITY\n SDC-0904-61304\n SFC-1103-60132\n TAM-0400-31033\n WPB-0900-32221\n \n\nTEST SITES\n----------\n Albuquerque VAMC - VMS/DSM and VMS/Cache\n Boston HCS - VMS/DSM and VMS/Cache\n \n El Paso HCS - NT/Cache and VMS/Cache\n Hines VAMC - VMS/DSM and VMS/Cache\n Honolulu VAMC - NT/Cache\n Manchester VAMC - NT/Cache NT and VMS/Cache\n Milwaukee VAMC - VMS/DSM\n North Chicago VAMC - VMS/DSM\n Salt Lake City VAMC - VMS/DSM\n San Diego VAMC - VMS/DSM and VMS/Cache\n Upstate New York HCS - VMS/DSM and VMS/Cache\n \nThis patch adds support for sending/receiving Laboratory Electronic\n \n INSTALLATION FILES:\n ==================\n The following software and documentation files are exported as part of\n this patch:\n \n File Name Contents Retrieval Format\n --------- -------- ----------------\n \nLAB_LEDI_III.KID LA*5.2*64 KIDS build ASCII\nData Interchange (LEDI) orders/results with Department of Defense (DoD)\n LR*5.2*286 KIDS build\n \n \nLAB_LEDI_III_IG.PDF LABORATORY ELECTRONIC DATA BINARY\n INSTALLATION GUIDE\n \nLAB_LEDI_III_IMP_UG.PDF LABORATORY ELECTRONIC DATA BINARY\n IMPLEMENTATION AND USER GUIDE\n \n The files listed above may be obtained via FTP. The preferred method is\nfacilities.\n to FTP the files from:\n \n download.vista.domain.ext\n \n This transmits the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as\n follows:\n \n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n \n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software] \n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\nLaboratory result verification has been enhanced to allow the designation\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR286 N/A 5465218 **286** (Deleted by KIDS)\n LR7OB63 9973912 9132350 **121,187,286**\n LR7OGM 8016197 8279122 **187,220,312,286**\n LR7OGMC 5100174 5463477 **187,230,312,286**\n LR7OGMG 3593445 3973477 **187,230,286**\n LR7OGMP 5548341 6065382 **187,246,282,286**\nof a performing laboratory and the use of the performing laboratory's\n LR7OR2 9125008 8919494 **121,187,219,285,286**\n LR7OSUM1 12883059 12868699 **121,187,256,286**\n LR7OSUM6 7911216 5450631 **121,201,187,286**\n LRAFUNC 5202410 5809534 **286**\n LRDIDLE0 5463932 6544739 **140,171,153,286**\n LRDPAREF 5111405 7469302 **153,222,286**\n LRDPAREX 7190033 6456580 **153,286**\n LREVENT 3678954 2907416 **153,286**\n LRFAST 19691126 18799737 **100,121,201,286**\n LRFASTS 6423167 6524547 **30,95,121,271,286**\nunits, normals, and normalcy status in results reporting.\n LRGP1 3988622 4165501 **112,269,286**\n LROE 14550901 11534796 **100,121,201,221,263,286**\n LRORD 12009917 12806626 **100,121,153,286**\n LRORD1 9848796 9190513 **1,8,121,153,201,286**\n LRORDB 3782224 7231598 **153,222,286**\n LROW3 7497722 6459972 **33,121,286**\n LRRP 11838355 9427993 **195,221,283,286**\n LRRP1 8015031 6556852 **153,221,283,286**\n LRRPU N/A 3220194 **286**\n LRSTUF1 13209134 11668378 **153,286**\n The addition of the "USE FOR REFERENCE TESTING" field (#13) to the\n\n LRVER 17228890 15441873 **153,286**\n LRVER1 8587449 7330679 **42,153,201,215,239,240,\n 263,232,286**\n LRVER3 14311842 13055299 **42,100,121,140,171,153,\n 221,286**\n LRVER4 19639169 14489554 **14,42,112,121,140,171,\n 153,188,279,283,286**\n LRVER5 14564045 14854455 **42,153,283,286**\n LRVERA 690805 5764794 **153,271,286**\n LRVR 13316120 11130012 **42,153,263,286**\n1. User during the verification process is able to specify the performing\n LRVR1 11269859 11667912 **42,153,221,286**\n LRVR3 10486080 11176919 **42,121,153,286**\n LRVR4 8885642 9645653 **14,42,121,153,221,263,\n 279,283,287,286**\n LRVR5 11950773 4666781 **1,42,153,263,283,286**\n LRWLST1 18457202 12664045 **48,65,121,153,261,286**\n LRWLST11 21393713 16883055 **121,128,153,202,286**\n \n List of preceding patches: 187, 202, 222, 230, 232, 256, 261, 269, 271\n 282, 283, 285, 287, 312\nlaboratory. The performing laboratory is selected from the list of\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \nSee LABORATORY ELECTRONIC DATA INTERCHANGE III (LEDI III) INSTALLATION GUIDE\n LA*5.2*64/LR*5.2*286\navailable entries in the site's INSTITUTION file (#4). The selection of\nentries is screened as follows:\n a. User can select the division they are logged on.\n b. User can select an institution that is configured in the LAB\n SHIPPING CONFIGURATION file (#62.9) as a host facility with their\n division as the collecting facility.\n \n "SITE/SPECIMEN SUB-FIELD" (#60.01) of the LABORATORY TEST file (#60).\n2. During acceptance and verification of results received from a reference\nlaboratory via an HL7 interface (LEDI), the performing laboratory, results,\nunits, normals and normalcy status contained in the HL7 message are stored\n"as is".\n\n3. Receipt of amended reports from a reference laboratory will generate a\nMailMan bulletin containing the particulars of the amended report. This\nbulletin is sent to the members of the mail group specified for\n"New Result" alerts in LA7 MESSAGE PARAMETER file (#62.48) for the interface.\n \n The addition of the "USE FOR REFERENCE TESTING" field to the "LR ATOMIC\n4. Amended reports received via a LEDI HL7 interface can be processed\nvia the Enter/verify/modify data (manual) option [LRENTER].\n \n5. Users using the Enter/verify/modify data (manual) option [LRENTER] to\nenter results manually from a reference laboratory can use the units and\nnormals specified in LABORATORY TEST file (#60) by configuring USE FOR\nREFERENCE TESTING field (#13) within the SITE/SPECIMEN subfile (#100).\nIf this field is not enabled for reference laboratory result data entry,\nthen the user is prompted for units, normals, high and low reference ranges\nto store with the results. The Edit atomic tests option [LRDIEATOMIC]\n TESTS" Input Template.\nallows Labortory Information Manager (LIM) to designate this functionality\nfor affected tests.\n \n6. NOIS DEN-1299-52099, NYH-0700-11942, PHI-0803-21507, TAM-0400-31033, and\nWPB-0900-32221 reported the defect of normalcy status (low/high/critical\nlow/critical high) being incorrectly evaluated when the test result is\nzero (0). Evaluation of normalcy status will properly deal with test\nresults of zero (0).\n \n7. Changing normalcy status and units will trigger the generation of audit\n\ntrail comments.\n \n8. During verification, the ordering provider's phone and pager information\nis displayed.\n \n9. Display of lab results in the Computerized Patient Record System\nGraphical User Interface (CPRS GUI) and Laboratory Interim Reports has\nbeen modified to display units and normals associated with results at time\nof verification. Results that are derived from a Set of Codes will be\nreported using the external form of the code.\nThe above change has been reviewed by the VISTA Blood Bank Developer and\n \n10. Display of performing laboratory has been added to CPRS GUI display of\nresults.\n\n11. NOIS DAY-0303-40775 reported a defect in display of lab results with\nembedded spaces. When lab results contained embedded spaces these spaces\nwere being removed prior to the display of the lab result. The removal of\ntheses spaces resulted in corruption of the result. Routines LR7OB63 and\nLR7OR2 have been corrected to trim leading and trailing spaces but leave\nembedded spaces.\n\n
\n \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \n \n7. For each of the installation questions answer 'NO'.\n \n8. If you unmapped the routine in step 1, rebuild your map set.\n \n9. Routine LR326 will be deleted after a successful patch installation.\n \nInstallation Example\n====================\n \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nSelect Installation Option: 6 Install Package(s) \nSelect INSTALL NAME: LR*5.2*327 Loaded from Distribution \n10/15/04@12:06:10 \n => LR*5.2*326 DSS LAR SUPPORT PATCH ECX*3.0*71\n \nThis Distribution was loaded on Oct 15, 2004@12:06:10 with header of \n \n LR*5.2*326 DSS LAR SUPPORT PATCH ECX*3.0*71\n It consisted of the following Install(s): \n LR*5.2*326 \n \nChecking Install for Package LR*5.2*307 \nWill first run the Environment Check Routine, LR326 \n \n \n --- Environment Check is Ok \n--- \n \n \nInstall Questions for LR*5.2*326 \n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*326 does not \nWant KIDS to INHIBIT LOGONs during the install? YES// NO \n \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO \n \nEnter the Device you want to print the Install messages. \nYou can queue the install by enter a 'Q' at the device prompt. \nEnter a '^' to abort the install. \n \nDEVICE: HOME// UCX/TELNET \n \nalter or modify any software design safeguards or safety critical \n \nInstall Started for LR*5.2*326 : \n Oct 15, 2004@09:56:40 \n \nBuild Distribution Date: Oct 15, 2004 \n \nLR*5.2*326 \n \n---------------------------------------- \n \nelements functions.\n Installing Routines: \n Oct 15, 2004@09:56:40 \n \n Running Pre-Install Routine: PRE^LR307 \n \n Running Post-Install Routine: POST^LR307 \n \n Updating Routine file... \n \n Updating KIDS files... \n \n \n LR*5.2*326 Installed. \n \n Oct 15, 2004@09:56:40 \n \n \nInstall Message sent \n \nInstall Completed \n \nRISK ANALYSIS: Changes made by patch LR*5.2*326 have no effect on Blood \nEND OF INSTALLATION EXAMPLE\n=========================== \nsoftware functionality, therefore RISK is none.\n \nDescription:\n \nRoutine Description:\n====================\n \nThe LRCAPDAR routine has been enhanced to capture the ordering provider \nfor each accession being passed to DSS LAR API.\n \nOption Description:\n==================\nThere is no option attached to this functionality. The data extraction in \n===========\nactivated by ECX DSS API.\n \nData Dictionary Changes:\n=======================\nAn additional field will be installed with this patch.\nPROVIDER (#12) field will be added to LAB DSS LAR EXTRACT (#64.036) file.\nThis field will be populated by the Laboratory DSS LAR API.\n \n \n \n \nNOTE: This patch is a companion to the ECX*3.0*71 patch.\n LR*5.2*326 is not called by any menu option and does not\n have any user interface. Patch LR*5.2*326 MUST\n be installed for the ECX*3.0*71 patch to work properly.\n \nTest Sites\n==========\nCheyenne, WY\nLittle Rock, AR\nPortland, OR\nThis patch implements a request from Decision Support System to expand \nMinneapolis, MN\n \nAssociated NOIS:\n================\nN/A\n \nRoutine Summary\n===============\n \nThe following is a list of routines included in this patch. The\nthe LAB DSS LAR EXTRACT (#64.036) file to include the passing ordering \nsecond line of each if these routines now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ===========\n LR326 N/A 2022894 326\n LRCAPDAR 7334799 7585446 143,169,258,307,326 \nprovider in DSS LAR API. The companion DSS patch is ECX*3.0*71. \n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \nThe install time for this patch is less than 5 minutes. This patch can \nbe installed when Laboratory users are on the system. Suggested time to \ninstall: non-peak requirements hours.\n \nNOTE: Patch LR*5.2*307 must be installed BEFORE this patch.\n \n \n1. If LRCAPDAR is mapped, disable mapping for it.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu.\n this option will load the KIDS patch onto your system.\n \n3. From the 'Kernal Installation & Distribution System' (KIDS)\n menu, select the 'Installation Menu'\n \n4. Use the 'Verify Checksum in Tranport Global' option to\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*326 does not \n confirm that the correct checksums are present.\n \n5. From the same menu select each of the following options:\n \n 'Compare Transport Global to Current System'\n 'Backup Transport Global'\n \n6. From the 'Installation Menu' of the KIDS menu, run the\n option 'Install Package(s)'. Select the package 'LR*5.2*326'\n and proceed with the installation.\n\n
\nThis patch resolves a problem introduced with coding changes in the \nroutine LRMIBUG in patch LR*5.2*318 that causes an undefined variable \nerror. This error will occur when the user adds antibiotics to the list \nof antibiotics in an ordered panel.\n \nThis problem was reported in NOIS calls:\n BHS-1204-10061 $ZE= <UNDEFINED>DELINT+6~LRMIBUG\n ALT-1204-20766 UNDEFINED ERROR IN MICRO\n\n
\nThis patch must be loaded by ALL sites who have loaded LR*5.2*72. This\npatch corrects problems encountered with the option Log-in regular\n(invoices) [LRBLILR] and Select units for patients [LRBLPIC] after\nLR*5.2*72. For a complete description of this patch, refer to the patch\ndescription in the patch message from the Forum Patch Module. The actual\npatch message itself MUST be forwarded to the BB Supervisor and/or LIM at\nevery site.\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*303 does not\nBank software functionality, therefore RISK is none.\n Coatesville VAMC\n Erie VAMC\n Grand Junction VAMC\n Heartland-East HCS\n Heartland-West HCS\n Lebanon VAMC\n Martinsburg VAMC\n Maryland HCS\n Milwaukee VAMC\n Montana HCS\n \n Philadelphia VAMC\n Pittsburg HCS\n Puget Sound HCS\n Roseburg VAMC\n Salt Lake City VAMC\n Sheridan VAMC\n Walla Walla VAMC\n Washington VAMC\n White City VAMC\n Wike Barre VAMC\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\n Wilmington VAMC\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\nmade, no specific validation requirements exist as a result of installation\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR303 N/A 4831421 **303** (Deleted by KIDS)\n LRLNCPMP 7461913 7416816 **215,232,278,303**\n LRSRVR 16543787 5915085 **232,303**\n LRSRVR1 N/A 11247287 **303**\n LRSRVR2 N/A 12542186 **303**\n LRSRVR3 N/A 13571036 **303**\n LRSRVR4 N/A 538253 **303**\n \nof this patch.\n List of preceding patches: 232, 278\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \nThe Laboratory package, in support of the VA Health Data Repository (HDR)\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*303):\n a. Print Transport Global\n b. Backup a Transport Global\nefforts, has developed the following reports to support VA Data\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*303'. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\nStandardization of laboratory results. These reports/extracts will\n YES//', choose 'NO'.\n \n 6. On a mapped system, rebuild your map set.\n \n Note: Routine LR303 will be deleted after successful patch installation.\n \n \nINSTALLATION EXAMPLE\n====================\n \nfacilitate centralized mapping and data validation of National Laboratory\nSelect Installation Option:\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: Install Package(s)\nSelect INSTALL NAME: LR*5.2*303 Loaded from Distribution 12/21/04@13:39:35\n => LR*5.2*303\n \nThis Distribution was loaded on Dec 21, 2004@13:39:35 with header of\n LR*5.2*303\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\nTest (NLT) and Logical Observation Identifiers Names and Codes (LOINC)\n It consisted of the following Install(s):\n LR*5.2*303\nChecking Install for Package LR*5.2*303\nWill first run the Environment Check Routine, LR303\n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nwithin VistA Laboratory.\nInstall Questions for LR*5.2*303\n \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// n NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// n NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LR*5.2*303 :\n Dec 21, 2004@13:40:26\n \nBuild Distribution Date: Dec 21, 2004\n \n Installing Routines:........\n************************************************************************** \n Dec 21, 2004@13:40:27\n \n Running Pre-Install Routine: PRE^LR303.\n \n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\n \nThis patch must be installed within five days of receipt in order to\n Running Post-Install Routine: POST^LR303.\n \n *** Post install started ***\n \n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \nprovide information to a centralized LOINC mapping team which will use\n Updating Routine file......\n \n Updating KIDS files.......\n \n LR*5.2*303 Installed.\n Dec 21, 2004@13:40:27\n \n Install Message sent #xxx\nthis information to provide recommended NLT and LOINC mappings for CH\nsubscript - chemistry, hematology, coagulation, urinalysis, serology type\nresults) used by each facility. These recommendations will be sent back\nto the facility for review and action. Installation of this patch is for\nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nthis reporting purpose only and has no effect on current laboratory\nfunctionality.\n************************************************************************** \n\n \n1. These LRLABSERVER server reports are available with this patch:\n \nLOCAL REPORT\n Send a message to: S.LRLABSERVER@domain name\n Subject:LOCAL REPORT\n \n \n The body of the message will be ignored. This will scan the database\nfor mapped LOINC data and return the results to the person sending the\nmail message request.\n \n \nLOCAL REPORT DELIMIT\n Send a message to: S.LRLABSERVER@domain name\n Subject: LOCAL REPORT DELIMIT\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*303 does not\n The body of the message will be ignored. This will scan the database\nfor mapped NLT and LOINC data. Results are returned to the person sending\nthe mail message request. The extracted data is returned as an attached\nfile in a delimited format using the "|" character as the field delimiter.\n \n Record legend for attached file: Station #-64 ien-61 ien-Time Aspect|NLT\n Code|NLT Name|Default LOINC Code|Default LOINC Name|Default Test|Time\n Aspect|Specimen|Data Location|Data Type|Input Transform|Units|Test Name|\n LOINC Code|LOINC Name|Reference Low|Reference High|Therapeutic Low|\n Therapeutic High|Subscript|Lab Section|\nalter or modify any software design safeguards or safety critical elements\n \n \nRELMA\n Send a message to: S.LRLABSERVER@domain name\n Subject: RELMA\n \n The body of the message will be ignored. This will scan the local site's\nLABORATORY TEST file (#60) and ANTIMICROBIAL SUSCEPTIBILITY file (#62.06)\nand extract data in a format for input into the Regenstrief LOINC Mapping\nAssistant (RELMA) mapping tool. Results are returned to the person sending\nfunctions.\nthe mail message request. The extracted data is returned as an attached\nfile in a delimited format using the "|" character as the field delimiter.\n \n Record legend for attached file: Station #-60 ien-Spec ien|TestName|Spec\n |Time Aspect|Units|LOINC|NLT #|Battery Code|Battery Description|Lab\n Section|Subscript|Comments|Data Type|Reference low|Reference high|\n Therapeutic low|Therapeutic high|\n \n \n2. Lab server mail messages will be purged after successful completion of\n \nthe server request. Supported MailMan API ZAPSERV^XMXAPI will be called to\ndelete the message from POSTMASTER server basket S.LRLABSERVER.\n \n \n ASSOCIATED E3R\n --------------\n None\n \n ASSOCIATED NOIS\n ---------------\nRISK ANALYSIS: Changes made by patch LR*5.2*303 have no effect on Blood\n None\n \n \n TEST SITES\n ----------\n Altoona VAMC\n Bay Pines VAMC\n Bulter VAMC\n Cheyenne VAMC\n Clarksburg VAMC\n\n
\n \nRISK ANALYSIS: Changes made by patch LR*5.2*311 have no effect on Blood \n \nBelow is a list of the routines included in this patch. The second line of\neach of these routines now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994 \n \n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== =============\nBank software functionality, therefore RISK is none.\n LR311PST new 3501668 311\n LRWOMEN 953781 627506 231,248,311\n \nAssociated NOIS: <None>\n \nAssociated E3Rs: <None>\n \nTest Sites:\n===========\n Loma Linda, CA - VMS/Cache\n \n Northern California HCS - VMS/DSM\n Washington, DC VAMC - VMS/DSM\n \n \nInstallation Instructions:\n==========================\n \nThis patch can be installed with users on the system. However, it is \nrecommended that installation occur when there is no Anatomic Pathology\nactivity or activity is at a minimum. This will prevent 'Cannot return to\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nsource routine' errors. \n \nThis patch is part of a multi-KIDS transport global. Please see the patch\ndescription for PXRM*2*1 for instructions to load and install this patch. \nmade, no specific validation requirements exist as a result of \ninstallation of this patch.\n \n \n NOTE: This patch is part of a multi-KIDS build that includes PXRM*2*1\n (CLINICAL REMINDERS), WV*1*16 (WOMEN'S HEALTH) and OR*3*210\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*311 does not \n (ORDER ENTRY/RESULTS REPORTING) (CPRS). Please see the patch\n description for PXRM*2*1 for information on retrieving the host\n file containing these patches.\n \n \n1) Currently the ADD^LRWOMEN utility notifies a Women's Health package\nutility whenever a Cytology or Surgical Pathology report is verified for a\nfemale patient. This functionality was provided with LR*5.2*231.\n \nAfter installation of patch LR*5.2*311, the ADD^LRWOMEN utility will also\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nnotify a new CPRS utility (LAB^ORB3LAB) for all patients, not just female\npatients. Integration Agreement #4287 grants the LABORATORY package\npermission to call the ORB3LAB routine.\n \n2) The code in the MOVE entry point of the LRWOMEN routine was replaced \nwith a QUIT command. With the release of LR*5.2*259, this entry point is \nno longer called. The entry point will be deleted in a future patch.\n \n3) A new entry point, SNOMED, is added to the LRWOMEN routine. This entry \npoint is called by the new indexes created with this patch (see #4 \nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nbelow) when a SNOMED code is changed for a Cytology or Surgical Pathology \nentry. This entry point will call a Women's Health package routine.\nIntegration Agreement #4525 grants the LABORATORY package permission to\ncall the WVLABCHK routine.\n \n4) Two new-style indexes are added to the LAB DATA (#63) file. These \nindexes will be executed when a SNOMED code is changed for a Cytology or \nSurgical Pathology entry.\n \nThe first index is on Subfile 63.12, Field .01 (ORGAN/TISSUE).\n \n FILE: 63.12\n NAME: AC\n SHORT DESCRIPTION: Notify Women's Health of SNOMED change\n TYPE: MUMPS \n EXECUTION: FIELD\n ROOT TYPE: INDEX FILE \n ROOT FILE: 63.12\n USE: ACTION\n DESCRIPTION: This MUMPS cross reference calls SNOMED^LRWOMEN any time a\n change to a SNOMED code is made. The SNOMED line tag notifies the \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*311 does not \n Women's Health package that a SNOMED change has been made on an already\n verified pathology report for a female patient.\n SET LOGIC: Q:$D(DIU(0)) D SNOMED^LRWOMEN\n KILL LOGIC: Q\n ORDER NUMBER: 1 \n TYPE OF VALUE: FIELD\n FILE: 63.12 \n FIELD: .01\n SUBSCRIPT NUMBER: 1 \n COLLATION: forwards\nalter or modify any software design safeguards or safety critical \n \nThe second index is on Subfile 63.912, Field .01 (CYTOPATH ORGAN/TISSUE).\n FILE: 63.912\n NAME: AC\n SHORT DESCRIPTION: Notify Women's Health of SNOMED change\n TYPE: MUMPS \n EXECUTION: FIELD\n ROOT TYPE: INDEX FILE \n ROOT FILE: 63.912\n USE: ACTION\nelements functions.\n DESCRIPTION: This MUMPS cross reference calls SNOMED^LRWOMEN any time a\n change to a SNOMED code is made. The SNOMED line tag notifies the \n Women's Health package that a SNOMED change has been made on an already\n verified pathology report for a female patient.\n SET LOGIC: Q:$D(DIU(0)) D SNOMED^LRWOMEN\n KILL LOGIC: Q\n ORDER NUMBER: 1 \n TYPE OF VALUE: FIELD\n FILE: 63.912 \n FIELD: .01\n \n SUBSCRIPT NUMBER: 1 \n COLLATION: forwards\n \nDocumentation:\n==============\nThere are no documentation changes for this patch.\n \n \nROUTINE SUMMARY:\n================\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*302 does not \n \nbe formally requested by notifying the National Laboratory Test \nCoordinator using the form provided on the VistA laboratory Documentation \nWeb Page. \nhttp://vista.domain.ext/clinicalspecialties/lab/\n \nForward your completed request form to the Exchange distribution group:\n VHAISD LAB NLT_LOINC\n \n===========================\n \n****************************IMPORTANT**********************************\nThis patch will completely remove certain files, replace the files with a \nstandardized copy and then re-point the saved field entries to the \nstandardized copy. It is high desirable to determine that current fields \nand files are free of incorrect data. This will ensure that the patch \ninstallation will not introduce any new errors.\n Failure to ensure FileMan verification of fields option can be run \nwithout generating warnings will result in unresolved errors, which could \nhave unpredictable results. The patch installation will not be affected \nby an invalid field. The patch will generate error message indicating \nthose files/fields that could not be successfully re-pointed after the \nThere is considerable PRE-installation file verification and preparation \nstandardized have been installed.\n \n*** Examples of a single file verify:\nSelect OPTION NAME: VA FileMan\n \n VA FileMan Version 22.0\n \nSelect VA FileMan Option: Utility Functions\n \nSelect Utility Functions Option: VERify Fields\nto be performed by staff familiar with the use of FileMan and Laboratory \n \nMODIFY WHAT FILE: WKLD CODE// 60 LABORATORY TEST (1059 entries)\nVERIFY WHICH FIELD: ALL\nDO YOU MEAN ALL THE FIELDS IN THE FILE? YES\n \nDEVICE: HOME//\n \nWhile the entire file should pass the verify fields check, the fields \nlisted below are the critical entries that should not produce any \nwarnings. If there are any warnings for these fields, they should be \nfile structure. Failure to perform this pre-install testing before \nrectified before the patch is installed or the post install re-pointing \nprocedure will not perform properly.\n \nThis is a list of files and fields that will be re-pointed after the LAB \nELECTRONIC CODES (#64.061) is installed. These fields should be free of \nverify field warnings. Errors or warnings in other fields WILL NOT affect \nthe post-install re-pointing process but should be addressed as soon a \npossible.\n \nTo ensure that there are not any existing pointer problems, files and \nattempting to install this patch significantly increases the risk of \nfields need to be validated. Data and file validation is done with the FM \nVerify Fields option. Only those fields pointing to the replaced files \nand the WKLD CODE file are an issue.\n \n \nFile # File Name Field # Field Name\n====== ========= ======= ==========\n60 LABORATORY TEST\n60.01 SITE/SPECIMEN SUB-FIELD 95.3 LOINC CODE\n \nencountering errors, during or post installation. The key element to \n61 TOPOGRAPHY FIELD\n61 TOPOGRAPHY FIELD .09 LEDI HL7\n61 TOPOGRAPHY FIELD .0961 TIME ASPECT\n \n62.05 URGENCY\n62.05 URGENCY 4 LEDI HL7\n \n62.4 AUTO INSTRUMENT\n62.4 AUTO INSTRUMENT .14 WKLD METHOD\n \nensuring a successful installation of the patch depends upon existing \n62.8 LAB SHIPPING MANIFEST\n62.801 SPECIMENS SUB-FIELD 1.14 PATIENT HEIGHT CODE\n62.801 SPECIMENS SUB-FIELD 1.24 PATIENT WEIGHT CODE\n62.801 SPECIMENS SUB-FIELD 2.14 COLLECTION VOLUME CODE\n62.801 SPECIMENS SUB-FIELD 2.24 COLLECTION DURATION CODE\n62.801 SPECIMENS SUB-FIELD 2.34 COLLECTION WEIGHT CODE\n62.801 SPECIMENS SUB-FIELD 1.13 PATIENT HEIGHT UNITS\n62.801 SPECIMENS SUB-FIELD 1.23 PATIENT WEIGHT UNITS\n62.801 SPECIMENS SUB-FIELD 2.13 COLLECTION VOLUME UNITS\n62.801 SPECIMENS SUB-FIELD 2.23 COLLECTION DURATION UNITS\nfiles not containing corrupt data. If corrupt data is present in the \n62.801 SPECIMENS SUB-FIELD 2.33 COLLECTION WEIGHT UNITS\n62.85 LAB SHIPPING EVENT .05 EVENT CODE\n \n62.9 LAB SHIPPING CONFIGURATION \n62.9001 TEST/PROFILE 1.15 PATIENT HEIGHT UNITS\n62.9001 TEST/PROFILE 1.25 PATIENT WEIGHT UNITS\n62.9001 TEST/PROFILE 2.15 COLLECTION VOLUME UNITS\n62.9001 TEST/PROFILE 2.25 COLLECTION DURATION UNITS\n62.9001 TEST/PROFILE 2.35 COLLECTION WEIGHT UNITS\n62.9001 TEST/PROFILE 1.16 PATIENT HEIGHT CODE\naffected files, when the fields are re-pointed during the post \n62.9001 TEST/PROFILE 1.26 PATIENT WEIGHT CODE\n62.9001 TEST/PROFILE 2.16 COLLECTION VOLUME CODE\n62.9001 TEST/PROFILE 2.26 COLLECTION DURATION CODE\n62.9001 TEST/PROFILE 2.36 COLLECTION WEIGHT CODE\n \n64.2 WKLD SUFFIX CODE\n64.2 WKLD SUFFIX CODE 1 WKLD SUFFIX CODE\n64.2 WKLD SUFFIX CODE 4 BILLABLE PROCEDURE\n64.2 WKLD SUFFIX CODE 7 COST\n64.2 WKLD SUFFIX CODE 8 PRICE\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \ninstallation update phase, errors will occur. Please read and follow all \n64.2 WKLD SUFFIX CODE 9 SORTING GROUP\n64.2 WKLD SUFFIX CODE 15 ACTIVATE WKLD CODE\n \n64 WKLD CODE\n64.02 TIME ASPECT SUB-FIELD .01 TIME ASPECT\n64.02 TIME ASPECT SUB-FIELD 1 UNITS\n \n68.2 LOAD/WORK LIST\n68.2 LOAD/WORK LIST .14 WKLD METHOD\n \nof the instructions outlined in this patch description.\n69.6 LAB PENDING ORDERS ENTRY\n69.6 LAB PENDING ORDERS ENTRY 6 SPECIMEN STATUS\n69.64 ORDERED TESTS SUB-FIELD 5 TEST STATUS\n \nResolving FM Verify Fields warnings instructions\n \nThe most common verify field errors are:\n1. Fields not properly cross referenced. This can be resolved by \nre-indexing the file.\n2. Fields failing input transform. This can be resolved by either editing \n***********************************************************************\nthe field and entering appropriate data; or deleting the existing data in \nthe field.\n \nNote: When performing FM Verify fields, an error will be produced in the \nTOPOGRAPHY FIELD((#61) file, SNOMED CODE (#2)field by the input transform \nlogic error.\nExample:\nENTRY# NAME ERROR\n1 RIGHT LUNG "28100" fails Input Transform\n ALREADY AN ENTRY\n \nThis input transform logic error will be corrected with the installation \nof this patch.\n** NO PRE-INSTALL CORRECTIVE ACTION IS REQUIRED. **\n \n \nWhen the Verify Field option is run on the various files, several \ndifferent kinds of warnings can be generated. It isn't possible to \ndescribe a resolution method for the type of warning discovered using the \nFM Verify field option, but here are some techniques used during testing. \nIf you require additional technical assistance, contact the EVS group.\nTechnical post-install notes are included at the end of the patch\n \nKnown problems:\n \nWKLD CODE (#64)\n========================\n--UNIT FOR COUNT-- POINTER\n \nENTRY# PROCEDURE ERROR\n1504 Shell Vial Technique No '68' in pointed-to File\n \ndescription. These technical notes can be used by the IRM service to \nThis broken pointer will be correct with the install. No action required.\n=======================\n--RELEASE DATE-- DATE\n \n1749 Misc Chem Test 5\n1 86023;ICPT( Missing\n \n1753 Misc Chem Test 9\n1 80100;ICPT( Missing\n \nprevent or resolve issues surrounding the installation of this patch. It \nEnter a release date to correct this problem.\n \n==========================\n \n--ACTIVATE WKLD CODE-\n \n SET OF CODES\n(CHECKING CROSS-REFERENCE)\n \nENTRY# PROCEDURE ERROR\nis impossible to anticipate all potential situations that exist; but the \n100074 Lactic Acid~ACA IV "1" not properly Cross-referenced\n \nRe-index the file will correct this problem.\n \n++++++++++++++++++\n \nTOPOGRAPHY FIELD (#61) File\n====================\nLEDI HL7 (#.09) field\n \nnotes address the most common. The key element ensuring successful \n POINTER\n(CANNOT CHECK CROSS-REFERENCE)\n \nENTRY# NAME ERROR\n22 KIDNEY "1275" fails Input Transform\n82 CILIARY GLAND "6417" fails Input Transform\n \nShould either delete the entry if not using this specimen or enter a \ncorrect entry.\n \ninstallation of the patch depends upon existing files not containing \n===========================\nVERIFY WHICH FIELD: SNOMED CODE \n \n FREE TEXT\n(CHECKING CROSS-REFERENCE)\n \nENTRY# NAME ERROR\n8729 TISSUE Missing\n8730 ORGANISM Missing\n \nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\ncorrupt data.\nEnter missing data, if input transform failure is reported this will be \ncorrected when patch is installed.\n \nThere is also a FM Verify field error 'fails Input Transform' in WKLD \nCODE (#64) file that will be corrected with the install of LR*5.2*302. \nThe screen preventing the selection of LOINC codes with Del (delete) \nstatus will be removed. This will allow LEDI sites to coordinate \ntransition from deprecated terms to active terms.\n The 'DEL' screen will be removed from the following 2 fields:\n DEFAULT LOINC CODE (#25) field.\n \n SPECIMEN (#20), sub-file TIME ASPECT (#30), LOINC CODE (#4) field.\nNO PRE-INSTALL CORRECTIVE ACTION IS REQUIRED for these errors.\n \nOther types of errors may require assistance from the EVS technical teams \nbefore proceeding.\n \nPRE-INSTALL ROUTINE\nNote: The pre-install routine will produce a listing of duplicate(s) \ncontained in WKLD CODE (#64) file if any are present.\n Those duplicates listed with a proceeding '*' SHOULD be resolved \nThis patch will update the WKLD CODE (#64) file and replace several \nbefore installation of the patch. However, the patch will install if the \nduplicates are present during installation.\n Those duplicates listed with a proceeding '+' will be deleted by the \npre-install program. No action is required.\n Those duplicates that do not have a preceding character will not \naffect the installation. Those entries that do not have a proceeding \ncharacter are locally created NLT codes and are provided to indicate to \nthe local user that multiples do exist. This information maybe useful \nwhen doing searches on the WKLD DATA (#64.1) file for a particular \ntest(s).\nlaboratory standardized files associated with National Laboratory Test \n \nExample of listing:\n Checking WKLD CODE file (#64) for duplicate names or numbers.\n \n+Blood Products Administration^2633\n+Blood Products Administration^3214\n \n+CPK MB/CPK Tot^3702\n+CPK MB/CPK Tot^3767\n \n(NLT) package and Logical Observation Identifier Naming Codes (LOINC) \n+Coagulation Factor VIII Inhib~BLOOD CENTER OF SE WISCONSIN^100873\nCoagulation Factor VIII Inhib~BLOOD CENTER OF SE WISCONSIN^100874\n \n*CPK MB/CPT Tot~BLOOD CENTER OF SE WISCONSIN^100973\n*CPK MB/CPT Tot~BLOOD CENTER OF SE WISCONSIN^100974\n \n+Hypersensitivity Pneumonitis^1557\n+Hypersensitivity Pneumonitis^1600\n \n+89026.0000 ^1600\ncoding. (See list below) This patch will remove certain WKLD CODE (#64) \n+89026.0000 ^2828\n End of duplicate listing.\n \n If '*' duplicates were listed they should be resolved before patch \ninstall.\n \n Those '+' will be removed during the post install.\n=====================\n \n \nfile duplicates. This patch will also correct certain field definitions \nRoutines:\n=====================\nLRDAGE\nThis patch contains a NEW age calculation routine, LRDAGE. This routine \nis used to calculate the age of the patient based on when the specimen \nwas collected instead of date of birth (DOB). For example, if the \nspecimen was collected one year ago, the age will be a year less than \ntoday's age. The routine is particularly useful in pediatric patient's \nnormal ranges. This age is used to determine the appropriate normal range \nbased on collection date. This patch expands the age format to include \nthat produce invalid warnings produced by the FileMan Verify Field \nday, month or year designation. This could affect the $SELECT statement \nevaluation of normal range. Sites are advised to review $SELECT statement \nin light of this age format. The format of the age is as follows:\n 1hr - 30 days = 1dy - 30dy\n 1 - 23 months = 1mo - 24mo\n >23 month = 2yr - 999yr\nThe default age of 99yr is return if a computation error occurs because \nof incorrect values passed to age API. Technical information for the API \ncall is contained in the routine documentation section.\n The functionality of this routine is not implemented by the patch \noption. In order to implement the numerous file/field corrections, it is \ninstallation. However, sites requiring the ability to determine age to \nthis degree, may wish to migrate their local M code in the EXECUTE CODE \n(#62.07) and DELTA CHECKS (#62.1) files to make use of this routine.\n \nRoutine Summary:\n================\n \nThe following is a list of the routine(s) included in this patch. The\n second line of each of these routine(s) will look like:\n \nnecessary to completely replace certain referenced NLT and LOINC files. \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \nRoutine Checksum Checksum\nName Before Patch After Patch Patch List\n ======= ============ =========== ==========\nLR302 N/A 7036526 302 (Deleted by KIDS)\nLR302A N/A 4415522 302\nLR302P N/A 3800106 302\n \nTo ensure that this patch does not introduce any new data validation \nLR302PO N/A 9375744 302\nLR302POA N/A 2988034 302\nLRDAGE 1480375 1454485 279,302\n \n \n \nASSOCIATED NOIS:\n ===============\n MAR-1104-21653\n \nerrors, it is desirable that the data currently stored pointing to \n TEST SITES:\n ==========\nLong Beach, CA VAMC\nDurham, NC VAMC\nSan Diego, CA VAMC\nMuskogee, OK VAMC\nCheyenne, WY\nHines, IL\nMartinsburg, WV\nBrockton, MA\nreplaced files is valid and errors resolved.\nBoston Health Care System\nCheyenne, WY\n \nRequired Builds:\n==========================\nLR*5.2*263\nLR*5.2*274\nLR*5.2*279\n \nInstallation Instructions: \n \n========================= \n \nThe patch LR*5.2*302 KIDS build file named LR52_302.KID stored in the \nASCII format can be obtained from the following Office of Information \nField Offices (OIFOs) ANONYMOUS SOFTWARE directories\nOIFO FTP Address Directory\nAlbany ftp.fo-albany.domain.ext anonymous.software \nHines ftp.fo-hines.domain.ext anonymous.software\nSalt Lake ftp.fo-slc.domain.ext anonymous.software\n \n \nAll users may remain on the system. Installation time is less than 30 \nminutes.\n \nNote: The patch should be installed during off peak hours.\n \nNo laboratory background jobs need to be stopped. No options need to be \nplaced out of service.\n \nLABORATORY USERS MUST NOT ACCESSION SPECIMENS OR ENTER/VERIFY RESULTS \nDURING THE INSTALLATION because several reference files are being deleted \nFile # File Name Update Method\nand replaced with this patch.\n \n \n============================ \n \nFrom the Kernel Installation & Distribution System (KIDS) menu \n \n 1. Use the 'Load a Distribution' option to load the \n LR_52_302.KID file onto your system.\n 2. The patch has now been loaded into a Transport global\n64.061 LAB ELECTRONIC CODES Replaced\n on your system. You now need to use KIDS to install\n the Transport global.\n On the KIDS menu, under the 'Installation' menu, use \n the following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 3. Users may remain on the system, but installation \n should be done at off peak hours.\n64.062 LAB ELECTRONIC SUBTYPES Replaced\n 4. Installation time is less than 30 minutes during off \n peak hours and less than 45 minutes during peak hours.\n 5. Installation of this patch requires no additional \n memory space.\n 6. From the 'Installation Menu' of the KIDS menu, run the \n option\n 'Install Package(s)' Select the package 'LR*5.2*302' \n and proceed with the install.\n 7. When prompted 'Want KIDS to INHIBIT LOGONS during the\n install? YES//' respond NO.\n64.2 WKLD SUFFIX CODES Replaced\n 8. When prompted 'Want to DISABLE scheduled Options, Menu\n Options, and Protocols? YES//' respond NO.\n \n \n================\nExample of install:\n \n Select Installation Option: LOAD a Distribution\nEnter a Host File: LR_52_302.KID\n \n64.3 WKLD INSTRUMENT MANUFACTURER Replaced\nKIDS Distribution saved on Dec 09, 2004@04:27:46\nComment: NLT/LOINC v2.13 Update\n \nThis Distribution contains Transport Globals for the following Package(s):\n LR*5.2*302\n \nOK to continue with Load? NO// YES\n \nDistribution OK!\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*302 does not \n64.81 LAB NLT/CPT CODES Replaced\nWant to Continue with Load? YES// \nLoading Distribution...\n \nBuild LR*5.2*302 has an Enviromental Check Routine\nWant to RUN the Environment Check Routine? YES// \n \n LR*5.2*302\nWill first run the Environment Check Routine, LR302\n \n \n95.3 LAB LOINC Replaced\n Checking WKLD CODE file (#64) for duplicate names or numbers\n \n End of duplicate listing.\n \n If duplicates were listed they should be resolved before patch install \n \n --- Environment Check is Ok ---\n \n Sending install loaded alert to mail group G.LMI\n \n95.31 LAB LOINC COMPONENT Replaced\n \nUsing VA FileMan menu "UTILITY FUNCTIONS",\n perform the option "VERIFY FIELDS",\n \n MODIFY WHAT FILE: WKLD CODE\n \n VERIFY WHICH FIELD: ALL\n \n DO YOU MEAN ALL THE FIELDS IN THE FILE? YES\n \n \nEnsure that this option runs CLEANLY before installation of this patch.\n \n \nUse INSTALL NAME: LR*5.2*302 to install this Distribution.\n \n \nSelect Installation Option: VERify Checksums in Transport Global\nSelect INSTALL NAME: LR*5.2*302 Loaded from Distribution \n12/9/04@01:53:23\n => NLT/LOINC v2.13 Update ;Created on Dec 09, 2004@04:27:46\n*64 WKLD CODE Updated with new terms.\n \nThis Distribution was loaded on Dec 09, 2004@01:53:23 with header of \n NLT/LOINC v2.13 Update ;Created on Dec 09, 2004@04:27:46\n It consisted of the following Install(s):\n LR*5.2*302\nDEVICE: HOME// TELNET TO ALPHAS\n \n \n 6 Routine checked, 0 failed.\n \n \n \nSelect Installation Option: INStall Package(s)\nSelect INSTALL NAME: LR*5.2*302 \n => NLT/LOINC v2.13 Update ;Created on Dec 09, 2004@04:27:46\n \nThis Distribution was loaded on Dec 09, 2004@01:53:23 with header of \n NLT/LOINC v2.13 Update ;Created on Dec 09, 2004@04:27:46\n It consisted of the following Install(s):\n LR*5.2*302\nChecking Install for Package LR*5.2*302\n============================\nWill first run the Environment Check Routine, LR302\n \n \n Checking WKLD CODE file (#64) for duplicate names or numbers\n \n End of duplicate listing.\n \nIf duplicates were listed they should be resolved before patch install \n \n --- Environment Check is Ok ---\nLOINC Copyright acknowledgement:\n \n Sending install loaded alert to mail group G.LMI\n \n \n Using VA FileMan menu "UTILITY FUNCTIONS",\n perform the option "VERIFY FIELDS",\n \n MODIFY WHAT FILE: WKLD CODE\n \n VERIFY WHICH FIELD: ALL\nLOINC was Copyrighted 1995, 1996, 1997, by Regenstrief Institute and the \n \n DO YOU MEAN ALL THE FIELDS IN THE FILE? YES\n \nEnsure that this option runs CLEANLY before installation of this patch. \n \nInstall Questions for LR*5.2*302\n \nIncoming Files:\n \n 61 TOPOGRAPHY FIELD (Partial Definition)\nLogical Observation Identifier Names and Codes (LOINC) Committee. All \nNote: You already have the 'TOPOGRAPHY FIELD' File.\n \n 64 WKLD CODE\nNote: You already have the 'WKLD CODE' File.\n \n 64.061 LAB ELECTRONIC CODES (including data)\nNote: You already have the 'LAB ELECTRONIC CODES' File.\nI will OVERWRITE your data with mine.\n \n 64.062 LAB ELECTRONIC SUBTYPES (including data)\nalter or modify any software design safeguards or safety critical \nrights reserved. LOINC is a trademark of the Regenstrief Institute.\nNote: You already have the 'LAB ELECTRONIC SUBTYPES' File.\nI will OVERWRITE your data with mine.\n \n 64.2 WKLD SUFFIX CODES (including data)\nNote: You already have the 'WKLD SUFFIX CODES' File.\nI will OVERWRITE your data with mine.\n \n 64.21 WKLD CODE LAB SECT (including data)\nNote: You already have the 'WKLD CODE LAB SECT' File.\nI will OVERWRITE your data with mine.\nContact information:\n \n 64.22 WKLD ITEM FOR COUNT (including data)\nNote: You already have the 'WKLD ITEM FOR COUNT' File.\nI will OVERWRITE your data with mine.\n \n 64.3 WKLD INSTRUMENT MANUFACTURER (including data)\nNote: You already have the 'WKLD INSTRUMENT MANUFACTURER' File.\nI will OVERWRITE your data with mine.\n \n 64.81 LAB NLT/CPT CODES (including data)\nLOINC\nNote: You already have the 'LAB NLT/CPT CODES' File.\nI will OVERWRITE your data with mine.\n \n 68.2 LOAD/WORK LIST\nNote: You already have the 'LOAD/WORK LIST' File.\n \n 95.3 LAB LOINC (including data)\nNote: You already have the 'LAB LOINC' File.\nI will OVERWRITE your data with mine.\n \nC/o Regenstrief Institute\n 95.31 LAB LOINC COMPONENT (including data)\nNote: You already have the 'LAB LOINC COMPONENT' File.\nI will OVERWRITE your data with mine.\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options,Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n1001 West 10th Street, RHC-5\n \nDEVICE: HOME// TELNET TO ALPHAS\nComplete \nLR*5.2*302 \n \n Install Started for LR*5.2*302 : \n Dec 09, 2004@01:57:39\n \nBuild Distribution Date: Dec 09, 2004\n \nIndianapolis, Indiana 46202 USA\n Installing Routines: \n Dec 09, 2004@01:57:39\n \n Running Pre-Install Routine: PRE^LR302 \n ** Saving Pointer Values **\n \n Saving File #60 data.\n \n Saving File #61 data.\n \n \n Saving File #62.05 data.\n \n Saving File #62.4 data.\n \n Saving File #62.8 data.\n \n Saving File #62.85 data.\n \n Saving File #62.9 data.\n \n========================\n Saving File #64.2 data.\n.......\n Saving File #68.2 data.\n \n Saving File #69.6 data.\n.......................................................................\n \n *** Preinstall completed ***\n \n Installing Data Dictionaries: \nVistA Laboratory Package LAB LOINC (#95.3) file does not support all of \n Dec 09, 2004@01:59:41\n \n Installing Data: \n Dec 09, 2004@02:04:45\n \n Running Post-Install Routine: POST^LR302 \n \n Updating DSS Feeder Key for AP NLT Codes\n \n Update DSS AP Feeder Key Complete\nthe fields contained in the LOINC database. Refer to the LOINC user's \n \n \n Building List Of Added NLT CODEs\n \n Sending message to LMI Mail Group.\n \n List Of Added WKLD CODEs Complete\n \n Processing data for File/Subfile #60.01\n \nelements functions. \nmanual for more field details. The following fields are imported and \n Processing data for File/Subfile #61\n \n Processing data for File/Subfile #62.05\n \n Processing data for File/Subfile #62.4\n \n Processing data for File/Subfile #62.85\n \n Processing data for File/Subfile #64.2\n ............\nsupported within VistA.\n Processing data for File/Subfile #68.2\n \n Processing data for File/Subfile #69.6\n.......................................................................\n \n Processing data for File/Subfile #69.64\n.......................................................................\n \n Historical data restored \n \n \n Sending install completion alert to mail group G.LMI\n \n \nLR*5.2*302 \n--------------------------------------------------\n Using VA FileMan menu "UTILITY FUNCTIONS",\n perform the option "VERIFY FIELDS", \n \n MODIFY WHAT FILE: WKLD CODE\n \n# Loinc Term VistA name\n VERIFY WHICH FIELD: ALL\n \n DO YOU MEAN ALL THE FIELDS IN THE FILE? YES \n \n \n Updating Routine file... \n \n Updating KIDS files... \n \n LR*5.2*302 Installed. Dec 09, 2004@02:13:10\n1 LOINC_NUM CODE + CHECK DIGIT\n \nInstall Completed\n \nLoading of patch LR*5.2*302 completed on Dec 09, 2004@01:57:10\nLIM: Review description for LR*5.2*302 use KIDS:Utilities: Build File \nPrint\n \nInstallation of patch LR*5.2*302 completed on Dec 09, 2004@02:13\n \n \n2 COMPONENT COMPONENT + LAB LOINC COMPONENT (95.31)\n POST INSTALLATION INSTRUCTIONS:\n =============================\nReview installed LOINC codes to ensure that codes with the status of \nDeprecated (DEL) are not used in your current mapping of LOINC codes. In \nsome cases, deprecated LOINC codes [LAB LOINC (#95.3) file, MAP TO (#21) \nfield] will have the suggested replacement LOINC code populated.\nNote:\nIf your site is a HOST LEDI site, changing of any LOINC or NLT codes \nshould be coordinated the collection site to ensure that both sites agree \nin LOINC and NLT mappings.\n3 PROPERTY PROPERTY\n \nLR*5.2*302 Technical Install Notes:\n=========================\n \nThis patch is attempting to clean-up the following files:\nFile # File Name Update Method\n64.061 LAB ELECTRONIC CODES Replaced\n64.062 LAB ELECTRONIC SUBTYPES Replaced\n64.2 WKLD SUFFIX CODES Replaced\n64.3 WKLD INSTRUMENT MANUFACTURE Replaced\n4 TIME_ASPECT TIME ASPECT\n64.81 LAB NLT/CPT CODES Replaced\n95.3 LAB LOINC Replaced\n95.31 LAB LOINC COMPONENT Replaced\n \n*64 WKLD CODE Updated\n \n \n \nThe currently installed files are not compatible with the incoming LOINC \nV2.13. Therefore these files are being completely removed and a fresh \n5 SYSTEM SYSTEM\nversion is being installed. When the new versions are installed certain \npointers in other files could be broken or incorrect.\n \nTo address this problem, the pre-install routine will save the existing \ndata in external format in the ^XTMP("LR302",FILE,IEN,FLD)=DATA\nThis file will be purged in 90 days.\nAll the fields that point to the replaced files will be saved before the \nold files are purged.\n \nThe post-install routine will:\n6 SCALE_TYPE SCALE TYPE\n1) Add any missing WKLD CODE to your system and create a mail message \ncontaining the added codes. If this process is successful the LAB NLT/CPT \nCODES (#64.81) should be empty of WKLD CODES.\n \n2) Compare your previous WKLD SUFFIX CODES (#64.2) to the file installed \nby the patch. A MailMan message is created listing any locally added. \nThese codes must be requested via the mail group indicated in the patch \ndescription. Codes should not be locally added to any of the NLT Package \nfiles.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*302 have no effect on Blood \n7 METHOD_TYPE METHOD TYPE\n3) Re-index WKLD CODE file\n \n4) Re-point the fields stored in the ^XTMP("LR302",FILE,IEN,FLD)=DATA \nfile. If errors occur during the re-pointing process the wording "ERROR" \nwill appear during the post-install.\nThe error is stored in this format.\n \nS ^XTMP("LR302","LRERR",LRCNT)=LRFILE_U_LRIEN_U_LRFLD_U_LRDATA\n \nThe file will be purged in 90 days.\n9 CLASS CLASSTYPE\nYou will have to manually enter the appropriate value.\n10 SOURCE SOURCE\n14 DT_LAST_CH DATE LAST CHANGED\n15 CHNG_REAS CHANGE REASON\n16 CHNG_TYPE CHANGE TYPE\n19 STATUS STATUS\n20 MAP_TO MAP TO\n23 VA_CD VA CODE\n59 SHORTNAME SHORTNAME\nBank software functionality, therefore RISK is none.\n \n \nBecause several standardized files are being completely replaced, the \npre-install routine will extract and save the values of the fields \npointing to the replaced files. \n \nThe complete WKLD SUFFIX CODES (#64.2) file is saved into \n^XTMP("LRNLT642") global for 90 days. The ^XTMP("LRNLT642") file can be \nused to assist those sites that may have mistakenly added terms to the \n(#64.2) file. Those local terms not included in the installed file should \n\n\nBlood Bank Clearance\n \n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\nSee LABORATORY POINT OF CARE (POC) INTERFACE INSTALLATION AND USER GUIDE\n PATCH LA*5.2*67 AND PATCH LR*5.2*290 Version 5.2 JUNE 2005\n \nSoftware and Documentation Retrieval Locations\n============================================== \nRISK ANALYSIS: Changes made by patch LR*5.2*290 have no effect on Blood\n \nNOTE: All sites are encouraged to use the File Transfer Protocol (FTP)\ncapability. Use the FTP address "download.vista.domain.ext" (without the\nquotes) to connect to the first available FTP server where the files are\nlocated.\n \n \nVistA Point of Care (POC) Interface Patches LR*5.2*290 and LA*5.2*67\nsoftware and Installation and User Guide are available at the following\nOffice of Information Field Offices (OIFOs) ANONYMOUS.SOFTWARE directories:\nBank software functionality, therefore RISK is none. \n \n \nOI FIELD OFFICE FTP ADDRESS DIRECTORY\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \nSoftware and Documentation Retrieval Format\n===========================================\n \n \nVistA Laboratory Point of Care (POC) Interface Patches LR*5.2*290 and\nLA*5.2*67 software and documentation files are exported in the following\nretrieval formats:\n \n \nFile Names Contents Retrieval Formats\n========== ======== =================\n \nLAB_POC.KID KIDS build ASCII\n=========================================\n \nLAB_52_LR290_LA67_POC_IUG.pdf Laboratory Point of Care BINARY\n (POC) Interface Patches\n LR*5.2*290 and LA*5.2*67\n Installation and User Guide\n \nLAB _52_LR290_LA67_POC_IUG.doc Laboratory Point of Care BINARY\n (POC) Interface Patches\n LR*5.2*290 and LA*5.2*67\n Installation and User Guide\n \n \nLAB_52_POC_HL7_SPEC.doc Laboratory HL7 Interface BINARY\n Specification for Point of\n Care (POC)\n \nLAB_52_POC_HL7_SPEC.pdf Laboratory HL7 Interface BINARY\n Specification for Point of\n Care (POC)\n \n \nThis patch adds support for Laboratory Point of Care (POC) interfaces.\n \nPOST-INSTALLATION INSTRUCTIONS\n------------------------------\nSee LABORATORY POINT OF CARE (POC) INTERFACE INSTALLATION AND USER GUIDE\n PATCH LA*5.2*67 AND PATCH LR*5.2*290 Version 5.2 JUNE 2005\n \n \nINSTALLATION EXAMPLE\n====================\n \nIt utilizes existing functionality provided by Laboratory Universal\nSee LABORATORY POINT OF CARE (POC) INTERFACE INSTALLATION AND USER GUIDE\n PATCH LA*5.2*67 AND PATCH LR*5.2*290 Version 5.2 JUNE 2005\nInterface (UI) and Laboratory Electronic Data Interchange (LEDI) software.\nIt supports the transmission, processing and storing of POC test results\n====================\nin the VistA Laboratory package. The ability of POC interfaces to subscribe\nto VistA HL7 ADT messages for patient demographics and location information\nis provided as needed.\n \n \nNOTE: THIS PATCH WILL BE INSTALLED WITH LA*5.2*67\n \n \n1. Laboratory orders created by this interface will have a CPRS Nature of\nOrder 'AUTO' assigned.\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*290 does not\n \n2. It creates a 'non-human' user 'LRLAB,POC' in NEW PERSON file (#200)\nwhich is used to create the order and accession associated with the point\nof care test result. This entry has been approved by the VA VistA Data Base\nAdministrator. Local site personnel should assign divisions to this user \nthat corresponds to the accession areas used for POC results.\n \n3. Options Summary list (supervisors') [LR SUP SUMMARY] and Summary list\n(extended supervisors') [LRLISTE] have been modified to display the\nperforming user, performing laboratory, LOINC code and Equipment Instance\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\nIdentifier (EII) for each test result when the long or extended format is\nchosen. The EII contains the vendor's make/model/serial number of the \ninstrument/equipment that produced the test result. When the vendor's\ninstrument interface transmits this information, it will be stored with\nthe test results.\n \n4. CPRS Lab Display of Recent Results will display performing laboratory\nname and address of tests in accordance with College of American Pathology\n(CAP) requirements. Routine LR7OGMG was modified to add performing\nlaboratory information to comments section of the CPRS display.\nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n5. NOIS MAR-0105-20968 reported the CPRS Lab Worksheet did not display the\nexternal value of 'set of codes' data types. Values that are set of codes\nwill be displayed using the external value of the set of codes. Routine\nLR7OGG was modified to return external values of set of codes to CPRS.\n \n \nASSOCIATED E3R\n--------------\n \n \n \nASSOCIATED NOIS/Remedy Ticket\n-----------------------------\nMAR-0105-20968/HD0000000071181\nSBY-0501-32827/HD0000000069437 \n \n \nTEST SITES\n----------\n Madison VAMC\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*290 does not\n New Jersey HCS\n Salt Lake City VAMC\n Shreveport VAMC\n Upstate New York System HCS\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\nalter or modify any software design safeguards or safety critical elements\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR290 N/A 4831439 **290** (Deleted by KIDS)\n LR7OGG 11097271 10933227 **187,290**\n LR7OGMG 3973477 5478031 **187,230,286,290**\n LRDIQ 10128715 2599216 **86,153,263,290**\n LRGP2 6353513 6108916 **153,221,263,290**\nfunctions.\n LRORDST 14420120 12502665 **100,107,121,153,202,290**\n LROW2 8572259 8727104 **121,290**\n LRUER 12281075 11948802 **201,290**\n LRVRPOC N/A 10290202 **290**\n LRVRPOCU N/A 8876916 **290**\n LRWLST 17313871 14863929 **46,65,100,121,153,202,\n 290**\n LRX 13923654 15315863 **65,153,201,217,290**\n \n List of preceding patches: 202, 217, 263, 286\n\n
\nBlood Bank Clearance:\n\n\nBEFORE:\n\n63.04,.111 REQUESTING LOC/DIV 0;13 VARIABLE POINTER\n \n FILE ORDER PREFIX LAYGO MESSAGE\n 44 1 SC( n Hospital Location \n 4 2 DIC(4, n Ordering Institution \n SCREEN ON FILE 4: S DIC("S")="I $G(^DIC(4,Y,99)),$G(^DIC(4,Y,6)\n )"\nRISK ANALYSIS: Changes made by patch LR*5.2*257 have no effect on Blood Bank\n\n LAST EDITED: FEB 01, 1997 \n HELP-PROMPT: Enter the hospital location or institution \n ordering this test. \n DESCRIPTION: This is the hospital location or institution\n ordering this test. \n\nAFTER:\n\n63.04,.111 REQUESTING LOC/DIV 0;13 VARIABLE POINTER\nsoftware functionality, therefore RISK is none.\n\n FILE ORDER PREFIX LAYGO MESSAGE\n 44 1 SC( n Hospital Location \n 4 2 DIC(4, n Ordering Institution \n\n LAST EDITED: FEB 01, 1997 \n HELP-PROMPT: Enter the hospital location or institution \n ordering this test. \n DESCRIPTION: This is the hospital location or institution\n ordering this test. \n\n\n\nSoftware Retrieval\n==================\nVistA Laboratory Multidivisional Antimicrobial Trend Report LR*5.2*257 is\ndistributed by Packman. \n\n\nDocumentation Retrieval Locations:\n==================================\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made,\nNOTE: All sites are encouraged to use the File Transfer Protocol (FTP)\ncapability. Use the FTP address "download.vista.domain.ext" (without the\nquotes) to connect to the first available FTP server where the files are\nlocated.\n\nVistA Laboratory 5.2 User Manual and VistA Laboratory Planning and\nImplementation Guide with change pages are available at the following\nOffice of Information Field Offices (OIFOs) ANONYMOUS.SOFTWARE directories:\n\n OI FIELD OFFICE FTP ADDRESS DIRECTORY\nno specific validation requirements exist as a result of installation of this\n---------------------------------------------------------------\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n\nDocumentation Retrieval Format\n==============================\nVistA Laboratory 5.2 User Manual and Vista Laboratory 5.2 Planning and\nImplementation Guide with change pages are exported in the following\nretrieval formats:\npatch.\n\n File Names Contents Retrieval Formats\n-------------------------------------------------------------------------\nlab5_2um.doc Laboratory 5.2 User Manual BINARY \n\n\nlab5_2pi.doc Laboratory 5.2 Planning and BINARY\n Implementation Guide\n\n\n\nVistA Website Locations:\n========================\nThe Laboratory 5.2 User Manual and Laboratory 5.2 Planning and Implementation\nGuide with change pages are accessible at the following locations:\n\nLaboratory Version 5.2 Home Page\n---------------------------------\nhttp://vista.domain.ext/ClinicalSpecialties/lab/\n\nVistA Documentation Library (VDL)\nThis patch provides the ability to print an Antimicrobial Trend Report by\n---------------------------------\nhttp://www.domain.ext/vdl/\n\n\n\nRelated NOIS/Remedy: \n====================\n FGH-0200-31523/HD0000000069224\n ALB-0600-50112/HD0000000069278\n\ndivision. There are three new additions to the LAB DATA (#63) file-\n\nE3RS:\n=====\n 11438\n\nTest Sites:\n===========\n Durham, NC\n Gainesville, FL\n VA Boston Healthcare System\n=====================\none new field for the "CH" subscript and two new fields for the "MI" subscript.\n\n\nROUTINE SUMMARY:\n================\nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n\n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n\n CHECK^XTSUMBLD results\nThese fields will be used to capture the ordering location and institution\nRoutine name Before Patch After Patch Patch List\n============ ============ =========== ==========\nLR257 NONE 2442358 257(Deleted by\n KIDS) \nLRMITSE 6478419 8737276 96,257\nLRMITSES 7787667 7819718 96,257\nLRMITSPE 6091299 7314510 96,257\nLRMITSPS 3052409 3271788 257\nLRMITSR 11570196 11570170 96,257\nLRMITSRH 2059425 2320614 257\nduring accessioning. In the MICROBIOLOGY (#63.05) sub-file of the LAB DATA \n\n\nINSTALLATION INSTRUCTIONS\n=========================\n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n\n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n(#63) file, the new fields are REQUESTING LOC/DIV (#63.05,.111) and\n\n 1. If any of the above routines are mapped, disable mapping for them.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n\n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation ' menu.\n\n 4. Use the 'Verify Checksum in Transport Global' option and verify that\nACCESSIONING INSTITUTION (#63.05,.112). In the CHEM, HEM, TOX, RIA, SER,\n all routines have the correct checksums.\n\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*257'. When prompted 'Want KIDS to\netc. (#63.04) sub-file of the LAB DATA (#63) file, the new field is\n INHIBIT LOGONS during the install? YES//', choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'. When prompted 'Want KIDS to Rebuild Menu Trees\n Upon Completion of Install? YES//"', choose 'NO'.\n\n 7. On a mapped system, rebuild your map set.\n\nNOTE: Routine LR257 will be deleted after successful patch installation.\nACCESSIONING INSTITUTION (#63.04,.112). In the CHEM, HEM, TOX, RIA, SER, etc.\n(#63.04) sub-file of the LAB DATA (#63) file, the REQUESTING LOC/DIV\n(#63.04,.111) field is modified to remove the screen on INSTITUTION file (#4)\nsince sites need to be able to point to entries in the INSTITUTION file (#4)\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*257 does not\nthat are not VA facilities such as DoD and commercial/civilian facilities.\n\nALB-0600-50112/HD0000000069278:\nPatch LR*5.2*257 also corrects two typographical errors. The query portion of\nthe Microbiology Trend Entry routine has two typographical errors. The word\nmisspelled as susceptability should be susceptibility. Also, the misspelled\nword procede should be proceed.\n\nMODIFIED OPTION\n===============\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\nNAME: LRMITS MENU TEXT: Microbiology Trend Report\n TYPE: run routine\n HELP FRAME: LRMITS OPTION PACKAGE: LAB SERVICE\nDESCRIPTION: The antimicrobial trend report is used to compare counts of\norganisms and patterns of antibiotic susceptibility. Different types of\nreports can be generated. The types of reports are categorized by: organism,\nspecimen, collection sample, patient, physician, and location. Specific\ncriteria can be applied to all report types. Criteria include: specific types\nof organisms, isolates collected after a specified time from admission, merge\ncriteria, antibiotic patterns, and detailed reports. These reports can be\nDIRECTIVE 99-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nprinted by division or selected divisions.\n ROUTINE: LRMITS\n\n\n\nDATA DICTIONARY CHANGES:\n========================\n\nNEW FIELDS:\n===========\n\n\nIn the MICROBIOLOGY (#63.05) sub-file of the LAB DATA (#63) file: \n\n63.05,.111 REQUESTING LOC/DIV 0;13 VARIABLE POINTER\n\n FILE ORDER PREFIX LAYGO MESSAGE\n 44 1 SC( n Enter Hospital Location \n 4 2 DIC(4, n Select appropriate Institution \n \n LAST EDITED: AUG 04, 2004 \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*257 does not alter\n DESCRIPTION: Enter the hospital location or institution\n ordering this test. \n\n63.05,.112 ACCESSIONING INSTITUTION 0;14 POINTER TO INSTITUTION FILE (#4)\n\n LAST EDITED: AUG 04, 2004 \n DESCRIPTION: This field contains the pointer to the\n institution where the specimen was accessioned.\n This field can be blank if LEDI or POC specimen \n is accessioned. The field will be set if an\nor modify any software design safeguards or safety critical elements\n actual user accepts the specimen. \n\nIn the CHEM, HEM, TOX, RIA, SER, etc. (#63.04) sub-file of the LAB DATA (#63)\nfile:\n\n63.04,.112 ACCESSIONING INSTITUTION 0;14 POINTER TO INSTITUTION FILE (#4)\n\n LAST EDITED: AUG 04, 2004 \n DESCRIPTION: This field contains the pointer to the\n institution where the specimen was accessioned.\nfunctions.\n This field can be blank if LEDI or POC specimen \n is accessioned. The field will be set if an\n actual user accepts the specimen. \n\n \nMODIFIED FIELD:\n===============\n\nIn the CHEM, HEM, TOX, RIA, SER, etc. (#63.04) sub-file of the LAB DATA (#63)\nfile:\n\n\nDuring the verification of Micro Data, an undefined error has occurred at \nline APP+5^LRMIUT1. This patch corrects this defect.\n\n
\nBlood Bank Clearance\nfunctions.\n a. Print Transport Global\n b. Backup a Transport Global\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*330'. When prompted 'Want KIDS to\n \n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n \n The install will automatically disable the following options:\n \n Accession order then immediately enter data [LR ACC THEN DATA]\n Batch data entry (chem, hem, tox, etc.) [LRSTUF]\n Bypass normal data entry [LRFAST]\n Enter/verify data (Load list) [LRVRW2]\nRISK ANALYSIS: Changes made by patch LR*5.2*330 have no effect on Blood\n Enter/verify data (Work list) [LRVRW] \n Enter/verify data (auto instrument) [LRVR]\n Fast Bypass Data Entry/Verify [LRFASTS]\n Group verify (EA, EL, EW) [LRGV]\n Special test accessioning [LRNONCOM]\n Group data review (verified & EM) [LRGVP] \n \n 6. On a mapped system, rebuild your map set.\n \n Note: Routine LR330 will be deleted after successful patch installation.\nBank software functionality, therefore RISK is none.\n \n \nINSTALLATION EXAMPLE\n====================\n \nSelect Installation Option:\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: Install Package(s)\n \nSelect INSTALL NAME: LR*5.2*330 Loaded from Distribution Loaded from\nDistribution 1/24/05@13:44:22\n => LR*5.2*330\n \nThis Distribution was loaded on Jan 24, 2005@13:44:22 with header of\n LR*5.2*330\n It consisted of the following Install(s):\n LR*5.2*330\nChecking Install for Package LR*5.2*330\nWill first run the Environment Check Routine, LR330\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*330\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\nmade, no specific validation requirements exist as a result of installation\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET\nof this patch.\n \n \n Install Started for LR*5.2*330 :\n Jan 24, 2005@13:46:54\n \nBuild Distribution Date: Jan 24, 2005\n \n Installing Routines:\n Jan 24, 2005@13:46:54\n \n--------------------------------------------------------------------------\n Running Pre-Install Routine: PRE^LR330\n \n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n \n Installing OPTION\n Jan 24, 2005@13:46:54\n \n LR*5.2*330\n \n Running Post-Install Routine: POST^LR330\n \n *** Post install started ***\n \n *** No action required ***\n==================== \n \n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*330 Installed.\nNOIS FAV-0105-71385 reported the inability to verify Laboratory Electronic\n Jan 24, 2005@13:46:55\n \n Install Message sent #3905\n \n Install Completed\nData Interchange (LEDI) results when one or all of the lab results being\nprocessed have 'comment' as the result. Functionality, released in patch\nLR*5.2*286, to prevent editing of reference laboratory results using option\nEnter/verify data (auto instrument) [LRVR] prevented user from releasing\nLEDI results.\n \nNOIS ASH-0105-31055 reported the inability to verify LEDI results when\none or all of the lab results being processed have 'canc' as the\n \nresult. Functionality, released in patch LR*5.2*286, to prevent\nediting of reference laboratory results using option Enter/verify data\n(auto instrument) [LRVR] prevented user from releasing LEDI results.\n \nThis patch allows users verifying reference laboratory results to\nrelease results that consist only of 'comment' or 'canc' type results.\n \n \n \n ASSOCIATED E3R\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*330 does not\n --------------\n None\n \n ASSOCIATED NOIS\n ---------------\n ASH-0105-31055/Remedy ticket HD0000000071185\n FAV-0105-71385/Remedy ticket HD0000000071204\n \n \n TEST SITES\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n ----------\n \n Asheville VAMC (Medium site) \n Boston HCS (Integrated/Large site)\n Fayetteville AR, VAMC (Medium site)\n Milwaukee VAMC (Large site)\n New Orleans VAMC (Large siet)\n \n \nROUTINE SUMMARY\nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR330 N/A 4831418 **330** (Deleted by KIDS)\n LRVR4 9645653 9819762 **14,42,121,153,221,263,\n \n 279,283,287,286,330**\n \n List of preceding patches: 286\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*330 does not\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \nalter or modify any software design safeguards or safety critical elements\n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*330):\n\n
\nThis patch will up date the LR reference to Person Class codes to conform \nwith the new codes released in XU*8*377.\n\n
\nThis patch updates the retrieval of Lab Results to only return verified \nResults when called on by CPRS via the Orders tap. \n \nThis patch removes unused Blood Bank functionality from the routine LR7OR1\nin support of the VBECS (Vista Blood Establishment Computer Software) \nBlood Bank Modernization Project.\n\n
\nThe three problems addressed in this patch were originally described in\nthe following NOIS calls:\nDAY-0204-42022 - EN+13~LRUPS undefined variable\nBHS-0804-11324 - <UNDEFINED>B+2^LRAUDA ERROR\nLON-0904-61172 - MAJOR SECTION REPORT, BOTH SCROLLING AND PRINTING\n\n
\nMultidivisional Printer Problems- This patch is for multidivisional sites that\nwish to print lab collect order copies at separate divisions. Also, this\npatch allows the site to change the default label printer from LABLABEL to\na division specific printer.\n\n
\nSTOP SNOMED CODING OLD AP REPORTS FROM SENDING ALERTS\n\n
\nTHIS IS A PATCH TO A PATCH (324) IT CORRECTS AN UNDEFINDED ERROR. THE \nPREVIOUS PATCHES ARE NOT REQUIRED SINCE THEY CAUSED ERRORS.\n\n
\nThis patch updates routine LRUMD to only include patients in the \nrequested sorting group when printing the data by test list.\n\n
\nThis patch corrects a problem with Batch Data Entry where\nexecutable code in a delta check is not executed.\n\n
\nTHIS CORRECTS A CODE ERROR IN 340, THE STATEMENT WAS IF 'X WHICH ONLY \nWORKS WHEN X IS NUMERIC. IN THIS CASE IT WAS ALPHA NUMERIC. THE \nSTATEMENT WAS CHANGED TO IF X="". X IS EXAMPLE VARIABLE.\n\n
\nThis patch corrects problems with the way reference ranges are\ndisplayed in search options and in CPRS and also fixes a bug \nwhich generates a SYNTAX error in option LRSORA (Search for HI/Lo\nValues). The patch also fixes a problem with the Microbiology\nTrend Report where no data is printed when specific locations are\nselected.\n\n
\nThis patch corrects 3 reporting problems: one with the Critical\nValue Report, one with Workload Code List Report, and one with\nthe Print List of Non-Draw Orders.\n\n
\nThis patch corrects report print problems with Reprint a WARD\nCollect Order and with Sum of Accessions by Date - AP\n\n
\nDescription:\n============\nThis patch will add a new Kernel look-up screen to the Laboratory Site\nfile (#69.9) in support of Orders Data Standardization.\n\n
\nINCORRECT OOS (OCCASION OF SERVICE) LOCATION GOING TO PCE\n\n
\nVISTA Laboratory Clinical Indicator Data Capture (Patch LR*5.2*291)\n\n
\nThis patch corrects a SUBSCRIPT error causing the HAM report to error\nout.\n\n
\nThis patch corrects 2 seperate problems in 3 different Remedy tickets.\n\n
\nThis patch corrects a data integrity problem caused by an input\ntransform setting data at the wrong global node and removes a\nmenu option that is obsolete.\n\n
\nThis patch corrects problems with the LEDI Turnaround Time Report and\nthe Worksheet Accession List.\n\n
\nADDING NEW LAB TEST WITH DOUBLE QUOTES\n\n
\nBlood Bank Team Coordination\n \nN/A\n \n \nAssociated PSI:\n===============\nPSI-05-068 \n \n \nTest Sites\n==========\nAll of the above changes have been reviewed by the VISTA Blood Bank \nDURHAM, NC -VAMC (Large site)\nNORTHERN CALIFORNIA HCS (Large site) \n \n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;; 5.2;LAB SERVICE;<patch list>;Sep 27, 1994\nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE \n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n LR343 N/A 12851791 343\n LR7OEVNT 5021306 deleted by KIDS\n \n Routines deleted by KIDS: LR343,LR70EVNT\n List of preceding patches: n/a\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \ncontrol functions.\n \nPROTOCOLS\n LR7O MOVEMENT EVENT (deleted)\n LR7O MOVEMENT EVENT TASK (deleted)\n \n \nDATA DICTIONARIES\n LABORATORY SITE file (#69.9)\n CANCEL ON ADMIT field (#150.3) (deleted)\n CANCEL ON DISCHARGE field (#150.4) (deleted)\n \n CANCEL ON SPECIALTY TRANSFER field (#150.5) (deleted)\n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \n The install time for this patch is approximately 6 minutes.\n Suggested time to install: non-peak requirement hours.\n This patch can be installed when Laboratory users are on the system.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*343 have no effect on Blood \n \n I M P O R T A N T\n =============================\n THIS INSTALLATION MUST BE QUEUED\n \n \n NOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\nBank software functionality, therefore RISK is none.\n Information Manager (LIM/ADPAC).\n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 3. Use the 'Verify Checksum in Transport Global' option and verify\n \n that all routines have the correct checksums.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*343*'\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*343 does not \n \n If prompted "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install?" choose "NO". Note: Responding "Yes" to the prompt for\n rebuilding menu trees can significantly increase install time.\n \n If prompted "Want KIDS to INHIBIT LOGONs during the install?"\n choose "NO".\n \n If prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//" choose "NO" unless the site has additional local\nalter or modify any software design safeguards or safety critical \n laboratory options that should be disabled during install.\n \n 6. When prompted for the DEVICE, enter "Q" to queue the build. If you\n do not queue the installation KIDS will abort the install. When\n you try to restart the install you may encounter an <UNDEF> error\n due to a bug in KIDS. If this happens you will need to use FileMan\n to modify the INSTALL file (#9.7) for entry LR*5.2*343 which \n currently has the status of "Start of Install" and set its' STATUS \n field to "Install Completed". Reload the transport global and \n install the patch again. \n============================\nelements functions.\n \n 7. Check your system for errors which may have occurred during the \n time this patch was installed. If the PROTOCOL DGPM MOVEMENT \n EVENTS was called during this patch installation, system errors \n (such as "Can't return to source" for routine LR7OEVNT) may have \n been generated. If so, those patient movements will have to be re-\n created. \n \n \nINSTALLATION EXAMPLE\n \n====================\n \nSelect Installation Option: Install Package(s)\nSelect INSTALL NAME: LR*5.2*343 Loaded from Distribution \n10/20/05@12:39:58\n => LR343 KIDS ;Created on Oct 20, 2005@11:59:59\n \nThis Distribution was loaded on Oct 20, 2005@12:39:58 with header of \n LR343 KIDS ;Created on Oct 20, 2005@11:59:59\n It consisted of the following Install(s):\nPOTENTIAL IMPACT ON SITES: This patch contains changes to 0 routines and \n LR*5.2*343\nChecking Install for Package LR*5.2*343\nWill first run the Environment Check Routine, LR343\n \n Environment is okay \n \nInstall Questions for LR*5.2*343\n \nWant KIDS to INHIBIT LOGONs during the install? NO// \n \n1 file identified in Veterans Health Administration (VHA) Directive \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// QUEUE TO PRINT ON\nDEVICE: HOME// P-MAIN\n \nRequest Start Time: Oct 20, 2005@12:42:41// (OCT 20, 2005@12:42:41)\nInstall Queued!\n \n2004-058, group B listing. The changes have no effect on Blood Bank \n \n \nSample Installation Output\n==========================\n \nInstall Started for LR*5.2*343 : \n Oct 20, 2005@12:42:42\n \nBuild Distribution Date: Oct 20, 2005\n \nfunctionality or medical device control functions. There is no adverse \n Installing Routines:...\n Oct 20, 2005@12:42:42\n \n Running Pre-Install Routine: PRE^LR343.\n \n Pre install started at Oct 20, 2005@12:42:42\n \n Sent install started alert to mail group G.LMI\n \n Setting DISABLE and ACTION fields for Protocols\npotential to sites.\n \n No actions required for pre install\n \n Pre install completed at Oct 20, 2005@12:47:42\n \n Installing PACKAGE COMPONENTS: \n \n Installing PROTOCOL...\n Oct 20, 2005@12:47:42\n \n \n Running Post-Install Routine: POST^LR343.\n \n Post install started at Oct 20, 2005@12:47:42\n \n File #69.9 field data update started\n \n File #69.9 field data deletion finished\n \n Post install completed at Oct 20, 2005@12:47:42\n \nVALIDATION REQUIREMENTS BY OPTION: \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LR*5.2*343 Installed. \n Oct 20, 2005@12:47:42\n \n Install Message sent\nThere are no validation requirements for this patch.\n \n \n \nSample MailMan Message\n======================\nPre install started at Oct 20, 2005@12:48:15\nSent install started alert to mail group G.LMI\nSetting DISABLE and ACTION fields for Protocols\nNo actions required for pre install\nPre install completed at Oct 20, 2005@12:48:55\nVISTA Laboratory Package patch LR*5.2*343 contains changes to software \n \nPost install started at Oct 20, 2005@12:53:59\nFile #69.9 field data update started\nFile #69.9 field data deletion finished\nPost install completed at Oct 20, 2005@12:54:45\nSending install completion alert to mail group G.LMI\nMINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL FUNCTIONS:\nThere are no test case scenarios for this patch.\n************************************************************************\n \nRemove the LABORATORY package's rules for managing laboratory order \nauto-discontinuance on admission, transfer, or discharge events and let \nthe existing rules in the OERR (ORDER ENTRY RESULTS REPORTING) package \nhandle the order auto-discontinuance process.\n \ncontrolled by VHA DIRECTIVE 2004-058, titled VISTA BLOOD BANK SOFTWARE. \nThe LABORATORY package's process that is used to decide if an order \nshould be discontinued when a patient move event is triggered will be \ndisabled. This business rule is already being handled by the OERR \npackage and the Lab's business rules do not perform all of the needed \nchecks that the OERR package performs. For example, the Lab's process \ndoes not check that a new movement is actually tied to the current \nadmission. An edit of a patient movement can result in erroneous auto \ndiscontinue of a patient's laboratory orders. OERR also provides checks \nin the software to establish whether the patient event is new or an edit \nto an existing event.\nChanges include: \n \nThe Lab's process has caused erroneous auto discontinuance of laboratory \norders because it does not check if a new movement is actually tied to \nthe patient's current admission. In the case outlined by the Patient \nSafety Issue (PSI) report it appeared that a user deleted and re-entered \na movement for a prior admission to make a correction. Since it was a \nnew movement the Lab code executed and the orders were discontinued. \nThis problem would especially impact sites with patients that are \ntransferred from the acute hospital to the nursing home.\n \n File #69.9 (Laboratory Site)\n \n \nTechnical Description\n=====================\nWhen the DGPM MOVEMENT EVENTS of the PROTOCOL file (#101) is triggered \nthe LR7O MOVEMENT EVENT protocol may be called (if it is an item of the \nDGPM MOVEMENT EVENTS protocol). In this situation the business rule \nprocessing in the LABORATORY package fails to make all of the needed \nchecks to properly determine if the order should be discontinued. If \nLab's logic discontinues the order there will be no order for OERR to \n Field #150.3 (CANCEL ON ADMIT) - Removed\napply its more detailed set of business rules against when the OERR code \nis called from the patient movement event.\n \nLab will no longer perform any package-level checks for order \nauto-discontinuance based on patient movements. These checks will be \nperformed by the OERR package. This change is accomplished by:\n \nDeletion of PROTOCOL file (#101) entries:\n LR7O MOVEMENT EVENT and LR7O MOVEMENT EVENT TASK\nDeletion of routine LR7OEVNT\n Field #150.4 (CANCEL ON DISCHARGE) - Removed\nDeletion of the following Data Dictionary for LABORATORY SITE file \n(#69.9):\n CANCEL ON ADMIT field (#150.3)\n CANCEL ON DISCHARGE field (#150.4)\n CANCEL ON SPECIALTY TRANSFER field (#150.5)\n \n \n \nNew Service Request:\n====================\n Field #150.5 (CANCEL ON SPECIALTY TRANSFER) - Removed\n#20050802 -- Remove Lab Package Options to DC Order on Patient Movement\n \n \nAssociated Remedy:\n==================\nHD0000000104211\n \n \nAssociated E3R:\n===============\n\n
\nThis patch corrects 2 PROBLEMS WITH THE TURNAROUND TIME REPORT\n(LR CAPTT).\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*329 does\nBank software functionality, therefore RISK is none.\n ANN ARBOR, MI \n BAY PINES, FL \n BLACK HILLS HCS\n BOSTON HCS \n BRONX, NY \n CENTRAL PLAINS HCS \n CENTRAL TEXAS HCS \n CLEVELAND, OH\n DAYTON, OH \n DETROIT, MI \n \n DUBLIN, GA \n DURHAM, NC \n FARGO, ND \n FRESNO, CA \n HAMPTON, VA \n HINES, IL \n HOUSTON, TX \n LEXINGTON, KY\n LOMA LINDA, CA\n LONG BEACH, CA\n \n MADISON, WI \n MANCHESTER, NH\n MARYLAND HCS \n MILWAUKEE, WI \n MINNEAPOLIS, MN\n MUSKOGEE, OK \n NEW YORK HCS \n NORTH CHICAGO, IL\n NORTHPORT, NY \n OKLAHOMA CITY, OK\n1. Remedy ticket HD0000000088913 reported the Laboratory software was\n PHILADELPHIA, PA \n PROVIDENCE, RI \n RICHMOND, VA \n SAN FRANCISCO, CA\n SAN JUAN, PR \n SHERIDAN, WY \n SHREVEPORT, LA \n SIOUX FALLS, SD \n ST CLOUD, MN \n TAMPA, FL \ncreating Laboratory Unique Identifiers (UID) which used the prefix '00'\n TENNESSEE VALLEY HCS\n UPSTATE NEW YORK HCS\n WEST PALM BEACH, FL \n \n\n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\ninstead of the site's two character identifier assigned to each accession\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR329 N/A 5595661 **329** (Deleted by KIDS)\n LROC 9241387 7783203 **121,295,329**\n \n List of preceding patches: 295\n Sites should use CHECK^XTSUMBLD to verify checksums.\narea. This situation exists when the UIDs from old previously purged\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\naccessions are still in the "C" cross-reference of the ACCESSION file\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n(#68), many from when the UID was first implemented in 1995.\n select the 'Installation' menu.\n \n 3. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*329):\n a. Print Transport Global\n b. Backup a Transport Global\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n \n all routines have the correct checksums.\n \n 4. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*329'.\n\n When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//' choose 'NO'. Responding 'Yes' to the prompt for \n rebuilding menu trees can significantly increase install time.\n\n When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//\nnot contain any changes to the VISTA BLOOD BANK Software as defined\nOne of the checks performed during UID creation is to check if the UID\n choose 'NO'.\n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', choose 'NO'.\n \n During install KIDS will place the Purge old orders & accessions\n option [LROC] out of order.\n \n Note: Routine LR329 will be deleted after successful patch installation.\n \nbeing generated exists in the "C" cross-reference. If it does and it is not\n \nINSTALLATION EXAMPLE\n====================\n \nSelect Installation Option:\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*329 Loaded from Distribution 4/11/05@16:15:44\nfor the accession being created then the software replaces the accession\n => LR*5.2*329\n \nThis Distribution was loaded on Apr 11, 2005@16:15:44 with header of\n LR*5.2*329\n It consisted of the following Install(s):\n LR*5.2*329\nChecking Install for Package LR*5.2*329\nWill first run the Environment Check Routine, LR329\n \n \narea identifier the site has specified for the accession area and uses "00"\n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*329\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nin its place to insure creation of a unique identifier.\nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n \n Install Started for LR*5.2*329 :\n Apr 11, 2005@16:16:28\n \nBuild Distribution Date: Apr 11, 2005\n \n Installing Routines:...\n Apr 11, 2005@16:16:28\n \n Running Pre-Install Routine: PRE^LR329.\n \nExample: LRO(68,"C",1550180008,25,2950118,8)\n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION..\n Apr 11, 2005@16:16:28\nWhere: LRO = LRO global\n \n Running Post-Install Routine: POST^LR329.\n \n *** Post install started ***\n \n *** Tasking check/cleanup "C" cross reference on ACCESSION file (#68) ***\n \n *** Task #XXXX tasked to run ***\n \n *** Post install completed ***\n 68 = ACCESSION file (#68)\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file......\n \n Updating KIDS files.......\n \n LR*5.2*329 Installed.\n Apr 11, 2005@16:16:28\n \n "C" = cross reference\n Install Message sent #XXXX\n\n\n\n\n\nby VHA DIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n 155018008 = UID\n 25 = accession area\n 2950118 = accession date (Jan 18 1995)\n 8 = accession number portion\n\nIf the software wanted to assign the normally generated accession UID\n1550180008 to accession area 25, accession date of Jan 18 2005, accession\nnumber of 18 but found the UID already exist for 1995 accession for the\nsame day and number then UID generating software would replace 15 with 00\nto create a UID 0050180008 to allow accessioning to continue. \n \n\nNote: The UID generating software will always produce an unique number.\nNo two accessions will ever have the same UID based on the "C" cross reference.\n \nThe routine LROC is modified to check for purged accessions and remove\npurged accession's UID from the "C" and "D" cross reference of the\nACCESSION (#68) file. This will correct the problem of 10 year\noverlapping accession UID. This routine is invoked by Purge old orders\n& accessions option [LROC].\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*329 does\nNote: After installation of this patch the Laboratory software will\ncontinue to create UIDs using the "00" prefix when an existing accession\nis still currently on the system and using the UID. This is to assure that\nthe UID assigned to an accession is unique. The Laboratory software is\ncapable of handling UIDs correctly when the UID has a "00" prefix. There\nis no inherent requirement that a specific UID conform exactly to its\nrelated accession.\n \n2. The check and purge of these cross-references will be tasked by the\npost-install of this patch to cleanup any existing entries in file #68.\nnot alter or modify any software design safeguards or safety critical\nThe post-install of this patch tasks a back-ground job to cleanup any\nexisting entries in file #68 that have been previously purged. After\nthis back-ground job has run to completion, the "C" and "D" should not\ncontain any UIDs related to purged accessions.\n \n3. As part of developer review, the Purge old orders & accessions option\n[LROC] has been made 'TaskMan aware'. Stopping of this tasked process can\nbe accomplished using standard TaskMan utilities.\n \n \nelements functions.\n ASSOCIATED E3R\n --------------\n None\n \n ASSOCIATED REMEDY\n ---------------\n HD0000000088913\n Duplicates:\n HD0000000096348\n HD0000000141232\n \n HD0000000141237\n HD0000000141258\n HD0000000141298\n HD0000000141977\n HD0000000142004\n HD0000000142663\n HD0000000143065\n HD0000000144052\n HD0000000145774\n HD0000000146357\nRISK ANALYSIS: Changes made by patch LR*5.2*329 have no effect on Blood\n HD0000000147586\n HD0000000147794\n HD0000000148645\n \n\n TEST SITES\n ----------\n \n ALEXANDRIA, LA\n ALTOONA, PA \n\n
\nUnder the auspices of the Program Office for Infectious Diseases \n\n\n\nThe Laboratory EPI program is designed to automatically provide data \non emerging pathogens to Veterans Affairs Headquarters (VAHQ) \nwithout additional individual data entry at the site level. The data will \nbe sent to Austin Automation Center (AAC) for initial processing and \ncoupling with denominator data related to workload. VAHQ data \nretrieval and analysis can then be accomplished.\n\nVAHQ the Laboratory Emerging Pathogens Initiative (EPI) software \n\npackage is to allow the Department of Veterans Affairs (DVA) to track \nEmerging Pathogens on the national level without the necessity for \nadditional local data entry. Using this objective information, plans can \nbe formulated on the national level for intervention strategies and \nresource needs. Results of aggregate data can also be shared with \nappropriate public health authorities for planning on the national level \nfor the non-VA and private health care sectors.\n\n
\nThis patch addresses several issues with accessioning. This patch will\nprevent the re-accessioning of accessioned and the accessioned part of \npartly accessioned lab orders. It will not allow the input of order\nnumbers exceeding eight characters in length. It adds to chemistry and \nmicrobiology accessioning (both standard and batch) a warning message the \npatient the test is for has died and the patient's date of death.\n\n
\n Blood Bank Clearance\nfunctions.\n|Data Type|Reference low|Reference high|Therapeutic low|Therapeutic high\n \n| 18 | 19 | 20 | 21 | 22 | 23 |\n|Use Ref Lab|Site Comment|Test Synonyms|Test Type|Default LOINC|Extract Ver|\n \n \n3. Due to migration within Veterans Health Administration from Microsoft\nExchange 2000 to Exchange 2003 the Microsoft Exchange system dropped support\nfor 4 character Unix file permission which are part of the header used to\nuuencode the file attachment. The extract changes the uuencode file header\n \nfrom "begin 0664 "_filename to "begin 664 "_filename to enable successful\nprocessing of the uuencoded file by Exchange.\n \n \n ASSOCIATED E3R\n --------------\n None\n \n ASSOCIATED REMEDY\n ---------------\nRISK ANALYSIS: Changes made by patch LR*5.2*346 have no effect on Blood\n None\n \n \n TEST SITES\n ----------\n Biloxi VAMC\n Boston HCS VAMC\n El Paso VAMC\n Milwaukee VAMC\n San Antonio VAMC\nBank software functionality, therefore RISK is none.\n Upstate New York HCS\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR346 N/A 4832883 **346** (Deleted by KIDS)\n LRSRVR 5915085 5140630 **232,303,346**\n LRSRVR2 12542186 9040430 **303,346**\n LRSRVR2A N/A 6229869 **346**\n LRSRVR3 13571036 13681273 **303,346**\n LRSRVR6 N/A 8991310 **346**\n LRSRVR7 N/A 7316475 **346**\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\n List of preceding patches: 303\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \nmade, no specific validation requirements exist as a result of installation\n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\nof this patch.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 3. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*346):\n a. Print Transport Global\n b. Backup a Transport Global\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n----------------------------------------------------------------------------\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 4. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*346'.\n \n When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES//' choose 'NO'. Responding 'Yes' to the prompt for\n rebuilding menu trees can significantly increase install time.\n \n \n When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//\n choose 'NO'.\n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', choose 'NO'.\n \n During install KIDS will place the LR LAB SERVER option [LRLABSERVER]\n out of order.\n \n ====================\nAs part of the VA/DoD Laboratory Data Sharing Interoperability (LDSI) Phase\n Note: Routine LR346 will be deleted after successful patch installation.\n \n \nINSTALLATION EXAMPLE\n====================\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*346 Loaded from Distribution 9/16/05@15:38:31\n2 project supporting the exchange of microbiology and anatomic pathology\n => LR*5.2*346\n \nThis Distribution was loaded on Sep 16, 2005@15:38:31 with header of\n LR*5.2*346\n It consisted of the following Install(s):\n LR*5.2*346\nChecking Install for Package LR*5.2*346\nWill first run the Environment Check Routine, LR346\n \n \nlaboratory test orders and results, enhancements have been made to the\n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*346\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nLaboratory server LRLABSERVER to extract selected VistA Laboratory files\nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \nfor SNOMED CT mapping.\n \n Install Started for LR*5.2*346 :\n Sep 16, 2005@17:07:36\n \nBuild Distribution Date: Sep 16, 2005\n \n Installing Routines:\n Sep 16, 2005@17:07:36\n \n Running Pre-Install Routine: PRE^LR346\n \n \n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION\n1. The following are new LRLABSERVER server reports made available with\n Sep 16, 2005@17:07:36\n \n \n Running Post-Install Routine: POST^LR346\n \n *** Post install started ***\n \n *** No action required ***\n \n *** Post install completed ***\nthis patch:\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*346 Installed.\n Sep 16, 2005@17:07:36\n \n \n Install Message sent #nnnnnn\n \nInstall Completed\n\na. SNOMED\n \n Send a message to: S.LRLABSERVER@domain name\n Subject: SNOMED\n \n The body of the message will be ignored. The following files are\n scanned and data is extracted and extract data in a format for input\n into Standards and Terminology Service (STS) mapping SNOMED tool:\n \n File # File Name\n ------ ---------\n 61 TOPOGRAPHY FIELD\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*346 does not\n 61.1 MORPHOLOGY FIELD\n 61.2 ETIOLOGY FIELD\n 61.3 FUNCTION FIELD\n 61.4 DISEASE FIELD\n 61.5 PROCEDURE FIELD\n 61.6 OCCUPATION FIELD\n 62 COLLECTION SAMPLE\n \n Results are returned to the person\n sending the mail message request. The extracted data is returned as an\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n attached file in a delimited format using the "|" character as\n the field delimiter.\n \n Record legend for attached file:\n Station #-File #-IEN|Entry Name|SNOMED I|VUID|SNOMED CT|\n SNOMED CT TERM|Mapping Exception|Related Specimen|Related Specimen ID|\n Extract Ver|\n \n Note: the fields RELATED SPECIMEN & RELATED SPECIMEN ID in the\n record are only valued when the record relates to an entry\nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n in COLLECTION SAMPLE file (#62) and indicates the related\n specimen in TOPOGRAPHY FIELD file (#61).\n \n \nb. NLT/CPT\n Send a message to: S.LRLABSERVER@domain name\n Subject: NLT/CPT\n \n The body of the message will be ignored. The database is scanned\n for mapped NLT, LOINC and CPT data. Results are returned to the person\n \n sending the mail message request. The extracted data is returned as an\n attached file in a delimited format using the "|" character as the field\n delimiter.\n \n Record legend for attached file:\n Station #-NLT IEN-CPT IEN-Spec-Time Aspect|NLT Code|NLT Name|CPT Code|CPT\n Name|Specimen|Time Aspect|LOINC Code|LOINC Short Name|\n \n \n2. The existing LRLABSERVER report RELMA has been modified to extract\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*346 does not\nadditional information requested by VA Data Standardization service.\n a. The extract will now include an extract version number. This patch\n will set the version number to 1.1.\n b. Include site's Laboratory Test site notes.\n c. Include laboratory test's synonyms\n d. Include laboratory test's type\n e. Include laboratory test's default LOINC code.\n f. Include mappings to suffixed NLT codes when laboratory code is mapped\n to a generic NLT code and suffixed codes also exist.\n \nalter or modify any software design safeguards or safety critical elements\nThe modified record layout of the extract is:\n \n Legend:\n| 1 | 2 | 3 | 4 | 5 | 6\n|Station #-60 ien-Spec ien-Index|Test Name|Spec|Time Aspect|Units|LOINC\n \n| 7 | 8 | 9 | 10 | 11 | 12\n|NLT #|Battery Code|Battery Description|Lab Section|Subscript|Comment\n \n| 13 | 14 | 15 | 16 | 17\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*328 does not\nBank software functionality, therefore RISK is none.\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n \n 4. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*328):\n a. Print Transport Global\n b. Backup a Transport Global\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes\n 5. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*328'. When prompted 'Want KIDS to\n INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted\n 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES//', choose 'NO'.\n \n During install KIDS will place the "Accession order then immediately\n enter data option [LR ACC THEN DATA] out of order.\n \n 6. On a mapped system, rebuild your map set.\nmade, no specific validation requirements exist as a result of installation\n \n Note: Routine LR328 will be deleted after successful patch installation.\n \n \nINSTALLATION EXAMPLE\n==================== \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*328 Loaded from Distribution Loaded from\nDistribution 4/21/05@16:56:33\nof this patch.\n => LR*5.2*328\n \nThis Distribution was loaded on Apr 21, 2005@16:56:33 with header of\n LR*5.2*328\n It consisted of the following Install(s):\n LR*5.2*328\nChecking Install for Package LR*5.2*328\nWill first run the Environment Check Routine, LR328\n \n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*328\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n Install Started for LR*5.2*328 :\n Apr 21, 2005@16:58:02\n \nBuild Distribution Date: Apr 21, 2005\n \n Installing Routines:\n Apr 21, 2005@16:58:02\nNature of Problem:\n \n Running Pre-Install Routine: PRE^LR328\n \n *** Pre install started ***\n \n *** No action required ***\n \n *** Pre install completed ***\n \n Installing PACKAGE COMPONENTS:\n PSI-04-059 identified a patient safety issue identified during the\n \n Installing OPTION\n Apr 21, 2005@16:58:02\n \n Running Post-Install Routine: POST^LR328\n \n *** Post install started ***\n \n *** No action required ***\n \n testing phase of the Laboratory Electronic Data Interchange (LEDI III)\n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*328 Installed.\n Apr 21, 2005@16:58:03\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n software patches LA*5.2*64 and LR*5.2*286.\n \n Install Message sent #XXXX\n \nInstall Completed\n\n\n\n\n\n\n \n Two test sites reported an undefined error related to the variable SEX\n which contains the patient's sex. During analysis of the reported error,\n it was determined, by the laboratory development team, that the variable\n that referenced the patient's sex was being killed between accessions when\n a laboratory order created two or more accessions.\n \n The problem occurs when laboratory users enter laboratory test results\n using the VistA Laboratory option "Accession order then immediately enter\nDIRECTIVE 2004-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n data [LR ACC THEN DATA]". If the laboratory order being processed\n creates two or more accessions, the second and any subsequent accessions,\n may calculate age and/or sex based normals and abnormals incorrectly.\n \n We believe this to be a pre-existing problem; however, we cannot\n determine how long the problem has been occurring. It is unknown as to\n whether any specific incidents have occurred if any. Also, but most\n importantly, no patients were harmed.\n \nSolution:\n \n The LR*5.2*328 patch was developed which will set patient's demographics\n between processing of accessions when using the "Accession order then\n immediately enter data [LR ACC THEN DATA]" option. This will ensure that\n the patient's age/sex is defined before calculating any age/sex based\n normals and determining abnormality flags.\n \n The routine LRFAST is modified to define the applicable patient \n demographic values for sex, date of birth, and age when processing each\n accession associated with the order.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*328 does not\n \n ASSOCIATED E3R\n --------------\n None\n \n ASSOCIATED REMEDY\n ---------------\n None\n \n ASSOCIATED PSI\nalter or modify any software design safeguards or safety critical elements\n ---------------\n PSI-04-059 PATIENT SAFETY ISSUE: Laboratory, 11/3/2004 5:20:06 PM\n \n \n TEST SITES\n ----------\n Durham VAMC \n Manchester VAMC\n Milwaukee VAMC\n North Chicago VAMC\nfunctions.\n \n \nROUTINE SUMMARY\n===============\n The following routines are included in this patch. The second line\n of each of these routines now looks like:\n <tab> ;;5.2;LAB SERVICE;<patchlist>;Sep 27, 1994\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n \n ------------ ------------ ----------- ------------\n LR328 N/A 4831454 **328** (Deleted by KIDS)\n LRFAST 19472230 19464995 **100,121,201,286,291,328**\n \n List of preceding patches: 291\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\nRISK ANALYSIS: Changes made by patch LR*5.2*328 have no effect on Blood\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n\n
\nThis patch corrects 2 problems with "DELETE TEST" and a problem\nwith exiting the "INTERIM REPORT". An issue is also addressed with\n"ELECTRONIC CATALOG".\n\n
\nThis patch will correct a problem with the display of Reference, Critical\nHIGH (60.01), THERAPEUTIC LOW (60.01,9.2), and THERAPEUTIC HIGH (60.01, \n9.3) has been changed.\n& Therapeutic ranges in the Laboratory Test Description in the Lab Test \nInformation option of the Tools menu in CPRS GUI by routine LR7OR4. It \nwill correct a problem with the display of reference ranges with a \npatient's laboratory test data in both CPRS GUI and the Laboratory \nPackage by routines LR7OGMC, LR7OGU, and LRRP1.\n \nIn the SITE/SPECIMEN SUB-FILE (60.01) the description for fields REFERENCE\n LOW (60.01,1), REFERENCE HIGH (60.01,2), CRITICAL LOW (60.01,3), CRITICAL\n\n
\n=====================\n1. Currently: If a Current Procedural Terminolgy (CPT) code is not\n \nThe updates described above are displayed in the following screen format. \nThis screen format is used in the menu options listed below it:\n \nProvider: PROVIDER, ONE// PRO PHYSICIAN\n \nSelect CPT codes: 88302\n \nTEST, PATIENT1 000-99-1234 DOB: Mar 05, 1955\n Collection Date: Jan 06, 2005@11:52\nfound or is marked inactive in the CPT file (#81), a general message,\n Acc #: NSP 05 1 Loc: 5N\n Specimen: \n Tissue Specimens: \n TAIL\n Test(s); SURGICAL PATH REPORTING/ SURGICAL PATHOLOGY LOG-IN/ \n Pathologist: PHYSICIAN, ONE\n \n Selected CPT Codes \n \n (1) 88302 LEVEL II - SURGICAL PATHOLOGY, GROSS AND MICROSCOP\n"Nothing Selected" displays, or no message at all displays. The CPT \n Surgical Pathology Level II {88518.0000}\n \nMenu Options:\n Lab CPT Billing [LRCAPES]\n Verify/release reports, anat path [LRAPR], \n CPT Coding selection\n Provisional anatomic diagnoses [LRAPAUPAD]\n Autopsy protocol [LRAPAUDAP]\n Autopsy protocol & SNOMED coding [LRAPAUDAB]\n Autopsy protocol & ICD9CM coding [LRAPAUDAA]\ncode is not selected and passed to PATIENT CARE ENCOUNTER (PCE).\n FS/Gross/Micro/Dx [LRAPDGM]\n FS/Gross/Micro/Dx/SNOMED Coding [LRAPDGS]\n FS/Gross/Micro/Dx/ICD9CM Coding [LRAPDGI]\n \n9. A couple of general corrections are included in this patch. For\ncertain $D statements which read, "'$DATA()#2", the modulo is incorrectly \napplied to the result of the "'$DATA()". Instead, the NOT operator "'" \nshould be applied to the evaluation of "$DATA()#2" to correctly read,\n"'($DATA()#2)". The following statements have been corrected:\n \n \na. In SETWKL+13^LRCAPES1, Q:'$D(^LAM(LRP,0))#2, has been changed to\n Q:'($D(^LAM(LRP,0))#2).\nb. In EN5+4^LRCAPPH1, Q:'$D(^LRO(69,LRCDT,1,LRSN,2,LRTST,0))#2, has been\n changed to Q:'($D(^LRO(69,LRCDT,1,LRSN,2,LRTST,0))#2).\n \nData Dictionary Changes\n=======================\nVistA Laboratory AP CPT Code Corrections Patch LR*5.2*308 software release\ncontains the following data dictionary changes:\n \nUpdate: If one or more CPT's are not found in the CPT file (#81), \nWKLD CODE file (#64)\n------------------------\nWKLD CODE file (#64), ES DISPLAY ORDER field (#26) has been modified \nto increase the quantity allowed from 100 to 1000.\n \n======================\nAssociated E3Rs - None\n---------------\n \nAssociated NOISs -\nthe following message displays and lists the CPT codes:\n---------------- \n \n \nCPH-0103-41645 / HD0000000069980\nFGH-0103-31657 / HD0000000069982\nMIN-0103-41656 / HD0000000069981\nBHS-0103-12034 / HD0000000069988\nUNY-0103-11749 / HD0000000069985\nWBP-0103-21809 / HD0000000069986\nSAM-0603-21566 / HD0000000070159\n "The following CPT Code(s) are not selected:\nJAC-1103-70158 / HD0000000070386\nALT-0304-20022 / HD0000000070580\nSBY-0304-31852 / HD0000000070614\nBIL-0304-31578 / HD0000000070606\nWRJ-0404-10360 / HD0000000070654\nHVH-0404-11404 / HD0000000070684\nCPH-0804-41938 / HD0000000070965\nMIN-1204-40394 / HD0000000071122\nHEH-0304-41954 / HD0000000070618\n \n Not found in #81: #####,#####,".\n=====================\nTest Sites:\n===========\n \nBoston HCS - VMS/CACHE (large integrated site)\nDurham VAMC - VMS/CACHE (large site)\nIowa City VAMC - VMS/CACHE (large integrated site)\nLong Beach VAMC - VMS/CACHE (large site)\n \n================\nFor one or more CPTs that are marked inactive in the CPT \nRoutine Summary:\n================\n \nThe following list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n \n<tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27 1994\n \n CHECK^XTSUMBLD results\n \nPatch Description\nfile (#81), the following message displays and lists the CPT codes:\nRoutine Before After Patch\nName Patch Patch List\n \nLR308 N/A 3577348 **308** (Deleted by KIDS)\nLRAPLG1 5113296 5107203 **72,121,248,308**\nLRAPUTL 9752029 9713709 **259,308**\nLRCAPES 13104305 13495108 **274,259,349,308**\nLRCAPES1 8132160 13575476 **274,308**\nLRCAPPH1 13504461 14078305 **127,136,138,158,263,264,274,291,359,308**\n \n "The following CPT Code(s) are not selected: \n \nSoftware Retrieval\n------------------\nVistA Laboratory Anatomic Pathology Current Procedural Terminology \nCorrections Patch LR*5.2*308 software is distributed by Packman.\n \nDocumentation Retrieval\n-----------------------\nVistA Laboratory Anatomic Pathology (AP) Current Procedural \nTerminology(CPT)Corrections Patch LR*5.2*308 software User Guide\n CPT(s) inactive in #81: #####,#####".\nis available at the following Office of Information Field Offices (OIFOs) \nANONYMOUS.SOFTWARE directories: \n \nOI Field Office FTP Address Directory\n--------------- ----------- ---------\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \nAll CPTs that are inactive or not found in file #81 will not be \nDocumentation Retrieval Formats\n-------------------------------\nVistA Laboratory Anatomic Pathology (AP) Current Procedural \nTerminology(CPT)Corrections Patch LR*5.2*308 User Guide files are \nexported in the following retrieval formats:\n \nFile Name Contents Retrieval Formats\n--------- -------- -----------------\nLAB_52_308_UG.doc VistA Laboratory Anatomic Pathology\n (AP) Current Procedural Terminology\npassed to PCE.\n (CPT)Corrections Patch LR*5.2*308\n User Guide BINARY\n \nLAB_52_308_UG.pdf VistA Laboratory Anatomic Pathology\n (AP) Current Procedural Terminology\n (CPT)Corrections Patch LR*5.2*308\n User Guide BINARY\n \n \nVistA Website Locations:\n \n-----------------------\nVistA Laboratory Anatomic Pathology (AP) Current Procedural \nTerminology(CPT)Corrections Patch LR*5.2*308 User Guide is accessible in \nMS Word (.doc) and Portable Document Format (.pdf) at the following \nVistA locations:\n \nLaboratory Version 5.2 Home Page\n--------------------------------\nhttp://vista.domain.ext/ClinicalSpecialties/lab/\n \n2. Currently: CPTs marked inactive in the WKLD CODE file (#64) \nVistA Documentation Library (VDL)\n---------------------------------\nwww.domain.ext/vdl/\ncan be selected and are passed to PCE.\n \nUpdate: If a selected CPT is marked inactive in file (#64), a \n================= \nsearch is made for another active CPT linked to the same workload code. \nIf another active CPT is found, the active CPT replaces the inactive CPT\nand is passed to PCE. The following message will display if an active\nreplacement is found:\n "The following CPT Code(s) are not selected: \n Inactive in #64\\Active Replacement Found: ##### \\ #####; ##### \\\n#####".\n \nIf no active replacement found, the selected CPT is not passed to \nPCE and is displayed in the following message:\nSeveral updates and enhancements have been identified as requiring \n "The following CPT Code(s) are not selected: \n CPT(s) inactive in #64: #####,#####". \n \n3. Currently: Inactive CPTs found in the WKLD CODE file (#64) \ncan be entered and passed to PCE for non-AP accessions. When an inactive\nCPT is selected and passed to PCE, the entire order is marked invalid for\nworkload and no workload is passed, and a mail message is generated at the\nsite which states "No lab OOS location defined".\n \nUpdate: If a CPT is found inactive in file #64, a search will be \nimmediate action after the installation of patch LR*5.2*274, AP CPT \nmade for another active replacement CPT linked to the same workload code.\nIf another active CPT is found, the active CPT replaces the inactive\nCPT. If no active replacement CPT is found, the original CPT is not\npassed to PCE, and thus no misleading mail message is generated.\n \n4. Currently: Any subsequent CPT codes entered on an accession \nwill replace or overlay the quantity previously passed to PCE.\nExample: CPT 88302 with quantity of 2 entered on day 1; PCE shows\nquantity of 2. On day 2, CPT 88302 with quantity of 1 entered; PCE shows\nupdated quantity of 1. It should show 3.\nCoding & NLT Code Update. This patch LR*5.2*308 includes updates\n \nUpdate: All subsequent CPT code quantities entered for an \naccession will be added to existing quantities stored in PCE.\n \n5. Currently: If a selected CPT is not linked to a workload code \nin the WKLD CODE file (#64), the CPT is passed to PCE, and the message\n"Storing in LMIP". This message incorrectly identifies the CPT as \nhaving been stored in the WKLD CODE file (#64).\n \nUpdate: Selected CPT codes that are not linked to a workload code \nthat have been identified in the NOIS's listed below. \nin the WKLD CODE file (#64) will not be passed to PCE, and the following\nmessage will display:\n "The following CPT Code(s) are not selected: \n Not linked to workload in #64: #####, #####".\n \n6. Currently: If a selected CPT code is linked to multiple workload \ncodes, the workload code with the lowest IEN is selected. This cannot be \nchanged; however, the problem has been reduced by increasing the number of \nallowed ES Display Order numbers that can be assigned to a specific \nCPT-workload code combination. The limit has been increased from 100 to \nThe following updates are included. \n1000. \n \n7. Currently: When more than one accession is entered for a patient on \nthe same date, at the same location, and the specimen collection date/time \ndoes not contain a unique time, then each accession for this patient will \nhave the same encounter/visit number assigned when CPT codes are entered \nand passed to PCE. \n \nUpdate: Within Anatomic Pathology (AP) Login, the "Date/time Specimen\ntaken:" prompt default has been changed from TODAY (date only) to NOW\n \n(date and time). This helps decrease the chance of having the same\nencounter number assigned to more than one accession entered on the same\npatient on the same date, at the same location.\n \n8. A couple of minor cosmetic updates are included in this patch:\na. The prompt "Releasing Pathologist:" has been changed to "Provider:" \nsince the name entered at this prompt must be an active provider. \nb. The pathologist or cytotechnologist name, if entered on the accession,\nis included in the header information that displays at the time CPT coding \nis entered.\n\n\nThis patch addresses a number of minor issues in the Lab Package.\n\n
\nDescription:\n*************************************************************************\nthe AUTOPSY SUPPLEMENTARY REPORT for Autopsy. The field is a flag, when \nset to '1', indicates a released supplementary report is being modified, \nand has not yet been released.\n \n63.207,.03 RELEASE SUPP REPORT MODIFIED 0;3 SET\n \n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: SEP 08, 2004 \n DESCRIPTION: This flag will be set to '1' when a\n ************************************\n released supplementary report is modified. It is\n removed when the modified supplementary report is\n released. \n \n63.817,.03 RELEASE SUPP REPORT MODIFIED 0;3 SET\n \n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: SEP 08, 2004 \n DESCRIPTION: This flag will be set to '1' when a \n \n released supplementary report is modified. It is \n removed when the modified supplementary report is\n released. \n \n63.907,.03 RELEASE SUPP REPORT MODIFIED 0;3 SET\n \n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: SEP 08, 2004 \n DESCRIPTION: This flag will be set to '1' when a \nBLOOD BANK CLEARANCE\n released supplementary report is modified. It is\n removed when the modified supplementary report is\n released. \n \n63.324,.03 RELEASE SUPP REPORT MODIFIED 0;3 SET\n \n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: SEP 08, 2004 \n DESCRIPTION: This flag will be set to '1' when a \n====================\n released supplementary report is modified. It is \n removed when the modified supplementary report is\n released. \n \nModifications:\n--------------\nThe following options have been modified. Please refer to the User \nGuide distributed with this patch for detailed information and examples.\n \nSupplementary Report, Anat Path [LRAPDSR] option\n \nSupplementary report release, anat path [LRAPRS] option\nAutopsy supplementary report [LRAPAUSR] option\nModify released pathology report [LRAPMRL] option \nPrint all reports on queue [LRAP PRINT ALL ON QUEUE] option\nPrint single report only [LRAP PRINT SINGLE] option\nPrint final path reports by accession # [LRAPFICH] option\n \n \nThis patch addresses the following E3R's:\n========================================\nVISTA Laboratory Package patch LR*5.2*317 contains changes to \nN/A\n \n \nThis patch addresses the following NOIS / Remedy Ticket:\n=======================================================\nBRX-0704-11083 / HD0000000070862\nCPH-0904-40215 / HD0000000070983\nMIA-0604-31201 / HD0000000070788\nPRO-0604-10213 / HD0000000070762\nSLC-0604-50484 / HD0000000070766\nsoftware controlled by VHA DIRECTIVE 2004-053, titled VISTA BLOOD \nSLC-0604-50594 / HD0000000070769\nSLC-0604-51082 / H00000000070778\n \n \nOverview of NOIS / Remedy Tickets:\n=================================\n \nBRX-0704-11083 / HD0000000070862\nProblem: Pathologists are complaining about changes in procedure done\nby the Electronic Signature patch. When a supplemental report is added \nBANK SOFTWARE. Changes include: \nthe system un-verifies the parent report. This unverified report becomes \navailable for other Pathologists and transcriptionists to edit it. Before \nonce a report was verified it could not be changed. The Chief Pathologist \nis very concerned with the legal and clinical ramifications of this change.\n \nResolution: The resolution of this issue is contained in the section \nabove that describes the resolution to patient safety issues #1 and #2.\n \nCPH-0904-40215 / HD0000000070983 - \nProblem: Our pathologists are concerned that post patch 259, addition of \nFile Sub-file Field Field Name Action\nsupplemental reports (additional information) must be added under MM Modify \noption, thus un-releasing the original report, and necessitating the \nre-release of both original and supplemental reports. They feel modified \nreports should be reserved for edition/correction of previous released \nreports. They feel this is a patient safety issue. \nThe post 259 options [LRAPDSR] and [LRAPDSS] are redundant when they are \noperable only with un-released reports. \n \nResolution: The resolution of this issue is contained in the section \nabove that describes the resolution to patient safety issues #1 and #2.\n===========\n---- -------- ----- ---------- ------\n \nMIA-0604-31201 / HD0000000070788 - \nProblem: According to our lab folks in Anatomic path they used to go in to \nan option called Supplementary Report, Anat Path to make a correction to \nthe original after it is released. They don't want to go under the edit \nmodify to reopen the report any ideas on how they can go into the \nsupplementary to attach to the original accession report or something like \nthat. \n \nResolution: The resolution of this issue is contained in the section \n63 63.207 .03 RELEASE SUPP REPORT MODIFIED New Field\nabove that describes the resolution to patient safety issues #1 and #2.\n \nPRO-0604-10213 / HD0000000070762 - \nProblem: Our LAB Service Chief does not want IRM to install patch \nLR*5.2*259 for the following Patient Safety, integrity, and additional \nkeystrokes reasons. For example the Surgical Pathology Reports, the new \npatch, takes the Supplemental report feature away (ie. For a special \nstain), it's replaced with a modified report feature, which allows you to \nmake changes to the original report in addition to adding. Also, while \nusing the modify report feature, while your in it, it makes the original \n63 63.324 .03 RELEASE SUPP REPORT MODIFIED New Field\nreport unavailable for the Providers to view. He feels that this is a \nMajor Patient Safety issue, that if a Doctor is with the patient, he won't \nbe able to view the report. \n \nResolution: The resolution of this issue is contained in the section \nabove that describes the resolution to patient safety issues #1 and #2.\n \nSLC-0604-50484 / HD0000000070766 - \nProblem: I've just reviewed the NOIS MEM-0504-71296, and we are struggling \nwith the same issues of supplementary reports that they are. (Post install \n63 63.817 .03 RELEASE SUPP REPORT MODIFIED New Field\nof patch LR*5.2*259). We currently do not have the electronic signature \nturned on. The concern is, that once a report is unreleased, the \npreviously released portion of the report is not viewable on CPRS, and the \nway we operate here is that the secretaries transcribe the report, and the \npathologist signs them sometime later. We have only had the patch \ninstalled for a couple of days, and the path lab has already received calls \nthat reports have "disappeared" on CPRS ... are there any suggestions for a \nprocess change that could help with this? \n \nResolution: The resolution of this issue is contained in the section \n63 63.907 .03 RELEASE SUPP REPORT MODIFIED New Field\nabove that describes the resolution to patient safety issues #1 and #2.\n \nSLC-0604-50594 / HD0000000070769 - \nProblem: Post installation of LA*5.2*259 we have encountered the usual \nproblems with any software install that changes the daily routine of \nworkflow, but there is a problem that we feel does affect patient care . \nWe now have to "unrelease" a report prior to adding a supplementary report, \nthe secretaries then transcribe the supplemental report, then the \npathologists must review/correct and sign it prior to the secretaries \nre-releasing the report. This leaves a window of several hours during \n \nwhich the original report is not viewable on the computer, we have already \nreceived calls about "disappearing" path reports. Our pathologists feel \nthat a supplemental report should truly be regarded as an addendum to the \noriginal report, and should not make the original report unviewable while \nthe supplemental report is being processed. \n \nResolution: The resolution of this issue is contained in the section \nabove that describes the resolution to patient safety issues #1 and #2.\n \nSLC-0604-51082 / H00000000070778 -\nAll of the above changes have been reviewed by the VISTA Blood Bank \nProblem: We have found a problem with the electronic signature patch. Our \ntranscriptionist mistakenly selected the field to add a date to the \nsupplementary report field (thru edit/modify), but didn't add text to the \nfree text field. He was unable to sign a supplementary report (the \ncomputer says it doesn't exist), but when he tries to release the original \nreport, it says that the supplementary needs to be released first. The lab \nfigured out a way to release this, but it is an issue. \n \nResolution: The resolution of this issue is contained in the section \nabove that describes the resolution to patient safety issues #1 and #2.\nDeveloper and found to have no impact on the VISTA BLOOD BANK \n \n \nTEST SITES\n==========\nAnn Arbor VAMC - CACHE/VMS, large site\nBoston HCS - CACHE/VMS, large integrated site\nLong Beach VAMC - CACHE/VMS, large site\nProvidence VAMC - CACHE/VMS, medium site\nSalem VAMC - CACHE/VMS, medium site\n \nSOFTWARE control functions.\nROUTINE SUMMARY:\n================\nThe following is a list of the routines included in this patch. \nThe second line of each of these routines look like:\n \n <tab> ;;5.2;LAB SERVICE;**<patch list>;Sep 27, 1994\n \nUsing old logic:\n \n CHECK^XTSUMBLD results\n \n Routine Before After \n Name Patch Patch Patch List\n ----------- -------- --------- ----------------------------\n LR317 N/A 6221288 **317** (DELETED BY KIDS)\n LR7OSAP 16576063 17166196 **121,187,230,256,259,317**\n LR7OSAP1 8012437 8222916 **121,227,230,259,317**\n LR7OSAP2 17315095 18146154 **230,256,259,317**\n LRAPAUSR 7980343 8097532 **1,173,248,259,317**\n LRAPBR1 8346961 8691424 **259,317**\n LRAPBR4 5636439 5950657 **259,317**\n \nRISK ANALYSIS: Changes made by patch LR*5.2*317 have no effect on \n LRAPD1 5673315 5050395 **41,91,248,259,317**\n LRAPDA 11977101 13331988 **72,73,91,121,248,259,295,317**\n LRAPDSR 4820936 5708731 **248,259,295,317**\n LRAPMRL 8314291 8358357 **259,295,317**\n LRAPMRL1 4140484 5097223 **259,317**\n LRAPR 12791716 12536700 **72,248,259,317**\n LRAPR1 N/A 5253992 **317**\n LRAPRES 10849835 10161024 **259,295,317**\n LRAPV 3996189 4248185 **72,201,259,317**\n LRSPRPT 12082607 12449414 **1,72,248,259,317**\nBlood Bank software functionality, therefore RISK is none.\n \n \nUsing new logic:\n CHECK1^XTSUMBLD results\n Routine Before After \n Name Patch Patch Patch List\n ----------- -------- --------- ----------------------------\n LR317 N/A 18182916 **317** (DELETED BY KIDS)\n LR7OSAP 34114559 37919526 **121,187,230,256,259,317**\n LR7OSAP1 24974232 26109314 **121,227,230,259,317**\n \n LR7OSAP2 52834321 59162352 **230,256,259,317**\n LRAPAUSR 34065623 34793694 **1,173,248,259,317**\n LRAPBR1 54673575 58834636 **259,317**\n LRAPBR4 30127062 32957954 **259,317**\n LRAPD1 24077474 22198195 **41,91,248,259,317**\n LRAPDA 64317056 76606340 **72,73,91,121,248,259,295,317**\n LRAPDSR 17788838 25438900 **248,259,295,317**\n LRAPMRL 66524711 21952067 **259,295,317**\n LRAPMRL1 15484610 21952067 **259,317**\n LRAPR 89817361 84430863 **72,248,259,317**\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*317 does \n LRAPR1 N/A 19317428 **317**\n LRAPRES 103360947 94733481 **259,295,317**\n LRAPV 13932043 15077938 **72,201,259,317**\n LRSPRPT 88845330 92562557 **1,72,248,259,317**\n \n NOTE: LR317 will be deleted after successful patch installation.\n \n \nSOFTWARE RETRIEVAL:\n===================\nnot alter or modify any software design safeguards or safety \n \nSoftware Retrieval\n------------------\nVistA Laboratory Anatomic Pathology Modifications/Enhancements \nto Address PSI-04-025 Patch LR*5.2*317 software is distributed by \nPackman.\n \nDocumentation Retrieval\n-----------------------\nVistA Laboratory Anatomic Pathology (AP) Modifications/Enhancements \ncritical elements functions.\nto Address PSI-04-025 Patch LR*5.2*317 User Guide is available at the \nfollowing Office of Information Field Offices (OIFOs) ANONYMOUS.SOFTWARE \ndirectories:\n \nOI Field Office FTP Address Directory\n--------------- ----------- ---------\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \n \nDocumentation Retrieval Formats\n-------------------------------\nVistA Laboratory Anatomic Pathology Supplementary Report Enhancements \nPatch LR*5.2*317 User Guide files are exported in the following retrieval \nformats:\n \nFile Name Contents Retrieval Formats\n--------- -------- -----------------\nLAB_52_317_UG.doc VistA Laboratory Anatomic Pathology\nPOTENTIAL IMPACT ON SITES: This patch contains changes to 0 \n (AP) Modifications/Enhancements \n to Address PSI-04-025 Patch \n LR*5.2*317 User Guide BINARY\n \n LAB_52_317_UG.pdf VistA Laboratory Anatomic Pathology\n (AP) Modifications/Enhancements\n to Address PSI-04-025 Patch\n LR*5.2*317 User Guide BINARY\n \nVistA Website Locations:\nroutines and 1 file identified in Veterans Health Administration \n-----------------------\nVistA Laboratory Anatomic Pathology (AP) Modifications/Enhancements \nto Address PSI-04-025 Patch LR*5.2*317 User Guide is accessible in \nMS Word (.doc) and Portable Document Format (.pdf) at the following \nVistA locations:\n \nLaboratory Version 5.2 Home Page\n--------------------------------\nhttp://vista.domain.ext/ClinicalSpecialties/lab/\n \n(VHA) Directive 2004-053, group B listing. The changes have no \nVistA Documentation Library (VDL)\n---------------------------------\nwww.domain.ext/vdl/\n \n \nINSTALLATION INSTRUCTIONS\n=========================\nThis patch can be installed with users on the system. However, it is \nrecommended that installation occur when there is no Anatomic Pathology\nactivity or activity is at a minimum. This will prevent 'Cannot return to \n ************************************\neffect on Blood Bank functionality or medical device control \nsource routine' errors. The Anatomic Pathology menu will be disabled \nautomatically by this patch and re-enabled after installation.\n \nInstall Time - less than 5 minutes.\n \nPRE-INSTALLATION INSTRUCTIONS\n=============================\n \n***************************************************************************\n*** IT IS VERY IMPORTANT THAT YOU FOLLOW THE PRE-INSTALLATION ***\nfunctions. There is no adverse potential to sites.\n*** INSTRUCTIONS BEFORE INSTALLING THE PATCH. ***\n*** ***\n*** All outstanding (unreleased) supplementary reports from July 23, *** \n*** 2003, the date LR*5.2*259 Anatomic Pathology Electronic Signature ***\n*** patch was first installed in a production account, until the present***\n*** MUST be released before installing this patch. If there are ***\n*** unverified supplementary reports, THE PATCH WILL NOT INSTALL. *** \n*** ***\n*** The appropriate Laboratory personnel should check for unverified ***\n*** supplementary reports and make sure all are reviewed and released ***\n \n*** before proceeding with this installation. The following option ***\n*** can be used to check for outstanding unreleased supplementary ***\n*** reports: List of unverified pathology reports [LRAPV] option. ***\n*** Selection #2 will create a listing of unverified supplementary ***\n*** reports. ***\n**************************************************************************\n**************************************************************************\n \n1. LOAD TRANSPORT GLOBAL\n ---------------------------------------\nVALIDATION REQUIREMENTS BY OPTION: \n Choose the PackMan message containing this patch and invoke the \n INSTALL/CHECK MESSAGE PackMan option.\n \n2. START UP KIDS\n Start up the Kernel Installation and distribution System \n Menu [XPD MAIN]:\n Edits and Distribution ...\n Utilities ...\n Installation ... \n Select Kernel Installation & Distribution System Option: INStallation\nThere are no validation requirements associated with this patch.\n ----\n 1 Load a Distribution\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n DD DD, 2nd Line Comparison\n \n \n Select Installation Option: \n \n \n3. Select Installation Option:\n -------------------------------\n NOTE: The following are OPTIONAL - (When prompted for the \n INSTALL NAME, enter LR*5.2*317):\n a. Backup a Transport Global - This option will create a \n backup message of any routines exported with this patch. \nMINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL FUNCTIONS:\n It will not backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option \n will allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch \n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will \n allow you to ensure the integrity of the routines that are in \n the transport global.\n \n4. Select Installation Option: Install Package(s) \nThere are no test case scenarios associated with this patch.\n ------------------\n **This is the step to start the installation of this KIDS patch: \n \n a. Choose the Install Package(s) option to start the patch install.\n (When prompted for the INSTALL NAME, enter LR*5.2*317.)\n b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n YES//' answer NO (unless otherwise indicated)\n c. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//' answer NO (unless otherwise indicated)\n \n \n5. If you have any unreleased supplementary reports from July 23, 2003\n until the present, the install will abort. To print the unreleased\n supplementary reports, you can print the install file.\n Here's an example:\n \nSelect Kernel Installation & Distribution System Option: utilities\n \nSelect Utilities Option: install File Print\nSelect INSTALL NAME: lr*5.2*317 Loaded from Distribution 8/25/06@14:37:36 \n \n=================\nDEVICE: HOME// ;;1000 UCX/TELNET\n \n \nPACKAGE: LR*5.2*317 Aug 25, 2006 2:39 pm PAGE 1\n COMPLETED ELAPSED\n---------------------------------------------------------------------------\nINSTALLED BY: IRM,PERSON\nNATIONAL PACKAGE: LAB SERVICE\n \nINSTALL STARTED: \n*************************************************************************\n \n \nROUTINES: \n \nPRE-INIT CHECK POINTS:\nXPD PREINSTALL STARTED \nXPD PREINSTALL COMPLETED \n \nFILES:\nLAB DATA \n \nVistA Laboratory Anatomic Pathology (AP) Modifications/Enhancements patch \nPOST-INIT CHECK POINTS:\nXPD POSTINSTALL STARTED \nXPD POSTINSTALL COMPLETED \n \nMESSAGES:\n \n Sending transport global loaded alert to mail group G.LMI \n \n \nUnreleased supplemental report(s) from July 23,2003 until present- must \nLR*5.2*317 addresses two patient safety issues (PSI) reported in PSI-04-025 \nbe released before install.\n \n \n Name: TEST,PATIENT Accession: NSP 04 2 \n \n \n --- Install Environment Check FAILED \n--- \n \nLR*5.2*317 Build will not be installed\nthat arose from the release and implementation of the VistA Laboratory \n Aug 25, 2006@14:38:55\n \n \nSelect Utilities Option: \n \n \n**NOTE: Routine LR317 will be deleted after successful patch installation.\nAnatomic Pathology Electronic Signature Patch LR*5.2*259.\n \nThe patient safety issues are described as follows:\n \n1. Users that should not be allowed to modify an Anatomic Pathology SF515 or \nAutopsy Protocol released report are given access to the Modify released report \nSPECIAL NOTE: \n[LRAPMRL] option in order to allow the user to add supplementary reports.\n \n2. The original Anatomic Pathology SF515 or Autopsy Protocol report is not \nviewable in the Computer Patient Records System (CPRS) during the time a \nsupplementary report is underway. Personnel are unable to view the report \nduring this time.\n \nThe VistA Laboratory Anatomic Pathology Electronic Signature Patch \nLR*5.2*259 changed the location and the method by which supplementary \nreports are added. The Modify released report [LRAPMRL] option is used to add \nInstallation of this patch MUST be coordinated with Laboratory personnel. \nsupplementary reports to the original report. Laboratory personnel allowed to \nadd supplementary reports to Anatomic Pathology released reports must have \naccess to the Modify released report [LRAPMRL] option. This access opened up \nthe potential for errors in which the report could be accidentally modified \nwhen a supplementary report was added.\n \nPatch LR*5.2*317 resolves this problem by removing the supplementary report \naddition functionality from the Modify released reports [LRAPMRL] option and \nplacing the functionality back to the Supplementary Report, Anat Path \n[LRAPDSR] option for Cytology, Electron Microscopy, and Surgical Pathology \nThe Pre-Installation instructions within the Installation Section below, \nreleased reports and the Autopsy supplementary report [LRAPAUSR] option for \nAutopsy released reports.\n \nAnother concern had to do with the addition of a supplementary report to a \nreleased Anatomic Pathology report, which unreleased the original report and \nmade it unavailable for viewing in Computerized Patient Record System (CPRS).\nThe time span in which the original report remained unavailable for viewing by \nthe Providers could be crucial. It was considered a major patient safety issue \nif a doctor, who was with a patient, was not able to view the report at that \ntime.\nMUST be followed and completed before installation can begin.\n \nPatch LR*5.2*317 resolves this problem by leaving the original report in \nreleased status during the time a supplementary report is being added. The \noriginal report remains available for viewing in CPRS during this time.\n \nEnhancements to LAB DATA file (#63):\n-------------\nA new field, RELEASE SUPP REPORT MODIFIED (#.03), has been added to the \nSUPPLEMENTARY REPORT SUB-FILE for the anatomic pathology sections \nCytopathology, Electron Microscopy, and Surgical Pathology; and to \n\n
\nThis patch addresses several issues in the Lab Service\npackage.\n\n
\nBlood Bank Clearance\n \n HD0000000112457\n HD0000000122951\n HD0000000131510\n HD0000000138475\n HD0000000138900\n HD0000000142655\n HD0000000154545\n HD0000000155087\n HD0000000160742\n HD0000000170863\n The IN COMMON ACCESSION field (#15.1) is added to the ACCESSION\n HD0000000179768\n HD0000000180175\n \n \nPARTICIPATING TEST SITES:\n=========================\nASHEVILLE, NC \nCENTRAL TEXAS HCS \nCLEVELAND, OH \nMARYLAND HCS\n NUMBER sub-file (#68.02) of the ACCESSION file (#68).\nMILWAUKEE, WI \nNORTH CHICAGO, IL \nSALISBURY, NC \nVA GREATER LOS ANGELES HCS\n \n \nREMEDY OVERVIEW:\n================\n \n1.1. HD0000000071160:\n \n---------------------\nA user reported encountering "FileMan DBS call failed during accessioning\nin routine LRWLST1" MailMan bulletins during accessioning. The generation\nof this bulletin occurs when Laboratory was making a duplicate FileMan DBS\ncall during accessioning that involved an accession area being 'in common'\nwith another accession area. This duplicate call would occur when the\naccession area has a lower internal entry number in ACCESSION file (#68)\nthan the accession area it is 'in common' with.\n \n \n STANDARD DATA DICTIONARY #68.02 -- ACCESSION NUMBER SUB-FILE\n1.2. HD0000000071160:\n----------------------\nDuring internal software review, the following issues were identified:\n \n a. It was determined that the "AD" CROSS-REFERENCE on ACCESSION field\n (#15) in ACCESSION NUMBER sub-file (#68.02) of ACCESSION file (#68)\n was not setting the reference to the 'in common' accession correctly\n on the accession. The patch will remove this cross-reference from\n the data dictionary. See 2b. for storing 'in common' accession\n reference.\n STORED IN ^LRO(68,D0,1,D1,1,\n \n b. Field IN COMMON ACCESSION (#15.1) in ACCESSION NUMBER sub-file\n (#68.02) of ACCESSION file (#68) is added to the data dictionary\n to store the reference to the 'in common' accession when this\n relationship exists. Routine LRWLST11 will update this field when\n appropriate.\n \n STANDARD DATA DICTIONARY #68.02 -- ACCESSION NUMBER SUB-FILE\n STORED IN ^LRO(68,D0,1,D1,1,\n \n \n DATA NAME GLOBAL DATA\n ELEMENT TITLE LOCATION TYPE\n -----------------------------------------------------------------------\n \n 68.02,15 ACCESSION .2;1 FREE TEXT\n \n PRINTABLE ACCESSION\n INPUT TRANSFORM: K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>15!\n ($L(X)<7) X\n LAST EDITED: MAR 03, 2005\n DATA NAME GLOBAL DATA\n HELP-PROMPT: ANSWER MUST BE ACCESSION, e.g., CH 0428 125\n DESCRIPTION: The printable form of the Accession is\n stored here.\n \n \n 68.02,15.1 IN COMMON ACCESSION AD;1 FREE TEXT\n \n INPUT TRANSFORM: K:$L(X)>15!($L(X)<7) X\n LAST EDITED: MAR 03, 2005\n HELP-PROMPT: Answer must be 7-15 characters in length\n ELEMENT TITLE LOCATION TYPE\n DESCRIPTION: When this accession area is 'in common'\n with another accession area the printable\n form of the 'in common' accession is stored\n here.\n \n c. Field LOG (#.001) in ACCESSION NUMBER sub-file (#68.02) of ACCESSION\n file (#68) is modified to increase the upper limit of accession\n numbers from 9999 to 999999.\n \n STANDARD DATA DICTIONARY #68.02 -- ACCESSION NUMBER SUB-FILE\n -----------------------------------------------------------------------\n STORED IN ^LRO(68,D0,1,D1,1,\n \n DATA NAME GLOBAL DATA\n ELEMENT TITLE LOCATION TYPE\n --------------------------------------------------------------------\n \n 68.02,.001 LOG NUMBER\n \n INPUT TRANSFORM: K:+X'=X!(X>999999)!(X<1)!(X?.E1"."1.N) X\n LAST EDITED: MAR 14, 2005\n====================\n \n HELP-PROMPT: Type a number between 1 and 999999, 0 Decimal\n Digits\n DESCRIPTION: The numeric part of the accession.\n \n \n d. The functionality to allow the user to force an accession to a\n specific number could cause a 'stack overflow' error due to how the\n M NEW command was implemented. Coding changes to LRWLST1 will only\n NEW certain variables once.\n \n 68.02,15 ACCESSION .2;1 FREE TEXT\n e. Direct READs in routine LRWLST1 have been replaced with FileMan\n supported DIR reader API calls.\n \n \n2. HD0000000093193:\n-------------------\nA user reported an <UNDEFINED>WN1A^LRWLST1 error when accessioning. This\nwould occur when attempting to force an accession number for an accession\narea that did not have any accessions for the current accession day.\nRoutine LRWLST1 will now handle displaying a default accession number 1\n \nwhen there are no existing accessions for the current accession day.\n \n \n3. HD0000000102626:\n-------------------\nA user reported a <SUBSCRIPT>GRID+21^LR7OGMG error when using the CPRS Lab\nReports tab to display recent laboratory results. This would occur when\nthere are three or more tests on an accession, at least two of the tests\nwere performed at different laboratories and a third test had a 'pending'\nresult and therefore no performing laboratory designated. The software\n PRINTABLE ACCESSION\nwas attempting to determine the performing laboratory for the pending\ntest. Routine LR7OGMG will now ignore tests that do not have a performing\nlaboratory when constructing the list of performing laboratories\nassociated with an accession's test results.\n \n \nINSTALLATION INSTRUCTIONS\n-------------------------\n The install time for this patch is less than 5 minute. This patch\n can be installed when Laboratory users are on the system.\n INPUT TRANSFORM: K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>15!\n Suggested time to install: non-peak requirement hours.\n \n \nNOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n \n ($L(X)<7) X\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 3. From this menu, you may then elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*331):\n a. Print Transport Global\n b. Backup a Transport Global\n LAST EDITED: MAR 03, 2005\n c. Compare Transport Global to Current System\n d. Verify Checksums in Transport Global\n \n Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 4. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*331'.\n \n When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n HELP-PROMPT: ANSWER MUST BE ACCESSION, e.g., CH 0428 125\n Install? YES//' choose 'NO'. Responding 'Yes' to the prompt for\n rebuilding menu trees can significantly increase install time.\n \n When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES// choose 'NO'. \n \n When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\n \n The install will automatically disable the following options:\n DESCRIPTION: The printable form of the Accession is\n \n Accession order then immediately enter data [LR ACC THEN DATA]\n Batch data entry (chem, hem, tox, etc.) [LRSTUF]\n Bypass normal data entry [LRFAST]\n Fast Bypass Data Entry/Verify [LRFASTS]\n Special test accessioning [LRNONCOM]\n Merge Accessions [LRACC MERGE]\n Add tests to a given accession [LRADD TO ACC]\n Add tests to an already existing order number. [LRADD TO ORDER]\n Lab add test(s) to an existing order [LRADDTST]\n stored here.\n Delete entire order or individual tests [LRCENDEL]\n Remove an accession [LRDELOG]\n Referral Patient Multi-purpose Accession [LRLEDI]\n Accessioning, standard (Microbiology) [LRMICROLOGIN]\n Accessioning tests ordered by ward order entry [LROE]\n Lab test order [LROW]\n Fast lab test order (IMMEDIATE COLLECT) [LROW IMMED COLLECT]\n Fast lab test order (ROUTINE) [LROW ROUTINE]\n Fast lab test order (SEND PATIENT) [LROW SEND PAT]\n Fast lab test order (WARD COLLECT) [LROW WARD COL]\nVISTA Laboratory Package patch LR*5.2*331 contains changes to software\n \n Receipt of routine lab collection from wards [LRPHEXCPT]\n Itemized routine lab collection [LRPHITEM]\n Manually accession QC, Environmental, etc. [LRQCLOG]\n Multipurpose accessioning [LRQUICK]\n Delete test from an accession [LRTSTOUT]\n \n \n Note: Routine LR331 will be deleted after successful patch installation. \n \n \n \nINSTALLATION EXAMPLE\n====================\n \nSelect Installation Option:\n \nSelect Kernel Installation & Distribution System Option: Installation\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*331 Loaded from Distribution Loaded from\nDistribution 3/10/05@16:26:40\n 68.02,15.1 IN COMMON ACCESSION AD;1 FREE TEXT\n => LR*5.2*331 \n \nThis Distribution was loaded on Mar 10, 2005@16:26:40 with header of\n LR*5.2*331 \n It consisted of the following Install(s):\n LR*5.2*331\nChecking Install for Package LR*5.2*331\nWill first run the Environment Check Routine, LR331\n \n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*331\n \nIncoming Files:\n \n \n 68 ACCESSION (Partial Definition)\n INPUT TRANSFORM: K:$L(X)>15!($L(X)<7) X\nNote: You already have the 'ACCESSION' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\n LAST EDITED: MAR 03, 2005\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET\n \n \n Install Started for LR*5.2*331 :\n Mar 10, 2005@16:27:01\n \nBuild Distribution Date: Mar 10, 2005\n \n HELP-PROMPT: Answer must be 7-15 characters in length\n Installing Routines:\n Mar 10, 2005@16:27:01\n \n Running Pre-Install Routine: PRE^LR331\n \n *** Pre install started ***\n \n Deleting Field #15 in file #68, ACCESSION\n \n Field will be installed as part of KIDS installation\n DESCRIPTION: When this accession area is 'in common'\n \n *** Pre install completed ***\n \n Installing Data Dictionaries:\n Mar 10, 2005@16:27:01\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION\n Mar 10, 2005@16:27:01\n with another accession area the printable\n \n Running Post-Install Routine: POST^LR331\n \n *** Post install started ***\n \n *** No action required ***\n \n *** Post install completed ***\n \n Sending install completion alert to mail group G.LMI\n form of the 'in common' accession is stored\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*331 Installed.\n Mar 10, 2005@16:27:01\n \n Install Message sent #xxxx\n \ncontrolled by VHA DIRECTIVE 2004-058, titled VISTA BLOOD BANK SOFTWARE.\n here.\nInstall Completed\n \nROUTINE SUMMARY:\n================\nThe following routines are included in this patch. The second line of\neach of these routines now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patchlist]**;Sep 27, 1994\n \n Checksum Checksum\n \nRoutine Name Before Patch After Patch Patch List\n------------ ------------ ----------- ------------\nLR331 N/A 5261822 331 (Deleted by KIDS)\nLR7OGMG 5478031 5490638 187,230,286,290,331\nLRWLST1 12664045 11171614 48,65,121,153,261,286,331\nLRWLST11 16883055 15996378 121,128,153,202,286,331\n\n The LOG field (#.001) in the ACCESSION NUMBER sub-file (#68.02) of\n the ACCESSION file (#68) is modified to increase the upper limit\n of accession numbers from 9999 to 999999.\n \n STANDARD DATA DICTIONARY #68.02 -- ACCESSION NUMBER SUB-FILE\n STORED IN ^LRO(68,D0,1,D1,1,\n \n DATA NAME GLOBAL DATA\nChanges include: \n ELEMENT TITLE LOCATION TYPE\n --------------------------------------------------------------------\n \n 68.02,.001 LOG NUMBER\n \n INPUT TRANSFORM: K:+X'=X!(X>999999)!(X<1)!(X?.E1"."1.N) X\n LAST EDITED: MAR 14, 2005\n HELP-PROMPT: Type a number between 1 and 999999, 0 Decimal\n Digits\n DESCRIPTION: The numeric part of the accession.\n \n \nAll of the above changes have been reviewed by the VISTA Blood Bank\nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE\ncontrol functions.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*331 have no effect on Blood\nBank software functionality, therefore RISK is none.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*331 does not\nalter or modify any software design safeguards or safety critical elements\n The patch will remove the "AD" cross-reference from the ACCESSION\nfunctions.\n \nPOTENTIAL IMPACT ON SITES: This patch contains changes to 0 routines and 1\nfile identified in Veterans Health Administration (VHA) Directive 2004-058,\ngroup B listing. The changes have no effect on Blood Bank functionality or\nmedical device control functions. There is no adverse potential to sites.\n \n \nVALIDATION REQUIREMENTS BY OPTION: \nThere are no validation requirements for this patch.\n field (#15) in the ACCESSION NUMBER sub-file (#68.02) in the\n \nMINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL FUNCTIONS:\nThere are no test case scenarios for this patch.\n============================================================================\n \nPatch Description:\n==================\nThis patch addresses 3 issues in the Laboratory package pertaining to \naccessioning.\n \n ACCESSION file (#68).\n \nASSOCIATED REMEDY TICKETS:\n==========================\n1. HD0000000071160 - LOCKED ACCESSION AREA\n \n2. HD0000000093193 - <UNDEFINED>WN1A^LRWLST1\n \n3. HD0000000102626 - Error - <SUBSCRIPT>GRID+21^LR7OGMG\n Duplicates: HD0000000102632\n HD0000000103751\n\n
\nPatch LR*5.2*158\n-----------------\nRoutine List\n Before After Patch\nRoutine Check Sum Check Sum List\n \nLRCAPPH 9623897 10294589 1,19,127,136,138,158\nLRCAPPH1 7546206 4949612 127,136,138,158\n \n-----------------\nFiles/Fields\nDefault PCE Provider/Phlebotomy Workload Capture\n \nFile: LABORATORY SITE (#69.9)\nField: PCE DEFAULT PROVIDER (#617)\nFile: LAB ORDER ENTRY\nField: PCE ENC (#30)\n \n------------------\nInstallation Instructions:\n \n1. All users may remain on the system.\n \n2. No options need be placed out of order.\n3. Install patch during non-peak hours.\n4. Laboratory specimens should not be accessioned or verified during\n installation of the patch.\n5. The Auto-Instruments 'LAB' job does not have to be stopped.\n6. Installation time of this patch is less than ten minutes.\n7. Journal requires no special attention.\n8. No options are contained in this patch\n \nNOIS List (Partial List)\nPurpose of the Patch:\n===========================\nMILW-1196-41783\nMOU-1196-31178\nSEP-1196-62013\nMAD-0297-41389\n===========================\nTest Site:\nAlpha Test Site: Long Beach\n \n------------------\nThis patch contains two enhancements. (1) Provide a PIMS certified Default\nPatch Description:\n \nThis patch provides a new field, PCE DEFAULT PROVIDER, in the LABORATORY\nSITE (#69) file to support the Laboratory PCE API workload data capture.\nThe default provider is defined locally based on PCE/PIMS workload\nprovider screening criteria. It is the responsibility of the LIM to\ncoordinate with the PCE/PIMS Coordinator to ensure that this field is\nproperly defined and maintained.\n \nFailure to enter a default provider will cause PCE and Laboratory\nProvider to be used for laboratory Patient Care Database workload\nphlebotomy workload data NOT TO BE PROCESSED. NONE of the workload data is\nlost. No default provider causes the workload data processing software to\nstop and wait until the field is properly defined.\n \nThe software logic will check the ordering provider for no termination\ndate and person class for the encounter date. If the ordering provider\nfails this check the default provider will be used instead.\n \nA cleanup utility will be provided to deal with previous provider\nrejection errors by reprocessing encounters using the default provider\ncollected via PCE API. (2) Correct excessive counting of laboratory\ninstead of the ordering provider of record.\n---------------------\nSecond Enhancement:\n \nLaboratory phlebotomy counts were being credited for non patient\nspecimens. Also other factors were inflating phlebotomy workload. A code\nchange now screens all workload to ensure that only patients from the\nPatient (#2) file are processed. Software logic has been change to capture\n1 phlebotomy count for each LAB ORDER with a collection type of Send\nPatient (SP), Immediate Collect (I) or Lab Collect (LC).\nphlebotomy workload.\n \nThe inflated phlebotomy counts coincide with the installation of patch\nLR*5.2*138. It is recommended that the manual counts be used for the date\nrange between this patch and LR*5.2*138 instead of the LMIP generated\ntotals. After this patch is installed the manual totals should match\nauto-captured phlebotomy totals +/- 5%. \n \n\n
\nThis patch corrects an improperly formatted FileMan call.\n\n
\nThis patch corrects a problem with 2 CPRS displays which show a \ncollection time that is not correct. \n\n
\nThis patch corrects a problem whereby a partial AP report is\nsent to TIU.\n\n
\nThis is a general purpose lab patch.\n\n
\nThis patch adds a new routine LREGFR2 to support a new constant value of \n175 for the eGFR formula. It details the creation of a new delta check \nEGFR2 to call the new routine and how to edit the existing Creatinine \nrecord in the LABORATORY TEST file (file # 60) to use the new delta check.\n\n
\n \n \n \nThis patch corrects a problem with the Labserver reports\nwhereby the reports are held up because the subject line \nin the MailMan message is too long (greater than 65 characters).\n\n
\nThis patch corrects a problem related to "in common" accession\nareas when tests with unique accession numbers are involved.\n\n
\n \n \n \nThis patch corrects a problem whereby a <SUBSCRIPT> error occurs\nin routine LA7ADL because of an inability to get a lock for setting\ndata into file 68 (Accession file) in routine LRWLST1.\n\n
\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*365 does not \nBank software functionality, therefore RISK is none.\nin the Clinical Reports section under the Reports tab of the CPRS GUI or \nto a List manager display of the associated report results.\n \nThis patch provides action alerts for Anatomic Pathology reports including\nElectron Microscopy (EM), Surgical Pathology (SP), Cytology (CY), and \nAutopsy (AU) reports. These action alerts are sent automatically to the\nordering provider and the primary care physician (PCP) at the time the\nreport is released. If requested, alerts may be sent to additional\nperson(s). These additional alerts are also action alerts. This\nfunctionality is now the same whether electronic signature (ES) is \n \nturned ON or OFF. Before this patch, additional alerts could not be\nrequested with electronic signature (ES) turned OFF.\n \nThe Supplementary report release, anat path [LRAPRS] option now sends \naction alerts automatically to the ordering provider and the PCP at the\ntime the supplementary report is released. If requested, alerts may be\nsent to additional person(s). These additional alerts are also action\nalerts. These alerts are sent whether electronic signature is turned ON\nor OFF.\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n Modified options:\n ================\n NAME: LRAPR\n MENU TEXT: Verify/release reports, anat path\n TYPE: run routine\n LOCK: LRVERIFY\n DESCRIPTION: This option is used to verify/release pathology reports.\n The user is prompted for the accession number of the report to be\n released. If electronic signature is not activated, the user is asked if\n the report is to be released, yes or no. If electronic signature has been\nmade, no specific validation requirements exist as a result of \n activated, the option is used to electronically sign and store pathology\n reports. It also allows CPT coding to be performed regardless of the\n release status of the chosen report. Another feature is the ability to\n print SNOMED codes for the given accession/report. Action alerts are\n sent automatically to the ordering provider and the primary physician or\n PCP at the time the report is released. If requested, alerts may be sent\n to additional person(s) and/or mail group(s). These additional alerts are\n also action alerts.\n ROUTINE: LRAPR \n \ninstallation of this patch.\n NAME: LRAPRS\n MENU TEXT: Supplementary report release, anat path\n TYPE: run routine\n DESCRIPTION: Releases supplementary reports for Surgical Pathology,\n Cytopathology, Electron Microscopy, or Autopsy. If all supplementary \n reports that exist for the chosen accession have already been released or\n if no supplementary reports exist for the accession, the user will be\n notified. If electronic signature is not activated, the user is asked if\n the report is to be released, yes or no. If electronic signature has\n been activated, the option is used to sign and store the supplementary\n \n report. Action alerts are sent automatically to the ordering provider and\n the primary physician or PCP at the time the supplementary reports are\n released. If requested, alerts may be sent to additional person(s)\n and/or mail group(s). These additional alerts are also action alerts.\n These alerts are sent whether electronic signature is on or off.\n ROUTINE: EN^LRAPR\n \n3) This patch provides a new option, Send an AP Alert [LRAP ALERT] \navailable on the Verify/release menu, anat path [LRAPVR] menu which\nallows a pathologist to send an action alert to a provider or other\nThis patch is being distributed in the OR*3*243 CPRS v27 build.\nperson(s) or mail group(s) after the case has been released. The use\nof this option requires the LRVERIFY key. Before, if they did not answer\nYES to the prompt to send an alert after a report was released, an alert\ncould not be sent unless the case was reopened and re-released.\n \n \n New Option:\n ===========\n NAME: LRAP ALERT MENU TEXT: Send an AP Alert\n TYPE: run routine\n \n LOCK: LRVERIFY\n DESCRIPTION: This option allows a pathologist to send an action alert \n to a provider or other person(s) or mail group(s) after the case has been\n released. \n ROUTINE: LRAPALRT \n \nThe following option was modified to include the new option, Send an AP \nAlert [LRAP ALERT] on the Verify/release menu, anat path [LRAPVR] menu.\n \n Modified Option:\nVistA Laboratory Anatomic Pathology (AP) Alerts and Clinical Patient \n ================\n NAME: LRAPVR\n MENU TEXT: Verify/release menu, anat path\n TYPE: menu\n DESCRIPTION: Anatomic pathology verify and release option menu. \n ITEM: LRAPR SYNONYM: RR\n DISPLAY ORDER: 1\n ITEM: LRAPV SYNONYM: LU\n DISPLAY ORDER: 3\n ITEM: LRAPRS SYNONYM: RS\nRecord System (CPRS) Report Changes Patch LR*5.2*365 software \n DISPLAY ORDER: 2\n ITEM: LRCAPES SYNONYM: CPT\n DISPLAY ORDER: 4\n ITEM: LRAP ALERT SYNONYM: SA\n \n Associated E3R:\n ===============\n 19879\n 18132\n 19040\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nrelease addresses 7 Patient Safety Issues (PSIs). Individual reports \n 19516\n 19106\n \n \n \n Associated Remedy:\n ==================\n HD0000000087038\n HD0000000145148\n HD0000000175194\nare displayed as one continuous scrolling display. A single row of \n HD0000000071165\n HD0000000175887\n \n Duplicate Remedy:\n =================\n HD0000000200282\n HD0000000161040\n HD0000000117241\n HD0000000131803\n HD0000000159885\nthe equal (=) sign is used to separate one report from the next. \n \n Associated PSI:\n ===============\n PSI-05-027\n PSI-07-135\n PSI-05-001\n PSI-06-134\n PSI-06-068\n PSI-07-031\n PSI-07-014\nAdditionally, the text- "Next SURGICAL PATHOLOGY Specimen..." is \n \n \n Test Sites:\n ===========\n \nCharleston, SC - Large\nCleveland, OH - Large\nHeartland-East HCS - Large/Integrated\nHudson Valley HCS - Medium/Integrated\nLoma Linda, CA - Large\nalso used to separate reports. However, with multiple reports and \nNorthern California HCS - Large\nPalo Alto HCS - Large/Integrated\nPhiladelphia, PA - Large\nPuget Sound HCS - Large/Integrated\nSan Diego, CA - Large\nTampa, FL - Large\n \n \nSoftware Retrieval\n==================\nthe use of single dashed lines in each report, it can be difficult \nVistA Laboratory AP Alerts and CPRS Report Changes Patch LR*5.2*365\nsoftware is distributed by PackMan.\n \nDocumentation Retrieval\n=======================\nVistA AP Alerts and CPRS Report Changes Patch LR*5.2*365 \nUser Guide is available at the following Office of Information Field\nOffices (OIFOs) ANONYMOUS.SOFTWARE directories:\n \nOI Field Office FTP Address Directory\nto distinguish the separation between AP reports. A new API has been \n--------------- ----------- ---------\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\n \n \nDocumentation Retrieval Formats\n===============================\nVistA AP Alerts and CPRS Report Changes Patch LR*5.2*365 User \nGuide files are exported in the following retrieval formats:\ncreated (EN^LR7OSAP4) for retrieving a detailed report for an \n \nFile Name Contents Retrieval Formats\n--------- -------- -----------------\nLAB_LR_52_365_UG.doc AP Alerts and CPRS Report Changes \n Patch LR*5.2*365 User Guide BINARY\n \nLAB_LR_52_365_UG.pdf AP Alerts and CPRS Report Changes\n Patch LR*5.2*365 User Guide BINARY\n \nVistA Website Locations:\nindividual Anatomic Pathology Specimen. This helps resolve the PSI \n========================\nVistA AP Alerts and CPRS Report Changes Patch LR*5.2*365 User Guide is\naccessible in MS Word (.doc) and Portable Document Format \n(.pdf) at the following VistA locations:\n \nLaboratory Version 5.2 Home Page\n--------------------------------\nhttp://vista.domain.ext/ClinicalSpecialties/lab/\n \nVistA Documentation Library (VDL)\nby allowing a package interface, like CPRS, to present each \n---------------------------------\nwww.domain.ext/vdl/\n \n \nInstallation Instructions:\n==========================\nThis patch is being distributed in the OR*3.0*243 CPRS v27 build.\n \nThis patch may be installed with users on the system; however, it should\nbe installed at a non-peak time to minimize disruption to the users.\nDIRECTIVE 2004-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\naccession and related specimens to the user and then display the \nInstallation of this patch should take less than 1 minute.\n \n1. Use the INSTALL/CHECK MESSAGE option on the PackMan Menu. \n \n2. From the Kernel Installation and Distribution System (KIDS) Menu, \n select the Installation menu. \n \n3. From the Installation menu, you may select to use the following \n options (when prompted for INSTALL NAME, enter LR*5.2*365): \n \nrelated report for the accession/specimens.\n a. Backup a Transport Global \n b. Compare Transport Global to Current System\n c. Print Transport Global \n d. Verify Checksums in Transport Global\n \n4. Use the Install Package(s) option and select the package LR*5.2*365.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//', respond YES. Responding "Yes" to this prompt can\n significantly increase install time.\n \n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//',\n respond NO.\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//', respond NO.\n \n Note: Routine LR365 will be deleted after successful patch installation.\n \nRoutine Information:\nPatches OR*3*210 and LR*5.2*311 implemented informational alerts \n====================\nThe second line of each of these routines now looks like:\n ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \nRoutine Name: LR365\n Before: n/a After: B3322693 **365**\nRoutine Name: LR7OSAP2\ngenerated for AP pathology results. Recipients of VA view alerts for \n Before: B59162352 After: B59966352 **230,256,259,317,365**\nRoutine Name: LR7OSAP4\n Before: n/a After: B2801060 **365**\nRoutine Name: LRAPALRT\n Before: n/a After: B3310137 **365**\nRoutine Name: LRAPDA\n Before: B76606340 After: B81540087 \n**72,73,91,121,248,259,295,317,365**\nRoutine Name: LRAPR\n Before: B84430863 After: B88035016 **72,248,259,317,365**\nAnatomic Pathology complained that clicking on the alert did not \nRoutine Name: LRAPRES1\n Before: B43595923 After: B43214564 **259,336,369,365**\nRoutine Name: LRWOMEN\n Before: B1458269 After: B1173687 **231,248,311,324,365**\n \nRoutine list of preceding patches: 317, 324, 369\nopen up or display the report to them in the same manner as other \nlab alerts are displayed. Once the recipients click on the alert, it \nis gone from view. If they did not make a note as to who the patient \nwas, they can not get the alert back. Providers can easily erase the \n \nalerts without recording the patient's name. A potential malignancy \nreport could be missed. Problem was identified from complaints of \nsurgeons and oncologists/hematologists. To correct this issue the \nnew action alert is provided to display AP reports. The Anatomic \nPathology informational alerts are now modified into action alerts \nthat upon processing will direct the user to the associated report \nin the Clinical Reports section under the Reports tab of the CPRS \nGUI or to a List manager display of the associated report results. \n \nThis patch provides action alerts for Anatomic Pathology tests \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*365 does\nincluding Electron Microscopy (EM), Surgical Pathology (SP), \nCytology (CY), and Autopsy (AU) results. These action alerts are \nsent automatically to the Ordering Provider, Primary Physician, or \nPrimary Care Provider at the time the report is released. If \nrequested, alerts may be sent to additional person(s) and \nmail group(s). These additional alerts are also action alerts. This \nfunctionality is now the same whether electronic signature (ES) is \nturned ON or OFF. Before this patch, additional alerts could not be \nrequested with electronic signature (ES) turned OFF.\n \nnot alter or modify any software design safeguards or safety critical\nThis patch provides the new Send an AP Alert [LRAP ALERT] option \nthat is available on the Verify/release menu, anat path [LRAPVR] \nwhich allows a pathologist to send an action alert to a provider, \nother individuals, or mail group(s) after the report has been \nreleased. Before this software release if the user did not answer \nYES to the prompt to send an alert after a report was released, an \nalert could not be sent unless the AP report was reopened and \nre-released.\n \n1) PSI-05-027 and PSI-07-135 identified a patient safety issue using the\nelements functions.\nCPRS Graphic User Interface (GUI) Lab Tab, Laboratory Results- Anatomic\nPathology (AP). The individual reports are displayed as one continuous\nscrolling display. A single row of equal (=) signs is used to separate\none report from the next. Additionally, the text- "Next SURGICAL\nPATHOLOGY Specimen..." is also used to separate reports. However, with\nmultiple reports and the use of single dashed lines in each report, it\ncan be difficult to distinguish the separation between AP reports.\n \nResolution:\nA new API has been created (EN^LR7OSAP4) for retrieving a detailed report \n \nfor an individual Anatomic Pathology Specimen. This resolves the \nPSI by allowing a package interface, like CPRS, to present each specimen \nto the user and then get the report on the specimen.\n \n2) PSI-06-068, PSI-07-014, PSI-05-001, PSI-06-134, and PSI-07-031\nidentified a patient safety issue with the Anatomic Pathology notification\nalerts. Patches OR*3*210 and LR*5.2*311 implemented informational alerts\ngenerated for pathology results. Recipients of VA view alerts for \nAnatomic Pathology have complained that clicking on the alert does not\nopen up or display the report to them in the same manner as other lab\nRISK ANALYSIS: Changes made by patch LR*5.2*365 have no effect on Blood \nalerts do (CH subscripted). Once they click on the alert, it's gone from\nview. If they didn't make a note as to who the patient was, they can't\nget it back. It would be helpful to have an action alert for these\nresults. Providers can easily erase them without recording the patient's\nname. A potential malignancy report could be missed. Problem was\nidentified from complaints of surgeons and oncologists/hematologists.\n \nResolution:\nThe Anatomic Pathology informational alerts are now modified into action\nalerts that upon processing will direct the user to the associated report\n\n
\nThis patch is a general purpose lab patch that addresses 2 issues.\nIt corrects a formatting issue in the option Search for Criticals\n(LRSORC). It also resolves an issue in LR7OSUM1 where 2 identical\nvalues are compared and they are evaluated as different because\none of the values has a trailing or leading 0.\n\n
\nThis is a patch to combine multiple alerts for Lab results. It requires\nthe installation of patch OR*2.5*47.\n\n
\nWorkload Archiving Patch\n\n
\n \n \nThis patch resolves an <UNDEF> scenario in the Short Accession List.\n\n
\nPatch LR*5.2*356 made changes to the way Laboratory Test results are \ndisplayed on the Labs Tab of CPRS GUI.\n \nThis patch will make further modifications to the reports on the Labs Tab \nand Coversheet of CPRS GUI.\n\n
\nThis patch is a VM general purpose lab patch that addresses 3 issues.\nIt corrects a problem with the DSS Lab Results Extract whereby results\nthat are greater than 10 characters long cause the record to be omitted\nfrom the extract. It also addresses a merge problem whereby "ghost"\ntests are added to a merged patient because of a failure to cleanup\nafter the previous merge attempt. The third issue that is addressed \nallows for a result that is supposed to be numeric to be entered with\n2 decimal points. This should not be allowed.\n\n
\nThis patch is a VM general purpose lab patch that addresses 3 issues.\nIt corrects a problem with the inability to enter antibiotic \nconcentrations,\naddresses a problem in file #64.1 (Workload Data) whereby incorrect data\ngets stored in the file when the order date is different from the \ncollection\ndate, and also addresses a problem whereby the draw time designator of\nRANDOM is not displayed on the patient report.\n\n
\nThis patch will allow the Computerized Patient Record System (CPRS) to \n===========================\nDocumentation is available for the entire VBECS package on the \nANONYMOUS.SOFTWRE directory at one of the following Office of Information \n(OI) Field Offices. Sites may retrieve documentation in either the \n".PDF" or "DOC" format in one of the following ways:\n \n1. The preferred method is to FTP the files from :\nDownload.vista.domain.ext\n \n2. Sites may also elect to retrieve documentation directly from a \nspecific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nNOTE: The documentation files listed below will be listed in each of the \nVBECS and LR patches that are part of the VBECS package and associate \npatches, they only need to be downloaded once.\n \nFile Name Retrieval format: Binary\n=========== ==========================\nREQUIRED PATCHES:\n \nKnown Defects and Anomalies.doc\nKnown Defects and Anomalies.pdf\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.doc\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \n \nGuide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) Version 1.4.0.0 User \nGuide Version.doc\nVistA Blood Establishment Computer Software (VBECS) Version 1.4.0.0 User \nGuide Version.pdf\n \nLR*5.2*292\n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system. You may wish to \ninstall it during non-peak hours. Installation will take less than 2 \nminutes.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the Packman menu. [Note: \n TEXT PRINT/DISPLAY option in the PackMan menu will display the \n patch text only.]\n \n \n 2. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n \n 3. From this menu, you may elect to use the following options (when\n prompted for the INSTALL NAME, enter LR*5.2*387).\n \n (a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n===========================\n \n (b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the\n patch is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n \n (c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n \n (d) Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n \n 4. Use the Install Package(s) option and select the package LR*5.2*387.\n \n 5. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES//', respond NO.\n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond NO.\nNEW PROTOCOLS:\n \nretrieve data for the Cumulative report from the pre-existing VBECS API's.\nN/A\n \n===========================\n \nBLOOD BANK CLEARANCE\n \nVISTA Laboratory Package patch LR*5.2*387 contains changes to software \ncontrolled by VHA DIRECTIVE 2004-058, titled VISTA BLOOD BANK SOFTWARE. \nChanges include: \n Routine: LR7OSBR\n \n Routine: LR7OSBR1\n \nAll of the above changes have been reviewed by the VISTA Blood Bank \nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE \ncontrol functions.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*387 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*387 does not \n===========================\nalter or modify any software design safeguards or safety critical \nelements functions.\n \nPOTENTIAL IMPACT ON SITES: This patch contains changes to 2 routines and \n0 files identified in Veterans Health Administration (VHA) Directive \n2004-058, group B listing. The changes have no effect on Blood Bank \nfunctionality or medical device control functions. There is no adverse \npotential to sites.\n \nVALIDATION REQUIREMENTS BY OPTION: \n \nThere are no validation requirements or options to be validated.\n \nMINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL FUNCTIONS:\nThere are no validation scenarios necessary with this patch.\n \n===========================\n \nASSOCIATED NOIS:\n \nN/A\nNEW OPTIONS:\n \n===========================\n \nASSOCIATED E3R:\n \nN/A\n \n===========================\n \nTEST SITES:\n \nCENTRAL TEXAS HCS\nHEARTLAND-EAST HCS\nNORTH CHICAGO, IL\nOKLAHOMA CITY, OK\nPHILADELPHIA, PA\nSAN DIEGO, CA \n \n \nInstallation Sequence \n======================\nN/A\nThe files listed below represent the patches that have either been \nreleased or will be part of the controlled phased release. The first 5 \npatches have been released and already installed. Patches starting with \nnumber 6 and are prefixed with an (*)\nwill need to follow the sequence listed below when your phased \ninstallation occurs.\n \n 1. OR*3.0*243 (released 8/20/08)\n 2. XT*7.3*116 (released ????\n 3. SR*3.0*168 (released ???\n \n 4. ECX*3*102 (released 8/25/08)\n 5. LR*5.2*387 (released ???\n 6. *LR*5.2*335\n 7. *LR*5.2*367\n 8. *VBECS Bundle (consisting of VBECS 1.0 and LR*5.2*325)\n 9. *VBEC*1.0*1\n 10. *OR*3.0*212\n \nDocumentation Retrieval:\n \n\n
\nLR*5.2*335 is being exported as part of the VBECS package release. The \nclinically and historically relevant information. This patch will install \n63.01 BLOOD BANK 141 PT CELLS(ser)+ANTI A IS\n63.01 BLOOD BANK 142 PT CELLS(sal)+ANTI A IS\n63.01 BLOOD BANK 143 PT CELLS+ANTI A SLIDE\n63.01 BLOOD BANK 144 PT CELLS(ser)+ANTI B IS\n63.01 BLOOD BANK 145 PT CELLS(sal)+ANTI B IS\n63.01 BLOOD BANK 146 PT CELLS+ANTI B SLIDE\n63.01 BLOOD BANK 147 PT CELLS(ser)+ANTI A,B IS\n63.01 BLOOD BANK 148 PT CELLS(ser)+ANTI A,B (RT)\n63.01 BLOOD BANK 149 PT CELLS(sal)+ANTI A,B (IS)\n63.01 BLOOD BANK 149.1 PT CELLS(sal)+ANTI A,B (RT)\nthe software necessary to prepare the data for extraction from the VistA \n63.01 BLOOD BANK 149.11 PT CELLS+ANTI A,B SLIDE\n63.01 BLOOD BANK 149.12 PT SERUM+A1 CELLS\n63.01 BLOOD BANK 149.13 PT SERUM+B CELLS\n63.01 BLOOD BANK 151 INTERPRETATION OF ABO TESTING\n63.01 BLOOD BANK 152 ABO TESTING COMMENT\n63.01 BLOOD BANK 153 INTERPRETATION ABO \nGROUP(cell)\n63.01 BLOOD BANK 154 INTERPRETATION ABO GROUP(ser)\n63.011 RBC ANTIGEN PRESENT .01 RBC ANTIGEN PRESENT\n63.011 RBC ANTIGEN PRESENT .02 COMMENT\ndatabase, and extract the data to text files for transfer to the VBECS \n63.0112 RBC ANTIGEN ABSENT .01 RBC ANTIGEN ABSENT\n63.0112 RBC ANTIGEN ABSENT .02 COMMENT\n63.0114 HLA ANTIGEN ABSENT .01 HLA ANTIGEN ABSENT\n63.0114 HLA ANTIGEN ABSENT .02 COMMENT\n63.012 ELUATE ANTIBODY .01 ELUATE ANTIBODY\n63.013 HLA ANTIGEN PRESENT .01 HLA ANTIGEN PRESENT\n63.013 HLA ANTIGEN PRESENT .02 COMMENT\n63.014 SCREEN CELL METHOD .01 SCREEN CELL METHOD\n63.014 SCREEN CELL METHOD .02 TECHNIQUE\n63.014 SCREEN CELL METHOD 1 SCREEN CELL\nsystem. Some of the VistA data will be standardized to nationally \n63.015 SCREEN CELL .01 SCREEN CELL\n63.015 SCREEN CELL .02 SOURCE\n63.015 SCREEN CELL .03 INTERPRETATION\n63.015 SCREEN CELL .04 IS\n63.015 SCREEN CELL .05 37 C\n63.015 SCREEN CELL .06 AHG\n63.015 SCREEN CELL .07 CONTROL CELL\n63.015 SCREEN CELL .08 ROOM TEMP\n63.015 SCREEN CELL .09 12-18 C\n63.015 SCREEN CELL .1 4 C\nrecognized Blood Bank definitions during the extraction. Logical checks \n63.018 RBC TYPING METHOD .01 RBC TYPING METHOD\n63.018 RBC TYPING METHOD .02 TECHNIQUE\n63.018 RBC TYPING METHOD 1 ANTISERUM\n63.019 ANTISERUM .01 ANTISERUM\n63.019 ANTISERUM .02 LOT #\n63.019 ANTISERUM .03 INTERPRETATION\n63.019 ANTISERUM .04 IS\n63.019 ANTISERUM .05 37 C\n63.019 ANTISERUM .06 AHG\n63.019 ANTISERUM .07 CONTROL CELL\nin the software will ensure data integrity. Once the data on the VistA \n63.019 ANTISERUM .08 ROOM TEMP\n63.019 ANTISERUM .09 12-18 C\n63.019 ANTISERUM .1 4 C\n63.199 SPECIMEN COMMENT .01 SPECIMEN COMMENT\n63.46 SERUM ANTIBODY .01 SERUM ANTIBODY\n63.46 SERUM ANTIBODY .02 ANTIBODY COMMENT\n63.48 ANTIBODY SCREEN COMMENT .01 ANTIBODY SCREEN COMMENT\n65.50 Entire File\n66.20 Entire File\n66.50 Entire File\nside have been evaluated and converted to the new database, specific \n66.90 Entire File\n \nThe following options are placed out of order:\nOption Name Option Text\n=======================================================================\nLRBLAD Print data change audits\nLRBLAR Remove data change audits\nLRBLDA Donor collection/deferral edit\nLRBLDAWARD Acknowledge donor award by deletion\nLRBLDC Donor collection/processing\nVistA Blood Bank options will be deactivated (placed out of order) so \nLRBLDCP Collection disposition/component preparation\nLRBLDCU Cumulative donations and awards\nLRBLDCX Edit donor consent\nLRBLDD Donor demographics\nLRBLDDAT ABO/Rh testing of donor units\nLRBLDEDIT Blood donor group/type edit\nLRBLDEF Permanent deferral/special comments\nLRBLDK Remove ex-donors\nLRBLDLG Donor registration\nLRBLDLT Enter/edit donor letters\nthat the legacy database cannot be altered. These options are listed \nLRBLDMV Move a blood donation\nLRBLDO Old blood donor records\nLRBLDPH Donor phenotyping\nLRBLDR Donor history, physical and consent form\nLRBLDRR Test review/Component labeling/release\nLRBLDT Lab tests(not ABO/Rh) on donor units\nLRBLDUC Donor unit ABO/Rh recheck\nLRBLIDN Disposition -not transfused\nLRBLIDR Disposition -relocation\nLRBLILA Unit CAUTION tag labels\nbelow under "The following options are placed out of order." More details \nLRBLILR Log-in regular (invoices)\nLRBLILS Enter blood inventory typing charges\nLRBLISH Shipping invoices for blood components\nLRBLIUC Unit ABO/Rh confirmation\nLRBLIUP Unit phenotyping\nLRBLIUR Units release to stock (cancel) by patient\nLRBLIW Inventory ABO/Rh testing worksheet\nLRBLJM Edit pooled blood product\nLRBLJTR Transfer unit to new division\nLRBLPC Request/select/xmatch blood components\ninstallation of this patch will be controlled by a phase release. An \ncan be found in the "Blood Bank Pre-Implementation Data Validation, \nLRBLPCS Blood component requests\nLRBLPED Pediatric unit preparation\nLRBLPEDIT Patient ABO/Rh edit\nLRBLPER Previous records\nLRBLPET Enter test data\nLRBLPH Patient Medication List\nLRBLPIC Select units for patients\nLRBLPLOGIN Specimen log-in\nLRBLPOST File 81 conversion\nLRBLPSI Special instructions\nMapping, and Conversion ADPAC Guide" document. The inadvertent or \nLRBLPT Blood transfusion results\nLRBLPTXR Unknown unit transfusion reaction\nLRBLPX Enter crossmatch results\nLRBLRIN Supplier invoices (inventory)\nLRBLRIS Special typing charges (inventory)\nLRBLRIT Supplier transactions (inventory)\nLRBLSEB Edit blood product file\nLRBLSEC Edit unit - patient fields\nLRBLSED Edit unit disposition fields\nLRBLSEE Free autologous/directed donor units\nunintentional deactivation of these options could cause a disruption in \nLRBLSEF Edit blood bank descriptions file\nLRBLSEH Edit donor history questions\nLRBLSEL Edit unit log-in\nLRBLSER Remove units with final disposition\nLRBLSET Tests for inclusion in transfusion report\nLRBLSEU Edit blood bank utility file\nLRBLSF Edit number of lines in a label\nLRBLSI Blood bank inventory edit options\nLRBLSLL Edit lab letter file\nLRBLSMS Maximum surgical blood order edit\nBlood Bank operations. \nLRBLSNO Edit Corresponding Antigen/Antibody\nLRBLSP Blood bank patient edit options\nLRBLSPP Edit previous transfusion record\nLRBLSRI Remove inappropriate transfusion requests\nLRBLSRQ Edit Blood Component Request File\nLRBLSSP Edit blood bank site parameters\nLRBLST Tests for display on patient look-up\nLRBLTTW Test worklist\nLRBLTX Tests for transfusion follow-up\nLRBLVAL Blood bank validation documentation\n \n \nRISK ANALYSIS: The changes made by patch LR*5.2*335 affect Blood Bank \nsoftware functionality, however the RISK is considered to be low.\n Inappropriate use of the "Disable VistA Blood Bank components"\n [VBEC BB COMPONENTS DISABLE] option can disable the VistA 5.2\n Blood Bank system. This risk is minimal since the "Enable VistA\n Blood Bank components" [VBEC BB COMPONENTS ENABLE] option can be\n used to restore full operations.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*335 does not \nPlease read and follow the instructions in the "Blood Bank \nalter or modify any software design safeguards or safety critical \nelements functions.\n \nPOTENTIAL IMPACT ON SITES: This patch contains changes to 0 routines and \n4 files identified in Veterans Health Administration (VHA) Directive \n2004-058, group B listing. The changes have no effect on medical device \ncontrol functions.\n This is the final step prior to the transfer of Blood Bank operations\n to the VBECS system. All future impact will be dealt with through VBECS\n development\nPre-Implementation Data Validation, Mapping, and Conversion Installation \n \nVALIDATION REQUIREMENTS BY OPTION:\n No VistA Blood Bank 5.2 options are released with this patch.\n However, the options listed above should be tested to ensure that\n they have been disabled after the completion of the data conversion.\n \n \nFILES CREATED DURING THE INSTALLATION OF THIS PATCH:\nFILE # NAME\n====== ====\nand User Guide" before proceeding with the installation.\n6000 VBECS SITE PARAMETERS\n6001 VBECS DATA INTEGRITY/CONVERSION STATISTICS\n6003 VISTA BLOOD BANK RESTRICTED OPTIONS LIST\n6005 VBECS MATCHING TABLE\n6007 STANDARD VBECS DATA\n6009 VBECS FILE & FIELD LEVEL SECURITY\n \nMAIL GROUPS CREATED DURING THE INSTALLATION OF THIS PATCH\nMAIL GROUP:\n===========\n \nVBECS DATA CONVERSION\n \nROUTINES INSTALLED DURING THE INSTALLATION OF THIS PATCH:\nROUTINE:\n========\nVBECDC00\nVBECDC01\nVBECDC02\nVBECDC19\nVBECDCDC\n \nVBECDCHX\nVBECDCM\nVBECDCM0\nVBECDCM1\nVBECDCM2\nVBECDCMP\nVBECDCNM\nVBECDCR\nVBECDCSP\nVBECDCST\nImplementation Manager will be assigned to your site and will contact \nBLOOD BANK CLEARANCE: 1/6/2009\nVBECDCU\nVBECDCU1\nVBECDCU2\nVBECDCX\nVBECDCX1\n \nOPTIONS CREATED DURING THE INSTALLATION OF THIS PATCH:\nOption Name Option Text\n=========== ===========\nVBEC ANTIBODY/ANTIGEN UTIL. Utilities that manipulate Antibody/Antigen \nVISTA Laboratory Package patch LR*5.2*335 contains changes to software \ndata\nVBEC BB COMPONENTS DISABLE Disable VistA Blood Bank components\nVBEC BB COMPONENTS ENABLE Enable VistA Blood Bank components\nVBEC CONVERSION UTILITIES Utilities used for the data conversion\nVBEC DATA CONV. TO HOST FILES Convert VistA Blood Bank data to host files\nVBEC DATA CONVERSION STATS Display data conversion statistics\nVBEC DATA VALIDATION Run Legacy VistA Blood Bank Data Validation\nVBEC DELETE ANTIBODY/ANTIGEN Delete Antibody/Antigen temporary matching \nfiles \nVBEC DELETE CONV. STATS Delete data conversion and anomaly check \ncontrolled by VHA DIRECTIVE 2004-058, titled VISTA BLOOD BANK SOFTWARE.\nhistories\nVBEC DELETE EXTRACTED DATA Delete all Blood Bank Data in Temporary \nGlobals\nVBEC DELETE SYSTEM LEVEL FILES Delete Blood Bank Data in System Level \nFiles\nVBEC DELETE TRANS. REACTION Delete Transfusion Reaction temporary \nmatch files\nVBEC INVALID DATA REPORT Invalid Blood Bank Data Report\nVBEC MAIN MENU VBECS Data Matching/Conversion Menu\nVBEC MATCH ANTIBODY/ANTIGEN Match VistA antibody/antigen data\nChanges include:\nVBEC MATCH TRANSFUS REACTION Match VistA transfusion reaction data\nVBEC POST-CONVERSION UTILITIES Utilities used after the data conversion \nhas run\nVBEC PRE-CONVERSION UTILITIES Utilities used prior to the data conversion\nVBEC PRINT SQL/VISTA MATCHES Matched Blood Bank data report\nVBEC SITE PARAMETER ENTER/EDIT Enter/Edit Site Parameter Data \nVBEC STANDARD ANTIBODIES Standard Antigens and Antibodies Print\nVBEC STANDARD TRANS. REACTIONS Standard Transfusion Reactions Print\nVBEC TRANS. REACTION UTILITIES Utilities that manipulate Trans. Reaction \ndata\nAccess is restricted on the following files:\nVBEC UNDO ANTIBODY/ANTIGEN Undo all antibody/antigen matches\nVBEC UNDO SINGLE MATCHING Unmatch a single matched VistA record \nVBEC UNDO TRANS. REACTIONS Undo all transfusion reaction matches\nVBEC UNMATCHED VISTA DATA RPT Unmatched VistA Blood Bank Data Report\nVBEC UPDATE ANTIBODY/ANTIGEN Update antibody/antigen records in \nmatching file\nVBEC UPDATE TRANS. REACT. REC Update trans. reaction records in matching \nfile\n \nAssociated Remedy Tickets: None\nFile # File Name Field # Field Name\n==========================\n \nTest Site(s):\n==============\n HEARTLAND-EAST HCS\n PHILADELPHIA, PA\n SAN DIEGO, CA\n \nInstallation Sequence \n======================\n===== ========= ======= ==========\nThe files listed below represent the patches will be part of the \ncontrolled phased release. Follow the sequence listed below when your \nphased installation occurs.\n \n 1. LR*5.2*335\n 2. LR*5.2*367\n 3. VBECS Bundle (consisting of VBEC*1*0 and LR*5.2*325)\n 4. VBEC*1.0*1\n 5. OR*3.0*212\n \n62.55 AGGLUTINATION STRENGTH .01 NAME\nCOMPONENT SUMMARY:\n==================\nThis patch installs ROUTINES, FILES, OPTIONS and a MAIL GROUP. For full \ndetails about the components being imported with this patch, please see \nthe Blood Bank Pre-Implementation Data Validation, Mapping, and \nConversion Technical Manual\n \nDocumentation Retrieval:\n========================\nAlthough this is a controlled, phased released, the user & technical \n62.55 AGGLUTINATION STRENGTH 1 WILL STAND FOR\ndocumentation will be available to all sites when the patch is officially \nreleased and the phased implementations start. This will allow sites the \nopportunity to retrieve the documents before their phased installation \ndate\n \nDocumentation is available for the VBECS package on the \nANONYMOUS.SOFTWARE directory at one of the following Office of \nInformation (OI) Field Offices. Sites may retrieve documentation either \nthe ".PDF" or "DOC" format in one of the following ways:\n \n63.01 BLOOD BANK .01 DATE/TIME SPECIMEN TAKEN\nThe preferred method is to FTP the files from:\nDownload.vista.domain.ext\n \nThis transmits files from the first available FTP server. Sites may also \nelect to retrieve documentation directly from a specific server as \nfollows:\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nyour POC for VBECS and will provide your site with the location of the \n63.01 BLOOD BANK .03 DATE REPORT COMPLETED\nNOTE: The documentation files listed below will be listed in each of the \nVBECS and LR patches that are part of the VBECS package and associate \npatches, they only need to be downloaded once.\n \nFile Name Retrieval format: Binary\n=========== ==========================\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.pdf\n63.01 BLOOD BANK .04 ENTERING PERSON\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.pdf\nVBECS Data Conversion Recommended Validation Method.xls\nVBECS Application Interfacing Support Software Installation and User \n63.01 BLOOD BANK .05 SPECIMEN\nConfiguration Guide.doc\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.pdf\nVBECS Implementation Process.xls\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.doc\n63.01 BLOOD BANK .055 COLLECTION SAMPLE\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.pdf\nKnown Defects and Anomalies.doc\nKnown Defects and Anomalies.pdf\n \n Installation Information:\n ==========================\n \n63.01 BLOOD BANK .06 ACCESSION NUMBER\nThis patch is exported as part of the VBECS Blood Bank System and allows \nthe conversion of limited existing Blood Bank data from VistA to VBECS. \nPlease refer to the "Blood Bank Pre-Implementation Data Validation, \nMapping, and Conversion Installation and User Guide" for installation \ninformation. The files listed below may be obtained via FTP. The \ninstallation of VBECS and its related patches are being handled as a \ncontrolled release. The implementation manager will contact you with the \nlocation of the KIDS Host Files prior to your scheduled installation \ndate. The documentation files will be available for download in advance \nof installation through the anonymous download site as shown below.\n63.01 BLOOD BANK .07 PHYSICIAN\n \n Installation Files: \n ===================\nThe following files are exported for LR*5.2*335:\n LR_52_335.KID\n \n VBECSBATCH.COM\n \nLR_52_335.KID and VBECSBATCH.COM files will be made available by the \nImplementation Manager prior to your site's implementation schedule along \n63.01 BLOOD BANK .08 WARD\nwith instruction to retrieve.\n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system.\nInstallation will take less than 5 minutes.\n \n 1) Use the 'LOAD A DISTRIBUTION' option on the KIDS Installation\n menu. The Host File name is LR_52_335.KID. Answer YES to the\n question: "Want to Continue with Load? YES//"\n63.01 BLOOD BANK .09 PHLEBOTOMIST\n 2) From the Kernel Installation and Distribution System Menu,\n select the Installation menu.\n 3) From this menu, you may elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*335).\n a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n63.01 BLOOD BANK .1 DATE/TIME RECEIVED\n (routines, DDs, templates, etc.).\n c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n d) Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n 4) Use the Install Package(s) option and select the package\n LR*5.2*335.\n 5) When prompted "Enter the Coordinator for Mail Group 'VBECS DATA\n CONVERSION':" Enter the name of the person who will manage the\n63.01 BLOOD BANK .12 ACCESSION LINK\n VBECS DATA CONVERSION mailgroup.\n 6) When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\n of Install? YES// respond YES \n 7) When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n YES//', respond NO.\n 8) When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond NO.\nKIDS Host Files prior to your scheduled installation date installation \n63.01 BLOOD BANK .99 SPECIMEN COMMENT\n63.01 BLOOD BANK 2.1 DIRECT AHG(POLYSPECIFIC)\n63.01 BLOOD BANK 2.2 DIRECT AHG(5 min incub)\n63.01 BLOOD BANK 2.3 DIRECT AHG CC\n63.01 BLOOD BANK 2.4 ANTI-IgG\n63.01 BLOOD BANK 2.5 ANTI-IgG CC\n63.01 BLOOD BANK 2.6 ANTI-COMPLEMENT\n63.01 BLOOD BANK 2.7 ANTI-COMPLEMENT (5 min incub)\n63.01 BLOOD BANK 2.8 ANTI-COMPLEMENT CC\n63.01 BLOOD BANK 2.9 DIRECT AHG INTERPRETATION\nSequence.\n63.01 BLOOD BANK 2.91 DIRECT AHG TEST COMMENT\n63.01 BLOOD BANK 3 ELUATE ANTIBODY\n63.01 BLOOD BANK 4 SCREEN CELL METHOD\n63.01 BLOOD BANK 6 ANTIBODY SCREEN \nINTERPRETATION\n63.01 BLOOD BANK 6.1 RBC ANTIGEN PRESENT\n63.01 BLOOD BANK 6.2 RBC ANTIGEN ABSENT\n63.01 BLOOD BANK 6.3 HLA ANTIGEN PRESENT\n63.01 BLOOD BANK 6.4 HLA ANTIGEN ABSENT\n63.01 BLOOD BANK 7 SERUM ANTIBODY\n \n63.01 BLOOD BANK 8 ANTIBODY SCREEN COMMENT\n63.01 BLOOD BANK 9 RBC TYPING METHOD\n63.01 BLOOD BANK 10 ABO INTERPRETATION\n63.01 BLOOD BANK 10.2 ABO TYPING TECH\n63.01 BLOOD BANK 10.3 ABO TESTING COMMENT\n63.01 BLOOD BANK 11 RH INTERPRETATION\n63.01 BLOOD BANK 11.2 RH TYPING TECH\n63.01 BLOOD BANK 11.3 RH TESTING COMMENT\n63.01 BLOOD BANK 121 PT CELLS+ANTI D (sal)\n63.01 BLOOD BANK 122 PT CELLS+RH CTRL (sal)\nSelect elements of VistA data must be transferred to the VBECS Blood Bank \n63.01 BLOOD BANK 123 PT CELLS(sal)+ANTI D(hp IS)\n63.01 BLOOD BANK 124 PT CELLS(ser)+ANTI D(hp IS)\n63.01 BLOOD BANK 125 PT CELLS+ANTI D (hp 37)\n63.01 BLOOD BANK 126 PT CELLS+ANTI D (hp AHG)\n63.01 BLOOD BANK 127 PT CELLS+ANTI D SLIDE (hp)\n63.01 BLOOD BANK 128 PT CELLS(sal)+RH CTRL (hp IS)\n63.01 BLOOD BANK 129 PT CELLS(ser)+RH CTRL(hp IS)\n63.01 BLOOD BANK 129.1 PT CELLS+RH CTRL (hp 37)\n63.01 BLOOD BANK 129.11 PT CELLS+RH CTRL (hp AHG)\n63.01 BLOOD BANK 129.12 PT CELLS+RH CTRL SLIDE (hp)\nsystem prior to its initial operation. This will preserve patient related \n63.01 BLOOD BANK 131 INTERPRETATION OF RH TESTING\n63.01 BLOOD BANK 132 RH TEST COMMENT\n63.01 BLOOD BANK 133 PT Cells(sal)+Anti D(mod) IS\n63.01 BLOOD BANK 134 PT Cells(ser)+Anti D(mod) IS\n63.01 BLOOD BANK 135 PT Cells+Anti D(mod) 37\n63.01 BLOOD BANK 136 PT Cells+Anti D(mod) AHG\n63.01 BLOOD BANK 138 PT Cells(sal)+RH Ctrl(sal) IS\n63.01 BLOOD BANK 139 PT Cells(ser)+RH Ctrl(sal) IS\n63.01 BLOOD BANK 139.1 PT Cells+RH Ctrl(sal) 37\n63.01 BLOOD BANK 139.11 PT Cells+RH Ctrl(sal) AHG\n\n
\nThe installation of LR*5.2*367 will be controlled by phase release to \nthe accession for the specified test and the associated Computerized \nopportunity to retrieve the documents before their phased installation \ndate\n \n \nDocumentation is available for the entire VBECS package on the \nANONYMOUS.SOFTWRE directory at one of the following Office of Information \n(OI) Field Offices. Sites may retrieve documentation either the ".PDF" \nor "DOC" format in one of the following ways:\n \nThe preferred method is to FTP the files from :\nPatient Record System (CPRS) order\n download.vista.domain.ext\n \nThis transmits files from the first available FTP server. Sites may also \nelect to retrieve documentation directly from a \nspecific server as follows:\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nNOTE: The documentation files listed below will be listed in each of the \n \nVBECS and LR patches that are part of the VBECS package and associate \npatches, they only need to be downloaded once.\n \nFile Name: Retrieval format: Binary\n========== ==========================\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nROUTINE: LR7OVB\nInstallation and User Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.pdf\nVBECS Data Conversion Recommended Validation Method.xls\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.doc\n========\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.pdf\nVBECS Implementation Process.xls\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \n \nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.pdf\nKnown Defects and Anomalies.doc\nKnown Defects and Anomalies.pdf\n \nInstallation Files: \n===================\n \nLR_52_367.KID\nOPTIONS: None\n \n \nThe host file LR_52_367 will be made available by the Implementation \nManager prior to your site's implementation schedule along with \ninstruction to retrieve.\n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system.\nInstallation will take less than 5 minutes.\n========\n \nThe installation of VBECS and its related patches are being handled as a \ncontrolled release. The implementation manager will contact you with the \nlocation of the KIDS Host Files prior to your scheduled installation date.\n \n 1) Use the 'LOAD A DISTRIBUTION' option on the KIDS Installation\n menu. The Host File name is LR_52_367.KID . Answer YES to the\n question: "Want to Continue with Load? YES//"\n 2) From the Kernel Installation and Distribution System Menu,\n select the Installation menu.\n \n \n 3) From this menu, you may elect to use the following options\n (when prompted for the INSTALL NAME, enter LR*5.2*367).\n a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\nPROTOCOL: LR7O VBECS RECEIVE\n c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n d) Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n 4) Use the Install Package(s) option and select the package\n LR*5.2*367.\n 5) When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n YES//', respond NO.\n 6) When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\nsupport the new blood bank software Vista Blood Establishment Computer \n=========\n Protocols? YES//', respond NO.\n \nBLOOD BANK CLEARANCE\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*367 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nDIRECTIVE 2004-053 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*367 does not \nalter or modify any software design safeguards or safety critical \nSystem, VBECS. An Implementation Manager will be assigned to your site \nelements functions.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*367 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nmade, no specific validation requirements exist as a result of \ninstallation of this patch.\n \n \nand will contact your POC for VBECS and will provide your site with the \nASSOCIATED Remedy Tickets: None\n==========================\n \nASSOCIATED NSR/E3R: None\n===================\n \nXINDEX Warnings:\n================\nXINDEX displays the following warning. The referenced routine (^ORMVBEC) \nwill be installed with patch OR*3*212. This patch is part of the \nlocation of the KIDS Host Files prior to your scheduled installation date.\ncontrolled release of VBECS and will be installed as part of the VBECS \nsystem installation.\n \nLR7OVB * * 105 Lines, 4318 Bytes, Checksum: B19945746\n COMPLETE+38 F - Reference to routine '^ORMVBEC'. That isn't in this \nUCI.\n \n--- Routine Detail ---\n***** ERRORS & WARNINGS IN LR7OVB *****\n COMPLETE+38 F - Reference to routine '^ORMVBEC'. That isn't in this \n \nUCI.\n \n***** INDEX OF LR7OVB *****\n \nTEST SITES:\n===========\nHEARTLAND-EAST HCS\nPHILADELPHIA, PA\nSAN DIEGO, CA\n \nThis patch will allow the VistA Blood Establishment Computer System \nREQUIRED BUILDS: None\n================\n \nInstallation Information:\n==========================\n \nThis patch LR*5.2*367 is being exported as part of the VBECS package \nrelease. This installation of these patches will be controlled by phase \nrelease. An Implementation Manager will be assigned to your site and will \ncontact your POC for VBECS and will provide your site with the location \n(VBECS) to use HL7 order update messages to complete orders created \nof the KIDS Host Files prior to your scheduled installation date \nInstallation Sequence\n \nInstallation Sequence \n======================\nThe files listed below represent the patches will be part of the \ncontrolled phased release. Follow the sequence listed below when your \nphased installation occurs.\n \n 1. LR*5.2*335\nthrough the Blood Bank Accession Area. The functionality will complete \n 2. LR*5.2*367\n 3. VBECS Bundle (consisting of VBEC*1*0 and LR*5.2*325)\n 4. VBEC*1.0*1\n 5. OR*3.0*212 \n \nDocumentation Retrieval:\n========================\nAlthough this is a controlled, phased released, the user & technical \ndocumentation will be available to all sites when the patch is officially \nreleased and the phased implementations start. This will allow sites the \n\n
\nLR*5.2*325 is being exported as part of the VBECS_BUNDLE_1.KID package \nROUTINES:\nGuide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.pdf\nKnown Defects and Anomalies.doc\nKnown Defects and Anomalies.pdf\n \n=========\nInstallation Instructions:\n==========================\nThis patch is exported as part of VBECS_BUNDLE_1.KID. Please refer to \nVBEC*1*0 install instructions for installation sequence information. \nLR325 \nLRCAPBB \nLRCAPBV \nLRCAPBV1 \n \nOptions: None\n========\n \nrelease. The installation of this bundle will be controlled by phase \n \nProtocols: None\n========== \n \nRemote Procedures: None\n===============\n \n \nFiles: None\n======\nrelease. An Implementation Manager will be assigned to your site and \n \nAssociated ICRs: None\n=============== \n \n \nAssociated Remedy: None\n==================\n \n \nAssociated NSR/E3R: None\nwill contact your POC for VBECS and will provide your site with the \n==============\n \n \nInstallation Sequence\n=====================\n \nThe files listed below represent the patches will be part of the \ncontrolled phased release. Follow the sequence listed below when your \nphased installation occurs.\n \nlocation of the KIDS Host Files prior to your scheduled installation date \n 1. LR*5.2*335\n 2. LR*5.2*367\n 3. VBECS Bundle (consisting of VBEC*1*0 and LR*5.2*325)\n 4. VBEC*1.0*1\n 5. OR*3.0*212\n \nDocumentation Retrieval:\n \nAlthough the software installation will be phased, the documentation will \nbe available for the entire VBECS package on the ANONYMOUS.SOFTWRE \nInstallation Sequence. The VBECS BUNDLE is a host file that consists of \ndirectory or at one of the following Office of Information (OI) Field \nOffices. Sites may retrieve documentation either the ".PDF" or "DOC" \nformat in one of the following ways:\n \n1. The preferred method is to FTP the files from : \nDownload.vista.domain.ext\n \n2. Sites may also elect to retrieve documentation directly from a \nspecific server as follows:\n Albany ftp.fo-albany.domain.ext\nboth VBEC*1*0 and LR*5.2*325. Installation of the VBECS BUNDLE will \n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nNOTE: The documentation files listed below will be listed in each of the \nVBECS patches that are part of the VBECS package and associate patches, \nthey only need to be downloaded once.\n \nFile Name Retrieval format: Binary\n========= =========================\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nautomatically install both VBEC*1*0 and LR*5.2*325\nADPAC Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \n \nTechnical Manual.pdf\nVBECS Data Conversion Recommended Validation Method.xls\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.doc\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.pdf\nVBECS Implementation Process.xls\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \n\n
\nMISCELLANEOUS- HOUSEKEEPING\n-includes fix for wrong lab sample when a UA is ordered\n\n
\nBLOOD BANK\n63.09,20 DESCRIPTION Delete\n \nINSTALLATION INSTRUCTIONS: \n========================== \nThis patch can be installed with users on the system. It is recommended \nto disable the Anatomic Pathology [LRAP] option at the "DISABLE Scheduled\nOptions, Menu Options, and Protocols?" prompt.\n \nInstall Time - less than 5 minutes. \n \n1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This \n \n option will load the KIDS patch onto your system.\n \n2. On the 'Kernel Installation & Distribution System' Menu (KIDS), select \n the 'Installation' menu.\n \n3. Use the 'Verify Checksum in Transport Global' option and verify that \n all routines have the correct checksums.\n \n4. On the KIDS menu, under the 'Installation' menu, use the following \n options: \nAll of the above changes have been reviewed by the VISTA Blood Bank\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n5. Use the 'Install Package(s)' option under the 'Installation' menu and \n select the package 'LR*5.2*309'.\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES// \n choose 'NO'.\n \nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE\n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//', disable the Anatomic Pathology [LRAP] option. \n \n \n \nINSTALLATION EXAMPLE: \n===================== \n \nExample #1 without data:\n======================== \ncontrol functions.\nSelect Installation Option: install Package(s)\nSelect INSTALL NAME: LR*5.2*309 Loaded from Distribution \n8/5/08@14:25:46\n => LR*5.2*309\n \nThis Distribution was loaded on Aug 05, 2008@14:25:46 with header of \n LR*5.2*309\n It consisted of the following Install(s):\n LR*5.2*309\nChecking Install for Package LR*5.2*309\n \nWill first run the Environment Check Routine, LR309\n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*309\n \n \nRISK ANALYSIS: Changes made by patch LR*5.2*309 have no effect on Blood\n \nWant KIDS to INHIBIT LOGONs during the install? NO// \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// \n \nEnter options you wish to mark as 'Out Of Order': LRAP\n 1 LRAP Anatomic pathology\n 2 LRAP ADD Add patient(s) to report print queue\n 3 LRAP ALERT Send an AP Alert\n 4 LRAP DELETE Delete report print queue\n 5 LRAP ESIG SWITCH Turn Electronic Signature On/Off\nBank software functionality, therefore RISK is none.\nPress <RETURN> to see more, '^' to exit this list, OR\nCHOOSE 1-5: 1 LRAP Anatomic pathology\n \nEnter options you wish to mark as 'Out Of Order': \n \nEnter protocols you wish to mark as 'Out Of Order': \n \nDelay Install (Minutes): (0-60): 0// \n \nEnter the Device you want to print the Install messages.\n \nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// ;;1000 UCX/TELNET\n \n \n Install Started for LR*5.2*309 : \n Aug 05, 2008@14:26:27\n \nBuild Distribution Date: Aug 01, 2008\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*309 does not\n \n Installing Routines:\n Aug 05, 2008@14:26:27\n \n Running Post-Install Routine: POST^LR309\n \n *** Post install started ***\n \nSearching for data in DESCRIPTION field (#20) in CYTOPATHOLOGY sub-file \n(#63.09) in LAB DATA file (#63).\n==========\nalter or modify any software design safeguards or safety critical \n \n \nLR*5.2*309 \n--------------------------------------------------------------------------\n Search finished\n \n No Data found in ^LR(D0,"CY",D1,"WP",0)\n \n *** Post install completed ***\n \nelements functions.\n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*309 Installed. \n Aug 05, 2008@14:26:27\n \n \n \n--------------------------------------------------------------------------\n +------------------------------------------------------------+\n 100% | 25 50 75 |\nComplete +------------------------------------------------------------+\n \n \nInstall Completed\n \nExample #2 with data:\n=====================\nPOTENTIAL IMPACT ON SITES: This patch contains changes to 0 routines\n \nSelect Installation Option: install Package(s)\nSelect INSTALL NAME: LR*5.2*309 Loaded from Distribution \n8/5/08@10:06:42\n => LR*5.2*309\n \nThis Distribution was loaded on Aug 05, 2008@10:06:42 with header of \n LR*5.2*309\n It consisted of the following Install(s):\n LR*5.2*309\nand 1 files identified in Veterans Health Administration (VHA) Directive\nChecking Install for Package LR*5.2*309\nWill first run the Environment Check Routine, LR309\n \n \n Sending install started alert to mail group G.LMI\n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*309\n \n2004-058, group B listing. The changes have no effect on Blood Bank\n \n \nWant KIDS to INHIBIT LOGONs during the install? NO// \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// \n \nEnter options you wish to mark as 'Out Of Order': LRAP\n 1 LRAP Anatomic pathology\n 2 LRAP ADD Add patient(s) to report print queue\n 3 LRAP ALERT Send an AP Alert\n 4 LRAP DELETE Delete report print queue\nfunctionality or medical device control functions. There is no adverse\n 5 LRAP ESIG SWITCH Turn Electronic Signature On/Off\nPress <RETURN> to see more, '^' to exit this list, OR\nCHOOSE 1-5: 1 LRAP Anatomic pathology\n \nEnter options you wish to mark as 'Out Of Order': \n \nEnter protocols you wish to mark as 'Out Of Order': \n \nDelay Install (Minutes): (0-60): 0// \n \npotential to sites.\nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// ;;1000 UCX/TELNET\n \n \n Install Started for LR*5.2*309 : \n Aug 05, 2008@10:07:55\n \n \nBuild Distribution Date: Aug 01, 2008\n \n Installing Routines:\n Aug 05, 2008@10:07:55\n \n Running Post-Install Routine: POST^LR309\n \n *** Post install started ***\n \nSearching for data in DESCRIPTION field (#20) in CYTOPATHOLOGY sub-file \nVALIDATION REQUIREMENTS BY OPTION: \n(#63.09) in LAB DATA file (#63).\n \n Search finished\n \n Data entries have been found in ^LR(D0,"CY",D1,"WP",0)\n \nThe data found is sent in a mail message to all users\nwho hold the security keys LRLIASON and LRAPSUPER. \nThe data will automatically be purged from the\n^XTMP("LR309", global in 180 days. \n \n \n \n \n \nLR*5.2*309 \n--------------------------------------------------------------------------\n \nData deleted from DESCRIPTION field (#20) in CYTOPATHOLOGY sub-file \n(#63.09) in LAB DATA file (#63).\n \n *** Post install completed ***\nThere are no Validation requirements or options to be validated\n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*309 Installed. \n Aug 05, 2008@10:07:56\n \nin this patch.\n \n--------------------------------------------------------------------------\n +------------------------------------------------------------+\n 100% | 25 50 75 |\nComplete +------------------------------------------------------------+\n \n \nInstall Completed\n \nRoutine Information:\n \n====================\n \n \nThe second line of each of these routines now looks like:\n ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 21\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \nRoutine Name: LR309\nMINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL \n Before: n/a After: B56461511 **309**\nRoutine Name: LRAUAW\n Before: B5818727 After: B5111264 **72,115,121,309**\n \nRoutine list of preceding patches: 121\nFUNCTIONS:\n \nThere are no Test Case Scenarios associated with this patch.\n \nDESCRIPTION: \nVISTA Laboratory Package patch LR*5.2*309 contains changes to \n============ \nThis patch removes one field, the DESCRIPTION field (#20), in the\nLAB DATA file (#63) CYTOPATHOLOGY sub-file (#63.09), and a reference to\nthis field in routine ^LRAUAW.\n \nAlthough it is highly unlikely that data exists in the DESCRIPTION \nfield (#20), the patch also checks for data that may have been entered in\nthe field. Any data that is found is moved to the ^XTMP("LR309")\nglobal and stored for 180 days before it is purged. If data is found,\nthe installation routine also generates and sends a mail message to the\nsoftware controlled by VHA DIRECTIVE 2004-058, titled VISTA \nholders of security keys LRLIASON and LRAPSUPER to be used as a source\ndocument to determine how the data should be handled if at all.\nThe message contains the LR*5.2*309 Data Report which lists the data \nfound, the accession number, the patient's name, social security number\nand gender.\n \nDATA DICTIONARY CHANGES: \n======================== \n The following is a list of the Data Dictionary entry in LAB DATA file \n(#63) that will be deleted by this patch:\nBLOOD BANK SOFTWARE. Changes include: \n \n63.09,20 DESCRIPTION WP;0 WORD-PROCESSING #63.91\n \n DESCRIPTION:\n Word processing field for description\n \n \nMODIFICATION OF THE LRAUAW ROUTINE:\n===================================\nPatch LR*5.2*309 also makes changes to the LRAUAW routine to remove a\n \nreference to the DESCRIPTION field (#20) of the CYTOPATHOLOGY sub-file\n(#63.09) in the LAB DATA file (#63). The change will be transparent to\nthe user.\n \nNEW SERVICE REQUEST (NSR): \n========================== \nN/A. \n \nASSOCIATED E3R: \n=============== \n File Field Action\nN/A. \n \nASSOCIATED NOIS: \n================ \nN/A. \n \nASSOCIATED REMEDY TICKETS: \n========================== \n HD0000000093288 \n \n \nTEST SITES: \n=========== \n Altoona, PA - small\n Wilmington, DE - medium\n Biloxi, MS - large\n \n \nSOFTWARE RETRIEVAL: \n==================== \n This patch is distributed by KIDS as a Packman message. \n\n\nThis patch is a VM general purpose lab patch that addresses 2 issues.\n \n 1. When printing an autopsy report through option "Entries by dates,\n patient and accession number", an <UNDEFINED> error occurs.\n \n 2. There are 3 indicators for DRAW TIMES related to antibiotics: PEAK,\n TROUGH, and RANDOM. The designator "RANDOM" does not appear on\n a report under the LABS tab in CPRS GUI, as do the designators \n "PEAK" and "TROUGH".\n\n
\nBLOOD BANK Clearance:\n LRBLPCSS\n Old call: D NEW^TIUPNAPI(.LRTIUPTR,DFN,DUZ,LRNTIME,LRTITLE,,,,DUZ)\n New call: \nD NEW^TIUPNAPI(.LRTIUPTR,DFN,DUZ,LRNTIME,LRTITLE,,,,DUZ,,1)\nwhere 1 is the new parameter.\n \nWhen the new parameter is set to 1 the following functionality is \nevoked:\n \na. Triggers the TIU API to abort creation and storage of the AP \nReport in TIU if the electronic signature fails. \n LRBLS\n \nb. An error message provides detailed information on the aborted \nstorage of the AP Report in TIU when an electronic signature fails. The \nerror message is:\n \n *** Report is being processed for storage in TIU. One moment please.\n*** \n \n \n *** Signature in TIU failed. ***\n \n \n \nPossible causes:\n \n1. Report contains 3 sequential characters matching those defined\nin the BLANK CHARACTER STRING field (#1.06), TIU PARAMETERS file \n(#8925.99)\nwhich are @@@.\n \nTo correct this situation use a data entry option to remove\nAll of the above changes have been reviewed by the VISTA Blood Bank \nthese characters from this report.\n \n2. There is some other TIU document setup problem.\n \nReport this situation to the Laboratory ADP Coordinator.\n \n \n *** Report storage in TIU failed. ***\n \n \nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE \n2). The patch updates routine: LREPI3 and LREPI5 to point to the correct\n ICD9 code for LEGIONNAIRES' DISEASE. Changed from 482.80 to 482.84\n \n3). API Updates:\n ------------ \n a. The ICD DIAGNOSIS file (#80) has unsupported fields: (#3) DIAGNOSIS\n and (#10) DESCRIPTION. The following APIs have been provided\n to retrieve these fields:\n $$ICDDX^ICDCODE and $$ICDD^ICDCODE.\n The Lab Service routines affected are as follows:\ncontrol functions.\n LR7OB63C, LR7OB63D, LR7OSAP1, LRAPCUM1, LRAPQAT1, LRAPT3, LRAUSICD,\n LRBEBA, LRBEBA2, LRBLJPP1, LRBLPC1, LREPI1A, LREPI3, LRSPRPT1,\n LRSPSICD and LRPXAPIU.\n \n b. The ICD OPERATION/PROCEDURE file (#80.1) has unsupported fields:\n (#4) OPERATION/PROCEDURE and (#10) DESCRIPTION. The following API\n has been provided to retrieve these fields:\n $$ICDOP^ICDCODE\n The Lab Service routines affected are as follows:\n LRBLPC1, LRBLJPP1 and LRAPQAT1.\n \n \n c. The CPT file (#81) has an unsupported field: (#2) SHORT NAME.\n The following APIs have been provided to retrieve the field:\n $$CPT^ICPTCOD and $$CPTD^ICPTCOD.\n The Lab Service routines affected are as follows:\n LRBEECPT, LRBLPCSS and LRBLS.\n \n \nAssociated E3R:\n===============\nRISK ANALYSIS: Changes made by patch LR*5.2*315 have limited effect on \nN/A\n \nAssociated NOIS / Remedy Ticket:\n================================\nHVH-0804-11491 / HD0000000070948\n \n Duplicates:\n UNY-0904-11549 / HD0000000071019\n MUS-1004-71347 / HD0000000071048\n N/A / HD0000000098477\nBlood Bank software functionality, therefore RISK is low.\n N/A / HD0000000226508\n N/A / HD0OOOOOO275681\n \nTest Sites:\n===========\nCanandaigua Health Care System (HCS)- Large/Integrated\nDurham VAMC- Large\nLexington VAMC - Medium\nWilmington VAMROC - Medium \n \n \n \nSoftware Retrieval\n==================\nAP Report Causes Unsigned CPRS Alert and New CPT APIs patch LR*5.2*315 \nsoftware is distributed by Packman.\n \nDocumentation Retrieval\n=======================\nVeterans Health Information Systems and Architecture (VistA) Laboratory\nAnatomic Pathology (AP) Report Causes Unsigned Computerized Patient Record\n=====================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*315 does not \nSystem (CPRS) Alert and New Current Procedural Terminology (CPT) \nApplication Programming Interface (APIs) Patch LR*5.2*315 User Guide is\navailable at the following Office of Information Field Offices (OIFOs)\nANONYMOUS.SOFTWARE directories:\n \nOI Field Office FTP Address Directory\n--------------- ----------- ---------\nALBANY ftp.fo-albany.domain.ext [ANONYMOUS.SOFTWARE]\nHINES ftp.fo-hines.domain.ext [ANONYMOUS.SOFTWARE]\nSALT LAKE CITY ftp.fo-slc.domain.ext [ANONYMOUS.SOFTWARE]\nalter or modify any software design safeguards or safety critical \n \n \nDocumentation Retrieval Formats\n===============================\nVistA Laboratory AP Report Causes Unsigned CPRS Alert and New CPT APIs\nPatch LR*5.2*315 User Guide files are exported in the following retrieval\nformats:\n \nFile Name Contents Retrieval Formats\n--------- -------- -----------------\nelements functions.\nLAB_52_315_UG.doc VistA Laboratory AP Report BINARY\n Causes Unsigned CPRS Alert\n and New CPT APIs Patch \n LR*5.2*315 User Guide \n \nLAB_52_315_UG.pdf VistA Laboratory AP Report BINARY\n Causes Unsigned CPRS Alert\n and New CPT APIs Patch \n LR*5.2*315 User Guide \n \n \n \nVistA Website Locations:\n========================\nVistA Laboratory AP Report Causes Unsigned CPRS Alert and New CPT APIs\nPatch LR*5.2*315 User Guide is accessible in MS Word (.DOC) format and\nPortable Document Format (.PDF) at the following VistA locations:\n \nLaboratory Version 5.2 Home Page\n--------------------------------\nhttp://vista.domain.ext/ClinicalSpecialties/lab/\nPOTENTIAL IMPACT ON SITES: This patch contains changes to 4 routines and \n \nVistA Documentation Library (VDL)\n---------------------------------\nwww.domain.ext/vdl/\n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system. You may wish to\ninstall it during non-peak hours. Installation will take less than 1 \nminute. It is recommended to disable the Anatomic Pathology [LRAP] option\n0 files identified in Veterans Health Administration (VHA) Directive \nat the "DISABLE Scheduled Options, Menu Options, and Protocols?" prompt.\n \n1. Use the INSTALL/CHECK MESSAGE option on the Packman Menu. \n \n2. From the Kernel Installation and Distribution System (KIDS) Menu, \n select the Installation menu. \n \n3. From the Installation menu, you may select to use the following \n options (when prompted for INSTALL NAME, enter LR*5.2*315): \n \n2004-058, group A listing.\n a. Backup a Transport Global \n b. Compare Transport Global to Current System\n c. Print Transport Global \n d. Verify Checksums in Transport Global\n \n4. Use the Install Package(s) option and select the package LR*5.2*315.\n \n5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//',\n respond NO.\n \n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//', Anatomic Pathology [LRAP] option.\n \n Note: Routine LR315 will be deleted after successful patch installation.\n \nInstallation Example:\n=====================\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*315 Loaded from Distribution \nVALIDATION REQUIREMENTS BY OPTION: \n10/18/08@16:48:47\n => LR*5.2*315\n \n This Distribution was loaded on Oct 18, 2008@16:48:47 with header of\n LR*5.2*315\n It consisted of the following Install(s):\n LR*5.2*315\n Checking Install for Package LR*5.2*315\n Will first run the Environment Check Routine, LR315\n \n---\n \n Sending install started alert to mail group G.LMI\n \n \n --- Environment Check is Ok ---\n \n \n Install Questions for LR*5.2*315\n \n \nVISTA Laboratory Package patch LR*5.2*315 contains changes to software \nOPTION: (EF-MS) Maximum surgical blood order edit [LRBLSMS]\n \n Want KIDS to INHIBIT LOGONs during the install? NO// \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//\n \n Enter options you wish to mark as 'Out Of Order': LRAP\n 1 LRAP Anatomic pathology\n 2 LRAP ADD Add patient(s) to report print queue\n 3 LRAP DELETE Delete report print queue\n 4 LRAP ESIG SWITCH Turn Electronic Signature On/Off\n 5 LRAP PRINT ALL ON QUEUE Print all reports on queue\n \n Press <RETURN> to see more, '^' to exit this list, OR\n CHOOSE 1-5: 1 LRAP Anatomic pathology\n \n Enter options you wish to mark as 'Out Of Order': \n \n Enter protocols you wish to mark as 'Out Of Order': \n \n Delay Install (Minutes): (0-60): 0// \n \n Enter the Device you want to print the Install messages.\n NORMAL:\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// ;;1000 UCX/TELNET\n \n \n Install Started for LR*5.2*315 : \n Oct 18, 2008@16:49:53\n \n Build Distribution Date: Oct 18, 2008\n \n \n Installing Routines:\n Oct 18, 2008@16:49:53\n \n Running Pre-Install Routine: PRE^LR315\n \n *** Pre install started ***\n \n \n \n 1. Enter a valid entry from the Current Procedure Terminology\nLR*5.2*315 \n \n -------------------------------------------------------------------\n \n *** Pre install completed ***\n \n \n Running Post-Install Routine: POST^LR315\n \n *** Post install started ***\n File (#81) at the "Select OPERATION" prompt.\n \n \n *** Post install completed ***\n \n \n Sending install completion alert to mail group G.LMI\n \n \n Updating Routine file...\n \n 2. Verify that the text displayed is the correct text for the\n Updating KIDS files...\n \n LR*5.2*315 Installed. \n Oct 18, 2008@16:49:53\n \n Install Message sent #87004\n--------------------------------------------------------------------------\n +------------------------------------------------------------+\n 100% | 25 50 75 |\nComplete +------------------------------------------------------------+\n procedure selected.\n \n \nInstall Completed\n 3. Press "Enter" at the "Selection OK ? YES//" prompt\n 4. Verify that the "Select BLOOD COMPONENT REQUEST:" prompt is \ncontrolled by VHA DIRECTIVE 2004-058, titled VISTA BLOOD BANK SOFTWARE. \ndisplayed.\n 5. Enter "^" at the "Select BLOOD COMPONENT REQUEST:" prompt and "Enter"\n at the "Select OPERATION:" prompt to exit.\n \n **EXPECTED OUTCOME:\n The correct text is displayed for the procedure selected.\n \n EXCEPTIONAL:\n N/A for coding changes made\n \nChanges include: \n BOUNDARY:\n This scenario applies to all sites.\n \n STRESS:\n Repeat this scenario for 3 different procedures.\n---\nOPTION: (UR-TX) Transfusion follow-up tests [LRBLTXA]\n \n NORMAL:\n \n Routines:\n 1. Enter a valid start date at the "Start with Date TODAY//" prompt.\n 2. Press "Enter" at the "Go to Date TODAY//" prompt.\n 4. Verify that the descriptive text listed for the ICD 9 codes is \naccurate.\n \n \n **EXPECTED OUTCOME:\n The correct text is displayed for the ICD 9 code displayed.\n \n EXCEPTIONAL:\n ---------\n N/A for coding changes made\n \n BOUNDARY:\n This scenario applies to all sites.\n \n STRESS:\n N/A.\n---\n \nMINIMAL TEST CASE SCENARIOS BY OPTION, INCLUSIVE OF ALL CONTROL FUNCTIONS:\n LRBLJPP1\nThere are no test case scenarios for this patch.\n \n \nDescription:\n============\n1). This patch corrects the following problem which can occur when an \nAnatomic Pathology (AP) report is released:\nPROBLEM (HVH-0804-11491/HD0000000070948): When an AP report is released \ncontaining 3 sequential characters defined in the BLANK CHARACTER STRING \nfield (#1.06), of the TIU PARAMETERS file (#8925.99), the Text \n LRBLPC1\nIntegration Utility (TIU) electronic signature fails without giving \nnotification to the user. The AP report is successfully created and \nstored in TIU, but is marked in TIU as an unsigned document, which in \nturn, may generate an alert in Computerized Patient Record System (CPRS).\n \nRESOLUTION: This patch adds a new parameter to the code that \ncalls the TIU API, NEW^TIUPNAPI. This TIU API is called at the time the \nAP report is released; it creates and stores the AP report in the TIU \nDOCUMENT file (#8925).\n \n\n
\n \nThis patch will modify routine LRPHLIST (collection label print)\nto allow the print job to be queued to a printer through TASKMAN.\n\n
\nThis patch is a VM general purpose lab patch that addresses 3 issues.\nIt corrects a problem with the inability to enter antibiotic \nconcentrations,\naddresses a problem in file #64.1 (Workload Data) whereby incorrect data\ngets stored in the file when the order date is different from the \ncollection\ndate, and also addresses a problem whereby the draw time designator of\nRANDOM is not displayed on the patient report.\n\n
\nThis patch is a VM general purpose lab patch that addresses 3 issues.\n \n 1. Turnaround time report for AP yields incorrect calculation of days\n sometimes when holiday occurs mid-week.\n \n 2. Alerts are being sent for patients from REFERRAL file (#67).\n \n 3. Modifying released pathology reports leads to incorrectly\n stored data.\n\n
\n \nThis patch is a VM general purpose lab patch that addresses 3 issues.\nIt corrects a problem with the inability to enter antibiotic \nconcentrations,\naddresses a problem with the WorkLoad Report whereby data from yearly\naccession areas is not picked up, and modifies a comment that is\nautomatically generated when a test is cancelled after a result has been\nentered.\n\n
\nThis patch is a VM general purpose lab patch that addresses 2 issues.\n The error also occurs when there is no RESULT NLT CODE on file\n and the user <returns> through this prompt.\n \n 1. The DSS Laboratory Extract gets a <SYNTAX> error when FileMan\n attempts to set an entry into the LAB DSS LAR EXTRACT FILE\n (# 64.036) when the entry has a text test result containing\n a semi-colon (;).\n \n 2. A <SUBSCRIPT> error occurs when a user enters an "^" at the\n RESULT NLT CODE prompt in option LR LOINC UNMAP/DELETE DEFAULT.\n\n
\nThis patch is a VM general purpose lab patch that addresses 2 issues.\n \n 1. The option MODIFY AN EXISTING DATA NAME allows for the modification\n of the input parameters for data elements that are not DATA NAMEs,\n leading to, in some cases, a corrupted database.\n \n 2. The option LRENTER (Enter/verify/modify data (manual)) sometimes\n prompts the user to select an accession area twice.\n\n
\nMISSING COLLECTION TYPE PROMPT\n\n
\nThis patch contains changes to the VBECS Blood Bank package. Refer to the \npatch listed in the Forum patch module for more details.\n\n
\nThis patch is a VM lab patch that addresses 2 LOINC mapping issues.\n confused and prompts one to "unmap" when one is in the "map" \n option.\n \n 1. When exiting the option "Map Lab Tests to LOINC Codes" after no\n matches are found related to an affirmative response to the\n prompt "Do you want to see possible LOINC code matches?", an\n <UNDEFINED> error results.\n \n 2. The option to map a default LOINC code and the option to unmap a\n default LOINC code use the same routines. Sometimes the code gets\n\n
\nThis patch addresses Patient Safety Issue PSPO #1384 which involves\ncritical lab test result alerts. When a lab test result is verified\nand that result lies outside the normal boundaries defined for the\ntest, alerts are generated that are sent to the physicians who are\nresponsible for the patient's care. In some cases these alerts are\nnot being generated.\n\n
\nThis patch is a VM lab patch that addresses a minor DD change, a change\n 2. The option descriptions for option LR WKLD REQUEST and option LR\n WKLD SERVICE are reversed.\n \n 3. During extraction of lab data for the Decision Support Software\n (DSS) it was discovered that some lab test names included a tilde\n character (~) or an exclamation point (!) which caused the record\n parser to incorrectly identify the end of the record and thus\n skip pertinent data.\nto 2 menu options, and a modification to the DSS extract for LAB.\n \n 1. The DELETE cross-reference code for field #10 (Cancelled By) of\n the TEST multiple of the SPECIMEN subfile (#69.03) of the LAB\n ORDERS file (#69) has faulty syntax which leads to a <SUBSCRIPT>\n error when a deletion of an entry in the CANCELLED BY field\n occurs.\n \n\n
\nBLOOD BANK STATEMENT\nBLOOD BANK STATEMENT\n 25 ORDER LABEL TESTS NEW\n 30 EXCLUDE URGENCY NEW\n 32 GREETING NEW\n 40 WELCOME TO NEW\n 42 YOUR HOST IS NEW\n 44 HOST TITLE NEW\n 45 SPACER LABEL PRINTER NEW\n 50 ATLERNATIVE LABEL ROUTINE NEW\n 51 NUMBER OF SCAN RE-TRY NEW\n 52 DELETE SAME DAY DUPLICATES NEW\n====================\n 54 BINGO BOARD DEVICE NEW\n \nHOWDY SPECIMEN TIMES BY UID FILE(#69.87): This file is used to capture and\nretain the specimen demographics.\n \nFILE # FIELD # FIELD NAME NEW/MODIFIED item(s)\n-------- --------- ----------------- --------------------\n69.87 .01 SPECIMEN UID NEW\n 2 INITIAL SCAN TIME NEW\n 4 TIME LABELS PRINTED NEW\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*405 does not \n 6 COLLECTOR NEW\n 8 COLLECTION TIME NEW\n 10 LAB ARRIVAL TIME NEW\n 12 RECEIVER NEW\n \n \nThe following is a list of menu options included in this patch:\n==============================================================\n \nOption Name Type New/Modified\ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \n----------- ---- ------------\nHOWDY BCE MAIN MENU menu NEW\nHOWDY MAIN MENU menu NEW\nLRHY BCE LABEL PRINT action NEW \nLRHY PATIENT CARD SCAN run routine NEW \nLRHY PATIENT CARD SCAN (BCE) run routine NEW \nLRHY PATIENT WAIT TIME run routine NEW \nLRHY PHLEBOTOMY LOG run routine NEW \nLRHY SCAN SPECIMENS INTO LAB action NEW \nLRHY SITE FILE EDIT run routine NEW \nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nLRHY TRACK COLLECTION run routine NEW\n \nSummary of new entries in the Options (File #19):\n================================================\n1. LRHY PATIENT CARD SCAN \nThis option initiates the Howdy process using the greeting from Howdy site\nfile & prints labels.\n \n2. LRHY PHLEBOTOMY LOG\nThis is the log used to track the collector's phlebotomy performance \n \ntimes.\n \n3. LRHY SCAN SPECIMENS INTO LAB\nThis option allows the Receiver to scan collected specimen labels to \ncapture Lab Receipt Time.\n \n4. LRHY TRACK COLLECTION \nThis option is used to display patient specimen collection demographics.\n \n5. LRHY PATIENT WAIT TIME\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*405 does not \nThis option displays how long a Patient waits to have a sample drawn.\n \n6. LRHY SITE FILE EDIT\nThis option enables the Keyholder to edit the Howdy site file.\n \n7. LRHY BCE PT CARD SCAN\nThis option enables Howdy to scan the Patient's VIC card when the Patient\narrives at the phlebotomy area.\n \n8. LRHY PRINT BCE PPID LABEL \nalter or modify any software design safeguards or safety critical \nBar Code Expansion (BCE) Compatible - This is the option the collector\nuses when verifying Positive Patient Identification (PPID) at time of\ncollection. Each collecting station will have a dedicated PC, scanner and\nbar code label printer. Howdy will recognize this person as the collector\nand date and time of collection. The collector will scan the patient's\nVIC card, armband or can type their SSN on their keyboard. The patient's\ndemographics appear on the screen with the current accessioned orders. \nThe collector then verifies each specimen in the presence of the patient\nto assure PPID. The labels then print and specimens are labeled\naccordingly.\nelements functions.\n \n9. HOWDY MAIN MENU\nThis option provides access to the traditional Howdy Main Menu. \n \n10. HOWDY BCE MAIN MENU\nThis option provides access to the Howdy BCE Main Menu.\n \nDocumentation Retrieval:\n=======================\nDocumentation describing the functionality introduced by this patch is \n \navailable in the [ANONYMOUS.SOFTWARE] directories at the following\nInternet addresses:\n \n Preferred or Specific Server Internet address\n ---------------------------- -------------------------\n First available ftp server download.vista.domain.ext <-- preferred\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n====================\nRISK ANALYSIS: Changes made by patch LR*5.2*405 have no effect on Blood \n Below is a list of the documentation files related to this patch and \n available via the FTP sites listed above.\n \n Document File Description File Name FTP Mode\n ------------------------------- ------------- --------------\n Howdy Computerized Login Process LR_52_405_UM.PDF binary\n User Manual \n Howdy Computerized Login Process LR_52_405_TM.PDF binary\n Technical Manual \n Howdy Computerized Login Process LR_52_405_IG.PDF binary\nBank software functionality, therefore RISK is none.\n Installation Guide\n Howdy Computerized Login Process LR_52_405_RN.PDF binary\n Release Notes\n \n After this patch is released, the updated manuals may also be retrieved \n from the Internet at http://www.domain.ext/vdl\n \n Test Sites:\n ==========\n To be determined.\n \n \n VISTA Software Application Requirements:\n =======================================\n Prior to installing VistA Howdy Computerized Phlebotomy Login \n Process, the following required software applications must be installed:\n \n Software Applications Versions:\n --------------------- --------\n Kernel 8.0\n VistA Laboratory 5.2\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n VA FileMan 22.0\n VA Mailman 7.1 or greater\n Kernel Toolkit 7.3\n \n INSTALLATION INSTRUCTIONS:\n =========================\n The install time for this patch should take less than 5 minutes. It is \n best if this patch is installed outside of normal working hours.\n \n NOTE: MailMan and Kernel patches must be current on the target system \nmade, no specific validation requirements exist as a result of \n to avoid problems loading and installing this patch.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of your PackMan menu to load \nthe KIDS distribution onto your system.\n \n 2. On the 'Kernel Installation & Distribution System' Menu (KIDS), \nselect the 'Installation' menu.\n \n From this menu you may choose the following options prior to \ninstalling this patch:\ninstallation of this patch.\n \n - Backup a Transport Global - this option creates a backup message \nof any routines exported with the patch. It does NOT backup any other\nchanges, such as data dictionaries or templates.\n \n - Compare Transport Global to Current System - this option allows \nyou to view all changes that are made when the patch is installed. It\ncompares all components of the patch (routines, DDs, templates, etc.).\n \n - Verify Checksums in Transport Global - this option allows you to \n \nensure the integrity of the routine that is in the transport global.\n \n 3. Use the 'Install Package(s)' option under the 'Installation' menu.\n \n When prompted for INSTALL NAME, enter: LR*5.2*405.\n \n Install Questions for LR*5.2*405:\n \n When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? NO//", respond NO. Responding "Yes" to the prompt for\nHowdy Computerized Phlebotomy Login Process (Howdy) is an automated \n rebuilding menu trees can significantly increase install time.\n \n When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//",\n respond NO.\n \n When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//", respond NO.\n \n 4. Verify that the installation of the patch completed correctly by \nusing the Kernel Installation & Distribution System [XPD MAIN]\nlaboratory check-in application used in Veterans Health Information \noptions:\n \n KIDS 'Utilities...' [XPD UTILITY] option 'Install File Print' [XPD\n PRINT INSTALL FILE] and selecting this patch (LR*5.2*405).\nSystems and Technology Architecture (VistA) Laboratory system to \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*405 does not\nprovide phlebotomy labs with the ability to:\n \n1. Read the Veteran Information Card (VIC) and instruct the patient \n to wait until called to the phlebotomy area.\n2. Search the VistA database for any phlebotomy orders pending on\n the patient.\n3. Process lab orders and print specimen labels.\n4. Verify that the correct lab specimens are drawn from the correct \n patient.\n5. Calculate and provide timeliness reports for Phlebotomy Lab \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA\n performance.\n6. Provide barcode technology for patient identification and \n positive specimen identification.\n7. Capture accurate collection and lab receipt times that allows the \n laboratory users to track outpatient lab samples from collection to \n verification.\n8. Assist in accomplishing the VA strategic plan, which specifies \n that 90% of laboratory specimens will be collected utilizing barcode \n technology.\n \nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\nThe Howdy bar code technology allows the lab personnel to use scanners to \nverify a veteran's identity and to track drawn sample(s) until the \nresults are entered into the VistA Laboratory system.\n \nHowdy addresses privacy issues. The scanning of the VIC feature eliminates\na hand-written log book for sign in, where the patient's name and SSN can\nbe viewed.\n \nThis patch addresses the following Remedy Ticket(s):\n===================================================\n \nN/A\n \nThis patch addresses the following Electronic Error & Enhancement Report \n(E3R):\n========================================================================\nE3R Entry #: 15882 20037 19545\n 19477 19221 19091\n 18805 1270 6247\n 8772 8807 9239\n 9496 9808 12301\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*405 does not\n 12981 13485 13638\n 13714 13865 14981\n 15124 15186 15249\n 15632 15715 16053\n 17038 17126 17923\n \nThis patch addresses the following Patient Safety Issues (PSIs):\n===============================================================\nN/A\n \nalter or modify any software design safeguards or safety critical\nData Dictionary Changes:\n=======================\nThis patch installs the following two new files:\n \nHOWDY SITE FILE (#69.86): This file is used to run the Howdy software\nand to reflect the site's business rules.\n \nFILE # FIELD # FIELD NAME NEW/MODIFIED item(s)\n-------- --------- ----------------- --------------------\n69.86 .01 NAME NEW\nelements functions.\n 2 LAB TEST (TO EXCLUDE) NEW\n 4 COLLECTION SAMPLE (TO EXCLUDE) NEW\n 6 SITE SPECIMEN (TO EXCLUDE) NEW\n 8 COLLECTION TYPES (TO EXCLUDE) NEW\n 10 PRINTERS NEW\n 11 ORDER LABEL ROUTINE NEW\n 12 FW ORDER LABELS NEW\n 16 EXCLUDE CLINICS NEW\n 18 CHECK FOR FUTURE ORDERS NEW\n 20 CHECK FOR PAST ORDERS NEW\n\n
\nThis patch is a VM patch that addresses 3 issues related to the\nwill create a situation whereby that provider will not be able to\nverify/electronically sign Anatomic Pathology reports. This happens\neven if the date is a future date.\n \n3. If more than one Special Studies is included in an Anatomic \nPathology report, the text of the subsequent Special Studies \nis not stored properly in the TIU document and thus doesn't display\nin CPRS.\nAnatomic Pathology area of the Lab package.\n \n1. When using option LRAPMOD (Print path modifications) an \n<UNDEFINED> error is encountered.\n \n \n2. Any date in the EXPIRATION DATE FIELD (#3) of the PERSON CLASS\nmultiple (#200.05) of the NEW PERSON file (#200) for a provider\n\n
\nThis patch is a VM patch that addresses 3 issues in the Lab package.\n3. <UNDEFINED> error occurs when trying to delete old user-defined\npatient/test lists. \n \n1. When trying to accession an order user gets the message "TEST \nNAME does not have an appropriate accession area. Order xxxxx IS \nNOT ACCESSIONED."\n \n2. The option GROUP DATA REVIEW (LRGVP) does not always show the\nproper report routing location.\n \n\n
\nThis patch is a VM patch that addresses a problem in the Lab package\nrelated to accessioning with in-common accession areas. When an\n"in-common" accession area is added to an existing accession area, it\nis possible that data in file #68 (ACCESSION) will be overlaid and 2\npatients will have the same accession number.\n\n
\nThis patch is a VM patch that addresses Patient Safety issue PSPO #2070.\nA lab test ordered through CPRS (Computerized Patient Record System) can\nbe placed on an order for the wrong patient in file #69(LAB ORDER ENTRY).\n\n
\n Description\n Computer System (VBECS). VBECS must be installed prior to installing \nInstall Questions for LR*5.2*382\n \n \nIncoming Mail Groups:\n \nEnter the Coordinator for Mail Group 'LRADT INTERFACE ADMIN': \n \nEnter TCP/IP address of LRADT LOGICAL LINK: 0.0.0.0\nEnter TCP Port of LRADT LOGICAL LINK: (1-9999999): 1234\n \n this patch.\nWant KIDS to INHIBIT LOGONs during the install? NO// \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? NO// \n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// UCX TELNET SESSION\n \n Install Started for LR*5.2*382 : \n \n May 27, 2008@23:06:32\n \nBuild Distribution Date: May 27, 2008\n \n Installing Routines:\n May 27, 2008@23:06:32\n \n Installing PACKAGE COMPONENTS: \n \n Installing MAIL GROUP\n Included in this patch is one routine, LRADT, that builds the ADT HL7 \n \nLR*5.2*382 \n--------------------------------------------------------------------------\n \n \n Installing HL LOGICAL LINK\n \n Installing HL7 APPLICATION PARAMETER\n \n Installing PROTOCOL\n messages, one HL LOGICAL LINK file (#870) entry named LRADT, two HL7 \n May 27, 2008@23:06:32\n \n Running Post-Install Routine: EN^LR382\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*382 Installed. \n May 27, 2008@23:06:33\n APPLICATION PARAMETER file (#771) entries named LRADT and LRADT TRIGGER, \n \n Install Message sent #10850169\n--------------------------------------------------------------------------\n \n +------------------------------------------------------------+\n 100% | 25 50 75 |\nComplete +------------------------------------------------------------+\n \n \nInstall Completed\n and the following PROTOCOL file (#101) entries:\n \n LRADT TRIGGER, LRADT-GMRA TRIGGER\n LRADT-A01 SERVER, LRADT-A01 CLIENT, VBECS-A01 CLIENT\n ===========\n LRADT-A02 SERVER, LRADT-A02 CLIENT, VBECS-A02 CLIENT\n LRADT-A03 SERVER, LRADT-A03 CLIENT, VBECS-A03 CLIENT\n LRADT-A04 SERVER, LRADT-A04 CLIENT, VBECS-A04 CLIENT\n LRADT-A08 SERVER, LRADT-A08 CLIENT \n LRADT-A11 SERVER, LRADT-A11 CLIENT, VBECS-A11 CLIENT\n LRADT-A12 SERVER, LRADT-A12 CLIENT, VBECS-A12 CLIENT\n LRADT-A13 SERVER, LRADT-A13 CLIENT, VBECS-A13 CLIENT\n \n The LRADT TRIGGER protocol is associated with existing VAFC ADT\n event protocols. The LRADT-GMRA TRIGGER protocol is associated with GMRA \n \n protocols triggered when patient allergies are signed or marked \n entered in error.\n \n Each TRIGGER protocol invokes routine LRADT to build the appropriate ADT \n message, which then transmits the message using the CLIENT/SERVER\n protocol pair associated with the ADT event.\n \n \n Test Sites\n ==========\n External Commercial Off the Shelf (COTS) applications and Vista \n \n \n Installation Instructions\n =========================\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n applications that interface with the Laboratory application may\n \n 3. From this menu, select the option Load a Distribution. When prompted\n for a file name, type in the directory where you have stored the host\n file, followed by the file name.\n \n 4. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter LR*5.2*382. \n \n a. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n additionally require patient information contained in ADT HL7\n is installed. It compares all components of the patch (routines,\n DDs, templates, etc.).\n b. Verify Checksums in Transport Global - this option will ensure\n the integrity of the routines that are in the transport global.\n \n 5. Use the Install Package(s) option and at the INSTALL NAME prompt,\n enter LR*5.2*382.\n \n 6. When prompted to enter a coordinator for the LRADT INTERFACE ADMIN\n mail group, enter the person or persons who will be responsible for\n messages. This patch contains the components necessary to transmit\n these mail groups.\n \n 7. At the prompt "TCP/IP address, enter the address of the system that\n will be receiving the ADT messages created by LAB ADT interface.\n \n 8. At the prompt "Port", enter the port associated with the TCP/IP \n address of the third party system that will be receiving the ADT \n messages created by the LAB ADT interface.\n \n 9. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//"\n patient information, within ADT HL7 messages, to two different receiving\n respond NO.\n \n 10. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//" respond NO.\n \n \n Example Installation:\n =====================\n \nSelect Installation Option: INSTall Package(s)\n systems: a third party COTS system and the Vista Blood Establishment \nSelect INSTALL NAME: LR*5.2*382 Loaded from Distribution \n5/27/08@23:06:14\n => PATCH 382 ;Created on May 27, 2008@11:25:30\n \nThis Distribution was loaded on May 27, 2008@23:06:14 with header of \n PATCH 382 MAY 275 ;Created on May 27, 2008@11:25:30\n It consisted of the following Install(s):\n LR*5.2*382\nChecking Install for Package LR*5.2*382\n \n\n
\nThis patch is being released in conjunction with VBEC*1*27. Install patch \nVBEC*1*27 to install the routines associated with this patch.\n\n
\nBLOOD BANK CLEARANCE\nelements functions.\n59 SHORTNAME SHORTNAME field (#81)\n \nThose local terms not included in the installed files should be formally \nrequested by notifying the National Laboratory Test Coordinator using the \nform provided on the VistA Laboratory Documentation Web Page. \nhttp://vista.domain.ext/clinicalspecialties/lab/\n \nForward your completed request form to the Exchange distribution group:\nVHAISD LAB NLT_LOINC\n \n \n===========================\nOPTIONS:\n \nNEW OPTION:\nPrint LOINC Code Status [LR LOINC STATUS PRINT]\nThis patch will provide an option to list LOINC deprecated terms. The \noption will also provide a list of currently mapped/linked laboratory \ntests that are linked to LOINC deprecated terms. This new option is \nlocated on the LOINC Mapping Utility Menu [LR LOINC UTILITY] menu. \n \nRISK ANALYSIS: Changes made by patch LR*5.2*334 have no effect on Blood \nMODIFIED OPTION:\nMap Lab Tests to LOINC Codes [LR LOINC MAP]\nThis option has been modified to permit the use of suffixed WKLD CODE \nin the NATIONAL VA LAB CODE (#64) field, of the LABORATORY TEST (#60) \nfile. This modified option is located on the LOINC Main Menu [LRLOINC] \nmenu.\n \n=========================\n \nDATA DICTIONARY MODIFICATIONS:\nBank software functionality, therefore RISK is none.\n \nThe screen has been removed from "NATIONAL VA LAB CODE" (#64) field, of \nthe "LABORATORY TEST" (#60) file. This will permit the use of suffixed \nWKLD CODE in the NATIONAL VA LAB CODE (#64) field, of the LABORATORY \nTEST(#60) file.\n \nA cross-reference has been created on the "STATUS" (#20) field of the \n"LAB LOINC" (#95.3) file.\n \nThe patch creates the following fields in the LAB LOINC (#95.3) file: \nVALIDATION REQUIREMENT BY OPTION: Because of the nature of the changes \nMASTER ENTRY FOR VUID field (#99.98), VUID field (#99.99), and EFFECTIVE \nDATE/TIME field multiple (#99.991) with an Effective DATE/TIME field \n(95.3099,.01) and STATUS field (95.3099,.02) which includes a date/time \nstamp and a status of 'active' or 'inactive' in the files being \nstandardized.\n \nThis patch also modifies data dictionaries to prevent future modification \nto these files at a local site.\n \nRoutine Summary:\nmade, no specific validation requirements exist as a result of \n================\n \nThe following is a list of the routine(s) included in this patch. The\n second line of each of these routine(s) will look like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \nRoutine Checksum checksum\ninstallation of this patch.\nName Before Patch After Patch Patch List\n ======= ============ =========== ==========\nLR334 N/A 4244176 334 (deleted by patch)\nLR334P N/A 3802010 334\nLR334PO N/A 9206370 334\nLR334POA N/A 2989047 334\nLR7OU5 13182116 12982551 127,201,272,334\nLRLNCC 2634007 2869430 232,280,334\nLRLNCST N/A 5628677 334\n \n====================== \n \nASSOCIATED NOIS:\n===============\nN/A\n \nASSOCIATED E3R:\n==============\nN/A\n \nTEST SITES:\n \n==========\nBiloxi VAMC, MS\nBoston HCS, MA\nEl Paso HCS, TX\nNorth Chicago VAMC, IL\nSalt Lake VAMC, UT\nSan Antonio VAMC, TX\nShreveport VAMC, LA\nTucson VAMC, AZ\n \nENHANCEMENTS:\n \nRequired Builds:\n==========================\nLR*5.2*272\nLR*5.2*302\nLR*5.2*232\nLR*5.2*280\nXU*8.0*299\nXT*7.3*93\nHDI*1.0*1\n====================\n \n \nInstallation Instructions: \n========================= \n \nThe patch LR*5.2*334 KIDS build file named LR_52_334.KID is stored in the \nASCII format.\n \nLAB_52_p334_IMPG.doc; VistA National Laboratory Test (NLT)/Logical \nObservation Identifier Naming Codes (LOINC) V2.14 Update Implementation \nGuide Patch LR*5.2*334 Version 5.2 - stored in a BINARY format.\nMap Lab Tests to LOINC Codes [LR LOINC MAP]\n \nLAB_52_p334_IMPG.pdf; VistA National Laboratory Test (NLT)/Logical \nObservation Identifier Naming Codes (LOINC) V2.14 Update Implementation \nGuide Patch LR*5.2*334 Version 5.2 - stored in a BINARY format.\n \nAll files can be obtained from the following Office of Information \nField Offices (OIFOs) ANONYMOUS SOFTWARE directories. All sites are \nencouraged to use the File Transfer Protocol (FTP) capability. Use the \nFTP address "download.vista.domain.ext" (without the quotes) to connect \nto the first available FTP server were the files are located.\nThis option has been modified to permit the use of suffixed WKLD CODE \nOIFO FTP Address Directory\nAlbany ftp.fo-albany.domain.ext anonymous.software \nHines ftp.fo-hines.domain.ext anonymous.software\nSalt Lake ftp.fo-slc.domain.ext anonymous.software\n \nAll users may remain on the system. Installation time is less than 30 \nminutes.\n \nNote: The patch should be installed during off peak hours.\n \nin the NATIONAL VA LAB CODE (#64) field, of the LABORATORY TEST (#60) \nNo laboratory background jobs need to be stopped. No options need to be \nplaced out of service.\n \nLABORATORY USERS MUST NOT ACCESSION SPECIMENS OR ENTER/VERIFY RESULTS\nDURING THE INSTALLATION because several reference files are being deleted \nand replaced with this patch.\n \n============================ \n \nFrom the Kernel Installation & Distribution System (KIDS) menu \nfile. This modified option is located on the LOINC Main Menu [LRLOINC] \n \n 1. Use the 'Load a Distribution' option to load the \n LR_52_334.KID file onto your system.\n 2. The patch has now been loaded into a Transport global\n on your system. You now need to use KIDS to install\n the Transport global.\n On the KIDS menu, under the 'Installation' menu, use \n the following options:\n Print Transport Global \n Compare Transport Global to Current System\nmenu\n Verify Checksums in Transport Global\n Backup a Transport Global\n 3. Users may remain on the system, but installation \n should be done at off peak hours.\n 4. Installation time is less than 30 minutes during off \n peak hours and less than 45 minutes during peak hours.\n 5. Installation of this patch requires no additional \n memory space.\n 6. From the 'Installation Menu' of the KIDS menu, run the \n option\n \n 'Install Package(s)' Select the package 'LR*5.2*334' \n and proceed with the install.\n 7. Want KIDS to Rebuild Menu Trees Upon Completion of Install? \n YES// respond 'YES'\n \n Note: Answering yes can significantly increase install time.\n \n 8. When prompted 'Want KIDS to INHIBIT LOGONS during the\n install? YES//' respond NO.\n 9. When prompted 'Want to DISABLE scheduled Options, Menu\nPrint LOINC Code Status [LR LOINC STATUS PRINT]\n Options, and Protocols? YES//' respond NO.\n \n================\nExample of install:\n \nSelect INSTALL NAME: LR*5.2*334\n Loaded from Distribution 10/13/05@14:50:38\n => NLT/LOINC v2.14 Update ;Created on Oct 13, 2005@13:46:31\n \nThis Distribution was loaded on Oct 13, 2005@14:50:38 with header of \nThis patch will provide an option to list LOINC deprecated terms. The \n NLT/LOINC v2.14 Update ;Created on Oct 13, 2005@13:46:31\n It consisted of the following Install(s):\n LR*5.2*334\nChecking Install for Package LR*5.2*334\nWill first run the Environment Check Routine, LR334\n \n --- Environment Check is Ok ---\n \n Sending install loaded alert to mail group G.LMI\n \noption will also provide a list of currently mapped/linked laboratory \nInstall Questions for LR*5.2*334\n \nIncoming Files:\n \n 60 LABORATORY TEST (Partial Definition)\nNote: You already have the 'LABORATORY TEST' File.\n \n 64 WKLD CODE\nNote: You already have the 'WKLD CODE' File.\n \n \ntests that are linked to LOINC deprecated terms. This new option is \n 64.061 LAB ELECTRONIC CODES (including data)\nNote: You already have the 'LAB ELECTRONIC CODES' File.\nI will OVERWRITE your data with mine.\n \n 64.062 LAB ELECTRONIC SUBTYPES (including data)\nNote: You already have the 'LAB ELECTRONIC SUBTYPES' File.\nI will OVERWRITE your data with mine.\n \n 64.2 WKLD SUFFIX CODES (including data)\nNote: You already have the 'WKLD SUFFIX CODES' File.\nlocated on the LOINC Mapping Utility Menu [LR LOINC UTILITY] menu. \nI will OVERWRITE your data with mine.\n \n 64.22 WKLD ITEM FOR COUNT (including data)\nNote: You already have the 'WKLD ITEM FOR COUNT' File.\nI will OVERWRITE your data with mine.\n \n 64.3 WKLD INSTRUMENT MANUFACTURER (including data)\nNote: You already have the 'WKLD INSTRUMENT MANUFACTURER' File.\nI will OVERWRITE your data with mine.\n \n \n 64.81 LAB NLT/CPT CODES (including data)\nNote: You already have the 'LAB NLT/CPT CODES' File.\nI will OVERWRITE your data with mine.\n \n 95.3 LAB LOINC (including data)\nNote: You already have the 'LAB LOINC' File.\nI will OVERWRITE your data with mine.\n \n 95.31 LAB LOINC COMPONENT (including data)\nNote: You already have the 'LAB LOINC COMPONENT' File.\n \nI will OVERWRITE your data with mine.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES//YES \n Note: Answering yes can significantly increase install time.\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nThis patch will support "Veterans Health Administration Unique \nEnter a '^' to abort the install.\n \nDEVICE: HOME// UCX/TELNET\n \n Install Started for LR*5.2*334 : \n Oct 13, 2005@15:07:27\n \nBuild Distribution Date: Oct 13, 2005\n \n Installing Routines:\nIdentifiers (VUID) standard. This patch will provide the necessary LAB \n Oct 13, 2005@15:07:27\n \n Running Pre-Install Routine: PRE^LR334\n \n . *** Preinstall completed ***\n \n Installing Data Dictionaries: \n Oct 13, 2005@15:07:27\n \n Installing Data: \nLOINC (#95.3) file data dictionary modifications in support of Data \n Oct 13, 2005@15:17:30\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n Oct 13, 2005@15:17:30\n \n Running Post-Install Routine: POST^LR334 . . . . . . . . . . . . . . . . \n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . .\nStandardization (DS) and the maintenance of those standards by Enterprise \n \n . Building List Of Added NLT CODEs\n .\n . Sending message to LMI Mail Group.\n .\n . List Of Added WKLD CODEs Complete\n..........................................................................\n.....\n \n Sending install completion alert to mail group G.LMI\nReference Terminology (ERT).\n \n . Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*334 Installed. \n Oct 13, 2005@15:20:24\n \n Install Message sent #XXXXX\n \n \n Call MENU rebuild\n \nStarting Menu Rebuild: Oct 13, 2005@15:20:26\n \nCollecting primary menus in the New Person file...\n \n . Primary menus found in the New Person file\n . ------------------------------------------\n \n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*334 does not \nLAB LOINC (#95.3) file protection has been significantly enhanced to \nDIUSER VA FileMan 1 06/04/92 10/05/05\n \nBuilding secondary menu trees....\n \nMerging.... done.\n \nMenu Rebuild Complete: Oct 13, 2005@15:20:40\n \n \nInstall Completed\nprevent field editing of the file. All fields will be populated by the DS \n \n \nLIM: Review description for LR*5.2*334 use KIDS:Utilities: Build File \nPrint\n \nPOST INSTALLATION INSTRUCTIONS:\n=============================\nReview installed LOINC codes to ensure that codes with the status of \nDeprecated (DEL) are not used in your current mapping of LOINC codes. In \nsome cases, deprecated LOINC codes [LAB LOINC (#95.3) file, MAP TO (#21) \nauthority, there are no fields in this file that are site editable.\nfield] will have the suggested replacement LOINC code populated.\n \nNote:\nIf your site is a HOST LEDI site, changing of any LOINC or NLT codes \nshould be coordinated with the collection site to ensure that both sites \nagree in LOINC and NLT mappings.\n \nNote:\n Please refer to the VistA NLT/LOINC V2.14 UPDATE Patch LR*5.2*334 \n Implementation Guide which provides the Laboratory Information \n \n Manager (LIM) a task-oriented approaches with step-by-step \n instructions and examples for mapping LOINC V2.14 codes.\nLAB LOINC (#95.3) file contents will be updated to the Regenstrief issued \nLOINC version 2.14.\n \nThis patch will update the WKLD CODE (#64) file and several laboratory \nstandardized files associated with National Laboratory Test (NLT) package \nand Logical Observation Identifier Naming Codes (LOINC) coding. (See list \ncontain any changes to the VISTA BLOOD BANK Software as defined by VHA \nbelow) \n \nFile # File Name Method\n \n64.061 LAB ELECTRONIC CODES Replaced\n64.062 LAB ELECTRONIC SUBTYPES Replaced\n64.2 WKLD SUFFIX CODES Replaced\n64.22 WKLD ITEM FOR COUNT Replaced\n64.3 WKLD INSTRUMENT MANUFACTURER Replaced\n64.81 LAB NLT/CPT CODES Replaced\nDIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n95.3 LAB LOINC Replaced\n95.31 LAB LOINC COMPONENT Replaced\n64 WKLD CODE Updated\n \n============================\n \nLOINC Copyright acknowledgement:\nLOINC was Copyrighted 1995, 1996, 1997, by Regenstrief Institute and the \nLogical Observation Identifier Names and Codes (LOINC) Committee. All \nrights reserved. LOINC is a trademark of the Regenstrief Institute.\n \nContact information:\nLOINC\nC/o Regenstrief Institute\n1001 West 10th Street, RHC-5\nIndianapolis, Indiana 46202 USA\n========================\n \nVistA Laboratory Package LAB LOINC (#95.3) file does not support all of \nthe fields contained in the LOINC database. Refer to the LOINC user's \nmanual for more field details. The following fields are imported and \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*334 does not \nsupported within VistA. The field "(#X)" refers to the field in the LAB \nLOINC (#95.3) file were the data is stored.\n \n# Loinc Term VistA name\n1 LOINC_NUM CODE field (#.01) + CHECK DIGIT field (#15)\n2 COMPONENT COMPONENT field (#1)+LAB LOINC COMPONENT file\n (95.31)\n3 PROPERTY PROPERTY field (#2)\n4 TIME_ASPCT TIME ASPECT field (#3)\n5 SYSTEM SYSTEM field (#4)\nalter or modify any software design safeguards or safety critical \n6 SCALE_TYP SCALE TYPE field (#5)\n7 METHOD_TYP METHOD TYPE field (#6)\n9 CLASS CLASSTYPE field (#41)\n10 SOURCE SOURCE field (#8)\n14 DT_LAST_CH DATE LAST CHANGED field (#22)\n15 CHNG_REAS CHANGE REASON field (#24)\n16 CHNG_TYPE CHANGE TYPE field (#23)\n19 STATUS STATUS field (#20)\n20 MAP_TO MAP TO field (#21)\n23 VA_CD VA CODE field (#34\n\n
\nRefer to National Patch Module.\n\n
\nThis patch is a VM patch that addresses 3 LOINC-related issues in the Lab\n when it should only print individual tests (atomic tests).\npackage.\n \n1. Option LR LOINC LOOKUP won't accept default.\n \n2. Option LR LOINC PRINT RESULT NLT prints MI (Microbiology) and BB \n (Blood Bank) tests when it should only print CH (Chemistry) tests.\n \n3. Option LR LOINC PRINT RESULT NLT prints profiles (cosmic tests)\n\n
\n \n2. Laboratory-related locking issues when doing accessioning\nThis patch is a VM patch that addresses 2 issues in the Lab package.\n \n \n \n1. In building the collection list, if an order fails to accession,\n sometimes subsequent orders fail to accession for the same reason\n even though the subsequent orders are ok.\n \n\n
\nINPUT TRANSFORM ERROR IS CAUSING DATA VERIFICATION ERROR.\n\n
\nThis patch is a VM patch that addresses 7 HOWDY-related issues in the Lab\n \n3. MI subscripted (Microbiology) tests will not accession in HOWDY\n if the MI test is on its own order and the site/specimen is not\n urine.\n \n4. The option LRHY PATIENT WAIT TIME reports inaccurate times.\n \n5. True accession number not appearing on LRHY PATIENT WAIT TIME\n report.\n \npackage.\n6. <SUBSCRIPT> error in option LRHY TRACK COLLECTION.\n \n7. Invalid link in HOWDY document.\n \n1. Option LRHY PPOC LABEL PRINT does not print an accession label\n when only one accession is selected from a group of 2 or more \n accessions.\n \n2. Option LRHY PPOC LABEL PRINT has sequence numbers, accession\n numbers, and collection samples running together on the screen.\n\n
\nLR*5.2*143 Patch Description:\nFile Installed:\nguidelines:\n \nEach sendout test should be coded with an appropriate specific WKLD Code\nprefix. If there is not an appropriate specific WKLD Code available,\nsubmit a request for WKLD Code addition(s) to the P&LMS Informatics Manage\nat the Dallas CIOFO. Forms are available in Patch LR*5.2*138 for making\nthese requests.\n \nEach sendout test should have a .8XXX suffix. All nationally recognized\nsendout laboratories have a suffix code numbers in the range of\nLAB DSS LAR EXTRACT ^LAR(64.036)\n.8000-.8999. Each sendout test should be assigned an .8XXX suffix\nindicating the laboratory that the specimen was sent for analysis. If the\nsame sendout test is sent to two or more laboratories, one method, is to\nhave a separate test for each sendout laboratory. Separate test for each\nsendout laboratory will allow different normal ranges and specimen\nrequirements and test cost. At the very least the sendout tests should be\ncoded to include the ordered test and the sendout laboratory whenever\npossible. In certain situations, sendout testing represents a significant\npercentage of total patient care cost. This cost requires better tracking\nto determine patient's overall treatment cost.\n \n \nThe Lab DSS API (routine LRCAPDSS) will be enhanced by patch LR*5.2*143 to\nextract all sendout tests based on the .8XXX suffix. It is not necessary\nto set the DSS Feeder Key to 'YES'.\n \nExample \nCEA done at VA Milwaukee\n86617.8694 CEA~VA MILWAUKEE\nCEA done at Smith Kline Beecham\n86617.8001 CEA~SMITH KLINE BEECHAM\n==================\n \nWith the new Lab DSS API enhancement, WKLD Codes conforming to any of the\nfollowing patterns will be extracted and passed to the DSS Workload API.\n \nWKLD CODE marked as Billable Procedure [LMIP Unit] (Austin Database)\nWKLD CODE with the suffix of .9999 (DSS ACC)\nWKLD CODE with the suffix of .8XXX (Sendout laboratory destination )\nWKLD CODE with the DSS Feeder Key (#14) field in the WKLD CODE file (#64)\nmarked YES\n \n \nNote:\nNational Laboratory Tests (NLT)and WKLD Codes can be considered to be the\nsame codes. NLT is the name of the VistA Package responsible for\ndistributing and updating WKLD Code files.\nInstallation Instructions:\nNOTE: This patch is invoked by patch ECX*2*18 and does not function\nindependently. There are no laboratory options associated with the patch.\n \n1. All users may remain on the system.\nDSS Clinical Data Extract API\n2. No options need be placed out of order.\n3. Install patch during non-peak hours.\n4. This patch has no effect on routine laboratory operations.\n5. The Auto-Instruments 'LAB' job(s) does not have to be stopped.\n6. Installation time of this patch is less than ten minutes.\n7. Journalling requires no special attention.\n \n===========================\nNOIS List \nNone\n==================\nDSS Program Office Request\n===========================\nTest Sites:\nAlpha Test Site: Long Beach\nBeta Test Sites : Portland, Murfreesboro\n \n----------------\nFunctionality:\n \nThe Laboratory Clinical Extraction API replaces the earlier clinical data\nROUTINE SUMMARY:\nextraction software that utilized the LABORATORY SITE file (#69) and the\nACCESSION file (#68). In an earlier guideline, DSS requested that the LIM\nadjust the purge date for these two files to retain 300 days of data. This\nrequest could not be done by numerous sites because of the lack of disk\nstorage capacity. Patch LR*5.2*143 will relieve the sites from retaining\n300 days of ORDERS and ACCESSION, and the normal PURGE OLD ORDERS AND\nACCESSION option date range can be restored.\n \nImplementation:\n \n \nThe DSS LAR Data (Patch LR*5.2*143 and the companion DSS patch ECX*2*18)\nextract utilizes the LAB DATA file (#63) and does not require the LAB\nORDERS file (#69) or the ACCESSION file (#68). Implementation of the DSS\nLAR API DOES require that the LIM link the 12 DSS LAR tests in the DSS LAB\nTEST file (#727.2) to all local corresponding tests in the LABORATORY\nTESTS file (#60). For DSS purposes, these corresponding laboratory tests\nmust be linked to the WKLD CODE file and must be individually orderable\n(atomic) tests. The link between LABORATORY TESTS file and the WKLD CODE\nfile is accomplished by assigning a WKLD CODE. The NATIONAL LABORATORY\nTEST field (#64) of the LABORATORY TESTS file (#60) provides this linkage.\nRoutine Name Before Patch After Patch Patch List\nThe NATIONAL LABORATORY TEST field is not used by LMIP data capture\nsoftware and will not effect LMIP counts. Patch LR*5.2*127 provided a\nmenu, "National Laboratory Test" [LR70 60-64], to link the LABORATORY\nTESTS file to the WKLD CODE file. \n \nNOTE: When linking the DSS LAR tests to local laboratory tests, only\natomic Laboratory Tests are selectable. Panel tests are NOT permitted to\nbe linked to any DSS survey test.\n \nThe DSS LAR extract also requires the LIM to identify all specimens that\nLRCAPDAR NA 5854094 143\nare derived from blood or urine, i.e., plasma, serum, clean catch. The LAB\nDSS LAR API will use these specimens to screen patient's results in the\nLAB DATA file and extract information for the 12 DSS tests.\n \nThe local DSS Coordinator will seek the LIM's assistance to identify tests\nand specimens. This should require less than 30 minutes to complete. The\nLIM is not required to actually initiate the data extraction. This will be\ndone by the local DSS Coordinator.\n \nThe LIM SHOULD coordinate the purging/archiving of the LAB DATA and the\nLRCAPDSS 5467821 5610986 127,143\nWKLD DATA files with the DSS Coordinator.\n \nThe data for the DSS LAR extract will be stored during processing in a new\nfile LAB DSS LAR (#64.036) and the data is stored in the global\n^LAR(64.036). This global will be purged by the calling DSS option when\nthe data has been transferred to the DSS laboratory clinical database.\nNormally this file will be empty. The design and functionality are the\nsame used by the WKLD LOG file (#64.03) for the DSS LAB extract. Neither\nthe LIM nor the Laboratory Package is responsible for purging data from\nthe WKLD LOG file (#64.03) or the LAB DSS LAR file (#64.036).\n==================\n \n \n------------------------------------------------------------\nLaboratory Management Index Program (LMIP) and DSS sendout tests setup and\nreferral lab identification guidelines:\n \nLMIP and DSS are reviewing data collected for laboratory sendout testing.\nThe collected data indicates that a consistent nation wide coding method\nfor capturing sendout tests is not being used. Each site should review\nthe WKLD Codes for sendout tests to assure that it follows these\n\n
\nThis patch is a VM patch that replaces a direct read of file #80 (ICD\nDiagnosis) with a call to a standard API ($$ICDDX^ICDCODE) in the form\nLREPI9.\n\n
\nThis is general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues related to screening for file #44 (Hospital\nLocation) and an accessioning issue.\n\n
\nThe following Lab changes or enhancements are included in this build:\n \n \n 1) CPRS API for Lab to call when a test is modified\n 2) Changes to identify File 60 changes that impact CPRS Quick Orders\n 3) National Lab Release: Hospital Location Change Management Tool\n 4) National Lab Release: Lab Test File 60 Audit Tool\n 5) National Lab Release: Inactivation of Collection Samples File Entries\n 6) National Lab Release: Inactivation of Topography File Entries\n 7) National Lab Release: Lapsed Orders\n\n
\nThis patch addresses the following issue(s):\n1. When printing a CAPTIONED template report in VA FileMan with the \nprinting of computed fields turned on for the ACCESSION (#68) file all of\nthe values printed for the HOSPITAL ID (#.09) computed field will be the\nsame. It will print a different value for each different AREA (#.01) and\nuse that value for all patients with accessions in that AREA (#.01)\n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues with the Howdy software relating to exclusionary\nfunctionality and also issues with the Howdy Wait Time\nreport and the Howdy Track Collection report.\n\n
\nThis patch is a VM patch that addresses issues in the lab package\nrelated to the VHIC 4.0 card.\n\n
\nThis patch is a VM patch that addresses 3 issues in the Lab package.\n \n3. Autopsy reports not viewable in CPRS.\n \n1. Option LRCENLKUP (Review By Order Number) gives misleading\n information when 1 sample of a multi-sample order is not\n collected.\n \n2. The option LRAPFICH (Print final path reports by accession number)\n prints the wrong year on the SNOMED CODE LISTING which is printed\n at the end of the pathology report for some AP accessions.\n\n
\nLab Version 5.2 Patch 433 - Anatomical Pathology Image Framework\nLRUDEL new value = 25303229\n \n \nRoutines:\nLR7OB63D new value = 29564352\nLRAPED new value = 33912945\nLRAPEDC new value = 5938079\nLRAPLG1 new value = 169348471\nLRAPRES new value = 188361634\n\n
\nThis patch will resolve the following issues in the Laboratory package:\n \n-Lab test accessioned without appropriate accession area\n-<SUBSCRIPT> error when using Enter/verify data (auto instrument) option\n-<UNDEFINED> error when editing Autopsy Acc #\n-LOINC code not appearing in panel tests\n\n
\nThis patch is a VM patch that addresses 2 issues in the Lab package.\n \n1. Incomplete test definition leads to "ghost" tests showing up in\n CPRS (Computerized Patient Record System).\n \n2. Panel tests sometimes get wrong urgency stored in file\n #68 (ACCESSION) when ordered with an atomic test with a higher\n urgency than the panel test.\n\n
\nThis patch is a VM patch that addresses 3 issues in the Lab package:\n \n1. Some data in file 69 is overlaid (wiped out) during\n accessioning.\n \n2. A DC'ed test (discontinued) was accessioned.\n \n3. Some panel tests not going to PCE.\n\n
\n1. Cannot add NHCU station number to Associated Division in File #68\n \n2. AP Edit Log-In option handles patient location edit incorrect\n\n
\n \nThis patch will modify routine LRPHLIST (collection label print)\nto allow the print job to be queued to a printer through TASKMAN.\n\n
\nThis patch is a VM patch that addresses 3 issues in the Lab package.\n \n1. Execute code does not perform correctly when a lab test is added \n to a previously verified accession.\n \n2. Convert delta checks to new format.\n \n3. <STORE> error when array fills up in micro\n\n
\nThis patch is a VM patch that addresses 3 issues in the Lab package:\n \n1. Semi-colon in lab test name prevents results entry.\n \n2. Confusing times in phlebotomy log.\n \n3. No warnings when panel test can't be accessioned.\n\n
\nThis patch is a VM patch that addresses 5 issues in the Lab package:\n \n4. Howdy accessioning sometimes generates an <UNDEFINED> error.\n \n5. Accession labels sometimes don't print in Howdy.\n \n1. Properly defined tests on an order not accessioning when one\n test is not properly defined.\n \n2. Improperly defined test causes subsequent tests/orders to not\n be accessioned.\n \n3. No warnings when panel test can't be accessioned.\n\n
\nThis patch is a VM patch that addresses 2 issues in the Lab package.\n \n1. Results can be entered on a test that is being cancelled.\n \n2. Problems with a date/time stamp in LRUMDP.\n\n
\n Patch LR*5.2*171 is a complete replacement for patch LR*5.2*140.\n reverse video. The control characters caused erratic \n printing in which the printer had to be powered off \n and on to clear the problem.\n \n 2. The problem of Incorrectly reported as comments not \n stored when the combined text strings are greater than 68\n characters has been resolved. In addition a date/time stamp\n and DUZ ID of the person making the change has been added \n to each incorrectly reported as comment.\n \n If you have not already installed Patch LR*5.2*140, do not install it.\n 3. Data names in the LAB DATA file (#63) have been limited to 50 \n characters.\n \n 4. The option Review Data Names [LR REVIEW DATA NAMES] will\n permit the user to review the data base for entries > 50\n characters.\n \n \n Reference NOIS: KAN-0395-40200\n MAN-O694-10052\n \n \n E3R E3R #9370\n \n \n Test Site(s): Muskogee, OK\n Asheville, NC\n Lexington, KY\n Loma Linda, CA\n \n This patch corrects these issues and also the following issues.\n Patch LR*5.2*140 corrected the following issues:\n \n 1. When using the Enter/Verify/Modify data (manual) [LRENTER] option to\n edit more than one result on a verified accession, an undefined\n variable DIE occurred.\n \n 2. When using the Enter/Verify/Modify data (manual) [LRENTER]\n to edit a result,the user is allowed to edit the results\n without entering their initials.\n \n \n \n Reference NOIS: NYN-0797-10830\n MAN-0797-10794\n \n \n Test Site(s): Manchester, NH\n New York, NY\n Durham, NC\n \n Installation:\n \n 1. The problem of erratic printing from the Group data \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n review (verified & EM) [LRGVP] option has been resolved. \n 3. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Install Package(s) 'LR*5.2*171'\n\n 4. Assign the option Review Data Names [LR REVIEW DATA NAMES] to\n appropriate lab person(s).\n \n 5. Remove the Environment Check Routine, LR171, from your system.\n \n \n Tests that were STAT or had critical results are \n\n\n displayed with control characters that produce the\n\n
\nThe patch addresses three (3) issues:\nthe verification of results marked as Not Performed.\n NOTE: Kernel patches must be current on the target system to avoid\n problems loading and/or installing this patch.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n \n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify\n that all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nAssociated NSR(s):\n \n To preserve a copy of the routines exported in this patch prior to \n installation, you should use the 'Backup a Transport Global' option \n at this time. You may also compare the routines in your production\n account to the routines in the patch by using the 'Compare a\n Transport Global to Current System' option.\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*438'.\n \n------------------\n If prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//,\n choose 'NO'.\n \n If prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\nN/A\n \nAssociated Remedy ticket(s):\n==========================\n1. INC000000500271 - MRSA testing on death\n2. INC000000069164 - LRGEN missing results\n \n- INC000000069285 (d)\n- INC000000069419 (d)\n- INC000000180798 (d)\n- INC000000069205 (d)\n3. INC000000937699 - Group Verify ignoring NP\n \nAssociated NSR(s):\n==================\nN/A\n \n1. Users report being unable to perform MRSA testing on deceased \nParticipating Test Sites:\n=========================\nTBD\n \nRemedy Overview:\n================\n \n1. INC000000500271 - MRSA Testing on Death\n \nProblem:\npatients but they are allowed to proceed through the accessioning process \n--------\nLaboratory staff indicates that they are not able to perform MRSA testing \non patients who are deceased. The application will not allow them to \naccession specimens or enter results for the MRSA test on deceased \npatients. Further, the user is allowed to progress through the \naccessioning session without an early warning that an order has been \ncanceled.\n \nResolution:\n-----------\nwithout an early warning that the test has been cancelled.\nTo avoid having MRSA tests cancelled at either patient death or \ndischarge, the desired test should be added as an Exempt Orderable Item \nfor the Death and/or Discharge event in the Delayed Orders/Auto-DC Set-up \nfunction.\n \nAdditionally, the routine LROE is modified to provide clear, early \nfeedback to the user that a test has been cancelled and will not be \naccessioned.\n \n2. INC000000069164 - LRGEN Missing Results\n2. LRGEN skips rows of results when the SITE/SPECIMEN prompt is \n \nProblem:\n--------\nThe defect occurs when using the LRGEN option (General report for \nselected tests) and when there are more than six (6) analytes on the \nselected tests. When the SITE/SPECIMEN prompt is answered with the \ndefault (ANY), the application only displays the first set of headings \nand results - that is: it only properly displays the first six results \nand skips the remaining results. This typically occurs on the results \nfor the last date of service. Though no results are displayed, \nanswered with the default (ANY) and it frequently displays/prints \nunnecessary headers are displayed or printed.\n \nResolution:\n-----------\nMultiple modifications and the addition of a function to routine LRGEN1, \ncorrect the missing results and unnecessary header issues.\n \n3. INC000000937699 - Group Verify Ignoring NP\n \nProblem:\nunnecessary headers.\n--------\nWhen Group Verify (GA) is used to verify results for a Work Load Area \nthat contains accessions that have tests that have been marked as Not \nPerformed on a prior date, the option can erroneously verify results that \nmay have been entered for the accession.\n \nResolution:\n-----------\nA modification to routine LRGV2 prevents the verification of any results \nthat may be associated with Not Performed test(s).\n3. Under certain circumstances, the Group Verify (GA) option allows \n \nComponents:\n===========\nN/A\n \nInstallation Instructions:\n==========================\n The install time for this patch is less than 2 minutes. This patch can\n be installed when Laboratory users are on the system.\n \n\n
\nThis patch is a VM patch that addresses 3 issues in the Lab package:\n \n1. Time ignored in searching date/time period.\n \n2. Units can be wrong in Search options.\n \n3. EGRF issue related to patient sex.\n\n
\nThis patch is a VM patch that addresses 2 issues related to CPT coding\n(Current Procedural Terminology) in the Laboratory package:\n \n1. Problems with ES Display List selections.\n \n2. Active CPT codes in file 64 are rejected as inactive.\n\n
\nThe patch addresses four (4) issues:\nun-queued output to P-Message, a Cache NOT OPEN error occurs.\n \n1. Clinical Reminder programs are referencing an incorrect subfield \nwhen retrieving a lab test pointer.\n2. When printing Future Labels, a Unique Identifier (UID) for an\nunrelated order can occasionally print on the label.\n3. In certain circumstances, lab results are not transmitted to the \nHealth Data Repository (HDR).\n4. When the Infection Control Survey Report is run specifying \n\n
\nThe patch addresses three (3) issues:\n1. Under certain conditions, the Anatomic Pathology option LRAPKILL\n (Delete accession #, anat path) gives the user ambiguous feedback\n about whether the delete of the accession was successful.\n2. The ORDERED TESTS BY PHY option misses AP and Howdy tests when an\n Accessioning Division is specified.\n3. Orders generated in CPRS and rejected in VBECS can be accessioned\n in VistA Lab.\n\n
\nThis patch is a VM patch that addresses 2 issues in the Lab package.\n \n1. Lab results search routine expands start/end search times.\n \n2. QC labels print with accession labels.\n\n
\nThis patch addresses four (4) issues:\n laboratory, and ordering provider are displaying in CPRS Laboratory\n progress notes for a patient's ordered test even though results are not\n verified for that test.\n \n4. Multiple updates to Microbiology preliminary comments sent by the \n Laboratory Electronic Data Interchange (LEDI) host site are not stored\n by the LEDI collecting site in the patient's record if the STORE\n DUPLICATE COMMENTS (#2.2) sub-field of the PROFILE (#50) field in the\n LOAD/WORKLIST (#68.2) file is set to "YES".\n \n1. The shipping manifest identifier is not shown on the Incomplete Status \n List (LRWRKINC) when printing the extended display.\n \n2. The test status may not be correctly reflected on the Incomplete \n Status List (LRWRKINC).\n \n3. Information such as report release date and time, performing \n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues with the Howdy software relating to exclusionary\nfunctionality for clinics, deleting of same day duplicate\ntests and some other minor Howdy issues.\n\n
\n Printer does not set-up properly when running cume reports manually.\n Adding LRPARAM to LRAC resolves this problem.\n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues with the collection times on the order report, CPT\ncode entry in AP, and the SNOMED extract.\n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues with accessioned lab tests marked as uncollected,\nand with accessioning creating erroneous nodes in the Laboratory\nOrder Entry file (#69).\n\n
\nAssociated Patches:(v)LR*5.2*446 <<= must be installed BEFORE `LR*5.2*458'\n===========\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nFile Name Contents Retrieval Format\n------------------ -------------------- ----------------\nLAB_AUTORELEASE_1_0.KID Host File containing ASCII\n KIDS software distribution\n \nThe VistA Documentation Library (VDL) web site will also contain \n \nThe build for this patch is distributed as part of a multi-package build \nLR_52_458_LA_52_88 Release Notes Binary\n for LR*5.2*458 and LA*5.2*88\n \nLab AutoRelease 1.0 User Guide Binary\n \nLab AutoRelease 1.0 Technical Manual Binary\n \nLab UI HL V1.6 Upgrade Installation Binary\n and User Guide LA*5.2*66\n \nthat contains LR*5.2*458 and LA*5.2*88 and contains functionality to \nLab UI HL V1.6 Upgrade Interface Binary\n Specifications Document \n \nThis website is usually updated within 1-3 days of the patch release date.\nThe VDL web address for Laboratory Universal Interface user documentation\nis: http://www.domain.ext/vdl/application.asp?appid=120\n \nInstallation Instructions\n=========================\n \nenable Auto Verification and Auto Release of normal lab results. \nThis patch, LR*5.2*458, is part of a combined build for Autoverification \nEnhancement patch. This patch may be loaded with users on the system. \nYou may want to install it during non-peak hours. Installation will take \nless than 10 minutes.\n \nRefer to the LR_52_458_LA_52_88 Release Notes referenced above for \ncomplete instructions on install and post installation configuration.\n \n1. DOWNLOAD HOST KIDS FILE\n ----------------------\nInitially developed at the Kansas City VAMC, this new process involves \n Download the KIDS file LAB_AUTORELEASE_1_0.KID from the \n ANONYMOUS.SOFTWARE directory of Albany, Hines, or the Salt Lake\n OIFO to the appropriate directory on your system.\n \n2. LOAD DISTRIBUTION\n -----------------\n Use the 'LOAD A DISTRIBUTION' option on the KIDS\n INSTALLATION menu, and enter: the directory onto which you\n have downloaded the host file, followed by\n LAB_AUTORELEASE_1_0.KID, the host file name. \nautomatic review and release of test results based on lab-established set \n \n3. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu [XPD\n MAIN]:\n Edits and Distribution ...\n Utilities ...\n Installation ...\n \n Select Kernel Installation & Distribution System Option:\nof boundaries, also referred as rules, rule sets, and algorithms. Lab \n INStallation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\nresults that are in a "normal" range, as pre-determined by the \n4. Select Installation Option:\n --------------------------\n \n a. Use the Load a Distribution and select Host File:\n LAB_AUTORELEASE_1_0.KID\n \n NOTE: The following are OPTIONAL - (When prompted for the INSTALL\n NAME, enter LA*5.2*88):\n \n b. Backup a Transport Global - This option will create a backup \nlaboratory, will transmit directly from the middleware to VistA lab files \n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n c. Compare Transport Global to Current System - This option will \n allow you to view all changes that will be made when this patch is\n installed. It compares all components of this patch m (routines,\n DD's, templates, etc.).\n d. Verify Checksums in Transport Global - This option will allow you\n to ensure the integrity of the routines that are in the transport\n global.\n e. Print Transport Global\nand on to Computerized Patient Record System (CPRS) without the \n \n5. Select Installation Option: Install Package(s) **This is the step \n to start the installation of this KIDS patch:\n --------------------------\n **This is the step to start the installation of this KIDS patch:\n a. Choose the Install Package(s) option to start the patch install.\n b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n YES//' answer NO\n c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? YES//' answer NO.\n \nintermediate step of requiring a lab technologist to manually review and \n \n \nRoutine Information:\n====================\n \n \nThe second line of each of these routines now looks like:\n;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994;Build 10\n \nThe checksums below are new checksums, and can be checked with \nsign off on these normal lab results. This process will eliminate the \nCHECK1^XTSUMBLD.\n \nRoutine Name: LR458\n Before: n/a After: B3643881 **458** DELETED AFTER INSTALL\nRoutine Name: LRDIQ\n Before: B5636912 After: B6385366 **86,153,263,290,458**\nRoutine Name: LRGP2\n Before: B20236690 After: B21346835 **153,221,263,290,350,446,458**\nRoutine Name: LRLISTPS\n Before: n/a After: B17691343 **458**\nneed for a qualified technologist to manually approve all "normal" \nRoutine Name: LRNIGHT\n Before: B6404812 After: B7575682 **291,350,458** \nRoutine Name: LRVER5\n Before: B147369024 After: B148324560 **42,153,283,286,350,458**\nRoutine Name: LRVR3\n Before: B71492279 After: B108418700 **42,121,153,286,291,350,458**\nRoutine Name: LRVRAR\n Before: n/a After: B69670046 **458**\nRoutine Name: LRVRARU\n Before: n/a After: B32878283 **458**\nresults before those results are filed in VistA Lab files and available \n \nRoutine list of preceding patches: 446\nfor clinicians to view in CPRS. \n \nEach VAMC site will determine which instruments will use this \nfunctionality as it can set up on an instrument by instrument basis. \nEssentially VistA Lab instruments are set up as either being available \nfor auto verification or not available for auto verification. If an \nSubject: LABORATORY AUTO VERICATION & AUTO RELEASE\ninstrument is set up for auto verification, then a lab result passing the \nrule set will be filed by the middleware in VistA lab files and available \nin CPRS and a lab result that cannot pass the rule set will be held in \nthe middleware system for review by a lab technologist. \n \nIn support of this auto verification and auto release functionality, this \npatch will add two new application proxy users. LRLAB AUTO RELEASE is \nused to indicate that the results in VistA Lab were released by an \nautomated Lab process without human interventions. LRLAB, AUTO VERIFY is \nused to indicate that the results were "approved" by an automated process \n \nusing a rules based system.\n \n--------------------------------------------------------------------------\n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\nCategory: ROUTINE\n------------------ ------------------- --------------------\nLOAD/WORK LIST (#68.2) PROFILE (#68.23), AUTO RELEASE (#2.4) New\n \nParameter Definitions Associated:\n \nParameter Definition Name New/Modified/Deleted\n------------------------- --------------------\nLR WORKLIST DATA CLEANUP New\n \nParameter Template New/Modified/Deleted\n ENHANCEMENT\n------------------------- --------------------\nLR PKG Modified\n \nInput Templates Associated:\n \nInput Template New/Modified/Deleted\n---------------------------------- --------------------\nLRLLDFT New\n \nOptions Associated:\n DATA DICTIONARY\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nSummary List (Patient) [LRLISTPS] Routine New\n \n \nNew Service Requests (NSRs):\n==============================\nNSR# 20131009: Employ laboratory autoverification in the Veterans Health \nAdministration. \n \n \nTest Sites:\n===========\nKansas City VAMC (Alpha)\nTucson (Beta)\nTampa (Beta)\nIowa City (Beta)\nFresno (Beta)\n \n \nDescription:\nSoftware and Documentation Retrieval Information\n ==============================\n VistA Laboratory patch LR*5.2*458 software is distributed by Host File, \nalong with LA*5.2*88. Software is available on the ANONYMOUS.SOFTWARE \ndirectory at one of the following Office of Information (OI) Field \nOffices. The preferred method is to retrieve the file using Secure File\nTransfer Protocol (SFTP) from: download.vista.domain.ext, which transmits\nfiles from the first available FTP server. Sites may also select to retrieve\ndocumentation directly from a specific server as follows: \n Albany ftp.fo-albany.domain.ext\n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues with Howdy:\n \n1. INC000001085378 - Draw time: 0\n2. INC000001056020 - Processed tests showing as "active"\n3. I7997705FY16 - Tests accessioned from excluded locations\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses\nissues with an incomplete audit log-in and with batch result\nentry of microbiology results:\n \n1. I8246369FY16 - Incomplete audit log-in\n2. I6575449FY16 - <UNDEFINED> error in micro results entry (batch) \n\n
\nPlease see forum for a complete description of patch LR*5.2*465\n\n
\nNov 23, 2016 - V14 - The following defect was corrected by a modification \n \n \nRISK ANALYSIS: Changes made by patch LR*5.2*462 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nmade, no specific validation requirements exist as a result of\ninstallation of this patch.\n \n \n \nOct 5, 2016 - V12 - This release enhances the "Delete accession #, anat\nPatch Components:\n-----------------\n \n \nFiles & Fields Associated:\n \n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nLABORATORY TEST CPRS SCREEN New\npath" option to update CPRS status to discontinued.\n (#60) (#21661)\nLABORATORY SITE CPRS AP DIALOG ON New\n (#69.9) (#21661)\nLAB ORDER ENTRY SUBSCRIPT New\n (#69) (#21661.71)\n CPRS AP SCREEN New\n (#21661.72)\n SURGEON/PHYSICIAN New\n (#21661.73)\n SURGERY CASE # New\n \n (#21661.74)\n SPECIMEN SUBMITTED New\n BY (#21661.811)\n BREIF CLINICAL New\n HISTORY \n (#21661.813)\n PREOPERATIVE New\n DIAGNOSIS \n (#21661.814)\n OPERATIVE FINDINGS New\nCorrects - Defect 373204 - \n (#21661.815) \n POST OPERATIVE New\n FINDINGS \n (#21661.816)\n \nLR CPRS PARAMETERS New\n (#69.71)\n \n \n \nVLE ANATOMIC PATHOLOGY - VistA LR462/OR405 SURGERY CASE DOES NOT DISPLAY \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\nON PATIENT DURING SPECIMEN LOGIN IN VISTA\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \nLRXOSX menu Modified\nLR7OAP CPRS 60 EDIT edit New\n \nLR7OAP CPRS 60 PRINT run routine New\nLR7OAP CPRS DIALOG MENU menu New\nLR7OAP CPRS DIALOG PRINT print New\n \n \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n \n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \nFix - M error when the accession has been cancelled using the "Delete\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nLR7OAPKP DIALOG PRINT LR CPRS PARAMETERS New\n SCREENS (#69.71)\n \nLR7OAP CPRS 60 INPUT LABORATORY TEST New\n EDIT (#60)\nto CRE863^LRAPLG1 routine that will restore the NOW// default instead of \naccession #, anat path"option and then a user tries to utilize the "Delete\n \n \nAdditional Information:\n \nN/A \n \n \nNew Service Requests (NSRs):\n---------------------------- \n#20140511\nentire order or individual test" option for the same order number. - \nThe Anatomic Pathology (AP) laboratory service needs a mechanism for \nclinicians to provide required patient-specific, procedure-specific, and \nspecimen-specific information to facilitate specimen processing by \npathologists. This mechanism must be in place for use by the specimen \nlabeling application in order to generate a primary specimen label that \npositively identifies the specimen and accurately associates it with the \npatient.\n \nPatient Safety Issues (PSIs):\n-----------------------------\nthere was a typo in the legacy code in the LROS routine.\nN/A\n \n \nRemedy Ticket(s) & Overview:\n----------------------------\n \nN/A\n \nProblem:\n-------\n \nN/A\n \nResolution:\n----------\nN/A\n \nTest Sites:\n----------\nAP Dialogs w/OR*3.0*405:\n North Florida/South Georgia VHCS\n \n Fresno\n Northern California\nDo no harm testing:\n Richmond\n \n \nDocumentation Retrieval Instructions:\n------------------------------------- \nUpdated documentation describing the new functionality introduced by this \npatch is available.\nSept 14, 2016 - V11 - Fixes 'no routine' error in APSUB^ORMBLDLR that was \n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/.\nThis transmits the files from the first available FTP server. Sites may \nalso elect to retrieve software directly from a specific server as \nfollows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\nstill calling LR7OAPMG which was changed with V10 to LR7OAPKM. Problem \n \nDocumentation can also be found on the VA Software Documentation Library \nat: http://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n-----------------------------------------------------------------------\nN/A\n \n \nPatch Installation:\nfound by developer once CPRS32 v16 GUI was available. The routine \n \n \nPre/Post Installation Overview:\n-------------------------------\nThis patch will install new fields to the LABORATORY TEST (#60), LAB \nORDER ENTRY (#69) and LABORATORY SITE PARAMETERS (#69.9) files. It will \nalso install a new file, LR CPRS SCREEN (#69.71), four new "LR7OAP" \noptions, a print template for the LR CPRS SCREEN file and an edit \ntemplate for the LABORATORY TEST file.\n \nLR7OAPMG has been added back into this build and will be removed at a \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is \nstrongly recommended that it be installed during non-peak hours when \nLAB usage is at a minimum.\n \n \nInstallation Instructions:\n--------------------------\nThis installation will install the components necessary to support the \nlater date.\nCPRS AP Order Dialog functionality released with OR*3.0*405.\n \n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter the patch \n LR*5.2*462:\npresenting a date and time.\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\nSept 8 - V10 - Fixes the following defects:\n \n4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' \n Respond: NO\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\nDefect # 373205 Surgeon Physician not displaying in VistA \n Respond: NO\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \n Respond: NO\n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \nPost-Installation Instructions:\nWhen submitted by is blank - the Surgeon does not display.\n-------------------------------\nN/A\n \nDefect # 373204 \nThe surgery case look up fails during log\n \nSept 1, 2016 - V9 - Fixes Undefined varible.\nDefect # - 371975 - Undefined variable when login the specimen in VistA \n \nif Surgeon/Physician is not selected in CPRS.\n \n \nAUG 25, 2016 - V8 - Fixes default bleed over problems with the \nPathologist and Submitted by fields in AP.\nAUG 12, 2016 - V7 - Fixes defect 357639:\n \nDefect: 357639 - VLE ANATOMIC PATHOLOGY - DURING SPECIMEN LOGIN IN VISTA, \nPATHOLOGIST FIELD POPULATES NAME OF SURGEON USED FOR A PRIOR ORDER\n \n423457: LI log in, anatomic path field of DATE/TIME SPECIMEN RECEIVED \nJULY 17, 2016 - V6 packman created and sent to forum - corrects problem \nin LRPLG1 routine.\nJULY 15, 2016 - V5 packman created and sent to forum - corrects hard \nerrors found by QA\nJULY 15, 2016 - V4 packman created and sent to forum\nJUNE 30, 2016 - V1 packman created and sent to forum\nJUNE 29, 2016 - V1 kids file to QA for do no harm testing\n \nThe build for this patch is distributed in support of the VLE \nAnatomic Pathology order dialog enhancements. It contains a modification \nshould default to NOW//\nto the LABORATORY TEST (#60), LAB ORDER ENTRY (#69), LABORATORY SITE\n(#69.9) and adds the new file LR CPRS PARAMETERS (#69.71).\n \n1- Anatomic Pathology specimen log-in option has been modified to \nprompt the user for an order number. This order number will be created \nby CPRS after patches OR*3.0*405 and LR*5.2*469 are installed.\n2- If a user enters an order number, the process deviates from the \ncurrent Log-in,anat path option in that it displays any data entered via\nCPRS AP order dialog. The fields presented could include any of the\nfollowing:\n \n a. SURGEON/PHYSICIAN\n b. SPECIMEN SUBMITTED BY\n c. SURGERY CASE #\n d. SPECIMEN DESCRIPTION/SPECIMEN (multiple)\n e. BRIEF CLINCAL DESCRIPTION\n f. PREOPERATIVE DIAGNOSIS\n g. OPERATIVE FINDINGS\n h. POSTOPERATIVE DIAGNOSIS\n3- If Surgical Case(s) are found for this patient in the last 7 days \nthey will be presented to the user for selection. If a case is selected \nOct 6, 2016 - V13 - Added the following as required patches: \nthe data from the Surgical Case will be displayed and the user will be \nasked if they wish to include this in the appropriate field in the \nAnatomic Pathology accession.\n4- If Surgical Case information is added to Anatomic Pathology \nfields it will display first and followed by the information obtained \nfrom the CPRS order.\n5- All other data entry/edit actions will be done via existing \nAnatomic Pathology options.\n \n \nLR*5.2*259,291,350,422,433,450\n \nBlood Bank Review:\n==================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*462 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by ProPath\nstandard titled: BBM Team Review of VistA Patches.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*462 does not \nalter or modify any software design safeguards or safety critical elements\nfunctions.\n\n
\nSept 30, 2016 - V9 - fixes defect #371947 by changing the values for the \nspecimen from the Specimen Description; she also pointed out that there is\n \nOption Name Type New/Modified/Deleted\n---------- ----- --------------------\nN/A\n \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\na character limitation in Specimen Description. Dev state that there is a\n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \n"switch" in the configuration to turn it on.\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ----- ------------------ --------------------\nN/A\n \n \nAdditional Information:\n \n \nN/A \n \n \n \nNew Service Requests (NSRs):\n-------------------------------------------- \n#20140511 \nThe Anatomic Pathology (AP) laboratory service needs a mechanism for \nclinicians to provide required patient-specific, procedure-specific, and \nspecimen-specific information to facilitate specimen processing by \nSept 14, 2016 - V8 - contains modifications to the LR AP DIALOG CONFIG \npathologists. This mechanism must be in place for use by the specimen \nlabeling application in order to generate a primary specimen label that \npositively identifies the specimen and accurately associates it with the \npatient.\n \nPatient Safety Issues (PSIs):\n---------------------------------------\nN/A\n \n \nfile in the following way:\nRemedy Ticket(s) & Overview:\n--------------------------------------------\n \nN/A\n \nProblem:\n------------\nN/A\n \nResolution:\n Each specimen of each orderable item within LR AP DIALOG CONFIG has\n--------------\nN/A\n \nTest Sites:\n---------------\nAP Dialogs w/OR*3.0*405:\n North Florida/South Georgia VHCS\n Fresno\n Northern California\n \n had the field HIDE FROM DESCRIPTION nullified so that the GUI will\nDocumentation Retrieval Instructions:\n-------------------------------------------------- \nUpdated documentation describing the new functionality introduced by this \npatch is available.\n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/.\nThis transmits the files from the first available FTP server. Sites may \nalso elect to retrieve software directly from a specific server as \nfollows:\n move the specimen name into the specimen description when building\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \nDocumentation can also be found on the VA Software Documentation Library \nat: http://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n--------------------------------------------------------------------------\n the specimen description.\nTBD\n \nPatch Installation:\n \nPre/Post Installation Overview:\n------------------------------------------\nThe environment check will ensure that the following ORDERABLE ITEMS and \nTOPOGRAPHY entries are an exact name match before patch LR*5.2*469 will \nbe allowed to install. This matching is critical due to the dependency of\nthe configuration in LR AP DIALOG CONFIG file by ORDERABLE ITEM and \nHIDE FROM DESCRIPTION field (#.02) of the SPECIMEN multiple (#3) of the \n \nTOPOGRAPHY.\n \nOrderable Item search Criteria:\n First check is for an exact name match\n If multiples found the check will fail\n If one or more match the name but none have a display group of\n anatomic pathology the check will fail\n If there is one exact name match with a display group of \n Anatomic Pathology the check will be successful\n \nAUG 12, 2016 - V7 packman created and sent to forum - contains modified \nSpecimen search Criteria:\n First check to see if SCT code has been assigned to any specimen\n If no association is found the check will fail\n Find all specimen entries in the environment check that have an\n SCT code assigned\n Find all specimens with an exact name match\n If SCT code is found for only one specimen check is successful\n If an exact name matches the SCT code the check is successful\n If multiple specimen with matching SCT code and matching names\n the check will fail\naorderable item and specimen lookups\n \n \n \nORDERABLE ITEMs checked:\n \n BONE MARROW\n BRONCHIAL CYTOLOGY\n BRONCHIAL BIOPSY\n DERMATOLOGY\n FINE NEEDLE ASPIRATE\nAUG 1, 2016 - V6 packman created and sent to forum - fixes unresolved \n GENERAL FLUID\n TISSUE EXAM\n GASTROINTESTINAL ENDOSCOPY\n GYNECOLOGY (PAP SMEAR)\n URINE\n UROLOGY,PROSTATE\n UROLOGY,BLADDER/URETER\n RENAL BIOPSY\n \nTOPOGRAPHY(specimens) - SNOMED CT ID codes checked:\npointers problem on install due to order dialog prompts that will not be \nABDOMEN - 113345001\nADRENAL GLAND - 23451007\nANAL CANAL - 34381000\nAPPENDIX - 66754008\nASCENDING COLON - 9040008\nBILE DUCT CYTOLOGIC MATERIAL - 110928002\nBILE DUCT MUCOUS MEMBRANE - 7035006\nBILIARY TRACT - 34707002\nBODY OF PANCREAS - 40133006\nBONE - 3138006\npopulated until OR*3.0*405 is installed.\nBONE MARROW - 14016003\nBREAST - 76752008\nBRONCHIAL CYTOLOGIC MATERIAL - 110912007\nBRONCHUS - 955009\nCARDIAC INCISURE OF STOMACH - 5459006\nCARDIAC OSTIUM OF STOMACH - 63853002\nCARDIO-ESOPHAGEAL JUNCTION - 25271004\nCECUM - 32713005\nCEREBROSPINAL FLUID CYTOLOGIC MATERIAL - 110969006\nCERVICAL CYTOLOGIC MATERIAL - 110949001\nJULY 21, 2016 - V5 packman created and sent to forum\nCHORIONIC VILLI - 2049008\nCOLON - 71854001\nDESCENDING COLON - 32622004\nDUODENUM - 38848004\nESOPHAGUS - 32849002\nESOPHAGUS, LOWER THIRD - 67173009\nESOPHAGUS, MIDDLE THIRD - 19000002\nESOPHAGUS, UPPER THIRD - 54738009\nGASTRIC FUNDUS - 414003\nGASTRIC JUICE - 31773000\nJULY 18, 2016 - V4 packman created and sent to forum\nGREATER CURVATURE OF STOMACH - 89382009\nHEAD OF PANCREAS - 64163001\nILEUM - 34516001\nJEJUNUM - 21306003\nKIDNEY - 64033007\nLEFT COLIC FLEXURE - 72592005\nLEFT TESTIS - 63239009\nLESSER CURVATURE OF STOMACH - 80085006\nLIVER - 10200004\nLUNG - 39607008\nJULY 15, 2016 - V3 packman created and sent to forum\nLYMPH NODE - 59441001\nMEDIASTINUM - 72410000\nNECK, LEFT SIDE - 170583000\nNECK, RIGHT SIDE - 170303002\nPANCREAS - 15776009\nPAROTID GLAND - 45289007\nPELVIS - 12921003\nPERIRENAL TISSUE - 47145004\nPERITONEAL CYTOLOGIC MATERIAL - 110944006\nPERITONEUM - 15425007\nJUNE 30, 2016 - V1 packman created and sent to forum\nPLEURAL CYTOLOGIC MATERIAL - 110913002\nPROSTATE - 41216001\nPYLORIC ANTRUM - 66051006\nPYLORUS - 280119005\nRECTOSIGMOID JUNCTION - 49832006\nRECTUM - 34402009\nRENAL PELVIS - 25990002\nRETROPERITONEUM - 82849001\nRIGHT COLIC FLEXURE - 48338005\nRIGHT TESTIS - 15598003\nLR AP DIALOG CONFIG file (#69.73) has been deleted in which the previous \nJUNE 29, 2016 - V1 kids file to QA for do no harm testing\nSALIVARY GLAND - 385294005\nSIGMOID COLON - 60184004\nSKIN - 39937001\nSMALL INTESTINE - 30315005\nSOFT TISSUES - 87784001\nSPLEEN - 78961009\nSTOMACH - 69695003\nSUBLINGUAL GLAND - 88481005\nSUBPHRENIC FOSSA - 243974009\nSYNOVIAL CYTOLOGIC MATERIAL - 110895009\n \nTAIL OF PANCREAS - 73239005\nTHYROID GLAND - 69748006\nTISSUE - 85756007\nTRANSVERSE COLON - 485005\nURETER - 87953007\nURINARY BLADDER - 89837001\nURINE - 78014005\nVAS DEFERENS - 57671007\nVERTEBRA - 51282000 \n \nThe build for this patch is distributed in support of the VLE \nPre-Installation Instructions:\n-------------------------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \nminutes \nto install\n \n1. The Laboratory ADPAC will need to create thirteen new lab tests to \n support the CPRS AP DIALOG functionality. These tests must be set up\nAnatomic Pathology order dialog enhancements. It contains the new file LR \n with a collection sample of AP SPECIMEN.\n \n If the COLLECTION SAMPLE file does not have an AP SPECIMEN entry\n refer to Section 2.2 of the following document:\n LEDI IV Installation Guide (Lab_Ledi_IV_Install_Guide.pd)\n \n \n2. Add thirteen new tests to the LABORATORY TEST file. Below are\n examples of what the AP tests should look like in the LABORATORY TEST\n File (#60) once the entries have been created. \nAP DIALOG CONFIG (#69.73).\n \nNOTE: Use the appropriate Institution(s) entries for your facility.\n \nWARNING: Make sure there are no other entries in the LABORATORY TEST file \nthat have the same name or synonym even though the subscript is\ndifferent. \n \nFor example: If there is an existing Bone Marrow with Subscript of \n'Cytology' then you may rename the test to 'Bone Marrow (Cytology)'.\nAlso if there is a synonym of 'Bone Marrow' then you may rename it to\n \n'Bone Marrow (CY)'.\n \nSet all tests up and TYPE NEITHER. When CPRS v32 is available you can \nset the TYPE to BOTH.\n \nWorkload code configuration should be done in compliance with your \ncurrent Laboratory practices.\n \nThe PRINT NAME is not important and can be whatever you wish it to be.\n \n1- The LR AP DIALOG CONFIG(#69.73) file is used to support the \nThe ACCESSION AREA should be whatever is in use at your facility as long \nas it is appropriate for the subscript of the test.\nLABORATORY TESTS (#60)\n \nNAME: BONE MARROW TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: BMARROW\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nbuilding and functioning of the CPRS AP DIALOG for the following thirteen \nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 118-BONE MARROW\n \n \nNAME: BRONCHIAL BIOPSY TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: BROBIOSP\ntests/orderable items:\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 109-BRONCHIAL BIOPSY\n \n \nNAME: BRONCHIAL CYTOLOGY TYPE: NEITHER\n SUBSCRIPT: CYTOLOGY HIGHEST URGENCY ALLOWED: STAT\n BONE MARROW\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: BRONC-CY\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: CYTOPATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Report Cytology\nCPRS SCREEN: 102-BRONCHIAL CYTOLOGY\n \n \nvalues were YES\n BRONCHIAL BIOPSY\nNAME: DERMATOLOGY TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: DERMATOL\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 124-DERMATOLOGY\n BRONCHIAL CYTOLOGY\n \n \nNAME: FINE NEEDLE ASPIRATE TYPE: NEITHER\n SUBSCRIPT: CYTOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: FNA\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: CYTOPATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n DERMATOLOGY\n NATIONAL VA LAB CODE: Report Cytology\nCPRS SCREEN: 103-FINE NEEDLE ASPIRATE\n \n \nNAME: GENERAL FLUID TYPE: NEITHER\n SUBSCRIPT: CYTOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: GENFLUID\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: CYTOPATHOLOGY\n FINE NEEDLE ASPIRATE\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Report Cytology\nCPRS SCREEN: 125-GENERAL FLUID\n \n \nNAME: TISSUE EXAM TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: GENSURG\n GASTROINTESTINAL ENDOSCOPY\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 116-TISSUE EXAM\n \n \nNAME: GASTROINTESTINAL ENDOSCOPY TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n GENERAL FLUID\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: GI-EDNO\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 119-GASTROINTESTINAL ENDOSCOPY\n \n \n GYNECOLOGY (PAP SMEAR)\nNAME: GYNECOLOGY (PAP SMEAR) TYPE: NEITHER\n SUBSCRIPT: CYTOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: GYN-PAP\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: CYTOPATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Report Cytology\nCPRS SCREEN: 126-GYNECOLOGY (PAP SMEAR)\n RENAL BIOPSY\n \n \nNAME: URINE TYPE: NEITHER\n SUBSCRIPT: CYTOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: URCYTO\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: CYTOPATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n TISSUE EXAM\n NATIONAL VA LAB CODE: Report Cytology\nCPRS SCREEN: 127-URINE\n \n \nNAME: UROLOGY,BLADDER/URETER TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: UROBLURE\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\n URINE\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 123-UROLOGY,BLADDER/URETER\n \n \nNAME: UROLOGY,PROSTATE TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: UROPROST\n \n UROLOGY,BLADDER/URETER\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement \n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 121-UROLOGY,PROSTATE\n \n \nNAME: RENAL BIOPSY TYPE: NEITHER\n SUBSCRIPT: SURGICAL PATHOLOGY HIGHEST URGENCY ALLOWED: STAT\n UROLOGY,PROSTATE\n REQUIRED COMMENT: ORDER COMMENT COMBINE TEST DURING ORDER: NO\n PRINT NAME: RENAL BX\nCOLLECTION SAMPLE: AP SPECIMEN\nINSTITUTION: CAMP MASTER ACCESSION AREA: SURGICAL PATHOLOGY\nSITE NOTES DATE: MAY 03, 2016\n NOTE: Test added in support of the VLE-AP order dialog enhancement\n NATIONAL VA LAB CODE: Surgical Pathology Tissue Exam\nCPRS SCREEN: 128-RENAL BIOPSY\n \n \n2- The LR AP DIALOG CONFIG file was created to support the new LR \n3. Confirm the ORDERABLE ITEMS were created properly in file 101.43.\n The number seen in the ID field will point to the internal entry \nnumber for the test\n in your LABORATORY TEST file.\n \nORDERABLE ITEMS (#101.43):\n \nNAME: BONE MARROW ID: 719;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: BONE MARROW\nSET: LAB\nOTHER LAB AP TESTS order dialog which will be released with OR*3.0*405.\nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \nNAME: BRONCHIAL BIOPSY ID: 5125;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: BRONCHIAL BIOPSY\nSET: LAB\nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \n \nNAME: BRONCHIAL CYTOLOGY ID: 5126;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: BRONCHIAL CYTOLOGY\nSET: LAB\nSET: AP\n LAB SECTION: CYTOLOGY TYPE: neither\n \n \nNAME: DERMATOLOGY ID: 5127;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: DERMATOLOGY\n \nSET: LAB\nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \nNAME: FINE NEEDLE ASPIRATE ID: 5128;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: FINE NEEDLE ASPIRATE\nSET: LAB\nSET: AP\n LAB SECTION: CYTOLOGY TYPE: neither\nBlood Bank Review:\n \n \nNAME: GENERAL FLUID ID: 5131;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: GENERAL FLUID\nSET: LAB\nSET: AP\n LAB SECTION: CYTOLOGY TYPE: neither\n \n \nNAME: TISSUE EXAM ID: 5133;99LRT\n==================\n DISPLAY GROUP: LABORATORY PACKAGE NAME: TISSUE EXAM\nSET: LAB\nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \nNAME: GASTROINTESTINAL ENDOSCOPY ID: 5129;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: GASTROINTESTINAL \nENDOSCOPY\nSET: LAB\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*469 does not \nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \nNAME: GYNECOLOGY (PAP SMEAR) ID: 5132;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: GYNECOLOGY (PAP \nSMEAR)\nSET: LAB\nSET: AP\n LAB SECTION: CYTOLOGY TYPE: neither\ncontain any changes to the VISTA BLOOD BANK Software as defined by ProPath\n \n \nNAME: URINE ID: 5137;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: URINE\nSET: LAB\nSET: AP\n LAB SECTION: CYTOLOGY TYPE: neither\n \n \nNAME: UROLOGY,BLADDER/URETER ID: 5134;99LRT\nDefect #371947 - During Sprint 12 Review demo the SMEs asked if the\nstandard titled: BBM Team Review of VistA Patches.\n DISPLAY GROUP: LABORATORY PACKAGE NAME: \nUROLOGY,BLADDER/URETER\nSET: LAB\nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \nNAME: UROLOGY,PROSTATE ID: 5135;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: UROLOGY,PROSTATE\nSET: LAB\n \nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \nNAME: RENAL BIOPSY ID: 5136;99LRT\n DISPLAY GROUP: LABORATORY PACKAGE NAME: RENAL BIOPSY\nSET: LAB\nSET: AP\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*469 does not \n4. Edit the ORDERABLE ITEM file (#101.43) and change the DISPLAY GROUP\n to ANATOMIC APTHOLOGY. This edit will remove the LAB entry from \nthe SET field.\n \n Select OPTION: eNTER OR EDIT FILE ENTRIES \n \n INPUT TO WHAT FILE: ORDERABLE ITEMS// \n EDIT WHICH FIELD: ALL// DISPLAY GROUP \n THEN EDIT FIELD: \n \nalter or modify any software design safeguards or safety critical elements\n Select ORDERABLE ITEMS NAME: BONE MARROW\n DISPLAY GROUP: LABORATORY// ANATOMIC PATHOLOGY \n \n \n Select ORDERABLE ITEMS NAME: \n \n Review of Orderable Item:\n NAME: BONE MARROW ID: 719;99LRT\n DISPLAY GROUP: ANATOMIC PATHOLOGY PACKAGE NAME: BONE MARROW\n SET: AP\nfunctions.\n LAB SECTION: SURGICAL PATHOLOGY TYPE: neither\n \n \n5. EDIT OF DISPLAY GROUPS FILE (#100.98): Editing the DISPLAY \n GROUPS file (#100.98) will display the Anatomic Pathology orders under\n Anatomic Pathology Display Group instead of the Laboratory Display\n group within the CPRS Order tab. The following steps will need to be\n performed.\n Coordinate these changes with your Clinical Coordinator.\n \n \n a. Edit ANATOMIC PATHOLOGY display group and add SP, CY and EM \n display groups as Members.\n INPUT TO WHAT FILE: DISPLAY GROUP// \n EDIT WHICH FIELD: ALL// \n \n \n Select DISPLAY GROUP NAME: anatOMIC PATHOLOGY \n NAME: ANATOMIC PATHOLOGY// \n Select MEMBER: SURGICAL PATHOLOGY \n Are you adding 'SURGICAL PATHOLOGY' as a new MEMBER (the 1ST for\nRISK ANALYSIS: Changes made by patch LR*5.2*469 have no effect on Blood \n this DISPLAY GROUP)? No// Y (Yes)\n MEMBER SEQUENCE: 1// \n Select MEMBER: CYTOLOGY \n Are you adding 'CYTOLOGY' as a new MEMBER (the 2ND for this\n DISPLAY GROUP)? No // Y (Yes)\n MEMBER SEQUENCE: 2// \n Select MEMBER: ELECTRON MICROSCOPY \n Are you adding 'ELECTRON MICROSCOPY' as a new MEMBER (the 3RD for\n this DISPLAY GROUP)? No// Y (Yes)\n MEMBER SEQUENCE: 3// \nBank software functionality, therefore RISK is none.\n Select MEMBER: \n MIXED NAME: Anat. Path.// \n SHORT NAME: AP// \n DEFAULT DIALOG: [leave blank]\n \n b.Delete the AP display groups (SP,CYand EM) from the LABORATORY \n display group entry.\n \n Select DISPLAY GROUP NAME: lab LABORATORY\n NAME: LABORATORY// \n \n Select MEMBER: CYTOLOGY// @\n SURE YOU WANT TO DELETE THE ENTIRE MEMBER? Y (Yes)\n Select MEMBER: AUTOPSY// SURGICAL PATHOLOGY \n ...OK? Yes// (Yes)\n \n MEMBER: SURGICAL PATHOLOGY// @\n SURE YOU WANT TO DELETE THE ENTIRE MEMBER? Y (Yes)\n Select MEMBER: ELECT RON MICROSCOPY \n ...OK? Yes// (Yes)\n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n MEMBER: ELECTRON MICROSCOPY// @\n SURE YOU WANT TO DELETE THE ENTIRE MEMBER? Y (Yes)\n Select MEMBER: ?\n Answer with MEMBER, or SEQUENCE\n Choose from:\n 1 CHEMISTRY\n 2 HEMATOLOGY\n 3 MICROBIOLOGY\n 4 BLOOD BANK\n 5 ANATOMIC PATHOLOGY\nspecimen could automatically populate in the Specimen Description [field]\nmade, no specific validation requirements exist as a result of\n 8 AUTOPSY\n \n You may enter a new MEMBER, if you wish\n Enter a display group. A display group that is an ancestor\n may not also be a member.\n Answer with DISPLAY GROUP NAME\n Do you want the entire 59-Entry DISPLAY GROUP List? \n \n You may enter a new DISPLAY GROUP, if you wish\n ANSWER MUST BE 3-30 CHARACTERS IN LENGTH\ninstallation of this patch.\n Select MEMBER:\n MIXED NAME: Lab// \n SHORT NAME: LAB// \n DEFAULT DIALOG: LR OTHER LAB TESTS//\n \n c. Add ANATOMIC PATHOLOGY display group to the ALL SERVICES display\n group.\n Select DISPLAY GROUP NAME: ALL SERVICES \n NAME: ALL SERVICES// \n Select MEMBER: CLINIC SCHEDULING// ANATOMIC PATHOLOGY \n \n Are you adding 'ANATOMIC PATHOLOGY' as a new MEMBER (the 21ST for\n this DISPLAY GROUP)? No// Y (Yes)\n MEMBER SEQUENCE: 21//\n Select MEMBER: \n MIXED NAME: All// \n SHORT NAME: ALL// \n DEFAULT DIALOG:\n \n6. REVIEW ORWOR CATEGORY SEQUENCE PARAMETER: Review the 'Anatomic \n Pathology' display group is set in ORWOR CATEGORY SEQUENCE parameter\n \n at the Package level as sequence number 74 which will enable the \n Anatomic Pathology order to sort ahead of other Laboratory orders on\n the CPRS Orders tab. If ANATOMIC PATHOLOGY is not present or not in \n sequence 74 have the IRM edit the package level.\n \n Note: If this parameter contains values for the User or System levels\n edit these entries and add ANATOMIC PATHOLOGY as a sequence \n number just before the LABORATORY entry.\n \nSelect OPTION NAME: XPAR MENU TOOLS General Parameter Tools\nPatch Components:\n \n \n LV List Values for a Selected Parameter\n LE List Values for a Selected Entity\n LP List Values for a Selected Package\n LT List Values for a Selected Template\n EP Edit Parameter Values\n ET Edit Parameter Values with Template\n EK Edit Parameter Definition Keyword\n \n--------------------------\nSelect General Parameter Tools <TEST ACCOUNT> Option: LV List Values for \na Selected Parameter\nSelect PARAMETER DEFINITION NAME: ORWOR CATEGORY SEQUENCE Orders\nCategory Sequence\n \nValues for ORWOR CATEGORY SEQUENCE\n \nParameter Instance Value\n-----------------------------------------------------------------\nPKG: ORDER ENTRY/RESULTS REPOR 10 M.A.S.\n \nPKG: ORDER ENTRY/RESULTS REPOR 20 ALLERGIES\nPKG: ORDER ENTRY/RESULTS REPOR 30 VITALS/MEASUREMENTS\nPKG: ORDER ENTRY/RESULTS REPOR 35 ACTIVITY\nPKG: ORDER ENTRY/RESULTS REPOR 40 NURSING\nPKG: ORDER ENTRY/RESULTS REPOR 50 DIETETICS\nPKG: ORDER ENTRY/RESULTS REPOR 59 CLINIC INFUSIONS\nPKG: ORDER ENTRY/RESULTS REPOR 60 IV MEDICATIONS\nPKG: ORDER ENTRY/RESULTS REPOR 65 OUTPATIENT MEDICATIONS\nPKG: ORDER ENTRY/RESULTS REPOR 68 NON-VA MEDICATIONS\nPKG: ORDER ENTRY/RESULTS REPOR 69 CLINIC MEDICATIONS\n Files & Fields Associated:\nPKG: ORDER ENTRY/RESULTS REPOR 70 INPATIENT MEDICATIONS\nPKG: ORDER ENTRY/RESULTS REPOR 74 ANATOMIC PATHOLOGY\nPKG: ORDER ENTRY/RESULTS REPOR 75 LABORATORY\nPKG: ORDER ENTRY/RESULTS REPOR 80 IMAGING\nPKG: ORDER ENTRY/RESULTS REPOR 90 CONSULTS\nPKG: ORDER ENTRY/RESULTS REPOR 100 PROCEDURES\nPKG: ORDER ENTRY/RESULTS REPOR 110 SURGERY\nPKG: ORDER ENTRY/RESULTS REPOR 120 OTHER HOSPITAL SERVICES\n \nEnter RETURN to continue or '^' to exit: \n \n \nParameter Instance Value\n-----------------------------------------------------------------\nPKG: ORDER ENTRY/RESULTS REPOR 130 SUPPLIES/DEVICES\nPKG: ORDER ENTRY/RESULTS REPOR 135 CLINIC SCHEDULING\n \nEnter RETURN to continue or '^' to exit: \n \n \n LV List Values for a Selected Parameter\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n LE List Values for a Selected Entity\n LP List Values for a Selected Package\n LT List Values for a Selected Template\n EP Edit Parameter Values\n ET Edit Parameter Values with Template\n EK Edit Parameter Definition Keyword\n \nSelect General Parameter Tools <TEST ACCOUNT> Option:\n \nInstallation Instructions:\nas that would be important. The specimen is usually a part of the\n------------------ ------------------- --------------------\n------------------------------\nThis installation will add the LR AP DIALOG CONFIG file (#69.73) and \nconfigure it for the Order Dialogs and Specimens listed in the environment\ncheck.\n \n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\nLR AP DIALOG CONFIG New\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter the patch \n LR*5.2*469:\n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n (#69.73)\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' \n Respond: NO\n \n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n Respond: NO\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \n Respond: NO\n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \nPost-Installation Instructions:\n---------------------------------------\nN/A\nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\ndescription. Stuti replied that a decision was made to remove the\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n\n
\nBuild Patch Description LR*5.2*163\n will have assigned CPT codes. This will cause a 2 to 4 fold increase\n in the workload Patient Care Encounter (PCE) Application Programmer\n Interface (API) traffic.\n \n The workload API is dependent on orderable tests being linked to a NLT\n code. National Laboratory File menu [LR70 60-64] option has sub-menu\n options to link the LABORATORY TEST file (#60) entries to NLT codes.\n \n 2. The routine LRCAPAMP that is used by the Recompile Phase 1 LMIP\n data [LR WKLD LMIP 1 REPEAT] option was not resetting all file entries.\n \n In certain situations, workload data could be lost.\n NOTE: Remember to recompile each division individually before repeating\n any additional data compiling.\n \n 3. The Workload code list [LRCAPD] option has been enhanced to\n display CPT codes and additional fields to be used by Laboratory\n Electronic Data Interchange (LEDI). NOTE: It is recommended that a\n new list be generated with this option.\n \n 4. The Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] option\n This patch upgrades the National Laboratory Test (NLT) codes. The\n now allows the user to edit all fields for any WKLD CODE in the file.\n This option should be restricted to the Laboratory Information\n Manager's (LIM's) menu.\n \n 5. The Add a new WKLD code to file [LRCAP CODE ADD] option now\n prompts for test cost and price.\n \n 7. The PRICE field (#8) has been added to the WKLD CODE file (#64).\n \n 8. Any conversion errors are stored in the LAB NLT/CPD CODE (#64.81).\n following enhancements are provided. The CPT/HCPCS CODES Version 6.0\n If no errors are generated during the CPT code linkage, this file will\n be empty after install is completed.\n \n 9. The PCE/VSIT ON field (#615) in LABORATORY SITE file (#69.9) will\n be set to "PCE/VSIT ONLY" which transmits CPT codes only to the workload\n API. No Clinic Stop Code data will be transmitted.\n \n 10 When using the Manual Linking of file 60 64 [LR7O 60-64 MANUAL]\n option to change an NLT code assigned to a test in the LABORATORY TEST\n file (#60), a FileMan error "??" would occur. This resulted in the\n is a required package for this patch.\n previous associated test in WKLD CODE file (#64) not being deleted. The\n routine LR7OU4 corrects this error.\n \n 1. All existing Current Procedural Terminology (CPT) codes in the\n WKLD CODE file (#64) will be removed. The 1997 CPT codes will be\n linked to existing codes. After installation, all relevant WKLD CODES\n\n
\nUpload new Etiology entries into file (61.2)\n\n
\nAssociated Patch: LA*5.2*90; which will be installed first as a part of\nmiddleware, sites will be able to switch from using class III interfaces\n \nParameter Name New/Modified/Deleted\n-------------- --------------------\nLR MI UI RELEASE DEFAULT NEW\n \nAdditional Information:\n \nN/A \n \nNew Service Requests (NSRs):\nto a UI standard interface. New functionality will be applied that will\n---------------------------- \nNSR #20131213 \nCarbapenem Resistant Enterobacteriaceae (CRE) Naming Conventions\nElectronic Interfacing of Automated Identification and Susceptibility \nTesting Instruments\n \nNSR #20140801\nTracking Multi-Drug Resistant Organisms \nPatient Safety Issues (PSIs):\n-----------------------------\nallow for an "MI" subscripted test to be added to the VistA Auto\nN/A\n \n \nRemedy Ticket(s) & Overview:\n----------------------------\n \nN/A\n \nProblem:\n-------\nInstrument file (#64.2). There will also be enhanced result processing and\nN/A\n \nResolution:\n----------\nN/A\n \nTest Sites:\n----------\nTampa (alpha)\nIowa City\nverify/release functions (see LA*5.2*90 patch descriptions for additional\nLexington\n \nSoftware and Documentation Retrieval Information \n==============================\nVistA Laboratory patch LR*5.2*474 software is distributed by Host File,\nalong with LA*5.2*90. \n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may \nalso elect to retrieve files directly from a specific server. \ndetails).\n \nSites may retrieve the software and/or documentation directly using \nSecure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory\nat the following OI Field Offices:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext \nSalt Lake City: fo-slc.domain.ext\n \nFile Name Contents Retrieval Format \n \n------------------ -------------------- ----------------\nLAB_MICRO_INTERFACE_ Host File containing ASCII\nRELEASE_1_0.KID KIDS software distribution \n \nLAB_MICRO_INTERFACE_RELEASE_1_0_DOCS.ZIP, which contains both .pdf and \n.doc formatted file of the following documents. Retrieval format is \nBINARY:\n \nLab Micro Interface Release 1.0 User Guide\nLab Micro Interface Release 1.0 Technical Manual and Security Guide \nThe build for this patch is distributed in support of the VistA \nLab Micro Deployment, Installation, Back-Out, and Rollback \nGuide \n \nThe VistA Documentation Library (VDL) web site will also contain the \nabove referenced documents. This website is usually updated within 1-3\ndays of the patch release date. The VDL web address for Laboratory\nUniversal Interface user documentation is:\nhttp://www.domain.ext/vdl/application.asp?appid=120\n \nNote: These previously released documents contain configuration and\nLaboratory Enhancement (VLE) Microbiology/Data Innovations interface \nmapping information that is useful to the implementation of the Universal\nInterface for Microbiology tests.\n------------------------------------------------------------------------\nLEDI IV Installation Guide LAB_LEDI_IV_IG.PDF binary\nLEDI IV User Manual LAB_LEDI_IV_UM.PDF binary\nLEDI IV Update AP/MICRO LEDI_IV__AP__MICRO_ binary\nConfiguration Guide CONFIGURATION_GUIDE.PDF binary\n \n \nPatch Installation:\nutilizing the Laboratory Universal Interface.\n-------------------\n \n \nPre/Post Installation Overview:\n-------------------------------\nThis patch, LR*5.2*474 is part of a combined build for the Laboratory \nMicrobiology Interface Enhancement patch.\n \nThis patch install must be coordinated with the Laboratory ADPAC to \nensure that all Lab Interface related activities are halted.\nthis combined build.\n \n \nThis installation will modify the Enter/verify data (auto instrument)\noption for the Microbiology Universal Interface process by providing the\nfollowing release options:\n \nSelect RELEASE action: Edit (full)// ?\n \nEntering 0 will abort review/release.\nEntering 1 will allow release 'as is' with no editing.\nEntering 2 will allow you to enter/edit comments then release.\nThe patch provide new functionality provides for the Enter/Verify data \nEntering 3 will allow you to enter full edit, similar to 'Results entry' \noption.\n \nSelections 1-3 will allow editing of status and approved date/time.\n \n Select one of the following:\n \n 0 Quit\n 1 Release\n 2 Comments/Release\n(Auto Instrument) option which will allow the technologist with the \n 3 Edit (full)\n \n \nPre-Installation Instructions:\n------------------------------\nEnsure that all Lab Interface activity has been halted !!\n \nThis would include:\n-Editing of an Auto Instrument file entry, \n-Turn off the Auto Downloading process to prevent the building and \nauthority to release three release actions.\ndownloading \nof a Load/Worklist to the Instrument Manager. \n-Shut down all LA7UI logical links and any other HL7 process (HLZTCP or \nHLLP processes) \nto prevent the processing of result messages from the IM.\n \nThis patch may be installed with users on the system as long as the above \nprocess controls have been followed.\n \n \n \nInstallation Instructions:\n--------------------------\nThis patch may be installed with users on the system although it is \n recommended that it be installed during non-peak hours to minimize \n potential disruption to users. This patch should take less than 5 \n minutes to install.\n \n \n1. DOWNLOAD HOST KIDS FILE \n ----------------------\n \n Download the KIDS file LAB_MICRO_INTERFACE_RELEASE_1_0.KID from \n the ANONYMOUS.SOFTWARE directory of Albany, Hines, or the Salt\n Lake OIFO to the appropriate directory on your system.\n \n2. LOAD DISTRIBUTION \n -----------------\n Use the 'LOAD A DISTRIBUTION' option on the KIDS \n INSTALLATION menu, and enter: the directory onto which you \n have downloaded the host file, followed by \n LAB_MICRO_INTERFACE_RELEASE_1_0.KID, the host file name. \nBlood Bank Review:\n \n3. START UP KIDS \n -------------\n Start up the Kernel Installation and Distribution System Menu \n [XPD MAIN]:\n Edits and Distribution ... \n Utilities ... \n Installation ... \n \n Select Kernel Installation & Distribution System Option: \n==================\n Installation \n -------------\n \n Load a Distribution \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Install Package(s) \n Restart Install of Package(s) \n Unload a Distribution \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*474 does not \n Backup a Transport Global \n \n4. Select Installation Option: \n ---------------------------\n \n a. Use the Load a Distribution and select Host File: \n LAB_MICRO_INTERFACE_RELEASE_1_0.KID\n b. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates.\ncontain any changes to the VISTA BLOOD BANK Software as defined by ProPath\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n d. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n \nstandard titled: BBM Team Review of VistA Patches.\n Install? NO//' \n Respond: NO\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n Respond: NO\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \n Respond: NO\n \n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' \n Respond: 0.\n \n \nPost-Installation Instructions:\n-------------------------------\nADPAC and Microbiology Tech instructions:\n \n1. After data has been received from the Data Innovations for an \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*474 does not \nautomated Microbiology instrument, the releasing Microbiology Technologist\nwill be presented with the following options:\n \nSelect RELEASE action: Edit (full)// ?\n \nEntering 0 will abort review/release.\nEntering 1 will allow release 'as is' with no editing.\nEntering 2 will allow you to enter/edit comments then release.\nEntering 3 will allow you to enter full edit, similar to 'Results entry' \noption.\nalter or modify any software design safeguards or safety critical elements\nSelections 1-3 will allow editing of status and approved date/time.\n \n Select one of the following:\n \n 0 Quit\n 1 Release\n 2 Comments/Release\n 3 Edit (full)\n \nSelect RELEASE action: Edit (full)// 0 Quit\nfunctions.\n \nDo you want to PURGE these results? NO//\n \n \n2. A new parameter LR MI UI RELEASE DEFAULT is included with this \npatch and it provides the VAMC site the ability to set the release default\nat the package and user levels.\n \nExample configuration:\n \n \nSelect OE/RR interface parameters <TEST ACCOUNT> Option: Select Lab\n liaison menu <TEST ACCOUNT> Option: OE/RR interface parameters\n \n \n EH Edit HOSPITAL SITE parameters\n AS Edit a lab administration schedule\n IL Inquire to a Lab administration schedule\n CC Update CPRS Parameters ...\n \nSelect OE/RR interface parameters <TEST ACCOUNT> Option: CC Update CPRS\nRISK ANALYSIS: Changes made by patch LR*5.2*474 have no effect on Blood \nParameters\n \n \n PA Update CPRS with Lab order parameters\n SI Update CPRS with Single Lab test\n UP Update CPRS with all Lab test parameters\n DO Domain Level Parameter Edit\n LO Location Level Parameter Edit\n PP Package Level Parameter Edit\n UL Display Lab User Parameters\nBank software functionality, therefore RISK is none.\n \nSelect Update CPRS Parameters <TEST ACCOUNT> Option: PP Package Level \nParameter Edit\n \nLab Package Level Parameters for Package: LAB SERVICE\n--------------------------------------------------------------------------\nCollect on Monday YES\nCollect on Tuesday YES\nCollect on Wednesday YES\nCollect on Thursday YES\n \nCollect on Friday YES\nCollect on Saturday YES\nCollect on Sunday YES\nLab Collects on Holidays YES\nLab Collect Days Allowed in Future 7\nMaximum Days for Continuous Orders \nDefault manual verify method \nDefault load/work list verify method\nDisplay Provider in Micro Result Entry \nDefault Micro Instrument Release Action VITEK Edit (full)\nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nPrompt CPRS Alert in Micro Result Entry Don't Ask\nPrompt CPRS Alert in CH Result Entry \nEGFR Creatinine IDMS-traceable Method \nEGFR Patient's Age Cutoff \nEGFR Result Cutoff \nSend an alert after AP release \nDefault AP Report Selection Prompt \nAsk Performing Lab AP YES\nAsk Performing Lab Micro YES\nPrint SNOMED Code System SNOMED I\nThe build for this patch is distributed as part of a multi-package build \nmade, no specific validation requirements exist as a result of\nDocument Surgery Package Case Info NO\nChemistry GUI Report Right Margin \nMicrobiology GUI Report Right Margin \nAP GUI Report Right Margin \nMethod of Assigning AP Accession Number\nDefault Accessioning Specimen\nDefault Accessioning Collection Sample\nDefault Accessioning Lab Test\nExclude removed tests from building\nUse default accession dates\ninstallation of this patch.\nPrint Reporting/Printing Facility None\nDays to keep of instrument data 1 2\nLab STS Default Mapping Files Directory \nLab STS Default Mapping Filespec *.TXT\n--------------------------------------------------------------------------\nCOLLECT MONDAY: YES// \nCOLLECT TUESDAY: YES// \nCOLLECT WEDNESDAY: YES// \nCOLLECT THURSDAY: YES// \nCOLLECT FRIDAY: YES// \n \nCOLLECT SATURDAY: YES// \nCOLLECT SUNDAY: YES// \nIGNORE HOLIDAYS: YES// \nLAB COLLECT DAYS ALLOWED IN FUTURE: 7// \nMAXIMUM DAYS FOR CONTINUOUS ORDERS: \nDefault manual verify method: \n \nFor Default load/work list verify method -\nSelect Accession Area: \nDisplay Provider in Micro Result Entry: \n \n \nFor Default Micro Instrument Release Action -\nSelect Load/Work List: VITEK \n \nLoad/Work List: VITEK// VITEK VITEK\nDefault load/work list verify method: Edit (full)// \n \nFor Default Micro Instrument Release Action -\nSelect Load/Work List: \n NOTE: This parameter will allow the default release action to be\nPatch Components:\n Load/Work List specific.\n \n \n3. Setting the default release action for a user:\n \nSelect Information-help menu <TEST ACCOUNT> Option: PP General Lab User \nParameters\n \nLab User Level Parameters for User: TECH,MICRO\n--------------------------------------------------------------------------\n-----------------\nDefault lab label printer\nDisplay previous comments for test\nDefault Performing Laboratory \nAsk Performing Lab AP \nAsk Performing Lab Micro \nDisplay Provider in Micro Result Entry \nPrompt CPRS Alert in CH Result Entry \nPrompt CPRS Alert in Micro Result Entry \nDefault Micro Instrument Release Action VITEK Release\nDefault AP Report Selection Prompt \nNone\nSend an alert after AP release \nDefault Accessioning Specimen\nDefault Accessioning Collection Sample\nDefault Accessioning Lab Test\nExclude removed tests from building\nUse default accession dates\nLab Messaging - Parse HL7 Messages \nLab Messaging - Display using Browser \nLab Messaging - Show Identifiers \nChemistry GUI Report Right Margin \n \nMicrobiology GUI Report Right Margin 132\nAP GUI Report Right Margin 240\nLab STS Default Mapping Files Directory \nLab STS Default Mapping Filespec \n--------------------------------------------------------------------------\n \nFor Default lab label printer -\nSelect Division: \n \nFor Display previous comments for test -\nFiles & Fields Associated:\nSelect Laboratory Test: \nDefault Performing Laboratory: \nAsk Performing Lab AP: \nAsk Performing Lab for MICRO: \nDisplay Provider in Micro Result Entry: \nSend CPRS Alert in CH Result Entry: \nSend CPRS Alert in Micro Result Entry: \n \nFor Default Micro Instrument Release Action -\nSelect Load/Work List: VITEK \n \nAre you adding VITEK as a new Load/Work List? Yes// YES\n \nLoad/Work List: VITEK// VITEK VITEK\nDefault load/work list verify method: Release\n \nFor Default Micro Instrument Release Action -\nSelect Load/Work List: \n NOTE: This parameter will allow the default release action to be\n Load/Work List specific.\nAP Report Selection Default: ^\nthat contains LA*5.2*90 and LR*5.2*474. The build contains functionality \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\nthat will allow Microbiology instrumentation to utilize the Lab Universal\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\nInterface. \n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \nN/A\n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \n \nN/A\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \n \nBy utilizing the Universal Interface and Instrument Manager (IM) \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nLR USER PARAMETER TEMPLATE NEW\n FILE (8989.52)\nLR PKG PARAMETER TEMPLATE NEW\n FILE (8989.52)\n \nParameters Associated:\n\n
\nThe NSR20140715 Surgical Pathology Report Enhancements for Readability \ncare provider, I need to view the Laboratory Surgical Pathology Report \ncolumns in-line, so the report is legible and I can provide timely care \nfor the patient. \nintake modifies the Laboratory Surgical Pathology report by lining up the \ncolumns so that the report is more legible. \n \nThis intake has been implemented locally at the Kansas City, Kansas VAMC. \n \nThe NSR for this intake addresses the following requirement: \n \n* VHBAO: NEED502503 Surgical Pathology Report Enhancement: As a health \n\n
\nSubject: ANATOMIC PATHOLOGY ORDER DIALOG ENHANCEMENT - FIX FOR AUTOPSY \nAssociated Patches: LR*5.2*462\npathologists. This mechanism must be in place for use by the specimen \nlabeling application in order to generate a primary specimen label that \npositively identifies the specimen and accurately associates it with the \npatient.\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \n \nRemedy Ticket(s) & Overview:\n----------------------------\n \nN/A\n \nProblem:\n-------\nN/A\n \nResolution:\nThe build for this patch is distributed in support of the VistA Lab \n----------\nN/A\n \nTest Sites:\n----------\nAP Dialogs w/OR*3.0*405:\n North Florida/South Georgia Veterans Health System (Gainesville, FL)\n Central California VA Health Care System (Fresno, CA)\n VA Northern California Health Care System\n Edward Hines Jr. VA Hospital\nEnhancement (VLE) Anatomic Pathology order dialog enhancements. This \n Philadelphia VA Medical Center\n \n \nDocumentation Retrieval Instructions:\n------------------------------------- \nSoftware being released as a host file and/or documentation describing \nthe new functionality introduced by this patch are available.\n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may \npatch is to fix an error to released patch LR*5.2*462 [ANATOMIC PATHOLOGY \nalso elect to retrieve files directly from a specific server. \n \nSites may retrieve the software and/or documentation directly using \nSecure \nFile Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at \nthe following OI Field Offices:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext \nSalt Lake City: fo-slc.domain.ext\nORDER DIALOG ENHANCEMENT]. It resolves the error generated when using the \n \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n-----------------------------------------------------------------------\nVistA laboratory Enhancements AP_VIP_Deployment_Installation_ Binary\n(VLE) Anatomic Pathlogy (AP) Roll Back_Back-Out_Guide.DOC\nOrder Dialogs\noption "Verify/release reports, anat path" [LRAPR] to verify/release an \nVistA laboratory Enhancements AP_VIP_Deployment_Installation_ Binary\n(VLE) Anatomic Pathlogy (AP) Roll Back_Back-Out_Guide.PDF\nOrder Dialogs\n \n \nPatch Installation:\n \n \nPre/Post Installation Overview:\n-------------------------------\nAutopsy (AU) accession. This patch is being released as an emergency \nThis patch is a fix for an Autopsy error that is triggered when users \n'Verify/Release Autopsy report in VistA. \n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is \nstrongly recommended that it be installed during non-peak hours when \nLAB usage is at a minimum.\n \n \npatch with a compliance date of Feb 5, 2017 to coincide with the \nInstallation Instructions:\n--------------------------\nThis patch may be installed with users on the system although it is \n recommended that it be installed during non-peak hours to minimize \n potential disruption to users. This patch should take less than 5 \n minutes to install.\n \nThis installation will install the components necessary to support the \nCPRS AP Order Dialog functionality released with OR*3.0*405.\n \nLR*5.2*462 compliance date of Feb 5, 2017\n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter the patch \n LR*5.2*462:\n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\nERROR\n \n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\nDefect Addressed - 451608\n choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' \n Respond: NO\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n Respond: NO\n \n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \n Respond: NO\n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \nPost-Installation Instructions:\n-------------------------------\nN/A\nThe patch contains two routine, no option or menus.\n \n \nRoutine Information:\n====================\n \nThe second line of each of these routines now looks like:\n;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 1\n \nThe checksums below are new checksums, and\ncan be checked with CHECK1^XTSUMBLD.\n \n \nRoutine Name: LR482\n Before: n/a After: B4627709 **482**\nRoutine Name: LRAPRES1\n Before: B70400068 After: B71690317 **259,336,369,365,397,413,350,\n 462,482**\n \nRoutine list of preceding patches: 462\nBlood Bank Review:\n==================\nAll of the above changes have been reviewed by the VISTA Blood Bank \nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE \ncontrol functions.\n \n \nRISK ANALYSIS: Changes made by patch LR*5.2*482 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*482 does not \nalter or modify any software design safeguards or safety critical \nelements functions.\n \nPOTENTIAL IMPACT ON SITES: This patch contains changes to routines and \nfiles identified in ProPath standard titled: BBM Team Review of VistA \nCategory: PATCH FOR A PATCH\nPatches, group B listing. The changes have no effect on Blood Bank \nfunctionality or medical device control functions. There is no adverse \npotential to sites.\n \n \nPatch Components:\n-----------------\n \nN/A\n \n EMERGENCY PATCH\nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n \n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nN/A\n \n \n \nDescription:\n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \n===========\nSecurity Key Name\n-----------------\nN/A\n \n \nTemplates Associated:\n \nN/A\n \nAdditional Information:\n \n \nN/A \n \n \nNew Service Requests (NSRs):\n---------------------------- \n#20140511\nThe Anatomic Pathology (AP) laboratory service needs a mechanism for \nclinicians to provide required patient-specific, procedure-specific, and \nspecimen-specific information to facilitate specimen processing by \n\n
\nThis is a general maintenance patch for the laboratory\n to transmit to HDR\n \n \n2. INC000000775621 - Lab order merging leads to incorrect\n status of file 100 orders\npackage by the Vista Maintenance team that addresses\nissues with some patients test results not getting transmitted\nto the HDR (Health Data Repository) and with some lab orders\nthat have the wrong status in file #100 (ORDER).\n \nASSOCIATED REMEDY TICKET:\n========================\n1. INC000001243211 - Failure of merged lab collect orders\n\n
\nSee National Patch Module for details.\n\n
\n This patch contains corrections that address issues related to the\n contain any changes to the VISTA BLOOD BANK Software as defined by \n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \n ProPath standard titled: BBM Team Review of VistA Patches.\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ----- ------------------ --------------------\nN/A\n \n \nAdditional Information:\n \n \nN/A \n \n \nNew Service Requests (NSRs):\n-------------------------------------------- \n#20140511 \n The Anatomic Pathology (AP) laboratory service needs a mechanism for \n clinicians to provide required patient-specific, procedure-specific, and \n specimen-specific information to facilitate specimen processing by \n pathologists. This mechanism must be in place for use by the specimen \n RISK ANALYSIS: Changes made by patch LR*5.2*479 have no effect on Blood \n labeling application in order to generate a primary specimen label that \n positively identifies the specimen and accurately associates it with the \n patient.\n \nPatient Safety Issues (PSIs):\n---------------------------------------\nN/A\n \n \nCA SDM Ticket(s) & Overview:\n Bank software functionality, therefore RISK is none.\n--------------------------------------------\n \nN/A\n \n \nTest Sites:\n---------------\nAP Dialogs w/OR*3.0*405:\n North Florida/South Georgia Veterans Health System (Gainesville, FL)\n Edward Hines Jr. VA Hospital\n \n Philadelphia VA Medical Center\n \nProblem:\n-------\n Sub files 60.0216611,.01 (AOE CPRS SCREEN) and 60.12166,.01 (AOE SCREEN) \n in the LABORAOTRY TEST file (#60) were erroneously released with the\n distribution of patch LR*5.2*462.\n \nResolution:\n-----------\n VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n These two fields will be removed from the data dictionary with the LR479 \n post-install routine.\n \nProblem:\n--------\nSub file 69.321661,.01 (VFD AOE) in the LAB ORDER ENTRY file (#69) was \nerroneously released with the distribution of patch LR*5.2*462.\n \nResoultion:\n-----------\n made, no specific validation requirements exist as a result of \n This field will be removed form the data dictionary with the LR479 \n post-install routine.\n \nProblem:\n--------\n Specimen Login in VistA does not assign correct accession number when \n using the new accession process added to the AP Specimen Log In option \n with patch LR*5.2*462. The order number entered at this point was created\n using the new AP Order Dialog in CPRS. The accession area assigned to the\n Laboratory test in file 60 was not being honored and only SURGICAL \n installation of this patch.\n PATHOLOGY (SP) and CYTOLOGY (CY) accession areas were being utilized.\n \nResolution:\n-----------\n Routine modifications were made to honor the correct accession area as\n defined in the Laboratory test file in association with the division\n of the user accessioning the order.\n \nProblem:\n--------\n \n Practitioner field in CPRS displays '0' if Surgeon/Physician is blank in \n VistA - Backdoor order only.\n \nResolution:\n-----------\n Routine modifications were made to correct the storage of a zero when no\n Surgeon/Physician was entered during the accessioning process. \n \nProblem:\n--------\n VistA Lab Enhancements (VLE) released patches LR*5.2*462 and LR*5.2*469.\nPatch Components:\n Lock login process of AP Orders via Accessioning menu - Post Release\n LR479.\n \nResolution:\n-----------\n Option Accessioning tests ordered by ward order entry [LROE] has been\n modified to not allow Anatomic Pathology orders to be processed. The \n user will see the following message before exiting the option:\n \n This is an Anatomic Path order \n--------------------------\n \n Must use 'Log-in, anat path' Option to accession this Order \n \nProblem:\n--------\n AP Backdoor order from VistA displays Send Patient to Lab as default \n Collection Status.\n \nResolution:\n-----------\n \n Routine modifications were made to change the default from SP Send \n Patient to WC Ward Collect.\n \nProblem:\n--------\n Backdoor AP Order from VistA does not display patient location in CPRS.\n \nResolution:\n-----------\n Routine modifications were made to pass the correct pointer to CPRS so \nFiles & Fields Associated:\n that the ordering location will be reflected correctly.\n \n \nProblem:\n--------\n Error <SUBSCRIPT>AP+2^LRXREF is being triggered during AP Specimen \n Log-in accessioning of orders created in CPRS. There was code in the \n routine that was trying to continue the accessioning process even if the \n test being accessioned did not have an accession area defined that \n matched the division of the accessioning person. The default lookup was \n \n expecting to find an SP for Surgical Pathology or a CY for Cytopathology \n accession area abbreviations. If a site has changed these abbreviations \n to something other than SP and CY the <SUBSCRIPT> error would be \n triggered.\n \nResolution:\n-----------\n Routine modifications were made to remove the default accession area \n logic and replace it with code that will exit the user with the following\n message:\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n \n[ TISSUE EXAM] DOES NOT HAVE AN APPROPRIATE ACCESSION AREA DEFINED \n Log-in Aborted\n \nProblem:\n--------\n The VLE AP project is unable to acquire an ICR with $$DEFAULT^ORWLRAP1.\n \nResolution:\n-----------\n------------------ ------------------- --------------------\n This API was removed from the input transform of the .01 field of file \n 69.73.\n \n DD: 69.73:.01\n \nProblem:\n--------\n The builder blocks had three misspellings (erosioin,technnique and SLide)\n for selectable values.\n \nLR AP DIALOG CONFIG 69.73,.01 ORDERABLE ITEM Modified\nResolution:\n-----------\n The patch has a post install sub-routine SPELL^LR479 that will search for\n strings that equal "erosioin", "technnique" or "SLide" within the 69.73\n file and set them to "erosion" and "technique" respectively.\n \n Routine: LR479\n \n \nProblem:\n (#69.73)\n--------\n For the Urology,Prostate dialog Right Testis specimen the builder block \n "Submission Type" should be "Specimen Type" and "Specimen Submission" \n should be "Submission Type".\n \nResolution:\n-----------\n The patch has a post install sub-routine TITLE^LR479 that will search for\n a builder block with a value of "Orchiectomy" and if the builder block \n title reads "Submission Type" it will be changed to "Specimen Type" and \n 69.73,.02 ALLOW OTHER Modified\n the second builder block title will be set to "Submission Type".\n \n Routine: LR479\n \n Documentation Retrieval Instructions:\n ------------------------------------- \n Software will be released via a PackMan message. \n \n The preferred method is to retrieve files from download.vista.domain.ext.\n This transmits the files from the first available server. Sites may \n The description of the issues can be reviewed in the Problem and\n SPECIMENS\n also elect to retrieve files directly from a specific server. \n \n Sites may retrieve the software and/or documentation directly using \n Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE \n directory at the following OI Field Offices:\n \n Albany: fo-albany.domain.ext\n Hines: fo-hines.domain.ext \n Salt Lake City: fo-slc.domain.ext\n \n 69.73,.03 RESTRICT Modified\n Title/File Name FTP Mode\n -------------------------------------------------------------------------\n N/A\n \n Documentation can also be found on the VA Software Documentation Library \n at:\n http://www4.domain.ext/vdl/\n \n \nPatch Installation:\n MULTIPLE SPECIMENS\n \n \n Pre/Post Installation Overview:\n -------------------------------\n N/A \n \n Pre-Installation Instructions:\n ------------------------------\n N/A\n \n 69.73,1 ORDER PROMPTS Modified\n Installation Instructions:\n --------------------------\n This patch may be installed with users on the system although it is \n strongly recommended that it be installed during non-peak hours when \n LAB usage is at a minimum. This patch should take less than 5 minutes to\ninstall.\n \n This installation will install the components necessary to support the \n CPRS AP Order Dialog future functionality that is being released with\n OR*3.0*405.\n 69.731,.02 HIDE Modified\n \n 1. Choose the PackMan message containing this patch.\n \n 2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter the \n patch LR*5.2*479:\n a. Backup a Transport Global - This option will create a backup\n 69.731,.03 REQUIRED Modified\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n 69.731,.04 DEFAULT Modified\n 4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \n 5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' \n Respond: NO\n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n Respond: NO\n 69.73,2 PAGES Modified\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \n Respond: NO\n \n 8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \n Post-Installation Instructions:\n -------------------------------\n 69.732,.01 PAGE# Modified\n N/A\n \n Back-Out Procedure:\n -------------------\n The build does not make any changes that would affect the operational \n state of the software and platform settings.\n \n1. Back-Out Strategy\n During installation, if the option to back up routines was run as \n directed, 'Backup a Transport Global', then routines have the ability\n 69.732,.02 PAGENAME Modified\n to be restored from the "backup" MailMan message that was generated.\n However, the KIDS installation process does not perform a restore of \n other VistA components, such as data dictionary, cross-reference, and\n template changes, etc. \n Prior to attempting a back-out of the software, please contact the VA\n Help Desk at 1-855-673-4357 for support or assistance.\n \n a. Back-Out Considerations\n The LIM and the Chief of Pathology have the authority to order \nthe\n Resolution sections of this patch description.\n 69.732,.03 HID Modified\n back-out.\n \n b. Back-Out Criteria\n Criteria for a back-out includes, but are not limited, to the\n following:\n i. Failed baseline testing.\n ii. Non-recoverable software error.\n \n c. Back-Out Risks\n No back-out risks have been determined at this time.\n 69.732,.04 REUIRED Modified\n d. Authority for Back-Out\n The LIM, the Lab Manager, and the Chief of Pathology have the\n authority to request and approve the back-out and accept the\n risks.\n \n2. Rollback Procedure\n The LR*5.2*479 build as well as any installed dependent patch changes \n that follow these releases need to be taken out in reverse of the\n order in which they were installed; routines and data dictionary\n modifications and populated data must also be rolled back in reverse\n 69.732,.06 W TITLE Modified\n order.\n Please contact the VA Help Desk at 1-855-763-4357 for support or \n assistance regarding roll-back procedures.\n \n a. Rollback Considerations\n No rollback considerations have been determined at this time.\n \n b. Rollback Criteria\n The only criteria for a rollback that has been determined at this\n time is that the installation failed baseline testing.\n 69.732,1 BULDER BLOCK Modified\n \n c. Rollback Risks\n The only risk determined at this time is the possibility of\n downtime which would only effect the users of the Laboratory\n package.\n \n d. Authority for Rollback\n The LIM, the Lab Manager, and the Chief of Pathology have the\n authority to require the rollback and accept the risks.\n \n 69.7321,.0 PG BLOCK TITLE Modified\n e. Rollback Procedure\n The need for a rollback is highly unlikely, however if it is\n required, please contact the Product Support team for\n assistance. The rollback procedure will require Lab downtime and\n a reinstall of any previous KIDS versions.\n \n \n Example of Captured Installation:\n ==================================\n \n 69.7321,.2 REQUIRED Modified\nEnter message action (in IN basket): Ignore// Xtract KIDS\n \nSelect PackMan function: 6 INSTALL/CHECK MESSAGE\n \nLine 389 Message #412245 Unloading KIDS Distribution LR*5.2*479\n LR*5.2*479\n \nWant to Continue with Load? YES// YES\nLoading Distribution...\n \n 69.7321,03 LIST Modified\n LR*5.2*479\nWill first run the Environment Check Routine, LR479\n \n \n \n --- Environment Check is Ok ---\n \n \n Sending install loaded alert to mail group G.LMI\n \n 69.7321.04 DEFAULT Modified\nSelect PackMan function: \n \n \nEnter message action (in IN basket): Ignore// \n \n \nSelect Installation <TEST ACCOUNT> Option: 5 Backup a Transport Global\nSelect INSTALL NAME: LR*5.2*479 2/21/17@10:44:12\n => LR*5.2*479\n \n 69.7321,1 VALUES Modified\nThis Distribution was loaded on Feb 21, 2017@10:44:12 with header of \n LR*5.2*479\n It consisted of the following Install(s):\n LR*5.2*479\nSubject: Backup of LR*5.2*479 install on Feb 21, 2017\n Replace \nLoading Routines for LR*5.2*479.........\nSend mail to: BELSCHWINDER,MICHAEL// BELSCHWINDER,MICHAEL\nSelect basket to send to: IN// \nAnd Send to: \n 69.73211,.01 VALUE Modified\n \n \nSelect Installation <TEST ACCOUNT> Option: 4 Compare Transport Global to \nCurrent System\nSelect INSTALL NAME: LR*5.2*479 2/21/17@10:44:12\n => LR*5.2*479\n \nThis Distribution was loaded on Feb 21, 2017@10:44:12 with header of \n LR*5.2*479\n It consisted of the following Install(s):\n \n 69.73211,.02 ASSOCIATE WITH Modified\n LR*5.2*479\n \n Select one of the following:\n \n 1 Full Comparison\n 2 Second line of Routines only\n 3 Routines only\n 4 Old style Routine compare\n \nType of Compare: 1 Full Comparison\n 69.73211,.03 SPECIAL Modified\nDEVICE: HOME// TELNET PORT\n \nReport is displayed....\n \n \nSelect Installation <TEST ACCOUNT> Option: 2 Verify Checksums in \nTransport Global\nSelect INSTALL NAME: LR*5.2*479 2/21/17@10:44:12\n => LR*5.2*479\n \n 69.73,3 SPECIMEN Modified\nThis Distribution was loaded on Feb 21, 2017@10:44:12 with header of \n LR*5.2*479\n It consisted of the following Install(s):\n LR*5.2*479\n \nWant each Routine Listed with Checksums: Yes// YES\nDEVICE: HOME// TELNET PORT\n \n \nPACKAGE: LR*5.2*479 Feb 21, 2017 10:53 am \n 69.733,.01 SPECIMEN Modified\nPAGE 1\n--------------------------------------------------------------------------\n \n \nLR479 Calculated 18225928\nLR7OFAO Calculated 52676862\nLRAP Calculated 25554526\nLRAPKOE Calculated 175040482\nLRAPLG Calculated 12446427\nLRAPLG1 Calculated 181849693\n 69.733,.02 HIDE FROM Modified\nLROE Calculated 39978878\nLRUWLF Calculated 11960061\nLRXREF Calculated 76007577\n \n 9 Routines checked, 0 failed.\n \nSelect Installation <TEST ACCOUNT> Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*479 2/21/17@10:44:12\n => LR*5.2*479\n \n Description \nThis Distribution was loaded on Feb 21, 2017@10:44:12 with header of \n LR*5.2*479\n It consisted of the following Install(s):\n LR*5.2*479\nChecking Install for Package LR*5.2*479\nWill first run the Environment Check Routine, LR479\n \n \n \n --- Environment Check is Ok \n 69.733,.03 Description Modified \n \n \n Sending install loaded alert to mail group G.LMI\n \nInstall Questions for LR*5.2*479\n \nIncoming Files:\n \n \n 69.73 LR AP DIALOG CONFIG (Partial Definition)\n POSITION\nNote: You already have the 'LR AP DIALOG CONFIG' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? NO// \n \n \nWant KIDS to INHIBIT LOGONs during the install? NO// \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? NO// \n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\n 69.733,1 BUILDER BLOCK Modified\nEnter a '^' to abort the install.\n \nDEVICE: HOME// ;;9999 TELNET PORT\n \n \n--------------------------------------------------------------------------\n \n Install Started for LR*5.2*479 : \n Feb 21, 2017@10:55:15\n \n 69.7331,.02 INACTIVATE Modified\nBuild Distribution Date: Feb 17, 2017\n \n Installing Routines:\n Feb 21, 2017@10:55:15\n \n Running Pre-Install Routine: PRE^LR479\n \n \n *** Preinstall completed ***\n \nBlood Bank Review:\n 69.7331,.03 REQUIRED Modified\n Installing Data Dictionaries: \n Feb 21, 2017@10:55:15\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n Feb 21, 2017@10:55:16\n \n Running Post-Install Routine: POST^LR479\n \n 69.7331,.04 DEFAULT Modified\n \n Correcting Spelling Errors\n \n \n Correcting Builder Block Title Names\n \n \n Sending install completion alert to mail group G.LMI\n \n \n 69.7331,.05 Description Modified\n Removing Obsolete fields from LABORATORY TEST (#60) File\n \n \n Remove Obsolete fields from LAB ORDER ENTRY (#69) File\n \n \n Sending install completion alert to mail group G.LMI\n \n Updating Routine file...\n \n POSITION\n Updating KIDS files...\n \n LR*5.2*479 Installed. \n Feb 21, 2017@10:55:16\n \n Not a production UCI\n \n \nLR*5.2*479 \n \n 69.7331,1 VALUES Modified\n \nInstall Completed\n 69.73311,.01 VALUES Modified\n 69.73311,.02 SPECIAL Modified\n 69.733,2.1 COLLECTION Modified\n SAMPLE HIDE\n 69.733,2.2 COLLECTION Modified \n==================\n SAMPLE DEFAULT\n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*479 does not \n---------- ----- --------------------\nLR7OAP CPRS DIALOG MENU Modified\n MENU\nLR7OAP CPRS DIALOG PRINT Modified\n PRINT \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n\n
\n This patch addresses the following issue:\n alter or modify any software design safeguards or safety critical \n \n File Name Contents Retrieval Format \n ------------------ -------------------- ----------------\n LAB_MICRO_INTERFACE_RELEASE_1_0_DOCS.ZIP binary\n \n This zip file contains the following documents in both .docx and .pdf\n \n VLE Micro_Lab_Micro_Interface_Release_1.0_Technical_Manual\n VLE Micro_Lab_Micro_Interface_Release_1.0_User_Guide\n VLE Micro_Deployment_Installation_Roll Back_Back Out_Guide\n elements functions.\n \n The VistA Documentation Library (VDL) web site will also contain the \n above referenced documents. This website is usually updated within 1-3\n days of the patch release date. The VDL web address for Laboratory\n Universal Interface user documentation is:\n http://www.domain.ext/vdl/application.asp?appid=120\n \n Pre/Post Installation Overview\n ------------------------------\n There are no Pre/Post installation routines associated with this \n \n patch. \n \n Pre-Installation Instructions\n -----------------------------\n This patch may be installed with users on the system although it is\n recommended that it be installed during non-peak hours to minimize \n potential disruption to users. This patch should take less than one \n minute to install.\n \n NOTE: Kernel patches must be current on the target system to avoid \n RISK ANALYSIS: Changes made by patch LR*5.2*480 have no effect on Blood \n problems loading and/or installing this patch.\n \n \n ==================== Installation Instructions ====================\n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n Bank software functionality, therefore RISK is none.\n system. You now need to use KIDS to install the transport global.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. Use the 'Verify Checksum in Transport Global' option and verify\n that all routines have the correct checksums.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n If you wish to preserve a copy of the routines exported in this \n patch prior to installation, you should use the 'Backup a \n Transport Global' option at this time. You may also compare the\n routines in your production account to the routines in the patch\n by using the 'Compare a Transport Global to Current System'\n option.\n VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu \n and select the package 'LR*5.2*480.\n \n When Prompted "Want KIDS to INHIBIT LOGONs during the install? \n NO//", respond NO. \n \n When Prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//", respond NO.\n \n made, no specific validation requirements exist as a result of \n Post-Installation Instructions\n ------------------------------\n There are no post-installation tasks.\n installation of this patch.\n \n - Microbiology accession is being removed from the 'Incomplete \nRemedy Ticket Overview:\n ==========================\n N/A\n \nNew Service Requests (NSR)s):\n ==================\n N/A\n \n Participating Test Sites:\n =========================\n test status report (LRWRKINC)' option when a PRELIMINARY result is\n James A. Haley Veterans Hospital\n Iowa City VA Healthcare System\n Lexington VA Medical Center\n \n Problem:\n --------\n When releasing a microbiology preliminary report using the new \n Universal Interface release options the status of the accession was being\n set to complete and was then no longer available on the Incomplete Test\n Status list report.\n released when using the Universal Interface Microbiology release options.\n \n Resolution:\n -----------\n The patch modifies LRVR0 at ACCEPT+68 and adds the following three lines\n of code:\n ;\n ; If Lab UI interface then prompt user for accession test \n complete date /time in EC3^LRMIEDZ2 call.\n I LRINTYPE=1 S LRFIFO=0\n \n \n Routine: LRVR0\n \n \n Problem: \n --------\n When a retransmission of microbiology results are received the accepting \n of the retransmission values was causing the existing\n organism, comments and susceptibilities to be deleted. This is expected \n functionality when handling verified microbiology reports\n from external reference laboratories. \n \n \n However when handling result transmission from a Universal Interface \n microbiology instrument the user before the report is\n verified can enter additional information that needs to be preserved. \n \n Resolution: \n -----------\n The patch modifies the handling of existing results based on the type of \n interface. LEDI types of interfaces will continue to\n remove previous information prior to storing new information from the \n Blood Bank Review:\n reference laboratory. Universal Interfaces type interfaces\n will maintain existing information entered by Laboratory or received via \n prior transmissions and merge the new transmission with\n the existing data before presenting to lab user for review. \n \n Routine: LRVRMI2A modified labels N9A, N12A, N17 \n \n Routine: LRVRMI4A modified labels N3A, N6A, N6B\n \n \n ==================\n Software and Documentation Retrieval Instructions:\n ---------------------------------------------------- \n Software being released as a Packman message and/or documentation\n describing the new functionality introduced by this patch are available.\n \n The preferred method is to retrieve files from download.vista.domain.ext.\n This transmits the files from the first available server. Sites may \n also elect to retrieve files directly from a specific server. \n \n Sites may retrieve the software and/or documentation directly using \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*480 does not \n Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE \n directory at the following OI Field Offices:\n \n Albany: fo-albany.domain.ext\n Hines: fo-hines.domain.ext \n Salt Lake City: fo-slc.domain.ext\n \n Documentation can also be found on the VA Software Documentation Library \n at: http://www4.domain.ext/vdl/\n \n\n
\n \nBlood Bank Review:\nProblem:\n--------\n With the release of patch LR*5.2*479 the second line of the routine\n LRAPKOE mistakenly contained a reference to patch LR*5.2*469.\n \nResolution:\n-----------\n This patch will correct the second line of the routine as follows:\n Second line as released with LR*5.2*479:\n ;;5.2;LAB SERVICE;**462,469,479**;Sep 27, 1994;Build 8\n==================\n \n Second line after the install of LR*5.2*483:\n ;;5.2;LAB SERVICE;**462,479,483**;Sep 27, 1994;\n \n Routine: LRAPKOE\n \n Software Retrieval Instructions:\n ------------------------------------- \n Software will be released via a PackMan message. \n \n \n \nPatch Installation:\n \n \n Pre/Post Installation Overview:\n -------------------------------\n N/A \n \n Pre-Installation Instructions:\n ------------------------------\n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*483 does not \n N/A\n \n Installation Instructions:\n --------------------------\n contain any changes to the VISTA BLOOD BANK Software as defined by \n ProPath standard titled: BBM Team Review of VistA Patches.\n \n RISK ANALYSIS: Changes made by patch LR*5.2*483 have no effect on Blood \n Bank software functionality, therefore RISK is none.\n \nThis patch contains only a correction to the second line of the routine \n VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \n made, no specific validation requirements exist as a result of \n installation of this patch.\n \nPatch Components:\n--------------------------\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\nLRAPKOE. The second line erroneously listed patch LR*5.2*469 when it was \n------------------ ------------------- --------------------\nN/A\n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \nreleased with LR*5.2*479. This reference to LR*5.2*469 will be removed as\n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nLRAPKOE was NOT released as part of LR*5.2*469. There are no other changes\nOption Name Type New/Modified/Deleted\n---------- ----- --------------------\nN/A\n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \nN/A\nto the functionality in LRAPKOE.\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \n \nTemplates Associated:\n \n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ----- ------------------ --------------------\nN/A\n \n \nAdditional Information:\n \nN/A \n \nPatch LR*5.2*479 should be installed on schedule.\n \nNew Service Requests (NSRs):\n-------------------------------------------- \nN/A\n \nPatient Safety Issues (PSIs):\n---------------------------------------\nN/A\n \n \n \nCA SDM Ticket(s) & Overview:\n--------------------------------------------\n \nN/A\n \n \nTest Sites:\n---------------\nN/A \n \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nFixes the undefined in LRWU5.\n\n
\nPlease see FORUM for full patch description and installation instructions.\n\n
\nThis patch addresses one (1) VistA Laboratory Anatomic Pathology issue:\n \nI13556053FY17: Multiple orders associated with one Anatomic Pathology\n accession\n\n
\nThis patch addresses two (2) VistA Laboratory issues related to override \nreference ranges:\n \n1. Override Reference Ranges Not Displaying on Reports\n2. Option LRENTER Prompt Answer of "YES" Treated as "NO"\n\n
\nThis is a general maintenance patch for the laboratory\npackage by the Vista Maintenance team that addresses an\nissue with the search criteria associated with the Howdy\nPatient Wait Time report.\n \nASSOCIATED SERVICE DESK TICKET:\n==============================\n1. R11469217FY17 - Entries outside entered search criteria\n included on Patient Wait Time report\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses two (2) VistA Laboratory issues related to the \ndeletion of Howdy duplicate test orders:\n \n1. Duplicate test is deleted in VistA but active in CPRS\n2. Error occurs when orders have more than one duplicate test\n\n
\nThis patch addresses three (3) VistA Laboratory issues related to \n3. The Lab Order Entry (#69) file Lab Arrival Date/Time (#20) field is \nerroneously set during collection list generation.\nphlebotomy collection list logic:\n \n1. Test orders that roll over from one collection list to another may \nappear to be ordered twice in CPRS even though they are only ordered once.\n \n2. Merged orders created by collection list generation sometimes do not \nhave correct CPRS start date/times.\n \n\n
\nThis patch addresses one (1) VistA Laboratory issue related to Interim \nReport option description updates and an update to the VistA Laboratory\nUser Manual.\n\n
\nThis patch addresses one (1) VistA Laboratory issue related to a software \nerror that occurs during Anatomic Pathology data entry of inactive CPT \ncodes which have replacement CPT codes.\n\n
\nThis patch addresses two (2) VistA Laboratory issues:\n \n1) LEDI Microbiology Results Endless Loop Issue\n2) Lapsed/Canceled Orders and Added Test Issue\n\n
\nNote: Patch LR*5.2*105 Must be installed BEFORE this patch is loaded.\nNOIS # SEP-0496-60804\nReporting Site: Sepulveda, Ca\nTesting Site: Sepulveda, Ca\n \nLRCAPAM1 routine corrects BLOOD INVENTORY workload not being counted in\nNon-Patient category for LMIP reports.\n \nLRCAPFDS routine corrects NULL SUBSCRIPT error occurs when the user\nselects a WKLD CODE LAB SECTION that does not have any WKLD CODES\nassigned.\n \nNOIS # DAY-0496-40011\nReporting Site: Dayton, OH\nTest Site(s) Long Beach, CA\n \nROUTINE SUMMARY:\n=================\n \n Routine Name Before Patch After Patch Patch List\nLRCAPAM1 14052207 14337228 105,119\nLRCAPAM3 12790683 13513963 42,119\nPatch Description:\nLRCAPAM4 12581527 13198299 42,105,119\nLRCAPFDS 6562403 7918114 105,119\nLRCAPMA1 5952535 5952535 105,119\nLRCAPV2 8714919 8714919 105,119\n \nOptions Effected by Patch:\n \nEdit or Print WKLD CODES [LR WKLD CODE EDIT PRINT]\nPHASE 1: Move data from 64.1 to 67.9. [LR WKLD LMIP 1]\nPHASE 3: Print of data to be sent to NDB. [LR WKLD LMIP 3]\nRoutine LRCAPV2 and LRCAPMA1 were exported in patch LR*5.2*105 with\nPHASE 4: Create E-mail message for NDB. [LR WKLD LMIP 4]\n \nInstallation Instructions:\n==================\n \nNote: Patch LR*5.2*105 MUST be installed before this patch is installed.\nThis patch also contains patches to patch LR*5.2*105.\n \n1. User may remain on the system.\n2. No options need be placed out of order.\nincorrect second lines.\n3. Install patch during non-peak hours.\n4. Laboratory specimens should not accessioned or verified during\n installation of the patch.\n5. Install this patch using Kernel Installation and Distribution System\n (KIDS).\n \nNOIS List\nNOIS # DAY-0496-40011\nNOIS # SEP-0496-60804\n \nRoutines LRCAPAM3 and LRCAPAM4 corrects consolidated institutions Phase 3\nand Phase 4 reports not recognizing site numbers which have alpha\ncharacters as apart of the site number.\n\n
\nSee National Patch Module for details.\n\n
\nThis patch addresses two (2) issues:\n \n1. Accessions which have been merged to other accessions or marked as \n "not performed" may be resulted even though these accessions are\n cancelled.\n \n2. Anatomic Pathology labels do not print while using the option \n REFERRAL PATIENT MULTI-PURPOSE option for accessioning orders.\n\n
\nThis patch addresses one (1) VistA Laboratory issue related to the \nprocessing of workload transactions received from VBECS (VistA Blood \nEstablishment Computer Software). Incorrect Lab Order Entry (#69) file \nentries are sometimes created.\n\n
\nThe patch addresses two (2) issues:\n parameters used in the call are improper. \n \n1. When the legacy CPRS List Manager option CPRS Ward Clerk\n Menu [OR OR/RR MENU WARD CLERK] is used to call Lab \n package routines (SET1^LRGEN) to display Lab Results by \n Test, a program error (UNDEFINED) is encountered.\n \n2. The VistA routine ^LRX performs a FileMan database server\n call ($$GET1^DID) to retrieve a global reference. The \n\n
\nThe patch addresses two (2) issues:\n unrelease a verified provisional report, the prompt to "Unrelease\n Report" is not displayed.\n \n1. When a user goes to the Multipurpose accessioning option [LRQUICK] \n in the Accessioning menu option [LR IN], the variable LRORDR may \n still be set and causes the accessioning routine to erroneously \n assume that specimen collection will be by Ward Collect.\n \n2. When Anatomic Pathology Electronic Signatures are turned off and \n the Verify/release reports, anat path [LRAPR] option is selected to\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses two (2) VistA Laboratory issues:\n(1) Statistical reports might list inaccurate information for monthly \naccession areas.\n(2) Inactive providers are displayed during Anatomic Pathology Log-In.\n\n
\nThis build exports changes to the field #1 of the Execute Code \nfile (#62.07) and affects the option RB Results Entry (Batch) \nfor Microbiology. \nAlso a new FileMan function is exported for reporting on lab \nresults for patients with a given specimen type, a lab test, and looking\nback over a specified number of days.\nThe Forum patch description offers more details and the NSRs involved.\n\n
\nThis patch addresses one (1) issue in the Lab package:\n \nPrevent error which can occur when incorrect facility identifier is \nreceived from the Point of Care (POC) interface.\n\n
\nSee National Patch Module for details.\n\n
\nThere is a problem of unknown origin where 7 nines (9999999) are getting\nstored in the LAB DATA file (# 63), the ACCESSION file (# 68),\nand the Cumulative Reports Global (^LAC("LRAC"). This patch replaces the\nthese erroneous data nodes with the laboratory inverse date. Initial search\nof the database is extensive and will take up to two hours. This is a one\ntime occurrence. A background task should be scheduled to run daily to clean\nup any new occurrences.\n\n\n\nNOTIFY TIER 2 OF FILE 60 UNDEF IF PRESENT\n\n
\nThe patch addresses one (1) issue:\n \n1. When a lab panel (cosmic) test is set up so the atomic tests in \n the panel split to separate accession areas (e.g.: one Chemistry\n and one Toxicology), results of the ordered panel test do not \n display all of the results of the atomic tests in the panel when \n viewed in CPRS from the Orders tab or from the Cover Sheet.\n\n
\nThis patch addresses two (2) VistA Laboratory issues related to accession \nlabels being skipped or the printing process generating duplicate labels \nendlessly as well as results being verified when the user has no initials \non file in the New Person (#200) file.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses the following one (1) VistA Laboratory issue: When a\nLEDI Host facility adds a new lab test to an accessioned order shipped \nfrom a Collection facility the UID is improperly assigned with the \nordering site's UID instead of the host site's UID. \n\n
\nThe patch addresses four (4) issues:\n2. When USING AP Log-in, anat path [option LRAPLG], an <UNDEFINED> error\n occurs in the NEXT subroutine of routine LRAPKOE when logging in a \n case for a deceased veteran ordered in CPRS.\n \n3. In AP Log-in, anat path [option LRAPLG], the PATHOLOGIST prompt is a \n required entry. The pathologist who will read the case is usually \n not known at the time the case is logged into the laboratory. The \n process should be modified to make entry of PATHOLOGIST optional.\n \n4. The routine (LRAPKOE) that processes Anatomic Pathology orders entered\n \n in CPRS needs to be modified to call VistA Imaging to add the case to\n the MAG PATH CASELIST file (#2005.42) to support Telepathology and to\n generate the HL7 message that is sent to digital pathology systems.\n1. Emerging Pathogen Initiative (EPI) data is collected in VistA and \n forwarded to the Austin Information Technology Center (AITC) for\n national roll-up monthly. Part of the collected data has to do with\n Clinical Reminders related to Hepatitis C. The Clinical Reminder data\n is formatted into the DSP segment of a HL7 record for delivery to the\n AITC. The data is currently being formatted improperly.\n \n\n
\nThis patch will update the DESCRIPTION field (#6) in file #62.07 with the\nwith LRSPEC=360.\nWhen the patch is installed, it saves the existing DESCRIPTION field \ncontents and the Execute codes in the installation log for later review \nif desired. The log can be used to manually restore local changes found\nand not restored by this patch.\n \nThis patch also modifies the routine LRMISTF by adding the \npreliminary comment fields for Bacteriology, TB Bacteriology, and \nMycology with corresponding expansion codes so that the canned messages \nfrom the LAB DESCRIPTIONS file (#62.5) appear during Results Entry \nPreliminary Comments field for Bacteriology, TB Bacteriology, and\n(Batch).\nMycology.\nAlso, it will clean up obsolete codes in the EXECUTE CODE field #1 of\nthe EXECUTE CODE file (#62.07), that were discovered after the release of\nLR*5.2*476. The obsolete execute codes were not introduced by LR*5.2*476\nbecause it was found that many sites have the codes before LR*5.2*476\nwas installed. In a nutshell, Mycology will be cleaned up of obsolete\nfield #19.2; in Bacteriology, the expression LRSPEC=68 will be replaced\n\n
\nR18600337FY18: Missing Anatomic Pathology Alerts\n----------\n \nThe root cause of this issue is not yet known. In the meantime, this \npatch provides an option which will search for missing Anatomic\nPathology alerts as well as other issues known to occur along with \nmissing alerts such as fields in the ORDERS (#100) file which are set \nincorrectly.\n \nRefer to the FORUM patch description for detailed information on alerts \nand MailMan messages which are generated after the search option \nR19264009FY18 (d)\ncompletes.\n \nProblem:\n-------\n \nAlerts might not be generated after Anatomic Pathology cases are verified.\n \nResolution: \n\n
\nProblem with option Results entry (batch) [LRMISTUF]\n\n
\nBuild Description LR*5.2*169\n companion DSS patch ECX*2*26) extract utilizes the LAB DATA file (#63)\n and does not require the LAB ORDER ENTRY file (#69) or the ACCESSION\n file (#68). Implementation of the DSS LAR Application Programmer\n Interface (API) DOES require that the Laboratory Information Manager\n (LIM) link the 12 DSS LAR tests in the DSS LAB TESTS file (#727.2) to\n all local corresponding tests in the LABORATORY TEST file (#60). \n \n Linking of DSS clinical tests has NO EFFECT ON WORKLOAD DATA CAPTURE.\n You should link the atomic test in LABORATORY TEST (#60) file that is\n used to report the result. \n \n \n For DSS purposes, these corresponding laboratory tests must be linked\n to the WKLD CODE file (#64) and must be individually orderable (atomic)\n tests. The link between LABORATORY TEST file (#60) and the WKLD CODE\n file (#64) is accomplished by assigning a WKLD CODE. The NATIONAL\n NATIONAL VA LAB CODE field (#64) of the LABORATORY TEST file (#60)\n provides this linkage.\n \n The NATIONAL VA LAB CODE field (#64) is not used by LMIP data capture\n software and will not effect LMIP counts. Patch LR*5.2*127 provided a\nFunctionality:\n menu, National Laboratory File [LR7O 60-64], to link the LABORATORY\n TEST file (#60) to the WKLD CODE file (#64). \n \n NOTE: When linking the DSS LAR tests to local laboratory tests, only\n atomic Laboratory Tests are selectable. Panel tests are NOT permitted to\n be linked to any DSS survey test.\n \n The DSS LAR extract also requires the LIM to identify all specimens\n that are derived from blood or urine, i.e., plasma, serum, clean\n catch. The LAB DSS LAR API will use these specimens to screen patient's\n This patch corrects the <UNDEF> error at TEST+3^LRCAPDAR ^(64).\n results in the LAB DATA file (#63) and extract information for the 12\n DSS tests.\n \n The local DSS Coordinator will seek the LIM's assistance to identify\n tests and specimens. This should require less than 30 minutes to\n complete. The LIM is not required to actually initiate the data\n extraction. This step will be completed by the local DSS Coordinator.\n The program has been modified to accept the new file structure put in\n place by the Decision Support System Extracts (DSS) patch ECX*2*18.\n \n Implementation:\n The DSS Laboratory Results (LAR) EXTRACT (patch LR*5.2*169 and the\n\n
\nThis patch addresses one (1) issue:\n \nAnatomic Pathology Log-In does not require that the patient's sex must \nmatch the SEX SPECIFIC (#2.5) field in the TOPOGRAPHY FIELD (#61) file for\nspecimens (if the sex specific field is defined).\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nLAB TEST NOT DISPLAYED IN CPRS MOST RECENT VIEW\n\n
\nThis patch addresses one (1) VistA Laboratory issue:\n \nThe status for a lab order in CPRS displays as "active" when the status\nshould display as "complete".\n\n
\nCANCELED LAB TEST PROBLEM\n\n
\nThis patch will prevent an error in CPRS that is occuring when a user is \nplacing a lab test order that has had a site/specimen deleted from the \nlab test setup.\n\n
\nMost Recent report in CPRS buttons greyed out\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThe patch addresses three (3) issues: \n2. Data corruption might occur in the data dictionary for file 63.04 if \n one or more users are adding or editing data names for Laboratory\n tests.\n \n3. A VistA software error might be generated during execution of option \n "Group verify (EA, EL, EW)" if results are being printed.\n \n1. When a lab panel (cosmic) test is set up so the atomic tests in the \n panel split to separate accession areas (e.g. one Chemistry and one\n Toxicology), results of the ordered panel test do not display all of\n the results of the atomic tests in the panel when viewed in the \n Computerized Patient Record System (CPRS) from the Orders tab or \n from the Cover Sheet.\n \n\n
\nThis patch addresses one (1) issue:\n \nA Social Work package Integration Control Registration (ICR) of 1528 is \nbeing retired.\n\n
\nThis patch contains a Description of problems, their associated Risk\nAnalysis, routines, input templates and DD's for the VistA Blood Bank\nsoftware. It is accompanied by two additional INFORMATION ONLY patches,\nLR*5.2*92 (Validation Scenarios) and LR*5.2*147 (Documentation Changes).\n \nSee the individual patch messages from the Forum Patch Module for complete\ninformation on these patches:\n\n
\nThe patch addresses one (1) issue:\n \n1. When the Itemized routine lab collection [LRPHITEM] option is used,\n a previously deleted order marked as Not Performed can be entered\n as collected. This sets the Lab Arrival Time (#69.01,20) in the\n LAB ORDER ENTRY file (#69) for the accession to the curent system\n time even when the order was cancelled.\n\n
\nLRCONJAM AND CUMULATIVE HEADER ISSUES\n\n
\nThe patch addresses one (1) issue: \n \n1. Patch LR*5.2*519 dealt with the proper display of lab results on\n panels with multiple ACCESSION AREAs. The new code in the patch \n revealed that the LAB DATA FILE (#63) at some sites may contain \n orphan zero nodes. These zero nodes are global records (i.e.: \n ^LR(D0,CH,D1,0)) that have no results. Encountering these orphan\n nodes in the database when rendering results for the same patient\n causes a SUBSCRIPT error.\n\n
\nThis patch addresses three (3) issues:\n option might delete the "not performed" status of the test.\n \n1. An atomic test which is a component of a panel might appear on the \n pending list even though the test is verified.\n \n2. A lab panel might appear on the pending list even though all components\n have been verified.\n \n3. If a test is marked as "not performed", the LRVR result verification \n\n
\nThis patch addresses two (2) issues:\n \n1. Microbiology reports might not display the accurate status of a test. \n2. Unverified Microbiology results are visible in CPRS reports during\n results verification sessions.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch is being released in conjunction with VBEC 2.3.2 Rev F. \nItems addressed in VBECS 2.3.2 Rev F are listed in the VistA Blood \n the components of the KIDS build.\n ii. Compare Transport Global to Current System - This option\n will allow you to view all changes that will be made when\n this patch is installed. It compares all of the components\n of this patch, such as routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the patch to\n install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\nEstablishment Computer Software (VBECS) 2.3.2 Rev F Release Notes.\n of Install? NO//', answer No\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//', answer No\n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? NO//', answer No\n \nPost-Installation Instructions:\n N/A\n \n \nBack-Out/Roll Back Plan:\n------------------------\n This patch consists of one routine. During the VistA Installation \n Procedure the installer should back up the modified routines by the\n use of the 'Backup a Transport Global' action (step 2B in\n the Installations Instructions).\n \n If rollback/backout is required, the installer can restore the routines\n using the MailMan message that were saved prior to installing the\nAssociated ticket(s):\n patch.\n \n If assistance is needed to rollback/backout the patch, please log a\n Service Now ticket.\n=====================\n N/A\n \nAssociated NSR(s):\n==================\n N/A\n \n \nPatient Safety Issues (PSIs):\n============================\n N/A\n \nParticipating Test Sites:\n=========================\n \nTBD\n \nA full description of patch changes and implementation process are \nDefect Tracking System Ticket(s) & Overview:\n============================================\n \n N/A\n \nAdditional Information:\n-----------------------\n \nBlood Bank Team Coordination:\n-----------------------------\nincluded in the VBECS 2.3.2 Rev F Release Notes.\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*535 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by \nProPath standard titled: BBM Team Review of VistA Patches.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*535 does not \nalter or modify any software design safeguards or safety critical \nelements functions.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*535 have no adverse effect on \nBlood Bank software functionality, therefore RISK is none.\n \n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nmade, no specific validation requirements exist as a result of \ninstallation of this patch.\n \n \nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\n \nDocumentation describing the new functionality introduced by this patch \nThe Test and Production accounts will be installed separately. There is \nis available on the VA Software Documentation Library at:\nhttp://www.domain.ext/vdl/application.asp?appid=182\n \nRefer to the VBECS 2.3.2 Rev F Release Notes for a list of the user \ndocumentation associated with this revision letter patch.\n \nAdditional VBECS information can be accessed on the VBECS SharePoint site \nat: https://dvagov.sharepoint.com/sites/oitepmovbecs\n \n \nno downtime associated with this patch installation. Refer to the VBECS \nPatch Installation:\n-------------------\n \nPre-Installation Instructions:\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \nNo options need to be disabled during installation.\n2.3.2 Rev F Release Notes for further installation details.\n \n \nInstallation Instructions:\n \n 1. Choose the PackMan message containing this build. Then select the\n INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n 2. From the Kernel Installation and Distribution System Menu, select the\n Installation Menu. From this menu, \n \n \n A. Select the Verify Checksums in Transport Global option to confirm \n the integrity of the routines that are in the transport global.\n When prompted for the INSTALL NAME enter the patch name LR*5.2*535.\n \n B. Select the Backup a Transport Global option to create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates. \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow you to view\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses two (2) issues:\n \n1. A panel might remain on the "Incomplete test status list" if it was \n ordered twice as Lab Collect.\n \n2. Building a Load/Worklist for a yearly accession area will cause a \n corrupted entry in the ACCESSION (#68) file.\n\n
\nThis patch addresses four (4) issues:\n test.\n \n4. The "NIGHTLY WKLD CODE CHECK REPORT" contains orders which have been \n purged from the environment.\n \n1. The CPRS status of an order might not be correct when panel \n components are deleted using option LRTSTOUT.\n \n2. Service correction comments are not displaying on canceled orders.\n \n3. A VistA software error might occur during background processing \n involving the LABORATORY TEST (#60) file due to an incompletely filed\n\n
\nFixes undefined for the option Reprint cumulative on a given patient [LRAC PT].\n\n\n
\nThis patch addresses the following issue:\n \nAny provider who is defined with the "MOHS" person class should be allowed\nto electronically sign Anatomic Pathology cases.\n\n
\nThis patch addresses one (1) issue:\nWorkload is not captured for Class I Microbiology interfaces.\n\n
\nThis patch addresses four (4) issues:\n4. If a session times out while entering Microbiology sensitivity results,\n the user may not be aware that the sensitivity results were not stored.\n \n1. Microbiology reports might not display the accurate status of a test. \n \n2. Unverified Microbiology results are visible in CPRS reports.\n \n3. VistA reports might not list an accurate status for Microbiology \n accessions.\n \n\n
\nBackup of LR*5.2*542 on May 04, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nBackup of LR*5.2*543 on May 25, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issues:\n \n1. CPRS orderable items might be defined for non-existent Laboratory tests.\n \n2. Canceled Microbiology accessions might appear on Laboratory statistical\n reports as pending and not canceled.\n\n
\nBackup of LR*5.2*545 on Jun 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issues:\n \nIf a test is canceled from an accession or merged to another accession\nafter the accession has been resulted on an instrument, it is possible to\nverify a result on the canceled or merged test using option "Enter/verify\ndata (auto instrument) (LRVR)".\n\n
\nThis patch updates the contents of the LR AP DIALOG CONFIG File (#69.73)\nin preparation for Anatomic Pathology order dialogs in CPRS v32A.\n\n
\nWorkload Archiving Patch\n and the Purge Lab Monthly Workloads file 67.9 [LRAR PURGE 67.9] option \n queued options. \n 2) The ARCHIVE TASK NUMBER field (#18) in the LAB ARCHIVAL ACTIVITY file\n (#95.11) is now deleted upon completion of the task. The Write Data\n to Off-line Media options, [LRAR WRITE MEDIA 67.99999] and [LRAR WRITE\n MEDIA 64.19999], then check for data in this field as a test of\n completion of archive. \n 3) For information: \n When archiving the LAB MONTHLY WORKLOADS file (#67.9), the date range \n selected for archiving must be in entire month chunks due to the file \n\n structure of File 67.9.\n \n For instance if you select a date range from March 1, 1994 to\n April 1,1994, you will archive the entire months of March and April. \n \n This patch to the Laboratory package does not contain any changes to the VISTA\n BLOOD BANK Software as defined by VHA DIRECTIVE 97-033 titled VISTA BLOOD BANK\n SOFTWARE VERSION 5.2. \n \n Reference NOIS: HIN-0297-41349 \n *************************NOTE************************************* \n \n Reporting Site: Hines, IL \n \n Test Site(s): Hines, IL \n Minneapolis, MN \n \n Patches LR*5.2*59 and LR*5.2*150 MUST be installed prior to \n installing this patch. \n \n ******************************************************************* \n\n 1) This patch makes the Purge Wkld Data file 64.1 [LRAR PURGE 64.1] option \n\n
\nBackup of LR*5.2*541 on Jul 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issues:\n \n1. An error will occur when canceling a component test in partially \n verified panels on referral orders.\n2. Some workflows for verification of Microbiology interfaced results will\n cause the CPRS order status to remain at "active" instead of changing\n to "complete".\n3. An invalid collection date/time could be entered when manually \n accessioning an order.\n\n
\nDefect Tracking System Ticket(s) & Overview:\n Two errors are recurring and preventing microbiology reports\n from being generated:\n - If the zero node is missing in this sub-file, an undefined \n error occurs in LST+3.\n - If the organism pointer to file #61.2 is null in the first \n piece of the zero node, a subscript error occurs at the end \n of LST+4\n \n Resolution:\n ----------\n===========================================\n For sites to be able to find and report Corrupted Organism nodes \n to their regional support group, an update to the nightly LAB \n Cleanup routine is implemented. This update will search for \n Corrupted Organism nodes and send a mailman message to the LMI \n mailman group.\n \n1. INC17480746 Frequent M Errors at multiple sites: LST^LR7OSMZ2\n \n Problem:\n -------\n We are seeing errors in LST^LR7OSMZ2 at multiple sites due to \n Corrupted Organism nodes in the MI section of the ^LR global. \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses the following issues:\n displaying any results during the time that the Laboratory is editing\n the results. \n \n3. This patch also includes a documentation update for another issue.\n No code changes are required for that issue.\n \n1. Laboratory users may not be aware that accessing a previously verified \n accession in Microbiology results entry causes the "RPT DATE APPROVED" \n field to be removed. If the users exit without entering a new "RPT DATE\n APPROVED", the results are not viewable in CPRS. \n \n2. It has been causing confusion for physicians and other users when a \n Microbiology report previously contained results but is now not\n\n
\nThis patch addresses the following issues:\n \n3. Accessions which roll over from the previous day to "today" will not \n build to a Load/Worklist if the HOLD-OVER SORT URGENCY (#300) field in \n the LABORATORY SITE (#69.9) file is defined as "zero".\n \n1. Non-numeric data entries may be defined as minimum and maximum values\n as well as number of decimal places for numeric data names.\n \n2. An error might occur during generation of the Epidemiology report if\n the LAB OOS encounter is edited for the addition of one or more CPT\n codes. In addition, a logic error was found during testing of this \n patch for the date range being searched.\n\n
\nDefect Tracking System Ticket(s) & Overview:\nSCAN TIME, TIME SPECIMEN COLLECTED and TIME SCANED INTO LAB from \napproximately 10 years ago. Entries in the HOWDY SPECIMEN TIMES BY UID \nfile #69.87 are never deleted. After 10 years, when lab accessions (UIDs) \nare no longer unique, data for current UIDs can no longer be added to \nfile #69.87, because the software checks for the presence of the UID and \ndoes not allow duplicates.\n \nThe site that reported the issue is using the option LRHY TRACK \nCOLLECTION to produce a report of patient specimens collected via Howdy. \nThat report retrieves data from the HOWDY SPECIMEN TIMES BY UID file \n===========================================\n(#69.87). The site gave several examples of accessions (UIDs) that are \nshowing data from 2011. Lab accession numbers (UIDs) are only unique for \n10 years. Many of the entries in this site's file #69.87 are > 9 years \nold, and thus have UIDs that are no longer unique and are the source of \nthis data error on the report.\n \nThe option that creates the entries in file #69.87 is LRHY PHLEBOTOMY \nLOG. The routine for that option checks to see if the UID entered in the \noption is already in file #69.87. If it is, the option does not add the \nUID to the file again. Because the only UID from 10 years ago is in the \n \nfile, the current UID cannot be added, and this is the real source of the \nproblem.\n \nThere should really be a utility added, perhaps called from LRNIGHT, that \nchecks file #69.87 for entries >9 years old and deletes those entries \nfrom the file. Note that this will eventually affect all VA sites that \nuse Howdy, and specifically those that use the LRHY PHLEBOTOMY LOG option.\n \n \n Resolution:\n1. INC20231002 - CTX Incorrect Information in VistA Track Collection\n ----------\nLogic is added to the NIGHTLY LAB CLEANUP process. The routine LRNIGHT \nwill run LRHOWDY^LRWU9A in the background. LRHOWDY^LRWU9A will delete \nrecords that are more than 9 years old from file #69.87.\n \n \n Technical Resolution:\n ---------------------\nWithin the SUBTASKS section of routine LRNIGHT, code is added to job off \nLRHOWDY^LRWU9A to background processing. \n \n \nEntry point LRHOWDY is added to routine LRWU9A. \n \nLRHOWDY loops through the SCAN index of file #69.87 and deletes records \nthat are greater than 9 years old, time is not considered so a record \nthat was scanned anytime today exactly 9 years ago is not deleted, the \nrecord must have been scanned over 9 years ago to be purged.\n Problem:\n -------\nIncorrect information is being populated in the VistA Track Collection on \nseveral patients. It is displaying incorrect information for the WALK-UP \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThe patch addresses one (1) issue: \n \n1. When using the Lab liaison menu option Add a new data name \n [LRWU5] or Modify an existing data name [LRWU6], one cannot enter a\n value less than one (1) at the Minimum value query. It displays the\n Help text (The smallest result value) and represents the Minimum value\n query.\n\n
\nThis patch addresses the following issue:\n \nIf duplicate VBECS orders are ordered as "Lab Collect", the process of \nrejecting the duplicate order in VBECS and completing the other order \nwill cause the completed order to not have a status of "complete" in \nVistA and CPRS.\n\n
\nAt Open M sites a Merge of a global into itself causes an error. A check has\n Reference NOIS: PRE-0797-60641\n Reporting Sites: Prescott, AZ\n Testing Sites: Prescott, AZ\n ROUTINE SUMMARY:\n =================\n \n The second line of the routine now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \nbeen added to make sure the global values are different before doing the merge.\n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- -----------\n LROR6A 15782769 16122062 24,100,128,186\n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your\n system.\n \n 2. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n \n Backup a Transport Global\n 4. Users may remain on the system, but installation should be done\n at off peak hours.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak hours\n and less than 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory space.\n 8. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'LR*5.2*186' and proceed\n with the install.\nThis patch should also be installed at non-Open M sites, even though they are\n 9. If any routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\nnot getting the error.\n This patch to the Laboratory package does not contain any changes to the\n VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 97-033 titled VISTA\n BLOOD BANK SOFTWARE VERSION 5.2.\n\n
\nThe patch addresses one (1) issue: \n \n1. When using auto-verification and not releasing all tests on a \npanel at the same time, the statement "ALL COMPLETED" Is not\nDISPLAYED when using the LOOKUP ACCESSION option [LR LOOKUP \nACCESSION]. This omission does not happen if all results are\nreleased at once, it is only a problem when some results are\nauto verified and then the rest released at a later time.\n\n
\nThis patch addresses two issues:\n \n2. The option "Set a new starting accession number" does not set a new \n starting number for monthly accession areas.\n \n1. An invalid "seconds" value for an accession's collection date/time \n might be stored when using option "Accessioning tests ordered by ward \n order entry (LROE)". This has caused problems downstream when \n transmitting information to Corporate Data Warehouse (CDW.). Research\n of the issue uncovered the fact that when used a certain way, the\n option will add ten seconds to the collection date/time entered by the\n user.\n\n
\nThis patch addresses one issue:\n \nA Microbiology result status might be marked as "completed" when it is \nnot complete.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses one issue:\n \nA test might not display a status of "Results received" at a LEDI\ncollecting site after results have been received.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch addresses two issues:\n \n1. The entry for "TRIMETHOPRIM/SULFAMETHOXAZOLE" is incorrectly spelled as\n "TRIMETHAPRIM/SULFAMETHOXAZOLE" in the ORGANISM SUB-FIELD FILE (#63.3) \n file as well as in the ANTIMICROBIAL SUSCEPTIBILITY (#62.06) file.\n \n2. The Lookup Accession report will show an inaccurate status for a panel \n if the full accession is specified and if the panel was not partially\n verified on the original accession date.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch along with LA*5.2*104 addresses one issue:\n \nVistA Laboratory (POC) Point of Care interface logic might incorrectly \ndetermine the reporting facility for POC results.\n\n
\nThis patch fixes problems encountered when user enter comments on\nlab specimens during accessioning.\n\n
\nMultidivisional sites have requested the ability to fine-tune the list of \norderable lab tests displayed to a user. This patch adds a flag field to \nthe ACCESSION AREA multiple-valued field (#6) in the LABORATORY TEST file \n(#60) that when set for an accession area at a site, will block users \nsigned in to that site from seeing that test in the list of orderable \nitems.\n \nRefer to the patch description for full details.\n\n
\nThis patch addresses three issues:\n which contain at least one profile, an error might occur.\n \n1. The status in CPRS might be incorrect for one or more tests if\n accessions were merged.\n \n2. The Incomplete test status report (LRWRKINC) might display inaccurate \n information if the user specified a past date instead of today.\n \n3. When merging is performed on an Emergency Room patient's accessions \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\n1. INC31264131 - Option LROS (Order/test status) Report Issue with \n Partially Verified.\n\n
\nThe patch addresses one (1) issue: \nthe order still needs to be collected and processed.\n \nWhen the order is accessioned by Howdy, no error message is displayed on \nthe screen and there is no way for the lab to know the order was needed.\n \n1. In certain situations, tests that are showing as collected do not \nhave an accession number. This happens when the user that accessions the \ntest is logged into a division that is not defined in the LAB TEST FILE \n(#60) for that test with an ACCESSION AREA. When the user uses the option \nAccession tests ordered by ward order entry [LROE] there is a message \nthat displays, but it is easily missed by the user causing lab tests to \nbe presumed accessioned by the provider when the lab does not know that \n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease review FORUM's Patch Module description and \ninstallation instructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n \nPlease note that patch LA*5.2*105 is a companion patch to this patch.\n\n
\nThis patch corrects a variety of problems with Anatomic Pathology reports.\n See the Description on the Forum patch module for full information on\nthis patch.\n\n
\nPlease review FORUM's Patch Module description and \ninstallation instructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and \ninstallation instructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nThis patch fixes the undefined error that occurs when non package\n(X) variable is killed by VADPT.\n\n\n
\nARCHIVE NOT FINDING A PATIENT\n\n
\nPlease refer to the 'LABORATORY ELECTRONIC DATA INTERCHANGE (LEDI) Patch\nLA*5.2*27 and patch LR*5.2*153 INSTALLATION GUIDE.\n\n
\n Reference NOIS: None\n ============\n 4) At the prompt DEVICE: select a valid printer name or print the report\n to the screen.\n \n Examine the report to verify that all instances of the date are\n formatted to include all four digits of the year.\n \n Repeat steps 1 through 4 above with the following exceptions.\n During step 2) answer NO.\n During step 3) answer NO.\n \n In accordance with the evaluation performed using established policies\n Examine the report to verify that all instances of the date are\n formatted to include all four digits of the year.\n \n \n OPTION: Blood bank consultation reports [LRBLCN]\n \n This option is available for those sites wishing to use VistA to \n generate a Chartable Consultative report on patients who after Blood\n Bank serological testing are found to have either an allo-antibody or a\n positive Direct Coombs. If this option is used at a site, then a sample\n and VHA Directive 97-033, documented on the patch change control summary\n report should be printed for each type of Consultative report generated\n and then reviewed to determine that all dates print using a 4 digit year\n format. This will need to be completed by a user with the LRBLSUPER key\n performing the following steps:\n \n 1) Select the option Blood bank consultation reports [LRBLCN].\n 2) At the prompt Select CONSULTATION: type in a "?". You will see a\n listing of each type of consultative report used at your facility.\n ANTIBODY or DIRECT COOMBS TEST REPORT.\n 3) At the prompt Select Patient Name: choose a name of a patient that\n and consultation with the FDA on 3/3/1998, this patch does not need to be\n is known to have an identified allo antibody or positive Direct\n Coombs test, whichever is appropriate.\n 4) At the prompt DEVICE: select a valid printer name or print the\n report to the screen.\n \n Examine the report to verify that all instances of the date are\n formatted to include all four digits of the year.\n \n Repeat steps 1-4 as necessary to provide an example of each \n type of consultative report generated at your facility.\n submitted to the FDA for approval. Changes only involve print routines\n \n OPTION: Print units with final disposition [LRBLRUF]\n \n This option is designed for a site to print a permanent hard copy of the\n BLOOD INVENTORY file (#65) prior to the use of the option Remove units\n with final disposition [LRBLSER] to purge the BLOOD INVENTORY file (#65)\n for a specified date range. This functionality is provided for those\n sites who may have a need or desire to not keep all BLOOD INVENTORY data\n on line indefinitely. It is not recommended that this option be run on\n a routine basis. However, if necessary the option is available.\n and have no affect on safety critical requirements and has no associated\n \n Because of the implications of generating this report, it is recommended\n that if a site wishes to verify that the printing of dates uses a 4\n digit year that this verification be done in a test environment. This\n report should be locked with the LRBLSUPER key so will need to have a\n user with that key perform the testing if performed.\n \n To verify the correct date format on these reports perform the following\n steps:\n 1) Select the option Print units with final disposition [LRBLRUF].\n risks. \n 2) If this option has been used in the past you may be prompted with the\n following. *** ANSWER NO AT THE PROMPT TO DELETE THE LIST ***\n \n There is a list of units printed by USER,PREVIOUS\n They should be deleted before printing another list. OK ? YES// N\n (NO)\n 3) At the prompt Start with Date TODAY// choose a date far enough in\n the past so that there will be unit with a final disposition entered.\n 4) At the prompt Go to Date TODAY// choose a date more recent than\n the Start with Date.\n \n 5) At the DEVICE: prompt, choose a valid printer name.\n \n Examine the report to verify that all instances of the date are\n formatted to include all four digits of the year.\n \n -----------------------------------------------\n Software Availability:\n \n This patch is available from one of the CIO Field Offices listed below.\n All VAMC's are encouraged to use their FTP capability to obtain the\n A COPY OF THIS PATCH MESSAGE MUST BE FORWARDED TO THE BLOOD BANK\n software from the appropriate directory\n \n CIO Field Office FTP Address Directory\n ---------------- ------------- -----------------\n Hines 152.129.1.110 anonymous.software\n Albany 152.127.1.5 anonymous.software\n Salt Lake 152.131.2.1 anonymous.software\n \n File Name:LAB_Y2K.KID\n \n SUPERVISOR AND THE LABORATORY INFORMATION MANAGER (LIM).\n \n Y2K routine changes included with this patch:\n \n Routine Line Tag Purpose of change\n ------- --------- -----------------\n LRBLJPA1 R+2 Format output to accommodate 4 digit year.\n R+5 Format output to accommodate 4 digit year.\n Y Expand date format to print a 4 digit year.\n H+3 Format output to accommodate 4 digit year.\n \n \n \n LRBLPBR1 T Expand date format to print a 4 digit year.\n N+3 Format output to accommodate 4 digit year.\n L+1 Format output to accommodate 4 digit year.\n R Format output to accommodate 4 digit year.\n \n LRUCN ASK+1 Expand date format to print a 4 digit year.\n H Format output to accommodate 4 digit year.\n \n \n During initial evaluation of LRBL namespaced routines it was reported\n \n that 26 routines would need renovation to be Y2K compliant. After\n further evaluation, it was determined that only two LRBL namespaced\n routines would need to be modified. The routines originally reported but\n not modified are:\n \n LRUDEL LRBLDEX1 LRBLDEX2 LRBLJPA LRBLJPA2\n LRBLJPP LRBLJTS LRBLJTS1 LRBLPC LRBLPC1\n LRBLPR LRBLPR1 LRBLPRA LRBLPT LRBLPT1\n LRBLPTR1 LRBLPUS LRBLPX LRBLPX1 LRBLRCT\n LRBLSET LRBLTA LRBLTA1 LRBLTXA\n PROBLEM: \n \n \nInstallation Instructions:\n =========================\n \nNote: This build contains LR*5.2*201 and LA*5.2*42 therefore, the\nenvironment for installation must satisfy all three patches. There are\nspecial considerations made for Automated instruments which are\nnot directly associated with Blood Bank.\n \n \n 1. The following patches must be installed prior to installation of this\n patch: LR*5.2*153, LA*5.2*27, LA*5.2*37, DI*21.0*44, XU*8.0*71.\n \n 2. From the Kernel Installation and Distribution Systems (KIDS)\n Menu, select the Installation Menu [XPD INSTALLATION MENU]:\n Select INSTALLATION OPTION\n Select Installation Option: Load a Distribution\n Enter a Host File: LAB_Y2K.KID\n Dialog:\n KIDS Distribution saved on Mar 23, 1998@13:22:30\n With the upcoming turn of the century (Y2K) the Office of the Chief\n Comment: LR*5.2*203 LR*5.2*201 LA*5.2*42 Y2K Enhancements 3-23-98\n \n \n This Distribution contains Transport Globals for the following\n Package(s):\n \n LR*5.2*203\n LR*5.2*201\n LA*5.2*42\n \n Information Office Technical Services has issued a guidelines document\n Want to Continue with Load? YES// \n Loading Distribution...\n \n \n It is strongly recommended to do a KIDS Backup before installing\n the build.\n \n 3. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n \n for VISTA Software Y2K requirements. This guideline lays out the core\n 4. From the 'Installation Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n \n 5. From the 'Installation Menu' of the KIDS menu, you may use the option\n 'Print Transport Global' to view what will be installed on your system\n prior to the Install.\n \n 6. Users can remain on the system. Installation should take less than\n ten minutes during non-peak hours.\n essentials to meet or exceed OMB, GAO and congressional requirements for\n \n 7. Primary Laboratory Options should be placed out of service\n and Laboratory Users should be off the system. Disable the menu\n option Laboratory [LRMENU] or the local equivalent during the\n install.\n \n Routine LAB or lab automated instruments interface thru the LSI\n should be stopped.\n \n If the site has direct-connect interfaces for lab automated\n Year 2000 requirements. The VISTA Blood Bank Software v 5.2 was\n instruments, these should be stopped.\n \n The HL7 background job (HLLP) for the Lab Universal Interface\n should be stopped.\n \n The routine LA7UIIN to process incoming HL7 messages should be\n not be running. This routine will shutdown automatically after 5\n minutes if no messages have been received.\n \n If using auto download for Lab automated instruments, the routine\n evaluated and found to have no existing problems as far as date storage\n LA7ADL should be stopped. Use the option 'Start/Stop Auto Download\n Background Job' [LA7 ADL START/STOP].\n if no \n \n 8. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package LR*5.2*203 and proceed with\n install.\n \n 9. If any routines were unmapped as part of step 3, they should be\n returned to the mapped set once the installation has run to\n Reporting Site: N/A\n and evaluation. The date in all instances is already stored internally\n completion. \n \n 10. After installation is complete, remove the routines LR201 and LA42 \n from your system.\n in a format which allows the definite determination of proper century.\n \n The Y2K guidelines document states that applications are required to\n expand the external date displays on reports or forms which can be\n considered legally binding documents between the VA and the veteran, an\n agent of the veteran, or a service- or product- provider to the VA.\n Using this statement as a guideline it was determined that the reports\n generated by the following options were to be modified to display the\n date using a 4 digit year format rather than the traditional dd/mm/yr\n \n format currently used:\n \n Print single BB patient report [LRBLP PRINT SINGLE]\n Print all BB patient reports on print queue [LRBLP PRINT ALL ON QUEUE]\n Blood bank consultation reports [LRBLCN] **> Locked with LRBLSUPER\n Print units with final disposition [LRBLRUF] **> Locked with LRBLSUPER\n \n \n RISK ANALYSIS: Since the coding changes only affect the format of the\n year printed on the report and have no functionality changes, the risk\n Test Site(s)--Alpha Platform w/ DSM OS: Milwaukee, Brockton\n is NONE.\n \n EFFECT ON FUNCTIONAL REQUIREMENTS/ INTENDED USES: Problem does not\n involve a software safety critical requirement and does NOT change the\n scope of a design safeguard or intended use.\n \n POTENTIAL IMPACT ON SITES: There is no potential impact on the sites\n from the installation of LR*5.2*203.\n \n VALIDATION TESTING REQUIREMENTS: Although the changes do not involve\n North Chicago\n any requirements or functional specifications, it is necessary to\n perform the following steps in order to confirm that the Patient\n chartable reports are printing dates using a 4 digit year format:\n \n OPTION: Print single BB patient report [LRBLP PRINT SINGLE]\n \n This option should generate a chartable patient report where the date\n format uses a 4 digit year regardless of whether the work was done\n before or after installation of the patch. To verify this:\n 1) Select the option Print single BB patient report [LRBLP PRINT\n \n SINGLE].\n 2) At the prompt Select Patient Name: type in a name of a patient who\n has previous Blood Bank results.\n 3) At the prompt Print component requests ? NO// press the ENTER key\n to accept NO as the response.\n 4) At the prompt DEVICE: select a valid printer name or print the report\n to the screen. \n \n Examine the report to verify that all instances of the date are\n formatted to include all four digits of the year.\n \n \n Repeat steps 1 through 4 above with the following exception:\n During step 3) answer YES to print component requests. \n \n Examine the report to verify that all instances of the date are\n formatted to include all four digits of the year.\n \n \n OPTION: Print all BB patient reports on print queue [LRBLP PRINT ALL\n ON QUEUE]\n DESCRIPTION:\n \n This option is used to print a batch of chartable patient reports. The\n format of the individual patient reports should be identical to the\n reports printed using the option Print single BB patient report [LRBLP\n PRINT SINGLE]. To verify the correct date format on these reports\n perform the following steps:\n 1) Select the option Print all BB patient reports on print queue [LRBLP\n PRINT ALL ON QUEUE].\n 2) At the prompt Save reports for reprinting ? NO// answer YES.\n 3) At the prompt Print component requests ? NO/ answer YES.\n\n
\nPATCH DESIGNATION: LR*5.2*201 PACKAGE: LAB SERVICE\n \n ^DD(69.91,0,"ID",2) = W:$D(^("0")) " ",$$FMTE^XLFDT($P(^("0"),U,3),"5Z")\n \n New Data Dictionary:\n ^DD(68,.097,0)= NON LAB ACCESSION AREA^S^1:YES;0:NO;^0;21^Q\n \n \n Routine Listing:\n \n Name Line Tag Description\n -------------------------------------------------------------------------\n \n \n LR5XCNV OBSOLETE ROUTINE - deleted\n LR5XCNV0 OBSOLETE ROUTINE - deleted\n LR5XCNV1 OBSOLETE ROUTINE - deleted\n LR5XCNV3 OBSOLETE ROUTINE - deleted\n LR5XCNV4 OBSOLETE ROUTINE - deleted\n LR5XCNV5 OBSOLETE ROUTINE - deleted\n LR5XCNV8 OBSOLETE ROUTINE - deleted\n LR5XCNV9 OBSOLETE ROUTINE - deleted\n LR5XCNVA OBSOLETE ROUTINE - deleted\n PATCH DESCRIPTION: \n LR5XCNVD OBSOLETE ROUTINE - deleted\n LR5XCNVP OBSOLETE ROUTINE - deleted\n LR5XCNVU OBSOLETE ROUTINE - deleted\n LR5XCNVX OBSOLETE ROUTINE - deleted\n LR5XOK OBSOLETE ROUTINE - deleted\n LR5XOK3 OBSOLETE ROUTINE - deleted\n LR5XOK31 OBSOLETE ROUTINE - deleted\n LR5XOK5 OBSOLETE ROUTINE - deleted\n LR5XOK51 OBSOLETE ROUTINE - deleted\n LR5XOK8 OBSOLETE ROUTINE - deleted\n This is the Year 2000 (Y2K) compliance patch containing the changes\n LR5XOK81 OBSOLETE ROUTINE - deleted\n LR5XOK9 OBSOLETE ROUTINE - deleted\n LR5XOK91 OBSOLETE ROUTINE - deleted\n LR5XOKA OBSOLETE ROUTINE - deleted\n LR5XOKA1 OBSOLETE ROUTINE - deleted\n LR5XOKU OBSOLETE ROUTINE - deleted\n LR5XTIM2 OBSOLETE ROUTINE - deleted\n LR5XTIME OBSOLETE ROUTINE - deleted\n LR7OSBR1 T dd/mm/yyyy\n L+1 formatting for the extra 2 century\n necessary to accommodate the year 2000. 2 digit (YY) year dates are\n characters.\n L+2 formatting for the extra 2 century\n characters.\n R+1 formatting for the extra 2 century\n characters.\n LR7OSOS DATE dd/mm/yyyy\n LR7OSUM3 UDT+7 dd/mm/yyyy\n LR7OSUM6 LRUDT+3 dd/mm/yyyy\n WR+5 formatting for the extra 2 century\n characters.\n replaced with 4 digit (CCYY) century year dates in laboratory routines\n WR1+1 formatting for the extra 2 century\n characters.\n LR7OU5 DQ+1 Update the LRAFUNC1 to XLFDT call.\n LR7OU64 CHECK+4 Update the LRAFUNC to XLFSTR call.\n DQ+2 Update the LRAFUNC1 to XLFDT call.\n LR7OU641 DQ+1 Update the LRAFUNC1 to XLFDT call.\n LRABG1 LRABG1+35:36 Set 4-digit date.\n LRAC3 LRAC3+32 dd/mm/yyyy\n LRAC3+43 dd/mm/yyyy\n LRAC4 Y2K New TMP file structure\n for patients' permanent clinical record. 2 digit year dates are replaced\n BS1 dd/mm/yyyy\n LRACK STA+1 2 digit to 4 digit date\n STA+3 ""\n LRACM1 DIC dd/mm/yyyy\n LRACM1+33 dd/mm/yyyy\n LRACM1+41 dd/mm/yyyy\n +1\n LRACM3 LRACM3+19 dd/mm/yyyy\n LRACS QUE+2 Ancillary to cumes.\n LRACS2 LRACS2+3 2 digit to 4 digit date\n in other laboratory routines where space was available. Because of the\n LRACS3 LRIFN+2 Ancillary to cumes.\n LRACSUM LRACSUM+43 Ancillary to cumes.\n LRACSUM3 LRACSUM3+31 2 digit to 4 digit\n LRACSUM3+37 2 digit to 4 digit\n \n LRACSUM4 Y2K Ancillary to cumes.\n LRACSUM6 LRACSUM6+4 2 digit to 4 digit\n LRACSUM6+7 Display format\n LRACSUM6+16 dd/mm/yyyy\n \n lack of space, labels are still printed with 2 digit year dates.\n LRAPAUA W1 Rename variable T to LRAUDT, expand to\n 4 digit year\n END Kill new variable.\n LRAPAUL PRT+1 Format output to accommodate 4 digit year.\n DT Expand to 4 digit year.\n H+1 Format output to accommodate 4 digit year.\n QUE Fix syntax problem with DBS call exported\n with LR*5.2*173\n LRAPBK SH+3 Rename variable LRW(1) to LRSPDT, expand\n to 4 digit year.\n \n SH+7 Rename variable LRW(1) to LRSPDT.\n LRAPDPT AP Expand to 4 digit year.\n AU Expand to 4 digit year.\n LRAPF F+5 Strip off seconds from Admission date \n (set in another routine).\n LRAPJNC W Format output to accommodate 4 digit year.\n L+1 Rename variable H(4) to LRDTINT.\n S+1 Rename variable H(5) to LRDTEXT, expand\n to 4 digit year.\n S+2 Rename variables H(4) and H(5) to LRDTINT \n VERSION: 5.2 PATCH NUMBER: 201\n Warning:\n and LRDTEXT.\n A Rename variable H(4) to LRDTINT.\n H+1 Format output to accommodate 4 digit year.\n END Kill new variables.\n LRAPL W+2 Rename variable S(1) to LRSPECDT.\n P Rename variable S(1) to LRSPECDT and\n expand to 4 digit year.\n END Kill new variable.\n LRAPLG GETP Expand to 4 digit year, format output\n to accommodate 4 digit year.\n Local label routines that call DD^LRX or DT^LRX will need to be modified\n LRAPPF1 EN+1 Expand to 4 digit year.\n EN+4 Format output to accommodate 4 digit year.\n LRAPQ W Expand to 4 digit year.\n W+2 Format output to accommodate 4 digit year.\n H+2 Format output to accommodate 4 digit year.\n LRAPQAT1 L Expand to 4 digit year.\n AU+1 Change direct global reads to ^DGPM( to\n using call INP^VADPT.\n A Assign local variable names to output\n variables from INP^VADPT.\n to call DDOLD^LRX or DTOLD^LRX to print 2-digit dates.\n LRAPQOR W Expand to 4 digit year, format output to\n accommodate 4 digit year.\n H+2 Display format\n LRAPQOR1 D Expand to 4 digit year.\n W Format output to accommodate 4 digit year.\n W2 Expand to 4 digit year.\n H1 Format output to accommodate 4 digit year.\n LRAPS1 EN Expand to 4 digit year.\n EN+3 Format output to accommodate 4 digit year.\n M Additional change to accommodate patch\n \n LR*5.2*203.\n LRAPSEM2 A Expand to 4 digit year. Format output\n to accommodate 4 digit year.\n H+2 Display format\n LRAPSL SET Expand to 4 digit year.\n LRAPTT B Format output to accommodate 4 digit year.\n S+4 Expand to 4 digit year.\n LRAPTT1 LRAPTT1+4 Format output to accommodate 4 digit year.\n LRAPV I Rename variable Z to LRDATE.\n 1 Rename variable Z to LRDATE.\n Patch LR*5.2*201 VISTA BLOOD BANK SOFTWARE V5.2 \n W Rename variable Z to LRDATE, expand to 4 \n digit year.\n 2+1 Rename variable Z to LRDATE.\n H1 Rename variable Z to LRDATE.\n LRAPWE T+2 Expand to 4 digit year.\n LRAUSTA FIX Expand to 4 digit year.\n WRT Rename variable M to LRSENIOR.\n Rename variable M(2) to LRESIDEN.\n WRT+2 Rename variable R(1) to LRAUDT.\n Rename variable R(2) to LRAUCOMP.\n DEVICE PRODUCT LABELING STATEMENT\n Rename variable R(3) to LRFAD.\n Rename variable W(15) to LRPAD.\n Change LRPAD to the correct data piece.\n WRT+3 Reference new variable names, format\n output to accommodate 4 digit year.\n WRT+4 Reference new variable name.\n WRT+5 Reference new variable name.\n H+1 Format output to accommodate 4 digit year\n END Kill new variables before exit routine.\n LRCAP64 LRCAP64+25 Replaced call to LRAFUNC1 date/time \n \n LRCAP64+27 function to Kernel date/time calls.\n LRCAP64+30 ""\n LRCAP64+32 ""\n LRCAP64+35 ""\n LRCAP64+45 ""\n LRCAP67 LRCAP67+19 Replaced call to LRAFUNC1 date/time \n LRCAP67+23 function to Kernel date/time calls.\n LRCAPA12 LRCAPA12+64 Display 4-digit date.\n LRCAPACC LRCAPACC+53 Display 4-digit date.\n LRCAPAM1 LRCAPAM1+11 Replaced call to LRAFUNC1 date/time \n March 10, 1998\n LRCAPAM1+12 function to Kernel date/time calls.\n LRCAPAM1+15 ""\n LRCAPAM2 LRCAPAM2+10 "" \n LRCAPAM2+19 ""\n LRCAPAM2+29 ""\n LRCAPAM3 LRCAPAM3+11 ""\n LRCAPAM3+18 ""\n LRCAPAM3+21 ""\n LRCAPAM3+29 ""\n LRCAPAM3+30 ""\n \n LRCAPAM3+55 ""\n LRCAPAM3+81 ""\n LRCAPAM4 LRCAPAM4+29 ""\n LRCAPAM4+74 ""\n LRCAPAM6 LRCAPAM6+10 ""\n LRCAPAM8 LRCAPAM8+6 ""\n LRCAPAM8+7 ""\n LRCAPAM9 LRCAPAM9+5 ""\n LRCAPAMP LRCAPAMP+13 ""\n LRCAPBB LRCAPBB+7 ""\n VISTA Laboratory Package patch LR*5.2*201 contains changes to software \n LRCAPD2 LRCAPD2+39 ""\n LRCAPDSS LRCAPDSS+17 ""\n LRCAPDSS+26 ""\n LRCAPMR LRCAPMR+29 ""\n LRCAPMR+36 ""\n LRCAPMR2 LRCAPMR2+65 ""\n LRCAPR1A LRCAPR1A+7 ""\n LRCAPR1A+8 ""\n LRCAPR3 LRCAPR3+14 ""\n LRCAPR3+23 ""\n PATCH SUBJECT: Y2K LABORATORY (LR) PATCH\n controlled by VHA DIRECTIVE 97-033, titled VISTA BLOOD BANK SOFTWARE \n LRCAPV1S LRCAPV1S+4 ""\n LRCAPV1S+5 ""\n LRCENDE1 ZAP Prevent complete accession deletion.\n LRDPA1 LRDPA1+16 Changed to Kernel Date/Time call\n LREXPD LREXPD+20 ""\n LRFAST AMIS +1 Replaced $$NOW^LRAFUNC1 with $$NOW^XLFDT.\n LRGEN LRGEN+7 Cleanup Variable\n LRGEN1 LRGEN1+20 Display 4-digit date.\n LRGEN1+27 Display 4-digit date.\n LRLIST LRLIST+5 Replaced call to LRAFUNC1 date/time \n VERSION 5.2. The following routines listed as part of Group B in the \n LRLIST+86 function to Kernel date/time calls.\n LRLISTE LRLISTE+4 ""\n LRLISTE+49 ""\n LRLSTWRL LRLSTWRL+12 ""\n LRMISEZ2 LRMISEZ2+26 dd/mm/yyyy\n LRMISEZ4 LRMISEZ4+17 dd/mm/yyyy\n LROE TASK Variable LRLBL is no longer killed.\n LROLOVER EN+4 Changed to Kernel date/time call.\n OVER+2 Enhanced $D statement\n ROLLAH+3 Set LRAD to correct date/time\n directive were modified to be Y2K compliant:\n ROLLAH+13 Add $G( statement prevent undefined.\n LRORD1 LEDI+1 Added $L statement for alpha characters\n in UID.\n LRORDIM EN+4 Changed $$DOW^LRAFUNC1 to $$DOW^XLFDT.\n EN+22 Changed $$NOW^LRAFUNC1 to $$NOW^XLFDT.\n CHK+1 Changed $$DOW^LRAFUNC1 to $$DOW^XLFDT.\n DATE+3 Changed $$CFMTDH^LRAFUNC1 to $$FMTH^XLFDT.\n DATE+7 Changed $$CDHTFM^LRAFUNC1 to\n $$HTFM^XLFDT.\n LRORDK KILL+7 Variable LRLABLIO is no longer killed.\n LRU, LRUA, LRUPT. \n LRPARAM LRPARAM+13 Replaced call to LRAFUNC1 date/time\n function to Kernel date/time calls.\n LRPEND LRPEND+10 ""\n LRPEND+37 ""\n LRQC LRQC+3 Changed to display 4-digit year date.\n LRRP5 DATE+3 Changed to display 4 digit year date.\n INIT+2 ""\n LRRP6 LRRP6+38 dd/mm/yyyy\n LRRP6+42\n LRRP6A1 LRRP6A1+15 dd/mm/yyyy\n \n LRRP6B1 LRRP6B1+12 dd/mm/yyyy\n LRSMAC LRSMAC+39 Replaced call to LRAFUNC1 date/time \n function to Kernel date/time calls.\n LROW2RP DATE Added an "F" to the %DT flags for 'date of\n order prompt.\n LRSORA2 PRTEST+5 Changed to display 4-digit year date.\n LRSORC1A PRINT+23 Formatting for the extra 2 century\n characters.\n PRNTST+9\n COM+8\n These are shared routines that are used by Blood Bank as well as general \n LRSORD1A PRINT+23 Formatting for the extra 2 century\n characters.\n PRNTST+9\n COM+8\n LRSTOPC OBSOLETE ROUTINE - deleted\n LRTOCOST LRTOCOST+5 Replaced call to LRAFUNC1 date/time\n function to\n LRTOCOST+7 Kernel date/time calls.\n LRTOCOST+8 ""\n LRTOCOST+56 ""\n Laboratory software. They were modified to display a date using a 4\n LRTOCOST+74 ""\n LRTSTSET LRTSTSET+25 ""\n LRTT5 LRTT5+38 ""\n LRTT5+54 ""\n LRTT5R1 LRTT5R1+27 ""\n LRU T Added description of functionality to line\n tag.\n A Added description of functionality to line\n tag, expand to 4 digit year.\n D Added description of functionality to line\n digit century year format and formatting was changed when necessary to\n tag, expand to 4 digit year.\n DA Added description of functionality to line\n tag, expand to 4 digit year.\n DT Checks if LRSS="BB". If not, expands to 4\n digit year. Selected Blood Bank internal\n displays are not modified due to current\n FDA constraints.\n V+3 Kill new variables.\n LRUA LRUA+3 Change call to D^LRU to newly created line\n tag DATE.\n accommodate the extra two characters in the year.\n LRUA+8 Change call to D^LRU to newly created line\n tag DATE.\n DATE New line tag, returns date/time in 4 digit\n year format.\n LRUDEL D Change call to D^LRU to newly created line\n tag DATE.\n REST+5 Change call to D^LRU to newly created line\n tag DATE.\n REST+6 Change call to D^LRU to newly created line\n tag DATE.\n \n DATE New line tag, returns date in eye-readable\n month format w/ 4 digit year.\n LRUER P Rename variable T to LRDATE.\n P+2 Rename variable T to LRDATE, format output\n to accommodate 4 digit year.\n H+1 Format output to accommodate 4 digit year.\n H1 Rename variable T to LRDATE, format output\n to accommodate 4 digit year.\n LRUMD W+1 Rename variable T(1) to LRDATE, expand to 4\n digit year.\n PRIORITY: MANDATORY STATUS OF PATCH: UNDER DEVELOPMENT\n The above change has been reviewed by the VISTA Blood Bank Developer and \n W+3 Rename variable T(1) to LRDATE.\n LRUMDM W+3 Rename variable from T(1) to LRDATE, expand\n to 4 digit year.\n W+5 Rename variable from T(1) to LRDATE, format\n output to accommodate 4 digit year.\n LRUMDP W+1 Rename variable from T(1) to LRDATE, expand\n to 4 digit year.\n W+2 Rename variable from T(1) to LRDATE.\n LRUP LRUP+3 Update the LRAFUNC1 to XLFDT call.\n LRUPT FIX+2 Rename variable from Y to LRDATE, expand to\n found to have no impact on the VISTA BLOOD BANK SOFTWARE version 5.2 \n 4 digit year.\n FIX+4 Rename variable from Y to LRDATE, format\n output to accommodate 4 digit year.\n A Rename variable from Y to LRDATE, format\n output to accommodate 4 digit year.\n LIST+3 Format output to accommodate 4 digit year.\n MORE+1 Rename variable Y to LRDATE, format output\n to accommodate 4 digit year.\n HDR Format output to accommodate 4 digit year.\n LRUTL STF+7 Update the LRAFUNC1 to XLFDT call.\n control functions.\n LRUTT W+1 Expand to 4 digit year, format output to\n accommodate 4 digit year.\n LRVER1 LRVER1+19 Replaced call to LRAFUNC1 date/time\n function to\n Kernel date/time calls.\n LRVER2 LRVER2+13 Display 4-digit date.\n LRVER2+27 ""\n LRVR2 LRVR2+13 Display 4-digit date.\n LRVR2+25 ""\n LRVR2+26 Changed to Kernel Date/time call\n \n LRWLST12 C3 Changed $$CDHTFM^LRAFUNC1 to $$HTFM^XLFDT.\n LRWRKIN1 X+16 Adjust column display to accommodate\n displaying\n X+24 4-digit year.\n LRWRKINC HED+5 Adjust column header to accommodate\n displaying\n HED+11 4-digit year.\n LRWU4 LRWU4+2 Set Kernel variable DT using approved call\n LRWU4+3 $$DT^XLFDT.\n AC2+2 Added "P" to %DT variable, assume past\n PROBLEM: With the upcoming turn of the century (Y2K) the Office of the \n dates.\n AC4+2 Display accession date with 4-digit year.\n LRX DD Changed to display 4-digit year date.\n DT+3 Used Kernel Date/Time call.\n DDOLD Provide backward compatible format for\n labels.\n DTOLD Provide call to return 2 digit date.\n Y2K Call to return dd/mm/yyyy Date/Time\n \n Reference NOIS: N/A\n Chief Information Office Technical Services has issued a guidelines \n \n Reporting Site: N/A\n \n Testing Site(s): Milwaukee, WI - Brockton/West Roxbury, MA\n North Chicago, Il\n \n \n ROUTINE SUMMARY:\n =================\n \n document for VISTA Software Y2K requirements. This guideline lays out\n The second line of the routine now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n the core essentials to meet or exceed OMB, GAO and congressional\n requirements for Year 2000 requirements. Laboratory software has been\n modified to meet or exceed these guidelines.\n DATE PATCH FIRST ENTERED: JAN 27, 1998\n \n RISK ANALYSIS: Changes made by patch LR*5.2*201 have no effect on Blood\n \n Bank software functionality, therefore RISK is none.\n \n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*201 does not \n alter or modify any software design safeguards or safety critical\n elements functions.\n \n \n POTENTIAL IMPACT ON SITES: This patch contains changes to a routine \n identified in Veterans Health Administration (VHA) Directive 97-033. The \n changes have no effect in Blood Bank functionality or medical device \n control functions. There is no adverse potential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation \n scenarios to be completed by sites after installing LR*5.2*201.\n \n \n -----------------------------------------------\n \n Software Availability:\n \n This patch is available from one of the CIO Field Offices listed below.\n All VAMC's are encouraged to use their FTP capability to obtain the\n software from the appropriate directory\n \n CIO Field Office FTP Address Directory\n ---------------- ------------- -----------------\n Hines 152.129.1.110 anonymous.software\n Albany 152.127.1.5 anonymous.software\nCATEGORY OF PATCH: ROUTINE\n Salt Lake 152.131.2.1 anonymous.software\n \n File Name:LAB_Y2K.KID\n \nNote: This patch is issued as a part of a KIDS Distribution in which\nthe Transport Global contains all three Laboratory Y2K patches.\nThe install order and patches are:\nLR*5.2*203 Blood Bank\nLR*5.2*201 Laboratory Service\nand LA*5.2*42 Automated Instruments.\nCATEGORY OF PATCH: DATA DICTIONARY\n \n Data dictionary changes include:\n \n Modified the write "ID" nodes for:\n ^DD(62.3,0,"ID",.02) = W:$D(^("0")) " ",$$FMTE^XLFDT($P(^("0"),U,2),"5Z")\n \n ^DD(67,0,"ID",.03) = W " ",$$FMTE^XLFDT($P(^(0),U,3),"5Z")\n \n ^DD(67.1,0,"ID",3) = W:$D(^("0")) " ",$$FMTE^XLFDT($P(^("0"),U,3),"5Z")\n \n\n\n Reference NOIS: HIN-0297-40272, DEN-0697-51422\n This patch to the Laboratory package does not contain any changes to the\n \n DEVICE: HOME// TELNET\n \n LR*5.2*155\n \n -------------------------------------------------------------------------\n \n Install Started for LR*5.2*155 : \n Mar 26, 1998@14:02:16\n \n VISTA BLOOD BANK Software as defined by VHA Directive 97-033 titled VISTA\n Installing Routines:\n Mar 26, 1998@14:02:17\n \n Updating Routine file...\n \n Updating KIDS files...\n \n LR*5.2*155 Installed. \n Mar 26, 1998@14:02:18\n BLOOD BANK SOFTWARE VERSION 5.2.\n \n \n 1. HIN-0297-40272\n Two problems were discovered with the QA functions for the Autopsy\n Accession Area.\n \n # 1: The user wasn't prompted to enter any QA codes while\n \n executing the option QA codes entry/edit [LRAPQACD] and\n choosing the Autopsy Accession Area.\n \n # 2: When using the option QA outcome review cases [LRAPQOR], not\n all of the information was printing. Prior to patch LR*5.2*72,\n the actual Autopsy accession # and date of autopsy would print\n on the 2nd part of the report.\n \n 2. It was reported that after patch LR*5.2*72 that the report format\n for Autopsy data review [LRAPAURV] did not accommodate the new\n Reporting Site: Hines, Long Beach\n accession # format.\n \n ROUTINE SUMMARY:\n =================\n \n The second line of the routine now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Values\n \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n LRAPQACD 1985498 1982867 72,85,155\n LRAPQOR2 5647114 5107599 155\n LRAURV 8143951 8364694 155\n \n Installation Instructions:\n =================\n \n Test Site(s) Hines, Madison, Long Beach\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n \n 2. From the 'Installation Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n \n 3. From the 'Installation Menu' of the KIDS menu, you may use the option\n 'Print Transport Global' to view what will be installed on your\n system prior to the Install.\n \n \n 4. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n \n 5. Users can remain on the system. Patch installation should take less\n than 5 minutes. No options need to be placed out of service. \n Install during non-peak times.\n \n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package LR*5.2*155 and proceed with \n DESCRIPTION:\n install.\n \n 7. If any routines were unmapped as part of step 4, they should be\n returned to the mapped set once the installation has run to\n completion. \n \n \n Below is an example of the dialogue seen during the KIDS load.\n \n Select Installation Option: INStall Package(s)\n ============\n Select INSTALL NAME: LR*5.2*155 Loaded from Distribution\n 3/26/98@13:49\n :39\n => LR*5.2*155\n \n This Distribution was loaded on Mar 26, 1998@13:49:39 with header of \n LR*5.2*155\n It consisted of the following Install(s):\n LR*5.2*155\n \n \n LR*5.2*155\n \n Install Questions for LR*5.2*155\n \n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis patch fixes comment problems during receipt of specimens from wards.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nRequired for special processing of file 63 for Patient Merge.\n\n
\n \n VISTA Laboratory Package patch LR*5.2*210 contains changes to software\n Gliadin Ab IgG 84140.3103 89635.0000\n Gliadin Ab Panel 82435.3103 89637.0000\n Specimen Collection Time 82373.3103 89359.0000\n Rh (D) Typing 86087.0000 86088.0000\n CD62L 86601.0000 86682.0000\n CDw124 86670.0000 86683.0000\n Rh Typing 86714.0000 86712.0000\n Plateletpheresis 86728.0000 86739.0000\n Drug Dependant Ab 89110.0000 84466.0000 X*Drug Dependant\n HLA DR 89079.0000 89569.0000\n controlled by VHA DIRECTIVE 97-033, titled VISTA BLOOD BANK SOFTWARE\n Glaidin Ab IgA 84295.0000 84028.0000 X*Glaidin Ab\n X*Hepatitis C RNA 97485.0000 87419.0000\n HIV Viral Load Ultra 98497.0000 87423.0000\n Smooth Muscle Ab 98589.0000 87379.0000\n Norchlordiazeposide 81030.0000 81411.0000\n \n Reference NOIS: N/A\n \n Reporting Site: N/A\n \n VERSION 5.2. Change includes:\n Testing Site(s): Long Beach, CA, Milwaukee, WI, Brockton, MA\n \n -----------------------------------------------\n Software Availability:\n \n This patch is available from one of the CIO Field Offices listed below.\n All VAMC's are encouraged to use their FTP capability to obtain the\n software from the appropriate directory.\n \n CIO Field Office FTP Address Directory\n LROS was modified to display the Patient Care Encounter (PCE) visit\n ---------------- ------------- -----------------\n Hines 152.129.1.110 anonymous.software\n Albany 152.127.1.5 anonymous.software\n Salt Lake 152.131.2.1 anonymous.software\n \n File Name:LR52_210.KID\n \n ROUTINE SUMMARY:\n =================\n \n number when one exists.\n The second line of the routine now looks like:\n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List \n ------------ ------------ ----------- -----------\n LR210 NA 13528777 210 \n LRCE 12940981 13197719 28,76,103,121\n \n 153,210\n LROS 14491271 14423120 121,153,210\n \n \n Installation Instructions:\n ==========================\n The Laboratory Information Manager (LIM) should be informed of/coordinate\n the installation this patch. This patch contains important codes required\n for Laboratory Management Index Program (LMIP) reporting and Laboratory\n Electronic Data Interchange (LEDI) implementation.\n The above change has been reviewed by the VISTA Blood Bank Developer and\n \n All users may remain on the system. Laboratory users should be idle (no\n accessioning or verifying). The LAB interface routine does not need to\n be stopped. The Universal Interface does not need to be stopped. The\n Health Level Seven Lower Level Protocols (HL7 LLPs) do not need to be\n stopped.\n \n The installation of this patch takes less than 10 minutes.\n \n 1. START FROM KERNEL \n found to have no impact on the VISTA BLOOD BANK SOFTWARE version 5.2\n From the KERNEL Installation and Distribution Systems (KIDS)\n Menu, select the Installation menu [XPD INSTALLATION MENU]: \n Installation\n Edits and Distribution ... \n Utilities ... \n Installation ... \n \n 2. SELECT INSTALLATION OPTION \n Select Installation Option: Load a Distribution \n Enter a Host File: LR52_210.KID\n control functions.\n \n This Distribution contains Transport Globals for the following \n Package(s): LR*5.2*210\n \n Want to RUN the Environment Check Routine? YES// \n LR*5.2*210\n Will first run the Environment Check Routine, LR210\n \n Use INSTALL NAME: LR*5.2*210 to install the Distribution. \n \n \n NOTE: The following are OPTIONAL:\n \n a. Backup a Transport Global - This option will create a backup \n message of any routines exported with this patch. It will not \n backup any other changes, such as DDs or templates. \n b. Compare Transport Global to Current System - This is not\n recommended. The reported data is misleading.\n c. Verify Checksums in Transport Global - This option will allow \n you to ensure the integrity of the routines that are in the \n transport global. \nDescription: \n PROBLEM: Sites have requested a means to verify CPT code capture. It\n \n 3. Use the install name LR*5.2*210 \n \n Note: If installation is successful, remove the routine LR210 from your\n system.\n \n 4. No routine mapping adjustments are required\n \nRoutine Information:\n====================\n was determined that displaying the PCE visit number when viewing the\n \nRoutine Name:\n - LRCE\n \nRoutine Name:\n - LROS\n \nRoutine Name:\n - LR210\n \n Order/Test Status for a patient would assist sites in verifying their\n==========================================================================\n data.\n \n RISK ANALYSIS: Changes made by patch LR*5.2*210 have no effect on Blood\n Bank software functionality, therefore RISK is none.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*210 does not\n alter or modify any software design safeguards or safety critical\n============\n elements functions.\n \n POTENTIAL IMPACT ON SITES: This patch contains changes to a routine\n identified in Veterans Health Administration (VHA) Directive 97-033. The\n changes have no effect in Blood Bank functionality or medical device\n control functions. There is no adverse potential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation\n scenarios to be completed by sites after installing LR*5.2*210.\n \n \n =============================\n \n This patch is the regular release of additional National Laboratory Test\n Codes (WKLD CODES). It contains the requested additional prefix and\n suffix codes required to identify ordered test and test results.\n LR*5.2*210 Patch Description:\n \n This patch contains updates of WKLD CODES stored in WKLD CODE file (#64).\n These codes are also known as National Laboratory Test codes. The added\n codes represent those codes requested, by various sources, to identify\n Patch LR*5.2*210 VISTA BLOOD BANK SOFTWARE V5.2 DEVICE PRODUCT LABELING\n ordered tests and results. If you wish to print the new additional WKLD\n CODES, use FileMan Print sorted by numbers. Begin with number 2990, end\n with 99999. Select caption print for the print fields.\n \n This patch contains updates of suffix codes stored in WKLD SUFFIX CODES\n file (#64.2). These codes were requested, by various sources, to identify\n methods used to determine results of ordered tests.\n \n This patch contains updates of manufacturers stored in WKLD INSTRUMENT\n MANUFACTURER file (#64.3). This file is a reference file used to group\n STATEMENT\n WKLD CODE SUFFIX codes by manufacturer.\n \n In addition to new NLT Codes the options Order/test status [LROS] and\n Review by order number [LRCENLKUP] have been enhanced to display the\n Visit number returned by the PCE interface for Laboratory CPT code\n capture. The number displayed corresponds to the internal entry number\n for the VISIT (#9000010) file. This number maybe useful when verifying\n Laboratory CPT workload capture. The VISIT file pointer is free text and\n each individual pointer number is separated by a semi-colon. CPT workload\n is only captured for patients seen on outpatient status. CPT codes are\n \n captured for ordered tests only. There is no relationship between\n accessioned/verified and CPT workload capture. CPT workload capture is\n based on entries in the LAB ORDER ENTRY (#69) file ONLY.\n \n Ordered tests must be linked via NATIONAL VA LAB CODE field (#64) of the\n LABORATORY TEST file (#60). All CPT codes associated with the linked NLT\n Code will be passed to the PCE interface.\n \n The new print option NLT Monthly Workload Detail [LR CAP ELROY] is also\n provided. This FileMan print option allows the user to select\n April 10, 1998\n institution/division, date range and NLT codes. The report will print\n sub-total by NLT code with grand total for the report period. This report\n maybe useful when reviewing data stored in LAB MONTHLY WORKLOADS file\n (#67.9) for workload trends by specific NLT Codes.\n \n Note: When selecting Institution use literal name (i.e. Long Beach), not\n station number (.i.e. 600).\n NOTE: Data is stored in the LAB MONTHLY WORKLOADS file by month only.\n There aren't any daily totals stored in this file.\n \n \n The Post install procedure will make some corrections to your database if\n appropriate. This is a list of possible corrections required by your\n systems. If corrections are made, they will be displayed during the\n install. They are also stored in the Install file for review.\n \n If the install is successful please remove the routine LR210 from your\n system.\n \n NLT Name Old Number New Number New Name\n Gliadin Ab IgA 84295.3103 89589.0000\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\n \n \nadditional logic which determines if the PCE package is active. If the PCE\npackage is not active, no CPT codes will be passed regardless of the entry\nin the PCE/VSIT ON field.\n 11.This patch provides utilities for linking ORDERABLE tests in\nLABORATORY TEST (#60) file to WKLD CODE (#64) file. This linkage differs\nfrom LMIP file setup. CPT Procedure coding is a rather non specific\nidentification of ORDERED tests. CPT codes identifies procedures ordered\nby the provider. LMIP coding identifies procedures and method of analysis\nused to collect management data. These coding system are used for two\ndifferent purposes and should not be confused.\nThe National Laboratory File [LR7O 60-64] menu under the LIM workload menu\nThere are two routines which provide this functionality, LR7OU4 and\nLR7OU5.\n \n \nExample of the Semi-automated option: \n \nSelect OPTION NAME: LRMENU Laboratory DHCP Menu\n \n \nSelect Laboratory DHCP Menu Option: Supervisor menu\n[LR LIM/WKLD] has options to link file Laboratory Test (#60) to WKLD CODE\n \nSelect Supervisor menu Option: Lab liaison menu\n \nSelect Lab liaison menu Option: National Laboratory File\n \nSelect National Laboratory File Option: ?\n \n 1 Semi-automatic Linking of file 60 to 64\n 2 Manual Linking of file 60 to 64\n \n(#64) file. The options you will use are:\nEnter ?? for more options, ??? for brief descriptions, ?OPTION for help\ntext.\n \nSelect National Laboratory File Option: 1 Semi-automatic Linking of file\n60 to 64\n \n This option will look for potential matches between file 64 (NLT) and\nfile 60. \n \n You will be allowed to create a permanent link between matching entries\n Semi-automatic Linking of file 60 to 64 [LR7O 60-64 AUTO]\nin these files. Tests with the type of NEITHER will be omitted during link\nphase. \n \n ONLY GENERIC NLT CODES CAN BE LINKED TO LAB TEST\n \n \n \n Those LAB TEST already linked to the NLT file will also be omitted.\n \n \n Manual Linking of file 60 to 64 [LR7O 60-64 MANUAL] \nReady to proceed? YES\nWould you like a list of WKLD CODES from LABORATORY TEST file? No// \n \n Do you want to automatically link entries when there is an exact\nmatch \n \n on the NAME in both files\n \n? No// Y\n (Yes)\n These options should be run in this order listed to reduce linking time.\n \n Did not find a exact name match for Lab Test 1,25-DIHYDROXYVIT D3\n Want to use a Verify WKLD code instead?\n \n Vitamin D 1 25 Dihydroxy 83998.0000\n \nSelect Verify WKLD if appropriate: VIT\n \n \n60 = 1,25-DIHYDROXYVIT D3\nIt may be beneficial to obtain a report of Laboratory Tests with Accession\n64 = Vitamin D 1 25 Dihydroxy 83998.0000 \n o----LINKED----o\n \n \n Did not find a exact name match for Lab Test ABO/RH TYPING\n Want to use a Verify WKLD code instead?\n \n ABO Cell Serum and Rh(D) 86082.0000\n \nSelect Verify WKLD if appropriate AB\nand Verify WKLD CODES listed. Each of the above options has the capability\n \n \n60 = ABO/RH TYPING\n64 = ABO Cell Serum and Rh(D) 86082.0000 \n o----LINKED----o\n \n \n60 = ACETALDEHYDE\n64 = Acetaldehyde 81502.0000 \n \nof producing this report.\n \n60 = ACETAMINOPHEN\n64 = Acetaminophen 81068.0000 \n o----LINKED----o\n \n \n60 = ACETONE\n64 = Acetone 81504.0000 \n o----LINKED----o\n \nDESCRIPTION:\n \n \n60 = ACETYLCHOLINE RECEPTOR\n64 = Acetylcholine receptor 89080.0000 \n o----LINKED----o\n \n \n60 = ACTH\n64 = ACTH 82020.0000 \n o----LINKED----o\n \nCoordinate the task of linking tests with the Laboratory LIM so it is\n \n Did not find a exact name match for Lab Test AFB CULTURE & SMEAR\n Want to use a Accession WKLD code instead?\n \n Accession Specimen Mycol Cult 87800.0000\n \nSelect Accession WKLD if appropriate ^\n \n================================================================\nExample of the PCE ^TMP("LRPXAPI") which is built by the LRCAPPH1 routine.\ncompleted before the scheduled start of collection of CPT codes for\n \n^TMP("LRPXAPI",545275466,"ENCOUNTER",1,"ENC D/T") = 2960709.140053\n^TMP("LRPXAPI",545275466,"ENCOUNTER",1,"ENCOUNTER TYPE") = A\n^TMP("LRPXAPI",545275466,"ENCOUNTER",1,"HOS LOC") = 41\n^TMP("LRPXAPI",545275466,"ENCOUNTER",1,"INSTITUTION") = 5000\n^TMP("LRPXAPI",545275466,"ENCOUNTER",1,"PATIENT") = 230\n^TMP("LRPXAPI",545275466,"ENCOUNTER",1,"SERVICE CATEGORY") = X\n^TMP("LRPXAPI",545275466,"PROCEDURE",1,"ENC PROVIDER") = 31\n^TMP("LRPXAPI",545275466,"PROCEDURE",1,"PROCEDURE") = 12345\n^TMP("LRPXAPI",545275466,"PROCEDURE",1,"QTY") = 1\nlaboratory activity (October 1, 1996). Only those tests that can be\n \n \nROUTINE SUMMARY:\n=================\n \n Routine Name Before Patch After Patch Patch List\nLR7OU4 NA 12072536 127\nLR7OU5 NA 13069620 127\nLRCAPDSS NA 5467821 127\nLRCAPFDS 6562403 8630651 105,119,127\nordered by clinicians on patients need to be linked.\nLRCAPPH 9417286 10523848 1,19,127\nLRCAPPH1 NA 3477475 127\nLRCAPV1A 2080378 2090945 105,127\n \n \nThis is the PCE/API patch which will be replacing the current method of\nrecording clinic stop codes with CPT codes. This patch creates several new\nfields and one new file LAB NLT/CPT CODES (#64.81).\nThe primary purpose of this patch (LR*5.2*127) is to convert from\n 1. A new field in LABORATORY TEST file(#60) named NATIONAL VA LAB\nCODE (#64). This new field links orderable tests in file #60 with generic\nWKLD CODES (a.k.a. NLT) (#64). Generic codes are those NLT codes ending in\nfour (4) zeros. Utilities (options) are provided for linking LABORATORY\nTEST (#60) file to WKLD CODE (#64) file. The new PCE/API uses this linkage\nto determine what CPT codes should be passed to the PCE/API. Orderable\ntests in LABORATORY TEST file should have a linkage to WKLD CODE.\n 2. Modified field PCE/VSIT ON (#615) in file LABORATORY SITE\n(#69.9) will control which reporting method should used. Field\nfunctionality change: The TRANSMIT CLINIC STOP CODES (#614) field in the\nreporting Laboratory clinic stop codes, to reporting CPT codes for ordered\nLABORATORY SITE (#69.9) file is no longer used to control reporting of\nclinic stop codes. The PCE package has replaced the clinic stop codes with\nCPT codes for each test collected. You should now use PCE/VSIT ON (#615)\nin LABORATORY SITE (#69.9) file to control both clinic stop code and CPT\ncode transmission. Patch LR*5.2*127 automatically sets the PCE/VSIT ON\nfield to report both clinic stop and CPT codes. It is expected that\nbeginning with Oct. 1, 1996 VA DHCP will begin reporting workload using\nCPT codes. Logic has been built into the software to determine when to\nstart reporting CPT codes to the PCE package. The TRANSMIT CLINIC STOP\nCODES (#614) field will be retired in a future version.\ntests done on patients. The Laboratory Package will capture and send CPT\n 3. A new field PCE COUNTED (#11) has been added to file LAB ORDER\nENTRY (#69). This field prevents an order from being counted more than\nonce.\n 4. The field CPT CODE (#18) has been modified in WKLD CODE\nfile(#64). This field's name has been changed to CODE and is a multiple.\nThe CODE entries can be of different types. Each code has optional fields\nof RELEASE DATE (#2) and INACTIVE DATE (#3). These fields can be used to\nscreen codes based on dates entered. There is another field REPLACEMENT\nCODE (#4) which is used for local record keeping. The software logic does\nnot use the REPLACEMENT CODE field.\ncodes via PCE/API. There is an install deadline involved (10/1/96) in\n 5. This patch also adds CPT codes to WKLD CODE FILE (#64) during\nthe post install phase.\n 6. Additional Fields have added to WKLD LOG FILE (#64.03). These\nfields are not directly related to PCE/API. These fields are used to\nsupport Laboratory Extract for DSS. Additional fields have been added to\nWKLD LOG FILE (#64.03) to support laboratory extract of LMIP codes for\nDSS. These files are not used by the Laboratory PCE/API. WKLD LOG FILE is\nbeing upgraded to support DSS API and is used exclusively by DSS and there\nis no direct user interaction. WKLD LOG FILE is a temporary storage file\nfor LMIP codes for DSS extracts. A new routine ,'LRCAPDSS' provides DSS\norder to support PCE functionality requirements.\nwith a API to extract laboratory workload data in batch mode. If the site\nis currently using WKLD LOG FILE for local purposes, this practice should\nbe terminated. WKLD LOG FILE IS USED EXCLUSIVELY TO SUPPORT DSS DATA\nEXTRACTION.\n 7. This patch also contains a new file LAB NLT/CPT CODES (#64.81).\nThis file is only used to transport data to upgrade existing WKLD CODES\n(NLT) test codes already released to the field. This file is used by the\nPost Install routine to add CPT codes to WKLD CODE (#64) file. Entries are\nautomatically purged from 64.81 file if the linking process was\nsuccessful. If there is an error during the linking process, a message is\n \nstored in #64.81 and the entry is not purge. A FileMan print of #64.81\nfile will display those codes which were not linked. If there are no\nerrors, file #64.81 will be empty after the post install routine runs to\ncompletion.\n Any new WKLD CODES released will already have assigned CPT Procedure\nand are distributed via national releases of NLT package. CPT coding of\nWKLD CODES is done by Health Administration Head Quarters and should not\nbe changed locally.\n 8 Option Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] has been\nenhanced to allow printing of WKLD CODES which have CPT code linkages.\nCreating links between file LABORATORY TEST (#60) and WKLD CODE (#64)\nModifications to routine LRCAPFDS provided this new functionality.\n 9. Routine LRCAPV1A has been modified to allow the user to enter a\nsynonym for newly created WKLD CODES using the option; 'Add a new WKLD\ncode to file [LRCAP CODE ADD].\n 10. This patch contains a new routine LRCAPPH1 and the modified\nroutine LRCAPPH. These routines gather the needed data and creates the\nPCE/API CPT linkage. 'LRCAPPH' has been change to look at the modified\nfield PCE/VSIT ON (#615) in file LABORATORY SITE file (#69.9) to determine\nwhich reporting method should used. The user can inactivate reporting,\nreport only CPT codes or report both CPT and Clinic Stop Codes. There is\n\n\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\n \n \n \nInstallation for all sites.\n\n
\n This patch to the Laboratory package does not contain any changes to\n printers. This patch supports 1x2, 15/16X3, and 10 part 2.4x4\n formats used on the Intermec printers, did not use all of the space.\n This resulted in a shortened test list. The label software has been\n adjusted to use the full amount of space available for the test list.\n This varies with the different label sizes and formats.\n The list of tests will be formatted such that a ";" separates each \n test abbreviation. If all of the accession tests can not print on the\n label due to lack of space then the list will be truncated. Truncation\n will be indicated by the characters "..." at the end of the label test\n list.\n NOIS ASH-1095-33536, BAY-0796-30672, MRN-0296-41708, WBP-0795-22054\n label stock.\n \n 16. Fixed the location not printing on 1x2 and 10 part labels.\n NOIS ASH-0795-30288, FHM-0396-50465, SHR-0696-70850\n \n 17. Fixed an undefined error, variables LRAN and LRACC, when printing\n future collection labels.\n NOIS MAN-0196-11087\n \n 18. Changed the setting of variables LRBAR0/LRBAR1 to values returned by\n a supported call to KERNEL (PSET^%ZISP) for bar code on (IOBARON)/bar\n \n code off (IOBAROFF) characteristics.\n NOIS SPO-0696-50319\n \n 19. Provided the ability to designate label type and label routine on a\n printer by printer basis. See the section on the POST-INSTALLATION\n INSTRUCTIONS item #1.\n NOIS AMA-0297-71215\n \n 20. To conform to VistA Programming Standards and Conventions (SAC),\n The following changes have been made:\n 2. Support exists for the following bar code symbologies:\n \n a. W * was changed to W $C() in the label routines.\n NOIS FNC-0697-31993\n \n b. Routine LRLABLD was changed to use an approved DBIA (#2469) when\n determining a user's default lab label printer. If a printer is\n associated with the user's home device by entering a printer in\n the LAB LABEL PRINTER field (#101) in the DEVICE (#3.5) file, then\n this printer becomes the default label printer instead of LABLABEL.\n It had been using a direct global read of global %ZIS.\n Code 39\n\n c. Routine LRPHLIST was changed to use the supported DBIA #10091 call. \n If the user has no institution defined in the NEW PERSON (#200) file,\n this call is used to determine the user's default institution, \n It had been using a direct global read of global XMB.\n \n 21. The Print future collection labels option [LRUFCL] was not determining\n the collection sample correctly. The collection sample is now derived\n from the COLLECTION SAMPLE field (#3) in the SPECIMEN # multiple \n field (#1) of the LAB ORDER ENTRY file (#69).\n Code 39 with check digit\n \n 22. Lab routine selection:\n \n a. The label routine selection is backward compatible with previous\n logic. The software determines a label routine by the value of the\n LABEL TYPE field (#302) in the LABORATORY SITE file (#69.9).\n \n b. If a site defines label devices in the LABEL DEVICE multiple field\n (#360) of the LABORATORY SITE file (#69.9), the label routine will\n be determined as follows:\n Code 128 bar code\n \n If an accession area is not defined (test/future order labels) then\n the accession area designated by DEFAULT ACCESSION AREA field (#.06)\n within LABEL DEVICE multiple field (#360) of the LABORATORY SITE\n file (#69.9) for following selection logic is used.\n \n If an alternate label routine for the accession area is designated\n then the label routine designated by fields ALTERNATE LABEL\n ENTRY (#5.2) and ALTERNATE LABEL ROUTINE (#5.3) of the\n ACCESSION file (#68) is used.\n \n \n Otherwise if site has designated an alternate label routine for the\n device then the label routine designated by fields ALTERNATE LABEL\n ENTRY (#.04) and ALTERNATE LABEL ROUTINE (#.05) within LABEL DEVICE\n multiple field (#360) of the LABORATORY SITE file (#69.9) is used.\n \n Otherwise if the printer is designated as an Intermec 4100 by the\n PRINTER TYPE field (#.02) of the LABEL DEVICE multiple field (#360)\n of the LABORATORY SITE file (#69.9), the label routine is determined\n by the LABEL STOCK field (#.03) of the LABEL DEVICE multiple field\n The bar code symbology used can be designated on an accession area\n (#360) of LABORATORY SITE file (#69.9) as follows:\n \n 1 15/16X3 --> routine LRLABELC\n 2 1X2 --> routine LRLABELA\n 3 2.5X4 10 PART --> routine LRLABELB\n \n c. If none of the conditions checked in b. above apply then the label\n routine designated in a. above is used.\n \n \n basis. See the BAR CODE PRINT field (#5) in the ACCESSION file (#68).\n 23. Intermec 4100 label format assignments:\n \n F0 - Reserved by manufacturer\n F1 - Presently not used (Unavailable on 4100BA models)\n F2 - Presently not used (Unavailable on 4100BA models)\n F3 - 1x2 Plain Label (Old Style)\n F4 - 1x2 Code 39 Label (Old Style)\n F5 - 1x2 Code 39/128 - UID\n F6 - Presently not used\n F7 - 15/16x3 Plain Label (Old Style)\n the VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 97-033\n The set of codes for this field has been expanded to allow designating\n F8 - 15/16x3 Code 39 (Old Style)\n F9 - 15/16x3 Code 39/128 - UID\n F10 - Presently not used\n F11 - Presently not used\n F12 - 10 Part Code 39 (Old Style)\n F13 - 10 Part Code 39/128 - UID\n F14 - Presently not used - Reserved for LEDI shipping labels\n F15 - Presently not used - Reserved for LEDI shipping labels\n F16 - Presently not used - Reserved for LEDI shipping labels\n F17 - Presently not used - Reserved for LEDI shipping labels\n a specific symbology. See item #23 below for the effect of this field\n F18 - Presently not used - Reserved for LEDI shipping labels\n F19 - Presently not used - Reserved for LEDI shipping labels\n \n Note: Formats F4, F8, and F12 print the bar code with a check digit.\n \n 24. Intermec format selection:\n Note: This is based on the printer being designated as Intermec printer,\n that is when the PRINTER TYPE field (#.02) in the LABEL DEVICE\n multiple field (#360) of the LABORATORY SITE file (#69.9)\n equals 1 and the value of the BAR CODE PRINT field (#5) in the\n when using the Intermec label printers.\n ACCESSION file (#68) is as listed in the below table:\n \n Intermec 4100\n 1x2 label 15/16X3 10 part label\n \n 0 F3 F7 F12\n 1 F4 F8 F12\n BAR CODE 2 F5 F9 F13\n PRINT 3 F5 F9 F13\n 4 F5 F9 F13\n \n \n BAR CODE PRINT set of code: 0 - NONE\n 1 - YES (Code 39 with check digit)\n 2 - Code39\n 3 - Code39 with check digit\n 4 - Code128\n \n NOTE: The site will need to program the Intermec 4100 printer for those\n formats which will be used based on label stock and bar code\n symbology selected.\n 3. Support exists for bar coding the short/long identifier on labels.\n Example: Site is using 1x2 labels and has specified BAR CODE\n PRINT of 0,1, or 4 for various accession areas.\n The Intermec 4100 printer would need to be\n downloaded with formats F3, F4, and F5.\n \n \n Associated NOIS\n ---------------\n AMA-0297-71215\n ASH-0795-30288\n The label software will now check the field TYPE OF ACCESSION NUMBER\n ASH-1095-33536\n BAN-1097-11647\n BAY-0796-30672\n BIG-0596-71566\n BRK-0696-11519\n BUF-0695-13329\n DAY-0497-42491\n FHM-0396-50465\n FNC-0697-31993\n GRJ-0395-50211\n (#.092) to determine the identifier to bar code. If a short identifier\n GRJ-1095-52265\n GRJ-0796-50216\n MAN-0196-10924\n MAN-0196-11087\n MRN-0296-41708\n PRO-0196-10343\n PRO-1096-11923\n SHR-0696-70850\n SPO-0696-50319\n WBP-0795-22054\n (accession number) is selected it will be formatted as determined in\n \n \n Test Sites\n ----------\n \n Asheville VAMC\n Bath VAMC\n Dayton VAMC\n Loma Linda VAMC\n Long Beach VAMC\n item #4 below. If it is a long identifier the Laboratory Unique\n Manchester VAMC\n Milwaukee VAMC\n North Chicago VAMC\n \n ----------------------------\n \n ROUTINE SUMMARY\n ---------------\n \n The following is a list of routines included in this patch. The second\n Identifier (UID) will be printed. Formats in the Intermec label routines\n line of each routine now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n LR161 N/A 2465270 161\n LRBARA 3774911 6240751 161\n titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n have been adjusted to handle the increased length of the bar code\n LRBARB 6451096 18545310 161\n LRBARC N/A 4506131 161\n LRBARCF N/A 4094580 161\n LRLABEL 1668195 826314 161\n LRLABEL1 2827443 978058 161\n LRLABEL2 1294781 590501 161\n LRLABEL3 1905479 847432 161\n LRLABEL5 2457165 1079193 161\n LRLABEL6 3490879 3114683 161\n LRLABELA 1935828 2536685 161\n printed.\n LRLABELB 4990488 6023279 161\n LRLABELC N/A 1616954 161\n LRLABELF 7055278 5776749 121,161\n LRLABLD 10046912 8089099 65,161\n LRLABLD0 9258958 9351158 1,65,121,161\n LRLABLDS 5030406 4835286 161\n LRLABLIO 7032106 5515879 107,161\n LRLABXOL 5526784 2794683 11,121,161\n LRLABXT 5435171 6060326 80,161\n LRPHLIS1 14289685 12110295 1,161\n NOIS PRO-1096-11923, MAN-0196-10924, BRK-0696-11519\n LRPHLIST 13349268 12051480 161\n \n \n FILE SECURITY\n -------------\n \n There are four new fields added by this patch which have FileMan Write\n Access equal to "@". This is required for security purposes. To edit these\n fields requires the user to have FileMan Programmers Access. The fields\n affected are:\n \n \n - ALTERNATE LABEL ENTRY (#5.2) and ALTERNATE LABEL ROUTINE (#5.3) of the\n ACCESSION file (#68).\n\n - ALTERNATE LABEL ENTRY (#.04) and ALTERNATE LABEL ROUTINE (#.05) within\n LABEL DEVICE multiple field (#360) of the LABORATORY SITE file (#69.9).\n \n \n INSTALLATION INSTRUCTIONS\n -------------------------\n 4. The ability to designate the length of a short identifier (accession\n The install time for this patch is less than 5 minutes. This patch\n can be installed when Laboratory users are on the system.\n However the following conditions apply:\n \n - Label printing should not be occurring\n \n \n \n NOTE: MailMan and KERNEL patches must be current on the target system to\n avoid problems loading and/or installing this patch.\n number) when it is selected to be bar coded on an accession label is\n \n Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC). The LIM/ADPAC needs to perform the\n file setup as explained in the post-installation instructions if\n applicable.\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n supported. When the accession number is less than the number specified,\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n it will be padded with zeros. See the description for the BAR CODE PAD\n \n 6. If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routine in your\n production account to the routine in the patch by using the 'Compare\n a Transport Global to Current System' option. These options can\n both be found under the 'Installation' menu.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*161'. When prompted 'Want to\n field (#5.1) in the ACCESSION file (#68) for additional information and\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LR161 can be deleted after successful patch installation.\n \n \n *****************************************************************************\n Below is an example of the dialogue seen during the KIDS install:\n examples.\n \n \n Select Installation Option: 6 Install Package(s)\n Select INSTALL NAME: LR*5.2*161 Loaded from Distribution \n 5/2/97@17:11:20\n => LR*5.2*161\n \n This Distribution was loaded on May 02, 1997@17:11:20 with header of\n LR*5.2*161\n It consisted of the following Install(s):\n \n \n LR*5.2*161\n \n LR*5.2*161\n Will first run the Environment Check Routine, LR161\n \n \n --- Environment Check is Ok ---\n \n Install Questions for LR*5.2*161\n \n 5. Support for local label routines on a printer or accession area basis\n Incoming Files:\n \n \n 62.05 URGENCY (Partial Definition)\n Note: You already have the 'URGENCY' File.\n \n \n 68 ACCESSION (Partial Definition)\n Note: You already have the 'ACCESSION' File.\n \n is available. To designate local label routines on a printer by printer\n \n 69.9 LABORATORY SITE (Partial Definition)\n Note: You already have the 'LABORATORY SITE' File.\n \n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n basis see the section on POST-INSTALLATION INSTRUCTIONS item #1.\n \n DEVICE: HOME// VIRTUAL TERMINAL\n \n \n Install Started for LR*5.2*161 :\n May 02, 1997@17:14:54\n \n Installing Routines:\n May 02, 1997@17:15:09\n \n To designate local label routines on an accession area basis see the\n Running Pre-Install Routine: PRE^LR161\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n *** Pre install completed ***\n \n Installing Data Dictionaries:\n May 02, 1997@17:15:45\n section on POST-INSTALLATION INSTRUCTIONS item #2 and complete the\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n May 02, 1997@17:15:46\n \n LR*5.2*161 \n \n Running Post-Install Routine: POST^LR161\n \n fields ALTERNATE LABEL ENTRY (#5.2) and ALTERNATE LABEL ROUTINE (#5.3)\n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n Updating Routine file...\n \n Updating KIDS files...\n \n in the ACCESSION file (#68).\n LR*5.2*161 Installed.\n May 02, 1997@17:16:09\n \n \n Install Completed\n \n \n Select Installation Option:\n \n \n \n End of example install\n \n *****************************************************************************\n \n \n POST-INSTALLATION INSTRUCTIONS\n ------------------------------\n \n The following actions should be performed by the Lab Information Manager \n (LIM) or the person(s) responsible for the maintenance of the files LABORATORY\n 6. The ability to print test urgencies on a label exists. Sites can\n SITE (#69.9) and ACCESSION (#68).\n \n 1. If a site is using local label routines or the Intermec 4100 label\n printers to print lab labels then perform the following steps.\n \n To define local label routines on a printer by printer basis, complete\n fields ALTERNATE LABEL ENTRY (#.04) and ALTERNATE LABEL ROUTINE (#.05).\n \n a. Define printers in the LABEL DEVICE multiple field (#360) in the\n LABORATORY SITE file (#69.9).\n \n designate on an individual urgency basis if the urgency is to print.\n \n *** Start of example ***\n Select OPTION: 1 ENTER OR EDIT FILE ENTRIES\n \n INPUT TO WHAT FILE: LABORATORY SITE//\n EDIT WHICH FIELD: ALL// LABEL DEVICE (multiple)\n EDIT WHICH LABEL DEVICE SUB-FIELD: ALL// ?\n Answer with LABEL DEVICE SUB-FIELD, or NUMBER\n Choose from:\n .01 LABEL DEVICE\n The urgency that is printed will be the highest urgency of all the\n .02 PRINTER TYPE\n .03 LABEL STOCK\n .04 ALTERNATE LABEL ENTRY (see note on FILE SECURITY)\n .05 ALTERNATE LABEL ROUTINE (see note on FILE SECURITY)\n .06 DEFAULT ACCESSION AREA\n FOLLOW A FIELD NAME WITH ';"CAPTION"' TO HAVE THE FIELD ASKED AS\n 'CAPTION: ' OR WITH ';T' TO USE THE FIELD 'TITLE' AS CAPTION\n EDIT WHICH LABEL DEVICE SUB-FIELD: ALL//\n THEN EDIT FIELD:\n \n tests on the accession. The highest urgency is determined as the\n \n Select LABORATORY SITE SITE NAME: 'name of your site'\n Select LABEL DEVICE: IRM DEVELOP INTERMEC\n LABEL DEVICE: IRM DEVELOP INTERMEC//\n PRINTER TYPE: INTERMEC 4100// ?\n Choose from:\n 0 OTHER\n 1 INTERMEC 4100\n PRINTER TYPE: INTERMEC 4100//\n LABEL STOCK: 2.5X4 10 PART// ?\n urgency with the lowest internal entry number in the URGENCY file\n Choose from:\n 0 OTHER\n 1 15/16X3\n 2 1X2\n 3 2.5X4 10 PART\n LABEL STOCK: 2.5X4 10 PART//\n ALTERNATE LABEL ENTRY: ?\n Answer must be 1-8 uppercase alpha and/or numeric characters in\n length. Site can enter an alternate label entry point to be used\n instead of the standard lab label routines used by the lab package\n (#62.05). Sites can designate a 1-5 character abbreviation that will\n when printing labels using this device. Field ALTERNATE LABEL\n ROUTINE (#.05) must be completed for the software to use this field.\n (see note on FILE SECURITY)\n ALTERNATE LABEL ENTRY:\n\n ALTERNATE LABEL ROUTINE: ??\n Answer must be 1-8 uppercase alpha and/or numeric characters in\n length. Site can enter an alternate label routine to be used \n instead of the standard lab label routines used by the lab package\n when printing labels using this device.\n be printed as the urgency. See the section on POST-INSTALLATION\n (see note on FILE SECURITY)\n ALTERNATE LABEL ROUTINE:\n \n DEFAULT ACCESSION AREA: ??\n Select accession area to use for default characteristics.\n This field is used by the label software when printing test\n or future order labels. When printing these types of labels\n there is no accession area identified to determine label\n characteristics such as type of barcode or accession\n area alternate label routine.\n INSTRUCTIONS item #3.\n \n The accession area designated for this device will be used\n by the software to obtain accession area specific\n characteristics when printing labels which are not associated\n with any particular accession area. Examples of these\n characteristics are barcode type, number of pad digits\n for barcode number, and alternate label routine.\n \n *** End of example ***\n \n \n b. Program the Intermec 4100 label printer with new formats using\n the Lab Bar Code Label Formatter option [LR BAR CF] located on\n the Lab liaison menu [LRLIAISON]\n \n \n 2. Edit the following fields in the ACCESSION file (#68), to set up the\n bar code parameters and/or local label routines for each accession\n area.\n \n *** Start of example ***\n 7. The Reprint accession label(s) option [LRLABXT] has been enhanced to\n \n Select OPTION: 1 ENTER OR EDIT FILE ENTRIES\n \n \n INPUT TO WHAT FILE: ACCESSION//\n EDIT WHICH FIELD: ALL// 5 BAR CODE PRINT\n THEN EDIT FIELD: 5.1 BAR CODE PAD\n THEN EDIT FIELD: 5.2 ALTERNATE LABEL ENTRY (see note on FILE SECURITY)\n THEN EDIT FIELD: 5.3 ALTERNATE LABEL ROUTINE (see note on FILE SECURITY)\n \n allow printing selected accessions.\n \n Select ACCESSION AREA: CHEMISTRY\n BAR CODE PRINT: CODE39 WITH CHECK DIGIT// ??\n This field is used by the label print utilities to determine if\n bar code labels should be printed for this accession area.\n Choose from:\n 0 NONE\n 1 YES\n 2 CODE39\n 3 CODE39 WITH CHECK DIGIT\n This patch will address enhancements and fixes to Lab label printing.\n \n 4 CODE128\n BAR CODE PRINT: CODE39 WITH CHECK DIGIT//\n BAR CODE PAD: ?\n Type a Number between 1 and 15, 0 Decimal Digits\n Enter the number of zeros ("0") to pad an accession number when\n printing a bar code using the accession number. Used when site\n needs a minimum length bar code on labels.\n \n Example if need a four digit bar code then enter four.\n This would produce the following:\n 8. The Print future collection labels option [LRUFCL] has been enhanced\n Accession number Bar Code\n 1 0001\n 12 0012\n 123 0123\n 1234 1234\n 12345 12345\n \n ALTERNATE LABEL ENTRY: ?\n Answer must be 1-8 uppercase alpha and/or numeric characters\n in length.\n to allow selection of a range of collection types. The collection type\n Site can enter an alternate label entry point to be used instead of\n the standard lab label routine entry point defined in file\n LABORATORY SITE (#69.9).\n \n This field overrides the label routine settings in file LABORATORY\n SITE (#69.9) for this accession area. Field ALTERNATE LABEL ROUTINE\n (#5.3) must be completed for the software to use this field.\n See description of field #5.3.\n (see note on FILE SECURITY)\n ALTERNATE LABEL ENTRY:\n WARD COLLECT is now selectable. A user can select one or more types\n ALTERNATE LABEL ROUTINE: ?\n Answer must be 1-8 uppercase alpha and/or numeric characters\n in length.\n Site can enter an alternate label routine to be used instead\n of the standard lab label routine defined in file LABORATORY\n SITE (#69.9).\n \n This field overrides the label routine settings in file LABORATORY\n SITE (#69.9) for this accession area. It is used in conjunction\n with field ALTERNATE LABEL ENTRY (#5.2) for building the\n when printing future collection labels.\n variable LRLABEL.\n (see note on FILE SECURITY)\n ALTERNATE LABEL ROUTINE:\n \n Select ACCESSION AREA:\n \n \n 3. Edit new fields LABEL PRINT (#5) and ABBREVIATION (#6) in the URGENCY\n file (#62.05) using FileMan's Enter/Edit option.\n \n \n Select OPTION: 1 ENTER OR EDIT FILE ENTRIES\n \n INPUT TO WHAT FILE: URGENCY//\n EDIT WHICH FIELD: ALL// 5 LABEL PRINT\n THEN EDIT FIELD: 6 ABBREVIATION\n THEN EDIT FIELD:\n \n \n Select URGENCY: ROUTINE\n LABEL PRINT: YES// ?\n 9. Fixed the null subscript error in array variable LRBAR when the\n Select if abbreviation is to be printed.\n Choose from:\n 0 NO\n 1 YES\n 2 YES, REVERSE FIELD\n LABEL PRINT: YES// ??\n Determines if urgency's abbreviation is to be printed on labels.\n If "YES, REVERSE FIELD" is selected and label printer supports\n reverse field printing, then abbreviation will be printed with\n white letters on a black background.\n variable LRAA was undefined.\n Choose from:\n 0 NO\n 1 YES\n 2 YES, REVERSE FIELD\n LABEL PRINT: YES//\n ABBREVIATION: ROUT\n \n Select URGENCY:\n \n \n NOIS GRJ-0395-50211\n *** End of example ***\n \n \n 10. Fixed printing of information in the wrong fields on the Intermec 4100\n 10-part labels. There was an extra carriage return being sent to the\n printer which was moving the accession and other information into the\n wrong fields.\n NOIS BUF-0695-13329\n \n 11. Fix an undefined variable error, usually LRAN, when printing test labels.\n All standard required lab variables will be defined when printing test\n labels.\n NOIS BAN-1097-11647, DAY-0497-42491, GRJ-0796-50216\n 1. The ability to designate label stock on a printer by printer basis\n \n 12. Fixed formatting the SSN on the 10-part label. There was an extra\n carriage return being sent to the printer which was moving the SSN\n into the next field.\n NOIS BIG-0596-71566\n \n 13. Fixed a problem in the Reprint accession label(s) option [LRLABXT]\n in which a user, after selecting the label device, would encounter\n a "Device Unavailable" message. This error was caused by the opening,\n closing, and reopening of the label device.\n is available. This is used for printing with the Intermec label\n NOIS PRO-0196-10343\n \n 14. Adjusted the label field positioning. Position of the field on label\n was near the edge which left little room for variation in label stock\n positioning.\n NOIS GRJ-1095-52265\n \n 15. When the list of tests are printed on accession labels the software\n attempts to print as many test abbreviations as will fit within the\n dimensions of the label. Some of the label formats, specifically the\n\n\n This patch to the Laboratory package does not contain any changes to\n 1. When patch LR*5.2*153 was released it contained changes to the code\n LRX 14065673 13923654 65,153,201,217\n \n INSTALLATION INSTRUCTIONS\n -------------------------\n The install time for this patch is less than 2 minutes. This patch\n can be installed when Laboratory users are on the system.\n However the following conditions apply:\n \n - Accessioning should not be occurring.\n Patch installation needs to be coordinated with the Laboratory\n in routine LRX used to create the UID. These changes performed a\n Information Manager (LIM/ADPAC).\n \n NOTE: MailMan and KERNEL patches must be current on the target system to\n avoid problems loading and/or installing this patch.\n \n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n check to determine if the UID that was to be created already existed.\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n The intent is to prevent the same UID being assigned to two or more\n \n 6. If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routine in your\n production account to the routine in the patch by using the 'Compare\n a Transport Global to Current System' option. These options can\n both be found under the 'Installation' menu.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*217'. When prompted 'Want to\n accessions. If the UID already existed then routine LRX created an\n DISABLE Scheduled Options, Menu Options, and Protocols? YES//',\n choose 'NO'.\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LR217 can be deleted after successful patch installation.\n \n \n *****************************************************************************\n Below is an example of the dialogue seen during the KIDS install:\n alternate UID substituting the accession area's numeric identifier\n \n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*217 Loaded from Distribution 8/28/98@15:5\n7:39\n => LR*5.2*217\n \nThis Distribution was loaded on Aug 28, 1998@15:57:39 with header of\nLR*5.2*217\nIt consisted of the following Install(s):\n with "00".\nLR*5.2*217\n \n LR*5.2*217\nWill first run the Environment Check Routine, LR217\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*217\n \n \n \n \nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n The code used to produce an alternate UID was setting a lock on\n \n \n Install Started for LR*5.2*217 :\n Aug 28, 1998@15:58:32\n \n Installing Routines:\n Aug 28, 1998@15:58:32\n \n Running Pre-Install Routine: PRE^LR217\n \n the global LRO(68,"C",uid) which was not being released.\n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n LR*5.2*217\n \n *** Pre install completed ***\n \n Running Post-Install Routine: POST^LR217\n \n the VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 97-033\n This caused other lab users to "hang" until the user with the lock\n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n Updating Routine file...\n \n Updating KIDS files...\n \n logged off and the lock was released. This condition has been found\n LR*5.2*217 Installed.\n Aug 28, 1998@15:58:34.\n \n Install Message sent #10909944\n \n Install Completed\n \n \n \nSelect Installation Option:\n to occur under three scenarios.\n \n \n \nEnd of example install\n \n *****************************************************************************\n \n The first is when a site switches the numeric identifier for an\n accession area and the identifier has been previously used.\n The second is when a site has modified the data dictionary for field\n NUMERIC IDENTIFIER (#.4) in the ACCESSION file (#68) to allow more\n than one accession area to have the same identifier. The third is\n explained in #2 below.\n titled VISTA BLOOD BANK SOFTWARE VERSION 5.2.\n \n See FileMan's field Description for fields TYPE OF ACCESSION NUMBER\n (#.092) and NUMERIC IDENTIFIER (#.4) in the ACCESSION file (#68)\n for further information.\n \n Solution: modified code in routine LRX to remove setting lock on\n global LRO(68,"C",uid). Since the routine also lock/unlocks\n global node LRO(68,"C"), this lock is not neccessary.\n \n NOIS CTX-0798-71641, PAL-0898-60857, PUG-0498-51586, LAS-0798-60721\n \n \n 2. It has been found that under the following conditions the code to\n create an accession's UID was being called twice. This resulted in\n the UID for the accession being changed to a UID that began with\n "00" even if the original UID was unique. This would occur when a\n site has accession areas in parallel and the parallel accession\n area has a lower internal entry number in the ACCESSION file (#68).\n \n Example: Accession area "B" is in parallel with accession area "A".\n Accession area "B" has a lower internal entry number in file\n \n ACCESSION (#68). When building acccessions from an order\n the accessions are created based on the internal entry\n number in the ACCESSION file (#68). In this example, the\n acccession for accession area "B" would be created first.\n But since it's in parallel with accession area "A" the\n software first creates an accession for accession area "A",\n then uses acccession area's "A" accession number for\n accession area's "B" accession. Next when the Lab software\n attempted to put tests on accession area "A" it detected\n that the UID existed and generated the alternate UID using\n This patch will address a locking problem concerning the LRO global and\n "00" as the NUMERIC IDENTIFIER even though it was the\n same accession.\n \n Solution: modified code in routine LRX to only generate an alternate\n UID if the UID exists and is not for the same accession.\n NOIS PUG-0498-511586\n\n \n Associated NOIS\n --------------\n a fix to Laboratory Unique Identifier (UID) creation.\n \n CTX-0798-71641\n LAS-0798-60721\n PAL-0898-60857\n PUG-0498-51586\n \n Test Sites\n ----------\n \n Central Texas HCS\n \n Las Vegas VAMC\n Milwaukee VAMC\n Palo Alto VAMC\n Puget Sound HCS\n \n ----------------------------\n \n ROUTINE SUMMARY\n ---------------\n \n \n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n CHECK^XTSUMBLD results\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- --------------\n LR217 N/A 2463818 217\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis patch corrects a problem where the comments were missing from\nthe Long Form Accession List (LRACC1) option.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nPatch LR*5.2*127 is required to be installed.\nRoutines Before Check Sum After Check Sum Patch List\n==================================================================\n \nLRCAPPH 10523848 10492287 1,19,127,136\n \n===================================================================\n \nNote: Patch LR*5.2*127 MUST be installed before this patch is installed. \n \n1. Users may remain on the system.\n \n2. No options need be placed out of order.\n3. Install patch during non-peak hours.\n4. Laboratory specimens should not be accessioned or verified during\ninstallation of the patch.\n5. Auto-instrument LAB routines does not have to be stopped.\n \nNOIS List\nMIN-0996-41784\nMIA-1096-30234\n1) This patch corrects the problem of multiple LRCAPPH jobs running and\nthe same time when only one is required. This problem appears when the\nsystem has slow response times and LRCAPPH jobs begin to accumulate.\n \n2) This patch also correct a variable used to for system response\nmonitoring.\n \n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis patch fixes the problem of not being able to choose the option Interim\n 4 Interim reports for 1 location (manual queue) \n\n The option Interim report for selected tests [LRRP3] could not be chosen. \n This patch resolves this problem by changing the menu text of the option \n [LRRP3] from Interim report for selected tests to Interim report for chosen \n tests. \n\n Reference NOIS: MAN-0496-12206 \n \n Reporting Site: Manchester, NH \nreport for selected tests [LRRP3] from the Ward Lab Menu. \n\n Test Site(s): \n \n \n Installation Instructions: \n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package in this message onto your system. \n 2. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n\n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n 3. Users may remain on the system, but installation should be done at \n off peak hours. \n 4. From the 'Installation Menu' of the KIDS menu, run the option \n 'Install Package(s)' Select the package 'LR*5.2*176' and proceed \n Before this patch: \n with the install. \n 5. Delete routine LR176. \n\n\n Select Ward lab menu Option: Interim \n 1 Interim report \n 2 Interim report by provider \n 3 Interim report for selected tests as ordered \n\n
\nSee National Patch Module for LR*5.2*214.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis patch corrects two problems:\nIND-0498-41683) is encountered when attempting to add a patient through\nthe LRDPA routine. After installing patch LR*5.2*153, general lab users\ncan no longer add patients to the PATIENT file (#2) even though the\nALLOW LAB TO ADD PATIENTS field (#13) of the LABORATORY SITE file (#69.9)\nis set to YES. Part of patch LR*5.2*153 was intended to eliminate first\nlevel addition of entries to the Patient file, but provide a second level\nentry. Patch LR*5.2*211 restores this second level entry ability.\n1. The first problem (as reported by Washington in NOIS # WAS-1297-20917)\nis encountered when using the VIC card magnetic stripe to identify\npatients within the Lab module. Prior to patch LR*5.2*211, the system\nwould not recognize the data transmitted from the Veteran's ID Card as a\nvalid patient identifier. With the installation of patch LR*5.2*211, the\ndata contained in the magnetic stripe will be interpreted appropriately.\n \n2. The second problem (as reported by Indianapolis in NOIS #\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\n \n \nERD 07/30/1998 09:32 4.0 L 5.0 12 L 13 L 14 L\n \n Patch 225 corrects the output to look like:\n \nERD a 07/30/1998 09:32 4.0 L 5.0 12 L 13 L 14 L\n Patch 201 inadvertently removed the indicator that designated which\n comment went with which result on the cumulative reports. This only\n affected the horizontally formatted reports. The following is an\n example of the output prior to patch 201.\n \nERD a 07/30/98 09:32 4.0 L 5.0 12 L 13 L 14 L\n \n After patch 201 the output resembled:\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nLab Archiving Enhancement Patch\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis patch includes the routines, files and data dictionary changes\nto support CPRS version 1. It is included with the CPRS Master build\nand should not be installed independent of CPRS. Refer to the CPRS\nInstallation Guide for installation instructions.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nNLT Mapping to LOINC LR*5.2*215\nVeteran Affairs, has agreed to use LOINC to identify test results.\n\nNLT Mapping to the Logical Observation Identifier Names and Codes (LOINC)\nhas the following features:\n\nProvides a method to communicate across laboratories in support of Clinical\nInformation Resource Network (CIRN) by mapping VistA lab test to LOINC codes.\n\nProvides sets of universal names and ID codes for identifying laboratory\nand clinical test results.\nThe purpose of the National Laboratory Test (NLT) Mapping to the Logical\n\nAllows the creation of a uniform naming convention for clinical terms.\n\nAllows the merging of clinical data across sites (where terminology may vary\nwidely.)\n\nRequires the adoption of naming or coding conventions, and the mapping of\nlocal terminology to these conventions.\n\nMaps the WKLD CODE file(#64) file to LOINC codes.\nObservation Identifier Names and Codes (LOINC) is to provide the mapping of\nChemistry tests result codes, and the standardization of files used in the\nLaboratory Software Package. Standardizing codes allows the movement of\ntests results from one computer system to another. This includes sharing\ninformation with both Veterans Health Information Systems and Technology\nArchitecture (VistA) and Non-VistA computer systems. The LOINC committee\nincluding the largest clinical laboratories in the United States, and\n\n
\nLR*5.2*239 FIX FOR LR*5.2*215\n\n
\nThis patch provides a link between Anatomic Pathology and the Women's\nHealth Program. For full details see the patch message in the Forum Patch\nModule.\n\n
\nRECONCILE AUTOPSY DATA DISCREPANCY\n \nUpon investigation, it has been determined that in-patient autopsy numbers for\npatients whose treating specialty had changed since they were originally logged\nin, were being totaled in the wrong treating specialty, or omitted from the\nreport all together. This resulted in subtotals not reconciling back to the\ngrand total. The solution is to create an 'Exceptions List' at the bottom of\nthe report. This list displays the autopsy accession number, it's current\ntreating specialty from the FACILITY TREATING SPECIALTY field (#.09) of the \nPATIENT MOVEMENT file (#405), and its original treating specialty from the\nTREATING SPECIALTY AT DEATH field (#14.6) of the LAB DATA file (#63). It also\n \ndisplays the total number of exceptions listed. The subtotals by treating\nspecialty plus the total number of exceptions now reconciles back to the grand\ntotal number of autopsies performed. This also gives the site the necessary\ninformation to update the LAB DATA file (#63) with the current treating\nspecialty number.\nThis patch corrects a problem with option [LRAPQOR] QA Outcome Review Cases.\nThis report's function is to break out by treating specialty, the number of\nautopsies performed over a given period of time. On the last page of the\nreport, it lists the total number of autopsies performed in the given date\nrange. Under this total, the number of autopsies, subtotaled by treating\nspecialty, are listed. These subtotals are not reconciling back to the grand\ntotal number of autopsies.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nPatch LR*5.2*221 VISTA BLOOD BANK SOFTWARE\n \nEKH-0998-40137, GAI-0898-30690, GNH-0498-41065, HAM-0898-21544,\nHUN-0798-20942, LEB-1298-22078, LOM-0498-60884, NAS-1098-31373,\nOKL-0698-70962, PHI-0598-20045, PHO-1298-60877, SDC-0598-60879,\nSLC-0998-50822, WIC-0898-41805, WPB-1198-31834, WAS-1098-31246,\nWNY-0998-11152, BAY-0798-31877, FHM-0897-51017, NCH-0596-40125,\nCLA-0598-20356, CIN-0998-41790, CMO-0998-41772, COS-0898-41373,\nNJH-1298-21603, EKH-0998-40488, GAI-0698-31676, MWV-0598-21363,\nSAM-1098-20301, IOW-1298-41014, BAN-0897-11956, PHO-0798-60573,\nCHS-0398-42380, MAD-1098-41673,\n \n1. Routines LRCENDEL, LROS, LRTSTJAN, and LRTSTOUT have been modified to\nTest Sites:\n===========\nLong Beach, CA\nMilwaukee, WI\nLoma Linda, CA\nNorth Chicago, IL\nWest Palm Beach, FL\n \nAdded Cross Reference:\n=====================\naccommodate the new ordered test status of NOT PERFORMED.\n--A new 'AE' MUMPS cross-reference has been created in the LAB ORDER (#69)\nfile, Subfile SPECIMEN # (#1), subfile TEST (#6), field CANCEL BY (#10).\nThis X-Ref is used to identify canceled test that must be sent to PCE for\ncredit. The data can be used by the billing software.\n \nDATA Dictionary Changes:\n========================\nACCESSION file (#68):\nThe *RESULT field (#5) of the Test subfield (#68.04) name has been changed\nto DISPOSITION field (#5).\n \n \nLAB ORDER ENTRY file (#69):\nA new cross-reference has been created on the CANCEL BY field (#10) of the\nTEST subfield (#69.03) to track tests which have disposition of Not\nPerformed.\n \nLOAD/WORKLIST file (#68.2)\nA new UID VERIFICATION field (#2.1) has been added to the LOAD/WORKLIST\nfile (#68.2), PROFILE multiple (#50).\n \n2. The ACCESSION file (#68), subfile (#68.04), *RESULT field (#5) marked\nLAB DATA file (#63)\nThe LOCATION field (#14.1) in the LAB DATA file (#63) input transform has\nchanged to conform to FileMan Version 22 variable cleanup.\n \nChanges Made By Patch LR*5.2*221:\n=================================\nIn the past, laboratory users were able to delete all traces of an order\nand specimens from various files (database). This would create a\ndiscrepancy between ward-printed documents and laboratory data files. In\naddition, if the tests were downloaded to automated instruments or LEDI\nfor deletion several years ago has been renamed to DISPOSITION field (#5).\nHost Laboratory, the result entry could produce corrupt Laboratory patient\nrecords.\n \nIt was also possible in certain situations for deleted accession numbers\nor order numbers to be assigned to two different patients.\n \nThe major component of this patch is to maintain a record of all ordered\nprocedures, ensuring that integrity of accession numbers is preserved.\nThis is accomplished in the following manner:\n \nThis DISPOSITION field (#5) is used to enter a DISPOSITION status for an\n1. Accessioned tests must be either canceled (canc), result entered and\nverified (this includes entering test comment) or designated 'Not\nPerformed' and a reason entered. The date, time, and the person entering\nthe 'Not Performed' reason will be stored in the laboratory patient\nrecord. In addition, the ACCESSION file (#68), and where appropriate, LAB\nORDER ENTRY file (#69) will be updated to reflect the 'Not Performed'\nstatus. The CPRS order status is changed to completed if 'SERVICE\nCORRECTION' is used as the 'Cancellation Reason'.\n \n2. If the site makes use of Interim Reports, in addition to the current\naccessioned test that is NOT PERFORMED.\nfunction, the software will also display those accessions that have the\nstatus of 'Not Performed'. The software will not display the 'Not\nPerformed' tests if there are any results entered but not verified.\n \n3. If it is determined at a later point, that a 'Not Performed' test\nshould be performed, the software will allow results to be entered and the\n'Not Performed' reason can be removed by the user.\n \n4. The new 'Not Performed' test status corrects numerous problems with\nRemove An Accession [LRDELOG] option or Delete Entire Order or individual\n \ntests [LRCENDEL] option were being used.\n \n***** CAUTION ****** CAUTION ****** CAUTION\nONCE AN ACCESSION NUMBER HAS BEEN ASSIGNED IT CANNOT BE DELETED!\nTHIS NEW RESTRICTION MAY CAUSE CONCERN IN CERTAIN AREAS OF THE LAB THAT\nMAKE A PRACTICE OF DELETING AN ACCESSION NUMBER AND RE-ASSIGNING IT TO A\nDIFFERENT PATIENT IN ORDER TO CORRESPOND TO MANUAL LOG BOOK ENTRIES. THIS\nPRACTICE OF RE-ASSIGNING ACCESSION NUMBERS SOMETIMES OCCURS IN HISTOLOGY\nAND CYTOLOGY DEPARTMENTS\n \n3. The LAB DATA file (#63), Service field (#14.1) was modified to include\nRoutine Summary:\n================\nThe second line of the routine now looks like:\n \n<tab> ;;5.2;LAB SERVICE;**[patch list]**;Sep 27,1994 \nRoutines: Before After Patch\n Check Check List\nLR221 N/A 2442952 221\nLR7OF5 10004887 10037595 223,221\nLR7OMERG 21447925 16402501 121,221\nVersion 5.2 DEVICE PRODUCT LABELING STATEMENT\nan input transform. This modification is consistent with the changes being\nLRCAPDSS 6043551 6167016 127,143,201,221\nLRCAPF 7808609 9622392 221\nLRCAPV1 11760779 12202571 42,119,153,221\nLRCAPV1S 4411865 4411858 42,153,201,221\nLRCAPV2 8985145 9018506 105,119,153,221\nLRCENDE1 11027407 10883548 100,107,121,201,202,221\nLRCENDEL 13496869 16365039 100,121,202,221\nLREXPD 4933677 4944336 153,201,221\nLRGEN1 9235134 7874566 201,221\nLRGEN2 14904638 15112799 121,153,221\nexported as part of VA FileMan V. 22.\nLRGP2 8849923 3525048 153,221\nLRLLS 8810252 12800210 116,221\nLRNUM 6162203 6523065 153,221\nLROE 15763453 14732765 100,121,201,221\nLROS 15245747 16807258 121,153,202,210,221\nLRPHEXPT 9259926 8575322 43,121,221\nLRPHITE1 11566534 11190758 100,121,198,202,208,221\nLRPHITE2 3592550 1527153 221\nLRPHITE3 2560860 2178370 100,198,208,221\nLRPHITEM 13730844 14270617 121,198,208,202,221\n \nLRPHSET1 7250784 7343884 121,191,221\nLRRD 8518062 8518201 221\nLRRP 11903812 11856365 195,221\nLRRP1 7537640 7638502 153,221\nLRRP2 13108827 14561533 106,121,221\nLRTOCOST 22163690 23554251 153,201,221\nLRTSTJAN 16094468 7681779 67,100,121,128,202,221\nLRTSTOUT 12155453 19411504 100,121,153,202,221\nLRTT5P1 12006801 12297887 153,221\nLRVER3 14057782 14311842 42,100,121,140,171,153,221\nThe above software changes have been reviewed by the VISTA Blood Bank\nLRVER3A 9513672 9561045 1,5,42,100,121,153,190,221\nLRVR1 10934986 11269859 42,153,221\nLRVR4 11173968 8714660 14,42,121,153,221\nLRVRA 6096750 6318899 153,221\nLRVRW 9712499 8795650 153,221\nLRWD 1493513 1464262 121,221\nLRWRKIN1 3732368 9653815 153,201,221\nLRWRKINC 12813235 19863974 153,201,221\nLRWRKLST 9498844 9455120 1,17,38,153,185,221\n \nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE V.\nRequired Patches:\n=================\nLA*5.2*27\n \nLA*5.2*47 [Note: This is the Automated Instrument portion of LR*5.2*221]\n \nLR*5.2*116\nLR*5.2*121\nLR*5.2*153\nLR*5.2*185\n5.2 controlled functions.\nLR*5.2*190\nLR*5.2*191\nLR*5.2*195\nLR*5.2*201\nLR*5.2*202\nLR*5.2*223\n \nInstallation Instructions:\n==========================\nThis patch is compatible with OERR 2.5 and both versions of CPRS.\n \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the\n PackMan menu. This option will load the KIDS\n package onto your system.\n 2. Review your mapped set. If the routines are\n mapped, they should be removed from the mapped set\n at this time.\n \n 3. The patch has now been loaded into a Transport\n global on your system. You now need to use KIDS to\nPROBLEM: A new disposition for accessioned tests called NOT PERFORMED has\n install the Transport global.\n \n On the KIDS menu, under the 'Installation' menu,\n use the following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation \n should be done during off peak hours and when\nbeen created. This disposition is assigned to a test that is not performed\n the Laboratory computer users are idle.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 10 minutes during\n offpeak hours, and less than 15 minutes during\n peak hours which is NOT RECOMMENDED.\n 7. Installation of this patch does not require any\n additional memory space.\n 8. From the 'Installation Menu' of the KIDS menu,\n run the option 'Install Package(s)'. Select the\n package 'LR*5.2*221' and proceed with the\nfor any type of reason. This will replace the past practice of canceling\n install.\n 9. If any routines were unmapped as part of step 2,\n they should be returned to the mapped set once\n the installation has run to completion.\n \nEnhancements:\n=============\n1. The 'Etiology WKLD Code (Force)' [LRCAPF] option has been corrected to\naccept WKLD Codes that do not have the suffix code of .0000 (Generic).\nNOIS: CHY-0798-51245\n=============================================\nor deleting tests which had no results entered.\n \n2. The WKLD Code capture routines have been modified not to count tests\nmarked as 'Not Performed'.\n \n3. The 'Delete entire order or individual tests' [LRCENDEL] option has\nbeen modified to place tests in the status of 'Not Performed' rather than\ndeleting the test or order from the file (database). Thus preventing\nelectronic white out of the ordered procedures. This enhancement corrects\nproblems of undefined errors after tests have been deleted. NOISs:\nALN-1198-11196, ASH-0898-30554, ATG-0698-31312, WNY-0698-11221,\n \nCLA-0598-20635 CMO-1198-41253, DEN-0898-50267, DUB-0898-30615,\nFGH-1198-32348, GAI-0698-32344 HAM-1098-21436, LAS-0698-60208,\nLEX-0898-41581, LEX-1198-40049, OM-0498-60788, MIN-0798-40025,\nMON-0798-51662, MUS-1098-71863, NAS-1098-31373, OKL-0698-71939\nSAG-0498-42248, SLC-1198-50813, TAM-0798-30677, AM-1298-31153,\nTOG-0898-11351\n \n4. The 'General report for selected tests' [LRGEN] option has been\ncorrected to display the full year and century with test results properly\naligned when less than 19 tests were requested. There are hosts of\nRISK ANALYSIS: Changes made by patch LR*5.2*221 have no effect on Blood\nassociated NOIS called. This may not represent a complete list. NOISs:\nLEB-1298-22078, TAM-1298-31153, CLA-1198-22013, ALX-1198-71715,\nALX-0898-71684, ASH-0898-30675, BEC-0998-20129, BYN-0598-11025,\nDAY-0798-42525, DEN-1098-50461, EKH-0998-40137, GAI-0898-30690,\nGNH-0498-41065, HAM-0898-21544, HUN-0798-20942, LEB-1298-22078,\nLOM-0498-60884, NAS-1098-31373, OKL-0698-70962, PHI-0598-20045,\nPHO-1298-60877, SDC-0598-60879, SLC-0998-50822, WIC-0898-41805,\nWPB-1198-31834\n \n5. The 'Group Verify (EA, EL, EW)' [LRGV] option has been enhanced to\nBank Software V. 52 functionality, therefore RISK is none.\nstore the Result NLT code with the verified results. The user cannot\ndirectly observe this.\n \n6. The Clear instrument/worklist data [LRINSTCLR] option has been\nenhanced. The changes to this option implements selective clearing of\ninstrument data from the LAH global. When entries are made in the LAH\nglobal to store instrument data pending verification, the date of creation\nand result updating is now recorded. This date will be used to selectively\nremove data from the LAH global based on the date original result was\nreceived or last updated.\n \n \nThe Clear instrument/worklist data [LRINSTCLR] option will now allow\nclearing by either of the following ways:\n \na. Data received before the selected date (optional time) is purged. If\nyou enter a date only then data received before that date is cleared. \n \nb. If you enter a date/time then data received before that date/time is\ncleared.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*221 does not\nExample:\n \nIf you enter Sept 4, 1998 then data received through Sept 3, 1998 is\ncleared. If you enter Sept 4, 1998 @1200 then data through Sept 4, 1998\n115959 is cleared.\n \nThe following routines support this enhancement:\n \na. LAGEN - Changes made to set date/time of entry creation and last\nupdate. Last update can be different than creation date if data is\nalter or modify any software design safeguards or safety critical element\nretransmitted (overlay data = yes) or additional results received.\n \nb. LRLLS - Clear instrument data option that does actual clearing based on\nuser's parameters. User can purge by date/time or blanket purge when using\noption Clear instrument/worklist data [LRINSTCLR].\n \nc. LRVR1 - Verifying routine with changes to setup date/time information\nwhen manual data entry is used during Enter/Verify Automated Instrument\n[LRVR] option.\n \nfunctions.\nd. LRVRW - Verifying routine with changes to setup date/time information\nwhen load/work list data entry is used during the Enter/verify data (Work\nlist) [LRVRW] option. \n \ne. If during the clearing process an entry in LAH is found with no\ndate/time for creation/update then the current date/time is added to the\nentry. This entry is then eligible for clearing the next time the option\nis run and it meets the date/time parameter.\n \n \n \n7. The routine LRNUM has been modified to control the echo of stored data.\nThis is not readily apparent to the user.\n \n8. The 'Order/test status' [LROS] option has been enhanced to display\ntests having the 'Not Performed' status. Also spacing was increased to\naccommodate accession area abbreviation of 5 characters. NOIS:\nWAS-1098-31246\n \n9. The 'Itemized routine lab collection' [LRPHITEM] option and 'Receipt of\nroutine lab collection from wards' [LRPHEXCPT] option has been enhanced to\nPOTENTIAL IMPACT ON SITES: This patch contains changes to files and\nconform to the 'Not Performed' status assignment. Order and accessioned\ntests are no longer deleted. NOIS: WNY-0998-11152\n \n10. The 'Interim report' [LRRP2] option has been enhanced to display\norders that contain only 'Not Perform' status and no results entered or\nverified.\n \n11. The option 'Turnaround times By Urgency' [LR TAT URGENCY] has been\nmodified to count only those tests that have been counted for Workload. In\norder for a test to be counted it must have WKLD Code assigned and\n \nroutines identified in Veterans Health Administration (VHA) Directive\nverified results. NOIS: BAY-0798-31877\n \n12. Various non-Microbiology Result Entry options were modified to\naccommodate 'Not Performed' test status.\n \n13. The option 'Ward lab menu' [LRWARDM] entry action routine has been\ncorrected not to set the variable LREND if no ward is selected. If no ward\nwas selected unpredictable software behavior could result. NOISs:\nFHM-0897-51017, NCH-0596-40125, CLA-0598-20356\n14. The INCOMPLETE TEST STATUS REPORT [LRWRKINC] option sorting/searching\n97-033. The changes have no effect to Blood Bank functionality or medical\ncapability was enhanced.\n \nExample:\n \nIf you answer "YES" to the prompt: Specify detailed sort criteria? No//\nThen you will be able to specify:\n \n - If controls should be excluded.\n - Specific tests to search for.\n - A lab arrival time. This will exclude uncollected specimens, \ndevice control functions. There is no adverse potential to sites.\n and specimens with a later arrival time.\n - Exclude non-required tests.\n - Exclude selected test(s) from report.\n - If report is generated for specific test(s) which are \n panels, then the user can have the report check the tests that\n make up the panel.\n \n15. The 'Incomplete test status report' [LRWRKINC] option has been\nmodified to honor tests having 'Not Performed' status and not include them\non the incomplete test list.\n \n \n16. Test that have rolled over can be verified by either the original\naccession number or the rolled over accession number and the test will be\nmarked completed on both accession numbers. NOISs: CIN-0998-41790,\nCMO-0998-41772, COS-0898-41373, NJH-1298-21603\n \n17. Correct problem of the Collection List not assigning correct accession\nnumbers when queued in a multidivisional setting. NOIS: EKH-0998-40488\n \n18. Correct the option 'Interim report by provider' [LRRD] not correctly\nVALIDATION REQUIREMENTS BY OPTION: There are no required validation\nhandling providers names with more than 20 characters. NOISs:\nGAI-0698-31676, MWV-0598-21363, SAM-1098-20301\n \n19. Merged accessions [LRACC MERGE] will now download to auto-instruments.\nOption would not accept partial accession number. Also merged tests\nmaintain the primary ordered test linkage. NOISs: IOW-1298-41014,\nBAN-0897-11956\n \n20. Incorrect data is extracted if the site has the 'COLLECT WKLD LOG FILE\nDATA' field (#616) of the LABORATORY SITE file (#69.9) set to yes during\nscenarios to be completed by sites after installing this patch.\nDSS Workload extraction procedure. The DSS Package has exclusive rights to\nthe WKLD LOG file (#64.03). The DSS Coordinator must sanction any local\nfield use of this file. This patch will set the field to null before\nstarting to process workload extraction requests. Also the default\nprovider was being extracted from the incorrect global location. NOIS:\nPHO-0798-60573\n \n21. Corrects a typographical error in referencing the XTMP global. NOIS:\nTAM-0698-31132\n \n \n22. The Merge Accessions [LRACC MERG] option has been modified to comply\nwith NP protocol. The test(s) that are merged into another accession will\nhave NP designation set and a delete notification is sent to CPRS as a\nDiscontinued Order. The reverse is true for the accession receiving the\nmerged test.\n \n23. During verification by automated instrument, using the Enter/verify\ndata (auto instrument) [LRVR] option, Enter/verify data (Load list)\n[LRVRW2] option or Enter/verify data (Work list) [LRVRW] option, the\nbuilding of the test list could cause an error when a user selects a\nPatch Description:\nloadlist profile with many tests. This would create a string too long\nerror. The lists of tests to be verified are now stored in the TMP global\ninstead of local arrays. This change will allow the site to place as many\ntests as required under a single profile. Collecting sites, using the LEDI\nsoftware, will now be able to place all tests sent to a host lab under a\nsingle profile on the worklist. The routines LRGP2 and LRVR1 have been\nenhanced to correct this problem. NOISs: CHS-0398-42380,\nMAD-1098-41673\n \nExamples:\n \n \nAccessioning [LR IN] menu\n \nThe name of the Delete entire order or individual tests [LRCENDEL] option\nand Delete test from an accession [LRTSTOUT] option was not changed. Tests\nare no longer deleted but will have a disposition (status) of 'NOT\nPERFORMED'. The test(s) will have a complete date assigned and will not\nappear in Incomplete Load/Worklist. Both options use the same logic.\n \nSelect Accessioning menu Option: del\nThe VISTA Laboratory software patch LR*5.2*221 contain several\n 1 Delete entire order or individual tests\n 2 Delete test from an accession\nCHOOSE 1-2: 1 Delete entire order or individual tests\n \nENTER ORDER NUMBER: 440\nOrder Test Urgency Status Accession\n -Lab Order # 440 Provider: BEAR,GUMMY O.\n BLOOD SERUM\n UREA NITROGEN ROUTINE Collected 01/05/1999@22:55 CH 0105 4\n : ~For Test: UREA NITROGEN\nThe VISTA Laboratory software patch LR*5.2*221 contain the following\nenhancements across several functions and procedures. One major\n : ~DEMO NP option \nAARDVARK,JIMMY JR. 333-22-2444\nChange entire order? No// Y (Yes)\n \nCancellation Reason: ? \n Answer with ORDER REASON NAME, or SYNONYM, or CODE\n Do you want the entire ORDER REASON List? Y (Yes)\nChoose from:\n CLOTTED SPECIMEN\n DUPLICATE TESTS\nenhancement or change in business practice is the handling of tests that\n HEMOLYZED SPECIMEN\n INSUFFICIENT SPECIMEN\n OTHER CANCEL REASON\n PATIENT UNAVAILABLE\n REQUESTING PHYSICIAN CANCELLED\n SERVICE CORRECTION\n \n*[This next prompt is new - It allows the use of entries in the LAB\nDESCRIPTION file (#62.5) that have special screens. The default screens\nare GENERAL, ORDER and LAB. If you wish to include additional screens,\nwill not be done (performed) for various reasons. It is clear that there\nenter them here.]\n \nSelect NP comment Lab Description screen: \n \nNot Perform Reason : NS\n (NO SPECIMEN RECEIVED) [Description file expanded text]\nSatisfactory Comment ? Yes// YES\n \n*[This is what a not performed accession/order will look like.]\n \nare legitimate reasons that an ordered procedure will not be performed by\nSelect Accessioning menu Option: ORDER/Test status\nSelect Patient Name: AARDVARK,JIMMY JR. 04-04-44 333222444 \n \n *** WARNING ***\n *** RESTRICTED RECORD ***\n \nDATE to begin review: TODAY// (JAN 05, 1999)\n \n Test Urgency Status Accession\n -Lab Order # 440 Provider: BEAR,GUMMY O.\nthe laboratory service. This enhancement does not prevent the laboratory\n BLOOD SERUM\n UREA NITROGEN *Canceled by: STALLING,FRANK \n : *NP Reason:NO SPECIMEN RECEIVED\n : *NP Action:01/05/1999@22:57\n : ~For Test: UREA NITROGEN\n : ~DEMO NP option \nOrders for date: 01/04/1999 OK? Yes// ^\nSelect Patient Name: \n \n24. Lab Descriptions cancellation comments cannot contain a semicolon ';'.\npersonnel from following established guidelines.\nIf semi-colon is entered, it will be converted to a dash '-'.\n \n25. The 'Accessioning test ordered by Ward order entry' [LROE] option now\nrequires the user to enter a collection date/time. 'NOW' is an acceptable\nentry. The default answer to the question 'Do you have the entire order?'\nhas been removed.\n \n26. A new UID VERIFICATION field (#2.1) has been added to LOAD/WORKLIST\nfile (#68.2), PROFILE multiple (#50).\n \n \nExample:\n \nWhen verifying by Lab Universal Identifier (UID) the site can configure\nhow accessions are selected.\n \nIf "PROFILE ACCESSION AREA ONLY" is selected then only those UIDs which\nare from the accession area designated for this profile can be selected.\n \nIf "ANY ACCESSION AREA" is selected then a UID from any accession area\ncan be selected. Note that an accession from a different area should have\nThis patch provides another status called "Not Performed" (NP). Not\ntests that would be in this editing profile.\n \nThe routine LRVRA behavior is controlled by the entries in this field.\n \n27. The routine LRVER1 has been enhanced to store LOINC code when tests\nare verified manually.\n \n28. The LOCATION (#14.1) field in the LAB DATA file (#63) input transform\nhas changed to conform to FileMan Version 22 variable cleanup.\n \nPerformed is considered a test completion status. The software treats NP\n29. The routine LRVR4 has been modified not to expand lab descriptions\nwhen processing instrument comments. This can have undesirable effects -\nexpands comments when it is not required, makes comments too long and they\nwill not be stored.\n \n30. Incremental locks have been added to routines LROE and LR7OF5 to\ncorrect CPRS orders not being receipted properly.\n \n31. In the past, those entries in the LAB DESCRIPTION file (#62.5) not\nhaving a screen defined would be expanded when entering comments. This\nstatus the same as verified test except there is no test result. Instead\nprevented the use of the same code for two different areas. For example 1+\nin microbiology may have a different expansion in blood bank. The software\nlogic has been enhanced to allow the same code to expand appropriately\ndepending on the screen. The same code can be used more than once.\n \nThe following example displays how to determine which Lab Descriptions\nthat does not have a screen using the Search and Edit combinations of VA\nFileMan 21.0.\n \nExamples:\nchanges to the BLOOD BANK SOFTWARE VERSION 5.2 controlled by VHA DIRECTIVE\nof storing a result, NP enhancement stores a comment indicating the reason\n \nVA FileMan 21.0\n \nSelect OPTION: SEARCH FILE ENTRIES\n \nOUTPUT FROM WHAT FILE: LAB DESCRIPTIONS//\n \n -A- SEARCH FOR LAB DESCRIPTIONS FIELD: SCREEN \n -A- CONDITION: NULL \n \nfor the NP status.\n -B- SEARCH FOR LAB DESCRIPTIONS FIELD: \n \nIF: A// SCREEN NULL\n \nSTORE RESULTS OF SEARCH IN TEMPLATE: \n \nSORT BY: NAME// \nSTART WITH NAME: FIRST// \nFIRST PRINT FIELD: .01 NAME \nTHEN PRINT FIELD: EXPANSION \n \nTHEN PRINT FIELD: \n \n *************************\nHeading (S/C): LAB DESCRIPTIONS SEARCH Replace \nDEVICE: TELNET Right Margin: 80// \nLAB DESCRIPTIONS SEARCH MAY 10,1999 10:36 PAGE\nNAME EXPANSION\n-------------------------------------------------\n \nExample:\nDV TEST PERFORMED AT DALLAS, TX VAMC LAB\nLX TEST PERFORMED AT LEXINGTON, KY VAMC LAB\n \n 2 MATCHES FOUND.\n \nUsing the results of the search edit those Lab Description(s) missing a\nscreen.\n \nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n \n *CALCIUM Not Performed: 02/11/19999 9:02pm by 104\nINPUT TO WHAT FILE: LAB DESCRIPTIONS// \nEDIT WHICH FIELD: ALL// .01 NAME \nTHEN EDIT FIELD: SCREEN \nTHEN EDIT FIELD: \n \nSelect LAB DESCRIPTIONS NAME: DV TEST PERFORMED AT DALLAS, TX\nVAMC LAB\nNAME: DV// \nSCREEN: ?\n Choose from: \n *NP Reason: Hemolyzed Specimen\n L LAB\n E AP EM\n S AP SURG\n H ALERT\n C AP CYTO\n M MICRO\n G GRAM STAIN\n F FUNGUS\n T TB\n P PARASITE\n \n V VIRUS\n Y SPUTUM SCREEN\n W SMEAR\n A ORDER\n D BB DISP\n R BB TRANS\n X BB TESTING\n Z BB COLLECT\n I AP GENERAL\n J BB AUDIT\nYou will note that NP comments start with the "*" that differentiate this\n K GENERAL\n B BB RELEASE\nSCREEN: O ORDER\n \nSelect LAB DESCRIPTIONS NAME: Repeat ..\n \nYOU SHOULD NOW VERIFY THAT THE LAB DESCRIPTIONS ARE EXPANDING\nAPPROPRIATELY.\n \n32. The "ORDERED TEST COST BY PROVIDER" [LR ORDERED TESTS BY PHY] option\ncomment from other types of comments. NP comment and reason is stored in\nhas been enhanced to allow selection of accessioning division or any given\norder. This will allow a report based on where the specimen was\naccessioned. The report will be based on the division of the user\naccessioning the specimen. If no division is selected, all divisions will\nbe included on the report.\nthe LAB Data file (#63) and in the LAB ORDER ENTRY (#69). The CPRS order\n97-033.\nis marked as 'Discontinued' and displayed on the 'Active Orders' screen\nwhen the LAB ORDER CANCEL notification in CPRS is enabled. If this is not\nacceptable then the CPRS order can be marked as Complete when 'SERVICE\nCORRECTION' is used as an Order Cancellation Reason.\n \nNP is different than "canc". Canc is a result that is stored in the\npatient's clinical record.\n \nThis enhancement allows the conveyance of the following information to the\nhealth care provider:\n \n \n1. The ordered procedure has been given a status of 'Not Performed' and\nthe reason for the status.\n2. It prevents numerous software errors resulting from missing data nodes\nin the database.\n \n3. Creates an audit trail of what ultimately happened to all tests ordered\nor accessioned.\n \nAssociated NOISs:\nBLOOD BANK SOFTWARE V.5.2 Changes:\n================\nCHY-0798-51245, ALN-1198-11196, ASH-0898-30554, ATG-0698-31312,\nWNY-0698-11221, CLA-0598-20635 CMO-1198-41253, DEN-0898-50267,\nDUB-0898-30615, FGH-1198-32348, GAI-0698-32344, HAM-1098-21436,\nLAS-0698-60208, LEX-0898-41581, LEX-1198-40049, COM-0498-60788,\nMIN-0798-40025, MON-0798-51662, MUS-1098-71863, NAS-1098-31373,\nOKL-0698-71939, SAG-0498-42248, SLC-1198-50813, TAM-0798-30677,\nTAM-1298-31153, TOG-0898-11351, LEB-1298-22078, TAM-1298-31153,\nCLA-1198-22013, ALX-1198-71715, ALX-0898-71684, ASH-0898-30675,\nBEC-0998-20129, BYN-0598-11025, DAY-0798-42525, DEN-1098-50461,\n\n
\nDETAILED WORKLOAD REPORT\n\n
\nThis patch corrects issues both with Y2K and also makes the Blood Bank\npackage compatible with changes being exported with VA FileMan version 22.\n For a complete description of the patch contents, see the Description of\nthe patch in the FORUM Patch Module.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nSee patch LR*5.2*230 in the National Patch Module for a description of\nthis build.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nBelow is a brief description only of changes included in this patch. For\n - Resolution: Screen displays associated with the ordering and\n - Resolution: Regardless of where in the queue a report is added, if the\n report record does not have the provider listed for any reason, the\n word "UNKNOWN" will be stuffed as the provider.\n NOTE--this issue has only been reported at one site and is not easily\n reproducible. The validity of the fix for this will be internally\n verified by development under controlled conditions only. This\n option does not contain any safety critical functions for the\n blood bank.\n \n Problem # 9:\n processing of blood components for a patient have been modified to\n When using the option Disposition - relocation [LRBLIDR] there were a\n variety of reported problems with the lookup for LOCATION to relocate\n blood to.\n NOIS: IND-1296-40311 BRX-0597-11400 LEB-0199-20568\n - Resolution: The lookup routine LRUC was rewritten. It now uses\n FileMan utilities to look up valid locations based on the division of\n the user at sign-on.\n \n Problem # 10:\n During the option Log-in regular (invoices) [LRBLILR], when the user is\n always include a 4 digit year, even if no year was previously\n presented the screen to edit units just logged in, if a unit had been\n accidentally logged in with an expiration date the same date as the log\n in, and the expiration date is edited correctly, the unit is still\n flagged as expiring today when re-displayed to the user. This was ONLY a\n flag problem. The actual expiration date of the unit always reflected\n the date correctly as input.\n NOIS: LEX-0197-40288\n - Resolution: The option has been edited so that the flags for units\n expiring the same day work appropriately.\n \n displayed.\n Problem # 11:\n During the background process of collecting workload for Blood Bank\n accessions, result data was being inappropriately stuffed into fields\n which had been starred for deletion. This data was then printing on the\n Accession area worklist [LRUWL] report.\n NOIS: ATG-0895-32603\n -Resolution: The collection of workload data no longer stuffs result data\n into inappropriate fields.\n \n Problem # 12:\n \n As of April 23, 1999 the VistA BLOOD BANK Software (v 5.2) is classified\n as a Medical Device # BK970021 with the FDA. According to VHA Directive\n 97-033, Section 4. ACTION part b., the CIOFO would embed in the form of a\n comment in routines that contain the controlled software a statement that\n the routine should not be modified. According to FDA, if a facility\n other than the original software manufacturer makes any changes to the\n cleared device, including changes to the software components of the\n medical device, this software no longer represents the cleared medical\n device and the facility making the modification becomes the medical\n device manufacturer of a new medical device. \n Problem # 2:\n - Resolution: Routines classified as Group A in VHA Directive 97-033\n will have the following verbiage inserted in the third line:\n ; Per VHA Directive 97-033, this routine should not be modified.\n Medical Device # BK970021\n \n Problem # 13:\n The Patient Merge software introduced a problem in the database\n that has affected the way some of the Lab routines determine the\n LABORATORY REFERENCE field (#2,63) from the PATIENT File (#2). \n - Resolution: Routines LRBLPAB and LRBLPD1 have been modified to use the\n It was discovered during Y2K testing of the Donor module of the Blood\n function $$LRDFN^L7OR1(DFN) to determine a patient's LRDFN. This\n function was introduced in LR*5.2*230 as a defensive programming\n measure to prevent an undefined error from occurring when attempting to\n determine the LRDFN from the ^DPT(DFN,"LR") node.\n \n Problem # 14:\n There may be some old post-init or otherwise unnecessary routines at\n sites. These will be removed during the KIDS install if they are\n present.\n -Resolution: If present on a system, routines LRBLFIX, LRBLFX72,\n Bank package that when donor collection information is entered into the\n LRBLJ, LRBLPOST, LRBLCON and LRBLXREF will be removed as part of the\n KIDS Install.\n \n Problem # 15:\n It was reported by Milwaukee via a mail message that when a blood bank\n specimen is drawn on one day but not actually accessioned until the next\n day, under certain circumstances an undefined error would occur when a\n tech attempts to assign units which require crossmatch using the option\n Select units for patients [LRBLPIC]. Upon further investigation it was\n discovered that the option was attempting to update the field COMPLETION\n computer, future times are allowed when entering the fields DATE/TIME\n TIME (#68.14,1) for workload purposes. It was further determined that\n when the error did not occur, the incorrect workload record was being\n updated. It is actually inappropriate to update this field as it is set\n when the original accession has the ABO/Rh and ABS results entered.\n -Resolution: Coding has been changed so that the field COMPLETION DATE\n (#68.14,1)is no longer updated as a result of using the option Select\n units for patients [LRBLPIC].\n \n Problem # 16:\n The patch LR*5.2*72 inadvertently exported a change in the length of the\n COLLECTION STARTED (#65.54,4.2) and DATE/TIME COLLECTION COMPLETED\n text allowed in the BLOOD PRODUCT File (#66) field SYNONYM (#66.021,.01).\n This resulted in sites being restricted to 5 character synonyms for\n entries made to this field after installation of that patch. \n -Resolution: The data dictionary for this field is being re-exported and\n the SYNONYM field (#66.021,.01) field will now be allowed to accept\n entries from 1-25 characters.\na full description please see the Patch Description in the Forum Patch\n (#65.54,4.3). This posed a problem during testing in the system being\n used for Y2K testing. The scenario where a unit is collected on\n 12-31-1999 but data is not entered until 12-1-2000 and the date/times\n being entered as 12-31@0800 defaults to the current year, which is a\n future time. This should not be allowed.\n NOIS: ISA-1099-13117\n - Resolution: The input transforms of the affected fields will be edited\n so that no future dates are allowed.\n \n Problem # 3:\nModule.\n It was reported by a site via an Outlook message that when logging in\n units using the option Log-in regular (invoices) [LRBLILR] and the\n barcode scanner is used, if a site's supplier uses Expiration Date\n barcodes utilizing a 4 digit year, then the display to the user seems to\n indicate that the scanner did not interpret the code correctly. The\n correct expiration date was in fact being assigned to the unit, however,\n the software was interpreting the input as if the user was manually\n inputting the expiration date. This could cause some confusion at sites.\n - Resolution: The routine which interprets barcodes has been modified so\n that the barcode scanner itself is interpreting the expiration date.\n \n \n Problem # 4: \n The input screen for the fields DIVISION in the BLOOD INVENTORY File\n (#65,.16) and ASSOCIATED DIVISION in the BLOOD PRODUCT File (#66.1,.01)\n incorrectly made the assumption that a site's division was dinumed to the\n INSTITUTION File (#4). \n NOIS: WPB-1196-31737\n - Resolution: The screen in the following input transforms have been\n changed to S DIC("S")="I +$G(^DIC(4,+Y,99))=+$P($$SITE^VASITE,U,3)"\n D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X"\n Problem # 1: \n BLOOD INVENTORY File (#65) field DIVISION (#65,.16)\n BLOOD PRODUCT File (#66) field ASSOCIATED DIVISION (# 66.1,.01)\n \n Problem # 5: \n In a multidivisional site, if the report Patient transfusions &\n hematology results [LRBLPCH] crashed for any reason, it could not be\n restarted if the name of the Blood Bank accession area was not BLOOD\n BANK. This is because in order to restart the crashed report, the option\n Delete a user's patient list [LRBLSDPL] needed to be run first. This\n option had the accession area hard coded to be BLOOD BANK therefore would\n It was determined by the VistA IV&V Y2K testing analysis that several\n not always work in a multidivisional site with more than one Blood Bank.\n NOIS: BHS-0899-12185\n - Resolution: The option Delete a user's patient list [LRBLSDPL] was\n modified to determine the accession area for the Blood Bank based on\n the user's division at sign-on. Previously, the accession area was\n hard-coded to be BLOOD BANK.\n NOTE-- the resolution to this problem will not be validated at the sites\n as it is not practical to ask sites to force a system crash. The\n validity of the fix for this will be internally verified by\n development under controlled conditions only. This option does\n displays within the Blood Bank software that historically displayed\n not contain any safety critical functions for the blood bank.\n \n Problem # 6: \n When a unit which was originally scanned during log-in is modified, such\n as thawing or irradiating, the unit could no longer be processed using a\n scanner. This affected both the Blood Bank as well as the Surgical Risk\n Initiative.\n NOIS: HIN-1196-40687 ALB-0298-52583\n - Resolution: When a unit is modified using the option Disposition -not\n transfused [LRBLIDN] and the Unit ID remains the same (i.e. unit not\n Month/Day only needed to also display a 4 digit year.\n pooled or split) the ^LRD(65,"C", cross-reference is now built if the\n scanner was used to process the modification.\n \n Problem # 7:\n It was discovered during internal testing by the developer that units\n that are modified in error, and the option Edit unit log in [LRBLSEL] is\n used to either edit or delete the modified unit, the ^LRD(65,"C",\n cross-reference was not being updated appropriately.\n - Resolution: Coding was changed to update the ^LRD(65,"C"\n cross-reference as appropriate when units are edited.\n NOIS: ISP-0899-N0355\n \n Problem # 8:\n When executing the option Print all BB patient reports on print queue\n [LRBLP PRINT ALL ON QUEUE] if for some reason the first patient blood\n bank report added to the print queue doesn't have a PROVIDER the report\n bombs with an undefined and none of the reports will print. Also, if a\n patient blood bank report added in the middle of the queue doesn't have a\n provider, the report will print the provider of the report just\n previously added to the queue.\n NOIS: ALB-0899-52597\n\n\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\n Y2K Waiver Exemption ID#: Y2KWE0040\n format. This calculation is now done using verified FileMan utilities.\n 'Install Package(s)' Select the package 'LR*5.2*242' and proceed\n with the install.\n 9. If any routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\n\n 2. The Patient Merge software introduced a problem in the database that\n has affected the way many of the Lab routines get the Laboratory\n Patient identifier (LABORATORY REFERENCE field (#63) in the PATIENT\n file (#2) also known as the LRDFN). The Patient Merge developers are\n working on a solution for the problem created in the database and the\n cause of the problem. Patch LR*5.2*242 is being created as a defensive \n measure against this problem and any possible future changes that may \n affect the problem global node: ^DPT(DFN,"LR").\n This patch may be installed at any time during the Y2K \n\n \n This patch to the Laboratory package does not contain any changes to the\n VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 97-033 titled VISTA\n BLOOD BANK SOFTWARE VERSION 5.2.\n \n PROBLEM: The Patient Merge software introduced a problem in the database\n that has affected the way many of the Lab routines determine the\n LABORATORY REFERENCE field (#2,63) from the PATIENT File (#2). Patch \n LR*5.2*242 is created as a defensive measure against this problem and any\n Moratorium (including the 12/15/1999 thru 1/15/2000 Y2K lockdown).\n possible future changes that may affect the problem global node\n ^DPT(DFN,"LR"). \n \n RISK ANALYSIS: Changes made by patch LR*5.2*242 have no effect on Blood\n Bank software functionality, therefore RISK is none.\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*242 does not\n alter or modify any software design safeguards or safety critical elements\n functions.\n \n\n POTENTIAL IMPACT ON SITES: Patch LR*5.2*242 contains no changes to \n routines identified in Veterans Health Administration (VHA) Directive \n 97-033. There is no adverse potential to sites.\n \n VALIDATION REQUIREMENTS BY OPTION: There are no required validation\n scenarios to be completed by sites after installing LR*5.2*242.\n\n \n Related NOIS: LEX-0599-42692\n BHS-0799-12636\n This patch corrects two problems:\n \n Test site(s): Oklahoma City, OK\n \n ROUTINE SUMMARY:\n ================\n The following is a list of the routine(s) included in this patch. The\n second line of each of these routine(s) will look like:\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n \n CHECK^XTSUMBLD results\n Routine name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n LR7OGU 3794087 3796964 187,242\n LRAPQACN 6886068 7049309 72,242\n LRAPQAFS 6133966 6306636 72,242\n LRAPQAMR 8875869 9048539 72,134,242\n LRAPQOR3 3828767 3833155 234,242\n LRAPS3 2265857 2247733 242\n LREPI2 5563295 5729687 132,157,175,242\n 1. The Indian Health Service reported a possible Y2K problem. Some of the\n LRGEN 6602814 6713858 121,201,202,242\n LRMIEDZ2 12615006 12271075 23,104,242\n LRMIV2 15350039 15031478 242\n LROW2RP 6088048 5879307 121,201,242\n LRRP4 3097412 3053252 121,242\n LRUQ 5009717 2073981 242\n \n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n Microbiology and Anatomic Pathology routines were using an unreliable\n option will load the KIDS package in this message onto your\n system.\n 2. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global.\n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n method of converting the internal year format to an external 4 digit\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation should be done\n at off peak hours.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak hours\n and less than 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory space.\n 8. From the 'Installation Menu' of the KIDS menu, run the option\n\n
\nFIX FOR PATCH 108\n\n
\nY2K Waiver Exemption ID#: Y2K??????\n \nPROBLEM: Date handling errors were found in the logic of patch\nLR*5.2*242. This patch corrects these errors.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*252 have no effect on Blood\nBank software functionality, therefore RISK is none.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*252 does not\nalter or modify any software design safeguards or safety critical elements\nfunctions.\nThis patch may be installed at any time during the Y2K \n \nPOTENTIAL IMPACT ON SITES: Patch LR*5.2*252 contains no changes to\nroutines identified in Veterans Health Administration (VHA) Directive\n99-053. There is no adverse potential to sites.\n \nVALIDATION REQUIREMENTS BY OPTION: There are no required validation\nscenarios to be completed by sites after installing LR*5.2*252.\n \n \nRelated NOIS: MOU-1299-32678\nMoratorium (including the 12/15/1999 thru 1/15/2000 Y2K lockdown).\n PUG-1299-52743\n \nTest site(s): MOUNTAIN HOME, TN\n PUGET SOUND HCS\n \nROUTINE SUMMARY:\n================\nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n \n \n <tab>;;5.2;LAB SERVICE;**[patch list]**;Sep 27, 1994\n \n CHECK^XTSUMBLD results\nRoutine name Before Patch After Patch Patch List\n============ ============ =========== ==========\nLR7OGU 3796964 3798654 187,242,252\nLRAPQACN 7049309 7049272 72,242,252\nLRAPQAFS 6306636 6306592 72,242,252\nLRAPQAMR 9048539 9048495 72,134,242,252\n \nThis patch corrects date input problems found in patch LR*5.2*242.\n Installation Instructions:\n ==========================\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport\n global.\n \n On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on the system, but installation should be\n done at off peak hours.\n 5. No options need to be placed out of service.\n 6. Installation time is less than 2 minutes during off peak\nThis patch to the Laboratory package does not contain any changes to the\n hours and less than 5 minutes during peak hours.\n 7. Installation of this patch requires no additional memory\n space.\n 8. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'LR*5.2*252' and\n proceed with the install.\n 9. If any routines were unmapped as part of step 2, they should\n be returned to the mapped set once the installation has run\n to completion.\nVISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled VISTA\nBLOOD BANK SOFTWARE VERSION.\n\n
\nA Y2K problem was logged in NOIS regarding the reports generated in the\n FC FUNCTION code search, SNOMED [LRAPSF]\n IC ICD9CM code search [LRAPSI]\n AX MULTIAXIAL code search, SNOMED [LRAPSEM]\n \nNOIS calls were logged because data was being omitted from the reports for\nyear 2000 accessions. Below is an example of the report generated by menu\nitem '[LRAPSM] MORPHOLOGY code search, SNOMED':\n \nSURGICAL PATHOLOGY (SP) SEARCH(Dec 30, 1999=>Jan 03, 2000)\n # = Not VA patient\n'[LRAPSEARCH] Search options, anat path' menu. This menu performs searches on\nSNOMED TOPOGRAPHY CODE: ALL-- SNOMED MORPHOLOGY CODE: ALL--\n-----------------------------------------------------------------------------\n NAME ID SEX AGE ACC # ORGAN/TISSUE MORPHOLOGY\nHOBBS,JOHN H 9801 M 63 SP 99 4814 SKIN OF CHEST BASAL CELL CARCI\n RX0\n SKIN OF HEAD BASAL CELL CARCI\n RX0\nJENKINS,CLARENCE 3133 M 41 SP 99 4808 TRACHEA HEMORRHAGE\nLAMBE,NORMAN B. 5487 M\nMONEY,CLAUDE C 4599 M\nAnatomic Pathology accessions based on morphology, disease, etiology,\nNELSON,DIANE M 4856 F\nNELSON,KENNETH R 1674 M 51 SP 99 4820 SKIN OF UPPER E PSORIASIS\nOWENS,ERNEST D 5310 M\n \nNotice that some of the names listed show no data in the Age, Acc #,\nOrgan/tissue, and Morphology columns. These are year 2000 accessions. All\n1999 accessions still reported correctly.\n \nIt was discovered that the two digit year was being used as a subscript in\nthe ^TMP global which stores that data temporarily so that it may be\nprocedure, function, or diagnosis code. The menu is shown below:\nprinted. The two digit year subscript is extracted from dates in the LAB DATA\nfile (#63) as follows:\n \nSurgical Pathology: DATE/TIME SPECIMEN RECEIVED field (#.1) of SURGICAL\n PATHOLOGY (sub-field #8, Sub-file #63.08)\nCytopathology: DATE/TIME SPECIMEN RECEIVED field (#.1) of\n CYTOPATHOLOGY (sub-field #9, Sub-file #63.09)\nElectron Microscopy: DATE/TIME SPECIMEN RECEIVED field (#.1) of EM\n (sub-field #2, Sub-file #63.02)\nAutopsy: AUTOPSY DATE/TIME field (#11)\n \n \nThe year subscript is created by extracting the second and third characters\nof the date. For example, if the date is 2991031.0800, the year subscript\nwill be 99. If the date is 3001031.0800, the year subscript will be 00.\n \nHere is an example:\n \n^TMP(545305223,99,2) = AU 99 2^20^M^WINKERBEAN,FUNKY^5533^10/14^2\n^TMP(545305223,99,2,151,0) = BRAIN\n^TMP(545305223,99,2,151,41770) = ABSCESS, DRAINING\n MC MORPHOLOGY code search, SNOMED [LRAPSM]\n^TMP(545305223,"00",1) = AU 00 1^81^M^FULTON,CHESTER E.^5537^1/13^2\n^TMP(545305223,"00",1,395,0) = SKIN BETWEEN FOURTH AND FIFTH TOES\n^TMP(545305223,"00",1,395,"02060") = SADDLE SHAPE\n \nThe second subscript is the two digit year. Subscript "00" was confusing\nthe code causing it to quit before executing the portion of code that\nprints the age, accession number, organ/tissue, and morphology.\n \nThe problem has been corrected by including the century indicator when\ncreating the second subscript. For year 1999, the subscript will be 299.\n DC DISEASE code search, SNOMED [LRAPSD]\nFor year 2000, the subscript will be 300. See below:\n \n^TMP(545305223,299,2) = AU 99 2^20^M^WINKERBEAN,FUNKY^5533^10/14^2\n^TMP(545305223,299,2,151,0) = BRAIN\n^TMP(545305223,299,2,151,41770) = ABSCESS, DRAINING\n^TMP(545305223,300,1) = AU 00 1^81^M^FULTON,CHESTER E.^5537^1/13^2\n^TMP(545305223,300,1,395,0) = SKIN BETWEEN FOURTH AND FIFTH TOES\n^TMP(545305223,300,1,395,"02060") = SADDLE SHAPE\n \nThis change to the ^TMP global structure has corrected the problem.\n EC ETIOLOGY code search, SNOMED [LRAPSE]\n \n PC PROCEDURE code search, SNOMED [LRAPSP]\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis is a patch for VISTA Laboratory Software, version 5.2.\nA detailed description of this patch is included in the patch\ndistribution message.\n\n
\nThis patch fixes an UNDEF in the routine LRVER1 at line EX2+1. This is a patch \nto patch LR*5.2*239.\n\n
\n This patch fixes the following problems in the option Add a new\n \n This patch to the Laboratory package does not contain any changes to the\n VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled\n VISTA BLOOD BANK SOFTWARE.\n \n Associated NOIS: NOL-1197-71309\n \n Test Site: Asheville, NC \n Montgomery, AL\n Muskogee, OK\n data name [LRWU5] that allows you to add a new data name to the LAB\n New Orleans, LA\n \n Reporting Site: New Orleans, LA\n \n \n ROUTINE SUMMARY\n ===============\n \n The second line of the routine now looks like:\n \n DATA file (#63).\n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n LRWU5 13485455 11320832 140,171,177,206\n \n \n Installation Instructions\n \n =========================\n It is recommended that this release be installed during off peak hours.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto your\n system.\n 2. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 1. Option does not allow you to enter a value less than zero for the\n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users may remain on system and no options need to be placed out of\n service.\n 5. Installation time is less than 2 minutes during off peak hours\n and less than 5 minutes during peak hours.\n minimum or maximum value for numeric data names.\n 6. Installation of this patch requires no additional memory space.\n 7. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'LR*5.2*206' and\n proceed with the install.\n 8. When Prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES//', respond NO.\n 9. If any routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\n \n 2. Option does not allow you to designate decimals for the minimum or\n maximum value for numeric data names.\n\n
\nThis patch to the Laboratory package does not contain any changes to the\n Solution: The code has been validated, brought up to national\n standard and released as a Class I national patch.\n \nThis patch can be installed as a stand-alone if CareVue package is not\nneeded, however if CareVue IS NEEDED then patch LA*5.2*53 MUST be\ninstalled.\n \nThe laboratory routines LRVER3A and LRMIUT have been modified to work with\nthis interface. These routines have been locally modified at the sites\nand the sites must ensure that precautions are taken to prevent loss of\nVISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled VISTA\nlocal modifications when patches to Laboratory are installed.\n \nAssociated NOIS\n===============\nNone\n \nTest Sites\n===============\nPhiladelphia, PA\nMartinsburg, WVA\nBLOOD BANK SOFTWARE.\n \nROUTINE SUMMARY\n===============\nThe following is a list of routines included in this patch. The second\nline of each routine now looks like:\n \n<tab>;;5.2;LAB SERVICE;**[patch list]**;;Sep 27, 1994\n \n CHECK^XTSUMBLD Results\n \n \nRoutine Name Before Patch After Patch Patch List\n------------ ------------ ----------- ----------\n \nLRVER3A 9561045 10780359 1,5,42,100,121,\n 153,190,221,254\nLRMIUT 3226335 3673249 254\n \nINSTALLATION INSTRUCTIONS\n=========================\nThe patch is distributed in KIDS format in a PackMan message.\nThis patch will install the CareVue interface package under the namespace\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package in this message onto\n your system.\n \n 2. Review your mapped set. If the routines are mapped, they\n should be removed from the mapped set at this time.\n \n 3. The patch has now been loaded into a Transport global on\n your system. You now need to use KIDS to install the \nLA7D as a Class I national patch.\n Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the \n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 4. It is recommended that this release be installed during off\n \n peak hours. To prevent a possible problem with the tasking\n of the next days laboratory orders, do not install this package\n at the same time as the following nightly tasked jobs:\n \n LRTASK ROLLOVER\n LRTASK NIGHTLY\n LRTASK CONJAM\n LRTASK CUM\n \n 5. No options need to be placed out of service.\n1. Problem: Current CareVue interface is Class III software.\n \n 6. Installation time is less than 2 minutes during off peak \n hours and less than 5 minutes during peak hours\n \n 7. From the 'Installation Menu' of the KIDS menu, run the \n option 'Install Package(s)' Select the package 'LR*5.2*254'\n and proceed with the install. When prompted 'Want to \n DISABLE Scheduled Options, Menu Options, and Protocols? \n YES//', choose 'NO'.\n \n \n 8. If any routines were unmapped as part of step 2, they \n should be returned to the mapped set once the installation \n has run to completion.\n \n 9. Please refer to Patch LA*5.2*53 for further instructions \n regarding CareVue. \n\n
\n \n============\n \n14. The Review by order number [LRCENLKUP] option date displays is\nconverted to use Kernel date conversion utilities.\n \n15. Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] option is enhanced\nto print all WKLD CODES, even if they have not been activated. This will\ncorrect the problem of WKLD CODES that have a suffix of .0000 not\nprinting.\n \n16. Workload Report [LRCAPR1] option has been enhanced to allow the user\n \nto select combinations of LEDI collecting institutions or Hospital\nlocations.\n \n17. When verifying Microbiology specimens the user is prompted for\nadditional workload. A screen has been added to allow only a number\nbetween 1 to 25. This is to prevent inadvertent entering of WKLD CODE\nnumber instead of the multiply by number.\n \nLaboratory Menu and Option Changes:\n============================\nThe Laboratory CPT Code Modifier enhancement patch LR*5.2*243 provides the\nLIM workload menu [LR LIM/WKLD MENU]\n \nThe LIM workload menu [LR LIM/WKLD MENU] is modified to add the new\nInActive WKLD CODE File CPT Codes Print [LRCAPCPTI] option.\n \nNew Option\n \nInActive WKLD CODE File CPT Codes Print [LRCAPCPTI] option\n \nThe new Inactive WKLD CODE File CPT Codes Print [LRCAPCPTI] option scans\nLaboratory Version 5.2 software application the ability to transmit\nthe WKLD CODE file (#64) for code(s) that are no longer allowed or code(s)\nthat are inactive in the CPT file (#81). The "WKLD CODE - CODE CHECK\nREPORT" is then generated displaying all CPT code(s) that are no longer\nallowed, code(s) that are inactive and why they are inappropriate,\nlaboratory test names linked to WKLD code(s) (i.e., laboratory test names\nlisted on the report will not receive PCE Workload credit), and code(s)\nrequiring a different entry in the CPT file (#81) in order to capture PCE\nWorkload data.\n \nThe new Inactive WKLD CODE File CPT Codes Print [LRCAPCPTI] option is also\nCurrent Procedural Terminology (CPT) codes and Modifiers to the Patient\nuseful when a new CPT Code file is released (i.e., new CPT code files are\nusually distributed annually). The new CPT Code files may contain codes\nthat are no longer allowed or codes that are inactive in the VISTA CPT\nfile (#81). When CPT codes defined in the WKLD CODE file (#64) are deemed\ninactive in the CPT file (#81), then the software enters a date in the\nWKLD CODE file (#64), Inactive Date field (#3) for those inactive codes.\nThe Laboratory PCE interface checks each CPT code in the WKLD CODE file\n(#64) before sending CPT workload to the PCE API. Whenever CPT code(s) are\nno longer allowed or has been inactivated a VA Mailman message containing\nthe "WKLD CODE - CODE CHECK REPORT" is sent once a day to the LMI mail\nCare Encounter (PCE) workload capture Application Interface (API). The\ngroup.\n \nExample: WKLD CODE - CODE CHECK REPORT\n \nSubj: WKLD CODE - CODE CHECK REPORT 12/14/99@14:44:25 [#83460]\nFrom: POSTMASTER In 'IN' basket. Page 1\n-----------------------------------------------------------------\nLab Order Number 100 has no Institution for the ordering location\n===================\n86081.0000 [1] ABO Cell and Rh(D) Typing\ntransmission of workload in the form of CPT codes is done in the\n86083 BLOOD TYPING;ANTIBODY SCREEN\nIs an inactive CPT code.\nAssociated Tests\n ABO/RH TYPING {1101}\nInactivation date of Dec 13, 1999 has been entered\n****************\nListing of all offending codes\n ICPT 82534\n \n****** END OF EXAMPLE ********\nbackground (no user interaction is required). Because of the background\n \n=====================\nData Dictionary Change Summary:\n \nThe following file and field changes occur with the installation of VISTA\nLaboratory CPT Code and Modifiers Patch LR*5.2*243.\n \nWKLD CODE file (#64)\n \n The WKLD CODE file (#64) was modified to convert existing file data to\nmethod of workload reporting several new fields were created and the\na new data structure, new fields were created, and existing fields were\nmodified to support the Laboratory workload reporting enhancements of CPT\ncodes and modifiers.\n \n1) CODE field (#18) multiple has been changed from a free text field to a\nvariable pointer.\n \n2) CODE field (#.01) has been changed from a free text field to a variable\npointer. This field is screened to allow only active code entries to the\nMORPHOLOGY FIELD file (#61.1), ICD DIAGNOSIS file (#80), and CPT file\nLaboratory software logic was modified.\n(#81).\n \n3) CODE subfile (#64.018) was modified to add the new CODE NOTES field\n(#6). This new word processing field is used for tracking general notes\nregarding a particular code.\n \n4) WKLD Code Notes field (#24) is a new word processing field used for\nstoring general notes regarding inactive or erroneous code(s) that is\nautomatically removed by the software.\n \n \n \n5) LOINC Code field (#4) was changed to point to the LOINC CODE file\n(#95.3).\n \n6) The new Default LOINC Code field (#25) points to the LOINC CODE file\n(#95.3). This field is used to identify the default LOINC code. This\nfield is usually used when the specimen is not clinically significant\n(i.e. body fluids). 'L FOR LOINC' was removed from the set of codes in\nfield TYPE (#64.018,5).\n \nLABORATORY SITE file (#69.9)\nCPT modifier provides the means by which the reporting physician can\n \n1) LABORATORY SITE file (#69.9), DIVISION PARAMETERS field (#618) multiple\nis a new field exported with this patch. These new fields are used to\ncustomize the automated Venipuncture workload reporting functionality.\n \n2) The new DIVISION PARAMETERS field (#.01) points to the INSTITUTION file\n(#4). This field allows the LABORATORY SITE file (#69.9) to be\nmulti-divisional for Venipuncture workload reporting.\n \n3) The new VENIPUNCTURE DEFAULT ACC AREA subfile (#618) points to the\nindicate that a service or procedure that has been performed has been\nACCESSION file (#68). This new field is used by the Venipuncture workload\nreporting background job to determine the accession area for the\nINSTITUTION to be use for Venipuncture workload reporting.\nAssociated NOIS\n===============\n \n \n \nTAM-0899-31723 ALB-1299-50818\nPRO-0999-11965 CLL-1099-43226\naltered by some specific circumstances but not changed in its definition\nLON-0999-62211 BHS-0999-11616\nHIN-0499-42772 NCH-0100-41945\nALB-0199-52914 \n \n \nTest Sites:\n===========\nLong Beach, CA\nKansas City, MO\nMilwaukee, WI\nor code. The judicious application of modifiers obviates the necessity for\nMuskogee, OK\n \n \nRoutine Summary:\n================\n \n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Values\nseparate procedure listing that may describe the modifying circumstances.\nRoutine Before After Patch List\nName Patch Patch List\n-------- -------- --------- --------\nLR243 N/A 7341436 243\nLRCAPPH 10281625 11522455 1,19,127,136,138,158,153,243\nLRCAPPH1 4949612 7745000 127,136,138,158,243\nLRCAPPH3 N/A 6642885 243\nLRCAPPH4 N/A 3179202 243\nLRCAPPNP N/A 1653480 243\nLRCAPR1 8086519 9529509 243\n \nLRCAPR2 8195892 8701428 88,105,243\nLRCAPR4 6795674 7338553 243\nLRCAPV3 8123485 8391773 105,243\nLRCAPVM 5012091 5237437 49,163,243\nLRCE 13210738 13336460 28,76,103,121,153,210,202,243\nLRCENDEL 16365039 15254614 100,121,202,221,243\nLRDIQ 9573488 10128715 86,153,243\nLRGP2 3525048 6353513 153,221,243\nLRMISTF1 14470635 14019130 121,128,202,243\nLROE 14732765 14550901 100,121,201,221,243\n \nLRORD3 7349040 7385601 153,243\nLROS 16807258 16882422 121,153,202,210,221,243\nLRSTUF2 8013388 8012263 121,153,243\nLRTSTSET 12634119 12775322 65,100,121,153,201,202,243\nLRTT5P1 12297887 12439150 153,221,243\nLRVER1 6428527 6801758 42,153,201,215,239,240,243\nLRVER3A 10780359 10780812 1,5,42,100,121,153,190,221,254,243\nLRVR 12695281 13316120 42,153,243\nLRVR4 8714660 8661306 14,42,121,153,221,243\nLRVR5 11783101 11729747 1,42,153,243\nNOTE: ONLY PATIENT ORDERS FROM HOSPITAL LOCATION WITH THE TYPE OF CLINIC,\nLRVRA 6318899 6374326 153,221,243\nLRXREF 9255866 9584168 70,153,243\n \nRequired Patch Installation List:\n \n \nLR*5.2*105\nLR*5.2*153\nLR*5.2*158\nLR*5.2*202\nMODULE, OR OTHER WILL RECEIVE CPT WORKLOAD CREDIT. THE SOFTWARE USES\nLR*5.2*221\nLR*5.2*240\nLR*5.2*254\nPX*1.0*73\nPX*1.0*74\nICPT*6.0*7\n \nInstallation Instructions\n=========================\n************************\nSubject: CPT CODE MODIFIERS\nLOCATION TYPE TO DETERMINE IF THE ORDER IS FOR AN OUT-PATIENT OR\nLABORATORY CURRENT PROCEDURAL TERMINOLOGY (CPT) CODES AND MODIFIERS PATCH\nLR*5.2*243 INSTALLATION AND IMPLEMENTATION GUIDE in PDF format is provided\nwith this patch. Please refer to this document for details and specific\ninstructions. The patch description does not include ALL implementation\nconsiderations or complete file setup instructions.\n************************\n \nThe VISTA Laboratory CPT Codes and Modifiers Patch LR*5.2*243 Installation\nand Implementation Guide is available in PDF (i.e., LR_CPTIG.PDF) at the\nfollowing FTP addresses:\nIN-PATIENT.\n \nOffice of Information Field Office FTP Address Directory\n======================================================================\nAlbany 152.127.1.5 anonymous.software\nHines 152.131.2.110 anonymous.software\nSalt Lake City 152.131.2.1 anonymous.software\n \n \n \n \n \n \nUsers may remain on the system, but installation should be done during off\npeak hours and when the Laboratory computer users are idle. None of the\nlaboratory tasked jobs need to be stopped.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan \n menu. This option will load the KIDS package onto your system.\n 2. Review your mapped set. If the routines are mapped,\n they should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global \nEnhancements and Modifications:\n on your system. You now need to use KIDS to install the \n Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 5. No options need to be placed out of service.\n 6. Installation time is less than 15 minutes during off peak\n=========================\n hours,and less than 30 minutes during\n peak hours which is NOT RECOMMENDED.\n 7. Installation of this patch require minimal \n disk space.\n 8. From the 'Installation Menu' of the KIDS menu, run the option \n 'Install Package(s)'. Select the package \n 'LR*5.2*243' and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they \n should be returned to the mapped set once the \n installation has run to completion.\n \n \n \nExample of install dialog:\n \nSelect INSTALL NAME: LR*5.2*243 Loaded from Distribution\n2/29/00@15:51:34\n => LR*5.2*243\n \nThis Distribution was loaded on Feb 29, 2000@15:51:34 with header of \n LR*5.2*243\nLaboratory CPT Code Modifiers Patch LR*5.2*243 contains the following\n It consisted of the following Install(s):\n LR*5.2*243\nChecking Install for Package LR*5.2*243\nWill first run the Environment Check Routine, LR243\n \n \n --- Environment Check is Ok ---\n \n \nInstall Questions for LR*5.2*243\nenhancements and changes:\n \nIncoming Files:\n \n \n 64 WKLD CODE\nNote: You already have the 'WKLD CODE' File.\n \n \n 69.9 LABORATORY SITE\nNote: You already have the 'LABORATORY SITE' File.\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\nNOTE: The asterisk ('*') indicates significant enhancements or file\nDEVICE: HOME// TELNET\nInstall Started for LR*5.2*243 : \n Feb 29, 2000@15:53:41\n \nBuild Distribution Date: Jan 27, 2000\n \n Installing Routines:\n Feb 29, 2000@15:53:41\n \n Installing Data Dictionaries: \n \nstructure changes. Two asterisks ('**') indicate new fields that will be\n Feb 29, 2000@15:53:43\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n Feb 29, 2000@15:53:43\n \n Running Post-Install Routine:\nCONV^LR243.......................................\n \nused by subsequent releases.\n Removing CPT Code 83019\n \n From 84483.0000 Helicobacter Pylorii Breath\n \n Removing CPT Code 80054\n \n From 81853.0000 Comprehensive Met Panel\n \n Removing CPT Code 87O87\n \n \n From 87553.0000 Urine Culture\n \n \n Creating Mail Message containing CPT Changes\n \n Sending message to LMI Mail Group\n \n Relinking NATIONAL VA LAB CODES TO WKLD CODE\n LR*5.2*243\n \n*1. The CPT Code Modifiers Patch LR*5.2*243 patch automatically removes\n \n \nUpdating Routine file...\n \nUpdating KIDS files...\n \nLR*5.2*243 Installed. \n Feb 29, 2000@15:54:32\n \n Install Message sent \nCPT workload credit for any test(s) with the status of NOT PERFORMED (NP).\n \n**** End of Example of Install dialog *******\n \n \nPost Installation Instructions:\n \nAfter the new file structures have been installed the post installation\nsoftware will perform the following:\n \n1. Review each code to determine if the code is valid and has not been\n \ninactivated in the CPT file (#81). If the code is inactive or erroneous,\nthe code is removed. The software will record the code removal in the WKLD\nCODE NOTES field (#24). A MailMan message addressed to the local LMI mail\ngroup will be generated if any codes are removed.\n \n2. The data in the file is converted to the new data structure of the WKLD\nCODE file (#64).\n \n3. ASSOCIATED NAMES in the WKLD CODE file (#64) are updated to reflect\ncurrent linkages.\n*2. When the Laboratory workload reporting LRNIGHTY background job is\n \n4. The Post Installation routine will set the WKLD CODE (#64) file\nBILLABLE PROCEDURE (#4) field to yes for the codes:\nVenipunture Outpatient [89343.0000]\nVenipunture Travel Time [89341.0000]\n**** Note: If the laboratory is does not perform venipuncture functions,\nthe BILLIABLE PROCEDURE field should be set to 'NO'.\n'Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] option can be used to\nedit the BILLABLE PROCEDURE field.\n \ntasked, a secondary program examines the WKLD CODE file (#64) to determine\n \n************************\nLABORATORY CURRENT PROCEDURAL TERMINOLOGY (CPT) CODES AND MODIFIERS PATCH\nLR*5.2*243 INSTALLATION AND IMPLEMENTATION GUIDE in PDF format is provided\nwith this patch. Please refer to this document for details and specific\ninstructions. The patch description does not include ALL implementation\nconsiderations or complete file setup instructions.\n************************\n \n \nif any CPT code(s) are inactive in the CPT file (#81) or if other file\nPCE Workload Capture Setup:\n \nThe Laboratory Information Manager (LIM) or the Information Resource\nManagement (IRM) service must do setup several procedure files/fields.\n \nNOTE: The asterisk (*) indicates new enhancements for patch LR*5.2*243.\n \n1. The LAB SERVICE package V. 5.2 must be installed. This is done by IRM.\n \n2. PCE workload must be turned on for Laboratory. Someone other than the\npointers are broken. If inactive code(s) are found, a VA Mailman message\nLIM usually does this.\n \n3. PCE PATIENT CARE ENCOUNTER Version 1.0 must be loaded on the system and\nfully patched. This is done by IRM.\n \n4. The LABORATORY SITE file (#69.9), WKLD STATS ON field (#17) must be set\nto YES. This is usually done by the LIM.\n \n5. The LABORATORY SITE file (#69.9), PCE/VSIT ON field (#615) definition\nentry should be defined other than OFF, the recommended entry is PCE/VSIT\nCategory: DATA DICTIONARY\nis automatically generated and sent once a day to the LMI Mail Group\nONLY. The VA FileMan Enter Edit [DIEDIT] option is used to defined the\nPCE/VSIT ON field (#615). This is done by the LIM or IRM.\n \n6. The LABORATORY SITE file (#69.9), PCE DEFAULT PROVIDER field (#617)\nshould have a valid active provider identified. This is usually the Chief\nof Pathology and Laboratory Medicine (P&LMS). The PCE DEFAULT PROVIDER\nfield (#617) in the past was required for the background job to run. This\npatch no longer requires a valid entry in this field. This field is used\nwhenever the ordering provider is not a valid active provider; the default\nprovider is substituted instead of the inactive provider. If the ordering\ncontaining information about the code(s) and the action(s) taken by the\nprovider and the default provider are both invalid the order will be\nmarked and skipped. A report will be sent to the local mail group G.LMI\nindicating the observed problem. This usually done by the LIM.\n \n7. The LABORATORY SITE file (#69.9), DEFAULT LAB OOS LOCATION (#.8) field\nmust have a valid HOSPITAL LOCATION defined. This field is defined by\nusing the Create Laboratory OOS Locations [LR WKLD LOCATION] option. This\noption will correctly name the DEFAULT LAB OOS location entry. This is\nusually done by the LIM.\nNOTE: This is a critical field entry. The CPT Workload capture will not be\nsoftware.\nperformed if this field has no entry or the entry is correct. All DEFAULT\nLAB OOS LOCATION names must begin with 'LAB DIV '\n \n8. The MAILMAN SITE PARAMETERS file (#4.3), DEFAULT INSTITUTION field\n(#217) must be defined. This is done by IRM.\n \n* 9. The LABORATORY SITE file (#69.9), DEFAULT BLOOD SPECIMEN field (#100)\nmust have a valid blood specimen defined. This is done by the LIM.\n \n10. Each Accession area that should have workload collected must have the\n \naccession area activated. The accession area is activated by using the\nTurn on workload stats for accession area [LR WKLD STATS ON ACC AREA]\noption. This is done by the LIM.\n \n11. Each accession area can have a default Occasion of Service (OOS)\nlocation defined. This allows each accession area to be assigned a\nspecific DEFAULT OOS LOCATION. Multi-divisional sites most often use this.\nThe default OOS location can be defined by using the Edit ACC Area OOS\nLocations [LR WKLD ACC AREA LOCATION] option. A DEFAULT OOS LOCATION\nshould be defined for each institution generating workload. This is done\n*3. The enhanced Laboratory workload software processes the workload data\nby the LIM.\n \n12. Every orderable test in LABORATORY TEST file (#60) must be linked to a\nNATIONAL VA LAB CODE (also referred to as WKLD CODE or NLT codes). The\nNATIONAL VA LAB CODE is linked by using the Semi-automatic Linking of file\n60 to 64 [LR7O 60-64 AUTO] and Manual Linking of file 60 to 64 [LR7O 60-64\nMANUAL] options. This is done by the LIM.\n \n13. Each WKLD CODE linked in the above step must be assigned valid CPT\ncodes, these CPT codes will be used to report workload to the Patient Care\nin LABORATORY SITE file (#69.9), PCE DEFAULT PROVIDER field (#617) and LAB\nEncounter (PCE) workload API. This is done by using the Edit or Print WKLD\nCODES [LR WKLD CODE EDIT PRINT] option. This is done by the LIM.\n \n \nSoftware Logic:\n \nAfter the file setup steps have been completed, the software logic of the\nbackground job will use the above-defined fields. The software will scan\ncollected orders, extract all valid CPT codes, and pass the CPT workload\ndata to the PCE workload API. In addition, the software will also will\nOOS LOCATION field (#.8) even if these two fields are not defined. A VA\ncapture LMIP venipuncture workload for ALL patients without regard for\nlocation type.\n \nNOTE: Outpatient locations are entries in HOSPITAL LOCATION file (#44)\nthat have the TYPE field (#2) defined as; CLINIC, MODULE or OTHER.\n \nThe software uses the cross reference of\n^LR(69,"AA",ORDER NUMBER, SPECIMEN) to determine what orders have been\ncollected. The software orders through the cross-reference and examines\neach order number using the following:\nMailman report is automatically generated and sent to the LMI mail group\n \n \n1. The order status must be collected.\n \n2. The order must be for a Patient from the PATIENT file (#2).\n \n*3. For venipuncture (specimen collection) workload capture ONLY,\ncollection type must be one of the following:\nLaboratory Collect (LC) = Venipuncture Travel Time - 89341.0000\nImmediate Collect (I) = Venipuncture Travel Time - 89341.0000\nonce a day indicating those orders requiring additional attention because\nSend Patient (SP) = Venipuncture Outpatient - 89343.0000\n*Note: Collection type is only used for venipuncture workload capture.\nCollection type has no bearing on CPT workload capture.\nBoth In-Patient and Outpatient receive LMIP venipuncture workload credit.\n \n4. The ordering provider is validated as a current active provider. If the\nordering provider is not valid, the default provider will be used if the\ndefault provider is valid. If neither of the providers is valid, the order\nis marked appropriately and skipped.\n \nthe default fields were not defined.\n5. CPT workload is only collected for Out-Patients based on HOSPITAL\nLOCATION file (#44) that have the TYPE field (#2) defined as: CLINIC,\nMODULE, or OTHER LOCATION. Venipuncture workload is NOT controlled by\nHOSPITAL LOCATION type.\n \n*6. This patch uses the INSTITUTION field (#3) of the HOSPITAL LOCATION\nfile (#44) to determine the institution that should receive CPT workload\ncredit. If the INSTITUTION field (#3) is not defined then the DEFAULT\nINSTITUTION is used.\nNOTE: See step 8 of the Setup instructions.\n ENHANCEMENT\n \n \n7. Each test is checked to ensure that it does not have the status of\nCANCEL or NOT PERFORMED before CPT workload is processed.\n \n8. Each test is checks the accession area's LAB OOS LOCATION. If defined\nthe accession area's LAB OOS LOCATION is used.\n \n9. Each collected test will be checked for a NATIONAL VA LAB CODE field\n(#64) in the LABORATORY TEST file (#60).\n \n*4. The automated Venipuncture workload reporting functionality used the\n10. The NATIONAL VA LAB CODE field (#64) point to the WKLD CODE file\n(#64). The software checks the WKLD CODE file (#64), CODE field (#18) for\nCPT codes.\n \n*11. This patch has changed the data dictionary definition of the CODE\nfield (#18) to a variable pointer. The patch installation will converts\nall valid codes to the new file structure and reset the cross-references.\nIf the code is invalid, the code is removed. A note will be entered in the\nWKLD CODE file (#64), WKLD CODE NOTES field (#24) indicating when the\nremoval occurred.\nsame criteria as the Laboratory workload reporting.\n \n*12. Each CPT code is checked to make sure it is valid (active). Each CPT\ncode is checked for allowed modifiers. If there are multiple occurrences\nof identical CPT codes, the software will automatically add the modifier\nDISTINCT PROCEDURAL SERVICE (59) to each succeeding CPT code if this\nmodifier is allowable.\n \n13. The specimen DATE/TIME OF COLLECTION is used as the encounter date\ntime.\n \n \nNOTE: If the scan of order passes all of the checks and there are valid\nCPT codes associated with the collected (accessioned) test, CPT workload\ndata is passed to the PCE workload API.\n \nListing of elements passed to PCE workload API.\n$$DATA2PCE^PXAPI\n \nOOS location\nReporting Institution\nProvider\n5. The enhanced Laboratory software will now acknowledge the actual user\nEncounter Date/time\nPatient Pointer\nStop Code number of the ordering location.\nService Category of OOS\nEncounter type of Ancillary\nCPT codes for each collected test as defined in WKLD CODE file.\n*CPT modifier if appropriate.\n \n*14. If an Order Test is marked as NOT PERFORMED by the laboratory and CPT\nworkload has already been sent to PCE, a background job will automatically\nentering lab test orders in LAB ORDER ENTRY file (#69) for the PCE\nsend delete CPT workload messages for that order to the PCE Workload API.\nNOTE: If the Not Performed test is ultimately verified, no CPT workload is\nsent after NOT PERFORMED delete has been sent.\n \n15. The PCE API passes back to the Laboratory software application the\nencounter number used to store the PCE API passed information. It is\npossible for one order to have multiple encounter number based on the\nACCESSION AREA's OOS definition. The PCE encounter number is displayed on\nvarious order status screens in the Visit Number(s).\n \nRegistered Encounter rather than the user that started or tasked the PCE\nExample: Order/test status screen - Visit Number(s): show the PCE\nencounter numbers.\nTest Urgency Status Accession\n -Lab Order # 162690 Provider: The man\n Visit Number(s): 99999;\n BLOOD \n CBC PROFILE ROUTINE Test Complete 12/02/1999@07:41 HE 1202 10\n -Lab Order # 162690 Provider: The man\n Visit Number(s): 99999;\n BLOOD SERUM\nWorkload background job.\n MAGNESIUM ROUTINE Test Complete 12/02/1999@08:02 DA 1202 32\n CHEM 7 ROUTINE Test Complete 12/02/1999@08:02 DA 1202 32\n -Lab Order # 163491 Provider: The man\n Visit Number(s): 99999;\n BLOOD SERUM\n URIC ACID ROUTINE Test Complete 12/02/1999@14:37 DA 1202 234\n \nBy using the User's Visit Review [PXQ USER REVIEW] option User's Visit\nReview one can determine what CPT workload has been captured for a given\norder. This is an example of the option. The Visit Number(s) information\n \nis entered at the 'Enter VISIT (UNIQUE ID or '1239):' prompt. \n Select one of the following:\n \n P Patient List of Visits\n I Internal Entry Number of VISIT\n \nSelect by (P)atient or (I)en: P// Internal Entry Number of VISIT\n \nEnter VISIT (UNIQUE ID or `1239): `99999\n 12-2-1999@06:57:38 PATIENT,SICK \n6. The LABORATORY SITE file (#69.9) locking logic is modified to correct\nLAB DIV 623 OOS ID 108 29TRC-MUS\n \n Select one of the following:\n \n D Default (first field of each file/subfile)\n A All fields in a file/subfile (except 'NULL')\n C Customized by User (Default plus added fields) \n \n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nTo customize your display use VA FileMan to add entries in file PCE\n ROUTINE\nthe problem of not being able to edit the LABORATORY SITE file (#69) while\nCUSTOMIZE REPORT, with your NAME, FILE/SUBFILE#s, and FIELD#s that you\nwant to have included in the report.\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \nEnter '^^' to exit option\nFormat of Print out: // All fields in a file/subfile (except 'NULL')\n \nDEVICE: HOME// TELNET Right Margin: 80// \n \n**************************************************************\nthe LRNIGHTY background job is running.\n*** R E C O R D O F R E L A T E D E N T R I E S ***\n \n The Following is the VISIT file entry and\n ALL records pointing back to this entry.\n \n VISIT RECORD --- #999999\n \n DATE/TIME --- DEC 02, 1999@06:57:38\n PATIENT --- PATIENT,SICK\n LOCATION --- LAB DIV 623 OOS ID 108\nOption Changes\n----------------------------------------------------------------\n FILE = VISIT #9000010 RECORD #99999\n VISIT/ADMIT DATE&TIME = DEC 02, 1999@06:57:38\n DATE VISIT CREATED = DEC 02, 1999@07:28:51\n TYPE = VA\n PATIENT NAME = PATIENT,SICK\n LOC. OF ENCOUNTER = MUSKOGEE, OK\n SERVICE CATEGORY = DAILY HOSPITALIZATION \n DSS ID = LABORATORY\n DEPENDENT ENTRY COUNT = 3\n \n DELETE FLAG = \n PARENT VISIT LINK = \n DATE LAST MODIFIED = DEC 02, 1999@07:28:52\n CHECK OUT DATE&TIME = \n ELIGIBILITY = NSC, VA PENSION\n HOSPITAL LOCATION = LAB DIV 623 OOS ID 108\n CREATED BY USER = WORKER,HARD V\n OPTION USED TO CREATE = LRENTER\n PROTOCOL = \n OUTSIDE LOCATION = \n*7. Add tests to a given accession [LRADD TO ACC] option is modified to\n VISIT ID = 29TRC-MUS\n PATIENT STATUS IN/OUT = IN\n ENCOUNTER TYPE = ANCILLARY\n SERVICE CONNECTED = \n AGENT ORANGE EXPOSURE = \n IONIZING RADIATION EXPOSURE = \n PERSIAN GULF EXPOSURE = \n MILITARY SEXUAL TRAUMA = \n COMMENTS = \n PACKAGE = PCE PATIENT CARE ENCOUNTER\nactivate the PCE Workload API. Any test(s) added to an accession will now\n DATA SOURCE = LAB DATA\n \n-----------------------------------------------------------------\n FILE = OUTPATIENT ENCOUNTER #409.68 RECORD #999999\n DATE = DEC 02, 1999@06:57:38\n PATIENT = PATIENT,SICK\n CLINIC STOP CODE = LABORATORY\n LOCATION = LAB DIV 623 OOS ID 108\n VISIT FILE ENTRY = DEC 02, 1999@06:57:38\n CHECK OUT PROCESS COMPLETION = DEC 02, 1999@07:28\nreceive PCE Workload credit.\n ORIGINATING PROCESS TYPE = STOP CODE ADDITION\n APPOINTMENT TYPE = REGULAR\n MEDICAL CENTER DIVISION = MUSKOGEE VAMC\n STATUS = INPATIENT APPOINTMENT\n ELIGIBILITY OF ENCOUNTER = NSC, VA PENSION\n UNIQUE VISIT NUMBER = 29TRC-MUS\n EDITED LAST BY = WORKER,HARD V\n DATE/TIME LAST EDITED = DEC 02, 1999@07:28:52\n CREATED BY = WORKER,HARD V\n DATE/TIME CREATED = DEC 02, 1999@07:28:52\n \n COMPUTER GENERATED? = YES\n-----------------------------------------------------------------\n FILE = V PROVIDER #9000010.06 RECORD #99999\n PROVIDER = GIVER,CARE\n PATIENT NAME = PATIENT,SICK\n VISIT = DEC 02, 1999@06:57:38\n PRIMARY/SECONDARY = PRIMARY\n PERSON CLASS = Physicians (M.D.)\n EDITED FLAG = EDITED\n AUDIT TRAIL = 24-A 5591;24-E 5591;\n8. Order/test status [LROS] option is modified to correctly display\n PACKAGE = LAB SERVICE\n DATA SOURCE = LAB DATA\n-----------------------------------------------------------------\n FILE = V CPT #9000010.18 RECORD #99999\n CPT = 85025\n PATIENT NAME = PATIENT,SICK\n VISIT = DEC 02, 1999@06:57:38\n PROVIDER NARRATIVE = AUTOMATED HEMOGRAM\n QUANTITY = 1\n ENCOUNTER PROVIDER = GIVER,CARE\ntest(s) added to an accession.\n AUDIT TRAIL = 24-A 5591;\n PACKAGE = LAB SERVICE\n DATA SOURCE = LAB DATA\n-----------------------------------------------------------------\n The Following is the OUTPATIENT ENCOUNTER entry and\n most of the records pointing back to it.\n \n OUTPATIENT ENCOUNTER --- #99999\n-----------------------------------------------------------------\n \n \n \n FILE = V CPT #9000010.18 RECORD #99999\n CPT = 85025\n PATIENT NAME = PATIENT,SICK\n VISIT = DEC 02, 1999@06:57:38\n PROVIDER NARRATIVE = AUTOMATED HEMOGRAM\n QUANTITY = 1\n ENCOUNTER PROVIDER = GIVER,CARE\n AUDIT TRAIL = 24-A 5591;\n PACKAGE = LAB SERVICE\n DATA SOURCE = LAB DATA\n9. Enter/verify data (auto instrument) [LRVR] option is enhanced to allow\n-----------------------------------------------------------------\n FILE=TRANSMITTED OUTPATIENT ENCOUNTER #409.73 RECORD #999999\n NUMBER = 999999\n OUTPATIENT ENCOUNTER = DEC 02, 1999@06:57:38\n TRANSMISSION REQUIRED = YES\n TRANSMISSION EVENT = ADD\n DATE/TIME OF EVENT = DEC 02, 1999@07:28:52\n USER CAUSING EVENT = WORKER,HARD V\n PATIENT = PATIENT,SICK\n ENCOUNTER DATE = DEC 02, 1999 06:57:38\nusers to edit, add, or subtract atomic test(s) from the test list before\n HOSPITAL LOCATION = LAB DIV 623 OOS ID 108\n PATIENT SSN = 1010101010\n ENCOUNTER DIVISION = MUSKOGEE VAMC\n ENCOUNTER DIVISION (INTERNAL) = 1\n-----------------------------------------------------------------\n The Following is the SCHEDULING VISITS file.\n This is where Scheduling stores the CPT codes.\n \nTHERE ARE PROCEDURES IN PCE BUT NO RECORD IN SCHEDULING **\n \nbeginning the verification of an atomic test(s) and to continue to the\n===============================================\n \n ****END OF EXAMPLE****\n \n \n*Venipuncture Workload Capture:\n \n************************\nLABORATORY CURRENT PROCEDURAL TERMINOLOGY (CPT) CODES AND MODIFIERS PATCH\nLR*5.2*243 INSTALLATION AND IMPLEMENTATION GUIDE in PDF format is provided\nnext accession number if the current accession is not collected. This\nwith this patch. Please refer to this document for details and specific\ninstructions. The patch description does not include ALL implementation\nconsiderations or complete file setup instructions.\n************************\n \n1. *Patch LR*5.2*243 will automatically collects venipuncture workload\ndata identical to other types of collected workload data. Venipuncture\nworkload data will appear on workload reports broken down by standard\nreporting criteria.\n \nenhancement applies to both verifying by accession number or UID\n2. Originally, LMIP workload reporting did not include venipuncture as a\nbillable procedure; therefore, the software entered a manual style tally\nof totals for the institution by day. Now LMIP workload does allow\nvenipuncture workload. This patch automatically captures venipuncture by\ninstitution, by date, by WKLD CODE, and by event time and stores them in\nthe WKLD DATA (#64.1) file. Certain data elements are required when\nrecording workload. One of the required data elements is accession area.\nTherefore, some accession area must be utilized to satisfy the required\ndata field. This patch provides new fields that can be used to customize\ndata collection.\n(Universal Identification).\n \n3. The venipuncture workload ACTUALLY indicates that the laboratory\nobtained at least one specimen from the patient.\n \nNOTE: THE SPECIMEN OBTAINED MAY NOT BE A BLOOD SPECIMEN. WHAT THE DEFAULT\nCODES (venipuncture) INDICATES IS THAT THE LAB COLLECTED A SPECIMEN FOR\nTHIS PARTICULAR ORDER. ONLY 1 SPECIMEN COLLECTION WORKLOAD UNIT PER ORDER\nIS CAPTURED REGARDLESS OF THE NUMBER OF ACTUAL SPECIMENS COLLECTED FOR THE\nORDER.\n \n \n4. Specimen Collection workload codes of Venipuncture Travel Time\n[89341.0000] is the default code for Lab Collect (LC) and Immediate\nCollect (I). Specimen Collection WKLD CODE of Venipuncture Outpatient\n[89343.0000] is default code for Send Patient (SP). \n \n5. *Venipuncture workload is captured based on INSTITUTION field (#3) in\nthe HOSPITAL LOCATION file (#44) of the ordering location. If no\nINSTITUTION is defined, the default institution defined by MAILMAN will be\nused.\n* There is a new field exported with this patch. The DIVISION PARAMETERS\n*10. Batch data entry [LRSTUF] option is modified to capture LMIP workload\nfield (#618) is a multiple in the LABORATORY SITE file (#69.9). There are\ntwo fields in the DIVISION PARAMETERS field (#618) multiple that can be\nused to customize the venipuncture workload collection.\n - DIVISION PARAMETER field (#.01) points to the INSTITUTION file (#4).\nThis field will allow the LABORATORY SITE file (#69.9) to be\nmulti-divisional.\n - PHLEBOTOMY DEFAULT ACC AREA field (#618) points to the ACCESSION file\n(#68).\n \n6. * The software will examine the ordering location for the INSTITUTION\ncounts.\nthat location is assigned. The software will look up in the LABORATORY\nSITE file (#69.9), DIVISION PARAMETERS subfile (#) to get the ACCESSION\narea to be used when storing venipuncture workload. The MAJ. SECT and the\nSUBSECTION fields in WKLD DATA (#64.1) file will be set to ACCESSION area\ndefined.\nNote: The default venipuncture ACCESSION area is HEMATOLOGY.\n LAB DIVISION is CLINICAL PATHOLOGY\n Date and Time is the SPECIMEN COLLECTION date/time.\n The LAB TEST is the first collected test in the order.\n \nDescription:\n \n7. * The Venipuncture workload capture assumes that there is an accession\narea that begins with the letters 'HEM'. If there is no accession area\nbeginning with the letters 'HEM', then venipuncture default accession area\nwill be the accession area having the internal entry number of 10 in the\nACCESSION file (#68).\n \n8. ** This patch creates a new multiple in the LABORATORY SITE file\n(#69.9), DIVISION PARAMETERS field (#618). This new multiple will be used\nto allow in the future, each institution to have the opportunity to\ncompletely define separate laboratory parameter definitions. The first\n11. Results entry (batch) [LRMISTUF] is modified to capture LMIP workload\nentry in this multiple is PHLEBOTOMY DEFAULT ACC AREA field (#618). This\nfield will allow each institution to define what accession area\nvenipuncture workload should be assigned. If this field is not defined\nthen the default Hematology accession area outlined above will be used.\n \n \nThis is a listing of captured venipuncture workload data.\nDATE: DEC 02, 1999\nWKLD CODE: +Venipuncture Outpatient UNIT WEIGHT: 1\nACCESSION WKLD CODE TIME: 12.5713 LAB TEST: GLUCOSE\ncounts.\n WEIGHT MULTIPLIER: 1 LAB DIVISION: CLINICAL PATHOLOGY\n MAJ. SECT.: SEND OUT SUBSECTION: SEND OUT\n ACC NO.: CH 1202 15 PATIENT: NOSE,LIMP\n ORIGINAL ACC DATE: DEC 02, 1999\n DATE ORDERED: DEC 02, 1999@12:57:13\n SPECIMEN NO.: 1 SPECIMEN: BLOOD\n REPORT ROUTING LOCATION: 2S PROVIDER: GINSBURG,RONNIE\n LOG IN PERSON: STALLING,FRANK LOCATION TYPE: WARD\n ORDERING LOCATION: 7 ATU URGENCY: ROUTINE\n VERIFY TECH.: STALLING,FRANK WORK AREA: SEND OUT\n \n12. The Bypass normal data entry [LRFAST] option is modified to accept the\nresponse of "YES" at the "Do you want to enter draw times?" prompt.\n \n13. The Accessioning tests ordered by ward order entry [LROE] option is\nmodified to accurately determine if the tasked ROLLOVER ACCESSION [LRTASK\nROLLOVER] option is actually running.\n\n\n \n============\n \n14. The Review by order number [LRCENLKUP] option date displays is\nconverted to use Kernel date conversion utilities.\n \n15. Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] option is enhanced\nto print all WKLD CODES, even if they have not been activated. This will\ncorrect the problem of WKLD CODES that have a suffix of .0000 not\nprinting.\n \n16. Workload Report [LRCAPR1] option has been enhanced to allow the user\n \nto select combinations of LEDI collecting institutions or Hospital\nlocations.\n \n17. When verifying Microbiology specimens the user is prompted for\nadditional workload. A screen has been added to allow only a number\nbetween 1 to 25. This is to prevent inadvertent entering of WKLD CODE\nnumber instead of the multiply by number.\n \nLaboratory Menu and Option Changes:\n============================\nThe Laboratory CPT Code Modifier enhancement patch LR*5.2*263 provides the\nLIM workload menu [LR LIM/WKLD MENU]\n \nThe LIM workload menu [LR LIM/WKLD MENU] is modified to add the new\nInActive WKLD CODE File CPT Codes Print [LRCAPCPTI] option.\n \nNew Option\n \nInActive WKLD CODE File CPT Codes Print [LRCAPCPTI] option\n \nThe new Inactive WKLD CODE File CPT Codes Print [LRCAPCPTI] option scans\nLaboratory Version 5.2 software application the ability to transmit\nthe WKLD CODE file (#64) for code(s) that are no longer allowed or code(s)\nthat are inactive in the CPT file (#81). The "WKLD CODE - CODE CHECK\nREPORT" is then generated displaying all CPT code(s) that are no longer\nallowed, code(s) that are inactive and why they are inappropriate,\nlaboratory test names linked to WKLD code(s) (i.e., laboratory test names\nlisted on the report will not receive PCE Workload credit), and code(s)\nrequiring a different entry in the CPT file (#81) in order to capture PCE\nWorkload data.\n \nThe new Inactive WKLD CODE File CPT Codes Print [LRCAPCPTI] option is also\nCurrent Procedural Terminology (CPT) codes and Modifiers to the Patient\nuseful when a new CPT Code file is released (i.e., new CPT code files are\nusually distributed annually). The new CPT Code files may contain codes\nthat are no longer allowed or codes that are inactive in the VISTA CPT\nfile (#81). When CPT codes defined in the WKLD CODE file (#64) are deemed\ninactive in the CPT file (#81), then the software enters a date in the\nWKLD CODE file (#64), Inactive Date field (#3) for those inactive codes.\nThe Laboratory PCE interface checks each CPT code in the WKLD CODE file\n(#64) before sending CPT workload to the PCE API. Whenever CPT code(s) are\nno longer allowed or has been inactivated a VA Mailman message containing\nthe "WKLD CODE - CODE CHECK REPORT" is sent once a day to the LMI mail\nCare Encounter (PCE) workload capture Application Interface (API). The\ngroup.\n \nExample: WKLD CODE - CODE CHECK REPORT\n \nSubj: WKLD CODE - CODE CHECK REPORT 12/14/99@14:44:25 [#83460]\nFrom: POSTMASTER In 'IN' basket. Page 1\n-----------------------------------------------------------------\nLab Order Number 100 has no Institution for the ordering location\n===================\n86081.0000 [1] ABO Cell and Rh(D) Typing\ntransmission of workload in the form of CPT codes is done in the\n86083 BLOOD TYPING;ANTIBODY SCREEN\nIs an inactive CPT code.\nAssociated Tests\n ABO/RH TYPING {1101}\nInactivation date of Dec 13, 1999 has been entered\n****************\nListing of all offending codes\n ICPT 82534\n \n****** END OF EXAMPLE ********\nbackground (no user interaction is required). Because of the background\n \n=====================\nData Dictionary Change Summary:\n \nThe following file and field changes occur with the installation of VISTA\nLaboratory CPT Code and Modifiers Patch LR*5.2*263.\n \nWKLD CODE file (#64)\n \n The WKLD CODE file (#64) was modified to convert existing file data to\nmethod of workload reporting several new fields were created and the\na new data structure, new fields were created, and existing fields were\nmodified to support the Laboratory workload reporting enhancements of CPT\ncodes and modifiers.\n \n1) CODE field (#18) multiple has been changed from a free text field to a\nvariable pointer.\n \n2) CODE field (#.01) has been changed from a free text field to a variable\npointer. This field is screened to allow only active code entries to the\nMORPHOLOGY FIELD file (#61.1), ICD DIAGNOSIS file (#80), and CPT file\nLaboratory software logic was modified.\n(#81).\n \n3) CODE subfile (#64.018) was modified to add the new CODE NOTES field\n(#6). This new word processing field is used for tracking general notes\nregarding a particular code.\n \n4) WKLD Code Notes field (#24) is a new word processing field used for\nstoring general notes regarding inactive or erroneous code(s) that is\nautomatically removed by the software.\n \n \n \n5) LOINC Code field (#4) was changed to point to the LOINC CODE file\n(#95.3).\n \n6) The new Default LOINC Code field (#25) points to the LOINC CODE file\n(#95.3). This field is used to identify the default LOINC code. This\nfield is usually used when the specimen is not clinically significant\n(i.e. body fluids). 'L FOR LOINC' was removed from the set of codes in\nfield TYPE (#64.018,5).\n \nLABORATORY SITE file (#69.9)\nCPT modifier provides the means by which the reporting physician can\n \n1) LABORATORY SITE file (#69.9), DIVISION PARAMETERS field (#618) multiple\nis a new field exported with this patch. These new fields are used to\ncustomize the automated Venipuncture workload reporting functionality.\n \n2) The new DIVISION PARAMETERS field (#.01) points to the INSTITUTION file\n(#4). This field allows the LABORATORY SITE file (#69.9) to be\nmulti-divisional for Venipuncture workload reporting.\n \n3) The new VENIPUNCTURE DEFAULT ACC AREA subfile (#618) points to the\nindicate that a service or procedure that has been performed has been\nACCESSION file (#68). This new field is used by the Venipuncture workload\nreporting background job to determine the accession area for the\nINSTITUTION to be use for Venipuncture workload reporting.\nAssociated NOIS\n===============\n \n \n \nTAM-0899-31723 ALB-1299-50818\nPRO-0999-11965 CLL-1099-43226\naltered by some specific circumstances but not changed in its definition\nLON-0999-62211 BHS-0999-11616\nHIN-0499-42772 NCH-0100-41945\nALB-0199-52914 IOW-0600-41401\nFAV-0600-71380 HUN-0600-21379\nPHI-0600-21370 TUA-0600-31347\n \n \nTest Sites:\n===========\nLong Beach, CA\nor code. The judicious application of modifiers obviates the necessity for\nKansas City, MO\nMilwaukee, WI\nMuskogee, OK\nIowa City, IA\nFayetteville, AR\nHuntington, WV\n \n \nRoutine Summary:\n================\nseparate procedure listing that may describe the modifying circumstances.\n \n \n <tab> ;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n Checksum Values\nRoutine Before After Patch List\nName Patch Patch List\n-------- -------- --------- --------\nLR263 N/A 7411624 263\nLRCAPPH 10281625 11522455 1,19,127,136,138,158,153,263\n \nLRCAPPH1 4949612 7745000 127,136,138,158,263\nLRCAPPH3 N/A 6642885 263\nLRCAPPH4 N/A 3179202 263\nLRCAPPNP N/A 1653480 263\nLRCAPR1 8086519 9529509 263\nLRCAPR2 8195892 8701428 88,105,263\nLRCAPR4 6795674 7338553 263\nLRCAPV3 8123485 8391773 105,263\nLRCAPVM 5012091 5237437 49,163,263\nLRCE 13210738 13336460 28,76,103,121,153,210,202,263\n \nLRCENDEL 16365039 15254614 100,121,202,221,263\nLRDIQ 9573488 10128715 86,153,263\nLRGP2 3525048 6353513 153,221,263\nLRMISTF1 14470635 14019130 121,128,202,263\nLROE 14732765 14550901 100,121,201,221,263\nLRORD3 7349040 7385601 153,263\nLROS 16807258 16882422 121,153,202,210,221,263\nLRSTUF2 8013388 8012263 121,153,263\nLRTSTSET 12634119 12775322 65,100,121,153,201,202,263\nLRTT5P1 12297887 12439150 153,221,263\nNOTE: ONLY PATIENT ORDERS FROM HOSPITAL LOCATION WITH THE TYPE OF CLINIC,\nLRVER1 6428527 6801758 42,153,201,215,239,240,263\nLRVER3A 10780359 10780812 1,5,42,100,121,153,190,221,254,263\nLRVR 12695281 13316120 42,153,263\nLRVR4 8714660 8661306 14,42,121,153,221,263\nLRVR5 11783101 11729747 1,42,153,263\nLRVRA 6318899 6374326 153,221,263\nLRXREF 9255866 9584168 70,153,263\n \nRequired Patch Installation List:\n \nMODULE, OR OTHER WILL RECEIVE CPT WORKLOAD CREDIT. THE SOFTWARE USES\n \nLR*5.2*105\nLR*5.2*153\nLR*5.2*158\nLR*5.2*202\nLR*5.2*221\nLR*5.2*240\nLR*5.2*254\nPX*1.0*73\nPX*1.0*74\nSubject: CPT CODE MODIFIERS\nLOCATION TYPE TO DETERMINE IF THE ORDER IS FOR AN OUT-PATIENT OR\nICPT*6.0*7\n \nInstallation Instructions\n=========================\n************************\nLABORATORY CURRENT PROCEDURAL TERMINOLOGY (CPT) CODES AND MODIFIERS PATCH\nLR*5.2*263 INSTALLATION AND IMPLEMENTATION GUIDE in PDF format is provided\nwith this patch. Please refer to this document for details and specific\ninstructions. The patch description does not include ALL implementation\nconsiderations or complete file setup instructions.\nIN-PATIENT.\n************************\n \nThe VISTA Laboratory CPT Codes and Modifiers Patch LR*5.2*263 Installation\nand Implementation Guide is available in PDF (i.e., LR_CPTIG.PDF) at the\nfollowing FTP addresses:\n \nOffice of Information Field Office FTP Address Directory\n======================================================================\nAlbany 152.127.1.5 anonymous.software\nHines 152.131.2.110 anonymous.software\n \nSalt Lake City 152.131.2.1 anonymous.software\n \n \n \n \n \nUsers may remain on the system, but installation should be done during off\npeak hours and when the Laboratory computer users are idle. None of the\nlaboratory tasked jobs need to be stopped.\n \nEnhancements and Modifications:\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan \n menu. This option will load the KIDS package onto your system.\n 2. Review your mapped set. If the routines are mapped,\n they should be removed from the mapped set at this time.\n 3. The patch has now been loaded into a Transport global \n on your system. You now need to use KIDS to install the \n Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n Print Transport Global\n=========================\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 5. No options need to be placed out of service.\n 6. Installation time is less than 15 minutes during off peak\n hours,and less than 30 minutes during\n peak hours which is NOT RECOMMENDED.\n 7. Installation of this patch require minimal \n disk space.\n 8. From the 'Installation Menu' of the KIDS menu, run the option \n \n 'Install Package(s)'. Select the package \n 'LR*5.2*263' and proceed with the install.\n 9. If any routines were unmapped as part of step 2, they \n should be returned to the mapped set once the \n installation has run to completion.\n \n \nExample of install dialog:\n \nSelect INSTALL NAME: LR*5.2*263 Loaded from Distribution\nLaboratory CPT Code Modifiers Patch LR*5.2*263 contains the following\n2/29/00@15:51:34\n => LR*5.2*263\n \nThis Distribution was loaded on Feb 29, 2000@15:51:34 with header of \n LR*5.2*263\n It consisted of the following Install(s):\n LR*5.2*263\nChecking Install for Package LR*5.2*263\nWill first run the Environment Check Routine, LR263\n \nenhancements and changes:\n \n --- Environment Check is Ok ---\n \n \nInstall Questions for LR*5.2*263\n \nIncoming Files:\n \n \n 64 WKLD CODE\n \nNote: You already have the 'WKLD CODE' File.\n \n \n 69.9 LABORATORY SITE\nNote: You already have the 'LABORATORY SITE' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nNOTE: The asterisk ('*') indicates significant enhancements or file\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\nDEVICE: HOME// TELNET\nInstall Started for LR*5.2*263 : \n Feb 29, 2000@15:53:41\n \nBuild Distribution Date: Jan 27, 2000\n \nstructure changes. \n \n Installing Routines:\n Feb 29, 2000@15:53:41\n \n Installing Data Dictionaries: \n Feb 29, 2000@15:53:43\n \n Installing PACKAGE COMPONENTS: \n \n Installing OPTION\n \n Feb 29, 2000@15:53:43\n \n Running Post-Install Routine:\nCONV^LR263.......................................\n \n Removing CPT Code 83019\n \n From 84483.0000 Helicobacter Pylorii Breath\n \n Removing CPT Code 80054\n \n \n From 81853.0000 Comprehensive Met Panel\n \n Removing CPT Code 87O87\n \n From 87553.0000 Urine Culture\n \n \n Creating Mail Message containing CPT Changes\n \n*1. The CPT Code Modifiers Patch LR*5.2*263 patch automatically removes\n Sending message to LMI Mail Group\n \n Relinking NATIONAL VA LAB CODES TO WKLD CODE\n LR*5.2*263\n \n \n \nUpdating Routine file...\n \nUpdating KIDS files...\nCPT workload credit for any test(s) with the status of NOT PERFORMED (NP).\n \nLR*5.2*263 Installed. \n Feb 29, 2000@15:54:32\n \n Install Message sent \n \n**** End of Example of Install dialog *******\n \n \nPost Installation Instructions:\n \n \nAfter the new file structures have been installed the post installation\nsoftware will perform the following:\n \n1. Review each code to determine if the code is valid and has not been\ninactivated in the CPT file (#81). If the code is inactive or erroneous,\nthe code is removed. The software will record the code removal in the WKLD\nCODE NOTES field (#24). A MailMan message addressed to the local LMI mail\ngroup will be generated if any codes are removed.\n \n*2. When the Laboratory workload reporting LRNIGHTY background job is\n2. The data in the file is converted to the new data structure of the WKLD\nCODE file (#64).\n \n3. ASSOCIATED NAMES in the WKLD CODE file (#64) are updated to reflect\ncurrent linkages.\n \n4. The Post Installation routine will set the WKLD CODE (#64) file\nBILLABLE PROCEDURE (#4) field to yes for the codes:\nVenipunture Outpatient [89343.0000]\nVenipunture Travel Time [89341.0000]\ntasked, a secondary program examines the WKLD CODE file (#64) to determine\n**** Note: If the laboratory is does not perform venipuncture functions,\nthe BILLIABLE PROCEDURE field should be set to 'NO'.\n'Edit or Print WKLD CODES [LR WKLD CODE EDIT PRINT] option can be used to\nedit the BILLABLE PROCEDURE field.\n \n \n************************\nLABORATORY CURRENT PROCEDURAL TERMINOLOGY (CPT) CODES AND MODIFIERS PATCH\nLR*5.2*263 INSTALLATION AND IMPLEMENTATION GUIDE in PDF format is provided\nwith this patch. Please refer to this document for details and specific\nif any CPT code(s) are inactive in the CPT file (#81) or if other file\ninstructions. The patch description does not include ALL implementation\nconsiderations or complete file setup instructions.\n************************\n \n \nPCE Workload Capture Setup:\n \nThe Laboratory Information Manager (LIM) or the Information Resource\nManagement (IRM) service must do setup several procedure files/fields.\n \npointers are broken. If inactive code(s) are found, a VA Mailman message\nNOTE: The asterisk (*) indicates new enhancements for patch LR*5.2*263.\n \n1. The LAB SERVICE package V. 5.2 must be installed. This is done by IRM.\n \n2. PCE workload must be turned on for Laboratory. Someone other than the\nLIM usually does this.\n \n3. PCE PATIENT CARE ENCOUNTER Version 1.0 must be loaded on the system and\nfully patched. This is done by IRM.\n \nCategory: DATA DICTIONARY\nis automatically generated and sent once a day to the LMI Mail Group\n4. The LABORATORY SITE file (#69.9), WKLD STATS ON field (#17) must be set\nto YES. This is usually done by the LIM.\n \n5. The LABORATORY SITE file (#69.9), PCE/VSIT ON field (#615) definition\nentry should be defined other than OFF, the recommended entry is PCE/VSIT\nONLY. The VA FileMan Enter Edit [DIEDIT] option is used to defined the\nPCE/VSIT ON field (#615). This is done by the LIM or IRM.\n \n6. The LABORATORY SITE file (#69.9), PCE DEFAULT PROVIDER field (#617)\nshould have a valid active provider identified. This is usually the Chief\ncontaining information about the code(s) and the action(s) taken by the\nof Pathology and Laboratory Medicine (P&LMS). The PCE DEFAULT PROVIDER\nfield (#617) in the past was required for the background job to run. This\npatch no longer requires a valid entry in this field. This field is used\nwhenever the ordering provider is not a valid active provider; the default\nprovider is substituted instead of the inactive provider. If the ordering\nprovider and the default provider are both invalid the order will be\nmarked and skipped. A report will be sent to the local mail group G.LMI\nindicating the observed problem. This usually done by the LIM.\n \n7. The LABORATORY SITE file (#69.9), DEFAULT LAB OOS LOCATION (#.8) field\nsoftware.\nmust have a valid HOSPITAL LOCATION defined. This field is defined by\nusing the Create Laboratory OOS Locations [LR WKLD LOCATION] option. This\noption will correctly name the DEFAULT LAB OOS location entry. This is\nusually done by the LIM.\nNOTE: This is a critical field entry. The CPT Workload capture will not be\nperformed if this field has no entry or the entry is correct. All DEFAULT\nLAB OOS LOCATION names must begin with 'LAB DIV '\n \n8. The MAILMAN SITE PARAMETERS file (#4.3), DEFAULT INSTITUTION field\n(#217) must be defined. This is done by IRM.\n \n \n* 9. The LABORATORY SITE file (#69.9), DEFAULT BLOOD SPECIMEN field (#100)\nmust have a valid blood specimen defined. This is done by the LIM.\n \n10. Each Accession area that should have workload collected must have the\naccession area activated. The accession area is activated by using the\nTurn on workload stats for accession area [LR WKLD STATS ON ACC AREA]\noption. This is done by the LIM.\n \n11. Each accession area can have a default Occasion of Service (OOS)\n*3. The enhanced Laboratory workload software processes the workload data\nlocation defined. This allows each accession area to be assigned a\nspecific DEFAULT OOS LOCATION. Multi-divisional sites most often use this.\nThe default OOS location can be defined by using the Edit ACC Area OOS\nLocations [LR WKLD ACC AREA LOCATION] option. A DEFAULT OOS LOCATION\nshould be defined for each institution generating workload. This is done\nby the LIM.\n \n12. Every orderable test in LABORATORY TEST file (#60) must be linked to a\nNATIONAL VA LAB CODE (also referred to as WKLD CODE or NLT codes). The\nNATIONAL VA LAB CODE is linked by using the Semi-automatic Linking of file\nin LABORATORY SITE file (#69.9), PCE DEFAULT PROVIDER field (#617) and LAB\n60 to 64 [LR7O 60-64 AUTO] and Manual Linking of file 60 to 64 [LR7O 60-64\nMANUAL] options. This is done by the LIM.\n \n13. Each WKLD CODE linked in the above step must be assigned valid CPT\ncodes, these CPT codes will be used to report workload to the Patient Care\nEncounter (PCE) workload API. This is done by using the Edit or Print WKLD\nCODES [LR WKLD CODE EDIT PRINT] option. This is done by the LIM.\n \n \nSoftware Logic:\nOOS LOCATION field (#.8) even if these two fields are not defined. A VA\n \nAfter the file setup steps have been completed, the software logic of the\nbackground job will use the above-defined fields. The software will scan\ncollected orders, extract all valid CPT codes, and pass the CPT workload\ndata to the PCE workload API. In addition, the software will also will\ncapture LMIP venipuncture workload for ALL patients without regard for\nlocation type.\n \nNOTE: Outpatient locations are entries in HOSPITAL LOCATION file (#44)\nthat have the TYPE field (#2) defined as; CLINIC, MODULE or OTHER.\nMailman report is automatically generated and sent to the LMI mail group\n \nThe software uses the cross reference of\n^LR(69,"AA",ORDER NUMBER, SPECIMEN) to determine what orders have been\ncollected. The software orders through the cross-reference and examines\neach order number using the following:\n \n \n1. The order status must be collected.\n \n2. The order must be for a Patient from the PATIENT file (#2).\nonce a day indicating those orders requiring additional attention because\n \n*3. For venipuncture (specimen collection) workload capture ONLY,\ncollection type must be one of the following:\nLaboratory Collect (LC) = Venipuncture Travel Time - 89341.0000\nImmediate Collect (I) = Venipuncture Travel Time - 89341.0000\nSend Patient (SP) = Venipuncture Outpatient - 89343.0000\n*Note: Collection type is only used for venipuncture workload capture.\nCollection type has no bearing on CPT workload capture.\nBoth In-Patient and Outpatient receive LMIP venipuncture workload credit.\n \nthe default fields were not defined.\n4. The ordering provider is validated as a current active provider. If the\nordering provider is not valid, the default provider will be used if the\ndefault provider is valid. If neither of the providers is valid, the order\nis marked appropriately and skipped.\n \n5. CPT workload is only collected for Out-Patients based on HOSPITAL\nLOCATION file (#44) that have the TYPE field (#2) defined as: CLINIC,\nMODULE, or OTHER LOCATION. Venipuncture workload is NOT controlled by\nHOSPITAL LOCATION type.\n \n ENHANCEMENT\n \n*6. This patch uses the INSTITUTION field (#3) of the HOSPITAL LOCATION\nfile (#44) to determine the institution that should receive CPT workload\ncredit. If the INSTITUTION field (#3) is not defined then the DEFAULT\nINSTITUTION is used.\nNOTE: See step 8 of the Setup instructions.\n \n7. Each test is checked to ensure that it does not have the status of\nCANCEL or NOT PERFORMED before CPT workload is processed.\n \n8. Each test is checks the accession area's LAB OOS LOCATION. If defined\n*4. The automated Venipuncture workload reporting functionality used the\nthe accession area's LAB OOS LOCATION is used.\n \n9. Each collected test will be checked for a NATIONAL VA LAB CODE field\n(#64) in the LABORATORY TEST file (#60).\n \n10. The NATIONAL VA LAB CODE field (#64) point to the WKLD CODE file\n(#64). The software checks the WKLD CODE file (#64), CODE field (#18) for\nCPT codes.\n \n*11. This patch has changed the data dictionary definition of the CODE\nsame criteria as the Laboratory workload reporting.\nfield (#18) to a variable pointer. The patch installation will converts\nall valid codes to the new file structure and reset the cross-references.\nIf the code is invalid, the code is removed. A note will be entered in the\nWKLD CODE file (#64), WKLD CODE NOTES field (#24) indicating when the\nremoval occurred.\n \n*12. Each CPT code is checked to make sure it is valid (active). Each CPT\ncode is checked for allowed modifiers. If there are multiple occurrences\nof identical CPT codes, the software will automatically add the modifier\nDISTINCT PROCEDURAL SERVICE (59) to each succeeding CPT code if this\n \nmodifier is allowable.\n \n13. The specimen DATE/TIME OF COLLECTION is used as the encounter date\ntime.\n \nNOTE: If the scan of order passes all of the checks and there are valid\nCPT codes associated with the collected (accessioned) test, CPT workload\ndata is passed to the PCE workload API.\n \nListing of elements passed to PCE workload API.\n5. The enhanced Laboratory software will now acknowledge the actual user\n$$DATA2PCE^PXAPI\n \nOOS location\nReporting Institution\nProvider\nEncounter Date/time\nPatient Pointer\nStop Code number of the ordering location.\nService Category of OOS\nEncounter type of Ancillary\nentering lab test orders in LAB ORDER ENTRY file (#69) for the PCE\nCPT codes for each collected test as defined in WKLD CODE file.\n*CPT modifier if appropriate.\n \n*14. If an Order Test is marked as NOT PERFORMED by the laboratory and CPT\nworkload has already been sent to PCE, a background job will automatically\nsend delete CPT workload messages for that order to the PCE Workload API.\nNOTE: If the Not Performed test is ultimately verified, no CPT workload is\nsent after NOT PERFORMED delete has been sent.\n \n15. The PCE API passes back to the Laboratory software application the\nRegistered Encounter rather than the user that started or tasked the PCE\nencounter number used to store the PCE API passed information. It is\npossible for one order to have multiple encounter number based on the\nACCESSION AREA's OOS definition. The PCE encounter number is displayed on\nvarious order status screens in the Visit Number(s).\n \nExample: Order/test status screen - Visit Number(s): show the PCE\nencounter numbers.\nTest Urgency Status Accession\n -Lab Order # 162690 Provider: The man\n Visit Number(s): 99999;\nWorkload background job.\n BLOOD \n CBC PROFILE ROUTINE Test Complete 12/02/1999@07:41 HE 1202 10\n -Lab Order # 162690 Provider: The man\n Visit Number(s): 99999;\n BLOOD SERUM\n MAGNESIUM ROUTINE Test Complete 12/02/1999@08:02 DA 1202 32\n CHEM 7 ROUTINE Test Complete 12/02/1999@08:02 DA 1202 32\n -Lab Order # 163491 Provider: The man\n Visit Number(s): 99999;\n BLOOD SERUM\n \n URIC ACID ROUTINE Test Complete 12/02/1999@14:37 DA 1202 234\n \nBy using the User's Visit Review [PXQ USER REVIEW] option User's Visit\nReview one can determine what CPT workload has been captured for a given\norder. This is an example of the option. The Visit Number(s) information\nis entered at the 'Enter VISIT (UNIQUE ID or '1239):' prompt. \n Select one of the following:\n \n P Patient List of Visits\n I Internal Entry Number of VISIT\n6. The LABORATORY SITE file (#69.9) locking logic is modified to correct\n \nSelect by (P)atient or (I)en: P// Internal Entry Number of VISIT\n \nEnter VISIT (UNIQUE ID or `1239): `99999\n 12-2-1999@06:57:38 PATIENT,SICK \nLAB DIV 623 OOS ID 108 29TRC-MUS\n \n Select one of the following:\n \n D Default (first field of each file/subfile)\n ROUTINE\nthe problem of not being able to edit the LABORATORY SITE file (#69) while\n A All fields in a file/subfile (except 'NULL')\n C Customized by User (Default plus added fields) \n \n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nTo customize your display use VA FileMan to add entries in file PCE\nCUSTOMIZE REPORT, with your NAME, FILE/SUBFILE#s, and FIELD#s that you\nwant to have included in the report.\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \nEnter '^^' to exit option\nthe LRNIGHTY background job is running.\nFormat of Print out: // All fields in a file/subfile (except 'NULL')\n \nDEVICE: HOME// TELNET Right Margin: 80// \n \n**************************************************************\n*** R E C O R D O F R E L A T E D E N T R I E S ***\n \n The Following is the VISIT file entry and\n ALL records pointing back to this entry.\n \nOption Changes\n VISIT RECORD --- #999999\n \n DATE/TIME --- DEC 02, 1999@06:57:38\n PATIENT --- PATIENT,SICK\n LOCATION --- LAB DIV 623 OOS ID 108\n----------------------------------------------------------------\n FILE = VISIT #9000010 RECORD #99999\n VISIT/ADMIT DATE&TIME = DEC 02, 1999@06:57:38\n DATE VISIT CREATED = DEC 02, 1999@07:28:51\n TYPE = VA\n \n PATIENT NAME = PATIENT,SICK\n LOC. OF ENCOUNTER = MUSKOGEE, OK\n SERVICE CATEGORY = DAILY HOSPITALIZATION \n DSS ID = LABORATORY\n DEPENDENT ENTRY COUNT = 3\n DELETE FLAG = \n PARENT VISIT LINK = \n DATE LAST MODIFIED = DEC 02, 1999@07:28:52\n CHECK OUT DATE&TIME = \n ELIGIBILITY = NSC, VA PENSION\n*7. Add tests to a given accession [LRADD TO ACC] option is modified to\n HOSPITAL LOCATION = LAB DIV 623 OOS ID 108\n CREATED BY USER = WORKER,HARD V\n OPTION USED TO CREATE = LRENTER\n PROTOCOL = \n OUTSIDE LOCATION = \n VISIT ID = 29TRC-MUS\n PATIENT STATUS IN/OUT = IN\n ENCOUNTER TYPE = ANCILLARY\n SERVICE CONNECTED = \n AGENT ORANGE EXPOSURE = \nactivate the PCE Workload API. Any test(s) added to an accession will now\n IONIZING RADIATION EXPOSURE = \n PERSIAN GULF EXPOSURE = \n MILITARY SEXUAL TRAUMA = \n COMMENTS = \n PACKAGE = PCE PATIENT CARE ENCOUNTER\n DATA SOURCE = LAB DATA\n \n-----------------------------------------------------------------\n FILE = OUTPATIENT ENCOUNTER #409.68 RECORD #999999\n DATE = DEC 02, 1999@06:57:38\nreceive PCE Workload credit.\n PATIENT = PATIENT,SICK\n CLINIC STOP CODE = LABORATORY\n LOCATION = LAB DIV 623 OOS ID 108\n VISIT FILE ENTRY = DEC 02, 1999@06:57:38\n CHECK OUT PROCESS COMPLETION = DEC 02, 1999@07:28\n ORIGINATING PROCESS TYPE = STOP CODE ADDITION\n APPOINTMENT TYPE = REGULAR\n MEDICAL CENTER DIVISION = MUSKOGEE VAMC\n STATUS = INPATIENT APPOINTMENT\n ELIGIBILITY OF ENCOUNTER = NSC, VA PENSION\n \n UNIQUE VISIT NUMBER = 29TRC-MUS\n EDITED LAST BY = WORKER,HARD V\n DATE/TIME LAST EDITED = DEC 02, 1999@07:28:52\n CREATED BY = WORKER,HARD V\n DATE/TIME CREATED = DEC 02, 1999@07:28:52\n COMPUTER GENERATED? = YES\n-----------------------------------------------------------------\n FILE = V PROVIDER #9000010.06 RECORD #99999\n PROVIDER = GIVER,CARE\n PATIENT NAME = PATIENT,SICK\n8. Order/test status [LROS] option is modified to correctly display\n VISIT = DEC 02, 1999@06:57:38\n PRIMARY/SECONDARY = PRIMARY\n PERSON CLASS = Physicians (M.D.)\n EDITED FLAG = EDITED\n AUDIT TRAIL = 24-A 5591;24-E 5591;\n PACKAGE = LAB SERVICE\n DATA SOURCE = LAB DATA\n-----------------------------------------------------------------\n FILE = V CPT #9000010.18 RECORD #99999\n CPT = 85025\ntest(s) added to an accession.\n PATIENT NAME = PATIENT,SICK\n VISIT = DEC 02, 1999@06:57:38\n PROVIDER NARRATIVE = AUTOMATED HEMOGRAM\n QUANTITY = 1\n ENCOUNTER PROVIDER = GIVER,CARE\n AUDIT TRAIL = 24-A 5591;\n PACKAGE = LAB SERVICE\n DATA SOURCE = LAB DATA\n-----------------------------------------------------------------\n The Following is the OUTPATIENT ENCOUNTER entry and\n \n \n most of the records pointing back to it.\n \n OUTPATIENT ENCOUNTER --- #99999\n-----------------------------------------------------------------\n \n FILE = V CPT #9000010.18 RECORD #99999\n CPT = 85025\n PATIENT NAME = PATIENT,SICK\n VISIT = DEC 02, 1999@06:57:38\n PROVIDER NARRATIVE = AUTOMATED HEMOGRAM\n9. Enter/verify data (auto instrument) [LRVR] option is enhanced to allow\n QUANTITY = 1\n ENCOUNTER PROVIDER = GIVER,CARE\n AUDIT TRAIL = 24-A 5591;\n PACKAGE = LAB SERVICE\n DATA SOURCE = LAB DATA\n-----------------------------------------------------------------\n FILE=TRANSMITTED OUTPATIENT ENCOUNTER #409.73 RECORD #999999\n NUMBER = 999999\n OUTPATIENT ENCOUNTER = DEC 02, 1999@06:57:38\n TRANSMISSION REQUIRED = YES\nusers to edit, add, or subtract atomic test(s) from the test list before\n TRANSMISSION EVENT = ADD\n DATE/TIME OF EVENT = DEC 02, 1999@07:28:52\n USER CAUSING EVENT = WORKER,HARD V\n PATIENT = PATIENT,SICK\n ENCOUNTER DATE = DEC 02, 1999 06:57:38\n HOSPITAL LOCATION = LAB DIV 623 OOS ID 108\n PATIENT SSN = 1010101010\n ENCOUNTER DIVISION = MUSKOGEE VAMC\n ENCOUNTER DIVISION (INTERNAL) = 1\n-----------------------------------------------------------------\nbeginning the verification of an atomic test(s) and to continue to the\n The Following is the SCHEDULING VISITS file.\n This is where Scheduling stores the CPT codes.\n \nTHERE ARE PROCEDURES IN PCE BUT NO RECORD IN SCHEDULING **\n \n===============================================\n \n ****END OF EXAMPLE****\n \n \nnext accession number if the current accession is not collected. This\n*Venipuncture Workload Capture:\n \n************************\nLABORATORY CURRENT PROCEDURAL TERMINOLOGY (CPT) CODES AND MODIFIERS PATCH\nLR*5.2*263 INSTALLATION AND IMPLEMENTATION GUIDE in PDF format is provided\nwith this patch. Please refer to this document for details and specific\ninstructions. The patch description does not include ALL implementation\nconsiderations or complete file setup instructions.\n************************\n \nenhancement applies to both verifying by accession number or UID\n1. *Patch LR*5.2*263 will automatically collects venipuncture workload\ndata identical to other types of collected workload data. Venipuncture\nworkload data will appear on workload reports broken down by standard\nreporting criteria.\n \n2. Originally, LMIP workload reporting did not include venipuncture as a\nbillable procedure; therefore, the software entered a manual style tally\nof totals for the institution by day. Now LMIP workload does allow\nvenipuncture workload. This patch automatically captures venipuncture by\ninstitution, by date, by WKLD CODE, and by event time and stores them in\n(Universal Identification).\nthe WKLD DATA (#64.1) file. Certain data elements are required when\nrecording workload. One of the required data elements is accession area.\nTherefore, some accession area must be utilized to satisfy the required\ndata field. This patch provides new fields that can be used to customize\ndata collection.\n \n3. The venipuncture workload ACTUALLY indicates that the laboratory\nobtained at least one specimen from the patient.\n \nNOTE: THE SPECIMEN OBTAINED MAY NOT BE A BLOOD SPECIMEN. WHAT THE DEFAULT\n \nCODES (venipuncture) INDICATES IS THAT THE LAB COLLECTED A SPECIMEN FOR\nTHIS PARTICULAR ORDER. ONLY 1 SPECIMEN COLLECTION WORKLOAD UNIT PER ORDER\nIS CAPTURED REGARDLESS OF THE NUMBER OF ACTUAL SPECIMENS COLLECTED FOR THE\nORDER.\n \n4. Specimen Collection workload codes of Venipuncture Travel Time\n[89341.0000] is the default code for Lab Collect (LC) and Immediate\nCollect (I). Specimen Collection WKLD CODE of Venipuncture Outpatient\n[89343.0000] is default code for Send Patient (SP). \n \n*10. Batch data entry [LRSTUF] option is modified to capture LMIP workload\n5. *Venipuncture workload is captured based on INSTITUTION field (#3) in\nthe HOSPITAL LOCATION file (#44) of the ordering location. If no\nINSTITUTION is defined, the default institution defined by MAILMAN will be\nused.\n* There is a new field exported with this patch. The DIVISION PARAMETERS\nfield (#618) is a multiple in the LABORATORY SITE file (#69.9). There are\ntwo fields in the DIVISION PARAMETERS field (#618) multiple that can be\nused to customize the venipuncture workload collection.\n - DIVISION PARAMETER field (#.01) points to the INSTITUTION file (#4).\nThis field will allow the LABORATORY SITE file (#69.9) to be\ncounts.\nmulti-divisional.\n - VENIPUNCTURE DEFAULT ACC AREA field (#618) points to the ACCESSION\nfile (#68).\n \n6. * The software will examine the ordering location for the INSTITUTION\nthat location is assigned. The software will look up in the LABORATORY\nSITE file (#69.9), DIVISION PARAMETERS subfile (#) to get the ACCESSION\narea to be used when storing venipuncture workload. The MAJ. SECT and the\nSUBSECTION fields in WKLD DATA (#64.1) file will be set to ACCESSION area\ndefined.\nDescription:\n \nNote: The default venipuncture ACCESSION area is HEMATOLOGY.\n LAB DIVISION is CLINICAL PATHOLOGY\n Date and Time is the SPECIMEN COLLECTION date/time.\n The LAB TEST is the first collected test in the order.\n \n7. * The Venipuncture workload capture assumes that there is an accession\narea that begins with the letters 'HEM'. If there is no accession area\nbeginning with the letters 'HEM', then venipuncture default accession area\nwill be the accession area having the internal entry number of 10 in the\nACCESSION file (#68).\n11. Results entry (batch) [LRMISTUF] is modified to capture LMIP workload\n \n8. ** This patch creates a new multiple in the LABORATORY SITE file\n(#69.9), DIVISION PARAMETERS field (#618). This new multiple will be used\nto allow in the future, each institution to have the opportunity to\ncompletely define separate laboratory parameter definitions. The first\nentry in this multiple is VENIPUNCTURE DEFAULT ACC AREA field (#618). This\nfield will allow each institution to define what accession area\nvenipuncture workload should be assigned. If this field is not defined\nthen the default Hematology accession area outlined above will be used.\n \ncounts.\n \nThis is a listing of captured venipuncture workload data.\nDATE: DEC 02, 1999\nWKLD CODE: +Venipuncture Outpatient UNIT WEIGHT: 1\nACCESSION WKLD CODE TIME: 12.5713 LAB TEST: GLUCOSE\n WEIGHT MULTIPLIER: 1 LAB DIVISION: CLINICAL PATHOLOGY\n MAJ. SECT.: SEND OUT SUBSECTION: SEND OUT\n ACC NO.: CH 1202 15 PATIENT: NOSE,LIMP\n ORIGINAL ACC DATE: DEC 02, 1999\n DATE ORDERED: DEC 02, 1999@12:57:13\n \n SPECIMEN NO.: 1 SPECIMEN: BLOOD\n REPORT ROUTING LOCATION: 2S PROVIDER: GINSBURG,RONNIE\n LOG IN PERSON: STALLING,FRANK LOCATION TYPE: WARD\n ORDERING LOCATION: 7 ATU URGENCY: ROUTINE\n VERIFY TECH.: STALLING,FRANK WORK AREA: SEND OUT\n12. The Bypass normal data entry [LRFAST] option is modified to accept the\nresponse of "YES" at the "Do you want to enter draw times?" prompt.\n \n13. The Accessioning tests ordered by ward order entry [LROE] option is\nmodified to accurately determine if the tasked ROLLOVER ACCESSION [LRTASK\nROLLOVER] option is actually running.\n\n\nPatch LR*5.2*218 VISTA BLOOD BANK SOFTWARE DEVICE PRODUCT LABELING\nhave been changed. A new code for Zebra ZPL II compatible printers has\n OPEN EXECUTE: W $C(2),"^PON^LH0,0",$C(3)\n CLOSE EXECUTE: S IONOFF=1\n DESCRIPTION: Zebra Stripe S-600 Thermal Printer\n\n NAME: P-ZEBRA S-Series 105SE LABEL PTR\n RIGHT MARGIN: 0\n PAGE LENGTH: 99999\n FORM FEED: $C(0)\n OPEN EXECUTE: W $C(2),"^PON^LH0,0",$C(3)\n CLOSE EXECUTE: S IONOFF=1\nbeen added. Use this code to designate Zebra printers. The label stock of\n DESCRIPTION: Zebra S-Series 105SE Thermal Printer\n \n NAME: P-ZEBRA A300 LABEL PTR\n RIGHT MARGIN: 0\n PAGE LENGTH: 99999\n FORM FEED: $C(0)\n OPEN EXECUTE: W $C(2),"^PON^LH0,0",$C(3)\n CLOSE EXECUTE: S IONOFF=1\n DESCRIPTION: Zebra A-300 Thermal Printer\n \n15/16x3 has been renamed 1x3 for clarity.\n 3. The following VISTA DEVICE file (#3.5) label setting should be/can be \n used as an example for ....\n \n NAME: LABLABEL $I: _LTA387:\n ASK DEVICE: NO ASK PARAMETERS: NO\n SIGN-ON/SYSTEM DEVICE: NO LOCATION OF TERMINAL: LABLABEL\n SUPPRESS FORM FEED AT CLOSE: YES *MARGIN WIDTH: 0\n *FORM FEED: $C(0) *PAGE LENGTH: 99999\n SUBTYPE: P-ZEBRA S500 LABEL PTR TYPE: TERMINAL\n LAT SERVER NODE: DSV38 LAT SERVER PORT: PORT_7\n \n VMS DEVICE TYPE: NOT SPOOLED LAT PORT SPEED: 96\n \n The device should be defined and setup in the operating system as\n a printer. The following communication parameters have been found\n to work well:\n baud rate: 9600\n stop bits: 1\n parity: none\n communication handshake: xon/xoff control\n \nAll of the above changes have been reviewed by the VISTA Blood Bank\n No special jumping or wiring should be required.\n \n It is important that initial configuration and media calibration\n be performed on the printer per the printer's user guide before\n attempting to print labels.\n \n 4. The field PRINTER TYPE (#.02) within the LABEL DEVICE multiple of\n the LABORATORY SITE file (#69.9) has been changed. A new code for\n Zebra ZPL II compatible printers has been added. Use this code to\n designate Zebra printers.\nDeveloper and found to have no impact on the VISTA BLOOD BANK SOFTWARE\n \n Note: Patch LR*5.2*161 introduced this field. This patch had code "2"\n represent INTERMEC 4100. In patch LR*5.2*218 this has been changed\n to represent INTERMEC 3000/4000 SERIES to reflect the fact that this\n software will also work with Intermec 3400/4100/4400 series printers.\n \n Example of setting up this printer in the laboratory software:\n \n \n Select VA FileMan Option: 1 Enter or Edit File Entries\ncontrol functions.\n \n INPUT TO WHAT FILE: LABORATORY SITE//\n EDIT WHICH FIELD: ALL// LABEL DEVICE (multiple)\n EDIT WHICH LABEL DEVICE SUB-FIELD: ALL//\n THEN EDIT FIELD:\n \n \n Select LABORATORY SITE SITE NAME: MILWAUKEE, WI 53295\n Select LABEL DEVICE: LABLABEL// LABLABEL LABLABEL _LTA387:\n ...OK? Yes// (Yes)\n \n \n LABEL DEVICE: LABLABEL//\n PRINTER TYPE: ZEBRA ZPL II COMPATIBLE// ?\n Enter the type of label printer attached to this device.\n Choose from:\n 0 OTHER\n 1 INTERMEC 3000/4000 SERIES\n 2 ZEBRA ZPL II COMPATIBLE\n PRINTER TYPE: ZEBRA ZPL II COMPATIBLE//\n LABEL STOCK: 1X2//\nPROBLEM: The patch will add support for label printing within the\n ALTERNATE LABEL ENTRY:\n ALTERNATE LABEL ROUTINE:\n DEFAULT ACCESSION AREA: CHEMISTRY\n \n 5. There is no downloading of a label format required for Zebra type\n printers. The label format is part of the label printing process.\n This is a change from Laboratory's previous experience with Intermec\n model printers which require a separate downloading of the label\n format prior to label printing.\n \nLaboratory software for Zebra Technologies Corporation thermal printers.\n 6. A new option Lab Zebra Label Utility [LR BAR ZEBRA UTILITY] is\n added by this patch. This option will be added to the menu option\n Lab liaison menu [LRLIAISON] by this KIDS install.\n \n NAME: LR BAR ZEBRA UTILITY MENU TEXT: Lab Zebra Label Utility\n TYPE: run routine CREATOR: 0\n PACKAGE: LAB SERVICE\n DESCRIPTION: This option is used to perform several configuration\n functions that relate to the Zebra label printers.\n \nSTATEMENT\nBlood Bank Caution Tag labels are not included in this support.\n It allows the user to:\n \n 1 Configuration Update\n 2 Print Configuration Label\n 3 Adjust Tear Off Position\n 4 Label Top Position\n 5 Set Darkness\n 6 Mode Protection (Stripe printers only)\n \n Some functions are applicable to specific models of Zebra\nThis software is written to utilize the functions and features of the\n printers. Based on the firmware version installed in a printer,\n the effect of these functions may vary. Parameters allowed by\n these functions may be different due to changes in firmware.\n Consult the ZPL II Programming Guide, specific model User's Guide\n and Firmware Release Notes for specific information.\n \n ROUTINE: EN^LRBARCFA\n UPPERCASE MENU TEXT: LAB ZEBRA LABEL UTILITY\n \n 7. It was reported to Lab Development subsequent to release of patch\nZebra Programming Language II - ZPL II(TM).\n LR*5.2*161 that depending on label stock and printer alignment,\n the 2nd (right side) 1x2 label on the 10 part label stock prints\n very close to the left margin when using Intermec 4000 series\n printers. The routine LRBARB has been changed to move the\n information over 15 dots to the right. This hopefully will provide\n enough of a buffer to allow for variation in label stock and printer\n calibration and still print legible labels. Site will need to download\n format 12 for this change to take affect. Use option Lab Bar Code\n Label Formatter [LR BAR CF] to perform this function.\n \n \n 8. NOIS: ATG-1298-31334 reported an undefined error when printing future\n collection labels on controls using option Print future collection\n labels [LRUFCL]. When printing future collection labels for the\n current day and the site has accessioned controls, the option would\n error because controls do not have a location entered in file\n LAB ORDER ENTRY (#69). This patch corrects this situation by not \n attempting to print labels for controls or orders with no location.\n \n 9. NOIS: BAY-0999-30794 reported that the option Print single future\n collection label [LRUFCLS] would display a misleading message when\nRISK ANALYSIS: Changes made by patch LR*5.2*218 have no effect on\n attempting to print labels for an order when one of the specimens on\n the order has no active tests. This can occur when all tests on a\n specimen have been cancelled. The message has been changed to\n indicate that only the specimen with no active tests will not be\n printed.\n\n10. NOIS: TAM-1299-32916 reported that when the laboratory order number\n went over 999,999 that the last digit of the order number was truncated\n on the label when printed on Intermec printers. The label formats for\n 1x2 and 10 part labels for Intermec and Zebra label printers have been\nBlood Bank software functionality, therefore RISK is none.\n adjusted to print the order number to 7 digits. The text "order #"\n which precedes the order number on the label has been standardized\n across label formats printed by Intermec and Zebra printers.\n \n The test label available for printing within the Laboratory software\n now prints a 7 digit order number.\n \n \n \n Associated NOIS\n \n --------------\n ATG-1298-31334\n BAY-0999-30794\n TAM-1299-32916\n \n Test Sites\n ----------\n Chicago HCS\n Lebanon VAMC\n Maryland HCS, Perry Point Division\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*218 does not\n Milwaukee VAMC\n North Chicago VAMC\n \n ----------------------------\n \n ROUTINE SUMMARY\n ---------------\n \n The following is a list of routines included in this patch. The second\n line of each routine now looks like:\nalter or modify any software design safeguards or safety critical elements\n \n <tab>;;5.2;LAB SERVICE;**[patch list]**; Sep 27, 1994\n \n CHECK^XTSUMBLD results\n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ------------\n LR218 N/A 4566190 **218**(Deleted by KIDS)\n LRBARA 6240751 3709747 **161,218**\n LRBARB 18545310 10237788 **161,218**\nfunctions.\n LRBARCF 4094580 3690809 **161,218**\n LRBARCFA N/A 7161568 **218**\n LRLABELA 2536685 1741393 **161,218**\n LRLABELB 6023279 5187746 **161,218**\n LRLABELD N/A 3621894 **218**\n LRLABELE N/A 6156659 **218**\n LRLABELG N/A 1534246 **218**\n LRLABLD 8089099 7185434 **65,161,218**\n LRLABLD0 9351158 9284158 **1,65,121,161,218**\n LRLABLDS 4835286 4940823 **161,218**\n \n \n LRLABLIO 5515879 4587336 **107,161,218**\n \n\n \n INSTALLATION INSTRUCTIONS\n -------------------------\n The install time for this patch is less than 10 minutes without menu\n rebuilding. Install time will be increased if KIDS performs menu\n rebuilding. Alerts will be generated and sent to local mail group LMI\n when the transport global is loaded, patch installation starts and\nPOTENTIAL IMPACT ON SITES: This patch contains changes to a file\n ends.\n \n This patch can be installed when Laboratory users are on the system.\n However the following conditions apply:\n \n - Accessioning/label printing should not be occurring.\n - Patch installation needs to be coordinated with the Laboratory\n Information Manager (LIM/ADPAC).\n \n NOTE: MailMan and KERNEL patches must be current on the target system to\nidentified in Veterans Health Administration (VHA) Directive 99-053,\n avoid problems loading and/or installing this patch.\n \n \n 1. If any of the above routines are mapped, disable mapping for them.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the transport global.\ngroup B listing. The changes have no effect in Blood Bank functionality\n \n 4. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 5. Use the 'Verify Checksum in Transport Global' option and verify that\n all routines have the correct checksums.\n \n 6. If you wish to preserve a copy of the routines exported in this patch\n prior to installation, you should use the 'Backup a Transport Global'\n option at this time. You may also compare the routine in your\nor medical device control functions. There is no adverse potential to\n production account to the routine in the patch by using the 'Compare\n a Transport Global to Current System' option. These options are\n both found under the 'Installation' menu.\n \n 7. Use the 'Install Package(s)' option under the 'Installation' menu\n and select the package 'LR*5.2*218'.\n \n When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES//", choose 'YES'\n \nsites.\n When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', choose 'NO'.\n \n 8. On a mapped system, rebuild your map set.\n \n 9. Routine LR218 will be deleted after successful patch installation\n by KIDS.\n \n \n *****************************************************************************\n \n Below is an example of the dialogue seen during the KIDS install:\n \nSelect Installation Option: 6 Install Package(s)\nSelect INSTALL NAME: LR*5.2*218 Loaded from Distribution 10/8/98@11:2\n6:30\n => LR*5.2*218\n \nThis Distribution was loaded on Oct 08, 1998@11:26:30 with header of\nLR*5.2*218\nIt consisted of the following Install(s):\n \nLR*5.2*218\n \n LR*5.2*218\nWill first run the Environment Check Routine, LR218\n \n \n --- Environment Check is Ok ---\n \nInstall Questions for LR*5.2*218\n \nVALIDATION REQUIREMENTS BY OPTION: There are no required validation\nIncoming Files:\n \n \n 69.9 LABORATORY SITE (Partial Definition)\nNote: You already have the 'LABORATORY SITE' File.\n\nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES//\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO \n \nscenarios to be completed by sites after installing this patch.\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TELNET VIRTUAL\n \n \n Install Started for LR*5.2*218 :\nFebruary 9, 2000\n \n Oct 08, 1998@11:30:08\n \n Installing Routines:\n Oct 08, 1998@11:30:08\n \n Running Pre-Install Routine: PRE^LR218\n \n *** Pre install started ***\n \n --- No actions required for pre install ---\n \n \n *** Pre install completed ***\n \n Installing Data Dictionaries:\n Oct 08, 1998@11:30:10\n \n Installing PACKAGE COMPONENTS:\n \n Installing OPTION\n Oct 08, 1998@11:30:11\n- Patch LR*5.2*218 will add support for label printing within the\n \n Running Post-Install Routine: POST^LR218\n \n *** Post install started ***\n \n --- No actions required for post install ---\n \n *** Post install completed ***\n \n Updating Routine file...\n Laboratory software for Zebra Technologies Corporation thermal printers.\n \n Updating KIDS files...\n \n LR*5.2*218 Installed.\n Oct 08, 1998@11:30:12.\n \n Install Message sent #103025\n \nStarting Menu Rebuild: Oct 08, 1998@11:30:12\n \n This software is written to utilize the functions and features of the\nCollecting primary menus in the New Person file...\n \n Primary menus found in the New Person file\n ------------------------------------------\n \nOPTION NAME MENU TEXT # OF LAST LAST\n USERS USED BUILT\n \nEVE Systems Manager Menu 34 10/08/98 10/07/98\nLRMENU Laboratory DHCP Menu 2 10/07/98 10/07/98\n Zebra Programming Language II - ZPL II(TM).\nLRWARDM Ward lab menu 1 02/14/89 10/07/98\n \n<****** menu list has been abbreviated for brevity ******>\n \nBuilding secondary menu trees....\n \nMenu Rebuild Complete: Oct 08, 1998@11:33:05\n \n \nComplete\n \n \n \n \nInstall Completed\n \n \n \n End of example install\n *****************************************************************************\n\n- It will adjust the label layout of the 2nd 1x2 label on the 10 part label\nPOST-INSTALLATION INSTRUCTIONS\n------------------------------\n\n1. If the site is using either the Intermec or Zebra brand printers,\neach printer used to print labels within the Laboratory package needs to be\ndefined within the Laboratory files. Use FileMan Enter/Edit option to\nedit file LABORATORY SITE (#69.9). An example follows:\n \nSelect VA FileMan Option: 1 Enter or Edit File Entries\n \n stock when printed on the Intermec 3000/4000 series printer\nINPUT TO WHAT FILE: LABORATORY SITE//\nEDIT WHICH FIELD: ALL// LABEL DEVICE (multiple)\n EDIT WHICH LABEL DEVICE SUB-FIELD: ALL//\nTHEN EDIT FIELD:\n \nSelect LABORATORY SITE SITE NAME: MILWAUKEE, WI 53295\nSelect LABEL DEVICE: IRM DEVELOP INTERMEC 4100//\n LABEL DEVICE: IRM DEVELOP INTERMEC 4100//\n PRINTER TYPE: INTERMEC 3000/4000 SERIES// ?\n Enter the type of label printer attached to this device.\n (see item #7 below).\n Choose from:\n 0 OTHER\n 1 INTERMEC 3000/4000 SERIES\n 2 ZEBRA ZPL II COMPATIBLE\n PRINTER TYPE: INTERMEC 3000/4000 SERIES//\n LABEL STOCK: 1X3// ?\n Select the type of label stock loaded in this device.\n Choose from:\n 0 OTHER\n 1 1X3\n \n \n 2 1X2\n 3 2.5X4 10 PART\n LABEL STOCK: 1X3//\n ALTERNATE LABEL ENTRY:\n ALTERNATE LABEL ROUTINE:\n DEFAULT ACCESSION AREA: CHEMISTRY//\nSelect LABEL DEVICE:\n \n2. If the site is using Intermec printers and 1x2 or 10 part label stock\n then the following formats need to be downloaded to each printer\n- It will correct problems reported in NOIS: ATG-1298-31334, BAY-0999-30794,\n as appropriate:\n 1x2 label - formats 3,4,5\n 10 part label - formats 12,13\n \n Use option Lab Bar Code Label Formatter [LR BAR CF] to perform this\n function.\n \n3. If the site will be using Zebra brand printers then review manufacturer's\n user guide for installation, setup and calibration instructions.\n Adjustments to some printer parameters can be performed via\n TAM-1299-32916 (see items #8, 9, 10 below).\n Lab Zebra Label Utility [LR BAR ZEBRA UTILITY] option. Review the\n option description for further information relating to the capabilities\n provided by this option.\n \n 1. This software has been specifically tested with the following models:\n Zebra Stripe S-600 printer\n Zebra Stripe S-500 printer\n Zebra Stripe S-300 printer\n Zebra A-Series 300 printer\n Zebra S-Series 105SE printer\nVISTA Laboratory Package patch LR*5.2*218 contains changes to software\n Intermec 4100 printer\n \n Specific site equipment was as follows:\n\n Chicago HCS: Zebra S-300 using 1x2 label stock\n\n Lebanon VAMC: Zebra S-500 using 1x2 label stock\n\n Maryland HCS-Perry Point Division: Zebra S-600 using 1x2 label stock\n \ncontrolled by VHA DIRECTIVE 99-053, titled VISTA BLOOD BANK SOFTWARE.\n Milwaukee VAMC: Zebra A300, S-500 and 105SE using 1x2 label stock\n Intermec 4100 using 1x2 label stock\n\n North Chicago VAMC: Zebra S-600 using 2.5x4 10 part label stock\n Intermec 4100 using 2.5x4 10 part label stock\n\n \n 2. The following VISTA TERMINAL TYPE file (#3.2) printer settings should \n be/can be used as examples for ....\n \nChanges include: The fields PRINTER TYPE (#.02) and LABEL STOCK (#.03)\n NAME: P-ZEBRA S300 LABEL PTR\n RIGHT MARGIN: 0\n PAGE LENGTH: 99999\n FORM FEED: $C(0)\n OPEN EXECUTE: W $C(2),"^PON^LH0,0",$C(3)\n CLOSE EXECUTE: S IONOFF=1\n DESCRIPTION: Zebra Stripe S-300 Thermal Printer\n \n NAME: P-ZEBRA S500 LABEL PTR\n RIGHT MARGIN: 0\nwithin the LABEL DEVICE multiple of the LABORATORY SITE file (#69.9)\n PAGE LENGTH: 99999\n FORM FEED: $C(0)\n OPEN EXECUTE: W $C(2),"^PON^LH0,0",$C(3)\n CLOSE EXECUTE: S IONOFF=1\n DESCRIPTION: Zebra Stripe S-500 Thermal Printer\n \n NAME: P-ZEBRA S600 LABEL PTR\n RIGHT MARGIN: 0\n PAGE LENGTH: 99999\n FORM FEED: $C(0)\n\n
\nThis is the entire Laboratory file, containing 41 Files.\nThe WKLD Code file and AUTO INSTRUMENT file have their own init and\nare not included in the LRINIT.\n If this is the first install of the laboratory package\nconsult the installation guide for more information.\n\n
\nIt is very important to install this patch prior to the end of\nwill correct this problem.\n \nSome sites have not been reporting all Issue From Stock transactions on\nAMIS due to the Delivery Date either being null, or a Delivery date\noutside the AMIS reporting period. To correct this problem, the Delivery\nDate is no longer asked and the routine will stuff in the current date.\n \nOnce this patch has been installed have Prosthetics use the List Open\nStock Issues option and make sure all transactions have a Delivery Date\nwith the date they are doing the data entry. This will assure that all\nthe quarter to assure that Prosthetics will report accurate\ntransactions are counted on AMIS.\n \nThis patch also addresses the problems from the following NOIS reports:\n \nLAS-0596-61654 \nSFC-0596-62183\nMAD-0596-42179\n \nChecksum Before After\nRMPROPN1 7720327 7297330\ninformation.\nRMPR29C 7821428 7921291\nRMPR6 20477861 20520152\nRMPR29A 17059538 17069195\nRMPRSTK 15195669 14968768\n \n INSTALLATION:\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package in this message onto your system.\n \n \n 2. Answer NO to the question: 'Shall I preserve what is on disk in a\nseparate back-up message ?'\n \n 3. The patch has now been loaded into a Transport global on your\nsystem. You now need to use KIDS to install the Transport global.\n \n 4. From the 'Installation' menu, use the option 'Verify Checksums 'in\nthe Transport Global' and verify that all routines have the correct\nchecksum.\n \nSites that have a Prosthetic Lab, AMIS currently will double count 2421's.\n 5. On the KIDS menu, under the 'Installation' menu, use the option\n'Install Package(s)'. Select the package 'RMPR*3.0*13' and proceed with\ninstallation.\n This patch corrects this problem.\n \nWhen the option 'List Open Stock Issues' is used, the new VISA Purchase\nCard transactions show on the list as well as Stock Issues. This patch\n\n
\nThis patch contains NEW functionality to interface the Prosthetics \nnumber series. Both Prosthetic and IFCAP purchase card orders will \nhave the same purchase order numbers.\n \nThis patch is an enormous time saver for Prosthetic users, by \neliminating the need for duplication of order input into both IFCAP \nand Prosthetics. This patch provides the Interface between IFCAP and \nProsthetics. \n \nThis patch also addresses the problems from the following NOIS \nreports:\nPurchase Card Module to IFCAP.\n \n NOIS\n---------------\n STX-0996-70100\n DAY-0896-41319\n DAY-0896-41131\n \n Mail Message:\n 22635364\n \n \nPatch Dependencies\n------------------\nThe following patches MUST BE INSTALLED prior to loading this patch:\n \nPRC*5*107\nRMPR*3*3\nRMPR*3*12\nRMPR*3*15\nRMPR*3*19\n \nThis new functionality will eliminate the need for Prosthetic \nInstallation Overview\n---------------------\n \n \nInstall Time\n------------\nThe estimated install time is 2 minutes or less.\n \n \nInstallation\nPurchasing Agents to enter both Prosthetic and IFCAP purchase card \n------------\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \noption l load the KIDS package in this message onto your system.\n \n2. The patch has now been loaded into a Transport global on your \nsystem. You now need to use KIDS to install the Transport global.\n \n3. From the 'Installation' menu, use the option 'Verify Checksums \n'in the Transport Global' and verify that all routines have the \norders. After this patch is installed, users will remain in the \ncorrect checksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option \n'Install Package(s)'. Select the package 'RMPR*3.0*20' and proceed \nwith installation.\n \nCHECK^XTSUMBLD results\n----------------------\nRMPR29P value = 8396439\nRMPR421 value = 4996627\nProsthetic options to create and cancel orders without going into the \nRMPR421A value = 13010718\nRMPR421B value = 5444806\nRMPR421C value = 6607288\nRMPR4C1 value = 8115231\nRMPR4C21 value = 6415903\nRMPR4LI value = 7506137\nRMPR4LOP value = 12607366\nRMPR4OPN value = 11453190\nRMPR4P22 value = 11642686\nRMPR4P24 value = 5567655\nIFCAP purchase card order options. The Prosthetic Purchase Card \nRMPR4UTL value = 6093300\nRMPRAINQ value = 8060339\nRMPRP55 value = 18639880\nRMPRPAT5 value = 8036386\nRMPRSE1 value = 15550927\n \norders will be assigned purchase order numbers using the IFCAP common \n\n
\nProsthetics software - Add/Change NPPD lines FY07\n\n
\n1. ERROR- <MAXNUMBER>EN1+1^RMPREXT\n \n2. Sending Gulf War Veteran status via national NPPD rollup\n\n
\n1. CAN+5^RMPR4M removing item from order\n5. Security Statement - Prosthetics Purchase Order\n \n2. Two entries in V PROVIDER file from Prosthetics Midnight PCE task\n \n3. Question on data in File 9000010 (Visit File) for field CREATED BY \n USER\n \n4. Error <SUBSCRIPT>DESP+19^RMPRN6\n \n\n
\n1. <UNDEFINED>MORE+3^RMPRFO6 when printing patient letter with \n continuation page.\n \n2. Remove option [Record 2237 Purchase to 2319].\n\n
\nScheduling Replacement Encapsulation for Prosthetics.\n\n
\n1. Status of original consult changes from closed to active when it is\n cloned and a Post Initial Action action occurs.\n \n2. Prosthetics ordering issue for multiple orders against suspense\n record.\n \n3. Prosthetics GUI Delayed Order Report problem.\n\n
\n1. Ship charges not removed during CPO when using '@' or '0.00'.\n \n2. L code grouping calculator problem when viewing screen 4 of 2319.\n \n3. 2319 not displaying pre patient merged 660 records.\n \n4. List Open Purchase Card transactions by Initiator report has POs\n cancelled in GUI.\n\n
\nThis patch will fix the problem of some vendors from \nCMS-0197-31032\nBIL-0197-30995\nCLE-0197-40968\nBEC-0197-20893\nATG-0197-30576\nMAD-0197-40460\n \nPatch Dependencies\n------------------\nThe following patches MUST BE INSTALLED prior to loading this patch:\nlooping. If a vendor does not have a contract, the prompt for \nRMPR*3*20\n \nInstall Time\n------------\nThe estimated install time is 2 minutes or less.\n \nInstallation\n------------\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \nContract Number will not be displayed.\noption l load the KIDS package in this message onto your system.\n \n2. The patch has now been loaded into a Transport global on your \nsystem. You now need to use KIDS to install the Transport global.\n \n3. From the 'Installation' menu, use the option 'Verify Checksums \n'in the Transport Global' and verify that all routines have the \ncorrect checksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option \n \n'Install Package(s)'. Select the package 'RMPR*3.0*22' and proceed \nwith installation.\n \nCHECK^XTSUMBLD results\n----------------------\nRMPR421A value = 13049745\n \nThis patch also addresses the problems from the following NOIS \nreports:\n \nNOIS\n---------------\n\n
\n1. No data available for clinics\n \n2. <SUBSCRIPT>CONT+5^RMPR29CA\n \n3. <UNDEFINED>UPD+2^RMPR29CA\n\n
\n1. Add notification to LIST OPEN PURCHASE CARD TRANSACTION report to\n identify "dangling" amendments. \n \n2. Purge Suspense records undefined error: EN1+5^RMPR8PG\n \n3. HOME OXYGEN PRESCRIPTION DATE in add/edit not defaulting\n\n
\n1. Error: $ZE= <UNDEFINED>PRT+2^RMPRP21\n \n2. RMPR INV DEACTIVATE - option does not honor case sensitivity\n \n3. Delete stock issue on an inactive HCPCS item\n \n4. Option Print OIF/OEF Items Issued problem from RMPR package \n \n5. Patient SSN security risk - SSN displays under CLAIM NUMBER on PO\n\n
\n1. <SUBSCRIPT>PRT+26^RMPRPRT1 error when print patient's 2319.\n \n2. Deleting stock boots user out of system <SUBSCRIPT>DIK+3^DIK\n \n3. <UNDEFINED>EN1+12^RMPRD1 \n\n
\n1. Home Oxygen Billing Transaction editing error:\n <UNDEFINED>COMMON+6^RMPOLM1\n\n
\n1. Duplicate encounters when editing\n \n2. EDIT INVENTORY ITEM - not allow edit of VENDOR\n \n3. Discontinue Prosthetic PCE's\n \n4. Eliminate rejected Prosthetic PCE's\n\n
\n1. OWL attaches wrong DD23 - roll/scroll item detail display of 2319\n \n2. OWL ERROR: <UNDEFINED>F+2^DIED\n \n3. Prosthetics software - Add/Change NPPD Lines FY08\n \n4. Prosthetics closed OWL/LAB Consult date discrepancy reported\n\n
\n1. <UNDEFINED>UPD+1^RMPR9CA Close GUI PO error\n \n2. <UNDEFINED>DIS+2^RMPRPAT2 Display/Print 2319\n \n3. <UNDEFINED>LINK+14^RMPRPCE1 Suspense Link Error\n\n
\n<UNDEFINED>MAIL+16^RMPR5HQ7 - during PIP monthly roll up\n\n
\n \n \n1. Prosthetics Home Oxygen software\n \n2. Purchase Card Number printed on invoice\n\n
\n \nIt is also in response to NOIS TAM-0197-31968\nThe variable RMPRTRN was being killed off too soon.\nThe KILL statement is moved after the I block, which may sometimes be\nexecuted and does use the variable to set a data node.\n \nTo install: Have all Prosthetic Lab users off the system. \n Use Kids to Load the Patch.\n Move the routine to all systems.\n \n \nThis patch is in response to NOIS MGY-0197-31093.\nIt updates the address for the National Footwear Center in New YorK\nfrom: 252 7th Avenue, Floor 2, New York, NY 10001 \nto : 210 Varick Street, Floor 10, New York, NY 10014\n \n \n\n
\n \nMULTIPLE FIXES TO THE PROSTHETICS GUI\n\n
\nMANDATORY PATIENT NOTIFICATIONS\n\n
\n1. <UNDEFINED>DT442+7^PRCFFUD1\n\n
\n1. HD311528 remove routines RMPRPCEA and RMPRPCEB\n \n2. HD321817 Remove names on Home Oxygen POs in IFCAP\n \n3. HD303222 no line tag called ELQQM in routine RMPRPIY6\n\n
\n1. Negative GROUPER COUNTER field in 669.9\n \n2. Prosthetics software - ED2\n \n3. NPPD lines not appearing for 5-Rental items \n\n
\n1. Remove field #9 from printed Prosthetics Patient Purchase Order\n \n2. Prosthetics - Change in NPPD line names\n \n3. FGH - still getting error <UNDEFINED>HDR+2^RMPRN63\n \n4. Security clause on Prosthetics Patient PO\n\n
\n1. Error in Suspense Processing when viewing 2319\n \n2. Calculation flag HCPCS item and shipping charge added together on \n display 2319\n\n
\n1. New Prosthetics line number: R99 B NONRESPONSE\n \n2. Cannot print home oxygen report\n \n3. Entire SSN appears on Home Oxygen letter\n\n
\n1. New NPPD (National Prosthetic Patient Database) Line updates needed\n to support the HCPCS (Healthcare Common Procedure Coding System) Item \n file (#661.1) national updates for NPPD reporting and PIP (Productivity\n Improvement Program) national rollup.\n\n
\nInstall Time\nload the KIDS package in this message onto your system.\n \n2. The patch has now been loaded into a Transport global on your system. You\nnow need to use KIDS to install the Transport global.\n \n3. From the 'Installation' menu, use the option 'Verify Checksums 'in the\nTransport Global' and verify that all routines have the correct checksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option 'Install\nPackage(s)'. Select the package 'RMPR*3.0*24' and proceed with installation.\n------------\n \nThe estimated install time is 2 minutes or less.\n \n \nInstallation\n------------\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option\n\n
\nProsthetics GUI Required date field does not transfer to Purchase Card \norder.\n\n
\n1. When using the "23 Display 2319" option, if a user decides to exit \n using the up caret (^) symbol at the Enter 10-2319 screen to VIEW\n prompt, they will receive a system error.\n \n2. When a user in the Prosthetics application views the Display/Print \n Display 2319 menu option, HCPCS items and shipping charges are not\n being displayed correctly.\n\n
\n1. Add new field #1.3 (VERSION DATE) to file #661.1 [PROSTHETIC HCPCS] to\n prints showing the patient social security number.\n facilitate synchronization of HCPCS (Healthcare Common Procedure \n Coding System) code update between VISTA Prosthetics GUI and an \n enterprise asset management system.\n \n2. Site received a subscript error in option Issue from Stock due to \n incomplete inventory item bar code scan.\n \n3. When reprinting Purchase Order on Vista a Patient Notification letter\n\n
\n1. Home Oxygen charges for patient do not total for all linked Fund \n Returned Delivery Verification Card and remove same options from\n Prosthetics Utilities Menu as the government contract for Letter \n Notification was cancelled. \n Control Points.\n \n2. The VistA National Prosthetic Patient Database (NPPD) reporting\n does not match the national NPPD rollup for Unique Social\n Security Number (SSN) totals between NEW item costs and USED\n inventory item costs.\n \n3. Delete Prosthetics options Manual Send Delivery Notification and \n\n
\n1. Excessive number of pages print for each letter when selecting\n 'print all' Home Oxygen letters.\n \n2. Prosthetics GUI display for 2319, screen 7 for HISA (Home \n Improvement Structural Alterations) displays no HISA information\n for known HISA order. \n\n
\n1. 2012 NPPD Line updates\n\n
\n1. Cannot link patient record to Suspense:\n3. Prosthetics GUI error when displaying Delayed Order Report (DOR)\n a. When select patients appearing on the GUI Delayed Order\n Report.\n \n b. After selecting patient, current issue item does not display.\n \n2. Report 'Print Item Usage By Location' fails to print due to a missing \n HCPCS item reference.\n \n\n
\n1. Unlinked patient 2319s not displaying in option 'Link Patient Record\n to Suspense'.\n\n
\nThis patch updates the Prosthetics Privacy Act Statements and fixes\nissues with Purchasing being unable to post Prosthetics Home Oxygen\ntransactions.\n\n
\n1. National HCPCS file updates are not handling multi line descriptions\n correctly.\n\n
\n This patch contains corrections to the following NOISs.\n routine RMPRPAT3, logical conditions were inserted to print either the\n shipping/delivery or total labor cost if the total cost field is null.\n \n NOIS LAS-0597-62425\n -------------------\n This patch corrects problems associated with NOIS LAS-0597-62425 (and\n others). If a user executes the menu Purchase Card Site Parameter and\n receives the following statement:\n \n Enter the IFCAP Site used with the Purchase Card Module\n \n The following site you select will be used on all your\n Purchase Card Transactions in IFCAP only.\n \n YOU ARE NOT AN AUTHORIZED FISCAL USER. CONTACT SITE MANAGER.\n \n This action will cause PRC("SITE") to be undefined.\n \n As a result, this would cause the error reported in the NOIS. However,\n when a valid FISCAL USER moves through the menu, the site parameter would\n be reset.\n NOIS SYR-0497-10562\n \n To resolve this problem, the code was changed to not allow a null value. \n \n \n NOIS NIN-0497-41607\n -------------------\n This patch corrects a problem with the COCP limitation reported in NOIS\n SYR-0497-10562. When the user executes the "Close Out Purchase" option\n and answer yes to the cost out transactions, the option responded with\n Dollar amount must be within contract authority guidelines. Changes were\n -------------------\n made to remove the $25000 and $2500 limitations.\n This patch corrects a printing problem reported in NOIS SYR-0497-10562.\n Under certain circumstances, when the user executes the "Display/Print\n Patient 2319" option, sorted by "Appliance Transactions" the total cost\n heading displayed more than one numeric value. This patch contains\n modifications that will display the total cost value only once. In\n\n\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\n1. Users are able to edit Inactive HCPCS items in Prosthetics.\n \n2. Purge process created for Prosthetics file #664 [PROSTHETICS 1358]\n\n
\nIn preparation for the VA's transition from IPv4 to IPv6 the PROSTHETICS\npackage will require a modification to make it IPv6 ready.\n\n
\n1. Home Oxygen Generate Letters option has site and prescription\n expiration date issues. \n \n2. Home Oxygen Billing and Home Oxygen Reporting has no check/flag for\n deceased patients. \n \n3. Insure work file is killed when running option 'LIST OPEN STOCK \n ISSUES'.\n\n
\nThis patch fixes multiple issues with the Prosthetics GUI \n \n4) The main menu form for Prosthetics does not set to \n allow resizing or minimization.\n \n5) Ability for two purchasing agents to access the same\n consult at the same time and order against it\n(graphical user interface) Suite.\n \n1) Incorrect display of "Station Number" on the OWL form\n \n2) Serial Number should allow 20 character and not\n be restricted to 15.\n \n3) The NUMBER OF BIDS is not being populated\n\n
\n1) Adding a new prescription to a Home Oxygen patient, will allow the\n user to associate an inactive HCPCS code.\n \n2) Remove all routines & option for Patient Notification Letter processing\n \n3) Home Oxygen 'New Patient' report gets <undefined> error\n \n4) Site is unable to edit MODEL#/CONTRACT# in option Edit 2319\n\n
\n1. Eye glass STAT consult not showing on Suspense List\n \n2. Add fields Lot, Model and Contract Number to Reconcile Close Out\n \n3. Site issue causing error in Suspense Processing\n \n4. Site was not getting diagnosis when using option RMPR VIEW 2319\n \n5. Reconciliation edit not working when used by two users at same time\n\n
\nWhen running the Delayed Order Report (DOR) in Prosthetics, the "Pt IEN"\nis not populated.\n\n
\nThis patch ensures that, when the user modifies the contract number in the\nRMPR OFFICIAL MENU|Purchasing|Edit 2319 option, the change is reflected \nin the RMPR4 RPC report.\n\n
\n \nRECONCILE/CLOSE OUT PURCHASE CARD TRANSACTION\nand located under the PURCHASING\n[RMPR PURCHASING MENU] option. The Reconcile/Close Out Purchase Card\nTransaction option allows you to perform IFCAP amendments or adjustment\nand reconciliation during the closing of prosthetic purchase orders.\nBefore this enhancement, users had to switch between both Prosthetics and\nIFCAP packages to complete these function.\nPATCH SUBJ: VISALEVEL II, RECONCILIATION\n \nPatch Description:\n \nIFCAP PATCH PRC*5*125 MUST BE INSTALLED BEFORE INSTALLING THIS PATCH.\n \nPatch RMPR*3.0*26 is an enhancement to the Close Out Purchase Card\nTransaction [RMPR4 CLOSE OUT] option. This option is now called\n\n
\nHome Oxygen billing process date failure has prevented users from viewing \nHome Oxygen items posted.\n\n
\nWhen jumping to Suspense Processing, station may be undefined. The option \nentry point was modified to check station and ensure it is defined.\n \nAssociated SDM Tickets:\n=======================\nR16621509FY17 - <UNDEFINED>RMPRPAT2+15^RMPRPAT2 *RMPR("STA")\nR16726784FY17 - <UNDEFINED>RMPRPAT2+15^RMPRPAT2 *RMPR("STA")\n\n\nThis distribution adds an option allowing Prosthetics end-users \nto select an IFCAP Purchase Request (form 2237) by its Obligation \nNumber and post the individual line items to individual patients' \nProsthetics 2319 records and link to existing patient prosthetics \nsuspense record.\n\n
\nThis patch will fix the subscript error issue in the EDIT 2319 [RMPR\n EDIT 2319] option. An error will occur when the option is used in two \n situations. There are two files that are looked at when the edit is being\n updated. If file PROSTHETICS 1358 (#664) does not contain the information\n it will have an error. If file RECORD OF PROS APPLIANCE/REPAIR (#660)\n does not have the referenced information it will have the error.\n\n
\nThis patch adds the variable RMPRSITIEN to obtain the INSTITUTION (#4) \nfile IEN for an entered station number. It will then store it correctly \nin the PROSTHETICS SUSPENSE (#668) file.\n\n
\nThis patch addresses 2 issues:\n1. The Lot Number entry is being put in the Description (#24) field in \nthe file RECORD OF PROS APP (#660).\n2. When a record in the file RECORD OF PROS APP (#660) does not have a \nsuspense date it receives a subscript error in the option View \nProsthetics Item Transactions [RMPR VIEW 2319 READ ONLY].\n\n
\nWhen an IFC Subscriber Protocol (GRMC IFC SUBSC) triggers an undefined\nerror is being received when a Prosthetics Inter-Facility Consult (IFC)\nis discontinued, because the Internal Entry Number (IEN) is\nnot defined. \n \nAn undefined error is being received when a Prosthetics Reconcile/Close \nOut Purchase Card Transaction [RMPR4 CLOSE OUT] is attempted, but the \nfile PROCUREMENT & ACCOUNTING TRANSACTIONS (#442) has been purged. \n\n
\nAssociated end user does not get the warning message "No open sequence\nnumber available for ### for transaction entry ###" when creating an \neyeglass order in VistA.\n\n
\nWhen a user edits a PROSTHETICS HCPCS using the option Add Inventory \nLOCATION or ITEMS [RMPR INV ADD] it will flip the field INVENTORY FLAG \n(#10) in file PROSTHETIC HCPCS (#661.1) to 'YES'.\n\n
\nThis patch fixes an issue when the field REMARKS (#8) of subfile HOME \nOXYGEN ITEM (#19.4) in file PROSTHETICS PATIENT (#665) contains less than \n3 characters and is being transferred to generate the billing in the \nmatching field REMARKS (#4) in file HOME OXYGEN TRANSACTIONS FILE \n(#665.72).\n\n
\nPatch RMPR*3.0*28 will export a new global RMPR(661.1, options [RMPR\nADD/EDIT HCPCS, RMPR NPPD HCPCS and RMPR HCPCS HISTORY],\nmodify input template [RMPRE2319], replaces all occurences of\nprompt 'Enter HCPCS' to 'Enter PSAS HCPCS',reverse display of records in\nall SUSPENSE MENU options. The patch will also\nexport a partial DD update for files 660, 664 and 664.1 and create a "G"\ncross referenced for file #660.\n\n
\n1. When using GIP inventory process, instead of PIP process, the stock\n issue record is missing the short description\n\n
\nPlease refer to patch description on FORUM for detailed instructions.\n\n
\n1. Suspense processing menu lock message when processing an item\n\n
\n1. Home Oxygen prescription expiration report not reflecting correct\n expiration date\n \n2. The allowable upper limit for the Suspense Purge Parameter needs\n to be increased. \n\n
\nPatch RMPR*3.0*207 was built to ensure that the latest expiration \ndate for a veteran's Home Oxygen prescriptions would show on the \nreport Prescription Expiration Dates. However, sites were allowed\nat one point to enter the date 01/01/2099 for an ongoing prescription \nexpiration date, but that process came to an end in 2016. However,\nsince those futuristic dates remain they are picked up as the most\ncurrent date on the Prescription Expiration Dates report and are not\nvalid.\n\n
\nThe patch addresses one (1) issue: \n \n1. Routine EN^RMPRFC4 is using the wrong API for looking up ICD10 codes.\n This is causing all Prosthetics IFC Consults to file an invalid value\n into PROSTHETIC SUSPENSE file (#668) ICD field (#1.6).\n\n
\nThe patch addresses one (1) issue: \n \n1. The Suspense Processing [RMPR SUSP MENU] option may show records \nout of reverse chronological sequence if the IEN numbers in a site's \nPROSTHETIC SUSPENSE file (#668) get disrupted and new records are created \nat lower IENs than old records.\n\n
\nThis patch addresses the following issue:\n \nINC27716753 - Due to an incorrect API call to retrieve ICD codes (fixed in\nRMPR*213), some records associated with the Form 2319 may contain the "-1"\nerror code in the SUSPENSE ICD field of the RECORD OF PROS APPLIANCE/ \nREPAIR file (#660).\n\n
\nThe patch addresses two (2) issues: \n \n2. The option "Purge Suspense Records" [RMPR PURGE SUS] does not give \n The user a chance to verify whether they want to proceed with the \n purge. They do not have an option to cancel out of the purge once \n the report is displayed, nor are they given an estimate of the date\n range that will be purged before they commit. As a result, sites \n are inadvertently running the purge or running it without \n understanding how much data they will lose. This is causing sites\n to unintentionally lose important patient data.\n \n1. When an end user attempts to reconcile the credit card charge to the\n purchase order using Reconcile/Close Out Purchase Card Transaction \n option [RMPR4 CLOSE OUT], the application allows the user to delete \n the last remaining billing item (original billing item) on the \n purchase. If after the delete, the end user times out or enters an \n "^" at Select ITEM, it leaves an incomplete record that cannot be \n canceled or edited through the menu.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nThis patch will correct string error, missing fields for shipping entries\nin file #660 and PSAS HCPCS prompt during the close-out of 1358.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nRoutine RMPRSTL was obmitted from Patch RMPR*3*13.\noption will load the KIDS package in this message onto your system.\n \n2. The patch has now been loaded into a Transport global on your\nsystem. You now need to use KIDS to install the Transport global.\n \n3. From the 'Installation' menu, use the option 'Verify Checksums 'in\nthe Transport Global' and verify that all routines have the correct\nchecksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option\nThis patch contains routine RMPRSTL.\n'Install Package(s)'. Select the package 'RMPR*3.0*14' and proceed with\ninstallation.\n \nIt is very important to install this patch prior to the end of\nthe quarter to assure that Prosthetics will report accurate information.\n \nINSTALLATION:\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n\n
\nThis is the new Prosthetic Inventory module and a modified lab module.\n\n
\nHOME OXYGEN PACKAGE\n\n
\nA patch for Prosthetics Inventory fixes.\n\n
\n \n \n \n \nChecksum After Install\nRMPR4P21 18707942\nRMPR4EPC 1452962 \n \n \nINSTALLATION:\n \n1. Reprint Option, PCR Reprint a Purchase Card Form has been \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option\nwill load the KIDS package in this message onto your system.\n \n 2. The patch has now been loaded into a Transport global on your system.\nYou now need to use KIDS to install the Transport global.\n \n 3. From the 'Installation' menu, use the option 'Verify Checksums 'in the\nTransport Global' and verify that all routines have the correct checksum.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the option 'Install\nmodified to allow a closed VISA transaction to be reprinted.\nPackage(s)'. Select the package 'RMPR*3.0*15' and proceed with installation.\n \n \n2. Purchasing Option, EDPC Edit Purchase Card Transaction has \nbeen modified to allow editing the Bank Authorization Number \nafter the VISA transaction has been closed.\n \n \n\n
\nThe HCPCS Coding Work Group and EP has just completed \nthis patch RMPR*3*12 was developed.\n COORDINATOR: LNAME,FNAME// <return>\n -----------\n Select AUTHORIZED SENDER: <return>\n --------\n ALLOW SELF ENROLLMENT?: n NO\n -\n REFERENCE COUNT: <return>\n --------\n LAST REFERENCED: <return>\n --------\n \n RESTRICTIONS: 0 UNRESTRICTED\n -\n Select MEMBER GROUP NAME: <return>\n --------\n Select REMOTE MEMBERS: <return>\n ---------\n Select DISTRIBUTION LIST: <return>\n --------\nThis information will also be used to capture data \nreported on AMIS, and will ultimately be part of an \nAMIS replacement system.\n \nThis patch brings in a new server option and server \nroutine. You will need to create a new Mail Group \ncalled RMPR SERVER, and assign the Chief of Prosthetics \nas a member. Members of this mail group will receive a \nthe final review of the HCPCS functionality.\nmessage that the server has been activated.\n \n \nPatch Dependencies\n------------------\nThe following patches MUST BE INSTALLED prior to loading this patch:\nRMPR*3*3\nRMPR*3*13\n \n \n \nInstallation Overview\n---------------------\nIf installed during the normal work day it is \nrecommended that the following menu options (File #19) \nand all of their descendants be disabled to prevent \npossible conflicts. Other DHCP users will not be affected.\n \nRMPR OFFICICAL\nRMPR CLERK\n \nThis patch will bring in new functionality consistent \nInstall Time\n------------\nThe estimated install time is 2 minutes or less.\n \nInstallation\n------------\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option will\nload the KIDS package in this message onto your system.\n \nwith private sector coding standards. This is also the \n2. The patch has now been loaded into a Transport global on your system. You\nnow need to use KIDS to install the Transport global.\n \n3. From the 'Installation' menu, use the option 'Verify Checksums 'in the\nTransport Global' and verify that all routines have the correct checksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option 'Install\nPackage(s)'. Select the package 'RMPR*3.0*12' and proceed with installation.\n \nCreat Mail Group\ncoding system used by MCCR for billing purposes and \n----------------\n Use VA FileMan to add the Mail Group:\n \n *Note: This Mail Group must have a real user in the MEMBER field.\n>D P^DI\n ------\n VA FileMan 21.0\n \n Select OPTION: ENTER OR EDIT FILE ENTRIES\n --------------------------\nwill be utilized by DSS. It is imperative that we use \n INPUT TO WHAT FILE: MAIL GROUP (XX entries)\n ----------\n EDIT WHICH FIELD: ALL// <return>\n --------\n \n Select MAIL GROUP NAME: RMPR SERVER\n -----------\n Are you adding 'RMPR SERVER' as a new MAIL GROUP (the XXX)? Y (Yes)\n\n MAIL GROUP COORDINATOR: <enter a coordinator>\na coding system that is consistent throughout the DVA \nSelect MEMBER: LNAME,FNAME <== Enter a real user here\n Are you adding 'LNAME,FNAME' as a new MEM (the X for this MAIL GROUP)?\n Y (Yes)\n -\n Select MEMBER: <return>\n --------\n DESCRIPTION: <return>\n --------\n 1> This Mail Group is used to alert Prosthetic Service Chiefs\n -----------------------------------------------------------\nsystem for accountability of information. This is why \n 2>that the National Data Extract Server has been activated, by who,\n -----------------------------------------------------------------\n 3>and for what dates.\n -------------------\n 4>\n EDIT Option: <return>\n TYPE: pu public\n --\n ORGANIZER: <enter a organizer>\n ------------------\n\n
\nPCE\n\n
\nWhen Prosthetics is using GIP, option Issue From Stock does not prompt\nThe following patch MUST BE INSTALLED prior to loading this patch;\n RMPR*3*12\n \nInstallation Overview\n---------------------\nIf installed during the normal work day it is\nrecommended that the following menu options (File #19)\nand all their descendants be disabled to prevent\npossible conflicts.. Other DHCP users will not be affected.\n \nfor HCPCS code. This patch will add the functionality to sites\nRMPR OFFICIAL\nRMPR CLERK\nInstall Time\n-------------\nThe estimated install time is 2 minutes or less.\n \n \nINSTALLATION:\n-------------\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\nusing GIP.\noption will load the KIDS package in this message onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\nsystem. You now need to use KIDS to install the Transport global.\n \n 3. From the 'Installation' menu, use the option 'Verify Checksums 'in\nthe Transport Global' and verify that the routine RMPRSTK has the correct\nchecksum.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the option\n \n'Install Package(s)'. Select the package 'RMPR*3.0*16' and proceed with\ninstallation.\nReference NOIS CLA-0996-21207.\n \n \nPatch Dependencies\n------------------\n\n
\n2002 HCPCS update\n\n
\nNPPD updates and View 2319 read only.\n\n
\nPATCH #72 - DBIA USAGE\n\n
\n2003 HCPCS UPDATE\n\n
\nDelay Order Report, 2319 button attached.\n\n
\nNois Fixes.\n\n
\nProsthetics Code Set Versioning.\n\n
\nCopy CPRS Consults.\n\n
\nThis has only one input template RMPRE2319 for file 660.\nThis will allow editing HCPCS in 2319 record.\n\n
\nENCAPSULATION OF IB. USE OF INSUR API INSIDE PROSTHETICS BILLINGS REPORT.\n\n
\nAllow consults to forward to a tracker only service and correct the \nproblem of overwriting the Initial Action Data when forwarding a consult.\n\n
\nSerial Number, Make and Model for recall.\n\n
\nAdd text to the PCE Interface Message and Remove SSN from the Patient \nCorrespondence and Patient Notification Letters.\n\n
\nCode Set Versionsing for ICD9. Replace all direct calls to ICD9 with API \nIDDX^ICDCODE.\n\n
\nCANCELING A CLONED CONSULT ISSUE\n\n
\nPatch Dependencies\nAll users may be on the system while this patch is loaded.\n \nInstall Time\n------------\nThe estimated install time is 2 minutes or less.\n \nInstallation\n------------\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option l\n------------------\nload the KIDS package in this message onto your system.\n \n2. The patch has now been loaded into a Transport global on your system. You\nnow need to use KIDS to install the Transport global.\n \n3. From the 'Installation' menu, use the option 'Verify Checksums 'in the\nTransport Global' and verify that all routines have the correct checksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option 'Install\nPackage(s)'. Select the package 'RMPR*3.0*18' and proceed with installation.\nThe following patches MUST BE INSTALLED prior to loading this patch:\n \n Verify Mail Group \n----------------\nPlease verify that mail group RMPR SERVER is on your system, and the Chief of\nProsthetics is a member.\nRMPR*3*12\nXM*DBA*104 \n \n \n Installation Overview\n ---------------------\n\n
\nPatch #61 - Barcoding and File Redesign.\n\n
\nPlease see FORUM for full patch description.\n\n
\nThis patch will address two issues;\n 1. Problem accessing the 2319 correspondence letter prompt.\n 2. The use of the % variable in 3 routines.\n\n
\nFix to the Prosthetics Reconciliation process to compare the correct \ndollar amounts so the program will not trigger an ammendment.\n\n
\nSYNTAX error during merge process due to Prosthetics package having null \nroutine node in Package File (9.4) due to incorrect KIDS build.\n\n
\nPROSTHETICS CLINICAL INDICATOR DATA CAPTURE BUILD\n\n
\nDescription:\nthen prompted for SPECIAL CATEGORY a forth item has been added,\nELIGIBILITY REFORM. Even though Eligibility Reform is suitable for\nboth Special Legislation and Eligibility Reform, you should select\nEligibility Reform so the transactions can be separated for trending\nanalysis.\n \nExample:\n TYPE OF TRANSACTION: INITIAL ISSUE//\n PATIENT CATEGORY: SC/OP// ?\n Enter the Patient Category for this issue.\n========================\n Choose from:\n 1 SC/OP\n 2 SC/IP\n 3 NSC/IP\n 4 NSC/OP\n PATIENT CATEGORY: SC/OP// 4 NSC/OP\n SPECIAL CATEGORY: ?\n Enter the patient's Special Category if applicable.\n Choose from:\n 1 SPECIAL LEGISLATION\nThis patch was developed in response to the Eligibility Refom\n 2 A&A\n 3 PHC\n 4 ELIGIBILITY REFORM\n SPECIAL CATEGORY: 4 ELIGIBILITY REFORM\n \n \n \n \n Patch Dependencies:\n =======================\nintroduced by PL-104-262.\n The following patches MUST BE INSTALLED prior to loading this patch:\n RMPR*3*3\n RMPR*3*12\n RMPR*3*15\n RMPR*3*16\n RMPR*3*18\n \n \n Patch Dependencies:\n =======================\n \n The following patches MUST BE INSTALLED prior to loading this patch:\n RMPR*3*3\n RMPR*3*12\n RMPR*3*15\n RMPR*3*16\n RMPR*3*18\n The estimated install time is 2 minutes or less.\n \n \n Installation\nThis patch will add the new public law as a choice when you add a\n ========================\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\nsystem. You need to use KIDS to install the Transport global.\n \n 3. From the 'Installation' menu, use the checksums 'in the\n Transport Global' and verify that all routines have the correct checksum.\ndisability code.\n \n \n 4. On the KIDS menu, under the 'Installation' menu, use the option\n 'Install Package(s)'. Select the package 'RMPR*3.0*19' and proceed with\n installation.\n \n \nRoutine Information:\n====================\n RMPR4LI value = 7635778\n \n RMPR4P21 value = 17560908\n RMPRED6 value = 24363847\n RMPRHIS value = 8052646\n RMPRHISD value = 7536482\n RMPRL9 value = 15221017\n RMPRLI value = 6867549\n RMPRP21 value = 18656811\n RMPRSTK value = 14899657\nYou will find when you select OPT/NSC under PATIENT CATEGORY, and\n\n
\nSUBSCRIPT ERROR/PCE ERROR MESSAGE\n\n
\nThis patch will address three issues:\n 1. The hard coded Default Barcode Printer Name\n 2. The P-ZEBRA printer subtype requirement\n 3. Items still being added to a inactive location\n\n
\n \n1. RMPR Clerk Menu not prompting for site\n2. Extra line feeds in Purchase Order ITEMS section after patch 90\n3. Oxygen letters: site name wrapping into patient's address\n\n
\n1. PIP roll-up does not match local Item Detail Report.\n \n2. Fix the ien for station number starting point in PIP Extract \n collection to begin at station ien 1 instead of 2.\n\n
\n1. Delete Field 19 (bogus entry) in File #660 which comflicts with\n field 4.1 of same file, both using node 0, piece 22.\n \n2. Prevent dual entries in File #661.6 and #661.7 from having time \n stamp one second apart for "return-in" when piece 6 of Suspense\n file #661.63) is null.\n\n
\n1. When using the option 'RMPR WH DISPLAY' and the DELIVER TO field is \n 'other' print "Deliver To Attention" on 2nd line.\n \n2. When using the option RECONCILE/CLOSE OUT PURCHASE C RMPR4 CLOSE \n OUT [Reconcile/Close Out Purchase Card Transaction] Shipment Date \n will occur for date query for each item on the Purchase Card.\n \n3. Prosthetics location prompt is case sensitive when using option [UP \n Reconcile Item Balance].\n\n
\nProsthetics PFSS\n\n
\nPROSTHETICS GUI PURCHASING NOT ADHERING TO VISTA FM DATA DICTIONARY FIELD\nLENGTHS FOR FILES #664/660.\n\n
\nThis is a fix for patch RMPR*3*19, and should only be loaded after patch \nThe following patches MUST BE INSTALLED prior to loading this patch:\nRMPR*3*19\n \nInstallation Overview\n ---------------------\nNo Prosthetics users should be on the system.\n \nInstall Time\n------------\nThe estimated install time is 2 minutes or less.\nRMPR*3*19.\n \n \nInstallation\n------------\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option l\nload the KIDS package in this message onto your system.\n \n2. The patch has now been loaded into a Transport global on your system. You\nnow need to use KIDS to install the Transport global.\n \n \n3. From the 'Installation' menu, use the option 'Verify Checksums 'in the\nTransport Global' and verify that all routines have the correct checksum.\n \n4. On the KIDS menu, under the 'Installation' menu, use the option 'Install\nPackage(s)'. Select the package 'RMPR*3.0*21' and proceed with installation.\n \n \nRMPRSTK value = 14878864\nThis patch will remove the offending DIC("W") from routine RMPRSTK.\n \n \n \nPatch Dependencies\n------------------\n\n\n1. Delete issue from stock error <SUBSCRIPT>DEL68^RMPRPCED\n \n2. Problem with option, Edit/Delte Issue from Stock \n\n
\n1. Up-arrow out of option [RMPR INQ SUSPENSE] and going to option [RMPR \n SUSP] will use the same patient from the initial inquiry, instead of\n prompting for new patient name.\n \n2. Consult cloning carries over inactive ICD9 diagnosis codes.\n \n3. Bad entries (null) in the VISIT File (9000010) when RMPR PCE \n BACKGROUND job running. \n\n
\n1. Type of Transaction data missing in Extract.\n \n2. HOME/O2 Suspense Issue - PROSTHETICS PATIENT RECORDS NOT LINKED\n TO SUSPENSE.\n\n
\n1. UNDEF ITM+9^RMPR29 - variable rmtype NULL\n \n2. Institution IEN appears instead of station number on PSAS HCPCS HISTORY\n and Nightly PCE Background mail message\n \n3. Inventory does not always update correctly with quantity issued \n\n
\nProsthetics midnight processing of issues to PCE causing invalid data \nstructures in file #900010,VISIT \n a. Subscript error in Austin transmission <SUBSCRIPT>SITE+10^VASITE\n b. File entry points to another patient\n c. AMBCARE data into Austin\n\n
\n1. 2421 FORM filing DELIVER TO and DELIVER TO ATTENTION in files 660 and \n 664 incorrectly.\n \n2. Full SSNs still visible in regular 2421\n \n3. RMPRPFC missing tag 'EN' in XDRMERG0 process\n\n
\nFollow-up patch to GUI Purchasing to put the Vista Option out of order.\n\n
\n1. Issue with P.O. continuation page\n2. Prosthetics Inventory message for ROP levels ignores partially filled\n orders as outstanding.\n3a. Inventory Order Report does not acknowledge partially filled orders.\n3b. Partially filled orders cannot be later updated with receipts that\n may be received.\n\n
\nThe DHCP Prosthetic package automates many functions for Prosthetics. The\n Purchasing Module\n \nPurchasing interfaces with IFCAP into the IFCAP 1358 module. Forms \nprinted include the Authorization Invoice (VAF 10-2421), and Authority to\nExceed Amount on the Service Card (FL 10-55). For tracking transactions\nassociated with purchasing, Prosthetics will accommodate the Prosthetic\nService Card Invoice (VAF 10-2520), the Prescription and Authorization for\nEyeglasses (VAF 10-2914), No-Form, Pickup/Delivery Charges, Request for\nEstimate (FL10-90), and Patient Notification Letter.\n \nrecord of Prosthetics Service (VA Form 10-2319) and the appropriate\n \n Electronic 10-2319 Module\n \nRecord of Prosthetics Services is fully incorporated into DHCP displayed in\nmultiple terminal screens. Appliances and services issued are\nautomatically recorded to the electronic VAF 10-2319 when purchases are\nobligated or issued from stock. In addition, PSC Card, Clothing\nAllowance, Auto Adaptive Equipment, Patient Correspondence, and other\npatient data is recorded and displayed within the Electronic VAF 10-2319\nModule. This is the module that provides the basis for all AMIS reports.\nVAF 1358 obligation, are updated at the time of purchase (entry into the\n \n Entitlement Records Module\n \nInformation collected by Medical Administration Service (MAS) to determine\neligibility of benefits to the veteran is displayed in this module.\nPatient data includes name, social security number, date of birth,\naddress, remarks, temporary address, phone, sex, next of kin, military\nservice, eligibility status, verification of eligibility, disability\nratings, diagnostic codes, admission date, discharge date, type of\ndischarge, clinic enrollment, and pending appointments.\ncomputer) of the item or service provided to the veteran. This update is\n \n AMIS Module\n \nThis module calculates the new and repair work sheets based on the infor-\nmation collected in the electronic 10-2319 file.\nThis module also automatically generates Genric Code sheets that will be\nsaved for editing and transmission to Austin.\n \n Inventory Module\n \naccomplished through direct links to IFCAP and the electronic patient VAF\nInventory is linked to the Generic Inventory Package. Each station has the\noption to activate GIP.\n \n \n Correspondence Module\n \nLetters sent to patients are generated from this module. Denial letters\nare counted on AMIS automatically when end-of-quarter AMIS reports are\nrun.\n \n10-2319. Purchasing is simplified by entering the information only once\n \n Scheduled Meetings and Home/Liaison Visits Module\n \nAppointment information for Prosthetics Clinics can be pulled over onto\nthe Prosthetics VAF 10-2527 to be printed as Appointment Roster and Clinic\nAction Sheets.\n \nHome/Liaison visits can also be entered and printed in this module. All\nAppointment Visits and Home/Liaison Visits will be calculated on AMIS at\nthe end of the quarter.\ninto the computer and letting it update your 1358 account balances and the\n \n Prosthetic Lab Module\n \nThe Prosthetic Lab module automates VA Form 10-2529-3, Request and Receipt\nfor Prosthetic Appliances or Services, which is used to maintain a\nconsolidated record of prosthetic services furnished to eligible veterans.\nThis includes activities at Orthotic Laboratories, Restoration\nLaboratories, Shoe Last Clinics, Wheelchair Repair Shops, National Foot\nCenters, and the Denver Distribution Center.\npatient VAF 10-2319.\n \n\n
\nDelete obsolete Incident Reporting files. Files in 742 file number range\nnow being used.\n\n
\n This patch addresses 2 issues:\na list of existing open cases by 'Case Number', 'Date of Incident' or \n'Patient'.\n \n1. A subscript error appears when scheduled auto email options are \nrun and entries in the QA INCIDENT REPORT (#742.4) file with a LOCAL CASE \nSTATUS (#.09) of "CLOSED", "DELETED, or "QUICK" have no value for the \nINCIDENT (#.02). \n \n2. A subscript error occurs when accessing the 'Full Incident Edit' [QAN \nINCIDENT FOLLOW-UP] option and then using a question mark '?' to view a \n\n
\nThis patch marks MENU options "Disabled-USE Joint Patient Safety \nReporting-JPSR" as requested by the VHANCPS JPSR TEAM.\n\n
\nDECOMMISSION INCIDENT REPORTING PACKAGE - REMOVE ALL FILES, ROUTINES, \nTEMPLATES, ETC\n\n
\nPROBLEM ADDING SECOND PATIENT\n\n
\nIncident reports not printing.\n\n
\nPatient ID fix\n\n
\nThe Clinical Monitoring System allows the users to create their own\nmonitors from a list of pre-defined conditions. The monitors then run\nnightly, scanning DHCP data for patients who meet the conditions of the\nmonitor. The user may select data elements from a pre-defined list to be\ncaptured when a patient falls out for a given monitor. Programmers may\nadd new data elements and conditions to the system. Users can design and\nprint ad hoc reports from the fall out data.\n\n
\nThis patch corrects the gathering of data for the processing of the \nOS-109 Death screen.\n\n
\nPatch QAO*3*9 addresses 3 issues:\n \n 1. QAOS 107 screen requires VDL documentation change (MAJOR \n surgery)\n 2. QAOS 101.1 screen not reporting unscheduled 10 day re-\n admissions when scheduled admission occurs on same day\n 3. QAOS 109 screen reporting duplicate death entries, due to\n time of death change\n\n
\nPatch QAO*3.0*10 updates the Occurrence Screen 'Return to OR in same \nadmission' (Screen 107) to work with recent Surgery enhancements.\n\n
\nThe package addresses the Occurrence Screen circular by automating the\ncollection of selected occurrence screens. The remaining screens that\nare not auto enrolled may be entered manually. Provision has been made\nfor identifying practitioner, system, and equipment related problems\nwith patient risk events.\n\n
\nThis patch changes ^RMPFET10 so that RMPFSTAP is only set if not defined.\n\n
\nThis patch adds a .E to a patern match used in the server option that\nreads in file updates.\n\n
\nThis patch gets the patient sensitivity information and sends it with the\nROES order.\n\n
\nPROBLEM WITH REMOVING AN ORDER FROM A TRANSMISSION BATCH AND RE-APPROVING\n\n
\nThis patch fixes problems with screen displays and printouts.\n\n
\nThis patch addresses three issues.\nAPI's will be incorporated into the routines. These changes will fix the\nerrors some sites reported when resequencing the Postmaster's inbox.\n3. Finally, the print request is ignored when a user enters a lowercase\n"p" when queueing the "List Orders by Patient or Status" Report. This has\nbeen fixed so the user may use either case.\n \nROES V2.0 patches 1,2,7,8 and 15 are required to be installed prior to\nthis patch. Since RMPF*2.0*1 was not a KIDS Build, KIDS will not look for\nit during the installation process.\n1. When a facility name is changed in the Institution File (^DIC(4)),\nROES users have a problem bringing up their existing ROES orders because\nROES uses the facility name as an identifier. This patch will change the\nfacility lookup routines to look at the facility number instead of the\nname. This becomes a major issue with the release of the Institution Gold\nFile which will standardize facility names across the VA.\n2. Secondly, this patch will fix some MailMan message addressing\nproblems. Sections of obsolete code will be removed and some new MailMan\n\n
\nThis patch addresses 2 issues regarding the ROES 2.0 package:\n o The ability to print the report has been added for partial\n screen displays.\n \n o The error occurring when print to a slave printer has been\n corrected. This was a problem in the code not returning back\n to the proper line tag.\n \n2. Enhancements for Bundled Pricing\n \n o 2nd year warrenty is the only extra component available on new\n \n Custom Hearing Aid Orders. This patch will add a new field,\n "AVAILABLE W/BUNDLED PRICING", to the 791811.2 file. This\n field will be the 4th piece of the zero node. This patch\n will set this field for 2nd year warranty to "yes", and all\n other extra components will be set to "no", or left blank.\n \n o This patch will add the field "AVAIL WITH EXTRA COMP ORDER"\n field in 791811.2 file. This field will be the 5th piece\n of the zero node. The only extra component that is not\n available after the initial Custom Hearing Aid Purchase is\n1. DAY-0201-40031 <ENDOFILE>READ+1^RMPFDE Error\n the 2nd year warranty. This field for the 2nd year warranty\n will be set to 1, for "NO".\n \n o The Product file, and Component file will be updated with the\n new contract items.\n \n o The end of file error has been corrected. This was happening\n because of the extra print that was printing on the bottom of\n the report. This should have been printing on the screen.\n This text has been removed from the report.\n \n\n
\nThis patch will fix a looping error with was transmitted with patch\nRMPF*2*17. When processing elgibility determinations, if the use would\nselect an order and process, they are returned to the eligibility screen\nand stuck in a loop. This has been corrected, a kill was added at the\nstart of the routine.\n\n
\nThis patch is for the addition of a new vendor for the Remote Order\nEntry Contract that went into place on July 1st. It will add new\nentries into the REMOTE INVENTORY PRODUCT (791811) and to the HEARING\nAID COMPONENTS (791811.2) files. This contract addition starts on\nSeptember 1st, 2001. This patch must be installed between COB August\n31st, 2001 and the morning of September 2nd, 2001.\n\n
\nThis patch is for the inactivation of Custom Hearing Aids that are\nunder the old contract. It will inactivate them, and remove all the\ncomponents. It will also disable the ability to do adjustments on\nprevious CHA orders under the old contract.\n\n
\nThis patch includes the new hearing aid contract items that can be ordered\nthrough ROES. The new contract period begins 2-1-98.\n\n
\nThis patch ensures all dates are Y2K compliant and corrects formatting of\nreports and displays for Y2K compliant dates.\n\n
\nPATCH TO FIX A PROBLEM WITH THE DISPLAY A BATCH OPTION\n\n
\nThis patch fixes a typo that makes required fields mandatory and changes\nthe order code in the Component File to be a required field.\n\n
\nThis patch addresses several issues that have come up at VAMC stations\n calculated ROES eligibility of SC or COM.\n1. RMPFDE2 - This routine was modified to allow Prosthetics and\n Sensory Aids Service(PSAS) users to exit the 'Display ROES 3\n Eligibility Requests[RMPFDE2]' option by entering '^' as well as the\n <Q>uit. The print of the eligibility request list to a slave printer\n was not working and has now been fixed.\n \n2. RMPFDE3 - 'Eligibility' was added to the VistA message text.\n Catastrophically disabled veterans in Priority Group 4 have\n been added to the selectable eligibilities.\n \n- The "Date of Death" was not being transmitted consistently.\n3. RMPFRPC0 - In the original release priority groups 1 and 2 were\n omitted from the message transmission because the priority group\n was not obtained before the determination of SC or COM eligibility.\n This oversight has been corrected. Also, in the pop-up message\n from PSAS, the eligibility request date, the requesting user and the\n date action was taken were added.\n \n4. RMPFRPC1 - A section was added to remove special characters\n (@#%?&/\\) from the values that are used in the URL. Also, the\n failure of the 'Date of Death' to be transmitted to the DDC has\n- The inability to exit the "Display ROES3 Eligibility Requests[RMPFDE2]"\n been corrected.\n \n5. The ROES 3 CPRS Tools option executable(ROES3.exe) was modified\n to:\n -Correct the spelling of 'priority'.\n -The title of the selection box was changed to 'You must select a\n Proposed Eligibility', and a selection was made mandatory.\n -A splash screen was added to the executable to help alleviate the\n problem of the application not getting focus in front of the CPRS\n screens. Circumstances may still exist where the CPRS screen has\n option by entering a circumflex(^).\n priority. In those situations the user can <Alt><Tab> to view the\n Audiogram screen.\n -The portion of the module that was used by developers to lookup a\n patient was removed. That section was not meant to be used by\n field stations.\n \nROUTINE SUMMARY:\n===============\n \nThe following routines are included with this patch. The second line\n- The "Display ROES3 Eligibility Requests[RMPFDE2]" option did not allow\nof these routines will look like:\n \n ;;3.0;REMOTE ORDER/ENTRY SYSTEM;**1**;11/1/02\n \nCHECK^XTSUMBLD results:\n \n Routine Name Before Patch After Patch Patch List\n RMPFDE2 4775274 4811678 1\n RMPFDE3 6656730 7069797 1\n RMPFRPC0 14317184 13128624 1\n printing to a slave device.\n RMPFRPC1 4846679 5112865 1\n \nSOFTWARE RETRIEVAL\n==================\n \nThis patch will be distributed in a PackMan message through the\nNational Patch Module. The patch zip file containing the ROES3.exe file\ncan be retrieved from the following FTP address:\n \n download.vista.domain.ext\n- The selection of a proposed eligibility is now mandatory before the\n \nThis transmits the files from the first available FTP server. Sites may\nalso elect to retrieve software directly from a specific server as\nfollows:\n \nOI FIELD OFFICE FTP ADDRESS DIRECTORY\n \nAlbany ftp.fo-albany.domain.ext anonymous.software\nHines ftp.fo-hines.domain.ext anonymous.software\nSalt Lake City ftp.fo-slc.domain.ext anonymous.software\n request for determination will be submitted.\n \n \nFILE NAME DESCRIPTION/TITLE RETRIEVAL FORMAT\n \nRMPF3_P1.ZIP[1.33 MB] ROES3 CPRS Tools Executable BINARY\n containing ROES3.exe\n \n \nINSTALLATION INSTRUCTIONS:\n=========================\n- The eligibility request date, the requesting user and the date the\n \nROES users should be off the system while these routines are being\ninstalled. This patch should be installed during non-peak hours to\nminimize disruption. Installation will take approximately 5 minutes\nor more, depending on the CPRS Tools menu structure at your site.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. Answer\n YES to the prompt 'Want to Continue with Load? YES//'. This\n will load the KIDS package onto your system.\n \n request was acted on were added to the popup message.\n 2. Review your mapped set. If the routines listed in the ROUTINE\n SUMMARY section are mapped, they should be removed from the mapped\n set at this time.\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n \n 4. From this menu, you may elect to use the following options (when\n prompted for INSTALL NAME, enter RMPF*3.0*1):\n a. Backup a Transport Global - this option will create a backup\nas a result of the release of the ROES 3.0 package. All issues\n- The removal of the ability to do a patient lookup. The application\n message of any routines exported with the patch.\n b. Compare Transport Global to Current System - this option will\n allow you to view all changes to routines that will be made when\n the patch is installed.\n c. Verify Checksums in Transport Global - this option will allow you\n to ensure the integrity of the routines that are in the Transport\n Global.\n \n 5. Use the Install Package(s) option and select the package RMPF*3.0*1.\n \n should be run from CPRS Tools where the patient is already known.\n 6. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n YES//", respond "NO."\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond "YES". When prompted to select the\n options you would like to place out of order, enter the following:\n Display ROES3 Eligibility Requests RMPFDE2\n ROES3 OPTION ACCESS RMPF ROES3\n \n 8. When prompted 'Delay Install (Minutes): (0-60): 0//; respond '0.'\n \n \n 9. If routines were unmapped as part of step 2, they should be returned\n to the mapped set once the installation is complete.\n \n10. Retrieve the file rmpf3_p1.zip and extract file ROES3.exe.\n ROES3DeskTop.exe is not included in this patch because it is\n unchanged from the initial release.\n \n11. Copy the ROES3.exe file over all existing copies of ROES3.exe\n currently used by any staff. DO NOT copy it over any existing\nIn addition, the Audiology and Speech Pathology Service(ASPS) National\n ROES3DeskTop.exe applications. The command line option from\n CPRS Tools should continue to work as intended, without further\n modification.\nProgram Office requested that:\n- PG4 be added as a selectable eligibility. This includes veterans who\n have a Catastrophic Disability and are in Priority Group 4.\n- The text 'Veterans receiving benefits under 38 U.S.C. 1151 (benefits for\n individuals disabled by treatment or vocational rehabilitation)' be\n added to the help text for category EP3.\naddressed in this patch are related to the ROES3.exe application that\n \n \nFunctional Change\n=================\nThe Black Hills Health Care System reported a problem with the ROES3.exe\napplication causing excessive CPU usage on the desktop systems. The\nproblem was isolated to the part of the application that waited for\nInternet Explorer to exit and then automatically pulled information from\nthe clipboard and formatted it as text for CPRS Notes. This\nfunctionality is removed by this patch. By removing this 'listener', the\nruns from the CPRS Tools menu, as opposed to the ROES3DeskTop.exe\nuser will no longer be able to paste the 'formatted' order information\ninto a note in CPRS. Users will continue to have the ability to highlight\nthe order information and copy and paste the unformatted information. The\nDDC is looking into more efficient ways to restore this functionality in a\nfuture enhancement if it is still desired by the user community.\n \nNOIS references addressed in this patch\n=======================================\n \nMAC-0104-61099\napplication.\nproblem:\nWhen a '#' sign was returned by the ADD^VADPT call in the patient's phone\nnumber, it created a break in the URL that was used in establishing a\nbrowser session to the ROES 3.0 web application from CPRS Tools. This\nusually showed up as an eligibility error at the DDC.\n \nresolution:\nRoutine RMPFRPC1 was modified to screen out any special characters from\nthe values used by the URL in ROES3.exe. The executable also has an added\nfunction that verifies the removal of those characters.\n Issues addressed in this patch are:\n \nSBY-0404-30089\nproblem:\nWhen the user attempted to print the ROES 3 Eligibility Request list to\na slave printer, it produced an error at LIST^RMPFDE2 and didn't print.\n \nresolution:\nWhen the print routine was updated, the slave printer part was overlooked.\nThis problem has been fixed in routine RMPFDE2.\n \n- A disruption of the parameters passed to the Denver Distribution\nWRJ-0104-10319 and MAC-0304-61626\nproblem:\nROES3 message boxes or the application itself were coming up behind the\nCPRS screens.\n \nresolution:\nA splash screen was added to the ROES3.exe application and it will give\nfocus to the ROES 3.0 application in most instances. Situations may\nexist where other applications have priority.\n \n Center(DDC) if the patient's phone number contained a '#' sign.\nE3R references addressed in this patch\n======================================\nNone.\n \nTest Sites\n==========\nBlack Hills ALPHA/ISM (NT)\nMountain Home ALPHA/DSM\nNew York VMS/CACHE\nSalisbury ALPHA/DSM\n- A failure to pass the priority group to the DDC if the patient had a\n \nRequired Builds\n===============\nROES 3.0 (RMPF*3.0)\n \nThis patch contains the following enhancements and problem resolutions:\n=======================================================================\n \nThe following routines and program have been modified:\n \n\n
\n \n1. As approved by the PSAS Program Office, all Veteran eligibility \n \n 2. RMPFRPC1 - DDC changed to DALC. Added check to see if running from a\n production account. Comments were added and clarified.\n \n \n SOFTWARE RETRIEVAL:\n =====================\n \n The following software files are exported as part of this patch:\n \ndeterminations calculated by the software will be automatically \n File Name Contents Transfer\n \n RMPF3_4.KID VistA modifications ASCII\n \n RMPF3_0P4.ZIP Updated executables (354 KB) BINARY\n Containing the following files:\n ROES3.exe CPRS link to ROES web application 37 KB\n ROES3DeskTop.exe Desktop link to ROES web application 708 KB\n \n RMPF3_0P4_DOC.ZIP Updated documentation (1.816 MB) BINARY\napproved. Veteran eligibility requests will no longer be sent to the \n Containing the following files:\n RMPF3_0P4IG.PDF Installation Guide\n RMPF3_0P4SG.PDF Security Guide\n RMPF3_0P4TM.PDF Technical Manual\n RMPF3_0P4UM.PDF User Manual\n RMPF3_0P4RN.PDF Release Notes\n \n The KIDS part of the patch will be distributed in a PackMan message. It \n and the zip file containing the executables can also be downloaded from\n the national download directory at:\nProsthetic and Sensory Aids Service (PSAS) staff for approval. Changes \n \n download.vista.domain.ext\n \n This site transmits the files from the first available FTP server. \n Sites may also elect to retrieve software directly from a specific server\n as follows:\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n \n Albany ftp.fo-albany.domain.ext anonymous.software\nin the background calculations for Veteran eligibility are detailed in \n Hines ftp.fo-hines.domain.ext anonymous.software\n Salt Lake City ftp.fo-slc.domain.ext anonymous.software\n \n \n INSTALLATION INSTRUCTIONS:\n =========================\n \n Make a backup copy of the current ROES3.exe and ROES3Desktop.exe\n files (from a location where they currently are being used) to a\n backup location. Note the locations where all instances of those\nthe Release Notes for this patch.\n executables exist, for future maintenance.\n \n All obsolete options, routines, remote procedure calls and files from\n previous ROES versions will be removed during the installation. The list\n items being removed is listed in the ROUTINE SUMMARY SECTION of the\n build.\n \n Only ROES users need be off the system while ROES*3.0*4 is being\n installed. This patch should be installed during non-peak hours to\n minimize disruption. The total installation may take 15 minutes or more,\n \n depending on the CPRS Tools menu structure and number of ROES and\n ROES Desktop executables to update at your site. Be sure that the KIDS\n install (steps 1-9) are completed before updating the executables (steps\n 10-11). The KIDS install will run in less than 2 minutes.\n \n Review your mapped set. If the routines listed in the ROUTINE SUMMARY\n section of the build are mapped, they should be removed from the mapped\n set at this time.\n \n 1. Choose the INSTALL/CHECK MESSAGE option on the PackMan menu. \n2. For added security, the web connection has been changed from \n Answer YES to the prompt 'Want to Continue with Load? YES//'. This\n will load the KIDS package onto your system.\n \n 2. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n \n 3. From this menu, you may elect to use the following options (when\n prompted for INSTALL NAME, enter RMPF*3.0*4):\n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will not\nclear http to secure http using the https protocol identifier.\n backup any changes to DD's.\n b. Compare Transport Global to Current System - this option will\n allow you to view all changes to routines that will be made \n when the patch is installed.\n c. Verify Checksums in Transport Global - this option will allow you\n to ensure the integrity of the routines that are in the \n Transport Global.\n \n 4. Then choose the Install Package(s) option and select RMPF*3.0*4.\n \n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//", respond NO (unless otherwise indicated)\n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? YES//', respond "YES". When prompted to select the\n options you would like to place out of order, enter the following:\n \n ROES3 OPTION ACCESS [RMPF ROES3]\n \n 7. If prompted 'Enter protocols you wish to mark as 'Out of Order': \nThis patch addresses several issues that have come up at the VA Medical \n3. Adjustments were made for 64 bit terminal servers to access and \n press <return>.\n \n 8. When prompted 'Delay Install (Minutes): (0-60): 0//; respond '0.'\n \n 9. If you unmapped routines at the start, those SENT TO SITE\n should be returned to the mapped set once this part of the\n installation is complete.\n \n 10. Retrieve the file RMPF3_0P4.ZIP and extract files ROES3.exe and\n ROES3DeskTop.exe.\nuse the ROES web site.\n \n 11. All existing instances of ROES3.exe and ROES3DeskTop.exe need to\n be replaced, regardless of whether they reside on server(s) or\n individual workstation(s).\n \n To do this, copy the new executable files to those locations,\n replacing the existing version. Take care NOT to inadvertently \n replace the ROES3.exe file with the ROES3DeskTop.exe file,\n or vice versa. When this is completed properly, the command line\n option from CPRS Tools and the desktop links to ROES should continue\n \n to work without any modifications.\n \n If additional guidance is needed for the GUI installation, please refer\n to the ROES 3 Installation Guide on the System Design and Development \n web page at: http://www.domain.ext/vdl. Within the Clinical section look for\n 'Remote Order Entry System (ROES)'. Under that option you will find the\n Installation Guide, Security Guide, Technical Manual and User Manual.\n4. Connections from CPRS to the ROES web server will only be allowed to \nactually enter the web site if they are from a VistA production account to\nprevent false Veteran information from becoming a part of the national\ndatabase.\n \n5. Menu options, routines, remote procedure calls and security keys \nfrom prior versions of ROES that are no longer needed will be removed.\nCenters since the first release of the ROES package. All issues addressed \n Obsolete Options removed: RMPFDE2 and RMPFDE4\n Obsolete Routines removed: RMPFDE1,RMPFDE2,RMPFDE3 and RMPFDE4\n Obsolete Keys removed: RMPF SUPERVISOR and RMPF SYSTEM MANAGER\n Obsolete Remote Procedures removed: RMPF ELIG MSG and RMPFELIG\n \n6. Modifications for VistA and Delphi coding standards are included.\n \n7. Documentation has been updated regarding the removal of the \neligibility interactions before connecting to ROES.\n \nin this patch are related to the ROES application that runs from the CPRS \n \n Associated Remedy Tickets:\n ====================================== \n N/A\n \n \n E3R references addressed in this patch\n ======================================\n N/A\n \nTools menu (ROES3.exe). The ROES Desktop application (ROES3Desktop.exe) \n Test Sites\n ========\n Miami \n Omaha\n Phoenix\n Columbia (SC)\n \n Required Builds\n =============\n \nis only included for issues 2 and 3 below.\n RMPF*3.0*1\n \n \n \n This patch contains the following enhancements and problem resolutions:\n ==========================================================\n \n The ROES application requires that the user's browser have JAVA\n available and enabled in order to function. Sun has not developed a\n 64-bit version of JAVA, so on 64-bit terminal server installations the\n \n browser is not JAVA capable. This may prevent some ROES features from\n working properly. 64-bit installations also have a 32-bit browser\n which resides at a location different from the normal 32-bit location.\n That new location is:\n C:\\Program Files (x86)\\Internet Explorer\\IEXPLORE.EXE.\n \n The ROES executables that connect to the internet application have been\n modified to check for the 32-bit Internet Explorer at that location.\n This change will not affect any current 32-bit installations because, if \n Internet Explorer is not found at that location, ROES will look in the\n Issues addressed in this patch are:\n usual installation directories:\n C:\\Program Files\\Internet Explorer\\IEXPLORE.EXE or\n C:\\Program Files\\PLUS!\\Microsoft Internet\\IEXPLORE.EXE\n \n On a 64-Bit installation, if the ROES application still does not work\n properly after installing the new executable, please ensure the path\n "C:\\Program Files (x86)\\Internet Explorer\\IEXPLORE.EXE" does exist on\n the workstation.\n \n All workstations accessing the ROES application from either CPRS or the\n \n desktop need to have the RPCBroker Listener running, as in the previous\n releases of ROES. Refer to the RPCBroker Installation Guide for further\n direction, if needed. It can be retrieved from http://www.domain.ext/vdl.\n \n The following VistA routines have been modified to address new standards\n guidelines.\n \n 1. RMPFRPC0 - Eligibility calculations were modified for new rules and\n categories and is now called directly from RMPFRPC1 instead of from\n remote procedure call RMPFELIG.\n\n
\n \nThere are 2 new GUI applications: ROES3.exe and ROES3DeskTop.exe.\n b) The ROES 2 mail group RMPF ROES UPDATES (PSAS) continues to be\n used in ROES 3 to receive notification that a request for eligibility\n is waiting to be processed.\n \nInstallation Instructions:\n==========================\n \nThis patch was created with Kernel V8 KIDS.\n***Please refer to the complete instructions in the Installation Guide***\n \n \n1. This is a completely new installation, so it will not affect any\ncurrent ROES 2 users or others on the system. It can be run parallel\nto the existing ROES 2 system, until ROES 2 is no longer supported.\nYou do not need to restrict users from signing on or to lock any\noptions.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\nThis option will load the KIDS package onto your system.\n \n3. You DO NOT need to stop Taskman or the background filers. None\n*****Please refer to the INSTALLATION GUIDE and TECHNICAL MANUAL\nof the routines require mapping, so mapping does not need to be\ndisabled.\n \n4. Using the Kernel Installation and Distribution System menu\n(KIDS), you may choose the following options prior to installing\nthis patch:\n \n a) All routines are new, so there should be no need to Backup\n the Transport Global.\n \nfor installation and setup directions *****\n b) Again, this is an all new module, so there should be no\n need to Compare the Transport Global to the Current System.\n \n c) Verify Checksums in the Transport Global. This option will\n allow you to ensure the integrity of the routines that are\n in the Transport Global.\n \n5. Use the 'Install Package(s)' option under the 'Installation'\n menu.\n \n \n a) Select INSTALL NAME: ROES 3.0\n \n b) When prompted 'Want KIDS to Rebuild Menu Trees Upon\n completion of install?' YES// respond "NO"\n \n c) When prompted 'Want KIDS to INHIBIT LOGONs during the\n install?' YES// respond "NO"\n \n d) When prompted 'Want to DISABLE Scheduled Options, Menu\n Options and Protocols?' NO// respond "NO"\n(1) ROES3.exe is designed to be attached to the CPRS Tools Menu. This\n \n e) When prompted 'Want to MOVE routines to other CPUs?' YES//\n respond "NO"\n \n6. Confirm the presence of the two mail groups described under 'Technical\n Description' and enter the names of the respective mail group\n coordinators if necessary.\n \n7. Unzip the ROES3.ZIP file containing the 2 new executables: \n ROES3.exe and ROES3DeskTop.exe\napplication uses the currently selected patient, looks up the current\n They can be placed on the network according to local policy,\n in a place where they can be referenced from CPRS Tools and\n from the user's workstation.\n \n8. Assign the Broker option RMPF ROES3 to users of either application.\n \n9. Add the application ROES3.exe to the CPRS Tools menu.\n \n10. Add a link to the ROES3DeskTop application on the selected user's\n workstation desktop.\neligibility information and connects to the DDC ROES 3 web site. If an\naccepted eligibility is not found, the user selects a proposed eligibility\nand triggers the sending of the request to PSAS for approval.\nThe Remote Order Entry System (ROES) version 3.0 was developed\n \n(2) ROES3DeskTop.exe is designed to be referenced from the user's \ndesktop, as it is not tied to a particular patient. It is used for\nstation orders, parameter setting, and certain updates to already\nexisting patient orders.\n \nNOIS references addressed in this patch\n=======================================\nThere are no NOIS or E3R references\n \nat the VA Denver Distribution Center(DDC). It is a changeover to\nTest Sites\n==========\nDenver\nNew York\nColumbia\nMountain Home\nAtlanta\nNashville\nWashington DC\n \na GUI(windows) based product that allows ordering of goods and\nFTP Software and Documentation\n==============================\n \n \nThis patch contains the following enhancements:\n===============================================\n \n \n \n ROUTINE SUMMARY\nservices over the internet and greatly reduces the amount of \n================\nThe second line of all listed routines will look like:\n <tab> ;;3.0;REMOTE ORDER ENTRY SYSTEM;;\n \nCHECK^XTSUMBLD results:\n \nRMPFRPC0 checksum = 14317184\nRMPFRPC1 checksum = 4846679\nRMPFRPC3 checksum = 2795744\nRMPFDE2 checksum = 4775274\nmaintenance and support at the local sites. All of the product\nRMPFDE3 checksum = 6656730\nRMPFDE4 checksum = 1968602\n \nTechnical Description\n=====================\n \n1. New file introduced with this patch:\n \n The ROES ELIGIBILITY CONFIRMATION file (#791814) is introduced to\n store the eligibility request information.\nand service information will be kept and maintained at the\n \n2. New VistA Options introduced with this patch:\n \n a) RMPF ROES3 is used to establish a context and allow access to\n the 2 new executables. It must be assigned to all users of \n the CPRS Tools or DeskTop applications.\n \n b) RMPFDE2 is used by PSAS to accept/edit/reject eligibility for\n ROES3 orders. This is a standard VistA option and must be\n placed on a user's menu.\nDDC, with real-time information on orders and inventory.\n \n c) RMPFDE4 is the option to be scheduled to remind all PSAS users\n in the RMPF ROES UPDATES (PSAS) mail group that requests for\n eligibility approval are waiting for approval.\n \n3. New VistA Remote Procedures introduced with this patch:\n \n a) RMPFDEMOG collects demographic data for transmission to the DDC\n for the site, user and patient.\n \n \n b) RMPFELIG calculates the approved ROES 3 eligibility.\n \n c) RMPF ELIG MSG sends the suggested eligibility to PSAS for approval.\n \n4. Mail groups in ROES 3\n \n a) The ROES 2 mail group RMPF ROES UPDATES (ASPS) continues to be\n used, only this time it is to alert audiologists when a request\n for eligibility approval has been acted upon.\n \n\n
\nThis system allows users of VA Medical Facilities to electronically\norder products and services from the Denver Distribution Center\nin Denver, Colorado.\n\n
\nThis is patch 1 of Spinal Cord Dysfunction Version 2. This patch will fix\nthe undefined variable SPNPAGE.\n\n
\nfix for 154.991\n\n
\nOutcome module fixes.\n\n
\nThis is patch 2 for Spinal Cord Dysfunction Version 2.0. This patch\nresolves the following NOIS: CAS-0497-10709, WIM-0497-20628,\nHOU-0497-70385, BRK-0397-12815, HUN-0397-20346, ISD-0397-70256,\nDAY-0397-40132, DEN-0297-51749, SDC-0297-61101, SDC-0297-60260,\nand LIT-0197-71898.\n\n
\nRevision of object code to support TIU objects for Spinal Cord\nDysfunction.\n\n
\nADD UNIQUE IDENTIFIER TO OUTGOING HL7 FIM MESSAGE\n\n
\nPlease see the National Patch Module for the full description.\n\n
\nThis patch will enhance the Spinal Cord Dysfunction 2.0 package \nThis problem is fixed with routine SPNLPIN. This patch is to correct an\nSPNPRTMT 1693776 1722973 **3** \nSPNPRTUP 605589 1237772 **3** \nSPNPST03 N/A 938139 **3** \n \n \nGeneral Information\n===================\n \nThis patch should be installed into your production UCI. It can be\ninstalled at anytime. Install time should not take more than ten minutes.\nerror in the Sort by Geographical Area. The routine SPNPSR06 has been\nThis patch has no other dependencies. No options need to be disabled.\nIf there are any questions, your supporting CIOFO Customer Service Patient\nInformation Management team will address them.\n \n \nInstallation instructions: \n========================= \n \nThis Patch is created with Kernel V8 KIDS. Follow these instructions: \n \ncorrected. The routines was modified to use D0 ("0" Zero) instead of\n1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build onto \n your system. \n2) On the KIDS menu, under the 'Installation' menu, use the option 'Verify \n Checksum in Transport Global' and verify that all routines have the \n correct checksums. \n3) From the 'Installation' Menu of KIDS, use the option 'Install \n Package(s)'. Select the package 'SPN*2*3' and proceed with install. \n4) If you are a MSM site, move the routines to the other servers. \n5) On a mapped system, rebuild your map set. \n6) Delete the post-init routine SPNPST03. \nDO ("O" Letter).\n \n2) NOIS# SDC-0697-61902 Data Error in FSS report\n \n Option: Functional Status Scores [SPNF FIM SCORES]\n \nWhen a user selects the option 2 Clinical Reported FIM, under the\n \nselection 2 Functional Information to enter Functional Status data for SCD\npatients, the user will get the wrong Extent & Completeness and Type of\nInjury data displayed when the user runs the Total Score Selection option\nin the Functional Status Score. Routine SPNFPLT1 has been modified to\ncalculate the data correctly. \n \n3) NOIS# LIT-0697-71551 Last Physical Date\n TAM-0297-30780 Last Physical Exam Field included in report.\n Option: Follow-up (Last Physical Exam)\n [SPNL F/U LAST PHYS EXAM]\nThis patch will also resolve the following: \n \nWhen the user enters dates in the Sub-Fields, ANNUAL REHAB EVAL OFFERED\n(#.01), ANNUAL REHAB EVAL RECEIVED (#1), and NEXT ANNUAL REHAB EVAL DUE \n(#2), under the Multiple field ANNUAL REHAB EVAL OFFERED #7 in file 154,\nSCD (Spinal Cord) Registry, the option Follow-up (Last Physical Exam) under\nthe Filtered Reports menu should display the date in the field ANNUAL\nREHAB EVAL RECEIVED #1 instead of the date in the field LAST PHYSICAL EXAM\n#1.2, which is no longer used will be deleted in a future release. This is\nfixed in the routines SPNLR and SPNLRE.\n \n \n4) NOIS# DEN-0597-52404 Reg. Injury Report Wrong Sent to printer\n Option: Registrant Injury Report\n [SPNL REGISTRANT INJURY REPORT]\n \nIf the user enters in filter criteria to screen on SCD Patients for the\nRegistrant Injury Report, the program would not use the filters if that\nreport were queued to a printer. This is fixed in routine SPNLPIN\n \n5) NOIS# BRK-0397-12815 Extract Error\n Database Correction: Field MS Type (#2.2) in SCD (SPINAL CORD) \n1) NOIS# IOW-0997-41147 Undefined Variable DO\n REGISTRY File (#154)\n \nThe data was not deleted in the global position prior the creation of the\nfield MS Type #2.2 in the in SCD (SPINAL CORD) REGISTRY File (154). The\nPost- Init will check the data and delete all invalid entries.\n \nNON-NOIS ISSUES\n \n6) Filtered Reports menu Enhancement\n \n \nThe option Filtered Reports [SPNL SCD REPORT(FILTERED)] menu has been\nmodified to allow users to turn off the filters. This enhancement will\ngive the users the option of using the filters for the filtered reports or\nskip the filters and go directly to the reports. The following routines\nhave been modified: SPNPRTMT, and SPNPRTUP.\n \n7) Patient Summary Report Fix\n \nThis patch will fix the report, Patient Summary Report [SPNL REGISTRY\nSUMMARY]. The Print Template [SPNL REGISTRY DUMP] in file 154 has been\n Option: Registrant General Report [SPNL REGISTRANT GENERAL REPORT]\nmodified by replacing the old field LAST PHYSICAL EXAM with the latest\nentry in field ANNUAL REHAB EVAL RECEIVED (#1) in the ANNUAL REHAB EVAL\nOFFERED multiple (#7). The new field will be listed as Last Annual Rehab\nReceived. \n \nTest Sites \n========== \nIowa City, IA \nSan Diego, CA \nLittle Rock, AR \nAn undefined D0 error will occur when the user uses the option Registrant\nDenver, CO \nBrockton, MA \nTampa, FL \n \nRoutine Summary:\n================\nThe following routines are included in this patch. The second line of\nthese routines should look like: \n \n <tab>;;2.0; Spinal Cord Dysfunction;**[patch list]**; 01/02/1997\nGeneral Report under the filtered Reports [SPNL SCD REPORTS (FILTERED)].\n \nCHECK^XTSUMBLD results: \n \nRoutine Name Before Patch After Patch Patch List \n============ ============ =========== ========== \nSPNFPLT1 5617787 5730334 **3** \nSPNLPIN 6042813 6551065 **3** \nSPNLR 4151564 4199229 **3** \nSPNLRE 3909143 4086084 **3** \nSPNPSR06 1393910 1400648 **3** \n\n\nRefer to patch description in patch modual.\n\n
\nRefer to description in patch.\n\n
\nPlease see the description on the patch menu.\n\n
\nSpinal Cord Dysfunction Version 2.0\n\n
\nSpinal Cord Dysfunction Decommissioning. This patch will remove all \ncomponents including the files and data.\n\n
\nThe Spinal Cord Dysfunction package is intended to provide a registry of\nSCD patients and to track their functional statuses.\n\n
\nUpdate to server message processing.\n\n
\nThis patch lowers the limit of time cards per message from 1000 to 300,\nand corrects the processing of termination dates when the year of the\ntermination ends in 00.\n\n
\nThis patch corrects an error in patch 19 which inadvertantly converted a\ndate of 0000 to 3000000 (Year 2000 with no month and day)\n\n
\nThis patch distributes the updated SERVER routine to correct the problem\ncreated in patch 19\n\n
\nThis patch accomplishes the following actions:\n3. Addition of an edit during the 'roll up' process to validate\ncombinations on the time card to the current master record.\n \n4. Makes corrections suggested by Kernel Team when calling %ZIS.\nSpecifically, changing Q:POP to I POP D HOME^%ZIS QUIT\n \n5. Corrects code that prevented printing of meal tickets on weekends and\nholidays when requested by the user.\n \n6. Corrects $Random problem in ABSVLS1 identified in NOIS: DAY-0400-41214\n \n \n7. Added feature to Single and Multiple posting options to notify user\nthat a volunteer has been terminated. Previously the user could not even\nsee volunteers who were terminated.\n \n8. Limits the number of Master Records (TT88's) per message to 150.\nPotential overflow problem in Austin.\n1. Enhanced label printing, including the ability to skip used label\npositions on a page.\n \n2. Dissemination of the master listing of Representatives and Deputies,\nincluding their areas of jurisdiction and appropriate label printing\noptions.\n \n\n
\nThis patch accomplishes the following actions:\n \nUpdate of the National Officials file (503334.1) data.\n\n
\nThis patch accomplishes the following actions:\n \nUpdate of the National Officials file (503334.1) data.\n\n
\nThis patch contains:\nreceived from the Austin Automation Center.\n \nAllow the user the option to print single or multiple, collated or\nuncollated labels.\n \nThe files and data and necessary to support the National Voluntary Service\nDirectory.\n \nCorrection to the Zip Code label program to sort by the standard 5 digit\nZip Code required by the USPS for bulk mail.\n \nCorrected an error found in posting the Last Award Date in the data\n\n
\nVoluntary Donation Module to Volunteer Timekeeping Package\n\n
\nThis patch will permit LAYGO access to the GPF/DONATION (503342) file for \nadding entries, without the need for specific LAYGO access through part \nIII of Kernel.\n\n
\nThis patch will add the 135V - VETERANS HISTORY VOLUNTARY SERVICE - VHVS \nentry into file 503332.\n\n
\nMiscellaneous corrections.\n\n
\nCorrects the use of the "," is the FR and TO strings in print templates.\n \nThis option also deletes access to the National Officials File.\n\n
\nThis patch corrects sorting on report by organization, where the \norganization contains a ",".\n\n
\n \nA companion patch, ABSV*4.0*32, contains the option that sends the data to\n Voluntary Data Migration Menu\n\n PREP Prepare for Transition to VSS\n VAL Validate Existing Data\n PRNT Print Results of Data Validation\n VOL Master Volunteer Edit\n DAIL Daily Time Edit\n OCC Occasional Hours Edit\n SEND Send Voluntary Data to VSS\n **> Locked with ABSV MIGRATION\nthe new system.\n\n (Note: the Send option will appear only after patch 32 is installed.)\n\n This menu is locked with the already existing ABSV MGR Security Key; so,\n only holders of that key will be able to run these options.\n\n Briefly,\n\n PREP option does some initial setup for your site and sends information\n that is used to establish your site on the VSS centralized server. Run\n \n this option once only.\n\n VAL option checks your existing data and creates a report of entries\n that contain inconsistent data that can be corrected before the data is\n sent to the new system. This option can be run as often as you like.\n\n PRNT option displays the results of the Validate option. It can be run\n as often as you like.\n\n VOL option allows the user to edit all the fields they need to correct\n \n a problem with the Volunteer information.\n\n DAIL option allows the user to edit all the fields they need to correct\n a problem with Regular Hours information.\n\n OCC option allows the user to edit all the fields they need to correct\n a problem with Occasional Hours information.\n\n SEND option sends the data to the new system. It should be run only once\n unless SI instructs you to run it again.\nPATCH DEPENDENCIES:\n\n\n PREPARE FOR TRANSITION TO VSS\n\n VSS will contain information about your Voluntary Service. If your site is\n multi-divisional, it will contain information about each division to which\n Volunteer Hours are recorded. Most of the information about your Voluntary\n Service and its staff will entered by Voluntary Service personnel using the\n new VSS web interface. However, some data is needed for initial setup of\n your site. The main purpose of the Prepare for Transition to VSS option is\n \n to gather this preliminary information and to send it to the people who will\n do the initial data entry.\n\n Following is the dialog you will see when running this option.\n\n Select Voluntary Data Migration Menu Option: Prepare for Transition to VSS\n\n You are starting the process that will move \n Voluntary Timekeeping data to the new \n Voluntary Service System application.\nNone.\n\n First, information about your site will be collected.\n Your Volunteer Daily Time file will be scanned to find \n all sites referenced. This will take some time.\n\n Done.\n\n Your primary site number is 605\n Hours are recorded to the following sites:\n 605\n \n\n The option has looked through your Volunteer Daily Time file and identified\n all the sites (or institutions) to which regular volunteer hours have been\n recorded since 10/1/1996. Displayed are your primary station number and\n the station numbers of all the sites for which hours were found.\n\n If this information appears to be incorrect, answer the following question\n "NO" and contact SI for further instructions. Otherwise, answer "YES" and\n proceed.\n\n \n Is this site information correct? YES\n\n Now an entry for your site is made in a new file that was installed on your\n system by patch 31, the Voluntary Migration Log file. The data recorded\n when running the migration options is stored in this file.\n\n\n Making an entry in the Voluntary Migration Log file.\n\n You will be asked for information about each station to which hours are\nNo NOISs or E3Rs are addressed by this patch.\n recorded. In this example, only one station is involved. If your\n multi-divisional site has more than one station, answer the questions for\n each station even if the answers are the same.\n\n\n Add information for Station Number 605\n\n STATION NAME: Loma Linda Test\n VISN: 22\n STREET ADDRESS LINE 1: 1 Hospital Way\nThis patch is part of the migration from the VistA-based Voluntary\n \n STREET ADDRESS LINE 2: <RET>\n CITY: Loma Linda\n STATE: CA\n ZIP CODE: 99999\n USER ADMIN'S LAST NAME: Boss\n USER ADMIN'S FIRST NAME: Big\n USER ADMIN'S MIDDLE NAME: B.\n USER ADMIN'S NT USERNAME: vhamaster\\vhaisfbossb\n\n The first seven questions are self-explanatory. \n \n\n The questions about the User Administrator refer to the lead person at\n your site. That person will be responsible for entering site data and\n setting up other local users. Often, it will be the Voluntary Service\n Chief.\n\n It is very important that this person's NT Username is entered correctly.\n You must enter both the domain and the username separated by a "\\".\n\n Next you are asked for the e-mail address of the recipient of this\nROUTINE SUMMARY:\n information. The message is sent via MailMan to a Microsoft Exchange\n address. SI will provide you with the necessary e-mail address. You can\n also send the message to local MailMan recipients. In the following\n example, John Smith is the user.\n\n Your local IRM must assure that mail can be sent successfully to the\n domain.ext domain. The sending of this message will be a test of that\n domain, which will also be used when the actual data is sent.\n\n Sending a message containing information about your site.\n================\n Enter a Recipient of the Institution Creation message: first.last@domain.ext\n Enter a Recipient of the Institution Creation message:\n SMITH,JOHN (use your own name here)\n Enter a Recipient of the Institution Creation message: <RET>\n Message sent. Message number: 8250639\n\n This completes the preparatory option on the MUMPS system. SI will\n contact you after your site has been initialized on VSS and the new\n system is ready to recieve your data. \n\n The following is a list of the routines that are included in this\n You can now proceed with the review of your local data.\n\n\n VALIDATE EXISTING DATA:\n\n PREP Prepare for Transition to VSS\n VAL Validate Existing Data\n PRNT Print Results of Data Validation\n VOL Master Volunteer Edit\n DAIL Daily Time Edit\n patch. The second line of each of these routines now looks like:\n OCC Occasional Hours Edit\n SEND Send Voluntary Data to VSS\n\n Select Voluntary Data Migration Menu Option: Validate Existing Data\n\n Data that will be moved to the new Voluntary Service System database\n will now be checked for consistency.\n\n The result will be recorded in the Voluntary Migration Log File.\n You will have the opportunity to print these results.\n ;;4.0;VOLUNTARY TIMEKEEPING;*31*;Jul 1994\n\n The data validation process will review all of the entries that will be\n moved from your VistA VTK system to the new VSS server. A report will be\n made containing each entry that has incorrect or inconsistent data.\n You can use that report to correct entries so that a complete set of data\n is moved to the new system.\n\n Entries that are reported as containing a problem will not be migrated to\n the new system unless the problem is corrected in your data.\n\n \n Because there are many records involved, running this option may take some\n time. Particularly time consuming will be the validation of the Volunteer\n Regular Hours.\n\n A dialog indicating progress is presented as the validation goes on. When\n the check of each file is done, the number of entries with errors is\n displayed.\n\n \n Do you want to proceed? YES\nRoutine Name Before Patch After Patch Patch List\n\n Creating list of all Volunteers with hours after Sept. 30, 1996.\n Done.\n\n Creating lists of valid Organization, Service, Schedule, and Award Codes.\n Done.\n\n Validating entries in the Volunteer Organization Codes File.\n Errors Found in Organization Codes: 1\n\n============ ============ =========== ==========\n Validating entries in the Service Assignment Codes File.\n Errors found in Service Assignment Codes: 1\n\n Validating Occasional Hours.\n Errors found in Occasional Hours: 12\n\n Validating Regular Hours.\n THIS WILL TAKE SOME TIME.\n Errors found in Regular Hours: 1\n\nTimeKeeping package to the web-based Voluntary Service System (VSS).\nABSVM N/A 15748896 31\n Validating Volunteer data.\n THIS WILL TAKE SONE TIME.\n Errors found in Volunteer data: 6\n\n The data checking on your system is complete!\n\n After the validation finishes, you can immediately print the results.\n Whether you print it at this time or not, the information on incorrect\n entries is stored and can be printed at any later time. \n\nABSVM1 N/A 3639237 31\n Do you want to print the results now? YES\n DEVICE: HOME//<RET>VIRTUAL CONNECTION Right Margin: 80//<RET> \n\n The error reports are grouped by type and indicate the record number (IEN)\n of the record that contains the problem. For the volunteers, the name of\n the volunteer is also shown to help in identification.\n \n This completes the data validation option. This option can be rerun with\n results reflecting the status of your data at the time it is rerun.\n\nABSVMHV1 N/A 17163056 31\n You do not, however, need to rerun the option just to view the results of\n a prior run. You can print previous results.\n\n\n PRINT RESULTS OF DATA VALIDATION:\n\n PREP Prepare for Transition to VSS\n VAL Validate Existing Data\n PRNT Print Results of Data Validation\n VOL Master Volunteer Edit\nABSVMLC1 N/A 703152 31\n DAIL Daily Time Edit\n OCC Occasional Hours Edit\n SEND Send Voluntary Data to VSS\n\n Select Voluntary Data Migration Menu Option: Print Results of Data Validation\n\n You can print results of the Examination of Existing Data \n by selecting the date/time that the examination was done.\n\n Note that the validation results are stored by date and time run. The\nABSVMLC2 N/A 559992 31\n simplest way to choose the results to print is to input the date that the\n validation was run. In the following example, the results of validation run\n "TODAY" are requested. You select the specific set of data validated to\n print. In this example, the results for Regular and Occasional Hours are\n selected.\n\n \n Select VALIDATION RESULTS TIME RUN: TODAY OCT 04, 2002\n 1 10-4-2002@18:14:10 Organizations NO, ONLY VALIDATION DONE\n 2 10-4-2002@18:14:11 Services NO, ONLY VALIDATION DONE\nABSVMLC3 N/A 759900 31\n 3 10-4-2002@18:14:11 Occasional Hours NO, ONLY VALIDATION DONE\n 4 10-4-2002@18:14:11 Regular Hours NO, ONLY VALIDATION DONE\n 5 10-4-2002@18:14:23 Volunteers NO, ONLY VALIDATION DONE\n CHOOSE 1-5: 4 10-4-2002@18:14:11 Regular Hours NO, ONLY VALIDATION DONE\n\n Do you want to select another result to print? YES\n\n Select VALIDATION RESULTS TIME RUN: T OCT 04, 2002\n 1 10-4-2002@18:14:10 Organizations NO, ONLY VALIDATION DONE\n 2 10-4-2002@18:14:11 Services NO, ONLY VALIDATION DONE\nABSVMRV1 N/A 10324879 31\n 3 10-4-2002@18:14:11 Occasional Hours NO, ONLY VALIDATION DONE\n 4 10-4-2002@18:14:11 Regular Hours NO, ONLY VALIDATION DONE\n 5 10-4-2002@18:14:23 Volunteers NO, ONLY VALIDATION DONE\n CHOOSE 1-5: 3 10-4-2002@18:14:11 Occasional Hours NO, ONLY VALIDATION DONE\n\n Do you want to select another result to print? NO\n DEVICE: HOME// VIRTUAL CONNECTION Right Margin: 80// \n\n\n\nABSVMS1 N/A 9693434 31\n CORRECTING DATA:\n\n You are requested to run the data validation option weeks before the actual\n switch to the new system so that you have the opportunity to correct invalid\n records. Corrected records will be migrated to the new system while those\n remaining with an error will be rejected.\n\n The method of correction will depend on the problem. In some cases, you\n will have to contact volunteers; in others, you will have to refer to paper\n records. When the necessary information is obtained, you will usually be\nABSVMUT1 N/A 8407468 31\n able to use the existing VTK options to make the change. You can also use\n the three options supplied in this patch: Master Volunteer Edit , Daily Time\n Edit, Occasional Hours Edit. If you cannot use the normal options, contact\n your local IRM. If your local IRM cannot resolve the issue they should file\n a NOIS report and NVS will assist in getting the problem resolved.\n\n Following is an example of correcting Volunteer data. Copied below is a\n line from the validation report run above:\n\n Volunteer record #3418 with Name MAYO,MARION has incorrect sex data.\nABSVMVV1 N/A 12548749 31\n\n A volunteer with record number 3418 in the Voluntary Master file whose name\n is Marion Mayo somehow has incorrect information in the SEX field. It is\n unimportant how that erroneous data got there. Suppose you determine that\n Marion is a woman. Correct the error by using the Register/Edit Volunteer\n in Master File option:\n\n \n Select Master File Maintenance Menu Option: Register/Edit Volunteer in\n Master File\n \nABSVMVV2 N/A 11698483 31\n\n Select Volunteer Name: `3418 MAYO,MARION\n\n Note: the volunteer is selected by putting an accent grave (`) in front of\n the entry number from the error report. This method should work for any\n data you are correcting, regardless of file. In this case, you could have\n also used the name.\n\n Do you wish to Add/Edit Volunteer specific data? YES//<RET> (YES)\n\nABSVMVV3 N/A 7742190 31\n NICKNAME: <RET>\n PSEUDO INDICATOR: <RET>\n SOCIAL SECURITY NUMBER: 999-99-9999// <RET>\n STREET ADDRESS #1: 1 Main St.// <RET>\n STREET ADDRESS #2: <RET>\n CITY: MORENO VALLEY// <RET>\n STATE: CALIFORNIA// <RET>\n ZIP CODE: 92553// <RET>\n\n Here the source of the error is clear. Somehow a "Z" was input into the\n\n SEX field. The data validation option identified this as being incorrect.\n Here, it is corrected to F for Female.\n\n SEX: Z// F Female, 21 and over\n BIRTH DATE: JUL 1970// ^\n Do you wish to continue to the next section? YES// NO (NO)\n Do you need to transmit this record to Austin? YES// NO (NO)\n < No Action Taken>\n\n Now, Marion's entry and the entries of the Regular Hours that she worked\n \n can be sent to the new system.\n\n\n Documentation:\n --------------------\n The ABSV_4_31ig.pdf, can be obtained from the ANONYMOUS.SOFTWARE\n directory at one of the OI Field Offices. The preferred method is to FTP\n the file from DOWNLOAD.VISTA.DOMAIN.EXT, which will transmit the file from\n the first available server. Alternatively, site may elect to retrieve the\n file from a specific OI Field Office. The documentation can be read via\nINSTALLATION INSTRUCTIONS\n the Adobe Acrobat Reader browser program. The .PDF file are binary file and\n must be transferred using binary file transfer tools.\n \n IO FIELD OFFICE FTP Address DIRECTORY\n --------------- ----------------- -----------------\n Hines FTP.FO-HINES.DOMAIN.EXT [ANONYMOUS.SOFTWARE]\n Albany FTP.FO-ALBANY.DOMAIN.EXT [ANONYMOUS.SOFTWARE]\n Salt Lake FTP.FO-SLC.DOMAIN.EXT [ANONYMOUS.SOFTWARE]\n \n \n=========================\n Files Description Block Count\n --------------- ------------------------ --------------\n ABSV_4_31ig.pdf Installation Guide (PDF) \n\n \n If you have further questions on obtaining the PDF files, please contact\n the CIO National Help desk at 1-888-596-4357, and ask for the Fiscal\n Management Team.\n\n \nThis patch should take less than 1 minute to load.\n - No existing data is changed during patch installation.\n - No options need to be disabled.\nThis patch installs routines, options, other components, and file 503339.5\n - None of these routines are or will be mapped.\n - Users can be on the system when this patch loads.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 2. From the Kernel Installation and Distribution System (KIDS) menu,\n you may elect to use the following options:\n\n a. Verify Checksums in Transport Global - this option will allow\nVOLUNTARY MIGRATION LOG. These are all new and will allow the site to\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - this option will allow you to view\n the components of the KIDS build.\n c. Backup a Transport Global - this options doesn't need to be\n run because all of the routines in this patch are new.\n d. Compare Transport Global to Current System - this options doesn't\n need to be run because all components in this patch are new.\n\n 3. Use the Install Package(s) option and select the package\nsend information used to set up a new station in VSS, to check existing\n ABSV*4.0*31.\n\n 4. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES//', respond NO.\n\n 5. When prompted 'Want KIDS to INHIBIT LOGONs during the\n Install? YES//', respond NO.\n\n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond NO.\nVTK data, and to print error reports of the data validation.\n \n\n\n\n\n Voluntary Service Staff Instructions for patch ABSV*4*31\n\n\n After patch ABSV*4*31 is installed at a site, the Voluntary Service staff\n can begin the data cleansing process. The Systems Implementation (SI)\n \n group will give specific instructions to the Voluntary Service staff\n regarding the timing and other particulars of the migration.\n\n This process will start when the patch is received by the site and should\n be completed not later than 2 weeks before the sites scheduled conversion\n date.\n\n The patch installs a new menu on the Volunteer Timekeeping Activity menu.\n The new menu looks like this:\n\n\n
\n \n \n \n \n After patch ABSV*4*33 is installed at a site, you need to delete the\n entry in the VOLUNTARY MIGRATION LOG file. You are going to need\n FileMan access for this, IRM should be able to help you. There should\n only be one entry in this file, your site station number. After deleting\n it, you need to re-run the 'Prepare for Transition to VSS' option under\n the 'Voluntary Data Migration Menu'. Please refer to patch ABSV*4.0*31\n documentation.\n\nThis patch installs routines, other components, and file 503339.5\n VA FileMan Version 22.0\n\n Enter or Edit File Entries\n Print File Entries\n Search File Entries\n Modify File Attributes\n Inquire to File Entries\n Utility Functions ...\n Data Dictionary Utilities ...\n Transfer Entries\nVOLUNTARY MIGRATION LOG. These are all updates, originally installed\n Other Options ...\n\nSelect VA FileMan Option: ENTER or Edit File Entries\n\nINPUT TO WHAT FILE: VOLUNTARY MIGRATION LOG// \nEDIT WHICH FIELD: ALL// \n\n\nSelect VOLUNTARY MIGRATION LOG SITE NUMBER: 662\nSITE NUMBER: 662// @\nwith patch ABSV*4.0*31, and will allow the site to check existing\n SURE YOU WANT TO DELETE THE ENTIRE '662' VOLUNTARY MIGRATION LOG? Y (Yes)\n\n\n\nThe following is a dialog of the 'Prepare for Transition to VSS' option:\n \n Voluntary Data Migration Menu \n \n PREP Prepare for Transition to VSS \n VAL Validate Existing Data \nVTK data, and to print error reports of the data validation.\n PRNT Print Results of Data Validation \n VOL Master Volunteer Edit \n DAIL Daily Time Edit \n OCC Occasional Hours Edit\n\n Select Voluntary Data Migration Menu Option: Prepare for Transition to VSS\n\n You are starting the process that will move \n Voluntary Timekeeping data to the new \n Voluntary Service System application.\n\n\n First, information about your site will be collected.\n Your Volunteer Daily Time file will be scanned to find \n all sites referenced. This will take some time.\n\n Done.\n\n Your primary site number is 605\n Hours are recorded to the following sites:\n 605\nAfter installing this patch, you need to re-run the 'Prepare for Transition\n 702\n 999\n\n The next section will allow you to designate which of the above sites\n you want data sent from. Your primary site will default to 'YES' \n Any Games site,(700, 701, 702, or 575W), will default to 'NO'.\n\n Do you want to continue? YES\n\n Making an entry in the Voluntary Migration Log file.\n to VSS' option under the 'Voluntary Data Migration Menu'.\n\n (You will be asked for information about each station to which hours are\n recorded. In this example, multiple stations are involved. One is a Games\n station and another is a test site. Only the primary station has data that\n the user wants to migrate.\n\n It is also, recommended that you use the station name from the institution\n file.)\n\n Add information for Station Number 605\n \n STATION NAME: Loma Linda Test\n VISN: 22\n STREET ADDRESS LINE 1: 1 Hospital Way\n STREET ADDRESS LINE 2: <RET>\n CITY: Loma Linda\n STATE: CA\n ZIP CODE: 99999\n USER ADMIN'S LAST NAME: Boss\n USER ADMIN'S FIRST NAME: Big\n USER ADMIN'S MIDDLE NAME: B.\nA companion patch, ABSV*4.0*32, contains the option that sends the data to\n USER ADMIN'S NT USERNAME: vhamaster\\vhaisfbossb\n\n\n Add information for Station Number 702\n Send this Station's Data?: NO\n\n Add information for Station Number 999\n Send this Station's Data?: YES// NO\n\n\nThis patch is part of the migration from the VistA-based Voluntary\nthe new system.\n Sending a message containing information about your site.\n Enter a Recipient of the Institution Creation message: first.last@domain.ext\n Enter a Recipient of the Institution Creation message:\n SMITH,JOHN (use your own name here)\n Enter a Recipient of the Institution Creation message: <RET>\n Message sent. Message number: 8250639\n\n\n If you have any questions or need assistance with this patch please contact\n the CIO National Help desk at 1-888-596-4357, and ask for the Fiscal\n \n Management Team.\n\n \nPATCH DEPENDENCIES:\n ABSV*4.0*31\n \nNOIS:\n NHM-0303-12436 = Service Code 170A missing\n \n \nTimeKeeping package to the web-based Voluntary Service System (VSS).\nROUTINE SUMMARY:\n================\n The following is a list of the routines that are included in this\n patch. The second line of each of these routines now looks like:\n ;;4.0;VOLUNTARY TIMEKEEPING;*31*;Jul 1994\n \nRoutine Name Before Patch After Patch Patch List\n============ ============ =========== ==========\nABSVM 15748896 17148928 31,33\nABSVM1 3639237 2810664 31,33\nIt is a patch for ABSV*4.0*31. It will add the missing Service Codes,\nABSVMHV1 17163056 17609281 31,33\nABSVMLC1 703152 1046809 31,33\nABSVMLC2 559992 918431 31,33\nABSVMS1 9693434 9910965 31,33\nABSVMUT1 8407468 8467551 31,33\nABSVMVV1 12548749 12661211 31,33\nABSVMVV2 11698483 11297170 31,33\nABSVMVV3 7742190 8199323 31,33\n\n \n170A and 270A-E. It also excludes data from any Game site; stations\nINSTALLATION INSTRUCTIONS\n=========================\n \nThis patch should take less than 1 minute to load.\n - No existing data is changed during patch installation.\n - None of these routines are or will be mapped.\n - Users can be on the system when this patch loads.\n - Voluntary Service should not be using the 'Voluntary Data Migration\n Menu'\n \n700, 701, 702,and 575W. For consolidated stations, the user will be\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 2. From the Kernel Installation and Distribution System (KIDS) menu,\n you may elect to use the following options:\n\n a. Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - this option will allow you to view\nprompted to send or not send data for each site. This will allow them \n the components of the KIDS build.\n c. Backup a Transport Global - this options doesn't need to be\n run because all of the routines in this patch are new.\n d. Compare Transport Global to Current System - this options doesn't\n need to be run because all components in this patch are new.\n\n 3. Use the Install Package(s) option and select the package\n ABSV*4.0*33.\n\n 4. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\nto exclude Voluntary Time Keeping data for old site numbers. \n Install? YES//', respond NO.\n\n 5. When prompted 'Want KIDS to INHIBIT LOGONs during the\n Install? YES//', respond NO.\n\n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond YES.\n\n Enter options you wish to mark as 'Out Of Order': ABSV MIGRATION MENU \n Voluntary Data Migration Menu\n\n \n Enter options you wish to mark as 'Out Of Order': \n \n Enter protocols you wish to mark as 'Out Of Order':\n \n\n \n\n\n Voluntary Service Staff Instructions for patch ABSV*4*31 \n\n
\nThis patch should be installed at all sites, even if your site has\n \nPATCH DEPENDENCIES:\n ABSV*4.0*33\n \nNOIS:\n NYH-0603-11946\n\n \nROUTINE SUMMARY:\n================\nalready migrated to the web-based Voluntary Service System (VSS).\n The following is a list of the routines that are included in this\n patch. The second line of each of these routines now looks like:\n ;;4.0;VOLUNTARY TIMEKEEPING;*31*;Jul 1994\n \nRoutine Name Before Patch After Patch Patch List\n============ ============ =========== ============\nABSVMHV1 17609281 17425691 **31,33,35**\nABSVMVV2 11297170 11722394 **31,33,35**\n\n \n\nINSTALLATION INSTRUCTIONS\n=========================\n \nThis patch should take less than 1 minute to load.\n - No existing data is changed during patch installation.\n - None of these routines are or will be mapped.\n - Users can be on the system when this patch loads.\n - Voluntary Service should not be using the 'Voluntary Data Migration\n Menu'\n \nABSV*4.0*35 is a patch for patch ABSV*4.0*33. It will correct a problem\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 2. From the Kernel Installation and Distribution System (KIDS) menu,\n you may elect to use the following options:\n\n a. Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - this option will allow you to view\nof missing volunteer's hours for sites where the ien is greater than 999999\n the components of the KIDS build.\n c. Backup a Transport Global - this options doesn't need to be\n run because all of the routines in this patch are new.\n d. Compare Transport Global to Current System - this options doesn't\n need to be run because all components in this patch are new.\n\n 3. Use the Install Package(s) option and select the package\n ABSV*4.0*35.\n\n 4. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\nin the VOLUNTEER DAILY TIME file. It also address the problem of corrupted\n Install? YES//', respond NO.\n\n 5. When prompted 'Want KIDS to INHIBIT LOGONs during the\n Install? YES//', respond NO.\n\n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//', respond YES.\n\n Enter options you wish to mark as 'Out Of Order': ABSV MIGRATION MENU \n Voluntary Data Migration Menu\ndata in the VOLUNTARY MASTER file and corruption in Print Template\n \n Enter options you wish to mark as 'Out Of Order': \n \n Enter protocols you wish to mark as 'Out Of Order':\n\nABSVM PARKING EXPORT for the VOLUNTARY MASTER file, 503330.\n \n\n
\nBackup of ABSV*4.0*45 on Apr 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n \nSee National Patch Module\n\n
\n This patch accomplishes the following:\n 4. System will now assume all dates are past dates.\n \n5. Prohibits the deletion of combination assignments except during the\nmonth of October.\n \n 6. When merging two timecards, the system will now prompt to another.\n \n 7. Adds two new reports to the Timekeeping Reports Menu. Both reports\nprovide monthly data by organization. One report prints all organizations\nfor one month, the other prints up to 10 organizations for the time period\n \nrequested.\n \n 8. Corrects an error caused when a volunteer tries to log in without a\nvalid combination assignment.\n \n 9. Gives a warning when the birth date entered is less than five years\nold. Questions user on the validity of the date.\n \n 10. Adds an ID Number field to all transmission related occasional hours\nprintouts.\n 1. Corrects errors in Patch ABSV*4*7, including a missing routine,\n \n 11. Allows user to print a list of the sign-in codes for all active\nvolunteers in the system.\n \n 12. Changes the program to complete the conversion to the year 2000.\nchecksum. \n \n 2. Deletes two mail groups left in Patch ABSV*4.0*7 \n \n 3. Corrects the UNSCHEDULED,VOLUNTEER meal ticket print.\n \n\n
\nThis patch corrects a 'syntax' error which occurs when print VAVS\nRepresentative labels for station number containing an alpha character.\n\n
\nVoluntary Service Directory File Data Update\n\n
\nThis patch corrects the following problems:\n 1. Failure to clean-up incomplete entries in the Daily Log File\n (503330.1)\n 2. Assumes past date when entering award date information.\n 3. Adds Data Dictionary changes for files 503336, 503339.2,\nand 503339.3.\n 4. Corrects Label Printing Problems\n\n
\nThis patch corrects the following problems:\n \n 5. Allows user to automatically schedule auto log-in transfer to\noccur daily.\n \n 6. Allows user to selectively shutdown auto log-in terminals. For this\noption to work, the terminal MUST be defined in the DEVICE file.\n \n 7. Adds fields to Site Parameters to prevent asking LUNCH question\nduring auto log-in on Saturdays, Sundays and Holidays selectively.\n \n \n 8. When halting auto log-in terminals for multiple divisions, the\n'site' question is asked each time.\n 1. Adds Support for National Veterans Games\n \n 2. Corrects problem with labels for National Directory\n \n 3. Adds routine to clear National Directory\n \n 4. Assumes user has privileges when job is queued.\n\n
\nVoluntary Service Directory File Data Update\n\n
\nThis patch updates the Sex field of the master to the new ages for boys\nand girls.\n\n
\nThis package is designed to automate the volunteer time keeping activities\nat a VA medical center.\n \n\n
\n During the New Clinic Visits option, some QUASAR users may see an \n others do not? Recent FileMan patches clean up the utilities \n for creating and entering data in sub-files (FILE^DICN and DIE).\n We believe the QUASAR problem shows up after the FM patches are \n installed.\n \n The legacy QUASAR code used old methodology for this call and \n needed to be updated. Patch ACKQ*2*3 corrects this problem.\n \n What is the impact of this bug on QUASAR data? Depending on how \n the Select DIAGNOSTIC CONDITION prompt is answered, the patient \n additional prompt while entering the DIAGNOSTIC CODE(s). This \n diagnostic history in the A&SP PATIENT file (#509850.2) may not \n be complete. It is advisable to use the Inquire - A&SP Patient \n option to update the diagnostic history.\n additional prompt is Select DIAGNOSTIC CONDITION. The prompt \n occurs after the diagnostic code has been entered into the A&SP \n CLINIC VISIT file (#509850.6) and while the A&SP PATIENT file's \n (#509850.2) diagnostic condition multiple (patient diagnostic \n history) is being updated.\n \n Why do some QUASAR users see this additional prompt, while \n\n
\n The AMIE C&P AUDIO worksheet (#1305) format has been \n reconfigured. The worksheet headings and organization have \n changed. Patch ACKQ*2*4 corrects this for QUASAR.\n \n Additionally, this patch replaces all "W *7" code with "W $C(7)"\n in nine (9) QUASAR routines and in the ACKQAS VISIT ENTRY input\n template on the A&SP CLINIC VISIT file (#509850.6). \n\n
\n When a C&P exam is adequated in QUASAR, the results are \n transmitted to the AMIE C&P software. If the transmission \n attempt to AMIE fails and the data is not successfully sent, \n QUASAR currently does not leave the visit in a "signed off on, \n but not adequated" state. This patch corrects this problem by \n leaving the visit in a "signed off on, but not adequated" state \n so that re-transmission can take place.\n\n
\n This patch corrects a problem reported in NOIS CTX-0997-70706.\n After installing ACKQ*2*5, sites reported that the adequator \n signature block does not print on the AMIE report. Patch \n ACKQ*2*6 corrects this problem.\n\n
\nY2K COMPLIANCE PATCH\n\n
\nSee description of patch on FORUM.\n\n
\nQuality: Audiology and Speech Pathology Audit and Review (QUASAR) is\ndesigned to capture patient treatment and workload information for\nAudiology and Speech Pathology clinic visits.\n\n
\nThis patch will correct to problem with in QUASAR\nthat allows the user to create a new visit for\ndeceased patients.\n\n
\nINCORRECT DIAGNOSTIC CODE DISPLAY\n\n
\nInterface of Medical Devices with QUASAR and the DALC.\n\n
\nThis patch will correct a problem with broken pointers.\nAssociated Remedy\nHD147036 - Quasar Patch ACKQ*3*9 - Amendments for Scheduling \n\n
\nThis patch addresses the following issues:\n needs to have the default changed from "NULL" to "YES".\n \n 1. From the New Clinic Visits [NEW CLINIC VISITS ACKQAS VISIT ENTRY] \n menu option, when checking out a patient that has the Combat \n Classification, the prompt does not display allowing the user to \n answer the Combat questions for the visit.\n \n 2. At each episode of care, the prompt to determine if the care\n provided is related to the combat experience of the OEF/OIF veteran\n\n
\nAs a follow up to patch LEX*2.0*64 modifications are necessary to \nall references of the newly deleted fields and use of the \ncorresponding API's is required to acquire the necessary \ninformation.\n\n
\nThis patch addresses one issue:\n \nThis patch will update all direct file reads to the ICD DIAGNOSIS (#80) \nfile,CPT MODIFIER (#81.3) file, and the CPT FILE (#81) file in the Quasar \napplication to the new associated API's.\n\n
\nICD-10 Remediation patch for QUASAR\n\n
\nFix event capture error's.\n\n
\nThis patch fixes the problem with updating diagnosis histories in the \nA&SP Patient file (#509850.2).\n\n
\nThis patch fixes problems with the updating of the Problem List via the \nPCE interface.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThe Audiometric module was developed in conjunction\n \n \n 509850.9<tab>AUDIOMETRIC EXAM<tab>^ACK(509850.9\n \n2. New options introduced with this patch:\n \n ACKQROES3<tab>Audiogram Display\n Uses new remote procedure call: ACKQAUD1. See Option file\n entries to see other existing XWB, XUS, and DDR RPCs\n accessed.\n \n(1) [ACKQROES3E] Enter or edit the data into file 509850.9. When\n ACKQROES3E<tab>Audiogram Data Edit\n Uses new remote procedure calls: ACKQROES and ACKQAUD2.\n See Option file entries to see other existing XWB, XUS,\n and DDR RPCs accessed.\n \n3. New remote procedure introduced with this patch:\n \n ACKQAUD1: returns array of data for last 2 exams\n Uses routines: ACKQAG01 and ACKQAG06\n \n signed, this transmits the data to the DDC for use with ROES 3\n ACKQAUD2: returns array of data for a specific exam\n Uses routine: ACKQAG02\n \n ACKQROES: transmits data to DDC & returns msg#, DDC msg#,\n error# and error msg.\n Uses routines: ACKQAG03, ACKQAG04 and ACKQAG05\n \nInstallation Instructions:\n=========================\n \n Custom Hearing Aid orders.\nThis patch was created with Kernel V8 KIDS.\n \n1. This is a completely new installation, so it will not affect\n any current ROES 3 users or others on the system. You do not\n need to restrict users from signing on or lock any options.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS package onto your system.\n \n3. You DO NOT need to stop Taskman or the background filers. None\n \n of the routines require mapping, so mapping does not need to be\n disabled.\n \n4. Using the Kernel Installation and Distribution System menu\n (KIDS), you may choose the following options prior to \n installing this patch:\n \n a) All routines are new, so there should be no need to Backup\n the Transport Global.\n \n(2) [ACKQROES3] View the audiogram generated from that data and\n b) Again, this is an all new module, so there should be no\n need to Compare Transport Global to the Current System.\n \n c) Verify Checksums in the Transport Global. This option will\n allow you to ensure the integrity of the routines that are\n in the transport global.\n \n5. Use the 'Install Package(s)' option under the 'Installation'\n menu. Installation should only take a few minutes.\n \n print VA form 10-2364.\n a) Select INSTALL NAME: ACKQ*3.0*3\n \n b) When prompted 'Want KIDS to Rebuild Menu Trees Upon\n Completion of Install?' YES// respond "NO"\n \n c) When prompted 'Want KIDS to INHIBIT LOGONs during the \n install?' YES// respond "NO".\n \n d) When prompted 'Want to DISABLE Scheduled Options, Menu\n Option and Protocols?' NO// respond "NO".\n \n \n e) When prompted 'Want to MOVE routines to other CPUs?' YES//\n respond "NO".\n \n6. Unzip the Audiogram.zip file containing the executables\n ACKQROES3.EXE and ACKQROES3E.EXE onto the network. They must\n reside in the same directory in order for the practitioner to\n view the audiogram display(ACKQROES3) from the audiogram edit\n program (ACKQROES3E). [An alternative is to place the\n executables on each client computer, referencing it in the\nNOIS references addressed in this patch\n application path of the CPRS Tools menu.]\n \n7. Assign Broker options ACKQROES3 and ACKQROES3E to selected ASPS\n staff members. This will provide access to the options and\n allow them to startup successfully when the user logs in.\n \n8. Add the ACKQROES3 and ACKQROES3E applications to the CPRS Tools\n menu. [See the separate installation guide for further\n instructions.]\n=======================================\nwith the Remote Order Entry System (ROES 3.0) at the VA Denver\nThere are no NOIS or E3R references.\n \nTest Sites\n==========\nDenver\nNew York\nColumbia\nMountain Home\nAtlanta\nNashville\nDistribution Center. [Prior ROES 2 VistA applications may be run\n \nFTP Software and Documentation\n==============================\nThis patch will be distributed in a PackMan message through the\nNational Patch Module and should be obtained from there.\nThe KIDS build for this patch is ACKQ*3.0*3.\nKIDS File (ACKQ*3.0*3): ACKQ_3_P3.KID\nZIP file of executables: AUDIOGRAM.ZIP\n \nDocumentation:\nconcurrently with the new system during the switchover]\n ACKQ_3_P3_IG.PDF Installation guide\n ACKQ_3_P3_SG.PDF Security guide\n ACKQ_3_P3_TM.PDF Technical manual\n ACKQ_3_P3_UM.PDF User manual\n \nNote: The .PDF and .ZIP files are binary files and must be \ntransferred in binary, not ASCII mode. These files can be read\nusing the Adobe Acrobat Reader program.\n \nThis patch contains the following enhancements:\nThis patch includes two new options. These two options are only\n==============================================\n \nThe Audiometric Exam Module (ACKQ*3.0*3) provides new\nfunctionality for ASPS, to simplify and enhance the entry, display\nand use of information obtained during the Audiometric exam of\na patient. This module is comprised of two distinct application\nfunctions: Audiogram Edit function and the Audiogram Display\nfunction.\n \nRecords are stored in a local QUASAR global (#509850.9).\n available in the Windows environment. Please refer to the \nWhen signed they are also transmitted from this application to the\nDenver Distribution Center (DDC) through the VistA MailMan system\nfor inclusion with orders for hearing aids and repairs when\nordered through the VistA Remote Order Entry System (ROES)\npackage.\n \nThe 'Audiogram Edit' function is a Windows based software\napplication that allows clinicians to enter, edit or view the\naudiometric exam information from the Computerized Patient\nRecord System (CPRS) Tools menu. Using this function, a new\nInstallation Guide for instructions on setting these options up.\naudiogram record can be entered, or an existing one can be edited.\n Once signed, the edited data can only be viewed.\n \nThe 'Audiogram Display' function is a Windows based software\napplication that allows clinicians to view a patient's audiogram\nfrom the CPRS Tools menu. It can also be called from the \nAudiogram Edit application, if they exist in the same directory\nand folder. This function presents the clinical information in a\nstandard format recognized within the hearing industry. The user\nhas a choice of viewing just the last audiogram, or the last two\n \nin the file.\n \nROUTINE SUMMARY\n===============\nThe second line of all listed routines will look like:\n <tab> ;;3.0;QUASAR AUDIOMETRIC MODULE;**3**;11/01/02\n \nCHECK^XTSUMBLD results:\n \nACKQAG01<tab>N/A<tab>9433779<tab>3\nThe 2 new GUI options are:\nACKQAG02<tab>N/A<tab>14506291<tab>3\nACKQAG03<tab>N/A<tab>4940176<tab>3\nACKQAG04<tab>N/A<tab>133577359<tab>3\nACKQAG05<tab>N/A<tab>1171193<tab>3\nACKQAG06<tab>N/A<tab>12622668<tab>3\n \nTechnical Description\n=====================\n \n1. New file introduced with this patch:\n\n
\nUpdates for Code Text Versioning. \n\n
\n \nThe Audiometric Exam Module was developed in conjunction with the Remote\n \n 3. Comments\n A comment box has been added to the Edit application where the clinician\n can enter up to 300 characters of text. A checkbox has been inserted\n directly above the comment area for use if the clinician would like to\n automatically insert the words "NOT ADEQUATE FOR RATING PURPOSES". This\n text will be saved to the file and will be imported into VA form 10-2364.\n \n 4. Update VA form 10-2364\n VA form 10 2364 has been modified to reflect the changes made to the form\nOrder Entry System (ROES 3.0) at the VA Denver Distribution Center(DDC)\n since the release of patch ACKQ*3.0*3. The comment section of the form is\n no longer editable.\n \n 5. Color Changes\n Color has been removed from the data entry boxes. This allows for a\n cleaner presentation and makes more of the screen available for the edit\n boxes.\n \n 6. Retransmit Audiogram\n In the Edit application, a menu option has been added to allow\nand is only available to run in the Windows environment. The application\n retransmission of a signed audiogram. This is necessary to transfer the\n speech, word and other readings that were not a part of the original\n transmission.\n \n 7. Removing Audiogram\n In the Edit application, a menu option has been added to allow deletion\n of a signed audiogram. This became necessary because, in their haste to\n enter audiograms under heavy workload pressures, users sometimes entered\n audiograms under the wrong patient and the error was not discovered until\n after transmission. This would then become a problem when data would be\ncan be installed completely from this patch, if ACKQ*3.0*3 was not\n on duplicate systems for the wrong patient. After installing this patch,\n when a local signed audiogram is deleted, a message with identifying\n information is sent to the DDC to delete the record there also.\n Clinicians should use utmost caution in both entering and removing\n audiograms.\n \n 8. File Changes\n Numerous fields were added to the AUDIOMETRIC EXAM file to provide the\n additional data needed for diagnostic and reporting purposes. The data\n type of many fields was changed at the request of the national program\ninstalled. Users are encouraged to consult the full Installation Guide\n office to more efficiently handle the text and tags required in the\n fields. Many that were numeric are now free text. Refer to the\n CHANGES/ADDITIONS TO FILE section for more detailed information.\n \n 9. New Fields on Edit Pages\n The new editable fields (bullet 8) and data type screening were added to\n the Edit program.\n \n 10. Masking Change\n Masking is no longer referenced in the fields with an '*', but will\nreferenced below if AKCQ*3.0*3 was not installed. If ACKQ*3.0*3 was \n instead be indicated by a non-zero numeric value in the 'Masking Level'\n field. Prior instances of the data without a masking level will continue\n to display the '*' sign.\n \n 11. No Response Change\n The symbol for 'No Response'(+) will now be stored in the text field with\n the numeric value.\n \n 12. No Testing, No Masking\n 'CNM', 'CNT', 'DNT' and 'FLAT; are now accommodated in the appropriate\n \n text fields in the file as well as in the Edit program.\n \n 13. Transducer Type\n Users can now indicate if testing was done via inserts or headphones.\n This is also displayed on the 10-2364.\n \n 14. Eliminate Duplicate Presentation and Material\n One selection of the Presentation Method and Material are now applicable\n to all of the Word Recognition tests, via a single drop down list.\n \ninstalled, then installing the KIDS build and copying the new executables \n 15. Tympanogram Type and Other Test\n Tympanogram Type and 'Other Test' types have been added to the Acoustic\n Immittance page.\n \n 16. Claim Number\n The Claim Number has been added to the Edit form so that it can be\n included on VA form 10-2364.\n \n 17. Maximum Value Change\n Maximum values allowed have been updated and associated 'Hints' have been\n \n adjusted.\n \n 18. Hints\n It is now possible for the user to inactivate or reactivate the hint\n feature.\n \n 19. Clinician Title\n The title of the clinician and location will now show on the display.\n \n 20. Presentation Method\nover the original executables of the same name will complete\n CD and Tape have been consolidated into a single Recorded type.\n \n 21. About Box\n An 'About' box was added to the main forms to comply with VistA\n convention.\n \n \n \nSoftware and Documentation Retrieval\n====================================\nThis patch addresses several issues that came up at the VAMC stations as\nthe install.\n \n The software and documentation for this patch can be found in the\n following [ANONYMOUS.SOFTWARE] directories:\n \n Preferred Address\n ----------------------\n First available FTP server download.vista.domain.ext\n \n Specific Field Office FTP address\n --------------------- -----------\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n File Name Description Format FTP Protocol\n ----------------- ------------- ------ ------------\n \n ACKQ_3_P12_RN.PDF Release notes PDF Binary\n ACKQ_3_P12_IG.PDF Installation Guide PDF Binary\n ACKQ_3_P12_UM.PDF User Manual PDF Binary\nREMEDY ticket(s) addressed in this patch\n ACKQ_3_P12_TM.PDF Technical manual PDF Binary\n ACKQ_3_P3_SG.PDF Security guide PDF Binary\n ACKQ_3_P12.KID KIDS build KIDS ASCII\n AUDIOGRAM_P12.ZIP Executables ZIP Binary\n \n \n \n Test Sites\n ==========\n Columbia(SC)\n ========================================\n Las Vegas\n Miami\n Tennessee Valley\n New York\n Salisbury\n Fayetteville AR\n \n \nROUTINE SUMMARY:\n================\n HD000000063808\n \nThe following is a list of the routines included in this patch.\nThe second line of each of these routines now looks like:\n \n<tab>;;v 3.0;QUASAR AUDIOMETRIC EXAM MODULE;**[patch list]**;11/01/02\n \n \n CHECK1^XTSUMBLD results\n \nRoutine Name Before Patch After Patch Patch List\n HD000000063675\n============ ============ =========== ==========\nACKQAG01 49470887 69211169 ** 3,12 **\nACKQAG02 61779051 62617084 ** 3,12 **\nACKQAG03 11574717 11560534 ** 3,12 **\nACKQAG04 65019411 68097423 ** 3,12 **\nACKQAG05 1840641 19012760 ** 3,12 **\nACKQAG06 47277438 63053336 ** 3,12 **\nACKQAG08 n/a 38815781 ** 12 **\n \n \n HD000000063875\n \n INSTALLATION INSTRUCTIONS:\n ==========================\n \n Installation of this patch will take about 5 minutes. Additional\n time will be needed if the GUI applications have been installed on\n individual client machines or the location of the applications on the\n network has changed. Users need not be off the system when applying this\n patch, but it should be installed during non-peak hours to minimize\n disruption to users.\n HD000000063682\n \n 1. On the KIDS menu under the 'INSTALLATION' menu, use the following\n options as desired:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n \n 2. On the KIDS menu under the 'INSTALLATION' menu, use the following\n option to install the patch:\n \n Install Package(s) (ACKQ*3.0*12)\n \n 3. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES//", respond 'NO'.\n \n 4. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//"\n respond 'NO'.\n \n 5. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond 'YES'.\n Overview of Remedy ticket(s):\n Options to disable:\n ACKQROES3\n ACKQROES3E\n \n 6. When prompted 'Delay Install (Minutes): (0-60): 0//; respond '0'.\n \n 7. Following the installation of the KIDS build, the system will\n immediately run routine ACKQAG08. This will move any existing\n 'No Response' or 'Masked' tags into the appropriate threshold fields.\n \na result of the initial release of the Audiometric Exam Module (patch\n ----------------------------\n 8. At this point the two revised executables (ACKQROES3.EXE and\n ACKQROES3E.EXE) should be copied over all existing copies on the\n network or client machine. Add the VistA menu options for any new\n application users and setup on their CPRS Toolbar as necessary, as\n detailed in the INSTALLATION GUIDE.\n \n 9. We do not anticipate any need to reinstall this patch. However, it\n may be reinstalled if necessary.\n Problem: When a user without context accessed the Edit Module, they were\n allowed to enter the application and view the screens. They were not able\n to actually edit the data.\n \n Solution: The application [ACKQROES3E.EXE] was modified to exit and halt\n the application if the user did not have the appropriate VistA\n application assigned to create context.\n \n Associated Remedy Ticket: HD000000063808\nACKQ*3.0*3). These changes have been made to the GUI(Windows based)\n \n \n \n -----\n Problem: Sites encountered a Null Subscript at EN2+4^ACKQAG02 when\n entering a new record and cancels out of entering the date and time of\n the exam.\n \n Solution: A fix is applied in routine ACKQAG02 and in the record setup\n to give the appropriate error message and exit the application if a valid\nEnter/Edit(ACKQROES3E.EXE) and Display(ACKQROES3.EXE) applications in the\n date and time are not entered.\n \n Associated Remedy Tickets: HD000000063675 and HD000000063875\n \n -----\n Problem: Some error messages or message prompts were coming up behind\n other screens. The only way for them to show up was to select the\n application from the bottom task bar.\n \n Solution: Most of the messages in the Audiogram Edit application are now\npackage for both the CPRS Toolbar and Desktop versions, as well as to the\n enclosed in code to send them to topmost position and after the message\n ends, to restore the previous topmost setup. This may not be a complete\n solution, but available documentation indicates it should help, if not\n eliminate the problem from this application.\n \n Associated Remedy Ticket: HD000000063682\n \n -----\n \n \nVistA part of the application. The VistA part includes the file data\nThis patch contains the following enhancements:\n===============================================\n \nThe Audiometric Exam Module provided new functionality for Audiology and\nSpeech Pathology Services(ASPS), to simplify and enhance the entry,\ndisplay and use of information obtained during the Audiometric exam of a\npatient. This module is comprised of two distinct application functions:\n Audiogram Edit function [ACKQROES3E.EXE]\n Audiogram Display function [ACKQROES3.EXE]\n \ndictionary, Remote Procedure Calls and routines.\nRecords are stored in the local AUDIOMETRIC EXAM file (^ACK(509850.9).\nWhen signed, the records are also transmitted from this global to the DDC\nthrough the VistA Mailman system. At the DDC, data from these records is\nincluded with orders for hearing aids and repairs when the orders are\nplaced through the VistA Remote Order Entry System (ROES) package.\nThey may also be viewed remotely from the ROES Patient Information screen\nof the ROES web application.\n \nACKQ*3.0*12 implements the following changes:\n \n \n 1. Removal of Buttons\n In both audiogram GUI applications, the buttons previously on the screens\n have been replaced by menu options at the top of the form.\n \n 2. Loop to Another Patient or Record\n In both applications, a menu option (Get New Record) has been added to\n allow the user to go to another record without exiting the application.\n If accessing through CPRS, record selection is limited to the current\n patient. From the Desktop application, users may select another patient\n or go to another record for the same patient.\n\n
\n \nTEST INSTALL VERSION 3\n\n
\nQuality: Audiology and Speech Pathology Audit and Review (QUASAR)\nis designed to capture patient treatment and workload information\nfor Audiology and Speech Pathology clinic visits.\n\n
\n This patch corrects several miscellaneous data entry problems that\n NOIS #LON-0596-61759 reported a duplicate screen display when using\n like to place out of order, enter the following: \n ECPAT Enter/Edit Patient Procedures\n ECBATCH Batch Enter Data by Patient\n ECBATCH PROC Data Entry (Batch) by Procedure\n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n CPUs. Alternately, you can wait until the installation is complete \n and move the routines listed in the ROUTINE INFORMATION section \n to all systems. \n the "Batch Data Entry by Patient" or "Data Entry (Batch) by Procedure"\n options. After selecting a procedure, from the listing of available\n procedures, the procedure name is echoed back plus printing the name\n two additional times. The additional printing of the procedure names\n has been eliminated.\n \n Problem 3.\n NOIS #LON-0596-61762 reported that when using the "Batch Data Entry\n by Patient", if an "^" is entered at the prompt "Is this information\n have been identified.\n correct?" the user is not exited from the option. The user is then\n prompted to "Select Next Patient". If a patient is selected the list of\n selected patients is numbered incorrectly. Now when an "^" is entered\n at "Is this information correct?" a screen displayed alerting the user\n that "**NOTE** No action taken. You must re-enter the correct patient\n and procedure data that has NOT been filed during this session. ". The\n user is then prompted to "Select Patient".\n \n Problem 4.\n After confirming a category using the "Local Category (Enter/Edit)"\n \n option the screen will display "??". The option correctly updated the\n category name but was not updating the date created information when \n the category was initially entered.\n \n Problem 5.\n NOIS STC-0696-40797 reported when creating an Event Code Screen the\n user is prompted with "Is the following information correct? YES// "\n when the data is listed previously on the screen. The display\n message has been changed to read "Is this information correct? YES// ".\n \n Problem 1.\n Problem 6.\n The routines ECED and ECDSSYN killed the variable ^TMP("ECPRO")\n incorrectly. The correct method killing ^TMP("ECPRO",$J) has\n been inserted. This will prevent procedure lists from being\n deleted by mistake.\n \n Problem 7.\n When using the data entry options and selecting a procedure from\n the listing displayed, an <UNDEF> error could occur if "01" was\n entered instead of "1". This error has been corrected.\n NOIS #OKL-0596-72092 reported an <UNDEF> error at SELC+1^ECBEN2A.\n \nROUTINE SUMMARY: \n==================\n \n The following routine is included in this patch. The second line of the\n routines will look like:\n \n <tab>;;2.0; EVENT CAPTURE ;**[patch list]**;8 May 96\n \n CHECK^XTSUMBLD results:\n The variable EC1 was undefined. All data entry options have been\n \nRoutine Name Before Patch After Patch Patch List\n \n ECBEN2A 16143247 17248422 1\n ECBEP1B 6124470 15735188 1\n ECDSS2 3173984 3165330 1\n ECDSSYN 11622115 11631282 1\n ECED 9546738 9549509 1\n ECED2 9397816 9471887 1\n ECED3 14007833 14074752 1 \n reviewed to ensure that the variable EC1 is defined.\n ECSCR 5323033 5255260 1\n \nINSTALLATION INSTRUCTIONS: \n==========================\n \n This patch may be loaded during regular hours. It mainly affects users of\n the Event Capture software. Installation will take less than 5 minutes. \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu\n and answer NO to the question 'Shall I preserve what is on disk in a \n separate back-up message ?'. Answer YES to the prompt 'Want to \n \n Continue with Load? YES//' \n 2. Review your mapped set. If any of the routines listed in the \n ROUTINE INFORMATION section are mapped, they should be \n removed from the mapped set at this time. None of the patched \n routines are on the recommended mapping list. \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n 4. From this menu, you may elect to use the following options \n (when prompted for INSTALL NAME, enter EC*2.0*1): \n a. Backup a Transport Global - this option will create a backup \n Problem 2.\n message of any routines exported with the patch.\n b. Compare Transport Global to Current System - this option will \n allow you to view all changes that will be made when the patch \n is installed.\n c. Verify Checksums in Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the transport global. \n 5. Use the Install Package(s) option and select the package EC*2.0*1. \n 6. When prompted 'Want to DISABLE Scheduled Options and Options? \n YES//', respond YES. When prompted to select the options you would \n\n\nRefer to the patch description for patch EC*2*10 in the NPM for a\ncomplete description of this patch.\n\n
\nThis patch addresses 1 issue:\n \n 1. This patch will update the EC NATIONAL PROCEDURE (#725)\n file by adding 5 new procedures.\n\n
\nThis patch will update the EC NATIONAL PROCEDURE (#725) file by adding 67 \nnew procedures.\n\n
\nThis patch will update the EC NATIONAL PROCEDURE (#725) file.\n\n
\nThis patch will update the EC NATIONAL PROCEDURE (#725) file.\n\n
\nUPDATE TO EC NATIONAL PROCEDURE (#725) FILE\n\n
\nSee the NPM for complete information on patch EC*2*11.\n\n
\nThis patch addresses the following three (3) remedy tickets:\n 1. <SYNTAX>GET+2^ECOB error.\n 2. Remove Files (#720) and (#720.2) flagged for deletion in EC*2*5.\n 3. An active DSS Unit with inactive Event Code Screens is presented as\n selectable in ECS GUI data entry.\n\n
\nThis patch will inactivate any DSS units that are set to send \nno records and have an inactive/invalid stop code\n\n
\nUPDATE TO EC NATIONAL PROCEDURE (#725) FILE\n\n
\nThis patch will inactivate any DSS units that are set to send \nno records and have an inactive/invalid stop code\n\n
\nFY18 EC Procedure Reason (#720.4) File Update\n\n
\n This patch will inactivate any DSS Units in the DSS UNIT file (#724) with\n the SEND TO PCE field (#13) set to 'Send No Records' and have an\n inactive/invalid Stop Code.\n\n
\nThis patch will update the EC NATIONAL PROCEDURE (#725) file.\n\n
\nEC PROCEDURE REASON (720.4) FILE UPDATE\n\n
\n This patch will inactivate any DSS Units in the DSS UNIT file (#724) with\n the SEND TO PCE field (#13) set to 'Send No Records' and have an\n inactive/invalid Stop Code.\n\n
\nMID-FY18 UPDATE TO EC NATIONAL PROCEDURE (#725) FILE\n\n
\n This patch will update the EC PROCEDURE REASON (#720.4) file by\n adding 1 new procedure reason to the file:\n \n CHAP WHOLE HEALTH\n\n
\n This patch will update the EC NATIONAL PROCEDURE (#725) file by \n adding 30 new procedures, inactivating 15 existing procedures,\n changing 16 CPT codes, and changing 16 procedure names in the file.\n\n
\nMid-FY19 UPDATE TO EC NATIONAL PROCEDURE (#725) FILE\n\n
\nThis patch will update the EC NATIONAL PROCEDURE (#725) file by adding \neight (8) new procedures, inactivating eleven (11) existing procedures, \nchanging four (4) CPT codes, and changing six (6) procedure names in the \nfile.\n\n
\nThis patch updates thirty-five (35) procedure codes to reflect Fiscal Year\n2020 Mid-Year changes, effective April 1, 2020.\n\n
\nThis patch updates two thousand three hundred ninety two (2,392) procedure\ncodes to reflect Fiscal Year 2021 changes, effective September 1, 2020.\n\n
\nThis patch EC*2.0*151 inactivates any DSS Units in the DSS UNIT file\n(#724) with the SEND TO PCE field (#13) set to 'Send No Records' and \nhave an inactive/invalid Stop Code.\n \nThis patch is being released along with SD*5.3*752 that provides Fiscal \nyear 2021 updates to the CLINIC STOP (#40.7) file. When inactivating \nstop codes in CLINIC STOP (#40.7) file, the DSS UNITS (#724) file also\nneeds to be updated. Both patches will be bundled together with the\nScheduling patch being the primary.\n\n
\nBackup of EC*2.0*153 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch updates forty four (44) procedure codes to reflect Fiscal Year \n2021 mid-year changes, effective April 1, 2021.\n\n
\nBackup of EC*2.0*152 on Jun 17, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee Patch Description.\n\n
\nThis patch, EC*2.0*155, inactivates any DSS Units in the DSS UNIT \n(#724) file with the SEND TO PCE (#13) field set to 'Send No Records' \nand have an inactive/invalid Stop Code.\n \nThis patch is being released along with patch SD*5.3*787, that provides\nprovides Fiscal Year 2022 updates to the CLINIC STOP (#40.7) file. When\ninactivating stop codes in CLINIC STOP (#40.7) file, the DSS UNIT (#724) \nfile also needs to be updated. Both patches will be bundled together\nwith the Scheduling patch being the primary.\n\n
\nThis patch updates twenty one (21) procedure codes to reflect Fiscal Year \n2022 changes, effective October 1, 2021. \n\n
\nNational Procedure Update (File #725).\n\n
\nThis patch updates twenty-two (22) procedure codes in the EC NATIONAL \nPROCEDURE FILE (#725) to reflect Fiscal Year 2023 changes, effective\nOctober 1, 2022. \n\n
\nThe patch addresses two (2) issues: \n \n1. This patch corrects the Name for 2 EC National Numbers that were \nupdated by EC*2.0*157.\n \n2. It changes 2 CPT codes for 2 EC National Numbers that were \nunavailable for the 2023 EC National Procedure file (#725) update.\n\n
\nSee patch description.\n\n
\nEvent Capture FY23 Sustainment.\n\n
\nThis patch updates eleven (11) procedure codes to reflect Fiscal Year \n2024 changes, effective October 1, 2023.\n\n
\nPatch EC*2.0*163 inactivates any DSS UNIT (#724) file record with the SEND\nTO PCE (#13) field set to 'Send No Records' and have an inactive/invalid\nStop Code.\n \nThis patch is being released along with patch SD*5.3*856, that provides\nFiscal Year 2024 updates to the CLINIC STOP (#40.7) file. When\ninactivating stop codes in CLINIC STOP (#40.7) file, the DSS UNIT (#724) \nfile also needs to be updated. Patch SD*5.3*856 will need to be installed\nprior to patch EC*2.0*163.\n\n
\nSee patch description.\n\n
\nINACTIVATE DSS UNITS USING INACTIVATED STOP CODES\n\n
\nThis patch updates forty six (46) procedure codes to reflect Semi Fiscal\nYear 2024 changes, effective April 1, 2024.\n\n
\nSee patch description.\n\n
\nFY25 EC NATIONAL PROCEDURE FILE (#725) UPDATE\n\n
\nNational Procedure Update (File #725).\n\n
\nEC*2*21 patch description in FORUM. Issued as a 'patch for patch' for EC*2*20.\n\n
\nNational Procedure Update (File #725).\n\n
\nThis patch updates entries in the EC NATIONAL PROCEDURE file (#725).\n== ========== ======\n \n169 CH062 COMMUNION\n170 CH063 COMPUTERIZED SPIRITUAL ASSESSMENT\n171 CH064 FIFTH STEP\n172 CH065 FUNERAL\n173 CH066 PATIENT EDUCATION-ADVANCED DIRECTIVES\n174 CH067 GROUP ON SPIRITUALITY EDUCATION\n175 CH068 PC-SEXUALITY\n176 CH069 PC-SPIRITUAL ASSESSMENT\n \n177 CH070 ADVANCE DIRECTIVE CONSULTATION\nThe procedure "PC-THEODICY-PT SPIRITUAL", national number "CH058",\nwill be changed to "PC-THEODICY-UNFAIRNESS OF GOD/LIFE 14091".\nThe internal entry number is 58. This patch will not install if entry\nnumber 58 is not "PC-THEODICY-PT SPIRITUAL".\n \nNew entries follow:\nIEN NATIONAL # NAME\n\n
\nUpdate Event Capture System, file #721, to keep track of a new classification\nMilitary Sexual Trauma (MST).\n\n
\nEvent Capture CPT Modifier Project. See patch on FORUM for more details.\n\n
\nSee patch description for details.\n\n
\nUPDATE ECS TO STORE MULTIPLE ICD-9 CODES\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nEC GUI - see description on FORUM.\n\n
\n*** Patient Care Encounter (PCE) Version 1.0 should be installed \nthe ECS extract fix. Targeted release date for patch ECX*2*23\n This field will indicate the default clinic associated with workload \n performed by this event code screen. This clinic will be used as the\n hospital location for the EC system workload records for PCE filing\n purposes. This clinic will also be the source for the stop code\n (DSS ID) needed by PCE. This field should be edited for each event\n code screen that will send to PCE. The clinic associated with the\n event code screen will be displayed to users during the data entry\n processes.\n \nEVENT CAPTURE PATIENT file (#721): The DATE/TIME OF PROCEDURE field\nis May 10, 1997.\n(#2) is modified to require time for every record entered. New\nfields which have been added to this file are described below.\nThe data entry options Enter/Edit Patient Procedures [ECPAT],\nBatch Enter Data by Patient [ECBATCH], and Data Entry (Batch) by\nProcedure [ECBATCH PROC] are modified to ask users these questions\nor update the fields automatically when appropriate. \n \n Field 19 - PCE CPT CODE \n The Current Procedural Terminology (CPT) code for the patient \n procedure performed. \n \n \n Field 20 - ICD-9 CODE \n The ICD-9 (diagnosis) for the procedure performed. This data \n element is required for all workload records. \n \n Field 21 - AGENT ORANGE \n This field will be used to indicate if this procedure is treating \n a VA patient for a problem that is related to Agent Orange Exposure.\n Data is Y if this patient was exposed to agent orange, N if not, \n or U if unknown. \nNOTE: Your site should NOT run the ECS extract, after installing\n \n Field 22 - RADIATION EXPOSURE \n This field will be used to indicate if this procedure is treating \n a VA patient for a problem that is related to Ionizing Radiation \n Exposure. Data is Y if this patient claims exposure to ionizing \n radiation, N if not, or U if unknown. \n \n Field 23 - ENVIRONMENTAL CONTAMINANTS \n This field will be used to indicate if this procedure is treating \n a VA patient for a problem that is related to Environmental \nEC*2*4, until the DSS Extracts patch ECX*2*23 is released and\n Contaminant Exposure. Data is Y if this patient claims exposure \n to environmental contaminants, N if not, or U if unknown. \n \n Field 24 - SERVICE CONNECTED \n This field will be used to indicate if this procedure is treating \n a VA patient for a service connected problem. Data is Y if this \n patient is service connected or N if not service connected for this \n treatment.\n \n Field 25 - SENT TO PCE \ninstalled on your system. Any ECS extract your site generated\n This field flags data that has been sent from Event Capture to PCE.\n \n Field 26 - ASSOCIATED CLINIC \n This is the clinic associated with this record. \n \n Field 27 - DSS ID \n The DSS ID, formerly stop code, associated with this patient record.\n \n Field 28 - VISIT \n This is the visit associated with this patient procedure. This\nprior to installing EC*2*4 is not affected. The ECS extract will only\n field is a pointer to the VISIT file (#9000010).\n \n Field 29 -IN/OUTPATIENT \n The status of the patient when this event occurred. The code "I" \n represents an inpatient event or an "O" represents an outpatient \n event occurred. \n \n Field 30 - PCE DATA FEED \n The field contains the EC data formatted to feed the Patient Care \n Encounter (PCE) software. \nbe impacted AFTER EC*2*4 is installed.\n \n Field 31 - SEND TO PCE \n This flag controls the EC system data that is ready to send to PCE. \n If this record should be sent to PCE, this flag will be set with a \n date. \n \n Field 32 - CHECKOUT D/T \n This field contains the checkout date and time of this procedure. \n The checkout date and time is generated when the nightly background \n job is run. \n \n \n Field 33 - REASON\n This field contains the reasons why this patient record was\n not sent to the Patient Care Encounter (PCE) software. This\n field is automatically populated during the PCE filing\n process.\n \nNEW CROSS REFERENCES: This patch includes a new MUMPS cross reference\nin the EVENT CAPTURE PATIENT file (#721). The AD cross reference on the\nSEND TO PCE field (#31) controls the filing of the data that is ready\n \nfor PCE. \n \nNEW OPTIONS: This patch adds two new options to collect, maintain, and\nreport the data filing to PCE. \n \n Nightly Data Feed to PCE [EC NIGHT] \n This option controls the routine that sends Event Capture data \n to Patient Care Encounter (PCE) software nightly. The EC system \n data is stored in the EVENT CAPTURE PATIENT file (#721). EC data \n that has been flagged to send to PCE will be picked and sent when \n before installing this patch. \nThis patch implements new functionality in the Event\n this routine is run. This routine should run nightly, therefore \n the rescheduling frequency is 1D. The time to queue this option \n to run should not conflict with system backup. \n \n PCE Data Summary [ECPCER] \n This option is exported on the Event Capture Reports [ECREPS] menu. \n This Event Capture data summary lists, by patient, key information \n that has been sent to the Patient Care Encounter (PCE) software. \n The date and time of the procedure, procedure name listed in PCE, \n volume of procedures sent, CPT and ICD-9 codes, associated clinic \nCapture (EC) package to allow the non-interactive filing of\n and DSS ID (formerly stop code), and the provider of care are listed \n on this report. \n \nHELP FRAMES: The following help frame is created. \n \nECPCER \n This Event Capture data summary lists, by patient, key information \n that has been sent to the Patient Care Encounter (PCE) software. \n The date and time of the procedure, procedure name listed in PCE, \n volume of procedures sent, CPT and ICD-9 codes, associated clinic \nthe EC system workload data to the Patient Care Encounter\n and DSS ID (formerly stop code), and the provider of care are listed \n on this report. \n \nSUMMARY OF THE PCE FILING PROCESS: \n \nEach DSS Unit should be edited to update the SEND TO PCE information.\nIf a DSS Unit is marked to send data to PCE, then when creating new\nevent code screens within this DSS Unit or editing existing event\ncode screens defined within this DSS Unit, a new prompt for an\nASSOCIATED CLINIC is displayed.\n(PCE) software. By utilizing this EC to PCE filing process,\n \nAn associated clinic should be defined for each event code screen\ndefined for DSS Units marked to send data to PCE. For entering new\nevent code screens, use the Event Code Screens (Create) [ECSCREEN]\noption. For existing event code screens, use the Procedure\nSynonym/Default Volume (Enter/Edit) [ECDSSYN] option. These\nassociated clinics will be displayed to users during data entry\nprocesses. \n \nThe data entry options Enter/Edit Patient Procedures [ECPAT],\nthe need for duplicate data entry into both packages diminishes\nBatch Enter Data by Patient [ECBATCH], and Data Entry (Batch)\nby Procedure [ECBATCH PROC] are updated to ask users the PCE\nrequired prompts. The DATE/TIME OF PROCEDURE field (#2) now\nrequires time as part of every procedure date. Each patient\nrecord entered must include a diagnosis code (ICD-9), an\ninpatient/outpatient indicator, and an active clinic. Users\nmanually entering this data must answer diagnosis, determine an\ninpatient or outpatient status, and accept the default clinic\nor select an active clinic. If it is an outpatient encounter,\nusers are also prompted to answer agent orange exposure,\nwhile supporting the transmission of workload data to\nionizing radiation exposure, environmental contaminants exposure,\nand related service connection. \n \nAfter the PCE prompts are answered, all appropriate patient\nrecords are formatted to file the data with PCE. This formatted\ndata string is stored in the PCE DATA FEED field (#30). The\nflag to file this record is then set in the SEND TO PCE field\n(#31). These fields exist in the EVENT CAPTURE PATIENT file\n(#721). The nightly scheduled Nightly Data Feed to PCE [EC NIGHT]\noption will file the data with PCE and store a pointer to the\nnationally supported databases. Outpatient data entered into\ncorresponding visit created in the VISIT file (#9000010).\nPatient data records that have been filed with PCE and are\nlater edited or deleted in the EC system will automatically\nsend an update to PCE. For those records that should be filed\nto PCE but are not sent due to missing or incorrect data will\nstore a reason in the REASON file (#33).\nEC, passed through PCE, updates the National Patient Care\nDatabase (NPCBD) at the Austin Automation Center (AAC). All\ndata entered into EC is passed to the Decision Support System\n \n(DSS) at the AAC using the VISTA DSS Extracts software.\n \nThis is a mandatory patch and MUST be installed. If your site does\nnot anticipate sending Event Capture data to PCE, this patch still\nMUST be installed. The only difference your users will see is both\nDATE and TIME are now required to enter workload data into Event\nCapture. They will never see the additional prompts required for\nthe filing of data to PCE.\n \n \nThree patches are required before installing this patch. Event\nThree NOIS messages are addressed in this patch. The AMIS Reports\nare modified to correct the problems reported in the following NOIS: \n \n ATG-1196-30490 AMIS Report Producing Incorrect Totals \n LON-0896-60887 AMIS Summary - Dropping Procedure \n BRX-0297-11162 Original Default Volume \n \n \nThe data dictionary changes made by this patch are listed below,\nfollowed by a summary of the PCE filing process and patch\nCapture patches EC*2*1, EC*2*2, and KERNEL patch XU*8*44. \ninstallation instructions. \nEC NATIONAL PROCEDURE file (#725): A new field called CPT\n(field #4) is added which should be edited for each local\nprocedure entry that sends workload data to PCE. A Current\nProcedural Terminology (CPT) code is required to pass EC\nprocedural data to PCE. Only the local EC procedures\nrepresenting workload that your sites wants sent to PCE\nrequire an associated CPT code. The option Local Procedure\n(Enter/Edit) [ECDSS PROCEDURE] is modified for users to edit\nthis field for local procedures and is exported as part of the\n \nEvent Capture Management Menu [ECMGR].\n \nMany new nationally defined procedures added in this patch\ninclude Speech Pathology and Blood Bank. Products for Social\nWork and Chaplain service have been completely redefined. A\ngeneric CPT code is associated with each existing active\nnational procedure entry. Use the National/Local Procedure\nReports [ECDSS1] option on the Management Reports [ECDSRPT] menu\nto review the new and updated entries in this file. \n \nThis patch will impact the DSS Extracts ECS Feeder Key report\n Field 4 - CPT \n The Current Procedural Terminology (CPT) code equivalent for this \n national or local procedure. Each EC recognized procedure must \n have an associated CPT code for filing with PCE. \n \nDSS UNIT file (#724): The DATA ENTRY DATE/TIME DEFAULT field\n(#11) is modified to accept N for NOW or X for NONE as a date/time\ndefault. T for TODAY is no longer a valid date/time default.\nAll existing DSS Units using T for TODAY will be updated to use\nN for NOW during the installation process.\nand the ECS extract. A DSS Extracts patch, ECX*2*23, is currently\n \nOne new field, SEND TO PCE (field #13), is added which must\nbe edited in order to activate the filing process. The option\nDSS Units for Event Capture (Enter/Edit) [ECSECT] is modified\nto edit these fields and is exported with the Event Capture\nManagement Menu [ECMGR].\n \n Field 13 - SEND TO PCE \n This field controls the method of sending data, by DSS Unit, to the \n PCE software. If this field contains an O, only outpatient data, for \nunder development that addresses the ECS feeder keys for FY97 and\n this DSS Unit, will be filed with PCE. If the field contains an A, \n all records, for this DSS Unit, can be filed with PCE. If the field \n contains an N or is null, no filing will occur. This field is exported \n null. \n \nEC EVENT CODE SCREENS FILE (#720.3): This file contains a single new field\nthat allows the site to associate a clinic with an event code screen.\nThis field is described below.\n \n Field 55 - ASSOCIATED CLINIC\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nUpdate Event Capture System, file #721, to keep track of a new classification\nMilitary Sexual Trauma (MST).\n\n
\nSee the patch description for EC*2*6 on the patch as generated from the\npatch module.\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nNational Procedure Update (File #725).\n\n
\nPlease see the National Patch Module for details of the enhancements included \nin this patch.\n\n
\nNational Procedure Update (File #725).\n\n
\n\n\n
\nThis patch addresses NOISes related to the Event Capture\nProvider Summary Report.\n\n
\nThis patch addresses NOISes related to the Event\nCapture GUI and roll-n-scroll.\n\n
\nNational Procedure Update (File #725).\n\n
\nSee patch description in EC*2*5 as generated from the patch module.\n\n
\nThis patch corrects the output for the Event Capture Provider (1-3) Summary\nReport.\n\n
\nPlease see the National Patch Module for details of the enhancements included \nin this patch.\n\n
\nNational Procedure Update (File #725).\n\n
\nA request was made to update the VistA Event Capture EC NATIONAL\nPROCEDURE (#725) file.\n\n
\n\n\n
\nThis patch provides a fix to the Event Capture Provider Summary\nReport.\n\n
\nThis patch addresses NOISes related to the Event Capture GUI and\nroll-n-scroll.\n\n
\nThis patch provides an update to Event Capture file #725.\n\n
\nEC*2.0*9\nAdd new entries to file #725.\n\n
\nThe patch updates EC National Procedure File 725.\n\n
\nAppointment Type changes to Regular.\n\n
\nThis patch updates EC 725 file.\n\n
\nThis provide the fix to couple of Remedy Tickets.\n\n
\nThis patch updates EC 725 file.\n\n
\nThis patch provides a fix to the ECS Records Failing Transmission to PCE\nReport.\n\n
\nThis patch updates EC 725 file.\n\n
\nThis patch updates file EC NATIONAL PROCEDURE (#725).\n\n
\nThis patch proveds a fix to the DSS Unit Workload Report.\n\n
\nSee the patch description in the National Patch Module for complete\ninformation on this patch.\n\n
\nThis patch updates file 725.\n\n
\nThis patch provides a fix to the Provider 1-7 Summary Report.\n\n
\nThis patch updates National Procedure File 725.\n\n
\nThis patch provides a fix to two EC GUI Reports.\n\n
\nThis patch provides a fix to the EC Procedure Reason Report.\n\n
\nCORRECT ERROR ON EVENT CODE SCREENS WITH CPT CODES REPORT\n\n
\nThis patch updates the file #725 EC NATIONAL PROCEDURE.\n\n
\nThis patch fixes several remedy tickets.\n\n
\nThis patch provides a fix to several remedy tickets.\n\n
\nUpdate to EC National Procedures File #725.\n\n
\nThis patch provides an update to National Procedure file 725#.\n\n
\nRefer to the patch description for patch EC*2.0*95 in the National Patch\nModule (NPM) on FORUM.\n\n
\nThis patch provides an update to National Procedure file 725#.\n\n
\nThis patch provides an update to National Procedure file 725#.\n\n
\nThis patch provides an update to the National Product File 725.\n\n
\nThis patch made changes to routine ECRRPC for VistA Application\nDevelopment OED.\n\n
\nThis patch provides a fix to the active associated clinics (file #44) s\nsearch routine ASCLN^ECUMRPC1.\n\n
\nEvent Capture 2009 Enhancements\n\n
\nThis patch updates the EC NATIONAL PROCEDURE (#725) file: it adds 14 new \nprocedure records, inactivates 3 existing procedure records, and updates \nnames and codes for 7 others.\n\n
\nSee the patch description in the National Patch Module for complete\ninformation on this patch.\n\n
\nThis patch contains modifications for the Recent Visit functionality.\n\n
\nThis patch will resolve issues with CPRS's Event Capture Patient Data\nSummary Report and with the Event Capture GUI form not updating the \npatient's status correctly.\n\n
\nThis patch will resolve issues with an Event Capture Timeout when started\nfrom CPRS (Computerized Patient Record System), the Event Capture GUI exit\nscreen, and Event Capture not auto-populating the location of the user's\nlast used information.\n\n
\nThis patch will update the EC NATIONAL PROCEDURE (#725) file.\n\n
\nThis patch will resolve issues with an Associated Clinic selection bug,\nmultiple syntax errors occurring in routine ECOB, and a bug not allowing\nthe answering of classification questions for inpatient procedures.\n\n
\nThis patch addresses 1 issue:\n \n1. Updates the EC NATIONAL PROCEDURE (#725) file by\n inactivating 112 existing procedure records\n\n
\nThis patch will update the EC NATIONAL PROCEDURES (#725)\nfile by inactivating 46 existing procedures, adding 4\nnew procedures, changing 4 CPT codes, and changing 27\nprocedure names in the file.\n\n
\nThis patch addresses 2 issues:\n \n 1. This patch will update the MEDICAL SPECIALTY (#723) file by\n adding 1 new medical specialty.\n \n 2. This patch will update the EC NATIONAL PROCEDURES (#725)\n file by adding 1 new procedure.\n\n
\nThe Event Capture module provides a mechanism to track and account for\npatient workload performed that is not recorded in any existing DHCP\npackage. These procedures and services are associated with the patient\nto whom they were delivered, the provider rendering the service or\nprocedure, and the workload unit responsible for delivering the service.\n\n
\nEvent Capture is that portion of the Decision Support System (DSS) which\nhas been designed to capture the workload for those areas which do not\ncurrently have a software system which may be extracted. Such areas as\nChaplain, Canteen, and non-associated clinics can use Event Capture to\ntrack their workload.\n\n
\nPCE Update + Miscellaneous Enhancements\n\n
\nThis is HBH*1.0*17\n\n
\nThis is HBH*1.0*16\n\n
\nThis is HBH*1.0*14\n\n
\nThis is HBH*1.0*19, Race/Ethnicity Mods, & Routine 2nd Line Correction\n\n
\nHBH*1.0*21, Patient Days of Care Report & Report Updates\n\n
\nHBH*1.0*22, Shorten SSN to Last Four on Reports \n\n
\nHBH*1.0*24, Medical Foster Home (MFH) Functionality \n\n
\nBuild for ICD-10 Class 1 Remediation\n\n
\nThis patch addresses one Home Based Primary Care (HBH) issue:\n \n1. The BUILD/VERIFY TRANSMISSION FILE option currently lacks the \nfunctionality to prevent test patient data from being built into the HBHC \nTRANSMIT (#634) file for transmission to Austin. A request was made for \nthis functionality to be implemented. \n\n
\nTotal Visits by Date Range Report [HBHCRP21] CPT Code Omission Update\n\n
\nPatch HBH*1.0*07\n\n
\nA user has reported an undefined error in FileMan when editing the COUNTY \nCODE (#25) field in the HBHC MEDICAL FOSTER HOME (#633.2) file. This \nissue is caused by the code in the INPUT/OUTPUT TRANSFORM for this field. \nPatch HBH*1.0*29 will update the Data Dictionary by removing the variable \nD0 from all KILL commands preventing the error from occurring.\n\n
\nPatch HBH*1*30 addresses the following issue:\n \n1. HBHC Medical Foster Home File (#633.2), Caregiver Date of Birth \nField (#26) is hard coded to only accept dates between 1/1/20-4/30/87. \n\n
\nBackup of HBH*1.0*33 on Jul 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe patch addresses one (1) issue:\n \n1. An error can occur when running the HBPC Medical Foster Home \n (MFH) Rate Paid Report in the Home Based Health Care application\n in VistA. The report my error out when using the Active or All\n patient selections when listing Current or All rates paid.\n\n
\nBackup of HBH*1.0*32 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch includes the following enhancements:\n3. Various other minor changes to the HBHC logic. Refer to the full patch \n description in FORUM for more information.\n \n1. Modify the VistA-HBPC module to increase the number of providers that \n can be assigned a unique Provider Number.\n \n2. Modify the VistA-HBPC module to add the site number with suffix-level \n granularity to patient-level HBPC data for each patient admission to an\n HBPC Program.\n \n\n
\nThis patch addresses the following issue:\n \nThe "Expanded Program Census Report" might generate an error when \nencountering a patient with no visits for the specified date range. The \nerror is caused by variable HBHCSTOP not being initialized as a fail-safe \nin case the patient's data does not meet certain criteria.\n\n
\nThis patch addresses one issue:\n \nIn certain instances, when creating a new HBHC admission with the VistA \noption Evaluation/Admission Data Entry [HBHCADM], the default home state \nthat is displayed for the patient's STATE CODE is not the same as the \npatient's home state.\n\n
\nPatch HBH*1.0*08\n\n
\nRefer to the patch for the patch description.\n\n
\nThis is the beta version of patch 10 of the HBHC v1.0 software, with patches\n1-9 installed. \n\n
\nThis patch will delete & re-create all FY98 visit information in HBHC VISIT\n(632) file from Outpatient Encounter (409.68) data. Corresponding old file\ninformation is also cleaned up in files: Transmit (634), Transmit History\n(634.6), Admission Errors (634.1), Visit Errors (634.2), Discharge Errors\n(634.3).\n\n
\nPatch HBH*1.0*11\n\n
\nThis is the beta version of patch 13, vT1.\n\n
\nThis is HBH*1.0*15\n\n
\nThis package contains HBH v1.0 Patch 4 routines, which include inits.\n\n
\n This package is used to update NLT files consisting of nationally\nstandardized terms and procedure names. Any new procedure of term\ncreated by the site must use terms already defined by the NLT package.\n Responsibility of the contents of these files has been granted to\nPathology & Laboratory Medicine Service.\n\n
\nThis patch addresses 3 issues. The first problem occurs when using the \noption Enter New New Equipment Requests [PRCN NX NEW]. The second problem\nis an undefined error that occurs when editing replacement information. \nThe third problem is an undefined error occurring when requests are \nprocessed in the option Create 2237 (PPM) [PRCN NX PPM 2237].\n\n
\nUsers are unable to delete Replacement Items on the Turn-In Requests using\nthe EDIT EQUIPMENT TURN-IN REQUEST [PRCN TURN EDIT] Option.\n\n
\nThis patch addresses one problem with a string too long error at\nthe routine line CMR+2^PRCNCMR:4 when the user was running the\nApprove Equipment Turn-In Request (CMR) [PRCN TURN CMR APP] option.\n\n
\nThere are several menu options that are not working as advertised.\n\n
\nPatch PRCN*1.0*16 is a modification of input template [PRCNTIPED] to \nallow for the deletion of all Replacement Items. The current template is\nonly allowing the deletion of the last item within the Edit Turn-in\nTransaction (PPM) option.\n\n
\n1. Equipment Request will not update to COMPLETE status\n\n
\nThis patch will correct an undefined variable error that is produced when \nmaking a call to Fileman v22.\n\n
\nThis patch addresses undefined variable errors in the Equipment/Turn-In \noccurs.\n\n2. NAS-0697-31502\n\nWhen a request for replacement equipment is edited and the quantity is \nincreased the user is asked to enter the replacement equipment for the line \nitem they choose, after the item is entered the program fails with an \nundefined variable.\n\n3. MEM-0697-70758\nRequest package. The following NOIS are addreessed by this patch.\n\nWhen a request is sent to Engineering and the request is updated to include \ntraining, a vendor must be entered into the ENG. TRAINING VENDOR (#55) \nfield, when this is done the program attempts to find that vendor in the \nVENDOR (#440) file and stuff the pointer into the ENG TRAIN VENDOR PTR \n(#55.5) field. The lookup was being done in the wrong file so an undefined \nerror would occur each time the lookup tried to reconcile the vendor.\n\n1. REN-0497-60517\n\nWhen a priority is placed on a new equipment request by a CMR Official and \nthe request is sent to PPM for review, during the review process PPM will \nanswer NO to the IS THIS NX EQUIPMENT prompt, they then enter a reason why \nthis is not NX equipment. Immediately following this, an undefined error \n\n
\nThis patch addresses a problem when printing the PRCN NX SERVICE REPORT. \nA problem was uncovered during testing of this patch that has been \naddressed. When asked to enter O for one service and a lowercase o was \nentered it was ignored and all services printed.\nThe following NOIS is addressed by this patch.\n \n1. MIW-0497-42110\n \nWhen printing the Service Priority Report [PRCN NX SERVICE REPORT] to a \nprinter, and the report is greater than one page in length, the report \nstops at page one. Printing the report to the screen functions properly.\n \n\n
\nExtract Equipment Turn-In user counts by role.\n\n
\nThis patch will stop the undefined error occurring in routine PRCNPPM.\n\n
\nThis patch addresses several issues. The first issue is the option\nat routine PRCNTIRQ when a user performs an up-arrow exit out of the list\nof items in a request while using the option Edit Equipment Turn-In\nRequest [PRCN TURN EDIT].\nCreate 2237 (PPM) [PRCN NX PPM 2237] is failing to set the transaction\nnumber items when the 2237 is being created. The second issue is an\nundefined error which occurs in routine PRCNREQE when running the\noption Edit Equipment Requests (PPM) [PRCN NX PPM EDIT]. The third\nissue is a null subscript error which logs at routine PRCNOTHR when a\nuser uses the option Review Equipment Requests (Concurring Official)\n[PRCN NX CONCUR] to select an equipment request transaction which\nis not set up for him to review. The last issue is an undefined error\n\n
\nThe Equipment/Turn-In Request module.\n\n
\nThis module allows for the request and approval of non-\nexpendable equipment and for the turn-in on non-expendable\nequipment.\n\n
\nSee LEX*2*1 in the Patch Module.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \n I15579788FY17 - Modifier ZB with code Q5102\nincluded in this patch.\n \n REQUEST/INCIDENTS:\n =================\n \n R13705179FY17 - Modifier JW with J codes J0120-J9999\n R15738393FY17 - Modifier JW with J codes J0120-J9999 (dupe)\n R15120982FY17 - Modifiers TC and 26 with code 77065, 77066 and 77067\n\n
\nPlease see the National Patch Module for details of the \nenhancements included in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the\nenhancements included in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nFinancial year 1999 update to ICD9 codes. Include in Lexicon.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nBackup of LEX*2.0*133 on Jun 02, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nBackup of LEX*2.0*134 on Jul 08, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nBackup of LEX*2.0*135 on Jul 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nThis the version LEX*2.0*13 release of the Lexicon file ^LEX incorporating\nthe CPT version 6.4 update.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nLEX*2.0*14\nLEXICON UPDATES\n\nThis patch includes amendments to some incorrect ICD9 codes and a change to \na CPT lookup routine to use API standards.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nLEX*2.0*15 CORRECTIONS TO LEXICON PACKAGE UTILITIES\nThis patch contains correction to faults in routines LEXA1,LEXA4 and LEXU\n\n
\nLEX*2.0*16 LEXICON CPT & HCPCS 2000 RELEASE\n\n
\nLEX*2.0*17 LEXICON ICD FY1999 & FY2000 RELEASE\n\n
\nLEX*2.0*18 UPDATE CPT AND HCPCS CODES FOR YEAR 2001\n\n
\nLEX*2.0*19 UPDATE ICD CODES FOR FISCAL YEAR 2002\n\n
\nSee Patch Module for LEX*2*2\n\n
\nLEX*2.0*21 UPDATE CPT & HCPCS CODES FOR FISCAL YEAR 2002\n\n
\nMilitary Treating Facilities 2nd QTR 2002\n\n
\nICD9 ANNUAL UPDATE FY 2003\n\n
\nCPT & HCPCS ANNUAL UPDATE FY 2003\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nSee Patch Module for LEX*2*3\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nThe Health Insurance Portability and Accessibility Act (HIPAA) stipulates \nthat diagnostic and procedure codes used for billing purposes must be the \ncodes that were applicable at the time the service was provided. The\ndata supporting Code Sets (date-sensitive codes) for the ICD-9-CM \ndiagnostic classification system and the Diagnosis Related Groups (DRG)\nGrouper are exported in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\n ICPT*6.0*38 Informational patch installed with LEX*2.0*53\n \nPlease see patch LEX*2.0*52 for install instructions\nincluded in this patch. This patch is part of a multi-package \ndistribution and includes the following patches installed in\nthe following order:\n \n LEX*2.0*52 Fixes for Lexicon, ICD and CPT problems\n ICPT*6.0*37 Routine ICPTMOD and ICPTMOD2\n ICD*18.0*29 Routine ICPTCODE and #80 Data Dictionary changes to file #80\n LEX*2.0*53 FY08 1st quarter ICD/CPT update\n\n
\nPlease see the National Patch Module for details of the enhancements\n ICPT*6.0*38 Informational patch installed with LEX*2.0*53\n \nPlease see patch LEX*2.0*52 for install instructions\nincluded in this patch. This patch is part of a multi-package \ndistribution and includes the following patches installed in\nthe following order:\n \n LEX*2.0*52 Fixes for Lexicon, ICD and CPT problems\n ICPT*6.0*37 Routine ICPTMOD and ICPTMOD2\n ICD*18.0*29 Routine ICPTCODE and #80 Data Dictionary changes to file #80\n LEX*2.0*53 FY08 1st quarter ICD/CPT update\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nCode Set FY08 3rd Qtr Update\n \nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch. Please see patch ICD*18.0*57 for install\ninstructions for this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch. \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch. \n\n
\nPlease see the National Patch Module for details of the enhancements\n 1 LEX*2.0*86\n 2 ICD*18.0*67\nincluded in this patch.\n \nThis a Multi-Package KIDS Distribution consisting of a KIDS hostfile\ncontaining two patches with the following install order: \n \n LEX_2_86.KID Distribution:\n \n Order Patch\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch. \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch installs the UCUM file and associated APIs.\n\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThe Lexicon is a dictionary of medical and biomedical terminology. This\nterminology is represented by major concepts which can be expressed in \nnumerous forms (concept, synonyms or lexical variants). These terms are \nmapped to coding schemes such as ICD, SNOMED or CPT. The Lexicon can be\nsearched by keywords or by code.\n\n
\nThe Lexicon contains medical and biomedical major concepts. Each major \nand computer systems.\nconcept can be expressed in numerous forms (major concepts, and synonyms \nor lexical variants to the major concepts). These expressions are updated\nusing VA terminology sources. These sources include the various disciplines\nnot well represented to date (i.e., Social Work, Nursing, etc.) and the\nLexicon itself through the capturing of terms not found within the file.\n \nUpdates to the Lexicon will be simultaneously sent to all sites, providing\nthem with the ability to communicate medical concepts across disciplines \n\n
\nThe SAGG (Statistical Analysis of Global Growth) Project will produce data\nenabling all VAMCs and IRMFOs to make various statistical analysis studies\nof global growth patterns within the DHCP environment.\n\n
\nAssociated patches: XU*8*121\n \nThis patch is being released by Capacity Management (CM) to allow\nthe Statistical Analysis of Global Growth (SAGG) Version 1.8 software\npackage to collect disk capacity information from the sites.\n \nAll DSM, MSM and OpenM-NT sites are instructed to install this patch.\n \nThis patch, in conjunction with Kernel patch XU*8*121, will support the\ncollection of disk capacity information from the following operating\nsystem platforms: DSM and OpenM-NT.\n \n \n \nInstallation:\n=============\n \nProvided that the 'SAGG Master Background Task' [KMPS SAGG REPORT] is not\ncurrently running, this installation can be performed at any time of the\nday with minimal disruption to users. Installation should not take longer\nthan 10-15 minutes.\n \nSubject: Collect Disk Capacity Information\n 1. DSM and MSM sites - You will need to diable any routines within \n the KMPS* namespace.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. As this install only affects the SAGG Master Background Task, you\n do not have to inhibit users from login into the system.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the 'Install\nCategory:\n Package(s)' option and select the package KMPS*1.8*1.\n ==========\n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', you can respond with NO.\n \n 7. DSM and MSM sites - after the patch has installed, rebuild your map\n set if necessary.\n \n The KMPS* namespaced routines are NOT recommended to be mapped. \n - Routine\n \nDescription:\n============\n\n
\nDescription: \nAll DSM, Cache for Windows NT and Cache for OpenVMS sites are instructed\n MON-0702-53239. \n \nInstallation Steps:\n===================\n \nProvided that the 'SAGG Master Background Task' [KMPS SAGG REPORT] is not \ncurrently running, this installation can be performed at any time of the day\nwith minimal disruption to users. Installation should not take longer than\n10-15 minutes. \n \nto install this patch.\n 1. Review the mail members of the KMPS-SAGG and KMP-CAPMAN mail groups\n with the FileMan Inquiry option. A pre-install routine will attempt\n to move mail members from the KMPS-SAGG mail group to the \n KMP-CAPMAN mail group.\n \n Any mail members that are not automatically moved will need to be \n entered manually with FileMan into the KMP-CAPMAN mail group after\n completion of the patch installation process.\n \n The patch will delete the KMPS-SAGG mail group during the patch \n \n installation process.\n \n 2. DSM sites - You will need to disable any routines within the KMPS*\n namespace. \n \n 3. Download the KIDS file KMPS1_8_2.KID from the ANONYMOUS.SOFTWARE\n directory of either Albany, Hines or the Salt Lake OIFO to the\n appropriate directory on your system.\n \n 4. Use 'Load a Distribution' option on the KIDS 'Installation' menu,\nThe original 'Status of SAGG Collection Routines' [KMPS SAGG STATUS] \n and enter: KMPS1_8_2.KID\n \n Provide the necessary directory path to the file if needed.\n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n Verify Checksums in Transport Global \noption has been renamed as the 'Check SAGG Environment' option. In \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n 6. As this install only affects the SAGG Master Background Task, you \n do not have to inhibit users from login into the system. \n \n 7. On the KIDS menu, under the 'Installation' menu, use the 'Install \n Package(s)' option and select the package KMPS*1.8*2. \n ==========\naddition to providing the previous information regarding the SAGG \n \n 8. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', you can respond with NO. \n \n 9. DSM sites - after the patch has installed, rebuild your map set if\n necessary. \n \n The KMPS* namespaced routines are NOT recommended to be mapped. \n \n 10. Review the contents of the KMP-CAPMAN mail group with the FileMan \ncollection routines, this option will now check the status of SAGG patch \n Inquiry option to ensure that the members of the KMPS-SAGG mail \n group have been properly copied.\ninstallation at the site.\n \nThe local mail message that is generated when the the SAGG background \n============\nroutines complete their collection process has been enhanced to \naccommodate the expanded volume set names found on the Cache for OpenVMS \nand Cache for Windows NT platforms. In addition, the local message will\nrecommend that the background job be run over the weekend hours if the job\nis started during the weekday.\n \nThe pre-install routine of this patch will move mail members from the\nKMPS-SAGG mail group to the KMP-CAPMAN mail group. The KMP-CAPMAN\nmail-group was created with the release of the Resource Usage Monitor\n(RUM) package. All SAGG notification messages will start utilizing the\n \nKMP-CAPMAN mail group. Any mail groups within the MAIL GROUP file that\nhave KMPS-SAGG as a MEMBER GROUP will have the KMPS-SAGG entry removed.\n \nThis patch will remove the KMPS-SAGG mail group from the MAIL GROUP file.\nThe 'Edit KMPS-SAGG Mail Group' [KMPS SAGG MAIL] option will be deleted.\nUse the 'Capacity Management Mail Group Edit' [KMP MAIL GROUP EDIT] option\nto change the the membership of the mail group that will receive package\nnotification messages.\n \nThis patch will now allow SAGG to accept alphanumeric characters within \nThis patch is being released by Capacity Management (CM) to correct the\nthe site number. This problem had effected the MPI facility located in\nAustin.\n \nThis patch will enable the collection of hardware information from sites\nrunning DSM. The hardware information will consist of the hardware name \n(such as Compaq AlphaServer ES40) and the number of active cpu processors \ninstalled within each node.\n \nSOFTWARE RETRIEVAL\n \n'Invalid reverse-path specification' transmission error within the\nThe software patch is not being distributed through the National Patch \nModule. The patch is being distributed as a host file.\n \n Host file name: KMPS1_8_2.KID\n \nThis file contains patch KMPS*1.8*2\n \nSites may retrieve the patch directly using FTP from the \nANONYMOUS.SOFTWARE directory at the following OI Field Offices:\n \nStatistical Analysis of Global Growth (SAGG) Version 1.8 software package.\n Albany: ftp.fo-albany.domain.ext\n Hines: ftp.fo-hines.domain.ext\n Salt Lake City: ftp.fo-slc.domain.ext\n \nThe following file will be available:\n \n File Name Description\n --------- -----------\n KMPS1_8_2.KID Host file containing KIDS software distribution\n \nThis patch release will also allow the collection routines to run on Cache\n * NOTE: Use ASCII mode when transferring the .KID file\n \n \n Checksum\nRoutine Old New 2nd Line\n \nKMPSENV n/a 45940 **2**\nKMPSGE 20004053 9750122 **1,2**\nKMPSLK 14824425 10632243 **1,2**\nKMPSPRE n/a 6696549 **2**\nfor OpenVMS platforms.\nKMPSPST n/a 1162953 **2**\nKMPSUTL 17505897 15926854 **1,2**\nKMPSUTL1 n/a 4494004 **1,2**\n \nNOTE: KMPSENV is an environment check routine used during patch install.\n KMPSPRE is a pre-install routine used during patch install.\n KMPSPST is a post-install routine used during patch install.\n KMPSUTL1 is a new routine.\n \nChecksums calculated by CHECK^XTSUMBLD\n \n \nTest sites include Albany IOFO, Cincinnati, Cleveland, Connecticut HCS, \nFayettville AR, Forum, Maryland HCS, Tomah, Washington and White River.\n \nThis patch addresses the following NOISes:\n WIC-0301-41553, TOM-1201-41071, WIM-0302-22413, HIN-0602-41061, \n FAV-0602-71295, CIN-0602-41640, SBY-0602-31773, MOU-0602-32292,\n TAM-0602-32529, NOL-0702-70404, LAS-0702-60685, WPB-0702-30974,\n SLC-0702-50997, LEB-0702-21442, CHS-0702-41454, SDC-0702-61500,\n CMM-0702-N1799, LAH-0702-61988, ATG-0702-32243, COA-0702-22639, and\n\n
\nSee patch KMPS*1.8*3 in the National Patch Module on FORUM for complete \n \nAll DSM, Cache for Windows NT and Cache for OpenVMS sites are instructed \nto install this patch after the installation of Kernel patch XU*8*268.\n \nThis patch will allow the 'Check SAGG Environment' option to properly \ndisplay the current patches that are installed and required at the \nsite.\n \nThis patch will also change the way SAGG obtains the M version for DSM \nsites.\ninformation on this patch.\n \nThis patch is being released by Capacity Planning (CP) to update the \n'Check SAGG Environment' [KMPS SAGG STATUS] option after the installation\nof Kernel patch XU*8*268.\n \nNOTE: Kernel patch XU*8*268 must be installed BEFORE installation of this\n patch.\n\n
\nThis KIDS distribution contains Statistical Analysis of Global Growth\nPatch XU*8.0*90. If this distribution detects that the patch is not\ninstalled at your site, the installation process will stop. If this\noccurs, you will need to obtain and install Kernel Patch XU*8.0*90 and\nthen you may begin the installation of this product. The SAGG Project \nv 1.8 package will utilize the %ZOSVKS-namespace routines that were\ninstalled with Kernel Patch XU*8.0*90.\n \nThis distribution will move SAGG from the A1B5 namespace into the KMPS\nnamespace. The data within the old SAGG PROJECT file (#11120) will be\nmoved into new SAGG PROJECT file (#8970.1). The old file, routines,\n(SAGG) version 1.8. This version of SAGG can be installed over any\noptions and mail group will be deleted.\n \nThe 'SAGG Project Manager' menu [KMPS SAGG MANAGER] will be added to the\n'Capacity Management' [XTCM MAIN] menu.\nprevious versions of SAGG without any adverse problems.\n \nAll DSM, MSM and OpenM-NT sites are instructed to install this\ndistribution. Sites which had a pre-release of SAGG v 1.8 should also\ninstall this distribution.\n \nThis distribution is dependent on the previous installation of Kernel\n\n
\nSAGG v2.0\n\n
\nThe SAGG (Statistical Analysis of Global Growth) Project will produce data\nenabling all VAMCs and IRMFOs to make various statistical analysis studies\nof global growth patterns within the DHCP environment.\n\n
\nThis patch contains the changes necessary to support the following\nitems:\n \n1. Delete references to files 3, 6, and 16.\n2. Recode electronic signatures per IG instructions.\n3. Address IC concerns regarding suspense processing and restrictions.\n4. Archive and purge\n5. Correct errors relating to FM 21.\n\n
\nPatient Funds Diagnostic Patch\n\n
\nPatient Funds Migration Patch\n\n
\nThis patch is the 3rd and final patch in the 3 patch series used to \nmigrate a legacy Patient Funds package to the new VPFS Enterprise \napplication. Only use this patch if the migration process has been \nsuccessfully completed.\n\n
\nThis patch corrects the issue of the inability to add Guardian\ninformation to new patients added since Veteran's Personal Finance \nSystem (VPFS) was successfully installed.\n\n
\n \nand BAN-0697-11023\nThis patch contains the changes necessary to support the following\nitems:\n \n1. Remove routines previously used for conversion from 3/6/16.\n2. Run a File 16 conversion of the Provider Authorizing Restriction field,\nof file 470 which was inadvertantly missed in Patch PRPF*3.0*6.\n3. Modify the header used in the PRPF Archive tape.\n4. Corrects problems identified in NOIS - DAY-0697-40888, DAN-0697-42229\n\n
\nThis patch addresses two unrelated problems in the Patient Funds\npackage that resulted in the following NOIS:\n \n Overview of NOIS MESSAGES:\n -------------------------\n CLE-1097-42161 - re occasional display of info from Engineering (due to\nnon-initialization of print buffer)\n TOM-1297-41000 - re inclusion of inactive patients in some reports\n\n
\nThis patch prevents a possible future management error. The default and\n -------------------------\n \n MAR-0798-20011 How to restore unintentionally deleted records.\n \n \n \n There are no E3R messages associated with this patch.\nmaximum date for archieving and purging was "TODAY" when logically one\nshould be purging or archieving "recent" data. To prevent recurrance of\nthis, the maximum date for these two events has been changed to TODAY-400.\n \n \n \n Overview of NOIS MESSAGES:\n \n\n
\nREMOVE OBSOLETE OPTIONS AND INVALID FORM ENTRY\n\n
\nREMOVE OBSOLETE OPTIONS AND INVALID FORM ENTRY\n\n
\nPERSONAL FUNDS MULTIDIV\n\n
\nCORRECT BAL CHECK REPORT\n\n
\nThis package is the class I version of the Patient funds accounting system.\n\n
\nThis patch corrects the reference in routine ICPTAPIU\nfrom ^TMP($J,"W") to ^UTILITY($J,"W"). This error resulted in the CPT\nCOPYRIGHT message hanging.\n \nThis was reported in NOIS HAM-0697-20037.\n\n
\nThis patch updates the CPT code files for 2002.\ndate hard-coded\n \nICPTZ1\ndate hard-coded\n \nICPTZ1RA\ndate hard-coded\n \nICPTZ2\ndate hard-coded\n \n \nICPTZUP\ndate hard-coded\n \nICPTZSRT\ninclude CPT code in the list for Austin\nif only the short description is changed\n \nICPTZ3\nadded pattern check for 4N1A so AMA codes ending in "T" could be added\n(The balance of the description is for internal SD&D documentation only)\n \nICPTZM0\nsplit into ICPTZM0 and ICPTZM01\nvarious changes to update the Modifier file from Ingenix file\n(see also ICPTZM09)\n \nThese routines are included in the build:\n \nICPT612R (preinit)\nhost file names changed\nThese INHOUSE routines were changed to make this year's CPT update.\n \nICPT612E (environment check)\n \nICPTAPIU\nchanged $$NUM to convert codes ending in "T" or other letter to numeric \nvalue for use in sort ranges like the "M" cross reference on the range\n \nICPTCOD\nchanged $$CPT, $$CPTD and $$CODM for same reason\n \n \nICPTMOD \nchanged $$MODP for same reason \n \nICPTPRN\ndate hard-coded\n \nICPTSR1 thru ICPTSR24\nroutines that contain all revised CPT codes - all AMA codes included\nagain this year because we went back to using AMA file instead of\nIngenix file and short descriptions are different.\nICPTZ\nrewrote RDDSK label so could use AMA files\n \nICPTZ1R\n\n
\nThis patch updates the CPT code files for 2003 and updates an API.\nrewrote RDDSK label so could use AMA files\n \nICPTZ1R\ndate hard-coded\n \nICPTZ1\ndate hard-coded\n \nICPTZ1RA\ndate hard-coded\n \n \nICPTZ2\ndate hard-coded\n \nICPTZUP\ndate hard-coded\n \nICPTZSRT\ninclude CPT code in the list for Austin\nif only the short description is changed\n(The balance of the description is for internal SD&D documentation only)\n \nICPTZ3\nadded pattern check for 4N1A so AMA codes ending in "T" could be added\n \nICPTZM0\nsplit into ICPTZM0 and ICPTZM01\nvarious changes to update the Modifier file from Ingenix file\n(see also ICPTZM09)\n \nThese routines are included in the build:\nThese INHOUSE routines were changed to make this year's CPT update.\n \nICPT613R (preinit)\nhost file names changed\n \nICPT613E (environment check)\n \nICPTPRN\ndate hard-coded\n \nICPTSR1 thru ICPTSR3\n \nroutines that contain all revised CPT codes - all AMA codes included\nagain this year because we went back to using AMA file instead of\nIngenix file and short descriptions are different.\nFollow instructions found with 'CPT Update Process Guide for Software \nDevelopers' in MS Word format.\n \nICPTZ\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch. \n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\n ICPT*6.0*38 Informational patch installed with LEX*2.0*53\n \nPlease see patch LEX*2.0*52 for install instructions\nincluded in this patch. This patch is part of a multi-package \ndistribution and includes the following patches installed in\nthe following order:\n \n LEX*2.0*52 Fixes for Lexicon, ICD and CPT problems\n ICPT*6.0*37 Routine ICPTMOD and ICPTMOD2\n ICD*18.0*29 Routine ICPTCODE and #80 Data Dictionary changes to file #80\n LEX*2.0*53 FY08 1st quarter ICD/CPT update\n\n
\nThis patch adds HEALTH SUMMARY (GMTS) to the application group of\nfile 81 (CPT). This allows selecting of CPT codes for components\nwho wish to search for CPT codes. See the national patch module\nfor a complete description of ICPT*6*2.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch contains the 1998 CPT Update. Please refer to the patch\ndescription in NPM for further information.\n\n
\nThis patch contains the 1999 CPT Update. Please refer to the patch\ndescription in NPM for further information.\n\n
\nCorrect Short Names for codes 64623 and 82544, per NOIS RIC-0299-21517.\n\n
\nThis patch adds two new parameters to the formal list of a number of the\nAPIs in the CPT/HPCPS code package. The patch also deletes the CPT\nmodifier file, ^DIC(81.3, as part of the installation. After the patch\ninstallation, a global installation is needed to restore the CPT modifier\nfile.\n\n
\nThis patch updates the CPT Modifier file (#81.3) with 1999 OWCP Medical\nFee Schedule CPT/Modifier pairs.\n\n
\nThis patch contains the 2000 CPT Update. See the patch description in the\nNational Patch Module for details.\n\n
\nSee associated package documentation for description.\n\n
\nASU patch 1, USR*1.0*1. This patch removes broken subclass pointers\nfrom file 8930 the USR CLASS FILE.\n\n
\nASU patch 10, USR*1.0*10. This patch fixes a problem with an undefined\nwhen removing a user from class membership. See the National Patch Module\nfor a complete description.\n\n
\nASU patch 11, USR*1.0*11. Make data element 8930,.03 required. See the\nNational Patch Module for a complete description.\n\n
\nAUS patch 12. USR*1.0*12. This patch fixes the problem of entering\nthe Expiration date less than the Effective date. BUILD CAN BE FOUND\nON THE NATIONAL PATCH MODULE UNDER PATCH USR*1.0*12.\n\n
\nThis patch fixes the problem that was detected by patch USR*1.0*12. Field \nthat will be run during the Post-Install. This utility routine will print \nthe total number of corrections made to the global ^USR(8930.3).\n \nThis patch will also correct the problem of entering a Authorized/Subscription \nEffective date that is greater than the Expriation date. This change is \nchanging the routine USRU and the DD(8930.3) input transform on the .04 \nfield.\n\nA description of the this build can be found on the NATIONAL PATCH MODULE \nUNDER USR*1.0*13. \n.04 (Expiration Date) in global ^USR(8930.3) is a date only field and is \nshowing some invalid entries when a VA Fileman validate is run. When a \nclinician is terminated the USR CLASS MEMBERSHIP expiration field is \nautomatically entered with the termination date and time. This patch will \ncorrect the auto termination routine (USRLM) from including the termination \ntime when a clinician is terminated.\n \nThe process of correcting the global will be done with a utility (USRFIX) \n\n
\nThis patch corrects a potential problem of a bad cross reference in the \nwill display the cross reference being deleted and also a count.\n\nA description of this build can be found on the NATIONAL PATCH MODULE UNDER \nUSR*1.0*14.\n^USR(8930.3) global. The patch will change routine USRUMMBR to not abort \nwith a undefined variable USRCHNG when a bad 0 node pointer is discovered. \nInstead of the routine aborting it will send a email message to the user \nDUZ reflecting the bad pointer. The message will require forwarding to \na IRM representative at that site to review the USR(8930.3) global.\n\nAlso provided with this patch will be a Post-Install routine that will scan \nthe global and delete any bad AUC or ACU cross references. The Post-Install \n\n
\n\nA description of this build can be found on the NATIONAL PATCH MODULE UNDER \nUSR*1.0*16.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE UNDER \nUSR*1.0*17.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE under \nUSR*1.0*18.\n\n
\nFor the description of this build see patch USR*1*15 in the National Patch\nModule.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE under \nUSR*1.0*20.\n\n
\nASU patch 2, USR*1.0*2. This patch prevents "terminated" users from\nbeing selected for class membership. See the National Patch module for\na complete description.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE under \nUSR*1.0*21.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE under \nUSR*1.0*22.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE UNDER \nUSR*1*19.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch USR*1*23.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch USR*1*24.\n\n
\nThe description of this patch may be found under the National Patch Module \nunder USR*1.0*25.\n\n
\nThe description for this build can be found in the National Patch Module \nunder USR*1*27.\n\n
\nSee patch USR*1*30 in the National Patch Module.\n\n
\nThis patch corrects three issues with MEMBERHSIP by USER and USER CLASS.\nIn "List Membership by Class" only the Expired\nMember listed, not the Active Member.\n \n \nIssue #1-- When looking at Manage Business Rules you will notice \nwhen you hit "Add Rule" selection, notice the system defaults to \na TIU Object / TITLE when nothing was selected.\n \nIssue #2-- In "List Membership by User" the dates are \nlist from most current to oldest.\n\n
\nhis patch prevents incomplete business rules and duplicate business rules\ngenerated when the search string already matches a member in that class.\nfrom being created. It also corrects the document hierarchy issue that\nallowed user access to a note due to a rule at a higher level. This patch\nincludes updates to FileMan fields STATUS (#.02) and ACTION (#.03) in\nAUTHORIZATION/SUBSCRIPTION file (#8930.1) to now require these fields when\ncreating rules. It also includes an updated INPUT TEMPLATE for USR\nAUTHORIZATION/SUBSCRIPTION (#8930.1) to perform requirement matching on\nfields USER CLASS (#.04), AND FLAG (#.05), and USER ROLE (#.06). The \npatch prevents the error "Already a member of this class" from being \n\n
\nASU patch 3, USR*1.0*3. This patch removes TIU dependencies from ASU.\nSee the National Patch module for a complete description.\n\n
\nThe description of this build can be found under patch USR*1*33 in the \nNational Patch Module.\n\n
\nPLEASE REFER TO THE PATCH DESCRIPTION FOR USR*1.0*39 FOR DETAILS.\n\n
\nThis patch addresses the following issue:\n \nThe word "granted" is spelled "grated" in help text displayed by options \n"USR LIST MEMBERSHIP BY CLASS" and "USR LIST MEMBERSHIP BY USER".\n\n
\nASU patch 4, USR*1.0*4. This patch adds options that allow examination\nof class memberships without editing capabilites. See the National\nPatch module for a complete description.\n\n
\nASU patch 5, USR*1.0*5. This patch eliminates multiple prompting for\nUser Classes with that have multiple matches.\n\n
\nASU patch 6, USR*1.0*6. This patch changes the display of user class\nmembership so that all instances of class membership will be displayed.\nSee the National Patch Module for a complete description.\n\n
\nASU patch 7, USR*1.0*7. This patch changes expanding/collapsing of\nclass trees. See the National Patch Module for a complete description.\n\n
\nASU patch 8, USR*1.0*8. This patch allows for two users to have the same\nname. See the National Patch Module for a complete description.\n\n
\nASU patch 9, USR*1.0*9. This patch changes the display name from the\nSIGNATURE NAME PRINTED BLOCK to the .01 field of file 200. See the\nNational Patch Module for a complete description.\n\n
\nAuthorization/Subscription Utility version 1.0\nrules are defined at a general level in either the Document Definition or\nUser Class Hierarchies, they are "inherited" by more specfic "descendent"\nclasses or TITLES.\n \nFeatures\n \n+ ASU lets you define, populate, and retrieve information about user\n classes. These user classes can be defined hospital-wide or more\n narrowly for a specific service and can be used across DHCP to replace\n and/or complement keys. \n \n \n+ ASU lets you link user classes with orders and order events or with\n TIU Document Definitions and document events. This part of ASU defines\n behavior for orders and TIU documents only. In a future version, it may\n be extended to define behavior for other clinical entitites.\n \n+ User classes can be populated via a multiple field in the New Person\n file pointing to the User Class file. \n \n+ Class members may be active or inactive. \nThis package implements a User Class Hierarchy which is useful for\n \n+ The Authorization/Subscription file links events (e.g., Sign) with\n Document/Order type (e.g., Clinical Warning Note) with User Classes\n (e.g., Provider Class). \n \n+ ASU allows infinite hierarchies of subclasses.\n \n+ ASU allows one level of document type to inherit document definition\n from a higher level.\nidentifying the roles that different users fulfill within the hospital,\nand allows for the specification of business rules for the handling of\ndocuments by members of such groups. ASU provides a method for identifying\nwho is AUTHORIZED to do something to a particular kind of document in a\ngiven status (e.g., An UNSIGNED CLINICAL DOCUMENT may be EDITED by a\nPROVIDER who is also the EXPECTED SIGNER of the document). When such\n\n
\nDescription:\n 1. Routine: TIUDEV\n a new note using the CPRS GUI.\n - TIUSRVLL: Added a condition to assure that UNSIGNED\n addenda are included in the list of notes presented\n to an author using the Review Progress Notes option.\n - TIUSRVLO: Modified date limit computation to assure\n that both upper and lower bounds are inclusive (e.g.,\n from TODAY to TODAY will get all of today's notes),\n when accessed through CPRS (this was already true\n within TIU itself).\n - TIUSRVP: Modified the VALIDATE function for evaluating\n Added ZTSAVE("OR*") to the list of variables to be\n electronic signatures passed from a client application\n to exclude a match when the user's es is NULL, and the\n string passed from the calling application is NULL.\n \n Routine Summary: \n ================\n The following is a list of the routines included in this patch. The \n second line of each of these routines will look like: \n \n <tab>;;1.0;TEXT INTEGRATION UTILITIES;**[Patch List]**;Jun 20, 1997 \n saved in the call to ^%ZTLOAD for queued output.\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n TIUDEV 663743 715912 1\n TIUEDI2 2954081 3117146 1\n TIUEDIT 15928365 16237072 1\n TIULA2 11422552 11932899 1\n TIULG 2290558 2618361 1\n TIULX 3630728 3681078 1\n TIUPEFIX 8681313 8870198 1\n This was done to prevent an UNDEF error when queuing\n TIUPRD 3348806 3379168 1\n TIURA 15894554 15915703 1\n TIURC 15436202 15421240 1\n TIURD1 20613578 19512855 1\n TIUSRV 15487391 15503668 1\n TIUSRVD 4955592 5082369 1\n TIUSRVLL 6543081 6594347 1\n TIUSRVLO 8206046 8457918 1\n TIUSRVP 8220630 8488903 1\n \n output from the Notes and Summaries Tabs of the CPRS\n \nData Dictionary: \n===============\nThis patch also exports a partial DD for the .01 field of file 8925,\nwith a correction to the KILL LOGIC for the ASVC2 Cross-reference on\nthat field.\n \n \nInput Templates:\n===============\n Chart.\nThe input templates TIU ENTER/EDIT PROGRESS NOTE and TIUZ ENTER/EDIT\nPN were modified to allow editing of expected cosigner, whenever one\nmay have been designated. These templates formerly only asked for\nexpected cosigner when the author was known to require one. This\nprohibited editing of mis-designated cosigners for notes that were\ncaptured through the upload process. \n \n \nInstallation Instructions: \n==========================\n \nThis patch may be installed with users on the system; however, it\nshould be installed at a non-peak time to minimize disruption to\nthe users. Installation of this patch will take less than 2 minutes. \n \n1. Use the INSTALL/CHECK MESSAGE option on the Packman Menu. \n \n2. Review your mapped set. If any of the routines listed in this \n patch are mapped, they should be removed from the mapped set at \n this time, along with TIUXRC* and TIUEPN*, which include the\n code for compiled cross-references and input template effected\n 2. Routines: TIUEDI2 TIUEDIT\n by this patch. \n \n3. From the Kernel Installation and Distribution System (KIDS) Menu, \n select the Installation menu. \n \n4. From the Installation menu, you may elect to use the following \n options (when prompted for INSTALL NAME, enter TIU*1.0*1): \n a. Backup a Transport Global \n b. Compare Transport Global to Current System \n c. Verify Checksums in Transport Global \n Modified TIUEDI2 to prevent prompting inappropriately\n \n5. Use the Install Package(s) option and select the package TIU*1.0*1.\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//', respond YES, and DISABLE the TIU* Options and\n Protocols.\n \n7. If routines were unmapped as part of step 2, they should be returned \n to the mapped set once the installation has run to completion.\n for the user to edit an unsaved note, for which they\n===========\n are not listed as the person by whom the note was\n entered. Modified TIUEDIT to assure that demographic\n variables are scoped appropriately between patients\n during successive entry of multiple TIU documents.\n \n 3. Routine: TIULA2\n - Modified the display of titles to indicate the title\n for which an addendum has been entered, and to pre-\n pend a "+" when a document has addenda, or a "*" when\n a document is an unsigned "STAT" document.\nPATCH 1: This patch resolves a number of problems with the Remote\n - Modified the selection code to allow multiple\n selection at any '^' TO STOP prompt, and to support\n the selection of an indefinite number of notes,\n without resulting in a STRLEN error, which had been\n reported by WPB when a range of approximately 200\n notes was selected.\n \n 4. Routine: TIULG WPB NOIS COS-0797-N0060\n Modified the BADSIG subroutine to print the message:\n < [TITLE] SAVED - WITHOUT SIGNATURE >\nProcedure Calls which support CPRS, the scoping of demographic variables,\n when the user elects not to sign the note on exit\n from the entry or edit function, rather than echoing\n a message indicating how to enter their electronic\n signature code using the User's Toolbox option.\n \n 5. Routine: TIULX\n Modified the CWAD subroutine to assure that the\n variable GMRPQT is appropriately scoped, prior to\n calling PAT^GMRPNOR1 to get the string indicating\n which CWAD indicators were on file for the current\nand one of the cross-references supporting the query by Service, which\n patient, and setting the variable VALMBCK="R" to\n assure that the Notes and Summaries Tabs of the\n CPRS chart are properly refreshed on return from\n a call to this subroutine.\n \n 6. Routine: TIUPEFIX\n Modified the STUFREC subroutine to assure that the\n appropriate status is computed when resolving upload\n errors.\n \nhave been reported since release of TIU.\n 7. Routine: TIUPRD\n Modified the Print Driver to ensure that all documents\n identified in a call to the routine do exist, and are\n not merely artifacts of corrupt cross-reference entries\n left by disconnect errors, or other interrupted\n processes.\n \n 8. Routine: TIURA\n Added a NEW command at the line tag PRINTX to scope\n the variable IOSTBM appropriately, and allow printing\n \n of documents to VA FileMan's Browser device.\n \n 9. Routine: TIURC\n Fixed the COPY function to assure that the appropriate\n visit location was being recorded for the "destination"\n note, rather than copying the visit location from the\n "source" note.\n \n10. Routine: TIURD1\n Modified to resolve a number of issues with reassign-\nThe following routines are included in this distribution:\n ment of addenda (particularly following signature),\n including the scrambling of signature blocks when\n addenda were swapped with, or moved to replace their\n originals.\n \n11. Routines: TIUSRV TIUSRVD\n TIUSRVLL TIUSRVLO\n TIUSRVP\n These routines, which primarily support TIU's Remote\n Procedure Calls, were modified to fix several issues\n \n that were identified during implementation of CPRS\n v1.0T12 at WPB, as follows:\n - TIUSRV: the variable VALMAR needed to be scoped\n using the NEW command to avoid collision with the\n variable's value in the calling environment,\n - TIUSRVD: the variables VAIN and VADM were scoped\n using the NEW command to avoid leaving demographic\n and inpatient variables around between successive\n patients. The subroutine TRAVERSE was modified to\n filter inactive titles from the list when composing\n\n\nThis patch is described on the National Patch Module, under patch\nTIU*1*15.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1.0*111.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*100.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*96.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*114.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*105.\n\n
\nThe description for this patch can be found in the National Patch Module\nunder TIU*1*110.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1*121.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*119.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*118.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1*116.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*9\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*117.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*125.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*120.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*115.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*123.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*127.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*122.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*126.\n\n
\nThe description of this build is found in the National Patch Module under \npatch TIU*1*129.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*132.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1.0*12.\n\n
\nThe description on this patch may be found in the National Patch Module\nunder TIU*1*109.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*124.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*138.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1*130.\n\n
\nThe description of this build can be found in the National Patch Module \nunder TIU*1*131.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*140.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*136.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*146.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*139.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*145. \n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*10.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*142.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*143.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*148.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*156.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*154.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*149.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*155.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*152.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*150.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*151.\n\n
\nThis patch is described on the National Patch Module, under TIU*1*18.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*135.\n\n
\nThe description of this build can be found in the National Patch Module, \nunder patch TIU*1*144.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*160.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*164.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*158.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*153.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch TIU*1*137.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*134.\n\n
\nThe description for this patch may be found in the National Patch Module \nunder TIU*1.0*170.\n\n
\nThe description of the build for patch TIU*1*165 can be found in the \nNational Patch Module.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1.0*13.\n\n
\nThe description for this patch may be found in the National Patch Module \nunder TIU*1.0*161.\n\n
\nThe description of this patch may be found under the National Patch Module \nunder TIU*1.0*167.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch TIU*1*162.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*181.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*159.\n\n
\nThe description on this patch may be found in the National Patch Module\nunder TIU*1*113.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*141.\n\n
\nThis patch is described on the National Patch Module, under patch TIU*1*24.\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1*112.\n\n
\nThe description for this patch may be found in the National Patch Module \nunder TIU*1*174.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*185.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch TIU*1.0*178.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*187.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*179.\n\n
\nThe description of this patch may be found in the National \nPatch Module under TIU*1.0*163.\n\n
\n\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*188.\n\n
\nThe description for this patch may be found in the National Patch Module \nunder TIU*1*177.\n\n
\nThe description of this build can be found in the National Patch Module \nunder TIU*1.0*169.\n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\nThe description of this patch may be found under the National Patch Module \nunder TIU*1.0*175.\n\n
\nCompleted Doc-CHANGE TITLE fix Replace\n\n
\nThe description of this build is found in the National Patch Module under\npatch TIU*1.0*166.\n\n
\nPlease refer to the patch description in the national patch module for\ninformation regarding this patch.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*180.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch TIU*1.0*173.\n\n
\nERROR DURING UPLOAD OF DOCUMENTS UNDER CERTAIN CONDITIONS.\n\n
\nThe description of this build can be found in the National Patch Module \nunder TIU*1*182.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*19.\n\n
\nWHEN THERE IS MORE THAN ONE OPERATION REPORT FOR THE SAME DAY, THERE IS \nNO WAY TO TELL WHICH OPERATION REPORT TO CHOOSE. ADD PRINCIPAL PROCEDURE \nNAME TO LIST.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*186.\n\n
\nIN CPRS GUI, NOTES, VIEW, SIGNED BY AUTHOR IT DISPLAYS NOTES BY SIGNED BY \nINSTEAD OF AUTHOR. IN ROLL AND SCROLL OPTION 2B Review Progress Notes, \nSS DOES THE SAME. IN ROLL AND SCROLL CPRS, NOTES, CV IT DOES THE SAME. \nTHIS PATCH WILL CORRECT THOSE PROBLEMS.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*191.\n\n
\nCORRECT A PROBLEM WITH ACTIVE/RECENT MEDS OBJECT. UNDER CERTAIN \nCONDITIONS IT WOULD SHOW A DISCONTINUED MED AND NOT THE ACTIVE MED FOR \nTHE SAME DRUG.\n \nPROBLEM WITH TIU DOCUMENT PARAMETER EDIT. SITES WERE CHANGING THE \nDOCUMENT NAME DURING THE EDIT AND LOOSING ALL THE PARAMETERS FOR THE \nDOCUMENT. ADDED A WARNING MESSAGE IF DOCUMENT NAME IS CHANGED OR DELETED.\n\n
\nIf the Patient Movement Record field (1401) of the TIU Document file \n(8925) is null an unfined error occurs when trying to edit the Discharge \nSummary. The input template TIU ENTER/EDIT DS will be modified to prevent \nthis hard error.\n\n
\nWHEN DELETING A TIU DOCUMENT PARAMETER AN UNDEFINED OCCURS.\n\n
\nFix problem in boilerplate logic when a line of boilerplate text contains \nmore than one object.\n\n
\nDOCUMENT PARAMETER VALUES CAN BE LOST WHILE EDITING A DOCUMENT PARAMETER.\n\n
\nContains the Missing Expected Cosigner Report and a fix to the TIU UNK \nADDENDA MENU option's synonym.\n\n
\nFor a complete description of this patch, please refer to the National\nPatch Module, under TIU*1*23.\n\n
\nThe description of this patch may be found in the national patch module \nunder patch TIU*1.0*209.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*202.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch TIU*1*184.\n\n
\nFix header display and prompts for TIU document display options and fix \nprompt for option TIU REVIEW DS CLINICIAN.\n.\n\n
\nFix ACL cross reference for field .02 in file 8925.1. Add field "SIGNED \nBY SURROGATE to file 8925.7 and provide tool to set this field for notes \nsigned prior to this patch.\n\n
\nThe description of this patch may be found in the national patch module \nunder patch TIU*1.0*218.\n\n
\nUNDEFINED ERROR IN TIUPUTS WHEN THERE IS NO DATE/TIME OUT OF OR. TIU \nVITALS OBJECTS (WEIGHT, HEIGHT AND TEMP) NOT WORKING PROPERLY WHEN \nRESULTS ARE REFUSED, UNAVAILABLE OR PASS.\n\n
\nFix display of a long Author's name in the TIU BROWSE menu options and \nfix the duplicate display of notes in the TIU SEARCH BY PATIENT/TITLE \noption.\n\n
\nThe description of this patch may be found under the National Patch Module \nunder TIU*1.0*200.\n\n
\nReport on and optionally fix mismatched ID notes. Report on parent notes \nthat may not be an id note.\n\n
\n This patch fixes a String Too Long error in Document Definition Action\n CREATE. This problem was communicated in a local NOIS message in Seattle.\n It has not been reported as a national NOIS.\n\n
\nFor a completed description of this patch, please refer to the National\nPatch Module, under TIU*1*25.\n\n
\nChange TIU AUTHORIZATION RPC to not allow deletion of a Parent ID note if \nit has a Child.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*211.\n\n
\nSee patch description in the National Patch Module.\n\n
\nThis patch will add a parameter to the TIU PARAMETERS file (8925.99) \ncalled LENGTH OF SIGNER ALERT PERIOD. This parameter will be used to \ndetermine how far back the TIU NIGHTLY TASK should search when looking \nfor documents needing a signature. Input transforms for fields START OF \nADD SGNR ALERT PERIOD and END OF ADD SGNR ALERT PERIOD in file 8925.99 \nwere not working properly and were corrected. It also correctS an \nundefined error in routine TIUSRVPT.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1.0*223.\n\n
\nFix boilerplate "TRY" function and prompts in TIU REVIEW SCREEN MRT.\n\n
\nWhen using Copy to create a new document, the print name from the \nProhibit Edit or Send Back of uncosinged documents.\norigingal document is the print name for the newly created document. \nSince the print name is what is displayed in CPRS this causes a problem.\n \n \nProhibit Edit, Delete, Amend of TIU Surgery documents in TIU LM or CPRS.\nChange error message when trying to delete Interdisciplinary Parent Note \nthat has kids.\n \n\n
\nFix provider encounter data in document upload.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*225.\n\n
\nFor a complete description of this patch, please refer to the National\npatch module, under TIU*1*28.\n\n
\nPlease see the National Patch Module for patch TIU*1*213.\n\n
\nModify TIU Medications object to include route and schedule for inpatient \nIV'S.\n\n
\nProblem 1 - when there are 2 appointments in the same day an uploaded \ndocument always posts to the last appointment.\nProblem 2 - Alerts for additional signer are being sent on a retracted \ndocument\nProblem 3 - Addendum alerts are sent to author and expected co-signer \ndaily when an additonal signer is overdue for signature\n\n
\nThe description of this patch may be found under the National Patch Module \nunder TIU*1.0*222.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*235.\n\n
\nThe description of this patch may be found under the National Patch Module\nunder TIU*1.0*230.\n\n
\nRestore routine TIULP, TIUSRVA and TIUFLF4 to pre-patch TIU*1.0*215 state.\n\n
\nUtility to analyze problems that may have been caused by the installation \nof patch TIU*1.0*215. Runs upon install and also as a stand alone option.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*238.\n\n
\nFix the following defects\nHD 169774 UPDATE OF 8925.1 "ACL" INDEX\nHD 71187 UNDEFINED STATUS+9^TIUR\nHD 69681 DIFFERENCE IN PRINTING IDENTIFIED SIGNERS\nHD 69457 UNDEFINED UPRBLD+38^TIURL\nHD 209427 LM rebuild list does not display properly after a line is \ndeleted.\n \nHD 71015 UNDEFINED SETREC+7^TIURL\n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*33.\n\n
\nFor a description of this build see the National Patch Module entry for \nTIU*1*234.\n\n
\nSee National Patch Module, TIU*1*219.\n\n
\nThe description of this patch may be found under the National Patch Module \nunder TIU*1.0*228.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*242.\n\n
\nThis patch will correct addendum, alert, and signature issues.\n\n
\nThis patch includes fixes for the following Remedy tickets:\n \n HD69299 - ID SIGNER/CO-SIGNER\n HD99628 - Spacebar option not working after patch TIU*1*173 \n HD69093 - Can not print warning for addendum\n HD94265 - Can not delete duplicate UNDICTATED Opertion Report\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*246.\n\n
\nPSI-07-154\n \nProblem with TIU C&P upload. The upload requires the IEN of file 396.4 as \nthe reference number. If there is an error on the upload processing the \nerror alert can post the exam results to the wrong veteran. The upload \ncan also post to closed exam requests.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*249.\n\n\n
\nFix the following defects.\n TIU BROWSE DOCUMENT MGR Individual Patient Document\n TIU BROWSE DOCUMENT MRT Individual Patient Document\n TIU MAIN MENU MGR Text Integration Utilities (MIS Manager)\n TIU MAIN MENU MRT Text Integration Utilities (MRT)\n TIU REVIEW SCREEN MIS MANAGER Multiple Patient Documents\n TIU REVIEW SCREEN MRT Multiple Patient Documents\n TIU SEARCH LIST MGR Search for Selected Documents\n TIU SEARCH LIST MRT Search for Selected Documents\n \n \nHD69695 When using copy to create a new document, the print name from the \n \nHD166528 Update message displayed when trying to delete an \nInterdisciplinary Parent note that has kids.\noriginal document is the print name for the newly created document.\nHD70760 In CPRS do not allow edit, delete, addendum of Nurse \nIntraoperative Report and Anesthesia Report. \n Also, prohibit Amend, or Verify/Unverify -> Edit functions\n for the Nurse Intraoperative Report and Anesthesia Report\n in the options listed below:\n \n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*37.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*244.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*250.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*257.\n\n
\nHD229090 Additional signer does not appear on documents that are \nadministratively closed\nHD247418 Incorrect ??doc for START OF ADD SGNR ALERT PERIOD. Also update \ntechnical manual\nHD70039 No entry in TIU Technical Manual for TIU Nightly Task\n\n
\nThis patch related to Remedy 277123 and PSPO 1093. The TIU option TIU \nMISSING TEXT CLEANUP retracts documents and therefore should be \nrestricted to users who hold security key TIU MISSING TEXT CLEAN.\nSecurity key TIU MISSING TEXT CLEAN should only be assigned to someone\nthat holds Chief,MIS or Chief, HIM class in USR.\n\n
\nThis patch adresses the following Remedy tickets:\n \n HD168903 - TIU documents/consults\n duplicate(s): HD211236,202522,193385\n HD311014 - One Progress Note on two consults\n HD152076 - User Class expires\n HD131840 - Addtl Signer - User Class Requiring Cosignature (error box)\n\n
\n This patch will correct the following issue:\n \n An Identified Signer disappears from a note after re-identifying\n the signer (using the Identify Additional Signature command) and \n then clicking on either the "Remove" or "Remove All" button. \n\n
\nThe description of this build can be found in the National Patch Module \nunder patch TIU*1*261.\n\n
\nSee TIU*1*252 in the National Patch Module.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*29.\n\n
\nThis build for TIU*1*259 addresses 2 issues.\n \nFirst, it adds the date of the document to alerts for OVERDUE signatures.\n \nSecond, it changes TIU VISTA MRT Option Unsigned/Uncosigned Report [TIU \nUNSIGNED/UNCOSIGNED REPORT] so that documents requiring a cosignature are\nsorted under the service of the Expected Cosigner rather than the author.\n\n
\n This patch will correct the following issues:\n \n When certain Patient Data Objects are imported from MED notes, internal \n data was incorrectly getting added to the note. \n \n Mobile Electronic Documentation was calculating when to suggest \n database compaction incorrectly. Also, when database compaction was \n suggested, and the users clicked Yes in order to compact the database, \n MED would get stuck in an infinite loop and hang.\n \n The Action menu, in MED is displaying on all tabs, even though it is \n If a user enters a note in Mobile Electronic Documentation, and does not \n only related to the Notes tab. This can cause confusion if there is a \n note selected on the notes tab and the user is on a different tab.\n \n When using a dialog template in MED, parent choices are grayed out. \n When the same choices are not grayed out if viewed in CPRS.\n \n Med Install guide references the wrong Key.\n \n If a user attempted to retrieve two patients with the same names they\n would import correctly, but only one would be selectable in the patient\n select a different note before exiting, in some cases the newly entered \n selection dialog.\n note would be lost.\n \n The parameter TIU MED HSTYPE was set to accept a free text value that \n should contain a pointer to the Health Summary type to be used with MED. \n This was a problem, because a user had to know the Internal entry \n number of the health summary in order to update the parameter.\n\n
\nThis patch will address an undefined error - <UNDEFINED>PRNTSCRN+5^TIURA2\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1*265.\n\n
\nThe description of this build can be found in the National Patch Module \nunder TIU*1*267.\n\n
\nPrevent notes without text from being signed\n\n
\nSee patch description on FORUM for patch TIU*1.0*275.\n\n
\nWhen a Nurse Intraoperative Report (NIR) or Anesthesia report is entered \nfollowing options:\n \nTIU BROWSE DOCUMENT MGR\nTIU BROWSE DOCUMENT MRT\nTIU SEARCH LIST MGR\nTIU REVIEW SCREEN MIS MANAGER\nand signed in the Surgery package, a note is created in Text Integration \nUtility (TIU). The note is created in file TIU DOCUMENT (8925). If the \nnote is entered and signed mistakenly in the Surgery Package there is no\nway to delete the note in either Surgery or TIU.\n \nThis patch will allow Privacy Act Officers or MIS/HIM Chiefs to\ndelete/retract Nurse Intraoperative reports (NIR) or Anesthesia \nreports (AR) from CPRS GUI - Surgery tab or in VistA through the \n\n
\nThis patch will resolve the following issues in the Text Integration\nUtilities package:\n \n-Inability to search for Expected Cosigner\n-Error loading boilerplate text with attached template\n\n
\nThis patch will resolve the following issues:\n1) Completed documents are showing on TIU report of "All My \nUnsigned" documents.\n2) GETFLD+2^TIUSRVF subscript errors\n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*30.\n\n
\nThis patch will correct the following issues:\n \n Users unable to find any results when searching for addenda using the \n Text Integration Utilities (MRT) [TIU MAIN MENU MRT] option\n \n String dates are being stored in the REFERENCE DATE field (#1301) of \n the TIU DOCUMENT file (#8925).\n\n
\nThis patch will resolve the following issues in the Text Integration\nUtilities package:\n \n-Redundant progress notes title display\n-Spelling error in TIU Template field\n\n
\nTIU changes for the VIA project. See patch description for details.\n\n
\nThis patch will resolve the following issues in the Text Integration\nUtility package:\n \n-Cannot search for documents with multiple keywords\n-Error saving TIU Document Parameter name\n\n
\nThe description of this build can be found under patch TIU*1*263 in the \nNational Patch Module.\n\n
\nTIU FIX REPORT INDEX\n \nThis patch will resolve a problem with the TIU REVIEW MRT ADD SGNR \nreport. The report was not displaying all documents with \nunsigned additional signatures. The underlying issue was found to be a \nproblem with the AC index in file 8925.7 (TIU MULTIPLE SIGNATURE). This \npatch corrects the report by fixing the deficiency with the AC index \nlogic. The post install routine rebuilds the AC index.\n\n
\nThis patch will resolve the following issues in the Text Integration\n 1. INC000000454162 - Uploaded documents create addendum without \nan author\n \n \nREMEDY TICKET OVERVIEW:\n======================\n1. INC000000454162\n \n \n Problem:\nUtilities package:\n -------\n If the system doesn't find a match for the patient and surgery case a \nfiling error is generated and you are able to \n \nedit the document which will then populate the attending & dictated by \nfields. If the document is uploaded and filed \n \nsuccessfully the attending and dictated by fields are blank. \nTIU*1.0*173 prevented these fields from being populated \n \n \nduring the upload process, which is correct, but didn't allow these \nfields need to be populated when an addendum is created.\n \n \n \n Resolution:\n ----------\n Check if the uploaded OPERATIVE REPORT is an addendum to an existing \ndocument, allow the Dictator/Author and Attending fields to be populated.\n \nAllow the TIU DOCUMENT fields Author/Dictator and Attending Physician \n \n \n \n \n ================INSTALLATION INSTRUCTIONS =================\n \nIt is not necessary to disable any options. It is recommended to install \nthis patch when users are off the system. It should take less than 2\nminutes to install this patch.\n \n(fields 1202 & \n 1. Choose the PackMan message containing this patch and invoke the\n INSTALL/CHECK MESSAGE PackMan option. \n \n 2. From the Kernel Installation & Distribution System menu, select \n the Installation menu. \n \n 3. From this menu, you may select to use the following options: \n (when prompted for INSTALL NAME, enter TIU*1.0*277)\n \n a. Verify Checksums in Transport Global - This option will allow\n1209) to be populated into addendums to OPERATION REPORT documents.\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n \n backup any other changes such as DD's or templates.\n \n 4. Use the Install Package(s) option and select the package \n TIU*1.0*277.\n \n 5. When Prompted "Want KIDS to INHIBIT LOGONs during the install? \n NO//" respond NO. \n \n 6. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? NO//" respond NO.\nASSOCIATED REMEDY TICKETS:\n=========================\n\n
\nThis patch will resolve the following issues in the Text Integration\nUtilities package:\n \n1) The reasignment of TIU documents can be required to be accomplished \ntwice before the reassign is successfull.\n2) Error occurs in TIUSRVR1 when TIUDA is passed in null\n\n
\nThis patch corrects an issue with the honoring of the ALLOW\nCHART PRINT OUTSIDE MAS parameter.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*26.\n\n
\nThe TIU*1.0*296 patch entails modifying the Computerized Patient Record\nnote being co-signed by the licensed clinician responsible for reviewing\nand approving the note. \n \nPrior to this modification, no TIU alerts were sent to the service \nproviders. This resulted in missed opportunities to provide needed \nservices for patients while the patients are on site, and forced staff to \ntake time to contact patients and reschedule needed services\n \nThis patch utilizes one new file (TIU TEXT EVENTS (#8925.71)) used to\ndefine the words or phrase that will be searched for in a TIU document \nSystem (CPRS) Consult/Request Tracking package to send a Text Integration\n(progress note, consult, etc.). If the words or phrase are found in the \nTIU document, then an alert is sent to the individual or team specified in\nthe TIU TEXT EVENTS file. \n \nOne new menu option-Text Event Edit [TIU TEXT EVENT EDIT]-will be added \nto the TIU Maintenance Menu [TIU IRM MAINTENANCE MENU]. This option is \nused only to set up a text event in the TIU TEXT EVENTS file.\n \n***IMPORTANT***: Any TIU document that is to be used for these alerts MUST\nhave the MUMPS code 'D TASK^TIUTIUS(DA)' entered in the POST-SIGNATURE\nUtilities (TIU) alert to the appropriate service provider immediately\nCODE (#4.9) field in the TIU DOCUMENT DEFINITION (#8925.1) file.\n \nThis patch will work in both CPRS GUI and the VistA system.\n \nThe NSR for this intake addresses the following requirements:\n \n VHBAO: NEED2949: Provide the ability for users to send TIU text alerts\n created by non-clinical staff in CPRS to service\n providers before being co-signed by a licensed\n clinician.\nafter a non-clinical staff member screens a patient and signs the\nassociated CPRS note\n \nThis functionality is needed so that after non-clinical staff members have\nscreened patients for potential risks (weight loss or gain, homelessness,\nsubstance abuse, etc.), the service provider will be alerted prior to the\n\n
\nSupport for VPR\n\n
\nThis patch will resolve the following issues:\n \n 1) AUTHORIZATION/SUBSCRIPTION UTILITY (ASU) CLINICAL COORDINATOR MANUAL\n documentation changes\n 2) Date range search options in TIU will reset the date range\n 3) Incorrect Philippines address format\n 4) Routine TIUSRVR2 does not contain 211 on the 2nd line\n\n
\nThis patch implements the CWAD AUTO-DEMOTION functionality.\n\n
\nCorrect cause of error <UNDEFINED> PRINT+23^GMRCTIUP\n\n
\nTIU RPC updates for VIAB*1*7.\n\n
\nThis patch will resolve the following issues:\n1) Document parameters cannot be deleted.\n2) Multiple TIU DOCUMENT PARAMETER records can be created\n3) TIU report display more documents types than requested\n\n
\nSee National Patch Module for details.\n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*32.\n\n
\nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant, the Mobile Electronic Documentation (MED) Graphical User \nInterface (GUI) requires an upgrade to Delphi version XE8 in order to\nimplement the, new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*258.\n\n
\nThis patch will address a problem with consult notes being assigned\n \n D GETPN^TIUCHLP changed to D PNFIX^TIUPNFIX\n 1331 C&P MEDICAL (TITLE)\n No change. Value is already D PNFIX^TIUPNFIX\n \n \n ================INSTALLATION INSTRUCTIONS =================\n \nIt is not necessary to disable any options. Users should not edit TIU \ndocument definitions during the install. It should take less than \n2 minutes to install this patch.\nAssociated NSR(s):\n \n 1. Ensure there are appropriate active user entries as members of both \n VistA mail groups 'PATIENT SAFETY NOTIFICATIONS' and 'TIU CACS'.\n This can be accomplished using option 'Mail Group Edit' on the\n Group/Distribution Management menu.\n \n 2. Choose the PackMan message containing this patch and invoke the\n INSTALL/CHECK MESSAGE PackMan option. \n \n 3. From the Kernel Installation & Distribution System menu, select \n==================\n the Installation menu. \n \n 4. From this menu, you may select to use the following options: \n (when prompted for INSTALL NAME, enter TIU*1.0*301)\n \n a. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\nN/A\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this\n patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n \n 5. Use the Install Package(s) option and select the package TIU*1.0*301\n \n \n 6. When Prompted "Rebuild Menu Tree Upon Completion: NO// respond NO.\n \n 7. When Prompted "Want KIDS to INHIBIT LOGONs during the install? \n NO//" respond NO. \n \n 8. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? NO//" respond NO.\nTest Sites:\n===========\nTBD\n \nSDM Ticket Overview:\nto an incorrect patient's chart as a result of post install instructions\n====================\nI10273633FY16 - Exact same note appearing on two different charts.\n \nProblem: \n========\nThe same consult note is documented in the correct patient chart as well\nas an incorrect patient chart, due to an incorrect consult number and an\nincorrect parameter value used when uploading the note through TIU. It\nwas determined that this is a result of post install instructions for\npatch TIU*1.0*131 not being followed leaving the TIU DOCUMENT \nfor patch TIU*1.0*131 not being completed.\nDEFINITIONS Progress Notes and Consults records with incorrect values in\nfield 4.8 (UPLOAD FILING ERROR CODE). The upload would not be filed and\ngenerate an error instead had the post install instructions for patch\nTIU*1.0*131 been completed.\n \nResolution:\n===========\nThis patch will run a post install routine. The post install routine\nwill review the PROGRESS NOTES class and CONSULTS document class (or\nCONSULTS class) and all entries within them in the TIU Document \n \nDefinitions file (8925.1). \n \nThe details of the install routine are as follows:\n - If the current value of the UPLOAD FILING ERROR CODE (field 4.8) for\n PROGRESS NOTES (and all document definitions under it) equals the\n pre-patch TIU*1.0*131 value of "D GETPN^TIUCHLP" it will be changed to \n "D PNFIX^TIUPNFIX" (if the record is not locked).\n - If the current value of the UPLOAD FILING ERROR CODE (field 4.8) \n for CONSULTS (and all document definitions under it) equals the\n pre-patch TIU*1.0*131 value of "D GETPN^TIUCHLP" it will be changed to\nAssociated CA SDM ticket(s):\n "D CNFIX^TIUCNFIX" (if the record is not locked).\n - If a record has the pre-patch TIU*1.0*131 value and cannot be updated \n due to being locked it will need to be manually corrected.\n \nThe below example information will be included in the mail message\nto any user defined as a member of VistA mail groups\n'PATIENT SAFETY NOTIFICATIONS' and 'TIU CACS' as well as to the user\nrunning the installation:\n \n Subj: PATCH TIU*1.0*301 \n============================\n From: PATCH TIU*1.0*301 In 'IN' basket. Page 1 \n--------------------------------------------------------------------------\n This patch reviews field 4.8 (UPLOAD FILING ERROR CODE) in the TIU \n DOCUMENT DEFINITIONS file for document classes and titles belonging to\n CONSULTS and PROGRESS NOTES and are addressed as follows: \n 1. CONSULTS with the pre-patch TIU*1.0*131 value of 'D GETPN^TIUCHLP'\n are changed to 'D CNFIX^TIUCNFIX'\n 2. PROGRESS NOTES with the pre-patch TIU*1.0*131 value of \n 'D GETPN^TIUCHLP' are changed to 'D PNFIX^TIUPNFIX'. \n 3. Any CONSULTS or PROGRESS NOTES with field 4.8 without a value are\nI10273633FY16\n not changed.\n 4. Any CONSULTS or PROGRESS NOTES with the pre-patch TIU*1.0*131 \n value of 'D GETPN^TIUCHLP' that are locked during the install\n NEED TO BE MANUALLY UPDATED using option TIU UPLOAD PARAMETER \n EDIT.\n 5. Any document definitions with a value other than 'D GETPN^TIUCHLP'\n are not updated.\n \n **IMPORTANT NOTE** The 'Enhanced Mismatched Consults List' [TIU144\n ENHANCED MISMATCH LIST] should be run regularly. Please take a moment \n INC000001014575(d)\n now to run it and create a reminder in your calendar to run it again\n every 6 months. If there are any mismatches, submit a help desk\n ticket for assistance resolving them.\n \n PATCH TIU*1.0*301 INSTALL\n UPLOAD FILING ERROR CODE (Field 4.8) Review:\n \n IEN Document Name (Type)\n Result\n --------------------------------------------\n PSPO #2595\n CONSULTS:\n 767 CONSULTS (DOCUMENT CLASS)\n D GETPN^TIUCHLP changed to D CNFIX^TIUCNFIX\n 788 OPTOMETRY EYE CONSULT REPORT (TITLE)\n D GETPN^TIUCHLP changed to D CNFIX^TIUCNFIX\n 1800 OPHTHALMOLOGY EYE CONSULT REPORT - PRALL (TITLE)\n The record is currently locked.\n Needs to be manually updated to D CNFIX^TIUCNFIX\n PROGRESS NOTES:\n 3 PROGRESS NOTES (CLASS)\n\n
\nThis patch will address errors encountered during background HL7 \nprocessing of incoming TIU Progress Notes (HL7 MDM messages)\n\n
\nedit destination encounter Reassigning a visit\n\n
\nTIU INDEX FIXES AND DOCUMENTATION CORRECTIONS\n\n
\nThis patch will resolve the following issue:\n1) Document definition title displaying incorrect mapped title \n2) TIU object TIU TPBN ACT OUT MEDS not initializing data\n\n
\nDuring the testing of this patch it was noted that the MED \napplication violated a security policy by allowing the application to \nwrite to the database that is stored in the program files folder. \nThis patch will correct this vulnerability by moving the database to \na natural location so the application can interact with it.\n \nThis patch will resolve the following issue in the Mobile Electronic\nDocument application:\n- No notes to import into CPRS via Med Import feature\n\n
\nThis build addresses NSR20080310 and NSR20141017 respectively. It \nlocal title to the national title Computer Downtime. If no local title is \nfound, the installer of the patch will be alerted to complete the mapping \nof one local title to Computer Downtime before attempting to reinstall \nthe patch. Whether or not the site has a local title mapped to the \nnational title Computer Downtime, the installation of the patch will\nproceed to completion.\nconsists of the following options:\nContingency Downtime Bookmark Progress Notes [TIU DOWNTIME BOOKMARK PN]\nCreate Post-Signature Alerts [TIUFPC CREATE POST-SIGNATURE]\nWhen this patch is installed at the sites, it will check file #8925.1, \nfield #3 (Boilerplate Text), for any existing text and delete it to make \nroom for the new text exported with the patch. Sites will be able to see \nthe old text in the install file kept by KIDS after installation has been \ncompleted. The pre-installation routine will check for the mapping of a \n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\n \n (IT) architecture that allows Veterans to receive care from Community \n Providers. \n \n This patch builds upon the HL7 processes created in patches GMRC*3.0*99 \nand\n GMRC*3.0*106. It sends from VistA to HSRM the CCRA progress notes filed \nby \n a provider for a patient in CPRS.\n This patch builds and sends a VistA Outbound MDM-T02 HL7 v.2.5.1 message \nfor any of \n The Community Care Referrals and Authorizations (CCR&A) application is \n the following CCRA Progress Note Titles that are used to file a \nhistorical Progress Notes\n from CPRS:\n 1 COMMUNITY CARE - PATIENT LETTER TITLE \n Std Title: NONVA PROGRESS NOTE\n 2 COMMUNITY CARE- ADMINISTRATIVE REQUEST TITLE \n Std Title: ADMINISTRATIVE NOTE\n 3 COMMUNITY CARE-COORDINATION NOTE TITLE \n Std Title: NONVA PROGRESS NOTE\n 4 COMMUNITY CARE-HOSPITAL NOTIFICATION NOTE TITLE \n an enterprise-wide system used by Community Care (CC) staff to \n Std Title: PRIMARY CARE ADMINISTRATIVE NOTE\n \n The patch installs also the following HL7 1.6 components:\n - new HL logical link: TIUCCRA \n - new HL7 applications: TIU CCRA SEND and TIU HSRM RECEIVE\n - new HL7 Protocols:\n 1 TIU CCRA-HSRM MDM-T02 CLIENT TIU CCRA-HSRM \nMDM-T02 CLIENT \n 2 TIU CCRA-HSRM MDM-T02 SERVER TIU CCRA-HSRM \nMDM-T02 SERVER \n automatically generate referrals and authorizations for all Veterans \n The message is triggered by the TIU Document Definition parameter:\n "POST-SIGNATURE CODE:". All CCRA Progress Note Titles that are required \n to trigger the MDM-T02 to HSRM will have to have POST-SIGNATURE CODE: D \nEN^TIUCCRHL()\n receiving care in the community. Clinical and VA CC staff located at VA \n Medical Centers, Outpatient Clinics, Community Based Outpatient Clinics, \n and VISN offices use this application. The CCR&A solution is an \nintegral \n component of the VA Community Care Information Technology \n\n
\nDuring analysis of ticket INC5361702, an area of code associated to the \nAlert Tracking module was discovered that needs remediation. This patch \nwill correct this design to not completely rebuild the Alert Tracking \nentry for each multiple Additional Signer that is added but rather make a \nsingle call to the TIU alert routine for all additional signers that will \ncreate only one new Alert Tracker record each time one or more additional \nsigners are added.\n\n
\nTIU TEXT ALERT ISSUES\n\n
\n \nProviders.\nThe Community Care Referrals and Authorizations (CCR&A) application is an\nenterprise-wide system used by Community Care (CC) staff to\nautomatically generate referrals and authorizations for all Veterans\nreceiving care in the community. Clinical and VA CC staff located at VA \nMedical Centers, Outpatient Clinics, Community Based Outpatient Clinics,\nand VISN offices use this application. The CCR&A solution is an integral\ncomponent of the VA Community Care Information Technology (IT)\narchitecture that allows Veterans to receive care from Community \n\n
\n \nProviders.\nThe Community Care Referrals and Authorizations (CCR&A) application is an\nenterprise-wide system used by Community Care (CC) staff to\nautomatically generate referrals and authorizations for all Veterans\nreceiving care in the community. Clinical and VA CC staff located at VA \nMedical Centers, Outpatient Clinics, Community Based Outpatient Clinics,\nand VISN offices use this application. The CCR&A solution is an integral\ncomponent of the VA Community Care Information Technology (IT)\narchitecture that allows Veterans to receive care from Community \n\n
\nPlease see the patch description for TIU*1.0*331 at DOMAIN.EXT.\n\n
\nDeploys a new document class and note titles for SMART notifications, \n(OR*3.0*377).\n \nPlease see the accompanying patch description for details and the \nComputerized Patient Record System (CPRS) version 31.b installation \nmanual for installation instructions.\nhigh risk medications status review, and a new note title "Healthe\nLiving Assessment".\n \nAdds a new informational prompt that may appear while taking an action on \na docment. The prompt displays a message from other software packages \nthat have a pointer to the document that the user is acting upon.\n \nThis patch also provides copy/paste APIs and globals for CPRS v31.b\n\n
\nPlease see the patch description on FORUM.\n\n
\nTIU BUSINESS RULES FOR USER ROLE SURROGATE DOES NOT WORK\n\n
\nPlease see patch description in FORUM\n\n
\nThe description of this patch may be found in the National Patch\nModule under TIU*1*35.\n\n
\nPlease see the patch description for TIU*1.0*328 for more information.\n\n
\nThis patch corrects an issue related to the copy/paste functionality\nreleased as part of CPRS 31B. The issue is due to selected login locations\ncontaining non-numeric values. These values are not handled properly \nresulting in pasted text not being saved or retrieved by the CPRS GUI.\nThere is also a problem with site entered userclasses to view all\ncopy/paste actions from being returned and thus a user may be excluded\nfrom viewing copy/paste data in the CPRS GUI as expected.\n\n
\nThis patch addresses the following issue:\nprogress notes USING TIU SEARCH LIST MGR \n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. Error when deleting unsigned progress notes using TIU SEARCH LIST \nMGR \n \n Problem:\n -------\n When using Vista option "Search for Selected Documents" [TIU SEARCH \n1. Error when deleting unsigned progress notes USING TIU SEARCH LIST MGR\nLIST\n MGR] to deleted unsigned progress notes completely out of file 8925, a \n hard error is generated. The Delete action must perform a complete \n deletion out of file 8925 (versus doing a retraction) in order for the\n problem to be reproduced. This error happens whether deleting notes \n singly, or a range of notes.\n \n Resolution:\n ----------\n Modify routine TIURB2 to call NOTIFY^TIUUTL before the TIU Note is \n \n deleted. \n \n \n \nTest Sites:\n==========\nTBD \n \n \nPre-Installation Instructions:\n \n=============================\nThis patch may be loaded with users on the system. You may wish to \ninstall it during non-peak hours. Installation will take less than 1 \nAssociated ticket(s):\n=====================\n \n1. INC14028939, INC15046834 (duplicate) - Error when deleting unsigned \n\n
\nBackup of TIU*1.0*330 on Apr 27, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the patch description for TIU*1.0*330 for more information.\n\n
\nBackup of TIU*1.0*337 on May 07, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nADD NEW TIU CONSULT FROM HSRM TO VISTA.\n\n
\nThe Computerized Patient Record System (CPRS) Graphical User Interface \n \nFor a complete listing of patches included in this release, please refer \nto the CPRS GUI v32a Release Notes. \n(GUI) v32a is an enhancement release. This patch (TIU*1*339) is a part\nof that enhancement release.\n \nSpecifically, this patch introduces the support for:\n \n NSR 20070817: Progress Notes Display Misleading\n NSR 20100706: Identify Required Fields in TIU Note Templates and\n Notify of Missing Required Fields\n\n
\nPlease see the patch description for TIU*1.0*347 for more information.\n\n
\nFile a note addendum with the note from HSRM. \n\n
\nPATCH 3: This patch fixes a number of problems with the batch upload\n the user isn't authorized to add an addendum to the\n TIULC1 5470005 5678356 3\n TIUMOVE 6394806 6445124 3\n TIUPEVNT 12440029 12489033 3\n TIUPNCV7 5344754 5294994 3\n TIUPUTC 11775034 11993374 3\n TIUPUTPN 6063243 6063169 3\n TIUPUTU 5268373 5381409 3\n TIURE 6411729 6529651 3\n TIURS 9109901 9376324 3\n TIUT 6965722 6971292 3\n selected record. This is the appropriate behavior, and\n \n \nInstallation Instructions: \n==========================\nThis patch may be installed with users on the system; however, it\nshould be installed at a non-peak time to minimize disruption to\nthe users. Installation of this patch will take less than 2 minutes. \n \n1. Use the INSTALL/CHECK MESSAGE option on the Packman Menu. \n \n will also prevent a rare UNDEF error at ADDENDUM+17^TIUADD\n2. Review your mapped set. If any of the routines listed in this \n patch are mapped, they should be removed from the mapped set at \n this time, along with TIUXRC* and TIUEPN*, which include the\n code for compiled cross-references and input template effected\n by this patch. \n \n3. From the Kernel Installation and Distribution System (KIDS) Menu, \n select the Installation menu. \n \n4. From the Installation menu, you may elect to use the following \n that had been observed at several test sites.\n options (when prompted for INSTALL NAME, enter TIU*1.0*3): \n a. Backup a Transport Global \n b. Compare Transport Global to Current System \n c. Verify Checksums in Transport Global \n \n5. Use the Install Package(s) option and select the package TIU*1.0*3.\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//', respond YES, and DISABLE the TIU* Options and\n Protocols.\n \n \n7. If routines were unmapped as part of step 2, they should be returned \n to the mapped set once the installation has run to completion.\n 2. Routine: TIUCHLP\n Modified the GETPAT and GETPN subroutines to accom-\n modate the changes to the filing error resolution\n approach for BOTH the alerts and the option to\n Review Upload Filing Events.\nfacilities of TIU, including the alerts and options for filing error\n \n 3. Routine: TIULC\n Changed line REQVER+2 to recognize when the requirement\n for verification has been satisfied for a given record,\n and not impose the requirement inappropriately. Coincides\n with changes to TIUT to assure that the release logic, and\n signature alerts are always executed appropriately.\n \n 4. Routine: TIULC1\n Added a function POSTSIGN, to identify the Post-signature\nresolution. It also fixes a discrepancy in the estimated time to\n action for a given document definition, and enforce its\n inheritance.\n \n 5. Routine: TIUMOVE NOIS: PUG-0997-50895\n Modified the MAIN subroutine to prevent an error reported\n by Puget Sound and Central Texas, where repetitive upload\n of single documents through the option for direct entry of\n a Discharge Summary was occasionally resulting in a mis-\n match to the patient.\n \ncompletion computed by the Progress Notes conversion.\n 6. Routine: TIUPEVNT NOIS: PUG-0997-50895\n Modified to help assure that changes to TIUMOVE are\n reflected appropriately in the handling of upload filer\n errors.\n \n 7. Routine: TIUPNCV7\n Modified the SETVAR subroutine to correct the\n computation of estimated time remaining.\n \n 8. Routine: TIUPUTC\n \n Modified the GETREC subroutine to prevent a\n <NULLSUBSCR> error when a caption is not associated\n with any particular field in the target file.\n \n 9. Routine: TIUPUTPN\n Modified to assure that notes that have been released from\n the DRAFT state are not overwritten when subsequent\n information is uploaded for the same title and visit (an\n addendum will be added instead).\n \nThe following routines are included in this distribution:\n10. Routine: TIUPUTU\n Modified the CANEDIT function to exclude overwriting\n any Discharge Summary record that had proceeded beyond\n release from draft, whether the release event was\n successfully recorded or not.\n \n11. Routine: TIURE\n Modified the FILERR subroutine to accommodate the\n changes to the error resolution approach when the\n option to Review Upload Filing Events is in use.\n \n \n12. Routine: TIURS\n Modified the ES subroutine to prevent prompting multiply\n to "Print this Note? NO//" when an addendum is added for\n cosigner's comments. Also changed ES subroutine to respond\n appropriately when the /ES/ block elements contain a semi-\n colon, preventing a COMMAND error. Implemented the post-\n signature action supported by changes in TIULC1.\n \n13. Routine: TIUT NOIS: PUG-0997-51130\n 1. Routine: TIUADD\n Modified the VERIFY subroutine to stuff DUZ for field\n 1306 (VERIFIED BY), whereas it was stuffing DT. Also\n modified the RELEASE subroutine to assure that the release\n logic is executed when an uploaded document fails to be\n filed initially, and is subsequently filed using the\n options or alerts for filing error correction.\n \n \n Routine Summary: \n ================\n Changed line ADDENDUM+9 to exit the subroutine when\n The following is a list of the routines included in this patch. The \n second line of each of these routines will look like: \n \n <tab>;;1.0;TEXT INTEGRATION UTILITIES;**[Patch List]**;Jun 20, 1997 \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n TIUADD 7939178 7989408 3\n TIUCHLP 5315023 5741332 3\n TIULC 8062118 8116087 3\n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*36.\n\n
\nThis patch will resolve the following issue:\n cosigner\n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. TIU Text Alerts do not work if user requires a cosigner\n \n Problem:\n -------\nWhen a TIU Text Event Alert is set up, a CPRS alert is sent to a team \nwhenever a note is signed that contains specific text. Users notified the \n1. TIU Text Alerts do not work if user requires a cosigner \nCACs that this did not seem to be working for author's who require a \ncosigner. It was tested and confirmed. When signing a note as an \nindependent author, the TIU Text Event Alert was sent as expected. When \nthe author required a cosigner, no alert(s) were sent when the author \nsigned, and no alert(s) were sent when the cosigner signed.\n \n Resolution:\n ----------\nRoutine TIUTIUS is modified to remove a line of code that stopped \nprocessing text alerts when the Note had been signed and cosigned and the \n \ncosigner and signer were different users.\n \nAssociated ticket(s):\n=====================\n \n1. INC18300016 - TIU Text Alerts do not work if user requires a \n\n
\nThis is a follow-up patch to TIU*1.0*290 to implement the redesigned \ncopy/paste tracking report. It also implements a solution to when the TIU \nTEMPLATE (#8927) file allowing long lines of greater than 80 characters.\n\n
\nThis patch addresses issues identified during the CPRS v31b deployment. \nRefer to the patch description for a comlete list of issues that are \naddressed.\n\n
\nFile a note addendum with the note from HSRM. \n\n
\nINC17388233 - Update TIU weight object from conversion using weigh/2.0 to \n weigh/2.20462262\n\n
\nFile a note addendum with the note from HSRM. \n\n
\nPlease refer to the patch description for contents and detailed \ninformation.\n\n
\nFile a note addendum with the note from HSRM. \n\n
\nFile a note addendum with the note from HSRM. \n\n
\nThe description of this patch may be found in the National Patch Module \nunder TIU*1*44.\n\n
\nPlease see FORUM for the patch description of TIU*1.0*355.\n\n
\nPlease see FORUM and TIU*1.0*343 for more information.\n\n
\nPlease see FORUM for the patch description of TIU*1.0*358.\n\n
\nRefer to the patch description for an explanation of the changes included \nin this patch.\n\n
\nPlease see FORUM for the patch description of TIU*1.0*357.\n\n
\nFile a note addendum with the note from HSRM. \n\n
\nManual pkg file update due to CCRA IP connection issues.\n\n
\nWhen printing the progress notes, a specific string of characters in the \nnote text can generate a hard error. This patch addresses this issue.\n\n
\nFor a complete description of this patch, please refer to the National\nPatch Module, under TIU*1*22.\n\n
\nPlease see FORUM for the complete description of TIU*1.0*365.\n\n
\nPlease see TIU*1.0*370 on FORUM for a complete description.\n\n
\nTIU interface will receive HL7 dispense record information and insert \nthis data into file 101.22. This file (101.22) will be used by the OTP \nreport.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*31.\n\n
\nFor a complete description of this patch, please refer to the National\nPatch Module, under TIU*1*27.\n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*41.\n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*40.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*34.\n\n
\nThe description of this patch may be found on the National Patch under\nTIU*1*42.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*46.\n\n
\nChanges were made to 10 Document Definition routines fixing minor errors\n \n2. If user entered a name like AGE (which happens to be the abbreviation\nof an object) as a new Document Definition, say, under option Sort\nDocument Definitions, it was not accepted. This was to prevent entering\nambiguous objects, but was too restrictive since the user may plan to make\nAGE say, a Title, in which case it doesn't create an ambiguous object. AGE\nis now accepted except under option Create Objects.\n \n3. If user entered Document Definition using Fileman with name like DOB\n(which happens to be the abbreviation of an object) and no other fields,\nand closing a small loophole which permitted users to edit objects and\nuser could edit it under Basics from the Sort option, and give it type\nObject. This creates an ambiguous object (if DOB is in boilerplate text,\ncode doesn't know whether to use original object PATIENT DATE OF BIRTH, or\nnew object DOB). User can no longer edit type of DOB to object.\n \n4. When using hidden action Print List (PL), neither P-MESSAGE nor\nBROWSER worked as a device. They work now.\npossibly make them ambiguous.\n \nProblems fixed:\n \n1. Messages "Deleted" and "NOT Deleted" wrapped when user deleted entry\nfrom Document Definition file. Messages are now written on following\nline.\n\n
\nFor a completed description of this patch, please refer to the National\nPatch Module, under TIU*1*20.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*49.\n\n
\nFor a complete description of this patch, please refer to the patch module, \nunder TIU*1*54.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*21.\n\n
\nA complete description of this patch can be found in the National Patch \nModule under TIU*1*56.\n\n
\nA complete description of this patch can be found in the National Patch\nModule under TIU*1*55.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*48.\n\n
\nFor a complete description of this patch, please refer to the patch module, \nunder TIU*1*50.\n\n
\nThe description of this patch may be found on the National Patch Module\nunder TIU*1*51.\n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\nThis build fixes Document Definition code that gave users the erroneous\nmessage NO OWNER when they tried to activate Titles whose boilerplate text\ncontained objects with no owner. Users also received this erroneous\nmessage when TRYing such a Title. The problem is fixed and users now\nreceive the message: BAD/INACTIVE OBJECT IN BOILERPLATE TEXT.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*59.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*45.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*38.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*70.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*69.\n\n
\nThe description of this patch may be found in the National Patch\nModule under TIU*1*65.\n\n
\nA complete description of this patch can be found in the National Patch\nModule under TIU*1*72.\n\n
\nFor a complete description of this patch, please refer to the National\nPatch Module, under TIU*1*57.\n\n
\nThe description of this patch may be found in the National Patch under \nTIU*1*66.\n\n
\nFor a complete description of this patch, please refer to the patch\nmodule, under TIU*1*47.\n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\nFor a complete description of this patch, please refer to the patch module, \nunder TIU*1*39.\n\n
\nFor a complete description of this patch, please refer to the patch module, \nunder TIU*1*52.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*67.\n\n
\nThe description of this build can be found in the National Patch Module\nunder TIU*1*77.\n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1*64.\n\n
\nFor a complete description of this patch, please refer to the patch\nmodule, under TIU*1*62..\n\n
\nThe description of this build can be found in the National Patch Module.\n\n
\nFor a complete description of this patch, please refer to the patch\nmodule, under TIU*1*76.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1.0*11.\n\n
\nFor a complete description of this patch, please refer to the patch module, \nunder TIU*1*53.\n\n
\nThe description of this patch may be found in the National Patch under\nTIU*1*84.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder TIU*1*83.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*73.\n\n
\nThe description of this patch may be found in the National Patch under \nTIU*1*68.\n\n
\nFor a complete description of this patch, please refer to the patch module, \nunder TIU*1*63.\n\n
\nThe description of this patch may be found in the National Patch under\nTIU*1*86.\n\n
\nThe description of this patch may be found in the National Patch under\nTIU*1*87.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*92.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*79.\n\n
\nThis patch is described on the National Patch Module, under patch\nTIU*1*4.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*94.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*80.\n\n
\nThe description of this build can be found in the National Patch Module\nunder TIU*1*90.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch TIU*1*91.\n\n
\nThe description of this build can be found in the National Patch Module,\nunder TIU*1*101.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*102.\n\n
\nThe description of this build can be found in the National Patch Module\nunder TIU*1*99.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*93.\n\n
\n \nThe description of this build can be found in the National Patch Module\nunder patch TIU*1.0*81.\n\n
\nThe description of this patch may be found in the National Patch under\nTIU*1*89.\n\n
\nThis patch is described on the National Patch Module, under patch\nTIU*1*7.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*98.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*82.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*103.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*104.\n\n
\nThe description of this patch may be found in the National Patch under\nTIU*1*88.\n\n
\nThe description of this build can be found in the National Patch Module\nunder the heading of TIU*1*78.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*107.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*58.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder TIU*1*108.\n\n
\nFor a complete description of this patch, please refer to the patch\nmodule, under TIU*1*61.\n\n
\nTEXT INTEGRATION UTILITIES v1.0\n \n+ Ability to view and manipulate clinical documents from a single program\n+ Upload capability for many types of documents\n+ Improved searching and retrieving capabilities across documents\n+ Less duplication of effort for clinicians, managers, and other staff\n+ Boilerplate support\n+ Links to the Computerized Patient Record System (CPRS), Authorization/\n Subscription Utility (ASU), Incomplete Record Tracking (IRT), and\n interfacility document transfer\n \n \nCosts\n \n+ Planning your Document and User Class hierarchies.\n+ Setting up the Document hierarchy so that your current Progress Notes\n can be converted into the new TIU structure\n+ Setting up and populating the User Classes (ASU)\n+ Setting up the Upload Utilities and other TIU parameters\n+ Converting existing progress notes and discharge summaries to TIU\n+ Switching Progress Notes and Discharge Summary menus to TIU menus\nText Integration Utilities (TIU) is a collection of software tools that\nmanage clinical documents in a standardized way. The initial release of\nVersion 1.0 includes Discharge Summary and Progress Notes. TIU replaces\nthe previous versions of these DHCP packages, while incorporating all of\nthe functionality of them.\n \nBenefits of TIU\n\n
\nThis package is designed to manage the capture, retention, retrieval and \nprocessing of any patient-visit-oriented document. Its first version will \nsupport Discharge Summaries, Progress Notes, and Consult Results.\n\n
\nPharmacy Data Management PATCH PSS*1*2. This fixes a no-compiled routine\nand null subscript error.\n\n
\nThis patch utilizes the new NDF APIs.\n\n
\nThe Computerized Patient Record System (CPRS) V. 1.0 has requested a \nmodification to an Application Programming Interface (API) from Pharmacy\nData Management V. 1.0. The modified API will provide CPRS with a flag to\nindicate a default Medication Route is being supplied from the PHARMACY\nORDERABLE ITEM (#50.7) file.\n\n
\nThis Pharmacy Data Management (PDM) patch is part of the Patient Financial\nreplacement system. The project consists of the implementation of the\nbilling replacement system, business process improvements, and\nenhancements to VistA to support integration with the COTS billing\nreplacement system. Significant changes to VistA legacy systems and\nancillary packages are necessary.\n \nSome of the PFSS software components are not operational until the PFSS\nOn/Off Switch, distributed with patch IB*2*260, is set to "ON". The\nability for the local site to set the switch to "ON will be provided at\nthe appropriate time with the release of a subsequent Integrated Billing\nServices System (PFSS) project. PFSS patches are being released on various\npatch.\n \nFor more information about the PFSS project, review the documentation\naccompanying this patch and refer to the following website:\nhttp://vista.domain.ext/billreplace/.\n \n \nFunctional Description:\n=======================\nThe Charge Description Master (CDM) is an industry standard financial tool\nschedules. Some patch functionality will not be active until a new PFSS\ncommon to all commercial billing systems and used in virtually every\nprivate hospital. The CDM is a comprehensive listing of all services\nperformed, drugs supplied, or supplies provided in a particular hospital\nalong with the value of those services/drugs/items, or charge amounts.\nEach of these entries are represented by a Charge Code, and the Charge\nCode is made up of a Department Code and Service Code. The Charge Code for\nPharmacy will be the department code 160 concatenated with the assigned\nService Code for the drug. The Department Code 160 will not be stored in\nany files and the Service Code will be established/approved by a central\nCDM Change Control Board (CCB). The implementation of the COTS billing\nswitch is activated during final implementation. PFSS will initially be\nsystem requires the VA PRODUCT file (#50.68)/DRUG file (#50) to link the\nservice master Service Code to every Pharmacy prescription fill or refill.\nFor drugs that are not associated with an entry in the VA PRODUCT file\n(#50.68), the approved Service Code must be populated by the user.\n \n \nTechnical Description:\n======================\nThis PDM patch PSS*1*92 provides the following functionality needed to\nsupport the PFSS project:\nimplemented at select pilot sites ONLY.\n \n1. A new SERVICE CODE field (#400) was added to the DRUG file (#50).\n2. The PSSCOMMON Input template was modified to accommodate the new\n SERVICE CODE field (#400) to be used with the DRUG ENTER/EDIT [PSS DRUG\n ENTER/EDIT] option for drugs that are not associated with an entry in\n the VA PRODUCT file (#50.68).\n3. The Integration Agreement (IA) #4483 was modified to include the new\n SERVICE CODE field (#400).\n \nThe purpose of the PFSS project is to prepare the Veterans Health\nInformation Systems and Technology Architecture (VistA) environment for\nthe implementation of a commercial off-the-shelf (COTS) billing\n\n
\n1) Only allow uppercase alphabet for the NAME field in files #51.1\nand #51.\n2) Allow elligible drugs to be marked for 'OP External Dispense'.\n\n
\nThis patch supports the National Council for Prescription Drug Programs (NCPDP) \nclaim; updates to the Rx Activity Log; and permanent storage of Claims activity \ninformation as reported by the ECME Billing Events Report. \n \nThis patch restores the ability to edit the DAW CODE field through the Drug \nEnter/Edit [PSS DRUG ENTER/EDIT] option in the Pharmacy Data Management (PDM)\napplication. This field was originally created by the patch PSS*1*90 (see item\n#3) but was unintentionally removed by patch PSS*1*92.\n \nThe following input template is included in this patch:\n \nstandard which was adopted under the Healthcare Insurance Portability and \n Template Name File Name (Number)\n ------------- ------------------\n PSSCOMMON DRUG (50)\nAccountability Act (HIPAA) for pharmacy claims. This patch is one of six to be\nreleased. Three patches will be released in a KIDS multi-build distribution \ncontaining: BPS*1*3, PSO*7*247, and IB*2*342. Three patches will be released\nindividually and they are: PRCA*4.5*247, PSX*2.0*62, and PSS*1.0*115.\n \nEnhancements included in the release of the six patches are a new option that \nwill enable the user to reopen a closed Electron Claims Management Engine (ECME)\n\n
\nThis patch contains updated Application Program Interfaces (APIs) that will \nPatient file (#55). \n \nThe DIC^PSSDI API has been modified to allow drug selection with matches\nto certain VA Classes that are passed to the call.\n \nClasses to be included or excluded are to be set up in the PSSVACL array\nwithin the DIC component.\n \nFor example, if only drugs with a VA Class of DX201 & DX202 were to be\navailable for selection, the local variable array would look like this:\nbe used by calling applications that currently do direct global reads or \n \nPSSVACL("DX201")=""\nPSSVACL("DX202")=""\nPSSVACL("R")="" - The "R" means only drugs with these classes will be\n available for selection. If these classes were to be\n excluded, the letter "P" would be used instead.\n \n \nA new API was added to routine PSS51P1. The PSSDQ component displays all \nthe entries in the Administrative Schedules file (#51.1). \nwrites to the Pharmacy Data Management files.\n \n \nThe ORDERABLE ITEM STATUS TRACKER (#81) field has been added as a returned\ndata element for the PSS^PSS59P7 API on the Pharmacy System file (#59.7).\n \nThe ORIGINAL WARD (#9), OTHER PRINT INFO (#31) & MED ROUTE (#132) fields \nwere added to the PSS436 component of the PSS55 API on the Pharmacy \n\n\nThis patch enhances an original Pharmacy Data Management API call \nRe-Engineering (PRE) API Manual.\n \nAdditionally, this patch introduces an API STATUS^PSS55MIS which requires\nthree parameters. The set of codes for STATUS field in the PHARMACY\nPATIENT file (#55) subfiles is returned. This API will invoke the\nFIELD^DID Fileman call and data will be returned to the calling\napplication as specified in the FIELD^DID FileMan documentation. \nSpecifications for this API can be found in the Pharmacy Re-Engineering\n(PRE) API Manual.\n \nDATA^PSS50. By replacing FileMan calls with direct reads, data retrieval \nFinally, this patch introduces CLINIC^PSS55MIS which requires three \nparameters. This API returns a clinic from the HOSPITAL LOCATION file \n(#44) based on a provided order number and patient DFN. This API invokes \nthe GETS^DIQ data retrieval call. Specifications for this API can be \nfound in the Pharmacy Re-Engineering (PRE) API Manual.\nfrom the DRUG file (#50) speed has been greatly improved. Specifications \nfor this API can be found in the Pharmacy Re-Engineering (PRE) API Manual.\n \nThis patch also enhances an original Pharmacy Data Management API call \nALL^PSS51P2. By replacing FileMan calls with direct reads, data \nretrieval from the MEDICATION ROUTES file (#51.2) speed has been greatly \nimproved. Specifications for this API can be found in the Pharmacy \n\n
\n1. In response to a patient safety issue, the Computerized Patient Record \na utility is provided to allow assignment of a route to multiple \norderable items, based on the dosage form. A new menu option has been set \nup for this feature. The new menu option is [PSS ADD DEFAULT MED ROUTE] \nand will be removed in a future patch.\nSystem V. 1.0 was modified to no longer always use a default in the \nmedication ordering dialog. Therefore, sites are required to enter a \ndefault in the PHARMACY ORDERABLE ITEM file (#50.7). However, in support \nof the previous business logic, a default of ORAL was not allowed. This \npatch changes this requirement and allows ORAL as a default medication \nroute. HD 144208, PSI-06-063\n \n2. In order to assist sites in assigning a new default medication route, \n\n
\nAs part of the Outpatient Pharmacy V. 7.0 Laser Labels Phase II project, \nanother parameter is being added to turn on sending the new warnings to\nthe Outpatient Pharmacy Automation Interface (OPAI). This is to \naccommodate vendors who may need to make changes to receive the new \nwarnings.\n \nCurrently the Bedford CMOP is the only CMOP not ready to receive the new\nformat.\n \nUntil the parameters are turned on, warning labels from the old RX CONSULT\nfile (#54) are used. When they are turned on, warnings from the WARNING\na new commercial data source is utilized to provide warning label \nLABEL-ENGLISH (#50.625) or the WARNING LABEL-SPANISH (#50.626) file will\nbe used. When the parameters are turned on, the "Do not transfer" warning\nlabel 20 from the old RX CONSULT file (#54) is automatically added, when\napplicable, during label printing, transmitting to CMOP, or sending to\nOPAI.\n \nExample warning labels for a drug when the warning source is set to "New":\n \n Take medication on an empty stomach one hour before or two to the three \n hours after a meal unless otherwise directed by your doctor.\ninformation. \n \n This drug may impair the ability to drive or operate machinery. Use care\n until you become familiar with its effects.\n \n CAUTION: Federal law prohibits the transfer of this drug to any person\n other than the patient for whom it was prescribed.\n \n \nThis patch is required by PSO*7*200 which will send the new warning label \ntext to OPAI and by PSX*2*54 which will send the new warning label text to\n \nCMOP.\n \n \nThe following changes are included in this patch:\n \nData Dictionary Changes:\n=======================\nNew fields:\n1. CMOP WARNING LABEL SOURCE field (#16.1) in the PHARMACY SYSTEM file\n(#59.7).\nA parameter was provided by patch PSS*1*87 to turn on the new warning\n \nThe new warning label processing is not fully functional for CMOP until\nthis field is set to "N" for "New" in the Pharmacy System Parameters Edit\n[PSS SYS EDIT] option. \n \n2. OPAI WARNING LABEL SOURCE field (#16.2) in the PHARMACY SYSTEM file\n(#59.7).\n \nThe new warning label processing is not fully functional for the \nOutpatient Pharmacy Automation Interface (OPAI) until this field is set to\nlabel format. This is currently being used in association with printing\n"N" for "New" in the Pharmacy System Parameters Edit [PSS SYS EDIT]\noption.\n \n \nRoutine Changes:\n================\nRoutine PSSYSP was modified to prompt for the above new fields.\nExample:\n \nSelect OPTION NAME: PSS SYS EDIT Pharmacy System Parameters Edit\nlaser labels. However, since not all Consolidated Mail Outpatient\nPharmacy System Parameters Edit\n \nPMIS PRINTER: L8150$PRT// \nPMIS LANGUAGE: English// \nWARNING LABEL SOURCE: NEW// \nCMOP WARNING LABEL SOURCE: ?\n Enter "N" for NEW to use commercial data source for CMOP warning \nlabels.\n Choose from: \n N NEW\nPharmacy (CMOP) facilities are reprogrammed to receive the new format, a\nCMOP WARNING LABEL SOURCE: N NEW\nOPAI WARNING LABEL SOURCE: N NEW\nnew parameter is being added for turning on the new warnings for CMOP. And\n\n
\nThis patch adds ORDERABLE ITEM field (#108) from the PHARMACY PATIENT \n* PSS435^PSS55\n* PSS436^PSS55\n \nAdditionally, this patch clears up an issue in DIC^PSSDI, DATA^PSS50, \nALL^PSS51P2, and MIX^PSSDI where in rare circumstances, an error could\noccur due to incorrect API initialization.\n \nFinally, this patch introduces the parameter PSSFREQ to AP^PSS51P1. \nPSSFREQ is compared to the FREQUENCY field (#2) in the ADMINISTRATION \nSCHEDULE file (#51.1) to filter records based on the frequency of \nfile (#55), NAME field (#.01) from the PHARMACY ORDERABLE ITEM file \ndelivery.\n(#50.7), DOSAGE FORM field (#.02) from the PHARMACY ODERABLE ITEM file \n(#50.07), and NAME field (#.01) from the DOSAGE FORM file (#50.606) to \nthe following APIs.\n \n* PSS431^PSS55\n* PSS432^PSS55\n* PSS433^PSS55\n\n
\nFixes the one time PRN orders problem.\n\n
\nThis patch fixes data dictionaries for Pharmacy Patient (#55), Pharmacy\nSystem (#59.7), and Drug (#50) files, as well as a couple of enhancement\nroutines.\n\n
\nThis patch contains the second quarter enhancements for the Pharmacy Data \ndefined must have a subtype prefixed with "P-". This prefix in the \nsubtype indicates that the device is a printer. If no data is defined in\nthis multiple, the ScripTalk printer tied to the division will be used. \nThe use of this multiple builds upon existing ScripTalk functionality, so\na divisional ScripTalk device must be defined for the mapped device\nfunctionality to work properly and to have a default device defined.\n \n a. LABEL PRINTER TO BE MAPPED field (#.01) - This field contains \nthe Pharmacy label printer(s) that the ScripTalk device is mapped. When \nthe printer device defined in this field is selected as the Pharmacy \nManagement V 1.0 package. The following data dictionary additions are\nprint device by the user, ScripTalk labels will print on the \ncorresponding mapped ScripTalk device.\n \n b. SCRIPTALK DEVICE field (#.02) - This field contains the ScripTalk \nprint device that will be tied to regular Pharmacy label device(s) \ndefined in the "LABEL PRINTER TO BE MAPPED" field.\nincluded for PHARMACY SYSTEM file (#59.7) and supports modifications made \nin Outpatient Pharmacy patch PSO*7*200.\n \n1. SCRIPTALK PRINT DEVICE MAPPING multiple (#47) - adds the capability \nto tie a ScripTalk printer to regular Pharmacy label printer(s) to \ncontrol where the ScripTalk labels print for multi-divisions. Multiple \nprint devices may be mapped to a ScripTalk printer, and any device \n\n
\nWith the deployment of Cache version 5, it was discovered that the short\nmodifies all routines that currently use a lock timeout value of less than\n3 seconds to check for the node ^DD("DILOCKTM") and to use the value\ndefined there, otherwise the lock timeout value is set to a default value\nof 3 seconds.\nlock timeout values could generate a lock failure. Patch DI*22*147, which\nhas already been released, provided a solution to resolve this issue and\nfuture lock issues.\n \nThis patch instituted a new default lock timeout of three seconds based on\na global node setting of ^DD("DILOCKTM")=3.\n \nIn order to avoid the lock issue in Pharmacy Data Management, this patch\n\n\n1. A site reported a problem with the medication route being blank on the\n \n2. During internal testing, it was discovered that there was a problem \nwith the Application Programming Interface (API) handled by routine \nPSS55. This patch corrects this problem.\n \n3. To assist Pharmacy in appropriately setting the new PROMPT FOR INJ. \nSITE IN BCMA field (#8), a search routine will execute when this patch is \ninstalled. The purpose of this routine is to look for all Medication \nRoute abbreviations that contain ID, IV, IM, SC or SQ. A message with the \nsubject of "PDM - Check Med Route Abbreviations" will be sent to the \nBar Code Medication Administration (BCMA) V. 3.0 Virtual Due List. During\nperson who installs the patch.\ninvestigation of possible corrections for this, it was determined that\nanother issue needed to be addressed with how to determine when to prompt\nfor an injection site. This patch assists to correct these problems by\nadding the PROMPT FOR INJ. SITE IN BCMA field (#8) to the MEDICATION\nROUTES file (#51.2). In addition, the new field has been added to the\ninput template PSS MEDICATION ROUTES. HD0000000166204, HD0000000164890,\nPSI-06-152, PSI-06-158\n\n
\nThe general purpose of this patch is to meet the requirements in support\nthe patches.\n \nThis patch modifies the Pharmacy Data Management V. 1.0 application as \ndescribed below:\n \n1. The following fields were added to DRUG file (#50) for determining\n metric quantity for electronic 3rd Party billing:\n \n a. NCPDP DISPENSE UNIT field (#82) - Allows entry of EA for EACH, GR\n for GRAMS or ML for MILLILITERS.\nof ePharmacy enhancements. This patch is one of five to be released. Three\n \n b. NCPDP QUANTITY MULTIPLIER field (#83) - This field contains the \n number that will be multiplied by the quantity in the prescription\n in order to determine the correct quantity to bill electronic 3rd\n party insurance companies. Only products with an NCPDP DISPENSE\n UNIT of GM or ML should have a value different than 1 (one) in this\n field. Numbers between 0.001 and 99999.999 are allowed entry \n into this field.\n \n2. The two fields above will be auto-populated by a post-install routine,\npatches will be released in the KIDS multi-build distribution BPS PSO IB\n which will be executed when this patch is installed. Although the \n majority of drugs will be updated with EA (EACH) for the NCPDP DISPENSE \n UNIT and 1 (one) for the NCPDP QUANTITY MULTIPLIER fields, a large \n number of drugs will be updated with GM (GRAMS) or ML (MILILLITERS). \n Furthermore, some drugs will also have a number different for the NCPDP\n QUANTITY MULTIPLIER field. The post-install routine relies on a \n built-in list provided by the National Drug File (NDF) group that \n contains the necessary information for the update being performed. \n \n Once this patch is installed, the user should be able to verify the\nBUNDLE 2.0, which contains BPS*1*5, IB*2*363, and PSO*7*260. Patches\n auto-population results by running the following Fileman Print option:\n \n \n OUTPUT FROM WHAT FILE: DRUG// \n SORT BY: GENERIC NAME// NCPDP DISPENSE UNIT \n START WITH NCPDP DISPENSE UNIT: FIRST// \n WITHIN NCPDP DISPENSE UNIT, SORT BY: GENERIC NAME \n START WITH GENERIC NAME: FIRST// \n WITHIN GENERIC NAME, SORT BY: \n FIRST PRINT FIELD: GENERIC NAME;@ \nPSX*2*63 and PSS*1*127 will be released as stand-alone patches. Since\n THEN PRINT FIELD: NCPDP DISPENSE UNIT \n THEN PRINT FIELD: NCPDP QUANTITY MULTIPLIER \n THEN PRINT FIELD: \n Heading (S/C): DRUG LIST// \n DEVICE: ;;999 UCX/TELNET Right Margin: 80// \n \n \n3. For the DRUG ENTER/EDIT [PSS DRUG ENTER/EDIT] option, the PSSCOMMON \n input template for DRUG file (#50) was modified to allow entry/edit of\n the NCPDP DISPENSE UNIT field (#82) and the NCPDP QUANTITY MULTIPLIER \nthere is an implementation dependency between the multi-build distribution\n field (#83). The following give additional information on definition \n and validation of these fields:\n \n a. When new drugs are defined, the values of EA for EACH and 1 (one)\n will be the default values for these new fields.\n \n b. When the NCPDP DISPENSE UNIT is changed from one value to another, \n the NCPDP QUANTITY MULTIPLIER will be defaulted to 1 (one) and a \n message stating such will be displayed. If the NCPDP QUANTITY\n MULTIPLIER field already contains 1 (one), no change will be made\nand the stand-alone patches, PSX*2*63 and PSS*1*127 must be installed\n nor will a message be displayed.\n \n c. When a valid value greater than or less than 1 (one) is entered for\n the NCPDP QUANTITY MULTIPLIER, a warning message will be displayed\n stating that typically a value of 1 (one) should be defined for\n this field. Then the user will be prompted to continue processing\n thereby accepting the new value or to edit and view extended help\n text for the type of NCPDP DISPENSE UNIT selected. If the user\n elects to ^ (shift six) to exit the "Ok to continue (Y/N)" prompt,\n the system will default the NCPCP QUANTITY MULTIPLIER to 1 (one)\nprior to the installation of the multi-build. For more specific\n and give a warning message stating such.\n \n \n4. The LOOKUP INTO DISPENSE DRUG FILE [PSS LOOK] option was modified to \n list the new NCPDP DISPENSE UNIT and NCPDP QUANTITY MULTIPLIER fields\n after the PRICE/DISPENSE UNIT field.\ninstructions please refer to the installation steps provided in each of\n\n
\nDuring testing of the Bar Code Medication Administration (BCMA) project \nfield (#128) of the UNIT DOSE sub-file (#55.06) of the PHARMACY PATIENT\nfile (#55) which is exported in this patch.\nBCMA-HSC Phase III, an issue was discovered with the order flag comments \nfor unit dose orders. There is not enough space to store the entire \ncomment, so the text is truncated. This patch corrects this problem for \nBCMA by storing the most recent text in an additional location. The \ncomment will still be stored in the current location. It will also be in \nthe MOST RECEMT FLAG COMMENT field (#129) of the NON-VERIFIED/PENDING file\n(#53.1) which is exported in an Inpatient Medications V5.0 patch. For\nactive unit dose orders, it will be stored in the MOST RECENT FLAG COMMENT\n\n
\nThis patch will correct the issues reported in:\n \n1) HD68616 - PSSMARK DRUG INACTIVE DATE IN FUTURE BLOCKS CMOP MARK\nTODAY\n2) HD70218 - PSSHLU Drug file edits change value in orderable item\nfile\n\n
\nThis patch will update the heptext for the DEA field in the DRUG file. As \nwell as send a mailman message concerning the changing DEA codes.\n\n
\nThis patch will correct the issues reported in:\n \nHD229420 - PSSHLU Orderable item is active but not appearing in CPRS\n\n
\nThe following data dictionary addition is included for PHARMACY SYSTEM\n \n Last Date Auto-Expire Processed\n INPUT TRANSFORM: S %DT="E" D ^%DT S X=Y K:X<1 X\n LAST EDITED: MAY 18, 2007\n HELP-PROMPT: Last Date Auto-Expire Processed\n DESCRIPTION: This is the last date that the nightly\n auto-expire processed. Processing will \n continue from this date the next time the\n job runs.\n \nfile (#59.7) and supports modifications made in Outpatient Pharmacy patch\n TECHNICAL DESCR: This is the last date that the nightly\n auto-expire processed. Processing will \n continue from this date the next time the\n job runs and will expire prescriptions with\n expiration dates up to and including DT-1.\nPSO*7*257.\n \n \nField Description:\n==================\n \n59.7,49.95 DATE AUTO-EXPIRE COMPLETED 49.99;8 DATE\n\n
\nThis patch will correct the issues reported in:\n CLASS field (#25) index (^PSDRUG("VAC") and identify drugs with\n multiple VAC indexs. If a drug has multiple indexs, re-index the\n VAC index. After the ^DRUG("VAC" has been re-indexed, send a MailMan \n message with the names, old VA DRUG CLASS indexs and the new VA\n DRUG CLASS index.\n \n1) HD0000000194979 - Orderable Item dialog box issue\n Modify the INPUT TRANSFORM for the PHARMACY ORDERABLE ITEM file \n (#50.7) SYNONYM subfile (#50.72) SYNONYM field #2 to use \n S X=$$TRIM^XLFSTR(X,"R"," ") to strip trailing spaces. \n \n2) HD0000000177768 - Lookup by VA Class brings up incorrect meds\n Create PSSP130 routine to step through the DRUG file (#50) VA DRUG\n\n\nThis patch fixes an error which occurs when an IV order is entered\nwith a non-standard schedule which contains a leading space. It also\ncorrects an error that occurs when an IV or Unit Dose order is entered in\nthe Computerized Patient Record System (CPRS) that contains an invalid\nschedule. This patch makes changes to the Pharmacy Data Management\nroutines that are used to control the validation of schedules when orders\nare entered in CPRS and Inpatient Medications.\n\n
\nThis patch will create a post install routine that will loop \nthrough the Drug file (#50) and get all the Local Possible Doses\nfor each drug and call the API to reformat it. A report will \nthen be generated that will display the drug ien, drug name, \noriginal Local Possible Dose and the reformatted Local Possible \nDose. The report will be sent to the holders of the PSNMGR key\nand Venessa France, developer of the patch.\n .\n Venessa France, developer of the patch.\n\n
\n1. In support of the project Inpatient Medications Requirements for \n \n3. In support of the Computerized Patient Record System (CPRS) GUI v27 \nrelease, the validation of schedules from the GUI has been modified. \nThe change was to allow day-of-week schedules to be entered in the \nformat: day@schedule. Schedule, in this case, is an already defined \nschedule such as BID. So, now a day-of-week schedule may be entered as\nMO-WE-FR@BID to signify you want to use the BID administration times \non Monday, Wednesday and Friday.\n \n4. In support of CPRS GUI v27, a modification has been made to the \nthe Special Focus Group Initial Request Analysis (IMR) Phase III, \nlist of available Medication Routes sent back to CPRS from Inpatient\nPharmacy when using the IV Dialog. If there is one orderable item\nin the order, Inpatient Pharmacy will return any default med route\nthat may be defined in the Pharmacy Orderable Item File #50.7 along\nwith any other med routes defined for the dosage form #50.606. \nDuplicate entries will be removed. If there is more than one orderable \nitem in the order, Inpatient Pharmacy will return a list of the common\nmed routes that match all orderable items.\n \n5. In support of CPRS GUI v27, remedy ticket, HD0000000220080 - "^ in \ntwo changes have been made in the input template PSSJ SCHEDULE EDIT. \nthe Schedule field" was addressed.\n \nProblem:\n--------\nUsers are allowed to include an "^" in the schedule when placing an \norder in CPRS GUI.\n \nResolution:\n-----------\nRoutine PSSGSGUI will be modified to disallow an "^" in the text of a\nFirst, if the schedule type is continuous and it is an odd schedule, \nschedule.\n \n6. The routine PSS0088 is being deleted with this patch. The routine\nwas part of patch PSS*1.0*88, and was used simply as a tally routine\nto identify medication routes that needed to be reviewed when the\nfunctionality of PSS*1.0*88 was installed. The tally routine's\nfunctionality is no longer necessary, so the routine will be deleted.\n \n7. In support of CPRS GUI v27, the array of schedules from the \nADMINISTRATION SCHEDULE file #51.1 that is returned to CPRS for schedule\nthe system will no longer allow the entry of administration times. \nselection on an order is being modified. Currently, a site can have\nmultiple schedules with the same name for the same package. The array\nof schedules presented for selection in CPRS GUI v26 only takes the\nschedule with the lowest IEN number in the ADMINISTRATION SCHEDULE file\n#51.1 if a duplicate exists.\n \nWith the changes in CPRS GUI v27, if there is a duplicate schedule,\nand if one of them contains ward-specific admin times for the ward\nlocation of the patient, the schedule returned for inclusion in the\narray of selectable schedules in CPRS will be the one with the ward-\nContinuous, non-odd schedules will still require administration times.\nspecific admin times. If no duplicate has ward-specific admin times\nfor the ward location of the patient, the schedule with the lowest\nIEN number will be returned. If both (or more than one)\nduplicate schedules have ward-specific admin times for the ward\nlocation of the patient, the schedule with the lowest IEN number in the\nADMINISTRATION SCHEDULE file #51.1 will be the schedule in the array\nreturned to CPRS.\n \n2. The second IMR change for the input template is if the schedule type\nis on-call, the system will no longer require a frequency.\n\n
\nThis patch will address the issues in Remedy tickets:\n \n1)HD0000000206450 - & in the NOUN field of the Dosage Form file\n When the NOUN in the DOSAGE FORM contains a "&", it causes\n CPRS to error when ordering medications.\n \n2)HD0000000249646 - 6 VA CLASSIFICATION Field\n The VA CLASSIFICATION field (#2) of the DRUG file (#50) allows user to \n delete the data in this field which is matched to National Drug File.\n\n
\nThis patch contains a set of APIs to be used by Clinical Reminders. \nThe calls are all to routine PSSCLINR. The APIs are:\n \nIX(PSSCRIX,PSSCRIV) Returns AND or VAC index of File 50\nDRUG(PSSCLID) Returns the Drug name from file 50 \nITEM(PSSCLII) Returns the Pharmacy Orderable Item pointer from file 50.\nING(PSSING) Return Drug Ingredient IEN from file 50.416 \nNEPS() Return Number of entries in file 55 \n\n
\nThis patch has enhancements which extend the capabilities of the Veterans \nactivate unless instructed specifically by the CBO.\n \nThis patch is being released along with PSO*7*303 and IB*2*405. These \npatches can be installed in any order but the full functionality contained\nwithin these patches will not be available until all 3 patches are\ninstalled.\n \nThis patch modifies the Pharmacy Data Management v1.0 application as \ndescribed below:\n \nHealth Information Systems and Technology Architecture (VistA) electronic \n1. A new Drug Enforcement Administration (DEA) Special Handling code, N\nfor Nutritional Supplement, was added as a selection to the DEA SPECIAL\nHDLG prompt for DRUG ENTER/EDIT [PSS DRUG ENTER/EDIT] option. Once \nOutpatient Pharmacy patch PSO*7*303 and Integrated Billing patch IB*2*405\nis installed, any drug defined with this new code will be treated in the\nsame manner as supply items and investigational drugs. The N DEA Special \nHandling code must be defined manually.\npharmacy (ePharmacy) billing system.\n \nAll sites should install this patches regardless of whether or not they \nhave been activated for ePharmacy by the Central Business Office (CBO). \nAfter the installation of these patches, the activation status of the \nsite will not be impacted. As before, activation of the ePharmacy \nproduct will require instructions provided by the CBO. Sites are not to \n\n
\nThis patch provides the functionality needed to prepare for the release of\nPharmacy Re-Engineering V. 0.5, which will change the current Pharmacy\nOrder Checking system from using the data stored in Vista to using data\nfrom the First DataBank commercial database system. There is set-up work \nthat is requred to be completed prior to the installation of Pharmacy \nRe-Engneering V. 0.5, and this patch provides the tools needed to complete\nthat set-up work.\n\n
\nThis patch has enhancements which extend the capabilities of the Veterans \n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*289\n INTEGRATED BILLING (IB) V. 2.0 IB*2*384\n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*7\n \nThe last three patches (PSO*7*289, IB*2*384 and BPS*1*7) will be released \nin the Kernel Installation and Distribution System (KIDS) multi-build \ndistribution BPS PSO IB BUNDLE 3.0. Patches PSX*2*65 and PSS*1*131 will \nbe released as stand-alone patches. Since there is an implementation \ndependency between the multi-build distribution and the stand-alone \npatches, PSX*2*65 and PSS*1*131 must be installed prior to the \nHealth Information Systems and Technology Architecture (VistA) electronic \ninstallation of the multi-build. For more specific instructions please \nrefer to the installation steps provided in each of the patches.\n \nAll sites should install these patches regardless of whether or not they \nhave been activated for ePharmacy by the Central Business Office (CBO). \nAfter the installation of these patches, the activation status of the \nsite will not be impacted. As before, activation of the ePharmacy \nproduct will require instructions provided by the CBO. Sites are not to \nactivate unless instructed specifically by the CBO.\n \npharmacy (ePharmacy) billing system. Below is a list of all the \nThis patch modifies the Pharmacy Data Management v1.0 application as \ndescribed below:\n \n1. A new Drug Enforcement Administration (DEA) Special Handling code, U\nfor Sensitive Diagnosis, was added as a selection to the DEA SPECIAL HDLG\nprompt for DRUG ENTER/EDIT [PSS DRUG ENTER/EDIT] option. When a signed\nRelease of Information (ROI) is on file and the drug is marked with this\nnew code, the drug may be third party billable. Drugs must be manually\nmarked with this new code, and this functionality works in conjunction\nwith ROI modifications made in IB*2*384.\napplications involved in this project along with their patch number:\n \n APPLICATION/VERSION PATCH\n --------------------------------------------------------------\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*65\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*131\n\n
\n\n\nThis patch adds a MUMPS style cross-reference to the FIRST \nSERVICE DATE field (#.07) in the PHARMACY PATIENT file (#55). \nWhen the FIRST SERVICE DATE field (#.07) is updated for a \npatient then the cross-reference is triggered and the patient \nis queued for transmission.\n\nThe following applications were also updated as part of the \nPBM Extracts Enhancement #3 project:\n \nThis patch addresses a request which support the Pharmacy \n Application/Version Patch\n -------------------------------------------------------------\n Pharmacy Benefits Management V. 4.0 PSU*4.0*5\n Inpatient Medications V. 5.0 PSJ*5.0*161\n Outpatient Pharmacy V. 7.0 PSO*7.0*170\n Registration V. 5.3 DG*5.3*671\n \n\n\nBenefits Management (PBM) Extracts Enhancement #3 \nproject. In order to allow the retransmission of only those \npatients who have had demographic updates, Pharmacy \nData Management V. 1.0 was modified to build an entry \nfor re-transmission in PBM PATIENT DEMOGRAPHICS \nfile (#59.9) whenever the FIRST SERVICE DATE field (#.07) \nin the PHARMACY PATIENT file (#55) is updated.\n\n
\nThis build is a patch to DRUG file (#50) which changes the data\ndictionary for fields NATIONAL DRUG FILE ENTRY (#20) and PSNDF\nVA PRODUCT NAME ENTRY (#22) to pointers. This patch requires\nNational Drug File V. 4.0 to be installed.\n\n
\nDescription:\n \nNO YES All med routes from dosage form \n display. Default med route \n pre-populates the selection box.\n \nNO NO All med routes from dosage form \n display. Nothing pre-populates the\n selection box.\n \nAdditionally, this patch will provide a new option called Default Med\nRoute For OI Report [PSS DEF MED ROUTE OI RPT] that will be added to the\nProblem:\nMedication Routes Management [PSS MEDICATION ROUTES MGMT] menu. The site\ncan use this report to identify the current default medication route for\nthe orderable item. Here is an example of the report:\n \n \nDEFAULT MED ROUTE FOR ORDERABLE ITEM REPORT JUN 17,2009 PAGE 1\n \nOI NAME DOSAGE FORM ASSOCIATED ROUTES DEFAULT ROUTE DRUG\n--------------------------------------------------------------------------\n \n--------\nIBERET LIQUID ORAL (BY MOUTH) IBERET-500 ORAL\nIBUPROFEN TAB ORAL (BY MOUTH) IBUPROFEN 600MG\nIDOXURIDINE OINT,OPH RIGHT EYE\n LEFT EYE\n BOTH EYES IDOXURIDINE 0.5%\nIMIPRAMINE TAB ORAL (BY MOUTH) IMIPRAMINE 25MG\n IMIPRAMINE 50MG\nINDOCYANINE INJ,SOLN INTRAMUSCULAR\n INTRAVENOUS INTRAVENOUS INDOCYANINE 25MG\nINSULIN INJ INTRAMUSCULAR\nCurrently, for unit dose orders and Outpatient Pharmacy orders, all\n INTRAVENOUS\n ORAL\n SUBCUTANEOUS INTRAVENOUS INSULIN LENTE\n INSULIN NPH\nmedication routes for the dosage form of the orderable item are being\ndisplayed in CPRS as possible medication routes to be selected. Even if\nan orderable item is to be given only Intramuscular (IM), the provider\nsees a dropdown list to select a potentially inappropriate medication\nroute of Subcutaneous (SC) or Intravenous (IV).\n \n===========\nResolution:\n-----------\nThis enhancement affects both Inpatient Medications unit dose orders\nentered via the Inpatient Medications order dialog in CPRS as well as\nOutpatient Pharmacy orders entered via CPRS. A new parameter will be added\nto the PHARMACY SYSTEM file (#59.7) to support this functionality (see\nbelow). With this parameter set to YES, CPRS order dialogs will display\nonly the default medication route for the orderable item in the medication\nroute selection list in CPRS if a default medication route is defined in\nthe PHARMACY ORDERABLE ITEM file (#50.7). If there is no default\n \nmedication route defined for the orderable item, then the current\nfunctionality will be retained and all possible medication routes for the\ndosage form will be displayed to the provider for selection in CPRS.\nRoutine PSSJORDF will be modified for this enhancement.\n \nThis enhancement adds the DEFAULT MED ROUTE FOR CPRS field (#80.7) to the\nPHARMACY SYSTEM file (#59.7) to support the functionality of this patch.\nThe field will serve as a toggle, allowing the site to choose whether they\nwant to implement the features of this patch in their system. This field\nis maintained by the Pharmacy System Parameters Edit [PSS SYS EDIT]\nThis enhancement is an interim resolution approved by the Inpatient\noption. The default for this field is YES when first accessing this field\nfrom this option. This field may be set to YES or NO. An example of\nsetting this to YES appears below.\n \nExample screen:\n \n Select Pharmacy Data Management Option: Pharmacy System Parameters Edit\n PMIS PRINTER: NULL DEVICE//\n PMIS LANGUAGE: English//\n WARNING LABEL SOURCE:\nMedications Workgroup and Pharmacy Legacy Quarterly Enhancement (PLQE)\n CMOP WARNING LABEL SOURCE:\n OPAI WARNING LABEL SOURCE:\n AUTOMATE CPRS REFILL:\n DEFAULT MED ROUTE FOR CPRS: Y YES\n \nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n \n59.7,80.7 DEFAULT MED ROUTE FOR CPRS 80;7 SET\nUser Group for Patient Safety Issue PSI 08-026, PSPO #852 as described in\n \n '0' FOR NO;\n '1' FOR YES;\n LAST EDITED: MAY 28, 2009\n HELP-PROMPT: Enter Y to display only the default med route\n in CPRS or N to continue with the current\n functionality.\n DESCRIPTION: This field should be marked "YES" if the site\n prefers the MED ROUTE field (#.06) in the\n PHARMACY ORDERABLE ITEM file (#50.7) to\nRemedy Ticket HD233682. This patch will help mitigate incorrect medication\n appear as the default/only entry during CPRS\n order entry. If no default medication route\n is defined in the PHARMACY ORDERABLE ITEM\n file (#50.7), then the routes from the DOSAGE\n FORM file (#50.606) will display.\n \n This field will affect only orders entered\n via the Inpatient Medications dialog or the\n Outpatient Medications dialog in CPRS. It \n will not impact IV Fluids entered via CPRS or\nroutes being displayed for selection in the Computerized Patient Record\n orders entered via backdoor Pharmacy.\n \n TECHNICAL DESCR: Set of codes. "YES" to display only the\n default med route in CPRS and "NO" to \n continue with the current functionality.\n \nThe following table summarizes the functionality of this patch.\n**NOTE** This patch will be exported with the new parameter set to YES.\n \n Default OI Med\nSystem V. 3.0 (CPRS).\nSite Parameter Route Defined CPRS Med Route Selection List\n-------------- -------------- -----------------------------\nYES YES Default med route is the only route in\n selection list. Default med route\n pre-populates the selection box.\n \nYES NO All med routes from dosage form \n display. Nothing pre-populates the\n selection box.\n \n\n
\nThis patch provides the Pharmacy Data Management support for the Class\nIII to Class I conversion project Immunizations Documentation by BCMA.\n \nIncluded in the patch is the addition of the ASSOCIATED IMMUNIZATION field\n(#9) in the PHARMACY ORDERABLE ITEM file (#50.7) and revisions to the\noptions Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] and Dispense \nDrug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE ITEMS].\n \nPatch PSB*3*47 provides the BCMA portion of the project.\n\n
\nThis patch will make some additional enhancements to the Pharmacy\nthis patch. This mail group will be used for various purposes, all\nThe following is a list of security keys included in this patch:\n \nSecurity Key\n------------ \nPSS_CUSTOM_TABLES_ADMIN SEND TO SITE\nPSS_CUSTOM_TABLES_APPROVER SEND TO SITE\nPSS_CUSTOM_TABLES_REL_MAN SEND TO SITE\nPSS_CUSTOM_TABLES_REQUESTOR SEND TO SITE\n \n \nrelating to the Pharmacy Re-Engineering (PRE) V. 0.5 project.\nThe following is a list of protocols included in this patch:\n \nProtocol\n-------- \nPSS MED ROUTE RECEIVE SEND TO SITE\n \n2) Data from the DOSE UNIT (#4) Field and the NUMERIC DOSE (#5) Field of\nthe LOCAL POSSIBLE DOSAGE (#50.0904) Subfile of the DRUG (#50) File will\nbe added as display elements to the Lookup into Dispense Drug File\n[PSS LOOK] option and the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option.\n \n3) A Vista Mail message will be sent to the PSS ORDER CHECKS Mail Group\nwhen an update is made to the STANDARD MEDICATION ROUTES (#51.23) File by\nRe-Engineering (PRE) V. 0.5 Pre-Release functionality that was released in\nthe New Term Rapid Turnaround (NTRT) process. This mail message will\ninclude what was updated, and will also include any automatic mapping\nactivities that occurred from the MEDICATION ROUTES (#51.2) File to the\nSTANDARD MEDICATION ROUTES (#51.23) File.\n \n4) The Request Change to Standard Medication Route [PSS MEDICATION ROUTE \nREQUEST] option has been changed to now refer the requestor to a web site\nto make the request.\n \n5) A new ADDITIVE FREQUENCY (#18) Field has been added to the IV ADDITIVES\npatch PSS*1.0*129. This patch also sends out four Vista Security Keys to\n(#52.6) File. This field will be used to provide a default value for the\nAdditive Frequency field in Computerized Patient Record System (CPRS) when\ncontinuous IV orders with additives are entered. Data will be\nauto-populated by a Post-Install routine for this patch, and this data\nshould be reviewed and edited as necessary. This new field can be edited\nusing the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option or the ADditives\nFile [PSSJI DRUG] option. These defaults will not start to appear in CPRS\nuntil Pharmacy Re-Engineering (PRE) V. 0.5. A new IV Additive Report [PSS\nIV ADDITIVE REPORT] option has also been added, and this report, in\naddition to the current IV Solution Report [PSS IV SOLUTION REPORT] \nbe used in the Pharmacy Enterprise Customization System (PECS)\noption, will now be located under the new IV Additive/Solution Reports\n[PSS ADDITIVE/SOLUTION REPORTS] Menu option, which will be located under\nthe Pharmacy Data Management [PSS MGR] Menu option.\n \nA Mail Message will be sent to the PSS ORDER CHECKS Mail Group and the\npatch installer upon completion of patch installation.\n \n \nThis patch addresses the following New Service Request (NSR):\n-------------------------------------------------------------\nApplication, which will be released at a later date.\nThere is no NSR associated with this patch. \n \n \nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nThere are no Remedy tickets associated with this patch.\n \n \nOverview of Remedy Ticket(s):\n-----------------------------\n \nThere are no Remedy tickets associated with this patch. \n \n \nComponents Exported With Patch: \n-------------------------------\n \n \nThe following is a list of fields included in this patch:\n \nField Name (Number) File Name (Number)\nThe enhancements to the Pre-Release functionality include:\n----------------------------------- ------------------------------\nADDITIVE FREQUENCY 18 IV ADDITIVES 52.6\n \n \nThe following is a list of templates included in this patch:\n \nTemplate Name Type File Name (Number)\n------------- ---- ------------------\nPSSIV ADD Input IV ADDITIVES (#52.6)\n \n \n \nThe following is a list of options included in this patch:\n \nOption Name Type Action\n----------- ---- ----------------------\nPSS IV ADDITIVE REPORT RUN SEND TO SITE\nPSS ADDITIVE/SOLUTION REPORT MENU SEND TO SITE\n \n \nThe following is a list of mail groups included in this patch:\n1) A new PSS ORDER CHECKS Mail Group will be created upon installation of\n \nMail Group\n---------- \nPSS ORDER CHECKS \n \nPlease note that the PSS ORDER CHECKS Mail Group is not an actual \ncomponent of the KIDS Build, but it is created during the Environment \nCheck routine.\n \n \n\n
\nPSS*1.0*143 adds validation checks to the PSS SCHEDULE EDIT option\nfrequency.\n \n2. Schedule Edit Validation Two\nThe system shall validate for frequencies greater than one day (1440\nminutes), that only one administration time is permitted.\nThe system shall present a warning message to the user if more than one\nadministration time is entered.\n \n3. Schedule Edit Validation Three\nIn Ward Administration Times field in the PSS SCHEDULE EDIT option, for\nto prevent the Standard Administration Times and Ward Administration\na schedule that has a Schedule Type of Continuous, the system shall\nprevent a user from entering administration times to Odd Schedules, a\nschedule whose frequency is not evenly divisible by or into 1440\nminutes (1 day).\n \n4. Schedule Edit Validation Four\nAdd validation to TYPE OF SCHEDULE field in PSS SCHEDULE EDIT to remove\nfrequency from the schedule file entry if the TYPE OF SCHEDULE is\nchanged from CONTINUOUS to ONE TIME, PRN, ON CALL, or DAY OF WEEK.\n \ntimes fields of a schedule from conflicting with the schedule's\n5. Schedule Edit Validation Five\nIn the PSS SCHEDULE EDIT option, the system shall prevent a user from\ncreating Day of Week (DOW) schedules that are not in the correct day of\nweek order. The correct order is: SU-MO-TU-WE-TH-FR-SA.\n \n6. Modify VistA Help Text\nThe Help Text in Standard Schedule Edit was modified to add additional\ntext so the user is able to see the added constraints when entering\nAdministration Times.\nfrequency if the frequency is numeric and the schedule type is\nContinuous.\n \n1. Schedule Edit Validation One\nThe system shall validate for frequencies of 1 day (1440 minutes) or\nless that the number of administration times equals 1440 divided by the\n\n
\nThis patch will correct the issues reported in:\n \n3) HD0000000324175 - 6 Enter/Edit Dosages\n In the "Enter/Edit Dosages" option in Pharmacy Data Management, there\n is a problem with the BCMA UNITS PER DOSE prompt when editing a\n Possible Dosage. The BCMA UNITS PER DOSE prompt should only be given\n if the Possible Dosage Package field is marked for Inpatient ("I"),\n and the Application Packages Use field for the drug contains a "I" or\n "U". Currently the prompt appears twice if the Possible Dosage Package\n and Drug is marked for Inpatient, (and it should only appear once).\n When the drug is not marked Inpatient, The prompt appears only once\n \n when it should not appear at all.\n \n4) HD0000000157266 - Synonym DUOU field does not allow for input of \n decimal\n The input template for DISPENSE UNITS PER ORDER UNIT (^DD(50,15)) \n allows for the input of decimal values (e.g. 2.5).\n1) HD0000000111095 - PSS WARNING BUILDER option fails to respond properly\n When using the VistA "Warning Builder" [PSS WARNING BUILDER] option\n and the user enters a ? or ?? for additional help information,\n the program returns very little help information.\n \n2) HD0000000133036 - Drug Synonym triggers are inconsistent\n Drug Synonym triggers are inconsistent with those on the drug level.\n\n\nThis patch corrects a defect introduced by patch PSS*1*143 in the\nHD0000000419996\n \nProblem:\n---------\nPatch PSS*1*143 changed the Standard Schedule Edit [PSS SCHEDULE EDIT]\noption to prevent the prompt for Admin Time from displaying when the\nschedule's Type is PRN, making it difficult to remove the admin times\nfrom existing PRN schedules. When the schedule type of an existing\nschedule is changed from Continuous to PRN, the admin times are removed,\nhowever, when an existing schedule with a schedule type of PRN is edited,\nStandard Schedule Edit [PSS SCHEDULE EDIT] option.\nthe admin times are not removed.\n \nIn addition, an inconsistency exists within the same option: at the\ninitial prompt for Schedule Type, entering or accepting a default of\n"PRN", has no affect on the value of admin times.\nHowever, after pressing Enter or Return to exit the Schedule Type\nprompt, if an up-arrow, or caret "^", is used to return to the Schedule\nType field, then entering "PRN" or accepting the default of "PRN" the\nsecond time the prompt is displayed does delete the admin times from the\nschedule.\n \n \nSolution:\n----------\nChange the Standard Schedule Edit [PSS SCHEDULE EDIT] option to delete\nadmin times from the schedule anytime "PRN" is entered, or accepted as a\ndefault, at the Schedule Type field. For existing PRN schedules, admin\ntimes may be deleted by re-entering "PRN", or accepting the default value\n"PRN", at the prompt for Schedule Type.\n \nChange the same option to make the Schedule Type prompt to have the same\n \neffect on the schedule's admin times for the initial and all subsequent\nprompts.\nHD0000000419996 - Admin times cannot be deleted from PRN schedules\nvia the Schedule Enter/Edit [PSS SCHEDULE EDIT] option.\n \nRemedy Overview\n---------------\n\n
\nThis patch is part of a set of patches that make up Pharmacy\n \nThis patch addresses the following New Service Request (NSR):\n-------------------------------------------------------------\nThere is no NSR associated with this patch. \n \n \nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nThere are no Remedy tickets associated with this patch.\n \nRe-engineering version 0.5. Version 0.5 will replace the current\n \nOverview of Remedy Ticket(s):\n-----------------------------\nThere are no Remedy tickets associated with this patch. \n \n \nComponents Exported With Patch: \n-------------------------------\n \nSee the National Patch Module for specifics relating to this patch.\nmedication order checking system with a new system that uses data from\nFirst DataBank (FDB). In addition to replacing the current Drug\nInteraction and Duplicate Class checks with the FDB equivalent of these\nchecks, Maximum Single Dose and Daily Dose Range Checks will now also\noccur in Outpatient Pharmacy, Inpatient Medications, and Computerized\nPatient Record System (CPRS).\n \n\n
\n \nCurrently, for IV orders, if there is more than one orderable item on the\norder, no default medication route is being denoted as a default in the\nCPRS selection list even if all the orderable items on the order share\nthe same default med route.\n \n \nResolution:\n-----------\nThis enhancement for IV orders will denote the default med route in the\nselection list in CPRS if all of the orderable items on the order have\nThis enhancement is an interim resolution approved by the Inpatient\nthe same default med route defined. If one or more orderable items on\nthe order have different default med routes, the current functionality\nwill be retained, and no med route in the selection list for CPRS will be\ndenoted as a default. Routine PSSJORDF will be modified for this\nenhancement.\nMedications Workgroup for Patient Safety Issue PSI 08-025, PSPO #852\nas described in Remedy Ticket HD233682. This patch will help resolve\nincorrect medication routes being displayed for selection in the\nComputerized Patient Record System (CPRS).\n \nProblem:\n--------\n\n
\nThis patch is being released in preparation for the medication routes\n \n - The USE DOSAGE FORM MED ROUTE LIST field (#10) is added to the PHARMACY\n ORDERABLE ITEM file (#50.7) with YES/NO values.\n \nThe above fields will be available when editing an existing or adding a \nnew orderable item using the following options:\n - Edit Orderable Items [PSS EDIT ORDERABLE ITEMS]\n - Drug Enter/Edit [PSS DRUG ENTER/EDIT\n - Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE\n ITEMS]\nenhancement patch PSS*1*159. This patch contains the following:\n \nThe Default Med Route For OI Report [PSS DEF MED ROUTE OI RPT] option\nis modified to include printing of the POSSIBLE MED ROUTES multiple.\n \nIn addition, a post install routine will run to update the USE DOSAGE\nFORM MED ROUTE LIST field (#10) based on the value of the DEFAULT MED\nROUTE FOR CPRS field (#80.7) of the PHARMACY SYSTEM file (#59.7). The\nUSE DOSAGE FORM MED ROUTE LIST field (#10) will be exported with "YES"\nfor sites that have the DEFAULT MED ROUTE FOR CPRS field (#80.7) set to\nNO. Otherwise, the USE DOSAGE FORM MED ROUTE LIST field (#10) will be \n \nset to NO.\n - The MED ROUTE field (#.06) of the PHARMACY ORDERABLE ITEM file (#50.7)\n is renamed DEFAULT MED ROUTE.\n \n - The POSSIBLE MED ROUTES multiple (#50.711) is added to the PHARMACY\n ORDERABLE ITEM file (#50.7). This multiple is pointing to the\n MEDICATION ROUTES file (#51.2).\n\n
\n \nThis is the package that holds the routines responsible for the pharmacy \nXML interface for drug order checks from First DataBank.\n\n
\nPatch PSS*1*18 has three purposes.\n \n 3. This patch contains a minor change to the DDs in the PHARMACY PATIENT\n file (#55). In reference to the Volume field (#1) under the IV\n sub-file, we changed the input transformer by increasing the range\n from 3000 to 9999.\n \n 1. This patch corrects a problem with patch PSS*1*13. A routine entry\n call was changed to access three entry points in routine PSSGS0.\n \n 2. This patch contains a new field called MAR SORT (#26.4). It is\n located in the PHARMACY SYSTEM file (#59.7). This field is a set of\n codes that allows the user to (0) sort by order's Schedule Type and\n then Medication Names and (1) sort by order's Medication Names.\n\n
\nThis patch is part of a set of patches that make up Pharmacy\n \nThis patch addresses the following New Service Request (NSR):\n-------------------------------------------------------------\nThere is no NSR associated with this patch. \n \n \nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nThere are no Remedy tickets associated with this patch.\n \nRe-engineering version 0.5. Version 0.5 will replace the current\n \nOverview of Remedy Ticket(s):\n-----------------------------\nThere are no Remedy tickets associated with this patch. \n \n \nComponents Exported With Patch: \n-------------------------------\n \n \nmedication order checking system with a new system that uses data from\nThe following is a list of fields included in this patch:\n \nField Name (Number) File Name (Number)\n----------------------------------- ------------------------------\nDISPLAY STATUS 157 IV Subfile 55.01\n of PHARMACY PATIENT 55\nDISPLAY STATUS 136 UNIT DOSE Subfile 55.06\n of PHARMACY PATIENT 55\nHOURS OF RECENTLY DC/EXPIRED 26.8 PHARMACY SYSTEM 59.7\n \nFirst DataBank (FDB). In addition to replacing the current Drug\n \nThe following is a list of options exported in this patch:\n \nOption Name Type Action\n----------- ---- ----------------------\nPSS ADDITIVE/SOLUTIONS Menu Send to Site\nPSS ADDITIVE/SOLUTION REPORTS Menu Delete at Site\nPSS DRG INTER MANAGEMENT Menu Delete at Site\nPSS ENHANCED ORDER CHECKS Menu Delete at Site \nPSS INTERACTION LOCAL ADD Run Delete at Site\nInteraction and Duplicate Class checks with the FDB equivalent of these\nPSS INTERACTION SEVERITY Action Delete at Site\nPSS INTERFACE SCHEDULER Run Send to Site\nPSS LOCAL DOSAGES EDIT Run Delete at Site\nPSS LOCAL DOSAGES EDIT ALL Run Delete at Site\nPSS MAP ONE MED ROUTE Run Delete at Site\nPSS MARK PREMIX SOLUTIONS Run Send to Site\nPSS MED ROUTES INITIAL MAPPING Run Delete at Site\nPSS ORDER CHECK CHANGES Run Send to Site\nPSS ORDER CHECK MANAGEMENT Menu Send to site\nPSS SCHEDULE PEPS INTERFACE CK Run Send to Site\nchecks, Maximum Single Dose and Daily Dose Range Checks will now also\nPSS STRENGTH MISMATCH Run Delete at Site\noccur in Outpatient Pharmacy, Inpatient Medications, and Computerized\nPatient Record System (CPRS).\n \n\n
\nThis patch contains software modifications to the Pharmacy Data Management \n . Patient decision-making should be advised by information about a known\n serious side effect with a product, or \n . Patient adherence to directions for the use of a product is essential\n to its effectiveness. \n \nThe features in the FDA Medication Guides project are being delivered in\nincremental releases. This patch is part of the Increment 2 release. The \nfeatures included in this release are:\n \n . Establishment of a Server Repository for FDA Medication Guides within \n(PDM) V. 1.0 application to support the FDA Medication Guides project. The \n the VA network.\n \n . Updates to 900+ entries in the VA PRODUCT file (#50.68) to store the \n corresponding FDA Medication Guide document name will be provided via\n the NDF Monthly Data Update patches.\n \n . Introduction of a PC based Java software component to enable the\n automatic retrieval of an FDA Medication Guide from within VistA. The\n software does not require any direct user interaction. It works as a \n bridge between VistA and the PC where it is installed. The software \nproject objective is to allow pharmacy staff to retrieve the FDA Medication \n identifies a request from VistA for a specific FDA Medication Guide and\n automatically retrieves it from the Server Repository and displays to the\n user via the Internet Explorer browser. \n \n . Introduction of a new option called Display FDA Medication Guide [PSN MED\n GUIDE] to the National Drug File V. 4.0 application for retrieving and \n displaying the FDA Medication Guide for a specific VA Product.\n \n . Introduction of new functionality to the Patient Prescription Processing\n [PSO LM BACKDOOR] option in the Outpatient Pharmacy V. 7.0 application\nGuide for prescriptions that contain FDA approved information that can help\n for retrieving and displaying the FDA Medication Guide for a specific \n prescription.\n \nBelow is a list of all the applications involved in this release along\nwith their patch number:\n \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*343\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*263\npatients avoid serious adverse events. The FDA requires that Medication\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*158\n \nThe FDA Medication Guides project is expected to complete in three \nincrements. Among other features, the next Increment will automate the \nprinting of FDA Medication Guides for prescriptions dispensed by the VA\nvia Outpatient Pharmacy application when the prescription label is printed.\n \nThe following modifications are included in this patch (PSS*1*158):\n \n 1. New Data Dictionary field added to PHARMACY SYSTEM (#59.7) file\nGuides be included with certain prescribed drugs and biological products \n \n A new field called FDA MED GUIDE SERVER URL (#100) is being added to the\n PHARMACY SYSTEM (#59.7) file. This field will be used to store the FDA\n Medication Guide Web server URL which will be used in conjunction with\n the FDA MED GUIDE (#100) field in the VA PRODUCT (#50.68) file to compose\n the complete FDA Medication Guide URL for a specific VA Product entry.\n \n 2. A post-install routine will run to set this new field with the value\n shown below, which is the current FDA Medication Guides web Server URL:\n \nwhen the Agency determines that: \n http://vaww.national.cmop.domain.ext/FDAMedGuides/\n \n Note: Integration Control Registration (ICR) #2613 is being modified to\n include this new field in the list of fields that can be read by\n the National Drug File (NDF) application.\n \n . Certain information is necessary to prevent serious adverse effects \n\n
\nThis patch addresses the New Service Request (NSR) #20070434 to prevent\n1. This enhancement utilizes three new fields that were added to the\n VA PRODUCT file (#50.68) as part of patch PSN*4*261. These fields will\n be used during the Match/Rematch process of the Drug Enter/Edit [PSS\n DRUG ENTER/EDIT] and the Enter/Edit Dosages [PSS EDIT DOSAGES] options\n to determine if possible dosages should be auto- created or not. The\n three fields are:\n - CREATE DEFAULT POSSIBLE DOSAGE field (#40)\n - POSSIBLE DOSAGES TO CREATE field (#41)\n - PACKAGE field (#42)\n \nthe inadvertent creation of supra-therapeutic possible dosages for high\nWhen CREATE DEFAULT POSSIBLE DOSAGE field (#40) is "YES", then the\nexisting functionality of auto-creating possible dosages will be retained.\nWhen this field is "NO", it will be used in combination with the value in\nPOSSIBLE DOSAGES TO CREATE field (#41) to determine the auto-creation of\npossible dosages.\n \nThe following conditions will apply when CREATE DEFAULT POSSIBLE DOSAGE\nfield (#40) is "NO":\n \n a. If POSSIBLE DOSAGES TO CREATE field (#41) is "NO", no possible\nrisk medications during the dosage creation segment of Pharmacy Data\n dosages will be auto-created and the following message will be\n displayed:\n \n "Due to National Drug File settings no possible dosages were\n auto-created."\n b. If POSSIBLE DOSAGES TO CREATE field (#41) is "O", 1x possible dosage\n will be auto-created for the package specified by the new PACKAGE\n field (#42) and the following message will be displayed:\n \n "Due to National Drug File settings only one possible dosage will be\nManagement and National Drug File (NDF) updates. The Pharmacy Data\n auto-created.\n If other dosages are needed, create POSSIBLE DOSAGES or LOCAL\n POSSIBLE DOSAGES as appropriate."\n \n c. If POSSIBLE DOSAGES TO CREATE field (#41) is "B", 1x and 2x possible\n dosages will be auto-created for the package specified by the new\n PACKAGE field (#42).\n \n2. This patch retires the Auto Create Dosages [PSS DOSAGE CONVERSION]\n option. This option is retired because, if it is run inadvertently, it\nManagement V. 1.0 and the National Drug File V. 4.0 were modified\n will delete all existing "Possible Dosages" and "Local Possible\n Dosages" and will re-set the Possible Dosages back to NDF settings. The\n changes that were entered locally by the site for "Possible Dosages"\n and "Local Possible Dosages" will be lost. Upon patch installation,\n this option will be removed from the Dosages [PSS DOSAGES MANAGEMENT]\n menu.\nto satisfy the request. The NDF portion is addressed in patch PSN*4*262.\n \nThis patch has the following enhancements:\n \n\n
\nThis patch makes a change to the interface when order checks are sent from\napplication that the message indicating order checks were not performed be\ndisplayed to the user.\n \nAdditionally, any time order checks are sent through the interface for \nthe PSS INTERFACE SCHEDULER job or as an individual user, certain fields \nare required numeric values. Is these fields are not numeric, the \ninterface request will fail. This patch will check those fields and \nsubstitute a value if necessary. These fields are as follows:\n \nDUZ (User's internal entry number) - the software will replace with 0.\nVistA to the Medication Order Check HealthCare Application (MOCHA). When\nJob Number - the software will replace with 0.\nStation Number - the software will use the leading numerics, but if\nthere are no leading numerics, the software will replace with 0.\nOrder Checks cannot be performed for any reason, a warning message is \ndisplayed to the user that order checks did not occur. There was an \noccurrence reported in a test account where Order Checks did not occur, \nbut no message was displayed to the user. At the end of all the order\ncheck processing, this patch will add an additional check to see if the\nflag that indicates the success or failure of the order checks is set. If\nit is not set, it will set the flag that will indicate to the calling\n\n
\nThis patch will correct the issues reported in Remedy Tickets:\nthe user enters a schedule with "QD","QOD","HS","TIW" the user is kicked\nout of Vista with this error <UNDEFINED>ENPSJ+6^PSSJSV *X.\n \n1) HD0000000222760 - Pharmacy standard schedule problem\nThe use of the @ in the ADMINISTRATION SCHEDULE file #51.1 Name field \n.01 with the exception of day-of-week schedules, causes the user to be\nlocked into a prescription for a 1 time order (reorder)\n \n2) HD0000000422160 - <UNDEFINED>ENPSJ+6^PSSJSV *X\nWhen using the VistA Standard Schedule Edit[ PSS SCHEDULE EDIT] option and\n\n
\nThis enhancement, approved by the Pharmacy Legacy Enhancement (PLE) User\nThe pharmacy Integration Control Registration (ICR) #2418 is modified\nto return appropriate medication routes for the orderable item (OI) in\nCPRS ordering dialog with the following conditions.\n \nNote: The fields referenced below are from the PHARMACY ORDERABLE ITEM\n file (#50.7):\n \n 1. ICR Modifications\n - Default Med Route\n It will be derived from the DEFAULT MED ROUTE field (#.06) if it's\nGroup, will resolve Patient Safety Issue PSI-08-026/PSPO #852 reported in\n populated or from the POSSIBLE MED ROUTES multiple (#50.711) if it's\n populated with single entry and the USE DOSAGE FORM MED ROUTE LIST\n field (#10) is set to "NO."\n \n - Optional Med Routes\n The medication route selection list in CPRS will be populated with\n entries from the POSSIBLE MED ROUTES multiple (#50.711) if the USE\n DOSAGE FORM MED ROUTE LIST field (#10) is set to "NO." Otherwise, it\n will be populated from the medication routes associated with the\n orderable item's dosage form, which is the current logic.\nRemedy Ticket HD233682.\n \n 2. The logic for editing the medication route has been modified in the \n following options:\n - Edit Orderable Items [PSS EDIT ORDERABLE ITEMS]\n - Drug Enter/Edit [PSS DRUG ENTER/EDIT]\n - Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE\n ITEMS]\n \n The software will now ensure that the DEFAULT MED ROUTE field (#.06)\n of the PHARMACY ORDERABLE ITEM file (#50.7) is either defined and/or\n \n at least one entry is defined in the POSSIBLE MED ROUTES multiple\n (#50.711) or the USE DOSAGE FORM MED ROUTE LIST field (#10) is set to\n YES so that the medication route selection during order entry is\n listed appropriately.\n \n Note: This patch will change USE DOSAGE FORM MED ROUTE LIST field\n (#10) of the PHARMACY ORDERABLE ITEM file (#50.7) from not\n required to a required field. In order to use the new\n functionality introduced in this patch, it is imperative that\n the user marks this field YES or NO. This field will be used to\nThis patch will help mitigate incorrect medication routes being displayed\n determine the medication route selection during order entry.\n \n 3. The Pharmacy System Parameters Edit [PSS SYS EDIT] option is modified\n to remove the DEFAULT MED ROUTE FOR CPRS field (#80.7) of the \n PHARMACY SYSTEM file (#59.7) from the list of fields that can be\n edited.\nfor selection in the Computerized Patient Record System (CPRS) V. 3.0.\nThis enhancement affects Inpatient Medications unit dose orders, IV Fluids\norders, and Outpatient Pharmacy orders entered via CPRS orders dialog.\n \n\n
\nWhen calls are made to the Medication Order Check Healthcare Application \nwill be aborted with the message indicating that order checks cannot be\nperformed.\n \nThis patch also addresses an issue (in conjunction with patch PSO*7.0*379)\nconcerning Orderable Items that are flaggeed as Supplies. If an order \ncheck is to be performed on an order that only has an Orderable Item with \nno Dispense Drug, an attempt is made to find the best drug available that \nis matched to the Orderable Item for the order check. Currently, if the \nOrderable Item is marked as a supply, no order checks are performed. But \nif the Orderable Item has both Supply and non-Supply Items matched to it, \n(MOCHA), a "Ping" type of call is made first to test the communication, \norder checks can possibly be performed on one of the non-supply items. \nThis patch makes the change to look for non-Supply Items matched to the \nsupply Orderable Item to perform the order checks on.\nand if that is successful, the subsequent order check call is made. If \neither call fails, the process is aborted, and a message is displayed \nindicating that order checks cannot be performed.\n \nWhat this patch introduces is a "re-try" if either of these calls fail. \nAfter a three second hang, the call (Ping or order check) will be\nattempted again, then if the same call fails a second time, the process\n\n
\nThis patch is being released as part of Pharmacy Legacy Enhancements Fiscal\nthan one Automated Dispensing Device (ADD) communicating with Veterans Health \nInformation Systems and Technology Architecture (VistA) through OPAI.\n \n1.A new OPAI sub-file (#50.0906) was added to the DRUG file (#50). It gives\n sites the flexibility to define ADDs at the drug level. The sub-file \n (#50.0906) contains the following new fields: \n DIVISION - This is the division associated with the ADD for the drug.\n This field is a pointer to the OUTPATIENT SITE file (#59).\n WINDOW - This field is a pointer to the PHARMACY AUTOMATED DISPENSING\n DNS NAME DEVICES file (#52.53). Orders with a route of WINDOW will be\nYear 2011 to address the Outpatient Pharmacy Automation Interface (OPAI) \n sent to this ADD.\n MAIL - This field is a pointer to the PHARMACY AUTOMATED DISPENSING\n DNS NAME DEVICES file (#52.53). Orders with a route of MAIL will be\n sent to this ADD.\n \n \n2. The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option was modified to include\n the new fields as part of data entry.\nEnhancements. The Outpatient Pharmacy patch PSO*7*354 is also being released \nas part of this enhancement.\n \nVeterans Affairs Medical Center (VAMC) facilities have moved to using multiple\nvendors for automated medication dispensing systems to improve the efficiency\nof outpatient pharmacy operations. The following enhancements were made to \nthe Pharmacy Data Management software to allow any one division to have more \n\n
\n This patch is an enhancement patch. It will create five (5) new security\nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nThere are no Remedy tickets associated with this patch.\n \nAssociated PSIs: \n----------------\nN/A \n \nOverview of Remedy Ticket(s):\n-----------------------------\n keys. They will be used to authenticate users using Kernel Authentication\nN/A\n \nComponents Exported With Patch: \n-------------------------------\n \n \nThe following is a list of Security Keys included in this patch:\n \nSecurity Key Name Action\n------------------- -------\n & Authorization for J2EE (KAAJEE). Users using the Pharmacy Product System-\nPSS_PPSN_MANAGER SEND TO SITE\nPSS_PPSN_MIGRATOR SEND TO SITE\nPSS_PPSN_SECOND-APPROVER SEND TO SITE\nPSS_PPSN_SUPERVISOR SEND TO SITE\nPSS_PPSN_VIEWER SEND TO SITE\n National (PPS-N) should be assigned these keys after installing this patch.\n PPS-N is a new development effort underway, which is a re-engineered\n product to eventually replace the National Drug File Management System\n (NDFMS). No routines are included in this patch.\n \n \n\n
\nThis patch corrects a patient safety issue in which editing the IV \nThis process has been enhanced by displaying the previously entered Print\nName as the default if only one is entered.\n Example:\n +------------------------------------------------------------+\n | Select IV ADDITIVES PRINT NAME: ADDITIVE1// |\n +------------------------------------------------------------+\n \nIf more than one Print Name were previously entered, the software will\ndisplay the list of all linked Additives and/or Solutions to select from\nso an edit may be made. Example:\nADDITIVES file (#52.6) and/or IV SOLUTIONS file (#52.7) using the Drug\n \n Example:\n +------------------------------------------------------------+ \n | <DRUG NAME> currently linked to the following IV Additives:|\n | |\n | 1. ADDITIVE1 |\n | 2. ADDITIVE2 |\n | |\n | Select 1-2 from list above or type 'NEW' to link |\n | to a new IV Additive: |\nEnter/Edit [PSS DRUG ENTER/EDIT] option is problematic. The current\n +------------------------------------------------------------+\n \nThe new enhancement will also allow the user to enter a new Additive or\nSolution and link it to the dispense drug. The software will give the user\nthe choice to enter and link the dispense drug to a new Additive or\nSolution as well as require a confirmation of the selected dispense drug\nthat will be linked to the selected Additive/Solution. \n \n Example (Create new IV Additive and link to drug):\n +--------------------------------------------------------------------+\nfunctionality needs to be changed to prevent erroneous matching with\n | <DRUG NAME> currently linked to the following IV Additives: |\n | |\n | 1. ADDITIVE1 |\n | 2. ADDITIVE2 |\n | |\n | Select 1-2 from list above or type 'NEW' to link |\n | to a new IV Additive: NEW |\n | |\n | Select IV ADDITIVES PRINT NAME: TEST |\n | Are you adding 'TEST' as a new IV ADDITIVES (the 33RD)? No// Yes |\nDispense Drugs. It is very easy to select the wrong item and incorrectly\n | IV ADDITIVES DRUG UNIT: GM GM |\n | PRINT NAME: TEST// |\n | Select DRUG GENERIC NAME: CEFAMANDOLE 1GM INJ// AM116 |\n | ARE YOU SURE YOU WANT TO SELECT CEFAMANDOLE 1GM INJ? No// Y (Yes) |\n | ... |\n | |\n | <DRUG NAME> currently linked to the following IV Additives: |\n | |\n | 1. ADDITIVE1 |\n | 2. ADDITIVE2 |\nchange the PRINT NAME field (#.01) of the additives or solutions files.\n | 3. TEST |\n | |\n | Select 1-3 from list above or type 'NEW' to link |\n | to a new IV Additive: NEW |\n +--------------------------------------------------------------------+\n \nThe new enhancement will also create the new sub-menu Inpatient Drug \nManagement [PSS INP MGR]. This sub-menu will be located under the \nPharmacy Data Management [PSS MGR] menu and will include the following \noptions:\nAlso, once an additive or solution is selected, it is unclear as to\n - ADditives File [PSSJI DRUG]\n - Dispense Drug Fields [PSSJU DRG]\n - Dispense Drug/ATC Set Up [PSSJU DRUG/ATC SET UP]\n - Edit Cost Data [PSSJU DCC]\n - EDit Drug Cost (IV) [PSSJI EDIT DRUG COST]\n - MARk/Unmark Dispense Drugs For Unit Dose [PSSJU MARK UD ITEMS]\n - PRimary Solution File (IV) [PSSJI SOLN]\n \n \nIn addition to these enhancements, an unrelated defect that was discovered\nwhether or not the user is still selecting or editing.\nwith the PSSIV ADD Input Template during testing was corrected in this \npatch. The error prevented valid ADMINISTRATION TIMES from being \nassociated with the IV ADDITIVE as well as QUICK CODES associated with \nthe IV ADDITIVE. The error was addressed by correctly validating the \nADMINISTRATION TIMES fields using the same validation as is used in the \nADMINISTRATION SCHEDULE file (#51.1).\n \n\n
\nThis patch creates a new Pharmacy Data Management option, Pharmacy quick\norder correction for CPRS [PSS QUICK1]. This option will allow the\npharmacy quick orders that weren't converted in the OR*2.5*49 patch\nconversion to be manually corrected and converted to the quick order in\nComputerized Patient Record System. The invalid data in each quick order\nwill be shown and the user will be prompted to correct the item. This\noption is not distributed on any menu. It should be assigned to the\nappropriate person in pharmacy that would make decisions about editing\nthese quick orders.\n\n
\nSpecial Instructions/Other Print Info\nfor IV).\n \nSpecial Instructions and Other Print Info may also be entered\nand/or edited from within Inpatient Medications V. 5.0 order entry\noptions.\n \nPrior to this enhancement, Inpatient Medications maximum character\nlength for Special Instructions was 180 characters and for Other Print\nInfo the maximum length was 60 characters. This enhancement resolves\nPatient Safety Issues PSPO 42, 1466 / Remedy Ticket HD336419\n________________________________________\n- Comment lengths between CPRS and Pharmacy.\n \nNo Allergy Assessment\n________________________\nThe No Allergy Assessment enhancement provides an interactive alert to the\npharmacist in Inpatient Medications V. 5.0 when no allergy assessment is\non file for the patient, and a method for the pharmacist to enter an\nallergy assessment after receiving the alert. A pharmacy intervention\nis automatically created if the pharmacist chooses to not enter an\nassessment.\nWith this enhancement, Special Instructions and Other Print Info have been\n \nThe No Allergy Assessment functionality will be available at the\nfollowing options:\n \nDelete Orders [PSJI DELETE ORDER]\nInpatient Order Entry [PSJ OE]\nNon-Verified/Pending Orders [PSJU VBW]\nOrder Entry [PSJU NE]\nOrder Entry (IV) [PSJI ORDER]\nProfile (IV) [PSJI PROFILE]\nmodified to support an unlimited amount of text. The existing\n \nWhen a patient with no allergy assessment is selected from one of the\naffected options, the following message will be displayed to the\npharmacist:\n \n"NO ALLERGY ASSESSMENT exists for this patient! Would you like to enter\none now?"\n \n - If the pharmacist enters 'YES' at this prompt, they are prompted\n for allergy information.\nfunctionality that copies the provider comments from the Computerized\n - If the pharmacist enters 'NO' at this prompt, a pharmacist intervention\n is created, with a type of 'NO ALLERGY ASSESSMENT'. The pharmacist is\n then prompted for Provider and Recommendation. A new Recommendation,\n 'UNABLE TO ASSESS', has been created specifically for this type of\n intervention.\n \nThis enhancement will address Patient Safety Issue PSPO 445.\nPatient Record System (CPRS) to be copied into each field has been\nretained, and an additional action has been added to optionally open a\nword processing edit dialog after copying the provider comments into the\nappropriate field (Special Instructions for Unit Dose, Other Print Info\n\n
\n This patch makes three enhancements to Pharmacy Data Management (PDM)\n \n The second enhancement is a change to the menu option entitled\n "Print PEPS Services Setup" {PSS CHECK PEPS SERVICES SETUP]. Additional\n functionality is provided to the user with a device prompt to send the\n output to a printer device or they may choose to print to the screen.\n \n The third enhancement deals with the way entries in the DOSE UNITS file\n (#51.24) are displayed. Some of the entries in this file are composed\n of TallMan lettering (mixed case). Under the menu option entitled\n "Request Change to Dose Unit" [PSS DOSE UNIT REQUEST], if a user\n and re-introduces an option from PSS*1*129 as a "stand alone" option:\n requests a change to an entry that is composed of Tallman lettering,\n previously, these entries did not collate as desired. Any entry\n composed of TallMan lettering is converted to uppercase when doing the\n lookup so that alphabetic sorting is maintained while still preserving\n Ta1lMan lettering. A Post-Install routine PSS164P is included to re-index\n the DOSE UNITS file (#51.24).\n \n The option "Find Unmapped Local Possible Dosages" [PSS LOCAL DOSAGES\n EDIT ALL] is exported and re-introduced as a "stand alone" option. The\n option loops through all Local Possible Dosages, identifies entries\n \n eligible for dosage checks that do not have data in the new Dose Unit\n and Numeric Dose fields, and prompts for data entry into these fields.\n It was purposely deleted with the install of MOCHA V1.0. It was thought\n that it was no longer needed. It is being exported at the request of\n the sites. It was found that some had not fully mapped their dosages\n completely and have since added new drugs to DRUG file (#50) as well\n as have unmatched some drugs to National Drug File (NDF).\n The first enhancement adds a new menu option under the menu option\n entitled "PEPS Services" [PSS PEPS SERVICES]. This new option is entitled\n "Print Interface Data File" [PSS VENDOR INTERFACE REPORT]. This report\n prints entries from the VENDOR INTERFACE DATA file (#59.74). The user is\n asked for a date/time range and the report is sorted by the most recent\n downtime first.\n\n\nThis patch will correct the following issues:\n \n Update the calculation for slashed dosages in outpatient pharmacy by \n correctly calculating duration in reation to dosage.\n \n Prevent display of non-editable field IV FLAG (#.03) in the PHARMACY \n ORDERABLE ITEM FILE (#50.7) from displaying when attempting to edit \n via fileman.\n\n
\nThis patch is being released as part of the DEA e-Prescribing of \n -----------------------------------------------------------------\n KERNEL V. 8.0 XU*8*580\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*166\n COMPUTERIZED PATIENT RECORD SYSTEM (CPRS) V. 3.0 OR*3*306\n CONTROLLED SUBSTANCES (CS) V. 3.0 PSD*3*73\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*391\n \nNote: Patches PSO*7*391 and PSD*3*73 will be released in the Kernel \n Installation and Distribution System (KIDS) multi-build distribution\n CPRSV29_PSO_PSD.\nControlled Substances (CS) project using Public Key Infrastructure (PKI)\n \nThis is the Pharmacy Data Management patch (PSS*1*166) that provides\nthe following enhancements and will be in the KIDS distribution PSS_1_166.\n \n1. This patch modifies Integration Control Registration (ICR) #3737 by\n adding the following two new Application Programming Interface (API):\n a. The API $$DETOX^PSSOPKI will return a "1" (one) if the drug name \n contains "BUPREN", a detoxification drug or a "0" (zero) otherwise.\n \n b. The API $$OIDETOX^PSSOPKI is provided to CPRS to determine\nto satisfy requirements requested by the Drug Enforcement Administration\n whether an orderable item has an associated detoxification drug.\n \n2. This patch modifies ICR #3784 - API $$IVDEA^PSSUTIL1 to return the \n specific CS FEDERAL SCHEDULE field (#19) code of the VA PRODUCT file\n (#50.68) or the specific DEA, SPECIAL HDLG field (#3) code of the DRUG\n file (#50) of the drugs tied to the Orderable Item.\n \n3. Patch PSS*1*159 introduced an issue where the user was prevented from\n up-arrowing (^) to quit out of the template in the Edit Orderable Items\n [PSS EDIT ORDERABLE ITEMS] option. This patch resolves that issue by\n(DEA).\n allowing the user to up-arrow out of the template.\nThe applications involved in this project along with their patch numbers \nare listed below and the same order should be followed when installing \nthe patches.\n \n APPLICATION PATCH\n\n
\nThis patch will correct the issues reported in:\nINC000000720652 - Audit File/Drug File Issue\nThe DRUG file (#50) uses a cross-reference trigger to update the PRICE PER\nDISPENSE UNIT field (#16) whenever the PRICE PER ORDER UNIT field (#13)\nand/or the DISPENSE UNITS PER ORDER UNIT field (#15) are changed. These\ncross-reference triggers are currently configured incorrectly and when \nsites turn auditing on for these fields no data is collected.\nINC000000607659 - Incorrect Drug Cost in Outpt Rx Clean up need\nIncorrect drug costs in Outpatient Pharmacy associated with the National\nDrug Class (NDC)\n \nWhen a prescription is released, the multiple, NDC BY OUTPATIENT SITE \n(#50.032) in the DRUG file (#50) is getting stored. Only the drugs that\nare E-PAYABLE should have this multiple stored in the DRUG file. \n \n\n
\nThis patch will address Patient Safety Issue PSPO00001088 and\nat the GENERIC DRUG prompt and introduced this issue. Patch\n5) This patch will also enhance the capabilities of the IV ADDITIVES\nFile (#52.6) and IV SOLUTIONS File (#52.7) so that a user can enter\na new additive or solution that has the same name as an existing entry.\nPreviously, a Fileman workaround had to be used to enter an identically\nnamed entry. With this patch, if the user types in a name that already\nexists in the file, they will first be presented with a list of available\nselections. If the user scrolls through the list without selecting an\nentry, they will be presented with the prompt to add a new entry.\n \nFor example - IV ADDITIVES File (#52.6)\nPSS*1.0*174 will fix this problem by properly allowing the\n \nCHOOSE 1-2: 1 PSSJI DRUG ADditives File\nADditives File\nSelect IV ADDITIVES PRINT NAME: TESTDRUG\n Lookup: PRINT NAME\n 1 TESTDRUG Additive Strength: 10 MG \n \n 2 TESTDRUG Additive Strength: N/A \n 3 TESTDRUG Additive Strength: 5 GM \n \nuser to exit the GENERIC DRUG prompt by using the caret (^).\n 4 TESTDRUG Additive Strength: 12 GM \n \nCHOOSE 1-4: \n Are you adding 'TESTDRUG' as a new IV ADDITIVES (the 77TH)? No// Y \n(Yes)\n \n \nFor example - IV SOLUTIONS File (#52.7)\n \nSelect OPTION NAME: PSSJI SOLN PRimary Solution File (IV)\n \nPRimary Solution File (IV)\nSelect IV SOLUTIONS PRINT NAME: 0.9% SODIUM CHLORIDE\n Lookup: PRINT NAME\n 1 0.9% SODIUM CHLORIDE 250 ML \n 2 0.9% SODIUM CHLORIDE 50 ML \n \n 3 0.9% SODIUM CHLORIDE 25 ML \n \nCHOOSE 1-3: \n \n2) Another issue addressed with this patch is the wording when the\n Are you adding '0.9% SODIUM CHLORIDE' as \n a new IV SOLUTIONS (the 32ND)? No// Y (Yes)\n \n6) This patch will also allow the addition of identically named\nIV ADDITIVES and IV SOLUTIONS from the DRUG ENTER/EDIT \n[PSS DRUG ENTER/EDIT] option when linking an additive or solution\nto the drug.\n \nFor example - new additive:\n \nUser is linking an IV Additive to a Generic Drug at the \nAN IV ITEM? Yes// Y (Yes)\nEdit Additives or Solutions: \n \n Select one of the following:\n \n A ADDITIVES\n S SOLUTIONS\n \nEnter response: ADDITIVES\n \nGENERIC DRUG prompt in menu option ADditives File [PSSJI DRUG]. It was\n CEFAZOLIN SOD 1GM INJ currently linked to the following IV Additives:\n \n \n \n 1. TESTDRUG Additive Strength: 10 MG\n \n 2. TESTDRUG Additive Strength: 5 GM\n \n 3. TESTDRUG Additive Strength: 12 GM\n \nunclear which drug name was the Additive and which was the\n 4. TESTDRUG Additive Strength: 12.5 GM\n \n \nSelect 1-4 from list above or type 'NEW' to link to a new IV Additive: NEW\n \nSelect IV ADDITIVES PRINT NAME: TESTDRUG\n Lookup: PRINT NAME\n 1 TESTDRUG Additive Strength: 10 MG \n \n 2 TESTDRUG Additive Strength: 5 GM \nGeneric Drug when selecting. This patch will remove the \n \n 3 TESTDRUG Additive Strength: 12 GM \n \n 4 TESTDRUG Additive Strength: 12.5 GM \n \nCHOOSE 1-4: \n Are you adding 'TESTDRUG' as a new IV ADDITIVES (the 78TH)? No// Y \n(Yes)\n \n \nuncertainty by clearly stating to the user which is the\nFor example - new solution:\n \nAN IV ITEM? Yes// (Yes)\nEdit Additives or Solutions: \n \n Select one of the following:\n \n A ADDITIVES\n S SOLUTIONS\n \nNew Service Request (NSR) 20110308 as well as defects introduced\nIV Additive and which is the Generic Drug. For example:\nEnter response: SOLUTIONS\n \n CEFAZOLIN SOD 1GM INJ currently linked to IV Solutions:\n \n 1. 0.9% SODIUM CHLORIDE 300 ML\n 2. 0.9% SODIUM CHLORIDE 300 ML\n 3. 0.9% SODIUM CHLORIDE 450 ML\n 4. 0.9% SODIUM CHLORIDE 254 ML\n \nSelect 1-4 from list above or type 'NEW' to link to a new IV Solution: NEW\n \n \nSelect IV SOLUTIONS PRINT NAME: 0.9% SODIUM CHLORIDE\n Lookup: PRINT NAME\n 1 0.9% SODIUM CHLORIDE 250 ML \n \n 2 0.9% SODIUM CHLORIDE 50 ML \n \n 3 0.9% SODIUM CHLORIDE 25 ML \n 4 0.9% SODIUM CHLORIDE 10 ML \n 5 0.9% SODIUM CHLORIDE 1000 ML \nPRINT NAME: CEFAZOLIN// \n \nPress <RETURN> to see more, '^' to exit this list, '^^' to exit all \nlists, OR\nCHOOSE 1-5: \n \n Are you adding '0.9% SODIUM CHLORIDE' as \n a new IV SOLUTIONS (the 33RD)? No// Y (Yes)\n \n \n \nGENERIC DRUG: CEFAZOLIN SOD 10GM M/D INJ// CEFAZ\n** NOTE **\nThis patch must be installed in conjunction with the Inpatient\nMedications v. 5.0 patch PSJ*5.0*289 for the full functionality\nto be realized.\n 1 CEFAZOLIN OPTH SOLN 50MG/CC (15CC) \n 2 CEFAZOLIN SOD 10GM M/D INJ AM115 \n 3 CEFAZOLIN SOD 1GM INJ AM115 N/F \nCHOOSE 1-3: 3 CEFAZOLIN SOD 1GM INJ AM115 N/\n \nYou are about to change the GENERIC DRUG linked to this ADDITIVE.\nby patch PSS*1.0*146.\nADDITIVE CEFAZOLIN is currently linked to \nGENERIC DRUG CEFAZOLIN SOD 10GM M/D INJ.\n \nAre you sure you want to link ADDITIVE CEFAZOLIN\nto GENERIC DRUG CEFAZOLIN SOD 1GM INJ? No//\n \n3) This patch will also serve as the overall resolution to the\nissue of ambiguous IV Additive strength when a pharmacist is\nfinishing an IV by adding a STRENGTH (#19) field to the \nIV ADDITIVES File (#52.6). The new STRENGTH (#19) field\n \ncan be populated when adding a new IV Additive or when editing\nan existing IV Additive via menu option ADditives File [PSSJI DRUG].\n \nFor example:\n \nPRINT NAME: CEFAZOLIN// \nGENERIC DRUG: CEFAZOLIN SOD 10GM M/D INJ// AM115\nUSED IN IV FLUID ORDER ENTRY: YES// \nDRUG UNIT: GM// \nSTRENGTH: 1// ??\n1) When adding a new IV Additive to the IV ADDITIVES File (#52.6),\n \nThis field identifies the numeric amount of medication that is\nprovided by one unit-of-use for the identified product.\n \nFor example, if one vial contains 50 MG of medication, the\nSTRENGTH will be entered as '50'. The DRUG UNIT of 'MG'\nis populated by the DRUG UNIT (#2) field.\n \n \nWhenever a lookup is performed on the IV ADDITIVES File (#52.6), the \nand the user is at the GENERIC DRUG prompt, there is no way\nSTRENGTH (#19) field will display next to the NAME (#.01) field\nwith the words "Additive Strength:" and then its value.\nAdditionally, the DRUG UNIT (#2) field will be appended to the\nSTRENGTH (#19) field. If the STRENGTH (#19) field is not\npopulated for the IV Additive, the text "N/A" will display, and\nthe DRUG UNIT (#2) field will not display.\n \nFor example:\n \nSelect IV TYPE: PIGGYBACK.\nto exit from the prompt. The input does not allow the user\nSelect ADDITIVE: CEFAZOL\n 1 CEFAZOLIN Additive Strength: 1 GM \n IV ROOM ONLY\n 2 CEFAZOLIN Additive Strength: 2 GM \n \n 3 CEFAZOLIN PREMIX Additive Strength: N/A \n \nCHOOSE 1-3:\n \n4) Additionally, this patch makes a small enhancement to the display\nto use the caret (^) to exit. The code that was modified\nof Quick Codes during the selection of an IV ADDITIVE during\norder entry. When a lookup is performed on an IV ADDITIVE, if there\nare QUICK CODES defined for the IV ADDITIVE, the QUICK CODE\nSTRENGTH (#1) field and the USUAL IV SCHEDULE (#4) field from the\nQUICK CODE Subfile (#52.61) will display next to the QUICK CODE.\nIf the QUICK CODE STRENGTH (#1) field is null, "N/A" will be displayed.\nIf the USUAL IV SCHEDULE (#4) field is null, "N/A" will be displayed.\n \nFor example:\nSelect ADDITIVE: CEFAZ\nin routine PSSVIDRG for patch PSS*1.0*146 changed the code\n 1 CEFAZOLIN Additive Strength: 1 GM \n \n - CEFAZ1GM - Quick Code Strength: 1 GM Schedule: N/A\n - CEFAZ2GM - Quick Code Strength: N/A Schedule: BID\n 2 CEFAZOLIN Additive Strength: 2 GM \n IV ROOM ONLY\n 3 CEFAZOLIN PREMIX Additive Strength: N/A \n \nCHOOSE 1-3: \n \n\n
\nIMR6 - HIGH RISK/ALERT MEDICATION FIELD ADDED TO PHARMACY ORDERABLE ITEM \nFILE #50.7\n\n
\nThis patch will activate the new Dosing Order Check functionality for\n \nThis patch addresses the following New Service Request (NSR):\n-------------------------------------------------------------\nThere is no NSR associated with this patch. \n \n \nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nThere are no Remedy tickets associated with this patch.\n \nSingle Dose checking only for Inpatient Medications, Outpatient Pharmacy,\n \nOverview of Remedy Ticket(s):\n-----------------------------\nThere are no Remedy tickets associated with this patch. \n \n \nComponents Exported With Patch: \n-------------------------------\n \n \nand Computerized Patient Record System (CPRS). A message will be displayed\nThe following is a list of fields included in this patch:\n \nField Name (Number) File Name (Number)\n---------------------------------------- ------------------------------\nEXCLUDE FROM ALL DOSE CHECKS 9 ADMINISTRATION SCHEDULE 51.1\nEXCLUDE FROM DAILY DOSE CHECK 10 ADMINISTRATION SCHEDULE 51.1\nDOSING ON/OFF 95 PHARMACY SYSTEM 59.7\nDOSING ACTIVITY DATE AND TIME subfile 82 of PHARMACY SYSTEM 59.7:\n DOSING ACTIVITY DATE AND TIME .01\n PERSON MAKING CHANGE 1\nto the user if the Single Dose entered for the medication order and all\n ENABLE/DISABLE 2 \n \nThe following is a list of data included in this patch:\n \nFile Entry\n------------------- -------------\nDOSE UNITS (#51.24) FILM(S)\nDOSE UNITS (#51.24) ELISA UNIT(S) \nDOSE UNITS (#51.24) MILLIONUNIT(S) new synonyms only:\n MILLION UNIT\nthe other pertinent data is able to be properly converted for a valid\n MILLION UNITS\n \n \nThe following is a list of templates included in this patch:\n \nTemplate Name Type File Name (Number)\n------------------ ----- -------------------------------\nPSSJ SCHEDULE EDIT Input ADMINISTRATION SCHEDULE (#51.1)\n \n \nDosing Check, and the result is an out-of-range warning. An error message\nThe following is a list of options included in the patch:\n \nOption Name Type\n-------------------------- ----\nPSS DRUG DOSING LOOKUP Run\nPSS DOSING ORDER CHECKS Run\nPSS TRAILING SPACES REPORT Run\n \n \nThe following is a list of security keys included in this patch:\nwill be displayed if for any reason the Single Dose check cannot be \n \nSecurity Key Name\n-----------------\nPSS ORDER CHECKS\nperformed.\n \n\n
\nThis patch is part of a group of patches that make up the new Medication \n \nThis patch also makes a second line patch list correction to the routine \nPSS551. In patch PSS*1*169, the second line of the routine mistakenly \nlisted patch 260. This patch removes the 260 designation.\n \nMOCHA v2.0 consists of the following patches:\n1. PSS*1*160\n2. MOCHA_2_0.KID host file which contains PSJ*5*252, PSO*7*372 and\nOR*3*345\n3. PSS*1*173\nThis patch is part of a group of patches that make up the new Medication \n4. MOCHA_2_FOLLOW UP COMBINED BUILD.KID host file which contains \nPSJ*5*257, PSO*7*416, OR*3*311 and GMRA*4*47\n \nThese files and patches contain software that supports MOCHA v2.0 \nfunctionality. The host files were created to simplify installation at \nVeterans Health Administration (VHA) facilities.\n \nPlease refer to the Installation Guide for installation instructions.\nOrder Check Healthcare Application v2.0 (MOCHA). These patches will add a\nmaximum single dose order check to the current Veterans Health Information\nSystems and Technology Architecture medication order checking system that\nuses the First DataBank (FDB) business logic and database. FDB custom\ndosing tables will be used to store custom dosing changes to FDB standard\nreference drug tables. Pharmacy Enterprise Customization System v.2.2\n(PECS) application was developed to meet the customization requirements.\n\n
\n Patch PSS*1*16 contains resolutions to the following issues:\n DA variable from the Kill logic and placed it in a clean up routine \n PSSDEE2. \n \n 2. In routine PSSDEE at APP+0, we changed the statement, "MARK \n THIS DRUG FOR AND EDIT" to "MARK THIS DRUG AND EDIT IT FOR:". \n \n 3. It corrects a problem indicated in NOIS BIR-1098-32686. The site \n indicated that the CMOP ID is no longer appearing in the Lookup into \n Dispense Drug File [PSS LOOK] option. This patch will correct \n this problem. \n \n 1. It corrects a problem indicated in NOIS LOU-0698-40167. In the \n Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, the system encountered \n an undefined variable (DA) when a user tried to mark a drug as \n Clozapine. The error was detected at UD^PSSDEE; however after \n further analysis, the culprit was really discovered in routine \n PSSCLDRG. In routine PSSCLDRG, ASK+3,END+0, and UNMARK+1, the DA \n variable is a part of the Kill logic. In this patch, we removed the \n\n
\nThis patch will correct the issues reported.\nperformed automatically. This happens before the user gets asked the\nquestion 'Do you want to merge new Local Possible Dosages?'\n \n3) HD0000000347730 - Errors in reminder index for non-VA meds\nThe VistA 'Clinical Reminders Index Build' [PXRM INDEX BUILD] option runs\nthe ^PSSSXRD routine used to create and rebuild the Clinical Reminders\nIndex and the ^PSOPXRMU routine used by the cross-reference to keep the\nindex current differ in how they set the discontinued date when that it is\nmissing. The differences in the discontinued date cause the Clinical\nReminders to be inaccurate.\n \n \n4) HD0000000500625 - Medication Reconciliation national component \n displaying on scalp instead of subcutaneous\nWhen users change the name of a Medication Instruction using the VistA\nMedication Instruction File Add/Edit [PSSJU MI] option, the system does\nperform the duplicate entry check. This allows users to create duplicate\nentries which in turn cause the Medication Reconciliation to display the\nincorrect data.\n \n5) HD0000000507504 - User unable to mark/unmark drugs for CMOP\n1) HD0000000174282 - Problem with PSS LOOK option\nWhen using the VistA 'CMOP Mark/Unmark (Single drug)' [PSSXX MARK] option\nand the users tries to mark or unmark drugs for CMOP the system displays\n"Do you wish to mark this drug to transmit to CMOP?"\n"Enter Yes or No: "\nIf the user enters a "Yes" or "No" response, the system repeats the \nprompt.\nIf the user enters a "Y", "y", "N" or "n" the system accepts the entry.\nThe VistA option 'Lookup into Dispense Drug File' [PSS LOOK] does not work\nthe same as the 'Drug File Inquiry' [PSB DRUG INQUIRY] option.\n \n2) HD0000000230104 - Using Drug Enter/Edit Option in PDM, local possible\n dosage merge performed automatically.\nWhen Using Drug Enter/Edit Option in PDM, local possible dosage merge\n\n
\nThis patch modifies the Application Programming Interfaces (API), \n$$DETOX^PSSOPKI to return a "1" (one) only if the drug name contains \n"BUPREN" and the dosage form does not contain "PATCH", otherwise a 0 \n("zero").\n\n\nThis patch will correct the following reported issues:\nDrug Enter/Edit options, the prompt for Additive Frequency is missing.\nCurrently the only way to edit the ADDITIVE FREQUENCY field (#18) is\nthrough FileMan.\n \n3) INC000000942809 - Message Sent field (#3) in the Vendor Interface\n Data file (#59.74) not populating.\nA defect was discovered with the population of the Message Sent field \n(#3) in the Vendor Interface Data file (#59.74). When the Interface\nScheduler [PSS INTERFACE SCHEDULER] job receives an error indicating\nthat the Vendor Database is down, it makes an entry in the Vendor\n \nInterface Data file (#59.74) and sends a VistA MailMan message to the\nmail group PSS ORDER CHECKS. When the message is sent, the message\nsent field(#3) is not being updated with the message sent flag.\n1) INC000000324382 - Drug Enter/Edit option\nThe Drug Enter/Edit [PSS DRUG ENTER/EDIT] VistA option deletes a drugs\nPossible Dosage of an inactive drug if the user answers YES to the "Do you\nwish to match/rematch to NATIONAL DRUG file?" prompt.\n \n2) INC000000861438 - PSSIV ADD Input Template \nWhen editing an IV Additive, using both the Additives File and the \n\n
\nThis patch will correct the issue reported in:\nINC000000824872 - UPDATE FDA MED GUIDES URL\nThe automatic printing functionality does not connect to the secure \nSharepoint to retrieve the requested guide and a sheet of paper prints \non my printer "ERROR: UNABLE TO AUTOMATICALLY PRINT MEDICATION GUIDE".\n\n
\nPatch PSS*1.0*190 addresses the following issue:\n \nUnable to enter new national drug interactions into Drug Interactions \nfile (#56).\n\n
\nThis patch will correct the issue reported:\n* This patch contains an environment check and will only install *\n* if one of the following conditions is met. *\n* *\n* 1) If the site is a CMOP site this patch will be installed. *\n* *\n* 2) If you are NOT a CMOP site and patches PSJ*5.0*194 and *\n* PSO*7.0*282 are installed. *\n* *\n* *\n*********************************************************************\n \n \n1) INC0000149525 - Problems placing PRN orders with multiple spaces/words\n \n \n*********************************************************************\n* WARNING *\n* *\n\n
\nHAPE EDI Revenue project - NCPDP Continuous Maintenance Standards\n\n
\nPatch PSS*1.0*191 provides enhancements to Pharmacy Data Management \norder:\n \n1. PSS*1*191\n2. PSJ*5*315\n3. PSB*3*83\n4. OR*3*417\n5. PSB*3*87\n \nATTENTION: This enhancement also includes a new Graphical User Interface\n(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is\nto support changes to the BCMA and Inpatient Medications\nrequired immediately after the KIDS install for the Patch to function.\n \nFor retrieval and installation instructions, please see the Client \nInstallation Instructions section.\n**************************************************************************\n \nThese enhancements are made to address NSR 20141012. \n They include: \n \n 1. Currently Sites have to create fake removal orders to allow for \napplications for Transdermal Administrations.\nappropriate removal of medications in BCMA. This patch will alleviate \nthat issue by adding a field to the ORDERABLE ITEM (#50.7) file titled \nPROMPT FOR REMOVAL IN BCMA (#12). This field implements changes that will\nsupport enhancements to the BCMA and Inpatient Medication applications to \ndisplay the removal times in Inpatient Medication orders using rules \ndetermined by the value of this field. The PROMPT FOR REMOVAL IN BCMA \n(#12) field can be set for Orderable Items that require removal to the \nfollowing values:\n \n NULL/0=No Removal Required \n \n 1 = Removal at Next Administration \n 2 = Removal Period Optional Prior to Next Administration \n 3 = Removal Period Required Prior to Next Administration\n \n 2. A post installation routine, PSS1P191, will update the new PROMPT\nFOR REMOVAL IN BCMA (#12) field to a value of 1 for all Orderable Items\nwith a Dosage Form that contain the word "PATCH". A message will be sent\nto the installer as well as all users holding the PSJU and PSJI MGR keys\nproviding a list of Orderable items that were updated during this process.\nThe PROMPT FOR REMOVAL IN BCMA (#12) field is only updated if it is\n******************************* ATTENTION ********************************\ncurrently set to a value of NULL so subsequent installations will not \nupdate the PROMPT FOR REMOVAL IN BCMA (#12) field again.\n \n 3. Routines edited for this patch will add the prompt "PROMPT FOR \nREMOVAL IN BCMA:" to the following three options:\n \n - Edit Orderable Items [PSS EDIT ORDERABLE ITEMS]\n - Drug Enter/Edit [PSS DRUG ENTER/EDIT]\n - Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE \n ITEMS]\n \n \n 4. Patch PSS*1.0*172 inadvertently missed adding the prompt, HIGH \nRISK/HIGH ALERT, to the following options, which is being added in \nthis patch:\n \n - Drug Enter/Edit [PSS DRUG ENTER/EDIT]\n - Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE\n ITEMS]\n \n5. A second post install routine PSSP191A will create another\nClinical Ancillary Services (CAS) Development-Delivery of Pharmacy \nemail report. This report will display orders for Medications Requiring \nRemoval that do not contain the necessary file structures to allow for \nthe new removal functionality to execute. The primary purpose for this \ninformation is to allow the site to determine the approximate amount of \nresources needed to discontinue these orders and re-create them after \npatch PSJ*5*315 is installed. Until the PSJ*5*315 patch is installed the \ncapability for processing these orders will not be available. More \ndetailed procedures and recommendations for this process are in the \ninstallation section of this Patch Description. A copy of this report \nwill be added to the Pharmacy Data Management [PSS MGR] menu as the Orders\nEnhancements (DDPE) VA Inpatient Medication Administration - Transdermal\nfor MRRs With Removal Properties [PSS MRR ORDERS DIAGNOSTIC RPT] option.\n \n 6. Two more reports will be added to the Orderable Item Management \n[PSS ORDERABLE ITEM MANAGEMENT] sub menu as options. The new report\noptions, Orderable Items that Require Removal Report [PSS MRR ORDERABLE\nITEMS RPT] option and Orderable Items Report for High Risk\\High Alert [PSS\nHR/HA ORDERABLE ITEMS RPT] option, will allow review of the settings in\nthe Orderable Items file (#50.7) for the values of the respective fields\nindicated in the report titles.\n \nenhancement includes 5 patches which must be installed in the following\n PSS*1.0*191 does not have any dependencies for installation.\n The full functionality introduced in this patch will not be\n available until patches PSJ*5.0*315, PSB*3.0*83 and PSB*3.0*87 \n are installed.\n \n Pre-existing orders will remain unaffected with installation.\n\n
\nThis patch is part of the Pharmacy Safety Updates project which was \n APPLICATION/VERSION PATCH\n New INPUT TRANSFORMS have been added to the VOLUME (#2) and USED IN IV\n FLUID ORDER ENTRY (#17) to enforce the following new rule introduced \n relating to this file: \n \n Rule: An Orderable Item can have only ONE IV solution with a specific\n volume when it is marked to be used in the IV Order Dialog.\n \n5. PSSCOMMON input template\n The PSSCOMMON input template used by the Drug File Enter/Edit [PSS DRUG\n ENTER/EDIT] option was modified to include the new MAXIMUM\n -----------------------------------------------------------------\n DAYS SUPPLY field (#66) in the DRUG file (#50) so that it can be edited\n along with the other fields in this option.\n \n6. PSSJ SCHEDULE EDIT Input template\n The PSSJ SCHEDULE EDIT input template used by the Standard Schedule \n Edit [PSS SCHEDULE EDIT] option was modified to include the new INACTIVE\n field (#12) in the ADMINISTRATION SCHEDULE file (#51.1) so that it can\n be edited along with the other fields in this option.\n \n7. Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] option \n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444\n This option was modified to display the IV Additive Strength value as\n seen below:\n \n ... \n Orderable Item -> PIPERACILLIN/TAZOBACTAM\n Dosage Form -> INJ\n \n Dispense Drugs:\n ---------------\n PIPERACILLIN 3/TAZOBACTAM 0.375GM/VI INJ\n INTEGRATED BILLING (IB) V. 2.0 IB*2*545\n PIPERACILLIN 2/TAZOBACTAM 0.25GM/VI INJ\n PIPERACILLIN 4/TAZOBACTAM 0.5GM/VI INJ\n PIPERACILLIN/TAZOBACTAM (A) Additive Strength: 3.375 GM \n PIPERACILLIN/TAZOBACTAM (A) Additive Strength: 2.25 GM \n PIPERACILLIN/TAZOBACTAM (A) Additive Strength: 4.5 GM \n ...\n \n8. PRimary Solution File (IV) [PSSJI SOLN] option\n This option was modified to enforce a new rule introduced to ensure that\n an Orderable Item can only have 1 active IV SOLUTION linked to it with a\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189\n specific VOLUME when the IV SOLUTION is marked YES for the USED IN IV\n FLUID ORDER ENTRY field (#17). When they user tries to perform an edit\n that breaks this rule by editing the screen fields VOLUME, USED IN IV\n FLUID ORDER ENTRY or INACTIVATION DATE, the error message below will be\n displayed and the editing won't be permitted.\n \n Only one Active IV Solution with a specific volume can be linked to\n an Orderable Item or Dispense Drug when the IV Solution is marked to\n be used in the CPRS IV Fluid Order Entry.\n \n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429\n9. Drug Enter/Edit [PSS DRUG ENTER/EDIT] option \n a) This option was modified to allow entry of the new MAXIMUM DAY SUPPLY\n \n ...\n NCPDP DISPENSE UNIT: EACH// \n NCPDP QUANTITY MULTIPLIER: 1// \n MAXIMUM DAYS SUPPLY: ??\n This field is used to determine the maximum number for days supply that\n may be assigned to this drug. The maximum value allowed for this field\n is 365 (days) for most drugs, however: \n INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313\n \n - Schedule 2 controlled substances have a 30-day maximum days supply \n limit \n - Schedules 3 thru 5 controlled substances have a 90-day maximum days\n supply limit \n - The maximum number of days supply for this drug cannot exceed the\n National Drug File (NDF) maximum value if it exists\n - No value can be entered for Clozapine drugs as the maximum days\n supply is controlled by the Clozapine functionality\n \n \n MAXIMUM DAYS SUPPLY: \n PRICE PER DISPENSE UNIT: 0.8280\n ...\n \n b) The exact same change described above in #8 was applied to this option\n where the user can create, edit and link IV Solution entries to a \n dispense drug.\n \n10. Lookup into Dispense Drug File [PSS LOOK] option\n This option was modified to display the new MAXIMUM DAYS SUPPLY (#66)\n \n field in the DRUG file (#50) along with the other dispense drug fields for\n the dispense drug selected, as shown below:\n \n ...\n DISPENSE UNIT: VA DISPENSE UNIT: CAP\n DISPENSE UNITS/ORDER UNIT: 20 PRICE/DISPENSE UNIT: 0.8280\n NCPDP DISPENSE UNIT: EACH NCPDP QUANTITY MULTIPLIER: 1.000\n MAXIMUM DAYS SUPPLY: 100\n APPL PKG USE: Outpatient Unit Dose Non-VA Med\n STRENGTH: 10 UNIT: MG\nThe following New service Requests (NSRs) are being addressed by this patch:\n POSSIBLE DOSAGES:\n ... \n \n11. Standard Schedule Edit [PSS SCHEDULE EDIT] option\n This option was modified to add the new INACTIVE field (#12) in the \n ADMINISTRATION SCHEDULE file (#51.1) to be updated for a schedule.\n \n ...\n OTHER LANGUAGE EXPANSION: \n INACTIVE: ??\nestablished to address specific New Service Requests (NSRs) as well as a\n \n This field is used to indicate that a Standard Schedule is inactive.\n Inactive schedules are filtered from the list of schedules sent to CPRS\n for selection when users are placing a medication order.\n \n Choose from: \n 1 YES\n INACTIVE: \n ...\n \n12. Administration Schedule File Report [PSS SCHEDULE REPORT] option\n NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply\n This option was modified to display the new INACTIVE field (#12)\n created in the ADMINISTRATION SCHEDULE file (#51.1) as seen below:\n \n ADMINISTRATION SCHEDULE FILE REPORT (All) PAGE: NN\n ----------------------------------------------------------------------\n ... \n *Q4H\n STANDARD ADMINISTRATION TIMES: 01-05-09-13-17-21\n OUTPATIENT EXPANSION: EVERY 4 HOURS\n OTHER LANGUAGE EXPANSION: \n ---------------------------------------------------------------------------\n SCHEDULE TYPE: CONTINUOUS\n FREQUENCY (IN MINUTES): 240\n EXCLUDE FROM ALL DOSE CHECKS: \n EXCLUDE FROM DAILY DOSE CHECK: \n INACTIVE: YES\n ...\n \n13. Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE ITEMS] &\n Drug Enter/Edit [PSS DRUG ENTER/EDIT] options\n A new rule described below is being introduced which is related to the\n The Outpatient Pharmacy and supporting VistA applications are being modified\n relationship between IV Solutions and Orderable Items.\n \n Rule: An Orderable Item can only have ONE IV solution with a specific\n volume when it is marked to be used in the CPRS IV Order Dialog.\n \n This option was modified to check every time the user tries to link a \n dispense drug to an orderable item whether the new rule is being broken\n or not. If the new rule is being broken the message below will be\n displayed and the user will not be able to proceed with linking the drug\n to the orderable item.\n to allow dispensing of more than 90 day supply fill for outpatient \n \n Matching [Dispense Drug Name] to [Orderable Item Name] would cause\n the orderable item to have more than one Active IV Solution with the\n same volume marked to be used in the IV FLUID ORDER ENTRY, which is\n not allowed.\n \n Please, review the IV Solutions associated with this drug before\n matching it to this orderable item or match it to a different \n orderable item.\n \n prescriptions. The new limit will be 365 days and will be set for each drug\n14. IV Solution Pre-Install Manual Clean-up (Environment Check routine)\n An environment check routine will run before the patch is installed to\n ensure that an orderable item does not have more than one IV Solution\n with the same volume when they are marked YES to be used in the CPRS IV\n Fluid Order Entry. If at least one orderable item entry is found, the\n patch installation will be aborted and a Mailman message will be sent to\n all users holding the following security keys: PSIVMGR, PSIJ MGR, PSNMGR.\n The message will contain a list of all orderable items that need to be \n cleaned up, as seen in the sample message below:\n \n individually. See below for more information on specific menu \n Subj: Duplicate IV Solution Volume under same Orderable Item [#215733]\n From: PATCH PSS*1*189 In 'IN' basket. Page 1\n -------------------------------------------------------------------------\n The list below shows IV Solutions in your database that need to be\n cleaned up before patch PSS*1*189 can be installed.\n \n Rule: An Orderable Item can only have ONE IV solution with a specific\n volume when it is marked to be used in the IV Order Dialog.\n \n Run Date/Time: Jun 12, 2015@09:49:16\n options related to this enhancement. \n -------------------------------------------------------------------------\n ORDERABLE ITEM (IEN)\n IV DISPENSE DRUG (IEN)\n IV SOLUTION (IEN)\n -------------------------------------------------------------------------\n DEXTROSE (196)\n Solution Volume: 1000 ML\n DEXTROSE 10% IN WATER (620)\n DEXTROSE 10% (7)\n DEXTROSE 5% IN 0.45% NS (623)\n \n DEXTROSE 5% 1/2 NS (10)\n DEXTROSE 5% 1000ML INJ (627)\n 5% DEXTROSE (1)\n \n15. IV Solution Post-Install Automatic Clean-up (Post-install routine)\n IV Solutions that are no longer used, meaning that either the IV\n Solution and/or the Dispense Drug and/or the Orderable Item are marked\n INACTIVE will have the field USED IN IV FLUID ORDER ENTRY set to 'NO'.\n A list of such IV Solutions will be sent to all users holding the\n following security keys: PSIVMGR, PSIJ MGR, PSNMGR. The message will\n NSR 20110308 Addition of a STRENGTH Property to IV ADDITIVES and Premixed \n contain a list of all IV Solutions that have been automatically updated\n as seen in the sample message below:\n \n Subj: Auto-update of the IV Solution file [#216328] 08/18/15@09:58 \n From: PATCH PSS*1*189 In 'IN' basket. Page 1 *New*\n -------------------------------------------------------------------------\n The list below shows IV Solutions in your database that had the field\n USED IN IV FLUID ORDER ENTRY set to 'NO' because either the Orderable\n Item, the Dispense Drug or the IV Solution itself was marked INACTIVE.\n \nRemedy Ticket and a Patient Safety Issue (PSI) related to the VistA Pharmacy\n IV SOLUTIONS\n Run Date/Time: Aug 18, 2015@09:58:38\n -------------------------------------------------------------------------\n ORDERABLE ITEM (IEN)\n IV DISPENSE DRUG (IEN)\n IV SOLUTION (IEN/VOLUME)\n -------------------------------------------------------------------------\n CEFAZOLIN (106)\n CEFAZOLIN SOD 1GM INJ (1498)\n 20% DEXTROSE (2/500 ML) *** INACTIVE DATE: JAN 11, 1994 ***\n 20% DEXTROSE (11/500 ML) *** INACTIVE DATE: JAN 11, 1994 ***\n ----------------------------------------------------------------------------\n \n16. New API for CPRS: $$MAXDS^PSSUTIL1\n This new API was created for CPRS to retrieve the Maximum Days Supply\n value for a specific medication. This API is available to CPRS through\n the Integration Control Registration (ICR) #3239. Below is a detailed \n description of the API.\n \n $$MAXDS^PSSUTIL1(INPUT)\n This API accepts an array containing the Pharmacy Orderable Item\n (required) and Dispense Drug (optional) and returns the maximum number\n Although patches PSJ*5*289 and PSS*1*174 introduced quite a few enhancements\n of Days Supply allowed to be dispensed for the specific medication.\n \n Parameters:\n Input: INPUT("PSOI") (Required)\n Pointer to the PHARMACY ORDERABLE ITEM file (#50.7). \n \n INPUT("DRUG") (Optional)\n Pointer to the DRUG file (#50). This parameter is optional.\n If not passed, the API will return the highest value from all\n the dispense drugs linked to the Pharmacy Orderable Item. \n to the IV Additives and IV Solutions ordering functionality they did not go\n \n Output $$MAXDS\n Maximum number of days supply that can be dispensed for the\n orderable item and/or dispense drug.\n \n17. IV Additives and Solutions - Display "INACTIVATION DATE"\n \n The INACTIVATION DATE will display whenever a VistA lookup is done on\n IV Additives and Solutions.\n \n far enough in addressing all the issues originally in the NSR. Patches \n This was accomplished by making the following two fields identifiers:\n \n FIELD NAME FIELD NUMBER FILE NAME/NUMBER\n ----------------------------------------------------------\n INACTIVATION DATE 12 IV ADDITIVES (#52.6)\n INACTIVATION DATE 8 IV SOLUTIONS (#52.7)\n \n \n Note: The following 'HELP'-PROMPT text will display for fields 8 & 12\n "Enter the date this drug was inactivated.\n PSJ*5*313 and PSS*1*189 will extend the display of the IV Additive strength\n \n \n \n ********************* EXAMPLE(1) ADDITIVES *********************\n \n Inpatient Drug Management - Additives File [PSSJI DRUG] \n \n Select Inpatient Drug Management Option: Additives File\n Select IV ADDITIVES PRINT NAME: PIPERACILLIN\n \n to other parts of the Inpatient Medications and Pharmacy Data Management \n Lookup: IV ADDITIVES PRINT NAME\n 1 PIPERACILLIN/TAZOBACTAM Additive Strength: 3.375 GM\n 2 PIPERACILLIN/TAZOBACTAM Additive Strength: 2.25 GM \n 3 PIPERACILLIN/TAZOBACTAM 03-5-2015 Additive Strength: 4.5 GM \n \n \n ********************* EXAMPLE(2) SOLUTIONS *********************\n \n Inpatient Drug Management - Primary Solution File (IV)\n \n applications. In addition, it will also impose a new rule where an Orderable\n Select Inpatient Drug Management Option: PRImary Solution File(IV) \n Select IV SOLUTIONS PRINT NAME: DEXTROSE 5% / NACL\n Lookup: PRINT NAME\n 1 DEXTROSE 5% / NACL 0.2% 1000 ML \n 2 DEXTROSE 5% / NACL 0.33% 1000 ML \n 3 DEXTROSE 5% / NACL 0.45% 1000 ML 12-03-15 \n 4 DEXTROSE 5% / NACL 0.9% 1000 ML \n \n ********************* END EXAMPLES ********************* \n Item can only have one IV Solution for a specific volume when it is marked\n to be used in the CPRS IV Fluid Order Entry. \napplications as approved by the Health Systems Enterprise Systems Manager\n \n NSR 20080907 Inactivate Pharmacy Standard Schedule\n ----------------------------------------------------------------------------\n This enhancement is a conversion of an existing Class III software solution\n that permits an entry in the ADMINISTRATION SCHEDULE file (#51.1) to be \n marked as INACTIVE via the Standard Schedule Edit [PSS SCHEDULE EDIT] option.\n Once marked INACTIVE the schedule is no longer shown on the CPRS \n ADMINISTRATION SCHEDULE list.\n \n \n(ESM).\n \nThe following Pharmacy Data Management functionality was modified:\n \n1. New MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50)\n This new field shown below was added to the DRUG file (#50) for storing\n the local maximum day supply value for a medication in an outpatient \n prescription.\n \n Field Name: MAXIMUM DAYS SUPPLY Format: Numeric\n \n \n INPUT TRANSFORM: D MXDAYSUP^PSSDDUT2\n HELP-PROMPT: This is the maximum number of days supply for this drug. \n DESCRIPTION: This field is used to determine the maximum number for\n days supply that may be assigned to this drug. The\n maximum value allowed for this field is 365 (days) for\n most drugs, however: \n \n - Schedule 2 controlled substances have a 30-day maximum\n days supply limit\n - Schedules 3 thru 5 controlled substances have a 90-day\nThis project is comprised of patches from five different applications, as\n maximum days supply limit \n - The maximum number of days supply for this drug cannot\n exceed the National Drug File (NDF) maximum value if it\n exists \n - No value can be entered for Clozapine drugs as the\n maximum days supply is controlled by the Clozapine\n functionality\n \n2. ADMINISTRATION SCHEDULE file (#51.1)\n a) A new field named INACTIVE (#12) shown below was added to the \nshown below:\n ADMINISTRATION SCHEDULE file (#51.1) to allow the filtering inactive\n schedules when providing a list to the CPRS application.\n \n Field Name: INACTIVE Format: Set of Codes ('1' FOR YES)\n \n HELP-PROMPT: Answer YES to mark this administration schedule entry\n as inactive. \n DESCRIPTION: This field is used to indicate that a Standard Schedule\n is inactive. Inactive schedules are filtered from the\n list of schedules sent to CPRS for selection when users\n \n are placing a medication order. \n \n b) The upper limit for the FREQUENCY (IN MINUTES) field (#2) was increased\n from 129,600 (90 days) to 525,600 (365 days).\n \n3. MEDICATION INSTRUCTION file (#51)\n The upper limit for the FREQUENCY (IN MINUTES) field (#31) was increased\n from 129,600 (90 days) to 525,600 (365 days).\n \n4. IV SOLUTIONS file (#52.7)\n\n\n This KIDS Build contains the Pharmacy Data Management Enhancement patch.\n 2. The Enter/Edit Drug Interaction [PSS INTERACTION LOCAL ADD] option\n will be modified to generate a MailMan message whenever a local drug\n interaction are added or a change is made to the severity of a\n nationally entered drug interaction.\n \n 3. Two new fields were added to the PHARMACY SYSTEM file (#59.7). The\n fields are PMIS PRINTER (#13) and PMIS LANGUAGE (#14). The Parameters\n Edit [PSS SYS EDIT] option will allow the user to access the fields.\n \n 4. In reference to the Lookup into Dispense Drug File [PSS LOOK] option,\n It contains DDs for specific files and routines.\n code was added to routine PSSLOOK to display the National Formulary\n and National Restriction fields.\n \n 5. In reference to the CMOP Mark/Unmark [PSXX MARK] option, code was\n added to routine PSSDINT to display the reasons why a drug cannot be\n marked for CMOP use.\n \n 6. This patch also corrects a potential problem found when generating\n the default frequency using the option Standard Schedule Edit [PSS\n SCHEDULE EDIT].\n \n The following issues are included in the KIDS Build:\n \n 1. A new INACTIVATION DATE field (#7) was added to the DOSAGE FORUM\n file #50.606. Also, a new INACTIVATION DATE field (#5) was added to\n the MEDICATION ROUTES file (#51.2).\n \n\n
\nThis patch addresses three (3) issues:\n3. Incorrect cross references may remain, and errors may occur during\n execution of the PSS EDIT TEXT option.\n \n1. Users may not be aware that changing a drug's strength does not change\n the concentration.\n \n2. The FileMan Description on the SYNONYM (#.01) field of the SYNONYM \n SUB-FIELD (#50.1) file for the DRUG (#50) file does not match the\n Input Transform.\n \n\n
\nMCCF ePharmacy Compliance Phase 3\n\n
\nThis patch will correct the following reported issues:\n in option PSS SCHEDULE PEPS INTERFACE CK is set to a low value,\n resulting in system issues.\n \n4) Drug-Drug Interaction Order Check cannot be validated when performing \n option PSS CHECK PEPS SERVICES SETUP.\n \n1) An error occurs during the drug renewal process if the drug has a \n lengthy drug-drug interaction check.\n \n2) An error may occur in the option PSS SCHEDULE EDIT if the user jumps \n ahead to various fields.\n \n3) Numerous background tasks might be tasked if the scheduling frequency \n\n
\nThe Pharmacy Interface Automation Project will provide a new standard\n \nNote: The patches should be installed in the order listed above as the \nlogical link, PSJ PADE used in the PSS patch is transported in the PSJ\npatch.\n \nAs part of this patch PSS*1*193, the following enhancements were made:\n \n1. Two new protocols PSS MFNM01 CLIENT and PSS MFNM01 SERVER were added to\nfacilitate sending MFN HL7 drug messages to PADE.\n \nbi-directional HL7 interface to the Pharmacy Automated Dispensing\n2. The Send Entire Drug File to External Interface [PSS MASTER FILE \nALL] option was modified to allow transmission of the drug file to an \nInpatient Interface (PADE) depending on the PADE setup. It also \nprovides the flexibility of sending all drugs marked for Unit Dose, \nIntravenous (IV) or Ward Stock or send selected drugs to PADE.\n \nSince this option now allows to send all or selected drugs to PADE, the\noption name "Send Entire Drug File to External Interface" was changed \nto "Send Drug File Entries to External Interface"\n \nEquipment (PADE) located at the point of care areas such as Inpatient\n3. A new PSS PADE INIT security key was added so that holders of this key \ncan only send "all" drugs to PADE noted in item 2.\n \n4. Option Drug Enter/Edit [PSS DRUG ENTER/EDIT] was modified to send an \naddition/update/both or none to PADE provided it is setup to receive such\nupdates.\nwards, Outpatient Clinics etc. The outbound HL7 messages will be triggered\nwhen drugs are added or modified depending on the site parameter setup.\n \nThe following two patches are provided for this project:\n PSJ*5*317 - Inpatient Medications V. 5.0.\n PSS*1*193 - Pharmacy Data Management V. 1.0.\n\n
\nThis patch will correct the following issues:\n user may not be aware that not all lines are displaying on the screen.\n \n3) Outpatient Pharmacy CK Action not working after Check Drug \n Interactions option is invoked if user enters "^" to exit out.\n \n1) The API DRGIEN^PSS50P7 that returns the Dispense Drugs in the DRUG \n file (#50) matched to a PHARMACY ORDERABLE ITEM file (#50.7) is not \n returning all matches if a Dispense Drug happens to have the same \n internal entry number in the DRUG (#50) file as the PHARMACY ORDERABLE \n ITEM (#50.7) file entry it points to. \n \n2) Lines may scroll off the screen when checking drug interactions. The \n\n
\nThis patch addresses the following three (3) issues:\n \n(3) The FIRST DATABANK UNIT (#1) field of the DOSE UNITS (#51.24) file \n for "APPLICATORFUL(S)" should be "APPLICATORFUL" instead of \n "APPLICATORFUL/S", and for "SUPPOSITOR(IES)", it should be\n "SUPPOSITORY" instead of "SUPPOSITORY/IES".\n \n(1) Patch PSS*1*127 incorrectly populated the NCPDP DISPENSE UNIT (#82) \n field of the DRUG (#50) file entry matched to VA PRODUCT (#50.68) \n file entry "MEMANTINE HCL 5MG/10MG TAB TITRATION PAK,49" (internal\n entry number 16512) as "RA" instead of "EA".\n \n(2) When invoking the PSS MAINTAIN ORDERABLE ITEMS option, several \n issues may occur involving the "INACTIVE DATE" prompt.\n\n
\nMOCHA 2.1 Dosing Enhancements.\n\n
\nThis patch is only installed by the CPRS group of package builds.\n PSS PRIMARY DRUG EDIT\n PSS PRIMARY/VA GENERIC REPORT\n PSS VA GENERIC DRUG REPORT\nThese options are deleted at the site.\nThis patch SHOULD NOT be installed outside of the CPRS build.\n \n \nRe-Install File 55 (Pharmacy Patient) for Inpatient Medications V. 5.0.\n \nOptions PSS CREATE ORDERABLE ITEMS\n PSS ORDERABLE ITEM STATUS\n PSS PRE-RELEASE MANUAL MATCH\n\n
\nThis patch addresses three (3) issues:\n between 0 and 222, 4 decimal digits". This does not accurately \n reflect the data stored in this field. There are many drug items\n on the market with a Price Per Dispense Unit greater than $222.\n \n The Data Dictionary needs to be updated to more accurately reflect\n the content of the field. \n \n3. There is an issue with the PRINT NAME Field (#.01) in the IV ADDITIVE \n File (#52.6) when it contains a tilde (~). When an IV label is \n printed for an additive that has a print name that contains a tilde, \n \n it may not display the amount of the IV additive. When the tilde is\n removed, the IV additive amount will print.\n1. When using Drug Enter/Edit [PSS DRUG ENTER/EDIT] Option for a drug\n that has been unmatched from the NDF, the NATIONAL FORUMULARY\n INDICATOR field on the screen displays 'YES" instead of 'NOT\n Matched to NDF'.\n \n2. The Data Dictionary for the DRUG File (#50) PRICE PER DISPENSE UNIT \n Field (#16) is incorrect. The Prompt Message displays "Type a Number \n\n
\n \nThis patch addresses one issue:\n \n1. New BUPRENORPHINE Dosage Form (FILM,BUCCAL) has been approved\n for the treatment of chronic pain and necessitates an update\n in the Detox API\n\n
\nMOCHA 2.1 Dosing Enhancements.\n\n
\nMOCHA 2.1b Follow Up patch.\n\n
\nThis build has been created to provide a Packman message-type patch for \nIndications for Use for Prescriptions and Medication Orders. This will \ngive the user the ability to enter most common indications and/or\nadditional indications for the medications in the Pharmacy Orderable Items\nfile (#50.7).\n\n
\nThis patch implements Medications Dosage Form domain changes required by \nthe Collaborative Terminology Tooling & Data Management (CTT & DM) Native\nStandardization (NDS) project.\n \nPlease see FORUM for full patch description and installation instructions.\n\n
\n This patch addresses three issues.\n processes.\n \n 3. It corrects a typo in the data dictionary for the DISPENSE DRUG field\n (#.02) of the DISPENSE LOG sub-file (#55.0611) in the PHARMACY PATIENT\n file (#55). The sub-file number was changed from 5506.11 to 55.0611.\n \n 1. The IV SOLUTIONS file (#52.7) VOLUME field (#2) has an upper limit\n of 4000ml. This patch will increase the volume field to 9999ml to meet\n the needs of the sites to enter solutions with a volume of greater than\n 4000ml.\n \n 2. It corrects a problem when displaying non-formulary drugs\n associated with the formulary alternative during the drug enter and edit\n\n
\n1. Free text is accepted in the NAME field (#.01) of the \n ADMINISTRATION SCHEDULE file (#51.1) when the TYPE OF\n SCHEDULE field (#5) is set to D (Day of the Week).\n \n2. Changes made to the NAME field (#.01) of the \n PHARMACY ORDERABLE ITEMS file (#50.7) via the Drug \n Enter/Edit [PSS DRUG ENTER/EDIT] option are not \n always reflected in the ORDERABLE ITEMS file (#101.43).\n\n
\nEPIP PSS REMEDIATION 1.0\n\n
\nWarranty issue repairs for MOCHA 2.1B.\n\n
\nUpdates to dosage forms for Buprenorphine containing products.\n\n
\nPSS*1.0*227\n\n
\nIssues:\n \n2. When invoking option PSSJI SOLN:\n \n a) An error occurs if a solution is defined to have 'UNIT DOSE \n MEDICATIONS" usage defined as "quick order only".\n \n b) Quick order restrictions are removed if "IV MEDICATIONS" and/or \n "IV SOLUTIONS" usages are defined as "quick order only".\n \nResolution:\n \n----------\n \nModified routines PSSVIDRG and ORMFN to preserve quick order settings on \nadditives and solutions. These changes also prevented the error which \noccurred when a solution or additive was defined to have unit doses as \n"quick order only".\n \nRoutine ORMFN is included in patch OR*3.0*487U which will be installed \nalong with routine PSSVIDRG in this patch.\n1. When invoking option PSSJI DRUG:\n \n a) An error occurs if an additive is defined to have "UNIT DOSE \n MEDICATIONS" usage defined as "quick order only".\n \n b) Quick order restrictions are removed if "IV MEDICATIONS" and/or \n "IV ADDITIVES" usages are defined as "quick order only.\n\n
\nThis patch has the following enhancements for Clinical Ancillary Services\n \n Help text added for this field during PSS DRUG ENTER/EDIT option:\n \n "K Not Renewable (by telephone)\n \n2. Manage Lookup List Inactive Entries\n \n The following files have added a new field identifier to their data \n dictionaries to indicate if they are marked as Inactive entries.\n \n(CAS) Enhancements (RXSU2).\n a. ADMINISTRATION SCHEDULE file (#51.1) the INACTIVE field (#12).\n b. DRUG TEXT file (#51.7) the INACTIVATION DATE field (#2).\n \n1. Update DEA SPECIAL HANDLING Field Documentation\n \n A new code letter "K" was added to for the DEA, SPECIAL HDLG (#3) in \n the DRUG file (#50) to document in VistA when providers renew\n medications for patients that cannot be automatically renewed by the\n patient via Audiocare.\n\n
\n1) Errors when using the PSS LOOK option in VistA\n2) Hard error within PSS DRUG ENTER/EDIT option for Lab Monitoring\n3) Duplicate prompt to create a new Orderable Item when entering a new \n Drug File entry\n\n
\nPatch PSS*1.0*215 is part of a Multi Build with patch PS0*7.0*452.\nThis build contains the Data Dictionary changes in support of PSO*7.0*452 \nand is a required build for PSO*7.0*452\nPSO*7.0*452 contains the routine changes.\nPSS*1.0*215 contains the DD changes.\n \nThe NSRs involved in this build are:\nNSR20150311 High Cost Rx Report; NSR20151109 Pharmacy Print from Suspense\nby Category; NSR20150512 Early Warning Advisory for Approaching the \nend of Rx Number Ranges; and NSR20151001 Pharmacy Patient Demographics.\n \n\n
\nMCCF EDI TAS EPHARMACY BUILDS 5 & 6\n\n
\nPharmacy Data Management PATCH PSS*1*3. This patch fixes the\nMark/Unmarking of a drug for Controlled Substances vs. Drug\nAccountability/Inventory Interface.\n\n
\nThis patch resolves two issues.\nNeither the field nor template is used by current software. References to\nthe USER file (#3) are contained in the field and template. The\nPHARMACISTS field was flagged for deletion. \n \n1. It creates a new sub-file EXEMPT WARD FROM AUTOCANCEL (#59.701) in the\nPHARMACY SYSTEM file (#59.7). This new sub-file will be used by\nOutpatient Pharmacy to exempt ward locations when prescriptions are\nauto-canceled.\n \n2. It deletes the PHARMACISTS field (#6) from the INPATIENT SITE file\n(#59.4) and PSJIORE input template from the PHARMACY PATIENT file (#55).\n\n
\nThis patch addresses the request from NSR #20170515 - Adds Respiratory \nTherapy Report.\nThis patch distributes one new field, #15, added to file #50.7. The option\nEdit Orderable Items [PSS EDIT ORDERABLE ITEMS] is updated by this patch\nvia its driver routine PSSPOIMO, and is used to mark a drug for use in\nrespiratory therapy treatment of patients. The drugs prescribed to\npatients for respiratory therapy treatment will be displayed in the Report\nfor Respiratory Therapy Medications.\n\n
\nSubject: FIX ERRORS CALLING DOSAGE CHECK\n \n1) Dosing check fails when values are added and then deleted from field\nDRUG(S) FOR DOSING CHK FREQ (#11.1) in the ADMINISTRATION SCHEDULE FILE\n(#51.1)\n \n2) Dosing check fails when an OLD SCHEDULE NAME(S) is used with a PRN\ndesignation.\n\n
\nThis patch will resolve the following issue.\nINC2574335 - Our drug file entry will not let me add the labs associated with\n the drug Clozapine that needs labs attached so that drug checks\n can be performed\n \nProblem: \n--------\nNoth Texas VAMC reported a problem when trying to use the Drug Enter/Edit \n[PSS DRUG ENTER/EDIT] option to mark a dispense drug a 'Clozapine' drug.\nAfter entering the lab test (WBC) and Specimen Type (BLOOD) they would get\na double question mark (??) after answering 'YES' at the 'Is this Correct?'\n \nprompt. \n \nResolution:\n-----------\nThe problem was a result of an internal call to Fileman to save the lab test\ndata. Fileman was getting lost because it found more than one match to the\nIEN for 'BLOOD' in the TOPOGRAPHY FIELD file (#61) because it did not \nrestrict the lookup to IEN only and other entries in that file had the \nABBREVIATION field (#6) set with a value that matched the IEN for 'BLOOD'.\n \nINC2574335 - Our drug file entry will not let me add the labs associated with\nTechnical Resolution:\n---------------------\nChanged the routine PSSCLOZ at CLOZAD2+2 to use 4 slashes (////) instead of\n3 slashes (///) when saving SPECIMEN TYPE FIELD (#2), as shown below:\n \n S DIC("DR")="2////"_PSSPTYN_";3///"_PSSTUFF\n the drug Clozapine that needs labs attached so that drug checks\n can be performed\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n\nThis patch addresses some display issues in the Lookup into Dispense \nDrug File Option [PSS LOOK]\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSS*1*235.\n\n
\nThe purpose of this build is to export the data dictionary for the \nPHARMACY ORDERABLE ITEM file (#50.7) in order to update the APPLICATION \nGROUP field to add GMTS. In addition, it exports the routine to return \nthe pharmacy orderable item information in order to support the Ad Hoc \nreport summary.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSS*1*236.\n\n
\nCORRECT THE URL FOR MEDICATION ROUTE REQUEST\n\n
\nThis patch, along with patch PSN*4*569 will address the following ePrescribing\n--------------------------------------------\n1. INC9317643 - We have noticed a number of drugs that do not auto match for\n inbound eRx orders\n \n DUPLICATE - INC9105989 - erx software auto-matched wrong drug product\n \nProblem: \n--------\nThe VA Health Administration Center Denver reported and issue with incoming\nePrescribing orders (eRx) not automatically matching the ordered drug with a\n(eRx) issue: \nVistA corresponding Dispense Drug, even when the NDC received matches 1 to 1\nwith a specific VA Product entry. They also noticed the issue to be more\nprevalent with dispense drugs that have been recently re-matched to a \ndifferent VA Product entry due to changes from MG to MGC in the strength. \nAfter researching this issue it was determined that the root cause of the\nproblem was a 'corruption' of the "APR" cross-reference in the DRUG file (#50)\nwhich was not properly set or killed after Dispense Drugs were matched,\nun-matched or re-matched to VA Product entries. Such cross-reference is used\nby the eRx drug auto-matching processing and that's the reason it failed\nfor some drugs. It turned out that two other cross-references "AND" and "APN"\n \nalso had the same issue. No user functionality side-effects have been\nreported related to these other two cross-references though.\n \n \nResolution: \n-----------\nThe setting and killing of the "APR", "AND" and "APN" cross-reference have\nbeen completely reviewed at every point where a Dispense Drug is matched,\nun-matched or re-matched to a VA Product and after this patch is installed\nthey should be properly maintained. Furthermore, a post-install routine\n1. INC9317643 - We have noticed a number of drugs that do not auto match for\nwill completely kill off the 3 cross-references and re-build them completely.\nThe NDF (National Drug File) patch PSS*1*243 is also being released along with\nthis patch because the matching functionality is available in both\napplications, NDF and PDM (Pharmacy Data Management). \n \n \nTechnical Resolution: \n---------------------\nChanged the routines PSSDEE1 and PSSUTIL to kill and set the cross-references\n"AND", "APN" and "APR" properly.\n inbound eRx orders\n \n DUPLICATE - INC9105989 - erx software auto-matched wrong drug product\n \nDefect Tracking System Ticket(s) & Overview: \n\n
\n This patch contains the following enhancements:\n 2. Within the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, a\n significant enhancement to the Mark/Unmark for Lab Monitor or\n Clozapine procedure was made.\n \n A. When updating Clozapine information, the user will have a choice\n to add, edit, or delete Clozapine Lab Test(s) for the selected\n drug.\n B. When updating Clozapine information, the user will have to add\n identification of two laboratory tests, WBC and Absolute\n Neutrophil Count (ANC).\n \n C. In the post-installation process, we added code to move data from\n the CLOZ node to the CLOZ2 node in the DRUG file (#50). (This is\n \n 3. In the DRUG file (#50), we expanded the field length of the WARNING\n LABEL field (#8) to 25 characters to allow longer names.\n \n 4. The routine PSSPOIDT was updated to properly delete data from the\n INACTIVE DATE field (#100) in the DRUG file (#50) when a drug is\n reactivated.\n 1. In the pre-installation process, we added code to:\n \n A. Delete the DRUG GROUP/INTERACTION field (#7) from the DRUG file\n (#50). This field has been marked for deletion.\n B. Delete the "I" node in the DRUG file (#50) if it does not contain\n data.\n \n\n
\nRemove HANG command from ST in PSSPRICE.\n\n
\nThis patch provides the functionality to add the other language \nIndications for Use in the PHARMACY ORDERABLE ITEMS file (#50.7).\n \nThe menu options Edit Orderable Items [PSS EDIT ORDERABLE ITEMS], \nDispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE ITEMS] \nand Drug Enter/Edit [PSS DRUG ENTER/EDIT] have been modified to prompt for\nother indications for use.\n\n
\n1. INC9511598 Med Instructions Display incorrectly with Clinic Medications\n Resolution:\n ----------\n This patch adds a new report which displays matches between the \n Medication Instruction file (#51) and the Medication Routes file \n (#51.2). \n \n The MEDICATION INSTRUCTION Name field (File #51) and MEDICATION ROUTE\n Abbreviation field (File #51.2) may have entries that use similar\n terminology and abbreviations but with different clinical meanings.\n The MED INSTRUCTION MED ROUTE TERM REPORT option identifies instances\n \n where the MEDICATION INSTRUCTION Name field and the MEDICATION ROUTE\n Abbreviation field are identical to facilitate review and correction\n of clinically inconsistent terminology between the two files. Local\n Pharmacy Informaticists should review and evaluate this report for\n possible corrective action to ensure that reports which use the\n expansion from the MEDICATION INSTRUCTION file are clinically valid\n when the data originates in the MEDICATION ROUTE file. \n \n This patch adds the Med Instruction Med Term Route Report to the\n Medication Instruction Management menu (PSS MED INSTRUCTION \n Problem:\n MANAGEMENT) and the Medication Routes Management menu (PSS MEDICATION\n ROUTES MGMT).\n \n Upon running the report, sites should refer to the Pharmacy Data\n Management User Manual located on the VistA Software Document Library\n for the dedicated Pharmacy website to discuss the potential options \n for file management or to see previous site's decisions on how similar\n entries were handled.\n \n Documentation updates are applied to the Pharmacy Data Management User\n -------\n Manual as well as the Pharmacy Data Management Technical \n Manual/Security Guide.\n The Med Route abbreviation for Clinic Meds and Inpatient Meds expands \n in the EMLR using the Med Instruction Name if the abbreviation is\n identical, which may result in a mismatch of clinical terminology if\n the fields were not defined properly.\n \n\n
\nThe released patch PSS*1*219 provided functionality to exclude \nbuccal film. \nbuprenorphine-containing products from requiring an X-number (Detox \nNumber) when they are specifically FDA approved with indication for the\ntreatment of pain. This was done by dosage form so that Butrans (patch)\nand Belbuca (film, buccal), the products available at the time, could be\nexcluded. However, a new product, Bunavail has been released to market. \nThis is also a buccal film but is primarily indicated for treatment of\nopioid substance use disorder. Therefore, changes are needed that will\nrequire an X-number when a Bunavail order is placed with a dosage form of\n\n
\nBackup of PSS*1.0*248 on May 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe current CMOP Share site is being decommissioned and will be\n \nhttps://vaww.cmopnational.domain.ext/CR/FDAMedGuides/ \n \nTo:\n \nhttps://vaww.vashare.domain.ext/sites/PBMNat/FDAMedGuides/ \ninaccessible for Med Guide retrieval. The application requires a \nconfiguration upgrade and installation to access the new URL. \n \nThis patch will update the Pharmacy System File (File #59.7) FDA MED GUIDE\nSERVER URL field (Field #100) with the new secure URL.\n \nPost-init routine PSS248P will change the FDA MED GUIDE SERVER URL field\nfrom this: \n\n
\nBackup of PSS*1.0*249 on Jun 17, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of PSS*1.0*226 on Jul 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSS*1.0*226.\n\n
\n This patch contains two enhancements:\n Interaction Management [PSS DRG INTER MANAGEMENT] menu.\n \n 1. In the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, we made\n modifications to routine PSSDEE to identify an entry when it is marked\n for Ward Stock. \n \n 2. A new option, Report of Locally Entered Interactions [PSS REPORT LOCAL\n INTERACTIONS] has been added. This report displays locally entered\n drug interactions and their severity. It is included on the Drug\n\n
\nBackup of PSS*1.0*247 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSS*1.0*247.\n\n
\nThis patch will fix the following:\n \nSome prescriptions for DEA Schedule II medication are allowed to be \nentered for greater than a 30 days supply.\n\n
\nFDA Medication Guide Automatic Printing functionality \n Component installed on servers to work with the new CMOP SharePoint\n URL. \n \n \nIf your site is currently utilizing the FDA Med Guide Auto Printing \nthe updated Java Application Components included in \nthis release, must be installed immediately following the installation \nof PSS*1*257. Failure to do so will disable Automatic printing \nfunctionality until the updated Java Application Component software is \ninstalled. \nincludes 2 patches which must be installed in the following order: \n \n***If your site does not utilize the FDA Med Guide Auto \nPrinting software, you only need to install Vista patch PSS*1*257 \nand no further action on PSO*7*665 is necessary.*** \n \n**************************************************************************\n \nThe previous SharePoint address is hard-coded and stored in the Pharmacy \nSystem File (File #59.7) FDA MED GUIDE SERVER URL field (Field #100). \n \n \nThis patch will update the Pharmacy System File (File #59.7) FDA MED \nGUIDE SERVER URL field (Field #100) with the new secure VA Share URL.\nPost-init routine PSS257P will change the FDA MED GUIDE SERVER URL field \n \nfrom this: \n \n"https://vaww.vashare.domain.ext/sites/PBMNat/FDAMedGuides/" \nto this: \n \nfile://v12.domain.ext/v12/PBM/Workgroup/VistA_MedGuides/\n1. PSS*1*257 - Vista patch that updates the Pharmacy System File \n \n \nPatch PS0*7.0*665 (Automatic Printing) will be released at the same time \nas this patch, PSS*1*257\nInformation only patches contain instructions to retrieve the \nnecessary files and documentation to update the Java Application \nComponent software to make this URL work with the system. \n \nThis patch (PSS*1*257) only makes the file update and does not alter any \nVistA functionality. \n (File#59.7) FDA MED GUIDE SERVER URL field (Field 100) with the new\n secure CMOP SharePoint URL.\n \n2. PSO*7*665 - Information only patch that contains instructions to \n update the FDA Med Guide Automatic Printing Java Application \n\n
\nThis patch will resolve the following issues:\n-----------------------------\nN/A\n \n \nAdditional Information:\n-----------------------\nDefect Tracking System Ticket(s) & Overview:\nINC20326718\n \n \n \nProblem:\n--------\nIt was reported by the Sacramento VA Medical Center that the Edit \nOrderable Items [PSS EDIT ORDERABLE ITEMS] menu inappropriately jumps \nseveral prompts with use of an up carat "^" and a question mark "?". \n \n \nResolution:\n-----------\nThe following changes were made to address the issue:\n1. INC20326718 - Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] menu \n1) Fix the logic so it does not inappropriately jump several prompts with \nuse of an up carat "^" and a question mark "?". \n \n \nTechnical Resolution:\n---------------------\nThe following changes were made to address the issue:\n1) Routine PSSPOIMO was updated in the DIR tag to move the 4 indication \nfields (14, 13, 14.1, and 14.2) added with PSO*7*204 and PSO*7*242 to the \nDR string variable. This will resolve the issue of the indicator fields \ninappropriately jumps with use of an up carat "^" and a question mark \ndisplaying after the user enters an up carat "^" to quit out of the \noption. In addition, the logic was updated in the DIR tag to not skip \nprompts if a question mark is used for the help text.\n"?". It was reported that the issue started occurring after the \nindication fields were added (i.e. PSS*1*204).\n \n \nPatient Safety Issues (PSIs):\n\n
\nThe Computerized Patient Record System (CPRS) Graphical User Interface \n20170512: Complex Non-VA Med Orders\n \n \nFor a complete listing of patches included in this release, please refer \nto the CPRS GUI v32 Release Notes.\n(GUI) v32 is an enhancement release. This patch (PSS*1*187) is a part of \nthat enhancement release.\n \nThis patch provides the needed functionalities to support the following \nNSRs:\n \n20090509: Park a Prescription\n20100101: Indication on all Prescriptions and Medication Orders\n\n
\nThis patch will update the PPSN web service to a more secure protocol:\n"encrypt_only_tlsv12".\n\n
\nSee FORUM patch description.\n\n
\n This patch contains two enhancements:\n \n 1. In the Lookup into Dispense Drug File [PSS LOOK] option, we made\n modifications to routine PSSLOOK to correct a typo. Indicatior changed\n to Indicator.\n \n 2. In the Standard Schedule Edit [PSS SCHEDULE EDIT] option, we made\n modifications to routine PSSJEEU to set DLAYGO to the file number. This\n correction should allow users to look up and add new entries to the file.\n\n
\nComputerized Patient Record System (CPRS) v33 MOE will address NSR \n20090602: Addition of a Function to Enter Stop and Start Dates for \nInpatient Medications in CPRS.\n \nThis patch is the preparation patch for the installation of CPRS v33 MOE. \nIt gives pharmacy informatics the ability to define one-time \nadministration schedules that should be excluded from the Start/Stop \nfunctionality in CPRS. The exclusion schedules can be defined at system \nor division level.\n\n
\nSee FORUM for patch description details.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSS*1*254.\n\n
\n \n 1. It adds a new AOC cross-reference to the VA CLASSIFICATION field (#2)\n in the DRUG file (#50).\n \n 2. In the PHARMACY PATIENT file (#55), it corrects a typo in a screen\n placed on the DISPENSE DRUG field (#.01) from the DISPENSE DRUG\n multiple (#55.07). The code was modified to reference the PHARMACY\n ORDERABLE ITEM field (#2.1) instead of the PRIMARY DRUG field (#64).\n **NOTE** This patch requires the installation of Inpatient Medications\n V. 5.0. Facilities using Inpatient Medications V. 4.5 do\n not need to install this patch. Inpatient Medications V. 5.0\n patch PSJ*5.0*30 contains enhancements that utilize changes\n introduced in this patch.\n \n This patch addresses two issues. \n \n\n
\nThis patch distributes a common pharmacy locking routine (PSSLOCK). This\npatch supports the patient and single order locking changes in Inpatient\nMedications V. 5.0 and Outpatient Pharmacy V. 7.0. This patch will NOT\nchange locking functionality until patches OR*3.0*48, PSJ*5.0*29 and\nPSO*7.0*27 are installed.\n\n
\n This patch deletes the VENDOR sub-file (#50.535001) from the DRUG file\n ^PSDRUG(D0,535000,D1,0)\n ==>(#.01) VENDOR [1P] ^ (#1) PRIMARY VENDOR [2S] ^ (#2)\n ==>VENDOR'S PRICE PER ORDER UNIT [3N] ^ (#3) VENDOR'S\n ==>ORDER UNIT [4P] ^ (#4) DISPENSE UNITS PER ORDER UNIT\n ==> [5N] ^ (#5) COMPANY STOCK NUMBER [6F] ^ (#6) START\n ==>DATE [7D] ^ (#7) STOP DATE [8D] ^ (#8) DUMMY [9F] ^\n ==>(#9) PRICE PER DISPENSE UNIT [10N] ^ \n (#50) and the associated data. The VENDOR sub-file (#50.535001) does not\n \n provide national support of current activities related to the Pharmacy\n Data Management (PDM) application.\n \n \n The following multiple and associated data will be deleted with this\n patch:\n\n
\nThis build contains routines, options, files, fields, and templates\nfor the National Formulary Indicator enhancement patch.\n\n
\n This patch contains the following enhancements.\n DISPENSE UNITS PER ORDER UNIT field (#15) in the DRUG file (#50).\n \n 3. In reference to the MEDICATION INSTRUCTION file (#51), this patch:\n a. Replaces erroneous %D subscripts in the ^PS(51 data globals by\n restoring the MEDICATION INSTRUCTION file (#51) data dictionary.\n (ex. ^PS(51,%D,...).\n b. Re-indexes the "A" cross-references on the NAME field (#.01).\n c. Reinstalls full set of DDs related to the MEDICATION INSTRUCTION\n file (#51).\n \n \n 4. During the Computerize Patient Record System (CPRS) Order Entry\n process, the schedule input transform routine PSSGSO was not allowing\n schedules 5TIMES/DAY and 5X/DAY to pass as valid non-standard\n schedules. This patch contains modifications to routine PSSGS0\n to allow these schedules to be entered. \n 1. In the Standard Schedule Edit [PSS SCHEDULE EDIT] option, it\n increases the maximum value of the Frequency (IN MINUTES) field (#2)\n from 50000 to 129600 minutes in the ADMINISTRATION SCHEDULE file\n (#51.1).\n \n 2. In the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, it increases\n the decimal length from three to four digits when displaying the\n\n
\n Modifications were made to two options, CMOP Mark/Unmark (Single drug) \n 2. The program currently checks for a "C" - CONTROLLED SUBSTANCES - NON \n NARCOTIC in the DEA, SPECIAL HDLG field (#3) of the drug to be marked \n for transmission. Routine PSSMARK was modified to check for a "1" - \n SCHEDULE 1, or a "2" - SCHEDULE 2 in the DEA, SPECIAL HDLG field (#3).\n If these values are assigned to the selected drug, the option will\n not allow the user to mark the drug for CMOP transmission.\n \n 3. Routines PSSMARK and PSSDEE were modified to change the current \n message display, "It is a controlled substance" to "It is a schedule \n I or schedule II controlled substance" when a user attempts to mark\n [PSSXX MARK] and Drug Enter/Edit [PSS DRUG ENTER/EDIT]. These \n a controlled substance drug that does contains a "1" or "2" in the\n DEA SPECIAL HDLG field (#3). \n \n 4. The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option was modified to \n display a new message to reflect changes to the option. Routine \n PSSMARK was modified to check for a "1" or a "2" in the DEA,\n SPECIAL HDLG field (#3). If either of these values exist and the drug\n is already marked for CMOP transmission, the option shall display a\n message to the user indicating that the drug has been unmarked for \n CMOP transmission. \n modifications were required to enable drugs identified as a Schedule \n \n 5. The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option has been enhanced to \n provide a list of reasons why a drug can not be marked for CMOP \n transmission. \n III-V controlled substance to be marked for CMOP transmission. \n \n 1. Both options were modified to remove the screen that disallows a drug \n identified as a Schedule III-V controlled substance to be marked for \n CMOP transmission. \n \n\n
\n This patch removes the INPATIENT PRESCRIPTION PROFILE (#70) and the\n INPATIENT NARRATIVE (#21) fields from the PHARMACY PATIENT file (#55).\n Field #21 was added with the release of Pharmacy Data Management (PDM)\n and it is conflicting with reserved fields designated for Outpatient\n Pharmacy. This patch will delete all data and DDs related to these\n fields. \n\n
\nThe option, Synonym Enter/Edit [PSS SYNONYM], has been created to provide\neasy access to the update the synonym information for an entry in the local\nDRUG file (#50).\n\n
\n This patch contain two enhanancements:\n \n 1. It restores the DDs related to the "AND" cross-reference placed on the\n NATIONAL DRUG FILE ENTRY field (#20) in the DRUG file (#50).\n \n 2. It removes the CHEMOTHERAPY DRUG field (#202) and data from the DRUG\n File (#50).\n\n
\n This patch contains one resolution.\n Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, entries in the "AOC" MUMPS\n cross-reference only exist if the VA CLASSIFICATION field (#2) was\n entered after the PHARMACY ORDERABLE ITEM field (#2.1) in the DRUG file\n (#50).\n \n Solution: To make sure entries are properly set, this patch replaces the\n "AOC" MUMPS cross-reference with a new "AOC" compound index associated\n with the VA CLASSIFICATION field (#2) and PHARMACY ORDERABLE ITEM field\n (#2.1) in the DRUG file (#50). This solution will create an entry in the\n "AOC" compound index anytime both fields are modified regardless of the\n \n order.\n Problem: This patch resolves a problem related to a report created by the\n Patients on Specific Drug(s) [PSJ PDV] option associated with the\n Inpatient Medications V. 5.0 application. The Pharmacy Data Management\n (PDM) V. 1.0 application allows the Patients on Specific Drug(s) [PSJ\n PDV] option to access data stored in the "AOC" MUMPS cross-reference to\n produce a report on specific VA Classification. A facility reported that\n they noticed missing entries after generating the report. When using the\n\n
\n This patch contains several problems and resolutions related Pharmacy \n Resolution: The characteristics of the INACTIVE DATE field (#.04) in the\n PHARMACY ORDERABLE ITEM file (#50.7) was enhanced by classifying the\n field as an identifier. When the user performs a lookup on selectable\n orderable items, the option will display the inactive date associated\n with the orderable item.\n \n 2. Problem: In the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, the \n user noticed excessive looping after matching or tying an IV Additive or \n Solution to an orderable item. The user is asked repeatedly to enter \n another IV Additive or Solution. The user has to press return several \n Data Management V. 1.0. \n times to move to the next section in the option. \n \n Resolution: The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option was \n enhanced to allow the user to decide whether to enter another IV \n Additive or Solution before moving to the next section. \n \n 3. Problem: In the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, the \n user encountered an <UNDEFINED> UD^PSSDEE error when editing a drug that \n has been previously marked for CMOP. After the "Do you wish to UNmark \n this drug to transmit to CMOP? " prompt, the problem occurred as a result\n \n of killing the DA variable found at line tag UNMARK+1 in the PSSMARK \n routine. When the coding logic returned to the PSSDEE routine, the DA \n variable was detected as undefined since it was not reset to its \n original value. \n \n Resolution: In reference to the Drug Enter/Edit [PSS DRUG ENTER/EDIT] \n option, the PSSDEE routine was modified to store the value of the DA \n variable into an alternate variable so that the value of the DA variable \n can be retained for further use. \n \n 1. Problem: In the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, a \n 4. Problem: A minor enhancement was added to the Edit Orderable Items \n [PSS EDIT ORDERABLE ITEMS] option. When editing the CORRESPONDING IV \n ITEM field (#4) or CORRESPONDING UD ITEM field (#3) in the PHARMACY \n ORDERABLE ITEM file (#50.7), the default prompt only showed the orderable\n item name and did not include any reference to the DOSAGE FORM field \n (#.02) in the PHARMACY ORDERABLE ITEM file (#50.7). The selection \n process was confusing if there were multiple orderable items with the \n same name with different dosage forms. \n \n Resolution: To alleviate confusion, the Edit Orderable Items [PSS EDIT \n problem was discovered with identifying an inactive orderable item \n ORDERABLE ITEMS] option was enhanced to display a message to the user \n prior to the prompt. The message will indicate both the orderable item \n name and dosage form information. \n \n 5. Problem: In the Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] \n option, the user noticed a problem with modifying and storing information\n related to the orderable item. The problem was related to an outdated \n global reference to a reconstructed National Drug File (NDF) file within \n the input transform placed on the PHARMACY ORDERABLE ITEM field (#2.1) in\n the DRUG file (#50). \n before it is matched or tied to a dispense drug. Users find it difficult\n \n Resolution: To resolve this problem, the input transform associated with \n the PHARMACY ORDERABLE ITEM field (#2.1) was modified by replacing the \n old NDF global reference with a NDF Application Programming Interfaces \n (API) call to retrieve the dosage form information from the proper file.\n \n \n 6. Problem: The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option failed to \n notify the user when a dispense drug is matched or tied to an inactive \n orderable item. The user would like to see a warning message before s/he \n to select an active orderable item since the inactive date is not \n is asked, "Do you want to match to a different Orderable Item? NO//." \n \n Resolution: To resolve this problem, the Drug Enter/Edit [PSS DRUG \n ENTER/EDIT] option was enhanced to warn the user when a dispense drug is \n matched or tied to an inactive orderable item and provide the name of the\n option where the user can make the proper changes. \n displayed. \n \n\n
\nThis patch provides the functionality needed to prepare for the Pharmacy\nThe Implementation Guide and Installation Guide for this patch can be\nobtained on the VISTA Pharmacy Data Management web page. The address is\nhttp://vista.domain.ext/pdm.\n \n \nThe Implementation Guide and Installation Guide are also available on\nthe ANONYMOUS.SOFTWARE directory at one of the following Office of\nInformation (OI) Field Offices. The file names are PDM1P34_IG.PDF for\nthe Installation Guide, and PDM1P34_IMPG.PDF for the Implementation Guide.\n \nOrdering Enhancements project. This project will involve patches by four\n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n Albany 152.127.1.5 anonymous.software\n Hines 152.129.1.110 anonymous.software\n Salt Lake City 152.131.2.1 anonymous.software \npackages; Computerized Patient Record System (CPRS), Inpatient\nMedications, Outpatient Pharmacy, and Pharmacy Data Management. This\nPharmacy Data Management patch, PSS*1*34, provides the tools necessary to\nset up the Pharmacy files in advance of the Pharmacy Ordering Enhancements\nproject.\n \n \n\n
\n1. Several sites have reported a problem when trying to document the\nPARAMETERS file (#53.45) and the DISPENSE DRUG sub-file (#53.11) of the\nNON-VERIFIED ORDERS file (#53.1). The problem with the input transform\nalso exists in the PHARMACY PATIENT file (#55), UNIT DOSE sub-file\n(#55.06), DISPENSE DRUG sub-file (#55.07), UNITS PER DOSE field (#.02).\nPatch PSJ*5*43 corrects the problem in the INPATIENT USER PARAMETERS file\n(#53.45) and the NON-VERIFIED ORDERS file (#53.1). This patch corrects\nthis problem in the PHARMACY PATIENT file (#55). NOIS#s NOL-0300-71473,\nHOU-0300-71626, and CMO-0300-43187.\n \n2. Site reported a problem where they entered an infusion rate of @x and\ndispensing of medications through the Bar Code Med Admin (BCMA)\nx labels didn't print. Only 1 label printed. The issue is that only one\nadministration time was specified. The administration time overrides the\nentry of @x when determining how many labels will print. This patch\nmodifies the field descriptions and the documentation for INFUSION RATE in\norder to clarify which field determines the number of labels. Modified\nUSUAL INFUSION RATE field (#2) in the IV ADDITIVES file (#52.6), QUICK\nCODE sub-file (#52.61) and the INFUSION RATE field (#.08) in the PHARMACY\nPATIENT file (#55), IV sub-file (#55.01).\n \n3. The vendor for the ATC systems called to say they now have two\nsoftware. The sites have reported receiving the following error:\nmachines with canister numbers higher than currently allowed. This patch\nmodifies the ATC CANISTER field (#1) of the DRUG file (#50), ATC CANISTER\nsub-file (#50.0212) to increase the canister limit from 500 to 800 and\nremove the references to Baxter since the company name has changed. This\npatch also modified the following entries to remove the references to the\ncompany name of Baxter: DRUG file (#50), ATC CANISTER sub-file (#212),\nfield description, DRUG file (#50), ATC MNEMONIC field (#212.2), DRUG file\n(#50), ATC CANISTER sub-file (#212), WARD GROUP FOR ATC CANISTER field\n(.01).\n \n \n4. An inconsistency was discovered between the Computerized \nPatient Record System (CPRS) and the Inpatient Medications validation of\nProvider Comments/Special Instructions. CPRS allows entry of text with no\nspaces while Inpatient Medications requires spaces. This patch corrects\nthis problem by modifying the validation of Special Instructions to allow\nan entry with no spaces.\n \n5. The INPATIENT PRESCRIPTION PROFILE field (#70) in the PHARMACY PATIENT\nfile (#55) is no longer used. This patch deletes this field.\n1. Data Validation Error: 701: The value 'AC' for field DOSES ORDERED in\nDISPENSE DRUG SUB-FIELD in file BCMA MEDICATION LOG is not valid.\n \nThe problem was with the input transform on the UNITS PER DOSE field\n(#.02) in the DISPENSE DRUG sub-file (#53.4502) of the INPATIENT USER\n\n
\nSee Patch PSS*1*33 in the National Patch Module for description of the\nBuild.\n\n
\nSee patch PSS*1*39 in the National Patch Module for description of the\nbuild.\n\n
\nThis patch adds a new field, NDF UPDATE (#5) to the ACTIVITY LOG\nmultiple (#214) in the DRUG file (#50).\n\n
\nThis patch exports two new options that can be used to assist sites in the\n \nOrderable Item/Dosages Report [PSS ORDERABLE ITEM DOSAGES] option:\nThis option prints a report that displays Inpatient and Outpatient\nDosages for Pharmacy Orderable Items. These are the dosages that will\ndisplay for selection through Computerized Patient Record System (CPRS)\nwhen an Orderable Item is selected for a medication order. The report is\nsorted by Pharmacy Orderable Item. Along with each dosage that is\ndisplayed on the report, the name of the Drug entry from the DRUG file\n(#50) that provides the dosage will also display. Not every dosage from\nthe DRUG file (#50) will display on this report. For example, if there are\npharmacy set-up work for the Pharmacy Ordering Enhancements (POE) project.\nduplicate Possible Dosages for a Pharmacy Orderable Item, and there are\ndifferent Dispense Units per Dose, then only the Possible Dosage with the\nlowest Dispense Units per Dose will display on the report. If there are\nPossible Dosages and Local Possible Dosages for drugs tied to the Pharmacy\nOrderable Item, then only the Possible Dosages will display on the report.\nIn summary, this report will screen out Possible Dosages and Local\nPossible Dosage when appropriate, so only the dosages selectable through\nCPRS will display on this report.\n \n \nThe two options are named:\nPatient Instructions Report [PSS INSTRUCTIONS/ITEMS REPORT] option:\nDue to numerous requests, a change has been made to the PATIENT\nINSTRUCTIONS field (#7) of the PHARMACY ORDERABLE ITEM file (#50.7). Data\nin this field will now be checked for possible expansions, by running each\nword through the MEDICATION INSTRUCTION file (#51), similar to how the\nSIG has been traditionally expanded in the Outpatient Pharmacy\napplication. The data will still be stored in condensed form, but will\nprint in expanded form when used by the various applications in POE. This\nincludes all reports, displays in CPRS, displays in Outpatient Pharmacy,\nand when the SIG prints on the Outpatient Pharmacy labels. It is important\n \nthat any Patient Instructions entered prior the installation of this patch\nbe reviewed, to ensure that if a word didn't expand when originally\nentered and now does expand, that the expansion is appropriate. The\nPatient Instructions Report option can be used to review any Patient\nInstructions that are entered in the PHARMACY ORDERABLE ITEM file (#50.7).\n \nIn addition to the new Patient Instructions Report, this patch makes a\nchange to the PATIENT INSTRUCTIONS field (#7) of the PHARMACY ORDERABLE\nITEM file (#50.7). When data is entered into this field, the expanded\nversion of the data will now echo back to the user.\n Orderable Item/Dosages Report [PSS ORDERABLE ITEM DOSAGES]\n \n \n \nChange pages have been issued for the Pharmacy Ordering Enhancements\nPharmacy Data Management Pre-Release Implementation Guide, initially\ndistributed with patch PSS*1*34. These change pages can be obtained on the\nVISTA Pharmacy Data Management web page at\nhttp://vista.domain.ext/PDM/pdm_documentation.htm .\n \nThe Pharmacy Ordering Enhancements Pharmacy Data Management Pre-Release\n Patient Instructions Report [PSS INSTRUCTIONS/ITEMS REPORT]\nImplementation Guide is also available on the ANONYMOUS.SOFTWARE directory\nat one of the following Office of Information (OI) Field Offices. The\nImplementation Guide's file name is PDM1P34_IMPG.PDF.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n Albany 152.127.1.5 anonymous.software\n Hines 152.129.1.110 anonymous.software\n Salt Lake City 152.131.2.1 anonymous.software \n \nThese options will be accessible under the Orderable Item Management [PSS\nORDERABLE ITEM MANAGEMENT] menu option.\n\n
\nThis patch contains an update to the ^DD global for the field TO\nSERVICE (1) of the D/C ON SERVICE TRANSFER (#23) multiple in the\nPHARMACY SYSTEM file (#59.7). This field had a typographical error in the\nexecutable help, resulting in an error.\n\n
\nThis patch provides the functionality needed to fix NOIS PTH-0301-21164.\nThis will fix the problem of bad interactions presently on your system\nas well.\n\n
\nWhen using the PRimary Solution File (IV) [PSSJI SOLN] option, and\nthe ADditives File [PSSJI DRUG] option, it was reported that at the end\nof the dialogue, the system is not responding correctly to the\n"YES" answer when prompted "Would you like to enter another IV Additive\nor Solution? NO//". This patch fixes this problem.\n\n
\nPhase 1 of the Pharmacy Ordering Enhancements (POE) project introduced\nthat entry to have Possible Dosages is that the combination of Dosage Form\nand Unit from the National Drug File match must be marked as convertible\nin the DOSAGE FORM (#50.606) file. This data in the DOSAGE FORM (#50.606)\nfile was populated at the Field Office and exported with patch PSS*1*34.\nThis data should only be edited and exported from the Field Office,\nso this patch is exporting the data again, and will put restrictions on\nthose particular fields. This patch will also put restrictions on fields\nin the DRUG (#50) file, to prevent invalid Possible Dosages from being\ncreated. In addition, this patch will look for any invalid Possible\nDosages in the DRUG (#50) file, and either delete that Possible Dosage, or\nfunctionality to create Possible Dosages and Local Possible Dosages in the\nremove the invalid package reference from that Possible Dosage. A mail\nmessage will also be generated that lists any drugs that were affected by\nthis install. This message will be sent to the person installing the\npatch, and all PSNMGR key holders. Reasons that a Possible Dosage would\nhave to be deleted are:\n \n1) The drug is not matched to the National Drug File.\n2) The match to the National Drug File does not produce a valid Unit or\n Dosage Form.\n3) The Unit from the National Drug File match does not match the Unit in\nDRUG (#50) file. This work is being done in preparation of phase 2 of the\n the DRUG (#50) file.\n4) The combination of Dosage Form/Unit from the National Drug File match\n is not marked as convertible in the DOSAGE FORM (#50.606) file.\nPOE project, when these Possible Dosages and Local Possible Dosages will\nbe selectable during the Medication Ordering process in Outpatient\nPharmacy, Inpatient Medications, and Computerized Patient Record System\n(CPRS).\n \nOne of the criteria that an entry in the DRUG (#50) file must meet for\n\n
\nThe Pharmacy Ordering Enhancements (POE) project provides enhancements\nInpatient Medications and Outpatient Pharmacy applications. This project\ndirectly supports Computerized Patient Record System (CPRS), which is a\nkey component of Veterans Health Administration's (VHA) plan to expand\nsupport for clinical operations. Additionally, order checks will be\nprovided for medication orders for which a dispense drug has not been\nselected during the CPRS order entry process. It is also intended as a way\nto help meet the goal outlined in Objective 8, Action 1 in the\nPrescription for Change, which outlines the need to coordinate\nnational/Veterans Integrated Service Network (VISN) formularies and share\ndrug treatment guideline information. This project will promote system-\nto Pharmacy Data Management (PDM) V. 1.0, Inpatient Medications\nwide sharing of drug reviews and treatment guidelines thereby enhancing\npatient safety.\n \nThis project consists of four patches that work together to accomplish\nthese goals listed in order of install:\n \n PSO*7*46\n OR*3*94\n PSS*1*38\n PSJ*5*50\nV. 5.0, Outpatient Pharmacy V. 7.0, and Order Entry/Results Reporting\n \n \nInstallation Instructions and Documentation Retrieval:\n======================================================\n \nThe Installation Guide, Release Notes, revised Pharmacy Data Management\n(PDM) Technical Manual, and Pharmacy Data Management (PDM) User Manual are\non the ANONYMOUS.SOFTWARE directory at one of the following Office of\nInformation (OI) Field Offices.\n \n(OE/RR) V. 3.0 medication ordering dialogues to eliminate redundant entry\nSites may retrieve documentation in one of the following ways:\n \n(1) The preferred method is to FTP the files from\ndownload.vista.domain.ext, which will transmit the files from the first\navailable FTP server.\n \n(2) Sites may also elect to retrieve documentation directly from a\nspecific server as follows:\n \nAlbany ftp.fo-albany.domain.ext\nof drug information during medication order entry, provide a more\nHines ftp.fo-hines.domain.ext\nSalt Lake City ftp.fo-slc.domain.ext\n \n The software distribution includes:\n \n FILE NAMES DESCRIPTION\n \n CPRS_POE_10.KID CPRS/Pharmacy Ordering Enhancements 1.0 Master Build\n CPRS_POE_1_1_IG.PDF Installation Guide\n CPRS_POE_1_0_RN.PDF Release Notes\nconsistent medication order entry process, provide expanded order\n PDM_1_0_TM.PDF Technical Manual/Security Guide\n PDM_1_0_UM.PDF User Manual \n \n(3) Documentation can also be retrieved from VISTA Document Library (VDL)\non the VA Intranet at the following address, http:/vista.domain.ext/vdl.\nchecking, display documented drug formulary statuses and corresponding\nrestriction/guidelines to the provider and pharmacist at the time of order\nentry, and improve the process of medication order transfer between\n\n
\n1) A problem has been reported concerning certain dosage selections in\n - The Review Dosages Report [PSS DOSAGE REVIEW REPORT] option.\n - The Orderable Item/Dosages Report [PSS ORDERABLE ITEM DOSAGES] option.\n - Display the leading zero when editing Dosages through either the Drug\n Enter/Edit [PSS DRUG ENTER/EDIT] option or the Enter/Edit Dosages [PSS\n EDIT DOSAGES] option.\n - The display of Dispense Units per Dose has also been changed in the\n Pharmacy Data Management options to display a leading zero when the\n number begins with a decimal point.\n \n2) This patch also contains a change that will affect Computerized Patient\n Inpatient Medications V. 5.0 and Computerized Patient Record System\n Record System (CPRS). The Pharmacy Data Management package returns\n information to CPRS regarding the DEA Special Handling indication of a\n Pharmacy Orderable item, which is based on the DEA Special Handling\n information from the Dispense Drugs tied to the Pharmacy Orderable\n Item. Currently, if the DEA Special Handling code contains a "1", or\n contains a "2", or contains both the "3" and the "A", this indicates to\n CPRS that a wet signature is required. If this first condition is not\n met, but the DEA Special Handling code contains a "4", or contains a\n "5", or contains a "3" and not the "A", then a wet signature is not\n required, but it does indicate that it is a controlled substance. This\n (CPRS) V. 3.0. The problem is in the Dosages that contain a "/", and\n patch changes that logic. With the installation of this patch, if the\n DEA Special Handling code contains a "1", or contains a "2", this\n indicates to CPRS that a wet signature is required. If this first\n condition is not met, but the DEA Special Handling code contains a "3",\n or contains a "4", or contains a "5", then a wet signature is not\n required, but it does indicate that it is a controlled substance.\n when the second part of that Dosage begins with a decimal point. A\n leading zero was not being added to that second part of the Dosage. For\n example, a Dosage that is currently being displayed as 0.25MG/.5ML will\n be displayed as 0.25MG/0.5ML.\n \n This change will affect the following:\n\n
\n1. A site reported a problem where a one-time order could not be\nsystem parameter is not defined, the system will use the continuous order\nparameters to determine the stop date, rather than the start and stop date\nbeing equal. Then, when BCMA marks the medication as 'Given', Inpatient\nMedications will expire the order. NOIS# BUT-0501-20609\n \n2. With the release of the Pharmacy Ordering Enhancements patches two\nspaces were allowed in the schedule field. In testing, it was discovered\nthat a user could enter the two spaces at the end of the schedule and it\nwas accepted by the software. The software was not intended to work this\nway. Upon installation of this patch, the trailing spaces will be\ndiscontinued by the provider because it was expired due to the start and\nstripped off the text the user enters at the schedule prompt.\nstop date being the same. However, the medication still displayed in Bar\nCode Medication Administration (BCMA) V. 1.0 because of the 12-hour rule\nfor displaying one-time orders on the Virtual Due List. This patch\ncorrects this problem by changing the way the stop date for one-time\norders is calculated. There will be a ward parameter, system parameter and\nthe standard calculation. The hierarchy will be to check the one-time ward\nparameter first, if not defined, check the system parameter. If the\n\n
\n1. A problem has been reported in the Drug Enter/Edit [PSS DRUG\n2. A problem was reported in the Dispense Drug/Orderable Item Maintenance\n [PSS MAINTAIN ORDERABLE ITEMS] option. If a drug is not marked for\n Outpatient (O), Unit Dose (U), or IV (I) in the APPLICATION PACKAGES'\n USE (#63) field of the DRUG (#50) file, then it is not selectable in\n this option. These drugs will now be selectable. They will still not be\n selectable for ordering, but now they can be matched to a Pharmacy\n Orderable Item.\n ENTER/EDIT] option. If a drug is edited that is not matched to Pharmacy\n Orderable Item, and the drug is matched to a Pharmacy Orderable Item in\n this option, then the Possible Dosages are reset after completion of\n the match. Possible Dosages should only be reset if the drug is matched\n to a Pharmacy Orderable Item when the option is first accessed, and the\n drug is rematched to a different Pharmacy Orderable Item with a\n different Dosage Form.\n \n\n
\nA problem can occur in Computerized Patient Record System (CPRS) when \n \nIn this example, the first and third Dosages come from different Dispense \nDrugs, but since each of these drugs has a top level Strength and Unit \nfrom the National Drug File match, the Strength and Unit are displayed \ninstead of the Dispense Drug name, which makes the selection ambiguous. \nIn addition, no matter which of these Local Possible Dosages is selected, \nthe first or the third, the same Dispense Drug is assigned to the order.\n \nTo fix this problem, this patch will make a change to the way Local \nPossible Dosages are returned to CPRS for display and selection. As in \nduplicate Local Possible Dosages are displayed for selection in the \nthis case, if there are duplicate Local Possible Dosages in the list, and \none of the duplicate sets also has a duplicate Strength and Unit for\ndifferent Dispense Drugs, then the Strength will not be returned to CPRS\nalong with the Local Possible Dosages. Then instead of CPRS displaying the\nStrength and Unit, CPRS will display the Dispense Drug name, which should\ndifferentiate the selection display, as long as the Dispense Drug names\nare different. This will also resolve the selection problem of the same\nDispense Drug being assigned to the order, regardless of the selection.\nmedication order entry process, and these duplicate Local Possible \nDosages have a duplicate Strength and Unit as part of the display. For \nexample, a dosage selection display such as:\n \nSMALL AMOUNT OF 0.1%\nSMALL AMOUNT OF 0.025%\nSMALL AMOUNT OF 0.1%\n\n
\n1. It was reported that although some Dosage Form entries are inactivated,\n times it picks a wrong drug. This problem is due to the existence of\n an old cross-references ("IV", "IV1", and "IV2") in the DRUG file\n (#50). This patch fixes this problem.\n they are still showing up in the following options:\n -Dosage Form File Enter/Edit [PSS DOSAGE FORM EDIT].\n -Noun/Dosage Form Report [PSS DOSE FORM/NOUN REPORT].\n This patch insures that the inactivated entries will not be displayed\n in those options.\n \n2. When using the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, it was\n reported that if the drug is selected using the synonym entry, some-\n\n\n1. When using the Drug Enter/edit [PSS DRUG ENTER/EDIT] option and the\n populate from the STRENGTH field (#2) of the VA PRODUCT file (#50.68).\n \n - The software will populate the Unit of the drug from the UNIT field\n (#902) of the DRUG file (#50) if it is defined, otherwise it will\n populate from the UNIT field (#3) of the VA PRODUCT file (#50.68).\n \n - If both the Strength and the Unit fields are not populated then the\n software will display null values.\n \n2. When creating new dosages for a drug, the PACKAGE field (#3) in\n Enter/Edit dosages [PSS EDIT DOSAGES] option, currently the software\n the DOSAGES multiple (#903) of the DRUG file (#50) is case-\n sensitive (allows only capital letters). This patch modifies the Input\n Transform of the PACKAGE field to accept lowercase letters as well.\n \n3. When using the Dosage Form File Enter/Edit [PSS DOSAGE FORM EDIT]\n option, it was reported that the MED ROUTE FOR DOSAGE FORM field (#.01)\n in the MED ROUTE FOR DOSAGE FORM multiple (#50.6061) of the DOSAGE FORM\n file (#50.606) can be assigned a Medication Route entry with a PACKAGE\n USE field (#3) of "FOR NATIONAL DRUG FILE ONLY" from the MEDICATION\n ROUTES file (#51.2). This patch prevents such Medication Route entries\n displays the Strength and the Unit of a drug only if it finds Possible\n from being assigned to the MED ROUTE FOR DOSAGE FORM multiple.\n Dosages assigned to that drug. This patch modifies routines PSSDOS and\n PSSDOSER to display the Strength, and the Unit of a drug that also has\n Local Possible Dosages assigned for the following conditions:\n \n - The software will populate the Strength of the drug from the STRENGTH\n field (#901) of the DRUG file (#50) if it is defined, otherwise it will\n\n
\nThis patch corrects a problem when using the option Lookup into Dispense\nDrug File [PSS LOOK]. Drugs with an application defined for use were\ninadvertently displayed as "none" under some circumstances.\n \nThis patch also corrects a problem with the display of synonyms under\ncertain circumstances.\n\n
\nAs a part of the Pharmacy Benefits Management (PBM) Extract enhancement\npackages affected since only one installation is necessary. The patches,\nin order of install, are:\n \n PSS*1*52 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*68 INPATIENT MEDICATIONS V. 5.0\n PSO*7*95 OUTPATIENT PHARMACY V. 7.0\n \nUpon completion of the installation of these three patches, the master\nbuild will start a routine that will build the two new fields from\nhistorical data in the PHARMACY PATIENT file (#55). When the build is\nproject, two new fields were added to the PHARMACY PATIENT file (#55).\ncomplete, the user who initiated the install and the members of the\nPSU PBM mail group will receive a message with a subject of BUILD OF FIRST\nPHARMACY SERVICE INFO COMPLETE.\nThey are FIRST SERVICE DATE (#.07) and ACTUAL/HISTORICAL FLAG (#.08).\nWith the addition of these two fields, Inpatient Medications V. 5.0 and\nOutpatient Pharmacy V. 7.0 have been modified to set this information\nwhen the first order for a patient becomes active.\n \nThis project consists of three patches combined in a master build.\nInstallation of this master build should be coordinated among the three\n\n
\n1. The Bar Code Medication Administration (BCMA) V. 2.0 release provides \nMed Order button in BCMA V. 2.0.\n \nThis project consists of two patches and a new version of BCMA that work\ntogether to accomplish these goals listed in order of install:\n \n PSS*1*46 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*58 INPATIENT MEDICATIONS V. 5.0\n BAR CODE MED ADMIN 2.0\nenhancements to Pharmacy Data Management (PDM) V. 1.0, and Inpatient \nMedications V. 5.0. The BCMA V. 2.0 release expands and improves the\nprocess of medication administration, especially in the area of IV\nmedications.\n \nIn support of this, Inpatient Medications V. 5.0 and PDM V. 1.0 have added\nthe ability to print barcode identifiers on IV labels, IV order \nverification and the ability to receive done priority orders via the CPRS \n\n
\n1. A site reported a problem with quitting the Drug Enter/Edit [PSS DRUG\nENTER/EDIT] option using the "^". When the user quits with an "^" at \nthe prompt "Match to another Orderable Item with same Dosage Form?" this\nwill not properly clean up. This has resulted in improper prompting when\nusing the Edit Data for a Patient in the Clozapine Program [PSO EDIT]\noption. This patch fixes this problem. NOIS PUG-0202-52260\n \n2. A site reported a problem with the display of the cost information for \na drug. This patch corrects this problem. NOIS NYH-1001-12352\n\n
\n A new field is being added to the IV multiple of the Pharmacy Patient \nfile (#55) to support a change in functionality for auto-reinstating\nInpatient Medications orders.\n Inpatient Medications orders which were on hold at the time a patient\nmovement occurred which caused them to be auto-discontinued were not\nreturned to on hold if the movement was deleted and the orders were\nauto-reinstated. This patch corrects this problem. NOIS: AAA-0802-N1994.\n\n
\n1. Currently Inpatient Medications V. 5.0 recognizes the following\nMedication Administration (BCMA) V. 1.0 correctly. The problem was that \nthe frequency for the medication administration was being calculated \ninappropriately. This patch corrects this problem. NOIS: HUN-0502-22756\n \n3. A site reported a problem quick orders not displaying entries from the\nSCHEDULE ADMINISTRATION file (#51.1) correctly when attempting to define \noutpatient quick orders. This patch corrects this problem. \nNOIS: DUB-1201-30587\nschedules as One Time schedules: NOW, ONCE, STAT, ONE TIME, 1 TIME, 1TIME,\n1-TIME , ONE-TIME, ONETIME\n \nThis patch will update the routines that Pharmacy Data Management (PDM)\nV. 1.0 uses to validate schedules for Computerized Patient Record System\n(CPRS) V. 1.0 to be consistent with Inpatient Medications V. 5.0.\n \n2. A site reported a problem with an order not appearing in Bar Code \n\n
\nHUI/VHA CIO SD&D PHARMACY DATA INTERCHANGE\nprotocol SEND DRUG UPDATE MESSAGE [PSS HUI DRUG UPDATE] as a subscriber.\nTo activate the sending of these HL7 messages the text from DISABLE field\nmust be deleted and at least one receiving protocol added as a subscriber. \n \nFor those sites who ARE NOT part of the Hui/VHA CIO SD&D Pharmacy Data \nInterchange project, NO FURTHER ACTION is necessary after installation of\nthe patch. \n \n \n2. When performing drug lookups, two issues were identified. First, the was\n \nnot aware of which item was being matched. For example, was the match for\nthe GENERIC NAME of the drug or was it the SYNONYM. The second issue had to\ndo with the search matching to the NATIONAL DRUG CLASS NAME first, before\nchecking for a GENERIC NAME. \n \nThis patch makes two changes to the drug lookup. First, the search will\ndisplay the item being searched on. Second, if a match is found on an item,\nbut the user doesn't select one of the matches displayed, the search will\ncontinue through all other items.\n1. This patch is in support of the Hui/VHA CIO SD&D Pharmacy Data\nInterchange project. The project provides a method for the one-way\nelectronic transfer of prescription orders from an external system to VistA\n \nThe purpose of this patch is to provide an HL7 notification of the addition\nof new drugs and drug updates to the DRUG file (#50). To receive this \nnotification, the receiving protocol must be attached to the sending\n\n
\n \none or all entries.\n \nThe Drug Text Enter/Edit [PSS DRUG TEXT ENTER/EDIT] option was changed to\nenhance the text displayed when editing or inactivating an entry. The new\ntext identifies the specific option that can be used to display linked\nitems.\n \nThe following cross-references were created for use in generating a list\nof DRUG file (#50) entries and PHARMACY ORDERABLE ITEM file (#50.7)\nentries associated with a DRUG TEXT file (#51.7) entry and for generating\nThe Pharmacy Data Management Drug Text Enter/Edit [PSS DRUG TEXT\nthe report in the Drug Text File Report [PSS DRUG TEXT FILE REPORT]\noption:\n 1. A full file cross-reference on the DRUG TEXT ENTRY field\n(#50.037) in the DRUG file (#50).\n 2. A full file cross-reference on the OI-DRUG TEXT ENTRY field (#50.76)\nof the PHARMACY ORDERABLE ITEM file (#50.7).\n \nNote: The population of the new 'DTXT' cross reference is done in a\npost-install background job. When this job completes, it will send a\nMailMan message to the installer of the patch and holders of the\nENTER/EDIT] option is being enhanced and a new Drug Text File Report [PSS\nPSNMGR key. The new Drug Text File Report [PSS DRUG TEXT FILE REPORT]\noption should then be run for all drug text entries in the DRUG TEXT\nfile (#51.7) to verify that the correct drug text is associated with the\ncorrect entries in the PHARMACY ORDERABLE ITEM file (#50.7) and the DRUG\nfile (#50). A listing of the original drug text file entries distributed\nwith Patch PSS*1*29 is provided in the Pharmacy Data Management user\nmanual.\n \nThere will be updates to the Pharmacy Data Management V.1.0 User and\nTechnical manuals for this patch.\nDRUG TEXT FILE REPORT] option is being added.\n \n \nThe Drug Text File Report [PSS DRUG TEXT FILE REPORT] option displays the\ndrug text name, synonyms, drug text, inactive date if inactive, and lists\nall drug and orderable items linked to it. This report can be printed for\n\n
\n1. When a user cannot access a patient order due to the order being locked\nAdd field# 148 FLAGGED to the IV multiple of the PHARMACY PATIENT file \n(#55).\nAdd field# 124 FLAGGED to the UNIT DOSE multiple of the PHARMACY PATIENT\nfile (#55).\n \nChanged field# .02 TYPE OF ACTIVITY, added two new codes to the existing \nset of codes. 'G' FOR FLAGGED; 'UG' FOR UNFLAGGED. This is in the \nACTIVITY LOG multiple (#55.04).\nChanged field# .04 REASON FOR ACTIVITY, increased the field size from 75 \nto 102. This is also in the ACTIVITY LOG multiple (#55.04).\nby another user, a warning message is displayed and hung for a couple \nsecond before scrolling off the screen. This patch will pause and \nrequire a return from the user before continuing with the process.\n \n2. The following DD changes are being made in order to support requested \nchanges to Inpatient Medications to allow flagging functionality. E3R\n#11177 and #12382\n \n\n
\n1. This patch, in conjunction with CPRS patches OR*3.0*149 and OR*3.0*158,\n problem for orders entered through CPRS GUI, and patch OR*3.0*158 will\n fix this problem for orders entered through CPRS ListMan. No problems\n will occur if the PSS*1.0*66 patch is installed without either one or\n both of the CPRS patches, but the functionality will not work properly\n until all patches are installed. NOIS JAC-0602-72390\n \n2. A site reported a problem with entering the cost information for drugs\n with cost like NNNNN.NNN per order unit. Currently, the PRICE PER ORDER\n UNIT field (#13) in the DRUG file (#50) only allows 4 digits before the\n decimal point. This patch modifies the Data Dictionary of this field to\n fixes a problem that can occur when entering an order for an outpatient\n accommodate 5 digits. NOIS POR-0902-50198\n \n3. A minor change has been made to the Pharmacy Data Management (PDM) \n Application Program Interface (API) to allow other pharmacy packages to\n make use of it, whenever they update the DRUG file (#50) so that PDM \n possibly generates an HL7 outgoing drug message.\n \n4. A site reported a problem with the display of the cost information\n for drugs with local possible dosages. This patch corrects this\n problem. NOIS REN-0902-60126\n in Computerized Patient Record System (CPRS) using the IV Fluids order\n dialogue. The DEA Special Handling check does not always function when\n entering those orders. So it is possible for a Provider without a DEA#\n or a VA# to enter an order through this dialogue for an Orderable Item,\n when that order should not be allowed to be placed. When this patch and\n both CPRS patches OR*3.0*149 and OR*3.0*158 are installed, this\n functionality will work properly. Patch OR*3.0*149 will fix this\n\n
\nAs part of the Outpatient Pharmacy V. 7.0 project to add Patient \nMedication Information (PMI) print to labels, a new field must be added to\nthe PHARMACY SYSTEM file (#59.7). The new field, PMIS SECTION DELETE (#15)\nwill allow the Pharmacy Benefits Manager to mark certain PMI sections to\ndelete them from printing on labels. This patch adds this new field and\npopulates it appropriately.\n\n
\n **NOTE** THIS PATCH SHOULD BE LOADED BEFORE PATCH OR*2.5*49.\n \n This procedure call has been changed to return an additional data\n element. The Default Schedule name for the Orderable Item is now\n returned in ^TMP("PSJSCH",$J). ^TMP("PSJSCH",$J)= DEFAULT SCHEDULE\n NAME.\n \n Problem #2: This patch resolves a problem related to the Drug\n Enter/Edit [PSS DRUG ENTER/EDIT] option. In routine PSSDEE,\n modifications were made to allow the user to enter a new drug.\n \n The PSS*1*5 patch resolves two problems with the Pharmacy Data\n Management package. They are listed below.\n \n Problem #1: This patch contains modifications to routine PSSJORDF.\n The procedure call START^PSSJORDF(PSJORD) is called by Consolidated\n Patient Record System (CPRS) and passes the Orderable Item internal\n entry number.\n\n\nThis patch provides new functionality that allows the Veteran Affairs\nThe other language translations are entered by using the new option OTHER\nLANGUAGE TRANSLATION SETUP [PSS OTHER LANGUAGE SETUP]. This new option is\nnot linked to any menu, but must be assigned to the person(s) responsible\nfor maintaining this functionality. \n \nThe following options must be used to enter the remaining language\ntranslations data: \n DRUG ENTER/EDIT [PSS DRUG ENTER/EDIT] \n DOSAGES ...[PSS DOSAGES MANAGEMENT] \n DOSAGE FORM FILE ENTER/EDIT [PSS DOSAGE FORM EDIT] \nMedical Centers to print a patient's prescription bottle label in another\n MEDICATION INSTRUCTION FILE ADD/EDIT [PSSJU MI] \n MEDICATION ROUTE FILE ENTER/EDIT [PSS MEDICATION ROUTES EDIT] \n ORDERABLE ITEM MANAGEMENT ... [PSS ORDERABLE ITEM MANAGEMENT] \n EDIT ORDERABLE ITEMS [PSS EDIT ORDERABLE ITEMS] \n STANDARD SCHEDULE EDIT [PSS SCHEDULE EDIT]\nlanguage. This functionality is accomplished by identifying which patients\nhas another language preference. To identify patients as having another\nlanguage preference use the option UPDATE PATIENT RECORD [PSO PAT]\nand the protocol action PATIENT RECORD UPDATE [PSO PATIENT RECORD\nUPDATE] and enter Yes in the new field OTHER LANGUAGE PREFERENCE field\n(#106) in the PHARMACY PATIENT file (#55). \n \n\n
\nPSS*1*68 and OR*3*176 are the first of a total of 6 patches that will \nVeterans Affairs (VA). These types of medications are commonly referred\nto as "Non-VA Meds."\n \nBelow is a list of functionalities that will be available at your site\nonce all 6 patches are installed: \n \n 1. Add common herbal and OTC products to the DRUG File and mark them \n as Non-VA Med. \n 2. Enhance current Outpatient Pharmacy software to display patients \n use of Non-VA Med. \ncomprise the Non-VA Meds (Herbals/OTC) project. These two patches are\n 3. Screen for drug-herbal and drug-drug interactions and display the \n results in both Inpatient and Outpatient Pharmacy. \n 4. Display Non-VA Med drugs on the Orders and Meds tab in CPRS. \n 5. Display of drug interaction information involving Non-VA Med \n through CPRS. \n \nThe Phase 1 of this project comprises functionality 1 only. It gives the\nsites the ability to add common herbal and OTC products to the DRUG File\nand mark them as Non-VA Med through the Drug Enter/Edit [PSS DRUG\nENTER/EDIT] option. Furthermore, it also allows the user to mark existing\nbeing released together to deliver Phase 1 of this project, which is\ndispense drugs as Non-VA Med. Once a drug is marked as Non-VA Med, a\nphysician using the CPRS GUI Version 23 application will be able to\ndocument the patient's use of such drug. Which is done by entering a\nNon-VA Med order for the patient. Functionalities 2 through 5 are part of\nthe Phase 2 of this project and will be delivered in a later time.\n \nAn important part of this patch is the update of the Drug file. As\nmentioned before, besides Herbal supplements and Over-the-Counter drugs\n(usually non-prescription drugs), any prescribed medication currently\ndispensed by the VA could be acquired by the patient from another source\nexplained in more details below. Phase 2 will contain the following 4\nother than the VA. Therefore, these drugs must also be marked as Non-VA\nMed. In order to reduce the amount of work necessary to mark the existing\ndispense drug for Non-VA Med use, the following update will occur\nautomatically with the installation of this patch: \n \n EVERY ACTIVE DISPENSE DRUG MARKED FOR OUTPATIENT USE WILL BE MARKED FOR \n NON-VA MED USE. \n \nThe following menu options have also been modified: \n \npatches: PSS*1*69, PSO*7*132, PSJ*5*107 and OR*3*187. They will be\n 1. Lookup into Dispense Drug File [PSS LOOK] \n \n If the dispense drug is marked as Non-VA, it will now print "Non-VA \n Med" in the "APPL PKG USE:" field. \n \n 2. Enter/Edit Dosages [PSS EDIT DOSAGES] \n \n If the dispense drug is marked as Non-VA, it will now print "Non-VA\n Med" under "This entry is marked for the following \n PHARMACY packages:." \nreleased in a later time. Once all patches are installed, they will\n \n 3. Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] \n \n If the orderable item is marked as Non-VA, it will now print "This \n Orderable Item is marked as a Non-VA Med." right after the indication\n of Formulary/Non-Formulary is printed. \n \nA new field NON-VA MED (#8) has been added to the PHARMACY ORDERABLE ITEM\nFile (#50.7).\nprovide the sites the ability to document herbal supplements,\nover-the-counter (OTC)(non-prescription) medications and other \nmedications taken by patients but not dispensed by the Department of\n\n
\n Data Dictionary (DD) changes are being made in order to support requested\n The ORDERS FILE PARENT ORDER sub-field (#150) was added to the IV\n multiple (#100) of the PHARMACY PATIENT file (#55).\n \n The ORDERS FILE PARENT ORDER sub-field (#125) was added to the UNIT DOSE\n multiple (#62) of the PHARMACY PATIENT file (#55).\n changes to Inpatient Medications V. 5.0 included in patch PSJ*5*80.\n \n The REQUESTED DURATION sub-field (#151) was added to the IV multiple\n (#100) of the PHARMACY PATIENT file (#55).\n \n The REQUESTED DURATION sub-field (#126) was added to the UNIT DOSE\n multiple (#62) of the PHARMACY PATIENT file (#55).\n \n\n
\n Several sites have noted that the common brand names printed on a\n Patient Medication Instruction Sheet are not always appropriate.\n This patch stops the printing of common brand names on PMIs printed\n in conjunction with the laser label.\n \n ****NOTE**** The stand alone option Print a PMI Sheet [PSNPMIS PRINT]\n is not modified by this patch.\n\n
\n1. This patch fixes the problem reported in NOIS HON-0403-60272 to\n codes contains the National Drug Code (NDC) number in a new format\n called "Global Trade Item Number (GTIN)". The GTIN has a 14-digit data\n structure, which is used within the EAN.UCC system for unique \n identification of trade items worldwide. This will allow BCMA GUI will \n correctly read the GTIN and search the synonym field for a matching NDC\n number.\n prevent the undefined variable error that occurs whenever DRUG file\n (#50) get updates and HL7 outgining drug message is sent out.\n \n2. This patch deletes the Pharmacy quick order correction for CPRS\n [PSS QUICK1] option, as it is an obsolete option. NOIS SBY-0403-30493\n \n3. This patch modifies the SYNONYM field (#.01) in the DRUG file (#50) to \n allow data entry using the new Reduced Space Symbology (RSS) bar \n\n
\nPharmacy Benefits Management (PBM) Strategic Healthcare Group in\nKernel V. 8.0\nComputerized Patient Record System (CPRS) V. 1.0\nPharmacy Data Management (PDM) V. 1.0\nOutpatient Pharmacy (OP) V. 7.0\nControlled Substances (CS) V. 3.0\n \nThis is the PDM patch that provides the following new functionalities:\n \n1. It provides CPRS with new API's 3737 and 3739 (these are modifications\nof existing API's 3373 and 3233 which shall remain unchanged). The logic\ncollaboration with the Drug Enforcement Administration (DEA), requested\nof deriving at the DEA SPECIAL HDLG code for drugs associated with an\norderable item has changed. The National Drug File data update patches\nPSN*4*64 and PSN*4*66 assign a CS Federal Schedule to controlled\nsubstances and identify controlled substances as narcotics or\nnon-narcotics by populating the CS FEDERAL SCHEDULE field (#19) of the VA\nPRODUCT file (#50.68). If any of the active dispense drugs associated with\nthe Pharmacy orderable item for the specified package are matched to an\nentry in NDF, then the most restrictive CS FEDERAL SCHEDULE code will be\nreturned. If there is no match or the CS FEDERAL SCHEDULE code is\nundefined, then the most restrictive DEA SPECIAL HDLG code mapped to the\nthe development of the first Public Key Infrastructure (PKI) VistA\ncorresponding CS FEDERAL SCHEDULE code will be returned using the\nfollowing table:\n \n CS FEDERAL SCHEDULE DEA, SPECIAL HDLG\nCode\nSchedule I narcotics 1 1\nSchedule II narcotics 2 2A\nSchedule II non-narcotics 2n 2C\nSchedule III narcotics 3 3A\nSchedule III non-narcotics 3n 3C\npilot project, named Electronic Prescription Order Entry for Schedule II\nSchedule IV narcotics 4 4\nSchedule V narcotics 5 5\n \n2. It includes a Post-Install routine to identify those drugs that show\ndiscrepancies between the CS FEDERAL SCHEDULE field (#19) of the VA\nPRODUCT file (#50.68) and DEA SPECIAL HDLG field (#3) of the DRUG file\n(#50), and generates the following 4 mail messages to the installer and\nthe holders of the PSNMGR keys:\nCS FEDERAL SCHEDULE AND DEA, SPECIAL HDLG DISCREPANCIES\nCONTROLLED SUBSTANCES NOT MATCHED\nControlled Substances. The objective is to develop an electronic order\nCONTROLLED SUBSTANCES NOT SET CORRECTLY\nDISCREPANCY IN DEA WITHIN DRUGS TIED TO AN OI\n \nThese mail messages can be used to clean up the DEA SPECIAL HDLG code in\nthe DRUG file where appropriate.\n \n3. It also provides the following new menu options to generate reports of\nthe above mail messages:\nControlled Substances/PKI Reports [PSS CS/PKI REPORTS] menu has the\nfollowing 4 new options:\nentry system for Schedule II controlled substances using digital\n 1 DEA Spec Hdlg & CS Fed Sch Discrepancy [PSS DEA VS CS FED. SCH.\n DISCR.]\n 2 Controlled Substances Not Matched to NDF [PSS CS NOT MATCHED TO NDF]\n 3 CS (DRUGS) Inconsistent with DEA Spec Hdlg [PSS CS DRUGS INCON WITH\n DEA]\n 4 CS (Ord. Item) Inconsistent with DEA Spec Hdlg [PSS CS (OI) INCON WITH\n DEA]\nThis new menu Controlled Substances/PKI Reports [PSS CS/PKI REPORTS],\nwill be added to the Pharmacy Data Management [PSS MGR] menu.\n \nsignatures. To make this project viable, modifications to the following\n4. When using the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option, if the CS\nFEDERAL SCHEDULE field (#19) of the VA PRODUCT file (#50.68) and the DEA\nSPECIAL HDLG field (#3) of the DRUG file (#50) have a discrepancy, then\nthis patch displays a warning message, "The CS Federal Schedule associated\nwith this drug in the VA Product file represents a DEA, Special Handling\ncode of XX", where XX is the CS FEDERAL SCHEDULE code mapped to\ncorresponding DEA SPECIAL HDLG code as defined in the above table.\n \n5. This patch ensures that the newly populated CS FEDERAL SCHEDULE field\n(#19) of the VA PRODUCT file (#50.68) is also included as part of the\npackages were identified:\ndrug details in the Lookup into Dispense Drug File [PSS LOOK] option.\n \n6. This patch introduces a new code "F" for NON REFILLABLE for the DEA\nSPECIAL HDLG field (#3) of the DRUG file (#50). This will allow sites to\nmark drugs other than controlled substances or clozapine drugs as NON\nREFILLABLE. This functionality will be effective in the Outpatient\nPharmacy V. 7.0 package only if the patch PSO*7.0*131 is installed.\n \n7. The designation "A" which stands for "NARCOTICS AND ALCOHOLICS" used in\nthe DEA, SPECIAL HDLG field (#3) of the DRUG file (#50), is changed in\nNational Drug File (NDF) V. 4.0\nthis patch to read as "NARCOTICS AND ALCOHOLS".\n\n
\n1. PSS*1*69 provides additional internal preparation at your site for \n used as a supply if the entry in the PHARMACY ORDERABLE ITEM file \n (#50.7) it is associated with has the SUPPLY field (#.09) set to 1 \n (one). Many sites have expressed their concern about having supply \n items automatically marked for Non-VA Med use. Therefore, sites can \n automatically unmark such items through this patch. The unmarking of \n supply items as Non-VA Meds will be optional. During the patch \n installation the installer will be prompted "Unmark supply items as \n Non-VA Meds? Y //". If 'YES' is selected, every supply item in the \n DRUG file (#50) marked for Non-VA Med use will be unmarked. If for any \n reason the installer chooses NOT to un-mark supply items for Non-VA \n the eventual release of the Herbal/OTC/Non-VA Meds Documentation \n Med use and later wishes to do so, run the Mumps routine PSSUNMSI \n distributed with this patch. \n \n2. A new multiple field NON-VA MEDS (#52.2), has been added to the \n PHARMACY PATIENT file (#55). This field will be used in the future \n to store Non-VA Med orders.\n \n3. The NON-VA MED field (#8) in the PHARMACY ORDERABLE ITEM file (#50.7)\n is being modified to be "Uneditable".\n project. \n \n An important part of this patch is the update of the DRUG file (#50). \n The Post-install routine for patch PSS*1*68 automatically marked for \n Non-VA Med use every active dispense drug that was marked for \n outpatient use. Some of these dispense drugs marked for Non-VA Med use \n were actually being used as supply items. A dispense drug is being \n\n
\n This patch provides functionality to allow an indicator to determine if a \n patient has at least one active prescription. This new routine PSSRXACT \n is to be used as a function call. The patient's internal dfn is required. \n the number 1 is returned to indicate that the patient has at least one \n active prescription, otherwise 0 (zero) is returned. \n \n S X=$$EN^PSSRXACT(DFN)\n\n
\nThis patch will fix an undefined error encountered when using the DEA Spec\nHdlg & CS Fed Sch Discrepancy [PSS DEA VS CS FED. SCH. DISCR.] option\nwhich is under the Controlled Substances/PKI Reports [PSS CS/PKI REPORTS]\nmenu. PSSPKIPR is the only routine contained in this patch.\n\n
\n This patch makes the following changes to address Year 2000 compliance\n Routine : PSSCREAT\n Line Tag : PSSCREAT+12\n Exception : Failure to include "F" in %DT parameter string\n Resolution: Replaces call to %DT with call that includes "F" in %DT\n parameter string.\n \n Routine : PSSPOIM1\n Line Tag : CHECK+1\n Exception : The call C^%DTC makes a comparison to an FileMan internal \n date format. FileMan dates are within compliances.\n issues in the Pharmacy Data Management package.\n Resolution: Later determined no action necessary\n \n Routine : PSSGMI\n Line Tag : ENDTC+2\n ENDTC1+2\n Exception : Not a legal document; two digit year is allowed.\n Resolution: Later determined no action necessary\n \n Routine : PSSLAB\n Line Tag : BEG+4\n BEG+5\n Exception : Not a legal document; two digit year is allowed.\n Resolution: Later determined no action necessary.\n \n\n
\nThis patch modifies the SYNONYM field (#.01) in the DRUG file (#50).\nBarcode Medication Administration (BCMA) uses the Global Trade Item\nNumber (GTIN) format for barcodes. The GTIN has a 14-digit data\nstructure, which is used within the Uniform Code Council/European Article\nNumbering (UCC/EAN) system for unique identification of trade items\nworldwide. This patch corrects the problem in which scanned GTIN entries\nstored in the SYNONYM field were not recognized when doing a lookup on\nentries withing the DRUG file (#50).\n\n
\nData Dictionary (DD) changes are being made to support requested changes\nfor Outpatient Pharmacy V. 7.0 patch PSO*7*135. Patch PSO*7*135 implements\nthe ScripTalk(R) 'talking' prescription labels functionality. The DD\nchanges in this patch are to provide new fields to store the history of\npatients' ScripTalk(R) enrollment activity.\n \nThe SCRIPTALK ENROLLMENT ACTIVITY multiple (#55.0108) was added to the\nPHARMACY PATIENT file (#55).\n\n
\n This change will add the new ROUND ATC PICK LIST UNITS field (#26.7)\n in the PHARMACY SYSTEM file (#59.7) for Inpatient Medications V 5.0 patch\n PSJ*5*119. NOIS ALT-0403-20970\n\n
\nThis project consists of 12 patches that work together to create a new\n GMPL*2*27\n GMRV*4*15\n LR*5.2*295\n OR*3*157\n PSS*1*62\n PSJ*5*90\n PSO*7*118\n PX*1*119\n RA*5*33\n YS*5.01*77\nClinical Reminders index global. The purpose of this index is to provide\n \nThe purpose of this patch (PSS*1*62) is to lay the groundwork for these\nchanges by creating a new cross-reference in the PHARMACY PATIENT file\n(#55) at both the UNIT DOSE multiple (#62) and the IV multiple (#100).\n \nThis patch can be installed independently of the other patches. The \ndocumentation describing the new functionality will be available when all \nassociated patches are released.\nrapid access to clinical data. All of the standard Clinical Reminders\nfinding types are included in the index.\n \nThe 12 patches that comprise this project are:\n \n PXRM*1.5*12\n DG*5.3*478\n\n
\nThe VAPN index for the Drug File (#50) was incorrectly set to the length \nof the VA Product Name All the routines that use the index use a \nmaximum of 30 characters to do the lookup. This patch deletes the \nexisting VAPN index and creates a new one using the DD definition for the \nVA Product Name field.\n\n
\nCorrect typo in file 54 (RX CONSULT), entry NO TRANSFER.\n\n
\n Phase I of the Inpatient Medications Requirements for the Special Focus\n OR*3*213 ORDER ENTRY/RESULTS REPORTING V. 1.0\n PSU*3*34 PHARMACY BENEFITS MANAGEMENT V. 3.0\n \n Patches PSS*1*79, OR*3*213, and PSU*3*34 contain changes to support the\n following enhancements in PSJ*5*110:\n \n 1. The Extend Stop Date on Renewal enhancements will allow an order to be\n renewed without creating a new order. Editing of the start date will no\n longer be allowed during the renewal process. In addition, limits have\n been set on the length of time after an order expires that it may be\n Group IRA project consists of four patches. The patches are combined in\n renewed. This is outlined in the BCMA 2001 Special Focus Report,\n Requirement #11.\n \n 2. The Complex Order enhancements will change the way complex orders are\n handled by linking complex components (child orders) together. If the\n actions Finish, Verify, Discontinue, or Renew are taken on one child\n order, the user will be alerted that the action must be taken on all of\n the complex component orders in the set. The user will then be prompted\n to take the appropriate action on each child order in the complex order\n set. This is outlined in BCMA 2001 Special Focus Report, Requirement #8.\n host file PSJ_PSS_OR_PSU_110.KID in order to simplify installation at VHA\n \n 3. The STAT and NOW Order Notification enhancements will alert users\n subscribing to new mail group PSJ STAT NOW PENDING ORDER when a pending\n STAT or NOW order has been received from Computerized Patient Record\n System (CPRS) V. 1.0. Users subscribing to the new mail group PSJ STAT\n NOW ACTIVE ORDER will receive an alert when a STAT or NOW order is made\n active. This is outlined in BCMA 2001 Special Focus Report, Requirement\n #12.\n \n In order to support the Extend Stop Date for Renewals changes, new fields\n facilities. Installation of this host file should be coordinated among\n will be created in the PHARMACY PATIENT file (#55) and the PHARMACY\n SYSTEM file (#59.7).\n \n 1. The PREVIOUS ORDERS FILE ENTRY sub-field (#4) will be added to the\n LAST RENEW multiple (#114) in the UNIT DOSE multiple (#62) in the\n PHARMACY PATIENT file (#55).\n \n 2. The PREVIOUS ORDERS FILE ENTRY sub-field (#4) will be added to the\n LAST RENEW multiple (#138) in the IV multiple (#100) in the PHARMACY\n PATIENT file (#55).\n the four packages affected since only one installation is necessary. The\n \n 3. The EXPIRED IV TIME LIMIT field (#34) will be added to the PHARMACY\n SYSTEM file (#59.7).\n \n 4. In support of Complex Orders changes, a new cross-reference will be\n created to group complex child orders by their parent order. For Unit\n Dose orders, the cross-reference will be indexed by the ORDERS FILE\n PARENT ORDER field (#125), the ORDERS FILE ENTRY field (#66), and the\n Unit Dose order number appended with "U". For IV orders, the cross-\n reference will be indexed by the ORDERS FILE PARENT ORDER field (#150),\n patches, in order of install, are:\n the ORDERS FILE ENTRY field (#110), and the IV order number appended with\n "V". The cross-reference definition will be created by the pre-install\n routine PSSCMPLX. These are the new cross-references added to the\n PHARMACY PATIENT file (#55) and the fields used as the trigger-points.\n The type of these cross-references is "New", not "Traditional".\n \n X-ref File/Sub-file Trigger-point field(s)\n -----------------------------------------------------------------\n ACX PHARMACY PATIENT (#55) ORDERS FILE PARENT ORDER (#125)\n /UNIT DOSE (#62) ORDERS FILE ENTRY (#66)\n \n \n ACX1 PHARMACY PATIENT (#55) ORDERS FILE PARENT ORDER (#150)\n /IV (#100) ORDERS FILE ENTRY (#110)\n PSS*1*79 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*110 INPATIENT MEDICATIONS V. 5.0\n\n
\n **********************************************************************\n \n There are three patches to support the Outpatient Pharmacy Automation\n Interface project. These patches should be installed separately in the\n following order:\n PSO*7*156 Outpatient Pharmacy\n PSS*1*82 Pharmacy Data Management\n PSN*4*84 National Drug File\n \n They contain routines, templates, options, and data dictionary changes to\n implement the Outpatient Pharmacy Automation Interface features. Please\n * This patch is part of the Outpatient Pharmacy Automation Interface *\n refer to the individual patch description of the other patches to get the\n names of the documentation files.\n \n Each patch will share the same starting description with more detail\n for each patch in the corresponding namespace patch number. There is\n only one installation guide. It can be found on the anonymous \n directory. The name of the installation guide \n PS_OUTPATIENT_AUTOMATION_INTERFACE_IG.doc.\n \n \n * Project and must be installed at all sites by *\n The patch enhances the current Health Level Seven (HL7) interface to\n ensure that the interface is compatible with all current Outpatient\n Pharmacy package V. 7.0 automation systems used by the Veterans Affairs\n Medical Centers (VAMCs). The current national VISTA HL7 interface is\n written to HL7 standard V. 2.2. Automated dispensing systems, such as\n the Baker APS Pharmacy 2000, are currently using an interface written to\n HL7 V. 2.3.1 standard using locally developed software. The automated\n dispensing systems have committed to be HL7 V. 2.4 compliant.\n \n This patch includes the following new features:\n * December 31, 2004 *\n 1. Creates an HL7 interface to the current HL7 V. 2.4 standard.\n 2. The interface transmits drug data to multiple vendor systems\n utilized by VAMCs whenever the following options are selected:\n A. Drug Enter/Edit [PSS DRUG ENTER/EDIT] option.\n B. Edit Orderable Items [PSS EDIT ORDERABLE ITEMS] option.\n C. Enter/Edit Dosages [PSS EDIT DOSAGES] option.\n D. Dispense Drug/Orderable Item Maintenance [PSS MAINTAIN ORDERABLE \n ITEMS] option.\n E. CMOP Mark/Unmark (Single drug) [PSSXX MARK] option.\n F. Synonym Enter/Edit [PSS SYNONYM EDIT] option.\n * *\n \n \n HL7 Interface:\n ==============\n This patch installs the following new HL7 Protocols:\n 1. PDM Master File Update [PSS EXT MFU SERVER] protocol.\n 2. PDM Master File Update Client [PSS EXT MFU CLIENT] protocol.\n \n This patch installs the following new HL7 Application Parameters:\n 1. PSS VISTA\n * Please review the Installation heading of this patch for *\n 2. PSS DISPENSE\n \n New Option:\n ===========\n A new option has been added to the PSS MGR menu called Send Entire \n Drug File to External Interface [PSS MASTER FILE ALL]. This is used to\n send the entire drug file to a dispensing system at first start-up to \n bring the dispensing system in synch with the National Drug file (#50).\n Each dispensing system will decide if they can receive these messages and\n a parameter setting ENABLE MASTER FILE UPDATE will need to be turned on\n * Installation Guide retrieval information *\n in the OUTPATIENT SITE file (#59) in order for these messages to be sent\n across.\n * *\n **********************************************************************\n\n
\nThis patch contains Application Programmer Interface's (API's) that will \n \nThese are the files that are affected. If any application is making \ndirect global reads or writes to any of these files, they must be \nreplaced by using the API's exported with this patch.\n \nFile Name: File Number:\nDRUG 50\nDRUG ELECTROLYTES 50.4\nDOSAGE FORM 50.606\nPHARMACY ORDERABLE ITEM 50.7\nbe used by calling applications that currently do direct global reads or \nMEDICATION INSTRUCTION 51\nADMINISTRATION SCHEDULE 51.1\nMEDICATION ROUTES 51.2\nORDER UNIT 51.5\nIV ADDITIVES 52.6\nIV SOLUTIONS 52.7\nRX CONSULT 54\nAPSP INTERVENTION TYPE 9009032.3\nAPSP INTERVENTION RECOMMENDATION 9009032.5\nwrites to the Pharmacy Data Management files. Since the DRUG file (#50), \nand other drug-related files are being replaced by a vendor product, any \ndirect M-based global reads or writes to these files must be replaced by \ncalling the API's provided in this patch. When the new data source is in \nplace, the calling applications will not be required to make any changes, \nbecause these API's will be flexible enough to retrieve the requested \ndata from the vendor product, when the time comes.\n\n
\nDescription:\nof claim responses (including drug utilization review responses and \nDocumentation Retrieval:\n========================\n \nThe ECME documentation is available on the ANONYMOUS.SOFTWARE directory\nat one of the following Office of Information (OI) Field Offices.\n \nSites may retrieve documentation in one of the following ways:\n \n(1) The preferred method is to FTP the files from\n download.vista.domain.ext, which will transmit the files from the\nwarnings) on a real-time basis, is being developed and introduced in a \n first available FTP server.\n \n(2) Sites may also elect to retrieve documentation directly from a\n specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext \n \nThe documentation distribution includes:\nphased implementation strategy. This deployment strategy was utilized due \n \n FILE NAME DESCRIPTION\n BPS_1_0_IG.PDF HIPAA NCPDP CONNECTION FOR EDI \n PHARMACY \n (DORMANT RELEASE) INSTALLATION GUIDE\n BPS_1_0_RN.PDF HIPAA NCPDP CONNECTION FOR EDI \n PHARMACY\n (DORMANT RELEASE) RELEASE NOTES\n \n(3) Documentation can also be retrieved from VISTA Documentation Library\nto the complexity of the functionality and the number of product line \n(VDL) on the Internet at the following address, http://www.domain.ext/vdl.\n \nInstallation Instructions:\n========================== \n \nThe software for this patch is being distributed via a host file. The \nhost file will contain the following package and builds:\n \n Host file name BPS_1_0.KID\n \ndependencies.\n Package:\n BPS_1\n \n Builds:\n PSS*1.0*81 \n IB*2.0*223\n IB*2.0*251\n PRCA*4.5*202\n \nSites may retrieve the software directly by using FTP from the \n \nANONYMOUS.SOFTWARE directory at the following OI Field Offices:\n \n Albany: ftp.fo-albany.domain.ext\n Hines: ftp.fo-hines.domain.ext\n Salt Lake City: ftp.fo-slc.domain.ext\n \nDo not install this patch while Pharmacy Data Management users are using \nthe software. Installation will take no longer than 15 minutes. There are\nno scheduling restrictions or recommendations.\n \nThe first release of this two part implementation is BPS*1*0, comprised of\nInstallation Steps\n \n 1. Use VA FileMan to add the new domain, EPHARMACY.VITRIA-EDI.AAC.DOMAIN.EXT,\n to the DOMAIN file (#4.2). The installation instructions are included\n in the patch description for the XM*DBA*160 patch. This domain must be\n in place before the installation of the IB*2*251 patch that is\n included in the BPS 1.0 Master Build.\n \n 2. Download the KIDS file BPS_1_0.KID via FTP. This file needs to be \n retrieved in ASCII format.\nthe new Electronic Claims Management Engine (ECME) package (in the BPS \n \n 3. Review mapped sets for the PSS*, IB*, and PRCA*namespaces. If the \n routines are mapped, they should be removed from the mapped set at\n this time.\n \n 4. From the Kernel Installation & Distribution System menu, select the \n Installation menu.\n \n 5. From this menu, select the Load a Distribution option. When prompted \n for a file name, enter the directory name where you FTPd the build, \nnamespace), plus the patches PSS*1*81, IB*2.0*223, IB*2.0*251, and \n followed by BPS_1_0. In our example, the file name is\n USER$:[ANONYMOUS]BPS_1_0.KID. Determine the location where you stored\n your build to decide the correct file name entry.\n \n 6. At the "Want to Continue with Load? YES//" prompt, enter YES.\n \n 7. At the "Want to RUN the Environment Check Routine: YES//" prompt, \n answer YES.\n \n 8. From this menu, the installer may select to use the following options:\nPRCA*4.5*202, which are listed here in order of installation. BPS*1*0 is a\n \n(When prompted for INSTALL NAME, enter BPS 1.0)\n \n a. Backup a Transport Global - This option will create a backup \n message of any routines exported with the patch. It will NOT backup\n any other changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - This option will allow\n you to view all changes that will be made when the patch is installed.\n It compares all components of the patch (routines, DDs, templates,\n===========\ndormant release that only allows each site to perform preliminary setup \n etc.).\n \n c. Verify Checksums in Transport Global - This option will ensure the \n integrity of the routines that are in the transport global.\n \n 9. At the "Select Installation Option:" prompt, enter 6 Install \n Package(s)\n \n10. At the "Select INSTALL NAME:" prompt, enter BPS 1.0.\n \nwork and to confirm that the software does not adversely affect other \n11. When prompted, "Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//" respond NO.\n \n12. When prompted, "Want KIDS to INHIBIT LOGONs during the install? YES//"\n respond NO.\n \n13. When prompted, "Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//" respond NO.\n \n14. When prompted, "Device:Home//" respond with the correct device and DO \npackages.\n NOT queue this to P-Message.\n \n15. If routines were unmapped as part of step 3, they should be returned \n to the mapped set once the installation has run to completion.\n \nThere are two main areas addressed by BPS*1*0:\n \na. Registration of the Pharmacy with the Vitria BusinessWare IE.\nb. The Insurance Matching of Group Plans with Pharmacy Plans\n \nFollowing the installation of BPS*1*0, each site must register their \n \npharmacy with Vitria and match applicable insurance group plans using the \ninsurance matching screens. These processes are detailed in the HIPAA \nNCPDP CONNECTION FOR EDI PHARMACY INSTALLATION GUIDE and the E-PHARMACY\nCLAIMS INSURANCE PROCESS document. Both of these documents are located on\nthe anonymous directory. It is very important that the IRM or person\ninstalling the patch at each facility provide a copy of these documents to\nits ADPAC(s) and any other relevant staff who will be responsible for\nregistering their pharmacy with Vitria and completing the insurance \nmatching process.\n \nPATCH OVERVIEW\nAt a later date, additional HIPAA NCPDP patches will be released to \nactivate all of the HIPAA NCPDP functionality. Until that time, sites will\nnot be able to electronically submit claims utilizing this new \nfunctionality.\n \nThe HIPAA NCPDP project was created in response to a Chief Business Office\n(CBO) request for modifications to several Veterans Health Information \nSystems and Technology Architecture (VistA) software applications in \naccordance with HIPAA Electronic Data Interchange (EDI) transactions and \nNCPDP mandated format standards, specifically the NCPDP Telecommunication \n \nStandard v.5.1.\n \nThe specific functionality for this patch is listed below.\n \nOverview of the Process:\n \nThe changes to Pharmacy Data Management are as follows:\n \n1. DEA, SPECIAL HDLG field (#3) in the DRUG (#50) file.\n \nThe Healthcare Insurance Portability and Accountability Act National \nRoutine PSSDDUT2 was modified to accommodate the use of the letter 'E' \nwithin the DEA, SPECIAL HDLG field (#3) of the DRUG file (#50).\n \n \nData Dictionary Changes in Outpatient Pharmacy:\n \n1. For the DRUG file (#50), the DEA, SPECIAL HDLG (#3) field for the drug\nwill need to accommodate the use of the letter 'E' to indicate that a drug\nis billable for ECME purposes. The routine dealing with the Help Text of\nthis field was modified to accommodate the inclusion of an 'E' within the\nCouncil for Prescription Drug Programs (HIPAA NCPDP) initiative, whose \nlist of possible entries.\n \n \nAssociated NOISs:\n=================\nN/A\n \n \nTest Sites:\n===========\nultimate goal is to provide functionality allowing electronic transmission\nNEW YORK HARBOR HCS\nNORTH TEXAS HCS\nANN ARBOR, MI \nBATTLE CREEK, MI \nDETROIT, MI\nIRON MOUNTAIN, MI\n \nRoutine Summary: \n================\nThe second line now reads as follows: \nof Outpatient Pharmacy (OP) prescription claims to payers and the receipt \n \n <TAB>;;7.0;PHARMACY DATA MANAGEMENT;**[patch list]**; 9/30/97\n \n CHECK^XTSUMBLD results: \n \nRoutine Before Patch After Patch Patch List \n======= ============ =========== ==========\nPSSDDUT2 16160245 16615950 3,21,61,81\n \n \n\n
\nInstall new Dose Forms in DOSAGE FORM file (#50.606).\n\n
\nAdd the non-VA med multiple from file #55 to the Clinical Reminders index.\n\n
\nThis patch contains updated Application Program Interfaces (APIs) that \nActive status. The API manual has been modified since the original version\nto indicate Active and Inactive APIs. If the API(s) you need have an\nInactive status, please contact the Pharmacy Re-Engineering team at the\nBirmingham Field Office.\nwill be used by calling applications that currently do direct global \nreads or writes to the Pharmacy Data Management files. A review of the \npreviously released APIs showed several entry points where additional \npieces of data were required to be returned.\n \nIf you have already made code modifications, or have made plans to make\ncode modifications to use any of the new APIs, please check the latest\nversion of the API manual to verify that the API(s) in question have an\n\n
\n1. The Inpatient Medications Orders for Outpatients project will allow a\n2. A new parameter has been added to the PHARMACY SYSTEM file (#59.7). It \nis the AUTO-DC IMO ORDERS field (#26.8). This new parameter will allow \nsites to control whether or not Inpatient Medications Orders for \nOutpatients are automatically discontinued during patient movements. This \nparameter will only be effective if sites are using Inpatient Medications \nto control discontinues on patient movements. If the site is using the \nCPRS auto-dc rules, this parameter will have no effect.\n \n3. As a part of the Inpatient Medications Requirements for the Special\nFocus Group IRA project, this patch modifies the definition of schedules\nuser the ability to order unit dose medications for outpatients. This is \nin the ADMINISTRATION SCHEDULE file (#51.1). TO accomplish this, the \nfollowing changes are being made to the PSSJ SCHEDULE EDIT input \ntemplate:\n a. Do not allow entry of a schedule with the name of OTHER. \n b. Do not allow entry of administration times for odd schedules. \n c. Display the calculated frequency to the user.\n \n4. Based on the upcoming requirement from the Joint Commission on\nAccreditation of Hospital Organizations, schedule names that are\nconsidered dangerous will no longer be allowed. The four schedules that \naccomplished through modifications to Inpatient Medications V. 5.0,\nwill no longer be allowed are: QD, HS, TIW and QOD. These schedules \ncannot be used either alone or as part of a schedule name. For example: \nQD is not allowed. Neither is QD ONCE.\n \n5. The Inpatient Medications Requirements for the Special Focus Group IRA\nproject will prevent users from entering free text schedules for inpatient\nmedication orders. This patch helps accomplish this by changing the\nvalidation of schedules entered through Computerized Patient Record System\n(CPRS) V. 1.0. This validation requires that schedules be defined in the\nADMINISTRATION SCHEDULE file (#51.1) or be a valid day-of-week, PRN or\nComputerized Patient Record System (CPRS) V. 1.0, and Scheduling V. 5.3.\nadministration time schedule before allowing the schedule to be added to\nan inpatient order.\n \n6. A provider entering an order into Computerized Patient Record System\n(CPRS) V. 1.0 must be permitted to place a limitation on the duration of\nan inpatient medication order. This capability exists for Unit Dose orders\nand Inpatient IV orders, but not for IV Fluid orders. This patch helps \naccomplish this by adding a new field to the PHARMACY PATIENT file (#55), \nIV multiple (#100) called REQUESTED IV LIMITATION (#152).\nThe purpose of this patch is to create three new fields in the PHARMACY\nPATIENT file (#55). In the UNIT DOSE multiple (#62), the CLINIC field\n(#130) and the APPOINTMENT DATE/TIME field (#131) have been added. In the\nIV multiple (#100), the APPOINTMENT DATE/TIME field (#139) has been added.\n \n\n
\nIn some cases when ordering a drug the incorrect dispense unit shows.\n\n
\nAs part of the Outpatient Pharmacy V. 7.0 Laser Labels Phase II project, \nData dictionary changes:\n===========================\nNew fields:\n1. PHARMACY SYSTEM file (#59.7), WARNING LABEL SOURCE field (#16)\nThe new warning label processing is not fully functional until this field\nis set to "N" for "New" in the Pharmacy System Parameters Edit [PSS SYS \nEDIT] option.\n2. DRUG file (#50), NEW WARNING LABEL LIST field (#8.1)\nIf the default warnings for a drug are not sufficient, a custom list of \nwarning numbers can be created and stored in this field.\na new commercial data source will be utilized to provide warning label\n3. DRUG file (#50), GENDER SPECIFIC LBLS ON ALL RX field (#8.2)\nIf the commercial data source has indicated that a particular warning \nonly applies to one gender, then if this flag is null or "Y", the warning \nwill print for all patients. If this field is "N", the warning will only\nprint for this drug when the patient is that specific gender.\n4. RX CONSULT file (#54), WARNING MAPPING field (#2)\n5. RX CONSULT file (#54), SPANISH TRANSLATION field (#3)\n \nThe last 2 fields in the above list will have some entries populated\nautomatically in a post-install routine with this patch. The mapping is\ninformation. \nused for matching entries in the old RX CONSULT file (#54) with the\nequivalent entry in the new WARNING LABEL-ENGLISH file (#50.625).\n \nNew options under the PSS Manager [PSS MGR] option:\n==================================================\n1. Warning Builder [PSS WARNING BUILDER] option allows the user to print a\ncopy of the old and new warning file entries and to choose various ways to\nselect drugs to review which warnings will print when the flag is turned\nto use the new warning label source. It also allows the user to override\nthe default warning labels to create a custom warning label list for the\n \nselected drug. This is done by specifying a list of warning numbers from\nthe old RX CONSULT file (#54) and/or the new commercial data source\nwarning file.\n2. Warning Mapping [PSS WARNING MAPPING] option can be used to match an\nentry from the old RX CONSULT file (#54) to the WARNING LABEL-ENGLISH \nfile (#50.625) to aid in using the Warning Builder (to identify local\nwarnings that do not have an equivalent entry in the new commercial data\nsource). The user can also enter a Spanish translation for an RX CONSULT\nfile (#54) entry, if desired, but whenever possible, the new commercial\ndata source's warnings should be used.\nThis patch is required by PSO*7*161 which does the printing of the \n \nTemplate changes:\n=================\nThis patch modifies the DRUG file (#50) INPUT template [PSSCOMMON] to \nallow the user to view the new warning labels for a drug and edit the NEW \nWARNING LABEL LIST field (#8.1), if desired. For drugs that have a \ngender-specific warning associated with them, the new GENDER SPECIFIC \nLBLS ON ALL RX field (#8.2) will also be prompted.\nwarning labels on the laser labels form.\n \nThe following changes are included in this patch:\n \n\n
\nA request has been made to allow sites to define inpatient orders for \noutpatients auto-dc capabilities on a clinic-by-clinic basis. This patch \nhelps to accomplish this goal by removing the AUTO-DC IMO ORDERS field\n(#26.8) and associated data from the PHARMACY SYSTEM file (#59.7).\n\n
\nThis patch will correct an undefined variable error that occurred during \nSQA testing of the Inpatient Medications patch PSJ*5.0*126. When the \nanalyst tried to use the ? or ?? lookup/help functionality for the TO \nSERVICE field in option [PSJ AC SETUP], the error occurred and prevented \nthe analyst from further testing CLE-0604-40092 (NOIS)/HD0000000068038.\nThis patch will be installed with patch PSJ*5.0*126.\n\n
\nCHANGE DATA DESCRIPTION FOR MEDICATION ROUTE FIELD #3 IN NON-VA MEDS \nSUB-FILE #55.05 IN PHARMACY PATIENT FILE #55. CHANGE FIELD LENGTH FROM \n20 TO 40.\n\n
\nThis patch makes a change to one of the Pharmacy Data Management \nencapsulation routines. A new component has been added that will allow \nother packages to perform VA FileMan data retrieval through a Pharmacy \nApplication Program Interface (API).\n\n
\nThis patch contains Application Program Interfaces (APIs) that will be \nsource, when the time comes.\n \nThese are the files that are affected. If any application is making \ndirect global reads or writes to any of these files, they must be \nreplaced by using the APIs exported with this patch.\n \nFile Name: File Number:\nRX PATIENT STATUS 53\nPHARMACY PATIENT 55\nPHARMACY SYSTEM 59.7\nused by calling applications that currently do direct global reads or \nwrites to the Pharmacy Data Management files. Since the PHARMACY PATIENT \nfile (#55) and PHARMACY SYSTEM file (#59.7) are being replaced as part of \nthe Pharmacy Re-engineering project, any direct M-based global reads or \nwrites to these files must be replaced by calling the APIs provided in \nthis patch. When the new data source is in place, the calling \napplications will not be required to make any changes, because these APIs \nwill be flexible enough to retrieve the requested data from the new data \n\n
\nThis patch fixes three problems and provides one enhancement. It will allow\nyou to edit the IV Additives and IV Solutions Print Names. The patch\nexpands the help text on the GENERIC NAME field and updates a typo in\nthe data dictionary in the VA Classification field in DRUG file (#50).\nThe post-install routine re-indexes the NATIONAL DRUG CLASS field, also\nin DRUG file (#50).\n\n
\nThis patch will fix the problem with lookups in the Pharmacy Orderable \nItem file (#50.7) when entering in lowercase drug names.\n\n
\n 1. PSI-05-051: A priority status of ASAP is not easily seen by the \n The site can select STAT, ASAP, or NOW orders, or any combination of \n the three for notification via the mail group functionality.\n \n This patch is adding two additional fields (parameters) to file 59.7, \n PHARMACY SYSTEM FILE to enable the sites to select the priorities that\n will be used in the Inpatient Medications PENDING and ACTIVE order \n notification software. This will solve the reported problem in \n HD98412 / PSI-05-051 by enabling the site to be notified when ASAP \n orders are submitted by the physician.\n finishing pharmacist. A STAT order is displayed as blinking and \n highlighted, but a ASAP order does not have any special visual\n effects. \n \n In order to avoid adding more special visual effects to the screen \n this patch is designed to provide two System Parameters that will\n allow the site a choice of what orders are sent to the PSJ STAT\n NOW ACTIVE ORDER and PSJ STAT NOW PENDING ORDER mail groups.\n\n
\nThis patch fixes an error that could occur when invoking the VAC^PSS50 or\nASP^PSS50 Application Program Interface, which are both supported by\nIntegration Agreement 4533.\n\n
\nThis patch will add MG-PE & NANOGRAM to the DRUG UNIT field #2 of\nIV ADDITIVES file #52.6\n\n
\nA change has been made to the DIC^PSSDI and MIX^PSSDI components of DBIA \n \nA new component, FNAME^PSSDI has been added to DBIA 4551. This component \nwill return the LABEL attribute of the Field passed into the call.\n \nPatch PSS*1*92 adds the SERVICE CODE field to the output of the \nDATA^PSS50 component of DBIA 4533. This patch cirrect the problem where \nthis field is not being returned if a "??" value is passed into the call.\n4551. DIC("S") will be killed within these components. Two new input \nparameters have been added to address screening issues. If the file you\nare passing in has an Inactivation Date field, and you want to screen on \nthat field, a new date input parameter is being added to the components, \nand if a date is passed in, a screen will be set for the calling\napplication. If the file you are passing in is the DRUG file (#50), and \nyou want to screen on the APPLICATION PACKAGES' USE field (#63), and new \ninput paramter has been added for that also.\n\n\nThis patch will correct the reported problems with in the \nWARNING BUILDER option [PSS WARNING BUILDER]. It will also\nmodify the input transform for the VOLUME field of IV SOLUTIONS\nfile #52.7 to allow a leading zero.\n\n
\n1. The Computerized Patient Record System (CPRS) V. 1.0 has requested a \nschedule selected had PRN in the name, an Expected First Dose is \ndisplayed which is not correct. This patch assists in correcting this\nproblem by modifying the TYPE OF SCHEDULE field (#5) in the ADMINISTRATION\nSCHEDULE file (#51.1) to allow PRN. This information will then be provided\nin an API to CPRS. PSI-05-026.\nnew Application Programming Interface (API) from Pharmacy Data Management \nV. 1.0. The new API will allow CPRS to request the current status of any \norder for both Inpatient Medications V. 5.0 and Outpatient Pharmacy V. \n7.0. \n \n2. During internal testing, it was discovered that the Expected First \nDose display in CPRS was inconsistent for PRN orders. If a provider \nchecked the PRN box, no Expected First Dose is displayed. However, if the \n\n
\nThis project involves six different applications that have been significantly\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*148\n field (#81). When a new prescription is entered for a specific drug, the DAW\n CODE from the drug is stored in the PRESCRIPTION file (#52) for each fill.\n This field is solely being used for electronic billing purposes. It \n communicates to the third party payer that a drug has a special \n characteristic, which will hopefully prevent the payer from rejecting the\n claim. Below are all 10 existing DAW CODES:\n \n 0 - NO PRODUCT SELECTION INDICATED\n 1 - SUBSTITUTION NOT ALLOWED BY PRESCRIBER\n 2 - SUBSTITUTION ALLOWED-PATIENT REQUESTED PRODUCT DISPENSED\n INTEGRATED BILLING (IB) V. 2.0 IB*2*276\n 3 - SUBSTITUTION ALLOWED-PHARMACIST SELECTED PRODUCT DISPENSED\n 4 - SUBSTITUTION ALLOWED-GENERIC DRUG NOT IN STOCK\n 5 - SUBSTITUTION ALLOWED-BRAND DRUG DISPENSED AS A GENERIC\n 6 - OVERRIDE\n 7 - SUBSTITUTION NOT ALLOWED-BRAND DRUG MANDATED BY LAW\n 8 - SUBSTITUTION ALLOWED-GENERIC DRUG NOT AVAILABLE IN MARKETPLACE\n 9 - OTHER\n \n Note: The existing entries in the DRUG file (#50) will NOT be automatically\n populated with a DAW CODE value upon installation of this patch.\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*90\n However, the null value is automatically save as 0 (zero) - NO PRODUCT\n SELECTION INDICATED in a prescription entered for a drug with a null\n DAW CODE.\n \n3. The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option has been modified to allow\n the user to associate a DAW CODE to a drug in the DRUG file (#50). \n \n4. The Lookup into Dispense Drug File [PSS LOOK] option has been modified to\n display the DAW CODE field (#81) content for the drug being displayed.\n Below is the exact point where the DAW CODE is displayed:\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*48\n \n ...\n DEA, SPECIAL HDLG: 6 NDC: 00172-4390-18\n DAW CODE: 5 - SUBSTITUTION ALLOWED-BRAND DRUG DISPENSED AS A GENERIC\n CS FEDERAL SCHEDULE:\n ...\n ACCOUNTS RECEIVABLE (AR) V. 4.5 PRCA*4.5*230\n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*1\n \nVeterans Health Information Systems and Technology Architecture (VistA) \nsoftware applications and infrastructure were enhanced, in order to allow the\nelectronic transmission of outpatient pharmacy prescription claims (WINDOW and\nchanged to enable VA Medical Centers to perform third party electronic billing\nMAIL fills) to third party payers via the network connections available\nthrough the Austin Automation Center (AAC). VistA will be enhanced to receive\nelectronic adjudicated responses from the third party payers, which include\nreal-time processing for Drug Review Utilization and Refill Too Soon rejects.\nReject information will be displayed to the pharmacist as the prescription is\nbeing processed. The pharmacist will have the capability to take the\nappropriate action to ensure patient safety or to override the reject and\nresubmit the claim to the payer for payment. When a status of "PAYABLE" is\nreturned by the payer for a released prescription, VistA will automatically \ncreate the bill in IB, authorize it and immediately create the receivable in\nfor prescriptions. \nthe AR application. Since the exact amount being paid by the payer is known,\na decrease adjustment will be automatically generated and applied so that the\nreceivable is equal to the net amount due from the payer.\n \nThe system also provides electronic payment matching capability (for\nelectronically billable outpatient pharmacy prescriptions) using the existing\nElectronic Data Interchange (EDI) Lockbox functionality which processes other\nelectronic payments from third party payers. This real-time electronic claims\nprocessing capability will be provided in accordance with the Healthcare\nInsurance Portability and Accountability Act (HIPAA), EDI transactions and \n \nthe National Council for Prescription Drug Programs (NCPDP) mandated format \nstandards, specifically NCPDP Telecommunication Standard V. 5.1. Additional \nfunctionality delivered with this project includes: \n \n . Auto-Release/Outpatient Pharmacy Automation Interface (OPAI) Integration.\n . Back-billing capability to allow electronic billing of claims from within \n the IB application.\n . Capability to MOVE a group of subscribers from one insurance plan to \n another while automatically "expiring" the old plan, which is a major\n time saver.\nBelow is a list of all the applications involved in this project along with\n . Pharmacy Dispensed As Written (DAW) prescription processing.\n \nOverview of the Process:\n \nWhen a prescription is about to be filled and dispensed by the pharmacy, the \nOP application submits the prescription to the new ECME application. ECME then\ncontacts IB to verify whether or not the prescription is electronically\nbillable. If so, ECME gathers the information necessary to generate a NCPDP\nclaim. The claim information is passed to the VistA Health Level Seven (HL7)\npackage. The HL7 package then sends the billing information to the AAC, where\ntheir patch number:\nit is routed to the corresponding third party insurance via Emdeon (formerly\nWebMD).\n \nOnce the payer processes the information, the response coming back from the\npayer is passed back to the site that made the request, and the information\nis stored in the ECME package. If the third party payer accepted the claim,\nthe adjudicated information is passed along to IB. If the claim was rejected\nthe problem can be worked on and a new claim can be submitted to the payer.\n \nFor electronically billable CMOP prescription processing, the third party\n \nclaim is sent before the prescription information is transmitted to the\nCMOP facility to be filled. Once the adjudicating response is electronically \nreceived from the third party payer, if there are no Drug Utilization Review\nor Refill Too Soon rejects, the prescription is then transmitted to the CMOP \nfacility. When the CMOP center sends the dispensing information back to VistA,\nthe National Drug Code (NDC) information is checked against the NDC sent to \nthe third party payer and, if different, a new claim is generated in the \nbackground and is sent to the third party payer. In case the CMOP facility \nindicates that it is unable to fill a "PAYABLE prescription fill, a reversal\nis automatically submitted to the third party payer for the corresponding \n APPLICATION/VERSION PATCH\nfill.\n \nThis patch modifies PDM V. 1.0 to support the other applications in the\nelectronic claims generation process. It does not interface with the ECME\napplication at all. The changes to this application are the following:\n \n1. A new multiple field has been added to the DRUG file (#50) to store the\n latest NDC numbers that have been dispensed at window as well as by CMOP\n for a specific division. This way, when the next prescription is entered by\n the division for the same drug, the last used NDC is automatically\n -----------------------------------------------------------------\n retrieved from this new multiple, stored in the PRESCRIPTION file (#52) and\n sent to the third party payer through ECME. Below is the multiple field and\n the fields under it:\n \n 32 NDC BY OUTPATIENT SITE\n .01 OUTPATIENT SITE \n 1 LAST LOCAL NDC \n 2 LAST CMOP NDC \n \n2. A new field has been added to the DRUG file (#50) to store the DAW CODE\n\n
\nThis patch will fix the UNDEFINED error that occurs when Using \n'Drug Enter/Edit' [PSS DRUG ENTER/EDIT] option. It will also\nmodify the trigger for PRICE PER ORDER UNIT field #13 of the\nDRUG file (#50) to use 4 decimal places instead of 3.\n\n
\n This patch contains Application Program Interfaces (APIs) that will be \n enough to retrieve the requested data from the new data source when\n the time comes.\n \n If any application is making direct global reads or writes to this file\n they must be replaced by using the APIs exported with this patch.\n used by calling applications that currently do direct global reads or \n writes to the Pharmacy Data Management file. Since the PHARMACY PATIENT\n file (#55) is being replaced as part of the Pharmacy Re-engineering\n project, any direct M-based global reads or writes to this file must be\n replaced by calling the APIs provided in this patch.\n \n When the new data source is in place, the calling applications will not\n be required to make any changes, because these APIs will be flexible\n\n
\nMANAGEMENT OF PHARMACY DATA FILES.\n\n
\nFor maintenance of Pharmacy files and fields.\n\n
\nDSS EXTRACTS v3.0\nEnhancement Patch ECX*3.0*1\n\n
\nPatch to patch ECX*3*9.\n\n
\nVBEC Extract\n\n
\nThis patch addes NPPD code 970 to routine ECXAPRO3.\n\n
\nThis patch provides a fix to the Pharmacy Extracts Unusual Volumes Report\n\n
\nADD 11 NEW LOINC CODES\nREMOVE 3 LOINC CODES\n\n
\nThis patch provides an update to National Clinic file 728.441.\n\n
\nThis patch provides an update to National Clinic file (#728.441).\n\n
\nFY10 DSS EXTRACT CHANGES\n\n
\n-Updates to the NATIONAL CLINIC (#728.441) file.\n\n
\nSee the Patch description for ECX*3*11 in the Patch Module.\n\n
\nThis patch will correct entry of stop codes in file 728.44 if there are\nduplicate codes in the CLINIC STOP file(#40.7), correct DSS Identifier \nNon-Conforming Clinics Report, and verify entry of DSS Stop code and \nDSS Credit Stop code before saving\n\n
\nThis patch has the following changes:\n-makes an update to the QUASAR Extract (ECXQSR).\n-corrects a problem when transmitting extracts. \n\n
\nThis patch will update the DSS Logical Observation Identifiers Names\nand Codes (LOINC) (#727.29) FILE by adding 120 new codes, removing \n5 existing codes, and changing the name of 6 DSS Test names.\n\n
\nThe patch is for an error occurring on the Transfer and Discharge Extract\n[ECXMOV], to fix a problem that is occurring on the SUR Volume Report\n[ECX SUR VOL REPORT], and to fix a problem on the Surgery Extract \n[ECXSURG].\n\n
\nFY 2011 ENHANCEMENTS\n\n
\nPatch ECX*3.0*131 adds 1 new clinic code to the NATIONAL CLINIC \n(#728.441) file.\n\n
\nThis patch will address an update to the NATIONAL CLINIC (#728.441) file.\n\n
\nThis patch will update the DSS Logical Observation Identifiers Names\nand Codes (LOINC) (#727.29) FILE by adding 19 new codes. Two of these 19 \ncodes already exist, so they will first be deleted then added to the file \nwith the new information.\n\n
\nFY12 DSS ENHANCEMENTS\n\n
\nDSS Extracts FY1999 Update.\n\n
\nPatch ECX*3.0*135 adds 35 new clinic codes and updates the description\nof 2 existing codes in the NATIONAL CLINIC (#728.441) file.\n\n
\nOne of the changes made in the recently released DSS FY 2012 updates \nand XXXXX represents the 3 to 5 character station code plus the characters\nH, O and 2.).\n \nThis change caused an error to be encountered when running the\nProsthetics (PRO) YTD HCPCS Report [ECX PRO YTD REPORT].\n \nAlso, the package date on the 2nd line of routine ECXUPRO1 was \ninadvertently Changed, and will be changed to the correct date of Dec 22,\n1997.\npatch was the addition of HO2 as a feeder location for the prosthetics \nextracts. \n \nHere is the description of the change from patch ECX*3*132:\n \nModify the PRO Extract programming to create a new Feeder Location value\nfor Home Oxygen records. Add a Feeder Location for Home Oxygen (XXXXXHO2)\nwhen the "NPPD New Code" = 800 x (where the x represents a letter code\n\n
\nPatch ECX*3.0*139 adds 14 new clinic codes and updates the description\nof 1 existing code in the NATIONAL CLINIC (#728.441) file.\n\n
\nPatch ECX*3.0*140 will update the DSS Logical Observation Identifiers \nNames and Codes (LOINC) FILE (#727.29) file by adding 4 new codes.\n\n
\nFY13 DSS ENHANCEMENTS\n\n
\nPatch ECX*3.0*141 adds 2 new clinic codes and updates the description\nof 2 existing codes in the NATIONAL CLINIC (#728.441) file.\n\n
\nPatch ECX*3.0*146 adds 41 new clinic codes and updates the description\nof 4 existing codes in the NATIONAL CLINIC (#728.441) file.\n\n
\nPatch ECX*3.0*142 addresses three different issues:\n \n 3. Worksheets for DSS Clinic Stops [ECXSCLOAD] option does not\n display edit to Inactive Clinics.\n \n 1. IVP Source Audit Report is displaying test patients.\n \n \n 2. After editing DSS Clinic Stop Codes routine (ECXSCLD) does\n not prompt for another clinic but returns to the prior menu.\n \n \n\n
\nPatch ECX*3.0*147 adds 7 new clinic codes and updates the description\n of 12 existing codes in the NATIONAL CLINIC (#728.441) file.\n\n
\nPatch ECX*3.0*150 updates the description 5 existing codes and \ninactivates 1414 codes in the NATIONAL CLINIC (#728.441) file. \n\n
\nThis patch will update the DSS LOINC (#727.29) file.\n\n
\nMID FY15 UPDATE TO THE NATIONAL CLINIC (#728.441) FILE\n\n
\nFY16 UPDATE TO THE NATIONAL CLINIC (#728.441) FILE\n\n
\n Patch ECX*3.0*156 addresses two issues:\n \n 1. The Clinic Visit Extract is not properly building the Feeder Key (#9) \n field value.\n \n 2. The LBB Pre-Extract Audit Report [ECX LBB PRE-EXTRACT] option is not\n picking up all entries.\n\n
\nThis patch will update the DSS LOINC (#727.29) file.\n\n
\nPatch ECX*3.0*159 adds 4 new entries and updates the SHORT DESCRIPTION \n(#1) field of 11 existing entries in the NATIONAL CLINIC (#728.441) file.\n\n
\nPatch ECX*3.0*163 updates the SHORT DESCRIPTION (#1) field of 3 existing \nentries in the NATIONAL CLINIC (#728.441) file.\n\n
\nThis patch will update the DSS LOINC (#727.29) file.\n\n
\nPatch ECX*3.0*165 updates the SHORT DESCRIPTION (#1) field of 10 existing \nentries in the NATIONAL CLINIC (#728.441) file.\n\n
\nThis patch updates the NATIONAL CLINIC (#728.441) file.\n\n
\nNATIONAL CLINIC (#728.441) File Update\n\n
\nPatch ECX*3.0*171 adds 15 new entries and updates the SHORT DESCRIPTION \n(#1) field of 9 existing entries in the NATIONAL CLINIC (#728.441) file.\n\n
\nMID-FY19 CHANGES FOR 4 CHAR CDS NATIONAL CLINIC (#728.441) FILE\n\n
\nPatch ECX*3.0*175 updates the SHORT DESCRIPTION (#1) field of four \nexisting entries in the NATIONAL CLINIC (#728.441) file.\n\n
\nThis patch updates thirteen (13) CHAR4 codes to reflect Fiscal Year 2020\nMid-Year changes, effective April 1, 2020.\n\n
\nThis patch updates eighteen (18) CHAR4 codes to reflect Fiscal Year 2021 \nchanges, effective October 1, 2020.\n\n
\n \nSee Patch Description\n\n
\nBackup of ECX*3.0*180 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch updates thirteen (13) CHAR4 codes to reflect Fiscal Year 2021 \nMid Year changes, effective April 1, 2021.\n\n
\nThis patch ECX*3.0*182 adds three (3) new CHAR4 codes to NATIONAL CLINIC \n(#727.441) file to reflect Fiscal Year 2022 changes, effective October 1, \n2021.\n\n
\n \nSee Patch Description.\n\n
\nPatch ECX*3.0*183 adds two (2) new CHAR4 codes and updates twenty six (26)\ncode names to NATIONAL CLINIC (#727.441) file to reflect Fiscal Year 2022\nMid-Year changes, effective April 1, 2022.\n\n
\n \nSee Patch Description.\n\n
\nSee Patch Description.\n\n
\nFY23 MID YEAR CHAR4 CODE UPDATE\n\n
\nDSS FY24 CHAR4 CODE UPDATES\n\n
\n \nSee Patch Description.\n\n
\nPatch ECX*3.0*189 updates TEN (10) code names and adds one (1) code name\nto the NATIONAL CLINIC (#728.441) file to be effective April 1, 2024.\n\n
\nPatch ECX*3.0*191 updates FIVE(5) code names to the NATIONAL CLINIC \n(#728.441) file to be effective OCT 1, 2024.\n\n
\nCHAR4 PATCH UPDATE OF NATIONAL CLINIC FILE (#728.441) FOR FY2025 MIDYEAR\n\n
\nINACTIVATE NATIONAL CLINIC CODE 'SOGI' IN FILE 728.441\n\n
\nECX*3.0*3\nFix null subscript error at FEEDER+26^ECXSCX.\n\n
\nDSS FY2000 Update\n\n
\nECX*3.0*4\nFind the treating specialty record for the admission; extend search.\n\n
\nSee patch description.\n\n
\nMiscellaneous fixes\n\n
\nPatch: ECX*3.0*36 CORRECTIONS TO PROSTHETICS REPORTS\nPlease see the description in the NPM for complete information.\n\n
\nPlease see the patch description in the NPM for complete details of this\npatch.\n\n
\nPatch ECX*3.0*5\n\n
\nPlease see the patch description in the NPM for complete details of this\npatch.\n\n
\nPlease see the patch description in the NPM for complete details of this\npatch.\n\n
\nPlease see the patch description in the NPM for complete details of this\npatch.\n\n
\nUpdate National Clinic File (#728.441) codes for FY2004\n\n
\nDSS*3.0*2\nRevisions for Y2K.\n\n
\nThis patch addresses the problem of the admission date field (36) storing \nthe wrong admission date in Surgery Extract (727.811;36).\n\n
\nThis patch addresses the problem when an inquiry is made to DSS\nMental Health Tests (727.5) file thru Fileman. The data for the\nTest Name field (.01) is not being displayed.\n\n
\n \nThe QUASAR Extract [ECXQSR] is incorrectly pulling invalid provider\nnumbers from the QUASAR A&SP Visit File. The extract is pulling the A&SP\nprovider without using the A&SP provider pointer logic resulting in an\ninvalid NEW PERSON file lookup.\n\n
\nThe DSS Clinics and StopCodes Worksheet file (#728.44) data entry \ncurrently allows invalid Stop Code values and it should not. It allows \nthem to be entered into the DSS Stop Code and the DSS Credit Stop Code \nfields. During data entry both these fields should be checked against \nvalid stop codes in the Clinic Stop file (#40.7) and not allow entry of a \nstopcode that does not exist in file #40.7, but instead give an error \nmessage when that occurs.\n\n
\nECX*3.0*6\n\n
\nFix for problem of picking up incorrect losing ward for Discharge While \nASIH type discharge records in MOV Extract.\n\n
\nReview Extract for Transmission not working. \n\n
\nFix for duplicate observation encounters in the Laboratory Extract.\n\n
\nAdd 'S' prefixed NDC codes to Pharmacy Extracts Incomplete Feeder Key\nReport, update YEAR MONTH field definition for the Clinic \nExtract file, identify inactive divisions in division selection list for \nthe Surgery Extract Audit Report, update DSS documentation with \nglobal journaling recommendation.\n\n
\nThis patch provides the fix to the CLINICAL EXTRACT and Quasar Extract\nReport.\n\n
\nThis patch provides a fix to the DSS Extracts when transmitting\nextracts to the production queue.\n\n
\nThis patch provides changes to file #727.813 -- LABORATORY EXTRACT (LAB)\nFile Data Definition.\n\n
\nDecision Support System's Fiscal Year 2005 updates.\n\n
\nThis patch updates VISTA file 728.441.\n\n
\nThe DSS Blood Bank Extract project will provide a means of exporting data \nfrom the VistA Blood Bank application and transmitting it to a DSS \ndatabase residing at the AAC. Data from the VistA Blood Bank package will\nbe stored by the extract routine in an intermediate file, where it will be\ntemporarily available for local site DSS review and audit prior to running\nof the extract. The data will then be transmitted to the AAC, where it \nwill be formatted and uploaded into other software products.\n\n
\nUpdate File #728.441 per DSS Program Office.\n\n
\nThe purpose of this patch is to add 960 F NPPD code to PRO Extract Audit\nReport.\n\n
\nWrong Production Division being pulled for Lab Extracts.\n\n
\nThis patch updates DSS file 728.441.\n\n
\nThis patch provides a fix to the Mental Health Extract.\n\n
\nThis patch provides the fix to the encounter number for the\nPrescription Extract.\n\n
\nThis patch updates the DSS LAB TESTS 727.2 file.\n\n
\nThis patch updates NATIONAL CLINIC file #728.441.\n\n
\nDSS FY 2006 Updates\n\n
\nThis patch provides the fix to several remedy tickets.\n\n
\nUse API distributed with NDF v4.0 for Pharmacy Feeder Keys.\n\n
\nUpdates the National Clinic file (#728.441).\n\n
\nThis patch addes NYH--NPPD Categories to routine ECXAPRO3.\n\n
\nThis patch provide a fix to ECX EXTRACT LOG SUMMARY routine and option.\n\n
\nThis patch updates file 728.441.\n\n
\nThis patch provide a fix to routine ECXUSUR.\n\n
\nThs patch provides a fix to the IV Extract.\n\n
\nThis patch provides a fix to the IVP DETAIL EXTRACT\n\n
\nThis patch provides a fix to the Prosthetic Extract and Nutrition Worksheets.\n\n
\nSee the Patch description for ECX*3*9 on the patch module.\n\n
\nThis patch provides a fix to the Surgery Extract routine.\n\n
\nFIX NUTR DIV/PHARM UNUSUAL VOL RPT FIX/LAB BBANK DIV FIX\n\n
\nThis patch provides a fix to the ECXQSR Extract.\n\n
\nThis patch updates the National Clinic file (#728.441).\n\n
\nThis patch updates the National Clinic file 728.441.\n\n
\nThis patch provides a fix to the Pharmacy Unusual Volume Report.\n\n
\nDSS FY08\n\n
\nThis patch provides a fix to the ECX PROS COST Report, Pharmacy Extracts\nIncomplete Feeder Key Report [ECX PHA FKEY],Surgery Unusual Volume Report\nand Nutrition (NUT) Extract Audit Report.\n\n
\nThis patch provides an update to file 727.2\n\n
\nDSS EXTRACTS v3.0\nNational Release\n\n
\nThe DSS software provides a way to load data from DHCP to a commercial\ndecision support system. The software extracts data from several DHCP\nfiles. Extracted data elements are stored in summary files which may\nbe reviewed before being transmitted to the commercial software.\n\n
\n This package contains a National Database Integration (NDBI) routine,\n build will perform an environment check to determine if the site is an\n integrated facility (NDBI site). If so, NDBI data files will be updated,\n as necessary, with corrected entries.\n \n This can be installed at any time while users are on the system and\n will take no more than a few minutes to complete.\n \n The checksum value for this routine is 73468.\n A7RXDRPT which will be referenced by the Duplicate Record Merge patch\n (XT*7.3*23). It must be installed at all sites. When installed it will\n populate the PACKAGE (#9.4) file with the new entry of NDBI and the\n fields AFFECTS RECORD MERGE (#20), FILE AFFECTED (#.01) with 'PATIENT'\n and NAME OF MERGE ROUTINE (#3) with 'A7RXDRPT'.\n \n When the Duplicate Resolution options, exported by the XT*7.3*23\n patch, are run for the PATIENT (#2) file, the routine exported in this\n\n
\n The National Database Integration System (NDBI) is an application\nroutines, A7RP* options and A7RC* options. The other build is NDBI LEGACY\nSYSTEM, consisting of all NDBI files, A7R* routines, A7RL* options and\nA7RC* options. \n \n The options are in the namespace of A7RC, A7RL and A7RP. The A7RC*\noptions are Common options used at the legacy and primary sites. They\nconsist of utilities that are used for the New Person and Patient files,\nand our NDBI Event Log utilities. The A7RL* options are Legacy options\nused to collect and process data from the legacy site only. The A7RP*\noptions are Primary options used to preview, merge and process the data\ndeveloped for the VA medical center integrations. This package contains\ncollected from legacy system. These A7RP* options are used on the primary\nsite only. \nthe files used at the legacy and primary sites. The entire application\nconsists of files, options, routines located in the A7R namespace, which\ncomprises the utilities used to consolidate the data extracted from the\nVISTA applications.\n \n The actual distribution of the application is sectioned into two builds.\nOne is the NDBI PRIMARY SYSTEM, consisting of all NDBI files, A7R*\n\n
\nSee Patch Description for details.\n\n
\nThis patch contains 2 enhancements and date error checking.\n\nThis patch contains enhancements requested by union representatives to assure\nthat employees have read and understood the employee bill of rights and to \nsend a bulletin to the union with additional incident information provided the\nemployee has provided their consent.\n\n
\nThis patch contains the enhancements required to implement the Needlestick\nAct (HR 5178) in ASISTS.\n\n
\nThis patch contains changes to the OOPS DOL MANUAL XMIT DATA, \nASISTS OWCP CHARGEBACK CODES File(#2263.6) and National Data Base \ntransmission routines OOPSNDB and OOPSNDBX.\n\n
\nEditing and Address Issues\n\n
\nPRINTING ISSUE\n\n
\nModifcations for the National Database project as well as modifications \nneeded to implement the NDB project reporting requirements and other \nNOIS and E3R's\n\n
\nPrint Log from Union Menu Correction\n\n
\nMultifacility Enhancements\n\n
\nThis patch contains modifications for the Electronic submission of CA1/CA2\nClaims to the Department of Labor (DOL) via the Austin Automation Center (AAC).\nThis is patch OOPS*1.0*8\n\n
\nDOL TYPE, SOURCE AND CAUSE CODES UPDATES\n\n
\n \nThis patch will fix reporting errors with the OSHA 300 Log report\nand the OSHA 300A Summary report.\n\n
\nThis patch contains new privacy act functionality identified by the\nASISTS customer, required modifications to the CA-7, and minor bug fixes.\n\n
\nThis patch provides a fix to transmission errors received from Austin. \n\n
\nThis patch contains one modification to adhere to a business rule with\na package that is external to ASISTS that was not exposed until after \nOOPS*2*15 was released. ASISTS will now include individuals in the\nlookup when a case is created if the termination date (NEW PERSON \nFile #200, TERMINATION DATE Field #9.2) is blank or contains a date \nequal to the current or a future date.\n\n
\nThis patch contains a modification to address an issue with the OSHA\n300 Log. A field has been added to collect data that will\nused to populate Column F in the OSHA 300 log. This will enable\nfacilities to have complete control over information in that field\nto eliminate OSHA citations.\n\n
\n1) E-Sig not on Printed Dual Benefits\n2) Report of incident is adding a year to the age. DOB is correct\n3) Cannot select current SECONDARY SUPERVISOR.,\n4) Employee information disappears\n5) Fields populated that should not be populated.\n6) NOI code Garbled when printing CA1\n7) Field exceeds max length error\n8) Time showing incorrectly on print of CA1 form\n9) Problem signing CA1 form for employee\n\n
\nThis patch fixes the potential for an undefined error when an employee\ndoes not have a hire date and updates the ASISTS OWCP CHARGEBACK CODES\nfile (#2263.6) with four new entries. \n\n
\nThis patch fixes the following issues:\n \n1) Allow the OWCP CHARGEBACK SUFFIX field (#.8) field to\n except numeric values\n2) Issue's with classifying Incident outcome\n3) Death is not checked on OSHA300 Report\n4) Fix misleading description on the "Reason for Controvert \n Report" and the "Reason for Dispute Report"\n\n
\nThis patch addresses an issue where a user with a 4 digit DUZ cannot\nClassify Incident Outcome.\n\n
\nThis patch updates the ASISTS OWCP CHARGEBACK CODES file (#2263.6) with\none new entry. \n\n
\nINSTITUTION FILE AND ACCUMAX CONTENTION FIXES\n\n
\nThis patch addresses the following:\n \n-Issues displaying Stations on the "Edit Site Parameter" form \n-Incident Outcome display order problems\n-OSHA 300 "Away From Work" and "Job Transfer/Restriction" calculation\n issues \n\n
\nThis patch fixes the following issues:\n \n1) Total Days Issue\n2) Save Location of Injury detail edits\n3) Incident Report Location of Injury availability\n\n
\nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the ASISTS Graphical User Interface (GUI) requires an \nupgrade to Delphi version XE8 in order to implement the new Remote \nProcedure Call (RPC) Broker allowing compliance.\n\n
\nThis patch fixes issues when running the "Display Incidence Rates \nWorksheet" option where the "Start Year" and "End Year" do not \nallow selection of 2017 dates.\n\n
\nWhen attempting to update OSHA 300 Summary Data in ASISTS adding new\nentries is supposed to select the next month and year in sequence, \nbut depending on the year of the currently selected record, the\nyear can be set to a previous year. Also, ASISTS does not enforce\nthe date restrictions when editing of OSHA 300A Summary if the\ncurrent month is January or February.\n\n
\nMenu's to be disabled that are no longer needed after the decommissioning\nof ASISTS (Automated Safety Incident Surveillance and Tracking System)\n\n
\nPatch OOPS*2*33 addresses an issue where OOPS tasks are still \nscheduled at certain sites\n\n
\nASISTS Enhancements and NOIS fixes\n\n
\nBug fix for the Log of Needlestick Incidents Option.\n\n
\nThis build contains minor bug fixes and enhancements requested by the ASISTS\nTAG. These enhancements include the ability to select Stations from a 'short'\nlist, make it easier to select the Body Part Most Affected, enter a 2\ncharacter extension to the OWCP Chargeback code, modifications when a claim\nis controverted, have the ability to enter and sign a Dual Benefits form, \nenter and sign a CA-7 Request for compensation form, and run a new report \nbased on the response to the Filing Instructions field (File 2260, Field 174).\n\n
\nThis build contains enhancements requested by the ASISTS TAG to implement\nthe Occupational Safety and Health Administration (OSHA 300) Log and minor\nbug fixes and NOIS.\n\n
\nDecommission designated ASISTS roll and scroll menu options.\n\n
\nThe purpose of this patch is to provide minor enhancements to the Occupational Safety and Health\n Administration (OSHA) 300 Log which was\n implemented in OOPS*2.0*7. This patch\n will also address other miscellaneous\n minor enhancements, reported and\n unreported bug fixes.\n\n\n
\nThis patch provides an update to file 2263.6 ASISTS OWCP CHARGEBACK CODE.\n\n
\nASISTS - VERSION 2.0\n\n
\nA null subscript error was reported when trying to run several of the\nreports under the option VIST ROSTER SORTS. This patch will correct this\nproblem.\n\n
\nTransmit AMIS report electronically.\n\n
\nAn incomplete data set was being displayed in the VARO Report. An error\nwas found in the routine ^ANRVRP9 that caused this problem. This patch\ncontains a fix to this routine.\n\n
\nThis is the Patch for Version 4.0 of Patient Reviews.\n\n
\nThis patch fixes the problem with the NEXT button on the last page of section 3 of the GUI client.\n\n
\nVisual Impairment Service Team (VIST) V 4.0.\n\n
\nSee patch ANRV*5*1 in the National Patch Module for complete information \non this patch.\n\n
\nThis build contains the routines, options and rpc's necessary for the \nBlind Rehabilitation/VIST V5.0 Java software.\n\n
\nThe Blind Rehabilitation System (BRS) is a VHA-wide application used to \n -Migrate the BRS application to the VA Enterprise Cloud (VAEC).\ntrack and manage the delivery of care to visually impaired patients.\n \nThe purpose of this patch:\n -Re-engineer the BRS application for compliance with VA \n Technical Reference Model (TRM) and secure coding standards.\n -Release the new version of BRS to production for use by VA \n staff with Two Factor Authentication (2FA) \n capability.\n\n
\nA database file of Visual Impairment Services Team (VIST) patients\nat this VA facility.\n\n
\nThis patch fixes several reported bugs. Please see the patch description\nfor WV*1*3 on FORUM for a full description of this patch.\n\n
\nPlease read the WV*1*13 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*14 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*12 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*15 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*17 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*16 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nDUZ undefinied fix in WVRALINK\n\n
\nThis patch replaces the full SSN with the last 4 digits of the SSN\nfor the generic letter in Women's Health (790.6) and for each of the\nnotification letters in file 790.404.\n\n
\nReplace CPT codes in file 790.2 for ones that have been inactivated.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder WV*1.0*23.\n\n
\nPlease read the WV*1*4 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nThis patch is a VM patch that addresses 2 issues in the Women's Health\npackage.\n \n1. No alert to case manager for PAP supplementary reports\n \n2. Errors when reports are sent to Women's Health package\n\n
\nThis patch modifies the Women's Health package to improve monitoring of \nfor installation instructions.\nhigh risk medcations prescribed or administered to women of childbearing\nage or women who are lactating. Specifically, the software now tracks a\nwoman's pregnancy and lacation status and notifies providers of changes in\nthese statuses. These statuses are used during order checking to remind \nproviders about the potential harm of such medications.\n \nPlease see the accompanying patch description for details and the \nComputerized Patient Record System (CPRS) version 31.b installation manual\n\n
\nThis patch modifies the Women's Health package to improve monitoring of \nfor installation instructions.\nhigh risk medcations prescribed or administered to women of childbearing\nage or women who are lactating. Specifically, the software now tracks a\nwoman's pregnancy and lacation status and notifies providers of changes in\nthese statuses. These statuses are used during order checking to remind \nproviders about the potential harm of such medications.\n \nPlease see the accompanying patch description for details and the \nComputerized Patient Record System (CPRS) version 31.b installation manual\n\n
\nPlease see forum for a complete description of patch WV*1.0*29\n\n
\nPlease refer to the patch description for detailed information about the \ncontents.\n\n
\nPlease see forum for a complete description of patch WV*1.0*30.\n\n
\nPlease read the WV*1*5 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*6 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*7 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*7 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*9 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*10 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nPlease read the WV*1*11 patch description on FORUM for an explanation of\nwhat this patch does.\n\n
\nThis KIDS Build contains all the components needed to install the Women's\nHealth v1.0 software package.\n\n
\nThis patch corrects the undefined errors in the Duplicate Record\n \nAssociated NOISs\n ================\n MAR-1098-21715\n BRX-1198-10261\nStatistics [RGCIRN CMOR DUP STATS] and the null subscript error in the\nPseudo-SSN Report [RGPR PRE-IMP SSN REPORT] option. This patch also\nincorporates changes to the Start/Restart CMOR Score Calculation [RGCIRN\nCMOR START] and CMOR Score Calculation Status [RGCIRN CMOR STATUS] options\nas well as changes to reduce the time of calculation. The CMOR INIT\nSTATUS field (#24) in the CIRN SITE PARAMETER file (# 991.8) was also\nupdated to reflect the changes in the CMOR Score Calculation Status\n[RGCIRN CMOR STATUS] option.\n\n
\nSee Forum Patch RG*.5*2 for a complete description.\n\n
\nSee FORUM Patch RG*.5*3 for a complete description.\n\n
\nThe Clinical Information Resource Network (CIRN) Pre-implementation\nsoftware Version 0.5 software calculates the CIRN Master of Record (CMOR)\nscores and also provides utilities for the cleanup of potential problem\nSSNs and Eligibility Codes.\n\n
\n CMOR SCORE CALCULATION STATUS OPTION\n Refer to patch RG*1*2 in the FORUM Patch Module for a complete\n description.\n\n
\nMPI/PD EXCEPTION MESSAGE SCREENING\nRefer to patch RG*1*11 in the FORUM Patch Module for a complete\ndescription.\n\n
\nRGDRM01 ERROR IN MERGE\nRefer to patch RG*1*10 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI/PD-CPRS REMOTE DATA VIEWS CORRECTION\nRefer to patch RG*1.0*14 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI/PD-CPRS REMOTE DATA VIEWS CORRECTION\nRefer to patch RG*1.0*15 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCIRN EXCEPTION HANDLING ENHANCEMENTS\nRefer to patch RG*1*12 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI/PD STATUS DISPLAY\nRefer to patch RG*1*16 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI EXCEPTION HANDLER\nRefer to patch RG*1*13 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOVE REFERENCES TO EXTENSIBLE EDITOR\nRefer to patch RG*1*18 in the FORUM Patch Module for a complete\ndescription.\n\n
\nINVALID DATE LAST TREATED EXCEPTION MESSAGES & HL7 MESSAGE ROUTING\nENHANCEMENT\n \nRefer to patch RG*1.0*17 in the FORUM Patch Module for a complete\ndescription.\n\n
\nGENERIC VA HL LINK\nRefer to patch RG*1*22 in the FORUM Patch Module for a complete\ndescription.\n\n
\nEXCEPTION MESSAGE ENHANCEMENTS\nRefer to patch RG*1*1 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI/PD UPDATE MENU STRUCTURE\nRefer to patch RG*1*19 in the FORUM Patch Module for a complete\ndescription.\n\n
\nADD/EDIT POINT OF CONTACT & MPI/PD HL7 DIAGNOSTIC MENU\nRefer to patch RG*1*21 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOTE DATA QUERY FEATURES\nRefer to patch RG*1*23 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCORRECTION FOR POINT OF CONTACT OPTION\nRefer to patch RG*1*24 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOTE PROCEDURE CALLS AND MISC. FIXES\nRefer to patch RG*1*25 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNEW MESSSAGE STRUCTURE - PHASE 1\nRefer to patch RG*1*26 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNEW MESSAGE STRUCTURE - PHASE 2\nRefer to patch RG*1*27 in the FORUM Patch Module for a complete\ndescription.\n\n
\nDUPLICATE A03 MESSAGES\nRefer to patch RG*1*28 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCLASS III UTILITIES CHANGED TO CLASS I\nRefer to patch RG*1*20 in the FORUM Patch Module for a complete\ndescription.\n\n
\nUTILITY REFINEMENTS & FIXES FOR NOIS\nRefer to patch RG*1*30 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCIRN EXCEPTION HANDLING OPTION\nRefer to patch RG*1*3 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch fixes a problem in the MPI/PD Exception Purge option. It was \nnot purging old exceptions that had no EXCEPTION STATUS field (#6) \ndefined. The post-install routine also purges old exceptions that have no\ncompletion date STOP field (#1.5) of the CIRN HL7 EXCEPTION LOG file\n(#991.1).\n\n
\nMONITORING, PDAT & ZPD SEGMENT\nRefer to patch RG*1*31 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNEW MESSAGE STRUCTURE - PHASE 3\nRefer to patch RG*1*29 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch addresses NOIS HAM-1203-22022 'User name backwards on MPI \nbulletin'. The Remote Sensitivity Indicated bulletin was displaying the \n<first name,last name> instead of <last name,first name>.\n\n
\nREMOVE 'TEST' PATIENT SCREEN - MPI CHANGES ITERATION 2\nRefer to patch RG*1.0*35 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOTE QUERY FAILS DUE TO BOGUS SSN\nRefer to patch RG*1.0*37 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch modifies the RGDRM01 routine to NEW the DIQUIET variable.\n\n
\nModify Name edit in Exception Handler to use Name Components.\n\n
\nAdd Exception Text to Exception Handler display.\n\n
\nMPI REMOTE QUERY FOR STATISTICS REPORT\nRefer to patch RG*1*41 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCPRS REMOTE DATA VIEWS\nRefer to patch RG*1*4 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCHANGE TO HL7 ADT-A24 AND ADT-A43 MESSAGE PROCESSING\nRefer to patch RG*1*42 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPOPULATING MORE FIELDS IN ZEL SEGMENT\nRefer to patch RG*1*40 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOVE SINGLE PATIENT INITIALIZATION\nRefer to patch RG*1*43 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch resolves a problem with the PATIENT AUDIT FILE PRINT [RGMT AUDIT \nPRINT] when tasking the job. \n\n
\nMPI CHANGES 3 & MPI CHANGES 4 ENHANCEMENTS\nRefer to patch RG*1.0*45 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPROCESSING PRIMARY REVIEW REJECT EXCEPTIONS\nRefer to patch RG*1*44 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI MESSAGING ENHANCEMENTS\nRefer to patch RG*1*47 in the FORUM Patch Module for a complete\ndescription.\n\n
\nEXCEPTION HANDLER ENHANCEMENTS\nRefer to patch RG*1*48 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nPRIMARY VIEW REJECT EXCEPTIONS\nRefer to patch RG*1*50 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nFAILED RPC RESULTS IN 'PLEASE CHECK BACK LATER' MESSAGE\nRefer to patch RG*1*53 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSTOP ADDRESS UPDATES\nRefer to patch RG*1*7 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch retires the Patient Data Review (PDR) functionality.\n\n
\n \nDATE OF DEATH BULLETINS/EXCEPTIONS\nRefer to patch RG*1*52 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch will make corrections to the Remote Patient Data Query Menu\n[RG REMOTE PDAT MENU].\nIt will also provide a report for patients that have invalid phone \nnumbers in the PHONE NUMBER [RESIDENCE] field(#.131) of the \nPatient file(#2).\n\n
\n \nDELETION OF PSEUDO SSN REASON\nRefer to patch RG*1*54 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nIDENTITY MANAGEMENT ISSUES FOR HDR II / CDS\nRefer to patch RG*1*51 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOVE POTENTIAL MATCHES RETURNED EXCEPTION REFERENCES\nRefer to patch RG*1*57 in the FORUM Patch Module for a complete\ndescription.\n\n
\nVISTA UPDATE CAN ERROR WHEN CMOR FIELD IS NULL\nRefer to patch RG*1*58 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMESSAGING ENHANCEMENTS FOR NEW FIELDS\n \nRefer to patch RG*1*59 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 10\nRefer to patch RG*1*60 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 12\nRefer to patch RG*1.0*61 in the FORUM Patch Module for a complete \ndescription.\n\n
\nFACILITY INTEGRATION MESSAGE\nThis patch contains functionality for processing the new Facility \nIntegration Message used during National Database Integration (NDBI)\nsite integrations. Refer to patch RG*1*5 in the FORUM Patch Module\nfor a complete description.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 13\nRefer to patch RG*1.0*62 in the FORUM Patch Module for a complete \ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 14\nRefer to patch RG*1.0*63 in the FORUM Patch Module for a complete \ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 15\nRefer to patch RG*1.0*64 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 / RELEASE 2\nRefer to patch RG*1.0*65 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - VIP 1\nRefer to patch RG*1.0*66 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - 'PREFERRED NAME'\nRefer to patch RG*1.0*67 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - 'DATE OF DEATH'\nRefer to patch RG*1.0*68 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - NOTIFICATION PROVIDER\nRefer to patch RG*1.0*69 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - MVI SENSITIVITY\nRefer to patch RG*1.0*70 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - SUPPORT LONG NAMES IN VA MPI\nRefer to patch RG*1.0*71 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSENDING FACILITY FORMAT / EXCEPTION MESSAGES\nRefer to patch RG*1*8 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - INPATIENT NAME UPDATES\nRefer to patch RG*1.0*72 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - DATE OF DEATH UPDATES\nRefer to patch RG*1.0*73 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - HAC SUPPORT \nRefer to patch RG*1.0*74 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - NEW DEMOGRAPHIC FIELDS\nRefer to patch RG*1.0*76 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - SEXUAL ORIENTATION UPDATES\nRefer to patch RG*1.0*77 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ENTERPRISE USER IDENTITY\nRefer to patch RG*1.0*75 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - POB HL7 UPDATES\nRefer to patch RG*1.0*78 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCIRN AWARE DUPLICATE RECORD MERGE\nRefer to patch RG*1*6 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNASHVILLE/MURFREESBORO NDBI/MPI CLEANUP\nRefer to patch RG*1*9 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis build contains various messaging support components required by both the \nclinical and demographic builds. It includes support for the following.\n \n1) Event Queue\n2) Exception Logging\n3) Subscription Services\n\n
\nClinical Information Resource Network (CIRN)\n\n
\nResource Usage Monitor Version 1.0 install.\n\n
\nPatch 1 for RUM v2.0\n\n
\nPatch KMPR*2*2\n\n
\nRUM V2.0\n\n
\nThe Resource Usage Monitor (RUM) is a component of Capacity Management's\nsuite of monitoring tools.\n\n
\nThe pre-init routine will change the name in the package file from\nas obsolete and will be eliminated in a future release (no sooner \nthan one year after the release date for this version). The routines \nare:\n \nRGCVTDT Call $$^RGCVTDT replaced by $$ENTRY^RGUTDT; same arguments\nRGCVTUU Replaced by RGUTUU; same entry points\nRGINIT* Replaced by RGUTIN*\nRGMSCALR Replaced by RGUTALR; same entry points\nRGMSCDAT Replaced by RGUTDAT; same entry points\nRGMSCDIC Call $$^RGMSCDIC replaced by ENTRY^RGUTDIC; same arguments\nCIRN RUN TIME LIBRARY to RUN TIME LIBRARY if it already exists in \nRGMSCEDT Replaced by RGUTEDT; same entry points\nRGMSCIMP Replaced by RGUTIMP; same entry points\nRGMSCLK* Replaced by RGUTLK*; same entry points\nRGMSCMTL Replaced by RGUTMTL; same entry points\nRGMSCTSK Replaced by RGUTTSK; same entry points\nRGMSCUSR Replaced by RGUTUSR; same entry points\nRGXY $$^RGXY replaced by $$XY^RGUT; same arguments\nRGZOSF* Replaced by RGUTOS*; same entry points except for \n elimination of math functions.\nthe file.\n \nThis is the set of routines common to all modules occupying the RG namespace. \nThey perform generic functions. \n \nIn this release of the runtime library, several routines have been \nrenamed under the RGUT subnamespace. The original routines are marked \n\n
\nThis patch provides updates for the FileMan Delphi Components (FMDC). FMDC\n Changes include making most procedures and functions protected instead\n of private, and referring to components by type rather than name.\n- NOIS issue LOM-0799-60075 is corrected (server side error due to a\n string length problem).\n- FMCheckBox components' display of retrieved null values as grayed-out\n checked values is corrected. It now displays them as unchecked. An\n invalid non-null text value will still appear as the grayed-out checked\n value.\n \nTHIS SOFTWARE DISTRIBUTION INCLUDES THE SOURCE CODE FOR THE COMPONENTS.\nis used by developers to access VA FileMan data from client RPC\nWHILE THE SOURCE CODE HAS BEEN PROVIDED, IT SHOULD NOT BE ALTERED\nDIRECTLY. IF AN ADDITIONAL FUNCTIONALITY IS NEEDED, DERIVE A COMPONENT\nBASED ON AN EXISTING COMPONENT INSTEAD, TO PROVIDE THAT FUNCTIONALITY. IF\nYOU THINK IT WOULD BE USEFUL TO A WIDE AUDIENCE, THEN SEND A SAMPLE TO\nTSOPENVISTA@DOMAIN.EXT.\n \nWhile this patch provides only provides code changes for developer's\nclient workstations, a build also is included for the server side so that\nthe patch number will appear in the package file. This build should be\ninstalled on the server simply to insure that the patch is noted as\nBroker-based applications.\ninstalled.\n \nThe software distribution includes:\n \nFILE NAMES DESCRIPTION Blocks Bytes\nFMDC1_0P1.EXE FMDC Self-Installing Executable 1894 969709\nFMDC1_0P1IG.PDF Installation Guide 146 74560\nFMDC1_0P1TM.PDF Technical Manual 71 36305\n \nNote: Use Binary mode for .PDF, and .EXE files\n \n \nUse FTP to retrieve the software from one of the following CIO Field\nOffices' ANONYMOUS.SOFTWARE directories:\n \n CIO FIELD OFFICE FTP Address \n Hines 152.129.1.110 isc-chicago.domain.ext\n Albany 152.127.1.5 isc-albany.domain.ext\n Salt Lake City 152.131.2.1 isc-slc.domain.ext\n \n \nThis patch provides the following enhancements and fixes:\nINSTALLATION:\n \nServer Side:\n============\n \n1. Installing this patch has no impact on users on the system. It can be\n installed at any time.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. Use this\n option to load the FMDC KIDS (Kernel Installation and Distribution\n \n System) build for this patch into a transport global on your system.\n \n3. Once the FMDC KIDS build for this patch has been loaded into a\n transport global on your system, on the KIDS menu use the following\n option to install the patch:\n Install Package(s) 'FMDC*1.0*1'\n ==========\n \nClient Side (Developers only):\n=============================\n- Delphi 4 support is now provided (in addition to Delphi 3)\n \nThe client side distribution should only be installed on workstations of\ndeveloper who wish to use FMDC. To install, please follow the installation\ninstructions in the most recent FileMan Delphi Components (FMDC)\nInstallation Guide (an updated Installation Guide is provided as part of\nthis patch).\n- Source code is now provided for the FMDC components\n- You can now derive custom components based on the FMDC components.\n\n
\nThis patch provides a FMDC1_0RM.TXT (7,024 bytes) file for the FileMan\n Hines 152.129.1.110 isc-chicago.domain.ext\n Albany 152.127.1.5 isc-albany.domain.ext\n Salt Lake City 152.131.2.1 isc-slc.domain.ext\n \n \nINSTALLATION:\n \nServer Side:\n============\n \nDelphi Components (FMDC). The readme file provides important information\n1. Installing this patch has no impact on users on the system. It can be\n installed at any time. The packman simply updates the Version multiple\n in the Package file.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. Use this\n option to load the FMDC KIDS (Kernel Installation and Distribution\n System) build for this patch into a transport global on your system.\n \n3. Once the FMDC KIDS build for this patch has been loaded into a\n transport global on your system, on the KIDS menu use the following\non how to recompile FMDC whenever a new RPC Broker Development Kit (BDK)\n option to install the patch:\n Install Package(s) 'FMDC*1.0*2'\n ==========\nis installed.\n \nUse FTP (ascii mode) to retrieve the file from one of the following\nCIO Field Offices' ANONYMOUS.SOFTWARE directories:\n \n CIO FIELD OFFICE FTP Address \n\n
\nVistA Imaging v 2.5 routines modified to correct bug fixes identified by\nImaging namespace database.\n \nRoutines:\nMAGQBPG2, MAGQBPRG, MAGQBUT1, MAGQBUT2\n \nData Dicitonary change to file 2006.1 on field #21, PURGE-RETEN DAYS PACS\nBIG FILE - input transforms code changed and is required by the background\nprocessor.\nInput transform was: \n^DD(2006.1,21,0)=PURGE-RETEN DAYS PACS BIG\nNOIS reports and during final release process.. \nFILE^NJ5,0^^3;1^K:+X'=X!(X>99999)!(X<1)!(X?.E1"."1N.N) X\nInput transform is now:\n^DD(2006.1,21,0)=PURGE-RETEN DAYS PACS BIG\nFILE^NJ5,0^^3;1^K:+X'=X!(X>99999)!(X<0)!(X?.E1"."1N.N) X\n \n \n \nRoutine check sum values:\nMAGDLB1 value = 12440903\nMAGDLB9 value = 4213608\n \nMAGDLBSR value = 5424331\nMAGDRA1 value = 6988221\nMAGQBPG2 value = 7018812\nMAGQBPRG value = 9377201\nMAGQBUT1 value = 13490806\nMAGQBUT2 value = 5019592\nMAGUSIT value = 15207655\nRoutines:\nMAGDLB1, MAGDLB9, MAGDLBSR, and MAGDRA1 are required to fix undef problems\nafter install Radiology patch 26. \n \nRoutines:\nMAGQBUT and MAGUSIT - routines for synchronizing the namespace with\n\n
\nThis patch identifies possible integrity problems in the Imaging and\nNAME: MAG DB IQ\n MENU TEXT: Imaging Database Integrity Checker Menu\n TYPE: menu CREATOR: BARRIOS,LUCILLE\n PACKAGE: IMAGING\n DESCRIPTION: Menu optons to start the scanning of the Imaging database.\nITEM: MAG_IC_RPT_GM SYNONYM: GM\nITEM: MAG_IC_RPT_QA SYNONYM: QA\nITEM: MAG_IC_SCAN SYNONYM: SC\n TIMESTAMP: 58681,42457\n UPPERCASE MENU TEXT: IMAGING DATABASE INTEGRITY CHE\nassociated parent report files.\n \n \nNAME: MAG_IC_RPT_GM\n MENU TEXT: Integrity Report on Global Moves\n TYPE: run routine CREATOR: BARRIOS,LUCILLE\n PACKAGE: IMAGING\n DESCRIPTION: Report from Imaging Integrity Check, limited to items\nrequrired\n for Central Office.\n ROUTINE: RPT^MAGICRPT("CO")\n \n UPPERCASE MENU TEXT: INTEGRITY REPORT ON GLOBAL MOVE\n \nNAME: MAG_IC_RPT_QA\n MENU TEXT: Comprehensive Image Integrity Report\n TYPE: run routine CREATOR: BARRIOS,LUCILLE\n PACKAGE: IMAGING\n DESCRIPTION: Report from Imaging Integrity Check, including all items\n required for Quality Assurance.\n ROUTINE: RPT^MAGICRPT("QA")\n UPPERCASE MENU TEXT: COMPREHENSIVE IMAGE INTEGRITY\nRoutines included:\n \nNAME: MAG_IC_SCAN\n MENU TEXT: Scan Database for Integrity Issues\n TYPE: run routine CREATOR: BARRIOS,LUCILLE\n PACKAGE: IMAGING X ACTION PRESENT: YES\n DESCRIPTION: Menu option to scan the Imaging database.\n EXIT ACTION: K MAGN100,MAGZ,VALID ROUTINE: RPT^MAGGSQI()\n UPPERCASE MENU TEXT: SCAN DATABASE FOR INTEGRITY IS\n \nMAGGSQI value = 20833776\nMAGICRPT value = 16785993\n \nMenu options exported:\n\n\nBuild for MAG*2.5*4 patch. \nselection of an existing TIU note for the patient whose images are being\ncaptured. If a selection was made on a non-existing note then the "OK"\nbutton on the display will be disabled, leaving only the Cancel or Help\nbutton for possible selection. \n \nContains the following routines:\n \nMAGGNTI value = 9207655\nMAGGTIA value = 10457801\nMAGGTIA2 value = 4308773\n \nMAGGTIG value = 11774320\nMAGGTII value = 5456481\nMAGGTRAI value = 8632417\nMAGGTRPT value = 11812366\nClinical workstation software has been modified to block the display of\nimages which areOn of Quiestionable Integrity (QI) due to possible\nmiss-associated images on the database.\n \nA further prevent mechanism has been added to the workstation capture\nsoftware to disable accidental attachment of an image for one patient to\nan existing TIU note of another patient. The software will require the\n\n
\nImaging patch for Patient Safety; this patch will block the display of\na null value for the DFN variable.\n \nRoutine MAGIPOS5 is a post routine and will be deleted at the end of the\nKIDS install. \n \nMAGBAPI value = 6095017\nMAGCRPT value = 17451573\nMAGGNTI value = 9279191\nMAGGSQI value = 21289551\nMAGGTIA value = 10453678\nassociated Radiology reports if the image entry has a questionable\nMAGGTIA2 value = 5246980\nMAGGTIG value = 11875351\nMAGGTII value = 6127443\nMAGGTRA1 value = 5798386\nMAGGTRAI value = 8956338\nMAGGTRP1 value = 6036421\nMAGGTRPT value = 12087508\nMAGIPOS5 value = 29453\nMAGQBPG1 value = 11417193\nMAGQBUT2 value = 15103200\nintegrity issue. The Verifier software has been modified to perform a\ndatabase integrity check on all Image file entries as well as verify image\nfile migration. It also allow integrity checking of the TEXT files and the\nsorting mechanism has been modified to allow more flexibility.\n \nRoutine MAGICRPT is being deleted and a new routine MAGCRPT has been\ncreated to do database scanning; this routine has been corrected to handle\n\n
\nHealth Eligibility Center patch implementing the generic carbon copy \nMAGGTU3 value = 7687105\nMAGIPOS8 value = 2442231\nMAGQBGCC value = 5450619\nMAGQBTM value = 13283746\nMAGQBUT1 value = 13532907\nMAGQBUT2 value = 15123710\nutility.\n \n \nRoutines:\n \nMAGBAPI value = 5940348\nMAGGSPP value = 3239627\nMAGGTAU value = 9198237\n\n
\nVISTA Imaging V 2.5. This build includes all files required\nfor a complete installation.\n \nInformation on VistA Imaging is available on web page\nhttp://vawww.domain.ext/imaging/\n\n
\n \nThis patch includes the following:\n \nEKG enhancements\nThin Client and Display settings check\nScanned Document default is now 300x300\n \nMAGGTU6 value = 5589547\nMAGIPS24 value = 5023772 (Deleted at install)\n\n
\nVersion 3.0 Patch 142 - Site IEN / Station Number Issue/\ninstalled.\n \n \nRoutines:\nMAGDPRCA new value = 98101426\nMAGIP142 new value = 4110380\nMAGVAG03 new value = 76377975\n \nPlease note that routine MAGIP142 is deleted after the KIDS Build is\n\n
\nPatch 150 is a patch to complete the Image Never Existed fix that\nThis Patch modifies 6 routines.\nThe RPC that returns a list of Patient images is changed. \nNow, images with the status 'Image Never Existed' will not be \nlisted with the Deleted Images of a patient.\nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*150 IMAGING\nMAGGI12 value = 101869499\nMAGGTAU value = 66990261\nMAGGTID value = 85911502\nMAGGTIG value = 61207085\nwas started in Patch 129 and Patch 135\nMAGIP150 value = 4214952\nMAGLOG value = 12957603\nMAGSIXG3 value = 84985360\ndone\n \nIMAGE File (#2005) entries that are deleted when the process to copy the \nfile to the Image Share (Tier1 Storage) and considered \n'Image Never Existed'. \nThe Display Client will list these images as 'Deleted' images. \nThis gives the provider the false impression that a relevant image may\nhave been associated with the Patient Record.\n\n
\nVersion 3.0 Patch 154 BACKGROUND PROCESSOR\n\n
\nVersion 3.0 Patch 156 - DICOM GATEWAY PATCH\nMAGDRPC8 = 64614729\nMAGGTU4D = 5715984\nMAGIP156 = 4110424\nMAGT7SO = 37886120\nMAGVORDR = 29838762\nMAGVRS52 = 26599737\n \n \n \nRoutines:\nMAG7UCFG = 21999763\nMAGBRTE4 = 74048747\nMAGDHOW2 = 48253924\nMAGDRPC4 = 99627815\n\n
\n \n \n \nPlease note that routine MAGIP157 is deleted after the KIDS Build is \ninstalled\nVersion 3.0 Patch 157 VIX AND HDIG PATCH\n \n \n \nRoutines:\nMAGIP157 = 4110433\nMAGROI01 = 22645329\nMAGVRD02 = 15760745\n\n
\n \n \n \nPlease note that routine MAGIP160 is deleted after the KIDS Build is \ninstalled\nVersion 3.0 Patch 160 HDIG 64-bit compatible\n \n \n \nRoutines:\nMAGIP160 value = 4110378\n \n \n\n
\nVistA Imaging V3.0 Patch 161 - Patch 138 Follow Up\nThis patch is also to be installed After Patch 156.\n \nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*161 IMAGING\nMAGDRPC8 value = 64895858\nMAGGTU4D value = 5312177\nMAGIP161 value = 4214969\ndone\nPatch 161 is the Patch 138 (MegaPatch) follow up.\nIt includes : \n - Patch 130 Display Client (Harris patch)\n - Patch 149 Display Client (Mantech/7Delta patch)\n - Fix for Radiology Images that don't display in RadViewer.\n - Fix to correctly upload SCU_LIST.DIC changes to VistA.\n - - - - \nThis patch is to be installed After Patch 138.\n\n
\nVistA Imaging V3.0 Patch 158 - Import API OCX fix\n it will send a windows message to MagThumbnailMaker, wait for a \n response back, then terminate itself.\n This design will allow the BP to continue processing abstracts as\n it does now. no change to the BP application is needed.\n \n \n Checksums\nRoutine Old New Patch List\nMAGGSFT 8060991 12528057 **7,8,94,158**\nMAGIP158 n/a 4832681 **158**\n - This patch tests the Modified Import OCX, new MagThumbnailMaker.exe\n \nNote: routine MAGIP158 is deleted after the KIDS Build is installed.\n \ndone\n and new mag_MakeAbs.exe\n Import OCX has been modified to perform the Copy to Network in a back\n background thread. This enables the main thread to maintain \n connection to the VistA Server.\n MagThumbnailMaker.exe is a new abstract/thumbnail maker. It will\n be called by the new mag_MakeAbs.exe.\n mag_MakeAbs.exe has been changed. Instead of making the abstracts, \n\n
\nVistA Imaging V3.0 Patch 163 MAG INDEX TERMS UPDATE 2015\n \nAdd the existing Specialty: Hematology Medical to the existing Procedure/Event: Blood Component Form\n \n \nThis Patch includes 4 new index terms:\n \nNew Specialty: Diagnostic/Interventional Radiology Abbreviation: DIR\nNew Specialty: Radiation Oncology Abbreviation: RONC\nNew Origin: URBAN (active for IHS sites only)\nNew Specialty: Physical Therapy Abbreviation: PT (IHS only)\n\n
\nMiscellaneous fixes\nend of installation.\n \nRoutines:\nMAGDLB6 value = 3354488\nMAGGSIA value = 5811759\nMAGGTIA1 value = 6825885\nMAGIPS21 value = 2652995\n \nRoutine MAGIPS21 is a pre- and post-install routine. It is deleted at the\n\n
\n \nMAGVGUID value = 34583705\nMAGVRS61 value = 95250185\nMAGDQR72 value = 8819008\n \nPlease note that routine MAGIP162 is deleted after the KIDS build is \ninstalled \nVistA Imaging V3.0 - Patch 162 - Query retrieve\n \nRoutines:\nMAGDQR03 value = 217560028\nMAGDRPCA value = 80785193\nMAGIP162 value = 4110396\nMAGVAG03 value = 76869387\nMAGVCWIA value = 117974804\n\n
\nVistA Imaging V3.0 - Path 153 - VistARAD viewer issues\n \n \nRoutines:\nMAGJMN1 value = 98640707\nMAGJTU4V Value = 5207279\nMAGJUTL5 value = 38198826\n\n
\nVistA Imaging V3.0 Patch 173 - TELEPATHOLOGY Maintenance\n - This patch handles some Telepathology bug fix\n \nMAGIP173\nMAGT7MA\n \n 2 Routines \nNote: routine MAGIP173 is deleted after the KIDS Build is installed\n\n
\nVistA Imaging V3.0 Patch 174 - Modality Worklist\n - This patch handles Modality Worklist fixes\n \nMAGIP174\n \n \n 1 Routin \nNote: routine MAGIP174 is deleted after the KIDS Build is installed\n\n
\nVistA Imaging V3.0 Patch 168 - BACKGROUND PROCESSOR 2012 Windows Compliant\n - This patch tests the BP to ensure it works with Windows Server 2012\n \nMAGIP168 Calculated 4013698\nMAGQBUT Calculated 147442023\n \n 2 Routines \nNote: routine MAGIP168 is deleted after the KIDS Build is installed\n\n
\nVistA Imaging V3.0 Patch 151 - Scanning Enhancements\nOption to add Additional Images to an Existing Image Group.\nMore details included in the list of Patient Consults.\nTWAIN device sharing issues fixed.\nUnsigned Notes are now correctly displayed for a Patient.\nUser is no longer asked to select Patient for Lab Selection.\nDate/Time dialog correctly displays am/pm for selected time.\nOption to display Configuration Buttons on Top or Left of window.\nChanges to captured PDF images (rotate ) are now\nsaved correctly.\nAnnotations are no longer created in the Capture\n \napplication. Capture application now communicates with\nthe Display application. Starting with Clinical Display patch 167\nan annotation window will open automatically and enable\nthe user to annotate immediately after the image is\ncaptured. User can also select any image from the 'Latest\nPatient Images' window, and have that image open in the\nAnnotation window of Clinical Display\n \nPlease note that routine MAGIP151 is deleted after the KIDS Build is\ninstalled.\nPatch 151 has fixes for the Clinical Capture Client. \nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*151 IMAGING\nMAGGA03A value = 26454333\nMAGGNLKP value = 14768217\nMAGGTIG value = 77381599\nMAGGTU3 value = 35227017\nMAGGTU4C value = 5135697\nMAGIP151 value = 7810500\ndone\nSummary of the issues fixed:\nProgress Notes window has been modified to fix errors when\n returning a list of Patient Notes.\nIssues when Scanning Images as PDF files have been fixed\nAbstracts are now created for PDF files.\nSpecialty, Proc/Event values were incorrectly saved.\n\n
\nVistA Imaging V3.0 Patch 167 - Display Issues\nA new option on the Image Delete window will allow\nthe user to Copy the Image to the local hard drive\nbefore deleting. This will enable the user to \nimport the image to a new Patient or Re-Index the \nImage without the need to Print and ReScan. \n \nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*167 IMAGING\nMAGGTID value = 85911502\nMAGGTU4D value = 5313921\n \nMAGIP167 value = 11436109\nMAGSIXG3 value = 84985360\ndone\nThis Patch includes a new Clinical Display Client\nChanges in the Clinical Display client will address the\nupgrade to MUSE API 3.\nAlso, Clinical Capture users will be able to open images \nin a seperate window of Clinical Display for Annotation.\nThis patch also had fixes from patch 150 for the\nImage Never Existed issue.\n\n
\nVistA Imaging V3 - Patch 164 - DICOM Maintenance G\n \n \n \nNote: routine MAGIP164 is deleted after the KIDS Build is installed\nMaintenanceDICOM Maintence\nPatch 164 DICOM/IMPORTER Maintenance\n - This patch handles some bug fix\n \nRoutine: MAGVIM05\nRoutine: MAGVIM10\nRoutine: MAGVIMRA\nRoutine: MAGIP164\n\n
\nVistA Imaging Display with 2 factor authentication (2FA)\nAlso, at start up a splash screen will be displayed. The Splash screen\nwill remain visible while the application is being initialized and will \nclose when the application is ready for use.\n \nDelphi XE8 is the new developer environment used to build the application. \nIn XE8 the Character set has changed from 1 byte/character\nto 2 byte/character. The change in character set forced a change in\nsome of the functions that were used for manipulating character and \ncharacter strings. But there will be no visible change to the GUI and\nthe user will not see any difference in functionality. \nThis patch has 3 changes.\n \nRoutines.\nSelect BUILD NAME: MAG*3.0*181 IMAGING\nMAGGTU4D value = 5320928\nMAGIP181 value = 4214985\ndone\n2 small changes when the application starts, and a change to the version \nof Delphi used to build the application.\n \nThis patch implements 2 Factor Authorization for the Login to VistA. \nWhen logging into a VA Site, the user will be prompted for their\nPIV PIN number and not their Access Verify codes.\n \n\n
\nVistA Imaging TeleReader with 2 factor authentication (2FA)\n \nDelphi XE8 is the new developer environment used to build the application. \nIn XE8 the Character set has changed from 1 byte/character\nto 2 byte/character. The change in character set forced a change in\nsome of the functions that were used for manipulating character and \ncharacter strings. But there will be no visible change to the GUI and\nthe user will not see any difference in functionality. \n \nRoutines.\nSelect BUILD NAME: MAG*3.0*182 IMAGING\nThis patch has 3 changes.\nMAGGTU4T value = 4714251\nMAGIP182 value = 4214994\ndone\n \nThis patch implements 2 Factor Authorization for the Login to VistA. \nWhen logging into a VA Site, the user will be prompted for their\nPIV PIN number and not their Access Verify codes.\n \nStopped using CAPRI Silent logon method to Remote Sites and\nnow use BSE Silent logon method.\n\n
\n \nMAGDCCSS value = 5605002\nMAGDGMRC value = 8587567\nMAGDHW0 value = 4070033\nMAGDHWA value = 13363951\nMAGDHWC value = 10917214\nMAGDHWS value = 8433031\nMAGDLB6 value = 3354488\nMAGDLBSR value = 5467588\nMAGDRA1 value = 7630701\nMAGDRA2 value = 7852272\nRoutines required for capturing DICOM images for Consults and Procedures.\nMAGDRCU1 value = 8444320\nMAGDRCU2 value = 9677365\nMAGDROUT value = 5323100\nMAGGNTI value = 9622527\nMAGGTIA2 value = 7860990\nMAGIPS10 value = 5448905\nMAGSDEL2 value = 7540929\nMAGSDHCP value = 3713231\n \nPlease note that routine MAGIPS10 will be deleted after the KIDS Build is \n \ninstalled.\nRoutine checksums:\n \nMAGDCCS value = 12895252\nMAGDCCS2 value = 6369003\nMAGDCCS3 value = 3965440\nMAGDCCSD value = 4446663\n\n
\nVersion 3.0 Patch 179 - Importer/VIX 2FA\n \nVistA Imaging V3.0 - Patch 179 - Importer/VIX 2FA\n \nRoutine: MAGIP179\n \nPlease note that routine MAGIP179 is deleted after the KIDS build is\ninstalled.\n\n
\n>VistA Imaging Capture\nPIV PIN number and not their Access Verify codes.\n \nAlso, at start up a splash screen will be displayed. The Splash screen\nwill remain visible while the application is being initialized and will \nclose when the application is ready for use.\n \nDelphi XE8 is the new developer environment used to build the application. \nIn XE8 the Character set has changed from 1 byte/character\nto 2 byte/character. The change in character set forced a change in\nsome of the functions that were used for manipulating character and \n V3.0 Patch 178 - 2 Factor Authentication\ncharacter strings. But there will be no visible change to the GUI and\nthe user will not see any difference in functionality. \n \nRoutines.\nSelect BUILD NAME: MAG*3.0*178 IMAGING\nMAGGTU4C value = 5140530\nMAGIP178 value = 4256676\n \nThis patch has 3 changes.\n2 small changes when the application starts, and a change to the version \nof Delphi used to build the application.\n \nThis patch implements 2 Factor Authorization for the Login to VistA. \nWhen logging into a VA Site, the user will be prompted for their\n\n
\nVistA Imaging V3.0 - Path 184 2FA/SSOi VistARAD\n \n \nRoutines:\n \nMAGJTU4V Value = 5410256\nMAGJUTL5 value = 38266240\n\n
\nRoutines for Patch 170\n \nRoutines:\nMAGIP170 value = 4892918\nMAGNTRAI value = 76381648\n \nPlease note that routine MAGIP170 is deleted after the KIDS Build is\ninstalled.\n\n
\nRelease of Information(ROI) Print issues.\nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*191 IMAGING\nMAGGTU4D value = 5528535\nMAGIP191 value = 4214993\ndone\n \nThe issue happens when a user is processing a Release of \nInformation (ROI) Print job and the user switches patient's\nin CPRS while the ROI Print job is running.\n \nThis could potentially cause the Second Patient's images to be\nincluded in the ROI Print job that is running for the First Patient.\n \n\n
\n \nMAGTP005\nMAGVIM05 \n \n \n \n \n \n \nPlease note that routine MAGIP166 is deleted after the KIDS build is \ninstalled \nVistA Imaging V3.0 - Patch 166 LDGW\n \nRoutines:\n \nMAG7RS \nMAGBRTE3\nMAGIP166\nMAGT7MA\n\n
\n \ninstalled\nVistA Imaging V3.0 - Patch 172 T3 - Reject duplicated UID\n \nRoutines:\nMAGIP172\nMAGVUID\nMAGVRD03\n \nPlease note that routine MAGIP172 is deleted after the KIDS build is \n\n
\nVistA Imaging V3.0 Patch 186 - BACKGROUND PROCESSOR fix\n - This patch will fix the queue entry not found or left-over issue.\n - Also take care the Auto (schedule) Verifier not running (stop at IQ \nset) issue\n \nMAGQBUT2\nMAGQBPG1\nMAGQBTM\nMAGIP186\n\n
\nRoutines for Patch 177\n \nRoutines:\nMAGIP177 value = 4110449\n \nPlease note that routine MAGIP177 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging Capture 189\n \n3 - The List of patient consults for Teledermatology does not display\n This functionality stopped working in a previous patch. It is fixed in \n this patch. \n \nSelect BUILD NAME: MAG*3.0*189 IMAGING\nMAGGTU4C value = 5350343\nMAGIP189 value = 4256693\ndone\n1 - Synchronize Patient with CPRS when CCOW is not active on the Desktop\n This functionality stopped working in a previous patch. It is fixed in \n this version.\n \n2 - Duplicate Capture issue.\n When Capturing an Image to an image group, if user clicks on capture\n a second time \n The same image is captured twice. \n\n
\nRoutines for the Imaging Site Usage reports.\n \nRoutines:\nMAGDROUT value = 5343680\nMAGIPS36 value = 4705155\n \nPlease note that routine MAGIPS36 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 - P180 \n \n \n \n \nPlease note that routine MAGIP180 is deleted after the KIDS build is\ninstalled\n \nRoutines:\n \nMAGDHOW1\nMAGDHOW3 \nMAGDRPC3 \nMAGDRPC4 \nMAGDRPC9 \n\n
\nSend VistA patient demographic changes to PACS using ADT A08 (patient \ninformation update) and/or ADT A47 (change patient identifier list) HL7 \nmessages.\n\n
\nVistA Imaging V3.0 - P192\n \nRoutines:\nMAGIP192\n \n \nPlease note that routine MAGIP192 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 185\nMAGNID01 value = 5509538\nMAGNILOG value = 4853922\nMAGNISET value = 4965992\nMAGNTRAI value = 82064307\nMAGNVQ01 value = 109845219\nMAGNVQ02 value = 21293638\nMAGNVQ03 value = 37899553\nMAGNVQ04 value = 18123604\nMAGNVQ05 value = 6884375\nMAGNVQ06 value = 45830251\n \nMAGNPARM value = 14479373\nMAGNU001 value = 14211594\nMAGNU002 value = 5805654\nMAGNU003 value = 39650764\nMAGVAG05 value = 3394973\nMAGVIM08 value = 23870020\n \nPlease note that routine MAGIP185 is deleted after the KIDS Build is\ninstalled.\nRoutines:\nMAGIP185 value = 7630518\nMAGGTSYS value = 14702469\nMAGNAN01 value = 23870147\nMAGNAN02 value = 15238181\nMAGNAN03 value = 67374239\nMAGNAU03 value = 23753647\n\n
\nVistA Imaging Patch 196 - BackGround Processor (BP)\nhas been changed to be selectable.\nThis will enable the BP to process more Queues per minute.\nGUI enhancements for Resizing of Columns, and positioning\nof buttons, and edit boxes on various forms to be visable\nat all times.\nNetwork Location properties has been fixed. \nNetwork Locations of type URL can now be edited in the \nBP GUI.\n \nThis will check the routines from a BUILD file.\nThe development environment used to build this version \nSelect BUILD NAME: MAG*3.0*196 IMAGING\nMAGBRTE4 value = 76402670\nMAGIP196 value = 4237416\nMAGQBUT4 value = 97374409\ndone.\nof the Background Processor was updated to Delphi XE8\nChange to Patch Installation:\nWith the installation of this Patch 196, previous versions\nof the BP Client GUI will be able to logon to VistA.\nFixes : \nEVAL Queue count is fixed.\nThe BP has a forced delay between processing Queues. That delay\n\n
\nVistA Imaging V3.0 - Patch 206\n \nRoutines:\n \nMAGIP206\n \nPlease note that routine MAGIP206 is deleted after the KIDS build is\ninstalled.\n\n
\nMAG*3.0*188\nSelect BUILD NAME: MAG*3.0*188 IMAGING\nMAGGTSYS value = 27028795\nMAGGTU4D value = 5740596\nMAGGTU4M value = 22884338\nMAGIP188 value = 4692901\ndone\nThis patch will resolve the following issues for Clinical Display:\nThe ability to Show or Hide the Grid on the EKG Display and \nwhile printing.\nThe ability to select multiple EKG's for display and printing.\nThe ability for a site to change the Format ID that is used\nto generate the EKG Image.\nCT scrolling issue in the Radiology Viewer.\nThis will check the routines from a BUILD file.\n\n
\nVistA Imaging V3.0 - P203 \ninstalled.\nRoutines:\n \nMAGIP203\nMAGDHOW3 \n \n \n \nPlease note that routine MAGIP203 is deleted after the KIDS build is\n\n
\nVistA Imaging V3.0 Patch 202 - MAG INDEX TERMS UPDATE\n \nRoutines:\n \nMAGIP202\n \nPlease note that routine MAGIP202 is deleted after the KIDS build is \ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 190\ninstalled\n \nRoutines:\n \nMAGDRPC5\nMAGDRPC9 \nMAGIP190\n \nPlease note that routine MAGIP190 is deleted after the KIDS build is\n\n
\nVistA Imaging Patch 3 - support for long file names.\nPlease note: Routine MAGIPOS3 is a post install routines that is deleted\nafter the KIDS installation is completed.\n \nChecksum values:\n \nMAGGTU1 value = 3618392\nMAGIPOS3 value = 4950507\nMAGQBPRG value = 9753805\nMAGUSIT value = 7097852\n \n\n
\nVistA Imaging V3.0 - Patch 210\n \nRoutines:\n \nMAGDHOW1\nMAGIP210\n \nPlease note that routine MAGIP210 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging Capture 211\nThis error occurs when trying to remove all images from the \nuser's \\temp folder when the user does not have permission to\ndelete from that folder.\nThis patch fixes 2 issues.\nFirst: when trying to Batch Capture multiple images,\nsometimes an error will occur when the application is processing\nsingle page PDF files. The PDF file will not be captured, and not\nincluded in the Image Group.\nSecond: When Closing the Capture application, sometimes an error\nwill occur, and the application will not close. The user must\nuse Taskmanager to 'kill' the application.\n\n
\nVistA Imaging Patch 198 - BackGround Processor (BP)\n135, 196, 198 will all be supported.\nThis patch fixes the memory leak issue in the \nThumbnail/Abstract maker.\nFixes an issue in the Verifier. The Verifier\nwas not checking the Operational Staus of TIER 2 Locations\nand was checking Off-Line Locations for Images.\nAlso, this Patch will be a Full Install of the Background\nProcessor and all utility applications. \nWhen Patch 198 KIDs is installed, BP Client versions\n\n
\nVistA Imaging V3.0 - Path 199 VistA RAD\n \nRoutines:\n \nMAGJTU4V\nMAGJUTL5\nMAGJMN1\n\n
\nRoutines for Patch 197\n \nRoutines:\nMAGIP197 value = 4967967\nMAGNAN03 value = 68058654\nMAGNVQ06 value = 45900223\n \nPlease note that routine MAGIP197 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging Capture 215\nThis patch fixes 1 issue.\nIn the Capture Application, when capturing images to Clinical\nProcedures, sometimes an error will occur. The error message\nstates: Cannot focus an Invisible window.\nThis issue is fixed. \n\n
\nVistA Imaging Patch 214 - BackGround Processor (BP)\nThis patch will assure there are no 'spaces' in the generated\npassword.\nWhen Patch 214 KIDs is installed, BP Client versions\n135, 196, 198 and 214 will all be supported.\nThis patch fixes the following issues:\nThe BP gets stuck in a loop displaying the error message 'Can't\nfind file'. the BP must be killed using TaskManager.\nThe BP Site Parameter Window will not open. the error message\nis shown 'Value not Initialized'.\nThe BP user is prompted to enter their PIV/PIN. this should\nnot happen\nThe BP uses Kernel utilities to generate encrypted passwords. \n\n
\nMAG*3.0*216\nThis patch fixes the Clinical Display Setup.exe that causes\nthe FBCS software to stop working after a Clinical Display \ninstall.\nThis will check the routines from a BUILD file.\n\n
\nVistA Imaging V3.0 - Patch 220 VistARAD Timestamp Issue\nRoutines:\n \nMAGIP220\nMAGJUTL2\n \nPlease note that routine MAGIP220 is deleted after the KIDS build is\ninstalled.\n\n
\nClinical Procedures and DICOM Consult Request Tracking.\nThis allows DICOM objects created during a CP examination to be sent\nto VistA Imaging and be processed automatically. It also allows them\nto be used with all of the other DICOM services, like query/retrieve\nand export.\n \nReports in DICOM Encapsulated PDF are highly recommended.\n \nThis patch and MD*1.0*60 work together to greatly imnprove\ninteroperability between Clinical Procedures and Vist Imaging\nCPRS Consult Request Tracking DICOM.\n \nThe CP studies have the same Instrument Order Number as the\nregular consult and procedure Accession Number (sss-GMR-nnnnnnnn).\n \n\n
\nRoutines for Patch 11, Test Build 27.\nMAG7UM value = 8130703\nMAG7UP value = 11171313\nMAGBRTE3 value = 5833319\nMAGBRTE4 value = 14663489\nMAGBRTE5 value = 12248946\nMAGBRTLD value = 6114349\nMAGBRTUT value = 6312859\nMAGDAUDR value = 6872220\nMAGDCCS value = 14263908\nMAGDCCS2 value = 6323959\n \nMAGDCCS3 value = 4054715\nMAGDCCSD value = 5138399\nMAGDCCSS value = 7793439\nMAGDFB value = 2768480\nMAGDFCNV value = 4298417\nMAGDGL value = 8693119\nMAGDHL7 value = 7588848\nMAGDHRS1 value = 4952354\nMAGDHWS value = 8397303\nMAGDIR8 value = 4729054\nRoutines:\nMAGDIR81 value = 13946127\nMAGDIR82 value = 7689405\nMAGDIR83 value = 7543877\nMAGDIR84 value = 7164900\nMAGDIR85 value = 2900846\nMAGDIR8A value = 10602838\nMAGDIR9A value = 10819306\nMAGDIR9B value = 6837304\nMAGDIR9E value = 15838144\nMAGDIRVE value = 15724185\nMAG7RS value = 11923364\nMAGDLB1 value = 12114206\nMAGDLB12 value = 8451648\nMAGDLB5 value = 4070169\nMAGDLB6 value = 4138192\nMAGDLB9 value = 4846825\nMAGDLBAA value = 6781952\nMAGDLBSR value = 7596015\nMAGDRA1 value = 7837939\nMAGDRA2 value = 7852272\nMAGDRCU2 value = 9684070\nMAG7RSD value = 5995508\nMAGDRPC1 value = 8949355\nMAGDRPC2 value = 5509304\nMAGDRPC3 value = 11531835\nMAGDRPC4 value = 15375596\nMAGDRPC5 value = 15154889\nMAGDRPC6 value = 9417357\nMAGDRPC7 value = 8750764\nMAGDRPC8 value = 10609976\nMAGDRTIM value = 7583708\nMAGENV11 value = 3658957\nMAG7RSO value = 4178690\nMAGIPS11 value = 4684033\nMAGJRT value = 12927055\nMAGXMA value = 3165496\n \nPlease note that routine MAGIPS11 is deleted after the KIDS Build is\ninstalled.\nMAG7RSR value = 4411159\nMAG7UDR value = 4129505\nMAG7UFO value = 3674965\n\n
\nVistA Imaging V3.0 - Patch 194 - Duplicate Rad Order Defect\ninstalled.\n \n \nRoutines:\n \nMAGVIM05 \nMAGIP194\n \nPlease note that routine MAGIP194 is deleted after the KIDS build is\n\n
\nVistA Imaging V3.0 - Patch 217 Importer III\nRoutines:\n \nMAGIP217\n \nPlease note that routine MAGIP217 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 201\nMAGNAN01 value = 23808502\nMAGVRS41 value = 187565067\nMAGVD011 value = 8804376\n \nPlease note that routine MAGIP201 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGIP201 value = 18271936\nMAGGSIA value = 36655133\nMAGGTIA1 value = 34882923\nMAGJEX2 value = 46640009\nMAGNUTL2 value = 9894691\nMAGNWRK1 value = 51777875\n\n
\nPatch 219 is a Telereader update.\nThis patch changes the Help files for Telereader from \nRoboHelp Help files, to Adobe PDF files.\n\n
\nVistA Imaging V3.0 - Patch 218\nRoutines:\n \nMAGIP218\n \nPlease note that routine MAGIP218 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging 3.0 - Patch 223 - Clinical Capture\n \nRoutines:\n \nMAGGTU4C\nMAGIP223\n \nPlease note that routine MAGIP223 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 222 BackGround Processor (BP)\nRoutines:\n \nMAGIP222\nMAGBVAL\nMAGQBUT4\n \nPlease note that routine MAGIP222 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 221\nMAGNVQ04 value = 30558931\nMAGNVQ05 value = 35641804\nMAGNVQ07 value = 5002623\nMAGNWRK1 value = 53919420\nMAGSIXG1 value = 40907827\nMAGSIXG2 value = 69913945\nMAGSIXG3 value = 109262683\nMAGVIM01 value = 195265246\nMAGUTL06 value = 19148168\n \n \nPlease note that routine MAGIP221 is deleted after the KIDS Build is\ninstalled.\nRoutines:\nMAGIP221 value = 8533414\nMAGDQR21 value = 188496027\nMAGGSIA value = 35830061\nMAGGTIA1 value = 34088332\nMAGNPCHE value = 19371617\nMAGNUTL2 value = 23733574\n\n
\nVistA Imaging 3.0 - Patch 233 - Clinical Capture\n \nRoutines:\n \nMAGGTU4C\nMAGIP233\n \nPlease note that routine MAGIP233 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 234\nRoutines:\n \nMAGIP234\nMAGGTRA1\nMAGGTU4D\n \nPlease note that routine MAGIP234 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for the Imaging Site Usage reports.\nMAGQST value = 4955242\n \nPlease note that routine MAGIPS29 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGIPS29 value = 7704207\nMAGQE1 value = 4787344\nMAGQE2 value = 6460721\nMAGQE3 value = 15683461\nMAGQE4 value = 5655117\nMAGQE5 value = 10424133\n\n
\nVistA Imaging V3.0 - Patch 235\nRoutines:\n \nMAGIP235\n \nPlease note that routine MAGIP235 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - P204\nRoutines:\n \nMAGIP204\n \nPlease note that routine MAGIP204 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 237\nRoutines:\n \nMAGIP237\n \nPlease note that routine MAGIP237 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 230\n \nRoutines:\nMAGIP230 value = 4189203\n \nPlease note that routine MAGIP230 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 225\nRoutines:\n \nMAGIP225\nMAGGTU4D\nMAGGTRA1\n \nPlease note that routine MAGIP225 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 238\nRoutines:\n \nMAGIP238\nMAGQBUT4 \n \nPlease note that routine MAGIP238 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 226\nRoutines:\n \nMAGIP226\nMAGGTU4C\n \nPlease note that routine MAGIP226 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 239\n \nPlease note that routine MAGIP239 is deleted after the KIDS build is\ninstalled.\nRoutines:\n \nMAGIP239\nMAGDRPC1\nMAGDGMRC\nMAGDRPC9\nMAGDQR02\nMAGVRS44\n\n
\nVistA Imaging V3.0 - Patch 252\nRoutines:\n \nMAGIP252\nMAGVIMRA\n \nPlease note that routine MAGIP252 is deleted after the KIDS build is\ninstalled.\n\n
\nThis patch addresses permissions issues with Windows 2000 and XP. All\nmodifications to the sofware are in the GUI application that is installed\non the workstation. The KIDS package is distributed only for updating\nthe package file and tracking the installation nationally. \n\n
\nVistA Imaging V3.0 - Patch 242\nRoutines:\n \nMAGIP242\nMAGGTU4T\n \nPlease note that routine MAGIP242 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 263\nPlease note that routine MAGIP263 is deleted after the KIDS build is\ninstalled.\n \nRoutines:\n \nMAGIP263\nMAGUE001\nMAGUE004\nMAGDQR04\n \n\n
\nVistA Imaging V3.0 - Patch 264\n \nRoutines:\nMAGIP264\nMAGGTU4C \n \nPlease note that routine MAGIP264 is deleted after the KIDS build is\ninstalled\n\n
\nVistA Imaging V3.0 - Patch 243\nRoutines:\n \nMAGIP243\nMAGQBUT4\n \nPlease note that routine MAGIP243 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 250\nRoutines:\n \nMAGIP250\nMAGVIM01\n \n \nPlease note that routine MAGIP250 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 281\nRoutines:\n \nMAGIP281\nMAGGTU4T\n \nPlease note that routine MAGIP281 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 282, Test Build 4.\n \nRoutines:\nMAGIP282 value = 4110419\nMAGGNTI2 value = 40037476\n \nPlease note that routine MAGIP282 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 251\nRoutines:\n \nMAGIP251\nMAGGTU4C\n \nPlease note that routine MAGIP251 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 280\ninstalled\n \nRoutines:\nMAGIP280\nMAGDQR04\nMAGDRPC9\n \n \nPlease note that routine MAGIP280 is deleted after the KIDS build is\n\n
\nVistA Imaging V3.0 - Patch 256\nRoutines:\n \nMAGIP256\nMAGGTU4D\n \nPlease note that routine MAGIP256 is deleted after the KIDS build is\ninstalled.\n\n
\nThis patch enhances the import API capabilities. \n\n
\nBackup of MAG*3.0*231 on Mar 15, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n \nStudy Tracker -- a set of routines to query PACS and retrieve images.\n\n
\nBackup of MAG*3.0*248 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nVistA Imaging V3.0 - Patch 248\nRoutines:\n \nMAGIP248\nMAGQBUT4\n \nPlease note that routine MAGIP248 is deleted after the KIDS build is\ninstalled.\n\n
\nBackup of MAG*3.0*254 on Apr 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of MAG*3.0*255 on May 05, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nVistA Imaging V3.0 - Path 255 VistA RAD VistA RAD\n \nRoutines:\n \nMAGJTU4V\nMAGJUTL5\nMAGJMN1\n\n
\nBackup of MAG*3.0*262 on Jun 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nVistA Imaging V3.0 - Patch 262\n \nRoutines:\nMAGVGUID\nMAGIP262\n \n \nPlease note that routine MAGIP262 is deleted after the KIDS build is\ninstalled\n\n
\nRoutines for Patch 40, Test Build 2.\n \nRoutines:\nMAG7RS value = 12193599\nMAGIPS40 value = 4705510\n \nPlease note that routine MAGIPS40 is deleted after the KIDS Build is\ninstalled.\n\n
\nBackup of MAG*3.0*283 on Jun 04, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nVistA Imaging V3.0 - Patch 283\ninstalled.\n \nRoutines:\nMAGIP283\nMAGVIM01\nMAGVIM03\nMAGVCWIA\n \nPlease note that routine MAGIP283 is deleted after the KIDS build is\n\n
\nBackup of MAG*3.0*258 on Jul 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nVistA Imaging V3.0 - Patch 258\nRoutines:\n \nMAGIP258\nMAGGTU4D\nMAGSIXG3\n \nPlease note that routine MAGIP258 is deleted after the KIDS build is\ninstalled.\n\n
\nImprovement to P231 Automatic Query/Retrieve.\n \nAdd last four of SSN to Accession Number Query to make query unique as a\nwork-around for merged PACS database where there are multiple studies\nwith the same accession number.\n\n
\nVistA Imaging V3.0 - Patch 257\nRoutines:\n \nMAGIP257\nMAGVRS06\n \nPlease note that routine MAGIP257 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 284.\n \nRoutines:\nMAGIP284 value = 11012642\n \nPlease note that routine MAGIP284 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 267\n \nRoutines:\nMAGGTU4C\nMAGIP267\n \n \nPlease note that routine MAGIP267 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 301, Test Build 4.\nMAGVIM08 value = 24688133\n \nPlease note that routine MAGIP301 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDHOW2 value = 88185944\nMAGDQR02 value = 64690388\nMAGDQR20 value = 83237743\nMAGIP301 value = 4110353\nMAGNVQ01 value = 111364623\nMAGSPID value = 11523584\n\n
\nVistA Imaging V3.0 - Patch 316\nRoutines:\n \nMAGIP316\nMAGGTU4D\n \nPlease note that routine MAGIP316 is deleted after the KIDS build is\ninstalled.\n\n
\nThis KIDS install will add the following support:\nMAGGSFT value = 3067100\nMAGGSIA value = 5464426\nMAGGSIA1 value = 9791476\nMAGGSIM value = 5360010\nMAGGSIU1 value = 3854213\nMAGGSIU2 value = 4516888\nMAGGSIU3 value = 7186347\nMAGGSIUI value = 11682244\nMAGGSIV value = 12079119\nMAGGSPP value = 3242430\nImaging import API with Clinical Procedures\nMAGGSTI value = 6260731\nMAGGSU1 value = 2676194\nMAGGTAU value = 9601918\nMAGGTSY1 value = 6104608\nMAGGTU3 value = 7481270\nMAGGTUP value = 7182048\nMAGIPOS7 value = 2508617\nMAGQBIM value = 3963432\nMAGQBPG1 value = 11319930\nMAGQBPRG value = 9369062\nBackground Processor Enhacements\nMAGQBTM value = 14438732\nMAGQBUT value = 12416907\nMAGQBUT1 value = 13611765\nMAGQBUT2 value = 15727225\nMAGQBUT4 value = 2633801\nMAGQST value = 714956\n \n \n \nPlease note that routine MAGIPOS7 is deleted after the KIDS application \nSupport for MIL 6.1 drivers (Meteor II and Orion Capture)\nis installed.\n \nRoutine checksum:\nMAGBAPI value = 7367416\nMAGGSCP value = 6108869\nMAGGSERR value = 3210527\n\n
\n \nMAGGNLKP value = 5120114\nMAGGNTI value = 9823383\nMAGGSCP value = 6072520\nMAGGSFL1 value = 5952938\nMAGGSFLT value = 9149177\nMAGGSFT value = 3683491\nMAGGSIA value = 6077587\nMAGGSIA1 value = 13485750\nMAGGSIM value = 5442685\nMAGGSIU1 value = 5521127\n \nMAGGSIU2 value = 4915214\nMAGGSIU3 value = 8910698\nMAGGSIUI value = 15004401\nMAGGSIV value = 15908776\nMAGGSIV1 value = 3907430\nMAGGSPP value = 5789193\nMAGGSQI value = 21356895\nMAGGTAU value = 11244676\nMAGGTERR value = 3000489\nMAGGTIA value = 11274455\nDocument scanning and image filtering.\nMAGGTIA1 value = 7046008\nMAGGTID value = 10903946\nMAGGTIG value = 10401360\nMAGGTII value = 8729176\nMAGGTMC value = 4890330\nMAGGTPT1 value = 7555501\nMAGGTRAI value = 9211973\nMAGGTRP1 value = 6078443\nMAGGTRPT value = 12184290\nMAGGTSR value = 4904140\n \nMAGGTU1 value = 4009879\nMAGGTU3 value = 11515909\nMAGGTU4 value = 8596313\nMAGGTU5 value = 4562085\nMAGGTU6 value = 9042947\nMAGGTU7 value = 9742723\nMAGGTU9 value = 8121952\nMAGGTUP value = 6949357\nMAGIPOS8 value = 10371822\nMAGLOG value = 4151777\nRoutine checksums:\nMAGQBAB value = 5521638\nMAGQBGCC value = 5471832\nMAGQBJB value = 6294131\nMAGQBJH value = 8678496\nMAGQBPG1 value = 12026245\nMAGQBPG2 value = 7662428\nMAGQBPRG value = 9927955\nMAGQBTM value = 14872817\nMAGQBUT value = 14453966\nMAGQBUT1 value = 16504458\n \nMAGQBUT2 value = 15657747\nMAGQBUT4 value = 4347014\nMAGQE5 value = 10174225\nMAGSDEL4 value = 2647473\nMAGSDLGR value = 6841689\nMAGSIMBR value = 4052881\nMAGSIXG1 value = 11374305\nMAGSIXGT value = 10338816\nMAGUSIT value = 6381382\n \nMAGBAPI value = 13283725\nRoutine MAGIPOS8 is deleted after the KIDS install.\nMAGBAPIP value = 4490136\nMAGFILEB value = 11644630\n\n
\nVistA Imaging V3.0 - Patch 271\nMAGVSPU2\n \nPlease note that routine MAGIP271 is deleted after the KIDS build is\ninstalled.\n \nRoutines:\nMAGIP271\nMAGVSOPE\nMAGVSOPD\nMAGVSOPU\nMAGVSPE2\nMAGVSPD2\n\n
\nVistA Imaging V3.0 - Patch 273\nRoutines:\n \nMAGIP273\n \nPlease note that routine MAGIP273 is deleted after the KIDS build is\ninstalled.\n\n
\nMenu 1-1 (Text Gateway/ Start Processing Text Messages from HIS)\n \nMenu option 1 - 1: Start Processing Text Messages from HIS\n Modify to prevent error when 0 node missing from \n ^MAGDWLST(2006.55,DIVISION,1,DFN,0)\n \nManagement Portal Security Settings with Install\n Initiate credentials prompting to open Management Portal\n \nLDGW Routines:\nMAGDWLP2\n Expand disk space warning message\nMAGDDEL2\nMAGDDR3\nMAGDDW4\nMAGDWLPA\nMAGDVRSN\n \nMenu option 1- 4: Display Modality Worklist Statistics \n Remove condition where "Exit" prompt timeout and COUNT = "<none>" \n prevents refresh of display.\n \nRead and Write operations for DICOM images\n Properly handle VR containing " or " i.e. "OB or OW".\n\n
\nVistA Imaging V3.0 - Patch 292\nRoutines:\n \nMAGIP292\nMAGGTU4T\nMAGDHOW1\n \nPlease note that routine MAGIP292 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 289\n \nRoutines:\nMAGIP289\n \nPlease note that routine MAGIP289 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 325\nRoutines:\n \nMAGIP325\nMAGQBUT4\n \nPlease note that routine MAGIP325 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 302\nRoutines:\n \nMAGIP302\n \nPlease note that routine MAGIP302 is deleted after the KIDS build is\ninstalled.\n\n
\nDICOM Exporter Enhancements and bug fixes.\n\n
\nVistA Imaging V3.0 - Patch 269\n\n
\nVistA Imaging V3.0 - Patch 321\nRoutines:\n \nMAGIP321\nMAGGTU4C\n\n \nPlease note that routine MAGIP321 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 30, Test Build 11.\nMAGDHL7 value = 7399823\nMAGDHRS1 value = 5025884\nMAGDIR81 value = 14282136\nMAGDIR82 value = 13464369\nMAGDIR83 value = 7606355\nMAGDIR85 value = 2914037\nMAGDIR9A value = 10789655\nMAGDIRVE value = 15732775\nMAGDLB1 value = 11911075\nMAGDRA1 value = 7842219\n \nMAGDRCU1 value = 8485773\nMAGDRPC1 value = 8395133\nMAGDRPC2 value = 12950501\nMAGDRPC3 value = 11631756\nMAGDRPC4 value = 15201662\nMAGDRPC5 value = 14221287\nMAGDRPC6 value = 11175169\nMAGDRPC8 value = 10596480\nMAGIPS30 value = 4783130\nMAGQE1 value = 4871610\nRoutines:\nMAGQE3 value = 15528150\nMAGQE4 value = 5670112\nMAGQE5 value = 10174225\nMAGQST value = 4967326\n \nPlease note that routine MAGIPS30 is deleted after the KIDS Build is\ninstalled.\nMAG7RS value = 12193599\nMAGBRTE4 value = 15019760\nMAGBRTE5 value = 12363938\nMAGBRTLD value = 5665322\nMAGBRTUT value = 6805146\nMAGDCCS2 value = 6363543\n\n
\nThis patch updates 2005.83 - IMAGE INDEX FOR TYPES\nEntry DD214 ENLISTED RECORD & RPT OF SEP is being changed to\nDD214 ARMED FORCES RECORD OF SVC AND SEP\n\n
\nVistA Imaging V3.0 - Patch 290\nPlease note that routine MAGIP290 is deleted after the KIDS build is\ninstalled.\nNew Field, #80 APP ALT XML VIEWER\nin the IMAGING USER PREFERENCES FILE #2006.18\n \nRoutines:\n \nMAGIP290\nMAGGTU4D\n \n\n
\nVistA Imaging V3.0 - Patch 320\nRoutines:\n \nMAGIP320\nMAGGTU4T\n \n \nPlease note that routine MAGIP320 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 293 BP\nRoutines:\n \nMAGIP293\nMAGQBUT4\n \nPlease note that routine MAGIP293 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 323.\nSee FORUM for detailed Patch Description.\n\n
\nVistA Imaging V3.0 - Patch 307\nMAGDIR8A\nMAGDRPC9\nMAGVORDR\nMAGVGUID\n \nPlease note that routine MAGIP307 is deleted after the KIDS build is\ninstalled.\n \nUpdates to correct parsing of accession area from the accession number \nand ensure proper lookup of the internal #68 entry.\nAlso fixes issue where a new STUDY UID gets generated from\nCHECK STUDY UID when a Print Set is used.\n \nRoutines:\nMAGIP307\n\n
\nVistA Imaging V3.0 - Patch 324\nRoutines:\n \nMAGIP324\n \nPlease note that routine MAGIP324 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging 3.0 - Patch 332\n \nUpdate to RPC MAGV IMPORT STATUS to fix the issue when an original UID is\npassed but the UID has been replaced so the lookup erroneously fails.\n \nRoutines:\nMAGVIM01\nMAGVIM09\nMAGIP332\n\n
\nVistA Imaging V3.0 - Patch 315\nRoutines:\n \nMAGIP315\nMAGGTU4D\n \nPlease note that routine MAGIP315 is deleted after the KIDS build is\ninstalled.\n\n
\nRoutines for Patch 5, Test Build 2.\n \nRoutines:\nMAGIPS05 value = 4705522\n \nPlease note that routine MAGIPS05 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 331 BP\nRoutines:\n \nMAGIP331\nMAGQBUT4\n \nPlease note that routine MAGIP331 is deleted after the KIDS build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 328\n \nROUTINES:\n---------\nMAGIP328\nMAGGTU4T\nMAGDTR02\nMAGDTR03\n\n
\nBackup of MAG*3.0*328 on Feb 01, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nVistA Imaging V3.0 - Patch 314\nRoutines:\n \nMAGIP314\n \nPlease note that routine MAGIP314 is deleted after the KIDS build is\ninstalled.\n\n
\nPlease see patch descrioption in FORUM.\n\n
\nPlease see the patch 352 description in FORUM for details.\n\n
\nSee FORUM Patch Description for details.\n\n
\nVistA Imaging V3.0 Patch 319 - DICOM Gateway IRIS upgrade\n \n \nRoutines:\nMAGIP319\n \nPlease note that routine MAGIP319 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 - Patch 291\ninstalled.\n \nRoutines:\n \nMAGIP291\nMAGGTU4C\n \n \nPlease note that routine MAGIP291 is deleted after the KIDS build is\n\n
\nPlease see the patch description in FORUM for details.\n\n
\nPatch 48 is a maintanence patch for \nMAGGSPP value = 5796302\nMAGGTIA value = 11492904\nMAGGTIG value = 10449383\nMAGGTII value = 8845764\nMAGGTLB value = 13369489\nMAGGTRPT value = 11950157\nMAGGTU3 value = 11723273\nMAGGTU4 value = 8466131\nMAGGTU5 value = 4744682\nMAGGTU6 value = 10108948\nImaging Display, Imaging Capture, Annotation editor and BP.\nMAGGTUP value = 6957380\nMAGIPO48 value = 7416703\nMAGQBGCC value = 5552170\nMAGQBUT value = 14796199\nMAGQBUT4 value = 4347014\nMAGSIXG1 value = 12432475\nMAGSIXGT value = 10585881\ndone\nIt deals with issues encountered in Alpha testing of Patch 8.\n \nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*48 IMAGING\nMAGFILEB value = 11713219\nMAGGSIU3 value = 8945343\nMAGGSIUI value = 14792968\n\n
\nThis build adds support for a separate site service for the TeleReader \nClient. Please see the patch description in FORUM for details.\n\n
\nVistA Imaging V3.0 - Patch 351\n \nRoutines:\n--------- \nMAGIP351\nMAGGTU4D\n\n
\nVistA Imaging V3.0 - Patch 345\n \nPlease note that routine MAGIP345 is deleted after the KIDS build is\ninstalled.\n \nRoutines:\n \nMAGVUID\nMAGGETUIDSTATUS\nMAGVIM09\nMAGIP345\n \n\n
\nVA patch 341 (companion to ISI patch 110) -- ISI Rad; replaces VistARad\n\n
\n \nMAG*3.0*334 is a patch that provides fixes to VistA Imaging Clinical Display. \n\n
\nA problem was caused by patch MAG*3.0*226 (October 2019) which changed\n \nThis patch corrects this problem.\nthe way that Clinical Capture stored DICOM images.\n \nInstead of saving them as DICOM objects, they were stored as raw JPEG\nimages with a *.DCM extension. These images need to be converted to\nDICOM and stored as proper DICOM objects. The previously stored JPEG\nimages need to be renamed using the *.JPG extension.\n \nThese changes must be performed on both Tier-1 and Tier-2 storage.\n\n
\nRoutines for Patch 357\nMAGVIM13 value = 7416635\n \nPlease note that routine MAGIP357 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGIP357 value = 26046319\nMAGVIM01 value = 215042408\nMAGVIM05 value = 238450531\nMAGVIM09 value = 120769362\nMAGVIM11 value = 4403964\nMAGVIM12 value = 8901430\n\n
\nVistA Imaging V3.0 - Patch 335\nPlease note that routine MAGIP335 is deleted after the KIDS build is\ninstalled.\n \nRoutines:\n \nMAGIP335\nMAGGTU4C\nMAGGTU6\n \n \n\n
\nImaging API for the Medicine conversion to CP reports\n\n
\nMAG*3.0*354 provides fixes to the Hybrid DICOM Image Gateway (HDIG).\n \n\n
\nTELEREADER WL BLANK PROCEDURE INDEX\n\n
\n MAG*3.0*375 provides VistA Imaging Mumps Bug fixes.\n\n
\nThis will check the routines from a BUILD file.\n PATIENT SAFETY NOTIFICATION\n \n Under certain circumstances, the EKG window will not\nrefresh properly when you select a new patient in CPRS; \ninstead of showing the new patient, the EKG window will\ncontinue to show the previous patient. \n \nTo prevent this problem:\n \n Verify that the 'Show MUSE EKGs' option under\nSelect BUILD NAME: MAG*3.0*63 IMAGING\n Options > View Preferences is checked;\n OR\n Do not minimize the Imaging Display window while viewing EKGs.\n \nThis problem will be corrected shortly by Imaging Patch 63.\n!***************************************************************!\nMAGGTII value = 8558917\nMAGGTU4 value = 12651615\nMAGIPS63 value = 5539441\ndone\nThe following message is displayed to clients \n!***************************************************************!\n \n\n
\nThis is MAG*3.0*31T10.\nMAGXCVP value = 9864505\nMAGXCVR value = 16849068\nMAGXCVS value = 17548265\nMAGXCVX value = 9257872\n \nImage Index Conversion.\n \nMAGIPS31 value = 6638669\nMAGXCVC value = 12825393\nMAGXCVI value = 12567821\nMAGXCVI1 value = 11895918\nMAGXCVL value = 7379304\n\n
\nThis will check the routines from a BUILD file.\n \nThis patch is an enhancement to the previous Clinical Display client. It \nallows users to connect and retrieve images and associated information \nfrom remote sites. This patch also provides an auto-caching feature that \nallows the user to request images be brought to their local machine in \npreparation for viewing.\nSelect BUILD NAME: MAG*3.0*45 IMAGING\nMAGGTU3 value = 12319136\nMAGGTU4 value = 13208753\nMAGGTU6 value = 10490182\nMAGGTUP value = 7097744\nMAGIPS45 value = 9265985\ndone\nChecksums computed with D CHECK^XTSUMBLD\n\n
\nSelect BUILD NAME: MAG*3.0*78 IMAGING\nMAGIPS78 value = 9014720\nMAGQE4 value = 12918538\n\n
\nRoutines for Patch 51, Test Build 22.\nMAGBRTUT value = 6881357\nMAGDCCSS value = 7813577\nMAGDFB value = 2735520\nMAGDFCNV value = 4468938\nMAGDGL value = 8800264\nMAGDGMRC value = 8586191\nMAGDHWA value = 13363551\nMAGDHWC value = 11574745\nMAGDHWS value = 8385051\nMAGDIR8 value = 4801612\n \nMAGDIR81 value = 15887244\nMAGDIR82 value = 13699038\nMAGDIR83 value = 8183019\nMAGDIR8A value = 10596882\nMAGDIR9A value = 11238086\nMAGDIR9B value = 6917351\nMAGDIR9E value = 13785673\nMAGDLB12 value = 8056663\nMAGDLB6 value = 3475437\nMAGDLBAA value = 6585681\nRoutines:\nMAGDLBV value = 6999551\nMAGDMEDK value = 3272291\nMAGDMEDL value = 6755625\nMAGDQR00 value = 2425880\nMAGDQR01 value = 8020820\nMAGDQR02 value = 15665200\nMAGDQR03 value = 9918762\nMAGDQR04 value = 12503040\nMAGDRA2 value = 7860816\nMAGDRCU2 value = 9684614\nMAG7UP value = 11177267\nMAGDRPC1 value = 11783859\nMAGDRPC2 value = 13189349\nMAGDRPC3 value = 11696591\nMAGDRPC4 value = 16384505\nMAGDRPC5 value = 14689488\nMAGDRPC6 value = 11177465\nMAGDRPC7 value = 8740525\nMAGDRPC8 value = 10596480\nMAGIPS51 value = 9657731\nMAGJEX2 value = 14452837\nMAGBRTE3 value = 5833319\nMAGUXRF value = 4648912\nMAGVCHK value = 7581330\n \nPlease note that routine MAGIPS51 is deleted after the KIDS Build is\ninstalled.\nMAGBRTE4 value = 15295929\nMAGBRTE5 value = 10025015\nMAGBRTK value = 7162000\nMAGBRTLD value = 7191644\n\n
\nImaging Patch 16, for VistARad maintenance update.\nMAGJMN1 value = 11493328\nMAGJORD value = 7374192\nMAGJUPD1 value = 17522294\nMAGJUTL3 value = 11237728\nRoutine Checksums:\nMAGGTAU value = 9853264\nMAGGTPT1 value = 6979388\nMAGJEX1 value = 25560938\nMAGJEX1B value = 6011556\nMAGJLS2B value = 16352911\nMAGJLS3 value = 16365765\nMAGJLST1 value = 28077172\n\n
\nVistARad Patch 18 software.\n\n
\nImaging v3.0 Patch 61. VistA Imaging Index Term Maintenance\nSelect BUILD NAME: MAG*3.0*61 IMAGING\nMAGIP61A value = 10598429\nMAGIPO61 value = 18706336\nMAGSIXGT value = 13741457\nMAGXIDX0 value = 12595354\nMAGXIDXU value = 21328286\ndone\nThis patch is to provide the utility that will automatically \nupdate the Imaging Index Files at all sites by processing a VistA \nmenu option. The Option will install updates to the Index Files that have\nbeen sent via a MailMan message. All updates installed will have been\napproved by the VistA Imaging Index Term Review Board.\n \nChecksums calculated with CHECK^XTSUMBLD\nThis will check the routines from a BUILD file.\n\n
\nSelect BUILD NAME: MAG*3.0*20 IMAGING\nMAGGTU6 value = 64383471\nMAGGTU7 value = 22552210\nMAGIPS20 value = 26957915\nMAGIPT20 value = 70909996\nMAGLOG value = 6935907\nMAGQBAB value = 10838980\nMAGQBD value = 7129737\nMAGQBGCC value = 11208984\nMAGQBIM value = 7456958\nMAGQBJB value = 18032148\nMAGBAPI value = 74386027\nMAGQBJH value = 24339395\nMAGQBJHR value = 14061671\nMAGQBPG1 value = 74002571\nMAGQBPG2 value = 20522184\nMAGQBPRG value = 57111603\nMAGQBTM value = 79154449\nMAGQBUT value = 78801561\nMAGQBUT1 value = 75489141\nMAGQBUT2 value = 73670919\nMAGQBUT4 value = 78268087\nMAGBAPIP value = 8622481\nMAGQBUT5 value = 13804118\nMAGQE1 value = 11840891\nMAGQE2 value = 17337879\nMAGQE3 value = 75394836\nMAGQE5 value = 48023547\nMAGUSIT value = 17597745\nMAGDIR82 value = 62866214\nMAGDLB12 value = 22838427\nMAGGSIUI value = 60693392\nMAGGSIV value = 38730975\nMAGGSIV1 value = 21788454\nMAGGTU3 value = 61285454\n\n
\nRoutines for Patch 50, Test Build 31.\nMAGDRPC2 value = 13362997\nMAGDRPC3 value = 14213495\nMAGDRPC4 value = 17119065\nMAGDRPC9 value = 9264716\nMAGGTIA2 value = 7600790\nMAGIPS50 value = 7277874\n \nPlease note that routine MAGIPS50 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGBRTUT value = 6909436\nMAGDGMRC value = 8627087\nMAGDHWA value = 13381903\nMAGDIR81 value = 15986378\nMAGDIR9B value = 6944410\nMAGDRPC1 value = 11246032\n\n
\nRoutines for Patch 52, Test Build 16.\n \nRoutines:\nMAGIPS52 value = 4705533\n \nPlease note that routine MAGIPS52 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 84, Test Build 1.\n \nRoutines:\nMAGDHWS value = 8664784\nMAGIPS84 value = 5182345\n \nPlease note that routine MAGIPS84 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 77, Test Build 7.\n \nRoutines:\nMAGENV77 value = 7864063\nMAGIPS77 value = 5564319\n \nPlease note that routine MAGIPS77 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 46, Test Build 28.\nMAGDTR02 value = 11542794\nMAGDTR03 value = 17747636\nMAGDTR04 value = 8324327\nMAGDTR05 value = 12647049\nMAGDTR06 value = 10053102\nMAGDTRDX value = 8254807\nMAGDTRLU value = 7439670\nMAGGNLKP value = 6081621\nMAGGNTI1 value = 11025078\nMAGGNTI2 value = 7904476\n \nMAGGNTI3 value = 5195830\nMAGGTPT1 value = 8609100\nMAGGTU3 value = 12647741\nMAGGTU31 value = 6267048\nMAGGTU4 value = 9595917\nMAGGTU41 value = 10672702\nMAGGTU6 value = 11306571\nMAGGTU71 value = 6245772\nMAGIPS46 value = 9488645\nMAGQE3 value = 15888752\nRoutines:\nMAGQE5 value = 13158187\nMAGQE6 value = 5946318\n \nPlease note that routine MAGIPS46 is deleted after the KIDS Build is\ninstalled.\nMAGDHRC0 value = 4285870\nMAGDHWC value = 12104444\nMAGDIR81 value = 16164949\nMAGDIR9A value = 11384181\nMAGDIR9E value = 14829187\nMAGDTR01 value = 10072315\n\n
\nVistARad Patch 65\n\n
\nRoutines for Patch 86, Test Build 4.\n \nRoutines:\nMAGDHL7 value = 7016595\nMAGDHW0 value = 4187105\nMAGIPS86 value = 5183006\n \nPlease note that routine MAGIPS86 is deleted after the KIDS Build is\ninstalled.\n\n
\n \nMAGJRT value = 11669345\nMAGJUTL3 value = 8695865\n \nPlease note that routine MAGIPOS9 is deleted after the KIDs installation.\nRouting application for VistA Imaging 3.0\n \nChecksums:\n \nMAGBRTLD value = 6108978\nMAGBRTUT value = 7369522\nMAGIPOS9 value = 3409921\nMAGJMN1 value = 11228518\n\n
\nRoutines for Patch 85, Test Build 5.\nMAGDRPC3 value = 14580986\nMAGDRPC5 value = 14944486\nMAGGSIA1 value = 13865284\nMAGGSIU2 value = 9527311\nMAGGSIUI value = 12223625\nMAGGTU1 value = 4211501\nMAGIPS85 value = 5272602\n \nPlease note that routine MAGIPS85 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGBRTE4 value = 15548436\nMAGBRTE5 value = 10484128\nMAGBRTUT value = 10369180\nMAGDCCS value = 14379289\nMAGDGMRC value = 8758583\nMAGDHWS value = 8766948\n\n
\nSelect BUILD NAME: MAG*3.0*81 IMAGING\nMAGIP81 value = 4894048\nMAGQBPG1 value = 76244753\nMAGQBPRG value = 57300845\nMAGQBTM value = 79858508\nMAGQBUT1 value = 76309021\nMAGQBUT2 value = 55361113\nMAGQBUT4 value = 78049028\nMAGQBUT5 value = 15869460\n\n
\nRoutines for Patch 69, Test Build 34.\n \nRoutines:\nMAGIPS69 value = 5182371\n \nPlease note that routine MAGIPS69 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistARad patch 76\n\n
\nThis will check the routines from a BUILD file.\nMAGGSIA1 value = 40441705\nMAGGSIU2 value = 19991293\nMAGGSIUI value = 44173317\nMAGGSIV value = 39311019\nMAGGSIV1 value = 22249629\nMAGGTAU value = 53570032\nMAGGTERR value = 6185941\nMAGGTIA1 value = 34754160\nMAGGTID value = 44603396\nMAGGTII value = 43921962\nSelect BUILD NAME: MAG*3.0*59 IMAGING\nMAGGTLB1 value = 24325063\nMAGGTMC1 value = 10841224\nMAGGTPT1 value = 32058249\nMAGGTRA value = 11950621\nMAGGTSR value = 18209701\nMAGGTSR1 value = 6582516\nMAGGTSY2 value = 5995567\nMAGGTSYS value = 11307252\nMAGGTU1 value = 7410851\nMAGGTU3 value = 33146590\nMAGBAPIP value = 9049823\nMAGGTU31 value = 37368094\nMAGGTU4 value = 39449032\nMAGGTU41 value = 29145844\nMAGGTU6 value = 48411406\nMAGGTU71 value = 12408880\nMAGGTU9 value = 41693963\nMAGGTUP value = 22068923\nMAGGTUX value = 84671980\nMAGGTUX1 value = 47937341\nMAGGTUX2 value = 16893557\nMAGGNLKP value = 14546243\nMAGGTUX3 value = 20033133\nMAGIPS59 value = 30034575\nMAGLOG value = 8166700\nMAGSIXG1 value = 48513335\nMAGSIXGT value = 67629374\ndone\n \nTIU Enhancements patch.\nAdds functionality to Capture Application that will allow user to: \nCreate a New TIU Note\nMAGGNTI value = 37673155\nCreate an Addendum to an existing signed TIU Note.\nSet the status of the new note/addendum to\n - unsigned\n - administrative closure\n - Signed.\n \nDisplays the Note Title from the TIU Document file (8925) in the\n Image List Window of Imaging Display, this assures \ndisplay of the current Note title because Note Titles sometimes change.\n \nMAGGNTI1 value = 44242412\nImaging Display\n - Stops users that do not have an Imaging Display security from signing \non to Imaging Display. User needs either MAGDISP CLIN or\nMAGDISP ADMIN or both.\n \nImaging Capture\nAutomatically generates Index Values for new Images that do not have \nindex values as input data. This happens when Applications using the \nImport API or Imaging Capture Client versions prior to version 3.0.8\nIndex Term Fix:\nMAGGNTI2 value = 21199592\nIterate through the entire Image Global and Fix the Index Terms if\nType Index is missing.\nMAGGNTI3 value = 11336428\nMAGGSIA value = 37580788\n\n
\nVistA Imaging patch 96 - CCOW tag for VistAWeb and update for sensitive \npatient dialog.\n \nSelect BUILD NAME: MAG*3.0*96 IMAGING\nMAGGTU4 value = 40765395\nMAGIPS96 value = 5627154\n\n
\nRoutines for Patch 72, Test Build 30.\nPlease note that routine MAGIPS72 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGGTLB value = 13513235\nMAGGTSR value = 8087923\nMAGGTU4 value = 9896091\nMAGGTU6 value = 11332297\nMAGIPS72 value = 5934151\n \n\n
\nRoutines for Patch 75, Test Build 13.\n \nRoutines:\nMAGIPS75 value = 4828235\n \nPlease note that routine MAGIPS75 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 102, Test Build 2.\n \nRoutines:\nMAGIP102 value = 4827958\n \nPlease note that routine MAGIP102 is deleted after the KIDS Build is\ninstalled.\n\n
\nMUSE EKG maintenance\n \nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*95 IMAGING\nMAGGTU4 value = 40789937\nMAGIPS95 value = 12175146\n \ndone\n\n
\nThis is MAG*3.0*17T50.\nMAGXCVI1 value = 10939208\nMAGXCVL value = 16869656\nMAGXCVP value = 9695429\nMAGXCVR value = 16626305\nMAGXCVS value = 14244944\nMAGXCVX value = 8611516\n \nImage Index Conversion.\n \nMAGIPS17 value = 3287056\nMAGLOG value = 3474965\nMAGXCVC value = 15924595\nMAGXCVH value = 3688285\nMAGXCVI value = 11055898\n\n
\nRoutines for Patch 103, Test Build 2.\n \nRoutines:\nMAGIP103 value = 4827966\n \nPlease note that routine MAGIP103 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 54, Test Build 40.\nMAGDCCU1 value = 8041167\nMAGDHL7 value = 7011790\nMAGDHLE value = 4675728\nMAGDHRC0 value = 4527100\nMAGDHWC value = 12121799\nMAGDHWS value = 8776710\nMAGDIR8 value = 5249219\nMAGDIR81 value = 16249703\nMAGDIR82 value = 13986318\nMAGDIR83 value = 8305683\n \nMAGDIR84 value = 7051552\nMAGDIR9A value = 11702546\nMAGDIR9B value = 7619455\nMAGDIR9E value = 14977047\nMAGDIRVE value = 15724398\nMAGDLB1 value = 12075022\nMAGDLBAA value = 6712810\nMAGDMEDL value = 6951528\nMAGDQR00 value = 2548544\nMAGDQR01 value = 11135896\nRoutines:\nMAGDQR02 value = 14306691\nMAGDQR03 value = 17339843\nMAGDQR04 value = 14824047\nMAGDQR05 value = 10792454\nMAGDQR06 value = 7405913\nMAGDQR07 value = 10362545\nMAGDQR08 value = 8854962\nMAGDRA2 value = 7976145\nMAGDRCU1 value = 8596186\nMAGDRCU2 value = 9821221\nMAG7UM value = 8243232\nMAGDRPC1 value = 9674272\nMAGDRPC2 value = 13440631\nMAGDRPC3 value = 14608057\nMAGDRPC4 value = 17974720\nMAGDRPC5 value = 15092525\nMAGDRPC6 value = 11312515\nMAGDRPC7 value = 9459019\nMAGDRPC8 value = 11952944\nMAGDRPC9 value = 11126815\nMAGDRUID value = 2900467\nMAGBRTE4 value = 15309819\nMAGDTR02 value = 11542094\nMAGDTR03 value = 17495982\nMAGDTR05 value = 12670562\nMAGDTR06 value = 10445490\nMAGDUID3 value = 3204144\nMAGENCHK value = 3430893\nMAGIPS54 value = 11466893\nMAGUE001 value = 4780297\nMAGUE002 value = 3962070\nMAGUE003 value = 2916905\nMAGBRTE5 value = 11533293\nMAGVCHK value = 8124399\nMAGXCVC value = 12902535\nMAGXCVI value = 12650053\nMAGXCVP value = 10064211\nMAGXCVR value = 16926210\nMAGXCVS value = 18315672\nMAGXIDXU value = 21366591\n \nPlease note that routine MAGIPS54 is deleted after the KIDS Build is\ninstalled.\nMAGBRTUT value = 10523100\nMAGDCCS value = 14420572\nMAGDCCS2 value = 6833559\n\n
\nVistARad patch 101\n\n
\nCode for the Clinical Display and Capture.\nMAGGA03A value = 24276061\nMAGGA03U value = 15820919\nMAGGA04 value = 10448835\nMAGGAII value = 118384476\nMAGGI11 value = 19558450\nMAGGI12 value = 30285951\nMAGGI13 value = 36748899\nMAGGI14 value = 39084079\nMAGGNTI value = 37753394\nMAGGSFL1 value = 17534133\n \nMAGGSFLT value = 33107414\nMAGGSIA value = 34720134\nMAGGSIA1 value = 40524442\nMAGGSQI value = 71964647\nMAGGTAU value = 66867957\nMAGGTIA1 value = 33003499\nMAGGTID value = 47456559\nMAGGTIG value = 58640406\nMAGGTPT1 value = 37889156\nMAGGTRAI value = 29892001\n \nMAGGTRPT value = 43638944\nMAGGTSYS value = 11574384\nMAGGTU3 value = 34334075\nMAGGTU31 value = 41847617\nMAGGTU4 value = 53401008\nMAGGTU41 value = 22378971\nMAGGTU42 value = 89107061\nMAGGTU4C value = 5489850\nMAGGTU4D value = 5495655\nMAGGTU4L value = 4501110\nRoutines:\nMAGGTU4T value = 5490003\nMAGGTU6 value = 51862098\nMAGGTU7 value = 23284378\nMAGGTUP value = 23999096\nMAGGTUX value = 85905158\nMAGIPS93 value = 176674164\nMAGKIDS value = 30231662\nMAGKIDS1 value = 40480221\nMAGSIXG1 value = 36487191\nMAGSIXG2 value = 63440737\n \nMAGSIXG3 value = 65195475\nMAGSIXG4 value = 12614135\nMAGUERR value = 24572740\nMAGUERR1 value = 25613179\nMAGUTL01 value = 28612084\nMAGUTL02 value = 48311130\nMAGUTL03 value = 11647866\nMAGUTL04 value = 23169366\nMAGUTL05 value = 18410909\nMAGUTL06 value = 18816077\nMAGGA01 value = 29307935\nMAGUTL07 value = 22761121\nMAGUTL08 value = 26051030\nMAGUTL10 value = 8165500\nMAGUXRF value = 41195502\nMAGGA02 value = 57822621\nMAGGA02A value = 40367747\nMAGGA03 value = 45753507\n\n
\nRoutines for Patch 111, Test Build 2.\n \nRoutines:\nMAGIP111 value = 4459800\nMAGS2BSE value = 2910061\n \nPlease note that routine MAGIP111 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 83, Test Build 34.\ninstalled.\n \nRoutines:\nMAGDQR21 value = 20769614\nMAGGTII value = 9489602\nMAGIPS83 value = 6840204\nMAGLOG value = 5040605\n \nPlease note that routine MAGIPS83 is deleted after the KIDS Build is\n\n
\nRoutines for Patch 108, Test Build 4.\nMAGNVIC value = 3535084\nMAGSIXGT value = 14416655\n \nPlease note that routine MAGIP108 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGGNTI value = 16297431\nMAGGSIU1 value = 5727576\nMAGGSIU2 value = 15503269\nMAGGSIUI value = 14029420\nMAGGSIV value = 16492919\nMAGIP108 value = 6746401\n\n
\nRoutines for Patch 90, Test Build 9.\nMAGJTU4V value = 3478059\nMAGJUTL3 value = 19746308\nMAGJUTL4 value = 21177891\nMAGJUTL5 value = 15130172\nMAGJVAPI value = 5546355\nMAGS2BSE value = 2835335\n \nRoutines:\nMAGGTU41 value = 5443844\nMAGJLS2 value = 25461554\nMAGJLS2B value = 20391246\nMAGJLS3 value = 18365062\nMAGJLST1 value = 16179057\nMAGJMN1 value = 18586606\n\n
\nRoutines for Patch 53, Test Build 29.\nMAGDIR9B value = 7655058\nMAGDLBAA value = 8068461\nMAGDRPC9 value = 13044987\nMAGDRPCA value = 17799839\nMAGDRPCB value = 19465055\nMAGIPS53 value = 5286805\n \nPlease note that routine MAGIPS53 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGBRTK value = 7352676\nMAGDAIRF value = 8123428\nMAGDAIRG value = 10868841\nMAGDIR81 value = 17308670\nMAGDIR8R value = 11763503\nMAGDIR9A value = 11731498\n\n
\nRoutines for Patch 94, Test Build 12.\nMAGGTU4D value = 3409945\nMAGGTU4L value = 3410009\nMAGGTU4T value = 3410073\nMAGGTUP value = 7812293\nMAGIPS94 value = 4941586\n \nPlease note that routine MAGIPS94 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGGAII value = 14524600\nMAGGI12 value = 7084999\nMAGGSFT value = 4413235\nMAGGTU4 value = 10296457\nMAGGTU42 value = 16116783\nMAGGTU4C value = 3409937\n\n
\nEnhancement patch for MAG ENTERPRISE:\nMAGQST value = 7876444\nMAGUSIT value = 12029601\n \nPlease note that routine MAGIPS19 is a KIDs post install routine and is \ndeleted after the KIDs install.\n \nRoutine checksums:\nMAGIPS19 value = 2463407\nMAGQBPG1 value = 12228392\nMAGQBUT value = 13147026\nMAGQBUT2 value = 15518936\nMAGQBUT4 value = 14489519\nMAGQBUT5 value = 9940521\n\n
\nRoutines for Patch 114, Test Build 11.\ninstalled.\n \nRoutines:\nMAGDDR value = 2636969\nMAGIP114 value = 7030232\nMAGNTLR2 value = 8297941\nMAGNTLRS value = 20095042\n \nPlease note that routine MAGIP114 is deleted after the KIDS Build is\n\n
\nRoutines for Patch 66, Test Build 71.\n \nPlease note that routine MAGIPS66 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDQR01 value = 11855515\nMAGDQR02 value = 14336295\nMAGDQR03 value = 18389209\nMAGDQR04 value = 15180168\nMAGDQR06 value = 7032267\nMAGIPS66 value = 6107571\n\n
\nRoutines for Patch 105, Test Build 14.\n \nRoutines:\nMAGIP105 value = 4466156\n \nPlease note that routine MAGIP105 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 98, Test Build 24.\nMAGSHEC value = 6865882\nMAGUF value = 5557376\n \nPlease note that routine MAGIPS98 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDOD01 value = 13883245\nMAGGDEV value = 5858674\nMAGIPS98 value = 2969837\nMAGSDEL5 value = 15686852\nMAGSDOFL value = 12685934\nMAGSFTCH value = 38894121\n\n
\nRoutines for Patch 115, Test Build 4.\n \nRoutines:\nMAGJEX1 value = 25703195\nMAGJMN1 value = 19116251\nMAGJPRF1 value = 22808620\nMAGJTU4V value = 3477480\nMAGJUTL5 value = 15135475\nMAGJVAPI value = 5898333\n\n
\nRoutines for Patch 106, Test Build 13.\nMAGGTU4T value = 3511363\nMAGIP106 value = 3993590\nMAGNDCMC value = 5330392\nMAGNGMR value = 13876633\nMAGNTLR3 value = 2994749\nMAGNUID1 value = 6357640\nMAGNUID2 value = 2830351\nMAGUXRF value = 6191185\n \nPlease note that routine MAGIP106 is deleted after the KIDS Build is\n \ninstalled.\nRoutines:\nMAGDHWC value = 12231552\nMAGGSIA1 value = 13960534\nMAGGTIA value = 12401847\nMAGGTU4C value = 3511227\nMAGGTU4D value = 3511235\nMAGGTU4L value = 3511299\n\n
\nRoutines for Patch 39, Test Build 28.\nMAGLOG value = 6505482\nMAGQBAB value = 6248046\nMAGQBD value = 4804096\nMAGQBGCC value = 9817430\nMAGQBIM value = 5640879\nMAGQBJB value = 7946372\nMAGQBJH value = 9334687\nMAGQBPG1 value = 17587779\nMAGQBPG2 value = 7742906\nMAGQBPRG value = 11705676\n \nMAGQBTM value = 16348461\nMAGQBU6A value = 21126520\nMAGQBUT value = 30554887\nMAGQBUT1 value = 23611991\nMAGQBUT2 value = 17468675\nMAGQBUT4 value = 13069038\nMAGQBUT5 value = 18100543\nMAGQBUT6 value = 29900309\nMAGQCBP value = 25623703\nMAGQE1 value = 5411143\nRoutines:\nMAGQE2 value = 6604569\nMAGQE5 value = 13439984\nMAGQE6 value = 7370203\nMAGQE7 value = 15755110\n \nPlease note that routine MAGIP39 is deleted after the KIDS Build is\ninstalled.\n \nPlease note that routine MAGIP39B is deleted after the KIDS Build is\ninstalled.\nMAGBAPI value = 17337697\nMAGBRTE4 value = 15016927\nMAGFILEB value = 11899853\nMAGIP39 value = 15355104\nMAGIP39B value = 33707188\nMAGIP39E value = 9567529\n\n
\nRoutines for Patch 49, Test Build 32.\nMAGDHLSO value = 4951039\nMAGDHLSV value = 15085746\nMAGDHLT value = 3638769\nMAGDHLTA value = 7653532\nMAGDHLTC value = 6732337\nMAGDHPS value = 10198148\nMAGDHRC0 value = 4547517\nMAGDHW0 value = 4192697\nMAGDHWA value = 11046156\nMAGDHWR value = 4356893\n \nMAGDIR8A value = 10347815\nMAGDIR8R value = 11916565\nMAGDIR9A value = 13157136\nMAGDRA2 value = 8580195\nMAGDRA3 value = 4189221\nMAGDRAHL value = 4739804\nMAGDRPC1 value = 9912701\nMAGDRPC3 value = 13481361\nMAGDRPC4 value = 14864088\nMAGDRPC9 value = 12920297\nRoutines:\nMAGDRUID value = 2900467\nMAGENV49 value = 4103690\nMAGIPS49 value = 5298688\n \nPlease note that routine MAGIPS49 is deleted after the KIDS Build is\ninstalled.\nMAG7UCFG value = 8010888\nMAG7UD value = 3154695\nMAGDHLE value = 5022942\nMAGDHLI value = 3542011\nMAGDHLL value = 4260332\nMAGDHLS value = 13291597\n\n
\nRoutines for Patch 117, Test Build 8.\nMAGGSIA1 value = 14320770\nMAGGTIA value = 12826247\nMAGGTIG value = 11417887\nMAGGTPT1 value = 10179062\nMAGGTRA value = 6187130\nMAGGTSY2 value = 3755850\nMAGGTSYS value = 6588238\nMAGGTU3 value = 8835971\nMAGGTU31 value = 13894838\nMAGGTU4C value = 3412178\n \nMAGGTU4D value = 3412186\nMAGGTU4L value = 3412250\nMAGGTU4T value = 3412314\nMAGGTU6 value = 11375864\nMAGGTUP value = 8164993\nMAGGTUX4 value = 5440465\nMAGGUJB value = 6496246\nMAGIP117 value = 5023042\nMAGSIXG1 value = 7218955\nMAGSIXG3 value = 13563632\nRoutines:\nMAGUXDPS value = 7753193\n \nPlease note that routine MAGIP117 is deleted after the KIDS Build is\ninstalled.\nMAGGA02 value = 10126913\nMAGGA02A value = 13686263\nMAGGA03Q value = 10905306\nMAGGA03U value = 4998553\nMAGGI13 value = 7845276\nMAGGROI value = 4826920\n\n
\nRoutines for Patch 99, Test Build 14.\nMAGZTEMP2 value = 12401847\n \nPlease note that routine MAGIPS99 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDIR9A value = 13157136\nMAGDIR9B value = 7763588\nMAGDIR9E value = 15337169\nMAGGTIA value = 11668616\nMAGIPS99 value = 6388466\nMAGZTEMP1 value = 12826247\n\n
\nImaging Site Usage reportinge reporting reporting.\nRoutine MAGIPS27 is deleted once the KIDs installation is complete. \n \nMAGIPS27 value = 5542226\nMAGQE1 value = 7724807\nMAGQE2 value = 8875505\nMAGQE3 value = 13373823\nMAGQE4 value = 7634179\nMAGQE5 value = 12363260\n \n\n
\nRoutines for Patch 104, Test Build 5.\n \nPlease note that routine MAGIP104 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDQR21 value = 22992217\nMAGIP104 value = 3117560\nMAGJEX1 value = 22704581\nMAGJEX1B value = 9507612\nMAGJUTL2 value = 14194819\nMAGJUTL5 value = 16389058\n\n
\nRoutines for Patch 121, Test Build 2.\nMAGQBUT4 value = 13069038\n \nPlease note that routine MAGIP121 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGGSIA1 value = 15138596\nMAGGSIU4 value = 13298331\nMAGGSIU5 value = 8121967\nMAGGSIUI value = 14513807\nMAGGSIV value = 16267430\nMAGIP121 value = 3771935\n\n
\nRoutines for Patch 120, Test Build 8.\nMAGJMN3 value = 3776166\nMAGJRPT value = 25862262\nMAGJTU4V value = 3585975\nMAGJUPD1 value = 19589826\nMAGJUTL2 value = 17540135\nMAGJUTL3 value = 20682689\nMAGJUTL4 value = 21304219\nMAGJUTL5 value = 16379041\n \nRoutines:\nMAGJEX1 value = 23534520\nMAGJEX1A value = 24904344\nMAGJEX2 value = 13889635\nMAGJLS3 value = 18509439\nMAGJLST1 value = 14882477\nMAGJMN1 value = 19373467\n\n
\nRoutines for Patch 122, Test Build 15.\nMAGGTPT1 value = 12237253\nMAGGTRPT value = 11915258\nMAGGTU4C value = 3512766\nMAGGTU4D value = 3512774\nMAGGTU4L value = 3512838\nMAGGTU4T value = 3512902\nMAGGTUP value = 8435949\nMAGIP122 value = 4915830\nMAGSANNO value = 18481118\nMAGSPID value = 2819774\n \n \nPlease note that routine MAGIP122 is deleted after the KIDS Build is\ninstalled.\nRoutines:\nMAGDRPC1 value = 9975466\nMAGGA03Q value = 11636461\nMAGGAII value = 20413618\nMAGGI12 value = 11845551\nMAGGI13 value = 10164161\nMAGGNTI value = 16354280\n\n
\nRoutines for Patch 123, Test Build 7.\nMAGDIR8A value = 10581895\nMAGDLB1 value = 12766001\nMAGDLB12 value = 8198942\nMAGDLB9 value = 4969298\nMAGDLBAA value = 8118057\nMAGDQR03 value = 18464598\nMAGDQR04 value = 15569898\nMAGDQR21 value = 23288835\nMAGDRA1 value = 8062807\nMAGDRA2 value = 9317212\n \nMAGDRAHL value = 4631070\nMAGDRPC3 value = 13904592\nMAGDRPC9 value = 13063850\nMAGDRPCA value = 18609605\nMAGDTR05 value = 12846226\nMAGIP123 value = 2905275\nMAGSPID value = 2839275\n \nPlease note that routine MAGIP123 is deleted after the KIDS Build is\ninstalled.\nRoutines:\nMAG7RS value = 13135219\nMAGDCCS value = 14748319\nMAGDCCS2 value = 7524490\nMAGDCCSD value = 5307168\nMAGDHLS value = 14585928\nMAGDIR81 value = 17859818\n\n
\nRoutines for Patch 124, Test Build 9.\n \nRoutines:\nMAGIP124 value = 4559147\n \nPlease note that routine MAGIP124 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 127, Test Build 9.\nMAGNTLR2 value = 9701399\nMAGNTLR4 value = 4675421\nMAGNTLR5 value = 3700659\nMAGNTLR6 value = 5942558\nMAGNTLRS value = 18148694\n \nPlease note that routine MAGIP127 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDTR01 value = 10127414\nMAGDTR03 value = 17783950\nMAGDTR04 value = 8787958\nMAGDTR05 value = 14098871\nMAGGTU4T value = 3613054\nMAGIP127 value = 4678258\n\n
\nRoutines for Patch 34, Test Build 35.\n \nRoutines:\nMAGIPS34 value = 2886768\n \nPlease note that routine MAGIPS34 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 116, Test Build 35.\n \nRoutines:\nMAGIP116 value = 2886566\n \nPlease note that routine MAGIP116 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 118, Test Build 35.\nMAGDQR01 value = 10215111\nMAGVRS21 value = 2823667\nMAGVRS24 value = 4410330\nMAGVRS31 value = 3079264\nMAGVRS41 value = 30228912\nMAGVRS42 value = 12201505\nMAGVRS43 value = 7578338\nMAGVRS44 value = 13926434\nMAGVRS45 value = 5247038\nMAGVRS46 value = 5857183\nMAGVRS51 value = 18061747\nMAGDQR02 value = 14623747\nMAGVRS52 value = 9106742\nMAGVRS61 value = 17820732\nMAGVRS71 value = 3184401\nMAGVRS81 value = 8694832\nMAGVRS82 value = 7085769\nMAGVSOPC value = 4221335\nMAGVSOPU value = 48817298\nMAGVSTDY value = 3494166\nMAGVUID value = 16416361\nMAGVUID1 value = 3192862\nMAGDQR03 value = 26241944\n \nPlease note that routine MAGIP118 is deleted after the KIDS Build is\ninstalled.\nMAGDQR04 value = 22474528\nMAGDQR05 value = 12458785\nMAGDQR06 value = 12808429\nMAGDQR07 value = 3462324\nMAGDQR08 value = 11135227\nMAGDQR09 value = 9701238\nMAGDQR10 value = 5838068\n \nMAGDQR11 value = 4093753\nMAGDQR12 value = 6766715\nMAGDQR13 value = 10738725\nMAGDQR22 value = 5932725\nMAGDQR23 value = 3787648\nMAGDQR31 value = 5530671\nMAGDQR32 value = 4894421\nMAGDQR71 value = 3683372\nMAGDQR72 value = 4232194\nMAGDQR73 value = 4336726\nRoutines:\nMAGDQR74 value = 4916336\nMAGDQRUE value = 3231286\nMAGDQRUL value = 5075915\nMAGDRPC8 value = 12088901\nMAGDRPC9 value = 15300257\nMAGDRPCA value = 18858560\nMAGDRPCB value = 19610086\nMAGFXQRS value = 3528617\nMAGGTID value = 15318885\nMAGIP118 value = 16658406\nMAGDCCS value = 14748319\nMAGJUTL6 value = 5235694\nMAGKIDS1 value = 8496976\nMAGUAUD value = 3432831\nMAGUE001 value = 5265937\nMAGUE002 value = 4127699\nMAGUE004 value = 2837439\nMAGUE005 value = 2768991\nMAGUFFLA value = 4780171\nMAGUFFLL value = 3976859\nMAGUPSE value = 3173130\nMAGDGMRC value = 9330669\nMAGURQRS value = 3271458\nMAGVAC01 value = 9767703\nMAGVAD01 value = 2734865\nMAGVAD02 value = 4280272\nMAGVAF01 value = 13045577\nMAGVAF02 value = 3488127\nMAGVAF03 value = 19053073\nMAGVAF04 value = 2921702\nMAGVAF05 value = 4899077\nMAGVAG01 value = 2797051\nMAGDLB1 value = 12761979\nMAGVAG02 value = 12435913\nMAGVAG03 value = 15139645\nMAGVAG04 value = 14868843\nMAGVAKL1 value = 7388351\nMAGVAQ01 value = 16822050\nMAGVAQ02 value = 10394360\nMAGVAU01 value = 5159205\nMAGVD001 value = 7603789\nMAGVD002 value = 4124064\nMAGVD003 value = 4420661\nMAGDLB6 value = 3631343\nMAGVD004 value = 4488582\nMAGVD005 value = 3174483\nMAGVD006 value = 5561142\nMAGVD007 value = 3685164\nMAGVD008 value = 3954473\nMAGVD010 value = 5632336\nMAGVDATE value = 3369336\nMAGVDGWP value = 17603694\nMAGVGUID value = 9565266\nMAGVIM01 value = 30059037\nMAGDMEDJ value = 10380972\nMAGVIM02 value = 13662782\nMAGVIM03 value = 9162433\nMAGVIM04 value = 11718870\nMAGVIM05 value = 15242382\nMAGVIM06 value = 12862098\nMAGVIM07 value = 15335247\nMAGVIM08 value = 4973894\nMAGVIM09 value = 5293910\nMAGVIM10 value = 8365751\nMAGVORDR value = 7090722\nMAGDQR00 value = 2610540\nMAGVRS01 value = 2771259\nMAGVRS04 value = 2988202\nMAGVRS05 value = 2843603\nMAGVRS06 value = 2963783\nMAGVRS07 value = 3017184\nMAGVRS08 value = 13251433\nMAGVRS09 value = 3304082\nMAGVRS11 value = 2822694\nMAGVRS14 value = 3873307\nMAGVRS15 value = 3427655\n\n
\nThis is MAG*3.0*25.\nMAGXCVI1 value = 11438388\nMAGXCVL value = 7336670\nMAGXCVP value = 9644213\nMAGXCVR value = 16855671\nMAGXCVS value = 15637378\nMAGXCVX value = 9302002\n \nImage Index Conversion.\n \nMAGIPS25 value = 3992054\nMAGXCVC value = 12676908\nMAGXCVE value = 16646332\nMAGXCVH value = 3720499\nMAGXCVI value = 10664148\n\n
\nRoutines for Patch 119, Test Build 4.\nPlease note that routine MAGIP119 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGDQR20 value = 15221835\nMAGDQR21 value = 23569984\nMAGGDEV value = 5937314\nMAGGTUX5 value = 3577043\nMAGIP119 value = 3152330\n \n\n
\nRoutines for Patch 129, Test Build 18.\n \nRoutines:\nMAGGNTI value = 16501984\nMAGGTU4C value = 3613451\nMAGIP129 value = 2888745\n \nPlease note that routine MAGIP129 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 140\n \nRoutines:\nMAGIP140 value = 13676169\nMAGGTU4C value = 5540791\n \nPlease note that routine MAGIP140 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 131,\n \nRoutines:\nMAGIP131 value = 3414337\nMAGGTU4D value = 5508411\nMAGGTPT1 value = 59311646\n \nPlease note that routine MAGIP131 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 133, Test Build 3.\nMAGJUTL3 value = 139481284\nMAGJUTL5 value = 38140374\n \nRoutines:\nMAGJEX1 value = 73078692\nMAGJMN1 value = 98640707\nMAGJRPT value = 103626332\nMAGJTU4V value = 5405270\nMAGJUPD1 value = 64000428\nMAGJUTL1 value = 71279028\n\n
\nRoutines for Patch 135, Test Build 10.\nMAGQBPRG value = 12188271\nMAGQBTM value = 16822600\nMAGQBUT1 value = 23584558\nMAGQBUT4 value = 13069038\nMAGQE3 value = 15906384\nMAGSDOFF value = 11766065\nMAGSDOFL value = 13348358\n \nPlease note that routine MAGIP135 is deleted after the KIDS Build is\ninstalled.\n \nRoutines:\nMAGBRTE4 value = 15105909\nMAGGSIU4 value = 13652811\nMAGGSIU5 value = 8305153\nMAGIP135 value = 7151218\nMAGQBPG1 value = 22947623\nMAGQBPG2 value = 7983035\n\n
\nVistA Imaging V3.0 Patch 143 - Import API OCX fix\n \n \nRoutines:\nMAGIP143 new value = ?\n \nPlease note that routine MAGIP143 is deleted after the KIDS Build is\ninstalled.\n\n
\nVistA Imaging V3.0 Patch 141 - HL7 Version 2.4 Corrections\nPlease note that routine MAGIP141 is deleted after the KIDS Build is\ninstalled.\n \n \nRoutines:\nMAGDFCNV new value = 13765242\nMAGDHLS new value = 78648405\nMAGDHLSV new value = 58263891\nMAGIP141 new value = 4110371\n \n\n
\nMAG_INDEX_TERMS UPDATE\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n------------------------------------------\n \n(INACTIVE for VA, ACTIVE for IHS) RID:262 Birth Certificate\nIHS sites would like to scan in Birth Certificates for various Admin \n \nfunctions and do not want to use miscellaneous as choice.\n \n \n \n \n \n\n
\nVersion 3.0 Patch 147 - Pixel Representation fix\n \n \nRoutines:\nMAGIP147 new value = 4110425\n \nPlease note that routine MAGIP147 is deleted after the KIDS Build is\ninstalled.\n\n
\nImaging Patch 22 -- Vistarad Maintenance\nMAGJMN1 value = 16954953\nMAGJORD value = 7481199\nMAGJRT value = 11832101\nMAGJUPD1 value = 17310296\nMAGJUTL1 value = 11539488\nMAGJUTL3 value = 9066809\nRoutine Checksums:\n \nMAGJEX1 value = 25378323\nMAGJEX1B value = 6070161\nMAGJLS2 value = 17792693\nMAGJLS2B value = 18169808\nMAGJLS3 value = 17053988\nMAGJLST1 value = 28230644\n\n
\nRoutines for Patch 87, Test Build 18.\n \nRoutines:\nMAGIPS87 value = 10146838\n \nPlease note that routine MAGIPS87 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 79, Test Build 18.\n \nRoutines:\nMAGIP079 value = 9797469\n \nPlease note that routine MAGIP079 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 110, Test Build 18.\n \nRoutines:\nMAGIP110 value = 4178905\n \nPlease note that routine MAGIP110 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 130, Test Build 18.\n \nRoutines:\nMAGIP130 value = 4056978\n \nPlease note that routine MAGIP130 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 137, Test Build 18.\n \nRoutines:\nMAGIP137 value = 4110417\n\n
\nRoutines for Patch 136, Test Build 18.\n \nRoutines:\nMAGIP136 value = 4697252\n \nPlease note that routine MAGIP136 is deleted after the KIDS Build is\ninstalled.\n\n
\nRoutines for Patch 138, Test Build 18.\nMAGDHLSV value = 58263891\nMAGTP007 value = 9622736\nMAGTP008 value = 12310637\nMAGTP009 value = 27179756\nMAGTP011 value = 28753443\nMAGTP013 value = 25065830\nMAGTP014 value = 23306962\nMAGUE006 value = 5793789\nMAGUE007 value = 7091388\nMAGUTERR value = 6322281\nMAGVIM02 value = 175056405\nMAGDHOW0 value = 10465024\nMAGVORDR value = 29337951\n \nPlease note that routine MAGIP138 is deleted after the KIDS Build is\ninstalled.\nMAGDHOW1 value = 26357227\nMAGDHOW2 value = 45184797\nMAGDHOW3 value = 27085242\nMAGDHOW4 value = 28473404\nMAGDHOW5 value = 34385390\nMAGDHOWA value = 36363777\nMAGDHOWC value = 33384506\nMAGDHOWE value = 99382335\n \nMAGDHOWS value = 11945066\nMAGDIR8 value = 11537939\nMAGDIR9E value = 79245586\nMAGDIWDV value = 19916483\nMAGDIWDX value = 30251763\nMAGDQR03 value = 216286453\nMAGDQR05 value = 49941837\nMAGDQR06 value = 59291840\nMAGDQR07 value = 4766521\nMAGDQR08 value = 59589471\nRoutines:\nMAGDQR73 value = 7054630\nMAGDRAHL value = 7989896\nMAGDRCU1 value = 29588459\nMAGDRCU2 value = 37880955\nMAGDRPC1 value = 49239029\nMAGDRPC4 value = 98879749\nMAGDRPC8 value = 64566169\nMAGDRPC9 value = 97645794\nMAGDRPCA value = 79625346\nMAGDRPCB value = 130297847\nMAG7RS value = 54519012\nMAGDRPCC value = 14382786\nMAGDTRDX value = 38833590\nMAGGSQI value = 72674359\nMAGNTLR2 value = 44630345\nMAGNTLR7 value = 13154680\nMAGVD001 value = 17941768\nMAGVD003 value = 7859463\nMAGVGUID value = 34710129\nMAGVIM06 value = 75204201\nMAGVRS43 value = 12239362\nMAGDCCS2 value = 18497178\nMAGVCAE value = 15420636\nMAGVCQRY value = 42068357\nMAGVCWIA value = 103244779\nMAGVIM09 value = 12262639\nMAGVRS51 value = 83190117\nMAGVRS52 value = 26054043\nMAGVIM01 value = 190017162\nMAGVIM05 value = 141244825\nMAGVIM10 value = 21368167\nMAGVIMRA value = 24367242\nMAGDFCNV value = 13765242\nMAGVUID value = 59224341\nMAGVUID2 value = 9557377\nMAGVRD01 value = 12392246\nMAGVRD02 value = 10515156\nMAGVRD03 value = 18143435\nMAGGTU4D value = 5507577\nMAGROI01 value = 20754112\nMAGGI12 value = 101354711\nMAGGTAU value = 66527291\nMAGGTID value = 83741782\nMAGDGMRC value = 23141065\nMAGGTPT1 value = 59311646\nMAGLOG value = 12957603\nMAGSIXG3 value = 81619873\nMAG7UNM value = 4937883\nMAGIP138 value = 245480718\nMAGI138O value = 56001068\nMAGDIR81 value = 110585980\nMAGDIR8A value = 45934196\nMAGDIR9A value = 63886585\nMAGDIR9F value = 58270523\nMAGDHLL value = 8663546\nMAGDRPC3 value = 65697385\nMAGGTIA2 value = 19378485\nMAGGTU6 value = 52891889\nMAGNTLRS value = 194558311\nMAGT7MA value = 117303477\nMAGT7S value = 33454697\nMAGT7SB value = 21850604\nMAGT7SI value = 13003738\nMAGT7SN value = 13407430\nMAGT7SO value = 35017277\nMAGDHLS value = 78648405\nMAGT7SP value = 40182060\nMAGT7SS value = 22952843\nMAGT7SSA value = 35520944\nMAGT7ST value = 5954594\nMAGT7SV value = 12817677\nMAGT7SX value = 12327921\nMAGTP003 value = 13897047\nMAGTP004 value = 63629002\nMAGTP005 value = 12289427\nMAGTP006 value = 13622610\n\n
\nVistA Imaging V3.0 Patch 149 - Print Issues\nMAGIP149 value = 4215025\ndone\nPlease note that routine MAGIP149 is deleted after the KIDS Build is\ninstalled.\n \nThis Patch includes a new Clinical Display Client\nChanges in the Clinical Display client will address the\nissues of 'fuzzy' or 'granular' printed images.\nRoutines in Patch 149:\nThis will check the routines from a BUILD file.\nSelect BUILD NAME: MAG*3.0*149 IMAGING\nMAGGTU4D value = 5109435\n\n
\nVistA Imaging V3.0 Patch 155 MAG INDEX TERMS UPDATE\n \nExisting Procedure/Event: IV\nadd to Specialty: Radiology\n \nNew Specialty: Sleep Medicine\nAssociate with existing Procedure/Events: Visit and Sleep Study\n \nThis Patch includes 2 new index terms\nNew Procedure/Event: CT Angiography\n Abbreviation: CTA\n Specialty: Radiology\n \nExisting Procedure/Event: Acupuncture\nadd to Specialty: Chiropratic\n\n
\nVISTA Imaging V 3.0. This build includes all files required for a complete\ninstallation of Vista Imaging Clinical (Capture and Display) and VistARad.\n \nInformation on VistA Imaging is available on web page\nhttp://vawww.domain.ext/imaging/\n\n
\nCMOR REQUEST FIXES\nRefer to patch MPIF*1.0*11 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSelection screen and Misc changes\nRefer to patch MPIF*1.0*17 in the FORUM Patch Module for a complete\ndescription.\n\n
\nEnhancement Project Patch\nRefer to patch MPIF*1.0*21 in the FORUM Patch Module for a complete\ndescription.\n\n
\nRemote Procedures\nRefer to patch MPIF*1.0*20 in the FORUM Patch Module for a complete \ndescription.\n\n
\nSPI ACTION NAME CHANGE AND TF LIST ERROR IN SPI AND DISPLAY ONLY \nQUERY\nRefer to patch MPIF*1.0*23 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNEW MESSSAGE STRUCTURE - PHASE 1\nRefer to patch MPIF*1*22 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNEW MESSSAGE STRUCTURE - PHASE 2\nRefer to patch MPIF*1*24 in the FORUM Patch Module for a complete\ndescription.\n\n
\nAICNL FIX AND DISPLAY MSG\nRefer to patch MPIF*1*26 in the FORUM Patch Module for a complete\ndescription.\n\n
\nNEW SEEDING, DOUBLE MSGS, LOCALS, MISSING CMOR TF\nRefer to patch MPIF*1.0*27 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI CHANGES - ITERATION 1\nRefer to patch MPIF*1.0*28 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee Patch Module for patch description.\n\n
\nCHANGE ROUTING FOR CMOR CHANGE MSGS\nRefer to patch MPIF*1.0*30 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch adds functionality to the Local/Missing ICN Resolution \nBackground Job [MPIF LOC/MIS ICN RES] option and the Single Patient \nInitialization to MPI [MPIF IND MPI LOAD] option to add the Treating \nFacility list.\n\n
\nCMOR SCREEN FIX\nRefer to patch MPIF*1.0*32 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCMOR CHANGE REQUEST AND INSTITUTIONS\nRefer to patch MPIF*1.0*34 in the FORUM Patch Module for a complete\ndescription.\n\n
\nFHIE AND ZPD SEGMENT ADDED FOR POW STATUS\nRefer to patch MPIF*1*25 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOVE SOME MPI SCREENS - MPI CHANGES ITERATION 2\nRefer to patch MPIF*1.0*33 in the FORUM Patch Module for a complete\ndescription.\n\n
\nRPC to PUSH CMOR from MPI and Remote Sync of Data\nRefer to patch MPIF*1*36 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSUPPORTING HDR\nRefer to patch MPIF*1.0*29 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI CHANGES ITERATION 2 - REST OF TASK #9\nRefer to patch MPIF*1*35 in the FORUM Patch Module for a complete\ndescription.\n\n
\nVTQ changed to VQQ in Real-Time MPI Queries\nRefer to patch MPIF*1.0*38 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCHANGE TO IDENTITY MANAGEMENT FIELDS\nRefer to patch MPIF*1*37 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCHANGE TO HL7 ADT-A24 AND ADT-A43 MESSAGE PROCESSING\nRefer to patch MPIF*1*41 in the FORUM Patch Module for a complete\ndescription.\n\n
\nRPC TO FIND LEGACY PATIENT IN PRIMARY VISTA\nRefer to patch MPIF*1*42 in the FORUM Patch Module for a complete\ndescription.\n\n
\nICN ASSIGNMENT CHANGE/REMOVE SINGLE PATIENT INITIALIZATION OPTION\nRefer to patch MPIF*1*43 in the FORUM Patch Module for a complete\ndescription.\n\n
\nICN CHECKSUM ISSUE\nRefer to patch MPIF*1*45 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI CHANGES 3 & MPI CHANGES 4 ENHANCEMENTS\nRefer to patch MPIF*1*44 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMPI CHANGES 4 - FROM IMDQ UAT TESTING\nRefer to patch MPIF*1*46 in the FORUM Patch Module for a complete\ndescription.\n\n
\nLOCAL/MISSING ICN JOB CHANGE FOR LOCALS NOT RESOLVED\nRefer to patch MPIF*1*39 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCAPTURE DATE/TIME AND WHO MARKED EXCEPTION PROCESSED\nRefer to patch MPIF*1*48 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nIDENTITY HUB CHANGES FOR MPI VISTA\nRefer to patch MPIF*1*52 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCMOR COMPARE, DIRECT CONNECT, INACTIVATE ICN, LOAD TO MPI\nRefer to patch MPIF*1*3 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nIDENTITY MANAGEMENT ISSUES FOR HDR II / CDS\nRefer to patch MPIF*1*51 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOVE POTENTIAL MATCHES RETURNED EXCEPTION REFERENCES\nRefer to patch MPIF*1*53 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSUPPORT FOR NATIONAL HEALTH INFORMATION EXCHANGE\nRefer to patch MPIF*1*55 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMESSAGING ENHANCEMENTS FOR NEW FIELDS\n \nRefer to patch MPIF*1*54 in the FORUM Patch Module for a complete\ndescription.\n\n
\nVIC 4.02 MPI INTEGRATION/HWSC\nRefer to patch MPIF*1*56 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPATIENT RECORD FLAG SUPPORT\nRefer to patch MPIF*1*58 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 10\nRefer to patch MPIF*1*57 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 12\nRefer to patch MPIF*1.0*59 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 13\nRefer to patch MPIF*1.0*60 in the FORUM Patch Module for a complete \ndescription.\n\n
\nENTERPRISE REGISTRATION - ITERATION 14\nRefer to patch MPIF*1.0*61 in the FORUM Patch Module for a complete \ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 15\nRefer to patch MPIF*1.0*62 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 / RELEASE 1\nRefer to patch MPIF*1.0*63 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 / RELEASE 2\nRefer to patch MPIF*1.0*64 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS\nRefer to patch MPIF*1.0*65 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - RELABEL SEX PROMPTS\nRefer to patch MPIF*1.0*66 in the FORUM Patch Module for a complete \ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - DATE OF DEATH UPDATES \nRefer to patch MPIF*1.0*67 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - MVI SENSITIVITY\nRefer to patch MPIF*1.0*68 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - REMOTE UPDATES FOR CLOUD\nRefer to patch MPIF*1.0*70 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - SUPPORT LONG NAMES IN VA MPI\nRefer to patch MPIF*1.0*69 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - EHRM SUPPORT\nRefer to patch MPIF*1.0*71 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - PROXY ADD PATIENT\nRefer to patch MPIF*1.0*73 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - PRF SUPPORT\nRefer to patch MPIF*1.0*74 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - HAC SUPPORT\nRefer to patch MPIF*1.0*75 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE- NORTH CHICAGO FULL ICN\nRefer to patch MPIF*1.0*76 in the FORUM Patch Module for a complete\ndescription.\n\n
\nBackup of MPIF*1.0*77 on Jul 14, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - WEB SERVICES SSL CONFIG\nRefer to patch MPIF*1.0*77 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - NEW DEMOGRAPHIC FIELDS\nRefer to patch MPIF*1.0*78 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - REGISTER A PATIENT\nRefer to patch MPIF*1.0*79 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - DISPLAY ONLY QUERY\nRefer to patch MPIF*1.0*80 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nMaster Patient Index project.\n\n
\nThis patch addresses the issue of one-time meds showing up on the Virtual\nDue List from previous movements and even previous admission. As released\nthe VDL will search back 30 days for one-time orders and display them on\nthe VDL if there is no associated administration in the BCMA medication\nlog. With this patch the VDL will now only go back as far as the current\nmovement eliminating one-time orders from showing up from previous\nmovements and admissions.\n\n
\nPatch PSB*1*9 contains the following:\n [PSBO WA] option is a combination of data that consists\n Corrective Action: The user is now able to mark a medication as\n NOT GIVEN at the "Admin Status:" prompt in the Edit Medication\n Log [PSB MED LOG EDIT] option and it appears correctly on the MAH.\n \n12. Problem: Large volume IV's do not print on the Due List [PSBO DL]\n option.\n \n Corrective Action: The Due List [PSBO DL] option has been corrected\n to display large volume IV's.\n \n of the ward location and the Room-Bed. When this combination of\n13. Modification: Added the COMMENT field (#.3) from the BCMA MEDICATION\n LOG file (#53.79) to the Medication Variance Log [PSBO MV] option.\n E3R - 13732 and 14810\n \n14. Modification: The message text the VDL displays when a patient has no\n orders have been modified. When there are no orders in VISTA for a\n selected patient the message, "No Active Orders at this Time" will be\n displayed. If there are orders in VISTA, but they do not fall within\n the start and stop times selected on the VDL the message,\n "No Meds to be Administered for the Time Period Selected!" will be\n data exceeds 32 characters it causes the report to print skewed.\n displayed. If no schedule types are selected on the VDL the message,\n "No Schedule Type(s) Selected!" will be displayed.\n E3R - 14680\n \n15. Modification: The process of Auto-update has been added to the BCMA\n functionality. Auto update is the process of automatically copying\n updated BCMA files from a server network drive to a client.\n \n The prompts "The UNC of the Auto-update Server" and "Autoupdate\n Notification Mail Group" have been added to Edit Divisional Parameters\n \n [PSB PARAMETERS] option.\n \n Please read the ReadMe.txt file found in your BCMA directory for a\n full description on the GUI update functionality.\n Corrective Action: The ward location and Room-Bed will now print\n on separate lines.\n \n3. Problem: The "Missing Dose Printer" prompt did not display on the GUI\n BCMA Site Parameters.\n \n \n Corrective Action: The GUI BCMA Site Parameters has been\n corrected to display the "Missing Dose Request Printer" prompt.\n \n4. Problem: When BCMA generates an error message to pharmacy because it\n cannot determine the schedule. It displays the orderable item number\n instead of the name. Below is an example.\n \n Order Number....: 570U\n Orderable Item..: 1695 <=====\n Patient.........: XXXXXX,SAMUEL (000 00 0000)\n1. Problem: The Virtual Due List (VDL) will only display the first\n Reason..........: Unable to determine schedule 2X/WEEK\n \n Corrective Action: The error message has been corrected to display\n the orderable item name instead of the number.\n \n Order Number....: 570U\n Orderable Item..: DIGOXIN TAB <======\n Patient.........: XXXXXX,SAMUEL (000 00 0000)\n Reason..........: Unable to determine schedule 2X/WEEK\n \n additive and solution for an Intravenous (IV) order.\n5. Problem: The following occurs when trying to print a Due List\n from the Due List [PSBO DL] option with a patient who has\n the same last name and last four digits of the SSN as another patient.\n When the last initial and last four digits of the SSN are entered\n it displays two choices.\n \n 1 M6383 MOUSE,MICKEY 11-13-48 XXXXX6383\n 2 M6383 MOUSE,MINNIE 4-3-36 XXXXX6383\n CHOOSE 1-2: 1\n \n \n The following question is then asked:\n \n There is more than one patient whose last name is 'MOUSE' and\n whose social security number ends with '6383'.\n Are you sure you wish to continue (Y/N)? Y\n \n When this question is answered, the Due List screen shifts down\n one line, skewing the screen.\n \n Corrective Action: The Due List [PSBO DL] option screen has\n Corrective Action: The VDL will now display all additives, strengths,\n been corrected to not skew when there is a multiple patient match.\n \n6. Problem: The user receives the following error message when\n attempting to start a PRN Piggyback. "Error(s) Filing Transaction\n MEDPASS. Business Logic Error: PRN Medications MUST Have a PRN\n Reason". The user is then unable to mark it as started.\n \n Corrective Action: The GUI VDL has been corrected to allow\n a user to mark a PRN Piggyback as started.\n \n solutions, and volumes for each IV order.\n7. Problem: User receives an undefined error when using the Missing Dose\n [PSBO MD] option.\n \n Corrective Action: The error was resolved by performing a KILL on the\n D0 variable.\n \n8. Problem: An IV order with a status of on call will not\n display on the VDL.\n \n Corrective Action: The VDL has been corrected to display IV's with\n \n a status of on call.\n \n9. Problem: When scanning a drug with more than 6 units per dose, only 6\n units display in the "MULTIPLE DOSES TO SCAN" GUI window.\n \n Corrective Action: The "MULTIPLE DOSES TO SCAN" window has been\n corrected to show and scan more than 6 units of a medication.\n \n10. Problem: When a user leaves the "Print to DEVICE:" prompt blank\n within the Due List [PSBO DL] option the user receives a "NULL\n2. Problem: The Room-Bed displaying on the Ward Administration Times\n SUBSCRIPT" error.\n \n Corrective Action: The "Print to DEVICE:" prompt has been changed\n to be a required prompt.\n \n11. Problem: When a user deletes the date and time from an order already\n given within the Edit Medication Log [PSB MED LOG EDIT] option, the\n medication still appears as given on the Medication Administration\n History report (MAH).\n \n\n
\nPatch PSB*1*10 contains the following:\n VDL is opened on Tuesday.\n12. Problem: An undefined variable error is generated in the\n Missing Dose Report [PSBO MD] option when searching for\n an MAS ward.\n \n Corrective Action: The code has been modified to properly\n loop through the MAS ward locations and not generate an\n error.\n \n13. Problem: If a patient has an 2 orders with the same orderable\n item and 2 different dispense drugs, the Ward Administration\n \n Times [PSBO WA] option will only print the first order on\n the report.\n \n Corrective Action: The Ward Administration Times [PSBO WA]\n option has been corrected to display both orders.\n \n14. Problem: If the administration time and the Virtual Due List\n Parameters Start Time: are equal to 2400, the dose would\n not display on the VDL.\n \n Corrective Action: BCMA has been modified to no longer\n Corrective Action: The VDL has been modified to properly display\n the 2400 medication.\n \n15. Problem: An odd schedule order will only print the first two digits\n of the administration time on the Due List [PSBO DL] option.\n \n Corrective Action: Odd schedule administration times will now print\n military time on the Due List [PSBO DL] option.\n \n16. Problem: If an odd schedule order calculates an administration\n generate an error messages to the due list error notification\n time to be 2400. The GUI VDL will display "3030@3010" in the\n "Admin Time" column.\n \n Corrective Action: The calculated admin time for midnight dose\n will now properly display 2400 in the "Admin Time" column.\n \n17. Problem: If an order contained an odd schedule greater than\n 24 hours, the subsequent doses would not display on the VDL.\n For example, if an order has a schedule of Q36H only the first\n dose would display on the VDL.\n mail group when the VDL is opened on a non scheduled\n \n Corrective Action: BCMA has been modified to properly calculate\n the subsequent doses for an odd schedule greater than 24 hours.\n \n18. Modification: The Label Print [PSBO BL] option has been\n modified to validate the drug requested for printing and the\n patient's current orders. If a drug is selected to print\n that the patient does not have a current order on. The\n following message will display\n \n administration day.\n "Patient not currently on medication: XYZ Med (Qty: 1)"\n Do you want to continue?\n E3R Number: 13809\n \n19. Modification: When the user performs a right-click on the VDL,\n the Start IV status on the VDL has been modified to Start.\n \n20. Modification: The GUI BCMA Site Parameters has been updated to include\n the following; Default Bar Code Format, Default Bar Code\n Prefix, Using Robot Rx, Allow Multiple Administration for On-Call,\n \n UNC of the Auto Update Server, Auto Update Notification,\n Default Prompt for INCL TRANSFERS, One Time Parameter.\n \n The Edit Divisional Parameters [PSB PARAMETERS] option will no\n longer be updated or maintained. All future enhancements and\n modifications will be made on the GUI BCMA Site Parameters.\n \n21. Modification: The Missing Dose Request [PSB MISSING DOSE REQUEST]\n option was modified to prompt the user for the dosage schedule.\n In the BCMA MISSING DOSE REQUEST file (#53.68), the SCHEDULE field\n2. Problem: The patient's weight displayed in the patient\n (#.19) has been added as a required field to store the schedule\n information.\n \n22. Modification: The Missing Dose Report [PSBO MD] option was\n modified to display the dosage schedule.\n E3R Number: 13030\n \n23. Modification: The Missing Dose Request [PSB MISSING DOSE REQUEST]\n option was modified to display the patient's social security number\n (last four digits), ward location, and room/bed information in the\n demographic box on the GUI VDL was incorrect.\n e-mail message sent to the missing dose notification mail group.\n E3R Number: 12780\n \n24. Modification: Modified the right click 'Display Order'\n accelerator key to 'O' to match accelerator key on menu option.\n \n Modified the right click 'Drug IEN Code' accelerator\n key to 'D' to match accelerator key on menu option.\n \n Accelerator keys enable the user to access a menu command\n \n from the keyboard by pressing Alt+ the appropriate letter.\n E3R Number: 15291\n \n25. Modification: The (MAH) [PSBO MH] option has been modified\n to display an asterisk with the initial if a student\n administered a medication. In the legend section on the MAH\n report, this asterisk will correspond to the student and the\n instructors initials, names, and date/time the medication\n was given.\n E3R Number: 14609\n \n Corrective Action: The calculation for the patient's weight has\n \n26. Modification: The (MAH) [PSBO MH] option has been modified\n to print an "***" in the date column when an order is discontinued.\n E3R Number: 13413/13852\n been modified.\n \n3. Problem: If a drug contains a future inactive date, the Label\n Print [PSBO DL] option will not print the drug.\n \n Corrective Action: The Label Print [PSBO DL] option has been modified\n to adhere to the future inactive date and print according to the date\n entered.\n \n1. Problem: Orders with a day of the week schedule are generating\n4. Problem: When a medication has been given and then the dispense\n drug has been changed on the order, the VDL will display the\n new dispense drug on the already given medication.\n \n Corrective Action: The VDL has been modified to properly display\n any changes in dispense drugs on an order.\n \n5. Problem: User received an undefined error when altering a medication\n status in Edit Medication Log [PSB MED LOG EDIT] option.\n \n false error messages to the due list error notification mail\n Corrective Action: The Edit Medication Log [PSB MED LOG EDIT] option\n has been modified to not generate an undefined error, by using\n standard coding logic.\n \n6. Problem: The Medication Administration History (MAH) [PSBO MH] option\n generates a null subscript error when the nurse or pharmacist initials\n are not present.\n \n Corrective Action: The MAH [PSBO MH] option has been modified to not\n generate an error when the nurse or pharmacist initials are not\n group. This occurs when the Virtual Due List (VDL) is opened\n entered. The report will print without the initials.\n \n7. Problem: Orders which contain an odd schedule were not printing on the\n Missed Medications [PSBO MM], Ward Administration Times [PSBO WA]\n and the Ward Administration Times [PSBO WA] reports.\n \n Corrective Action: The reports have been modified to print\n odd schedule orders.\n \n8. Problem: The Last Action column on the Virtual Due List is not\n on a day the order is not scheduled to be administered.\n displaying the four digit year.\n \n Corrective Action: The Virtual Due List has been modified to display\n the full four digit year.\n \n9. Problem: In reference to the Medication Variance Log [PSBO VR]\n option, a site noticed that this report indicates only the patient\n current ward location when the report is generated. Although the\n patient may have received several administrations of medications on\n different wards, the report does not denote the patient specific\n \n location when the medication was administrated. The lack of this\n information made it difficult for providers to track down the\n locations that had irregularities in the administration of medications\n to the patients.\n \n Corrective Action: Modifications were made to the Medication Variance\n Log [PSBO VR] option to allow the report to display the patient\n location associated with each event date/time the medication was\n administrated to the patient.\n \n For example, an order with a schedule of MO-WE-FR\n \n10. Problem: Intravenous (IV) orders with a schedule of one-time\n generate a "Data Validation Error: 701: The value '.143022'\n for field ORDER ADMINISTRATION TIME in file BCMA MEDICATION LOG\n is not valid" error when trying to mark them as started.\n \n Corrective Action: BCMA has been modified to allow one-time\n IV orders to be marked as started without generating an error.\n \n11. Problem: The VDL is displaying an incorrect message when a medication\n will generate an error message to the mail group if the\n is marked as held. For example, when a medication is marked as held\n and the user tries to mark the next medication as given, the message\n "*** NOTICE, Aspirin was given 2 minutes ago" is being displayed.\n \n Corrective Action: The message has been updated to properly\n reflect the change in status. The new message displayed in the\n above example is;\n \n "*** NOTICE, Aspirin was HELD 2 minutes ago"\n \n\n
\nA problem was found in PSB*1*10 with how the Bar Code Medication\n to the BCMA MISSING DOSE REQUEST file (#53.68) storing the external\n room-bed value.\n \n Corrective Action: The Missing Dose Report [PSBO MD] option was\n corrected by properly storing the internal room-bed value in\n the BCMA MISSING DOSE REQUEST file (#53.68).\n \n2. Problem: Orders that contain administration times (0900-1500) as\n a schedule do not display on the VDL. When a\n user tries to access the BCMA VDL, a MailMan message will be sent\nAdministration (BCMA) Virtual Due List (VDL) processes orders with\n to the Due List Error Notification Mail Group for the pharmacist\n to correct the order. The message that is generated is stated below:\n "No Admin time required for non-standard schedules."\n \n Corrective Action: The VDL has been corrected to properly display\n orders that contain an administration time (0900-1500) as a schedule.\n \n3. Problem: When printing the Missed Medications [PSBO MM] option report\n by ward, there would be no truncation between data. This resulted in\n data overlapping, making the report unreadable.\ncertain schedules. Below are the listed problems found with PSB*1*10.\n \n Corrective Action: To display all the data in a readable format, the\n Missed Medications [PSBO MM] option report has been modified by\n removing the ward location as a column. The ward location still\n displays as a header.\n \n4. Problem: Orders that contain a standard day of the week schedule\n (i.e. MO-TU@0900) that are in the ADMINISTRATION SCHEDULE file (#51.1)\n do not display properly on the VDL.\n \nPlease note: PSB*1*10 should not be removed. PSB*1*15 has been developed\n Corrective Action: The VDL has been corrected to properly display\n standard day of the week schedules.\n \n5. Problem: IV Piggyback orders that contain a standard schedule (Q8H)\n with no frequency defined in the ADMINISTRATION SCHEDULE file #(51.1)\n do not display on the VDL.\n \n Corrective Action: The VDL has been corrected to properly display these\n these types of orders.\nto address these problems.\n \n \n1. Problem: The Missing Dose Report [PSBO MD] option is generating an\n illegal number error when a user tries to run the report. This was due\n\n
\n1. A site reported a problem where a one-time order could not be\n system parameter is not defined, the system will use the continuous order\n parameters to determine the stop date, rather than the start and stop \n date being equal. Then, when BCMA marks the medication as 'Given',\n Inpatient Medications will expire the order. NOIS# BUT-0501-20609.\n \n2. Manual Medication Entry [PSB MED LOG NEW ENTRY] option was generating a\n false Due List Error Notification message when accessed.\n \n BCMA V. 1.0 has been corrected to no longer generate an e-mail message.\n NOIS# NOP-0801-11096\n discontinued by the provider because it was expired due to the start and\n CTX-0801-72721\n \n This project consists of a master build containing three patches that \n work together to accomplish these goals listed in order of install.\n Installation of this master build should be coordinated among the three\n packages affected since only one installation is necessary. The patches,\n in order of install, are:\n \n PSS*1*44 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*63 INPATIENT MEDICATIONS V. 5.0\n stop date being the same. However, the medication still displayed in Bar\n PSB*1*13 BAR CODE MEDICATION ADMINISTRATION V. 1.0\n Code Medication Administration (BCMA) V. 1.0 because of the 12-hour rule \n for displaying one-time orders on the Virtual Due List. This patch\n corrects this problem by changing the way the one-time orders is\n calculated. There will be a ward parameter, system parameter and the\n standard calculation. The hierarchy will be to check the one-time ward\n parameter first, if not defined, check the system parameter. If the\n\n
\nPatch PSB*1*14 contains the following:\n2. Problem: In reference to the Missing Dose Request Report [PSB MISSING\n DOSE REQUEST] option, the dosage schedule was added to the report\n in PSB*1*10; however, each medication order was counted or\n displayed individually. The sites would like the report to\n display a sum of identical medication orders.\n \n Corrective Action: Modifications were made to display the sum of\n medication orders that was identical and had an identical dosage\n schedule.\n \n \n3. Problem: When a user selects to sort or print The Medication Variance\n Log [PSBO MV] option by ward, the report displays the variance\n information for all Wards. The site would like the report to\n display only the variance information related to the Ward selected\n via ScreenMan.\n \n Corrective Action: Modifications were made to the option to display\n only the variance information related to the selected Ward.\n \n \n1. Problem: The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] option\n4. Problem: If the user enters in an old date (i.e. 1/21/1931), when\n running the Due List [PSBO DL] option, Bar Code Medication\n Administration (BCMA) generates an undefined variable error.\n \n Corrective Action: The Due List [PSBO DL] option does not generate\n an error when an old date is entered.\n \n5. Problem: If an order was placed with a schedule of Q3MONTHS, it would\n display on the Virtual Due List (VDL) everyday.\n \n did not properly refresh after entering an effectiveness past the\n Corrective Action: The VDL was corrected to display an order with\n a schedule of Q3MONTHS, once every 3 months.\n \n6. Problem: The word missing is misspelled in the report header of the\n Missing Dose Followup [PSB MISSING DOSE FOLLOWUP] option. The header\n displays "Currently Unresolved Mising Dose Requests"\n \n Corrective Action: The misspelled word has been corrected.\n \n7. Problem: The Missed Medications [PSBO MM] option report does not\n allowed time.\n display the first dose for an odd schedule.\n \n Corrective Action: The Missed Medications [PSBO MM] option report\n has been modified to properly display the first dose for an odd\n schedule.\n \n Corrective Action: The refresh command was added to the menu option\n to properly display the screen.\n \n\n
\n Y2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n printing the station number in front of the Internal Entry Number (IEN)\n on the ZEBRA barcode labels. As released labels would print only the\n IEN as a barcode for the selected medication. After this patch labels\n will be formatted as SiteNumber-IEN if the parameter PSB DEFAULT BARCODE\n SITE is set to yes.\n \n 2. Use a different server name for the monthly SAGG reporting. Sites will\n notice no change with the SAGG update.\n \n Old Server: KMP1-BCMA-SERVER@ISC-ALBANY.DOMAIN.EXT\n This patch may be installed during the Y2K Moratorium, either\n New Server: KMP90-BCMA-SERVER@ISC-ALBANY.DOMAIN.EXT\n \n 3. Further enhancements were done so the One-Time medications do not \n appear on the Virtual Due List by discontinuing the order without having\n to mark the order as 'Do Not Give'.\n \n *************************************************************************\n NOTICE: This patch is released prior to a Y2K Waiver and can only be\n installed in a TEST environment until a waiver is received. Upon\n granting of the waiver a message will be sent to all sites informing them\n BEFORE 12/15/99 or AFTER 1/15/2000.\n that this patch may be moved to live.\n *************************************************************************\n This patch MAY NOT be installed between 12/15/1999 and 1/15/2000\n (the Y2K Lockdown Period).\n \n This patch contains 3 improvements.\n \n 1. Sites that are scheduled to integrate with a primary site can begin\n\n
\nY2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n \n 2. Problem: User input dates in VA Fileman format not accepted by BCMA.\n \n Corrective Action: BCMA was modified to accept and store user inputted\n dates in a VA Fileman format.\n \n 3. Problem: The administration times report on the GUI Virtual Due List\n will only display a 24 hour period, even if a time range is selected.\n \n Corrective Action: The administration times report on the GUI Virtual\n This patch may be installed during the Y2K Moratorium, either\n Due List was made consistent to the administration times report on the\n CHUI by removing the administration time fields.\n \n 4. If BCMA has been designated to be used for QA and testing purposes\n only, a notification will be displayed when starting BCMA.\n \n 5. Problem: If the Client/Server clock variance was greater than the\n acceptable limit defined in the PSB Parameters, the Virtual Due List\n would display the PC time.\n \n BEFORE 12/15/99 or AFTER 1/15/2000.\n Corrective Action: Server/Client clock variance corrected to display\n server time.\n \n 6. Required functionality added: Means Test Check Alert.\n \n 7. Mandatory Security Check - The Director, Health Information Management \nHeadquarters, and VA General Counsel have requested modifications to patient\nlook-up functionality in VistA. This request results from a grievance filed by\nemployees that cites non-compliance with the Employee Privacy Act System of\nRecords. The citation states that employee Social Security Number(SSN) and\nPatch PSB*1.0*3 contains the following fixes:\nDate of Birth (DOB) data is presented without soliciting the information from\nthe system and without notification to appropriate site personnel that this\ninformation has been accessed.\n 1. Problem: Orphan jobs were left running due to a disconnect in\n communication between the server and client.\n \n Corrective Action: Incorporate RPC Broker patch XWB*1.1*6 to allow\n orphan jobs to die.\n\n
\n \n2. Problem: The Missed Medications [PSBO MM] option does not print\n Corrective Action: The software has been corrected to not generate an\n error.\n \n15. Problem: When running the MAH report, the initials of the nurse who\n administered a PRN, on-call and one-time do not print on the report.\n \n Corrective Action: The MAH report has been corrected to properly print\n the initials of the nurse who administered an PRN, on-call, and\n one-time.\n \n one-time orders.\n16. Problem: When running the MAH report, one-time orders outside the date\n range are being printed.\n \n Corrective Action: One-time orders will display within selected date\n range on the MAH report.\n \n17. Problem: If no action was taken on a one-time order, they would stay\n on the VDL for 30 days.\n \n Corrective Action: One-time orders with no action will now drop off\n \n the VDL after 12 hours.\n Corrective Action: The Missed Medications [PSBO MM] option will\n now print missed one-time orders on the report.\n \n3. Problem: The stop date on the Due List is not recognized when a date is\n entered.\n \n Corrective Action: The Stop Date prompt has been removed from the Due\nPatch PSB*1.0*4 contains the following fixes:\n List.\n \n4. Problem: BCMA did not accept a dosage which contained decimals\n (i.e.,0.01)\n \n Corrective Action: BCMA has been corrected to accept a dosage which\n contains a decimal.\n \n5. Problem: Medications marked as "Do not give" and "Discontinued" are\n printing on the Due List.\n \n \n Corrective Action: Medications marked as "Do not give" and\n "Discontinued" will no longer print on the Due List.\n \n6. Problem: When on-call's are chosen to print on the Due List the\n report would print one-times. When one-times are chosen\n the report would print on-call's.\n \n Corrective Action: The Due List will now properly print one-times\n and on-call's.\n1. Problem: An undefined error was generated when running the Medication\n \n7. Problem: The user is unable to document the administration of a\n one-time order through the Manual Medication Entry\n [PSB MED LOG ENTRY] option.\n The message "Error: OKAY to give" 'press return to continue or\n ^ to exit', would display. No further action can be taken\n at this point.\n \n Corrective Action: One-time orders can now be properly documented\n through the Manual Medication Entry [PSB MED LOG ENTRY] option.\n Administration History (MAH) report.\n \n8. Problem: Within the Edit Divisional Parameters [PSB PARAMETERS] option,\n "Allowed Mins Before Sched Admin" would allow the administration of a\n medication to be administered based on the minutes prior to an\n "Administration Time."\n \n Corrective Action: The functionality of the question has been changed\n to allow the administration of a medication based on the number\n of minutes prior to the "active time" of an order.\n \n \n9. Problem: Within the Edit Log Medication [PSB MED LOG EDIT] option ,\n a nurse was unable to edit his or her own administration record if\n another nurse made an entry to that medication.\n \n Corrective Action: The Edit Log Medication [PSB MED LOG EDIT] option\n has been modified to allow a nurse to edit his or her own\n administration entries.\n \n10. Problem: Within the Edit Divisional Parameters [PSB PARAMETERS] option\n the user was not able to determine which division they had signed on\n Corrective Action: The BCMA Software was corrected to not pass an\n too.\n \n Corrective Action: The Edit Divisional Parameters [PSB PARAMETERS]\n option will now see the following message displayed: "You are\n currently logged onto Division: XXX", with XXX being the division\n you are logged onto.\n \n11. Problem: On the GUI Virtual Due List (VDL) when the nurse administers\n a PRN medication, the previous four PRN administrations are displayed\n with the message "Okay to administer - Brief Administration History"\n undefined variable, thus not generate an error.\n \n Corrective Action: The display message has been changed to now read\n "Brief Administration History".\n \n12. Problem: On-call and PRNs medications would display on the GUI VDL\n even if they were not active.\n \n Corrective Action: The GUI VDL will not display an on-call or PRN\n order until it has become active.\n \n \n13. Problem: Within the Label Print [PSBO BL] and Drug File Inquiry\n [PSB DRUG INQUIRY] options, the Drug selection would allow the display\n and selection of inactive drugs and those marked for other packages.\n \n Corrective Action: The Drug Selection prompt will only display\n active rugs and those marked for packages "I" and "U".\n \n14. Problem: When attempting to run the Medication Administration Log\n [PSBO ML] option, an error is generated due to incomplete data.\n \n\n
\n1. Problem: Sites using the Robot Rx are having difficulty with \n 1.1 The DRUG file #50 cannot contain a synonym that is 16 or 18 \n2. Problem: Sites which are attempting to integrate are concerned that\n the current prompt "Include Site Number" within Edit Divisional \n Parameters[PSB PARAMETERS] option may have duplicates numbers at \n other sites.\n \n Corrective Action: The prompt "Include Site Number" has been changed\n to "Default Barcode Prefix". This will allow each site to enter in\n a one to five alphanumeric prefix instead of just the site's prefix.\n \n3. Problem: The GUI Virtual Due List (VDL) does not wrap the "Dosage",\n digits in length and begins with a "3". If matches to this \n cutting off the dosage display.\n \n Corrective Action. The GUI Virtual Due List has been corrected to\n properly wrap the "Dosage".\n \n4. Problem: If a user defines a reason under Reasons a Med is\n given PRN, beginning with a numeric value, the GUI Virtual Due List\n would display the actual number of the reason, instead of the text.\n Please see NOIS HAM-0100-22249 for an example.\n \n pattern exist, they must be changed to a different format. \n Corrective Action: The GUI Virtual Due List has been corrected to\n properly display the PRN reason defined.\n \n5. Problem: Non-verified medications are printing on the Missed\n Medications Report.\n \n Corrective Action: The Missed Medications Report\n has been modified to exclude non-verified medications.\n \n6. Problem: When administering an injectable drug from the VDL, you are\n Once these are changed, new synonyms matching this format \n first prompted with the "Enter Quantity and Units" screen.\n Once this screen is completed, the "Injection Site Needed" screen\n appears. If you press cancel, the medication entry is logged as given\n and no injection site is filed with an entry.\n \n Corrective Action: The VDL has been modified to make injectable site\n a required field.\n \n7. Problem: An error "Exception Elist error in module VCLX40.BPL AT\n 0001A9FS" is generated in GUI when the following scenario occurs.\n cannot be entered while using Robot Rx. To search for \n The user scans a drug that comes in 5mg doses and patient needs\n 10mg dose. The user scanned the medication once, then used the\n touch screen to make the second check mark on the second dose.\n \n Corrective Action: The dosage screen has been modified to require the\n second dose to be scanned in, instead of manually marked.\n \n8. Problem: Scan a PRN that requires an amount to be entered such as an\n injection or a cream. The "Enter Quantity and Units" window comes up\n and the user enters the amount and hits enter. Next the "Medication\n possible matches in the DRUG file #50, please follow\n Log" screen is displayed and the user then realizes they incorrectly\n entered the amount, so the cancel button is pressed. The "Medication\n Log" screen is displayed and says "Order Administration Cancelled"\n The user hits enter then scans the med again. The "Enter Quantity\n and Units" screen doesn't come up again, but skips straight to the\n "Medication Log" and keeps the quantity and units from the first scan.\n \n Corrective Action: When cancel is chosen, BCMA will now properly\n cancel out.\n \n these steps.\n9. Problem: There are inconsistencies when marking IV's\n as held or refused.\n \n Corrective Action: IV's can be marked as started, held or\n refused.\n \n10. Problem: The Missing Dose Followup [PSB MISSING DOSE FOLLOWUP] option\n would not stop scrolling if more than 14 medications were present.\n This did not give the user the ability to select the appropriate dose.\n \n \n Corrective Action: The Missing Dose Followup [PSB MISSING DOSE\n FOLLOWUP] option will now properly scroll, allowing the user the\n ability to select a dose.\n \n11. Problem: Within the Drug File Inquiry [PSB DRUG INQUIRY]option,\n if an inquiry is done on a drug that has 50 or more characters\n in the MESSAGE: field, the screen locks and the process needs to\n be stopped.\n \n Corrective Action: The Drug File Inquiry [PSB DRUG INQUIRY]option\n \n has been corrected to no longer lock up if text is greater than 50\n characters.\n \n12. Modification: Display the initials and name of the nurse on the\n Medication Administration History (MAH) [PSBO MH] option.\n \n13. Modification: The MAH now displays the status of "HOLD".\n \n14. Problem: The Missing Dose Request [PSB MISSING DOSE REQUEST], option\n would allow the user to select an inactive drug.\n a) Access VA FileMan\n \n Corrective Action: The Missing Dose Request [PSB MISSING DOSE REQUEST]\n option has been modified to prevent the selection of inactive drugs.\n \n15. Problem: When the administration time and the stop time for a\n continuous order are the same, the system would calculate the\n last dose as a dose to be given. Please see example below, were the\n last dose of 1900 was calculated because the stop time was 1900.\n \n (1)Orderable Item: MINERALS/MULTIVITAMINS TAB\n Bar Code Medication Administration (BCMA) reading the barcode.\n \n Instructions:\n (2)Dosage Ordered: 1 TAB (3)Start: 02/10/00 11:43\n (4) Med Route: ORAL (5)Stop: 02/10/00 19:00\n (6) Schedule Type: CONTINUOUS (7) Self Med: NO\n (8) Schedule: Q2H\n (9) Admin Times: 01-03-05-07-09-11-13-15-17-19-21-23\n (10) Provider: BUNNY,BUGS\n (11) Special Instructions: FOR 3 DOSES\n This order will display 4 doses on the VDL.\n \n b) Select OPTION: 3 SEARCH FILE ENTRIES and enter in the\n Corrective Action: BCMA has been corrected to calculate the\n appropriate doses when the stop time and administration\n time are the same.\n \n16. Problem: The scanner ready status was inconsistent.\n \n Corrective Action: The scanner status is in a ready status during\n most functions in BCMA.\n \n17. Problem: The "Allowed Mins to Enter PRN Effect" prompt within the Edit\n =\n Divisional Parameters [PSB PARAMETERS] option was being stored\n incorrectly.\n \n Corrective Action: The "Allowed Mins to Enter PRN Effect" prompt is\n now being stored correctly.\n \n18. Problem: An error occurred when cancelling the GUI BCMA log on.\n \n Corrective Action: The error has been corrected.\n \n information as it appears below.\n19. Modification: The full version number for BCMA GUI is now located in\n the About BCMA.\n \n20. Problem: If a medication has a med route of intradermal, the injection\n site box will not appear on the VDL during administration.\n \n Corrective Action: The injection site box will now appear on the VDL\n when intradermal is the med route for a medication.\n \n21. Problem: The following scenario would not generate the message ** NO\n \n SPECIFIED MEDICATIONS TO PRINT **" on the Due List. If a user\n choose to print the Due List for a specified schedule and there are no\n medications for that particular schedule, but other medications exist\n for other schedule types.\n \n Corrective Action: The report was corrected to properly display\n \n the message ** NO SPECIFIED MEDICATIONS TO PRINT **" when there\n are no medications to print for the specified schedule type.\n \n OUTPUT FROM WHAT FILE: DRUG//\n22. Problem: Users are unable to identify old one-time orders on\n Missed Medications [PSBO MM] option.\n \n Corrective Action: The start date/date for a one-time order has been\n added to the Missed Medication Report.\n ====\n -A- SEARCH FOR DRUG FIELD: 9 SYNONYM (multiple)\n =\n -A- SEARCH FOR DRUG SYNONYM SUB-FIELD: .01 SYNONYM\n *If your site is not using the Robot Rx system, \n ===\n -A- CONDITION: 3 MATCHES\n =\n -A- MATCHES: 1"3"15E\n =======\n -B- SEARCH FOR DRUG SYNONYM SUB-FIELD: .01 SYNONYM\n ===\n -B- CONDITION: 3 MATCHES\n =\n -B- MATCHES: 1"3"17E\n please skip section 1.\n =======\n -C- SEARCH FOR DRUG SYNONYM SUB-FIELD:<RET>\n -C- SEARCH FOR DRUG FIELD:<RET>\n \n IF: A DRUG SYNONYM MATCHES 1"3"15E\n =\n \n DO YOU WANT THIS SEARCH SPECIFICATION TO BE CONSIDERED \n TRUE FOR CONDITION\n -A-\n \n 1) WHEN AT LEAST ONE OF THE 'SYNONYM' MULTIPLES SATISFIES IT\n 2) WHEN ALL OF THE 'SYNONYM' MULTIPLES SATISFY IT\n CHOOSE 1-2: 1// 1\n =\n OR: B Or DRUG SYNONYM MATCHES 1"3"17E\n =\n DO YOU WANT THIS SEARCH SPECIFICATION TO BE CONSIDERED \n TRUE FOR CONDITION\n -B-\n 1) WHEN AT LEAST ONE OF THE 'SYNONYM' MULTIPLES SATISFIES IT\n Corrective Action: The BCMA software has been modified to recognize \n 2) WHEN ALL OF THE 'SYNONYM' MULTIPLES SATISFY IT\n CHOOSE 1-2: 1// 1\n =\n OR:\n \n STORE RESULTS OF SEARCH IN TEMPLATE:\n \n SORT BY: GENERIC NAME// <RET>\n START WITH GENERIC NAME: FIRST//<RET>\n FIRST PRINT FIELD: .01 GENERIC NAME\n the Robot Rx barcode format. In order for BCMA to function with \n ===\n THEN PRINT FIELD: SYNONYM (multiple)\n =======\n THEN PRINT SYNONYM SUB-FIELD: .01 SYNONYM\n ===\n THEN PRINT SYNONYM SUB-FIELD: <RET>\n THEN PRINT FIELD: <RET>\nHeading (S/C): DRUG SEARCH//<RET>\nDEVICE: 0;80;999 ***\nDRUG SEARCH MAR 13,2000 09:57 PAGE\n Robot Rx, please follow the directions in the order listed below.\nGENERIC NAME SYNONYM\n--------------------------------------------------------------------------\n \n \nACETAMINOPHEN 325MG TAB APAP\n TYLENOL\n ACET325\n 000677000100\n 051111048893\n \n 305111104882120100\n \n \n 1 MATCH FOUND.\n \n 1.2 A new prompt "Using Robot Rx" has been added to\n Edit Divisional Parameters [PSB PARAMETERS]option.\n The user should answer Yes to thE question when they\n are now ready to use Robot Rx.\n \n\n
\nPatch 6 contains the following modifications:\n GUI would allow freetext.\n \n Corrective Action: The "reason needed" field will not accept freetext.\n \n3. Problem: The "Last Given" column is updated each time an action\n occurs, including refused and held. This can be confusing to the\n user since a medication marked as held will also show a date and \n time in the last given column.\n \n Corrective Action: The "Last Given" column will be changed to "Last\n \n Action". The last status will also be displayed in the column next to\n the date and time.\n1. Problem: The verifying nurse initials are not displayed on the Virtual\n Due List (VDL).\n \n Corrective Action: The VDL has been modified to display the verifying\n nurse initials.\n \n2. Problem: The "reason needed" field on the missing dose screen on the \n\n
\n1. Installing Bar Code Medication Administration (BCMA) on a network\n The file roboex32.dll is typically installed into the\n c:\\windows\\system directory or (for Windows NT machines)\n the c:\\winnt\\system32 directory.\n \n C. Share the BCMA directory on the file server. Optionally, the\n directory can be set to READ ONLY via the shared directory\n properties. In a Windows NT environment, NTFS file\n security can be set to further secure this directory.\n Additionally, a login script file can be created that will\n automatically map the network drive each time a\n drive.\n user logs in. This helps in the event that a user accidentally\n disconnects from the network drive.\n \n2. Pointing the client PC/laptop to the file server.\n \n A. Map each laptop or client PC to the network drive mentioned in the\n previous step.\n \n B. Create an icon that points to the file bcma.exe (on the network\n drive). Via the icon's properties, set up the necessary command\n \n line parameters to connect to your VistA system.\n \nUsing this method, no BCMA files are required on the local client's PC.\nWhen it is time to install the next BCMA GUI patch, have all users log out\nof BCMA, install the patch on the file server that is sharing the files\nand the upgrade will be complete.\n \nThe above installation instructions will only work with patch PSB*1*3 or\nlater. Previous patches require additional files to be moved to the\nshared BCMA directory.\n A. To install BCMA on a network drive, install BCMA on the file server\n that will perform the file sharing. BCMA is typically installed into\n c:\\program files\\vista\\bcma.\n \n B. Perform a file search on the file server to locate the file\n roboex32.dll. Copy this file to the file server's BCMA directory.\n\n
\nPatch PSB*1*7 contains the following:\n \n display the nurse's initials when a one-time has been marked\n as refused.\n \n9. Problem: Within the Due List [PSBO DL] option, the "On Call:"\n prompt will not save the users settings upon exit.\n The field defaults to "No" after the user has exited the option.\n \n Corrective Action: The "On Call:" prompt has been modified\n to save the users settings upon exiting the option.\n \n2. Problem: A user is unable to distinguish identical one-time\n10. Problem: If a medication order has 2 or more units per dose, BCMA will\n display the Multiple Doses to Scan screen to allow the user\n to scan the second, third, etc doses. If a nurse enters an Internal\n Entry Number (IEN) for the second dose and did not press ENTER,\n but immediately pressed DONE, the IEN entered would not be marked as \n Given.\n \n Corrective Action: Validation is now performed on any text entered\n in the "Scan Medication Bar Code" prompt, regardless if the user\n pressed ENTER or not.\n orders on the Virtual Due List (VDL), when multiple identical\n \n11. Problem: If a user double clicks on an IV order on the VDL, the\n "Dosage Ordered:" prompt would display data.\n \n Corrective Action: The "Dosage Ordered:" prompt has been\n corrected to not display any data on the VDL if an IV is order.\n \n12. Problem: If a patient has an IEN of "1" from\n the PATIENT file (#2) the VDL would generate the error\n "RPC ERROR GETORDERLIST" and not display any orders.\n one-time orders exist.\n \n Corrective Action: The VDL has been corrected to not error\n with a patient who has an IEN of "1".\n \n13. Problem: If a medication is marked as held or refused through the\n Manual Medication Entry [PSB MED LOG NEW ENTRY] option, the\n MAH report displays the entered date/time, not the\n administered date/time.\n \n Corrective Action: The MAH has been corrected to display the\n \n administered date/time instead of the entered date/time.\n \n14. Problem: The Ward Administration Times [PSBO WA] option was\n printing medications for incorrect days. For example, if the\n medication had a schedule of MO-WE-FR and the report was\n printed on Tuesday, the medications for MO-WE-FR would print\n on the report.\n \n Corrective Action: The Ward Administration Times [PSBO WA] option\n has been corrected to properly print the medications for the correct\n Corrective Action: The pop up box, Multiple Orders for Scanned Drugs,\n days.\n \n15. Problem: If BCMA is writing to the BCMA MEDICATION LOG file (#53.79)\n and an MAH is run a "NULLSUBSCRIPT" error is generated.\n \n Corrective Action: The code has been corrected by using\n standard coding conventions.\n \n16. Modification: The "Room/Bed:" prompt has been added to the\n Missing Dose Request [PSB MISSING DOSE REQUEST] option.\n will now display the Type, Active Medication, Special Instructions,\n \n17. Modification: The "MED ROUTE:" prompt has been added to the\n Due List [PSBO DL] option.\n \n18. Modification: The ward location and room-bed have\n been added to the BCMA-Order Problem e-mail message.\n \n19. Modification: The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT]\n option has been modified to display the ADMINISTRATION MEDICATION\n field (#.08) from the BCMA MEDICATION LOG file (#53.79).\n Dosage, Schedule, Route, Admin Time, Last Action, and Start\n \n20. Modification: BCMA GUI has been modified to allow column resizing.\n Any changes to the column settings will be saved, allowing the user\n to re-enter the GUI to the saved settings. The original column\n settings can be reset through the Reset User Parameters\n [PSB USER PARAM RESET] option.\n \n21. Modification: The Patient Medication Log in GUI has been modified to\n display the INCLUDE COMMENTS field (#.28) and the INCLUDE AUDITS\n field (#.29). All comments and audits are now viewable through the\n date/time for each order. To select the correct order for\n GUI.\n \n22. Modification: The Missed Medications [PSBO MM] option and the Ward\n Administration Times [PSBO WA] option have been modified to\n not display self-medications.\n \n23. Modification: The Medication Administration Log [PSBO ML] option\n has been modified to display the START DATE/TIME field (#10).\n \n24. Modification: The ORDER NUMBER field (#.01) has been added to the\n administration, highlight the order and then click the OK button.\n Missed Medications [PSBO MM] option.\n \n25. Modification: The Missed Medications [PSBO MM] option will only\n print one-time medications within the last movement date.\n \n26. Modification: The BCMA GUI screen can now be maximized to fit the\n entire screen.\n \n27. Modification: The Manual Medication Entry [PSB MED LOG NEW ENTRY]\n option has been modified to display the history of the last four\n \n \n administrations for a PRN order.\n \n28. Modification: The patient record locking functionality has been\n removed, allowing multiple sessions of BCMA to be opened for one\n patient.\n \n29. Modification: New key functions.\n \n Shift-Tab - Takes focus off the Scan Medication Bar Code\n to the VDL, allowing the user to scroll up and down the\n3. Problem: Users were unable to print reports to a slave device within\n VDL orders. Press the Enter key to display a highlighted\n order.\n \n Right Click - on a selected order and select Display\n Order to view detailed order information.\n \n ALT-D,O - Displays detailed order information.\n \n Select Due List [PSBO DL] option, then select\n Display Order - To view detailed order information.\n all Bar Code Medication Administration (BCMA) CHUI options.\n \n F4 - To view detailed order information.\n \n F5 - Refresh the VDL.\n \n CTRL,O - To open a new patient.\n \n30. Modification: The GUI VDL has been modified to shut down when\n a "PSB GETORDERLIST" error is encountered. When such an error is\n encountered the VDL would display "No Active Orders". This information\n \n is a result of the broker returning no information. This modification\n prevents the user from viewing a VDL with false information when\n such an error is generated.\n \n31. Modification: The GUI Broker has a timeout value called\n RPCTimeLimit as defined in the quoted text below:\n \n Description\n \n This property is a public integer property that is available at\n Corrective Action: BCMA CHUI has been modified to allow the printing\n run-time only. It specifies the length of time a client will\n wait for a response from an RPC. The default and minimum value of\n this property is 30 seconds.\n If an RPC is expected to take more than 30 seconds to complete,\n adjust the RPCTimeLimit property accordingly. However, it is not\n advisable to have a RPCTimeLimit that is too long. Otherwise,\n the client-end of the application will appear to "hang", if the\n server doesn't respond in a timely fashion.\n \n The BCMA default has been changed from 30 seconds to 60 seconds.\n of reports to a slave printer.\n This can be changed with the new command line parameter of 'T' for\n timeout.\n Your command line might look as follows:\n \n "D:\\Program Files\\vista\\Bcma\\BCMA.exe" S=BGHAM P=9307 T=30\n \n Any value below 30 seconds will be disregarded.\n \n4. Problem: When entering an order through the Inpatient Order\n Entry [PSJ OE] option, for a drug that has a units per dose\n of 1, it is not necessary to manually enter a 1 in the\n1. Problem: An undefined variable PSBSTRT error is generated\n "UNITS PER DOSE:" prompt. If the user chooses to bypass the\n "UNITS PER DOSE:" prompt field entry, the system will default\n to a 1. When the user elects to view the order detail on the\n VDL by double clicking on the order, the" Units" prompt\n is left blank.\n \n Corrective Action: The VDL has been corrected to properly display\n a 1 in the UNITS PER DOSE field (#.02), when a user views the\n detail order information.\n \n within the PRN Effectiveness List [PSBO PE] option when\n5. Problem: The wording for the prompts listed below within menu\n Edit Divisional Parameters [PSB PARAMETERS] option were incorrect.\n \n Corrective Action: The following prompts have been changed in\n the PARAMETER DEFINITION file (#8989.51) in the DISPLAY TEXT\n field (#.02).\n \n From: To:\n Include Blank Addendums at end Default prompt for INCL BLANKS <Y/N>\n Include Continuous Meds Default prompt for INCL CONT <Y/N>\n the user chooses a hospital location instead of a nursing\n Include IV Med Orders Default prompt for INCL IV MEDS <Y/N>\n Include On Call Meds Default prompt for INCL ON-CALL <Y/N>\n Include One-Time Meds Default prompt for INCL ONE-TIME<Y/N>\n Include PRN Meds Default prompt for INCL PRN <Y/N>\n Include Unit Dose Med Orders Default prompt for INCL UD MEDS<Y/N>\n \n6. Problem: Medication orders that have an ODD Schedule do not\n display on the VDL. An ODD Schedule is a schedule that is not\n evenly divisible by 24 hours (Q18H or Q7H).\n \n location at the "Ward Location:" prompt.\n Corrective Action: BCMA has been modified to accept and display ODD\n Schedule types on the VDL.\n \n If your site plans on using ODD Schedules, please read the\n following NOTES.\n \n ***NOTE*** When ordering medications with an ODD Schedule,\n DO NOT enter a time into the "ADMIN TIMES:" prompt when placing an\n order within the Inpatient Order Entry [PSJ OE] option.\n BCMA will automatically calculate the administration time to the\n \n minute, based on the start date/time of the order. If you want the\n administration time to display to the nearest hour, edit the\n "START DATE/TIME:" prompt field to be on the hour.\n \n For example if the start time is at 0837 for a Q5H, the\n administration times will be at 0837, and at 1337. To display the\n order on the VDL on the hour, edit the start time to be at 0800.\n \n ***NOTE*** If a time is entered at the "ADMIN TIMES:" prompt when\n placing an order for an ODD Schedule, that administration time is\n Corrective Action: The PRN Effectiveness List [PSBO PE] option\n when the medication will be displayed on the VDL everyday.\n For example, if an order is placed with a schedule\n of Q5H with an administration time of at 0900. The order will appear\n on the VDL at 0900 everyday. Do not enter administration times\n if you want ODD Schedules to function properly.\n \n ***NOTE*** ODD Schedules are NOT to be entered in the ADMINISTRATION\n SCHEDULE file (#51.1)\n \n7. Problem: No data is being displayed under the columns U/Ord and U/Gvn,\n has been corrected to not error if a hospital location is chosen.\n within the medication log report when an IV is ordered.\n \n Corrective Action: The medication log report has been modified to\n display "N/A" in the two columns for IV orders.\n \n8. Problem: The Medication Administration History (MAH) report\n does not display the nurse's initials when a one-time is marked\n as refused.\n \n Corrective Action: The MAH report has been modified to\n\n
\nPatch PSB*1*11 contains the following:\n \n2. Modification: This patch includes a new API between Inpatient\n Medications and Bar Code Medication Administration\n (BCMA) (Integration Agreement #3174).\n \n The entry point EN^PSBIPM is provided by the Bar Code Medication\n Administration (BCMA) package to provide information to Inpatient\n Medications to be used in determining the start date for a renewed\n order.\n \n \n The new API will:\n \n a. Pass the ORDER ADMINISTRATION TIME field (#.13) of the BCMA\n MEDICATION LOG file (#53.79).\n \n b. Pass the ADMINISTRATION DATE/TIME field (#.06) of the BCMA\n MEDICATION LOG file (#53.79).\n \n c. Pass the ADMINISTRATION STATUS field (#.09) of the BCMA\n MEDICATION LOG file (#53.79).\n1. Problem: When attempting to chart a medication the user receives the\n \n3. The PSBPOST post installation routine re-indexes the BCMA MEDICATION\n LOG file (#53.79). The new subscript added is "AORDX".\n following error.\n \n 310: The IENS> +10+1 conflicts with FDA.\n \n Corrective Action: The error was resolved by performing a NEW command\n on the variable PSBFDA.\n\n
\nBAR CODE MED ADMIN - VERSION 1.0\n\n
\n \n2. Problem: Version 2.0 beta test sites experienced errors in\n routines PSBMD and PSBVDLU1.\n \n Corrective Action: The errors experienced in those routines have\n been corrected.\n \n3. Problem: With the installation of BCMA version 2.0, routine PSBIPM was\n renamed to PSBAPIM.\n \n Corrective Action: PSBIPM is no longer being used in version 2 and \n1. Problem: If a medication is marked from given to not given to\n will be removed with this patch.\n \n4. Problem: With the installation of BCMA version 2.0, the Edit \n Divisional Parameters [PSB PARAMETERS] option is no longer functional.\n \n Corrective Action: The Edit Divisional Parameters [PSB PARAMETERS]\n option will be removed with this patch. Any access to site parameters\n needs to be made through the GUI BCMA Site Parameters application.\n \n5. Problem: The Missed Medications [PSBO MM] option was generating\n given, the Medication Administration History (MAH) [PSBO MH] option\n the Due List Error Notification message, "No admin time required for a\n Non-Standard schedule," on expired orders.\n \n Corrective Action: The Missed Medications [PSBO MM] option will no\n longer generate the message "No admin time required for a Non-Standard\n schedule" on expired orders.\n \n6. Problem: When an order has a schedule in the day of week format, and\n had a frequency associated with it, the order was not displaying on \n the Virtual Due List (VDL) on the days scheduled.\n would display these actions as three separate administration actions\n \n Corrective Action: An order with a schedule in the day of week format\n and a frequency associated with it, will display correctly on the\n VDL on the days scheduled.\n \n7. Problem: The "Order Num" column was printing next to the "Medication"\n column on the Missed Medications [PSBO MM] option. This caused some\n confusion with the order number being interpreted as a dosage for\n some medications.\n \n of given, not given and given.\n Corrective Action: The "Order Num" column was moved to be the\n first column on the Missed Medications [PSBO MM] option.\n \n8. Problem: The Edit Medication Log [PSB MED LOG EDIT] option allowed\n a medication patch to be marked not given from removed.\n \n Corrective Action: The Edit Medication Log [PSB MED LOG EDIT] option\n has been modified to not allow a patch to be marked as not given\n from removed.\n \n \n9. Problem: One-time orders with a future start date/time would print\n on the Missed Medications [PSBO MM] option.\n \n Corrective Action: The Missed Medications [PSBO MM] option has been\n corrected to only print one-time order when the order start date/time\n is within the report start and stop date/time.\n \n10. Problem: IV orders with a future start date and time would display\n on the IV tab of the VDL before due.\n \n Corrective Action: The MAH will now properly display these three\n Corrective Action: The IV tab of the VDL has been modified to not\n display IV order until the order start date and time has been reached.\n \n11. Problem: The GUI generated an error when attempting to display\n unit dose orders on the VDL.\n \n Corrective Action: The VDL has been modified to properly display\n unit dose orders on the VDL.\n actions as one correct action.\n \n\n
\nInstall this patch before installing Patch PSB*2*6. It will perform the\n \nBCMA Order Problem Notification Started on JAN 7,2003@08:24:18.\nThis will let the user know the date and time the process started.\n \nBCMA Order Problem Notification Finished on JAN 7,2003@08:30:47.\nThis will let the user know the date and time the process finished.\n \nThe person installing this patch will also receive a MailMan message\nwith the subject: BCMA Pre patch 6 - Order Problem Notification. This will\nlet the user know that PSB*2*6 will have a problem displaying an order,\nsame medication order validation as Patch PSB*2*6, and allows Pharmacists\nwhich is identified in the message text. A separate MailMan message\nwill be generated for each Order Problem.\nan opportunity to review "problem" medication orders before your site\ninstalls PSB*2*6. Ensure that PSB*2*6 is installed immediately following\nthe correction of any problem medication orders. Failure to do so may\nresult in medication orders not displaying on the Virtual Due List (VDL).\n \nThe person installing this patch will receive two separate MailMan\nmessages with the following subjects:\n\n
\n***NOTE*** Do NOT install this patch until you receive the message\nwhen to display a Continuous medication order on \n LOG NEW ENTRY] option, the medication will not display on the VDL for \n the nurse to mark it as "Removed."\n \n Corrective Action: Medication orders with a dosage form of "PATCH"\n given by a nurse using the Manual Medication Entry [PSB MED LOG NEW\n ENTRY] option will now display on the VDL for the nurse\n to mark them as "Removed." \n \n12. Problem: The Admin Time column on the IVP/IVPB tab of the VDL is \n displaying administration times of "0000" for odd schedule orders.\nthe Virtual Due List (VDL).\n \n Corrective Action: The Admin Time column on the IVP/IVPB tab of\n VDL will now display the correct time for an odd schedule order. \n \n13. Problem: The data entered in the "Enter Quantity and Units" dialogue \n box from the IVP/PB tab was not being stored in the medication log.\n \n Corrective Action: The data is now being properly stored in the\n medication log.\n \n \n14. Problem: If a medication order is marked as "Not Given", the user is \n unable to update the medication using the Manual Medication Entry \n [PSB MED LOG NEW ENTRY] option.\n \n Corrective Action: The user will now be able to update medication\n orders that have been marked as "Not Given" using the Manual \n Medication Entry [PSB MED LOG NEW ENTRY] option. \n \n15. Problem: If a PRN medication order with the dosage form of "PATCH" \n was marked as "Given", it would duplicate on the VDL. The user was \nAt the end of this installation a post install routine will clean up the \n unable to mark the medication as "Removed."\n \n Corrective Action: PRN medication orders with the dosage form of\n "PATCH" will follow the "PATCH" business rule.\n \n16. Problem: The Ward Administration Times report displays IV orders with \n admin times based on the frequency calculated by IPM. The display of \n large volume IV's on this report is confusing to the user.\n \n Corrective Action: IV's with a IV type of Admixture, Hyperal, Syringe \nBCMA Medication Log APATCH INDEX. The person installing the patch will be \n Not Intermittent, Chemotherapy (Admixture), Chemotherapy (Syringe \n Non-Intermittent) will not be displayed on this report.\n \n17. Problem: A Schedule Type of "R" displays in the "Type" column on the \n VDL for medication orders that have a dosage form of "PATCH" and \n a previous Schedule Type of Fill on Request. \n \n Corrective Action: The correct Schedule Type will display in the \n "Type" column on the VDL.\n \nnotified the routine has completed successfully via a MailMan email with \n18. Problem: A condition exists that causes a medication order to have\n the same previous and following order number. Because of this \n scenario, the BCMA application is put into an infinite loop or may \n cause an error when the VDL is opened.\n \n Corrective Action: In support of several NOIS tickets regarding this \n issue, BCMA has implemented a temporary fix that now allows a \n medication order with the same previous and following order number to \n display on the VDL. This is not a comprehensive fix, but will allow \n BCMA to function properly while Inpatient Meds researches the problem.\nthe subject line "BCMA APATCH INDEX CLEAN HAS COMPLETED".\n \n19. Problem: A one-time medication order marked as "Missing," \n would not display on the Missed Medications [PSBO MM] option.\n \n Corrective Action: A one-time medication order marked as "Missing,"\n will now display on the Missed Medications [PSBO MM] option. \n \n20. Problem: Day of the Week schedules that include the "@" sign followed \n by a valid time do not display on the Virtual Due List.\n \n \n Corrective Action: Day of the Week schedules in this format now\n display correctly on the Virtual Due List. \n \n1. Problem: The Medication Administration History [PSBO MH] option \n"BCMA AADT X-REF CHECK COMPLETED" from the installation of PSB*2.0*9 and\n displays medication orders beyond the requested report dates.\n \n Corrective Action: The Medication Administration History [PSBO MH] \n option now displays medication orders within the requested report \n dates.\n \n2. Problem: When a patient is discharged and reinstated, the MAH \n displays "***" in the date column.\n \n Corrective Action: The Medication Administration History [PSBO MH] \nthe message "BCMA Order Problem Notification Finished" from the \n option has been modified to not display "***" in the Date\n column for medication orders that have been discontinued and\n then reinstated. \n \n3. Problem: PRN last actions listed as "Not Given" display on the\n Medication Log Information dialog box.\n \n Corrective Action: The last four actions of a PRN medication order\n will not display an action of "Not Given", in the Medication Log\n Information dialog box.\ninstallation of PSB*2.0*18. Installing this patch before receiving these \n \n4. Problem: A medication order for a Patch displayed multiple \n times on the VDL, if it was marked as "Given", then "Not Given"\n and then "Given" again.\n \n Corrective Action: A medication order for a Patch will display \n appropriately, regardless of how many times an action has been \n applied to the associated patch order.\n \n5. Problem: After a patient receives a patch for the second time \nmessages may cause the Bar Code Medication Administration (BCMA) program \n the "Last Action" column on the VDL displays the incorrect date and \n time.\n \n Corrective Action: The "Last Action" column will now display the \n correct date and time for patches. \n \n6. Problem: When an active IV order that has an infusing bag is edited\n through Computerized Patient Record System (CPRS), via the "CHANGE"\n action, the "old" order disappears from the BCMA VDL IV tab. \n This prevents clinicians from knowing the status of the old order.\nto error.\n \n Corrective Action: Continue to display the status of an edited IV \n order on the BCMA VDL IV tab. \n \n7. Problem: The Missed Medications [PSBO MM] option generates\n a "String too long" error message for medication orders that contain\n a schedule in a minute's format (i.e., Q2').\n \n Corrective Action: The Missed Medications [PSBO MM] option now \n displays medication orders that contain a schedule using a minute's \n \n format. \n \n8. Problem: The Medication Administration History [PSBO MH] option \n generates a "String too long" error message for medication orders \n that contains a schedule in a minute's format (i.e., Q2').\n \n Corrective Action: The Medication Administration History [PSBO MH] \n option now displays medication orders that contain a schedule using a \n minute's format. However, schedules with a frequency of less than 45 \n minutes will display the message "Due Every # Minutes", where # is the\nThis patch contains changes to how BCMA V. 2.0 processes schedule\n frequency.\n \n9. Problem: Ward Administration Times [PSBO WA] option generates\n a "String too long" error message for medication orders that contain\n a schedule in a minute's format (i.e., Q2').\n \n Corrective Action: The Ward Administration Times [PSBO WA] option \n now displays medication orders that contain a schedule using a \n minute's format. However, schedules with a frequency of less than 30 \n minutes will display the message "Due Every # Minutes", where # is \ninformation from Inpatient Medications V. 5.0, and how it determines \n the frequency.\n \n10. Problem: Medication orders that include a Day of the Week schedule \n generate a false Due List Notification Error on a day not due.\n \n Corrective Action: Medication orders that include a Day of the Week \n schedule will no longer generate a false Due List Notification Error.\n \n11. Problem: If a medication order with the dosage form of "PATCH" is \n administered by a nurse using the Manual Medication Entry [PSB MED \n\n
\n1. Problem: The Medication Administration History [PSBO MH] option and \n \n Corrective Action: The code has been modified to properly display \n the patient's medication orders when accessing the VDL.\n Manual Medication Entry [PSB MED LOG NEW ENTRY] option are generating \n an undefined error, because of a missing orderable item name on a \n medication order.\n \n Corrective Action: The undefined error has been corrected. \n \n2. Problem: Users are receiving an undefined variable error in routine \n PSBVDLU1 when accessing the patient's medication orders on the VDL.\n\n
\n *** ATTENTION: This patch includes a new GUI.\n orders are marked as "Refused."\n Request" dialog box is now a required field.\n \n13. Problem: The Right-Click feature used to access the "Take Action\n on WS" command was not available for a ward stock IV bag marked as\n "Held" on the VDL.\n \n Corrective Action: The Right-Click feature used to access the "Take\n Action on WS" command is now available for a ward stock IV bag marked \n as "Held" on the VDL.\n \n \n14. Problem: When users sign on to the BCMA GUI application, and are\n prompted to scan the patient's wristband, a lower portion of the \n screen display is grayed out.\n \n Corrective Action: The GUI screen display has been corrected.\n \n15. Problem: Reports would not print from the GUI application when\n print devices had the same name.\n \n Corrective Action: The GUI printing function has been modified to \n Corrective Action: The GUI VDL will not apply the status of "Refused"\n print reports to devices that have the same name.\n \n16. Problem: A medication order with a schedule of "AC&HS," displays\n on the BCMA VDL with a schedule of "ACHS."\n \n Corrective Action: The GUI has been modified to properly display the\n schedule.\n \n17. Problem: The shortcut keys of "ALT+A" used to display "Allergies"\n would go to the "Start Time:" field of the "Virtual Due List \n to medication orders placed on Provider Hold when marking multiple\n Parameters:" section of the VDL.\n \n Corrective Action: The shortcut key for "Allergies" has been changed\n to ALT-G.\n \n18. Problem: If a medication order is created or edited using the\n Manual Medication Entry [PSB MED LOG NEW ENTRY] option or the Edit\n Medication Log [PSB MED LOG EDIT] option, the last action would \n display incorrectly on the "Last Action" column of the VDL by\n dropping off any trailing zero of the time from the date/time format.\n medication orders.\n \n Corrective Action: The last action for a medication order will now\n display correctly under the "Last Action" column on the VDL.\n \n19. Problem: Users who mark a PRN medication order, with the dosage\n form of "PATCH" as "Given," cannot document a PRN effectiveness using\n the Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] option.\n \n Corrective Action: Users can now document a PRN effectiveness for a\n "Given" PRN medication order with a dosage form of "PATCH."\n \n \n20. Problem: Under the IV Medication Tab, if a medication order gets\n discontinued when a ward stock IV bag has a status of "Stopped," no \n data would display under the "IV Bag Chronology."\n \n Corrective Action: Data will correctly display under the "IV Bag\n Chronology" display area when an IV order becomes discontinued and a \n ward stock IV bag has status of "Stopped" status.\n \n21. Problem: The Special Instructions pop-up box does not function on\n2. Problem: Comments entered when a ward stock IV bag is completed\n the IV Medication Tab when the Pharmacist enters an exclamation ("!") \n to copy and flag the Provider comments for display in a BCMA\n message dialogue box.\n \n Corrective Action: The Special Instructions pop-up box will now \n display on the IV Medication Tab when a Pharmacist finishes\n an IV order and uses the "!" key to copy and flag the Provider \n comments for display on the BCMA VDL.\n \n22. Problem: The "ALLERGIES:" bar on the VDL displays "No allergies on\n and another ward stock IV bag begins infusing, are carried from one IV\n file" when no assessment was completed.\n \n Corrective Action: The "ALLERGIES:" bar will now display "No Allergy\n Assessment" if there are no allergies assessed and "No Known \nAllergies"\n if there is an allergy assessed, but no allergies.\n bag to another.\n \n Installation of this GUI is required in order to see the full\n Corrective Action: Comments entered for an IV bag will not carry over\n to the next IV bag.\n \n3. Problem: The error message "Missing Data" sporadically displays on\n the VDL when a user tries to administer a medication via the "CPRS Med\n Order" button.\n \n Corrective Action: The "Missing Data" message has been corrected.\n \n4. Problem: The error message, "'.' Not a valid integer" sporadically\n functionality of this patch. ***\n displays when a user accesses a patient record on the VDL.\n \n Corrective Action: The VDL has been corrected to not generate the\n error message.\n \n5. Problem: Any report printed from the GUI VDL, displays inactive\n wards in the "Ward" field under the "Print by" section.\n \n Correction Action: Inactive wards will no longer be available for\n selection on reports printed from the GUI VDL.\n \n \n6. Problem: A medication order with the dosage form of "PATCH" marked\n as "Given" using the Manual Medication Entry [PSB MED LOG NEW ENTRY]\n option, does not display on the VDL as "Given."\n \n Corrective Action: Medication orders with a dosage form of "PATCH"\n marked as "Given" using the Manual Medication Entry [PSB MED LOG NEW \n ENTRY] option, will display on the VDL as "Given.\n \n7. Problem: The "Provider:" field on the "Order Manager" dialog\nFor retrieval and installation instructions, please see the Client\n screen does not display all valid Providers when performing a partial\n lookup. This was a result of BCMA not validating the inactive date\n correctly.\n \n Corrective Action: The code has been modified to perform the \n validation on the inactive date. The correct Providers will display\n for selection under the "Provider:" field on the "Order Manager"\n dialog screen.\n \n8. Problem: Drugs with a future inactive date were not available for\nInstallation Instructions section.\n printing on labels using the Label Print [PSBO BL] option.\n \n Corrective Action: Drugs with future inactive dates are now available\n for printing on labels.\n \n9. Problem: BCMA does not perform a version check between the GUI\n application and CHUI application side.\n \n Corrective Action: BCMA will validate the version of the GUI \n application running on the GUI against the CHUI application.\n \n The client version must match the patch number on the VistA server,\n and if compatible, the previous GUI version will be allowed to run. \n GUI version will be allowed to run. No prior version will be allowed \n to run on the client.\n \n10. Problem: The current "Typical" installation process for the BCMA\n GUI application installs both the BCMA client and the BCMA Site \n Parameter application. This is not appropriate for an installation\n a ward P.C. \n \n1. Problem: Any order displayed as Provider Hold on the GUI Virtual\n Corrective Action: The "Typical" installation process has been \n modified to only install the BCMA client.\n \n11. Problem: The action of marking multiple medications, as "Held" or\n "Refused" does not always apply to every medication on the VDL. For\n example, if a medication is already marked as "Given", the action of \n "Held" or "Refused" will not apply to that medication order.\n \n Corrective Action: If multiple medications are highlighted on the \n VDL, and the action of "Held" or "Refused" does not apply to\n Due List (VDL) is also marked as "Refused" when multiple medication\n a highlighted order, an Informational dialog box will display with\n the message, "Held or Refused will NOT be applied to the following\n order(s):" with a list of orders.\n \n12. Problem: The message "ERROR: MISSING DATA - ALL FIELDS ARE\n REQUIRED," Missing Field: NEEDED BY DATE/TIME," displays when a user\n selects the Missing Dose Followup [PSB MISSING DOSE FOLLOWUP] option, \n to complete and save a request.\n \n Corrective Action: The Date@Time Needed field on the "Missing Dose\n\n\n1. BCMA will display a Notification Popup box, once per patient session, \n \n2. BCMA will now document fractional dose medication orders, which occur \nwhen a medication order contains a units per dose that is not a whole\nnumber. When a user administers a fractional dose medication using BCMA, \na Multiple or a Fractional Dose dialog box will display for documenting\nthe actual amount and user comments.\n \n3. Three fields have been removed from the Parameters tab of the BCMA Site\nParameters application since the functionality no longer exists. They\ninclude the "General System Error:" field, the "Auto Update Notification:"\nfor the Unit Dose and IVP/IVPB Medication Tabs. The Popup box displays if\nfield in the Mail Groups section of the Parameters tab and\nthe "UNC of the Auto Update Server:" field in the Misc. Options section of\nthe Parameters tab.\na patient has had a recent movement, and at least one of the last actions\noccurred within the specified timeframe defined in the "Patient Transfer \nNotification Timeframe:" field on the Parameters tab of the BCMA Site\nParameters application. The Popup box will display the patient movement\ntype and transaction type within brackets, and the Virtual Due List (VDL)\nwill display the transaction type in the "Last Action" column for a \nmedication displayed on the VDL.\n\n
\n Problem: In reference to the Medication Variance Log [PSBO MV] option, a \n LOG file (#53.78).\n \n Problem: In reference to the Medication Variance Log [PSBO MV] option, \n several sites are experiencing problems with displaying variance \n information as a result of incompatible ward names stored in the \n BCMA MEDICATION VARIANCE LOG file (#53.78). If the user selects a ward \n name from the WARD LOCATION file (#42) that does not match the ward name \n store in the BCMA MEDICATION VARIANCE LOG file (#53.78), the variance \n log information will not display on the report.\n \n functional discrepancy was discovered in the coding logic used to \n \n Corrective Action: The Ward Name Conversion Process [PSB WARD CONV] \n option was add to the Bar Code Medication Administration Manager \n [PSB MGR] option to allow each site an opportunity to make the \n appropriate corrections to incompatible ward, room and bed names stored \n in their local BCMA MEDICATION VARIANCE LOG file (#53.78). The \n following functions are incorporated in the Ward Name Conversion Process\n [PSB WARD CONV] option:\n \n \n extract previous variance information stored in the BCMA VARIANCE LOG\n o Allow the user to select a specified date range to control the amount \n time needed to complete the process and the amount data that will be \n changed. \n \n o Automatically, convert Ward Name to Ward IEN if the Ward Name in BCMA \n MEDICATION VARIANCE LOG file (#53.78) is identical to the Ward Name in \n the WARD LOCATION file (#42). \n \n o Display a list of un-identifiable ward names to the user. \n \n file (#53.78). The report will only show variance information related \n o Allow the user to change the un-identifiable ward name to a ward name \n stored in the NURS LOCATION file (#211.4) and select the appropriate \n room and bed location.\n \n o Send an e-mail message to the user when the Ward Name Conversion \n Process is completed. \n to patients currently assigned to the selected ward.\n \n Resolution: Modifications were made to rebuild the data structure used \n to sort, store, and display the variance information related to all\n patients associated with the selected ward stored in the BCMA VARIANCE\n\n
\nNOTE: Patch PSB*2*12 makes changes to the ward-specific IV Parameters \nbags on the Virtual Due List (VDL), regardless of the settings for the \npatient's respective ward. \n \nCorrective Action: The IV Parameters settings for the "ALL" ward affect \nthe display of a patient's IV bags VDL only when the settings are not \ndefined for the patient's respective ward. Please be aware that after you \ninstall this patch, all ward-specific IV Parameters defined for wards \nother than "ALL" will work immediately. These parameters control when an \nIV bag is valid, and when BCMA warns a user the status of an IV order \nhas changed. If your site has defined ward-specific IV Parameters, \nfunctionality included in the GUI BCMA Site Parameters application. \nplease review them BEFORE installing this patch, and notify the \nappropriate personnel to ensure that problems are not experienced once \ninstalled.\n \n2. Problem: The PSB DEFAULT BARCODE PREFIX Site Parameter was set to \naccept 1 to 5 characters so the user had to specify a prefix in the GUI \nBar Code Medication Administration (BCMA) Site Parameters application. If \nnone was specified, the barcode number was not recognized when the user \nscanned a patient's medication for administration.\n \nPlease be sure to read the Problem and Corrective Action statements below \n Corrective Action: The PSB DEFAULT BARCODE PREFIX Site Parameter has \nbeen set to accept 0 to 5 characters, so the user does not need to \nspecify a prefix in the GUI BCMA Site Parameters application. When a \nbarcode is printed, no prefix is added to the barcode so the label scans \nsuccessfully during medication administration.\n \n3. Problem: Changes made to the IV Parameters when using the GUI BCMA \nSite Parameters application were not always being saved for the selected \ndivision.\n \nand coordinate the installation of this patch appropriately before \n Corrective Action: Changes made to the IV Parameters when using the \nGUI BCMA Site Parameters application are now being saved for the selected \ndivision.\n \n4. Problem: When the unit of administration is a patch and that patch \nhas a "Given" status, the BCMA Virtual Due List (VDL) displayed the last \naction date/time of the order in the "Last Action" column. The VDL did \nnot display the last action date/time of the orderable item.\n \n Corrective Action: When the unit of administration is a patch and \ninstalling it. (See suggestion at bottom of Corrective Action please.)\nthe patch has a "Given" status, the BCMA VDL displays in the "Last \nAction" column the last action date/time of the orderable item.\n \n 5. Problem: Text in the "U/Gvn" column of the BCMA Medication Log \nReport did not provide word wrapping. This became apparent after \nfree-text 'quantity and units' data was entered during the administration \nof a medication dose.\n \n Corrective Action: After entering free-text 'quantity and units' \ndata during the administration of a medication dose, information in the \n \n"U/Gvn" column of the BCMA Medication Log Report will appropriately word \nwrap.\n \n6. Problem: The following is an example of an error that occurred when \na user attempted to administer a unit dose medication with an "IV Push" \nmed route:\n \n "^Error(s) Filing Transaction MEDPASS\n Data Validation Error: 701: The value 'KCL 20MEQ/D5/NACL {2}' \n for field UNIT OF ADMINISTRATION in SOLUTIONS SUB-FIELD in file BCMA\n1. Problem: The GUI BCMA Site Parameters application, IV Parameters \n MEDICATION LOG is not valid."\n \nThe above error occurred under particular conditions associated with the \nIV solution. \n \n Corrective Action: The user is able to administer unit dose \nmedications with an "IV push" medication route, regardless of the IV \nsolution.\nsettings for specific wards did function as required. The IV Parameter \nsettings for the "ALL" ward always affected the display of a patient's IV \n\n\n1. Problem: The error message "Error(s) Filing Transaction MEDPASS" \n file (#53.68), when the user enters a "@" in the "Patient Name:" \n prompt.\n \n Correction: The Missing Dose Request [PSB MISSING DOSE REQUEST] option\n has been modified to not create an entry in the MISSING DOSE REQUEST\n file (#53.68) file, when a user enters a "@" in the "Patient Name:"\n prompt.\n displays when the infusion rate for an IV Piggyback order includes more\n than 30 characters.\n \n Correction: The INFUSION RATE field (#.35) of the BCMA MEDICATION LOG\n file (#53.79) was increased from 30 to 47 characters.\n \n2. Problem: The Missing Dose Request [PSB MISSING DOSE REQUEST] option\n is creating incomplete entries in the MISSING DOSE REQUEST\n\n
\nProblem: If there is a continuous order, with an admin times, and \ncorrections.\n \nIf a DUE LIST ERROR message is encountered with a Reason of "Invalid \nfrequency received from order" please do the following.\n \n1. Determine if the schedule listed in the mail message is in FILE# 51.1 \n the ADMINISTRATION SCHEDULE FILE. \n a. If it is not, Log a NOIS.\n b. If it is, determine if the TYPE OF SCHEDULE is CONTINUOUS.\n i. If it is not, log a NOIS.\nthe frequency is null, the GUI Bar Code Medication Administration (BCMA)\n ii. If it is, determine if the frequency is a valid number \n greater than zero.\n 1. If it is, log a NOIS.\n 2. If it is not, correct the frequency.\ndoes not display the order on the Virtual Due List (VDL) and a Due List \nError Notification message is not generated.\n \nCorrective Action: BCMA will generate a Due List Error Notification \nmessage for those continuous orders that contain a standard schedule \nwith admin times and no frequency. This can also occur to non-standard \nSchedules. Pharmacy should review the problem order and make necessary \n\n
\nProblem: When a Day of the Week schedule is created with [PSS SCHEDULE \nEDIT] option, the order is showing as due everyday on the Virtual Due\nList. The Ward Administration Times [PSBO WA] option and the Medication\nDue List [PSBO DL] option displays the same problem.\n \nCorrective Action: Day of the Week schedules displays correctly on the \nVirtual Due List, Ward Administration Times [PSBO WA] option, and \nMedication Due List [PSBO DL] option.\n\n
\n1. Problem: The "BCMA ORDER LAST ACTION:", which is displayed in order \n more then two digits. Please see example below.\n \n The value 0.125 for field DOSES GIVEN in dispense drug subfield in file\n BCMA MEDICATION LOG IS NOT VALID\n \n The value 0.125 for field DOSES ORDERED in dispense drug subfield in \n file BCMA MEDICATION LOG IS NOT VALID\n \n Corrective Action: BCMA has been modified to accept up to four\n fractional digits for doses ordered and doses given.\n view screen under Inpatient Medications V 5.0., was displaying the \n last action by orderable item instead of the order number.\n \n Corrective Action: The "BCMA ORDER LAST ACTION:" has been corrected to\n display the last action by order number.\n \n2. Problem: BCMA was generating the message below when a nurse\n tried to administer a medication that had a fractional dose ordered of\n\n
\n1. Problem: The GUI Bar Code Medication Administration (BCMA) Site \n \n2. Problem: The Medication History Report, which is available by \n performing a right-click on an order from the BCMA Virtual Due List\n (VDL), displays incorrect data for an IV medication order. This occurs\n when an IV order contains more than one orderable item.\n \n Corrective Action: The Medication History Report will now display the \n medication history for each orderable item contained in an IV \n medication order.\n \n Parameters application does not perform a version check between the \n3. Problem: A user can administer multiple patches for an On-Call \n medication order, with a dosage form of "PATCH," without the previous\n patch being removed.\n \n Corrective Action: For an On-Call medication order with a dosage form \n of "PATCH," a user must first remove the previous patch administered\n before allowing any proceeding patches to be given.\n \n4. Problem: The administration times for a medication order that uses a \n Day-of-the-Week schedule (i.e., MO-WE-FR@0900) do not print on the \n GUI application and the CHUI application.\n MAH.\n \n Corrective Action: The MAH will now display the administration times \n for a medication order containing a Day-of-the-Week schedule.\n \n5. Problem: The VDL generates displays an error if the user types \n special characters (i.e., "^" or "?") when entering a comment for a\n medication order.\n \n Corrective Action: Any special characters entered with comments \n \n will be removed when BCMA files the comment.\n \n6. Problem: The option "Take Action on WS" was removed in BCMA patch \n PSB*2*20. This option allowed the user to change the status of a ward\n stock IV bag.\n \n Corrective Action: The option "Take Action on WS" has been added to \n patch PSB*2*19.\n \n7. Problem: The new Reduced Space Symbology (RSS) bar codes contain the \n Corrective Action: BCMA will validate the version of the GUI BCMA \n National Drug Code (NDC) number in a new format called "Global Trade \n Item Number (GTIN)." The GTIN has a 14-digit data structure, which is\n used within the EAN.UCC System for the unique identification of trade\n items worldwide.\n \n Corrective Action: BCMA GUI will correctly read the GTIN and search \n the SYNONYM field (#.01) of the DRUG file (#50) for a matching NDC\n number.\n \n8. Problem: The BCMA GUI Due List Report allows the user to select a \n Site Parameters application running on the client against the CHUI\n stop time that is prior to the start time.\n \n Corrective Action: The BCMA GUI Due List will not allow the user to \n select a stop time that is prior to the start time:\n \n9. Problem: The MAH Report only displays the action of "Removed" for a \n PRN, On-Call, and One-Time medication order with a dosage form of\n "PATCH."\n \n Corrective Action: The MAH Report will now display actions of \n application. The client version must match the patch number on the\n "Removed" and "Given." for PRN, On-Call, and One-Time medication\n orders with a dosage form of "PATCH."\n \n10. Problem: If an IV medication order has an infusing bag and becomes \n expired, the infusing bag continues to display on the VDL, along with\n the other available bags.\n \n Corrective Action: Available bags will not display when an IV \n medication order becomes expired.\n VistA server, and if compatible, the previous GUI version will be\n allowed to run. No prior version will be allowed to run on the client.\n\n
\n1. Bar Code Medication Administration (BCMA) will provide a visual\ncheck box is selected in the GUI BCMA Site Parameters application. All\nother schedule types will remain selected on the VDL by default when the\nuser opens a patient's record.\n \n3. The VDL will display a BCMA Clinical Reminders marquee at the lower\nright hand corner. The "count" is the number of PRN medications\nwithout Effectiveness comments within the hours defined in the\n"PRN Documentation" field on the Parameters tab of the GUI BCMA Site\nParameters application or within the current admission whichever is \ngreater.\nindicator on the Virtual Due List (VDL) to identify which schedule types\nA mouse-over list displays the last four undocumented PRN orders.\nWhen the user double clicks anywhere on the PRN Effectiveness row of\nthe BCMA Clinical Reminders marquee, the PRN Effectiveness Log dialog box\ndisplays all PRN orders that need PRN Effectiveness and allowing\ndocumentation of PRN Effectiveness comments for each order listed.\n \nThe "count" will update/refresh when the user:\na) opens a patient file.\nb) administers a PRN medication order.\nc) completes the documentation of a PRN Effectiveness.\nhave active orders within the specified start and stop date/time for the\nd) refreshes the VDL.\n \nA Med History button has been added to display the Medication\nAdministration History for the order selected.\n \n4. When administering a PRN medication, the units given column\nwithin the Last Four Actions table and a drop down box for the users to\nselect the PRN Reason have been added to the Medication Log dialog box.\nUnits given will not display for orders with multiple dispensed drugs.\n \nselected Medication Tab. A green "alert light" to the left of the\n5. An updated PRN Effectiveness Log dialog will ease the process of\nPRN Effectiveness documentation. It displays a list of undocumented PRN\nmedications for a specific order, or across orders, including PRN \nmedications from previous or expired orders. The dialog box\nincludes a "units given" column, which will not display units for orders\nwith multiple dispensed drugs. The division column has been removed.\nSchedule Type indicates that it has active orders for the specified\ntimeframe, and a gray "alert light" to the left of the Schedule Type\nindicates that it has no active orders for the specified timeframe.\n \n2. PRN medications will display on the VDL if the PRN Schedule Types\n\n
\n***NOTE*** This patch should be discussed at each Department of \nmenu contains the Documenting Backlog PRNs [PSB PRN DOCUMENTING] option \nwhich will allow a user to run a report for a date range that will \nsearch through the BCMA MEDICATION LOG file (#53.79) for all \nundocumented PRNs. The Documenting Backlog PRNs [PSB PRN DOCUMENTING]\noption will automatically enter in a comment of "Administrative Closure"\nfor all undocumented PRNs identified by the report.\n \nIn accordance with M1, Part 1, Chapter 5, these blank sections of the PRN \ndocumentation will reflect the term "Administrative Closure" when the \nsoftware is used to close these blank portions related to the PRN \nVeterans Affairs Medical Centers (VAMC) before being invoked. \ndocumentation. The sites medical record review committee should document \nthe decision to run the patch to administrative close the undocumented \nPRN if the site chooses to use this option. In those cases where the sites\nhave reviewed the charts and find that the PRN documentation appears in\nthe patient record in other than the BCMA PRN field, the site should\nindividually enter "documented in progress note."\n \nThe person installing the patch will receive a MailMan message when\nthe process has completed. The subject line will read, "BCMA PRN\nDOCUMENTATION Notification."\n \nProblem: Sites are experiencing a large number of undocumented \nPro Re Nata (PRN) effectiveness in the counter displaying under the\n"BCMA Clinical Reminders" section of the GUI Bar Code Medication\nAdministration (BCMA) Virtual Due List (VDL). \n \nSolution: The Bar Code Medication Administration Manager [PSB MGR] \n\n
\nThe VistA Bar Code Medical Administration Backup System (Patch PSB*2*17)\non a Pharmacy Medical Administration Record (MAR) and Medical \nAdministration History (MAH). Workstation(s) are updated using the \nVA Health Level (HL7) package and are available for use according to \nlocal policies concerning VistA, BCMA or network outages.\nsoftware being released will provide a Class I solution to the BCMA \nContingency IRA #20020403. This plan reflects the intent of VHA Directive\n6210, The Automated Information Systems (AIS) Security, which states that \nall facilities are responsible for the development, maintenance, and\nannual testing of individual AIS contingency. This software maintains a\ncurrent copy, on the designated workstation, of all the inpatient pharmacy\nactivities including the inpatient medical orders(Unit Dose and IV), \nmedication administration and patient allergies, that are included \n\n
\nProblem: NOIS SAJ-0803-71312\nThe BCMA Due List [PSBODL] option, and the VDL will generate a Due List \nError Notification message for IV Piggyback medication orders with a \nSchedule Type of Continuous that have Admin times, and A frequency set to \nnull. The BCMA Due List [PSBODL] option, and the VDL will generate a Due \nList Error Notification message for orders with Schedule Type of \nContinuous that are Unit Dose and IV Piggyback orders that have schedules \nnames in the format of administration times but the Admin times do not \nexist on the order (i.e., schedule = 1200-1600 admin times = NULL).\nAn IV Piggyback order with a Schedule Type of Continuous that has Admin \ntimes, (i.e., Q12H with admin times of 0800-2000), and a frequency set to \nnull, does not display on the Bar Code Medication Administration (BCMA) \nGraphical User Interface (GUI) Virtual Due List (VDL) IVP/IVPB Medication \nTab and the Due List [PSBODL] option. The VDL and the Due List [PSBODL] \noption also do not generate a Due List Error Notification message.\n \nCorrective Action:\n\n
\n 1. Problem: NOIS ISB-1102-30304\n selection process used in other provider system applications such as \n Inpatient Medication V 5.0 and Pharmacy Data Management V 1.0.\n \n 2. Problem: NOIS NCH-1102-40363\n The Medication Variance Log [PSBO MV] option will inappropriately display\n variance information related to medication orders with a status of\n "REMOVED" on the BCMA Variance Log Report.\n \n Corrective Action: The Medication Variance Log [PSBO MV] option will not \n display variance information related to medication orders with a status \n The Drug File Inquiry [PSB DRUG INQUIRY] option does not resemble or\n of "REMOVED" on the BCMA Variance Log Report.\n \n 3. Problem: NOIS MAD-0902-42331\n The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] option will\n improperly allow users an opportunity to enter a comment for PRN \n medication orders that do not have a status of "GIVEN".\n \n Corrective Action: The Enter PRN Effectiveness [PSB MED LOG PRN EFFECT] \n option will only allow users an opportunity to enter a comment for PRN \n medication orders with a status of "GIVEN".\n follow a similar drug selection process used in other provider system\n \n 4. Problem: NOIS CLL-0203-40445\n The Label Print [PSBO BL] option will not retrieve the correct drug name\n if the user enters the drug name as lower case letters.\n \n Corrective Action: The Label Print [PSBO BL] option will retrieve the \n correct drug name if the user enters the drug name as lower case letters.\n \n 5. Problem: NOIS ISB-1102-32339\n The Medication Variance Log [PSBO MV] option will only display variance\n applications such as Inpatient Medication V 5.0 and Pharmacy Data\n information related to patients currently assigned to the selected ward\n on the BCMA Variance Log Report. The option will not display variances\n information associated with previous patients assigned to the selected\n wards.\n \n Corrective Action: The Medication Variance Log [PSBO MV] option will \n rebuild the data structure used to sort, store, and display the variance \n information related to all patients assigned to the selected ward stored \n in the BCMA MEDICATION VARIANCE LOG file (#53.78).\n \n Management V 1.0. A site is requesting modifications that will add\n 6. Problem: NOIS MWV-0102-23190 \n The Medication Variance Log [PSBO MV] option will not display variance\n information on the BCMA Variance Log Report when the user selects to\n print the report by ward names. Several sites are experiencing this\n problem as a result of incompatible ward names between the BCMA\n MEDICATION VARIANCE LOG file (#53.78) and the NURS LOCATION file\n (#211.4). In addition, sites should populate their NURS LOCATION file \n (#211.4) with the proper ward name from the WARD LOCATION file (#42) to \n prevent this problem from reoccurring.\n \n consistency to the drug selection process. \n Corrective Action: The Medication Variance Log [PSBO MV] option will \n compare the ward's internal entry number (IEN) stored in the BCMA \n MEDICATION VARIANCE LOG file (#53.78) to the ward's IEN stored in the \n WARD LOCATION file (#42). The BCMA application will store the ward's IEN\n for future variances. Site must use the new Ward Name Conversion Process\n [PSB WARD CONVERSION] option under the Bar Code Medication Administration\n Manager [PSB MGR] option to convert the ward name associated with \n previous variance information stored in the BCMA MEDICATION VARIANCE LOG \n file (#53.78) in order to print a BCMA Variance Log Report based on \n previous variance information. \n \n \n The Ward Name Conversion Process [PSB WARD CONVERSION] option is \n temporary. However, in the future, Bar Code Medication Administration \n patch PSB*2*23 will remove the temporary Ward Name Conversion Process \n option from your system. The Ward Name Conversion Process option will \n perform the following functions: \n \n a. Allow users to select a specified date range, which will control the \n amount of data and time needed to complete the process.\n b. Convert the ward's name to the ward's internal entry number (IEN) if \n Corrective Action: The Drug File Inquiry [PSB DRUG INQUIRY] option has a \n the Ward Name in BCMA MEDICATION VARIANCE LOG file (#53.78) is\n identical to the Ward Name in the WARD LOCATION file (#42).\n c. Display a list of un-identifiable ward names and allows the user to \n make the appropriate corrections.\n revised continuous search index function that resembles the drug \n\n
\n1. Problem: NOIS AAA-0303-N1449\n \n \n2. Problem: NOIS ISB-0503-30409\n After a medication patch order is "Given," if that order expires or is\n discontinued, and the patient has no other active orders, the patch \n does not display on the VDL; the message "No Active Orders" displays \n instead.\n \n Corrective Action:\n If a patch is "Given" and not "Removed," it should display on the VDL \n The "Last Action" column on the Bar Code Medication Administration\n until it is marked as "Removed." A patch with the status of "Given" \n will display on the VDL until it is marked as "Removed."\n \n \n3. Problem: NOIS ISB-0503-30409\n After a large volume IV order is "Infusing," if that order expires or \n is discontinued and the patient has no other active orders, the \n infusing IV does not always display on the VDL; the message "No \n Active Orders" displays instead.\n \n (BCMA) Virtual Due List (VDL) displays inaccurate information via a \n Corrective Action:\n If an IV is "Infusing" and not "Completed," it should display on the \n VDL up to 7 days after the order is expired/discontinued or until the \n order is marked as "Completed." An IV that is "Infusing" will \n display on the VDL for 7 days after the order is expired/discontinued \n or until it is marked as "Completed."\n \n \n \n \n sequence of administrative actions upon two distinct orders having the\n \n \n4. Problem: NOIS HAM-0103-22522, HUN-0403-21086\n The Edit Medication Log [PSB MED LOG EDIT] option does not allow the \n user to change the status of a medication patch from "Given" to \n "Removed." An attempt to change the status from "Given" to "Removed" \n using the Edit Medication Log [PSB MED LOG EDIT] option displays the \n message "Allowed status codes are Given, Not Given, Held, and \n Refused," preventing the status change of the medication patch.\n \n same orderable item.\n Corrective Action:\n The Edit Medication Log [PSB MED LOG EDIT] option will allow the \n status of a "Given" medication patch to be changed to "Removed."\n \n \n5. Problem: NOIS ISB-0703-30098\n The Manual Medication Entry [PSB MED LOG NEW ENTRY] allows the user to\n enter any administration status for any order type. For example, the \n user can create a new BCMA Medication Log entry for a medication \n patch order, with an administration status of "Completed." \n \n \n Corrective Action:\n The Manual Medication Entry [PSB MED LOG NEW ENTRY] will only allow \n the user to enter "Given," "Held," or "Refused" for orders which are \n not IV orders. A status for an IV order will not be allowed since IV \n medications cannot be entered via this menu option.\n \n \n6. Problem: NOIS ISB-0703-30653\n The "Schedule:" prompt in the Manual Medication Entry [PSB MED LOG NEW\n Corrective Action:\n ENTRY] option screen displays the schedule type instead of the \n schedule.\n \n Corrective Action:\n The "Schedule:" prompt in the Manual Medication Entry [PSB MED LOG NEW\n ENTRY] option screen will display the schedule.\n \n \n7. Problem: NOIS CLL-0303-40554\n The Manual Medication Entry [PSB MED LOG NEW ENTRY] option allows the \n The "Last Action" column on the BCMA VDL will display appropriate and\n user to enter a future date and time for a medication administration, \n which sometimes causes inaccurate information on BCMA reports.\n \n Corrective Action:\n The Manual Medication Entry [PSB MED LOG NEW ENTRY] option will not \n allow the user to enter a future date and time for a medication \n administration.\n accurate status, date and time information per orderable item.\n\n
\n*** ATTENTION: This patch includes a new Graphical User Interface (GUI) \nPatch PSB*2*30 presents some changes to the 'look and feel' of the Bar \n \n Corrective Action:\nBCMA will allow the user to submit a Missing Dose Request for a \nmedication patch order when another patch from that order displays a \nstatus of "GIVEN" on the VDL.\n \n \n9. Problem: NOIS ISB-0703-31421\nWhen the user submits a Missing Dose Request for a PRN medication and \nimmediately (without refreshing the BCMA VDL) marks that PRN as "GIVEN," \nCode Medication Administration (BCMA) GUI. One change is the additive and \nBCMA files into the BCMA Medication Log a null value as the PRN Reason.\n \n Corrective Action:\nBCMA will file into the BCMA Medication Log the PRN Reason as selected by \nthe user for the respective PRN administration.\n \n \n10. Problem: NOIS SDC-0803-60738\nWhen a Global Trade Identification Number (GTIN) bar code was scanned, \nBCMA would strip out the National Drug Code (NDC) number from the GTIN \nsolution display automatically for an infusing bag in the IV chronology \nand perform a search on it. This would result in BCMA not finding a match \nand displaying the error message "Invalid Medication Lookup. DO NOT \nGIVE!!"\n \n Corrective Action: \nThe logic that performs the lookup has been modified to not strip out the \nNDC number. \n \n \n11. Enhancement: E3R#18328\nsection of the Virtual Due List (VDL). Another change is during the \nBCMA GUI will allow a medication patch to be marked as "HELD" or \n"REFUSED" while another patch from the same order displays as "GIVEN" and \nnot marked "REMOVED."\n \n \n12. Enhancement: E3R#13940\nBCMA GUI will provide the user access to the BCMA Medication Variance Log\nReport from the Reports menu of the VDL.\nadministration of a Pro Re Nata (PRN) the PRN reason may be selected by \ntyping the first letter of the PRN Reason. BCMA will focus on the PRN \nReasons that start with the first letter typed in the PRN Reason \nselection area.\n \n \nexecutable file.\n1. Problem: NOIS CPH-0703-40060\nWhen an IV medication order becomes expired while an IV bag is \n"INFUSING" or "STOPPED," the un-administered bags of that order are still \n"available" for administration. \n \nCorrective Action:\nWhen an IV medication order expires, the un-administered IV bags will not \ndisplay on the BCMA VDL.\n \n \n Installation of this GUI is NOT required immediately after the \n2. Problem: NOIS RIC-0703-20366\nThe "Scanner Status:" indicator on the BCMA VDL displays red when the \nuser switches from another application back to the BCMA GUI.\n \nCorrective Action:\nThe BCMA VDL Scanner Status indicator will display green when it is \npossible to scan medication using BCMA. \n \n \n3. Problem: NOIS ISB-0303-31005\nKIDS install for the Patch to function. ***\nMultiple IV bags of an order may be "INFUSING" simultaneously. BCMA does \nnot allow proper maintenance of any of these administered IV bags. For \nexample the user cannot "COMPLETE" any of the "INFUSING" IV bags.\n \nCorrective Action:\nBCMA will allow the maintenance of an order with multiple "INFUSING" IV \nbags.\n \n \n4. Problem: NOIS ISB-0703-31029\n \nIf the BCMA GUI user enters a space alone as documentation of PRN \nEffectiveness, an "information box" displays because the space is \ninappropriately treated as a special character. \n \n Corrective Action:\nWhen documenting PRN Effectiveness using the BCMA GUI via a lone space \ncharacter, the lone space will not be treated as a special character; \ninstead the user will be asked to re-enter the data.\n \n \n \n5. Problem: NOIS ISB-0703-30373\nThe user must scroll the list of output devices to select the most \nrecently used print device.\n \n Corrective Action:\nThe print device most recently selected by the user will display first in \nthe list of selectable print devices.\n \n \n6. Problem: NOIS ISB-0703-30480\nFor retrieval and installation instructions, please see the Client \nUsing the BCMA Site Parameter GUI application, the user can seemingly \ncreate an unlimited number of entries for a "Default Answer List" such as \nthe BCMA "Injection Site" list . These entries should then be selectable \nfrom the respective list box during certain medication administration \nusing the BCMA GUI. Without notice to the user, BCMA limits the number \nof entries/selections to 60.\n \n Corrective Action:\nUsing the BCMA Site Parameter GUI application, the user will be able to \ncreate up to 100 entries for a BCMA "Default Answer List" list box. \nInstallation Instructions section.\nTherefore it will be possible for the user to have up to 100 entries to \nselect from the respective BCMA GUI list box.\n \n \n7. Problem: NOIS ISB-0703-30478\nUsing the BCMA Site Parameter GUI application the user can seemingly \ncreate entries for a BCMA "Default Answer List" box, such as the BCMA \n"Injection Site" list, longer than 30 characters. Without notice to the \nuser, BCMA limits the number of characters for a list entry to 30.\n \n \n Corrective Action:\nUsing the BCMA Site Parameter GUI application the user will not be able \nto create entries for a BCMA "Default Answer List" more than 30 \ncharacters in length.\n \n \n8. Problem: NOIS ISB-0703-30290\nUsing the BCMA GUI, the user cannot submit a Missing Dose Request for a \nmedication patch order when another patch from that order displays a \nstatus of "GIVEN" on the VDL.\n\n
\n1. The user is allowed to view and print the Bar Code Medication \n within the last 7 days.\n \n3. When the user opens a patient record from the BCMA GUI application, the\n Vitals Cumulative Report can be accessed from the Reports menu.\n \n4. When enabled, BCMA will broadcast BCMA Medication Log data to \n applications that subscribe to BCMA Heath Level 7 (HL7) Messaging. \n The events or transactions tht trigger the message broadcasts are\n MEDPASS, UPDATE, STATUS, ADD COMMENT, and PRN EFFECTIVENESS. Upon the \n completion of each "trigger event," BCMA will send HL7 version 2.4 \n Administration (BCMA) ward specific reports via the BCMA GUI (Graphical\n compliant messages to COTS and other subscribing products or \n applications. The BCMA HL7 interface must be activated after \n installation for messaging to occur.\n \n5. When the user launches the BCMA GUI application, the message box\n displays information regarding BCMA 508 compliance. This information\n can also be found in the BCMA Help, About dialog box.\n \n6. When the user scans a currently infusing or stopped bag on the VDL IV\n tab and the associated order has had any changes made to it since the\n user interface) application without having to open a patient record.\n infusing or stopped bag's label was printed, the Scan IV box will \n display Order changes including bag status and changes made on the \n associated order.\n \n7. A new column "Bag Information" has been added to the VDL IV tab. This\n column contains the administration status, date and time of the \n currently infusing or stopped bag on its associated order and one of \n the following messages if the order has changed since the bag label \n was printed. "INFUSING bag on changed order" or"STOPPED bag on changed \n order". This column is updated every time the patient record is opened \n \n or the VDL is refreshed.\n \n8. Problem: NOIS MIN-0703-42067\n The Bar Code Medication Administration (BCMA) Graphical User Interface\n (GUI) does not print the Medication History Report for large volume\n IV's under the GUI IV Medication Tab.\n \n Corrective Action:\n The BCMA GUI Medication History Report for IV Medications will print\n for large volume IV's under the GUI IV Medication Tab.\n2. When administering a PRN medication or documenting a PRN \n \n9. Problem: NOIS TAB-0903-40220\n When users take BCMA offline by unchecking the BCMA on-line check box\n on the GUI BCMA Site Parameters Facility Tab, the users are unable to\n sign in again to the BCMA Site Parameters application and get the\n following error: "The BCMA Application is not active for this\n division", followed by an application error.\n \n Corrective Action: When users take BCMA offline by unchecking the\n BCMA on-line check box on the GUI BCMA Site Parameters Facility Tab,\n Effectiveness, the Medication Log dialog box or the PRN Effectiveness \n the users will be able to sign in again to the BCMA Site Parameters\n application without receiving the above errors.\n \n10. Problem: NOIS ISB-0703-30291\n When a user selects a report from the BCMA GUI Reports menu, the\n "Print by" area of the associated dialog box does not display all\n wards in the Ward list box.\n \n Corrective Action:\n The "Print by" area of the BCMA GUI report dialog boxes displays all \n Log respectively will display a vitals table with the vital signs: \n wards in the Ward list box.\n \n11. Problem: NOIS MAD-0203-42078\n When the user attempts to enter an order via the Computerized Patient \n Record System (CPRS) Med Order Button, the order is being cancelled \n due to an error, "missing data, unable to file"\n \n Corrective Action:\n The user will be able to successfully enter an order via CPRS Med \n Order Button without receiving the above error.\n Temperature (Temp), Pulse, Respiration (Resp), Blood Pressure (BP) and \n Pain. Each of the vital signs will list up to 4 vital entries made \n\n
\n1. Problem: The Missed Medications [PSBO MM] option does not display a \n Provider takes if Off Hold, no verbiage is displayed next to the \n medication.\n \n Corrective Action: The Missed Medications [PSBO MM] option displays \n "(On Hold)" date and time below a medication when the Provider places\n it on Hold. When the Provider takes if off Hold, it displays the\n "(On Hold)" date and time as well as the "(Off Hold)": date and time\n below the medication.\n One-Time order for the new ward after a patient is transferred to\n another ward.\n \n Corrective Action: The Missed Medications [PSBO MM] option displays a \n One-Time order after a patient is transferred to another ward.\n \n2. Problem: The Missed Medications [PSBO MM] option displays "(Hold)"\n next to a medication when a Provider places it on Hold. When the \n\n
\n1. Problem: The Bar Code Medication Administration (BCMA) Order Manager\n a ward stock entry on GUI BCMA.\n \n Corrective Action: GUI BCMA has been modified to regconize the synonym\n number of an IV medication.\n \n3. Problem: When using the CPRS Med Order button, the orderable item \n lookup was using a direct global read.\n \n Correction: The orderable item lookup has been modified to call a \n Computerized Patient Record System (CPRS) Application Program Interface\n dialogue box from the CPRS Med Order button displays the\n (API) instead of using a direct global read.\n "Invalid Medication Lookup, DO NOT GIVE!!"\n \n Corrective Action: The BCMA Order Manager dialogue box has been\n corrected to perform a lookup on the drug synonym number.\n \n2. Problem: The user will receive the "Invalid Medication Lookup,\n DO NOT GIVE!!" error message box when scanning an IV bag to create\n\n
\n1. Problem: NOIS ISB-0503-30379\n option display the PRN Effectiveness reasons using word wrap.\n \n2 Problem: NOIS ISB-0503-31838\n A medication order with a Day-of-the-Week schedule, will use\n the frequency from Inpatient Medication, and incorrectly display the \n data on the Graphical User Interface (GUI) Bar Code Medication \n Administration (BCMA) Virtual Due List (VDL) as being due everyday.\n \n Corrective Action: A medication order with a Day-of-the-Week \n schedule correctly displays on the GUI BCMA VDL on the day scheduled.\n The Medication Administration History [PSBO MH] option \n \n3. Problem: NOIS LIT-0303-72207 \n The Medication Administration History [PSBO MH] option will not \n display medication orders with an odd schedule, which include\n administration times.\n \n Corrective Action: The Medication Administration History [PSBO MH] \n option displays odd schedules with administration times, along with\n the following message, "NOTE - ODD SCHEDULE NO LONGER ALLOWS \n ADMIN TIMES." \n and the Medication Administration Log [PSBO ML] option displays\n \n4. Problem: NOIS ISB-1102-30781 \n The Medication Administration History [PSBO MH] option and the \n Medication History Report are not accessible to the user when\n a medication is not due. \n \n Corrective Action: The Medication Administration History [PSBO MH] \n Option and the Medication History report displays three asterisks \n ("***") in the Date column when a medication is not due.\n \n the Pro Re Nata (PRN) Effectiveness reasons on one continuous \n5. Problem: NOIS AMA-0403-70477 \n The Patient Due List Report and the Ward Administration Time Report \n will not display a "due" medication, on the correct day, for \n schedules with frequencies greater than 24 hours, (i.e.,Q36).\n \n Corrective Action: The Patient Due List Report and the Ward \n Administration Time Report display "due" medication, on the correct\n day, for schedules with a frequency greater then 24 hours.\n \n6. Problem: NOIS MAD-0303-40194 \n sentence rather than wrapping the information to several lines for\n The Medication Administration Log [PSBO ML] option, Medication Log \n Report displays the medication as "GIVEN" with the incorrect dosage \n value, after the medication status was marked as "Not Given" on the\n VDL.\n \n Corrective Action: The Medication Administration Log [PSBO ML] option\n and the Medication Log Report display the medications administration \n units of zero when the medication is set to "NOT GIVEN" on the VDL.\n \n7. Problem: NOIS ISB-0703-30482 \n viewing.\n The Medication Administration History [PSBO MH] option,\n Medication History Report, will display the word "HOLD" in the Date \n column, for all days on the report, even after the medication is \n taken Off Hold.\n \n Corrective Action: The Medication Administration History [PSBO MH] \n option, Medication History Report, displays "HOLD" in the Date column \n on the days that the medication was placed On Hold, through the end \n date of the report. When the medication is taken Off Hold, the word \n "HOLD" Appears on the Report from the On Hold date to the Off Hold \n \n date.\n \n8. Problem: NOIS ISB-0703-30482\n The Medication Administration History [PSBO MH] option incorrectly \n displays orders with a Schedule Type of Continuous, with a Schedule in\n the format of administration times (i.e. Schedule = 1200-1400) but\n where the Admin times have been deleted. Continuous schedules with\n valid admin times that are not Day-of-the-Week Schedules but have a\n NULL frequency are also incorrectly displayed.\n \n Corrective Action: The Medication Administration History [PSBO MH] \n Corrective Action: The Medication Administration History [PSBO MH] \n option will not display orders that meet the above criteria.\n \n9. Enhancement: E3R NO.15232\n The Medication Administration History [PSBO MH] \n option and the Medication History report displays the date as well \n as the time the order was started on the report.\n option and the Medication Administration Log [PSBO ML] \n\n\n*** DUE TO PURGED PENDING-ORDERS, BCMA MAY NOT BE ABLE TO TRACK AND \n Medications with a Schedule Type of Continuous and marked as "Held" may\n not display on the Due List [PSBO DL] option report.\n This issue becomes very apparent when the Bar Code Medication \n Administration (BCMA) system is generating Internal Entry Numbers\n (IEN) for the BCMA Medication Log file (#53.79) which exceed the date \n numerically.\n \n Corrective Action:\n Medications with a Schedule Type of Continuous and marked as "Held"\n will display on the Due List [PSBO DL] option report.\nDISPLAY ORDER HISTORY AND ORDER CHANGES. WITH INSTALLATION OF \n \n \n2. Problem: NOIS ISB-0703-30657\n When creating an administration for a Pro Re Nata (PRN) order in the \n Manual Medication Entry [PSB MED LOG NEW ENTRY] option, the "Brief \n Administration History" displays the status of "Not Given" as one of\n the last four actions.\n \n Corrective Action:\n When creating an administration for a PRN order in the Manual Medication \nPSB*2.0*35, BCMA ERRORS CAUSED BY PURGED PENDING-ORDERS ARE INTERCEPTED, \n Entry [PSB MED LOG NEW ENTRY] option, the "Brief Administration \n History" will not display the status of "Not Given" as one of the last \n four actions. \n \n \n3. Problem: NOIS WPB-0503-31999\n The latest printed label for an IV medication order may not display\n on the BCMA Virtual Due List (VDL) as an "available bag" when it \n should.\n \nBUT WILL NOT ALLOW BCMA TO TRACK AND DISPLAY COMPLETE ORDER HISTORY AND \n Corrective Action:\n All printed labels that are valid and should be available for \n administration will appropriately display as "available" on the VDL.\n \n \n4. Problem: NOIS NCH-1003-41434\n The BCMA Label Print [PSBO BL] option does not allow the use of a drugs\n internal entry number (IEN) alone to select a "Drug Name" for a \n printed label.\n \nORDER CHANGE DATA. ***\n Corrective Action:\n The BCMA Label Print [PSBO BL] option will select the appropriate \n drug when the user enters solely the drugs IEN to select a "Drug \n Name" for a printed label.\n \n \n5. Problem: NOIS UNY-1003-10407\n Allergy data is being displayed in the report header "Reactions:"\n field of reports printed via the VDL, such as the Medication Due \n List report.\n \n \n Corrective Action: \n Adverse Drug Reaction information will display in the report \n header, "Reactions:" field of reports printed via the VDL.\n \n \n6. Problem: NOIS ALX-1103-70256\n An error occurs when the user attempts to access a \n patients VDL and that patient has an active medication order \n with an ACTION STATUS field (#.09) of the BCMA MEDICATION LOG \n \n file (#53.79) equal to null. The error message encountered is \n "$ZE=<SUBSCRIPT>EN+75^PSBVDLUD."\n \n Corrective Action:\n A patients VDL will display without error when that patient has \n an active medication order with an ACTION STATUS field (#.09) of the \n BCMA MEDICATION LOG file (#53.79) equal to null.\n \n1. Problem NOIS HIN-0703-41481:\n\n
\n ****NOTE**** Patch PSB*2*23 will remove the Ward Name Conversion \n time that a patch was "Removed," instead of "Given," under the "Admin \n Time" column.\n \n Corrective Action: The PRN Effectiveness List [PSBO PE] option will \n display the date and time that a patch is "Given" under the "Admin Time"\n column. \n \n 2. Problem: NOIS ISB-0303-30557\n The PRN Effectiveness List [PSBO PE] option displays a PRN medication\n entry twice on the PRN Effectiveness List Report when the user enters a\n Process [PSB WARD CONVERSION] option from your system. Please complete \n Missing Dose Request and administers the medication at a later time.\n \n Corrective Action: The PRN Effectiveness List [PSBO PE] option will not \n display a PRN medication entry twice on the PRN Effectiveness List\n Report when the user enters a Missing Dose Request and administers the\n medication at a later time.\n \n 3. Problem: NOIS ISB-0903-31938 \n The Missing Dose Report [PSBO MD] option will display the header "Dosage\n Schedule" on the Bar Code Medication Administration (BCMA) Character\n the ward name conversion process before installing patch PSB*2*23, \n User Interface (CHUI) Missing Dose Report. This header is not\n consistent with the naming scheme that describes the medication order\n schedule information sent to the Pharmacy via the e-mail notification\n message.\n \n Corrective Action: The Missing Dose Request [PSBO MD] option displays\n the header "Schedule" on the BCMA CHUI Missing Dose Report. This\n information coincides with the BCMA naming scheme that describes the\n medication order schedule information sent to the Pharmacy via the\n e-mail notification message.\n using the Ward Name Conversion Process [PSB WARD CONVERSION] option in \n \n 4. Problem: NOIS ISB-0703-30029\n The Missing Dose Request [PSB MISSING DOSE REQUEST] option creates a\n variance entry in the BCMA MEDICATION VARIANCE LOG File (#53.78) when\n the user enters a Missing Dose Request outside the timeframe specified\n for the "Allowable Time Limits" parameter within the Parameters Tab of\n the GUI BCMA Site Parameters application.\n \n Corrective Action: The Missing Dose Request [PSB MISSING DOSE REQUEST]\n option will not create a variance entry in the BCMA MEDICATION VARIANCE\n patch PSB*2*14. \n LOG File (#53.78) when the user enters a Missing Dose Request outside\n the timeframe specified for the "Allowable Time Limits" parameter within\n the Parameters Tab of the GUI BCMA Site Parameters application.\n \n 5. Enhancement: E3R #13009 \n The Missing Dose Request [PSB MISSING DOSE REQUEST] option will display \n the medication order schedule information in the e-mail notification \n message sent from BCMA to the Pharmacy for a Missing Dose Request. \n \n 6. Enhancement: E3R #17312 \n \n The Missing Dose Request [PSB MISSING DOSE REQUEST] option displays the \n medication order schedule information on the Missing Dose Report sent \n from BCMA to the Pharmacy-selected printing device.\n 1. Problem: NOIS ISB-0203-31993\n Pro Ra Nata (PRN)\n The PRN Effectiveness List [PSBO PE] option displays the date and\n\n
\n*** ATTENTION: This patch includes a new Graphical User Interface (GUI)\nInstallation Instructions section.\n \n1. When administering a Pro Re Nata (PRN) medication or documenting a PRN \n Effectiveness and the PRN Reason is one set via the Bar Code Medication\n Administration (BCMA) Site Parameters settings to initiate a pain score\n reading, BCMA will automatically initiate a pain score reading to be \n filed with other Vital Measurement information.\n \n \n2. Problem: NOIS DUB-0803-31307\n executable file. Installation of this new GUI is REQUIRED in order \n When all of a patient's active medication orders of an order type have no\n scheduled administrations within the date range of the BCMA Virtual Due\n List (VDL), the message "No Active Orders at this Time" displays. \n This message is not accurate.\n \n Corrective Action:\n When all a patient's active medication orders of an order type have no\n scheduled administrations within the date range of the BCMA Virtual Due\n List (VDL), the message "No Administration(s) due at this time" will\n display.\n for the patch to function. The new GUI MUST be installed IMMEDIATELY \n \n \n3. Problem: NOIS NYH-0903-10598\n BCMA is not showing the correct number of PRN Reminders for patients. \n BCMA calculates the number of PRN Reminders based on the date/time of \n patient's transfer and not the date/time of the patient's admission.\n \n Corrective Action:\n BCMA will identify and display PRN Reminders based on the date/time of \n the patient's admission.\n after the KIDS install in order for the software to function. ***\n \n4. Problem: NOIS ISB-1103-31688\n The error "$ZE= NTE+16^PSBSVHL7:1, %DSM-E-UNDEF, undefined variable " \n may occur when comment internal entity numbers (IEN), of the BCMA Medication \n Log are not in sync with the BCMA Medication Log comment sub-file index. BCM\n Health Level 7 (HL7) messaging may attempt to transmit a comment which\n does not exist, causing the error.\n \n Corrective Action:\n BCMA HL7 messaging will transmit the appropriate comment independent \n \n of the BCMA Medication Log comment sub-file index.\n \n5. Problem: NOIS ISB-1103-31567 \n The BCMA Cumulative Vitals report does not display the vital changes if \n only one measurement was changed for the designated date range.\n \n Corrective Action: The Cumulative Vitals report will show all changes \n that occur within the designated date range.\n \n \n \nFor retrieval and installation instructions, please see the Client\n\n
\n1. Problem: When a user attempts to log on to the GUI BCMA, they receive \n2. Problem: Sites are unable to access the GUI, due to the VISTA side\n needing the most current version of BCMA.\n \n Corrective Action: The code which checks the version number has been\n corrected to properly return the correct version.\n the following messages:\n \n RPC BOWDPS5 GETUDID in Option PSB GUI CONTEXT - USER **NOT FOUND**\n RPC BOWDPS5 GETIVID in Option PSB GUI CONTEXT - USER **NOT FOUND**\n \n Corrective Action: The RPC's ORBCMA5 GETUDID and ORBCMA5 GETIVID were\n added to BCMA Client Context [PSB GUI CONTEXT - USER] option.\n \n\n
\n1. Problem: When a medication was given and then not given the Gui did \n to the log file, which caused BCMA to shut down.\n \n Corrective Action: Additional error trapping was added to report the \n error to the user without shutting down.\n \n3. Problem: When attempting to mark multiple patches as removed, the user\n receives the following error message:\n \n "Error(s) Filing Transaction MEDPASS"\n Business Logic Error: PRN Medications MUST Have a PRN Reason\n not validate.\n Business Logic Error: PRN Orders cannot be marked NOT Given\n \n Corrective Action: BCMA GUI has been modified to not allow the\n multiple marking of patches as removed.\n \n4. Problem: User was receiving an undefined variable error in routine \n PSBVDLU1 when attempting to log on to the BCMA GUI application.\n \n Corrective Action: The code was modified to not error when logging on\n to the GUI application.\n \n \n5. Problem: When using the CPRS Med Order button, the IV Fluid Order\n screen is not displaying the same volume as the BCMA Order Manager\n screen.\n \n Corrective Action: The IV Fluid Order screen is now displaying the\n same volume as the BCMA Order Manager screen.\n \n6. Problem: The user would recieve an error when trying to launch\n multiple copies of the BCMA GUI.\n Corrective Action:The GUI will validate when a user marks a med from \n \n Corrective Action: The GUI has been corrected to display the\n Open Error message, "There is already one copy of Bar Code\n Medication Administration running on this machine!"\n \n7. Problem: When launching the BCMA Site Parameters application, the focus\n was not on the electronic signature box.\n \n Corrective Action: The BCMA Site Parameters application has been\n modified to place focus on the electronic signature box.\n Given to Not Given that the user either has the "PSB MANAGER" key or \n \n8. Problem: One-time orders were printing on the Due List [PSBO DL]\n option after the stop date of the order.\n \n Corrective Action: The printed Due List [PSBO DL] option was modified\n to not print one-time orders past the stop date of the order.\n that the user id matches the user id that made the entry in the med \n log.\n \n2. Problem: An error would occur if the user did not have write access \n\n
\n1. Problem: Patient's who did not have a PRN medication administered were\n incorrectly displaying on the PRN Effectiveness List [PSBO PE] option.\n \n Corrective Action: There is a post install routine, which runs to clean\n up erroneous file entries that were causing the patient's to display\n on the PRN Effectiveness List [PSBO PE] option. The routine has also\n been corrected to not create the erroneous file entries.\n\n
\n1. Problem: An allocation error was being generated when starting the Bar\n \n Corrective Action: The GUI has been corrected to allow printing when\n selecting a mnemonic.\n \n3. Problem: The data entered in the Enter Quantity and Units dialogue box\n from the IVP/PB tab was not being stored in the medication log.\n \n Corrective Action: The data is now being properly stored in the\n medicatin log.\n \n Code Medication Administration (BCMA) GUI application. The error\n4. Problem: The Not Given action was not available on the Virtual Due \n List (VDL) unless the user performed a refresh.\n \n Corrective Action: The Not Given action is now available with out\n the user having to perform a refresh on the VDL.\n \n5. Problem: The Multiple Doses to Scan dialogue box does not display to\n the user when a multiple unit per dose order is administered from the\n GUI IVP/IVPB Virtual Due List (VDL) tab.\n \n was a result of a large number of printers in the DEVICE file (#3.5).\n Corrective Action: The GUI IVP/IVPB VDL tab has been corrected to\n properly display when a unit dose order has multiple units per dose.\n \n Corrective Action: The software has been modified to allow for a large\n number of entries in the DEVICE file (#3.5).\n \n2. Problem: Users could not print from the GUI application when selecting\n a mnemonic name from the DEVICE file (#3.5)\n\n
\n1. Problem: If a gap of time exists between the original continuous IV\n order stop date/time and the renewed order start date/time, \n the Bar Code Medication Administration (BCMA) Virtual Due List (VDL) \n IV tab would not display the original order until the expected stop \n date and time.\n \n Correction: The BCMA VDL IV tab will now display the original order \n until the stop date/time of the order is reached.\n\n
\n Patch Description:\n Corrective Action: The BCMA Print Label [PSBO BL] option was modified to \n perform the drug validate process before the device selection process. \n Therefore, the drug validation process will be performed if the system \n device was set to BROWSER or queued to a device.\n \n Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem\n was discovered in the coding logic that created an entry in the BCMA \n Report Request file (#53.69). If the user canceled the label print \n process as a result of a mismatch between the selected drug and patient, \n an impartial or bogus entry would remain in the BCMA Report Request file \n ================= \n (#53.69) occupying vital system resources. \n \n Corrective Action: The BCMA Print Label [PSBO BL] option was modified by \n inserting the necessary coding logic to delete the impartial or bogus \n entry in the BCMA Report Request file (#53.69) when the print label \n procedure is cancelled as a result of a mismatch between the selected \n drug and patient.\n \n Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem\n was discovered in the ScreenMan data input functions. If the selected \n \n patient requires a Means Test, the option will abruptly display a message\n to the user indicating "*** Patient Requires a Means Test ***" and the \n ScreenMan data input process was rearranged out of order.\n \n Corrective Action: The BCMA Print Label [PSBO BL] option was modified by \n inserting the necessary coding logic to refresh the ScreenMan data input \n screen when the Means Test notification message rearranged the data input\n process. By refreshing the screen, the data input flow will return to \n the next data input field.\n \n Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem\n Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem\n was discovered in the coding logic used to set a variable that contained \n the internal entry number of the selected drug. This problem was not \n discovered in the initial release of BCMA V 2.0.\n \n Corrective Action: The BCMA Print Label [PSBO BL] option was modified by\n inserting the correct coding logic to extract and store the selected drug\n internal entry number in the proper variable.\n \n Problem: In reference to the BCMA Print Label [PSBO BL] option, a problem\n was discovered in the drug validation process used to compare the \n was discovered in the drug validation process used to check the patient \n medication orders. The option only validated medication orders that were \n classified a Unit Dose and it did not validate medication orders that \n were classified as IV orders containing IV Additives and IV Solutions.\n \n Corrective Action: The BCMA Print Label [PSBO BL] option was modified \n by inserting the proper coding logic to validate IV orders that contained\n IV Additives and IV Solutions.\n selected drug with medication orders listed for the patient. The drug \n validate process was performed only if the system device was set to \n BROWSER or the user device.\n \n\n
\nBAR CODE MED ADMIN - VERSION 2.0\n\n
\n\n Install both patches on to the Vista Server and the PSB*3*7 \n on to the Contingency Workstations as close together as \n possible during non-peak times. Since the location of the \n Pharmacy Orders "Admin Times" data has been changed \n in the HL7 message you could see orders on the workstation \n missing this data on orders updated due to transitions of data\n during the installation of these patches. The missing data will \n correct itself when that order is updated. \n Once installed it is suggested that the sites review the \n Contingency System reports. Any missing "Admin Times"\n \n can be corrected by running the Single Patient Init\n [PSB BCBU INIT SINGLE PT] option or the Workstation \n can be re-initialized.\n \n *****************************************************\n \n 1. A fix for the '&' delimiter problem with the admin times. The \n admin times was moved to another Field of the HL7 message \n in the pharmacy patch PSJ*5.0*123.\n This patch compensates for the pharmacy change.\n*******************Important Note********************\n \n 2. When a user was added, edited or terminated, BCMA Contingency \n Software would be called and the user would be evaluated, \n and if appropriate be transmitted to the BCMA Contingency \n Workstations. This evaluation was not occurring correctly. \n As a result, all users added, changed or terminated were being \n transmitted to the workstations. An additional screen was added\n to ensure that only the appropriate users accounts were \n transmitted to the workstation.\n \n \n 3. When a user had multiple divisions defined under their user \n account and the workstations were setup using the \n multidivisional capability the users divisions were not \n interpreted correctly. A bug was found in the code that \n looped through the user's division multiple and was corrected.\n \n \n 4. The user Update portion of the BCMA Contingency was not checking \n the status of the "PSB BKUP ONLINE" parameter. Additional code\n was added to check for the status of the "PSB BKUP ONLINE" \nSites running the Bar Code Medication Administration (BCMA) \n parameter. If the parameter is set to "NO" then no updates \n will be transmitted to the workstation from the user portion\n of the package.\n \n Contingency Software must install this patch on all \n Contingency workstations in addition to being installed\n on to the Vista Server. This patch is being released in \n conjunction with the Inpatient Pharmacy patch PSJ*5*123. \n\n
\n \n BCMA will ignore all BCMA Medication Log (file #53.79)records with \n Action Status field (field #.09) equal to ""; and when appropriate, \n BCMA will send an electronic message (e-message) to members of the\n mail group that is specified via the BCMA Site Parameter - "Mail \n Groups/Due List Error", when such a record is processed. The \n subject line of this e-message will read "BCMA - Admin XXXX \n Problem". The subject line of this e-message will contain the \n internal entry number (IEN), identifying the errant BCMA Medication \n Log (file #53.79) record. That IEN is represented above by the\n text "XXXX". PSB*3.0*11 will allow access to the errant records via \n1. Problem: Remedy #HD0000000092269\n Manual Medication Entry [PSB MED LOG NEW ENTRY] option for deletion \n or correction. The errant records may be accessed using \n Manual Medication Entry [PSB MED LOG NEW ENTRY] option\n by users possessing the PSB Manager Key or the user who initiated \n that administration. Details about the errant administration are \n within the e-message sent. The e-message will contain data \n necessary to reprocess, via the Manual Medication Entry [PSB MED LOG \n NEW ENTRY] option, that incomplete and errant administration.\n The following is an example e-message:\n**************************************************************************\n Bar Code Medication Administration (BCMA) software errors at line \n \n Subj: BCMA - Admin 11111 Problem [#22222222] 07/13/05@13:37 12 lines\n From: JACKSON,TODD ELLIS In 'IN' basket. Page 1\n -----------------------------------------------------------------------\n The following administration was NOT displayed\n on the Virtual Due List\n \n Order Number....: 21V\n Orderable Item..: HEPARIN SOLN\n Patient.........: BCMAPATIENT,ONE (000-00-9678)\n "EN+78^PSBVDLPB" when a BCMA Medication Log (file #53.79) record \n Ward/Bed........: 7A GEN MED 724-A\n Reason..........: JUL 13, 2005@07:00 admin's ACTION STATUS is "UNKNOWN".\n Schedule........: Q3H\n Action Dt/Tm....: JUL 13, 2005@11:32:50\n BCMA Med Log IEN: 11111\n User............: ( # 00000000000 ) BCMAUSER,ONE\n \n**************************************************************************\n Per the above example, to correct the example, errant entry #11111, \n the specified "User" or a person holding the PSB Manager Key may use \n being processed has its Action Status (field #.09) equal to "" . \n the Manual Medication Entry [PSB MED LOG NEW ENTRY] option and \n correct the "Reason" for the "BCMA - Admin Problem"; that person can \n correct that "JUL 13, 2005@07:00 admin's ACTION STATUS" per the \n specified patient and order, via corresponding responses to Manual \n Medication Entry [PSB MED LOG NEW ENTRY] option prompts. The \n "correction" is to properly complete or delete that incomplete \n administration.\n \n An e-message triggered by an incomplete administration of a Pro\n Re Nata (PRN) [As Needed] medication must be maintained via VISTA \n The errant record is the result of an administration not properly \n File Manager (FileMan). The IEN of the entry that needs corrected \n is labeled "BCMA Med Log IEN:" within the e-message as well as \n displayed in the e-message's subject line, immediately after the \n text "BCMA - Admin".\n \n It is possible to correct any errant BCMA Medication Log (file \n #53.79) entry using FileMan and the IEN supplied by this e-message.\n \n \n2. Problem: Remedy #HD0000000093022\n saved/discarded via Manual Medication Entry[PSB MED LOG NEW ENTRY] \n The Manual Medication Entry [PSB MED LOG NEW ENTRY] option does not \n maintain the "Given" status per medication patch administrations on \n the BCMA Virtual Due List (VDL). The user is unable to determine \n which administered patch must be removed when the VDL does not \n display the patch as "Given". \n \n Corrective Action:\n A patch administered via the Manual Medication Entry [PSB MED LOG \n NEW ENTRY] option will show as "Given" on the BCMA VDL.\n \n \n \n3. Problem: Remedy #HD0000000103739\n The Manual Medication Entry [PSB MED LOG NEW ENTRY] option \n malfunctions when attempting to administer an "odd schedule" order \n on days the order is not scheduled to be administered.\n \n Corrective Action:\n Display appropriate data when "odd schedule" order administrations \n are attempted.\n Corrective Action:\n\n
\nINC8883572 - PRN orders during undo-given in BCMA sending invalid Mailman \nmessages.\n\n
\nThis patch, in conjunction with PSJ*5*406, will resolve the following issue:\n \nProblem: \n--------\nThe VA North Texas Health Care System reported that when displaying and\nprinting patient order the print out includes removal times for medications\nthat does not require removal. The source of the problem was identified in\nthe schedule used for these orders. If it contains the ampersand character\n(&), e.g. AC&HS, it shifts fields within the HL7 message communicated between\nthe main VistA system and the BCBU workstation, which causes it to populate\nthe REMOVE TIMING field (#7.4) within the ORDER NUMBER sub-file (#53.701) in\n \nthe BCMA BACKUP DATA file (#53.7).\n \nSolution:\n--------\nChanged the routine PSJHL3 via the PSJ*5*406 patch to escape the schedule \nfield value before including it in the HL7 message bound to the BCBU \nworkstation and changed the processing of the incoming message to un-scape \nschedule field value before parsing when at the BCBU workstation. \n \nTechnical Resolution:\n1) INC11397447 - BCMA Backup workstation patient print out and order display\n---------------------\nThis patch changes the routine ALPBHL1U at line tag RXE+29 to un-escape the\nschedule field value before parsing when processing the incoming HL7 message\nat the BCBU workstation. \n removal times for INHALATION Medications\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC11397447 - BCMA Backup workstation patient print out and order display\n removal times for INHALATION Medications\n\n
\nBackup of PSB*3.0*130 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will resolve the following issues:\n \nProblem: \n-------\nThe Audie L. Murphy Memorial Veterans' Hospital reported that when they\nsubmitted a missing dose for an inpatient order with 3 or more dispense drugs\nassociated with it and later scanned the medication received BCMA Med Logs only\nhad a record of the first and last dispense drug associated with the order.\nSome orders require a combination of dispense drugs to achieve the exact dose\nordered. For example: an order of 75MG for Prednisone would require a\ncombination of 3 20MG tablets, plus 1 10MG table plus 1 5MG tablet. Upon\n \nresearch it was determined that this issue was introduced by patch PSB*3*99,\nissue #3 (I9892810FY16). In addressing that issue the patch accidentally\nintroduced the issue reported above. This issue is also being considered a\nPatient Safety Issue (PSI) and the number assigned by the Patient Safety team\nis HITPS-7596.\n \nResolution:\n----------\nThe software was modified to prevent the deletion of some of the dispense\ndrugs in the BCMA Medication Log when 3 or more dispense drugs are marked\n1) INC14580997 - BCMA Missing Dose Routing BUG\nmissing doses on an order and later are scanned. \n \nTechnical Resolution:\n--------------------\nModified the line UPDATED+97 on the routine PSBML2 to not mark a dispense drug\nto be deleted from the BCMA Medication Log if it was previously populated with\nan valid dispense drug in the order.\n \n \nPatient Safety Issues (PSIs):\n HITPS-7596\n-----------------------------\nHITPS-7596\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC14580997 - BCMA Missing Dose Routing BUG\n HITPS-7596\n\n
\nBackup of PSB*3.0*123 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of PSB*3.0*106 on Jul 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSB*3*106.\n\n
\nBackup of PSB*3.0*108 on Jul 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSB*3*108.\n\n
\nError when filing multiple doses with comments\n\n
\nBackup of PSB*3.0*82 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe following enhancements were made in this patch:\n \n1. The Status and Schedule Type will have their own columns with their\n values spelled out, e.g., G will be 'Given' and P will be 'PRN'.\n2. Units Ordered is being added as a new column.\n3. Previous statuses will be displayed in reverse chronological order.\n\n
\nThis patch will resolve the following issue:\nBackup (BCBU) is pulling information from vista incorrectly into the \nBCMA BACKUP DATA file (#53.7) for the field name "SUPPLEMENTAL COMMENTS".\nThis field contains all special instructions, provider comments, or other \nprint information pertinent to this order. The NTE notes segment in the \nHL7 message (i.e. "NTE^6^L" and "NTE^21^L") is not removing the data\ncorrectly when it gets an update into the BCMA BACKUP DATA file (#53.7). \nThis is the reason why it is displaying incorrectly in BCBU workstation. \n \n1) INC15616683 - BCMA (Bar Code Medication Administration) Backup (BCBU)\n workstation patient prints out and order display is\n incorrect for the field name "SUPPLEMENTAL COMMENTS"\n in BCMA BACKUP DATA file (#53.7)\nProblem: \n--------\nThe Honolulu VA Pacific Islands Health Care System reported the Barcode \n\n
\nThe description of this build can be found in the National Patch Module \nunder PSB*3*131.\n\n
\nINC1980869 - BCMA Status code is not avaiable in BCMA for the MAH report\n\n
\nThis patch addresses the following issues:\nProblem:\n--------\nThe "B" index for fields ADDITIVES or SOLUTIONS is not created when the \nIEN of either is 1. The ADDITIVES field points to the IV ADDITIVES file \n#52.6 and the SOLUTIONS field points to the IV SOLUTIONS file #52.7. In \nroutine PSBMD these fields are set to a value of 1 as a placeholder \nbefore the filer routine (FILE^DIE) is called. When the IEN of the field \nis also 1 (pointer in file #52.6 or file #52.7) the index does not get \ncreated because the filer routine doesn't detect a change and doesn't set \nthe index. This issue was found while analyzing another ticket. \n \n \n \nResolution:\n-----------\nRoutine PSBMD is modified to set the value of the placeholder to 0 \ninstead of 1. This ensures that the filer routine will create the "B" \nindex correctly. \n \nTechnical Resolution:\n---------------------\n1. INC19372204 - Missing "B" index for solution, Addictive in File 53.68\nLines modified: RPC+37, RPC+39, RPC+42, RPC+43\nBefore this patch these lines set the following\n ^PSB(53.68,+PSBIENS,.6,I,0)=I\n ^PSB(53.68,+PSBIENS,.7,I,0)=I\n ^PSB(53.68,+PSBIENS,.6,I,0)=X\n ^PSB(53.68,+PSBIENS,.7,I,0)=X\nAfter the patch these lines set the following:\n ^PSB(53.68,+PSBIENS,.6,I,0)=0\n ^PSB(53.68,+PSBIENS,.7,I,0)=0\n ^PSB(53.68,+PSBIENS,.6,I,0)=0\n \n ^PSB(53.68,+PSBIENS,.7,I,0)=0\n \nDefect Tracking System Ticket(s) & Overview:\n \n1. INC19372204 - Missing "B" index for solution, Addictive in File 53.68\n \n\n
\nINC20442596 - Unable to generate Expired/DC'd/Expiring Order Report in \nBCMA\n\n
\nDescription:\n \nDefect Tracking System Ticket(s) & Overview:\n \n1. INC21077835 - BCBU NOT SHOWING ACCURATE PRN MEDICATION EXPIRE DATE\n \nProblem:\n--------\nPatient with 2 PRN medications (both oral medications) set to expire \n1/21/22@2359 printed contingency MAR that shows medication expires \n1/20/22@2359. Further testing showed that the same issue is seen with IV \n===========\norders.\n \n \nResolution:\n-----------\nModify routine ALPBFRM1 so that the column for the day of the stop will \nnot be asterisks.\n \nTechnical Resolution:\n---------------------\n \nRoutine ALPBFRM1 is modified as follows:\n \nLine added at ADMTIM+16:\n . . S \nALPBNOAS=$S(ALPBPRNG:0,$$OTYP^ALPBUTL($P($G(DATA(3)),"^"))="IV":0,1:1)\nThis line sets ALPBNOAS to 0 when the order is PRN or IV\n \nLine ADMTIM+17 is modified:\n&ALPBNOAS is added to the IF condition so time is not stripped from \nSTART/STOP times when the order is PRN or IV\nThis patch addresses the following issues:\n \nLine ASTER+3 is modified:\n&(ALPBNOAS) is added to the IF condition so that '******' is not \npopulated in the column on STOP day\n \n1. INC21077835 - BCBU NOT SHOWING ACCURATE PRN MEDICATION EXPIRE DATE\n \n \n \n\n
\nThis build introduces changes to allow the BCMA GUI to display additional \nallergy information in the Patient Allergy List, add the CPRS Order Check \nto the Display Order report, and add remote allergies to the VDL \nAllergies list.\n\n
\nINC20967576 - Data is not showing in BCMA Medication History Report\n\n
\nUnable to mark a patch as removed\n\n
\nINC23089823 - Error in BCMA Medication Overview Report\n\n
\nSee FORUM patch description.\n\n
\nThis patch addresses one issue:\n \nUsers with a future termination date are not allowed to access BCBU.\n\n
\nDefect Tracking System Ticket(s) & Overview:\n \nResolution:\n-----------\nThe BCMA code (routine PSBVDLU1) was trying to decide if the med should \nbe given on Tuesday using the 2 letter code TU, the schedule name \nSATURDAY contains TU and determines that it should be given on Tuesday, \nwhich was incorrect. The code is modified to prevent this from occurring.\n \nTechnical Resolution:\n---------------------\n \nLines OKAY+40 through OKAY+43 is changed from\n S PSBDOW=$P("SU^MO^TU^WE^TH^FR^SA",U,%Y+1) ;p145\n I $F(PSBSCH,PSBDOW)>0 S PSBOKAY=1 Q PSBOKAY\n S PSBOKAY=0\n Q PSBOKAY\n \nTo\n ;PSB*3*145 Prevent Saturday schedule from being given on Tuesday\n N PSBSCH1 S PSBSCH1=PSBSCH\n I PSBSCH1["SATU" S PSBSCH1=$TR(PSBSCH1,"SATU","SATA")\n1. INC30190209 - SATURDAY SCHEDULE PROMPT BCMA VDL TO ADMINISTER DRUG SAT \n S PSBDOW=$P("SU^MO^TU^WE^TH^FR^SA",U,%Y+1)\n ;I $F(PSBSCH,PSBDOW)>0 S PSBOKAY=1 Q PSBOKAY\n I $F(PSBSCH1,PSBDOW)>0 S PSBOKAY=1 Q PSBOKAY\n S PSBOKAY=0\n Q PSBOKAY\nAND TUESDAY\n \nProblem:\n--------\nSATURDAY, pharmacy standard schedule prompts BCMA Virtual Due List to \nalso administer the drug on Tuesday.\n\n\nINC30094266 - BCMA show ml/hl for unit dose tab.\n\n
\nThis patch addresses one issue: Discharge edits cause deletion of a \npatient's record in the BCBU BACKUPDATA (#53.7) file even though the \npatient is currently an inpatient.\n\n
\n \nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nPatient information does not print on Order Details report\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\n***\n \n \n \n \n***\n \n \n \nThis patch is a component of the Bar Code Medication Administration \n(BCMA) - Health Services Commitee (HSC) project and is the development of \nphase one of the BCMA-HSC Coversheet. PSB*3.0*16 will interface between \nBCMA databases and the new BCMA Coversheet and its Graphical User \nInterface (GUI).\n\n
\nCorrection for two Issues:\n \nREMEDY 91869\nREMEDY 99958\n\n
\n \n*************************************************\n HD0000000118033\n \n Test Sites:\n ===========\n UPSTATE NEW YORK HCS\n SAN FRANCISCO, CA\n MEMPHIS, TN\n LITTLE ROCK, AR\n \nRoutine Summary:\n \n ================\n The second line now reads as follows:\n \n <TAB>;;3.0;BAR CODE MED ADMIN;**[patch list]**;Mar 2004\n \n CHECK^XTSUMBLD results:\n \n \n Routine Before Patch After Patch Patch List\n ------- ------------ ----------- ------------------\n \n ALPB8 ------ 1016866 8\n ALPBOP ------ 1898706 8\n ALPBPWRD 7025105 9768019 8\n ALPBPALL 6006540 6414482 8\n ALPBPPAT 5702674 5081715 8\n ALPBFRM1 9887439 11248156 8\n ALPBUTL3 3052806 4245189 8\n ALPBCBU 1637834 1710946 8\n ALPBINP 9416944 10451599 8\n ALPBUTL1 6143314 6275666 8\nEnhancements and issues addressed in this patch are as follows:\n ALPBHL1 14736637 14979457 7,8\n ALPBBK 6214167 6214134 8\n ALPBELOG 6391337 6391337 8\n ALPBFRM2 8886579 8886579 8\n ALPBFRMU 4053521 4295514 8\n ALPBGEN 10414189 10201828 7,8\n ALPBGEN1 8591971 8809016 8\n ALPBGEN2 2679718 2679718 8\n ALPBIN 4105691 4105691 8\n ALPBIND 5809117 5809117 8\n \n ALPBPARM 8937865 9127203 8\n ALPBSP1 4545482 4545482 8\n ALPBSP2 845669 845669 8\n ALPBSPAT 2404489 2404489 8\n ALPBSWRD 5435921 5435921 8\n ALPBUTL 9642997 9642997 8\n ALPBUTL2 1954969 1954969 8\n \n \nPatch retrieval Instructions:\n \n====================================\nTo obtain the software use one the following OI Field Offices'\nANONYMOUS.SOFTWARE directories:\n \n \n Albany ftp.fo-albany.domain.ext anonymous.software\n Hines ftp.fo-hines.domain.ext anonymous.software\n Salt Lake City ftp.fo-slc.domain.ext anonymous.software\n \nThe distribution file is as follows.\n1. It was reported by a site that Lodgers and Dom patients were\n \nPSB_3_8.KID\nPSB_3_8.ZIP (optional see note below)\n \n****************Note for optional zip file********************\nThe Zip file in this patch contains an updated Cache.Dat file.\nOn new installations it is recommended that you use the new\nCache.dat file released with this patch. If this is used for\nan existing workstation then the workstation would need to\nbe initialized with patient data.\n creating alerts. Lodgers and Dom patient are now screened.\n**************************************************************\n \n \n The documentation distribution includes:\n \n FILE NAME DESCRIPTION\n \nPSB_3_BCBU_IG_R0206.PDF BCMA Backup System (BCBU)\n INSTALLATION GUIDE\n \n \n \n \n Installation Instructions:\n ==========================\n This patch can be installed with users on the system. Installation will\n take less than 1 minute.\n \n Suggested time to install: non-peak requirement hours.\n \n 1. From the Kernel Installation & Distribution System menu, select\n2. It was reported that when a patient was discharged the discharged \n the LOAD DISTRIBUTION option and load PSB_3_8.KID\n \n 2. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n \n 3. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 4. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter PSB*3.0*8):\n \n message was not always being sent to the workstations and an alert\n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch (routines,\n DDs, templates, etc.).\n c. Verify Checksums in Transport Global - this option will ensure\n the integrity of the routines that are in the transport global.\n \n was being generated. The problem was caused by how movements were\n 5. Use the Install Package(s) option and select the package PSB*3.0*8.\n \n 6. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n YES//" respond NO.\n \n 7. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//" respond NO.\n \n 8. If any routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n sent to the Contingency by Patient Movements. The Contingency will\n completion.\n \n \n \n \nPost-Installation Steps (Important)\n \nA new option, PSB BCBU WRKSTN PURGE ORDERS, was released as part of\nPSB*3.0*8 build. IRM staff must add it to the list of Scheduled Startup\nOptions in TaskMan on the workstations. To do this, access menu\n compensates for these issues now.\nSchedule/Unschedule Options on the TaskMan Management menu. This option\nshould be queued to run during non peak hours and set with a rescheduling\nfrequency of 1D. Review the Workstation parameter settings using the PSB\nBCBU WRKSTN PARAMETER EDIT option to make changes on how much patient\nhistorical data is retained\n \n Example Installation:\n=====================\n \nSelect Installation Option: 1 Load a Distribution\n \n \nEnter a Host File: C:\\BCMABU\\PSB_3_8.KID\n \n \nKIDS Distribution saved on Jun 16, 2005@09:04:12\n \nComment: BCBU UPDATES AND CORRECTIONS\n \nThis Distribution contains Transport Globals for the following Package(s):\n \n3. When printing the Medication Administration Report (MAR) for current\nBuild PSB*3.0*8\n \nDistribution OK!\n \nWant to Continue with Load? YES//\n \n PSB*3.0*8\n \nUse INSTALL NAME: PSB*3.0*8 to install this Distribution.\n \n orders it would also include any non-active orders for the current\n \n \nSelect Installation Option: 6 Install Package(s)\n \nSelect INSTALL NAME: PSB*3.0*8 Loaded from Distribution Loaded\nfrom Distribution 6/16/05@08:09:36\n \n => BCBU UPDATES AND CORRECTIONS ;Created on Jun 16, 2005@09:04:12\n \n \n day being printed. The report now goes by date and time.\nThis Distribution was loaded on Jun 16, 2005@08:09:36 with header of\n \n BCBU UPDATES AND CORRECTIONS ;Created on Jun 16, 2005@09:04:12\n \nIt consisted of the following Install(s):\n \n PSB*3.0*8\n \nChecking Install for Package PSB*3.0*8\n \n \nInstall Questions for PSB*3.0*8\n \nIncoming Files:\n \n 53.7 BCMA BACKUP DATA\n \nNote: You already have the 'BCMA BACKUP DATA' File.\n \n \n 53.71 BCMA BACKUP PARAMETERS\n4. A new purge utility has been introduced for the workstation. It\n \nNote: You already have the 'BCMA BACKUP PARAMETERS' File.\n \n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n \n********************Important Note***************\n allows the site to define how much historical data to maintain on the\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// TCP/IP Terminal\n \n Install Started for PSB*3.0*8 :\n workstation. Any unwanted data will be removed from the workstation.\n \nJun 16, 2005@08:12:22\n \nBuild Distribution Date: Jun 16, 2005\n \nInstalling Routines:\n \n Jun 16, 2005@08:12:22\n \n Installing Data Dictionaries:\n \n \n Jun 16, 2005@08:12:22\n \n Installing PACKAGE COMPONENTS:\n \n Installing FORM\n \n Installing OPTION\n \n Jun 16, 2005@08:12:23\n5. The way the Med Log information is being displayed on the MAR has\n \nRunning Post-Install Routine: POST^ALPB8\n \n Updating Routine file...\n \n Updating KIDS files...\n \n PSB*3.0*8 Installed.\n \n Jun 16, 2005@08:12:23\n changed. In the previous version the information was displayed by date\n \n Install Message sent #2318\n \n Install Completed\n entered and the user had to select a starting date when running the\n MAR. Depending on the frequency of the MED Log this could cause the\n report to be long. The report now reverses the order of the Med Log\n information so the report displays the most recent first. The user can\n then opt for how many to display by numeric value such as 1, 2 or more.\n \n \n6. A blank page was added between the patients on multi patient\n reports for easier sorting.\n \n7. Provider comments were moved to be displayed along with the Drug\n and Give information.\n \n8. The sorting of orders on the MAR reports have been grouped by the\n order type. Types include Pending, Unit Dose, IV and PRN.\n \n If the site is running the BCMA Contingency software then this\n9. A place holder for the Last Action of drugs has been added to the\n reports. A future patch will complete the functionality.\n \n10. A problem with Pending orders remaining on the workstation when\n replacement orders are done by pharmacy has been resolved.\n \n11. A problem was discovered with the user access updater. When a user's\n name changed it did not update the Contingency workstations\n correctly.\n \n patch must also be installed on the workstations. Once installed\n12. A <UNDEFINED>NURV+16^ALPBCBU error has been resolved.\n \n13. A problem with updating the Contingency workstations during a patient\n movement activity has been addressed.\n \n14. Added the function to sort MARS by Room/Bed or by Patient Name.\n \n15. Patients that had no allergies reported to the contingency do not\n display any allergies data on a MAR. Now when no allergies are found\n on the contingency, the following will display on the MAR. "Allergies:\n it is suggested that the sites review the Contingency system\n No allergies reported to the Contingency"\n \n16. Possibility of routine ALPBPWRD erroring out at line\n ..S ^TMP($J,"BCBU",+ALPRM,ALPRM,ALPBD,ALPBPTN)=ALPBIEN\n When sorting by room/bed Cache tries to convert certain room/beds like\n 5E155 and produces a <MAXNUM> error. The problem occurs when the\n variable is manipulated. Cache will take the 5E155 and convert it to\n "5" appended with 155 zeros. A code change was made to prevent this\n issue.\n \n reports.\n Associated Tickets\n =================\n HD0000000093730\n HD0000000068823\n HD0000000068579\n HD0000000068341\n HD0000000068274\n HD0000000068227\n HD0000000068220\n HD0000000068196\n \n HD0000000068158\n HD0000000068107\n HD0000000068024\n HD0000000068021\n HD0000000067859\n HD0000000067827\n HD0000000067769\n HD0000000067729\n HD0000000067714\n HD0000000096190\n\n
\nThis patch addresses three Remedy tickets, HD68121, HD113034, and HD90393.\nthe undefined error will not occur. This locking fix was created by the \nMinneapolis IRM staff, and has been working in their production area for \nmonths. The fix is being brought back to the VMP group so it can become \npart of a national patch release, and other sites can avoid this error in \nthe future.\n \nThe second issue, HD113034, happens when a medication PATCH (such as \nFentanyl) is marked as REMOVED after initially being given to the \npatient. If you right-click the mouse on the order in BCMA and mark the \npatch as "REMOVED", when you subsequently check the med log, the units \n \ngiven remains 1. However, if you use the BCMA menu option FILE/EDIT Med \nLog and mark it "REMOVED", the units given becomes 0, and the audit trail \nshows "Doses given '1' deleted". The correct value for units given is \nactually 1 (as right-clicking the mouse shows), because the medication \nwas indeed given, but the patch was subsequently removed, not deleted or \nrefused.\n \nThe third issue in this patch, HD90393, addresses a printing problem with \nthe PRN Effectiveness report when it is printed by Ward/Room-Bed. When \nthis printing filter is applied, the report prints in patient DFN order, \n \nnot Ward/Room-Bed order. This fix corrects a problem in the BCMA code so \nthat when the Ward/Room-bed filter is applied, the report will print \nproperly.\nThe first issue, HD68121, is the result of a file locking problem with \nthe routine PSBMD. This error only appeared after the site converted to \nCache' version 5. There is an undefined variable error created with \nMissing Dose reports in Pharmacy, even though a record is created in \n^PSB(53.68). By attempting to lock the ^PSB(53.68) file before \nattempting to print the report, it will ensure that the file exists so \n\n
\nStore error generated when using Display Order option in BCMA\n\n
\nThis patch addresses Remedy Ticket HD127231, which arose after the \nthe first six lines of the orderable item in duplicate.\n \nThe fix included in this patch will still print the patient header \ninformation on subsequent MAH pages, but it will not reprint the first \nsix lines of the orderable item information.\n \n**NOTE** This fix only affects the report when printed to a printer.\nThis does not affect the GUI display or printing the report to the\nterminal screen.\ninstall of patch PSB*3*20. Patch PSB*3*20 added the patient header \ninformation to the MAH report if the report for a medication ran longer\nthan one page. Additionally, PSB*3*20 was designed to reprint the first \nsix lines of the orderable item information on subsequent pages to help \nthe nurses keep track of what medication they were viewing\non the MAH report. However, when the next medication on the report was \ndue to be printed, and a page break occurred before the orderable item \ninformation was printed, the second page of the report printed\n\n
\n1. Problem: NOIS MAD-0104-40858 \n \n2. Problem: NOIS BUT-0204-20463\n The Medication Administration History [PSBO MH] option and the Due \n List [PSBO DL] option add an exclamation point (i.e., Spec Inst:\n !Please verify) to the prefix of a Special Instruction.\n \n Corrective Action: The Medication Administration History [PSBO MH] \n option and the Due List [PSBO DL] option correctly removes \n the exclamation point (i.e., Spec Inst: Please verify) added\n to a Special Instruction.\n The Bar Code Medication Administration (BCMA) reports,\n \n3. Problem: NOIS BED-0204-10327\n When a clinician administers a Pro Rea Nata (PRN) medication using \n the Manual Medication Entry [PSB MED LOG NEW ENTRY] option, and the\n administration date/time is set to an earlier timeframe, the PRN\n administration date/time displays incorrectly on BCMA PRN\n Effectiveness Log Report as the entered date/time of this \n administration occurred.\n \n Corrective Action: When a clinician administers a PRN medication \n with the exception of the Cumulative/Vitals Measurement Report, does \n using the Manual Medication Entry [PSB MED LOG NEW ENTRY] option, and\n the administration date/time is set to an earlier timeframe, the PRN\n administration date/time displays correctly on the BCMA PRN\n Effectiveness Log Report as the actual date/time of the\n administration.\n \n4. Problem: NOIS NTH-0304-72663\n A "Null subscript" error occurs at routine line "EN+4^PSBVDLPA"\n when there is single patient with data entered in the BCMA Medication \n Log File (#53.79) and indexes. This error occurs during the \n not display allergy information in the reports header.\n initial implementation of the BCMA Graphical User Interface (GUI) \n system.\n \n Corrective Action: The initial implementation of the BCMA GUI will \n not generate a "Null subscript" error at routine line "EN+4^PSBVDLPA".\n \n Corrective Action: The BCMA Reports, with the exception of the \n Cumulative/Vitals Measurement Report, displays allergy information in\n the reports header. The Reactions header has also been removed\n from the report and replaced with the "ADRs:" header.\n\n
\n***************************Important Note*************************\n1. It was reported that after loading Patch PSB*3*8, the medication log \n \nSelect Installation Option: 1 Load a Distribution\n \nEnter a Host File: USER$:[COWNIEK]PSB_3_29.KID\n \nKIDS Distribution saved on Apr 13, 2006@16:09:30\n \nComment: patch 29\n \nThis Distribution contains Transport Globals for the following Package(s):\n history was no longer printing. \n \n PSB*3.0*29\n \nDistribution OK!\n \nWant to Continue with Load? YES// \n \nLoading Distribution...\n \n PSB*3.0*29\n \n \nUse INSTALL NAME: PSB*3.0*29 to install this Distribution.\n \nSelect Installation Option: 6 Install Package(s)\n \nSelect INSTALL NAME: PSB*3.0*29 Loaded from Distribution \n4/17/06@12:31:58\n \n => patch 29 ;Created on Apr 13, 2006@16:09:30\n \n Example:...\nThis Distribution was loaded on Apr 17, 2006@12:31:58 with header of \n patch 29 ;Created on Apr 13, 2006@16:09:30\n \n It consisted of the following Install(s):\n \n PSB*3.0*29\n \nChecking Install for Package PSB*3.0*29\n \nInstall Questions for PSB*3.0*29\n \n \nIncoming Files:\n \n 53.7 BCMA BACKUP DATA (Partial Definition)\n \nNote: You already have the 'BCMA BACKUP DATA' File.\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n \n BCMA MEDICATION LOG HISTORY\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// UCX TELNET SESSION\n \n Install Started for PSB*3.0*29 : \n \n Log Date Message Log Entry Person\nPSB*3.0*29 \n--------------------------------------------------------------------------\n \n Apr 17, 2006@12:34\n \nBuild Distribution Date: Apr 13, 2006\n \n Installing Routines:\n \n Apr 17, 2006@12:34\n No entries since the above date are on file.\n \n Installing Data Dictionaries: \n \n Apr 17, 2006@12:34\n \n Updating Routine file...\n \n Updating KIDS files...\n \n PSB*3.0*29 Installed. \n \n \n Apr 17, 2006@12:34\n \n Install Message sent #1504712\n \nInstall Completed\n \n \n \nRoutine Summary:\n This was caused by a missing cross reference (IMLOG) in file 53.7. \n================\n \nThe second line now reads as follows:\n<TAB>;;3.0;BAR CODE MED ADMIN;**[patch list]**;Mar 2004 \n \n \n \n CHECK^XTSUMBLD results:\n \n Routine Before Patch After Patch Patch List\n If the site is running the BCMA Contingency software then this\n Cross reference has been added.\n ------- ------------ ----------- ----------\n ALPBPALL 6414482 6407974 8,29\n \nRoutine Information:\n====================\n \nRoutine Name: ALPBPALL\n \n Checksum:\n \n \n CHECK1^XTSUMBLD results:\n \n Routine Before Patch After Patch Patch List\n ------- ------------ ----------- ----------\n ALPBPALL 25867705 25843033 8,29\n2. It was reported that the Print all option was not working correctly. \n Routine ALPBPALL has been corrected.\n \n \n Associated Tickets\n ==================\n HD0000000139114\n HD0000000138995\n patch must also be installed on the workstations. Once installed\n HD0000000135330\n \n \n \nTest Sites:\n===========\nBIRMINGHAM, AL \nBRONX, NY\nMILWAUKEE, WI\nMOUTAIN HOME, TN\n it is suggested that the sites review the Contingency system \n \n \nPatch retrieval Instructions: \n====================================\n \nTo obtain the software use one the following OI Field Offices' \nANONYMOUS.SOFTWARE directories:\n \n Albany ftp.fo-albany.domain.ext anonymous.software\n Hines ftp.fo-hines.domain.ext anonymous.software\n reports. \n Salt Lake City ftp.fo-slc.domain.ext anonymous.software\n \n \n \nThe distribution file is as follows.\n \nPSB_3_29.KID\n \nThere is no documentation distribution included in this patch.\n \n******************************************************************\nInstallation Instructions:\n==========================\n \nThis patch can be installed with users on the system. Installation will\ntake less than 1 minute.\n \nSuggested time to install: non-peak requirement hours.\n \n 1. From the Kernel Installation & Distribution System menu, select\n the LOAD DISTRIBUTION option and load PSB_3_29.KID\n \n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter PSB*3.0*29):\n \n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\nIssues addressed in this patch are as follows: \n \n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch (routines,\n DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - this option will ensure\n the integrity of the routines that are in the transport global.\n \n 4. Use the Install Package(s) option and select the package PSB*3.0*29.\n \n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? \n YES//" respond NO.\n \n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//" respond NO.\n \n \nExample Installation:\n=====================\n\n
\n \nIssues (PSI) and Remedy Ticket resolution and BCMA Coversheet refinement.\n8. Enhancement: Enhanced "*UNKNOWN* Action Status" support.\n BCMA Medication Log File (File #53.79) entries having unknown \n Action Status (field #.09) data can be maintained via the GUI BCMA \n Edit Med Log only. These entries may be maintained by persons holding\n the BCMA manager's key [PSB MANAGER] or that user unable to complete \n the original administration. PSB*3.0*13 supports the VISTA "Unknown \n Action Status Report" option [PSBO XA]. The [PSBO XA] option \n provides persons holding the BCMA manager's key [PSB MANAGER] \n resource to generate a report to display BCMA Medication Log File \n (#53.79) entries having "unknown" Action Status (field #.09) data. \n***\n Users holding the BCMA manager's key [PSB MANAGER] can access the \n PSBO XA report via the BCMA GUI as well. BCMA has been enhanced to \n display a "pop-up box" when a user begins an action on an order \n \n \n9. Enhancement: Saved Coversheet Personal Parameters\n PSB*3.0*13 will maintain personal parameters per BCMA Coversheet \n views to be saved and retrieved when using BCMA. \n \n1. Problem: PSI-05-064\n BCMA functionality enables a BCMA user to edit the free text \n BCMA MEDICATION LOG FILE-DISPENSE DRUG SUBFILE (# 53.795) "Units\n of Administration" (field #.04) for an administered medication, when \n using the Edit Medication Log. Consequently, the GUI Edit \n Medication Log (Edit Med Log) allows a BCMA user to modify text in \n the field labeled "Units" of the "BCMA - Edit Med Log" dialog box. \n***\n The user is able to change the "Units" from "PATCH" to any other text\n value. Changing a "PATCH" medication to some other "Units", causes \n BCMA to not process the administration properly; and causes the BCMA \n Virtual Due List (VDL) to not present the administration properly.\n \n Corrective Action:\n The BCMA GUI Edit Med Log will not allow any BCMA user to edit the \n BCMA MEDICATION LOG FILE/DISPENSE DRUG SUBFILE (# 53.795) "Units \n of Administration" (field # .04) of an administered "PATCH" \n medication.\n \n \n2. Problem: PSI-05-032\n The VDL displays a GIVEN medication patch until it has been marked as\n "REMOVED". This is causing some confusion to users.\n \n Corrective Action:\n BCMA will provide a site parameter that will specify the number of \n days (7-14) a GIVEN patch will display on the VDL. The count of \n days the GIVEN patch displays on the VDL begins when the \n medication order expires. This parameter may be set to ""\nThis patch is a component of the Bar Code Medication Administration \n (null) to allow GIVEN patches to display on the VDL until it is \n marked as REMOVED.\n \n \n3. Problem: PSI-05-115\n The Special Instructions on the VDL will display the entire Special \n Instructions by wrapping the text as needed using the spaces in the \n Special Instructions. However, ff a word or phrase (without spaces) \n in the Special Instructions can not be wrapped due to the word or \n phrase being longer then the width of the column, the text would be \n(BCMA) Version 3.0. The main function of PSB*3.0*13 and the \n truncated when the text ran into the right side of the column. In \n addition, when the above happens, some of the ending words in the \n special instructions may be omitted as well.\n \n Correction Action:\n When a word or phrase (without spaces) can not be wrapped and does \n not fit in the column width, the text will be truncated with an \n ellipsis to indicate that a portion of the word or phrase was \n truncated. The occasional omission of ending words in the special \n instructions will be corrected. \ncorresponding BCMA Graphical User Interface (GUI) software (BCMA Version 3\n \n \n4. Problem: HD0000000121694\n While a medication patch is being "administered" using Manual \n Medication Entry[PSB MED LOG NEW ENTRY], that particular scheduled \n administration does not display on the BCMA Virtual Due List (VDL).\n \n Corrective Action:\n Display the saved "action status" of an administration, while it is \n being administered using Manual Medication Entry [PSB MED LOG NEW \nPatch 13 [3.0.13]) is to support BCMA v3.0 Clinical Context Object \n ENTRY]\n \n \n5. Problem: HD0000000127625\n An error occurs when the BCMA coversheet is to display data for one \n order only; and that order is an expired, large volume IV.\n \n Corrective Action:\n The BCMA Coversheet will display without error when the only order \n information to display on the BCMA coversheet pertains to an expired,\nWorkgroup (CCOW) compliance. The PSB*3.0*13 GUI and this Character User \n large volume IV.\n \n \n6. Problem: HD0000000132184\n An error occurs when the BCMA GUI Computerized Patient Record System \n (CPRS)/BCMA Medication Order Button (MOB) is used and ORDER \n File (#100) PATIENT LOCATION (field #6) data does not link to a \n WARD LOCATION File (#42) entry.\n \n Corrective Action:\nInterface (CHUI) software (PSB*3.0*13) also support Patient Safety \n BCMA will provide HOSPITAL LOCATION File (#44) data per ORDER File \n (#100) PATIENT LOCATION (field #6) data when the CPRS/BCMA MOB is \n used. CPRS will ORDER File (#100) PATIENT LOCATION (field #6) data \n to a HOSPITAL LOCATION File (#44) entry \n \n \n7. Enhancement: CCOW compliancy\n This patch (PSB*3.0*13) will enable BCMA CCOW compliancy.\n \n \n\n
\nThis patch corrects display problems with the Missed Med Rpt\n\n
\nProblem with Medication History Report.\n\n
\n \n \n \nEnhancement - Compliance with Section 508 of the Rehabilitation Act of\n 1973:\n PSB*3.0*10 and its corresponding BCMA GUI[Version 3 Patch 10 \n (3.0.10.9)] will assure BCMA is compliant with Section 508 of the \n Rehabilitation Act of 1973, after proper installation as defined in \n the BCMA 508 Software Requirements Specifications.\n \n \nProblem #HD0000000159234 - Means Test Pop-up Does Not Display:\n \nEnhancement - Signal BCMA Idle Timeout:\n BCMA GUI Version 3 Patch 10 will signal to the user as BCMA Idle \n Timeout limit is approaching. There will be an audible "beep" thirty\n (30) seconds, twenty (20) seconds, and ten (10) seconds prior to the\n idle time limit set via the "BCMA Idle Timeout" site parameter.\n \n \nEnhancement - Indication When not all Drugs Have Been Scanned Per a\n Multiple Drug Order :\n Bar Code Medication Administration (BCMA) Graphical User Interface\n BCMA GUI Version 3 Patch 10 will display a message box when\n the user has not scanned all the dispensed drugs per a medication \n order that includes multiple dispensed drugs. The message box will \n display, requesting user confirmation.\n (GUI) Means Test Pop-Up Does Not Display after the installation of\n BCMA GUI Version 3 Patch 13. \n \nCorrective Action:\n Modify the BCMA GUI to allow the BCMA GUI Means Test Pop-up to display\n when appropriate. \n\n
\nEdit Med Log creates duplicate entries\n\n
\nMed Route display issues\n\n
\nUnable to Edit Med Log in BCMA\n\n
\n \n \n \n1. Problem: PSI-06-029/HD0000000126326\n Processing the BCMA Missed Medications Report causes the client to \n "time-out" when the report is to display within the BCMA GUI \n Application and prior to sending the report to a printer.\n \n Corrective Action:\n Make the Missed Medications Report process faster so the client \n does not "time-out".\n \n \n \n2. Problem: PSI-06-019/HD0000000130671\n There is difficulty determining the application of a medical patch \n that has not been marked as REMOVED when that order has expired or \n discontinued.\n \n Corrective Action:\n Allow the user to view and act on patches for expired or discontinued \n orders when the patient's BCMA Virtual Due List (VDL) first opens.\nThis patch is a component of the Bar Code Medication Administration \n \n \n3. Problem: PSI-06-056/HD0000000131075\n Issues related to extra Pro Re Nata (PRN) doses of medication \n ordered as QDPRN or BIDPRN and reports of nurses missing the last \n administration time, have cause patient safety concerns. \n \n Corrective Action:\n The BCMA PRN administration dialog box will be enhanced to provide the\n following features for all PRN administrations: Icon, Schedule, Last\n(BCMA) Health Systems Committee (HSC) Phase III project. The main\n Given and Reminder checkbox and statement.\n \n \n4. Problem: PSI-06-014/HD0000000128909\n Administration problems have been caused when Med Route abbreviations\n on the VDL have been confused.\n \n Corrective Action:\n Display the expanded version of the Med Route.\n \nfunction of PSB*3*32 and the corresponding BCMA Graphical User\n \n5. Problem: PSI-06-060/HD0000000143603\n Due to a limitation in the Delphi application, there is a 255-pixel\n limit on the row height in the BCMA GUI VDL that results in truncation\n of an order when there are a large number of additives/solutions on\n the order.\n \n Corrective Action:\n Adjust display area of medications on the VDL to compensate for orders\n with a large number of items to display.\nInterface (GUI) software (BCMA Version 3 Patch 32 [3.0.32.*]) is to\n \n \n6. Enhancement: New Coversheet Overview Reports.\n As a part of the BCMA HSC Phase III, patch PSB*3.0*32 and \n PSB.3.0.32 GUI will provide BCMA users with reports that display \n Coversheet Overview data. There is a new Coversheet Report for each \n Coversheet Overview.\n \n \n7. Enhancement: Global Report Enhancements.\nprovide the BCMA user with additional BCMA Coversheet and reporting \n Various enhancements have been made to BCMA reports in general. These\n enhancements are presented in BCMA HSC Phase III documentation.\n \n \n8. Enhancement: Coversheet and Other Miscellaneous Enhancements.\n A variety of new Coversheet and miscellaneous feature will be \n supported with the installation of this patch. The BCMA HSC Phase \n III documentation provides details of these new features.\nsupport.\n \n\n
\nCan't enter Manual Med entry for discharged patient.\n\n
\n*** ATTENTION: This patch includes a new Graphical User Interface \n use. The correct GUI must be installed to support BCMA \n Computerized Patient Record System (CPRS) Med Order \n functionality ***\n \nFor retrieval and installation instructions, please see the Client\nInstallation Instructions section.\n \n 1. Problem: NOIS HWH-0204-41213\n The Instructor information does not display in the legend of the \n Medication Administration History [PSBO MH] option, and the audit log\n (GUI) executable file. Installation of this new GUI is \n of the Medication Administration Log [PSBO ML] option.\n \n Corrective Action: The Instructor information displays in the legend \n of the Medication Administration History [PSBO MH] option, and the\n audit log of the Medication Administration Log [PSBO ML] option.\n \n2. Corrective Action: When student and instructor information is \n present at login the GUI BCMA CPRS Med Order button is disabled.\n \n3. Problem: NOIS HUN-0104-20931\n REQUIRED in order for the patch to function. The new GUI\n Infusing IV bags are duplicated on a "following" order after the\n order that was active when the IV bag was infusing has become\n "discontinued". The Virtual Due List (VDL) attempts to display \n duplicate bags and associates the same IV bags with multiple orders.\n \n Corrective Action:\n When an order with an infusing bag is discontinued, the VDL will\n either continue to display the infusing bag with the discontinued \n order, or the VDL will display the infusing bag with an active \n "following" order, but not both.\n MUST be installed IMMEDIATELY after the KIDS install in \n \n4. Problem: NOIS ISB-0304-30352\n If an IV order with an infusing bag expires and the patient's record \n is not accessed using Inpatient Medications (IPM) (e.g., the\n Inpatient Order Entry [PSJ OE] option) the following message may\n appear, hindering an user's attempt to take action on the order:\n \n "Either the order status or the current scan status displayed \n on the VDL does not match the status recorded in VistA! This \n may be due to someone editing the order in VistA or another \n order for the software to function. This Patch includes a \n individual scanning the medication. Your current action will \n be canceled and the VDL will be refreshed to reflect the most \n current order information."\n \n Corrective Action:\n A user will be able to take action on an expired IV order having an \n infusing bag via the BCMA GUI VDL as appropriate.\n \n5. Problem: NOIS MOU-0304-32821\n The temporary, scratch global ^PSBORDA is automatically monitored and \n Post install that corrects problem number six below. The \n documented via journaling procedures. It is not necessary to journal \n this temporary global since it is used solely as a temporary data \n storage area.\n \n Corrective Action:\n The global ^PSBORDA will be renamed as an appropriate scratch "^TMP" \n global with the first two subscripts being "PSB" followed by "$J".\n \n6. Problem: NOIS ISB-0404-31737\n With the release of BCMA Version 2 (PSB*2.0), any unit dose \n installation time frame for this post install will vary based\n order that is displayed on the "IVP/IVPB" tab and administered will \n have a Ward Stock number generated and placed in the IV Unique \n ID field (FIELD #.26) of the BCMA Medication Log (FILE #53.79)\n The Ward Stock number is stored in the BCMA Medication Log global and \n is not displayed on the VDL or any BCMA Report.\n \n Corrective Action:\n A unit dose order that is displayed on the "IVP/IVPB" tab and \n administered will not have a Ward Stock number generated and placed\n in the IV Unique ID field (FIELD #.26) of the BCMA Medication Log \n on the size of the site. This build will validate the correct \n (FILE #53.79). A post install will clean up all incorrect previous\n entries.\n version of Bar Code Medication Administration (BCMA) GUI is in\n\n
\nThis patch will add the new Barcode Label Print [PSBO BZ] option \nto the Bar Code Medication Administration application. Review \nthe patch description for detail functionality. \n\n\n
\nThis patch contains miscellaneous fixes for the BCMA Contingency plan \nfunctionality.\nbackup system.\n \nThis patch addresses the following remedy tickets:\nHD139965 -- Patient data not available on clients after PSB*3.0*8\nHD150133 -- Problem with new Contigency set up.\nHD189870 -- Variable needs to be NEW'd\n \nThis patch also contains an enhancement to the BCBU user init \n\n
\nMed Admin History report intermittently displays\n\n
\nDUE LIST DISPLAYED MED NOT DUE\n\n
\nThis patch corrects the following remedy tickets for BCMA issues:\n \n \n \nHD189271 - A piece of code in PSBOPM needs to be changed.\nHD167891 - Medication Administration History display problem in CPRS\n\n
\n \nVersion 3.0 Managing Scanning Failures (MSF) project. The main function\nof PSB*3*28 and the corresponding BCMA GUI software (BCMA Version 3 Patch\n28 [3.0.28]) is to document scanning failures during BCMA patient and\nmedication verification. Please see Release Notes document for more \ndetails on the following enhancements.\n \n1. Enhancement: Document Unable to Scan events. This patch will enable\n the user to document Unable to Scan events that occur during BCMA\n patient and medication verification. The Computerized Patient Record\n System Medical Order Button and the creation of ward stock orders in\nATTENTION: This patch includes a new Graphical User Interface (GUI)\n BCMA will not be fully supported by the Unable to Scan functionality.\n \n2. Enhancement: Send a MailMan message for each Unable to Scan event.\n When a user documents an Unable to Scan event, a message will\n be sent to persons who are members of the mail group established\n via the BCMA Site Parameter's Unable to Scan mail group field\n setting. This message will also be sent to the user submitting\n the Unable to Scan event documentation.\n \n3. Enhancement: Add two new Unable to Scan Reports.\nexecutable file. Installation of this GUI is required immediately\n Detailed and summary reports of BCMA Unable to Scan data may be\n executed by persons holding the PSB UNABLE TO SCAN security key.\n \n4. Enhancement: Added Division Filtering to Unable to Scan Reports.\n The user's division is detected upon login, and used to filter\n Entire Facility and Nurse Unit options on the Summary Report, and All\n Patients/Wards option on the Detailed Report.\n \n5. Enhancement: Added new PSB*3*32 functionality to the MSF reports.\n Patch PSB*3*32 created new report functionality requirements, such as\nafter the KIDS install for the Patch to function.\n allowing a start and stop time, and report preview. For consistency,\n these have been included in the MSF reports.\n \n6. Enhancement: Usability.\n Made changes based on feedback from the MSF usability study.\n \n7. Enhancement: Allow Action on Infusing or Stopped IV Bags.\n Added Take Action on Bag option to the IV Bag Chronology Window to\n allow user to take action on infusing or stopped bags without having\n to rescan the IV bag.\n \nFor retrieval and installation instructions, please see the Client\nInstallation Instructions section.\n \nThis patch is a component of the Bar Code Medication Administration (BCMA)\n\n
\nThis patch will correct the following issues.\nHD226037 - Initials don't show on MAH or Med log for first action on med\nHD190817 - Record needs to show the initials of the nurse who \n administered the medication not the initials of nurse who \n created the error.\nHD255639 - Missing Field Definition.\n \nPartial Correction for\nHD260760 - Routine's Don't meet 1995 M standard.\n\n
\nONE-TIME PRN CAN BE GIVEN MULTIPLE TIMES.\n\n
\nThis patch provides the components for the Class III to Class I conversion\nproject Immunizations Documentation by BCMA.\n \nIncluded in this patch is a new option named Immunizations Documentation\nby BCMA Nightly Task [PSB PX BCMA2PCE TASK].\n \nPatch PSS*1*141 provides the Pharmacy Data Management portion of the\nproject.\n\n
\nThis patch will correct errors generated when BCMA is used in \nenvironments with mixed Operating Systems (OS)\n\n
\n*** ATTENTION: This patch includes a new Graphical User Interface (GUI)\n 1. Problem: NOIS BUT-1203-21780\n chronological order; chronologically latter order activities will display\n before earlier order activities.\n Bar Code Medication Administration (BCMA) users are not able to re-\n instate a medication patch if it had been unintentionally marked as \n 'REMOVED' via BCMA. This issue has been delegated a 'PATIENT SAFETY' \n keyword.\n \n Corrective Action:\n The removal of a medication patch may be undone if it had been\n unintentionally marked as 'REMOVED'; this may be accomplished by the\n user who marked the medication patch as 'REMOVED' or by a user\n executable file. Installation of this new GUI is REQUIRED in order\n allocated the "PSB MANAGER" key.\n \n \n 2. Problem: NOIS ISB-0204-30176\n The prompt "Enter the DATE of Administration: Today//" of the Manual \n Medication Entry [PSB MED LOG NEW ENTRY] option has caused confusion.\n The user unintentionally accepts the default (i.e. "Today") when \n attempting to document a past administration. \n \n Corrective Action:\n for the patch to function. The new GUI MUST be installed IMMEDIATELY \n The prompt "Enter the DATE of Administration: Today //" will be\n replaced by the prompt "Enter the DATE the medication was \n administered: //" when using the Manual Medication Entry \n [PSB MED LOG NEW ENTRY] option. Also, this new prompt will not accept\n the entry of a future date/time for an administration.\n \n \n 3. Problem: NOIS PHO-0904-61033\n The BCMA Medication History report does not show large volume IV\n medications data when viewed via the Computerized Patient Record System\n after the KIDS install in order for the software to function. *** \n (CPRS) GUI "Orders/View/Details..." option.\n \n Corrective Action:\n The BCMA Medication History report will display large volume IV \n medications data when viewed via the CPRS GUI.\n \n \n 4. Problem: NOIS LAH-0404-61280\n The user is unable to access a patient's VDL when receiving an error\n message containing the text "GETPRNS+17^PSBPRN". These messages occur\n \n when a patient is no longer admitted when that patient's VDL is\n refreshed.\n \n Corrective Action:\n BCMA will continue, without error, when a patient is no longer admitted\n while that patient's VDL is being viewed and refreshed.\n \n \n 5. Problem: NOIS MWV-0704-20690\n The user is able to change the status of an order's patch medication\n For retrieval and installation instructions, please see the Client\n while that order concurrently has another 'GIVEN' and not 'REMOVED'\n patch medication. After the initial status of a patch of that order has \n been set to a status other than 'GIVEN', that patch can then be\n administered via BCMA, without a warning to the user concerning a\n concurrently 'GIVEN' patch.\n \n Corrective Action: \n BCMA will not allow multiple patches of a patch medication order to be\n at the status of 'GIVEN' concurrently.\n \n Installation Instructions section.\n \n 6. Problem: NOIS SFC-0704-60956\n The user is unable to edit a 'NOT GIVEN' administration using the VISTA\n "Edit Medication Log" [PSB MED LOG EDIT] option.\n \n Corrective Action:\n The user will be able to edit 'NOT GIVEN' administrations using the GUI\n version of the "Edit Med Log" found under the "File" menu of the BCMA\n VDL.\n \n \n \n 7. Problem: NOIS CLL-0704-40997\n If an IV piggyback bag is marked as 'GIVEN', the VDL is not refreshed,\n and the VDL "start/stop time" parameters are reset making that specific\n administration no longer display on the VDL, then that 'GIVEN' bag can\n be scanned and administered again.\n \n Corrective Action:\n BCMA will not allow an IV piggyback bag to be scanned and 'GIVEN' multiple\n times.\n \n \n \n 8. Enhancement: Include Comments on the Medication History Report.\n PSB*3.0*3 will provide the user the ability to include comments that\n were documented during an administration to appear on the Medication\n History Report. This new functionality is accessible via the BCMA GUI\n and CPRS GUI.\n \n 9. Enhancement: Report Medication History in reverse chronological order.\n PSB*3.0*3 will display the Medication History Report in reverse\n\n
\nThis patch addresses 4 issues:\n1. The PRN EFFECTIVENESS field (#.22) does not show up on the "Medication \n Admin History" report but does on the "Medication Log" report.\n2. MANUAL MEDICATION ENTRY [PSB MED LOG NEW ENTRY] Issue/Unknown Status\n Report.\n3. "Missed Medications" report in BCMA did not display a missed\n medication.\n4. Problems with "Missed Medication" report.\n\n
\n This Patch Addresses 4 issues:\n 4. Patients are Duplicating on Reports for wards with similar names.\n \n 1. An invalid MUMPS date (a date prior to 12/31/1840) entered for the\n BCMA Administration Times report creates an infinite loop which sends\n out BCMA Order Problem emails.\n 2. An undefined error occurs at PTLKUP+16^PSBMLLKU when a Nursing Ward\n contains lowercase letters.\n 3. Orders with a Status of On Call do not print on the BCMA Missed Meds \n Report or the BCMA Administration Times Report\n\n
\nThis patch addresses Patient Safety issue PSPO #1401 and three\nrunning the MANUAL MEDICATION ENTRY [PSB MED LOG NEW ENTRY] option.\n3. Receiving error "<SUBSCRIPT>EN+12^PSBOMH1" when running the Medication \nAdministration History (MAH) report when the nurse has given a medication \nand does not have his/her initials in the NEW PERSON file (#200).\n4. The Medication Therapy report does not contain PRN Effectiveness \ninformation.\nadditional issues in Bar Code Medication Administration (BCMA):\n \n \n \n1. PSPO #1401 - When a pain score is entered through BCMA and then marked \n"entered in error" in Vitals, the errant pain score still shows on the \nBCMA Coversheet and other reports.\n2. Receiving an error "Error - <UNDEFINED>SCANFAIL+9^PSBMLEN1" when \n\n
\nATTENTION: This patch includes a new Graphical User Interface (GUI)\n \nThis enhancement will also bring the BCMA application compliant to\nSection 508 of the Rehabilitation Act of 1973 and Rehabilitation Act\nAmendments of 1998, which mandates that all software developed by federal\nagencies allow access to and use of information and data by individuals\nwith disabilities.\n \nPlease see the Release Notes for more details on the following\nenhancements.\n \nexecutable file. Installation of this GUI is required immediately after\n1. Enhancement: This will enable a single version of BCMA to be\n maintained by VHA and yet be installed and operate in a "plug and play"\n fashion in an IHS or Tribal facility running Resource and Patient\n Management System (RPMS).\n \n2. Enhancement: The BCMA Graphical User Interface (GUI) will display\n vital measurements from the Veterans Administration (VA)\n VITALS/MEASUREMENTS package for VHA sites or optionally use the\n IHS PCC SUITE (APC) package which supports the V MEASURMENT file, if\n operating at an IHS facility and that facility is configured to use the\nthe KIDS install for the Patch to function.\n V MEASUREMENT file.\n \n3. Enhancement: Section 508 Compliance including Edit Med Log\n Administration Selection form and a list of forms which have labels\n which will be converted to VA508StaticText.\n \n \nThis Patch also Addresses 7 reported issues:\n \n1. PSI-07-223 (PSPO-823) - If an IV order is already infusing when it is\n \n placed on provider hold, the IV can be stopped and then infused again\n while still on provider hold.\n2. PSPO-1678 - The MULTIPLE DOSE pop up form blocks the dosage on the\n Virtual Due List (VDL).\n3. All BCMA reports have a default date based on the Laptop Time instead\n of the Server Time.\n4. The MedLog form in BCMA will accept a space for the required comment.\n5. 3 Missing Dose request reasons are missing from the Reason drop down\n box on the BCMA Missing Dose form.\n6. Remove the obsolete Scratch HFS Directory from the BCMA Parameters GUI.\n \n7. The units ordered do not display on the BCMA Medication Log report\n when a missing dose is requested and the order is held and then given.\nThis enhancement is intended to enable the BCMA application to recognize\nwhether it is operating in the Indian Health Service (IHS) or Veterans\nHealth Administration (VHA) environment, and respond by recognizing and\ndisplaying the patient identifier appropriate to the environment.\n\n
\nThis Patch Addresses 3 issues:\nScheduled administration time of tomorrow, the BCMA MAH shows\na medication as scheduled to be given today.\n \n1. PSPO #1648 - The BCMA Medication Administration History Report \n(MAH) does not line up the action taken on a medication with the \nscheduled time of that administration.\n2. The BCMA MAH displays active medications on hold when an order is \nplaced on Provider Hold, an additional action is taken in Inpatient Meds,\nand then the order taken off provider hold.\n3. When an order is created with a start date of today and a first\n\n
\nThis Patch Addresses 2 issues:\n2. A schedule with a frequency of greater than 1440 minutes \n(24 hours) and a start date after today does not display as a Future\nOrder on the BCMA Due List Report. \n \n1. When a user logs into BCMA and their device time is exactly \nmidnight, VistA will add the value of $H to the current time to \nget the BCMA server time. This server time will be greater than \nthe highest allowable Fileman date, which is October 15, 2114. \nIf the BCMA Due List Report is run with the invalid default server \ntime, an infinite loop will be creating, eventually causing a "Disk Full"\nerror.\n\n
\nThis Patch Addresses 3 issues:\ntime.\n \n1. The error "<SUBSCRIPT>ADM+3^PSBCSUTX" occurs\nwhen selecting the BCMA Coversheet tab if the patient\nonly has an IV Order and no Unit Dose Orders.\n2. The BCMA Medication Variance Report does not paginate\ncorrectly.\n3. The BCMA Medication Variance Report displays a variance\nwhen a patch is removed, even if the patch was given on\n\n
\nThis Patch Addresses 3 issues:\n indicate what is causing the error.\n \n1. An error occurs when running the BCMA Unable to Scan Detailed \n report, causing BCMA to shut down.\n2. The Missed Medications Report is displaying invalid Start and\n Stop Date and Date/Times for One Time orders.\n3. The Missed Medications Report is displaying an invalid comment and\n status for a given medication.\n4. The BCMA "Filing Transaction MEDPASS" error message does not \n\n
\nATTENTION: This patch includes a new Graphical User Interface (GUI) \nRequest Analysis (IMR SFG IRA) Phase III/Phase IV, as well as \nmodifications requested by the BCMA and Inpatient Medications \nworkgroups. The Inpatient Pharmacy patch PSJ*5*153 is also being \nreleased as part of these enhancements. \n \n1. In order to allow facilities to select a timeframe that better matches\n their site policies, the site parameter that sets the amount of time\n that nurses have to document the PRN Effectiveness assessment is being\n expanded from 240 to 960 minutes.\n \nexecutable file. Installation of this GUI is required immediately after \n2. A new site parameter was added to the PARAMETERS file (#8989.5) & \n PARAMETERS DEFINTION file (#8989.51) to allow sites to prohibit \n administration of non-nurse verified medication orders, or to display a\n warning before administering non-nurse verified medication orders. \n Facilities will be able to set this option by division. \n \n3. The Missed Medications report will now include a "Verified" column that\n will contain the initials of the nurse who verified the order, or three\n asterisks, indicating that the order was not nurse verified.\n \nthe KIDS install for the Patch to function.\n4. A visual indicator will be displayed on the BCMA Virtual Due List (VDL)\n which will reflect whether an order has provider override reasons\n associated with the order. \n \n5. If the override information exists for an order, it will also be\n displayed on the order detail report.\n \nFor retrieval and installation instructions, please see the Client\nInstallation Instructions section.\n \nThe Allergy and Alerts Project addresses enhancements identified during \nInpatient Medications Requirementxs for Special Focus Group Initial \n\n
\nThis Patch Addresses 4 issues:\nthe BCMA Medication Log forms omit the leading zero if the Units\nGiven field value is a decimal less than one.\n4. PSPO #2015 - BCMA is accepting "Spacebar" as a valid\ninput for scanning a Drug IEN and returning the last\nmedication the BCMA User Scanned.\n \n1. The PSB BAG DETAIL RPC is returning duplicate entries for\na single action, causing the action to be displayed twice in\nthe Details section of the BCMA IV Tab.\n2. The message "Error @ -100" is seen in Details section \non the BCMA IV Tab if a site has the optional AU05 cross \nreference turned on.\n3. The Units Given fields on the PRN Effectiveness Log and \n\n
\n \n1. Enhancement: Read Only Bar Code Medication Administration (BCMA).\n This patch deploys the BCMA-HSC project "Read Only BCMA"\n functionality. After the installation of this build (PSB*3.0*4)\n and installation of the released Read Only BCMA GUI executable\n file, users allocated the "PSB READ ONLY" security key will be\n granted documented Read Only BCMA functionality. Also, as\n documented, users allocated the "PSB STUDENT" security key using\n BCMA while no BCMA instructor is using BCMA, will be granted Read\n Only BCMA functionality until a BCMA Instructor has accessed BCMA.\n \n*** ATTENTION: This patch includes a new Graphical User Interface (GUI) \n \n2. Enhancement: Patient Record Flag Reporting.\n This patch provides "Patient Record Flag" reporting functionality.\n During patient selection, information about any active Patient\n Record Flag(s) associated with the selected patient will be\n presented to the user. This patch also give the user the ability\n to display and print details of all active Patient Record Flags.\n This patch will also display a "FLAG" button via the patient's GUI\n Virtual Due List. This "FLAG" button gives the user access to a\n report of the all the active Patient Record Flags associated with\n executable file. Installation of this GUI is required immediately \n the patient.\n after the KIDS install for the Patch to function. *** \n \nFor retrieval and installation instructions, please see the Client\nInstallation Instructions section.\n \n \n\n
\nThis patch addresses the following issues:\n displayed on the BCBU MAR report. PSPO# 1613\n \n3. A prompt and help message in VistA under the BCMA Backup System \n [PSB BCBU WRKSTN MAIN] option is currently not displaying properly\n or consistently among the following three BCBU MAR print options \n Print MAR for All Wards, Print MAR for Selected Patient, and Print MAR \n for Selected Ward.\n \n4. While using Room/Bed sort in the BCMA Backup System (Wrkstn) option \n Print MAR for Selected Ward, the system produces an error if a patient\n1. Future medication orders display on the Bar Code Medication\n has no Room or Bed assigned.\n Administration Backup System (BCBU) Medication Administration Record \n (MAR) as current. An asterisk should be displaying in the\n administration time fields until the actual start dates have\n been reached. \n \n2. Held medications are currently being displayed on the BCBU MAR option \n Print MAR for a Selected Patient. Held medications should not be\n\n
\nThis Patch Addresses 3 issues:\n \n3. The BCMA MAH displays all meds as not due until the day after\nthe start date.\n \n1. PSPO 2134 - A Given dose does not display on the BCMA \nMedication Administration History (MAH) report when another dose is\ngiven for the same Administration time on the wrong day.\n \n2. A given dose of an IVPB will not display on the BCMA MAH report\nif the time given is edited to a time prior to the original given time\nof the medication.\n\n
\nThis Patch Addresses 2 issues:\n \n1. The BCMA Missed Medications Report may be inconsistent\n when run for a whole day versus incremental times if\n the order's Administration Times are edited.\n2. The Initials of the Nurse who marked an IV Bag infusing\n do not display in the Legend of the BCMA IV Overview\n Coversheet report when a different Nurse marks the bag\n Stopped or Completed.\n\n
\n*************************************************************************\nATTENTION: This patch includes a new Graphical User Interface (GUI) \nexecutable file. Installation of this GUI is required immediately after \nthe KIDS install for the Patch to function.\n \nThis version of BCMA was successfully tested in the field against Wireless\nMedication Administration version 4.8 at Pittsburgh and Loma Linda.\n \nFor retrieval and installation instructions, please see the Client\nInstallation Instructions section.\n \n IMPORTANT: PATCH PSJ*5*267 MUST BE INSTALLED BEFORE THE INSTALLATION \nThe Special Instructions and Other Print Info Project addresses \nenhancements identified during Inpatient Medications Requirements for \nSpecial Focus Group Initial Request Analysis (IMR SFG IRA) Phase \nIII/Phase IV, as well as modifications requested by the Bar Code\nMedication Administration (BCMA) and Inpatient Medications workgroups. \n \nThe Inpatient Pharmacy patch PSJ*5*267 is also being released as part of\nthese enhancements. The projects purpose is to Standardize the character\nlength between CPRS Provider's Comment, Inpatient Medications Special\nInstructions, and the IV Pharmacy Other Print Information fields.\n OF THIS PATCH.\n \nThe Inpatient Pharmacy patch PSJ*5*267 will add new fields to Inpatient \nMedication to support an unlimited amount of text for Special \nInstructions and Other Print Info (SI/OPI). \n \n1. BCMA Remote Procedure Calls (RPC) will be modified to send over the new\n Inpatient Medications SI/OPI fields in an unlimited format to the BCMA\n GUI client.\n \n2. For backwards compatibility, of existing Active orders on file that\n \n were using the old fixed length SI/OPI fields, then this information \n will be included in the new unlimited format also.\n \n3. Modify the following reports to print the unlimited SI/OPI information:\n a. Medication Administration History (MAH) Report\n b. Display Order detail Report\n c. Due List Report\n d. IV Bag Status Report\n e. Cover Sheet Report - Medication Overview Report\n f. Cover Sheet Report - PRN Overview Report\n BCMA patch PSB*3*68 contains changes that will not function until patch \n g. Cover Sheet Report - IV Overview Report\n h. Cover Sheet Report - Expired/DC'd/Expiring Report\n i. BCMA Backup System (BCBU) Print MAR for All Wards\n j. BCMA Backup System (BCBU) Print MAR for Selected Patient\n k. BCMA Backup System (BCBU) Print MAR for Selected Ward\n \n4. Add new check box field to allow if the unlimited text will be printed\n on the following reports:\n a. Due List Report\n b. IV Bag Status Report\n PSJ*5*267 is installed. Both patches, PSJ*5*267 and PSB*3*68 need to be\n c. Cover Sheet Report - Medication Overview Report\n d. Cover Sheet Report - PRN Overview Report\n e. Cover Sheet Report - IV Overview Report\n f. Cover Sheet Report - Expired/DC'd/Expiring Report\n \n5. BCMA Client:\n a. Added window to display unlimited Special Instructions / Other\n Print Info via menu, right-click, and function key (F6). This\n window is also used to display Special Instructions / Other Print\n Info when an order is flagged in Inpatient Medications and is given\n installed for Inpatient Medications and BCMA to function correctly.\n in BCMA.\n b. Fields which displayed Special Instructions / Other Print Info in\n forms were widened to 80 characters and have vertical scroll.\n c. Added Last Injections Site column to the Unit Dose VDL to show the \n what the last site was per Orderable item.\n d. Enhanced the Injection Site dialog window to show two \n history tables.\n 1) To show the last 4 sites per the medication being given.\n 2) To show last 10 sites per the patient for any medication.\n The tables above will use a new Division parameter, "Injection Site \n*************************************************************************\n History Max Hours", added with this patch that controls how many\n hours to look back when compiling these history tables. The default\n will be initialized to 72 hours, with this patch.\n \nThis Patch also Addresses 3 reported Remedy ticket issues:\n \n1. After scanning a medication that requires multiple doses\n or dosage strengths, the multiple dose dialog box's \n invalid medication pop-up functionality appears to be broken.\n2. Unable to view all allergies/ADRs on BCMA GUI for patient with\n \n numerous allergies/ADRs.\n3. The Patient Record Flag changes from Red to Black if you lock\n your computer. \n \nPlease refer to the release notes for a full detailed list and examples \nof items included in this patch.\n\n
\n***********************************************************************\nThe Special Instructions and Other Print Info Project addresses \nenhancements identified during Inpatient Medications Requirements for \nSpecial Focus Group Initial Request Analysis (IMR SFG IRA) Phase \nIII/Phase IV, as well as modifications requested by the Bar Code\nMedication Administration (BCMA) and Inpatient Medications workgroups. \n \nThe Inpatient Pharmacy patch PSJ*5*267 is also being released as part of\nthese enhancements. The projects purpose is to Standardize the character\nlength between CPRS Provider's Comment, Inpatient Medications Special\nInstructions, and the IV Pharmacy Other Print Information fields.\nIMPORTANT: PATCH PSJ*5*267 MUST BE INSTALLED IMMEDIATELY BEFORE\n \nThe Inpatient Pharmacy patch PSJ*5*267 will add new fields to Inpatient \nMedication to support an unlimited amount of text for Special \nInstructions and Other Print Info (SI/OPI).\n \nThe enhacnement in this patch will support the new unlimited lines of \ntext that will now be sent by Inpatient Medications to the BCMA\nContingency software workstations, in the HL7 NTE|21 segement.\n \nPlease refer to the release notes for a full detailed list and examples \nINSTALLATION OF THIS PATCH.\nof items included in this patch.\n \n If the site is running the BCMA Contingency software then this patch\n must also be installed on the workstations. Once installed it is \n suggested that the sites review the Contingency system MAR reports.\n***********************************************************************\n \n\n
\n This Patch Addresses 2 issues:\n \n1. PSPO 2012 - IV Bag Parameters are not defined for an Institution\n which contains active wards.\n \n2. After Multiple edits of solutions, invalid IV bags in BCMA may be\n administered.\n\n
\nThis Patch Addresses 3 issues:\n day of the week schedule.\n \n1. An order with an Unknown Action status is unavailable\n when using the Edit Med Log option if another user runs\n the BCMA Medication Administration History (MAH) report.\n2. A fatal error occurs when using the Unable to Scan function\n in BCMA and then scanning another medication. \n3. A fatal error occurs when clicking on the BCMA Coversheet if \n a patient's only current order is an IV Piggyback which has a \n\n
\nThis Patch Addresses 3 issues:\n \n1. A broker error occurs when attempting to open BCMA (Bar Code\n Medication Administration) for a patient who has and Intravenous\n Piggyback (IVPB) medication with an unknown Action Status. \n2. The header on several reports do not delineate a patient's room\n number with a colon.\n3. The BCMA Missed Medications Report does not contain meds that\n are held or refused when run in VistA.\n\n
\nThis Patch Addresses 2 issues:\n the BCMA UNABLE TO SCAN LOG (#53.77) file is greater than 40\n characters.\n \n1. An Undefined error occurs at LINE+13^PSBOML when the \n BCMA Med Log report is run and finds a BCMA MED LOG \n (#53.79) entry without a corresponding PHARMACY PATIENT (#55)\n entry.\n2. When giving an IV via the Unable to Scan feature, the user will\n receive a "Incomplete Data Returned from Vista" pop up box if the\n data attempting to be stored in the ORDERABLE ITEM (#15) field of\n\n
\n Please see the National Patch Module for details of the changes\n included in this patch.\n\n
\n \n appropriate.\n \n \n 2. Problem: NOIS MIW-0504-40557\n Scheduled administration times are reported and totaled on the\n Ward Administration Times Report per each clock hour. If an\n order s stop time is between clock hours, that order s final\n scheduled administration is neither reported nor added to the\n report totals.\n \n 1. Problem: NOIS CTX-0804-70321\n Corrective Action:\n The BCMA Ward Administration Times Report will report and\n total all appropriate scheduled administration times. \n \n \n 3. Problem: NOIS LIT-0704-71393\n The initial administration of an order which displays on the BCMA\n Graphical User Interface (GUI) Intravenous/Piggyback (IVPB) Tab \n may result with an administration status of "GIVEN", "HELD", or\n "REFUSED". When this same order is administered via the VISTA \n Large volume IV orders do not show on the Due List Report. The\n Manual Medication Entry [PSB MED LOG NEW ENTRY] option, the \n initial administration status can only be "GIVEN".\n \n Corrective Action:\n The Manual Medication Entry [PSB MED LOG NEW ENTRY] option will\n allow the initial administration of an IVPB order to result in\n an administration status of "GIVEN", "HELD", or "REFUSED".\n \n \n 4. Problem: NOIS UNY-0304-10606\n Bar Code Medication Administration (BCMA) Due List Report does\n When the user prints a Medication Administration History (MAH)\n report with a date range exceeding seven (7) days, Pro Re Nata\n (PRN) order activity, which occurred that last day of the\n report s date range, does not display.\n \n Corrective Action:\n PRN activity occurring within the selected MAH report date range\n will display on that MAH report.\n \n \n not display information for large volume IV orders that have\n 5. Problem:\n When creating a MAH report, the administration times of orders\n that have start time between the report's date range do not\n display properly.\n \n Corrective Action:\n The MAH report will display order administration times properly.\n \n \n 6. Problem: NOIS ISB-0105-30190\n been created on the date selected for reporting. \n When using the GUI Edit Med Log to add a comment for an \n administration having units given less than 1.0, the message - "When \n changing the admin status to Given, at least one dispensed drug must \n have a units given ..." - is displayed and the comment is not filed.\n This error is due to the value in the Units Given field of the GUI\n Edit Med Log being presented without the "leading zero" when the \n value is less than 1.0.\n \n Corrective Action:\n When the Units Given value of an administration is less than zero, \n \n it will be presented via the GUI Edit Med Log with the leading zero.\n \n \n 7. Problem: NOIS ISB-1104-31950\n The Medication History Report does not display a leading zero in\n its "Units GIVEN" data field when display a numerical fraction.\n \n Corrective Action:\n A leading zero will display in the Medication History Report,\n "Units GIVEN" data field when appropriate.\n Corrective Action:\n \n \n 8. Problem: NOIS BUT-1204-21117\n There are instances when the "Units Of Administration" data field\n of the Medication History Report does not "break" and remain legible.\n \n Corrective Action:\n The "Units Of Administration" data field of the Medication History\n Report will "break" and maintain whole words and legibility.\n \n The BCMA Due List Report will display large volume IV data when\n \n 9. Problem: NOIS UNY-0105-11034\n The heading for the Due List Report, "Future Orders" section is \n displayed and is not followed by "Future Order" data when at least\n one future active order exists, and no future order has a scheduled \n administration within the selected report time parameters. \n \n Corrective Action:\n The heading for the Due List Report, "Future Orders" section will not\n display, unless "Future Order" data is to be displayed.\n\n
\nClinic Order and Witness for High Risk / High Alert drugs.\n\n
\nThis Patch Addresses 2 issues.\n in the PHARMACY PATIENT IV subfile (#55.01) cannot be marked\n as given using the Manual Medication Entry [PSB MED LOG NEW ENTRY] \n option.\n \n1. When the INFUSION RATE field (#.08) in the PHARMACY PATIENT IV subfile\n (#55.01) is greater than 27 characters (30 character max) for an \n Intravenous Piggyback (IVPB) order, the text added by the software \n will cause the infusion rate to exceed the 47 character maximum\n in BCMA.\n \n2. An IVPB order with a SCHEDULE (#.09) and a STATUS (#100) of "On Call" \n\n
\nIMR6 CLINIC ORDER ENHANCEMENT FOR BCBU\n\n
\nThis Patch Addresses 2 issues:\nprinted by ward.\n \n1. An order will not display on the Bar Code Medication\nAdministration (BCMA) Virtual Due List (VDL) properly \nif the order has its first administration time not on the\nhour and the start date and time are not exactly on the hour.\n \n2. The BCMA PRN Effectiveness Report and Medication\nVariance Report do not display the ward name when\n\n
\nThis Patch Addresses 6 issues:\nHistory (MAH) report.\n4. The undefined error <UNDEFINED>FILEIT+10^PSBML *PSBHDR occurs\nwhen logging into BCMA.\n5. Immunizations given as Clinic orders in BCMA are not recorded in the \nV IMMUNIZATIONS (#9000010.11) file.\n6. BCMA accepts a partial scan of a patient's SSN when scanning a \npatient's wristband.\n \n1. The Bar Code Medication Administration (BCMA) Missed Medications\nreport does not include orders with a status of "Renewed" \n2. BCMA incorrectly rounds a patient's height down on the BCMA Virtual\nDue List (VDL) and on report headers, and incorrectly calculates a \npatient's weight on report headers.\n3. Orders with a start time exactly the same as the last administration\ntime will display as not due in the BCMA Medication Administration \n\n
\nThis Patch Addresses 5 issues:\nof Last 4 digits of a patient's Social Security Number (SSN) as the \npatient identifier.\n4. A dangling "AADT" index causes an undefined error to occur when\na site runs the BCMA Extract (ECXBCM) option. \n5. The Meds on Patient section of the BCMA Virtual Due List (VDL) \ndisplays an Intravenous (IV) bag as infusing after it has been marked\ncompleted if the Action Date/Time was edited using the Edit Med Log\noption.\n \n1. The Bar Code Medication Administration (BCMA) Medication History\nreport displays data prior to the report start date when run in the\nComputerized Records System (CPRS) application. \n2. BCMA Labels for Unit dose drugs are missing the Indian Health \nServices (HIS) Health Record Number (HRN) in place of Last 4 digits of a\npatient's Social Security Number (SSN) as the patient Identifier.\n3. The BCMA Unknown Actions Report does not display IHS HRN in place\n\n
\nThis Patch Addresses 7 issues:\n3. The BCMA Medication Log and Medication Variance report headers\ndo not display the time frame of the report.\n4. The BCMA AUDIT LOG (#53.799) sub-file does not include an entry \nfor Pro Re Nada (PRN) Effectiveness when a PRN is "Un-Given"\n5. The Legend of the Medication Therapy report does not include users\nwho entered comments for an order.\n6. The 2nd line of routine PSBOPE has an invalid format.\n7. Update the unsupported $$UCASE^XUSG Application Programming \nInterface (API) to the supported API $$UP^XLFSTR in routine PSBMLLKU.\n \n1. The Medication History report in Bar Code Medication \nAdministration (BCMA) displays amounts in the Units Given\nfield for an order that has not been given. \n2. When a user makes a change to an order using the Edit Med Log\noption which does not change the action status, several reports \ndisplay the initials of the person who edited the order instead of\nwho created the action on the order.\n\n
\nThis Patch Addresses 6 issues:\na different division. \n4. The BCMA Administration Times report does not display historical\ndata when run by ward.\n5. The BCMA Clinical Reminders tab does not display that a PRN \nEffectiveness is needed when the PRN is given on the same day as the \npatient is admitted.\n6. The Unable to Scan detailed report does not display the full Health \nRecord Number (HRN) for Indian Health Services (IHS) sites.\n \n1. The Bar Code Medication Administration (BCMA) MEDICATION\nVARIANCE LOG (#53.78) file does not save data in DRUG SCANNED\n(#.07) field.\n2. BCMA stores the initials of the user who viewed the patient's record\ninstead of the initials of the user who marked a Vital Entered in Error.\n3. The BCMA Unable to Scan Detailed report does not display any data\nwhen run for a Nursing Ward if the user running the report is logged into \n\n
\nThis Patch Addresses 7 issues:\n Record System (CPRS) application when converting weight from pounds\n to kilograms.\n4. BCMA report headers display the diagnosis for a patient's last\n admission after the patient has been discharged. \n5. The BCMA Coversheet is loading slowly for long term care patients.\n6. The Unit Dose tab of the BCMA VDL loads slowly for long term care\n patients.\n7. The BCMA Medication Variance report displays the medication name twice\n under the medication field of the report\n \n1. An Undefined error occurs at SCANPT+49^PSBRPC if an accent (`) mark is\n passed in when manually keying in a patient's wristband.\n2. Bar Code Medication Administration (BCMA) report headers display the\n last ward and room/bed the patient was admitted to after they are \n discharged.\n3. BCMA report headers and the BCMA Virtual Due List (VDL) round a\n patient's weight to less significant digits than the Computerized \n\n
\nSee patch description for details.\n\n
\nNo warning for early, late or second ward stock IVPB\n\n
\n******************************* ATTENTION ********************************\n3. PSB*3*83\n \n12. BCMA Due List report now includes Remove Times on the report below \n the admin times that are due per Medication.\n \n13. BCMA Coversheet Medication Overview report and the Coversheet \n Expired/DC'd/Expiring Orders report will now include Missed-Removals \n and Removals on the reports.\n \n14. BCMA Medication Log report changed the heading from "Inj Site" to \n "Body Site". The Medication detail body text will display the proper\n4. OR*3*417\n label of "Inj Site:" or "Derm Site:" just prior to the name of the\n Body site for that medication.\n \n15. BCMA Medication History Heading line changed from "Injection Site" to\n "Body Site".\n \n16. A body site diagram will be added to the BCMA Parameter GUI client \n application for the purpose of showing a dot on the body diagram that\n is associated with the Text representation of that site location on\n the body.\n5. PSB*3*87\n \n17. The BCMA Parameter GUI client application has access to a new kernel \n parameter titled in GUI application as "Dermal Site History Max\n Days:". This allows the BCMA coordinator the ability to control how\n many days of prior dermal body site location history will appear, when\n a clinician is giving a new dermal medication that is prompting for a\n body site location.\n \n18. The Orders for MRRs With Removal Properties [PSS MRR ORDERS DIAGNOSTIC\n RPT] option found on the Pharmacy Data Management [PSS MGR] menu, \n \n will also be placed on the Bar Code Medication Administration Manager\n [PSB MGR] menu.\n \n \n*NOTE* Non-standard schedules such as DAY@HHMM, HHMM, or other Odd \n schedules, are not capable of calculating removal times due to a\n lack of a Frequency. Regardless of the Prompt for Removal in BCMA\n code value they will not prompt for removal in BCMA and should be\n avoided.\nATTENTION: This enhancement also includes a new Graphical User Interface\n(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is\nrequired immediately after the KIDS install for the Patch to function.\n \nFor retrieval and installation instructions, please see the Client \nInstallation Instructions section.\n \n**************************************************************************\n \nThe Clinical Ancillary Services Development-Delivery of Pharmacy \nEnhancements (CAS DDPE) project addresses several NSR's, which center \naround providing a means for properly handling Transdermal Medications \nRequiring Removal (MRR) beyond the current medications of dosage form \nPatch. These enhancements interface with Inpatient Pharmacy package, \nwhich will be storing Scheduled Removal Times, for inpatient orders that \nare designated as MRR type medications. See associated patches PSS*1*191 \nand PSJ*5*315, for details on how MRR medications are designated.\nClinical Ancillary Services (CAS) Development-Delivery of Pharmacy \n \nThis BCMA enhancement also includes a new Graphical User Interface (GUI) \nexecutable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is required \nimmediately after the KIDS install for the Patch to function.\n \nFeatures of the BCMA GUI provided by this project are listed below.\n \n 1. Change the current GUI Unit Dose tab column labeled "Admin Time" to \n "Next Dose Action".\n \nEnhancements (DDPE) VA Inpatient Medication Administration - Transdermal\n 2. The "Next Dose Action" column will now contain both the next admin\n times for scheduled administrations as well as the next Removal time\n for MRR type medications. The initial login to BCMA, will sort the\n Unit Dose tab in ascending order by this column, so older actions for\n medications will be at the top of the VDL display.\n \n a. The Next Action of an administration will contain the word "DUE"\n followed by the scheduled admin time in the standard date@admin\n time format currently in use.\n b. The Next Action of a removal will contain the word "REMOVE"\nenhancement includes 5 patches which must be installed in the following\n followed by the scheduled removal time in the standard\n date@time format.\n c. The Next Action of an administration that is past due to be\n given will contain the word "LATE" followed by the scheduled\n admin time in the standard date@admin time format currently in\n use. \n d. The Next Action of a removal that is past due to be removed will\n contain the word "LATE-RM" followed by the scheduled removal time\n in the standard date@time format.\n \norder:\n 3. Change the current GUI column labeled "Wit" to "Alert".\n \n 4. The Alert column will still have the ability to display the Witness \n required icon and will also be able to display a new Remove icon. \n a. The icon is displayed only for MRR type meds that were Given and\n their next Action is for Removal.\n \n 5. Early/Late warnings will also be associated with medications being \n removed early or late using the same early late time range that is\n used for early or late medication admins.\n \n a. User comments are prompted for and stored upon continuing with\n the Early/Late removal action.\n \n 6. Variances will also be tracked for Early/Late Removals in the same \n manner as they are currently for Early/Late medication\n administrations and will appear on the Medication Variance Log report.\n \n 7. BCMA Medication Administration History (MAH) report will now print\n the associated Give, which was previously overwritten by the Remove\n action, chronologically after the Remove for the Print by Patient \n1. PSS*1*191\n report. The print by Ward report will now include the count of\n Removals scheduled for the report time period.\n \n 8. BMCA Medication Log will now show the historical Give date/time below \n the current status of the medication, which shows the Remove\n date/time.\n \n 9. BCMA Missed Medications report will also show Removals that were\n missed or up and coming, similar to how missed Gives are currently\n notated. The column Heading has been changed from "Admin Date/Time"\n2. PSJ*5*315\n to "Missed Date/Time".\n \n10. BCMA Display Order report now includes the Removal Times for this\n order directly below the current Admin Times.\n \n11. BCMA Medication History report now includes a prior Give line item\n directly below the current status line item of Remove (RM). The Remove\n last action on this administration overwrites the Give information and\n was no longer printing on this report. This information is now being\n retrieved from the Audit log and printed on this report.\n\n
\n******************************* ATTENTION ********************************\n5. PSB*3*87\n \nATTENTION: This enhancement also includes a new Graphical User Interface\n(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is\nrequired immediately after the KIDS install for the Patch to function.\n \nFor retrieval and installation instructions, please see the Client \nInstallation Instructions section.\n**************************************************************************\n \n \nPSB*3*87 will enhance the BAR CODE MEDICATION ADMINISTRATION (BCMA) Backup\nSystem (BCBU) to support Medications Requiring Removal (MRR). The Backup\nSystem will be able to store the Removal times and duration of\nadministration associated with each medication order.\n \nThis patch will add two new fields to the ORDER NUMBER (#53.702) \nsub-file under the BCMA BACKUP DATA (#53.7) file. The two new fields \nare the REMOVE TIMING (#7.4) field and DURATION OF ADMINISTRATION (#7.5) \nfield. These fields implement changes that will support enhancements to \nMedical Administration Record(s) MAR reports in the BCBU application.\nCASDDPE VA Inpatient Medication Administration - Transdermal enhancement\n \nThe MAR reports will print each Scheduled Removal times for MRR \nmedications in the Grid in the same manner as Admin times. The Remove\ntimes will appear below the current scheduled Administration time in the\nGrid and will be separated by the Label "Remove" in the times column. \nAsterisks will print in the body of the Grid in each Removal action box\nfor removal times that are not valid per the Date in that column heading.\n \nThe MAR reports will also no longer display the Order number of the\nmedications being administered.\nincludes 5 patches which must be installed in the following order:\n \nPlease refer to the BCMA Backup System (BCBU) Installation Guide for \nPSB*3*87 for installation details.\n \n1. PSS*1*191\n2. PSJ*5*315\n3. PSB*3*83\n4. OR*3*417\n\n
\nThis patch will resolve the following issues:\n3. The BCMA Drug IEN Synonym Check [PSB DRUG IEN CHECK] option needs to\n be added to the Medication Administration Menu Pharmacy [PSB PHARMACY]\n menu.\n \n4. The IV Bag Detail on the IV tab does not display for a patient when \n opening the patient's Virtual Due List (VDL) after having another \n patient's VDL open.\n \n1. The Bar code Medication Administration (BCMA) Due List Report does not\n display Intravenous Piggy Back (IVPB) orders with an Inpatient \n Pharmacy Status of "On Call".\n \n2. The Missed Medication Report shows missed administrations prior to an \n edit when an order's Administration time are edited.\n \n\n
\nFix for eHMP defect 4250. Places SEQUENCE values on ITEMs in the \nPROTOCOL file (#101).\n\n
\nPatch PSB*3*97 will change the version number of the Bar Code \nSome reports that print Legends had some issues where the user name and\ninitials were inaccurate for transdermal type medications.\nMedication Administration (BCMA) client application to version 97\nfrom version 83 to correct an issue discovered immediately after release\nof version 83. \n \nA hard error can occur in the BCMA client application with a new button\nprovided that displays a Body Site Image for selecting body location of\ntransdermal type medications.\n \n\n
\nThis patch will resolve the following issues:\n \n3. Medications cannot be administered in BCMA after Nurse's initials \n deleted.\n \n4. Medications Orders requiring removal with a schedule type of "One-Time"\n and Frequency greater than zero do not display the correct removal\n time in the "Next Dose Action" field on the BCMA VDL.\n \n1. The Bar Code Medication Administration (BCMA) Order Mode indicator\n light is not displaying when the only active orders have a pharmacy\n status of renewed, on call, or provider hold.\n \n2. The BCMA Active Order Indicator light is not displaying for the Unit \n Dose tab when the only active orders have a Pharmacy Status of Renewed\n or Provider Hold.\n\n
\nThis patch will resolve the following issues:\n \n3. The BCMA Display Order report displays dates in the data field in \n internal Fileman format.\n \n4. An Undefined error occurs when the Medication Therapy report is run \n with no schedule types selected.\n \n1. The Bar Code Medication Administration (BCMA) IVP/IVPB tab continues\n to display orders with a Schedule Type of On Call after the order is \n administered.\n \n2. The BCMA Display Order report displays both BCMA EXPIRED and BCMA\n EXPIRE DENIED in the data field of the Pharmacy Activity section when a\n one time dose medication is administered.\n\n
\nThis patch will resolve the following issues:\nthen\n \n Resolution:\n -----------\n Routine PSBML2 was modified to store the correct medication dosages\n in the DISPENSE DRUG (#53.795) sub-file when the edited order is\n administered. \n \n4. R12817870FY17 - PRN requiring effective is not showing on BCMA Clinical\n Reminders\n \n infusing, the medication log shows each ingredient of the infusing IV \n Problem:\n --------\n A PRN medication requiring a PRN Effectiveness does not display on the\n BCMA Clinical Reminders if the patient is discharged and re-admitted.\n \n Resolution:\n -----------\n Routine PSBPRN was modified to display the order under the BCMA \nClinical \n Reminders when the patient is discharged and re-admitted, as long as \nOrder\nthe\n order falls within the PRN Documentation parameter.\n \n5. I10114492FY16 - Mark Documenting Backlog PRNs option OOO\n \n Problem:\n --------\n The unsupported Documenting Backlog PRNs [PSB PRN DOCUMENTING] option\n needs to be marked out of order and removed from the Bar Code \nMedication\n to have units of zero.\n Administration Manager [PSB MGR] menu option. This option runs a \nversion\n 2 routine in BCMA (currently on version 3), and should not be active\n on a nationally released menu option.\n \n Resolution:\n -----------\n Post Install routine PSB399P will mark the Documenting Backlog PRNs\n option [PSB PRN DOCUMENTING] "out of order" and remove the option\n from the Bar Code Medication Administration Manager [PSB MGR] menu.\n \n \n \n6. I6216135FY16 - <UNDEFINED>RESETADM+7^PSBUTL error in BCMA\n \n Problem:\n --------\n An error occurs the first time an order is administered in BCMA.\n \n Resolution:\n -----------\n3. When a multiple dose medication has been edited prior to \n Routine PSBUTL was modified to properly record the first BCMA \n medication administration.\n \n \n7. I10181534FY16 - Extra Data populated when pulling by Ward\n \n Problem:\n --------\n A BCMA user was attempting to pull data by ward. When data populated\n it listed patients that are not associated with the ward selected.\nadministration,\n \n The problem happened because the ward searched had a name that the \nfirst\n characters were similar to a date (e.g., 8-8, 10-11, etc.). The \nroutine \n PSBMLLKU (line tag PTLKUP) used to perform a Fileman lookup using all\n cross-references in the PATIENT file (#2). This lookup approach \n sometimes produced wrong entries because it would match with a date \nfrom\n the "E" x-ref (CV DATED EDITED) because for example "8-8" would trigger\n it will display on the Missed Meds report after administration.\n a match a 08/08/17 (current year) causing such patients to be included\n in the lookup result.\n \n Resolution:\n -----------\n The code at the PTLKUP^PSBMLLKU was modified to only include the cross-\n references that are relevant to the patient lookup popup window (last \n name, first name, SSN, ward, room and bed).\n \n4. A PRN medication requiring a PRN Effectiveness does not display in the\n \n BCMA Clinical Reminders section if the patient is discharged and \n re-admitted.\n \n5. The unsupported Documenting Backlog PRNs [PSB PRN DOCUMENTING] option\n needs to be marked out of order, and removed from the Bar Code \nMedication\n Administration Manager [PSB MGR] menu option.\n \n6. An error occurs when a site new to BCMA attempts to create their first \n order.\n1. The Bar Code Medication Administration (BCMA) GUI does not store the\n \n7. The patient lookup window sometimes lists the wrong patient when users\n are doing a search by the ward name and the first part of the ward name\n matches with a valid date.\n \nASSOCIATED NSR(S):\n==================\nN/A\n \n \n initials of the 2nd user who witnesses a high risk/high alert \nASSOCIATED CA TICKET(S):\n============================\n1. I9892136FY16 - 2nd Witness Initials not stored\n2. I9842129FY16 - TPN shows 0 units for each ingredient - Med Log\n3. I9892810FY16 - False missed med when Inpatient Pharmacy edits\n dispense drug\n4. R12817870FY17 - PRN requiring effective is not showing on BCMA\n Clinical Reminders\n5. I10114492FY16 - Mark Documenting Backlog PRNs option OOO\n6. I6216135FY16 - <UNDEFINED>RESETADM+7^PSBUTL error in BCMA\ncontinuous\n7. I10181534FY16 - Extra Data populated when pulling by Ward\n \n \nPARTICIPATING TEST SITES:\n=========================\nTBD\n \n \nCA OVERVIEW:\n================\n intravenous (IV) order which has been marked stopped and then marked\n1. I9892136FY16 - 2nd Witness Initials not stored\n \n Problem:\n --------\n The second witness' information is not stored in the ADMIN WITNESSED BY\n (#.29) field of the BCMA MEDICATION LOG (#53.79) file when an IV bag\n with a high risk/high alert medication is marked stopped and then\n infusing again.\n \n Resolution:\n infusing again.\n -----------\n Routine PSBML2 was modified to remove the first witness' information\n and store the second's information in the ADMIN WITNESSED BY (#.29) \n field. The first user's information will be preserved in the AUDIT LOG\n sub-file (#53.799).\n \n2. I9842129FY16 - TPN shows 0 units for each ingredient - Med Log\n \n Problem:\n --------\n \n When a missing dose is requested for an IV order, then as held or \nrefused,\n and then infusing, the Medication History report shows each ingredient \nof \n the infusing IV Order to display units of zero. \n \n Resolution:\n -----------\n Routine PSBML2 was modified to store the correct units for each IV bag\n ingredient in the UNIT OF ADMINISTRATION (#.04) field of both the \n2. If an IV order is marked as a missing dose, then as held or refused, \n ADDITIVES (#53.796) and SOLUTIONS (#53.797) sub-files.\n \n3. I9892810FY16 - False missed med when Inpatient Pharmacy edits\n dispense drug\n \n Problem:\n --------\n A multiple dose medication will incorrectly display on the BCMA Missed\n Medications report when the dosage form of the order was edited after\n a missing dose request is made on the order.\n\n
\nThis patch will resolve the following issues.\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. I9592038FY16 - Frequently, BCMA users are not able to access the BCBU\n database\n \nProblem: \n--------\nFrequently, BCMA users are not able to access the BCBU database. This result\nin local IT support spending time to resolve what should be a minor issue.\n \nHowever, the fix is not always simple or straight forward. Typically, the\nproblem is that the user has had a Verify Code change since they last\naccessed a contingency. Normally, doing a User Initialization does not\nresolve the issue and IT support has to either replace the database or\nmanually give the user a new Verify code on the contingency computer.\n \nResolution:\n-----------\nModified the routines ALPBGEN, ALPBGEN1 and ALPBGEN2 to remove some\nunnecessary restrictions for sending a user update over to the BCBU\n1. I9592038FY16 - Frequently, BCMA users are not able to access the BCBU\nworkstation. For example, if a user was terminated in the main VistA System\nit would not be sent to the BCBU workstation. This caused terminated users\nin the main VistA System to remain active in the BCBU workstation.\n \n \n2. I8652828FY16 - Getting ALERT BCBU Contingency Error 46364090 / Missing HLL\n Links Array Med-Log\n \nProblem: \n--------\n database\nIn a multi-divisional BCBU configuration all Divisions are required to have\nan HL7 Logical Link associated. When a division is missing the association an\nalert is generated for every transaction that is supposed to go to the BCBU\nworkstation for that division. The problem is that the Alert does not identify\nwhich division is missing the Logical Link, which makes it hard for the users\nto identify the source of the problem and resolve it. Furthermore, the fact \nthat the Alert does not identify which patient was being processed when the \nissue happened makes it hard to troubleshoot and fix the problem as well.\n \nResolution:\n2. I8652828FY16 - Getting ALERT BCBU Contingency Error 46364090 / Missing HLL\n-----------\nModified the routine ALPBCBU to include the site number and the patient DFN\nnumber in the Alert subject. This way users will know exactly which division\nand the patient that was being processed when a BCBU Alert is generated due to\nan error. \n \nHere is how the Alert text will be modified:\n \n Before: BCBU Contingency Error\n Missing HLL Links Array Med-Log\n Links Array Med-Log\n \n After: BCBU Contingency Error / Site: 442 / DFN: 1930382\n Missing HLL Links Array Med-Log\n \n \n3. I6161931FY16 - Received the error $ZE= <UNDEFINED>ZPD+5^IVMPREC8 *HLFS\n I16851052FY18 - Undefined: GENACK+10^RGADTP *HL("MID") \n \nProblem: \n-------- \n3. I6161931FY16 - Received the error $ZE= <UNDEFINED>ZPD+5^IVMPREC8 *HLFS\nWhen an HL7 message is received from an Income Verification Match (IVM) Center\ncontaining demographics data for a patient that includes a date of death the\nBCBU application is automatically invoked if such patient has active inpatient\norders. Many other subscribing applications are automatically invoked by the \nsame process and they all share the same local variables from the invoking\nprocess. The routine ALPBINP was incorrectly killing HL7 local variables such\nas HL, HLA, HLCS, HLCTR and HLFS, which were being used by other applications\nand in these two specific incidents reported caused the Income Verification\nMatch (IVM) and Registration applications to error out.\n \n I16851052FY18 - Undefined: GENACK+10^RGADTP *HL("MID") \nResolution:\n-----------\nModified the routine ALPBCBU to NEW the variables HL, HLA, HLECH and HLQ and\nalso modified the routine ALPBINP to no longer kill the HL7 variables HLCS, \nHLCTR and HLFS.\n \nNOTE: This fix could not be tested in a development or an SQA environments\n because it requires an incoming HL7 message from an external entity.\n \n\n\n \n all administration and order processing has occurred and BCMA\n begins to free memory per MOB activity. Because a variable\n needed by BCMA MOB exit activities has been cleared, BCMA generates\n the "<UNDEFINED>MOBR+25^PSBAPIPM" before processing has completed.\n \n \n Corrective Action:\n PSB*3*15 will allow BCMA MOB exiting processing to complete\n without error.\n \n 1. Problem: HD000000088329\n The Medication Order Button (MOB) within the Graphical User\n Interface, Bar Code Medication Administration system (BCMA)\n malfunctions after the Installation of patch PSB*3*9. When the\n BCMA MOB is used to administer medications and create orders, \n all data is stored and maintained properly. The malfunction\n occurs when the post PSB*3*9, BCMA system frees memory after\n\n
\nThis patch will resolve the following issue.\n \nProblem: \n--------\nMilwaukee VAMC reported getting a RPC Broker Timeout error when running the\nBCMA Missed Medications Report for one specific ward (9C). The reason they\nwere getting this error is because Ward 9C has quite a few long term care\npatients and the report retrieves information for every single order with\nmedication that requires removal (e.g., patches) for all patients in that\nward before deciding whether the order should be in the report or not.\n \n \nResolution:\n-----------\nModified the routine PBUTL at the REMOVES line tag and moved the screening\nfilters up before the call to D PSJ1^PSBVT. This change will have no impact\nwhatsoever on the output of the report and it will considerably decrease the\namount of time it takes to run it.\n1. R16686630FY17 - Ward 9C keeps getting this error (Timeout) intermittently\n when trying to run the Missed Medications Report \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. R16686630FY17 - Ward 9C keeps getting this error (Timeout) intermittently\n when trying to run the Missed Medications Report \n\n
\nThis patch will resolve the following issues.\nProblem: \n--------\nIt was reported that almost all of the BCBU Contingency Error Alerts that\nDivisional sites receive continually are for patients who are not admitted\nor are deceased. Furthermore, testing of BCBU data for Clinic Orders reveals\nthat the patient records for clinics using BCMA are rarely complete causing\nthe menu options in BCBU to be placed OUT of ORDER to prevent medication\nerrors during contingency operations.\n \nResolution:\n \n-----------\nIt was identified that updates for BCMA Medication Logs for patients that are\nno longer inpatient fail to identify the correct division for which the HL7 \nmessage should be sent to. A fix was made to retrieve the correct Division\nusing the Institution in the Medication Log if the patient is no longer\ninpatient. In addition, the BCBU Contingeny Error Alerts will no longer be\ngenerated for patients that are deceased.\n1. R18279880FY18 - BCBU not consistently updating Clinic Orders\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. R18279880FY18 - Frequently, BCMA users are not able to access the BCBU\n database\n \n\n
\nThis patch will resolve the following issue.\n \nProblem: \n--------\nAn issue was discovered when loading the BCMA coversheet and the patient\nhas an order with an administration schedule that does not have a whole\nnumber of hour(s) frequency between administrations (e.g., 7 TIMEs A DAY,\nONCE EVERY 3.5 HOURS, etc.). The reason is because the program that\ncalculates the next dose's administration date/time assumed the frequency to\nbe a whole number of hours like 4 or 6 and not 3.1466 or 3.5. Since the\nprogram could not come up with a valid date/time it went into an infinite\n \nloop which would freeze the BCMA application when the users tried to view the\npatient's coversheet.\n \nResolution:\n-----------\nThe routine PSBCSUTX was modified at line tag NEXTADM+24 to take into account\nthat the frequency of a schedule does not necessarily produces a whole number\nof hours and it will calculate the next administration date/time for such\nfrequencies.\nR19023599FY18 - PSB GUI Context consuming a lot of CPU on Bay Pines VistA\n Front ends\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nR19023599FY18 - PSB GUI Context consuming a lot of CPU on Bay Pines VistA\n Front ends\n\n
\nThis patch provides multi-division sites the ability to run the report \n'Missing Dose Followup' by division. Single division sites are not \naffected by the changes in this patch.\n\n
\nThis patch will resolve the following issue.\n--------\nAn issue was discovered with the Barcode Medication Administration (BCMA) \nMissed Medications Report for 'odd' (non-standard) schedule orders, e.g.\nQ18H - ONCE EVERY 18 HOURS. When the report is run for a date range that\nstarts prior to the start date/time of such orders in some cases it will\nmistakenly include these orders in the report even if the order does not\nhave any missing dose for the date range selected for the report.\n \nResolution:\n-----------\n \nThe routine PSBOMM was modified at line tag EN1+49 to prevent it from\ncalculating a dose date/time that is prior to the order start date/time.\nINC0328665 - Issue with BCMA Missed Medications Report\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC0328665 - Issue with BCMA Missed Medications Report\n \nProblem: \n\n
\nThis patch will resolve the following issue.\nINC0962039 - WNY - Vista Not Updating BCBU orders when patients are\n discharged/deceased\nINC1002829 - BCBU patient census not updating\n(Duplicate)\n \nProblem: \n--------\nAn issue was discovered with the Barcode Medication Administration (BCMA) \nBackup System (BCBU) after the installation of patch PSB*3*105. After the\npatient is discharged or a date of death is entered for him/her the patient\n \ndata is not being properly removed from the BCBU workstation. In the case of\ndischarged patient that are later admitted or have a clinic appointment their\norders from their previous admission are still visible on the BCBU\nworkstation and are listed on the patient's Medication Administration Reports\n(MAR).\n \nResolution:\n-----------\nRemoved the filter introduced by PSB*3*110 to prevent alerts from being\ngenerated for patient movements if the patient is no longer inpatient. The\nINC0962039 - WNY - Vista Not Updating BCBU orders when patients are\nreason is because such filter prevented patient discharge events, which are\nhandled as patient movements, from removing he patient's data from the \nBCBU workstation. The filter was re-introduced at the Alert generation point\nand exclude patient discharge movements.\n \nTechnical Resolution:\n---------------------\nChanged the routine ALPBCBU to remove the filter from the PMOV line tag and\nplaced a check in the ERRLOG line tag to prevent Alerts for patient movement\nevents after the patient had already been discharged. \n discharged/deceased\nINC1002829 - BCBU patient census not updating\n(Duplicate)\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n
\nPatch PSB*3.0*111 corrects one issue in the report 'Missing Dose \nFollowup'. The issue reported by a single site at a multidivisional \nsetting is that after one record is selected for completion and is saved,\nit is not dropping off the list of available records. The expected\nbahavior is that after one record in the report is completed and saved, it\nshould no be part of the list.\n \nReference: INC1537335 - GLA - PBS*3*100 Patch Missing Dose Followup list \nis not updating after resolving the missing dose.\n\n
\nThis patch will resolve the following issue.\n \nProblem: \n--------\nBath VA Medical Center reported a problem with the BCMA Medication Admin\nHistory report for patch medication orders. For certain situations the report\nomits a patch given action if the same patch removal date falls outside the\ndate range selected to run the report. In the report example below run \non 08/30/2018, for the date range 08/27/18 thru 08/29/2018 the 'G0800' under\nthe 08/29/2018 column would not be displayed because the patch applied on\n08/29/2018 was already removed on 08/30/2018 and 08/30/2018 was not included\n \nin the report date range.\n \n=============================================================================\nLocation | | | | |\nStart Date Stop Date | Admin | | | |\nand Time and Time | Times | 08/27/2018 | 08/28/2018 | 08/29/2018|\n-----------------------------------------------------------------------------\nINPATIENT | | | | | \n08/25/2018 09/14/2018| 0800 | RM0755 | RM0755 | RM0755 |\n@07:00 @08:00 | | G0800 | G0800 | G0800 <-- | \nINC1697793 - BCMA med log and medication administration history reports\n | | | | |\nFENTANYL TRANSDERMAL PATCH | | | | |\n FENTANYL TRANSDERMAL | | | | |\n 50MCG/HR PATCH Give: ONE | | | | |\n(50MCG/HR) PATCH TOP MISC Q24H| | | | |\n | | | | |\n Removal Times: 0800 | | | | |\n RPH: RN: | | | | |\n Special Instructions:\n TESTING BCMA PATCH ISSUE\n display\n-----------------------------------------------------------------------------\n \n \nResolution:\n-----------\nModified the VistA code responsible for generating the report content to check\nthe 'Given' Date/Time when the 'Removal' Date/Time falls outside the date\nrange selected for the report. If the 'Given' Date/Time is within the date\nrange selected then the entry will be included in the report.\n \n \nTechnical Resolution:\n---------------------\nChanged the routine PSBOMH1 at EN+5 and EN+9 to check for the 'Given' date\nwhen the 'Removal' date falls outside the date range selected for the report.\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC1697793 - BCMA med log and medIcation administration history reports\n display\n\n
\nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the BCMA Graphical User Interface (GUI) requires an \nupgrade to Delphi version XE8 in order to implement the new Remote \nProcedure Call (RPC) Broker allowing compliance.\n \nThis patch also updates the Med Order Button to utilize the same version \nof the Dynamically Linked Library (DLL) as the Computerized Patient \nRecord System (CPRS). The version number is controlled by the PSB MOB \nDLL REQUIRED VERSION parameter.\n\n
\nThis patch addresses the request from NSR #20170515 - Adds Respiratory \nTherapy Report.\nAfter this patch is installed, Respiratory Therapists will have access to \nthe new option Report for Respiratory Therapy Medications [PSB \nRPT RESP THERAPY MEDS] VistA to produce a report of patients on\nRespiratory Therapy medications.\n\n
\nError administering multiple doses.\n\n
\nThis patch will resolve the following issue.\n \nProblem: \n--------\nCaptain James A. Lovell Federal Health Care Center reported a problem with\nthe BCBU Initialize options below:\n \n Default Workstation Initialize [PSB BCBU INIT WRKSTN DFT]\n Divisional Workstation Initialize [PSB BCBU INIT WRKSTN DIV]\n \nWhenever these options were executed and one or more Workstation Link were\n \nselected for the initialization the option still generated and sent HL7\nmessage updates to all other existing BCBU Workstation Links.\n \nSolution:\n--------\nThe two Workstation Initialize options above were modified to screen out any\nWorkstation Link not selected from the HL7 update if the user selects one or\nmore specific Workstation Link(s) to update when executing these options. In\nother words, only the selected Workstation Link(s) will be initialized.\n \nINC2794138 - When BCBU init is ran and only one HL7 link is entered it still\nTechnical Resolution:\n---------------------\nThe routines ALPBIN, ALPBIND and ALPBINP were modified to keep track and \nscreen out Workstation Link(s) not selected for the HL7 initialization\nupdate.\n updates numerous links\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC2794138 - When BCBU init is ran and only one HL7 link is entered it still\n updates numerous links\n\n
\nThis patch will resolve the following issue.\n--------\nJames A. Haley VA Medical Center reported a problem with the BCMA Missed \nMedication Report. They were getting an error whenever they tried to run it \nfor a patient that had a PATCH medication order and the dispense drug had\nbeen edited using the BCMA GUI. An additional side effect was the fact that\nthe order no longer showed on the patient's VDL.\n \nResolution:\n-----------\nThe error happened because the Transdermal Project patch PSB*3*83 assumed the\n \nIEN for the DISPENSE DRUG sub-file (#53.796) in the BCMA MEDICATION LOG file\n(#53.79) would always be 1 (one) for a PATCH medication order. Such\nassumption turned out to be incorrect because when the user edits the\ndispense drug for an order in BCMA the IEN 1 gets deleted and IEN 2 gets\ncreated. If a second edit is performed IEN 2 is then deleted and IEN 3 gets\ncreated and so forth. That's the reason the order would not show up on the \nBCMA Patient's VDL and also caused the Missed Medication Report to error out.\n \nTechnical Resolution:\n---------------------\nINC2383720 - Error at REMOVES+23^PSBULTL unable to run report in BCMA\nChanged the following routines: PSBMLEN, PSBMLEN1, PSBO1, PSBUTL, PSBVDLPA,\nPSBVDLRM and PSBVDLVL to retrieve the first dispense drug in the DISPENSE\nDRUG sub-file (#53.795) instead of assuming the IEN 1 to contain the order\ndispense drug. For PATCH medication orders there should only be one dispense\ndrug.\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC2383720 - Error at REMOVES+23^PSBULTL unable to run report in BCMA\n \nProblem: \n\n
\nBCMA WINDOWS 10 AND DELPHI 10 UPDATE.\n\n
\nThis patch will resolve the following issue.\nINC4109840 - CPRS shuts down repeatedly when trying to access BCMA \n(Duplicate) medication history record in CPRS reports tab\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC3683945 - AEU can't look at med admin history (BCMA) due to an error after\n inputting a date range\nINC3570947 - CPRS error caused by patch PSB*3*112, installed at our site on\n(Duplicate) 12/11/2018\nINC3507924 - In CPRS trying to run the Med Admin History report for 11-29\n \n(Duplicate) through 12-5 get the attached error message <UNDEFINED>EN+112^\n PSBOMH1 *PSBAR(64988)\nINC4109840 - CPRS shuts down repeatedly when trying to access BCMA \n(Duplicate) medication history record in CPRS reports tab\n \nProblem: \n--------\nAfter the release of PSB*3*112 a new issue was introduced that caused the \nBCMA Medication Admin History Report to cause an <UNDEFINED> error and exit\nthe BCMA GUI application. The problem is specific to a patient with a PATCH\nINC3683945 - AEU can't look at med admin history (BCMA) due to an error after\nMedication with a ONE TIME schedule (ex: Start Date of D and End Date of D+1)\nand after the PATCH is given on day D and marked removed on day D+1, when the\nuser ran the report for the date Range D thru D the error happens.\n \nResolution:\n-----------\nThis patch prevents the error from happening when the BCMA Medication Admin\nHistory Report is run following the instructions above.\n \nTechnical Resolution:\n inputting a date range\n---------------------\nChanged the routines PSBOMH and PSBOMH1 to prevent the PSBAR array from \ncrashing when the subscript is undefined.\nINC3570947 - CPRS error caused by patch PSB*3*112, installed at our site on\n(Duplicate) 12/11/2018\nINC3507924 - In CPRS trying to run the Med Admin History report for 11-29\n(Duplicate) through 12-5 get the attached error message <UNDEFINED>EN+112^\n PSBOMH1 *PSBAR(64988)\n\n
\nPSB*3.0*113 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\nINC6279084 - Rx ONE TIME PRN orders not revert to active when undo on BCMA\n\n
\nThis patch will resolve the following issue.\n--------\nThe South Texas Veterans Health Care Medical Center reported two problems\nwith the the Initialize a Backup Workstation with BCMA Users [PSB BCBU USER\nINIT] option:\n 1) Users were not able to access the BCBU workstations with their ACCESS/\n VERIFY codes after the option above was run. Thei ACCESS/VERIFY codes\n should match what they use in the main VistA account. Usually, a re-run\n of the option resolves the problem, which is not ideal.\n 2) If there are two users with similar names (e.g., 'NURSE,USER' and \n 'NURSE,USER A' existed, the user with the shorter name would not be able\n \n to access the BCBU workstation, even after the second initialization.\n \nResolution:\n-----------\n1) The setting of cross-references for the newly created users at the\n initialized BCBU workstation was being executed before their ACCESS/\n VERIFY codes were saved. To resolve the problem the cross-references\n setting was moved to run after the ACCESS/VERIFY codes are saved and it\n will address this problem.\n2) The problem happened because the user lookup for 'NURSE,USER' would\nINC3062938 - BCBU/VISTA\n find more than one match, 'NURSE,USER' and 'NURSE,USER A' which would\n prevent it from being updated. To resolve this problem the lookup call\n to find the user record was changed to perform and EXACT match for the\n user name. This way a lookup for 'NURSE,USER' will not find 'NURSE,USER \n A' as a possible match.\n \nTechnical Resolution:\n---------------------\n1) Moved the call to IX1^DIK from line FILE+19 to FILE+23 in the ALPBGEN1\n routine, which is past the setting of the ACCESS/VERIFY codes.\n \n2) Changed the DIC(0)="LM" to DIC(0)="LMX" at line FILE+9 in the ALPBGEN1\n routine, which will force an exact match of the user name.\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC3062938 - BCBU/VISTA\n \nProblem: \n\n
\nThis patch will resolve the following issue:\nN/A\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC5649941 - Medication Patches with a continuous schedule (daily) \n do not show as administered when viewing the medication\n \n administration history report in CPRS with a date \n \nProblem: \n-------\nThe Canandaigua VA Medical Center reported that the Medication \nAdministration History (MAH) Report does not display all the\nadministration activity (given/removed) of continuous patch medication\norders depending on the date range selected for the report. When the date\nrange selected for the MAH report exceeds 7 days and there is a Given\nactivity for a patch medication on the last day of the first week, the\n1. INC5649941 - Medication Patches with a continuous schedule (daily) \nreport will not display it if the patch was already Removed at the time\nthe report was ran.\n \nResolution:\n----------\nThis patch will correct the code to include the Given activity for a \npatch on the last day of the first week in the report.\n \nTechnical Resolution:\n--------------------\n do not show as administered when viewing the medication\nThe code at the EN+62 on the PSBOMH1 routine was not taking into account\nthat the Given date for the order being processed could fall on the week\nbefore the week of the Removal in the report. The code was changed to\ninclude the Given activity in the correct week of the report.\n administration history report in CPRS with a date\n \n \nNew Service Requests (NSRs):\n---------------------------- \n\n
\nThis patch will resolve the following issues:\n--------------------------------------------\n1) INC8817299 -BCBU MAR Shows Expired Meds as Requiring Administration\n \nProblem: \n--------\nBCBU MAR reports were showing medications on the grid as needing\nadministration on their Stop date/time, when the time value ends in a zero,\ne.g. 0900 & 0930. \n \nSolution:\n \n--------\nCorrect BCBU routine ALPBFRM1 to put asterisks in that time cell on the MAR\nGrid.\n \nTechnical Resolution:\n---------------------\nIn routine ALPBFRM1, "+" the variable, when it is created after it\nconcatenates the time to the end of the date. This will trim off \ninsignificant trailing zeros, prior to later compare operations checking if\nthe grid cell date.time is = to the stop date.time of this order.\n1) INC8817299 - BCBU MAR Shows Expired Meds as Requiring Administration\n \n2) INC9226190 - BCMA Contingency program requires verify code be changed\n each time you log into the program\n \nProblem: \n--------\nVA Western New York Healthcare System at Buffalo reported that after patch\nPSB*3*122 was installed the Initialize a Backup Workstation with BCMA Users \n[PSB BCBU USER INIT] option which is used to send BCMA users over from VistA\nto the BCBU workstation was forcing the users to change their VERIFY CODE at\n2) INC9226190 - BCMA Contingency program requires verify code be changed\nthe BCBU workstations when they tried to logon. It was confirmed that the\nissue was introduced by PSB*3*122. In order to fix the problem that required\nthe option above to be run twice in order for the new users ACCESS/VERIFY \nCODEs to work the re-indexing of the new records on the NEW PERSON file (#200) \nwas moved past the "hard setting" of ACCESS/VERIFY CODEs, which resolved the\noriginal but the re-indexing also treats the ACCESS CODE as new and therefore\nforces a new VERIFY CODE to be entered by the user at the BCBU workstation.\n \nSolution:\n--------\n each time you log into the program\nKept the "hard setting" of the ACCESS CODE prior to re-indexing the new record\nin the NEW PERSON file (#200) but moved the "hard setting" of the VERIFY CODE\ninformation after the re-indexing which addresses the issue.\n \nTechnical Resolution:\n---------------------\nMoved the call "D IX1^DIK" up to FILE+20, before setting the VERIFY CODE \ninformation.\n INC9209704(d) - Modify MIW BCMA BU devices to prevent users from needing\n to create a secondary Verify Code\n \nDefect Tracking System Ticket(s) & Overview:\n\n
\n*** Bar Code Medication Administration (BCMA) Version 3.0 ***\n1. Problem: NOIS ISB-0603-31561\nprevious order will display on the new order based on the IV Site \nParameter settings in the GUI BCMA Site Parameters application.\nA medication order that has administration times set for today, but \nbefore the Start Time of the order, displays on the Bar Code Medication \nAdministration (BCMA) Due List Report.\n \nCorrective Action:\nThe Due List Report will not display medication orders until the Start \nDate/Time of the medication order takes affect.\n \n2. Problem: NOIS ISB-0903-31964\n \nWhen the user selects a time frame for the Medication Administration \nHistory (MAH) Report and no administrations are due, the report lists the \nmedication order number from Inpatient Medications V. 5.0 under the \n"Initial-Name Legend" section.\n \nCorrective Action: \nThe MAH Report will not display the order number from Inpatient \nMedications V. 5.0 under the "Initial-Name Legend" section when no \nadministrations are due for a specific time frame.\n \nThis build consists of BCMA Version 3.0 rollover code and resolution to a \n3. Problem: NOIS LAH-1203-61493\nThe user receives the following error message, "BCMA failed to \ncommunicate with VISTA," if the Graphical User Interface (GUI) BCMA times\nout and is unable to connect to the server.\n \nCorrective Action: \nThe processing time for the GUI BCMA software to display the patient s \nrecord on the BCMA Virtual Due List (VDL) has been reduced.\n \n4. Problem: NOIS LIT-0603-71923\nfew outstanding BCMA defects.\nUsers sometimes receive an "allocation failure" error message when \naccessing a patient s record using the GUI BCMA.\n \nCorrective Action: \nThe "allocation failure" error message has been corrected.\n \n5. Problem: NOIS MAD-1203-42204\nThe MAH Report takes an extended amount of time to run if the Start Date \nand the Stop Date of the report, requested by the user, are for different \nyears. For example, if the Start Date is 12/28/03 and the Stop Date is \n \n01/03/04.\n \nCorrective Action: \nThe user can now request different years for the MAH Report without \nexperiencing extended delays as BCMA accesses the data. \n \n6. Problem: NOIS MIN-1203-41637\nUsers sometimes experience an "Invalid Medication Lookup" error message \nafter scanning a medication in the "Scan Medication Bar Code:" field of \nthe "Order Manager" dialog box when using the BCMA Med Order Button in \nListed below are primary National Online Information Sharing ticket \nGUI BCMA.\n \nCorrective Action: \nThe BCMA medication lookup process has been corrected to properly \nvalidate the medications scanned in the "Scan Medication Bar Code:" field \nof the "Order Manager" dialog box in GUI BCMA.\n \n7. Problem: NOIS UNY-0104-10174\nMultiple IV medication orders display as merged on the IV Medication Tab \nafter an order is discontinued, but the IV bag is still infusing.\n(NOIS) identification information representing BCMA defects/problems\n \nCorrective Action: \nMultiple IV medication orders will display properly on the IV Medication \nTab. \n \n8. Problem: NOIS TNV-0104-30647\nUsers sometimes experience the following error message, "ERROR: 16^Server \nProtocol Disabled," when using the Edit Medication Log [PSB MED LOG EDIT] \noption. This occurs when the PSB BCMA RASO17 SRV Health Level Seven (HL7) \nserver protocol is being disabled.\nand their respective corrective action.\n \nCorrective Action:\nThe error message is only intended to notify the BCMA software that the \nprotocol is being disabled. BCMA will now validate the message and not \ndisplay it to users. \n \n9. Problem: NOIS ISB-0104-31384\nWhen an IV medication order with an infusing bag is "Renewed," the \nrenewed order continues to display on the IV Medication Tab of the BCMA \nVDL until the infusing bag is "Completed," even if the "Renewed" order's\n \nStart Date/Time has expired.\n \nCorrective Action:\nWhen an IV medication order with an infusing bag is "Renewed," the \nrenewed order will continue to display on the IV Medication Tab of the \nBCMA VDL until the infusing bag is "Completed," or until the Start \nDate/Time of the new order that was created during the renewal process. \nOnce the new order is active, the infusing bag from the previous order \nwill display on the BCMA VDL with the new order, along with any \nadditional bags created from the new order. Any available bags from the \n\n
\nThe pre-installation for this patch runs routine ^NVS11PRE. This routine\nupdates the PACKAGE file (#9.4) to ensure that there is a version 2.0\nentry for the record for the "OS-OPENM" package reocrd.\n \nThe core function of this patch removes Y2K monitoring routines and server\noptions. This patch also contains a revised routine ^NVSMSG. The repair\nis to date format during the creation of a VA MailMan message. Various\nother clean up has been done to NVSMSG.\n\n
\nThe pre-installation for this patch runs routine ^NVS11PRE. This routine\nupdates the PACKAGE file (#9.4) to ensure that there is a version 2.0\nentry for the record for the "OS-OPENM" package reocrd.\n \nThe core function of this patch removes Y2K monitoring routines and server\noptions. This patch also contains a revised routine ^NVSMSG. The repair\nis to date format during the creation of a VA MailMan message. Various\nother clean up has been done to NVSMSG.\n\n
\nThis build contains revised Avanti System backup procedure routines\nfor patch OSI*2.0*12.\n\n
\nThis build contains a single routine that is run as a post-installation \nprocess. This routine is only appropriate for VMS/Cache systems and a \nspecific check for that environment is made before any processing is done.\n \nIf appropriate, the routine examines the Terminal Type file (#3.2) for any\nentries containing the name prefix P-MESSAGE. If any are found, the OPEN \nEXECUTE and CLOSE EXECUTE fields are modified to match current VistA \nstandards for VMS/Cache installations.\n\n
\nPatch EN*7*33 FIXED ASSETS CORRECTIONS\n1. Update TOTAL ASSET VALUE in 6914 when FC DOCUMENT to 00 (FA) has zero\n value.\n2. Update FUND names list to match FMS table values.\n\n
\nThe patch contains FAP-Interface related enhancements such as\n o CMR (EIL) Report modified\n o Nonexpendable Expensed Inventory Report modified\n o Adjustment Vouchers & Report\n o Summary of SGL Balances Report\n o Transaction Register Report\n o Voucher Summary Report modified\n o Document History Report modified\n o FAP Document changes (BBFY, validity checks, etc.)\n o Equipment SPEX field\n o Cost Center inferred from CMR (EIL)\n\n
\nCorrect 'invalid' EIL cost centers that were introduced by patch EN*7*39.\n\n
\n o Do not update equipment physical inventory dates on the basis of PM\n work orders that were closed out with a PM status of DEFERRED.\n o Update work order status whenever a date complete is entered during the\n edit phase of a new work order entry option.\n o Test for the existence of local variable ENX in line TOP15+7^ENWOD2\n before referencing it.\n o Add a line feed to the positioning logic for work order bar code. \n\n
\n 1. Updates NX FUND, NX SGL, and NX BOC files for Fiscal Year 1998.\n 2. Renames Excess standard general ledger from 1561 to 1524.\n 3. Modifies Adjustment Voucher reason codes appropriate for FB Document.\n 4. Moves equipment from Funds 4138, 6019, or 5014A1 to Fund AMAF.\n 5. Moves equipment from Fund 8129G to Fund 8129S.\n 6. Moves Trust equipment from SGL 1754 to SGL 1750.\n 7. Lists ADPE Trust equipment that should be manually moved from SGL 1750\n to SGL 1751.\n\n
\no Correct possible <UNDEF> error at NEWNX+8^ENEQNX1 (queueing of NX\no Accomodate large numbers of equipment records during multiple\n equipment editing (Purchase Order Group Edit) by locking equipment\n records one at a time when the count exceeds 50\no Accomodate a new version of MedTester upload software released by\n DNI Nevada (the manufacturer)\n inventory exception lists)\no Use Engineering Computer Port file for customizing bar coded equipment\n and location labels\no Improve the selection algorithm for inclusion of user-specified fields\n on bar coded equipment and location labels and use VA FileMan calls\n instead of global reads\no Correct possible <UNDEF> error at STMPLT+4^ENEQP (direct posting of\n equipment repair histories)\n\n
\nPatch EN*7*28 PROGRESS REPORT (10-0051) ENHANCEMENT\n 9. Project Application miscellaneous updates\n 1. Progress Report support for Station Level Projects\n 2. Progress Report content modified\n 3. Progress Report format modified\n 4. Progress Report edit screens modified\n 5. Progress Report data validation added\n 6. Progress Report electronic transmission modified\n 7. Progress Report Actions Due Report added\n 8. 5-Yr Plan Project miscellaneous updates\n\n
\no Allows entry of Capital Lease assets. These are items of nonexpendable\n order comments (re: option ENDSY).\n \no Inserts a pattern test of user entered PM work orders before performing\n a concatenation (re: option ENPMR2).\n \no Prevents a <NULLSUBSCR> error when invalid ranges are entered during the\n assignment of electronic work orders.\n \no Corrects inappropriate references to local variable %ZIS(0) and allows\n users to queue incoming inspection work orders on multiple equipment\n equipment purchased with the Supply Fund and owned by the VA facility.\n receipts more reliably. The user is asked for a queue date and time when\n the first equpment record is entered. All subsequent equipment records\n automatically use that same date and time.\n The facility then makes incremental lease payments to the Supply Fund\n until the Supply Fund has been reimbursed in accordance with policy in\n effect at the time the Capital Lease equipment was acquired. Facilities\n should begin to depreciate Capital Lease equipment as soon as it is\n acquired.\n \no Removes a redundant call to VA FileMan in the printing code for work\n\n
\n Project Tracking fixes:\n 1. Provide support for NCS GOE project reports within Station Level\n program validation.\n 2. Fix applicable Milestones when Construction Method = Station Labor.\n 3. Fix queuing of Actions Due report.\n\n
\nUpdate software to treat expensed ADPE, motor vehicles, and firearms in\nthe same manner as other expensed equipment based on the policy change\nto VA Handbook 7127/1.\n o CMR INVENTORY (EIL) REPORT modified\n o NONEXPENDABLE EXPENSED INVENTORY REPORT modified\n o INVENTORY EXCEPTION LISTING modified\n o ACCOUNTABLE NX FOR STATION REPORT modified\n o FIND & ASSEMBLE option modified for equipment archives.\n\n
\nCorrections for possible Y2K problems.\n\n
\nThis patch adds Fund 4539 (Franchise Fund) to the NX FUND (#6914.6) file.\n\n
\no Update JCAHO field (#27) in Equipment file (#6914) based on changes to\n corresponding field (#3) in Equipment Category file (#6911) when update\n is requested by user.\no Print LAST SERVICED DATE on first equipment edit screen in proper Y2K\n format.\n\n
\nFix problems with maintenance of incomplete work order (AINC) x-ref.\n1. Discontinue use of AINC x-ref to store assigned technician data.\n2. When user transfers a work order, require that new shop be different\n from current shop.\n\n
\nA module that works with the existing Equipment Management and Equipment\nRepair modules. It serves as a tool for identifying specific pieces of\nequipment that may be subject to YEAR 2000 problems. It also provides a\nmeans of planning and tracking the necessary corrective action.\n\n
\nPatch for a patch. A data entry screen in EN*7*51 contains a reference to\na field that will be introduced with EN*7*55. This causes an <UNDEF> error\nduring equipment edit sessions. The sole purpose of this emergency patch\nis to replace the defective edit screen.\n\n
\n o Restructure the AMAF fund into six different funds (AMAFxx).\n o Add Administrative/Office code "02" for General Counsel.\n\n
\no Add Utility System field to the Y2K Equipment Management Module.\no Install national reporting capability for Y2K equipment management.\n\n
\no Enables national roll-up of Y2K equipment data (correction to EN*7.0*55).\n\n
\n 1. Prevent changes or deletions of work order numbers via the Edit Work\n the PM input template when PM work orders closed via this option.\n 6. Stop posting disapproved work orders to the equipment history.\n 7. Accommodate local cross-references on equipment history multiple.\n 8. Include count of equipment records with no FUNCTIONAL CLASSIFICATION \n and a Y2K CATEGORY of 'NOT APPLICABLE' in the electronic Y2K progress\n report sent to VACO.\n Order Data option. Introduce a new separate 'Delete Open Work Order'\n option locked by new security key ENWODEL for deletions.\n 2. When a WORK ACTION is entered, prompt for another one.\n 3. Re-calculate work order TOTAL HOURS and TOTAL LABOR COST when ASSIGNED\n TECH field is edited or deleted.\n 4. Perform requested technician substitutions (if any) when Rapid\n Closeout of PM Work Orders option is queued.\n 5. Modify Close Out Work Order option to update equipment file and use\n\n
\n o Modify FA and FR Documents to include the entire CMR value instead of\n o Transmit FR Documents for all existing equipment to populate CMR values\n in Fixed Assets.\n o Fix CMR Inventory (EIL) report problem with local template and update\n references on signature page.\n just the first two characters of the CMR value.\n o Modify the Transaction Register and Document History reports to display\n the entire CMR value sent on FA and FR Documents.\n o Modify the CMR File Enter/Edit option to generate FR Documents when a\n CMR name is changed instead of when the first two characters of the CMR\n name is changed.\n o Prevent CMR entries from being deleted if equipment points to the CMR.\n o Force correction of dangling CMR pointers in the equipment file.\n\n
\no Makes it possible for Open-M sites to connect MedTesters (electrical\n piece of equipment is found twice in the same MedTester upload is\n handled as gracefully as possible.\no Prevents Y2K work orders from being used for correcting failed PMIs.\n safety analyzers) and portable bar code readers to VistA terminals\n without using a special port definition.\no Initializes variable ENFLG between MedTester records to correct a\n problem with the logic used to detect a test failure.\no Updates the MedTester upload software so a test failure in the new\n defibrillator test will be detected in a similar manner to a failure\n during the electrical safety (EKG) test.\no Updates the MedTester upload software so that a case where the same\n\n
\nJANUS 2020 BARCODE READER ENHANCEMENT\n\n
\no Corrects routine ENY2K1 so that Equipment Replacement Schedule displays\n properly on the Cumulative Report.\no Allows users to include equipment records that lack a MANUFACTURER\n and/or a MODEL on the Detailed Y2K Report.\no Insures that all new Y2K work order numbers are checked against the\n ^ENG(6914,"AL") x-ref to prevent duplication.\n\n
\nFix Delete Old Incomplete PM Work Orders [ENDELPM] option so a valid\ndefault date is calculated if option is run on February 29th.\n\n
\nSpace/Facility module minor enhancements:\n off of a display screen.\n o Prevent deletion of ENG SPACE file entries that are pointed to by\n either the EQUIPMENT file (#6914) or the WORK ORDER file (#6920).\n o Remove ZZ prefix from local entries in ENG SPACE FUNCTION file.\n o Allow decimal digit in CEILING HT field of ENG SPACE file.\n o Use computed field for total quantity of key in EMPLOYEE(KEY) file.\n o Increase length of KEY fields in LOCKS file.\n o Display OTHER KEY field on Display/Edit Room Data option.\n o Delete ISSUED TO multiple from LOCKS file.\n o Replace WRITE with DDIOL in DD of EMPLOYEE field in EMPLOYEE(KEY) file.\n o Prevent C0MMENTS field in the ENG SPACE file from scrolling other data\n\n
\nIncrease Nonexpendable (NX) Equipment Capitalization Threshold\n o Enhance package to permit different thresholds for capitalization\n and accountability.\n o Increase capitalization threshold from $5,000 to $25,000.\n o Perform a one-time task to expense equipment that does not meet\n the new capitalization threshold.\n\n
\n o Modify the work order screen display/edit so the edit session is ended\n when a date complete is entered. Post install updates existing\n equipment histories using work order data to correct inconsistencies\n that may have occurred prior to this patch.\n \n o Modify code to strip the time from the date when posting data to\n equipment histories. Post install updates existing equipment histories\n that were posted with a time prior to this patch.\n\n
\nUse "00" as the beginning budget fiscal year (BBFY) on FAP documents for\nthe Franchise Fund (4539).\n\n
\no Fix Accountable NX for Station [ENFAR8] report.\no Fix DJ screen handler to prevent undefined error when timeout occurs\n during a word processing field edit.\n\n
\nMinor fixes for MedTester uploads and PM work order close out.\n\n
\nThis patch includes enhancements requested by the National Database\nIntegration Team (NDBI) to support future site integrations. This patch\nalso improves month/year prompts for several options.\n\n
\nThe following Engineering options are now obsolete:\nThis option is now Out of Order. Construction project data is now \nentered and reported in a web database at http://vaww.domain.ext/capassets.\n\nPlease, contact your Network Capital Assets Coordinator, or VSSC\nrepresentative for assistance.\n\n 1. Transmit 5-Yr Plan Projects [ENPLMFX]\n 2. Transmit Project Applications [ENPLMAX]\n 3. Transmit Project Status Reports [ENPLMRX]\n\n\nThe users will now get the following message:\n----------------------------------------------\n\n\n
\nCorrection to ENLIB3 so that EQUITY ACCOUNT will be inferred properly. A\npatch for patch EN*7.0*33.\n \nPost-Installation routine corrects data in AEMS/MERS Equipment File\n(#6914).\n \nCode in routine ENLIB3 that infers AO when such is not available from\nIFCAP is now deactivated at the request of FMS.\n\n
\nIncrease Equipment Capitalization Threshold to $100,000.00\n\n
\nExtract AEMS/MERS Work Orders for Asset Management to compare CoreFLS and\nEngineering package.\n\n
\nThe system language, in some cases, treats the "E" in a number string as \nan exponential notation. For instance, "1E3" would equate to "1000". \nDue to this "E" exponential notation, like in the NOIS, the value of the \ninput Purchase Order number becomes too large for the system to handle \nand the system issues the error "illegal number".\n\n
\nThis patch addresses the problem where a network printer is\nunable to be used as a companion printer.\n\n
\nThis patch will install menu option 16 for CoreFLS Data Cleansing Reports. It\nwill then install a sub-menu for 6911 reports. Please see patch documentation \nfor description of data cleansing reports for 6911 file.\n\n
\nDATA CLEANSING REPORTS FOR 6914 FILE\n\n
\nCoreFLS Data Cleansing Reports for the Work Order (#6920) file.\n\n
\nCoreFLS Data Quality Assurance - Engineering Space (#6928) Patch EN*7.0*77\n\n
\nCoreFLS Data Cleansing Reports for BUILDING FILE (#6928.3)\n\n
\nCoreFLS Data Cleansing Reports for AEMS/MERS file PM PROCEDURES (#6914.2)\n\n
\nThis enhancement patch modifies the FD Document (for Turn-In) process to\nsave the original asset value and capture the fair market value. The new\nOriginal Asset Value field is added to equipment screen 2. A post-init\npopulates the new Original Asset Value field for existing FD-T documents.\n\n
\nCoreFLS Data Cleansing Reports for Engineering Employee File (#6929)\n\n
\nThis patch will add the AMAFMF fund code to the NX FUND (#6914.6) file.\n\n
\nThe operational test site using CoreFLS was reverted to its pre-CoreFLS \nstate and the CoreFLS project was suspended. Consequently halting all \ndata cleansing efforts and requiring that components of the data \ncleansing patches (EN*7.0*74, EN*7.0*75, EN*7.0*76, EN*7.0*77, EN*7.0*78, \nEN*7.0*79, and EN*7.0*81) be removed at each site.\n\n
\nThis patch contains a template to extract data from file 6914.\n\n
\nThis patch adds fund code AMAFIT to the NX FUND (#6914.6) file.\n\n
\nThis patch contains the IT Equipment Tracking project enhancements.\nThe Engineering (AEMS/MERS) package is modified to provide IT personnel a\nnew top level menu. IT personnel will be able to edit selected data\nfields of IT equipment in the non-expendable equipment inventory. The\nproject will also add support for the individual assignment of\nresponsibility for IT assets. Individuals can sign electronic hand\nreceipts to accept responsibility.\n\n
\nThere is a known bug with some of the outputs where assignments are listed\nunder a person that does not actually have that assignment. These outputs\nare searching the assignments for a specific person or equipment item. The\nproblem is that the utility being used also includes assignments that\npartially match the search criteria. For example, a search for active\nassignments for a person with internal entry number 100 will also include\nany active assignments for other persons whose internal entry number \nstarts with 100 such as 1001, 10025 etc.\n\n
\nThis patch addresses two issues about non-standard IO symbols for the\nbar code printing in the Engineering application running under the Red\nHat Linux operating system.\n\n
\nThis patch addresses 3 issues:\n1. User is receiving an Undefined Error when entering a "^" and any \nother character at an edit prompt followed by a "^" at the next edit\nprompt when using ENGINEERING EMPLOYEE FILE option and KEY DISTRIBUTION BY\nEMPLOYEE option.\n2. Text Change to Directive # printed on Hand Receipt.\n3. EQUIPMENT INVENTORY FILE (#6914) CMR field (#19) trigger is not \nworking properly.\n\n
\nManufacturer List File (#6912) with selected data (ien > 3000 and <50000).\n\n
\nPatch EN*7.0*92 adds 1 new code to the NON-EXPENDABLE EQUIPMENT BUDGET \nOBJECT CODES (NX BOC) (#6914.4) file and and re-names code 1524 to 1995 \nin the NON-EXPENDABLE STANDARD GENERAL LEDGER (NX SGL)(#6914.3).\n\n
\nThis patch addresses 1 issue:\n \nUser is receiving an Undefined Error when deleting an entry using \nthe Enter/Edit Room Planning Data [ENSP-PLAN1] Menu Option\n\n
\nThis patch addresses three issues:\n3. The third issue is about an error - <NOTOPEN>^PRT1^ENWOD in the \n Multiple Work Order Entry [ENWOMULTI] option when the device is forced\n queuing the job in a task.\n \n1. The first issue will add 1 new code and deactivate 3 old codes in the\n Non-Expendable Equipment Budget Object Codes (NX BOC) file (#6914.4).\n \n2, The second issue involves a subscript error occurring at \n NEWLOC+1^ENEQNX1 when there is no nonexpendable inventory data uploaded\n from the portable bar code reader to the Barcode Program file (#446.4).\n \n\n
\nThis build supports the interface between the Real Time Location System \non #.01 sub-field of the multiple field Responsible Shop. This build also\nplaces the flag 'NOREINDEX' in all the fields with an RTLS trigger in\norder to stop the flooding of the file #6930 in case one of those fields\nis reindexed. See the Forum patch description for the list of fields\naffected in files #6914 and #6928.\n(RTLS) at Intelligent Insites and VistA files #6914 and #6928 in \nEngineering.\n \nAfter installation of this patch, field #.01 of file #6928 will have\none RTLS trigger to notify the RTLS database of the creation of a new\nroom. Also, this build places MUMPS cross references (behave like a\ntrigger) on multiple fields of file #6914, expands the description text\nfor fields #23 and #24, and adds a description to the cross reference 'AB'\n\n
\nThe patch addresses 1 issue:\n \n1. Users are not able to set an Equipment Return Date greater than 90\n days in the future. Some equipment needs this date to be as far as\n 365 days in the future.\n\n
\nThis patch addresses the following SNOW ticket:\n \nINC29452812 - User needs to be able to import new records to the \n ENGINEERING INV. File (#6914) from a tab-delimited\n spreadsheet.\n\n
\nNEW QUAD-ANNUAL & PENT-ANNUAL FREQUENCY NOT DISPLAYING\n\n
\nPatch EN*7*35 contains Equipment Inventory module and Work Order module\n o Improve Inventory Exception List\n o Improve Equipment Category History\n o Work Order Selection by Equipment or Location\n o Multiple Work Order Entry\n o Notify Work Order Requester\n o Improve Capture of Preventive Maintenance Manhours\n o Remove limit on number of PM Work Orders\n o Incoming Inspection Work Order for New Equipment\n o Remove ZZ from Manufacturer List file\n o More flexibility in barcode label format\nenhancements that were originally developed for the next version of the\n o New Parent System/Component Hierarchy report\nEngineering package.\n \n o Purchase Order Group Equipment Edit\n o Condition Codes for Equipment\n o Equipment Flagging\n o Equipment Lockout/Tagout\n o Station Specific New Equipment Bulletins\n\n
\nThis patch enhances and fixes the Engineering Archive module.\n 1. Adds EQUIPMENT INV. (#6914) file archive capability.\n 2. Save values of LOCATION, PARTS ORDERED ON ACC.#, VENDER SERVICE COST,\n and WORK ACTION fields during work order archives.\n 3. Only ask archive device once during archive or recall session.\n 4. Only use tape commands when device type is MAGTAPE.\n 5. Delete the data dictionary when the archive global is deleted.\n 6. Update the WO ARCHIVE data dictionary to match the WORK ORDER file.\n 7. Adds Delete Equipment Record option.\n\n
\no Allows posting of Preventive Maintenance Inspections (PMI) to Equipment\no Allows '^' escape from parent system hierarchy report.\no Allows slave printing of new and transferred work orders, even when\n AUTOPRINT WORK ORDER software option is set.\no Includes four revised input templates:\n - ENEQPMP in File #6911\n - ENEQPMP in File #6914\n - ENWOEDIT in File #6920\n - ENWOWARDXFER in File #6920\no Allows printing of punctuation in bar coded location labels.\no Resets local variable DIC for each look-up during 'Rapid Closeout of PM\n Repair Histories in the absence of an ASSIGNED TECHNICIAN.\n Worklist' option.\no Ignores free text locations when displaying incomplete work orders for a\n range of locations.\no Validates "G" cross-reference in File #6920 during work order display\n (routine ENWOD2).\no Corrects errors in PMI Worklist generation by LOCAL ID.\no Allows free text locations in PM worklists.\no Adds TRIGGER to Eng Building File (#6928.3). Entries to the Building NAME\n will automatically update the Building DIVISION.\no Corrects an error in looking up equipment records by EQUIPMENT CATEGORY\n (EC.<value>).\no Restores 'Incomplete Work Order' menu options.\n\n
\nRestructuring of Work Order Module, conversion of LOCATIONS from\nfree text into pointers, and electronic transmissions to Regional\nConstruction offices.\n\n
\nFirst proposed in the mid to late 1970's, MUMPS coding of this package\nbegan about 1980. National distribution of hardware and software took\nplace in 1984.\n Principal modules include Work Control, Equipment Managment, and\nConstruction Tracking.\n\n
\n This patch adds:\n print data from the REMINDER EXTRACT SUMMARY file (810.3)\n REQUIRED BUILDS:\n ================\n CLINICAL REMINDERS 1.5\n \n INSTALLATION INSTRUCTIONS:\n ==========================\n \n This patch should be loaded during non-peak hours to minimize disruption\n to users. Installation will take less than 15 minutes.\n \n * 2 new sort templates, one to identify terms to distribute and one\n **Warning** \n When an option is included in the patch build, the question REBUILD MENUS\n is asked as a PRE-INSTALL question. If you choose to have KIDs rebuild\n the menus it will happen at the end of the build installation and may\n take several hours.\n \n 1. Download the KIDS file HEP_C_EXTRACT_1_0.KID via FTP from any\n of the anonymous.software directories listed above. Move the file\n to the appropriate directory on your system.\n \n for the REMINDER EXTRACT SUMMARY file\n 2. Review your mapped set. If any of the routines listed in the\n Routines section are mapped, they should be removed from the mapped\n set at this time. \n \n 3. From the Kernel Installation and Distribution System (KIDS) menu,\n select the Installation menu.\n \n 4. Use Load a Distribution option on the KIDS Installation menu, and\n enter: HEP_C_EXTRACT_1_0.KID\n \n * 3 new print templates, all related to reporting the EPI findings\n 5. From this menu, you may elect to use the following options\n (when prompted for INSTALL NAME, enter HEPATITIS_C_EXTRACT).\n \n Note - Option (a.), Backup a Transport Global, can and must be\n referenced exclusively by the primary build name of\n HEPATITIS_C_EXTRACT. Option (b.) can be run by either using the\n primary build name of HEPATITIS_C_EXTRACT or the individual patch\n names (e.g., PXRM*1.5*1, etc.). Options (c.) and (d.) must be run\n for each individual build (using the patch names) included in\n this transport.\n \n \n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - this option will\n allow you to ensure the integrity of the routines that are in\n This patch modifies the:\n the transport global.\n d. Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n \n 6. Use the Install Package(s) option and select the package\n HEPATITIS_C_EXTRACT.\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond NO.\n \n * description in the VA-HEP C RISK ASSESSMENT reminder definition\n 8. If routines were unmapped as part of step 2, they should be returned\n to the mapped set once the installation has run to completion.\n \n POST INSTALLATION INSTRUCTIONS\n ============================== \n The details of the setup to be completed is available in the\n documentation. Generally, these steps need to be done by the REMINDERS\n MANAGER or the CLINICAL REMINDERS APPLICATION COORDINATOR. The success of\n the Hepatitis C updates to the EPI database will depend on a Hepatitis\n Team at your site addressing all of the issues in the documentation.\n * description for 3 previously distributed Reminder Terms\n \n 1. See the descriptions for the reminder definitions and \n the descriptions in the REMINDER TERMS file to determine what\n additional setup is required for the terms. You will need to review\n the reminder terms with laboratory and pharmacy coordinators.\n \n 2. You can use the Detailed Reminders Due report to determine if all\n the correct patients are being identified to send to the EPI\n database.\n \n * name and description for the Reminder Term PREV POSITIVE TEST FOR\n 3. You may need to check that all dispensed drugs are mapped to the\n national drug file entries represented by the Hepatitis C Medication\n terms. If you have local dispensed drugs that cannot be mapped to the\n national drug file (VA GENERIC, #50.6), you will need to enter the\n dispensed drugs as findings for the appropriate national reminder\n term.\n \n 4. Add local laboratory tests with appropriate CONDITIONS in the\n REMINDER TERM file for the laboratory terms.\n \n HEP C, which is renamed PREVIOUSLY ASSESSED HEP C RISK\n 5. The VA-NATIONAL EPI LAB EXTRACT and VA-NATIONAL EPI RX EXTRACT\n reminders should NOT be added to the "Clinical Reminders for Search"\n parameter for clinicians. The Reminders Manager may want to create a\n National EPI Update reminder category and add these reminders to it,\n along with the VA-HEP C RISK ASSESSMENT REMINDER. The category could\n be added to the CPRS Reminder Categories parameter option for testing\n the setup of the reminder terms and reviewing the results.\n \nDETAILED DESCRIPTION:\n=====================\n * 2 new reminder definitions to the REMINDER DEFINITION file (811.9)\n \nData Dictionary:\n \n 1. REMINDER DEFINITION file (811.9)\n The reminder for VA-NATIONAL EPI DB UPDATE may be used at sites to\n determine whether a patient has data that is sent to the Austin\n Automation Center to update the national EPI database.\n \n 2. REMINDER TERM file (811.5)\n There are twenty reminder terms used by the lab and pharmacy extract\n reminders. Eighteen of these terms are newly distributed in this\n This patch will work with the LR*5.2*260 patch and two pharmacy\n file. These new terms represent Hepatitis A, Hepatitis B and\n Hepatitis C lab and medication information. The reminder terms may be\n used at sites in locally defined reminders for clinicians providing\n clinical care for Hepatitis patients.\n \n Hepatitis A laboratory reminder terms:\n HAV Ab positive Hepatitis A virus antibody total positive\n HAV IgM Ab positive Hepatitis A virus antibody immunoglobulin\n M positive \n HAV IgG positive Hepatitis A virus antibody immunoglobulin\n patches (PSO*7*45 and PSJ*5*48) to extract Hepatitis C risk\n G positive\n Bilirubin\n \n Hepatitis B laboratory reminder terms:\n HBs Ag positive Hepatitis B surface antigen positive \n HBc Ab IgM positive Hepatitis B core antibody immunoglobulin\n M positive \n HBs Ab positive Hepatitis B surface antibody positive\n HBe Ag positive Hepatitis B e antigen positive \n \n assessment, laboratory and medication data. The extracted data will be\n Hepatitis C laboratory reminder terms: \n HEP C VIRUS ANTIBODY NEGATIVE \n HEP C VIRUS ANTIBODY POSITIVE \n TRANSFERASE (AST) (SGOT)\n ALANINE AMINO (ALT) (SGPT)\n \n Hepatitis Medications (based on VA GENERIC file): \n INTERFERON ALFA-2A \n INTERFERON ALFA-2B \n INTERFERON ALFA-2B/RIBAVIRIN \n used to update the EPI database at the AAC.\n INTERFERON ALFA-3N \n INTERFERON ALFACON-1 \n INTERFERON BETA-1A \n INTERFERON BETA-1B \n RIBAVIRIN \n \nSort Template:\n \n PXRM EPI LAB AND MED TERMS contains reminder term entries defined above\n to distribute with the REMINDER TERM (811.5) data dictionary.\n \n \n PXRM EXTRACT EPI BY FIND_PT sorts an extract by Finding Item and SSN.\n This sort template may be useful when looking up an SSN to compare\n findings to an error message returned to the site from the AAC. When\n the AAC has problems processing a sites extracted data, the original\n extract message and SSN are returned to the site in an error message\n for review and correction.\n General Overview:\n =================\n This patch is released in response to Congressional reporting\n requirements and a policy letter distributed by the Under Secretary\n * 18 new national terms to the REMINDER TERM file (811.5)\n of Health addressing treatment of Hepatitis patients.\n \n The data extracted for Risk Assessment is based on the VA-HEP C RISK\n ASSESSMENT reminder definition. The data extracted from laboratory is\n based on the VA-NATIONAL EPI LAB EXTRACT reminder, previously\n distributed as VA-NATIONAL EPI DB UPDATE. Both of these reminders were\n first released in the Clinical Reminders V.1.5 package. A new reminder\n definition, VA-NATIONAL EPI RX EXTRACT, is distributed in this patch for\n extracting medications. These three reminder definitions provide the\n criteria for extracting the risk assessment, lab, and medication data.\n * 1 new file, REMINDER EXTRACT SUMMARY (810.3), that temporarily\n \n The reminder evaluation and update to the EPI database occurs on the\n 15th of the month following the reporting month. The option that manages\n this update is the LREPI NIGHTLY TASK. This task currently runs nightly\n at each site. Note: The monthly task on the 15th occurs because the LAG\n DAYS field in the LAB SEARCH/EXTRACT file (69.5) is set to "15" for each\n pathogen. The LR*5.2*260 patch contains new processing logic that sends\n data extracted from reminder extract results to the EPI database.\n \n This patch also fixes a problem where CUSTOMIZED PATIENT COHORT LOGIC\n stores data extracted from reminder evaluation processing when\nwas \n not being used in the reminder evaluation. (NOIS SLC-0600-52703).\n \n NOIS Messages:\n ==============\n SLC-0600-52703\n MON-0800-50154\n \n \n Build Components:\n updating the EPI database. This temporary data can be used to\n =================\n Data Dictionary for three files:\n REMINDER EXTRACT SUMMARY (810.3) (new) \n REMINDER DEFINITION (811.9)\n REMINDER TERM (811.5)\n \n Option:\n PXRM REMINDER REPORTS menu (description change; lists new options)\n PXRM REMINDERS DUE (no change, just attach to menu)\n PXRM EXTRACT EPI TOTALS (new)\n compare to data in HL7 messages sent to the EPI database, and\n PXRM EXTRACT EPI FINDING LIST (new)\n \n Print Templates to print data from the REMINDER EXTRACT SUMMARY:\n PXRM EXTRACT EPI FINDING LIST (new)\n PXRM EXTRACT EPI FINDING HDR (new)\n PXRM EXTRACT EPI FINDING TOT (new) \n \n Sort Templates:\n PXRM EPI LAB AND MED TERMS (new)(identifies reminder terms to\n include in this patch)\n validate that the appropriate data is extracted.\n PXRM EXTRACT EPI BY FIND_PT (new)(sorts the extract data in the\n REMINDER EXTRACT SUMMARY file)\n \n Routines:\n \n The second line of each routine looks like:\n \n <tab>;;1.5;CLINICAL REMINDERS;**1**;June 19, 2000\n \n Routine Old Checksum New Checksum Patch List\n * 2 new options added to the PXRM REMINDER REPORTS option menu to\n ======= ============ ============ ==========\n PXRMLOGX 3009219 3005995 **1**\n PXRMP1I n/a 2412825 **1** \n PXRMP1IE n/a 349212 **1**\n PXRMTERM 6249864 6249864 **1**\n PXRMXX 2465756 9832947 **1**\n PXRMXX1 n/a 8675493 **1**\n PXRMXX2 n/a 8200381 **1**\n PXRMXXT n/a 573203 **1**\n \n\n
\nThis patch makes changes to MST synchronization and dialog so that\ndates passed to the MST API will not be rejected by the API.\n\n
\nNOIS fixes, see the National Patch Module for a complete description.\n\n
\nNOIS fixes, see the National Patch Module for a complete description.\n\n
\nNOIS fixes, see the National Patch Module for a complete description.\n\n
\nThe description of this patch is found in the National Patch Module under \nthe name PXRM*1.5*15. It contains 3 National Mental Health Reminders.\n\n
\nSEE NATIONAL PATCH MODULE\n\n
\nThe description of this patch is found in the National Patch Module under \nthe name PXRM*1.5*18. Clinical Reminders - Code Set Versioning\n\n
\nThis patch creates a utility that provides an estimate of size of the\nClinical Reminders index. See the National Patch Module entry for full\ndetails.\n\n
\nSee description in the National Patch Module under the patch number \nPXRM*1.5*21\n\n
\nThis patch creates the Clinical Reminder index global. See the National\nPatch module for a complete description.\n\n
\nClinical Reminders version 1.5 patch 2. This patch includes a number of\nbug fixes and enhancements. Please see the National Patch module for a\ncomplete description.\n\n
\nReminder Dialogs for TIU.\n\n
\nThis patch update the Exchange Utility so it is compatible with version\n1.5 of Clinical Reminders.\n\n
\nThis patch includes fixes and minor changes to the Reminders Due report.\n\n
\nThis patch provides tools for Clinical Reminders to support MST\nfunctionality. See the National Patch Module for a complete\ndescription.\n\n
\nThis patch distributes the VA-MST SCREENING reminder that was missing\nfrom patch PXRM*1.5*7.\n\n
\nThis patch contains national reminders for the IHD QUERI project:\n \nVA-IHD ELEVATED LDL\nVA-IHD LIPID PROFILE\n \nSee national patch module for details.\n\n
\nThis build installs Clinical Reminders V1.5 as a separate package from the\nPatient Care Encounter (PCE) package. \n\n
\nClinical Reminders\n\n
\nRelease National VA-TBI/POLYTRAUMA REHAB/REINTEGRATION PLAN OF \nCARE Dialog.\n\n
\nPolytrauma marker.\n\n\n
\nARCH\n\n\n\n
\nHigh Risk Mental Health.\n\n\n\n
\nDG API Updates.\n\n
\nNational Teratogneric Medications Order Checks\n\n\n
\nSee description in the national patch module under patch PXRM*2*2.\n\n
\nNational Clinical Reminders content updates.\n\n\n
\nHigh Risk Mental Health phase 2.\n\n\n
\nNational Clinical Reminders content updates.\n\n\n
\nNational Clinical Reminders content updates.\n\n\n
\nNational Clinical Reminders content updates: VA-TETRATOGENIC MEDICATIONS\nORDER CHECKS, Update #1.\n\n\n
\nNational Clinical Reminders content updates: Pneumoccocal vaccine.\n\n\n
\nNational Clinical Reminders content updates.\n\n\n
\nClinical Reminders ICD-10 changes.\n\n\n
\nNational Clinical Reminders content updates, Mental Health dialogs,\nincrements 1 and 2.\n\n\n
\nNational Clinical Reminders content update Ebola screening.\n\n\n
\nMyHealtheVet National Clinical Reminders\n\n
\nThis patch corrects a problem with the "AB" index of file #100.21 not\nbeing populated when copying a reminder patient list to an OE/RR team\nlist. In the post-init it checks all existing lists in file #100.21 and\nensures the "AB" index is populated for all of them.\n\n\n\n
\nNational Clinical Reminders content updates: Airborne hazard templates.\n\n\n
\nNational Clinical Reminders content updates, Mental Health dialogs\nincrement 3.\n\n\n
\nNational Clinical Reminders content update Veteran's Choice Note.\n\n\n\n
\nNational Clinical Reminders content updates: Lung oncology templates.\n\n\n
\nNational Clinical Reminders content update of national taxonomies.\n\n\n
\nNational Clinical Reminders content update Pneumococcal reminders.\n\n\n
\nNational Clinical Reminders content update Advance Directive.\n\n\n
\nNational Clinical Reminders content updates: VA-TERATOGENIC MEDICATIONS\nORDER CHECKS (UPDATE #2 PXRM*2*51)\n\n\n
\nNational Clinical Reminders content update: Hepatitis C.\n\n\n
\nMyHealtheVet National Clinical Reminders\n\n
\nNational Clinical Reminders content updates: MST screening.\n\n\n
\nNational Clinical Reminders taxonomy update, increment 2.\n\n\n
\nClinical Reminders Dialog Search Report.\n\n
\nNational Clinical Reminders content updates: Caregiver templates.\n\n\n\n
\nNational Clinical Reminders Telederm templates.\n\n\n
\nSelectable Immunizations\n\n
\nTDAP/Zoster/PNEUMO Reminder Updates\n\n\n
\nThis patch is in support of the Mental Health PCL-5 instrument patch. It \nThe following clinical reminder items are updated to use PCL-5 as a\nfinding instead of PCLC:\n \n VA-PTSD REASSESSMENT (PCL) reminder definition\n \n VA-MH CPT ASSESSMENT GROUP dialog group\n VA-MH PEI ASSESSMENT GP dialog group\n \n VA-PTSD EVALUATION (PCL) reminder dialog\n VA-PTSD SCREENING reminder dialog\nwill modify nationally released clinical reminders and reminder dialogs \n \nThe effects of updating the dialog groups will be seen in the VA-MH CPT* \nand the VA-MH PEI* reminder dialogs. They will open the PCL-5 instrument \nnow instead of the PCLC instrument.\n \n \nPatch Components:\n-----------------\n \nFiles & Fields Associated: N/A\nto use the PCL-5 instrument instead of the previously used PCLC \n \nForms Associated: N/A\n \nMail Groups Associated: N/A\n \nOptions Associated: N/A\n \nProtocols Associated: N/A\n \nSecurity Keys Associated: N/A\ninstrument. The PCLC and PCLM instruments are inactivated with the \n \nTemplates Associated: N/A\n \n \nNew Service Requests (NSRs):\n----------------------------\nNSR #20150509: Posttraumatic Stress Disorder (PTSD) Checklist 5 (PCL-5) \nand Mental Health Assistant Stabilization (MHAS) \n \nPatient Safety Issues (PSIs):\nassociated mental health patch.\n-----------------------------\nN/A\n \nRemedy Ticket(s) & Overview:\n----------------------------\nN/A\n \nTest Sites:\n----------\nTBD\n \n \n \nDocumentation Retrieval Instructions:\n------------------------------------- \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n \n \nPatch Installation:\n Please refer to the information contained in the Mental Health patch\n------------------\n \n Instructions for installation of the software are included in the \n Mental Health PCL-5 patch YS*5.01*119.\n \nPost-Installation Instructions:\n-------------------------------\n \n See Mental Health PCL-5 patch YS*5.01*119 for post-installation \n instructions.\n for installation instructions.\n \n\n
\nNational Clinical Reminders content updates: VA-LIFE-SUSTAINING TREATEMENT.\n\n\n
\nContains the Reminder Definitions, Dialogs, and associated components to \ncreate the standardized national template set for Home Telehealth (HT).\n\n
\nRemoval of old-style MRD and bug fixes.\n\n\n\n
\nClinical Reminders ICD-10 follow-up build.\n\n\n\n
\nThis patch will:\n - Inactivate MyHealtheVet (MHV) Reminders.\n\n
\nThis patch modifies the Clinical Reminders package to improve monitoring \nof teratogens prescribed or administered to women of childbearing age. \nSpecifically, the software now prompts providers to document a woman's \npregnancy and lacation status when appropriate using reminder dialogs.\n \nPlease see the accompanying patch description for details and the \nComputerized Patient Record System (CPRS) version 31 installation manual \nfor installation instructions.\n\n
\nUpdates for COVID-19 status banner.\n\n\n
\nPrevious diagnosis API.\n\n\n
\nBackup of PXRM*2.0*75 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch address a problem with male radiology reports merging across a \npatients.\n\n
\nThis patch supports PCE standardization.\n \nFor detailed information and installation instructions, please see the PCE\nStandardization 1.0 Installation Guide.\n\n\nTo take full advantage of the PCE standardization work, changes to VistA\napplications that use PCE data are required. These applications include\nClinical Reminders, Health Summary, Problem List, and Order Entry/Results\nReporting. To make it easier for sites, the builds for PCE (PX*1.0*211),\nClinical Reminders (PXRM*2.0*42), Health Summary (GMTS*2.7*122), Problem List\n(GMPL*2.0*53), and Order Entry/Results Reporting (OR*3.0*501) are being\ndistributed in a multi-package build named PCE STANDARDIZATION 1.0.\n\n
\nRelease National VA-TBI SCREENING Reminder and Dialog.\n\n\n\n
\nBackup of PXRM*2.0*77 on Aug 18, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issue:\n \nReminder dialogs which are elements and have a class of "NATIONAL"\nshould not be edited.\n\n
\nAddresses INC21025485,INC21350480\n\n
\nClinical Reminders VIMM changes\n\n\n
\nThis patch addresses some issue with deleting notes that had a sexual \norientation entered on. See the Patch Description for more details\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nPlease see PXRM*2.0*89 on FORUM for a complete description.\n\n
\nNational Skin Risk Assessment Dialogs\n\n
\nIntegration of Clinical Reminders with the new version of the Mental\nHealth package.\n\n\n
\nClinical Reminders version 2.0.\n\n
\nThis patch addresses the appointment blocking for domiciliary patients.\nThe blocking API is modified to treat DOM patients as inpatients. This\npatch also corrects a problem in the Automated MT Report and makes a \nmodification for DCD sites when the letters are initially set up in the\nletter status file.'\n\n
\nThe GMT THRESHOLDS (#712.5) file needs to be updated for the 2018\ncalendar year (income year 2017). \n\n
\nThis patch will enable the ORU~Z10 HL7 message to process when the \nprevious means test on file was a converted means test and the means test \non the ORU~Z10 message is for an income year after the converted means \ntest.\n\n
\nPlease see the EAS*1.0*151 patch description for detailed information \nregarding this patch.\n\n
\nThe Geographic-Based Means Test thresholds for Calendar Year 2019 are\nhttp://www.domain.ext/healthbenefits/cost/income_thresholds.asp\n \nThis patch, EAS*1.0*170, is one of three VistA 2019 threshold patches. It\naddresses the annual updates for the GMT Thresholds. Patch DG*5.3*973 will\nupdate the thresholds for the Means Tests and the Maximum Annual Pension\nRate. Patch IB*2.0*635 will address the annual updates for the Pharmacy\nCopay Thresholds.\ndistributed with this patch. The updated values for the GMT THRESHOLDS\nfile (#712.5) are used in the determination of a veteran's GMT Threshold\nfor a given income year, based on locality and number of dependents.\n \nGeographical income level thresholds are set yearly by the U.S. Department\nof Housing and Urban Development (HUD). This large set of income\nthresholds is usually referred to as the HUD index. The geographic based\nincome limits for Income Year (IY) 2018 can be found January 1, 2019 at:\n\n
\nPlease see the EAS*1.0*174 patch description for detailed information \nregarding this patch.\n\n
\nThe GMT THRESHOLDS (#712.5) file needs to be updated for the 2020 \ncalendar year.\n\n
\nPlease see the EAS*1.0*190 patch description for detailed information \nregarding this patch\n\n
\nThe GMT THRESHOLDS (#712.5) file needs to be updated for the 2021 \ncalendar year.\n\n
\nPlease see the EAS*1.0*203 patch description for detailed information \nregarding this patch.\n\n
\nPatch EAS*1.0*202 addresses an issue where the Military Service Data (MSE)\nscreen is displaying 'Unanswered' when using the Edit an Existing LTC\nCopayment Test [EASEC LTC COPAY TEST EDIT] option.\n\n
\nAnnual updates for the GMT Thresholds are needed for calendar year 2022 \n(income year 2021).\n\n
\nAnnual updates for the GMT Thresholds are needed for calendar year 2023 \n(income year 2022).\n\n
\nPlease see the EAS*1.0*222 patch description for detailed information \nregarding this patch.\n\n
\nAnnual updates for the GMT Thresholds are needed for calendar year 2024\n(income year 2023).\n\n
\nAnnual updates for the GMT Thresholds are needed for calendar year 2025\n(income year 2024).\n\n
\nThis patch addresses a fix for flagging 0-day letters and correcting the \nnewing of the "VAROOT" variable to correct an interaction with older DG \nroutines.\n \nThis patch addresses the following NOIS's"\nSLC-0502-51019\nBAC-0502-41276\n\n
\nSee national patch module for detailed description.\n\n
\nThis patch distributes several enhancements to the EAS MT means test \nletters and appointment blocking application as required by the Rossio 22 \nreport and the subsequent VA Directive.\n\n
\nSee national patch module for detailed description.\n\n
\nThis build provides an API which provides the correct enrollment date\nas documented in DBIA#3624\n\n
\nThe software for this patch, EAS*1*23 and associated patch, IVM*2*69, are \nincome (that is below the Means Test Threshold) with information obtained \nfrom the Internal Revenue Service (IRS) and Social Security \nAdministration (SSA). \nnot being distributed through the National Patch Module. These patches \nare being distributed as a single KIDS software distribution (host \nfile). This patch contains the informational portion of EAS*1*23 and \nprovides field personnel with instructions on how to acquire, install and \nimplement the patch software.\n \nThe Health Eligibility Center (HEC) has reinstated the Income \nVerification Matching program, which matches a veteran's self-reported \n\n
\nADDITIONAL ENHANCEMENTS REQUIRED TO HANDLE SENDING AND RECEIVING OF OTHER\nHL7 MESSAGES BASED UPON RECEIPT OF A Z06 MESSAGE.\n\n
\nEMERGENCY FIX FOR Z09 MESSAGES. DETERMINE WHICH Z09 MESSAGES GO TO HEC\nLEGACY AND WHICH ONES GO TO EDB.\n\n
\nCORRECTLY DISPLAY THE NEW MT STATUS ON BULLETINS SENT TO THE SITE AFTER A\nMT EDB Z06 HAS BEEN RECEIVED.\n\n
\nLTC Copayments Phase III\n\n
\nThe View Patient Address [EAS VIEW PATIENT ADDRESS] menu option will \n \nIn the situation where the user queues the output either by entering a \n"Q" at the device prompt, or the selected device has the QUEUEING Field \n(#5.5) set to "FORCED" in the DEVICE File (#3.5), when the USE command is \ninvoked, the DEVICE has not yet been opened by the process because it's \nbeen queued for a later time. The error results due to the device not \nyet being available. \nallow a user to display the Patient's address along with Address Change \nDate, Address Change Source, and Address Change Site (if applicable) \ninformation. This option calls the EASAILK1 routine, which does a lookup \non the patient file, then, calls the standard device API (%ZIS) to open \nthe selected output device to output the information to. This error is \noccurring because immediately after calling the device API (%ZIS), the \nroutine invokes the USE command to open the device to begin sending \noutput to it. \n\n
\nLong Term Care Copayments Phase IV\n\n
\nFix Z09 issue pertaining to Income Year for multiple years.\n\n
\nSDC-1003-60902\nupdate the LINK TO FILE #2 field (#3.4) in the 1010EZ HOLDING File \n(#712). Since this field is a pointer to the PATIENT File, when it's \nupdated, FileMan calls the patient lookup, DPTLK, to validate the patient \nDFN being passed in. The patient lookup checks a series of \ncross-references on the patient file, one of which is the "SSN" \ncross-reference. When the DFN being checked matches the initial portion \nof a SSN uniquely, the IEN of this matching SSN is returned and stored as \nthe pointer to the PATIENT File instead of the correct IEN.\n \n \nATG-0803-32133\nDAY-0500-42574\n \nThe site reported a problem when trying to print the DGRPT 10-10T \nREGISTRATION to a slave device. They get an Invalid Output Device error \nand no forms print out. This error is caused by the %ZIS variable being\nset to Forced Queuing when calling the device entry.\n \nUnder certain conditions, when a user creates a new link a between a new \nweb based 1010EZ application in the 1010EZ HOLDING File (#712) and the \nPATIENT File (#2) using the menu protocol Link to Patient File [EAS EZ \nLINK TO FILE 2] of the Electronic 10-10EZ Processing [EAS EZ 1010EZ \nPROCESSING] List Manager application, the incorrect patient is selected \nand displayed. This is caused by the FileMan DIE call which is used to \n\n
\nThis build contains 1 routine to fix an undefined variable while \nuploading a Delete Z06 from the EDB.\n\n
\nAdd ability to process IVM close case/converted Pharmacy Exemption Income\ntests via Z06 transmissions from the EDB.\n\n
\n1010EZ Phase 2.5 enhancements.\n\n
\n1010 EZ Phase 3.0\n\n
\nFIX EAS MT APPT EXPIRATION RPT\n\n
\nEAS part of PFSS.\n\n
\nFix Z06 Delete Logic\n\n
\nUpdate Radiation Exposure Method EAS\n\n
\nThis patch contain routines that have been modified\nto call the Scheduling Encapsulation API SDAPI^SDAMA301\ninstead of referencing the global for appointment data retrieval. \nThis patch also addresses the error handling when an error occurs.\n\n
\nREPRINT 60 DAY LETTERS PRINTING NON-USER ENROLLEES\n\n
\nUSE ADMISSION DATE IN CALCULATED LTC COPAYMENTS REPORT\n\n
\nPlease refer to the National Patch Module for a description\nof the changes included in this patch.\n\n
\nMEANS TEST - EVC RELEASE 2\n\n
\nThis patch fixes a subscript error that is encountered when printing the\n1010EZ. It also fixes a prompt to look for a Y instead of a YES.\nThis patch adds code to ask the user if the patient is the correct patient \nwhen processing the 1010EZ from the web. If not, the code\nwill allow the patient with the same name to be added if entered in\ndouble quotation marks.\nThis patch also removes the word "Enclosure" from the 0 and 30 day\nMeans Test letters.\n\n
\n2010 GMT THRESHOLDS UPDATE\n\n
\nFixes errors reported by ^XINDEX utility due to LOCK commands withou \ntimeouts\n\n
\nThis patch a problem where users are experiencing a COMMAND system error\nwhen working with Long Term Care (LTC) means tests.\n\n
\n \n\n
\nThis patch will fix issues that were caused due to patch EAS*1.0*81 \nfor the 1010EZ web application.\nAlso, the statement "A monthly amount can be entered\nwith an '*' after it." is taken out of the double\nquestion mark help text for ALL OTHER INCOME\nfield (.17) of file INDIVIDUAL ANNUAL INCOME (408.21).\nThis patch also fixes the correct filing of the relation of the child\nif the child is a step son or daughter.\n\n
\nThis patch corrects a <STORE> error inadverdently introduced by an IB\npatch with the collection of eIV Eligibility/Benefit data from third\nparties. A call in the 10-10 Print option can potentially trigger the\n<STORE> error if there are an inordinate number of these eIV Eligibility/\nBenefit entries. This patch adjusts the original call to reduce the \ndata collection and size of the local parameter being created.\n\n
\n1010EZ changes for the Military Service Data Sharing (MSDS) project.\n\n
\nThis patch addresses the issue that the Calculated LTC Copayments \nPrint report [EASEC LTC COPAY PRINT], can in certain circumstances \nprovide estimates that are different from what the actual billing option \nLTC Billing Clock [IBAEC LTC CLOCK INQURIY] generates. A disclaimer has \nbeen inserted stating that the Calculated LTC Copayments Print report \nprovides projected estimates.\n\n
\nThis patch contains VistA changes to support technology and\nbusiness changes that are occurring with the implementation of \nDiscontinue Annual Means Test Renewal.\n\n
\nThis patch is in response to Item #22 in the Rossio Report. In the area\nSystems (EAS) software of locally implemented software that has been\nconverted from Class III to Class I.\nof Means Test (MT) Deficiencies, Item #22 required that the Veterans\nHealth Administration (VHA) identify best practices for means testing and\nacquiring veterans' signatures at the local level and explore the\npromulgation of these best practices throughout the system. In response\nto the Report, the Enrollment Task Force requested implementation on a\nnational basis of local sites' initiative s developed to manage scheduling\nactivities for veterans who require the completion of a means test. This\npatch will provide a national patch release to the Enrollment Application\n\n
\nThis patch addresses the following:\n \n- Updates the Executable Help Text for ALL OTHER INCOME (#.17) in the \n INDIVIDUAL ANNUAL INCOME (#408.21) file.\n\n
\nEnrollment System Redesign (ESR) became the official System \nof Record on March 29, 2009. The Health Eligibility Center Legacy (HECL)\nsystem will be decommissioned. This patch will inactivate the HL7\nprotocols used for messaging with the HECL and will be installed shortly\nbefore the HECL is decommissioned.\n\n
\nThe Geographic-Based Means Test thresholds for Calendar Year 2015 are\ndistributed with this patch. The updated values for the GMT THRESHOLDS\nfile (#712.5) are used in the determination of a veteran's GMT Threshold\nfor a given income year, based on locality and number of dependents.\n\n
\nVFA ESR 3.12 Receive Conversion/Reversal Tests from ES Project.\n\n
\n The Health Eligibility Center (HEC) requested modifications to the \n ----------------------------------------------------------\n Due to the Income Verification Match (IVM) process, the BT CLAIMS\n PROCESSING Mailgroup will be automatically created in VistA with the\n installation of this patch at each VistA Site. VistA users are\n responsible for adding the appropriate members to the Mailgroup. The\n appropriate VistA staff are added to the Mailgroup when they want to be\n notified of a change in the Veteran's BT Financial Indicator status.\n The bulletin that will be loaded with this patch is called EAS BT CLAIMS\n PROCESSING.\n \n Enrollment System (ES) and VistA Registration, Enrollment and\n The bulletin will be sent to each member of the Mailgroup and will\n contain the following information:\n \n Mail Message From: Health EligibilityCenter Date: MM/DD/YYYY HH:MM\n Subject: IVM-Beneficiary Travel Financial Indicator upload FOR<DFN>\n \n An Income Verification Match verified Beneficiary Travel information\n has been uploaded for the following patient.\n \n Patient Name:\n Eligibility (VistA REE) software to support the requirements of the\n LAST 4 OF SSN: \n ICN:\n DFN:\n STATION NUMBER:\n Prev Category:\n New Category:\n Date of Test:\n Income Year of Conversion:\n \n - When a converted/reversal Rx Copay Test is received from IVM, a\n Veterans Financial Assessment (VFA) projects.\n check will be done to see if the new copay exemption status is\n different than the old copay exemption status (e.g. the new status is\n NON-EXEMPT and the old status is EXEMPT, or the new status is EXEMPT\n and the old status is NON-EXEMPT).\n - If the status has changed, a check will be done to see if the \n Beneficiary Travel indicator has changed. If indicator changed, a\n a bulletin will be sent to the BT CLAIMS PROCESSING Mailgroup.\n \n HL7 Changes\n ----------------------------------------------------------\n \n This patch supports HL7 enhancements that sends BT Financial Indicator \n Z06 ZMT-32 and Contributed to Spouse Z10 ZIR-2 and stores them in the \n database. Supports HL7 Z07 ZIR-15 that sends VistA Contributed to Spouse\n changes to ES. Patch DG*5.3*890 will be released in conjunction with\n this EAS patch.\n Modified Z07 message builder to include the Contributed to Spouse \n indicator on the ORU Z07 ZIR segment.\n Added a trigger for an ORF Z07 message when a change is made to \n the Contributed to Spouse indicator.\n This patch modifies the Enrollment Application System V1.0 application\n as described below:\n \n Add a Beneficiary Travel Bulletin.\n\n
\nThe Geographic-Based Means Test thresholds for Calendar Year 2016 are \ndistributed with this patch. The updated values for the GMT THRESHOLDS \nfile (712.5) are used in the determination of a veteran's GMT Threshold \nfor a given income year, based on locality and number of dependents.\n\n
\nPatch EAS*1*122 addresses 1 issue:\n \n 1. When using the Integrated Billing LTC Billing Clock\n Maintenance [IBAEC LTC CLOCK EDIT] menu option\n and after entering "?" or "??" at the "Select PATIENT\n Name" prompt users might encounter an undefined error.\n\n
\nThe Geographic-Based Means Test thresholds for Calendar Year 2017 are \ndistributed with this patch. The updated values for the GMT THRESHOLDS \nfile (712.5) are used in the determination of a veteran's GMT Threshold \nfor a given income year, based on locality and number of dependents.\n\n
\nThis patch corrects the Geographic-Based Means Test thresholds for \nincome limits for Income Year (IY) 2016 can be found January 1, 2017 at:\nhttps://www.huduser.gov/portal/datasets/il.html#2016\nCalendar Year 2017 previously sent in patch EAS*1.0*144. The updated\nvalues for the GMT THRESHOLDS file (#712.5) are used in the determination\nof a veteran's GMT Threshold for a given income year, based on locality\nand number of dependents.\n \nGeographical income level thresholds are set yearly by the U.S. Department\nof Housing and Urban Development (HUD). This large set of income\nthresholds is usually referred to as the HUD index. The geographic based\n\n
\nENROLLMENT APPLICATION SYSTEM v1.0\n\n
\nA site reported a problem where a one-time order could not be discontinued\nsystem parameter is not defined, the system will use the continuous order\nparameters to determine the stop date, rather than the start and stop date\nbeing equal. Then, when BCMA marks the medication as 'Given', Inpatient\nMedications will expire the order. NOIS# BUT-0501-20609\nby the provider because it was expired due to the start and stop date\nbeing the same. However, the medication still displayed in Bar Code\nMedication Administration (BCMA) V. 1.0 because of the 12-hour rule for\ndisplaying one-time orders on the Virtual Due List. This patch corrects\nthis problem by changing the way the stop date for one-time orders is\ncalculated. There will be a ward parameter, system parameter and the\nstandard calculation. The hierarchy will be to check the one-time ward\nparameter first, if not defined, check the system parameter. If the\n\n
\nCM Tools package version 1.0\n\n
\nPatch KMPD*2.0*1 for Capacity Management Tools\n\n
\nPatch KMPD*2*2 for Capacity Management Tools\n\n
\nPatch KMPD*2*3\n\n
\nPatch KMPD*2*4\n\n
\nPatch KMPD*2*6\n\n
\nCM Tools 2.0\n\n
\nIncludes fixes and upgrades to CPRS Coversheet Load functionality.\n\n
\nPatch corrects mistyped calling routine when queuing report in option \n \nI '$D(ZTRTN) S DGPGM=$S($D(DGPGM):DGPGM,$D(PGM):PGM,1:"") G:DGPGM="" CLO \nSE S ZTRTN="DQ^DGBTUTQ"\n'Standard Claims Output' in menu REPORT OF CLAIM AMOUNTS.\n \nQUE+2^DGBTUTQ (old)\n \nI '$D(ZTRTN) S DGPGM=$S($D(DGPGM):DGPGM,$D(PGM):PGM,1:"") G:DGPGM="" CLO \nSE S ZTRTN="DQ^DGJUTQ" \n \nQUE+2^DGBTUTQ (new)\n\n
\nThis patch contain routines that have been modified\nto call the Scheduling Encapsulation API SDAPI^SDAMA301\ninstead of referencing the global for appointment data retrieval. \nThis patch also addresses the error handling when an error occurs.\n\n
\n \nThis patch removes the ability to edit Beneficiary Travel\nreimbursement rates and inserts the 02/01/2008 rates into\nthe MAS EVENT RATES (#43.1) file.\n\n
\nTHIS PATCH WILL INSERT THE 11/17/2008 RATES INTO THE MAS EVENT RATES \n(43.1) FILE\n\n
\nUpdate Beneficiary Travel Deductible Rates\n\n
\nThis patch addresses these issues:\n- updates the DD in the Beneficiary Travel Claim File (#392) to meet \nVA SAC in regards to $NEXT commands.\n- Prints the second line of an address in the VA 70-3542d form\n- Corrects the calculations used to find the default mileage value.\n- Allows a lowercase "p" to print the VA 70-3542d form.\n\n
\nBeneficiary Travel Dashboard\n\n
\nContains enhancements for Beneficiary Travel Package and \nMileage Reporting System.\n\n
\nThis patch addresses 4 issues:\n \n 3. The CBO has requested that the Default Mileage be removed when using\n the Claim Enter/Edit [DGBT BENE TRAVEL SCREEN] option.\n \n 4. When using the View of Claim [DGBT BENE TRAVEL VIEW] option, the \n "Auth. Person" will change to whoever is printing the report.\n \n 1. A subscript error occurs when printing the "Standard Claims Output"\n report from the Report of Claim Amounts [DGBT BENE TRAVEL REPORT] \n option.\n \n 2. Entry cannot be processed since the seconds portion of the Claim\n DATE/TIME (#.(#.01) field of the BENEFICIARY TRAVEL CLAIM (#392) \n file is equal to 60. \n\n
\nThis patch provides Beneficiary Travel with the interface capabilities to\n \nA new field is added to the Parameter Rates Enter/Edit option that will be\nused to activate the coreFLS interface:\n \nCOREFLS ACTIVE:?\n Enter 'Yes' if using the coreFLS system for vendors.\n Choose from: \n 1 YES\n 0 NO\n \nthe Core Financial Logististics System (coreFLS). coreFLS will replace\nTechnical information.\n----------------------\nMajority of coding enhancements are done in the DR strings of the DIE\ncall. Each DR string calls a new routine, DGBTCLS. When a prompt for\nCOREFLS VENDOR is given an Output Tranform will set up a variable for its\nprevious entry. If a response is given at the vendor prompt no Query to\ncoreFLS is given. If the previous entry is the same as the current\nresponse (including a <return>) the Query to coreFLS is given. Reason for\nthis is: New entries through Fileman to the local vendor file, LOCAL\nVENDOR (#392.31) is forbidden (no LAYGO). Adding new entries is done\nthe Integrated Funds Distribution, Control Point Activity, and Procurement\nonly by querying and accepting a vendor through coreFLS. Due to the local\nfile being no LAYGO and adding vendors is done through a different file\ninterface, the rule of querying coreFLS if the current and previous\nentries are the same is used. Example of this is: User is prompted for\ncoreFLS Vendor and enters a name not found in the local vendor file, the\nresponse is ??, the user must hit the <return> key to pass through. At\nthis time previous and current values of vendor are the same, so the\nprompt to Query coreFLS is given. Only draw back is getting the prompt\nwhen user is in edit mode and gets the Query coreFLS prompt when hitting\n<return> through accepted reponses.\n(IFCAP) package.\n \nView the DR strings to display executed calls.\n \n \nNew Fields added with Output Transforms\n---------------------------------------\nFile: BENEFICIARY TRAVEL CLAIM (#392)\n New Fields added: COREFLS CARRIER (#14)\n Output Transform: K DGBTPRV S DGBTPRV=$$PREV^DGBTCLS(.Y)\n \n \nFile: MAS PARAMETERS (#43)\n New Fields added: COREFLS ACTIVE (#723)\n \nOptions effected.\n-----------------\nParameter Rates Enter/Edit\nEnter a Claim\nEdit a Claim\nDisplay a Claim\nStandard Claims Output (by Carrier)\nVendor information for coreFLS will be remotely held on a national\n \nNew menus added.\n----------------\nAdd a local vendor (COREFLS)\nUpdate Local Vendor (COREFLS)\n \nNew Security key\n----------------\nDGBT LOCAL VENDOR\n \ndatabase. To aliviate traffic over a network system, a local vendor file,\nNew Fields added with Output Transforms\n---------------------------------------\nFile: BENEFICIARY TRAVEL CLAIM (#392)\n New Fields added: COREFLS CARRIER (#14)\n Output Transform: K DGBTPRV S DGBTPRV=$$PREV^DGBTCSL(.Y)\n \nFile: MAS PARAMETERS (#43)\n New Fields added: COREFLS ACTIVE (#723)\nLOCAL VENDOR (#392.31) will be accessed to retrieve frequently used\nvendors.\n\n
\nModifications to the Beneficiary Travel Claims screen<1> for Veterans\nFinancial Assesment discontinuation of Means Test Expirations.\n\n
\nThis patch addresses five issues:\n when entering claims.\n \n4. A subscript error occurs when using the View of Claim \n [DGBT BENE TRAVEL VIEW] option.\n \n5. Users are being returned to the Beneficiary Travel Menu [DGBT BENE \n TRAVEL MENU] after completing a claim.\n \n1. After the release of patch DGBT*1.0*20, it is possible to \n inadvertently modify the Division of existing claims.\n \n2. Special Mode claims are being rejected, with a generic "DATA DID \n NOT FILE DUE TO ERRORS" message.\n \n3. Users are reporting getting an <UNDEFINED>COMPLT+3^DGBTE *% error \n\n
\nThis patch addresses 6 issues:\n Mode claim.\n \n 4. The departure and destination information is missing.\n \n 5. Special Mode accounts are not being selected correctly.\n \n 6. The proper Division is not being retained when editing the denial \n letter.\n \n 1. Beneficiary Travel is not correctly calculating the total monthly \n deductible.\n \n 2. The WHO ENTERED INTO FILE (#12) and DATE ENTERED INTO THE FILE \n (#13) fields of the BENEFICIARY TRAVEL CLAIM (#392) file are blank.\n \n 3. A correction is needed for the help text when entering a Special \n\n
\n This patch addresses 7 issues:\n \n 4. There is duplicate wording in the denial letter template.\n \n 5. Special Mode claims are incorrectly displaying 'One Way' every \n time.\n \n 6. An undefined error occurs when there is single division.\n \n 7. Existing claims are being erased.\n \n 1. The Report Of Claim Amounts report is not displaying values for \n Special Mode claims.\n \n 2. The Bene Travel software is incorrectly displaying 9 digit zip \n codes.\n \n 3. The denial letter is not printing the correct user name.\n\n
\nThis patch addresses 2 issues:\n \n 1. Bene Travel is incorrectly granting deductible waivers.\n \n 2. Claim deductibles are being modified after payment.\n\n
\nThis patch addresses 3 issues:\n \n 1. The mileage fee cap is too low.\n \n 2. The Beneficiary Travel denial letter template is incorrect.\n \n 3. The Beneficiary Travel application is running slow. \n\n
\nPatch DGBT*1*34 will address the following 2 issues:\n \n 1. Denial Letter is printing the wrong Division\n \n 2. The Claim Enter/Edit option is freezing/slow\n\n
\n 1. Beneficiary Travel (BT) Error <UNDEFINED>MANRQ+11^DGBTRDVW *DGBTA is \n occurring at many R4 sites.\n\n
\nDGBT*1.0*35 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\nPlease refer to patch description on FORUM for installation purposes.\n\n
\n1. Correct 'BB' key index, then re-index cross reference.\n \n2. Edit changes to the new 'BB' cross reference in routines; DGBTCSL and\n DGBTVUP.\n\n
\nThis patch will update the Beneficiary Travel (BT) Package to utilize the \nnew Residential Address components introduced with patch DG*5.3*941.\n\n
\nThis patch will disable the Mileage claim related functionality\nwithin the Beneficiary Travel package.\n\n
\nDGBT*1.0*41 is a decommission patch for the special mode processing \nportion of the Beneficiary Travel (BT) application. This patch will \nremove the use of several options. \n\n
\nThis patch removes the [DGBT LOCAL VENDOR ADD] Add a local vendor \n(COREFLS) and [DGBT LOCAL VENDOR UPDATE] Update a local vendor (COREFLS) \nfrom the [DGBT BENE TRAVEL MENU] Beneficiary Travel Menu.\n \nIt add a new menu option [DGBT LOCAL VENDOR MENU] Local Vendor (Task) \nMenu with options [DGBT LOCAL VENDOR ADD] Add a local vendor (COREFLS) \nand [DGBT LOCAL VENDOR UPDATE] Update a local vendor (COREFLS).\n\n
\nThis patch corrects the COMMA+3^%DTC:2, %DSM-E-STRLEN generated in the \nSTANDARD CLAIMS OUTPUT REPORT caused by leftover variable X3 from other \noptions.\n\n
\nLocal Vendor (Task) Menu [DGBT LOCAL VENDOR MENU] will be renamed Local \nVendor Menu (COREFLS) [DGBT LOCAL VENDOR MENU] and added to the \nBeneficiary Travel Menu [DGBT BENE TRAVEL MENU]. The key DGBT LOCAL \nVENDOR will be added to the Local Vendor Menu (COREFLS) [DGBT LOCAL \nVENDOR \nMENU].\n\n
\nCorrect DGBT calls to COMMA^%DTC to confirm that the variable X3 used\nis a clean copy.\n\n
\nDisable Corefls/Reversion back to VistA software ONLY.\n\n
\nBeneficiary Travel v1.0. Breakout of Beneficiary Travel (DGBT) from\nRegistration (DG) v5.3.\n\n
\nThis patch provides Incomplete Records Tracking with the interface\n \nA new menu is added to your Incomplete Records Tracking Menu. This menu\ncalled, Add a local vendor (COREFLS), will allow users holding the DGJ\nLOCAL VENDOR key the ability to add CoreFLS vendors to the LOCAL VENDOR\nfile (#392.31). This menu will verify the existence of the CoreFLS \npackage before allowing the user to proceed with the CoreFLS vendor query.\n \nA Variable Pointer is added to the TRANSCRIBED BY field (#10.04) allowing \na user to choose a CoreFLS vendor from the LOCAL VENDOR fie (#392.31). \nUsers will not be allowed to add vendors (LAYGO) at this field into the \ncapabilities to the Core Financial Logistics System (CoreFLS). CoreFLS\nLOCAL VENDOR file, similar to accessing a vendor from the VENDOR file\n(#440). Users can only add CoreFLS vendors through the above mentioned\n'Add a local vendor (COREFLS)' holding the DGJ LOCAL VENDOR key.\n \nOptions effected.\n-----------------\nEnter/Edit an IRT\n \nNew menus added.\n----------------\nwill replace the Integrated Funds Distribution, Control Point Activity,\nAdd a local vendor (COREFLS)\n \nNew Security key\n----------------\n DGJ LOCAL VENDOR\nand Procurement (IFCAP) package.\n \nVendor information for CoreFLS will be held nationally on a remote\ndatabase. To alleviate traffic over your network, a local vendor file,\nLOCAL VENDOR (#392.31) has been placed on your local system to be used to\nstore and access your frequently use vendors.\n\n
\nDBIA #4376. Correct DD node of the TRANSCRIBED BY field in the \nINCOMPLETE RECORDS file.\n\n
\nDISABLE COREFLS SOFTWARE. Remove variable pointer to #392.31 in \nTRANSCRIBED BY (#10.04) Field of #393.\n\n
\nBreakout of Incomplete Records Tracking (DGJ 1.0) package from the\nRegistration namespace (DG).\n\n
\nThis patch fixes various problems discovered during the installation and\nimplementation of the Clinical Case Registries v1.0 package. It also\ncontains some enhancements.\n\n
\nThis build contains modifications required by the new Race & Ethnicity \ndata model.\n\n
\nThis build fixes the code that causes very long execution of the nightly\ndata extraction process and a couple of other data extraction problems.\n\n
\nThis build introduces Immunology Case Registry v3.0 and several fixes for \nthe the Clinical Case Registries.\n\n
\nUpdates for the Code Text Descriptors project.\n\n
\nThis patch fixes problems discovered during the implementation of the\nImmunology Case Registry in the Clinical Case Registries framework.\n\n
\nImmunology Case (ICR) and Hepatitis C (Hep C) registries historical data\nextraction and HL7 context management (CCOW).\n\n
\nThe Clinical Case Registry package automatically collects and creates\nLocal sites have the ability to review the local registry list before\nautomated data extraction and transmission. Data extraction and\ntransmission will be timed daily and will not require manual intervention.\nlocal registries of patients using the predefined search criteria.\n \nThis release contains the infrastructure and definitions of the Hepatitis\nC registry. The software will search for patients that pass the\npre-defined selection rules that identify a patient with Hepatitis C\n(e.g., ICD-9 code relating to Hepatitis C, positive laboratory serology\ntest results for Hepatitis C testing).\n \n\n
\nPost-implementation enhancements for the Clinical Case Registries v1.5\npackage.\n\n
\nClinical Case Registries patch ROR*1.5*10. See Patch Description for\ndetails.\n\n
\nADD SUBSCRIPT TO VARIABLE FOR LAB API CALL\n\n
\nCORRECTION TO FIB-4 CALCULATION (LIVER SCORE)\n\n
\nThis build fixes several Clinical Case Registries problems and implements \nseveral enhancements.\n\n
\nBuild for ICD-10 Class 1 Remediation\n\n
\nEnhancements to Clinical Case Registries to include new SLEEP APNEA \nregistry and report enhancements for screen on gender and addition of \noptional ICN column.\n\n
\nUpdates for ICD-10 for local registries, add additional data element\nOEF/OIF/OND period of service for selection of patients, notify mail group\nif nightly job does not run due to user not possessing the ROR VA IRM\nsecurity key and add 2 new HEP-C registry drugs.\n\n
\nPatch reference and additional information may be found on Forum for \nROR*1.5*24\n\n
\nEnhancements to Clinical Case Registries to include new registries\nand report enhancements.\n\n
\nUpdates to support ICD-10 for PTF's increase in the number of ICD-10\ncodes to 25.\n\n
\nPatch reference and additional information may be found on Forum for \nROR*1.5*26\n\n
\nPatch reference and additional information may be found on Forum for \npatch ROR*1.5*28\n\n
\nThis patch contains changes to the following:\n \n1. A new Selection Panel on each report to allow the user to limit \nthe report to patients with a diagnosis of interest in a date range. \n \n2. Two new reports Hep A and Hep B are included in this patch. \n\n
\nADD HEP C ICD9-CODES 070.70 AND 070.71 TO PATIENT SEARCH\n\n
\nInclude two New Registries: \nDRUG file (#799.51) as a NATIONAL entry for use in the CCR VA HEPC \nRegistry.\n \nAdded code to change the LOINC Codes result values to uppercase as \npositive values were being missed if the site used mixed case to store a \npositive result. \n \nUpdate Labels to Reference "Birth\nSex" on all Report Panels\nThe existing "Sex" labels on all report panels will be changed to "Birth \n VA IPF - Idiopathic Pulmonary Fibrosis (IPF) Registry\nSex." In addition, the change will be implemented under Report Options \nin the General Utilization and Demographics Report Selection Panel. As \nthis list is alphabetized, the order will change to maintain alphabetical \norder. \n VA HYPOPARA - Hypoparathyroidism Registry\n \nThe following medications will be added to the ROR GENERIC DRUG File \n(#799.51):\n Add HEPC Registry Medication SOFOSBUVIR/VELPATASVIR\n \nThe medication, SOFOSBUVIR/VELPATASVIR, will be added to the ROR GENERIC\n\n
\nThe description of this build can be found in the National Patch Module \nunder ROR*1.5*31.\n\n
\nPatch reference and additional information may be found on Forum for \nROR*1.5*32.\n\n
\n1. Six new local registries added\n LAMIVUDINE/ TDF\n \n 3. A new Future Appointment selection paneladded to selected reports\n 4. The new panel will have a radio button with a label \n "All Patients" which will be the default. A second button\n with a label "Only patients with an appointment in the\n next X days".\n \n5. On the report header for reports that display "Only patients with\n appointment in the X number of days", new text will be displayed as\n2. Three new medications are added to the ROR GENERIC DRUG file\n follows to et the user know that the report was run for future \n appointments only.\n \n6. New LOINC codes have been added to the ROR LAB SEARCH file (#798.9) \n to add patients to the HIV pending list.\n7. A correction was made on the Combined Meds and Labs, \n DAA Lab Monitoring, Hepatitis A and the Hepatitis B\n reports when sorting by the ICN, PACT or PCP columns. \n \n 8. The version of the CCR software has been updated \n (#799.51) to be used as inclusion criteria for patients in the\n respective registry(s).\n a. HIV registry : \n BICTEGRAVIR/EMTRICITABINE/TENOFOVIR\n \n EFAVIRENZ/LAMIVUDINE/TENOFOVIR\n \n\n
\nThe following functionality is included in this patch.\n \nCurrent Inpatient report with admission date time for diagnosis.\n \nAll reports with future appointments listed will include the future \nclinic also.\n \nFix Hep A/B LOINC code table.\nAdd Future Appointment panel to the Diagnosis and Procedure reports\n\n
\nTwo new local registries will be added to this patch. VA HEAD AND NECK \nA conversion included in the post-init to set the status from pending to \nconfirmed for all HEPC and HIV records in the registries. Also pending \ncomments will be deleted out.\nand VA HYPOTHYROIDISM.\nThe AUTO CONFIRM field of the ROR REGISTRY PARAMETERS (798.1) will be \nset to Yes to auto confirm for the two national registries VA HEPC and VA \nHIV.\nAll code pertaining to pending in the two national registries VA HEPC and \nVA HIV will be documented in the code as pending but will be commented as \nsuch.\nA new HIV drug will be added to the file.\n\n
\nCreate and populate the VA COVID19 registry.\n\n
\nThis patch adds a new registry called VA RECENT PATIENTS that adds \npatients that have had an admission or an event within the last two \nyears. The nightly job ROR TASK when runs will set those entries in the \nVA RECENT PATIENTS registy to a status of delete (5) if the entry has not \nhad activity within the last two years. Also 34 new LOINC\ncodes have been added to the ROR LAB SEARCH file for the VA COVID19 \nregistry.\n\n
\nThe Clinical Case Registries (CCR) identifies patients with positive \nantibody results for inclusion in the HIV and HCV registries. This patch \nfixes an error where patients with laboratory results that are not \npositive are incorrectly categorized as positive and are incorrectly \nincluded in the HIV and HCV registries. Code changes have been made to the\nRORUPD04 and RORX024A routines to rectify this issue.\n \nA revised Graphical User Interface (GUI) executable is included in the\npatch so the version of the CCR software is updated to 1.5.38.\n\n
\n \nRoutines changed to eliminate the SSN number from display.\nDIALOG changes for SSN.\n\n
\nCORRECT MISSING OUTPATIENT PROCEDURES AND ADD MEDICATIONS TO ROR DRUG FILE\n\n
\nTwo drugs are added to the ROR GENERIC DRUG (#799.51) file for use by the\nVA HIV registry. They are; 1)CABOTEGRAVIR and 2)CABOTEGRAVIR/RILPIVIRINE.\n \nThere is a new GUI. The version number is 1.5.40.\n\n
\nThis patch changes the value of the NATIONAL (#.09) field in the ROR \nother registries in the package are considered "local" and their patient \ndata is not transmitted to any other database. \n \nWith this patch, these two registries are changed to "local", too. Their \npatient data will no longer be transmitted to any other database.\n \nThe CCR package checks many VistA packages for patient information to \nupdate its various registries. Therefore, the ROR TASK option that is\ncurrently scheduled to run on all VistA systems should continue to run\nevery day so that all registries at the site can continue to be updated on\nREGISTRY PARAMETERS (#798.1) file for two entries; 1) VA HEPC and\na daily basis.\n \nNOTE: This patch should be installed at sites that run CERNER, too.\n However, CERNER sites do not need to have the ROR TASK option\n scheduled.\n \nThere is a new GUI. The version number is 1.5.41.\n2) VA HIV.\n \nBefore the patch, the value is "1" (i.e., YES). \nAfter the patch, the value is "0" (i.e., NO).\n \nPrior to this patch, these two registries were considered "national" and \ntheir patient data was transmitted to a national database every day. All \n\n
\nThis patch includes the following changes to the Clinical Case Registries\n update this registry. Also, this registry will no longer appear in the\n list of registries displayed to the users so they will not be able to\n select it.\n \n 3. The Graphical User Interface (GUI) now supports the latest changes to\n the RPC Broker package. The latest Personal Identity Verification\n (PIV) certificate will be selected automatically, however, a new\n "/showcerts" command line switch was added to allow the user to\n display the PIV certificate selection screen in case it is needed.\n \n(CCR) package.\n 4. The version of the CCR software is updated to 1.5.42.\n \n \n NOTE: This patch should be installed at sites that run CERNER, too.\n However, CERNER sites do not need to have the ROR TASK option\n scheduled.\n \n 1. One drug is added to the ROR GENERIC DRUG (#799.51) file for use by \n the VA HIV registry. The drug is LENACAPAVIR.\n \n 2. The VA TRANSGENDER registry is inactivated. The REGISTRY STATUS field\n (#11) of the ROR REGISTRY PARAMETERS (#798.1) file for this registry \n is set to 1 (i.e., INACTIVE). The daily update process will no longer\n\n
\nADD RALTEGRAVIR TO THE GENERIC DRUG FILE IN CCR\n\n
\nADD RALTEGRAVIR TO THE GENERIC DRUG FILE IN CCR\n\n
\nThis build fixes several Clinical Case Registries problems.\n\n
\nClinical Case Registries patch ROR*1.5*8. See Patch Description for \ndetails.\n\n
\nAIDS OI CHECKBOX ISSUE\n\n
\nClinical Case Registries (CCR) V1.5 package. \nThis build can be used both for updating the CCR V1.0\nand for a "virgin" installation of the package.\n\n
\nThe Functional Independence Measurement (FIM) consists of a Delphi form \nand associated M routines that provides the ability to enter FIM data \ninto the FSOD database and CPRS progress notes. Data is stored in a \nlocal FileMan database for later transmission to the FSOD database in \nAustin.\n\n
\nVISTA SECURITY REMEDIATION UPDATES FOR FOUR SLASHES\n\n
\nFunctional Independence Measurement (FIM) Graphical User \nInterface (GUI) update for VA Technical Reference Model \n(TRM) compliance\n\n
\nNew version option only\n\n
\nNew version to address issues found in patch 1 (RMIM*1.0*1).\n\n
\nFixes for first time users unable to access GUI, imprecise DOB error, \nand file access issue with RMIM EDIT SITE PARAMETER option. \nAddition of'0-Unspecified' to Admission Class list and change from Rehab \nBed Unit Admission Date/Discharge Date to Therapy Start Date/End Date.\n\n
\nUSER NOT GETTING PROMPTED TO COMPLETE A CONSULT\n\n
\nNew version to address issue found in patch 5 (RMIM*1.0*5)\n\n
\nThis patch corrects problems with the cosigner not receiving notification \nthey need to cosign a report. \n\n
\nThis patch addresses one Functional Independence issue:\n \nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the Functional Independence Measurement (FIM) Graphical\nUser Interface (GUI) requires an upgrade to Delphi version XE8 in order to\nimplement the new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nFIM WINDOWS 10 UPDATES\n\n
\nThe Functional Independence Measurement (FIM) consists of a Delphi form\nand associated M routines that provides the ability to enter FIM data\ninto the FSOD database and CPRS progress notes. Data is stored in a\nlocal FileMan database for later transmission to the FSOD database in\nAustin.\n\n
\nThis build contains common files, libraries, etc. used by all the XOB* \npackages.\n \nIt also contains options, protocols and list templates used to manage \nFoundations site parameters and operations.\n\n
\nThis build contains common files, libraries, etc. used by all the XOB* \npackages.\n \nIt also contains options, protocols and list templates used to manage \nFoundations site parameters and operations.\n \n[Build: 1.5.0.026]\n\n
\nThis build contains common files, libraries, etc. used by all the XOB* \npackages.\n \nIt also contains options, protocols and list templates used to manage \nFoundations site parameters and operations.\n\n
\nContains common files, libraries, etc. used by all the XOB*\npackages. \n \nAlso, contains options, protocols and list templates used to\nmanage Foundations site parameters and operations.\n\n
\nThis build contains the M side software for the Foundations Toolbox.\n \n \nThis build requires that the M XML Parser 1.1 be installed in the account.\n\n
\n This patch will set the RPC Broker variable XWBOS in VistALink routine\n XOBVSKT which is used in TCP/IP socket processes.\n \n Setting this variable is necessary to accomodate remote procedure calls \n that test for this variable directly.\n\n
\nThis build contains TCP/IP transport functionality that enables\nHandler.\n \nThe VISTALINK package contains two native request handlers. One handles \nsystem-type requests, like client heartbeats and close socket requests. \nThe other handler processes RPC requests.\n \nOther packages can also supply handlers. For example, VISTALINK SECURITY\n(XOBS) supplies a handler that is used to process VistA security-related\nrequests.\n \nsynchronous communication from the following:\nVISTALINK allows the following request formats:\n 1) XML and conform to a XML Schema \n 2) a proprietary format (package must supply a proprietary parser)\n 3) both 1 and 2\n \nVISTALINK also supplies a Java/J2EE component that allows developers of\nJava applications to make synchronous requests on the M server and for M\napplications to make synchronous requests of Java/J2EE application\nservers. The Java/J2EE side implements the J2EE Connector Architecture\nv1.0 framework (J2CA).\n 1) from non-M based systems to M-based VistA servers\n \n** NOTE: As of 7/2005, VISTALINK only supports Java to M communication.\n \nFinally, VISTALINK contains a number of library calls available to \nother packages for developing a request handler if needed. (Currently, \nonly VISTALINK SECURITY is allowed to use these calls.)\n 2) from M VistA servers to non-M systems (typically Java/J2EE based\n systems)\n \nThe communications are in the form of requests. For requests received by\nthe M-based system, the VISTALINK package contains a Request Manager to\nmanage these requests. Requests are forwarded to the appropriate Request\n\n
\nFor complete information, see the patch description for patch XOBV*1.5*1\nin the National Patch Module on FORUM.\n\n
\nThis build contains TCP/IP transport functionality that enables\nHandler.\n \nThe VISTALINK package contains two native request handlers. One handles \nsystem-type requests, like client heartbeats and close socket requests. \nThe other handler processes RPC requests.\n \nOther packages can also supply handlers. For example, VISTALINK SECURITY\n(XOBS) supplies a handler that is used to process VistA security-related\nrequests.\n \nsynchronous communication from the following:\nVISTALINK allows the following request formats:\n 1) XML and conform to a XML Schema \n 2) a proprietary format (package must supply a proprietary parser)\n 3) both 1 and 2\n \nVISTALINK also supplies a Java/J2EE component that allows developers of\nJava applications to make synchronous requests on the M server and for M\napplications to make synchronous requests of Java/J2EE application\nservers. The Java/J2EE side implements the J2EE Connector Architecture\nv1.0 framework (J2CA).\n 1) from non-M based systems to M-based VistA servers\n \n** NOTE: VISTALINK v1.5 only supports Java to M communication.\n \nFinally, VISTALINK contains a number of library calls available to \nother packages for developing a request handler if needed. (Currently, \nonly VISTALINK SECURITY is allowed to use these calls.)\n \n[Build: 1.5.0.026]\n 2) from M VistA servers to non-M systems (typically Java/J2EE based\n systems)\n \nThe communications are in the form of requests. For requests received by\nthe M-based system, the VISTALINK package contains a Request Manager to\nmanage these requests. Requests are forwarded to the appropriate Request\n\n
\nAdds a new RPC, XOBV VALIDATE SAML that is used to sign in with a PIV \ncard using 2 Factor Authentication.\n\n
\nThis patch corrects an issue within the VISTALINK package:\n \nVistaLink server errors are not respecting the Kernel's limits for logging\nerrors. \n\n
\n1. Fix Non-Provisioned User Login Problem\n syntax errors when code stored in the $ET and $EC variables executes;\n and a problem of blanks appearing in the error descriptions in the \n error trap due to extrinsic function EZBLD^DIALOG being called\n incorrectly.\n \n When a non-provisioned user fails a login, subsequent attempts result \n in a "Socket timeout has occurred" error, when they should still\n receive the "Error processing login credentials" error.\n \n2. Fix Three Issues in Routine XOBVLL\n \n There are three known issues in routine XOBVLL: two occurrences of\n\n
\nThis build contains TCP/IP transport functionality that enables\nHandler.\n \nThe VISTALINK package contains two native request handlers. One handles \nsystem-type requests, like client heartbeats and close socket requests. \nThe other handler processes RPC requests.\n \nOther packages can also supply handlers. For example, VISTALINK SECURITY\n(XOBS) supplies a handler that is used to process VistA security-related\nrequests.\n \nsynchronous communication from the following:\nVISTALINK allows the following request formats:\n 1) XML and conform to a XML Schema \n 2) a proprietary format (package must supply a proprietary parser)\n 3) both 1 and 2\n \nVISTALINK also supplies a Java/J2EE component that allows developers of\nJava applications to make synchronous requests on the M server and for M\napplications to make synchronous requests of Java/J2EE application\nservers. The Java/J2EE side implements the J2EE Connector Architecture\nv1.0 framework (J2CA).\n 1) from non-M based systems to M-based VistA servers\n \n** NOTE: As of 7/2005, VISTALINK only supports Java to M communication.\n \nFinally, VISTALINK contains a number of library calls available to \nother packages for developing a request handler if needed. (Currently, \nonly VISTALINK SECURITY is allowed to use these calls.)\n 2) from M VistA servers to non-M systems (typically Java/J2EE based\n systems)\n \nThe communications are in the form of requests. For requests received by\nthe M-based system, the VISTALINK package contains a Request Manager to\nmanage these requests. Requests are forwarded to the appropriate Request\n\n
\nSee the patch description for patch XOBS*1.0*2 on Forum.\n \n[M Build: 1.0.2.6]\n\n
\nContains the client/server M-side security module for VistALink. This\nmodule acts mainly as a wrapper around Kernel's login functionality, as\nwell as around the RPC Broker's authorization functionality. VistALink\nuses this module for end-user authentication and for RPC authorization.\n\n
\nContains the client/server M-side security module for VistALink. This\nmodule acts mainly as a wrapper around Kernel's login functionality, as\nwell as around the RPC Broker's authorization functionality. VistALink\nuses this module for end-user authentication and for RPC authorization.\n \n[Build: 1.5.0.026]\n\n
\nThis patch corrects 2 issues within the VISTALINK SECURITY package:\n \nApplication variables not cleaned up between RPC requests.\nVistaLink's context variables are not updated properly.\n\n
\nThis patch corrects an issue within the VISTALINK package:\n \nVistaLink server errors are not respecting the Kernel's limits for logging\nerrors. \n\n
\nContains the client/server M-side security module for VistALink. This\nmodule acts mainly as a wrapper around Kernel's login functionality, as\nwell as around the RPC Broker's authorization functionality. VistALink\nuses this module for end-user authentication and for RPC authorization.\n\n
\nCONTAINS ROUTINES COMPRISING THE SECURITY SUBSYSTEM FOR VISTALINK.\n\n
\nThis is the build for the HealtheVet Desktop. The desktop is primarily\na client-side Java application. Some server-side components may be added\nin the future.\n\n
\nThis patch will enhance the identification of the VistA system connected \nto, such that when patient context is established or subscribed to, the \nproper VistA system will be used to match patient context.\n \nThis patch takes advantage of a system identifier used to flag a \nproduction system definitively.\n\n
\nRefer to the National Patch Module for complete details of the \nenhancements included in this patch.\n\n
\nRefer to the National Patch Module for complete details of the \nenhancements included in this patch.\n\n
\nThis patch is designated for the decommissioning of the Care Management \nPROVIDER\n 4 ORRCM CLIENT Care Management Client Context\n 5 ORRCMC DASHBOARD Care Management Dashboard 1.8.0\n 6 ORRCMC PATIENT TASK Care Management Task 1.0\n 7 ORRCMC SIGN LIST Sign List 1.0\n 8 ORRCMM CLINICIAN Clinician Perspective Selector\n 9 ORRCMM CLINICIAN NURSE Clinician Nurse and Sign List \nPerspectives\n 10 ORRCMM CLINICIAN QUERY Clinician Dashboard and Query \nSelector\n(CM) application. \n 11 ORRCMM CM ALL All Care Management Perspectives\n 12 ORRCMM NURSE QUERY Nursing Dashboard and Query Selector\n \nThe follow options will be removed from Vista:\n \n 1 ORRC CM MENU Care Management Menu\n 2 ORRC ORD ACK INQ BY ORDER ORDER ACKNOWLEDGEMENT INQUIRY BY \nORDER\n 3 ORRC ORD ACK INQ BY PROV ORDER ACKNOWLEDGEMENT INQUIRY BY \n\n
\nThe purpose of this patch is to remove unused routines in the Care \nManagement (CM) package from VistA. \n\n
\nThis package contains the Care Management modules. These modules include \nthe clinician dashboard, the nursing dashboard, the query tool, and the \ntask editor. Options are used to grant access to the modules or \ncomponents within the modules.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nPlease refer to the National Patch Module for the detail of this\npatch build.\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nPlease refer to the National Patch Module for the detail of this\npatch build.\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nMD*1.0*16 (Clinical Flowsheets Version 1.0)\ncollected information as discrete data. Some data elements, such as \nvital signs, are available to the Vitals Package and Computerized Patient \nRecord System (CPRS). Various reports built on the other data elements \nare available for CPRS in the form of TIU Notes.\n \nThere are two ways to enter data into Clinical Flowsheets: manually and\nvia Health Level 7 (HL7) messaging. Any instrument or external system\ncapable of sending HL7 messages can be considered a source of data for\nClinical Flowsheets (provided that the HL7 messages conform to Clinical\nFlowsheets requirements).\n \n \nClinical Flowsheets uses VistA Data Extraction Framework (VDEF) support,\nHL7 messaging, and the CP Gateway service to notify the medical device of\nthe patient's admission, discharge, and transfer.\n \nThe Clinical Flowsheets patch consists of these three (3) Graphical User\nInterface (GUI) components and one (1) Kernel Installation & Distribution\nSystem (KIDS) build:\n \n - CP Console\nThe Clinical Flowsheets patch of the Clinical Procedures (CP) package\n - CP Flowsheets\n - CP Gateway Service\n - MD1_0P16.KID\n \n \n++++++\nNOTE:\n A. IF THE SITE IS NOT CURRENTLY RUNNING CLINICAL PROCEDURES, ONLY\nTHE KIDS BUILD NEEDS TO BE INSTALLED. ALL OTHER INSTALLATION\nINSTRUCTIONS AND POST-INSTALLS CAN BE IGNORED.\nprovides an electronic representation of the traditional paper flowsheet\n \n B. IF THE SITE IS RUNNING CLINICAL PROCEDURES AND DOES NOT PLAN ON\nIMPLEMENTING CLINICAL FLOWSHEETS AT THIS TIME, ONLY THE KIDS AND CP\nCONSOLE (REPLACEMENT FOR THE CURRENT CP MANAGER) NEED TO BE INSTALLED.\n \n C. IF THE SITE IS RUNNING CLINICAL PROCEDURES AND WISH TO BEGIN THE\nIMPLEMENTATION OF CLINICAL FLOWSHEETS, THEN ALL 4 COMPONENTS NEED TO BE\nINSTALLED: KIDS, CP CONSOLE, CP FLOWSHEETS AND THE NEW CP GATEWAY\nSERVICE.-\n++++++\nmaintained during each inpatient stay. Vitals, Intake & Output (I&O), \n \n \nFEATURES:\n=========\n1. FEATURE: Provide GUI to view, enter and edit patient's data.\nClinical Flowsheets provides a user-friendly, customizable, GUI with\n"flow-sheets" to view, manually edit, and manually enter patient ICU\nVitals and I&O information.\n \n2. FEATURE: Interface with Intensive Care Unit (ICU) devices.\nWound Documentation, etc., are examples of data types that can be \nClinical Flowsheets project and application will provide an interface for\nthe collection of patient data from ICU monitoring devices. The\ncollected and verified data will be stored automatically in the\nappropriate VistA database(s).\n \n3. FEATURE: Introduces the Admission Discharge Transfer (ADT) system.\nWith VDEF support, HL7 messaging, and the CP Gateway service, CP's ADT \nsub-system will notify the ICU device of the patient admission, \ndischarge, \nand transfer.\nrecorded via Clinical Flowsheets into the Veterans Health Information\n \n4. FEATURE: Standardized Terminology Files.\nClinical Flowsheets supports standardized terminology files with Vitals\nMeasurements, and I&O terms. This standardized terminology file is also \na component of patch MD*1*16.\nSystem and Technology Architecture (VistA) system. Clinical Flowsheets\nprovides a departure from its predecessor applications by storing \n\n
\n \nMD*1.0*12 - Clinical Flowsheets HL7 Redesign\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nTERMINOLOGY FILE UPDATES\n\n
\nCHANGE QUALIFER CC TO CUBIC CENTIMETER\n\n
\nCLINICAL PROCEDURES TERMINOLOGY FILE UPDATES\n\n
\nMODIFY AUTO-COMPLETE OF PROCEDURE TIME\n\n
\nPlease see patch MD*1.0*29 on Forum for complete details and installation \ninstructions for this patch.\n\n
\nAIS APPROVED TERMINOLOGY ADDITIONS/UPDATES\n\n
\nPROCEDURE AUTO CHECK-IN ISSUE\nPROCEDURE AUTO CHECK-IN ISSUE\n\n
\nCLINICAL PROCEDURES TERMINOLOGY FILE UPDATES\n\n
\nTest patch MD*1.0*42 v2 August 18, 2015\nflag to the Clinical Procedures (CP) Instrument File so that CP will send \n---------------------------\nN/A\n \nProblem:\n--------\n \nResolution:\n-----------\n \n \nonly an "outbound" Health Level 7 (HL7) message containing Computerized \nTest Sites:\n----------\nPortland VA Medical Center, Portland, Oregon (VAMC)\nVA Boston Health Care System, West Roxbury, MA (VAHCS)\nVA Connecticut Health Care System West Haven Campus, West Haven, CT \n(VAHCS)\nJames A. Haley Veterans Hospital, Tampa, Florida (VAHCS)\n \n \nDocumentation Retrieval Instructions\nPatient Record System (CPRS) patient information to the medical \n------------------------------------ \nThe functionality introduced by this patch is described herein.\n \n \nPre/Post Installation Overview\n------------------------------\nThere are no Pre/Post installation routines associated with this patch.\n \n \nPre-Installation Instructions\ninstrument. The CP procedure is automatically placed in Completed status \n-------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \n \nInstallation Instructions\n-----------------------------\n1. Choose the PackMan message containing this patch.\nafter the HL7 message is sent, thus preventing an "inbound" HL7 message \n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select \n the Installation Menu. From this menu, you may elect to use the \n following options. When prompted for the INSTALL NAME enter\n MD*1.0*42.\n \n a. Verify Checksums in Transport Global - This option will \n allow you to ensure the integrity of the routines that are in\ncontaining the test results from being sent back to the CPRS Consult \n the transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\nNote. \n \n4. From the Installation Menu, select the Install Package(s) option \n and choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO// Press <Enter>\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO// Press <Enter>\n \n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO// Press <Enter>\n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0// respond 0.\n \n \nPost-Installation Instructions\n------------------------------\nN/A\n \nThe physician can then edit the Consult Note by manually pasting in data \n \nRoutine Information:\n====================\n \n \nThe second line of each of these routines now looks like:\n ;;1.0;CLINICAL PROCEDURES;**[Patch List]**;Apr 01, 2004;Build 7\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\nfrom a test result reporting system to complete the Consult. \n \nRoutine Name: MDRPCOP\n Before: B79065771 After: B83622221 **4,6,11,20,42**\nRoutine Name: MDWOR\n Before: B43803580 After: B47515185 **14,11,21,20,37,42**\n \nRoutine list of preceding patches: 20,37\n \nThis modification is beneficial for users of reporting systems-such as \nthe Clinical Assessment, Reporting, and Tracking System for Cardiac \nCatheterization Laboratories (CART-CL) application-who do not want the \ntest results from the medical instrument to populate the CPRS Consult \nNote, but prefer to manually paste the test results from the reporting \nsystem into the Consult Note. \n \nThe CONSULT KEEP OPEN field in the CP INSTRUMENT File (#702.09) must be \nset to Yes for this functionality to work. This triggers the routines \nthat put the CP procedure in Completed status to interrupt the \n======================================================\nbi-directional flow.\n \n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n----------------------- ------------------------ --------------------\n \nCP INSTRUMENT (#702.09) CONSULT KEEP OPEN (.401) New\n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nDescription:\nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n===========\n----------- ---- --------------------\nN/A\n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \n \nTemplates Associated:\n \nThe NSR20131203 Clinical Procedures Uni-directional Configuration Option \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nN/A\n \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\nenhancement entails changing the current VistA functionality to add a \n----------------------------\n20131203 CP UNI-DIRECTIONAL CONFIGURATION OPTION\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nRemedy Ticket(s) & Overview\n\n
\nThis patch creates an event for broadcasting new or updated data in the\nClinical Observations (CLiO) module.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nIPv6 MODIFICATIONS\n\n
\nCORRECTION FOR AUTO CHECK-IN SETUP\n\n
\nCLINICAL PROCEDURES TERMINOLOGY FILE UPDATES\n\n
\nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the Clinical Procedures (CP User) Graphical\nUser Interface (GUI) requires an upgrade to Delphi version XE8 in order to\nimplement the new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the Clinical Procedures (CP Hemodialysis) Graphical\nUser Interface (GUI) requires an upgrade to Delphi version XE8 in order to\nimplement the new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nThis patch addresses one Clinical Procedures issue:\n \nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the Clinical Procedures (CP Flowsheet) Graphical\nUser Interface (GUI) requires an upgrade to Delphi version XE8 in order to\nimplement the new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nThis patch addresses one Clinical Procedures issue:\n \nIn preparation for the VA's transition to become two factor authentication\n(2FA) compliant the Clinical Procedures (CP Console) Graphical\nUser Interface (GUI) requires an upgrade to Delphi version XE8 in order to\nimplement the new Remote Procedure Call (RPC) Broker allowing compliance.\n\n
\nMODIFICATIONS TO UTILIZE IMMUN FILE GROUP DATA\n\n
\n \nCP TERMINOLOGY CORRECTIONS FOR PATCH MD*1*39\n\n
\nThis patch fixes a defect in CP Hemodialysis. \n \n1. I15834349FY17 - LOM - Function missing in HEMODIALYSIS\nIn CP Hemodialysis, the patient selection grid lost the \nability to sort the included information after the\nprevious patch. \n \nNOTE: Patch MD*1*56 includes a new GUI executable for CP \nHemodialysis .\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nCP FLOWSHEET TERMINOLOGY ADD/MODIFY TERMS\n\n
\nCLINICAL PROCEDURES FLOWSHEET TERMINOLOGY UPDATES\n\n
\nThe purpose of this patch is to provide a software bug fix for Clinical \nProcedures functionality. This patch addresses the following issues:\n \n-Duplicate reports with the same time stamp\n\n
\nThis patch addresses four (4) issues:\n \n4. A follow up CP order placed the same day as a scheduled CP order\n will check in with out it being scheduled.\n \n1. A cancelation message is not being sent to the instrument \n when an order is canceled or discontinued through CPRS.\n \n2. TIU Note Title of Procedures edited in CP Console (GUI) are being\n lost.\n \n3. Attempting to import in CP Console (GUI) results in an error. \n\n
\nClinical Procedures and DICOM Consult Request Tracking.\nThis allows DICOM objects created during a CP examination to be sent\nto VistA Imaging and be processed automatically. It also allows them\nto be used with all of the other DICOM services, like query/retrieve\nand export.\n \nReports in DICOM Encapsulated PDF are highly recommended.\n \nThis patch and MAG*3.0*208 work together to greatly imnprove \ninteroperability between Clinical Procedures and Vist Imaging\nCPRS Consult Request Tracking DICOM.\n \nThe CP studies have the same Instrument Order Number as the\nregular consult and procedure Accession Number (sss-GMR-nnnnnnnn).\n \n\n
\nHigh Volume Procedure Setup modifications to allow setting of the \nassociated note title's two technical fields - COMMIT ACTION and \nPOST-SIGNATURE CODE.\n \nConsult / Procedure to Clinical Procedure conversion utilities.\n\n
\nCP CONSOLE NETWORK HELP FILE\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nCP USER UPDATE FOR WINDOWS 10, NEW DELPHI AND NETWORK HELP FILE.\n\n
\nCP FLOWSHEETS WINDOWS 10 HELP FILE\n\n
\nThis patch will address the issues in the following tickets:\nINC3431411, INC3430523, INC3525351, INC3559705\nHemodialysis CPs are failing to auto check-in after the first day.\n\n
\nMD*1.0*67 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\nCP FLOWSHEETS TERMINOLOGY UPDATES\n\n
\nMD*1*70 - CP HEMO DEFAULT DATE 12-30-1899\nThis patch will resolve the following issue in the Clinical Procedures\npackage:\n \nThe default value for Diagnosis date and Initial Therapy date is set to \nthe arbitrarily value of 12-30-1899. Initial analysis showed that the \ncode was looking for that specific date to replace it with a null entry, \nbut this code was being bypassed incorrectly\n\n
\nELIMINATE ALERTS FOR RETRACTED NOTES AND MODS TO HIGH VOLUME SETUP\n\n
\nMD*1.0*75 - CP HEMODIALISIS DEFAULT DATE 12-30-1899 IN TIU DOCUMENTS\nas <blank>\nThis patch will resolve the following issue in the Clinical Procedures\npackage:\nOn the current Treatment Status Report Screen Diagnosis Date and Initial \nTherapy Date is blank it looks like the TIU Document Details section is \nstill populated with 12/30/1899.\nCODE MODIFIED TO: CP APP-HEMODIALYSIS select Patient and view Submit tab\nscreen that shows in Document Details section that Diagnosis Date and\nInitial Therapy Date \n\n
\nThe patch addresses one (1) issue:\n \nINC7452263 - In the CP Console, where the views for the CP flowsheets \nare built if you save and move to another patient too quickly. This new\npatient will receive the previous patients record temporarily confusing \nthe user.\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nCLINICAL PROCEDURES FLOWSHEET TERMINOLOGY UPDATE\n\n
\nAUTO CHECK-IN ISSUES WITH MUSE PROCEDURES\n\n
\nThis patch addresses the following issue:\n \nEncounters for procedures that are read and completed in the MUSE system \nare not crossing over correctly which causes the encounters to remain\nopen.\n\n
\nCP CONSOLE NETWORK HELP FILE\n\n
\nThis patch addresses the following issue:\n \nINC31290396 - Consult to Procedures Conversion Utility Issue\n\n
\nSee FORUM for full patch description.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nBackup of MD*1.0*88 on Jan 10, 2025\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch\n\n
\nPlease refer to the National Patch Module for the detail of this patch \nbuild.\n\n
\nPlease refer to the National Patch Module for the detail of this\npatch build.\n\n
\nClinical Procedures Version 1.0.\n\n
\nClinical Procedures (CP) primarily functions as a conduit for passing final\npatient results, using HL7 messaging, between vendor clinical information\nsystems (CIS), and the VISTA hospital information system. Clinical\nProcedures was developed in conjunction with Consults, CPRS, TIU and\nVISTA Imaging and is fully integrated with these packages.\n\n
\nPATCH OVERVIEW\nto the complexity of the functionality and the number of product line\ndependencies.\n \nThis is the second part of the Electronic Claims Management Engine (ECME)\npackage (in the BPS namespace), also known as the active build. It\ncomprises of these patches: BPS*1*1, PSO*7*148, PSS*1*90, PSX*2*48 and\nIB*2*276.\n \nThis build will introduce functionality supporting Point of Service\nOutpatient Pharmacy claim and billing processing by collecting billing and\n \nclinical information within the prescription fill workflow process. This\nbuild will create real-time electronic claims and send claim data to\nadjudicating payers from the new VistA Electronic Claims Management Engine\n(ECME) via the VistA HL7 module (using the PSO NCPDP link) to the Vitria\nserver at the FSC in Austin, TX in a HIPAA compliant (NCPDP V. 5.1)\nformat. Vitria will then store and forward these transactions to WebMD for\nfinal submission to the payer on a real-time basis. Payer responses will\nbe received and returned to VistA in the appropriate manner (i.e. - claim\ntransactions sent to Integrated Billing (IB), Drug Utilization responses\nand warnings sent to the Outpatient Pharmacy V. 7.0 package and rejections\nThe Healthcare Insurance Portability and Accountability Act National\nmade available to the appropriate personnel for review and analysis).\n \nWithin VistA, throughout this process, constant bi-directional\ncommunication via API's between Outpatient Pharmacy, Integrated Billing,\nand ECME will process and generate these claim and billing transactions at\nthe appropriate trigger points within the standard VA process workflow.\nCouncil for Prescription Drug Programs (HIPAA NCPDP) initiative, whose\nultimate goal is to provide functionality allowing electronic transmission\nof Outpatient Pharmacy (OP) prescription claims to payers and the receipt\nof claim responses (including drug utilization review responses and\nwarnings) on a real-time basis, is being developed and introduced in a\nphased implementation strategy. This deployment strategy was utilized due\n\n
\nePharmacy Phase 5 - NCPDP D.0\n\n
\nModify reversal process to get the reversal payer sheet from the pharmacy \nplan.\n\n
\nePharmacy Phase 6\n\n
\nThis patch fixes random subscript errors, allows users to select \na Drug Class Code as an option during the Payable Claims Report \n[BPS RPT PAYABLE] and fixes issues while sorting in the ECME \nUser Screen [BPS USER SCREEN].\n\n
\nEPHARMACY OPERATING RULES\n\n
\nePayments ePharmacy Compliance\nBPS IB PRCA EPAYMENTS BUNDLE 1.0\n\n
\nHAPE EDI Revenue project - NCPDP Continuous Maintenance Standards\n\n
\nMCCF ePharmacy Compliance Phase 3\n\n
\nMCCF EDI TAS ePharmacy Iteration 1\n\n
\nThis patch supports the National Council for Prescription Drug Programs \nthat will enable the user to reopen a closed Electronic Claims Management\nEngine (ECME) claim; updates to the Rx Activity Log; and permanent storage\nof Claims activity information as reported by the ECME Billing Events\nReport. \n(NCPDP) standard which was adopted under the Healthcare Insurance\nPortability and Accountability Act (HIPAA) for pharmacy claims. This patch\nis one of six to be released. Three patches will be released in a KIDS\nmulti-build distribution containing: BPS*1*3, PSO*7*247, and IB*2*342. \nThree patches will be released individually and they are: PRCA*4.5*247,\nPSX*2*62, and PSS*1*115.\n \nEnhancements included in the release of the six patches are a new option \n\n
\nMCCF EDI TAS EPHARMACY BUILD 2\n\n
\nMCCF EDI TAS EPHARMACY BUILDS 3 & 4\n\n
\nMCCF EDI TAS EPHARMACY BUILDS 5 & 6\n\n
\nMCCF EDI TAS EPHARMACY BUILD 13\n\n
\nBackup of BPS PSO IB BUNDLE 16.0, BPS*1.0*28, PSO*7.0*560, IB*2\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch modifies the Application Program Interface (API) that\nprocesses claims in E-Pharmacy to check for a valid user before it\nstores that information in the BPS Transaction File\n(#9002313.59).\n\n
\nThe HIPPA NPI project supports the use of NPI within the Electronic \nClaims Management Engine (ECME) application.\n\n
\nThis patch has enhancements which extend the capabilities of the Veterans\n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*5\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*127\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*63\n \nThe first three patches (BPS*1*5, IB*2*363,and PSO*7*260) will be\nreleased in the Kernel Installation and Distribution System (KIDS)\nmulti-build distribution BPS PSO IB BUNDLE 2.0. Patches PSX*2*63 and\nPSS*1*127 will be released as stand-alone patches. Since there is an\nimplementation dependency between the multi-build distribution and the\nstand-alone patches, PSX*2*63 and PSS*1*127 must be installed prior to\nHealth Information Systems and Technology Architecture (VistA) electronic\nthe installation of the multi-build. For more specific instructions\nplease refer to the installation steps provided in each of the patches.\npharmacy (ePharmacy) system. Below is a list of all the applications\ninvolved in this project along with their patch number:\n \n APPLICATION/VERSION PATCH\n --------------------------------------------------------------\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*260\n INTEGRATED BILLING (IB) V. 2.0 IB*2*363\n\n
\nE-PHARMACY ENHANCEMENTS\n\n
\nDescription:\nof claim responses (including drug utilization review responses and \nRoutine Summary: \n================\nThe second line now reads as follows: \n \n <TAB>;;1.0;IHS Pharmacy Point of Sale; **[patch list]**; Jun 2004\n \n CHECK^XTSUMBLD results: \n \nRoutine Checksum Value \n======= ============== \nwarnings) on a real-time basis, is being developed and introduced in a \nBPSECA1 6485606\nBPSECA2 1682902\nBPSECA4 6220829\nBPSECA5 4789118\nBPSECA7 711596\nBPSECA8 3062006\nBPSECA9 4929109\nBPSECFM 2542538\nBPSECP0 1231669\nBPSECP1 8373351\nphased implementation strategy. This deployment strategy was utilized due \nBPSECP2 4648149\nBPSECP3 8882441\nBPSECR0 1379515\nBPSECR1 1717840\nBPSECR2 3480905\nBPSECX0 754266\nBPSECX1 4278553\nBPSECX4 569954\nBPSECZ3 4496980\nBPSECZA 4449840\nto the complexity of the functionality and the number of product line \nBPSER1A 3879379\nBPSER2A 5013615\nBPSER3A 3060197\nBPSER4A 4098816\nBPSES00 1681063\nBPSJACK 10839099\nBPSJAREG 3471785\nBPSJHLI 1245414\nBPSJHLT 11644295\nBPSJINI1 6280511\ndependencies.\nBPSJINIT 7809002\nBPSJPHNM 7830674\nBPSJPREG 3683655\nBPSJUTL 2750894\nBPSJUTL1 3176342\nBPSJVAL 3292489\nBPSJVAL1 9341066\nBPSJVAL2 7321923\nBPSJXI1 1888198\nBPSJZPR 10852903\n \nBPSJZQR 1211753\nBPSJZRP 6572546\nBPSMHDR 5172150\nBPSOS02 922003\nBPSOS03 4762173\nBPSOS2 5794835\nBPSOS2A 3438805\nBPSOS2B 12833055\nBPSOS2C 5657589\nBPSOS2D 1377421\nThe first release of this two part implementation is BPS*1*0, comprised of\nBPSOS2E 1432527\nBPSOS2F 2190\nBPSOS6A 1692241\nBPSOS6E 2202299\nBPSOS6F 975863\nBPSOS6G 583939\nBPSOS6H 4134763\nBPSOS6I 15473221\nBPSOS6K 1898226\nBPSOS6L 1105023\nthe new Electronic Claims Management Engine (ECME) package (in the BPS \nBPSOS6N 16897666\nBPSOS96 776535\nBPSOS97 696242\nBPSOSA 2151744\nBPSOSAA 2532955\nBPSOSAB 9179518\nBPSOSAD 613947\nBPSOSAM 11538762\nBPSOSAN 1994745\nBPSOSAO 1873331\nnamespace), plus the patches PSS*1*81, IB*2.0*223, IB*2.0*251, and \nBPSOSAP 2403666\nBPSOSAQ 735144\nBPSOSAR 8262363\nBPSOSAS 1745519\nBPSOSAW 5124351\nBPSOSAY 1379312\nBPSOSAZ 1186543\nBPSOSB 959796\nBPSOSB0 113802\nBPSOSB1 2139\nPRCA*4.5*202, which are listed here in order of installation. BPS*1*0 is a\nBPSOSB2 2146\nBPSOSB4 2160\nBPSOSB5 2167\nBPSOSBA 101168\nBPSOSBC 617661\nBPSOSBD 2674634\nBPSOSBE 2279\nBPSOSBI 2307\nBPSOSBL 101245\nBPSOSBP 484897\n===========\ndormant release that only allows each site to perform preliminary setup \nBPSOSBQ 485350\nBPSOSBT 485371\nBPSOSBU 2391\nBPSOSBW 4604870\nBPSOSC1 2746444\nBPSOSC2 10781985\nBPSOSC3 2261922\nBPSOSCA 4059491\nBPSOSCF 10660104\nBPSOSD1 2151\nwork and to confirm that the software does not adversely affect other \nBPSOSEC 3788978\nBPSOSFD 13905233\nBPSOSH2 6439291\nBPSOSH4 7279183\nBPSOSH5 4709954\nBPSOSH6 6286709\nBPSOSH7 9955590\nBPSOSHF 3902159\nBPSOSHR 4748980\nBPSOSHU 358514\npackages.\nBPSOSI 6988972\nBPSOSI7 2207252\nBPSOSI8 7983989\nBPSOSIB 1520498\nBPSOSIO 1817298\nBPSOSIP 124772\nBPSOSIW 2934848\nBPSOSIY 13182481\nBPSOSIZ 9743963\nBPSOSJ1 2985572\n \nBPSOSK 5983189\nBPSOSK2 1179461\nBPSOSL 7117465\nBPSOSL1 2520334\nBPSOSM 2149792\nBPSOSM1 10236213\nBPSOSMA 2958187\nBPSOSMB 3244227\nBPSOSMC 5914845\nBPSOSMZ 1902484\nThere are two main areas addressed by BPS*1*0:\nBPSOSN0 2010\nBPSOSN4 844510\nBPSOSN7 289249\nBPSOSO1 1391042\nBPSOSO2 6339508\nBPSOSO3 2231\nBPSOSO4 2238\nBPSOSO5 2245\nBPSOSQ1 2227577\nBPSOSQ2 8749786\n \nBPSOSQ3 10336941\nBPSOSQ4 8580589\nBPSOSQF 2968761\nBPSOSQG 5287867\nBPSOSQH 957180\nBPSOSQJ 6618401\nBPSOSQL 10953965\nBPSOSQS 8333856\nBPSOSR1 6141326\nBPSOSR2 579087\na. Registration of the Pharmacy with the Vitria BusinessWare IE.\nBPSOSR4 4195196\nBPSOSRB 8237522\nBPSOSS2 2327741\nBPSOSS3 670477\nBPSOSS6 214430\nBPSOSS7 67706\nBPSOSS8 7915679\nBPSOSS9 1158213\nBPSOSSG 11401688\nBPSOSU1 2630136\nb. The Insurance Matching of Group Plans with Pharmacy Plans\nBPSOSU2 1004112\nBPSOSU3 877677\nBPSOSU4 4710582\nBPSOSU5 764934\nBPSOSU7 2698763\nBPSOSU8 3768830\nBPSOSU9 1857421\nBPSOSUA 8511603\nBPSOSUB 3172501\nBPSOSUC 1896200\n \nBPSOSUD 6705940\nBPSOSUE 4667712\nBPSOSX 6863167\nBPSOSXA 2383\nBPSOSXE 1952199\nBPSRDT 12823556\nBPSUTIL 464990\n \n \nDocumentation Retrieval:\nFollowing the installation of BPS*1*0, each site must register their \n========================\n \nThe ECME documentation is available on the ANONYMOUS.SOFTWARE directory\nat one of the following Office of Information (OI) Field Offices.\n \nSites may retrieve documentation in one of the following ways:\n \n(1) The preferred method is to FTP the files from\n download.vista.domain.ext, which will transmit the files from the\n first available FTP server.\n \npharmacy with Vitria and match applicable insurance group plans using the \n \n(2) Sites may also elect to retrieve documentation directly from a\n specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext \n \nThe documentation distribution includes:\n \ninsurance matching screens. These processes are detailed in the HIPAA \n FILE NAME DESCRIPTION\n BPS_1_0_IG.PDF HIPAA NCPDP CONNECTION FOR EDI \n PHARMACY (DORMANT RELEASE)\n INSTALLATION GUIDE \n BPS_1_0_RN.PDF HIPAA NCPDP CONNECTION FOR EDI\n PHARMACY (DORMANT RELEASE)\n RELEASE NOTES\n IB_2_251_TM.PDF INTEGRATED BILLING IB*2.0*251 \n (e-PHARMACY) TECHNICAL MANUAL\n IB_2_251_UM.PDF e-PHARMACY CLAIMS INSURANCE PROCESS\nNCPDP CONNECTION FOR EDI PHARMACY INSTALLATION GUIDE and the E-PHARMACY \n USER MANUAL\n \n(3) Documentation can also be retrieved from VISTA Documentation Library\n(VDL) on the Internet at the following address, http://www.domain.ext/vdl.\n \nInstallation Instructions:\n========================== \n \nThe software for this patch is being distributed via a host file. The \nhost file will contain the following package and builds:\nCLAIMS INSURANCE PROCESS document. Both of these documents are located on\n \n Host file name BPS_1_0.KID\n \n Package:\n BPS_1\n \n Builds:\n PSS*1.0*81 \n IB*2.0*223\n IB*2.0*251\nthe anonymous directory. It is very important that the IRM or person\n PRCA*4.5*202\n \nSites may retrieve the software directly by using FTP from the \nANONYMOUS.SOFTWARE directory at the following OI Field Offices:\n \n Albany: ftp.fo-albany.domain.ext\n Hines: ftp.fo-hines.domain.ext\n Salt Lake City: ftp.fo-slc.domain.ext\n \nDo not install this patch while Pharmacy Data Management users are using \ninstalling the patch at each facility provide a copy of these documents to\nthe software. Installation will take no longer than 15 minutes. There are\nno scheduling restrictions or recommendations.\n \nInstallation Steps\n \n 1. Use VA FileMan to add the new domain, EPHARMACY.VITRIA-EDI.AAC.DOMAIN.EXT,\n to the DOMAIN file (#4.2). The installation instructions are included\n in the patch description for the XM*DBA*160 patch. This domain must be\n in place before the installation of the IB*2*251 patch that is\n included in the BPS 1.0 Master Build.\nits ADPAC(s) and any other relevant staff who will be responsible for\n \n 2. Download the KIDS file BPS_1_0.KID via FTP. This file needs to be \n retrieved in ASCII format.\n \n 3. Review mapped sets for the PSS*, IB*, and PRCA* namespaces. If the \n routines are mapped, they should be removed from the mapped set at\n this time.\n \n 4. From the Kernel Installation & Distribution System menu, select the \n Installation menu.\nregistering their pharmacy with Vitria and completing the insurance \n \n 5. From this menu, select the Load a Distribution option. When prompted \n for a file name, enter the directory name where you FTPd the build, \n followed by BPS_1_0. In our example, the file name is\n USER$:[ANONYMOUS]BPS_1_0.KID. Determine the location where you stored\n your build to decide the correct file name entry.\n \n 6. At the "Want to Continue with Load? YES//" prompt, enter YES.\n \n 7. At the "Want to RUN the Environment Check Routine: YES//" prompt, \nmatching process.\n answer YES.\n \n 8. From this menu, the installer may select to use the following options:\n \n(When prompted for INSTALL NAME, enter BPS 1.0)\n \n a. Backup a Transport Global - This option will create a backup \n message of any routines exported with the patch. It will NOT backup\n any other changes such as DDs or templates.\n \n \n b. Compare Transport Global to Current System - This option will allow\n you to view all changes that will be made when the patch is installed.\n It compares all components of the patch (routines, DDs, templates,\n etc.).\n \n c. Verify Checksums in Transport Global - This option will ensure the \n integrity of the routines that are in the transport global.\n \n 9. At the "Select Installation Option:" prompt, enter 6 Install \n Package(s)\nPATCH OVERVIEW\nAt a later date, additional HIPAA NCPDP patches will be released to \n \n10. At the "Select INSTALL NAME:" prompt, enter BPS 1.0.\n \n11. When prompted, "Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? YES//" respond NO.\n \n12. When prompted, "Want KIDS to INHIBIT LOGONs during the install? YES//"\n respond NO.\n \n13. When prompted, "Want to DISABLE Scheduled Options, Menu Options, and \nactivate all of the HIPAA NCPDP functionality. Until that time, sites will\n Protocols? YES//" respond NO.\n \n14. When prompted, "Device:Home//" respond with the correct device and DO \n NOT queue this to P-Message.\n \n15. If routines were unmapped as part of step 3, they should be returned \n to the mapped set once the installation has run to completion.\nnot be able to electronically submit claims utilizing this new \nfunctionality.\n \nThe HIPAA NCPDP project was created in response to a Chief Business Office\n(CBO) request for modifications to several Veterans Health Information \nSystems and Technology Architecture (VistA) software applications in \naccordance with HIPAA Electronic Data Interchange (EDI) transactions and \nNCPDP mandated format standards, specifically the NCPDP Telecommunication \n \nStandard v.5.1.\n \nThe specific functionality for this patch is listed below.\n \n(1) A user interface has been developed to facilitate entry and filing\n Registration and Point of Contact information for each specific\n Application (Site) and Pharmacies at a site.\n \n(2) An HL7 interface is included that will create and send HL7 messages\n containing the Application and Pharmacy Registration data to Vitria.\nThe Healthcare Insurance Portability and Accountability Act National \n This data notifies Vitria that the site will soon be sending \n electronic third party pharmacy claims. \n \n(3) An additional HL7 interface is included which receives messages from\n Vitria containing the most up to date Payer Sheet data, and files the\n data into the appropriate Vista table. This interface will run \n continously, and will keep the site updated with the most recent\n changes and additions to the third party Payer sheets.\n \nNew Globals:\nCouncil for Prescription Drug Programs (HIPAA NCPDP) initiative, whose \n============\n \nThe following globals will be created when installing this build.\n \n^BPS - MOSTLY STATIC\n^BPSC - VERY DYNAMIC - WILL CONTINUALLY GROW\n^BPSCOMB - STATIC - CURRENTLY NOT USED BY THE VA\n^BPSECP - DYNAMIC - DOESNT GROW\n^BPSECX - DYAMIC - DOESNT GROW A LOT\n^BPSEI - STATIC - CURRENTLY NOT USED BY THE VA\nultimate goal is to provide functionality allowing electronic transmission\n^BPSF - STATIC - DOESNT GROW\n^BPSR - DYNAMIC - GROWS CONTINUALLY\n^BPST - DYNAMIC - GROWS\n^BPSTL - DYNAMIC - GROWS\n \n \nAssociated NOISs:\n=================\nN/A\n \nof Outpatient Pharmacy (OP) prescription claims to payers and the receipt \n \nTest Sites:\n===========\nNEW YORK HARBOR HCS\nNORTH TEXAS HCS\nANN ARBOR, MI \nBATTLE CREEK, MI \nDETROIT, MI\nIRON MOUNTAIN, MI\n \n\n
\nPLEASE READ THE ENTIRE DESCRIPTION AND INSTALLATION INSTRUCTIONS\n \n status and the fact that the count stopped at ">100".\n - The counter for Queued Up has been changed to display the actual\n number up to a maximum of 1000. If more than 1000 are queued up,\n the display will show "> 1000".\n - The description "Requests in the queue" has been changed to\n "Requests waiting for purge"\n \n (example)\n Request Processor Status\n MAINTENANCE: Running and not Scheduled\n 1) Adds the name of the Request Queue to the VDEF Alert message.\n Current Task # [Proc]: 7399750 [21663B42]\n Requests waiting for purge: 14 Last request#: 14\n Checked Out(0) Queued Up(0) Errored Out(0)\n \n 9) Changed the M lock used to protect the VDEF Request Queue so that\n it doesn't prevent using FileMan to access the VDEF queue file.\n \n10) Creates the new Application "VDEF ALERTS" and the new Mail Group\n "VDEF NATIONAL ALERTS" and changes the VistA Mail Group for VDEF\n Alerts from the HL7 group to the new VDEF group.\n \n \n11) Removed the Scheduled task from the Status of VDEF components [VDEF\n Status] display and added the TaskMan status of the task.\n \n12) Removed the XQASUPV variable from the alert call so that VDEF\n alerts are no longer forwarded to unread alerts supervisor mail\n group.\n \n13) Added the date and time and the TaskMan task status to the VDEF\n Status display.\n 2) Eliminates false VDEF Alerts.\n \n \nIRM NOTES:\n===========\nBefore installing this patch, make sure you have completely installed \nXU*8.0*339 and run the '% program' conversion RELOAD^ZTMGRSET utility.\n \nThis patch REQUIRES Kernel patch XU*8.0*339 which fixes a bug in the\n$$ASKSTOP^%ZTLOAD() API and also creates a new API JOB^%ZTLOAD().\nVDEF requires both of these to be updated by the XU*8.0*339 patch in\n \nOrder for VDEF*1*3 to install.\n \nThis VDEF patch uses the $$JOB^%ZTLOAD functionality released with\nXU*8*399. Please confirm that the post-KIDS install steps for XU*8*399\nhave been done. The following MUMPS code should indicate that XU*8*399 is\nin the second line of the %ZTLOAD routine:\n>ZL %ZTLOAD ZP +1:+2\n \nFor the duration of the installation of this patch, all VDEF Request\nQueue processors that were in the Running state will be temporarily \n 3) Eliminates the problem of VDEF Request Queue processor not being\nsuspended. The pre-install and post-install routines will suspend and \nthen restart all Request Queue processors that were in the Running state \nafter installation of this patch. VDEF messages will continue to \naccumulate in the queues during suspension and will start processing \nagain after the patch has completed installation. This is the equivalent \nof you using the VDEF Configuration and Status Menu option "SusR \nSuspend/Run Request Queue" to suspend and restart the Request Queues.\n \nWhen you see the message "Waiting for processes to quit . .", there\nwill be approximately a 5 second wait.\n restarted by TaskMan.\n \nPLEASE NOTE: The VDEF Post-install program will not start the VDEF \nprocesses on test or Legacy systems that have the Test System flag set.\n \n \nIRM'S POST-INSTALLATION REQUIREMENTS\n====================================\n1. NEW MAIL GROUP AND APPLICATION FOR VDEF ALERTS\n After you have installed this patch, there will be a new Application\n named VDEF ALERTS which will have the Mail Group VDEF NATIONAL ALERTS\n \n assigned to it. The new Mail Group will not have any local members in\n it. YOU MUST ASSIGN THE LOCAL MEMBERS. It will have the remote member\n GARDNER.JEFF@DOMAIN.EXT. Please verify these that these two new\n definitions are correctly set up. If a site does not have the Mail\n Group VDEF NATIONAL ALERTS, VDEF will continue the alerts to the HL7\n Mail Group.\n \n2. MODIFY THE 'VDEF STARTUP OPTION' SCHEDULED TASK.\n Using the TaskMan option 'Schedule/Unschedule Options', edit the\n parameters for the task VDEF STARTUP OPTION as indicated in the screen\n 4) No longer sets the flag for unread VDEF Alerts to be sent to a mail\n example shown here.\n \n Edit Option Schedule\n Option Name: VDEF STARTUP OPTION \n Menu Text: VDEF STARTUP OPTION TASK ID: 5998624\n ___________________________________________________________________\n QUEUED TO RUN AT WHAT TIME: (Enter current date/time + 5 minutes)\n DEVICE FOR QUEUED JOB OUTPUT: \n QUEUED TO RUN ON VOLUME SET: \n RESCHEDULING FREQUENCY: 300S (Enter 300S)\n group supervisor.\n TASK PARAMETERS: \n SPECIAL QUEUEING: Startup Persistent (Change from STARTUP\n to Startup Persistent\n \n \nThis patch addresses the following New Service Request (NSR):\n=============================================================\nThere is no NSR associated with this patch.\n \n \nBEFORE INSTALLING THIS PATCH.\n \nThis patch addresses the following Remedy ticket(s):\n====================================================\n65927,99499,100952,102184,102329,103092,103286,104402,105065,106497\n106674,107101,107142,107326,107508,107589,107773,107927,108431,108661\n108873,108915,109469,109521,109627,109638,109715,109725,110057,110285\n110501,110688,110765,110891,111109,112391,112642\n \n \nOverview of Patch Items:\n========================\nThis patch also includes numerous enhancements to the VistA Data\n1) A pre-install routine, PREIN^VDEFKIDS, is included in this patch that\n suspends VDEF Request Queue processing through the duration of this\n patch installation. It also stops and deletes the TaskMan tasks driving\n the processes and the VDEF monitor processes.\n \n2) A post-install routine, POSTIN^VDEFKIDS, is included in this patch\n that restarts VDEF Request Queues after installation of this patch.\n It also creates new VDEF monitor tasks.\n \n3) The routine VDEFUTIL has been changed to not set the flag for an \nExtraction Framework (VDEF) functionality:\n unread VDEF Alert to be sent to the supervisor. This program has also\n been changed to prefix the date & time to the VDEF alert text and to\n use the new VDEF alert mail group to send a MailMan message to the VDEF\n developer whenever a VDEF alert occurs.\n \n4) The routine VDEFCONT has been changed to eliminate the false VDEF\n Alerts from being generated. It has also been changed to include\n the name of the Request Queue in the VDEF Alert message.\n \n5) The routine VDEFREQ has been changed to eliminate the problem of\n \n TaskMan not restarting the VDEF Request Queue processor EN^VDEFREQ.\n Instead, VDEFREQ does not re-schedule itself with TaskMan but uses\n an M HANG command loop based on the number of seconds in file\n #579.3, field .05 - CHECK-OUT TIME LIMIT.\n \n6) The routine VDEFMNU has been changed to display the VMS process ID\n for the Request Queue Task in the Status of VDEF components [VDEF\n Status] display. The counter for Processed Requests has been dropped\n from the Status of VDEF components [VDEF Status] display. It was\n useless information.\n 1) In the VDEF Configuration and Status Menu [VDEF CONFIGURATION MENU],\n \n7) The routine VDEFQM has been changed to incorporate two VDEF APIs\n that will requeue requests that are stuck in the Checked Out or\n Errored Out state.\n \n8) A new routine VDEFMON has been created to monitor the Request Queue\n process and restart it if it dies as well as automatically re-queuing\n requests that have Errored Out or get stuck in the Checked Out status.\n \n9) There are no VDEF global changes in this patch.\n the options marked below with an asterisk now return to the option\n \n \nTest Sites:\n===========\nBAY PINES\nEL PASO\nLOUISVILLE\nMARYLAND (Integrated)\nMEMPHIS\nPHILADELPHIA\n prompt instead of going back to the main VDEF Configuration and Status\nPHOENIX\nSAN FRANCISCO\n \n \nLOCATION OF DOCUMENTATION FOR THIS PATCH\n========================================\nThere will be a documentation update for this patch to the VDEF V1.0 \nInstallation & User Configuration Guide and the VDEF V1.0 Technical Manual\n \n \n Menu.\nINSTALLATION INSTRUCTIONS\n=========================\n \nInstall Time - less than 5 minutes\n \n1. LOAD TRANSPORT GLOBAL\n ---------------------\n Choose the PackMan message containing this patch and invoke the\n INSTALL/CHECK MESSAGE PackMan option. The build includes an\n Environment check routine VDEFKIDS.\n \n \nLoading Distribution...\n \n VDEF*1.0*3\nWill first run the Environment Check Routine, VDEFKIDS\n \n2. COMPONENTS SENT WITH PATCH\n --------------------------\n Routine Summary\n The following routines are included in this patch. The second line\n Site Site-Wide Parameters\n of Each of these routines now looks like:\n ;;1.0;VDEF;**3**;Dec 28, 2004\n \n Checksum\nRoutine Old New Patch List\nVDEFCONT 8818367 8818367 **3**\nVDEFKIDS 13711730 5283479 **3**\nVDEFMNU 47567743 14047707 **3**\nVDEFMON 8468795 3113945 **3**\nVDEFQM 12629742 12740824 **3**\n \n * Req Request Queue Parameters\nVDEFREQ 7914740 7914740 **3**\nVDEFUTIL 5715842 5715842 **3**\n \nSites should use CHECK^XTSUMBLD to verify checksums.\n \nNOTE: The above checksums are based on your site having installed\nVDEF*1*3 v9. If you are installing VDEF*1*3 for the first time or if you \ndid not install VDEF*1*3 v9, your old checksums will not match those in \nthe above list.\n \n * ActR Activate/Inactivate Requestor\nIf you are installing VDEF*1*3 for the first time and all your current\nVDEF* programs are V1.0, your old checksums should be:\nVDEFCONT 10134570\nVDEFKIDS N/A\nVDEFMNU 12329753\nVDEFMON N/A\nVDEFQM 11427789\nVDEFREQ 7981911\nVDEFUTIL 1413855\n \n * SusR Suspend/Run Request Queue\n3. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu\n [XPD MAIN]:\n Edits and Distribution\n Utilities\n Installation\n \n Select Kernel Installation & Distribution System Option:\n INStallation\n * Cust VDEF Custodial Package Activate/Inactivate\n \n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\n \n * API VDEF Event API Activate/Inactivate\n Select Installation Option:\n \n4. Select Installation Option:\n ---------------------------\n When prompted for the INSTALL NAME, enter VDEF*1.0*3.\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option will\n Stat Status of VDEF components\n allow you to view all changes that will be made when this\n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n5. Select Installation Option: Install Package(s)\n ----------------------------------------------\n Select INSTALL NAME: VDEF*1.0*3 Loaded from Distribution\n * Sch Request Processor Schedule\n MM/DD/YY@HH:MM\n => VDEF*1*3 v9\n \n Select Installation Option: INstall Package(s)\n \n => VDEF*1*3 v9\n \n This Distribution was loaded on Dec 22, 2005@11:48:44 with header of\n VDEF*1*3 v9\n It consisted of the following Install(s):\n \n VDEF*1.0*3 Checking Install for Package VDEF*1.0*3\n \n Will first run the Environment Check Routine, VDEFKIDS\n \n Suspending Request Queues and stopping associated TaskMan jobs\n \n Stopping the MONITOR^VDEFCONT task\n \n Stopping the MONITOR^VDEFMON task\n \n 2) A new process, the "VDEF Request Queue Monitor" has been added to\n Waiting for processes to quit . . .\n \n Install Questions for VDEF*1.0*3\n \n \n Incoming Mail Groups:\n \n Enter the Coordinator for Mail Group 'VDEF NATIONAL ALERTS': //\n <enter your name> \n \n monitor the VDEF Request Queue process and restart it when it stops\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO\n \n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// TCP\n \n \n if the state of the Request Queue is Running. This new monitor is\n \n Install Started for VDEF*1.0*3 : \n Dec 22, 2005@11:50:14\n \n Build Distribution Date: Dec 22, 2005\n \n Installing Routines:\n Dec 22, 2005@11:50:14\n \n Installing PACKAGE COMPONENTS: \n automatically started by the VDEF Startup option. This process is\n \n Installing MAIL GROUP\n \n Installing HL7 APPLICATION PARAMETER\n Dec 22, 2005@11:50:14\n \n Running Post-Install Routine: POSTIN^VDEFKIDS\n \n (NOTE: the next 4 lines will not be displayed in a test or Legacy\n Environment installation. Instead it will display:\n hardcoded to run every 10 minutes. The VDEF Request Queue Monitor will\n "VDEF is not started on test systems."\n \n Running Post-Install Routine: POSTIN^VDEFKIDS\n \n Starting the Request Queues and associated Tasks\n \n Starting the MONITOR^VDEFCONT task\n \n Starting the MONITOR^VDEFMON task\n \n also automatically requeue any Checked Out and Errored Out VDEF\n Updating Routine file...\n \n Updating KIDS files...\n \n VDEF*1.0*3 Installed.\n \n Dec 22, 2005@11:50:14 \n \n NO Install Message sent\n \n requests.\n 100% Complete \n \n Install Completed\n \n \nBUILD COMPONENTS\n=================\n \nENVIRONMENT CHECK : VDEFKIDS DELETE ENV ROUTINE: No\n PRE-INIT ROUTINE : DELETE PRE-INIT ROUTINE: No\n \n POST-INIT ROUTINE : POSTIN^VDEFKIDS DELETE POST-INIT ROUTINE: No\n PRE-TRANSPORT RTN : \n \nROUTINE:\n VDEFCONT SEND TO SITE\n VDEFMNU SEND TO SITE\n VDEFMON SEND TO SITE\n VDEFQM SEND TO SITE\n VDEFREQ SEND TO SITE\n VDEFUTIL SEND TO SITE\n 3) VDEF Alert messages are now prefixed with the date & time of the\n \nREQUIRED BUILDS: ACTION:\n VDEF 1.0 Don't install, remove global\n XU*8.0*339 Don't install, remove global\n \n \n \nPOST INSTALLATION CHECKS:\n1) Verify that the three VDEF tasks shown in the example exist after\n the install is complete. The EN^VDEFREQ and MONITOR^VDEFMON tasks\n alert in the format MM/DD/YY@HH:MM:SS.\n should be active while the MONITOR^VDEFCONT task may be scheduled\n or active.\n \n (example task list)\n \n Task list Dec 22, 2005 11:26 am Page 1\n----------------------------------------------------------------------\n7399750: EN^VDEFREQ, VDEF Request Processor for MAINTENANCE. No device.\n DAYT12. From Today at 11:26, By you. Started running Today\n at 11:26. Job #: 560347970 [21663B42]\n \n----------------------------------------------------------------------\n7399751: MONITOR^VDEFCONT, VDEF Checked Out Monitor. No device. \n DAYT12,ROU. From Today at 11:26, By you. Scheduled for Today\n at 11:27\n----------------------------------------------------------------------\n7399752: MONITOR^VDEFMON, VDEF Request Processor Monitor. No device.\n DAYT12,ROU. From Today at 11:26, By you.\n Started running Today at 11:26. Job #: 560552879 [21695BAF]\n----------------------------------------------------------------------\n \n 4) Original VDEF Alert message texts are clearer in context.\n2) Run the Status of VDEF components [VDEF Status] display and verify the\n following:\n - Requestor status is Activated\n - Request Processor Status is "Running"\n - Task status is "Active-Running"\n - the Current Task # matches the task # for the EN^VDEFREQ task.\n \n (example of the Status of VDEF components [VDEF Status] display)\n \n VDEF Status - Dec 22, 2005@11:50:14\nDESCRIPTION:\n \nLogical Link Status\n VDEFVIE1: stopped or caught up\n VDEFVIE2: stopped or caught up\n VDEFVIE3: stopped or caught up\n \nRequestor Status\n MAINTENANCE: Activated Dest.: VISTA HL7 Req. Queue: \nMAINTENANCE\n \nRequest Processor Status\n 5) New VDEF Alerts have been added.\n MAINTENANCE: Running\n Current Task # [Proc]: 7410052 [21A53BA8] Task status: Active-\n Running\n Requests waiting for purge: 0 Last request#: \n Checked Out(0) Queued Up(0) Errored Out(0)\n \nIMPORTANT NOTES ON THE Status of VDEF components [VDEF Status] DISPLAY\n==========================================\nThe "Request Processor Status" is simply the status flag of the process in\na VDEF global. It is possible to have the status "Running" even if the VMS\n - VDEF CHECKED OUT MONITOR FAILED TO START. CHECK ERROR TRAP.\nprocess of the task had died.\n \nIF THE REQUEST QUEUE PROCESSOR TASK (EN^VDEFREQ) IS RUNNING:\nThe Request Processor Status will show "Running" and the task status will \nshow "Active-Running".\n \nIF THE REQUEST QUEUE PROCESSOR TASK (EN^VDEFREQ) IS SUSPENDED BY SITE \nUSING the VDEF Configuration and Status Menu:\nThe Request Processor Status will show "Suspended" and the task status \nwill show "Interrupted".\n - RECORD <IEN> IN QUEUE <QUEUE NAME> HUNG IN CHECKED OUT STATUS.\n \n VDEF Status - Dec 22, 2005@11:50:14\nLogical Link Status\n VDEFVIE1: stopped or caught up\n VDEFVIE2: stopped or caught up\n VDEFVIE3: stopped or caught up\n \nRequestor Status\n MAINTENANCE: Activated Dest.: VISTA HL7 Req. Queue: MAINTENANCE\n \n - VDEF REQUEST PROCESS <QUEUE NAME> FAILED TO START. CHECK ERROR\n Request Processor Status\n MAINTENANCE: Suspended\n Current Task # [Proc]: 7410053 [0] Task status: Interrupted\n Requests waiting for purge: 0 Last request#: \n Checked Out(0) Queued Up(0) Errored Out(0)\n \nIMPORTANT:\nIF THE REQUEST QUEUE PROCESSOR TASK (EN^VDEFREQ) IS RUNNING BUT THE VMS \nPROCESS HAS STOPPED:\nThe Request Processor Status will STILL show "Running" and the task status\n TRAP.\nwill STILL show "Active-Running".\n \nThis is because of the way that an application communicates with TaskMan \nto stop a task. It makes a request to TaskMan to stop the task and waits \nfor the status of the task to go to "stop requested". Then the application\nquits back to TaskMan and only then does TaskMan update the task status to\nstopped or interrupted. If the VMS process for the EN^VDEFREQ task had\ndied, then the VDEFREQ program is not running and cannot quit back to\nTaskMan. This is why the TaskMan task status stays "Active-Running".\n \n - VDEF QUEUE PROCESS MONITOR DID NOT START. CHECK ERROR TRAP.\n \nHOW TO VERIFY THAT THIS PATCH TESTS SUCCESSFULLY\n================================================\n1) From the VDEF Configuration and Status Menu, suspend the MAINTENANCE\n request queue. You should get the two alerts shown below.\n \n MM/DD/YY@HH:MM:SS VDEF REQUEST QUEUE PROCESSOR FOR MAINTENANCE HAS\n EXITED.\n MM/DD/YY@HH:MM:SS VDEF QUEUE MAINTENANCE IS SUSPENDED. PLEASE START IT.\n \n - VDEF HAS REQUEUED CHECKED OUT RECORDS. NO ACTION NEEDED.\n Note that you may have to wait up to ten minutes to get these\n alerts. This is the interval that the VDEF process monitor runs at.\n \n2) From the VDEF Configuration and Status Menu, restart the MAINTENANCE\n Request Queue by changing the status to Running.\n \n3) WITHOUT suspending the VDEF Request Queue 'MAINTENANCE', use the VDEF \n Status display to identify the VMS process ID for the Request Queue\n Task. Then use ^RESJOB to kill that job. You should get the\n following alert:\n - VDEF HAS REQUEUED ERRORED OUT RECORDS. NO ACTION NEEDED.\n \n MM/DD/YY@HH:MM:SS VDEF QUEUE MAINTENANCE AUTO-RESTARTED. NO ACTION\n REQUIRED.\n \n Note that you may have to wait up to ten minutes to get these\n alerts. This is the interval that the VDEF process monitor runs at.\n \n If you kill the process while there is a VDEF Request in the\n Checked Out status, you may also get this alert:\n \n - VDEF QUEUE PROCESS MONITOR HAS EXITED.\n MM/DD/YY@HH:MM:SS RECORD nnn IN QUEUE MAINTENANCE HUNG IN Checked\n Out Status.\n \n NOTE: Doing this will leave an orphaned TaskMan task for EN^VDEFREQ\n that you will have to clean and delete.\n \n4) If you do get a Checked Out request alert, use %G and look at the\n record. If it's a valid alert, the data in piece 2 of the zero node\n will be "C".\n ^VDEFHL7(579.3,1,1,record ien,0) = IEN^STATUS^......\n============\n - VDEF QUEUE '"_QUEUE_"' AUTO-RESTARTED. NO ACTION REQUIRED.\n \n5) If you get any requests that get hung in the Checked Out or\n Errored Out Status, they will get requeued by the VDEF queue\n process monitor which runs every ten minutes. If this monitor does\n requeue any requests, you will get one or both of these alerts:\n \n MM/DD/YY@HH:MM:SS VDEF HAS REQUEUED CHECKED OUT RECORDS. NO ACTION\n NEEDED.\n \n MM/DD/YY@HH:MM:SS VDEF HAS REQUEUED ERRORED OUT RECORDS. NO ACTION\n - VDEF QUEUE '"_QUEUE_"' IS SUSPENDED. PLEASE START IT.\n NEEDED.\n \n NOTE: Without direct, intentional intervention in the ^VDEFHL7\n queue by modifying a record, you will have to wait for a\n request to get checked out hung or errored out on it's own. If\n you don't want to wait, instructions on how to do that for the\n purposes of verifying the testing of this patch are available\n from the VDEF developer.\n \n6) VDEF alerts will no longer be sent to members of the HL7 mail group\n - VDEF REQUEST QUEUE PROCESSOR FOR "_$P(QUEUE,U)_" HAS EXITED.\n but will be sent to the members in the new VDEF NATIONAL ALERTS\n mail group.\n \n7) You have had the patch in place for 2 weeks and have seen no\n adverse affects and it has not affected the functionality of any\n other option(s).\n \n8) You have communicated your test results to the SQA representative\n and given your approval for its release.\n \n 6) All VDEF alerts will send a MailMan message to the VDEF developer\n On FORUM that includes the alert text, the site name and ID and\n the date & time of the alert.\n \n 7) Includes a new program VDEFKIDS that has two APIs, VDEFKIDS\n and POSTIN^VDEFKIDS. These APIs are defined in the build as the\n \n Environment Check and post install routines. Although the\n Pre-install routine does pre-installation type functions, it is\n defined in the build as the Environment Check routine, NOT the\n Pre-install routine. This is to prevent any VDEF* routines that\n are in the build from being filed over actively running routines\n causing an EDITED error trap error. By the time KIDS runs the\n Pre-Install routine, ALL the routines in the build have already\n been loaded whereas when the Environment routine is run, no other\n programs in the build have been installed.\n \nThis patch fixes 4 problems in the VistA Data Extraction Framework\n The pre-install routine will:\n - suspend all VDEF Request Queues\n - stop the TaskMan tasks associated with these queues\n - stop the VDEF checked out request monitor\n - stop the VDEF Request Queue process monitor\n \n The post-install routine (in production systems only) will:\n - un-suspend all VDEF Request Queues (change state to running)\n - create new TaskMan tasks for these queues\n - start the VDEF checked out request monitor\n(VDEF) V1.0 functionality:\n - start the VDEF Request Queue process monitor\n \n 8) The Status of VDEF components [VDEF Status] option screen has been\n modified. See the example that follows.\n - The VMS Process ID associated with the VDEF Request Queue process\n task has been added.\n - The TaskMan task status has been added.\n - The counter for Processed requests has been deleted. This was\n useless information because it was simply a count of the number\n of records in the VDEF Request Queue that are in the Processed\n\n
\nPlease see the National Patch Module on Forum for the patch description.\n\n\n
\nPlease see the National Patch Module for the description.\n\n\n
\nThis patch will fix the input transform utility that inadvertently\nrestricted the values to greater than 30 days and update the REQUEST\nQUEUE WAKEUP PERIOD description to reflect how the field is\ndefined.\n\n
\nThis patch will fix the VDEF Request Processor so that when it\nencounters a VDEF REQUEST QUEUE file (#579.3) record NAME \nVALUE PAIRS MULTIPLE (#579.311) with an internal entry \nnumber value other than a one (1) or two (2) it will continue\nprocessing as long as the data associated with each respective\nnode is valid.\n\n
\nThis build is for the GOLD disk. It was buld on the FOIVISTA account. \n\n
\nVDEF stands for VistA Data Extraction Framework, a data-driven scripting\ntool for automated HL7 message generation.\n\n
\nKernel Installation and Distribution System first time install. This\npackage is used to install Kernel for the first time. It will install\na part of KIDS that will then allow you to use KIDS to install Kernel.\n\n
\nRoutine to import data to MDR.\n\n
\nSee National Patch Module for details.\n\n
\nThis patch creates entries in file 7115.1 for the locked down file Master \nRadiology Procedure (71.99)\n\n
\nThis patch supports Native Domain Standardization of the Payers Domain.\n \nPlease see FORUM for full patch description and installation instructions.\n\n
\nThis patch supports Native Domain Standardization of the Demographics \nDomain. \n \nPlease see FORUM for full patch description and installation instructions.\n\n
\nThis patch supports Native Domain Standardization of the Medications \nDosage Form Domain.\n \nPlease see FORUM for full patch description and installation instructions.\n\n
\nPlease see patch description on FORUM.\n\n
\nRefer to National Patch Module for details\n\n
\nSee National Patch Module for details\n\n
\nSee National Patch Module for details\n\n
\nSee National Patch Module for details\n\n
\nSee National Patch Module for details.\n\n
\nRefer to National Patch Module.\n\n
\nProblem List\n\n
\nHealth Data & Informatics V1.0 package release.\n\n
\nDESCRIPTION:\nfacilitate automatically purging the log. A post-init will run to clean\n \n 2. Unload the distribution\n Use the INSTALL/CHECK MESSAGE option on the PackMan menu to unload\n the KIDS distribution included with this message.\n \n 3. Stop all incoming filers.\n On the 'Filer and Link Management Options' menu, select the\n 'Monitor, Start, Stop Filers' option. At that menu level, choose\n the action 'Stop incoming filer' to stop each incoming filer.\n \nup any existing TMP("MHV7LOG") entries.\n 4. Install the transport global.\n From the Kernel Installation and Distribution System Menu,\n select the Installation menu.\n \n 5. From this menu, you may elect to use the following options\n (when prompted for INSTALL NAME, enter MHV*1.0*1):\n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - this option will\n \n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - this option will\n allow you to ensure the integrity of the routines that are in\n the transport global.\n d. Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu\nA new menu, MHV LOG MENU, has been added. The log provides information \n and select the package 'MHV*1.0*1'.\n \n 7. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? YES//', Respond as fits your situation, see note above.\n \n 8. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES//', respond NO.\n \n 9. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', choose 'NO'.\nof use to MHV developers, and should only be used by IRM staff in the \n \n10. At the DEVICE prompt, you can send your output to any printer or\n HFS file, display it on the terminal screen, or queue it to run\n at a scheduled time.\n \n11. After the install, restart the incoming filers.\n On the 'Filer and Link Management Options' menu, select the\n 'Monitor, Start, Stop Filers' option. At that menu level, choose\n the action 'Start incoming filer' to start the default number of\n incoming filers.\nevent troubleshooting an MHV interface becomes necessary. The MHV user \n \n12. Log on to each node running the HL7 listener and run the post init\n Routine CLEANLOG^MHV1P1.\n \n \n \nROUTINE SUMMARY:\n================\nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\nmanual provides information on how to use these options.\n \n <tab> ;;1.0;My HealtheVet;**1**;Aug 23, 2005\n \n CHECK^XTSUMBLD results\nRoutine name Before Patch After Patch Patch List\n============ ============ =========== ==========\nMHV1P1 N/A 674288 1\nMHV7R1 7907937 7704915 1\nMHV7R2 8857636 8693511 1\nMHV7U 6547453 7067072 1\nIncluded options are:\nMHVUL1 N/A 5527922 1\nMHVUL2 N/A 5279644 1\nMHVUL3 N/A 10342175 1\n MHV LOG CONFIG Configure Logging Parameters\n MHV LOG INFO Display Log Information\n============\n MHV LOG OFF Turn Off Logging\n MHV LOG ON Turn On Logging\n MHV LOG PURGE Purge Log\n MHV LOG SIZE Display Log Size\n MHV LOG VIEW View Log Entries\n \nA new option has been added, MHV CLIENT, as a broker context for a future \nMHV GUI client. The following remote procedures are also included:\n MHV LOG INFO\n MHV LOG OFF\n \n MHV LOG ON\n MHV LOG PURGE\n MHV LOG SIZE\n MHV LOG CONFIG\n MHV LOG SUMMARY\n MHV LOG DETAIL\n \nThe MHV 1.0 release went to the field with two HL7 protocols having the\n"debug" flag set. These event driver protocols will be released with the \nflag turned off. The following protocols are being shipped:\nThe MHV 1.0 release for MHV Rx Refill went to the field with logging to a\n MHV OMP-O09 Event Driver\n MHV OMP-O09 Subscriber\n MHV QBP-Q13 Event Driver\n MHV QBP-Q13 Subscriber\n \n \nAssociated Remedy Ticket\n====================\nHD 131029\n \nTMP global left on. The non-standard use of TMP by the MHV log causes\nTest Sites\n==========\nTampa VAMC\nBay Pines VAMC\nBaltimore VAMC\nVISN 2 \n \n \nINSTALLATION INSTRUCTIONS\n==========================\nthe TMP entries to not be cleaned up automatically.\nThe patch is distributed in KIDS format in a PackMan message.\n \nThis patch requires MHV 1.0\n \n \n **WARNING**\n \nInbound HL7 messages for MHV should not be processed during installation\nof this patch. All incoming filers should be stopped before installation.\n \nThis patch will turn off logging in the HL7 receiver routines allowing it\nBefore you install this patch in production, please identify all the\nproduction node(s) that have the TMP("MHV7LOG") global. This should be\nthe same node(s) running the HL7 Listener. You will need to log on to\neach of these node(s) and run the post-init routine CLEANLOG^MHV1P1 will\ndelete the global entries since TMP is not translated. The\nTMP("MHV7LOG") global should have many entries.\n \n ****\n \n \nto be switched on and off externally as designed. An XTMP global will be\n **Notice**\nThis patch includes new options.\nWhen an option is included in the patch build, the question REBUILD MENUS\nis asked as a PRE-INSTALL question. If you choose to have KIDs rebuild\nthe menus it will happen at the end of the build installation and may\ntake several hours.\n \nNote: Most sites have a nightly batch job that rebuilds the menus so if\nyou queued the installations ensure that it will complete prior to the\nbatch job. Or, if you are installing several builds, wait until the\nused instead of TMP. Options will be added to control logging and to\nlast one to use the KIDs rebuild functionality.\n \n ****\n \nThe install time for this patch is less than 5 minutes. This patch can be\ninstalled with users on the system.\n \n \n \n 1. These routines should not be mapped.\n\n\n \nIssue Description:\n==================\nJAZZ Story: 409966\nThis patch addresses the issue related to retrieving User Name Components \nthat contain space characters, and enhancing the user query by \nretrieving more fields from New User File #200.\n \n \n \n \n \n \n \nBusiness Impact Description:\n============================\nThe impact for the providers who are using SM cannot be added to the \nSM Triage Groups if their names contain a space.\n \n \n \n MHV Secure Messaging (SM)\n \n \nEMERGENCY Issues Fix.\n\n
\nMHV MEDICATION HL7 MODIFICATIONS\n\n
\nMHV MEDICATION HL7 MODIFICATIONS\n\n
\nMHV*1*2 PHR Infrastructure\nlogging features released with MHV*1*1.\n Update DD: YES\n Send Security Code: YES\n Date Comes With File: YES\n Site Data: REPLACE\n Resolve Pointers: NO\n \n MHV RESPONSE MAP (#2275.4) - New file\n Update DD: YES\n Send Security Code: YES\n Date Comes With File: YES\n \n Site Data: REPLACE\n Resolve Pointers: NO\n \nField:\n BUILDER ROUTINE (#.06) File: MHV REQUEST TYPE (#2275.3)\n DESCRIPTION (#2) File: MHV REQUEST TYPE (#2275.3)\n NAME (#.01) File: MHV RESPONSE MAP (#2275.4)\n RESPONSE PROTOCOL (#.02) File: MHV RESPONSE MAP (#2275.4)\n BUILDER ROUTINE (#.03) File: MHV RESPONSE MAP (#2275.4)\n BOUNDARY SEGMENT (#.04) File: MHV RESPONSE MAP (#2275.4)\n \n \nRoutine:\nMHV1P2 MHV7B0 MHV7B1 MHV7B1B \nMHV7B2 MHV7BU MHV7BUS MHV7R1 \nMHV7R2 MHV7RU MHV7RUS MHV7T \nMHV7TB MHV7U MHVRQI MHVU1\nMHVU2 MHVUL2 MHVXRX MHVXRXR \n \nProtocol:\n MHV ORP-O10 Event Driver\nDetailed Description\n MHV ORP-O10 Subscriber \n MHV RTB-K13 Event Driver\n MHV RTB-K13 Subscriber \n \nHL Logical Link:\n MHVVA \n \n \nDocumentation Retrieval:\n------------------------ \n--------------------\nThe software for this patch is distributed as KIDS build MHV*1.0*2.\nThe My HealtheVet Technical Manual is available through the VistA \nDocumentation Library (VDL) at the following address:\n \n http://www.domain.ext/vdl/HealtheVet.asp?appID=153\n \n \nTest Sites:\n-----------\nDetroit\nMHV*1*2 releases a number of infrastructure changes to improve interface \nLong Beach\nWashington\nBoston\nRichmond\n \n \n \n ================INSTALLATION INSTRUCTIONS =================\n \nThe patch is distributed in KIDS format in a PackMan message.\ndevelopment and support. Processing common to many interfaces such as \n \nThis patch requires MHV*1*1\n \nInstall time - less than 5 minutes. \n \nThis patch can be installed with users on the system, and should be \ninstalled during off-peak hours. No options need to be disabled to \ninstall this patch.\n \n \nvalidating patient identifiers, and common segment builders has been \nPre/Post Installation Overview\n------------------------------\nThe pre-init routine PRE^MHV1P2 turns on MHV Application Logging. It \nwill log information about MHV HL7 messages received during the patch \ninstall. This is only a precaution as the MHV application is tolerant of \nmessaging failures that might be caused by loading the patch. If a \nmessage was received during the patch installation, you will be notified \nand asked to check the error trap for errors in the MHV namespace. If \nany are found, you should log a remedy ticket.\nThe post init routine POST^MHV1P2 will update the MHVVA logical link and \nconsolidated into centralized functions. Use of HL7 package APIs and \nturn off MHV Application Logging. For test systems, it will remove data \nfrom the DNS DOMAIN (#.08), TCP/IP ADDRESS (#400.01), and TCP/IP PORT \n(#400.02) fields and set AUTOSTART (#4.5) to Disabled. For production \nsystems, it will ensure the correct values are in the DNS DOMAIN (#.08), \nTCP/IP ADDRESS (#400.01), and TCP/IP PORT (#400.02) fields and set \nAUTOSTART (#4.5) to Enabled.\n \n \n1. LOAD TRANSPORT GLOBAL \n ---------------------\nvariables has been moved from individual interfaces and encapsulated in \n Choose the PackMan message containing this patch and invoke the \n INSTALL/CHECK MESSAGE PackMan option. \n \n2. START UP KIDS \n -------------\n Start up the Kernel Installation and Distribution System Menu \n [XPD MAIN]: \n \n Edits and Distribution ... \n Utilities ... \n \ncentralized functions. If a move from HL7 v1.6 to the new HLO engine \n Installation ... \n \nSelect Kernel Installation & Distribution System Option: INStallation \n ---\n Load a Distribution \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Install Package(s) \n Restart Install of Package(s) \nbecomes necessary, the impact will be minimized. All interfaces and \n Unload a Distribution \n Backup a Transport Global \n \nSelect Installation Option: \n \n3. Select Installation Option: \n ---------------------------\n NOTE: The following are OPTIONAL - (When prompted for the\n INSTALL NAME, enter MHV*1.0*2):\n \nextractors have been updated to use the logging utility introduced with \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this\n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\nMHV*1*1. The message transmitter now provides support for extractors \n \n4. Select Installation Option: Install Package(s) \n ----------------------------------------------\n **This is the step to start the installation of this KIDS patch: \n \n a. Choose the Install Package(s) option to start the patch\n install.\nb. When prompted 'Want KIDS to INHIBIT LOGONs during the\n install? YES//' answer NO \n c. When prompted 'Want to DISABLE Scheduled Options, Menu \nthat need to use a local array to hold extracted data. \n Options, and Protocols? YES//' answer NO\n \nThe MHV Rx refill interfaces introduced with MHV 1.0 use original mode \nacknowledgements, a synchronous call into VistA, and do not require a \nlogical link to respond to the MHV system. The MHV HL7 interface \nframework also supports enhanced mode acknowledgments, an asynchronous \nSummary\ncall into VistA. The PHR HL7 interfaces will use enhanced mode \nacknowledgements, and require a logical link to define the connection to \nthe MHV system. The new link is MHVVA and is distributed with this \npatch. This link references a new domain, MHV.DOMAIN.EXT, but does not \nrequire this domain to be entered in the DOMAIN file (#4.2).\n \nEvent driver and subscriber protocols for the RTB^K13 query response \nmessage and the ORP^O10 order response message are being released to \nsupport a future change in Rx refill messaging from original mode \nacknowledgements to enhanced mode acknowledgements.\n-------\n \nMHV*1*2 updates the MHV REQUEST TYPE file #2275.3 with entries to support \nthe new PHR interfaces. These entries are disabled by having the BLOCKED \nfield #.03 set to YES. A new field, ROUTINE BUILDER field #.06, holds \nthe name of the query specific builder routine used by RTB^K13 types. A \nnew field DESCRIPTION field #2 provides a brief description of the \ninterface supported by that request type.\n \nThe MHV RESPONSE MAP file #2275.4 is new with this release. It is used \nto map inbound messages to the protocol and routine used to create the \nMHV*1*2 delivers infrastructure changes in support of upcoming Personal \nresponse message, and the segment used to break messages on a whole \nrecord boundary.\n \nPHR HL7 interfaces have the potential to carry very large messages. \nMHV*1*2 introduces the ability to break those messages into multiple \nsmaller messages for a "bolus" style response.\n \nMHV*1*2 fixes a bug where the TX field formatter did not correctly \ncalculate the size of the data put in the field, and thus could not \nenforce field size constraints. This issue was not encountered in \nHealth Record (PHR) HL7 interfaces. It also consolidates features common \nproduction because existing interfaces do not require such constraints. \nThe TX field formatter was rewritten to use an improved algorithm and fix \nthis bug.\n \nMHV*1*2 also fixes a bug where an incorrect ACK code and segment \ndescriptor could be returned on negative acknowledgments triggered by the \nrequest manager. This issue was not encountered in production because \nthe conditions required to trigger it have not occurred. These are \nimproper interface configuration, and catastrophic data integrity errors.\n \nto message receivers and builders, and encapsulates interaction with the \nThe pre-init routine PRE^MHV1P2 turns on MHV Application Logging. It \nwill log information about MHV HL7 messages received during the patch \ninstall. This is only a precaution as the MHV application is tolerant of \nmessaging failures that might be caused by loading the patch. If a \nmessage was received during the patch installation, you will be notified \nand asked to check the error trap for errors in the MHV namespace. If \nany are found, you should log a remedy ticket.\nThe post init routine POST^MHV1P2 will update the MHVVA logical link and \nturn off MHV Application Logging. For test systems, it will remove data \nfrom the DNS DOMAIN (#.08), TCP/IP ADDRESS (#400.01), and TCP/IP PORT \nHL7 v1.6 package to ease transition to HLO based interfaces should that \n(#400.02) fields and set AUTOSTART (#4.5) to Disabled. For production \nsystems, it will ensure the correct values are in the DNS DOMAIN (#.08), \nTCP/IP ADDRESS (#400.01), and TCP/IP PORT (#400.02) fields and set \nAUTOSTART (#4.5) to Enabled.\n \n \nNew Service Request (NSR):\n--------------------------\nThere is no NSR associated with this patch.\n \nbecome necessary. Most routines were modified to take advantage of the \n \nRemedy Ticket(s):\n-----------------\nThere are no Remedy tickets associated with this patch.\n \n \nComponents Sent With Patch \n--------------------------\nFile:\n MHV REQUEST TYPE (#2275.3)\n\n
\nMHV*1*5 Secure Messaging\n \nSummary\n-------\nMHV*1*5 delivers HL7 interfaces needed to support Secure Messaging. \nSecure Messaging leverages the existing TIUHL7 interface to save message \nthreads as progress notes. MHV*1*5 installs the components necessary to \nuse the TIUHL7 interface. MHV*1*5 also installs a new demographics query \nused to support secure messaging.\n\n
\nSummary\n-------\nMHV*1*6 delivers the HL7 interfaces needed to support Secure Messaging. \nThere are nine new queries in the MHV namespace that support the \nadministration and daily operation of the Secure Messaging enterprise \nsystem. MHV*1*6 installs the components necessary to execute the admin\nqueries to retrieve information on patients, providers, clinics, and\nteams.\n\n
\n \nSM Primary Care team.\n \nMHV*1*9 uses a different support PCMM call to always return the patient's\n currently assigned, Primary Care provider.\n \n \nDetailed Description\n--------------------\nSecure Messaging allows patients and clinicians to email each other securely\nand confidentially, and allows clinicians to post those email threads to the\nMHV*1*9 Secure Messaging\nmedical record as progress notes.\n \nRelationships between patients and clinicians are established based on\nPCMM providers, clinic appointments and Order Entry/Results Reporting (OE/RR)\nteams. Secure Messaging uses triage groups based on these relationships to\nmanage which patients are able to email which providers. More information\non Secure Messaging can be found on the MHV product web site\n \nhttp://vaww1.domain.ext/MyHealtheVet/, and MHV web site www.myhealth.domain.ext.\n \n \nWhen patients are assigned to other PCMM teams their MHV SM PCMM provider\nassociation is broken. This results in MHV SM users not able to send messages\nto/from their SM Primary Care team.\n \nBefore this patch, MHV application routines (MHVXPAT and MHVXDEMS) call,\nIA#1916 SCAPMC - SUPPORTED PCMM CALLS, application programmer interface (API)\ncall to $$PRPT^SCAPMC() to return a patient's Primary Care provider to MHV SM.\nThis API does not always return the current Primary Care provider.\n \nMHV*1*9 patch resolves the issue by always returning the SM patient's Primary Care\nSummary\nprovider using the support call, IA#1252 PRIMARY CARE INPUT AND OUTPUT API CALLS,\nAPI $$OUTPTPR^SDUTL3().\n-------\nWhen My HealtheVet (MHV) Secure Messaging (SM) patients are assigned to\nPrimary Care Management Module (PCMM) teams other than their Primary Care\nprovider team, their MHV SM PCMM Primary Care provider association is broken.\nThis results in MHV SM users not able to send messages to/from their\n\n
\nMHV Secure Messaging Workload Credit (SM WLC) ICD 10 EMERGENCY Issues Fix\n\n
\n \n \n \n \nMHV Secure Messaging Workload Credit (SM WLC) ICD 10 EMERGENCY Issues Fix\n\n
\nThe is the initial release the My HealtheVet package. It defines HL7 \ninterfaces for supporting internet prescription refill and queries for \nprescription information.\n\n
\nThis package supports the My HealtheVet website. It exposes interfaces \nfor extracting patient data, supporting prescription refill, and more.\n\n
\nThis build contains the routine(s), RPC context option, and remote \nprocedures used by the Electronic Signature (XOBE) package.\n \n[Build: 1.0.0.024]\n\n
\nContains the M-side portion of the electronic signature methods for \nrehosted applications that validate, store, and retrieve electronic \nsignature data.\n\n
\nDO NOT RESUSCITATE (DNR) DISPLAY PROBLEMS AND HOT LIST DUPLICATE PATIENT \nDISPLAY ISSUE\n\n
\nVARIOUS GUI MODIFICATIONS\n\n
\nThis patch addresses the following issue:\n \n \nProblem:\n--------\nWhen a patient has long list of active and recently expired meds creating \nan array of 1000+ nodes (approximately 200 meds), and Shift Handoff Tool \nis using the "Med Detail" data object, then the RPC Broker call CRHD PAT \nACTMEDS can get stuck in an endless loop.\n \nIf a Shift Hand Off patient has 200+ meds and is causing an endless loop, \n \nthen sites can change the display to "Med Summary" as a temporary work \naround. Once the patient is discharged, they can switch back to the "Med \nDetails" display.\n \n \nResolution:\n-----------\nRoutine CRHDAM is modified to prevent the endless loop from occurring. \nThe existing logic could end up resetting a counter node which caused the \nloop to start over at the top of the meds list. This is occurring \nINCORRECT DRUG LINKED IN AUTOMATED DISPENSING SYSTEM FROM ONEVA\nbecause the logic did not take into account the array of meds may contain \ndifferent number of lines for each Unit Dose, IV, and non-VA meds with in \nthe array and therefor didn't count correctly in some situations. \n \n \nTechnical Resolution:\n---------------------\nThere was logic that was attempting to limit the number of meds that were \nreviewed to 998 lines of the array. No reason for this can be determined \nplus it didn't work and when it didn't it reset the node to -1 which \n \ncaused the loop to start over from the top of the array of meds.\n \nLine PSGI+7 is changed from \nS CRHDNUM=0 F S CRHDNUM=$O(CRHDLST(CRHDNUM)) Q:'CRHDNUM!('CRHDFG) D \nTo\nS CRHDNUM=0 F S CRHDNUM=$O(CRHDLST(CRHDNUM)) Q:'CRHDNUM D\n \nLine PSGI+16 is changed from \n..I CRHDNUM2=CRHDLSTR S CRHDFG=0\nTo\n \n..;I CRHDNUM2=CRHDLSTR S CRHDFG=0\nDefect\nTracking System Ticket(s) & Overview:\n \n1. INC29032277 - Long Med List causes Endless Loop on Med Detail Display \n\n\nThis patch will add four new DNS domain entries to the REMOTE APPLICATION\nfile (#8994.5). The REMOTE APPLICATION file (#8994.5) was introduced as\npart of the Broker Security Enhancement (BSE) to secure access via the\nremote user or visitor approach by GUI applications. The remote visitor\naccess permits applications where users need to access a large number of\nsites, without requiring a separate access code and verify code at each\nsite.\n\n
\nAdmissions and Discharges to DEFAS WII LOA8 ADT MESSAGE\n\n
\nAdmissions and Discharges to DEFAS WII LOA8 ADT MESSAGE\n\n
\nThis patch is being released in support of the VBECS (VistA Blood \n \nInstallation and User Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.pdf\nVBECS Data Conversion Recommended Validation Method.xls\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.doc\nOptions: VBECS VISTALINK CONTEXT\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.pdf\nVBECS Implementation Process.xls\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \n========\nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.pdf\nKnown Defects and Anomalies.doc\nKnown Defects and Anomalies.pdf\n \n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system.\n \nInstallation will take less than 5 minutes.\n \n 1) Use the 'LOAD A DISTRIBUTION' option on the KIDS Installation\n menu. The Host File name is VBEC_1_1.KID . Answer YES to the\n question: "Want to Continue with Load? YES//"\n 2) From the Kernel Installation and Distribution System Menu,\n select the Installation menu.\n 3) From this menu, you may elect to use the following options\n (when prompted for the INSTALL NAME, enter VBEC*1.0*1).\n a) Backup a Transport Global - this option will create a backup\n \n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n d) Print Transport Global - this option will allow you to view the\nProtocols: VBEC OMG CLIENT\n components of the KIDS build.\n 4) Use the Install Package(s) option and select the package\n VBEC*1.0*1.\n 5) When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' respond YES\n 6) When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//', respond NO.\n 7) When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', respond NO.\n========== \n \nRemote Procedures: VBEC DSS EXTRACT\n==================\nEstablishment Computer System) Blood Bank Package. The routines, \n \n \nFiles: VBECS DSS EXTRACT (# 6002.03)\n======\n \nAssociated ICRs: None\n=============== \n \n \nAssociated Remedy Tickets: None\nprotocols, remote procedures, and options in this patch are used by the \n==========================\n \n \nAssociated NSR/E3R: None\n==============\n \n Test Site(s):\n==============\n \n HEARTLAND-EAST HCS\nDSS (Decision Support System) and CPRS (Computerized Patient Record \n PHILADELPHIA, PA\n SAN DIEGO, CA\n \n Installation Information:\n==========================\n \nVBEC*1*1 is being exported as part of the VBECS package release. The \ninstallation of VBEC*1*1 will be controlled by phase a phased release. \nAn Implementation Manager will be assigned to your site and will contact \nyour POC for VBECS and will provide your site with the location of the \nSystem). There is no direct user interaction with the contents of this \nKIDS Host Files prior to your scheduled installation date. \n \nInstallation Sequence\n=====================\n \nThe patches listed below represent those that will be part of the \ncontrolled phased release. Follow the sequence listed below when your \nphased installation occurs.\n \n 1. LR*5.2*335\npatch.\n 2. LR*5.2*367\n 3. VBECS Bundle (consisting of VBEC*1*0 and LR*5.2*325)\n 4. VBEC*1.0*1\n 5. OR*3.0*212\n \n Installation File:\n \nVBEC_1_1.KID \nThe VBEC_1_1.KID file will be made available by the Implementation \nManager prior to your site's implementation schedule along with \n \ninstruction to retrieve. \n \n \nDocumentation Retrieval:\n \nDocumentation is available for the entire VBECS package on the \nANONYMOUS.SOFTWRE directory at one of the following Office of Information \n(OI) Field Offices. Sites may retrieve documentation in either ".PDF" or \n"DOC" format in one of the following ways:\n \nRoutines: VBECDSS\n1. The preferred method is to FTP the files from :\nDownload.vista.domain.ext\n \n2. Sites may also elect to retrieve documentation directly from a \nspecific server as follows:\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nNOTE: The documentation files listed below will be listed in each of the \n======== VBECHLOR\nVBECS and LR patches that are part of the VBECS package and associate \npatches, they only need to be downloaded once.\n \nFile Name Retrieval format: Binary\n=========== ==========================\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \n\n
\nThis patch is part of the VBECS BUNDLE 1.0 controlled release. See the\ndescription for the VBECS BUNDLE 1.0 for patch details.\n\n
\nThis patch contains changes to the VBECS Blood Bank package. Refer to the \npatch listed in the Forum patch module for more details.\n\n
\nThis patch contains changes to the VBECS Blood Bank package. Refer to the \npatch listed in the Forum patch module for more details.\n\n
\nVBEC*1*54 is exported as part of the VistA Blood Establishment Computer \nTherefore, to allow adequate time for impact analysis and testing the \nVBECRPCC\n \nDATA DICTIONARY:\n================\n N/A\n \nREMEDY TICKETS:\n===============\nINC000000923654\nINC000000925197\nchanges prior to installation in Production, it is imperative that Office \nINC000000948143\n \nTEST SITES:\n===========\nDurham, NC \n Heartland-East HCS \n >Marion, IL \n >Poplar Bluff, MO \n >St. Louis, MO \n Milwaukee, WI \nof Information Technology (OIT) Field Operations coordinate the \nSan Diego, CA\nSan Francisco, CA\n \nDocumentation: \n============== \nDocumentation is available for the VBECS package on the \nANONYMOUS.SOFTWARE directory at one of the following Office of \nInformation (OI) Field Offices. Sites will be able to utilize\nDocumentation in either the ".PDF" or "DOCX" format after they extract \nthe ZIP file.\ninstallation of Blood Bank software patches with Pathology & Laboratory \n \nThe preferred method is to FTP the files from:\nDownload.vista.domain.ext\n \nThis transmits files from the first available FTP server. Sites may also \nelect to retrieve documentation directly from a specific server as \nfollows:\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\nMedicine Service staff.\n \nNOTE: The ZIP file listed below will be listed in each of the \nVBECS and LR patches that are part of the VBECS package and associated \npatches. It only needs to be downloaded once.\n \nFile Name Retrieval format: \n=========== ================= \nVBECS_2_0_0_DOCS_BUNDLE.ZIP BINARY \n \n \n \nThe following files are contained in the VBECS_2_0_0_DOCS_BUNDLE.ZIP file \nand will not be individually located on the OI Field Office Anonymous \nDirectories.\n \nThe VBECS_2_0_0_DOCS_BUNDLE.ZIP file needs to be extracted on your \nsystem for use.\n \n=======================================================================\nVeterans Health Administration (VHA) Customer Documents:\nVistA Blood Establishment Computer Software (VBECS) 2.0.0 Release \nThe VBEC*1*54 patch addresses several issues. Refer to the sample \nNotes.docx\nVistA Blood Establishment Computer Software (VBECS) 2.0.0 Release \nNotes.pdf\nVistA Blood Establishment Computer Software (VBECS) 2.0.0 Technical \nManual-Security Guide.docx\nVistA Blood Establishment Computer Software (VBECS) 2.0.0 Technical \nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 2.0.0 User Guide.docx\nVistA Blood Establishment Computer Software (VBECS) 2.0.0 User Guide.pdf\nVBECS Known Defects and Anomalies.docx\nvalidation scenarios listed with the correction to verify changes: \nVBECS Known Defects and Anomalies.pdf\n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system.\nInstallation will take less than 5 minutes.\n \n 1) Use the INSTALL/CHECK MESSAGE option on the PackMan menu to unload\n the KIDS distribution included with this message.\n 2) From the Kernel Installation and Distribution System Menu,\n \n select the Installation menu.\n 3) From this menu, you may elect to use the following options\n (when prompted for the INSTALL NAME, enter VBEC*1.0*54).\n a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n 1. 109 VistA MR 103013 - The CPRS Blood Bank Report, Diagnostic Tests\n c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n d) Print Transport Global - this option will allow you to view \n the components of the KIDS build.\n 4) Use the Install Package(s) option and select the package \n VBEC*1.0*54.\n 5) When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//' respond NO\n 6) When prompted 'Want to DISABLE Scheduled Options, Menu Options, \nSystem (VBECS) Version 2.0.0 release.\n Section has displayed Transfusion Reaction Workup test results\n and Protocols? NO//' respond NO.\n with patient Type and Screen test results. This was not done by\n the legacy blood bank system. The change made to the VBECA1B1\n routine will eliminate Transfusion Reaction Workup test results\n from the Blood Bank Report, Diagnostic Tests Section. Note - the\n Transfusion Reactions Section of the CPRS Blood Bank Report does\n not change and will still display Transfusion Reaction\n Interpretations.\n Associated Remedy Tickets: INC000000923654 and INC000000925197.\n \n \n Verification: Locate a patient with a Transfusion Reaction in VBECS.\n Using this patient run the CPRS Blood Bank Report and note that\n transfusion reaction testing is visible in the Diagnostic Tests\n Section and the Transfusion Reactions Section has an interpretation.\n Install VBEC*1*54. Repeat the lookup of the CPRS Blood Bank Report\n and verify that the transfusion reaction testing is absent in the\n CPRS Blood Bank Report, Diagnostic Tests Section. Verify that the\n Transfusion Reactions Section of the CPRS Blood Bank Report does\n not change and still displays the Transfusion Reaction\n Interpretations after VBEC*1*54 is installed.\nTo meet Food & Drug Administration (FDA) requirements, VBECS related \n \n 2. 110 VistA MR 121713 - VBECS was able to accept a specimen when the\n CPRS order was assigned a Lab accession number as the order was\n added to a collection list and the specimen was not collected (no\n collection date/time). This change requires that the specimen\n accession number must also have a collection date and time in VistA\n before it can be used in VBECS for processing.\n \n Remedy Ticket: INC000000948143\n \nVistA (Veterans Health Information Systems Technology Architecture) \n Verification: Attempt to accept a VBECS order with a blood bank\n specimen that does not have a collection date and time assigned in\n VistA but has been assigned an accession number per a Lab collection\n list. VBECS will allow processing of the specimen UID for an order\n only when the specimen has a date and time collected assigned after\n VBEC*1*54 is installed.\n \n 3. 111 VistA MR 061214 - The release of ICD*18.0*57 started a \n retirement countdown for ICR 3990 used to lookup ICD codes. This \n lookup is used by the LRBLPCH (Patient transfusions & hematology \npatches require customer validation in local Test accounts prior to \n results) option in VistA Blood Bank. No new transfusion \n data has been entered since LR*5.2*408 (compliance date August 18, \n 2011) was installed to turn off VistA Blood Bank. The end \n result is that the LRBLPCH option is obsolete and the change to \n ICD codes is not relevant. The LRBLPCH option will be placed out \n of order with the installation of this patch.\n \n Verification: Any attempt to execute the option will return a\n message that it is out of order.\n \ninstallation in Production. The user validates the Blood Bank software \n 4. 112 VistA MR 111914 - Workload configuration and details are not\n maintained in the development accounts which results in errors when\n the workload process is triggered. Minor changes to the VistA \n workload code prevents the workload process from proceeding when \n there is no workload to process. Changes to the VBECRPCC routine\n will prevent the error caused when there is no workload to process.\n \n Verification: None\n \n \nfor its intended use prior to its acceptance and use for patient care.\nThere is also a VistA Blood Establishment Computer Software (VBECS) \n2.0.0 server update that is also being released. Please refer \nto the VistA Blood Establishment Computer Software (VBECS) 2.0.0 \nRelease Notes for detailed information about corrections in that release.\n \n \nBLOOD BANK CLEARANCE: \n=====================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch VBEC*1*54 contains \nchanges to a package referenced in BBM TEAM REVIEW OF VISTA PATCHES. \n \nThis patch does not alter or modify any VistA Blood Bank software design \nsafeguards or safety critical elements functions.\n \nRISK ANALYSIS: Changes made by patch VBEC*1*54 have no affect on Blood \nBank software functionality, therefore RISK is none.\n \nROUTINE:\n========\nVBECA1B1\nVBECRPCB\n\n
\nVBEC*1*0 is being exported as part of the VBECS_BUNDLE_1.KID package \n \n assigned as a Secondary Menu Option.\n \n \nPROTOCOL:\n=========\n VBECS ADT-AO8 CLIENT - This protocol is used to deliver HL7 messages\n from VistA to VBECS via the VBECSPTU logical link.\n \n VBECS ADT-A08 ROUTER - This protocol is used to receive an HL7 message\n from the VAFC ADT-A08 SERVER protocol and executes routing logic to\nI. OVERVIEW\n determine whether the message is to be forwarded to VBECS. VBECS\n receives only messages that contain changes to various patient\n demographic data.\n \n VBECS ADT-AO8 SERVER - This event driver protocol is triggered by the\n \n VBECS ADT-A40 CLIENT - This protocol is used to deliver the HL7\n message from VistA to VBECS via the VBECSPTM logical link.\n \n VBECS ADT-A40 SERVER - This event driver protocol is triggered by the\nThe VistA Blood Establishment Computer Software (VBECS) shall facilitate \n \n \n VBECS OMG CLIENT - This is the subscriber protocol to the VBECS OMG\n SERVER protocol that receives the HL7 message from VBECS providing\n order updates to the original order message.\n \n VBECS OMG SERVER - This protocol is triggered when an HL7 message from\n VBECS is received by the HL7 package.\n \nHL7 APPLICATION PARAMETER:\nongoing compliance with Food and Drug Administration (FDA) standards for \n==========================\n VBECS - This HL7 Application represents the VBECS side of the VBECS/CPRS \ninterface.\n \n VBECS ADT - This HL7 Application represents the receiving application\n of the Patient Update and Patient Merge router protocols.\n \n VBECS TRIGGER - This HL7 Application represents the VBECS side of the\n Patient Update and Patient Merge interfaces.\n \nmedical devices and enhance the Department of Veterans Affairs (VA) \nHL LOGICAL LINK:\n================\n VBECS-OERR - Used to transmit HL7 messages from VBECS to CPRS.\n \n VBECSPTM - Used to transmit HL7 messages from VistA to VBECS when a\n patient merge event occurs.\n \n VBECSPTU - Used to transmit HL7 messages from VistA to VBECS when a\n patient update event occurs.\n \nVeterans Health Administration's (VHA) ability to deliver quality \nPARAMETER DEFINITION:\n=====================\n VBECS VISTALINK - Parameter definition used to identify all VBECS \nParameters.\n \nPARAMETERS:\n===========\n LISTENER IP ADDRESS - Stores the value of the Blood Bank medical\n device server where the VistALink listener is installed.\n \nservices to meet the needs of the user community. VBECS is considered an \n LISTENER PORT NUMBER - Stores the value of the port number where Blood\n Bank medical device VistALink listener is listening.\n \n These Parameters are used by M APIs to build the XML messages used by \nVistALink.\n VBECS Blood Products\n VBECS DSS Extract\n VBECS Order Entry\n VBECS Patient ABID\n VBECS Patient ABO_RH\nencapsulated medical device and therefore does not communicate directly \n VBECS Patient Available Units\n VBECS Patient Report\n VBECS Patient TRRX\n VBECS Patient Transfusion History\n VBECS Update Workload Event\n VBECS Workload\n \nREMOTE PROCEDURE:\n=================\n VBECS ACCESSION AREA LOOKUP\nwith other VistA applications.\n VBECS BLOOD BANK USER LOOKUP\n VBECS DIVISION LOOKUP\n VBECS DSS EXTRACT\n VBECS HCPCS CODES LOOKUP\n VBECS HOSPITAL LOCATION LOOKUP\n VBECS LAB ACCESSION UID LOOKUP\n VBECS LAB ORDER LOOKUP BY UID\n VBECS LAB TEST RESULTS LOOKUP\n VBECS LABORATORY TEST LOOKUP\n VBECS MED PROFILE LOOKUP\n \n VBECS PATIENT LOOKUP\n VBECS PROVIDER LOOKUP\n VBECS WORKLOAD CODES LOOKUP\n \nGLOBALS - FILES:\n===============\n ^VBEC(6002.01, - VBECS WORKLOAD CAPTURE File (#6002.01)\n \n ICRs:\n =====\nrelease. The installation of this bundle will be controlled by phase \nTwo new namespaces are being introduced into the VistA enterprise with \n The following ICRs were created to allow data transfer between the Blood \nBank medical device and the VBECS Application Interfacing Support \nsoftware.\n 4607, 4608, 4609, 4610, 4611, 4612, 4613, 4614, 4615, 4616, 4617,\n 4618, 4619, 4620, 4621, 4622, 4623, 4624, 4625, 4626, 4627, 4628, 4633\n \n The following ICRs were created, or modified, to allow data transfer \nbetween the VBECS Application Interfacing Support software and other \nVistA applications.\n 1587, 1963, 2400, 2503, 2817, 3176, 3177, 3181, 3631, 3879, 4629,\nthe release of VBECS. The first, gov.va.med.vbecs, represents the Blood \n 4636, 4766, 4767, 4773, 4774, 4776, 4779,\n \nASSOCIATED REMEDY TICKETS\n=========================\n N/A\n \nTEST SITES:\n===========\n HEARTLAND-EAST HCS\n PHILADELPHIA, PA\nBank medical device software. The second, VBEC, represents the VBECS \n SAN DIEGO, CA\n \nSACC Exemptions:\n================\nXINDEX displays the following warning. The Standards And Conventions \nCommittee granted an exemption to allow the use of a star read on May 4th \n2006.\n \nVBECRL * * 114 Lines, 4099 Bytes, Checksum: B10917646\n FOR READ VBECX#VBECREAD:VBECTO SET TOFLAG=$T DO:VBECFRST CHK \nApplication Interfacing Support software. The VBEC namespace, created in \nDO:'VBECS\n TOP QUIT:DONE\n READ+6 I - Star or pound READ used.\n \nInstallation Sequence \n======================\nThe files listed below represent the patches that will be part of the \ncontrolled phased release. Follow the sequence listed below when your \nphased installation occurs.\n \nthe VBEC 1.0 KIDS build, will be added to the Package file in VistA and \n 1. LR*5.2*335\n 2. LR*5.2*367\n 3. VBECS Bundle (consisting of VBEC*1*0 and LR*5.2*325)\n 4. VBEC*1.0*1\n 5. OR*3.0*212\n \nDocumentation Retrieval:\n \nDocumentation is available for the entire VBECS package on the \nANONYMOUS.SOFTWRE directory at one of the following Office of Information \nis used to identify the M software and files that support interfacing \n(OI) Field Offices. Sites may retrieve documentation in either ".PDF" or \n"DOC" format in one of the following ways:\n \n1. The preferred method is to FTP the files from :\nDownload.vista.domain.ext\n \n2. Sites may also elect to retrieve documentation directly from a \nspecific server as follows:\n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\nother VistA applications with the Blood Bank medical device. This \n Salt Lake City ftp.fo-slc.domain.ext\n \nNOTE: The documentation files listed below will be listed in each of the \nVBECS and LR patches that are part of the VBECS package and associate \npatches, they only need to be downloaded once.\n \nFile Name Retrieval format: Binary\n=========== ==========================\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.doc\nsoftware is not released as part of the Blood Bank medical device.\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nADPAC Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nInstallation and User Guide.pdf\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.doc\nBlood Bank Pre-Implementation Data Validation, Mapping, and Conversion \nTechnical Manual.pdf\n \nVBECS Data Conversion Recommended Validation Method.xls\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.doc\nVBECS Application Interfacing Support Software Installation and User \nConfiguration Guide.pdf\nVBECS Implementation Process.xls\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Installation \nGuide.pdf\nII. FUNCTIONAL OVERVIEW\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 Technical \nManual-Security Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.doc\nVistA Blood Establishment Computer Software (VBECS) 1.4.0.0 User Guide.pdf\nKnown Defects and Anomalies.doc\nKnown Defects and Anomalies.pdf\n \nINSTALLATION INSTRUCTIONS:\nrelease. An Implementation Manager will be assigned to your site and \nThe reengineered Blood Bank system uses VistALink and Health Level Seven \n==========================\n \n Pre-Installation Items:\n =======================\n \n Environment Check:\n ------------------\nProgrammer access is required to install this patch. Prior to \ninstallation, the installer must ensure the DUZ(0) node of the DUZ array \nis set to the "@" symbol.\n(HL7) messaging for data exchange with a client-server mode application \n \n Users on the System:\n --------------------\n This patch may be installed with users on the system.\n \n Software Installation Time:\n ---------------------------\n The estimated installation time for this patch is less than \n 5 minutes during non-peak hours.\n \ninterfacing architecture through M Application Programmer Interfaces \n Queuing:\n ---------\n Note: Patch installation requires responses from the installer and\n must not be queued.\n \n Pre-requisites:\n ---------------\n Patch installer must enter the collection sample types for new Lab\n tests created during installation. Obtain sample types from the\n Laboratory Information Manager\n(APIs), VistA Remote Procedure Calls (RPCs), and HL7 interfaces released \n \n Namespace:\n ----------\n The namespace for the VBECS Application Interfacing Support package is:\n Name: VBECS - Prefix: VBEC\n \n Required Patches:\n -----------------\n Application Patch/Build\n ----------------------------- -----------\nin the VBEC 1.0 KIDS build.\n Laboratory Services LR*5.2*187\n LR*5.2*288\n LR*5.2*294\n Toolkit XT*7.3*58\n \n New File and Global Information:\n --------------------------------\n There is one new global, ^VBEC. The ^VBEC global contains the\n following new file.\n Journaling\n \n File # File Name Global Root Recommended\n ------ ------------------------ ------------ -----------\n 6002.01 VBECS WORKLOAD CAPTURE ^VBEC(6002.01, YES\n \n VBECS Configuration Checklists:\n -------------------------------\n a. Complete Appendix D: Configuration Checklist of the VistA Blood\n Establishment Computer Software (VBECS) Installation Guide.\n b. Complete Appendix B: Configuration Worksheet of the VBECS \n Application Interfacing Support Software Installation and User\nThis software will provide a transparent database transition through the \n Configuration Guide.\n \n Installation Steps:\n ===================\n \nThe installation of VBECS and its related patches are being handled as a \ncontrolled release. The implementation manager will contact you with the \nlocation of the KIDS Host Files prior to your scheduled installation \ndate. The documentation files will be available for download in advance \nof installation through the anonymous download site.\nuse of M APIs, RPCs, and HL7 interfaces. The APIs released in this build \n \n 1. Use the 'LOAD A DISTRIBUTION' option (#1) on the 'KIDS INSTALLATION'\n menu, and enter: VBECS_BUNDLE_1.KID \n \n 2. From the 'Kernel Installation & Distribution System' menu, select\n the Installation menu.\n \n 3. From this menu, you may now elect to use the following options (when\n prompted for INSTALL NAME, enter VBECS BUNDLE 1.0)\n \nwill allow other VistA applications to continue the retrieval of Blood \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - This option will allow you\nBank data stored in the Blood Bank system. The RPCs will allow the Blood \n to ensure the integrity of the routines that are in the\n transport global.\n \n d. Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n \n 4. Use the Install Package(s) option and select package\n VBECS_BUNDLE_1.KID. This will automatically install VBEC*1*0\n and LR*5.2*325\n \nwill contact your POC for VBECS and will provide your site with the \nBank system to continue to retrieve data from other VistA applications. \n 5. When prompted "Enter the Coordinator for Mail Group 'VBECS INTERFACE\n ADMIN':", please enter the name of the individual that will be\n responsible for maintaining the new mail group. This mail group\n receives notifications when an HL7 transmission, or a query through\n the VBECS VistALink client, to the Blood Bank medical device has\n failed. The users added to this group would be Lab/Blood Bank\n supervisors and/or IRM staff responsible for managing the VBECS\n package and interfaces.\n \n 6. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\nThe HL7 interfaces will allow the exchange of data between the Blood Bank \n Install? NO//', respond Yes.\n \n 7. When prompted 'VBECS Server IP Address:', enter the Cluster\n IP address from Appendix B: Configuration Worksheet, Hardware\n Information, row 1.\n \n 8. When prompted 'VBECS VistALink Listener Service Port Number:',\n enter the VistALink Listener Service port number from\n Appendix B: Configuration Worksheet, Hardware Information, row 2\n for installing in the TEST account, row 3 for installing in the\nsystem and other VistA applications.\n PRODUCTION account.\n \n 9. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n No//', it is recommended you answer NO.\n \n 8. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? No//', respond NO\n \n 11. When prompted by "Select COLLECTION SAMPLE for Lab Test\n ABO/RH - LAB:," select the collection sample appropriate for the\n \n ABO/Rh test.\n \n 12. When prompted by "Select COLLECTION SAMPLE for Lab Test ANTIBODY\n SCREEN - LAB:," select the collection sample appropriate for the\n Antibody Screen test.\n \n 13. When prompted by "Select COLLECTION SAMPLE for Lab Test DIRECT\n ANTIGLOBULIN TEST - LAB:," select the collection sample appropriate\n for the Direct Antiglobulin Test test.\n \nIII. TECHNICAL COMPONENTS\n 14. When prompted by "Select COLLECTION SAMPLE for Lab Test TRANSFUSION\n REACTION WORKUP - LAB:," select the collection sample appropriate\n for the Transfusion Reaction Workup test.\n \n 15. When prompted by "Select COLLECTION SAMPLE for Lab Test \n TYPE & SCREEN - LAB:," select the collection sample appropriate for\n the Type & Screen test.\n \n 16. The POST Installation routine VBECPOST will be deleted from\n your system automatically after successful installation.\nThis section lists the components of the VBECS, and LAB SERVICES \ninstalled in VistA by the VBEC BUNDLE 1.0 Multi Package KIDS build that \nsupports VBECS.\n \n \nlocation of the KIDS Host Files prior to your scheduled installation date \nMAIL GROUP:\n===========\n VBECS INTERFACE ADMIN - Receives alert mail messages when problems \narise with VBECS Application Interfacing. The users added to this group \nwould be Lab/Blood Bank supervisors and/or IRM responsible for managing \nthe VBECS package and interfaces.\n \nROUTINES:\n=========\nVBECA1\nInstallation Sequence. The VBECS BUNDLE is a host file that consists of \nVBECA1A\nVBECA1B\nVBECA1B1\nVBECA3\nVBECA3A\nVBECA3B\nVBECA3C\nVBECA4\nVBECA5A\nVBECA5B\nboth VBEC*1*0 and LR*5.2*325. Installation of the VBECS BUNDLE will \nVBECA6\nVBECA7\nVBECA7A\nVBECA7A1\nVBECA7B\nVBECENV\nVBECHLRT\nVBECLU\nVBECLU0\nVBECLU3\nautomatically install both VBEC*1*0 and LR*5.2*325\nVBECPOST\nVBECRL\nVBECRPC\nVBECRPC1\nVBECRPCA\nVBECRPCB\nVBECRPCC\nVBECRPCD\nVBECRPCE\nVBECRPCH\n=====================\nVBECRPCM\nVBECRPCP\nVBECRPCW\nVBECVLC\n \n \nOPTION:\n=======\n VBECS VISTALINK CONTEXT - (B)roker type option used by VistALink to\n authenticate users. All Blood Bank users must have this option\n\n
\nThis patch (VBEC*2*1) is being released in conjunction with the Vista \nThe VistA patch is released with a seven (7) day compliance date.\n=======================================================================\nVeterans Health Administration (VHA) Customer Documents:\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 Release \nNotes.docx\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 Release \nNotes.pdf\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 Technical \nManual-Security Guide.docx\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 Technical \nManual-Security Guide.pdf\n \nVistA Blood Establishment Computer Software (VBECS) 2.3.0 User Guide.docx\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 User Guide.pdf\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 Admin User \nGuide.docx\nVistA Blood Establishment Computer Software (VBECS) 2.3.0 Admin User \nGuide.pdf\nVBECS Known Defects and Anomalies.docx\nVBECS Known Defects and Anomalies.pdf\n \n \nBLOOD BANK CLEARANCE\n \nPATCH INSTALLATION:\n===================\n \nPre/Post installation Overview:\n===============================\nRefer to the VistA Blood Establishment Computer Software (VBECS) 2.3.0 \nRelease Notes document for pre and post installation information and \ninstructions.\n \n====================\nPre-Installation Instructions:\n==============================\nCreate a test with the following information prior to patch installation.\n \nNAME: VBEC PATIENT REFLEX TEST TYPE: NEITHER\n SUBSCRIPT: WORKLOAD HIGHEST URGENCY ALLOWED: ROUTINE\n PRINT NAME: VBEC PATIENT REFLEX CREATION DATE: <Use current date>\n \nInstallation Instructions:\n==========================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch VBEC*2*1 contains \nThis patch may be loaded with users on the system.\nInstallation will take less than 5 minutes.\n \n 1) Use the INSTALL/CHECK MESSAGE option on the PackMan menu to unload\n the KIDS distribution included with this message.\n 2) From the Kernel Installation and Distribution System Menu,\n select the Installation menu.\n 3) From this menu, you may elect to use the following options\n (when prompted for the INSTALL NAME, enter VBEC*2*1).\n a) Backup a Transport Global - this option will create a backup\nchanges to a package referenced in VHA OI SEPG SOP 192-023 Review of \n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n d) Print Transport Global - this option will allow you to view \nVISTA Patches for Effects on VISTA Blood Bank Software. This patch does \n the components of the KIDS build.\n 4) Use the Install Package(s) option and select the package \n VBEC*2*1.\n 5) If prompted 'This Patch is for Version 2, you are running\n Version 1 Want to continue installing this build? No//' respond \nYES.\n 6) When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//' respond NO.\n 7) When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' respond NO.\nnot alter or modify any VistA Blood Bank software design safeguards or \nsafety critical elements functions.\n \nBlood Establishment Computer Software (VBECS) VBECS 2.3.0 server patch.\nRISK ANALYSIS: Changes made by patch VBEC*2*1 have no adverse effect on \nVistA Blood Bank software functionality, therefore RISK is none.\n \nVALIDATION REQUIREMENTS:\n========================\nThe VBECS 2.3.0 update and VBEC*2*1 require customer validation in the \nlocal Test account prior to installation in Production to meet Food & \nDrug Administration (FDA) requirements. The user validates the Blood Bank \nsoftware for its intended use prior to its acceptance and use for patient \ncare. The VBECS 2.3.0 Release Notes contain descriptions of the changes \n \nmade in this patch and includes validation scenarios.\n \nIt is imperative that the installation of VBEC*2*1 occur prior to the \ninstallation of the VBECS 2.3.0 server patch. Coordinate the installation \nwith Pathology & Laboratory Medicine Service staff to allow adequate time \nfor impact analysis and testing the changes prior to installation in \nProduction.\n \nFiles & Fields Associated:\n==========================\nInstallation of this patch will have no effect on sites who have not \nN/A\n \nFORMS ASSOCIATED:\n=================\nN/A\n \nMAIL GROUPS ASSOCIATED:\n=======================\nN/A\n \ninstalled VBECS.\nOPTIONS ASSOCIATED:\n===================\nN/A\n \nPROTOCOLS ASSOCIATED:\n=====================\nN/A\n \nSECURITY KEYS ASSOCIATED:\n=========================\n \nN/A\n \nTEMPLATES ASSOCIATED:\n=====================\nN/A\n \nADDITIONAL INFORMATION:\n=======================\nN/A\n \nA full description of the VistA patch changes and implementation process \nNEW SERVICE REQUESTS (NSRS):\n============================\nN/A\n \nPATIENT SAFETY ISSUES (PSIS):\n=============================\nN/A\n \nDEFECT TRACKING SYSTEM TICKET(S) & OVERVIEW:\n============================================\nare included in the VBECS 2.3.0 Release Notes.\nI5868220FY15\nI7744342FY16\nI6114955FY16\nI7083226FY16\nI17762673FY18\n \nTEST SITES:\n===========\nMILWAUKEE, WI\nPHILADELPHIA, PA\n \nSAN FRANCISCO, CA\nHINES, IL\nIOWA CITY, IA\n \nDOCUMENTATION RETRIEVAL INSTRUCTIONS:\n=====================================\nDocumentation describing the new functionality introduced by this patch \nis available. Documentation can be found on the VA Software Documentation \nLibrary at: https://www.domain.ext/vdl/application.asp?appid=182\n \n\n
\nThis patch (VBEC*2*3) serves to alert VA facilities using the Vista Blood \n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system.\nInstallation will take less than 5 minutes.\n \n 1) Use the INSTALL/CHECK MESSAGE option on the PackMan menu to unload\n the KIDS distribution included with this message.\n 2) From the Kernel Installation and Distribution System Menu,\n select the Installation menu.\n 3) From this menu, you may elect to use the following options\nA full description of patch changes and implementation process are \n (when prompted for the INSTALL NAME, enter VBEC*2*3).\n a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\nincluded in the VBECS 2.3.1 Release Notes.\n transport global.\n d) Print Transport Global - this option will allow you to view \n the components of the KIDS build.\n 4) Use the Install Package(s) option and select the package \n VBEC*2*3.\n 5) When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//' respond NO\n 6) When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' respond NO.\n \n \nBack-Out Plan\n -------------\n During installation, if the option to back up routines was run as \n directed, "Backup a Transport Global", then routines will have the \n ability to be restored from the "backup" MailMan message that was \n generated. However, the KIDS installation process does not perform a \n restore of other VistA components, such as data dictionary, \n cross-reference, and template changes, etc. \n \n Prior to attempting a back-out of the software, submit a YOUR IT \nThe patch is released with a sixty (60) day compliance date.\nServices \n ticket with the Enterprise Service Desk (ESD) for assistance with the \n procedure. \n \n For VistA patches, the general strategy for back-out is to repair the \n code with another follow-on patch. Depending on each individual patch, \n sites will be given a procedure detailing how to complete the back-out.\n \n If any issue(s) with the software are discovered after it is nationally \n released the development team will research the issue and provide \n \n guidance for any immediate, possible work around.\n \n Long-term solutions will be one of the following: installation of a \n follow-up patch to correct the defect, a follow-up patch to remove the \n defective updates, or a procedure detailing how the software can be \n safely backed out of the production system.\nBLOOD BANK CLEARANCE\n====================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch VBEC*2*3 contains \nchanges to a package referenced in VHA OI SEPG SOP 192-023 Review of \nEstablishment Computer Software (VBECS) that VBECS 2.3.1 server patch has \nVISTA Patches for Effects on VISTA Blood Bank Software. This patch does \nnot alter or modify any VistA Blood Bank software design safeguards or \nsafety critical elements functions.\n \nRISK ANALYSIS: Changes made by patch VBEC*2*3 have no adverse effect on \nVistA Blood Bank software functionality, therefore RISK is none.\n \nVALIDATION REQUIREMENTS:\n========================\nThe VBECS 2.3.1 server patch requires customer validation in the local \nbeen released for installation.\nTest account prior to installation in Production to meet Food & Drug \nAdministration (FDA) requirements. The user validates the Blood Bank \nsoftware for its intended use prior to its acceptance and use for patient \ncare. The VBECS 2.3.1 Release Notes contain descriptions of the changes \nmade in this patch and includes validation scenarios.\n \nIt is imperative that the AITC coordinate the installation of the VBECS \n2.3.1 server patch with Pathology & Laboratory Medicine Service staff to \nallow adequate time for impact analysis and testing the changes prior to \ninstallation in Production.\n \n \nPRIORITY:\n=========\nMandatory\n \nCategory:\n=========\nRoutine\nInformational\n \nSites who have not installed VBECS have no action to take with this patch.\nCOMPONENTS:\n===========\nRoutines:\n VBEC2P3\n VBECHLRT\n \nDEFECT TRACKING SYSTEM TICKET(S) & OVERVIEW:\n============================================\nINC1232882 - update to the VBECS Blood Product Code file\n \n \nTEST SITES:\n===========\nIowa City\nMilwaukee\nSan Diego\n \nDOCUMENTATION RETRIEVAL INSTRUCTIONS:\n=====================================\nDocumentation describing the new functionality introduced by this patch \nis available. (.docx and .pdf files)\nVBECS 2.3.1 will be installed by System Administrators at the Austin \n \nVeterans Health Administration (VHA) Customer Documents:\nVistA Blood Establishment Computer Software (VBECS) 2.3.1 Administrator \nUser Guide\nVistA Blood Establishment Computer Software (VBECS) 2.3.1 Release \nNotes.docx\nVistA Blood Establishment Computer Software (VBECS) 2.3.1 Technical \nManual-Security Guide.docx\nVistA Blood Establishment Computer Software (VBECS) 2.3.1 User Guide.docx\nVBECS 2.3.1 Known Defects and Anomalies.docx\nInformation Technology Center (AITC). Please refer to VBECS 2.3.1 Release \n \nDocumentation can be found on the VA Software Documentation Library at: \nhttp://www4.domain.ext/vdl/\n \n \nPATCH INSTALLATION:\n===================\n \nPre/Post installation Overview:\n===============================\nNotes for details.\nRefer to the VistA Blood Establishment Computer Software (VBECS) 2.3.1 \nRelease \nNotes document for pre and post installation information and instructions.\n \nPre-Installation Instructions:\n==============================\nRefer to the VistA Blood Establishment Computer Software (VBECS) 2.3.1 \nRelease \nNotes document for pre and post installation information and instructions.\n \n\n
\nThis patch installs updates to the Computerized Patient Record System \n \nNew Service Requests (NSRs):\n----------------------------\n20170604: CPRS Blood Bank Report \n \nWork Items:\n-----------\n214353 CPRS CQ# 19382: Need to update the VAIS and DBIA 4623\n434646 VistA - Fixing canned comments on tests sent to VistA\n822792 NSR 20170604: CPRS Blood Bank Report\n906324 Transmit the ABO/Rh of Transfused Units to CPRS for Display in\nA full description of patch changes, implementation process, and \n the CPRS Blood Bank Report\n939717 Update VBECS VistA MailMan server to report VBECS VistA version\n 2 patches\n970431 Replace Expiration Date with Issued Date/Time on the CPRS Blood\n Bank Report in the Available/Issued Units section\n1093252 Remove reaction strengths for DAT tests from CPRS blood bank\n report.\n1186563 CPRS Blood Bank Report does not differentiate tests completed\n on the same date/time\n \nvalidation scenarios are included in the VBECS 2.3.2 Rev F Release Notes.\n1230175 Add reference range for ABS and DAT to CPRS Blood Bank Report\n1247284 Cancelled orders remain in Component Requests section CRPS\n Blood Bank Report\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nN/A\n \nTest Sites:\n-----------\nTBD\n \n \nSoftware and Documentation Retrieval Instructions:\nThe Test and Production accounts will be installed separately. There is \n \nDocumentation describing the new functionality introduced by this patch \nis available on the VA Software Documentation Library at:\nhttp://www.domain.ext/vdl/application.asp?appid=182\n \nRefer to the VBECS 2.3.2 Rev F Release Notes for a list of the user \ndocumentation associated with this revision letter patch.\n \nAdditional VBECS information can be accessed on the VBECS SharePoint site \nat: https://dvagov.sharepoint.com/sites/oitepmovbecs\nno downtime associated with this patch installation. Refer to the VBECS \n \n \n \nPatch Installation:\n-------------------\n \nPre-Installation Instructions:\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \n2.3.2 Rev F Release Notes for further installation details.\nminutes to install.\n \nNo options need to be disabled during installation.\n \n \nInstallation Instructions:\n \n 1. Choose the PackMan message containing this build. Then select the\n INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n \n 2. From the Kernel Installation and Distribution System Menu, select the\n Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global option to confirm \n the integrity of the routines that are in the transport global.\n When prompted for the INSTALL NAME enter the patch name VBEC*2.0*8.\n \n B. Select the Backup a Transport Global option to create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates. \n \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n ii. Compare Transport Global to Current System - This option\n will allow you to view all changes that will be made when\n this patch is installed. It compares all of the components\n of this patch, such as routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the patch to\n \n install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\n of Install? NO//', answer No\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//', answer No\n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? NO//', answer No\n(CPRS) BLOOD BANK REPORT.\nPatch Components:\n \nPost-Installation Instructions:\n N/A\n \nBack-Out/Roll Back Plan:\n------------------------\n This patch consists of five routines. During the VistA Installation \n Procedure the installer should back up the modified routines by the\n use of the 'Backup a Transport Global' action (step 2B in\n the Installations Instructions).\n-----------------\n \n If rollback/backout is required, the installer can restore the routines\n using the MailMan message that were saved prior to installing the\n patch.\n \n If assistance is needed to rollback/backout the patch, please log a\n Service Now ticket.\n \n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \n \n \nForms Associated:\n \nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\nN/A\n \n \nMail Groups Associated:\n \nThis patch also serves to alert VA facilities using the Vista Blood \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nN/A\nEstablishment Computer Software (VBECS) that VBECS 2.3.2 Rev F server \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \n \nSecurity Keys Associated: \npatch has been released for installation. VBECS 2.3.2 Rev F will be \n \nSecurity Key Name\n-----------------\nN/A\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\ninstalled by System Administrators at the Austin Information Technology \n \n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\nN/A\n \n \nParameter Definitions Associated:\nCenter (AITC). \n \nParameter Name New/Modified/Deleted\n-------------- --------------------\nN/A\n \n \nAdditional Information:\n-----------------------\n \nBlood Bank Team Coordination:\n \n-----------------------------\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch VBEC*2*8 contains \nchanges to a package referenced in VHA OI SEPG SOP 192-023 Review of \nVISTA Patches for Effects on VISTA Blood Bank Software. This patch does \nnot alter or modify any VistA Blood Bank software design safeguards or \nsafety critical elements functions.\n \nRISK ANALYSIS: Changes made by patch VBEC*2*8 have no effect on VistA \nBlood Bank software functionality, therefore RISK is none.\n \n\n
\nThis package, VBECS, exists in the M environment to\nperform integrity checks on existing VistA Blood Bank\ndata, convert relevant data for migration to parallel\napplications, and to migrate VistA data to parallel\napplications when specific application events are\ntriggered.\n\n
\nSee patch MMRS*1*1 in the National Patch Module on FORUM for complete \ninformation on this patch.\n\n
\nThis patch addresses one issue:\n \nThe discharge format of the MRSA IPEC Report sometimes incorrectly displays\nthe BDOC (Number of bed days of care for the unit) total.\n\n
\n1) TICKET 604438\n \nThe patch modifies the MRSA Program Tools (MRSA-PT) Isolation Report \n(MMRS REPORTS MENU) to list any patient with any of the mapped \netiologies/sensitivities. Prior to installation, the report only lists\npatients for one (1) mapped etiology/sensitivity. The patch modifies two \n(2) routines in the MRSA-PT application.\n\n
\nRefer to National Patch Module.\n\n
\nThe patch addresses one (1) issues:\n \n1. Many facilities report that the MDRO Tool CDI Report is \n running very slowly. This is occurring because the report\n is examining a large set of microbiology results for every \n patient including those that fall outside of the date range\n specified at report run time.\n\n
\nRefer to the National Patch Module.\n\n
\nPlease see patch description on FORUM.\n\n
\nBackup of MMRS*1.0*9 on May 17, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issues:\n \n1. After invoking the option "MMRS MRSA WARD MAPPING SETUP", the ward \n locations might not be mapped to the division specified by the user.\n \n2. After invoking the option "MDRO TOOLS LAB PARAMETER SETUP", the \n parameters might not be mapped to the division specified by the user.\n\n
\nVHA Directive 2007-002, MRSA Prevention Initiative, requires facilities to\nscreen patients on Admission, subsequent Transfer(s), and Discharge.\nFacilities are required to report compliance rates with Nares Screening on\nAdmission to the Facility and Unit(s) and on Discharge. This information\nalso determines the Prevalence and Transmission rates of MRSA. Data is\nreported monthly to the Inpatient Evaluation Center (IPEC). The purpose\nofthe software will allow facilities to extract MRSA data for reporting\npurposes.\n\n
\nVA's NHIN product supports the VA's business initiatives for\nThe VA NHIN system will access the VA MPI to retrieve\npatient demographics and the VA Vista(s) to retrieve patient\nmedical information. Version 1.0 of the NHIN supports these\nmedical domains: Patient Problem List Patient Allergies \nPatient Medications (Pharmacy All Out-Patient Pharmacy).\n\nThe VA NHIN system accesses this information in the form of\na HITSP CCD or (C32) Continuity of Care Document.\n\nThe VA NHIN also provides the VA ROI office with support for\nthe increased exchange of health information between VA and\nthe patient authorizations process with a web page for the\nConsumer Preferences and Policy Management System. \n\nnon-VA providers (other government and private sector health\norganizations) that are providing care to veterans because\nit is estimated that 3 out of 4 veterans receive care from\nnon-VA providers.\n\nThe VA NHIN system provides VistaWeb with access to the\navailable patient medical information provided by the NHIN.\n\n
\nThis is the initial installation of the Emergency Department Information \nSystem (EDIS). This is the module that handles tracking of a patient \nthrough an emergency department visit. The user interface for this \napplication is a web application.\n\n
\nThis patch addresses an issue with multiple patient record flags causing \nan error at WRITE+4^XOBVSKT.\n\n
\n1. INC15787506 - EDIS v2.2 patient movement issues which caused patient \nedited or re-added to the board as the application still considered them \nas being on the board.\n \n Technical Explanation:\n ----------------------\nOn the room select boxes used in the popups, on the CPE screen, using the \n"click" event to capture changes to the selection which works properly if \nyou click directly on the list item you want to change to. If for some \nreason you miss clicked on the select boxes but did not click on a list \nitem it was still triggering the click event and which was causing the \nto disappear from EDIS display board.\nsave functionality to run but doing so with the default value, in the \ncase of room bed that is 0 which was the patient ghosting. \n \n Resolution:\n -----------\nThe click method which updates the room has been changed to no longer \ndefault to "0". The VistA routine EDPQDB has been updated to \ndisplay any existing patients with a LOC field entry of "0" as being on \nthe default room set by the TRACKING AREA File (231.9) field INITIAL \nROOM. A pre-install routine will close all ambulance patients and named \n \npatients older then 5 days with a LOC of "0". \n Problem:\n --------\nWhen moving a patient between rooms the patient would in some cases \ndisappear from the board. These patient entries when viewed in VistA \nwould display in file #230 (ED LOG) as having a LOC field (3.4) entry of \n"0". When a patient disappears from the board they are unable to be \n\n
\nPatch EDP*2.0*16 addresses the following defects:\n \n1.INC15877607 - Unverifiable order created when pharmacy processes/edits\nmedication orders.\n \n Problem:\n --------\nWhen an outpatient pharmacy order is created in CPRS then edited in VistA \noption "PSO LM BACKDOOR ORDERS" the "New" column in EDIS counts an \nadditional order more than it should on the CPE screen. \n \n \n Technical Explanation:\n ----------------------\nIn the EDIS Mumps code anytime a new order is created it is automatically \nassumed to be a new order regardless of its status. When some fields are \nedited in pharmacy backdoor such as dosage, instead of editing the \ncurrent order a new order is created. This order is sent to routine \nEDPFMON where EDIS checks the status of the HL7 message sent from \npharmacy. The current code does not check to see if the order is an \nedited order or an actual new order, so it adds the edited order as it \nwas a new order. In file #230 (ED LOG) you can see both the original and \n1.INC15877607 - Unverifiable order created when pharmacy processes/edits\nedited order.\n \n Resolution:\n -----------\nEDIS will now check to see if the order already exist and will check to \nsee if the order is an "Active" or "New" order before updating the "New" \ncolumn. \n \n2.INC12684952 - EDIS is passing a provider pointer of 0 to DATA2PCE.\n \nmedication orders.\n Problem:\n --------\nThere is currently a defect in the Document Storage Systems (DSS) \nsoftware which is creating "V" Purpose of Visit (POV) entries that have a \nprovider narrative pointer of 0. These V POV entries are picked up in \nEDIS where they cause the system to error when the Activity Report is run.\n \n Technical Explanation:\n ----------------------\nThe "0" entry is in file #9000010.07 V POV field (#.04) PROVIDER \n2.INC12684952 - EDIS is passing a provider pointer of 0 to DATA2PCE.\nNARRATIVE, EDIS uses this file to retrieve the diagnosis name for a \npatient when the Activity Report is run. An undefined error occurs in \nroutine EDPQPCE when 0 is passed and EDIS attempts to assign this value \nto a variable. \n \n Resolution:\n -----------\nEDIS will now check for null values to prevent undefined errors. \nAdditionally, if the name pointer is invalid EDIS will use the diagnosis \nInternal Entry Number (IEN) to retrieve the name from the ICD Diagnosis \n3.JIRA-418 - Remote Procedure Calls (RPC) added to EDIS menu option.\nfile (#80). \n \n3.JIRA-418 - Remote Procedure Calls (RPC) added to EDIS menu option.\n \n Problem:\n --------\nThe current login configuration for EDIS uses VIA code which is slated \nfor decommission and must be changed. \n \n Resolution:\n \n -----------\nMultiple RPCs from the kernal namespace are being added to the EDIS \noption EDPF TRACKING SYSTEM to login to the application instead \nof using the VIA system.\nDefect Tracking System Tickets(s) & Overview:\n=============================================\n\n
\nPatch EDP*2.0*20 addresses the following issues:\n \n1. INC21639750 - EDIS board is displaying old (discharged) patients on \nthe board as if they are currently being seen in the ER.\n2. JIRA EDIS-458 - Update Mumps code to remove direct references to the \nORDER File #100 and replace with ORX8 API.\n\n
\nPatch EDP*2.0*23 is the VistA component of the new Emergency Department \nPatch EDP*2.0*24 will release to update EDIS's Graphic User Interface \n(GUI) to utilize these changes.\nIntegration Software (EDIS) features and adds the following enhancement \ncapabilities:\n \n1.EDIS-592 - Admittance time delay calculation.\n2.EDIS-697 - Add door to doctor time to row data.\n3.EDIS-623, 624, 626 - Waiting room board configurable text fields I, II, \nIII\n \n\n
\nPatch EDP*2.0*29 is the Vista component for patch EDP*2.0*28. The \nEmergency Department Integration Software (EDIS) will require this patch \ninstalled in order to support the new login methods made by patch 28.\n\n
\nThis patch is one part of a GUI patch that contains fixes for the issues \nWhen a Room/Bed is marked as never display any patient assigned to that\nRoom or Bed will disappear from the CPE board. This occurs because the \ndrop down boxes that Rooms/Beds can be selected from still included those \nthat are marked to not be displayed on the board. Once this happens the \nonly way to find the patient is to move their location in VistA or mark \nthe Room/Bed as visible on the Board through the configuration page.\n \nResolution:\n-----------\nAdded a check to exclude Rooms/Beds from the Room/Bed selection drop \nlisted below:\ndown when the field "DISPLAY WHEN" (FILE #231.8 FIELD .07) is set as\n"Never". \n \n2. INC33193019: Delay Summary Report Changes. \n \nProblem:\n--------\nOn the "Delay Summary Report" in the reports tab there are several \nchanges the business required to be made for certain metrics and layout. \nFirst the headers needed to be more defined so users can distinguish \n \nbetween the various data types. Second various metrics have had their \ntime values adjusted.\n \nResolution:\n-----------\nAdded underlining to the headers for "All ED Visits", "VA Admitted", and \n"Not VA Admitted". Changed the labels on the JAVA GUI and data values for \nthe following:\n \nAll ED Visits:\n \n"Total Visits Over Six Hours" to "Total Visits Over 240 Minutes"\n \nVA Admitted:\n"Total Visits Over Six Hours" to "Total Visits Over 360 Minutes"\n"Average Delay Time" to "Average Admit Delay Time"\n"Number of Admit Delays Over Six Hours" to "Number of Admit Delays Over \n150 Minutes"\n \n1. INC36508590: Patient stuck in a hidden room in EDIS. \n \nProblem:\n--------\n\n
\nEDIS-1210 change the following for accessing a sensitive record from\n"Are you sure you wish to continue?" to "Do you want to continue accessing\nthis patient record?"\n\n
\n1) EDIS-1252 - Integrated site fix for scheduling applications.\nassume the user is always at the primary site regardless of which \ndivision the clinic they are trying to add the patient to.\n \nTechnical explanation:\n--------\nIn the Mumps code where EDIS listens to the SDAM APPOINTMENT EVENTS \nprotocol for patient check-ins the site value for the check-in uses the \nlocal variable DUZ(2). This value is from the CONNECTOREDIS proxy account \nthe EDIS JAVA GUI uses to add information to Vista. The problem is sites \nonly have one of these accounts and it is typically located in the \n \nprimary site. As the example above states if the connector proxy account \nis at 561 then EDIS uses it's DUZ(2) value even for patients at 561A4. \nSince the correct site code is never assigned to that patient they never \nappear in the other division's display board. \n \nResolution:\n-----------\nEDIS now adds patients to sites based on the clinics location rather than \nthe location of the connector proxy account. \nProblem:\n--------\nScheduling applications Vista Scheduling Graphic User Interface (VS GUI) \nand Integrated Scheduling Solution (ISS) are not supported for integrated \nsites with multiple divisions by EDIS. For example, if a site like 561 \nhas another division 561A4 it is currently not possible to add the \npatient in the 561A4 site in EDIS. This happens because EDIS is coded to \n\n
\nThis patch addresses an issue with multiple patient record flags causing \nan error at WRITE+4^XOBVSKT.\n\n
\nThis patch resolves multiple reported errors and issues within EDIS.\n\n
\nEDIS Patch Description (EDP*2.0*2) \n \nEDPFAA\nEDPRPT1\nEDPRPT2\nEDPRPT7\nEDPRPT7C\nEDPRPT10\nEDPRPTBV\nEDPQLE\nEDPLPCE\n \nEDPQPCE\nEDPFLEX\nEDPLEX\nEDPX\nEDPLOG\nEDPCONV\n \nPre/Post Installation Overview\n------------------------------\nLEX*2.0*80 must be installed prior to this patch\nRoutines\nICD*18.0*57 must be installed prior to this patch\nEDP*2.0*6 must be installed prior to this patch\nPX*1.0*199 must be installed with this patch (prior to or after). \n \nInstallation Instructions\n-------------------------\nThis patch may be installed with users on the system, although it is \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \nminutes to install.\n--------\n \n \nPre-Installation Instructions\n-----------------------------\n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option.\n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\nThe second line of each of these routines now looks like:\n following option. When prompted for the INSTALL, enter the patch #\n (EDP*2.0*2):\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n back up any other changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n;;2.0;EMERGENCY DEPARTMENT;**6,2**;Dec 3, 2012;Build 1\n (routines, DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install. Enter EDP*2.0*2.\n \n5. When prompted Want KIDS to Rebuild Menu Trees Upon Completion of\nOr\n Install? NO//, respond NO.\n \n6. When prompted Want KIDS to INHIBIT LOGONs during the install? NO//,\n respond NO.\n \n7. When prompted Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//, respond NO.\n \n8. If prompted Delay Install (Minutes): (0 - 60): 0//, respond 0.\n \nThe second line of each of these routines now looks like:\nPost-Installation Instructions\n------------------------------\nEDPCONV may need to be run if this is an upgrade from prior to EDIS 1.0.\n;;2.0;EMERGENCY DEPARTMENT;**2**;Dec 3, 2012;Build 1\n\n
\nThis patch corrects 1 issue within the EMERGENCY DEPARTMENT package:\n \n* ED LOG fields have ICD 9 references that need to be removed\n\n
\nThis patch corrects 2 issues within the EMERGENCY DEPARTMENT package:\n \n1. I10849240FY16 - Users who have never been assigned an EDIS staff role \n see Assess and Visit buttons in triplicate.\n \n2. I10842158FY16 - The Shift Report is generating incorrect data.\n\n
\nThis patch corrects 2 issues within the EMERGENCY DEPARTMENT package:\n \n1. An error in a site's error-trap occurs, when an EDIS user attempts to \n edit and save a patient's record, and that record ultimately contains\n "null" in the CPT procedure narrative field.\n \n2. Duplicate primary providers are appearing on encounters.\n\n
\nThe following menu options will have the VIAB WEB SERVICES OPTION added \n EDPF TRACKING VIEW STAFF Assign Staff\n EDPF TRACKING VIEW TRIAGE Triage Patient\n EDPF TRACKING VIEW UPDATE Update Tracking Board\n \nThe remote procedure XUS DIVISION SET will be added to the following \noption.\n \n EDPF TRACKING SYSTEM\nto ensure 2FA functionality.\n \n EDPF TRACKING VIEW BOARD Display Board\n EDPF TRACKING VIEW CONFIGURE Configure Tracking Board\n EDPF TRACKING VIEW DISPOSITION Disposition Patient\n EDPF TRACKING VIEW EDIT CLOSED Edit Closed Patient\n EDPF TRACKING VIEW REPORTS Tracking Reports\n EDPF TRACKING VIEW SIGNIN Sign In Patient\n\n
\nBackup of EDP*2.0*15 on Jun 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n \nEDIS Version 2.0, full build.\n\n
\nThis is the Emergency Department Information System (EDIS).\n\n
\nPatch XOBW*1*4. Please refer to NPM for more detail.\n\n
\nThis is the initial version of the HealtheVet Web Services Client (HWSC) \napplication.\n \nThe functionality contained in this application allows VistA applications\nto access remote web services.\n\n
\nThe Virtual Patient Record (VPR) monitors a VistA system for new data\nand activity, and makes that data available to a subscribing client.\n\n
\nThis patch will resolve the following issues in the VPR package:\nOutpatient Medications\n \n1. The XML return from the "Allergy/Adverse Reaction Tracking" type does \nnot include the "entered" date field if the allergy is "No known allergy".\n \n2. The routine VPRDGMRA has unnecessary code that is potentially \ndangerous.\n \n3. The initial Fill date is missing from the VPR XML output for \n\n
\nThis patch extends the Virtual Patient Record (VPR) application, to \nretrieve the requested data.\n \nThis patch also installs a mechanism to monitor clinical data events in \nVistA, to enable retrieval of updated information as a patient's data\nchanges. New Protocol file (#101) entries will be added, and linked to\nappropriate clinical application events; the file and record numbers\nmodified will be collected in the new VPR Subscription file (#560) until\nretrieved and updated.\n \n \nprovide a new method of retrieving patient health data from a Veterans\nPatch Installation:\n-------------------\nSoftware is being released as a host file, DI_222_9_VPR_1_8.KID. The host\nfile contains two patches; DI*22.2*9 and VPR*1*8. Refer to Patch \nDI*22.2*9 for installation instructions.\n \nPatches DI*22.2*9 and VPR*1*8 are scheduled to be released nationally as a\nbundle. Installation of these patches into Production within the first 5\ndays from the National Release date is requested. The VA leadership has \nasked for an expedited release to comply with the schedule for the high\nHealth Information Systems (VistA) database.\nprofile Mission Act. Certain functionality has to be loaded into\nproduction in 130 VA Medical Centers within a short timeframe. We\nappreciate your cooperation.\n \n \nBackout Procedures:\n-------------------\nBack-out will be done only with the concurrence and participation of the \ndevelopment team, health product support, and appropriate VA site/region \npersonnel. All components exported by the patch (excluding linked \n \nProtocol menus) are new and could be removed from the system if needed.\nPlease call the national help desk or enter a help desk ticket for\nassistance.\nPatch DI*22.2*9 released a new VA FileManager utility that provides the \nability to map VistA files and fields to other data models, and extract \nthat data as XML or JSON objects. This VPR patch will populate the new \nEntity file (#1.5) to map VistA data elements to InterSystems' Summary \nData Architecture (SDA) model, and use the new supported calls to \n\n
\nPARTIAL FILL ON SAME DAY DOES NOT DISPLAY\n\n
\nEmergency Patch to correct incident INC9096091 with undefined errors in\nVPR PTF entity.\n\n
\nThe Virtual Patient Record (VPR) provides a data extract RPC to return\ndata as requested from the local VistA system.\n\n
\nThis patch will resolve the following issues in the Virtual Patient \nRecord (VPR)\npackage:\n \n1. INC8143771 - Wrong medication displaying on Essential Med List \nand JLV; OEL^PSOORRL API used incorrectly\n\n
\nBackup of VPR*1.0*25 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe Virtual Patient Record (VPR) data extract RPC, which returns data\nfrom the local VistA system, is updated in this patch.\n\n
\nThis patch adds the following:\n \nVitals routine VPRDGMV was inadvertently left out of patch VPR*1*33. \nRe-added in this patch.\n\n
\nJLV and VLER support\n\n
\nThis patch to the Virtual Patient Record (VPR) package updates the VPR GET \n * Orders\n * Problems\n * Wellness Reminders (new)\n \n \nDocumentation Retrieval\n-----------------------\nDocumentation can be found on the VA Software Documentation Library:\n http://www4.domain.ext/vdl/\n \nPATIENT DATA remote procedure call (RPC) that extracts patient health data \n \nPatch Installation\n------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 1 minute \nto install.\n \n1. Choose the PackMan message containing this patch.\n \nfrom a Veterans Health Information Systems and Technology Architecture \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME, enter VPR*1.0*5.\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD?s or templates.\n b. Compare Transport Global to Current System - This option will\n(VistA) database in Extensible Markup Language (XML) format, requested by \n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD?s, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \nthe Joint Legacy Viewer (JLV) and Virtual Lifetime Electronic Record (VLER) \n5. When prompted ?Want KIDS to Rebuild Menu Trees Upon Completion of \n Install? NO//? enter NO.\n \n6. When prompted ?Want KIDS to INHIBIT LOGONs during the install?\n NO//? enter NO.\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//? enter NO.\n \n8. If prompted ?Delay Install (Minutes): (0 ? 60): 0// respond 0.\nprojects. Data domains updated are:\n * Demographics\n * Functional Independence Measurements (new)\n * Immunizations\n\n
\nThis patch updates the VPR GET PATIENT DATA remote procedure call \n(RPC). It will now parse for the ASCII BELL character among other\ninvalid ASCII characters.\n\n
\nThis patch address one ticket: INC1583647. The problem is that the \nRadiology Contrast Media allergy isn't showing up on the JLV display.\n\n
\nPlease see the National Patch Module entry for VPR*1*11 for details.\n\n
\nThe Virtual Patient Record (VPR) monitors a VistA system for new data\nand activity, and makes that data available to a subscribing client.\n\n
\nThis application contains utilities to build and manage a copy of the\npatient's record, including local and remote data. The authoritative\ncopy of the data will continue to be each local VistA service.\n\n
\nNursing Admission Assessment, Reassessment, and Interdisciplinary Plan \nof Care.\n\n
\nVA Point of Service (VPS KIOSKS).\n\n
\nThis patch corrects the check-in time stored in the SDES APPOINTMENT file \n(#409.84) when veterans check in through the VetLink kiosks.\n\n
\nVA Point of Service (VPS KIOSKS).\n\n
\nVPS*1*4 includes:\n1. New RPC to Print Patient Wristband with option to print EDIPI/SSN\nbarcode\n2 New RPC to print Patient label with option to print EDIPI/SSN barcode \n3. New RPCs to integrate with Howdy package\n4. New RPC to integrate with Patient Clinical Reminders\n5. Enhancement to Patient Demographic\n\n
\nThis patch\n\n
\nThe VistA Integration Adapter (VIA) team needs to create two new proxy\nand the new Application Proxy is implemented by the post-init routine\nVIABRPC5. After successful installation, the site will need to\nmanually create the Connector Proxy utilizing Foundations Manager\nas detailed in the Post-Installation instructions.\n \n \n \n************************ Important Information ***********************\n** **\n** Note: A VistaLink listener port needs to be open, available and **\nusers in order to connect via VistALink and to allow Remote Procedure\n** maintained by each production site. **\n** **\n** Note: The host name/address and VistALink port must be correctly **\n** defined in the VistALink **\n** gov.va.med.vistalink.connectorConfig.xml file **\n** **\n**********************************************************************\nCalls (RPC) to be invoked. These users are VIABCONNECTORPROXY,VIAB\nfor the Connector Proxy and VIABAPPLICATIONPROXY,VIAB for the\nApplication Proxy. In addition, a new menu option is created.\n \nIn order to implement the changes required for this patch, a\ncombination of patch updates and post-installation steps are required.\nThe new VIAB WEB SERVICES OPTION option is installed by the patch\n\n
\nVIAB*1.0*15\nthat omission.\n \n(2). Moves LISTORDERS on the 'AF' cross reference\n \n(3). Uses DATE/TIME ORDERED in LISTORDERS and LISTORDERACTIONS compare \n \nChanges include:\n \n(1). Add a $GET to ORDACT2+4^VIABMS4\nThe remote procedure VIABMS contains a target LISTORDERACTIONS that \nfilters orders by ORDER ACTION. When checking the STATUS field which is \ndefined on the 3-node of the file, it does not include a $GET to protect \nagainst the possibility that the node might not be present. This corrects \n\n
\nThis patch changes the GETACT tag in VIABMS to gather all dispositions \nwith the flag "VA".\n\n
\nThis patch adds the RPC SDEC APPSLOTS for odd clinic start times to \nthe VIAB WEB SERVICES option to register this RPC. See ICR 7071 for \napproval to call the RPC.\n\n
\nThis patch fixes the following COVID-19 VIA applications:\n1. Bed Management Solutions (BMS). [ListOrderActions] fix when Order \n Text field has '[' in its result.\n2. Adds a new RPC to the REMOTE PROCEDURE CALL file (#8994), VIAB GETDEM\n to return patient demographic data using the PIMS supported DEM^VADPT\n API call.\n3. Adds RPC VIAB GETDEM to VIA's VIAB WEB SERVICES OPTION option.\n\n
\nADD RPC VIAB PATCH, SO THAT VIAB WEB SERVICES CAN DETERMINE WHEN VISTA \nPATCHES ARE PRESENT. EX: OR*3.0*524\n\n
\nBackup of VIAB*1.0*21 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe VistA Integration Adapter (VIA) team needs to create two new proxy\nand the new Application Proxy is implemented by the post-init routine\nVIABRPC5. After successful installation, the site will need to\nmanually create the Connector Proxy utilizing Foundations Manager\nas detailed in the Post-Installation instructions.\n \n \n \n************************ Important Information ***********************\n** **\n** Note: A VistaLink listener port needs to be open, available and **\nusers in order to connect via VistALink and to allow Remote Procedure\n** maintained by each production site. **\n** **\n** Note: The host name/address and VistALink port must be correctly **\n** defined in the VistALink **\n** gov.va.med.vistalink.connectorConfig.xml file **\n** **\n**********************************************************************\nCalls (RPC) to be invoked. These users are VIABCONNECTORPROXY,VIAB\nfor the Connector Proxy and VIABAPPLICATIONPROXY,VIAB for the\nApplication Proxy. In addition, a new menu option is created.\n \nIn order to implement the changes required for this patch, a\ncombination of patch updates and post-installation steps are required.\nThe new VIAB WEB SERVICES OPTION option is installed by the patch\n\n
\nPCE changes brought on by PX*1.0*211 require changes for mobile \napplications. This patch will change the return for saveNoteandEncounter \nservice of Vista Integration Adapter to provide better messaging for the\ncalling application. However, this patch is NOT dependent on PX*1.0*211. \nThe return array may contain some new values if PX*1.0*211 is present. \n\n
\nDescription:\ncharacters, LIST^DIC returns an 'overflow' error "The data requested for\nthe record is too long to pack together." and the result doesn't pass over\nto BMS.\n \nResolution: In an effort to pass the result to BMS, the text will get \ntruncated after 3675 characters with the trailing tag:\n \n"<*NOTE: order text reached max length, please check appropriate system \nfor full order text*>"\n===========\n \nThis patch addresses the return text value from the Bed Management System\n(BMS) LISTORDERACTIONS call when the result string exceeds a number of \ncharacters.\n \nProblem: LISTORDERACTIONS uses the LIST^DIC call within its code. If the\nsize of the Order's Order Text field is too wordy and exceeds a number of\n\n
\nThe VistA integration Adaptor (VIA) project requires access to certain \nRemote Procedure Calls (RPCs). The purpose of this patch is to publish\nthose RPCs in the OPTION file (#19), RPC field (#320) which allows VIA\nto access.\n\n
\nVista Integration Adapter enhancements updates for Increments 1 and 3. \nUpdated VIAB WEB SERVICES OPTION to include new RPC's. Added 3 new RPC's.\n\n
\nAdd proxy user for eHMP\n\n
\nRoutine HMPTFU2, converted from VAFCTFU2.\n\n
\nMerge S68 changes into eHMP.\n\n
\nEnterprise Health Management Platform Package Release.\n \nSee FORUM patch description for details.\n\n
\nVTCM INITIAL INSTALLATION\n\n
\nScheduling Calendar View initial build.\n\n
\nScheduling Calendar View initial build.\n\n
\nVSE-3285 - VistA: Correct <COMMAND> error in MBAARPC2\nROUTINE: MBAAAPI1\nProblem: \nA <COMMAND> error is being encountered when the CPRS STATUS of \nthe appointment being cancelled is not equal to SCHEDULED. The current \ncode quits without returning back a required value.\nResolution: \nModified the code to return back 0 (variable RETURN) when returning \nback. This will prevent the <COMMAND> error.\n \n\n
\nThis build is the initial installation release of the VistA Package \nSizing Utility.\n\n
\nThis Real Time Location System (RTLS) patch provides the foundation\nfor the interface between WaveMark and legacy VistA packages by creating\nan application proxy user and a common menu that will contain\nfuture Remote Procedure Calls (RPC) for multiple packages and files in\nVistA. The menu option will be assigned as secondary menu to the\napplication proxy user created. The RPC menu exported by this patch may be\nexpanded in future patches with other new RPC lists for other VistA \npackages.\n\n
\nThis Real Time Location System (RTLS) patch provides the foundation\nfor the interface between WaveMark and legacy VistA packages by creating\nan application proxy user and a common menu that will contain\nfuture Remote Procedure Calls (RPC) for multiple packages and files in\nVistA. The menu option will be assigned as secondary menu to the\napplication proxy user created. The RPC menu exported by this patch may be\nexpanded in future patches with other new RPC lists for other VistA \npackages.\n\n
\nThis Real Time Location System (RTLS) patch supports the interface \nwith WaveMark with new functionality for the Catheterization Lab which\ninvolves the following VistA packages:\n \n- IFCAP/GIP: obtaining item master updates for WaveMark from IFCAP.\nSetting par values from WaveMark into GIP, and setting the quantity\non-hand in GIP.\n- Employee/Patient: retrieving employee (file #200) and patient (file #2)\ninformation for WaveMark.\n\n
\nThis build supports the RTLS interface between Intelligent Insites\norder to hold Engineering changes momentarily while they are sent to \nRTLS. Once the changes are transmitted, the file is cleaned up.\n \nThe changes from Engineering files are transmitted to RTLS via the option \nVIAA MAKE A WEB CALL TO MULE. This option should be scheduled to run in \nTaskMan periodically. See the patch description in Forum for additional \ndetails on how to set it up.\nand the VistA Engineering files #6914 and #6928. A list of remote\nprocedure calls (RPC) is exported with this patch as part of the\ninterface. The RPC list will be added to the common VistA option\n'VIAA01 RTLS RPC MENU'. At the post-init phase, the patch checks and if\nneeded completes the set ups for a web server and a web service used to \ncommunicate with RTLS.\n \nThe new file PENDING RTLS EVENTS, #6930, is exported with this patch in \n\n
\nThis patch addresses one issue about a syntactically incorrect error \noccurring in the interface with the EQUIPMENT INV. FILE #6914 via the\nDecision Support System (DSS) GUI AbovePAR (APAR) system.\n\n
\nSix new national domain entries need to be added in the DOMAIN (#4.2) \nfile.\n\n
\nThis patch will fix a reported issue in FORUM where it is receiving \nthousands of mail messages from every site. The issue is being caused by \nthe 'GOV' domain in file DOMAIN (#4.2) which has a field RELAY DOMAIN \n(#2) in the DOMAIN (#4.2) file of 'DOMAIN.EXT', and the field SYNONYM \n(#.01) in sub-file SYNONYM (#5) in file DOMAIN (#4.2) of the domain \n'DOMAIN.EXT' when the field is 'GOV'.\n\n
\nTwo new national domain entries need to be added in the DOMAIN (#4.2) \nfile.\n\n
\nEnterprise Terminology Services 1.0 - LOINC Database Definitions and \nroutines\n\n
\nRxNorm routines and Database Definitions. Also includes some LOINC\nupdates.\n\n
\nEnterprise Terminology Services 1.0 - LOINC Database Definitions and \nroutines\n\n
\nJLV*2.8*3 - add RPCs to JLV Webservice. Please read the patch desciption \nfor more details.\n\n
\nJLV*2.8*5 - added XUS SET VISITOR and ORWLR CUMULATIVE REPORT RPCs to JLV\nWebservice. Please read the patch desciption for more details.\n\n
\nThis patch will add the new COVID-19 Identifier RPC ORWPT2 COVID to the\nJLV WEB SERVICES menu option.\n\n
\nJLV*2.9*1 adds needed RPCs to the JLV WEB SERVICES option, and removes \nmultiple RPCs no longer needed. In addition the CURRENT VERSION field of\nthe PACKAGE(#9.4) file will be updated to 2.9 for the JOINT LEGACY VIEWER\nentry.\n\n
\nThe purpose of patch KMP*4.0*0 is to deploy the VistA Business Event \nto collect metrics using standard InterSystems provided APIs.\nMonitor (VBEM) as part of the Capacity Management (KMP*) VistA System\nMonitor (KMPV) tools suite. T VBEM will collect Cache metrics for VistA\nfunctions (Menu Options, TaskMan Jobs and Remote Procedure Calls) such\nthat they can be used in conjunction with metrics collected via other\ndeployed capacity management tools. This functionality will replace\ncurrent Resource Utilization Monitor (RUM) functionality.\n \nThis patch also updates the existing VistA Timed Collection Monitor (VTCM)\n\n
\nInstalls version 3 of the VistA System Monitor. This includes real time \ndata transmissions and the addition of the Coversheet and Errortrap \nmonitors.\n\n
\nConfigurations needed to run efficiently on IRIS VistA systems.\n\n
\nThis patch is intended to fix a number of small defects in VistA System \nMonitor code.\n\n
\nWeb VistA Remote Access Management (WebVRAM) Initial Release\n\n
\nThe description of this build can be found in the National Patch Module \nunder WEBG*1*3.\n\n
\nThe CPRS Team will no longer send the Mental Health dll in the CPRS \npackaged releases. \n \nTo prepare for this change in the CPRS release process, the WebVRAM \nProduct will programmatically determine which version of the Mental \nHealth dll needs to be launched for a WebVRAM user at any given site. \n \nThe Mental Health RPC, YTQ VERSRV, will be added to the WEBG WEBVRAM GUI \nuser-context option, which is covered by ICR 7418.\n\n
\nThe Computerized Patient Record System (CPRS) Team will no longer \nThe new WebVRAM Remote Procedure Call (RPC), WEBG GMRV VERSRV, will be\nadded to the WEBG WEBVRAM GUI [WEBG WEBVRAM GUI] option.\nsend the General Medical Record Vitals (GMRV) Dynamic-Link Library \n(DLL) in the CPRS packaged releases. \n \nTo prepare for this change in the CPRS release process, the Web VistA \nRemote Access Management (WebVRAM) Product will programmatically \ndetermine which version of the Vitals DLL needs to be launched \nfor a WebVRAM user at any given site. \n \n\n
\nAPAT patch 2 contains fixes to DSSO 2.0 and corresponds to executable\nDSSAPAT 2.3.2.\n\n
\nContains components for the DSS APAT product\n\n
\nThis patch removes checks of the AUTOMATED INVENTORY (GIP) field (#2)\nin the PROSTHETIC SITE PARAMETERS (#669.9) file and INVENTORY FLAG field \n(#10) in the PROSTHETIC HCPCS (#661.1) file.\n\n
\nDSSO*2.0*5 contains enhancements and maintenance to DSSO*2*0 and \ncorresponds to executable DSSAPAT 2.4.3. The main enhancements delivered\nby this patch are modifications to the HL7 extract and the Duplicate \nAppliance Transaction (DAT) Prepopulator and involves conversion of dates \nto HL7 format.\n\n
\nDSSO*2.0*3 contains enhancements and maintenance to DSSO 2.0 and\ncorresponds to executable DSSAPAT 2.5.\n\n
\nContains components for the DSS APAT product\n\n
\nThis patch exports the new option PREA AMPL GUI. This patch also contains\nvalidate that AMPL is an entry in the REMOTE APPLICATION (#8994.5) File,\nand then the VistA can add that user to the NEW PERSON (#200) File without\nuser intervention and return the requested data.\na post-init routine that adds ADVANCED MEDICATION PLATFORM (AMPL) as an\nentry in the REMOTE APPLICATION (#8994.5) File, and links it to the new\nPRE AMPL GUI option. This must occur prior to the release of the full AMPL\nproject. When using the AMPL application, if a user makes a request to see\nVistA data from a VistA instance where the user does not have an entry in\nthe NEW PERSON (#200) File, this VistA system will use the Security\nAssertion Mark-up Language (SAML) token to authenticate the user and\nauthorize that user to view the requested data. Part of that process is to\n\n
\nThis patch exports the new option PREA AMPL GUI. This patch also contains\nvalidate that AMPL is an entry in the REMOTE APPLICATION (#8994.5) File,\nand then the VistA can add that user to the NEW PERSON (#200) File without\nuser intervention and return the requested data.\na post-init routine that adds ADVANCED MEDICATION PLATFORM (AMPL) as an\nentry in the REMOTE APPLICATION (#8994.5) File, and links it to the new\nPRE AMPL GUI option. This must occur prior to the release of the full AMPL\nproject. When using the AMPL application, if a user makes a request to see\nVistA data from a VistA instance where the user does not have an entry in\nthe NEW PERSON (#200) File, this VistA system will use the Security\nAssertion Mark-up Language (SAML) token to authenticate the user and\nauthorize that user to view the requested data. Part of that process is to\n\n
\nThis patch exports a new option that will identify the users who will \noption exported with this patch.\n \n \nThe option will work as follows:\n \nThe stand-alone option, PREA AMPL GUI ACCESS, when invoked creates the\nlist of users that will receive AMPL access based on VistA Security Key\nownership and Person Class affiliation. When the option is run in the test\naccount, the list will only be sent to the person who ran the option, in a\nVistA Mail Message. The message might also be sent in outlook, but that\nreceive access to the Advanced Medication Platform (AMPL) GUI application\ndepends on the mail configuration at each site. When the option is run in\nproduction the user will be given the choice to only send the list to the\nperson who ran the option, or additionally send it to the VA IT EPMO EPMD\nPRE Pharm GUI SSOi Outlook Mail Group that will handle the granting of\nAMPL access to everyone on the list. When the option is run and the list\ngoes to the mail group, the option will be inactivated. The list will not\nbe submitted immediately to get the access granted, so until that time it\nis submitted, the site contact can request changes to the user list by\nmessaging the VA IT EPMO EPMD PRE Pharm GUI SSOi Outlook Mail Group. The\nsite will be notified when the list is submitted. After submission, access\nwhen it is initially installed at each site at a later date.\ncan still be granted to users or removed from users on an individual basis\nby following the steps provided by Appendix A of the PREA Technical\nManual.\n \nThe option uses the following hierarchy to determine the granting of AMPL\naccess:\n \n1) A user is not granted AMPL access if the user has a past date or the \ncurrent date in the TERMINATION DATE Field (#9.2) of the NEW PERSON File\n(#200).\n \n \n2) A user is not granted AMPL access if the DISUSER Field (#7) of the NEW \nPERSON File (#200) is set to '1' (YES) for that user.\n \n3) A user is granted AMPL access if they are assigned any of the following\nVistA Security Keys:\n \n PSORPH\n PSO TECH ADV\n PSD TECH\nOther than verifying successful patch PREA*1*3 installation, no further \n PSD TECH ADV\n PSDRPH\n PSDMGR\n PSJ PHARM TECH\n PSJ RPHARM\n PSJI MGR\n PSJI PHARM TECH\n PSJU MGR\n PSJU RPH\n \naction is required at this time. The AMPL application will be a phased \n4) A user is granted AMPL access if that user has an active entry in the\nPERSON CLASS Subfile (#200.05) of the NEW PERSON File (#200), and that\nPerson Class entry in the PERSON CLASS File (#8932.1) has the text "PHARM"\ncontained in the PROVIDER TYPE Field (.01) or the CLASSIFICATION Field \n(#1). The text "PHARM" can be in uppercase, lowercase, or any combination.\n \n \nNote: Routine PREAPO2 is included in this patch only to correct some minor\nissues to non-executable code to adhere to the M Programming Standards \nand Conventions.\nrollout, and the AMPL Implementation Manager will be in contact with each\nsite at the appropriate time prior to the site's AMPL implementation, and\nwill coordinate with the appropriate site personnel the running of the\n\n
\nThis patch will distribute the Medical Health eScreening (MHE) option\nrequired for the MHE Proxy User.\n\n
\nLighthouse is an API platform that gives developers secure access to the \nVA data they need to build helpful tools and services for Veterans.\n\n
\nThis patch will add non person users to file 200 so the Immunization\nGateway (IZG) and MyHealtheVet (MHV) applications may use IAM established\nauthorization to establish a VistA context.\n\n
\nVeterans Data Integration and Federation Enterprise Platform (VDIF-EP)\nis a standards based, healthcare IT integration and interoperability\nplatform using Intersystems' HealthShare suite of products. It includes\nthe ability to read, write, and share VistA data.\n\n
\nInitialize Package File entry for ISI IMAGING\n\n
\nISI patch 1.1*110 (companion to VA patch 3.0*341) -- ISI Rad; replaces VistARad\n\n
\nClinical Decision Support Platform is the core system to power Clinical\ninteract with electronic health record data, as well as specific\napplications providing clinical decision support such as Covid-19 Patient\nManager (CPM), Lung Cancer Screening Platform (LCSPv2).\n \nThis patch will distribute an updated Option CDSP RPC CONTEXT. The OPTION \nCDSP RPC CONTEXT contains additional RPCs, all of which have new approved \nIntegration Agreements.These additional RPCs will enable new Applications\nto be launched from the Clinical Decision Support Platform as listed below.\n \nLung Cancer Screening Pv2: TIU CREATE RECORD Text Integration Utility and \nDecision Support (CDS) applications. This platform enables rapid\nPXRPC SAVE2 Patient Care Encounter. These RPCs will give the Lung Cancer\nScreening App the ability to create TIU Documents that document actions \ntaken during a LCSPv2 encounter.\n \nPrecision Oncology: ORWPT LIST ALL Order Entry Results Reporting. Get and \nfilter list of patients. This RPC returns a set of patient names for use \nwith a long list box for selection by the user.\n \nClinical Decision Support Platform: VPR GET PATIENT DATA JSON Virtual \nPatient Record. This RPC will be added to supports APPs such as Lung \ndevelopment and deployment of applications that follow Substitutable\nCancer Screening and Precision Oncology. The RPC is to be used as an \nalternative to VPR GET PATIENT DATA, which returns data in XML. There \nare frameworks identified where XML libraries often have vulnerabilities \n(expat and friends) and deserializing XML is more difficult than JSON.\n \nClinical Decision Support Platform: LHS CHECK OPTION ACCESS Lighthouse. \nThis RPC scours Primary Menu Options, Secondary Menu Options and Common \nOptions to determine if the DUZ passed in has access to the option passed \nin.\n \nMedical Applications and Reusable Technologies (SMART) family of \nTask Manager: Several OR Team access RPC are being added to streamline \npatient selection.\nstandards such as SMART on FHIR (Fast Healthcare Interoperability\nResources) and CDS Hooks. CDSP facilitates the launch of CDS applications\nfrom within the VA Electronic Health Record (EHR) - CPRS and Clinical\nContext Management (CCOW) vault patient context synchronization. The\nsystem encompasses technical infrastructure and shared capabilities to\n\n
\nAdds CDSP RPC CONTEXT menu option\n\n
\n \nThe CRMS*1.0*0 patch delivers the necessary components for the support of \nN/A\n \nEntities Associated:\n \nEntity Name New/Modified/Deleted\n----------- --------------------\nCRMS ACTIVITY LOG New\nCRMS ACTIVITY LIST New\nCRMS CMOP LOG New\nCRMS CMOP M New\nthe SalesForce Customer Relations Management (CRM) project, Outpatient\nCRMS COPAY LOG New\nCRMS COPAY LIST New\nCRMS ECME LOG New\nCRMS ECME M New\nCRMS eRX LOG New\nCRMS eRX M New \nCRMS GET TEMPORARY ADDRESS New\nCRMS LABEL LOG New\nCRMS LABELS LIST New\nCRMS LOT EXP New\nPharmacy requirements, on the VistA level. It has been designed to\nCRMS LOT EXP M New\nCRMS PARTIALS LOG New\nCRMS PARTIALS LIST New\nCRMS REFILL LOG New\nCRMS REFILL LIST New\nCRMS TEMP ADDRESS UPDATE New\n \n \nAdditional Information:\n-----------------------\nprovide REST services for the Java scripted calls used by the SalesForce\n \n \nBlood Bank Team Coordination:\n-----------------------------\nN/A\n \n \nNew Service Requests (NSRs):\n----------------------------\nN/A \nUser Interface.\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nN/A\n \n \n \n \nTest Sites:\n-----------\nMiami VAMC, FL\nWest Palm Beach VAMC, FL\n \n \nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\nThe patch releases the necessary Remote Procedure Calls (RPCs) and \nThe software for this patch is being released in a PackMan message.\n \n \nDocumentation describing the new functionality is included in this \nrelease. Documentation can be found on the VA Software Documentation \nLibrary at: https://www.domain.ext/vdl/. Documentation can also be \nobtained at https://download.vista.domain.ext/index.html/SOFTWARE. \n \n \nDocumentation Title File \nENTITY (#1.5) file entries for retrieval of VistA data from a VistA\nName \n---------------------------------------------------------------------\n \n \n \nPatch Installation:\n-------------------\n \n \nPre/Post Installation Overview:\ninstance. The patch supports the operations of the Virtual Care Centers,\n-------------------------------\n \n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \nOutpatient Pharmacy, as well as individual patient-related requests.\n \n \n \nInstallation Instructions:\n \n1. Choose the PackMan message containing this build. Then select \n the INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n \n2. From the Kernel Installation and Distribution System Menu, \nSubject: VCC SALESFORCE CRM SUPPORT\n \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter the patch or build name. \n CRMS*1.0*0\n \n NOTE: Using <spacebar><enter> will not bring up a \n Multi-Package build even if it was loaded \nIn addition, there is a post-install routine that will add the CRMS WEB\n immediately before this step. It will only \n bring up the last patch in the build.\n \n B. Select the Backup a Transport Global option to create \n a backup message. You must use this option for each\n patch contained in the Host File. For each patch you\n can specify what to backup; the entire Build or just\n Routines. The backup message can be used to restore\n just the routines or everything that will restore your \n system to pre-patch condition.\nCHART menu context to the connector proxy user.\n \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n all of the components of this patch, such as \n routines, DDs, templates, etc.\n \n \n D. Select the Install Package(s) option and choose the \n patch to install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//', answer NO.\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \n install? NO//', answer NO.\n \n****NOTE**** There are post-install instructions for setting up the \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//', answer NO.\n \n \nPost-Installation Instructions:\n-------------------------------\nNOTE: The below instructions, for adding the PROXY USER, were included\nin the previous PSO patch POS*7.0*642. If the procedures to add the\nPROXY user were completed after the installation of PSO*7.0*642,\nyou may skip these post-installation steps below.\nconnector proxy user. These MUST be completed for these patch components\n \n******************************* MANDATORY *******************************\nThe designated site representative must contact the deployment team\nthrough the VHAEKH PSO-7-6-42 mail distribution list in Outlook to get the\naccess/verify code for the CONNECTOR PROXY for your site. This will be\nsent encrypted via Outlook.\n************************************************************************* \n \n \nHOW TO SET UP CONNECTOR PROXY USER THROUGH FOUNDATIONS:\nto function. These instructions were also included in patch PSO*7.0*642.\n=======================================================\nUsing Vista Option FOUNDATIONS MANAGEMENT [XOBU SITE SETUP MENU]:\n \n <<< VistALink Parameters >>>\n \n VistALink Version: 1.6 Heartbeat Rate: 180 Latency Delta: 180\n \n <<< VistALink Listener Status Log >>>\n ID Box-Volume Port Status Status Date/Time \nConfiguration \nIf completed during installation of patch PSO*7.0*642, the\n \n \n \n \n \n Enter ?? for more actions\nSP Site Parameters SL Start Listener\nCFG Manage Configurations STP Stop Listener\nCP Enter/Edit Connector Proxy User SB Start Box\nRE Refresh CU Clean Up Log\nPost-installation instructions in this patch may be ignored.\nCM Connection Manager\nSelect Action:Quit// CP Enter/Edit Connector Proxy User \nEnter NPF CONNECTOR PROXY name : PSO,CONNECTOR PROXY\n Are you adding PSO,CONNECTOR PROXY as a new NEW PERSON (the\n198970TH)? No// Y (Yes)\n \nChecking SOUNDEX for matches.\n \n. <different potential matches for each site>\n \n \nType <Enter> to continue or '^' to exit: \nDo you still want to add this entry: NO//Y\nWant to edit ACCESS CODE (Y/N): Y\nEnter a new ACCESS CODE <Hidden>: *********** <Use ACCESS CODE provided \nto your site> \nPlease re-type the new code to show that I have it right: ***********\nOK, Access code has been changed!\nThe VERIFY CODE has been deleted as a security measure.\nYou will need to enter a new VERIFY code so the user can sign-on.\n \n \nPatch Components:\nWant to edit VERIFY CODE (Y/N): Y\n \nEnter a new VERIFY CODE: ************ <Use VERIFY CODE provided to your \nsite>\n \nPlease re-type the new code to show that I have it right: ************\n \n \n \n \n-----------------\nBack-Out/Roll Back Plan:\n------------------------\nDue to the complexity of this patch, it is not recommended for back-out,\nand a restore from a backup of the Transport Global should not be\nattempted. In the event that this patch needs to be backed out, the patch\ninstaller should enter a ServiceNow Ticket. The development team will need\nto issue a follow-up patch in order to comprehensively back-out this \npatch.\n \nRoutine Information:\n \n====================\n \n \nThe second line of each of these routines now looks like:\n ;;1.0;CRMS - VAHC CRM;**0**;SEP 2022;Build 1\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \nCategory: ROUTINE\nForms Associated:\n \nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\nN/A\n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\n OTHER\nN/A\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nCRMS WEB CHART Broker New\n \n \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \n \nSecurity Keys Associated: \n \nSecurity Key Name\nDescription:\n-----------------\nN/A\n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\n \n===========\nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\nCRMS ACTIVITY LOG New\nCRMS CMOP LOG New\nCRMS COPAY LOG New\nCRMS ECME LOG New\nCRMS ERX LOG New\nCRMS GET TEMPORARY ADDRESS New\n \nCRMS LABEL LOG New\nCRMS LOT EXPIRATION New\nCRMS PARTIALS LOG New\nCRMS REFILL LOG New\nCRMS TEMP ADDRESS UPDATE New\n \nParameter Definitions Associated:\n \nParameter Name New/Modified/Deleted\n-------------- --------------------\n\n
\n1. CTX-0798-70193, WBP-0798-20679.\n \n 'Installation' menu, use the following options\n \n Load a Distribution\n Print Transport Global\n Compare Transpsort global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n \n INSTALL NAME: GEC*2.0*17\n ==========\nSITES THAT HAVE NOT INSTALLED PATCH GEC*2.0*16, SHOULD NOT INSTALL THIS\n (Optional) At the prompt: 'Want to DISABLE Scheduled\n Options and Menu Options?' enter NO.\n ==\nPATCH.\n \nSITES THAT HAVE INSTALLED GEC*2.0*16 SHOULD INSTALL PATCH GEC*2.0*17, THIS\nPATCH INCLUDES FIELDS THAT ARE CHANGED BACK TO THEIR ORIGINAL STATE PRIOR\nTO PATCH 16.\n \nSITES THAT HAD PROBLEMS WITH FEE BASIS CODE SHEETS 994.10 AFTER\nINSTALLATION OF GEC*2.0*16, SHOULD INSTALL THIS PATCH. THEN CREATE,\nThis patch(GEC*2.0*17) will correct problems associated with\nMARK, BATCH AND TRANSMIT CODE SHEETS AGAIN TO ENSURE ACCEPTANCE OF\nNEW CODE SHEETS.\n \nALL AMIS CODE SHEETS THAT REJECTED AFTER INSTALLATION OF PATCH GEC*2.0*16\nSHOULD CREATE, MARK, BATCH AND TRANSMIT CODE SHEETS AGAIN TO ENSURE\nACCEPTANCE OF NEW CODE SHEETS.\n \nBelow is listing of fields that were revised.\n \n \npatch(GEC*2.0*16). Patch 16 was designed to allow Generic Code Sheet to\nField number Field name Patch 16 Patch 17\n============ ========== ======== ========\n208 Birth Date mmyyyy mmyy\n209 Entry Date mmyyyy mmyy\n461.17 Year of Pymt yyyy yy\n461.2 Begin Year yyyy yy\n461.21 Begin Month yyyy yy\n461.23 Vendor Inv Yr yyyy yy\n462.06 Header Budget yyyy yy\n462.07 Header End Budget FY yyyy yy\naccept four (4) digits for the year (ex. 1998). These changes were not\n462.24 Delivery Yr yyyy yy\n462.31 Ending Yr yyyy yy\n462.4 Effective Yr yyyy yy\n463.11 Reversal Fisc Yr yyyy yy\n467.04 HDR Accept Yr yyyy yy\n467.09 HDR VI Yr yyyy yy\n467.12 HDR VI Log Yr yyyy yy\n1547 Date of Last Assessment mmyyy mmyy\n1600 Fee Transaction Date mmyyyy mmyy\n2200.01 Date Evaluated mmyyyy mmyy\ncompatible with Austin, TX and certain AMIS code sheets were rejected.\n2200.06 Birth Year yyyy yy\n2200.19 HBHC Admission Date mmyyyy mmyy\n2200.43 Date of Visit mmyyyy mmyy\n2200.5 Discharge Date mmyyyy mmyy\n4267 Fiscal Yr yyyy yy\n4272 Contract Starting Date mmyyyy mmyy\n4273 Contract Termin Date mmyyyy mmyy\n4281 Date of Birth Part 2 mmyyyy mmyy\n4297 Date of Birth Part 3 mmyyyy mmyy\n4350 Period Ending mmddyyyy mmddyy\nPatch GEC*2.0*16 has been entered in error. Patch (GEC*2.0*17) contains\n5007 Patient Date of Birth mmddyyyy mmddyy\n5011 Action Effective Date mmddyyyy mmddyy\n5017 Effective Date '01' Seq mddyyyyy mmddyy\n5025 Medicate for Week of mmddyyyy mmddyy\n5040 Specimen Collection Date mmddyyyy mmddyy\n5063 Counseling Session Date mmddyyyy mmddyy\n \n \n Test Sites:\n ==========\nfields from file 2100 which will allow entry and acceptance of two (2)\n 631 - Northampton, MA\n 674 - Central Texal (Temple)\n \n Routine Summary:\n ===============\n N/A\n \n Checksums:\n =========\n N/A\ndigits for the year (ex. 98). Below are a list of instructions for sites\n \n \n Data Dictionary(s) Name of File\n --------------------------------------------------------\n ^GECS(2100, GENERIC CODE SHEET File\n \n \n Installation Instruction:\n ========================\n 1. This patch can be loaded with users on the system.\nto follow:\n \n 2. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//" respond NO.\n ===\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\n will load the KIDS package into your system.\n \n 4. The patch has now been loaded into a transport global and you will\n use KIDS to install the transport global. On the KIDS menu, under the\n\n
\nAn error can occur with HSIF Revenue Funds during the transmission of the \nAccounts Receivable monthly information to FMS. This error occurs during \nthe transmission of a TR document and is due to the BATCH TYPE field \n(#.7) in the GENERIC CODE SHEET TRANSACTION TYPE/SEGMENT file (#2101.2) \nbeing incorrect.\n \nThis patch corrects that error.\n\n
\nThis patch corrects a problem with the Transfer (TR) document that is \nused to transfer dollars from the MCCF fund to the HSIF fund.\n\n
\nThis patch will resolve an issue with MCCF/HSIF TR documents that are \ntransmitted to FMS. In some instances, references to "TR" will be \nchanged to "CR" in the data that is transmitted. This patch is being \nreleased in conjunction with Accounts Receivable patch PRCA*4.5*178.\n\n
\nThis patch corrects the issue where by an undefined variable error is\noccuring when a user attempts to exit an option by entering a caret (^)\nat the prompt.\n\n
\nThis patch increases the number of possible unique batch numbers that can \nbe generated for modified billing documents being sent to FMS from 1000 \nto 12250.\n\n
\nThis patch changes the retention period for the Generic Code Sheet Purge \noption from 365 days to 7 years.\n\n
\nInactivate code sheet transaction types 994.00, 994.01, 994.02, 994.10,\nand 994.90.\n\n
\nThis patch addresses a change request with the IO variable for the code\nsheet printing in the Keypunch a Code Sheet option running under the\nLinux operating system.\n\n
\n1. Modify 'PRC GECS PURGE' for improved date control \n\n
\n1. Modify GEC document for correct date in CTL segment for IFCAP orders\n and 1358 when Date Committed not in current Fiscal Year\n\n
\n1. BOI-0199-52715.\n Routine GECSTRAN have been revised to correct this problem:\n \n FEN.662.994.10.012899.XXXXXX.$\n ^\n |\n |____ Problem corrected no space.\n \n \nTest Sites:\n==========\n When creating batches via Generic Code Sheet, batches are\nBoise, ID - 531\n \n \nRoutine Summary:\n===============\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;2.0;GCS;**[Patch List}**;Mar 14, 1995\n \n generated with a space:\nChecksums: CHECK^XTSUMBLD\n=========\n \nRtn Nm Chksum Before Chksum Patch List\n------------------------------------------------------------------\nGECSTRAN 9702778 9698310 13,15,20\n \nInstallation Instruction:\n========================\n1. This patch can be loaded with users on the system.\n \n \n2. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\nProtocols? YES//" respond NO.\n ==\n \n3. Routine mapping is NOT recommended for these routines. If you are\nusing routine mapping, review your mapped set and ensure that these\nroutines are NOT in your mapped routine before proceeding and rebuild\nyour map set afterward before reactivating TaskMan.\n \n 089 FEN.531.994.10.0119 99.FB9059.015MXXXXXX.$\n4. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nwill load the KIDS package into your system.\n \n5. The patch has now been loaded into a transport global and you will\nuse KIDS to install the transport global. On the KIDS menu, under the\n'Installation' menu, use the following options\n \n2 Verify Checksums in Transport Global\n3 Print Transport Global\n4 Compare Transport Global to Current System\n ^\n5 Backup a Transport Global\n6 Install Package(s)\n INSTALL NAME: GEC*2.0*20\n ==========\n \n (Optional) At the prompt: 'Want to DISABLE Scheduled\n Options and Menu Options?' enter NO.\n \n6. MSM-DOS Sites - Answer YES to the question 'Want to MOVE routines to\nother CPU's?'. Enter the names of your Computer and Print server(s).\n |\n \n7. If routines were unmapped as part of step 2, they should be returned\nto the mapped set once the installation has run to completion.\n |____ Inappropriate space.\n \n\n
\n1. REN-0698-61170.\n WAS-0398-21559, PUG-0398-51984, BHH-0598-40274, NCH-0898-41263,\n2. Routine mapping is NOT recommended for these routines. If you are\nusing routine mapping, review your mapped set and ensure that these\nroutines are NOT in your mapped routine before proceeding and rebuild\nyour map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nwill load the KIDS package into your system.\n \n4. The patch has now been loaded into a transport global and you will\nuse KIDS to install the transport global. On the KIDS menu, under the\n GAI-0898-31096, BED-0297-11503.\n'Installation' menu, use the following options\n \n2 Verify Checksums in Transport Global\n3 Print Transport Global\n4 Compare Transport Global to Current System\n5 Backup a Transport Global\n6 Install Package(s)\n \n INSTALL NAME: GEC*2.0*19\n (Optional) At the prompt: 'Want to DISABLE Scheduled\n Transactions created when prior year service orders are updated\n Options and Menu Options?' enter NO.\n \n5. MSM-DOS Sites - Answer YES to the question 'Want to MOVE routines to\nother CPU's?'. Enter the names of your Compute and Print server(s).\n \n6. If routines were unmapped as part of step 3, they should be returned\nto the mapped set once the installation has run to completion.\n on IFCAP are being rejected by FMS. Currently these transactions\n are sent in the SO (Service Order Document) format but FMS requires\n updates for accrued documents to be in the AR (Accrual Receiver\n Document) format. Various routines have been revised to accept\n AR type transactions. A new routine GECSAR has been created to\n add 'AR:FMS' entry into file #2101.2, the routine will prompt for\n the following entry:\n When using the 'Mark Batch for Retransmission' option,\n -----------------------------------------------------------------\n D ^GECSAR\n \n Step (1)\n ========\n Enter 'FINANCIAL MANAGEMENT' for Batch Type!\n BATCH TYPE: // <------- User Response\n \n \n Step (2)\n [GECS RETRANSMIT], only batches for the primary division\n ========\n The following data has been added to file #2101.2\n AR:FMS\n FINANCIAL MANAGEMENT\n Y\n FMS ACCRUAL RECEIVER DOCUMENT\n \n Enter RETURN to continue or '^' to exit:\n \n <NOTE TO USER: When the above routine ^GECSAR has completed its update,\n are listed and selectable when trying to retrieve primary\n please delete.> \n \n \n With the acceptance of AR type transactions, a new 'STATUS' to indicate\n 'Final - No Further Activity Allowed' transaction was accepted by FMS\n and no edits, rebuild, or retransmission may occur for any SO/AR\n with a Status of 'F'. This change has taken place in Data Dictionary\n file #2100.1 and field #3. The set-of-codes for field #3 of file\n #2100.1 has been revised as follows:\n \n division with a suffix. Routine GECSMUT2 has been revised.\n Q: queued for transmission\n M: marked for immediate transmission\n T: transmitted to Austin\n E: error in transmission\n A: accepted by FMS\n R: rejected by FMS\n F: final - no further activity allowed <------ New Entry\n \n Data Dictionay Name of File\n -------------------------------------------------\n \n ^GECS(2100.1, GENERIC CODE SHEET STACK FILE \n \n \n \n \n \nTest Sites:\n==========\nReno, NV - 654\nBedford, MA - 518\n2. MOU-1095-31993, COA-1096-21575, CHY-1196-50499, DAN-1096-41015,\nShreveport, LA - 667\nMoutain Home, TN - 621\n \n \nRoutine Summary:\n===============\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;2.0;GCS;**[Patch List}**;Mar 14, 1995\n HUN-1096-21584, LEA-1096-41007, MAR-1196-21134, SHR-1196-71105,\n \nChecksums: CHECK^XTSUMBLD\n=========\n \nRtn Nm Chksum Before Chksum Patch List\n------------------------------------------------------------------\nGECSAR NEW 1499349 19\nGECSUTIL 5890081 6141404 1,19\nGECSSGET 976530 1011350 19\nGECSEDIT 5772540 6464940 2,6,9,14,15,19\n SHR-1096-71255, WIM-0797-21425, LAK-1297-30984, PUG-0397-51302,\nGECSUFMS 9172067 9186149 7,8,15,19\nGECSUFM1 6271178 6285260 4,8,10,19\nGECSSTAA 5608443 5988243 4,5,10,12,19\nGECSSTT1 5092396 5501547 19\nGECSMUT2 4230177 4325832 19\n \nInstallation Instruction:\n========================\n1. This patch can be loaded with users on the system.\n \n\n
\n Y2K Waiver Request ID#:Y2KW0001 Y2K Waiver Status: Approved\n \n \nTest Sites:\n==========\nMuskogee, OK - 623\nTuscaloosa, AL - 679\n \n \nRoutine Summary:\n===============\n This patch may be installed during the Y2K Moratorium, either\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;2.0;GCS;**[Patch List}**;Mar 14, 1995\n \nChecksums: CHECK^XTSUMBLD\n=========\n \nRtn Nm Chksum Before Chksum Patch List\n------------------------------------------------------------------\n BEFORE 12/15/99 or AFTER 1/15/2000. This patch MAY NOT be\nGECSPURG 5541863 5633010 23\nGECSPUR1 6739363 7042889 23\n \n \nInstallation Instruction:\n========================\n1. This patch can be loaded with users on the system. Installation\n will take less than 5 minutes. \n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n installed between 12/15/99 and 1/15/2000(the Y2K Lockdown Period).\n option will load the KIDS package onto your system.\n \n3. Routine mapping is NOT recommended for these routines.\n \n4. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nwill load the KIDS package into your system.\n \n5. The patch has now been loaded into a transport global and you will\nuse KIDS to install the transport global. On the KIDS menu, under the\n'Installation' menu, use the following options\n \n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n INSTALL NAME: GEC*2.0*23\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES//NO\n1. MUS-1299-70853.\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n == \n \n6. If routines were unmapped as part of step 3, they should be returned\nto the mapped set once the installation has run to completion.\n When trying to purge old batches via GENERIC CODE SHEET, routines\n not allowing purge of batches with a suffix. Routine GECSPURG and\n GECSPUR1 has been revised to allow deletion of selected batches.\n\n
\n Y2K Waiver Request ID#:Y2KW0001 Y2K Waiver Status: Approved\n created to allow the below segments to be put into a status of active\n Install Package(s)\n INSTALL NAME: GEC*2.0*24\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n \n and those not listed below will be set to a status of inactive.\n6. AXP Sites - Answer NO to the question "Want to MOVE routines\n to other CPUs?"\n \n7. If the routines were unmapped, the mapped set should be rebuilt\n once the installation has run to completion.\n \n8. AXP and OpenM/Cache Sites Only - Remove TaskMan from a WAIT/STOP state.\n \nSPECIAL NOTE: ACTIVE SEGMENTS\n=============================\n157 - Pharmacy Service - Outpatient Pharmacy\n158 - Pharmacy Service - Inpatient Pharmacy\n171 - Mental Health & Behavioral Sciences - Psych. Service Code Sheet\n174 - Spinal Cord Injury Census Data\n200 - Nursing Service - Manpower Utilization\n this patch may be installed during the Y2K Moratorium, AFTER \n201 - Nursing Service - Man-hours Worked\n218 - Environmental Management - Environmental Care Operations\n219 - Environmental Management - Textile Care Operations\n220 - Environmental Management - Contracted Hours\n290 - Medical Admin. Service - C&P Exams Code Sheet\n334 - Medical Admin. Service - Psychiatry\n335 - Medical Admin. Service - Intermediate\n336 - Medical Admin. Service - Medicine\n337 - Medical Admin. Service - Neurology\n338 - Medical Admin. Service - Rehabilitation Medicine\n 1/15/2000. \n339 - Medical Admin. Service - Blind Rehabilitation\n340 - Medical Admin. Service - Spinal Cord Injury\n341 - Medical Admin. Service - Surgery\n344 - Medical Admin. Service - Non-VA Public Hospitals\n345 - Medical Admin. Service - VA Nursing Home\n346 - Medical Admin. Service - VA Domiciliary\n347 - Medical Admin. Service - Non-VA Civil Hospitals\n348 - Medical Admin. Service - Non-VA Federal Hospitals\n349 - Medical Admin. Service - Community Nursing Home\n350 - Medical Admin. Service - State Domiciliary\n \n362 - Spinal Cord Injury Home Care Unit Data\n363 - Spinal Cord Injury Home Care Special Programs Data\nJ15 - Medical Service - Cardiac Catheterization\nJ19 - Medical Service - Dialysis\nJ42 - Medical Service - SICU\n \nSegment 228 (Medical Admin. Service - Outpatient Care-Visits to Fee\nPhysicians) and Segment 223 (Medical Admin. Service - Staff Visits to\nClinics) will be loaded using external data linkages and will be stored on\nthe VWM Database.\n1. The Austin Automation Center in conjunction with the VHA CIO FO has\n \n \nTest Sites:\n==========\nCleveland, OH - 541\nMartinez, CA - 612\n \n \nRoutine Summary:\n===============\n developed a new interim database called the VHA Work Measurement(VWM)\nThe following routine(s) are included in this patch. The second line of\neach of these routines now looks like:\n \n <tab>;;2.0;GCS;**[Patch List}**;10/4/00\n \nChecksums: CHECK^XTSUMBLD\n=========\n \nRtn Nm Chksum Before Chksum After Patch List\n------------------------------------------------------------------\n System. With the development of this new database only the segments\nGECSSEG New 1165320 24\n \n \nInstallation Instruction:\n========================\nNOTE OF IMPORTANCE:\nRoutine will automatically execute in the Post-Install immediately after\nthe installation of this package. This routine should not be queued to\nrun at a later time.\n \n below will remain in an active status in file #2101.2, while all other\n1. Users are allowed to be on the system during the Installation.\n \n2. Routine mapping is NOT recommended for these routines.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n4. You Do Not need to stop TaskMan or the background filers.\n (AXP Sites - Place TaskMan in a WAIT state.\n OpenM/Cache Sites - STOP TaskMan.)\n segments will be in a inactive status. A new routine GECSSEG has been\n \n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n\n
\n This patch may not be installed during the Y2K Leap Year Lockdown\n===========================\n1. IF YOUR SITE (HAS NOT) INSTALLED PATCH GEC*2.0*24, THEN (DONOT) INSTALL\n THIS PATCH GEC*2.0*25.\n \n2. IF YOUR SITE (HAS) INSTALLED PATCH GEC*2.0*24, THEN PLEASE (DO) INSTALL\n THIS PATCH GEC*2.0*25.\n \n \nTest Sites:\n==========\n period of 2/28/2000 to 3/3/2000.\nOklahoma, City - 635\n \n \n \nRoutine Summary:\n===============\nThe following routine(s) are included in this patch. The second line of\neach of these routines now looks like:\n \n <tab>;;2.0;GCS;**[Patch List}**;2/14/00\n \n \nChecksums: CHECK^XTSUMBLD\n=========\n \nRtn Nm Chksum Before Chksum After Patch List\n------------------------------------------------------------------\nGECSACT New 351621 25\n \n \nInstallation Instruction:\n1. The Austin Automation Center VHA Work Measurement(VWM) System will\n========================\nNOTE OF IMPORTANCE:\nRoutine will automatically execute in the Post-Install immediately after\nthe installation of this package. This routine should not be queued to\nrun at a later time.\n \n1. Users are allowed to be on the system during the Installation.\n \n2. Routine mapping is NOT recommended for these routines. If you\nare using routine mapping, review your mapped set and ensure that\n not be able to accommendate the inactive segments, all segments in\nthese routines are NOT in your mapped routine set before proceeding\nand rebuild your map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n4. You Do Not need to stop TaskMan or the background filers.\n (AXP Sites - Place TaskMan in a WAIT state.\n OpenM/Cache Sites - STOP TaskMan.)\n \n file #2101.2 will be placed in a status of active.\n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s)\n \n INSTALL NAME: GEC*2.0*25\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n \n6. AXP Sites - Answer NO to the question "Want to MOVE routines\n \n to other CPUs?"\n \n7. If the routines were unmapped, the mapped set should be rebuilt\n once the installation has run to completion.\n \n8. AXP and OpenM/Cache Sites Only - Remove TaskMan from a WAIT/STOP state.\nSPECIAL NOTE OF IMPORTANCE:\n\n
\nThis routine corrects a problem with the background job hanging\nwhen trying to set the status.\n\n
\nThis patch will store the mailman error when code sheets are\nnot transmitted.\n\n
\nThis patch contains internal changes to support the Accounts\nReceivable Millenium Bill patch PRCA*4.5*170.\n\n
\nThis package allows for the creation and entry of code sheets;\nthe management of the code sheet from creation to batching to\ntransmission.\n\n
\n This Kernel patch is dependent on MailMan patch XM*7.1*24. Both\n during the install process.\n-KIDS now creates Packman messages in a format that MailMan can\n understand.\n-Two options, 'Recover deleted option set' [XQOOREDO] and 'Toggle\n options/protocols on and off' [XQOOTOG] are now under 'Out-Of-Order\n Set Management' menu.\n-Corrects undefined error when 'Compare Transport Global to Current System'\n option is queued. NOIS OKL-0296-70233 and LAS-0396-60110\n-When a link to Package file doesn't exist during the load process, the\n Install file wasn't being updated with a new link during the install\npatches must be installed at the same time. This patch contains the\n process. This is now corrected.\n-The install process will display a message for each CPU it updates. It\n use to only display a message for the first one.\n===========================================================================\nThis patch can be installed with users on the system, no user should be\nusing KIDS during the install of this patch. MSM sites must manually move\nthe routine XPDIJ to their other CPUs. KIDS cannot automatically move this\nroutine for you.\n \n===========================================================================\nfollowing features:\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the option \n 'Verify Checksum in Transport Global' and verify that all routines\n\n have the correct checksums.\n 5. On the KIDS menu, under the 'Installation' menu, use the option \n 'Backup a Transport Global' to make a backup copy of the old\n routines being brought in by this patch.\n 6. On the KIDS menu, under the 'Installation' menu, use the option \n 'Install Package(s)'. Select the package 'XU*8.0*21' and proceed\n with install.\n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'.\n 8. MSM Sites - D ^%RCOPY to move the routine XPDIJ to your other\n-KIDS will disable Protocols during the install process. This\n CPUs.\n 9. AXP Sites, after patch has installed, rebuild your map set.\n ==================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Name Checksum Patch List\n -----------------------------------------------------------\n functionality was removed in patch XU*8.0*10.\n XPDCOM 2299089 21\n XPDDI 7062234 21\n XPDDP 12102989 21\n XPDE 13757383 2,15,21\n XPDI 16025869 10,21\n XPDIA 10483361 10,15,21\n XPDIJ 17914806 2,21\n XPDIP 8712983 15,21\n XPDIPM 1775672 21\n XPDIQ 6662686 21\n-KIDS will not disable Options or Protocols which have an Action of\n XPDMENU 1821149 21\n XPDTC 11632956 10,15,21\n XPDTP 2309897 21\n XPDUTL 2331761 21\n XQOO 20281727 10,21\n XQOO1 14241374 10,21\n ===========================================================================\n OPTIONS:\n\n'Toggle options/protocols on and off' Option name: XQOOTOG\n 'USE AS LINK FOR MENU ITEMS'.\n This option is used to write or remove Out-Of-Order messages from\n individual options or protocols.\n'Recover deleted option set' Option name: XQOOREDO\n This option will recover an option set that has been deleted from ^XTMP\n by looping through the Option and Protocol Files to find all that have\n a particular Out-of-order message. It rebuilds the option set in ^XTMP.\n\n ============================================================================\n DOCUMENTATION:\n\n-Two new functions, $$PRODE^XPDUTL and $$OPTDE^XPDUTL, can be called\nThese two functions can be called in a Pre-Init or Post-Init routine to\ndisable or enable an Option or Protocol.\n $$PRODE^XPDUTL(name,action) ;Disable/Enable a Protocol\n name=Protocol Name, action= 1-enable, 0-disable\n returns: 1-success, 0-failure\n\n $$OPTDE^XPDUTL(name,action) ;Disable/Enable an Option\n name=Option Name, action= 1-enable, 0-disable\n returns: 1-success, 0-failure\n\n\n
\nThis patch adds two new fields and removes several fields marked for\nXU*8*108 to send a local install message. \n>>You may want to add local MAIL GROUPS that should be notified when a \n package is installed.<<\n\nFIELD REMOVAL the following fields are removed.\n4 *ROUTINE\n5 *GLOBAL\n11.1 *MAINTENANCE ISC\n11.4 *VERIFICATION\n11.5 *ALPHA\nremoval.\n11.6 *BETA\n11.7 *DELTA\n12 *PRIMARY HELP FRAME\n200.1 *USER TERMINATE TAG\n200.2 *USER TERMINATE ROUTINE\n1920 *STATUS\n1933 *KEY VARIABLE\nAnd in the VERSION multipule\n51 *RELEASE NOTE\n61 *INSTALLATION NOTES\n\n62 *SYSTEM REQUIREMENTS\n63 *PROGRAMMER NOTES\n\nThe following fields marked with a * have been left at this time.\n 9.5 *MENU (multiple)\n 10.6 *LOWEST FILE NUMBER\n 11 *HIGHEST FILE NUMBER\n\n\nSeveral fields used by DIFROM and marked for removal have had the * removed \nNEW FIELDS\nfrom the name.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Apr 10, 1999\n\n Checksum\nRoutine Old New 2nd Line\nXUPCH117 6388451 **117**\nThis Patch adds a new field with data to the PACKAGE file: ADDITIONAL\n\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nInstallation:\n\n 1. Install is file data only. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\nPREFIXS. This was requested by the DBA so that packages could check patches\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nin KIDS when the patch was in alternate prefix namespace. \n \n 4. Users can remain on the system. \n This patch can be queued and installed at any time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*117'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n =========================================================================\nThis patch adds a new field: MAIL GROUP, that KIDS will use with patch\n\n
\nThis patch fixes several problems associated with alerts and provides\nrequested the ability to view and/or process an alert and then be able to\npackage identifier indicated by XQAPKG.\n \n \nSETSURO^XQALSURO(XQAUSER,XQALSURO,XQALSTRT,XQALEND) - Establishes for the\nuser with internal entry number XQAUSER a surrogate with the internal\nentry number XQALSURO. XQALSTRT is an optional start date/time in\ninternal VA Filemanager format, and XQALEND is an optional end date/time\nin internal VA Filemanager format.\n \n \nforward (as reflected in the above NOIS entries) or set the alert as new\nREMVSURO^XQALSURO(XQAUSER) - Removes the current surrogate (if any) for\nthe user with the internal entry number XQAUSER.\n \n \n$$CURRSURO^XQALSURO(XQAUSER) - For the user with internal entry number\nXQAUSER returns the internal entry number of the current surrogate or -1\nif there is no surrogate specified.\n \n \nALERTDAT^XQALBUTL(XQAID,ROOT) - Returns information from ALERT TRACKING\nagain for subsequent processing. The current patch adds the ability to\nfile for alert with XQAID. The data is returned descendent from the\nclosed root passed in ROOT. If ROOT is not specified, the data is\nreturned in the array XQALERTD. The array is subscripted by the field\nnumber, the value is returned as the internal value (including NULL\nvalues) and, if the internal and external values differ, followed by the\nexternal value separated by '^'. If the field names are desired, they\nare also included as a second subscript to the array (with a null value).\nIf the alert is not present, the array root is returned with a NULL\nvalue.\n \nforward or re-new the alert at the point where previously the user was\n \nUSERLIST^XQALBUTL(XQAID,ROOT) - Returns recipients of alert with ID of\nXQAID from ALERT TRACKING file in an array descendent from the closed\narray specified in ROOT. If ROOT is not specified, then the data is\nreturned in XQALUSRS. The data is returned subscripted by an integer,\nand the value contains the internal entry number for the user in File 200\nand the external value for the user's name (the .01 field in file 200)\nseparated by '^'. If the specified alert is not present, the array root\nis returned with a NULL value.\n \nasked about continuing alert processing.\n \nUSERDATA^XQALBUTL(XQAID,XQAUSER,ROOT) - returns information from the\nALERT TRACKING file related to the alert with an ID of XQAID for the user\nspecified by the internal entry number in XQAUSER. The data is returned\ndescendent from the closed root passed in ROOT. If ROOT is not\nspecified, the data is returned in the array XQALUSER. The array is\nsubscripted by the field number, the value is returned as the internal\nvalue (including NULL values) and, if the internal and external values\ndiffer, followed by the external value separated by '^'. If the field\nnames are desired they are also included as a second subscript to the\nRoutines affected: XQALERT1, XQALFWD\narray (with a NULL value). If the alert is not present, the array root\nis returned with a NULL value.\n \n \nChanges to Data Dictionaries:\n \nALERT File (8992)\n \nAdded field .02 (SURROGATE FOR ALERTS) Added field .03 (SURROGATE START\nDATE/TIME) Added field .04 (SURROGATE END DATE/TIME)\n \n \nALERT DATE/TIME subfile (8992.01)\n \nAdded field .1 (CAN DELETE WITHOUT PROCESSING)\n \n \nALERT TRACKING file (8992.1)\n \nRECIPIENT subfile (8992.11)\n \n \nAdded field .09 (DELETED BY USER)\n \n \n \nChanges to Options:\n \nAdded 'XQALERT SURROGATE SET/REMOVE' as a new option. Added 'XQALERT\nSURROGATE SET/REMOVE' as an item under the 'XQALERT MGR' option.\n \n \nWBP-0198-22413\nRoutine Summary:\n================\n \nThe following routines are included in this patch. The second\nline of each of these routines now looks like:\n \n<tab>;;8.0;KERNEL;[Patch List];Jul 10, 1995\n \n \nChecksums:\n \n==========\n \nChecksums obtained using CHECK^XTSUMBLD\n \nRtn Nm Chksum Before Chksum After Patch List\n------ ------------- ------------ ----------\nXQALBUTL 2035856 4732286 **114**\nXQALDEL 12561210 14175555 **6,24,65,114**\nXQALDOIT 9852030 10091815 **1,6,65,114**\nXQALERT1 18178207 31077482 **20,65,114**\nnumerous requested enhancements.\nWhile CPRS has supported a capability to send alerts directly to a\nXQALFWD 10594990 10666938 **6,65,91,111,114**\nXQALSET 12975662 14779633 **6,65,75,114**\nXQALSURO New 5607165 **114**\n \n \nInstallation:\n \n1. DSM sites - Some of these routines may be mapped,\nso you will need to disable mapping for the affected routines.\n \ndesignated surrogate, this has left other packages without such an\n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n3. The patch has now been loaded into a Transport global on your\nsystem. You now need to use KIDS to install the Transport global.\nOn the KIDS menu, under the 'Installation' menu, use the following\noptions:\n \nVerify Checksums in Transport Global\nPrint Transport Global\nability. This NOIS and CPRS developers have requested a more generic\nCompare Transport Global to Current System\nBackup a Transport Global\n \n4. Users can remain on the system. This patch can be loaded any\nnon-peak time.\n \nThis patch can be queued for install at non-peak hours.\n \n5. On the KIDS menu, under the 'Installation' menu, use the following\noption:\nsurrogate capability supported directly by the alerts within Kernel. The\nSelect KIDS OPTION: Install\n=======\nInstall Package(s)\nSelect INSTALL NAME: XU*8.0*114\n==========\n \nNo Options or Protocols need to be placed out-of-order.\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n==\n \ncurrent patch adds the ability for an individual using a new 'S' option\n6. MSM-DOS Sites - Answer YES to the question 'Want to MOVE\nroutines to other CPUs?'. Enter the names of your Compute and\nPrint server(s).\nAXP Sites - Answer NO to this question.\n \n7. If the routines were unmapped as part of step 1, they should be\nreturned to the Mapped set once the installation has run to\ncompletion.\nwithin the alerts to designate and/or remove a surrogate for their\nalerts. The user may, if desired, specify a start date/time and/or an\nend date/time for the surrogate to be effective. If an end date/time is\nspecified, the surrogate will be removed automatically effective with the\nfirst alert sent to the user after the end date/time has passed. If a\n \nstart date/time is not specified, the surrogate becomes active\nimmediately. If an end date/time is not specified, the surrogate is\nactive until the user removes the surrogate. A message is sent to the\nsurrogate to indicate that he has been designated as a surrogate, and a\nmessage is sent when the surrogate is removed. If the user has no alerts\nand selects the alert option, he will be asked if he wants to add or\nremove a surrogate. A new option (XQALERT SURROGATE SET/REMOVE) is also\nprovided which may be used by IRM or ADPAC staff to add or remove a\nsurrogate for a selected user. This option has been added to the Alert\nManager option.\nNOIS\nRoutines affected: XQALERT1, XQALSET, XQALSURO (a new routine)\n \n \nISL-0299-50356\n \nA problem was identified such that if an alert was deleted for a given\nuser, and then the same alert was specified to be deleted for the same\nuser, it resulted in the alert being deleted for the next user with a\nhigher internal entry number and the alert was still active. This patch\ncorrects this problem.\n \nRoutines affected: XQALDEL\n \n \nFunctionality requested by CPRS developers\n \nThe ability for a user to delete specific alerts without viewing and/or\nprocessing them has been requested many times. In this patch, this\nfunctionality is included by providing the new 'D' option within the\nalerts. This option provides the ability to delete "information only"\nalerts. Alerts which require processing can not currently be deleted. In\nHUN-0997-20420 MAC-1198-60864\nthe future, however, if alerts requiring processing are created with the\nnew variable XQACNDEL set to 1 they too would be able to be deleted\n(i.e., the developer of the code which creates the alert can specify if\nit must be processed or can be deleted). Any alerts which were selected\nfor deletion, but could not be deleted will be noted for the user. The\nability for the user to delete alerts other than information only will\nrequire that the developers within a package decide that specific alerts,\nwhich would normally invoke processing via an option or routine, may be\ndeleted specifically by the user without processing. They would then set\nthe variable XQACNDEL to a value of 1 (one) prior to calling SET^XQALERT\n \nto set up the alert. Deletion of an alert by the user (or by IRM or\nADPAC staff using the existing option) is noted within the ALERT TRACKING\nfile as deletion by a user (with the user ID) without processing of the\nalert.\nRoutines affected: XQALERT1, XQALDEL\n \n \nThere have been several requests for the display of pending alerts to\nreturn to the current screen after an alert has been processed. This\ncapability is included within the current patch.\nThe ability to forward an alert has been limited to the point of\nRoutines affected: XQALERT1\n \n \nThe following entry points are added within this patch and are entered as\nsupported references.\n \nAHISTORY^XQALBUTL(XQAID,ROOT) - Provides information from the ALERT\nTRACKING file for the alert indicated by the alert ID (XQAID). The\ninformation is returned descendent from the closed root specified by ROOT\nin the form that it is present in the ALERT TRACKING file.\nselection and prior to processing an alert. A number of users have\n \n \n$$PENDING^XQALBUTL(XQAUSER,XQAID) - Returns 1 (one) if the alert\nindicated by the alert ID (XQAID) is currently pending for the user with\ninternal entry number specified by XQAUSER. Otherwise a value of 0\n(zero) is returned.\n \n \n$$PKGPEND(XQAUSER,XQAPKG) - Returns 1 if the user indicated by XQAUSER\nhas any pending alerts with the first ';'-piece of XQAID equal to the\n\n
\n \n **PLEASE NOTE** THE SOFTWARE NOW DISPLAYS THE TEXT OF EACH OPTION IT\nPROCESSES AS IT DOES SO. YOUR USERS WILL, THEREFORE, NOTICE A CHANGE IN\nBEHAVIOR AS MENU TEMPLATES RUN.\n \n \n This patch contains 4 routines and 1 help frame.\n \n Checksums were calculated by CHECK^XTSUMBLD\n \nRoutine Before After Patch List\n This patch fixes a couple of problems with menu templates: 1. The\n \nXQT 14403654 14503760 **20,47,46,37**\nXQT1 10829937 10816354 **59,37**\nXQT2 12277933 14513265 **37**\nXQT3 12864808 13422394 **46,37**\n \n \n \n============================================================\nInstallation Instructions:\nselection of a numbered choice outside of the range of the actual list\n \n1. Users are allowed on the system, and this patch may be queued.\n A "clobber" error may result if users are in these routines.\n \n2. These routines is not usually mapped, so you shouldn't have to\n disable mapping.\n \n3. Use the "Install/Check Message" option on the PackMan menu to \n load the package.\n \ncould cause an <UNDEF> (DAY-0497-42420 and BYN-0297-10733); 2. Failure to\n4. On the KIDS menu use the following options:\n \n Veryify Checksums in Transport Global\n Print Transport Global (Optional)\n Compare Trasport Global to Current System\n Backup transport Globa\n Install XU*8.0*37\n \n \n5. MSM sites answer 'YES' to the question: "Want to MOVE routines \nreenter the primary tree when backing up from a secondary tree\n to other CPUs?" AXP sites answer 'NO'.\n \n6. Rebuild mapped set if necessary.\n(DAY-1295-41818); and, the inability to skip an option in a template by\nhitting a RETURN (FNC-1297-30868); and 3.Prevents the selection of a\nbroker-type option when creating a menu template.\n \n\n
\nThis patch fixes one NOIS, one E3R, and several requested fixes for CPRS.\n in a master build.\n - Allow run routines for master builds. \n - Allow install to "inhibit login" for the install\n duration.\n - Fix an erroneous message when exporting data without \n the DD.\n - Delete one-time run routines after install.\n Development sites can override this by setting\n the KERNEL PARAMETERS file with "XPD NO_EPP_DELETE"\n with a value of 1.\n\n - Update the "Date Distributed" field in the build\n and transport to the install and include in tracking\n message. This will help track test versions installed.\n \n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\nISL-0299-51863 Increase the size of the "load file" string.\n Checksum\nRoutine Old New 2nd Line\nXPDB1 734412 **108**\nXPDCOM 5277873 5533101 **21,58,108**\nXPDDCS 4096637 4207018 **2,44,108**\nXPDDP 12306591 12220575 **21,28,44,68,100,108**\nXPDH 4137606 4932993 **58,95,108**\nXPDI 13691537 14086873 **10,21,39,41,44,58,68,108**\nXPDI1 6953243 7291162 **58,61,95,108**\nXPDIB 2753452 3407499 **10,58,108**\n\nXPDIJ 10800990 6991648 **2,21,28,41,44,68,81,95,108**\nXPDIJ1 9316977 10020629 **41,68,108**\nXPDIK 14344733 13945620 **15,58,108**\nXPDIL 11193690 11501302 **15,44,58,68,108**\nXPDIL1 10189777 11093962 **15,17,39,41,44,66,68,76,85,100,108**\nXPDIP 9539699 9539699 **15,21,28,30,41,44,51,58,83,92,100,108**\nXPDIPM 1853833 1828492 **21,28,68,108**\nXPDIQ 7824317 7324723 **21,28,58,61,95,108**\nXPDIST 2400065 4011005 **66,108**\nXPDIU 8180046 8188323 **15,41,44,51,58,101,108**\nE3R # 12059 Send Mail Message to local group.\nXPDT 19282131 19317490 **2,10,28,41,44,51,58,66,68,85,100,108**\nXPDTC 13394346 13712257 **10,15,21,39,41,44,58,83,92,95,100,108**\nXPDUTL 2708596 2995571 **21,28,39,81,100,108**\nXPDV 11643577 11647335 **30,44,58,108**\n\nList of preceding patches: 58, 100, 101\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n The mail group is defined in the Package file and is\n\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n new with patch XU*8*117.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. \n This patch can be queued and installed at any time.\n\n \n 5. Use "D ^XPDKRN" then \n Install Package(s) 'XU*8.0*108'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\nCPRS - Allow utilities to work on all components included\n\n\n
\nThis patch is in support of changes coming to the RPC Broker.\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXQCS 12250092 12133342 **15,28,82,116,115**\nXUINPCH3 555958 **115**\nXUPARAM 1006391 1340230 **65,115**\nAdded a "B" cross-reference to the Division multiple in the New Person \nXUSRA 1890066 1579938 **70,115**\nXUSRB 5738122 5880708 **11,16,28,32,59,70,82,109,115**\nXUSRB2 783689 **115**\n\nList of preceding patches: 65, 109, 116\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\nfile. Created/Added new RPC to set the division during logon.\n 1. DSM sites - Some of these routines may be mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\nA new field in the Kernel System parameters file to hold a broker parameter,\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can also be queued for install at non-peak hours.\n\nthe Broker Activity Timeout field. Updated forms and templates for the new\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*115'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\nfield.\n=========================================================================\n\nRIC-0799-20190 Reported an error that is fixed with this patch.\n\n\n
\nHOU-0399-73122 \nMOM-0799-52593\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. \n Stop TASKMAN, and have submanagers stop.\n \n \nAMA-0799-72651\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*118'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\nSPO-0799-52388\n OpenM Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n \nZIS2\nZIS6\nZISTCP\nZISTCPS\nZISUTL\nZOSVMSM\n This patch has updates to allow Cache sites to run taskman on two or more\nZOSVONT\nZOSVVXD\nZTLOAD\nZTLOAD1\nZTLOAD2\nZTER\nZTM\nZTM0\nZTM1\nZTM2\n nodes at the same time. How locking was being used with the IO queue was\nZTM4\nZTM5\nZTM6\nZTMKU\nZTMON\nZTMON1\nZTMS\nZTMS0\nZTMS1\nZTMS2\n changed to use ^%ZTSCH("DEV",io) in its place. This should allow more than\nZTMS3\nZTMS7\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 118\n ===\n \n one sub-manager to look at the "IO" list at the same time. If there is a\n 10. DSM Sites, after patch has installed, rebuild your map set.\n \n 11. In the production account, You will need to edit file 14.7\n first DO ^ZTMCHK and from the second screen look for\n "Cpu-volume Pair: ROU:APP1".\n Edit file 14.7 and change the name from ROU to ROU:APP1\n then add a new entry ROU:APP3. The ROU is the volume set name you\n gave the system and the APP1 should be your Cache configuration \n name. The Avanti team will provide more info on setting up for\n running dual taskman nodes.\n delay in one device it will not delay other devices. The submanagers now\n \n 12. Restart TASKMAN with D RESTART^ZTMB. DSM sites this may require\n a privileged user.\n\n\n==========================================================================\n keep a list of available submanagers as well as there count. The option\n "XUTM QCLEAN" will reset the count as part of its work. Each lock timeout\n As part of the overall work the error that this site was getting has been\n was checked for constancy. Changes to make the STARTUP flag in the\n OPTION SCHEDULE file work better.\n ZTM*, XUTMK, XUTMG19\n \n The code to share licenses when GUI and Telnet users from the same work\n station are connected is in place and ZU now calls it. There will be a \n broker patch to follow that will complete the work. \n ZOSVONT, ZOSVVXD, ZOSVMSM, ZUONT, ZUVXD\n \nSAG-0599-42045 ZISTCPS There wasn't any way to stop the listener other than\n fixed. \nHL7 Team ZTLOAD the use of JOBEXAM/FORCEX. Changed to have listener\n ZTLOAD2 check for LOGON INHIBIT and call $$S^%ZTLOAD to see if\n the task has been asked to stop.\n ZTER The entry point UNWIND^%ZTER would return 0 to a\n calling function. This has been changed to -9 to\n make it easier to tell if return is from the \n error trap. \n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\n ZTLOAD will reject requests to queue to a device the has QUEUING field \nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXUTMG14P 883159 1096983 **118**\nXUTMG19 3890099 4412102 **20,67,118**\nXUTMK 6655042 7364498 **49,67,118**\nXUTMOPT 3807330 3961784 **2,111,112,118**\nZIS2 10140057 10170284 **69,104,112,118**\n set to NOT ALLOWED.\nZIS6 9295013 9023565 **24,49,69,118**\nZISTCP 2862626 2703750 **36,34,59,69,118**\nZISTCPS 1057561 1103406 **78,118**\nZISUTL 2112295 2273417 **18,24,34,69,118**\nZOSVMSM 10431698 10122636 **13,25,49,94,107,118**\nZOSVONT 5510564 6757287 **34,94,107,118**\nZOSVVXD 6011813 6204470 **13,65,71,94,107,118**\nZTER 18976906 18980475 **8,18,32,24,36,63,73,79,86,112,118**\nZTLOAD 1753065 1773483 **67,118**\nZTLOAD1 6628172 6704108 **112,118**\n ZTLOAD1, ZTLOAD2, ZISUTL\nZTLOAD2 3185920 4207916 **1,67,118**\nZTM 8229940 7928004 **24,36,64,67,118**\nZTM0 5937824 6113151 **42,36,67,88,118**\nZTM1 5569955 5627291 **118**\nZTM2 3666292 3672059 **23,118**\nZTM4 2450447 2321835 **1,118**\nZTM5 3748675 3223273 **24,36,118**\nZTM6 1889159 1943469 **23,118**\nZTMKU 8211227 8280155 **118**\nZTMON 3969317 4340327 **118**\n \nZTMON1 7519989 7653545 **36,118**\nZTMS 5281307 5545783 **2,18,24,36,67,94,118**\nZTMS0 3205484 3316930 **24,118**\nZTMS1 6242844 8217798 **36,49,104,118**\nZTMS2 5301865 5746563 **2,18,23,36,67,118**\nZTMS3 10008753 9711469 **1,18,36,49,64,67,94,118**\nZTMS7 1498041 1489086 **1,118**\nZUONT 1969174 1992793 **34,94,118**\nZUVXD 4462372 4517687 **13,24,84,94,118**\n\nSAG-0699-40716\nList of preceding patches: 1, 69, 78, 88, 94, 104, 107, 112\nSites should use CHECK^XTSUMBLD to verify checksums.\n\nBe sure to follow step 11 below.\n\n========================================================================= \nInstallation:\n\nUsers can remain on the system\n\nLIT-0199-70997\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n\nISF-0699-00000 XTER1A The fix to XTER1A for working with Mailman patch\n If the 5th parameter is missing or 0 then it will\n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO ^ZTEDIT\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\n work as before, a 1 will prevent ZTSK from being newed.\n \n \nFAV-0499-70417 ZTEDIT* If the user has the screenman editor as default then\n they get a UNDEF error. Fixed.\n \nWPB-0599-32576 The New Person file doesn't have a New User Bulletin.\nSTX-0599-72647 Added it back in.\n\nTAM-0899-30289 XM*7.1*50 broke printing. Fixed.\n XLFSTR Updated function call \n $$TRIM^XLFSTR(x[,"[L][R]"][,char]).\n This call will trim spaces or other char from the left,\n right or both sides of a input string.\n W "["_$$TRIM^XLFSTR(" A B C ")_"]" => [A B C]\n W "["_$$TRIM^XLFSTR("//A B C//",,"/")_"]" => [A B C]\n \nISL-0699-51707 XLFDT The FMADD call would return 141301 if passed (0,0)\n This has been fixed.\n \n\nY2K testing XLFDT3 The SCH^XLFDT didn't handle Feb 29, 2000.\n This has been fixed.\n \nMCM-1195-51777 Option XUERTRP CLEAN was not on the XUERRS menu.\n Linked up.\n \n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\nMON-0599-52241 XUTMRP Under some conditions the Taskman Repoint Waiting\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXLFDT 4068329 4050775 **71,120**\nXLFDT3 6320544 6415507 **71,120**\nXLFSTR 2042372 1941897 **112,120**\nXTER1A 13449705 13096442 **63,112,120**\nXUTMDEVQ 268897 294750 **20,120**\nXUTMRP 15705216 15577050 **2,20,86,120**\nTAM-0499-30489 XUTMRP1 Task would error out. Also some of the prompts were\nXUTMRP1 7012212 7184681 **2,86,120**\nZTEDIT 11385452 11385452 **16,120**\nZTEDIT1 9783719 9783719 **16,120**\nZTEDIT2 12431351 12255678 **9,16,120**\nZTEDIT3 9890321 9327277 **16,120**\nZTEDIT4 4936626 4936626 **16,120**\n\nList of preceding patches: 16, 71, 86, 112\nSites should use CHECK^XTSUMBLD to verify checksums.\n\nMON-0599-52241 not meaningful, Fixed.\n==============================================================================\nInstallation:\n\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nHARDHATS XUTMDEVQ A request to be able to return ZTSK. Added a 5th\n 4. This patch can be loaded any non-peak time.\n Users can remain on the system. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*120'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n parameter to stop the newing of ZTSK.\n ==\n \n 8. After installing this patch,\n OpenM Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n \nZTEDIT*\n\n \n\n\nY2K Waiver Exemption ID# Y2KWE0025\n\nZTLOAD1\nZTLOAD3\nZTM\nZTM0\nZTM1\nZTM4\nZTM5\nZTM6\nZTMGRSET\nZTMKU\nHIN-1099-41741 ZTMGRSET Updated the list of OS types to show\nZTMON\nZTMON1\nZTMS\nZTMS1\nZTMS2\nZTMS3\nZTMS7\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n VAX DSV(V7) and Cache.\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 127\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n \n \n 11. Restart TASKMAN with D RESTART^ZTMB. DSM sites this may require\n a privileged user.\n \n \n 12. Add a MAIL GROUP to the bulletin "XUTM PROBLEM DEVICE".\n Schedule the option "XUTM QPROBLEM DEVICE" once a day.\nZIS6 Add the task time and $H to the slot data\nZISTCPS Has a fix for a change in Cache between 2.1.6 and 3.1\nXUTMKA New, To look for devices that are having problems.\n\n\nRoutine Summary\n\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;\n\n Checksum\nRoutine Old New 2nd Line\nXUTMKA 1312470 **127**\nXUTMOPT 3961784 4026913 **2,111,112,118,127**\nZIS6 9023565 9115588 **24,49,69,118,127**\nZISTCPS 1103406 1115181 **78,118,127**\nMAR-1099-21847 This patch should address the performance problems in Taskman \nZISUTL 2273417 2307058 **18,24,34,69,118,127**\nZTLOAD 1773483 1559971 **67,118,127**\nZTLOAD1 6704108 6808427 **112,118,127**\nZTLOAD3 3918318 3910561 **67,127**\nZTM 7928004 8571416 **24,36,64,67,118,127**\nZTM0 6113151 6026624 **42,36,67,88,118,127**\nZTM1 5627291 5465675 **118,127**\nZTM4 2321835 2164226 **1,118,127**\nZTM5 3223273 4063072 **24,36,118,127**\nZTM6 1943469 2656166 **23,118,127**\nTAM-1099-31772 caused by patch XU*8*118.\nZTMCHK1 6522196 6595933 **127**\nZTMGRSET 14310699 14239565 **34,36,69,94,121,127**\nZTMKU 8280155 8841182 **118,127**\nZTMON 4340327 4458377 **118,127**\nZTMON1 7653545 9616420 **36,118,127**\nZTMS 5545783 5576536 **2,18,24,36,67,94,118,127**\nZTMS1 8217798 8021013 **36,49,104,118,127**\nZTMS2 5746563 5847661 **2,18,23,36,67,118,127**\nZTMS3 9711469 9841850 **1,18,36,49,64,67,94,118,127**\nZTMS7 1489086 1828513 **1,118,127**\nNTH-0999-72794 STL-1099-40458 MAR-1099-23207 SDC-1099-60815 WRJ-0899-13025\n\nList of preceding patches: 118, 121\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n\n========================================================================= \nInstallation:\n\nUsers can remain on the system, STOP TASKMAN.\n\nSTX-1099-72163\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. \n STOP TASKMAN, and have submanagers stop, STOP other background filers.\n "DO STOP^ZTMKU"\n \nSHR-1099-71855 ZISUTL The UNDEF in %ZIS5 has been fixed.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*127'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\nCON-0999-12912 WRJ-0999-12571 BED-0999-12380\n OpenM Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n \n\n\nZIS6\nZISTCPS\nZISUTL\nZTLOAD\n\n
\n1. CTX-1099-72732, DAN-1099-40868. Waiver Exemption ID#: Y2KWE0019.\n \nTest Sites:\n===========\nCentral Texas HCS- 674\nDanville, IL - 550\n \n \nInstallation Instruction:\n========================\n \n Renewed Alerts Not Reappearing. When sites renew alerts they are\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n disappearing. The following Data Dictionary has been revised to\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 3. Users can remain on the system. This patch can be loaded any\n non-peakpeak time.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*133'\n ==========\n correct this problem:\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 1. ^DD(8992.1,.01\n 2. ^DD(8992.1,.03 \n 3. ^DD(8992.01,.02\n \n\n
\n\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Before After Patch\n Routine Checksum Checksum List\n ----------------------------------------------------------------------\n XPDE 15253053 15204188 **2,15,21,44,51,68,131**\n XPDIA 13691537 14296891 **10,15,21,28,44,58,68,131**\n XPDIA0 NEW 2357876 **131**\n XPDIA1 9001554 10621758 **2,44,51,58,68,85,131**\n KIDS routines have been modified to support patch HL*1.6*57. Patch 57\n XPDIA2 6372331 6756887 **68,131**\n XPDTA 7580607 8868649 **15,44,58,131**\n XPDTA1 5005398 4715012 **44,68,85,131**\n XPDTC 13724075 13813303 **10,15,21,39,41,44,58,83,92,95,\n 100,108,124,131**\n=============================================================================\n This patch can be installed with users on the system, but no other users\n should be using KIDS while you install this patch.\n===========================================================================\n INSTALLATION:\n added a new field multiple, 'SUBSCRIBER', to the Protocol file, #101. Also,\n \n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n \n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the patch in the \n Transport global.\n the HL LOWER LEVEL PROTOCOL PARAMETER file, #869.2, was merged into the\n \n 4. Users can remain on the system. This patch can be queued and \n installed at any time. TaskMan can remain running.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n HL LOGICAL LINK file, #870.\n \n 6. As with the installation of all Kernel patches, it is recommended\n that you return to programmers prompt and use D ^XPDKRN:\n Install Package(s)\n INSTALL NAME: XU*8.0*131\n =========\n \n 7. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n\n=============================================================================\n ROUTINES:\n Checksums obtained using CHECK^XTSUMBLD\n\n
\n\n \n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*135'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n == \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n2. Whenever a name is changed or added in the NEW PERSON file, it is\n\n \nNOTE: When patch has completed loading proceed with the following steps:\n \n \n 1. From Programmers Mode, execute the following routine:\n \n >D ^XUYDEV \n \n \n necessary to transmit the new name to the Accu-Max system via HL7\n 2. Next the routine will display:\n \n The Following Data Has Been Added To File #8989.518\n ====================================================\n DEVICE\n DEV\n Device\n \n \n Press the return key to continue or '^' to exit:\n Messaging. Routines will routinely check for the existence of\n\n ^DGRU(46.11,"AC") node. For those entries which exist, a Master\n File Update("MFU") HL7 Message will be created and sent to the\n Accu-Max system if they have a "Physician" class. Several new\n cross-references are being added to the Name and Provider Class\n fields of file #200. These new cross-references will trigger the\n data into the RAI/MDS Monitor file(#46.11).\nY2K Waiver Request ID#:Y2KW0001 Y2K Waiver Status: Approved\n \n3. MON-0899-52735.\n When using the Deactivate a User option [XUSERDEACT], a prompt\n will display to "Delete All Mail Access:". When cursor is set\n to the field to respond the system shows that the user has 0\n messages in their mail box or group though their are messages.\n Routine XUSTERM and XUSRB1 has been revised to correct this\n problem.\n \n4. ISL-1199-51331.\nthis patch may be installed during the Y2K Moratorium, AFTER \n To allow CPRS Notification users the ability to identify users\n and/or OE/RR teams, the DEVICE file #3.5, will be added to the\n PARAMETER ENTITY file #8989.518. A new routine(^XUYDEV) has\n been created to allow entry of the DEVICE into file #8989.518.\n When patch has completed loading, proceed with the following\n steps:\n \n 1. From Programmer Mode, execute the following routine:\n \n >D ^XUYDEV \n1/15/2000. \n \n \n 2. Next the routine will display:\n \n The Following Data Has Been Added To File #8989.518\n ====================================================\n DEVICE\n DEV\n Device\n \n \n \n Press the return key to continue or '^' to exit:\n \n \nTest Sites:\n===========\nWashington D.C. - 688\nBronx, NY - 526\nMadison, WI - 607\nAlbany, NY - 500\n1. E3R - 12385.\nBiloxi, MS - 520\nTampa, FL - 673\n \nRoutine Summary:\n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;11/26/99\n \n In support of MailMan patch XM*7.1*107, this patch adds a new whole\nChecksums: CHECK^XTSUMBLD\n==========\n \nRtn Nm Chksum Before Chksum Patch List\n===================================================================\nXU8P135 NEW 380717 **135**\nXUYDEV NEW 903293 **135**\nXUSTERM 14376497 13878375 **36,73,135**\nXUSRB1 10103967 10106207 **28,82,135**\n \n file cross reference ("AH", on the DIVISION field) to the NEW PERSON\n \n \nInstallation Instruction:\n========================\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n file, to enable limited broadcast messager by division.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 3. Users can remain on the system. This patch can be loaded any\n non-peak time.\n\n\n Y2K Waiver Request ID#:Y2KW0001 Y2K Waiver Status: Approved\n and time.\n \n \nTest Sites:\n===========\nMartinsburg, WV - 613\nBronx, NY - 526\n \n \nRoutine Summary:\n this patch may be installed during the Y2K Moratorium, AFTER \n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;09/20/96\n \nChecksums: CHECK^XTSUMBLD\n==========\n \nRtn Nm Chksum Before Chksum After Patch List\n 1/15/2000.\n=====================================================================\nXQ55 10774418 10830712 140\n \n \nInstallation Instruction:\n========================\n1. Users are allowed to be on the system during the Installation.\n \n2. Routine mapping is NOT recommended for these routines.\n \n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n4. You Do Not need to stop TaskMan or the background filers.\n (AXP Sites - Place TaskMan in a WAIT state.\n OpenM/Cache Sites - STOP TaskMan.)\n \n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n1. BRX-1197-11294.\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s)\n INSTALL NAME: XU*8.0*140\n ==========\n \n When using the 'Option Access By User' option and a user has not\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n \n6. AXP Sites - Answer NO to the question "Want to MOVE routines\n to other CPUs?"\n \n7. If the routines were unmapped, the mapped set should be rebuilt\n previously logged on to the system, the Last on date is displayed\n once the installation has run to completion.\n \n8. AXP and OpenM/Cache Sites Only - Remove TaskMan from a WAIT/STOP state.\n errouneously. Routine XQ55 have been revised to display a null\n last on date, should last on date for a user contain a blank date\n\n
\nWhile investigating NOIS DAY-0200-40034 a leap year problem was found in\n\nSites should use the following to see if any tasks are affected by evaluating\nthe QUEUED TO RUN AT WHAT TIME field to see if it appropriate for the task.\nLook for task that should have been scheduled for Feb 29,2000.\n\nSelect OPTION: PRINT FILE ENTRIES \n\nOUTPUT FROM WHAT FILE: // 19.2 OPTION SCHEDULING\n (13 entries)\nSORT BY: NUMBER// 2 QUEUED TO RUN AT WHAT TIME\nSCH^XLFDT. This would affect tasks scheduled for the last day of the month.\nSTART WITH QUEUED TO RUN AT WHAT TIME: FIRST// FEB 15,2000 (FEB 15, 2000)\nGO TO QUEUED TO RUN AT WHAT TIME: LAST// MAR 1,2000 (MAR 01, 2000@24:00)\n WITHIN QUEUED TO RUN AT WHAT TIME, SORT BY: \nFIRST PRINT FIELD: .01 NAME\nTHEN PRINT FIELD: 2;L19 QUEUED TO RUN AT WHAT TIME\nTHEN PRINT FIELD: 6;L20 RESCHEDULING FREQUENCY\nTHEN PRINT FIELD: \n\n *************************\nHeading (S/C): OPTION SCHEDULING LIST Replace \nTaskman uses this routine to evaluate the RESCHEDULING FREQUENCY field in \nSTORE PRINT LOGIC IN TEMPLATE: \nSTART AT PAGE: 1// \nDEVICE: SYSTEM\n\n...SORRY, HOLD ON...\n\nOPTION SCHEDULING LIST FEB 9,2000 12:44 PAGE 1\n QUEUED TO RUN AT RESCHEDULING\nNAME WHAT TIME FREQUENCY\n----------------------------------------------------------------------------\nthe Option Scheduling file.\nJOES SPECIAL FEB 28,2000 22:00 1M(L@2200)\nXUTM PROBLEM DEVICES FEB 28,2000 21:00 1M(15@2100,L@2100)\n----------------------------------------------------------------------------\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\n\nRoutine Old New 2nd Line\nXLFDT2 3530137 3576737 **71,86,141**\nXLFDT3 6415507 5174266 **71,120,141**\n\nList of preceding patches: 86, 120\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\nAlso fixed is a looping problem if the schedule requests a day beyond the\n>>>Users may remain on the system.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\nend of the month. Like 30th of each month for February or 31st for April.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peakpeak time.\nNow it will default to the LAST DAY of the month. This would make a schedule\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*141'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \nof "1M(30@2200)" for February be eveluated as "1M(L@2200)".\n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\n\n
\n This patch may not be installed during the Y2K Leap Year Lockdown\n \n Inaddition input template XUEDITOPT has been revised to allow Broker\n type options to prompt for RPCKEY and RULES fields.\n \n \n \nTest Sites:\n===========\nMartinsburg, WV - 613\nBronx, NY - 526\n period of 2/28/2000 to 3/3/2000.\n \n \nRoutine Summary:\n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;09/20/96\n \nChecksums: CHECK^XTSUMBLD\n \n==========\n \nRtn Nm Chksum Before Chksum After Patch List\n====================================================================\nXQ5 13875754 16374150 44,130\n \n \nInstallation Instruction:\n========================\n1. Users are allowed to be on the system during the Installation.\n \n \n2. Routine mapping is NOT recommended for these routines. If you\nare using routine mapping, review your mapped set and ensure that\nthese routines are NOT in your mapped routine set before proceeding\nand rebuild your map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n4. You Do Not need to stop TaskMan or the background filers.\n1. MWV-0997-20795.\n (AXP Sites - Place TaskMan in a WAIT state.\n OpenM/Cache Sites - STOP TaskMan.)\n \n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n When setting defaults to a print type option, then accessing the\n Backup a Transport Global\n \n Install Package(s)\n INSTALL NAME: XU*8.0*130\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n option thru Edit option, Edit option overwrites any defaults that\n == \n \n6. AXP Sites - Answer NO to the question "Want to MOVE routines\n to other CPUs?"\n \n7. If the routines were unmapped, the mapped set should be rebuilt\n once the installation has run to completion.\n \n8. AXP and OpenM/Cache Sites Only - Remove TaskMan from a WAIT/STOP state.\n were previously set, should a template be selected. The routine\n XQ5 has been revised to display to user a list of current defaults.\n\n
\nRUM updates.\n\n
\nGet discription from the web.\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 3. Users can remain on the system. This patch can be loaded any\n \n non-peakpeak time.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*106'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n========================================================================= \n \n 5. After the install there is a part of the conversion that must\n be done by a user.\n Now "D MANUAL^XUINPCH2" to convert the ones that need user input.\n \n=========================================================================\nInstallation:\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n\n
\nSee XU*8.0*134 of the National Patch Module for full documentation.\n\n
\nThis Patch installs a routine that can do a DNS lookup to convert a \nIF YOU ARE INSTALLING THIS PATCH IN A TEST ENVIRONMENT ALONG WITH HL7\nPATCH 63, DO NOT POINT TO A PRODUCTION DNS! THIS COULD RESULT IN\nTRANSMITTING TEST HL7 MESSAGES TO A SITE'S PRODUCTION SYSTEM.\nThe install will test for a HL7 test parameter and not install the\ndefault DNS address in this case. PLEASE CHECK.\n********************************************************************** \n\nSee DBIA# 3056 for documentation on the API's.\n\nThere is a entry point for testing: TEST^XLFNSLK\ndomain name to an IP address. This routine has two supported API's.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;June 25, 1999\n\n Checksum\nRoutine Old New 2nd Line\nXLFNSLK 7523173 **142**\n\nThe change by VISN's to the 10. private IP addressing pushed the need\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n\n 1. DSM sites - This is a new routine.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\nfor this patch. \n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n\n Backup a Transport Global\n \n 4. Users can remain on the system. \n This patch can be queued and installed at any time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*142'\n ==========\n \n***************IMPORTANT*********************************************\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n 6. The POST install has entered the address of one of the national \n DNS servers. PLEASE CHANGE TO THE CORRECT ONE FOR YOUR SITE.\n From the EVE menu > Operations Management > Kernel Management Menu\n > Enter/Edit Kernel Site Parameters. Go to the third screen and\n enter the correct DNS IP address for your site.\n Here are the national DNS IP address's\n\nThis patch is used by HL7 patch HL*1.6*63.\n 152.127.1.12 ns1\n 152.128.1.12 ns2\n 152.129.1.12 ns3\n 152.130.1.12 ns4\n 152.131.1.12 ns5\n 152.132.1.12 ns6\n =========================================================================\nThe POST install will enter the address of one of the national \nDNS servers. PLEASE CHANGE TO THE CORRECT ONE FOR YOUR SITE.\n\n
\nThis patch addresses some of the problems that taskman is having with\nCLE-0200-40051, BAY-0100-31168, TAM-0100-32225, JAC-0100-72572,\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\nJAC-0200-70074, CTX-0300-70786\n \nZIS2\nZIS6\nZOSVONT\nZOSVVXD\nZTLOAD3\nZTM\nZTM0\nZTM5\nZTM6\n\nZTMGRSET\nZTMON\nZTMS\nZTMS1\nZTMS3\nZTMS4\nZTMS7\n\n \n 9. And in the manager account, (OpenM sites remain in VAH)\nThree new fields were added to the TASKMAN SITE PARAMETERS file.\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 136\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n 11. Restart TASKMAN or remove TASKMAN from the wait state.\n\n\n"Balance Interval" to control how offen the manager does the Balance code.\n=========================================================================\n"Auto Delete Tasks" to control if the sub-manager will set ZTREQ to "@"\n before the task starts.\n"Manager Startup Delay" to control how long the manager waits when starting.\n This field isn't used for a RESTART.\n\nthe ORB NOTIFICATION RESOURCE and the ORW THREAD RESOURCE.\nTAM-0100-32225\nA problem in the use of ZTREQ to re-schedule a task was fixed with a\nchange to %ZTLOAD3. \n\nMAC-0300-61865\nIf there was an error in the loadbalance routine the variable ZTOVERLD would\nbe undefined, ZTM6.\n\nAlso fix is a incorrect label in the ShareLic code of ZOSVONT.\nLIT-0300-71933, FGH-0300-32520\nWorking with West LA and Seattle, a locking conflict was identified\n Routine %LICENSE not in DMS 7.2 as expected. ZOSVVXD.\n The need for %ZOSV1 eleminated, Routine ZOSV1VXD deleted by install.\n ZTMGRSET updated to reflect this change.\n\nCML-1299-4077 XUTMQ3 \nChanged to adapt to the new Taskman "IO" list.\n\nALB-1299-50759 %ZIS2 \nProblem with the HFS parameters in the device file not being used when\ncalled from Taskman and ZTIO was used to setup the device.\nwhen Taskman was trying to allocate resource devices.\n \nZIS6 was changed to consolidate the resource device checking.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nWith this change taskman skips the lock of ^%ZTSCH("DEV",IO) to prevent\nXUTMQ 8141476 8186969 **20,136**\nXUTMQ3 6060152 5747866 **136**\nZIS2 10170284 10178860 **69,104,112,118,136**\nZIS6 9115588 10232057 **24,49,69,118,127,136**\nZOSVONT 6645833 5179130 **34,94,107,118,136**\nZOSVVXD 6204470 7443216 **13,65,71,94,107,118,136**\nZTLOAD3 3910561 4046069 **67,127,136**\nZTM 8571416 9005201 **24,36,64,67,118,127,136**\nZTM0 6026624 6089712 **42,36,67,88,118,127,136**\nZTM5 4063072 4417939 **24,36,118,127,136**\ntwo tasks from trying to open the same device at the same time. The \nZTM6 2656166 2656180 **23,118,127,136**\nZTMGRSET 14239565 14179554 **34,36,69,94,121,127,136**\nZTMON 4458377 4675862 **118,127,136**\nZTMS 5576536 5488776 **2,18,24,36,67,94,118,127,136**\nZTMS1 8021013 8379658 **36,49,104,118,127,136**\nZTMS3 9841850 9642200 **1,18,36,49,64,67,94,118,127,136**\nZTMS4 4980927 5100103 **136**\nZTMS7 1828513 2052318 **1,118,127,136**\n\nList of preceding patches: 20, 127\nresource device has its own lock to control this.\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system. STOP TASKMAN. <<<\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \nThis should fix a number of NOIS reports.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\nNJH-0100-20258, NTH-0100-70436, CLE-0100-40398, CTX-0100-70947,\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n STOP TASKMAN. D STOP^ZTMKU\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*136'\n\n\nSee XU*8.0*152 in the National Patch Module on FORUM for details.\n\n
\nRUM for OpenM/Cache.\n\n
\n This patch contains the following features:\n\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no user should be using KIDS during the install of this patch.\n===========================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n-Fixes problem when installing new Protocols, they would remain disabled.\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n ===========================================================================\n \n ROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Name Checksum Patch List\n -----------------------------------------------------------\n Nois CLA-0696-20835.\n XPDET 4659158 15,39\n XPDI 16016321 10,21,39\n XPDIL1 6256689 15,17,39\n XPDTC 12678971 10,15,21,39\n XPDUTL 2641528 21,28,39\n XQOO1 14071629 10,21,39\n ============================================================================\n-The function $$PATCH^XPDUTL(patch) will handle patches with sequence\n numbers, which were added in patch 30.\n-Setting XPDABORT=2 wasn't aborting install.\n-Out of Order message on an option now contains the package name.\n===========================================================================\n\n
\nSee XU*8.0*158 in the National Patch Module on FORUM for details.\n\n
\n1. ISL-0797-50726.\n \n VERIFY CODE MUST be changed before continued use.\n \n ACCESS CODE:\n \n \nNEW - Good morning JOSHUA\n You last signed on today at 09:00\n Device:_TNT0001\n \n Site discovered that when a user attempts to logon and the PROHIBITED\n SMITH,JOSHUA M. you are NOT AUTHORIZED to access the system during\n the hours of 10:00 am thru 1:30 pm. Please try before 10:00 am or\n after 1:30 pm.\n \n ACCESS CODE:\n \n \n \nTest Sites:\n===========\n TIMES FOR SIGN-ON(file #200 and field #15) has been set with a time\nAnn Arbor, MI - 506\nBronx, NY - 526\n \nRoutine Summary:\n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;07/03/95\n \n range that the user may not sign-on, an invalid message is displayed\nChecksums: CHECK^XTSUMBLD\n==========\n \nRtn Nm Chksum Before Chksum After Patch List\n====================================================================\nXUS1A 5446713 7137988 153\n \n \nInstallation Instruction:\n========================\n to the user. Display has been revised as follows:\n1. Users ARE NOT allowed to be on the system during the Installation.\n \n2. Routine mapping is NOT recommended for these routines. If you\nare using routine mapping, review your mapped set and ensure that\nthese routines are NOT in your mapped routine set before proceeding\nand rebuild your map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n \n4. You Do Not need to stop TaskMan or the background filers.\n \n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nOLD - Good morning JOSHUA\n \n Install Package(s)\n INSTALL NAME: XU*8.0*153\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n You last signed on today at 09:00\n \n6. DSM/AXP Sites - Answer NO to the question "Want to MOVE routines\n to other CPUs?"\n \n7. DSM/AXP Sites: If the routines were unmapped per STEP #2, the\n mapped set should be rebuilt once the installation has run to\n completion.\n Device:_TNT0001\n\n
\n1. PUG-1299-50101.\nPuget Sound HCS - 663\n \n \nRoutine Summary:\n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;07/10/95\n \n When an alert is sent to a user the Forward and Renew prompts are\nChecksums: CHECK^XTSUMBLD\n==========\n \nRtn Nm Chksum Before Chksum After Patch List\n====================================================================\nXQALERT1 30892967 30893715 20,65,114,123,125\n \n \nInstallation Instruction:\n========================\n displayed as F(orward) or R(enew). Changing to display as (F)orward\n1. Users are allowed to be on the system during the Installation.\n \n2. Routine mapping is NOT recommended for these routines. If you\nare using routine mapping, review your mapped set and ensure that\nthese routines are NOT in your mapped routine set before proceeding\nand rebuild your map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n or (R)enew.\n4. You Do Not need to stop TaskMan or the background filers.\n \n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n Install Package(s)\n INSTALL NAME: XU*8.0*164\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n \n \n6. DSM/AXP Sites - Answer NO to the question "Want to MOVE routines\n to other CPUs?"\n \n7. DSM/AXP Sites: If the routines were unmapped per STEP #2, the\n mapped set should be rebuilt once the installation has run to\n completion.\n \nTest Sites:\n===========\n\n
\nThis is the replacement patch for XU*8*138. If patch XU*8*138 has been loaded\nNPF so that a trace to the original authentication can be made. No Access\nand Verify codes are, however, entered in the NPF so that the visitor may\nnot log in. He or she will only see that information provided by the CPRS\nforeign views software. A bulletin, XUVISIT, will be sent when an entry\nis made in the New person File if the site has assigned a valid mail group\nto the bulletin. The software defines a new multiple in the NPF called\n"VISITED FROM" which stores the information brought from the home system.\nThere is a new SORT and PRINT template to show NPF entries that have been\nVISITORS to a site. XUS VISIT USER.\n\nthis patch should fix the changes that XU*8*138 made to the cross references\nThe Sign-on log has new fields to record the remote site and remote ien of a\nvisitor. A new Print template XUSEC REMOTE ACCESS and sort template \nXUSEC REMOTE ACCESS to print just entries from remote users.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nof file 200.\nRoutine Old New 2nd Line\nXUESSO1 n/a 4118958 **165**\nXUS1 10153593 10540362 **9,59,111,165**\nXUSCLEAN 6583467 6966234 **13,59,165**\nXUSRB 5880708 6041270 **11,16,28,32,59,70,82,109,115,165**\n\nList of preceding patches: 111, 115\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \n\nInstallation:\n\n>>>Users may remain on the system.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \nThis Kernel patch allows users to be validated through the\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \ntraditional Access and Verify Codes on their home systems and then carry\n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can be queued for install at non-peak hours.\n With the Users on the system there is a small chance that a user would\n get a CLOBER/NOSOURCE error.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*165'\nthat authentication to other systems where they may not be entered in the\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\nNew Person File (NPF). A packet of information is carried with the user\nto the system being visited, and that information is then entered in the\n\n
\n1. HOU-1099-72362.\n \n \nRoutine Summary:\n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;07/10/95\n \nChecksums: CHECK^XTSUMBLD\n Option SYNC FLAG FILE CONTROL [XUTM SYNC] does not appear to allow\n==========\n \nRtn Nm Chksum Before Chksum After Patch List\n====================================================================\nZTMS2 5847661 6602171 2,18,23,36,67,118,127,163\nXUTMSYNC 655698 655786 163\n \n \nInstallation Instruction:\n========================\n users to remove old entries in the Task SYNC FLAG file ^%ZISL(14.8,.\n1. Users are allowed to be on the system during the Installation.\n \n2. Routine mapping is NOT recommended for these routines. If you\nare using routine mapping, review your mapped set and ensure that\nthese routines are NOT in your mapped routine set before proceeding\nand rebuild your map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n Routine ZTMS2 and XUTMSYNC has been revised to correct this problem. \n4. STOP TASKMAN and STOP other background filers. "DO STOP^ZTMKU"\n \n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n Install Package(s)\n INSTALL NAME: XU*8.0*163\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n \n \n6. DSM/AXP Sites - Answer NO to the question "Want to MOVE routines\n to other CPUs?"\n \n7. DSM/AXP Sites: If the routines were unmapped per STEP #2, the\n mapped set should be rebuilt once the installation has run to\n completion.\n \n8. After installing this patch:\n OpenM Sites - you donot need to move anything, skip this step.\nTest Sites:\n DSM/MSM Sites - you need to move a total of 1 routine from your\n production account to each manager account:\n \n ZTMS2\n \n \n9. And in the manager account, (Openm sites remain in VAH)\n all sites:\n \n DO RELOAD^ZTMGRSET\n===========\n Select the System\n Patch number to load: 163\n ===\n \n10.DSM Sites, after patch has installed, rebuild your map set.\n \n \n11.Restart TASKMAN with "D RESTART^ZTMB. DSM sites this may\n require a privileged user.\nHouston, TX - 580\n\n
\nIn working with the RAI/MDS folks a problem was found in how the FMTHL7\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXLFCRC n/a 568962 **166**\nXLFDT 4050775 4352260 **71,120,166**\n\nand HL7TFM API's of XLFDT worked. This has been fixed.\nList of preceding patches: 120\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n>>>Taskman may remain running.\n\n 1. DSM sites - Some of these routines are usually mapped,\nFM stores midnight as 3000803.24 and HL7 standard requires it to be sent\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \nas 200008040000-0800 i.e. Midnight of the night extending from Aug 3 to\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\n This patch can be queued and installed at any time.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\nAug 4, 2000. \n option:\n Install Package(s) 'XU*8.0*166'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n\n =========================================================================\nAlso a new routine XLFCRC to compute CRC's, both 16 and 32 bit.\nSee DBIA 3156 for details.\n\n\n
\nIVM-0400-31566\nThis causes the calling routine to get an error. Fix to see that on a time-\nout the device is closed.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;June 25, 1999\n\n Checksum\nRoutine Old New 2nd Line\nAn option queued in the option scheduling file that didn't have a \nXLFNSLK 7523173 7558282 **142,151**\nXQ1 11958439 11902300 **1,15,59,67,46,151**\n\nList of preceding patches: 46, 142\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Do not allow users to log in to the system during installation.\nrescheduling frequency would not have the ZTQPARAM variable or other \n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\nparameters available. This was because the entry was deleted from the \n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER/NOSOURCE\n errors is acceptable, then users can stay on the system.)\noption schedule file before the variables were set-up. The fix was to set-\n Also place TASKMAN in a wait state.\n Option: Place Taskman in a WAIT State\n \n 5. Use "D ^XPDKRN" then:\n Install Package(s) 'XU*8.0*151'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\nup the variables first.\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n\n 7. Allow users to sign-on.\n Remove TASKMAN from the wait state.\n Option: Remove Taskman from WAIT State\n=========================================================================\n\nIt has been found in testing at Bay Pines that if the call to the DNS times \nout the XLFNSLK routine fails to close the device used to call the DNS. \n\n
\n*** Note there are routines that need to moved as part of this patch.\n levels so we have some room for our DO's.\n 7. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 162\n ===\n \n 8. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\n \nBAY-0600-31579 When adding a HUNT GROUP device to the IO queue the\nMIN-0600-41387 device type wasn't added at the top level. This would\n cause errors at I2+2^%ZTMS1. Fixed to set the correct\n node. ZTM4\n \nISL-1199-51207 When trying to restore the variables on a Cache system\n XTER2 would get an error. The special Cache data item\n from $ZU(56) is stored. This was fixed by changing the\n \n name from OpenM_ZU to $ZU(... then %ZTER saves it because \n XTER2 already knows not to restore anything that starts \n with a "$".\n \nNVS call The new Taskman parameter Balance interval was not getting\n picked up correctly. Fixed to get the right data. ZTM5\n \nRequest from the Mailman developer to save off data in ZTLOAD so user can\nqueue reports to p-message. Change to ZTLOAD1.\n \n BRX-0999-10965 The error trap doesn't record any data for stack overflow\nFor standard VA systems the new routine ZUSET will rename the correct ZU*\nroutine to ZU for the site.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;JUL 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\n of allocation errors. Before on a allocation error\nZTER 18980475 18198227 **8,18,32,24,36,63,73,79,86,112,118,162**\nZTER1 4369079 4369129 **18,24,36,49,112,162**\nZTLOAD1 6808427 6923394 **112,118,127,162**\nZTM4 2164226 2223405 **1,118,127,162**\nZTM5 4417939 4418054 **24,36,118,127,136,162**\nZTMS 5488776 5607220 **2,18,24,36,67,94,118,127,136,162**\nZUMSM 3349196 3457106 **13,42,49,94,107,162**\nZUONT 1992793 2038011 **34,94,118,162**\nZUSET n/a 751876 **162**\nZUVXD 4517687 4620305 **13,24,84,94,118,162**\n we would call the M vendors error trap. The current \n\nList of preceding patches: 107, 118, 136\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nInstallation:\n \n>>>Users may remain on the system.\n \n 1. DSM sites - Some of these routines are usually mapped,\n vendors error trap tries to set variables and also gets\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n an error. The fix to this problem was to do a exclusive\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can not be queued. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n kill to get some room and then record the error.\n option:\n Install Package(s) 'XU*8.0*162'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step. \n For stack overflow error we pop the stack back 8\n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n \nZTER\nZTER1\nZTLOAD1\nZTM4\nZTM5\nZTMS\n \n\n
\nMSG # 19318228 Controlled Subs needed to have a second person witness\n========================================================================= \nInstallation:\n \n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\nwhen 'wasting a narcotic dose'. This patch adds a new supported reference\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Inhibit users from login into the system. (If you install when few\n user are on the system and the possibility of some CLOBER errors is\n acceptable then users can stay on the system.)\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\nto provide a way to ask for a Access/Verify Code pair with out changing\n Install Package(s) 'XU*8.0*26'\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\n 8. Enable user's login.\n \n=========================================================================\nSUPPORTED REFERENCE.\n\n$$WITNESS^XUVERIFY(prefix_text,keys)\nDUZ or other gyrations.\n\n Returns the IEN of a entry in the new person file that has entered a\n valid ACCESS/VERIFY code pair.\n \n prefix_text is a string that will be displayed before both the ACCESS\n and VERIFY code prompts.\n \n keys is a list of '^' delimited security KEY names, One of which the\n person entering the A/V code must have so that the IEN is returned.\n \n\n$$CHKAV^XUVERIFY(access_";"_verify)\n\n Returns the IEN of the entry in the new person file that has this\n valid ACCESS/VERIFY code pair.\n\n\nroutine new checksum\nXUS 7592994\nXUVERIFY 3907067\n\n\n
\nWhen placed in production the change in HL7 to call the XLFDT routine for \nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXLFDT 4352260 4356861 **71,120,166,168**\n\nList of preceding patches: 166\nSites should use CHECK^XTSUMBLD to verify checksums.\nHL7 to FileMan date conversion exposed an existing bug in the HL7TFM code.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n>>>Taskman may remain running.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \nThis patch corrects that problem.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\n This patch can be queued and installed at any time.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*168'\nBlood Bank Team Coordination:\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n=============================\nClearance - Sept. 7, 2000\n\nRoutine Summary\n\n
\n \nXU*8*162, no users are allowed on the system.\nTo avoid the problem:\nInhibit log on and install patch XU*8.0*162 per instructions make sure you\nhave a session logged in at programmer mode and immediately install patch\n170 per instructions in this patch. Allow users back in the system.\n \nCMH-0800-N3105\nPatch XU*8*162 made a call to $$AVJ^%ZOSF in place of $$AVJ^%ZOSV in ZUONT.\nThis caused a NOLINE error. Fixed to make the correct call. This affects \nCache sites only.\n**** Users will need to be off the system during this install ****\n \nMVW-0800-22126, NJH-0800-22956, TAM-0800-32655, CLA-0800-22898\nMAC-0900-60221\nPatch XU*8*151 did fix the use of the ZTQPARAM variable or other \nparameters available if the scheduled option didn't have a re-queue frequence \nbut if the option was on a schedule it broke the re-schedule. \nThis patch fixes the re-scheduling. As part of the post INIT it will go\nthru the Scheduled options (file 19.2) an reschedule any that have a past \ndate to run.\n \n**** Taskman will need to be in a wait state during this install ****\nBlood Bank Team Coordination:\n=============================\nClearance - Sept. 8, 2000\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n \n Checksum\n \nRoutine Old New 2nd Line\nXQ1 11902300 12116128 **1,15,59,67,46,151,170**\nXUTMPCH n/a 930054 **170**\nZUONT 2038011 2038331 **34,94,118,162,170**\nZUSET 751876 1042105 **162,170**\n \nList of preceding patches: 151, 162\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \n !!! WARNING!!!\nInstallation:\n \n>>>Do not allow users to log in to the system during installation.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \nNT sites need to install patch XU*8*162 and XU*8*170 TOGETHER\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nMake sure you have Patch XU*8.0*162 and XU*8.0*170 before going any\n 4. Inhibit users from login into the system. \n Get all current users off the system or they will get an EDITED\n error when they return to the menu system.\n Also place TASKMAN in a wait state.\n Stop BACKGROUND task or they will get an EDITED error when done.\n \n 5. Use "D ^XPDKRN" then:\n Install Package(s) 'XU*8.0*170'\n ==========\n \nfurther. XU*8*162 is required for this patch but there is a problem with\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n This routine will rename the correct routine to ZU for you.\n Rename ZUONT to ZU, OK? No// >>>>Cache sites answer YES\n >>>>DSM sites answer NO\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \nroutine ZUONT which has big impact on NT sites. After installing patch\n 7. Allow users to sign-on.\n Remove TASKMAN from the wait state.\n \n=========================================================================\n\n
\nThis patch is in support of the following Broker NOIS\nchanged by patch XU*8*134 (Name Standardization)\n\nThis patch also provides support for the Broker User Info properties.\n\nMIW-0500-42196 XUS1 Patch XU*8*165 broke the auto sign-in (single sign-in).\n The routine was already in this patch so the fix was\n added to the routine.\n\nBlood Bank Team Coordination:\n=============================\nISW-1299-21488, ISW-1299-22382\nClearance - August 17,2000\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXUS1 10540362 10615522 **9,59,111,165,150**\n\nXUSER 1616062 2107735 **75,97,99,150**\nXUSRB 6041270 6120921 **11,16,28,32,59,70,82,109,115,165,150**\nXUSRB2 783689 1351749 **115,150**\nXUSRB4 n/a 1401530 **150**\n\nList of preceding patches: 99, 115, 165\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\nThis patch also adds a new field to the new person file under the Division\n\n>>>Users may remain on the system.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\nfield. This new field is Default and is used by the GUI log-on to select\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\none division to pre-select. This is only needed for users that have more \n non-peak time.\n This patch can be queued for install at non-peak hours.\n Taskman can remain running. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*150'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\nthan one division.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\n\n\nThis patch updates the EDIT AN EXISTING USER form. This form was also\n\n
\nSee patch XU*8*178 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nHUN-0800-22470 The change that patch XU*8*153 made to "prohibited \n user problems. Here is the new message:\n \n No PRIMARY MENU assigned to user or User is missing KEY to menu!\n\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\nBAY-0600-31674 times for sign-on" did not work as planed. This patch\n Checksum\nRoutine Old New 2nd Line\nXQCHK 18037162 18364121 **47,110,149**\nXUS 8138431 8139177 **16,26,49,59,149**\nXUS1A 7137988 5648404 **153,149**\nXUS3 5732668 5735173 **32,149**\n\nList of preceding patches: 32, 59, 110, 153\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n also add a new message to tell the user that is blocked\n========================================================================= \nInstallation:\n\n>>>Do not allow users to log in to the system during installation.\n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n from sign-on what the prohibited time are.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n \n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Current users can remain on the system.\n Inhibit new users from login into the system.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*149'\nANN-0598-41422 The message of "No Access Allowed for this User"\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n 7. Allow new users to login to the system.\n=========================================================================\n was not helpful so a new message has been added to \n the sign-on to report that the user doesn't have a\n PRIMARY MENU or KEY to assist IRM with evaluating\n\n
\nNOIS\ncross-reference of each field. The post-INIT will reindex the data\ncorresponding entry in the Name Components file.\n \nFor example, if FIX^XLFNP176 finds a name in the .01 field of the New\nPerson file stored as:\n \n Name: SMITH,JOHN M D\n \nit assumes M D is a suffix, and changes the name to SMITH,JOHN MD. It also\nstores MD in the SUFFIX field (#5) in the Name Components file.\n \nto setup the cross-reference. Some experamental fields from the\n \nHow to use:\n----------\nFIX^XLFNP176 can be run with VISTA users online. However, it is\nrecommended that it be run during non-peak times.\n \nRun FIX^XLFNP176 from programmer mode:\n \n >D FIX^XLFNP176\n \ndevelopment account were send and will be removed. Routine XUINPCH3\nThe routine need only be run onced to fix the problem.\n \n \nCustomizing the list of problem suffixes checked by FIX^XLFNP176\n----------------------------------------------------------------\nIf you wish to modify the list of problem suffixes checked by XLFNP176,\nyou can edit the text at line tag LINE^XLFNP176. Replace the list with an\nup-arrow (^)-delimited list of suffixes that may occur at the end of the\nNames stored in your New Person file.\n \nis just the Post-INIT routine. The discription was changed on other\nBlood Bank Team Coordination:\n=============================\nClearance - Nov. 2, 2000 \n \n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\nfields.\n Checksum\nRoutine Old New 2nd Line\nXLFNP176 n/a 9524118 **176**\nXUINPCH3 555958 1351290 **115,176**\n\nList of preceding patches: 115\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\nThe fields being loaded:\n\n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n\n\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n53.1,53.2,53.3,53.4,53.6,53.7,53.8,54.1\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 3. Users can remain on the system. \n This patch can be queued and installed at any time.\n\n\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*176'\n =========\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n\n=========================================================================\n\n \nMIA-0700-30488\nNAME STANDARDIZATION: SPACES WITHIN SUFFIXES\nNOIS\n====\nANN-0800-42960\nMAN-0800-12845\n \nBackground\n==========\nThe Name Standardization Patch (Kernel Patch XU*8.0*134), which was\nreleased on April 6, 2000, includes a data conversion run as part of the\nLEB-0800-20388\nPost-Installation of that patch. The data conversion converts all names\nstored in the .01 field of the New Person file to standard form. It also\nparses each name into its component parts (Given Name, Middle Name, Family\nName, and Suffix), and stores those component parts in the Name Components\nfile (#20) also released with the patch.\n \n \nProblem\n=======\nThe data conversion looks for specific suffixes at the end of the name,\nDAY-1000-40325\nsuch as MD, PHD, and DDS. However, it was not accounting for suffixes that\ncontain periods, such as M.D., Ph.D. and D.D.S. When the data conversion\nfinds a name with a suffix that contains periods the name could be\nincorrectly parsed.\n \nFor example, suppose the name as stored in the .01 field of the New Person\nfile before patch XU*8.0*134 was installed was:\n \n Original name: SMITH,JOHN M.D.\n \nSBY-1000-30177\nThe result after the data conversion would be:\n \n New standardized name: SMITH,JOHN M D\n \n Name components as stored in the Name Components file:\n Given: JOHN M.\n Middle: D.\n Family: SMITH\n Suffix:\n \n\nNote that in the above, the suffix M.D. was not recognized as a suffix.\n'M' was considered part of the person's first (given) name, and 'D' was\nconsidered the middle initial.\n \n \nSolution\n========\nIn order to correct names that were parsed incorrectly by the data\nconversion, routine XLFNP176 is included in this patch. The FIX^XLFNP176\nentry point loops through the entries in the New Person file and looks for\nPatch XU*8*165 unintentionly send all fields in file 200 not just the\nnames that may have been standardized and parsed incorrectly. It will then\noptionally correct the name in the New Person file and the corresponding\nname components in the Name Components file.\n \nNOTE: Sites should still install patch XU*8*134. The FIX^XLFNP176 entry\npoint is designed to run on systems on which the data conversion has\nalready been run.\n \n \nFIX^XLFNP176 Description\nones needed for the patch. This patch fixes the problem caused in\n========================\nThis directly mode utility loops through all entries in the New Person\nfile (#200) and looks in the .01 field for names that end in any of the\nfollowing strings (without the single quotes (')):\n \n ' M D'\n ' D D S'\n ' PH D'\n ' R N'\n ' D P M'\nthe DEA# and VA# fields. The main problem was a change made to the\n ' D O'\n ' P A'\n ' N P'\n ' C R N A'\n ' L P N'\n \nIf it finds any of the above strings at the end of the name, it assumes\nthat string is a suffix. It removes the spaces from the suffix and stores\nthe modified name in the .01 field of the New Person file. It also stores\nthe suffix (without embedded spaces) in the Suffix field (#5) of the\n\n\n1. HOU-0198-70327.\n Manage Mailman ...\n INSTALL NAME: XU*8.0*154\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES// NO\n == \n \n6. DSM/AXP Sites - Answer NO to the question "Want to MOVE routines\n Menu Management ...\n to other CPUs?"\n \n7. DSM/AXP Sites: If the routines were unmapped per STEP #2, the\n mapped set should be rebuilt once the installation has run to\n completion.\n Programmer Options ...\n Operations Management ...\n Spool Management ...\n System Security ...\n Taskman Management ...\n User Management ...\n Application Utilities ...\n Capacity Management ...\n This patch corrects the %DSM-E-NUMBER, illegal number error should\n Captioned OP in a Template \n HL7 Main Menu ...\n Suggestion Box\n \nSelect Systems Manager Menu Option: M\n 1 Manage Mailman \n 2 Menu Management \nCHOOSE 1-2:\n111111111111111111111111111111111111111111111111111111111111111111\n%DSM-E-NUMBER, illegal number\n an extraordinarily long be entered (usually caused by something or\n%DSM-I-ATLABEL, C+2^XQ71:4 R XQJ:DTIME S:'$T XQJ=U I XQJ?1N.N G\nC:'$D(XQ(XQ\nJ-1#20+1)) W " " S XQUR="",XQY=+XQ(XQJ-1#20+1) I XQY>0 S\nXQY0=$P(^XUTL("XQO",XQ\nDIC,"^",XQY),U,2,99),XQA=$P(XQ(XQJ-1#20+1),U,3) G W\n>\n \n**************** Corrected Below *******************************\n \n \n someone hand laying on the keyboard). An example is display below:\nSelect Systems Manager Menu Option: M\n 1 Manage Mailman \n 2 Menu Management \nCHOOSE 1-2:\n1111111111111111111111111111111111111111111111111111111111111111\n \n 1 Manage Mailman \n 2 Menu Management \nCHOOSE 1-2: \n \n \n \nNOTE: Returns the User back to the Selection Prompt for the correct\n choice.\n \n \n \nTest Sites:\n===========\nHouston, TX - 580\n \n \n \nRoutine Summary:\n================\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;8.0;KERNEL;**[Patch List]**;07/03/95\n \nChecksums: CHECK^XTSUMBLD\n==========\n Core Applications ...\n \nRtn Nm Chksum Before Chksum After Patch List\n====================================================================\nXQ71 13242248 13403778 154\n \n \nInstallation Instruction:\n========================\n1. Users are allowed to be on the system during the Installation.\n \n Device Management ...\n2. Routine mapping is NOT recommended for these routines. If you\nare using routine mapping, review your mapped set and ensure that\nthese routines are NOT in your mapped routine set before proceeding\nand rebuild your map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nloads the patch into a Transport Global onto your system.\n \n4. You Do Not need to stop TaskMan or the background filers.\n \n FM VA FileMan ...\n \n5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s)\n\n\nBRX-0900-12121\nTo support P-MESSAGE a change was made to ZTMS3 to move the clean-up\nof temp globals to after the device has been closed.\n\nATG-0700-31453\nIn working with NVS it has been found that at times the persistent\ntask restart code is too good and schedules many copies of the same task\nbefore one starts and signals that it is running. The other copies\nget caught waiting for a lock on the global node ^%ZTSCH("TASK",<task>).\nThis has been fixed by using a timeout on earlier lock before the\ntask is setup. This change was made in ZTMS2.\nWith changes to the security checks that Mailman makes before allowing\n\nXUTMOPT is included to provide an API for applications to check on\nscheduled tasks.\nBlood Bank Team Coordination:\n=============================\nClearance - Nov. 2, 2000\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\na message to be sent, any tasks that Taskman start as part of the system\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXUTMOPT 4026913 4559820 **2,111,112,118,127,175**\nZTM0 6089712 5998062 **42,36,67,88,118,127,136,175**\nZTMS2 6724503 7001305 **2,18,23,36,67,118,127,163,167,175**\nZTMS3 9642200 9642200 **1,18,36,49,64,67,94,118,127,136,175**\n\nList of preceding patches: 136, 167\nstartup need to have the DUZ set to a valid user. After talking with the\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n>>>Taskman does need to be stopped.\n\n 1. DSM sites - This routines maybe mapped,\n so you will need to disable mapping for the affected routines.\nDBA it was decided to have Taskman use POSTMASTER as the user (DUZ=.5).\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\nThis change will only affect tasks started when Taskman first starts,\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\n Also place TASKMAN in a wait state.\n Use option: Place Taskman in a WAIT State\n \n 5. In Programmer mode:\n Use "D ^XPDKRN" then\nthat have the special queueing field set to STARTUP or Startup Persistent.\n Install Package(s) 'XU*8.0*175'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to one several routine from \nZTM0 is the routine that has been changed for this patch.\n your production account to each manager account:\n \nZTM0\nZTMS2\nZTMS3\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n\n Patch number to load: 175\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n \n 11. Remove TASKMAN from the wait state. (DO RUN^ZTMKU)\n\n=========================================================================\n\n\n\n\n-- The '%Index of Routines' option doesn't call the new version.\n of the VOLUME SETS you have listed, once the installation starts.\n \n MSM Sites - Once the install starts, KIDS will pause 5 minutes to\n allow time for you to go to the other CPUs, and make them ready to\n receive the patched routines.\n 'D ^XUP' to setup the enviroment, then 'D ^XPDCPU' to load them.\n \n 8. After installing this patch, you need to move several routines from \n your productions account to the manager account:\n\n\n ZIS5\n ZIS6\n ZISC\n ZISHVXD\n ZISHMSM\n ZISUTL\n ZOSV1VXD\n ZTER\n ZTER1\n ZTM\nNOIS DAY-0496-41713 Submanager count always low. Site and John Beaufait\n ZTM5\n ZTMDCL\n ZTMS \n ZTMS0 \n\n\n and in the manager account rename\n\n Example: ZL ZISUTL ZS %ZISUTL\n \ndid a great job of researching this problem.\n ZIS5 to %ZIS5\n ZIS6 to %ZIS6\n ZISC to %ZISC\n ZISHMSM to %ZISH (MSM only)\n ZISHVXD to %ZISH (VAX DSM only) \n ZISUTL to %ZISUTL\n ZOSV1VXD to %ZOSV1 (VAX DSM only)\n ZTER to %ZTER\n ZTER1 to %ZTER1\n ZTM to %ZTM\n\n ZTM5 to %ZTM5\n ZTMDCL to %ZTMDCL\n ZTMS to %ZTMS\n ZTMS0 to %ZTMS0\n \n\n 9. MSM sites now move both the % and non-% new routines to the MGR\n uci of the other CPU's. \n 9. AXP Sites, after patch has installed, rebuild your map set.\n 10. Restart Taskman and enable user's login.\nNOIS WBP-0596-21109, SDC-0496-60862 After patch XU*8*18 if the site has\n \n\n=========================================================================\n\nerror screens setup in taskman, a task getting an error would not get\nits status updated. This was especially true when the error happened\nsetting up Network Mail tasks, Follow-up Mail would check on the status\nof the task and not start new ones believing that one was starting.\nE3R #8206 On VAX DSM to have TelNet links HALT from ZUVXD and not wait\nThanks to David Dahlstrand for noticing the link.\n\nNOIS PUG-0596-51586 The new OPEN^%ZISH call wouldn't work to write a \nnewversion of a file. Problem was only with the VAX DSM version.\n\nFILEMAN TEAM Problems with $$FTG^%ZISH on VAX DSM and reading records\ngreater than 255 char. ZISHMSM had the same problem.\n\nNOIS DES-0795-41067 TaskMan on MSM system could see the SYSTEM SHUTDOWN\nflag and would set the X-ref of the Inhibit Logon's field to prevent users\nfor the next user.\nfrom login on. If the shutdown was aborted the X-ref would keep user from\nlogin on but looking at the Volume Set file would show the Logon Inhibit\nfield still set to NO, this was confusing to sites. This has been fixed\nby adding a new item to the set of codes System Shutdown that is set and\ncleared by taskman.\n\nNOIS IHS-0696-N0286 Site found a call to a missing TAG in %ZISH, it was \npart of some code that is undocumented and the call has been removed.\n\nNOIS DAY-0196-42100 Intermittent UNDEF in XQALDEV. One entry point didn't\n\nhave all the variables setup.\n\nNOIS HUN-0396-20414 At VAX DSM sites running taskman from DCL the log \nfiles could excced the VMS limit and bring Taskman to a stop. The fix\nis to not record a log file.\n\nFORUM errors. UNDEF Error at SETVAR^%ZIS1 when slecting a item from the\nLocal Synonym list.\n\nBRX-0296-10688 Site needed to help identify devices to users. Site wanted\nNOIS DAY-0596-40526 A syntax error at RES+1^%ZOSV1VXD\nthe display the Mnemonic. This is a multipule and would cause problems.\nAdded code to display the Device Location like the FM loopup does.\n\n\nroutine new checksum\nXQALDEL 13827021\nZIS5 7634324\nZIS6 9961139\nZISC 8469046\nZISHMSM 5232475\n\nZISHVXD 6949854\nZISUTL 2111550\nZOSV1VXD 2355845\nZTER 18727059\nZTER1 5363987\nZTM 7509587\nZTM5 3649126\nZTMDCL 527042\nZTMS 4863268\nZTMS0 3205484\nNOIS SDC-0596-60064 Problem was that users couldn't use ScreenMan after\nZUVXD 4856063\n\n========================================================================= \nInstallation:\n\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\ndoing 'Print a spool document' because the IO parameters didn't get reset.\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 5. Stop TASKMAN.\n Inhibit users from login into the system. (If you install when few\n user are on the system and the possibility of some CLOBER errors in \n\n %ZIS is acceptable then users can stay on the system.)\n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Install Package(s) 'XU*8.0*24'\n 7. VAX DSM Sites in the production account rename ZUVXD to ZU.\n \n MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n NOTE: You will see the following message: TASKMAN is not running.\n You must run the routine XPDCPU in the production UCI for each\n\n
\nThis patch adds the DELSTAT API to the alert functionality to provide\nlist.\n \nExample: D DELSTAT^XQALBUTL("OR;14765;23",.RESULTS)\n \nReturned: The value of RESULTS indicates the number of entries in\n the array. The entries are then ordered in numerical \n order in the RESULTS array.\n RESULTS = 3\n RESULTS(1) = "146^0" User 146 - not deleted\n RESULTS(2) = "297^1" User 297 - deleted\ninformation on whether an alert has been deleted for various users. The\n RESULTS(3) = "673^0" User 673 - not deleted\n \n \nRoutine Summary:\n================\n \n The following routines are included in the patch. The second\nline of each of these routines now look like this:\n \n ;;8.0;KERNEL;**[patch list]**; Jul 05, 1995\nAPI was requested for CPRS functionality.\n \n Checksums were obtained using CHECK^XTSUMBLD\n \nRoutine Before After Patch List\n---------------------------------------------------------------\n \nXQALBUTL 4983080 8443097 **114,125,171**\n \n \n Installation Instructions:\n \n ==========================\n \n 1. These routines are not usually mapped on systems that allow\n mapping so you may not have to disable mapping.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options: \nDELSTAT - For the most recent alert with XQAIDVAL as the PackageID\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n Install Package XU*8.0*171\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to \n other CPUs?'. Enter the names of your Compute and Print server(s).\n AXP sites should answer "no" to this question.\n 6. Rebuild your mapped set if necessary.\n 7. If users are allowed to remain on the system during installation\npassed in, on return array VALUES contains the DUZ for users in \n errors may occur when the routines are loaded.\nVALUES along with an indicator of whether the alert has been \ndeleted or not, e.g., DUZ^0 if not deleted or DUZ^1 if deleted. \nNote that contents of VALUES will be killed prior to building the \n\n\nAs a part of its security the RPC Broker requires that a Remote Procedure\nIn addition, this patch modifies the Screenman option for Editing Options\nto add the ability to add context options within the ITEMS subfile.\n \nThis modification was requested and tested by the developers working on a \nPatient Lookup object and Smart Card applications.\n \n \nRoutine Summary:\n================\n \nCall (RPC) be included within a Broker (Client/Server) or Context option,\n The following routines are included in the patch. The second\nline of each of these routines now look like this:\n \n ;;8.0;KERNEL;**[patch list]**; Jul 05, 1995\n \n Checksums were obtained using CHECK^XTSUMBLD\n \nRoutine Before After Patch List\n---------------------------------------------------------------\n \nand that this option be included within the user's menu tree. This has\n XQCS 127133342 13170786 15,28,82,116,115,177\n \n Installation Instructions:\n ==========================\n \n 1. These routines are not usually mapped on systems that allow\n mapping so you may not have to disable mapping.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your \nresulted in some context options including hundreds of RPCs. This patch\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n Install Package XU*8.0*177\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to \n other CPUs?'. Enter the names of your Compute and Print server(s).\nmodifies XQCS to look also at the ITEMS subfile (which has been used for\n AXP sites should answer "no" to this question.\n 6. Rebuild your mapped set if necessary.\n 7. If users are allowed to remain on the system during installation\n errors may occur when the routines are loaded.\nmenu items) within a context option, and if these point to other context\noptions, the RPCs included in that context will be included as a part of\nthe original context.\n \n\n
\nIV&V testing, Inpatient Meds, Pharmacy\n\nBlood Bank Team Coordination:\n=============================\nClearance - Nov. 2, 2000 \n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n\n Checksum\nRoutine Old New 2nd Line\nXLFDT 4356861 4357199 **71,120,166,168,179**\n\nList of preceding patches: 168\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\nIn testing a problem was found that HL7TFM will return trailing zeros when \n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\nconverting a HL7 date like 200101091230 would return a value like 3010109.1230 \n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\nthis causes a problem in sorting. There will be a follow-up patch to finish the \n This patch can be queued and installed at any time.\n This patch can be queued for install at non-peak hours.\n TASKMAN can remain running.\n Option: Place Taskman in a WAIT State\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*179'\n ==========\nchanges to address correct conversion of Midnight.\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO \n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n\n\n\n=========================================================================\n\nBefore w $$HL7TFM^XLFDT(200101091230)--> 3010109.1230\nAfter w $$HL7TFM^XLFDT(200101091230)--> 3010109.123\n\n
\nAdd Specialty Codes to Person Class file.\n\n
\nLAS-1000-62717, BOI-1000-52970 XUS1A, XUESSO1 \n \n Checksum\nRoutine Old New 2nd Line\nXUESSO1 4118958 4127624 **165,183**\nXUS1A 5648404 5708683 **153,149,183**\n \nList of preceding patches: 149, 165\nSites should use CHECK^XTSUMBLD to verify checksums. \n \n========================================================================= \nDuring the early testing of RDV the DUZ value was hard set just before\nInstallation:\n \n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\nthe call to the RPC. When the code was fixed to properly set DUZ the\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nold code didn't get removed. This has been fixed.\n \n 4. Users can remain on the system.\n This patch can be queued and installed at any time.\n TASKMAN can remain running.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*183'\n ==========\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// YES \n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n
\nNOIS: DAY-1000-42520 Vista Security (Verify Code) \n letters (upper case and lower), numbers, and, characters \n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n that are neither letters nor numbers (like "#", "@" or "$"). \n 4. Users can remain on the system if installed at non-peak hours.\n There is a small chance that a user could get a CLOBER error if they\n are signing on at the time the routines change. \n This patch can be queued and installed at non-peak time. \n TASKMAN can remain running. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following \n option: \n Install Package(s) 'XU*8.0*180' \n ==========\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO \n \n No Options or Protocols need to be placed out-of-order. \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO \n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set. \n=========================================================================\n b. Passwords shall be changed no less frequently than every 90 days. \n Information systems shall not permit re-assignment of the last \n three passwords used. \n \n c. Accounts that have been inactive for 90 days shall be disabled. \n \n d. To preclude password guessing, an intruder lock out feature \nThese changes are required to meet VHA DIRECTIVE 6210 \n shall suspend accounts after five invalid attempts to log on. \n Where round-the-clock system administration service is available, \n system administrator intervention shall be required to clear a \n locked account. Where round-the-clock system administration \n service is not available, accounts shall remained locked out \n for at least ten minutes. \n \nHere is what was done based on the requirement from VHA POLICY:\nItem a. Because VistA has been case-insensitive for many years, we chose\n to retain this characteristic. This means that VistA only has three \nAvailable at http://vaww.domain.ext/publ/direc/health/direct/vha6210d.pdf\n sets of characters to build a password from: alpha, numeric and \n punctuation. The change from the past requirements is the new \n requirement for punctuation characters and an increase in length \n from 6 to 8 characters.\n \n The Kernel XUS2 routine was changed to require that \n verify codes be composed of the following three groups of \n characters: alpha, numeric, and punctuation.\n \nItem b. This rule was implemented by changing the valid range in the data \nThe rules listed below are from the Document "VA Account and Password \n dictionary and then checking the value in the KERNEL SYSTEM \n PARAMETERS file (#8989.3) and resetting the value if it is found \n to be greater than 90. Kernel has long kept old verify codes based \n on the date they were changed. A change has been made to limit the \n time frame for removal in option "Purge Log of Old Access and Verify \n Codes" [XUSERAOLD].\n \nItem c. This rule was implemented by making changes to the scheduled Kernel \n option 'Automatic Deactivation of Users' [XUAUTODEACTIVEATE] routine \n XUSTERM1. This option has been changed to check each user's last \nManagement Interim Policy" \n sign-on date and if it is more than 90 days old, sets the DISUSER \n field for that user. If this happens the user will get a "No Access \n Allowed for this User." message when they trying to logon.\n \n Note: The DISUSER field is shown on the 'User Inquiry' and is on the \n second page of the Kernel option "Edit an Existing User" [XUSEREDIT]. \n \nItem d. Kernel has always implemented a form of 'lockout'. Changes where made \n to the Kernel System parameters file DEFAULT # OF ATTEMPTS and DEFAULT \n LOCK-OUT TIME field's. The values in the KSP were checked and changed \n \n to meet the new limits for these fields.\n \n \n Note: In addition, the sign-on code was changed to echo \n an asterisk (*) for each character entered. This \n follows the Microsoft Windows login style, which is \n a change from the VMS login style.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\n a. Controls shall be implemented to require strong passwords. \nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n \n Checksum\nRoutine Old New 2nd Line\nXUINPCH4 n/a 786391 **180**\nXUS 8139177 8362765 **16,26,49,59,149,180**\nXUS2 14055468 15802718 **59,180**\nXUS4 3275391 3759854 **180**\nXUSPURGE 6034721 4746135 **180**\n Passwords shall be at least eight characters in length, and \nXUSRB 6139976 6227685 **11,16,28,32,59,70,82,109,115,165,150,180**\nXUSTERM1 12539120 11515045 **102,180**\nXUSTZ 3010944 3161912 **36,180**\n \nList of preceding patches: 36, 102, 149, 150\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \n========================================================================= \nInstallation: \n contain three of the following four kinds of characters: \n \n>>>Users may remain on the system. \n>>>Taskman does not need to be stopped. \n \n 1. DSM sites - Some of these routines are usually mapped, \n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n\n
\n This patch changes the way KIDS secures a Packman Message. The prompt:\n\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no user should be using KIDS during the install of this patch.\n===========================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 'Enter the scramble hint:' \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n has been removed. A new prompt:\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n ===========================================================================\n \n ROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Name Checksum Patch List\n -----------------------------------------------------------\n 'Do you wish to secure this message? No//'\n XPDTP 2358145 21,40\n\n\n ;;7.1;MailMan;**33**;Jun 02, 1994\n \n XMASEC 4454626 33\n XMD 4879878 33\n ============================================================================\n will be asked after you enter the text for a message. This correct the\n problem that was identified by Nois CLE-0696-40353.\n This patch is the same as MailMan patch XM*7.1*33. Both patches contain\n the same MailMan and Kernel routines.\n===========================================================================\n\n
\n XU*8*155\nexperienced an endless loop when control characters were somehow\nentered into the prompt looking for an option name. This patch changes\nthose errant lines of code to standard, Kernel calls to UP^%XLFSTR().\n \nList of Test Sites\n==================\nWhite City, OR\nRoseburg, OR\nBay Pines, FLA\nMike Boggess\nDescription\n \nRoutine Summary\n===============\n \nThe second line of these routines should look like this:\n ;;8.0;KERNEL;**<Patch List>**;Jul 10, 1995\n \nRoutine Old New Patch List\n \nXQ11 10587910 10802256 155\n===========\nXQ7 2523046 2648795 44,60,155\nXQSET 11252847 11378596 28,82,155\nXQSRV 9902131 10172674 155\nXQSRV5 18958753 19104128 155\nXQT 14503760 14728981 20,47,46,37,155\nXQT3 13422394 13658700 46,37,155\n \nSites should use CHECK^XTSUMBLD to verify checksums.\n \nThis patch was reviewed and approved by Blood Bank on 11/21/00.\n \n \n========================================================================= \nInstallation:\n \n>>>Users may remain on the system.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n With the advent of the Cache 3.2 Operating system the underlying\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\ncharacter set of ASCII has been changed to Latin I, an ISO standard that\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peakpeak time.\n This patch can be queued for install at non-peak hours.\n With the Users on the system there is a small chance that a user\n would get a CLOBER/NOSOURCE error.\n \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\nthe VA supports. This change caused, however, an ancient piece of code to\n option:\n Install Package(s) 'XU*8.0*155'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\nbreak that has been promulgated throughout the Menu System over the years\nwhich was used to change strings of code to all uppercase. White City\n\n
\nNot actually applied.\n\n
\nSee patch description.\n\n
\nNOIS CPH-0301-43012\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXUESSO1 4127624 4782174 **165,183,196**\n\nList of preceding patches: 183\n CPH-0301-43024\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n>>>Do not allow users to make RDV requests during the install.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \nSite was getting a null subscript error when a site that did not have a\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\nstation number in the institution file (#4) made a RDV request to the site.\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can be queued for install at non-peak hours.\n TASKMAN can remain running.\n Do not allow users to make RDV requests during the install.\n \nThis was fixed by checking for the station number when the request is made\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*196'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\nto prevent sending a invalid request. At the remote site a second set of\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n\ncheck are made to see that all the needed parameters are in place before\nstarting to log the visit.\n \n\n
\nALX-0500-70393 XUTMRP, XUTMRP1\nto add more space and see that entries don't run off the side of the page. Added \nsome CPRS parameter info .Added a list of the Mailman info (Last use, mail \ngroups). Compiled print template XUCT01 will be rebuilt. The Person \nClass was also added to routine XQUSR.\nAdded a question to the Terminate User option to show the User Inquiry.\n(XUSTERM)\n\nMON-0800-50494, DUB-0900-31169, CML-0500-40711 XUTMQ\nThe future task list was not showing up. Corrected the global reference\nthat it was using.\nWhen the DEVICE name and $I were changed with tasks still queued to the\n\nXUTMK\nFrom a question from NVS, Fixed a problem that caused this routine not to \nclean-up Taskman monitor data in the %ZTSCH global.\n\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\nold DEVICE name, (XUTM REPNT) option could not find the old device name\n\n Checksum\nRoutine Old New 2nd Line\nXQUSR 5053391 4960998 **169**\nXUSER1 n/a 1428663 **169**\nXUSTERM 13933270 14433091 **36,73,135,148,169**\nXUTMK 7364498 8630418 **49,67,118,169**\nXUTMQ 8186969 8210432 **20,136,169**\nXUTMRP 15577050 13191393 **2,20,86,120,169**\nXUTMRP1 7184681 5994786 **2,86,120,169**\nand would cause an <UNDEFINED> error in XUTMRP1. Now, even if the DEVICE\nXUTMTP 10473436 10842367 **20,86,169**\n\nList of preceding patches: 118, 120, 136, 148\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n\nname was removed or changed, the option will still work\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can be queued and installed at any time.\n TASKMAN and Background tasks can remain running.\nE3R 14749 \n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*169'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\nThe "Person Class" and "Has E-SIG" and "Write Med's" were added to the print \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n\ntemplate [XUSERINQ] for this option "XUSERINQ". The KEYS HELD list was changed \n\n
\nNOIS: ISB-0201-31135\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;JUL 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nZTLOAD3 4046069 4541001 **67,127,136,192**\n\nIn the code for REQ^%ZTLOAD the new schedule time is put in the wrong\nList of preceding patches: 136\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nInstallation:\n \n>>>Users may remain on the system.\n>>>TaskMan does not need to be stopped.\n \n 1. DSM sites - Some of these routines are usually mapped,\npiece of the TASK. The code which puts the time in the task record was\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \nnot found at REQ^%ZTLOAD. The code at REQ^%ZTLOAD transfers control to\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch cannot be queued.\n **There is a slight chance that a job (User or TaskMan) could access\n this routine and get some CLOBER/NOSOURCE errors.\n%ZTLOAD3 which then contains the code being fixed. The 5th piece of\n If this isn't acceptable then see that all jobs on the system are\n stopped before installing this patch.\n \n 5. In Programmer mode:\n Use "D ^XPDKRN" then\n Install Package(s) 'XU*8.0*192'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO \n \n^%ZTSK(ztsk,0) was set when piece 6 should have been set. \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move the following routine from \n your production account to each manager account:\n \n ZTLOAD3\nAlso the original create $H is moved to a new field (#16) and the $H\n \n 7. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 192\n ===\n \n 8. DSM Sites, after patch has installed, rebuild your map set.\n \nat the time of requeueing is set into the 5th piece. \n=========================================================================\n\nThis patch fixes this problem.\n\n
\nThis patch is being released by Capacity Management (CM) for installation\nThis patch removes the MSM versions of the collection routines (ZOSVKSME\nand ZOSVKSMS) from the production environment.\n \nProvided that the 'SAGG Master Background Task' [KMPS SAGG REPORT] is not\ncurrently running, this installation can be performed at any time of the\nday with minimal disruption to users. Installation should not take longer\nthan 10-15 minutes.\n \nInstallation:\n============\nof modifications to the ^%ZOSVK* collection routines that are used by the\n \n 1. You will need to disable any routines within the %ZOSVK* namespace.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\nStatistical Analysis of Global Growth (SAGG) Version 1.8 software package.\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. You do not need to inhibit users from login into the system.\n \n 5. Ensure that the 'SAGG Master Background Task' [KMPS SAGG REPORT] is\n not currently running by using the 'Status of SAGG Collection\n \n Routines' [KMPS SAGG STATUS] option and verifying the following\n message is displayed:\n \n The temporary collection global (i.e., ^XTMP("KMPS")) has no data.\n \n 6. On the KIDS menu, under the 'Installation' menu, use the 'Install\n Package(s)' option and select the package \n \n XU*8.0*197\n ========== \nAll DSM and OpenM-NT (Cache) sites are instructed to install this patch.\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', you can respond with NO.\n \n 8. OpenM-NT (Cache) sites - you do not need to move any routines, skip\n this step.\n \n DSM sites - you need to move several routines from your production\n account to manager account. \n \n \n ZOSVKSD\n ZOSVKSOE\n ZOSVKSOS\n ZOSVKSVE\n ZOSVKSVS\n \n 9. OpenM-NT (Cache) sites remain in VAH.\n \n DSM sites remain in the manager account.\n \nThis patch makes modifications to the ^%ZOSVK* collection routines that\n All sites:\n \n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 197\n ===\n \n 10. After patch has installed, rebuild your map set if necessary.\nare used by the SAGG software package.\n \n\n\nThis patch creates two new components that add the following functionality to \n package to which the KIDS build belongs. The package-level parameters \n contained in the PARAMETERS file (#8989.5) are used as default values in \n cases where the site hasn't set up or modified the parameter.\n \n c. Export the entries in PARAMETER ENTITY (#8989.518) file.\n \n d. Synchronize/resolve any issues with "pointed to" files and entries.\n \n e. The incoming data replaces any data at the site.\n \nKIDS:\n \n 2. A KIDS Build component that allows users to export entries from the \n PARAMETER TEMPLATE File (#8989.52).\n a. Export the Parameter Template for each entry.\n \n b. Export each Parameter Definition (#8989.51) that is pointed to,\n without the PARAMETERS file (#8989.5) entry.\n \n \nRoutine Summary\n \nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n \n Checksum\nRoutine Old New 2nd Line\nXPDE 15289814 15641945 **2,15,21,44,51,68,131,182,201**\nXPDIA3 n/a 3070143 **201**\nXPDTA2 n/a 2361795 **201**\n \n 1. A KIDS Build component that allows users to export entries from the \nList of preceding patches: 182\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nInstallation:\n \n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n \n 1. DSM sites - Some of these routines are usually mapped,\n PARAMETER DEFINITION File (#8989.51).\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n a. Export the Parameter Definition for each entry.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can be queued and installed at any time.\n TASKMAN can remain running.\n \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*201'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n b. Export the entries in the PARAMETERS file (#8989.5) that pointed to \n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n the exported Parameter Definition (Step A) and had as the entity the \n\n
\nThis patch adds some capabilities within the routine XUSRB related to\nThe patch contains only a single routine.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of \neach of these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n \n Checksum\nRoutine Old New 2nd Line\nXUSRB 6227685 8143764 **11,16,28,32,59,70,82,109,115,165,150,180,213**\nEnterprise Single Sign-on (ESSO). \n \nList of preceding patches: 36, 102, 149, 150, 180\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \n========================================================================= \nInstallation: \n \n>>>Users may remain on the system. \n>>>Taskman does not need to be stopped. \n \n \n 1. DSM sites - Some of the routine is usually mapped, \n so you will need to disable mapping for the routine. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \nOne change will enable the RPCBroker to determine proxy servers which \n options: \n \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n 4. Users can remain on the system if installed at non-peak hours.\n There is a small chance that a user could get a CLOBER error if they\n are signing on at the time the routines change. \ncan be used for an ESSO sign-on. \n This patch can be queued and installed at non-peak time. \n TASKMAN can remain running. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following \n option: \n Install Package(s) 'XU*8.0*213' \n ==========\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO \n \n No Options or Protocols need to be placed out-of-order. \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO \n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set. \nAnother change is specific to the CAPRI program of VBA to permit an \nESSO-like sign-on using methods used in remote data views.\n \n\n
\nSee patch XU*8*214 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n This patch contains the following features:\n-KIDS will now send an Alert if an Install encounters an error.\n==============================================================================\n\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no user should be using KIDS during the install of this patch.\nSince this patch is an update to KIDS, this patch should not be installed\nwith any other patch.\n\n**MSM sites must manually move the routines XPDIJ and XPDCPU to their other\n CPUs. KIDS cannot automatically move this routines for you.**\n\n==============================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n-Fixes problems when installing PCE 1.0; \n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. MSM Sites - D ^%RCOPY to move the routine XPDIJ and XPDCPU to your\n other CPUs.\n When Options and Protocols are disabled and the Install is restarted, those\n 7. AXP Sites, after patch has installed, rebuild your map set.\n ===========================================================================\n \n ROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Name Checksum Patch List\n -----------------------------------------------------------\n XPDCPU 6456291 41\n Protocols remain disabled even when install finishes. Nois MAR-0896-20332\n XPDET 4654700 15,39,41\n XPDI 15955866 10,21,39,41\n XPDIGP 6735250 41\n XPDIJ 10666490 2,21,28,41\n XPDIJ1 8772642 41\n XPDIL1 6509127 15,17,39,41\n XPDIP 9642216 15,21,28,30,41\n XPDIU 6010331 15,41\n XPDT 17390342 2,10,28,41\n XPDTC 12638033 10,15,21,39,41\n Protocols are installed without pointer to the Package file.\n XQOO1 14519526 10,21,39,41\n ============================================================================\n All routines were not being installed on all CPUs.\n-Fixes bad expression error in DIK1 when loading patch GMRA*4*2 or DVBA*2.7*11\n Nois POR-0896-50403\n\n
\n\nPatch Solution\n==============\n\nThis patch introduces a new Kernel option XUSER DIV CHG, menu text: Change my \nDivision. It has been added to the TBOX on the COMMON Menu.\n\nHere is the Option description:\n\n The Kernel option "Change my Division" allows you to change the\n division to which you are currently assigned. This option performs\nPatch XU*8*210, R/S Change Division\n the same function as entering your current division at the signon\n prompt "Select DIVISION: default division //".\n \n If you only have one division to select from, XUSER DIV CHG will show you \n your current division and indicate that you cannot change it.\n \n================\nThe following NOIS calls are also corrected:\nHIN-0801-41754, FRE-0801-64066, BAC-0701-41456\n\n===================================\nThe problem:\nIn the User Inquiry option, the CPRS Parameter Info is for the wrong\nperson. It has been fixed to report for the correct person.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\n\nRoutine Old New 2nd Line\nXUSER1 1428663 3013639 **169,210**\n\nList of preceding patches: 169\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\nProblem Statement\n>>>Taskman does not need to be stopped.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n=================\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\n This patch can be queued for install at non-peak hours.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*210'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\nPatch XU*8*210 addresses the need for users at multi-divisional or consolidated sites to change the division they represent without having to sign out and then sign back onto the system. \n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n\n\n\n
\nPatch XU*8.0*208, Strong Verify clean-up\n5. MIN-0701-40152\n 4. Users can remain on the system.\n This patch can be queued for install at non-peak hours.\n\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*208'\n ==========\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n6. DEN-0701-50838\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n 6. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\n\n\n\nPatch XU*8.0*208 is composed of the following two parts. Each part is described\nin the form of a Problem Statement and Patch Solution as follows.\n\nNOTE: All fields added or modified by this patch (XU*8.0*208) and referenced in\nthis patch description reside in the NEW PERSON file (#200).\n\n\nPart 1 - Problem Statement:\n---------------------------\n\nPatch XU*8*180 introduced a feature whereby the DISUSER flag (#7) was set for\nany user that had not signed onto the system in the last 90 days. This caused\nthe problem that if the DISUSER flag was cleared and the user did not sign onto\nthe system before the next scheduled time for the XUAUTODEACTIVATE option to\nrun, the DISUSER flag was being set again, causing extra work for IRM. The same\nproblem occurred when a user that was reactivated did not sign onto the system\nbefore the XUAUTODEACTIVATE option ran.\nThis Patch Addresses the Following NOIS Calls:\n\nPart 1 - Patch Solution:\n------------------------\n\nTo fix this problem, a new field ENTRY LAST EDIT DATE (#202.04) was added to\nthe NEW PERSON file (#200) to keep track of the date of some edits. The\nfollowing fields now trigger the current date to the ENTRY LAST EDIT DATE\nfield: DISUSER, ACCESS CODE (#2), and TERMINATION DATE (#9.2).\n\nThe conditions under which the DISUSER field is set have also been changed. If\n==============================================\nany of the following conditions are true, we don't set the DISUSER flag:\n\n ;Last sign-on within 90 days\n ;User edited in last 30 days\n ;User set up in last 30 days\n ;Verify code changed in last 30 days\n\nThe TERMINATION DATE and DISUSER fields were moved to the first page of the\nEdit an Existing User ScreenMan form to make them easier to see.\n\n\n\nPart 2 - Problem Statement:\n---------------------------\n\nA problem was identified in that not all sign-on code (i.e. XUP, WebMail, POP3\nserver) was setting the LAST SIGN-ON DATE field (#202).\n\nPart 2 - Patch Solution:\n------------------------\n\n1. DAY-0501-41059\nThe known places where this was happening have been fixed. Specifically they\nwere: XUP and XUSRA that POP3. WEBMAIL has been patched on FORUM.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\n2. FOR-0701-20582\nXUP 4867034 5102490 **208**\nXUSERNEW 7347033 7464165 **16,49,134,208**\nXUSRA 1579938 1722541 **70,115,208**\nXUSTERM1 11515045 12346209 **102,180,208**\n\nList of preceding patches: 115, 134, 180\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n=========================================================================\nInstallation:\n3. CLE-0601-42777\n\n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n4. MEM-0701-70137\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n\n
\nPatch XU*8*199: IOPAR Corrupting Tasks\n==============\n =========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step. \n \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n \nZIS\nZIS1\nZISC\nZISUTL\nZTMS2\n \n 9. And in the manager account, (OpenM sites remain in VAH)\nThe Text Integration Utility (TIU) has been encountering run away jobs at some \n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 199\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n 11. Enable user's login.\n Remove TASKMAN from the wait state. (DO RUN^ZTMKU)\n \nsites due to the IO variable IOPAR being left behind by an earlier task. After \n \n=========================================================================\na lot of work by the sites, National Vista Support (NVS), and TIU developers, \nthe following pattern has been identified: Because the IOPAR variable is left\nbehind by an earlier task, it overrides the normal Open parameter in the DEVICE \nfile (#3.5) if either conditions exist:\n \n * When TIU (or any routine making a call %ZTLOAD) queues to a Host File \n================================\n System (HFS) device, they could experience this problem depending on what \n devices had been used before.\n \n * If TaskMan opens the device for a task which cannot be opened,\n TaskMan reschedules the task incorrectly using that same IOPAR variable, \n which is still in the symbol table.\n \n \nPatch Solution:\n===========\n \n \nSeveral places in the code have been fixed to ensure that extra IO variables \nare not left behind after tasks have finished processing. This patch corrects \nthe problem that the TIU has come across by changing the routine %ZTMS2 to kill \nthe IOPAR variable before setting up the task. The %ZTMS2 routine now kills all \nIO variables before setting up a call to open a device. In addition, any \nspecial IO variables for that device are killed when the routine %ZISC is \ncalled to closed the device. \n \nThis patch also introduces a new extrinsic function UNIQUE^ZISUTL, which \nPer the patch description below, this patch was intended to correct a problem \ncreates a unique IO parameter. This parameter takes the string $H_"-"_$J and \nruns a CRC32 on it to get a 10 digit number. If UNIQUE^ZISUTL is called using \na parameter, it will concatenate the number just before the last period (.) in \nthe parameter string. Here are some examples on this:\n \n W $$UNIQUE() >>2987896688\n W $$UNIQUE("last") >>last_9041564\n W $$UNIQUE("$USR:[USER.FORT.EDIT]TEST.TMP")\n >>$USR:[USER.FORT.EDIT]TEST_2603399923.TMP\n \nidentified in NOIS reports NOIS: NAS-0700-31644, CHA-0700-32007, \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;JUL 10, 1995\n \n Checksum\nRoutine Old New 2nd Line\nZIS 9454725 9332342 **18,23,69,112,199**\nZIS1 10540675 9968286 **18,49,69,104,112,199**\nZISC 8004258 8130420 **24,36,49,69,199**\nMIW-0201-40662, DAY-0401-41059, and BRX-0501-10502.\nZISUTL 2307058 2825748 **18,24,34,69,118,127,199**\nZTMS2 7001305 7090453 **2,18,23,36,67,118,127,163,167,175,199**\n \nList of preceding patches: 112, 175\nSites should use CHECK^XTSUMBLD to verify checksums.\n========================================================================= \nInstallation:\n \n>>>Do not allow users to log in to the system during installation.\n>>>Users may remain on the system. They may get EDITED error if they\n \n are selecting a device at the time.\n>>>Taskman does need to be in a wait state.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n \n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users could remain on the system. They may get a EDITED error if they\nProblem Statement:\n are selecting a device at the time.\n This patch can not be queued.\n Also place TASKMAN in a wait state. (DO WAIT^ZTMKU)\n Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors is\n acceptable, then users can stay on the system.)\n \n 5. In Programmer mode:\n Use "D ^XPDKRN" then\n Install Package(s) 'XU*8.0*199'\n\n\nThis patch enhances the Master File Server\nmessage handler and the IFR clean up code\nto compensate for HL7 package problems.\n\n
\nPatch XU*8.0*216\nrelease of Patch XU*8*199, a new problem was discovered in the use and \nsetting of the IOCPU variable. Unfortunately, this underlying problem was \nnot discovered during the testing phase. To cause the problem you had to \nuse OPEN^%ZISH to open the host file and use ^%ZISC to close it, then \nwithout calling ^%ZIS use OPEN^%ZISH again to open a host file when you \ncall ^%ZISC the file would not get closed. Patch XU*8*216 corrects this \nproblem. If sites installed any local modifications to correct this \nproblem, based on advice provided by NVS in NOIS, please remove them prior \nto or immediately after the installation of this patch. We regret the \nerror and any inconvenience this has caused. \n\n\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;JUL 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nZISC 8130420 8069178 **24,36,49,69,199,216**\nNOIS: ALT-1101-22356, DAY-1101-41446, BAY-1101-32090, WAS-1101-22142,\n\nList of preceding patches: 199\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n=========================================================================\nInstallation:\n\n>>>If you accept a slight risk of jobs getting a CLOBBER/EDITED error\n>>>users and TaskMan may remain running. Otherwise stop all other\n>>>jobs on the system.\n DAY-1101-42557, LAS-1101-62483, MAC-1101-62500, NOL-1201-70575\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors is\n acceptable, then users and TaskMan can stay on the system.)\nTest Sites: Dayton, OH; White River Junction Vt;\n Also place TASKMAN in a wait state. (DO WAIT^ZTMKU)\n \n\n 5. In Programmer mode:\n Use "D ^XPDKRN" then\n Install Package(s) 'XU*8.0*216'\n ==========\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n So. Nevada Healthcare System\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n 8. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step.\n DSM/MSM sites - you need to move several routines from\n your production account to each manager account:\n\nZISC\n\n\n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 216\n ===\n\n 10. DSM Sites, after patch has installed, rebuild your map set.\n\nPatch XU*8*199, IOPAR Corrupting Tasks, was released on 11/21/01. After the \n 11. Enable user's login.\n Remove TASKMAN from the wait state. (DO RUN^ZTMKU)\n\n=========================================================================\n\n\n
\nThis patch adds some new fields to the TERMINAL TYPE file (#3.2) in support of \n \nField # Name\n \n .001 NUMBER\n .01 CTRL CODE ABBREVIATION\n 1 FULL NAME\n 2 CONTROL CODE \n \nNOIS: PUG-0101-51613\nAdds the 'Alternate Syntax for Device Specification' to the Device\nBar Code Medication Administration (BCMA) and barcode printers.\nHandler help.\nAdds a new HELP FRAME 'XUDOC DEVICE ALT SYNTAX' and updates %ZIS7 to\nto use the new HELP FRAME. \n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;JUL 10, 1995\n \n Checksum\n \nRoutine Old New 2nd Line\nZIS7 3002967 2928520 **205**\n \nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nInstallation:\n \n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\nThe new field, CONTROL CODES (#55), is a multiple of control codes. The \n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\napplications that use this field will have to describe to the sites how to \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 3. Users can remain on the system. \n TASKMAN can remain running.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*205'\npopulate it. Before any new abbreviations are added to this file see that they \n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n 5. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move one routine from \nhave been added to Integration Agrement #3435 first. The CONTROL CODE field \n your production account to each manager account:\n \nZIS7\n \n 6. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 205\n ===\ncontains MUMPS code.\n \n 7. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n \n \n\n
\nPatch XU*8*215\n^%LICENSE have, in some cases, been resulting in errors which changed \nthe way other errors get handled. This has been resolved by seeing that \n$ECODE variable is cleared after the call.\n \n3. Correctly add together the enterprise and division licenses in the \n$$AVJ^%ZOSV call. $$AVJ is used by Kernel to check how many available jobs \nare on the system. Only a few sites have division licenses. Most have \nenterprise licenses.\n \nRoutine Summary\n \nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n \n Checksum\nRoutine Old New 2nd Line\nZOSVONT 5179130 5640784 **34,94,107,118,136,215**\nZOSVVXD 7443216 7675098 **13,65,71,94,107,118,136,215**\n \nList of preceding patches: 136\nThis patch introduces the following three enhancements.\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n=========================================================================\nInstallation:\n \n>>>Users may remain on the system.\n>>>Taskman does not need to be stopped.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n1. A new function named GETPEER has been created to get the IP address of \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can not be queued.\n TASKMAN can remain running.\n \n 5. In Programmer mode:\nthe caller to the TCP service. It has been designed to specifically work \n Use "D ^XPDKRN" then\n Install Package(s) 'XU*8.0*215'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \nwith a device connected as a TCP/IP listener in support of RPCBroker.\n 8. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step.\n DSM/MSM sites - you need to move several routines from\n your production account to each manager account:\n \nZOSVONT\nZOSVVXD\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n \n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 215\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n \n2. In SHARELIC^%ZOSV, the call made to the Cache operating system utility \n\n
\nPERSON CLASS file patch.\n \nNOTE: The file PERSON CLASS is in global ^USC. This will be a NEW global\nfor most sites. Please be sure to place this global and add it to your\ntranslation tables. This is a static file.\n\nThe patch also:\nAdds a PERSON CLASS field to the NEW PERSON file. This multiple includes\nthe following fields: NUMBER (.001), PERSON CLASS (.01), EFFECTIVE DATE\n(2), EXPIRATION DATE (3).\n \nUser documentation for this patch in PDF (Portable Document Format) is\nAdds the PERSON CLASS field to the following options: Edit an Existing\nUser, Add a New User to the System, and Reactivate a User.\n \nAdds three new menu options:\n \nPERSON CLASS EDIT ,(XU-PERSON CLASS EDIT), to the User Management menu.\nThis option only allows entry of PERSON CLASS data.\n \nUser PC Build Print, (XUSER PC BUILD) to print the entries of the\nindividuals in the NEW PERSON file who hold the Provider key AND have a\navailable on the Infrastructure Home Page at\nVerify Code. It prints these fields: NAME, PROVIDER CLASS (free text),\nand PROVIDER TYPE (set of codes). The last two fields may contain data\nonly at sites that have implemented Decision Support System (DSS). This\noption is not attached to a menu but may be added to the secondary menu of\nany user who will be working on this project.\n \nUser PC Build Edit, (XUSER PC BUILD EDIT), a straight DIE option to allow\nfast entry of PERSON CLASS data. This option is not attached to a menu\nbut may be added to the secondary menu of a user who will be performing\ndata entry.\nhttp://www.vista.domain.ext/softserv/infrastr.uct/ under New\n \n \n routine new checksum\n XUA4A72 1853480\n =========================================================================\n \n Installation:\n \n 1. This is a new routine and will not be mapped on any systems.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nPerson file. The PDF documentation may also be retrieved from the\n This option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Users can remain on the system.\nanonymous directories at Hines, Albany, and Salt Lake City with the \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*27'\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\n \n =========================================================================\n SUPPORTED REFERENCE.\n \nfilename of 'XU_8_27.pdf'. \n $$GET^XUA4A72(duz[, date])\n \n Returns the 'IEN^Profession^Specialty^Sub-specialty^Effect date\n ^Expired date^VA code' for the person identified by the DUZ in effect\n on the date passed in (TODAY if no date passed in). The date is in\n internal format.\n \n Returns -1 if DUZ doesn't point to a valid user or user has never had a\n Person Class assigned. Returns -2 if no active Person Class on that\n date. \n\n \n $$IEN2CODE^XUA4A72(ien)\n \n Returns the VA CODE from the Person Class file that corresponds to \n the IEN number passed in. If the IEN isn't valid it returns the empty\n string.\n \n=========================================================================\n\nThis patch adds a new file PERSON CLASS (8932.1) with data. \n\n
\nSee patch XU*8*211 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING **\n--------------------------- End of Warning -------------------------\n XQALERT1 30893715 30919356 **20,65,114,123,125,164,173**\n XQALSET 14823261 15152866 **1,6,65,75,114,125,173**\n XQALSURO 7933100 12681484 **114,125,173**\n XQAL173P N/A 304597 **173**\n \nList of preceding patches: 125,164\n \n \nBlood Bank Team Coordination:\n=============================\n \nClearance - 04/05/2002\n \n \nInstallation Instructions:\n \n 1. Users ARE allowed to be on the system during the\n installation but if you have not recently run a scheduled purge of\n old alerts you may want to schedule the installation for off hours.\n \n 2. DSM sites - Some of these routines are usually mapped,\n1. Surrogates for processing alerts may have an end date and time for the\n so you will need to disable mapping for the affected routines.\n \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS (Kernel Installation and Distribution\n System) package onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. The patch has now been loaded into a transport global on your\n system. On the KIDS menu, select the 'Installation' menu and use\nsurrogate relationship. The actual removal of the surrogate has been\n the following options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Return to Programmers Prompt and use "D ^XPDKRN":\n Select KIDS OPTION: Install\n =======\n Install Package(s)\n Select INSTALL NAME: XU*8.0*173\nperformed when the next alert was sent to an individual. This resulted,\n ==========\n \n Checking Install for Package XU*8.0*173\n \n Install Questions for XU*8.0*173\n \n Incoming Files:\n \n \n 8992 ALERT (Partial Definition)\nhowever, in the user still appearing to have a surrogate after the\n Note: You already have the 'ALERT' File.\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? \nYES// NO\n ==\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and \nProtocols? YES// NO\n ==\nstated end time if another user tried to set them as their surrogate.\n \n 6. AXP Sites - Answer 'NO' to the question 'Want to MOVE\n routines to other CPUs?'.\n \n 7. If the routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\nThis patch modifies the processing so that the removal of the specified\nsurrogate happens on any surrogate related look-up after the specified end\ntime. This will correct the problem that had been reported (E3R #14940).\n \n \n2. Code has been modified to correct problems identified with setting\nsurrogates (BRX-1000-10427, COS-0401-41366, WRJ-1201-11337).\n \n3. The problem indicated as a mismatch in XQAID values (ISL-0200-52883) is\nhandled by a re-indexing of the "B" cross-reference in FILE: ALERT\nTRACKING (#8992.1) in the post-installation routine.\n \n4. A small change was made in XQALERT to clarify the way in which alerts\nare referenced from the menu system (ISL-0898-51279) and to correct a\nIf your site does not purge old alerts the post install routine,\npotential problem with matching the "B" cross-reference in FILE: ALERT\nTRACKING (#8992.1).\n \n5. A cross-reference was added to FIELD: SURROGATE (#.02) of FILE: ALERT\n(#8992) to permit rapid lookup of users who have specified a selected user\nas their surrogate (E3R #15158). This is made available via the "XQAL\nSURROGATE FOR WHICH USERS" (View Surrogate for Which Users) option on the\nXQALERT MGR menu. The supported reference API SUROFOR^XQALSURO has been\nadded for other applications to access this data.\n \nwhich reindexes the "B" cross-reference of the FILE: ALERT TRACKING\n D SUROFOR^XQALSURO(.LIST,USERDUZ)\n \nwill return data in the variable LIST. The value of LIST indicates the\nnumber of entries returned. The array list will return the users DUZ\nvalue in file 200 and the NAME (.01) field from file 200 separated by an\n'^'.\n LIST = 3\n LIST(1) = "54^LNAME1,FNAME1"\n LIST(2) = "75^LNAME2,FNAME2"\n LIST(3) = "247^LNAME3,FNAME3"\n(# 8992.1), may take considerably longer than would be the case if you\n \nThe post-install routine, XQAL173P, also builds the cross-reference for\ncurrent surrogates. This routine is set to be removed following the\ninstallation.\n \n6. In addition, it was noted that while interactive specification of a\nsurrogate checked for cyclic relationships among surrogates, the API for\nnon-interactive setting of a surrogated (SETSURO^XQALSURO) simply set the\nspecified surrogate. While this API can continue to be used, a new API\n(SETSURO1^XQALSURO) has been created which should be used to obtain a\nregularly purge. In that case, you will want to schedule the\nreturn value (1 if successful, 0 if not successful) indicating whether the\nsurrogate could be set.\n \n S VAL=$$SETSURO1^XQALSURO(USERDUZ,SURODUZ,STRTDATE,ENDDATE)\n \n \nWhere USERDUZ and SURODUZ are the internal entry numbers in file 200 for\nthe user and selected surrogate, respectively. STRTDATE and ENDDATE are\noptional date/time values for when the surrogate relationship should\nstart and end. If STRTDATE is not specified, the surrogate becomes active\ninstallation so the post installation routine may run on a weekend or\nimmediately. If ENDDATE is not specified, the surrogate remains active\nuntil another surrogate is specified or the surrogate is removed.\n \n \nList of Test Sites\n==================\nBATTLE CREEK, MI \nCHARLESTON, SC \nCHICAGO HCS \nLEXINGTON, KY \novernight.\nNORTHERN CALIFORNIA HCS \nSAN FRANCISCO, CA \nSPOKANE, WA \nWEST PALM BEACH, FL \n \n \nRoutine Summary:\n================\nThe following routines are included in this patch. The second\nline of each of these routines now looks like:\n \n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \nChecksums:\n==========\nChecksums obtained using CHECK^XTSUMBLD\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XQALERT 5402974 5560549 **1,65,125,173**\n\n
\nFor the patch description see the patch message or the patch module on\nForum.\n\n
\nAssociated patches: (v)SD*5.3*262 install with patch `XU*8*234'\n be performed on the key(s) for that user. If this argument is not\n specified, it will perform the test for the current user, as it has \n done in the past.\n \n Generated for Mental Health Assistant GUI, patch YS*5.01*71 at the \n request of the Database Administrator.\n \n NOISs V01-1201-N0503\n E3Rs none\n \n (v)DG*5.3*447 install with patch `XU*8*234'\n List of Test Sites\n North Texas Health Care System\nSalt Lake\n \n \n Routine Summary:\n ================\n The following routines are included in this patch. The second\n line of each of these routines now looks like:\n \n (v)YS*5.01*71 install with patch `XU*8*234'\n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Checksums:\n ==========\n Checksums obtained using CHECK^XTSUMBLD\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XUSRB 8143764 8323600 **11,16,28,32,59,70,82\n 109,115,165,150,180\n \n 213,234**\n List of preceding patches: 213\n \n \n Blood Bank Team Coordination:\n =============================\n Clearance - 4-26-2002\n This patch has been reviewed and cleared. The changes to the XUS KEY \n CHECK RPC have no effect on Blood Bank functionality.\n \n 1. This patch provides a change in the "XUS KEY CHECK" RPC necessary\n Software and Documentation Retrieval:\n =====================================\n \n The software for this patch is not being distributed through the\n National Patch Module. This patch along with patches DG*5.3*447\n and SD*5.3*262 \n are being released in a single KIDS software distribution with Patch \n YS*5.01*71. This patch only includes the informational portion of\n XU*8.0*234.\n \n for other applications to use the RPC to full advantage. Whereas\n Please refer to the 'Software and Documentation Retrieval' and \n 'Installation Instructions' sections of the YS*5.01*71 patch\n description for the instructions on how to acquire, install, and \n implement the patch software.\n the RPC would originally return an indicator of whether the current\n user owned the key or keys, this adds an additional argument which\n can be used to specify another user's DUZ value, and the check will\n\n
\nSee patch XU*8*230 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nNOIS: SLC-0202-52313\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXLFMSMT 6989075 6910116 **228**\n\nSites should use CHECK^XTSUMBLD to verify checksums.\nProblem: The Body Surface Area calculation in XLFMSMT returned the wrong\n\n=========================================================================\nInstallation:\n\n>>>Users may remain on the system.\n>>>TaskMan does *not* need to be stopped.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n\nvalues. A check of the Web for BSA showed that the formula had been\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\nentered switching the powers.\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can be queued for install at non-peak hours.\n TaskMan can remain running.\n\n 5. Installation will take less than 2 minutes.\n On the KIDS menu, under the 'Installation' menu, use the following\nFix: Enter the formula correctly. Sample value BSA(100,43) = 1.00\n option:\n Install Package(s) 'XU*8.0*228'\n ==========\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n 6. DSM Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\nTest Site: Salt Lake City\nBloodBank: 4/12/2002\n\n\n
\n*** Patch for MSM sites ***\nto the Cookbook to come out with recommendations on settings. If unsure\nwhat value to use leave the TASK PARTITION SIZE field blank and your\ncurrent sysgen value will be used.\n \n \nroutine new checksum\nZTM0 5451877\nZUMSM 2237614\n========================================================================= \nInstallation:\n \n \n 1. This patch is only for MSM sites.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\nThis patch changes ZU (for MSM) to look in the TASKMAN SITE PARAMETERS\n Install Package(s)\n 4. Stop TASKMAN.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Install Package(s) 'XU*8.0*42'\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. After installing this patch, you need to one routine from \n your productions account to the manager account:\n ZTM0\nfile for the TASK PARTITION SIZE field. If this field has data then a\n and in the manager account rename\n ZTM0 to %ZTM0\n \n Example: ZL ZTM0 ZS %ZTM0\n \n 8. Restart TASKMAN.\n \n ===========================================================================\ncall is made to the MSM utility %PARTSIZ to change the jobs partition\nsize limit. TASKMAN will also use this value in its job command when\nstarting a new submanager. This will allow sites to reduce the default\npartition size in SYSGEN, increasing the number of disk buffers.\nThis will allow sites to adjust partition site for running PCE. Look\n\n
\nXU*8*156\nMenu Rebuild Rewrite - Part 1\nRefer to patch XU*8*156 in the FORUM Patch Module for a complete\ndescription.\n\n
\nXU*8*157\nMenu Rebuild Rewrite - Part 2\nRefer to patch XU*8*157 in the FORUM Patch Module for a complete\ndescription.\n\n
\nTest Site: ANCHORAGE\nNOIS: LOU-0601-40314, LEX-0401-42341, COA-0401-21786, HVH-0101-11346\n\nProblem: TCP clients on Cache were opened in 'mumps' mode, this caused some \nproblems when talking with DSM systems. This caused problems with HL7.\nFix: This patch changes the way that TCP devices are opened on Cache \nsystems to be in packet mode. This makes it behave more like the way that \nDSM does.\n\nNOIS: HVH-0101-11346, COA-0401-21786, LEX-0401-42341, LOU-0601-40314\nProblem: ZISTCPS would halt when told to stop. When called from a job \nstarted by Taskman the task would not be cleaned up. This caused problems \nBlood Bank Clearence: 4/12/2002\nwith HL7.\nFix: To have ZISTCPS just QUIT when told to stop.\n\nProblem: VMS and DSM utilities require the job number in hex, but Taskman \nlisting would just show the job number in decimal.\nFix: In a task listing of running tasks, include the job number in hex when \nthe job numbers is greater that 2048.\n\n\nRoutine Summary\n\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXUTMTP1 5115647 5550117 **20,225**\nZISTCP 2703750 3208452 **36,34,59,69,118,225**\nZISTCPS 1115181 1281564 **78,118,127,225**\nZUONT 2038331 2065413 **34,94,118,162,170,225**\nProblem: The call to Intersystems' license share should only be called for \nZUSET 1042105 1042105 **162,170,225**\nZUVXD 4620305 4178529 **13,24,84,94,118,162,225**\n\nList of preceding patches: 20, 127, 170\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n=========================================================================\nInstallation:\n>>>Users may remain on the system.\n>>>TaskMan does not need to be stopped.\nTelnet and TCP connections. Not for LAT.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\nFix: This patch changes ZU to check the type of device and only call the \n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can not be queued.\nIntersystems License share code for Telnet connections, this is done \n TaskMan can remain running.\n\n 5. In Programmer mode:\n Install Package(s) 'XU*8.0*225'\n ==========\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\nfor both DSM and Cache. \n ==\n\n 6. After installing this patch,\n Cache Sites - you don't need to move anything, skip this step.\n DSM/MSM sites - you need to move several routines from\n your production account to each manager account:\n\nZISTCP\nZISTCPS\n\n\n 7. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 225\n ===\n\n 8. DSM Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nSee patch XU*8*147 in the National Patch Module for complete information\non this patch.\n\n
\nAlerts are used to send time sensitive notifications for information or\nonly be forwarded once.\n ==\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO\n ==\n \n 6. AXP Sites - Answer 'NO' to the question 'Want to MOVE\n routines to other CPUs?'.\n \n \n 7. If the routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\nIn addition, there have been some who wanted these unread alerts forwarded\nto a specific individual, e.g., someone in QA, who would monitor unread\nalerts and could insure forwarding to proper individuals if they could not\nprocess them fully (ASH-0100-31970). To assist in this capability, the\ncurrent patch also adds a 'DAYS FOR BACKUP REVIEWER' (#.15) field to the\n'ALERT DATE/TIME(#1)' subfile of the 'ALERT(#8992)' file. In addition, it\nadds an 'XQAL BACKUP REVIEWER' entry in the PARAMETER DEFINITION \n(#8989.51) file, and an option, Set Backup Reviewer for Alerts [XQAL SET\nfor further processing. When created, some alerts may specify a number of\nBACKUP REVIEWER] on the Alert Management [XQALERT MGR] menu.\n \n \nIf an alert is generated with a number of days specified in the variable\nXQAREVUE, after the specified number of days has passed if the alert\nremains unread, and if a valid entry is present in the ALERT BACKUP\nREVIEWER parameter for the User, Service, Division, or System \nentities, \nthe alert will be forwarded to the indicated individual at the lowest\nlevel found for processing.\ndays for forwarding to a supervisor or to e-mail surrogates. If the alert\n \nNOISs (SHR-0100-70069; SHR-1099-70923; ASH-0100-31970)\nE3Rs (13228, 13229)\n \nList of Test Sites\n==================\nBATTLE CREEK, MI \nCHARLESTON, SC \nDUBLIN, GA \nNORTHERN CALIFORNIA HCS \nremains unread after this period of time the alert is forwarded, if\nOIFO-SAN FRANCISCO \nPUGET SOUND HCS \nSAN FRANCISCO, CA \nSHREVEPORT, LA \n \n \nRoutine Summary:\n================\nThe following routines are included in this patch. The second\nline of each of these routines now looks like:\npossible, to a supervisor or e-mail surrogate as indicated. A problem has\n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \nChecksums:\n==========\nChecksums obtained using CHECK^XTSUMBLD\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XQALDEL 14175555 26334655 **6,24,65,114,174**\nbeen reported when after the alert has been forwarded to the backup\n \nList of preceding patches: 114\n \n \nBlood Bank Team Coordination:\n=============================\nClearance - 4/5/2002\n \n \nInstallation Instructions:\nindividual, it is repeatedly reforwarded on following days until the alert\n \n 1. Users ARE allowed to be on the system during the\n installation.\n \n 2. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS (Kernel Installation and Distribution\n System) package onto your system.\nis removed either manually or as a result of normal alert removal\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. The patch has now been loaded into a transport global on your\n system. On the KIDS menu, select the 'Installation' menu and use\n the following options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n(SHR-0100-70069). This patch corrects this behavior, so the alert will\n \n Return to Programmers Prompt and use "D ^XPDKRN":\n Select KIDS OPTION: Install\n =======\n Install Package(s)\n Select INSTALL NAME: XU*8.0*174\n ==========\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//\n NO \n\n
\n This Kernel patch contains the following features:\n-A new field, PRE-TRANSPORTATION ROUTINE (#900), is in the BUILD file.\n developer can retrieve the data by using the same variable, XPDGREF. Since\n these nodes are part of the transport global, they will be removed when the\n install is completed.\n\n KIDS didn't turn off Alpha/Beta testing when the final version of a package\n was released. Because of this bug, Kernel 8.0 and Radiology 4.5 still have\n Alpha/Beta testing turned on. You can run the routine XQABTMP to turn off\n testing for those packages.\n\n A new function is available to developers, $$PATCH^XPDUTL(patch) will return\n-Updates to routines and data dictionary to support the new security features\n 1 if patch was loaded on current system and 0 if it wasn't loaded. This\n function can be used in your Environment Check routine.\n i.e. I '$$PATCH^XPDUTL("XU*8.0*28") W !,"You must install patch XU*8.0*28"\n\n of the RPC Broker. This patch is a prerequisite to installing the released\n version 1.0 of the RPC Broker. RPC Broker version 1.0 is scheduled to be\n released at the end of May, 1996, and will need to be installed to support\n the PCMM with a graphical interface.\n\n Please note: The sign-on project that was distributed with the RPC Broker\n Developer Preview Kit (version 1T11) will not function after\n this patch is installed. The Preview Kit served the function\n\n of illustrating possible DHCP directions. It was not intended\n for use in production environments. We are providing this\n warning to you as an advisory.\n\n===========================================================================\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no user should be using KIDS during the install of this patch.\nMSM sites must manually move the routine XPDIJ to their other CPUs. KIDS\ncannot automatically move this routine for you. \n===========================================================================\n-KIDS will now correctly turn off Alpha/Beta testing for a package.\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n-The routine XQABTMP can be used to turn off Alpha/Beta testing for\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. MSM Sites - D ^%RCOPY to move the routine XPDIJ to your other\n CPUs.\n 7. AXP Sites, after patch has installed, rebuild your map set.\n previously released packages that used KIDS. i.e. Kernel 8.0,\n ==================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Name Checksum Patch List\n -----------------------------------------------------------\n XPDDP 12181499 21,28\n XPDIA 12064759 10,15,21,28\n Radiology 4.5, Toolkit 7.3\n XPDIJ 18206759 2,21,28\n XPDIP 8727472 15,21,28\n XPDIPM 1817853 21,28\n XPDIQ 6693337 21,28\n XPDT 17164426 2,10,28\n XPDUTL 2564737 21,28\n XQABLOAD 13951526 28\n XQABTMP 2221215 new\n XQCS 9069982 15,28\n XQSET 11570399 28\n-Build File Print now pages correctly when displaying the description.\n XUSRB 2627976 11,16,28\n XUSRB1 9903269 new\n ============================================================================\n\n DATA DICTIONARY: Partial DDs\n\n File: BUILD #9.6, Field: PRE-TRANSPORTATION ROUTINE #900.\n This field contains a [TAG^]ROUTINE that will be run during the\n transportation process for the Build. This will allow a developer\n to populate the transport global using the variable XPDGREF.\n-New function $$PATCH^XPDUTL(patch) checks if patch has been installed.\n\n File: OPTION #19, Field: TYPE #4.\n This set of codes field has been updated to include the code\n B = Broker (Client/Server). \n ===========================================================================\n\n FORMS:\n XPD EDIT BUILD (File 9.6)\n Was change to add the field, PRE-TRANSPORTATION ROUTINE, to page 1.\n ============================================================================\n-The TYPE field in the OPTION file now contains B:Broker (Client/Server).\n\n DOCUMENTATION:\n Developers can now put information in the KIDS Transport Global, which\n can be used by the Pre- or Post-install routines. KIDS will run the\n [TAG^]ROUTINE in the field PRE-TRANSPORTATION ROUTINE during the transport\n process. This routine can use the variable XPDGREF to set nodes in the\n transport global.\n i.e. S @XPDGREF@("My Namespace",1)="Information I need during install"\n\n During the install process, in the Pre- or Post-install routines, the\n\n\nThis is an update to %ZOSV2 for VAX/ALPHA sites only. It supports updates\n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package in this message onto your system. \n 2. Answer NO to the question: \n 'Shall I preserve what is on disk in a separate back-up message ?' \n 3. From the 'Installation Menu' of the KIDS menu, run the option \n 'Verify Checksums in Transport Global' and verify that all routines \n have the correct checksum. \n 4. From the 'Installation Menu' of the KIDS menu, run the option\n'Install Package(s).' Select the package and proceed with install.\n \nto VPM (Kernel Toolkit's VMS Performance Monitor) and must be installed\n 5. After installing this patch, you need to move the routine from \n your production account to the manager account: \n \n ZOSV2VXD\n \n 6. Rename the routine to, "%ZOSV2." If this routine is mapped, be sure\nto disable mapping of this routine.\nprior to installing Kernel Toolkit patch XT*7.3*17.\n \nROUTINE CHECKSUM\n------- ----------\nZOSV2VXD value = 9513833 \n \nInstallation:\n\n
\nThis patch removes a command that is not necessary and conflicts with \n \n \nBlood Bank Team Coordination:\n=============================\n Clearance - Aug 28, 2002\n \nThanks To Test Sites:\n=====================\n Clarksburg, WV\n \nthe M-to-M Broker.\n \n \nRoutine Summary:\n================\nThe following routine is included in this patch. The second\nline of this routine now looks like:\n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \nChecksums:\n \n==========\nChecksums obtained using CHECK^XTSUMBLD\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XUSRB 8323600* 8315324 **11,16,28,32,59,70,82\n 109,115,165,150,180\n 213,234,238**\n \n*If patch XU*8*234, which was released as a part of patch YS*5.01*71,is \nOther than removing this one command, this patch is equivalent to \nNOT installed (not required for this patch) the Chksum Before would be \n8143764.\n \nList of preceding patches: 213 (234 may be installed as well)\n \n \nInstallation Instructions:\n \n 1. Users ARE allowed to be on the system during the \n installation. However, you should select a time when minimal\nXU*8*234. For those sites which do not install various packages, e.g., \n users are on the system. Installation of this patch may affect \n users who are just connecting from a client application with \n RPCBroker.\n \n 2. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \n This option will load the KIDS (Kernel Installation and Distribution \n System) package onto your system.\nCMOP, etc., this patch may be installed without installation of patch \n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. The patch has now been loaded into a transport global on your \n system. On the KIDS menu, select the 'Installation' menu and use\n the following options: \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\nXU*8*234 (which was released as a part of YS*5.01*71). However, if \n \n Return to Programmers Prompt and use "D ^XPDKRN":\n Select KIDS OPTION: Install\n =======\n Install Package(s) \n Select INSTALL NAME: XU*8.0*238\n ==========\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nsuch a site subsequently installs XU*8*234 after this patch, this patch \n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? \n YES// NO\n ==\n \n 6. AXP Sites - Answer 'NO' to the question 'Want to MOVE \n routines to other CPUs?'.\n \n 7. If the routines were unmapped as part of step 2, they should be \n returned to the mapped set once the installation has run to \nshould be installed again.\n completion.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nInstitution file & Reasonable Charges project\n \nRefer to patch XU*8*217 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nSee description text in Patch Module for details on this patch.\n\n\n
\nSee patch XU*8*236 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch XU*8*259 in the National Patch Module for complete information\non this patch.\n\n
\nThis patch is in support of the Hui/VHA CIO SD&D Pharmacy Data \n- XUHUI SEND HL7 MESSAGE (protocol from the Protocol, #101, file)\n \nTaskMan does not need to be STOPPED or placed in a WAIT state and \ninstallation should take less than a minute.\n \n 1. AXP/DSM sites: No review of mapped routine set is necessary \nsince these routines are new.\n \n 2. Shutdown all Logical Links, incoming and outgoing filers, and\nthe Link Manager using the Filer and Link Management options listed \nbelow:\n- XUHUI MFN and XUHUI MFK (HL7 protocols from the Protocol, #101, file)\n \n Stop All Messaging Background Processes [HL STOP ALL]\n TCP Link Manager Start/Stop [HL START/STOP LINK MANAGER]\n \n AXP/DSM SITES ONLY: Disable all HL7 UCX Services for this\n installation.\n \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \nThis option will load the KIDS package onto your system. \n \n- XUHUI MFN and XUHUI MFK (HL7 applications from the HL7 Application \n 4. The patch has now been loaded into a transport global on your \nsystem. You now need to use KIDS to install the transport global. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the \nfollowing options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \nParameter, #771, file)\n 6. On the KIDS menu, under the 'Installation' menu, use the \nfollowing option: \n Select Installation Option: Install Package(s) \n Select INSTALL NAME: XU*8*239\n ==========\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONs during the install?\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? \n \n- HUI PROV (logical links from the HL7 Logical Link, #870, file)\n 7. Start up all Logical Links and incoming and outgoing filers using \nthe Filer and Link Management Option's 'Restart/Start All Links and \nFilers \n[HL TASK RESTART]' menu option.\n \n (Note that links that do not have "autostart" enabled will need\n to be restarted manually.)\n \n AXP/DSM SITES ONLY: If you previously disabled an HL7 UCX Service\n for this installation, you may enable it now.\n \n \n 8. AXP/DSM Sites - After the patch has been installed, no rebuilding\nyour map set is necessary.\n \n>>> Sample Installation Dialog <<<\n \nSelect INSTALL NAME: XU*8.0*239 Loaded from Distribution Loaded \nfrom D\nistribution 7/10/02@11:33:20\n => XU*8*239 TEST v1\n **Take special notice of the special post installation**\n \nThis Distribution was loaded on Jul 10, 2002@11:33:20 with header of \n XU*8*239 TEST v1\n It consisted of the following Install(s):\n XU*8.0*239\nChecking Install for Package XU*8.0*239\n \nInstall Questions for XU*8.0*239\n \n \n **instructions \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \nDEVICE: HOME// 0;P-OTHER;80;999 SYSTEM\n \n \n Install Started for XU*8.0*239 : \n Jul 10, 2002@11:36:42\n \nBuild Distribution Date: Jul 10, 2002\n \n Installing Routines:\n Jul 10, 2002@11:36:42\n \n Installing PACKAGE COMPONENTS: \n \nTest Sites: \nXU*8.0*239 \n \n Installing HL LOGICAL LINK\n \n Installing HL7 APPLICATION PARAMETER\n \n Installing PROTOCOL\n Jul 10, 2002@11:36:43\n \n Updating Routine file...\nInterchange project. The project provides a method for the one-way \n================\n \n Updating KIDS files...\n \n XU*8.0*239 Installed. \n Jul 10, 2002@11:36:43\n \n \n=========================================================================\n Special Post Installation Instructions\n=========================================================================\nPalo Alto, Clarksburg WV, North Chicago, and Oklahoma City.\n \n For Those Sites Who ARE NOT part of the Hui/VHA OI SD&D \nPharmacy \nData Interchange project, no further action is necessary.\n \n========================================================================\n For Those Sites Who ARE part of the Hui/VHA OI SD&D Pharmacy Data \nInterchange project, perform the following steps:\n \nPart 1: Removal of the 'DISABLE' message so the Protocols will launch:\n \n \n>D Q^DI \n \nVA FileMan 22.0\n \nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n \nINPUT TO WHAT FILE: PROTOCOL// \nEDIT WHICH FIELD: ALL// DISABLE \nTHEN EDIT FIELD: \nBlood Bank Team Coordination: \n \nSelect PROTOCOL NAME: XUHUI\n 1 XUHUI FIELD CHANGE EVENT Field Change Event \n 2 XUHUI MFK \n 3 XUHUI MFN \n 4 XUHUI SEND HL7 MESSAGE Send HL7 MFN message \n 5 XUHUI SEND MESSAGE Send Notification Message \nCHOOSE 1-5: 1 XUHUI FIELD CHANGE EVENT Field Change Event \nDISABLE: *Do not remove this message Replace @\n SURE YOU WANT TO DELETE? Y (Yes)\n================\n \n \nSelect PROTOCOL NAME: XUHUI\n 1 XUHUI FIELD CHANGE EVENT Field Change Event \n 2 XUHUI MFK \n 3 XUHUI MFN \n 4 XUHUI SEND HL7 MESSAGE Send HL7 MFN message \n 5 XUHUI SEND MESSAGE Send Notification Message \nCHOOSE 1-5: 4 XUHUI SEND HL7 MESSAGE Send HL7 MFN message \nDISABLE: *Do not remove this message Replace @\nClearance - Oct 8, 2002\n SURE YOU WANT TO DELETE? Y (Yes) \n \nPart 2: Enabling AUTOSTART in the HUI PROV logical link:\n \nINPUT TO WHAT FILE: PROTOCOL// HL LOGICAL LINK (205 entries)\nEDIT WHICH FIELD: ALL// AUTOSTART \nTHEN EDIT FIELD: \n \nSelect HL LOGICAL LINK NODE: HUI PROV\nAUTOSTART: E Enabled\n \n \nSelect HL LOGICAL LINK NODE:\n \n \nHUI HL7 Messaging is now enabled.\nRoutine Summary: \n================\n The following routine is included in this patch. The second line of \nelectronic transfer of prescription orders from an external system to \nthis routine now look like: \n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995 \n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n XUHUIHL7 -N/A- 3202066 239\n \nVistA.\nProtocol Summary: \n================\n \nAME: XUHUI FIELD CHANGE EVENT ITEM TEXT: Field Change Event\n DISABLE: *Do not remove this message TYPE: extended action\n CREATOR: GARCIA,JOSE\n DESCRIPTION: This is used to launch, in the backgound, the protocols \nthat\n are listed in the ITEM multiple. Called from routine: DEQUE^XUHUI. \nITEM: XUHUI SEND MESSAGE\n \nITEM: XUHUI SEND HL7 MESSAGE\n \nNAME: XUHUI SEND HL7 MESSAGE ITEM TEXT: Send HL7 MFN message\n DISABLE: *Do not remove this message TYPE: action\n CREATOR: GARCIA,JOSE\n DESCRIPTION: This Action protocol is used to send an HL7 MFN message \nto the\n HUI remote middleware. \n ENTRY ACTION: D ^XUHUIHL7 \n \nThis patch transports the following entries:\nNAME: XUHUI MFN TYPE: event driver\n CREATOR: GARCIA,JOSE\n DESCRIPTION: This HL7 event protocol is one of two protocols used to\n generate staff/practitioner master file (MFN) messages. This particular\n protocol represents the sending system. \n SENDING APPLICATION: XUHUI MFN TRANSACTION MESSAGE TYPE: MFN\n EVENT TYPE: M02 VERSION ID: 2.3.1\n RESPONSE PROCESSING ROUTINE: Q\nSUBSCRIBERS: XUHUI MFK\n \n \nNAME: XUHUI MFK TYPE: subscriber\n CREATOR: GARCIA,JOSE\n DESCRIPTION: This HL7 event protocol is one of two protocols used to\n generate staff/practitioner master file (MFN) messages. This particular\n protocol represents the receiving system. \n RECEIVING APPLICATION: XUHUI MFK EVENT TYPE: M02\n LOGICAL LINK: HUI PROV RESPONSE MESSAGE TYPE: MFK\n PROCESSING ROUTINE: Q\n \nHL7 Application Parameter Summary: \n- XUHUIHL7 (routine)\n================\n \nNAME: XUHUI MFN ACTIVE/INACTIVE: ACTIVE\n \n \nNAME: XUHUI MFK ACTIVE/INACTIVE: ACTIVE\n \n \nHL7 Logical Link Summary: \n================\n- XUHUI FIELD CHANGE EVENT (protocol from the Protocol, #101, file)\n \nNODE: HUI PROV LLP TYPE: TCP\n AUTOSTART: Enabled QUEUE SIZE: 10\n TCP/IP ADDRESS: 127.0.0.1 TCP/IP PORT: 2080\n TCP/IP SERVICE TYPE: CLIENT (SENDER) \n \nInstallation Instructions: \n==========================\nThis patch can be installed with VISTA users online. However, it is \nrecommended that it be Queued for a time of generally least activity. \n\n
\n This patch contains the following features:\n -Fixes bug that left ^XTMP("XPDI", global for certain patches.\n XQ5 13875754 44\n XQ7 2506259 44\n XTSUMCK 15685964 44 (new)\n XTSUMCK1 2208048 44 (new)\n ZTPTCH 4513173 44 (new)\n============================================================================\nDOCUMENTATION:\n\n OPTION:\n\n-Fixes bug when Environment Check Routine is run during the load process and\n Systems Manager Menu ...\n Programmer Options ...\n Routine Tools ...\n\n'Check Routines on Other CPUs' Option name: XUPR RTN CHKSUM\n This option will compare the Checksum for routines in the Production\n account of one system to the checksums for the same routines on another\n system. It is only for sites who have Compute and Print Servers with\n different routine directories.\n\n the variable XPDQUIT or XPDABORT is set to 2. The Install file would be\n'Routines by Patch Number' Option name: XUPR RTN PATCH\n This options will print routines associated with a patch. You must\n enter a list of routines and then the output will be by patch numbers.\n\n\n Systems Manager Menu ...\n Programmer Options ...\n Kernel Installation & Distribution System ...\n Utilities ...\n\n incomplete and the install would get an undef error.\n'Display Patches for a Package' Option name: XPD PRINT PACKAGE PATCHES\n This option will print all patches installed for a Package. It displays\n the Date Installed and who installed the patches. It optionally will\n print the description of the patch. All information comes from the\n Package file.\n\n'Rollup Patches into a Build' Option name: XPD ROLLUP PATCHES\n This option will find all the patches for a Package and add their Build\n file definition to the Package Build file definition. This will enable\n you to create a single Build file entry that contains the definition for\n-New message, if the Install file is incomplete the user will get the message\n a patched Package.\n\n\n DATA DICTIONARY: Partial DD\n\n File: BUILD #9.6\n Field: REQUIRED BUILD #11\n Subfield:\n .01 REQUIRED BUILD\n Enter a Build name, a patch or package, that is required to\n '**INSTALL FILE CORRUPTED**', and the install will abort.\n be installed before this Build is installed. KIDS will check\n the Package file, Version multiple and Patch Application\n History multiple, to verify that the Required Build has been\n installed. \n 1 ACTION\n This is the action you want to happen when installing this\n Build and the Required Build has not been installed at the\n site. \n\n Field: MULTIPLE BUILD #10\n-New Alerts will be sent to the installer if an error occurs during the\n Subfield:\n .001 INSTALL ORDER\n This is the order in which this package will be installed.\n .01 MULTIPLE BUILD\n Name of Build that will be part of this multi-package\n distribution or a patch that is part of this Build definition. \n\n File: INSTALL #9.7\n Field: VOLUME SET #30\n Subfield:\n install process or if a CPU is not updated.\n .01 VOLUME SET\n Enter the name of the VOLUME SET that you want updated when\n this package is installed. This field points to the VOLUME SET\n file, #14.5. A VOLUME SET must have the field SIGNON/PRODUCTION\n VOLUME SET, #9, set to YES.\n\n File: VOLUME SET #14.5\n Field: SIGNON/PRODUCTION VOLUME SET #9\n Enter Yes if this Volume Set has the following properties:\n 1. Users can sign-on into the Kernel Menu system or the RPC\n-New options: Routines by Patch Number, Display Patches for a Package,\n Broker Server routine is running there.\n 2. Has a productions UCI which contains application routines.\n 3. The ^XTMP global is translated.\n If you enter Yes the Kernel Installation and Distribution\n System will be able to move routines to this Volume Set. The\n Kernel Menu system will be able to run the Menu Microsurgery\n and keep menus updated.\n Rollup Patches into a Build, and Check Routines on Other CPUs.\n\n-New type of Build, MULTI-PACKAGE. It contains a list of other Builds.\n-New field, REQUIRED BUILD #11, in file BUILD #9.6.\n-New field, SIGNON/PRODUCTION VOLUME SET #9, in file VOLUME SET #14.5.\n-KIDS will support HL7 type fields in the Protocol file, #101.\n-KIDS will also support the following files as components:\n MAIL GROUP #3.8\n HL7 APPLICATION PARAMETER #771\n HL LOWER LEVEL PROTOCOL PARAMETER #869.2\n HL LOGICAL LINK #870\n==============================================================================\n DAY-0996-41414\n **** INSTALL INSTRUCTIONS ****\n==============================================================================\n\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no other users should be using KIDS while you install this patch.\nSince this patch is an update to KIDS, no other patches should be installed\nduring the installation of this patch.\n\n**MSM sites must manually move the routines XPDIJ and XPDCPU to their other\n CPUs. KIDS cannot automatically move these routines for you.**\n -Fixes undef error in XPDIK when install patch with DD's.\n==============================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n FRE-0996-60791, ANN-0996-41556\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. MSM Sites - D ^%RCOPY to move the routine XPDIJ and XPDCPU to your\n -Fixes subscript error when converting a package.\n other CPUs.\n 7. Move the routine ZTPTCH to your Manager Account(s) and rename as %ZTPTCH\n on all systems where the users can signon through ZU.\n 8. AXP Sites, after patch has installed, rebuild your map set.\n 9. MSM Sites - You should edit the SIGNON/PRODUCTION VOLUME SET field using\n the 'Volume Set Edit' option under the 'Edit Taskman Parameters' menu.\n Enter 'YES' for your Compute and Printer servers. Enter 'NO' for your\n File servers.\n 10. MSM Sites - Drop into programmer mode and DO KICK^XQ7. This will start\n Micro-surgery on all the servers you just edited in the VOLUME SET file.\n REN-1095-62643, BOI-1095-53144, MUS-0696-70425\n===========================================================================\n \nROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Name Checksum Patch List\n -----------------------------------------------------------\n XPDCPU 6460017 41,44\n XPDDCS 4096637 2,44\n -Fixes nouci errors when MenuMan's Micro-surgery runs on MSM sites.\n XPDDP 11584192 21,28,44\n XPDDPCK 3463634 44 (new)\n XPDE 15036235 2,15,21,44\n XPDER 6591221 44 (new)\n XPDET 5054183 15,39,41,44\n XPDI 17816610 10,21,39,41,44\n XPDIA 12898389 10,15,21,28,44\n XPDIA1 7754922 2,44\n XPDIJ 10173098 2,21,28,41,44\n XPDIL 10583214 15,44\n BEC-0996-21668\n XPDIL1 8511833 15,17,39,41,44\n XPDIP 9737651 15,21,28,30,41,44\n XPDIU 7734016 15,41,44\n XPDR 18038674 1,2,44\n XPDT 19190604 2,10,28,41,44\n XPDTA 7419894 15,44\n XPDTA1 4760350 44\n XPDTC 12862739 10,15,21,39,41,44\n XPDTP 2384575 21,40,44\n XPDV 9865255 30,44\n\n\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*222 7 NOIS AND 2 E3R\n\n
\nSee patch XU*8*246 in the National Patch Module for complete information\non this patch. \n\n
\nSee patch XU*8*266 in the National Patch Module for complete information\non this patch.\n\n
\nE-Sig Improvements\n will be done by taking the current date+random(60)+30 days to give a date\n when the user will need to select a new E-SIG code.\nThe option XUSESIG BLOCK is included in this patch.\n \nKERNEL functions to help developers.\n \n$$CHKSUM^XUSESIG1($name_value,flag)\nThis would take a root ($name_value) and build a checksum for all data in the\nroot. (Not used now, flag would be used when there is more that one checksum\nalgorithm.)\n\n \n$$ESBLOCK^XUSESIG1(ien)\nThis extrinsic function would return the set of fields from the new \nperson file that are need as part of the hash for a acceptable E-Sig. \nIf IEN is not passed in then DUZ is used.\n(E-Sig block, E-Sig title, Degree, Current Date/Time)\n \n$$EN^XUSESIG1(checksum,esblock)\nIf the ESBLOCK is not passed then the function would get the ESBLOCK. In \neither case this extrinsic function would encode the ESBLOCK using the \nNew E-SIG functions so that other developers can follow the General\nchecksum as the KEY. Return a encoded string. \n\n$$CMP^XUSESIG1(checksum,$name_value)\nThe extrinsic function would compare the checksum passed in to the \ncalculated value from the $NAME_VALUE. Return 1 for match, 0 for no \nmatch.\n \n$$DE^XUSESIG1(checksum,encoded_string)\nThis extrinsic function would decode the string using the checksum as \nthe key. Return a decoded string.\nCounsels guidelines on E-SIG. This comes from a meeting at Birmingham on\n \n\nRoutine ChkSum 2nd Line\nXUSESIG 5865804 ;;8.0;KERNEL;**14**;Jul 10, 1995\nXUSESIG1 864068 ;;8.0;KERNEL;**14**;Jul 10, 1995\n\n========================================================================= \nInstallation:\n \n 1. These routines may be mapped on systems that allow mapping,\n9/18-20/95. New routine XUSESIG1.\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n\n Backup a Transport Global\n 4. Inhibit users from login into the system. (If you install when few\n user are on the system and the possibility of some CLOBER errors is\n acceptable then users can stay on the system.)\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Install Package(s) 'XU*8.0*14'\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\nChanges to the New Person file:\n\n=========================================================================\n\n Added a DEGREE field to hold MD, RN, LPN...\n Added a DATE E-SIG LAST CHANGED field. The seeding of the this field\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nSee patch XU*8*189.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*229 KIDS fixes\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*274 Fix to Tasked DEACTIVATE user.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*267 DEA API and INST DEA #\n\n
\nPatch XU*8*263 REINDEX THE USER KEY'S [XUSE KEY RE-INDEX] FIX. Please refer to\nthe Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nPatch XU*8*269 Add LOCKING to XUESSO1.\n\n
\nPatch XU*8*257 rebuilds the ISO Menu. Please refer to the Description in FORUM\nPatch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*278 Cache/NT %ZIS4 fix.\n\n
\nSee patch XU*8*240 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis patch contains 7 routines, 1 option, and 1 input template. It\n2. Routines XQSMD1 and XQOO: Confusion resulted when a user encountered\nan option that contained a hyphen in the option name. The software could\nnot easily distinguish between this type of option and two different\noptions presented with a hyphen between them as a range of options to\nselect. The software now looks first to see if a single option meets the\nselection criterion, and if so it ignores the possibility of a range of\noptions.\n \n3. The option XUEDITOPT and the input template [XUEDITOPT]: A piece of\ncode was added to the template in Kernel 8 to start micro surgery to\nreplaces XU*8*4 which has been canceled. It fixes 3 problems in the Menu\nrebuild the compiled menus after an option was created or changed. This\nresulted in errors because the code called FileMan from within a template.\nThe call was therefore moved to the Exit Action of the option to avoid\nthat conflict. [NOIS ERI-1095-21763, FTM-1095-43520]\n \n=========================================================================\nINSTALLATION: \n 1. Many of these routines may be mapped on systems that allow\n mapping, so you may need to disable mapping.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \nSystem:\n option will load the KIDS package onto your system. \n 3. Answer NO to the question: \n 'Shall I preserve what is on disk in a separate back-up message ?' \n 4. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n 5. On the KIDS menu, under the 'Installation' menu, use the option \n 'Verify Checksum in Transport Global' and verify that all routines \n have the correct checksums. \n 6. On the KIDS menu, under the 'Installation' menu, use the option \n 'Install Package(s)'. Select the package 'XU*8.0*29' and proceed \n \n with the install. \n 7. Rebuild your mapped set if necessary.\n========================================================================\n \nROUTINE CHECKSUM PATCHES IN 2ND LINE\n \nXQ72 10277570 **29**\nXQ75 14473337 **29**\nXQ83R 15234319 **29**\nXQCHK 7318302 **29**\n1. Routines XQ72, XQ75, XQ83R, XQCHK, and XQT: If a parent option on the\nXQOO 20509324 **10,21,29**\nXQSMD1 14983624 **29**\nXQT 14370309 **20,29**\ntop of a menu tree was placed out-of-order or locked a user might be able\nto jump through it because of the way the compiled menus in ^XUTL were\nbeing built. [NOIS WBP-0895-22132]\n \n\n
\nPatch XU*8*282 PERSON CLASS EXPIRED. Please refer to the Description in Forum\nPatch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*258 Multiple Sign on Update.\n\n
\n See the National Patch Module for a complete description.\n\n
\nSee Patch Module for a complete description.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*224 Fix XUPARAM.\n\n
\nPATCH XU*8*273 SWITCH IDENTITIES FIX.\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nSee patch XU*8*280.\n\n
\nSee patch XU*8*301 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nXU*8.0*296\ndefinition does not define 0 as an allowed value. This causes "0" to\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XU*8.0*296 Loaded from Distribution <date/time>\n ==========\n Install Questions for XU*8.0*296\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\ndisplay during display functions instead of null or NO.\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n\nTo fix this, "0" (meaning NO) is being added to the set of codes for this\nfield and the others in this multiple.\n\nThis patch contains no routines; only the DD changes.\n\nSTANDARD DATA DICTIONARY #200.032 -- ACCESSIBLE FILE SUB-FILE\nSTORED IN ^VA(200,\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n200.032,1 DATA DICTIONARY ACCESS 0;2 SET\n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: APR 08, 2003 \n DESCRIPTION: This field is a flag that, when set to 1, gives\n the user data dictionary access to the file (in\n the .01 field) represented in this record. \nNOIS: ISD-0500-72669\n\n200.032,2 DELETE ACCESS 0;3 SET\n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: APR 08, 2003 \n DESCRIPTION: This field is a flag that, when set to 1, gives\n the user delete access to the file (in the .01\n field) represented in this record. \n\n200.032,3 LAYGO ACCESS 0;4 SET\nTest Sites: Dallas OIFO\n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: APR 08, 2003 \n DESCRIPTION: This field is a flag that, when set to 1, gives\n the user LAYGO access to the file (in the .01\n field) represented in this record. \n\n200.032,4 READ ACCESS 0;5 SET\n '1' FOR YES; \n '0' FOR NO; \nBlood Bank Team Clearance: 4/9/03\n LAST EDITED: APR 08, 2003 \n DESCRIPTION: This field is a flag that, when set to 1, gives\n the user read access to the file (in the .01\n field) represented in this record. \n\n200.032,5 WRITE ACCESS 0;6 SET\n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: APR 08, 2003 \n DESCRIPTION: This field is a flag that, when set to 1, gives\n\n the user write access to the file (in the .01\n field) represented in this record. \n\n200.032,6 AUDIT ACCESS 0;7 SET\n '1' FOR YES; \n '0' FOR NO; \n LAST EDITED: APR 08, 2003 \n DESCRIPTION: This field is a flag that, when set to 1, gives\n the user audit access to the file (in the .01\n field) represented in this record. \nThe Kernel Part III post routine, XUINCON - BUILDS ACCESSIBLE FILE MULTIPLE,\n\nNOTE: This patch may be installed at any time. Users may be on the system.\nIt has no patch pre-requisites.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After\nsets the NEW PERSON (#200) file's ACCESSIBLE FILE (#200.032) sub-file's\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nNo routines are included in this patch.\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time. Users may be on the system.\nWRITE ACCESS (#5) field to zero at D1+1^XUINCON. The Set of Codes field\nIt has no patch pre-requisites.\n1. Users may be on the system during installation of this patch.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. Users may be on the system. You do not need to stop TaskMan.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n\n
\nXU*8.0*297\nto 63 characters so that more of the name appears when the user enters '?'\nto get a list of spool documents when using option [XU-SPL-PRINT] Print A\nSpool Document. The post-init (POST^XU8P297) for this patch will kill\nthe existing "B" xref and reindex the NAME (#.01) field. Here's the new DD\nfor that field. Nothing's changed, except the size of the "B" xref.\n\nSTANDARD DATA DICTIONARY #3.51 -- SPOOL DOCUMENT FILE\nSTORED IN ^XMB(3.51,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n\n----------------------------------------------------------------------------\n3.51,.01 NAME 0;1 FREE TEXT (Required)\n INPUT TRANSFORM: K:$L(X)>80!($L(X)<3)!'(X'?1P.E)!(X'?.ANP)!(X?1.\n 2E1"-".E) X\n LAST EDITED: MAR 04, 1988 \n HELP-PROMPT: Answer must be 3-80 characters in length, and \n not look like a TERM. TYPE. \n DESCRIPTION: This field holds the name of the spool\n document. To avoid device handler confusion,\n the name of the spool document must not look\nNOIS: PUG-0403-50483\n like the name of a terminal type, e.g. C-VT100,\n since either name might be contained in a\n response to the device prompt. \n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n CROSS-REFERENCE: 3.51^B \n 1)= S ^XMB(3.51,"B",$E(X,1,63),DA)=""\n 2)= K ^XMB(3.51,"B",$E(X,1,63),DA)\n\n2. The print template [XU-ZISPL-USER] is altered so that the first 44 (up\nfrom 20) characters of the spool document names are shown when using option\nTest Sites: Puget Sound HCS\n[XU-SPL-LIST] List Spool Documents. During the install, you will see the\nfollowing message:\n The following Routines were created during this install:\n XUCT02\nXUCT02 is the routine into which the print template is compiled.\n\nNOTE: This patch should be installed during off-hours, when a minimal number\nof users are on the system. It has no patch pre-requisites.\n============================================================================ \n\nBlood Bank Team Clearance: 4/11/03\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXU8P297 * new * 32940 297\n* Checksums produced by CHECK^XTSUMBLD\n\n\nThis patch introduces routine ^XU8P297, which has no user entry points,\nand will be deleted once it has run.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off-hours, when a minimal number\nof users are on the system. It has no patch pre-requisites.\n1. Users may be on the system during installation of this patch.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nThis patch concerns the SPOOL DOCUMENT (#3.51) file.\n3. Users may be on the system. You do not need to stop TaskMan.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XU*8.0*297 Loaded from Distribution <date/time>\n ==========\n\n Install Questions for XU*8.0*297\n\n Incoming Files:\n 3.51 SPOOL DOCUMENT (Partial Definition)\n Note: You already have the 'SPOOL DOCUMENT' File.\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n1. The length of the "B" xref on the NAME (#.01) field is increased from 30\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n\n
\nXU*8.0*300\nSometimes, a user's PERSON CLASS history can look pretty confusing:\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XU*8.0*300 Loaded from Distribution <date/time>\n ==========\n Install Questions for XU*8.0*300\n\n Incoming Files:\n 200 NEW PERSON (Partial Definition)\n Note: You already have the 'NEW PERSON' File.\n\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\nPerson Class Effective Expired\n ------------------------------\n Nursing Service OCT 1,1995 NOV 17,1998\n Nursing Service NOV 17,1998 APR 13,2000\n Nursing Service APR 13,2000 JUN 2,1998 <<problem\n Physician Assistants & Advanced Practice JUN 2,1998 OCT 1,1995 <problem\n Physician Assistants & Advanced Practice OCT 1,1995\n\n1. The API $$GET^XUA4A72, given a person and a date, retrieves the active\n\nclass for that person on that date. It can get confused when confronted\nwith problems such as those above, and return an error (no active class for\nthis person on this date) for 5/18/2000, for example. This patch makes the\nAPI a bit smarter. It will return the last person class for 5/18/2000. It\nwill return the same one (not the first one) for 11/1/1996.\n\n2. When a new PERSON CLASS record is added to the multiple, the expired date\nof the previous one is set to the effective date of the new one. If the\neffective date of the new one is prior to the effective date of the previous\none, this results in records such as those marked "problem" above. To remedy\nNOIS: NHM-0500-11955\nthis, we add a simple check: If the Effective Date of the previous class is\ngreater than the Effective Date of the new class, then we set the Expired\nDate of the previous class to be the same as its Effective Date.\n\n3. Patch XU*8*49 purportedly prevented you from adding a new PERSON CLASS\nrecord with an effective date prior to the effective date of the previous\none. It didn't work. This patch does. A new input transform on the\nEffective Date (#2) field sees to it.\n\nSTANDARD DATA DICTIONARY #200.05 -- PERSON CLASS SUB-FILE \nTest Sites: Northampton, MA\nSTORED IN ^VA(200,D0,"USC1",\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n200.05,2 Effective Date 0;2 DATE (Required)\n INPUT TRANSFORM: N %DT,% S %DT="EX",%=$O(^VA(200,D0,"USC1",DA),-\n 1) S:% %=$P($G(^(%,0)),U,2) S:% %DT(0)=% D ^%DT\n S X=Y K:Y<1 X\n LAST EDITED: APR 24, 2003\nBlood Bank Team Clearance: 5/1/2003\n HELP-PROMPT: The date that this Person Class became\n effective.\n DESCRIPTION: This field is trigger by adding a new person\n class.\n\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n\n CROSS-REFERENCE: 200.05^AD \n 1)= S ^VA(200,DA(1),"USC1","AD",$E(X,1,30),DA)=""\n 2)= K ^VA(200,DA(1),"USC1","AD",$E(X,1,30),DA)\n\n 3)= Don't Delete\n This X-ref is by date and allows us to find the\n most current entry in the file.\n\n CROSS-REFERENCE: 200.05^AE^MUMPS\n 1)= D SET2^XUA4A72\n 2)= D KILL2^XUA4A72\n 3)= Special Trigger\n This Special X-ref sets the Expiration date of\n the previous person class entry to the current\nThis patch concerns the PERSON CLASS (#200.05) subfile of the NEW PERSON\n record's Effective date.\n\nNOTE: This patch should be installed during off-hours, when a minimal number\nof users are on the system. It requires patch XU*8.0*222.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n(#200) file.\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXUA4A72 4721844 4894947 27,49,74,132,222,300\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\n\nNOTE: This patch should be installed during off-hours, when a minimal number\nof users are on the system. It requires patch XU*8.0*222.\n1. Users may be on the system during installation of this patch.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. Users may be on the system. You do not need to stop TaskMan.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n\n
\nXU*8.0*291\nshould be from himself or the Postmaster.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*8.0*2 and XM*8.0*15, as\nwell as Kernel patch XU*8.0*69.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nZISPL 14330151 14237859 23,69,291\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nE3Rs: 6512, 9016\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*8.0*2 and XM*8.0*15, as\nwell as Kernel patch XU*8.0*69.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan.\nTest Sites: FORUM (VMS/DSM), Cleveland (VMS/DSM), Grand Junction (Cache/NT)\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XU*8.0*291 Loaded from Distribution <date/time>\n ==========\n Install Questions for XU*8.0*291\nBlood Bank Team Clearance: 4/2/03\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nWhen converting a spool document to a MailMan message, the user can now\nenter the subject of the message, select the basket when addressing to\nhimself, address the message to anyone else, and choose whether the message\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nSee patch XU*8*277.\n\n
\nSee patch XU*8*251 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*283 DEA/PKI pilot.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nSee patch XU*8*288 Updated DEA~XUSER API.\n\n
\nSee patch XU*8*307 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*304 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*310 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n This patch contains a routine, and input template, and a change to\nserver on the system from 1 to 365 days.\n \n2. [MCM-1096-51188] A site complained that the edit template XUEDITOPT\ndid not allow them to edit the field SERVER DEVICE when working with a\nserver-type option. This was corrected when the new field was added to\nthe template.\n \n3. [SLC-1096-50407] Under certain circumstances, servers that were\ndesignated as "Run Immediately" in the SERVER ACTION field were not\nrunning at all but being queued because of a logic error. This problem\nthe data dictionary of the Option File [^DIC(19)]. It corrects 3 problems\nwas also noted by IHS.\n \n=============================================================\n \n CHECKSUMS WITH PATCH LIST\n \nProgram Before After\n \n XQSRV1 8538091 8877273 **50**\nwith servers:\n \n1. [CML-0296-N1840 and LIT-0496-71332 ] Server tasks were retained for\n30 days in ^ZTSK, and several sites complained that this was too long and\ntherefore a waste of disk space. The default task retention time was\nlowered to 14 days, and a field was added to the Option File (ZTSK\nRETENTION DAYS) to allow the site to set the retention time for each\n\n
\n%ZOSVKR update.\n\n
\nPlease refer the Description in Forum Patch Module for details.\nPatch XU*8*313 BCMA Contingency Support.\n\n
\nSee patch XU*8*308 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*324 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis patch provides several reporting options for Alerts, including\nThis patch adds the following options:\nList of Test Sites\n==================\nANN ARBOR, MI\nCLEVELAND, OH\nDAYTON, OH\nDUBLIN, GA\nDURHAM, NC\nFARGO, ND\nLEXINGTON, KY\nLITTLE ROCK, AR (C)\n \nMARYLAND HCS \nNEW JERSEY HCS \nNORTH CHICAGO, IL \nNORTHERN CALIFORNIA HCS\nPALO ALTO HCS\nPHILADELPHIA, PA \nPHOENIX, AZ\nSAN FRANCISCO, CA\n \n \nReport Menu for Alerts (XQAL REPORTS MENU)\nRoutine Summary:\n================\nThe following routines are included in this patch. The second\nline of each of these routines now looks like:\n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \nChecksums:\n==========\nChecksums obtained using CHECK^XTSUMBLD\n \n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XQARPRT1 N/A 33282029 **316**\n XQARPRT2 N/A 33312830 **316**\n \n \nList of preceding patches: none\n \n \nThis menu provides several options for generating reports on alerts for\nBlood Bank Team Coordination:\n=============================\nClearance - Approved 8/21/2003\n \n \nInstallation Instructions:\n \n 1. Users ARE allowed to be on the system during the\n installation.\n \nusers or patients.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS (Kernel Installation and Distribution\n System) package onto your system.\n \n 3. You DO NOT need to stop TaskMan or the background filers.\n \n 4. The patch has now been loaded into a transport global on your\n system. On the KIDS menu, select the 'Installation' menu and use\n the following options:\n Verify Checksums in Transport Global\n \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n Return to Programmers Prompt and use "D ^XPDKRN":\n Select KIDS OPTION: Install\n =======\n Install Package(s)\n Select INSTALL NAME: XU*8.0*316\n ==========\n \n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//\n NO\n ==\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO\n ==\n \nUser Alerts Count Report (XQAL USER ALERTS COUNT)\n 5. AXP Sites - Answer 'NO' to the question 'Want to MOVE\n routines to other CPUs?'.\n \nones that: list users with large number of alerts in the ALERTS file\nThis option is used to generate a report on users who have more than a\nspecified number of alerts in the ALERTS file (#8992). The report covers\na specified range of dates, and can be sorted by user name, number of\nalerts, or by service/section. In addition, the report in each of these\nformats may be generated by Divisions if desired.\n \nFor each user who has the specified number of alerts or more, the report\nincludes the user name, the section/service for the user, the number of\nalerts in the ALERTS file, the last sign-on date, the number of Critical\nalerts or Abnormal Imaging alerts, and the date of the oldest alert.\n(#8992); list alerts for a specified user from a specified date; list\n \nThe counting of alerts may also be restricted to those alerts which contain \nspecific text or phrases.\n \n \nCritical Alerts Count Report (XQAL CRITICAL ALERT COUNT)\n \nThis option is used to generate a report of users who have more than a\nspecified number of alerts containing the word 'critical' or the words\n'abnormal imaging' between the specified start and end dates. The report\nalerts for a specified patient for a specified day or date range. \nis presented in descending order for the number of critical/abnormal\nimaging alerts present.\n \nFor each user who has the specified number of critical/abnormal\nimaging alerts or more, the report includes the user name, the\nsection/service for the user, the number of alerts in the ALERTS file, the\nlast sign-on date, the number of Critical alerts or Abnormal Imaging\nalerts, and the date of the oldest alert.\n \n \nSince the retention period for alerts in the ALERT TRACKING file\nList Alerts for a user from a specified date (XQAL ALERT LIST FROM DATE)\n \nThis option is used to obtain a list of alerts from the ALERT TRACKING\nfile (#8992.1) for a specified user for a specified date range. The user\nmay select all of the alerts to be displayed, or enter specific text or\nphrases to select only alerts which contain the specified text. In the\nlatter case, the user may also select to see only those alerts which match\nthe criteria and are only info only alerts, only action alerts, or both.\n \nThe listing includes the internal entry number for the alert in the ALERT\n(#8992.1) is currently a site parameter, some users may have alerts\nTRACKING file, the date and time the alert was generated, the message\ntext of the alert, and information about any option or routine to be\nexecuted for processing the alert.\n \n \nPatient Alert List for specified date (XQAL PATIENT ALERT LIST)\n \nThis option is used to obtain a list of alerts for a specified patient\nfrom the ALERT TRACKING file (#8992.1) for a selected date range (it is\nrecommended that this range be only a few days at most, since every entry\nin the ALERTS file that no longer are present in the ALERT TRACKING file,\nin the ALERT TRACKING file in the selected date range must be checked to\nprovide a complete listing of alerts for a patient).\n \nA prompt is provided to obtain a quick scan listing of dates with at least\nsome alerts for the patient on it based on OR and DVB alerts (other\npatient related alerts need to be identified by looking at each alert's\nmessage text and are included in the full list, but not the quick scan).\n \nThe user may select all of the alerts to be displayed, or enter specific\ntext or phrases to select only alerts which contain the specified text. \ndata from both sources is used when necessary.\nIn the latter case, the user may also select to see only those alerts\nwhich match the criteria and are info only alerts, only action alerts,\nor both.\n \nThe listing includes the internal entry number for the alert in the ALERT\nTRACKING file, the date and time the alert was generated, the message\ntext of the alert, and information about any option or routine to be\nexecuted for processing the alert.\n \n \n \nView data for Alert Tracking file entry (XQAL VIEW ALERT TRACKING ENTRY)\n \nThis option can be used to obtain a listing of data in captioned format for\nselected entries in the ALERT TRACKING file (#8992.1). The internal entry\nnumbers for the entries to be listed must be entered individually.\n \n \nThere were no NOIS or E3Rs related to this patch.\n \n \n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\n\n
\nSee patch XU*8*292 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*327 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPatch XU*8.0*204 NEW PERSON ADDITION BULLETIN. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nXU*8*317 UPDATE PERSON CLASS FILE. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\n ** You need to install Kernel Patch XU*8*50 before installing this patch **\n -HL LOGICAL LINK entries were not being cross-referenced.\n -The post-install routine XQP50 will update the Patch Application History\n multiple with the information about patch 50. The DATE APPLIED and APPLIED\n BY fields will be the same as this patch. \n\n=============================================================================\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n\n This patch can be installed with users on the system, but no other users\n=============================================================================\n should be using KIDS while you install this patch.\n Since this patch is an update to KIDS, no other patches should be installed\n during the installation of this patch.\n=============================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n -This patch now allows you to transport a Global Package correctly. This bug\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n was introduced with patch 44.\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n \nROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After \n -The input transform for the Name field in the Build file has been changed\n Name Checksum Checksum Patch List\n -----------------------------------------------------------\n XPDE 15036235 15041471 2,15,21,44,51\n XPDET 5054183 5054366 15,39,41,44,51\n XPDIA1 7754922 7766653 2,44,51\n XPDIP 9737651 9751058 15,21,28,30,41,44,51\n XPDIU 7734016 7856776 15,41,44,51\n XPDT 19190604 19179554 2,10,28,41,44,51\n XQP50 NEW 4073107 51\n===========================================================================\n to allow sites to create local patches. It now allows 6 digit patch numbers\n\n i.e. XU*8.0*662001\n -Kernel 8 patches will now contain the sequence number in the Patch\n Application History multiple of the Package file.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8*302.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8*312.\n\n
\nKernel Patch XU*8*295 Clean-up County Codes for States (#5) file. \nPlease refer to the Description in Forum Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*293 Cache 5 fix to AVJ~%ZOSV.\n\n
\nPatch XU*8.0*303 FIX $$ACCESS~XUCHK. Please refer to the Description in Forum\nPatch Module for details.\n\n
\nPatch XU*8.0*314 Release User Fix. Please refer to the Description in Forum\nPatch Module for details.\n\n
\nPatch XU*8.0*334\n ^HOLIDAY("B",3031226,3031226) =\n \n \nRoutine Summary:\n================\n \nThe following routine is included in this patch. The second line of \nthe routine now looks like:\n<tab;;8.0;KERNEL;**[Patches List]**;Jul 10, 1995\n \n \nChecksums:\n=========\nChecksums obtained using CHECK^XTSUMBLD\n \nRoutine Chksum Before Chksum After Patch List\n----- ------------- ------------ ----------\nXU8P334 NEW **334**\n \nThis routine is set to delete after the installation, so you may not\ndo the checksum for the routine. \n This patch updates the HOLIDAY (# 40.5) file. A new holiday entry is \n \nBlood Bank Team Coordination:\n=============================\nBlood Bank Clearance -\n \nInstallation Instructions:\n==========================\n \n1. Users ARE allowed to be on the system during the installation. \n However, it is recommended that the patch be installed during\n added in the HOLIDAY (#40.5) file for the holiday on December 26, 2003.\n non-peak time. It will take about five minutes to install the\n patch, but you may queue the installation if you wish.\n \n2. You DO NOT need to stop TaskMan or the background filers.\n \n3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system.\n \n4. The patch has now been loaded into a Transport global on your system. \n You now need to use KIDS to install the Transport global. On the KIDS\n \n menu, under the 'Installation' menu, use the following options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) \n New entry:\n Select INSTALL NAME:XU*8.0*334\n ==========\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ^HOLIDAY(3031226,0) = 3031226^December 26, 2003\n \n The "B" cross-reference of the new entry:\n\n\nMSG from Warren Wright about large numbers of DEVICE LOCK bulletins\nThe check to close hung SPOOL documents had a incorrect test.\nZTMON1 7519989 ;;8.0;KERNEL;**36**;Jul 10, 1995\nZTMS 5200197 ;;8.0;KERNEL;**2,18,24,36**;Jul 10, 1995\nZTMS1 6210144 ;;8.0;KERNEL;**36**;JUL 10, 1995\nZTMS2 5283853 ;;8.0;KERNEL;**2,18,23,36**;Jul 10, 1995\nZTMS3 9454395 ;;8.0;KERNEL;**1,18,36**;Jul 03, 1995\n========================================================================= \nINSTALLATION:\n \n1. Some of these routines are usually mapped on systems that allow\nmapping, so you will need to disable mapping for the affected routines.\n \n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n3. The patch has now been loaded into a Transport global on your system.\nYou now need to use KIDS to install the Transport global.\nOn the KIDS menu, under the 'Installation' menu, use the following\noptions:\n Verify Checksums in Transport Global\n Print Transport Global\nNOIS SEP-0796-62056 The purge option was failing to get any site data\n Compare Transport Global to Current System\n Backup a Transport Global\n \n4. Users can remain on the system. \nAlso STOP TASKMAN. As long running jobs exit, they will get CLOBER errors.\nThis isn't a problem because they have finished their work and TaskMan\nwill start new ones.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\noptions:\nfrom the Kernel System Parameter file. It was looking at the wrong node.\n Install Package(s) 'XU*8.0*36'\n \n6. MSM Sites - Answer YES to the question 'Want to MOVE routines to other\nCPUs?'. Enter the names of your Compute and Print server(s).\n \n7. After installing this patch, you need to move several routines from\nyour production account to the manager account:\n \n ZIS4MSM\n ZIS4VXD\n \n ZISC\n ZISHMSM\n ZISHVXD\n ZISTCP\n ZTER\n ZTER1\n ZTM\n ZTM0\n ZTM5\n ZTMGRSET\nNOIS NOL-0796-70230 If the data in the spool file was longer that 255\n ZTMON1\n ZTMS\n ZTMS1\n ZTMS2\n ZTMS3\n \n and in the manager account, rename:\n \n DO RELOAD^ZTMGRSET\n Select the System\ncharacters, it would cause an error in %ZIS4 on DSM systems. This has\n Patch number to load: 36\n \n8. AXP Sites, after patch has installed, rebuild your map set.\n \n9. Start TaskMan, Restart Taskman on other nodes if you need to run more\nthan one TaskMan.\nbeen fixed but the report may not print the way it would have if sent\ndirectly to the printer.\n \nsent when someone leans on keyboard.\nNOIS WBP-0796-20862 When the number of spool documents is checked, only\nthose with data are counted. This is changed to count all spool documents \nwith or without data.\n \nE3R -- Request for a way to have the current date as part of a auto \ngenerated name (GENERATE SPL DOC NAME). Now if the device name includes\n"|DT|" that string will be replaced with the current date.\n \nE3R 8844 To include Person class in the User Inquiry.\n \n \nNOIS IVM-1095-32452 Some times taskman doesn't release devices\nwhen it should.\n \nNOIS NOL-0996-70063 At a dual TaskMan site Problem starting tasks on\nthe working node. The TaskMan part of this patch was developed to address\nproblems at dual TaskMan sites after the install of patch 24. It is\nunclear exactly what the problem was, but with load balancing work would\nback up. There is a new algorithm to start new submanagers and when\nsubmanagers should exit. We try and keep the number of submanagers at a\nlevel equal to a: the number of devices in the IO list. b: the MIN\nNOIS MCM-1195-51490 That the DEVICE LOCK bulletins aren't much help.\nSUBMANAGER CNT. All submanagers will remain if the JOB list has any tasks\nin it.\n \n ----- This patch adds two new fields to the TaskMan site\nparameter file (14.7): (1), MIN SUBMANAGER CNT, allows a site to set a\nlower limit on the number of submanagers to keep around. (2), TM MASTER,\nis only used when a volume set is mounted on another but shares the\nlibrary account. This is a pointer back to file 14.7 and would point to\nthe entry that is the control entry for TaskMan on that node.\n \n \nLocal MSG #1082921 \n DIC error in Add a New User. Problem in the page numbering of the\nnew FORM for Add a New User and SECONDARY MENUS. Sending out all three\nFORMs with unified page numbering.\n \n \nNOIS MAD-0895-40177 Some sites have some leftover nodes in the Institution \nfile.\n \nCollect more data in the standard error trap.\nNOIS CLE-1095-43605 The check if a user needed to be deactivated was\n \nIn patch 24 $X was set to zero before doing the close execute code.\nThis was changed to check if $X>0 and to set it to 1 so that code (like\nP-MESSAGE) that test $X would still work. \n \nIf some package was installed after Kernel 8, the "ID" nodes on the\nNEW PERSON file got changed back to an early version. Nodes are reset.\n \nNOIS IND-0996-41382 Changes to FTG^%ZISH made in XU*8*24 didn't work for\ninput like S Y=$$FTG^%ZISH("","TEST.DAT",$NA(OUT(0)),1) it did work\ncounting 'Keep at Terminate' keys even though they would never be removed. \nfine on S Y=$$FTG^%ZISH("","TEST.DAT",$NA(^TMP("XX",$J,0)),3). Fixed.\n \nVarious requests to bring back ZTMGRSET. This new version will load all\nall routines if called from the top, or only the routines with a given\npatch number if called at RELOAD^ZTMGRSET.\n \nNOIS BRK-1096-12512, CHW-0996-42161 While testing changes to %ZTER for\nuse with the new error trap we got ECODE errors under some conditions.\nThis has been fixed with a small change to %ZTER.\n \n \nRoutine CheckSum 2nd Line\nXUINPCH 1467475 ;;8.0;;KERNEL;**20,36**;Feb. 9, 1996\nXUSTERM 14380010 ;;8.0;KERNEL;**36**;Jul 10, 1995\nXUSTZ 3010944 ;;8.0;KERNEL;**36**;Jul 10, 1995\nXUTMUSE2 13026855 ;;8.0;KERNEL;**36**;Jul 10, 1995\nZIS3 6450084 ;;8.0;KERNEL;**18,36**;JUL 10, 1995\nZIS4MSM 6649854 ;;8.0;KERNEL;**23,36**;JUL 03, 1995\nZIS4VXD 8342152 ;;8.0;KERNEL;**23,36**;JUL 03, 1995\nZISC 8463272 ;;8.0;KERNEL;**24,36**;JUL 10, 1995\nZISHMSM 5354551 ;;8.0;KERNEL;**24,36**;JUL 10, 1995\nNOIS MAC-0696-61616 WBP-1195-20971 CTX-0896-71639 \nZISHVXD 7245146 ;;8.0;KERNEL;**24,36**;JUL 10, 1995\nZISPL1 8550686 ;;8.0;KERNEL;**23,36**;Jul 10, 1995\nZISPL2 4088281 ;;8.0;KERNEL;**23,36**;Jul 10, 1995\nZISTCP 1828160 ;;8.0;KERNEL;**36**;Jun 02, 1994\nZTER 18736553 ;;8.0;KERNEL;**8,18,32,24,36**;JUL 10, 1995\nZTER1 5603505 ;;8.0;KERNEL;**18,24,36**;JUL 10, 1995\nZTM 7805017 ;;8.0;KERNEL;**24,36**;JUL 10, 1995\nZTM0 5563711 ;;8.0;KERNEL;**42,36**;JUL 10, 1995\nZTM5 3748675 ;;8.0;KERNEL;**24,36**;JUL 10, 1995\nZTMGRSET 12724965 ;;8.0;KERNEL;**36**;Dec 30, 1993\n\n\nKernel patch XU*8.0*289 'Grant Access by Profile' Fix. Please refer\nto the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8.0*336.\n\n
\nSee patch XU*8*332 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nRead the WARNING below carefully prior to installing this patch.\nalert will be sent as a last resort to members of G.PATCH.\n tracking for what reason a user was sent an\n alert.\n \n CROSS-REFERENCE: 8992.2^B\n 1)= S ^XTV(8992.2,"B",$E(X,1,30),DA)=""\n 2)= K ^XTV(8992.2,"B",$E(X,1,30),DA)\n \n \nThe following is the global map structure of the new multiple:\n \n \n^XTV(8992.2,D0,0)= (#.01) NAME [1F] ^\n \n \n \nChanges to the ALERT TRACKING file (#8992.1)\n--------------------------------------------\n \nThis patch adds the following three (3) multiples to the Alert Tracking\nfile.\n \n \n \n8992.11,1 RECIPIENT TYPE 1;0 POINTER Multiple #8992.111\n (Add New Entry without Asking)\n \n \n8992.111,.01 RECIPIENT TYPE 0;1 POINTER TO ALERT RECIPIENT TYPE FILE\n (#8992.2) (Required)\n \n LAST EDITED: OCT 20, 2003\n HELP-PROMPT: This is a pointer to a file of different\n*************************** WARNING ************************************\n recipient types (i.e., the reason someone\n was sent the alert)\n DESCRIPTION: This field is used to track how a specific\n recipient was selected for receiving the\n alert. The initial recipients are those to\n whom the alert was initially directed\n (INITIAL RECIPIENT). Other recipients\n may be the result of forwarding.\n Recipients of the alert from forwarding\n are noted by the type of forwarding involved\n \n (FWD BY USER, EMAIL SURROGATE, CHIEF/\n SUPERVISOR, BACKUP REVIEWER, or\n LAST HOPE).\n \n Marked as a specific category are those to\n whom the alert was directed, but who were\n not available to receive an alert due to\n lack of access (marked with the suffix\n "-UNDELIVERABLE" added to the basis for the\n alert being sent to the user).\nThe number of alerts generated to inactive users may be very large. Your\n \n Those who have alerts forwarded to their\n surrogate or receive the alert while acting\n as a surrogate for another user are\n indicated by entries in fields #.02 (SENT\n TO SURROGATE) and #.03 (ACTING AS\n SURROGATE) respectively. In addition,\n those who are acting as surrogates are\n identified in the current field by the\n suffix "-SURROGATE" added to the basis\nstaff may need assistance in dealing with them and, in the case of unsigned\n for the alert being received. Since the\n recipient may be acting as surrogate for\n more than one user, the actual users for\n which the message was sent on a\n surrogate basis are indicated in the\n SURROGATE FOR sub-file (#8992.113)\n under the RECIPIENT sub-file.\n \n The values stored for this field are\n pointers to entries in the ALERT RECIPIENT\ndocuments, (many of the alerts) someone available to sign them. You will\n TYPE file (#8992.2).\n \n CROSS-REFERENCE:8992.111^B\n 1)= S ^XTV(8992.1,DA(2),20,DA(1),1,"B",$E(X,1,3\n 0),DA)=""\n \n 2)= K ^XTV(8992.1,DA(2),20,DA(1),1,"B",$E(X,1,3\n 0),DA)\n \n \nnot see alerts to inactive users from CPRS unless patch OR*3*200 (which will \n8992.111,.02 SENT TO SURROGATE 0;2 POINTER TO NEW PERSON FILE (#200)\n \n LAST EDITED: FEB 21, 2003\n HELP-PROMPT: This is the individual that was sent the\n alert in a surrogate capacity instead of the\n originally specified recipient.\n DESCRIPTION: This field is used to identify the surrogate\n to whom the alert was sent instead of this\n originally specified recipient.\n \nbe released shortly after this patch) has been installed.\n \n8992.111,.03 ACTING AS SURROGATE 0;3 SET\n \n 'Y' FOR YES;\n 'N' FOR NO;\n LAST EDITED: FEB 20, 2003\n HELP-PROMPT: Enter Y (YES) if this recipient received the\n alert acting as surrogate for another user.\n DESCRIPTION: This field is used to identify those\n recipients who were sent the alert\n \n \n because they were selected as an active\n surrogate for the originally intended\n user. In most cases only the Y (YES)\n entries will be entered.\n \n \n8992.111,.04 ALERT DATE/TIME 0;4 DATE\n \n INPUT TRANSFORM:S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X\n LAST EDITED: FEB 21, 2003\n*************************************************************************\n HELP-PROMPT: This is the date and time the alert was\n sent/forwarded to the current recipient with\n this recipient type\n DESCRIPTION: This is the date and time the alert was\n sent/forwarded to the current recipient with\n this recipient type\n \nThe following is the global map structure of the new multiple:\n \n^XTV(8992.1,D0,20,D1,1,0)=^8992.111PA^^ (#1) RECIPIENT TYPE\n \n^XTV(8992.1,D0,20,D1,1,D2,0)= (#.01) RECIPIENT TYPE [1P] ^ (#.02) SENT TO\n ==>SURROGATE [2P] ^ (#.03) ACTING AS SURROGATE\n ==>[3S] ^ (#.04) ALERT DATE/TIME [4D] ^\n \n \n \n8992.11,2 FORWARDED DATE/TIME 2;0 DATE Multiple #8992.112\n \n LAST EDITED: FEB 21, 2003\n \nIn the roll-and-scroll or List Manager environment, this patch causes\n8992.112,.01 FORWARDED DATE/TIME 0;1 DATE (Multiply asked)\n \n INPUT TRANSFORM:S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X\n LAST EDITED: FEB 21, 2003\n HELP-PROMPT: This is the date/time that the alert was\n forwarded to the current recipient\n DESCRIPTION: This field is used to track the date/time of\n forwarding of the alert to this recipient.\n This is a multiple field to track instances\n in which multiple copies of the alert may be\nalerts which contain the text "CRITICAL" or "ABNORMAL IMA" are displayed in\n forwarded to a single recipient for various\n reasons. This multiple field will indicate\n when it was forwarded and the basis for\n forwarding of the alert.\n \n CROSS-REFERENCE:8992.112^B\n 1)= S ^XTV(8992.1,DA(2),20,DA(1),2,"B",$E(X,1,3\n 0),DA)=""\n \n 2)= K ^XTV(8992.1,DA(2),20,DA(1),2,"B",$E(X,1,3\nreverse video to cause these alert to stand out in the midst of many other\n 0),DA)\n \n \n8992.112,.02 FORWARDING CATEGORY 0;2 POINTER TO ALERT RECIPIENT TYPE FILE\n (#8992.2)\n \n LAST EDITED: OCT 20, 2003\n HELP-PROMPT:This field points to a file containing the\n different reasons for forwarding.\n DESCRIPTION:This field is used to track the basis on which\nalerts.\n the alert is forwarded to the current\n recipient. The alert might be forwarded\n to the recipient by a user directly, or by\n programmed forwarding related to alerts not\n being processed within a specified time to\n EMAIL SURROGATE, CHIEF/SUPERVISOR; BACKUP\n REVIEWER, or LAST RESORT.\n \n Entries for this field are pointers to the\n values in the ALERT RECIPIENT TYPE file\n \n (#8992.2).\n \n \n8992.112,.03 FORWARDED BY OR FOR 0;3 POINTER TO NEW PERSON FILE (#200)\n \n LAST EDITED: APR 04, 2003\n HELP-PROMPT:This is the individual that forwarded the\n alert, or the alert was forwarded for.\n DESCRIPTION:This is a record of the individual who\n forwarded the alert, or on whose behalf the\nIt was found that sending an alert to a mail group, only the individual\n alert was forwarded if it was forwarded\n automatically.\n \n \n8992.112,1.01 FORWARDING COMMENT 1;1 FREE TEXT\n \n INPUT TRANSFORM:K:$L(X)>240!($L(X)<1) X\n LAST EDITED: FEB 20, 2003\n HELP-PROMPT:Answer must be 1-240 characters in length.\n DESCRIPTION:This is the comment which was sent to the\nmembers were identified. This has been modified to include other mail\n recipient along with the forwarded alert.\n \nThe following is the global map structure of the new multiple:\n \n^XTV(8992.1,D0,20,D1,2,0)=^8992.112D^^ (#2) FORWARDED DATE/TIME\n^XTV(8992.1,D0,20,D1,2,D2,0)= (#.01) FORWARDED DATE/TIME [1D] ^ (#.02)\n ==>FORWARDING CATEGORY [2P] ^ (#.03) FORWARDED BY\n ==>OR FOR [3P] ^\n^XTV(8992.1,D0,20,D1,2,D2,1)= (#1.01) FORWARDING COMMENT [1F] ^\n \nThis patch addresses a patient safety issue in which alerts sent to an\ngroups which are members of the mail group as well.\n \n \n \n8992.11,3 SURROGATE FOR 3;0 POINTER Multiple #8992.113\n \n \n8992.113,.01 SURROGATE FOR 0;1 POINTER TO NEW PERSON FILE (#200)\n (Multiply asked)\n \n LAST EDITED: FEB 20, 2003\n \n HELP-PROMPT:Enter the NEW PERSON entry for which the\n current recipient is acting as surrogate on\n this alert.\n DESCRIPTION:This field is used to track which user or\n users the current recipient is receiving the\n current alert while acting as surrogate.\n \n CROSS-REFERENCE:8992.113^B\n 1)= S ^XTV(8992.1,DA(2),20,DA(1),3,"B",$E(X,1,3\n 0),DA)=""\nThe XQAL UNPROCESSED ALERTS mail group is created by this patch and during\n \n 2)= K ^XTV(8992.1,DA(2),20,DA(1),3,"B",$E(X,1,3\n 0),DA)\n \n \n8992.113,.02 DATE/TIME - SURROGATE FOR 0;2 DATE\n \n INPUT TRANSFORM:S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X\n LAST EDITED: FEB 20, 2003\n HELP-PROMPT:Enter the date/time that this alert was\nthe Post-Init phase the individual installing the patch will be set up as\n received while acting as a surrogate for the\n intended recipient.\n DESCRIPTION:\n This field has the date/time when the alert\n was sent to the current recipient while\n acting as a surrogate for the originally\n intended recipient.\n \nThe following is the global map structure of the new multiple:\n \na member of the mail group. We recommend that this mail group be\n^XTV(8992.1,D0,20,D1,3,0)=^8992.113P^^ (#3) SURROGATE FOR\n^XTV(8992.1,D0,20,D1,3,D2,0)= (#.01) SURROGATE FOR [1P] ^ (#.02) DATE/TIME -\n ==>SURROGATE FOR [2D] ^\n \n \nNOISs\nMON-0902-51640\nLEX-1102-41218\nOKL-0902-71635\nHEH-0303-40570\npopulated with a few individuals who can forward otherwise undelivered\nDAY-0903-42005\nNYH-1003-11010\nMWV-1003-22265\nMWV-1003-22662\nSBY-1003-30092\nSBY-1003-32710\nASH-1203-30593\nHVH-0304-12467\nLEX-0803-41741\nSFC-1201-60229\nalerts on to a proper individuals.\nANN-0304-40985\nHIN-0604-40728\nISH-1202-41625\nDAY-0903-40490\nMAR-0304-20707\n \n \n \nE3Rs\n \n \nList of Test Sites\n==================\nBIRMINGHAM, AL (Alpha/DSM) \nCLARKSBURG, WV (VMS/Cache)\nDAYTON, OH (Alpha/DSM)\nFARGO, ND (Alpha/ISM (NT))\nLEXINGTON, KY (Alpha/DSM)\nNORTHERN CALIFORNIA HCS (Alpha/DSM)\nTOMAH,WI (VMS/Cache)\n \nAn option was earlier provided for establishing individuals as BACKUP\n \nRoutine Summary:\nThe following routines are included in this patch. The second\nline of each of these routines now looks like:\n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \nChecksums:\n==========\nChecksums obtained using CHECK^XTSUMBLD\nREVIEWER entries in the PARAMETER FILE, but the original option did not\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XQAL285P N/A 3472855 **285**\n XQALBUTL 8443097 23353614 **114,125,171,285**\n XQALDATA 3525117 3637657 **207,285**\n XQALDEL 26334655 21668304 **6,24,65,114,174,285**\n XQALERT 5560549 8063898 **1,65,125,173,285**\n XQALERT1 30919356 32870507 **20,65,114,123,125,164,173,285**\n XQALFWD 10746790 13242253 **6,65,91,111,114,128,129,285**\ninactive user were not received by anyone. If there are no active\nprovide an easy way in which to delete or edit the entry. This has been\n XQALSET 16240502 29403670 **1,6,65,75,114,125,173,207,285**\n XQALSET1 N/A 1679250 **285**\n XQALSURO 12681484 14207055 **114,125,173,285**\n \n \nList of preceding patches: 129,171,173,174,207\n \n \nBlood Bank Clearance:\n=============================\ncorrected in this patch.\nClearance - Mar. 19, 2004\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*285 \ncontains changes to a package referenced in VHA IO SEPG SOP 192-023 \n"Review of VISTA Patches for Effects on VISTA Blood Bank Software . This \npatch does not alter or modify any VistA Blood Bank software design \nsafeguards or safety critical elements functions.\n \nRISK ANALYSIS: Changes made by patch XU*8*285 have no effect on Blood \nBank software functionality, therefore RISK is none.\n \n \n \nInstallation Instructions:\n \n 1. Users ARE allowed to be on the system during the\n installation.\n \n 2. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\nThis patch also corrects undefined errors which occur sporadically at\n This option will load the KIDS (Kernel Installation and Distribution\n System) package onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. The patch has now been loaded into a transport global on your\n system. On the KIDS menu, select the 'Installation' menu and use\n the following options:\n Verify Checksums in Transport Global\n Print Transport Global\nDELETEA+7^XQALDEL and at DELA+1^XQALDEL.\n Compare Transport Global to Current System\n Backup a Transport Global\n \n Return to Programmers Prompt and use "D ^XPDKRN":\n Select KIDS OPTION: Install\n =======\n Install Package(s)\n Select INSTALL NAME: XU*8.0*285\n ==========\n \n \n Enter the Coordinator for Mail Group 'XQAL UNPROCESSED ALERTS': \n username\n ========\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n YES// NO\n ==\n \n 6. AXP Sites - Answer 'NO' to the question 'Want to MOVE\nFor Developers, a new input variable during generation of alerts is\n routines to other CPUs?'.\n \n 7. If the routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\nXQADFN. This value should contain the DFN value for the patient if the\nalert is patient related. Use of this variable will provide a more\nreliable indicator of the patient than that previously used (the second\nrecipients or surrogates among the list of specified recipients the alert\ncomma piece of the value of XQAID as used by CPRS).\n \n \n \nFor Developers this patch adds the following APIs as Supported References:\n \nThis patch creates a new entry point for setting up alerts. SETUP1^XQALERT\nis now recommended for creation of an alert. It is used in the form\n S RETVAL=$$SETUP1^XQALERT\nthe value returned is a string with the first '^'-piece a 1 if the alert\nwill be directed to the appropriate BACKUP REVIEWER as determined from the\nwas delivered to at least one valid recipient or 0 if the alert could not\nbe delivered. In the latter case, the variable XQALERR will be defined\nand contain a string explaining why the alert was not delivered. The second\n'^'-piece is the IEN in the Alert Tracking file for the alert and the third\n'^'-piece is the complete value of XQAID for the alert. The second or third\npiece values may be used by an application to retain a reference to the\nalert in the ALERT TRACKING file (#8992.1).\n \n \nThe original entry point SETUP^XQALERT for creating an alert did not\nPARAMETERS file. If there is no identifiable BACKUP REVIEWER entry, the\nreturn any indication if an alert was not deliverable for any reason. This\nentry point is still valid for backward compatibility, but no longer\nrecommended.\n \n$$ACTVSURO^XQALSURO(IENVALUE) - returns the currently active surrogate for\nthe user specified. This includes potential surrogates of the current\nsurrogate. To determine the currently active surrogate for the user with\nDUZ of IENVALUE, use\n S ACTIVE=$$ACTVSURO^XQALSURO(IENVALUE)\nIf the returned value is greater than zero, it will indicate the active\nalert will be sent to members of the "XQAL UNPROCESSED ALERTS" mail\nsurrogate. If the returned value is not greater than zero (actually -1),\nit will indicate that there are no currently active surrogates for the\nuser.\n \n$$CHEKUSER^XQALSET(IENVALUE) - Returns 0 if no valid user or surrogate,\notherwise returns IEN of user or his currently active surrogate\n \nAddition of the ALERT RECIPIENT TYPE file (#8992.2)\n---------------------------------------------------\n \ngroup. If there are no active members specified for that mail group, the\nThe ALERT RECIPIENT TYPE file was added to contain indicators as to why\nan alert was sent.\n \n8992.2,.01 NAME 0;1 FREE TEXT (Required)\n \n INPUT TRANSFORM: K:$L(X)>45!($L(X)<3)!'(X'?1P.E) X\n LAST EDITED: OCT 17, 2003\n HELP-PROMPT: Answer must be 3-45 characters in length.\n DESCRIPTION: This file is used to maintain a list of\n recipient types for alerts. It is used in\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8*275.\n\n\n\n
\nKernel Patch XU*8.0*340 Modify Option 'Person Class Edit. Please refer to\nthe Description in Forum Patch Module for details.\n\n
\nSee patch XU*8*330 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nKernel Patch XU*8.0*338 Fix Printing Alerts. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nThis patch adds changes and enhancements to the Unwinder (XQOR*) in support \nof the Text Integration Utilities (TIU) package. These changes include:\n\n 1) the ability to programmatically change the menu passed to XQOR\n 2) some modifications to the response time monitoring calls\n 3) the suppression of linefeeds when XQORM is called non-interactively\n 4) the ability to map numeric input to a protocol that should be run\n 5) the storage of HL7 messages in ^TMP to free up partition space\n\n
\nKernel Patch XU*8.0*342 'Option Access by User Fix'.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nKernel Patch XU*8.0*352 'NEW PERSON FILE MODIFICATIONS'.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8.0*268 in the National Patch Module on FORUM for complete \n \nAll DSM, Cache for Windows NT and Cache for OpenVMS sites are instructed \nto install this patch.\ninformation on this patch.\n \nThis patch is being released by Capacity Planning (CP) for installation of\nmodifications to the %ZOSVK* collection routines that are used by the \nStatistical Analysis of Global Growth (SAGG) Version 1.8 software package.\n \nNOTE: SAGG patch KMPS*1.8*3 must be installed AFTER installation of this\n patch.\n\n
\nSee patch XU*8*356 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*354 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*347 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n \nthis parameter will cause XUP, if the Select OPTION NAME: is skipped, to branch\n \n>>>Allow KIDS to Inhibit logon's during the install. \n>>>TaskMan does *not* need to be stopped. \n \n 1. DSM sites - If any of these routines are mapped, \n you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \nto the VPE environment. \n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n \n 4. Allow KIDS to Inhibit logon's during the install. (There is a small\n chance that a few users could get CLOBER errors.) \n TaskMan does not need to be stopped. \n \n 5. Installation will take less than 2 minutes. \n In Programmer mode: \n Use "D ^XPDKRN" then \n Install Package(s) 'XU*8.0*284' \n ==========\n \nNOIS: ISL-0103-52332 This Patch adds a new API in a new routine for\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES \n \n Want KIDS to INHIBIT LOGONs during the install? YES// YES \n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO \n \n 8. After installing this patch, \n Cache/GTM Sites - you don't need to move anything, skip this step. \n DSM sites - you need to move one routine from \n your production account to each manager account: ZOSVVXD \napplications to use to check and see if they are running in a PRODUCTION\n \n 9. DSM in the manager account, (Cache/GTM sites remain in VAH) \n All sites: \n DO RELOAD^ZTMGRSET \n Select the System \n Patch number to load: 284 \n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set. \n \naccount or a TEST account. Integration #: 4440 \n 11. In the VAH account: \n Please run the Memu option "Ask if Production Account" (XU SID ASK). \n This will ask if the current account is the Production account. \n Please answer acordinly. \n \n The Option "Startup PROD check" (XU SID STARTUP) should be scheduled \n for startup so that when TaskMan starts the SID is checked. \n=========================================================================\n \nThe new API is: \n $$PROD^XUPROD([force]) \n It returns 1 if the current account is a production account. \nPatch Tracking #: 37387952\n It returns 0 if it is a TEST account. \n \n The parameter value of 1, allows an application to force a full test. \n \nThese is a new Menu item under the "Kernel Management Menu", "Ask if Production\nAccount" (XU SID ASK) this option will ask if the current account is the\nProduction account. If the answer is "Yes" then the current SID is set as the\nproduction SID so checks will return 1. If account is not the production\naccount then a fake value is stored so that the check will return 0. The first\ncheck each day will force a full test. \nTest Sites: FORUM, NORTHERN CALIFORNIA HCS, Boston Healthcare System \n \nThe option "Startup PROD check" (XU SID STARTUP) should be added to the Taskman\nscheduling file and scheduled for startup so that when Taskman start the SID is\nalso checked. \n \nOther required patches: For GT.M sites, XU*8*275 has the needed change \nto ZOSVGTM. \n \nNew fields in the KERNEL SYSTEM PARAMETERS file (8989.3). \nSTANDARD DATA DICTIONARY #8989.3 -- KERNEL SYSTEM PARAMETERS FILE \n CPRS v25 t12 test sites. Blood Bank Clearance: 3/18/2004 \nSTORED IN ^XTV(8989.3, (1 ENTRY) SITE: SF CIOFO, KERNEL PATCH ACCOUNT \n \nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE \n-------------------------------------------------------------------------------\n \n8989.3,501 PRODUCTION SID;1 SET (Required) \n \n Production \n '0' FOR No; \n \n '1' FOR Yes; \n LAST EDITED: OCT 22, 2003 \n DESCRIPTION: This field holds a flag to indicate if this is \n a Production account. It is a Yes/No flag with \n internal values of 1 = Yes, 0 = No. It is set \n by the system after comparing the System ID \n with the current System ID, at some point in \n the future will be checked against a master \n system. \n \nThis patch adds two parameters to XUP with SYS or USR values that can be set to\n8989.3,502 System ID SID;2 FREE TEXT \n \n INPUT TRANSFORM: K:$L(X)>100!($L(X)<8) X \n LAST EDITED: OCT 22, 2003 \n HELP-PROMPT: Answer must be 8-100 characters in length \n DESCRIPTION: This field holds the SYSTEM ID, if this is a \n production system. This value is compared \n with the current system value and at some point \n in the future will be checked against a master \n system. \ncontrol XUP. The first is "XUS-XUP SET ERROR TRAP". If set this will set an\n \n \n8989.3,503 SID LAST CHECKED SID;3 DATE \n \n \n INPUT TRANSFORM: S %DT="ETX" D ^%DT S X=Y K:Y<1 X \n LAST EDITED: JUN 30, 2003 \n DESCRIPTION: This field holds the date/time that the SID was \n last checked. If the SID has not been \n compared with the stored one today a full \nerror trap to return to XUP and ask if the error should be recorded. The other\n check will be done, otherwise the PROD api will \n just return the current value. \n \n \nRoutine Summary The following routines are included in this patch. The second\nline of each of these routines now looks like: \n ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995 \n \n Checksum\nRoutine Old New Patch List\nis "XUS-XUP VPE" for users that like to work in the VPE environment, setting\nXUP 4983304 5169232 **208,258,284**\nXUPROD n/a 1670496 **284**\nZOSVVXD 7675098 8031174 **13,65,71,94,107,118,136,215,284**\nZOSVONT 6784414 6775555 **34,94,107,118,136,215,293,284** \n \nList of preceding patches: 215, 258, 293\nSites should use CHECK^XTSUMBLD to verify checksums. \n \n=========================================================================\nInstallation: \n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*363\n\n
\nThis is a reissue of Patch XU*8*14 without the code that requires the\npatch.\n\nChanges to the New Person file:\n Added a DEGREE field to hold MD, RN, LPN...\n Added a DATE E-SIG LAST CHANGED field. This field is just for on-line \n documentation purposes. Sites may use this field for local reporting \n and management, but the Kernel does NOT perform any action aside \n from updating the field when the E-sig is changed by the user.\n \nThe option XUSESIG BLOCK is included in this patch.\nusers to change their E-SIG every 90 days. You may install this patch\nThe forms XUEXISTING USER, XUREACT USER, and XUNEW USER are included in\nthe patch. The new field DEGREE has been added to the Forms.\n \nKERNEL functions to help developers.\n \n$$CHKSUM^XUSESIG1($name_value,flag)\nThis EXTRINSIC FUNCTION will take a root ($name_value) and build a\nchecksum for all data in the root. (Not used now, flag would be used when\nthere is more than one checksum algorithm.) \n\nwhether or not you previously installed XU*8*14. (Sites who installed\n$$ESBLOCK^XUSESIG1(ien)\nThis extrinsic function will return the set of fields from the new \nperson file that are needed as part of the hash for an acceptable E-Sig. \nIf IEN is not passed in, then DUZ is used.\n(E-Sig block, E-Sig title, Degree, Current Date/Time)\n \n$$EN^XUSESIG1(checksum,esblock)\nIf the ESBLOCK is not passed then the function would get the ESBLOCK. In \neither case this extrinsic function would encode the ESBLOCK using the \nchecksum as the KEY. Returns an encoded string. \nXU*8*14 prior to it being marked 'Entered in Error' were advised that they\n\n$$CMP^XUSESIG1(checksum,$name_value)\nThis extrinsic function will compare the checksum passed in to the \ncalculated value from the $NAME_VALUE. Return 1 for match, 0 for no \nmatch.\n \n$$DE^XUSESIG1(checksum,encoded_string)\nThis extrinsic function would decode the string using the checksum as \nthe key. Return a decoded string.\n \nneed not de-install the patch.)\n Routine Summary: \n ================\n \n The following routines are included in this patch. The second line of\n these routines now look like:\n \n ;;8.0;KERNEL;**[patch list]**;Date\n \n \n CHECK^XTSUMBLD results: \n\n \n Routine Name Before Patch 14 After Patch 14 After Patch Patch \nList\n ------------ --------------- -------------- ----------- --------\n XUSESIG 5534368 5865804 6027869 **14,55**\n XUSESIG1 N/A 864068 864068 **14,55**\n\n========================================================================= \nInstallation:\n \nThe new E-SIG functions allow developers to follow the General Counsel's\n1. Some of these routines are usually mapped on systems that allow\nmapping, so you will need to disable mapping for the affected routines.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n3. The patch has now been loaded into a Transport global on your system.\nYou now need to use KIDS to install the Transport global.\nOn the KIDS menu, under the 'Installation' menu, use the following\noptions:\nguidelines on E-SIG. The guidelines are the result of a meeting held in\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n4. Users can remain on the system. This patch can be queued and\ninstalled at any time. \n\n5. On the KIDS menu, under the 'Installation' menu, use the following\noptions:\nBirmingham on 9/18-20/95. A new routine, XUSESIG1, is included in this\n Install Package(s) 'XU*8.0*55'\n =========\n \n6. MSM Sites - Answer YES to the question 'Want to MOVE routines to other\nCPUs?'. Enter the names of your Compute and Print server(s).\n \n7. AXP Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\n\n\n
\nKernel Patch XU*8.0*351 Reactivate a User [XUSERREACT] Fix. \nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8*370 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch XU*8*328 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch XU*8*373 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch XU*8*360 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n This Kernel patch contains the following features:\n was queued and it got an error during install.\n===========================================================================\n\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no user should be using KIDS during the install of this patch.\n===========================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n-KIDS will now save Patch names that contain Sequence numbers in the\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n ==================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Patch Application History field of the Package file.\n Name Checksum Patch List\n -----------------------------------------------------------\n XPDIP 9952535 15,21,28,30\n XPDIR 2689416 30\n XPDV 9093649 30\n ============================================================================\n-KIDS will now check for duplicate Version numbers and Patch names when\n updating the Package file.\n-KIDS will now clean up missing Files in the Build file. This is done when\n using the 'Verify a Build' option.\n-Fixes problem in NOIS ELP-0596-70080, couldn't restart install if install\n\n
\n This patch contains a single routine, ^XQOO3, that fixes a bug in the\n This patch can be installed with users on the system. There are no\nassociated or required patches that need to be installed.\n \n=============================================================================\n \nINSTALLATION:\n \n 1. This routine is not usually mapped on systems that allow mapping.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\noption "Protocols Marked Out Of Order in Protocol File." In the event that\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\nthere was a single set of protocols marked as Out-Of-Order the software\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n \nROUTINES:\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Before After \nwould fail with an <UNDEF> error.\n Name Checksum Checksum Patch List\n -----------------------------------------------------------\nXQOO3 8090117 8314463 57 **57**\n \nAll checksums were calculated using CHECK^XTSUMBLD.\n \n===========================================================================\n \n=============================================================================\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n \n\n
\nSee patch XU*8*344 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*388 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n Patch XU*8*366 (RETURN ALERTS FROM SURROGATE) resolves a patient safety\n listing of alerts AND THERE ARE NO CURRENT SURROGATES (either due to the\n LAST EDITED: NOV 12, 2004\n HELP-PROMPT: This is the user who will be the surrogate\n during the time period specified\n DESCRIPTION: This is a pointer to the user in the NEW\n PERSON file who will be acting as the\n surrogate for the time period specified.\n \n \n 8992.02,.03 END DATE TIME 0;3 DATE\n \n end of the surrogacy period or removal of the last surrogate) alerts which\n INPUT TRANSFORM: S %DT="ESTX" D ^%DT S X=Y K:Y<1 X\n LAST EDITED: NOV 12, 2004\n HELP-PROMPT: This is an optional date/time for when the\n surrogate relationship will be terminated.\n DESCRIPTION: This is an optional date/time for when the\n surrogate relationship will be terminated.\n If there is no value entered, then the\n relationship will continue until it is\n specifically terminated.\n \n were sent to the surrogate(s) and have not been processed by the surrogate\n \n 8992.02,.04 NEEDS RETURN 0;4 SET\n \n '1' FOR YES;\n '0' FOR NO;\n LAST EDITED: MAR 16, 2005\n HELP-PROMPT: This is a flag which is used to determine\n whether alerts have been returned to the\n intended recipient or not\n DESCRIPTION: This field is used as a flag to indicate\n are returned to the user as new alerts with a comment indicating they were\n whether the alerts have been returned to the\n intended recipient or not.\n \n CROSS-REFERENCE: 8992.02^AC\n 1)= S ^XTV(8992,DA(1),2,"AC",$E(X,1,30),DA)=\n ""\n \n 2)= K ^XTV(8992,DA(1),2,"AC",$E(X,1,30),DA)\n 3)= This x-ref is used to track alerts needing\n return from surrogates\n returned from the surrogate. If the surrogate was not an intended\n This cross reference is used to identify\n periods for which any alerts forwarded to a\n surrogate have not been returned to the\n intended recipient.\n \n \n The following field was added to the sub-file for the SURROGATE FOR field (#3)\n of the ALERT TRACKING file (#8992.1):\n \n \n recipient of the alert(s), either as an initially specified recipient or\n \n 8992.113,.03 DATE-TIME RETURNED 0;3 DATE\n \n INPUT TRANSFORM:S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X\n LAST EDITED: MAR 16, 2005\n HELP-PROMPT:This is the date-time that the alert was\n returned to the originally intended recipient\n DESCRIPTION:\n This field is a record for the date-time that\n an alert for which this recipient was acting as\n by receiving the alert by forwarding from another recipient, the alert will\n a surrogate was returned to the originally\n intended recipient of the alert.\n \n \n In addition the AUD cross-reference was added to the ALERT DATE/TIME field\n (#.04) the sub-file associated with the RECIPIENT TYPE field (#1) of the\n ALERT TRACKING file (#8992.1).\n \n \n NOISs\n be deleted from the surrogate. If the surrogate was an intended recipient\n MIW-0704-40544 TIU ALERTS FOR ADDITIONAL SIGNER NOT REGENERATED\n ALT-0104-20049 Surrogate Setting\n \n E3Rs\n #19537, MULTIPLE SURROGATES\n #19178, DATE CHECK FOR SURROGATE ASSIGNMENT\n #17330, ALLOW MULTIPLE SURROGATES\n #16711, MULTIPLE SURROGATES FOR ALERT\n #16237, SELECTIVE SURROGATE DESIGNATION BY END-USER\n \n of the alert it will also remain with the surrogate.\n \n List of Test Sites\n ==================\nCLARKSBURG, WV\nPORTLAND, OR (C)\nPUGET SOUND HCS\nSALISBURY, NC\nWEST PALM BEACH, FL\n \n \n \n Routine Summary:\n The following routines are included in this patch. The second\n line of each of these routines now looks like:\n \n <tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \n Checksums:\n ==========\n Checksums obtained using CHECK^XTSUMBLD\n \n issue (PSI-04-036) by modifying the handling of alerts sent to surrogates\n A consequence of the modifications made to track the periods of surrogacy\n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XQA366PO N/A 1270650 **366**\n XQALERT 8063898 8345286 **1,65,125,173,285,366**\n XQALERT1 32870507 32133568 **20,65,114,123,125,164,173,285,\n 366**\n XQALSUR1 N/A 24977392 **366**\n XQALSUR2 N/A 4795616 **366**\n XQALSURO 14207055 21906288 **114,125,173,285,366**\n \n is the ability to add multiple surrogate periods with different start times.\n Checksums obtained using CHECK1^XTSUMBLD from XT*7.3*94 (new style)\n \n Rtn Nm Chksum Before Chksum After Patch List\n ------ ------------- ------------ ----------\n XQA366PO N/A 1749690 **366**\n XQALERT 15349948 16208814 **1,65,125,173,285,366**\n XQALERT1 79355953 77322571 **20,65,114,123,125,164,173,285,\n 366**\n XQALSUR1 N/A 65103748 **366**\n XQALSUR2 N/A 6279756 **366**\n The most recent active start time determines which of the surrogate periods\n XQALSURO 42941175 62950995 **114,125,173,285,366**\n \n List of preceding patches: 285\n \n Blood Bank Clearance:\n =============================\n Clearance - Apr. 21, 2005\n \n EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*366 contains\n changes to a package referenced in VHA OI SEPG SOP 192-023 Review of VISTA\n is active. Therefore, the termination date/time for a given period of\n Patches for Effects on VISTA Blood Bank Software. This patch does not\n alter or modify any VistA Blood Bank software design safeguards or safety\n critical elements functions.\n \n RISK ANALYSIS: Changes made by patch XU*8*366 have no effect on Blood Bank\n software functionality, therefore RISK is none.\n \n \n Installation Instructions:\n \n surrogacy, if specified, only determines the end of the surrogacy if no\n 1. Users ARE allowed to be on the system during the\n installation.\n \n 2. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.\n This option will load the KIDS (Kernel Installation and Distribution\n System) package onto your system.\n \n other surrogacy period starts prior to that time. It does not determine\n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. The patch has now been loaded into a transport global on your\n system. On the KIDS menu, select the 'Installation' menu and use\n the following options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n the actual end time if another period of surrogacy starts before the\n Return to Programmers Prompt and use "D ^XPDKRN":\n Select KIDS OPTION: Install\n =======\n Install Package(s)\n Select INSTALL NAME: XU*8.0*366\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\n specified end time (or there was no end time specified). A pair of\n YES// NO\n ==\n \n 6. AXP Sites - Answer 'NO' to the question 'Want to MOVE\n routines to other CPUs?'.\n \n \n 7. If the routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\n users can be specified in advance as mutual surrogates with opposite rolls,\n as long as the periods of surrogacy do not overlap resulting in a circular\n to return unprocessed alerts to the originally intended recipient of the\n relationship.\n \n In the Roll and Scroll environment, selection of Surrogate processing will\n list current surrogate(s) and give the option to remove one or more of the\n surrogates, and the option to add a surrogate, which if it is a later start\n date/time than a currently active or scheduled surrogate, will become active\n at the date/time specified.\n \n A new supported reference (SUROLIST^XQALSURO) has been added to provide a\n list of current and scheduled surrogates for a user.\n alert after a surrogacy period ends. As a byproduct of the changes made,\n \n D SUROLIST^XQALSURO(XQAUSER,.XQALIST)\n \n where XQALIST is passed by reference. On return XQALIST contains the\n number of entries returned, and an array containing the current and\n scheduled surrogates with '^'-separated values for internal entry number in\n the NEW PERSON file (#200), the value for the NAME field (#.01) from the\n NEW PERSON file (#200), the start date/time for the surrogacy period and the\n end date/time for the surrogacy period. If a surrogate has no end date/time\n value and is followed by another surrogate, the first surrogate will show an\n it is now possible to schedule multiple different (temporal) surrogate\n end date/time value equal to the start date/time of the following surrogate.\n \n returns XQALIST=count\n XQALIST(1)=IEN2^NEWPERSON,USER2^STARTDATETIME^ENDDATETIME\n XQALIST(2)=3^NAME,USER3^3050407.1227^3050409\n \n The supported reference to remove surrogates (REMVSURO^XQALSURO) has been\n modified to add two additional OPTIONAL arguments which specify the IEN of\n a surrogate and the start date/time for that surrogate session to be removed\n (these values can be obtained with the SUROLIST^XQALSURO call described\n periods in advance.\n above). If these two optional arguments are not specified, the call to\n REMVSURO^XQALSURO will remove the current or next scheduled surrogate entry\n (as it has in the past).\n \n These features will become active in windowed applications, such as CPRS,\n only after the applications implement code changes to take advantage of the\n new functionality included in this patch.\n \n The following field (and sub-file) was added to the ALERT file (#8992):\n \n \n 8992,2 SURROGATE 2;0 DATE Multiple #8992.02\n \n DESCRIPTION: This field is a multiple based on the start\n date/time for a surrogate relationship. This\n will permit multiple surrogate relationships\n to be scheduled.\n \n Since a start date/time for the surrogate\n relationship is required, if the user does not\n enter one, then the NOW as the current\n Alerts are sent to the specified surrogate, or surrogates if there is a\n date/time will be used.\n \n \n 8992.02,.01 SURROGATE START DATE/TIME 0;1 DATE (Required) (Multiply asked)\n \n INPUT TRANSFORM: S %DT="ESTX" D ^%DT S X=Y K:Y<1 X\n LAST EDITED: NOV 12, 2004\n HELP-PROMPT: This is the START DATE/TIME for the surrogate\n DESCRIPTION: This is the starting date and time for a\n surrogate relationship.\n sequence of consecutive periods of surrogacy. When a user requests a\n \n CROSS-REFERENCE: 8992.02^B\n 1)= S ^XTV(8992,DA(1),2,"B",$E(X,1,30),DA)=\n ""\n 2)= K ^XTV(8992,DA(1),2,"B",$E(X,1,30),DA)\n \n \n 8992.02,.02 SURROGATE USER 0;2 POINTER TO NEW PERSON FILE (#200)\n (Required)\n \n\n
\nKernel Patch XU*8.0*377, UPDATE PERSON CLASS FILE, Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nSee patch XU*8*398 in the National Patch Module for complete information\non this patch.\n\n
\nPlease see the National Patch Module for complete instructions.\nPatch XU*8*242.\n\n
\nSee patch XU*8*306 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8*339.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXU*8*265 3 Strikes and You Are Out\n\n
\n Prerequisites: none\n asked if the Build has an Environment Check Routine.\n\nSelect Installation Option: Compare Transport Global to Current System\n\nSelect INSTALL NAME: TEST 2.2 Loaded from Distribution 2/26/97@13:04:56\n => TEST ;Created on Feb 24, 1997@12:44:26\n\n Select one of the following:\n\n 1 Full Comparison\n 2 Second line of Routines only\n -FAV-1096-72757 Restarting an Install ignores the variable XPDNOQUE, when\n 3 Routines only\n\nType of Compare: 2 Second line of Routines only\nDEVICE: HOME// \n\n\n 3. When adding Options or Protocols to a Build, you now have 2 new 'Action\n Types': 4 ATTACH TO MENU and 5 DISABLE DURING INSTALL.\n ATTACH TO MENU should be used to attach an Option or Protocol that you\n are not exporting to a Menu you are exporting.\n the variable is set in an Environment Check Routine.\n DISABLE DURING INSTALL should be used to designate all the Options and\n Protocols that you are not exporting, but you want them put out of order\n during the install process.\n\n\n 4. When a Mail Group is exported with KIDS, the installing user will be\n asked for the Mail Group Coordinator when they use the install option.\n The Coordinator will only be added to the Mail Group if the Mail Group\n is new or there is currently not a Coordinator. The Mail Group Coordinator\n is optional.\n -The Option 'Compare Transport Global to Current System' will now let you\n\nEXAMPLE:\nSelect Kernel Installation & Distribution System Option: Installation\n\nSelect Installation Option: Install Package(s)\nSelect INSTALL NAME: TEST 2.2 Loaded from Distribution\n\nThis Distribution was loaded on Feb 27, 1997@08:11:04 with header of \nTEST ;Created on Feb 24, 1997@12:44:26\nIt consisted of the following Install(s):\n compare just routines or just the 2nd line of routines.\nTEST 2.2\n\n TEST 2.2\n\nInstall Questions for TEST 2.2\n\nIncoming Mail Groups:\n\nEnter the Coordinator for Mail Group 'HL7': DIMICELI,RON RD \n\n -An Option or Protocol can now have an 'Action Type' of 'ATTACH TO MENU' or\nEnter the Coordinator for Mail Group 'RON TEST': \n\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// \n\n\n 'DISABLE DURING INSTALL'.\n -The user will now be prompted for the Mail Group Coordinator if an Install\n is sending Mail Group(s).\n -Developers can now send Options and Protocols with the OUT OF ORDER MESSAGE\n=========================================================================== \n field already set. The Options and Protocols will remain out of order after\n the install has completed.\n\n=============================================================================\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n\n This patch can be installed with users on the system, but no other users\n should be using KIDS while you install this patch.\n Since this patch is an update to KIDS, no other patches should be installed\n This patch contains the following features and corrections:\n during the installation of this patch.\n=============================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n -An undefined error when installing data and the user said 'NO' to install\n global.\n 4. Users can remain on the system. This patch can be queued and installed\n at any time. TaskMan can remain running.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n the Data Dictionary. Since the Data Dictionary is not present, the user\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n \nROUTINES:\n Checksums obtained using CHECK^XTSUMBLD\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n gets an error.\n Before After Patch\nRoutine Checksum Checksum List\n----------------------------------------------------------------------\nXPDCOM 2299089 5277873 21,58\nXPDET 5054366 5058369 15,39,41,44,51,58\nXPDH 2594827 3370027 58\nXPDI 17816610 13319818 10,21,39,41,44,58\nXPDI1 new 6631631 58\nXPDIA 12898389 13293339 10,15,21,28,44,58\nXPDIA1 7754922 7937994 2,44,51,58\n -Duplicate FileMan templates were not being installed, even if they were\nXPDIB 2632713 2753452 10,58\nXPDIK 10192795 14344733 15,58\nXPDIL 10583214 11156235 15,44,58\nXPDIP 9769805 9760615 15,21,28,30,41,44,51,58\nXPDIQ 6693337 7513883 21,28,58\nXPDIR 2689416 2964712 30,58\nXPDIU 7856776 8165680 15,41,44,51,58\nXPDT 19179554 19247892 2,10,28,41,44,51,58\nXPDTA 7419894 7580607 15,44,58\nXPDTC 12862739 13401215 10,15,21,39,41,44,58\n for two different files.\nXPDV 9865255 11643577 30,44,58\nXQOO1 14519526 14826502 10,21,39,41,58\n===========================================================================\nDOCUMENTATION:\n 1. PARTIAL DD: BUILD #9.6\n SUB DD: ENTRIES #9.68\n FIELD: ACTION #.03\n 0 SEND TO SITE\n 1 DELETE AT SITE\n 2 USE AS LINK FOR MENU ITEMS\n -The question, 'Want to RUN the Environment Check Routine', will only be\n 3 MERGE MENU ITEMS\n 4 ATTACH TO MENU\n 5 DISABLE DURING INSTALL\n\n\n 2. The 'Compare Transport Global to Current System' will now let you compare\n just the Routines or just the 2nd line of the Routines.\n\nEXAMPLE:\nSelect Kernel Installation & Distribution System Option: Installation\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8.0*337 SSO/UC Kernel support.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*391 Limit %ZIS page length.\n\n
\nKernel Patch XU*8.0*361 Proxy Application User for Rehosting effort.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8*350 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*400 New String Functions SENTENCE and TITLE.\n\n
\nSee patch XU*8*386 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*392 Error trap adds quotes to arrays.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*409 Fix when close execute changes IO.\n\n
\nKernel Patch XU*8.0*411. Please refer to the Description in Forum Patch\nModule for details. \n\n
\n PREREQUISITES: XU*8.0*58\n=============================================================================\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n\n This patch can be installed with users on the system, but no other users\n should be using KIDS while you install this patch.\n Since this patch is an update to KIDS, no other patches should be installed\n during the installation of this patch.\n=============================================================================\n \n============================================================================\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the affected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 4. Users can remain on the system. This patch can be queued and installed\n at any time. TaskMan can remain running.\n\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\n This patch corrects two errors that was introduced in patch XU*8.0*58.\n===========================================================================\n \nROUTINES:\n Checksums obtained using CHECK^XTSUMBLD\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After Patch\n Routine Checksum Checksum List\n ----------------------------------------------------------------------\nISA-0497-1-448 An undefined error occurred at DIR+19^XPDIQ if the installing\n XPDIQ 7513883 7519323 21,28,58,61\n XPDI1 6631631 6640407 58,61\n===========================================================================\n package asks an question without having a default answer.\nWhen moving routines to other CPUs and the install is not queued, the job on\n the other CPU will show the message, "Can't Lock global, another XPDCPU must\n be running".\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*395 HealtheVet CCOW follow-up.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*415 Undefind error in %ZTLOAD1.\n\n
\nSee patch XU*8*413 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*378 in the National Patch Module for complete information\non this patch.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8*385 Cache HFS parameter update.\n\n
\nKernel Patch XU*8.0*384. Please refer to the Description in Forum Patch \nModule for details.\n\n
\nSee patch XU*8*329 in the National Patch Module for complete\ninformation on this patch.\n\n
\nThe routine ORBSTAT was transported as a part of Kernel 8.0 to insure that\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n 2. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'\n 3. From the 'Installion Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n 4. Inhibit users from login into the system. (If you install when few\n user are on the system and the posibility of some CLOBER errors is\nthe alert statistics would perform correctly with the movement of alert\n acceptable then users can stay on the system.)\n 5. From the 'Installion Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'XU*8.0*7' and proceed with\n install.\n 6. Enable user's login if inhibited.\n========================================================================= \ndata from file 200 to file 8992. Unfortunately, a couple of references to\nfile 200 were not converted, resulting in no output for the total alert\ncount. This patch includes correction of these references within the\nroutine and a print template for file 8992 which is used by this routine.\n \n========================================================================= \nInstallation:\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*353 TMP global clean-up changes.\n\n
\nXU*8*420 - Please refer to the patch description in FORUM for details\n\n
\nSee patch XU*8*426 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nThis patch is part of the Broker Security Enhancement (in conjunction \nwith patch XWB*1.1*45).\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8*404.\n\n\n
\nXU*8*393 KIDS HFS checksums to FORUM.\nPlease refer to the Description in the FORUM Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*419 C&A Remediation by pre-expiring new verify code.\n\n
\nKernel Patch XU*8.0*410 APIs' NPI. \nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8*357 in the National Patch Module for complete\ninformation on this patch.\n\n
\n This patch contains the following fixes and features:\n=============================================================================\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n\n This patch can be installed with users on the system, but no other users\n should be using KIDS while you install this patch.\n Since this patch is an update to KIDS, no other patches should be installed\n during the installation of this patch.\n=============================================================================\n \n - MUS-0497-71493 A no label error when installing patch XU*8*58 on an\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the affected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 4. Users can remain on the system. This patch can be queued and installed\n at any time. TaskMan can remain running.\n Open M system.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\n - The National Package install module on FORUM can now track patches.\n===========================================================================\n \nROUTINES:\n Checksums obtained using CHECK^XTSUMBLD\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After Patch\n Routine Checksum Checksum List\n ----------------------------------------------------------------------\n KIDS will now be able to update the module for patches.\n XPDET 5058369 5059212 15,39,41,44,51,58,66\n XPDIL1 8511833 8519937 15,17,39,41,44,66\n XPDIST 2343711 2400065 66\n XPDT 19247892 19357441 2,10,28,41,44,51,58,66\n===========================================================================\n - Corrects a problem with multi-builds. When a multi-build contains more\n build names that can fit on one header line, a second header line is\n create. The first build on the second line will begin with a colon, this\n will prevent the build from being installed.\n\n
\nCache Taskman with DCL environment.\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XU*8.0*355\n\n
\nKernel Patch XU*8.0*427 Jumping Fixed. Please refer to the Description in\nForum Patch Module for details.\n\n
\nSee patch XU*8*430 in the National Patch Module for complete\ninformation on this patch.\n\n
\nSee patch XU*8*428 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*436 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nPatch XU*8*435 (FIX SPOOLER PRINT FOR NPI LISTS)\n \nSee Description in the patch module on Forum.\n\n
\nKernel Patch XU*8.0*369 Compare local/national checksums.\nPlease refer to the Description in Forum Patch Module for details. \n\n
\nExtract data related to the New Person (#200), Institution (#4), and IB \nNon/Other VA Billing Provider (#355.93) files related to entries with a \nvalid NPI on file.\n\n
\nPLEASE NOTE: Sites currently testing Broker version T9 or who have\nEdit,' the field 'RESOURCE SLOTS' would get reset to 1. The patch\nXUS 7592994 7619050 **16,26,49**\nXUSERNEW 6789632 6995154 **16,49**\nXUTMK 6472549 6514964 **49**\nXUTMRJD 6336192 6554859 **49**\nZIS1 9986473 10316454 **18,49**\nZIS4MSM 6649854 7202298 **23,36,49**\nZIS4VXD 8342152 8150990 **23,36,49**\nZIS6 9961139 9917028 **24,49**\nZISC 8463272 7980129 **24,36,49**\nZISHMSM 5354551 5354575 **24,36,49**\nresolves this by performing changes to the DD.\nZOSVMSM 11524674 11538678 **13,25,49**\nZTER1 5603505 5664740 **18,24,36,49**\nZTLOAD5 4735916 **49**\nZTMS1 6234917 6234917 **36,49**\nZTMS3 9454395 9603212 **1,18,36,49**\nZUMSM 2237614 2252648 **13,42,49**\n \n========================================================================= \nInstallation:\n \n \n 1. Some of these routines are usually mapped on systems that allow \n mapping, so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\nISL-1196-50019 When a system crashes, resources are left\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from logging into the system.\n Also place TASKMAN in a wait state.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\nand still allocated, preventing new jobs from starting. This patch\n options:\n Install Package(s) 'XU*8.0*49'\n =========\n \n 6. MSM Sites - With Taskman not working you need to move the routine to\n other CPU's with the D ^XPDCPU\n MSM Sites - On each cpu rename ZUMSM to ZU with: ZL ZUMSM ZS ZU\n \n 7. After installing this patch, you need to move several routines from \n your production account to each manager account:\nprovides a new option that can release all resources at startup (Clear all\n ZIS1\n ZIS4MSM\n ZIS4VXD\n ZIS6\n ZISC\n ZISHMSM\n ZOSVMSM\n ZTER1\n ZTLOAD5\n ZTMS1\nResources) and also an option to release a given slot on a resource (Clear\n ZTMS3\n \n And in the manager account,\n \n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 49\n ==\n Move these MGR routines to your other CPU's.\n \none Resource). New routine XUDHRES, change to ZIS6, ZISC.\n 8. AXP Sites, after patch has installed, rebuild your map set.\n \n 9. Enable user's login.\n Remove TASKMAN from the wait state.\n \n =========================================================================\n \nMUR-0196-30539-XQ33 The option to delete unreferenced options\ninstalled a test version of XU*8*59 will need to reinstall XU*8*59 after\nfrom the option file didn't check for options used in the new TaskMan\nSchedule file. Added field 209.2 (KEEP FROM DELETING) to the option file.\n \nCTX-0297-70559 It was possible to get an earlier entry with\nthe Effective Date greater than the next entry. This caused problems when\nprogrames tried to find the current person class. Fixed with a change to\nthe DD so only greater dates are allowed. \n \n \nCHANGES MADE IN RESPONSE TO REQUESTS:\ninstalling this patch.\n \nWhen using the RJD option to stop a TaskMan job, you used to have to\nDISPLAY the task before you could delete it. Modification to routine\nXUTMRJD was made to allow site to say NO to the display and still delete\nthe task from the running task list. MSG 1060759 (Pete Tichenor)\n \nRemoves the testing for MWAPI from ZUMSM. (Trouble calls)\n \nHave XUS display the Node the user is on. Changed the XUS routine to\ndisplay the Volume-set:Node rather than just the Volume-set alone.\n \nChanged the first read to include output text as before in order to flush\nthe input buffer on certain systems, such as MSM. (E3R 8568)\n \nCleans-up pointers to files 3,6,16,20 in sort and print templates. It\nadds checks to code of XUSERNEW, XUA4A7 so they are ready for file\n3,6,16,20 cleanup.\n \nCleans up cross-references in files DEVICE, OPTION, and KERMIT HOLDING.\n \nINVALID LOCK - This patch adds a timeout to the one lock without one.\nThis patch fixes the following NOISs and REQUESTS:\nRoutine XUTMK was modified to resolve this problem. (E3R #9278)\n \nUpdates the ID nodes of files 3.2 and 3.5 to use DDIOL. Routine XUINPCH\n \nCorrects a problem with the status code returned by STAT^%ZTLOAD. It\nformerly returned "Inactive: Interrupted" when it should have returned\n"Active: Running". Fixed with changes to %ZTLOAD5.\n \nChanges a call in %ZTMS3 from ZSYNC to PURGELST^%MSMOPS on MSM 4.3\nsystems. In response to a request from MSM.\n \n \nChanges the way ZTMS1 waits under load.\n \nChanges %ZIS4 to clean up the IO("ERROR") and IO("LASTERR") variable.\n \nThis patch made a change to the setting of IO("ZIO"). ZIS4VXD, ZIS4MSM.\n \nChanges PRIORITY code to keep jobs from assuming system priority.\n(Capacity Management ZOSVMSM) \n \n NOIS Description of fix: \nFix $$STATUS^%ZISH not looking at the correct variable.\n \nImproves the $STACK reporting on DSM systems.\n \nAdds the following new entry point for modifying resource devices (please\nsee the Supported References file for full details):\n$$RES^XUDHSET(device_name,resource_name,slot_count,description,subtype)\n device_name For the resource device.\n resource_name (optional) The resource name if not the same as the device\n name.\n \n slot_count The number of concurrent jobs that can use this device.\n defaults to 1.\n description The device description, defaults to 'Resource Device'.\n subtype The subtype to use, defaults to P-OTHER.\n returns If an error '-1^text'\n The 'IEN^device name' like a DIC call.\n \n \n \nRoutine Summary:\nLAS-1196-60534 When using the option 'Resource Device\n================\n \n Checksum\nRoutine Old New 2nd Line\nXQ33 8337880 8946889 **49**\nXUA4A7 5092665 5114645 **49**\nXUA4A72 2742817 3400179 **27,49**\nXUDHRES 917964 **49**\nXUDHSET 1534104 **49**\nXUINPCH 1467475 2465171 **20,36,49**\n\n\nXU*8.0*452 patch to patch XU*8.0*438 and patch XU*8.0*410\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*381 Update Task Display with message data.\n\n
\nSee patch XU*8*444 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*449 in the National Patch Module on FORUM for complete \ninformation on this patch.\n\n
\nKernel patch XU*8.0*454; Fix the option 'Add/Edit NPI values for \nProviders'. Please refer to the Description in Forum Patch Module for\ndetails.\n\n
\nKernel patch XU*8.0*450 Input Transform for Person Class.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*437 XUSESIG and other small fixes.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*414 (0045-FY06 ISS Maint.XU.04.045-XU414) E@time bad reschedule\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*425 XLFNSLK clobbers IO.\n\n
\nNumerous Kernel fixes.\n\n\n
\nKernel patch XU*8.0*459; Enhance the option 'User Inquiry'.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8.0*463 "Change default answers in KIDS."\n\n
\nKernel patch XU*8.0*462; Fix the option 'Print Local NPI Reports'.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8.0*468 in the National Patch Module for complete\ninformation on this patch.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*455 Error in %ZTER on GT.M/DSM\n\n
\nKernel patch XU*8.0*465; DIERR Leak - Output Transform Field #12.3\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*372 Fix three slash stuff of DUZ.\n\n
\nKernel patch XU*8.0*467; NPI Phase II Modifications. Please refer to the \nDescription in Forum Patch Module for details.\n\n
\nPatch XU*8.0*453, NPI Phase II enhancements.\n\n
\nThis is the Auto Sign-on patch (aka Single Sign-on)\nAll of this work is in support of RPC Broker, CPRS and GUI clients.\n\nThere were some other fixes that had been applied to the routines and \nfiles needed by this patch so they are also fixed.\n To the "Enter/Edit Kernel Site Parameters" form;\n Added the AUTO SIGN-ON field to page 1,\n Added the DEFAULT DIRECTORY FOR HFS field to page 3.\n\n File 3.081 Field 1 changed from 15 to 30 characters.\n \nThis patch has several Kernel routines as well as new fields in the Kernel\nWBP-0396-20726 XQ1 The setting of DIPCRIA, DIASKHD, and DISUPNO was not\n correct and has been fixed.\n \nDAY-0697-41746 XQ1 Startup Options Getting Deleted in file 19.2\n\nE3R #10159, File 200 Field 20.2 changed from 30 to 40 characters. \n\n Checksum\nRoutine Old New 2nd Line\nXQ1 11726256 **1,15,59**\nSystem parameteres file and the New Person file and the forms to edit\nXQ82 3479466 **59**\nXQT1 10251041 **59**\nXUINENV 713144 **59**\nXUS 8138431 **16,26,49,59**\nXUS1 8848266 10420726 **9,59**\nXUS1B 1917370 **59**\nXUS2 14055468 **59**\nXUSCLEAN 6326709 6583467 **13,59**\nXUSRB 2961367 4666750 **11,16,28,32,59**\nXUVERIFY 3907067 3888236 **2,26,59**\nthese files. PLEASE be sure to edit the AUTO SIGN-ON field in the Kernel\nZIS4MSM 6649854 7202298 **23,36,49,59**\nZIS4ONT 8238234 **34,59**\nZIS4VXD 8342152 8151150 **23,36,49,59**\nZISTCP 2230177 2687385 **36,34,59**\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines.\nSystem parameters file. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into system. \n Also place TASKMAN in a wait state.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*59'\n*** This patch will increase the use of the LOCK table ***\n =========\n \n 6. DSM/MSM Sites - Move the following two routines to the MGR account.\n ZIS4MSM\n ZIS4ONT\n ZIS4VXD\n ZISTCP\n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n*** NOTE THAT AUTO SIGN-ON DOES NOT WORK ON MSM SYSTEMS ***\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 59\n ==\n \n 8. DSM Sites, after patch has installed, rebuild your map set.\n 9. Enable user's login.\n Remove TASKMAN from the wait state.\n\n=========================================================================\n\n\n\n
\nPatch XU*8*439 MODIFICATION OF BSE TO USE HTTP/1.0\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*432 "XUP Clean-up."\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*434 Set DILOCKTM in Kernel.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nKernel Patch XU*8.0*365 Clean Up Invalid Nodes for Security File. \nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nKernel patch XU*8.0*487; New Taxonomy Codes for Person Class file. Please\nrefer to the Description in Forum Patch Module for details.\n\n
\nSee the description for patch XU*8*483 in the patch module on Forum.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*440 Modifications for mixed VMS/Linux.\n\n
\n \nIt was found that the Broker sign-on were allowed even when Logon were\ninhibited.\n \nBoth problems fixed by patching XUSRB\n \nSFC-1197-61181 XUSRA The SQLI interface was making use of a call in\n XUSRA that called an entry point in XUS that had \n chaged with patch 59. This is now fixed.\n \n Checksum\n*** Patch XU*8*59 MUST be installed before this patch ***\nRoutine Old New 2nd Line\nXUSRA 1213791 1890066 **70**\nXUSRB 4666750 5125201 **11,16,28,32,59,70**\n \n========================================================================= \nInstallation:\n \n 1. DSM sites - One of these routines may by mapped,\n so you will need to disable mapping for the effected routine. \n \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\nA problem was found when using a Broker v1.0 application on Windows 95\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\n Stop the Broker listener to prevent the possibility of some CLOBER\n errors.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*70'\nand server side has Broker v1.1 with Auto sign-on. The 16bit app will\n =========\n \n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n \n 7. DSM Sites, after patch has installed, rebuild your map set.\n \n 8. All sites, Restart the Broker listener.\n =========================================================================\nprevent the server from contacting the ClientAgent, this will cause the\n16 bit PCMM to time-out and close the sign-on.\nThe fix is to disable the auto sign-on if the client is Broker v1.0\n \n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nSee the description on the patch module on FORUM.\n\n
\nKernel XU*8*478; Rebuild Menu Tree Fixed. Please refer to the Description \nin Forum Patch Module for details.\n\n
\nThis Kernel patch XU*8.0*503; See If a User Access to an Option.\nPlease refer to the Description in Forum Module for details.\n\n
\nSee the patch description on Forum.\n\n
\nPlease see FORUM patch module for details.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n\n\n\n\n
\nThis patch contains enhancements and modifications to the XUS NPI EXTRACT\n currently scheduled Task Manager task (which was set up by site\n Information Resource Management (IRM) staff with the installation of\n patch XU*8.0*453) which automatically runs the extract every three\n months.\n \n2. This patch addresses an issue found with sites that did not choose to\n install the PSO*7.0*273 patch. Any such sites were receiving a\n <NOROUTINE> error when attempting to run the extract (See Remedy Ticket\n 217164 below). A solution has been included which will prevent this \n error from occurring.\nREPORT [XUS NPI EXTRACT] option which is already loaded at the sites. The\n \n3. This patch also changes both the format of and the number of \n verification messages that get sent when the XUS NPI EXTRACT REPORT\n option [XUS NPI EXTRACT] is run. Currently, a verification email\n message is sent to each member of the "NPI EXTRACT VERIFICATION" mail\n group for each extract mail message that is created. With the\n installation of this patch, only one verification message will be\n created and sent to each member of the "NPI EXTRACT VERIFICATION" mail\n group.\nchanges contained in this patch address the following:\n \n1. With the installation of this patch, an approved Chief Business Office\n (CBO) staff member (with a valid network user identification and \n password), shall have the ability to remotely schedule the XUS NPI\n EXTRACT REPORT [XUS NPI EXTRACT] option to run at each selected site \n on a chosen date or dates. This new functionality will replace the\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nKernel patch XU*8.0*508; Error on the 'Option Access by User'.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nEnhancements to Unwinder routines (XQOR*) in support of CPRS 1.0\n were allowed, the user erroneously entered something like 1-4B,\n and then typed a return at 'For entry 1-4B enter: ".\n \n 3) Added "E" as a flag for XQORM(0). It will allow ambiguous lookups\n to be resolved interactively when XQORM is called without XQORM(0)\n containing an "A".\n \n 4) Made a change that sets full screen earlier when being called by\n list manager so that selection lists are properly displayed.\nThese enhancements include:\n \n 1) A new parameter which may be passed to XQORM - XQORM("ALT")\n This allows the calling routine to supply an alternative lookup\n to be used if the user types something that does not appear on\n the menu.\n \n 2) Fixed a bug that caused the menu to be exited if numeric ranges\n\n\nPlease see the National Patch Module for complete instructions.\nPatch XU*8*399.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nSee patch XU*8*401 in the National Patch Module for complete information.\n\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*499 Get Client IP when connecting via SSH.\n\n
\nPlease see the patch description in the Patch Module on FORUM.\n\n\n
\nKernel patch XU*8.0*497; Update Person Class file. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n
\nNOIS DAY-0196-40185 If the listing of Unsuccessful Tasks was queued to\nMSG# 19794130 From Dave Alexander. This message asked for EN^XUTMDEVQ \nto not new POP so that the calling routine can check the status. \n \nA long standing requests to display more info on running tasks that have\ndeleted there entry in the %ZTSK global.\n \nNOIS CLE-1195-40343 In the "Grant Access by Profile" option. Secondary\nMenu items that were in common with current secondary menu items would\nget duplicated. This has been fixed be adding a "B" X-ref to the\nSecondary Menu subfile. A post init will re-index this new X-ref on\na printer it would cause a extra blank page on the printer.\ncurrent entries. The adding of this B X-ref made it necessary to make\nchanges to other XQ routines that loop through the secondary menu list.\n \nNOIS BUT-1295-20458 BOS-0496-10026\nIn the "Grant Access by Profile" option. The \ndeletion of Keys, Files and Secondary options didn't work. If this\noption was run twice in a row it would not use the new template user.\nThis would only happen if the job wasn't queued. This has been fixed.\n \nNOIS --- The entry point EN^XQH leaves the variable XQH behind. This can\n \ncause problems if the user goes back into XQH. The change kills XQH at\nthe exit from the EN^XQH call.\n \nMSG# 19316051 It has been pointed out that files 4 and 49 are missing\nthe data type flag from the second piece of the .01 field. The .01 field\nfor both files is included.\n \nIt was pointed out that the QUEUED TO RUN ON VOLUME SET field in the \nOPTION SCHEDULING file would not allow the use of the NODE syntax\nthat is allowed in the DEVICE file.\nNOIS NAS-1295-30824 Entering a ^ to exit from a listing of tasks being\n \nDAY-0196-42100, HUN-1195-21343, BRX-1095-12548\nAfter a user process all the alerts, it still asks to process alerts even \nthough there no more alerts. it is nuisance. Why it happening? in XQALERT1 \nDOIT+8 it checks for the values XQX1 and XQAROU. After all alerts are \nprocessed, XQX1 is cleaned up properly but not XQAROU. \n \n \nroutine new checksum\nXQ12 17600046\nrequeued would cause an UNDEF error.\nXQALERT1 19524336\nXQH 8473100\nXQLOCK 12699105\nXQT 13634679\nXQTOC 9046523\nXUSERBLK 10269237\nXUTMG19 3660168\nXUTMD1 2754306\nXUTMDEVQ 268897\nXUTMQ 8141476\n \nXUTMRP 15458022\nXUTMTP 10672535\nXUTMTP1 5115647\nXUTMTPD 6357425\nXUTMTPU 5891396\nXUTMUTL 2233454\n \n========================================================================= \nInstallation:\n \nMSG# 18395346 From Dave Alexander. If in the Delete tasks option a "^" \n 1. These routines may be mapped on systems that allow mapping, \n if so you will need to disable mapping for the effected routines. \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'\n 4. From the 'Installation Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n 5. Users can be on the system.\nwouldn't stop the listing.\n 6. From the 'Installation Menu' of the KIDS menu, run the option\n 'Install Package(s)' Select the package 'XU*8.0*20' and proceed with\n install.\n Their is a POST-INIT that will run to build a B X-ref for the\n Secondary menu in the New Person file.\n 7. If you are a MSM site move the routines to the other servers. \n On a mapped system, rebuild your map set. \n \n \n=========================================================================\n \n\n
\n=============================================================================\n E3R #10306.\n -Protocols will now delete properly at the site.\n -The variable XPDABORT will correctly abort the install in both the Pre &\n Post install routines.\n -The variable DIR is newed before call to environment check routine.\n ISW-0597-21778\n\n=============================================================================\nROUTINES:\n Checksums obtained using CHECK^XTSUMBLD\n ****** This patch must be QUEUED during the install process ******\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After Patch\nRoutine Checksum Checksum List\n----------------------------------------------------------------------\nXPDDP 11584192 11970878 **21,28,44,68**\nXPDE 15041471 15253053 **2,15,21,44,51,68**\nXPDI 13319818 13691537 **10,21,39,41,44,58,68**\nXPDIA 13293339 13299802 **10,15,21,28,44,58,68**\n=============================================================================\nXPDIA1 7937994 9226085 **2,44,51,58,68**\nXPDIA2 3520152 6372331 **68**\nXPDIJ 10173098 10435806 **2,21,28,41,44,68**\nXPDIJ1 8772642 9316977 **41,68**\nXPDIL 11156235 11193690 **15,44,58,68**\nXPDIL1 8519937 9389594 **15,17,39,41,44,66,68**\nXPDIPM 1817853 1853883 **21,28,68**\nXPDT 19357441 18817747 **2,10,28,41,44,51,58,66,68**\nXPDTA1 4760350 4948004 **44,68**\n=============================================================================\n\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n\n This patch can be installed with users on the system, but no other users\n should be using KIDS while you install this patch.\n Since this patch is an update to KIDS, no other patches should be installed\n during the installation of this patch.\n\n ****** This patch must be QUEUED during the install process ******\n\nThis patch contains fixes that were identified by mail messages and E3R\n===========================================================================\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 4. Users can remain on the system. This patch can be queued and installed\n -A patch will not be installed if the site is not running the correct version\n at any time. TaskMan can remain running.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n INSTALL NAME: XU*8.0*68\n =========\n for the package.\n 6. At the device prompt, make sure you queue the install:\n DEVICE: HOME// QUEUE TO PRINT ON\n =\n 7. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n -Multiple Build definition will now be sent to the site, along with all the\n builds that make up the Multiple Build.\n\n
\nKernel patch XU*8.0*509; New Taxonomies.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8*451 in the National Patch Module for complete\ninformation on this patch.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n
\nKernel patch XU*8.0*489; DEACTIVATE A USER & KEYS. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*469 Maintain Institution in Auto Sign-on.\n\n
\nXU*8*466 "Visitor add to NPF update."\nPlease refer to the Description in the FORUM Patch Module for details.\n\n
\nKernel patch XU*8.0*475; Error When Replicating A User. Please refer to \nthe Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*518 Several small fixes.\n\n
\nThis patch was requested because of different errors that needed to be \nSites can add their own entries to the file. There is a field to allow\nthe advanced strings that Taskman has been using. Current entries in\nTaskmans error screen file are moved to the new file as part of the\ninstall.\n\n Checksum\nRoutine Old New 2nd Line\nXTER 17066911 17970380 **63**\nXTER1A 16667281 16315266 **63**\nXUINPCH 2465171 3137390 **20,36,49,63**\nscreened at the OpenM site.\nXUTMKE1 5103401 3519416 **63**\nXUTMKE2 9221275 2696336 **63**\nZTER 18727059 19357862 **8,18,32,24,36,34,63**\n\n========================================================================= \nInstallation:\n \n1. There is no need for these routines to be mapped on systems that allow\nmapping.\n \n\n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n3. The patch has now been loaded into a Transport global on your system.\nYou now need to use KIDS to install the Transport global.\nOn the KIDS menu, under the 'Installation' menu, use the following\noptions:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nThis patch updates the error routines and Taskman to use a common place to\n Backup a Transport Global\n \n4. Users can remain on the system. This patch can be queued and\ninstalled at any time. \n\n5. On the KIDS menu, under the 'Installation' menu, use the following\noption:\n Install Package(s) 'XU*8.0*63'\n =========\n \ncheck to see if errors should NOT be recorded or should be screened from\n6. MSM Sites - Answer YES to the question 'Want to MOVE routines to other\nCPUs?'. Enter the names of your Compute and Print server(s).\n \n7. After installing this patch, you need to move one routine from \n your production account to each manager account:\n ZTER\n \n And in the manager account,\n \n DO RELOAD^ZTMGRSET\nthe normal XTER listing. The current ERROR MESSAGE file has been enhanced\n Select the System\n Patch number to load: 63\n ==\n MSM Site - Move these MGR routines to your other CPU's.\n \n\n=========================================================================\n\nto control this action. The %ZTER routine checks the list and will not\nrecord errors that are flagged not to record.\n \n\n
\nKernel patch XU*8.0*527; CLEAN THE TEXT LINE. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n
\nKernel patch XU*8.0*494; Fix UNDEFINED in XQ83A. Please\nrefer to the Description in Forum Patch Module for details.\n\n
\nKernel patch XU*8.0*519; Modify PRINT LOCAL NPI REPORTS. Please refer\nto the Description in Forum Patch Module for details.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*514 XUSTZ error fix.\n\n
\nPlease see the patch description in the Patch Module on FORUM.\n\n\n
\nKernel patch XU*8.0*531; Updates the Person Class file #(8932.1).\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nKernel patch XU*8.0*536; New Taxonomies. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nHUN-0396-21050 XQAL* Fix several small problems that cause errors in \n\nTUA-0997-30470 ZISH* Fix to use the DEFAULT DIRECTORY FOR HFS field\nCHY-1097-52881 in file 8989.3 (KSP). Fix use of recordsize to\n match CIRN.\n \nLAK-0897-30499 DEVICE file $I field length increased to 40 char. \n \nAXP TEAM ZOSFVXD Disable priority changing, This has caused performance\n ZOSVVXD problems when lower priority jobs hold locks on\n critical code sections.\nHUN-0996-21721 special cases. Changed to use TMP from XUTL.\n \nCHY-0597-50132 XUS91 Made a fix to make the code more robust.\n\n Fix description for rescheduling frequency. \n\n XUWORKDY Fix problem if HOLIDAY file is missing.\n \n Checksum\nRoutine Old New 2nd Line\nXQALDEL 13827021 12561210 **6,24,65**\nForum 24021577 If the user has a mix of Info and action alerts,\nXQALDOIT 10428734 9852030 **1,6,65**\nXQALERT 5798541 5307017 **1,65**\nXQALERT1 19524336 18178207 **20,65**\nXQALFWD 10036386 10058961 **6,65**\nXQALSET 13085815 12680442 **1,6,65**\nXUINPCH 3256791 3950316 **20,36,43,49,63,65**\nXUPARAM 1006391 **65**\nXUS91 8526517 **18,65**\nXUTMG43 921517 **18,65**\nXUWORKDY 1331031 1179273 **65**\n during processing of alerts the display will \nZISHMSM 5354551 5685657 **24,36,49,65**\nZISHONT 5001907 **34,65**\nZISHVXD 6891389 **24,36,65**\nZOSFVXD 7401132 7407077 **65**\nZOSVVXD 7519714 7658715 **13,65**\nZTPTCH 4509174 4561379 **44,65**\n \n========================================================================= \nInstallation:\n\n stop before doing an action that could cause\n 1. Some of these routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n 4. Inhibit users from login into the system. (If you install when few\n info to scroll off the top.\n user are on the system and the possibility of some CLOBER/EDITED\n errors is acceptable then users can stay on the system.)\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System \n \n Backup a Transport Global\n Install Package(s) 'XU*8.0*65'\n =========\n \n 6. After installing this patch, \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n\n ZISHMSM\nCIRN ZISHMSM Fix the way that %ZISH under MSM open's multiple\n ZISHONT\n ZISHVXD\n ZOSFVXD\n ZOSVVXD\n \n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n host files.\n Patch number to load: 65\n ==\n\n 7. DSM Sites, after patch has installed, rebuild your map set.\n\n 8. Enable user's login.\n\n =========================================================================\n\n\n
\nPatch XU*8*523 BROKER SECURITY ENCHANCEMENT FOR IMAGING\n \nSee the description in the patch module on Forum.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*524 SSH fix.\n\n
\nKernel patch XU*8.0*541; Update the Person Class file. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nKernel patch XU*8.0*538; Clean up Delegated Options that have been \ndeleted. Please refer to the Description in Forum Patch Module for \ndetails.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*534 Taskman Cleanup.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n\n
\nKernel patch XU*8.0*528; Fix NPI Extract Report. Please refer to the \nDescription in Forum Patch Module for details.\n\n
\nKernel patch XU*8.0*545; Fix audited Options Log, and update the Person \nClass file (#8932.1). Please refer to the Description in Forum Patch\nModule for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*546 More Mixed OS device fixes.\n\n
\n*** This patch is a high priority because it is needed by the OpenM ***\n \n ZTER Change to allow OpenM sites to use the new error\n trapping. The check was conditional because early\n versions didn't support this. Then OpenM started\n changing its name with each version. Fixed to remove\n version checking, assume all VA site running current\n version that supports standard error trapping.\n \n The options XUDEV RES-ONE and XUDEV RES-CLEAR didn't\n get linked to the XUTIO menu in patch 49.\n*** sites to adjust to changes made by Intersystem in build 52e that***\n Resending to link them up.\n \nBIL-0298-30193 Alert tracking file 8992.1 was missing field .08\n to control retention of alerts.\n \n Checksum\nRoutine Old New 2nd Line\nXQ33 8946889 9007179 **49,73**\nXUSTERM 14376497 **36,73**\nZTER 18727059 19441177 **8,18,32,24,36,63,73**\n*** is going out to the sites. ***\n \n========================================================================= \nInstallation:\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n 4. Users can remain on the system. This patch can be loaded any\n non-peek time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*73'\n =========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\nISL-0198-51102 XUSTERM Didn't have code to call the extended-action option\n \n 8. After installing this patch, \n DSM/MSM sites - you need to move one routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n ZTER\n \n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n in XUSTERM2.\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 73\n ==\n \n 9. MSM sites move these routines to the MGR accounts on other CPU's.\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n \n XQ33 Fix from IHS about deleting options.\n\n
\nThis is the NPI Crosswalk Extract that has been modified as \nrequested by CBO.\n\n
\nSUPPORT FOR NON-PATIENT IDENTITY MANAGMENT\nRefer to patch XU*8.0*551 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKernel patch XU*8.0*537; Fix UNDEFINED in XQ83A. Please refer\nto the Description in Forum Patch Module for details.\n\n
\nSee patch XU*8*504 in the National Patch Module for complete\ninformation on this patch.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXU*8*431 Error Trap Summary.\n\n
\nKernel patch XU*8.0*553; FIXS MENU JUMPING Please refer to the Description\nin Forum Patch Module for details.\n\n
\nKernel patch XU*8.0*560; Updates the Person Class file (#8932.1). Please \nrefer to the Description in Forum Patch Module for details.\n\n
\nSee the Patch Module on FORUM for a description.\n\n\n
\nPrerequisites:\n When the routine XUSHSHP was written to hash the signature block in\n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: XU*8.0*60\n =========\n 8. MSM Sites - Answer YES to the question 'Want to MOVE \n routines to other CPUs?'. Enter the names of your \n Compute and Print server(s).\n AXP Sites - Answer NO to this question.\n 9. Rebuild your mapped set if necessary.\n file 200, several local variables were used which were not within the\n Kernel namespace. As would be expected, at least one of the\n variables is now another namespace and conflicts have arisen. This\n patch uses the NEW command to limit the scope of these incorrectly\n namespaced variables to the code in which they are used, and will\n prevent future problems with other packages due to this error.\n \n Several alpha sites reported unusually high activity associated\n with the XUTL global. This was identified as a problem related to \n=========== \n a spuriously high date value being set into the "AT" cross \n reference in file 19. Since this date was always ahead of NOW,\n micro-surgery would restart as soon as it had completed. To \n correct this problem, this patch contains a change to XQ83 which \n will reset any of these spurious future nodes to NOW and stop this \n excess activity. A change is also made in XQ7 which will prevent \n these nodes being set incorrectly in the future.\n \n There have also been some reports of problems [NOIS CLA-0397-22395]\n associated with the value of ZTCPU being reset as a result of a call\n The following patches must be installed before this patch: 44\n to KICK^XQ7 during KIDS installations. This problem is corrected by\n NEWING the value ZTCPU before it is used in KICK^XQ7.\n \n \nCategory:\n=======\n Routine\n \n \nTest Sites :\n \n==============\n \n \nRoutine Summary :\n==============\n The following is a list of the routines included in this patch. The\n second line of each of these routines now looks like:\n \n XQ7 <tab>;;8.0;KERNEL;**44,60**;Jul 10, 1995\n XQ83 <tab>;;8.0;KERNEL;**60**;Jul 10, 1995\n \n XUSHSHP <tab>;;8.0;KERNEL;**60**;Jul 10, 1995\n \n \nRoutine Name Patch List\n------------ --------------\nXQ7 44,60\nXQ83 60\nXUSHSHP 60\n \nChecksums:\nSubject:\n=========\n Rtn Nm Chksum Before Chksum After Patch List\n \n XQ7 2506259 2523046 44,60\n XQ83 9490213 10007662 60\n XUSHSHP 11148336 11486766 60\n \n _X_ Used CHECK^XTSUMBLD (or) ___ Used KIDS option\n \n To test if the transport has been corrupted, you can use the \n======\n "Verify Package Integrity" option. This option is under Utilities \n under the KIDS menu. It will compare the checksums in the build \n with the current checksums and list any that differ.\n \n \nInstallation Instructions:\n===================\n \n 1. Users ARE allowed to be on the system during the \n installation. However, since XQ83 is referenced during the\n XU*8*60 CORRECT NAMESPACE PROBLEM/FIX MICROSURGERY\n log-on procedure, BRIEFLY INHIBITING LOGONS while the patch is\n installed is recommended\n 2. DO NOT place TaskMan in a WAIT/STOP state. \n 3. The routines in this patch are used in the background and\n will not normally affect journaling, compiled templates, or\n option usage.\n 4. These routines are usually mapped on systems that allow \n mapping, so you will need to disable mapping for the affected\n routines.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \n \n This option will load the KIDS package onto your system. \n 6. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport\n global. \n 7. On the KIDS menu, under the 'Installation' menu, use the\n following options: \n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n\n
\nKernel patch XU*8*570; ADD A TAXONOMY FOR THE PERSON CLASS FILE.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee the description in the patch module on Forum.\n\n
\nPlease see the National Patch Module for the patch description.\n\n\n
\nKernel patch XU*8*581; NEW TAXONOMIES FOR THE PERSON CLASS FILE.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\n \nXU*8*543 Auto Sign-on Fix.\n\n
\nPlease see the National Patch Module on Forum for the description.\n\n\n
\nKernel patch XU*8*570; FIXES: OUT OF ORDER OPTION.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nKernel patch XU*8*586; NEW PERSON CLASSED. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\n\n\n
\nThis patch includes routines that either needed change because of Y2K\nVA FileMan to External\n \n 9. DSM Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\n\n Return conversion to an external format of a date in VA FileMan format.\n arguments: x VA FileMan date\n y [optional] Affects output as follows:\n If '$D(y) then return standard VA FileMan format.\n If +y = 1 then return standard VA FileMan format.\n If +y = 2 then return MM/DD/YY@HH:MM:SS format.\n If +y = 3 then return DD/MM/YY@HH:MM:SS format.\n If +y = 4 then return YY/MM/DD@HH:MM:SS format.\n If +y = 5 then return MM/DD/YYYYHH:MM:SS format.\nanalysis or provide new date formats for others to use.\n If +y = 6 then return DD/MM/YYYY@HH:MM:SS format.\n If +y = 7 then return YYYY/MM/DD@HH:MM:SS format.\n If y contains "D" then Date only.\n If y contains "F" then output date with leading blanks.\n If y contains "P" then output "HH:MM:SS am/pm".\n If y contains "M" then output "HH:MM" only.\n If y contains "S" then force seconds in the output.\n If y contains "Z" then output date with leading zeros.\n \n W $$HTE^XLFDT("54786,40523") --> Dec 31, 1990@11:15:23\n\n W $$HTE^XLFDT("54786,40523",2) --> 12/31/90@11:15:23\n W $$FMTE^XLFDT(2940629.105744,1) --> Jun 29, 1994@10:57:44\n W $$FMTE^XLFDT(2940629.105744,"2M") --> 6/29/94@10:57\n W $$FMTE^XLFDT(2940629.1057,"2S") --> 6/29/94@10:57:00\n W $$FMTE^XLFDT(2940629.1057,"4D") --> 94/6/29\n W $$FMTE^XLFDT(2940629.1057,"1P") --> Jun 29, 1994 10:57 am\n W $$FMTE^XLFDT(2940629.1057,"2P") --> 6/29/94 10:57 am\n W $$FMTE^XLFDT(3000229.1105,"5") --> 2/29/2000@11:05\n W $$FMTE^XLFDT(3000229.1105,"5ZP") --> 02/29/2000 11:05 am\n W $$FMTE^XLFDT(3000229.1105,"5F") --> 2/29/2000@11:05\nSee the Web page to see the new formats available with FMTE^XLFDT and\n W $$FMTE^XLFDT(3000229.1105,"6Z") --> 29/02/2000@11:05\n W $$FMTE^XLFDT(3000301.1105,"7") --> 2000/3/1@11:05\n\n\n\n Checksum\nRoutine Old New 2nd Line\nXLFDT 2542000 4068329 **71**\nXLFDT1 1537932 2415851 **71**\nXLFDT2 4162412 3429255 **71**\nHTE^XLFDT. \nXLFDT3 7128144 6320544 **71**\nXLFDT4 1396443 1396443 **71**\nXQDATE 1632193 1671306 **71**\nXTER2 13615695 10464968 **71**\nXUWORKDY 1331031 902683 **65,71**\nZOSVVXD 7658715 7782508 **13,65,71**\n \n========================================================================= \nInstallation:\n\n http://www.vista.domain.ext/softserv/infrastr.uct/kernel/y2k/index.html\n 1. DSM sites - Some of these routines may be mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peek time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\nHere is a sample, Note the NEW values for y. 5, 6, 7 \n option:\n Install Package(s) 'XU*8.0*71'\n =========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n \n 8. After installing this patch, \n DSM sites - you need to move one routines from \n your production account to each manager account:\n$$FMTE(x[,y])\n OpenM Sites - you don't need to move anything, skip this step.\n ZOSVVXD\n \n And in the manager account, (OpenM sites remain in VAH)\n \n DSM sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 71\n ==\n\n\nPlease refer to the Description in the FORUM Patch Module for details.\n\n
\nSee the patch module on Forum for the full description.\n\n
\nThis patch changes the minimum verify code lenght for service accounts\n(User Class = CONNECTOR PROXY) from 8 to 12 characters.\n \nIt also provides a new report as two options (inquire-style and\nreport-style). The report provides details about connector proxy \nservice accounts to help with account management.\n\n
\nThis patch was created to support Outpatient Pharmacy in printing Food\n \nNew field in the DEVICE file (#3.5) - WINDOWS NETWORK PRINTER NAME (#75)\n------------------------------------------------------------------------\n3.5,75 WINDOWS NETWORK PRINTER NAME WIN;1 FREE TEXT\n \n INPUT TRANSFORM: K:$L(X)>50!($L(X)<5) X\n LAST EDITED: AUG 23, 2011 \n HELP-PROMPT: Answer must be 5-50 characters in length. \n DESCRIPTION: This is the Windows network name for the\n printer (e.g., '\\\\vhaistfpc4\\IST-HP4525-1').\nand Drug Administration (FDA) Medication Guide documents using a Java\n It is used by Windows applications that\n interact with VistA and need a printer \n identified for output purposes. \n \nThe new field can be edited via the Edit All Device Fields [XUDEVEDITALL] \noption under the Kernel Device Management options as seen below:\n \n Select Device Edit Option: Edit All Device Fields\n \n Select DEVICE NAME: FDAMGPRT FDA MG Printer _TNA1316: \napplication. These documents are in Adobe Portable Document Format (.pdf),\n NAME: FDAMGPRT// \n LOCATION OF TERMINAL: Pharmacy// \n Select MNEMONIC: \n ...\n TELNET PORT: \n REMOTE PRINTER NAME: \n WINDOWS NETWORK PRINTER NAME: ??\n This is the Windows network name for the printer (e.g., \n '\\\\vhaistfpc4\\IST-HP4525-1'). It is used by Windows applications that \n interact with VistA and need a printer identified for output purposes.\nwhich is a file format not supported by VistA.\n \n WINDOWS NETWORK PRINTER NAME: \\\\vhaistfpc4\\IST-HP4525-9\n LAB LABEL PRINTER:\n ...\n \nThere was a problem with the HTTP Toolkit API $$GETURL^XTHC10. It was\nmodifying the array variable IO, which could cause issues for the calling\nroutine. The NEW command was placed for the IO variable inside the XTHC10\nroutine to resolve this problem.\n \nA new field, WINDOWS NETWORK PRINTER NAME (#75), is being added to the\nDEVICE file (#3.5). This field will be used to store the Windows network\nprinter name, which VistA passes on to a Java Application responsible\nfor printing FDA Medication Guide documents.\n\n
\nKernel patch XU*8*591; NEW PERSON CLASSED. Please refer to the \n Description in Forum Patch Module for details.\n\n
\nKernel patch XU*8*582; Fix Error Trap.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch XU*8*513.\n\n
\nBSE LOGIN ERROR Troubleshooting\n\n
\nSee patch description on FORUM for XU*8.0*590 for details.\n\n
\nKernel patch XU*8*601; NEW PERSON CLASSED. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nBOI-0398-52635, BRX-0398-12325\nentering mm/dd/yy would not report the errors there were on that date.\n \n Checksum\nRoutine Old New 2nd Line\nXTER2 10464968 10468040 **71,77**\nXUWORKDY 902683 908391 **65,71,77**\n \n========================================================================= \nInstallation:\n \nHIN-0398-42171 XUWORKDY\n 1. DSM sites - This routine may be mapped,\n so you will need to disable mapping for the effected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\nDuring the fixing of XUWORKDY for Y2K issues the changes weren't tested\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time. (There is a very small possibility of some CLOBER\n errors)\n \nwith data that couldn't be calculated. Dates missing the month or day\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*77'\n =========\n \n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\nare invalid. \n \nDAY-0398-42487\nHOU-0398-72500 XTER2\nDuring the fixing of XTER2 for Y2K issues, Testing didn't find that\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nKernel patch XU*8*587; FIXES: SINGLE FILE ADD/DELETE FOR A USER OPTION.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nSee patch description on FORUM for XU*8.0*599 for details.\n\n
\nSee patch description on FORUM for XU*8.0*593 for details.\n\n
\nKernel patch XU*8*604; NEW PERSON CLASSED. Please refer to the \nDescription in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\n\n\n
\nPlease see the National Patch Module for the patch description. \n\n\n
\nKernel patch XU*8*598; FIX: the API $$TRIM^XLFSTR. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nEnhancements to Unwinder routines (XQOR*) in support of CPRS 1.0\n were allowed, the user erroneously entered something like 1-4B,\n and then typed a return at 'For entry 1-4B enter: ".\n \n 3) Added "E" as a flag for XQORM(0). It will allow ambiguous lookups\n to be resolved interactively when XQORM is called without XQORM(0)\n containing an "A".\n \n 4) Made a change that sets full screen earlier when being called by\n list manager so that selection lists are properly displayed.\nThese enhancements include:\n \n 1) A new parameter which may be passed to XQORM - XQORM("ALT")\n This allows the calling routine to supply an alternative lookup\n to be used if the user types something that does not appear on\n the menu.\n \n 2) Fixed a bug that caused the menu to be exited if numeric ranges\n\n\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nSee the patch module on Forum for the description.\nXU*8*522\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch XU*8*602.\n\n
\nKernel patch XU*8*588; FIX: <UNDEFINED> ERROR IN XUSTERM.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nKernel patch XU*8*616; Update the Person Class file. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nSee patch description on FORUM for XU*8*614.\n\n
\n \nPlease refer to the Description in the FORUM Patch Module for details.\n\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\n\n\n
\nIPv4 and IPv6 utilities, IA #5844.\n \nSee description of patch XU*8*605 on FORUM.\n\n
\nPlease see description of patch XU*8*632 on FORUM.\n\n
\n=============================================================================\n E3R #10306.\n -Protocols will now delete properly at the site.\n -The variable XPDABORT will correctly abort the install in both the Pre &\n Post install routines.\n -The variable DIR is newed before call to environment check routine.\n ISW-0597-21778\n\n=============================================================================\nROUTINES:\n Checksums obtained using CHECK^XTSUMBLD\n ****** This patch must be QUEUED during the install process ******\n The second line of the routine now looks like:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n Before After Patch\nRoutine Checksum Checksum List\n----------------------------------------------------------------------\nXPDDP 11584192 11970878 **21,28,44,68**\nXPDE 15041471 15253053 **2,15,21,44,51,68**\nXPDI 13319818 13691537 **10,21,39,41,44,58,68**\nXPDIA 13293339 13299802 **10,15,21,28,44,58,68**\n=============================================================================\nXPDIA1 7937994 9226085 **2,44,51,58,68**\nXPDIA2 3520152 6372331 **68**\nXPDIJ 10173098 10435806 **2,21,28,41,44,68**\nXPDIJ1 8772642 9316977 **41,68**\nXPDIL 11156235 11193690 **15,44,58,68**\nXPDIL1 8519937 9389594 **15,17,39,41,44,66,68**\nXPDIPM 1817853 1853883 **21,28,68**\nXPDT 19357441 18817747 **2,10,28,41,44,51,58,66,68**\nXPDTA1 4760350 4948004 **44,68**\n=============================================================================\n\n **** INSTALL INSTRUCTIONS ****\n=============================================================================\n\n This patch can be installed with users on the system, but no other users\n should be using KIDS while you install this patch.\n Since this patch is an update to KIDS, no other patches should be installed\n during the installation of this patch.\n\n ****** This patch must be QUEUED during the install process ******\n\nThis patch contains fixes that were identified by mail messages and E3R\n===========================================================================\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 4. Users can remain on the system. This patch can be queued and installed\n -A patch will not be installed if the site is not running the correct version\n at any time. TaskMan can remain running.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n INSTALL NAME: XU*8.0*68\n =========\n for the package.\n 6. At the device prompt, make sure you queue the install:\n DEVICE: HOME// QUEUE TO PRINT ON\n =\n 7. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n -Multiple Build definition will now be sent to the site, along with all the\n builds that make up the Multiple Build.\n\n
\nSee patch description on FORUM for XU*8*629.\n\n
\nAdd RUM support for Linux and Windows operating systems.\n\n
\nFix typo in routine XQSMDCPY that references file 19. It should be file \n\n
\nKernel patch XU*8*634; Update the Person Class file. Please refer to the \nDescription in Forum Patch Module for details.\n\n
\nFix identification of new A* options that are part of a VistA national \npatch namespace. These should not be identified as belonging to a local\nnamespace when a new OPTION file (#19) entry is added.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\n \nThis patch fixes code in XQARPRT1 to point to the new Alert Critical Text\nFile 8992.3 to search for critical text to flag an alert as critical.\n\n
\nSee patch XU*8*650 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nSee patch XU*8*625 in the National Patch Module for complete \ninformation on this patch.\n\n
\nThis patch is one in a series of patches to support the VA's transition \nThis patch updates several places where IPv4 address formats were \nhard-coded in routines, and have now been replaced with calls to \nIPv4/IPv6 Application Programmer Interfaces (APIs) to support the VA's \ntransition to IPv6. Several changes have also been made in algorithms \nthat will improve the efficiency of IP address handling.\n \nNo current functionality has been changed. IPv6 functionality for future \nsupport cannot be completely tested until additional changes are made in \nVistA, and a test environment is established to replicate the planned VA \nnetwork architecture.\nfrom IPv4 to IPv6. IPv6 is a protocol designed to handle the growth rate \nof the Internet and to cope with the demanding requirements of services,\nmobility, and end-to-end security. A Federal Chief Information Office \n(CIO) memo "Transition to IPv6" released in September of 2010 requires\nagencies to continue their IPv6 transition efforts and has established\nspecific milestones associated with enabling an IPv6 operational\ncapability by the end of FY2014.\n \n\n
\n*** This patch is a high priority because it is needed by the OpenM ***\n \n ZTER Change to allow OpenM sites to use the new error\n trapping. The check was conditional because early\n versions didn't support this. Then OpenM started\n changing its name with each version. Fixed to remove\n version checking, assume all VA site running current\n version that supports standard error trapping.\n \n The options XUDEV RES-ONE and XUDEV RES-CLEAR didn't\n get linked to the XUTIO menu in patch 49.\n*** sites to adjust to changes made by Intersystem in build 52e that***\n Resending to link them up.\n \nBIL-0298-30193 Alert tracking file 8992.1 was missing field .08\n to control retention of alerts.\n \n Checksum\nRoutine Old New 2nd Line\nXQ33 8946889 9007179 **49,73**\nXUSTERM 14376497 **36,73**\nZTER 18727059 19441177 **8,18,32,24,36,63,73**\n*** is going out to the sites. ***\n \n========================================================================= \nInstallation:\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n 4. Users can remain on the system. This patch can be loaded any\n non-peek time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*73'\n =========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\nISL-0198-51102 XUSTERM Didn't have code to call the extended-action option\n \n 8. After installing this patch, \n DSM/MSM sites - you need to move one routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n ZTER\n \n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n in XUSTERM2.\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 73\n ==\n \n 9. MSM sites move these routines to the MGR accounts on other CPU's.\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\n \n XQ33 Fix from IHS about deleting options.\n\n
\nKernel patch XU*8*654. This patch supports MFS. Please refer to the\ndescription in Forum Patch Module for details.\n\n
\nPlease see description of patch on FORUM.\n \nVistA Service Assembler (VSA) \n \nVistA Integration Adapter (VIA)\n \nVistA Access Enhancements (VAE)\n \nElectronic Health Management Platform (eHMP)\n \nVistA.js/EWD.js\n \n \nRPC Broker\n \nVeterans Access, Choice, and Accountability Act of 2014 (VACAA)\n- Public Law 9P. L.) 113-146, VACAA, which was enacted on August 7, 2014\n and amended through the Department of Veterans Affairs Expiring\n Authorities Act of 2014 (P.L. 113-175), improves the access of eligible\n Veterans to health care through non-VA entities and providers.\nThis patch provides utilities to Identify and Authenticate VistA users\nfrom sources external to VistA.\n \nIdentity and Access Management (IAM)\n- Provide a centralized authentication service for single sign-on to \n multiple VA applications, including VistA and applications that access \n VistA.\n\n
\nThis patch is in support of the Drug Enforcement Agency (DEA) \n \nApplication Programmer Interface (API) $$VDEA^XUSER was modified to \nreturn those users with no valid DEA number (none on file, or expired \nexpiration date) and a valid VA number as valid DEA prescribers. The API \nwas also changed to highlight those users who are grandfathered, in case \ngrandfathering is no longer allowed at some point in the future.\n\ne-Prescribing of Controlled Substances (CS) (ePCS) using Public Key \nInfrastructure (PKI). The following modifications to the VistA Kernel \nhave been made to meet current ePCS requirements.\n \nRoutine ^XUSC1C was modified to prevent an infinite loop when a read \nfailed at the start of a "conversation". Routine ^XUSC1C was also modified\nto replace hard-coded string comparison of IP addresses with supported\nKernel API calls (ICR 5844).\n\n
\nThis patch provides enhancements needed to implement Single Sign-On \nInternal (SSOi) for identification and authentication of users into VistA.\n \nThe use of these utilities are expected to improve security and auditing\ncapabilities in accordance with VA Handbook 6500 Appendix F and revision 4\nof NIST SP 800-53. As required by FIPS 199 and using guidance from NIST SP\n800-60, the recommended security categorization for these applications is\nHIGH.\n\n
\nEnable SAGG to run on Linux, VMS and Windows operating systems.\n\n
\nThis patch fixes a problem where Cache job numbers ($J) are reused during \nperiods of high-volume client-server connections (many connections within \na day). Data in the ^TMP("XQCS",$J) global is not deleted when a \nconnection is reset, and will persist into a new user session, often \ncausing RPC Broker connection errors.\n \nThis patch kills the ^TMP("XQCS",$J) global for a new session when DUZ is \nundefined or equal to zero.\n\n\nKernel patch XU*8*664. This patch supports MFS. Please refer to the\ndescription in Forum Patch Module for details.\n\n
\nKernel patch XU*8*665. This patch supports MFS.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nKernel patch XU*8*666. This patch supports MFS.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nThese routines have been patched in support of the RPC Broker 1T19.\n \n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n \n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Inhibit users from login into system. \n 5. Inhibit users from login into the system. (If you install when few\n user are on the system and the possibility of some CLOBER errors is\n acceptable then users can stay on the system.)\n 6. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Install Package(s) 'XU*8.0*23'\nroutine new checksum\n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 8. After installing this patch, you need to move several routines from \n your productions account to the manager account:\n ZTER\n and in the manager account rename\n ZTER to %ZTER\n \n Example: ZL ZOSVVXD ZS %ZOSV\n \nXUS3 5732668\n 9. AXP Sites, after patch has installed, rebuild your map set.\n 10. Enable user's login.\n \n \n=========================================================================\nXUSRB 2741649\nZTER 18166218\n \n========================================================================= \nInstallation:\n\n
\nThis patch was requested because of different errors that needed to be \nSites can add their own entries to the file. There is a field to allow\nthe advanced strings that Taskman has been using. Current entries in\nTaskmans error screen file are moved to the new file as part of the\ninstall.\n\n Checksum\nRoutine Old New 2nd Line\nXTER 17066911 17970380 **63**\nXTER1A 16667281 16315266 **63**\nXUINPCH 2465171 3137390 **20,36,49,63**\nscreened at the OpenM site.\nXUTMKE1 5103401 3519416 **63**\nXUTMKE2 9221275 2696336 **63**\nZTER 18727059 19357862 **8,18,32,24,36,34,63**\n\n========================================================================= \nInstallation:\n \n1. There is no need for these routines to be mapped on systems that allow\nmapping.\n \n\n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n3. The patch has now been loaded into a Transport global on your system.\nYou now need to use KIDS to install the Transport global.\nOn the KIDS menu, under the 'Installation' menu, use the following\noptions:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nThis patch updates the error routines and Taskman to use a common place to\n Backup a Transport Global\n \n4. Users can remain on the system. This patch can be queued and\ninstalled at any time. \n\n5. On the KIDS menu, under the 'Installation' menu, use the following\noption:\n Install Package(s) 'XU*8.0*63'\n =========\n \ncheck to see if errors should NOT be recorded or should be screened from\n6. MSM Sites - Answer YES to the question 'Want to MOVE routines to other\nCPUs?'. Enter the names of your Compute and Print server(s).\n \n7. After installing this patch, you need to move one routine from \n your production account to each manager account:\n ZTER\n \n And in the manager account,\n \n DO RELOAD^ZTMGRSET\nthe normal XTER listing. The current ERROR MESSAGE file has been enhanced\n Select the System\n Patch number to load: 63\n ==\n MSM Site - Move these MGR routines to your other CPU's.\n \n\n=========================================================================\n\nto control this action. The %ZTER routine checks the list and will not\nrecord errors that are flagged not to record.\n \n\n
\nKernel patch XU*8*675. This patch supports MFS, the TIU domain.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nJSON Encoding/Decoding utility.\n\n
\nThis package contains routines necessary to accommodate\nthe UTC changes to the INSTITUTION file (#4).\n\n
\nSubject: SECURE HASH LIBRARY FUNCTIONS\n180-4) specifies secure hash algorithms for computing a condensed \nrepresentation of electronic data (message). The hash algorithms \nspecified in this Standard are called secure because, for a given \nalgorithm, it is computationally infeasible 1) to find a message that \ncorresponds to a given message digest, or 2) to find two different \nmessages that produce the same message digest. Any change to a message \nwill, with a very high probability, result in a different message digest.\n \nSHA-256 algorithm taken from the NIST document:\n http://csrc.nist.gov/groups/STM/cavp/documents/shs/sha256-384-512.pdf\n \n \nThis routine provides new Kernel APIS for Secure Hash Algorithm (SHA-256) \nhashing of input of various formats:\n$$FILE^XLFSH256(FILENUM,IEN,FIELD) - Return the SHA-256 hash for the \n specified file entry\n$$HOSTFILE^XLFSH256(PATH,FILENAME) - Return the SHA-256 hash for a \n host file\n$$ROUTINE^XLFSH256(ROUTINE) - Return the SHA-256 hash for a \n routine\n$$SHA256^XLFSH256(MESSAGE) - SHA-256 hash for a message that \nCategory: ROUTINE\ncan \n be passed as a single string\n$$LSHA256^XLFSH256(MSUB,NBLOCKS) - SHA-256 hash for a message too \nlong \n to be passed as a single string\n \nIn addition, this routine provides several new Math Library Functions \nthat were used to create the SHA-256 hash:\n$$AND^XLFSH256(X,Y) - logical bitwise AND 32 bits\n$$NOT^XLFSH256(X) - logical bitwise NOT 32 bits\n ENHANCEMENT\n$$XOR^XLFSH256(X,Y) - logical bitwise XOR 32 bits\n$$N32H^XLFSH256(X) - Convert 32 bit decimal to \nhexidecimal\n$$RD4BYTES^XLFSH256(MESSAGE,OFFSET) - Return the big-endian 32 bits \n value\n$$N64BIG^XLFSH256(NUM) - Return a 64-bit big-endian integer\n$$RROTATE^XLFSH256(X,N) - Right rotate 32 bits\n$$RSHIFT^XLFSH256(X,N) - Right shift 32 bits\n \nDescription:\n===========\n \nFederal Information Processing Standards Publication 180-4 (FIPS PUB \n\n
\nKernel patch XU*8*677. This patch supports MFS, the PERSON CLASS domain. \nPlease refer to the description in Forum Patch Module for details.\n\n
\nPlease see FORUM for full patch description and installation instructions.\n\n
\nKernel patch XU*8*683. This patch supports MFS.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nKernel patch XU*8*682. This patch supports MFS, the Demographics files \n(RACE, MARITAL STATUS, and RELIGION).\nPlease refer to the description in Forum Patch Module for details.\n\n
\nJoint Legacy Viewer (JLV) is a joint VA and DoD graphical web based \nThis patch adds an entry in the REMOTE APPLICATION file (#8994.5) for the\nJLV application. The entry in this file will allow the Kernel Broker code\nin the host VistA system to Janus JLV authentication requests for remote\nuser access, and is done in accordance with instructions on the use of the\nBroker Security Enhancement (BSE) as provided by the VistA Infrastructure\nteam and RPC Broker software documentation. The Kernel Sign-on Log will \nshow when the JLV application is used to access VistA.\n \nBy using BSE, JLV can discontinue use of the MDWS style of authentication,\nwhich has been deprecated and will be permanently disabled at a future\napplication that is used by both VA providers as well as DoD providers. \ndate. The file entry contains the name of the application, the application\ncode (hashed), context option, and method of visitor authentication.\n \nThe menu option "JLV GUI Menu Option" [JLV WEB SERVICES] in the OPTION\nfile (#19) contains the Remote Procedure Calls (RPCs) for the JLV\napplication.\nThe JLV web based application displays all clinical information on a\npatient from VA and DoD sources.\n \nThis patch provides a means for uniquely identifying non-VA users \naccessing VistA through the JLV application using National Health \nInformation Network (NHIN) standards for user identification.\n \n\n
\nKernel patch XU*8*686. This patch supports MFS.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nHUN-0396-21050 XQAL* Fix several small problems that cause errors in \n\nTUA-0997-30470 ZISH* Fix to use the DEFAULT DIRECTORY FOR HFS field\nCHY-1097-52881 in file 8989.3 (KSP). Fix use of recordsize to\n match CIRN.\n \nLAK-0897-30499 DEVICE file $I field length increased to 40 char. \n \nAXP TEAM ZOSFVXD Disable priority changing, This has caused performance\n ZOSVVXD problems when lower priority jobs hold locks on\n critical code sections.\nHUN-0996-21721 special cases. Changed to use TMP from XUTL.\n \nCHY-0597-50132 XUS91 Made a fix to make the code more robust.\n\n Fix description for rescheduling frequency. \n\n XUWORKDY Fix problem if HOLIDAY file is missing.\n \n Checksum\nRoutine Old New 2nd Line\nXQALDEL 13827021 12561210 **6,24,65**\nForum 24021577 If the user has a mix of Info and action alerts,\nXQALDOIT 10428734 9852030 **1,6,65**\nXQALERT 5798541 5307017 **1,65**\nXQALERT1 19524336 18178207 **20,65**\nXQALFWD 10036386 10058961 **6,65**\nXQALSET 13085815 12680442 **1,6,65**\nXUINPCH 3256791 3950316 **20,36,43,49,63,65**\nXUPARAM 1006391 **65**\nXUS91 8526517 **18,65**\nXUTMG43 921517 **18,65**\nXUWORKDY 1331031 1179273 **65**\n during processing of alerts the display will \nZISHMSM 5354551 5685657 **24,36,49,65**\nZISHONT 5001907 **34,65**\nZISHVXD 6891389 **24,36,65**\nZOSFVXD 7401132 7407077 **65**\nZOSVVXD 7519714 7658715 **13,65**\nZTPTCH 4509174 4561379 **44,65**\n \n========================================================================= \nInstallation:\n\n stop before doing an action that could cause\n 1. Some of these routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n 4. Inhibit users from login into the system. (If you install when few\n info to scroll off the top.\n user are on the system and the possibility of some CLOBER/EDITED\n errors is acceptable then users can stay on the system.)\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System \n \n Backup a Transport Global\n Install Package(s) 'XU*8.0*65'\n =========\n \n 6. After installing this patch, \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n\n ZISHMSM\nCIRN ZISHMSM Fix the way that %ZISH under MSM open's multiple\n ZISHONT\n ZISHVXD\n ZOSFVXD\n ZOSVVXD\n \n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n host files.\n Patch number to load: 65\n ==\n\n 7. DSM Sites, after patch has installed, rebuild your map set.\n\n 8. Enable user's login.\n\n =========================================================================\n\n\n
\nKernel support routines for KMP Capacity Management.\n\n
\nKERNEL VISTA PATCH ENHANCEMENTS - RPCS FOR NEW PERSON FILE\nRefer to patch XU*8.0*691 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKernel patch XU*8*684. This patch fixes the broadcast function of the \nInstitution file.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nFix Cross Reference on Fields 28 and 29 of File 200.\n\n
\nKernel patch XU*8*698. This patch cleans up duplicated PARENT FACILITY \nentries on the ASSOCIATION (#14) field in the INSTUTITION file.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nPlease see the description on Forum\n\n
\nThis patch adds "ABNL IMA" to the ALERT CRITICAL TEXT file (#8992.3) and\nchecks for "NON" (like "NOT") to screen Alerts with critical text that are\nindicated is not critical.\n \nSee the Patch Description for XU*8*690 in the Forum Patch Module for\ncomplete details.\n\n
\nKERNEL VISTA ENHANCEMENTS - MVI NEW PERSON STAT REPORT\nRefer to patch XU*8.0*705 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch XU*8.0*703 corrects issues found in patch XU*8.0*679 and \nreported in tickets INC2380289 and INC2422028. The input transform for \nthe NEW PERSON file (#200) DEGREE field (10.6) and the NAME COMPONENT \nfile (#20) DEGREE field (6) were modified and routine XUSESIG3.\n\n
\nPrerequisites:\n When the routine XUSHSHP was written to hash the signature block in\n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: XU*8.0*60\n =========\n 8. MSM Sites - Answer YES to the question 'Want to MOVE \n routines to other CPUs?'. Enter the names of your \n Compute and Print server(s).\n AXP Sites - Answer NO to this question.\n 9. Rebuild your mapped set if necessary.\n file 200, several local variables were used which were not within the\n Kernel namespace. As would be expected, at least one of the\n variables is now another namespace and conflicts have arisen. This\n patch uses the NEW command to limit the scope of these incorrectly\n namespaced variables to the code in which they are used, and will\n prevent future problems with other packages due to this error.\n \n Several alpha sites reported unusually high activity associated\n with the XUTL global. This was identified as a problem related to \n=========== \n a spuriously high date value being set into the "AT" cross \n reference in file 19. Since this date was always ahead of NOW,\n micro-surgery would restart as soon as it had completed. To \n correct this problem, this patch contains a change to XQ83 which \n will reset any of these spurious future nodes to NOW and stop this \n excess activity. A change is also made in XQ7 which will prevent \n these nodes being set incorrectly in the future.\n \n There have also been some reports of problems [NOIS CLA-0397-22395]\n associated with the value of ZTCPU being reset as a result of a call\n The following patches must be installed before this patch: 44\n to KICK^XQ7 during KIDS installations. This problem is corrected by\n NEWING the value ZTCPU before it is used in KICK^XQ7.\n \n \nCategory:\n=======\n Routine\n \n \nTest Sites :\n \n==============\n \n \nRoutine Summary :\n==============\n The following is a list of the routines included in this patch. The\n second line of each of these routines now looks like:\n \n XQ7 <tab>;;8.0;KERNEL;**44,60**;Jul 10, 1995\n XQ83 <tab>;;8.0;KERNEL;**60**;Jul 10, 1995\n \n XUSHSHP <tab>;;8.0;KERNEL;**60**;Jul 10, 1995\n \n \nRoutine Name Patch List\n------------ --------------\nXQ7 44,60\nXQ83 60\nXUSHSHP 60\n \nChecksums:\nSubject:\n=========\n Rtn Nm Chksum Before Chksum After Patch List\n \n XQ7 2506259 2523046 44,60\n XQ83 9490213 10007662 60\n XUSHSHP 11148336 11486766 60\n \n _X_ Used CHECK^XTSUMBLD (or) ___ Used KIDS option\n \n To test if the transport has been corrupted, you can use the \n======\n "Verify Package Integrity" option. This option is under Utilities \n under the KIDS menu. It will compare the checksums in the build \n with the current checksums and list any that differ.\n \n \nInstallation Instructions:\n===================\n \n 1. Users ARE allowed to be on the system during the \n installation. However, since XQ83 is referenced during the\n XU*8*60 CORRECT NAMESPACE PROBLEM/FIX MICROSURGERY\n log-on procedure, BRIEFLY INHIBITING LOGONS while the patch is\n installed is recommended\n 2. DO NOT place TaskMan in a WAIT/STOP state. \n 3. The routines in this patch are used in the background and\n will not normally affect journaling, compiled templates, or\n option usage.\n 4. These routines are usually mapped on systems that allow \n mapping, so you will need to disable mapping for the affected\n routines.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \n \n This option will load the KIDS package onto your system. \n 6. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport\n global. \n 7. On the KIDS menu, under the 'Installation' menu, use the\n following options: \n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n\n
\nKernel patch XU*8*693. \nThis patch edits Bulletins.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nKERNEL VISTA ENHANCEMENTS - PPMS PIE SUPPORT\nRefer to patch XU*8.0*711 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSubject: Update %ZOSF to support SACWG changes\nnames. It increases the length from 8 to 16 characters. \n names and tags\n \nProblem:\n XINDEX utility needs to support routine name and labels to 16 characters\n and local variables names to 16 characters\n \nResolution:\n Change %ZOSF("TEST") to check for 16 characters instead of 8 in routine\n ZOSFONT\n \n \n \nTest Sites: \n===========\nFargo, ND\nSouth Texas, TX\n \n \nSoftware and Documentation Retrieve Instructions:\n=================================================\nThis patch is part of the TOOLKIT XINDEX 7.3 bundle. Please see\nThis patch also makes several changes to the ZOSFONT routine, but only\nthe Software and Document Retrieve Instruction in patch XT*7.3*140\n \n \nPatch Installation:\n===================\nThis patch is part of the TOOLKIT XINDEX 7.3 bundle. Please see\nthe Patch Installation in patch XT*7.3*140\n \n \nRoutine Information:\nthe ^%ZOSF("TEST") node will be set.\n====================\nThe second line of each of these routines now looks like:\n ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 10\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \n Routine Name: XU8P661 \n Before: n/a After: B83899 **661** \n Routine Name: ZOSFONT \n \n Before: B19625334 After: B28658128 **34,104,365,661** \n \nRoutine list of preceding patches: 365 \n \nThe routine ZOSFONT has the following changes:\n 1. A new tag, NOASK, allows the setup of the %ZOSF global without\n user interaction.\n 2. A new tag, ONE(X) allows the setup of a single node in the\n %ZOSF global. This allows this patch to update just\n \n %ZOSF("TEST").\n 3. There is now a short description for each %ZOSF node in the\n text.\n \nThere are 2 changes to the ^%ZOSF global:\n 1. The node ^%ZOSF("TEST") is changed, the checking of routine pattern has\n been removed. It is changed from\n I X?1(1""%"",1A).7AN,$D(^$ROUTINE(X)) to\n I X]"",$D(^$ROUTINE(X)).\n 2. The node ^%ZOSF("GSEL;Select Globals") is deleted. This node\nCategory: DATA DICTIONARY\n was incorrectly defined in patch XU*8*365. Patch 365 was\n suppose to set the ^%ZOSF("GSEL") global, but mistakenly set the wrong\n global node.\n \nThe post install routine XU8P661 cleans up the ^%ZOSF global.\n 1. The node ^%ZOSF("GSEL;Select Globals") is deleted\n 2. Sets node ^%ZOSF("TEST")\n \n \nPatch Components\n ROUTINE\n================\nFiles & Fields Associated:\n \nBUILD file #9.6 PRE-TRANSPORTATION ROUTINE #900\n ENVIRONMENT CHECK ROUTINE #913\n DEL ENV ROUTINE #913.1\n POST-INSTALL ROUINTE #914\n PRE-INSTALL ROUINTE #916\nINSTALL file #9.7 ROUTINES multiple #40\nROUTINE file #9.8 NAME #.01\n \n TAG #5\nTASKS file #14.4 Entry Point #.01\n Routine Name #2\nOPTION file #19 ROUTINE #25\nXQAB ERRORS LOGGED\n file 8991.5 ROUTINE #.02\nALERT TRACKING file #8992.1 ROUTINE TAG #1.03\nREMOTE PROCEDURE file #8994 TAG #.02\n ROUTINE #.03\n \n \n \nForms Associated:\nN/A\n \nMail Groups Associated:\nN/A\n \nOptions Associated:\nN/A\n \nDescription:\nProtocols Associated:\nN/A\n \nSecurity Keys Associated:\nN/A\n \nTemplates Associated:\nN/A\n \nNew Service Requests (NSRs):\n===========\nN/A\n \nPatient Safety Issues (PSIs):\nN/A\n \n \nBlood Bank Clearance\n====================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8.0*661 contains\nchanges to a package referenced in ProPath standard titled: BBM Team Review\nThis patch supports the change of the SAC for longer Tags and Routine\nof VistA Patches. This patch does not alter or modify any VistA Blood Bank\nsoftware design safeguards or safety critical elements functions.\n \nRISK ANALYSIS: Changes made by patch XU*8.0*661 have no effect on Blood Bank\nsoftware functionality, therefore RISK is none.\n \n \nDefect Tracking System Ticket(s) & Overview:\n============================================\nTicket: I9055002FY16 - XINDEX doesn't support SACC changes to routine\n\n\nKERNEL VISTA ENHANCEMENTS - EHRM SUPPORT\nRefer to patch XU*8.0*710 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee National Patch Module for complete information on this patch. \n\n
\nSee patch XU*8*607 in the National Patch Module for complete information\non this patch.\n\n
\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nKernel patch XU*8*701 IMPROVE USER AUTHENTICATION. Please refer to \nNational Patch Module for more information.\n\n
\nKernel patch XU*8.0*720 - Support National Patch Module. Please refer to \nthe patch description on Forum for detail information.\n\n
\nThis patch includes routines that either needed change because of Y2K\nVA FileMan to External\n \n 9. DSM Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\n\n Return conversion to an external format of a date in VA FileMan format.\n arguments: x VA FileMan date\n y [optional] Affects output as follows:\n If '$D(y) then return standard VA FileMan format.\n If +y = 1 then return standard VA FileMan format.\n If +y = 2 then return MM/DD/YY@HH:MM:SS format.\n If +y = 3 then return DD/MM/YY@HH:MM:SS format.\n If +y = 4 then return YY/MM/DD@HH:MM:SS format.\n If +y = 5 then return MM/DD/YYYYHH:MM:SS format.\nanalysis or provide new date formats for others to use.\n If +y = 6 then return DD/MM/YYYY@HH:MM:SS format.\n If +y = 7 then return YYYY/MM/DD@HH:MM:SS format.\n If y contains "D" then Date only.\n If y contains "F" then output date with leading blanks.\n If y contains "P" then output "HH:MM:SS am/pm".\n If y contains "M" then output "HH:MM" only.\n If y contains "S" then force seconds in the output.\n If y contains "Z" then output date with leading zeros.\n \n W $$HTE^XLFDT("54786,40523") --> Dec 31, 1990@11:15:23\n\n W $$HTE^XLFDT("54786,40523",2) --> 12/31/90@11:15:23\n W $$FMTE^XLFDT(2940629.105744,1) --> Jun 29, 1994@10:57:44\n W $$FMTE^XLFDT(2940629.105744,"2M") --> 6/29/94@10:57\n W $$FMTE^XLFDT(2940629.1057,"2S") --> 6/29/94@10:57:00\n W $$FMTE^XLFDT(2940629.1057,"4D") --> 94/6/29\n W $$FMTE^XLFDT(2940629.1057,"1P") --> Jun 29, 1994 10:57 am\n W $$FMTE^XLFDT(2940629.1057,"2P") --> 6/29/94 10:57 am\n W $$FMTE^XLFDT(3000229.1105,"5") --> 2/29/2000@11:05\n W $$FMTE^XLFDT(3000229.1105,"5ZP") --> 02/29/2000 11:05 am\n W $$FMTE^XLFDT(3000229.1105,"5F") --> 2/29/2000@11:05\nSee the Web page to see the new formats available with FMTE^XLFDT and\n W $$FMTE^XLFDT(3000229.1105,"6Z") --> 29/02/2000@11:05\n W $$FMTE^XLFDT(3000301.1105,"7") --> 2000/3/1@11:05\n\n\n\n Checksum\nRoutine Old New 2nd Line\nXLFDT 2542000 4068329 **71**\nXLFDT1 1537932 2415851 **71**\nXLFDT2 4162412 3429255 **71**\nHTE^XLFDT. \nXLFDT3 7128144 6320544 **71**\nXLFDT4 1396443 1396443 **71**\nXQDATE 1632193 1671306 **71**\nXTER2 13615695 10464968 **71**\nXUWORKDY 1331031 902683 **65,71**\nZOSVVXD 7658715 7782508 **13,65,71**\n \n========================================================================= \nInstallation:\n\n http://www.vista.domain.ext/softserv/infrastr.uct/kernel/y2k/index.html\n 1. DSM sites - Some of these routines may be mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peek time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\nHere is a sample, Note the NEW values for y. 5, 6, 7 \n option:\n Install Package(s) 'XU*8.0*71'\n =========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n \n 8. After installing this patch, \n DSM sites - you need to move one routines from \n your production account to each manager account:\n$$FMTE(x[,y])\n OpenM Sites - you don't need to move anything, skip this step.\n ZOSVVXD\n \n And in the manager account, (OpenM sites remain in VAH)\n \n DSM sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 71\n ==\n\n\nKernel patch XU*8*723 creates a new field CERNER (#102) in the INSTITUION \nfile (#4). Please refer to National Patch Module for detail information.\n\n
\nKERNEL VISTA ISSUE - NATIONAL PROVIDER IDENTIFIER\nRefer to patch XU*8.0*724 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKernel patch XU*8*702 REFLECTION 2-FACTOR AUTHENTICATION. Please refer to\nNational Patch Module for more information.\n\n
\nKernel patch XU*8*723 - SUPPORT REMOTE APPLICATIONS.\nPlease refer to National Patch Module for detail information.\n\n
\nThis Kernel patch modifies the existed cross reference LOC1 in the \nInstitution to be a New Style compound cross reference using the NAME and \nCURRENT LOCATION fields for Event Capture package. The modification of \nthe cross reference will address an issue that the cross reference and the\nCURRENT LOCATION field were out of synch.\n\n
\nThis patch fixes the option DISPLAY OF PROGRAMMER MODE ENTRY \nLIST [XUPMDISP]. Please refer to the description in Forum Patch Module for\ndetails.\n\n
\nKernel patch XU*8*653. This patch supports CPRS. Please refer to the\ndescription in Forum Patch Module for details.\n\n
\nKernel patch XU*8*707 KERNEL FILE ACCESS SECURITY SUPPORT AUDIT FILE.\nPlease refer to National Patch Module for more information.\n\n
\nKERNEL VISTA ENHANCEMENT - NEW PERSON EXTRACT\nRefer to patch XU*8.0*725 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKernel patch XU*8*730 CLARIFY USAGE OF MULTIPLE SURROGATE PERIODS. Please\nrefer to National Patch Module for more information.\n\n
\nBOI-0398-52635, BRX-0398-12325\nentering mm/dd/yy would not report the errors there were on that date.\n \n Checksum\nRoutine Old New 2nd Line\nXTER2 10464968 10468040 **71,77**\nXUWORKDY 902683 908391 **65,71,77**\n \n========================================================================= \nInstallation:\n \nHIN-0398-42171 XUWORKDY\n 1. DSM sites - This routine may be mapped,\n so you will need to disable mapping for the effected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\nDuring the fixing of XUWORKDY for Y2K issues the changes weren't tested\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time. (There is a very small possibility of some CLOBER\n errors)\n \nwith data that couldn't be calculated. Dates missing the month or day\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*77'\n =========\n \n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\nare invalid. \n \nDAY-0398-42487\nHOU-0398-72500 XTER2\nDuring the fixing of XTER2 for Y2K issues, Testing didn't find that\n\n
\nKernel patch XU*8*685. This patch fixes Error Trap Limit.\nPlease refer to the description in Forum Patch Module for details. \n\n
\nKERNEL VISTA ISSUES - NPI DUPLICATES\nRefer to patch XU*8.0*732 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch fixes the Kernel API PROD^XUPROD. Please refer to the \ndescription in Forum Patch Module for details. \n\n
\nThis patch adds the InterSystems Corporation IRIS data platform to Kernel \ncode, VA is transistioning to the IRIS plaform from the InterSystems \nCorporation Cache platform, this patch ensures Kernel functionality will \nremain intact when the transistion occurs. It maintains compatibility \nwith the Cache platform.\n\n
\nKERNEL VISTA ENHANCEMENT - NEW PERSON EXTRACT (CPRS TAB)\nRefer to patch XU*8.0*733 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see Patch Description on Forum\n\n
\nThis patch fixes the following menu options\nList Unreferenced Menu Options [XQ LIST UNREFERENCED OPTIONS] \nDelete Unreferenced Options [XQ UNREF'D OPTIONS]. Currently,\nwhen running these options, the option names starting with numbers\ndo not appear on the list. Code was modified in routine XQ33 to include\noptions whose names start with numbers.\n\n
\nKernel patch XU*8*735 - FIX MFS of INSTITUTION file. Please\nrefer to National Patch Module for detail information.\n\n
\n1) %ZOSVKR: allow VBEM to collect on IRIS platform.\n2) %ZOSVKSD: skip directory in ^SYS("UCI" if not physically present.\n\n\nKernel patch XU*8*739 ADD DATE PARAMETER TO XUSER APIs.\nPlease refer to National Patch Module for more information.\n\n
\nThis is an emergency patch to Kernel to provide the routine we asked\n this change. The two patched got out of sync.\n \n Checksum\nRoutine Old New 2nd Line\nZISTCPS NEW 1057561 **78**\n \n========================================================================= \nInstallation:\n \n 1. DSM sites - Don't need/use this routine.\nthe MailMan maintance developer to call. The MailMan patch didn't note \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\nthe dependency with Kernel, this was our mistake.\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*78'\n =========\n \n \n 8. After installing this patch, \n OpenM Sites - You need to rename this routine.\n ZL ZISTCPS ZS %ZISTCPS\n \n=========================================================================\n \n ZISTCPS This is a new routine that has the general TCP/IP\n server for OpenM in it. This function was moved\n to help standardize the call in %ZISTCP.\n The MailMan listener for OpenM was changed to reflect\n\n
\nKernel patch XU*8*731, PREVENT DUPLICATE VISITOR RECORDS. Please refer\nto National Patch Module for more information.\n\n
\nPlease see Patch Description on Forum\n\n
\nBackup of XU*8.0*741 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch XU*8.0*741 modifies the [EDIT AN EXISTING USER] option. \nPlease refer to the description in Forum Patch Module for details.\n\n
\nBackup of XU*8.0*737 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nKernel patch XU*8*737 OPTION OUT OF ORDER ERROR.\nPlease refer to National Patch Module for more information.\n\n
\nBackup of XU*8.0*742 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch fixes the Kernel API PROD^XUPROD. Please refer to the \ndescription in Forum Patch Module for details. \n\n
\nBackup of XU*8.0*744 on Apr 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nKERNEL VISTA ENHANCEMENT - PPMS/PIE SUPPORT\nRefer to patch XU*8.0*744 in the FORUM Patch Module for a complete\ndescription.\n\n
\n**** This patch will add to the number of entries in the LOCK table. ****\n determine if the task is still active.\n ZTLOAD7\n ZTM\n ZTM0\n ZTMS\n ZTMS2\n ZTMS3\n\n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n \n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 67\n ==\n \n 9. DSM Sites, after patch has installed, rebuild your map set.\n 10. Enable user's login.\n Remove TASKMAN from the wait state.\n\n=========================================================================\n These problems were reported in the following NOIS's: MAR-1196-20400, \n\n CMO-1196-41389, WNY-1296-11772, MAD-0197-40149, ISH-0197-41376, \n HIN-0297-41185.\n \n In addition to being tested locally, the following sites tested this patch:\n \n Baltimore VAMC, Dayton VAMC, Columbia VAMC\n \n**** Depending on the number of jobs on a system node the Lock table ****\nWNY-1296-11772, CMO-1196-41389, MAR-1196-20400\nHIN-0297-41185 ZTMS3 Prevent TaskMan and Kernel clean-up programs from \nISH-0197-41376 blowing away tasks that need to run for long periods\nMAD-0197-40149 XUTMK of time. This requires that tasks only use \n XUTMRJD INCREMENTAL locks.\n \nLong time requests for tasks that restart themselfas if they stop unexpectedly.\nPart of the problem has been to know when a TASK is running. The change to \nprevent clean-up programs from deleting the info about long running tasks\nputs into place the needed part so that taskman can check and restart tasks\n**** may need to be increased. ****\nthat need to be persistent.\n\nSFC-1197-60720 ZTMS2 Taskman would not check the device file OUT-OF-SERVICE\n ZTMS3 field. This was caused by DT not being set at the time\n ZTMS of the call to %ZIS.\n\nZTLOAD has two new supported tags.\n\n$$PSET^%ZTLOAD to set a task as persistent. Returns 1 if the flag is set other\nwise returns 0.\n\nPCLEAR^%ZTLOAD to clear the persistent flag for a task.\n\n Checksum\nRoutine Old New 2nd Line\nXQ1 11726256 11899807 **1,15,59,67**\nXQ82 3479466 3479466 **59,67**\nXUTMG19 3890099 **20,67**\nXUTMK 6472549 6655042 **49,67**\nXUTMRJD 6554859 6838266 **49,67**\nXUTMTZ 7805273 **67**\n Certain long running task (i.e. HL7 filers and LLP's) are getting removed \nZTLOAD 1188558 1753065 **67**\nZTLOAD2 3203201 3185920 **1,67**\nZTLOAD3 3918318 **67**\nZTLOAD7 3885066 4104573 **67**\nZTM 7821111 8229940 **24,36,64,67**\nZTM0 5563711 5758864 **42,36,67**\nZTMS 5336388 5366119 **2,18,24,36,67**\nZTMS2 5283853 5301865 **2,18,23,36,67**\nZTMS3 9572340 10241859 **1,18,36,49,64,67**\n\n from the system by the daily 'job' and 'Taskman' clean-up routines even \n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n though they are still active. Taskman has been modified to lock the \n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n ^%ZTSCH("TASK",tasknumber) node when starting a task and release the lock \n user are on the system and the possibility of some CLOBER errors is\n acceptable then users can stay on the system.)\n Also place TASKMAN in a wait state.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*67'\n =========\n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n at completion. The clean-up routines will now attempt to lock this node to \n other CPUs?'. Enter the names of your Compute and Print server(s).\n MSM Sites - With Taskman not working you need to move the routine to\n other CPU's with the D ^XPDCPU\n \n 8. After installing this patch, \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n ZTLOAD\n ZTLOAD3\n\n\nBackup of XU*8.0*743 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nKERNEL VISTA ENHANCEMENT - MPI NEW PERSON REMOTE AUDIT VIEW\nRefer to patch XU*8.0*743 in the FORUM Patch Module for a complete\ndescription.\n\n
\nBackup of XU*8.0*750 on Aug 25, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see Patch Description on Forum\n\n
\nKernel patch XU*8*753-FIX API $$CHKDGT-XUSNPIE1. Please refer to\nNational Patch Module for detail information.\n\n
\nThis Kernel patch fixes the option XUS NPI LOCAL REPORTS. Please prefer \nto the Patch Description on the National Patch Molude for the detail\ninformation.\n\n
\nKernel patch XU*8*754 KERNEL ALERTS FIXES. Please refer\nto National Patch Module for more information.\n\n
\nKernel patch XU*8*751 REMOVE CS DRUG SCHEDULE GRANDFATHERING.\nPlease refer to National Patch Module for more information.\n\n
\nKERNEL VISTA ENHANCEMENT - MPI WEB SERVICES FOR VISTA-LIKE SYSTEMS\nRefer to patch XU*8.0*757 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKernel patch XU*8*734 DEFERRED CPRS ALERTS FOR SURROGATES. Please refer\nto National Patch Module for more information.\n\n
\nPlease see Patch Description on Forum\n\n
\nKernel patch XU*8*758 - VISTA TRANSITION MENU. Please refer to\nNational Patch Module for detail information.\n\n
\nKernel patch XU*8*746, REMOTE USER SECURITY. Please refer to National\nPatch Module for more information.\n\n
\nBackup of XU*8.0*746 on Apr 05, 2022\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee FORUM Patch description.\n\n
\nKERNEL PATCH XU*8*769 - UPDATE [XUMF FORUM] HL LOGICAL LINK\n Another one: \n Standard Captioned Output? Yes// n (No)\n First Print FIELD: DNS DOMAIN \n Then Print FIELD: TCP/IP ADDRESS \n Then Print FIELD: \n Heading (S/C): HL LOGICAL LINK List Replace \n DEVICE: TELNET PORT Right Margin: 80// \n \n HL LOGICAL LINK List MAR 03, 2022@05:19\n DNS DOMAIN\n \n TCP/IP ADDRESS\n ------------------------------------------------------------\n \n HL7.DOMAIN.EXT\n 127.0.0.14\n \n This patch, at the end of the installation process, also queries the \n Institution Master File (IMF) to get the gold file of istitutions from\n the Forum account, and automatically updates the local INSTITUTION (#4)\n file.\nThis patch updates the DNS DOMAIN field for the [XUMF FORUM] HL\n LOGICAL LINK to be "HL7.DOMAIN.EXT".\n \n FileMan Inquire looks like:\n \n Output from what File: OPTION// 870 HL LOGICAL LINK (165 entries)\n Select HL LOGICAL LINK NODE: XUMF FORUM\n\n
\nSee FORUM for patch description.\n\n
\nKernel patch XU*8*771, FIX to XU*8*746. Please refer to National Patch\nModule for more information.\n\n
\nKERNEL VISTA ENHANCEMENT - PPMS/PIE UPDATE\nRefer to patch XU*8.0*767 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis Kernel patch fixes the option XUS NPI LOCAL REPORTS. Please prefer \nto the Patch Description on the National Patch Molude for the detail\ninformation.\n\n
\nKernel patch XU*8*766 -FIX the API $$ACCESS^XQCHK. Please refer to the \nNational Patch Module for detail information.\n\n
\nKernel patch XU*8*770 -FIX the - $ZERROR logged out of VistA \n[XMHELP-ON-LINE-USER_MANUAL]. Please refer to the National Patch Module\nfor detail information.\n\n
\nPlease see Patch Description on Forum\n\n
\nPlease see the patch description for contents.\n\n
\nSee XU*8.0*775 on FORUM patch description.\n\n
\nKernel patch XU*8.0*780 VIA-VDIF REMOTE APPLICATION ENTRIES. Please\nrefer to National Patch Module for more information.\n\n
\nXU*8.0*774 - FIXES THE NPI REPORT. Please refer the patch description on\nthe National Patch Module (NPM) for more detail informtion.\n\n
\nKERNEL patch XU*8*777 - FIX OPTION [XQAL USER ALERTS COUNT]\nformats may be generated by Divisions if desired. \n \n For each user who has the specified number of alerts or more, the report \nincludes the user name, the section/service for the user, the number of \nalerts in the ALERTS file, the last sign-on date, the number of Critical\nalerts or Abnormal Imaging alerts, and the date of the oldest alert.\n \nThis patch fixes the "Undefined SERVICE/SECTION Err" in the option User \nAlerts Count Report [XQAL USER ALERTS COUNT].\n \n This option is used to generate a report on users who have more than a\nspecified number of alerts in the ALERTS file (#8992). The report covers\na specified range of dates, and can be sorted by user name, number of\nalerts, or by service/section. In addition, the report in each of these \n\n
\nPlease see Patch Description on Forum\n\n
\nKERNEL VISTA ENHANCEMENTS - ENTERPRISE USER IDENTITY \nRefer to patch XU*8.0*663 in the FORUM Patch Module for a complete\ndescription.\n\n
\n XU*8*46 - Jump Problems and XQUIT\nthe headers were occasionally executed before the entry action rather than\nafter the entry action, the latter always being the correct sequence.\n[NOIS DAY-0994-40200, SPO-0597-50637]\n \n This patch also synchronizes the single uparrow jump ("^") and the\ndouble uparrow or rubber-band jump ("^^") so that both react the same\nwhen the variable XQUIT is set during the execution of an Entry Action.\n[NOIS DAY-0596-41019].\n \n The program ^XQDATE has been modified to correct a flaw that could\n \nmake time stand still by not cleaning up after itself.\n[NOIS BRX-0498-10234, CMO-0498-40588].\n \n \n Patch 46 also includes an enhancement to XQUIT processing. If XQUIT\nis encountered in a jump path the software will return the user to the\noption the user jumped from rather than stopping in mid-jump. It Also\nrequired the inclusion of a Screen-based Option Editor (OPED). Please see\nthe option "Kernel New Features Help" for a complete look at these\nfeatures.\n There are no associated patches.\n \n This patch contains the routine XQP46INI, a post install routine,\nthat may be deleted after the install.\n \n==========================================================================\n \nINSTALLATION: \n 1. These routines may be mapped on systems that allow\n it so you may have to disable mapping.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n \n option will load the KIDS package onto your system. \n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n 4. On the KIDS menu, under the 'Installation' menu, use the following \n options: \n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global\n Install Package(s) \n This patch contains 22 routines, a new Kernel File (Menu Systen Quick\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to \n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. Rebuild your mapped set if necessary.\n 7. If users are allowed to remain on the system during installation\n errors may occur when the routines are loaded.\n \n==========================================================================\n \n \n CHECK SUMS (^XTSUMBLD) AND PATCH LISTS\nHelp), 13 Help Frames, and 3 Options; which fix a couple of problems with\n \n The second line of these routines should look like this:\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n \nProgram Before After\nXQ 14578606 **9** 14086805 **9,46**\nXQ1 11899807 **1,15,59,67** 11798740 **1,15,59,67,46**\nXQ12 17600046 **9,20** 16945386 **9,20,46**\nXQ33 9007179 **49,73** 9049114 **49,73,46**\nXQ41 9107783 (no patches) 9203288 **46**\njumping. Under certain circumstances the Entry Action and Header would\nXQ71 13240707 (no patches) 13242248 **46**\nXQ72 10277570 **47** 12632194 **47,46**\nXQ72A 2885580 (no patches) 1074331 **46**\nXQ73 6791337 (no patches) 9215463 **46**\nXQ75 14473337 **47** 14455067 **47,46**\nXQ8A 4565915 (no patches) 4621077 **46**\nXQDATE 1671306 **71** 1673092 **71,46**\nXQHLP 11192542 (no patches) 11275643 **46**\nXQP46INI New 297767 **46**\nXQT 14370309 **20,47** 14403654 **20,47,46**\nnot be executed for the parent option of a secondary menu tree and the\nXQT1 10251041 **59** 10829937 **59,46**\nXQT2 12236113 (no patches) 12277933 **46**\nXQT3 12852830 (no patches) 12864808 **46**\nXQT4 15421169 (no patches) 15441632 **46**\nXQOPED New 1020766 **46**\nXQUIT New 6864597 **46**\nXQUTL New 3002763 **46**\nXUCOMMAND option which is the parent of the Common Options. In addition,\n\n\nKernel patch XU*8*772, ALERTS FIXES. Please refer to National Patch \nModule for more information.\n\n
\nBackup of XU*8.0*663 on Mar 13, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease refer to National Patch Module for more information.\n\n
\nSee National Patch Module on Forum for Description\n\n
\nSee FORUM for patch description.\n\n
\nKernel patch XU*8.0*779 FIX SAML REMOTE APPLICATION VERIFICATION. Please\nrefer to National Patch Module for more information.\n\n
\nSee National Patch Module on Forum for patch XU*8*784 FIX GETUSER2 ALERTS \nSORT\n\n
\nThis Kernel patch XU*8.0*788 sets LOCKS for options, and Audit for\nfields. Please refer to the description in Forum Patch Module for\ndetails. \n\n
\nKernel patch XU*8*790 RETAIN ALERT SURROGATE HISTORY. Please refer\nto National Patch Module on Forum for more information.\n\n
\nThis Kernel patch XU*8.0*789 - FIX ERROR WHEN ADDING USERS.\nPlease refer to the description in Forum Patch Module for details.\n\n
\nThis patch fixes several NOIS and FORUM mail message problems.\nby killing %ZISQUIT after each try.\n========================================================================= \n\n\nNOIS SAT-0196-71702 The number of characters on the task number that were\nincluded in the VMS name was to small for the current task numbers at some\nsites. This has been fixed in %ZTMS3 to allow more characters in the name.\n\nNOIS BRX-0196-10212 The executable help for the related frame subfield\nof the Help frame file has bad code in it that prevents its use. The\ncode has been commented out. (sent as a partial DD for file 9.2)\n\n\n'IO/%ZTIO MM' TaskMan errors, This was used to confirm and understand an\n issue. The problem is understood and there isn't an need for the entry in\n the error log. It has been removed from ZTMS2.\n\nForum # 17283911 On this message it was agreed that IO should be restored\nif POP was returned with a non-zero value. It currently is returned as 'NULL'\nin this case. This has been fixed.\n \nForum # 18837345 The help display of printers was impacted by a screen\n%ZIS("S") that changed the naked. This did not follow SAC guidelines, \nNOIS HOT-0196-40372 When displaying the $JOB number in XUS91, if the number was\nand has been fixed in ZIS5.\n\nThe OPEN/USE/CLOSE ^%ZISUTL calls didn't work. This has been fixed in\nZISUTL and ZIS1. The setting of IO(0) was changed to only happen one time\nso that IO(0) should always point to the HOME device, fixed in ZIS.\n\nHans found that the taskman resource logging was not being done. The fix\nwas found in XUTMG43. To make the sorting of taskman work consistent\nthe resource log string was changed in %ZTMS and %ZTMS3\n\ngreater than 127 it was converted to a HEX value needed by DSM sites. This \nI was found that the order of event during error traping needed improvment.\nalso requested was a hang to allow IO ports to reset during errors. This\nhas been done in %ZTMS.\n \nroutine new checksum\nXUS91 8464418\nXUTMG43 487942\nZIS 9225804\nZIS1 9986473\nZIS3 6454404\ncaused problems with the newer versions of MSM that can have $JOB values greater\nZIS5 7443452\nZISUTL 2297285\nZTER 18033524\nZTER1 5362718\nZTMS 5438606\nZTMS2 5327585\nZTMS3 8978754\n\n========================================================================= \nInstallation:\nthan 127. This has been changed to check for values greater than 32768.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n 2. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'\n 3. From the 'Installation Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n 4. Inhibit users from login into system. \n 5. From the 'Installation Menu' of the KIDS menu, run the option 'Install\n\n Package(s)' Select the package 'XU*8.0*18' and proceed with install.\n 6. After installing this patch, you need to move several routines from \n your productions account to the manager account:\n ZIS\n ZIS1\n ZIS3\n ZIS5\n ZISUTL\n ZTER\n ZTER1\nNOIS DAY-1295-41565 In %ZIS3 the use of %ZISQUIT in a hunt group would cause\n ZTMS\n ZTMS2\n ZTMS3\n and in the manager account rename\n ZIS to %ZIS\n ZIS1 to %ZIS1\n ZIS3 to %ZIS3\n ZIS5 to %ZIS5\n ZISUTL to %ZISUTL\n ZTER to %ZTER\nthe complete hunt group to fail, not the one entry. This has been fixed\n ZTER1 to %ZTER1\n ZTMS to %ZTMS\n ZTMS2 to %ZTMS2\n ZTMS3 to %ZTMS3\n\n Example: ZL ZOSVVXD ZS %ZOSV\n \n 7. On MSM move the routines to the other servers. \n On DSM, rebuild your map set. \n 9. Enable user's login.\n\n\nISB-0598-31461 ZISHVXD The use of the "default HFS directory" was not\n so that function keys would not work in screen\n man or the Screen editor. This has been fixed\n by turning off escape processing at the start\n of ZU. \n \n Checksum\nRoutine Old New 2nd Line\nZISHMSM 5685657 5978186 **24,36,49,65,84**\nZISHONT 5001907 5018937 **34,65,84**\nZISHVXD 6891389 7237979 **24,36,65,84**\nWRJ-0498-11566 implemented correctly by the list function. \nZUVXD 4856063 4645869 **13,24,84**\n \n========================================================================= \nInstallation:\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\nIOW-0598-41669 This has been fix to work correctly. PWD will\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nBEC-0598-21309 show the Default if that is un use.\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n \n 5. Return to Programmers Prompt and use "D ^XPDKRN":\n Install Package(s) 'XU*8.0*84'\n =========\n \n 6. DSM -- Rename ZUVXD: ZL ZUVXD ZS ZU\n \n \n 7. After installing this patch, \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n ZISHVXD, ZISHONT, ZISHMSM\n \n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n DO RELOAD^ZTMGRSET\nSFC-0598-61569 Field 20 of file 8992.1 was misspelled as \n Select the System\n Patch number to load: 84\n ==\n \n 8. DSM Sites, after patch has installed, rebuild your map set.\n \n \n=========================================================================\n RECEIPIENT.\n \nFORUM MSG ZUVXD Using ZSLOT users could get there process set\n\n
\nPlease see Patch Description on Forum.\n\n
\nPlease refer to patch description on Forum for patch XU*8*756, VISTA \nKERNEL SIGN-ON LOG RETENTION PERIOD.\n\n
\nKERNEL PATCH XU*8*797 - Modification of input transform on NON-KIDS\nINSTALL DATE field in PATCH MONITOR file(#9.9). Please refer to the NPM \nfor detail information.\n\n
\nThere were two snow tickets that reported undefine errors in routines \nXPDANLYZ2 and XPDANLYZ6 when trying to analyze a build.\n\n
\nFIX FOR DELAYED SSOI LOGIN\n\n
\nThis patch fixes the menu path display functionality of options\n[XUSERINQ] and [XU USERFIND]. \n\n
\nPlease refer to National Patch Module for more information.\n\n
\nFIX SYNTAX ERROR IN XQALERT1 ROUTINE\n\n
\nPlease see Patch Description for XU*8*802 on Forum Patch module.\n\n
\nDAY-0198-40011 If, as described in the NOIS, a person changes class,\n========================================================================= \nInstallation:\n\n 1. DSM sites - This routine may be mapped,\n so you will need to disable mapping for the effected routine. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n from 1 to 2 and then back to 1. The package allows \n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n the editing of the first entry, thus destroying the \n non-peek time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Use "D ^XPDKRN" then\n Install Package(s) 'XU*8.0*74'\n =========\n \n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n history information. Fixed with a change to the form.\n =========================================================================\n\n XU-PERSON CLASS and routine XUA4A72.\n \n Checksum\nRoutine Old New 2nd Line\nXUA4A72 2742817 4441866 **27,49,74**\n\n
\nBackup of XU*8.0*810 on Feb 04, 2025\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see Patch Description for XU*8*811 on Forum Patch module.\n\n
\nPlease refer to patch description on Forum for patch XU*8*800, PROGRAMMER\nMODE ACCESS\n\n
\nKernel patch XU*8*801, FIX ALERTS for SURROGATES and TERMINATED\n\n
\nThis patch fixes some issues found with the TaskMan Sync Flag \nfunctionality. A bug has been found with the XUTM SYNC option where the \ncalls that pass Sync Flag and the ZIO are flipped, thus not working as\nintended. Also, an overall analysis of the Sync Flag functionality\nthroughout TaskMan is being done to see if other bugs exist that hinder\nits use.\n\n
\nThis build transports the $I field (#1) of the DEVICE (#3.5) file. The \nfield is modified to have a maximum lengh of 250 in order to support \ndevices coresponding to Linux path names.\n\n
\nBackup of XU*8.0*801 on Mar 24, 2025\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nKernel patch XU*8*815 - TIMED READ PARAMETER THE USER FILE. Please refer \nto National Patch Module for more details.\n\n
\nKERNEL VISTA ENHANCEMENTS - ENTERPRISE USER SEARCH REBOOT\nRefer to patch XU*8.0*799 in the FORUM Patch Module for a complete\ndescription.\n\n
\nDAY-1097-42595 XQALSET During testing of TIU it was found that alerts\n 0 User can't sign-on.\n 0^DISUSER User can't sign-on because of DISUSER flag.\n 0^TERMINATED^2980310 User terminated on date.\n 1^NEW A new user, could sign-on.\n 1^ACTIVE^2980310.09 A active user, last sign-on date.\n \n Checksum\nRoutine Old New 2nd Line\nXQALSET 12680442 12975662 **1,6,65,75**\nXUSER 699878 1279527 **75**\n get sent to users that have been terminated. TIU\n \n ========================================================================= \nInstallation:\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n suggested that a change to ALERTS to not sent\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n alerts to user that can't sign-on.\n 4. Inhibit users from login into the system. (If you install when few\n user are on the system and the possibility of some CLOBER errors is\n acceptable then users can stay on the system.)\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*75'\n =========\n \n \n \n 6. DSM Sites, after patch has installed, rebuild your map set and\n enable user logins.\n =========================================================================\n XUSER As part of the change to XQALSET a API was created\n ACTIVE^XUSER to check if the user can sign-on.\n It returns the following codes:\n "" No user record.\n\n
\nKernel patch XU*8*807, convert "Service/Section Edit" option to Class I.\n\n
\nKERNEL VISTA ENHANCEMENT - NEW PERSON EXTRACT UPDATES\nRefer to patch XU*8.0*819 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKERNEL Patch XU*8*826 - UPDATE KIDS BACKUP BUILD. Please refer to National\nPatch Module for more details.\n\n
\nIMPORTANT!!! IMPORTANT!!! IMPORTANT!!!\nprotocols will need to be MANUALLY checked to ensure that a newly-created \n SDAM LATE ENTRY\n IBACM OP LINK\n DVBA C&P SCHD EVENT\n PXK SDAM TO V-FILES\n RMPR SCH EVENT\n DGEN SD DISPLAY CURRENT ENROLLMENT\n VAFH HL7 OUTPATIENT CAPTURE\n VAFC HL7 OUTPATIENT CAPTURE\n \n \nprotocol did not take the place of the deleted, one covering up the broken \nNOTE: the "<==" represent comments made by the author and are not part of the \ncaptures.\n \nFIGURE 1: Using FM, a protocol, ZZKYLE MENU 1, is displayed with four \nprotocols (ITEMs) attached.\n \nNXT,KDE>D P^DI\n \nVA FileMan 21.0\n \npointer.\nSelect OPTION: 5 INQUIRE TO FILE ENTRIES\nOUTPUT FROM WHAT FILE: PROTOCOL// \nSelect PROTOCOL NAME: ZZKYLE MENU 1 ItemText \nANOTHER ONE: \nSTANDARD CAPTIONED OUTPUT? Yes// (Yes)\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \nComputed Fields\n \nNAME: ZZKYLE MENU 1 ITEM TEXT: ItemText\n TYPE: menu CREATOR: DIMICELI,RON\n \n PACKAGE: 283 COLUMN WIDTH: 26\n MNEMONIC WIDTH: 4\nITEM: ZZKYLE ACTION 1 MNEMONIC: ZZ <== 1st Item\n SEQUENCE: 1\nITEM: ZZKYLE ACTION 2 <== 2nd Item\nITEM: ZZKYLE ACTION 3 <== 3rd Item\nITEM: ZZKYLE ACTION 4 <== 4th Item\n HEADER: D SHOW^VALM MENU PROMPT: Select ZZ Action:\n TIMESTAMP: 57379,39444\n \nNOTE: It is important to note that the PROTOCOL file has the same structure as \n \nSTEP 1: Review the Protocols that were identified above as having a protocol \ndeleted by a KIDS patch (i.e. PXCE ADD/EDIT MENU, DGPM MOVEMENT EVENTS, etc.).\n \n \nFIGURE 2: Here two protocols have been deleted, ZZKYLE ACTION 2 and ZZKYLE \nACTION 3, similar to the way a KIDS patch would have deleted them prior to \nXU*8*68.\n \nNXT,KDE>D P^DI\nthe OPTION file (#19) whereas field #10, ITEM corresponds to field #10, MENU, \n \nVA FileMan 21.0\n \nSelect OPTION: 5 INQUIRE TO FILE ENTRIES\nOUTPUT FROM WHAT FILE: PROTOCOL// \nSelect PROTOCOL NAME: ZZKYLE MENU 1 ItemText \nANOTHER ONE: \nSTANDARD CAPTIONED OUTPUT? Yes// (Yes)\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \nComputed Fields\nin the OPTION file. Field #10, ITEM is a multiple and a pointer to the .01 \n \nNAME: ZZKYLE MENU 1 ITEM TEXT: ItemText\n TYPE: menu CREATOR: DIMICELI,RON\n PACKAGE: 283 COLUMN WIDTH: 26\n MNEMONIC WIDTH: 4\nITEM: ZZKYLE ACTION 1 MNEMONIC: ZZ <== 1st Item\n SEQUENCE: 1\nITEM: 194 <== Broken Pointer\nITEM: 195 <== Broken Pointer\nITEM: ZZKYLE ACTION 4 <== 4th Item\nfield of the parent file. \n HEADER: D SHOW^VALM MENU PROMPT: Select ZZ Action:\n TIMESTAMP: 57379,39444\n \n \nSTEP 2: Broken pointers can be easily identified because a numeric will appear \nin the ITEM field. The routine XQ3 (shown in figure 4) will clean these up. \nYou must verify that the others actually should be connected to this protocol.\n \n \nFIGURE 3: Here a new protocol was created, ZZJACK. However, the new protocol \n \nwas created in IEN 194, covering up the previous broken pointer.\n \nNXT,KDE>D P^DI\n \nVA FileMan 21.0\n \nSelect OPTION: 5 INQUIRE TO FILE ENTRIES\nOUTPUT FROM WHAT FILE: PROTOCOL// \nSelect PROTOCOL NAME: ZZKYLE MENU 1 ItemText \nANOTHER ONE: \n \nSTANDARD CAPTIONED OUTPUT? Yes// (Yes)\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \nComputed Fields\n \nNAME: ZZKYLE MENU 1 ITEM TEXT: ItemText\n TYPE: menu CREATOR: DIMICELI,RON\n PACKAGE: 283 COLUMN WIDTH: 26\n MNEMONIC WIDTH: 4\nITEM: ZZKYLE ACTION 1 MNEMONIC: ZZ <== 1st Item\n SEQUENCE: 1\n \nThree patches that deleted protocols have been identified. The protocols \nITEM: ZZJACK <== 2nd Item (Bogus)\nITEM: 195 <== Broken Pointer\nITEM: ZZKYLE ACTION 4 <== 4th Item\n HEADER: D SHOW^VALM MENU PROMPT: Select ZZ Action:\n TIMESTAMP: 57379,39444\n \n \nSTEP 3: In the above figure (Figure 3), it was verify that the 1st ITEM, \nZZKYLE ACTION 1, should be attached to this protocol. The 2nd ITEM, ZZJACK, \nis discovered to belong to a different protocol entry and should be removed \ndeleted in these patches may have resulted in broken pointers. However, there \nfrom this entry. Use FM to manually remove it from the multiple attached to \nthis protocol (shown in figure 5). The 3rd ITEM is broken and XQ3 will clean \nit out (shown in figure 4). The 4th ITEM is verified as valid.\n \n \nFIGURE 4: Execute ENASK^XQ3 setting "%=2" from programmers mode.\n \nNXT,KDE>S %=2 D ENASK^XQ3\nDo you want to remove any 'Dangling Pointers' from your PROTOCOL File? Y// Y\n \nis a possibility that a newly created protocol could reuse same IEN as the \nPLEASE WAIT while I check this out . . . \n \nOption ZZKYLE MENU 1 points to missing option 195\nYour PROTOCOL File is OK now (1 pointer fixed).\n \n \nNXT,KDE>D P^DI\n \nVA FileMan 21.0\n \ndeleted one, and thus cover-up the broken pointer. Sites will need to \nSelect OPTION: 5 INQUIRE TO FILE ENTRIES\nOUTPUT FROM WHAT FILE: PROTOCOL// \nSelect PROTOCOL NAME: ZZKYLE MENU 1 ItemText \nANOTHER ONE: \nSTANDARD CAPTIONED OUTPUT? Yes// (Yes)\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \nComputed Fields\n \nNAME: ZZKYLE MENU 1 ITEM TEXT: ItemText\n TYPE: menu CREATOR: DIMICELI,RON\nmanually ensure that a newly created protocol hasn't overwritten any of the \n PACKAGE: 283 COLUMN WIDTH: 26\n MNEMONIC WIDTH: 4\nITEM: ZZKYLE ACTION 1 MNEMONIC: ZZ <== 1st Item\n SEQUENCE: 1\nITEM: ZZJACK <== 2nd Item (Bogus)\nITEM: ZZKYLE ACTION 4 <== 3rd Item (was 4th)\n HEADER: D SHOW^VALM MENU PROMPT: Select ZZ Action:\n TIMESTAMP: 57379,39444\n \n \nbroken ones. The three patches are identified below along with ITEM's (field \nFIGURE 5: Use FM to remove the bogus protocol, ZZJACK.\n \nNXT,KDE>D P^DI\n \nVA FileMan 21.0\n \nSelect OPTION: 1 ENTER OR EDIT FILE ENTRIES\nINPUT TO WHAT FILE: PROTOCOL// \nEDIT WHICH FIELD: ALL// 10 ITEM (multiple)\n EDIT WHICH ITEM SUB-FIELD: ALL// .01 ITEM \n#10 multiple) that one can reasonably expect to find attached to the \n THEN EDIT ITEM SUB-FIELD: \nTHEN EDIT FIELD: \n \nSelect PROTOCOL NAME: ZZKYLE MENU 1 ItemText \nSelect ITEM: ZZKYLE ACTION 4// ZZJACK BOGUS PROTOCOL ENTRY \n ...OK? Yes// (Yes)\n ITEM: ZZJACK// @\n \n SURE YOU WANT TO DELETE THE ENTIRE ITEM? Y (Yes)\n \nprotocols. Figures 1-5 below the ITEM listings are simulations where two \nSelect ITEM: \n \nSelect PROTOCOL NAME: \n \nSelect OPTION: 5 INQUIRE TO FILE ENTRIES\n \nOUTPUT FROM WHAT FILE: PROTOCOL// \nSelect PROTOCOL NAME: ZZKYLE MENU 1 ItemText \nANOTHER ONE: \nSTANDARD CAPTIONED OUTPUT? Yes// (Yes)\nbroken pointers were created and one was covered up with a newly created \nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \nComputed Fields\n\nNAME: ZZKYLE MENU 1 ITEM TEXT: ItemText\n TYPE: menu CREATOR: DIMICELI,RON\n PACKAGE: 283 COLUMN WIDTH: 26\n MNEMONIC WIDTH: 4\nITEM: ZZKYLE ACTION 1 MNEMONIC: ZZ <== 1st Item\n SEQUENCE: 1\nITEM: ZZKYLE ACTION 4 <== 2nd Item (Was 4th)\nprotocol. The STEPs associated with the figures are the actions needed to \n HEADER: D SHOW^VALM MENU PROMPT: Select ZZ Action:\n TIMESTAMP: 57455,50320\n \n \nDESCRIPTION\ncleanup the PROTOCOL file.\n \n \nPATCH DATE PROTOCOL (deleted) FOUND ON (file 101) \n=======================================================================\nPX*1.0*14 2/98 PXCE ADD/EDIT STOP CODE PXCE ADD/EDIT MENU\n \nDVBA*2.7*12 9/97 DVBA C SUPER QUIT DVBA C VIEW EXAMS (MENU)\n DVBA C VIEW EXAMS (MENU) no parent known\n DVBA C VIEW JUMP (ACTION) DVBA C VIEW EXAMS (MENU)\n============\n \nDG*5.3*140 2/98 EDR BDC CAPTURE EVENTS no parent known\n VAFED EDR INPATIENT CAPTURE DGPM MOVEMENT EVENTS\n VAFED EDR OUTPATIENT CAPTURE SDAM APPOINTMENT EVENTS\n \n \nNOTE: The parent protocol of the other two deleted AMIE protocols was also \ndeleted, DVBA C VIEW EXAMS (MENU). There should have been no negative impact \nfrom the AMIE patch. The EDR BDC CAPTURE EVENTS protocol was also determined \nnot to be a child of any known protocols.\nKIDS patch XU*8*68 fixed a bug when protocols were "Deleted at Site" resulting \n \nThe following depicts ITEMs that may reasonably be found on the protocols \nidentified above:\n \nITEMS:\n FOUND ON:\n PXCE ADD/EDIT MENU\n PXCE ADD/EDIT DISPLAY BRIEF\n PXCE ADD/EDIT DISPLAY DETAIL\n PXCE CPT ADD\nin broken (dangling) pointers within the PROTOCOL file (#101). Patch XU*8*80 \n PXCE DELETE V-FILE\n PXCE EDIT V-FILE\n PXCE ENCOUNTER EDIT\n PXCE EXAM ADD\n PXCE HEALTH FACTORS ADD\n PXCE IMMUNIZATION ADD\n PXCE PATIENT ED ADD\n PXCE POV ADD\n PXCE PROVIDER ADD\n PXCE QUIT\nwill give sites the ability to periodically search the PROTOCOL file for \n PXCE SKIN TEST ADD\n PXCE TREATMENT ADD\n PXCE ADD/EDIT INTERVIEW\n \n DGPM MOVEMENT EVENTS\n ORU PATIENT MOVMT\n ORU AUTOLIST\n DGPM TREATING SPECIALTY EVENT\n DGJ INCOMPLETE EVENT\n DGOERR NOTE\nbroken pointers and execute a routine (ENASK^XQ3) to automatically remove \n DG MEANS TEST DOM\n SD APPT STATUS\n IB CATEGORY C BILLING\n SC PCMM INPATIENT ACTIVITY\n SC ASSIGN PC TEAM ON DISCHARGE\n GMRADGPM MARK CHART\n PSJ OR PAT ADT\n DVB ADMISSION HINQ\n YS PATIENT MOVEMENT\n VSIT PATIENT STATUS\nthem. However, patches that were installed prior to XU*8*68 that deleted \n PSD PAT ADT\n VAFH HL7 INPATIENT CAPTURE\n VAFC HL7 INPATIENT CAPTURE\n FHWMAS (not nationally released)\n OR GUA DC GENERIC ORDERS\n OCX ORDER CHECK PATIENT MOVE\n \n SDAM APPOINTMENT EVENTS\n ORU PATIENT MOVMT\n DG MEANS TEST REQUIRED\n\n
\nThis patch is in support of CIRN. It will add fields to the Institution\nIncludes a routine with several APIs for the CIRN developers to use.\n option:\n Install Package(s) 'XU*8.0*43'\n =========\n \n\n =========================================================================\n\n\nSupported References\n\nPARENT^XUAF4(array, station, association) - for a specified institution which \nis the parent for this association type.\n\nINPUT Variables\nArray - As input, it is the $NAME reference for the Array name you want \n results back in. (This needs to be in your namespace)\nfile, an entry to the Facility Type file, and add new Institution file\nStation - The lookup value - either ien, station number, station name.\n If IEN it will need to have the ` in front of it.\nAssociation - The type of assocation from the Institution Association Types \n file. (in CIRN's case it is = VISN) \n\nOutput Variable - array("p",ien)=station name ^ station number\n\nNote: We have a business rule that institution can only have one parent per\nassociation.\n\nassociations.\nSIBLING^XUAF4(array, child ,association) - all sibling institutions of a\n given institution of a given association.\n\nINPUT Variables\nArray - As input it is the $NAME reference for the Array name you want \n results back in. (This needs to be in your namespace)\nChild - The lookup value - either ien, station number, station name. \n If IEN it will need to have the ` in front of it.\nAssociation - The type of assocation from the Institution Association Types \n file. (in CIRN's case it is = VISN)\n**NOTE: It will add all 22 VISN's in the format 'VISN xx' and\n\nOutput Variable - array("p",pien,"c",cien)=station name ^ station number\n\nNote: We have a business rule that institution can only have one parent per\nassociation.\n\nCHILDREN^XUAF4(array, parent, association) - for a specified parent return a \n list of all child institutions for a given association.\n \nInput Variables \nbuild the associations for each station in that VISN.\nArray - As input it is the $NAME reference for the Array name you want\n results back in. (This needs to be in your namespace)\nParent - The lookup value either ien, station number, station name. \n If IEN it will need to have the ` in front of it.\nAssociation - The type of assocation from the Institution Association Types \n file. (in CIRN's case it is = VISN)\n \nOutput Variable - array ("c" , ien)=station name ^ station number\n\nNNT^XUAF4(ien) - \n\n This will return the station name ^ station number ^ station type\n IEN - The pointer value into file 4.\n\nCIRN^XUAF4(inst [,value]) - This function returns the value of the CIRN \n enabled field from the institution file.\n\ninst - The pointer value (IEN) into file 4.\n\nvalue - (optional) Restricted to use by CIRN. This allows the setting of the\n field to a new value (Yes, No or @ to delete)\nThere is a new form OPTION; EVE:OPERATIONS:KERNEL:INSTITUTION to edit the\n\nOutput - "Yes", "No" or the empty string\n\n Checksum\nRoutine Old New 2nd Line\nXU8P43P 1825656 **43**\nXUAF4 1190987 **43**\n\n========================================================================= \nInstallation:\nInstitution file.\n\n 1. DSM sites - New routine.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peek time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n\n\nThis patch is being released by Capacity Management (CM) in anticipation\n \n \n \n NOTE: If you are a 'OpenM-NT' site, you must verify that the\n routine mapping configuration on each of your NT system(s)\n contains %ZO* or, at least, %ZOSV*.\n \n You MUST review the mapping configuration on ALL of your\n NT-VISTA Network configuration files (i.e., VANETA.DEF and\n VANETB.DEF).\n \nThis patch in conjunction with the future release of SAGG v 1.8 will\n If needed, you will also need to modify ALL of your\n NT-VISTA Network configuration files (i.e., VANETA.DEF and\n VANETB.DEF).\n \n Use the following instructions to complete this task:\n \n On the 'Open M NextGen Thin Client' buttons, click on the\n 'Configure Open M' (i.e., Wizard) button.\n \n On the top menu line of the 'Open M Configurations' window:\nsupport the collection of global growth data from the following operating\n \n Select File\n -\n Edit Network Configuration...\n \n On the top menu line of the 'Open M - Namespace/Network\n Configuration' window:\n \n Select File\n -\nsystem platforms: DSM, MSM and OpenM-NT.\n Open Configuration [Remote]...\n \n A 'Choose Connection' window opens:\n \n Choose the appropriate 'Connection' to your NT system\n \n Click the 'OK' button\n \n Select the correct system from the 'File Name' box\n \n \n *** You will need to review ALL of your ***\n *** VISTA configurations ***\n \n Click the 'OK' button\n \n Click on the 'Routine Mapping' radial button -> o\n \n Review the entries and ensure that the following is\n present:\n \nThis patch distribution will be adding new %ZOSV* routines to the system\n Routines Type Destination Location\n -------- ---- --------------------\n %ZO* ALL ROU\n (or, at least, %ZOSV*)\n \n If the above is present, continue to Step 8.\n \n However, if the above is NOT present, click the 'Insert\n Mapping' button and add %ZO* to the routine mapping list.\n \nspecific manager routine set. The accompanying installation instructions\n Then, on the top menu line of the 'Open M Namespace/Network\n Configuration' window:\n \n Select File\n -\n Save Configuration\n \n Restart OpenM after making this change on ALL VISTA\n configurations of the OpenM-NT cluster.\n \nwill guide you in adding these routines to your system.\n Review ALL of your NT-VISTA configurations and make the\n appropriate modifications, if necessary.\n \n After restarting your OpenM systems, you will log into the\n VAH UCI to complete the next step.\n \n \n 8. All sites must run the KMPLOAD routine in order to rename the\n system specific collection routines to the %ZOSVK-namespace.\n \n \n \n NOTE: If you are a 'DSM for OpenVMS' site, you must have\n performed Step 7 and be logged into the MCR UCI in order to\n complete this step as shown below.\n \n NOTE: If you are a 'MSM-DOS' site, you must have performed Step 7\n and be logged into the MGR UCI. You must run this routine\n on all MGR UCIs on every CPU, such as, compute, print, file\n and shadow servers as shown below.\n \nThis distribution also contains two routines within the new KMP*\n NOTE: If you are an 'OpenM-NT' site, you must have verified the\n routine mapping for every node configuration as outlined in\n Step 7. You must be logged into the VAH UCI in order to\n complete this step as shown below.\n \n \n Now, once logged into the appropiate UCI as defined above for your\n site, run the KMPLOAD routine.\n \n > D ^KMPLOAD\nof the national release of the Resource Usage Monitor (RUM) Version 1.0\nnamespace:\n \n Loading ZOSVKRx Saved as %ZOSVKR\n Loading ZOSVKSxE Saved as %ZOSVKSE\n Loading ZOSVKSxS Saved as %ZOSVKSS\n \n Finished\n \n \n NOTE: The above listing of routines is only shown as an example.\n The listing that you will obtain will vary depending on your\n \n system configuration.\n \n \n 9. The KMP* and %ZOSVK* namespaced routines are NOT recommended to\n be mapped.\n KMPENV An environment check routine which determines which system\n specific collection routines should be installed. The\n system variable ^%ZOSF("OS") will be used to determine the\n type of sysem on which this distribution is running.\n \n KMPLOAD A loader routine that will be used to rename the ZOSVK*\n routines to %ZOSVK*.\n \nand Statistical Analysis of Global Growth (SAGG) Version 1.8 software\nThe KMP* namespace has been designated for the use of Capacity Management\nroutines. Both of these routines are only necessary for the installation\nof this distribution and can be deleted after successful completion of\nthis patch.\n \n \nInstallation:\n============\n \nThe installation of this patch does not affect any options. Therefore,\npackages.\nthis installation can be performed at any time of the day with minimal\ndisruption to users. Provided the information that is listed immediately\nbelow does NOT apply to your site's configuration, installation should not\ntake longer than 10-15 minutes.\n \n \nNOTE: If you are an 'OpenM-NT' site, review the 'NOTE' section in Step 7\n to determine if additional preparation work is necessary.\n \n \n \n 1. You will not need to review your mapped routine sets.\n \n \n 2. Load the patch distribution onto your system by following these\n instructions:\n \n Enter 'X' at the 'Select MESSAGE Action: IGNORE//' (or DELETE//)\n mail prompt and select the 'INSTALL/CHECK MESSAGE' option.\n \n \nThis patch will not affect the current versions of the RUM and SAGG\n 3. From the 'Kernel Installation & Distribution System' (KIDS) menu,\n select the 'Installation' menu.\n \n \n 4. You may now elect to use the following options: \n \n When prompted for the INSTALL NAME, enter XU*8.0*90\n =========\n \n a. Backup a Transport Global - this option will create a backup\nsoftware that is running at the sites. Therefore, all DSM, MSM and\n message of any routines exported with this release. It will\n NOT backup any other changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the\n release is installed. It compares all components of the\n release (routines, DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\nOpenM-NT sites are instructed to install this patch. Sites which had a\n transport global.\n \n \n 5. Use the 'Install Package(s)' option and select the package\n XU*8.0*90.\n =========\n \n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', you can respond with NO.\npre-release of SAGG v 1.8 should also install this patch.\n \n \n 7. If you are either a 'DSM for OpenVMS' or 'MSM-DOS' site, after\n successful completion of the installation, move and restore the\n KMPLOAD and ZOSVK* routines to the MGR UCI(s) with the ^%RS and\n ^%RR system routines.\n \n If you are a 'MSM-DOS' site, you must also move these routines to\n all MGR UCIs on every CPU, such as, compute, print, file and shadow\n servers. \n\n\n\n\n\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n ZISUTL Errors at Lake City/ Gainsville (a CIRN site) when \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n using the Direct Connect and a printer had been \n \n 4. Inhibit users from login into the system. (If you install when few\n user are on the system and the possibility of some CLOBER errors is\n acceptable then users can stay on the system.)\n Also place TASKMAN in a wait state.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*69'\n =========\n selected but not Opened and the XCSA routine made \n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n \n 8. After installing this patch, \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n ZIS,ZIS1,ZIS2,ZIS3,ZIS5,ZIS6,ZISC\n ZIS4MSM,ZIS4VXD,ZIS4ONT\n use of the USE^%ZISUTL call to restore IO variables. \n ZISS,ZISS1,ZISS2,ZISP\n ZISUTL\n ZISTCP\n ZTMGRSET\n And in the manager account, (OpenM sites remain in VAH)\n \n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 69\n \n ==\n \n 9. MSM sites move these routines to the MGR accounts on other CPU's.\n \n 10. ALL sites move routine XUINPCH to all other accounts that share the\n %ZIS global and "D POST69^XUINPCH" to clean-up the DD for that account.\n \n 11. DSM Sites, after patch has installed, rebuild your map set.\n \n 12. Enable user's login.\nTAM-0298-31594 ZISUTL Error at Tampa when saved device in Direct Connect\n Remove Taskman from WAIT State.\n \n=========================================================================\n\n had a IO="". Fixed by not saving device.\n \nMAN-0997-11116 ZIS4ONT Missing lines in spooler output.\n***************************************************************************\nSTC-0997-40029\n\nBRX-0496-11600 ZIS1 If a job is queued to a device name that isn't\n defined you get a UNDEF error at SETVAR^%ZIS1.\n This has been fixed.\n \n ZISTCP Trapping CLOSE errors without clearing $ECODE\n caused problems.\n Move the OpenM server code to ZISTCPS so the\n listen tag will work as a single thread server\nBecause the %ZIS global is a shared global between many accounts this patch\n under all OS's. This causes a change to mail-\n man routine XMRONT, part of patch XM*7.1*28.\n \nAIM-1097-N1741 ZIS4* When opening a slave device $X and $Y didn't\n ZIS3 get set to zero.\n \nE3R 10153 ZIS2 If a device has a Access Prohibited time the\n range was not displayed.\n \nISD-0197-71937 ZISS Getting some Execute fields with a $P when\nneeds to be installed in each account that access to the %ZIS global at the\n ZISS1 the complete node is needed.\n ZISS2\n ZISP\n\nWPB-0897-31818 ZISPL Under LIST spool document it would only show\n the HOME device as having printed anything.\n This was because the File was updated before\n the device was asked.\nBRK-1197-11008 The Spool data file wasn't getting cleaned up\n when the Spooler purge routine ran.\nsame time.\n \nCLA-0498-22781 ZIS6 Routine %ZIS6 was setting the wrong global for\n the resource slot sub-file zero node. This has\n been fixed, The post init will clean-up the\n ^%ZIS(3.54,n,1,0) nodes. The TRIGGER X-ref\n on the $I field of the device file was forceing\n new entries into the resource file. This has\n been fixed and the extra entries will be removed\n in the post init.\n\n***************************************************************************\nWith this Kernel patch we have deleted fields *FORM FEED, *BACK SPACE from \nthe device file. Removed the asterik from fields *MARGIN WIDTH, *PAGE LENGTH \nin the device file while changing the way they work\n \nFirst, the X-ref that stuffs these fields when the SUBTYPE field is edited\nwill be removed so that the MARGIN WIDTH and PAGE LENGTH fields can act as\noverrides to the Terminal Type file fields.\n \nThis way if the terminal type file is edited all devices that point to\nthis entry will get the new values right away, without having to re-index\nRead below about changes in how the MARGIN and PAGE LENGTH fields in the\nthe subtype field of the device file.\n \nIf a particular device has the same characteristics as others of the same\ntype but has a different paper size, a new terminal type will not be\nneeded.\n\n Checksum\nRoutine Old New 2nd Line\nXUDHRES 917964 1098608 **49,69**\nXUINPCH 3950316 4506459 **20,36,49,63,65,69**\ndevice file have changed.\nZIS 9308978 9534282 **18,23,69**\nZIS1 10316454 10963783 **18,49,69**\nZIS2 10804239 10569129 **69**\nZIS3 6450084 5727193 **18,36,69**\nZIS4MSM 7202298 7301961 **23,36,49,59,69**\nZIS4ONT 8238234 7540912 **34,59,69**\nZIS4VXD 8151150 7956394 **23,36,49,59,69**\nZIS5 7634324 7647180 **18,24,69**\nZIS6 9917028 9295013 **24,49,69**\nZISC 7980129 8004258 **24,36,49,69**\n***************************************************************************\nZISP 1595683 1756861 **69**\nZISPL 12813725 14330151 **23,69**\nZISPL1 8550686 8439616 **23,36,69**\nZISPL2 4088281 4750042 **23,36,69**\nZISS 8559518 8580158 **69**\nZISS1 7994076 7921540 **69**\nZISS2 845268 846028 **69**\nZISTCP 2660587 2862626 **36,34,59,69**\nZISUTL 2111550 2112295 **18,24,34,69**\nZTMGRSET 12724965 13594462 **34,36,69**\n\n
\nNOIS BEC-0296-21503 Taskman getting error after install of patch XU*8*13.\n \n 1. These routines is for MSM sites only. \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'\n 4. From the 'Installation Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n 5. Inhibit users from login into system. \nThis is only a issue for MSM sites, and then only for ones with\n 6. From the 'Installation Menu' of the KIDS menu, run the option 'Install\n Package(s)' Select the package 'XU*8.0*25' and proceed with install.\n 7. After installing this patch, you need to move the routine from \n your productions account to the manager account:\n ZOSVMSM\n and in the manager account rename\n ZOSVMSM to %ZOSV\n \n Example: ZL ZOSVMSM ZS %ZOSV\n \nLOG SYSTEM RT turned on. \n 8. On MSM move the routines to the other servers. \n 9. Enable user's login.\n========================================================================= \n \nroutine new checksum\nZOSVMSM 11540039\n \n========================================================================= \nInstallation:\n\n
\n XU*8*87\na bug that went out with that patch. Dayton discovered\nthat XQUIT processing did not work with queued options.\nFrankly, it never occurred to me that XQUIT would be \nused in that manner. They were publishing a report that\nthey did not want on holidays, so they set the XQUIT \nvariable in the Entry Action if it was a holiday.\n \n Checksums were obtained using CHECK^XTSUMBLD.\n \nRoutine Before After Patch List\n \n \nXQUIT 6864597 6972284 **46,87**\n \n============================================================\nInstallation Instructions:\n \n1. Users are allowed on the system, and this patch may be queued.\n \n2. This routine is not usually mapped, so you shouldn't have to\n disable mapping.\n Patch XU*8*46 should be installed before this one.\n \n3. Use the "Install/Check Message" option on the PackMan menu to \n load the package.\n \n4. On the KIDS menu use the following options:\n \n Veryify Checksums in Transport Global\n Print Transport Global (Optional)\n Compare Trasport Global to Current System\n Backup transport Global\n \n \n5. MSM sites answer 'YES' to the question: "Want to MOVE routines \n to other CPUs?" AXP sites answer 'NO'.\n \n6. Rebuild mapped set if necessary.\n This patch contains two new fields to the Option File\nXQUIT MESSAGE and XQUIT EXECUTABLE that were inadvertently\nleft out of Patch XU*8*46. The documentation for using\nthese fields is found in the option Kernel New Features.\n This patch also contians a simgle routine that fixes\n\n
\nBRX-0498-11226, SBY-0498-30822\nRoutine Old New 2nd Line\nXUTMKE1 3519416 2055344 **63,79**\nXUTMKE2 2696336 4239503 **63,79**\nZTER 19441177 19821674 **8,18,32,24,36,63,73,79**\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - One of these routines are usually mapped,\n so you will need to disable mapping for the effected routine.\nWhen using the remove a error screen user will get an error.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\nAdded a FORM to do the editing of Error Screens.\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Use "D ^XPDKRN" then\n\n Install Package(s) 'XU*8.0*79'\n =========\n \n \n 8. After installing this patch, \n DSM/MSM sites - you need to move one routines from \n your production account to each manager account:\n OpenM Sites - you don't need to move anything, skip this step.\n ZTER\n And in the manager account, (OpenM sites remain in VAH)\nComments about the counting of errors.\n \n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 79\n ==\n \n 9. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\n\nSCREEN^%ZTER was changed to count errors of "Don't Show" as well as\nthe "Don't Record".\n\n Checksum\n\n
\nThis patch is being released by Capacity Management (CM) in anticipation\n \n \n \n NOTE: If you are a 'OpenM-NT' site, you must verify that the\n routine mapping configuration on each of your NT system(s)\n contains %ZO* or, at least, %ZOSV*.\n \n You MUST review the mapping configuration on ALL of your\n NT-VISTA Network configuration files (i.e., VANETA.DEF and\n VANETB.DEF).\n \nThis patch in conjunction with the future release of SAGG v 1.8 will\n If needed, you will also need to modify ALL of your\n NT-VISTA Network configuration files (i.e., VANETA.DEF and\n VANETB.DEF).\n \n Use the following instructions to complete this task:\n \n On the 'Open M NextGen Thin Client' buttons, click on the\n 'Configure Open M' (i.e., Wizard) button.\n \n On the top menu line of the 'Open M Configurations' window:\nsupport the collection of global growth data from the following operating\n \n Select File\n -\n Edit Network Configuration...\n \n On the top menu line of the 'Open M - Namespace/Network\n Configuration' window:\n \n Select File\n -\nsystem platforms: DSM, MSM and OpenM-NT.\n Open Configuration [Remote]...\n \n A 'Choose Connection' window opens:\n \n Choose the appropriate 'Connection' to your NT system\n \n Click the 'OK' button\n \n Select the correct system from the 'File Name' box\n \n \n *** You will need to review ALL of your ***\n *** VISTA configurations ***\n \n Click the 'OK' button\n \n Click on the 'Routine Mapping' radial button -> o\n \n Review the entries and ensure that the following is\n present:\n \nThis patch distribution will be adding new %ZOSV* routines to the system\n Routines Type Destination Location\n -------- ---- --------------------\n %ZO* ALL ROU\n (or, at least, %ZOSV*)\n \n If the above is present, continue to Step 8.\n \n However, if the above is NOT present, click the 'Insert\n Mapping' button and add %ZO* to the routine mapping list.\n \nspecific manager routine set. The accompanying installation instructions\n Then, on the top menu line of the 'Open M Namespace/Network\n Configuration' window:\n \n Select File\n -\n Save Configuration\n \n Restart OpenM after making this change on ALL VISTA\n configurations of the OpenM-NT cluster.\n \nwill guide you in adding these routines to your system.\n Review ALL of your NT-VISTA configurations and make the\n appropriate modifications, if necessary.\n \n After restarting your OpenM systems, you will log into the\n VAH UCI to complete the next step.\n \n \n 8. All sites must run the KMPLOAD routine in order to rename the\n system specific collection routines to the %ZOSVK-namespace.\n \n \n \n NOTE: If you are a 'DSM for OpenVMS' site, you must have\n performed Step 7 and be logged into the MCR UCI in order to\n complete this step as shown below.\n \n NOTE: If you are a 'MSM-DOS' site, you must have performed Step 7\n and be logged into the MGR UCI. You must run this routine\n on all MGR UCIs on every CPU, such as, compute, print, file\n and shadow servers as shown below.\n \nThis distribution also contains two routines within the new KMP*\n NOTE: If you are an 'OpenM-NT' site, you must have verified the\n routine mapping for every node configuration as outlined in\n Step 7. You must be logged into the VAH UCI in order to\n complete this step as shown below.\n \n \n Now, once logged into the appropiate UCI as defined above for your\n site, run the KMPLOAD routine.\n \n > D ^KMPLOAD\nof the national release of the Resource Usage Monitor (RUM) Version 1.0\nnamespace:\n \n Loading ZOSVKRx Saved as %ZOSVKR\n Loading ZOSVKSxE Saved as %ZOSVKSE\n Loading ZOSVKSxS Saved as %ZOSVKSS\n \n Finished\n \n \n NOTE: The above listing of routines is only shown as an example.\n The listing that you will obtain will vary depending on your\n \n system configuration.\n \n \n 9. The KMP* and %ZOSVK* namespaced routines are NOT recommended to\n be mapped.\n KMPENV An environment check routine which determines which system\n specific collection routines should be installed. The\n system variable ^%ZOSF("OS") will be used to determine the\n type of sysem on which this distribution is running.\n \n KMPLOAD A loader routine that will be used to rename the ZOSVK*\n routines to %ZOSVK*.\n \nand Statistical Analysis of Global Growth (SAGG) Version 1.8 software\nThe KMP* namespace has been designated for the use of Capacity Management\nroutines. Both of these routines are only necessary for the installation\nof this distribution and can be deleted after successful completion of\nthis patch.\n \n \nInstallation:\n============\n \nThe installation of this patch does not affect any options. Therefore,\npackages.\nthis installation can be performed at any time of the day with minimal\ndisruption to users. Provided the information that is listed immediately\nbelow does NOT apply to your site's configuration, installation should not\ntake longer than 10-15 minutes.\n \n \nNOTE: If you are an 'OpenM-NT' site, review the 'NOTE' section in Step 7\n to determine if additional preparation work is necessary.\n \n \n \n 1. You will not need to review your mapped routine sets.\n \n \n 2. Load the patch distribution onto your system by following these\n instructions:\n \n Enter 'X' at the 'Select MESSAGE Action: IGNORE//' (or DELETE//)\n mail prompt and select the 'INSTALL/CHECK MESSAGE' option.\n \n \nThis patch will not affect the current versions of the RUM and SAGG\n 3. From the 'Kernel Installation & Distribution System' (KIDS) menu,\n select the 'Installation' menu.\n \n \n 4. You may now elect to use the following options: \n \n When prompted for the INSTALL NAME, enter XU*8.0*90\n =========\n \n a. Backup a Transport Global - this option will create a backup\nsoftware that is running at the sites. Therefore, all DSM, MSM and\n message of any routines exported with this release. It will\n NOT backup any other changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the\n release is installed. It compares all components of the\n release (routines, DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\nOpenM-NT sites are instructed to install this patch. Sites which had a\n transport global.\n \n \n 5. Use the 'Install Package(s)' option and select the package\n XU*8.0*90.\n =========\n \n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', you can respond with NO.\npre-release of SAGG v 1.8 should also install this patch.\n \n \n 7. If you are either a 'DSM for OpenVMS' or 'MSM-DOS' site, after\n successful completion of the installation, move and restore the\n KMPLOAD and ZOSVK* routines to the MGR UCI(s) with the ^%RS and\n ^%RR system routines.\n \n If you are a 'MSM-DOS' site, you must also move these routines to\n all MGR UCIs on every CPU, such as, compute, print, file and shadow\n servers. \n\n\nFor ALPHA/NT OpenM/Cache sites, these routines were included in\nwill not cause any problems.\n\n Checksum\nRoutine Old New 2nd Line\nXGKB 3707191 3850098 **34**\nXUCIONT 2479520 **34**\nZISFONT 4576199 **34**\nZISHONT 5001907 5018937 **34,65,84**\nZOSFONT 6905729 **34**\nZOSVONT 5179039 **34**\nthe KRN_ONT_34.RTN file(s) that were used as part of the conversion\nZTMGRSET 13364303 13594462 **34,36,69**\nZUONT 1897334 1794899 **34**\n\n =========================================================================\n Installation:\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\nprocess to OpenM/Cache. This file went through several revisions \n system. You now need to use KIDS to install the Transport global.\n \n 3. Users can remain on the system. This patch can be loaded any\n non-peek time.\n This patch can NOT be queued.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\nduring the course of the project so depending on when a site\n Print Transport Global\n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) 'XU*8.0*34'\n =========\n \n 5. *** OpenM sites ONLY *** After installing this patch.\n a. You need to rename ZUONT to ZU.\n b. DO RELOAD^ZTMGRSET\n Select the System\nconverted, the old checksums for these routines may vary from what\n Patch number to load: 34\n ==\n \n =========================================================================\n\nthis patch indicates. Avaliable Jobs and Act Jobs adjusted to work\nwith both OpenM (NextGen Build52e) and Cache.\n\nThis patch is only needed by OpenM sites, Installing at other sites\n\n
\nDBIA XUSER New file 200 API for DSS.\n of IEN's for file 4 that have been assigned to the user.\n\n Checksum\nRoutine Old New 2nd Line\nXUSER 1279527 1441396 **75,97**\n \n=========================================================================\nInstallation:\n\n 1. DSM sites - This routine may be mapped, if so you will need\n The call is S X=$$DIV4^XUSER(.ZZ[,duz])\n to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Input: The first parameter is a local variable that\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n is passed by reference. \n Use "D ^XPDKRN" then ***\n Install Package(s) 'XU*8.0*97'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\n The second is optional a IEN to the New Person file.\n\n If not passed it defaults to the current DUZ.\n Outout: Returns a 1 if the user has a Division entry\n in the New Person file, else returns 0.\n If it returns a 1 then the first parameter is an array\n\n
\n Patch XU*8*81 should be installed first.\n Checksums were calculated by CHECK^XTSUMBLD\n \n The first line of your routine should look like this:\n ;;8.0;KERNEL;**81,89**;Jul 10, 1995\n \nRoutine Before After Patch List\n \nXQ8 12888022 11887347 **81,89**\n \n============================================================\n \nInstallation Instructions:\n \n1. Users are allowed on the system, and this patch may be queued.\n \n2. This routine is not usually mapped, so you shouldn't have to\n disable mapping.\n \n3. Use the "Install/Check Message" option on the PackMan menu to \n load the package.\n \n This patch contains 1 routine that has been modified to correct\n4. On the KIDS menu use the following options:\n \n Veryify Checksums in Transport Global\n Print Transport Global (Optional)\n Compare Trasport Global to Current System\n Backup transport Global\n \n5. MSM sites answer 'YES' to the question: "Want to MOVE routines \n to other CPUs?" AXP sites answer 'NO'.\n \na problem encountered by the menu rebuild system. Under certain\n6. Rebuild mapped set if necessary.\ncircumstances the Common Options in the menu XUCOMMAND were not being\ntime-stamped properly, causing this menu to be rebuilt frequently and\nunnecessarily. This could result in an <UNDEFINED> error while the menu \nwas being rebuilt.\n \n\n
\nWPB-0598-31519 XUTM* When listing tasks, a 2 digit year was used in the\n checking the OOS field on the OLD device.\n Changed to allow longer $I's in OpenM.\n \nTAM-1098-31054 XUTMRP1 Was failing to clear a Lock on each task repointed.\n \nMON-0798-50789 XLFDT2 If a task had a requeue schedule of "1M", the\nFAR-0798-40749 time for rescheduling would be lost.\n Fixed to correctly bring forward the schedule time.\n \nBRK-0998-11910 ZTER When checking for SCREENED errors, only the first\n display. There shouldn't be any confusion with\nOKL-0998-71037 XUTMKE string in the list was checked. Taskman error\nCIN-0998-42052 display updated to use the new screening list.\n \n \n Checksum\nRoutine Old New 2nd Line\nXLFDT2 3530137 3530137 **71,86**\nXUTMKE 11733011 11960485 **86**\nXUTMRP 15458022 15705216 **2,20,86**\nXUTMRP1 6998776 7012212 **2,86**\n a task scheduled for 2000 being mistaken for 1900.\nXUTMTP 10672535 10473436 **20,86**\nXUTMTR1 13285469 12285561 **86**\nXUTMTR2 9481244 8489866 **86**\nXUTMUSE2 13026855 13051739 **36,86**\nZTER 19821674 19873831 **8,18,32,24,36,63,73,79,86**\n\nList of preceding patches: 2, 8, 18, 20, 24, 32, 36, 63, 71, 73, 79\nChecksum's calculated by CHECK^XTSUMBLD\n\n========================================================================= \n This NOIS pointed out that 2097 could be mistaken\nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n for 1997 and make user wonder why the task was so\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system.\n \n late. Reports now use 4 digit years.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*86'\n =========\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. After installing this patch,\n OpenM Sites - you don't need to move anything, skip this step. \n \n DSM/MSM sites - you need to move one routine from \n your production account to each manager account:\n \n ZTER\n \n 7. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 86\nBRX-0298-12277 XUTMRP User would get an UNDEF if trying to re-point a\n ==\n \n 8. DSM Sites, after patch has installed, rebuild your map set.\n\n=========================================================================\n\n device that was OUT-OF-SERVICE. Fixed by not\n\n
\nThis build fixes an <UNDEF> error that sometimes occurred when\ntransferring a users' keys.\n\n
\nThis patch is in support of the new Capacity Management namespace KMPR.\n\n ZOSVKRV\n ZOSVKSME\n ZOSVKSMS\n ZOSVKSOE\n ZOSVKSOS\n ZOSVKSVE\n ZOSVKSVS\n\n 8. And in the manager account, (OpenM sites remain in VAH)\n All sites:\nThe ZOSVKR* and ZOSVKS* are included unchanged at the request of the DBA.\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 94\n ==\n \n 9. DSM Sites, after patch has installed, rebuild your map set.\n 10. Enable user's login.\n Remove TASKMAN from the wait state.\n\n\nThese routines were introduced with patch XU*8*90. Patch XU*8*90\n=========================================================================\n\ninstalled certain ZOSVKR* and ZOSVKS* routines based on your platform's\noperating system. Please do not be alarmed if you are notified prior to\ninstalling patch XU*8*94 that certain ZOSVKR* and ZOSVKS* routine do not\nexist in your account.\n\nMWV-0398-21933 ZTMS3 Add to the after task cleanup IO("P"),IO("DOC")\n so they can't upset re-queuing of following tasks.\nThe Kernel routines will call ^%ZOSVKR through %ZOSV and the XQOR routines\n\n Checksum\nRoutine Old New 2nd Line\nXQ 14125950 14125950 **9,46**\nXQOR1 11515076 11260336 **48,56,94**\nXQORO 13000044 11424424 **48,56,94**\nXUTMG43 921517 844913 **18,65,94**\nZOSVKRM 186974 **90,94**\nZOSVKRO 186974 **90,94**\nZOSVKRV 5026320 **90,94**\nwill call %ZOSVKR directly.\nZOSVKSME 4496261 **90,94**\nZOSVKSMS 2730370 **90,94**\nZOSVKSOE 6067956 **90,94**\nZOSVKSOS 14826279 **90,94**\nZOSVKSVE 9688078 **90,94**\nZOSVKSVS 4925185 **90,94**\nZOSVMSM 11538678 10267389 **13,25,49,94**\nZOSVONT 5179039 5191213 **34,94**\nZOSVVXD 7782508 5822652 **13,65,71,94**\nZTMGRSET 13594462 14184637 **34,36,69,94**\n\nZTMS 5366119 5281307 **2,18,24,36,67,94**\nZTMS3 10241859 10008753 **1,18,36,49,64,67,94**\nZUMSM 2252648 2427019 **13,42,49,94**\nZUONT 1794899 1969174 **34,94**\nZUVXD 4645869 4462372 **13,24,84,94**\n\nList of preceding patches: 1, 2, 9, 13, 18, 24, 25, 34, 36, 42, 46, 48, 49\n56, 64, 65, 67, 69, 71, 84, 90\nChecksum's calculated by CHECK^XTSUMBLD\n\nThe %ZOSV routine has been modified to call the new %ZOSVKR routine.\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\nThis should help protect folks outside of the VA who use VistA.\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n \n users are on the system and the possibility of some CLOBER errors is\n acceptable, then users can stay on the system.)\n Also place TASKMAN in a wait state, and stop submanagers.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*94'\n =========\n \n No Options or Protocols need to be placed out-of-order.\nThe ZTMGRSET routine has been updated to save the new routine under the\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. After installing this patch, \n DSM sites rename ZUVXD to ZU.\n OpenM sites rename ZUONT to ZU.\n MSM sites rename ZUMSM to ZU.\n \n 7. OpenM Sites - you don't need to move anything, skip this step.\n DSM/MSM sites - you need to move several routines from \ncorrect name.\n your production account to each manager account:\n \n ZTMGRSET\n ZTMS\n ZTMS3\n ZOSVMSM\n ZOSVONT\n ZOSVVXD\n ZOSVKRM\n ZOSVKRO\n\n\nISL-0598-50691 XUSRB When a GUI-Broker process exited the M system\n its context when completing the sign-on.\n \n XQCS These two routines improve the interface between \n XQSET the Remote Proceedure Call (RPC) Broker and the \n traditional Menu System. With this patch installed \n sites will be able to mark Broker-type options \n out-of-order, lock them with keys and reverse keys, \n and restrict the days and times during which they \n are allowed to run.\n\n it failed to clean-up the temp globals\n \n Checksum\nRoutine Old New 2nd Line\nXQCS 9069982 12754137 **15,28,82**\nXQSET 11570399 11252847 **28,82**\nXUSRB 5125201 5576613 **11,16,28,32,59,70,82**\nXUSRB1 9903269 10103967 **28,82**\n\nList of preceding patches: 11, 15, 16, 28, 32, 59, 70\nChecksum's calculated by CHECK^XTSUMBLD\n as roll and scroll M processes do.\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines may be mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n It was discovered that not all local Broker \n 4. Stop the Broker server. (If you install when few users are on the \n system and the possibility of some CLOBER errors is acceptable, \n then users can stay on the system.)\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*82'\n =========\n \n development was making the call to establish \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n Restart the Broker server.\n\n===========================================================================\n\n an application context. They were just adding\n the local RPC to the SIGN-ON context. This \n loophole has been fixed by having sign-on remove\n\n
\n Please see the Patch Module on FORUM for a detailed description.\n\n
\nThis patch is dsigned to allow a site to cleanup all dangling pointer\nassociated with their county codes in their Patient, person, Fee basis\nVendor and HBHC Patient files.\n\n
\nPCE PCE has it's own Location file (#9999999.06) which\nXUINPCH 4506459 5067911 **20,36,49,63,65,69,96**\n\nTHIS ROUTINE ONLY CARRIES POST-INIT CODE\nChecksum's calculated by CHECK^XTSUMBLD\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n points to the institution file. This file needs to\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n be updated whenever a entry is added to or deleted from \n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. This patch can be queued and installed at any time.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n\n the institution file. The PCE file will be updated \n Install Package(s) 'XU*8.0*96'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n=========================================================================\n\n to include all current entries in file 4.\n See DBIA 1039\n \n Checksum\nRoutine Old New 2nd Line\n\n
\n XQ The XQ routine in patch XU*8*94 did not have \n\n Checksum\nRoutine Old New 2nd Line\nXQ 14125950 14095659 **9,46,94,103**\n\nList of preceding patches: 9, 46, 94\nSites should use CHECK^XTSUMBLD to verify checksums\n \n========================================================================= \nInstallation:\n the changes included. It was changed back to\n\n 1. DSM sites - This routine is usually mapped,\n so you will need to disable mapping for the affected routine. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n its "before" state accidentally. While this \n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (Anybody using an option\n will get a CLOBER error when they return to the menus.)\n\n did not cause any operational problems. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*103'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n The changes still need to get out to the field.\n 6. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\n\n \nRoutine Summary\nSecond line\n ;;8.0;KERNEL;**9,46,94,103**;Jul 10, 1995\n\n
\nASH-1098-30259 The Option REMOVE A TYPE OF ERROR pointed to\n \nE3R 11300 XUWORKDY The E3R included the code for 2 new entry points\n in XUWORKDY.\n \n $$WORKDAY^XUWORKDY(date) returns 1 if the day is a\n workday (Mon-Fri and not a Holiday) else 0,\n \n $$WORKPLUS(date,offset) given a date and a offset\n in days +/-, returns the date that will give\n that number of workdays.\nBRX-0898-11548 the wrong routine. Corrected.\n \nANN-0798-40365 The screen on file 3.5 is not compatible with FM\n relational jumps to file 3.2 during prints.\n Changed to work in this environment.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\nMAC-0698-62282\n Checksum\nRoutine Old New 2nd Line\nXQALFWD 10058961 10528433 **6,65,91**\nXUINPCH 5067911 5067911 **20,36,49,63,65,69,96,91**\nXUWORKDY 908391 1501394 **65,71,77,91**\n\nList of preceding patches: 6, 20, 36, 49, 63, 65, 69, 71, 77, 96\nSites should use CHECK^XTSUMBLD to verify checksums\n\n============================================================================\n \nInstallation:\n\n 1. DSM sites - One of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\nPUG-0498-52588 XQALFWD The input to the Comment field didn't follow\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors are\n VA guidelines and allow ? or ?? for help. Fixed. \n acceptable in the XQALFWD routine, then users can stay on the system.)\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*91'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\n\nBIL-0797-30082 XQALFWD The code at MAIL1 wouldn't allow forwarding\n of alert to a mail message.\n\n
\n**Note that the KERNEL 8.0 install had a separate file for the MGR routines\nHOU-1198-72017 ZIS2 If a device had the QUEUEING field set to NOT\n ZOSFONT\n ZTMS1\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 104\n ===\n \n ZIS1 ALLOWED and queuing was selected, the device\n 10. DSM Sites, after patch has installed, rebuild your map set.\n 11. Enable user's login.\n Remove TASKMAN from the wait state.\n\n\n=========================================================================\n would be selected with just the IO("Q") flag\n cleared. This patch will cause the user to be\n reasked the device question.\n \nWNY-0398-11876 ZISFVXD The %ZISF routine wasn't making consistent use\nSAM-1098-22294 ZISFMSM of the HFS default directory.\nLEB-1198-20188 See F# 26562896\n \n**and then cleaned up un-needed routines, because of this you may not\nCPRS ZISHMSM The call to OPEN^%ZISH wasn't setting the IO\n ZISHONT subtype variables to appropriate values. \n ZISHVXD Now they will default to P-OTHER 132 by 60.\n \n ZOSFONT Avanti team, Do not allow HIGH priority on Cache.\n \nHL7 team ZTMS1 When running dual taskman on DSM systems, if a \n task requests to run on the other node from the\n one that picks it up, then the task is placed\n in the "C" list and is lost. This is fixed\n**have copies of routine not needed by your system\n by having the sub-manager look in the "C" list\n as part of its checking for work to do.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;JUL 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\n \nZIS1 10963783 10911260 **18,49,69,104**\nZIS2 10569129 10396923 **69,104**\nZIS3 5727193 6138459 **18,36,69,104**\nZISFMSM 4473223 4796822 **104**\nZISFVXD 5940026 6059078 **104**\nZISHMSM 5978186 6060577 **24,36,49,65,84,104**\nZISHONT 5018937 5114296 **34,65,84,104**\nZISHVXD 7237979 7315736 **24,36,65,84,104**\nZOSFONT 6905729 6981333 **34,104**\nZTMS1 6234917 6242844 **36,49,104**\nBRX-0898-12101 ZIS2 If a device had the Out Of Service field set, the\n\nList of preceding patches: 18, 24, 34, 36, 49, 65, 69, 84\nSites should use CHECK^XTSUMBLD to verify checksums\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n user was asked if this was OK. The outcome was that\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n the user could queue to a device that was OOS.\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors is\n acceptable, then users can stay on the system.) The risk is users or\n tasks that are in the Device Handler at install time. \n Also place TASKMAN in a wait state.\n \n 5. D ^XPDKRN\n This change will make OOS devices unavailable.\n Install Package(s) 'XU*8.0*104'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\n OpenM Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n\n your production account to each manager account:\n \n ZIS1\n ZIS2\n ZIS3\n ZISFMSM\n ZISFVXD\n ZISHMSM\n ZISHONT\n ZISHVXD\n\n\nNOIS IVM-1295-30057 If printing a spool document to a slave device the\ntasks it was still using the old $H format. (Cross CPU and waiting HFS)\n\nWhen investigating another problem I notice that the load balance algorithm\nwould allow more that one system to start new work. This was fixed by having\nthe node that was going to start new work to tell the other nodes to wait.\n\nEric Jurasas, Change to %ZIS to work with TelNet virtual terminal on MSM 4.3\n\nroutine new checksum\nZIS 9308978\nthe question about the number of copies would go to the slave device.\nZIS4DTM 7025909\nZIS4MSM 6576195\nZIS4MSQ 8966654\nZIS4VXD 8256988\nZISPL 12813725\nZISPL1 8860672\nZISPL2 4292041\nZTM2 3666292\nZTM6 1889159\nZTMS2 5278281\nTo fix the number of copies prompt was moved before the device prompt.\n\n========================================================================= \nInstallation:\n\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n 4. Inhibit users from login into system. \n Also place TASKMAN in a wait state.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n options:\nNOIS ANN-0296-40311 The ZISPL* routines were still looking at the old\n Install Package(s) 'XU*8.0*23'\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. After installing this patch, you need to move several routines from \n your productions account to the manager account:\n ZIS\n ZIS4DTM\n ZIS4MSM\n ZIS4MSQ\n ZIS4VXD\nKernel site parameter file. Fixed by having them and %ZIS4 look at the\n ZTM2\n ZTM6\n ZTMS2\n and in the manager account rename\n ZIS to %ZIS\n ZTM2 to %ZTM2\n ZTM6 to %ZTM6\n ZTMS2 to %ZTMS2\n ZIS4VXD to %ZIS4 (for DSM sites)\n ZIS4MSM to %ZIS4 (for MSM sites)\nnew Kernel system parameter file.\n \n Example: ZL ZOSVVXD ZS %ZOSV\n \n 8. AXP Sites, after patch has installed, rebuild your map set.\n 9. Enable user's login.\n Remove TASKMAN from the wait state.\n\n=========================================================================\n\n\nNOIS ALT-1195-20982 When taskman would internally set new run times for\n\n
\nHIN-1298-40427 XUSRB A convoluted link with patch XU*8*69 is causing\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 05, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXUSRB 5576613 5738122 **11,16,28,32,59,70,82,109**\n\n problems in CPRS at DSM sites. The error is\nList of preceding patches: 11, 16, 28, 32, 59, 70, 82\nSites should use CHECK^XTSUMBLD to verify checksums\n\n========================================================================= \nInstallation:\n\n\n 1. DSM sites - This routines is usually mapped,\n so you will need to disable mapping for the affected routines. \n \n %DSM-E-DEVNOTOPN at QUIT^%ZIS6 with IO(0) null.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n This only happens at DSM sites that do not have\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. \n Stop the Broker server(s).\n "DO STOP^XWBTCP(<socket>)" on each node that has Broker running.\n (If you install when few users are on the system and the possibility \n of some CLOBER/NOSOURCE errors is acceptable, Leave the Broker \n running and queue the install for after hours.)\n\n auto sign-on disabled. The code that calls the\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n\n Install Package(s) 'XU*8.0*109'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n client agent mades a call to HOME^%ZIS and TCP\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n If the Broker was stopped, Remember to restart it.\n "DO STRT^XWBTCP(<socket>)" on each Broker node.\n =========================================================================\n\n connection don't work as a home device. The fix \n is to have the XUSRB save the NULL device as the \n HOME device before the call to Client agent.\n\n
\nThis patch contains KERNEL updates for the RUM package. \n 2. Now checks to see if RUM is turned on before continuing.\n 3. Calls %ZOSVKR through new label RU().\n \nZOSVONT A change to allow opening TCP/IP devices from %ZIS.\n DEVOK will not try and open CHANNEL type devices.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 21, 1998\nChanges to %ZOSVKR\n\n Checksum\nRoutine Old New 2nd Line\nZOSVKRM 186974 217494 **90,94,107**\nZOSVKRO 186974 217494 **90,94,107**\nZOSVKRV 5026320 5456477 **90,94,107**\nZOSVMSM 11538678 10431698 **13,25,49,94,107**\nZOSVONT 5179039 5510564 **34,94,107**\nZOSVVXD 7782508 6011813 **13,65,71,94,107**\nZUMSM 2252648 3349196 **13,42,49,94,107**\n 1. New label 'RU(KMPROPT,KMPRTYP,KMPRSTAT)' is introduced. All calls to \n\nList of preceding patches: 13, 25, 34, 42, 49, 65, 71, 90, 94\nSites should use CHECK^XTSUMBLD to verify checksums\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n %ZOSVKR will now go through this label.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n 2. %ZOSVKR now collects data on a daily basis only (previous versions \n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded at any\n non-peak time.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*107'\n ==========\n collected data hourly).\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\n OpenM Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n \n\n ZOSVKRM\n ZOSVKRO\n ZOSVKRV\n ZOSVMSM\n ZOSVONT\n ZOSVVXD\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n DO RELOAD^ZTMGRSET\nChanges to LOGRSRC^%ZOSV\n Select the System\n Patch number to load: 107\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n ***MSM Sites "ZL ZUMSM ZS ZU" **\n=========================================================================\n\n 1. Adds 2 new parameters: TYPE and STATUS.\n\n
\nNOIS RTN Description\nDAY-1098-42371 XUTMOPT "One time queueing" would allow queueing to devices\n that cannot be queued to. Checks were added to \n prevent this.\n \nBOS-0199-10157 XQALFWD When forwarding an alert, and no comment was entered\n the alert was not forwarded and the user did not \n know the alert wasn't sent.\n \nIND-1298-71717 XPARDD When making a call to EN^XPAR and the data is \n as a set of codes, sometimes it would talk. This\nLIT-1298-71717 XUS1 The code that logs users into the sign-on log\n unwanted behavior has been fixed. \n \n XUSTAT We found that XUSTAT had a reference to file 3.\n This has been changed to file 200.\n \nMIN-0199-40756 The Institution file still has some subfiles \n 49.01 and 49.02 that still point to file 3. \n These had been marked for deletion and now are \n deleted.\n \n is very old and if the current date/time was in\nALX-0199-71347 An error was occurring when a new entry was added\n to the Institution file because of the AD x-ref.\n The fix was to new the variable DS in the x-ref\n code.\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\n use, it would add 1 second to the time. With the\nRoutine Old New 2nd Line\nXQALFWD 10528433 10594990 **6,65,91,111**\nXUINPCH 5067911 5263885 **20,36,49,63,65,69,96,91,111**\nXUS1 10420726 10153593 **9,59,111**\nXUSTAT 12766906 12791683 **111**\nXUTMOPT 3629975 3867301 **2,111**\n\nList of preceding patches: 2, 6, 9, 20, 36, 49, 59, 63, 65, 69, 91, 96\nSites should use CHECK^XTSUMBLD to verify checksums\n========================================================================= \n large number of users and tasks that are logged\nInstallation:\n\n 1. DSM sites - Some of these routines maybe mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n these days it often would increment past 60 seconds\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n and sometimes past 60 minutes. The fix was to \n This patch can be queued for install at non-peak hours.\n\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*111'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n increment by 100th of a second.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n\n \n\n
\nSee Patch Module for details.\n\n
\n See Patch Module for details.\n\n
\nFOIA XVIRPOST This routine for setting up a DHCP system from\n\n \n ZIS\n ZIS1\n ZIS2\n ZTLOAD1\n ZTER\n ZTER1\n \n 9. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 112\n ===\n \n 10. DSM Sites, after patch has installed, rebuild your map set.\n 11. Enable user's login.\n\n\n=========================================================================\n FORUM XTER1A Addressed a conflict with XM*7.1*50 and sending\n\n error report as mail message.\n \n XLFSTR New function call added $$TRIM^XLFSTR(x[,"[L][R]"]).\n This call will trim spaces from the left, right\n or both of a input string.\n \nMWV-1298-22309 ZTLOAD1 It was possible for a task that was being requeued\n scratch still referenced files 3, 16. Fixed.\nMIW-0898-40133 to end up with a invalid device because of how\n %ZTLOAD was building the entry in the task global.\n \n WebTop ZIS Code to allow special applications to establish a\n Broker ZIS1 home device from the background. [F#28972403]\n \n Cache ZTER Added code to save a special Cache variable.\n ZTER1 Simplify some code in UNWIND.\n \n\n Requested by the DBA.\n FORUM ZIS2 Taskman was getting a subscript error because of\n a job tasked to a slave device. Fix was to check\n if IO="" and set POP it true.\n \n\n Request from DBA to add E-MAIL ADDRESS field to\n NEW PERSON file. Field .151 node .15\n To be used by IFCAP.\n \nRoutine Summary\n \nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;8.0;KERNEL;<patchlist>;Jul 10, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXLFSTR 1841692 2042372 **112**\nXTER1A 16315266 13449705 **63,112**\nXUAF4 1190987 1458355 **43,112**\nXUTMOPT 3867301 3807330 **2,111,112**\n XUAF4 Fixed in the $$LKUP API.\nXVIRPOST 4773190 3825342 **112**\nZIS 9534282 9454725 **18,23,69,112**\nZIS1 10963783 10540675 **18,49,69,104,112**\nZIS2 10569129 10140057 **69,104,112**\nZTER 19873831 18976906 **8,18,32,24,36,63,73,79,86,112**\nZTER1 5603505 4369079 **18,24,36,49,112**\nZTLOAD1 6320450 6628172 **112**\n\nList of preceding patches: 2, 8, 18, 23, 24, 32, 36, 43, 49, 63, 69, 73\n79, 86, 104, 111\n \nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Do not allow users to log in to the system during installation.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \nLAS-0399-60359 XUTMOPT In fixing the problem in NOIS DAY-1098-42371 I\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n broke "One time queueing" if a device wasn't needed.\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors is\n acceptable, then users can stay on the system.)\n \n 5. \n Use "D ^XPDKRN" then\n Install Package(s) 'XU*8.0*112'\n Now works correctly in both cases.\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 8. After installing this patch,\n OpenM Sites - you don't need to move anything, skip this step. \n DSM/MSM sites - you need to move several routines from \n your production account to each manager account:\n\n
\nThis patch is to re-namespace the routines called from within the protocol\nXQORDD1 6335340 **98**\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\nfile from OR* routine to XQOR* routines. It turns out that only 2\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nroutines and the compiled cross-references needed to be changed.\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors is\n acceptable, then users can stay on the system.)\n Also place TASKMAN in a wait state.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*98'\nThe 2 routine are ORDD101 to XQORD101 and ORDD1 to XQORDD1 and the X-ref\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\n\nfrom ORD1 to XQORC.\n\n Checksum\nRoutine Old New 2nd Line\nXQORD101 7689712 **98**\n\n
\nThis patch is being released by Capacity Management (CM) in anticipation\nThis distribution also contains the ZTMGRSET routine which will save the\nnew routine under the correct name.\n \n \nInstallation:\n============\n \n 1. DSM sites - Some of these routines are usually mapped, so you will\n need to disable mapping for the affected routines.\n \nof a future patch for the Statistical Analysis of Global Growth (SAGG)\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\nVersion 1.8 software package. A future SAGG patch will enable the\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER errors\n is accecptable, then users can stay on the system.) \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n \ncollection of disk capacity information from the sites.\n Install Package(s) 'XU*8.0*121'\n ==========\n \n No options or Protocols need to be placed out-of-order.\n \n Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO\n ==\n \n 6. OpenM sites - you do not need to move any routines, skip this step.\n \n \n DSM and MSM sites - you need to move several routines from your\n production account to each manager account.\n \n ZOSVKSD\n ZTMGRSET\n \n 7. And in the manager account, (OpenM sites remain in VAH)\n All sites:\n \nThis patch distrbution will be adding a new %ZOSVK* routine to the\n DO RELOAD^ZTMGRSET\n Select the System\n Patch number to load: 121\n ===\n 8. DSM sites - after patch has installed, rebuild your map set.\n \n 9. Enable user logins.\nsystem-specific manager routine set. The accompanying installation\ninstructions will guide you in adding these routines to your system.\n \n\n
\nKernel 8.0 is the latest release of VA Kernel software. This version\nsupersedes version 7.1.\n\n
\nThis is the basic package containing the KERNEL.\n\n
\nThis patch prevents a NULLSUBSCR error from occuring on inbound batch\nacknowledgments and corrects a problem with the format of the MSA segment.\n\n
\nThis patch fixes the problems as described in NOIS #BRX-0896-12049.\n \nRoutine Summary:\n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \nChecksums:\nThe problems come from the "date.time" subscript of the ^TMP("HL",\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ----------\n HLLP 13472823 13466846 1,12,29\n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n^TMP("HLR", and ^TMP("HLS", which is not correctly set to comply with\n==========================\n 1. Users are allowed to be on the system during the installation.\n 2. Stop all the HLLP logical links for v 1.5 interface. \n 3. AXP SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\nthe FileMan format.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*29\n =========\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 6. MSM Sites - Answer 'YES' to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites: Rebuild your mapped set if necessary.\n 8. Restart all the HLLP logical links which have been stopped at step\n 2.\n \nTest Sites:\n===========\n \n\n\nSee the National Patch Module on Forum.\n\n\n
\nSee the National Patch Module on Forum for a complete description.\n\n\n
\nPlease see the National Patch Module on Forum for a complete description.\n\n\n
\nPlease see the National Patch Module for the description.\n\n\n
\nPlease see the National Patch Module on Forum.\n\n\n
\nPlease see the National Patch Module on Forum for a complete description.\n\n\n
\nPlease seen the National Patch Module on Forum for a complete description.\n\n\n
\nThis patch adds a new entry into the Country Code file (#779.004) to\n 1. Users are allowed to be on the system during the installation.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \nsolve the problem as describled in NOIS ISF-0297-60099. This new entry\n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s)\n INSTALL NAME: HL*1.6*23\n ==========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n \n 4. MSM Sites - Answer 'NO' to the question 'Want to MOVE routines to\n other CPUs?'.\ncontains a 2-character Country Code, "US" (United States of America), in\norder to conform to the ISO 3166 standard.\n \n \nInstallation Instructions:\n==========================\n \n\n
\n\n\n
\nSee the National Patch Module on Forum for the patch description.\n\n\n
\nThis patch addresses the following:\n \n-Problems caused while editing active HL Logical Links\n-Problems with "AE" cross reference leading to incorrect setting\n values and inability to delete.\n-Incorrect documentation for HL7 API GENACK^HLMA1 and potential\n <UNDEFINED> error.\n-Extrinsic function NEWEVENT^HLEVAPI could potentially execute\n without returning a value resulting in a <COMMAND> error. \n\n
\nTo allow for the creation of new links via the Link Edit [HL EDIT LOGICAL \nLINKS] option, the validation logic will allow users to proceed to the \nedit screen if the link is new. Also, it will allow users to proceed if\nthe Logical Link is a Multithreaded Listener regardless of the SHUTDOWN \nLLP? (#14) field value in the HL LOGICAL LINK (#870) file.\n\n
\nIn preparation for the VA's transition from IPv4 to IPv6 the HL7 package \nwill require modifications to make it IPv6 ready.\n\n
\nThis patch modifies the Fileman validation logic to account\nfor the upgrade to Fileman V22.2.\n\n
\nThis patch addresses issues when editing HL LOGICAL LINKS, <STORE> errors\ncaused by excessive out queue arrays and potential issues with router\nprotocols where additional, unwanted data is processed.\n\n
\nResolve issues with the HL7 receiving process that could lead to the \nprocess getting stuck in an endless loop.\n\n
\nResolves issue with the HL7 process that a bad value for\nHLL("LINKS") would affect subsequent process with HL7\n\n\nThis patch updates the MPI (Master Patient Index) listener to work on\nLinux and Unix systems.\n\n
\nThis patch will do the following to correct the problems found in DD and\n (#771.7).\n \nTest Sites :\n==============\n \n \nInstallation Instructions:\n==========================\n 1. Patch HL*1.6*26 must be installed before this patch.\n 2. Users are allowed to be on the system during the installation.\ndata in files #772 and #771.7:\n 3. Shut down all the outgoing filers.\n 4. Shut down all the incoming filers.\n 5. No routine mapping for this patch.\n 6. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \n This option will load the KIDS package onto your system. \n 7. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n 1. Rewrite the KILL logic for the 'AXMITOUT1' cross-reference of\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*24\n ==========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 8. MSM Sites - Answer 'NO' to the question 'Want to MOVE routines\n 'Logical Link' field (#772,11) in the HL7 Message Text file (#772).\n to other CPUs?'.\n 9. Restart all the outgoing and incoming filers which have been shut\n down at step 2 and 3.\n 10. You may delete the post-install routine 'HLPAT24' after you have\n successfully installed this patch.\n 2. Rewrite the KILL logic for the 'AXMITOUT2' cross-reference of\n 'Status' field (#772,20) in the HL7 Message Text file (#772).\n 3. Modify DD of 'Error Type' field (#772,23) in the HL7 Message Text\n file (#772).\n 4. Modify data of the entry, CODE=1, in the HL7 Error Message file\n\n
\n This patch will address 1 issue:\n \n 1. When several HL7 event driver protocols share the same sending\n application, message type, event type, and version ID, the HL7 \n software will only retrieve the first protocol, even if it is not the\n correct protocol for the current message being processed.\n\n
\nThis patch updates the Health Level Seven (HL7) routines with a version \ncheck that does not include "IRIS".\n\n
\nHealth Level Seven (HL7) patch HL*1.6*173 modifies the software to\nensure the most recently run HL7 monitor is used when checking against\nthe REQUEUE MIN-MONITOR (#4) field in the HL7 MONITOR (#776.1) file.\n\n
\nPatch HL*1.6*174 addresses 2 issues\n1. An undefined DUZ(2) error in the XPAR1 routine due to the DUZ() array \n not being set up properly.\n2. An undefined HLNK error in the HLTPCK1A routine due to the domain\n of the sending site not being found in the DOMAIN(4.2) file "B" cross\n reference.\n\n
\nMAKE ALL HL FILERS PERSISTENT\n\n
\nPatch HL*1.6*176 addresses an <UNDEFINED> ZTSKMST error when using the\nMonitoring master job start menu [HLEV MASTER JOB START] option.\n\n
\nThis patch provides two new features, "Don't Purge" and "Reprocessing"\n \n 1. Users are allowed to be on the system during the installation.\n 2. Check and make sure that the 'HL PURGE TRANSMISSIONS' option is not\n scheduled during the time of installation.\n 3. Stop all the incoming filers. \n 4. AXP SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 6. The patch has now been loaded into a Transport global on your\n 2. Clear the flag field "DON'T PURGE" (#772,15) to allow the message\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*33\n to be purged by the "HL PURGE TRANSMISSIONS" option. Either of the\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 7. MSM Sites - Answer 'YES' to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 8. AXP Sites: Rebuild your mapped set if necessary.\n 9. Restart all the incoming filers, which have been stopped in step #3.\n 10. Re-schedule 'HL PURGE TRANSMISSIONS' option if this option was\n scheduled and has been stopped in step #2. \n following two extrinsic functions may be used for this purpose:\n $$TOPURG^HLCIRN or $$SETPURG^HLCIRN(0)\n \n 3. Reprocessing the message by calling the extrinsic function:\n $$REPROC^HLCIRN(IEN,RTN)\n where: IEN is the child message IEN (or the parent message IEN).\n RTN is the routine to be Xecuted for reprocessing the\nmessages, which were requested by the CIRN project. The new extrinsic\n message.\n \n \nThese extrinsic functions and their associated parameters, return values,\nand results are described as follows:\n \n $$DONTPURG^HLCIRN():\n purpose: to set the "DON'T PURGE" field (#772,15).\n input: none\n return value: 1 means field has been successfully set\nfunction calls allow the VISTA/DHCP applications to interface with HL7\n -1 means call has failed; nothing has been changed\n \n $$TOPURG^HLCIRN():\n purpose: to clear the "DON'T PURGE" field (#772,15).\n input: none\n return value: 0 means field has been successfully cleared\n -1 means call has failed; nothing has been changed\n \n $$SETPURG^HLCIRN(STATUS):\n purpose: either to set (STATUS=1) or to clear (STATUS=0) the\nin the following ways:\n "DON'T PURGE" field (#772,15).\n input: STATUS=1 used to set the "DON'T PURGE" field.\n STATUS=0 used to clear the "DON'T PURGE" field.\n return value: 1 means field has been successfully set\n 0 means field has been successfully cleared\n -1 means call has failed; nothing has been changed\n \n $$REPROC^HLCIRN(IEN,RTN):\n purpose: to reprocess message.\n input: IEN= the child message IEN (or the parent message\n \n IEN) of file #772.\n RTN= routine, to be Xecuted for reprocessing the\n message.\n return value: 0 means call has been successfully completed\n -1 means call has failed; nothing has been changed\n \nThe extrinsic functions, $$DONTPURG^HLCIRN(), $$TOPURG^HLCIRN(), and\n$$SETPURG^HLCIRN(STATUS) should be called by one of the following\nroutines:\n - RTN routine, which is provided to $$REPROC^HLCIRN(IEN,RTN).\n 1. Set the new flag field "DON'T PURGE" (#772,15) to prevent a message\n - routine stored in field "GENERATE/PROCESS ROUTINE"(#101,771).\n - routine stored in field "GENERATE/PROCESS ACK ROUTINE"(#101,772). \n \nWhen called by these routines, HL7 assumes that the variables,\nHLMTIENS(child message IEN of file #772) and HLMTIEN(parent message IEN of\nfile #772), are already properly defined. Otherwise, if they are called\nelsewhere, at least the HLMTIEN should be defined in order to make them to\nwork. If only HLMTIEN is defined, then the call will only update the\nentry of parent message. Of course, having only a defined HLMTIENS is\nenough for HL7 to find the corresponding value for HLMTIEN, and\n being purged by the "HL PURGE TRANSMISSIONS" option. Either of the\nconsequently HL7 will update entries for both child and parent massages.\n \nThe IEN, which is provided to $$REPROC^HLCIRN(IEN,RTN) should be the child\nmessage IEN of file #772. This will make HL7 update the "STATUS" for both\nchild and parent message entries. If the IEN is the parent message IEN,\nthen only the "STATUS" of the parent message entry will be updated.\n \n \nRoutine Summary:\n================\n following two extrinsic functions may be used for this purpose:\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n $$DONTPURG^HLCIRN or $$SETPURG^HLCIRN(1)\n ------------ --------------- -------------- ------------\n HLCIRN N/A 4336697 33\n HLTPCK1 4288888 4143076 8,33\n HLUOPT1 9958836 9990663 10,13,21,33\n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n==========================\n\n
\nThis patch contains changes to the Mailman LLP to further improve\nperformance and IO issues and ensure the process dies off after a shutdown\nrequest.\n\n
\nThis patch provides two new features, "Don't Purge" and "Reprocessing"\n \n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*36\n 2. Clear the flag field "DON'T PURGE" (#772,15) to allow the message\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 7. DSM Sites: Rebuild your mapped set if necessary.\n 8. Restart all the incoming filers, which have been stopped in step #3.\n 9. Re-schedule 'HL PURGE TRANSMISSIONS' option if this option was\n scheduled and has been stopped in step #2. \n to be purged by the "HL PURGE TRANSMISSIONS" option. The following\n extrinsic function may be used for this purpose:\n $$TOPURG^HLUTIL()\n \n 3. Reprocessing the message by calling the extrinsic function:\n $$REPROC^HLUTIL(IEN,RTN)\n where: IEN is the child message IEN (or the parent message IEN).\n RTN is the routine to be Xecuted for reprocessing the\nmessages, which were originally requested by the CIRN project. The new\n message.\n \n \n These extrinsic functions and their associated parameters, return values,\n and results are described as follows:\n \n $$DONTPURG^HLUTIL():\n purpose: to set the "DON'T PURGE" field (#772,15).\n input: none\n return value: 1 means field has been successfully set\nextrinsic function calls allow the VISTA/DHCP applications to interface\n -1 means call has failed; nothing has been changed\n \n $$TOPURG^HLUTIL():\n purpose: to clear the "DON'T PURGE" field (#772,15).\n input: none\n return value: 0 means field has been successfully cleared\n -1 means call has failed; nothing has been changed\n \n $$REPROC^HLUTIL(IEN,RTN):\n purpose: to reprocess message.\nwith HL7 in the following ways:\n input: IEN= the child message IEN (or the parent message\n IEN) of file #772.\n RTN= routine, to be Xecuted for reprocessing the\n message.\n return value: 0 means call has been successfully completed\n -1 means call has failed; nothing has been changed\n \nThe extrinsic functions, $$DONTPURG^HLUTIL(), $$TOPURG^HLUTIL(), should be\ncalled by one of the following routines:\n - RTN routine, which is provided to $$REPROC^HLUTIL(IEN,RTN).\n \n - routine stored in field "GENERATE/PROCESS ROUTINE"(#101,771).\n - routine stored in field "GENERATE/PROCESS ACK ROUTINE"(#101,772). \n \nWhen called by these routines, HL7 assumes that the variables,\nHLMTIENS(child message IEN of file #772) and HLMTIEN(parent message IEN of\nfile #772), are already properly defined. Otherwise, if they are called\nelsewhere, at least the HLMTIEN should be defined in order to make them to\nwork. If only HLMTIEN is defined, then the call will only update the\nentry of parent message. Of course, having only a defined HLMTIENS is\nenough for HL7 to find the corresponding value for HLMTIEN, and\n 1. Set the new flag field "DON'T PURGE" (#772,15) to prevent a message\nconsequently HL7 will update entries for both child and parent massages.\n \nThe IEN, which is provided to $$REPROC^HLUTIL(IEN,RTN) should be the child\nmessage IEN of file #772. This will make HL7 update the "STATUS" for both\nchild and parent message entries. If the IEN is the parent message IEN,\nthen only the "STATUS" of the parent message entry will be updated.\n \n \nRoutine Summary:\n================\n being purged by the "HL PURGE TRANSMISSIONS" option. The following\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n extrinsic function may be used for this purpose:\n ------------ --------------- -------------- -----------\n HLUTIL N/A 4603738 36\n HLTPCK1 4288888 4288888 8,36\n HLUOPT1 9958836 9990663 10,13,21,36\n \n From CHECK^XTSUMBLD\n \n \nInstallation Instructions:\n==========================\n $$DONTPURG^HLUTIL()\n 1. Users are allowed to be on the system during the installation.\n 2. Check and make sure that the 'HL PURGE TRANSMISSIONS' option is not\n scheduled during the time of installation.\n 3. Stop all the incoming filers.\n 4. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 6. The patch has now been loaded into a Transport global on your\n\n
\nThis patch solves the following problems:\n$$OLDM10^HLFNC(X,HLECDE) and $$OLDM11^HLFNC(X,HLECDE).\n \nRoutine Summary:\n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \n NOIS ISF-1097-61155: The M10 and M11 check digit algorithms do not\nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ------------\n HLFNC 5564618 6477455 38\n \n From CHECK^XTSUMBLD \n \n \n comply with the HL7 Standard.\nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 4. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*38\n =========\nThe two extrinsic functions, $$M10^HLFNC(X,HLECDE) and\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 5. DSM Sites: Rebuild your mapped set if necessary.\n$$M11^HLFNC(X,HLECDE) are calls for the new and HL7 Standardized\nalgorithms for M10 and M11, respectively.\n \nHowever, old and non-Standard algorithms calls has been moved to calls,\n\n
\nThis patch solves the following problems:\n 6. Corrects a problem with messages that are dynamically addressed over\n mailman-type logical link (see patch 14 documentation). The system\n link monitor was not updated correctly.\n \nPLEASE SEE THE PATCH MODULE FOR DETAILS. \n 1. IND-0797-40843: A corrupted message with message ID missing crashed\n the HL7 incoming filer.\n 2. SLC-0897-50592: eliminates priority setting in HLLP processes.\n 3. STX-0897-70964: An unexpected message block sequence, issued by the\n VIC machine, blew out the HL7 LLP process.\n 4. IND-0198-40985: system monitor/process priority.\n 5. Fixes the problem with undefined application name in fields (MSH;3)\n and/or (MSH;5).\n\n
\nPATCH FOR PATCH 34. Missing routine HLUTIL3.\n\n
\nThis patch solves the following problems:\n 2. Return the input X only, if encoding character is not defined.\n \nNothing has been changed for the numeric data type input with encoding\ncharacter, its result will contain the X with its corresponding check\ndigit and algorithms.\n \nFor example,\n \n >W $$M10^HLFNC("12345","|")\n 12345|5|M10\n NOIS PHI-0798-20072 and PHI-0698-22536: Patient ID with alphanumeric\n \n >W $$M10^HLFNC("9999","^")\n 9999^4^M10\n \n >W $$M11^HLFNC("128952","^")\n 128952^7^M11\n \n >W $$M11^HLFNC("1234567","|")\n 1234567|4|M11\n \n data type.\n >W $$M11^HLFNC("1234-F","|")\n 1234-F||\n \n >W $$M10^HLFNC("401-56-1234","^")\n 401-56-1234^^\n \n \nRoutine Summary:\n================\nThe following is a list of the routines included in this patch. The\n \nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ------------\n HLFNC 6477455 6494537 38,42\nThe two extrinsic functions, $$M10^HLFNC(X,HLECDE) and\n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n$$M11^HLFNC(X,HLECDE) have been improved for the input ID with\n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 4. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \nalphanumeric data type. The additional output will be as follows:\n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*42\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 5. DSM Sites: Rebuild your mapped set if necessary.\n \n 1. Return X concatenated with encoding characters, if X is alphanumeric.\n\n\nThis patch to patch number 2 corrects errors in the first and second lines\nof the routines HLCS and HLCSDR2. Remaining code is unchanged.\n \nThe checksum values are as follows:\nHLCS value = 5044367\nHLCSDR2 value = 5218053\n\n
\n \n6. HL7 reference file updates to support draft 2 of HEALTH LEVEL SEVEN, \n Version 2.3\n \nPlease see the patch module on Forum for details.\nHL*1.6*14 introduces the following new features as part of the CIRN\nproject and addresses a number of NOIS related issues:\n \n1. Dynamic addressing of messages\n2. Subscription registry (new file and APIs)\n3. Auto-restart of logical links\n4. Mapping of logical links to institutions (and related api's)\n5. A new option to shut down all logical links\n\n
\nThis patch solves the following problems:\n second line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \n Checksums:\n ==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ------------\n NOIS ISB-1097-32281: Batch message transmission problems for both initial\n HLCSHDR 5439890 6047496 37\n HLTP0 3059585 3159167 25,37\n \n From CHECK^XTSUMBLD \n \n \n Installation Instructions:\n ==========================\n 1. Users are allowed to be on the system during the installation.\n 2. Stop all the outgoing and incoming filers by using the HL7 "Stop\n and acknowledgement messages with missing acknowledgement code, reference\n all incoming filers" and "Stop all outgoing filers" options.\n 3. DSM SITES: Review your mapped set. If any of the routines listed\n in the Routine Summary section are mapped, they should be removed\n from the mapped set at this time.\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n batch control ID, etc. This was causing UNDEFINED variable errors in\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*37\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n HLTP01+47^HLTP01.\n 6. DSM Sites: Rebuild your mapped set if necessary.\n 7. Restart the outgoing and incoming filers, by using the HL7 "Start\n default number of incoming & outgoing filer" option, which have\n been stopped in step #2.\n \n Routine Summary:\n ================\n The following is a list of the routines included in this patch. The\n\n
\nDEVELOPERS: SEE BELOW FOR DESCRIPTION OF A NEW API\n site parameters.\n4. New field in 869.3 to support a local mail group for Messaging system\n alerts and notifications.\n5. New public FUNCTION CALL to retrieve an application-specific mail group\n for alerts and notifications pertaining to initiating or processing a\n particular transaction. The second piece returned is the\n active/inactive flag.\n \nGETAPP^HLCS2(HLAPP)\n ;Function to Retrieve parameters pertaining to a specific\nSummary:\nsending or receiving application\n ;HLAPP=APPLICATION NAME OR IEN OF FILE 771\n ;Returns MAIL GROUP NAME^'a' or 'i' (active or inactive) \n \nEXAMPLE:KRN,KDE>S ZZPARMS=$$GETAPP^HLCS2("JC TEST SERVER") W ZZPARMS\n \nRESULT: ZZPARMS=JOHN^a\n \n1. Enhancements to Systems Link Monitor:\n -more information in header to help distinguish multiple displays.\n -provides both a full and abbreviated display format, as well as a\n help screen\n2. Additional required Messaging site parameters added to file 869.3.\n3. Updated option "Edit Communication Server Parameters" to support new\n\n\n=============================================================================\nand in HL7 MESSAGE TEXT, file 772. To speed up the conversion, run the\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n INSTALL NAME: HL*1.6*19\n =========\n\n The length of the install depends on the size of file 772. The average\n install takes about 15 minutes for 40,000 entries in file 772. \n\n 9. Allow users back on the system and remove Taskman from wait state,\n'Purge Message Text File Entries' option to remove old messages.\n use the option 'Remove Taskman from WAIT State'.\n\n 10. Use the 'Edit Communication Server parameters' option to add a Mail\n Group to the 'Mail Group for Alerts' field.\n\n 11. Startup all Logical Links and incoming and outgoing filers. Use the\n 'Restart All Links and Filers' option.\n\n\n============================================================================= \n \nData Dictionary Modifications:\n============================== \n\n 869.1 HL LOWER LEVEL PROTOCOL TYPE\n No modifications were made to the data dictionary. One record,\n TCP, has been added and will be merged into your current data.\n \n 869.2 HL LOWER LEVEL PROTOCOL PARAMETER\n \n 400.01 TCP/IP ADDRESS (F) [400;1]\nEarlier version of Patch 19, prior to test version 25, are Uni-directional.\n 400.02 TCP/IP PORT (NJ5,0) [400;2]\n 400.03 TCP/IP SERVICE TYPE (S) [400;3]\n 400.04 PERSISTENT (S) [400;4]\n 400.06 STARTUP NODE (P14.7) [400;6]\n\n 771.6 HL7 MESSAGE STATUS\n No modifications were made to the data dictionary. Several new\n statuses have been added and will overwrite your current data.\n\n 771.7 HL7 ERROR MESSAGE\nAll TCP Logical Links must be redefined to work with this version of patch\n No modifications were made to the data dictionary. Several new\n errors messages have been added and will overwrite your current data.\n\n 772 HL7 MESSAGE TEXT\n The .01 field, DATE/TIME ENTERED, has been changed from a pointer to\n a date/time field.\n\n 773 HL7 MESSAGE ADMINISTRATION\n The .01 field, DATE/TIME ENTERED, has been changed from a date/time to\n a pointer to file 772. Fields have been added to this file for bi-\n19. Messages might also need to be modified.\n directional TCP messages.\n\n\nNew Option\n============================== \n\n'View Transmission Log' Option name: HL VIEW TRANSMISSION LOG\n This option is used to view the Transmission Log; i.e.,\n the Message Administration File entries. It displays those\n messages that have been sent or are pending. Display of\n\n messages with HL7 errors or exceptions is not yet supported.\n\nNew Alert\n==============================\nIf a message exceeds the 'RE-TRANSMISION ATTEMPTS' for a Logical Link, an\nalert will be generated. The alert will be sent to the Mail Group defined\nin the HL COMMUNICATION SERVER PARAMETERS file, 869.3.\n\n\nRoutine Modifications:\nDescription:\n======================\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**19**;JUL 17, 1995\n\nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n============\n HLCS 5666872 5781112 **2,9,14,19**\n HLCS1 10146376 10172566 **19**\n HLCSHDR 6047496 5939243 **37,19**\n HLCSHDR1 NEW 6658466 **19**\n HLCSIN 2120979 2517664 **2,30,14,19**\n HLCSLNCH 7065769 11290939 **6,19**\n HLCSRPT NEW 14324083 **19**\n HLCSRPT1 NEW 9680356 **19**\n HLCSTCP NEW 3731985 **19**\n HLCSTCP1 NEW 4613833 **19**\nThis patch introduces TCP/IP as a transport layer for the HL7 package. \n HLCSTCP2 NEW 7316489 **19**\n HLCSUTL 4322424 5134775 **2,19**\n HLDTIW2B 5008365 5012027 **14,19**\n HLDTIWP0 7906384 7922736 **19**\n HLDTIWU3 2154979 2083370 **19**\n HLMA 3791837 3745291 **19**\n HLMA1 4194174 4230657 **19**\n HLMA2 1082489 3410765 **19**\n HLPAT19 NEW 845483 **19**\n HLTF 7445472 7170159 **1,19**\nFor information on how to work with TCP/IP HL7 interfaces, see the new \n HLTF0 4765190 3173064 **12,19**\n HLTF1 9700889 9479987 **5,8,22,25,19**\n HLTP3 NEW 12380779 **19**\n HLTP4 NEW 7754632 **19**\n HLTPCK2 NEW 3804314 **19**\n HLTPCK2A NEW 11350701 **19**\n HLUOPT1 9990663 11568432 **10,13,21,36,19**\n HLUTIL 4603738 1343106 **36,19**\n HLUTIL2 3877956 5547421 **19**\n\n"DHCP HL7 User Manual: TCP/IP Supplement", which is in the file\n\n\nInstallation Instructions:\n========================== \n 1. Use the option 'Purge Message Text File Entries' option to remove\n old messages. Suggested answers:\n\n Enter the cutoff date for all messages REGARDLESS OF STATUS: T-90// T-28\n Enter last INCLUSIVE date for status SUCCESSFULLY TRANSMITTED: T-7// T-2\n Purge entries with an ERROR STATUS? NO// YES\nHL71_6P19.PDF, available from the Customer Service anonymous directories.\n Cutoff date for AWAITING ACKNOWLEDGEMENT status: T-30// T-7\n\n 2. Make sure all messages have been transmitted. Run the option 'Systems\n Link Monitor', under the 'Communications Server' menu, and make sure\n 'messages to send' is equal to 'messages sent' for all Logical Links.\n\n 3. Shutdown all Logical Links and incoming and outgoing filers. Use the\n 'Shut Down All Logical Links', 'Stop all incoming filers', and 'Stop\n all outgoing filers' options.\n\n\n 4. User are NOT allowed on the system during installation. Inhibit logins\n and place Taskman in a wait state, use the option 'Place Taskman in a\n WAIT State'. Have the submanager shutdown after finishing their current\n task.\n\n 5. Some of these routines are new. Currently we do not recommend that you\n add these routines to your map set.\n \n 6. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. This\n option loads the KIDS package into a Transport global onto your\nThis patch will convert the messages in HL7 MESSAGE ADMINISTRATION, file 773,\n system.\n\n 7. You now need to use KIDS to install the Transport global. From programmer\n prompt Do ^XPDKRN.\n \n 8. On the KIDS menu, under the Installation menu, use the following\n options:\n \n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n\n
\nThis patch addresses the following issues:\n HL LOWER LEVEL PROTOCOL PARAMETER file.\n4. The API GENERATE^HLMA would return the parameter HLRESLT, when passed\n by reference, equal to the message id. But, multiple messages could\n have been generated. This patch will now also return the array \n HLRESLT, where HLRESLT(1)=2nd message id.\n \nRoutine Modifications:\n======================\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n HLCS 5781112 5743323 2,9,14,19,43\n HLCS2 4802116 7195833 14,40,43\n HLCSAC NEW 2497076 43\n1. Support is provided for connecting to the Master Patient Index (MPI).\n HLCSAS NEW 2943880 43\n HLCSAS1 NEW 1742491 43\n HLCSLNCH 11290939 11368535 6,19,43\n HLCSTCP 3731985 4005742 19,43\n HLCSTCP1 4613833 4899040 19,43\n HLCSTCP2 7316489 7436704 19,43\n HLMA 3745291 5502295 19,43\n HLMA1 4230657 3849338 19,43\n HLMA2 3410765 7300625 19,43\n HLTF 7170159 7284127 1,19,43\n2. FileMan auditing ordinarily depends on DUZ, but when VA FileMan records\n HLTP 5532648 4283999 14,43\n HLTP3 12380779 12440103 19,43\n HLUTIL2 5547421 5380198 19,43\n \n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n are updated by subscriber protocols, DUZ is undefined, disabling\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n \n 3. Shutdown all Logical Links and incoming and outgoing filers. Use the\n 'Shut Down All Logical Links', 'Stop all incoming filers', and 'Stop\n all outgoing filers' options.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n \n audting. Changes in this patch combined with changes that will be \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n 2 Verify Checksums in Transport Global\n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global\n 6 Install Package(s) \n released VA FileMan V22.0 allow auditing based on subscriber protocol,\n INSTALL NAME: HL*1.6*43\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the\n 'Restart All Links and Filers' option.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n rather than DUZ.\n3. Autostart of a Logical Link now uses the AUTOSTART NODE field in the\n\n
\n \n would return the following value: DOE,JOHNSR\n \n This occurred because this function specifically checked from the second\n component to the last whether the next component contained two\n double quotes (e.g.: "") or had no value. When this condition was\n encountered, this function did not place a space between each\n component and the component immediately following starting from the\n second.\n \n After this patch is installed, the return value will now be DOE,JOHN SR\nThe CIRN developers was the first to discover and report a problem with\n for the above example.\n \n The following code may be used in programmer mode to test this function:\n NOTE: The '>' character is the mumps programmer prompt.\n \n >R X\n DOE~JOHN~""~SR <---Enter this data on the READ command.\n >W $$FMNAME^HLFNC(X,"~")\n DOE,JOHN SR <---This should be the the result after this patch\n is installed.\nthe function $$FMNAME^HLFNC(X,HLECDE). Additional details of their\n You may also try the following:\n >W $$FMNAME^HLFNC("DOE~JOHN~~SR","~")\n DOE,JOHN SR\n \nBefore this patch is installed, you should have installed patch HL*1.6*42.\n \nRoutine Summary: \n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\nfindings are recorded in NOIS: BAY-0499-31160.\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995 \n \nChecksums: \n==========\n \n Routine Name Checksum Before Checksum After Patch List \n ------------ --------------- -------------- ------------\n HLFNC 6494537 5785780 38,42,51\n \n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n If the variable X is used as the first parameter of this function\n option will load the KIDS package onto your system. \n 4. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n and has a value of DOE~JOHN~""~SR\n Install Package(s) \n INSTALL NAME: HL*1.6*51 \n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n 5. DSM Sites: Rebuild your mapped set if necessary. \n \n this function when invoked (e.g.: S Y=$$FMNAME^HLFNC(X,"~") )\n\n\nThis patch solves the following problems:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ------------\n HLCSMON 9246839 9506155 34,40,48\n NOIS BHH-0299-40326: The Logical Links, displayed on the System Monitor\n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n last screen, were duplicates from some of the\n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 4. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Logical Links of its previous screen.\n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*48\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 5. DSM Sites: Rebuild your mapped set if necessary.\n \nRoutine Summary:\n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n\n
\nThis patch solves the following problem:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \n Checksums:\n ==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ------------\n HLCSDL 4175013 4198429 2,44\n To prevent an "undefined variable HLDP" error for the X3.28 lower level\n \n From CHECK^XTSUMBLD \n \n \n Installation Instructions:\n ==========================\n 1. Users are allowed to be on the system during the installation.\n 2. Use the HL7 "Stop LLP" to stop the LLPs, which are executed in\n X3.28 protocol.\n 3. DSM SITES: Review your mapped set. If any of the routines listed\n protocol. This error occurs when starting the LLP, it fails to establish\n in the Routine Summary section are mapped, they should be removed\n from the mapped set at this time.\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n a connection and autostart is enabled.\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*44\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 6. DSM Sites: Rebuild your mapped set if necessary.\n 7. Restart the LLPs by using the HL7 "Start LLP" option, which have\n \n been stopped in step #2.\n Routine Summary:\n ================\n The following is a list of the routines included in this patch. The\n second line of each of these routines now looks like:\n\n
\nThis patch corrects the problem identified in NOIS IVM-0499-31407,\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n HLTF 7284127 7261750 1,19,43,55\n \n \nInstallation Instructions:\nmessage IDs no longer created for version 1.5 messages.\n==========================\n 1. Users are allowed to be on the system during the installation.\n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n \n 3. Shutdown all Logical Links and incoming and outgoing filers. Use the\n 'Shut Down All Logical Links', 'Stop all incoming filers', and 'Stop\n all outgoing filers' options.\n\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n 2 Verify Checksums in Transport Global\n\n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global\n 6 Install Package(s) \n INSTALL NAME: HL*1.6*55\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the\nRoutine Modifications:\n 'Restart All Links and Filers' option.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n\n======================\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n\n
\nInformational\n\n
\nDescription:\nthe message text after selecting an individual record from the list. \n 773 HL7 MESSAGE ADMINISTRATION\n The STATUS field, #20, has been changed to add the "AG"\ncross-reference.\nThe other NOIS reported the routine HLCSRPT errorred out with an \nundefined variable message in some circumstances. \n \nSecond, additional functionality is provided as follows:\nRefined message searchs. The messages search is now expanded to allow\nthe user to select a message search based any combination (or all) of\nthe search fields. They include status code, message type, event type\nand logical link. The default entry for each field is "ALL". As before,\nall message searching will be limited to a user entered start date/time.\n============\nThe single criteria message searching is replaced with this enhanced \nsearching capability. \nPending messages. The option for pending messages has not changed.\nError listing. An option providing for the display of messages that\nare in an error status is added. The default is all errorred messages,\nbut the user may select a specific error code.\n \nThis patch also contains the DD for file 773, Message Administration\nFile. It adds a new cross-reference, "AG", which pertains to the\nStatus field. A Post-Install routine is run to set the cross-reference.\nThis patch requires running the purge message option and shutting down\n \nRoutine Summary:\n================\nThe following routines are included in this patch. The second line of\neach\nof these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \n Checksum\nRoutine Old New 2nd Line\nall links and filers before installing the patch.\nHLCSRPT 14324083 10630512 **19,50**\nHLCSRPT1 9680356 13849369 **19,50**\nHLCSRPT2 NEW 18087507 **50**\nHLCSRPT3 NEW 10792707 **50**\nHLP50PST NEW 36805 **50**\n \nList of preceding patches: 19\nSites should use CHECK^XTSUMBLD to verify checksums.\n \nInstallation Instructions:\n \n========================== \n 1. Use the option 'Purge Message Text File Entries' option to remove\n old messages.\n \n 2. Make sure all messages have been transmitted. Run the option\n'Systems\n Link Monitor', under the 'Communications Server' menu, and make sure\n 'messages to send' is equal to 'messages sent' for all Logical\nLinks.\n \nThis patch provides both additional functionality and NOIS fixes.\n 3. Shutdown all Logical Links and incoming and outgoing filers. Use the\n 'Shut Down All Logical Links', 'Stop all incoming filers', and 'Stop\n all outgoing filers' options.\n \n 4. User are allowed on the system during installation. Do NOT inhibit\nlogins\n and do NOT place Taskman in a wait state.\n \n 5. Some of these routines are new. Currently we do not recommend that\nyou\n \n add these routines to your map set.\n \n 6. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. This\n option loads the KIDS package into a Transport global onto your\n system.\n \n 7. You now need to use KIDS to install the Transport global. From\nprogrammer\n prompt Do ^XPDKRN.\n \nFirst, it provides fixes for the following NOISes: BAC-0599-40603 and \n 8. On the KIDS menu, under the Installation menu, use the following\n options:\n \n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n INSTALL NAME: HL*1.6*50\n =========\nIND-0599-40402. One NOIS reported, in some cases, a failure to display \n \n 9. Startup all Logical Links and incoming and outgoing filers. Use the\n 'Restart All Links and Filers' option.\n \n \n==========================================================================\n=== \nData Dictionary Modifications:\n============================== \n \n\n
\nThis patch has made changes for the following:\n TaskMan, and as the default when run interactively.\n 4. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*47\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 7. DSM Sites: Rebuild your mapped set if necessary.\n - Field #869.3,42 PURGE AWAITING ACK MESSAGES: The number of days\n 8. Restart all the Logical links, incoming and outgoing filers, which\n have been stopped in step #3.\n 9. Re-schedule 'HL PURGE TRANSMISSIONS' option if this option was\n scheduled and has been stopped in step #2.\n 10. Use the "Edit Communication Server parameters" option to enter\n and/or change the data described in DESCRIPTION section for fields-\n (#869.3,41), (#869.3,42), and (#869.3,43).\n "Awaiting Application Acknowledgement" messages are retained before\n they are purged. If no value is entered, the default is 30 days.\n Used as the actual value when the "Purge Messages" option is\n scheduled through TaskMan, and as the default when run\n interactively.\n \n - Field #869.3,43 PURGE ALL MESSAGES: The number of days that any\n \n status message are retained before they are purged(except for ERROR\n status messages). If no value is entered, the default is 90 days.\n Used as the actual value when the "Purge Messages" option is\n scheduled through TaskMan, and as the default when run\n interactively.\n \n Please find the following HL7 options to enter or change data for\n fields described above:\n \n step 1. HL MAIN MENU\n 1. Adds three new fields in HL COMMUNICATION SERVER PARAMETERS file\n step 2. Communications Server ...\n step 3. Edit Communication Server parameters\n \n And then you will enter the FileMan ScreenMan form as follows:\n \n --------------------------------------------------------------------\n \n Edit HL7 Site Parameters\n \n \n (#869.3): \n Current Domain: NXT.KERNEL.ISC-SF.DOMAIN.EXT \n Current Institution: ISC SAN FRANCISCO \n Is this a Production or Test Account? test \n \n Default Number of Incoming Filers: 1 \n Default Number of Outgoing Filers: 1 \n \n Mail Group for Alerts: HL7 \n \n Days to Keep Completed Messages: 7 \n \n Days to Keep Awaiting ACK Messages: 30 \n Days Before Purging All Messages: 90 \n \n ________________________________________________________________\n \n \n COMMAND: Press <PF1>H for help\n Insert\n \n -----------------------------------------------------------------\n - Field #869.3,41 PURGE COMPLETED MESSAGES: The number of days\n \n The old method which was used to change the data for the above three\n fields, by entering numbers in the TASK PARAMETERS field of the OPTION\n SCHEDULING FILE, will be replaced by this new method as described\n above, when the "Purge Message Text File Entries [HL PURGE\n TRANSMISSIONS]" OPTION is scheduled to TaskMan.\n \n 2. Brings in updated data for files: HL7 MESSAGE STATUS and HL7 ERROR\n MESSAGE, these two files can only be used by HL7 routines.\n \n "Successfully Completed" messages are retained before they are\n 3. Solves problems for NOIS ISF-0499-63255: Entries existed in file #773\n with broken pointers to file #772.\n \nRoutine Summary:\n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n purged. If no value is entered, the default is 7 days. Used as the\n \nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- -----------------\n HL47PRE new 613093 47\n HLUOPT1 11568432 13112533 10,13,21,36,19,47\n HLTP01 5246181 5245980 2,25,34,47\n HLTP1 4286152 4286011 34,47\n actual value when the "Purge Messages" option is scheduled through\n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n 2. Check and make sure that the 'HL PURGE TRANSMISSIONS' option is not\n scheduled during the time of installation.\n 3. Stop all the Logical links, incoming and outgoing filers.\n\n
\nDescription: \n \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in \n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n \n 3. Shutdown all Logical Links and incoming and outgoing filers. Use the \n 'Shut Down All Logical Links', 'Stop all incoming filers', and 'Stop \n all outgoing filers' options.\n \n For DSM sites ONLY, if you have an HL7 UCX Service associated\n After this patch is installed, non-persistent client LLPs\n with the account(uci/directory) where you are installing this patch,\n please disable this service.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n will still have to be started as they were before this patch.\n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*49\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n To start an LLP, use the 'Start LLP' option.\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n 'Restart All Links and Filers' option. \n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager as follows:\n To start an LLP automatically after a system reboot,\n \n STEP 1: HL7 Main Menu\n STEP 2: V1.6 OPTIONS\n STEP 3: Communications Server\n STEP 4: TCP/IP Link Manager Start/Stop\n \nLink Manager is NOT currently running!\n \n Would you like to start the Link Manager now? YES// \n Link Manager queued as task number 2712635\n either use the Interface Workbench to edit Logical Links or use FileMan\n \n 9. Create entry in OPTION SCHEDULING file as follows:\n \n In order to set up this option to startup when the system/TaskMan starts,\n please find the following HL7 options to create an entry\n in the OPTION SCHEDULING file:\n \n STEP 1: Taskman Management ... \n STEP 2: Schedule/Unschedule Options \n STEP 3 (Create the following entry): \n to edit the AUTOSTART field(#4.5) of the HL LOGICAL LINK file(#870).\n \nSelect OPTION to schedule or reschedule: HL AUTOSTART LINK MANAGER \n Are you adding 'HL AUTOSTART LINK MANAGER' as \n a new OPTION SCHEDULING (the 12TH)? No// Y \n \n STEP 4 (From STEP 3 you will automatically enter the FileMan ScreenMan form \n as follows and you should edit the 'SPECIAL QUEUEING' field \n to have a value of 'Startup Persistent'): \n \n Edit Option Schedule\n For each Logical Link that wish to start automatically after a re-boot\n Option Name: HL AUTOSTART LINK MANAGER \n Menu Text: Autostart Link Manager TASK ID:\n __________________________________________________________________________\n \n QUEUED TO RUN AT WHAT TIME:\n \nDEVICE FOR QUEUED JOB OUTPUT:\n \n QUEUED TO RUN ON VOLUME SET:\n \n of the system, you must edit the AUTOSTART field to have a value\n RESCHEDULING FREQUENCY:\n \n TASK PARAMETERS:\n \n SPECIAL QUEUEING: Startup Persistent \n \n_______________________________________________________________________________\n \n \n \n of ENABLED. Do NOT simply enable the AUTOSTART field\n \n \nCOMMAND: Press <PF1>H for help Insert \n \n============================================================================= \nData Dictionary Modifications: \n============================== \n 869.2 HL LOWER LEVEL PROTOCOL PARAMETER \n \n 400.05 RETENTION (NJ6,0), [400;5] (new)\n============\n for all Logical Links. Only select those that you wish start\n \n 869.3 HL COMMUNICATION SERVER PARAMETERS\n \n 51 DEFAULT RETENTION (NJ6,0), [5;1] (new)\n \n 52 LINK MANAGER TASK NUMBER (NJ15,0), [5;2] (new)\n \n 53 STOP LINK MANAGER (S), [5;3] (new)\n \n 54 LM LAST KNOWN $H (F), [5;4] (new)\n that are both legitimate and appropriate for your site.\n \n 870 HL LOGICAL LINK\n \n 3 LLP ONLINE (S), [0;4] (old)\n \n changed to:\n \n 3 DEVICE TYPE (S), [0;4] (new)\n \nNew Options:\n \n============================== \n 'TCP/IP Link Manager Start/Stop' Option name: HL START/STOP LINK MANAGER\n 'Autostart Link Manager' Option name: HL AUTOSTART LINK MANAGER\n \nNew for Systems Link Monitor:\n==============================\n \n 1. Status of whether TaskMan is currently running.\n 2. Status of whether Link Manager currently running.\n 3. Additional STATES for non-persistent client links:\n Note, although you may have started a non-persistent LLP,\n o ENABLED\n o INACTIVE\n 4. New DEVICE TYPE column replaces DEVICE ON-LINE column.\n 5. New DEVICE TYPES:\n PC -- Persistent TCP/IP Client\n NC -- Non-Persistent TCP/IP Client\n SS -- Single-threaded TCP/IP Server\n MS -- Multi-threaded TCP/IP Server\n SH -- Serial HLLP\n SX -- Serial X3.28\n the system process representing this LLP does not actually start\n MM -- MailMan\n \n \nConfiguration considerations:\n==============================\n \n The only configuration parameter is Retention. \n This may be edited per Logical Link using the Interface Workbench. \n Also, a Default Retention time may be edited \n using the 'Edit Communication Server parameters' option. \n until messages are in the associated message queue. Once a process\n \n The order of precedence for Retention is as follows: \n \n 1. Retention (Per Logical Link value overrides any defaults).\n 2. Default Retention (System-wide account default.\n If valued, this field is the default\n per Logical Link when the Retention\n field is left unvalued).\n 3. 15 seconds (System-wide account default. This value\n is used when both Retention and Default\n is started, it will remain running on the system until the associated\n Retention are left unvalued).\n \n You may wish to accept the system-wide default of 15 seconds for \n Retention of your non-persistent TCP/IP client Logical Links. \n Once you become more familiar with the frequency and load of each link, \n you may adjust these Retention values accordingly. \n \nTroubleshooting information:\n============================\n The HL7 Systems Link Monitor is a useful tool to help\n queue is emptied and the associated Retention time has expired.\n you troubleshoot problems with either the Link Manager\n or the individual Logical Links. This tool will monitor\n both TaskMan and Link Manager. When either of these\n does not appear to be running, a warning will be\n displayed on the Systems Link Monitor.\n \n \n ALERT NOTIFICATION\n \n It highly recommended that sites establish a mail group\n The Retention time is the time in seconds in which the LLP process\n for HL7 related alerts. Once this has been establish,\n use the 'Edit Communication Server parameters' option\n to identify the Mail Group for Alerts.\n \n If a mail group has been created and identified, the Link Manager\n will use this mail group to send the following alert whenever\n it finds a configuration problem between the links and TaskMan:\n \n HL7 Logical Link LLname shutdown due to TaskMan unable to process task request\n \n will wait while continually checking for messages in the associated\n The most likely cause for receiving such an alert is having TaskMan running\n in non-DCL context and having a Logical Link with an associated\n STARTUP NODE other than where TaskMan is currently running. This applies\n to both the AXP and AVANTI sites.\n \n After receiving this alert, make the needed corrections and restart\n the Logical Link if necessary.\n This patch addresses the issue of reducing the number of required logical\n message queue. If messages are found in the queue before the retention\n time has expired, the LLP process will continue to de-queue messages\n as before. Otherwise, the LLP process will actually return back\n to TaskMan's sub-manager and possibly terminate. When this occurs,\n a status of INACTIVE is indicated on the STATE column\n of the system link monitor for this LLP. \n \n \nThis patch also addresses the following issues: \n \n links running as active concurrent processes. Before this patch,\n 1. Fix allocation error in HLCSDR.\n Related NOIS: SFC-0599-60101\n SBY-0199-30725\n HIN-1298-40436\n Actual error: $ZE= INT+22^%ET:1, %DSM-E-ALLOC, allocation failure\n Description: This error was first seen after the introduction of\n patch HL*1.6*14. This patch 14, utilized error\n trapping to trap disconnect errors so that processing\n may continue once the errors have passed. However,\n if the associated port/device was bad/busy, the code\n all possible HL7 TCP/IP Client Logical Links would have to be defined\n would continually loop to the code that sets the trap.\n As the stack continues to grow, an allocation error\n would result in about 4 to 6+ hours after the logical\n link was started or when the device became bad/busy.\n This allocation error was seen associated with\n the applications using the serial HLLP protocol of\n the HL7 v1.6 (HLCSDR* routines).\n \n 2. Fix allocation error in HLCSMON.\n Description: If a user enters '?' and <RET> repeatedly at the\n and started as LLPs. These LLPs would run and remain as active processes\n command prompt of the Systems Link Monitor, an\n allocation error will be encountered after 6+ attempts.\n \n 3. Fix extraneous display of **STOP** on CACHE sites.\n Related NOIS: MAN-0799-11246\n Description: When the Restart All Links and Filers option is run,\n **STOP** is displayed after failing to connect to\n a listener. This is now corrected by this patch.\n \nRoutine Modifications: \n on the system regardless of the frequency to deliver HL7 messages.\n======================\nThe following routines are included in this patch. The second line of these\nroutines now looks like:\n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;29-Jan-97 14:25\n \nCHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n This was true with both persistent and non-persistent client\n HLCS2 7195833 8763479 14,40,43,49\n HLCSDL 4198429 4174780 2,44,49\n HLCSDR 3946224 3936049 2,14,49\n HLCSLM NEW 6276510 49\n HLCSLNCH 11368535 12855635 6,19,43,49\n HLCSLSM NEW 154819 49\n HLCSMM1 1462301 1445162 35,49\n HLCSMON 9506155 10703763 34,40,48,49\n HLCSMON1 3987859 5535017 15,40,49\n HLCSTCP 4005742 4550642 19,43,49\n connection-type LLPs.\n HLCSTCP2 7436704 7773433 19,43,49\n HLCSTERM 2560922 2618931 40,49\n HLDTIW2A 4178875 4164880 14,49\n HLDTIW2B 5012027 5250753 14,19,49\n HLDTIWP1 8445958 8449802 14,49\n \n \nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n\n
\nDistribute VA TCP Logical Link definitions. \n\n
\nThis patch does the following works to comply with the HL7 standard:\n - #773,16 (event type).\n - #773,15 (message type).\n - Sub-field: #771.06,.01 (message type) of field #771,6.\n 4. Deletes duplicate entries in file #779.001 and #771.2.\n 5. Bring new data of version, event types, and message types into files,\n #771.5 (HL7 Version file), #779.001 and #771.2, to comply with HL7\n 2.3 and 2.3.1 Standard.\n \n \nRoutine Summary:\n \n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \nChecksums:\n==========\n \n 1. Modifies some entries in file #779.001 (HL7 Event Type Code file) and\n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ----------\n HLPAT54 new 7691750 54\n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n #771.2 (HL7 Message Type file).\n 2. Stop all the Logical links, incoming and outgoing filers.\n 3. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 4. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global \n 2. Finds duplicate entries in file #779.001 and #771.2.\n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*54\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 5. Restart all the Logical links, incoming and outgoing filers, which\n have been stopped in step #3.\n 3. Resolves duplicate entries pointers for the following fields:\n - #101,770.4 (event type).\n - #101,770.3 (message type).\n - #101,770.11 (message type).\n\n
\n VISTA HL7 patch HL*1.6*57 addresses most of the outstanding HL7 1.6\nInterfaces are now more intuitive, consistent and simpler regardless of\n re-transmissions, the action below will be performed.\n \n \n 200.21 EXCEED RE-TRANSMIT ACTION 200;10 SET\n 'I' FOR ignore; \n 'R' FOR restart; \n 'S' FOR shutdown;\n \n DESCRIPTION: This field determines what to do when a message exceeds\n the number of retry attempts for this Logical Link.\nthe role of the VISTA system as sender or receiver or the mode of\n Actions are: Ignore = send alert once and keep trying to resend\n Restart = send alert once and shutdown link then start link\n Shutdown = send alert once and shutdown link\n \n(2) There is a new entry in HL7 ERROR MESSAGE file, #771.7.\n \n CODE: 109 SHORT TEXT: Duplicate Message\n DESCRIPTION: Message has already been received and processed. This is\n a duplicate. \n \ncommunication (Mailman, TCP, serial, local app-to-app). The number of\n The following NOIS's are addressed by this patch:\n ISF-0499-61219\n ISF-0499-61021\n BRX-0499-11335\n MIA-0499-31927\n SAG-0599-42045\n ISH-0696-40781\n BAY-1099-32639\n SLC-1099-51078\n BAY-0499-31357\nprotocol definitions that are required to support a simple interface has\n SDC-1099-62397\n ISB-1099-31173\n BAC-0699-40281\n BIG-0999-72027\n \n15. The DATE/TIME field of the HL7 Message Header has been enhanced to\ninclude the timezone offset.\n \n16. New public functions:\n \nbeen reduced in most cases to just two.\n MSGSTAT^HLUTIL(X) ;message status\n input value: X = message id\n return value: status^status updated^error msg.^error type pointer^\n status:\n 0 = message doesn't exist\n 1 = pending transmission\n 1.5 = being transmitted\n 2 = awaiting application acknowledgement\n 3 = successfully completed\n 4 = error\n \n 8 = being generated\n 9 = awaiting processing\n \n MSGACT^HLUTIL(X,HLIENACT) ;outgoing message action\n input value: X = message id\n HLIENACT = 1-cancel; 2-requeue\n return value: 1 = action sucessfull\n 0 = action failed\n \n CHKLL^HLUTIL(X) ;check setup of Logical Link\n3. Redesigned Menu. The HL7 MAIN MENU option has been completely\n input value: X = institution name or number\n return value: 1 = setup OK\n 0 = LL setup incorrect\n \n17. New Option: "Validate Interfaces"\n \nUse this option to check your interface setups for potential problems.\nStarting with an Event Driver Protocol, the event driver, subscriber(s)\nand application definitions will be scanned and a report generated.\n \nreorganized to reflect user preferences both from the field and the JAD\nAfter patch 57 is installed, your pre-57 interfaces will continue to work.\nHowever, you may be interested in upgrading your existing interfaces to\nthe post-57 style to take advantage of the new features. If you run this\noption on a pre-57 setup, you can use the report as a guide for making\nmodifications. If your post-57 setup results in fewer protocols, be sure\nto remove the unneeded protocols. Remember-if the report on a pre-57\ninterface reports errors, it does NOT mean the interface has been broken\nor will stop working because of patch 57. Use the report as a guide only\nfor upgrading or for troubleshooting an existing POST-57 interface.\n \nFocus Group.\nNo conversion of existing interfaces that have been properly defined will\nbe necessary.\n \nAdditional details regarding changes to the Application Parameter File,\nEvent Point Protocols, Subscriber Protocols and key related fields are\ndefined below. \n \n The following routines are included in this patch. The second line of each\n of these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n HLCS 5743323 5745388 2,9,14,19,43,57\n HLCS2 8763479 10072062 14,40,43,49,57\n HLCSAS1 1742491 1743950 43,57\n HLCSDL 4174780 4111820 2,44,49,57\n HLCSDR 3936049 3904673 2,14,49,57\ndeficiencies cited by the HL7 Joint Application Development (JAD) Focus\n4. Event types for version 2.1 messages are no longer required. HL7\n HLCSFMN0 5857525 5857070 15,57\n HLCSFMN2 NEW 1942573 57\n HLCSHDR 5939243 7364841 37,19,57\n HLCSHDR1 6658466 7750238 19,57\n HLCSHDR2 NEW 1077600 57\n HLCSLM 157679 6371649 49,57\n HLCSLNCH 12855635 12643769 6,19,43,49,57\n HLCSLSM 154819 191876 49,57\n HLCSMM 2776063 2836421 17,35,57\n HLCSORAT 5245857 5441831 57\n1.6 is now backward compatible to HL7 Standard, version 2.1 transactions.\n HLCSRPT3 10792707 10830740 50,57\n HLCSTCP 4469052 5152314 19,43,49,57\n HLCSTCP1 4899040 4965932 19,43,57\n HLCSTCP2 7731395 10328595 19,43,49,57\n HLERCHK NEW 12063792 57\n HLFNC2 5393929 5397412 2,26,57\n HLMA2 3410765 7268935 19,43,57\n HLPAT57 NEW 1630585 57\n HLSUB 4535863 5277110 14,57\n HLTP01 5245980 5262489 2,25,34,47,57\nVISTA HL7 version 1.5 interfaces should be upgraded to 1.6 as soon as\n HLTP3 12440103 14050232 19,43,57\n HLTP31 NEW 1680845 57\n HLTP4 7754632 7805100 19,57\n HLTPCK1A 7334335 14402537 2,25,34,57\n HLTPCK2A 11350701 15262342 19,57\n HLUOPT 11331726 11707096 57\n HLUTIL 134301 2643574 36,19,57\n HLUTIL2 5380198 5387464 19,43,57\n \nList of preceding patches: 14, 15, 26, 34, 35, 43, 49, 50\npossible. Version 1.5 fields have been marked for removal from the system.\nSites should use CHECK^XTSUMBLD to verify checksums.\n \nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n \n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \nOnce this occurs, version 1.5 interfaces will no longer function. There\n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the opitons:\n \n Shut Down All Logical Links\n Stop all incoming filers\n Stop all outgoing filers\n TCP/IP Link Manager Start/Stop\n \n For DSM sites ONLY, if you have an HL7 UCX Service associated\nshould be no new development using the 1.5 interface method.\n with the account(uci/directory) where you are installing this patch,\n please disable this service.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*57\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n5. Merger of Split Logical Link and Lower Level Protocol Parameter\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n 'Restart/Start All Links and Filers' option. \n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager using the option: "TCP/IP\nFiles. File 870 (Logical Link) and file 869.2 (HL LOWER LEVEL PROTOCOL\n Link Manager Start/Stop."\n \n=========================================================================\n \nFor a complete and up-to-date set of documents, tutorials and\npresentations (and access to the HL7 Standard) please\nvisit the OpenVista Website (frequently) at:\n \nhttp://vista2.domain.ext/openvista/\n \nPARAMETER) have been merged into a single file.\nAt this site, you'll be able to find the new DEVELOPER MANUAL as well as\nsupplemental information on DYNAMIC ADDRESSING and TCP/IP SUPPORT.\n=========================================================================\n \n \n \n Interface Configuration with Patch 57\n \nThis section explains what has changed with Patch 57, and how the various\nfiles and fields will be used and the new business rules associated with\nGroup and Part 2 of the OpenVISTA Tactical Plan.\n \nvalidating a message header.\n \n Event Point Protocols\n \nAn event point protocol is a specific type of HL7 protocol defined in file\n101. It represents the sending side of a particular HL7 transaction. It\ndoes not have to be a VISTA event point. However, if the event point\noriginates in VISTA, several fields have been renamed along with changes\nto underlying code to more clearly define how VISTA HL7 uses them. When a\nmessage is being generated in VISTA, the header will contain the data from\n6. Response message type and event type can now be different from the\nthese fields and is delivered to each of the subscribers found in the\nSUBSCRIBERS multiple. Note that the ITEM multiple is no longer used for\nHL7 transactions.\n \nEvent Driver Protocol Key Fields\n \n770.1 SENDING APPLICATION (P771), [770;1]\n770.3 TRANSACTION MESSAGE TYPE (P771.2'), [770;3]\n770.4 EVENT TYPE (P779.001'), [770;4]\n770.6 PROCESSING ID (S), [770;6]\ninitial message's message type/event type pair. The Transaction Message\n770.8 ACCEPT ACK CODE (P779.003'), [770;8]\n770.9 APPLICATION ACK TYPE (P779.003'), [770;9]\n770.95 VERSION ID (*P771.5'), [770;10]\n772 RESPONSE PROCESSING ROUTINE (K), [772;E1,245]\n775 SUBSCRIBERS (Multiple-101.0775), [775;0]\n .01 SUBSCRIBERS (M*P101), [0;1]\n \n \n Subscriber Protocols\n \ntype and Event type are no longer defined on the subscriber protocol for a\nThis type of protocol contains all of the parameters for and is always\nassociated with the RECEIVING SYSTEM. The logical link field can be used\nto describe a single point-to-point interface between a sending and\nreceiving system. If this interface included two VISTA systems, the\nlogical link would always point to the remote system. All other settings\nin the interface definition would remain the same on both systems. The\nRESPONSE MESSAGE TYPE and EVENT TYPE are now used only for responses. \n \nWhen a message is received, the following validation checks are performed.\nOn the receiving system, the HL7 package parses the inbound message header\nmessage to be successfully delivered. This information is now derived from\nand identifies the Sending Application, Receiving Application, Message\nType, Event Type and version. If the event type is missing, it validates\nthat the version is less than 2.2. It validates the sending and receiving\napplication by checking them against the Application Parameter file. If\nthey are missing or "Inactive" an error is logged. It then looks up the\nEvent Driver protocol using the AHL1 cross-reference or, if missing the\nevent type, uses the new AHL21 cross-reference on file 101. Delivery to\nthe Subscriber protocol is then based on Receiving Application. An error\nis recorded if either the event driver or subscriber protocol cannot be\nfound. Next, HL7 sets the logical link for the "return path" based on the\nthe Event Point Protocol only. The Response Message Type and Event Type\nentry in the logical link field, (field 770.7). HL7 then checks to see if\nthe sending and/or receiving facility fields are required for each\napplication in the transaction (file 771). If the sending or receiving\nfacility is required and the header is blank an error is logged. If the\nfacility information in the header differs from data in file 771 an error\nis logged. If no data exists in the application parameter file but the\nfacility information is required, HL7 expects the header to contain the\nnew default facility data. The receiving facility data is checked against\nthe receiving system's site parameter settings and the sending facility\ndata is checked against the logical link definition (file 870). If the\nfields are now used for defining the message type and event type of the\nsending facility data (Domain name) is present and cannot resolve to a\nlogical link, an error is logged, otherwise, the logical link of the\nsending facility is used as the return path for responses regardless of\nhow the subscriber protocol logical link field was defined.\n \nSubscriber Protocol Key Fields:\n \n770.11 RESPONSE MESSAGE TYPE (P771.2'), [770;11]\n770.2 RECEIVING APPLICATION (P771), [770;2]\n770.4 EVENT TYPE (P779.001'), [770;4]\nsubscriber response. \n770.6 PROCESSING ID (S), [770;6]\n770.7 LOGICAL LINK (P870'), [770;7]\n771 PROCESSING ROUTINE (K), [771;E1,245]\n773.1 SENDING FACILITY REQUIRED? (S), [773;1]\n773.2 RECEIVING FACILITY REQUIRED? (S), [773;2]\n773.3 SECURITY REQUIRED? (S), [773;3]\n773.4 DATE/TIME OF MESSAGE REQUIRED? (S), [773;4]\n774 ROUTING LOGIC (K), [774;E1,245]\n \n \n \n Application Parameter File\n \n \nThis file contains the basic settings needed to describe an application\nthat either sends or receives a message. \n \n**Note that the fields pertaining to VISTA HL7 version 1.5 have been\n marked for removal from the system.\n \nThe default field separator is the up-caret ("^") and the default encoding\n7. "Report" Option Fixed. The HL7 option, "Report" has been fixed to\ncharacters are "~|\\&." Developers are not required to use these defaults.\nThe preferred characters for the sake of message readability is the\nvertical bar ("|") as a field separator and "~^\\&" as the encoding\ncharacters. Note that the "^"-character cannot be placed first in the list\ndue to VA Fileman limitations.\n \n.01 NAME (RFX), [0;1]\n2 ACTIVE/INACTIVE (S), [0;2]\n3 FACILITY NAME (F), [0;3]\n4 MAIL GROUP (P3.8'), [0;4]\n \nproperly display non-TCP status codes and errors. The option has been\n5 *HL7 SEGMENT (Multiple-771.05), [SEG;0]\n .01 HL7 SEGMENT (MRP771.3'), [0;1]\n 2 FIELDS USED IN THIS SEGMENT (RF), [F;1]\n6 *HL7 MESSAGE (Multiple-771.06), [MSG;0]\n .01 HL7 MESSAGE (MRP771.2'), [0;1]\n 1 PROCESSING ROUTINE (RF), [R;E1,17]\n7 COUNTRY CODE (P779.004'), [0;7]\n100 HL7 FIELD SEPARATOR (F), [FS;E1,2]\n101 HL7 ENCODING CHARACTERS (F), [EC;E1,4]\n \nrenamed to, "Link Error/Status Report (non-TCP)."\n \n Logical Links\n \nThe Logical Link File (870) and the HL LOWER LEVEL PROTOCOL PARAMETERS\nfile (869.2) have been merged into 870. The pointer from 870 to 869.2 has\nbeen changed to point to file 869.1 (HL LOWER LEVEL PROTOCOL TYPE). Users\nmay now define parameters for multiple LLP's under the same Logical Link\ndefinition and simply change the "type" pointer as needed. A number of\nfields in 869.2 have been removed since the standard does not allow the\nsettings to be altered. Since there has always been a 1:1 correspondence\n \nof Logical Links to LLP Parameters, users should be able to safely remove\nfile 869.2 after installing this patch.\n \n Properly Defined VISTA-to-VISTA Interface (Before HL*1.6*57)\n \nThe following is an example of a PROPERLY defined point-to-point interface\nbetween two VISTA Systems. In this example, the Sending System initiates\nan ADT message to the Receiving System and expects an Acknowledgement.\n \n4.1 Event Point Protocol Stored on Sending System \n8. Same-System Batch Messages. It has not been possible to exchange\n(Interface Workbench View):\n(1) JC ADT SERVER\n Text: Test tcp links\n Package:\n Message Type Rcvd: ADT Accept Acknowledgement: AL\n Event Type Rcvd: A01 Application Acknowledgement: NE\n Priority: <DEFAULT>\n Processing ID: DEBUG\n Version ID: 2.3\n Entry Action: <NONE>\nbatch messages between applications running on the same system. This has\n Exit Action: <NONE>\n Process ACK Routine: Q\n Subscribers: JC ADT RECV \n \n(VA FileMan View):\n NAME: JC ADT SERVER ITEM TEXT: Test tcp links\n TYPE: event driver CREATOR: CLEMENS,JOHN\n ITEM: JC ADT RECV\n TIMESTAMP: 56930,57258 \n SERVER APPLICATION: JC ADT SERVER\nbeen corrected.\n 770.3 MESSAGE TYPE RECEIVED: ADT \n 770.4 EVENT TYPE: A01\n PROCESSING ID: DEBUG \n ACCEPT ACK CODE: AL\n APPLICATION ACK TYPE: NE \n VERSION ID: 2.3\n GENERATE/PROCESS ACK ROUTINE: Q\n \n Subscriber Protocol Stored on Sending System\n \n \n(Interface Workbench View):\n(1) JC ADT RECV\n Text: TEST SUBSCRIBER USING TCP LINK\n Package:\n Message Type Rcvd: ACK Sending Facility Required: NO\n Message Type Sent: ADT Receiving Facility Required: NO\n Event Type Rcvd/Sent: A01 Date/Time of Message Required: YES\n Priority: IMMEDIATE Security Required:\n Processing ID: DEBUG Logical Link:\n Version ID: 2.3\n9. Message Header Enhancements to Improve Security. Message headers\n Routing Logic: <NONE>\n Entry Action: <NONE>\n Exit Action: <NONE>\n Process Routine: D REC^JCHL7TST \n \n(VA Fileman View): \nNAME: JC ADT RECV\n ITEM TEXT: TEST SUBSCRIBER USING TCP LINK\n DISABLE: YES \n TYPE: subscriber\nhave been enhanced to improve security. It is now possible to identify the\n CREATOR: CLEMENS,JOHN \n TIMESTAMP: 56930,56581\n CLIENT (SUBSCRIBER): JC TEST RECV \n 770.3 MESSAGE TYPE RECEIVED: ACK\n 770.4 EVENT TYPE: A01 \n PRIORITY: IMMEDIATE\n PROCESSING ID: DEBUG \n VERSION ID: 2.3\n 770.11 MESSAGE TYPE GENERATED: ADT \n GENERATE/PROCESS ROUTINE: D REC^JCHL7TST\nsource of a message and route (deferred) acknowledgements based entirely\n SENDING FACILITY REQUIRED?: NO RECEIVING FACILITY REQUIRED?: NO\n DATE/TIME OF MESSAGE REQUIRED?: YES \n \n \n Event Point Protocol Stored on the Receiving System\n \nOn the receiving system, the event point protocol is set up the same as on\nthe sending system, however, the subscriber protocol must be set up\ndifferently (see below).\n \n1. Exportable Interface Definitions. Class I Interface definitions are\non header information. When enabled, the facility id field contains the\n \n Subscriber Protocol Stored on the Receiving System\n \n(VA Fileman View):\nNAME: JC ADT RECV\n ITEM TEXT: TEST SUBSCRIBER USING TCP LINK\n DISABLE: YES \n TYPE: subscriber\n CREATOR: CLEMENS,JOHN \n TIMESTAMP: 56930,56581\nsource domain and destination domain as well as the Institution Number.\n CLIENT (SUBSCRIBER): JC ADT RECV \n 770.3 MESSAGE TYPE RECEIVED: ADT\n 770.4 EVENT TYPE: A01 \n PRIORITY: IMMEDIATE\n PROCESSING ID: DEBUG \n VERSION ID: 2.3\n 770.11 MESSAGE TYPE GENERATED: ACK \n GENERATE/PROCESS ROUTINE: D REC^JCHL7TST\n SENDING FACILITY REQUIRED?: NO RECEIVING FACILITY REQUIRED?: NO\n DATE/TIME OF MESSAGE REQUIRED?: YES \nFacility ID follows the HL7 Version 2.3 format, INSTITUTION\n \nNotice that the data for 770.3 and 770.11 must be reversed in order for\nHL7 to generate an ACK with the proper message type (ACK~A01) defined in\nthe header.\n \nIf the receiving system is capable of initiating the same transaction to\nthe sending system in this example, a new set of protocols and unique\nsending and receiving application definitions must be supplied.\n \n Properly Defined VISTA-to-VISTA Interface (After HL*1.6*57)\nNUMBER_cs_DOMAIN_NAME_cs_"DNS." For improved security, it is now possible\n \nAfter Patch 57 is installed, you will see the following differences:\n \nOn the sending system, field 770.3 and 770.4 of the EVENT POINT PROTOCOL\nare used to generate the header of the initial message. \n \nImportant consequence: The same setup can be exported to the receiving\nsystem because field 770.11 is correctly defined as "ACK" before and after\nthe installation of patch 57 and field 770.11 is used to generate the\nresponse. If an ack is not required (as is currently the case for many\nto validate a source domain against entries in the logical link file. When\nCIRN definitions) for a given interface the subscriber configuration is of\nno consequence. \n \nTherefore:\n \n1. No conversion of properly defined interfaces (see above) is\nnecessary.\n \n2. If the receiving system needs to initiate the same transaction as\nwell as receive it, the same two protocols can be used for both cases.\nvalid domain information is present in the message header, the HL7 package\nNote that some interface setups may be improperly defined, but work anyway\nbecause of unusual circumstances. All interfaces currently in production\nshould be reviewed based on this document.\n \nTo assist with this, an "interface debugger" routine (^HLERCHK) has been\nsupplied with patch 57 to examine one or all interfaces.\nUse this as a general tool for interface troubleshooting after\ninstalling the patch. It examines each HL7 Event Driver Protocol,\nSubscriber Protocols, and Application Definitions and generates a report\nof potential problems. It can be used with pre-Patch 57 setups as a guide\n \nfor converting an interface to post-57 format. However, if it reports\nissues with a pre-57 setup, this should not be interpreted as an\nindication that the interface is not set up correctly.\n \n \n Event Point Protocol (for both Sending and Receiving System)\n \nNAME: JC ADT SERVER TYPE: event driver\n CREATOR: CLEMENS,JOHN\n DESCRIPTION: Testing message transmissions \n(1) attempts to resolve the domain to the corresponding logical link and\n SENDING APPLICATION: JC NXT SEND\n 770.3 TRANSACTION MESSAGE TYPE: ADT \n 770.4 EVENT TYPE: A01\n PROCESSING ID: PRODUCTION \n ACCEPT ACK CODE: AL\n VERSION ID: 2.2 \n PROCESSING ROUTINE: Q\n RESPONSE PROCESSING ROUTINE: Q \n SENDING FACILITY REQUIRED?: YES\n RECEIVING FACILITY REQUIRED?: NO\n \n SUBSCRIBERS: JC ADT RECV\n \n Subscriber Protocol (for both Sending and Receiving System)\n \nNAME: JC ADT RECV TYPE: subscriber\n CREATOR: CLEMENS,JOHN \n RECEIVING APPLICATION: JC KRN REC\n 770.3 TRANSACTION MESSAGE TYPE: ADT \n 770.4 EVENT TYPE: A01\n PROCESSING ID: PRODUCTION\n(2) uses this information as the return path for responses in place of\n VERSION ID: 2.2 \n 770.11 RESPONSE MESSAGE TYPE: ACK\n PROCESSING ROUTINE: Q \n SENDING FACILITY REQUIRED?: NO\n RECEIVING FACILITY REQUIRED?: NO\nnow exportable to all VISTA systems with little or no modification at the\nwhat may be defined in the Protocol file, Logical Link field.\n \n10. Message Header Enhancements Facilitate Message Broker Integration.\nEnhancements to message header also facilitate the integration of Message\nBrokers into our Enterprise Application Integration strategy. In a future\nenhancement, it will be possible to query a DNS for current IP\ninformation. Note that any data that currently exists in the HL7\nApplication Parameter file (771), Facility ID field, overrides this\nenhancement. Data for the 'default' Sending Facility ID (if required and\nno Application Parameter is defined) is derived from the HL7 Communication\nsite. \nServer Parameter file and edited using the option, Edit Site Parameters.\nData for the Receiving Facility ID field is derived from the HL7 Logical\nLink File (870).\n \n11. Processing ID Field Checking. Another improved security feature\nincludes a check of the processing id field against the protocol\ndefinition or the site parameter file. On the receiving system, a mismatch\nbetween the message and the local definition results in an error. This can\nprevent test or debug messages from being processed in production\naccounts, and vice versa. \n \n \n12. Startup and Shutdown Enhancements. A new option has been created,\n"Stop All Logical Links And Filers". The "Restart All Links And Filers"\noption has also been fixed; it was shutting down all links, and then\nrestarting only those links with AUTOSTART ENABLED. Now only AUTOSTART\nlinks are shut down and restarted.\n \n13. Interface Workbench Replacement. The former HL7 option, "Interface\nWorkbench," has been replaced. Due to the HL7 package's underlying\narchitecture, it is relatively unintuitive to use and has been a problem\n2. Reduction in Interface Development, Testing and Activation Time.\nto maintain. The new user interface also eliminates 21 routines and 62\nprotocols.\n \n14. Message Synchronization Over TCP. When a connection is broken it is\npossible for subsequent transactions to get out of synch. A fix is\nprovided to assist with re-synchronizing the two systems. The following\nchanges were added:\n \n(1) A new field has been added to the HL LOGICAL LINK file, #870. When a TCP\n client exceeds the parameter value for the maximum number of\n\n\nThis patch \nwith HL*1.6*39. If this is the case, it is important to insure that the\nlinks on both the sending and receiving systems are properly configured\nand enabled.\n \nIf there is no routing logic defined on the subscriber protocol, Vista HL7\nwill assume that the link defined on the subscriber protocol is the\ncorrect return path and Mailman will not be queried.\n \n2. Fixes a corrupted node found on the logical link, LR NCH-L which\nprevented patch HL*1.6*57 from converting this link.\n1. Resolves an issue with how to address responses to messages\n \n \n The following routines are included in this patch. The second line of\neach of these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ========== \narriving over a Mailman-type Logical Link. \n HLTP01 5262489 5578885 **2,25,34,47,60**\n HLPAT60 **NEW** 805414\n \n \nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n \n \n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Shut Down All Logical Links\n Stop all incoming filers\n Stop all outgoing filers\n TCP/IP Link Manager Start/Stop\nIf ROUTING LOGIC is defined, the response will be dynamically addressed\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2 Verify Checksums in Transport Global \nusing the SOURCE DOMAIN provided by querying Mailman. In some cases this\n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*60\n =========\n \n Answer 'YES' to 'Want KIDS to Rebuild Menu Trees upon Completion\n of Install?'.\n \ncould result in a response being returned over a logical link that is\n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'.\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n 'Restart/Start All Links and Filers' option. \n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\ndifferent from the one the message arrived on. Specifically, the source\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager using the option: "TCP/IP\n Link Manager Start/Stop."\ndomain will resolve to one of the VA-namespaced logical links exported\n\n
\nThis patch addresses the following issues:\n \nRoutine Modifications:\n======================\nThe following routines are included in this patch. The second line of\nthese routines now look like:\n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \nCHECK^XTSUMBLD results: \n \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n HLCS2 10072062 10270936 14,40,43,49,57,58\n HLCSTCP 5152314 5155167 19,43,49,57,58\n HLCSUTL 5134775 6479348 2,19,58\n HLMA 5502295 6284735 19,43,58\n HLMA2 7268935 7530649 19,43,57,58\n HLSUB 5277110 5501510 14,57,58\n HLTP3 14050232 14451393 19,43,57,58 \n HLTP31 1680845 1651062 57,58\n1. ISB-1299-31632, AUS-1299-N1595: Errors when using HL7 Ping option. After\n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n \n 3. Use the option 'Stop All Messaging Background Processes' to disable\n error, ping doesn't work for any site.\n all links and filers.\n \n For DSM sites ONLY, if you have an HL7 UCX Service associated\n with the account(uci/directory) where you are installing this patch,\n please disable this service.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your\n2. DET-1199-41731: Undefined error when transmitting HL7 messages.\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n 2 Verify Checksums in Transport Global\n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global\n 6 Install Package(s) \n INSTALL NAME: HL*1.6*58\n3. TAM-1199-32092: The option HL TASK RESTART, start wrong number of\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the\n 'Restart All Links and Filers' option.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n------------------------------------------------------------------------------\n outbound filers.\nNew Public Functions (only for TCP messages)\n \n $$MSGLINE(msgid)\n return the number of lines in a message header and text\n input: msgid = message id\n output: return number of lines\n \n $$MSG^HLCSUTL(msgid, ref)\n return the message header and text in the given reference\n input: msgid = message id\n4. Support for CPRS Remote Patient Data View project.\n ref = closed local or global reference to place message\n output: return 1 for success and 0 if message doesn't exist\n The message is returned with blank lines between each line.\n example:\n \nref(1)=MSH^~|\\&^VOICERAD^^RADIOLOGY^^20000110145151-0800^^ORU~R01^1231^T^2.2\nref(2)=\nref(3)=PID^^^100~10~M11^^JONES~JOHN~J^^19421112^M^^^^^^^^^^123456789\nref(4)=\nref(5)=OBR^^^^7089898.8543-1~043091-66~L^^^199104301200^"^"^^^^^"^^3232~HARR\n5. Cleans up application variables between inbound transactions.\nIS~JACK^^^^MEDICINE^^199104301010\nref(6)=\nref(7)=OBX^^TX^I~IMPRESSION~L^^HEART NORMAL SIZE\nref(8)=\nref(9)=OBX^^ST^D~DIAGNOSTIC CODE~L^^NORMAL\nref(10)=\nref(11)=OBX^^TX^R~REPORT~L^^Heart appears to be of normal size.\nref(12)=\nref(13)=OBX^^TX^R~REPORT~L^^No infiltrate or abnormal mass noted.\nref(14)=\n\n
\nThis patch introduces DNS support for Vista HL7. In order to conduct HL7\nmade to the locally specified Domain Name Server (found in the Kernel Site\n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'.\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the\n \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\nParameters) to retrieve the current IP address. This feature was\n (Note that links that do not have "autostart" enabled will need\n to be restarted manually)\n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager using the option: "TCP/IP\n Link Manager Start/Stop."\nintroduced in Kernel patch XU*8*142. One or more IP addresses may be\nregistered on the DNS systems. The DNS was initially seeded with IP\ninformation supplied by HL*1.6*39 and any subsequent changes made to date\nto the VA* and MPI logical links. These IP addresses are associated\nspecifically with the service "HL7" on the DNS and the port 5000. The port\nnumber is currently fixed for HL7 and should not be changed. If only one\nIP address is returned, it will be stored in the site's local Logical Link\nfile and used for subsequent connections. If more than one IP is returned,\nmessage exchange between sites using TCP, the TCP/IP address of each site\neach address will be tried in sequence until a successful connection is\nmade. The successful IP address will then be stored and used until the\nnext connection attempt that fails.\n \nQueries to the DNS will work only if the Logical Link (file 870) points to\nthe correct Domain (file 4.2). Review the link definitions paying\nparticular attention to those links in your VISN and verify that the\nDomain field is defined correctly.\n \nThe Logical Link that represents your site should be configured as a\nrunning an HL7 service must be known by all other sites. If the address is\n"multithreaded listener" to receive INBOUND connection requests. The IP\naddress and port for this listener is known by all other sites and\nreferenced by them to establish a connection. Changing the IP address will\nprevent sites from establishing a connection. Therefore, if you wish to\nestablish a new IP address, your VA DNS must be updated in advance of the\nchange. It must contain an entry in the format, HL7.yoursite.domain.ext,\nand your new TCP/IP address. For example, DNS will contain an entry for\nBay Pines VA looking like, "HL7.BAY-PINES.DOMAIN.EXT." This entry will\nreturn a TCP/IP address of 152.130.80.5. \n \nchanged, such as from "152.x.x.x" to "10.x.x.x," or when the HL7 service\nPlease note that the HL7 development team is not involved with maintenance\nof the VA's DNS systems. Questions should be refered to your local or\nVISN-level DNS administrator, or via MS Exchange to the group, "VHA CIO\nDNS ADMIN."\n \nFollowing the installation of this patch you should enable your TCP/IP\nlistener for inbound HL7 connections. Detailed instructions for this may\nbe found in the HL7 Document, "Vista HL7 Site Manager and Developer\nManual" released as HL*1.6*56. Here, you will find information for both\nCache and for configuring UCX/TCP services under the VMS operating system.\nis moved to a different computer, or when multiple computers are able to\n \nThe following routines are included in this patch. The second line of\neach of these routines now looks like:\n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ========== \nsupport HL7 services at a single domain, other sites can use DNS to\n HLCSTCP2 10328595 11299763 **19,43,49,57,63**\n HLMA 6284735 7929932 **19,43,58,63**\n \n List of preceding patches: 57, 58\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n Installation Instructions: \n ==========================\n 1. Users are allowed to be on the system during the installation. \n \n"discover" this information without interruption in message exchange.\n 2. DSM SITES: Review your mapped set. If any of the routines listed\n in the Routine Summary section are mapped, they should be removed\n from the mapped set at this time.\n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n \n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2 Verify Checksums in Transport Global \nWhen a connection attempt over a TCP Logical Link fails, a call will be\n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*63\n =========\n \n Answer 'NO' to 'Want KIDS to Rebuild Menu Trees upon Completion\n of Install?'.\n \n\n
\nThis patch solves the following problems:\n \n 1. Fayetteville\n 2. Martinsburg\n \n \nRoutine Summary:\n================\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like:\n \n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995\n \n \nChecksums:\n==========\n \n Routine Name Checksum Before Checksum After Patch List\n ------------ --------------- -------------- ------------------\n HLCSQUE 4308358 4338251 14,61\n HLCSREQ 1749378 1790153 61\n 1. NOIS MWV-1297-20006: Requeuer screen didn't show the correct\n \n \n From CHECK^XTSUMBLD \n \n \nInstallation Instructions:\n==========================\n 1. Users are allowed to be on the system during the installation.\n 2. Stop all the Logical links, incoming and outgoing filers.\n 3. DSM SITES: Review your mapped set. If any of the routines listed in\n information in columns "Queue Size" and "Pending."\n the Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system. \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n 2. Fixes the DICN-Error nodes problems for "IN" queue of HL LOGICAL LINK\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*61\n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n 6. DSM Sites: Rebuild your mapped set if necessary.\n 7. Restart all the Logical links, incoming and outgoing filers, which\n file(#870).\n have been stopped in step #2.\n \n \nTest sites :\n\n
\nThe ^HLCS global is reported to be growing rapidly and uncontrollably.\ncall to $$DT^XLFDT.\n-The subject field of the message has been modified slightly. The sending\nfacility now derives the site name from the ^VASITE call.\n-An effort has been made to optimize the transfer of message text from\n^HLCS to ^XMB. It now uses the merge command to move text 100 lines at a\ntime into ^XMB. Please note that any benefit derived from this change has\nnot been proven yet.\n \nThis patch contains the following routine:\n \nMailman-type Logical Links are growing continuously because messages are\n^HLCSMM\n \nThe second line now looks like this:\n ;;1.6;HEALTH LEVEL SEVEN;**17**;Oct 13, 1995\n \n \nInstallation\n \no Disable all HL7 version 1.6 OUTBOUND FILERS and\nwait for the process' to disappear from the system status.\nnever set to a 'done' status after it is handed off to Mailman.\n \n Select V1.6 OPTIONS Option: COMmunications Server\n 1 Edit Communication Server parameters\n 2 Manage incoming & outgoing filers ...\n 3 Monitor incoming & outgoing filers\n 4 Start LLP\n 5 Stop LLP\n 6 Systems Link Monitor\n 7 Logical Link Queue Management ...\n 8 Report\n \n \nSelect Communications Server Option: 2\n =\n 1 Start default number of incoming & outgoing filers\n 2 Start an incoming filer\n 3 Start an outgoing filer\n 4 Stop all incoming filers\n 5 Stop all outgoing filers\n 6 Stop an incoming filer\n 7 Stop an outgoing filer\nThis patch corrects the problem of uncontrolled growth of file 870.\n \nSelect Manage incoming & outgoing filers Option: 5\n =\n \nUse the option, SYSTEMS LINK MONITOR to check the status of messages being\nprocessed out of your active Logical Links. It will look SIMILAR to this:\n \n MESSAGES MESSAGES MESSAGES MESSAGES DEVICE \n NODE RECEIVED PROCESSED TO SEND SENT ON-LINE STATE \nAMB-CARE 0 0 1 1 Y OUT QUEUE\n \n \nNotice that MESSAGES TO SEND and MESSAGES SENT are equal. As long as the\nfilers are disabled, no new messages will be queued. It is now safe to\nCLEAR THE QUEUE OF ALL ENTRIES.\n \nSelect the option LOGICAL LINK QUEUE MANAGEMENT, then\nselect CLEAR A QUEUE OF ALL ENTRIES. Use this option to clear out all of\nyour 'Mailman' type links.\n \nNow disable the logical links you have just cleared and prepare to install\nFurther, it corrects the following miscellaneous problems:\nthis patch. Use the option, STOP LLP to shut down the links.\n \no AXP sites should check and remove HL* from their map sets.\n (Mapping of HL7 1.6 routines is not recommended at this time)\no Users may remain on the system.\no Load the KIDS BUILD FILE using the Packman option INSTALL/CHECK MESSAGE.\no On the KIDS menu, under the 'Installation' menu, use the following \n option: \n Select Installation Option: Install Package(s) \n ==================\n-The date field of the zero node in ^XMB(3.9 is set incorrectly if the\n Select INSTALL NAME: HL*1.6*17 \n =========\n Answer 'NO' to 'Want to DISABLE Schedule Options, Menu Options,\n and Protocols?' \no MSM Sites - Answer 'YES' to the question 'Want to MOVE routines to\n other CPUs?' Then enter the names of your other Compute and Print\n server(s). \n \nAfter the KIDS installation has completed, remember to re-enable all\npreviously disabled Logical Links (START LLP) and re-start your default\nbackground job has been running for several days. It is now updated with a\nnumber of INBOUND and OUTBOUND filers.\n\n
\n1. Introduces HL7 version 2.3.1 MESSAGE STRUCTURE components:\n \n INSTALL NAME: HL*1.6*59\n =========\n \n Answer 'NO' to 'Want KIDS to Rebuild Menu Trees upon Completion\n of Install?'.\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'.\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n3. In file 771, HL APPLICATION PARAMETER, the input transforms for FIELD\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the\n \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note that links that do not have "autostart" enabled will need\n to be restarted manually)\n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n SEPARATOR and ENCODING CHARACTERS have been modified to prevent reuse\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager using the option: "TCP/IP\n Link Manager Start/Stop."\n of the field separator in the encoding characters. Each of the\n characters defined must be unique.\n \n4. HL*1.6*57 introduced a new menu structure. However, the old, obsolete\n menus were not removed. This patch will remove them.\n \n5. Fixes a problem with STUB records left behind in file 870 (Logical\n -Introduces a new file (#779.005) to hold the new HL7 MESSAGE\n Link) resulting in freezing of links and the System Link Monitor as\n well as causing queues to grow until disk space is used up.\n \nNOTE: Some sites may have a considerable number of messages needing to be\npurged from file 870. Please consider disabling journalling of ^HLCS() for\nabout a week after installing this patch.\n \n6. Changes the PROCESSING ID field of file 101 to be no longer required.\nNote that HL7 message headers are populated with information for\n'TRAINING' or 'PRODUCTION' taken from the HL7 site parameters. Use the\n STRUCTURE CODES.\noption, SITE PARAMETER EDIT, to verify that your production account is\nidentified as such and your test/training account is identified as\n'TRAINING.' The event driver protocol PROCESSING ID field is now used only\nfor DEBUG mode. Debug mode will override your site parameter setting. Make\nsure the protocol is set to 'debug' on both the sending and receiving\nsystem.\n \n7. Corrects a problem with creating new subscriptions when a user edits\nthe zero node of file 774.\n \n -Adds a new field, MESSAGE STRUCTURE (#770.5), to the Protocol\nThis patch resolves the following NOIS calls:\n \n AMA-0300-70683\n ISD-0300-71919\n HOU-0400-71933\n \nThe following routines are included in this patch. The second line of\neach of these routines now looks like:\n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n file. When defined, the MESSAGE STRUCTURE will be added to the\n \n CHECK^XTSUMBLD results: \n \n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ========== \n HLCSHDR 7364841 7637619 **37,19,57,59**\n HLCSHDR1 7750238 8586633 **19,57,59**\n HLCSQUE 4338251 4440270 **14,61,59**\n HLCSQUE1 1150239 1371156 **14,59**\n HLFNC2 5397412 5365297 **2,26,57,59**\n version 2.3.1 message header.\n HLTP4 7805100 7964901 **19,57,59**\n HLTPCK1A 14402537 14751742 **2,25,34,57,59**\n HLTPCK2A 15262342 15611547 **19,57,59**\n HLUTIL2 5387464 5486507 **19,43,57,59**\n HLTPCK1 4288888 4452787 **8,36,59**\n HLTPCK2 3804314 3962788 **19,59**\n HLTP3 14451393 14649677 **19,43,57,58,59**\n HLSUB 5501510 5552075 **14,57,58,59**\n \n List of preceding patches: 14, 36, 57, 58, 61\n \n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n Installation Instructions: \n ==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed\n in the Routine Summary section are mapped, they should be removed\n from the mapped set at this time.\n \n2. The message type of outbound messages was incorrectly stored in file\n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 773. This has been fixed.\n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n\n
\nThis patch addresses the following issues:\n $$MSGACT^HLUTIL = outgoing message action, cancel or requeue\n position or # of retries^# open failed^ack timeout\n \n status:\n 0 = message doesn't exist\n 1 = pending transmission\n 1.5 = being tranmitted\n 1.7 = awaiting response, # of retries\n 2 = awaiting application ack\n 3 = successfully completed\n 4 = error\n $$CHKLL^HLUTIL = check setup of Logical Link\n 8 = being generated\n 9 = awaiting processing\n\n\n$$MSGACT^HLUTIL(X,HLIENACT) ;outgoing message action\n input value: X = message id\n HLIENACT = 1-cancel; 2-requeue\n\n return value: 1 = action sucessful\n 0 = action failed\n $$FLD^HLCSUTL = returns a field from a message segment\n\n\n$$CHKLL^HLUTIL(X) ;check setup of Logical Link\n input value: X = institution number or name\n\n return value: 1 = setup OK\n 0 = LL setup incorrect\n\n\n$$FLD^HLCSUTL(NODE,FLD) ;This function will return the value for the field\n\n input value: NODE = HLNODE from the HLNEXT call, passed by reference\n FLD = number, field position in segment\n note: HL("FS") must be defined\n\n return value: value for the field in this segment\n\nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n 1. Added new status, AWAITING RESPONSE, to the HL7 MESSAGE STATUS file.\n \n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n 2. New parameter, HL("ACKTIME"), will reset the Acknowledgement Timeout,\n\n For DSM sites ONLY, disabled all HL7 UCX Services \n for this installation.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n for the one message. This parameter can be passed in GENERATE^HLMA or\n options: \n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*64\n =========\n \n DIRECT^HLMA APIs.\n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'.\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note that links that do not have "autostart" enabled will need to\n 3. Retransmission alerts are no longer generated.\n be restarted manually)\n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager using the option: "TCP/IP\n Link Manager Start/Stop."\n\n 4. DEVNOTOPN errors will no longer be recorded.\n\nRoutine Information:\n====================\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;JUL 17,1995\n\n Checksum\nRoutine Old New 2nd Line\n======== ======== ======== ===================== \n 5. New APIs:\nHLCSAC 2497076 2564816 **43,64**\nHLCSTCP 5155167 5175308 **19,43,49,57,58,64**\nHLCSTCP1 4965932 5081718 **19,43,57,64**\nHLCSTCP2 11299763 11197019 **19,43,49,57,63,64**\nHLCSUTL 6479348 6969973 **2,19,58,64**\nHLMA2 7530649 7925412 **19,43,57,58,64**\nHLTF0 3173064 3232637 **12,19,64**\nHLUTIL 2643574 3175738 **36,19,57,64**\n\nList of preceding patches: 57, 58, 63\n $$MSGSTAT^HLUTIL = returns status of a message\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n\nDocumentation:\n==============\n\n$$MSGSTAT^HLUTIL(X) ;message status\n input value: X = message id\n\n return value: status^status updated^error msg.^error type pointer^queue\n\n\nThis patch addresses the following issues:\n Connect message. This is for the Remote Data View project.\n\n\nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n \n the Routine Summary section are mapped, they should be removed from \n 1. Corrects problem creating an acknowledgement message MSH for a serial\n the mapped set at this time. \n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n\n For DSM sites ONLY, disabled all HL7 UCX Services \n connection.\n for this installation.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2. Enhancements to the System Link Monitor. Display is now alphabetical\n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*65\n =========\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'.\n\n and views can also be defined. Use the 'Site Parameter Edit' option\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n\n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note that links that do not have "autostart" enabled will need to\n be restarted manually)\n \n to create Link Monitor VIEWS.\n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n \n 8. Start Link Manager using the option: "TCP/IP\n Link Manager Start/Stop."\n\n\nRoutine Information:\n 3. New computed field in file 773, MESSAGE SIZE. This field counts the\n====================\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;JUL 17,1995\n\n Checksum\nRoutine Old New 2nd Line\n======== ======== ======== ===================== \nHLCSHDR 7637619 7573404 **37,19,57,59,65**\nHLCSMON 10703763 11036657 **34,40,48,49,65**\n number of characters in a message. It can be used in FileMan reports.\nHLCSMON1 5535017 3592657 **15,40,49,65**\nHLCSUTL 6969973 7737730 **2,19,58,64,65**\nHLMA2 7925412 7999576 **19,43,57,58,64,65**\n\nList of preceding patches: 49, 59, 64\nSites should use CHECK^XTSUMBLD to verify checksums.\n 4. Update the INITIAL MESSAGE field in file 773 for a response to a Direct\n\n
\n \n are added to HL7 date/time formats whenever time is included.\nInstallation Instructions: \n==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n \n For DSM sites ONLY, disabled all HL7 UCX Services \n for this installation.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n Also, please install this patch prior to installing patch RG*1*4.\n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n This patch is needed by the CPRS Remote Data Views.\n 6 Install Package(s) \n INSTALL NAME: HL*1.6*66\n =========\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'.\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols?'.\n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n If RG*1*4 is already installed, install this patch as soon\n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note that links that do not have "autostart" enabled will need to\n be restarted manually)\n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service\n for this installation, you may now enable it.\n \n 7. DSM Sites: Rebuild your mapped set if necessary.\n as posssible.\n \n 8. Start Link Manager using the option: "TCP/IP\n Link Manager Start/Stop."\n \n Future patch XM*7.1*51, which will change the domain names for\n all sites which have requested it, will not be released until all\n sites have installed HL*1.6*66.\n *** PLEASE NOTE THE FOLLOWING: ***\n \n **********************************\n \nThis patch addresses the following issues:\n 1. ISA-0600-10916 Correct problem with HLDATE^HLFNC when midnight is\n used.\n 2. CHS-0499-43088 Corrects a problem with Mailman Logical Links when\n mail group has no members. Updated to use new Mailman API's and send a\n message to the HL7 mail group.\n 3. ISF-0600-61155 Prevents an UNDEFINED when the subscription control\n \n number is not passed into GET^HLSUB.\n 4. ISB-0600-32294 Prevents the loss of the 'AC' cross reference\n on pending messages.\n 5. WIM-0700-20527 PROBLEM ON SYSTEMS LINK MONITOR. Patch HL*1.6*65\n introduced some new enhancements to the HL7 System Link Monitor.\n However, this patch also introduced a new bug that prevented users\n from backing up a screen when in 'Screened' mode. This patch corrects\n this problem with the monitor.\n 6. General variable cleanup in routine HLTP3 associated with Dynamic\n Addressing and Enhanced Headers. This patch fixes the\n This patch requires patch XU*8.0*168 HL7 date fix.\n Invalid Message Control ID in MSA Segment that was encountered with\n patch RG*1*4 CPRS REMOTE DATA VIEWS.\n 7. Related NOISes:\n ELP-0700-72334 Undefined Variable @ SF+14~HLTPCK2A\n LAS-0700-62279 MESSAGE ERROR FROM NEW ORLEANS\n BIR-0700-32233 Undefined Variable\n MUR-0800-30482 <UNDEF(ECODE)>SF+14^HLTPCK2A\n PRE-0800-60365 $ZE= <UNDEFINED>SF+14^HLTPCK2A\n This patch fixes the undefined variable at SF+14^HLTPCK2A. This was\n first encountered after the staff at New Orleans VAMC changed their\n Also, this patch corrects the interpretation of midnight when\n domain entry to include the '.MED' in front of the '.DOMAIN.EXT' suffix.\n Afterwards, sites receiving CIRN/HL7 messages from New Orleans would\n encounter this error. In addition, this patch changes the way that it\n performs a FileMan lookup of the Domain Name. Previously, it was only\n based only on the .01/Name field. After this patch is installed, the\n lookup process will work with either the Name or Synonym.\n 8. Related NOISes:\n AUG-0800-32024 LINK HAS NEGATIVE NUMBERS\n AUG-0800-31661 HL7 INTERFACE NOT WORKING\n AUS-0800-N0079 Negative Numbers on Monitor\n converting FileMan to HL7 date/time formats and vice versa.\n ISB-0800-30179 Entries in the 'AC' x-ref but with a status of 3\n This patch fixes the problem where sites encountered negative\n numbers in the 'TO SEND' column of the HL7 System Link Monitor.\n These negative numbers were a result of the HL7 code inadvertently\n changing the status of messages to 'SUCCESSFULLY COMPLETED'\n in the wrong file. Although the 'AC' cross-reference existed\n for these messages, the status of 'SUCCESSFULLY COMPLETED' prevented\n these message from being delivered.\n In addition, the use of $$REPROC^HLUTIL(IEN, routine) extrinsic\n function after this patch is installed, will update the\n In addition, the Vista HL7 Functions $$HLDATE^HLFNC(X,Y) and\n DATE/TIME PROCESSED field(#100) in the HL7 MESSAGE ADMINISTRATION\n file (#870).\n \nRoutine Information:\n====================\nThe following routines are included in this patch. The second line of\neach of these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;JUL 17,1995\n \n Checksum\n $$FMDATE^HLFNC(X) now call the Kernel functions $$FMTHL7^XLFDT(X)\n Routine Old New 2nd Line\n ======== ======== ======== ===================== \n HLCSMM 2836421 2312930 **17,35,57,66**\n HLCSMON 11036657 11192960 **34,40,48,49,65,66**\n HLCSTCP2 11197019 11334736 **19,43,49,57,63,64,66**\n HLFNC 5785780 5669016 **38,42,51,66**\n HLMA 7929932 7962943 **19,43,58,63,66**\n HLSUB 5552075 5558527 **14,57,58,59,66**\n HLTP3 14649677 14792516 **19,43,57,58,59,66**\n HLTP31 1651062 1770560 **57,58,66**\n and $$HL7TFM^XLFDT(X) respectively. Furthermore, ZULU offsets\n HLTPCK2A 15611547 16050022 **19,57,59,66**\n HLUTIL 3175738 3187029 **36,19,57,64,66**\n \n \n List of preceding patches: 51, 58, 59, 63, 64, 65\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \nExternal patch dependency: XU*8.0*168 HL7 date fix.\n \n \n\n
\n * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\nTest Site: Milwaukee, WI; Puget Sound HCS; Grand Junction, CO\n5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu to load the\n KIDS package into a Transport global on your system. \n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n Select INSTALL NAME: HL*1.6*67 Loaded from Distribution <date/time>\nWhen sending HL7 transactions to other VA sites over TCP links, Cache/NT\n =========\n Install Questions for HL*1.6*67\n\n Want KIDS to INHIBIT LOGONS during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nsites must send an initial HELO to overcome buffering issues. However,\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n7. Cache/NT sites: Once the patch is installed, review the list of \nHL LOGICAL LINKs whose SAY HELO field was set to YES by the post-init, and\nmake sure they were all links to VA sites, and that no TCP links to VA sites\nwere left out. (If the name started with 'VA' it was considered a VA site.)\n8. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\nthe initial HELO is not part of the HL7 standard, and may cause a reject\n RA Restart/Start All Links and Filers\n (Note: Links which do not have "autostart" enabled will need to\n be restarted manually)\n \n9. DSM Sites: If you previously disabled an HL7 UCX Service for this\n installation, you may now enable it.\n10. DSM Sites: Rebuild your mapped set if necessary.\n11. Start Link Manager using the option: "TCP/IP Link Manager Start/Stop."\nerror when sent to a COTS system.\n\nThis patch adds a new field, SAY HELO, to file 870, HL LOGICAL LINK,\nso that for every logical link, the Cache/NT site can decide whether or\nnot to send the initial HELO. The default will be NO, since it is not\npart of the HL7 standard.\n ATTENTION\n\nThe form HL7 LOGICAL LINK has been updated to include this field. Only\nCache/NT sites should set it, since it does not apply to other sites,\nand will be ignored at other sites.\n\nAt Cache/NT sites with patch HL*1.6*39 (which distributed VA Logical Link\ndefinitions) installed, the post-init will go through file 870,\nHL LOGICAL LINK, and for every TCP link to a VA site (if the name of the\nlink starts with 'VA', OR if the link is 'MPIVA'), set SAY HELO to YES.\nIt will show you which links it has set. You should review the list and\n Read this patch. If you are a Cache/NT site, you MIGHT have to\nmanually correct any which shouldn't have been set, or set any that were\nmissed.\n\nThe post-init will NOT run at:\n- Cache/NT sites which have not installed patch HL*1.6*39.\n- non-Cache/NT sites.\n\nHere's the new field:\n\nSTANDARD DATA DICTIONARY #870 -- HL LOGICAL LINK FILE\n PERFORM MANUAL EDITS!\nSTORED IN ^HLCS(870,\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n870,400.07 SAY HELO 400;7 SET\n\n 'Y' FOR YES; \n 'N' FOR NO; \n LAST EDITED: NOV 02, 2000 \n * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\n HELP-PROMPT: Send initial HELO for Cache/NT TCP links? \n DESCRIPTION: This field is applicable only to Cache/NT sites\n with TCP links. If you are not a Cache/NT\n site, or this is not a TCP link, this field \n does not apply, AND will be ignored. \n\n If this TCP link is for a VA site, answer YES. \n If this TCP link is for a COTS system, answer\n NO. This is the default. \n\n\n TECHNICAL DESCR: When sending HL7 transactions to other VA sites\n over TCP links, Cache/NT sites must send an\n initial HELO to overcome buffering issues. \n However, the initial HELO is not part of the\n HL7 standard, and may cause a reject error when\n sent to a COTS system. \n\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*66.\n============================================================================\nPatch HL*1.6*67\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;JUL 17,1995\n\n Before After\nName Checksum Checksum Patch List\n---------------------------------------------------------------------\nHLCSTCP2 11334736 11552851 19,43,49,57,63,64,66,67\nHLPAT67 * new * 2870677 67\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nHLPAT67 is a post-init and has no user-callable entry points.\n============================================================================\n\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*66.\n1. Users may be on the system during the installation of this patch.\nNOIS: PUG-0800-52938\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s).\n3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n\n4. DSM sites: Disable all HL7 UCX Services for this installation.\n\n
\nPatch HL*1.6*68\n\n1. Ignores domain closures and security key requirements, so that it will\nsend to FOC-AUSTIN, even if that domain is closed or has a security key.\n\n2. Sites may again use the auto-startup feature for MailMan type Logical\nLinks. If DUZ is 0 or undefined, DUZ will be set to .5 (POSTMASTER), for\nthe purpose of sending the messages.\n\n3. Error message has been improved. If the message is not sent for some\nreason, the error message will clearly state the reason why. Sites are\n\nreminded to ensure that the mail group which receives error messages is\npopulated. To do this:\n\nW $$PARAM^HLCS2. Piece 8 should be the name of a mail group. You should \nbe in that mail group. This group receives error messages if there's any \nproblems in creating the HL7 MailMan messages. The subject is\n"Error handing HL7 message off to Mailman".\n\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*66.\nNOIS: MIW-0900-41651\n============================================================================\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;JUL 17,1995\n\n Before After\nName Checksum Checksum Patch List\n---------------------------------------------------------------------\nHLCSMM 2312930 3644711 17,35,57,66,68\nTest Site: Milwaukee, WI\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n============================================================================\n\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*66.\n1. Users may be on the system during the installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\nThis patch 'news' variables in routine ^HLCSMM so that they do not leak out\n affected routine(s).\n3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n\n4. DSM sites: Disable all HL7 UCX Services for this installation.\n5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu to load the\nand cause problems. ^HLCSMM uses MailMan to send HL7 messages for MailMan\n KIDS package into a Transport global on your system. \n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n Select INSTALL NAME: HL*1.6*68 Loaded from Distribution <date/time>\n =========\ntype Logical Links.\n Install Questions for HL*1.6*68\n\n Want KIDS to INHIBIT LOGONS during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n7. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note: Links which do not have "autostart" enabled will need to\n be restarted manually)\n \n8. DSM Sites: If you previously disabled an HL7 UCX Service for this\nThe following improvements are also made:\n installation, you may now enable it.\n9. DSM Sites: Rebuild your mapped set if necessary.\n10. Start Link Manager using the option: "TCP/IP Link Manager Start/Stop."\n\n
\nPatch to the HLCSMON routine.\n\n
\nFix free-text stored instead of internal entry number problem.\n\n
\n \n generated and sent to Forum.\n INSTALL NAME: HL*1.6*69 \n =========\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'. \n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n \n \n Filer and Link Management Options -> \n RA Restart/Start All Links and Filers \n (Note that links that do not have "autostart" enabled will need to \n be restarted manually) \n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service \n for this installation, you may now enable it. \n \n 7. DSM Sites: Rebuild your mapped set if necessary. \n \n This problem was originally indentified in Milwaukee when the Dictaphone\n 8. Start Link Manager using the option: "TCP/IP \n Link Manager Start/Stop." \n application tried to execute a MPI/PD processing routine (EN^RGADT).\n \n Most recently, the problem appeared at the Birmingham VAMC. Some user\n inactivated a Lab interface application which caused an endless loop\n creating application acks that were never received/processed because the\n VistA HL7 application was inactivated.\n \nThis patch addresses the following issues:\n The problem lies in the CONT^HLTP3 subroutines, the HL("EIDS") variable,\n defining the subscribing protocol, is not defined. The software sets the\n HL("EIDS") variable to HLEIDS. The value of HLEIDS is not reliable, in\n most cases the variable has not been properly set/killed.\n \n In addition, the inbound filers were not locking the cross-reference\n ^HLMA("AC","I",... in order to flush to global cache buffers.\n \n In this case, the HL7 link receiving a message for an application\n kills the cross-reference(entry in the inbound tcp/ip queue),\n \n releases other locks, the inbound filers kicks in and grabs the lock at a\n different parent level ^HLMA(ien), checks for the existence of\n ^HLMA("AC","I",LLien,MSGien) and since no locking was performed on this\n cross-reference, this piece of code thinks this entry exists. Hence, the\n inbound filers begin to process this message, finds\n variables left around from a previous message(MPI/PD or HL7 itself),\n invokes code that uses these variables to set other HL7 variables when\n these variables itself are not setup properly. This in turn causes the\n code to call the MPI/PD application which in turn fires off exception\n messages to Forum.\n 1. ISH-1000-42883 wrong processing routine being executed for VistA HL7 apps\n \n These problems may be triggered by an inbound HL7 message that was not\n properly constructed in terms of the HL7 MSH segment. The VistA HL7\n software needs from the MSH segment, the Sending/Receiving Application\n names, Message Type, Event Type and Version ID.\n The HL7 Protocol setups may also have triggered this problem if the data\n in the MSH segment of an inbound message does not match the interface\n definition setups.\n \n Therefore, sites will still need to correct problems with their local\n \n interfaces. This patch only prevents the wrong application from being\n executed.\n \nRoutine Information:\n====================\n The following routines are included in this patch. The second line of each\n of these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995\n \n CHECK^XTSUMBLD checksum results:\n 2. SDC-1100-60210 Problem with HL7/Radiology link\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ====================\n HLTP3 14792516 15038079 19,43,57,58,59,66,69\n \n List of preceding patches: 66\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n \nInstallation Instructions: \n \n==========================\n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in \n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and \n the Link Manager. Use the options: \n \n The wrong processing routine is being executed (EN^RGADT)\n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes \n LM TCP/IP Link Manager Start/Stop \n \n For DSM sites ONLY, disabled all HL7 UCX Services \n for this installation. \n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n for non-MPI/PD applications. This causes a MPI/PD exception to be\n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n\n\nThe test sites for Patch HL*1.6*76 are:\n \nan I/O problem will be encountered. Patch HL*1.6*76 addresses\nthese issues by passing back to the calling application information regarding\nany error it encounters. Furthermore, it cleans up the cross reference\nit created and closes the device before returning to the calling application.\nIn addition, the post-init routine HLPAT76 will find all incomplete messages\nthat were affected by READ errors prior to this patch. This post-init will\nset the status of these messages so that they do not affect other messages in\nthe queue.\n \nPart 5 - After the Integrated Billing (IB) patch IB*2*150 was activated,\n \nmany sites encountered several entries in their Lock Table. This was a result\nof the direct connect locking ^HLMA global nodes and never releasing the locks.\nThis IB patch utilizes an Integrated Billing Background Filer to send\nseveral HL7 messages. To achieve this, this filer calls the direct connect\nAPI to send these messages. However, each HL7 message sent adds two entries\ninto the Lock Table causing some sites to fill up their Lock Table.\nThis HL7 patch fixes this problem by having the direct connect API\nproperly release the locks when it no longer needs them.\n \n \nThis Patch Addresses the Following NOIS Calls:\nRoutine Information:\n====================\n \n The following routines are included in this patch. The second line of each\n of these routines now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;JUL 17,1995\n \n Checksum\n Routine Old New 2nd Line\n HLCSTCP2 11552851 11428718 **19,43,49,57,63,64,66,67,76**\n==============================================\n HLCSTCP3 new 1935770 **76**\n HLMA2 7999576 8028267 **19,43,57,58,64,65,76**\n HLPAT76 new 1888010 **76**\n \n List of preceding patches: 65, 67\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n This patch introduces the following new routines: HLCSTCP3 and HLPAT76.\n Routine HLPAT76 is a post-init and has no user-callable entry points.\n \n \nInstallation Instructions: \n==========================\n \n 1. Users are allowed to be on the system during this installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in \n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n \n 3. Use the VISTA HL7 Filer and Link Management options, listed below, to \n 1. ISH-0700-41306 Enhanced Message Header issue: 'AA' received before 'CA'\n shutdown (1) all Logical Links, (2) the incoming and outgoing filers, and \n (3) the Link Manager. Use the options: \n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes \n LM TCP/IP Link Manager Start/Stop \n \n DSM SITES ONLY: Disable all HL7 UCX Services for this installation.\n \n 4. Use the option INSTALL/CHECK MESSAGE located on the PackMan menu to load \n 2. BRX-0701-12759 VANJHL7 in error state\n the KIDS package onto your system.\n \n 5. Patch HL*1.6*76 has now been loaded into a Transport global on your \n system. The next step is to use KIDS to install the Transport global. To \n do this, follow the KIDS menu path to the Installation menu:\n \n KIDS Kernel Installation & Distribution System\n Installation\n \n On the Installation menu, use the following options: \n 3. BRX-0701-12760 Undefined error CHKMSG+6^HLCSTCP2\n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*76 \n =========\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'. \n 4. POR-0701-52464 problem with VANJH LINK\n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n \n 6. Follow the HL7 menu path to the option Restart/Start All Links and Filers\n to startup all Logical Links and incoming and outgoing filers:\n \n Filer and Link Management Options -> \n RA Restart/Start All Links and Filers \n \n 5. BHS-0701-12356 VABED Link\n NOTE: Links that do not have "Autostart" enabled will need to \n be restarted manually) \n \n DSM SITES ONLY: If you previously disabled an HL7 UCX Service \n for this installation, you may enable it now enable it. \n \n 7. DSM SITES: Rebuild your mapped set if necessary. \n \n 8. Start Link Manager using the option: TCP/IP Link Manager Start/Stop. \n=======================================\n 6. ERI-0701-22675 Possible run-away HL7 job on Sun 7/29/01\n \n \nThis patch is composed of the following five parts:\n===================================================\n \n 1. Part 1 addresses out of order HL7 acknowledgements on Cache' \n systems. \n 2. Part 2 addresses non-persistent TCP/IP client links, which are not \n maintaining a connection during the retention period. \n \n 3. Part 3 addresses the near SACC routine size limit (10K) of the HL7 routine\n HLCSTCP2.\n 4. Part 4 addresses direct connect handling network errors properly.\n Read errors encountered through the direct connect were affecting\n both the Institution File Redesign (IFR) clean-up and the activation \n of Integrated Billing (IB).\n 5. Part 5 addresses direct connect handling of M LOCKS.\n \n \nPart 1 - The out of order HL7 acknowledgements on Cache' systems are related\n 1. White River Junction VAMC.\nto the inconsistent use of OPEN parameters between client\nand server (listener) processes. These acknowledgements are communicating\nover a TCP/IP socket on Cache' systems.\n \nThe VISTA HL7 package makes use of the following Kernel APIs\nto open a TCP/IP socket:\n \n 1. CALL^%ZISTCP -- Used by the client. This API uses STREAM mode.\n 2. LISTEN^%ZISTCP -- Used by the single-threaded listener. This API uses\n packet mode.\n 2. Butler VAMC.\n 3. LISTEN^%ZISTCPS -- Used by the multi-threaded listener. This API uses\n packet mode.\n \nWhen initiated from Cache' to DSM systems, HL7 messages should look like this:\n \n Order Cache' DSM\n ===== ====== ===\n 1 client sends message----------------> listener\n 2 client <--------------------listener sends Commit ACK\n 3 listener <------------------client sends Application Response\n 3. Tuscaloosa VAMC.\n 4 listener sends Commit ACK------------> client\n \nHowever, with the inconsistent parameters used by the Kernel\nAPIs, listed above, the following HL7 message scenario occurs:\n \n Order Cache' DSM\n ===== ====== ===\n 1 client sends message----------------> listener\n 4 client <--------------------listener sends Commit ACK\n 2 listener <------------------client sends Application Response\n 4. Wilmington VAMC.\n 3 listener sends Commit ACK------------> client\n \nNotice that the Commit ACK (Order #4) for the initial message (Order #1)\narrives after the application response message (Order #2). This is happening\nbecause the client process is using stream mode (Kernel API CALL^%ZISTCP).\nSteam mode is causing the initial message to wait for the full timeout\nto expire on the READ before the client process actually sees\nwhat was just read. Therefore, if the READ TIMEOUT is set to 30 seconds,\nthe client will sit on the READ command for the entire 30 seconds\nwhile the listener process receives the application response\n 5. San Francisco VAMC.\nas soon as it is available.\n \n \nPart 2 - The second part of this patch will help reduce the OPEN failure rate\nthat may be related to rapid OPENS and CLOSES by maintaining the connection\nduring the retention period.\n \nPart 3 - This patch creates the new HL7 routine HLCSTCP3 to accommodate\nthe spillover in excess of 10K from HLCSTCP2.\n \n 6. Loma Linda VAMC\nPart 4 - The Institution File Redesign (IFR) Patch XU*8*206 may encounter\nproblems with the clean-up process if network problems are present.\nDuring the clean-up, IFR will download the Master Institution File from FORUM.\nThis is done via an HL7 feature called "direct connect". The VISTA HL7\ndevelopers have discovered a problem when read errors are encountered\nacross the wide area network when using the direct connect.\nOnce this read error is encountered, it causes an error in the direct connect\nand the connection is dropped and the IFR clean-up encounters an error.\nWhen this happens, the direct connect does not clear the cross reference\nit created. Subsequently, when the clean-up is restarted,\n\n
\nThis patch enhances the purge utility by supporting a 'vaporization date'\nfor HL7 messages. See the patch module for details.\n\n
\nTest sites: Grand Junction, El Paso, San Francisco, Big Spring\nBilling patch was released. (There was no problem with the Integrated\nBilling (IB) patch. But after the patch, IB used some parts of the\nHL7 package differently than before.) Some problems were fixed by\nHL*1.6*76, but problems remained. After patch HL*1.6*76 was installed,\nREAD and WRITE errors remained, but were more specific to Cache sites.\nThis patch fixes the additional problems not fixed by HL*1.6*76.\n \nThe two routines included in this patch are shown below, along with\neach routine's second line.\n \n \n Routine Second Line\n ========= =========================================================\n HLCSTCP2 ;;1.6;HEALTH LEVEL SEVEN;**19,43,49,57,63,64,66,67,76,77\n **;JUL 17,1995\n HLCSTCP3 ;;1.6;HEALTH LEVEL SEVEN;**76,77**;JUL 17, 1995\n \nThe VA Kernel checksums for these routines (calculated using\nCHECK^XTSUMBLD) are listed below.\n \n Checksum Checksum\nNOIS: ELP-0801-70936, GRJ-0801-51450, MAN-0701-12428,\n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== =====================\n HLCSTCP2 11428718 12129232 **19,43,49,57,63,64,66,\n 67,76,77**\n HLCSTCP3 1935770 2092970 **19,57,59,72,80**\n \nSites should use CHECK^XTSUMBLD to verify checksums after patch\ninstallation.\n \n Installation Instructions:\n PRO-0801-11300\n ==========================\n \n NOTICE: Do no proceed unless patch HL*1.6*76 has been installed.\n \n 1. Users are allowed to be on the system during the installation.\n \n 2. AXP/DSM SITES: Review your mapped routine set. If any of the\n routines listed in the ROUTINE SUMMARY section are mapped, they\n should be removed from the mapped set at this time.\n \n \n 3. Shutdown all Logical Links, incoming and outgoing filers, and\n the Link Manager using the Filer and Link Management options\n listed below.\n \n Stop All Messaging Background Processes [HL STOP ALL]\n TCP/IP Link Manager Start/Stop [HL START/STOP LINK MANAGER]\n \n AXP/DSM SITES ONLY: Disable all HL7 UCX Services for this\n installation.\n \nNote: This patch requires that KIDS build HL*1.6*76\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 5. This patch is now loaded into a transport global on your\n system. The next step is to use KIDS to install the Transport\n global. This is done using the 'Installation' menu's 'Install\n Package(s) [XPD INSTALL BUILD]' menu option. When using this\n menu option to install the patch build, you will be asked\n several questions. The questions, and the answers you should\n supply, are shown below.\n be installed.\n \n INSTALL NAME: <HL*1.6*77>\n Want KIDS to INHIBIT LOGONS during the install? <NO>\n Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? <NO>\n \n 6. Start up all Logical Links and incoming and outgoing filers using\n the Filer and Link Management Option's 'Restart/Start All Links\n and Filers [HL TASK RESTART]' menu option.\n \n \n (Note that links that do not have "autostart" enabled will need\n to be restarted manually.)\n \n AXP/DSM SITES ONLY: If you previously disabled an HL7 UCX Service\n for this installation, you may enable it now enable it.\n \n 7. AXP/DSM Sites: After the patch has been installed, rebuild your\n map set, if necessary.\n \n 8. Start Link Manager using the 'TCP/IP Link Manager Start/Stop [HL\nPatch HL*1.6*76 fixed problems encountered when a recent Integrated\n START/STOP LINK MANAGER]' menu option.\n\n
\nPatch HL*1.6*81, Correct setup for sites using DNS and HL7\n READ THIS IMPORTANT INFORMATIONAL PATCH\n * * * * * * * * * * * * * * * * * * * *\n \n \nThis Patch Addresses the Following NOIS Call:\n---------------------------------------------\n \nISB-0901-31233, HL7 DNS uses and helpful Websites\n \n \n==========================================================\nProblem Scenario:\n-----------------\n \nThrough monitoring the HL7 Network between Veterans Affairs Medical\nCenters (VAMC) and the Master Patient Index (MPI), a need has arisen for\nclarification on the use of HL7 and Domain Name Servers (DNS). Mainly, the\nIP address where the HL7 Listener is running at the sites must match the\nIP address associated with the HL7 domain name in the DNS.\n \n \n \nPatch Solution:\n---------------\n \nThe express purpose of this Informational Patch is to make sites aware of\nthe HL7 Frequently Asked Questions (FAQ) web site. It addresses\ninformation on DNS support as it relates to HL7. Specifically, it provides\ninformation on how to ensure that sites are correctly set up to use the\nDNS with respect to HL7. This is addressed in the FAQ beginning at the\nquestion "How do I correctly set up my site to use DNS?". \n \nCategory: INFORMATIONAL\nHere is the URL for the HL7 FAQ web site:\n \n http://vaww.vista.domain.ext/hl7/hl7_faq.htm.\n \n \nNote: Even though this is an informational patch, please be sure to \n install it so the FORUM Patch tracking system gets updated.\n \nInstallation Instructions:\n==========================\n \n \n1. Users are allowed to be on the system during the installation.\n \n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n3. This patch is now loaded into a transport global on your\n system. The next step is to use KIDS to install the Transport\n global. To do this, use the 'Installation [XPD INSTALLATION\n MENU]' menu. On this menu, use the following options in the\nDescription:\n order shown below:\n \n 3 Print Transport Global\n 6 Install Package(s)\n \n When using the 'Install Package(s)' option to install the patch \n build, you will be asked the following questions. The questions\n asked and the answers you should supply are shown below:\n \n INSTALL NAME: HL*1.6*81\n===========\n Want KIDS to INHIBIT LOGONS during the install? <NO>\n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? <NO>\n \n * * * * * * * * * * * * * * * * * * * *\n\n
\nThe test sites for Patch HL*1.6*75 are Bay Pines VAMC, Palo Alto VAMC, \nback up, the option forces you to stop the process before you can re-\nset to Shutdown, then the client logical link quits and the Link \nManager will not attempt to restart the Link. In this particular case,\nthe SHUTDOWN LLP field (#14) is set to YES in the HL LOGICAL LINKS \nfile.\n \nThe other condition in which the value Error gets stuffed in the STATE \nfield (#4) is when the client logical link gets an unexpected error. If \nthe client logical link encounters an error other than the expected \nerrors: OPENERR, NOTOPEN, DEVNOTOPN, WRITE, or READ, it logs the error \nin the error trap and shuts down the client logical link.\nenable it to continue the communication process.\n \nIn this case, the SHUTDOWN LLP field is set and the client logical link \nhas to be restarted manually.\n=======================================================================\n \n \nTHIS PATCH ADDRESSES THE FOLLOWING ISSUE:\n=========================================\n \n 1. E3R #14227, MAKE HL START ALITTLE SMARTER [#31168789]\n \n \n \nROUTINE INFORMATION: \n====================\n \nThe following routine is included in this patch. The second line of the \nroutine now looks like this: \n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;Oct 13, 1995 \n \nNote: Entries in the HL LOGICAL LINKS file (#870) that are in an Error \n Checksum \n Routine Old New 2nd Line \n ======== ======== ======== ====================\n \n HLCSLNCH 12643769 13101795 **6,19,43,49,57,75**\n \n List of preceding patches: 57\n \n Sites should use CHECK^XTSUMBLD to verify checksums. \n \n STATE can be identified on the System Link Monitor by the word \n \nINSTALLATION INSTRUCTIONS: \n==========================\n \n 1. Users are allowed to be on the system during the installation.\n \n 2. DSM SITES: Review your mapped set. If any of the routines listed \n in the Routine Summary section are mapped, they should be removed \n from the mapped set at this time. \n \n Error in the STATE column.\n 3. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 4. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global.\n To do this, on the KIDS menu under Installation, use the \n following options: \n \n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n \n INSTALL NAME: HL*1.6*75 \n \n =========\n \n Answer NO to the prompt 'Want KIDS to INHIBIT LOGONS during the \n install?'. \nThe following is a screen capture of the HL7 System Link Monitor with a\n \n Answer NO to the prompt 'Want to DISABLE Scheduled Options, \n Menu Options'.\n \n 5. DSM Sites: Rebuild your mapped set if necessary. \nclient logical link in an Error STATE.\n \nand San Francisco VAMC.\n \nHL7 System Link Monitor\n=======================================================================\n SYSTEM LINK MONITOR for ISC SALT LAKE CITY (T System)\n \n MESSAGES MESSAGES MESSAGES MESSAGES DEVICE \n NODE RECEIVED PROCESSED TO SEND SENT TYPE STATE\n \n VADAN 38 38 38 38 NC Error\n \n \n \n \n \n Incoming filers running => 1 TaskMan running \n Outgoing filers running => 1 Link Manager running\n \n Select a Command:\n (N)EXT (B)ACKUP (A)LL LINKS (S)CREENED (V)IEWS (Q)UIT (?) HELP:\n=======================================================================\n \n \n \nThe following screen capture shows the two steps required to re-enable \nthe client logical link (VADAN) shown in the previous screen capture.\n \n \nStep 1 (Screen Capture Begins Here)\n=======================================================================\n Select Communications Server Option: Start/Stop Links \n \n This option is used to launch the lower level protocol for the\nPATCH DESCRIPTION:\n appropriate device. Please select the node with which you want\n to communicate\n \n Select HL LOGICAL LINK NODE: VADAN\n \n The LLP was last started on APR 14, 2000 11:20:58.\n \n Okay to shut down this job? YES\n \n The job for the VADAN Lower Level Protocol will be shut down.\n==================\n=======================================================================\n(Screen Capture Ends Here For Step 1)\n \n \nStep 2 (Screen Capture Begins Here)\n=======================================================================\n \n Select Communications Server Option: Start/Stop Links\n \n This option is used to launch the lower level protocol for the\n \n appropriate device. Please select the node with which you want\n to communicate\n \n Select HL LOGICAL LINK NODE: VADAN\n \n The LLP was last shutdown on APR 17, 2000 13:32:47.\n This LLP has been enabled!\n=======================================================================\n(Screen Capture Ends Here For Step 2)\n \nCurrently if the System Link Monitor displays a client logical link in\n \nBefore this patch (Patch HL*1.6*75), using the option Start/Stop Links \nto re-enable a client logical link in an Error STATE was a two-step \nprocess. After this patch has been installed, using the option \nStart/Stop Links to re-enable a client logical link in an Error STATE \nwill become a one-step process. However, this will only apply to client \nlogical links in which the SHUTDOWN LLP field is set to YES while in an \nError STATE. (See the following explanation "Description of What Causes \nan Error State" for more information on Error States.)\n \nan Error STATE and you use the HL START option to attempt to start it\n \nDescription of What Causes an Error State\n=======================================================================\nError STATEs can be related to retransmissions. If the number of retry \nattempts has been exceeded, an alert is sent and the word Error appears \nin the STATE column on the System Link Monitor for that client logical \nlink. This relates to the EXCEED RE-TRANSMIT ACTION field (#200.021) in \nthe HL LOGICAL LINKS file. If the EXCEED RE-TRANSMIT ACTION field is \nset to Restart, the client logical link quits and the Link Manager \nqueues (restarts) the link. If the EXCEED RE-TRANSMIT ACTION field is \n\n
\nPatch HL*1.6*82\nprotocol during the APIs GENERATE^HLMA or DIRECT^HLMA, and any of the\nprotocols in HLL("LINKS") is not a subscriber type protocol, the message\nis created, but an error is returned.\n \nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*76.\n============================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n \n ;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;JUL 17,1995\n \n Before After\nName Checksum Checksum Patch List\n---------------------------------------------------------------------\nHLCS2 10270936 10941124 14,40,43,49,57,58,82\nHLMA 7962943 9200711 19,43,58,63,66,82\nHLMA2 8028267 8331015 19,43,57,58,64,65,76,82\n* Checksums produced by CHECK^XTSUMBLD\n \nNOIS: ISF-0600-61085\nThis patch introduces no new routines.\n============================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*76.\n1. Users may be on the system during the installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s).\n3. Shutdown all Logical Links and incoming and outgoing filers, and\nTest Sites: FO-OAKLAND\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n \n4. DSM sites: Disable all HL7 UCX Services for this installation.\n5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu to load the\n KIDS package into a Transport global on your system. \n6. On the KIDS:Installation menu, use the following options to install the\nIf you call the APIs GENERATE^HLMA or DIRECT^HLMA, with HLL("LINKS") pre-\n Transport Global:\n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n Select INSTALL NAME: HL*1.6*82 Loaded from Distribution <date/time>\n =========\n Install Questions for HL*1.6*82\n \nset, but incorrectly, the API should return an error, but it doesn't. This\n Want KIDS to INHIBIT LOGONS during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <Do NOT queue it!>\n ------------------\npatch ensures that an error is returned, before any message is created.\n7. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note: Links which do not have "autostart" enabled will need to\n be restarted manually)\n \n8. DSM Sites: If you previously disabled an HL7 UCX Service for this\n installation, you may now enable it.\n9. DSM Sites: Rebuild your mapped set if necessary.\n \n10. Start Link Manager using the option: "TCP/IP Link Manager Start/Stop."\nIf HLL("LINKS") is set in the routing logic or the entry action of a\n\n\nPatch HL*1.6*83\n \nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patch HL*1.6*66.\n============================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;JUL 17,1995\n \n Before After\n \nName Checksum Checksum Patch List\n---------------------------------------------------------------------\nHLSUB 5558527 5395528 14,57,58,59,66,83\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n============================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when activity is at\nNOIS: ISA-0800-11764\na minimum. It requires HL7 patch HL*1.6*66.\n1. Users may be on the system during the installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s).\n3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\nTest Sites: FO-ALBANY\n \n4. DSM sites: Disable all HL7 UCX Services for this installation.\n5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu to load the\n KIDS package into a Transport global on your system. \n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \nIf VistA HL7 is processing an HL7 message, and calls the API UPD^HLSUB\n 6 Install Package(s) \n Select INSTALL NAME: HL*1.6*83 Loaded from Distribution <date/time>\n =========\n Install Questions for HL*1.6*83\n \n Want KIDS to INHIBIT LOGONS during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nto add/update a subscription, and the 5th parameter indicates that the\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n7. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note: Links which do not have "autostart" enabled will need to\ntermination date should be deleted, and there's already a subscription\n be restarted manually)\n \n8. DSM Sites: If you previously disabled an HL7 UCX Service for this\n installation, you may now enable it.\n9. DSM Sites: Rebuild your mapped set if necessary.\n10. Start Link Manager using the option: "TCP/IP Link Manager Start/Stop."\nwith a termination date, it fails to delete the termination date.\nThis patch fixes that. \n\n
\nHL7 Capacity Mgt Phase I API\n\n
\nPatch HL*1.6*62\ninbound filers. A whole file cross reference has been added to message\n Before After\nName Checksum Checksum Patch List\n---------------------------------------------------------------------\nHLCSDR1 10571563 8554313 2,22,27,30,34,62\nHLCSDR2 5218053 4813200 2,9,62\nHLCSIN 2517664 4825867 2,30,14,19,62\nHLCSOUT 4118513 4765416 25,30,62 \nHLCSUTL2 2181860 2309661 18,28,62\nHLPAT62 *NEW* 236063 62\nHLUOPT1 13112533 12526225 10,13,21,36,19,47,62\nSTATUS field of the IN QUEUE multiple of the HL LOGICAL LINK FILE, #870.\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nHLPAT62 - post-init for this patch has no user-callable entry points\n============================================================================\n\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patches HL*1.6*28, *34, & *47.\n1. Users may be on the system during the installation of this patch.\nThe inbound filers can now go directly to the logical links which have\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s).\n3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n\n4. DSM sites: Disable all HL7 UCX Services for this installation.\ninbound messages pending, instead of constantly checking each logical\n5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu to load the\n KIDS package into a Transport global on your system. \n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n 2 Verify Checksums in Transport Global \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n Select INSTALL NAME: HL*1.6*62 Loaded from Distribution <date/time>\nlink to see if any messages are pending.\n =========\n Install Questions for HL*1.6*62\n\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONS during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n7. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options ->\n RA Restart/Start All Links and Filers\n (Note: Links which do not have "autostart" enabled will need to\nThe post-init for this patch will go through file 870 and fire the new xref.\n be restarted manually)\n \n8. DSM Sites: If you previously disabled an HL7 UCX Service for this\n installation, you may now enable it.\n9. DSM Sites: Rebuild your mapped set if necessary.\n10. Start Link Manager using the option: "TCP/IP Link Manager Start/Stop."\n\nHere's the updated field with its new xref:\n* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\n\nSTANDARD DATA DICTIONARY #870.019 -- IN QUEUE SUB-FILE\nSTORED IN ^HLCS(870,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n870.019,1 STATUS 0;2 SET\n 'P' FOR PENDING; \n 'D' FOR DONE PROCESSING; \n 'S' FOR STUB RECORD; \n LAST EDITED: MAY 08, 2000 \nNOIS: LAS-0100-61912, GRJ-0400-51133, HIN-0501-42418\n HELP-PROMPT: This is the status of an individual message in \n the queue. These statuses control the flow and \n processing of the message. \n DESCRIPTION: Status of a particular message. Can be Stub,\n Pending, or Done. These statuses control the\n processing of a message. For example, a stub\n record is created when a message is enqueued,\n and cannot be processed until its status is\n changed from 'stub' to 'pending'. Changing\n this status is the last thing the Low Layer\nTest Sites: Las Vegas, NV; Grand Junction, CO\n Protocol does after reading in a message. \n Finally, once the message has been processed,\n its status is changed to 'done'. \n CROSS-REFERENCE: 870^AISTAT \n 1)= S ^HLCS(870,"AISTAT",$E(X,1,30),DA(1),DA)=""\n 2)= K ^HLCS(870,"AISTAT",$E(X,1,30),DA(1),DA)\n Used to quickly identify links with messages\n in any status, thus improving performance.\n* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\n\nThis patch increases the amount of time between checks to see if the filers\nThe option, HL PURGE TRANSMISSIONS, is updated to improve the description\nand to set the SCHEDULING RECOMMENDED field to YES.\n\nHere's the updated option:\n* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\nNAME: HL PURGE TRANSMISSIONS MENU TEXT: Purge Messages\nTYPE: run routine CREATOR: DIMICELI,RON\nPACKAGE: HEALTH LEVEL SEVEN\nDESCRIPTION: This option purges entries from the HL7 message files: \n 773 - HL7 MESSAGE ADMINISTRATION \nhave been asked to stop. In most cases, the check is performed at most\n 772 - HL7 MESSAGE TEXT \n \nThese files contain a record of all outgoing HL7 transmissions and their \nstatus. Messages are purged if they are in a certain status and are a\ncertain number of days old. The default parameters (number of days) are\ntaken from fields in file 869.3, HL COMMUNICATION SERVER PARAMETERS. The\nfields should be set such that a balance is struck between the need to\nkeep disk space from filling up and the need to keep messages around long\nenough so that they can be investigated in case problems arise. Please\nsee the descriptions of these fields for more information: \nonce a minute.\n 41 - PURGE COMPLETED MESSAGES \n 42 - PURGE AWAITING ACK MESSAGES \n 43 - PURGE ALL MESSAGES \n \nNote that the number of days in field 43 must be greater than or equal to\nthe number of days in field 42, which must be greater than or equal to the\nnumber of days in field 41. If any of the fields violates this rule, then\nthe default values of these fields will be used, instead. \n \nTo purge entries in an error status, run this option directly and answer\n\n'Yes' to the question about purging them. It is recommended that entries in\nan error status be reviewed before purging. For this reason, such messages\nare NOT purged by automatically recurring scheduled runs of this option. \n \nIt is recommended that this option be scheduled to run once a day to keep\nthe files from getting too large. On TaskMan's 'Edit Option Schedule', the\nTASK PARAMETERS field is ignored. Instead, the parameters are taken from\nthe fields in file 869.3, noted above. \nROUTINE: PURGE^HLUOPT1 TIMESTAMP: 55644,54515\nSCHEDULING RECOMMENDED: YES UPPERCASE MENU TEXT: PURGE MESSAGES\nFor serial connections, this patch also improves the efficiency of the\n* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\n\nNOTE: This patch should be installed during off hours, when activity is at\na minimum. It requires HL7 patches HL*1.6*28, *34, & *47.\n============================================================================\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;JUL 17,1995\n\n\n
\nTest sites: San Francisco VAMC, Bay Pines VAMC, Nashville VAMC\ncreating HL7 batch messages. A mismatch in field separator characters will\noccur in a message if a VistA application specifies a field separator\ncharacter other than the Circumflex.\n \nThis patch removes the dependency on hard-coded field separator characters\nin VistA HL7. This change will accommodate VistA applications that use\nfield separator characters other than the Circumflex, ensuring that batch\nmessages will have the same field separator character in all their\nsegments.\n \n \n \nRoutine Information:\n=====================\n \nThe following routine is included in this patch. The second line of the\nroutine now looks like this:\n \n;;1.6;HEALTH LEVEL SEVEN;<PATCHLIST>; Oct 13, 1995.\n \nThe VA Kernel checksums for this routine (calculated using \nNOIS: ISH-0701-40476, Incorrect field separator in BTS segment\nCHECK^XTSUMBLD) are listed below:\n \n Checksum Checksum \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== =====================\n HLTF1 9479987 9693677 **5,8,22,25,19,78**\n \nSites should use CHECK^XTSUMBLD to verify checksums after the patch\nhas been installed.\n \n \nInstallation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation.\n \n 2. AXP/DSM SITES: Review your mapped routine set. If any of the\n routines listed in the ROUTINE SUMMARY section are mapped, they\n should be removed from the mapped set at this time.\n \n 3. Shutdown all Logical Links, incoming and outgoing filers, and\nNote: This patch requires that KIDS build HL*1.6*19\n the Link Manager using the Filer and Link Management options\n listed below:\n \n Stop All Messaging Background Processes [HL STOP ALL]\n TCP Link Manager Start/Stop [HL START/STOP LINK MANAGER]\n \n AXP/DSM SITES ONLY: Disable all HL7 UCX Services for this\n installation.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n be installed.\n option will load the KIDS package onto your system.\n \n 5. This patch is now loaded into a transport global on your\n system. The next step is to use KIDS to install the Transport\n global. To do this, use the 'Installation [XPD INSTALLATION \n MENU]' menu. You should use each of the following 'Installation'\n menu options in the order shown below:\n \n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n \n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n \n When using the 'Install Package(s)' menu option to install \n the patch build, you will be asked several questions. The \n questions asked, and the answers you should supply, are \n shown below.\n \n INSTALL NAME: <HL*1.6*78>\nNOIS call ISH-0701-40476 reported the existence of the Circumflex\n Want KIDS to INHIBIT LOGONS during the install? <NO>\n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? <NO>\n \n 6. Start up all Logical Links and incoming and outgoing filers using\n the Filer and Link Management Option's 'Restart/Start All Links\n and Filers [HL TASK RESTART]' menu option.\n \n (Note that links that do not have "autostart" enabled will need\n to be restarted manually.)\ncharacter (^) hard-coded as the field separator in the BTS segment when\n \n AXP/DSM SITES ONLY: If you previously disabled an HL7 UCX Service\n for this installation, you may enable it now.\n \n 7. AXP/DSM Sites: After the patch has been installed, rebuild your\n map set, if necessary.\n \n 8. Start Link Manager using the 'TCP Link Manager Start/Stop [HL\n START/STOP LINK MANAGER]' menu option. \n\n
\nTest sites: Bay Pines, Grand Junction, Sheridan, Tampa,\n \n and Protocols?'. \n \n 6. Startup all Logical Links and incoming and outgoing filers. Use the \n \n Filer and Link Management Options -> \n RA Restart/Start All Links and Filers \n (Note that links that do not have "autostart" enabled will need to \n be restarted manually) \n \n For DSM sites ONLY, if you previously disabled an HL7 UCX Service \nDescription:\n for this installation, you may now enable it. \n \n 7. DSM Sites: Rebuild your mapped set if necessary. \n \n 8. Start Link Manager using the option: "TCP/IP \n Link Manager Start/Stop." \n============\n \nPatch HL*1.6*71 fixes the corruption of the MSH Header where the MSH segment \nis received a second time after the body of the HL7 message has been received. \nWhat occurs is the current VistA HL7 TCP/IP code attempts to reset itself when \nincomplete data is received. This usually happens when a timeout has expired \nand the complete MSH segment has not been received. When this happens, VistA \nHL7 drops original MSH Header. The original body of the message is now left \n Milwaukee, and Iron Mountain\nwithout the header. Next, the sender of the original message resends a repeat \nof the original MSH Header and the body again. The outcome is shown below:\n \n 1) Message body.\n 2) Message (MSH) header.\n 3) Message body. \n \nVistA HL7 now read 1) the Message body and 2) the Message Header as the\noriginal message header itself. \n \n \nAfter the installation of this patch (HL*1.6*71), VistA HL7 listeners will no \nlonger attempt to reset after timeouts have occurred, once a start block has\nbeen received.\n \nThis patch also fixes the problem where VistA HL7 will attempt to process an \nincomplete message. These incomplete messages are the result of a timeout \noccurring before the end-block character (<EB>) is reached while reading\ninbound data. Also, network performance issues may contribute to the\noccurrence of Read timeouts. Furthermore, large inbound messages (100 lines\nor more) with relatively short Read timeouts on the receiving side\nPatch HL*1.6*71 addresses the following NOIS:\ncan also increase the likelihood of receiving incomplete messages.\nThis patch will discard all incomplete messages as if no data\nhad been received. At which point, the sender of the HL7 message needs \nto resend the message again to ensure guaranteed delivery.\n \n \nRoutine Information:\n====================\nThe following routines are included in this patch. The second line\nof each of these routines now looks like:\n \n \n ;;1.6;HEALTH LEVEL SEVEN;<patchlist>;JUL 17,1995\n \n Checksum\n Routine Old New 2nd Line\n ======== ======== ======== ===================== \n HLCSTCP1 5081718 5982461 **19,43,57,64,71**\n \n List of preceding patches: 64\n Sites should use CHECK^XTSUMBLD to verify checksums.\n 1. ISH-1100-40056 mpi/pd: commit ack issue, 'MSH' multiple corruption\n \n \nInstallation Instructions: \n==========================\n \n 1. Users are allowed to be on the system during the installation. \n \n 2. DSM SITES: Review your mapped set. If any of the routines listed in\n the Routine Summary section are mapped, they should be removed from \n the mapped set at this time. \n 2. MAC-0101-61601 corrupted MSH multiple (773) \n \n 3. Shutdown all Logical Links and incoming and outgoing filers, and\n the Link Manager. Use the options:\n \n Filer and Link Management Options -> \n SA Stop All Messaging Background Processes\n LM TCP/IP Link Manager Start/Stop\n \n For DSM sites ONLY, disabled all HL7 UCX Services \n for this installation.\n 3. ISA-1101-11782 HL7 MESSAGE TRUNCATED ON REMOTE USER LOGGING\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global. \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n 2 Verify Checksums in Transport Global \n \n 3 Print Transport Global \n 4 Compare Transport Global to Current System \n 5 Backup a Transport Global \n 6 Install Package(s) \n INSTALL NAME: HL*1.6*71 \n =========\n \n Answer 'NO' to 'Want KIDS to INHIBIT LOGONS during the install?'. \n \n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n\n
\nThe Inbound and Outbound filers can be forced into an infinite loop if\n \n ;;1.6;HEALTH LEVEL SEVEN;**18**;Oct 13, 1995\n \nTo install this patch\n=====================\n \n1. Stop all running filers (select options 4 and 5, below)\n \nSelect Communications Server Option: MANage incoming & outgoing filers\n \nentries in file 869.3 (HL COMMUNICATION SERVER PARAMETERS) are deleted.\n \n 1 Start default number of incoming & outgoing filers\n 2 Start an incoming filer\n 3 Start an outgoing filer\n 4 Stop all incoming filers\n 5 Stop all outgoing filers\n 6 Stop an incoming filer\n 7 Stop an outgoing filer\n \n \nThe file and related monitors will then not provide accurate information\n2. AXP sites should check and remove HL* from their map sets.\n (Mapping of HL7 1.6 routines is not recommended at this time)\n \n3. Users may remain on the system.\n \n4. Load the KIDS BUILD FILE using the Packman option INSTALL/CHECK\nMESSAGE.\n \n5. On the KIDS menu, under the 'Installation' menu, use the following \n option: \nregarding the number of filers actually running on your system.\n Select Installation Option: Install Package(s) \n ==================\n Select INSTALL NAME: HL*1.6*18 \n =========\n Answer 'NO' to 'Want to DISABLE Schedule Options, Menu Options,\n and Protocols?' \n \n6. MSM Sites - Answer 'YES' to the question 'Want to MOVE routines to\n other CPUs?' Then enter the names of your other Compute and Print\n server(s). \n \n \n7. After the KIDS installation has completed, remember to re-start your\ndefault number of INBOUND and OUTBOUND filers. (option 1 above)\nThe routine ^HLCSUTL2 has been modified to signal a filer to stop whether\nthe user sets the stop flag or actually deletes the entry from the file.\n \nThe second line of HLCSUTL2 now looks like:\n\n
\nTest sites: MPI\nTMP("HCSI",$J,1). Inadequate coding in the Health Level Seven (HL7)\npackage's direct connect software is the cause of this problem. Patch\nHL*1.6*89 fixes this undefined error condition.\n \nThe routine HLCSAS is included in this patch. The first and second\nlines of this routine are shown below.\n \n HLCSAS ;ISCSF/RWF - MPI direct connect server ;02/19/99 11:44\n ;;1.6;HEALTH LEVEL SEVEN;**43,89**;Jul 17,1995\n \n \nThe VA Kernel checksum for the routine included in this patch\n(calculated using CHECK^XTSUMBLD) is listed below.\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== =====================\n HLCSAS 2943880 3066068 43,89\n \nSites should use CHECK^XTSUMBLD to verify checksums after patch\ninstallation.\nNOIS: ISF-0102-62265\n \n Installation Instructions:\n ==========================\n \n NOTICE: Do not proceed unless patch HL*1.6*43 has been installed.\n \n 1. Users are allowed to be on the system during the installation.\n \n 2. AXP/DSM SITES: Review your mapped routine set. If the\n routine listed in the ROUTINE SUMMARY section is mapped, it\n \n should be removed from the mapped set at this time.\n \n 3. Shutdown all Logical Links, incoming and outgoing filers, and\n the Link Manager using the Filer and Link Management options\n listed below.\n \n Stop All Messaging Background Processes [HL STOP ALL]\n TCP/IP Link Manager Start/Stop [HL START/STOP LINK MANAGER]\n \n AXP/DSM SITES ONLY: Disable all HL7 UCX Services for this\nNote: This patch requires that KIDS build HL*1.6*43\n installation.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 5. This patch is now loaded into a transport global on your\n system. The next step is to use KIDS to install the Transport\n global. This is done using the 'Installation' menu's 'Install\n Package(s) [XPD INSTALL BUILD]' menu option. When using this\n menu option to install the patch build, you will be asked\n be installed.\n several questions. The questions, and the answers you should\n supply, are shown below.\n \n INSTALL NAME: <HL*1.6*89>\n Want KIDS to INHIBIT LOGONS during the install? <NO>\n Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? <NO>\n \n 6. Start up all Logical Links and incoming and outgoing filers using\n the Filer and Link Management Option's 'Restart/Start All Links\n \n and Filers [HL TASK RESTART]' menu option.\n \n (Note that links that do not have "autostart" enabled will need\n to be restarted manually.)\n \n AXP/DSM SITES ONLY: If you previously disabled an HL7 UCX Service\n for this installation, you may enable it now.\n \n 7. AXP/DSM Sites: After the patch has been installed, rebuild your\n map set, if necessary.\nThe Master Patient Index (MPI) system sometimes experiences an undefined\n \n 8. Start Link Manager using the 'TCP/IP Link Manager Start/Stop [HL\n START/STOP LINK MANAGER]' menu option.\nerror at MPIDIRQ+5^MPIDIRQ. The undefined variable is the local variable\n\n\nThe purpose of this patch is to export the VAFHIE entry in the\n ACK TIMEOUT: 240\n \n2. The routines for this patch are new and can be deleted after\n installation; therefore routine mapping is not an issue for\n this patch.\n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n \n4. From this menu, you may elect to use the following options (when\n prompted for the INSTALL NAME, enter HL*1.6*92).\n TCP/IP ADDRESS: 127.0.0.1 \n \n (a) Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n \n (b) Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the\n patch is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n \n TCP/IP PORT: 5000\n (c) Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n (d) Print Transport Global - this option will allow you to view the\n components of the KIDS build.\n \n5. Use the Install Package(s) option and select the package HL*1.6*92.\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//',\n TCP/IP SERVICE TYPE: CLIENT (SENDER)\n respond NO.\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//', respond NO.\n \n8. Routines HLP92ENV and HLP92 can be deleted from your system after\n successful installation of this patch.\n \nThe Federal Heath Information Exchange (FHIE) will\nrequire this enhancement for viewing data from facilities outside\nthe Veteran's Health Administration (VHA). Patch HL*1.6*92 is\ndistributed as an EMERGENCY patch because it needs to be in place\nat all facilities to enable FHIE to begin data transmissions by April 25,\nHL LOGICAL LINK (#870) file. The VAFHIE node is distributed\n2002.\n \nInstructions in patch XM*999*148 must be followed prior to\ninstalling patch HL*1.6*92. XM*999*148 is an informational patch\nwith directions for creating the FHIE.DOMAIN.EXT domain.\n \nTest Sites:\n===========\nEl Paso VAMC\nSan Francisco VAMC\nwith data in the following fields:\nPuget Sound HCS\nWashington VAMC\n \nRoutine Summary:\n================\nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n \n;;1.6;HEALTH LEVEL SEVEN;**[Patch List]**;JUL 17, 1995\nCHECK^XTSUMBLD results:\n \n \nRoutine Before Patch After Patch \n-------- ------------ ------------ \nHLP92 N/A 7643045 \nHLP92ENV N/A 1183086 \n \nEnvironment Check Routine HLP92ENV:\n===================================\nThe environment check routine, HLP92ENV, checks to see if patch\nXM*999*148 is in place. It does this by checking for the existence\n NODE: VAFHIE\nof the FHIE.DOMAIN.EXT entry in the DOMAIN (#4.2) file. If the\nentry is not found, the routine aborts with the following message:\n \n "No DOMAIN (#4.2) file entry was found for FHIE.DOMAIN.EXT.\n Follow the instructions in VA MailMan patch XM*999*148 to create\n this new entry in the DOMAIN (#4.2) file. After the new DOMAIN\n has been created, re-install patch HL*1.6*92."\n \nPre-Install Routine PRE^HLP92:\n==============================\n INSTITUTION: AUSTIN\nThe pre-install routine, PRE^HLP92, looks for the AUSTIN (Station Number\n200) entry in the INSTITUTION (#4) file. If the entry is present, the\npre-install is done. If the entry does not exist, it is created. This\nentry is pointed to from the HL LOGICAL LINK (#870) file by the VAFHIE\nentry distributed in this patch.\n \nPost-Install Routine PST^HLP92:\n===============================\nThe post-install routine, PST^HLP92, sets the AUTOSTART (#4.5) field\nto Enabled for the VAFHIE entry in the HL LOGICAL LINK (#870) file.\n LLP TYPE: TCP\nThen, it examines the system to determine if it is the production or\ntest account. If it is the production account, the post-install is\nfinished. If it is a test account, the TCP/IP ADDRESS (#400.01) and\nDOMAIN (#.03) fields for the VAFHIE entry in the HL LOGICAL LINK (#870)\nfile are removed to ensure that messaging does not occur from a test\naccount.\n \nWhen Installing in Test Account:\n==========================\nBefore installing this patch in your test account, confirm that the\n DOMAIN: FHIE.DOMAIN.EXT\nDEFAULT PROCESSING ID (#.03) field in the HL COMMUNICATION SERVER\nPARAMETERS (#869.3) file is set up properly according to the instructions\nfor the creation of a mirror account. In programmer mode, enter the\nfollowing command.\n \n>W $$PARAM^HLCS2\n45^FO-SLC.DOMAIN.EXT^T^51^ISC SALT LAKE CITY^^3^HL7^25^30^85^30\n \nIf the third piece of the returned data is NOT "T", then the steps for\nmirroring a test account should be reviewed and updated.\n EXCEED RE-TRANSMIT ACTION: restart\n \nInstallation Instructions:\n==========================\nThis patch may be loaded with users on the system. You may wish\nto install it during non-peak hours. Installation will take less\nthan 3 minutes.\n \n1. Use the INSTALL/CHECK MESSAGE option on the Packman menu. [Note: \n TEXT PRINT/DISPLAY option in the PackMan menu will display the \n patch text only.]\n\n
\nTest sites: Greater Los Angeles Regional Healthcare (West Los Angeles),\n \n \nAll HLP array elements are optional; they are not required when these\nAPIs are called. However, it is strongly recommended that the\nHLP("NAMESPACE") array element be defined whenever it is possible to\ndetermine the proper namespace.\n \n \nNote: HL7 messaging by the Master Patient Index (MPI) application occurs\n using the EN^HLCSAC API. The private use of this API by the MPI\n application is covered by Integration Agreement 3471. It is\nThe Health Level 7 (HL7) messages sent and received by sites are being\n important that MPI HL7 messages be assigned the correct namespace,\n and this is done automatically now. There is no need for the\n MPI application to pass their namespace into the EN^HLCSAC API.\n In the future, if this API is opened up to other applications,\n there is a way to override the MPI namespace saved. If the\n local variable HLP("NAMESPACE") is defined before calling the\n EN^HLCSAC API, the value of HLP("NAMESPACE") will be saved in\n the message as the namespace.\n \n \nincreasingly studied for workflow patterns and totals. This evaluation of\nThe first and second lines of the routines included in this patch are\nshown below.\n \nHLCSAS1 ;ISCSF/RWF - Read data ;08/24/99 08:06\n ;;1.6;HEALTH LEVEL SEVEN;**43,57,91**;Jul 17,1995\nHLMA ;AISC/SAW-Message Administration Module ;09/20/2001 12:34\n ;;1.6;HEALTH LEVEL SEVEN;**19,43,58,63,66,82,91**;Oct 13, 1995\nHLMA1 ;AISC/SAW-Message Administration Module (Cont'd) ;04/06/99\n 10:56\n ;;1.6;HEALTH LEVEL SEVEN;**19,43,91**;Oct 13, 1995\nHL7 data by clients of the HL7 package has resulted in the request for HL7\nHLMA2 ;AISC/SAW-Message Administration Module ;09/20/2001 12:35\n ;;1.6;HEALTH LEVEL SEVEN;**19,43,57,58,64,65,76,82,91**;\n Oct 13, 1995\nHLTF0 ;AISC/SAW,JRP - File Data in Message Text File ;\n 05/05/2000 09:01\n ;;1.6;HEALTH LEVEL SEVEN;**12,19,64,91**;Oct 13, 1995\nHLTP1 ;AISC/SAW-Transaction Processor Module (Cont'd) ;04/21/98 09:38\n ;;1.6;HEALTH LEVEL SEVEN;**34,47,91**;Oct 13, 1995\nHLTP4 ;SFIRMFO/RSD - Transaction Processor for TCP ;03/07/2000 17:41\n ;;1.6;HEALTH LEVEL SEVEN;**19,57,59,91**;Oct 13, 1995\ntotals subdivided by the namespace of the message's originating package.\n \nThe VA Kernel checksum for the routine included in this patch\n(calculated using CHECK^XTSUMBLD) is listed below.\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== =====================\n HLCSAS1 1743950 2183617 43,57,91\n HLMA 9200711 9200711 19,43,58,63,66,82,91\n HLMA1 3849338 3849338 19,43,91\nUnfortunately, the namespace of a message is not always determinable.\n HLMA2 8331015 8331015 19,43,57,58,64,65,76,82,91\n HLTF0 3232637 3415603 12,19,64,91\n HLTP1 4286011 4286011 34,47,91\n HLTP4 7964901 7964901 19,57,59,91\n \nSites should use CHECK^XTSUMBLD to verify checksums after patch\ninstallation.\n \nThere are five routines above whose checksums will not change after this\npatch is installed; HLMA, HLMA1, HLMA2, HLTP1, and HLTP4. The only\n \nchanges made to these routines is the addition of comment lines\ndocumenting the new HLP("NAMESPACE") array element. Since comment lines\nare not counted in a routine's checksum, the addition of these comment\nlines do not affect the routine's checksums.\n \nInstallation Instructions:\n==========================\n \n NOTICE: Do not proceed unless patches HL*1.6*47, HL*1.6*57,\n HL*1.6*59, and HL*1.6*82 have been installed.\nThis patch provides a method for HL7 clients to pass their namespace into\n \n 1. Users are allowed to be on the system during the installation.\n \n 2. AXP/DSM SITES: Review your mapped routine set. If the\n routine listed in the ROUTINE SUMMARY section is mapped, it\n should be removed from the mapped set at this time.\n \n 3. Stop all background processes (logical links and incoming\n and outgoing filers) using the 'Filer and Link Management\n Option's 'Stop All Messaging Background Processes [HL STOP ALL]'\nthe HL7 APIs that create messages or acknowledgements. When this is done,\n menu option.\n \n 4. Stop the link manager using the 'TCP Link Manager Start/Stop\n [HL START/STOP LINK MANAGER]' menu option.\n \n 5. AXP/DSM SITES ONLY: Disable all HL7 UCX Services for this\n installation.\n \n 6. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\nthe provided namespace will be stored with the message, enabling\n \n 7. This patch is now loaded into a transport global on your\n system. The next step is to use KIDS to install the Transport\n global. This is done using the 'Installation' menu's 'Install\n Package(s) [XPD INSTALL BUILD]' menu option. When using this\n menu option to install the patch build, you will be asked\n several questions. The questions, and the answers you should\n supply, are shown below.\n \n INSTALL NAME: <HL*1.6*91>\n Grand Junction, Sheridan\nsubsequent totaling by namespace. Additional details of this patch are\n Want KIDS to INHIBIT LOGONS during the install? <NO>\n Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? <NO>\n \n 8. Start all background processes (logical links and incoming\n and outgoing filers) using the Filer and Link Management\n Option's 'Restart/Start All Links and Filers [HL TASK RESTART]'\n menu option.\n \n (Note that links that do not have "autostart" enabled will need\nprovided next.\n to be restarted manually.)\n \n 9. AXP/DSM SITES ONLY: If you previously disabled an HL7 UCX Service\n for this installation, you may enable it now.\n \n 10. AXP/DSM SITES ONLY: After the patch has been installed, rebuild\n your map set, if necessary.\n \n 11. Start the link manager using the 'TCP Link Manager Start/Stop\n [HL START/STOP LINK MANAGER]' menu option.\n \nDETAILS\n \nThere are three supported HL7 APIs by which HL7 messages are created:\n \n - GENERATE^HLMA(HLEID,HLARYTYP,HLFORMAT,.HLRESLT,HLMTIEN,.HLP)\n - GENACK^HLMA1(HLEID,HLMTIENS,HLEIDS,HLARYTYP,HLFORMAT,\n .HLRESLTA,HLMTIENA,.HLP)\n \n - DIRECT^HLMA(HLEID,HLARYTYP,HLFORMAT,.HLRESLT,HLMTIEN,.HLP)\n \nIn all three APIs, the last parameter HLP is passed by reference. Prior\nto calling these APIs, the client package may set HLP array elements and\nthen pass these by reference into the API. An example call using the HLP\narray is shown below.\n \n <tab>S HLP("SECURITY")=1214315\n <tab>D GENERATE^HLMA(HLEID,HLARYTYP,HLFORMAT,.HLRESLT,HLMTIEN,.HLP)\n \nNOIS: None\nThese APIs, including the HLP pass-by-reference array, are documented in\nsection 12.1.2, 12.1.3, and 12.1.4 of the VistA HL7 Site Manager &\nDeveloper Manual.\n \nAfter patch HL*1.6*91 is installed, an additional HLP array element may\nbe defined before calling these APIs by which the namespace of the client\nprocess can be made known to the API code. This additional HLP array\nelement is HLP("NAMESPACE"). An example call using this new array\nelement is shown below.\n \n \n <tab>S HLP("NAMESPACE")="DG"\n <tab>S HLP("SECURITY")=1214315\n <tab>D GENERATE^HLMA(HLEID,HLARYTYP,HLFORMAT,.HLRESLT,HLMTIEN,.HLP)\n \n(The array contained in these three APIs is HLP, and this patch\ndocumentation consistently refers to HLP. However, since this is a\npass-by-reference array, any array name may be selected by the client\nprocess calling these APIs.)\n \nPatch HL*1.6*91 creates a new field in the HL7 Message Text file (#772)\nNote: This patch requires that KIDS builds HL*1.6*47, HL*1.6*57,\nto store the client process namespace when it is passed as described\nabove. This new field's definition is shown below.\n \n'NAMESPACE' FIELD STANDARD DATA DICTIONARY LISTING\n--------------------------------------------------\n772,16 NAMESPACE 0;13 FREE TEXT\n \n INPUT TRANSFORM: K:$L(X)>4!($L(X)<1)!'(X?1U1.3NU) X\n LAST EDITED: FEB 15, 2002\n HELP-PROMPT: Answer must be 1-4 characters in length,\n HL*1.6*59, and HL*1.6*82 be installed.\n and start with 1 uppercase letter,\n followed by up to 3 uppercase letters and\n numerics.\n DESCRIPTION: This field must not be filled in\n manually. It will be filled in\n automatically by the HL7 processes that\n create entries in the HL7 Message Text\n file (#772). In most instances,\n applications will call GENERATE^HLMA,\n GENACK^HLMA, or DIRECT^HLMA. When they\n \n do, they will pass by reference into the\n last OPTIONS (in the documentation)\n parameter the value of the namespace.\n The value of the namespace will be in the\n form of OPTIONS("NAMESPACE")=NAMESPACE.\n \n Please note that the calls to the three\n APIs mentioned above use the variable HLP\n to hold the passed in by reference array.\n So, in the HLMA code (and other code\nOVERVIEW\n invoked by HLMA), the actual variable\n used is HLP("NAMESPACE").\n \n This field is populated by UPDATE^HLTF0.\n \nWhen the client process defines HLP("NAMESPACE") prior to the API call,\nand passes in the HLP array (as shown in the above example), the defined\nnamespace is stored in the HL7 Message Text file (#772) entry created.\nThe code that actually stores HLP("NAMESPACE") in this file is contained\nin UPDATE^HLTF0.\n\n\nRefer to the Forum patch text on patch HL*1.6*85 for patch information.\n\n
\nAssociated Patches: This patch requires that KIDS build HL*1.6*77 be \n ISH-0900-40469 re-transmissions for a message awaiting an ack\n (Note that links that do not have "autostart" enabled will need\n to be restarted manually.)\n \n AXP/DSM SITES ONLY: If you previously disabled an HL7 UCX Service\n for this installation, you may enable it now.\n \n 7. AXP/DSM Sites: After the patch has been installed, rebuild your\n map set, if necessary.\n \n 8. Start Link Manager using the 'TCP Link Manager Start/Stop [HL\n \n START/STOP LINK MANAGER]' menu option. \nThis patch fixes the problem where a TCP client logical link and its \ncorresponding listener logical link lose synchronization. Loss of \nsynchronization creates excessive retransmission of messages and their \nacknowledgements, causing side effects: one is that the client link gets \nstuck in a "Reading" state because its TCP receive buffer fills up; \nanother is that the disk on both the sending and the receiving sides \nfills up at a faster rate.\n \n installed.\nThis patch makes corrections in the way the TCP client logical link \nretransmits a message when its corresponding acknowledgement does not \narrive in time or receives an incorrect acknowledgement. Previous HL7 \ncode allowed the logical link to retransmit a message when the \nacknowledgement message was incorrect, including an "incorrect msg id" \nacknowledgement. This patch corrects the code to allow retransmission of \na message only when the logical link does not receive an acknowledgement \nin time (timed out) and ignores incorrect acknowledgements.\n \nRoutine Information:\n \n=====================\n \nThe following routine is included in this patch. The second line of the \nroutine now looks like this:\n \n;;1.6;HEALTH LEVEL SEVEN;**19,43,49,57,63,64,66,67,76,77,87**;JUL 17,1995.\n \nThe VA Kernel checksums for this routine (calculated using \nCHECK^XTSUMBLD) are listed below:\n \nTest sites: Oklahoma City VAMC, Muskogee VAMC, San Francisco VAMC\n Routine Checksum Checksum \n Name Before Patch After Patch \n ======== ============ =========== \n HLCSTCP2 12129232 12913767 \n \n Patch List\n =====================\n **19,43,49,57,63,64,66,67,76,77,87**;\n \nSites should use CHECK^XTSUMBLD to verify checksums after the patch\n \nhas been installed.\n \nInstallation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation.\n \n 2. AXP/DSM SITES: Review your mapped routine set. If any of the\n routines listed in the ROUTINE SUMMARY section are mapped, they\n should be removed from the mapped set at this time.\nNOIS: OKL-1201-70586 VA* Logical Links not transmitting\n \n 3. Shutdown all Logical Links, incoming and outgoing filers, and\n the Link Manager using the Filer and Link Management options\n listed below:\n \n Stop All Messaging Background Processes [HL STOP ALL]\n TCP Link Manager Start/Stop [HL START/STOP LINK MANAGER]\n \n AXP/DSM SITES ONLY: Disable all HL7 UCX Services for this\n installation.\n ISF-0700-62124 Duplicate Entries for messages\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 5. This patch is now loaded into a transport global on your\n system. The next step is to use KIDS to install the Transport\n global. To do this, use the 'Installation [XPD INSTALLATION \n MENU]' menu. You should use each of the following 'Installation'\n menu options in the order shown below:\n \n SDC-0301-60090 Message stuck in 'Awaiting ACK' status\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n \n When using the 'Install Package(s)' menu option to install \n the patch build, you will be asked several questions. The \n questions asked, and the answers you should supply, are \n shown below.\n ISF-0400-62120 Excessive Retransmissions\n \n INSTALL NAME: <HL*1.6*87>\n Want KIDS to INHIBIT LOGONS during the install? <NO>\n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? <NO>\n \n 6. Start up all Logical Links and incoming and outgoing filers using\n the Filer and Link Management Option's 'Restart/Start All Links\n and Filers [HL TASK RESTART]' menu option.\n \n\n
\nSee patch HL*1.6*95 in the National Patch Module for complete information \non this patch.\n\n
\nSee the full patch description for HL*1.6*94 on the national Forum patch\nmodule system. \n\n
\nSee patch HL*1.6*99 in the National Patch Module for complete information \non this patch.\n\n
\nSee patch HL*1.6*100 in the National Patch Module for complete information\non this patch.\n\n
\nSee patch HL*1.6*88 in the National Patch Module for complete information\non this patch.\n\n
\nThis patch is used to fix the problems described in NOIS calls: \n- catch the erroneous client message entry with illegal message type.\n \nIt will fix the problems for the incoming filer as follows:\n -mock MSA segment error when a batch message is received.\n -missing original outgoing message of the incoming message error.\n -missing Event Type Protocol pointer error.\n \n \nROUTINE INFORMATION \n====================\nHUN-0297-21666, LEX-0297-41531, BAC-0297-40046, IND-0197-42390,\n \nThe following routines are included in this patch. The second line of\n these routines now look like:\n \n <tab>;;1.6;HEALTH LEVEL SEVEN;**Patch List**;Oct 13, 1995\n \n CHECK^XTSUMBLD results\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\nJAC-0297-71674, MAR-0297-20929, etc. The filers erred out abnormally when\n HLCSOUT 3686510 4104234 25\n HLTF1 13439654 9700889 5,8,22,25\n HLTF2 N/A 4516843 25\n HLTP0 3059568 3059585 25\n HLTP01 3988246 3987933 2,25\n HLTPCK1A 10899550 9629334 2,25\n \n \nINSTALLATION INSTRUCTIONS \n=========================\nunexpected data were encountered. This patch will catch these unexpected\n1. Users may remain on the system during the installation of this \n patch. \n2. Shut down all the incoming and outgoing filers by using the \n options: 'Stop all incoming filers' and 'Stop all outgoing filers'\n3. For mapped AXP sites, disable mapping for these routines.\n4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system.\n5. On the KIDS menu, under the 'Installation' menu,\n use the following options:\n \ndata to prevent these errors.\n Print Transport Global \n Compare Transport Global to Current System \n Verify Checksums in Transport Global \n Backup a Transport Global \n \n6. On the KIDS menu, under the 'Installation' menu, use the following \n option: \n Select Installation Option: Install Package(s) \n ================\n Select INSTALL NAME: HL*1.6*25 \n \n =========\n Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols?'. \n7. MSM Sites - Answer 'YES' to the question 'Want to\n MOVE routines to other CPUs?'. \n Then enter the names of your other Compute and Print server(s). \n8. AXP Sites - After the patch has been installed, rebuild your map \n set. \n9. Restart the incoming and outgoing filers.\nIt will fix the problems for the outgoing filer as follows:\n -catch the erroneous client message entry with incorrect Logical Link.\n -catch the erroneous client message entry with parent message missing.\n\n
\nSee patch HL*1.6*98 in the National Patch Module for complete information \non this patch.\n\n
\nSee patch HL*1.6*93 description on Forum for full instructions and \ninformation.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch HL*1.6*101.\n\n
\nSee patch HL*1.6*103 in the National Patch Module for complete information\non this patch.\n\n
\nsee build description in the Patch description section.\n\n
\nPlease see patch HL*1.6*107 description on Forum for full instructions and\ninformation.\n\n
\nSee patch HL*1.6*84 in the National Patch Module for complete information \non this patch.\n\n
\nSee patch HL*1.6*109 in the National Patch Module for complete information\non this patch.\n\n
\nPlease see the patch description in the National Patch Module for a complete\ndescription of this patch.\n\n
\nSee description for patch HL*1.6*108 in the National Patch Module for\ncomplete information on this patch.\n\n
\n \nHL*1.6*26\n 8. Rebuild your mapped set if necessary.\nRecognize 'out-of-order' server protocols\n \nCategory:\n=======\n* Routine\n Enhancement (Mandatory)\n* Data Dictionary\n Sort Template\n \nPrerequisites:\n \nDescription:\n=========\nThis patch enables recognition of HL7 Server Protocols that have been\nplaced out of order as well as those Server Protocols that have no\nclients. This information is returned to the HL7 calling application as an\nerror message while calling the entry point, INIT^HLFNC2. Two new error\nmessages have been added to file 771.7, HL7 ERROR MESSAGE. They are:\n \nCODE: 15 SHORT TEXT: No client\n=========== \nDESCRIPTION: No clients are defined for this server protocol. Unless the\napplication intends to submit a specific client using the HLL("LINKS")\narray, this message should not be sent. \n \n \nCODE: 16 SHORT TEXT: Server Protocol\nDisabled\nDESCRIPTION: The server protocol has been placed OUT OF SERVICE. The\nmessage has been rejected by the HL7 Message Service. The sending\napplication must retain the message for later transmission. \n None\n \n \n \n \n \n \nTest Sites :\n==============\nRequested by CIRN Developers\n \n \nRoutine Summary :\n==============\n <tab ;;1.6;HEALTH LEVEL SEVEN;**2,26**;Oct 13, 1995\n \nRoutine Name Patch List\n----------------- --------------\nHLFNC2 2,26\n \nChecksums:\n=========\n \n Rtn Nm Chksum Before Chksum After \n HLFNC2 5211111 5393929\n \nFROM CHECK^XTSUMBLD \n \n To test if the transport has been corrupted, you can use the \n "Verify Package Integrity" option. This option is under Utilities \n under the KIDS menu. It will compare the checksums in the build \n with the current checksums and list any that differ.\n \nSubject:\n \nInstallation Instructions:\n===================\n \nNOTE any instructions that are different for 486 or Alpha sites.\n \n 1. Users ARE allowed to be on the system during the \n installation. \n 2. You DO NOT need to place TaskMan in a WAIT/STOP state. \n 3. Review your mapped set. If any of the routines listed in the\n======\n Routine Summary section are mapped, they should be removed from\n the mapped set at this time.\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. \n This option will load the KIDS package onto your system. \n 5. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport\n global.\n 6. On the KIDS menu, under the 'Installation' menu, use the\n following options:\n \n \n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global\n Install Package(s) \n INSTALL NAME: HL*1.6*26\n 7. MSM Sites - Answer YES to the question 'Want to MOVE \n routines to other CPUs?'. Enter the names of your Compute and \n Print server(s).\n AXP Sites - Answer NO to this question.\n\n\nPlease see the patch description on Forum, in the National Patch Module.\n\n
\nSee patch HL*1.6*114 in the National Patch Module for complete information\non this patch.\n\n
\nPlease see the patch description on Forum, in the National Patch Module.\n\n
\nPlease see the patch description on Forum, in the National Patch Module.\n\n
\nHL7 parsing utilities.\n\n
\nHL7 2.0\n\n
\nPlease see the NPM on Forum for a complete description.\n\n\n
\n\n\n\n\n
\nMore control over Inbound/Outbound Filer processes\n\n
\nSee the NPM for a complete description of this patch.\n\n\n
\nSee the National Patch Module on Forum.\n\n\n
\nPlease see the National Patch Module for a full description.\n\n\n\n
\nHLO Purge Settings\n\n\n
\nSee the NPM for the description.\n\n\n
\nPatch HL*1.6*138 corrects several minor problems with HL7 OPTIMIZED (HLO)\nand provides several new features.\n\n
\nThis package is a generic implementation the Health Level Seven (HL7)\nprotocol for use by all DHCP applications. The HL7 protocol provides a\nsingle, standard interface between computer systems for the exchange of\nclinical information.\n\n
\nThis patch addresses many problems associated with Electronic Signature in\nsigned online and not allow for 'wet' signatures on the paper chart\n(paperless). 2 or Yes (allow chart signature) is for sites that want all\norders signed online, but also allow for those cases where there might be\na manually signed order in the chart somewhere. This last option is the\nmost likely scenerio for most hospitals at this point in time.\n \nThe printing of new and unsigned orders has been modified. Orders print\n(chart copies, labels, service copies, requisitions) when they are\nreleased. Prior to this patch, they would print again when they were\nsigned. This is no longer the case because of the confusion and potential\nOE/RR 2.5. A new field has been added to the Order Parameters file called\nfor error when duplicate orders are printed.\nElectronic Record. It can be set to 1 of 3 choices:\n 0 for No\n 1 for Yes\n 2 for Yes (allow chart signature)\n \nNo entry or 0 will essentially keep the functionality for Electronic\nSignature the same. 1 or Yes is for sites that want to have all orders\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch OR*2.5*57.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch OR*2.5*61.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch OR*2.5*58.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch OR*2.5*60.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch OR*2.5*62.\n\n
\nThe description of this build can be found in the National Patch Module \nunder the description of patch OR*2.5*64\n\n
\nSee description of build in National Patch Module under the patch OR*2.5*63.\n\n
\nAn optional parameter is added to the formal list of the subroutine\n D PATIENT^ORU1(.ORPAT,1) ; Will suppress initial page feed\n \nwhereas,\n \n D PATIENT^ORU1(.ORPAT) ; Will allow initial page feed/no side-\n ; effect (this is how the subroutine was\n ; uniformly called by v2.5\nPATIENT^ORU1, which will suppress the initial page feed issued by the\nlook-up, prior to presenting the list of patients from which the user may\nselect. Because the parameter is optional, and must be set to 1 by the\ncalling application to affect the look-up, the change is backward\ncompatible, and without side-effects.\n \nAnnotated example of use:\n \n\n
\nThe description of this build can be found in the National Patch Module \nunder patch OR*2.5*54.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch OR*2.5*55.\n\n
\nThe description of this build can be found in the National Patch Module \nunder patch OR*2.5*56.\n\n
\nThe description of this build can be found in the National Patch Module\nunder patch OR*2.5*59.\n\n
\nThis patch corrects OPENERR errors which occur in DEL^%ZISH when no data\nis returned for a CPRS report.\n\n
\nThis patch will add the edit/resubmit consults option to the\nlist manager.\n \nPlease see the patch module on FORUM for a complete description\nof this patch. In addition, you may want to review consult\npatches GMRC*3*15 and GMRC*3*18, which are also required to see\nthe entire functionality.\n\n
\nThe description for this patch can be found in the National Patch Module\nunder OR*3*113.\n\n
\nYou can see the description of this build in the National Patch Tracking \nmodule under patch number OR*3*115.\n\n
\nThis build includes the GUI specific portions of CPRS that were pulled\nout of the OR3.0 build.\n \nRoutines: ORW* \nOR*\nOption: OR CPRS GUI CHART\n \nalso TIUSRVP and TIUEDIT\n\n
\nPatch OR*3*95 updates a number of menu editor and related items. Please\nsee the FORUM patch description for a complete description of all of the\nchanges included in this patch.\n\n
\nThis is the updated version of the performance monitor. Please see the\nFORUM patch description for complete details regarding this patch.\n\n
\nThis is the updated version of the performance monitor. Please see the\nFORUM patch description for complete details regarding this patch.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis patch corrects a problem of getting a Null Subscript error when\nprinting orders that have no order text.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nPlease see FORUM patch description for a complete analysis of this patch.\n\n
\nRefer to the patch description on the patch message.\n\n
\nPlease see the full patch description on the FORUM account for this patch.\n\n
\nSee National Patch Module.\n\n
\nDatabase clean up for POE related issues. Please see FORUM for complete \npatch details.\n\n
\nSee FORUM for the full description of this patch. Update to database \nclean up distributed in patch OR*3*138.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to description on the patch message.\nprinting orders that have no order text.\n\n
\nBCMA ORDER COM V1.1\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis patch includes a API EN^ORBCMA2 required by BCMA V2. The #DBIA for \nthis API is 3616.\n\n
\nThis patch is being released to turn off the spell checking functionality \nbased on input from the National Center for Patient Safety.\n\n
\nThis patch is in support of the Hui/VHA CIO SD&D Pharmacy Data Interchange\nproject. The project provides a method for the one-way electronic transfer\nof prescription orders from an external system to VistA.\n\n
\nFixes problem with November dates being interpreted as "NOW". Please see \npatch description on FORUM for complete details.\n\n
\nUpdate to post-install for patch OR*3*158. Please see FORUM patch module \nfor full details.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThe description of this build is found in the National Patch Module under \npatch OR*3.0*159.\n\n
\nThe description of this build is found in the National Patch Module under \npatch OR*3.0*171.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nUpdates to Event Delayed Order code.\nSee FORUM patch description for complete details.\n\n
\nRefer to the patch description on the patch message.\n\n
\nDescription:\nThe following is a list of the routine(s) included in this patch. The\nsecond line of each of these routine(s) will look like:\n \n<tab>;;3.0;ORDER ENTRY/RESULTS REPORTING;**<patch list>**;Dec 17, 1997\n \n CHECK^XTSUMBLD results\n Routine name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n ORMGMRC 12946666 3,26,68,92,153\n ORMLR 15500365 3,92,153\n===========\n ORMRA 16479106 3,53,92,110,136,153\n ORQRY 10982388 153\n \nInstallation Instructions:\n==========================\n \nInstallation of this patch will take less than 2 minutes. Although\nusers need not be off the system when applying this patch, it should be\ninstalled at a nonpeak time to minimize disruption to users.\n \n \n 1. Use the INSTALL/CHECK MESSAGE option on the Packman Menu, to \n load the KIDS Transport Distribution global. \n \n 2. Review your mapped set. If any of the routines listed in the \n ROUTINE SUMMARY section are mapped, they should be removed \n from the mapped set at this time. \n \n 3. From the Kernel Installation and Distribution System (KIDS) Menu, \n select the Installation menu. \n \nThis patch provides server side updates for the CPRS Query Tool. This\n 4. From the installation menu, you may elect to use the following \n options (when prompted for INSTALL NAME, enter OR*3.0*153): \n \n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 5. Use the Install Package(s) option and select the package \n OR*3.0*153.\n \ntool allows queries to be created for Orders, Documents, Appointments,\n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n YES//', respond 'NO'.\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? YES//', respond 'YES', and disable\n OR* Options and Protocols.\n \n 8. If routines were unmapped as part of step 2, they should \n be returned to the mapped set once the installation has \n run to completion.\nand Visits.\n \nROUTINE SUMMARY:\n================\n\n
\nCRSP CMOP FIX\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRemove Race and Ethinicity codes\n\n
\nSee National Patch Module (NPM) on FORUM.\n\n
\nFixes problem with allergy orders that didn't pass correctly from CPRS. \nSee the full description on FORUM.\n\n
\nUpdate to performance monitor for pharmacy transitional benefits \nprogram. Please see FORUM for a complete description.\n\n
\nEmergency patch / GUI 22.12 to fix problems with GUI 22.11 / patch \nOR*3*173.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the FORUM description for a complete review of the changes \nincorporated in this patch.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nSee description on patch message.\n\n
\nEmergency Patch to reduce number of calls to RPC "ORWPT ID INFO." Also \nincludes fix for slow TIU Template loading.\n\n
\nThe description of this build is found in the National Patch Module under\npatch OR*3*174.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nNote: This patch can only be installed at sites running CPRS.\n \nThe entry point to do medication order checks for drug-drug interactions,\nduplicate drug orders and duplicate drug class orders was changed from\n^PSOORDRG to EN^PSOORDRG. This patch changes references in routine ORKPS\nto the new entry point EN^PSOORDRG.\n\n
\nSee NPM on Forum for description.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nGroup Notes\n\n
\nUpdate to performance monitor to exclude Non-VA med entries.\n\n
\nImplement Clinical Reminders index.\n\n
\nThis patch corrects a problem of getting a Null Subscript error when\nprinting orders that have no order text.\n\n
\nSee the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nPatch Description:\nmatching source record. To address this issue a utility has been written \nOREORV2 N/A 8511634 217\n \nInstallation Instructions:\n==========================\nThis patch should be loaded during non-peak hours to minimize disruption \nto users. Installation should take less than 2 minutes. Users are allowed \nto be on the system during the installation. TaskMan does not need to be \nstopped.\n \n1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\nthat will perform an analysis of the ORDERABLE ITEM FILE, file # 101.43, \n \n2. From the Kernel Installation and Distribution System Menu, select the \nInstallation menu.\n \n3. From this menu, you may elect to use the following options (when \nprompted for INSTALL NAME, enter OR*3.0*217):\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \nand produce a detailed report of its findings. This utility will scan the \n4. Use the Install Package(s) options and select the package OR*3.0*217.\n \n5. When prompted 'Want KIDS to INHIBIT LOGONS during install? YES//', \nrespond "NO".\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options and \nProtocols? YES//', respond "NO".\nthe ORDERABLE ITEM FILE record by record. This utility determines the \nfollowing about the current ORDBERABLE ITEM FILE record being processed:\n \n1. Is the ID field null?\n \n2. Is the source record IEN stored in the ID field null?\n \n==================\n3. Is the source record package code stored in the ID field null?\n \n4. Is the data stored in the ID field properly formatted?\n \n5. Is the source record package code part of the current interface \nspecification?\n \n6. Is there a matching source record?\n \n7. Is it currently flagged as active?\nThis patch provides a utility, consisting of a set of three routines, to \n \nA temporary global is build tracking all of the above for a detailed \nreport. Only an ORDERABLE ITEM FILE record passing all tests is modified.\nAt this point it will be flagged as inactive effective immediately. After\nthe utility has printed its report the temporary global created by this\nutility is deleted. The utility is to be run at any time the null\nsubscript error is encountered during the ordering process.\n \nIt is these invalid orderable items with no matching source records that \nare generating the NULLSUBSCR errors described in the associated NOIS \nfind records in the ORDERABLE ITEM FILE # 101.43 which do not have \ncases. The flagging of records in the ORDERABLE ITEM FILE # 101.43 \nwithout matching source records as inactive will prevent CPRS GUI from \npresenting them to the user as valid orderable items. The routines in \nthis patch can be run anytime a selected orderable item generates the \nNULLSUBSCR error.\n \nAssociated NOIS:\n================\n1. ALB-1001-51034 - UNDEF VAR LOAD+6~ORWDLR32\n2. DAN-0204-42157 - Error on Order of Lab Test\nmatching records in their source files. It will flag any active Orderable \n3. NJH-0402-20607 - Receiving error message in CPRS\n4. SBY-0803-30443 - LOAD+4~ORWDLR32:1,%DSM-E-NULLSUBSCR\n \nOPTIONS\n=======\n \nCPRS Clean-up Utilities menu (ORE MGR, a menu option) was modified. A new \noption was added to it.\n \nOrderable Items Records Validation (ORE ORDERABLE ITEMS VALIDATION, a run \nItem record without a matching source record as inactive and print a \nroutine option) was created. It has been added to the CPRS Clean-up \nUtilities menu.\n \nThe menu path to the new option is:\n CPRS Manger Menu\n CPRS Configuration (IRM) - IR\n CPRS Clean-up Utilities - UT\n Orderable Items Records Validation - OI\n \nHOW TO RUN THE UTILITY:\ndetailed report of its findings.\n=======================\n \n1. Enter the "CPRS Manager Menu".\n \n2. Select the "CPRS Configuration (IRM)" option.\n \n3. Select the "CPRS Clean-up Utilities" option.\n \n4. Select the "Orderable Items Records Validation" option.\n \n \n5. The user will be presented with a screen with a brief description of \nthe option's functionality. At the "Do you wish to run this program? \nEnter Yes or No?" prompt enter Y for yes. Entering N for No will return \nthe user to the menu.\n \n6. The user will be prompted for a device for the utilities output. The \noutput can be sent to the terminal screen. A printer for hard copy can be \nselected. This is recommended. It can be queued to the Kernel Spool and \nset to run at a preferred later time. \n \nThe issue is an active orderable item record that does not have a \nROUTINE SUMMARY:\n================\nThe following routines are included in this patch. The second line of \neach of these routines now looks like:\n ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997\n \nRoutine name Before Patch After Patch Patch List\n============ ============ =========== ==========\nOREORV N/A 4346077 217\nOREORV1 N/A 3985270 217\n\n
\nCPRS M-side changes in support of removing allergies as\norders. Please see the forum module for a complete description\nof this patch.\n\n
\nThis patch will make the CPRS-ARTS interface compatible with the re-design\nof the National Drug File.\n\n
\nSupport for allergy data standardization updates that are needed\nin the CPRS package. Please see FORUM for a complete description.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis the OR part of a multi package patch to add Additional IV Drug Units\n- MG-PE & NANOGRAM the primary patch will be in PSJ*5.0*152.\n\n
\nCORRECT THE FILING OF THE PATIENT NAME IN THE AUTO LINKED LIST PROCESS. \n\n
\nCPRS GUI 26\n\n
\nRefer to the patch description on the patch message.\n\n
\nUPDATING ORWRP TIME/OCC LIMITS ALL PARAMETER\n\n
\n This patch fixes an incorrect Web address for activating VistaWeb from\n CPRS. The parameter: ORWRP VISTAWEB ADDRESS is changed to:\n "https://vistaweb.domain.ext/ToolsPage.aspx"\n\n
\nFIX UNSIGNED ORDERS NOT GENERATING ALERTS.\nMORE USEFUL NUMERIC PROMPT ERROR MESSAGES\nFIX RESTRICTED PATIENT LIST SCROLLING BUG.\n\n
\nThis patch is part of the Patient Financial Services System (PFSS) \nbilling replacement system, business process improvements, and \nenhancements to Veterans Health Information Systems and Technology \nArchitecture (VistA) to support integration with the COTS billing \nreplacement system. Significant changes to VistA legacy systems and \nancillary packages are necessary.\n \nSome of the PFSS software components are not operational until the PFSS \nOn/Off Switch, distributed with patch IB*2*260, is set to "ON . The \nability for the local site to set the switch to "ON will be provided at \nthe appropriate time with the release of a subsequent Integrated Billing \nproject. PFSS patches are being released on various schedules. Some \npatch.\n \nFor more information about the PFSS project, review the documentation \naccompanying this patch and refer to the following website: \nhttp://vista.domain.ext/billreplace/\n \nThe OR*3.0*228 patch is phase II of the CPRS portion of the PFSS \nproject. Phase I of the CPRS portion of the project is contained in \nOR*3.0*215.\npatch functionality will not be active until a new PFSS switch is \nactivated during final implementation. PFSS will initially be implemented \nat select pilot sites ONLY.\n \nThe purpose of the PFSS project is to prepare the VistA environment for \nthe implementation of a commercial off-the-shelf (COTS) billing \nreplacement system. The project consists of the implementation of the \n\n
\nCorrects problem with CIDC assign parameter and disable for all providers.\n\n
\nThis patch addresses two issues, First orderable items not turning off\nReminders. Second the DEA# and VA# fields are not being check, when\nnarcotics are ordered with the outpatient IV dialog in CPRS.\n\n
\nThis patch addresses problems with:\n-The LAB Quick Orders not displaying (CH) LAB Quick Orders.\n-Expert System VITALS^ORQQVI not finding all vital measurements.\n-Display Patient Alerts and Alert Recipients, display truncating Order \n number. \n\n
\nTHIS PATCH ADDRESSES A PROBLEM WITH THE PROBLEM LIST LEX SEARCH AND ADDS \nTHE WOR DRUG TO THE ORDER CHECK DUPLICATE DRUG CHECK WARNING.\n\n
\nThis patch contains the routine ORY244 which will scan Order file #100 \nfor missing abnormal results, from Fileman date 3050901 to present and \nrestore them. \n\n
\nCPRS Miscelaneous fixes.\n\n
\nThis patch corrects an error that was causing IV orders to only be \nvalid for 6 minutes after the time the order was placed.\n\n
\nRefer to the patch description on the patch message.\n\n
\nAdds option for editing quick orders by user. Fixes bugs when editing \nquick orders.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis build/patch address 3 issues:\n5. The correct IEN for pointer for Imaging is\nchecked and update if needed by the post init routine ORY26508.\n6. Modify SESSION^ORCHECK to also check the ADVERSE REACTION ASSESSMENT \n(120.86) for allergies before assuming the error message stored at \n^OR(100,+ORIFN,9 is up to date and displaying the "no allergy assessment" \nerror again upon signing the order.\n7. If they comment is the same, set the ORDIALOG flag \n"FORMAT" to "@" to prevent the duplication of the comment in CPRS.\n8. Modify MEDHIST^ORWPS to set ORPHMID regardless if the flag CKPKG for \nPSB*2.0*19 is set. Use ORPHMID in the call to HISTORY^PSBMLHS instead\n1. "AW" Cross Reference on TO field of File 100 not updated when order \nof ORPSID.\nchanges.\n2. Lab Threshold exceeded warning not working when results has a greater \nthan or less than symbol. Example: <5 or >5\n3. Quick Orders not retaining Dosage when edited and dose is over 20 \ncharacters.\n4.Update the routine ORB3TIM2 to work the alert even when not passed in \nORBLST (expired).\n\n
\nCorrect CPRS RPC used by CAPRI, that was trying to return future \nappointments.\n\n
\nThis patch corrects the issue introduced in OR*3.0*265 where pending \norders no longer display the Medication Administration History.It also \naddresses a subscript error and a disk full error from ORWPS1\n\n
\n \nthe start date.\n \n3. Creating a new menu by copying an existing menu is resulting in an \nerror.\n \n4. If a patient has only clinical procedures reports in the Procedures \n(local only) section of the CPRS reports tab, the reports will not print \nto a printer.\nThis patch will address a few issues:\n1. When using the Search orders by nature or status option, if the user \nentere a start date of T-1 and an end date of T, the search will return \nno results.\n \n2. In the option 'Search orders by nature or status', the help text for\nthe date ranges state that the start date must be older than the end\ndate. But the option will allow the user to enter an end date older than\n\n
\nCorrects the issue with Tasks accumulating while waiting for a \npartition. Caused by ORMEVNT exiting without unlocking a global that it \nlocked. \n\n
\nCPRS GUI 26\n\n
\nRefer to the patch description on the patch message.\n\n
\nThe purpose of this patch is to address an issue that has been reported \n \n Problem:\n --------\n The problem deals with the display of the order information for \n Outpatient prescriptions once the order has been accepted in CPRS.\n \n The drug name is missing from the order text in the display. The \n problem was traced back to \n \n Resolution:\nwith the drug name missing from pending orders.\n -----------\n OR*2.5*49 released a menu option that performs a conversion on\n the ORDER DIALOG (#101.41) file. The [ORCM CONVERT MENUS] option is\n being removed.\n \nOverview:\n=========\n1. HD199896 Drug name missing from Pending Orders\n HD154624 duplicate\n HD157144 duplicate\n HD163806 duplicate\n\n
\n \nSee patch OR*3*37 in the National Patch Module for description on this\nbuild.\n\n
\nUPDATE ORDER DOSAGE WITH NEW FORMAT\n\n
\n1. A problem was discovered with the Results Reporting [OR RESULTS\nmay need some text moved to "Reason for Study". Since "Reason for Study"\n --------\n Radiology and Imaging quick orders may need to be updated as a result\n of the changes in OR*3*243.\n \n Resolution:\n -----------\n A new option will be provided, Radiology/Imaging Quick Order Search\n [ORCM RA SEARCH]. This option will search for Radiology and Imaging\n quick orders that have free text fields that contain text. A sample\n message and additional details are included below the 'Important \nhas a size limit of 64 characters changes must be made by a person who can\n Notes' section.\n \n3. HD0000000232271 Need routine to identify Radiology QOs with default\n date\n \n Problem:\n --------\n Radiology and Imaging quick orders should no longer contain a default\n of TODAY for Date Desired. Sites need assistance in locating and \n updating the quick orders that need to be updated.\nreview what, if any, portion of the text should be moved into the new\n \n Resolution:\n -----------\n The search option for item 2 includes a search for quick orders that\n contain either 'T' or 'TODAY' for the Date Desired prompt. In addition,\n the option will remove the Date Desired default as requested by the\n user. A sample message and additional details are included below.\n \n***Important Notes*** \nIf you identify quick orders that need to be updated, you must wait \nfield. This patch will allow sites to produce a list of existing quick\nuntil after the installation of OR*3*243 to make these updates. Use the\nEnter/edit quick orders [ORCM QUICK ORDERS] option to update the quick \norders, where appropriate. It may also be necessary for providers to edit\ntheir personal quick orders.\n \nEven disabled quick orders will be shown, for review purposes. The results\nwill be sent as a mail message to the person who ran the option. Please\nnote, it may be necessary for this menu option to be assigned to the\nperson responsible for the review (i.e. Clinical Coordinator and/or\nRadiology ADPAC).\norders that should be reviewed. HD0000000217362\n \nThe following shows a sample message. It is difficult to read since it is \nformatted to print 132 characters. In the column for "Text or Start \nDate/Time", there will be a "T" or "D" to indicate "Text" or "Date".\n \nSelect OPTION NAME: ORCM RA SEARCH RADIOLOGY/IMAGING QUICK ORDER\nSEARCH\nRADIOLOGY/IMAGING QUICK ORDER SEARCH\nClear Date Desired with a response of "TODAY"? Y\nExclude quick orders with STAT urgency? Y\n \n \nRequested Start Time: NOW// (NOV 19, 2007@11:36:42)\n \nThe check of Radiology/Imaging Quick Orders is queued\n (to start NOW).\n \nYOU WILL RECEIVE A MAILMAN MESSAGE WHEN TASK #154113 HAS COMPLETED.\n \nSample mail message:\nSubj: RADIOLOGY/IMAGING QUICK ORDERS [#668609] 04/15/08@20:39 592 lines \n3. There should no longer be a default of 'TODAY' for "Date Desired" on a \nFrom: CPRS, SEARCH In 'IN' basket. Page 1\n--------------------------------------------------------------------------\n The check of Radiology/Imaging Quick Orders is complete.\n \n Here is the list of all quick orders that should be reviewed: \n \nQuick Order Name Disable Text Text or Start \nDate/Time\n Ancestors/Menus or Reminders\n \nRadiology quick order. Some sites have requested the ability to\nRAGR CHEST 2 VIEWS PA&LAT STAT QO D: TODAY\n On a menu or in an order set\n T: POST OP SURGERY\n \nRAGR CHEST 2 VIEW DISABLED T: TEST\n \nORWDQ E87030CE no longer used T: TESTING\n \nORWDQ 3A173B44 T: h/o high grade \nfever\nautomatically remove 'TODAY' from the "Date Desired" prompt. In addition,\n \nEnd sample mail message\nthere was a request to be able to exclude quick orders with an order\nREPORTING] menu after the installation of GMTS*2.7*85. This patch corrects\nurgency of 'STAT'. HD0000000232271\n \nAssociated Remedy:\n==================\n1. HD0000000241916 GMTS *85 Problem\n2. HD0000000217362 Need routine to identify potential quick order problems\n3. HD0000000232271 Need routine to identify Radiology QOs with default\n date \n \nAssociated NSR(s):\nthis problem. HD0000000241916\n==================\nN/A\n \nTest Sites:\n===========\nTBD \n \nOverview:\n=========\n1. HD0000000241916 GMTS *85 Problem\n \n \n Problem:\n --------\n After a site installed GMTS*2.7*85, they discovered an error would\n occur if they used the Results Reporting Menu [OR RESULTS REPORTING]\n option to display Health Summary results. It was discovered that the\n variable XQORNOD was being set by the Order Entry Results Reporting\n package incorrectly, with only one piece, and this was causing a\n <SYNTAX>OP+3^XQCHK error to appear.\n \n2. OR*3*243 will add a "Reason for Study" prompt to the Computerized \n Example:\n --------\nSelect OPTION NAME: OR RESULTS REPORTING Results Reporting Menu\nResults Reporting Menu\n \nSelect Patient: GMTS,TEST PATIENT DOB ######### \n \n \n \n R E S U L T S R E P O R T I N G \nPatient Record System (CPRS) Graphical User Interface (GUI) "Order an\nGMTS,TEST PATIENT ###-##-#### DOB (AGE) Wt (lb): NF\n-------------------------------------------------------------------------\n --- Main Results Menu ---\n \n1 Health Summary 8 Daily Order Summary\n2 Lab Results (Interim) 9 Order Summary for Date/time Range\n3 Graph Lab Tests 10 Customized Order Summary\n4 Blood Bank Report 11 Print Chart Copy Summary\n5 Anatomic Pathology Report 12 Outpatient RX Profile\n6 Vitals SF511 Report \nImaging Procedure" dialog. The "Reason for Study" requirement was\n7 Vitals Cumulative Report Ad Hoc Health Summary\n \nSelect Item(s): 1 Health Summary \n \n --- Health Summary ---\nSelect Health Summary Type: CLINICAL REMINDERS// <<<Can choose any \nHealth\n Summary Type\nDEVICE: HOME// TELNET TERMINAL\n \nimplemented in the Radiology package with RA*5.0*75. Existing Radiology\n 04/22/2008 \n11:58\n*************** CONFIDENTIAL CLINICAL REMINDERS SUMMARY \n*****************\nI $D(XQORNOD) S \n%XQ=+XQORNOD,%XQ1=U_$P(XQORNOD,";",2),%XQ=@(%XQ1_%XQ_",0)"),\n ^\nXQOPT=$P(%XQ,U)_U_$P(%XQ,U,2)\n<SYNTAX>OP+3^XQCHK\n \nand Imaging quick orders that have text in "History and Reason for Exam"\n Resolution:\n -----------\n Routine ORPRS07 has been modified to properly set two pieces into\n XQORNOD and thus not generate the error when displaying Health Summary\n results when using the Results Reporting Menu [OR RESULTS REPORTING]\n option.\n \n2. HD0000000217362 Need routine to identify potential quick order problems\n \n Problem:\n\n
\n1. For very lengthy patient instructions, there is the possibility that\nThe report will contain the orderable item name, dispense drug name, \nprescription number and the internal entry number (IEN) of the entry from \nthe ORDERS file (#100) as well as other information about the patient and \norder. Below is a sample output for the report:\n \nSubj: TRUNCATED PATIENT INSTRUCTIONS [#660505] 02/28/08@23:43 7 lines\nFrom: CPRS, SEARCH In 'IN' basket. Page 1 *New*\n--------------------------------------------------------------------------\n The check for truncated Patient Instructions is complete.\n \nthey can be truncated when transferred from Outpatient Pharmacy V. 7.0 to\n Here is the list of the affected orders: \n \nPatient/Division SSN Item/Dispense Status/RX# Stop/OIEN\nCPRSPATIENT,GENERAL 1234 ACETAZOLAMIDE TAB ACTIVE 09/24/2008\nDAYTON ACETAZOLAMIDE 250MG 2666845 12608385\n \nIn addition to reporting the orders, this routine will also correct the \ninformation in the ORDERS file (#100). It is important to check these \norders and verify the corrected information is accurate.\n \nOrder Entry/Results Reporting V. 3.0. Patch OR*3.0*243 corrects the\nAssociated Remedy:\n==================\n1. HD0000000236377 Patient instructions are truncated\n \nAssociated NSR(s):\n==================\nN/A\n \nTest Sites:\n===========\nproblem with the truncation. However, there is no way to identify orders\nTBD \n \nOverview:\n=========\n1. HD0000000236377 Patient instructions are truncated\n \n Problem:\n --------\n For very lengthy patient instructions, there is the possibility that \n they can be truncated when transferred from Outpatient Pharmacy V. 7.0\nthat need to be corrected. This patch corrects this problem by creating a \n to Order Entry/Results Reporting V. 3.0. Patch OR*3.0*243 corrects the\n problem with the truncation. However, there is no way to identify \n orders that need to be corrected.\n \n Resolution:\n -----------\n Routine ORY299 will execute as a post-install routine. It will search\n through the last 365 days of Outpatient prescriptions, comparing\n patient instructions. A report will be sent to the person who installed\n the patch. In addition, the routine will use the patient instructions\nroutine to search through the previous 365 days of Outpatient \n from Pharmacy to correct truncated patient instructions.\nprescriptions, comparing patient instructions. A report will be sent to \nthe person who installs the patch. It will be sorted by division.\n \n\n
\nThe description of this patch may be found in the National Patch Module \nunder OR*3.0*301.\n\n
\n1. A site reported a problem with accessing a patient's records afte r\n \nAssociated Remedy:\n==================\n1. HD0000000223856 Intermittent Error message when signing lab orders.\n2. HD0000000069676 help description no longer true\n \nAssociated NSR(s):\n==================\nN/A\n \ntheir system was co-located. A problem was discovered with the length of\nTest Sites:\n===========\n \nOverview:\n=========\n1. HD0000000223856 Intermittent Error message when signing lab orders.\n \n Problem:\n --------\n The problem has to do with errors occasionally showing up when\nthe lock timeouts. This patch corrects this problem by modifying the locks\n attempting to sign orders. However, the message detail shows no name\n for the person who is working on the order.\n \n Resolution:\n -----------\n The lock timeouts in routine ORX2 have been updated to use the new\n system parameter.\n \n2. HD0000000069676 help description no longer true\n \nto use the system parameter for timeouts, if available. HD0000000223856\n Problem:\n --------\n The problem has to do with the description associated with the OR\n OREMAS MED ORDERS parameter. The description does not indicate that\n this parameters only affects Inpatient Medications orders.\n \n Resolution:\n -----------\n The DESCRIPTION field (#8989.512) of the PARAMETER DEFINITION file\n (#8989.51) was updated to accurately reflect what orders are covered by\n \n this paramter.\n2. A site reported an issue with the help text/description associated with\nthe parameter OR OREMAS MED ORDERS. The description for this parameter\ndoes not make it clear that it only affects Inpatient Medications orders. \nHD0000000069676\n\n
\nCurrently, the Computerized Patient Record System (CPRS) V. 1.0 uses the\n \nA new software package, Clinical Observations, will also collect patient\nvital signs but store the records in a different file. However, both GEN.\nMED. REC. - VITALS V. 5.0 and the new Clinical Observations package will\nupdate the Clinical Reminders Index global, specifically, the 120.5\nsection. This patch ensures that vitals information, regardless of its'\nsource will continue to display appropriately on the CPRS cover sheet.\n \nAssociated Remedy:\n==================\nGMRV VITAL MEASUREMENT file (#120.5) to retrieve vitals information to\nHD 222625 CPRS Vitals API\n \nAssociated NSR(s):\n==================\nN/A\n \nTest Sites:\n===========\nTBD \n \ndisplay on the Cover Sheet.\nOverview:\n=========\n1. HD222625 CPRS Vitals API\n \n Problem:\n --------\n Vitals information will no longer be stored in file 120.5. CPRS must\n retrieve data using the Clinical Reminders Index global.\n \n Resolution:\n \n -----------\n CPRS access to retrieve vitals information will now be retrieved using\n the Clinical Reminders Index global and the Application Programming\n Interface (API) provided by the GEN. MED. REC. - VITALS V. 5.0 package.\nThe purpose of this patch is to modify the retrieval of vitals \ninformation to use the Clinical Reminders Index global in conjunction \nwith a standard Application Program Interface supplied by the GEN. MED. \nREC. - VITALS V. 5.0 package. No functional changes are included, only the\naccess method.\n\n
\n1. When an Outpatient complex prescription contains an EXCEPT conjunction \ncorrects this problem by prompting for 'Give additional dose NOW' if the \nschedule does not have a schedule type of 'ONE-TIME'. \nHD0000000277913, PSPO #1140\nthere is a problem when it is transferred to Inpatient Medications. The \nnew order created does not adequately reflect the provider's intent. This \npatch corrects this problem by no longer allowing an Outpatient complex \norder with a conjunction of 'EXCEPT' to be transferred to Inpatient. \nHD0000000269669, PSPO #1031\n \n2. With the release of OR*3*243, there is no longer a 'Give additional \ndose NOW' prompt in the [ORCM QUICK ORDERS] menu option. This patch \n\n
\n1. A site reported that the parameter ORQQLR DATE RANGE INPT does not\nand time of the parent order. when an inpatient is selected. \nHD0000000069365, HD0000000069851\n \n3. When entering a continuous lab order, with a response to 'How Long?'\nthat exceeds one day, the stop date is displaying incorrectly. The change\nin item #2 for ORCSEND1 corrects this issue, as well, The collection date\nand time of the last child order created will be used as the stop date and\ntime of the parent order. HD0000000070009\n \n4. A provider accidentally selected both a parent lab order as well as\nhonor the value at the location level. Routine ORWCV has been modified to\nmultiple child orders and then chose the action of 'discontinue'. Upon \nsignature, an error box displayed indicating the order had already been\nsigned. Two changes have been made to address this issue. \n \nFirst, lab orders will no longer display the parent order. Only the child\norders will be displayed once the parent order is signed and released to\nservice. Routine ORCSEND1 has been modified to 'veil' the parent order\nonce the child orders are all created.\n \nSecond, routine ORQ2 was modified to include the parent's stop date and\ninclude the patient's location when an inpatient is selected. \ntime in the detail display of the child order. This refers to the detail\ndisplay from the Orders tab. HD0000000070670\n \n5. When troubleshooting an alert problem, it appears that the child orders\nfor a lab order do not show all the needed information. Routine ORCSEND3\nwas modified to treat child orders exactly as parent orders or a single\nlab order. All the available information, such as signature, order checks,\netc. will now be found in the detailed display of each child order.\nHD0000000069279\n \n2. When entering continuous lab orders with schedules that have a 'once\ndaily' frequency, a response to 'How Long?' of n or xn should calculate\nthe same stop date/time. Routine ORCSEND1 has been modified to use the\ncollection date and time of the last child order created as the stop date\n\n
\nThis patch implements the interface between CPRS and VBECS, installing\na new order dialog and other supporting components. CPRS and VBECS are\nboth required to install this patch.\n\n
\nRefer to the patch description on the patch message.\n\n
\n1. A site reported a problem with duplicate orders in Inpatient\nthe ORWDX routine.\n \n4. During unit testing of the changes for the problem of duplicate \norders, an issue was found with locking of patient events. When multiple \norders for the same event are manually released, a lock on the patient \nevent remains after the process is completed.\n \n \nOverview:\n=========\nMedications V. 5.0. If there were delayed-event orders manually released\n1. HD0000000199004 Discontinued order not showing in CPRS\n HD0000000069901 duplicate\n HD0000000070256 duplicate\n HD0000000092874 duplicate\n HD0000000165137 duplicate\n HD0000000174026 duplicate\n HD0000000280582 duplicate\n HD0000000300668 duplicate\n \n Problem:\nat the same time that the associated event occurred, duplicate orders were\n --------\n A series of delayed orders for Inpatient Medications was written. The \n orders were released to the service manually from the Computerized \n Patient Record System (CPRS) GUI at the same time the associated\n patient movement was performed. This resulted in some of the orders\n being duplicated in Inpatient Medications.\n \n Resolution:\n -----------\n The locking logic in the release process has been modified to handle \nsent to the service. PSI-07-128\n this situation. If the movement and manual release begin at the same \n time, only one will be allowed to process the orders. Routine ORWDX \n was modified to handle this.\n \n In addition to the locking issue that was identified, there was a \n check added to ORWDX to ensure that the order had not already been \n released by a movement if the user selected manual release. This check \n already existed in the movement routine.\n \n2. HD0000000281619 Delayed Radiology orders discontinuing on release\n \n HD0000000284481 duplicate\n \n Problem:\n --------\n Delayed Radiology orders were being rejected by Radiology upon manual \n release. The error message was 'missing/invalid location'.\n \n Resolution:\n -----------\n Routine ORWDX has been modified to record the location and treating \n2. Two of the test sites reported a problem regarding the change in item \n specialty for an order after the lock is successful, but before \n transmitting the order to the service.\n \n3. HD0000000298397 Intermittent ORWDX errors\n \n Problem:\n --------\n Under certain conditions, an error occurs in ORWDX when attempting to\n build the error message back to the user.\n \n#1 adversely affecting delayed Radiology orders.\n Resolution:\n -----------\n Routine ORWDX has been modified to ensure the error message array\n contains all the appropriate information so that no error will occur\n when the patient event is locked.\n \n4. HD0000000307535 Manual release of delayed orders could leave event \n lock\n \n Problem:\n \n --------\n When manually releasing more than one delayed order for a single \n patient event, the event can remain locked once the process finishes.\n Specifically, ^ORE(100.2,event number,0) will remain locked.\n \n The problem is that routine ORWDX issues an incremental lock for the \n patient event associated with each order that is being released.\n However, when the process completes, a single 'unlock' is issued. For \n example: three orders, associate with event number 9573 are manually \n released. When the process completes, the following entry remains in\n3. Two test sites reported a problem of receiving intermittent errors in \n the lock table:\n 38) 20E5C892 2 ^["^^_$1$DGA228:[CHEY19.VBB]"]ORE(100.2,9573, 0)\n \n Solution:\n ---------\n Routine ORWDX has been modified to only issue one lock per event, \n regardless of the number of orders released that are associated with\n the event.\n\n
\nA site reported a patient safety issue with the alert information \n \nIn the interim, the alert text is being modified to alleviate some of the \nconfusion. In addition, some documentation updates are being made to \nremind sites to enable both of the alerts to ensure the provider gets all \nthe appropriate information.\n \nThe NAME field (.01) and the MESSAGE TEXT field (.03) of the OE/RR \nNOTIFICATIONS file (#100.9) are being modified for alerts 22 and 25 \n(internal entry numbers for the two alerts). Alert 22 is being changed \nfrom IMAGING RESULTS to IMAGING RESULTS, NON CRITICAL. Alert 25 is being \ndisplayed when imaging results, either abnormal or not, are completed. \nchanged from ABNORMAL IMAGING RESULTS to ABNL IMAGING RESLT, NEED ATTN.\n \nThe change is being made using a post-installation routine. The person \ninstalling the patch will receive a MailMan message with a subject of \n'OE/RR NOTIFICATIONS ALERT NAME UPDATES' when the update is complete.\n \nThis patch requires a change in the Radiology/Nuclear Medicine V. 5.0 \npackage. The documentation changes to update the notification name will \nbe included in a separate documentation release.\n \nThe problem stems from the fact that the alerts can be disabled and, if \nPlease note: the post-install routine, ORY268, will be removed in a \nfuture patch.\n \nAssociated Remedy:\n==================\n1. HD0000000132027 Imaging Results versus Abnormal imaging results\n \nAssociated NSR(s):\n==================\nN/A\nso, due to the text of the alert, the provider may miss some critical \n \nTest Sites:\n===========\nTBA\n \nOverview:\n=========\n \n1. HD0000000132027 Imaging Results versus Abnormal imaging results\n \ninformation.\n Problem:\n =========\n The Radiology Package currently always sends the following alert \n notifications to OERR/CPRS, conditioned on the type of result (normal, \n abnormal, amended - normal or abnormal)\n 22 - IMAGING RESULTS (contains normal results)\n 25 - ABNORMAL IMAGING RESULTS (contains abnormal results)\n 53 - IMAGING RESULTS AMENDED (contains both normal and abnormal)\n Based on the parameter settings, some of these alerts may not display. \n Due to the text of the alert subject, this may be misleading for the \n \n provider.\n \n Solution:\n =========\n The 'imaging results' notification may refer to both normal and \n abnormal results. The abnormal results are non-critical. The agreement \n between the Computerized Patient Record System (CPRS) Clinical\n Workgroup and the Radiology subject matter expert is to modify the\n text of alerts 22 and 25 to reduce the confusion. Alert 22 will \n become 'IMAGING RESULTS NON CRITICAL'. Alert 25 will become 'ABNL\nThe final solution is considered an enhancement and the Radiology subject \n IMAGING RESLT, NEED ATTN'.\nmatter expert will be working with the patient safety office to formulate \na new service request to outline the desired behavior.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*319.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*307.\n\n
\nRefer to the patch description on the patch message.\n\n
\nA site reported a problem where a narcotic order replaced an audiology \n Upon examining the order affected in the ORDERS file (#100), it was \n discovered that an Outpatient Pharmacy prescription had over-written\n the audiology consult.\n \n Resolution:\n -----------\n An issue was found in the Class III code which performs the AudioCare \n renewal process. The issue was in the difference between how the \n Computerized Patient Records System (CPRS) assigns a new order number\n and the process AudioCare renewal was using.\nconsult order.\n \n The decision was to create a Class I interface from the AudioCare \n refill/renewal system. The refill portion will not be affected. The \n renewal process will now use a standard CPRS Application Programming \n Interface (API) to perform the renewal.\n \nOverview:\n=========\nHD0000000296920 Unexpected narcotic order found in OERR for a patient\n \n Problem:\n --------\n\n
\nThis patch will correct the following problems.\n \nHD0000000339814 - Glucophage Contrast Media Order Check not triggered.\n \n Glucophage Contrast Media and Glucophage Lab Results Order Checks are \n not triggered for a metformin order with lower case letters in the drug\n name. For instance, a site using TALLman lettering for a metformin\n order (metFORMIN) did not fire checks.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*330.\n\n
\nThis patch corrects 2 issues within the ORDER ENTRY/RESULTS REPORTING \npackage:\n \n1. Signing multiple Lab Collect orders can result in a crash if their \n collection time has passed.\n \n2. IV Medication quick orders do not show the "Give additional dose NOW?" \n prompt when appropriate.\n\n
\nA site reported a problem where a narcotic order replaced an audiology \n Upon examining the order affected in the ORDERS file (#100), it was \n discovered that an Outpatient Pharmacy prescription had over-written\n the audiology consult.\n \n Resolution:\n -----------\n An issue was found in the Class III code which performs the AudioCare \n renewal process. The issue was in the difference between how the \n Computerized Patient Records System (CPRS) assigns a new order number\n and the process AudioCare renewal was using.\nconsult order.\n \n The decision was to create a Class I interface from the AudioCare \n refill/renewal system. The refill portion will not be affected. The \n renewal process will now use a standard CPRS Application Programming \n Interface (API) to perform the renewal.\n \nOverview:\n=========\nHD0000000296920 Unexpected narcotic order found in OERR for a patient\n \n Problem:\n --------\n\n
\nThis patch corrects the following issue within the ORDER ENTRY/RESULTS\n \nHD0000000377607 - DC1+5^ORCSEND Errors\n \n The Order file's veiled field originally was used to hide unreleased \n orders many years ago. The functionality was brought to use once more \n by patch OR*3*282 to hide lab parent orders once they are signed.\n Unfortunately, it was not discovered that running the Lab Order Checks\n clean up utilities purged old veiled orders. This functionality may \n have been appropriate for unsigned new orders but not for signed parent\n orders.\nREPORTING package:\n \nHD0000000352115 - Delayed order release event for repeating lab quick \n order.\n \n A repeating lab order with a released delay will wrongly copy the value\n Ordering Parameters Location field found in the firing event to the\n Ordering Location of the child order. \n\n
\nThis patch corrects several problems withg Lab ordering via CPRS List\nManager. \n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*280.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*280.\n\n
\nThis patch resolves the following problems:\n \n Implemented key filtering and range checking for daily dosages. Problem \n with auto-calculation of daily dosage, and problem changing tablets in\n daily dosing.\n \n <UNDEFINED> error on start-up, which occurs when entering a New Patient \n whose most recent INR was cancelled.\n \n Replacing the number of tablets in daily dosing may result in a zero \n being appended unintentionally.\n \n \n Division by zero error in Rosendaal Report, which occurs when \n patienthas two consecutive INRs which are identical, one in-range and \n one-out, due to goal range change. \n \n Problem where lab orders were not being placed by Anticoagulator unless \n a note was also written. This was happening because the Order Entry API \n requires an Encounter Location, and the corresponding variable was only \n being set if a note was also entered.\n \n Assure that cosigner is identified as primary provider in PCE, if user \n Problem where changes in the patient location were not being recorded \n when the user clicked on the Save and Exit button.\n \n The original application didn't allow INRs to be ordered for collection \n on the weekend. Site's reported that they often need to order for \n weekend collection. The application was modified to inform the user \n that the date they selected for the next draw is a Saturday (or \n Sunday), and allow them to leave it or change it, as they deem \n appropriate.\n is a non-Provider (e.g., Student, Pharmacy Tech, etc.).\n \n Problem with Other Indication not being "remembered" between sessions.\n \n Assure that Scheduled (in addition to Pending or Active) Consults get \n completed when Initial Note is filed.\n\n
\n This patch will correct an issue with complex orders entered through\n CPRS. If the complex order uses a THEN conjunction and the admin time of \n a single section of the order is before the current time, that\n administration was being dropped off. This would only happen on a section\n of the complex order other than the first section.\n\n
\nThis patch will correct an index out of bounds error that occurs when a \nuser adds too many coversheet reports to the CPRS gui.\n\n
\nUnseen orders are being auto-unflagged when processing a flagged orders \nalert.\n \nA flagged order recipient doesn't see a notification if an order is \nflagged too soon after a previous flagged order.\n\n
\nRefer to the patch description on the patch message.\n\n
\n1. Patch OR*3*281 added a temporary menu option and routine to the system\nbe used. This patch removes PHARMACY as an option.\n4. Enter/edit quick orders [ORCM QUICK ORDERS] option would get an \nundefined error when editing the infusion rate field if the text was over \n20 characters in length.\nto assist in cleaning up Radiology quick orders. This patch removes that\noption and routine. HD0000000218893\n2. Patch OR*3*299 added a temporary routine to the system to clean up \nproblem Outpatient medication orders. This patch removes that routine.\nHD0000000284146\n3. Enter/edit QO restriction [ORCM QO ITEMS] allows PHARMACY as a \nrestriction. However, the code that processes restrictions does not check \nfor this. The workgroup decision was that the specific package needed to \n\n
\nProblem:\n \nResolution:\nModified routine ORCACT0 to disallow the transfer of a complex order with \nTHEN as the conjunction.\n \nAssociated Remedy:\n==================\nHD0000000205100 - 1 Complex Orders Transferring for Providers\n \n \nA site reported a problem with the transfer of complex Outpatient \nAssociated NSR(s):\n==================\nN/A\n \n \nTest Sites:\n===========\nMedication orders that contained a conjunction of THEN. The problem is \nthat when the order goes (in its entirety) to Inpatient Medications there \nis no way for the provider or the finishing pharmacist to determine how \nfar into the process the order has progressed.\n \nThe patient safety workgroup recommended that transfer of Outpatient \nmedication orders with a THEN conjunction should be prevented.\n\n
\nThis patch corrects an issue within the ORDER ENTRY/RESULTS REPORTING \npackage:\n \nHD0000000343856 - If there are multiple lab orders in a given day then\nthe Lab Orders clinical report will only display one.\n\n
\nThis patch will correct the following issues:\n \n4)Incorrect data is showing up on the Search orders by Nature or Status \n [OR NATURE/STATUS ORDER SEARCH] report.\n1)Relative dates are not saving time in custom views in the CPRS orders \n tab.\n \n2)Data on the clinical surgery report is hanging over from one item to \n another.\n \n3)When creating a new patient movement, discontinued orders are \n displaying on the "Copy active orders for selected event" dialog\n\n
\nThis patch will correct the following issues\nand/or dietetic orders, the auto discontinue of these orders is not being\nrecorded in the OE/RR PATIENT EVENT file (#100.2). There is also a rare\ncircumstance in which if the user discharging the patient is assigned to a\ndifferent division than the location of the ward. The entry to the OE/RR\nPATIENT EVENT file (#100.2) is not created.\nWhen a patient is discharged and the user, at the Review Delayed Orders \nprompt, enters "^^" or lets the system timeout the discharge process does\nnot fully complete. Once the Review Delayed Orders prompt is exited in one\nof the ways described above, processes that are supposed to take place\nduring the discharge don't happen. This is causing some orders to not\ndiscontinue.\n \nIt was discovered that if a patient is discharged and only has pharmacy \n\n
\nThis patch is part of the Identification of Principal Mental Health\nProvider(IPMHP) project. It is to be released in conjunction with PCMM\npatch SD*5.3*575, with SD*5.3*575 being installed first. The purpose of\nthis patch is to implement the API being released in SD*5.3*575 to display\nthe Principal Mental Health Provider in two locations within CPRS GUI, one\nbeing the patient detail display and the other being the Primary Care\nbutton detailed display.\n\n
\n1. HD0000000377325 - 9 SHWTLT+10^XPAREDT3 Error \n selection.\n \n 3. HD0000000300224 - 2 LAB QUICK ORDER\n --------------------------------------------\n When building a quick order the How long field does not properly\n apply the Max days limit when using Xnumber of times format.\n \n 4. HD0000000406792 - 3 Standard Schedule (Changed) Creates Endless \n Loop for Finishing Pharmacist\n --------------------------------------------\n --------------------------------------------\n When renewing an order with an invalid/changed schedule, IV orders\n are not properly verified.\n Selecting the GUI Reports User Display Parameters option causes a \n SHWTLT+10^XPAREDT3 Error.\n \n 2. HD0000000069559 - 9 PUG-1101-51042 Can't change user values-Report \n parameters \n --------------------------------------------\n The GUI Reports User Display Parameters option does not allow user \n\n
\nThis patch corrects an issue with a recursive lookup that causes a very\nlong pause in the software. It also corrects a situation where a user\ncan select a large number of items to replace, but only some of them are\nupdated.\n\n
\n1. The Display Patient Alerts and Alert Recipeients [ORB3 ALERT\ninformation is written over the previous information. This patch corrects \nthis problem by having the chart review information behave the same as the\nother verify actions. If an action is chart reviewed, and the previous\naction was not chart reviewed, the current chart review information is\nused for the previous action. HD0000000268742\nRECIPIENTS] option always uses the default action of 'Close' - even when \nthere is more than one screen of alerts. This patch modifies this \nbehavior so that if a screen is not the last screen of the display, the \ndefault action is 'Next Screen'. HD0000000069366\n2. The Orders tab detailed display shows the order along with the most\nrecent Chart Review information. However, when there is a change to the\noriginal order, and that change has a chart review performed, the detail\ninformation is incorrect. The problem is that the current chart review \n\n
\nThis patch will correct the following issues:\n3)A subscript error when an ordernumber of 0 is sent back to the ORWDX1 \nORDMATCH Remote procedure call.\n1)An undefined error when a patient in observation is discharged.\n \n2)When using the Manage orderable items [ORCM ORDERABLES MENU] for \nediting orderable items, orderable items are selectable for edit by \ninternalentry number (IEN) even if they are not in the appropriate \ndisplay group.\n \n \n\n
\nThis patch corrects 4 issues within the ORDER ENTRY/RESULTS REPORTING \n option Medication Quick Order Report [OR MEDICATION QO CHECKER]. If \n the user enters a lower case letter 'n' the report runs anyway.\n \n3. When using the remove function for VistA option Team List Mgmt Menu\n [ORLP TEAM MENU] the special number '999' is used to display more \n patients. When the list contains more than 998 patients, the entry\n '999' removes the patient in position 999 instead of displaying more\n patients.\n \n4. When using the remove function for VistA option Team List Mgmt Menu\npackage:\n [ORLP TEAM MENU] the special number '999' is used to display more \n patients. When the list contains more than 39 patients and one of the \n patients has an IEN of 999, the entry '999' has you select between the \n patient and the more option.\n \n1. Cancelling orders from a Delayed Orders list in CPRS (Computerized \n Patient Record System) GUI (Graphical User Interface) causes them \n to appear in the Active Orders list. They should be filtered out \n until the release event happens.\n \n2. Patch OR*3*296 added the prompt 'Do you wish to continue?' to Vista\n\n
\nThis patch is described in the National Patch Module under OR*3*2.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder OR*3.0*357.\n\n\n
\nThe purpose of this patch is to provide a software bug fix for CPRS. \nThis patch corrects the following issue:\n \n-Schedule change error for IMO orders\n\n
\nThis patch corrects 4 issues within the ORDER ENTRY/RESULTS REPORTING \n \n3. Copying a lab order with a static date results in a new order with a \n blank date.\n \n4. Copying a lab order will not generate a duplicate check against the\n original order.\npackage:\n \n1. Copying a generic order that used static dates (eg Jul 9, \n 2010) instead of relative dates (eg T+3) may result in a new order with\n invalid dates.\n \n2. Renewing a nursing order with static dates may result in a new order \n with invalid dates.\n\n
\nThis patch updates the OE/RR NOTIFICATION (#100.9) alert CONSULT/REQUEST\nUPDATED to inform the user of all actions that triggers the alert. The \npatch also updates the ORDER DIALOG (#101.41) entry GMRCOR REQUEST to \nalways prompt the user with the RELATED SERVICES saved on the Quick Order \nand allow them to change it, if needed. The help text when creating a \nnew prompt has been updated to remove the "subfile" wording.\n\n
\nThis patch will correct the following\n \n1. When a patient has changed clinics and is displaying on the team \n list for the new clinic. They are not being removed from the old\n clinic's team list.\n \n2. When listing all patients on a clinic team list using the \n Anticoagulation Patinet Lists [ORAM PATIENT LIST MENU] option, patients\n whos name begins with the letter Z do not show up.\n\n
\nThis is a companion patch to the Medication Order Check Healthcare \nApplication (MOCHA) version 1.0 Enhancements 1 group of patches that will\nresolve a number of issues with the Computerized Patient Record System\n(CPRS) version 3.0 order checking functionality. See the patch message for\na full listing of issues addressed and installation instructions.\n\n
\n1. In the Computerized Patient Record System (CPRS), on the Labs tab,\n2. In CPRS, on the Labs tab, under Microbiology, the accession number\ndisplay should be changed to show the COTS accession number. This patch\nmakes this change by looking for the presence of the API GETACC^LRJWLST\nand, if present, uses the API to retrieve the COTS accession number from\nthe LAB DATA file (#63). If no COTS accession number is available, the \nlegacy accession number will display.\n \n3. Laboratory V5.2 patch LR*5.2*425 is adding the ability to inactivate a\ncollection sample. CPRS will now honor the INACTIVE DATE (#64.9101) field\nin the COLLECTION SAMPLE (#62) file.\nunder Anatomic Pathology, the accession number display should be changed\n \n4. An error was occurring in CPRS when attempting to display the Anatomic \nPathology supplemental report. The error was caused by a modification \ndone in support of the LEDI v4 release. In order to eliminate the error, \na modification was done to CPRS to support the LEDI v4 change.\n \n5. There are two new order reasons being used by Laboratory V5.2. They \nare Obsolete Order and Purged Order. A request was made that these two \nreasons be added to the ORDER REASON file (#100.03). The post install of \nthis patch will automatically add these reasons.\nto show the Commercial-Off-The-Shelf (COTS) accession number. This patch\n \n6. The Lab users have requested that when certain fields are updated in \nthe LABORATORY TEST (#60) file, there should be a CPRS call made to search\nfor quick orders that contain the test that was updated. If any are found,\nthe appropriate personnel will be notified. This patch addresses this\nissue by creating a new routine ORLRQO that will search for the specified\ntest and notify the members of the OR CACS mail group. They will be told\nthe quick order name and whether it is active or inactive.\n \n7. Since the COTS system, when present, will now be considered the Lab\nmakes this change by looking for the presence of the Application\nsystem of record, the date/time completed from the COTS system should be\nwhat is stored in the Lab system as the date/time completed. However, this\nmight cause some concern on the CPRS side since there may be a delay if\nthe interface from VistA to the COTS system is down for any reason. In\norder to help mitigate this issue, this patch will modify the information\nstored in the RESULTS DATE/TIME field (#71) of the ORDER file (#100) to\ncontain the date/time the results information was sent to CPRS, rather\nthan the date/time completed from the COTS system.\n \n8. Laboratory V5.2 patch LR*5.2*425 is adding the ability to inactivate a\nProgramming Interface (API) GETACC^LRJWLST. If that API exists, CPRS will\ntopography. CPRS will now honor the INACTIVE DATE (#64.9103) field\nin the TOPOGRAPHY FIELD (#61) file.\n \n9. The Laboratory Lab System Re-engineering project (LSRP) has requested\nan API to allow Lab to unveil an order in CPRS. This patch adds that new\nAPI.\n \n10. LSRP has requested an API to update the PACKAGE REFERENCE field (#33) \nof the ORDER file (#100). This patch adds that new API.\nuse it to retrieve the COTS accession number from the LAB DATA file \n(#63). If no COTS accession number is available, the legacy accession \nnumber will display.\n \n\n
\nThe description of this patch may be found in the National Patch Module \nunder OR*3.0*348.\n\n
\nCONTAINS COMPONENTS NEEDED TO COMPLETE THE PRE-INSTALLATION OF\nCOMPUTERIZED PATIENT RECORD SYSTEM (CPRS) VERSION 29. REFER TO THE PATCH\nDESCRIPTION FOR INSTALLATION INSTRUCTIONS AND COMPONENT INFORMATION.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*306.\n\n
\nThis patch will correct the following issues:\n \n3) In certain scenarios, when entries to the Orders File (#100) are \n deleted, there are dangling cross references that are left behind. \n These cause errors during nightly processing and cprs order views.\n1) When ordering certain types of quick orders. Information about the \n order such as service connected and treatment factors display, even \n though there has been no opportunity to enter this information about \n the order.\n \n2) When orderable items are flagged to display an alert to the provider \n when they are expiring. They were not creating alerts correctly for \n the outpatient paramter.\n\n
\nThis patch will correct the following issues:\n range (TTR) using the Rosendaal method count inactive patients. \n This is incorrect because the Rosendaal method makes no mention of \n missed appointments.\n \n4) It is possible to create progress notes that contain no text. This \n is caused by the user having the ability to continue and file the \n note before making a selection about what data to put in the note.\n \n5) The patients lost to follow up utility does not take missed \n appointments into account. This will cause a provider to incorrectly \n1) When running the Anticoagulation Management GUI, in some cases \n believe that a patient has been seen, where he/she may have, in \n reality, just missed an appointment.\n \n6) Error "'' is not a valid floating point value" is displaying when \n entering 0.25 as the tablet size for a Monday dose.\n the help file will fail to be found.\n \n2) After a Missed Appointment has been filed, there are cases in \n which the Daily dosing schedule and total weekly dose don't \n coincide with what has been entered into the patient notes.\n \n3) The clinic and facility-wide calculation of the time in therapeutic \n\n
\nThis patch corrects 1 issue within the ORDER ENTRY/RESULTS REPORTING \npackage:\n \n1. The Patient Selection screen can be set up to display a clinic's \n appointments for a date range. The screen will show no more than 200\n appointments. The screen does not show the user any message that the\n maximum has been reached and that some of the appointments for the date\n range are not being displayed. The appointments dropped can be from any\n part of the date range.\n\n
\nIn support of the Clinic Orders project, a need has been identified to \nsend Nurse Verify information from the Computerized Patient Record System \nV. 1.0 to Inpatient Medications V. 5.0. The purpose of this patch is to \nmake this modification.\n\n
\nDelayed orders for allergies were not properly released to the ADVERSE\norders were being left in an active status. This caused confusion in the\ndisplay of allergy orders. \n \n \nThis patch will correct the above problems.\n \n \nThis patch includes one new protocol, OR GMRA UPDATE and also includes the\nGMRAOR ALLERGY ENTER/EDIT order dialog. \n \nREACTION TRACKING (ART) package upon patient movement. The status of the\nChanges have been made to the GMRAOR ALLERGY ENTER/EDIT order dialog and\nits items in support of allergy entry via the CPRS GUI. \n \nA new routine ORMGMRA is also exported with this patch.\norders was not properly updated to active upon patient movement.\n \nWhen an order for NO KNOWN ALLERGIES was entered, these orders were not\ndisplaying properly with allergy orders. The post-install for this patch\nwill correct the "AW" cross-reference on all NKA orders in the file.\n \nWhen a reaction to a causitive agent was entered, pre-existing NKA\n\n
\nThis patch will correct the following issues:\n \n4) When a mail message from AudiCare Auto-renwal is alerting about an \n invalid Provider status, the provider in question is not known.\n1) Parameter definition description missing for OR AUTORENEWAL USER.\n \n2) Renewed prescriptions processed by AUDIOCARE are showing the user \n who processed audiocare renewals as the person who entered the \n renewal.\n \n3) Mail messages from AudioCare Auto-renewal are not displaying \n enough information to identify a patient in CPRS.\n\n
\nPrevent notes without text from being signed\n\n
\nCONTAINS FOLLOW-UP FIXES FOR ORDER ENTRY/RESULTS REPORTING SOFTWARE \nVERSION 3.0 PATCH 345 (OR*3*345). REFER TO THE PATCH DESCRIPTION FOR \nINSTALLATION INSTRUCTIONS AND COMPONENT INFORMATION.\n\n
\nTHIS PATCH CORRECTS THE SAME PATIENT SAFETY ISSUE CORRECTED IN PATCH \nOR*3*380, HOWEVER, IT INCORPORATES OTHER CHANGES MADE BY PATCH OR*3*311, \nPART OF THE MOCHA 2 BUILD. REFER TO THE PATCH DESCRIPTION FOR A DETAILED \nEXPLANATION.\n\n
\nThis patch corrects 1 issue within the ORDER ENTRY/RESULTS REPORTING \npackage:\n \n1. The Auto-unflagging of orders with the ORPF AUTO UNFLAG parameter set\n to YES has resulted in pharmacy queries or reccomendations not being\n read or responded to.\n\n
\nDelayed order-Framestack-Cumulative Report fixes\n\n
\nThis patch corrects 3 issues within the ORDER ENTRY/RESULTS REPORTING \n the Cover Sheet and the Vitals entry form.\npackage:\n \n1. Changing an unsigned order does not update the entering provider.\n \n2. Chart Copies are enabled for printing even when no format has \n been set up.\n \n3. There is a discrepancy in metric measure conversions for weight between\n\n
\nModified the API LMENTRY^ORB3U1 to properly parse out the alert message \ncontaining the CV tagged data in addition to the current parsing \nmechanism in place.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3*361.\n\n
\nCPRS RPC changes for the VIA project. See patch description for further \ndetails.\n\n
\nSee patch description for full content description.\n\n
\nThe purpose of this patch is to provide an API to Pharmacy for returning \nthe nature of order for a CPRS order.\n\n
\nThis patch corrects 6 issues within the ORDER ENTRY/RESULTS REPORTING \n4. CPRS will allow a duplicate team list name when entering personal \n lists.\n \n5. Occasionally, the option ORLP3M DISPLAY LIST SOURCE displays the\n current user's list source instead of the selected user.\n \n6. Various ORLP options do not timeout when selecting a list in use \n elsewhere.\npackage relating to team lists:\n \n1. Error on entering "^" at the Type prompt of option ORLP TEAM ADD.\n \n2. Team list visibility is changed when edited.\n \n3. Locks are set late when creating or renaming lists.\n \n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3.0*385.\n\n
\nNote: This patch can only be installed at sites running CPRS.\nFrom: SHAPIRO.NANCY@SANFRANCISCO.DOMAIN.EXT Page 1\n--------------------------------------------------------------------------\n \nI stumbled onto this minor problem. If I access options in\nthe following order, I get my DUZ displayed instead of my name.\n \nPATIENT LIST MGMT MENU\n DISPLAY USER'S TEAMS\nTEAM LIST MGMT MENU\n EXAMINE/PRINT EXISTING LIST(S) <--- DUZ appears instead of user's name\n \n \nSelect Patient List Mgmt Menu Option [TEST]: ?\n \n PS Patient Selection Preference Mgmt ...\n TM Display User's Teams\n PT Display Patients Linked to a User via Teams\n TE Team List Mgmt Menu ...\n \nSelect Patient List Mgmt Menu Option [TEST]: TM Display User's Teams\n \nAddresses NOIS: SFC-0198-60744\nFind teams linked to user: SHAPIRO,NANCY// NS IRM\n \n \n SHAPIRO,NANCY IS ON THE FOLLOWING TEAMS:\n \n12/31/97 PAGE: 001\n--------------------------------------------------------------------------\n1 NANCY\n \n \n \nSelect Patient List Mgmt Menu Option [TEST]: ?\n \n PS Patient Selection Preference Mgmt ...\n TM Display User's Teams\n PT Display Patients Linked to a User via Teams\n TE Team List Mgmt Menu ...\n \nSelect Patient List Mgmt Menu Option [TEST]: TE Team List Mgmt Menu\nSelect Team List Mgmt Menu Option [TEST]: ?\n \nFixes a team list display problem as reported and described by Nancy\n CR Create/Add to Team List\n EX Examine/Print Existing List(s)\n PR Remove Providers from a List\n PT Remove Patients from a List\n DE Delete Existing List(s)\n AL Remove Autolinks\n \nEnter ?? for more options, ??? for brief descriptions, ?OPTION for help\ntext.\n \nShapiro at San Francisco:\n Select Team List Mgmt Menu Option [TEST]: EX Examine/Print Existing\n \n Select LIST to examine/print: 1003201// \n \n \nSubj: CPRS TEAM DISPLAY PROBLEM [#491781] 31 Dec 97 10:59 PDT 74 Lines\n\n
\nThe International Classification of Diseases, Tenth Revision (ICD-10) \nalpha-numeric characters. This value does not include the decimal point, \nwhich follows the third character for the ICD-10-CM code set. There is no \ndecimal point in the ICD-10-PCS code set. \n \nThese code sets have the potential to reveal more about quality of care, \nso that data can be used in a more meaningful way to better understand \ncomplications, better design clinically robust algorithms, and better \ntrack the outcomes of care. ICD-10-CM also incorporates greater \nspecificity and clinical detail to provide information for clinical \ndecision making and outcomes research.\nClass 1 Software Remediation project replaces the 30-year-old set of \ndiagnosis and procedure codes (ICD-9-CM) that medical personnel use. \nDates of service, or dates of discharge for inpatients, that occur on or \nafter the implementation date will use the ICD-10 code set. Clinical \nModification (ICD-10-CM) diagnosis codes increase from about 13,000 ICD-9 \ncodes to more than 68,000. Procedure Coding System (ICD-10-PCS) procedure \ncodes increase from about 3,800 ICD-9 codes to nearly 87,000. Both \nsystems also expand the number of characters allotted to seven \n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3.0*398.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThe description of this patch may be found in the National Patch Module\nunder OR*3.0*391.\n\n
\nSets the ORWRP TIME/OCC LIMITS INDV parameter at the Package level for \nseveral OE/RR REPORT file entries.\n\n
\nEmergency release of 30.A to address ICD10 issues.\n\n
\nThe purpose of this patch is to provide a software bug fix for CPRS \norders functionality. This patch addresses the following issues:\n \n-'Treating Specialty' disappears when order is renewed or Give Additional \nDose Now is selected.\n\n
\nThis patch corrects 2 issues within the ORDER ENTRY/RESULTS REPORTING \npackage:\n \n1. Non-OERR alerts are being deleted without the rights to do so.\n \n2. Typo in the CPRS User Guide:GUI Version.\n\n
\nThis build changes the source of Primary Care information in the \nheader and details wondow from VistA to PCMMR.\n\n
\nSee description on patch message.\n\n
\nOR*3.0*402\n\n
\nThis build contains the OE/RR items affected by the rename of EARLIEST \nDATE (123;17) to CLINICALLY INDICATED DATE.\nThis build should restore the M routines, order dialogs, and ORCDGMRC\nEARLIEST DATE DEFAULT parameter to a pre-OR*3.0*350 state.\n\n
\nCONTAINS ROUTINE UPDATES THAT WILL ENABLE COMPUTERIZED PATIENT RECORD \nSYSTEM (CPRS) VERSION 1.0.29 TO DISPLAY SIGNS/SYMPTOMS WITH MEDICATION \nORDER CHECK MESSAGES AND WILL ENABLE REMOTE DATA INTEROPERABILITY (RDI) \nTO RETRIEVE SIGN/SYMPTOM, SEVERITY, AND OBSERVED/HISTORICAL DATA FOR AN \nADVERSE REACTION FROM THE HEALTH DATA REPOSITORY (HDR). REFER TO THE \nPATCH DESCRIPTION FOR INSTALLATION INSTRUCTIONS AND FURTHER INFORMATION.\n\n
\nOR RPC updates for VIAB*1*7.\n\n
\nThe OR*3.0*422 patch allows the use of special characters (particularly \n \n--------\nWith the switch to using CPRS GUI Order Menus rather than ListManager \nordering menu options, there remains a limitation on the characters \nallowed to build menu items. Specifically, the equal sign (=), comma \n(,), semi-colon (;), and hyphen (-) are restricted when they do not need \nto be.\n \nResolution:\n-----------\nRemove the restrictions on certain special characters by modifying the \nUse of the following special characters will now be allowed: hyphen (-), \nCHKNAM tag inside the ORUTL routine in order to remove the restriction \nfor the characters stated above. The up-arrow (^) still remains as a \nrestricted character because of M (MUMPS) restrictions.\n \nTest Sites:\n \nHunter Holmes McGuire VA Medical Center (Richmond)\n \nOrlando VA Medical Center\n \nsemicolon (;), comma (,), and equal sign (=). Use of the caret (^) is \nWilliam S. Middleton Memorial Veterans Hospital (Madison)\n \nVA Central Plains Health Care System (Omaha, Lincoln, Grand Island of NE, \nDes Moines, Knoxville, Iowa City of IA)\n \n \nDocumentation Retrieval Instructions\n------------------------------------ \n \n \nstill restricted because it is used as a field delimiter in VistA. \nPre/Post Installation Overview\n------------------------------\n \n \nPre-Installation Instructions\n-------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \n \n \nInstallation Instructions\n-----------------------------\n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select \n the Installation Menu. From this menu, you may elect to use the \nAdditional changes will be made to the Data Dictionary elements of the \n following options. When prompted for the INSTALL NAME enter\n OR*3.0*422.\n \n a. Verify Checksums in Transport Global - This option will \n allow you to ensure the integrity of the routines that are in\n the transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this \nORDER DIALOG (#101.41) file to modify the Help displayed when entering a \n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n \n4. From the Installation Menu, select the Install Package(s) option \n and choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\nquestion mark at a VistA prompt. The affected fields are: \n Install? NO// Press <Enter>\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO// Press <Enter>\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO// Press <Enter>\n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0// respond 0.\n \n \n \nPost-Installation Instructions\nN/A\n* ORDER DIALOG (#101.41) file, DISPLAY TEXT (#2) field \npunctuation) within the Order Menu Management Menu Editor. A previous \n \n* ORDER DIALOG (#101.41) file, ITEMS (#10) sub-file, DISPLAY TEXT (#4) \nfield \n \nThis intake has been implemented locally at the VA centers in Fargo, ND; \nSioux Falls, SD; Meade, MD; Minneapolis, MN; Omaha, NE; Richmond, VA; St. \nCloud, MN; Seattle, WA; Milwaukee, WI; Hot Springs, AR; Des Moines, IA; \nand Iowa City, IA. \n \nThe NSR for this intake addresses the following requirement: \nVistA patch disallowed use of special characters. The patch was intended \n \n* VHBAO: NEED3045 Provide the ability for the users to include \npunctuation and other special characters in CPRS order menu notes.\n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\nto prevent display problems within ListManager; however, most sites are \n--------------------- -------------------- --------------------\nORDER DIALOG (#101.41) DISPLAY TEXT (#2) MODIFIED\n \nORDER DIALOG,\nITEMS (#101.412) DISPLAY TEXT (#4) MODIFIED\n \n \n \nForms Associated:\n \nusing the Computerized Patient Record System (CPRS) Graphical User \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \nInterface (GUI) and the inability to utilize punctuation can negatively \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nN/A\n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nimpact the clarity of menu options and instructions. This modification \nN/A\n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \nTemplates Associated:\n \nrestores the ability to use certain special characters in Order Menu \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nN/A\n \nAdditional Information:\n \n \nNew Service Requests (NSRs)\n----------------------------\nNSR 20131108 REMOVE LISTMANAGER RESTRICTIONS ON MNEMONICS\nManagement so that users can more clearly specify order menu options. \n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \nRemedy Ticket(s) & Overview\n---------------------------\nN/A\n \nProblem:\n\n
\nThe description of this patch can be found in the National Patch Module.\n\n
\nPatch OR*3.0*425 allows inpatient delayed \nspecific scenario in which inpatient delayed \norders are written for an admission event, \nbut then the patient is not admitted (post \ntreatment/post procedure the patient remains \nan outpatient) and the delayed orders are \nrequired at an outpatient location, such as \na Post Anesthesia Care Unit. Under the current \nfunctionality, these inpatient delayed orders \ncannot be released to the outpatient location \nbecause the admission event never occurred. \norders (with the exception of Unit-Dose \nAfter implementation of this patch, the delayed \norders (with the exception of Unit-Dose Meds \norders and Diet orders) can be successfully \nreleased to an outpatient location.\nMeds orders and Diet orders) to be manually \nreleased to outpatient locations. Without \nthis modification, care to patients can be \ndelayed while providers re-enter orders \npreviously entered as inpatient orders.\n \nThis solution is designed to address the \n\n
\nOR*3.0*417 makes changes to order details in support of Bar Code\norder:\n \n1. PSS*1*191\n2. PSJ*5*315\n3. PSB*3*83\n4. PSB*3*87\n5. OR*3*417\n \nATTENTION: This enhancement also includes a new Graphical User Interface\n(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is\nMedications Administration (BCMA) and Inpatient Medications enhancements\nrequired immediately after the KIDS install for the Patch to function.\n \nFor retrieval and installation instructions, please see the Client \nInstallation Instructions section.\n \n**************************************************************************\n \nThe change made by OR*3*417 is in support of requirements for patch\nPSB*3.0*83. All the patches in this group should be installed prior to \npatch OR*3.0*417.\nfor Transdermal Administrations.\n \nThe change will add a line to the Order Details report and the Medication\nAdministration History Report in the Computerized Patient Record System\n(CPRS). These reports will display the Removal times for Medications\nthat Require Removal (MRRs).\n \n******************************* ATTENTION ********************************\n \nClinical Ancillary Services (CAS) Development-Delivery of Pharmacy \nEnhancements (DDPE) VA Inpatient Medication Administration - Transdermal\nenhancement includes 5 patches which must be installed in the following\n\n
\nChanges were needed in OE/RR to store data for the eHMP (Enterprise \nrepository for the eHMP data.\n \nThe changes include tracking when an Order was flagged or unflagged by a \nuser. There were also changes to store clinical data in the JDS for \nunsigned, as well as signed, orders. Additionally, discontinued orders \nnow trigger updates to the JDS.\n \nIncludes changes related to patches: 286,424,269\nHealth Management Platform). The eHMP needed data that has dates and \ntimes with seconds and also required triggers when relevant OE/RR data \nwere created and/or edited. The OR* namespace routines were modified to \ncall the appropriate eHMP API (application programmer interface) line \ntags, where needed.\n \nThese eHMP APIs store the data with a date and time stamp that has \nseconds, which are required by the JDS (JSON data store). The JDS is the \n\n
\nOR*3.0*415\n\n
\nPatch OR*3.0*420 modifies the existing Pharmacy package in VistA to\nItem will be displayed in the Information field in the Medication Order \n-----------------\nN/A\n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nN/A\n \ndialog once an Orderable Item is selected. Once a dispense drug is chosen \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\n----------------------------\n20100311 CPRS LAB MONITORING\n \n \n(by selecting a dosage in the order dialog), the lab test information \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nRemedy Ticket(s) & Overview\n---------------------------\nN/A\n \nProblem:\nwill be replaced by the National Standard Drug Information found in the\n--------\n \nResolution:\n-----------\n \n \nTest Sites:\n----------\nJames H. Quillen VA Medical Center (Mountain Home) \nVA Maryland Healthcare (Baltimore, Loch Raven & Perry Point) \nMESSAGE (#101) field of the DRUG (#50) file. This message currently\nTomah VA Medical Center\nEdward Hines Jr., VA Hospital\n \nSoftware and Documentation Retrieval Instructions:\n---------------------------------------------------- \nSoftware being released as a host file and/or documentation describing the\nnew functionality introduced by this patch are available.\n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may also\nshows in CPRS when ordering a dispense drug and is not changed by this\nelect to retrieve files directly from a specific server. \n \nSites may retrieve the software and/or documentation directly using Secure\nFile Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the\nfollowing OI Field Offices:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext \nSalt Lake City: fo-slc.domain.ext\n \nmodification.\nDocumentation can also be found on the VA Software Documentation Library \nat: http://www4.domain.ext/vdl/\n \nPre/Post Installation Overview\n------------------------------\nThere are no Pre-installation routines associated with this patch.\n \n \nPre-Installation Instructions\n-------------------------\n \nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \n \nInstallation Instructions\n-----------------------------\n1. Choose the PackMan message containing this patch.\n \nNote: Follow-on work to allow persistence of the lab test information in \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select \n the Installation Menu. From this menu, you may elect to use the \n following options. When prompted for the INSTALL NAME enter\n OR*3.0*420.\n \n a. Verify Checksums in Transport Global - This option will \n allow you to ensure the integrity of the routines that are in\n the transport global.\nthe Medication Order dialog is expected to be addressed in CPRS v32.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n \ndisplay the most recent associated lab results when a clinician is\n \n4. From the Installation Menu, select the Install Package(s) option \n and choose the patch to install.\n \n5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO// Press <Enter>\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO// Press <Enter>\n \n7. If prompted "Delay Install (Minutes): (0 - 60): 0// enter 0.\nIn order to monitor lab results, lab tests are associated with an \n \n \nPost-Installation Instructions\n------------------------------\nA site Pharmacy CAC/ADPAC will have to set the OR CPRS LAB DISPLAY \nENABLEd parameter to a value of "Yes" using he XPAR MENU TOOLS option \nin order for this functionality to be accessed.\nOrderable Item using the PSS DRUG ENTER/EDIT option in VistA by entering \na lab test in the LAB TEST MONITOR (#17.2) field of the DRUG (#50) file. \n \nThe NSR for this intake addresses the following requirement: \n \n* VHBAO:NEED126: Ability to display laboratory test results, in a single \n view, for ordering inpatient and outpatient medications\n while viewing the Medication Order dialog in CPRS.\nordering medication using the Computerized Patient Record System (CPRS)\n \nThis modification has been implemented locally at the VA centers in \nClarksburg, WV; Hines, IL; Iron Mountain, MI; and Chicago, IL.\n \nThis build contains the components for the CPRS Graphical User Interface \n(GUI) to display relevant laboratory results in the Medication Ordering \ndialog.\n \nTo use the features, the following setup steps are advised:\n * Establish drug-to-lab mapping relationship using the PSS DRUG \nInpatient or Outpatient Medication Order dialogs. Without this\n ENTER/EDIT option. Follow the OUTPATIENT marking pathway to set up a\n LAB MONITOR drug. Lab name, specimen type and number of days to look\n back are required fields for the program to work.\n \n * If not already set correctly, review the site local terms for SERUM \n CREATININE and SERUM SPECIMEN in the CPRS Order Check menus. This is \n required for calculation of Creatinine Clearance.\n \n * When the lab requested is "Creatinine", a second line for CrCl will be \n returned.\nmodification, the clinician must look in numerous locations for this\n \nThe routine ORWDPLM2 is included. This is a version of the display that\nwill work as a TIU OBJECT. The object method is:\n \nS X=$$SL^ORWDLPM2(DFN,\n$S($G(X0)]"":$P(X0,U),$G(NODE0)]"":$P(NODE0,U),1:""),"^TMP($J,""ORWDPLM2""\n)")\n \nThe display is wrapped for ease of reading, but the object method must be \nentered as part of one single line.\ninformation. The information is important for safe and effective\n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n----------------------- ------------------------ --------------------\nN/A\n \nmedication management. \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n \n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nN/A\n \nThe lab results for the most recent lab test associated with an Orderable \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \nSecurity Keys Associated:\n \nSecurity Key Name\n\n
\nThis patch will fix the following issue:\n1. Drug Interaction Order Checks\n\n
\nThis patch contains corrections to the OE/RR patient selection screen.\nSee the National Patch Module for a complete description of the changes.\n\n
\nNOTIFICATIONS SHOWING 'MANDATORY' WHEN THEY ARE NOT\n\n
\nPlease see forum for a complete patch description.\n\n
\nOption ORK EDITABLE BY USER, ORQQPL4 RPC fix\n\n
\nThe description of this patch can be found in the National Patch Module.\n\n
\nFLAGGED ORDER SURROGATE NOTIFICATION ISSUE\n\n
\nSee patch description for details.\n\n
\nSee National Patch Module for full details of enhancements.\n\n
\nPatch OR*3.0*459 addresses the following issue:\n \n1. Anti-Coagulation Show Rate not displaying correct information\n\n
\nThis patch corrects 3 issues within the ORDER ENTRY/RESULTS REPORTING \n \n3. Users can't remove themselves from patient lists of type "Patient \n Manual" \npackage:\n \n1. The hard error <UNDEFINED>EN+3^LEXAFIL occasionally and sporadically\n occurs when the user uses a function in CPRS that calls the Remote\n Procedure Call (RPC) ORWPCE4 LEX.\n \n2. The automated monthly controlled substance report to providers is \n sending the internal id for Prescription instead of the external id.\n\n
\nPatch OR*3.0*428 addresses the following two issues:\n \n1. Undefined error at IN+27^ORDV06B when running the All Medications \nReport in CPRS for Inpatient orders. \n \n2. Undefined error at IN+41^ORDV06B when running the All Medications \nreport in CPRS for Oupatient or Non-VA orders.\n\n
\nPatch OR*3.0*450 will address the following two issues:\nNote: issue 2 is documentation only\n \n1. Flagged Orderable Item Alert not processing all inpatient items in an \n order\n2. CPRS GUI Technical Manual update Lab test order "other" clarification\n\n
\nMOCHA 2.1 follow-up\n\n
\nThe purpose of this build is to resolve the problem with Anticoagulation \nManagement Tool (AMT) and how it deals with edits and complications.\n \nR18005975FY18 - Problem with Complications\n\n
\nORDER DETAILS, DRUG RESTRICTION, & RENEWED ORDER ISSUES\n\n
\nThis patch corrects a single issue - an error the CPRS Debug report that \nonly occurs if there is unexpected data in the XTMP debug log.\n\n
\n \nPatch OR*3.0*462 addresses these 2 issues:\n \nI10009975FY16 - If a user edits an existing diet Quick Order using option \n[ORCM QUICK ORDERS], the system allows a REGULAR/NPO diet to be ordered \nwith another diet.\n \nI10480945FY16 - Medication orders flagged by a pharmacist that are then \nupdated by the pharmacists cannot then be un-flagged in CPRS or PSJ OE.\n\n
\nThis patch corrects 2 issues within the ORDER ENTRY/RESULTS REPORTING \npackage:\n \n1. The show rate calculation skips over visits with an INR that repeats\nthe previous visit's INR.\n \n2. When a patient comes in early - 48 hours before the next draw date -\nthen it is counted as a missed appointment.\n\n
\nThis patch will resolve the following issue: \n1. Prevent truncation of drug data returned from Pharmacy when finishing \nan order.\n\n
\nThis patch corrects 3 issues within the ORDER ENTRY/RESULTS REPORTING \n \n3. When a weight or height entry in to the patient's vitals is marked as\n Pass, Unavailable or Refused the CrCL value for the patient disappears\n even though there is a previous valid entry.\npackage:\n \n1. Orderable Items with a value in the Type field of Neither appear as an\n available lab test when ordering in CPRS.\n \n2. When the last creatinine lab has a "canc" result then the CrCL\n calculation will skip all results with the same specimen and go on to\n look at lab results for other specimens. \n\n
\nBug fixes to RTC Orders\n\n
\nLab labels print when not requested\n\n
\nMOCHA 2.1B Warranty Issues\n\n
\nThis patch addresses two (2) issues:\n--------------------------------------------\n1. I7370452FY16 - PHARMACY ORDERABLE ITEMS / ORDERABLE ITEMS\n I10581756FY16 (d) \n \n Problem: \n --------\n The PHARMACY ORDERABLE ITEMS file (#50.7) NAME field (#.01) is \n not always synced with the ORDERABLE ITEMS file (#101.43) NAME\n field (#.01).\n \n \n The NAME field (#.01) in the ORDERABLE ITEMS file (#101.43) is \n a combination of the NAME field (#.01), max length 40, in the \n PHARMACY ORDERABLE ITEMS file (#50.7) and the NAME field (#.01), \n max length 30, in the DOSAGE FORM file (#50.606). There is a \n space between the two fields and a space at the end of the field.\n This could produce a NAME that is 72 characters in length. \n \n The problem is that the maximum length for the NAME field (#.01)\n in the ORDERABLE ITEMS file (#101.43) is 63 characters. This \n can result in truncation, as well as failed update "pushes" when \n1. The PHARMACY ORDERABLE ITEM file (#50.7) NAME field (#.01) is \n the combination of the Pharmacy Orderable Items Name and Dosage\n Form Name is greater than 63 characters.\n \n The maximum field length for the NAME field (#.01) in the \n ORDERABLE ITEMS file (#101.43) needs to be increased to 72 \n characters.\n \n Resolution:\n -----------\n A Data Dictionary update has been made to the NAME Field (#.01) in \n not always synced with ORDERABLE ITEM file (#101.43) NAME field\n the ORDERABLE ITEM file (#101.43) to increase the maximum field \n length limit to 72 characters.\n \n2. I17614498FY18 - ROOM-BED PRINT DEVICE PARAMETER ISSUES\n \n Problem:\n --------\n \n If a default label printer is defined for a Room-Bed using any of the\n parameters "ORPF CHART COPY PRINT DEVICE ", "ORPF LABEL PRINT DEVICE",\n (#.01).\n "ORPF REQUISITION PRINT DEVICE" and "ORPF WORK COPY PRINT DEVICE", the\n parameter setting is ignored during the CPRS ordering process.\n \n Resolution:\n -----------\n \n Modify routine ORWD2 to determine whether a "device" parameter\n definition exists for the patient's Room-Bed. The "device" parameter \n descriptions were updated to clarify that the location(s) for each \n Room-Bed must have the corresponding "prompt" parameter defined in\n2. Room-Bed default printer parameters are ignored during the ordering \n order for the Room-Bed device to display. The CPRS Technical Manual\n was also updated to include that clarification.\n process.\n \nDefect Tracking System Ticket(s) & Overview:\n\n
\nIssues:\n \n2. When invoking option PSSJI SOLN:\n \n a) An error occurs if a solution is defined to have 'UNIT DOSE \n MEDICATIONS" usage defined as "quick order only".\n \n b) Quick order restrictions are removed if "IV MEDICATIONS" and/or \n "IV SOLUTIONS" usages are defined as "quick order only".\n \nResolution:\n \n----------\n \nModified routines PSSVIDRG and ORMFN to preserve quick order settings on \nadditives and solutions. These changes also prevented the error which \noccurred when a solution or additive was defined to have unit doses as \n"quick order only".\n \nRoutine PSSVIDRG is included in patch PSS*1.0*229 which will be installed \nalong with routine ORMFN in this patch.\n1. When invoking option PSSJI DRUG:\n \n a) An error occurs if an additive is defined to have "UNIT DOSE \n MEDICATIONS" usage defined as "quick order only".\n \n b) Quick order restrictions are removed if "IV MEDICATIONS" and/or \n "IV ADDITIVES" usages are defined as "quick order only.\n\n
\nLAB LABELS INCORRECTLY PRINTED\n\n
\nPlease see forum for a complete description of patch OR*3.0*441\n\n
\nPlease see forum for a complete description of patch OR*3.0*435\n\n
\nThe One Consult Admin Key Consult project is being designed to improve \n \nRemote Procedures Associated:\n New/Modified/\nRemote Procedure Name Deleted \n--------------------- -------------\nN/A\n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n----------------- -------------\nPatch Components\nGMRC ADMIN RBP TO CC New\n \nTemplates, Input Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \nTemplates, List Associated:\n New/Modified/\n================ \nTemplate Name Type Deleted \n------------- ---- -------------\nN/A\n \nTemplates, Print Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \nTemplates, Sort Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \nAdditional Information\n---------------------------- \nN/A\n \nFiles & Fields Associated:\nNew Service Requests (NSRs)\n---------------------------- \nN/A\n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \nDefect Tracking System Ticket(s) & Overview\n-------------------------------------------\n \nN/A\n \nTest Sites:\n----------\nTBD\n \nDocumentation Retrieval Instructions\n------------------------------------\nUpdated documentation describing the new functionality introduced by this \npatch is available.\nFile Name (#) New/Modified/\n \nThe preferred method is to retrieve files from download.vista.domain.ext. \nThis transmits the files from the first available server. Sites may also \nselect to retrieve files directly from a specific server.\n \nSites may retrieve the documentation directly using Secure File Transfer \nProtocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI \nField Offices:\n \n Hines: fo-hines.domain.ext \n Sub-file Name (#) Field Name(Number) Deleted\n Salt Lake City: fo-slc.domain.ext\n \nDocumentation can also be found on the VA Software Documentation Library \nat: \n \nhttp://www.domain.ext/vdl/\n \nTitle File Name FTP Mode\n-----------------------------------------------------------------------\nN/A \n------------------- ------------------ -------------\n \nPatch Installation:\n \nInstallation Instructions\n-------------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install. \n \n100 100.008,80 New\nPre-Installation Instructions\n-----------------------------\nN/A\n \nInstallation Instructions\n-----------------------------\n \n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \nthe current business process used by VistA providers when an imaging order\n \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following option. When prompted for the INSTALL enter patch \n OR*3.0*490:\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option will\nBulletins Associated:\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \n New/Modified/\n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//NO \n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO// \n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? NO//\n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0// respond 0.\nBulletin Name Deleted \n \nPost-Installation Instructions\n------------------------------\nFor all users who will need to be able to perform the task detailed \nabove, these users will need the "GMRC ADMIN RBP TO CC" security key.\n \nBackout and Rollback Procedure:\n-------------------------------\nThis patch contains three RA routines. The decision to back-out or \nrollback software will be a joint decision between development team, VA \n------------- -------------\nsite/region personnel and other appropriate VA personnel.\n \nPrior to installing an updated KIDS package, the site/region should have \nsaved a backup of the routines in a mail message using the Backup a \nTransport Global [XPD BACKUP] menu option (this is done at time of \ninstall).The message containing the backed-up routines can be loaded with \nthe "XtractPackMan" function at the Message Action prompt. The Packman \nfunction "INSTALL/CHECK MESSAGE" is then used to install the backed-up \nroutines onto the VistA System. \n \nN/A\nValidation of Roll Back Procedure:\n----------------------------------\nThe Roll Back Procedure can be verified by printing the first 2 lines of \nthe three RA routines contained in this patch using the option First Line \nRoutine Print [XU FIRST LINE PRINT]. Once the routines contained in the \nOR*3.0*490 patch have been rolled back, the first two lines of the \nRoutines will no longer contain the designation of patch OR*3.0*490 in \nthe patch list section on line 2.\n \nBack-out/Rollback Strategy:\n \n---------------------------\nIn the event of a catastrophic failure, the Facility CIO may make the \ndecision to back-out the patch.\n \nIt is imperative that you have performed a backup of the routines \nincluded in this patch prior to installation.\n \nThe back-out plan is to restore the routines from the backup created.\n \nNo data was modified by this patch installation and, therefore, no \nDialogs Associated:\nrollback strategy is required.\n \nTo verify the back-out completed successfully, ensure the checksum \nmatches the pre-patch checksum from the patch descriptions.\n New/Modified/\nDialog Name Deleted \nis referred to a Community Care provider. Currently, a user creates a new\n----------- -------------\nN/A\n \nForms Associated:\n New/Modified/\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\nN/A\n \nFunctions Associated:\nconsult, then signs the order on the orders tab.\n New/Modified/\nFunction Name Deleted \n------------- -------------\nN/A\n \nHL Logical Link:\n New/Modified/\nHL Logical Name Deleted \n--------------- -------------\nN/A\n \n \nHL7 Application Parameters:\n New/Modified/\nHL7 Parameter Name Deleted \n------------------ -------------\nN/A\n \nHLO Application Registry:\n New/Modified/\nHLO Registry Name Deleted \nThe goal of this project is to automatically sign the consult if the \n----------------- -------------\nN/A\n \nHelp Frames Associated:\n New/Modified/\nHelp Frame Name Deleted \n--------------- -------------\nN/A\n \nMail Groups Associated:\nconsult service name contains -DS or -ADMIN, and the user has the key\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\nN/A\n \nOptions Associated:\n New/Modified/\nOption Name Type Deleted \n----------- ---- -------------\nN/A \n"GMRC ADMIN RBP TO CC", and then send the consult to community care.\n \nParameter Definitions:\n \nParameter Name New/Modified/\n Deleted \n-------------- -------------\nN/A\n \nParameter Template:\n New/Modified/\n \nTemplate Name Deleted \n------------- -------------\nN/A\n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\nN/A\n \n\n
\nINC2101638: Missing Text on "Return to Clinic" Orders\na total of 1 appointment(s)."\n \nResolution: \n----------\n \nModify routine ORWDXM1 to force the user to edit the order which will \ninclude entering a new date. (The same date may be entered for the copied \norder if that complies with procedures to have two "Return to Clinic" \norders for the same clinic and same date.)\n \n \nINC2105632: RTC orders canceled when INTERVAL is zero (0)\n \nProblem:\n--------\n \nWhen a using the VISTA CPRS CLINICIAN MENU option OR OE/RR MENU CLINICIAN \nto place a RTC order and the Number of Appointments is greater than one \n(1), the Interval should not be allowed to be zero (0).\n \nResolution:\nProblem:\n-----------\n \nThe patch modifies the INTERVAL item (OR GTX SCH INTERVAL) for the ORDER \nDIALOG SD RTC in the ORDER DIALOG file (#101.41). The modification makes \nthe INTERVAL a required field when the value of the Number of \nAppointments field is greater than one (1).\n-------\n \nWhen a "Return to Clinic" order is copied, the text "on or around" is \nmissing before the date. Example: The order should state "Return to \nClinic ABC on or around (Sep 24, 2018) for a total of 1 appointment(s)." \nInstead, a copied order will state "Return to Clinic ABC Sep 24, 2018 for \n\n
\nVSR RPC BACKDOOR UPDATES\n\n
\nThe Mental Health Suicide Prevention - Suicide High Risk Patient \n \nThis patch implements the functionality that allows CPRS to display the \nDBRS data stored in VistA Registration database.\nEnhancements (SHRPE) effort incorporates enhancements that will modify the\nVistA Registration application and CPRS.\n \nThe Disruptive Behavior Reporting System (DBRS) record numbers can now be \nrecorded in the Registration (DG) files that are related to Patient Record\nFlags (PRF) which now provides a convenient reference between VistA and \nthe DBRS. The "Patient Record Flags" screen in CPRS is updated to display\nDBRS numbers entered for the patient.\n\n
\nThis patch addresses two issues:\n \n1. The C index in the OE/RR NOTIFICATIONS file (#100.9) contains entries\n for the .01 NAME field.\n \n2. A Lab VBECS component might have a modifier filed when there should be \n no modifier.\n\n
\nThis patch is for NSR20130714 Unified Action Profile\n\n
\nCPRS GUI corrections for Windows 10\n\n
\nOR*3.0*495 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\nThe patch addresses two (2) issues:\n \n1. Lab order checking for order frequency does not occur for future \n orders.\n \n2. Lab order checking for duplicate orders does not occur for future \norders.\n\n
\nThis patch adds the VETERAN VIDEO CALL URL field to the Hospital Location \nfile, Appointment multiple.\n\n
\nMENTAL HEALTH NCC PROJECT 5.01\n\n
\nView Alerts Optimization. Please see OR*3.0*500 Patch Description for \ndetails.\n\n
\nSee the patch description for a full listing of functionality and changes.\n\n
\nPlease see the patch description for OR*3.0*518.\n\n
\nCOVID-19 GUI changes supporting patch.\n\n
\nThis patch is the M side of CPRS GUI v31B. This patch will be distributed \nas part of a multi-package build. Please see the entry in the National \nPatch Module for detailed information about this patch and CPRS GUI v31B.\n\n
\nRefer to the patch description.\n\n
\nSee patch description.\n\n
\nPlease see the NPM on FORUM for the description.\n\n
\nORDER DETAILS DISPLAYING INCORRECT DRUG\n\n
\nIn CPRS, in the Current Order view of the Orders tab a clinical medication\norder that is placed using a quick order and is subsequently edited by\nchanging the drug name, is displayed with a status of dc/edit. This status\nshould not display as the Current Order view should only be displaying\norder statuses of active or pending.\n\n
\nThis patch is being released in conjunction with VBEC 2.3.2 Rev F. \nItems addressed in VBECS 2.3.2 Rev F are listed in the VistA Blood \n ii. Compare Transport Global to Current System - This option\n will allow you to view all changes that will be made when\n this patch is installed. It compares all of the components\n of this patch, such as routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the patch to\n install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion\n of Install? NO//', answer No\nEstablishment Computer Software (VBECS) 2.3.2 Rev F Release Notes.\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//', answer No\n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? NO//', answer No\n \nPost-Installation Instructions:\n N/A\n \n \nBack-Out/Roll Back Plan:\n------------------------\n This patch consists of three routines. During the VistA Installation \n Procedure the installer should back up the modified routines by the\n use of the 'Backup a Transport Global' action (step 2B in\n the Installations Instructions).\n \n If rollback/backout is required, the installer can restore the routines\n using the MailMan message that were saved prior to installing the\n patch.\nAssociated ticket(s):\n \n If assistance is needed to rollback/backout the patch, please log a \n Service Now ticket.\n=====================\n N/A\n \nAssociated NSR(s):\n==================\n N/A\n \n \nPatient Safety Issues (PSIs):\n============================\n N/A\n \nParticipating Test Sites:\n=========================\n \nTBD\n \nA full description of patch changes and implementation process are \nDefect Tracking System Ticket(s) & Overview:\n============================================\n \nn/a\n \nAdditional Information:\n-----------------------\n \nBlood Bank Team Coordination:\n-----------------------------\nincluded in the VBECS 2.3.2 Rev F Release Notes.\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*535 does not \ncontain any changes to the VISTA BLOOD BANK Software as defined by \nProPath standard titled: BBM Team Review of VistA Patches.\n \nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*535 does not \nalter or modify any software design safeguards or safety critical \nelements functions.\n \nRISK ANALYSIS: Changes made by patch LR*5.2*535 have no adverse effect on \nBlood Bank software functionality, therefore RISK is none.\n \n \nVALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes \nmade, no specific validation requirements exist as a result of \ninstallation of this patch.\n \nSoftware and Documentation Retrieval Instructions:\n \nDocumentation describing the new functionality introduced by this patch \nis available on the VA Software Documentation Library at:\nhttp://www.domain.ext/vdl/application.asp?appid=182\nThe Test and Production accounts will be installed separately. There is \n \nRefer to the VBECS 2.3.2 Rev F Release Notes for a list of the user \ndocumentation associated with this revision letter patch.\n \nAdditional VBECS information can be accessed on the VBECS SharePoint site \nat:\nhttps://dvagov.sharepoint.com/sites/oitepmovbecs\n \n \nPatch Installation:\nno downtime associated with this patch installation. Refer to the VBECS \n-------------------\n \nPre-Installation Instructions:\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \nNo options need to be disabled during installation.\n \n2.3.2 Rev F Release Notes for further installation details.\n \nInstallation Instructions:\n \n 1. Choose the PackMan message containing this build. Then select the\n INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n 2. From the Kernel Installation and Distribution System Menu, select the\n Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global option to confirm \n \n the integrity of the routines that are in the transport global.\n When prompted for the INSTALL NAME enter the patch name OR*3.0*527.\n \n B. Select the Backup a Transport Global option to create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates. \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n\n
\nThis patch addresses two (2) issues:\n1. The "Display the Notifications a User Can Receive" option does not \n display the ORB PROCESSING FLAG parameter edits based on Team.\n2. Results might erroneously flag as "critical" in two CPRS reports on \n the Labs tab.\n\n
\nClinically indicated date is changing when using T+XXX or +XXX function.\n\n
\nSee patch description for information regarding modifications.\n\n
\nThe purpose of this patch is to swap the display of Imperial and Metric \nmeasurements on the CPRS coversheet display of Vitals. See the patch for \na full description.\n\n
\nThis patch corrects the following issue:\n \nIf lengthy drug-drug interaction message is transmitted to a remote email \naddress, a buffer error might occur and stall MailMan transmissions.\n\n
\nPlease see OR*3.0*476 Patch Description for more info.\n\n
\nThe patch modifies OR routine "OROTHCL" and RPC "OROTHCL GET" to update\nThere are no actual code changes made to these components.\nthe comments and description to indicate that this code and RPC, in\naddition to Other Than Honorable (OTH), will display the following\ninformation on the CPRS button at the top of the screen and in the\nassociated pop-up window:\n- Presumptive Psychosis (PP) status based on the settings in the PATIENT\n file (#2) and in the INSURANCE VERIFICATION PROCESSOR file (#355.33) \n- Inactive Patient Record Flags (PRF) assigned to the patient and a\n history of PRF changes. \n\n
\nBackup of OR*3.0*545 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issue:\n \nThe order check message might not be accurate when signing a Clinic\nInfusion order.\n\n
\nBackup of OR*3.0*544 on Apr 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the issue of a hard M error during the patient look \nup using the last 5 digits of the social security number or the last \nletter of the last name and the last 5 digits of the social security \nnumber.\n\n
\nBackup of OR*3.0*529 on Apr 27, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the patch description for OR*3.0*529 for more information.\n\n
\nBackup of OR*3.0*542 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n \nThe patch modifies the ORPRF routine and adds a new ORPRFHST routine to \ndisplay the history of active patient records flags in a pop-up window \nassociated with the Flag button in CPRS.\n\n
\nBackup of PCE STANDARDIZATION 1.0, PX*1.0*211, PXRM*2.0*42, GMT\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nTo take full advantage of the PCE standardization work, changes to VistA\nStandardization 1.0 Installation Guide.\n\nIn the documentation for DATA2PCE the description of the variable PPEDIT,\nwhich is one of the input parameters to DATA2PCE is:\n\nPPEDIT\n(Optional) If an existing encounter already has a Primary Provider and you\nwant to edit it set this to 1.\n\nAlthough it was documented, DATA2PCE did not actually enforce this, the\napplications that use PCE data are required. These applications include\nprimary provider could be edited even when PPEDIT did not equal 1. DATA2PCE\nwas changed in PX*1.0*211 to work as documented. After that change, internal\ntesting found that the primary provider could no longer be edited from CPRS.\nThe cause of this was tracked to the way CPRS was calling DATA2PCE, it was not\nproperly passing the PPEDIT parameter. The call to DATA2PCE in the routine\nORWPCE1 was corrected. \n\nClinical Reminders, Health Summary, Problem List, and Order Entry/Results\nReporting. To make it easier for sites, the builds for PCE (PX*1.0*211),\nClinical Reminders (PXRM*2.0*42), Health Summary (GMTS*2.7*122), Problem List\n(GMPL*2.0*53), and Order Entry/Results Reporting (OR*3.0*501) are being\ndistributed in a multi-package build named PCE STANDARDIZATION 1.0.\n\nFor detailed information and installation instructions, please see the PCE\n\n
\nBackup of OR*3.0*550 on May 06, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n1. PDMP AoD Health Summary not always displaying manual PDMP notes \n on the HS report, even though they were documented in the PDMP progress\n note.\n \n Resolution:\n ----------\n Routine ORPDMPHS is modified to not quit when the patient has no data \n in the PDMP QUERY LOG (#101.62). Instead, processing will bypass\n displaying the data in PDMP QUERY LOG when no data exists for the\n patient and allowing the data for manually entered PDMP notes to be\n displayed.\n \n Problem:\n -------\n The PDMP ADHOC Health Summary report is supposed to display PDMP \n queries that were initiated from within CPRS as well as manual queries\n (if the manual PDMP query was documented in the standard PDMP progress\n note). However, if a patient never had a query initiated within CPRS\n (by using the PDMP query button), their manual queries are not showing\n\n
\nBackup of OR*3.0*548 on Jun 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issue:\n1. INC16882015 - Inactivated orderable items can be selected in the \noption Enter/edit QO restrictions\n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. Inactivated orderable items can be selected in the option \nEnter/edit QO restrictions \n \n Problem:\n -------\n1. Inactivated orderable items can be selected in the option Enter/edit \n Inactivated pharmacy or lab orderable items can be selected when using \n the option Enter/edit QO restrictions. It was also found that the 'SR\n Search/replace orderables' option also displays inactive Orderable \n Items to replace orderable items.\n \n \n Resolution:\n ----------\n Routine ORCMEDT6 is modified to display that inactive Orderable Items \n (OI) are inactive. It will also display that inactive OIs are\nQO restrictions\n inactive on the 'Search for:' and 'Replace with:' prompts in option\n Search/replace orderables.\n \n \nAssociated ticket(s):\n=====================\n \n\n
\nBackup of OR*3.0*557 on Jun 10, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee patch description for full details.\n\n
\nSee patch description for OR*3.0*547.\n\n
\nBackup of OR*3.0*556 on Jul 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issue:\n \nIf an order dialog is defined containing more than one prompt having the \nsame "ID", information might not be stored when placing the order and/or \na software error might occur in CPRS.\n\n
\nBackup of OR*3.0*553 on Jul 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of OR*3.0*453 on Jul 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nProvider Role Tool changes. For detailed information, please refer to the \npatch description.\n\n
\nBackup of OR*3.0*560 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe purpose of this patch is to revert the functionality for showing \nmetrics Vitals first on the coversheet. See the patch description for a \nfull description.\n\n
\nPlease see the patch description for information about this build.\n\n
\nCare Management Decommission - Removes code from CPRS for Care\nmanagement.\n\n
\n1. INC18693308 - CPRS NOW DOSE ISSUE IN CLINIC INFUSIONS\nmedications (BCMA for outpatients, unit dose) as well as IVs for non-BCMA \nunits but appears broke in clinic infusions.\n \n Resolution:\n ----------\nRoutine ORCSEND is modified to allow order dialog 'CLINIC OR PAT FLUID \nOE' to work the same as dialog 'PSJI OR PAT FLUID OE' when determining if \nPSJI^ORCSEND3 should be executed. After this patch, when an order that \nis for package PSJ and uses DIALOG 'CLINIC OR PAT FLUID OE' processing \nwill continue through PSJI^ORCSEND3 and the NOW order will be created \n \nwhen signing of the order.\n Problem:\n -------\nIn CPRS, when using the clinic infusions (BCMA for outpatients, IV) \nordering pathway, when ordering an IV and then clicking the "give \nadditional dose now" button, upon signing the order the now dose never \nactually gets ordered. \nThis is a glitch in the system. This "now" function works in clinic \n\n
\nThis patch addresses the following issue:\n \nThe prompts of an existing order dialog cannot be edited after the\ninstall of OR*3.0*556.\n\n
\nAdd ORAM as an Additional Prefix in the Package file entry for ORDER \nENTRY/RESULTS REPORTING.\n\n
\nSee patch description for full information.\n\n
\nThis patch addresses the following issue:\n \nIn the History of Actions Taken section of the Patient Record Flag (PRF) \ndisplay in CPRS, the Site ID should reflect the STATION NUMBER (#99) \nfield of the INSTITUTION (#4) file, not the internal entry number.\n\n
\nDefect Tracking System Ticket(s) & Overview:\nCPRS, the medication is not showing in BCMA as being nurse verified. In \nBCMA, after being nurse verified, the medication is still showing *** in \nthe Ver column of the Coversheet, Unit Dose, and IV tabs.\n \nResolution:\n-----------\nThe issue is due to not sending an HL7 message for nurse verification. \nThis occurs because the processing quits out when the order action is not \na change (XX) or new (NW). When the medication has put on hold and then \nreleased off hold, the action of the nurse to verify it is a Release Hold \n \n(RL) action and fails to continue to the code that sends the message. \nThe correction is to modify routine ORCSEND to move the quit logic to \nafter the message is sent for the pharmacy package.\n \nTechnical Resolution:\n---------------------\nRoutine ORCSEND is modified to move the quit logic and conditionally call \nVER^ORMBLDPS for package PS only when the action is NW, XX, or RL.\n \nThe quit in line VR+6^ORCSEND is commented out, that quit is then added \n1. INC19397308 - MEDICATION RELEASED FROM HOLD NOT SHOWING NURSE \nafter line VR+9^ORCSEND. Line VR+9^ORCSEND is changed from 'I \n$$NMSP^ORCD(ORPKG)="PS" D VER^ORMBLDPS(ORIFN) Q' to 'I \n$$NMSP^ORCD(ORPKG)="PS"&(ORX="NW!(ORX="XX")!(ORX="RL")) D \nVER^ORMBLDPS(ORIFN) Q'\n VERIFIED IN BCMA\n \n \nProblem:\n--------\nAfter a medication is released from hold and is verified by a nurse in \n\n
\nSee the patch description for full information.\n\n
\nThis patch addresses the following issue:\n \n \n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. CPRS - Wrong Message on Cancelled Order.\n \n Problem:\n -------\nIn CPRS, placed an order and then cancelled it. Attempt to sign the \n1. CPRS - Wrong Message on Cancelled Order\norder and you'll get the message "order has been signed". The reason \nshould say, this order has been cancelled.\n \n Resolution:\n ----------\nModify routine ORCACT01 so display the message "This order has been \ncanceled!" when the SIGNATURE STATUS for the ORDER ACTION sub record of \nthe order being signed is 5. \n \n Technical Resolution:\n \n ---------------------\nThe value of 5 for the SIGNATURE STATUS field is 'NOT REQUIRED due to \ncancel/lapse'. At line ES+7^ORCACT01 add code:\nI X=5 S ERROR="This order has been canceled!" Q ;p580\n \nAssociated ticket(s):\n=====================\n \n1. INC20497278 - CPRS - Wrong Message on Cancelled Order\n\n
\nThis patch addresses the following issue:\n \nDuplicate order checking might display an incorrect dispense drug against \npending clinic medications.\n\n
\nThis patch addresses the following issue:\n \nWhen viewing Laboratory result alerts in CPRS and VistA as well as on\nsome CPRS Laboratory reports, abnormal flags display next to test results\nwith no spacing between the results and flags. (Example: POSITIVEH)\n\n
\nThe purpose of this patch is to export the report for patient \ndemographics, along with the supporting code, to add self identified \ngender. See the patch description for a full descriptions.\n\n
\nThis patch is part of a combined build, made up of the following nine \n PXRM*2.0*65 Reminder changes for VIMM\n TIU*1.0*289 CPRS V32 MODIFICATIONS\n PSJ*5.0*399 CPRS32 - INDICATIONS\n YS*5.01*211 CPRS V32B MENTAL HEALTH DLL\npatches:\n \n GMRA*4.0*51 SUPPORT FOR CPRS V32\n GMTS*2.7*115 SUPPORT FOR CPRS V32\n OR*3.0*405 CPRS V32\n PSB*3.0*93 CPRS V32 BCMA CHANGES\n PSO*7.0*441 PARK-A-PRESCRIPTION MODIFICATIONS\n PX*1.0*217 Immunization Calculation Engine (ICE) interface\n\n
\nSee description on patch message.\n\n
\nThe Health Data Repository (HDR) system will now require the 'client \nname' field to be populated for all requests. The purpose of this patch \nis to add this information to the requests sent from the Order \nEntry/Results Reporting package to HDR. These requests are necessary for \nperforming functions such as remote order checking on outpatient \nprescriptions and allergies.\n\n
\nThis patch will correct a <SUBSCRIPT>RESETID+7^ORCDPS error that can\noccur while editing quick orders while using the Update Meds Quick\nOrders for indication prompt [ORCM UPD INDICATION QO] option.\n\n
\nThis patch will temporarily remove the requirement for indication. This \nshould only impact copy to new order actions.\n\n
\nEmergency GUI release. Please see the patch description for the full \ninformation.\n\n
\nPlease see FORUM for a complete description of OR*3.0*596.\n\n
\nThis patch addresses four defects, please look to the patch description\nfor specific technical details.\n\n
\nThe purpose of this build is to revert ORMPS2. See the patch description \nfor additional information.\n\n
\nPlease refer to the patch description for detailed information about the \ncontents.\n\n
\nSee FORUM for patch description.\n\n
\nSee FORUM for patch description details.\n\n
\nThis patch address the following issue:\n \nMOCHA duplicate order check displaying "UNRELEASED" on a released \nprescription (Active, Discontinued, etc.), which is misleading.\n \nSee the patch description for additional information.\n\n
\nThe patch addresses two (2) issues\n \n1. Reformat complications message, removing embedded line breaks in\nmessage text that caused lower portion to be obscured\n \n2. Update AntiCoagulate Splash Screen with features added to CPRS Splash\nScreen\n\n
\nDescription:\n \nInstallation Instructions:\n \n1. Choose the PackMan message containing this build. Then select \n the INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n2. From the Kernel Installation and Distribution System Menu, \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \nThis patch addresses the following issues:\n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter the patch name. \n (OR*3.0*603)\n \n NOTE: Using <spacebar><enter> will not bring up a \n Multi-Package build even if it was loaded \n immediately before this step. It will only \n bring up the last patch in the build.\n \n \n B. Select the Backup a Transport Global option to create\n a backup message. You must use this option and specify \n what to backup; the entire Build or just Routines.\n The backup message can be used to restore the routines\n and components of the build to the pre-patch condition.\n \n i. At the Installation option menu, select Backup \n a Transport Global.\n ii. At the Select INSTALL NAME prompt, enter your \n build OR*3.0*603.\n1. In CPRS, the action of "Change Release Event" can be done on clinic\n iii. When prompted for the following, enter "R" for \n Routines or "B" for Build.\n \n Select one of the following:\n \n B Build\n R Routines\n \n Enter response: Build\n \nmedications.\n iv. When prompted "Do you wish to secure your build? \n NO//", press <enter> and take the default response \n of "NO".\n v. When prompted with, "Send mail to: Last name, First \n Name", press <enter> to take default recipient. Add \n any additional recipients.\n vi. When prompted with "Select basket to send to: IN//", \n press <enter> and take the default IN mailbox or select \n a different mailbox.\n \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n all of the components of this patch, such as \n routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the \n2. In CPRS, Lab Overview (Collected Specimen) results are returned in \n patch to install. \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//', answer NO.\n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \n install? NO//', answer NO.\n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//', answer NO.\nwrong sort order by collection dates.\n \n\n
\nThis patch will address the following issue: \n \nIt was reported that when a provider ordered acetaminophen IV and then\nordered PO, a duplicate drug therapy alert did not populate (HITPS-10794).\n\n
\nThis patch addresses three issues:\n1. IV order admin time editing not going to CPRS.\n2. Add new override reason.\n3. Corrected the spelling of 'UDPATE' to 'UPDATE' in the parameter 'ORWPCE\nASK ENCOUNTER UPDATE' in the field 'VALUE TERM'.\n \nFor additional information, please see the patch description.\n\n
\nThe Purpose of this patch is to address VIA OR Consult Error. This is \nerror is causing VistA to crash. The error is due to improper use of the \nconsult Remote procedure (RPC) by not passing a Patient record number \nDFN. Without a DFN the program crashes causing errors in VistA. This \nerror is being called when the consult tab is being shown when a patient \nisn't selected. It will tell the use that they are missing DFN\n\n
\nMultidivisional sites have requested that the list of lab tests shown in \nthe Lab Test and Anatomic Pathology order dialogs is filtered. After \ninstallation of this patch, tests that are associated with one or more \ninstitutions/divisions are only shown to users who are logged in to one \nof those institutions/divisions. This will prevent users from ordering a \ntest that cannot be processed at their local facility.\n \nRefer to the patch description for full details.\n\n
\nThis patch will address the following issue: \n \nCancelling an unsigned order in the Computerized Patient Record System\ndoes not record who and when it was cancelled.\n\n
\nThis patch addresses the following issues:\nresults outside of given date range.\n \n1. In CPRS, personal quick order processed a prescription order on an \ninactivated drug for outpatient.\n \n2. In CPRS, Lab Overview, Pending Lab Orders, and Lab Orders (All) Exceed \nMax Occurrence Limit.\n \n3. In CPRS, Lab Overview, Pending Lab Orders, and Lab Orders (All) return \n\n
\nThis will release a new context menu for the SalesForce CRM application.\n\n
\nThis patch introduces the following modifications:\n \n3. The Care Management Package has been decommissioned. There are\nremaining API calls to Care Management routines in the Order\nEntry/Results Reporting (OE/RR) package. This patch removes those API\ncalls.\n \n4. It adds a new option to allow sites to edit the ORDER CHECK OVERRIDE\nREASONS (#100.04) file.\n \n5. It corrects the display of the patient's name in the View Patient\n \nNotifications alert detail dialog.\n \n6. It corrects an Integration Control Registrations (ICR) documentation\nissue recently discovered during development activities.\n \n7. It adds a new entry to the ORDER CHECK OVERRIDE REASONS (#100.04)\nfile.\n1. This patch creates a new Glucophage/Metformin Order Check that uses an\nestimated Glomerular Filtration Rate (eGFR) calculation instead of using\nthe Serum Creatinine as the current Order Check does.\n \n2. A problem was discovered in the Computerized Patient Record System\n(CPRS) v31b release with the display of ordering providers in the alert\nlist. This patch will correct this issue.\n\n
\nPlease see OR*3.0*628 on FORUM for a complete description.\n\n
\nPlease refer to the patch description for detailed information about this \nrelease.\n\n
\nCreate a report to display OTP Medication Dispense information.\n\n
\n \nThis patch addresses the following issues:\n1.INC30866117- VISTAOR-36875 -Mumps error <UNDEFINED>RMK^DGRPD\n2.INC26012459- VISTAOR-33839 -Mumps error SUBSCRIPT>ACT+3^ORQ20\n3.INC28417583- VISTAOR-35385 -Mumps error <UNDEFINED>RPT+14^ORWRP\n4.INC25496568- VISTAOR-35194 -Unable to print from CPRS\n\n
\nBackup of OR*3.0*535 on Oct 30, 2024\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issues:\nnot displaying correct information\n \n1. INC26544844 - Provider Role Tool transfers an order but the \nORDER REQUIRES ELEC SIGNATURE\nnotification sent by Audio RENEWAL goes to original provider\n \n2. INC17990929 - CPRS Provider NPI Display Issue\n \n3. INC30979000 - ORB3 RECIP NOTIFICATIONS\n\n
\nThis patch, along with other patches, adds Pharmacogenomic (PGx) order\nchecking to medication orders entered through Inpatient Medications,\nOutpatient Pharmacy and Computerized Patient Record System (CPRS). A \npatient's genomic test results will be retrieved from the Health Data\nRepository (HDR), and along with the prospective drug(s) of a medication\norder is sent to the vendor to retrieve interactions between the patient's\ngenes and the prospective drug(s).\n\n
\nSee description on patch message.\n\n
\nSee National Patch Module for description of this patch OR*3*40.\n\n
\nSee national patch module for description of this patch.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis patch corrects a problem of getting a Null Subscript error when\nprinting orders that have no order text.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis patch filters inactive providers and inactive wards from team\nselection lists during team list maintenance.\n\n
\n \n \nCorrects dialogs in FH\n\n
\nThis patch removes several unused fields from the OE/RR NOTIFICATIONS file\n(#100.9). See the National Patch Module on FORUM for more details on this\npatch.\n\n
\nOR*3.0*10 See National Patch Module for a description of the changes\nincorporated in this patch.\n\n
\nRefer to the patch description on the patch message.\n\n
\nPlease see the patch module on forum for a complete description of\nthis patch.\n \nThe patch tracker message on forum is message number 29329466.\n\n
\nThis patch is a multi-build to address problems with date/time consistency\nRMPR*3.0*54\nGMRC*3.0*19\nas a result of changes implemented in patch HL*1.6*66. This patch will\ninclude the following builds. Please see the individual patch\ndescriptions for more detail regarding the changes made.\n \nOR*3.0*97\nGMRA*4.0*16\nFH*5.0*28\nLR*5.2*265\n\n
\nPatch OR*3.0*92 changed the location where order text is saved. This\npatch will update two entries in the OE/RR PRINT FIELDS file to\naccommodate this new location.\n\n
\nRefer to the patch description on the patch message.\n\n
\nRefer to the patch description on the patch message.\n\n
\nThis patch distributes the CPRS Performance monitor report. This report\nis styled after a report developed by VISN 19. Please see the patch\ndescription on FORUM for a detailed description of this report.\n\n
\nThis build contains Order Entry/Results Reporting version 3.0. It\nis exported as part of the release of CPRS.\n\n
\n This MailMan patch is in KIDS format. Please make sure you follow the\n Nois: ISW-1195-21138, LEX-0895-42101.\n-Fixes undefined error in screening logic, Nois: WIM-0196-20064,\n LAS-1295-61714.\n-The Copy action will now work on a patch in KIDS format.\n-The Copy action will also copy the date/time of the responses to a\n message. E3R 7877\n \n===========================================================================\n This patch should be installed after hours, when there is minimum users on\n the system. You should put the XMUSER Option out of order.\n Installation instructions. This patch contains the following features:\n \n===========================================================================\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'.\n 4. The patch has now been loaded into a Transport global on your\n\n system. You now need to use KIDS to install the Transport global.\n 5. On the KIDS menu, under the 'Installation' menu, use the option \n 'Verify Checksum in Transport Global' and verify that all routines\n have the correct checksums.\n 6. On the KIDS menu, under the 'Installation' menu, use the option \n 'Install Package(s)'. Select the package 'XM*7.1*24' and proceed\n with install.\n 7. Answer YES to the question:\n 'Want to DISABLE Scheduled Options and Menu Options?'\n 8. Enter XMUSER at the question:\n-PackMan will now be KIDS aware. Patches created after Kernel patch\n 'Enter options you wish to mark as 'Out Of Order':'\n 9. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'.\n 10. AXP Sites, after patch has installed, rebuild your map set.\n ==================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n XU*8*21 is installed will be able to use Summarize, Print, and Text Print\n Name Checksum Patch List\n ----------------------------------------------------------\n XMA2C0 8936155 24\n XMA7G1 1193700 24\n XMAD1 7085638 24\n XMAP 8812311 24\n XMB 7281814 3,7,24\n XMBPOST 6164025 4,13,23,24\n XMP 8440919 4,24\n XMP2 9454113 24\n options of PackMan. Nois: MAC-1095-60621, ISA-0595-10416.\n XMP2A 9900587 24\n XMP3 7025241 24\n \n\n =====================================================================\n DATA DICTIONARY:\n\n A new code was added to the MESSAGE TYPE field (Set of Codes);\n K for KIDS Distribution.\n\n-You can now '^' out of the Print Message option in PackMan, Nois:\n FILE: MESSAGE #3.9\n FIELD: MESSAGE TYPE #1.7\n\n CHY-0595-50665.\n-Corrects allocation error when XMTEXT is to large and passed to XMB.\n\n
\n This MailMan patch is in response to the following:\nMGY-1295-31820 Postmaster will no longer put messages in its waste basket.\n The messages will be deleted.\n\nFNC-1196-32114 XMAUTOPURGE get no open error when queued.\n===========================================================================\n This patch should be installed during off-peak hours when network mail\n activity is low. This patch can be installed with users on the system.\n===========================================================================\n \nINSTALLATION:\nANN-1196-40100 Packman will now halt properly when an error is found in\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n a routine it is trying to transport.\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \n ROUTINES:\n The second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\n XMPH 4682271 4842981 34\n XMR 6434522 6876928 30,34\n XMR0B 9731612 9558225 4,6,13,34\n XMRUCX 338699 357201 27,34\n XMS 5986074 5910151 8,20,34\nBRX-1295-11486, AUG-0796-31857, FTM-0296-42025 Mailman now keeps track of\n XMS0 9449052 9445201 13,8,20,23,27,34\n XMUT4A 4333719 4382977 34\n============================================================================\n DATA DICTIONARY: Partial DD\n\n File: DOMAIN #4.2\n\n Field:\n 1.61 NEW VALIDATION NUMBER\n This field is used for security. It is a temporary value,\n the old and new Validations number. If the link breaks before a site\n it is set when a new validation number is negotiated with\n another Domain. It is moved to the Validation Number,\n field 1.6, after it is confirmed by the other Domain.\n\n receives a new Val. number, MM will allow the old number next time the\n site reconnects.\n\n\n
\nPatch XM*7.1*129\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMR1 14522719 14463657 7,50,94,107,123,129\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*123.\n1. Users may be on the system during installation of this patch.\nNOIS: MAD-0500-41856\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Madison, WI\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*129 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIf a message with no text is received from a remote site, accept it, instead\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nof aborting.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*123.\n\n
\nPatch XM*7.1*130\nTest Site: Bronx, NY\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nAllow anyone to forward a priority message to a mail group, if the site\nso chooses. A new field has been added to file 4.3, MAILMAN SITE PARAMETERS,\nand option XMKSP, MailMan Site Parameters, has been updated to include it.\nHere's the new field:\n\nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\nSTORED IN ^XMB(1, (1 ENTRY)\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n\n-----------------------------------------------------------------------------\n4.3,21 FORWARD PRIORITY MAIL TO GROUP 2;1 SET\n\n '0' FOR NO; \n '1' FOR YES; \n HELP-PROMPT: Let users forward priority messages to mail\n groups? \n DESCRIPTION: Enter YES is you wish to allow users to forward\n priority messages to mail groups. \n \nNOIS: MON-1099-51059, HOU-0100-72381\n Enter NO if you don't. (This is the default.) \n Then only the message originator or anyone with\n the XM GROUP PRIORITY key may forward priority\n messages to mail groups. \n\n*Note: If you do nothing with this new field, then this patch will not\nchange MailMan's behavior with regard to the forwarding of priority messages.\nOnly if you answer YES will the behavior change as described above.\n\nE3R: 7137\nTest Site: Montana HCS\nTest Site: Bronx, NY\nImprove QD searches to deal with a mixture of upper and lower case.\n\nE3R: 7506\nTest Site: Bronx, NY\nAdd institution and title info to Help:User Information. Such info will\nbe displayed if it exists and if the user's and site's preferences are set\nto display them.\n\nNOTE: This patch should be installed during off hours, when user activity\nWhen creating a PackMan message, and you decide to abort it while selecting\nis at a minimum. It requires MailMan patches XM*7.1*110, XM*7.1*120,\nand XM*7.1*128.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\nrecipients, MailMan ignores you and continues on. MailMan has now been\n--------------------------------------------------------------\nXMHIU 8274187 8325597 50,107,128,130\nXMJMQ1 7395902 7972269 40,50,110,130\nXMJMS 5639134 5873945 50,120,130\nXMXSEC1 11938650 12141474 50,95,110,130\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \ntaught to listen better.\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*110, XM*7.1*120,\nand XM*7.1*128.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*130 Loaded from Distribution <date/time>\n ==========\nE3R: 3029, 6336, 7402\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n
\nPatch XM*7.1*134\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMP 15950247 16023439 50,75,100,110,127,134\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*127.\n1. Users may be on the system during installation of this patch.\nNOIS: ISW-0600-22431\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: OIFO Washington\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*134 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIf you try to print the last response of a message, the whole message is\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nprinted by mistake. This patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*127.\n\n
\nPatch XM*7.1*133\nIf a message has been latered, indicate it in the header when displaying\nthe message.\n\nE3R 4975\nTest Site: Biloxi, MS\nIf a reply to a message from a remote site stayed local, make it clear in the\nreply header when displaying it.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\n\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMP1 16386050 17261262 40,50,75,110,133\nNOIS FAR-0600-41904\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\n1. Users may be on the system during installation of this patch.\nTest Site: Fargo, ND\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nDon't abort when printing a message with a response missing from the response\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*133 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nmultiple.\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nE3R 2479\nTest Site: Biloxi, MS\n\n
\nPatch XM*7.1*132\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMXREPLY 5648876 5876870 50,85,99,107,132\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: BRX-\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: Bronx, NY\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*132 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nWhen a user replies to a scrambled message from a remote site and sends it\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nover the network, an "undefined" error occurs. This patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n\n
\nPatch XM*7.1*138\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMXADDR1 11852631 12529716 50,78,83,96,104,107,127,138\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*127.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: DUB-0700-30004\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: Dublin, GA\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*138 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nAvoid infinite loop if Remote User Directory has local users in it.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*127.\n============================================================================ \n\n
\nPatch XM*7.1*139\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMXADDR3 6636062 8018411 107,139\nXMXADDRG 15011724 14977775 50,99,107,139\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n1. Users may be on the system during installation of this patch.\nNOIS: MON-0799-52993\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Montana HCS\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*139 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIgnore upper/lower case differences when minusing remote recipient addressees.\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n============================================================================ \n\n
\nPatch XM*7.1*137\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMD 9220624 9221858 50,104,110,137\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*110.\n1. Users may be on the system during installation of this patch.\nNOIS: BRX-0600-12672\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: BRONX\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*137 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nAvoid abort if message number is missing from 'latered messages' record\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nduring 'latered messages' report.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\n\n
\nPatch XM*7.1*131\nAdd status line showing number of new messages in new message list.\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJBM 10706426 10732311 50,110,131\nXMJMFA 6600695 6784168 50,110,131\nXMJMFB 15590623 15929930 50,110,131\n\nXMJML 11033330 11937833 50,131\nXMJMLN 13840736 14755647 50,110,131\nXMJMLR 14100278 14200855 50,110,131\nXMJMOI 17925576 18181531 50,87,89,110,127,131\nXMJMOR 13211462 14599384 50,75,110,131\nXMJMORX 14207041 15388148 50,110,131\nXMJMQ 15891582 15971466 40,57,70,50,96,110,131\nXMJMQ1 7972269 8577594 40,50,110,130,131\nXMJMSO 8232068 8539565 50,110,127,131\nXMVGROUP 6851604 7521910 50,104,107,131\nE3R 2404\nXMXADDR 14565832 15038029 50,96,101,104,107,131\nXMXAPI 6992361 7362843 50,110,131\nXMXMSGS 9944188 10394514 50,110,124,131\nXMXMSGS2 7381168 7750414 50,106,110,127,131\nXMXPARM 14291441 15160844 50,96,107,127,131\nXMXSEC1 12141474 12312603 50,95,110,130,131\nXMXUTIL 11858021 12222792 40,50,107,127,131\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nTest Site: Biloxi, MS\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*107, XM*7.1*124,\nXM*7.1*127, and XM*7.1*130.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nIf a message is broadcast, then prompt sender for a vaporize date, if one\n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nhasn't already been supplied.\n Select INSTALL NAME: XM*7.1*131 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nE3R 3417\nTest Site: Biloxi, MS\nAdd an option to vaporize groups of messages.\n\nRelated help frames have been updated, and a new help frame,\nXM-U-M-VAPORIZE EDIT-2, has been added.\nA new API, VAPORMSG^XMXAPI, has been added.\n\nE3R 6215\nTest Site: Biloxi, MS\nList broadcast recipients first during Q or QD.\n\nE3R 14211\nTest Site: Palo Alto, CA\nNOIS TAM-0700-30683\nLet site decide whether or not to let a user drop out of a non-self-enrolling\nmail group. A new field has been added to file 4.3, MAILMAN SITE PARAMETERS,\nand option XMKSP has been updated to include it. Here's the new field:\n\nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\nSTORED IN ^XMB(1, (1 ENTRY) (VERSION 7.1)\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\nTest Site: Tampa, FL\n4.3,22 DROP OUT OF RESTRICTED GROUP 2;2 SET\n \n '0' FOR NO;\n '1' FOR YES;\n LAST EDITED: JUN 06, 2000\n HELP-PROMPT: Let users drop out of non-self-enrolling mail\n groups?\n DESCRIPTION: Enter YES if you wish to allow users to drop\n out of non-self-enrolling mail groups. The\n users will be warned that this is a\nIf you new a message in the WASTE basket, it tells you,\n non-self-enrolling group, and that they won't\n be allowed to rejoin later, and then they will\n be asked to re-confirm the decision to drop out.\n \n Enter NO if you don't. (This is the default.)\n Then users will have to contact IRM or the mail\n group coordinator to ask to be dropped.\n \n TECHNICAL DESCR: If a mail group is not a self-enrolling mail\n group, then users can't just join. They must\n"Message saved to basket." This patch fixes that.\n be added by the mail group coordinator.\n \n If a user no longer wishes to be a member of\n such a group, he must ask the group coordinator\n to drop him. But what if the group coordinator\n has left the organization or is unresponsive?\n Then what? Then the user will have to ask IRM\n to help. This problem can be avoided by\n setting this field to YES.\n \n\n Some would argue that the coordinator added the\n user to the group for a reason, and the user\n should not be allowed to drop out. (Perhaps\n the coordinator is the user's boss.) They\n would argue that it is MailMan's job to prevent\n the user from dropping out. (Set the field to\n NO.) Others would argue that it is not\n MailMan's job at all, but the boss's job to\n prevent the user from dropping out, and to\n discipline the user if he does. (Set the field\nE3R 1305, 4838\n to YES.)\n\n*Note: If you do nothing with this new field, then this patch will not\nchange MailMan's behavior. Users will not be able to drop out of\nnon-self-enrolling mail groups.\n\nAdditionally,\n\nThis patch introduces two more new APIs:\n$$TPMSGCT^XMXUTIL - returns # of new priority messages in a user's mailbox.\nTest Site: Biloxi, MS\n$$BPMSGCT^XMXUTIL - returns # of new priority messages in a user's basket.\n\nThis patch fixes a problem noticed on FORUM that could cause infinite looping\nof error messages from remote sites.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*107, XM*7.1*124,\nXM*7.1*127, and XM*7.1*130.\n============================================================================ \n\n\n
\nPatch XM*7.1*136\nDuring the MESSAGE file integrity check, if a message subject is >65, then\ntruncate it; <3, pad it with "...".\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*108.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMA32A 9900106 9915667 27,37,44,55,50,136\nXMUT4BA 16133058 16544870 50,108,136\nXMUT4C 7571867 7616619 10,22,50,108,136\n\n* Checksums produced by CHECK^XTSUMBLD\n\nNOIS: none\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*108.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: FORUM\n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nExempt from the 'date purge' any messages in the transmit queues or the\n Select INSTALL NAME: XM*7.1*136 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nserver baskets.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOIS: BUT-0600-20499\nTest Site: Butler, PA\n\n
\nWe recommend that you run option XMAUTOPURGE daily to purge your system of\nNOIS: LAK-0396-31177\nThe post-install routine, ^XMYPOST7, will run about 3 minutes per\n1000 mailboxes. See the description above about what it will be doing.\n*NOTE*: It will try to lock ^XMB(3.7). If it cannot lock it, it will not\nrun, and you will have to run it manually at a future time. So if you see\nthat ^XMYPOST7 stopped running as soon as it started, then you know it could\nnot get a lock. \n\n^XMYPOST8 will not run. Do not run it.\n===========================================================================\n \nRtns: ^XMA32,^XMA32A\nINSTALLATION:\n1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the affected routine.\n2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Verify Checksums in Transport Global\nThese "date purge" routines have been changed to\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \nROUTINES:\n- improve efficiency\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA3 11195689 14547045 37\nXMA30 5617809 7561526 37\nXMA31 2140577 1080 27,37\nXMA32 13342847 12437801 37\n- make the coding clearer\nXMA32A 11841830 9601895 27,37\nXMADJF1B 4665477 4754529 10,16,37\nXMDIRRCV 1862431 1909690 37\nXMDIRSND 1508027 1583505 37\nXMYPOST7 **new** 959425 37\nXMYPOST8 **new** 649189 37\n\n============================================================================\n- recognize more internet date formats\n- purge messages which think they are responses but really aren't\n- purge responses which think they are original messages but really aren't\n- recognize and comply with a task stop request\n\nunreferenced messages. It runs approximately 40 minutes per 100,000 messages.\nNOIS: NYN-0996-10302\nRtns: ^XMA3\nDD: file 4.3, field #4.304, 'MESSAGES NOT TO PURGE WEEKDAYS'\nMakes the documentation in the routine and DD match the code in the routine.\n\nNOIS: MIN-0195-40075\nRtns: ^XMA3,^XMA30,^XMA31\nMake sure that messages within the no-purge-days buffer aren't deleted.\n\nNOIS: WBP-0996-22202\nYour mileage may vary.\nRtns: ^XMA3,^XMA30,^XMA31\nDD: file 4.3, new field #142, 'NO-PURGE DAYS BUFFER'\nLets the site specify the no-purge number of days.\nRoutines are modified to improve efficiency and clarity.\n\nSTANDARD DATA DICTIONARY #4.3 -- KERNEL SITE PARAMETERS FILE 11/1/96 PAGE 127\nSTORED IN ^XMB(1, (1 ENTRY) SITE: MAILMAN RELEASED UCI: REL,NMM (VERSION 7.\n1) \n\nDATA NAME GLOBAL DATA\n\nELEMENT TITLE LOCATION TYPE\n-------------------------------------------------------------------------------\n4.3,142 NO-PURGE DAYS BUFFER .14;2 NUMBER\n\n INPUT TRANSFORM: K:+X'=X!(X>10)!(X<1)!(X?.E1"."1N.N) X\n\n LAST EDITED: OCT 08, 1996 \n HELP-PROMPT: Type a Number between 1 and 10, 0 Decimal \n Digits \n DESCRIPTION: This field is used during the\nOption XMSTAT will show you the results of the last 20 purges: purge type,\n un-referenced-messages purge to avoid purging\n the last few messages in the message file,\n according to their send date.\n We subtract the NO-PURGE DAYS BUFFER from\n today's date, giving a 'no-purge date'. Local\n messages which were created on or after that\n date are not subject to purge. Messages from\n other sites are not affected by this buffer. \n If this field is not filled in, it defaults to\n 7 days. One day is probably all that is\nwhen they were run and how long they took, and how many messages were purged.\n needed, however. \n One situation in which this buffer may be\n useful is in the case of a message sent only to\n a remote site. Such a message is unreferenced\n and would otherwise be subject to purge. If a\n reply came from the remote site after the\n original message had been purged, the sender\n would have access only to the reply and not to\n the original message. The NO-PURGE DAYS BUFFER\n could be set to a reasonable number of days to\n\n allow for a reply.\n\nNOIS: WBP-0596-21011\nRtns: ^XMDIRSND,^XMDIRRCV\nDelete Server messages from Postmaster's Mailbox after processing them.\n\nNOIS: MCM-1295-51144\nRtns: ^XMA3\nWhile cleaning out Postmaster's ARRIVING basket, deletes any message which\nis still arriving after 'NO-PURGE DAYS BUFFER' number of days.\nMailMan patch XM*7.1*37 contains the following enhancements and bug fixes:\n\nNOIS: None\nRtns: ^XMADJF1B,^XMYPOST7\nThis problem was revealed during testing of this patch. MailMan does not\nuse FileMan to add messages to a user's basket; he does it himself, and that\nincludes updating the zero node. Up 'til now, when MM delivered a message to\na user's basket, he put the message number (not the number of messages) into\npiece 4 of the zero node of the message multiple. This patch corrects that\nmistake. ^XMYPOST7 goes through all message multiples of everyone's mailbox\nand corrects the message multiple zero nodes.\n\n\nNOIS: DAY-0196-41801\nRtns: ^XMA30\nThe user status report now includes 'last sign on', as well as 'last mail use'.\n\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order. No one should be\nusing MailMan. The filers (mail delivery tasks) should not be running.\n\n\n
\nPatch XM*7.1*141\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMVGROUP 7521910 7972968 50,104,107,131,141\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: CON-0700-12427\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: CONNECTICUT HCS\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*141 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nFix abort when user tries to disenroll from a group.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n============================================================================ \n\n
\nPatch XM*7.1*140\nDATA NAME GLOBAL DATA\n Digits \n DESCRIPTION: When you read new messages by basket, MailMan\n suggests the IN basket to read first. If you\n want MailMan to suggest other basket(s) before \n suggesting the IN basket, then fill in this\n field with a priority order number. MailMan\n will suggest the basket(s) in the priority\n order set by you. The IN basket will be\n suggested last. (You will not be able to\n choose the IN basket.) Once all the priority\nELEMENT TITLE LOCATION TYPE\n baskets have been read, MailMan will suggest\n baskets in alphabetical order. \n CROSS-REFERENCE: 3.701^AP \n 1)= S ^XMB(3.7,DA(1),2,"AP",$E(X,1,30),DA)=""\n 2)= K ^XMB(3.7,DA(1),2,"AP",$E(X,1,30),DA)\n\nAdditionally:\n-When sending or forwarding a message using one of the ^XMD APIs, and there\nare no recipients, XMMG is set to "Error = No recipients." Previously,\nthere was no error message.\n--------------------------------------------------------------------------\n\n-MailMan's version of FileMan's ^DIR 'set of codes' reader has been improved.\nIt now offers selection completion and understands either the code or the\ntext, and asks for clarification if the user enters something ambiguous.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n============================================================================ \n\nROUTINES:\n4.3,23 TITLE SOURCE 0;11 SET\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXM 11416143 10976819 17,35,50,140\nXMD 7425316 7686115 33,50,98,103,107,140\nXMGAPI4 4204061 5089993 50,140\nXMJBM1 4157424 3151843 50,140\n 'S' FOR SIGNATURE BLOCK TITLE; \nXMJBN 10390839 15626783 50,100,140\nXMJBU 1507122 2739459 50,140\nXMJDIR 5974273 6074159 50,110,140\nXMVVITA 4785601 7287397 50,101,110,140\nXMVVITAE 10408258 11186176 50,74,107,140\nXMXUTIL 12222792 12959022 40,50,107,127,131,140\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n 'T' FOR TITLE; \n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n LAST EDITED: JUL 18, 2000 \n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*140 Loaded from Distribution <date/time>\n ==========\n HELP-PROMPT: Where should the user's title come from? \n Checking Install for Package XM*7.1*140\n\n Install Questions for XM*7.1*140\n\n Incoming Files:\n\n 3.7 MAILBOX (Partial Definition)\n Note: You already have the 'MAILBOX' File.\n\n 4.3 MAILMAN SITE PARAMETERS (Partial Definition)\n DESCRIPTION: Where in the NEW PERSON file should the user's\n Note: You already have the 'MAILMAN SITE PARAMETERS' File.\n\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n title come from? \n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\n \n Enter 'S' if the user's title should come from\n field 20.3, SIGNATURE BLOCK TITLE. If that\n field is empty, then we'll try field 8, TITLE. \n \n Enter 'T' if the user's title should come from\n field 8, TITLE. If that field is empty, we\n won't show any title. \n \n The default is 'T', if this field is not filled\nTest Sites: Biloxi, MS; Houston, TX; San Francisco, CA\n in. \n\nE3R 13115\nUsers may choose in which order new messages should be read.\nNew help frames (XM-U-P-OPTIONS-4, XM-U-P-NEW MESSAGES READ ORDER) have been\nadded, and related help frames updated. The following field has been added\nto file 3.7:\nSTANDARD DATA DICTIONARY #3.7 -- MAILBOX FILE\nSTORED IN ^XMB(3.7,\nDATA NAME GLOBAL DATA\n\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n3.7,21 NEW MESSAGES READ ORDER 0;19 SET\n 'N' FOR Newest First; \n 'O' FOR Oldest First; \n LAST EDITED: JUL 19, 2000 \n HELP-PROMPT: In which order do you want to read your new \n messages? \n DESCRIPTION: 'Newest First' means new messages are read in\n reverse order. 'Oldest First' means new\nE3R 12694\n messages are read in the order in which they\n were sent. \n If you don't choose, your new messages will be\n read 'Oldest First'. \n Note: When you display a list of new messages,\n they will be displayed in the order you\n selected in the field 'MESSAGE ORDER'. \n\nE3R 14123\nUsers may choose the default selection to the prompt which appears with\nSites may choose where MailMan gets a user's title. The following field\nthe 'New Messages and Responses' option. A new help frame (XM-U-P-NEW\nMESSAGES OPTION) has been added, and related help frames updated. The\nfollowing field has been added to file 3.7, and is available for editing\nunder 'Personal Preferences|\nUser Options Edit'.\nSTANDARD DATA DICTIONARY #3.7 -- MAILBOX FILE\nSTORED IN ^XMB(3.7,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\nhas been added to file 4.3, and option XMKSP has been updated to include it:\n3.7,20 NEW MESSAGES DEFAULT OPTION 0;18 SET\n 'LB' FOR LIST BASKETS WITH NEW MAIL; \n 'LN' FOR LIST ALL NEW MESSAGES; \n 'P' FOR PRINT ALL NEW MESSAGES; \n 'R' FOR READ NEW MAIL BY BASKET; \n LAST EDITED: JUL 17, 2000 \n HELP-PROMPT: Select default new messages option \n DESCRIPTION: This is the default choice which will appear\n when you select the 'New Messages and\n Responses' option. \nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\n If you don't choose a default, the default will\n be 'Read new mail by basket'. \n\nAlso, when the user chooses to read new mail by basket, the user may have\nbasket(s) other than the IN basket presented as the default basket(s) from\nwhich to read. A new help frame (XM-U-P-READ NEW MSGS BSKT) has been added,\nand related help frames updated. The following field has been added to the\nBASKET subfile of file 3.7, and is available for editing under\n'Personal Preferences|User Options Edit'. \nSTANDARD DATA DICTIONARY #3.7 -- MAILBOX FILE\nSTORED IN ^XMB(1, (1 ENTRY)\nSTANDARD DATA DICTIONARY #3.701 -- BASKET SUB-FILE\nSTORED IN ^XMB(3.7,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n3.701,4 READ NEW MSGS BASKET PRIORITY 0;4 NUMBER\n Read new messages basket priority\n INPUT TRANSFORM: K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X\n LAST EDITED: JUL 19, 2000 \n HELP-PROMPT: Type a Number between 1 and 99, 0 Decimal \n\n
\nPatch XM*7.1*143\nFix an abort which occurred because of typos in parameter checking routine\nfor MailMan APIs.\n\nNOIS: WBP-0100-22822\nTest Site: Wilkes Barre, PA; Dayton, OH\nRemove an errant DIR("B") which was hanging around after MailMan exits and\npopping up in unexpected places elsewhere.\n\nNOIS: none\nTest Site: DOMAIN.EXT\n\nFix an abort which occurred on FORUM because of a badly written $G() command.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \nNOIS: MON-0800-50661\n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJBM 10732311 10627394 50,110,131,143\nXMJMOI 18181531 18282681 50,87,89,110,127,131,143\nXMXMSGS 10394514 10461549 50,110,124,131,143\nXMXMSGS2 7750414 7663790 50,106,110,127,131,143\nXMXPARM 15160844 15143763 50,96,107,127,131,143\n* Checksums produced by CHECK^XTSUMBLD\n\nTest Site: Montana HCS\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nFix logic which results in improper deletion of vaporize date when\n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nbroadcasting a message by forwarding it.\n Select INSTALL NAME: XM*7.1*143 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nNOIS: TAM-0800-30156\nTest Site: Tampa, FL\n\n\nPatch XM*7.1*145\nAlso prevents the following error which may occur during logon and throw\nthe user off the system:\n$ZERROR=NU+12^XMGAPI4:3, %DSM-E-UNDEF, undefined variable Y\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*140.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMGAPI4 5089993 5418259 50,140,145\nXMJBN 15626783 15087232 50,100,140,145\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS: DUB-1299-32692\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*140.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nTest Sites: Danville, IL; Dublin, GA\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*145 Loaded from Distribution <date/time>\nThis patch prevents an abort which occurs when a user parks at the new\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\nmessages menu, starts up another session, reads all his new messages in\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthat other session, and then goes back to the original session and tries\nto continue reading new messages.\n\n\n
\nPatch XM*7.1*144\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*75, XM*7.1*84, and\nXM*7.1*140.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXM 10976819 10981828 17,35,50,140,144\nXMJBL 4523065 5397834 50,144\nXMJDIR 6074159 5458230 50,110,140,144\nXMJERR 454500 375961 50,144\nXMJMBULL 1399629 1994222 50,84,144\nXMJMSA 1939332 1902278 50,144\nXMXMBOX 1289002 1264480 50,144\nNOIS: SFC-0800-62050\nXMXPARMB 4788158 3879548 50,144\nXMXPRT 3044670 3257492 50,75,144\nXMXTO 1915321 1746429 50,144\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nTest Site: San Francisco, CA\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*75, XM*7.1*84, and\nXM*7.1*140.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\nPrevent error which occurs when user enters "query r" at\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*144 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n"Select message action: Ignore//" prompt.\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nE3R 6585\nDo not offer a default subject for anonymous suggestions.\n\n
\nPatch XM*7.1*142\nduplicated field 25, TRANSMISSION TASK#. All routines which reference\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthe phantom field now reference field 25. The pre-init with this patch\nwill set the phantom field for entries in file 4.2999 to null.\n\nThis patch also 'new's the variable ZTSYNC before creating the task to\ntransmit messages to a remote site. (This will prevent "bleeding" of\nSYNC FLAGs used by applications to ensure that tasks are run in sequence,\nand then only if the preceding task completed successfully.)\nSuch SYNC FLAGs are not applicable to MailMan. \n\n\nNOTE: This patch requires MailMan patch XM*7.1*97, XM*7.1*107,\nand XM*7.1*127.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\nTest Site: Tampa, FL\n----------------------------------------------------------\nXMB 4363515 3744054 3,7,24,26,27,50,142\nXMBPOST 9626449 8035121 4,13,23,24,27,38,50,142\nXMC2 12105966 11919093 13,23,27,50,142\nXMKPL 2060011 2875442 50,142\nXMKPLQ 9249196 5786623 50,142\nXMKPO 2606344 3092912 50,142\nXMS0 9308250 9155857 13,8,20,23,27,34,55,50,142\nXMS5 13329767 13300220 13,8,23,27,55,58,50,142\nXMS5B 4006973 4007283 13,23,142\n\nXMTDF 4326406 4390490 50,127,142\nXMTDL 18497319 18718545 50,97,142\nXMTDL1 5049974 4584627 50,107,142\nXMTDT 5385940 5589575 50,142\nXMYPRE8 * NEW * 228290 142\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\nXMYPRE8 has no user callable entry points.\nNOIS: ISB-0700-32092, CMC-1299-30434, CMC-0200-31328, CMH-1199-N1398,\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*97, XM*7.1*107,\nand XM*7.1*127.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n CML-0700-41882, CMP-0700-61026, TAM-0300-33196\n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Stop TaskMan. Shut down the listeners. You may also wish to shut down\n HL7 filers/LLP's and other background tasks which may attempt to create\n new messages. During the installation of this patch, we do not want any\n messages coming in or going out. Users should not be on the system.\nImprove remote transmit process by eliminating the phantom task number\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*142 Loaded from Distribution <date/time>\n ==========\n Install Questions:\nfield in piece 2 of the zero node for entries in file 4.2999.\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// YES\n ===\n Enter options you wish to mark as 'Out Of Order': XMUSER MailMan Menu\n ======\n Enter options you wish to mark as 'Out Of Order': <press return>\n ==============\n Enter protocols you wish to mark as 'Out Of Order': <press return>\n ==============\nThis field is not in the data dictionary, and yet was being used, and\n Delay Install (Minutes): (0-60): 0// <press return>\n ==============\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Start TaskMan. If you shut down HL7 filers/LLP's and other\n background tasks in step 4, be sure to restart them, too.\n\n
\nPatch XM*7.1*147\nmay not be null as an input value. The correction is that MailMan will no\nlonger set XMINSTR("SELF BSKT") to null.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*119.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMKP 16947852 16261814 50,89,119,147\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nNOIS: MIW-0900-41651\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*119.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\nTest Sites: Milwaukee, WI\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*147 Loaded from Distribution <date/time>\n ==========\n Install Questions:\nThis patch corrects an error which may occur in the second and subsequent\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\nusages of SENDMSG^XMXAPI if one of the recipients is the sender of the\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nmessage and the input variable XMINSTR is used, but not newed. \nThe first usage causes XMINSTR("SELF BSKT") to be set to null. The second\nand subsequent usages fail to send the message because XMINSTR("SELF BSKT")\n\n\nPatch XM*7.1*146\nE3R: 8432\n members of the group so that a certain level of comfort is achieved that the\n Super Searches will only be conducted for just cause. The more people there\n are, who are aware that a Super Search has been conducted, the less likely\n it is that the capability will be abused.\n \n The site Information Security Officer should be the coordinator of this\n group.\n\n\nNOTE: This patch should be installed during off hours, when user activity\nTest Site: White River Junction, VT\nis at a minimum. It requires MailMan patches XM*7.1*108, XM*7.1*109,\n& XM*7.1*144.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\nLet authorized users search the Message file for messages based on the same\n-----------------------------------------------------------------\nXMJDIR 5458230 6123825 50,110,140,144,146\nXMJERR 375961 374282 50,144,146\nXMJMF 18005162 3844343 50,146\nXMJMF1 * NEW * 11694773 146\nXMJMF2 * NEW * 6206910 146\nXMJMFA 6784168 6729708 50,110,131,146\nXMJMFB 15929930 16215095 50,110,131,146\nXMJMFC * NEW * 11137057 146\nXMJMOI 18282681 18383177 50,87,89,110,127,131,143,146\nsearch criteria one can use when one is searching for one's own messages.\nXMXAPIG 1672216 1692175 109,146\nXMXLIST 10491222 6225911 50,108,146\nXMXLIST1 12617251 12801864 50,108,146\nXMXLIST2 * NEW * 6802380 146\nXMXPARMB 3879548 3923435 50,144,146\nXMXSEC1 12312603 12986076 50,95,110,130,131,146\nXMXSEC2 27323685 27320982 50,89,95,110\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines. They have no callable\nThe user would be able to search every message.\nentry points:\nXMJMF1\nXMJMF2\nXMJMFC\nXMXLIST2\n\nThis patch introduces the following new APIs:\n$$SSPRIV^XMXSEC1 - Is the user allowed to Super Search?\n$$ZSSPRIV^XMXSEC1 - Is the user allowed to Super Search?\n===========================================================================\nAmong other uses would be the ability to follow up on EEO harassment cases\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*108, XM*7.1*109,\n& XM*7.1*144.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nin which the offending user harassed via MailMan messages.\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*146 Loaded from Distribution <date/time>\n\n ==========\n Install Questions:\n\n Incoming Mail Groups:\n Enter the Coordinator for Mail Group 'XM SUPER SEARCH': <Your site's ISO>\n =================\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nThis patch improves the message search capability.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n- The Postmaster is now able to search the remote transmit queues.\n\n- You are now able to search for messages that have a certain number of\nlines of text or more.\n- You are now able to search the MESSAGE file using all the criteria\navailable when searching your own mailbox.\n- Help frames have been updated, and new help frames have been added to\nreflect the changes.\n- The API LISTMSGS^XMXAPIB has been improved to incorporate the changes, too.\n\nThe following entries have been added to their respective files:\n\nE3R: 3764\nOUTPUT FROM WHAT FILE: 19 OPTION\n(This option has been added to the XMMGR 'Manage MailMan' menu.)\nNAME: XM SUPER SEARCH MENU TEXT: Super Search Message File\n TYPE: run routine CREATOR: BEUSCHEL,GARY\n LOCK: XM SUPER SEARCH PACKAGE: MAILMAN\n DESCRIPTION: This option lets the authorized user (anyone holding the XM\n SUPER SEARCH key) search the Message file for messages meeting any number of\n criteria, no matter who sent the messages.\n \n This option should not be used lightly. One example in which usage is\nTest Site: Biloxi, MS\n justified would be the search for evidence in an EEO harassment case.\n \n This option should be audited to track who uses it.\n \n Every search will trigger the sending of the XM SUPER SEARCH bulletin to the\n XM SUPER SEARCH mail group. The bulletin will record who (DUZ) conducted\n the search and what criteria were used. It will not record the results of\n the search.\n \n The XM SUPER SEARCH mail group must have at least two active local users in\nLet the user search the Message file for messages using the same criteria\n it who have logged on recently. If it doesn't, the search will not be\n performed. Members of this mail group should be anyone whose responsibility\n it is to ensure that security is maintained and privileges are not abused.\n The mail group coordinator should be the site's Information Security Officer\n or another responsible individual.\n ROUTINE: SUPER^XMJMF\n UPPERCASE MENU TEXT: SUPER SEARCH MESSAGE FILE\n\n\nOUTPUT FROM WHAT FILE: SECURITY KEY\navailable when searching one's mailbox. The user would be limited to\nNAME: XM SUPER SEARCH DESCRIPTIVE NAME: Search all messages\n DESCRIPTION: This key lets the user use the option XM SUPER SEARCH, which\n performs a search for messages in the MESSAGE file based on multiple\n criteria. This key should be given, on a time-limited basis, to trusted\n individuals who have a valid need to research messages in the MESSAGE file.\n For example, in sexual or other harassment cases, in which the harassment is\n in the form of MailMan messages.\n\n\nOUTPUT FROM WHAT FILE: 3.6 BULLETIN\nmessages sent to or sent by the user.\nNAME: XM SUPER SEARCH SUBJECT: Super Search Conducted\n RETENTION DAYS: 90\n MESSAGE: |1| conducted a Super Search of the Message file. The criteria\n used were:\n DESCRIPTION: Every time a super search is conducted, this bulletin is sent\n to alert those responsible for ensuring that the capability is not misused.\n \n A super search is a search of the entire Message file based on any number of\n criteria. All messages are looked at, regardless of who sent them.\n \n\n This bulletin reports who performed the search and what criteria were used.\n \n This bulletin is sent to the mail group XM SUPER SEARCH. The ISO should be\n a member of that group.\n \n See the XM SUPER SEARCH option for more information.\nPARAMETER: 1\n DESCRIPTION: The user who conducted the Super Search.\n\n\nNOIS: IOW-0500-42246\nOUTPUT FROM WHAT FILE: 3.8 MAIL GROUP\nNAME: XM SUPER SEARCH TYPE: public\n ALLOW SELF ENROLLMENT?: NO\n DESCRIPTION: This mail group is sent a bulletin whenever someone conducts\n a Super Search using the XM SUPER SEARCH option. The bulletin tells who\n conducted the search and what search criteria were used.\n \n Members of this mail group should be anyone who ought to be notified\n whenever a Super Search is conducted. At an absolute minimum, the site ISO\n and alternate ISO(s) should be members. There should be enough responsible\n\n
\nPatch XM*7.1*148\n1. Prevents the Postmaster from BRowsing messages in the transmit queues.\n\n2. Improves error tracking during message addressing:\n- If you address a message to a mail group with no members, you will be\ninformed that the group has no members.\n- ^TMP("XMERR",$J) for message addressing API errors now contains:\n^TMP("XMERR",$J,<error #>)=<dialog #>\n^TMP("XMERR",$J,<error #>,"PARAM","ID")="XMTO"\n^TMP("XMERR",$J,<error #>,"PARAM","VALUE")=<recipient>\n^TMP("XMERR",$J,<error #>,"TEXT",<i>)=<line i of error message>\n\n^TMP("XMERR",$J,"E",<dialog #>,<error #>)=""\n\nThe pre-init with this patch deletes three DIALOG file entries which are\nbeing replaced with new ones.\n\nNOTE: This patch requires MailMan patches XM*7.1*133, XM*7.1*134,\nXM*7.1*138, XM*7.1*139, & XM*7.1*146.\n============================================================================ \n\nROUTINES:\nNOIS: MON-0800-51277\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMJMLR1 6891665 5264830 50,72,110,148\nXMJMOI 18383177 18491420 50,87,89,110,127,131,143,146,148\nXMJMP 16023439 15497599 50,75,100,110,127,134,148\nXMJMP1 17261262 19109250 40,50,75,110,133,148\nTest Site: Montana HCS\nXMXADDR 15038029 15075462 50,96,101,104,107,131,148\nXMXADDR1 12529716 12201693 50,78,83,96,104,107,127,138,148\nXMXADDR2 11569369 11091661 50,107,148\nXMXADDR3 8018411 7292198 107,139,148\nXMXADDR4 7390105 7386662 107,148\nXMXADDRD 10214397 9985665 50,104,107,148\nXMXADDRG 14977775 14941972 50,99,107,139,148\nXMYPRE7 35197 35006 127,148\n* Checksums produced by CHECK^XTSUMBLD\n\nWhen user backs up on a broadcast message with a response, default to 0,\nThis patch introduces no new routines.\n============================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patches XM*7.1*133, XM*7.1*134,\nXM*7.1*138, XM*7.1*139, & XM*7.1*146.\n1. Users should not be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \ninstead of 1.\n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users should not be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*7.1*148 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nThis patch also:\n\n DEVICE: HOME// <It's up to you. You may queue it, if you wish.>\n -------------------------------------------------\n6. Let users back on the system.\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n============================================================================\n\n\n\nPatch XM*7.1*149\nthe reply is the text in the 2 node, saved by the editor. The user would\nimmediately be told that a new response had arrived. (It would be from\n"* no name *" if the user backed up to see it.) This patch fixes that. \n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*144..\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXM 10981828 11093966 17,35,50,140,144,149\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\nNOIS: MAR-0500-22472\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*144.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\nTest Sites: Maryland HCS\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*149 Loaded from Distribution <date/time>\n ==========\nIf a user opens second session while editing a reply to a message, and\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nenters MailMan by typing "D ^XM" from the programmer prompt, it is possible\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthat the reply message stub will be killed. When the user returns to the\nfirst session, exits the editor, and transmits the reply, the zero node of\nthe reply is gone, (killed in the second session), and all that is left of\n\n
\n This MailMan patch will change how an 'ANSWER' message looks. The message\n===========================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n will now show the users response, the users network signature, and then\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n===========================================================================\n the original message. The orignal message with be preceded with a '>'.\n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\n XMA11B 3291121 3593034 39\n XMA2 10106075 10059315 5,6,10,15,39\n The user can now edit the entire message, including the original message,\n===========================================================================\n\n by using the 'Edit' option at the 'TRANSMIT option: ' prompt.\n\n===========================================================================\n This patch should be installed after hours, when there is minimum users on\n the system. You should put the XMUSER Option out of order.\n\n
\nPatch XM*7.1*152\nis at a minimum. It requires MailMan patch XM*7.1*118.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\n\nXMJMT 7558831 7600587 50,107,118,152\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*118.\n1. Users may be on the system during installation of this patch.\nNOIS: none\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Sites: FORUM\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*152 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nDuring message addressing, if a user enters ?? at the 'send to:' prompt\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nto ask for Domain information, and the selected domain has a relay domain,\nan abort occurs. This patch fixes that. \n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*150\n\n 3.9 MESSAGE (Partial Definition)\n Note: You already have the 'MESSAGE' File.\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nSTANDARD DATA DICTIONARY #3.715 -- FILTER SUB-FILE\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n6. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nSTORED IN ^XMB(3.7,\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n3.715,9 FORWARD TO 1;0 Multiple #3.7159\n\n3.7159,.01 FORWARD TO 0;1 FREE TEXT (Multiply asked)\n\n INPUT TRANSFORM:D FWDTO^XMTDF(.X,$G(XMIA)) I $D(X) K:$L(X)>50!(\n $L(X)<1) X\n LAST EDITED: OCT 17, 2000 \n HELP-PROMPT: Answer must be 1-50 characters in length.\n DESCRIPTION: Enter the person, group, device, or server to\n whom or to which the message is to be\n forwarded. The message will be forwarded under\n the following conditions, and you will be\n listed as the forwarder.\n\nE3R 14955\n This will only apply when:\n - delivering a message to you for the first\n time.\n\n This will not apply when:\n - you sent the message.\n - the message is already in your mailbox.\n - delivering replies.\n - the message is closed, confidential, or\n otherwise sensitive.\nTest Site: Biloxi, MS\n\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n CROSS-REFERENCE:3.7159^B\n 1)= S ^XMB(3.7,DA(2),15,DA(1),1,"B",$E(X,1,30),\n DA)=""\n\n 2)= K ^XMB(3.7,DA(2),15,DA(1),1,"B",$E(X,1,30),\n DA)\n\nNOTE: This patch should be installed during off hours, when user activity\nAdd 'FORWARD TO' action to message filters.\nis at a minimum. It requires MailMan patches XM*7.1*140 and XM*7.1*142.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nThe help frame XM-U-P-FILTER ACTIONS has been updated.\nXMTDF 4390490 5739561 50,127,142,150\nXMTDL2 9530207 10072873 50,127,150\nXMTDT 5589575 8285616 50,142,150\nXMVVITA 7287397 7295482 50,101,110,140,150\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*140 and XM*7.1*142.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the\nIn your message filters, you are now able to specify recipients to whom\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nfiltered messages should be forwarded.\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*150 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*150\n\n Incoming Files:\n 3.7 MAILBOX (Partial Definition)\n Note: You already have the 'MAILBOX' File.\n\n\n
\nPatch XM*7.1*153\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMCODE 11817911 12139966 50,110,153\n\nXMJMP2 2711990 2695696 110,153\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\n1. Users may be on the system during installation of this patch.\nNOIS: TUC-1000-62033\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Sites: Tucson, AZ\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*153 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nWhen prompting a user for a password on a scrambled message, MailMan now\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\ndisplays the subject and sender, too.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\n\n
\nPatch XM*7.1*155\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMLR1 5264830 5293649 52,72,110,148,155\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*148.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: none\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Sites: FORUM\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*155 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nWhile in the new messages list, if a user attempts a ?search, an abort\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\noccurs. This patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*148.\n\n
\nPatch XM*7.1*151\nAlso, this patch includes routine XMTDL2, to correct line 2 in patch\nXM*7.1*150. The code is unchanged.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*147 and XM*7.1*150.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMKP 16261814 16277893 50,89,119,147,151\nXMTDL 18718545 18831179 50,97,142,151\nXMTDL2 10072873 10072873 50,127,150,151\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS: LOM-0800-63083\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*147 and XM*7.1*150.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nTest Site: Loma Linda, CA\n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nIf two (or more) people are signed on as the same user (either normally\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*151 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*151\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nor as a surrogate) and they forward the same message at the same time,\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n6. Start the background filer.\nit is possible that one forward clobbers the others, and the others won't\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nbe delivered. This patch fixes that.\n\n\n
\nPatch XM*7.1*156\nis at a minimum. It requires MailMan patch XM*7.1*131.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\n\nXMJMSO 8539565 8831110 50,110,127,131,156\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*131.\n1. Users may be on the system during installation of this patch.\nNOIS: BAY-1000-32222\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Sites: BAY PINES, FL\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*156 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIf a user enters an incomplete date for a message vaporize date, assume\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthe future, not the past. Also, if the user is entering a vaporize date\nfor a new message, the vaporize date be no earlier than tomorrow.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*154\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*148.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------------------------\nXMJMOI 18491420 18964660 50,87,89,110,127,131,143,146,148,154\nXMJMOI1 3117776 3352332 110,154\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS: HIN-0600-41009\nis at a minimum. It requires MailMan patch XM*7.1*148.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Sites: Hines, IL\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*154 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nIf two users are signed on as the same user, and both are working on the\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nsame message, and one user saves the message to another basket, an abort\noccurs if the other user tries to save the message, too.\nThis patch fixes that. \n\n\n
\nPatch XM*7.1*157\n\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n===========================================================================\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n3.73,.01 DATE MESSAGE WILL BE NEW 0;1 DATE (Required)\n\n Date Message Will Be New \n INPUT TRANSFORM: S %DT(0)="NOW",%DT="ETF" D ^%DT K %DT(0) S X=Y \n K:Y<1 X\n\n\n LAST EDITED: NOV 16, 2000 \n HELP-PROMPT: Enter a date or date @ time on which you wish \n this message to be new. \n DESCRIPTION: This field should be in FileMan format. The\n file will be X-referenced by it and the\n background filer will process it on that date. \n\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n\n CROSS-REFERENCE: ^^TRIGGER^3.73^1 \nNOIS: ISF-1100-60233\n 1)= X ^DD(3.73,.01,1,1,1.3) I X S X=DIV S Y(1)=\n $S($D(^XMB(3.73,D0,0)):^(0),1:"") S X=$P(Y(1),U\n ,2),X=X S DIU=X K Y S X=DIV S X=$S($D(XMDUZ):XM\n DUZ,1:DUZ) X ^DD(3.73,.01,1,1,1.4)\n 1.3)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S \n Y(1)=$S($D(^XMB(3.73,D0,0)):^(0),1:"") S X=$S('\n $D(^VA(200,+$P(Y(1),U,2),0)):"",1:$P(^(0),U,1))\n =""\n\n 1.4)= S DIH=$S($D(^XMB(3.73,DIV(0),0)):^(0),1:"\nTest Sites: San Francisco OIFO\n "),DIV=X S $P(^(0),U,2)=DIV,DIH=3.73,DIG=1 D ^D\n ICR:$O(^DD(DIH,DIG,1,0))>0\n\n 2)= Q\n\n CREATE CONDITION)= USER=""\n CREATE VALUE)= S X=$S($D(XMDUZ):XMDUZ,1:DUZ)\n DELETE VALUE)= NO EFFECT\n FIELD)= USER\n\nThe .01 field of file 3.73 contains a date input transform. This patch\n CROSS-REFERENCE: 3.73^AB1^MUMPS \n 1)= N XMDUZ,XMZ,XMREC S XMREC=$G(^XMB(3.73,DA,0\n )),XMDUZ=$P(XMREC,U,2),XMZ=$P(XMREC,U,3) I XMZ]\n "" S ^XMB(3.73,"AB",X,XMDUZ,XMZ,DA)=""\n\n 2)= N XMDUZ,XMZ,XMREC S XMREC=$G(^XMB(3.73,DA,0\n )),XMDUZ=$P(XMREC,U,2),XMZ=$P(XMREC,U,3) I XMZ]\n "" K ^XMB(3.73,"AB",X,XMDUZ,XMZ,DA)\n This xref activates when a user changes the\n date/time that a message is latered. \nadds a K %DT(0) to the input transform to prevent leakage.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nNo routines are included in this patch.\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nSTANDARD DATA DICTIONARY #3.73 -- MESSAGES TO BE NEW AT A LATER DATE FILE\nis at a minimum. It requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nSTORED IN ^XMB(3.73,\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*157 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n\n\nPatch XM*7.1*160\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*143.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n-----------------------------------------------------------------\nXMJBM 10627394 11268978 50,110,131,143,160\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*143.\nNOIS: PUG-1100-51632\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Sites: PUGET SOUND HCS\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*160 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nIf a user has only confidential messages in her basket, and a surrogate\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\ntries to read the messages in that basket using the Classic reader, the\nsurrogate is simply tossed out of the basket with no explanation.\nThis patch will ensure that the surrogate is given an explanation.\n\n\n
\nPatch XM*7.1*161\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*160.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n-----------------------------------------------------------------\nXMJBM 11268978 11317455 50,110,131,143,160,161\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*160.\nNOIS: none\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Sites: FORUM\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*161 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nIf a user, using the Classic reader, deletes all the messages in his basket,\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nMailMan tells him that he has only confidential messages in his basket, and\nthat as a surrogate, he is not allowed to read them. This patch corrects\nthat.\n\n\n
\n Prerequisites: none\nANN-0397-41843 Sites were sometimes getting a '550 Domain file locked'\n message after installing patch XM*7.1*34\n\nThis patch also contains code which lays the groundwork for the upcoming\ndomain name changes.\n===========================================================================\n This patch should be installed during off-peak hours when network mail\n activity is low. This patch can be installed with users on the system.\n===========================================================================\n \n=========================================================================== \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. Users can remain on the system. This patch can be queued and should be\n installed during off-peak hours. TaskMan can remain running.\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n This MailMan patch is in response to the following:\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 7. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n\n \n ROUTINES:\n Checksums were calculated with CHECK^XTSUMBLD\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\n XM0 5124637 3346676 4,42\nIOW-0397-40004, MWV-0297-20667, BAY-0397-30178, FAV-0397-71157\n XMP2A 9900587 10037244 24,42\n XMR0B 9558225 9580242 4,6,13,34,42\n============================================================================\n\n KIDS messages were losing the Message Type field during transmission.\n When the user installed the patch they would get an 'UNDEFINDED\n FUNCTION' error.\n\n\n
\nPatch XM*7.1*162\nis at a minimum. It requires MailMan patch XM*7.1*132.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\n\nXMXREPLY 5876870 5772421 50,85,99,107,132,162\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*132.\n1. Users may be on the system during installation of this patch.\nNOIS: ISW-1100-22093\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Sites: FORUM\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*162 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIf a message from a remote site has no remote message ID associated with it,\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nan abort occurs if a user attempts to reply remotely to it. This patch\nprevents the abort by sending the reply as an original message.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*164\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*162.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMYPRE9 * NEW * 84031 164\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nXMYPRE9 has no user-callable entry points.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nNOIS: WRJ-1100-10829\nIt requires MailMan patch XM*7.1*162.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Site: White River Junction, VT\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*164 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nSomehow, the bulletin XMDATANO got corrupted. This patch restores that\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nbulletin to what it should be.\n\nThe pre-init will delete the corrupted version of the bulletin.\n\n\n
\nThis is an informational patch for DSM sites only. Other sites may\n\n$\n\nUnsuccessful connection after maximum retries\n\n$type hlseven.log\n$!HLSEVEN.COM-for incoming connect requests\n$!-------------------------------------------------------------\n$ set noon !Don't stop\n$ set noverify !change as needed \nOpening _BG8215:\nThis patch repeats information in AXP ALERT*117, an excerpt of which follows:\n1> _BG8215: not ready!\n2> _BG8215: not ready!\n3> _BG8215: not ready!\n4> _BG8215: not ready!\n5> _BG8215: not ready!\n6> _BG8215: not ready!\n7> _BG8215: not ready!\n8> _BG8215: not ready!\n9> _BG8215: not ready!\n10> _BG8215: not ready!\n\nCould not open _BG8215: - exiting\n HLSEVEN job terminated at 2-NOV-2000 07:50:40.84\n$\n\nA successful connection after 2 retries\n\n$type hlseven.log\n$!HLSEVEN.COM-for incoming connect requests\n$!-------------------------------------------------------------\n$ set noon !Don't stop\nTO: AXP/VMS DSM SITES\n$ set noverify !change as needed \nOpening _BG8215:\n1> _BG8215: not ready!\n2> _BG8215: not ready!\n_BG8215: is now ready for use - entering DSM\n HLSEVEN job terminated at 2-NOV-2000 07:50:40.84\n$\n\nThe XMINET_ALPHA.COM command procedure is included below, and can be copied\n& pasted into a VMS file directly from this message. Alternatively, the\nFROM: National AXP/VMS Technical Support Team\nXMINET_ALPHA.COM (XM7_1P165.COM) file will be available for downloading from\nthe [.SOFTWARE] directories at the following ftp sites:\n\nHines 152.129.1.110\nAlbany 152.127.1.5\nSalt Lake City 152.131.2.1\n\nTo install:\n\nDisable the UCX XMINETMM service\nRE: AXP ALERT*117 HLSEVEN and XMINETMM "Openfail errors"\n$ UCX DISABLE SERVICE XMINETMM (UCX Version 4.2)\nor\n$ TCPIP DISABLE SERVICE XMINETMM (TCPIP Version 5.0A) \n\nUsing either method, place this new XMINET_ALPHA.COM procedure in the\nSYS$LOGIN directory of the XMINETMM user. Be sure to edit accordingly. \n\nCopy and Paste Method:\n\n$ SET DEFAULT USER$:[XMINETMM] or equivalent of the XMINETMM user.\n\n\nCopy file from below into your Windows buffer by highlighting the entire\ntext of the XMINET_ALPHA.COM file below.\n\n$ CREATE XMINET_ALPHA.COM\n\nPaste the contents of your windows buffer and use CTRL Z to close file.\nThen check/edit XMINET_ALPHA.COM to ensure that the DSM command line is\ncorrect for your system. (You may use your previous version of\nXMINET_ALPHA.COM file as a reference. The entry SOC^XMRUCX is correct.\nHLSEVEN has uncovered a VMS TCP/IP problem regarding DSM not being able to\nSOC25^XMRUCX should no longer be used.)\n\nUsing FTP Method:\n\nTo retrieve from [.SOFTWARE] directories listed above:\n\n$FTP 152.127.1.5\n220 ISC1A2.ISC-ALBANY.DOMAIN.EXT FTP Server (Version 5.0) Ready.\nConnected to 152.127.1.5. \nName (152.127.1.5:dsmmgr): ANONYMOUS\nopen a BG device for use. This problem is related to multi-processor CPU\n331 Guest login OK, send ident as password.\nPassword: \n230 Guest login OK, access restrictions apply.\nFTP> SET DEF [.SOFTWARE]\n250-CWD command successful.\n250 New default directory is VA4$:[ANONYMOUS.SOFTWARE]\nFTP> GET XM7_1P165.COM XMINET_ALPHA.COM\n200 TYPE set to IMAGE.\n200 PORT command successful.\n150 Opening data connection for VA4$:[ANONYMOUS.SOFTWARE]XM7_1P165.COM;\nsystems (i.e. ES40, 4100) with more than one CPU. It is not VMS or UCX\n (152.127.1.6,3281)\n226 Transfer complete.\nlocal: SYS$:[DSMMGR]XMINET_ALPHA.COM;1 remote: XM7_1P165.COM\n144638 bytes received in 00:00:00.04 seconds (3284.83 Kbytes/s)\nFTP> EXIT\n221 Goodbye.\n$\n\nCheck/edit XMINET_ALPHA.COM to ensure that the DSM command line is\ncorrect for your system. (You may use your previous version of\ndisregard. DSM sites, you must manually perform updates. It is important\n(TCPIP) version specific, as we have identified the problem on systems\nXMINET_ALPHA.COM file as a reference. The entry SOC^XMRUCX is correct.\nSOC25^XMRUCX should no longer be used.)\n\n$ COPY XMINET_ALPHA.COM USER$:[XMINETMM] or equivalent of the XMINETMM user.\n\nBefore enabling the XMINETMM service, be sure to check the file ownership\nand protection. \n\nEnable the UCX XMINETMM service\n$ UCX ENABLE SERVICE XMINETMM (UCX Version 4.2)\nrunning VMS 6.2-1H3 to VMS 7.2.1 and also UCX version 4.2 ECO 3 as well as\nor\n$ TCPIP ENABLE SERVICE XMINETMM (TCPIP Version 5.0A)\n\nPlease note that Mailman puts a leading space before the "$" of each DCL\ncommand line in the XMINET_ALPHA.COM file as it is documented. If you choose\nto cut and paste the file from this message, you will need to edit it to\nremove the spaces before enabling the services.\n\n*** Cut here ***\n\nTCPIP version 5.0A. A condition can occur where the server site will fail\n$!XMINET_ALPHA.COM - for incoming connect requests\n$!-------------------------------------------------------------\n$ set noon !don't stop\n$ set noverify !change as needed \n$! set verify !change as needed\n$ purge/keep=5 sys$login:*.log !Purge log files only\n$ set proc/priv=(share) !Required for MBX device\n$ x=f$trnlnm("sys$net") !This is our MBX device\n$! \n$ write sys$output "Opening "+x !This can be viewed in the log file\nto open the BGnnnn: device and the HLSEVEN.LOG will report the following\n$! Check status of the BG device before going to DSM\n$ cnt=0\n$ CHECK:\n$ stat=f$getdvi("''x'","STS")\n$ if cnt .eq. 10\n$ then\n$ write sys$output "Could not open ''x' - exiting"\n$ goto EXIT\n$ else\n$ if stat .ne. 16\nerrors:\n$ then\n$ cnt=cnt+1\n$ write sys$output "''cnt'> ''x' not ready!"\n$ wait 00:00:01 !Wait one second to assure connection\n$ goto CHECK\n$ else\n$ write sys$output "''x' is now ready for use - entering DSM"\n$!-------------------------------------------------------------\n$! **Be sure this command line is correct for your system\n$! **and if access control is enabled, that this account has\n\n$! **access to this uci,vol & routine.\n$!\n$ DSM/E=DSMMGR/U=VAH/V=ROU/DATA="''X'" SOC^XMRUCX\n$!-------------------------------------------------------------\n$ endif\n$ endif\n$ EXIT:\n$ logout/brief\n\n*** end cut here ***\n%DSM-F-OPENERR, error opening device or file\n\nIMPORTANT!!! IMPORTANT!!! IMPORTANT!!!\n\nThis XMINET_ALPHA.COM file is a generic file to be used and EDITED by all\nVMS/DSM sites. Please refer to the comment lines in the command procedure.\nTHIS COMMAND PROCEDURE MAY NOT WORK AS DISTRIBUTED.\nPlease verify that the DSM command line is correct for your site.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum.\n-DSM-E-ERRCODE, Error Code = 0\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nThis patch has no routines.\n-SYSTEM-F-BADPARAM, bad parameter value\n\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum.\n1. Users may be on the system during installation of this patch.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n\n Users may be on the system.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*165 Loaded from Distribution <date/time>\n ==========\nthat you read this patch and follow the instructions to update your\nVistA uses two types of "listen services", HLSEVEN and XMINETMM. Tests have\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nshown that the XMINETMM service is also prone to the same symptoms as seen\n ------------------------------------------------\n5. Now read and follow the instructions in the Patch Description to\nupdate your XMINET_ALPHA.COM file.\n===========================================================================\nby the HLSEVEN service. These tests were run on the FORUM system and have\nproduced retries during heavy activity periods. Therefore, the AXP, HLSEVEN\nand Mailman teams have agreed to jointly release the following Alert and\nInformational patches. \n\nAXP Alert*117\nHL*1.6*70\nXM*7.1*165\nXMINET_ALPHA.COM file.\n\nThe following is an excerpt from Compaq Engineering acknowledging our\nfindings and their description of the problem.\n\n********************************************************************\nCompaq\n\nEngineering thinks the problem here is a race between the INETACP, which\nhas just created the process via $CREPRC(), and the process just created.\n\n\nThe INETACP doesn't relinquish its ownership of the BG device for the\naccepted connection (which it passes in SYS$NET process logical) until\nsometime after $CREPRC() returns success status. If the process gets to\nrun first it may have trouble assigning this BG momentarily. \n\nThis situation only occurs for listen services; nolisten services\n(like FTP) are handled very differently.\n*********************************************************************\n\nAlthough this problem has been acknowledged, Compaq is reluctant to issue a\nPatch XM*7.1*165\npatch to the current version of TCPIP V5.0 due to its complexity. They have \nagreed to provide a fix in a future release. This future release should be \nTCPIP Services for VMS version 5.1, due sometime next year (2001). As an \ninterim "work-around" solution, new HLSEVEN.COM and XMINET_ALPHA.COM command \nprocedures have been written to compensate for this "race condition". \n\nXMINET_ALPHA.COM Descriptions\n\nThis command procedure has been edited to check the status of the BG device\nprior to entering DSM. It contains two IF-THEN-ELSE statements. The first\n\nis a loop to count to 10. The command procedure will terminate after 10\ntries to gain access to the BG device. The second is a loop to test the bit\nmask status [stat=f$getdvi("''x'","STS")] of the BG device. It was found\nthat with a bit mask value of 65552, DSM could not open the BG device but a\nbit mask value of 16 allowed DSM to open the BG device. If the bit mask\nvalue is not equal to 16, then the command procedures will wait one second\nand try again. \n\nTypical log file entries:\n\nNOIS: none\nNote - New log files will not be generated if the XMINET_ALPHA.LOG file\nversion number has reached 32767. To generate new log files, delete all\nXMINET_ALPHA.LOG files and new ones will be generated starting with version\n1. Please also note that empty log files may be normal. If the current log\nfile for the latest connection is still open and the connection is still\nactive, the file will be empty and nothing will be displayed. Very busy\nXMINETMM services may see this and they can also generate failure to purge\nerror messages. Keeping more log files in the purge statement in the\ncommand procedures can avoid purge error messages - adjust accordingly.\n\nTest Sites: FORUM\nSuccessful connection with no retries\n\n$type hlseven.log\n$!HLSEVEN.COM-for incoming connect requests\n$!-------------------------------------------------------------\n$ set noon !Don't stop\n$ set noverify !change as needed \nOpening _BG8534:\n_BG8534: is now ready for use - entering DSM\n HLSEVEN job terminated at 2-NOV-2000 07:55:38.44\n\n\nPatch XM*7.1*135\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMRUCX 841742 478788 27,34,50,135\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\nNOIS: NAS-1099-33188\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: \n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*135 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nInstead of going to ^XUSCLEAN when incoming net mail is finished, simply\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nquit. Also, make the SOC25 entry point identical to the SOC entry point.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n\n
\nPatch XM*7.1*158\nSUFFIX. They continue to be added to file 4.2, DOMAIN.\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nA new bulletin, XM DOMAIN ADDED, now notifies G.POSTMASTER of these\nnew domains.\n\nThe pre-init, XMYPOSTD deletes all entries from the INTERNET SUFFIX\nfile 4.2996. A new DD will be brought in for this file, along with\nall its data. It is populated with all the internationally recognized\ntop-level domains. You will not be able to edit that file, except for\nadding notes.\n\n\nA 'B' xref is added to the .01 field of the TRANSMISSION SCRIPT multiple\nof the DOMAIN file 4.2. The post-init, POST^XMYPOSTD, sets the 'B' xref.\n\nNOTE: This patch requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\nTest Site: Puget Sound HCS\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------------\nXMR0B 8875848 8051092 4,6,13,34,42,62,50,158\nXMYPOSTD * NEW * 3967175 158\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\nNOIS: RIC-1100-21104\nXMYPOSTD has no user callable entry points.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*50.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nAn incoming message from a top-level domain that is not recognized by\n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Stop TaskMan. Shut down the listeners. You may also wish to shut down\n HL7 filers/LLP's and other background tasks which may attempt to create\n new messages. During the installation of this patch, we do not want any\n messages coming in or going out. Users should not be on the system.\nMailMan can cause problems. This patch prepares MailMan for that\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*158 Loaded from Distribution <date/time>\n ==========\n Install Questions:\neventuality.\nIncoming Files:\n\n 4.2996 INTERNET SUFFIX (including data)\nNote: You already have the 'INTERNET SUFFIX' File.\nI will OVERWRITE your data with mine.\n\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// YES\n ===\n\n Enter options you wish to mark as 'Out Of Order': XMUSER MailMan Menu\n ======\n Enter options you wish to mark as 'Out Of Order': <press return>\n ==============\n Enter protocols you wish to mark as 'Out Of Order': <press return>\n ==============\n Delay Install (Minutes): (0-60): 0// <press return>\n ==============\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nThese top-level domains are no longer added to file 4.2996, INTERNET\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Start TaskMan. If you shut down HL7 filers/LLP's and other\n background tasks in step 4, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n\n
\n ************************************************************\nIf a site lists itself as the PARENT in file 4.3, MAILMAN SITE PARAMETERS,\nthat can cause problems. This patch puts a screen on that field in the DD\nto prevent this from happening.\n\nThe pre-init for this patch will check to ensure that your site does not\nhave itself as its PARENT. If it does, the PARENT field will be deleted\nand you will have to enter the correct PARENT.\n\nIf field 3, PARENT, in file 4.3 is filled in, you should ensure that it\ndoes not point to its own domain. It should be the domain considered\n It is important that you read the information in this patch.\nthe parent of your facility. The parent domain is the domain to which\nmail is sent, when your facility doesn't quite know what to do with it.\n\nFor example,\n1. The parent domain of the MailMan development account, \nMAILMAN.ISC-SF.DOMAIN.EXT, is ISC-SF.DOMAIN.EXT.\n(The parent domain should NOT be MAILMAN.ISC-SF.DOMAIN.EXT)\n2. The parent domain of ISC-SF.DOMAIN.EXT is DOMAIN.EXT. It could also\nbe GK.DOMAIN.EXT or whatever domain your site uses to send mail to the\ninternet. (The parent domain should NOT be ISC-SF.DOMAIN.EXT)\n You may have to manually fix something.\n\nThe account that you install this patch in probably matches one of the\nexamples. If not, the parent domain should be the domain through which\nyou route messages to remote sites over the internet.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\n ************************************************************\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMYPRE10 * new * 1299000 166\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nPatch XM*7.1*166\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*166 Loaded from Distribution <date/time>\n\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\nNOIS: TUC-0101-60657\n DEVICE: HOME// <It's up to you, you may queue it if you wish.>\n -----------------------------------------------\n6. Check the Install File Print. If you see this, you need to take action.\nIf you don't see it, you're OK:\n\n***********************************************\n \nField 3, PARENT, in file 4.3 was deleted.\nYou must enter a new PARENT.\nSee the patch description for how to choose one.\nTest Sites: Tucson, AZ\n \n***********************************************\n\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\n
\nPatch XM*7.1*170\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------------\nXMS0A 9199959 9159707 2,13,55,50,170\n \n \n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*50.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest Site: Hines\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Stop TaskMan. Shut down the listeners. You may also wish to shut down\n HL7 filers/LLP's and other background tasks which may attempt to create\nNOIS: HIN-0201-42151\n new messages. During the installation of this patch, we do not want any\n messages coming in or going out. Users should not be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*170 Loaded from Distribution <date/time>\nPut quotes around an address containing blanks when sending messages to\n ==========\n Install Questions:\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nremote sites.\n \n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Start TaskMan. If you shut down HL7 filers/LLP's and other\n background tasks in step 4, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n \n===========================================================================\nNOTE: This patch requires MailMan patch XM*7.1*50.\n============================================================================ \n\n
\nPatch XM*7.1*172\nHelp Frames are updated.\nDialogs have been added.\n\nA new API, QX^XMXUTIL3, has been added, to perform the above actions.\nSee DBIA 2737 for details.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*137 & XM*7.1*154.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMD 9221858 9242714 50,104,110,137,172\nXMJMOI 18964660 14281898 50,87,89,110,127,131,143,146,148,154,172\nXMJMOI1 3352332 8242009 110,154,172\nE3R 15488\nXMJMP1 19109250 19119781 40,50,75,110,133,148,172\nXMJMQ 15971466 13062269 40,57,70,50,96,110,131,172\nXMJMQ1 8577594 13480745 40,50,110,130,131,172\nXMJMRO 4485523 5033137 50,89,110,127,172\nXMXSEC2 27320982 27625845 50,89,95,110,146,172\nXMXUTIL3 3652490 5771323 50,172\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\nTest Sites: FORUM\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*137 & XM*7.1*154.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\nAdd the following message actions at the Message Action: Ignore// prompt:\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*172 Loaded from Distribution <date/time>\n ==========\nQC - Show all users who are current on the message (read all responses).\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nQNC - Show all users who are not current on the message.\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nQT - Show all users who have terminated the message.\n\n\n
\nPatch XM*7.1*169\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------------\nXMR0B 8051092 8083120 4,6,13,34,42,62,50,158,169\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*158.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest Site: Beckley, WV\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Stop TaskMan. Shut down the listeners. You may also wish to shut down\n HL7 filers/LLP's and other background tasks which may attempt to create\nNOIS: BEC-0201-21992\n new messages. During the installation of this patch, we do not want any\n messages coming in or going out. Users should not be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*169 Loaded from Distribution <date/time>\nWhen receiving mail from a site, make sure the site's name is in upper case.\n ==========\n Install Questions:\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nOtherwise, MailMan might not find it in the DOMAIN file.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Start TaskMan. If you shut down HL7 filers/LLP's and other\n background tasks in step 4, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n\n===========================================================================\nNOTE: This patch requires MailMan patch XM*7.1*158.\n============================================================================ \n\n
\nPatch XM*7.1*171\nIn the FILTER subfile of file 3.7, MAILBOX,\nField 5, FROM, has some new help text.\nField 6, ADDRESSED TO, is expanded to 55 characters.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*146 and XM*7.1*150.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------------\nXMJMF2 6206910 6828041 146,171\nXMJMFB 16215095 17121533 50,110,131,146,171\nXMTDF 5739561 7250797 50,127,142,150,171\nXMXLIST 6225911 6277109 50,108,146,171\n* Checksums produced by CHECK^XTSUMBLD\nTest Site: Columbia, MO\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*146 and XM*7.1*150.\n1. Users may be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nNOIS: CMO-0101-42392\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. You do not need to stop TaskMan. Users may be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\nFix Filter/query messages addressed to a private mail group.\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*171 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n\nFilter won't recognize such messages at all.\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\nQuery does find them, but the user interface is problematical when changing\n7. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n8. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthe 'addressed to' selection.\n\n\n
\nThis MailMan patch is in response to a problem noted on FORUM.\nMailMan sends a message to Site A about the rejection.\nMailMan keeps trying to forward the message from Site B to Site C\nand keeps sending rejection messages to Site A, ad infinitum, ad nauseum.\nMailMan does not notify the user at Site B who forwarded the message.\n \nThis patch does two things:\n1. Sends the reject message to the user who forwarded the message.\n2. Changes the status of the message so that MailMan does not attempt to\nsend it again.\n===========================================================================\n \n \n This patch can be installed with users on the system.\n===========================================================================\n \nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\nA description of the problem:\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\nSite A (from outside the VA) sends a message to Site B (in the VA).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\nUser at Site B forwards the message to Site C (in the VA).\n XMSERR 2286812 3651687 32\n============================================================================\nSite C has records in ^XMBX(4.501 (do not accept messages from domains\nwhich match).\nSite C rejects the message because the originating domain (Site A)\npartial-matches the 'do not accept' record.\n\n
\nPatch XM*7.1*175\nIt requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n\nXMP2A 10101095 10271572 24,42,50,175\nXMPH 3963996 4915924 34,50,175\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nTest Site: Cleveland, OH\nIt requires MailMan patch XM*7.1*50.\n1. Users may be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the Background Filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*175 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nE3R 15757\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you - you may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nAdd more information to the header of PackMan printouts, including\nsubject, message number, who sent it, and when.\n\nNOTE: This patch may be installed at any time.\n\n
\nPatch XM*7.1*168\nand XM*7.1*156.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\n\nXM 11093966 11099027 17,35,50,140,144,149,168\nXMJMSO 8831110 8864099 50,110,127,131,156,168\nXMXSEND 11102759 11097083 50,106,107,116,168\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS: PUG-0201-50586\nis at a minimum. It requires MailMan patches XM*7.1*116, XM*7.1*149,\nand XM*7.1*156.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\nTest Site: Puget Sound HCS\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*168 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nHOME^%ZIS is improperly called in several places, which can result in\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nIO becoming null. This patch fixes that.\n===========================================================================\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*116, XM*7.1*149,\n\n
\nPatch XM*7.1*174\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------\nXMC11 11806932 11867009 50,174\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nTest Site: Dublin, GA\nIt requires MailMan patch XM*7.1*50.\n1. Users may be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the Background Filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*174 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nNOIS: DUB-1099-31240\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you - you may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf you attempt to play a script for a queue which already has a task\nassociated with it, you could be stuck in an endless warning loop,\nif you do not possess the XUPROGMODE key. This patch fixes that.\n\n\n
\nPatch XM*7.1*176\nso GATEWAY tried again in lower case, as it usually does. GK then closed\nthe connection. This left the offending message clogging the queue at\nGATEWAY. The fix is that if the receiving site is non-MailMan, and the\nreceiving site does not like the recipient, the sending site will not try\nthat recipient again.\n\nNOTE: This patch requires MailMan patch XM*7.1*148.\n============================================================================ \n\nROUTINES:\n\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMSM 7239792 7204635 4,6,13,20,50,176\nXMSMAIL 4239659 4266359 59,50,107,176\nXMXADDR3 7292198 7967909 107,139,148,176\n\nTest Site: FORUM\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*148.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Stop TaskMan. Shut down the listeners. You may also wish to shut down\n HL7 filers/LLP's and other background tasks which may attempt to create\nNOIS: none\n new messages. During the installation of this patch, we do not want any\n messages coming in or going out. Users should not be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*176 Loaded from Distribution <date/time>\nImprove MailMan's actions at the sending site during remote transmissions\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// YES\n ===\n Enter options you wish to mark as 'Out Of Order': XMUSER MailMan Menu\n ======\n Enter options you wish to mark as 'Out Of Order': <press return>\n ==============\nif the receiving site notifies the sending site that a recipient isn't found.\n Enter protocols you wish to mark as 'Out Of Order': <press return>\n ==============\n Delay Install (Minutes): (0-60): 0// <press return>\n ==============\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n\n7. Start TaskMan. If you shut down HL7 filers/LLP's and other\n background tasks in step 5, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nWe had a problem at GATEWAY transmitting to GK. GK didn't like a recipient,\n\n
\nPatch XM*7.1*163\nXMENROLL - Enroll in (or Disenroll from) a Mail Group\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*163 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n\nIncoming Files:\n 3.8 MAIL GROUP (Partial Definition)\nXMMGR-MAIL-GRP-COORDINATOR - Mail Group Coordinator's Edit\nNote: You already have the 'MAIL GROUP' File.\n\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nXMMGR-MAIL-GRP-COORD-W/REMOTES - Mail Group Coordinator's Edit W/Remotes\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nXMEDITPERSGROUP - Personal Mail Group Edit\n\nThe option XMEDITMG is being converted from an 'edit' type option to a 'run\nroutine' type option. The pre-init, ^XMYPRE11, will delete the fields in the\noption which are no longer applicable.\n\nThe pre-init will also check entries in file 3.8, MAIL GROUP. If the group is\n\npublic, any entry in the 'Restrictions' field (#10) will be deleted. (This\nfield only applies to private groups.) If the group is private, any entry in\nthe 'Allow self-enrollment?' (#7) field will be deleted. This field only\napplies to public groups. \n\nIf someone other than the organizer or coordinator adds users to a public\nmail group which doesn't allow self-enrollment, or to a private mail group,\na new bulletin, XM GROUP EDIT NOTIFY, is sent to the organizer and\ncoordinator to let them know which users were added and who added them.\n\nE3R 2658, 8649, 15053\nA new security key, XM GROUP EDIT MASTER, is being created, which should be\nassigned to any users, such as ADPACs, who need to be able to edit other\nusers' mail groups.\nNAME: XM GROUP EDIT MASTER\n DESCRIPTIVE NAME: Edit other users' mail groups\n DESCRIPTION: People who need to be able to edit other users' mail groups\n and add new users to them should be assigned this key. \n \n Holders of this key may edit any mail group, except personal mail groups. \n (Personal mail groups are those which only the organizer may edit or use.) \nTest Sites: Puget Sound HCS, Charleston, SC\n \n The following users should NOT be given this key, because they already\n possess the privilege this key grants: \n - Holders of the XMMGR key. \n - Clinical Application Coordinators, as identified in file 8930,\n USR Class, belonging to the TIU package. \n\nApplicable Help frames are updated.\n\nNew APIs have been added. See DBIA 3006.\nWhen users join a mail group, or when users are added to mail groups,\nADDMBRS^XMXAPIG - Add members to mail groups. Optionally forward past\n mail group messages.\nJOIN^XMXAPIG - Enable user to enroll in mail group. Optionally forward\n past mail group messages.\nDROP^XMXAPIG - Enable user to drop from a mail group.\n$$MEMBER^XMXAPIG - Is user a member of a mail group?\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*141 & XM*7.1*148.\n============================================================================ \noptionally Find and Forward past mail group messages to the users.\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n---------------------------------------------------------------------------\nXMVGROUP 7972968 12125651 50,104,107,131,141,163\nXMVGRP * NEW * 10944118 163\n\nXMXADDR 15075462 15486856 50,96,101,104,107,131,148,163\nXMXADDR1 12201693 12248366 50,78,83,96,104,107,127,138,148,163\nXMXADDR4 7386662 7400001 107,148,163\nXMXADDRG 14941972 15107024 50,99,107,139,148,163\nXMXAPIG 1692175 4324918 109,146,163\nXMXGRP * NEW * 9502286 163\nXMXGRP1 * NEW * 10875164 163\nXMYPRE11 * NEW * 687829 163\n* Checksums produced by CHECK^XTSUMBLD\n\nThe following options now include this capability:\nThis patch introduces the following new routines:\nXMVGRP - no user-callable entry points.\nXMXGRP - no user-callable entry points.\nXMXGRP1 - no user-callable entry points.\nXMYPRE11 - no user-callable entry points.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*141 & XM*7.1*148.\nXMEDITMG - Mail Group Edit\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n\n
\nPatch XM*7.1*178\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------------\nXMXPARM 15143763 14940380 50,96,107,127,131,143,178\n\nXMXPARM1 2907067 4052895 50,96,127,178\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*143.\nNOIS: BRX-0301-12876\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Bronx\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*178 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nWhen using the API SENDBULL^XMXAPI, if you specify "" for XMBODY, it causes\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nan error. It shouldn't. This patch fixes that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*143.\n\n
\nPatch XM*7.1*173\nThe following options are improved:\n ==============\n Delay Install (Minutes): (0-60): 0// <press return>\n ==============\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Start TaskMan. If you shut down HL7 filers/LLP's and other\nXMQHIST Historical Queue Data/Stats Report\n background tasks in step 4, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nXMQUEUED Queues with Messages to Transmit Report\nXMQACTIVE Actively Transmitting/Receiving Queues Report\nXMSTARTQUE-ALL Transmit All Queues\nXMQDISP Display Active & Inactive Message Queues\nThe pre-init deletes some fields (ENTRY ACTION, EXIT ACTION) which are\nno longer used in options XMQUEUED & XMQDISP.\n\nThe following field is updated. The field is larger and no longer accepts\n\ndigits after the decimal point.\n\nSTANDARD DATA DICTIONARY #4.2999 -- MESSAGE STATISTICS FILE\nSTORED IN ^XMBS(4.2999,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n4.2999,5 RATE OF TRANSMISSION 3;5 NUMBER\n INPUT TRANSFORM: K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1N.N) X\n LAST EDITED: MAR 20, 2001 \nTest Site: FORUM; Clarksburg, WV\n HELP-PROMPT: Type a Number between 0 and 999999999, 0 Decimal \n Digits \n DESCRIPTION: This is the transmission rate in characters per\n second for the current transmission. It may be\n for a single line or for a block or for the\n entire message. It is updated regularly during\n the transmission. \n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*142 & XM*7.1*176.\n\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------------------\nXMLSTAT 1232153 1231749 173\nNOIS: ISL-0299-52128\nXMS4 2836511 2449556 50,173\nXMS5 13300220 10992631 13,8,23,27,55,58,50,142,173\nXMS5A 3571279 3634911 55,50,173\nXMSMAIL 4266359 4266449 59,50,107,176,173\nXMYPRE8 228290 275167 142,173\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\nIncrease from 8 to 9, the number of characters of the device name that is\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*142 & XM*7.1*176.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. On the Manage MailMan:Local Delivery Management menu, use the following\nkept in field 6, NETWORK DEVICE, of file 4.2999, MESSAGE STATISTICS.\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Stop TaskMan. Shut down the listeners. You may also wish to shut down\n HL7 filers/LLP's and other background tasks which may attempt to create\n new messages. During the installation of this patch, we do not want any\n messages coming in or going out. Users should not be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\nThat way, there is less of a chance that important information is dropped.\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*173 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// YES\n ===\n Enter options you wish to mark as 'Out Of Order': XMUSER MailMan Menu\n ======\n Enter options you wish to mark as 'Out Of Order': <press return>\n ==============\n Enter protocols you wish to mark as 'Out Of Order': <press return>\n\n
\nPatch XM*7.1*177\n\nAdditionally, the group message actions have been made more efficient.\nActions involving new messages are faster. Actions involving moving\nmessages out of a basket are faster. So, 'New Toggle', 'Delete',\n'Terminate', 'Filter', and 'Save' are faster.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*126, *136, *143, *151, *168, &\n*172.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------------------\nXMJMOI 14281898 14358567 50,87,89,110,127,131,143,146,148,154,172,177\nXMJMOR 14599384 14568568 50,75,110,131,177\nNOIS: IVM-0301-32726, BAY-0101-30908\nXMJMORX 15388148 12555666 50,110,131,177\nXMJMORX1 2575833 6931876 50,110,177\nXMTDL2 10072873 10414584 50,127,150,151,177\nXMTDT 8285616 8336537 50,142,150,177\nXMUT4C 7616619 7618380 10,22,50,108,136,177\nXMXBSKT 12283844 12536572 50,106,115,126,177\nXMXMBOX 1264480 1530327 50,144,177\nXMXMSGS 10461549 10777832 50,110,124,131,143,177\nXMXMSGS2 7663790 8054067 50,106,110,127,131,143,177\nXMXSEC 23410717 23318832 50,110,127,177\nTest Site: HEC-ATLANTA; Bay Pines, FL\nXMXSEND 11097083 10382185 50,106,107,116,168,177\nXMXUTIL 12959022 13260929 40,50,107,127,131,140,177\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nAt times of high messaging activity, contention in getting locks on the\nminimum. It requires MailMan patches XM*7.1*126, *136, *143, *151, *168, &\n*172.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the\nMESSAGE file causes problems. This patch attempts to ameliorate that\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nproblem by removing MailMan's locking of the MESSAGE file, and letting\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*177 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*177\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nFileMan handle it alone. You will never again see the message, "We're\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n6. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\nhaving problems getting a lock on the MESSAGE file, do you want to wait?"\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\n
\nPatch XM*7.1*159\n\n bulletin is sent.\n\n When the option is scheduled:\n\n 1) The option runs at the scheduled time, as specified by the QUEUED TO\n RUN AT WHAT TIME field (2) of the OPTION SCHEDULING file (19.2).\n\n 2) If the RESCHEDULING FREQUENCY field (6) of file 19.2 is set, the option\n is scheduled to run repeatedly.\n\nNOIS: PUG-0800-50981\n 3) It uses the DATE PURGE CUTOFF DAYS field, or the default of 730 days if\n it's empty, to calculate the cutoff date.\n\n 4) It does not run in Test mode.\n\n 5) If the DATE PURGE GRACE PERIOD field (10.04) of file 4.3 is empty, the\n purge runs at the time for which the option is scheduled.\n\n 6) Otherwise, at the scheduled time the option only broadcasts the XM DATE\n PURGE WARNING bulletin to all users and queues a second task to perform\nE3R: 2736, 2765, 3286, 8959, 10302, 12540\n the date purge GRACE PERIOD number of days later.\n\n 7) If the DEVICE FOR QUEUED JOB OUTPUT field (3) of file 19.2 is empty,\n the purge runs without printing a report.\n\n 8) Otherwise it prints the report on the selected device.\n\n *Messages in SHARED,MAIL's mailbox and messages in the POSTMASTER's remote\n transmit queues and server baskets (including released patch messages on\n FORUM) are exempt from the purge. \nWarn the user of an impending purge-by-date a certain number of days before\n ROUTINE: ENTER^XMA32 SCHEDULING RECOMMENDED: YES\n UPPERCASE MENU TEXT: PURGE MESSAGES BY ORIGINATION \n\nHere's the new warning bulletin:\n\nOUTPUT FROM WHAT FILE: BULLETIN// \nNAME: XM DATE PURGE WARNING SUBJECT: Date Purge Scheduled for |1|\n PRIORITY?: YES\n MESSAGE: Attention! On |1|, all* messages (and their responses) sent on\n or before |2| will be deleted from the system. They will be gone forever.\nthe messages are actually purged. The warning will be a broadcast bulletin,\n \n You can find out if this will affect any messages in your mailbox and take\n appropriate measures. \n \n From the main MailMan menu, respond to the prompts as follows: \n \n Select MailMan Menu Option: Query/Search for Messages \n =\n Select message search method: M Search my Mailbox by multiple criteria \n =\nwhich will vaporize on the purge date. This patch includes updated options\n Select search action: Enter 'Subject contains' string// DB Enter 'Message\n sent on or before' date ==\n Message sent on or before: |2| \n |3|\n \n This search will find all of your messages which will be deleted. \n \n * Messages in SHARED,MAIL's mailbox, and messages in the POSTMASTER's remote\n transmit queues and server baskets (includes released patches on FORUM) are\n exempt from the purge. \nXMKSP and XMPURGE-BY-DATE, new bulletin XM DATE PURGE WARNING, and two new\n DESCRIPTION: This is the warning bulletin that is broadcast to all users\n whenever option XMPURGE-BY-DATE is used to purge messages older than a\n certain date. See that option for more information.\nPARAMETER: 1\n DESCRIPTION: The date that the date purge will run. \nPARAMETER: 2\n DESCRIPTION: All messages this date and older will be purged. \nPARAMETER: 3\n DESCRIPTION: A line of '=' as long as parameter 2\n\nfields in file #4.3, MAILMAN SITE PARAMETERS. Read on for details.\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*120 & XM*7.1*136.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n--------------------------------------------------------------------\nXMA32 6537619 8333956 37,50,159\nXMA32A 9915667 9150003 27,37,44,55,50,136,159\nXMXBULL 5258679 5447862 50,107,120,159\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nTwo new fields have been added to file #4.3 MAILMAN SITE PARAMETERS. The\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*120 & XM*7.1*136.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n\noption XMKSP, to edit those parameters, has been updated to include them.\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*159 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nSTORED IN ^XMB(1,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n4.3,10.03 DATE PURGE CUTOFF DAYS .18;1 NUMBER\n INPUT TRANSFORM: K:+X'=X!(X>9999)!(X<365)!(X?.E1"."1N.N) X\n LAST EDITED: NOV 17, 2000 \nTest Sites: FORUM, Puget Sound HCS\n HELP-PROMPT: Type a Number between 365 and 9999, 0 Decimal \n Digits \n DESCRIPTION: This field is used by the option\n XMPURGE-BY-DATE. When this option is run, the\n date purge will be set to purge all messages\n originating this many days ago and before. \n \n If this field is null, the default will be 730\n days (2 years). \n\n\n4.3,10.04 DATE PURGE GRACE PERIOD .18;2 NUMBER\n INPUT TRANSFORM: K:+X'=X!(X>31)!(X<3)!(X?.E1"."1N.N) X\n LAST EDITED: NOV 17, 2000 \n HELP-PROMPT: Type a Number between 3 and 31, 0 Decimal \n Digits \n DESCRIPTION: This is the number of days' warning the users\n get before the date purge, XMPURGE-BY-DATE, is\n run. \n \n This field is used by the option\nE3R: 3753\n XMPURGE-BY-DATE only if that option is\n scheduled, not if it is run interactively. \n \n At the scheduled date/time, the bulletin, XM\n DATE PURGE WARNING, is broadcast to all users\n to warn them of the coming date purge, and the\n actual date purge is then queued to run this\n many days later. \n \n If this field is null, the date purge will run\nRecognize and support the vaporize days field which is in file #3.6,\n at the scheduled date/time, and no bulletin\n will be sent. \n\nYou are now able to schedule the option XMPURGE-BY-DATE. You couldn't do\nthat before.\n\nNAME: XMPURGE-BY-DATE\n MENU TEXT: Purge Messages by Origination Date\n TYPE: run routine CREATOR: POSTMASTER\n LOCK: XMMGR PACKAGE: MAILMAN\nBULLETIN. (This is field #5, RETENTION DAYS, which has been there since\n DESCRIPTION: You must hold the XMMGR and XMSTAR keys to run this option. \n \n XMPURGE-BY-DATE will delete *all* messages originating before a cutoff\n date. It will delete those messages from users' mailboxes, and then delete\n them from the MESSAGE file, along with any responses chained to them. This\n flexible option can be run interactively or scheduled to run on a\n recurring basis, the cutoff date can be controlled, users may or may not\n be sent a warning bulletin to warn them of the purge ahead of time, and\n the option may produce a report to show how many messages and responses it\n deleted.\n1994, but never used!) If the field is filled in, the bulletin will be set\n\n When the option is run interactively:\n\n 1) It asks for the cutoff date. The default is based on the DATE PURGE\n CUTOFF DAYS field (10.03) in the MAILMAN SITE PARAMETERS file (4.3). If\n that field is null, it defaults to 730 days (2 years) in the past.\n\n 2) It asks whether to run the option in Test mode. In Test mode, the\n option will not purge any messages, just report how many and which would\n have been purged.\nto vaporize that many days from the time the bulletin is sent. \n\n 3) It asks for the output device on which to print the report. The purge\n and report can be queued here to run later.\n\n 4) If it's queued more than 3 days in the future, the option immediately\n broadcasts the XM DATE PURGE WARNING bulletin to all users to notify them\n of the upcoming purge and give them a chance to save off old messages\n beforehand.\n\n 5) If it's queued less than 3 days in the future, or is not queued, no\n\n
\nPatch XM*7.1*181\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*163.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMVGRP 10944118 11414072 163,181\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS: DAY-0401-42491\nis at a minimum. It requires MailMan patch XM*7.1*163.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Site: Dayton, OH\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*181 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nWhen adding a new member to a mail group, and choosing to forward existing\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\ngroup messages to the new member, MailMan asks for a date range of messages\nto search. If the oldest message on the system is less than one year old,\nthen MailMan should give a default date of the oldest message, instead of a\ndate from a year ago. This patch fixes that.\n\n
\n \n===========================================================================\n \nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n This MailMan patch contains the following bug fix:\n options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\n XM 4894935 4976038 17,35\n============================================================================\n-Prevents XUTESTUSER option from being able to complete a user's unsent\n message or response. NOIS WWW-0796-51230\n===========================================================================\n \n This patch should be installed after hours, when there is minimum users on\n the system. You should put the XMUSER Option out of order.\n\n
\nPatch XM*7.1*180\nNOTE: This patch may be installed at any time, even during hours of peak\nusage. It requires MailMan patch XM*7.1*125.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n-----------------------------------------------------------------\nXMUTERM 13549078 13770249 50,125,180\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time, even during hours of peak\nusage. It requires MailMan patch XM*7.1*125.\nNOIS ANN-0401-41468\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: ANN-ARBOR, MI\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*180 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nA bogus message number at the end of the MESSAGE file 3.9 prevents the\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\noption XMMGR-PURGE-MESSAGE from functioning properly and letting a user\nselect a message to purge. This patch checks for and kills such bogus\nmessage numbers, so that the purge selection functions properly.\n\n\n
\nPatch XM*7.1*182\nusage. It requires MailMan patch XM*7.1*176.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\n \nXMSERR 3280474 868666 32,50,182\nXMSM 7204635 7427993 4,6,13,20,50,176,182\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time, even during hours of peak\nusage. It requires MailMan patch XM*7.1*176.\nNOIS: none\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: GATEWAY.DOMAIN.EXT\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*182 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nWhen sending a message to a remote site, and the remote site refuses to\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\naccept a message from the particular sender, delete the message from the\nqueue, and notify the sender that the message was rejected.\n \nNOTE: This patch may be installed at any time, even during hours of peak\n\n
\nPatch XM*7.1*51\napproved. \n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n10. On the KIDS:Utilites menu, use the following option to review the\ninstall:\n Install File Print\n\nReview the automatic synonym additions which occurred during the PRE-INIT.\nIf there were any errors noted for a particular domain, that domain did not\nhave its new name added as a synonym. (Error messages are preceded by ***,\nand tell you what was wrong.) You must correct the error manually and add\nthe synonym manually. Remember, you are not to change any domain name.\n\nJust add the new name as a synonym. \n\nReview the automatic domain name changes which occurred during the POST-INIT.\nIf there were any errors noted for a particular domain, that domain did not\nhave its name changed. (Error messages are preceded by ***,\nand tell you what was wrong.) You must correct the error manually and\nperform the name change manually.\n\nIf you have questions or need any help, please enter a NOIS.\n===========================================================================\nThis patch will complete the 2-step domain name change process begun in patch\nXM*7.1*50. The synonyms will become the new domain names, and the old domain\nnames will become the synonyms. The domain names will be changed in the\ntransmission scripts. The names of the transmission queues will be changed.\n(These are the Postmaster's baskets where the messages waiting to be\ntransmitted are kept.) And finally, the domain name of the site will be\nchanged, too, if it is one of the sites which requested it. \n\n\nThis will all happen automatically, during the post-init. It should take\nless than 5 minutes. You will be instructed to review the install file print\nto check for and correct any errors after the patch has been installed. \n\nThe domain name changes will not adversely affect the flow of mail.\n\nThis patch will also begin the 2-step domain name change process for the\nsecond round of domain name changes. It will add as synonyms the desired\nnew names for sites which requested it. For all other VA sites, which did\nnot express any interest in changing their names, it will add a synonym of\nTest Sites: Montana HCS; Biloxi, MS\nxxx.DOMAIN.EXT. A future patch will complete the domain name change\nprocess, once all sites have installed this patch.\n\nNOTE: This patch requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMUDNC 3683283 13102674 50,51\nXMYPOSTA 2107256 4556859 50,51\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*50.\nNOIS: DET-0898-40391, CIH-1197-40757, ALL-0297-41999, BTM-1095-10195\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n\n<< Background filer will stop soon. >>\n5. Place TaskMan in a WAIT State. Shut down the listeners.\n You may also wish to shut down HL7 filers/LLP's and other background\n tasks which may attempt to create new messages. During the installation\n of this patch, we do not want any messages coming in or going out.\n Users should not be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nPatch XM*7.1*50, released August 1999, added ".DOMAIN.EXT" synonyms in the\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*51 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// YES\n ===\nDOMAIN file for every site which requested it. It also added new names as\n Enter options you wish to mark as 'Out Of Order': XMUSER MailMan Menu\n ======\n Enter options you wish to mark as 'Out Of Order': <press return>\n ==============\n Enter protocols you wish to mark as 'Out Of Order': <press return>\n ==============\n Delay Install (Minutes): (0-60): 0// <press return>\n ==============\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nsynonyms for sites which have merged or which requested and had name changes\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Remove TaskMan from a WAIT State. If you shut down HL7 filers/LLP's\n and other background tasks in step 4, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n\n
\nPatch XM*7.1*183\nis at a minimum. It requires MailMan patch XM*7.1*177.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\n\nXMJMORX1 6931876 7025098 50,110,177,183\nXMXMSGS2 8054067 8470689 50,106,110,127,131,143,177,183\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\nNOIS: MON-0501-50530\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: Montana HCS\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*183 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nWhen a surrogate saves messages to the WASTE basket, MailMan allows\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nconfidential messages to be saved, too. It shouldn't. This patch fixes\nthat.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*184\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------------------\nXMXBSKT 12536572 12498784 50,106,115,126,177,184\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\nNOIS: REN-0501-61866\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: Reno, NV\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*184 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nIf a user, who does not hold the XMMGR key and is not a Postmaster\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nsurrogate, goes into SHARED,MAIL and attempts to resequence messages\nin a basket, MailMan tells the user he's resequencing, but then doesn't\nresequence them. This patch fixes that.\n\n\n
\nPatch XM*7.1*185\nis at a minimum. It requires MailMan patch XM*7.1*177.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\n\nXMXSEND 10382185 10773097 50,106,107,116,168,177,185\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\n1. Users may be on the system during installation of this patch.\nNOIS: REN-0501-61987\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Reno, NV\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*185 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIf you create a broadcast message and enter "Later" at the "Transmit"\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nprompt to send the message later, the job is tasked, but the message\nnever gets sent. This patch fixes it so that it does get sent.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*186\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\nXMJMOI 14358567 14395055 50,87,89,110,127,131,143,146,\n \n 148,154,172,177,186\nXMJMOR 14568568 14592944 50,75,110,131,177,186\nXMJMORX1 7025098 7116146 50,110,177,183,186\nXMS5A 3634911 4341470 55,50,173,186\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOIS: SBY-0501-32200\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*173 & XM*7.1*183.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\nTest Site: Salisbury, NC\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*186 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nIf a user is working on the same message in two differents sessions, an\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nabort my occur if the user attempts to save the message in both sessions.\n===========================================================================\n \nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*173 & XM*7.1*183.\n\n
\nPatch XM*7.1*187\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*182.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\nXMSERR 868666 877158 32,50,182,187\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS: none\nis at a minimum. It requires MailMan patch XM*7.1*182.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Site: FORUM\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*187 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nWhen sending a message from FORUM to GK, if GK does not like the FROM\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\naddress, it returns "501 Syntax Error". MailMan moves on to the next\nmessage, but does not delete the message from the queue or attempt to\nnotify the sender of the problem. This patch ensures that both actions\noccur.\n\n
\nPatch XM*7.1*188\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\nXMXUTIL2 7762911 7760090 50,188\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: WIC-0501-42618\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: Wichita, KS\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*188 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nMailMan makes a filtered broadcast message new, even though DELIVER NEW?\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nis set to NO in the filter. This patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*50.\n\n
\nPatch XM*7.1*189\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\nXMJMR 20504072 20744645 50,107,127,189\nXMJMS 5873945 6300984 50,120,130,189\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOIS: HUN-1100-22076, ALB-0301-52954, CTX-0401-70603\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\nTest Site: \n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*189 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nSometimes, when a user is editing a reply in one MailMan session, and then\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nstarts a second MailMan session, the reply message stub is killed by the\n===========================================================================\nsecond session. When the user returns to the first session and sends the\nreply, the reply appears to be from "* No Name *". This patch detects when\nthe stub has been killed, and recreates it.\n\n
\nMailMan patch XM*7.1*43 contains the following bug fix:\nThis patch may be installed at any time, except when the IN-BASKET-PURGE\nis running.\n===========================================================================\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\n the patch into a Transport Global on your system.\n3. On the KIDS:Installation menu, use the following options to install the\n\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n5. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \nNOIS: DAY-0397-41813\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMAI1 7933692 8026797 43\n\nRtns: ^XMAI1\n============================================================================\nTest Site: Dayton,OH\nTranslate the date of a remote-originated message to FileMan before comparing\nit to the purge date.\n\n===========================================================================\n\n
\nPatch XM*7.1*179\n"run routine" type. (Pre-init XMYPRE11 will help do this.)\n tells you when it started and ended, how long it took, how many messages were\n purged, and how many were left. \n \n Next, it displays information about each user in the MESSAGE file 3.7. It\n tells you how many messages they have in their mailboxes, when they last\n logged on, and when they last used MailMan. \n ROUTINE: STAT^XMA3 UPPERCASE MENU TEXT: MESSAGE STATISTICS\n\n\nNAME: XMUT-CHKFIL\n\n MENU TEXT: Check MailMan Files for Errors\n TYPE: run routine CREATOR: BEUSCHEL,GARY\n LOCK: XUPROG PACKAGE: MAILMAN\n DESCRIPTION: This option checks for and corrects errors in the MAILBOX file\n 3.7 and the MESSAGE file 3.9. It checks important fields and cross\n references. \n \n It is recommended that this option be run monthly or every few months, or\n whenever there seems to be a database problem. \n \nHere, then, are the options:\n It produces a report of the errors detected, and what, if anything, it did to\n fix them. If it didn't fix them, it tells you what you can do to fix them. \n \n Although the system will not fail because of errors detected, your users may\n call you about the problems they experience. This utility will allow you to\n detect them first and correct them before anyone knows. \n ROUTINE: CHKFILES^XMUT4 SCHEDULING RECOMMENDED: YES\n UPPERCASE MENU TEXT: CHECK MAILMAN FILES FOR ERRORS\n\nNOTE: This patch should be installed during off hours, when user activity\n\nis at a minimum. It requires MailMan patch XM*7.1*177.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------------\nNAME: XMCLEAN MENU TEXT: Clean out waste baskets\nXMA3 17147624 11956377 37,54,69,50,179\nXMA30 7080895 10546676 37,50,179\nXMUT4 13628025 13898092 50,74,108,179\nXMUT41 5625084 6742163 108,179\nXMUT4B 20142397 1683 50,108,179\nXMUT4BA 16544870 2138 50,108,136,179\nXMUT4C 7618380 8586474 10,22,50,108,136,177,179\nXMYPRE11 687829 239841 163,179\n* Checksums produced by CHECK^XTSUMBLD\n\n TYPE: run routine CREATOR: POSTMASTER\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*177.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n DESCRIPTION: This option empties users' WASTE baskets, that is, it deletes\n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n all the messages in users' WASTE baskets in the MAILBOX file 3.7. Messages in\n Select INSTALL NAME: XM*7.1*179 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n the MESSAGE file 3.9 are not affected. \n\n DEVICE: HOME// <It's up to you, you may queue it if you wish.>\n -----------------------------------------------\n (Just don't queue it for a time when XMCLEAN, XMAUTOPURGE, or XMUT-CHKFIL\n will be running!)\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n \n\n It is recommended that this option be scheduled to run daily, right before\n option XMAUTOPURGE. \n ROUTINE: CLEAN^XMA3 SCHEDULING RECOMMENDED: YES\n UPPERCASE MENU TEXT: CLEAN OUT WASTE BASKETS\n\n\nNAME: XMPURGE MENU TEXT: Purge Unreferenced Messages\n TYPE: run routine CREATOR: POSTMASTER\n DESCRIPTION: This option, if scheduled, does exactly what option\n XMAUTOPURGE does, and then stops. \nE3R 15242\n \n This option, if run interactively, does exactly what option XMAUTOPURGE does,\n and then it does exactly what option XMSTAT does, and then it stops. \n \n You should NOT schedule this option. \n ROUTINE: SCAN^XMA3\n UPPERCASE MENU TEXT: PURGE UNREFERENCED MESSAGES\n\n\nNAME: XMAUTOPURGE\nTest Sites: Puget Sound HCS\n MENU TEXT: Automatic Purge of MailMan Messages\n TYPE: run routine CREATOR: POSTMASTER\n DESCRIPTION: This option automatically purges unreferenced MailMan messages,\n that is, it deletes from file 3.9, MESSAGE, any messages which are not in \n anyone's basket. It is strongly recommended that this option be scheduled to\n run daily, right after option XMCLEAN. \n \n The following messages are considered 'referenced', and will not be purged: \n - Messages in user baskets \n - Messages in transit (arriving or being sent) \nMake tasked options XMCLEAN, XMAUTOPURGE, XMPURGE, and XMUT-CHKFIL honor\n - Server messages \n - Messages being edited (including aborted edits) \n - Messages which have been latered \n \n Several fields in file 4.3, MAILMAN SITE PARAMETERS, influence the behavior of\n this option. Here they are, but feel free to look at their Data Dictionary\n descriptions for more information on them: \n \n 4.301 - NO-PURGE DAYS BUFFER - MailMan does not purge any messages created or\n received in the last few days. You choose how many days. The default is 2. \nTaskMan stop requests.\n \n 142 - NO-PURGE DAYS BUFFER (LOCAL) - MailMan does not purge local messages\n created in the last few days. You choose how many days. The default is 7. \n \n 4.304 - WEEKDAY DAYS TO PURGE - On Saturdays, MailMan goes through the entire\n MESSAGE file looking for messages to purge. On the other days of the week,\n however, MailMan has the option of only looking at messages created or\n received recently. You choose how many days. The default is to go through\n the entire MESSAGE file. It is strongly recommended that you set this field\n to something reasonable, like 30 to 60 days. (But only if you follow the\n\n recommendation to schedule this option to run daily. Otherwise leave this\n field blank.) \n \n 4.303 - AUTOMATIC INTEGRITY CHECK - MailMan gives you the option of running\n the MAILBOX file portion of the integrity checker (option XMUT-CHKFIL) before\n it actually purges the unreferenced messages. The M xref on file 3.7 is used\n to determine whether a message is referenced (in someone's basket) or not. If\n the M xref is messed up, then the purge might delete messages it shouldn't, or\n leave message it should delete. The integrity checker ensures that the M xref\n is correct. You choose whether to run it or not. The default is to run it. \nImprove the description for options XMCLEAN, XMAUTOPURGE, XMPURGE, XMSTAT,\n The recommendation is to run it. However, if you find that it is simply\n taking too long, you may opt not to run it. If you opt not to run it, then it\n is recommended that you schedule option XMUT-CHKFIL to run monthly, because\n globals can and do become corrupted. \n INDEPENDENTLY INVOCABLE: NO\n ROUTINE: EN^XMA3 TIMESTAMP: 55536,32239\n TIMESTAMP OF PRIMARY MENU: 54318,54986\n SCHEDULING RECOMMENDED: YES\n UPPERCASE MENU TEXT: AUTOMATIC PURGE OF MAILMAN MES\n\nand XMUT-CHKFIL. Change option XMPURGE from an "action" type to a\n\nNAME: XMSTAT MENU TEXT: Message statistics\n TYPE: run routine CREATOR: POSTMASTER\n PACKAGE: MAILMAN\n DESCRIPTION: This interactive option displays information about past purges\n and about current mailbox usage. This option should not be scheduled. \n \n First, it displays the types and results of the last 20 purges of the MESSAGE\n file 3.9. It tells you whether the purge was an unreferenced message purge\n (option XMPURGE or XMAUTOPURGE), or a date purge (option XMPURGE-BY-DATE). It\n\n
\nPatch XM*7.1*190\nwill ensure that all recipients, even those with forwarding addresses,\nsee the intended reply.\n \nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*172.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMXSEC2 27625845 28416133 50,89,95,110,146,172,190\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n===========================================================================\n \nNOIS BHH-0701-40720\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*172.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\nTest Sites: BLACK HILLS HCS\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*190 Loaded from Distribution <date/time>\n ==========\n Install Questions:\nCurrently, broadcast message replies are delivered, but are not seen as\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\nnew to the users. This is because such broadcasts do not have recipient\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nlists (under QD), and MailMan uses recipient lists to deliver replies.\nTo fix this, MailMan will no longer permit a reply to such broadcasts.\nA new broadcast message will have to be sent, in lieu of a reply. This\n\n
\nPatch XM*7.1*191\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMP1 19119781 19097000 40,50,75,110,133,148,172,191\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*172.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS GRJ-0701-52169\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: Grand Junction, CO\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*191 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nThis patch expands the display of a message's vaporize date from a 2-digit\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nyear to a 4-digit year.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*172.\n\n
\nPatch XM*7.1*192\npatch closes some loopholes which caused some users to be targeted for\nmailbox deletion, when they really shouldn't have been.\n\nSome users never log on, but have forwarding addresses and have all their\nmail forwarded. Previously, these options might have deleted their\nmailboxes. Now, a report suggests further investigation.\n\nSome users never log on, but have surrogates read and answer their mail.\nPreviously, these options might have deleted their mailboxes. Now, they\nare left alone.\n\n\nSome users don't log on traditionally, so their last logon date might be\nreally old. However, they do manage to read mail, one way or another.\nPreviously, these options might have suggested their mailboxes be deleted.\nNow they are left alone.\n\nTwo more columns have been added to the XMMGR-TERMINATE-SUGGEST report.\nIf a user has been DISUSER'd, the user is included in the report, and that\nfact is noted on the report. Also, if the user has any surrogates, one of\nthem is shown. (Space limitations prevent showing more than one.)\nNOIS ISW-0701-21674\n\nOption descriptions are updated.\n\nAdditionally, if a user's mailbox is deleted, MailMan now looks to see if\nthe user is a coordinator or organizer of any mail group. If so, MailMan\nreplaces the user with the Postmaster. Previously, those fields were not\nchecked at all.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*180.\nTest Sites: OIFO-Washington; Oklahoma City\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMUTERM 13770249 7174403 50,125,180,192\nThis patch concerns options XMMGR-TERMINATE-MANY and XMMGR-TERMINATE-SUGGEST,\nXMUTERM1 14564305 17136578 50,125,192\nXMUTERM2 * NEW * 10569752 192\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nXMUTERM2 - no user-callable entry points\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nwhich check to see if users should have their mailboxes deleted, because they\nis at a minimum. It requires MailMan patch XM*7.1*180.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nhaven't used MailMan in a while, or because there's something screwy about\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*192 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\nthem in the NEW PERSON file, such as a missing access or verify code or main\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\nmenu, or they were terminated and were allowed to keep their mailbox. This\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\n
\n * * * * * * * * * * * * * * * * * * * *\nNOIS ISW-0801-20974\nTest Sites: OIFO Washington\n\nIf you use the MailMan option for transferring VistA email messages via\ndisk/tape to another site, you will have problems if the SEND field\nsetting for the TAPE entry in the Communications Protocol file is wrong.\nThe SEND field for the TAPE entry must be set to:\n\nSEND: W XMSG,! ; S XMTRAN="S: "_XMSG D TRAN^XMC1\n ==\n !! A T T E N T I O N !!\nMost of the entries we have found for this don't have the ",!" following\nthe "W XMS". Without the ",!" you don't get the line feed at the end of\neach line. This causes a buffer overflow when you try to receive the\nmessage. Please look at your entry, and edit, if necessary:\n\nUsing FileMan:\n\nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n =====\nINPUT TO WHAT FILE: COMMUNICATIONS PROTOCOL// <press enter>\n You must manually CHECK an entry in the\nEDIT WHICH FIELD: ALL// SEND\n ====\nTHEN EDIT FIELD: <press enter>\n\n\nSelect COMMUNICATIONS PROTOCOL NAME: TAPE\n ====\nSEND: W XMSG ; S XMTRAN="S: "_XMSG D TRAN^XMC1 Replace MSG With MSG,!\n === =====\n Replace <press enter>\n COMMUNICATIONS PROTOCOL FILE\n W XMSG,! ; S XMTRAN="S: "_XMSG D TRAN^XMC1\n\nSelect COMMUNICATIONS PROTOCOL NAME:\n\nNOTE: This patch may be installed at any time. Even though the patch is\ninformational, please install it, so that the patch installation message\nis sent to FORUM. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES: This patch contains no routines\n and CORRECT it, if necessary.\n\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time. Even though the patch is\ninformational, please install it, so that the patch installation message\nis sent to FORUM. It requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n * * * * * * * * * * * * * * * * * * * *\n3. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Print Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*193 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n===========================================================================\nPatch XM*7.1*193\n\n\n
\nPatch XM*7.1*196\nread and reply to messages normally, or to leave the unsent message alone\nand still be able to read messages, but not reply to them.\n\nIf a surrogate with send privilege assumes a user's identity, and\nthat user is logged on and composing a message, the surrogate is thrown\noff the system. This patch takes a gentler approach. The surrogate is\ntold that the session is concurrent with another, and is not thrown off.\n\nIf a user starts up a second MailMan session while in the middle of\nediting a message in the first MailMan session, the user may be thrown\n\noff the system. This patch takes a gentler approach. The user is told\nthat the session is concurrent with another, and is not thrown off.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*189.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\nNOIS: DUB-0801-31849, TOG-1099-10040, FAV-0300-71554, MON-1099-50906\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\nXM 11099027 11391363 17,35,50,140,144,149,168,196\nXMJMR 20744645 10586054 50,107,127,189,196\nXMJMR1 * NEW * 10598504 196\nXMJMRO 5033137 5040542 50,89,110,127,172,196\nXMJMS 6300984 7995221 50,120,130,189,196\nXMYPRE7 35006 25031 127,148,196\nTest Site: Dublin, GA; Fayetteville, AR; Montana HCS\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*189.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nIf a surrogate with just read privilege (not send) assumes a user's\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*196 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nidentity, and that user has an unsent message in the buffer, the surrogate\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nis thrown off the system. This patch takes a gentler approach. The\nsurrogate can now decide whether to delete the unsent message and then\n\n
\nPatch XM*7.1*194\nthe connection.\n\nMailMan has code designed to detect bad forwarding addresses and remove\nthem. It makes the decision to delete a forwarding address based on\nreceiving an error (any error!) from the remote site after having given\nthe remote site a message recipient. Unfortunately, DOMAIN.EXT's anti-\nspam measure has caused MailMan to delete perfectly good forwarding\naddresses. This patch changes what MailMan does once a remote site says,\n"Stop! I can't can't take any more!":\n1) MailMan doesn't delete the user's forwarding address.\n\n2) MailMan stops trying to add more recipients.\n\nHere's a sample of the messages which let the user know his forwarding\naddress was deleted (inappropriately!).\n\nSubj: Forwarding Address Deleted [#34506097] 14 Aug 01 13:02 4 lines\nFrom: POSTMASTER - COMPUTER PROGRAMMER In 'IN' basket. Page 1\n----------------------------------------------------------------------\nYour forwarding address: <not shown>@DOMAIN.EXT\nhas been deleted because it is not valid.\nNOIS PUG-0801-51201\nThe error message is:\n552 Too many recipients, max 50\n\nSubj: Forwarding Address Deleted [#34506097] 14 Aug 01 13:02 4 lines\nFrom: POSTMASTER - COMPUTER PROGRAMMER In 'IN' basket. Page 1\n----------------------------------------------------------------------\nYour forwarding address: <not shown>@DOMAIN.EXT\nhas been deleted because it is not valid.\nThe error message is:\n221 Closing connection\nTest Site: Puget Sound HCS\n\nThis patch ensures that a user's forwarding address will not be deleted as\na result of error messages such as those above.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*159, *173, *179 & *182.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMA32 8333956 8481844 37,50,159,194\nXMSM 7427993 7510310 4,6,13,20,50,176,182,194\nXMSMAIL 4266449 4582357 59,50,107,176,173,194\nXMUT4 13898092 13944070 50,74,108,179,194\n* Checksums produced by CHECK^XTSUMBLD\nDOMAIN.EXT (or the gateway to it) sometimes sets limits on the number\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*159, *173, *179 & *182.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nof recipients that can be on a message sent from another site. It's\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nan anti-spam measure. Once it hits that number, it won't accept any\n Install Package(s)\n Select INSTALL NAME: XM*7.1*194 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nmore recipients, and if the site tries to send more, DOMAIN.EXT closes\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\n
\nPatch XM*7.1*195\nas the password, the recipient (remote or not) will be able to open it\nby entering any number of that character. For example, if the password\nis AAAAA, the recipient can open the message by entering AAA or AAAAAAA.\n \nFor this reason, this patch will prohibit the use of repeating characters\nas passwords for scrambled messages.\n \nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*153 & *163.\n============================================================================ \n \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMJMCODE 12139966 12533067 50,110,153,195\nXMXADDR4 7400001 7441891 107,148,163,195\nNOIS BRX-0801-12006\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*153 & *163.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nTest Sites: Bronx VAMC\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n \n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*195 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nIf you scramble a message with a string of 2's as the password, and send\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthe message to a remote site, the recipient will not be able to open it.\n \nIf you scramble a message with a string of any other repeating character\n\n
\nPatch XM*7.1*197\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*145 & *186.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n-----------------------------------------------------------------------------\nXMJBN 15087232 10845646 50,100,140,145,197\nXMJBN1 * NEW * 4689617 197\nXMJMOI 14395055 14514331 50,87,89,110,127,131,143,\n 146,148,154,172,177,186,197\nXMVVITAE 11186176 11306765 50,74,107,140,197\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nNOIS: ANN-0900-42146\nXMJBN1 - contains no user-callable entry points\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*145 & *186.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: Ann Arbor, MI\n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan or the\n background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*7.1*197 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*197\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nIf you ask MailMan to 'new' some of the messages you see while reading\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it, if you wish>\n -------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nnew messages, but you are thrown off the system for some reason before\nMailMan has a chance to 'new' them, those messages will not be newed.\nThis patch ensures that they will be, the next time you log on.\n\n
\nPatch XM*7.1*199\n\nThis patch also:\n- changes *7 to $C(7).\n- makes the menus appear faster by setting invalid choices to dialog file\nentry numbers, instead of dialog file text.\n- improves the file check of file 3.9 by checking the entire "C" xref of the\nrecipient multiple. Previously, only those related to local recipients were\nchecked; now, those of remote recipients are included, too.\n- uses dialog file entries in places they hadn't been used before.\n- makes the choices line up better when becoming a surrogate.\n\n- warns users who are sending a message Later that if they minused anyone\nfrom any groups, those minuses will be ignored. If they want the minuses\nto be honored, they must transmit the message now.\n\nNOTE: This patch should be installed during off hours, when user activity is\nat a minimum. It requires MailMan patches XM*7.1*155,*161,*170,*190 & *194.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\nNOIS none\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nXMA1B 705206 741680 50,199\nXMA2 1214246 1117192 5,6,10,15,39,50,199\nXMJBM 11317455 11354270 50,110,131,143,160,161,199\nXMJDIR 6123825 6153613 50,110,140,144,146,199\nXMJMLR1 5293649 5288778 50,72,110,148,155,199\nTest Sites: FORUM; OIFO Oakland\nXMJMOI1 8242009 8260018 110,154,172,199\nXMJMOIE 3061396 3136973 50,110,127,199\nXMJMSO 8864099 10097928 50,110,127,131,156,168,199\nXMS0A 9159707 9203659 2,13,55,50,170,199\nXMSMAIL 4582357 4045228 59,50,107,176,173,194,199\nXMUT4C 8586474 8591370 10,22,50,108,136,177,179,199\nXMVSURR 2918495 2862179 50,107,199\nXMXSEC1 12986076 12980312 50,95,110,130,131,146,199\nXMXSEC2 28416133 24844137 50,89,95,110,146,172,190,199\nXMXSEC3 4290614 3310628 110,199\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity is\nat a minimum. It requires MailMan patches XM*7.1*155,*161,*170,*190 & *194.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nIf you send a message to an AOL account, AOL reports to the recipient that\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nthe message is from an unknown sender at an unknown domain. Testing has\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*199 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nshown that this is because the header fields do not have a space after the\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\ncolon. This patch inserts a space after the colon, to make AOL happy.\n\n
\nMailMan patch XM*7.1*36 contains the following enhancements and bug fixes:\nNOIS: NOL-0896-70074 Routine: ^XMAD1A\nIf successful, X will have the value of the mail group internal entry number.\nIf unsuccessful, X will be zero.\n\nWhere:\n\nA =Mail group name (if new group)\n Mail group internal entry number (if existing group)\nB =Mail group type flag (0=public; 1=private)\nC =DUZ of organizer (.5=Postmaster assumed, if 0 passed)\nD =Self enrollment allowed flag (0=no; 1=yes)\nEnsures that recipient multiple records start from 1.\n.E=Array of members to be enrolled.\n Members must be local users.\n Array must consist of DUZ's only; not names.\n E(n)="", where n is the member's DUZ.\n.F=Mail group description array.\n F(1)="first line"\n F(2)="second line"\n etc.\nG =Silent flag (0=interactive; 1=silent)\n============================================================================\n\n\nNOIS: none\nReference message #23076068 on FORUM from Skip Williams. Correct the\ndocumentation on page 46 of the 'Programmer Reference Manual'.\nIn the Example, Step 3 -- Deliver Message to Recipients, the last line of\ncode should be:\n\n D ENT1^XMD ; Call for MailMan Delivery\n\nNOIS: none Routines: ^XMA21G,^XMA7G,^XMAD1,\nE3R: 7039,8898 Routine: ^XMA21A,^XMA21G\n ^XMAD1A,^XMA5A,^XMFAX\n DD: file 3.8, field 14 (new)\n file 3.8, field 15 (new)\n file 3.9, (within Recipient multiple)\n field 13 (new)\n file 3.9, (within Recipient multiple)\n field 14 (new)\n file 4.3, field 143 (new)\n\nMailMan, with this patch, is now able to fax messages. Currently, only FORUM\nUsers holding new security key "XM GROUP PRIORITY" may forward priority\n(to my knowledge) is able to take advantage of this new capability, which\nrequires the presence of the AKF* suite of fax software and files and fax\ncapability. The site manager should indicate whether or not the site is\nfax-enabled by setting the new field #143 in file 4.3 (default is "no"). \n\nTwo new mail group multiples have been added to the Mail Group file: Fax\nRecipient, and Fax Group. These multiples point to associated files in the fax\n(AKF*) suite. These files (^AKF("FAXR", Fax Rolodex, and ^AKF("FAXG", Fax\nGroup) must be populated through the fax suite. LAYGO through MailMan is not\npermitted. \nmail to groups.\n\nWhen a mail message is sent (or forwarded) to a mail group with these fax\nmultiples populated, the message is also transferred to the fax suite, and a\ntask is queued to fax the message to those recipients pointed to by the group. \n\nFax recipients are faxed only the original message. Replies to mail messages\nare not faxed. Replies are not delivered as e-mail to fax recipients, unless\nthey are also on the message as "normal" recipients. \n\nMailMan faxes do not have a cover page. They print in much the same way as a\n\nmessage is printed on a printer. \n\nIndividual fax recipients are stored in the recipient multiple of the message\n(identified as F.<fax recipient>). A "Query" of the message will reveal that\nthe message was sent to the Mail Group. A "Query Detail" will reveal fax\nrecipients, when the message was transferred to the fax suite, and the fax ID\nassigned to it by the fax suite, but will not reveal the transmission status. \n(The user can ascertain the transmission status via the fax suite and the fax\nID.) \n\nNOIS: PIH-0496-21979 Routine: ^XMA21A\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\nNOT INCLUDED in this patch is:\n1) a necessary change to ^AKFAX to enable it to\nrecognize a MailMan Fax so that it can suppress the cover page for MailMan\nfaxes and address the fax to the recipient ("MailMan Fax for ... ").\n2) a new field in file #589500 - ^AKF("FAX", FAX TRANSMISSION FILE\n589500,3 MAILMAN FAX 0;4 SET OF CODES\n '0' FOR NO;\n '1' FOR YES;\n HELP-PROMPT: Is this a MailMan-generated fax?\nIf NETWORK - MAX LINES @ SEND TO field is null in the KERNEL SITE PARAMETERS\n DESCRIPTION: Routine ^AKFAX checks this field to see if the\n fax is a MailMan generated fax. If it is, then\n 1) the fax cover sheet is suppressed and\n 2) two additional lines are added to the top of\n the fax, identifying the recipient and the fax ID.\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n\nFollowing are DD extracts of the new fields:\n\nSTANDARD DATA DICTIONARY #4.3 -- KERNEL SITE PARAMETERS FILE STORED IN ^XMB(1,\nfile, the default maximum message lines is no longer 2000 - it is unlimited. \n\n4.3,143 FAX ENABLED 0;19 SET OF CODES\n '0' FOR no; \n '1' FOR yes; \n HELP-PROMPT: Is your site fax enabled? \n DESCRIPTION: Your site is fax enabled if you have the suite\n of fax software and files (^AKF) and fax\n capability and you choose to allow faxes to be\n sent via MailMan. \n To send faxes via MailMan, Mail groups (file\n \n\n 3.8) must first be populated in the fax\n recipient and fax group multiples. Then, when\n a user sends a message to a mail group, the\n message is also faxed to any fax recipients in\n that mail group.\n Responses to the message are not faxed.\n \nSTANDARD DATA DICTIONARY #3.8 -- MAIL GROUP FILE STORED IN ^XMB(3.8, \n\n3.8,14 FAX RECIPIENT 8;0 POINTER Multiple #3.814\nIn connection with this, I am passing on a request from Brenda Bishop (via Hal\n3.814,.01 FAX RECIPIENT 0;1 POINTER TO FAX ROLODEX FILE (#589499)\n (Multiply asked)\n HELP-PROMPT: Enter the fax recipient who should receive \n faxes sent to this mail group. \n DESCRIPTION: This is a list of individual recipients who\n will receive by fax any mail sent to this\n mail group. They receive the original\n message only. They do not receive responses.\n CROSS-REFERENCE: 3.814^B \n 1)= S ^XMB(3.8,DA(1),8,"B",$E(X,1,30),DA)=""\nWhitley) @ ISC-BIRM.DOMAIN.EXT to all sites running CMOP (the Consolidated Mail\n 2)= K ^XMB(3.8,DA(1),8,"B",$E(X,1,30),DA)\n\n3.8,15 FAX GROUP 9;0 POINTER Multiple #3.815\n3.815,.01 FAX GROUP 0;1 POINTER TO FAX GROUP FILE (#589498)\n (Multiply asked)\n INPUT TRANSFORM: S DIC("S")="N XM S XM=$G(^(3)) I $P(XM,U,2)!(\n $G(XMDUZ,DUZ)=+XM)" D ^DIC K DIC S DIC=DIE,X=\n +Y K:Y<0 X\n HELP-PROMPT: Enter the fax group which should receive \n faxes sent to this mail group. \nOutpatient Pharmacy Package): \n DESCRIPTION: Each member of the fax group will receive by\n fax any message sent to this mail group. \n Only the original message will be faxed. \n Responses will not be faxed. \n SCREEN: S DIC("S")="N XM S XM=$G(^(3))\n I $P(XM,U,2)!($G(XMDUZ,DUZ)=+XM)"\n EXPLANATION: Group must be public or user must be\n (surrogate of) creator of group.\n CROSS-REFERENCE: 3.815^B \n 1)= S ^XMB(3.8,DA(1),9,"B",$E(X,1,30),DA)=""\n \n 2)= K ^XMB(3.8,DA(1),9,"B",$E(X,1,30),DA)\n\nSTANDARD DATA DICTIONARY #3.9 -- MESSAGE FILE STORED IN ^XMB(3.9,\n\n3.91,13 FAX RECIPIENT 0;11 POINTER TO FAX ROLODEX FILE (#589499)\n HELP-PROMPT: Enter the fax recipient \n DESCRIPTION: When the message is addressed to a fax\n recipient, this field points to the fax\n rolodex file. After the message is handed\n off to the fax software, the pointer in this\n"Sites using the Consolidated Mail Outpatient Pharmacy (CMOP) package are\n field is deleted, the STATUS field is deleted,\n and the FAX ID field is set to the fax ID\n number assigned to it by the fax software.\n CROSS-REFERENCE: 3.91^AFAX \n 1)= S ^XMB(3.9,DA(1),1,"AFAX",$E(X,1,30),DA)=""\n 2)= K ^XMB(3.9,DA(1),1,"AFAX",$E(X,1,30),DA)\n This cross reference makes it possible for\n MailMan to immediately find the recipients\n to fax a message to.\n\nadvised to set the Kernel site parameter field [NETWORK - MAX LINES @\n3.91,14 FAX ID 0;12 FREE TEXT (1-14 CHARS)\n HELP-PROMPT: Enter the fax ID\n DESCRIPTION: This is the fax ID as assigned to it by the\n fax software (^AKF*).\n\n===========================================================================\n\n This patch should be installed after hours, when user activity is at a\n minimum. You should put the XMUSER Option out of order and shut down\n mail delivery tasks. A cross reference ("F", on FORWARDING ADDRESS) is\nSEND TO] field to Null (without value)."\n being added to the MAIL BOX file, and a lock must be placed on the whole\n global for the duration of the indexing. If the lock cannot be obtained,\n the indexing of the new cross reference will not run. If the indexing does\n not run, you can do it later by running ^XMYPOST6 yourself. ^XMYPOST6\n will take about 1 minute per 2500 users in the ^XMB(3.7 global.\n===========================================================================\n \nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routine.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\nNOIS: TUC-0395-60417 Routine: ^XMA7G\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \nNOIS: ISF-0195-60010 Routine: ^XMAH0\n DD: file 3.8, field .01 - add "LAYGO" node\n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\n \n XMA0 9701230 10480365 15,36\n XMA01 2756871 2847569 36\n XMA1 9575986 9580091 31,36\n XMA21A 8186870 7475211 4,30,36\n XMA21G 9710102 11073971 31,36\n XMA5A 14213526 13683319 31,36\nPrevents users from adding a private mail group with the same name as a\n XMA7G 5426292 5211523 36\n XMAD1 7205963 7275936 24,27,36\n XMAD1A 5656044 6312375 36\n XMAH0 1594203 1761641 36\n XMAI2 1646281 1510945 36\n XMAP 8812311 8826127 24,36\n XMAPHOST 6366459 6157206 7,14,27,36\n XMBGRP 5496318 5680054 13,36\n XMFAX **new** 4957190 36\n XMR1A 6956680 6979581 13,36\npublic one.\n XMUT5G 380003 338629 36\n XMYPOST6 **new** 11500 36\n\n============================================================================\n\nNOIS: SPO-0595-50655 Routine: ^XMYPOST6\n DD: file 3.8, field .01 - remove identifier node\nRemoves the identifier (Coordinator field) from the .01 field of the Mail\nGroup file. (DBIA #1622)\n\nNOIS: None Routine: ^XMYPOST6\nMessage range will no longer delete when user times out answering question,\n DD: file 3.7, field 2 - add a cross reference\nAdd a new cross reference (F) on the FORWARDING ADDRESS field of the MAIL BOX\nfile. This enables the site manager to easily find and remedy bad forwarding\naddresses.\n\nNOIS: SBY-0695-30284 Routine: ^XMAP\nIf the user's institution field is set to null, '()' will no longer appear\nafter the user's name when showing institutions on mail messages.\n \nNOIS: ATG-0495-30025 Routine: ^XMA0\n"Are you sure?"\nIf you save a group of messages to a new mailbox, the zero node of the\nmessage multiple will be created. Previously, it hadn't been.\n\nNOIS: DAY-1096-41348 Routine: ^XMA1\nIf '^' is contained in the response to 'Select message action' prompt,\nMM will up-arrow out.\n\nNOIS: None Routine: ^XMA5A,^XMAI2,^XMAPHOST,^XMUT5G\nRemove references to the old user file: ^DIC(3\n\n\nNOIS: SDC-1296-61151 Routine: ^XMA0,^XMA1\nCorrect MailMan's response if the user chooses not to proceed with message\ntermination.\n\nNOIS: None Routine: ^XMA21G\nReference mail message #22778858 on FORUM from Milt Roberson. MM aborted\nwhen trying to expand a group which included a remote member at a numeric\naddress at compuserve.com. This fixes that.\n\nNOIS: BRX-0197-10241 Routine: ^XMA0,^XMA01\nNOIS: PHO-0896-61825 Routine: ^XMA21A\nAt the <save,delete,terminate,print> "which messages" prompt, if the user's\nanswer includes ^, then the function is aborted.\n\nE3R: 9311 Routine: ^XMA7G\nUsers enrolled in a mail group which does not allow self-enrollment can no\nlonger disenroll themselves.\n\nNOIS: None Routine: ^XMR1A\nPrevent subscript in global reference from being more than 64 characters long.\nReference FORUM msg #23054338.\nDomain names starting with a number are valid and will no longer be rejected.\n\nNOIS: MEM-0197-70649 Routine: ^XMBGRP\nRoutine no longer attempts to write to the screen during 'silent' calls.\nDocumentation corrected. Parameter 'D' in call to function $$MG^XMBGRP,\nif set to 0 will not allow self-enrollment in a group; 1 will allow.\n\nReplace the description of $$MG^XMBGRP on page 31 of the Programmer Reference\nManual with the following: \n\n============================================================================\n\n$$MG^XMBGRP\n\nThis extrinsic function is used to create a new mail group or to add members\nto an existing mail group. Only local users may be enrolled as members with\nthis function.\n\nUsage: S X=$$MG^XMBGRP(A,B,C,D,.E,.F,G)\n\n(B,C,D,.F are ignored if the mail group previously exists.)\n\n\n\nPatch XM*7.1*200\n\n INPUT TRANSFORM: K:$L(X)>110!($L(X)<1) X\n LAST EDITED: NOV 28, 2001\n HELP-PROMPT: Answer must be 1-110 characters in length.\n DESCRIPTION: This field is only used if FWD TYPE is\n Auto-Forward. This field lists the original\n user (and possibly the user's surrogate) who\n forwarded the message to the user with the\n forwarding address.\n\n3.91,8.04 FWD TYPE ORIGINAL F;5 SET\nHere are some scenarios:\n 'F' FOR Filter-Forward;\n 'R' FOR Regular-Forward;\n LAST EDITED: NOV 28, 2001\n HELP-PROMPT: What kind of forwarding, originally?\n DESCRIPTION: This field is only used if FWD TYPE is\n Auto-Forward. This field reveals how the\n message was forwarded to the user who had the\n forwarding address listing the recipient in\n the .01 field.\n\n\n Regular-Forward - A user simply forwarded this\n message to the user with the forwarding\n address. This is the default, if this field\n is null.\n\n Filter-Forward - A user has an active message\n filter listing the user with the forwarding\n address as a "forward to" person. This message\n was sent to the user and then automatically\n forwarded to the user during message delivery.\n1. A user has a forwarding address, with no local delivery. Someone\n\n Note that Auto-Forward is not a possibility,\n because Auto-Forward is allowed only to remote\n recipients or to devices or servers.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*163 & *177.\n============================================================================ \n\nROUTINES:\nforwards the user a message, and it gets auto-forwarded. We can't tell\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------\nXMJMQ 13062269 14102654 40,57,70,50,96,110,131,172,200\nXMKP 16277893 16071912 50,89,119,147,151,200\nXMKP1 * NEW * 1811191 200\nXMTDT 8336537 8338601 50,142,150,177,200\nwho forwarded the message to the user. This is the situation described\nXMXADDR 15486856 15771323 50,96,101,104,107,131,148,163,200\nXMXUTIL4 8751511 9367334 50,96,127,200\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\nXMKP1 - has no user-callable entry point\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nin the NOIS. Here's the QD before the patch:\nis at a minimum. It requires MailMan patches XM*7.1*163 & *177.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nANNA.GLYPTA@DOMAIN.EXT\n Install Package(s)\n Select INSTALL NAME: XM*7.1*200 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Incoming Files:\n 3.9 MESSAGE (Partial Definition)\n Note: You already have the 'MESSAGE' File.\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Forwarded by: GLYPTA,ANNA 27 Nov 01 11:11\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n\n\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nHere's the QD after the patch:\n\nANNA.GLYPTA@DOMAIN.EXT\n Auto-Forwarded by: GLYPTA,ANNA 27 Nov 01 11:11\n Forwarded to GLYPTA,ANNA by: OLEUM,LYNN\n\n2. Same scenario as above, but a different forwarder.\nHere's the QD before the patch:\n\nNOIS PUG-1101-52069\nANNA.GLYPTA@DOMAIN.EXT\n Forwarded by: GLYPTA,ANNA 27 Nov 01 11:11\n\nHere's the QD after the patch:\n\nANNA.GLYPTA@DOMAIN.EXT\n Auto-Forwarded by: GLYPTA,ANNA 27 Nov 01 11:11\n Filter-Forwarded to GLYPTA,ANNA by: PATCH,USER\n\n3. This is a simpler scenario. There's no question as to who forwarded\nTest Site: Puget Sound HCS\nthe message, but we're not sure how. Here's the QD before the patch:\n\nGLYPTA,ANNA\n Forwarded by: PATCH,USER 27 Nov 01 11:11\n\nHere's the QD after the patch:\n\nGLYPTA,ANNA\n Filter-Forwarded by: PATCH,USER 27 Nov 01 11:11\n\n\nThe API QD^XMXUTIL3 is enhanced to include this new information. Additional\nfields returned under XMTROOT for each recipient:\n"FWD TYPE" (present only if forwarding is not "regular")\n Type of forwarding.\n "F" - Filter-Forward\n "A" - Auto-Forward\n "R" - Regular-Forward (default)\n\n"FWD BY ORIG" (present only if "FWD TYPE" is "A")\n Name of the person, possibly followed by, in parentheses,\nWhen auto-forwarding or filter-forwarding messages, MailMan does not retain\n the name of the surrogate of the person, who forwarded\n the message to the recipient, who had auto-forwarding.\n\n"FWD TYPE ORIG" (present only if "FWD TYPE" is "A" and the "FWD BY ORIG"\n person filter-forwarded to the recipient.)\n Type of forwarding, which led to the auto-forwarding.\n "F" - Filter-Forward\n "R" - Regular-Forward (default)\n\nIn order to facilitate this, three new fields are added to the recipient\nthe event chain as well as it should. This can lead to questions as to how\nmultiple in file 3.9:\n\nSTANDARD DATA DICTIONARY #3.91 -- RECIPIENT SUB-FILE STORED IN ^XMB(3.9,\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n3.91,8.02 FWD TYPE F;3 SET\n 'F' FOR Filter-Forward;\n 'A' FOR Auto-Forward;\na message was forwarded. This patch addresses that problem by making it\n 'R' FOR Regular-Forward;\n LAST EDITED: NOV 28, 2001\n HELP-PROMPT: What kind of forwarding?\n DESCRIPTION: Regular-Forward - A user simply forwarded this\n message to the recipient in the .01 field.\n This is the default, if this field is null.\n\n Auto-Forward - A user has a forwarding address\n listing the recipient in the .01 field. This\n message was sent to the user and then\nclear how messages came to be forwarded.\n automatically forwarded to the recipient.\n\n Filter-Forward - A user has an active message\n filter listing the recipient in the .01 field\n as a "forward to" person. This message was\n sent to the user and then automatically\n forwarded to the recipient during message\n delivery.\n\n3.91,8.03 FWD BY ORIGINAL F;4 FREE TEXT\n\n
\nPatch XM*7.1*201\n\nIf you reply to a scrambled message while reading new messages, and hit\n'transmit', MailMan informs you that it is "scrambling..." your reply.\nIf you reply to a scrambled message while reading existing messages in a\nbasket, and hit 'transmit', MailMan fails to inform you that it is\n"scrambling..." your reply. This patch fixes that. \n\nIf an address to a remote, non-MailMan site has blanks in it (but no commas),\nthe blanks should be translated to underscores, but aren't. This patch fixes\nthat.\n\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*196 and *199.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nNOIS: none\nName Checksum Checksum Patch List\n-----------------------------------------------------------------------------\nXMJMLN 14755647 14794710 50,110,131,201\nXMJMRO 5040542 5049970 50,89,110,127,172,196,201\nXMSMAIL 4045228 4109319 59,50,107,176,173,194,199,201\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines:\n===========================================================================\n \nTest Site: Biloxi, MS\nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*196 and *199.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan or the\n background filer.\n\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*201 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*201\nIf the Postmaster goes into one of the baskets of messages waiting to be\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it, if you wish>\ntransmitted to a remote site, and does a query to find a particular set of\n -------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nmessages, and then tries to toggle the transmission priority on some of\nthem, MailMan will abort. This patch fixes that.\n\n
\n * * * * * * * * * * * * * * * * * * * * * * *\nTest Sites: Montana HCS; Biloxi, MS\n and other background tasks in step 4, be sure to restart them, too.\n8. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n9. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n10. On the KIDS:Utilites menu, use the following option to review the\ninstall:\n Install File Print\n\n\nReview the automatic synonym additions which occurred during the PRE-INIT.\nIf there were any errors noted for a particular domain, that domain did not\nhave its new name added as a synonym. (Error messages are preceded by ***,\nand tell you what was wrong.) You must correct the error manually and add\nthe synonym manually. Remember, you are not to change any domain name.\nJust add the new name as a synonym. \n\nReview the automatic domain name changes which occurred during the POST-INIT.\nIf there were any errors noted for a particular domain, that domain did not\nhave its name changed. (Error messages are preceded by ***,\nNOIS: none; E3R: none\nand tell you what was wrong.) You must correct the error manually and\nperform the name change manually.\n\nIf you have questions or need any help, please enter a NOIS.\n===========================================================================\n\nPatch XM*7.1*51, released May 2001, ensured that every VHA site had\na ".DOMAIN.EXT" synonym in the DOMAIN file. It also added new names as\nsynonyms for sites which requested name changes because of mergers, or\notherwise, and had name changes approved. \n\nThis patch will complete the 2-step domain name change process begun in\n ATTENTION!\npatch XM*7.1*51. The synonyms will become the new domain names, and the\nold domain names will become the synonyms. The domain names will be\nchanged in the transmission scripts. The names of the transmission queues\nwill be changed. (These are the Postmaster's baskets where the messages\nwaiting to be transmitted are kept.) And finally, the domain name of the\nsite will be changed, too, if it is one of the sites which requested it. \n\nThis will all happen automatically, during the post-init. It should take\nless than 5 minutes. You will be instructed to review the install file print\nto check for and correct any errors after the patch has been installed. \n After installing this patch, please\n\nThe domain name changes will not adversely affect the flow of mail.\n\nThis patch will also begin the 2-step domain name change process for the\nnext round of domain name changes. It will add as synonyms the desired\nnew names for sites which requested it. A future patch will complete the\ndomain name change process, once all sites have installed this patch.\n\nNOTE: This patch requires MailMan patch XM*7.1*51.\n============================================================================ \n Review the Install File Print for errors.\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMUDNC 13102674 14015749 50,51,198\nXMYPOSTA 4556859 3414561 50,51,198\n See the Installation Instructions for details.\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch requires MailMan patch XM*7.1*51.\n1. Users should not be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n * * * * * * * * * * * * * * * * * * * * * * *\n4. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. Place TaskMan in a WAIT State. Shut down the listeners.\n You may also wish to shut down HL7 filers/LLP's and other background\n tasks which may attempt to create new messages. During the installation\n of this patch, we do not want any messages coming in or going out.\n\n Users should not be on the system.\n6. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*198 Loaded from Distribution <date/time>\n ==========\nPatch XM*7.1*198\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// YES\n ===\n Enter options you wish to mark as 'Out Of Order': XMUSER MailMan Menu\n ======\n Enter options you wish to mark as 'Out Of Order': <press return>\n ==============\n Enter protocols you wish to mark as 'Out Of Order': <press return>\n\n ==============\n Delay Install (Minutes): (0-60): 0// <press return>\n ==============\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do not queue this.>\n --------------------\n7. Remove TaskMan from a WAIT State. If you shut down HL7 filers/LLP's\n\n
\nPatch XM*7.1*202\n\nE3R: 15051, 16001\nTest Site: Puget Sound HCS; FORUM\nCurrently, when displaying a list of messages using the Summary message\ndisplay, the number of characters allotted to the subject is the same as\nthe number of characters allotted to the sender. This patch changes that\nratio. Now twice as many characters are allotted to the subject as are\nallotted to the sender. This is the same ratio as has always been used\nin the Detail message display.\n\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*148.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\nNOIS: LAS-0102-62116\n-----------------------------------------------------------------------------\nXMJML 11937833 11875758 50,131,202\nXMXADDRD 9985665 9903650 50,104,107,148,202\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines:\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nTest Site: Las Vegas, NV; Puget Sound HCS; FORUM\nminimum. It requires MailMan patch XM*7.1*148.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan or the\n background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nIf a site has its own domain closed (FLAGS=C) in the Domain file 4.2,\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*202 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*202\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nMailMan will accept mail addressed to the site by its name, but reject\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it, if you wish>\n -------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nmail addressed to the site by any of its synonyms. This patch fixes that.\n===========================================================================\nThe mail is now accepted, regardless of whether it's addressed using the\nsite name or synonym, or the value of the FLAGS field.\n\n
\nPatch XM*7.1*203\nTest Site: FORUM\n\nIf a message in a remote transmit queue has already transmitted, but for\nwhatever reason is stuck in the queue, it holds up all the rest of the\nmessages in the queue. Manual intervention is required to delete the\nmessage from the queue. This patch fixes that. Such a message is now\nautomatically deleted from the queue.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*175 & *201.\n\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------------------------\nXMPH 4915924 4952939 34,50,175,203\nNOIS: DAY-0202-42705\nXMR1A 3017305 3080398 13,36,50,203\nXMSMAIL 4109319 4164879 59,50,107,176,173,194,199,201,203\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines:\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*175 & *201.\nTest Site: Dayton, OH\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan or the\n background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*203 Loaded from Distribution <date/time>\n ==========\n Install Questions for XM*7.1*203\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nIf MailMan detects a control character in a routine when creating a PackMan\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it, if you wish>\n -------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nmessage, it aborts with a "level" error. This patch fixes that.\n\nNOIS: none\n\n
\nMailMan patch XM*7.1*45 contains the following bug fix:\nMailMan from bombing and will delete non-existent mail group references\nduring mail group inquiry.\n\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order.\n===========================================================================\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\n the patch into a Transport Global on your system.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nE3R: 9706\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n5. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nRtns: ^XMA5,^XMHIG\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA5 1197080 11192062 31,45\nXMHIG * new * 4741088 45\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nOption: XMHELPGROUP\nTest Sites: Fort Meade, Brockton\nWhen a user deletes a mail group, references to it from other mail groups\nare not deleted. When a user gets help on a mail group which has a\nnon-existent mail group as a member, MailMan bombs. This patch will keep\n\n
\nMailMan patch XM*7.1*41 contains the following bug fixes and enhancements:\n L("SENDER") - sender's name\n\nReturns 4 new variables:\n L("SENDER DUZ") - sender's DUZ (null if remote)\n L("BSKT IEN") - basket IEN\n L("DATE FM") - date sent, in FileMan format (null if uncertain)\n L("BROADCAST") - 1 if message was broadcast; 0 otherwise\n\nPlease correct/include in documentation in 'MailMan V.7.1 Programmer Reference\nManual' pages 14-16.\n\n\n===========================================================================\nThis patch may be installed with users on the system.\n===========================================================================\n \nINSTALLATION:\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\n the patch into a Transport Global on your system.\n2. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nNOIS: IND-0297-42072\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n3. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n============================================================================ \n \nROUTINES:\nRtn: ^XMGAPI2\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMGAPI2 2120231 3885152 41\n\n============================================================================\nTest Site: Indianapolis,IN\nReturns info for broadcast message now, instead of returning error stating that\nuser is not sender or recipient. Returns message type correctly now. \n\nNote correct definition for the following variable:\n\n\n This patch corrects a missing node in bulletins that was introduced\n \n===========================================================================\nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for this routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'.\n 4. The patch has now been loaded into a Transport global on your\n with patch XM*7.1*24. NOIS MIN-0396-4104\n system. You now need to use KIDS to install the Transport global.\n 5. On the KIDS menu, under the 'Installation' menu, use the option \n 'Verify Checksum in Transport Global' and verify that all routines\n have the correct checksums.\n 6. On the KIDS menu, under the 'Installation' menu, use the option \n 'Install Package(s)'. Select the package 'XM*7.1*26' and proceed\n with install.\n 7. Answer YES to the question:\n 'Want to DISABLE Scheduled Options and Menu Options?'\n 8. Enter XMUSER at the question:\n\n 'Enter options you wish to mark as 'Out Of Order':'\n 9. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'.\n 10. AXP Sites, after patch has installed, rebuild your map set.\n ==================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n This MailMan patch is in KIDS format. Please make sure you follow the\n Name Checksum Patch List\n ----------------------------------------------------------\n XMB 7219230 3,7,24,26\n \n\n\n Installation instructions.\n\n===========================================================================\n This patch should be installed after hours, when there is minimum users on\n the system. You should put the XMUSER Option out of order.\n\n
\nMailMan patch XM*7.1*47 contains the following bug fix:\n\nThis user may act as surrogate for:\n\nUSER,ONE (No Privileges) <== bug\nUSER,TWO (Read and Write Privileges)\n\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order.\n===========================================================================\n\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\n the patch into a Transport Global on your system.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nNOIS: TOG-0597-11935\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n5. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\nRtn: ^XMA7\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA7 10079999 10080629 10,47\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nTest Site: Togus, ME\nWhen using the 'user information' option, in the list showing users for whom\nthe user may act as surrogate, the first user in the list shows\n'no privileges', no matter which privileges have been granted.\nThis patch fixes that bug.\n\n
\nMailMan patch XM*7.1*40 contains the following enhancements:\n a) recognizes partial last name, partial first name for the first time ever\n b) query by addressee's DUZ for the first time ever\n c) query by addressee's nickname for the first time ever\n3) enables 'Q name' to work on remote addressees for the first time ever!\n a) recognizes partial last name\n b) recognizes partial last name, partial first name\n c) recognizes partial last name, partial domain\n d) (does not work with I: or CC: remote addressees)\n4) enables 'Q name' to work on devices and servers (D. and S.) for the first\n time ever\n\n3) improves display aesthetics\n\nThe following concerns the RECIPIENT multiple of the MESSAGE file:\nThe "C" cross reference data has always existed for the .01 field (RECIPIENT).\nBut... the DD has the "C" xref on field 1 (LAST RESPONSE READ).\nSo... We switch the xref in the DD from field 1 to field .01. as follows:\nRoutine XMYPRE1 deletes the "C" xref on field 1 (LAST RESPONSE READ).\nThe partial DD in this patch sets the "C" xref on field .01 (RECIPIENT).\nSince the actual "C" xref data has always been on field .01, we don't need\nto do anything with the "C" xref data - just leave it alone.\nNOIS: MCM-0197-51792\n\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order.\n===========================================================================\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\nRtns: ^XMA1,^XMJMQ,^XMJMQ1,^XMJMP1,^XMXUTIL,^XMYPRE1\n the patch into a Transport Global on your system.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\nDD: file 3.9, field .01 of RECIPIENT multiple - adds "C" xref to DD\n5. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nTest Site: Miles City,MT; Bronx,NY\nXMA1 9580091 9717771 31,36,40\nXMJMP1 * new * 11388791 40\nXMJMQ * new * 14561364 40\nXMJMQ1 * new * 3291603 40\nXMXUTIL * new * 2338705 40\nXMYPRE1 * new * 32634 40\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nImproves the query (Q,QD,QN,Q name) function:\n1) makes coding clearer\n2) makes 'Q name' perform more like a FileMan lookup for local addressees\n\n
\nMailMan patch XM*7.1*44 contains the following enhancements:\nBroadcast mail is now delivered only to users who have an access code, a verify\n(Terminate user mailbox), and the other is headed "Deact VISTA Access"\n(Deactivate VISTA Access). Besides being of interest to the Site Manager,\nthis report is also designed to be submitted to other services. The intent is\nthat the other services would check one of the columns for each user in the\nreport and return the report to the Site Manager to act on. \n\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order. The filers should\nbe shut down. ^XMADJF1 is probably mapped on your system.\ncode, a primary menu, and a mail box.\n===========================================================================\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option to load\n the patch into a transport global.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n5. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \nROUTINES:\nFour new options have been added to XMMGR-DISK-SPACE-MANAGEMENT menu:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA32A 9601895 10911370 27,37,44\nXMADJF1 8481461 8709221 44\nXMGAPI3 2791662 3149530 29,44\nXMZTERM * new * 15108400 44\n\nXMZTERM1 * new * 14445630 44\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n----------------------------------------------------------------------------\nNAME: XMMGR-PURGE-MESSAGE MENU TEXT: Purge a message\nDESCRIPTION: This option enables you to purge any message.\n\nPurge means:\n\n-delete the message from all user mailboxes\n-delete the message from the MESSAGE global ^XMB(3.9\n-delete all responses from the MESSAGE global ^XMB(3.9\n\nPurge is not reversible. The message is gone forever.\n\n----------------------------------------------------------------------------\nNAME: XMMGR-TERMINATE-ONE MENU TEXT: Terminate one mail user\nDESCRIPTION: This option lets you remove the mailbox of any user\nwho meets the criteria of either the XMMGR-TERMINATE-MANY option or the\nNOIS: OKL-0497-70538\nXMMGR-TERMINATE-SUGGEST option.\nAs a result, the user will not receive any mail. \n\nRemember,\n-Whenever you give a user a new access code,\n the system gives the user a mailbox if he doesn't already have one.\n-Whenever a user logs on,\n the system gives the user a mailbox if he doesn't already have one.\n\n----------------------------------------------------------------------------\nE3R: 9173,9994\nNAME: XMMGR-TERMINATE-MANY MENU TEXT: Terminate many mail users\nDESCRIPTION: This option goes through the MAIL BOX global and removes any\nmailbox if\n- the user is not in the NEW PERSON file.\n- the user has no access code and was not terminated.\n- the user has no access code and was terminated w/o mailbox retention.\n- the user has an access code and primary menu, but no verify code, AND \n - has never signed on, since being added before a cutoff date. \n OR \n - last signed on before a cutoff date.\nRtns: ^XMA32A,^XMADJF1,^XMGAPI3,^XMZTERM,^XMZTERM1\n\nRemove means:\n- Delete user's private mail groups\n- Remove user from membership in all groups\n- Remove user as an authorized sender from all groups \n- Remove user from anyone's list of surrogates\n- Delete user's latered-messages list\n- Delete user's mail box\nAs a result, the user will not receive any mail.\n\nOptions: XMMGR,XMMGR-TERMINATE-ONE,XMMGR-TERMINATE-MANY,\nThis option can be run in 'test' or 'real' mode. \n\nThe report lists, in DUZ order:\n-The user's DUZ and name\n-Whether the user has an access code, verify code, and primary menu\n-When the user was added to the NEW PERSON file\n-When the user last signed on\n-When the user was terminated (if applicable)\n-If the user was terminated, then whether the site manager chose to delete\n the user's mailbox. (It's generally a good idea to go ahead and delete\n XMMGR-TERMINATE-SUGGEST,XMMGR-PURGE-MESSAGE\n the mailbox upon termination.) \n\n----------------------------------------------------------------------------\nNAME: XMMGR-TERMINATE-SUGGEST\nMENU TEXT: Terminate mail user suggestions\nDESCRIPTION: This option goes through the MailBox global and reports on\nusers who perhaps should have their mail access terminated. \n\nUsers are included in the report if\n- the user was terminated before a manager-supplied cutoff date\nTest Sites: Oklahoma City, OK; Prescott, AZ; St. Louis, MO; Houston, TX\n and allowed to keep a mailbox.\n- the user has an access code, verify code, and primary menu,\n but last signed on before a manager-supplied cutoff date. \n\nThis option does not terminate mail access. \n\nThe report page breaks on Service/Section and includes the following \ninformation: \n-User's DUZ and name\n-Whether the user has an access code, a verify code, and a primary menu\n\n-When the user last signed on\n-When the user was terminated (if applicable)\n-If the user was terminated, then whether the site manager chose\n to delete the user's mailbox. (Remember, you should usually answer 'yes'\n to this question, unless the user is coming back and needs to have his mail\n retained.)\n-How many new messages the user has. (New messages are never purged, except \n during purge-by-date purges.) \n\nFinally there are two blank columns. One is headed "Term User Mbox"\n\n
\nMailMan patch XM*7.1*46 contains the following bug fix:\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order.\n===========================================================================\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\n the patch into a Transport Global on your system.\n\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n5. AXP Sites, after patch has installed, rebuild your map set.\nNOIS: PAL-0597-61414\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA2C 3972504 4143045 46\nRtn: ^XMA2C\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nTest Site: Palo Alto, CA\nIf a user terminates the original message immediately after having copied it,\nthe first user in the recipient multiple is terminated, which is not\nnecessarily the user. This patch fixes this bug. \n\n\n
\nMailMan patch XM*7.1*52 contains the following fix\n\n===========================================================================\nThis patch should be installed with no users on the system and with the\nfilers shut down.\n===========================================================================\n \nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n\n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\nNOIS: IVM-0997-32203,WNY-0197-11745\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMADJF1 8709221 8724294 44,52\nRtn: ^XMADJF1\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nTest Site: Atlanta, GA\nResponses to messages with 9+ digit message numbers were being added to the\nmessage whose number was the 1st 8 digits of the message number. For example,\na response to message number 123456789 was added to message number 12345678.\nThis patch makes sure that responses are added to the correct message.\n\n
\nMailMan patch XM*7.1*48 contains the following bug fix:\n===========================================================================\nThis patch should be installed during off-peak hours when network mail\nactivity is low. This patch can be installed with users on the system.\n===========================================================================\n \nINSTALLATION:\n1. If any of these routines is mapped (on systems which allow mapping),\n disable mapping for the affected routine(s).\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads\n the patch into a Transport Global on your system.\n\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n4. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n5. AXP Sites, after patch has installed, rebuild your map set.\nNOIS: BRK-0197-10525\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMS 5910151 5835931 8,20,34,48\nRtn: ^XMS\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nTest Site: Brockton, MA\nCode $S($D(...):^(),1:"") replaced with $G(...).\nCode is functionally equivalent, but former code was causing problems at\nthe site.\n\n\n
\nMailMan patch XM*7.1*49 contains the following cautionary measure:\n===========================================================================\nThis patch may be installed at any time.\n===========================================================================\n \nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n\n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nNOIS: WIM-0897-20733\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMYPOST2 8288260 9070792 49\n\n* Checksums produced by CHECK^XTSUMBLD\nRtn: ^XMYPOST2\n============================================================================\nTest Site: Wilmington, DE\nUpon use of the "Christen a Domain" option, warns user that the facility\nname is about to be changed in the Kernel Site Parameters file, and asks\nthe user if s/he really wants to do this.\n\n\n
\nMailMan patch XM*7.1*53 contains the following bug fix:\nroutine ^XMA2C blew up with an undefined error. This patch fixes this bug. \n\n===========================================================================\nThis patch should be installed after hours, when user activity is at a\nminimum. You should put the XMUSER Option out of order.\n===========================================================================\n\nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \nNOIS: PUG-1097-50245\n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n TOG-0997-10285\nXMA2C 4143045 4163417 46,53\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n BRX-0897-12178\nRtn: ^XMA2C\nTest Site: Puget Sound HCS; Togus, ME; Bronx, NY\nThis patch fixes a bug introduced in patch XM*7.1*46. If a message had\ntoo many lines, too many responses, or too many recipients to copy, then\n\n
\nMailMan patch XM*7.1*54 contains the following bug fix:\n\n===========================================================================\nThis patch may be installed at any time.\n===========================================================================\n\nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n\n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \nNOIS: BOS-1097-12284\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA3 14547045 14693914 37,53\n\nRtn: ^XMA3\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nTest Site: Boston, MA\nThis patch fixes a bug introduced in patch XM*7.1*37. During the init for the\nunreferenced message purge, it $ORDERs through one global, but gets its record\nfrom another global. This patch makes sure it gets its record from the same\nglobal it $ORDERs through.\n\n
\nMailMan patch XM*7.1*56 contains the following bug fix:\n===========================================================================\n \nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\nNOIS: ISB-0697-32421\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMBGRP 5680054 8013060 13,36,56\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nRtn: ^XMBGRP\nTest Site: CIOFO-Birmingham\n$$MG^XMBGRP does not add members to mail groups correctly.\n\n===========================================================================\nThis patch may be installed at any time.\n\n
\n\n then reboot MSM on the NT machine. This will restart the TCP/IP poller.\n \n===========================================================================\nINSTALLATION:\n 1. This routine might be mapped on systems that allow mapping,\n so you will need to disable mapping for the routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'.\n This MailMan patch is in KIDS format. Please make sure you follow the\n 4. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 5. On the KIDS menu, under the 'Installation' menu, use the option \n 'Verify Checksum in Transport Global' and verify that all routines\n have the correct checksums.\n 6. On the KIDS menu, under the 'Installation' menu, use the option \n 'Install Package(s)'. Select the package 'XM*7.1*25' and proceed\n with install.\n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'.\n Installation instructions. This patch corrects an error with the TCP/IP\n 8. AXP Sites, after patch has installed, rebuild your map set.\n 9. MSM Sites, after patch has installed, move the routine XMRTCP to\n your NT machine. Then reboot MSM on the NT machine, this will\n restart the TCP/IP mail poller.\n ==================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n poller, on the NT machine, that was introduced with Kernel patch 18,\n Name Checksum Patch List\n ----------------------------------------------------------\n XMRTCP 2975517 8,25\n\n XU*8.0*18. NOIS: WRJ-0396-10453\n\n===========================================================================\n This patch can be installed with users on the system. This patch will only\n install 1 routine, XMRTCP. You must move the routine to your NT machine and\n\n
\nMailMan patch XM*7.1*55 addresses Y2K preparedness.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n\n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n===========================================================================\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMA32A 10911370 10902381 27,37,44,55\nXMDIR1 10096361 9721400 27,55\nXMRPCTS0 6044236 5929098 6,12,31,55\nXMRTCPGO 2862153 2857890 8,55\nXMS0 9445201 9233148 13,8,20,23,27,34,55\nXMS0A 8601934 8144942 2,13,55\nXMS5 12968983 12887076 13,8,23,27,55\nXMS5A 4118857 3624422 55\nThis patch should be installed after-hours, when user activity is at a\nXMUT4A 4382977 4424419 34,55\nXMUT5R1 2850555 2356802 55\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nminimum. You should put the XMUSER option out of order. The filers should\nbe shut down.\n===========================================================================\n\nINSTALLATION:\n\n
\nMailMan patch XM*7.1*57 contains the following bug fix:\n===========================================================================\n \nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\nNOIS: ISA-0298-10292\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMJMQ 14561364 15112719 40,57\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nRtn: ^XMJMQ\nTest Site: CIOFO-Albany\nQD does not show status of messages sent to server or printer.\n\n===========================================================================\nThis patch should be installed when user activity is at a minimum.\n\n
\nPatch XM*7.1*61 is a replacement for patch XM*7.1*28, which was 'entered\n This patch is primarily for support of MSM-NT version 4.3 and OpenM-NT\n \n Select Option: 15 - Network Configuration\n \n Select Option: 12 - User-Defined Services\n \n Current User-Defined Services: \n \n Index Name Protocol Port Password Psize Start UCI Routine\n ----- ------------ -------- ----- -------- ----- ----- ------- -------\n 1 MSMRVG TCPIP 33086 MSMRVG BEG^WSAGENT\n NextGen 2.0.\n \n Enter Service Index: 2\n Enter Service Name: MAIL\n Enter Routine Reference: SOC25^XMRMSM\n Select UCI: VAH,ROU\n Enter Partition Size <40>:\n Enter Password: \n Enter TCPIP Port Number: 25\n Autostart?: Y\n \n \n Now you must remove the old Automatic Partition Startup entry for the Mail\n listener, who's Entry reference is ^XMRINETD. Reboot the MSM-NT box.\n \n=========================================================================== \n \n ROUTINES:\n Checksums were calculated using CHECK^XTSUMBLD\n The second line of the routine now looks like:\n\n Checksum\n This patch should be installed during off-peak hours when network mail\nRoutine Old New 2nd Line\nXMLTCP 2446407 2573202 **8,27,61**\nXMRMSM 400263 326967 **61**\nXMRONT new 598867 **61**\nXMRPCTS 4760679 4755631 **6,11,31,61**\nXMRPCTSA 3483840 3490824 **6,31,61**\n\nCallable entry points in new routines\nXMRONT none\n \n activity is low. This patch can be installed with users on the system.\n=========================================================================== \n \n OPTION:\nNAME: XMRONT MENU TEXT: Start XMRONT TCP Listener\n This is the TCP/IP Listener for MailMan. This option should NOT\n be on any Menu and should NOT be run directly. It must be schedule to start \n every time the system is rebooted. You can schedule this option by using the\n 'Schedule/Unschedule Options' option under the 'Taskman Management' menu. You\n must specify the option XMRONT and then enter 'STARTUP' in the SPECIAL QUEUING\n field.\n===========================================================================\n ROUTINE: XMRONT SCHEDULING RECOMMENDED: YES\n \nDEFINITIONS:\n AXP = Dec AXP system running DSM on VMS\n MSM = PC running MSM on DOS\nin error'. This patch addresses the following NOIS:\n MSM-NT = PC running MSM on NT Version 4.3\n OpenM-NT = Dec ALPHA or PC running OpenM NextGen 2.0 or Cache on NT.\n \nINSTALL INSTRUCTIONS:\nAXP: Some of these routines might be mapped, so you will need to disable\n mapping for the affected routines.\n \nMSM-NT: Where TCP/IP Mail is running, kill the Mail listener. In the Manager\n account D ^KILLJOB and kill the job who's routine name is XMRINETD.\n \nBHH-0498-40242, BUT-0498-20230, GRJ-0498-50226\nOpenM-NT: Where TCP/IP Mail is running, kill the Mail listener. In the\n Manager account D ^RESJOB and kill the job who's routine name is XMRONT\n or it may be %ZISTCP, in either case it will own device |TCP|25.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS Distribution onto your system.\n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the patch in the Transport\n global.\n 3. Users can remain on the system. This patch can be queued and installed\n\n at any time. TaskMan can remain running.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n \nMSM: Answer YES to the question 'Want to MOVE routines to other CPUs?'.\n\n Enter the names of your Compute and Print server(s).\n \nAXP: After patch has been installed, rebuild your map set.\n \n ***AXP and MSM sites are done with the installation.***\n ***The rest of the install is for OpenM-NT and MSM-NT.***\n \nOpenM-NT: In the Production account job the Mail listener, J ^XMRONT.\n Also, schedule the option XMRONT to start everytime the system is\n rebooted. Do the following from the EVE menu:\n PREREQUISITES: XU*8.0*78\n \n Select Systems Manager Menu Option: Taskman Management\n ==================\n \n Select Taskman Management Option: Schedule/Unschedule Options\n ===========================\n \n Select OPTION to schedule or reschedule: XMRONT Start XMRONT TCP Listener\n ======\n \n===========================================================================\n Edit Option Schedule\n Option Name: XMRONT \n Menu Text: Start XMRONT TCP Listener TASK ID:\n __________________________________________________________________________\n \n QUEUED TO RUN AT WHAT TIME: <return>\n \n DEVICE FOR QUEUED JOB OUTPUT: <return> \n \n Q UEUED TO RUN ON VOLUME SET: <return> \n \n \n RESCHEDULING FREQUENCY: <return> \n \n TASK PARAMETERS: <return> \n \n SPECIAL QUEUEING: STARTUP \n =======\n_______________________________________________________________________________\nThis field is only for special jobs that need to start every time the\nsystem is rebooted.\n All sites should load this patch regardless of their operating system.\n \n \n \nMSM-NT: In your Manager account of your do the following:\n \n Do ^SYSGEN\n \n Select Option: 3 - Edit Configuration Parameters\n \n Select Configuration <ROU>:\n\n
\nMailMan patch XM*7.1*59 addresses NOIS CMH-0398-N2220.\n===========================================================================\n\nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\nMessages intended to be sent to or via a certain domain may unintentionally\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------\nXMR0B 9580242 9564128 4,6,13,34,42,62\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nbe sent via another domain. This patch fixes this problem.\n\n===========================================================================\nThis patch should be installed after-hours, when user activity is at a\nminimum. You should put the XMUSER option out of order. The filers should\nbe shut down.\n\n
\nMailMan patch XM*7.1*59 addresses problems caused during remote transmission\nIf the 'from' string contains illegal characters, the 'from' string will be\nenclosed in quotes.\n\nThe local site will not see the change in the 'from' string.\nThe receiving site will see the change.\n\nFor example:\n\n'National Patch Module' will become '"National Patch Module"'\n'<Patient Feedback Pkg>' will become '"Patient Feedback Pkg"'\nwhen a message's 'from' address contains illegal characters.\n\nMessages from users will continue to be treated as usual. That is, if the\nuser's name contains ',' or ' ', all ', .' will become '._+'.\nIf the user's name contains any other illegal characters, such as '()',\nthe entire user's name will be enclosed in quotes.\n\n===========================================================================\nThis patch should be installed after-hours, when user activity is at a\nminimum. You should put the XMUSER option out of order. The filers should\nbe shut down.\n\n===========================================================================\n\nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \nThis patch only addresses locally originating messages which are sent to\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\nremote sites.\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMSMAIL 4652921 5893340 59\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n\nAs the message is being transmitted to the remote site, MailMan examines\nthe 'from' string.\nIf the 'from' string is enclosed in "<>", the "<>" are stripped off.\n\n
\nMailMan patch XM*7.1*64 re-introduces an entry point which was inadvertently\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \nleft out of a routine in a previous patch (XM*7.1*55).\n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMUT5R1 2356802 2364104 55,64\n\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n===========================================================================\nThis patch may be installed at any time. It will not interfere with any\nuser activity.\n===========================================================================\n\nINSTALLATION:\n\n
\nMailMan patch XM*7.1*65 addresses a problem experienced on FORUM.\nThis patch adds a restriction to addressing groups with authorized senders,\nnamely, remote senders cannot send mail to such groups.\n\n===========================================================================\nThis patch should be installed after-hours, when user activity is at a\nminimum. You should put the XMUSER option out of order. The filers should\nbe shut down.\n===========================================================================\n\nINSTALLATION:\n\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \nSomeone from a remote site sent a message to G.EVERYBODY@FORUM. This group\n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nis used to broadcast messages VA-wide. There are four authorized senders\nName Checksum Checksum Patch List\n-------------------------------------------------------------\nXMA21G 11073971 11358760 31,36,65\nXMR 6876928 6901880 30,34,65\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nfor the group, one of which is POSTMASTER. The background job which receives\nmessages from remote sites has its XMDUZ set to .5, which is the POSTMASTER.\nSo MailMan considered this remote sender to be authorized to address the\ngroup. This is not acceptable.\n\n\n
\nMailMan patch XM*7.1*58 addresses the following NOIS:\n===========================================================================\nThis patch should be installed after-hours, when user activity is at a\nminimum. You should put the XMUSER option out of order. The filers should\nbe shut down.\n===========================================================================\n\nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nBRK-0897-10428, BRX-1196-10659, & HOU-0897-71511\n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n4. DSM Sites: After patch has installed, rebuild your map set. \n\nand was tested at those respective sites:\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMS5 12887076 12421886 13,8,23,27,55,58\nBrockton, MA; Bronx, NY; Houston, TX\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n\nAborts occasionally occurred during remote transmission when one transmission\ntask was attempting to add a record to the transmit audit multiple, just as\nanother task was killing the multiple. This patch fixes that.\n\n\n
\nMailMan patch XM*7.1*65 addresses NOIS ISD-0898-71122.\nmay occur.\n===========================================================================\n\nINSTALLATION:\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \nTest site is CIOFO-DALLAS.\n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n4. DSM Sites: After patch has installed, rebuild your map set. \n\n============================================================================ \n \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------\nXMP2 9454113 9332554 24,66\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\nProblem statement: When installing a packman global data with leading tildes,\na syntax error occurs. This patch fixes this problem.\n\n===========================================================================\nThis patch may be installed at any time. However, this patch should NOT\nbe loaded at the same time as any other patches, because a clobber error\n\n
\nMailMan patch XM*7.1*68 fixes a bug as described in NOIS TAM-1098-30390.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------\nXMAD1A 6312375 7330837 36,68\nTest site is Tampa, FL.\nXMJMQ 15112710 15192669 40,57,68\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n\nINSTALLATION:\nNote: This patch should be installed after-hours, when user activity is at a\nminimum.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n\n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n4. DSM Sites: After patch has installed, rebuild your map set. \nIf a remote address begins with "F.", MailMan thinks the address is a fax.\n============================================================================ \nThis patch ensures that MailMan does not confuse a fax address with a remote\naddress.\n\nNote: This patch should be installed after-hours, when user activity is at a\nminimum.\n\n
\n This Mailman patch will set the vaporization date for messages that are\n the parameter is set in the Routine field for the XMYB-BROADCAST-VA-WIDE\n Option.\n \n Case #1 - if Routine field looks like: ENT^XMGAPI3("*"), this means\n that the message was sent to ALL mail users, then the Vaporization date\n will be set to T+7.\n \n Case #2 - if the Routine entry looks like: ENT^XMAPI3(".6"), this means\n that the message was sent to *just* SHARED MAIL's IN BASKET, then the\n Vaporization date will be set to T+30.\n distributed via the XMYB-BROADCAST-VA-WIDE Server Option, for example, \n===========================================================================\n\n This patch can be installed with users on the system.\n===========================================================================\n\nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n Secretary Brown's Daily Message. The vaporization date is set only if\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n the message stays in the users IN BASKET. If a user saves the message to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n=========================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Name Checksum Patch List\n ----------------------------------------------------------\n another Basket, the vaporization date is not maintained. A user can enter\n XMGAPI3 2791662 29\n============================================================================\n a new vaporization date by entering 'V' at the 'MESSAGE Action' prompt.\n\n This patch will not effect broadcast messages that originate locally, but \n only those originated from FORUM. The vaporization date is depended on how\n\n\nMailMan patch XM*7.1*70 is a patch for a patch released in error (XM*7.1*68).\nminimum.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------\nIt fixes a bug as described in NOIS TAM-1098-30390.\nXMAD1A 6312375 7330837 36,70\nXMJMQ 15112719 15192669 40,57,70\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n\nINSTALLATION:\nNote: This patch should be installed after-hours, when user activity is at a\nminimum.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest site is Tampa, FL.\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n\n ==\n4. DSM Sites: After patch has installed, rebuild your map set. \n============================================================================ \nIf a remote address begins with "F.", MailMan thinks the address is a fax.\nThis patch ensures that MailMan does not confuse a fax address with a remote\naddress.\n\nNote: This patch should be installed after-hours, when user activity is at a\n\n
\nMailMan patch XM*7.1*67 adds a new key, 'XM NO BROADCASTS',\nThis IRA was initiated because users with accounts in multiple sites were\nseeing the same broadcast message everywhere they logged on. These users\nwanted a way to avoid broadcast messages.\n\nWhen and if you assign this key to a user, you should advise them that\nthey will not see any broadcast messages at all.\n\nThis patch also deletes two keys which are not used by MailMan:\nXMPRIORITY and XMPRIORITY-OVERRIDE\n\nin response to an Initial Requirements Analysis (IRA):\nNote: This patch may be installed at any time.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------\n"MailMan - Screen Out Selected Users".\nXMADJF1 8724294 9044468 44,52,67\nXMGAPI3 3149530 3505605 29,44,67\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n\nINSTALLATION:\nNote: This patch may be installed at any time.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nCoincidentally, it also fulfills the suggestion of E3R 10653.\n the patch into a Transport Global on your system.\n3. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\n Are you sure you want the BACKGROUND FILERS to STOP delivering mail? NO//YES\n ===\n << Background filer will stop soon. >>\n4. On the KIDS:Installation menu, use the following options to install the \n Transport Global: \n Verify Checksums in Transport Global \nThis patch was tested at Wilkes-Barre, PA.\n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n << Background filer will start soon. >>\n\n6. DSM Sites: After patch has installed, rebuild your map set. \n============================================================================\nAny user possessing the key 'XM NO BROADCASTS'\nwill NOT receive ANY broadcast messages.\n\n\n
\nMailMan patch XM*7.1*69 fixes a bug as described in NOIS ISH-0199-40487.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n-------------------------------------------------------------\nXMA3 14693914 14700672 37,54,69\nTest site: CIOFO-HINES.\n* Checksums produced by CHECK^XTSUMBLD\n============================================================================\n\nINSTALLATION:\nNote: This patch may be installed at any time.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. On the KIDS:Installation menu, use the following options to install the \n\n Transport Global: \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n Install Package(s) \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n4. DSM Sites: After patch has installed, rebuild your map set. \n============================================================================ \nUnder certain conditions, a message which is in the process of arriving\nfrom another site may be deleted from the Postmaster's ARRIVING basket,\nthus preventing it from being delivered, and causing it to eventually be\npurged from the system. This patch fixes this problem.\n\nNote: This patch may be installed at any time.\n\n
\nPatch XM*7.1*50. The BIG patch! It is important that you read this patch\nnew manuals are in PDF documents on the infrastructure web site at:\na. This patch should be installed after hours, when user activity is at a\nJust add the new name as a synonym. \n===========================================================================\nminimum. It should not be queued, because TaskMan should not be running.\nb. This patch requires Kernel patches XU*8.0*67, XU*8.0*112, and XU*8.0*113.\nc. For any site running MAS (all VAMCs), this patch requires FileMan patch\nDI*22.0*1. Caution: KIDS will not check for this patch because not all\nsites run MAS. It is up to each site running MAS to check for DI*22.0*1.\nd. All MailMan users, including fictitious users, must have an access code,\nor they will no longer receive mail.\ne. To shorten installation time, which runs about 1 hour per 200,000 messages\nin file 3.9, you might consider running the message purges the day before\nhttp://www.vista.domain.ext/\nthe installation:\n- XMMGR-PURGE-AI-XREF (AI x-Ref Purge of Received Network Messages)\n- XMPURGE-BY-DATE (Purge Messages by Origination Date)\n- XMAUTOPURGE (Automatic Purge of MailMan Messages)\nf. DSM sites running SlotMaster may see routine mapping problems with ZSLOT\nusers, even after disabling mapping. Therefore, such sites should consider\nthe following steps:\n- Shutdown ZSLOT on all nodes.\n- Disable all mapped XM routines.\n- Load this patch.\nsoftserv/infrastr.uct/notebook/active/xm_patch_50_notebook.htm\n- Enter manual edits.\n- Rebuild mapped routine sets.\n- Shutdown/restart all DSM configurations.\nAn alternative to the above steps is to disable all mapped XM routines about\na week before you load this patch. That way you wouldn't need to shutdown\nZSLOT or shutdown/restart DSM configurations.\ng. If your site is running POP3, you should immediately load patch XM*7.1*71\nafter installing this patch.\n============================================================================ \n \n- XM*7.1*50 Patch Description\nThis patch deletes the following routines:\nXMZTERM (replaced by XMUTERM in this patch)\nXMZTERM1 (replaced by XMUTERM1 in this patch)\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n- MailMan V.7.1 & XM*7.1*50 Release Notes\n----------------------------------------------------------\nXM 4976038 11416143 17,35,50\nXM0 3346676 580 4,42,50\nXMA 11666053 79959 4,18,50\nXMA0 10480365 573755 15,36,50\nXMA01 2847569 1068 36,50\nXMA02 6053078 879 4,5,50\nXMA03 7773789 66257 50\nXMA0A 6404929 1148 7,16,50\nXMA1 9717771 827 31,36,40,50\n- MailMan V.7.1 & XM*7.1*50 Getting Started\nXMA10 5587620 1067 50\nXMA11 11668318 19543 50\nXMA11A 6856608 291270 50\nXMA11B 3593034 1468 39,50\nXMA1A 3777724 1152 50\nXMA1B 7260820 705206 50\nXMA1C 1474193 99629 50\nXMA1E 1530615 1172 50\nXMA2 10059315 1214246 5,6,10,15,39,50\nXMA20 4266922 1071 50\n- MailMan V.7.1 & XM*7.1*50 User Manual\nXMA21 11321545 1920696 4,31,50\nXMA210 1920955 1364 31,50\nXMA21A 7475211 1466 4,30,36,50\nXMA21B 3903898 1472 50\nXMA21FWD 406565 2649 50\nXMA21G 11358760 1502 31,36,65,50\nXMA22 7780497 887 50\nXMA24 10721719 1091 31,50\nXMA25 5071849 1096 50\nXMA2B 4986311 4956922 50\n- MailMan V.7.1 & XM*7.1*50 Programmer Manual\nXMA2C 4163417 1166 46,53,50\nXMA2C0 9088344 1454 24,27,50\nXMA2R 4793721 3427633 27,50\nXMA3 14700672 17147624 37,54,69,50\nXMA30 7561526 7080895 37,50\nXMA32 12437801 6537619 37,50\nXMA32A 10902381 9900106 27,37,44,55,50\nXMA4 1695677 839 50\nXMA5 11192062 843 31,45,50\nXMA50 4115522 1083 50\n- MailMan V.7.1 & XM*7.1*50 Technical Manual\nXMA51 3840890 1088 50\nXMA5A 13683319 1168 31,36,50\nXMA6 986923 847 50\nXMA7 10080629 16522 10,47,50\nXMA7G 5211523 1206 36,50\nXMA7G1 1193700 1500 24,50\nXMAD0 481945 1143 50\nXMAD1 7275936 1148 24,27,36,50\nXMAD1A 7330837 1538 36,70,50\nXMAD1X 3265319 1676 50\n\nXMAD2 2503657 208202 31,50\nXMADA 1034 1034 50\nXMADDOC 1992 1992 50\nXMADDOC1 4357710 2578 50\nXMADDOC2 3589 2392 50\nXMADGO 2112000 10833 5,27,50\nXMADGO1 788007 2075 50\nXMADJ999 419074 2470 50\nXMADJF0 5354543 2029 50\nXMADJF1 9044468 2036 44,52,67,50\ndescription and follow the install instructions.\nHighlights of the patch:\nXMADJF1A 912544 2556 50\nXMADJF1B 4754529 2564 10,16,37,50\nXMAH 5026238 1544316 5,16,50\nXMAH0 1761641 1159 36,50\nXMAH1 8757966 2172709 4,50\nXMAI 4557700 923 50\nXMAI0 1750753 1163 50\nXMAI1 8026797 1168 43,50\nXMAI2 1510945 3037343 36,50\nXMAK 4457158 737 50\n- Addresses 54 distinct NOIS and 40 distinct E3R.\nXMAL0 7710735 1175 50\nXMAL0A 7458546 1565 50\nXMANON 836515 1806 7,50\nXMAP 8826127 951 24,36,50\nXMAP0 4991024 1191 27,50\nXMAP1 3005830 1196 50\nXMAPHOST 6157206 9890299 7,14,27,36,50\nXMASEC 4454626 46560 33,50\nXMB 7258608 4363515 3,7,24,26,27,50\nXMB1 8930890 830 31,50\n- For those sites requesting it, performs, along with follow-on patch\nXMBGRP 8013060 8135589 13,36,56,50\nXMBPOST 9856673 9626449 4,13,23,24,27,38,50\nXMC 4113929 3216956 13,50\nXMC1 6875049 7147079 4,13,20,27,50\nXMC11 11677623 11806932 50\nXMC11A 3517372 4391366 27,50\nXMC2 12142809 12105966 13,23,27,50\nXMC3 5809172 5862128 20,50\nXMC4 5412826 991572 50\nXMCD 5190692 5277071 50\n XM*7.1*51, automatic domain name change from .DOMAIN.EXT to .DOMAIN.EXT, as\nXMCTLK 9708749 9742452 10,27,50\nXMD 4879878 6535767 33,50\nXMDF 1706479 1431567 50\nXMDIRQST 7236196 7357280 9,50\nXMDIRRCV 1909690 1913144 37,50\nXMDIRSND 1583505 1897078 37,50\nXME 10528702 643 50\nXME1 8041932 839 50\nXMFAX 4957190 4921115 36,50\nXMGAPI2 3885152 3885630 41,50\n well as domain rename. This patch adds the new domain names as synonyms to\nXMGAPI3 3505605 2171233 29,44,67,50\nXMGAPI4 3952807 4204061 50\nXMHIG 4741088 5360885 45,50\nXMHIU * New * 5960638 50\nXMJBL * New * 4523065 50\nXMJBM * New * 12165199 50\nXMJBM1 * New * 4157424 50\nXMJBN * New * 10185228 50\nXMJBU * New * 1507122 50\nXMJDIR * New * 2003843 50\n the current domain names. XM*7.1*51 will actually change the domain names.\nXMJERR * New * 454500 50\nXMJMA * New * 2991838 50\nXMJMBULL * New * 1365629 50\nXMJMC * New * 8169036 50\nXMJMCODE * New * 11042686 50\nXMJMD * New * 7370754 50\nXMJMF * New * 18005162 50\nXMJMFA * New * 6204287 50\nXMJMFB * New * 15137131 50\nXMJML * New * 11033330 50\n (XM*7.1*51 will be released after all sites have installed XM*7.1*50.)\nXMJMLN * New * 13240819 50\nXMJMLR * New * 13545823 50\nXMJMLR1 * New * 6523962 50\nXMJMOI * New * 16872170 50\nXMJMOIE * New * 4582157 50\nXMJMOR * New * 14242356 50\nXMJMORX * New * 14790879 50\nXMJMORX1 * New * 2472219 50\nXMJMP * New * 16472134 50\nXMJMP1 11388791 14179283 40,50\n- Adds many new APIs.\nXMJMQ 15192669 16189088 40,57,70,50\nXMJMQ1 3291603 3608941 40,50\nXMJMR * New * 18651915 50\nXMJMRO * New * 2449032 50\nXMJMS * New * 6092728 50\nXMJMSA * New * 1939332 50\nXMJMSO * New * 12952439 50\nXMJMT * New * 10637487 50\nXMKP * New * 15443979 50\nXMKPL * New * 2060011 50\n- Replaces the old user help frames with an entire new set of help frames.\nXMKPLQ * New * 9249196 50\nXMKPO * New * 2606344 50\nXMP 8440919 8546955 4,24,50\nXMP2A 10037244 10101095 24,42,50\nXMP3 7025241 6844934 24,50\nXMPC 5263348 5352206 50\nXMPG 4354526 4353568 50\nXMPH 4842981 3963996 34,50\nXMPSEC 5817282 7152889 50\nXMR 6901880 14031423 30,34,65,50\n (The IRM help frames have not been updated.)\nXMR0 8606729 874 27,50\nXMR0A 3476739 2289812 27,50\nXMR0B 9564128 8875848 4,6,13,34,42,62,50\nXMR0BLOB 5117794 4867143 50\nXMR1 7053085 13292215 7,50\n (Cache' sites may have a different 'before' checksum and)\n (patch list for XMR1. Please disregard the differences.)\nXMR1A 6979581 3017305 13,36,50\nXMR2 7882048 6207716 50\nXMRENT 2303842 2263450 31,50\n\n- Makes many changes to the MailMan DDs.\nXMRMSM 326967 339884 61,50\nXMRONT 598867 621984 61,50\nXMRPCTS0 5929098 6262116 6,12,31,55,50\nXMRPCTS1 6929051 5691788 6,50\n (Your XMRPCTS1 'before' checksum may be)\n (different, because of your TWIX info. )\nXMRPCTSA 3490824 3495721 6,31,61,50\nXMRTCP 4812676 4798863 8,25,27,50\nXMRUCX 357201 841742 27,34,50\nXMS 5835931 5837542 8,20,34,48,50\n- Renames file 3.7 from MAIL BOX to MAILBOX.\nXMS0 9233148 9308250 13,8,20,23,27,34,55,50\nXMS0A 8144942 9199959 2,13,55,50\nXMS0BLOB 6815258 6975716 50\nXMS1 7375190 1321634 13,8,23,50\nXMS2 1293876 885 50\nXMS3 13059868 12996474 22,50\nXMS4 3616422 2836511 50\nXMS5 12421886 13329767 13,8,23,27,55,58,50\nXMS5A 3624422 3571279 55,50\nXMSERR 3651687 3280474 32,50\n- Renames file 4.3 from KERNEL SITE PARAMETERS to MAILMAN SITE PARAMETERS.\nXMSM 10210546 7239792 4,6,13,20,50\nXMSM1 1692536 1238 50\nXMSMAIL 5893340 4937839 59,50\nXMTDF * New * 3998255 50\nXMTDL * New * 18249122 50\nXMTDL1 * New * 5047763 50\nXMTDL2 * New * 8743997 50\nXMTDO * New * 1746764 50\nXMTDT * New * 5385940 50\nXMUDNC * New * 3683283 50\n- Improves global integrity checker.\nXMUPIN * New * 13825872 50\nXMUT1 8603321 3818573 50\nXMUT1A 4040808 3948769 50\nXMUT2 4770720 4582154 50\nXMUT4 4510855 17112758 50\nXMUT4A 4424419 1411742 34,55,50\nXMUT4B 8543914 18488496 50\nXMUT4BA 8604816 15364896 50\nXMUT4C 3745269 7228866 10,22,50\nXMUT5 4455724 5739686 50\n- Improves message search.\nXMUT5B 2824190 2644064 50\nXMUT5Q 8765057 8502082 50\nXMUT6 2438497 2312993 50\nXMUTERM * New * 15007949 50\nXMUTERM1 * New * 14471083 50\nXMUTPUR0 1145390 1365512 7,50\nXMVGROUP * New * 6214836 50\nXMVSURR * New * 2622785 50\nXMVVITA * New * 4126813 50\nXMVVITAE * New * 12045708 50\n- Insists that users must have a mailbox and an access code in order to\nXMXADDR * New * 18774539 50\nXMXADDR1 * New * 12069509 50\nXMXADDR2 * New * 6515109 50\nXMXADDRD * New * 9657048 50\nXMXADDRG * New * 15430701 50\nXMXANSER * New * 2242310 50\nXMXAPI * New * 6705900 50\nXMXAPIB * New * 3472533 50\nXMXAPIU * New * 596863 50\nXMXBSKT * New * 12393935 50\n receive messages. This is to ensure that messages do not accumulate in\nXMXBULL * New * 5479615 50\nXMXEDIT * New * 3880586 50\nXMXLIST * New * 10429141 50\nXMXLIST1 * New * 12554823 50\nXMXMBOX * New * 1289002 50\nXMXMSGS * New * 10966038 50\nXMXMSGS1 * New * 9891647 50\nXMXMSGS2 * New * 5670519 50\nXMXPARM * New * 19704732 50\nXMXPARM1 * New * 5916152 50\n inactive mailboxes, never to be deleted. It is very important that any\nXMXPARMB * New * 4788158 50\nXMXPRT * New * 3036286 50\nXMXREPLY * New * 4925239 50\nXMXSEC * New * 18599731 50\nXMXSEC1 * New * 12851118 50\nXMXSEC2 * New * 20994061 50\nXMXSEND * New * 10879355 50\nXMXTO * New * 1915321 50\nXMXUTIL 2338705 10432772 40,50\nXMXUTIL1 * New * 5489564 50\n ficticious user be properly set up so that mail deliveries to these users\nXMXUTIL2 * New * 7762911 50\nXMXUTIL3 * New * 3652490 50\nXMXUTIL4 * New * 9117363 50\nXMYMNEM 5559955 4398404 50\nXMYPOST2 9070792 7919115 49,50\nXMYPOST9 * New * 5996100 50\nXMYPOSTA * New * 2107256 50\nXMYPRE 4770905 3732264 50 \nXMYPRE2 * New * 12021025 50\nXMYPRE2A * New * 15738292 50\n are not stopped.\nXMYPRE2B * New * 3451238 50\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\n\nRoutine Callable at Description\n---------------------------------------------------------------------------\nXMHIU N/A\nXMJBL N/A\nTest Sites: DOMAIN.EXT; GATEWAY.DOMAIN.EXT; Indianapolis, IN;\n- Implements message filtering.\nXMJBM N/A\nXMJBM1 N/A\nXMJBN N/A\nXMJBU N/A\nXMJDIR N/A\nXMJERR N/A\nXMJMA N/A\nXMJMBULL N/A\nXMJMC N/A\nXMJMCODE N/A\n- Improves local message delivery system.\nXMJMD N/A\nXMJMF N/A\nXMJMFA N/A\nXMJMFB N/A\nXMJML N/A\nXMJMLN N/A\nXMJMLR N/A\nXMJMLR1 N/A\nXMJMOI N/A\nXMJMOIE N/A\n- Adds 'full screen' user interface for managing and reading messages.\nXMJMOR N/A\nXMJMORX N/A\nXMJMORX1 N/A\nXMJMP N/A\nXMJMR N/A\nXMJMRO N/A\nXMJMS N/A\nXMJMSA N/A\nXMJMSO N/A\nXMJMT N/A\n- Rewrites 'classic' user interface to improve maintainability.\nXMKP N/A\nXMKPL N/A\nXMKPLQ N/A\nXMKPO N/A\nXMTDF N/A\nXMTDL N/A\nXMTDL1 N/A\nXMTDL2 N/A\nXMTDO N/A\nXMTDT N/A\n- Most ^XMA* routines have been superseded by other routines.\nXMUDNC N/A\nXMUPIN N/A\nXMUTERM N/A\nXMUTERM1 N/A\nXMVGROUP N/A\nXMVSURR N/A\nXMVVITA N/A\nXMVVITAE INIT Initialize user setup information\n OTHER Setup as someone else\n SELF Return to oneself\n- (new) ^XMJ* routines comprise the user interface.\nXMXADDR N/A\nXMXADDR1 N/A\nXMXADDR2 N/A\nXMXADDRD N/A\nXMXADDRG N/A\nXMXANSER N/A\nXMXAPI ADDRNSND Address and send a message (doesn't handle msg body)\n ANSRMSG Answer a message\n CRE8XMZ Create a new message in message file\n DELMSG Delete messages from a basket\n- (new) ^XMK* routines perform message posting.\n FLTRMSG Filter messages\n FWDMSG Forward messages\n LATERMSG 'Later' messages\n MOVEMSG Move messages from/to a basket\n PRTMSG Print messages\n PUTSERV Put a message in a server basket\n REPLYMSG Reply to message\n SENDBULL Send a bulletin (returns XMZ)\n SENDMSG Send a message\n TASKBULL Send a bulletin (quicker, but does not return XMZ)\n- (new) ^XMT* routines perform message delivery.\n TERMMSG Terminate messages\n TOWHOM Check one message addressee\n VSUBJ Validate a message subject\n ZAPSERV Delete a message from a server basket\nXMXAPIB CRE8BSKT Create a basket\n CRE8MBOX Create a mailbox\n DELBSKT Delete a basket\n FLTRBSKT Filter messages in a basket\n FLTRMBOX Filter all messages in a mailbox\n LISTBSKT Get a list of baskets\n- (new) ^XMX* routines comprise the APIs.\n LISTMSGS Get a list of messages in one or all baskets.\n (Search criteria may be used.)\n NAMEBSKT Change the name of a basket\n QBSKT Get info on a basket\n QMBOX Query a mailbox\n RSEQBSKT Resequence messages in a basket\n TERMMBOX Remove all traces of a user from MM globals\nXMXAPIU READ Read/Manage messages in Mailbox (interactive)\n READNEW Read new messages in a Mailbox (interactive)\n SEND Send a message (interactive)\n- (new) ^XMV* routines comprise user identity.\n TOWHOM Address a message (interactive)\nXMXBSKT N/A\nXMXBULL N/A\nXMXEDIT CLOSED Toggle message 'closed'\n CONFID Toggle message 'confidential'\n CONFIRM Toggle message 'confirm receipt requested'\n DELIVER Set/delete delivery basket\n INFO Toggle message 'information only'\n PRIORITY Toggle message 'priority'\n SUBJ Change message subject\n Montana HCS, MT; San Francisco, CA; SAIC Corp.;\n- ^XMR* has been rewritten.\n TEXT Replace message text\n VAPOR Set/delete message vaporize date\nXMXLIST N/A\nXMXLIST1 N/A\nXMXMBOX N/A\nXMXMSGS N/A\nXMXMSGS1 N/A\nXMXMSGS2 N/A\nXMXPARM N/A\nXMXPARM1 N/A\n- Improves the remote message xref, ^XMBX(3.9,"AI", by enabling it to handle\nXMXPARMB N/A\nXMXPRT N/A\nXMXREPLY N/A\nXMXSEC $$ACCESS May user access message?\n $$ANSWER May user answer message?\n $$BCAST Is this a broadcast message?\n $$CLOSED Is this message closed?\n $$CONFID Is this message confidential?\n $$CONFIRM Is this message confirm receipt requested?\n $$COPY May user copy message?\nlonger message IDs. Specifically, the xref has changed\n $$DELETE May user delete message?\n $$FORWARD May user forward message?\n $$INFO Is this message information only?\n $$LATER May user later message?\n $$MOVE May user save/filter message?\n $$ORIGIN8R Did user send this message?\n $$POSTPRIV Does user have postmaster privilege?\n $$PRIORITY Is this message priority?\n $$READ May user read message?\n $$REPLY May user reply to message?\nfrom: ^XMBX(3.9,"AI",site@msgid,xmz)=fm date/time\n $$RPRIV Does surrogate have read privilege?\n $$RWPRIV Does surrogate have read/write privilege?\n $$SEND May user send a message?\n $$SURRACC May surrogate access message?\n $$SURRCONF May surrogate *not* access message?\n $$WPRIV Does surrogate have write privilege?\n $$ZCLOSED Is this message closed?\n $$ZCONFID Is this message confidential?\n $$ZCONFIRM Is this message confirm receipt requested?\n $$ZINFO Is this message information only?\nto: ^XMBX(3.9,"AI",site,msgid,xmz)=fm date \n $$ZORIGIN8 Did user send this message?\n $$ZPOSTPRV Does user have postmaster privilege?\n $$ZPRI Is this message priority?\nXMXSEC1 $$COPYAMT May the copy contain the requested responses?\n $$COPYLIMS Get the site's copy limits.\n $$COPYRECP May the copy be sent to the original's recipients?\n $$PAKMAN Is this a PackMan message?\n CHKLINES May this message be sent to a remote site?\n CHKMSG Is message really there & may user access it?\n GETRESTR Get restrictions on what user may do with message\nThe post-init will reconfigure the xref. (This could take anywhere from 1/2\n OPTGRP What may user do at basket/message group level?\nXMXSEC2 $$EDIT May user edit message?\n OPTEDIT If user may edit message, what may/may not be edited?\n OPTMSG What may/may not the user do with this message?\nXMXSEND N/A\nXMXTO N/A\nXMXUTIL $$BMSGCT Number of messages in user's basket\n $$BNMSGCT Number of new messages in user's basket\n $$BSKTNAME Basket name\n $$NAME User's name\nhour to several hours, depending on how large the global is.) Here's a tip:\n $$NETNAME User's network name\n $$NEWS Info on new messages in user's mailbox\n $$TMSGCT Number of messages in user's mailbox\n $$TNMSGCT Number of new messages in user's mailbox\n KVAPOR Edit message vaporize date in user's basket\n LASTACC Record info on user's last access of message\n MAKENEW Make message new\n NONEW Make message not new\n PAGE Enter RETURN to continue or '^' to exit:\n WAIT Press RETURN to continue:\nYou can cut down the time that this will take by running option\nXMXUTIL1 $$CONVERT Convert InterNet date/time to FileMan date/time\n $$CTRL Strip control characters\n $$DECODEUP ~U~ to ^\n $$ENCODEUP ^ to ~U~\n $$GMTDIFF +-HHMM difference from GMT\n $$INDT Convert FileMan date/time to InterNet date/time\n $$MAXBLANK Reduce 3 or more consecutive blanks to 2\n $$MELD Combine string and number\n $$MMDT Convert FileMan date/time to MailMan date/time\n $$SCRUB Strip control characters and leading/trailing blanks\nXMMGR-PURGE-AI-XREF (AI x-Ref Purge of Received Network Messages)\n $$STRIP Strip leading/trailing blanks\n $$TIMEDIFF Decimal time difference to +-HHMM\n $$TSTAMP Time stamp\n $$ZONEDIFF +-HHMM from another time zone\nXMXUTIL2 $$BSKT Which basket is message in?\n $$DATE Get message date.\n $$FROM Get message from.\n $$KSEQN Get message sequence number in user's basket.\n $$LINE How many lines are in the message?\n $$NEW Is this message new for this user?\nprior to installing this patch. This will reduce the number of xrefs in the\n $$PRI Is this message priority?\n $$QRESP Is this a response?\n $$RESP How many responses are in the message?\n $$SUBJ Get message subject.\n $$ZDATE Get message date.\n $$ZFROM Get message from.\n $$ZNODE Get message zero node.\n $$ZPRI Is this message priority?\n $$ZREAD How many responses has the user read?\n $$ZSUBJ Get message subject.\n German Heart Institute, Berlin, Germany; San Francisco CIOFO\nAI xref global.\n INMSG Message info\n INMSG1 General message info\n INMSG2 Specific message info\n INRESP Response info\n INRESPS Message response info\nXMXUTIL3 Q List message's addressees\n QD List message's recipients\n QL List message's later'd addressees\n QN List message's network header lines\nXMXUTIL4 N/A\n- Enables message number recycling. To do this,\nXMYPOST9 N/A\nXMYPOSTA N/A\nXMYPRE2 N/A\nXMYPRE2A N/A\nXMYPRE2B N/A\n===========================================================================\n \nINSTALLATION:\n\nNOTES:\n--A new field (17.1, MAX DIGITS FOR MESSAGE NUMBER) has been added to file\na. This patch should be installed after hours, when user activity is at a\nminimum. It should not be queued, because TaskMan should not be running.\nb. This patch requires Kernel patches XU*8.0*67, XU*8.0*112, and XU*8.0*113.\nc. For any site running MAS (all VAMCs), this patch requires FileMan patch\nDI*22.0*1. Caution: KIDS will not check for this patch because not all\nsites run MAS. It is up to each site running MAS to check for DI*22.0*1.\nd. All MailMan users, including fictitious users, must have an access code,\nor they will no longer receive mail.\ne. To shorten installation time, which runs about 1 hour per 200,000 messages\nin file 3.9, you might consider running the message purges the day before\n4.3, to let each site decide how large the numbers may get before they\nthe installation:\n- XMMGR-PURGE-AI-XREF (AI x-Ref Purge of Received Network Messages)\n- XMPURGE-BY-DATE (Purge Messages by Origination Date)\n- XMAUTOPURGE (Automatic Purge of MailMan Messages)\nf. DSM sites running SlotMaster may see routine mapping problems with ZSLOT\nusers, even after disabling mapping. Therefore, such sites should consider\nthe following steps:\n- Shutdown ZSLOT on all nodes.\n- Disable all mapped XM routines.\n- Load this patch.\nrecycle and start again (from 100000). The post-init will set it to\n- Enter manual edits.\n- Rebuild mapped routine sets.\n- Shutdown/restart all DSM c nfigurations.\nAn alternative to the above steps is to disable all mapped XM routines about\na week before you load this patch. That way you wouldn't need to shutdown\nZSLOT or shutdown/restart DSM configurations.\ng. If your site is running POP3, you should immediately load patch XM*7.1*71\nafter installing this patch.\n\nINSTRUCTIONS:\nthe maximum length of your site's existing message numbers. (If it's less\n1. This patch replaces routine ^XMRPCTS1, which contains your site's TWIX\n routing info. Before you install this patch, copy the current TWIX info\n from that routine at your site. After you install this patch, edit\n the new ^XMRPCTS1 to set your site's current TWIX info. Specifically:\nXMRPCTS1 ;(KC-VAMC)/XXX-Simple PCTS front end to MailMan ;03/19/98 11:10\n ;;7.1;MailMan;**6,50**;Jun 02, 1994\n N XMUS,XMFM,XMSTR,XMRI,XMTO,XMABORT\n ;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n ;All should be sent to XXX@VHA.DMIA the local PCTS Domain\n ;Edit these for your site. <---Copy your site's TWIX info\nthan 7, it will be set to 7. If it's greater than 14, it will be set to 14.)\n S XMUS="XXXX" ;Local routing indicator <---from this line\n S XMFM="YYYY" ;from line <---and this line\n I XMUS="XXXX"!(XMFM="YYYY") S %="FIX Routing codes !!!"_XMPCTS0("ERR")\n ;-------------------------------------------------------------\n2. The TIME ZONE field in file 4.3 must have your site's time zone in it.\n Please check and ensure that it is there.\n3. DSM SITES: Disable all mapped XM routines. In step 13, we'll rebuild\n the map set with *different* routines, because many have become obsolete.\n4. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option to load\n the patch into a transport global.\nYou may change it afterward.\n5. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer (XMAD)\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail NO// YES\n ===\n<<< Mail Deliveries will stop momentarily. >>>\n<< Background filer will stop before delivering the next message !!! >>>\n6. Stop TaskMan. You may also wish to shut down HL7 filers/LLP's and other\n background tasks which may attempt to create new messages.\n7. Place option XMUSER out of order. (We do it ourselves, instead of letting\n--A new field (31, LOCAL CREATE DATE) has been added to file 3.9. The post-\nKIDS do it, because we're going to place XMUSER back in order during the\npost-init.) To place XMUSER out of order, enter FileMan, and:\nVA FileMan 21.0\nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n ==========================\nINPUT TO WHAT FILE: OPTION// <press return>\n ==============\nEDIT WHICH FIELD: ALL// OUT OF ORDER MESSAGE\n ==================== \nTHEN EDIT FIELD: <press return>\ninit will go through the file 3.9, populate the new field with the date\n ==============\nSelect OPTION NAME: XMUSER MailMan Menu\n ======\nOUT OF ORDER MESSAGE: Loading MailMan patch XM*7.1*50\n ===============================\nSelect OPTION NAME: <press return>\n ==============\nSelect OPTION: <press return>\n ==============\n8. If you journal the global ^XMBX, your journal space may fill up when the\n\nthe message was sent, and create the new "C" xref. (This will take about\n ^XMBX(3.9,"AI", xref global is reconfigured. You may wish to disable\n journaling. To disable journaling:\n8a. DSM SITES: You may disable journaling for a particular global:\n >D ^%GLOMAN\n ==========\n Global Management Utility\n\n Global > ^XMBX\n ====\n ^XMBX is currently defined\n1 hour per 200,000 messages.) Here's a tip:\n\n 1. Show GLOBAL Characteristics\n 2. Change Access Privileges\n 3. Change Journaling Capability\n 4. Change DATA GROWTH AREA\n\n Enter option > 3\n =\n Journaling [E=Enabled/D=Disabled] <E> D\n =\nYou can cut down the time that this will take by running option\n - Characteristics updated\n\n 1. Show GLOBAL Characteristics\n 2. Change Access Privileges\n 3. Change Journaling Capability\n 4. Change DATA GROWTH AREA\n\n Enter option > <press return>\n ==============\n Global > ^<press return>\nXMPURGE-BY-DATE (Purge Messages by Origination Date)\n ==============\n8b. CACHE SITES: You may disable journaling for a specific job:\n %SYS>D DISABLE^%NOJRN\n ================\n8c. MSM SITES: Consult MSM documentation for how to disable journaling.\n9. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nand XMAUTOPURGE (Automatic Purge of MailMan Messages)\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*50 Loaded from Distribution <date/time>\n =========\n => <header> ;Created on <date/time>\n\n This Distribution was loaded on <date/time> with header of \n <header> ;Created on <date/time>\n It consisted of the following Install(s):\n XM*7.1*50\nprior to installing this patch. This will reduce the number of messages\n\n XM*7.1*50\n\n Install Questions for XM*7.1*50\n Incoming Files:\n\n 3.6 BULLETIN (Partial Definition)\n Note: You already have the 'BULLETIN' File.\n\n 3.7 MAILBOX\nin file 3.9.\n *BUT YOU ALREADY HAVE 'MAIL BOX' AS FILE #3.7!\n Shall I write over your MAIL BOX File? YES// <press enter>\n =============\n\n 3.73 MESSAGES TO BE NEW AT A LATER DATE\n Note: You already have the 'MESSAGES TO BE NEW AT A LATER DATE' File.\n\n 3.8 MAIL GROUP (Partial Definition)\n Note: You already have the 'MAIL GROUP' File.\n\n--The message purge processes have been changed to operate off LOCAL\n 3.9 MESSAGE\n Note: You already have the 'MESSAGE' File.\n\n 4.2 DOMAIN (Partial Definition)\n Note: You already have the 'DOMAIN' File.\n\n 4.2997 REMOTE USER DIRECTORY (Partial Definition)\n Note: You already have the 'REMOTE USER DIRECTORY' File.\n\n 4.2999 MESSAGE STATISTICS (Partial Definition)\nCREATE DATE. The date purge routine is now much faster, since it has an\n Note: You already have the 'MESSAGE STATISTICS' File.\n\n 4.3 MAILMAN SITE PARAMETERS\n *BUT YOU ALREADY HAVE 'KERNEL SITE PARAMETERS' AS FILE #4.3!\n Shall I write over your KERNEL SITE PARAMETERS File? YES// <press enter>\n =============\n\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n\nappropriate xref to work with. The weekday unreferenced messages purge can\n ----------------------------------------------------------------------\n NOTE: If you want users to be able to use MailMan during the post-init,\n it's important that you answer NO to the following question,\n otherwise KIDS will place all options in this patch out of order until\n the install is finished:\n ----------------------------------------------------------------------\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n\n ... <lots of installation stuff is shown> ...\nThe changes included in this patch are so extensive, that several of the\nfocus better and thus be more efficient.\n\n ----------------------------------------------------------------------\n NOTE: When the POST-INIT starts, continue with steps 10 through 17.\n The following is displayed when the post-init starts:\n\n Running Post-Install Routine: ^XMYPOST9\n\nFire xrefs on 'timezone' field of the MailMan site parms file.\n \nCheck/Redo AI xref...\n--Other fields have changed their focus from message number to the LOCAL\n ----------------------------------------------------------------------\n\n ... <lots of installation stuff is shown> ...\n\n XM*7.1*50 Installed. \n <shows date and time>\n \n Install Message sent #<shows message number>\n\n Starting Menu Rebuild: <shows date and time>\nCREATE DATE:\n ... <shows rebuilding of menus> ...\n Install Completed.\n\n10. Start TaskMan. If you shut down HL7 filers/LLPs or any other background\n tasks, you may restart them.\n11. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n << Background filer will start soon. >>\nFile 3.7, MailBox:\n12. Place option XMUSER back in order by entering FileMan and:\nVA FileMan 21.0\nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n ==========================\nINPUT TO WHAT FILE: OPTION// <press return>\n ==============\nEDIT WHICH FIELD: ALL// OUT OF ORDER MESSAGE\n ==================== \nTHEN EDIT FIELD: <press return>\n ==============\n3.7,1.2 MESSAGE @ REINSTATEMENT becomes DATE @ REINSTATEMENT (The post-\nSelect OPTION NAME: XMUSER MailMan Menu\n ======\nOUT OF ORDER MESSAGE: Loading MailMan patch XM*7.1*50\n Replace @\n === \n SURE YOU WANT TO DELETE? Y (Yes)\n ===\nSelect OPTION NAME: <press return>\n ==============\nSelect OPTION: <press return>\ninit will change any existing message numbers in this field to their equiv-\n ==============\n13. DSM SITES: After patch has installed, rebuild your map set.\n Many routines have become obsolete and should be removed from the map\n set. Here is a new recommended list of routines to map, should your\n site choose to map routines:\n Minimum Additional\n ------- ----------\n XM XMBPOST\n XMC1 XMC,XMC1*\n XMJ* XMD\nalent dates.\n XML1CRC,XML4CRC*,XMLSWP* XMK*\n XMR,XMR0* XML\n XMS,XMS0* XMR1*\n XMS1,XMSMAIL\n XMVVITAE\n XMXSEC\n XMXUTIL\n14. This patch replaces routine ^XMRPCTS1, which contains your site's TWIX\n routing info. In step 1, you copied the TWIX info for your site from\n that routine. Now, edit the new ^XMRPCTS1 to set your site's TWIX info.\nFile 4.3, MailMan Site Parameters:\n Specifically:\nXMRPCTS1 ;(KC-VAMC)/XXX-Simple PCTS front end to MailMan ;03/19/98 11:10\n ;;7.1;MailMan;**6,50**;Jun 02, 1994\n N XMUS,XMFM,XMSTR,XMRI,XMTO,XMABORT\n ;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n ;All should be sent to XXX@VHA.DMIA the local PCTS Domain\n ;Edit these for your site. <---Put your site's TWIX info\n S XMUS="XXXX" ;Local routing indicator <---at this line\n S XMFM="YYYY" ;from line <---and this line\n I XMUS="XXXX"!(XMFM="YYYY") S %="FIX Routing codes !!!"_XMPCTS0("ERR")\n4.3,4.301 NO-PURGE MESSAGES BUFFER becomes NO-PURGE DAYS BUFFER (The post-\n ;-------------------------------------------------------------\n15. For those sites using class III ^ASKX820, you should edit routine\n^ASKX820. It calls ENT^XMAD1, an illegal entry point which no longer exists.\nReplace it with a call to ENT1^XMD.\n16. For those sites running class III WordManager, you will have to find the\n WordManager routine containing D OK^XMA22. For version 5.01, it's in\n routine ^WMWTWM. It may be in other routines in other versions.\n OK^XMA22 is an undocumented entry point into MailMan which no longer\n exists. Edit the WordManager routine as follows:\nReplace:\ninit will set this field to null, which defaults to 2 days. You may change\n S ^XMB(3.9,XMZ,2,0)="^^"_(J-1)_"^"_(J-1)\nEDIT ;\n S DIE="^XMB(3.9,",DA=XMZ,DR=".01;3" D ^DIE\nREC ;\n S XMMG=$P(^DIC(3,DUZ,0),"^",1) D DES^XMA21 G:X="^" EXIT\nSEND ;\n S XMR="",XMTEXT="^XMB(3.9,XMZ,2," D OK^XMA22,EN1^XMD\nEXIT U TRM S R7=ZR7,TRM=$I K ZR7,ZMM\nwith:\n S ^XMB(3.9,XMZ,2,0)="^^"_(J-1)_"^"_(J-1)\nMailMan manuals have been rewritten. The full patch description and the\nit afterward.\nEDIT ;\n ;S DIE="^XMB(3.9,",DA=XMZ,DR=".01;3" D ^DIE\nREC ;\n ;S XMMG=$P(^DIC(3,DUZ,0),"^",1) D DES^XMA21 G:X="^" EXIT\nSEND ;\n ;S XMR="",XMTEXT="^XMB(3.9,XMZ,2," D OK^XMA22,EN1^XMD\nERS ; EDIT, REC, SEND\n N XMV,XMRESTR,XMINSTR,XMSUBJ,XMABORT\n S XMABORT=0\n S XMSUBJ=XMSUB\n4.302,3 FIRST MESSAGE TO PROCESS becomes START PURGE DATE\n D INIT^XMVVITAE\n D ES^XMJMSO\n D BODY^XMJMS(XMDUZ,XMZ,XMSUBJ,.XMRESTR,.XMABORT)\n I XMABORT D KILLMSG^XMXUTIL(XMZ) G EXIT\n D INIT^XMXADDR\n D TOWHOM^XMJMT(XMDUZ,"Send",.XMINSTR,.XMRESTR,.XMABORT)\n D:'XMABORT SENDMSG^XMJMSO(XMDUZ,XMZ,XMSUBJ,.XMINSTR,.XMRESTR,.XMABORT)\n D:XMABORT KILLMSG^XMXUTIL(XMZ)\n D CLEANUP^XMXADDR\nEXIT U TRM S R7=ZR7,TRM=$I K ZR7,ZMM\n4.302,4 LAST MESSAGE TO PROCESS becomes STOP PURGE DATE\n17. For those sites using class III ^BJMAIL*, you should edit routine ^BJMAIL\nto correct its egregious violations of the SAC. If you don't, MailMan will\nwill not function properly. Once you have edited ^BJMAIL, you may delete\nroutine ^BJMAIL1, since it will no longer be used. Edit ^BJMAIL as follows:\nReplace:\nMSG Q:'$D(T)\n ... thru ...\nWRITE ;Write a message - not part of the main program.\nWith:\nMSG ;\n4.302,8 LAST MESSAGE PROCESSED becomes LAST DATE PROCESSED\n N XMINSTR\n Q:'$D(T)\n Q:'$O(T(0))\n D GROUP\n Q:$O(TO(""))=""\n I $G(CONFIRM) S XMINSTR("FLAGS")=$G(XMINSTR("FLAGS"))_"R"\n I $G(PRIO) S XMINSTR("FLAGS")=$G(XMINSTR("FLAGS"))_"P"\n I $G(INFO) S XMINSTR("FLAGS")=$G(XMINSTR("FLAGS"))_"I"\n I '$D(FROM) S FROM=.5\n D SETFROM^XMD(.FROM,.XMINSTR)\n4.3,4.304 WEEKDAY MESSAGES TO PURGE becomes WEEKDAY DAYS TO PURGE (Any value\n I '$D(TITLE) S TITLE="Title not specified by sender"\n I $L(TITLE)>65 S TITLE=$E(TITLE,1,65)\n I $L(TITLE)<3 S TITLE=TITLE_"..."\n D SENDMSG^XMXAPI(FROM,TITLE,"T",.TO,.XMINSTR)\n K CONFIRM,FROM,GROUP,INFO,PRIO,T,TITLE,TO\n Q\nGROUP ;\n Q:$G(GROUP)=""\n I +GROUP=GROUP S:$D(^XMB(3.8,GROUP,0)) TO($P(^XMB(3.8,GROUP,0),U))="" Q\n S TO("G."_GROUP)=""\nyour site has in this field will be changed by the post-init from number of\n Q\nWRITE ;Write a message - not part of the main program\n\n ----------------------------------------------------------------------\n NOTE: Once the POST-INIT stops, continue with steps 18 through the end.\n ----------------------------------------------------------------------\n\n18. If you disabled journaling in step 8, you should enable it again here.\n18a. DSM SITES:\n >D ^%GLOMAN\nmessages to the equivalent number of days. You may change it afterward.)\n Global Management Utility\n Global > ^XMBX\n ====\n ^XMBX is currently defined\n\n 1. Show GLOBAL Characteristics\n 2. Change Access Privileges\n 3. Change Journaling Capability\n 4. Change DATA GROWTH AREA\n\n4.3,142 NO-PURGE DAYS BUFFER becomes NO-PURGE DAYS BUFFER (LOCAL)\n Enter option > 3\n =\n Journaling [E=Enabled/D=Disabled] <D> E\n =\n - Characteristics updated\n\n 1. Show GLOBAL Characteristics\n 2. Change Access Privileges\n 3. Change Journaling Capability\n 4. Change DATA GROWTH AREA\n\n\n Enter option > <press return>\n ==============\n Global > ^<press return>\n ==============\n18b. CACHE SITES:\n %SYS>D ENABLE^%NOJRN\n ===============\n18c. MSM SITES: Consult MSM documentation for how to enable journaling.\n19. For those sites running POP3, you should load patch XM*7.1*71 immediately\nNOTES:\n after loading this patch. Other sites may load patch XM*7.1*71 at their\n leisure.\n20. On the KIDS:Utilites menu, use the following option to review the\ninstall:\n Install File Print\nReview the automatic domain name changes which occurred during the post-init.\nIf there were any errors noted for a particular domain, that domain did not\nhave its new name added as a synonym. (Error messages are preceded by ***,\nand tell you what was wrong.) You must correct the error manually and add\nthe synonym manually. Remember, you are not to change any domain name.\n\n\nPatch XM*7.1*71\nminimum. It requires MailMan patch XM*7.1*50.\n\nClass III routines ^XMRPOPA, ^XMRPOPB, and ^XMRPOPC are replaced by class I\nroutine ^XMRPOP. These class III routines should be deleted after the\ninstall.\n\nClass III routine ^XMUCXPOP becomes Class I. Even though you may already\nhave it on your system, this patch treats it as a new routine, because it is\nnew to MailMan.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMRPOP * New * 11236318 71\nXMUCXPOP * New * 361549 71\nTest Site: DOMAIN.EXT\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\n\nRoutine Callable at Description\n-----------------------------------------------------------------------\nXMRPOP N/A\nXMUCXPOP N/A\n===========================================================================\n\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option to load\n the patch into a transport global.\n2. You do not need to stop TaskMan or the background filers.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nIn response to E3R #10591, and management directive,\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*71 Loaded from Distribution <date/time>\n =========\n => <header> ;Created on <date/time>\n\n This Distribution was loaded on <date/time> with header of \n <header> ;Created on <date/time>\nthis patch raises the class III POP3 server routines to class I,\n It consisted of the following Install(s):\n XM*7.1*71\n\n XM*7.1*71\n\n Install Questions for XM*7.1*71\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n XM*7.1*71\nand incorporates them into MailMan.\n \n Install Started for XM*7.1*71 : \n <shows date and time>\n \n Installing Routines:\n <shows date and time>\n \n Updating Routine file...\n \n Updating KIDS files...\n\n \n XM*7.1*71 Installed. \n <shows date and time>\n \n Install Message sent #<shows message number>\n \n Install Completed.\n4. If you have the class III routines ^XMRPOPA, ^XMRPOPB, and ^XMRPOPC at\nyour site, you should delete them. They are not part of MailMan. They\nhave been replaced by MailMan routine ^XMRPOP. They are obsolete. If you\nNOTE: This patch should be installed after hours, when user activity is at a\nchoose not to delete these routines, you should rename them to the ^XMZ*\nnamespace. \n===========================================================================\n\n
\nPatch XM*7.1*72\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMJMLR1 6523962 7836320 50,72\n\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: Montana HCS\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*72 Loaded from Distribution <date/time>\n\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThis patch adds a command to the full screen reader to refresh the display\nof the current page of messages. Enter "=" to refresh the display.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n\n
\nPatch XM*7.1*76\n\nAll fields are rearranged so that similar fields are grouped together in\nthe editing sequence.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThere are no routines in this patch.\n\n\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n2. You do not need to stop TaskMan or the background filers.\n3. On the KIDS:Installation menu, use the following options to install the\nTest Site: Montana HCS\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*76 Loaded from Distribution <date/time>\n =========\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n===========================================================================\nIn response to NOIS MON-0799-52264, this patch updates option\nXMKSP MailMan Site Parameters.\n\nFields 16.1 (P-MESSAGE LINE LIMIT) and 17.1 (MAX DIGITS FOR MESSAGE NUMBER)\nare added.\n\n
\nPatch XM*7.1*73\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n\nXMXUTIL1 5489564 5531421 50,73\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest Site: Indianapolis, IN\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*7.1*73 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThis patch fixes the $$CONVERT^XMXUTIL1 function. If the date/time to be\nconverted did not include a time zone, the function reported an invalid\ndate/time. Now, the time zone is assumed to be the current one.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*74\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n\nXMUT4 17112758 17135000 50,74\nXMVVITAE 12045708 12062054 50,74\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nTest Site: DBA's Platinum Account\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n Install Package(s)\n Select INSTALL NAME: XM*7.1*74 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf the postmaster has no remote message transmit queues, then MailMan aborts\nduring the global checker (^XMUT4), and during user setup (^XMVVITAE).\nThis patch fixes that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*78\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------\nXMXADDR1 12069509 12072106 50,78\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nTest Site: Indianapolis VAMC\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n Install Package(s)\n Select INSTALL NAME: XM*7.1*78 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf a remote address contains a blank and a left parenthesis, it may be\ncorrupted by the address checker provided with patch XM*7.1*50.\nFor example, the address "G.LAB REPORTS(F)@domain" becomes\n"REPORTS(F)@domain". This patch fixes this problem.\n\n\n
\n This MailMan patch is dependent on Kernel patch XU*8*24, which should\n-Transmission scripts were not switching over. Nois BRX-0496-10709 &\n options:\n Taskman Management ...\n Taskman Management Utilities ...\n Taskman Error Log ...\n List Error Screens\n Add Error Screens\n\n Use the option 'List Error Screens' to see what errors you are currently\n screening. Use the option 'Add Error Screens' to add the following errors:\n AXP sites 486 sites\n ALB-0596-51476.\n --------- ---------\n DISCON DSCON\n HANGUP\n REJECT\n CONNECFAIL\n\n OPTION:\n\n Manage Mailman ...\n Network Management ...\n-XMDUZ is undefined when receiving mail. Nois IVM-0896-31669.\n Transmission Management ...\n\n 'Toggle a script out of service' Option name: XMSCRIPTOUT\n This options lets you edit the OUT OF SERVICE field for a Transmission\n Script in the Domain file. You can also requeue the Domain for transmission\n from this option.\n\n\n DATA DICTIONARY: Partial DD\n\n-Statistics was not collecting Response time. Nois DAY-0596-40308.\n File: DOMAIN #4.2\n\n Field:\n 4 TRANSMISSION SCRIPT\n Subfield:\n 1.5 OUT OF SERVICE\n This is the preferred field to set to take a script out of\n service,to prevent it from being used.\n\n File: MESSAGE STATISTICS #4.2999\n-XMB will now 'NEW X'. Nois MEM-0496-70250, MIN-0396-42065, &\n\n Fields:\n 41 XMIT START DATE/TIME\n This field helps MailMan determine, after a fatal error,\n whether to start the transmission process at script 1,\n try 1, or to start elsewhere.\n\n 42 XMIT FINISH DATE/TIME\n This may be useful information for debugging purposes.\n\n NAS-0496-30171.\n 43 XMIT SCRIPT\n This tells MailMan which script is/was being used.\n\n 44 XMIT TRIES\n This tells MailMan how many tries have been made with\n the current script.\n\n 45 XMIT LATEST TRY DATE/TIME\n This may be useful information for debugging purposes.\n\n-Change the header of the statistics report, 'Last Sign On' is now\n 46 XMIT SCRIPT CYCLE ITERATIONS\n This is the number of script cycles we have tried. This\n field starts off at 0. After we have tried all the scripts\n available, we bump up this field by 1.\n\n 47 XMIT FIRST SCRIPT\n This field notes which script has the highest priority, that\n is, which script was tried first.\n\n 51 XMIT SCRIPT RECORD\n 'Last Mail Use'. Nois DAY-0196-41801.\n This is a copy of the zero node of the latest script used.\n\n 60 XMIT AUDIT\n This multiple contains an audit of the attempts that have\n been made during this transmission.\n-Undefined error on Headerless print of messages. Nois BRX-0196-10570.\n-Subscript errors from internet messages when the address is to long.\n be installed before this patch. This patch contains the following bug\n Nois HIN-0296-41163.\n-More information is being recorded in the MESSAGE STATISTICS file,\n # 4.2999. This will help with debugging transmission scripts.\n-A new Option 'Toggle a script out of service' can be used to place a\n Transmission Script out of service and requeue the domain.\n-MM now uses the new M95 Error trap in DSM. This change and the updating\n of the Taskman Error Screening should prevent numerous disconnect error from\n showing up in your error trap.\n-Purge by date was not purging Internet messages. Nois HIN-0896-40170 and\n PHO-0796-60127\n fixes and features:\n===========================================================================\n *** You MUST install Kernel patch XU*8*24 before installing this patch ***\n\n This patch should be installed after hours, when there is minimum users on\n the system. You should put the XMUSER Option out of order.\n\n MSM Sites: The routine XMRTCP must be moved to your NT machine and then\n reboot MSM on the NT machine. This will restart the TCP/IP poller.\n===========================================================================\n\n\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Verify Checksums in Transport Global\n-Sites getting errors with TCP/IP mail in ^XMC1A. Nois NCH-0696-41098,\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n=========================================================================== \n \n ROUTINES:\n WNY-0696-10208, & BRX-0696-11028.\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Name Checksum Patch List\n ----------------------------------------------------------\n XMA2C0 9088344 24,27\n XMA2R 4793721 27\n XMA31 2140577 27\n XMA32A 11841830 27\n XMAD1 7205963 24,27\n-The date/time of original message is added to a copied message.\n XMADGO 2112000 5,27\n XMAFTP 3717135 27\n XMAP0 4991024 27\n XMAPHOST 6366459 7,14,27\n XMB 7258608 3,7,24,26,27\n XMBPOST 9662243 1,4,13,23,24,27\n XMC1 6875049 4,13,20,27\n XMC11A 3517372 27\n XMC1A 7333631 27\n XMC2 12142809 13,23,27\n-The 'TCP/IP POLLER RUN FLAG' in file 4.3 is cleared when poller is\n XMCTLK 9708749 10,27\n XMCTRAP 144752 20,27\n XMDIR1 10096361 27\n XMDIR1A 4726311 27\n XMDIR1B 3077473 27\n XMLTCP 2446407 8,27\n XMR0 8606729 27\n XMR0A 3476739 27\n XMRFTP 3153916 27\n XMRFTPUX 3165955 27\n restarted.\n XMRTCP 4812676 8,25,27\n XMRUCX 338699 27\n XMS0 9449052 8,13,20,23,27\n XMS5 12968983 8,13,23,27\n XMUT5C 3064751 27\n============================================================================\n DOCUMENTATION:\n\n In order to fully utilize the new Error Processing in MailMan, you should\n start screening the 'Disconnect Errors'. To do this, look at the following\n\n
\nPatch XM*7.1*79\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n\nXMJMC 8169036 8264139 50,79\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest Site: FORUM\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*7.1*79 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nWhen a PackMan message is copied, field 1.7 (MESSAGE TYPE) in the MESSAGE\nfile should be set to either "K" for KIDS or "X" for PackMan. MailMan\npatch XM*7.1*50 inadvertently omitted this. This patch fixes that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*80\nNOTE: This patch may be installed at any time. It requires MailMan patch\nXM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------\nXMUTPUR0 1365512 2780488 7,50,80\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time. It requires MailMan patch\nXM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: FGH-0899-30616\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nTest Site: NORTH FLORIDA/SOUTH GEORGIA\n Install Package(s)\n Select INSTALL NAME: XM*7.1*80 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nDuring the AI xref purge, MailMan aborts if any AI xref is improperly\nformed. This patch changes the code to recognize and kill any improperly\nformed AI xrefs.\n\n\n
\nPatch XM*7.1*75\nThis patch establishes what happens when you print to the terminal. \n\n A. If you print a message from the "Message Action: Ignore//" prompt,\n MailMan will not pause at all.\n B. If you print a message or messages from the Classic-mode message list,\n MailMan will not pause at all.\n C. If you print a message(s) from the Detailed-mode or Summary-mode,\n Mailman will pause just before giving the message list again.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nTest Site: Montana HCS\nXMJMOR 14242356 14209869 50,75\nXMJMP 16472134 16504280 50,75\nXMJMP1 14179283 14502445 40,50,75\nXMXPRT 3036286 3044670 50,75\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\n\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nWhen you read a message at your terminal, every time the screen fills up,\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*75 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nMailMan pauses the display until you press return to continue. \nWhen you print a message or messages to a terminal, MailMan's behavior does\nnot make much sense.\n\n\n
\nPatch XM*7.1*81\nand delete all of the ones named SCRIPT.\n\nYou may let MailMan delete the scripts, or you may do it yourself.\nYou may wish to make a backup of the DOMAIN file before deleting\nthe scripts. A pre-install question will ask you what you want to\ndo. If you choose to let MailMan delete the scripts, the\npre-init will go ahead and delete them. Otherwise, the pre-init\nwill not run, and you should go through the DOMAIN file yourself\nand delete all IDCU scripts.\n\n\nNOTE: This patch may be installed at any time.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nNOIS: ASH-0899-30768\nXMYPRE4 * NEW * 2102170 81\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*81 Loaded from Distribution <date/time>\nAs you know, IDCU is no longer with us.\n =========\n Install Questions for XM*7.1*81\n\n Do you want me to delete all scripts named SCRIPT? YES// <it's up to you!>\nAnswer YES or NO here. If you answer YES, the pre-init will run and will\ndelete all scripts named SCRIPT. (It will also let you know if, after\ndeleting any scripts, a domain is left without any transmission scripts.)\nIf you answer NO, the pre-init will stop without doing anything, and you must\ngo through the DOMAIN file yourself and delete all IDCU scripts. \n\nIt is necessary to delete all IDCU scripts from the DOMAIN file.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIn examining the scripts, it appears that all IDCU scripts are\nnamed SCRIPT. Therefore, the pre-init in this patch is designed\nto go through all the transmission scripts in the DOMAIN file\n\n
\nPatch XM*7.1*83\nThis patch restores such lookups.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*78.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMXADDR1 12072106 12065832 50,78,83\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nNOIS: ISW-0899-22203\nminimum. It requires MailMan patch XM*7.1*78.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: CIOFO-ALBANY & CIOFO-WASHINGTON\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*83 Loaded from Distribution <date/time>\n =========\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nIf you send a message to "LASTNAME,FIRST@DOMAIN", it gets there.\nIf you send a message to "LAS,FIRS@DOMAIN", you get "addressee not found".\nAn unintended consequence of patch XM*7.1*50 was that lookups using comma\npiecing stopped working for message sent to remote sites.\n\n
\nPatch XM*7.1*84\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMJMBULL 1365629 1399629 50,84\n\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nNOIS: TAM-0899-31629\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*84 Loaded from Distribution <date/time>\nTest Site: Tampa, FL\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nOption XMPOST may error out with an undefined XMDUZ. This patch fixes that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n\n
\nPatch XM*7.1*87\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50..\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------\nXMJMOI 16872170 17074520 50,87\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: LAS-0999-60456\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nTest Site: Las Vegas, NV\n Install Package(s)\n Select INSTALL NAME: XM*7.1*87 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf, after reading a KIDS message, you WRITE a new message from the\nMessage action: IGNORE// prompt, MailMan thinks you're creating a PackMan\nmessage. This patch disabuses MailMan of that notion.\n\n\n
\nPatch XM*7.1*88\nIt requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n\nXMUPIN 13825872 13888699 50,88\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nNOIS: NOP-0999-10911\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nTest Site: Northport, NY\n Select INSTALL NAME: XM*7.1*88 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThe multi-basket IN basket purge aborts, because a parameter is missing\nfrom a call. This patch inserts the missing parameter.\n\nNOTE: This patch may be installed at any time.\n\n
\nPatch XM*7.1*86\nminimum. It requires MailMan patch XM*7.1*71.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\n\nXMRPOP 11236318 11250302 71,86\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*71.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nNOIS: none\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nTest Site: FORUM\n Select INSTALL NAME: XM*7.1*86 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf an error occurs in the POP server, MailMan may abort with an undefined\nXMCMD. This patch prevents MailMan from aborting.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*91\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\n\nXMAPHOST 9890299 9918694 7,14,27,36,50,91\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest Site: FORUM\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*7.1*91 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nSometimes, when printing to P-MESSAGE device, MailMan aborts because the\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nXMV variables (with user info) might not be properly set up. This patch\nensures that they are properly set up.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\n This patch changes the way KIDS secures a Packman Message. The prompt:\n\nThis patch should be installed during off-peak hours. Users can be on the\nsystem, but no user should be using KIDS during the install of this patch.\n===========================================================================\n \nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 'Enter the scramble hint:' \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n has been removed. A new prompt:\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n ===========================================================================\n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**33**;Jun 02, 1994\n \n Name Checksum Patch List\n -----------------------------------------------------------\n 'Do you wish to secure this message? No//'\n XMASEC 4454626 33\n XMD 4879878 33\n\n ;;8.0;KERNEL;**[patch list]**;Jul 10, 1995\n\n XPDTP 2358145 21,40\n ============================================================================\n will be asked after you enter the text for a message. This correct the\n problem that was identified by Nois CLE-0696-40353.\n This patch is the same as Kernel patch XU*8*40. Both patches contain\n the same MailMan and Kernel routines.\n===========================================================================\n\n
\nPatch XM*7.1*92\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMUT5 5739686 4497129 50,92\n\nXMUT5B 2644064 1096729 50,92\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nTest Site: FORUM\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*7.1*92 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nThis patch improves the display of the local message queue delivery status\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nprovided by option XMMGR-CHECK-BACKGROUND-FILER.\n\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n\n
\n *** It is VERY IMPORTANT that you READ the information in this PATCH. ***\n\nK ^XMB(3.9,"I")\nK ^XMB(3.9,"Rxxxxxx")\n\nNOTE: This patch may be installed at any time.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \nThe only official whole-file cross references on the MESSAGE file are what\n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMYPRE5 * NEW * 300476 93\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nyou see below. If you see others, they are either bogus or they are local\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nmodifications. This patch shows you and deletes the known bogus cross\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*93 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nreferences. If you see other cross references, and are unsure whether they\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nare bogus or whether they are local modifications, please log a NOIS.\nDo not delete anything without consulting Customer Service.\n\n------------------------------------------------------------------------\nIf your site is pre-patch XM*7.1*50, this is what you should see when you\n\ndo the following:\n>D ^%G\n\nGlobal ^DD(3.9,0,"IX"\n DD(3.9,0,"IX"\n^DD(3.9,0,"IX","AI",3.9,9) = \n^DD(3.9,0,"IX","B",3.9,.01) = \n^DD(3.9,0,"IX","C",3.9,1) = <-- exists, but never used.\n\nPre-patch XM*7.1*50, you should see no xrefs after the "B" xref:\nPatch XM*7.1*93\n>D ^%G\n\nGlobal ^XMB(3.9,"C":\n XMB(3.9,"C":\nGlobal ^ <-- nothing!\n\n------------------------------------------------------------------------\nIf your site is post-patch XM*7.1*50, this is what you should see when you\ndo the following:\n>D ^%G\n\n\nGlobal ^DD(3.9,0,"IX"\n DD(3.9,0,"IX"\n^DD(3.9,0,"IX","AI",3.9,9) = \n^DD(3.9,0,"IX","AL",3.914,4) = <-- new with patch XM*7.1*50\n^DD(3.9,0,"IX","AW",3.914,2) = <-- new with patch XM*7.1*50\n^DD(3.9,0,"IX","B",3.9,.01) = \n^DD(3.9,0,"IX","C",3.9,31) = <-- new with patch XM*7.1*50\n\nPost-patch XM*7.1*50, you should see no xrefs after the "C" xref:\nNOIS: KAN-0999-40493\nGlobal ^XMB(3.9,"D":\n XMB(3.9,"D":\nGlobal ^ <-- nothing!\n\n------------------------------------------------------------------------\nThis is what some pre-patch XM*7.1*50 sites see:\n>D ^%G\n\nGlobal ^DD(3.9,0,"IX"\n DD(3.9,0,"IX"\nTest Site: Kansas City, MO\n^DD(3.9,0,"IX","AI",3.9,9) = \n^DD(3.9,0,"IX","B",3.9,.01) = \n^DD(3.9,0,"IX","C",3.9,1) = \n^DD(3.9,0,"IX","I",3.9,9) = <-- bogus! This appears to be a precursor\n to the "AI" xref, and was never properly\n deleted.\n\n------------------------------------------------------------------------\nThis is what some (post-patch XM*7.1*50) sites see:\n>D ^%G\n\n\nGlobal ^DD(3.9,0,"IX"\n DD(3.9,0,"IX"\n^DD(3.9,0,"IX","AI",3.9,9) = \n^DD(3.9,0,"IX","AL",3.914,4) = \n^DD(3.9,0,"IX","AW",3.914,2) = \n^DD(3.9,0,"IX","B",3.9,.01) = \n^DD(3.9,0,"IX","C",3.9,31) = \n^DD(3.9,0,"IX","I",3.9,9) = <-- bogus! This appears to be a precursor\n to the "AI" xref, and was never properly\nThere seem to be some bogus cross references left over from previous\n deleted.\n\n------------------------------------------------------------------------\nThis is what any site might see, regardless of patch XM*7.1*50:\n\nGlobal ^XMB(3.9,"D":\n XMB(3.9,"D": Everything that follows is bogus!\n^XMB(3.9,"I","TCP/IP INTERFACE@1052",1239824) = 2890228.161\n^XMB(3.9,"I","TCP/IP INTERFACE@1054",1240498) = 2890301.0032\n^XMB(3.9,"R1014436",1,0) = ^3.91A^0^0\nincarnations of MailMan.\n^XMB(3.9,"R1014514",1,0) = ^3.91A^0^0\n^XMB(3.9,"R1014690",1,0) = ^3.91A^0^0\n^XMB(3.9,"R1015376",1,0) = ^3.91A^0^0\n^XMB(3.9,"R1017643",1,0) = ^3.91A^0^0\n^XMB(3.9,"R1050403",1,0) = ^3.91A^0^0\n\n------------------------------------------------------------------------\nThe only routine in this patch is a pre-init, which will kill the known\nbogus xrefs:\nK ^DD(3.9,0,"IX","I")\n\n
\nPatch XM*7.1*85\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n----------------------------------------------------------\nXMXREPLY 4925239 5097167 50,85\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: TAM-0899-32035\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nTest Site: Tampa, FL\n Install Package(s)\n Select INSTALL NAME: XM*7.1*85 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf a message looks as if it's from a remote site (piece 2 of the zero node\ncontains "@"), but it's really a local message, MailMan aborts trying to\nfigure out who it's from. This patch prevents MailMan from aborting.\n\n\n
\nPatch XM*7.1*89\nuser is told 'you haven't read response x', whether the user read response\nx or not. The user won't be pestered about response x any more.\n3. If a message is sent to FRED@ANOTHERSITE, and then later forwarded to\nFRED at this site, Q does not show FRED; only QD does.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*87.\n============================================================================ \n\nROUTINES:\n\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMJMOI 17074520 17103064 50,87,89\nXMJMRO 2449032 2478663 50,89\nXMKP 15443979 15719989 50,89\nXMXSEC2 20994061 21338911 50,89\nNOIS: MON-0999-50325, MON-0999-50323\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*87.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: Montana HCS\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*89 Loaded from Distribution <date/time>\n\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\nThis patch fixes several problems:\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n1. If a message is forwarded to * (broadcast to all users), the message\nnow becomes 'information only'. It didn't used to.\n2. If a broadcast message has responses, and a user reads the message, the\n\n
\nPatch XM*7.1*94\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMR1 13292215 14522459 7,50,94\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\nNOIS: none\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: GATEWAY.DOMAIN.EXT\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*94 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nWhen receiving mail from another site, and the subject, from, and sender\nlengths are large, the process can abort with "string too long" when\nattempting to file these fields in the MESSAGE file. This patch ensures\nthat this doesn't happen.\n\n
\nPatch XM*7.1*96\nminimum. It requires MailMan patch XM*7.1*83 and FileMan patch DI*22.0*1.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\n\nXMJMQ 16189088 16042167 40,57,70,50,96\nXMXADDR 18774539 18766785 50,96\nXMXADDR1 12065832 11791491 50,78,83,96\nXMXPARM 19704732 19474825 50,96\nXMXPARM1 5916152 5657265 50,96\nXMXUTIL4 9117363 8973867 50,96\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nNOIS: none\nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*83 and FileMan patch DI*22.0*1.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Sites: ISC-SF.DOMAIN.EXT\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*96 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nThis patch alters some FIND^DIC and $$FIND1^DIC calls (removes the\n===========================================================================\n"Q" flag) in support of the NEW PERSON file name standardization project.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*77\nfile and deletes any duplicates.\n\nThe .01 field of the MEMBER multiple of the MAIL GROUP file is altered\nas follows:\n1. the "B" xref is converted from a traditional xref to a new index.\n2. a uniqueness key is added.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50 and FileMan patch DI*22.0*12.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMYPRE3 * NEW * 1406835 77\n\nNOIS: BRX-0297-10955\n*Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50 and FileMan patch DI*22.0*12.\nINSTALLATION:\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n2. You do not need to stop TaskMan or the background filers.\n3. On the KIDS:Installation menu, use the following options to install the\nTest Site: Bronx\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*77 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n===========================================================================\nThis patch ensures that duplicate members cannot be added to the\nMEMBER multiple of the MAIL GROUP file. \n\nThe pre-init for this patch checks the MEMBER multiple of the MAIL GROUP\n\n
\nPatch XM*7.1*97\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n--------------------------------------------------------------\nXMTDL 18249122 18497319 50,97\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: none\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan, but you should stop the background\n filer. On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\nTest Site: GATEWAY.DOMAIN.EXT\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*97 Loaded from Distribution <date/time>\n =========\n Install Questions:\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\nThere's a strange problem with local mail delivery which sometimes occurs.\n5. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIt manifests itself in an undefined ^XMB(3.9,XMZ,3,0) in RDELIVER^XMTDL.\nThis patch adds a variable which should aid in debugging.\n\n\n
\nPatch XM*7.1*98\nTest Site: Iron Mountain, MI\n\nPatch XM*7.1*50 introduced a bug into WHO^XMA21. When X is a group name,\nXMY only contains the first member of the group. This patch fixes that,\nso that XMY contains all members of the group.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMA21 1920696 2315418 4,31,50,98\nXMD 6535767 6947940 33,50,98\n\nNOIS: ISL-0999-52799\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nTest Site: CIOFO-SALT LAKE CITY\n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*98 Loaded from Distribution <date/time>\n =========\n\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nPatch XM*7.1*50 introduced a bug into ENT2^XMD. It started killing XMSUB.\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThis patch puts a stop to that.\n\nNOIS: IRO-0999-42186\n\n
\nPatch XM*7.1*100\nMailMan aborts. This patch fixes that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*75.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMJBN 10185228 10390839 50,100\nXMJMP 16504280 16560016 50,75,100\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOIS: BAC-1099-40361\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*75.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: Battle Creek, MI\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*100 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nWhen acting as a surrogate, and printing new messages, a confidential\nmessage sends MailMan into an endless loop. This patch fixes that.\n\nWhen printing several messages at once, if one of them is scrambled,\n\n
\n \n===========================================================================\n \nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n This MailMan patch is in response to Nois BRX-1195-11719 and E3R 7344, to\n options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \nstop message bouncing caused by invalid subdomains. If a message is\n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ----------------------------------------------------------\n XMA21A 8460688 8186870 4,30\n XMR 6264225 6434522 30\naddressed to a subdomain not known to its parent domain, the message will\n============================================================================\nbe rejected. It will not be bounced back to FORUM, as it was previously.\nThe originator will receive a message; 'Sub-domain XXX not found.'\n===========================================================================\n \n This patch can be installed with users on the system.\n\n
\nPatch XM*7.1*95\nminimum. It requires MailMan patch XM*7.1*89.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\n\nXMXSEC1 12851118 13791136 50,95\nXMXSEC2 21338911 21310509 50,89,95\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*89.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nNOIS: WAS-0999-21379\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nTest Sites: Washington,D.C.; Fargo,ND\n Select INSTALL NAME: XM*7.1*95 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nMailMan patch XM*7.1*50 removed the ability to forward messages in the\nPostmaster's transmit queue baskets. This patch restores that ability.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*99\nit checked for the presence of a global node (^XMBPOST("POST")). Any\naccount in which anyone had ever sent a response would have had this node.\nSome development accounts didn't have this node, so the pre-init did not\nrun.\n\nThis patch checks for the presence of a different node to determine whether\nthe pre-init should run. If it ran in patch XM*7.1*50, it won't run again,\nbut if it didn't run in patch XM*7.1*50, it will run.\n\nThis patch also:\n\n- resends the DDs for files 3.7, 3.9, 4.2999, and 4.3. No changes are made\nto the DDs. We just want to ensure that sites have the full and correct DDs.\n\n- corrects an incorrect patch list in the second line of routine ^XMXREPLY.\nIt changes 84 to 85. (NOIS ISB-1099-30184: Patch XM*7.1*85 created an\nincorrect patch list in routine ^XMXREPLY.)\n\n- prevents an error message from being sent if a user up-arrows out of a\nselection while addressing a group. \n\nNOIS: none\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*85.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\nTest Site: CIOFO-SAN FRANCISCO\n--------------------------------------------------------------\nXMXADDRG 15430701 15444713 50,99\nXMXREPLY 5097167 5097167 50,85,99\nXMYPRE6 * new * 12721120 99\nXMYPRE6A * new * 15207878 99\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*85.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nThe pre-init for MailMan patch XM*7.1*50 deleted unneeded fields from the\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*99 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\ndata dictionary and the globals.\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nTo decide whether it should run (and to prevent it from running twice),\n\n\nPatch XM*7.1*103\nminimum. It requires MailMan patch XM*7.1*98.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\n\nXMD 6947940 7129791 33,50,98,103\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*98.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nNOIS: LOM-1099-61129\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nTest Site: Loma Linda, CA\n Select INSTALL NAME: XM*7.1*103 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nPatch XM*7.1*50 introduced a bug into EN1^XMD. It replaced the FROM field\nin the message stub with DUZ. This patch puts a stop to that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\n\n
\nPatch XM*7.1*101\nAllow forwarding of messages from remote postmasters if the forwarding\naddress is local. (To avoid looping error messages, messages from remote\npostmasters are not forwarded to remote addresses.)\n\nFYI:\nIf a fictitious user is a member of a mail group, and the sole purpose of\nthat fictitious user is to have a forwarding address of a device,\nthe preferred method is to put the device directly in the mail group (in\nthe remote member multiple) and get rid of the fictitious user.\n\n\nNOIS: DAY-1099-41161\nTest Site: Dayton, OH\n\nWhen minusing a user during message addressing, MailMan should limit the\nchoices to the current addressees, as it did before patch XM*7.1*50.\nThis patch restores that functionality.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*96.\n============================================================================ \nNOIS: AMA-1099-70251\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMVVITA 4126813 4257402 50,101\nXMXADDR 18766785 18242989 50,96,101\nTest Site: Amarillo, TX\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*96.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*101 Loaded from Distribution <date/time>\nAllow users to have a server option (S.xxx) as a forwarding address.\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n(Users may have remote addresses, as well as local devices and servers\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nas forwarding addresses.)\n\n\n
\nPatch XM*7.1*105\nthe message has recipients.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMA2R 3427633 3913497 27,50,105\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nY2K Waiver Exemption ID: WE0009\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*105 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nNOIS: SHE-1099-52199\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nTest Site: Wilmington, DE\n\nAdds two checks to the API, $$ENT^XMA2R, which replies to a message.\nOne check makes sure the message exists, and the other check makes sure\n\n
\nPatch XM*7.1*90\nNote that the restriction is only removed at the sending site.\n(At the receiving site, the restriction is unchanged. If MailMan receives\na line over 255 characters, it chops it up into as many lines as needed.)\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMLTCP 2573202 2433601 8,27,61,90\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nNOIS: AMA-0399-70162, BHS-0799-11263, BOI-0499-50453, CMO-0397-42224,\nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n GRJ-0899-50198\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*90 Loaded from Distribution <date/time>\n =========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nTest Sites: DSS: Bay Pines, FL\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n PDX: Grand Junction, CO; Boston HCS\n===========================================================================\n\nThis patch fixes problems experienced in the PDX and DSS packages.\nThis patch removes the string length restriction for TCP/IP transmissions.\n\n
\nPatch XM*7.1*104\nDOMAIN files, MailMan rightly asks the user to select one. \n\nIf a mail group contains a device name or option name or remote address\nwhich has exact, as well as partial matches, MailMan should automatically\nselect the exact match. However, it doesn't. This patch makes MailMan\nselect the exact match.\n\nAlso in this patch,\n^XMDF - Correct code which is never executed.\n^XMGAPI3 - Prepare for name change from DOMAIN.EXT to DOMAIN.EXT\n\n^XMJMD - Correct how largest message number is obtained.\n^XMVGROUP - If a site has faxing enabled, allow mail group edit options\n to edit fax multiples in mail group file.\n^XMXADDR1 - Don't accept broadcast messages from remote sites.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*101.\n============================================================================ \n\nROUTINES:\nY2K Waiver Exemption ID: WE0008\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMDF 1431567 1438292 50,104\nXMGAPI3 2171233 2143520 29,44,67,50,104\nXMJMD 7370754 7370688 50,104\nXMVGROUP 6214836 6303194 50,104\n\nXMXADDR 18242989 18270156 50,96,101,104\nXMXADDR1 11791491 12136703 50,78,83,96,104\nXMXADDRD 9657048 9742967 50,104\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*101.\nNOIS: MAD-1099-41351\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: Madison, WI\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*104 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nRoutines: ^XMXADDR, ^XMXADDR1, ^XMXADDRD\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf a user enters an address, which is a device name or option name or remote\naddress which has exact, as well as partial matches in the DEVICE, OPTION, or\n\n
\nPatch XM*7.1*102\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*91.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMAPHOST 9918694 9975581 7,14,27,36,50,91,102\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*91.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: BRX-1099-10488\n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nTest Site: Bronx, NY\n Install Package(s)\n Select INSTALL NAME: XM*7.1*102 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nPost patch XM*7.1*50, setting XMSUB to a message subject, and then queueing\na report to the p-message device fails to pick up the message subject.\nThis patch corrects that.\n\n\n
\nPatch XM*7.1*106\nMailMan's locks, and lets FileMan handle the locking. If FileMan can't get\nthe lock, MailMan will keep calling Fileman until FileMan succeeds.\n\nAlso in this patch:\n^XMXBSKT - When resequencing messages in a basket, use local create date.\n^XMXSEND - Additional code to ensure message recycling functions correctly.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMXBSKT 12393935 13019759 50,106\nXMXMSGS2 5670519 6491081 50,106\nY2K Waiver Exemption ID: Y2KWE0010\nXMXSEND 10879355 11913872 50,106\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan, but you should stop the background\n filer. On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n4. On the KIDS:Installation menu, use the following options to install the\nNOIS: IVM-1099-31783, IVM-1099-33078\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*106 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nTest Site: HEC, Atlanta, GA\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Press Return> <Do NOT queue it!>\n ==============\n5. Start the background filer.\n\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThere seems to be a problem with getting a lock sometimes, when attempting to\nfile a message into or delete a message from a basket. This patch removes\n\n
\nPatch XM*7.1*108\n\nAdds more checks to the MailMan global integrity checking routines:\n- makes sure every IEN in the Message file is a number\n- makes sure no recipient in the Message file is null.\n- makes sure there isn't more than one B xref per basket in the Mailbox file\n- makes sure messages in the WASTE basket aren't new\n- makes sure the names of the IN and WASTE baskets haven't been changed\n\nNOIS: none\nTest Site: Indianapolis, IN\n\n\nThe API, LISTMSGS^XMXAPIB, may incorrectly state whether there are more\nmessages in the list. This patch fixes that.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*50 and XM*7.1*74.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\nY2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMUT4 17135000 13628025 50,74,108\nXMUT41 * NEW * 5625084 108\nXMUT4A 1411742 1491748 34,55,50,108\nXMUT4B 18488496 20142397 50,108\nXMUT4BA 15364896 16133058 50,108\nThis patch may be installed during the Y2K Moratorium, either BEFORE 12/15/99\nXMUT4C 7228866 7571867 10,22,50,108\nXMXLIST 10429141 10491222 50,108\nXMXLIST1 12554823 12617251 50,108\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\n\nRoutine Callable at Description\n---------------------------------------------------------------------------\nor AFTER 1/15/2000. This patch MAY NOT be installed between 12/15/1999 and\nXMUT41 N/A\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patches XM*7.1*50 and XM*7.1*74.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n1/15/2000 (the Y2K Lockdown Period). \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*108 Loaded from Distribution <date/time>\n ==========\n\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nNOIS: FAV-1199-72207\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nTest Site: Fayetteville, AR\n\n
\nMailMan patch XM*7.1*38 is a patch for XM*7.1*27. It contains the following\n a minimum. You should put the XMUSER Option out of order.\n\n MSM Sites: The routine XMRTCP must be moved to your NT machine and then\n reboot MSM on the NT machine. This will restart the TCP/IP poller.\n===========================================================================\n\nINSTALLATION:\n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the affected routines.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\nbug fix:\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n=========================================================================== \n \n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n Checksum Checksum\n Name Before After Patch List\nFixes 'undefined variable' problem with the variable XMB("ITERATIONS").\n ----------------------------------------------------------\n XMBPOST 9662243 9856673 4,13,23,24,27,38\n============================================================================\nThis problem occurs when patch XM*7.1*27 is loaded after remote transmission\ntasks have been queued, but before they have a chance to run.\n\n===========================================================================\n This patch should be installed after hours, when user activity is at\n\n\nPatch XM*7.1*111\n\nA typo in routine ^XMUT2 caused the large message report to always start with\nthe first message in the message global, even if the user chose a different\nmessage. This patch fixes that. This patch also changes the starting\nparameter from message number to message date. We're doing this because\nmessage numbers can be recycled.\n\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n============================================================================ \n\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMUT2 4582154 6143350 50,111\n\nY2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \nThis patch may be installed during the Y2K Moratorium, either BEFORE 12/15/99\n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nor AFTER 1/15/2000. This patch MAY NOT be installed between 12/15/1999 and\n Select INSTALL NAME: XM*7.1*111 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n1/15/2000 (the Y2K Lockdown Period). \n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOIS: RIC-1299-20703\nTest Site: Richmond, VA\n\n
\nPatch XM*7.1*113\nA message being received on FORUM from another site caused an abort when\nthe addressee equated to null. MailMan now checks for a null addressee.\n\nNOTE: This patch should be installed after hours, when network mail activity\nis at a minimum. It requires MailMan patch XM*7.1*50. \n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMR 14031423 14137871 30,34,65,50,113\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\nY2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when network mail activity\nis at a minimum. It requires MailMan patch XM*7.1*50. \n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\nThis patch may be installed during the Y2K Moratorium, either BEFORE 12/15/99\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*113 Loaded from Distribution <date/time>\n ==========\n Install Questions:\nor AFTER 1/15/2000. This patch MAY NOT be installed between 12/15/1999 and\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n1/15/2000 (the Y2K Lockdown Period). \n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOIS: none\nTest Site: DOMAIN.EXT\n\n
\nPatch XM*7.1*114\nFor the Large Message Report, this patch makes the bounds for the message\nlines in the routine match the bounds in file 4.3, field 8.14, LARGE MESSAGE\nREPORT LINES. \n\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*111.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMUT2 6143350 6132805 50,111,114\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nY2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*111.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\nThis patch may be installed during the Y2K Moratorium, either BEFORE 12/15/99\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*114 Loaded from Distribution <date/time>\n ==========\n Install Questions:\nor AFTER 1/15/2000. This patch MAY NOT be installed between 12/15/1999 and\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n1/15/2000 (the Y2K Lockdown Period). \n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOIS: GRJ-0100-53031\nTest Site: Grand Junction, CO\n\n
\nPatch XM*7.1*112\n\nThe background filer checker is improved. It now lets you know which message\nit is delivering. Also, for new messages, it lets you know the last person\nto whom it was delivered.\n\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*92.\n============================================================================ \n\nROUTINES:\n\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMUT5 4497129 6383246 50,92,112\nXMUT5B 1096729 1726462 50,92,112\n\n* Checksums produced by CHECK^XTSUMBLD\nY2K Waiver Request ID#: Y2KW0001 Y2K Waiver Status: Approved\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*92.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nThis patch may be installed during the Y2K Moratorium, either BEFORE 12/15/99\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nor AFTER 1/15/2000. This patch MAY NOT be installed between 12/15/1999 and\n Select INSTALL NAME: XM*7.1*112 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n1/15/2000 (the Y2K Lockdown Period). \n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOIS: none\nTest Site: DOMAIN.EXT\n\n
\nPatch XM*7.1*107\nwhen a domain has a relay domain, which has a relay domain, which... circles\n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMA0 573755 585506 15,36,50,107\nXMA11A 291270 295406 50,107\nXMA21 2315418 2506941 4,31,50,98,107\nXMA2R 3913497 3921855 27,50,105,107\nXMAH 1544316 1548452 5,16,50,107\nXMAH1 2172709 2176845 4,50,107\nXMAPHOST 9975581 6997854 7,14,27,36,50,91,102,107\nback to itself. MailMan lets the user know what's wrong. \nXMC 3216956 3221092 13,50,107\nXMD 7129791 7425316 33,50,98,103,107\nXMDF 1438292 1442428 50,104,107\nXMDIRSND 1897078 1897188 37,50,107\nXMHIG 5360885 6112149 45,50,107\nXMHIU 5960638 8160561 50,107\nXMJMR 18651915 15901868 50,107\nXMJMT 10637487 7384600 50,107\nXMR1 14522459 14522897 7,50,94,107\nXMRENT 2263450 2263514 31,50,107\n\nXMSMAIL 4937839 4239659 59,50,107\nXMTDL1 5047763 5049974 50,107\nXMTDO 1746764 2076668 50,107\nXMVGROUP 6303194 6851604 50,104,107\nXMVSURR 2622785 2918495 50,107\nXMVVITAE 12062054 10408258 50,74,107\nXMXADDR 18270156 14565832 50,96,101,104,107\nXMXADDR1 12136703 11262685 50,78,83,96,104,107\nXMXADDR2 6515109 11569369 50,107\nXMXADDR3 * new * 6636062 107\nNOIS: ANN-1199-42486, BIL-1199-31104\nXMXADDR4 * new * 7390105 107\nXMXADDRD 9742967 10214397 50,104,107\nXMXADDRG 15444713 15011724 50,99,107\nXMXBULL 5479615 5106591 50,107\nXMXMSGS1 9891647 4910024 50,107\nXMXPARM 19474825 13144486 50,96,107\nXMXREPLY 5097167 5648876 50,85,99,107\nXMXSEND 11913872 10324142 50,106,107\nXMXUTIL 10432772 10994143 40,50,107\nXMYPOSTB * new * 483566 107\nTest Sites: Ann Arbor, MI; Biloxi, MS\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\n\nRoutine Callable at Description\n---------------------------------------------------------------------------\nXMXADDR3 N/A\nXMXADDR4 N/A\nXMYPOSTB N/A\nA typo causes an abort in APIs HDR^XMA0 and PR2^XMA0. Typo is fixed.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires Kernel patch XU*8.0*135 and MailMan patches XM*7.1*74,\nXM*7.1*94, XM*7.1*99, XM*7.1*102, XM*7.1*103, XM*7.1*104, XM*7.1*105,\nand XM*7.1*106.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n\n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan, but you should stop the background\n filer. On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nNOIS: DAY-1199-41994, WAS-1199-20590\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*107 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nTest Site: Madison, WI\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n5. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\nSometimes, when a user becomes a surrogate, his own (not the surrogate's)\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nmessages are displayed. This patch fixes that.\n\nNOIS: LAS-1299-60664\nTest Site: Las Vegas, NV\nMessage addressed to G.<space>@<local site name> invokes the space-bar recall\nfor mail group. This "feature" is now disabled.\n\nNOIS: MAD-1299-42404\nTest Site: Madison, WI\nNon-MailMan systems, such as MS Exchange, do not recognize I:<recipient>,\nY2K Waiver Exemption ID: Y2KWE0024\nand return error messages when recipients are addressed as info-only.\nMailMan now leaves off the "I:" when sending messages to info-only recipients\non non-MailMan systems.\n\nNOIS: WAS-1199-20590, BRX-1199-10383\nTest Sites: Washington, DC; Madison, WI; Bronx, NY\nSites have noticed sometimes, when becoming the Postmaster, MailMan informs\nthem that the last user to become the Postmaster was someone who is not a\nvalid Postmaster surrogate. When a package sets XMDUZ=.5 and then sends a\nmessage using ^XMD, MailMan records that use as "last used MailMan". It\nThis patch may be installed at any time during the Y2K Moratorium (including\nshouldn't. This patch fixes that.\n\nE3R: 12385\nTest Site: Tampa, FL; Albany, NY\nThis patch lets an authorized user send a limited broadcast message to a\nsubset of local users. A subset might include all users who have a certain\nprimary menu or who belong to a certain division, or any other way that users\nin the NEW PERSON file might be categorized.\n\nUsers authorized to send limited broadcasts are the POSTMASTER, any holder\nthe 12/15/1999 thru 1/15/2000 Y2K lockdown). \nof the XMSTAR key, and any holder of the new key, XMSTAR LIMITED.\nThe XMSTAR and XMSTAR LIMITED keys are mutually exclusive.\n\nLimited broadcast types are predefined in the new LIMITED BROADCAST multiple\nof file 4.3, the MAILMAN SITE PARAMETERS file:\n50 LIMITED BROADCAST (Multiple-4.32), [5;0]\n .01 LIMITED BROADCAST (MF), [0;1]\n 1 POINTED TO FILE (RNJ9,3), [0;2]\n 2 NEW PERSON FILE XREF (RF), [0;3]\n\n\nThe multiple will be loaded with 4 limited broadcasts by the post init:\nLIMITED BROADCAST POINTED TO FILE NEW PERSON FILE XREF\n----------------- ---------------------- --------------------\nDIVISION 4 (institution) "AH"\nKEY 19.1 (security key) "AB"\nPRIMARY MENU 19 (option) "AP"\nSERVICE/SECTION 49 (service/section) "E"\n\nThe cross references listed in the NEW PERSON FILE XREF field enable MailMan\nto quickly identify the users who should receive the limited broadcast\nNOIS: ANN-1199-42486\nmessages. In support of this patch, Kernel patch XU*8.0*135 adds a\nnew whole-file cross reference ("AH", on the DIVISION field) to the NEW\nPERSON file. This new cross reference enables a limited broadcast by DIVISION. \n\nYou may add more limited broadcasts to the multiple, if you wish.\n\nUsing another new field in file 4.3, you may set a limited broadcast default\nchoice, which is displayed whenever someone goes to send a limited broadcast.\n51 LIMITED BROADCAST DEFAULT, [0;20]\nThe post-init will set this field to DIVISION. You may change it if you wish.\nTest Site: Ann Arbor, MI\n\nThe option XMKSP Edit MailMan Site Parameters is updated to include the new\nfields.\n\nAdditional fixes in this patch:\n- MailMan now recognizes when a message has only 'latered' recipients. When\nforwarding or sending messages which have only 'latered' recipients, MailMan\ndid not recognize those recipients and issued an error message. This patch\ncorrects that. \n\nCircular relay domains create an allocation error. MailMan now recognizes\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires Kernel patch XU*8.0*135 and MailMan patches XM*7.1*74,\nXM*7.1*94, XM*7.1*99, XM*7.1*102, XM*7.1*103, XM*7.1*104, XM*7.1*105,\nand XM*7.1*106.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n\nPatch XM*7.1*116\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*107.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMXSEND 10324142 11102759 50,106,107,116\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nThis patch may be installed at any time,\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*107.\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n2. You do not need to stop TaskMan or the background filer.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nEXCEPT from 2/28/2000 through 3/3/2000 (the Leapyear Lockdown Period). \n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*116 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n===========================================================================\nNOIS: NHM-0100-12338\nTest Site: Northampton, MA\nFixes a bug which causes messages queued for later delivery to a personal\nmail group not to be delivered.\n\n
\nPatch XM*7.1*109\nhas any active local members. This new API is supported, as described in\nDBIA 3006.\n\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*107.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMXAPIG * NEW * 1672216 109\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\n\nThis patch may be installed at any time,\nRoutine Callable at Description\n---------------------------------------------------------------------------\nXMXAPIG $$GOTLOCAL Does a mail group have any active local members?\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*107.\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nEXCEPT from 2/28/2000 through 3/3/2000 (the Leapyear Lockdown Period). \n2. You do not need to stop TaskMan or the background filer.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*109 Loaded from Distribution <date/time>\n ==========\n\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nE3R: 13290\n ------------------------------------------------\n===========================================================================\nTest Site: Washington CIOFO@Hampton\n\nAdds a new API, $$GOTLOCAL^XMXAPIG, which checks a mail group to see if it\n\n
\nPatch XM*7.1*121\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMTDO 2076668 2076731 50,107,121\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n1. Users may be on the system during installation of this patch.\nNOIS: SHR-0200-72671\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Shreveport, LA\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*121 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nFix a typo that causes the status of a server message to remain "hand off\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nready", when it should be "hand off done". \n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n\n
\nPatch XM*7.1*115\nprocess. This patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*106.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n\n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMXBSKT 13019759 12324702 50,106,115\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nThis patch may not be installed during the Y2K Leap Year Lockdown period\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*106.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n4. On the KIDS:Installation menu, use the following options to install the\nof 2/28/2000 to 3/3/2000.\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*115 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nNOIS: PUG-0200-50349\n===========================================================================\nTest Site: Puget Sound HCS\nResequencing one of the Postmaster's transmit queue baskets while messages\nin that queue are transmitting may result in an abort in the resequencing\n\n
\nPatch XM*7.1*119\noriginal message and THEN put the original message in the delivery queue.\nThis prevents an abort which sometimes happened when the steps were the\nother way around. \n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*89.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMKP 15719989 16947852 50,89,119\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nThis patch may not be installed during the Y2K Leap Year Lockdown period\nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*89.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nof 2/28/2000 to 3/3/2000.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*119 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nNOIS: DAY-0200-41195\n===========================================================================\nTest Site: Dayton, OH\n\nFIRST add the message number of the reply to the response multiple of the\n\n
\nMailMan Patch XM*7.1*31\n\n ROUTINES:\n The second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n Name Checksum Checksum Patch List\n ---------------------------------------------------------- \n XMA1 10558704 9575986 31\n XMA21 9603768 11321545 4,31\n XMA210 1925522 1920955 31\nNOIS: NAS-1295-30255 Routines: ^XMB1\n XMA21G 10231186 9710102 31\n XMA24 10412829 10721719 31\n XMA5 11164486 11197080 31\n XMA5A 14101090 14213526 31\n XMAD2 2440129 2503657 31\n XMB1 8922945 8930890 31\n XMGAPI0 2337589 2451955 31\n XMRENT 2314897 2303842 31\n XMRPCTS 5007367 4760679 6,11,31\n XMRPCTS0 5966846 6044236 6,12,31\n CLE-0396-41473\n XMRPCTSA 4903763 3483840 6,31\n\n============================================================================\n Later'd messages report will now appear even if ^'d out of prior option.\n\nNOIS: BRX-0396-10222 Routines: ^XMAD2\n MAD-0196-40136\n MCM-0896-50571\n Fixes error caused by Later'd messages becoming new after the user has\n been deactivated and deleted from ^XMB(3.7.\n\n\nNOIS: TOM-1195-41441 Routines: ^XMA21\n Sender doesn't have to broadcast twice when forwarding.\n\nNOIS: CMO-1195-40423 Routines: ^XMA24\n Lets sender deselect ('-*') broadcast.\n\nNOIS: FTM-1195-41507 Routines: ^XMA24\n Ask sender for basket when sending to SHARED,MAIL, whether or not "ask\n basket" is set to "yes".\nNOIS: BRX-0496-11847 Routines: ^XMA5,^XMA5A\n\nNOIS: GRJ-1094-50087 Routines: ^XMA21G\n Make error message clearer by changing from "not found" to "mail group\n not found".\n\nNOIS: none Routines: ^XMA21,^XMA210\n No Nois, refer to FORUM mail msg 19872177.\n If user enters a number in response to 'send to:' prompt, and the DUZ is\n not found in ^VA(200, MailMan will no longer try to use the number as an\n IEN to pick out a mail name or remote user.\n Fixes subscript error when QD'ing numeric recipients, such as those\n\nNOIS: MWV-0396-21324 Routines: ^XMA21,^XMA21G\n This concerns what happens when a user deselects an addressee (-name or\n -g.group) at a 'send to:' prompt, after already broadcasting ('*').\n If "-g.group", MailMan lets the user know that the message will still go\n to all local users.\n If "-name", MailMan checks to see if the "name" is already specified as a\n recipient. If he is, then MailMan tells the user that the message will still\n go to all local users. If he isn't, then MailMan just tells the user that\n "name" is not found.\n @AOL.COM\n\nE3R: 8885 Routines: ^XMA21\n Removes all SSN cross-references from the lookup at the 'Send to:' prompt. \n This ensures that if the user enters a number, it cannot partial match (and\n display) an SSN. Lookup on the ^VA(200 is now confined to the following\n cross references: NAME(B), ALIAS(BB), INITIAL(C), NICK NAME(D) \n\nNOIS: ALB-0596-50002 Routines: ^XMRENT\n Prevents an error from occuring when the SENDER field (piece 4) of a message\n is zero.\n\n\nNOIS: DAY-1096-41059 Routines: ^XMGAPI0\n If a message subject is longer than 65 characters, it is truncated to the\n first 250 characters.\n\nNOIS: ANN-1096-41381 Routines: ^XMRPCTS0\n Check to make sure a task is running, rather than just assuming it is.\n\nNOIS: WPB-0894-30125 Routine: ^XMA1\n The default message action for a message which is NEWed is IGNORE, even if\nNOIS: DAY-0995-40521 Routines: ^XMA21\n the site or the user has specified that the default message action is\n DELETE. If a user deletes a message after NEWing it, the message will be\n deleted. The default is changed only for the duration of your actions on\n that particular message. When you get to the next message, your default is\n whatever it is supposed to be. \n===========================================================================\n\n This patch should be installed after hours, when user activity is at a\n minimum. You should put the XMUSER Option out of order.\n===========================================================================\n Removes phantom recipients when using XMY array during programmer calls\n \nINSTALLATION:\n 1. This routine is usually mapped on systems that allow mapping,\n so you will need to disable mapping for the affected routine.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n to ^XMB(bulletin) or ^XMD(message).\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. AXP Sites, after patch has installed, rebuild your map set.\n============================================================================ \n \n\n\nPatch XM*7.1*125\nis at a minimum. It requires MailMan patch XM*7.1*50.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\n\nXMUTERM 15130895 13549078 50,125\nXMUTERM1 14471083 14564305 50,125\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS: MAD-0100-42586\nis at a minimum. It requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Site: Madison, WI\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*125 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\nChange the option XMMGR-TERMINATE-SUGGEST.\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\nInstead of reporting on users who have never logged on, only report on such\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nusers if they were added before the IRM-supplied cutoff date. \n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*123\nThis patch also improves the background filer checker. It tells you if\nthe background filers have been shut down, and how to restart them.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*107 and XM*7.1*112.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMR1 14522897 14522719 7,50,94,107,123\nXMUT5 6383246 6643977 50,92,112,123\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS: PUG-0300-50243\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*7.1*107 and XM*7.1*112.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \nTest Site: Puget Sound HCS\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*123 Loaded from Distribution <date/time>\nFix a string length error which occurs when receiving network mail.\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\nA long sender string combined with a long subject can push a message's zero\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nnode beyond 255 chars and cause the error. This patch prevents that\nerror from occuring.\n\n\n
\nPatch XM*7.1*120\n- bulletin subjects will be truncated if they are longer than 65 characters.\n- users will no longer be able to enter a subject of the format Rnnnn.\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*107.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n\n \n Before After\nName Checksum Checksum Patch List\n----------------------------------------------------------\nXMJMS 6092728 5639134 50,120\nXMXBULL 5106591 5258679 50,107,120\n\n* Checksums produced by CHECK^XTSUMBLD\n===========================================================================\n \nNOIS: WBP-0200-22440\nINSTALLATION:\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*107.\n1. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n2. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n3. You do not need to stop TaskMan or the background filers.\n4. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Site: Wilkes Barre, PA\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*120 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n\n5. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nEnsure that subjects are 3-65 characters, and are not of the format 1"R"1.N\n===========================================================================\n(which is reserved for responses). \n\nIn particular,\n\n
\nPatch XM*7.1*122\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMDIRQST 7357280 7546757 9,50,122\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: BOI-0300-50551\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: Boise, ID\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*122 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nPrevent a site from requesting a user directory from itself.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*7.1*50.\n============================================================================ \n\n
\nPatch XM*7.1*118\n\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*107 and FileMan patch DI*22.0*30.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMJMT 7384600 7558831 50,107,118\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nThis patch may be installed at any time,\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires MailMan patch XM*7.1*107 and FileMan patch DI*22.0*30.\n1. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n2. You do not need to stop TaskMan or the background filer.\n3. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nEXCEPT from 2/28/2000 through 3/3/2000 (the Leapyear Lockdown Period). \n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*118 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n===========================================================================\nNOIS: FGH-0899-30810\nTest Site: NORTH FLORIDA/SOUTH GEORGIA\nWhen you address a message to a user, you will no longer see the "replace ...\nwith ..." prompt when the user has a long name.\n\n
\nPatch XM*7.1*128\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMHIU 8160561 8274187 50,107,128\n\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n1. Users may be on the system during installation of this patch.\nNOIS: BRX-0500-10188\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Bronx, NY\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*128 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nIn the option Help:User Information, limit user lookups on file 200 to the\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nB,BB,C, and D indexes (name, alias, initial, and nickname). \n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*107.\n\n
\nPatch XM*7.1*126\n^TMP("XMLIST",539496244,"BSKT","98 BASKET^10",1) = \n^TMP("XMLIST",539496244,"BSKT","DELIVERY^8",2) = \n^TMP("XMLIST",539496244,"BSKT","FREDOLINA^9",3) = \n^TMP("XMLIST",539496244,"BSKT","FRED^2",11) = < - not in alpha order!\n^TMP("XMLIST",539496244,"BSKT","IN^1",4) = \n\nAfter this patch, the xref looks like this:\n^TMP("XMLIST",539496244,"BSKT","98 BASKET",1) = \n^TMP("XMLIST",539496244,"BSKT","DELIVERY",2) = \n^TMP("XMLIST",539496244,"BSKT","FRED",11) = \n\n^TMP("XMLIST",539496244,"BSKT","FREDOLINA",3) = \n^TMP("XMLIST",539496244,"BSKT","IN",4) = \n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*115.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\nNOIS: TAM-0400-30135\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMXBSKT 12324702 12283844 50,106,115,126\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\nTest Site: Tampa, FL\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*115.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\nChange the "BSKT" cross reference produced by API LISTBSKT^XMXAPIB\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*126 Loaded from Distribution <date/time>\n ==========\nto ensure that the baskets are always in alphabet order.\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nExample:\nBefore this patch, the xref looks like this:\n\n\nPatch XM*7.1*110\nTest Site: Dayton, OH\nXMXEDIT 3880586 7247978 50,110\nXMXMSGS 10966038 9819629 50,110\nXMXMSGS2 6491081 7686410 50,106,110\nXMXSEC 18599731 21173851 50,110\nXMXSEC1 13791136 11938650 50,95,110\nXMXSEC2 21310509 27323685 50,89,95,110\nXMXSEC3 * NEW * 4290614 110\n \n* Checksums produced by CHECK^XTSUMBLD\n \nDon't display user's DUZ when displaying a list of latered messages from which\nThis patch introduces the following new routines:\n \nRoutine Callable at Description\n---------------------------------------------------------------------------\nXMJMOI1 N/A\nXMJMP2 N/A\nXMXSEC3 N/A\n===========================================================================\n \nINSTALLATION:\nto choose.\nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires FileMan patch DI*22.0*17 and MailMan patches XM*7.1*72,\nXM*7.1*79, XM*7.1*95, XM*7.1*100, XM*7.1*101, and XM*7.1*121.\n1. Users may be on the system during patch installation.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer. Users may be\n on the system.\n \n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*110 Loaded from Distribution <date/time>\n ==========\n Install Questions:\nNOIS: ISD-0200-71796\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \nTest Site: CIOFO-Dallas\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf you copy a PackMan or KIDS message and send it "priority", MailMan might\nnot recognize the copy as a PackMan or KIDS message. This patch fixes that.\n \nNOIS: TAM-0200-32595\n \nTest Site: Tampa, FL\nThe bulletin APIs SENDBULL^XMXAPI and TASKBULL^XMXAPI are changed so that\nthey don't insist on having XMBODY, which is an optional parameter.\n \nNOIS: WAS-1299-20453\nTest Site: Washington, DC\nIf a scrambled message with no hint is sent to a remote site, MailMan does\nnot recognize that it is scrambled. This patch fixes that.\n \nNOIS: WBP-0100-21166\nNOIS: ALN-1199-12259\nTest Site: Wilkes Barre, PA\nIf you queue a range of messages to print later, and then delete the messages\nyou queued, MailMan won't print them. This patch fixes that.\n \nE3R 12092, 13084 - Provide "new toggle" command to make messages new if\nthey're not new, and make them not new if they're new. The command is "NT".\nHelp frames have been updated to include the new command, and a new help\nframe, XM-U-M-NEW-2, explains it. New API: NTOGLMSG^XMXAPI\n \nE3R 12169 - Provide a command to add the user's network signature to an\nTest Site: Albany, NY\noriginal message. The command is "NS", and is available at the transmit\nprompt when sending a new message. It is also available when editing a\nmessage sent only to oneself. Help frames have been updated to include the\nnew command, and a new help frame, XM-U-M-NETWORK SIGNATURE, explains it.\nNew API: NETSIG^XMXEDIT\n \nE3R 13400 - Upon return from ANSWER, COPY, or WRITE command, redisplay\nmessage header to make it clear that you are back at original message. \n \nAdditional enhancements:\nWhen you save a new message to a different basket, it updates the last message\n- When editing a message the user has sent only to himself, the user may now\nscramble or unscramble the message, and add his network signature to the\nmessage, too.\n- When answering a message, if the user doesn't have a network signature,\nMailMan now asks the user if he would like to create one.\n- Added entry and exit action to option XMEDITMG so that MailMan knows that\na user is interactively editing a mail group.\n \nNOTE: This patch should be installed after hours, when user activity is at a\nminimum. It requires FileMan patch DI*22.0*17 and MailMan patches XM*7.1*72,\narrival date, and MailMan may tell you that a new message arrived, when it\nXM*7.1*79, XM*7.1*95, XM*7.1*100, XM*7.1*101, and XM*7.1*121.\n============================================================================ \n \nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nreally didn't. This patch fixes that.\nXMA0 585506 305822 15,36,50,107,110\nXMA2R 3921855 3986868 27,50,105,107,110\nXMJBM 12165199 10706426 50,110\nXMJDIR 2003843 5974273 50,110\nXMJMA 2991838 3663986 50,110\nXMJMC 8264139 9725999 50,79,110\nXMJMCODE 11042686 11817911 50,110\nXMJMD 7370688 9220624 50,104,110\nXMJMFA 6204287 6600695 50,110\nXMJMFB 15137131 15590623 50,110\n \nXMJMLN 13240819 13840736 50,110\nXMJMLR 13545823 14100278 50,110\nXMJMLR1 7836320 6891665 50,72,110\nXMJMOI 17103064 16677374 50,87,89,110\nXMJMOI1 * NEW * 3117776 110\nXMJMOIE 4582157 2143008 50,110\nXMJMOR 14209869 13211462 50,75,110\nXMJMORX 14790879 14207041 50,110\nXMJMORX1 2472219 2575833 50,110\nXMJMP 16560016 13553026 50,75,100,110\nNOIS: DAY-0899-41718\nXMJMP1 14502445 16386050 40,50,75,110\nXMJMP2 * NEW * 2711990 110\nXMJMQ 16042167 15891582 40,57,70,50,96,110\nXMJMQ1 3608941 7395902 40,50,110\nXMJMRO 2478663 4304954 50,89,110\nXMJMSO 12952439 7280605 50,110\nXMTDO 2076731 1653155 50,107,121,110\nXMVVITA 4257402 4785601 50,101,110\nXMXANSER 2242310 1893573 50,110\nXMXAPI 6705900 6992361 50,110\n\n
\nPatch XM*7.1*124\nis at a minimum. It requires MailMan patch XM*7.1*110.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\n\nXMXMSGS 9819629 9944188 50,110,124\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\nNOIS: TAM-0400-30289\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: Tampa, FL\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*7.1*124 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nThe API MOVEMSG^XMXAPI should not require XMK (basket number) when\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nXMZ (message IEN in MESSAGE file) is used to identify a message,\nbut it does. This patch corrects that.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*7.1*127\nNOIS: REN-0300-62618\nXMTDL2 8743997 9530207 50,127\nXMXADDR1 11262685 11852631 50,78,83,96,104,107,127\nXMXEDIT 7247978 7275716 50,110,127\nXMXMSGS2 7686410 7381168 50,106,110,127\nXMXPARM 13144486 14291441 50,96,107,127\nXMXPARM1 5657265 2907067 50,96,127\nXMXSEC 21173851 23410717 50,110,127\nXMXUTIL 10994143 11858021 40,50,107,127\nXMXUTIL4 8973867 8751511 50,96,127\nXMYPOSTC * NEW * 190385 127\nTest Site: Reno, NV\nXMYPRE7 * NEW * 35197 127\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routines:\nXMYPOSTC has no user callable entry points.\nXMYPRE7 has no user callable entry points.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nEnsure that MailMan does not decrement new message counters below zero.\nis at a minimum. It requires MailMan patch XM*7.1*110.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nThanks to additional test sites:\n Install Package(s)\n Select INSTALL NAME: XM*7.1*127 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nPuget Sound HCS\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n6. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n\n===========================================================================\nE3R 2731, 5983, 6044 - At the "Enter message action: IGNORE//" prompt, two\nnew actions have been added to let you access user and mail group help:\n HG Help:Group Information\n\n HU Help:User Information\nExisting help frames have been updated.\n\nE3R 3521 - At the "Enter message action: IGNORE//" prompt, a new\naction has been added to let you easily print to the VA FileMan Browser:\n BR Print to the Browser\nExisting help frames have been updated, and a new help frame,\nXM-U-M-BROWSER, has been created.\n\nE3R 5451, 13225 - When filtering a message during message delivery to your\nNOIS: REN-1099-63025\nmailbox, you can now automatically set the message vaporize date. You can\nalso specify that the message should not be made new. You can set these\nnew fields under Personal Preferences:Message Filter Edit.\nThis will only apply to new messages which you have not seen before. It\nwon't apply to responses or forwarded messages with responses. It won't\napply when you filter messages which are already in your mailbox. \nA new help frame, XM-U-P-FILTER ACTIONS, has been added, and existing help\nframes have been updated.\n\nE3R 5100, 13891 - When addressing a message, if an addressee is not found in\nTest Site: Reno, NV\nthe local user file, MailMan now asks "Do you want to check the REMOTE USER\nDIRECTORY? No//". Also, if we do check it and find an entry, MailMan now\nasks "OK?", instead of simply selecting it. This should prevent unwanted\naddressees, because the REMOTE USER DIRECTORY entry might not be what the\nsender wants.\n\nE3R 6861 - If a user has read all the responses of a message, then when he\ngoes to read the message, only the message header is displayed, followed by\nthe "Enter message action: IGNORE//" prompt. Inexperienced users may not\nknow to enter 'B' to Backup. MailMan now gives the following information:\nIf a message is queued to print later, and the user has chosen to print\n"You are at the end of this message. Enter 'B' to Backup and review it."\n\nE3R 13475 - When showing information about a mail group\n(option XMHELPGROUP), in addition to showing member groups, also show\ngroups to which the group belongs (Is a member group of:)\nTo accomplish this, a whole-file cross reference, "AD", is added to the\n.01 field (MEMBER GROUP NAME) of the MEMBER GROUP multiple of file 3.8.\nThe post-init, which comes with this patch, will populate the xref.\nExisting help frames have been updated.\n\na range of responses, which includes the last response, then when it comes\nAdditionally:\n\n- The "RI" (Reply and include responses) command now has a new capability to\nlet you include responses from another message. This capability is also\navailable when creating a new message ("IM" Include Message).\nA new help frame, XM-U-M-INCLUDE MESSAGE, has been added, and existing help\nframes updated.\n\n- The SCRAMBLE^XMXEDIT API now checks to ensure that the key and hint\nconform to the limitations set by the data dictionary.\ntime to print the message, if more responses have since arrived, then\n\n- Those APIs which return error text\nin ^TMP("XMERR",$J,<error number>,"TEXT",i), now also\nreturn, for errors whose text is in the DIALOG file:\n^TMP("XMERR",$J,<error number>)=<dialog file ien>\n^TMP("XMERR",$J,"E",<dialog file ien>,<error number>)=""\nand, for a very small subset of errors,\nif something is wrong with one of the input parameters:\n^TMP("XMERR",$J,<error number>,"PARAM","ID")=<parameter name>\n^TMP("XMERR",$J,<error number>,"PARAM","VALUE")=<parameter value>\nthey'll be printed, too.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*7.1*110.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nXMHIG 6112149 6746672 45,50,107,127\nXMJMOI 16677374 17925576 50,87,89,110,127\nXMJMOIE 2143008 3061396 50,110,127\nXMJMP 13553026 15950247 50,75,100,110,127\nXMJMR 15901868 20504072 50,107,127\nXMJMRO 4304954 4485523 50,89,110,127\nXMJMSO 7280605 8232068 50,110,127\nXMTDF 3998255 4326406 50,127\n\n\nMailman patched through 30 Oct 1996\n\n
\nPatch XM*8.0*4\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMCP 2311480 2312858 4\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time. It has no patch prerequisites,\nexcept, of course, that MailMan 8.0 be installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \nNOIS: ISD-0802-72865\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nTest Site: FO-Dallas\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*4 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*4\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nTwo function entry points in a Poller routine do not have the required open\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nand close parentheses. This patch fixes that.\n\nNOTE: This patch may be installed at any time. It has no patch prerequisites,\nexcept, of course, that MailMan 8.0 be installed.\n\n
\nPatch XM*8.0*14\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*8.0*8.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMCQH 5816398 6140105 8,14\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*8.0*8.\nNOIS: CMH-0103-N0393\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: CMOP-Hines\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*14 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*14\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf you run OPTION: Historical Queue Data/Stats Report [XMQHIST] after you\ninstall Kernel patch XU*8.0*189, the default start date appears as a 5-digit\nnumber, instead of the current month and year. This patch fixes that.\n\n\n
\nPatch XM*8.0*10\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*8.0*6 and XM*8.0*8.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\n\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMA30 10571799 10649028 10\nXMA32A 9150003 9204908 10\nXMCQ 4988121 4998052 10\nXMCQA 6587405 6634954 8,10\nXMCX 5865594 5876513 6,10\nXMHIG 6374158 6438217 10\nXMJBL 4988691 5051435 10\nXMJMD 9375016 9431467 10\nNOIS: CPH-0601-42716\nXMJMQ 14078177 14105562 10\nXMP2A 8263048 8327294 10\nXMPC 5352206 5360977 10\nXMPH 4952939 4962739 10\nXMUT2 6124745 6195089 10\nXMUT5 6643977 6663310 10\nXMUTERM1 17510874 17593134 10\nXMUTPUR0 2780450 2889401 10\nXMXPRT 3257492 3274601 10\n* Checksums produced by CHECK^XTSUMBLD\nTest Site: Central Plains HCS\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patches XM*8.0*6 and XM*8.0*8.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nThis patch corrects the check to see if a device is a Video Terminal.\n Install Package(s)\n Select INSTALL NAME: XM*8.0*10 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*10\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nVideo Terminal names *start* with "C-". The check now reflects this.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n(Previously, MailMan assumed, wrongly, that if the device name *contained*\n"C-", that it was a Video Terminal.)\n\n
\nPatch XM*8.0*11\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\n\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMC1A 3411138 3522021 11\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS: PAL-0402-60941\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\nTest Site: Palo Alto HCS\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*11 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*11\n\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\nWhen trying to connect to a site which is unreachable for whatever reason,\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nMailMan may burn CPU cycles in a tight loop. The patch adds a 1 second\nhang within the loop to mitigate that.\n\n\n
\nPatch XM*8.0*13\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*8.0*10.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMA30 10649028 10730063 10,13\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt requires MailMan patch XM*8.0*10.\nNOIS: CMH-0103-N0418\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: CMOP-Hines\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*13 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*13\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf you run OPTION: Message statistics [XMSTAT], and select "M" for "All\nMailboxes", MailMan reports on "Inactive Mailboxes", instead. This patch\nfixes that.\n\n\n
\n * * * * * ATTENTION * * * * *\n\nc. Edit the PRE-OPEN EXECUTE (#19.7) field of the P-MESSAGE entries in\n the DEVICE (#3.5) file, using the instructions as a *pattern*.\n (Note: There may be some differences, depending on your system.)\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nVMS/DSM sites might look like this. *** Your site may vary slightly. ***\n-------\nBefore:\nPRE-OPEN EXECUTE:\n S IO=$P(IO,".")_$J_"."_$P(IO,".",2)\n\nNOIS: BRX-0802-12085\nAfter:\nPRE-OPEN EXECUTE:\n D EN^XMAPHOST Q:$G(POP) S IO=$P(IO,".")_$J_"."_$P(IO,".",2)\n =========================\n <<Add the underlined text to the beginning. Please note that there are >>\n <<2 spaces after the 'Q:$G(POP)'! Do not make any other changes. It is>>\n <<OK for the rest of the text to look different from what's shown here. >>\n\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nCache OpenM/NT and Cache VMS sites might look like this.\nP-MESSAGE has the following problems:\n---------------------------- *** Your site may vary slightly. ***\nBefore:\nPRE-OPEN EXECUTE:\n S IO=$P(IO,".")_$J_"."_$P(IO,".",2)\n\nAfter:\nPRE-OPEN EXECUTE:\n D EN^XMAPHOST Q:$G(POP) S IO=$P(IO,".")_$J_"."_$P(IO,".",2)\n =========================\n <<Add the underlined text to the beginning. Please note that there are >>\n1) A calling program can't get the message number back.\n <<2 spaces after the 'Q:$G(POP)'! Do not make any other changes. It is>>\n <<OK for the rest of the text to look different from what's shown here. >>\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n\n7. Edit the P-MESSAGE entries in the TERMINAL TYPE (#3.2) file.\na. First, print out a copy of the P-MESSAGE entries in the TERMINAL TYPE\n (#3.2) file, so you have a record of what they look like before you edit\n them. This is very important, so you can refer back to it in case you\n make an editing mistake.\nb. Edit the CLOSE EXECUTE (#7) field of the P-MESSAGE entries in the\n2) Users aren't able to specify subject, sender, and recipients if they\n TERMINAL TYPE (#3.2) file, using the instructions as a *pattern*.\n (Note: There may be some differences, depending on your system.)\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nVMS/DSM sites might look like this. *** Your site may vary slightly. ***\n-------\nBefore:\nCLOSE EXECUTE: \n W:$X ! S XMREC="R X#255:1" X "U IO:DISCONNECT" D ^XMAPHOST,READ^XMAPHOST\n ==================== ==========\n X "C IO:DELETE" K XMIO,IO(1,IO) Q\nqueue the print.\n ===== ==\n <<Delete the underlined text. Do not make any other changes. It is >>\n <<OK for the rest of the text to look different from what's shown here.>>\n\nAfter:\nCLOSE EXECUTE:\n W:$X ! X "U IO:DISCONNECT" D READ^XMAPHOST X "C IO:DELETE" K IO(1,IO)\n\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nCache OpenM/NT and Cache VMS sites might look like this.\n\n---------------------------- *** Your site may vary slightly. ***\nBefore:\nCLOSE EXECUTE: \n W:$X ! S XMREC="R X#255:1" U IO:("R") D ^XMAPHOST,READ^XMAPHOST\n ==================== ==========\n X "C IO:""D""" K XMIO,IO(1,IO) Q\n ===== ==\n <<Delete the underlined text. Do not make any other changes. It is >>\n <<OK for the rest of the text to look different from what's shown here.>>\n\nThis patch fixes these problems, which have also been mentioned in the\nAfter:\nCLOSE EXECUTE:\n W:$X ! U IO:("R") D READ^XMAPHOST X "C IO:""D""" K IO(1,IO)\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n\n8. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n9. You may delete the post-init, ^XMYPRE1.\n============================================================================\nfollowing E3Rs:\n\n You must make manual changes to your P-MESSAGE entries\nE3R: 5147,6405,13621\nWhen printing to the P-MESSAGE device, perform all user interaction before\nthe text is put into the message, and enable users to specify P-MESSAGE\nsubject, sender, and recipients even if they queue the print.\n\nE3R: 13766\nWhen printing to the P-MESSAGE device, return the message number of the\nmessage created. The message number will be returned only if the calling\nprogram has set the variable XMZBACK. If $D(XMZBACK), then XMZ will be\nset upon return, and XMZBACK will be killed.\n in your DEVICE (#3.5) and TERMINAL TYPE (#3.2) files!\n\nE3R: 14895\nWhen printing to the P-MESSAGE device, and the user has chosen to have the\nmessage appear to be from the POSTMASTER, put the user's DUZ in the SENDER\n(#1.1) field of the MESSAGE (#3.9) file.\n\nThe post-init ensures that some DIALOG (#.84) file entries which are no\nlonger needed are deleted.\n\nNOTE: This patch should be installed during off hours, when user activity\n Please read and follow the patch instructions for details on the changes!\nis at a minumum. It requires MailMan patch XM*8.0*10, as well as\nKernel patches XU*8.0*162 and XU*8.0*175.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n \n Before After\nName Checksum Checksum Patch List\n * * * * * ATTENTION * * * * *\n--------------------------------------------------------------------------\nXMAPHOST 7077399 9091852 2\nXMUT5 6663310 6762357 10,2\nXMYPRE1 * NEW * 68287 2\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nXMYPRE1 has no user entry points, and may be deleted following install.\n============================================================================\n \n\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minumum. It requires MailMan patch XM*8.0*10, as well as\nKernel patches XU*8.0*162 and XU*8.0*175.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\nPatch XM*8.0*2\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*2 Loaded from Distribution <date/time>\n ========\n\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\nTest Sites: Bronx, NY; Tampa, FL; Montana HCS; Altoona, PA\n ------------------\n6. Edit the P-MESSAGE entries in the DEVICE (#3.5) file.\na. First, print out a copy of the P-MESSAGE entries in the DEVICE (#3.5)\n file, so you have a record of what they look like before you edit them.\n This is very important, so you can refer back to it in case you make an\n editing mistake.\nb. Make sure the first 9 characters of the device name is "P-MESSAGE". If\n it isn't, queued p-messages will not contain the requested subjects, or\n be delivered to the requested users. Default values will be used,\n instead.\n\n\nPatch XM*8.0*15\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMJMOI 14666274 15155593 15\nXMXAPI 7362843 7484319 15\nXMXAPIU 596863 904353 15\nXMXPARM 14944409 15011904 15\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS: TUA-0203-31789\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: Tuscaloosa, AL\n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*8.0*15 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*15\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nIf you forward a message to broadcast, agree that you'd like to set a\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nvaporize date, but enter ^ at the vaporize date prompt, the message is\nbroadcast. This patch will change the process, so that an ^ will abort\nthe broadcast.\n\n
\nPatch XM*8.0*16\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMXAPIG 5257560 5257560 16\nXMXBSKT 12498784 12520227 16\nXMXGRP 9498223 9498181 16\nXMXMSGS2 8470689 8537934 16\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS: ISL-0303-51989\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: OIFO Salt Lake\n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*8.0*16 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*16\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nIf you use the API ADDMBRS^XMXAPIG to add a remote user to a mail group\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nin the MAIL GROUP (#3.8) file, MailMan adds the user to the DISTRIBUTION\nLIST (#3.813) multiple, instead of to the REMOTE MEMBER (#3.812) multiple.\nThis patch fixes that.\n\n
\nPatch XM*8.0*17\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*8.0*2.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMAPHOST 9091852 9096253 2,17\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*8.0*2.\nNOIS: MWV-0403-20860\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: Martinsburg, WV\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*17 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*17\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nP-MESSAGE assumes that if there are more than 66 consecutive null lines in a\nprint-out, that we must have reached the EOF. This patch changes that limit\nto 250.\n\n\n
\nPatch XM*8.0*19\nis at a minimum. It requires MailMan patch XM*8.0*6.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\n\nXMRUCX 1138934 1139164 6,19\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*8.0*6.\n1. Users may be on the system during installation of this patch.\nNOIS: none\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: BCMA Contingency\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*19 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*19\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThis patch helps make MailMan GT.M ready. All sites should install this\npatch.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*8.0*20\nNOTE: This patch should be installed during off hours, when user activity is\nat a minimum. It has no requirements, except that MailMan 8.0 be installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMA21 2501947 2566788 20\nXMAH 1584093 104835 20\nXMJMSO 10097928 10159973 20\nXMJMT 8959953 8989620 20\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nNOIS: TAM-0703-30693\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity is\nat a minimum. It has no requirements, except that MailMan 8.0 be installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\nTest Site: Tampa, FL\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*20 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*20\n\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\nCurrently if you want to create a message and set a date for it to vaporize,\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nthe earliest allowable vaporize date is the next day. This patch changes\nthe earliest vaporize date to 60 minutes from now.\n\n\n
\n * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\nTest Site: Las Vegas, NV\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nThe communications testing routine, XMCDNT, distributed with MailMan 8.0\n7. In the TCP/IP DEVICE (#8.25) field of the MAILMAN SITE PARAMETERS (#4.3)\n file, enter the name of the device used at your site for TCP/IP scripts.\n If you don't know it, you can find it by doing a FileMan Inquiry for FORUM\n (or any other domain with a TCP/IP script) in the DOMAIN (#4.2) file:\n\nSelect OPTION: INQUIRE TO FILE ENTRIES\nOUTPUT FROM WHAT FILE: DEVICE// 4.2 DOMAIN (548 entries)\nSelect DOMAIN NAME: DOMAIN.EXT\nANOTHER ONE:\nSTANDARD CAPTIONED OUTPUT? Yes// (Yes)\nwas an old version which does not work. This patch provides a version\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no\n Computed Fields\n\nNAME: DOMAIN.EXT FLAGS: S\n PHYSICAL LINK DEVICE: NULL DEVICE <<< 2nd choice <<<\nTRANSMISSION SCRIPT: TCP/IP PRIORITY: 5\n NUMBER OF ATTEMPTS: 30 TYPE: Simple Mail Transfer Protocol\n PHYSICAL LINK / DEVICE: NULL DEVICE <<< 1st choice <<<\n\nYour first choice for the device is the one in the TCP/IP script. If there\nthat works.\nisn't any there, then your second choice is as indicated. Note:\n- Not all of the fields are shown in this example.\n- Your TCP/IP script may have a different name from the one shown.\n- Your device may have a different name from the one shown.\n===========================================================================\n\n2. This patch also adds a new field to the MAILMAN SITE PARAMETERS (#4.3)\nfile. You should fill it in with the DEVICE you normally use for your\nTCP/IP scripts in DOMAIN (#4.2) file. With the addition of this new field,\nit is now possible to distribute new domains automatically, rather than\nhaving you enter them manually. Here's the new field:\n ATTENTION!\n\nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\nSTORED IN ^XMB(1,\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n4.3,8.25 TCP/IP DEVICE NETWORK;5 FREE TEXT\n INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X I $D(X) S %ZIS="NQRS",IO\n P=X D ^%ZIS K:POP X S:$D(X) X=ION W:$D(X) " Sto\n\n red internally as ",X D ^%ZISC S IOP="HOME" D ^\n %ZIS K IOP,%ZIS\n HELP-PROMPT: Which device shall be used for TCP/IP?\n DESCRIPTION: For TCP/IP connections, the physical\n link/device to be used is usually standard -\n some sort of NULL device. This field is a\n free-text pointer to that device in the DEVICE\n (#3.5) file.\n\n The device pointed to by this field will be\n This patch contains a new field, which you should populate.\n used for a TCP/IP connection if, in the DOMAIN\n (#4.2) file, the device field is null in both\n of the following fields:\n - PHYSICAL LINK / DEVICE (#1.3) field of the\n TRANSMISSION SCRIPT (#4) multiple\n - PHYSICAL LINK DEVICE (#17) field\n\n For more information, see the PHYSICAL LINK\n DEVICE (#17) field, in the DOMAIN (#4.2) file.\n\n * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n\n3. Finally, this patch corrects the descriptions in two fields:\n- MAIL GROUP (#3.8) file, MEMBER GROUPS (#11) field - invalid information\ndeleted\n- DOMAIN (#4.2) file, PHYSICAL LINK DEVICE (#17) field - information about\ndefault values corrected\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except, of course, that\n\nMailMan 8.0 be installed. Installation will take less than 1 minute.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nPatch XM*8.0*3\nXMCDNT 401792 659873 3\nXMKPR1 5051210 5167213 3\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except, of course, that\n\nMailMan 8.0 be installed. Installation will take less than 1 minute.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan or the\n background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n1. NOIS: LAS-0802-62501\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*3 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*3\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n
\nPatch XM*8.0*21\nis at a minimum. It requires MailMan patch XM*8.0*17.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\n\nXMAPHOST 9096253 9963881 2,17,21\nXMD 7748228 7841354 21\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*8.0*17.\nNOIS: ZZZ-0703-N1995\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: CoreFLS Dev\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*21 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*21\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nP-MESSAGE can abort if MailMan notices any errors in the user's setup.\nThis patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nPatch XM*8.0*23\nis at a minimum. It has no patch pre-requisites.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\n\nXMPG 4410165 4460555 23\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisites.\n1. Users may be on the system during installation of this patch.\nNOIS: ISP-0903-N2480\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nTest Site: Bay Pines OIFO\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*23 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*23\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nThe API, ENT^XMPG, does not check to ensure that the user who is using it\nhas an access code and a mailbox. This patch fixes that.\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\n * * * * * * * * * * * * * * * * * * * *\nPatch XM*8.0*22\nSEND: W XMSG ; S XMTRAN="S: "_XMSG D TRAN^XMC1 Replace MSG With MSG,!\n === =====\n Replace <press enter>\n =============\n W XMSG,! ; S XMTRAN="S: "_XMSG D TRAN^XMC1\n\nSelect COMMUNICATIONS PROTOCOL NAME:\n\n8. The Kernel Systems Manual tells you how to set up HFS (Host File Server)\ndevices. (In v8, Chapter 18 on Host Files is pages 229-232.) If your site\n\nis using an HFS device to send mail to and receive mail from another site,\nyour settings should deviate from the recommendations in the manual as\nfollows:\n\nUsing FileMan:\n\nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n =====\nINPUT TO WHAT FILE: COMMUNICATIONS PROTOCOL// DEVICE \n ======\nNOIS: CMC-0803-31054\nEDIT WHICH FIELD: ALL// ASK HOST FILE\n ========\nTHEN EDIT FIELD: ASK HFS I/O OPERATION\n =======\nTHEN EDIT FIELD: <press enter>\n\nSelect DEVICE NAME: HFS <=== Yours may be different\n ===\nASK HOST FILE: YES// <=== Must be YES\nASK HFS I/O OPERATION: YES// <=== Must be YES\nTest Sites: Tennessee Valley HCS (DSM/VMS); Murfreesboro CMOP (Cache/NT);\n\nASK HOST FILE should be set to YES, so that you will be prompted for\n"HOST FILE NAME:". The site creating the host file could accept the default\nor select a name. The site reading the host file would enter the name of\nthe file from the sending site.\n\nASK HFS I/O OPERATION should be set to YES, so that you will be prompted\n"INPUT/OUTPUT OPERATION:". The site creating the host file would answer\n"NEW", and the site reading the host file would answer "READONLY".\n\n Charleston CMOP (Cache/NT); Portland, OR (Cache/VMS)\nThis is what it should look like when you use the options:\n\nOption: Sequential Media Queue Transmission [XMS-SEQ-TRANSMIT]\n \nThis option lets you select only those queues which have messages. If\nyou can't select a queue, it either doesn't exist or it has no messages.\n\nSelect DOMAIN NAME: DOMAIN.EXT 1 msgs\nDEVICE: HOME// HFS DISK FILE\nHOST FILE NAME: TMP.TMP//FORUM.DAT INPUT/OUTPUT OPERATION: ?\n\nEnter one of the following host file input/ouput operation:\n R = READONLY\n N = NEWVERSION\n RW = READ/WRITE\n INPUT/OUTPUT OPERATION: N\n\nDumping messages now ... Messages dumped: 1\n\nOption: Sequential Media Message Reception [XMR-SEQ-RECEIVE]\n\nAttempts to use the option Sequential Media Queue Transmission\nDEVICE: HOME// HFS DISK FILE\nHOST FILE NAME: TMP.TMP//FORUM.DAT INPUT/OUTPUT OPERATION: R\n\nMessages received: 1\n===========================================================================\n[XMS-SEQ-TRANSMIT] fail with the variable ER undefined.\nThis patch fixes that.\n \n !! A T T E N T I O N !!\nIMPORTANT: If you are using the HFS device to receive the mail, you should\neither have an HFS_IN device with the Open Parameter set to ReadOnly or set\nthe ASK HFS I/O OPERATION to YES and choose READONLY when using the device.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisites.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n You must manually CHECK entries in the\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMCB 3553056 3880657 22\nXMR 11613068 11821822 22\nXMTDR 10257008 10279631 22\n* Checksums produced by CHECK^XTSUMBLD\n\n DEVICE FILE and\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisites.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n COMMUNICATIONS PROTOCOL FILE\n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n and CORRECT them, if necessary.\n Select INSTALL NAME: XM*8.0*22 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*22\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n See instructions.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n7. This is a repeat of the information provided in patch XM*7.1*193.\nIf you use the MailMan option for transferring VistA email messages via\ndisk/tape to another site, you will have problems if the SEND field\nsetting for the TAPE entry in the Communications Protocol file is wrong.\nThe SEND field for the TAPE entry must be set to:\n * * * * * * * * * * * * * * * * * * * *\n\nSEND: W XMSG,! ; S XMTRAN="S: "_XMSG D TRAN^XMC1\n ==\nMost of the entries we have found for this don't have the ",!" following\nthe "W XMSG". Without the ",!" you don't get the line feed at the end of\neach line. This causes a buffer overflow when you try to receive the\nmessage. Please look at your entry, and edit, if necessary:\n\nUsing FileMan:\n\n\nSelect OPTION: ENTER OR EDIT FILE ENTRIES \n =====\nINPUT TO WHAT FILE: COMMUNICATIONS PROTOCOL// <press enter>\nEDIT WHICH FIELD: ALL// SEND\n ====\nTHEN EDIT FIELD: <press enter>\n\n\nSelect COMMUNICATIONS PROTOCOL NAME: TAPE\n ====\n\n
\nPatch XM*8.0*24\n\n It is strongly recommended that you answer YES\n to prevent your site from unwittingly relaying\n destructive mail.\n\n If you answer YES, you should define your\n "inside" sites in the MY DOMAIN (field #41)\n multiple, so that MailMan can distinguish them\n from outside sites.\n\n Note: This does NOT prevent users from\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n receiving mail from outside sites. It also\n does NOT prevent users from forwarding mail to\n outside sites. Such uses are perfectly OK.\n\n4.3,41 MY DOMAINS 4.1;0 Multiple #4.341\n\n4.341,.01 MY DOMAINS 0;1 FREE TEXT (Multiply asked)\n\n INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X\n LAST EDITED: FEB 09, 2004\n\n HELP-PROMPT: Answer must be 3-30 characters in length.\n DESCRIPTION: If you answered YES to PREVENT MESSAGE\n RELAYING? (field #40), to stop your site from\n relaying messages from outside sites through\n your site to other outside sites, you may add\n entries here, in order to define what is an\n "inside" site, or sites whose messages your\n site is willing to relay.\n\n For example, if your site is a VA site, then\nNOIS: MWV-0104-22303, TUC-0104-62259, MAD-0104-42234, PAL-0204-60051\n other VA sites are "inside" sites, and your\n site should relay mail for them. So, any\n site whose domain name ends in ".DOMAIN.EXT" is\n an "inside" site. So VA sites should have\n only one record in this multiple, and it\n should be ".DOMAIN.EXT".\n\n The default, if there are no entries in this\n multiple, is your site's domain name.\n\nTest Sites: FORUM; Martinsburg, WV; Martinez, CA; Palo Alto, CA; FO-Hines;\n MailMan will check the site name of any site\n which connects to it, and identifies itself\n in the SMTP HELO <sitename> command. If the\n sitename ends in any of the entries in this\n multiple, then any mail coming from that site\n through your site to other sites, will be\n accepted and relayed onward.\n\n If the sitename does not end in any of the\n entries in this multiple, then messages will\n Madison, WI; FO-Albany; Central Alabama HCS; Montana HCS;\n only be accepted that are addressed to\n recipients whose sitenames end in one of the\n entries in this multiple. Otherwise, the\n site will receive an error message telling it\n that relaying is denied, and messages will\n not be accepted for relaying onward.\n\n CROSS-REFERENCE: 4.341^B\n 1)= S ^XMB(1,DA(1),4.1,"B",$E(X,1,30),DA)=""\n 2)= K ^XMB(1,DA(1),4.1,"B",$E(X,1,30),DA)\n Columbus, OH\n\nThe post-init routine, ^XMYP24, will populate these fields for VA sites.\nSpecifically, PREVENT MESSAGE RELAYING? (#40) will be set to YES, and\n".DOMAIN.EXT" will be added to the MY DOMAIN (#41) multiple. Non-VA sites\nwill have to populate these fields manually if they want to prevent message\nrelaying. Routine ^XMYP24 will be deleted once it has run.\n\nOption XMKSP [MailMan Site Parameters] and Help Frame\nXM-I-S-SITE PARAMETERS-REMOTE have been modified to include the new fields.\n\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch XM*8.0*6. This patch will take less\nthan one minute to install.\n\nIMPORTANT NOTE TO NON-VA SITES:\nThis patch is only active for VA sites. VA sites are sites whose domain\nname ends in ".DOMAIN.EXT". This patch will have absolutely no effect at\nnon-VA sites. If you want to prevent MailMan at your non-VA site from\nacting as an unwitting relay, you must edit fields 40 and 41 in file 4.3.\n============================================================================ \nRecently, a MailMan site unwittingly acted as a relay for a non-VA site\n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMR1 11104837 13422146 6,24\nXMYP24 * NEW * 138765 24\nsending a message containing the MyDoom virus to another non-VA site. To\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces routine ^XMYP24, which will be deleted once the\npost-init has run.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch XM*8.0*6. This patch will take less\nthan 1 minute to install.\n\ncorrect this, MailMan will no longer relay mail from a non-VA site to a\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan or the\n background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nnon-VA site. This patch is about trying to prevent spammers and virus\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*24 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*24\n\n Incoming Files:\n\npropagators from sending their email through your site and from disguising\n 4.3 MAILMAN SITE PARAMETERS (Partial Definition)\n Note: You already have the 'MAILMAN SITE PARAMETERS' File.\n\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\ntheir messages to appear to be coming from your site.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n7. Enter a MAIL GROUP for the new bulletin XM RELAY ATTEMPTED.\n===========================================================================\n\nLet's be clear here. We're talking about when a site connects to your\nsite, and says, hi, I've got some messages for you. For instance, if the\nsite is AOL, it will say, HELO AOL.COM. Your site says "Hey, wassup?".\nThe other site says I've got a message from so-and-so, to FRED@YAHOO.COM.\nBefore this patch, MailMan would say, OK, and accept the message and\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\nrelay it on to FRED@YAHOO.COM. Now, however, MailMan will say, I'm sorry\nbut I'm not going to relay this message and act as a stooge for you - do\nit yourself. Here's an example. (I'm using AOL and Yahoo just because\nthey're familiar. I'm not suggesting that they are part of the problem.)\n\n11:24:48 R: HELO AOL.COM <--- from outside site\n11:24:48 S: 250 OK DOMAIN.EXT [8.0,DUP,SER,FTP] <--- through FORUM\n11:24:48 Waiting for input\n11:24:48 R: MAIL FROM:<WILMA@AOL.COM>\n11:24:48 S: 250 OK Message-ID:9979753@DOMAIN.EXT\n\n11:24:48 Waiting for input\n11:24:48 R: RCPT TO:<FRED@YAHOO.COM> <--- to an outside user\n11:24:48 S: 550 Relaying denied. <--- No way!\n\nIf WILMA at AOL sends you a message at your site, and you want to forward\nthe message on to FRED@YAHOO.COM, that's fine. This patch will not prevent\nyou from doing that. That's something completely different from what this\npatch is designed to prevent.\n\nThis patch adds a new bulletin which will notify the POSTMASTER any time\n ATTENTION!\nMailMan refuses to relay a message. You are encouraged to add a mail group\nto the bulletin to notify additional responsible persons.\nHere's the bulletin:\n\nNAME: XM RELAY ATTEMPTED SUBJECT: Potential SPAM or VIRUS stopped\n RETENTION DAYS: 7\n MESSAGE: A site calling itself |1| attempted to relay a message from: |3|\n to: |2| through this site.\n \n This attempt was denied.\n You should enter a MAIL GROUP for the new bulletin XM RELAY ATTEMPTED.\n \n By far the most important thing that a service provider can do to reduce\n spam or viruses is to ensure that any mail servers in operation accept only\n outgoing mail from machines within their own domains. This prohibits SMTP\n relaying, denying spammers and virus propagators a necessary component of\n anonymity.\nMAIL GROUP: POSTMASTER\n DESCRIPTION: This bulletin is sent when MailMan prevents an outside site\n from relaying a message to an outside site through this site.\nPARAMETER: 1\n\n DESCRIPTION: The name of the site attempting to relay the message through\n this site.\nPARAMETER: 2\n DESCRIPTION: The intended recipient of the message.\nPARAMETER: 3\n DESCRIPTION: The envelope from of the message.\n\nThis patch adds two new fields to the MAILMAN SITE PARAMETERS (#4.3) file:\n\nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\n Non-VA sites should read the patch description carefully. Non-VA sites\nSTORED IN ^XMB(1, (1 ENTRY)\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n4.3,40 PREVENT MESSAGE RELAY? 4;1 SET\n\n '1' FOR YES;\n '0' FOR NO;\n LAST EDITED: FEB 09, 2004\n HELP-PROMPT: Should message relaying be prevented?\n will need to set new fields manually.\n DESCRIPTION: Answer YES if you want to prevent outside sites\n from sending mail through your site to other\n outside sites. Spammers and Virus propagators\n use this technique to disguise the source of\n their mail, and to make it appear to come from\n a trusted source, namely your site.\n\n Answer NO if you want your site to act as a\n relay site for anyone.\n\n\n
\nPatch XM*8.0*25\n\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*25 contains \nchanges to a package referenced in VHA IO SEPG SOP 192-023 "Review of VISTA \nPatches for Effects on VISTA Blood Bank Software . This patch does not \nalter or modify any VistA Blood Bank software design safeguards or safety \ncritical elements functions.\n\nRISK ANALYSIS: Changes made by patch XU*8*25 have no effect on Blood Bank \nsoftware functionality, therefore RISK is none.\n\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires MailMan patch XM*8.0*19.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\nNOIS: none\n------------------------------------------------------------------\nXMJBN 10845646 11255537 25\nXMRUCX 1139164 1512174 6,19,25\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nTest Site: Martinez HCS, Puget Sound HCS\nis at a minimum. It requires MailMan patch XM*8.0*19.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*19 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*19\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nThis patch adds TCP/IP service for Cache/VMS. All sites should install\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nthis patch.\n\n7. Cache/VMS Sites: Add something like this to your VMS TCPIP script:\n$!-------------------------------------------------------------\n$! for Cache\n$! assign 'f$trnlnm("SYS$NET")' SYS$NET\n$! ccontrol session <configname> "-U" "<namespace>" "CACHEVMS^XMRUCX"\n$!-------------------------------------------------------------\n===========================================================================\n\nBlood Bank Clearance: 3/23/2004\n\n\nSee patch XM*8*18 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\n \nDIQUIET Variable is not NEWED or KILLED in the Mail Manager Routines. As \npart of a preventative measure, the DIQUIET variable is being NEWed in \nthe Mailman routines.\n\n
\n \nScheduling an option to P-MESSAGE\n\n
\nIf you stay in user menu while selecting P-MESSAGE and then go to \nanother application with the DEVICE prompt, the XMQUIET variable is not \nkilled. Therefore, the 'Subject' and the subsequent questions are not \nasked (version 3 changes).\n\n
\nDelivery queue clogged by very large messages\n\n
\nPatch XM*8.0*5\nMailMan 8.0 be installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\n\nXMJMORX1 7116146 7133283 5\nXMKPR 10051281 10056227 5\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except, of course, that\nNOIS: HIN-0902-41106\nMailMan 8.0 be installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Site: FORUM\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*5 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*5\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nIf you do a search for messages, and then forward 2 of them to a remote site,\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\nMailMan tells you that it forwarded 4 messages. This patch fixes that.\n===========================================================================\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except, of course, that\n\n
\nClose ALL OGC domains (with the "RC-<something>.GC.DOMAIN.EXT" format).\n\n
\nUndefined error at Q+12^XMXUTIL3.\n\n
\nCorrects XM*8*26\n\n
\nAllow a non-human user to send bulletins.\n\n
\nThere are two fixes in this patch: The first issue concerns an error \nmessage when trying to secure a KIDS build in Packman. The second\nissue occurs while using the XMXAPI's, the variable DIERR is being\nleaked which could cause other issues in Fileman if it is not \ncleaned up.\n\n
\nThis patch will prevent users from adding themselves as their\nown surrogate, correct the Mailman Developers Guide so \nthe documentation is accurate regarding the API XMXAPIG,\nand inactivate the domain LRN.DOMAIN.EXT.\n\n
\nThis patch updates the Mailman TCPIP entry point to handle\ninstances where the software is run on Linux based Operating \nSystems.\n\n
\n \nThis patch will address the following issues:\n1. Mailman returns an error "may not be real person"\n2. Partial message is being delivered due to multiple\nmessage parts that come through from different servers at different times.\n3. Compile errors on the $ZC command.\n\n
\nPatch XM*8.0*47 addresses five issues:\nmessage will not be sent. When using the Mailman application to send a \nmessage, subject lines are automatically truncated. The code changes will \nduplicate this functionality.\n \n3. An entry in the BULLETIN(3.6) file named XM DOMAIN ADDED makes several \nreferences to the NOIS system which is no longer used. In an effort to \ncorrect this issue and avoid future issues, the name NOIS will be \nreplaced with the more generic term "trouble ticket."\n \n4. Two Mailman API's have been confirmed to be functioning incorrectly. \n \nThe COPYAMT^XMXSEC1 API does not properly count the number of lines in a \nmail message. The OPTEDIT^XMXSEC2 API does not properly check if a \nmessage text or message subject line can be edited.\n \n5. Mailman API QX^XMXUTIL3 is not properly displaying a list of users \nthat are either current or not current in reading a message.\n1. When using the Mailman extrinsic function $$MG^XMBGRP to create a new \nmail group, if the organizer's DUZ is only 4 digits, and those 4 digits \nmatch with the last 4 of the SSN of any person in the New Person(#200) \nfile, the call will fail and the mail group will not be created.\n \n2. When using the Mailman API SENDMSG^XMXAPI, if the subject line is \nunder 3 characters or over 65 characters the API will fail and the \n\n
\nIn preparation for the VA's transition from IPv4 to IPv6 the MailMan \npackage will require modifications to make it IPv6 ready.\n\n
\nPatch XM*8.0*1\nis at a minimum. It has no patch prerequisites, except, of course, that\nMailMan 8.0 be installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n \n Before After\n\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMKP 16206281 16231239 1\nXMTDL 18753082 18995257 1\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOIS: BAY-0802-31743\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except, of course, that\nMailMan 8.0 be installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer.\nTest Site: Bay Pines, FL\n On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n STOP background filer\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nIf you send or forward a message to * (Broadcast to all local users), as well\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*1 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*1\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\nas to SHARED,MAIL, the message is not delivered to SHARED,MAIL. This patch\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n6. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\nfixes that. \n START background filer\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n\nNOTE: This patch should be installed during off hours, when user activity\n\n
\nThe variable DIRUT is being left in the partition when reports use the \nP-MESSAGE device. This can result in inappropriate program execution as\nwell as being a SAC standard violation. This patch corrects this\ndeficiency.\n\n
\nPatch XM*8.0*51 addresses an issue with two MailMan commands.\nMailMan needs to be updated to disable the EXPN and VRFY commands.\n There is no configuration option to tune SMTP commands in MailMan.\n This impacts all VistA sites that enable the MailMan service.\n\n
\nThis Mailman patch XM*8.0*52 - sets LOCKS for options, and Audit for\nfields. Please refer to the description in Forum Patch.\n\n
\nPatch XM*8.0*6\nnotify of the problem. This message gets bigger and bigger with\nsubsequent failures, because it reports on every previous failed attempt,\nwhich can number in the 1000s. This patch limits the message size by\nreporting a maximum of 100 previous failed attempts.\n\n2. Patch XM*8.0*1 failed to include the patch number in the second line of\nroutine ^XMTDL. This patch adds it.\n\n3. For GT.M systems, change the listener from the non-standard port 2525\nto standard 25 in routine ^XMRUCX.\n\n\n4. In routine ^XMR1, add a check to reject a connection if the site\nattempting to connect is listed in the NETWORK SENDERS REJECTED (#4.501)\nfile.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patches XM*8.0*1 and *5.\n============================================================================ \n\nROUTINES:\nRemedy Ticket: HD 12891 / CHG 4269\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMCX 5550363 5865594 6\nXMKPR 10056227 11722808 5,6\nXMR1 10825754 11104837 6\nXMRUCX 1143285 1138934 6\nTest Sites: MPI-AUSTIN, CIOFO-ALBANY\nXMTDL 18995257 18999651 1,6\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patches XM*8.0*1 and *5.\n1. Users may be on the system during installation of this patch.\n\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan,\n but you should stop the background filer. Failure to do so may result\n in "source routine edited" errors.\n On the Manage MailMan:Local Delivery Management menu, use the\n following option to stop the background filer:\n STOP background filer\nThis patch contains several fixes.\nAre you sure you want the BACKGROUND FILERS to STOP delivering mail? NO// YES\n ===\n<< Background filer will stop soon. >>\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*8.0*6 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*6\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n1. When MailMan has tried all the scripts to transmit a queue, and the\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Do NOT queue it!>\n ------------------\n6. Start the background filer.\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n<< Background filer will start soon. >>\n7. DSM Sites: After patch has installed, rebuild your map set, if necessary.\ntransmission still fails, MailMan sends the postmaster a message to\n===========================================================================\n\n
\nPatch XM*8.0*7\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\n\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMRTCP 3549159 3556521 7\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nRemedy Ticket: HD 13399 / CHG 4289\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\nTest Site: Long Beach, CA\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*7 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*7\n\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\nThis patch fixes a problem in routine ^XMRTCP. It attempts to access a\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nnon-existing variable called XMB("LASTTRY"). The actual name of the\nvariable is XMB("LAST TRY").\n\n\n\nPatch XM*8.0*8\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\n\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMCQA 6380548 6587405 8\nXMCQH 2468361 5816398 8\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nRemedy Ticket: HD 11287 / CHG 4299\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\nTest Site: CMOP-HINES\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*8 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*8\n\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\nThe Transmission Queue History report produced by OPTION: Historical Queue\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nData/Stats Report [XMQHIST] shows zero sent and received for every site.\nThis patch fixes that.\n\n\n
\nPatch XM*8.0*9\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXMJMOR 14793912 14800752 9\nXMJMORX 13578226 13600647 9\nXMJMP 15497599 15552495 9\nXMJMP1 18918998 18999813 9\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS: TOG-0502-11848\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisites, except that MailMan 8 must\nbe installed.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \nTest Site: Togus, ME\n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: XM*8.0*9 Loaded from Distribution <date/time>\n ========\n Install Questions for XM*8.0*9\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nWhen using the option "Read/Manage Messages" and selecting to print a\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nmessage from the displayed list, if an ^ is entered at the device prompt\nto abort, MailMan will echo back 1 message printed. Nothing actually\nprints. This patch fixes that.\n\n
\nPatch XM*8.0*12\nNOTE: This patch may be installed at any time.\nIt has no patch prerequisites, except that MailMan 8 must be installed.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;8.0;MailMan;**[patch list]**;Jun 28, 2002\n\n Before After\nName Checksum Checksum Patch List\n\n------------------------------------------------------------------\nXMC 3542655 3544373 12\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: This patch may be installed at any time.\nIt has no patch prerequisites, except that MailMan 8 must be installed.\nNOIS: HIN-1202-41276\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan\n or the background filer.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\nTest Site: Hines\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XM*8.0*12 Loaded from Distribution <date/time>\n =========\n Install Questions for XM*8.0*12\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nIf you D ^XMC from the programmer prompt, select '1' to enter MailMan,\nand upon exiting MailMan, press RETURN to exit ^XMC, the routine aborts\nwith an undefined XMABORT. This patch fixes that.\n\n\n
\nMailMan 8.0\n(through patches XU*8.0*216 and DI*22.0*68, respectively).\n\n11. You can now send, forward, or filter-forward messages to H.device\n(Headerless print). It will print the message, without a header, on the\ndevice. As before, sending messages to D.device will print them with\na header.\n\n12. In response to NOIS HWH-0502-41774, if you become a surrogate of a user,\nand try to access a message that the user is not on (but you are), you will\nbe told that you will have to forward the message to the user, in order to\naccess it as the user. You will then be given the opportunity to forward\n\nit, if it's OK to do so. (For example, if the message is closed, you would\nnot be allowed to forward it, if you didn't send it.)\n\n13. In response to NOIS CHY-0597-50209, when using TalkMan to communicate\nwith a site, MailMan will only consider using scripts whose TYPE is TELNET.\n\n14. The pre-init, PRE^XMYPRE, will\n- K ^DOPT("XMC"), to reset the programmer options (D ^XMC).\n- Kill the old "AC" xref definition for NETWORK PRIORITY TRANSMISSION field\n6, in the basket multiple of file 3.7, and change all xrefs\nMailMan 8.0 offers the following improvements over MailMan 7.1:\n^XMB(3.7,.5,2,"AC",1,XMK,XMZ) to ^XMB(3.7,.5,2,XMK,1,"AC",1,XMZ).\n- Delete the following fields from file 4.2999, MESSAGE STATISTICS, because\nthey are not used:\n 7 OUTGOING MESSAGE COUNT\n 8 CHARACTERS REC'D\n 9 INCOMING MESSAGE COUNT\n 10 CHARACTERS SENT \n- Delete the ENTRY ACTION fields for options XMQSHOW, XMSUBEDIT, XMDXPROT.\n\n15. The post-init, POST^XMYPRE, will\n\n- Go through MailMan's security keys and ensure that the 'mutually\nexclusive' keys are correct.\n\n16. Here are DD changes:\n\na. MESSAGE file 3.7\n\n- Change field 2, FORWARDING ADDRESS to fix the bulletin xref. FileMan\nthought that it was firing XM-FWD-ADDRESS-CHECKER, yet it was actually\nfiring XMZFWDBULL. It now fires XM FWD ADDRESS CHANGE, a new bulletin,\n1. MailMan is now DNS aware. It can use the Kernel API MAIL^XLFNSLK\nwhich looks like the old ones, but has a better name.\n\nSTANDARD DATA DICTIONARY #3.7 -- MAILBOX FILE\nSTORED IN ^XMB(3.7,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n3.7,2 FORWARDING ADDRESS 0;2 FREE TEXT\n Remote address to which mail is routed \n INPUT TRANSFORM: D XMFWD^XMVVITA(.X,$G(XMIA)) I $D(X) K:$L(X)>50\nto retrieve IP addresses. It is no longer necessary to manually update the\n !($L(X)<1) X\n LAST EDITED: APR 23, 2002 \n HELP-PROMPT: Enter a forwarding address (name@domain) of up \n to 50 characters. \n DESCRIPTION: This field names an additional address to which\n any messages addressed to you are routed. This\n address must be a remote address or a local\n device. \n \n If you want a local user to see your messages,\nIP addresses in the DOMAIN file, 4.2. The IP address fields will remain in\n make that user a surrogate. \n \n See the LOCAL DELIVERY FLAG. If you do not\n edit this field to 'ON', then mail will only be\n delivered to your FORWARDING ADDRESS and not to\n your Mailbox. \n\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n\n CROSS-REFERENCE: ^^BULLETIN MESSAGE \nfile 4.2, and MailMan will use them. However, if they don't work, MailMan\n 1)= S Y(0)=X,D0=DA X "N DIIND F DIIND=1.001:.00\n 1 Q:$D(^DD(3.7,2,1,1,DIIND))[0 X ^(DIIND)" K X\n MY S XMB="XM FWD ADDRESS CHANGE" D ^XMB:$D(^XMB\n (3.7,"B",XMB)),ENT^XMUT7(DA) K Y,XMB\n 1.001)= S X=Y(0) S Y(1)=$S($D(^XMB(3.7,D0,0)):^\n (0),1:"") S X=$S('$D(^VA(200,+$P(Y(1),U,1),0)):\n "",1:$P(^(0),U,1)) S XMB(1)=X\n 1.002)= S X=Y(0) S Y(1)=$S($D(^XMB(3.7,D0,0)):^\n (0),1:"") S X=$P(Y(1),U,2) S XMB(2)=X\n 2)= Q\nwill use the Kernel API to retrieve a list of valid IP addresses. When\n CREATE PARAMETER #1)= NAME\n CREATE PARAMETER #2)= FORWARDING ADDRESS\n CREATE VALUE)= XM FWD ADDRESS CHANGE\n DELETE VALUE)= NO EFFECT\n This cross reference sends two bulletins. \n \n The first, XM FWD ADDRESS CHANGE, notifies\n responsible individuals (belonging to the mail\n group associated with the bulletin) that a user \n has changed his forwarding address. This is\nMailMan finds one that works, MailMan will replace the non-working IP\n the "official" bulletin of this cross\n reference. \n \n The second, XM FWD ADDRESS CHECK, is sent to\n the user's new forwarding address as test to\n see if the address is valid. If it's not\n valid, the sender (the Postmaster) will receive\n an error message. This bulletin has been\n piggy-backed onto the "official" bulletin. \n FileMan is not aware of this. \n\naddress with the working one. In order to activate DNS awareness, this\n\n CROSS-REFERENCE: 3.7^F \n 1)= S ^XMB(3.7,"F",$E(X,1,30),DA)=""\n 2)= K ^XMB(3.7,"F",$E(X,1,30),DA)\n This cross reference enables the site manager\n to easily find a user who enters a bad\n forwarding address. \n\n- Change field 3.702,6 - NETWORK PRIORITY TRANSMISSION\nto expand the set of codes to add low priority, and to change the "AC" xref\nnew field in the MAILMAN SITE PARAMETERS file 4.3 must be set to 'yes':\nfrom user-level to message-level. (See item 3, above, for more info.)\n\n3.702,6 NETWORK PRIORITY TRANSMISSION? 0;6 SET\n '1' FOR HIGH PRIORITY; \n '0' FOR REGULAR PRIORITY; \n '2' FOR LOW PRIORITY; \n HELP-PROMPT: How should this message be handled during \n transmission? \n DESCRIPTION: This field is used to flag messages that need\n to be transmitted before or after all other\n 4.3,8.22 DNS AWARE Yes or No?\n messages in a queue. \n\n Messages in the queue which are flagged as HIGH\n priority are transmitted before all other\n messages. \n\n Messages in the queue which are flagged as\n REGULAR priority (default) are transmitted\n next. \n\nAlso, routine ^XLFNSLK must exist, and the following field in the\n Messages in the queue which are flagged as LOW\n priority are transmitted after all other\n messages. \n\n Messages with the same priority are transmitted\n in IEN order, which is not necessarily the\n order in which they appear in the transmit\n queue. \n\n Only the POSTMASTER (or surrogate) may change\nKERNEL SYSTEMS PARAMETERS file 8989.3 must be properly filled in with\n the priority of a message in a transmit queue. \n If, during a transmission, MailMan has problems \n with a particular message, MailMan may flag\n that message as LOW priority, so that other\n messages in the queue will transmit, before the\n problem message is attempted again. \n\n Changes to message priorities can be made even\n while a queue is being transmitted. \n\nan IP address:\n FIELD INDEX: AC (#12) REGULAR IR SORTING ONLY\n Short Descr: Transmission Priority Cross Reference\n Description: This xref is used by MailMan during message\n transmission to identify messages which should\n be transmitted first (high priority) or last \n (low priority). Messages with regular priority\n are not xref'd.\n Set Logic: S ^XMB(3.7,DA(2),2,DA(1),1,"AC",$E(X,1,1),DA)=""\n Set Cond: S X=X\n Kill Logic: K ^XMB(3.7,DA(2),2,DA(1),1,"AC",$E(X,1,1),DA)\n 8989.3,51 DNS IP IP address for DNS\n Kill Cond: S X=X\n Whole Kill: K ^XMB(3.7,DA(2),2,DA(1),1,"AC")\n X(1): NETWORK PRIORITY TRANSMISSION? (3.702,6)\n (Subscr 1) (Len 1) (forwards)\n\nb. MAIL GROUP file 3.8, add a trigger to field .01 to populate field 5.1\n\nSTANDARD DATA DICTIONARY #3.8 -- MAIL GROUP FILE\nSTORED IN ^XMB(3.8,\nDATA NAME GLOBAL DATA\n\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n3.8,.01 NAME 0;1 FREE TEXT (Required)\n MAIL GROUP NAME \n INPUT TRANSFORM: S:X?1"G.".E!(X?1"g.".E) X=$E(X,3,99) K:$L(X)>30\n !($L(X)<3)!'(X'?1P.E)!(X'?.ANP) X\n HELP-PROMPT: ANSWER MUST BE 3-30 CHARACTERS IN LENGTH \n DESCRIPTION: The name of a mail group, i.e. a list of\n recipients who can all be addressed at once by\n reference to this name. \n2. For TCP/IP connections, MailMan can now build transmission scripts\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n CROSS-REFERENCE: 3.8^B \n 1)= S ^XMB(3.8,"B",$E(X,1,30),DA)=""\n 2)= K ^XMB(3.8,"B",$E(X,1,30),DA)\n CROSS-REFERENCE: ^^TRIGGER^3.8^5 \n 1)= X ^DD(3.8,.01,1,2,1.3) I X S X=DIV S Y(1)=$\n S($D(^XMB(3.8,D0,3)):^(3),1:"") S X=$P(Y(1),U,1\n ),X=X S DIU=X K Y S X=DIV S X=$G(XMDUZ,DUZ) S D\n IH=$G(^XMB(3.8,DIV(0),3)),DIV=X S $P(^(3),U,1)=\n DIV,DIH=3.8,DIG=5 D ^DICR\non-the-fly. (Transmission scripts exist in the DOMAIN file 4.2, in the\n 1.3)= K DIV S DIV=X,D0=DA,DIV(0)=D0 S Y(0)=X S \n Y(1)=$S($D(^XMB(3.8,D0,3)):^(3),1:"") S X=$S('$\n D(^VA(200,+$P(Y(1),U,1),0)):"",1:$P(^(0),U,1))=\n ""\n 2)= Q\n CREATE CONDITION)= ORGANIZER=""\n CREATE VALUE)= S X=$G(XMDUZ,DUZ)\n DELETE VALUE)= NO EFFECT\n FIELD)= ORGANIZER\n When a user creates a mail group, this trigger\nTest Sites: FORUM, San Francisco, Central Alabama, FO-Albany, FO-Oakland\nTRANSMISSION SCRIPT multiple, in the TEXT field 2.) If the TYPE is "SMTP",\n makes that user the organizer of the group. \n The user is free to change that field. \n\nc. INTER-UCI TRANSFER file 4.281, increase domain name field lengths to \nagree with .01 field in file 4.2. Also increase lengths of B & C xrefs.\n\nSTANDARD DATA DICTIONARY #4.281 -- INTER-UCI TRANSFER FILE\nSTORED IN ^%ZISL(4.281,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n"TCPCHAN", or null, and the TEXT field has no records, and these fields\n---------------------------------------------------------------------------\n4.281,.01 FROM DOMAIN 0;1 FREE TEXT (Required)\n INPUT TRANSFORM: K:$L(X)>64!($L(X)<3)!'(X'?1P.E) X\n HELP-PROMPT: Answer must be 3-64 characters in length\n CROSS-REFERENCE: 4.281^B\n 1)= S ^%ZISL(4.281,"B",$E(X,1,64),DA)=""\n 2)= K ^%ZISL(4.281,"B",$E(X,1,64),DA)\n\n4.281,1 TO DOMAIN 0;2 FREE TEXT\n INPUT TRANSFORM: K:$L(X)>64!($L(X)<3) X\nin the MAILMAN SITE PARAMETERS file 4.3 are filled in:\n HELP-PROMPT: Answer must be 3-64 characters in length\n CROSS-REFERENCE: 4.281^C\n 1)= S ^%ZISL(4.281,"C",$E(X,1,64),DA)=""\n 2)= K ^%ZISL(4.281,"C",$E(X,1,64),DA)\n 3)= XXXX - Do not delete\n This cross-reference is used by the receiving\n UCI to find entries which have been\n 'transmitted' to it from other UCIs.\n\nd. Add fields to MESSAGE STATISTICS file 4.2999.\n 4.3,8.23 TCP/IP COMMUNICATIONS PROTOCOL Points to file 3.4\n\nSTANDARD DATA DICTIONARY #4.2999 -- MESSAGE STATISTICS FILE\nSTORED IN ^XMBS(4.2999,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n4.2999,8 DIRECTION 3;8 SET\n 'S' FOR SENDING; \n 'R' FOR RECEIVING; \n HELP-PROMPT: Are we sending or receiving? \n 4.3,8.24 TCP/IP TRANSMISSION SCRIPT Points to file 4.6\n DESCRIPTION: This field is used to report whether, at any\n given time, we are sending messages to, or\n receiving messages from, the site. \n\n4.2999,48 XMIT IP ADDRESSES TRIED 4;8 FREE TEXT\n INPUT TRANSFORM: K:$L(X)>100!($L(X)<3) X\n HELP-PROMPT: Answer must be 3-100 characters in length.\n DESCRIPTION: This is a list of IP addresses, separated by\n commas, which have already been used in\n attempting to connect with the site.\n...then MailMan creates the script. This one is for FORUM:\n\n We use this list in conjunction with the DNS\n server, which returns a list of valid addresses\n to try. Using both lists, we can come up with\n the next IP address to try.\n\n4.29992,3 XMIT AUDIT IP ADDRESS 0;4 FREE TEXT\n INPUT TRANSFORM: K:$L(X)>20!($L(X)<1) X\n HELP-PROMPT: Answer must be 1-20 characters in length. \n DESCRIPTION: This is the IP address used for this attempt.\n O H=DOMAIN.EXT,P=TCP/IP-MAILMAN\n\ne. Change fields in MESSAGE STATISTICS file 4.2999.\n\nChanged the title and description:\n\n4.2999,.01 NAME 0;1 POINTER TO DOMAIN FILE (#4.2)\n (Required)\n Domain name \n INPUT TRANSFORM: S:$D(X) DINUM=X\n DESCRIPTION: Domain for which network mail transmission\n C TCPCHAN-SOCKET25\n information is collected.\n NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER\n CROSS-REFERENCE: 4.2999^B\n 1)= S ^XMBS(4.2999,"B",$E(X,1,30),DA)=""\n 2)= K ^XMBS(4.2999,"B",$E(X,1,30),DA)\n\nChanged to a pointer and changed the help prompt:\n\n4.2999,2 MESSAGE IN TRANSIT 3;2 POINTER TO MESSAGE FILE (#3.9)\n HELP-PROMPT: Enter the IEN of the message being transmitted.\nwhere:\n DESCRIPTION: This points to the 3.9 (Message) file entry of\n the message being transmitted.\n\nCorrected the spelling of "included":\n\n4.29991,103 MESSAGES RECEIVED 0;3 NUMBER\n\n INPUT TRANSFORM:K:+X'=X!(X>9999999)!(X<0)!(X?.E1"."1N.N) X\n HELP-PROMPT: Type a Number between 0 and 9999999, 0 Decimal\n Digits\n "DOMAIN.EXT" is taken from the DOMAIN name.\n DESCRIPTION: Messages received are included here even if\n they are received only to be forwarded on to\n another site. Also included are responses and\n messages received previously (as long as they\n have additional recipients).\n\nIncreased the length of the following fields:\n\n4.29991,104 CHARACTERS SENT 0;4 NUMBER\n INPUT TRANSFORM:K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1.N) X\n\n "TCP/IP-MAILMAN" is the protocol pointed to by field 8.23\n HELP-PROMPT: Type a number between 0 and 999999999, 0\n Decimal Digits\n DESCRIPTION: This is a count of the number of characters in\n the messages sent.\n\n4.29991,105 CHARACTERS RECEIVED 0;5 NUMBER\n INPUT TRANSFORM:K:+X'=X!(X>999999999)!(X<0)!(X?.E1"."1.N) X\n HELP-PROMPT: Type a number between 0 and 999999999, 0\n Decimal Digits\n DESCRIPTION: This is a count of the number of characters in\n "TCPCHAN-SOCKET25" is the script pointed to by field 8.24.\n the messages received.\n\n4.29991,106 LINES SENT 0;6 NUMBER\n INPUT TRANSFORM:K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1.N) X\n HELP-PROMPT: Type a number between 0 and 99999999, 0 Decimal\n Digits\n DESCRIPTION: This is a count of the number of lines in the\n message sent.\n\n4.29991,107 LINES RECEIVED 0;7 NUMBER\n\n INPUT TRANSFORM:K:+X'=X!(X>99999999)!(X<0)!(X?.E1"."1.N) X\n HELP-PROMPT: Type a number between 0 and 99999999, 0 Decimal\n Digits\n DESCRIPTION: This is a count of the number of lines in the\n messages received.\n\nf. Add fields to MAILMAN SITE PARAMETERS file 4.3\n(See items 1 and 2, above, for more info.)\n\nSTANDARD DATA DICTIONARY #4.3 -- MAILMAN SITE PARAMETERS FILE\n3. Messages in transmit queues can now be designated as low priority, as\nSTORED IN ^XMB(1,\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n4.3,8.22 DNS AWARE NETWORK;2 SET\n '0' FOR NO;\n '1' FOR YES;\n HELP-PROMPT: Should MailMan use DNS to look up IP addresses?\n DESCRIPTION: In order for MailMan to be DNS aware, the site\n must have installed the requisite Kernel\nwell as high priority. If a message gets stuck in a transmit queue and is\n patches for DNS.\n\n If you answer 'no', MailMan will use the IP\n addresses in the domain scripts.\n\n If you answer 'yes', MailMan will use the IP\n addresses in the domain scripts, but if they\n fail, or don't exist, MailMan will use DNS to\n ascertain other IP addresses to try. MailMan\n will replace failed script IP address with the\nholding up the rest of the queue for whatever reason, MailMan will make\n successful DNS IP address.\n\n4.3,8.23 TCP/IP COMMUNICATIONS PROTOCOL NETWORK;3\n POINTER TO COMMUNICATIONS PROTOCOL FILE (#3.4)\n (Required)\n HELP-PROMPT: Which protocol shall be used for TCP/IP?\n DESCRIPTION: For TCP/IP connections, the scripts (the TEXT\n field, 2, in the TRANSMISSION SCRIPT multiple,\n 4, of the DOMAIN file, 4.2) are ignored.\n\nthat message a low priority message, so that all the other messages are\n We identify the TCP/IP transmission scripts in\n file 4.2 by the TYPE field, 1.2, within the\n TRANSMISSION SCRIPT multiple. Those whose TYPE\n is 'SMTP', 'TCPCHAN', or null are considered\n TCP/IP transmission scripts.\n\n We can ignore the scripts, because they are\n standard.\n\n Here's an example of one for FORUM:\ntransmitted ahead of it. The postmaster can also make these priority\n\n O H=DOMAIN.EXT,P=TCP/IP-MAILMAN\n C TCPCHAN-SOCKET25-VXD\n\n In this script, the TCP/IP-MAILMAN refers to\n the communications protocol to use. This field\n should point to the communications protocol in\n file 3.4 that should be used for TCP/IP\n connections.\n\nchanges. In the message queue, high-priority messages are now marked with\n4.3,8.24 TCP/IP TRANSMISSION SCRIPT NETWORK;4\n POINTER TO TRANSMISSION SCRIPT FILE (#4.6)\n (Required)\n HELP-PROMPT: Which script shall be used for TCP/IP?\n DESCRIPTION: For TCP/IP connections, the scripts (the TEXT\n field, 2, in the TRANSMISSION SCRIPT multiple,\n 4, of the DOMAIN file, 4.2) are ignored.\n\n We identify the TCP/IP transmission scripts in\n file 4.2 by the TYPE field, 1.2, within the\n'^', instead of '$'. Low priority messages are marked with 'v'.\n TRANSMISSION SCRIPT multiple. Those whose TYPE\n is 'SMTP', 'TCPCHAN', or null are considered\n TCP/IP transmission scripts.\n\n We can ignore the scripts, because they are\n standard.\n\n Here's an example of one for FORUM:\n\n O H=DOMAIN.EXT,P=TCP/IP-MAILMAN\nMailMan 8.0 is a maintenance release. It includes the complete MailMan\n\n C TCPCHAN-SOCKET25-VXD\n\n In this script, the TCPCHAN-SOCKET25-VXD refers\n to the transmission script to use. This field\n should point to the transmission script in file\n 4.6 that should be used for TCP/IP connections.\n\nNOTE: This release should be installed after hours, when user activity is at\na minimum. Your site should be patched through MailMan patch XM*7.1*198.\nIt is also expected that Kernel 8.0 and FileMan 22.0 are installed and are\nThe postmaster can now change the transmit priority at the message level\nreasonably up-to-date (through patches XU*8.0*216 and DI*22.0*68,\nrespectively). It is up to you to check this. KIDS will not.\nInstallation will take approximately 5 minutes.\n============================================================================ \n\nROUTINES:\nThe second line of the routines now look like:\n ;;8.0;MailMan;;Jun 28, 2002\n \nRoutine list and checksums can be found in routines XMNTEG and XMNTEG0.\n(at the 'Message action: Ignore//' prompt). As at the basket level, the\n\n===========================================================================\n \nINSTALLATION:\nNOTES:\na. This release should be installed after hours, when user activity is at a\nminimum. Your site should be patched through MailMan patch XM*7.1*198. It\nis also expected that Kernel 8.0 and FileMan 22.0 are installed and are\nreasonably up-to-date (through patches XU*8.0*216 and DI*22.0*68,\nrespectively). It is up to you to check this. KIDS will not.\ncommand to use is 'X'. (In a user basket, the 'X' at the message level is\nb. Installation will take approximately 5 minutes.\nc. DSM sites running SlotMaster may see routine mapping problems with ZSLOT\nusers, even after disabling mapping. Therefore, such sites should consider\nthe following steps:\n- Shutdown ZSLOT on all nodes.\n- Disable all mapped XM routines.\n- Install this release.\n- Enter manual edits.\n- Rebuild mapped routine sets.\n- Shutdown/restart all DSM configurations.\na command to unload a PackMan message or KIDS build. In a remote transmit\nAn alternative to the above steps is to disable all mapped XM routines about\na week before you load this release. That way you wouldn't need to shutdown\nZSLOT or shutdown/restart DSM configurations.\n\n1. Users may NOT be on the system during installation of this release.\n2. DSM Sites: disable mapping for all MailMan routines.\n3. Retrieve the MailMan 8.0 KIDS build (XM8.KID) via FTP from one of the\n Anonymous Directories by following the instructions in the MailMan 8.0\n Release Message.\n4. On the KIDS:Installation menu, use the following option to load the\nqueue, the 'X' changes the transmit priority. The difference is the\n build into a Transport Global on your system:\n Load a Distribution\n Enter a Host File: E:\\INETPUB\\FTPROOT\\XM8.KID or USR$:[USER.NAME]XM8.KID\n ========================== =======================\n (How you answer the above prompt depends on the system you're on and where\n you placed the build you retrieved in the previous step. The answers\n shown are examples only.)\n5. Users should not be on the system.\n Place TaskMan in a WAIT state.\n You may also wish to shut down HL7 filers/LLP's and other background\ncontext, and writers of MailMan front-ends should take note!)\n tasks which may attempt to create new messages.\n6. On the Manage MailMan:Local Delivery Management menu, use the following\n option to stop the background filer:\n STOP background filer\nAre you sure you want Background Filers to stop delivering mail? No// YES\n ===\n<< Background Filers will stop soon. >>\n7. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: MAILMAN 8.0 Loaded from Distribution <date/time>\n ===========\nInstall Questions for MAILMAN 8.0\n\nIncoming Files:\n\n4. MailMan date/times are now in a standard format, produced by the Kernel\n 3.4 COMMUNICATIONS PROTOCOL\nNote: You already have the 'COMMUNICATIONS PROTOCOL' File.\n\n 3.6 BULLETIN\nNote: You already have the 'BULLETIN' File.\n\n 3.7 MAILBOX\nNote: You already have the 'MAILBOX' File.\n\n 3.73 MESSAGES TO BE NEW AT A LATER DATE\nAPI: $$FMTE^XLFDT(datetime,"2Z"). Previously, 3020803.153204 would be\nNote: You already have the 'MESSAGES TO BE NEW AT A LATER DATE' File.\n\n 3.8 MAIL GROUP\nNote: You already have the 'MAIL GROUP' File.\n\n 3.816 DISTRIBUTION LIST\nNote: You already have the 'DISTRIBUTION LIST' File.\n\n 3.9 MESSAGE\nNote: You already have the 'MESSAGE' File.\nsuite of data dictionaries, but it does not populate the files. This\ndisplayed as '03 Aug 02 15:32'. Now, it is displayed as '08/03/02@15:32'.\n\n 4.2 DOMAIN\nNote: You already have the 'DOMAIN' File.\n\n 4.281 INTER-UCI TRANSFER\nNote: You already have the 'INTER-UCI TRANSFER' File.\n\n 4.2996 INTERNET SUFFIX\nNote: You already have the 'INTERNET SUFFIX' File.\n\nThis change is also carried through to all MailMan APIs which return\n 4.2997 REMOTE USER DIRECTORY\nNote: You already have the 'REMOTE USER DIRECTORY' File.\n\n 4.2998 MESSAGE DELIVERY STATS\nNote: You already have the 'MESSAGE DELIVERY STATS' File.\n\n 4.2999 MESSAGE STATISTICS\nNote: You already have the 'MESSAGE STATISTICS' File.\n\n 4.3 MAILMAN SITE PARAMETERS\ndate/time in MailMan format. Users of such APIs should take note!\nNote: You already have the 'MAILMAN SITE PARAMETERS' File.\n\n 4.4 MAILMAN TIME ZONE\nNote: You already have the 'MAILMAN TIME ZONE' File.\n\n 4.501 NETWORK SENDERS REJECTED\nNote: You already have the 'NETWORK SENDERS REJECTED' File.\n\n 4.6 TRANSMISSION SCRIPT\nNote: You already have the 'TRANSMISSION SCRIPT' File.\n\n\nIncoming Mail Groups:\n\nEnter the Coordinator for Mail Group 'XM SUPER SEARCH': <Your site's ISO>\n =================\nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\nWant KIDS to INHIBIT LOGONs during the install? YES// YES\n ===\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n5. MailMan remote message IDs now include the message date, to ensure that\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <Don't queue this>\n ------------------\n8. Remove TaskMan from WAIT State. If you shut down HL7 filers/LLPs or\n any other background tasks, you may restart them.\n9. Start the background filer.\nif you are told that a message is a duplicate of a previously received\n On the Manage MailMan:Local Delivery Management menu, use the following\n option to start the background filer:\n START background filer\n << Background Filers will start soon. >>\n10. Ensure that the new fields in file 4.3, MAILMAN SITE PARAMETERS, are\ncorrectly entered:\n 8.22 DNS AWARE Yes or No?\n 8.23 TCP/IP COMMUNICATIONS PROTOCOL Points to file 3.4\n 8.24 TCP/IP TRANSMISSION SCRIPT Points to file 4.6\n11. DSM Sites: If your site maps routines, then rebuild your map set.\nmessage, it really is. Sites will no longer have problems sending messages\n Many routines have become obsolete and should be removed from the map\n set. Here is a new recommended list of routines to map, should your\n site choose to map routines:\n Minimum Additional\n ------- ----------\n XM XMC1A,XMC1B\n XMC1 XMK*\n XMJ* XML\n XMR XMR1,XMR2,XMR3*\n XMS XMS1,XMS2,XMS3\nfrom a production account to a test account which was created by "mirroring"\n XMT*\n XMVVITAE\n XMXADDR*\n XMXSEC*\n XMXUTIL*\n===========================================================================\nthe production account. The remote message ID is now the message number\nfollowing by a period, followed by the 7-digit FileMan message creation\nversion expects that a site already has MailMan 7.1 installed and running,\ndate. Before, a remote message ID might be 34561234@DOMAIN.EXT. Now it\nwould be 34561234.3020803@DOMAIN.EXT.\n\n6. The ^XMC*, ^XMR*, ^XMS* suite of routines, which are responsible for\nscheduling, transmitting to, and receiving messages from remote sites, have\nbeen completely overhauled to make them easier to understand and easier to\nmaintain.\n\n7. MailMan will no longer display user names by taking them directly from\nthe .01 field of the NEW PERSON file, 200. The API, $$NAMEFMT^XLFNAME,\nand that it is patched through XM*7.1*198. It is also expected that\nsupplied as part of the Name Standardization project, is used, instead.\nThus, the names of people whose last names, for instance, contain periods,\napostrophes, or spaces, are properly displayed (ST. IVES, O'MALLEY, and\nVAN DYKE), instead of improperly (STIVES, OMALLEY, and VANDYKE).\n\n8. In response to NOIS FAV-0202-71819, messages with responses may no longer\nbe forwarded to broadcast to all users. Such messages may have important\ninformation in the responses, and as we all know, responses are not auto-\nforwarded to remote sites for users with auto-forward addresses. Users who\nattempt to broadcast messages with responses will be encouraged to copy the\nKernel 8.0 and FileMan 22.0 are installed and are reasonably up-to-date\nmessage and its responses into a new message, which can be broadcast.\n\n9. Incoming PackMan and KIDS messages are no longer subject to the\nrestriction NETWORK - MAX LINES RECEIVE (field 8.31, file 4.3). Other kinds\nof messages continue to be subject to that restriction.\n\n10. If a task transmitting messages to another site fails and has to be\nrequeued, it really is requeued. Previously, that wasn't true. Previously,\nthe failing task queued up a new task to take its place, and then the\nfailing task stopped.\n\n\nMailMan is a communications package that can be used by software\nand hardware. In its' user mode it operates in a kind of mode that\nis very nice for asynchronous teleconferencing. It has many functions\nthat can be used by software, including the ability to address messages\nto software (servers) and extract data from message fields.\n\n
\nThis build contains the routines for the PCE Health Summary components.\nThe routines, excluding GMTSP8, were originally distributed with Health\nSummary v2.7, but were modified as a result of alpha/beta and useability\ntesting\n\n
\nPatch GMTS*2.7*17. Please see the patch description on the \nnational patch module.\n\n
\nThis patch is in support of the Mental Health PCL-5 instrument patch. It \n \nPatch Components:\n-----------------\n \nFiles & Fields Associated: N/A\n \nForms Associated: N/A\n \nMail Groups Associated: N/A\n \nwill modify the list of mental health instruments presented as selection \nOptions Associated: N/A\n \nProtocols Associated: N/A\n \nSecurity Keys Associated: N/A\n \nTemplates Associated: N/A\n \nNew Service Requests (NSRs):\n----------------------------\nitems in health summary when using the ad hoc health summary option in \nN/A\n \nPatient Safety Issues (PSIs):\n-----------------------------\nPSPO 2497: Mental health instruments that use a complex scoring algorithm \ndisplay an incorrect score when used in Health Summary and Clinical \nReminders. \n \nRemedy Ticket(s) & Overview:\n----------------------------\nCPRS. The patch will prevent instruments that are inoperative or not \nN/A\n \nTest Sites:\n----------\nTBD\n \n \nDocumentation Retrieval Instructions:\n------------------------------------- \nDocumentation can also be found on the VA Software Documentation Library \nscored correctly from being selected.\nat:\nhttp://www4.domain.ext/vdl/\n \n \nPatch Installation:\n------------------\n \n Instructions for installation of the software are included in the \n Mental Health PCL-5 patch YS*5.01*119.\n \n \nPost-Installation Instructions:\n-------------------------------\nN/A\nPlease refer to the information contained in the Mental Health patch for \ninstallation instructions.\n \n\n
\n Patch GMTS*2.7*121 addresses the following issue:\n \n 1. Ad Hoc Health Summary Menu [GMTS HS ADHOC] is providing inaccurate\n results on the occurrence limit.\n\n
\nClinical Reminders component output standardization.\n\n\n
\nThe Office of Spinal Cord Injury/Disorder (SCI/D) is requesting to \ndecommission the VistA Spinal Cord Dysfunction (SCD) application and \ndata. The VistA SCD application and stored data will be removed from \nVA's inventory of applications. Therefore, all Health Summary \nreferences to the SCD application will be removed.\n\n
\nPatch GMTS*2.7*19. Please see the national patch module for\na complete description of this patch.\n\n
\nThe purpose of this build is to implement two new Health Summary \ncomponents. Please see the patch description for a full description.\n\n
\nThis patch will resolve the following issues in the Health summary \npackage:\n \n1. INC3453605 - If a user attempts to use the Health Summary component \nMed Reconciliation (MRR1) on a patient with a quick order with the \nquantity missing the error <SUBSCRIPT>OPTDISP+11^GMTSPST1 occurs\n\n
\nThe Health Summary report Essential Med List for Review does not exit \nproperly when a user viewing the report enters a "^" to exit the report.\n\n
\nThe purpose of this patch is to support patch SOW*3.0*65 (which will \ncompletely decommission the Social Work (SOW) package from VistA) and \nremove all Social Work GMTS code and components.\n\n
\nPlease see patch description on Forum for detailed instructions.\n\n
\nTHIS PATCH ADDRESSES THE INCORRECT CALL TO THE API OEL^PSOORRL (IA 2400).\n\n
\nThis patch will install new national components that are released with \nCPRS version 31 (OR*3*377). Refer to the patch description for the list \nof components.\n\n
\nCORRECT DOD RX'S NOT DISPLAYING ON EMLR REPORT\n\n
\nThis patch will install new national components that are released with \nCPRS version 31MA (OR*3*519). Refer to the patch description for the list \nof components.\n\n
\nBackup of GMTS*2.7*136 on May 04, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch contains changes so that the Clinical Reminder and Clinical\nMaintenance components will print a trailing "(E)" for the last date of\nreminders satisified by an historical enocounter.\n\n
\nThe patch addresses one (1) issue:\n \n1. In CPRS, selecting the Reports tab> Clinical Reports> Laboratory> \n Blood Transfusion Report produces a report that lists units per\n date as one (1) less than they should be when the number of units\n is greater than one (1).\n\n
\nBackup of PCE STANDARDIZATION 1.0, PX*1.0*211, PXRM*2.0*42, GMT\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch supports PCE standardization.\n \nFor detailed information and installation instructions, please see the PCE\nStandardization 1.0 Installation Guide.\n\n\n\nTo take full advantage of the PCE standardization work, changes to VistA\napplications that use PCE data are required. These applications include\nClinical Reminders, Health Summary, Problem List, and Order Entry/Results\nReporting. To make it easier for sites, the builds for PCE (PX*1.0*211),\nClinical Reminders (PXRM*2.0*42), Health Summary (GMTS*2.7*122), Problem List\n(GMPL*2.0*53), and Order Entry/Results Reporting (OR*3.0*501) are being\ndistributed in a multi-package build named PCE STANDARDIZATION 1.0.\n\n
\nThe patch addresses one (1) issue:\n \n1. In CPRS on the Reports tab when selecting Surgery Clinical reports,\n Surgery case statuses may display ABORTED when they are actually\n COMPLETED. When this occurs, the VistA Surgery package correctly\n displays case status.\n\n
\nThis patch distributes a new health summary component for sexual \norientation. Please see the patch description for a full explanation.\n\n
\nPlease refer to the patch description for contents and a detailed \ndescription.\n\n
\nThis patch addresses the following issue(s):\n \nUnverified Laboratory Microbiology results are displayed in the \nMicrobiology Ad Hoc Health Summary Report.\n \nSee patch description on FORUM for specific details.\n\n
\nRefer to the patch description for an explanation of the changes included \nin this patch.\n\n
\nThis patch addresses the following issues:\n \n2. INC18892605: Essential Med List, Non-VA medications instructions print\nthe old directions first and the new directions second.\n \n1. With the introduction of PARK functionality (CPRS 32B release), and\nonce the Park functionality is enabled, the Health Summary Type of\nEssential Med List for Review needs to be able to display "Active/Parked"\nas a status. These changes in Health Summary routines, along with changes\nin patch PSO*7.0*712, will allow the Essential Med List for Review to be\nable to display "Active/Parked" when the prescription is in a Parked \nstatus.\n\n
\nThis patch will address the following issue:\n \nComplex Non-VA med orders do not display correctly with Health Summary\nComponent MRT2.\n\n
\nHealth Summary patch GMTS*2.7*23. This patch adds a new Health Summary\ncomponent for Clinical Reminders. The name of this component is CLINICAL\nREMINDERS SUMMARY, the abbreviation is CRS.\n\n
\nThis is health summary patch GMTS*2.7*18. Please\nsee the national patch module for a complete description.\n\n
\nThis patch correct problem with page lengths longer than the\nHFS device they are sent to. See the GMTS*2.7*21 patch description\non the National Patch Modual.\n\n
\nThis is Health Summary (GMTS) patch 24. Please see the national patch\nmodule for a complete description of the modifications included in this\npatch.\n\n
\nPatch 27 GMTS*2.7*27, Y2K patch. See the National Patch Module for a\ncomplete description of this patch.\n\n
\nThis is patch GMTS*2.7*20 for health summary. Please see the \nNational Patch Module for a complete description of this patch.\n\n
\nHealth Summary patch to update the Current Orders, IV Pharmacy, Outpatient\nPharmacy, and Unit Dose Pharmacy components.\n \nRefer to description within the Patch Module on Forum Patch GMTS*2.7*15.\n\n
\nThis patch contains 3 routines that must be installed in conjunction with\nRoutine Component Checksum\n------- -------- --------\nGMTSLRAE Surgical Pathology (SP) 11034834\nGMTSLREE Electron Microscopy (EM) 6062333\nGMTSLRPE Cytopathology (CY) 6384929\n \n \nInstallation: Users may remain on the system during installation of this\npatch; however, we recommend installing it during non-peak hours to\nminimize disruption to the users.\npatch, LAB*5.2*72, which is changing how the accession numbers are stored.\n \nWith patch LAB*5.2*72, the accession number along with the accession area\nand year will be stored in the accession field. The following routines\nhave been changed to accommodate the printing of the Anatomic Path\nAccession numbers as a result of LR*5.2*72.\n \n \n\n
\nPatch GMTS*2.7*25 fixes various components in the health summary\npackage. For a complete description of the changes see the\nNATIONAL PATCH MODULE.\n\n
\nThis patch will add three new SURGERY components and will modify\nthe output to two other SURGERY components. Please see the national\npatch module for a complete description of the changes in patch\nGMTS*2.7*11.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*28.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*30.\n\n
\nImaging Health Summary Component\n\nThe full description of this patch may be found on the National Patch Module \nunder GMTS*2.7*26.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*32.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*31.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*33.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*36.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*35.\n\n
\nThe patch corrects problems reported in the following NOIS:\n \n GAI-0996-30232 2ND LEVEL PROCEDURE CODES (Surgery Components)\n TOP-0896-40519 using HS from Third Party Joint (Lab Orders)\n DAN-0596-41443 Other Procedures not displaying on Brief\n PAL-1096-61259 Occurence limit for surg comp\n WIC-1096-42206 Error when running health summary type\n\n
\nPatch 34 GMTS*2.7*34, change format of Clinical Reminder output. See the\nNational Patch Module for a complete description of this patch.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*37.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*40.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*42.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*44.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*45.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*43.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*29.\n\n
\nThe description of this patch may be found on the National Patch Module \nunder GMTS*2.7*46.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*48.\n\n
\nFixes to HS Utilities, MAX String error\n \nNOIS: POR-0995-51855\n MAC-1195-61525\n BRX-0596-1045\n HOT-0396-41244\n BOS-1096-12910\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*47.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*50.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*49.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*51.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*53.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*54.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*52.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*55.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*56.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*59.\n\n
\nSee Patch Module for GMTS*2.7*13.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*61.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*58.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*60.\n\n
\nThe description for this patch may be found in the National Patch Module \nunder GMTS*2.7*68.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*62.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in patch GMTS*2.7*65.\n\n
\nThe description of this build is found in the National Patch Module under \npatch GMTS*2.7*57.\n\n
\nThis patch addresses issues noted in NOIS:\n \nPAL-1096-60251\nSUX-0996-41769\nISL-1196-50805\nE3R 9149\nE3R 9347\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nSee the National Patch module for information for this patch.\n\n
\nRoutines which have been added/modified to update the Oncology Health \nSummary, to reflect changes to the FORDS (Facility Oncology Registry Data \nStandards) and addition of AJCC (American Joint Committee on Cancer) \nCollaborative Staging.\n\n
\nCorrect the Branch of Service line in the demographic Health Summary \ndisplay. The last 1- 4 characters are dropped.\n\n
\nUpdates the subroutine, invoked by the DD screen for the SELECTION ITEM \nsub-field of the HEALTH SUMMARY TYPE (#142) file, for use in the \nCreate/Modify Health Summary Type option, so that the screen's pattern \nmatch will allow selection of entries which have SYNONYM (field #.09 in\nthe HEALTH FACTORS (#9999999.64) file) that is of the pattern GEC_n_XXXX.\n\n
\nFixes algorithm used to process date field values for range of entries to \ndisplay in Health Summary component GLOBAL ASSESSMENT FUNCTIONING.\nProblem occurred only when user interaction was on the last day of month.\n\n
\n \nHealth summary needs to use a new Lab API to collect the correct data for\ntest results from the Lab package.\n\n
\nThis patch adds a new Vitals API call to several Vital Signs Health\nSummary Components. It also adds a new Outpatient Pharmacy API call to \nan Outpatient Pharmacy Health Summary Component.\n\n
\nThis patch addresses the issues of a non-numeric modifier not \ndisplaying.\n\n
\nThis patch in conjunction with patch PXRM*2*4 restores the display\nof the Clinical Reminders disclaimer for the Clinical Reminders\nMaintenace, Brief, and Due Health Summary components.\n\n
\nUpdated Rad/Nuc Med health summary\n\n
\nThe description of this patch may be found in the National Patch Module\nunder GMTS*2.7*81.\n\n
\nNational Skin Risk Assessment HS Types and HS Objects\n\n
\nHealth Summary and OE/RR Report display of Radiology's new 'Reason for \nStudy' field (field 1.1 in ^RAO(75.1)). The ORDV03 routine and OE/RR \nReports file #101.24, associated with this patch, are included in \nOR*3.0*243. GMTS*2.7*84 is dependent upon OR*3.0*243, not visa versa.\n \nRefer to the National Patch Module for complete details of the \nenhancements included in this patch.\n\n
\nThis patch will correct multiple problems in the Health Summary package.\n\n
\nIf a Mental Health instrument is administered multiple times for the same \nvisit through CPRS via Progress Notes and Clinical Reminders, all the \ntests do not display in the MHAL and MHAS Health Summary components.\n\n
\nThis patch installs several routines to support the Progress Notes and\nDischarge Summary components of Health Summary, which are compatible with\nand rely upon TIU.\n \nNOTE: This patch may only be installed in an account where TIU exists.\n\n
\nPatches PSO*7*316 and GMTS*2.7*92 correct issues reported with the \nProblem:\n--------\nThe report was hard-coded to display a patient's last four digits of the \nSSN in the body of the report.\n \nResolution:\n-----------\nRemoved the programming that displayed the last four digits of patient \nSSN. Additionally, the release of health summary patch GMTS*2.7*85 now\npermits the removal of the patient SSN from the health summary overall\nTool #2: Medication Worksheet. The Health Summary patch GMTS*2.7*92\nheader. The change in this patch now permits the worksheet to be\nprinted with no SSN references remaining.\n \n2. Wrong pharmacy division name printing on the report header.\n \nProblem:\n--------\nAt integrated sites, the name of the primary facility would print on the \nreport even when generated from the legacy facility.\n \nwill require patch PSO*7*316 and will create a national entry in the\nResolution:\n-----------\nThe internal programming that selects the name of the pharmacy\ndivision shown at the top of the worksheet and the pharmacy phone\nnumber associated with it has been revised. \n \n3. Medication Worksheet does not distinguish ACTIVE and HOLD status \nprescriptions.\n \nProblem:\nHEALTH SUMMARY COMPONENT file (#142.1) for Tool #2: Medication Worksheet.\n--------\nIn the initial release of Medication Reconciliation software with \nPSO*7*294, one of the known issues was that a prescription with status of \nHOLD was not clearly identified as such in the Medication Worksheet.\n \nResolution:\n-----------\nA status indicator is added for prescriptions with status of HOLD, \nsimilar to the existing indicator for PENDING prescriptions in that \nreport.\n \n \n4. The initial release of Medication Reconciliation tools with patch \nPSO*7*294 required manual creation of Health Summary components.\n \nProblem:\n--------\nThere is no guarantee that all VA facilities set up the components \nexactly as indicated in the Medication Reconciliation Implementation \nGuide.\n \n \nResolution:\n-----------\nThis patch introduces the following file entries with nationally \nstandardized internal entry numbers (IENs).\n \n HEALTH SUMMARY COMPONENT file (#142.1)\n ======================================\n Entry #252 - Medication Worksheet (Tool #2)\n \n HEALTH SUMMARY TYPE file (#141)\n1. Current standards for patient privacy and confidentiality were not \n ===============================\n The above-listed Health Summary Component (IEN #252) will be added\n to the existing GMTS HS ADHOC OPTION Health Summary type\n \n VAQ - DATA SEGMENT file (#394.71)\n =================================\n This file contains an entry corresponding to the above-listed\n Health Summary Component (IEN #252) that will be listed as\n Medication Worksheet (tool #2). \nbeing met within the report.\n \n\n
\nCurrently, the NAME field (.01) of the HEALTH SUMMARY OBJECTS file \nstore the full 60 characters.\n(#142.5) had a 'B' cross-reference that only stored the first 30 \ncharacters of the name. When attempting to install a TIU/HS Object in \nClinical Reminder Exchange, a FileMan error: "The update failed, \nUPDATE^DIE returned the following error message" would occur when the \nreceiving site has multiple Health Summary Object entries that are not \nunique until after the 30 character length.\n \nThis patch corrects this problem by modifying the 'B' cross-reference to \n\n
\nIn the Medication Worksheet report in CPRS, the signature lines\nof a prescription carry over to subsequent prescriptions\n\n
\nThis patch will resolve the following Remedy tickets:\n \nHD70142 - TIU-HS Object (SII) not pulling column headers\nHD231399 - Health Summary changes to coincide with LR*5.2*356\nHD230879 - Mental Health Components\nHD336184 - MENU OPTION GMTS HS BY LOC wasting many sheets\n\n
\nThe Mental Health Package is removing file #90 as part of a cleanup \nproject. This patch will permanently deactivate the MENTAL HEALTH \nPHYSICAL EXAM health summary component, rebuild the Health Summary Ad Hoc \nReport, and create a report of Health Summary Types and Objects that used \nthe MENTAL HEALTH PHYSICAL EXAM component.\n\n
\n1. As a part of the Lab Re-engineering project, displays are being\n2. In some cases, the status of a test displays as 'COMPLETED' on the \nComputerized Patient Record System (CPRS) Reports Tab and Lab Tab \ndisplays, rather than the appropriate status of 'CANCELED'. This patch \ncorrects this problem.\n \n3. In support of New Service Request 20070438, a change is required in \nthe Health Summary package. This patch makes this change to the Lab \nDisplay Status. The change will be dormant until CPRS v30 is installed.\nmodified to show the Cerner COTS (Commercial Off-The-Shelf) accession\nnumber for those orders that are being performed on Cerner.\n \nOne of these displays is controlled by the Health Summary v2.7 package. \nThe purpose of this patch is to modify the display on the Reports Tab - \nClinical Reports - Laboratory - Lab Orders to show the COTS accession \nnumber if it is available.\n \n\n
\nGMTS*2.7*16. See national patch module for a description of the\nchanges incorporated in this patch.\n\n
\nA subscript error occurs when editing an AD HOC report.\nThe descriptions of two heath summary components contain spelling errors.\nCPRS is not displaying the correct name for nationally released health \nsummary reports\n\n
\nHigh Risk MH Phase II\nUpdates the MH HIGH RISK PRF HX Health Summary Component to display Cat 1 \nand 2 PRF for suicide risk. Component description is also updated.\n\n
\nThe description of this patch may be found in the National Patch Module \nunder GMTS*2.7*86.\n\n
\nDistributes ONE new HEALTH SUMMARY COMPONENT and TWO new HEALTH SUMMARY \nTYPEs, one of which will be a REMOTE type.\nComponent: CAT 1 PRF STATUS (IEN=257)\n Types: VA-CAT 1 PRF STATUS\n REMOTE CAT 1 PRF STATUS (IEN=500021)\n\n
\nThis build will remediate certain GMTS component routines to comply with \nthe expanded fields added for the ICD-10 PTF Project (DG*5.3*884). See \nNPM entry for details.\n\n
\nTools to build and display health summaries. The health summary pulls\ninformation from ancillary packages and presents it in an integrated\nfashion.\n\n
\nThis patch is being released by Capacity Management (CM) in anticiptaion\nThe Capacity Management (CM) development team is removing obsolete\nreferences to the Resource Usage Monitor (RUM) code. CM has deemed that\nthese references are no longer necessary in order to monitor system\nresource consumption. The system workload data that was gleaned from the\nexisting code in these routines will be located within Kernel's menu\nmanager routines.\nof the national release of the Resource Usage Monitor (RUM) Version 1.0\nsoftware package.\n \nThis patch will not affect the current versions of the RUM software that\nare running at the sites. Therefore, all DSM, MSM and OpenM-NT sites are\ninstructed to install this patch. Test sites which had a pre-release of\nthe RUM software should also install this patch.\n \n\n
\nFix select large number of items from list.\nINC26441621\n\n
\n \n \n This patch contains 2 routines.\n \n Checksums were calculated by CHECK^XTSUMBLD\n \nRoutine Before After Patch List\n \nVALM 8568102 8970241 **1,3**\nVALM1 5659194 6964336 **3**\n \n List Manager Print Problems\n============================================================\n \nInstallation Instructions:\n \n1. Users are allowed on the system, and this patch may be queued.\n A "clobber" error may result if users are in these routines.\n \n2. These routines are usually mapped, so you might have to\n disable mapping on those machines that allow mapping.\n \n \n3. Use the "Install/Check Message" option on the PackMan menu to \n load the package.\n \n4. On the KIDS menu use the following options:\n \n Veryify Checksums in Transport Global\n Print Transport Global (Optional)\n Compare Trasport Global to Current System\n Backup Transport Global\n Install VALM*1.0*3\n This patch fixes a couple of problems reported by the CPRS Team.\n \n5. Reload mapped set if appropriate. \nWhen printing the list or printing the screen an extra page feed would\ncause a blank page before printing began. Also, when the list item is\nlonger than the device's column width in characters, data could be lost or\nhard to read. The software now eliminates the page feed and warns the user\nthat the list item may be too long to print properly.\n\n
\nPatch VALM*1.0*4\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires MailMan patch XM*7.1*50. \n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\n \n Before After\n\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nVALM4 6209662 6275971 4\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOIS: HUN-1198-20777\nNOTE: Users should not be on the system during installation of this patch.\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires MailMan patch XM*7.1*50. \n1. Users should NOT be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan.\nTest Site: Huntington, WV\n Users should NOT be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VALM*1.0*4 Loaded from Distribution <date/time>\n ==========\nIf the text contains control characters, it can mess up the printing and\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\ncause List Manager to fail to print some lines of text. This patch\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nchecks text for control characters and strips any off before printing.\n\nNOTE: Users should not be on the system during installation of this patch.\n\n
\nPatch VALM*1.0*5\nqueued) to a device. Although patch VALM*1.0*3 was subsequently marked\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\n"entered in error", many sites did not back it out, because it also contained\nsome desired new features. Patch VALM*1.0*3 remains "entered in error".\n\nPatch VALM*1.0*5 replaces patch VALM*1.0*3. It corrects the errors and\nretains the desired features introduced in patch VALM*1.0*3.\nWhen printing a list (PL) or printing a screen (PS):\n - Do not eject an extra blank page before starting the print.\n - If the list item width is greater than the device width, print a warning\n message.\n\n\nNOTE: Users should not be on the system during installation of this patch.\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires patch VALM*1.0*1. \n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.1;MailMan;**[patch list]**;Jun 02, 1994\nNOIS: BAC-1299-40994, BIG-0100-70871, BUT-0200-20477, CHA-1299-30668,\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nVALM 8568102 8596069 1,5\nVALM1 5659194 6138029 5\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n CLL-0300-40521, CMO-1299-40623, FAV-0200-71768, HUN-1299-20803,\n===========================================================================\n \nINSTALLATION:\nNOTE: Users should not be on the system during installation of this patch.\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires patch VALM*1.0*1. \n1. Users should NOT be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n IOW-0200-40725, LOM-1299-61417, MAD-1299-40809, STL-1299-40640,\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system.\n If it loads, go on to step 4.\n If you get the following error message:\n**INSTALL ABORTED** Patch VALM*1.0*1 is Required to install this package!!\nVALM*1.0*5 Build will not be installed, Transport Global deleted! \n and you are sure that you have installed VALM*1.0*1, you probably need\n to use FileMan to edit the package entry as follows. (This problem was\n caused because VALM*1.0*1 was released without a package file link.)\nD Q^DI\n WIM-1299-20665\nSelect OPTION: ENTER OR EDIT FILE ENTRIES\n =====\nINPUT TO WHAT FILE: PACKAGE// <press enter>\nEDIT WHICH FIELD: ALL// 22 VERSION (multiple)\n ==\n EDIT WHICH VERSION SUB-FIELD: ALL// 1105 PATCH APPLICATION HISTORY\n(multiple) ====\n EDIT WHICH PATCH APPLICATION HISTORY SUB-FIELD: ALL// .01 PATCH\nAPPLICATION HISTORY ===\n THEN EDIT PATCH APPLICATION HISTORY SUB-FIELD: <press enter>\nTest Sites: Columbia, MO; Butler, PA; Battle Creek, MI; Wilmington, DE\n THEN EDIT VERSION SUB-FIELD: <press enter>\nTHEN EDIT FIELD: <press enter>\n\nSelect PACKAGE NAME: VALM LIST MANAGER VALM\n ====\nSelect VERSION: 1.0// <press enter>\n Select PATCH APPLICATION HISTORY: 1 SEQ #1\n ========\n Are you adding '1 SEQ #1' as \n a new PATCH APPLICATION HISTORY (the 3RD for this VERSION)? No// Y (Yes)\n\n ===\n Select PATCH APPLICATION HISTORY: <press enter>\n Now try loading it again.\n\n4. You do not need to stop TaskMan.\n Users should NOT be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\nBackground: Patch VALM*1.0*3 introduced an error when printing directly (not\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VALM*1.0*5 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n\n
\nPatch VALM*1.0*6\nAPIs have not been changed at all.) Although these APIs will continue\nto be supported, applications which use them might consider switching\nto the standard Kernel APIs, too.\n\nThe following are the ListManager APIs which are no longer called,\nalong with their Kernel equivalents:\n\nListManager Kernel\n----------- ------\n$$FDATE^VALM1(X) $$FMTE^XLFDT(X,"2D")\n\n$$FTIME^VALM1(X) $$FMTE^XLFDT(X)\n$$FDTTM^VALM1(X) $$FMTE^XLFDT(X,2)\n$$NOW^VALM1() $$FMTE^XLFDT($$NOW^XLFDT)\n$$UPPER^VALM1(X) $$UP^XLFSTR(X)\n$$LOWER^VALM1(X) no equivalent - too esoteric\n\nNOTE: Users should not be on the system during installation of this patch.\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires patch VALM*1.0*4 and VALM*1.0*5.\nNOIS: ZZZ-1200-N0512\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;1.0;List Manager;**[patch list]**;Aug 13, 1993\n \n Before After\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nVALM 8596069 8483757 1,5,6\nTest Site: FORUM, CPRS\nVALM1 6138029 6406024 5,6\nVALM11 1873339 1738235 6\nVALM2 5605143 4952899 6\nVALM4 6275971 6223503 4,6\nVALM40 6770263 6733503 6\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \n\nINSTALLATION:\nNOTE: Users should not be on the system during installation of this patch.\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires patch VALM*1.0*4 and VALM*1.0*5.\n1. Users should NOT be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system.\nRecognize up-arrow so that the user can exit help text smoothly.\n4. You do not need to stop TaskMan.\n Users should NOT be on the system.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VALM*1.0*6 Loaded from Distribution <date/time>\n\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\nAlso, List Manager no longer calls its Date/Time or string manipulation\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nAPIs. Instead, it calls the equivalent Kernel APIs. (The ListManager\n\n
\nPatch VALM*1.0*7\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires patch VALM*1.0*6.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;1.0;List Manager;**[patch list]**;Aug 13, 1993\n \n Before After\n\nName Checksum Checksum Patch List\n--------------------------------------------------------------\nVALM 8483757 8475059 1,5,6,7\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOTE: Users should not be on the system during installation of this patch.\nNOIS: none\nIf they are using any application which uses List Manager (e.g. CPRS,\nOutpatient Pharmacy, Appointment Management), they may experience a Clobber\nError. This patch requires patch VALM*1.0*6.\n1. Users should NOT be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system.\n4. You do not need to stop TaskMan.\n Users should NOT be on the system.\nTest Site: BCMA Contingency\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VALM*1.0*7 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\nThis patch changes one line of code so that List Manager will work\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n===========================================================================\nunder GT.M, too. All sites should install this patch.\n\nNOTE: Users should not be on the system during installation of this patch.\n\n
\nSee patch VALM*1*8 in the National Patch Module for complete\ninformation on this patch.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n\n
\n \n With this functionality, sites will now have the ability to pre-define\n much of the dialog encountered during ordering. \n Sites may now: \n 1) Pre-define how service will be rendered (inpatient or outpatient)\n 2) Pre-define a reason for request (may be presented for editing or\n automatically entered)\n 3) Pre-define urgency of request\n 4) Pre-define place of consultation\n 5) Designate specific requests to bypass the ATTENTION: prompt\n 6) Designate certain requests as not requiring a PROVISIONAL DIAGNOSIS\n Enhancements: \n \n These enhancements will function only if an individual procedure or\n consult protocols is placed on an add orders screen. These protocols are\n in the namespace GMRCR or GMRCT. These protocols can be created by\n using the Setup Consult/Request Protocols [GMRC SETUP PROTOCOLS] option.\n \n \n \n The patch will also provide a new field in the REQUEST SERVICES(123.5)\n file called DAYS BEFORE PURGE (.06). This field control the number of\n -------------\n days that a completed consult or procedure order for that service will\n remain in the ORDER (100) file before being purged. For those services\n not having an entry in the field, orders will be maintained for 180 days.\n \n \n The GMRC SETUP REQUEST SERVICE input template on file 123.5 has been\n modified to include the new parameter for editing when setting up a new\n service.\n \n This will now be seen when using the Setup Consult/Request Services [GMRC\n The Consult/Request Tracking package will now support quick orders. This\n SETUP REQUEST SERVICES] option.\n patch will provide an option to modify existing Consult/Request Tracking\n protocols into quick orders. The new option exported is Setup\n Consult/Request Quick Order Protocols [GMRC QUICK ORDER SETUP] and this\n will be an item on the Consult/Request Management [GMRC MGR] menu.\n \n\n
\nThe description of this build can be found under GMRC*2.5*12 of the National \nPatch Module.\n\n
\nThe description of this build can be viewed under patch GRMC*2.5*13 in the \nNational Patch Module.\n\n
\nThis patch installs protocols and routines which will be used by patch\nalong with the routines:\n GMRCPOST\n GMRCPOS1\nOR*2.5*49 to allow CPRS to order consults for the services defined in the\nConsults/Request Tracking package.\n \nThis patch includes the following Protocols:\n GMRC EVSEND OR\n GMRC ORDERABLE ITEM UPDATE\n GMRC RECEIVE\n \n\n
\nYou can view the description of this patch in the National Patch Module \nunder the description of patch GMRC*2.5*16.\n\n
\nYou can view the description of this patch in the National Patch Module \nunder the description of patch GMRC*2.5*15.\n\n
\nConsult/Request Tracking and Resulting Package. Version 3.0.\nversion and patch information in the second line:\n GMRCASV 14952702 16419292 1\n GMRCAU 1632657 1632657 1\n GMRCCLR 3864606 3864606 1\n GMRCCPRS 1830089 1830089 1\n GMRCDDX 639606 639606 1\n GMRCDPCK 5953294 5953294 1\n GMRCEDIT 8745771 8745771 1\n GMRCEDT1 41636279 42298856 1\n GMRCEDT2 4798079 4364666 1\n GMRCEDT3 11149403 11149403 1\n ;;3.0;CONSULT/REQUEST TRACKING;**1**;\n GMRCEDT4 1160301 1160301 1\n GMRCFP 3129592 3129592 1\n GMRCGUIA 11746652 16311788 1\n GMRCHK 103936 103936 1\n GMRCHL7 11366432 11227877 1\n GMRCHL72 10268678 10268678 1\n GMRCHL7A 15539062 15549800 1\n GMRCHL7B 6319284 6319284 1\n GMRCHL7U 9344818 9344818 1\n GMRCMCP 7084708 7495076 1\n \n GMRCMENU 322309 322309 1\n GMRCMER 1693402 1692437 1\n GMRCMP 3361738 3361738 1\n GMRCMSS 1854144 1854144 1\n GMRCMU 928617 928617 1\n GMRCNTEG 3709091 3709091 1\n GMRCP 5045467 5045493 1\n GMRCP513 37240108 36405539 1\n GMRCPC 1890933 1890933 1\n GMRCPH 3981291 3981291 1\nThe following routines also have added changes which correct errors found\n GMRCPOR 5323056 5323056 1\n GMRCPOR1 2773 2773 1\n GMRCPP 855172 855172 1\n GMRCPR 926638 926638 1\n GMRCPR0 9262745 9410954 1\n GMRCPREF 5325580 5325580 1\n GMRCPRP 11879566 11879566 1\n GMRCPRPS 2793058 2793058 1\n GMRCPS 5339380 5339380 1\n GMRCPSEL 2393689 2393689 1\nin the interim at test sites and reported on local NOIS, as opposed to the\n GMRCPURG 17580800 20913126 1\n GMRCPX 239159 239159 1\n GMRCPZ 5085859 5085859 1\n GMRCQC 1818487 1818487 1\n GMRCQCST 19101320 19226914 1\n GMRCR 7488448 8370696 1\n GMRCR06 2960366 3275332 1\n GMRCRA 4195804 4195804 1\n GMRCREXT 1810492 1810492 1\n GMRCS 3962816 3962816 1\nNational NOIS system. The local test site NOIS's that have been resolved\n GMRCSL 1522448 1522448 1\n GMRCSLDT 6489744 6700981 1\n GMRCSLM 12065220 12065330 1\n GMRCSLM1 16808468 15946873 1\n GMRCSLM2 23538324 24019338 1\n GMRCSLM3 13045869 13938903 1\n GMRCSLMV 1499320 1499320 1\n GMRCSPD 5582555 5582555 1\n GMRCSRVS 17464043 17464043 1\n GMRCSSP 2367305 2429041 1\nin this build will not be made part of the National NOIS system. Any\n GMRCST 906358 906358 1\n GMRCSTAT 2263491 2263491 1\n GMRCSTLM 10254158 10254158 1\n GMRCSTU 29686934 29955625 1\n GMRCT 3616444 3367975 1\n GMRCTIU 21744331 21928765 1\n GMRCTIU1 3453903 3453903 1\n GMRCU 4219990 4219990 1\n GMRCUTIL 7303115 7303115 1\n GMRCUTL1 3455205 3455205 1\nlocal NOIS that is not fixed in this build, will move to the National NOIS\n GMRCXMF 5910209 5910209 1\n GMRCXQ 326583 326583 1\nsystem, and the National Patch Module management process.\n \n \n GMRC513U - Used to error when the patients location was not defined in\n the order \n GMRCADC - Corrects the loop for Selecting an item from an alert\n GMRCQCST - Fixes an STS+5^GMRCQCST error by initializing the counter.\n GMRCSLDT - Fixes DOB display in header.\n GMRCSLM1 - Changes the status displayed in List manager to 99 (No\n status) if its not defined in the consult record.\n GMRCT - Removed logic that was stopping notifications to be sent to\n the notification users, logic matches 2.5 now.\n \nThis build represents the starting point for tracking NOIS for Version\n The following routines were changed to call one location for message\n handling which now displays the message, and asks the user to press\n return to continue. This was in response to sites saying they could not\n see the message being returned because it scrolled off too fast.\n GMRC101C\n GMRCA1\n GMRCADC\n GMRCAFRD\n GMRCAR\n GMRCASV\n3.0. All of the routines that were distributed in the released 3.0\n GMRCEDT1\n GMRCEDT2\n GMRCMCP\n GMRCP513\n GMRCPR0\n GMRCR\n GMRCR06\n GMRCSLDT\n GMRCSLM\n GMRCSLM2\nversion of CONSULT/REQUEST TRACKING were inadvertantly distributed with\n GMRCSLM3\n GMRCSSP\n GMRCSTU\n GMRCTIU\n \nThe following routine added clean-up of variables:\n GMRCHL7\n GMRCHL7A\n GMRCMER\n GMRCP\n "3.0T9;CONSULT/REQUEST TRACKING" in the second line, rather than\n GMRCTIU\n \nThe following routine was deleted from site in error when V1 was\ninstalled:\n GMRCA2\n \nThe following routine has the latest purge logic for removing the order\nfrom CPRS, but leaves the consult in the Consult package:\n GMRCPURG\n \n "3.0;CONSULT/REQUEST TRACKING"\nThe following routine has changes to support the GUI Consults application:\n GMRCGUIA\n \nThis patch also contains one input template:\n GMRC SETUP REQUEST SERVICE for FILE #123.5 which had an extra field as\n its last prompt, which should not have been in the list.\n \n \n ROUTINE SUMMARY:\n ================\n \n The following is a list of the routine(s) included in this patch. The\n second line of each of these routine(s) will look like:\n \n <tab>;;3.0;CONSULTS/REQUEST TRACKING;**1**;JAN 12, 1998\n \n CHECK^XTSUMBLD results\n Routine name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n GMRC101 8413793 8413793 1\n GMRC101C 18401713 18676779 1\n All of the routines are redistributed in this build with the following\n GMRC101H 2966584 2966584 1\n GMRC513U 13170437 12667767 1\n GMRCA1 19694805 21176193 1\n GMRCA2 N/A 1578391 1\n GMRCACTM 6258472 6258472 1\n GMRCADC 6541482 6388044 1\n GMRCAFRD 15372394 17106062 1\n GMRCALOR 2588991 2588991 1\n GMRCALRT 4230024 4230024 1\n GMRCAR 14909687 17439366 1\n\n
\nSee National Patch Module for complete details of enhancements.\n\n
\nCompanion patch for CPRS GUI v31b. Will be distributed as part of the \nREQUIRIED bundle for 31b.\n\n
\nWhen Cerner Millenium replaces any given VistA instance, it will be \n \n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n ------------------ ----------------- --------------------\nHL LOGICAL LINK (#870) DATA ONLY N/A (no modified, new or \n deleted Files or Fields)\n \nParameter:\n \nThe generated HL7 message will not route to the converted VistA but to the\nFile Name (Number) Parameter New/Modified/Deleted\n------------------ ------------ --------------------\nPARAMETER DEFINITION (#8989.51) GMRC IFC REGIONAL ROUTER New\n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \nappropriate VDIF Regional Router. This will happen via one of the 4 GMRC\nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \nIFC Logical Links that are included in this patch. These links are\nN/A\n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \nN/A\n \nSecurity Keys Associated:\ndesignated "GMRC IFC1" through "GMRC IFC4".\n \nSecurity Key Name\n-----------------\nN/A\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nN/A\n \n \nAdditional Information:\nNEW PARAMETER This data is held in the Parameter Definition File \n(#8989.51)\n \nParameter - GMRC IFC REGIONAL ROUTER \nThis Parameter contains the one Logical Link for the programmatically \ndetermined VDIF Regional Router. The Links are "GMRC IFC1" - "GMRC IFC4"\nfor production, and "GMRC IFC0" to be used for testing. This Parameter\npoints to the HL LOGICAL LINK File (#870). \nIn the case of test systems, a fifth GMRC IFC Logical Link is included \n \nNew Service Requests (NSRs):\n---------------------------- \nN/A\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \nDefect Tracking System Ticket(s) & Overview:\nlabeled "GMRC IFC0", this Logical Link has no configuration included and\n--------------------------------------------\nN/A\n \nTest Sites:\n -------------\nPuget Sound, WA\nSpokane, WA\n \nSoftware and Documentation Retrieval Instructions:\n---------------------------------------------------- \nwill need to be setup to send to the appropriate VDIF Test router. As\nSoftware being released as a Packman Message.\n \nThere are no files or KIDs builds to acquire. \n \nDocumentation for the DST GUI can be found on the VA Software \nDocumentation Library at: http://www.domain.ext/vdl/\n \n \nTitle File Name FTP Mode\n-----------------------------------------------------------------------\nthere are numerous test systems involved the Logical Link configuration\nN/A \n \nPatch Installation:\n \nPre/Post Installation Overview:\n-------------------------------\nN/A\n \nPre-Installation Instructions:\n------------------------------\nnecessary for the InterFacility Consults (IFC) system to recognize that\nwill need to be done manually for test systems. As there is an unknown\nN/A \n \nInstallation Instructions:\n--------------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 minutes\nto install.\n \n 1. Choose the PackMan message containing this patch.\nnumber of test configurations, the local test site will need to determine\n \n 2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation Menu. From this menu, you may elect to use the\n following options. When prompted for the INSTALL NAME enter the\n patch #(ex. GMRC*3.0*154):\n a. Backup a Transport Global - This option will create a backup \n message of any routines exported with this patch. It will not\n backup any other changes such as DDs or templates.\nthe appropriate values for the test Logical Link.\n b. Compare Transport Global to Current System - This option will \n (allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch\n routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow you \n to ensure the integrity of the routines that are in the transport\n global.\n \n 4. From the Installation Menu, select the Install Package(s) option \n and choose the patch to install.\n \n \n 5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//'\n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//'\n \n 7. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \nThe Test system is determined by the presence of the ^%ZOSF("TEST") node \nPost-Installation Instructions:\n-------------------------------\nN/A\n \nBack-Out Plan:\n--------------------\nIf there is a need to backout this patch. The routine save that was made \nat the time of install will need to be used to overwrite the routines in\nthis patch. Once this is done the other elements included in this patch\nwill become non-functional and incapable of affecting the system.\non the installed system.\n \nIf there is a need to change the automatically assigned VDIF Logical Link\nthis information is held in a new Parameter, GMRC IFC REGIONAL ROUTER\nwhich contains the name of the Logical Link to be used when a converted\nthe HL7 message should no longer be routed to the VistA instance, but\nsite is detected by the IFC system.\n \nIf this installation is in a Test system, the default VDIF router will be\nGMRC IFC0 which will require the manual entry of the URL and Port to be\nused to connect to the Test VDIF router.\n \nFileman should be used to add this information. You will need to acquire\nthe correct test VDIF Router from the appropriate IT personnel involved in\nthe Cerner Testing and Deployment.\n \nshould go to the VDIF (Veterans Data Integration and Federation) router. A\nThe steps for adding this information are as follows:\n VISTA>D P^DI\n \n VA FileMan 22.2\n \n Select OPTION: 1 ENTER OR EDIT FILE ENTRIES\n \n Input to what File: HL LOGICAL LINK// (141 entries)\n \n EDIT WHICH FIELD: ALL// <<<< you can enter DNS DOMAIN,or TCP/IP ADDRESS\nnew status, "C", has already been added to the Treating Facility List\n and you will need to add TCP/IP PORT\n \n Select HL LOGICAL LINK NODE: GMRC IFC0 \n DNS DOMAIN: <<< you can enter a URL here OR\n TCP/IP ADDRESS: <<< or you can enter a TCP/IP address here\n TCP/IP PORT: <<< Enter a port number\n \nYou will need to consult with IT involved with the Cerner Implementation\nAnd Testing in order to get the properly values for your test system\n \n(#391.91) to indicate a specific site has been converted. When the new\nBack-Out Plan: \n--------------------\nIf there is a need to backout this patch. The routine save that was made \nat the time of install will need to be used to overwrite the routines in\nthis patch. Once this is done the other elements included in this patch\nwill become non-functional and incapable of affecting the system.\n_________________________________________________________________________\n \n Defect: <UNDEFINED>OTHER+13^GMRCIACT ^GMR(123,370322041,12)\n \nstatus is detected within the IFC process the originally intended VistA\n This patch addresses the following defect that occurs when Cerner sends\n an update via HL7 to a previously filed Vista Prosthetics IFC order:\n ERROR TEXT: <UNDEFINED>OTHER+13^GMRCIACT ^GMR(123,370322041,12)\n \n The error occurs when the Vista Consult Request Tracking Interfacility\n Consult (IFC) processing logic assuming the incoming Cerner Order number\n is a local Consult order number. Prior to EHRM Prosthetics IFC, there \n were always two different Vista stations involved in an IFC transaction. \n With the implementation of the EHRM Prosthetics IFC interface, both the \n Placer System (Cerner) order number and the Filler System (Vista \nsystem destination will be changed to one of 4 VDIF production routers\n Prosthetics) order number are associated with the same Vista station.\n As a result, checking the station number associated with the consult \n order is not sufficient to determine which order (Placer or Filler) is \n the local order.\n \n To address this issue, Consults Request Tracking will use the Filler \n System order number as the local order number if the following are true:\n 1) The Filler System station is equal to the Placer System station\n -AND-\n 2) The incoming IFC message is a PROSTHETICS IFC order\nthat are regionally located.\n -AND-\n 3) The Filler System station is equal to the local system's station\n -AND-\n 4) The Filler System order exists in local REQUEST/COSULTATION file \n (#123).\n \n \nPatch Components:\n----------------\n \n\n\nConsults build to go along with CPRS GUI v31MA (Mission Act), OR*3.0*519.\nContains the data dictionary and code changes to implement order save, \nedit/resubmit, and view/print of integrated Decision Support Tool \n(DST) and Consult Toolbox (CTB) functionality in CPRS GUI.\nSee FORUM patch description for full details.\n\n
\nPlease see patch description in FORUM.\n\n
\nTHIS PATCH ADDRESS THE ISSUE OF NON-PRINTABLE CONTROL CODES BEING SAVED \nTO THE CONSULT RECORD.\n\n
\nPlease see the patch description in FORUM.\n\n
\nThis patch addresses the following issue:\n \nThe consult auto-discontinue process invokes the discontinue action based \non the first cancellation of a consult even though a consult might have \nbeen resubmitted and cancelled at a later date.\n\n
\nBackup of GMRC*3.0*177 on Jun 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee national patch module for description of this patch.\n\n
\nBackup of GMRC*3.0*173 on Aug 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see patch description in FORUM.\n\n
\nThis patch addresses the following issue:\nCross reference AIFC in the REQUEST/CONSULTATION FILE (#123) was found to \nhave an incorrect field length for the field REMOTE CONSULT FILE ENTRY \n(#.06).\nThe field length for File (#123)/Field (#.06) is 12. The cross reference \nAIFC\nField (#.06) length is incorrect at 9.\nThe AIFC cross reference field length will be corrected to 12 numeric \ncharacters and then the AIFC cross reference will be rebuilt.\n\n
\nChanges to the Completion Time Statistics and Service Consults By\nA description of the this build can be found on the NATIONAL PATCH MODULE \nUNDER GMRC*3.0*7.\nStatus (including Service Consults Pending Resolution) reports.\n\nDo to a problem with KIDS and List Templates the template "GMRC PENDING \nCONSULTS" would not work correctly. There will be a Post Install routine \n(GMRC7L) that will install the "GMRC PENDING CONSULTS" template.\n\nKIDS will install the other List Template (GMRC REQUEST COMPLETE STAT).\n \n\n
\nPlease look to the patch description for specific technical details.\n\n
\nPlease look to the patch description for specific technical details.\n\n
\nPlease look to the patch description for specific technical details.\n\n
\nManual pkg file update due to CCRA IP connection issues.\n\n
\nModifications to the outgoing Order Entry (ORM) HL7 message when a \nmillennium generated Prosthetics Inter Facility Consult (IFC) has\na "Post Other" or "Post Complete" action taken on it in Vista.\n\n
\nSee National Patch Module for complete details of enhancements included in\nthis patch.\n\n
\nPlease refer to the National Patch Module for complete details of\nenhancements.\n\n
\nSee the National Patch Module for a complete listing of modifications made\nby this patch.\n\n
\nA description of this build can be found on the NATIONAL PATCH MODULE UNDER \nGMRC*3.0*18.\n\n
\nBuild can be found on the National Patch Module under Patch GMRC*3.0*20.\n\n
\nSee the National Patch Module for a complete list of enhancements.\n\n
\nBuild can be found on the National Patch Module under Patch GMRC*3.0*21.\n\n
\nThis patch fixes problems related to the Consult/Request\nafter this patch is installed:\n \nNAME: GMRC EVSEND OR \n ITEM TEXT: Consults event sent to OE/RR\n TYPE: extended action \n PACKAGE: CONSULT/REQUEST TRACKING\n -----Menu Items---------------------------------\n ITEM: OR RECEIVE SEQUENCE: 1\n ITEM: OCX ORDER CHECK HL7 RECIEVE SEQUENCE: 2\n \nTracking 3.0 installation.\nNAME: GMRC ORDERABLE ITEM UPDATE\n ITEM TEXT: Update Consults orderable item\n TYPE: extended action \n PACKAGE: CONSULT/REQUEST TRACKING\n -----Menu Items---------------------------------\n ITEM: OR ITEM RECEIVE SEQUENCE: 1\n \n 2) This patch also corrects the package pointer in the Dialog File\n(101.41) for 2 Dialog entries "GMRCOR CONSULT" and "GMRCOR REQUEST". This\ndone when the post-installation routine is run.\n 1) It restores the protocol menu items for GMRC EVSEND OR and GMRC\nORDERABLE ITEM UPDATE. The Consult/Request Tracking V3.0 was distributed\nwith "SEND TO SITE" which deletes OR and OCX namespaced protocol menu\nitems which must be in the menu items list in order for the CPRS and\nConsults packages to communicate with each other.\n \nThe following is what the menu items should be for the GMRC protocols\n\n
\nSee the National Patch Module for complete details of this patch.\n\n
\nSee the National Patch Module for complete details of enhancements\nincluded in this patch.\n\n
\nBuild can be found on the National Patch Module under Patch GMRC*3.0*23.\n\n
\nThis BUILD includes the Inter-facility Consults enhancement. See the \nNational Patch Module for full details.\n\n
\nSee the National Patch Module for details of the changes included in this \nbuild.\n\n
\nSee the National Patch Module for full details of the changes and/or\nenhancements included in this build. \n\n
\nSee the National Patch Module for a full list of the enhancements \nprovided by this patch. \n\n
\nCheck the National Patch Module for complete details of enhancements \nprovided in this patch. \n\n
\nPlease refer to the National Patch Module for full details of the changes \nand enhancements provided by this patch.\n\n
\nRefer to the National Patch Module for complete details of the \nchanges/enhancements included in this patch.\n\n
\nSee the National Patch module for details of the changes included in this \npatch.\n\n
\nDisassociate Results\n\n
\nRefer to the National Patch Module for complete details of the \nenhancements included in this patch.\n\n
\nSee the National Patch Module for full details of the enhancements \nincluded in this build. \n\n
\nPlease refer to the National Patch Module for a complete list of the \nenhancements included in this patch.\n\n
\nSee the National Patch Module for complete details of the enhancements \nincluded in this patch.\n\n
\nThis patch addresses the problem where a consult service can become a\nsubservice within its own subservice hierarchy.\n\n
\nThis patch corrects the inaccurate identification of the location of \ncomments when viewing an SF513 for an IFC. It also corrects the situation\nwhere the extraneous text, "Clinical Procedure Report", is displayed\ninappropriately when performing a detailed display.\n\n
\nModify Consult/Request Completion Time Statistics process to take into \nconsideration when the consult was completed the same day as the request \ndate.\n\n
\nSee the National Patch Module for the details of enhancements included in \nthis patch.\n\n
\nSee National Patch Module for details of enhancements.\n\n
\nLIST MANAGER ALLOWS FORWARDING USING TERMINATED USER\n\n
\nThis patch corrects a situation where the Significant Finding for a\nconsult is not stored.\n\n
\nThis patch adds a new Kernel look-up screen in support of Orders Data \nStandardization.\n\n
\nCONSULT/SCHEDULING LINK\n\n
\nThis patch adds a call to Imaging, at the request of the Imaging \npackage, to allow Imaging to process Consult HL7 messages.\n\n
\nThis patch exports one consult service. The service will create or \nreplace an entry in the REQUEST SERVICES (#123.5) file. This patch also \nmodifies an API routine to accept the Service Name as well as the Service \nIEN as input. Thes changes are being made at the request of the Home \nTelehealth Project group.\n\n
\nThis patch corrects group updating to store the appropriate Last Action \nTaken and to update Inter-Facility Consults at the partnering facility. \nIt also removes an inappropriate time zone stamp in the display of Consult\nactivities and prevents Services set-up as Inter-Facility from being \nadded as a Related Service to a Consult Procedure. This patch also \nprovides a list of consults which have the Significant Finding stored as \nan ampersand.\n\n
\nThis patch corrects a couple of printing issues, a consult forwarding\nissue, an administrative completion issue, and duplicate service names.\nIt also adds an additional warning when creating Consult Services and\nadditional information in the Consult documentation.\n\n
\nThis patch corrects Consult alerts being sent to users who do not wish to \nreceive them, missing Consult alerts and invalid data displaying on \nalerts.\n\n
\nThis patch modifies alert recipients in certain circumstances. It also \nmodifies an api used to determine a users update authority.\n\n
\nSee National Patch Module for details of enhancements.\n\n
\nThis build is for patch GMRC*3*57. The patch creates a new service in \n123.5 that supports the VA Suicide Hotline.\nOne post install routine adds the new serivce and also includes in the \nsub-service of the All Services grouper.\n\n
\nThis patch modifies the SF 513 report to allow for a longer \nConsult Name than 38 characters to print, and the patch also corrects \nthe Completion Time Statistics and Print Completion Time Statistics to\nprint for the actual date entered.\n\n
\nThis patch makes updates to the IFC Patient Error Report (#201) by \nincluding the Ordered Service for first report received at 3 hours, by \nsetting the priority of the SUICIDE HOTLINE Consult messages, and by \ncorrecting the "from" in the 24 hour report. This patch also creates two \nnew error reports #702 "Service is Disabled" and #703 "Procedure is \nInactive" to alert the user when a service/procedure is \ndisabled/inactivated by the Consulting Site.\n\n
\nThis patch corrects the Service Consults Schedule-Management \nReport to allow printing of all services under the Service/Specialty\nentered regardless of where it falls in the hierarchy. Help text\nis also added to menu OPTION - GMRC RPT SD SCH-MGT CONSULTS.\n\n
\nThis patch reformats the Consult Service reports (PC, CC, CP, IFC, IR, \ngroupers. The patch also corrects the issue where a "Quit" was received\nin the middle of the report which also caused incorrect page numbers and\nthe down arrow to stop working. The undefined error at SETUP CONSULT\nSERVICE has been corrected, and an alert issue in Vista has been fixed to\nallow multiple commands to be performed on the consult alert.\nNU, and SC) total section to print the totals like the Consult \nPerformance Monitor Report. Consult Reports (SC, IFC, IR, NU, PI, and \nPR) will now print a total service total line even if the total is \nzero, if the report is ran for an individual service or the grouper and \nfor all statuses. Zero service total lines will not print when the \nreport is ran for All Services, but a listing of those services will\nbe listed at the end of the report. In addition, the "ALL SERVICES" total\nsection will not count a service twice if it can be found in multiple\n\n
\nCPRS internal ClearQuest ticket 17822. Remedy ticket 292869 \nThis routine will search through ^GMR(123 and reformat comments when the \nfollowing conditions are all true:\nComment is a result of the Edit/Resubmit process, NOT just Add Comment.\n Comment is longer than 80 characters AND stored on a single global node\n OR\n Comment maybe be stored on more than one global node (i.e. user entered \n carriage returns) but has lines of text exceeding 80 characters\n \nRoutine will create a backup of comments before reformatting in a \ntemporary array, ^XTMP("GMRC_PRE69",$J). Temporary array is set to \nand 293770. Added comments during Edit/Resubmit action in CPRS GUI are \nexpire 45 days from the date of execution.\nRoutine will also send MailMan to installer containing the global \nlocation and text of any comments found prior to being reformatted.\nnot wrapping at 74 characters. As a result, comments are being stored on \na single node of the Request/Processing Activity multiple in file 123.\n \nLong comments are hard to read in CPRS GUI due to the need to scroll to \nthe right to read the entire text. Also for InterFacility Consults,\ncomments of length greater than 255 characters will not transmit via HL7.\n \n\n\nThis patch adds a call to Prosthetics, at the request of the Prosthetics \npackage, to allow Prosthetics to process Consult HL7 messages.\n\n
\nSee National Patch Module for complete details of enhancements.\n\n
\nThis patch searches for Consult Results that are attached to the wrong \npatient record. A Mailman message is sent to the installer with a report \nof those records, so they can be evaluated by the site and corrected, if \nneeded.\n\n
\nThis patch corrects an issue which causes an Inter-Facility Consult (IFC)\nto not transmit correctly to the consulting site and appear as a local\nconsult.\n\n
\nGMRC changes in support of CPRS GUI v28\n\n
\nThis patch stores and provides an audit of the PREVIOUS ATTENTION TO \nfield. The value is displayed in the Details section of the Consult\norder. In Vista, the patch prompts the user with the current ATTENTION \nvalue which they are then allowed to change, if needed. This patch also\nprevents consults in a status of "PR" and consults with unsigned or\nuncosigned notes from being forwarded to a new service. The patch also \ncorrects the lock in GMRCGUIA which was missing a time out value.\n\n
\nThis patch will address the following 3 items:\n SERVICES tied to the Consult Service.\n \n3. The Consult/Request Tracking Technical Manual and the Consult/Result\n Tracking User Manual do not state that the alert CONSULT/REQUEST\n UPDATED is sent when a consult is scheduled.\n \n1. In CPRS GUI, users can forward to a tracking only service when they \n have update authority at the parent level. However, when using CPRS\n List Manager in VistA, users cannot forward to a tracking only service\n when they have update authority at the parent level.\n \n2. When users change the SERVICE USAGE of a Consult Service to 'Grouper \n Only' or 'Disabled', they are not warned when there are any RELATED \n\n
\nTracking Issues\n\n
\nThis patch searches for Consult Results that are attached to the wrong \npatient record. A Mailman message is sent to the installer with a report \nof those records, so they can be evaluated by the site and corrected, if \nneeded.\n\n
\nThis patch prevents alerts being sent to the user performing the\naction that generated the alert and makes sure the persons receiving\nalerts is similar between VistA and CPRS GUI. It also corrects a\nword used inappropriately when returning a user's update authority\nand adds a file lock timeout value where needed.\n\n
\nThis patch corrects the wording in the description for the \nGMRC RPT PER MON report. Also, the addition of clarification\nwording for the Group Update function of Consult Alterts.\nThe clarification wording addresses PSPO #2198. Consults\nUpdate Manual is also being updated.\n\n
\nSee National Patch Module for detailed explanation of enhancements.\n\n
\nThis patch implements the New Service Request (NSR) 20130715 which masks \nPre-Installation Instructions:\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \nInstallation Instructions:\n1. Choose the PackMan message containing this patch.\n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n3. From the Kernel Installation and Distribution System Menu, select \nthe first 5 digits of the patients social security number with 'X's on \nthe Installation Menu. From this menu, you may elect to use the \nfollowing options. When prompted for the INSTALL NAME enter GMRC*3.0*\na. Backup a Transport Global - This option will create a backup \nmessage of any routines exported with this patch. It will not backup any \nother changes such as DDs or templates.\nb. Compare Transport Global to Current System - This option will \nallow you to view all changes that will be made when this patch is \ninstalled. It compares all components of this patch (routines, DDs, \ntemplates, etc.).c. Verify Checksums in Transport Global - This \n allow you to ensure the integrity of the routines that are in the \nthe Standard Form (SF) 513 Consult Form. This code modification has been\ntransport global.\nto ensure the integrity of the routines that are in the transport global.\n4. From the Installation Menu, select the Install Package(s) option \n and choose the patch to install.\n5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//'\n This patch does not require logons to be inhibited.\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//' \nreviewed by Patient Safety and the SSN Reduction team because the\n This patch does not require any items to be disabled.\n \nRoutine Information:\n====================\nGMRCP5D\n \n \nUser Information: \n Entered By : DOUGLAS HALL Date Entered : DEC 15,2015\n Completed By: Date Completed: \n513 has two other unique identifiers (name and DOB).\n Released By : Date Released : \n \n \nRoutine Information:\n====================\n \n \nRoutine Name: GMRCP5D\n Description of Changes:\n Before\n \n *****************************************************************\n .D BLD("HDR",SUB,1,0,GMRCSN)\n *****************************************************************\n After\n *****************************************************************\n .D BLD("HDR",SUB,1,0,"XXX-XX-"_$P(GMRCSN,"-",2,3)\n *****************************************************************\n End of Differences\n \n \nThis NSR is part of the VistA Intake Program (VIP) which delivers\n==========================================================================\nUser Information: \n Entered By : HALL,DOUGLAS Date Entered : JAN 15,2015\n Completed By: Date Completed: \nVistA modifications developed at sites as class I VistA software.\n \n\n\nRemove diagnosis code validation from processing of new and edit/resubmit \nconsult orders.\n\n
\nHandles the GMRC portion of changing EARLIEST DATE in 123 to CLINICIALLY \nINDICATED DATE.\n\n
\nImplement the NEW style AG cross-reference in the REQUEST/CONSULTATION \nfile 123 for all entries that do not have an appointment scheduled.\n\n
\nAdded a call to Health Management Platform (HMP) API to initiate an \nunsolicited sync action to send a comment as it is added to the consult.\n\n
\nThe Consult Closure Tool allows users to track consults, associated \nfollow-up appointments, and associated progress notes. Consults may be \nclosed interactively. A consult/note report may be printed. A CPRS team \nmay be updated.\n\n
\nThis patch corrects a hard error that continues to occur with \nInter-Facility Consults. The background routine GMRCIBKG has been \nchanged to return the correct Station Number so that Inter-Facility \nConsults processes correctly. \n\n
\nSee the National Patch Module for full description of enhancements.\n\n
\nAdds override mechanism for Send additional alerts on consult comments. \nReleased with OR*3*452.\n\n
\nThis patch fixes a data integrity issue related to the following issue:\nThis patch is bundled with a Scheduling patch that addresses this and \n \nOptions Associated:\n New/Modified/\nOption Name Type Deleted \n----------- ---- -------------\nN/A\n \n \n \nParameter Definitions:\nother issues. Below is a list of all the applications involved in this\n New/Modified/\nParameter Name Deleted \n-------------- -------------\nN/A\n \n \n \nParameter Template:\n New/Modified/\nTemplate Name Deleted \nbundle along with their patch number:\n------------- -------------\nN/A\n \n \n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\nN/A\n \n \n \n \nRemote Procedures Associated:\n New/Modified/\nRemote Procedure Name Deleted \n--------------------- -------------\nN/A\n \n \n APPLICATION/VERSION PATCH\n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n----------------- -------------\nN/A\n \n \n \nTemplates, Input Associated:\n ---------------------------------------------------------------\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nTemplates, List Associated:\n New/Modified/\nTemplate Name Type Deleted \n SCHEDULING (SD) V. 5.3 SD*5.3*679\n------------- ---- -------------\nN/A\n \n \n \nTemplates, Print Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n CONSULT/REQUEST TRACKING (GMRC) V. 3.0 GMRC*3.0*98\n \n \n \nTemplates, Sort Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\n---------------------------- \nN/A\n \n \nPatient Safety Issues (PSIs)\nPatch Components\n-----------------------------\nN/A\n \n \nService Desk Manager (SDM) Ticket(s) & Overview\n-----------------------------------------------\n1. I16857061FY18 Consults are showing activities out of order in CPRS; \n VistA FM shows activities in correct chronological order\n \nProblem:\n \n================\n-------\nOur site is experiencing issues with Consults where the activities being \nrecorded are out of order. I originally thought this was a result of the \nCONSULT TOOLBOX tool, but there are multiple sites reporting this issue, \nand the consensus is that this is being caused by VSE.\n \nResolution:\n----------\nThe code that saves the SCHEDULED or STATUS CHANGE event when the \nappointment is scheduled or canceled was corrected to save the timestamp\n \ncorrectly.\n \n \nTest Sites:\n----------\nTBA\n \n \nDocumentation Retrieval Instructions\n------------------------------------ \nFiles & Fields Associated:\nUpdated documentation describing the new functionality introduced by this \npatch is available.\n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/.\nThis transmits the files from the first available FTP server. Sites may \nalso elect to retrieve software directly from a specific server as \nfollows:\n \n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n \n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n--------------------------------------------------------------------------\nVistA Scheduling Enhancements GUI User Guide VSE_VA_GUI_UG.PDF Binary\nVistA Scheduling Enhancements Technical Manual VSE_TM.PDF Binary\nFile Name (#) New/Modified/\n \n \nPatch Installation:\n \n \n Pre/Post Installation Overview\n ------------------------------\n The components sent with this patch GMRC*3.0*98 have been included in \n the Host File SD_GMRC_VSE_BUNDLE_1_5.KID. Please follow the instructions\n listed in the INSTALLATION INSTRUCTIONS section of the patch description\n Sub-file Name (#) Field Name (Number) Deleted\n for patch SD*5.3*679.\n \n \n Installation Instructions\n -------------------------\n The components sent with this patch GMRC*3.0*98 have been included in \n the Host File SD_GMRC_VSE_BUNDLE_1_5.KID. Please follow the instructions\n listed in the INSTALLATION INSTRUCTIONS section of the patch description\n for patch SD*5.3*679.\n------------------- --------------------------------- -------------\nN/A\n \nBulletins Associated:\n1. I16857061FY18 - If a scheduler makes or cancels an appointment for a \n New/Modified/\nBulletin Name Deleted \n------------- -------------\nN/A\n \n \n \nDialogs Associated:\n New/Modified/\nDialog Name Deleted \n consult and the current time ends in a zero (like \n----------- -------------\nN/A\n \n \n \nForms Associated:\n New/Modified/\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\nN/A\n 9:40), then the event recorded in the consult will\n \n \n \nFunctions Associated:\n New/Modified/\nFunction Name Deleted \n------------- -------------\nN/A\n \n \n display at the end of the consult event history instead\n \nHL Logical Link:\n New/Modified/\nHL Logical Name Deleted \n--------------- -------------\nN/A\n \n \n \nHL7 Application Parameters:\n of in sequence.\n New/Modified/\nHL7 Parameter Name Deleted \n------------------ -------------\nN/A\n \n \n \nHLO Application Registry:\n New/Modified/\nHLO Registry Name Deleted \n \n----------------- -------------\nN/A\n \n \n \nHelp Frames Associated:\n New/Modified/\nHelp Frame Name Deleted \n--------------- -------------\nN/A\nThis issue requires a fix to repair existing data effected by the issue.\n \n \n \nMail Groups Associated:\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\nN/A\n \n \n\n
\nAdded a call to Health Management Platform (HMP) API to initiate an \nunsolicited sync action to send a comment as it is added to the consult.\n\n
\nGMRC patch 106 test version 3\n\n
\nPatch GMRC*3*104 addresses the following issue:\n \n1. Deleting sub-service entries in the REQUEST SERVICES [123.5] file \ncauses data integrity issues.\n\n
\nThis report is sorted by a From Date and a To Date. The report is then \ndisplayed by Consult to Service/Specialty headers along with a list of \nthe Releasing Person as a sub-header to the above header group. The \nsub-header has a total field which represents the number of consults\nreleased by policy for each Releasing Person. The header contains a\ngrand total of all the sub-totals.\n\n
\nThe description of this build can be found in the National Patch Module \nunder GMRC*3.0*114.\n\n
\nSee National Patch Module for full description of enhancements.\n\n
\nThis patch is being released to correct a defect identified in Incident\nINC3759691, and to add descriptions to three new reports on the Consult \nManagement menu (GMRC MGR):\n \n GR Administratively Released Consults by Group\n ST Completion Time Statistics\n US Administratively Released Consults by User\n\n
\nThis patch creates an NTE segment in the ORMO001 message which will\ncontain the UCID.\n\n
\nGMRC PATCH 112 - Emergency patch to fix control character issues in\nconsult file, causing infinite looping in HL7 message processing\n\n
\nAssociated patches: Informational Patch GMRC*3.0*125\n \nThis Decision Support Tool VistA patch includes a protocol that invokes a \nprocess to retrieve the consult factor text from DST and insert it into a \nconsult comment whenever a consult order is signed that contains the \nstring "DST ID:" in the Reason for Request field.\n\n
\nGMRC*3.0*105 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\n The Community Care Referrals and Authorizations (CCR&A) application is \n \n This patch builds upon the HL7 processes created in patches \n GMRC*3.0*99 and GMRC*3.0*106. It includes an update to the Other\n Health Information (OHI) data being sent from VistA to the HealthShare\n Referral Management system (HSRM), adding several new OHI fields and\n the provider NPI value. It also allows VistA to receive consult status\n updates from HSRM and associated consult notes.\n an enterprise-wide system used by Community Care (CC) staff to \n automatically generate referrals and authorizations for all Veterans \n receiving care in the community. Clinical and VA CC staff located at \n VA Medical Centers, Outpatient Clinics, Community Based Outpatient\n Clinics, and VISN offices use this application. The CCR&A solution is\n an integral component of the VA Community Care Information Technology\n (IT) architecture that allows Veterans to receive care from Community \n Providers. \n\n
\nGMRC*3.0*146\nAdd Admin Complete consult notes\nFix DX issue\n\n
\nConsult/Request Tracking and Resulting Package. Version 3.0.\n\n
\nThis package provides the tools needed for Consults and Requests to be\nordered via OE/RR and then tracked by the service receiving the order.\n\n
\nSee National Patch module entry for DG*5.3*77 for detailed information on\nthe contents of this patch.\n\n
\nSee NPM for description of patch.\n\n
\nSee National Patch Module \n \n \n \n \nAdd Location and Room Bed to Admission Alert.\n\n
\nPost patch 91 fixes\n\n
\nPatch DG*5.3*172, which is included in the Clinical Information Resource\n 991.07 SCORE CALCULATION DATE\n Pseudo-SSN Report\n Eligibility Code Files Report\n Marital Status File - Map Non-Standard Entries\n Religion File - Map Non-Standard Entries\n Begin Religion/Marital Status Conversion\n Stop Religion/Marital Status Conversion\n CIRN Master of Record Menu ...\n \nThe following options will be deleted after the conversion is completed.\n Marital Status File - Map Non-Standard Entries\n \n Religion File - Map Non-Standard Entries\n Begin Religion/Marital Status Conversion\n Stop Religion/Marital Status Conversion\nThese fields facilitate the functionality of the CIRN software utility,\nStart/Restart CMOR Score Calculation [RGCIRN CMOR START] option, which\ncalculates a metric used for determining the CIRN Master of Record (CMOR)\nsite. This metric is based on patient activity at the site for the present\nFiscal Year (FY) plus the prior two FYs. In essence, the software reviews\nindicators of patient activity and assigns points for activity. The result\nis a standard measurement that the system can utilize in determining the\nCMOR site for each patient.\nNetwork (CIRN) Pre-implementation software Version 0.5 release, contains\n \nSecond, the patch delivers the utilities related to the MARITAL STATUS\nfile (#11) and RELIGION file (#13) clean-up during the implementation\nphase. The utilities (1) analyze the MARITAL STATUS and RELIGION files for\nnon-standard entries, (2) allow the user to specify, for each non-standard\nentry, which standard entry should be mapped with associated patients,\n(3) actually re-point the associated patients to the standard entries,\n(4) delete the non-standard entries after re-pointing, and (5) delete the\nfiles, templates, and user options after the clean-up process has been\ncompleted. A description of the MARITAL STATUS and RELIGION files clean-up\ntwo components.\nfollows.\n \nAnalysis Step:\nWhen the patch is first installed, an analysis step is automatically run.\nThis analysis step reviews all files and fields on the local system that\npoint to the MARITAL STATUS and RELIGION files. The resultant analysis\ndata is then stored in a temporary file, the MARITAL/RELIGION CONVERSION\nfile (# 390.1), for later processing. See the conversion step for more\ninformation on this later process.\n \n \nThe second part of the analysis reviews the MARITAL STATUS and RELIGION\nfiles. It adds standard entries to these files that are missing and\nsearches for non-standard entries. This analysis data is also stored in a\ntemporary file, the MARITAL/RELIGION MAPPING file (# 390.2), for later\nprocessing. See the mapping step for more information on this later\nprocess.\n \nMapping Step:\nAny non-standard entries found during the analysis step must be mapped to\na valid standard entry. This information is used during the conversion\nFirst, the patch provides a partial Data Dictionary (DD) update that adds\nstep to map patients who are associated with the non-standard entries.\nThere are two menu options in the CIRN Pre-Implementation Menu [RGPR\nPRE-IMP MENU] for mapping these entries.\n \n Marital Status File - Map Non-Standard Entries\n [DG172 PRE-IMP MAR STAT MAP]\n Religion File - Map Non-Standard Entries\n [DG172 PRE-IMP RELIGION MAP]\n \nThe mapping data designated by the user is then stored in File #390.2.\ntwo new fields to the PATIENT file (#2). These new fields are listed\n \nConversion Step:\nAfter the mapping of non-standard entries is complete, a conversion\nprocess is run which re-points non-standard entries to the designated\nstandard entries. The options, also in the CIRN Pre-Implementation Menu,\nto begin and stop the conversion process are listed below.\n \n Begin Religion/Marital Status Conversion\n [DG172 PRE-IMP START CONVERSION]\n Stop Religion/Marital Status Conversion\nbelow.\n [DG172 PRE-IMP STOP CONVERSION]\n \nThe conversion process will update each file/field that points to the\nMARITAL STATUS and RELIGION files based on the analysis data stored in\nFile #390.1.\n \nAs the conversion process is running, the progress is stored in two files.\nThe first File # 390.1 stores the last entry processed for each file/field\nthat needs to be converted. As each file/field is converted, it is flagged\nas finished.\n \n \nThe second File #390.2 stores the number of times a non-standard entry was\nfound and converted across all files/fields.\n \nAfter the conversion process is complete, an e-mail message is generated\nand delivered to the user of the Begin Religion/Marital Status Conversion\noption. The message reports the number of conversions that took place for\neach non-standard entry.\n \nUn-Install Step:\n 991.06 CMOR ACTIVITY SCORE\nAfter the conversion is finished, the two temporary files, File #390.1 and\nFile #390.2, are deleted along with the non-standard entries from the\nMARITAL STATUS and RELIGION files. Associated templates and menu options\nare also deleted.\n \nThe complete CIRN Pre-Implementation Menu, prior to conversion, is listed\nbelow.\n \nSelect CIRN Pre-Implementation Menu Option:\n \n\n
\nSee National Patch Module\n\n
\nThis build is part of the overall patch SD*5.3*149, and provides the\ncapability to capture GAF scores as part of the Census record and a call\nto send GAF data to the Mental Health package from the scan forms.\n\n
\nSEE NATIONAL PATCH MODULE FOR DESCRIPTION\n\n
\nSee National Patch Module\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nThis patch will change the POST-KOREAN END DATE (#.05) and BRIEF \nDESCRIPTION (#20) fields in the PERIOD OF SERVICE (#21) file to\nprevent overlapping with VIETNAM ERA period of service.\n \nThe END DATE (#.05) field will be changed from 8/4/1964 to 2/27/1961\nand the BRIEF DESCRIPTION (#20) field will be changed to 2/1/55-2/27/61.\n\n
\nSee National Patch Module.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*175 in the National Patch Module.\n\n
\nThis patch updates the PTF CENSUS DATE File (#45.86) for the first\n CLOSEOUT DATE: JAN 15, 1999\n OK TO XMIT PTF TRANSACTIONS: MAR 31, 1997\n CURRENTLY ACTIVE?: YES \n CENSUS PERIOD START DATE: OCT 01, 1998\nquarter of FY 1999 (10/1/1998-12/31/1998). The closeout date for this\ncensus is 1/15/1999.\n \nThe DATE(#.01), CLOSEOUT DATE (#.02), OK TO XMIT PTF TRANSACTIONS (#.03),\nCURRENTLY ACTIVE?(#.04), and CENSUS PERIOD START DATE (#.05) fields in\nthe PTF CENSUS DATE file (#45.86) will be updated as follows:\n \n DATE: DEC 31, 1998 \n\n
\n1999 Means Test Threshold update patch. See National Patch Module for\nfurther details.\n\n
\nSee National Patch Module for description.\n\n
\nNPCDB patient demographics extraction\n\n
\nSEE NATIONAL PATCH MODULE\n\n
\nSEE NATIONAL PATCH MODULE\n\n
\nACRP transmission segment issues\n\n
\nSEE NATIONAL PATCH MODULE\n\n
\nADT/R Portion of PCMM - DG*5.3*84\n\n
\nSee National Patch Module on FORUM for a description of the contents of\nthis patch.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*177 in the National Patch Module.\n\n
\nPatient Survey for Dr Steinhauser.\n\n
\n2nd QTR FY99 PTF Census patch.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*222 in the National Patch Module.\n\n
\n It prevents the duplication of the pseudo WHILE ASIH discharge. In a\n test environment changing a TRANSFER TO ASIH(OTHER FACILITY) to a\n TRANSFER TO ASIH incorrectly created a duplicate WHILE ASIH discharge.\n The effect of this extra discharge would be reflected in the Bed Status\n Report. This patch prevents the duplication from occuring.\n\n
\nSee National Patch Module.\n\n
\nFix to PD1 segment builder to prevent PC provider = -1 from being sent\nto Austin.\n\n
\nFor a complete description, refer to the FORUM Patch Module\nfor patch DG*5.3*149.\n\n
\nThe changes included in this patch are described in the description of\npatch DG*5.3*230 in the National Patch Module.\n\n
\nThis is the quarterly update patch for FY 96, quarter 2. The changes\nincluded in this patch are described in the description of patch DG*5.3*78\nin the National Patch Module.\n\n
\nThis patch updates the PTF CENSUS DATE File (#45.86) for the third\npermanent routines so it may be loaded out of sequence, if necessary, to\nmeet the 6/30/1999 date.\nquarter of FY 1999 (4/1/1999-6/30/1999). The closeout date for this\ncensus is 7/16/1999.\n \nThis patch addresses the Quarterly Census issue discussed in VHA\nDirective 98-056.\n \nThis patch may be installed at anytime, however, it must be installed\nbefore 6/30/1999. This patch does not affect any options or any\n\n
\nVHA Directive 98-058, "Sexual Trauma Counseling Care and Services"\nrequires that VHA provide care and counseling to veterans determined to\nhave been a victim of sexual trauma while the veteran was serving on\nactive duty. This patch will focus on the data collection for this\ndirective.\n\n
\nAddresses SHARING AGREEMENT SUBCATEGORY ISSUES raised in NOISes\nSYR-0698-11882 and ALB-1298-52122. Allows the editing of the Subcategory\nname, and screens subcategory selection by whether it is active.\n\n
\n Patch DG*5.3*149 added new cross references to a number of fields\n .05 MARITAL STATUS\n .08 RELIGIOUS PREFERENCE\n .09 SOCIAL SECURITY NUMBER\n .111 STREET ADDRESS [LINE 1]\n .1112 ZIP+4\n .112 STREET ADDRESS [LINE 2]\n .113 STREET ADDRESS [LINE 3]\n .114 CITY\n .115 STATE\n .117 COUNTY\n from the PATIENT file (#2). Clinical Information Resource Network\n .131 PHONE NUMBER [RESIDENCE]\n .132 PHONE NUMBER [WORK]\n .211 K-NAME OF PRIMARY NOK\n .219 K-PHONE NUMBER\n .2403 MOTHER'S MAIDEN NAME\n .301 SERVICE CONNECTED?\n .302 SERVICE CONNECTED PERCENTAGE\n .31115 EMPLOYMENT STATUS\n .323 PERIOD OF SERVICE\n .351 DATE OF DEATH\n (CIRN) needs to monitor changes made to these fields. This patch\n 391 TYPE\n 1901 VETERAN\n \n The post-install routine DG53231P is invoked to re-compile all Print\n Templates and Input Templates for the affected fields. \n turns audit ON for a number of fields in the PATIENT file. \n \n The following is a list of fields in the PATIENT file for which \n auditing is turned on: \n .02 SEX\n .03 DATE OF BIRTH\n\n
\n \nThis KIDS build installs the routine DG53233P which activates the\nENROLLMENT QUERY ACTIVE (#15) field of the IVM SITE PARAMETER (#301.9).\n \nIt also includes a change to the description to correct a spelling mistake\nin the Data Dictionary for the IVM SITE PARAMETER (#301.9) file.\n\n
\nNew routine (DGMTARR) creates and prints 3 new Means Test reports. The\n'Report for Specific Income Amount' . This report uses input from the\nuser to define a dollar range and date range, and prints veterans whose\nincome falls between the dollar range and date range. The 'Report of\nincome range Less than Threshold' will print veterans whose income is\nwithin the selected range less than the Threshold amount. The last\nreport, 'Report of Same Income', shows veterans who reported the identical\nincome value for all 10 income fields.\n\n
\nSee the National Patch Module for a complete description of this patch.\n\n
\nE3R 12006 notes that the terms "Primary Care Physician" and "Primary Care\n \nNo routines are included.\nProvider" are used in ways that may be confusing. The Primary Care\nProvider for the PCMM package is different from the Inpatient Primary Care\nProvider. For purposes of clarity, in the PATIENT MOVEMENT file (#405),\nthe field name of field #.08 has been changed from PRIMARY CARE PHYSICIAN\nto PRIMARY PHYSICIAN.\n \nThe Data Dictionary for this field is included, as is the DGPM SPECIALTY\nTRANSFER input template, to accommodate this change.\n\n
\nThis patch updates the PTF CENSUS DATE File (#45.86) for the fourth\nquarter of FY 1999 (7/1/99 - 9/30/1999). The closeout date for this\ncensus is 10/15/99.\n \nThis patch addresses the Quarterly Census issue discussed in VHA\nDirective 98-056.\n\n
\nThis patch corrects a problem reported when entering breakeven days for\nmultiple DRGs using the Enter Breakeven Days, [DG PTF BREAK EVEN ENTER],\noption.\n \nIt was also discovered that this option will not accept fiscal years after\n1999.\n\n
\nSee NPM for description.\n\n
\nIncome Inconsistency for SC veterans 50-100%.\n\n
\nThis patch will prevent a user from accessing or creating their own\nPatient (#2) file entry if the Restrict Patient Record Access (#1201) in\nthe MAS Parameters (#43) file is set to yes and the user does not hold\nthe DG RECORD ACCESS security key. \n \nIf the user does not have a SSN defined in the New Person (#200) file they\nwill not be allowed to access any Patient file record. If the SSN in the\nNew Person file matches the Patient file SSN they will not be allowed to\naccess or create their own Patient file record.\n\n
\nSee National Patch Module for description of changes included in this patch.\n\n
\nY2K DGR report fixes\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*226 in the National Patch Module.\n\n
\nRE-ENROLLMENT - ACTIVATE CD FUNCTIONS\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nThis build contains changes to a load/edit screen routine for PCMM patch \nSD*5.3*177.\n\n
\nRefer to National Patch Module for details\n\n
\nSee the National Patch Module for a complete description of patch\nDG*5.3*253.\n\n
\nSee NPM for description.\n\n
\nThis patch corrects Enrollment issues.\n\n
\nThis patch distributes the Means Test thresholds for the year 2000.\n\n
\nThis patch updates the PTF CENSUS DATE (#45.86) file for the 1st quarter\nof FY 2000 census.\n\n
\nMeans Tests affecting workload patch. See National Patch Module for\nfurther details.\n\n
\nTREATING FACILITY/PATIENT MERGE NAME\nRefer to patch DG*5.3*240 in the FORUM Patch Module for a complete \ndescription.\n\n
\nNew PTF Places of Disposition\n\n
\nSee the national patch module for details.\n\n
\nPATIENT MERGE/MEANS TEST MODIFICATION\n\n
\nThis patch contains modifications to the patient look up process for GUI\nTwo RPCs will be created for GUI applications:\n \n - DG SENSITIVE RECORD ACCESS determines if the user is accessing\nhis/her own Patient file record, if the record is sensitive or if\nthe patient's primary eligibility code is employee.\n \n - DG SENSITIVE RECORD BULLETIN updates the DG Security Log file and\ngenerates the Sensitive Record Access mail message.\ninterfaces and provides functionality for Privacy Act compliance for\nemployees.\n \nIf the patient's primary eligibility code is employee, the DOB and SSN\nfields will display *SENSITIVE* until the user acknowledges they wish to\naccess the sensitive record. The DG Security Log file is updated and\nthe Sensitive Record Access mail message generated.\n \n\n
\nThis is the quarterly update patch for FY 96, quarter #3. The\nchanges included in this patch are described in the description\nof patch DG*5.3*93 in the National Patch Module.\n\n
\nExcess HL7 messages from patient lookup\n\n
\nThis patch modifies routine DGPTMOVE to correctly display the next fiscal\nyear in the Move Trim Values, [DG PTF MOVE TRIM], option.\n\n
\nPatient Lookup Functionality\n\n
\nAddresses NOIS NCH-0999-43030. Remove Cease Enrollment option from \n[DGEN PATIENT ENROLLMENT] ListMan interface.\n\n
\nThis patch updates the PTF CENSUS DATE (#45.86) file for the 2nd quarter\nof FY 2000 census.\n\n
\nSee National Patch Module for details. \n\n
\nThis patch eliminates the undefined error when execution returns to\nthe routine DGREG after the DINUM variable has been newed in the routine\nDIR1 at IT+1 and set to an inversed date/time.\n \nThe changes included in this patch are described in the description of\npatch DG*5.3*245 in the National Patch Module.\n\n
\nSee National Patch Module for details.\n\n
\nSee national patch module entry DG*5.3*99 for details on the contents of\nthis build.\n\n
\nPATIENT file DD change\n\n
\nIf the DGSENFLG variable is set by the calling program, the patient's\nsensitive record status should not be checked during a patient look up.\nThis patch modifies routines DGSEC and DGSEC4 restoring this process to\nits original functionality prior to DG*5.3*249, DGSEC MODIFICATIONS &\nPRIVACY ACT COMPLIANCE FOR EMPLOYEES.\n\n
\nCPT MODIFIERS AND MST\n\n
\nResolve Issue with invalid Receiving Facility and Undefined Variable DGX\nin DGPMV301\n\n
\nCPRS REMOTE DATA VIEWS\nRefer to patch DG*5.3*261 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatient Wristband and History Listing.\n\n
\nThis patch updates the PTF Census Dates (#45.86) file with the dates for\nthe 3rd quarter PTF census.\n\n
\nVAFC EXCEPTION HANDLER OPTION\nRefer to patch DG*5.3*255 in the FORUM Patch Module for a complete \ndescription.\n\n
\nSee National Patch Module (Patch DG*5.3*291) for details.\n\n
\n KIDS distribution of the Registration portion of the Ambulatory Care\n Reporting Project.\n \n The changes included in this patch are described in the description of\n patch DG*5.3*94 in the National Patch Module.\n\n
\nThis patch installs the routine and Data Dictionary change required to\nthis instruction, a commercial product was selected to implement this\ndirection. This patch installs the Data Collection functionality needed\nby the COTS system for initial data seeding of the HL7 interface required\nfor this product.\nperform the Data Collection process which will be used to seed the\nCommercial-Off-The-Shelf Resident Assessment Instrument / Minimum Data Set\nVer. 2.0 (RAI/MDS). MDS Ver 2.0 is currently used in Medicare (Title 18)\nskilled nursing facilities and Medicaid (Title 19) nursing facilities.\n \nIn May 1995, the VHA's Long-term Care Policy Plan, Information Letter IL\n10-95-024 was approved and charged the Office of Geriatrics and Extended\nCare with national implementation and automation of the RAI/MDS. Under\n\n
\nThis patch corrects the problem of not being able to enter a future date\non the last day of the month when running the "List of Patients on ASIH" \nreport. The correction to this problem enables the user to enter any future\ndate. In so doing, if a future date is entered the user is reminded that they\nmay want to queue this report so as to avoid printing a negative report.\n \nThis problem was reported in NOIS # MIN-0199-42808.\n \nThe routine DGOASIH was modified to correct this problem.\n\n
\nThis patch addresses the Tricare/Champus issue, where closing PTF records\nfor patients with a single eligibility of "Tricare/Champus" paired with a\nPeriod of Service of "Champus" causes the 114 error.\n\n
\nSee National Patch Module for details.\n\n
\nThis patch installs the routines and Data Dictionary changes required for\nthis instruction, a commercial product was selected to implement this\ndirection. This patch installs the VistA portion of the HL7 interface\nrequired for this commercial product.\nthe VistA HL7 Interface to the Commercial-Off-The-Shelf Resident\nAssessment Instrument / Minimum Data Set Ver. 2.0 (RAI/MDS). MDS Ver 2.0\nis currently used in Medicare (Title 18) skilled nursing facilities and\nMedicaid (Title 19) nursing facilities.\n \nIn May 1995, the VHA's Long-term Care Policy Plan, Information Letter IL\n10-95-024 was approved and charged the Office of Geriatrics and Extended\nCare with national implementation and automation of the RAI/MDS. Under\n\n
\nSee National Patch Module (Patch DG*5.3*292) for details.\n\n
\nDelete patients from PATIENT/IHS FILE when patients are deleted from\nPATIENT FILE.\n\n
\nSTOP ADDRESS UPDATES\nRefer to patch DG*5.3*295 in the FORUM Patch Module for a complete\ndescription.\n\n
\nTREATING FACILITY LIST\nRefer to patch DG*5.3*316 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee national patch module DG*5.3*100 for details of this patch.\n\n
\nPlease see Natinal Patch Module for details.\n\n
\nThis patch updates the PTF Census Dates (#45.86) file with the dates for \nthe 4rd quarter PTF census.\n\n
\nEXCEPTION MESSAGES / PATIENT DATA REVIEW\nRefer to patch DG*5.3*307 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see DG*5.3*290 in the National Patch Module for a complete\ndescription.\n\n
\nThis patch is a clean up to follow patch DG*5.3*267. It will correct the \nproblems of where a previous income years test was made non primary after \na future test became active for the current income year.\n\n
\nThis API returns an array of data from the Patient Treatment\n (2)=2nd thru 10th ICD9 codes\n \nIntegration Agreements #3157(API) and #3164 (RPC) have been obtained.\nfile (#45). It can also be done as a Remote Procedure call\n(in the Remote Procedure file #8994, see DG PATIENT TREATMENT DATA).\n \nThe call is to RPC^DGPTFAPI(RESULTS,PTFNUMBR) where RESULTS is the\narray passed by reference, and PTFNUMBR is the IFN of the Patient\nTreatment file. Currently, the data returned is:\n RESULTS(0)=1 or -1 if an error occured\n (1)=type of disposition^place of disposition^1st ICD9 code\n\n
\nTo address several miscellaneous Treating Specialty, IRT and VADPT NOISs.\n\n
\nExtract patient address information from a list of social security\nnumbers.\n\n
\nContains routine DGPTFVC1 which fixes a problem in performing the validity\nchecks on station number. See the National Patch Module entry for\nDG*5.3*79 for more information.\n\n
\nSee NPM for description.\n\n
\nThis patch is being distributed as part of the National implementation of\nthe 1010EZ web initiative. This initiative allows a veteran to enter and\nsubmit an enrollment application through an online 1010EZ form to their\npreferred VAH medical facility. \n\n
\nThis patch provides an API to determine if a patient's treating specialty\nfor a specified movement or date/time is or was an observation specialty.\nRoutine DGPMOBS provides three entry points: MVT, PT and SPEC.\n \nPlease see NPM patch description for complete documentation.\n\n
\nPlease refer to patch number DG*5.3*305.\n\n
\nThis patch is designed to correct the message that is received when the \nfacility received is not found during the processing of incoming HL7\nmessages.\n\n
\nFix 1010F printing problems\n\n
\nAllow sites to enter MT before CAD\n\n
\nSee patch DG*5.3*318 in FORUM for description of this Build.\n\n
\nNew Data Seed for RAI/MDS.\n\n
\nSee National Patch Module description.\n\n
\nSee National Patch Module for details.\n\n
\nICN HISTORY CORRECTION\nRefer to patch DG*5.3*329 in the FORUM Patch Module for a complete\ndescription.\n\n
\nExtract patient address information from a list of social security\nnumbers.\n\n
\nIncorrect values from GETSTAT^DGMSTAPI.\n\n
\nPlease refer to patch DG*5.3*330.\n\n
\nFACILITY + SUFFIX ON PV1 SEGMENTS\n\n
\nPlease see Patch DG*5.3*337 in the National Patch Module for description of\nthis Build.\n\n
\nRoutines needed for Patch DG*5.3*311. The routines are DGMTU11, DG311PTR,\nDG311PIR and DG311RPT. Please see National Patch Module for more details.\n\n
\nPlease refer to patch DG*5.3*297.\n\n
\nSee National Patch Module.\n\n
\nPatch DG*5.3*353 addresses NOIS LOM-0900-60219 where the "Yes or No"\nresponse at the "TREATED FOR AO CONDITION:" and "TREATED FOR IR\nCONDITION:" PTF movement prompts are overwritten with the current fileman\ndate. This situation creates validation issues.\n\n
\nSee Patch DG*5.3*302 in the National Patch Module for description of this\nBuild.\n\n
\nPlease refer to patch DG*5.3*347.\n\n
\nSee patch DG*5.3*335 in the National Patch Module for description of this\nbuild.\n\n
\nSee patch DG*5.3*346 in the National Patch Module for description of this\nbuild.\n\n
\nSee patch DG*5.3*345 in the National Patch Module for description of this build.\n\n
\nCORRECT CONSISTENCY CHECK FOR CD ENTRY\n\n
\n See National Patch Module for description of changes included in this\n patch.\n\n
\nPlease see Patch DG*5.3*294 in the National Patch Module for description of\nthis Build.\n\n
\nPlease see Patch DG*5.3*327 in the National Patch Module for description of\nthis Build.\n\n
\nThis patch solves a patient information display break problem, and patient lock problem.\n\n
\nThis patch will install a new version of routine DGRUHL1. The new version\nwill send the DGRU REJECT bulletin to the DGRU RAI NOTIFICATION mail group\nwhen an HL7 message gets rejected by the Accu-Med System and will include\nthe patient name, SSN, HL7 event code, reject reason, parent message ID,\nand the date/time of the parent message.\n\n
\nPlease see National Patch Module for description of this Patch.\n\n
\nPATIENT DATA REVIEW ENHANCEMENTS\nRefer to patch DG*5.3*333 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*101 in the National Patch Module.\n\n
\nSee Description in National Patch Module.\n\n
\nFixing problems with Inpatient List.\n\n
\nSee Description in National Patch Module.\n\n
\nKIDS Build for DG*5.3*372\n\n
\n \n Patch DG*5.3*286 addresses the Patient Inquiry issue noted in NOIS\n TAM-0799-31096.\n \n Scheduled Admit data was being lost at the $$OKLINE(17) page break. The\n "X" variable, holding the Scheduled Admits data was being overwritten\n whenever at the ^DIR call used to create the page break. The situation\n was corrected by "newing" the "X" variable at the OKLINE call.\n\n
\nThis patch addresses the issue that is described in the following NOIS:\nShould either of the two Database Server calls fail, a message will be\nsent to the VistA mail group "DGEN ELIGIBILITY ALERT" and the HEC mail\ngroup "ELIGIBILITY ALERT". This will allow the remaining records in the\nbatch to be processed.\n \nThe following messages will be returned when the Purple heart information\ndid not file correctly:\n \n Unable to update Purple Heart Data\n Unable to update Purple Heart History\n SLC-0401-51241: ERROR: EDITPH1+7^DGRPLE:1\n \nThis error resulted from processing an ORU-Z11 transmission from the HEC.\nWhen the record fails to update, the error "undefined variable\n^DPT(DFN,.53)" causes the ORU-Z11 transmission to stop, and the remaining\nrecord in the batch are not processed.\n \nThe FileMan DIE calls have been replaced with Database Server calls.\n\n
\nCorrecting the Medicaid number display in the Insurance data screen.\n\n
\nSee NPM for description.\n\n
\nPlease refer to Patch DG*5.3*344.\n\n
\nPlease see the National Patch Module in Forum for description of this patch.\n\n
\nThis will resolve issue with the ability of an active lodger to be\nDispositioned. \n\n
\nDescription:\n \nCorrected by using formatted SS# whenever Primary Long ID missing. If no\nSS# found, "No ID found" notation will print.\n============\nPatch DG 287 addresses NOIS WRJ-0100-12175 issue dealing with the Patient\nWristband Print. It was found that for selected patients, specifically\nTRICARE, the PID was not printing on the wrist band.\n \nIt was found that due to file definition for some patients (ie. TRICARE),\nthe Primary Long ID was not set consistent with the other categories thus\ncreating a missing ID.\n\n
\nCORRECTION TO DGSEC ROUTINE FOR PATIENT LOOKUP\n\n
\nSee patch DG*5.3*378 in the National Patch Module for description of this\nbuild.\n\n
\nPATIENT DATA REVIEW - NAME COMPARISON\nRefer to patch DG*5.3*384 in the FORUM Patch Module for a complete\ndescription.\n\n
\nKIDS distribution of the DHCP portion of the Veteran Identification Card\n(VIC) Project.\n \nThe changes included in this patch are described in the description of\npatch DG*5.3*73 in the National Patch Module.\n\n
\nThis patch will install a new version of routine DGRUGDS. The DGRUGDS\nRAI ward, the user will be allowed to make another selection and no HL7\nA01 Admit message will be transmitted for the non-RAI patient. If the\nselected patient was an RAI-ward patient but currently inactive (for\nexample, ASIH), no HL7 A01 Admit message will be created and the user may\nselect another patient if desired, or quit.\n \n \n \n.\nroutine does the data seeding of patient data in the RAI/MDS\nCOTS system. HL7 A01 Admit messages are created for patients\ncurrently active in wards assigned to the selected division. \n \nThis version will also allow the user to select individual or multiple\npatients currently active in RAI designated wards. If the patient is\nactive in an RAI ward, an HL7 A01 Admit message will be created\nand sent to the RAI/MDS COTS system. If the selected patient is not in an\n\n
\nPATIENT SELECT CRITERIA FOR CPRS REMOTE DATA VIEWS\nRefer to patch DG*5.3*392 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee national patch module for description.\n\n
\nNON-TREATING PREFERRED FACILITY CLEAN UP\n\n
\nLegacy Sites do not Check for MPI.\n\n
\nThis build corrects a problem in the DGEN339 routine when sending more \nthan 1000 veteran merge records to the HEC Production account.\nTransmissions of fewer than 1000 veteran records will not see the error.\n\n
\n1997 Means Test Threshold update patch. See National Patch Module for\nfurther details.\n\n
\nSee national patch module for description.\n\n
\nSee patch DG*5.3*351 in the National Patch Module for description of this\nbuild.\n\n
\nREMOVE EXECUTE ON OPEN PARAMETER FIELD.\n\n
\nSee patch DG*5.3*395 in the National Patch Module for description of this\nbuild.\n\n
\nReport crashes due to storage error in memory. Moved ICD9 codes to ^TMP.\n\n
\nSee national patch module for description.\n\n
\nSee national patch module for description.\n\n
\nDRG REPORTS & OPTIONS\n\n
\nSee National Patch Module for description.\n\n
\nThis patch prevents selecting those INSTITUTION entries that has no\nStation Number as patients' Claim Foler Location.\n\n
\nPatch to fix problem with Compiled Templates in the DG Namespace\n\n
\nThe changes included in this patch are described in the description of\npatch DG*5.3*397 (Mill Bill - LTC/Visit/Medication Co-Pay) in the National\nPatch Module.\n\n
\nThis patch adds a new edit check validating the Suffix field in the\nPTF record contains 'PA' if the discharge treating specialty is\none of the PRRTP specialty codes.\n\n
\nSee patch description for patch DG*5.3*429 in national patch module.\n\n
\nSee NPM for description.\n\n
\nPATIENT MPI/PD DATA INQUIRY RETRIEVAL\nRefer to patch DG*5.3*414 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch changes the PTF quarterly census closeout date to the 19th of \nthe month following the census date. \n\n
\nThe changes included in this patch are described in the description\nsection of patch DG*5.3*379 in the National Patch Module.\n\n
\nCo-Pay Tests are incorrectly displaying as required for Inpatients. A\nprevious patch (DG*5.3*358) has corrected most of the menu options for\npatients who have been admitted on a domiciliary ward, and do not display\nMeans Test and Medication Co-payment Exemption messages.\n\n
\nNEW CROSS REFERENCE ON SSN\nRefer to patch DG*5.3*440 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis KIDS build contains the changes described in the national patch\nmodule under DG*5.3*80.\n\n
\nSee National Patch Module for description.\n\n
\nPlease see Patch DG*5.3*445 in the National Patch Module for description \nof this Build.\n\n
\nA new API named APLD^DGUTL2 has been created with this patch. The API\nAPLD^DGUTL2 will return the specific dates and total days for a patient's\nPASS, LEAVE and ASIH for the billing period specified. APLD^DGUTL2 will\ngenerate a -1 extrinsically if the parameters passed into the API are\ninvalid.\n\n
\nSee national patch module on FORUM for description.\n\n
\nHardship Information sharing between sites.\n\n
\nThe changes included in this patch are described in the description\nsection of patch DG*5.3*443 in the National Patch Module.\n\n
\nSCREEN TREATING FACILITY LIST\nRefer to patch DG*5.3*448 in the FORUM Patch Module for a complete\ndescription.\n\n
\nAddresses NOIS V19-0202-50263 and others that are closed.\n\n
\nChange priority rule for priority group 3.\n\n
\nThis patch is in response to Item #22 in the Rossio Report. In the area\nof Means Test (MT) Deficiencies, Item #22 required that the Veterans\nHealth Administration (VHA) identify best practices for means testing and\nacquiring veterans' signatures at the local level and explore the\npromulgation of these best practices throughout the system. This patch\nadds a site controllable parameter to post a means test completion\nbulletin to a local mail group.\n\n
\nSee National Patch Module for description.\n\n
\nPlease see Patch DG*5.3*332 in the National Patch Module for description of \nthis Build.\n\n
\nDistribution of mail group for the Austin web-based Missing Patient\nRegister application.\n\n
\nVistA HL7 Upgrade v1.5 to v1.6 - VAMC side\n\n
\nAssociated patches: (v)SD*5.3*262 install with patch `DG*5.3*447'\ninstallation instructions.\n \n \nRemote Procedures\n-----------------\n \nDGWPT BYWARD\n Returns a list of patients currently residing on a specified ward\n location.\n \n (v)XU*8*234 install with patch `DG*5.3*447'\n \nDGWPT CLINRNG\n Returns a list of selectable options from which a user can choose\n a date range for appointments.\n \nDGWPT DFLTSRC\n Return user's default patient list source.\n \n \nDGWPT DIEDON\n (v)YS*5.01*71 install with patch `DG*5.3*447'\n Returns date of death if patient has expired. Otherwise returns 0.\n \nDGWPT SAVDFLT\n Saves user's preference for default list source.\n \nDGWPT SELCHK\n Returns a 1 if the patient record is flagged as sensitive, otherwise\n returns 0.\n \nDGWPT SELECT\n \n RPC to return key information on a patient as follows:\n 1 2 3 4 5 6 7 8 9 10 11 12 13 14\nNAME^SEX^DOB^SSN^LOCIEN^LOCNM^RMBD^CWAD^SENSITIVE^ADMITTED^CONV^SC^SC%^\nICN\n \nDGWPT TOP\n Returns the last selected patient by the defined user.\n \nDGWPT1 PRCARE\n Return primary care information for a patient in the format:\nThis patch is released in support of Mental Health Assistant GUI patch \n VAL=Primary Care Team^Primary Care Provider^Attending\n \n \nAssociated NOIS:\n================\nNONE\n \nTest Sites:\n===========\nMinneapolis VAMC, MN\nYS*5.01*71. Patch DG*5.3*447 contains the following Remote Procedures and \nSalt Lake City HCS, UT\nVA Health Care Network Upstate New York\nVA N. Florida/S. Georgia Veterans HCS\nVA North Texas HCS\n \n \nROUTINE SUMMARY:\n================\n The second line of the routine now looks like:\n \nroutines.\n <tab>;;5.3;Registration;**[patch list]**;Aug 13, 1993\n Checksum Values\n \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \n \n DGLP3USR N/A 5761869 447\n DGQPT N/A 18835443 447\n DGQPT1 N/A 17196488 447\n \n DGQPT2 N/A 2845976 447\n DGQPTQ1 N/A 9659046 447\n DGQPTQ11 N/A 13181943 447\n DGQPTQ2 N/A 11842536 447\n DGQPTQ5 N/A 13189119 447\n DGQPTQ6 N/A 9925723 447\n DGWPT N/A 3719607 447\n DGWPT1 N/A 7065014 447\n \n \nPlease refer to the information contained in the Mental Health patch for \nInstallation Instructions:\n==========================\n \n Instructions for installation of the software are included in the \n Mental Health Assistant (MHA) patch YS*5.01* 71.\n\n
\nSee National patch module for detailed description.\n\n
\nREMOVE TREATING FACILITY SCREEN\nRefer to patch DG*5.3*449 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee National Patch module for description of patch.\n\n
\nSee national patch module on forum for description.\n\n
\nThis patch addresses a problem with a Patient NAME changed to a number when\na future MEANS TEST is executed and then LOAD PATIENT DATA is used.\n\n\n
\nThis patch addresses PTF closeout for census problem that contributes to\nduplicate census records.\n\n\n
\nKIDS Build for DG*5.3*431\n\n
\nSend MPI seed data to the HEC.\n\n
\nSee patch DG*5.3*387 in the National Patch Module for description of this\nbuild.\n\n
\nThis patch adds the HOSPICE Nursing Home Care as a new specialty to\nthe SPECIALTY (#42.4) file. An entry in the FACILITY TREATING SPECIALTY (#45.7)\nis optional.\n\n\n
\nThis patch will address the problem when there are too many patient\nmovements on one admission and the 'string too long' error is created.\nA local array instead of a single variable will be used in DGUTL2 routine.\n\n\n
\nStop redundant HL7 messaging.\n\n
\nSee national patch module for complete description.\n\n
\nThis patch is being distributed to update the APSOD xref on the \nDate of death field. The kill logic is being updated to notify\noutpatient pharmacy when a date of death is deleted.\n\n
\nNEW MESSSAGE STRUCTURE - PHASE 1\nRefer to patch DG*5.3*428 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nWithin several HL7 messaging programs there is a call to invoke the \nprocess to send an acknowledgment back to the HEC that is using the \nwrong variable. Also several programs do not clean up the temporary \nglobal - ^TMP prior to and/or after creation of a query.\n\n
\nNEW MESSAGE STRUCTURE - PHASE 2\nRefer to patch DG*5.3*474 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch addresses Geographic Means Test as a new Means Test Indicator\n Change: 'AN' WILL STAND FOR 'CAT A NSC'.\n To: 'AN' WILL STAND FOR 'NSC MT COPAY EXEMPT'.\n \n Change: 'C' WILL STAND FOR 'CAT C'.\n To: 'C' WILL STAND FOR 'MT COPAY REQUIRED'.\n \n Add: 'G' WILL STAND FOR 'GMT COPAY REQUIRED'.\n \nThe algorithm logic in PTF for determining the means test indicator in \nroutines DGPTUTL and DGPTFVC1 have been modified to include patients with \nvalue used in PTF. This new value will be added to the Means Test\nGMT status. A new API ($$PA^DGMTUTL) is used to determine whether a\nstatus of 'pending adjudication' will be 'mt copay required' or 'gmt copay\nrequired'.\n \nAustin edit checks have been modified in routine VAFHLZIR to include the\nnew value of 'G' when validating means test indicators for transmissions\nto Austin.\nIndicator (#10) field of the PTF (#45) file. The new value will be titled\nGMT COPAY REQUIRED and have the code value of 'G'. In addition, two means\ntest indicators will have their descriptions changed to reflect Enrollment\nchanges to CAT A and CAT C Copay status. The following Data Dictionary\nchanges will be made to the Means Test Indicator (#10) field of the PTF\n(#45) file:\n \n\n
\nGMT THRESHOLDS UNDEFINED\n\n
\nModify the ADDRESS CHANGE DT/TM (field #.118) of the Patient (#2) file\nfrom a Time required field to a Time not required field.\n\n
\nCLEANUP RECORDS FROM THE 408.12, 408.21, & 408.22 FILES THAT WERE \nPARTIALLY STUBBED IN BECAUSE OF AN HL7 VER. 1.6 PROBLEM. \nNOIS:NIN-0802-40682\n\n
\nENROLLMENT SUB-PRIORITIES\n\n
\nHL7 segment builder changes.\n\n
\n \n \n \n \nHIPAA CONFIDENTIAL ADDRESS.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*113 in the National Patch Module.\n\n
\nFix undefined error from DGBT BENE TRAVEL SCREEN (Claim Enter/Edit).\n\n
\nAddress's the following NOIS:\nthe ANNUAL MEANS TEST File (#408.31), but the MT from the PATIENT file is\ndisplayed. This patch fixes that inconsistency.\n \nThis patch will also install a cross-check which will update the CURRENT \nMEANS TEST STATUS field, if necessary, during patient lookups.\nCLL-0802-41804\nSLC-0502-52697\n \nThis patch fixes the manner in which the current means test is displayed \nduring a patient inquiry by calling the current means test API instead of \nusing the CURRENT MEANS TEST STATUS field from the PATIENT File (#2). \nThis field is not always in-synch with the patient's current MT from the \nANNUAL MEANS TEST File (#408.31). All processing is done on the MT from\n\n
\nThis patch contains changes to various patient data HL7 segment \n \nHL7 routines are modified as follows:\n \nVAFCA04 - ROL segment is added (inpatient only).\n \nVAFCADT2 - ROL segment is added to transmissions: \n A01 - Admission A11 - Cancel Admission\n A02 - Transfer A12 - Cancel Transfer\n A03 - Discharge A13 - Cancel Discharge\n A08 - Treating Specialty Update\nbuilders required in the Registration and PTF software for the collection \n \nVAFCMSG3 - ROL segment is added (inpatient only).\n \nThe ROL segment will be transmitted for the required attending physician \nand may include the ROL segment for the primary (admitting) physician \n(not required). The transmission component in the ROL segment will send\nthe letter 'A' signifying Admitting provider and the letter 'T' signifying\nthe Attending provider.\n \nADDITIONAL INFO ON POST-INIT ROUTINE DG53484P:\nof Primary (admitting) provider. These changes will be sent to the \n---------------------------------------------- \nDG*5.3*484 distributes a post-init routine that changes the name of the\n"NPTF" application in the HL7 APPLICATION PARAMETER file (#771) to "NPTF-\n484". This change allows the proper collection of the ADT ROL segments \nat the National Patient Care Database.\n \nRoutine DG53484P can be deleted after successfully completing the patch.\nAustin Automation Center for storage in the National Patient Care \nDatabase.\n \n \nChanges to the HL7 segment builders:\n-------------------------------------\n\n
\nFIX MT UPLOAD PROBLEM\n\n
\nPatient name standardization patch. \n\n
\nFix Patient Look-Up Problem\n\n
\nnois ISA-0403-11105\n\n
\nSee National Patch module for description of patch.\n\n
\nGeographic Means Tests was introduced changing the naming conventions of\n replace Category 'A' Veteran with MT Copay Exempt; replace Category\n 'C' Veteran with MT Copay Required; add GMT Copay Required.\n \n2. Patients with a Pending Adjudication Means Test status will display\n whether the pending adjudication is for MT Copay Required or GMT Copay\n Required, with the latter determination being displayed.\n \n3. Title of 'Means Test Indicator's' under the parameters display will be\n replaced with 'Means Test Copay Applicability'.\n \nCategory A and Category C Means Tests. This patch will update the Gains\n4. Title of 'Means Test Display' under the parameters will be replaced \n with 'Means Test Copay Applicability Display'.\nand Losses (G&L) Sheet with modifications needed to conform to these\nchanges in the display of Means Test status.\n \nChanges will include the following:\n-----------------------------------\n \n1. The legend diplayed when listing Means Test statuses for patients will\n\n
\nHIPAA Confidential Address changes.\n\n
\nGEOGRAPHIC MEANS TESTING - PHASE II\n\n
\nMODIFY HOW PATIENT SENSITIVITY IS CHANGED\n\n
\nMPI CHANGES - ITERATION 1\nRefer to patch DG*5.3*505 in the FORUM Patch Module for a complete\ndescription.\n\n
\nEmergency patch to facilitate the patient file conversion.\n\n
\nPATCH: DG*5.3*495\n \nSUBJECT: FIX MT NO LONGER REQUIRED ISSUE\n\n
\nSee patch description for DG*5.3*487.\n\n
\nDG PRE-REGISTRATION OPTIONS\n\n
\nLTC Copayment Phase III\n\n
\nThe 55 INCOME DATA MISSING inconsistency results if none of the income \nThis patch updates the business rules for the 55 INCOME DATA MISSING \nerror to bring the consistency checker in line with the checks being \nperformed by the means test requirements.\nquestions on screen 9 of the Load/Edit Patient Data screen are answered \nand the patient has not agreed to pay the deductible. Sites are \nindicating that they are getting the 55 INCOME DATA MISSING error for \nveterans who do not require income information. Unless they enter a "0" \ninto the income fields, they cannot clear the error. By entering a "0" \nin these cases, they feel the veteran's income data is misrepresentative \nand that they should not have to enter a "0" to clear this error.\n \n\n
\nKilled DG20NAME after call to NCEDIT at linetag 101.\n\n
\nPATIENT DATA REVIEW FIXES & ENHANCEMENTS\nRefer to patch DG*5.3*477 in the FORUM Patch Module for a complete\ndescription.\n\n
\nUR 72 HOUR BULLETIN\n\n
\nFIX VISTA VIEW PAST MEANS TEST SCREEN 2-4\n\n
\nThe report included in this patch is the follow up to Patch DG*5.3*512,\nprocess, where at least one PTF record within the Fiscal Year must include\na valid Means Test status for the patient. The patient will be included\non the report only if ALL the patient's PTF records within the date range\nselected have a current MT Status Indicator of 'U'. This will focus the\nlist on patients who have no valid MT status in the National Patient Care\nDatabase (NPCD) for the date range chosen.\nwhich was a KIDS build released on May 29, 2003. \n \nDue to the changes brought in by patch DG*5.3*512, reports are needed to\nidentify patients who require a Means Test and who have had inpatient\nepisodes of care transmitted with a MT indicator of U. A new report \noption called PTF Records Transmitted with MT Indicator of U [DG PTF TRANS\nMT EQUAL U RPT] will be added to the PTF Output Menu [DG PTF OUTPUT MENU].\nThis report conforms to requirements related to the VERA allocation\n\n
\nSee National patch module for patch description\n\n
\nPlease refer to patch DG*5.3*425 in the National Patch Module for a \ncomplete description of this patch.\n\n
\nThis patch fixes a problem with IN5^VADPT returning old admissions for \noutpatients.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPlease see the National Patch Module for details\n of the enhancements included in this patch.\n\n
\nDescription:\n===========\n \nThis patch adds to the print utility routine DGUTQ code which will allow\nforce queuing of reports.\n \nThis patch addresses the following NOIS message(s):\n---------------------------------------------------\nCMO-0600-41899 CANCEL CLINIC AVAILABILITY GIVES END OF FILE ERROR\n\n
\nThis is the cleanup of the Name Component file #20.\n\n
\nThis patch avoids an undefined error which is preventing users from\nadmitting patients in certain circumstances, and prevents orders from\nbeing released multiple times. \n\n
\nNEW MESSAGE STRUCTURE - PHASE 3\nRefer to patch DG*5.3*479 in the FORUM Patch Module for a complete\ndescription.\n\n
\n \nSee national patch module DG*5.3*82 for details of this patch.\n\n
\nSee National Patch Module for description.\n\n
\nProblems in registration system caused by filter for inpatient roster, \nunclear description in period of service field, use of pseudo SSN s in \nclaim number and error entering more than 3 surgeries in a day.\n\n
\nPlease refer to Patch DG*5.3*533\n\n
\nFixes for NOISes TAM-0303-31335, ISA1098-12507, DAN-0700-40870, NOL-0998-70264, SFC-1202-61040.\n\n
\nThis patch will modify the SCREEN and INPUT TRANSFORM for setting the ADV\ncross-reference on the INSTITUTION file (#4) pointer in MEDICAL CENTER \nDIVISION file (40.8) field 7.\n\n
\nTHIS PATCH CORRECTS A LOCK PROBLEM WHEN MULTIPLE PATIENTS ARE EDITTED, \nA NULL SUBSCRIPT ERROR REPORTED IN ROUTINE VAFHPURG, AND A PTF \nTRANSMISSION PROBLEM WHICH FAILED TO INITIALIZE THE LINE COUNT VARIABLE.\n\n
\nThis patch contains a couple of cleanup routines to remove duplicate and \nbad Means Tests from the ANNUAL MEANS TEST file #408.31.\n\n
\nThis patch fixes various NOIS calls. See NPM for details.\n\n
\nSee National Patch Module for description.\n\n
\nFIX DISPLAY ON SCREEN 4 FOR MEANS TEST VIEW\n\n
\nThe Patch (DG*5.3*546) fixes problems related to Insurance Data, Primary and\nSecondary IDs.\n\n
\nFix to ADT/HL7 messaging\n\n
\nThis allows pick lists to return entries beyond those that match the \nentering a patient or a bill number.\nuser's input exactly. With the fuzzy lookups in place a bill number\nsuch as K301EL2 may also return patients whose names begin with KEL.\nThis has an unexpected result on the AR options when the user\nentered bill numbers.\n \nWith this patch an Integration Agreement for the Accounts Receivable \nsoftware package has been approved, this will allow for the correction to \nthe patient fuzzy lookup that has caused sites to have problems when \n\n
\nDate of Death Modifications to ZPD segment\n\n
\nThis patch fixes reported problems with the DG SCHED AMIT option, MST\nSummary Report, the Detailed Demographic Report, Fee Basis PTF records \nwith no admit time, CUM ADC Totals on the BSR and printing a blank\nlines for 'DON'T DISPLAY' Totals on the BSR.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nSee National Patch module for description.\n\n
\n \n \nMessaging changes for HIPAA confidential address communications\n\n
\nFixes assorted backlog NOIS calls.\n\n
\nREMOVAL OF WORKLOAD CAPTURE FROM REGISTRATION\n\n
\nFix for blank level 2 and higher totals for Cum ADC on the Bed Status \nReport caused by DG*5.3*529.\n\n
\nUpdates record in file 407.7.\n\n
\nSee National Patch Module for description.\n\n
\nrestores routine DGPTFTR to the version that existed \nprior to install of DG*5.3*530.\n\n
\nCORRECT FUTURE APPOINTMENTS ON DEATH BULLETIN\n\n
\nTRIGGER UPDATES\nRefer to patch DG*5.3*575 in the FORUM Patch Module for a complete\ndescription.\n\n
\nREMOVAL OF AMPIZZ AND ATSSN CROSS-REFERENCES - MPI CHANGES ITERATION 2\nRefer to patch DG*5.3*589 in the FORUM Patch Module for a complete\ndescription.\n\n
\nCombat Veteran Phase II\n\n
\nFIX LINKED FIELD FOR MT/CP TESTS. REMOVE LINK WHEN A MT OR RXCT IS \nDELETED.\n\n
\nACCESS TO PAI, CHECK IN LODGER FIX, DELETING DUMMY REGISTRATION.\n\n
\nNew VistA fields for 1010EZ Phase 2.5 enhancements.\n\n
\nThis patch will prevent the DG MEANS TEST SUPERVISOR MENU's Purge \nDuplicates option from purging IVM Converted Tests that appear to be bad\nduplicates. These tests were flipped to NOT PRIMARY and this utility\nwill flip them back to PRIMARY prior to purging any duplicate Income \ntests.\n\n
\nPlease refer to patch DG*5.3*571 in the National Patch Module for a \ncomplete description of this patch.\n\n
\nSee the Patch Description for DG*5.3*572 in the FORUM patch module.\n\n
\nUpdates to Registration Routines\n\n
\nPatient File cleanup and $(G) to DGPMVDD\n\n
\nThis build contains routines to cleanup various failed Means Test Uploads \nand duplicate Means Test purges.\n\n
\nSUPPORT FOR HDR\nRefer to patch DG*5.3*520 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch repairs certain Patient Record Flag displays when\npatient lookups are done from within ScreenMan.\n\n
\nThis patch concerns a situation where an incomplete patient record\nis temporarily created when adding a new patient, and incorrect\ntext in the definition of an option. \n\n
\n1. Due to sites experiencing performance issues, modifications were made \n to have tasks removed from Taskman after completion.\n2. Modification to prevent duplicate ISO bulletins and log entries \n created during the addition of a spouse or dependant.\n\n
\nAdd Clinical Reminder index cross-references to PTF.\n\n
\nSee National Patch module for description.\n\n
\nThis patch is concerned with identifying test patients.\n\n
\nThis patch will incorporate the changes required by the FEE BASIS \nEncapsulation Project. No functionality will be introduced.\n\n
\nPatient Safety issue regarding iens with decimals; \nroutines with undefined variables\n\n
\nPatch is in support of Pub. L. 107-103, section 505.\nThis patch will add new fields to the patient file and new options\nthat will allow the tracking of Fugitive Felon Information as provided\nby the appropriate sources and provides both reporting and inquiry \nmechanisms.\n\n
\nThis patch is in support of the Billing Replacement - Encapsulation \nwhich had been retrieving insurance information from either the INSURANCE \nFile (#36) or the INSURANCE TYPE sub-file (#2.312) of the PATIENT File \n(#2), has been modified to use the $$INSUR^IBBAPI API call originally \nreleased with patch IB*2*256, IB INSURANCE API.\nProject. The objective of this project is to standardize existing VistA \nIntegrated Billing and Accounts Receivable functionality so that a new \nCOTS billing/AR product may be effectively integrated into the VistA \nsuite. This will be accomplished by replacing direct IB and AR touch \npoints with standard authorized API's available to all VistA packages. \n \nThis patch will replace all current direct access of Insurance \nInformation in the VistA Registration package with a new API call. Code \n\n
\nThis patch provides a list\nof records with bad SSNs, fixes the sort template for NPTF reports,\nand reformats the attending MD name in HL7 segments. \n\n
\nSee National Patch Module for description.\n\n
\nThis patch introduces software changes for NOIS issues reported within the\nPatient Records Flag module that is part of the Registration V. 5.3 \npackage.\n\n
\nDate of Death Enhancements\n\n
\nOBSOLETE PROTOCOL CLEANUP\nRefer to patch DG*5.3*639 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPTF problem with Rendering Provider for CPT updates. Inactive providers \nwith inactive date later than CPT record date are not allowed as valid\nprovider.\n\n
\nDisplay Bad Address Indicator at patient lookup.\n \nReport.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*130 in the National Patch Module.\n\n
\nThis patch concerns a situation where the patient record has a large \nThe VDEF / Standardized Messaging team request that when the APID build\nprocess is called from the VDEF process, any "HL7 special characters" that\ncould be found in patient street address data, be encoded to HL7\nstandards.\nnumber of aliases. The HL7 message to update the MPI was being built\nincorrectly and causing an exception on the MPI in cases where the patient\nrecord has several aliases. The MPI was then not able to process the\nmessage and update the record. \n AND\nThe MPI DQ Team requests that the ALIAS SSN (2.01,1) field be added to \nthe Display Remote Patient Data Query [RG REMOTE PDAT DISPLAY] Option. \n AND\n\n
\nThis patch will remove any duplicate race entries in the 2.02 multiple\nof the patient file, and will ensure that when data is imported \nusing the Register Once Messaging (ROM) query during registration,\nthat entries in the Race and Ethnicity multiples are dynamically \nnumbered.\n\n
\nThis patch disables old VIC prompts in Registration.\n\n
\nThis patch facilitates using the VIC card in mag readers, no longer\ndisplays messages on "missing" patients, and allows PTF Fee Basis \nrecords to close.\n\n
\nPatient catastrophic edits.\ndetermined to be catastrophic).\n \n1. Two or more edits (name, ssn, dob, or sex) during the Registration \nprocess create alert to those holding the DG CATASTROPHIC EDIT key.\n2. Alerts retained for 365 days.\n3. Alert allows patient information displayed with collected data on \nreview and catastrophic edit status.\n4. Report displays alert information (going back one year) on \ncatatastrophic edits (alerts posted, alerts reviewed, and alerts \n\n
\nThis patch updates the PTF AUSTIN ERROR CODES file #45.64 and \ncorrects the output transform for the CONFIDENTIAL ADDRESS COUNTY \nfield #.14111 in the patient file.\n\n
\nCleans up dangling PATIENT RELATIONS file # 408.12 that have a bad\npointer to a bad patient or person record (field #.01 or #.03 or both)\n\n
\nThis patch is to modify the census routines to include care provided at \nnon-VA facilities.\n\n
\n1. Prevent sending blank message to Austin\n \n2. Expand DG1 segment in HL7 RAI/MDS packet to include up to 13 diagnosis\n \n3. Error during the Process Dicom Images on DIG1 with a broker error.\n\n
\nSee National Patch Module for patch description.\n\n
\nAdd asterisks to identify Insurance Buffer entries back into Screen 5\nof the Patient Load/Edit Screens. This makes use of a new field added\nto the return from Insurance Encapsulation API.\n \nThe IN1 and IN2 HL7 segment builders are modified to use the Insurance \nEncapsulation API.\n\n
\nThe patch will modify the PTF transmission message to \n include up to 13 diagnoses from the PTF.\n\n
\nAdd asterisks to identify Insurance Buffer entries back into Screen 5\nof the Patient Load/Edit Screens. This makes use of a new field added\nto the return from Insurance Encapsulation API.\n \nThe IN1 and IN2 HL7 segment builders are modified to use the Insurance\nEncapsulation API.\n\n
\nThis patch addresses the patient name lookup, cleans up variables left\nin the symbol table, allows the creation of VIC cards for patients without\na first name, backs out the changes to the CUM ADC totals on the BSR, and\ncreates cross-reference entries for test patients. \n\n
\nThis patch corrects a problem when coding the 501 or MAS screen in\n the Load/Edit PTF Data [DG PTF SCREEN] option.\n\n
\nThis patch fixes a problem with transmitting HL7 messages for outpatients,\nand corrects a system error when transmitting PTF census records to AAC.\n\n
\n1010 EZ PHASE 3.0\n\n
\nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nThis patch corrects a problem when timing out while registering collateral\npatients, when adding a patient using Fileman and updating the name\ncomponents, and when processing address data returned from the query\nto the last site treated. \n\n
\nThis patch corrects a problem with the display of the alias SSN.\n\n
\nHURRICANE KATRINA - EMERGENCY RESPONSE INDICATOR\n\n
\nThis patch corrects problems when adding patients.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*137 in the National Patch Module.\n\n
\nPlease refer to patch DG*5.3*684 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nThe purpose of this patch is to replace the PIVOT FILE DAYS TO RETAIN \nfield (#391.702) in the MAS PARAMETERS (#43) file.\nIt was discovered that field 391.702 was pointing to the same node(HL7)\nand piece(4) as the CREATE MFU FOR RAI MDS field (#391.7014).\n\n
\nPrevents error in MPI's Patient Data Review and cleans up file #391.98.\n\n
\n REQUIRED MEANS TEST WARNING DOESN'T SHOW IN CPRS\n\n
\nNEW TRIGGER AND PID SEGMENT FIX\nRefer to patch DG*5.3*648 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch covers updating of patient name components.\n\n
\nThis patch corrects problems caused when Patient Treatment file (#45)\nrecords are deleted.\n\n
\nSee NPM for description.\n\n
\nAdd cross-references to support OEF/OIF data extraction; see the\nNational Patch Module for a complete description.\n\n\n\n\n
\nHANDLING HL ENCODING CHAR IN PID 2.4\nRefer to patch DG*5.3*698 in the FORUM Patch Module for a complete \ndescription.\n\n
\n Permanent Address abort still updating DT/TM Stamp\n\n
\nPlease refer to patch DG*5.3*554 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nPlease refer to patch DG*5.3*679 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nThis patch disables the HL7 subscription\ncontrol functionality, and fixes the SERVICE ENTRY DATE [LAST] (#.326) \nfield display when using the Remote Patient Data Query.\n\n
\nPatch contains functionality for GUI Patient Lookup.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*141 in the National Patch Module.\n\n
\nFIX MEANS TEST DISPLAY\n\n
\nThis patch adds the HOSPICE Nursing Home Care as a new specialty to\nthe SPECIALTY (#42.4) file. An entry in the FACILITY TREATING SPECIALTY (#45.7)\nis optional.\n\n\n
\nThis patch updates the Multiple Birth Indicator and temporary address,\ncorrects a date validation API, updates the patient name components and\ncorrects the alias SSN.\n\n
\nFIX FOR MASTER PATIENT INDEX NAME SYNCHRONIZATION ISSUE\nRefer to patch DG*5.3*711 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch fixes a problem with collateral patient names, the zip codes\nof emergency contacts and designees, the data dictionary of the \nINPATIENT CPT CODE file (#46) and the 'Edit Census Date Parameters'\noption.\n\n
\nSee National Patch Module for description.\n\n
\n This patch deals with non-VA PTF census problems, the inability to\nselect certain ICD9 codes on the 501 screen of PTF Load/Edit, and a \nsystem error when transferring patients. \n\n
\nThis patch allows the patient security check to account for proxy users,\nand protects a system variable before displaying patient record flags.\n\n
\nPlease refer to patch DG*5.3*718 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nPlease refer to patch DG*5.3*673 in the National Patch Module for a \ncomplete description of this patch.\n\n
\nThis patch fixes a problem with the combat vet field used in screen 801\nin the PTF Load/Edit option, fixes the transmission date on retransmitted\ntransactions, permits closing a record when the patient has a single\nlegal name, and refines the handling of the PTF census date file.\n\n
\nSee National Patch module for description.\n\n
\n This patch permits deleting patient's middle name or suffix and \n the multiple birth indicator (MBI). It also will not consider an MBI\n change as part of a possible catastrophic edit.\n\n
\nPlease refer to patch DG*5.3*689 in the National Patch Module for a \ncomplete description of this patch.\n\n
\nAdd Field Triggers for ORU~Z07s\n\n
\nSee the Patch Description in the Forum Patch Module for DG*5.3*716.\n\n
\nUndefined MERGE+39 Pgm DGENUPL4\n\n
\nIRR Method and Help Text Updates\n\n
\nAdd ^ to file 408.31 field .23-SOURCE OF INCOME TEST and\nthe sites. The only way to block the users from editing these\ntwo fields is to change the data dictioanry to make the fields\nun-editable.\nfield 2-PRIMARY INCOME TEST FOR YEAR\nto maintain data integrity of the records in the Annual Means Test File\n \nThere are sites that are editing two fields using Fileman to allow\ntests to be modified that should not be edited. These fields are\nPRIMARY INCOME TEST FOR YEAR (field 2) and SOURCE OF INCOME TEST\n(field #.23) in the Annual Means Test file #408.31. Some of the MT\nReverasals in IVM 2.9 are due to manual editing of these records at\n\n
\nPlease refer to patch DG*5.3*650 in the National Patch Module for a\ncomplete description of this patch.\n\n
\n \nDelete REQUIRED means test from deceased patients.\n\n
\nPlease see National Patch Module for description.\n\n
\nPlease refer to the National Patch Module for a description of this patch.\n\n
\nPlease refer to the National Patch Module for a description of this patch.\n\n
\nThis patch corrects a system error when adding rated disabilities,\ndata exceptions in the MPI for the "date last treated", printing of \nthe full SSN on the G&L report, and not generating UR admission \nbulletins on ASIH transfers. \n\n
\nTRIGGER FOR 1010EZ COMBAT AFTER 11/11/98\n\n
\n This patch resolves problems related to the patient's address, the \nemergency contact work phone, the principal investigator report, \nand the patient name change bulletin.\n\n
\nPOW STATUS NOT TRANSFERRING TO VETERAN'S ID CARD\n\n
\nThis patch contain routines that have been modified\nto call the Scheduling Encapsulation API SDAPI^SDAMA301\ninstead of referencing the global for appointment data retrieval. \nThis patch also addresses the error handling when an error occurs.\n\n
\nSee National Patch Module for description.\n\n
\nFIX UPLOAD OF CLAIM FOLDER LOCATION\n\n
\nSTOP UPDATE OF ADDRESS IN PTF\n\n
\n \n \nDG INVALID STATE/COUNTY REPORT ERRORS AFTER INSTALL OF DG*5.3*694.\n\n
\nPlease refer to the National Patch module for a description of the changes\nincluded in this patch.\n\n
\nFix IN1 segment builder\n\n
\nAdd CHDR Security keys\n\n
\nThis patch corrects certain dates in the PXRMINDX index,\nan unnecesary "incomplete" message, and turns on audit for the ICN.\n\n
\nENHANCEMENT TO VISTA PATIENT UPDATE MESSAGING\nRefer to patch DG*5.3*707 in the FORUM Patch Module for a complete \ndescription.\n\n
\nThis patch corrects DRG reports, PTF record search reports, the PTF close \nout edit for surgical codes, replaces a system error with an \nan error bulletin, and determines the proper variable to use\nwhen doing certain ICD9 code lookups. \n\n
\n1998 Means Test Threshold update patch. See National Patch Module for\nfurther details.\n\n
\nPlease see the national patch module for a description of the changes\nincluded in this patch.\n\n
\nPlease refer to patch DG*5.3*761 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nUPDATE THE ALIAS MULTIPLE\nRefer to patch DG*5.3*756 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the national patch module for a description of the changes\nincluded in this patch.\n\n
\nPlease refer to patch DG*5.3*755 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nSee National Patch Module for description.\n\n
\nThis patch fixes an invalid input array entry\nerror that occurs when using the DGEN APPTS,NOT ENROLLED \nUpcoming Appointments without Enrollment option.\n\n
\nThis patch replaces ^%DTC calls in VADPT* routines, references to HCFA, \nchanges Widow/widower entry and corrects Eligibility Inquiry and mothers \nmaiden name in PID segment.\n\n
\nThis patch corrects the following:\nProblem deleting PTF record when procedure has been deleted.\nSCI output on Registration view to show full value\nDefault city choice in Registration to use full City name instead of \nabbreviation.\n\n
\nThis patch fixes the listing of future/pending appointments on screen 14\nof the Load/Edit patient data option.\n\n
\nThis patch fixes the request of requiring the Source of Notification field\nto be answered when a Date of Death is issued. \n\n
\nDISABLE SOME Z07 CONSISTENCY CHECKS\n\n
\nCorrecting missing Treating Specialty code in PTF Census transmissions.\n\n
\nSee the National Patch Module (NPM) entry for a description of the changes\nincluded with this patch.\n\n
\nSee national patch module for complete description.\n\n
\nThis patch addresses the following:\n- corrects hours and minutes of the 'date last treated' for MPI\n- requires precise dates for the Confidential Address Start and\n End dates\n- retires the Patient Data Review (PDR) functionality in MPI \n\n
\nUpdate to RELIGION file (#13).\n\n
\nThis patch changes the default for the prompt "Do you wish to proceed\nwith the Means Test" from "YES" to "NO" when the prompt displays for option\noptions in the pre-registration menu.\n\n
\nThis patch allows for data entry changes to correctly calculate bilateral \nknee and hip procedures.\n\n
\n \nModified DISCHARGE DATE field (#70) and DISCHARGE SPECIALTY \nfield (#71) of the PTF file (#45).\nUpdated technical descriptions for LOSING SPECIALTY field (#2) and the\nMOVEMENT DATE field (#10) of the 501 multiple subfile (#45.02) of the PTF\nfile (#45).\nUpdates eligibility for an ASIH movement. \nRecreated the trigger for the LOSING SPECIALTY field (#2) of the \n501 multiple subfile (#45.02). \n\n
\n This patch addresses issues regarding the patient sensitivity/security\ncheck, and the check for same last name and last 4 digits of SSN.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*91 in the National Patch Module.\n\n
\nVIC HL7 LOGICAL LINK UPDATE - VIC NCMD\nThis Routine will only be run once.\n \nPURPOSE: Update 'VIC NCMD' Logical Link for TCP/IP transmissions. The \ncurrent definition has a hard coded IP Address. The existing Data will \nbe removed and replaced by a DNS domain name in HLCS(870\n \nThe routine will find the IEN by looking at HLCS(870,'B','VIC NCMD',ien\nThen the first data piece ('^') will be updated with the new data.\n \n\n\nThis patch makes field #6 USE FOR Z07 in file #38.6 IN\nINCONSISTENT DATA ELEMENTS undeditable. It also updates the\ndata to correspond with the values that were sent out with the\nVHA Directive.\n \nThis patch also modifies the VADPT0 routine.\n\n
\nPTF PSEUDO DISCHARGE FIX, MISSING ROUTINE FIX, MAILMAN MESSAGE FIX FOR PDX\n\n
\nPatch for ENROLLMENT VISTA CHANGES TO SUPPORT ESR (RELEASE 2).\n \nSee the Patch description for DG*5.3*688 as documented in the Forum Patch \nModule.\n\n
\nPROJECT 112/SHAD.\n \nPIMS REGISTRATION\n PTF CHANGES\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nDG*5.3*786 does the following:\n- modifies the ROUTING LOGIC in the DG HOME TELEHEALTH ADT-A03 CLIENT \n protocol. \n- modifies the DNS DOMAIN for the HL7 LOGICAL LINKS for HOME \n TELEHEALTH.\n- recompiles the input template for the 501 screen. \n- modifies the data dictionary for the CPT MODIFIER field (#.03) in the\n INPATIENT CPT CODE file (#46). \n- corrects routine DGRPCF to increment the file header for the \n INCONSISTENT DATA file (#38.5) only when a record is added.\n- modifies routines DGRRLUA and DGRRLU6 to account for providers whose\n names contain apostrophes.\n- modifies the ADGRU09 cross reference in the PATIENT MOVEMENT file\n (#405) to fix a problem when using ^DIK to delete certain records.\n\n
\nPlease refer to the patch description in this patch on FORUM\n\n
\nThis patch corrects the erroneous calculation of the CV End date on the\nUnsupported CV end date report. The code was changed from calculating a\n2 year window to calculating a 3 or 5 year window. Please refer to the\nnational patch module on Forum for a full description of the problems\ncorrected with this patch.\n\n
\n \nADD FILE 2 X-REFS: \nEMAIL ADDRESS, CELL PHONE NUMBER, AND BAD ADDRESS INDICATOR\nRefer to patch DG*5.3*712 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch addresses a request which supports the Pharmacy Benefits\nare accessed and updated. The six fields are:\n SEX (#.02)\n PRIMARY ELIGIBILITY CODE (#.361)\n CURRENT MEANS TEST STATUS (#.14)\n CURRENT ENROLLMENT (#27.01)\n PROVIDER (#.104)\n DATE ENTERED INTO FILE (#.097)\nManagement (PBM)Extracts Enhancement #3 project. In order to allow the\nretransmission of only those patients who have had demographic updates,\nOutpatient Pharmacy V. 7.0, Inpatient Medications V. 5.0, Registration\nV. 5.3 and Pharmacy Data Management V. 1.0 were modified to build an\nentry for re-transmission in PBM PATIENT DEMOGRAPHICS File #59.9.\n \nThis patch will introduce six (6) new fields to the DG Field Monitor Event\ndriver. This will enhance the PBM extract process anytime these fields\n\n
\nThis patch corrects the following:\nEnsures that the Registration package will store long patient \nnames properly. \nCatastrophic edit warning will not be displayed if only the \npseudo Social Security Number is being changed. \nCatastrophic edit warning will be displayed if two or more edits to any\npotential CE field(patient name, ssn, dob, sex) have been done on the \nsame day.\n\n
\nTREATING SPECIALTY UPDATES FOR FY10\n\n
\nThis build contains the changes made to the registration routines for the\nScheduling IEMM patch SD*5.3*66.\n\n
\nFIXES FOR PTF 501 DISPLAY AND WAIT LIST ERROR\n\n
\nThis patch corrects:\n1. Correcting Record index of 3 fields in patient file\n to use DA instead of DFN.\n2. Determination of radiation method for SVC^VADPT API.\n3. Change Patient Type Update[DG PATIENT TYPE PARAMETER EDIT] option to \n prevent users from adding a new patient type.\n\n
\nFix errors caused by DGRPCE1 and DGRPE1.\n\n
\nTREATING SPECIALTY SERVICE UPDATE\n\n
\n2010 Means Test Threshold Updates\n\n
\nTREATING SPECIALTY UPDATES\n\n
\n \nVETERAN ON-LINE APPLICATION (VOA) ENHANCEMENT\nRefer to patch DG*5.3*800 in the FORUM Patch Module for a complete\ndescription.\n\n
\n-WHO ENTERED PATIENT field (#.096) in the PATIENT FILE (#2) is null or \n incorrect. \n\n
\nSee NPM for description.\n\n
\nThis patch corrects a problem where a consistency check error for error\n55 is displayed when a patient actually HAS income data on file for the year.\nPlease refer to the National Patch Module (NPM) for a complete\ndescription of the contents of this patch.\n\n
\n \nMPI SUPPORT FOR JOINT VA/DOD MEDICAL CENTER \nRefer to patch DG*5.3*821 in the FORUM Patch Module for a complete\ndescription.\n\n
\nModifications to Patient Registration to prevent the 'Edit a Means Test'\nprompt if the on file MT belongs to another site.\n\n
\n This patch will allow a PTF record for a FEE BASIS patient with a means\n test status of "Required" to be closed and transmitted to Austin. It will\n also allow setting of 501 transmissions flag for PTF's with more than 25\n records.\n\n
\nThe patch is to fix an error with the IF statement logic in the Vista \nPIMS VAFHAPV1 API.\n\n
\nCannot view patient registration data for patient on LINUX OS.\n\n
\n2010 Means Test Threshold Updates\n\n
\nSUPPORT FOR NATIONAL HEALTH INFORMATION EXCHANGE\nRefer to patch DG*5.3*825 in the FORUM Patch Module for a complete\ndescription.\n\n
\nEDR shutdown.\nSee NPM for description.\n\n
\n This patch will change the PTF(Patient Treatment File) Census \n closeout date from the 14th day of the month following the\n census date to the 7th.\n\n
\nThis patch prevents registration from updating the IVM means test status.\nPlease refer to the National Patch Module (NPM) for a full description of\nthis patch.\n\n
\nThis patch will correct the "before DOB" on the Potential Catastrophic \nEdit of Patient Identifying Data alert. It will also add ED observation \nfor API to ask readmit question.\n\n
\nThis patch will correct the following issue:\ntime value when entering the date of death.\n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nPATIENT (2) DATE OF DEATH (.351) Modified \n \nThe [DG CO-PAY TEST FUTURE LIST] Copay Exempt Test Needing Update \nAt Next Appt report menu option is incorrectly including future-appointed \npatients whose latest, expired or soon-to expire Co-pay Exemption Tests \nhave been converted by IVM. These cases need to be excluded from the\nreport.\n \nThe [DG DEATH ENTRY] Death Entry option is not allowing the entry of a\n\n
\nThis patch fixes the listing of a patient on the call list when the patient\nis scheduled for an appointment in a non-count clinic.\n\n
\nTREATING SPECIALTY UPDATES\n\n
\nDG*5.3*787 patch corrects two SAC (Standards and Conventions) violations.\n\n
\nThis patch contains VistA changes to support technology and business \nchanges that are occurring with the implementation of Public Law 111-163.\n\n
\nThis patch has enhancements to the Veterans Health Information Systems \nVeteran actually receives care. As a result, the value of the preferred \nfacility assignment is limited. CR 9620 specifies changes needed in the \nway that a Veteran's Preferred Facility is entered and stored in ESR and \nVistA. These changes are necessitated by the requirements of the \nVeterans Benefit Handbook Project.\n \n \n***NOTE***\nThis patch needs to be released and loaded at the same time as ESR 3.5.\n \nand Technology Architecture (VistA) system to support technology and \n \nThis patch modifies the Registration v5.3 application as described below:\n \n1. Modify VistA to lock the Preferred Facility to prevent users from \nchanging the field once ESR has assigned it.\n \n2. Modify VistA to display to a VistA user the following help text when \na VistA user attempts to edit the Preferred Facility field.\n \n "Preferred Facility can only be edited/modified by an ESR user, \nbusiness changes that are occurring with the implementation of the \n please contact HEC to request changes/edits"\n \n3. Modify VistA to upload SOURCE DESIGNATION from ESR. Source \nDesignation field (#27.03) is automatically assigned by the ESR or VistA\nsystem and is a new field in the PATIENT file (#2). Valid Source\nDesignation's are:\n a. V = VistA\n b. E = ESR\n c. PA = PCP Active\n d. PI = PCP Inactive\nEnrollment System Redesign (ESR) Preferred Facility project, Change \n \n4. Modify VistA to allow a user to ONLY change Preferred Facility if a\nveteran's PF Source Designation is PCP Inactive (PI) or VistA (V).\n \n5. Modify VistA to trigger a Z07 HL7 message to be sent to ESR when a \nPreferred Facility has been assigned/modified.\n \n6. Modify VistA to store the Preferred Facility and associated Source\nDesignation in the Patient file (#2). If VistA receives a Z11 HL7 \nmessage with Preferred Facility, display what ESR sent in the Patient\nRequest (CR) 9620.\nEnrollment [DGEN PATIENT ENROLLMENT] menu. If no Z11 has been received, \ndisplay the most recent Preferred Facility assigned.\n \n7. Preferred Facility shall be changed to a required field and must be \nentered by a VistA user when the veteran is first registered/enrolled in \nthe VA Medical Center.\n \nCurrently, a Veteran selects a Preferred Facility (PF) at the time of \napplication for enrollment. The Preferred Facility information is rarely \nupdated by the Veteran and is not linked to the location where the \n\n
\nSee National Patch Module for description.\n\n
\n1. This patch introduces an additional check on the Dependent's Effective\ndon't own. The original check did not differentiate between parent and\ndivisions of the parent.\nDate when entering a new dependent using the Spouse/Dependent Add ("DA")\nprotocol on the Family Demographic Data, Screen <8> in the Load/Edit\nPatient Data (DG LOAD PATIENT DA TA) option on the Registration Menu.\nThis check will prevent the effective date from being prior to the\nVeteran's Date of Birth.\n \n2. This patch adjust's a check introduced with DG*5.3*799 which was to\nprevent sites from editing MT's through the registration menu's that they\n\n\nDistributes API's for Patient Record Flag retrival in support of\nHigh Risk Mental Health Initiative\n\n
\nMilitary Service Data Sharing (MSDS) project\n\n
\nMESSAGING ENHANCEMENTS FOR NEW FIELDS\n \nRefer to patch DG*5.3*837 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch will add two new entries to the HL LOGICAL LINK (#870)\nfile. The entries are for two new vendors, Authentidate and Cardiocom.\n\n
\nTREATING FACILITY LIST (#391.91) FILE ISSUES\n \nRefer to patch DG*5.3*856 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch contains VistA changes to support technology and business\nchanges that are occurring with the implementation of Pension Data \nSharing.\n\n
\n1. Modify search to insure that Secondary Diagnosis Codes 10-13 in\n Patient Treatment File (PTF) will be searched when running option\n 'Diagnostic Code PTF Record Search'.\n \n2. XINDEX errors caused by $N(ext) command in cross reference triggers in\n Patient Movement File (#405) which are in violation of SACC\n (Standards & Conventions Committee) standards.\n\n
\nSee NPM for description.\n\n
\nThis patch contains VistA changes to support technology and business\nchanges that are occurring with the implementation of Permanent\nAddress Verification.\n\n
\nThis patch addresses 3 issues:\n(#391) \nfor EDIT MISSING DATA? (#102) \n \nThere is a misspelled word in data dictionary help text in the PATIENT \nFile (#2) \nfor CANCELLATION REMARKS (#.98) \n \nThe NAME field of the PATIENT TYPE File (#391) is allowed to be changed.\n \nThere is a misspelled word in database help text in the PATIENT TYPE File \n\n
\nPatch DG*5.3*866 addresses the following issue:\n \n 1. Pseudo Social Security Number Calculator allows duplicates.\n This is creating an issue for the New Born Project with\n with multiple births and bill processing.\n\n
\nDGPF NEW CAT1 FLAG AND CONVERSION\n\n
\nPatch DG*5.3*870 modifies 2 Registration routines to accommodate the new \nInternational Classification of Disease Tenth Revision (ICD10) code \nstructure. The ICD10 new code structure is being expanded and allowing \nfor letters and numbers to be used.\n\n
\nPatch DG*5.3*868 addresses the following issue:\n \n 1. Inactive International Classification of Diseases (ICD) code \n cannot be assigned to Patient Treatment File (PTF)\n due to system sending date and time of movement.\n Date is only required information.\n\n
\nVIC 4.02 MPI INTEGRATION\nRefer to patch DG*5.3*857 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch addresses 3 issues:\n PATIENT DATA] Option.\n \n1. Medicaid inconsistency check isn't working when a field consistency\n edit check that is processed prior to it is set to DON'T CHECK. \n2. When the SOCIAL SECURITY NUMBER field (#.09) of the PATIENT file (#2) \n is updated, the PRIMARY LONG ID field (#.363) and the PRIMARY SHORT ID\n field (#.364) of the PATIENT file (#2) are not updated accordingly. \n3. An undefined error is occurring during an attempt to close a Patient\n Treatment File (PTF) (#45) record via LOAD/EDIT PTF DATA [DG LOAD \n\n
\nThis build contains the changes made as a result of SD*5.3*143. See that\ndescription for details.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 10\nRefer to patch DG*5.3*863 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch addresses 4 issues:\nIn PATIENT file (#2), the trigger is not working correctly for\nfields ADDRESS CHANGE SOURCE (#.119), CELLULAR NUMBER CHANGE \nSOURCE (#.1311), PAGER NUMBER CHANGE SOURCE (#.1313), and EMAIL ADDRESS\nCHANGE SOURCE (#.137).\n\n
\n ***NOTICE***\nRegistration system (DG), Fee Basis System (FB), and Integrated Billing\n TYPE OF PATIENT (#391) NAME (#.01) New Data content\n (Single new record added "NEWBORN OF VETERAN") No Data Dictionary\n changes\n \n VA ADMITTING REGULATION (#43.4) NAME (#.01) New Data content\n (Single new record added "NON-VA FOR FEMALE VET+NEWBORN")\n No Data Dictionary\n changes\n \n INCONSISTENT DATA ELEMENTS (#38.6) New Data content\n(IB).\n Two new records added:\n 313 NEWBORN REQUIRES SPONSOR\n 314 NEWBORN NEEDS ELIGIBLE SPONSOR No Data Dictionary\n changes\n \n \n Forms Associated:\n \n Form Name File # New/Modified/Deleted\n --------- ------ --------------------\n \n N/A\n \n Mail Groups Associated:\n \n \n Mail Group Name New/Modified/Deleted\n --------------- --------------------\n N/A\n \n Options Associated:\nBelow is a list of all the applications involved in this project along with\n \n Option Name Type New/Modified/Deleted\n ----------- ---- --------------------\n N/A\n \n Protocols Associated:\n \n Protocol Name New/Modified/Deleted\n ------------- --------------------\n N/A\ntheir patch number:\n \n Security Keys Associated:\n \n Security Key Name\n -----------------\n N/A\n \n Templates Associated:\n \n Template Name Type File Name (#) New/Modified/Deleted\n \n ------------- ---- ------------- --------------------\n \n \n Additional Information:\n \n \n New Service Requests (NSRs):\n -----------------------------\n NSR 20100901\n \n APPLICATION/VERSION PATCH\n Patient Safety Issues (PSIs):\n ------------------------------\n N/A\n \n Remedy Ticket(s) & Overviews:\n -----------------------------\n N/A\n \n \n Test Sites:\n ---------------------------------------------------------------\n -----------\n \n LEXINGTON\n PUGET SOUND\n \n \nDocumentation Retrieval Instructions:\n-------------------------------------\nUpdated documentation describing the new functionality introduced by this\npatch is available.\n PATIENT REGISTRATION (DG) V 5.3 DG*5.3*867\n \nThe preferred method is to FTP the files from ftp://download.vista.domain.ext/\nThis transmits the files from the first available FTP server. Sites may also\nelect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \n The documentation will be in the form of Adobe Acrobat files.\n FEE BASIS (FB) V 3.5 FB*3.5*146\n \n Documentation can also be found on the VA Software Documentation Library\n at: http://www4.domain.ext/vdl/\n \n File Description File Name FTP Mode\n --------------------------------------------------------------------------\n Fee Basis User Manual fb3_5um.pdf Binary\n PIMS v5.3 ADT User Manual Registration dg_5_3_reg_um.pdf Binary\n \nThe procedure guide, Care for Newborn of Women Veterans, located at\nUsers should be made aware that processing of Newborn claims must ONLY be\n INTEGRATED BILLING (IB) 2.0 IB*2.0*499\nhttp://nonvacare.hac.domain.ext/policy-programs/procedure-guides.asp,\nshould be distributed to those personnel registering newborns and/or\nprocessing newborn claims.\n \n \n Patch Installation:\n \n \nPre/Post Installation Overview\n------------------------------\n \nThere are three post installation routines associated with this patch DG867PO,\nFB146PO, and IB499PO. These routines primarily serve as filters for the data\ntransmitted to the appropriate files listed above, so that only the intended\ndata is delivered. The only exception is the IB499PO routine which\nprogrammatically makes an addition to the help text of the FAMILY PREFIX field\n(#.03) in the SPONSOR RELATIONSHIP file (#355.81). These post installation\nroutines may be deleted after successful installation of the NEWBORN DG FB IB\nBUNDLE 1.0\n \nInstallation Instructions\nThe patches (DG*5.3*867, FB*3.5*146, and IB*2.0*499) are being released in the\n-------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize potential\ndisruption to users. This patch should take less than 5 minutes to install.\n \nFB*3.5*147 is a required patch and must be installed before DG*5.3*867.\n \nDG*5.3*867 is one of three patches for this release (including FB*3.5*146 and\nIB*2.0*499). The patches will be installed as a bundle in the following order:\n \nKernel Installation and Distribution System (KIDS) multi-build distribution\n1) DG*5.3*867\n2) FB*3.5*146\n3) IB*2.0*499\n \n \n Pre-Installation Instructions\n -----------------------------\n 1. OBTAIN PATCHES\n --------------\nObtain the host file NEWBORN_1_2_DG_FB_IB.KID which contains the following\nNEWBORN DG FB IB BUNDLE 1.0\npatches:\n \n DG*5.3*867\n FB*3.5*146\n IB*2.0*499\n \nSites can retrieve VistA software from the following FTP addresses. The\npreferred method is to FTP the files from:\n \n download.vista.domain.ext\n \n \nThis will transmit the files from the first available FTP server. Sites may\nalso elect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \nThe NEWBORN_1_2_DG_FB_IB.KID host file is located in the anonymous.software\ndirectory. Use ASCII Mode when downloading the file.\nThe purpose of the Caregivers: Newborn Claims Processing Enhancement Project\n \n 2. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu option\n [XPD MAIN]:\n \n Edits and Distribution ...\n Utilities ...\n Installation ...\n \nis to enhance VistA Fee Basis application in support of compliance with\n Select Kernel Installation & Distribution System Option: Installation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\nPublic Law 111-163, the Caregiver and Veterans Omnibus Health Services Act\n \n Select Installation Option:\n \n 3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD\n -------------------------------------\n From the Installation menu, select the Load a Distribution option.\n \n When prompted for "Enter a Host File:" Enter the full directory path\n where you saved the host file NEWBORN_1_2_DG_FB_IB.KID\n (e.g., SYS$SYSDEVICE:[ANONYMOUS]NEWBORN_1_2_DG_FB_IB.KID)\nof 2010. This law makes changes to sections of Title 38, United States Code\n \n When prompted for "OK to continue with Load? NO//", Enter "YES."\n \n The following will display:\n \n Loading Distribution...\n \n NEWBORN DG FB IB BUNDLE 1.0\n DG*5.3*867\n FB*3.5*146\nentered in VistA. No entry in FBCS should be performed.\nto furnish health care services to a newborn child of a Woman Veteran who\n IB*2.0*499\n Use INSTALL NAME: NEWBORN DG FB IB BUNDLE 1.0 to install this\n distribution.\n \n 4. RUN OPTIONAL INSTALLATION OPTIONS FOR MULTI-BUILD\n -------------------------------------------------\n From the Installation menu, you may select to use the following options\n(when prompted for the INSTALL NAME, enter NEWBORN DG FB IB BUNDLE 1.0\n \n a. Backup a Transport Global - This option will create a backup\nis receiving maternity care furnished by the Department of Veterans Affairs\n message of any routines exported with this patch. It will not\n backup any other changes such as data dictionaries or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, data dictionaries, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n(VA) for not more than seven days after the birth of the child.\n 5. INSTALL MULTI-BUILD\n -------------------\n This is the step to start the installation of this KIDS patch. This will\n need to be run for the NEWBORN DG FB IB BUNDLE 1.0\n \n a. Choose the Install Package(s) option to start the patch\n install.\n b. When prompted for the "Select INSTALL NAME:" enter\n NEWBORN DG FB IB BUNDLE 1.0\n c. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n \n NO//", answer NO\n d. When prompted "Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? NO//", answer NO\n e. When prompted "Device: HOME//", enter HOME\n to display the Install message on the screen (or enter the device\n you want to print the Install message). You may queue the\n install if you wish.\n \n \nPost-Installation Instructions\nThe scope of these enhancements is to capture information on healthcare\n------------------------------\n \n*** IMPORTANT NOTE ***\nPlease note there are three post installation routines that may be deleted\nafter successful installation of the NEWBORN DG FB IB BUNDLE 1.0. These are:\n \nDG867PO\nFB146PO\nIB499PO\nservices provided to newborn children of Women Veterans. Affected functions\ninclude eligibility determination, enrollment and registration, documentation\nof referrals and authorization for care, claims processing, and payment. Only\nmodification to the Fee Basis (FB) and the Registration (DG) packages are\nnecessary to meet the requirements of this enhancement. The Integrated\n ***********\nBilling (IB) Patch is included to provide required data for the Fee Basis\ninstall to reference.\n \n \nThe primary purpose of this enhancement is to allow the Electronic Filing of\nNewborn claims.\n \nFunctional Description\n------------------------------\nThe following features and functions have been added to the Fee Basis workflow\nThis patch, along with FB*3.5*146 and IB*2.0*499, is being released as a\nprocess applying to both Civil Hospital and Medical Fee:\n \n 1. A new Patient Type of NEWBORN OF VETERAN has been added to the TYPE OF\nPATIENT file (#391). This new selection will be available on Registration\nScreen <7>.\n \n 2. A sponsor is required for all Newborns determined by having the DOB less\nthan one (1) year from the present date. An inconsistency check has been added\nto check the presence of a sponsor. If an inconsistency is found the\ninconsistency check will prompt the user to return to Screen <15> in\nbundle, and all three will be automatically installed in the correct order.\nregistration to enter a Sponsor.\n \n 3. All Sponsors for Newborns must be listed as eligible for care. An\ninconsistency check will check the status of the Sponsors Eligibility. The\ncheck will trigger if the Sponsor has no Eligibility status.\n \nAll other statuses (i.e. Pending Verification, Verified, and Pending\nRe-verification) are acceptable.\n \n 4. Fee Authorization dates associated with Newborns have checks in place to\n \nnot allow Authorization dates that fall outside the accepted range of Newborn\nAuthorization. The range is DOB to DOB+7. The system will warn the user and\nnot accept an Authorization date that falls outside the appropriate range for\na Newborn.\n \n 5. When a Veteran Mother of a Sponsored Newborn is reviewed in the\nRegistration screens, Screen <15> will display the Newborn(s), with the\nadditional header of "Sponsored Newborn".\n \n 6. The FAMILY PREFIX "NB Newborn of Vet" has been added to the Help text in\nThis patch has enhancements that extend the capabilities of the Veterans\nthe FAMILY PREFIX field (#.03) in the SPONSOR RELATIONSHIP file (#355.81)\n \n 8. The following default values were added when entering a Newborn with a\ndate of birth of less than one (1) year from present date. Defaults will \nonly be assigned when specified screens are accessed during the\nregistration process: PATIENT DATA, SCREEN <2> Marital field is defaulted\nto NEVER MARRIED. APPLICANT/SPOUSE EMPLOYMENT DATA, SCREEN <4> Status\nfield is defaulted to NOT EMPLOYED. FAMILY DEMOGRAPHIC DATA, SCREEN <8>\nMarried Last Year field is defaulted to NO.\n \nHealth Information Systems and Technology Architecture (VistA) Patient\n \n Patch Components\n ================\n \n \n Files & Fields Associated:\n \n \n File Name (#) Field Name (#) New/Modified/Deleted\n ------------- -------------- -----------------\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nPatient Record Flag - Missing Patient (introduction)\n\n
\nVIC CARD ENHANCEMENT\nRefer to patch DG*5.3*874 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch contains VistA changes to support technology and business\nchanges that are occurring with the implementation of Discontinue\nAnnual Means Test Renewal.\n\n
\nThis patch addresses the following:\n \n- Resolves an <UNDEFINED> error that occurs when editing the PRIMARY \n PHYSICIAN (#.08) field in the PATIENT MOVEMENT (#405) file.\n \n- Updates the input transform and executable help text for the ALL OTHER \n INCOME (#.17) field in the INDIVIDUAL ANNUAL INCOME (#408.21) file.\n\n
\nThis build makes the ICD-10 changes to PTF for the Clinical Reminders\nIndex.\n\n\n
\nSee National Patch Module for description.\n\n
\nThis is the ADT ICD-10 Remediation patch.\n\n
\nRegistration changes for the VIA Project. See patch description for \ndetails.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 12\nRefer to patch DG*5.3*876 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThe VistA integration Adaptor (VIA) project requires access to certain \nRemote Procedure Calls (RPCs) that are part of the REGISTRATION package. \nThe purpose of this patch is to publish one additional RPC allowing access\nfor use by VIA by setting the field APP PROXY ALLOWED field (#.11) of the \nREMOTE PROCEDURE file (#8994) to YES. This patch deals specifically with\nthe VAFCTFU CONVERT ICN TO DFN RPC.\n\n
\nPatch DG*5.3*893 addresses the following 3 issues:\n non-count\n \n- The Call List [DGEN NEACL MGT RPT1] has a bug when comparing the \n patient's preferred facility to the selected facility. \n It cause them not to match if the preferred facility code begins \n with 4 numerics instead of 3.\n \n- Patients whose first enrollment was before the install date of patch\n DG*5.3*779 do not have an AEAR index on the APPOINTMENT REQUEST ON \n 1010EZ (#1010.159) field in the PATIENT (#2) file\n \n- The Tracking Report [DGEN NEACL MGT RPT2] has a bug which causes the API\n that gathers appointments to only return one appointment. This can cause\n a blank appointment date to display if the first appointment is a \n\n
\nThe Means Test thresholds for Calendar Year 2015 are distributed with this\n MT COPAY EXEMPT 1ST DEP INCOME (#3) - $6,396\n MT COPAY EXEMPT INCOME PER DEP (#4) - $2,198\n THRESHOLD PROPERTY (#8) - $80,000\n CHILD INCOME EXCLUSION (#17) - $10,300\n \nIn addition, this patch will update the following fields in the \nPARAMETERS file (#8989.5) for Income Year 2014 to:\n \n DGMT MAPR GLOBAL RATE 5 \n DGMT MAPR 0 DEPENDENTS 12868\npatch. The post-installation routine, DG53910P, will create a new subentry\n DGMT MAPR 1 DEPENDENTS 16851\n DGMT MAPR N DEPENDENTS 2198\n \nThis patch, DG*5.3*910 is one of three VistA 2015 threshold patches. It \nupdates the thresholds for the Means Tests and the Maximum Annual Pension \nRate. Patch EAS*1.0*125 will address the annual updates for the GMT \nThresholds and patch IB*2.0*540 will address the annual updates for the \nPharmacy Copay Thresholds.\n(or replace an existing one) for calendar year 2015 in the MEANS TEST DATA\n(#250) multiple field of the MAS PARAMETERS (#43) file. Six subfields\nwithin the multiple will be updated with the new Means Test threshold data\nvalues as follows:\n \n MEANS TEST DATA (#.01) - 2015\n MT COPAY EXEMPT VET INCOME (#2) - $31,978\n\n
\nPatch DG*5.3*859 addresses an issue with the DG Home Telehealth mail \nalerts that users receive when an HL7 message does not receive the\nproper acknowledgement and an error alert is created. Users are finding\nit difficult to research the alert received without more information \nincluded in the message.\n\n
\nPatch DG*5.3*872 addresses 2 issues:\n \n 1. APPOINTMENT TYPE SUB-CATEGORY field (#24) of the APPOINTMENT \n sub-file (#2.98) of the PATIENT file (#2) is not assigned\n properly.\n 2. Patient Address Update option is not displaying correctly.\n\n
\nPatch DG*5.3*895 addresses 2 issues:\n \n 1.) Deletion of admission can cause orphaned nodes\n 2.) Inconsistency 55 issue with service connected veterans who agree to \n copay, but decline to provide income data\n\n
\nSee National Patch Module (NPM) for a description of the changes included\nwith this patch.\n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*157 in the National Patch Module.\n\n
\nThis patch addresses 4 issues:\npatch, DG*5.3*93\n \n4. DRG Frequency Report is not showing all patients in the Service \ncategory.\n \n1. Bad Address Indicator is not working as the Help prompt suggests. \nUser needs to manually remove the indicator when entering changes. \n \n2. SAC violation in Patch DG*5.3*864, a non-incremental lock was \nintroduced.\n \n3. User manual needs updated to reflect functionality changes from prior \n\n
\n \nPatch DG*5.3*892 addresses 3 issues:\n \n 1.) Undefined error when entering Confidential Address\n 2.) PRF Assignment Action Not Linked Report issue\n 3.) Documentation change needed for MISSING PATIENT PRF\n\n
\nAfter the installation of the DG*5.3*850 patch, sites reported these \n INQUIRY] a hard error occurs.\nthree issues that are being fixed with this patch:\n \n1) The Census Status Report [DGPT CENSUS STATUS REPORT] is reporting the\n admission ward instead of the last movement ward.\n2) When entering a movement for a Post-Vietnam P.O.S. and the SW Asia\n Service flag has been set, a prompt for establishing the SW Asia\n condition will cause a hard error when answered.\n3) When performing an inquiry in option MPCR INQUIRY [DGPT MPCR\n\n
\nThis patch replaces CD STATUS DIAGNOSES, CD STATUS PROCEDURES and CD \nSTATUS CONDITIONS with CD DESCRIPTORS, thus eliminating the use of ICD \nand CPT codes for qualifying CD Reasons. Six new descriptors with a TYPE \nof "DE" are added to the Catastrophic Disability REASONS file #27.17.\n\n
\nPlease refer to DG*5.3*884 in the National Patch Module for a description\nof this patch.\n\n
\nMASTER VETERAN INDEX VISTA ISSUES - ITERATION 13\nRefer to patch DG*5.3*902 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*897 addresses one issue:\n \n 1. Patient File Update Utility is not dinuming patients with \n multiple races correctly.\n\n
\nENTERPRISE REGISTRATION - ITERATION 14\nRefer to patch DG*5.3*915 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch contains VistA changes to support technology and business\nchanges that are occurring with the implementation of the Email Address \nIndicator project.\n\n
\nThe Health Eligibility Center (HEC) requested modifications to the \nThe following are the new guidelines on whether a patient means test is \ncurrent.\n \n1. The Means Test Effective Date is between (inclusive): 1/2/2012 and \n 12/31/2012\n2. The Mean Test Effective Date is greater than 1/1/2013 AND has a MT\n Status of MT Copay Exempt, GMT Copay Required, or Pending Adjudication\n3. The MT Status equals MT Copay Required\n4. The MT Status equals No Longer Required\n5. The Means Test Effective Date is not a future date\nEnrollment System (ES) and VistA Registration, Enrollment and Eligibility \n(VistA REE) software to support the requirements of the Means Test Report \nfor ES project 4.0. \n \nThe new requirements check whether the patient means test is current or \nnot. If the means test is current than the patient record is not \ndisplayed. \n \n\n
\nThe changes included in this patch are described in the description\nof patch DG*5.3*143 in the National Patch Module.\n\n
\n *************************************************************************\n *************************************************************************\n \n The Health Eligibility Center (HEC) requested modifications to the \n Enrollment System Redesign (ESR) and VistA Registration, Enrollment and\n Eligibility (Vista REE) software to support the requirements of the\n Health Benefit Plans project.\n \n This patch modifies the Registration v5.3 application as described below:\n \n -- Create a new file containing the Health Benefit Plans and their\n Note: This patch is being released in support of the Enrollment System\n expanded descriptions.\n -- Modify Register a Patient [DG REGISTER PATIENT], \n Load/Edit Patient Data [DG LOAD PATIENT DATA] and \n View Registration Data [DG REGISTRATION VIEW]\n to allow user to view HBP profile for a veteran.\n -- Display expanded help text for HBP\n -- Store all history of assignments for HBP and be able to view\n -- Store data from the Z11 message when received from ES\n -- Create an API that will provide HBP information to Vista \n downstream applications to include the HBP Name and HBP\n Re-design (ESR) Health Benefit Plans project. DG*5.3*871 is\n Description.\n released in host file DG_53_P891.KID along with several other\n patches.\n \n It is imperative that this patch be installed no later than the\n compliance date. Your understanding and support is appreciated.\n \n\n
\n*************************************************************************\n \nThis patch modifies the Registration v5.3 application as described below:\n \nCreate a new data dictionary question for Contributed to Spousal Support.\nCreate a new data dictionary question for Contributed to Child Support.\n \n-- Health Eligibility Center (HEC) requested the Contributed to \n Spouse and Contributed to Child field be converted to accept a True\n (Yes) or False (No) response instead of a dollar amount. This field \n will be available to the user if the Lived with Patient Indicator\n Note: This patch is being released in support of the Enrollment System\n is populated with a False (No) response. \n-- This patch will decommission the AMOUNT CONTRIBUTED TO SPOUSE (Field \n #.07) and AMOUNT CONTRIBUTED TO CHILD (Field #.19) in the Income \n Relation (File #408.22). The Means Test and Rx Copay Test will no \n longer prompt for entry to these two fields.\n-- This patch will add a new CONTRIBUTED TO SPOUSAL SUPPORT (Field #.21) \n to the Income Relation File (File #408.22). The field will be a Y/N \n or Null set. This patch will prompt for entry of this new field at \n the appropriate point in the Means Test and Rx Copay test process.\n-- Modified Z07 message builder to include the Contributed to Spouse\n (ES) 4.0 project. DG*5.3*890 is released in host file\n indicator on the ORU Z07 ZIR segment.\n Added a trigger for an ORF Z07 message when a change is made to\n the Contributed to Spouse indicator.\n DG_53_P891.KID along with several other patches.\n \n It is imperative that this patch be installed no later than the\n compliance date. Your understanding and support is appreciated.\n \n *************************************************************************\n\n
\nThis patch modifies the Registration v5.3 application as described below:\n Mailgroup to notify select members that there has been a change in\n the Veteran's BT Financial Indicator status.\n \n-- This patch will display a new Beneficiary Travel Financial Indicator\n on the Means Test and Copay Test overview screens. The BT Financial\n indicator will be sent from the Enrollment System and share with all\n sites of record when the Income Verification Matching (IVM)\n application has performed a Conversion and/or Reversal on an income\n test where the Veteran had a BT award prior to the IVM action. A\n bulletin will be generated and sent to the BT CLAIMS PROCESSING\n\n
\nThis patch contains changes to the Date of Death application necessary to \naccomodate having the Master Veteran Index become the authoritative \nsource for Date of Death data entry.\n\n
\nThis patch, DG*5.3*922 is one of three VistA 2016 threshold patches. It \nupdates the thresholds for the Means Tests and the Maximum Annual Pension \nRate. Patch EAS*1.0*134 will address the annual updates for the GMT \nThresholds and patch IB*2.0*557 will address the annual updates for the \nPharmacy Copay Thresholds.\n\n
\nPatch DG*5.3*911 will address one issue:\nIntegrated Sites working with a Patient Record Flag must first\nassign the flag to their "main" site and then edit the flag for\nother sites to be able to receive/process the incoming HL7 messages, or\nelse the message is rejected as not coming from owning site.\n\n
\nDG*5.3*909 will update the Registration application to allow for the \nentering and maintenance of the Camp Lejeune Eligibility related data.\n \nPlease refer to Forum for a complete description of the updates.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 15\nRefer to patch DG*5.3*919 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*917 addresses one issue:\n1) Menu option Add/Edit Suffix Effective Date [DG PTF SUFFIX EFF \n DATE EDIT] was marked Out of Order in a previous patch. \n Business Owner has requested that this option be re-activated\n\n
\nSee National Patch module for description.\n\n
\n \nThis patch inactivates Eleven Treating Specialty (TS) codes\n\n
\nPatch DG*5.3*797 added the new MILITARY SERVICE EPISODE sub-file #2.3216 \nany of those inconsistencies is edited, the user is prompted with a set \nof eligibility-related fields that includes the Last Service Episode \nfields. Since these inconsistencies were not modified for DG*5.3*797, \nthe user is being prompted with the old MSE fields for SERVICE EPISODE \n[LAST]. These are the inconsistencies that are considered related to \nEligibility:\n \n 9 VETERAN STATUS UNSPECIFIED\n 10 SC PROMPT UNANSWERED\n 11 SC PROMPT INCONSISTENT\nin the PATIENT (#2) file to store Military Service Episode (MSE) data.\n 12 SC% UNSPECIFIED FOR SC VET\n 13 POS UNSPECIFIED\n 14 ELIG CODE UNSPECIFIED\n 18 ELIG/VET STATUS INCONSISTENT\n 19 ELIG/NONVET STAT INCONSISTENT\n 20 ELIG/SC% INCONSISTENT\n 22 ELIG CODE INCONSISTENT\n 24 POS/ELIG CODE INCONSISTENT\n 36 PATIENT TYPE UNDEFINED\n \nChanges in that patch included modifications to several consistency \n \nThis patch fixes this problem which was reported in Remedy ticket \nHD0000000623739 (DG*5.3*797 - MSDS MSE inappropriate prompts). When \nediting any of those eligibility-related inconsistencies, the user will \nnot be prompted with the old MSE fields and will now edit the MSE data in \nsub-file #2.3216 on the new Screen 6.1.\nchecks that used MSE data. The consistency checks that are listed in the \nDG*5.3*797 patch description are correctly using the new MILITARY SERVICE \nEPISODE sub-file #2.3216 and the new Screen 6.1 to edit the data.\n \nHowever, there is a set of consistency checks in the INCONSISTENT DATA \nELEMENTS (#38.6) file that are considered related to Eligibility. If \n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 16 / RELEASE 2\nRefer to patch DG*5.3*926 in the FORUM Patch Module for a complete\ndescription.\n\n
\nModified DG10 routine to allow for additional fields in file 2 to trigger\n.1213 Temporary Address Line 3\n.1214 Temporary City\n.1215 Temporary State\n.1216 Temporary Zipcode\n.21011 Primary NOK Work Phone Number\n.215 Primary NOK Streed Address Line 3\n.331 Emergency Contact Name\n.332 Emergency Contact Relationship\n.333 Emergency Contact Street Address Line 1\n.334 Emergency Contact Street Address Line 2\nan unsolicited update. Here are the fields that trigger freshness update:\n.335 Emergency Contact Street Address Line 3\n.336 Emergency Contact City\n.337 Emergency Contact State\n.338 Emergency Contact Zipcode\n.3731 Service COnnected Conditions\n.3121 Insurance\n \nField # Field Name\n======= ==========\n.033 Age\n.133 Email Address\n.1211 Temporary Address Line 1\n.1212 Temporary Address Line 2\n\n
\nThis patch, DG*5.3*930 is one of three VistA 2017 threshold patches. It \nupdates the thresholds for the Means Tests and the Maximum Annual Pension \nRate. Patch EAS*1.0*144 will address the annual updates for the GMT \nThresholds and patch IB*2.0*583 will address the annual updates for the \nPharmacy Copay Thresholds.\n\n
\nThis patch allows for the addition of language data to the Patient file.\n\n\n
\nRegistration/Enrollment system sends notification emails if there is an \nissue with the Upload process to a remote email address that has been \ndecommissioned. This patch will not allow emails to be sent to the remote\nemail group, but continue to use the local mail group.\n\n
\nIncrease Engagement in My HealtheVet (IEMHV)\nThe Preregister a Patient [DGPRE PRE-REGISTER] option has been enhanced \nto display a message alerting the clerk that the selected patient \nhas neither completed My HealtheVet registration, nor documented their \ndesire to be excluded from My HealtheVet registration. Recent assistance \nprovided by Pre-Registration clerks with the patient's My HealtheVet\nenrollment is displayed within the alert/reminder.\n \nSocialization Questions and Responses\n-------------------------------------\nThe Preregister a Patient [DGPRE PRE-REGISTER] option has been enhanced \n \nto capture a patient's My HealtheVet registration status during the \npre-registration process.\n \nMy HealtheVet Registration Actions\n--------------------------------\nThe Preregister a Patient [DGPRE PRE-REGISTER] option has been enhanced \nto capture actions Pre-Registration clerks performed to assist with a\npatient's My HealtheVet registration.\nThis patch contains enhancements to Pre-Registration functionality in the\nPreregister a Patient [DGPRE PRE-REGISTER] option in the VistA\nRegistration V.5.3 package to increase patient engagement in My \nHealtheVet.\n \nMy HealtheVet Enrollment Alert/Reminder\n---------------------------------------\n\n
\nThis patch modifies the Registration v5.3 application to update the \nprompt text and display of the Birth Sex and Self-Identified Gender \nIdentity fields. See patch description on Forum for full details.\n\n
\nPTF Y2K UPDATES\n \nUse post install to delete output tx on field 2/file 45.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - 'PREFERRED NAME'\nRefer to patch DG*5.3*937 in the FORUM Patch Module for a complete\ndescription.\n\n
\nENROLLMENT SYSTEM MODERNIZATION (ESM) MANAGE DATE OF DEATH IN VISTA\n\n
\nPatch DG*5.3*912 addresses 3 issues:\n multiple records\n \n1.) Issue with Patient Treatment File (PTF) 801 screen, Current \n Procedural Terminilogy (CPT) codes File (#81) SHORT NAME field (#2)\n has been deleted.\n2.) Military Service Data Inconsistencies Detail Report has data \n listed when nothing is wrong in the patient record.\n3.) Patient Treatment File with multiple Current Procedural\n Terminilogy (CPT) codes, enter the wrong deletion date if there are\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - 'DATE OF DEATH'\nRefer to patch DG*5.3*943 in the FORUM Patch Module for a complete\ndescription.\n\n
\nDescription:\n===========\n \nPATCH DG*5.3*938 ADDRESSES AND ISSUE WITH FOREIGN ADDRESS INFORMATION NOT\nBEING SENT IN THE 'PID' SEGMENT IN A01 EVENT HL7 MESSAGES.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - POB COUNTRY/PROVINCE\nRefer to patch DG*5.3*944 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThe following enhancements are included in this patch:\nAdding EDIPI to header line\nDisplay Health Benefit Plans Currently Assigned to Veteran\nChanged label Permanent Address to Mailing Address\nChanged label Temporary Address to Temporary Mailing Address\nDisplay Residential Address\nExpanded Health Benefit Plan details\n\n
\nENROLLMENT SYSTEMS COMMUNITY CARE(ESCC) HEALTH BENEFIT PLAN UPDATES\n\n
\nDG*5.3*940 EHBD BUILD 3 UPDATES\n\n
\nDG*5.3*162\nRevisions for Y2K.\n\n
\nPatch DG*5.3*942 (this patch) adds these two (2) new entries to the HL \nLOGICAL LINK (#870) File: 200TA and 200TB. This patch via \npost-install routine DG53P942 modifies the DNS DOMAIN for facility\n200T7. \n\n
\nAnnual update of Geographic Means Test (GMT) thresholds are needed for\ncalendar year 2018 (income year 2017). \n\n
\nEnrollment System Modernization Project VistA DG_53_P935.KID Build\nenhancements; see the patch description for more information.\n\n
\nThis patch implements Demographics domain changes required by the\nCollaborative Terminology Tooling & Data Management (CTT & DM) Native\nStandardization (NDS) project.\n \nPlease see FORUM for full patch description and installation instructions.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - RELABEL SEX PROMPTS\nRefer to patch DG*5.3*950 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*954 fixes a <SUBSCRIPT>PIVNW+16~VAFHPIVT ~VAT(391.71,"") \nerror.\n\n
\nThis patch addresses an issue with the Scheduled Admissions List [DG \nSCHED ADMIT PRINT] option where the DATE/TIME value is being reported as \ninvalid\n\n
\nPlease see the DG*5.3*959 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*945 addresses the issue of the Purge Duplicate\nIncome Tests [DG CLEANUP INCOME TEST DUPES] option not completing\ndue to an error in routine DG53558N.\n\n
\nDESCRIPTION:\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - DATE OF DEATH UPDATES\nRefer to patch DG*5.3*963 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee National Patch module for description.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ACTIVE DUAL CONSUMER (ADC) \nRefer to patch DG*5.3*955 in the FORUM Patch Module for a complete\ndescription.\n\n
\nOffice of Mental Health is requesting 4 Treating Specialty (TS) Codes be \ninactivated with an inactivation date of 10/1/18\n\n
\nThis Build contains components for the report enhancements to PRF by the \nSHRPE project.\n\n
\nPlease refer to the Patch Description in FORUM for patch DG*5.3*970\n\n
\nPlease see the DG*5.3*947 patch description for detailed information \nregarding this patch.\n\n
\nThis patch addresses NSR 20171118. It modifies the option Religion List \nfor Inpatients [DG RELIGION LIST] to display only the last four digits of\na patient's Social Security Number (SSN). This option is used to run a\nreport listing inpatients by religious faith. Currently, this option\nunnecessarily displays each patient's full SSN. This modification helps\nprotect patient privacy and supports national SSN reduction efforts.\n\n
\nPatch DG*5.3*965 addresses 2 issues:\n1. <SUBSCRIPT>PIVNW+40^VAFHPIVT error (Pivot file entry not there).\n2. SAM-site is receiving SUBSCRIPT>SAVE+11^DGRPECE error\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - MVI SENSITIVITY\nRefer to patch DG*5.3*967 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the DG*5.3*941 patch description for detailed information \nregarding this patch.\n\n
\nThe Means Test thresholds for Calendar Year 2019 are distributed with this\nThresholds and patch IB*2.0*635 will address the annual updates for the \nPharmacy Copay Thresholds.\npatch. The post-installation routine, DG53973P, will create a new subentry\n(or replace an existing one) for calendar year 2019 in the MEANS TEST DATA\n(#250) multiple field of the MAS PARAMETERS (#43) file. \n \n \nThis patch, DG*5.3*973 is one of three VistA 2019 threshold patches. It \nupdates the thresholds for the Means Tests and the Maximum Annual Pension \nRate. Patch EAS*1.0*170 will address the annual updates for the GMT \n\n
\nThis build includes Data Dictionary updates for Year 2000 compliance. The\nfollowing DD's are being patched:\n \n PATIENT File, #2\n CENSUS File, #41.9\n MEDICAL CENTER DIVISION File, #40.8\n\n
\nUser gets <UNDEFINED>ACTIVE+51^DGPFAPIU *DGACT(0) when using the Reminder \nTest[PXRM REMINDER TEST] option in the Reminder Managers Menu[PXRM \nMANAGERS MENU] when the end date of the PRF Assignment date is the same \nas the end date for the report. \n\n
\nPlease see the DG*5.3*966 patch description for detailed information \nregarding this patch.\n\n
\nThis patch addresses enhancements to Patient Record Flags (PRF) to \nrecorded in the PRF FileMan files to enable a convenient reference \nbetween VistA and DBRS.\n \n2. Modification to support TIU/CPRS Progress Note Properties' action list \nfunctionality. \n \n3. Enhancements to PRF flags ownership transfers. The patch implements \nnew functionality and makes modification to existing code to improve the \nprocess of ownership transfer and eliminate issues reported by PRF users. \n \nimprove the delivery of targeted Mental Health care for individuals at \n4. Various enhancements and fixes related to PRF flag HL7 transmissions \n \nPlease see the patch description of the patch in FORUM for details.\nhigh risk for suicide.\n \nEnhancements to PRF reports were made to improve effective management of \ncoordination of care for high risk individuals and to include new data \nelements introduced with this patch.\n \n1. The Disruptive Behavior Reporting System (DBRS) record numbers are now \n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - SUPPORT LONG NAMES IN VA MPI\nRefer to patch DG*5.3*974 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*975 fixes an issue where the old MSE (Military Service\nEpisode) data is being deleted from an incoming ORFZ11 and new MSE data\nis not being stored.\n\n
\nPlease refer to the Patch Description in FORUM for patch DG*5.3*976\n\n
\nUser reported an issue in the ISO Sensitive Records Report-Export [DG \nSENSITIVE RCDS RPT-EXPORT] option where the data is not being displayed \ncorrectly if the PATIENT NAME (.01) field is 30 characters long. The \nprint template does not account for the "^" it concatenates to the end of \nthe patients name to use as a delimiter. Therefore, the PATIENT NAME \n(.01) and the DATE/TIME RECORD ACCESSED (#50) field would be displayed \ntogether.\n\n
\nPlease see the DG*5.3*978 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*987 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - EHRM SUPPORT\nRefer to patch DG*5.3*981 in the FORUM Patch Module for a complete\ndescription.\n\n
\nDG*5.3*170\nRevisions for Y2K.\n\n
\nPatch DG*5.3*984 modifies routine VAFHLZPD to use a different Application \nProgram Interface (API) call when retrieving the Homeless Indicator due \nto the decommissioning of the Social Work (SOWK) package.\n\n
\nPlease see the DG*5.3*982 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*972 patch description for detailed information \nregarding this patch.\n\n
\nThe Means Test thresholds for Calendar Year 2020 are distributed with this\npatch. The post-installation routine, DG53995P, will create a new subentry\n(or replace an existing one) for calendar year 2020 in the MEANS TEST DATA\n(#250) multiple field of the MAS PARAMETERS (#43) file.\n\n
\nPlease see the DG*5.3*985 patch description for detailed information \nregarding this patch.\n\n
\nThe patch is delivered in a bundle with IVM*2.0*184 and implements \n \nThis patch also introduces a sub-eligibility, which is implemented as a\nnew "EXPANDED MH CARE TYPE" field in VistA PATIENT file (#2), for EMERGENT\nMH OTH type that supports providing mental health care in one or more\n90-day periods (additional periods require authorization) for eligible\npatients.\n \nThis patch also introduces supportive reporting to identify those patients\nregistered as "EMERGENT MH OTH" (abbreviated as OTH-90). \n \nEXPANDED MH CARE NON-ENROLLEES as a primary eligibility code (and a\nHL7 messaging has been updated in this patch to ensure VistA Registration \nchanges are communicated to the Enrollment System (ES). OTH patient data\nwill be shared with ES and if a patient record is updated in ES, it will \ncontinue to be updated in VistA.\nMedical Administration Service (MAS) eligibility code) in VistA\nRegistration to identify and support Other Than Honorably (OTH) discharged\npatients who need mental healthcare services, in order to help reduce the\nnumber of Veteran suicides. These patients are awaiting adjudication and\nare entitled to receiving mental health treatment during that timeframe\nfrom the VA either for 90-day episodes of care for service related\nemergent mental health issues.\n\n
\nPatch DG*5.3*989 will update the QRD segment of an HL7 Z11 query message\nto pass in the Integration Control Number (ICN) (#991.01) field of the\nPatient (#2) file as requested by the Enrollment System Redesign (ESR)\nteam.\n\n
\nPatch DG*5.3*1002 modifies routine VAFHLZPD to use a different\nApplication Program Interface (API) call when retrieving the Homeless\nIndicator due to the decommissioning of the Social Work (SOWK) package.\n\n
\nPlease refer to patch description on FORUM for detailed instructions.\n\n
\nPlease see the DG*5.3*1006 patch description for detailed information \nregarding this patch.\n\n
\nSee National Patch Module for description.\n\n
\nRefer to the DG*5.3*1011 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ENTERPRISE REGISTRATION UPDATES\nRefer to patch DG*5.3*1000 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - CARMA SUPPORT\nRefer to patch DG*5.3*1001 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the DG*5.3*996 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*998 patch description for detailed information\nregarding this patch.\n\n
\nThis patch implements EXPANDED MH CARE NON-ENROLLEE as a primary\neligibility code in VistA Registration to identify and support nonveterans\nthat need emergent mental healthcare services.\n\n
\nThis patch creates a new protocol that is executed whenever a field that \npoints to the ICD DIAGNOSIS file (#80) is modified. See the associated \npatch description for complete details about this patch.\n\n
\nPatch DG*5.3*992 addresses two issues.\n when readmitting a patient that was previously in an \n observation status.\n \n 1. Users are unable to add/edit or delete catastrophically \n disabled data from the Patient (#2) file once entered even \n when they are signed into the facility that originally created \n the entry.\n \n 2. An issue where the incorrect pivot number and ward are \n sometimes saved in the PADE OUTBOUND MESSAGES file (#58.72) \n\n
\nRefer to the DG*5.3*1012 patch description for detailed information \nregarding this patch.\n\n
\nDG*5.3*163\nRevisions for Y2K.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - PRF SUPPORT\nRefer to patch DG*5.3*1024 in the FORUM Patch Module for a complete\ndescription.\n\n
\nDisplay postal code at the end of foreign addresses instead of at the\nbeginning.\n\n
\nPlease see the DG*5.3*997 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*1008 patch description for detailed information\nregarding this patch.\n\n
\n \nPlease see the DG*5.3*993 patch description for detailed information \nregarding this patch\n\n
\nPatch DG*5.3*1007 address two issues\n \n1. The Service Component (.04) field of the Military Service Episode \n(.3216) sub-file is not being extracted with the corresponding Military \nService Episode data\n \n2. Incorrect Help Text Displays on Registration Screen for Multiple Birth \nIndicator\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - TFL API UPDATE\nRefer to patch DG*5.3*1026 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*1016 implements the following:\nregistration then changed to OTH and subsequent MST re-screening \nresulting in no or decline.\n \n3. Provides a fix to ensure that the OTH Patient Inquiry option displays \nan ACTIVE OTH status if the patient transitions from OTH Emergent to OTH \nExtended.\n \n4. Provides a fix to ensure that the OTH Patient Inquiry option displays \nthe correct current Primary Eligibility.\n \n1. Provides a fix to ensure 'Reevaluate Eligibility' Mailman messages \nsent to DGEN ELIGIBILITY ALERT group are sent only for patients \nregistered as 'OTH' patients, per the defined business scenario.\n \n2. Provides enhancement to the 'Reevaluate Eligibility' Mailman message \nto be sent to DGEN ELIGIBILITY ALERT group for patients first registered \nas NON-OTH patients and screened positively for MST, but whose \n\n
\nPlease see the DG*5.3*1015 patch description for detailed information \nregarding this patch.\n\n
\nSee National Patch Module for description.\n\n
\nSee National Patch Module for description.\n\n
\nPlease see the DG*5.3*1031 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - HAC SUPPORT\nRefer to patch DG*5.3*1013 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*1017 addresses an issue of an incorrect display of a PRF \nAssignment status. This issue occurs when using the Record Flag Manual \nQuery [DGPF MANUAL QUERY] option because the current code does not \naccount for a status that was updated via REFRESH INACTIVE.\n\n
\nPlease see the DG*5.3*1014 patch description for detailed information \nregarding this patch.\n\n
\nThis patch corrects issues identified during the warranty period for \nComputerized Patient Record System (CPRS) v31b.\n \nIt also modifies the SCHEDULED ADMISSION file (#41.1), enabling it to\nnotify other software packages when an entry is added, updated or removed.\nThere are no end-user functionality changes in this patch.\n \nPlease refer to the patch description for the list of issues and \nadditional details.\n\n
\nDG*5.3*1025 (Registration) is bundled with IB*2.0*685 (Integrated \nBilling) in host file.\n \nThis patch introduces report to identify Former Service Members whose\nPrimary Eligibility changed from EXPANDED MH CARE NON-ENROLLEE to a new\nPrimary Eligibility with a verified eligibility status. These patients are\nno longer treated under the Other Than Honorable (OTH) authority (VHA\nDirective 1601A.02).\n\n
\nPlease see the DG*5.3*1041 patch description for detailed information \nregarding this patch.\n\n
\nThe Means Test thresholds for Calendar Year 2021 are distributed with this\npatch. The post-installation routine, DG531039P, will create a new \nsubentry (or replace an existing one) for calendar year 2021 in the MEANS\nTEST DATA (#250) multiple field of the MAS PARAMETERS (#43) file.\n \nPatch DG*5.3*1039 updates the thresholds for the Means Tests and the \nMaximum Annual Pension Rate.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - SIGI UPDATES\nRefer to patch DG*5.3*1033 in the FORUM Patch Module for a complete\ndescription.\n\n
\nDG*5.3*166\nRevisions for Y2K.\n\n
\nPatch DG*5.3*1023 addresses an issue where the Collateral Patient's \naddress is not being copied from the sponsor and will not display in the \nRF1 segment of the transmitted HL7 Z07 message.\n\n
\nWhen comparing the Date of Death with the current date during the \nvalidation process from an incoming Z11 message, it gets rejected with an \nerror message "Date of Death cannot be a future date", even if the date \nof death is at the same day with current date.\n \nThe issue will occur when the Date of Death for inpatients contains date \nand time, e.g., 3201028.0701. The code compares the Date of Death to the \ncurrent date format (variable DT), which does not include time, e.g., \n3201028.\n\n
\nThe patch modifies DG routines to provide data for OR RPC to display on \nCPRS screens and windows the following:\n-Presumptive Psychosis button and related information,\n-inactive Patient Record Flags indicator and related information.\n\n
\nBackup of DG*5.3*1048 on Mar 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the DG*5.3*1048 patch description for detailed information \nregarding this patch.\n\n
\nBackup of DG*5.3*1043 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch DG*5.3*1043 addresses the following issues:\n \n1. An UNDEFINED EN+37^DGRUDYN Error occurs regularly due to the\n DGRU INPATIENT CAPTURE item protocol being enabled.\n2. EWL needs to be removed as a selectable option from the New \n Enrollee Appointment Request (NEAR) Management Edit option\n Status.\n\n
\nBackup of DG*5.3*1049 on Apr 07, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the DG*5.3*1049 patch description for detailed information \nregarding this patch.\n\n
\nBackup of DG*5.3*1040 on Apr 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee NPM for description.\n\n
\nPlease refer to the National Patch Module for the detail of this \npatch build.\n\n
\nBackup of DG*5.3*1018 on Apr 27, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the DG*5.3*1018 patch description for detailed information \nregarding this patch.\n\n
\nBackup of DG*5.3*1042 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - TFL UPDATES\nRefer to patch DG*5.3*1042 in the FORUM Patch Module for a complete\ndescription.\n\n
\nBackup of IB*2.0*688, DG*5.3*1034 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nDG*5.3*1034 (Registration) is bundled with IB*2.0*688 (Integrated Billing)\nin host file IB_2_0_P688.KID.\n \nThis patch introduces reports to help Registration and Integrated Billing \napplication users identify veterans that are registered as eligible for \nOther Than Honorable and Presumptive Psychosis benefits. List their\nencounters and prescription in order to assist billing.\n\n
\nBackup of DG*5.3*1053 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch DG*5.3*1053 addresses the following issues(s):\n \n1. An UNDEFINED error, EN+37^DGRUDYN, occurs when a Patient's Ward does\n not have a RAI SUBSCRIPTION NUMBER (#900.1) field in the Medical\n Center Division (#40.8) file. Also, this patch will enable the \n RAI/MDS Inpatient event capture DGRU INPATIENT CAPTURE protocol\n disabled by patch DG*5.3*1043 and put it back on the Movement\n Events v 5.0 [DGPM MOVEMENT EVENTS] protocol menu.\n\n
\nBackup of DG*5.3*1055 on Jun 07, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nSee National Patch Module for description of changes\nincluded in this patch.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - TFL SITE LIST\nRefer to patch DG*5.3*1055 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch introduces reports to identify veterans that have been \ninformation for localized messaging can be input by the Clinical\nApplication Coordinator.\nregistered for Presumptive Psychosis (PP) benefits by using the workaround\nsettings, and need additional PP category settings in Registration\ndatabase. List their episodes of care and released prescription in order\nto assist billing.\n \nThis patch will also add any localized messaging text to the OTH button in\nCPRS if it is populated for the patient. The text "Call Registration Team\nfor Details." will always be displayed and cannot be edited. Any further\n\n
\nPlease see the DG*5.3*1027 patch description for detailed information \nregarding this patch.\n\n
\nBackup of DG*5.3*1044 on Jul 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the DG*5.3*1044 patch description for detailed information\nregarding this patch.\n\n
\nBackup of DG*5.3*1050 on Jul 14, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENTS - ADDITIONAL TFL UPDATE\nRefer to patch DG*5.3*1050 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch introduces the new report Potential Presumptive Psychosis \nthose eligible for Other Than Honorable (OTH) benefits. Per the Deborah \nSampson Act, Former Service Members who experienced Military Sexual Trauma\n(MST) are eligible for the full range of MST-related care-both mental\nhealth and other medical care.\nPatient Report [DG POTEN PRESUMPT PSYCHOSIS] to identify patients who have\nbeen registered in VistA using the Presumptive Psychosis (PP) 'workaround'\nprocess since 38U.S. Code 1702 was passed on 3/14/2013. The report is to\nbe used by Registration/Enrollment users to identify PP patients without\nPP category and select the PP category for them.\n \nThis patch implements two modifications to support benefits provided by \nthe Deborah Sampson Act for all Former Service Members (FSM) including \n\n
\nPlease see the DG*5.3*1045 patch description for detailed information\nregarding this patch.\n\n
\nPlease see the DG*5.3*1056 patch description for detailed information \nregarding this patch.\n\n
\nThis KIDS build is created to send out a new cross reference on the Date of\nDeath field. This new cross reference will call an Outpatient Pharmacy\nroutine (APSOD^PSOCAN3(DA)).\nThis code will discontinue all active prescriptions when a date of death is\nentered for a patient. This new xref is used with version 7.0 of Outpatient\nPharmacy.\n\n
\nPlease see the DG*5.3*1061 patch description for detailed information \nregarding this patch.\n\n
\nBusiness owner requested to add three procedure codes to trigger VistA to \nask the number of dialysis treatments. The codes are: 5A1D70Z, 5A1D80Z, \n5A1D90Z. \n\n
\nPlease see the DG*5.3*1065 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*1054 addresses an issue where a user reported their Vista\ninstance freezing when sending a PRF Query message to Austin MHV during\nthe Registration process.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - NEW DEMOGRAPHIC FIELDS\nRefer to patch DG*5.3*1059 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*1063 addresses 2 issues. \n If the HL array exists from a previous process it will attempt\n to use it first, before the HLFS & HLECH variables causing a\n potential discrepancy in the PID build segments which is causing \n an error at receiving sites.\n1. Certain ICD10 codes are not being found in the Diagnostic Code \n PTF Record Search [DG PTF ICD DIAGNOSTIC SEARCH] option due \n to the DGVDT variable being set to the ICD10 code set \n implementation date and passing that date into an optional\n search date parameter causing any ICD10 code activated \n after 10/01/2015 to not be returned by the search function. \n2. Discrepancies between PID encoding characters when using \n Record Flag Assignment [DGPF RECORD FLAG ASSIGNMENT].\n\n
\nThe Means Test thresholds for Calendar Year 2022 are distributed with this\npatch. The post-installation routine, DG1068P, will create a new \nsubentry (or replace an existing one) for calendar year 2022 in the MEANS\nTEST DATA (#250) multiple field of the MAS PARAMETERS (#43) file.\n \nPatch DG*5.3*1068 updates the thresholds for the Means Tests and the \nMaximum Annual Pension Rate.\n\n
\nThis patch will update the description in the Patient Address Update [DG \nADDRESS UPDATE] option to add parentheses around the file (#301.7) to \nmeet proper FileMan formatting.\n \n \nIt will also correct the name (#.01) OFFICE OF ECONOMIC OPPORTUNITY in \nthe Other Federal Agency file (#35) to be spelled correctly.\n\n
\nPatch DG*5.3*1052 addresses 3 issues.\n \n 3. An update to the Collateral Patient Register [DG COLLATERAL\n PATIENT] option to add a 'WARNING' message to notify users that\n they could potentially be editing the identity of a patient.\n \n 1. User reported an UNDEFINED ODS+2^DGDIS error after entering '^'\n at the 'Select the type of disposition:' prompt in the Disposition\n an Application [DG DISPOSITION APPLICATION] option.\n \n 2. User reported an UNDEFINED ANS+15^DGDIS error after entering\n '^' at one of multiple possible prompts in the Disposition an\n Application [DG DISPOSITION APPLICATION] option.\n\n
\nThis KIDS build is created to send out a new cross reference on the Date of\nDeath field. This new cross reference will call an Outpatient Pharmacy\nroutine (APSOD^PSOCAN3(DA)).\nThis code will discontinue all active prescriptions when a date of death is\nentered for a patient. This new xref is used with version 7.0 of Outpatient\nPharmacy.\n\n
\nPlease see the DG*5.3*1067 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*1069 addresses an issue introduced by patch DG*5.3*1054 that\neliminated PRF Queries to be sent to non-medical treating facilities.\n200CRNR is considered a VAMC and should therefor receive the PRF Query.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - PATIENT RECORD FLAG SUPPORT\nRefer to patch DG*5.3*1079 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - SEXUAL ORIENTATION UPDATES\nRefer to patch DG*5.3*1071 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the DG*5.3*1075 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*1064 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*1081 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*1074 adds one Treatment Specialty code to the SPECIALITY \n(#42.4) File and the FACILITY TREATING SPECIALTY (#45.7) File.\n\n
\nPatch DG*5.3*1083 addresses an undefined error due to the Census PTF\nrecord not being created correctly when a PTF is being closed out.\n\n
\nSee NPM for description.\n\n
\nUpdates the thresholds for the Means Tests in the MAS PARAMETERS (#43)\nfile and the Maximum Annual Pension Rate in the PARAMETER (#8989.5) file.\n\n
\nPlease see the DG*5.3*1082 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*1084 addresses 2 issues\n \n1. A reported issue where the potential for a blank error to be posted in\nthe error trap exists.\n \n2. The removal of the Agent Orange Registration # from the DG LOAD PATIENT\nDATA option screen 6 (MILITARY SERVICE DATA SCREEN) > Environmental\nFactors screen, with the approval from the business owners.\n\n
\nThis patch creates a new protocol that is executed whenever a field in \nthe PTF (#45) file that points to the ICD PROCEDURE (#80.1) file is\nmodified. See the associated patch description for complete details about\nthis patch.\n\n
\nPLEASE REFER TO THE PATCH DESCRIPTION ON FORUM FOR THE INSTALLATION \nINSTRUCTIONS.\n\n
\nPlease see the DG*5.3*1085 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - SIGI UPDATES\nRefer to patch DG*5.3*1088 in the FORUM Patch Module for a complete\ndescription.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - A19 SEXUAL ORIENTATION/PRONOUN \nPROCESSING\nRefer to patch DG*5.3*1092 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the DG*5.3*1090 patch description for detailed information \nregarding this patch.\n\n
\nThe purpose of this build is to cleanup note pointer issues in the sexual \norientation portion of the patient file. Please see the patch description \nfor a more detailed explanation.\n\n
\nSee National Patch Module for description of changes included in this\npatch.\n\n
\nMASTER VETERAN INDEX VISTA ISSUE - NAME OVERWRITE\nRefer to patch DG*5.3*1099 in the FORUM Patch Module for a complete\ndescription.\n\n
\nSee FORUM for Patch Description.\n\n
\nPatch DG*5.3*1078 addresses an issue with incoming Patient Record Flag \n(PRF) history records that are auto populating the CREATED BY SITE (#.09) \nfield of the PRF ASSIGNMENT HISTORY (#26.14) file, if the incoming field\nis null.\n\n
\nPlease see the DG*5.3*1093 patch description for detailed information \nregarding this patch.\n\n
\nImprove the HELP message for ADMIT DATE by removing all references to a \nfuture date.\n\n
\nBackup of DG*5.3*1101 on Aug 03, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nFIXES INACTIVE FLAG BUTTON IN CPRS FOR NON-VETS\n\n
\nPatch DG*5.3*1106 addresses an issue of the Created by Site (#.09) field\nof the PRF Assignment History (#26.14) file not being stored for certain\n'Edit' actions.\n\n
\nPlease see the DG*5.3*1098 patch description for detailed information \nregarding this patch.\n\n
\nADMIT DATE HELP TEXT MODIFIED FOR NO FUTURE DATES\n\n
\nSee National Patch Module for description.\n\n
\nBackup of DG*5.3*1105 on Nov 01, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nRESTORE GOLD VERSION OF ROUTINES DGPMV2 & DGPMV21\n\n
\nPlease see the DG*5.3*1103 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*1110 patch description for detailed information \nregarding this patch.\n\n
\nSee FORUM for patch description.\n\n
\nPlease see the DG*5.3*1109 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - SEXUAL ORIENTATION UPDATES\nRefer to patch DG*5.3*1112 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThe purpose of this patch is to add missing Name Component records in the \nPATIENT file #2 , and the NAME COMPONENTS (file #20). The missing name \ncomponent entries can cause the name to not update on Toolkit ADR Compare \nand to not display on the Master Patient Index Extended Patient data \ninquiry (MPI EDAT).\n\n
\nPrevent scheduled admission to inactive ward.\n\n
\nPlease see the DG*5.3*1111 patch description for detailed information \nregarding this patch.\n\n
\nExtend the allowable DBRS number digits from 6 to 7\n\n
\nPatch DG*5.3*1113 addresses an issue where certain PRF Flag Assignment\nupdates did not store the Created By Site (.09) field of the PRF\nAssignment History (#26.14) file after the release of patch DG*5.3*1078.\nThis patch will correct any records with a null value after the install of\npatch DG*5.3*1078. This patch also stores the site ID for any other\nlocations that stores a PRF Assignment History (#26.14) update within the\nRegistration software.\n\n
\nPatch DG*5.3*1122 Replaces offensive language in the DIALOG(#.84) file\n\n
\nSee FORUM for patch description.\n\n
\nPlease see the DG*5.3*1118 patch description for detailed information \nregarding this patch.\n\n
\nADD VALIDATION TO IS PRIMARY DIVISION FIELD\n\n
\nENHANCEMENT TO DGOTHBT2\n\n
\nPatch DG*5.3*1130 updates the message that is displayed when accessing\na patient that is marked as having a sensitive patient record.\n\n
\nPlease see the DG*5.3*1121 patch description for detailed information \nregarding this patch.\n\n
\n \n See the description for patch DG*5.3*87 in the National Patch Module.\n\n
\nSee National Patch Module for description.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - PROSTHETICS PATIENT CREATE API\nRefer to patch DG*5.3*1096 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the DG*5.3*1129 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*1132 addresses an issue of the incorrect Treating Specialty \nabbreviation being displayed in the Gains & Losses Sheet report.\n\n
\nPatch DG*5.3*1134 corrects an issue where the wrong email internal\nentry number (IEN) is being stored in the PTF RELEASE file (#45.83)\nwhen a PTF transmission results in multiple emails being generated.\n\n
\nPlease see the DG*5.3*1141 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - PREFERRED NAME DELETION\nRefer to patch DG*5.3*1139 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*1135 addresses an issue where PRF Transmissions will not \ncomplete if one of the records contain a 'DELETE' status for the DBRS \ndata.\n\n
\nPatch DG*5.3*1142 Updates the verbiage in the Description(#2) and\nText(#4) fields for file entry 261124 in the Dialog(#.84) file.\n\n
\nRefer to National Patch Module for details\n\n
\nPlease see the DG*5.3*1127 patch description for detailed information \nregarding this patch.\n\n
\nMASTER VETERAN INDEX VISTA ENHANCEMENT - PROXY ADD UPDATES\nRefer to patch DG*5.3*1131 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPatch DG*5.3*1144 Addresses an issue where when editing the \nELIGIBILITY(#.01) Field of the PATIENT ELIGIBILITIES SUB-FILE (#361) of \nthe Patient (#2) file.\n\n
\nPlease see the DG*5.3*1138 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*1147 patch description for detailed information \nregarding this patch.\n\n
\nPlease see the DG*5.3*1140 patch description for detailed information \nregarding this patch.\n\n
\nPatch DG*5.3*1148 addresses an issue where PRF Transmissions will not \ncomplete if the last PRF ASSIGNMENT HISTORY (#26.14) file entry it \nencounters has a DBRS (#.04) STATUS of "Deleted"\n\n
\nSee the National Patch Module for details. Patches DG*5.3*24, DG*5.3*75,\nDG*5.3*91, and DG*5.3*123 and SD*5.3*70 (which includes the patch\nDG*5.3*106) must be loaded before loading this patch.\n\n
\nSee National Patch Module for description.\n\n
\nPrevent erroneous Mileage Remark in Claim Enter/Edit.\n\n
\nSee National Patch Module for description.\n\n
\nSee NPM for description.\n\n
\nSee National Patch Module for description.\n\n
\nSee National Patch Module (NPM) for a description of the contents of this\npatch.\n\n
\nThis contains fixes related to output fixes for the PCMM software\n(distributed as SD*5.3*41).\n \nBoth SD*5.3*41 and SD*5.3*45 must be installed prior to loading this\npatch.\n\n
\nACRP Reports Menu (phase 2) options\n\n
\nUpdate of workload closeout dates for FY1999.\n\n
\nAs a result of Practice Profiling the need to track Primary Care Provider\nPlease refer to the patch description, release notes and user guide for a\ndetailed explination of the changes.\nis now manditory. PCMM has been chosen to collect and track this\ninformation. Patch SD*5.3*148 has been developed to help address some of\nthe current usability issues of PCMM. \n \nThis build will only hold the changes to the server/VISTA software.\nAdditional changes are being made to the client side and are being\ndistributed in another mechanism.\n\n\n
\nSee patch SD*5.3*151 in the NPM for complete information on this patch.\n\n
\nThis patch corrects the division name that displays for add/edits on the\nOutpatient Encounter Status Update Report.\n\nThis problem was reported in NOIS MIN-0898-41750.\n\n\n
\nUtility for re-flagging unsent FY1998 Q1 & Q2 NPCDB activity for \ntransmission.\n\n
\nSee NPM for description.\n\n
\nScheduling report issues\n\n
\nThis patch provides the capability to display and capture Global\nAssessment of Function (GAF) Scores and related data during appointment\ncheck-out. All new GAF data will be passed to the Mental Health system\nthrough Mental Health provided API's.\n\n
\n *** NOTE: This patch should be loaded during non-peak hours to minimize\n disruption to users. \n \n Scheduling calls ListManager incorrectly, causing some terminal\n emulators to become trapped outside the scrolling region. This\n problem was noted in NOIS message LAK-0798-31437. It affects the\n options Edit Outpatient Encounter [SCENI OP ENCOUNTER EDIT] and\n Correct Incomplete Encounters [SCENI IEMM ERROR CORRECTION]. The\n routine SCENIA2 has been modified to fix this defect. \n\n
\nSee National Patch Module for description.\n\n
\nEncounter 'Action Required' Report NOIS issues.\n\n
\nIEMM Issues\n\n
\nReport/purge option issues\n\n
\nScheduling output issues\n\n
\nDeleted encounter IEMM errors\n\n
\nACRP report issues\n\n
\nPerson Class date sensitivity for ROL segment\n\n
\nDuplicate encounter locks\n\n
\nThis is the release of Scheduling patch SD*5.3*157. The primary purpose\nof this patch is to enable Multiple Position Reassignment functionality.\nPlease refer to the patch description for further details and installation\ninstructions.\n\n
\nSee NPM for complete description.\n \n(1) This has an environment check routine to make sure SD*5.3*44 (ACRP) is\ninstalled.\n(2) In conjunction with DG*5.3*102, this modifies how occasion of service\nencounters are handled.\n(3) This has a post-install routine to output clinics that either have no\nSTOP CODE or an inactive one.\n\n
\nACRP report issues\n\n
\nDuplicate encounter cleanup utility.\n\n
\nContinue Function on Find Next Available Appointment fixed.\n\n
\nIEMM issues\n\n
\n \n \n \n \nAddressing NOISE call BIL-0299-30467: Y2K problem.\n\n
\nThis contains server changes for patch SD*5.3*169. Please refer to the\npatch module for a description of these changes.\n\n
\n \nUpdate Amb. Care database workload date for FY 1999.\n\n
\nOpen the GAF Score 90 day window to allow entry of a new GAf scores within\nthe window. This distribution will carry associated patch PX*1*64.\n\n
\nClinic Profile option creates a null subscript error when ALL clinics are\nselected.\n\n
\nPCMM output issues\n\n
\nThis fixes an infinite loop that occurs in the ACRP's nightly background\njob.\n \nFor a complete description, see the NPM.\n\n
\nACRP issues\n\n
\nFor a complete description, refer to the FORUM Patch Module\nfor patch SD*5.3*185.\n\n
\nCLINIC LIST OPTION CREATES AN ILLEGAL NUMBER ERROR\n\n
\nVHA Directive 98-058, "Sexual Trauma Counseling Care and Services"\nrequires that VHA provide care and counseling to veterans determined to\nhave been a victim of sexual trauma while the veteran was serving on\nactive duty. This patch will focus on the data collection for this\ndirective.\n \nThis is the Scheduling portion of the patch. See REGISTRATION DG*5.3*195\n\n
\n'Clinic Waiting Time' extract\n\n
\nACRP report issues\n\n
\nThis patch address NOIS OKL-1098-72014. It corrects a possible error\nin the Clinic Next Available Appt. Monitoring Report [SDOQM CLINIC\nNEXT AVAIL REPORT]. This error would occur if the clinic\navailability grid is not current for the selected clinic.\nThe change in the routine remaps the clinic availability grids used\nin the report if they are not present. Clinic Next Available Appointment\nMonitoring Report correction.\n\n
\n \nThis patch contains tools to help the user evaluate and convert PC Attending\nassignments to PC Practitioner assignments. It also provides a report to\nevaluate the existing preceptor relationship. These relationships will be\ncompared to the new business rules for Primary Care provider and Associate\nProvider.\n\n
\nModify Workload Closeout dates for FY2000 and Re-flag unsent NPCDB activity\n\n
\nMark unsent FY1999 Q1 & Q2 NPCDB activity for transmission\n\n
\nThis increases the AMB CARE LAG FOR ACK field (#704) of the SCHEDULING\nPARAMETER File (#404.91) to at least 7 days.\n \nFor a complete description, see the NPM.\n\n
\nSee patch SD*5.3*203 in the NPM for complete information on this patch.\n\n
\nThis build contains changes to the PCMM software for patch SD*5.3*177.\n\n
\nRoutine SDLTP Incorrectly setting FileMan Variable\n\n
\n \nno patients if it encounters an irregular data dictionary while building\nthe list. This patch restricts the cross-references the underlying\nFileman lookup will use to avoid potential irregularities.\n[NOIS: MRN-1099-40037, STL-0999-42707, ANC-0999-52492, WAS-0999-21980,\nSDC-0999-61114, LOM-0999-60895, REN-1099-60336]\n \n2. The KIDS build for this patch re-exports DG*5.3*239, a patch which\nwas included in the SD*5.3*177 KIDS build, but without instructions to\nupdate national package tracking. DG*5.3*239 is included in this build,\nwithout modification, except KIDS will perform the update which was\nDescription:\nmissed.\n \n3. GUI Multiple Assignment StringList(0) error. Server code in\nSD*5.3*177 introduced an error which caused most client users to receive a\nStringList error when attempting Patient Multiple Assignments. The\nerroneous code has been removed. [NOIS: PUG-1099-50905, SDC-1099-61954,\nSUX-1099-41704, BIR-1099-31652, FTL-1099-52214, NCH-1099-42392]\n \n4. Client/server synchronization verification [RPC: SCMC VERIFY C/S\nSYNC], which was enforced with SD*5.3*177, was creating unnecessary\n===========\nentries in files 404.45 and 404.46. Extraneous entries will be removed.\nThe RPC will be adjusted to avoid creating future extraneous entries. \n \n5. If a patient death is entered through the option DEATH ENTRY, no PCMM\ninformation is included in the PATIENT HAS EXPIRED mailman bulletin. This\npatch will include the information in the bulletin. [NOIS:\nBAY-0999-30405, DAN-0999-41617, CLL-1099-40444]\n \nThis patch is an emergency patch to address critical issues. It does not\nrequire a waiver.\n \n1. Since loading Fileman 22, some sites are not able to lookup patients\nusing the Patient Assignment form in the PCMM client; the lookup returns\n\n
\nThis patch addresses a combination of different NOISes using the same\nscheduling routines.\n\n
\nNext Available Appointment Wait Time\n\n
\nScheduling output issues\n\n
\nSee the national patch module for details.\n\n
\nThis build contains the changes necessary to perform three checks in the PCMM\nbe displayed.\n\nDuring the patient lookup, when the list of patients is displayed for selection,\nany patient that is an employee will have their SSN and date of birth screened.\nThe word sensitive will replace the respective information.\nGUI patient lookup.\n\nPCMM GUI lookup will now check for the existance of patients with duplicate\nlast name and last four of their SSN. A message dialog box will be displayed\nif one is found.\n\nAfter the selection of the patient PCMM will now check for the existance of\nmeans test information. If a means test is required a message dialog box will\n\n
\nSD*5.3*204, Phase III NOIS fixes.\n \nRelease build. \n\n
\nThis patch contains fixes to the ambulatory care module. See the National\nPatch Module for a complete description of the changes.\n\n
\nSee NPM for description.\n\n
\nY2K ENCOUNTER DATE SELECTION PROBLEM \n\n
\nBuild Clinic option does not map 60 minute grid correctly if creating\ndates with existing appointments\n\n
\nCPT MODIFIERS, MST\n\n
\nSD VISIT REPORT UNDEFINED ERROR\n\n
\nDatabase closeout removal and retransmission utility.\n\n
\nThis patch provides the capability to suppress GAF Scores for Collateral\npatients.\n\n
\nThe changes included in this patch are described in the description of\npatch SD*5.3*210 in the National Patch Module.\n\n
\nThis contains fixes for the PCMM RPC, the SC PATIENT LOOKUP.\nIt used to error out when value entered resulted in a large list of\npatients (e.g.'SMITH'). Now the limit is 500.\n \nFor a complete description, see NPM.\n\n
\nThe changes included in this patch are described in the description of\npatch SD*5.3*212 in the National Patch Module.\n\n
\nInconsistent Response to DISPLAY PENDING APPOINTMENTS Prompt\n\n
\nThis patch updates the NPCD Encounter Month Multiple (#404.9171) in the\nScheduling Parameter (#404.91) file with workload closeout dates for\nFY2001.\n\n
\nSee patch SD*5.3*230 in the NPM for complete information on this patch.\n\n
\nFix compile delay time for Clinic Pattern setup's and re-builds.\n\n
\nEncounter Date/Time Trans error 421 issues.\n\n
\nMental Health Stop Codes not requring a GAF score.\n\n
\nSee National Patch Module (NPM)\n\n
\nSee National Patch Module for description.\n\n
\nAPPOINTMENT MANAGEMENT DISPLAY FULL CLINIC NAME\n\n
\n1) This patch addresses a problem with the SDCANCEL, 'Cancel Clinic\n"NON-CANCELLED" appointments that same day, both earlier and later and\nacross all clinics. This problem was identified in NOIS NWI-0400-42186.\n \n2) The other problem occurred when making new appointments in SDM, 'Make\nAppointment'. When the option to display clinic availability was run and\na 'M' was entered at the 'DATE/TIME:' prompt to show additional days. If\nthe end of one month were on the screen, the first day of the next month\nwould sometimes get skipped. This would happen more for clinics that were\nonly open one or two days per week. The logic has been changed to include\nthe missing day. This problem was identified in NOIS BRX-0500-11068 and\nAvailability' option. The problem exists in the auto rebook section that\nBHH-0500-40921.\nruns by answering (Yes) to the 'Want to auto-rebook appointments now?'\nquestion. If a patient has an additional appointment for the same day at\nanother clinic that is set at an earlier time, then only the appointment\nwith the cancelled clinic would display on the CANCELLED CLINIC\nAUTO-REBOOK REPORT. However, if the other appointment was set for a later\ntime on the same day, then the MULTIPLE APPNTS. ON CANCELLED DATE message\nwould appear on the report. The logic has been changed to check for other\n\n
\nClinic Wait Time revisions\n\n
\nCWT fix\n\n
\nThe changes included in this patch are described in the description\nsection of patch SD*5.3*234 in the National Patch Module.\n\n
\nThis patch addresses ACRP Ad Hoc Report, [SCRPW AD HOC REPORT], issues as\n ELP-0800-72223 reported "DISK FULL", "Report Looping", reports\n "stopped irregularly", and inappropriate resource consumption\n problems when using the 'ACRP Ad Hoc Report' option. These problems\n were the result of a variable not being "New"ed or reset within\n routine IPRT^SCRPW28. Patch SD*5.3*232 resolves these issues.\nfollows:\n \n1. NOIS call REN-0900-61733 reported a "<PARAMETER>^SCRPW25" error.\n The absence of a "QUIT" statement at the end of the\n routine CPQ^SCRPW25 caused the error. Patch SD*5.3*232 resolves this\n issue.\n \n2. NOIS calls MAD-0400-41755,HIN-0500-41434,SDC-0800-61974,and\n\n
\nThe changes included in this patch are described in the description\nsection of patch SD*5.3*231 in the National Patch Module.\n\n
\nThis patch changes the add/edit encounter building and transmission logic\nto include both primary and secondary stop code values (if defined for the\ncorresponding hospital location).\n\n
\nMiscelaneous ACRP report issues\n\n
\nThis prevents creation of records in TRANSMITTED OUTPATIENT ENCOUNTER FIle\n(#409.73) for visits prior to 10/1/96. Post-installation cleans up\nexisting entries of this type.\n \nFor complete description see NPM.\n\n
\nCan't Edit Disposition Location.\n \nA description for this build can be found on the National Patch Module\nunder Patch SD*5.3*217.\n\n
\nACRP ENCOUNTER ISSUES\n \n1. Properly display and update Encounter classifications for Service\n Connected 50 to 100% patients.\n \n2. Substitute difficult to interpret messages on the Encounter 'Action\n Required' Report.\n \n3. Corrected MST validation logic for codes 7040, 704, 706 and 903.\n\n
\nClinic Wait Time issues\n\n
\nFY 2002 Update workload closeout dates.\nThis patch will add the 2002 dates to the existing table.\nThe database closeout fields for FY 2000 and 2001 will also\nbe updated to allow the current plus 2 previous years.\n\n
\nN XQORS INSTEAD OF K TO PRESERVE ORIGINAL VALUE.\n\n
\nRetransmit ACRP for July 26-29, 2001.\n\n
\nSee patch SD*5.3*231 in the NPM for complete information on this patch.\n\n
\nThe changes included in this patch are described in the description of\npatch SD*5.3*244 (Mill Bill - LTC/Visit/Medication Co-Pay) in the National\nPatch Module.\n\n
\nClinic Wait time enhancements.\n\n
\n Health Promotion Initiative extract\n\n
\nThis patch allows for calculation of the related close-out dates and for\ngenerating appropriate messages if applicable.\n\n\n
\nThis patch is in response to Item #22 in the Rossio Report. In the area\nof Means Test (MT) Deficiencies, Item #22 required that the Veterans\nHealth Administration (VHA) identify best practices for means testing and\nacquiring veterans' signatures at the local level and explore the\npromulgation of these best practices throughout the system. This patch\nincorporates into the scheduling software an Enrollment Application\nSystems (EAS) API which will inidcate whether to block or allow future\nappointments and appointment check-in/out for veterans based on their\ncurrent means test status.\n\n
\nAssociated patches: (v)YS*5.01*71 install with patch `SD*5.3*262'\nwindows utilities.\n \nLABEL FUNCTION\n===== ========\n \nACTLOC(LOC) Returns TRUE if active hospital location is\n referenced in variable LOC.\n \nCLINLOC(Y,FROM,DIR) Return a set of clinics from HOSPITAL\n LOCATION\n (v)XU*8*234 install with patch `SD*5.3*262'\n (Y=returned list, FROM=text to $O from, DIR=$O\n direction)\n \nINPLOC(Y,FROM,DIR) Return a set of wards from HOSPITAL LOCATION\n (Y=returned list, FROM=text to $O from, DIR=$O\n direction)\n \nHOSPLOC(Y,FROM,DIR) Return a set of locations from HOSPITAL LOCATION\n (Y=returned list, FROM=text to $O from, DIR=$O\n direction)\n (v)DG*5.3*447 install with patch `SD*5.3*262'\n \nAssociated NOIS:\n ================\n NONE\n \nTest Sites:\n ===========\n Minneapolis VAMC, MN\n Salt Lake City HCS, UT\n VA Health Care Network Upstate New York\n \n VA N. Florida/S. Georgia Veterans HCS\n VA North Texas HCS\n \n ROUTINE SUMMARY:\n ================\n The second line of the routine now looks like:\n \n ;;5.3;Scheduling;**[PATCH LIST]**;Aug 13, 1993\n Checksum Values\n \nThis patch is being release in support of Mental Health patch \n Routine Name Before Patch After Patch Patch List\n ------------ ------------ ----------- ----------\n \n SDWU N/A 1812546 262\n \nInstallation Instructions:\n ==========================\n \n Instructions for installation of the software are included in the \n Mental Health Assistant (MHA) patch YS*5.01* 71.\nYS*5.01*71. Please refer to the information contained in that patch for \ninstallation instructions.\n \nThis patch adds routine SDWU. This routine adds the following general \n\n
\nUpdate letter functionality for name standardization and removal of full \nSSN.\n\n
\n'SC Veterans Awaiting Appointments' option.\n\n
\nEnhancements and fix for the 'SC Veterans Awaiting Appointments' [SCRPW \nSC VETS AWAITING APPTS] option.\n\n
\nSee patch SD*5.3*268 in the NPM for complete information on this patch.\n\n
\nSee patch SD*5.3*271 in the NPM for complete information on this patch.\n\n
\nThis is the FY 96 quarterly update patch #1. The changes \nincluded in this patch are described in the description of patch\nSD*5.3*39 in the National Patch Module.\n\n
\n Please refer to the National Patch Module for complete details.\n \n This distribution contains the following enhancements:\n \n * For a user specified patient, mark all encounters that were\n rejected by the National Patient Care Database for retransmission\n \n * Do not include the DG1 HL7 segment when transmitting an Occasion of\n Service to the National Patient Care Database\n\n
\nThis patch contains the first release of a series of APIs that will \nappointment information will be moved to the GOTS database and \ndeleted from the Scheduling files.\nbe used to integrate M-based Class I, Class III and local applications\nwith the Government Off-the-Shelf (GOTS) Scheduling application being\ndeveloped by the Scheduling Replacement team.\n \nThe APIs contained in this patch will replace other methods of\naccessing the patient appointment information stored in the \nPatient sub-file(#2.98) and the Hospital Location sub-file \n(#44.001). During implementation of the new GOTS Scheduler, this \n\n
\nELECTRONIC WAIT LIST VERSION 1.0\n\n
\n \n^\n\n
\nThis patch addresses Geographic Means Test as a new Means Test Indicator \n copay required' or 'gmt copay required' for a means test indicator.\n \n2. Ambulatory Care validity checks have been modified to include the new \n GMT means test indicator.\n \n3. The Means Test/Eligibility/Enrollment Report [SCRPW MT/ELIG/ENROLLMENT\n RPT] has been modified to address the following:\n \n a. Include the new GMT COPAY REQUIRED means test indicator.\n \nunder Ambulatory Care Reporting. In addition, two reports under the \n b. Change the description of three existing means test indicators \n to reflect Enrollment changes to means test statuses of CAT A \n and CAT C. The means test indicators will refect the following \n changes:\n \n Old Values New Values\n -------------------- -----------------------\n AS SC CATEGORY A AS SC MT COPAY EXEMPT\n AN NSC CATEGORY A AN NSC MT COPAY EXEMPT\n C CATEGORY C C MT COPAY REQUIRED\nAmbulatory Care menu have been modified to address the new GMT indicator \n G GMT COPAY REQUIRED\n \n c. Change column descriptions in the report to reflect new \n changes.\n \n d. Include a new Group 8 Enrollment Priority to reflect \n Enrollment's addition of a new enrollment priority.\n \n4. The Means Test Visits & Uniques (OP3, OP4, OP5) report [SCRPW DVM \n MEANS TEST SUMMARY] has been modified to address Enrollment changes.\nand changes to descriptions of three other means test indicators.\n \n a. Include the new GMT COPAY REQUIRED means test indicator.\n \n b. Column headings have been changed to the following:\n \n Old Description New Description\n -------------------------------- ----------------------\n CATEGORY A SERVICE CONNECTED SC - MT COPAY EXEMPT\n CATEGORY A NON-SERVICE CONNECTED NSC - MT COPAY EXEMPT\n CATEGORY C MT COPAY REQUIRED\n \n GMT COPAY REQUIRED\n1. The algorithm logic in Ambulatory Care for determining the means test \n indicator in $$MTI^SCDXUTL0 has been modified to include patients with\n GMT COPAY REQUIRED status. A new API ($$PA^DGMTUTL) is used to\n determine whether a status of 'pending adjudication' will return 'mt\n\n
\nPatch to transmit data to AAC.\n\n
\nThis patch contains the first release of a series of APIs that will \nappointment information will be moved to the GOTS database and \ndeleted from the Scheduling files.\nbe used to integrate M-based Class I, Class III and local applications\nwith the Government Off-the-Shelf (GOTS) Scheduling application being\ndeveloped by the Scheduling Replacement team.\n \nThe APIs contained in this patch will replace other methods of\naccessing the patient appointment information stored in the \nPatient sub-file(#2.98) and the Hospital Location sub-file \n(#44.001,#44.003). During implementation of the new GOTS Scheduler, this \n\n
\nPCMM PATCH FOR SD*5.3*264\n\n
\nThis patch is being issued in conjunction with patches from Lab,\nRadiology, and PCE. For details, see the National Patch Module.\n\n
\nWhen the option PRINT SCHEDULING LETTERS [SDPRLETTERS] is run, the \npatient's confidential address will be printed if the patient has \nrequested that their Scheduling/Appointment correspondence be sent \nto the confidential address.\n\n
\nSCRPW24:\nAdded logic to handle GMT Copay Status.\nModified linetag ENES to call FileMan API EXTERNAL^DILFD.\nModified linetag ENROL to remove the statement- Q:X>366 "".\n \nSCRPW43:\nCorrected enrollment priority selection list at SCAT+10, adding a zero \nback in front of 'No Enrollment'.\n \nSDCLAS & SDCLAS1:\n\n
\nPCMM WORKLOAD TRANSMISSION TO AAC\nentry and reports\n \nAdded WORKLOAD (.08) field to PCMM HL7 EVENT file to differentiate HL7 \nmessage types\n \nAdded New type crossrefence to POSTION ASSIGNMENT HISTORY (#404.52) and \nTEAM POSITION (#404.57)\n \nAddress NOIS TAM-1102-32213 active position assignments only on FTEE \n\n
\nSee patch SD*5.3*289 in the NPM for complete information on this patch.\n\n
\nIn response to Policy Board (NLB) comment on the VHA Veterans Equitable\nupdating.\n \nCurrent policy establishes a requirement to block transmission of \noutpatient encounters (ACRP) to the National Patient Care Database if the\npatient's current Means Test status equals "Required." This leads to\nunder-reported workload and inaccurate information in national\ndatabases. \n \nSoftware has been implemented which blocks the ability to schedule future \nappointments for veterans whose financial assessment needs updating. VHA \nResource Allocation (VERA) process, the CBO requests the removal of:\nDirective 2002-019, dated April 4, 2002, provided guidance to facilities \non the implementation of the appointment blocking software. If a \nveteran's financial assessment needs updating, the software prevents the \nability to make future appointments for the veteran. This restriction \nshall also be removed at the request of the CBO. \n \n(1) the current restriction that blocks transmission of outpatient \nencounters (ACRP) to the National Patient Care Database (NPCD) if a\nveteran's updated financial assessment (Means Test) information is not\ncomplete, and \n(2) the restriction that blocks the ability to schedule\nfuture appointments for veterans whose financial assessments need\n\n
\n \nADD STATION NUMBER TO HL7 PRIMARY CARE MESSAGE\n\n
\nThe visit deletion process allows now to delete a dependent credit/stop visit\nif the primary stop/code addition visit has to be deleted after all entries\nare removed.\nThe Institution, if passed to PCE, is now accepted and properly filed.\n\n\n
\nSee National Patch Module for description.\n\n
\n1. A new report may be generated for selected patients from a list of \npatients entered by their names or SSN. That option was added to the \nexisting process of generating reports.\n2. The Summary option was modified to allow the user to specify which Stop \nCode Pair to include. This modification permits print selection to be limited\nto the clinic with the selected stop code pair.\n\n\n
\n1. Add code '370M' to PCMM HL7 ERROR CODE (#404.472) file.\n \n2. Fix routine SCMCHLR9 allowing '^' to quit 'PCMM Error Transmission \n Report' when abundant number of errors can be displayed.\n\n
\nDue to the changes brought in by patch SD*5.3*296, reports are needed to\nprocess, where at least one encounter within the Fiscal Year must include\na valid Means Test status for the patient. The patient will be included\non the report only if ALL the patient's encounters within the date range\nselected have a current MT Status (at encounter Transmission) equal to\nRequired. This will focus the list on patients who have no valid MT\nstatus in the National Patient Care Database (NPCD) for the date range\nchosen. The current FY is the suggested date range for this report.\nidentify patients who require a Means Test and who have had encounters \ntransmitted with a MT indicator of U. This patch provides the this\nreport.\n \nThe new report option is called Encounters Transmitted with MT Status of U\n[SCRPW TRANS MT EQUAL U RPT]. It will be added to the Incomplete Encounter\nReports [SCENI IEMM REPORTS MENU] menu when this patch is installed.\nThis report conforms to requirements related to the VERA allocation\n\n
\nThis is the Phase I patch of the Transitional Pharmacy Benefit Project\n1) The patient must be a veteran.\n \n2) The veteran must be enrolled for VA health care system before July 25, \n2003.\n \n3) Before July 25,2003, the veteran must have requested their first \n primary care appointment with the VA.\n \n4) The veteran must have no active prescriptions dispensed by the local \n VHA pharmacy, excluding Supply and Investigational items, for the past \n(TPB). This project provides functionality for the "Medication Prescribed \n 485 days from October 22, 2003.\n \n5) The veteran must be waiting more than 30 days for their first \n appointment with a Primary Care Physician on or after October 22, \n 2003, or the veteran is deemed eligible via an Electronic Wait\n List/Scheduling extract run at each local site.\n \n \nWhen the post-init of the combined build is run, the routines exported in\npatch SD*5.3*300 will scan the PATIENT file (#2) and the SD WAIT LIST\nby Non-VA Physicians" to accommodate the Veterans Health Administration \nfile (#409.3), and will build a temporary storage global of patients who\nmay be eligible for this benefit.\n \n \nThis patch is being sent out as a combined build, along with patch \nPSO*7*145.\n \n \nFor KIDS Build and documentation retrieval information, please refer to \npatch PSO*7*145.\n(VHA) Directive 2003-047 that allows Department of Veterans Affairs (VA) \nto furnish medications from non-VA physicians. It mandates that for\neligible veterans that meet certain criteria, VHA will fill prescriptions\nwritten by non-VA physicians and dentists. To determine eligibility, a\npatient must meet the following criteria:\n \n\n
\nThis API will return 0,1,-1, depending on whether the patient has an \nappointment.\n\n
\nRelease III of the Scheduling Replacement APIs.\n\n
\nSee patch SD*5.3*307 in the NPM for complete information on this patch.\n\n
\nThis patch releases functionality that provides Outpatient Pharmacy V. \ninformation is released in this patch.\n \nA change has also been made to the call Outpatient Pharmacy V. 7.0 uses \nto determine a default institution and station number, when a patient is \nmanually added to the TPB ELIGIBILITY file (#52.91). The default \ninstitution and station number is currently retrieved from the clinic of \nthe nearest scheduled appointment for that patient. The change made in \nthis patch is to first look for the nearest primary care appointment, and \nuse that clinic to get the default institution and station number. If \nthere is no primary care appointment for that patient, then the software \n7.0 information about primary care appointments and encounters. In \nwill look for the nearest appointment, regardless of whether it is a \nprimary care appointment, and use that clinic to determine the default \ninstitution and station number. \nOutpatient Pharmacy V. 7.0, when a patient is displayed on the patient \ninformation screen, and that patient is eligible for the Transitional \nPharmacy Benefit, that patient's nearest primary care appointment or \nencounter will display. That functionality will begin with the release of \npatch PSO*7*146. The primary care criteria is based on the DSS ID and \nCredit Stop Pairs that were defined in patches SD*5.3*300 and \nPSO*7.0*145. The functionality to provide Outpatient Pharmacy V. 7.0 this \n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\n The changes included in this patch are described in the description\n of patch SD*5.3*74 in the National Patch Module.\n\n
\nSee patch SD*5.3*311 in the NPM for complete information on this patch.\n\n
\n \nencounter. The report identifies the encounter, finds any progress note \nassociated with the encounter, it looks at the progress note and reports \nthe date the PN was signed by the provider. It then looks at the results \nand reports the encounter as compliant or non compliant based on \nnationally or locally defined criteria.\nPatches SD*5.3*292 and TIU*1.0*168 combined build.\n \nOQP is interested in gathering data for a performance indicators involving\nScheduling and TIU. \n \nThis patch addresses the indicator; it measures the percentages of \noutpatient encounters in ambulatory care with a completed or amended \nelectronic progress notes signed by the primary care provider for that \n\n
\nThis patch addresses the ENDOFILE error message received in 'Cancel Clinic\nCMO-0600-41899 CANCEL CLINIC AVAILABILITY GIVES END OF FILE ERROR\nMAC-0200-60343 UNDEFINED SYMBOL, DH IN SDUNC ROUTINE.\nAvailability' [SDCANCEL] when queuing the print job is not performed. It \nalso addresses 'Restore Clinic Availability' [SDRESTORE] when an \nundefined variable (DH) occurs due to missing appointment patterns for \nthat day of week.\n \n \nThis patch addresses the following NOIS message(s):\n---------------------------------------------------\n\n
\nThis is an emergency patch for the routine SCMSVUT1.\n\n
\nThis patch fixes a problem with one of the options distributed in patch\nSD*5.3*292. When users selected to run the [SCRPW PM DETAILED REPORT]\nPERFORMANCE MONITOR DETAILED REPORT and the users opted to run the\nreport for individual providers, the report will fail to generate any\ninformation because of a bad reference to one of the arrays in routine \nSDPMUT2.\n\n
\nThis patch will provide patient appointment wait time statistics to the\nNational Database in Austin, Tx. An initial seeding routine will scan\npatient appointments from 9.01.2002 to present and appointment data\nmeeting specified criteria will be wrapped in a HL7 batch message and\ntransmitted to AAC. Subsequent, bi-weekly, transmissions will update the \nNational Database.\n\n
\nThis report was requested in support of the Transitional Pharmacy Benefit \nor not attended their appointments and then been rebooked to TPB \nassociated clinics. If so, their cancellation and rebook details are \ndisplayed. Otherwise the appointment closest to the report run date is \nshown.\n \nThis patch adds a new option, Transitional Pharmacy Benefit Deferred Appt \nReport [SD TRANS RX CANC APPT REPORT] to the Outputs menu [SDOUTPUT].\n \nRoutine SDPHARM1, which provides scheduling information to the Outpatient \nPharmacy V 7.0 package, has been updated to use the new Scheduling \nproject. It will be used by each medical center to report the number of \nApplication Programmer Interface calls, instead of direct global reads to \nretrieve data from the APPOINTMENT subfile (#2.98) of the PATIENT file \n(#2).\n \nThis patch removes the routines SDPBE and SDPHARM which generated \ninformation on Transitional Pharmacy Benefits Eligibility in an earlier \nphase of the project and are no longer required.\npatients who have rescheduled their primary care appointment until the \nmedication supplied under the Transitional Pharmacy Benefit program is \nexhausted.\n \nA query is made to the Outpatient Pharmacy V. 7.0 package to get a list \nof TPB eligible patients for a given date range. From this list, the \npatients' appointments are examined to determine if they have cancelled \n\n
\nACRP AD HOC REPORT DOES NOT RECOGNIZE PRIMARY DX\n\n
\nThis fixes the problem with PCMM's Team's Patients report not aborting\nwhen up-arrow is entered.\n \nSee NPM for complete description.\n\n
\nUndefined variable in Trend of Facilities Report.\n\n
\nThis patch contains several enhancements and modifications to the\n developed by AAC and the Messaging and Interface Services Team.\n - New report options added to print Transmission and Acknowledgement\n Summaries. \n - Release Notes have been updated with additional, detailed\n technical information.\n - An expanded 409.6 file will permanently store detailed transmission\n information.\nPatient Appointment Information Transmission, originally released in \npatch SD*5.3*290.\n \n - New components are added to SCH.11, SCH6, and SCH.7 segments of\n HL7 transmission.\n - The appointment selection logic for update runs has been modified.\n - Rejection error codes have been expanded.\n - Independent reports, reflecting the transmission status, have been \n\n
\nConfidential Address Imm\n\n
\nRollup of Additional Encounter Performance Measures to AAC.\n\n
\nThis patch includes some modification and fixes to PAIT.\n\n
\nFix locking mechanism in SCRPW16 and dis-allow today's date from checkout \nprocess. Also, the Encounter Action Required Report is incorrectly \nindicating Environmental Contaminants when it should be MST.\n\n
\nThis patch fixes an undefined variable error in option SCENI IEMM ERROR \nCORRECTION.\n\n
\nRemove form feed before the each patient appointment letter when printing \nscheduling letters. Change the state printed in the address to the 2 \nletter abbreviation.\n\n
\nUndefined variable error in routine SCRPI01.\n\n
\nTable File update: TRANSMITTED OUTPATIENT ENCOUNTER ERROR CODE File\n(#409.76). Also fix to prevent sending MM Messages over 100K.\n \nSee NPM for complete description.\n\n
\nPERFORMANCE MONITOR SUMMARY REPORT ERROR\n\n
\nNew Scheduling Replacement API\n\n
\nREMOVAL OF CHECK OUT PARAMETERS FOR CLINIC PROFILE.\n\n
\nThis patch corrects a problem associated with NOIS ISB-0700-30733 which \nhas error codes in file TRANSMITTED OUTPATIENT ENCOUNTER ERROR CODE file \nincorrectly marked as VISTA rather than NPCD.\n\n
\nIncomplete Encounter Errors still appear on error list after being \ncorrected until user selects Retransmit Encounter. They should be \nautomatically removed after being corrected.\n\n
\nInclusion of additional fields for HL7 message transmissions to AAC. \nAlso removes reference to 'DSS' in mail group SD PM NOTIFICATION TIU.\nThe routine SDPMHLS, responsible for creating the structure of the HL7 \nmessage, has been modified to allow inclusion of data for \nprogress notes pending signatures and encounters without progress notes.\n \nTotals for unique encounter providers and unique stop codes at the \ndivision level should also now match the sum of the totals for these \nvalues of each facility in that division.\n \n\n
\nCORRECT 'ASTAT','T' CROSS-REFERENCE IN THE PCMM HL7 TRANSMISSION LOG FILE \nAND SET THE STATUS FIELD TO 'A'.\n\n
\nFix form feed problem between report and patient letters when \nauto-rebooking a single "No-Show" appointment.\n\n
\nSee National Patch Module for description of changes included with this\nbuild.\n\n
\nD140 Error Code fix.\n\n
\nDSS Request for FY2005 Stop Codes\n\n
\nBAD ADDRESS INDICATOR NEEDS TO STOP PRINTING SCHEDULING LETTERS.\n\n
\nFix for 9020 Errors/MST for non-vets.\n\n
\nFUTURE APPOINTMENTS NOT PRINTING ON ROUTING SLIPS. \n\n
\nCPT Codes not printing and Error Message Cleanup\n\n
\nTwo main purposes of this patch are:\n- inclusion of Combat Veteran and Military History into PAIT\n- automatic verification of PAIT transmission data via a Forum.S.Server\nAdditionally, several fixes/modifications are included following their \nidentification in NOIS calls.\n\n\n
\nSee FORUM's National Patch Module for a complete description.\n\n
\n1. Correct Wait List Parameter Edit for Service/Specialty for '^'\n deletion error.\n \n2. Correct Wait List Enter/Edit pointing to different Service/Specialty\n after data entry when viewing Inquiry or Report.\n\n
\nAction required for inpatient appointments.\n\n
\nERROR IN SDM0 FOR DIR(0) STRING.\n\n
\nNo Transmitted Data Message.\n\n
\n \n1. UNDEFINED IN WAIT LIST REPORTING\n2. MUMPS ERROR IN WAIT LIST STAT REPORT\n3. NULL SUBSCRIPT IN WAIT LIST REPORTING \n\n
\nACRP Report error. CRI1+17^SCRPW45. The report ODPS Outpatient \nDiagnosis/Procedure Code Search generates an error when the "'" single \nquote is entered at the IF: prompt.\n\n
\nTHIS PATCH ADDRESS A PROBLEM WITH THE SCRPW SC VETS AWAITING APPTS \nREPORT. IF A PATIENT HAS NO DATE ENTERED IN THE PATIENT FILE THIS PATIENT \nIS INCORRECTLY BEING REPORTED ON THIS REPORT. A CORRECTION WAS MADE TO \nCORRECT THIS ERROR.\n\n
\nCORRECTS DUPLICATE DISPLAY AND LETTERS IN CANCEL AVAILABILITY.\n\n
\nTHIS PATCH CORRECTS 2 PROBLEMS. THE FIRST FIXES THE DATE PROMPT IN THE \nPRE-APPOINTMENT LETTERS. THE SECOND GIVES THE ABILITY TO PRINT A \nCANCELLATION LETTER WHEN RESCHEDULING AN APPOINTMENT FOR THE SAME \nDATE/TIME IN A DIFFERENT CLINIC.\n\n
\nDis-allow scheduling appointments on days where availablity has been \ncanceled via the option "SET UP A CLINIC".\n\n
\n The changes included in this patch are described in the description\n of patch SD*5.3*71 in the National Patch Module.\n\n
\nScrolling past enrollment data in Scheduling Management.\n\n
\nPRE APPT AND CLINIC CANCELLED LETTERS NOT PRINTING CORRECTLY.\n\n
\nPrevent the Ambulatory Care Transmission History Report from being \nstarted if it is already running.\n\n
\nFix problem reading date input and reporting of clinic activity and \navailability on the Appointment List. \n\n
\nCORRECTION FOR SENDING ALERTS FOR MISSING ENCOUNTER POINTERS.\n\n
\nDiscrepancy with Amb Proc Report\n\n
\nThis patch updates file 40.7 (Stop Codes).\n\n
\nAdd stop code 643 "Send-Out Procedures - Radiology" to file 409.45. \n(OUTPATIENT CLASSIFICATION STOP CODE EXCEPTION)\n\n
\nAPPT W/L OVERDUE REPORT\nEWL QUESTIONS\n\n
\nSee National Patch Module for description\n\n
\nCorrect several errors and/or problems with the Wait List reports.\n\n
\nAppointment availability not being restored properly on cancelled \nappointments.\n\n
\nThis patch will address a problem reported with the option ACRP AD HOC \nREPORT. The site reports that test Patient are printing on the report and \nwould like them screened and not print on the report.\n\n
\nUnable to inactivate stop code on wait list.\n\n
\nBAD ADDRESS INDICATOR W/LETTERS.\n\n
\nPractitioner's Patients List Report no longer prints the Means Test \nStatus Code.\n\n
\nCorrect functionality in Appointment Management so that when a user goes \nto assign a patient to a Closed PCMM Team, they receive a warning message \nthat the selected team has been closed.\n\n
\nFIX ISSUE WITH CANCEL CLINIC AVAIL AND ISSUE WITH DISPLAY CLINIC AVAIL RPT\n\n
\n \nErrors in SDWLQOF/SDWLQOI/SDWLQSR/SDWLROI/SDWLRPS2/SDWLRQ1/SDWLRQ2/SDWLRSR\n 1. Print directly to printer\n 2. No default for $SELECT\n 3. EOF error for DIR read in tasked job\n 4. Unsupported entry point call in ZTLOAD instead of %ZTLOAD\n\n
\nLast and Next appointment dates to not print on the Detailed Patient \nAssignment report.\n\n
\nPrimary Care Management Module - SD*5.3*41\n\n
\nEncapsulated APIs\nSDAPI - 2 New Fields Added\nNEXTAPPT / GETAPPT / PATAPPT / GETPLIST - Modified to call SDAPI instead \nof direct calls to the Global.\n\n
\nFix null institution, wait list type and clinic problem.\n \nModify Wait List Cleanup option to print report of null fields: \ninstitution, wait list type and wait list clinic.\n \nCorrect problem where patient is not removed from Wait List for same \nselected clinic during disposition.\n\n
\n \n \n \nAdds appointment info to file 409.3 and provides option to disposition EWL\nentries after making appointment. Creates background job to monitor EWL\nWait List types and notifies user by mailman of changes.\n\n
\nThis patch will provide the ability to sort routing slips by physical \nlocation.\n\n
\nError Undefined variable SDATA("BEFORE","STATUS")\n\n\nUNDEFINED VARIABLE ERROR IN ROUTINE SDAMC\n\n
\nAppointment Management list of appointments does not display "Checked In" \nappointments.\n\n
\nAssociated Clinic not printing on Practitioner's Patients and Team \nPatient Listing reports. This patch will also back out changes made in \npatch 432.\n\n
\nThe direct reference to the INJURING PARTIES INSURANCE company field, \nlocated in the DISPOSITION multiple of the PATIENT file, has been \nremoved. This field must be encapsulated from direct reference and is not \navailable via an API. After installation of this patch, the option \nSDPATIENT [Patient Profile MAS] will display "UNSUPPORTED" for the \nInjurinng Parties Insurance Company.\n\n
\nCORRECTION OF AVAILIBILITY DISPLAY REPORT.\n\n
\nSee national patch module descriptions for SD*5.3*77 and DG*5.3*102.\n\n
\nThe Institution selection in several EWL reports only includes\ninstitutions that have been set up via EWL Parameter enter/edit. Logic\nchanged to allow PCMM team institutions, as well as, those set up via EWL\nParameter enter/edit.\n\n
\nThis patch updates the Stop Code Clinic File 40.7.\n\n
\nPLACE STOP CODE 690 ON THE EXEMPTION LIST.\n\n
\nThis patch permits inter-facility transfer of Electronic Wait List \nVeterans.\n\n
\nSD*5.3*459 HURRICANE KATRINA (ERI)\n\n
\nADDITIONAL PERFORMANCE DATA INTO AUSTIN\n\n
\nThis patch correct multiple problems in the Scheduling 5.3 package. \nFirst, the sensitive Patient warning was not being displayed in the \noption, "Expanded Display".\n \nA form feed was removed in routine SDDPA to conform with VA \nstandards and reduce waste.\n \nDisplay the inactive clinics messages corrected.\n\n
\nUser can't Remap a Holiday for site only.\n\n
\nEncounters Transmitted with MT Status of U, need to flag patients on \nreport who No Longer Require a means test.\n\n
\n Veterans Health Survey Extract\n\n
\nError codes not returned in documented node.\n\n
\nUsers cannot disposition deceased patients from wait list\n\n
\nNo Show / No Action Taken on No Show Report.\n\n
\nThis patch addresses the Service Connection Priority assignment and \nverifies priority in a VA Taskman nightly batch job.\n\n
\nThis patch updates file 40.7.\n\n
\nNo Show Letters printing for Checked Out and No Action Taken appts.\n\n
\nPMS VISTA CHANGES TO SUPPORT EDB (EVC1 Early release)\n\n
\nThis patch will allow keeping the wait list entry status up to date with \nany related appointment cancellation by clinic, performed either for a \npatient or for a clinic. The related EWL entries will be opened following \nthe cancellation and optionally closed again if rebooked.\n\n
\nSee national patch module descriptions for SD*5.3*85 and DG*5.3*102.\n\n
\nInstitution missing in file 409.3\n\n
\nAmbcare Data into Austin - POW Status Rejects\n\n
\nWait list statistics report column fix\n\n
\nProvide the ability to place veterans on multiple teams and/or\npositions.\n\n
\nThis patch updates the CLINIC STOP (40.7) file.\n\n
\nAPI to return encounter or appointment date/time for a patient that\nStand-alone option SD IMO EDIT added to prompt for "Administer Inpatient\nMeds?" for a clinic.\ncan receive inpatient medication from an authorized clinic.\n \nAdditional field "Administer Inpatient Meds?" added to Hospital Location \nfile (44).\n \nPrompt added for "Administer Inpatient Meds?" field during option SET UP \nA CLINIC.\n \n\n
\nCorrect creation of ASDCN xref.\n\n
\nFix problem with Clinic Availability report with clinics that have a \nfuture start date.\n\n
\n1. Problem with Cancel Clinic Availability allowing overlap of cancelled\n time sectors.\n \n2. Restore Clinic Availability issuing bogus message "CLINIC DOES NOT \n MEET ON THIS DATE".\n\n
\nChange to text description for D00 and D000 errors. Also, new logic \nadded to check for inactive person class.\n\n
\nEncounters need CPT codes and a Primary DX before being 'Checked Out'.\nPost-install looks for Austin rejects w/o a Primary Dx. For full details,\nsee NPM.\n\n
\nThis patch will prevent multiple instances of the PCMM HL7 TRANSMISSION \nfrom occurring.\n\n
\nFix undefined variable error at INIT+4^SDAMEP1.\n\n
\nLinks appointment to consult/procedure.\n\n
\nPCMM Team/POS Wait List not screening by Institution/Team.\n\n
\nFix problem with ACRP Ad Hoc Report.\n\n
\nCorrect creation of ASDCN xref.\n\n
\npatch corrects a problem in calculating the patients ENROLLMENT\nSTATUS on the EWL PATIENT file.\n\n
\nThis patch provides updates to the CLINIC STOP (#40.7) file.\n\n
\nFixes to the Display Clinic Availability grid and the Set Up a Clinic \nmenu option.\n\n
\nSee National Patch Module for description.\n\n
\nThis patch provides an update to file 40.7.\n\n
\nThis patch will enforce business rules in PCMM and inactivate patient and\nprovider PCMM assignments if they are no longer active based on the\nbusiness rules.\n \nPlease refer to the PCMM Release Notes/Installation Guide for complete \ndetails.\n\n
\nOption 'Appointment List' [SDLIST] has been modified to call a Scheduling \nAPI to retrieve appointment data. Patient phone number has been added to \nthe report. Service Connected percent has been added to the 'Other\nInformation' section.\n\n
\nOptions 'Veterans Without Activity Since A Specified Date' [SCRPW \nVETS W/OUT ACTIVITY' and 'SC Veterans Awaiting Appointments' [SCRPW SC\nVETS AWAITING APPTS] have been modified to display a disclaimer.\n\n
\nCORRECTION OF SYNTAC ERROR IN EWL/PCMM API.\n\n
\nOptions 'Future Appointments for Inpatients' [SDWARD] and 'Inpatient\nAppointment List' [SDAPP INPT] have been modified to call a Scheduling API\nto retrieve appointment data.\n\n
\nDuplicate Patient Appointments for Clinic View\n\n
\nCorrection to Performance Monitor Report, etc.\n\n
\nThis patch updates the Clinic Stop File 40.7\n\n
\nSee National Patch Module\n\n
\nEncounters dated on or after March 1, 2007, that contain Stop Code 101 \nneed to be changed to Stop Code 130. This build contains a post-init \nroutine which will make the applicable updates.\n\n
\nSee patch description in national patch module.\n\n
\nInactivate menu option SD TRANS RX CANC APPT REPORT per HSD&D request. \nAlso, fix errors occurring with several Scheduling options: Clinic \nAvailability Report, Clinic Assignment Listing, No Show Report, Patient \nProfile MAS and Cancelling Appointment.\n\n
\nThis patch addresses several issues related to Scheduling, including one\nrelated also to integrity of the REQUEST/CONSULTATION file (#123) \naccessed from a scheduling routine.\n\n
\nPlease refer to patch SD*5.3*519 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nEWL ENROLLEE RE-CALCULATION.\n\n
\nOption 'Retroactive Visits List' [SDAM RPT RETROACTIVE LIST] has been\nmodified to call a Scheduling API to retrieve appointment data.\n\n
\nFiscal Year 2008 Updates to Clinic Stop (#40.7) file.\n\n
\nCheck-Out API Bullet-proofing. For complete details, see NPM.\n\n
\nSEE PATCH MODULE ON FORUM\n \nOEF OIF TRANSITIONAL PATIENT ADVOCATE\n\n
\nFix multiple errors caused by a "lingering" "C" node in Hospital Location \nfile (#44).\n\n
\nPlease refer to patch SD*5.3*516 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nPlease refer to patch SD*5.3*495 in the National Patch Module for a\ncomplete description of this patch.\n\n
\n This is an intermediate solution that has to prevent incorrect \n inactivation. The checksum of both routines is the same as before \ninstallation of patch SD*5.3*498.\ninactivation.\n Routines SCMCTSK1 and SCMCTSK2 are restored to their original code which\n will force the functionality being active before installation of\n patch SD*5.3*498.\n \n Patients assigned to the Team Position with providers change will be\n excluded from evaluation for potential inactivation, as it was introduced\n with patch SD*5.3*297, and no patient will be incorrectly marked for\n\n
\nEWL ENROLLEE RE-CALCULATION. REPLACEMENT PATCH FOR SD*5.3*486 WHICH \nENTERED IN ERROR DUE TO A CORRUPT 'B' CROSS-REFERENCE IN EWL CLEAN-UP \nfile (#409.39).\n\n
\nOutpatient Encounter Workload Statistics report includes non-count clinic \nencounters and it should not. There is also a fix to the Trend of \nFacility Uniques by 12 Month report for an <Undefined> error.\n\n
\nFix problem with ACRP transmission validation logic.\n\n
\nFY08 Supplemental Update to the Clinic Stop (#40.7) file. Adding 1 new \ncode.\n\n
\nFixes non-printing of Inpatient Provider in Inpatient MailMan messages.\nFixes subjects for PCMM MailMan messages removes full name and full SSN\nfrom message subject. For complete description, see NPM.\n\n
\nThis patch address three enhancements to the EWL Wait List. First, a new \nreport is created to break down the wait list specialties/locations by \n<30,>30, and >120 totals. Second, the Wait List Static report will \nexclude 'PREVIOUS REMAINING' and '# REMAINING'. Finally, the EWL display \noutput will ask if only 'OPEN' entries are to be displayed.\n\n
\nFix several issues including problem with cancelling clinic availability, \nthe Clinic Assignment listing and the No Show report.\n\n
\nThis patch adresses the following PCMM issues:\n- Proper unflagging both patients and providers if criteria are met\n- Verification of patients assigned to a position with changed providers\n- Multiple providers verification for a valid appointment\n- Any scheduled time on the 15th and the last day of a month for the SCMC\n PCMM NIGHTLY TASK should generate expected messages. \n\n
\nMakes corrections to Remap a Clinic, Clinic Availability report, Clinic \nWorkload report and the Provider/Diagnosis report.\n\n
\nThis patch corrects\n1 The Associated Clinic display for PCMM reports.\n2 The display of appointment information on PCMM reports.\n3 Correct lookup if position IEN is 1.\n\n
\nThis patch will correct a problem with the Patient Team/Position\nAdditionally, the patch will update SD WAIT LIST REPORTS MENU with all\nexpected thirteen options. Five of them were unintentionally detached with\npreviously released patch SD*5.3*297.\n \nA problem with the Preceptor Link being updated correctly will also be \ncorrected. In some cases, the user receives a message that the Preceptor \nPosition requires a staff assignment. In other case, the user just isn't \nallowed to remove the staff assignment or the preceptor assignment. The \nconfusion comes in as the Preceptor Team Position may be inactive but the \nstatus of the Preceptor link may see it as active since it was not \nassignments not showing correctly within the CPRS package. The following\nupdated correctly. Changes are not saved because the "AD" MUMPS \ncross-reference is not being updated correctly. This cross-reference is \ntriggered by the PRECEPTOR TEAM POSITION (#.06) field of the PRECEPTOR \nASSIGNMENT HISTORY (#404.53) file.\nerror will also be fixed: <SUBSCRIPT>SORT+39^SCMCHLR2 while working in the\nPCMM Error Processing option.\n \nThe Outpatient Profile file (404.41) fields 201-204 will be distributed\nwith the proper documentation as currently it states incorrectly that\nthese fields are "Not Implemented".\n \n\n
\nThis patch addresses several EWL, PAIT, and Scheduling issues.\n\n
\nProvide Fiscal Year 2009 updates to the CLINIC STOP (#40.7) file, as \nrequested by the Decision Support Services (DSS) office.\n\n
\nFix two <Undefined> errors which occur when running the ACRP Ad Hoc \nReport with Current Enrollment Status or Perf Monitor Date Signed\nas one of the Report Limitations.\n \nThis patch also fixes a <SYNTAX> error which occurs when running the\nACRP Ad Hoc Report with Perf Monitor Acceptable Provider as one of the\nReport Limitations.\n\n
\nFixes problem in Patient Listing w/ Team Assignments Report. For complete\ndetails, see NPM.\n\n
\nFixes to the Clinic Utilization Statistical Summary and Clinic Workload \nreports.\n\n
\nPCMM Phase III Enhancements.\n\n
\nThis patch corrects the Appointment Listing, so that clinic names print \nand also corrects Set Up a Clinic so that a Midnight to 8am clinic can be \nset up.\n\n
\nThis patch addresses five fixes related to PCMM, EWL and PAIT. \n\n
\nThis patch addresses several EWL, PCMM and Scheduling issues reported in \n 230475 (d)\n5) HD0000000271138 - Existing PAIT documentation updates.\nthe following Remedy tickets, and update to PCMM and PAIT documentation.\n \n1) HD0000000188897 - SD AMB PROC MGMT REPORT not accurate\n2) HD0000000192037 - Truncated text in file 44, Appointment,\n Patient, OTHER fld 3\n 238195 (d)\n3) HD0000000243629 - Incorrect person class\n4) HD0000000209762 - Rejection code 850 not in file 404.472\n\n
\nPCMM PHASE III - INACTIVATION OF PROVIDERS.\n\n
\nFiscal Year 2009 Supplemental Update to the Clinic Stop (#40.7) file.\n\n
\nPROJ 112/SHAD\nAGENT ORANGE/KOREAN DMZ\nFOREIGN ADDRESS\n\n
\nThis contains fixes related to the PCMM software (distributed as\nSD*5.3*41). This should be installed immediately after the installation\nof SD*5.3*41. See National Patch Module (NPM) for a description of the\ncontents of this patch.\n\n
\nThis uses SSN if PID does not exist in PCMM's patient lookup. For\ncomplete patch description, see NPM.\n\n
\nThis patch corrects errors with the Display Appointments and Cancel \nClinic Availability (the Pre-Cancellation list build) menu options.\n\n
\nThis patch will fix any appointment records within the Appointment \nsub-file of the Patient file where the Purpose of Visit field contains an \ninvalid value. All such invalid values will be changed to a value of 3.\n\n
\nFix SDLT routine for Scheduling letters\n\n
\nThis patch contains fixes for the following issues:\nComputed date fields not printing the year when doing a Fileman inquiry\nTurn off option DPA Detailed Patient Assignments[SC PCMM DETAILED LIST \nPTS]\nPractitioners Patients report header issue\nRoll and scroll problem with PCMM enrollment\n\n
\nThis patch addresses the following issues:\n1) Functionality related to matching an appointment with EWL entries if \n the non-removal reason is already in place. \n2) Calculation and printing report: 30, Over 30, Over 120 Day Report to\n a spooler.\n3) Proper identification and notification of only open EWL entries\n existing for a particular clinic.\n4) Update the EWL USER MANUAL to reflect correctly a new functionality, \n see 1).\n\n
\nFY2010 updates to the CLINIC STOP (#40.7) file.\n\n
\nSee National Patch Module, SD*5.3*536\n\n
\nFix Audit Trail in Hospital Location file (#44) for field 2505 - \nInactivate Date. Also, fix option Find Next Available Appointment when \ndoing lookup by Team, so that it uses the new multiple field (#5 - \nAssociated Clinic) in the Team Position file (#404.57).\n\n
\nFY2010 Supplemental update to Clinic Stop file (#40.7).\n\n
\nFix to validation logic for Ambcare transmissions to allow 3 new values\nwhich were added to the Radiation Exposure Method field (#.3212) in the\nPatient file (#2) with patch DG*5.3*659.\n\n
\nThis build contains changes to two routines. They are needed to correct a\nproblem of properly filing the primary diagnosis. If the encounter does\nnot have a primary diagnosis than it will not be accepted by Austin.\n\n
\nAdd new Help text at the date prompts to inform users that past dates \nmust include the year when input, do not allow appts to be made prior to\ndate a new day of the week is added to clinic pattern and fix \nNonconforming Clinic report to indicate when a stop code was Inactivated.\n\n
\nCorrects errors that occur when printing Routing Slips and Display Clinic\nAvailability report.\n\n
\n- Fixes the entry for the DATA ENTRY CLERK (#7) field in the HOSPITAL\n LOCATION FILE (#44).\n- Deletes the CATEGORY OF VISIT (#1.5) field of the ENROLLMENT CLINIC \n multiple (#2.001) in the PATIENT FILE (#2).\n- Fixes the entry for the DATA ENTRY CLERK (#19) field in the PATIENT FILE\n (#2).\n- Corrects a problem when passing service connected types through Quasar. \n\n
\nFY2011 updates to the Clinic Stop file (#40.7).\n\n
\nUpdate Scheduling routines to use replacement API's for unsupported/deleted\ndata dictionary fields in the ICD files.\n\n
\nFix for several Recall Reminder issues: case sensitivity issue when \nmaking a Recall Reminder entry, incorrect wording in message display in \nCPRS, date range issue with Printing letters by team, an <Undefined> \nerror that occurs with Print Letters by Clinic or by Provider if an \nup-arrow is entered at the date range prompt and extraneous text that \nprints at the top of the Letter for Nonresponsive Patients and displaying \nthe full clinic name on the CPRS Cover Sheet.\n\n
\nPatch fixes 2 discrepancies with the ACRP Ad Hoc report.\n.\n\n
\nThis patch provides mid-Fiscal Year 2011 updates to the CLINIC STOP\nfile (#40.7) as requested by the Decision Support Office (DSO).\n\n
\nThis patch will allow printing only one "second" letter or card for the \nnonresponsive patients.\n \nThis patch will also correct the words for the Lab test(s) line that do\nnot wrap properly problem when manually printing recall reminder letters.\n \nLast, this patch will fix the issue for patient's clinic does not match \nthe selected hospital location for the letter.\n\n
\nRefer to entry SD*5.3*92 of the National Patch Module.\n\n
\nFix issue with ACRP CUSS report involving whole days that have been\nACRP Ad Hoc report when data is missing in the Patient Enrollment file\nand an error that occurs with the Patient Activity by Appointment\nFrequency report.\ncancelled. Report erroneously calculates clinic capacity using a zero for\nwhole days that have been cancelled. The normal number of available slots\nshould be used for the clinic capacity and only the number of open slots\nshould reflect zero for that day. Also, the patch fixes an erroneous\ncolumn heading for the ACRP Ad Hoc report when run for a delimited\nformat for export to a spreadsheet, also the use of a single character\nvariable name, an error that causes the Ambcare nightly transmission to\nfail due to an invalid eligibility code, an error that occurs with the\n\n
\nFixes undefined variable error - <Undefined>EN+15^SCENIA0.\n\n
\nFiscal Year 2011 Table Maintenance updates to the Clinic Stop file \n(#40.7).\n\n
\nThis patch enhances PCMM (Patient Care Management Module) functionality.\nPlease . Please \nreview the FORUM patch module for a complete description.\n\n
\nFixes to kill some variables that are not killed after exiting Expand \nEntry, correct incorrect appointment status that displays after running \nthe Purge Scheduling Data option, fix Data Dictionary discrepancy for the \nSpecial Availability Flag field (#3) of the sub-file #44.005 in the \nHospital Location file (#44) and fix undefined error that occasionally \noccurs in routine SDM2A when attempting to make an appointment.\n\n
\nFix several issues that exist with the IEMM option Edit Outpatient\nEncounter [SCENI OP ENCOUNTER EDIT]. \n\n
\nThis patch will fix an issue with the security key for providers, an \nissue with displaying recall reminders on the CPRS cover sheet and \nprohibit selecting an inactive provider when adding a new recall reminder.\n\n
\nPatch fixes incorrect time that occasionally occurs when an appointment \nthem know a selected clinic is inactive.\nis cancelled, also 'No Action Taken' appointments not appearing on the No \nShow report (when requested). Finally, patch fixes a few issues with the \nAppointment List. If one clinic is selected and availability has not \nbeen set up for the selected date, the clinic name does not print in the \nreport header. If all clinics or a list of clinics are selected, any \nclinics not set up with availability for the selected date are ignored \nand not included on the report. Finally, by design, inactive clinics can \nbe selected for the report, but no indication is given to the user to let \n\n
\nFixes sporadic undefined error in SCMCDD1. For complete description, see\nNPM.\n\n
\nMid-Fiscal Year 2012 table maintenance updates to the Clinic Stop file \n(#40.7).\n\n
\nTwo new reports for high risk mental health, Ad Hoc no show report\nand the nightly background job no show report.\n\n
\nFixes subscript error introduced with patch SD*5.3*567.\n\n
\nThis patch addresses the following issues: A date without a year will no\nlonger bring up a past date. A cancelled appointment will now bring up \nthe Electronic Wait List if the patient has other pending appointments.\nThe INACTIVATION DATE ENTERED BY Field will no longer be filled when the\nuser views a clinic.\n\n
\nPatch makes the Clinic Field (#4.5) a required field in the Recall \nReminders file (#403.5) and includes post-init routine SD53P566 which \nwill provide a report of all entries in file #403.5 that do not have a \nclinic. Also prohibits users from entering patients into the Patient \nfile (#2) through the SDRR CARD ADD and SDRR PATIENT INQUIRY options. \nFinally, the patch includes a couple of fixes to the SDRR PATIENT INQUIRY \noption - displaying "User Who Entered" field incorrectly and displaying a \nDate Reminder Sent for all a patient's reminders, even those that have \nnot been sent yet.\n\n
\nThis patch addresses several issues related to PCMM, and EWL as follows:\n - eliminate any closed EWL entries from evaluation of any 'NULL' values\n in their required fields, and do not display closed entries at all\n- The SD WAIT LIST OPEN CLOSED ENTRY option was modified not to allow\n opening of close EWL entries with code ER:ENTERED IN ERROR\n- Routine SDRPA20 was modified to populate null only in the Admission Type\n sequence of the PV1 segment, if no Appointment Type is coming with the\n appointment record.\n- Properly reflect patient inactivation rules on the PCMM inactivation\n messages generated by SCMC PCMM NIGHTLY TASK\n- The SD WAIT LIST CLEANUP report was modified to:\n - evaluate only opened EWL entries\n - close any incomplete entries without the CURRENT STATUS field (# 23)\n of the SD WAIT LIST file (# 409.3) being populated at all.\n Those entries will be closed with code ER:ENTERED IN ERROR populated\n in the DISPOSITION field (# 21).\n\n
\nThis patch provides the ability to store Capacity and FTEE for all roles \nin PCMM including primary care and non-primary care teams and to enter \nand retrieve them in PCMM GUI. The FTEE and Panel Size report colum titles\nwill be modified accordingly.\n\n
\nPatch fixes an error that occasionally occurs with the ACRP Ad Hoc \nreport. It also fixes a misspelling in the description in the Option \nfile (#19) for ACRP option Retransmit Ambulatory Data by Date Range.\n\n
\n1. When cancelling an appointment within the Appointment Management Module\n [SDAM APPT MGT] option, if another user cancels the same appointment \n at the same time an undefined error occurs. \n \n2. If an appointment is cancelled "by clinic" within the Appointment \n Management Module [SDAM APPT MGT] option, the Appointment Management \n Module reverts to patient view instead of clinic view.\n\n
\nFiscal Year 2013 Table Maintenance for CLINIC STOP file (#40.7).\n\n
\nPatch for NOIS: MAD-1196-40990\nEMPLOYEES 7 RESEARCH REQUIRING MT\n \nCorrects the ELAP^SDPCE API call to return the eligibility pointer and\nappointment type pointer in the correct piece positions.\n\n
\n1. An error that occurs when un-assigning a patient with a future dated\n4. An error that occurs when a user enters "^^" at the prompt "Enter response:\n 1//" using the PCMM Assign or Unassign protocol.\n assignment.\n \n2. No warning message is displayed when Assigning/Re-assigning a deceased\n patient.\n \n3. The user has the ability to assign/unassign a deceased patient\n to a team or position after their date of death.\n \n\n
\nThis patch addresses one Scheduling issue:\n \n1. Previously deleted unused fields were reinstalled into system from \npatch SD*5.3*568.\n\n
\nThis patch provides Fiscal Year 2013 Mid Year updates to the CLINIC STOP\n(#40.7) file as requested by the Decision Support Office (DSO).\n\n
\nThis patch has code changes for increment 3 for the no show reports. It\nalso has new increment 3 functionality to look at the PRF flag as a CAT 1\nNational flag and also has two new reports, the ad hoc proactive report\nand the nightly job proactive report.\n\n
\nIMPORTANT NOTE: \nThis patch will fix the problem of allowing entry of a month and year\nfor the recall dates that result in no letter printing.\n \nThis patch will also disable the Recall Reminders conversion options.\nIf site has not finished the conversion from Class III to Class I yet\nand Patch SD*5.3*536 has not been installed; please DO NOT install this\npatch.\n \nThis patch will prevent the input date value from being accepted for the \nRECALL DATE (#5) and RECALL DATE (PER PATIENT) (#5.5) fields in the\nRECALL REMINDERS (#403.5) file if it is before or current date.\n \n\n
\n \n3. When running the Historical Provider Position Assignment Listing \n report by provider no assignment data is returned due to an incorrect \n variable name.\n1. The user has the ability to reactivate an automatically inactivated \n patient to an inactive team and position.\n \n \n2. The user has the ability to reactivate an automatically inactivated \n deceased patient to their previously assigned team and position.\n \n \n\n
\nThis patch provides Fiscal Year 2014 updates to the CLINIC STOP (#40.7) \nfile as requested by the Decision Support Office (DSO).\n\n
\n \n1. When an appointment is cancelled, the software rounds and files the\n cancellation date/time rather than filing the precise time.\n \n2. When a user attempts to cancel a checked out appointment, a warning\n message is displayed with the incorrect appointment number.\n\n
\nThis patch provides Fiscal Year 2014 Mid Year updates to the CLINIC STOP \n(#40.7) file as requested by the Decision Support Office (DSO).\n\n
\nSee NPM for description.\n\n
\nThis patch addresses two Electronic Waitlist(EWL) issues:\n \n1. The system does not allow a user to create an appointment with an \n appointment date that is greater than 120 days from the desired date.\n \n2. The current Electronic Waitlist (EWL) User Manual reflects incorrect \n instructions for canceling an appointment.\n\n
\nThis patch will fix the following several issues:\n \n4. Fix <UNDEFINED>DQD4+7^SDRRRECL error.\n \n5. Fix <UNDEFINED>START+17^SDRRTSK1 error.\n \n6. Fix the problem of the suffix in a patient's name is printing before\n the last name in the letter salutation.\n \n7. Remove the comma between city and state when printing recall patient's \n address.\n \n1. Add date letter printed and first letter of patient's last name and\n last four digits of patient's social security number to the recall \n letters.\n \n2. Fix <UNDEFINED>DATE+21^SDRRTSK error.\n \n3. Fix <UNDEFINED>DQD1+7^SDRRRECL error.\n\n
\nThis patch will fix the following issues with locally created codes in \nthe ELIGIBILITY CODE file (#8):\n1) OUT OF SYNC problem when making an appointment.\n2) OUT OF SYNC problem when adding a patient to the electronic wait list.\n3) Ambulatory Care Nightly Transmission generating reject errors due to \nsoftware not recognizing local eligibility codes having an Internal Entry \nNumber (IEN) greater than 99.\n\n
\nThis patch will fix a functionality issue that was introduced with patch\nSD*5.3*591, whereby the incorrect status for an appointment is being\ndisplayed in Appointment Management when an appointment has only been\npartially Checked out. The original request pointed to incorrect displayed\nstatus of an appointment if it was purged. Additionally the List by \nAppointment protocol was evaluated to provide a consistent appointment \nstatus display when this protocol is executed in PXCE ENCOUNTER ENTRY \noption in Patient Care Encounter (PCE).\n\n
\nThis patch will address several inconsistencies in a list of patients\nselected and displayed as available ones for multi assignment by \nappointment in a clinic. That list of patients is available in PCMM GUI.\nAdditionally this patch will address a problem with incorrect indication \nof the patient Primary Care assignment if a hanging cross-reference in \nthe Patient Team Position Assignment file (# 404.43) is evaluated as a \nvalid one.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nScheduling - ICD10 Remediation\n\n
\nScheduling changes for VIA project. See patch description for details.\n\n
\nThis patch provides Fiscal Year 2015 updates to the CLINIC STOP \nfile (#40.7) as requested by the Office of Finance, Managerial Cost \nAccounting Office (MCAO).\n\n
\nThis patch will fix the following issues:\n Recall Patient Inquiry [SDRR PATIENT INQUIRY].\n \n1. an issue that allows users to select clinics for recall reminders that\n are inactive or scheduled to be inactive on the selected recall date. \n \n2. an issue with menu option Convert Retired Providers/Clinic Recalls\n [SDRR CONVERT ENTRIES].\n \n3. a display issue with the Date Second Reminder Sent field when doing a\n\n
\n \nSee patch description in the Patch Module for patch SD*5.3*90.\n\n
\nThis patch will address two issues:\n- Duplicate encounters are being created for visits causing patient data \nto not link correctly.\n- The display in the Make Consult Appointment [SC MAKE CONSULT \nAPPOINTMENT] is truncating the Consult Name, causing incorrect consults \nto be scheduled.\n\n
\nThis patch will fix/update the following three (3) issues:\n \n1. Patient names are not sorted in alphabetical order for the Appointment \n List.\n \n2. The description for appointment type Organ Donors.\n \n3. The length of the data field Clinic IEN Number in the Patient\n Appointment Information Transmission (PAIT) documentation.\n\n
\nThis patch addresses four Electronic Wait List [EWL] issues:\n option the user is prompted to select an entry to view but all entries \n are displayed.\n4. When using the Enrollment Wait List (Sch/PCMM) Statistic Report [SD \n WAIT LIST ENROLL REPORT] option there is a calculation error in the \n DO NOT REMOVE DATE COLUMN.\n \n1. Clinics with an inactive dates in the SD WL CLINIC LOCATION file \n (#409.32) can create wait list entries when using the MAKE APPOINTMENT \n [SDAM APPT MAKE] protocol.\n2. When creating an entry using the ENTER/EDIT WAIT LIST (Sch/PCMM) [SD \n WAIT LIST ENTER/EDIT] option with the PCMM TEAM ASSIGN wait list type \n an undefined error occurs.\n3. When using the INQUIRE WAIT LIST (Sch/PCMM) [SD WAIT LIST INQUIRY] \n\n
\nThis build includes legacy PCMM data extract routines used for comparison \nto PCMM Web for data validation. The routines have been added as options\nto the SCMC PCMM Extracts menu.\n\n
\nThis patch provides Fiscal Year 2015 Mid-Year updates to the CLINIC \nSTOP file (#40.7) as requested by the Office of Finance, Managerial \nCost Accounting Office (MCAO).\n\n
\nPatch SD*5.3*630 addresses the following 2 issues:\n \n- Duplicate encounters show on the PCE Encounter List screen for a future\n appointment that has notes associated with it before the date of the \n visit.\n- Consult Service names are being truncated in the Make Consult\n Appointment [SC MAKE CONSULT APPOINTMENT] option\n\n
\nBuild for Scheduling Enhancement #4\n\n
\nSHUTDOWN OF HL7 FOR PCMM.\n\n
\nCorrects the handling of associated credit stop codes for Hospital\nlocations that are exempted from sending diagnostic codes\n\n
\nThis patch addresses adding three (3) new fields to the HOSPITAL LOCATION \n 2) control the clinics that display appointment information to Veterans \n and \n 3) improve the clinic information that is exposed to patients so that it \n is meaningful and relevant to clinical care.\n \nThis patch adds three (3) new fields and modifies two (2) Scheduling \noptions. \n1. Three (3) new fields were added to the HOSPITAL LOCATION File (#44).\n - PATIENT FRIENDLY NAME\n - DIRECT PATIENT SCHEDULING?\nFile (#44) to compensate for defects that exist in the current VistA \n - DISPLAY CLIN APPT TO PATIENTS?\n \n2. The Set up a Clinic [SDBUILD] and Clinic Profile [SDCLINIC] options \n were modified to display the three new fields.\nScheduling package. This effort was requested by the Veterans Health\nAdministration (VHA) Access and Clinic Administrative Program (ACAP) \nin support of the VistA Scheduling Enhancements (VSE) project.\n \nThe purpose of this work is to add VistA Scheduling fields to \n 1) control the clinics that are exposed to Veterans for direct patient \n scheduling of appointments, \n\n
\nThis patch provides Fiscal Year 2016 updates to the CLINIC STOP (#40.7) \nfile as requested by the Office of Finance, Managerial Cost Accounting \nOffice (MCAO).\n\n
\nIn preparation for the VA's transition from Internet Protocol version 4 \nwith the long-anticipated problem of IPv4 address exhaustion. IPv6 is \nintended to replace IPv4.\n \nVistA is only compatible with IPv4 currently and this effort is to \nprepare for IPv6 compatibility.\n(IPv4) to Internet Protocol version 6 (IPv6), the Patient Appointment \nInformation Transmission (PAIT) package will require modifications to \nmake it IPv6 ready.\n \nIPv6 is the latest version of the Internet Protocol (IP), the \ncommunications protocol that provides an identification and location \nsystem for computers on networks and routes traffic across the Internet. \nIPv6 was developed by the Internet Engineering Task Force (IETF) to deal \n\n
\nThis is the KIDS build for SD*5.3*603. It contains the modifications to \nVistA to support PCMM Web.\n\n
\nThis patch stops sending appointment data for bi-monthly transmission \nfrom VistA to the Austin Information Technology Center (AITC).\n\n
\nThis patch provides Fiscal Year 2016 Mid-Year updates to the CLINIC STOP \n(#40.7) file as requested by the Office of Finance, Managerial Cost \nAccounting Office (MACO).\n\n
\nPatch SD*5.3*638 addresses three Remedy ticket issues:\n \n3. When adding wait list entries by service specialty, if a specific \nclinic is added and auditing is on, a subscript error will occur.\n \n1. A request has been made to discontinue the bi-monthly EWL transmissions\nto Austin. This process is handled through the SD WAIT LIST TRANS TO AAC \n[SD Wait List Trans to AAC] option. \n \n2. Users are unable to remove data from the DATE INACTIVATED (#3) field \nin the SD WL CLINIC LOCATION (#409.32) file if there are open wait list \nentries.\n\n
\nVeterans Health Administration (VHA) created over 2.5 million \nCommunity Care Consults means that VA needs a tracking mechanism to \nidentify these consults. Due to the urgent necessity to track care in the \ncommunity consults, this patch adds a new stop code 669, COMMUNITY CARE \nCONSULT, to the CLINIC STOP (#40.7) file as requested by the Office of \nFinance, Managerial Cost Accounting Office (MCAO).\nauthorizations for Veterans to receive care in the community in fiscal \nyear 2015 - an 8.6% increase in authorizations when compared to fiscal \nyear 2014.\n \nThe Access and Clinic Administration Program (ACAP) requested that the \nStop Code Council establish a new Stop Code to track Community Care \nConsults. Tracking Community Care Consults is a high priority of the \nSecretary of the VA and Congress. The enormous volume and importance of \n\n
\nPCMM Reporting Device problems. For a complete description, please see\nthe NPM.\n\n
\nDescription:\nThis patch contains server functionality to perform the following \ntasks:\n \n1) Extract appointment and encounter data from Vista Scheduling.\n2) Aggregate extracted data for a specified date range.\n3) Format the aggregated data in a predefined XML schema.\n4) Send the XML data to a requesting application through the RPC Broker.\n \nThe report is not available from any legacy VistA option.\n \n===========\nThe only functionality available within legacy VistA is an option to \nqueue the data extraction and compilation process via VistA option BUILD \nXML DATA [SD VSE REPORT DATA]. This option has also been added to the\nOption Scheduling (#19.2) file to run nightly as a regularly scheduled\nbackground task. The compiled data is stored in the ^TMP global and is \ndeleted completely and recompiled when the SD VSE REPORT DATA option is \nrun.\n \n \nVistA Remote Procedure Call (RPC) SD VSE FILTER RPC is available for the\n \nVSE Clinical Scheduler application to return the list of Report Types\n(Mental Health, Primary Care, Specialty Care), the list of available date\naggregates (Year, Quarter, Month, Week, Date), and the date range\ncorresponding to the selected date aggregate. The values returned by SD\nVSE FILTER RPC are used to populate the corresponding E3 report filters.\n \nVista Remote Procedure Call (RPC) SD VSE REPORT RPC returns the report \ndata corresponding to the values selected by the initial three filters \n(Report Type, Date Aggregate, Date Range). \nThis patch contains server side functionality for the Vista Scheduling\nEnhancements (VSE) Enhancements 3 (E3) project. The VSE E3 project \nimplements a GUI reporting application designed to run on user\nworkstations, and launched via a "Dashboard" button in the Reports\ntab in the VSE Enhancement 1 (E1) Clinical Scheduler GUI application.\n \n\n
\nVistA Scheduling GUI Release 3\n\n
\nBuild for adding 'CID/PREFERRED DATE' to the title field in files #2, \n#409.3, and #409.36. It also updates input and output routines where\n'desired date' has been shown to the user. From this patch forward,\n'desired date' is replaced with 'CID/Preferred Date' and 'CID/PD' in \nreports where there is a space restriction. The field name\n'DESIRED DATE OF APPOINTMENT' and the title 'CID/PREFERRED DATE' have the \nsame meaning.\n\n
\nThis patch release includes two bug fixes:\n \n1. Fixes an issue that caused patient's Date of Death warning message not\n always showing when changing to a different patient in the Appointment\n Management.\n \n2. Fixes an issue that prevented clinic's telephone number from printing\n an extra character on a scheduling letter.\n\n
\nThis patch provides Fiscal Year 2017 updates to the CLINIC STOP (#40.7) \nfile as requested by the Office of Finance, Managerial Cost Accounting \nOffice (MCAO). Associated patch EC*2.0*133 inactivates any DSS Units in \nEvent Capture set to Send No Records to PCE with an associated Stop Code \nbeing inactivated by the SD patch.\n\n
\nSD*5.3*661 adds four new Stop Codes to the CLINIC STOP (#40.7) file as \nexempt from copayments these opioid education visits, designated clinics\nmust be established. An emergency Stop Code patch is required to \nimplement these clinics by March 15, 2017.\nrequested by the Office of Finance, Managerial Cost Accounting Office \n(MCAO).\n \nThe Comprehensive Addiction and Recovery Act (CARA) of 2016 directs the \nDepartment of Veterans Affairs to expand its opioid safety initiative to \ninclude all VA medical facilities. CARA exempts Veterans from paying a \ncopayment to the VA for education on opioid safety to include overdose \nprevention and treatment for overdose. In order to schedule, track and \n\n
\nThis patch allows capturing of language data during the making of an \nappointment if no value is on file.\n\n
\nSD*5.3*657 provides Fiscal Year 2017 Mid-Year updates to the CLINIC STOP \n(#40.7) file as requested by the Office of Finance, Managerial Cost \nAccounting Office (MCAO).\n\n
\nRefer to National Patch Module for details\n\n
\nThis patch will delete the "trigger" cross references listed below and\n.03 POSITION ASSIGNED DATE\n Xref-AEVENT4\n.04 POSITION UNASSIGNED DATE\n Xref-AEVENT5\n.05 PC ROLE\n Xref-AEVENT2\n \nPOSITION ASSIGNMENT HISTORY FILE (#404.52)\n.01 TEAM POSITION\n Xref-AEVENT1\ndelete data in the PCMM HL7 EVENT FILE.\n.02 EFFECTIVE DATE\n Xref-AEVENT2\n.03 PRACTITIONER\n Xref-AEVENT3\n.04 STATUS\n Xref-ASTATUS\n.09 FTEE EQUIVALENT\n Xref-AFTEE\n \nPRECEPTOR ASSIGNMENT HISTORY FILE (#404.53)\n \n.01 TEAM POSITION\n Xref-AEVENT1\n.02 EFFECTIVE DATE\n Xref-AEVENT2\n.04 STATUS\n Xref-AEVENT3\n.06 PRECEPTOR TEAM POSITION\n Xref-AEVENT4\n \nTEAM POSITION FILE (#404.57)\nFiles:\n.04 POSSIBLE PRIMARY PRACTITIONER?\n FIELD INDEX: AE (#208)\n.08 MAX NUMBER OF PATIENTS\n FIELD INDEX: AD (#207)\n \nTEAM POSITION HISTORY FILE (#404.59)\n.03 STATUS\n FIELD INDEX: AC (#209)\n \nThe entry points in routine SCMCHLX called by the cross references and\nPATIENT TEAM POSITION ASSIGNMENT FILE (#404.43)\nindexes were modified to exit immediately.\n.01 PATIENT TEAM ASSIGNMENT\n Xref-AEVENT1\n.02 TEAM POSITION\n Xref-AEVENT3\n\n
\nThis patch provides Fiscal Year 2018 updates to the CLINIC STOP (#40.7)\nfile as requested by the Office of Finance, Managerial Cost Accounting \nOffice (MCAO). Associated patch EC*2.0*136 inactivates any DSS Units in\nEvent Capture set to Send No Records to PCE with an associated Stop Code \nbeing inactivated by the SD patch.\n\n
\nThis patch adds consistency checks for DIRECT PATIENT SCHEDULING? field \nAdditional changes added to fix hard error when calling Wait List or \nRecall Reminder whenever the help text for Select LANGUAGE DATE/TIME: \nprompt invoked while executing the Make Appointment option in [SDAM \nAPPT MGT] Appointment Management.\n(#61) and DISPLAY CLIN APPT TO PATIENTS? field (#62) in the HOSPITAL \nLOCATION file (#44) when creating a new clinic or editing an existing \nclinic by using the Set up a Clinic [SDBUILD] menu option.\n \nThis effort was requested by the Veterans Health Administration (VHA) \nAccess and Clinic Administration Program (ACAP) in support of the VistA \nScheduling Enhancements (VSE) project.\n \n\n
\nSD*5.3*664 provides updates to the OUTPATIENT CLASSIFICATION STOP CODE\nEXCEPTION file (#409.45) as requested by the VISN 20 Veteran Equitable \nResource Allocation Coordinator and approved by the Office of Community \nCare - Policy and Planning.\n \nAfter the installation of this patch, the OUTPATIENT CLASSIFICATION STOP\nCODE EXCEPTION file (#409.45) will be locked down.\n\n
\nThis patch release includes three bug fixes:\n3. Fixes some misspelling words on the fields and indexed in the \n Outpatient Encounter file (#409.68).\n \n1. Fixes an issue that prevented from printing an extra blank page before\n printing the actual pre-appointment letter when make appointment.\n \n2. Fixes an issue that prevented from printing an extra blank page before\n printing the actual cancel appointment letter in the Appointment \n Management.\n \n\n
\nThis patch fixes the following three (3) issues:\n \n3. When running the Recall Patient Inquiry, if queuing is selected, the\n error <NOTOPEN>ALL+1^SDRRINQ1 occurred.\n \n1. When running Recall Reminder nightly background job, Clean Up Clinic\n Recall Entries [SDRR CLEAN-UP], Delete Reason APPT SCHEDULED is missing\n in the RECALL REMINDERS REMOVED file (#403.56).\n \n2. When entering a patient into Recall Reminder, customer requests to \n limit the clinic that the patient should be scheduled in with only the\n clinic TYPE is clinic.\n\n
\nThis patch corrects an issue where no data was appearing on the \nTransmission History Report - Full [SCDX AMBCAR XMIT HIST FULL] when \ncalled to a Print Queue. The data would appear when called to the \nscreen. \n\n
\nSee NPM for description.\n\n
\nSee National Patch Module for description.\n\n
\nPCMM API Date check function.\n\n
\nThis patch release addresses the following issues:\n \n1. Fixes an issue that could prevent date sent fields from updating when \n displaying patient's recall letter or card on the computer screen.\n2. Fixes an issue where warning message would not create in MailMan for\n patient with Bad Address Indicator.\n3. Fixes an incorrect word in the MailMan message for patients with Bad\n Address.\n4. Fixes incorrect Canadian address format.\n\n
\nSD*5.3*677 provides Fiscal Year 2018 Mid-Year updates to the CLINIC STOP \n(#40.7) file as requested by the Office of Finance, Managerial Cost \nAccounting Office (MCAO).\n\n
\nThis patch (SD*5.3*680) addresses this one (1) issue:\n(1) I16592426FY17 - Self Identified Gender\n - SDL--PREAPPOINTMENT LETTERS Print Template and VistA\n routines SDEC40, SDECU, and SDLT are modified and\n remove gender implication(s).\n\n
\n This patch will address 1 issue:\n \n 1. Canceling clinic availability for a date that has previously been\n removed from availability will incorrectly restore availability for\n that date.\n\n
\nThis patch contains the VistA components necessary to support the 1.5 \n address on the Patient Info form, and the name of the\nN/A\n \n \n \nMail Groups Associated:\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\nN/A\n \n associated county is contained in another county in the\n \n \nOptions Associated:\n New/Modified/\nOption Name Type Deleted \n----------- ---- -------------\nCLINICAL SCHEDULING PROCEDURE CALLS [SDECRPC] Broker MODIFIED\n \n \n \n same state (such as ROBERTS and ROBERTSON), an error\nParameter Definitions:\n New/Modified/\nParameter Name Deleted \n-------------- -------------\nN/A\n \n \n \nParameter Template:\n New/Modified/\n message would be displayed.\nTemplate Name Deleted \n------------- -------------\nN/A\n \n \n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\n3. I16857061FY18 - If a scheduler makes or cancels an appointment for a \nN/A\n \n \n \nRemote Procedures Associated:\n New/Modified/\nRemote Procedure Name Deleted \n--------------------- -------------\nSDEC BOOKHLDY New \n \n consult and the current time ends in a zero (like \n \n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n----------------- -------------\nN/A\n \n \n \n 9:40), then the event recorded in the consult will\nTemplates, Input Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nTemplates, List Associated:\n New/Modified/\n display at the end of the consult event history instead\nTemplate Name Type Deleted \n------------- ---- -------------\nN/A\n \n \n \nTemplates, Print Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\n of in sequence.\nN/A\n \n \n \nTemplates, Sort Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\n---------------------------- \nN/A\n \n \nrelease of VistA Scheduling Enhancements (VSE) as well as addressing the\nThe third issue requires a fix to repair existing data effected by the\nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nService Desk Manager (SDM) Ticket(s) & Overview\n-----------------------------------------------\n1. I15980703FY17 ENH REQ: VSE issue: Scheduling "clinics" on a specific \n holiday opens up ALL holidays to scheduling.\n \nissue. That repair is done in a separate patch, which will be bundled\nProblem:\n-------\nWhen setting up clinics, VistA recognizes holidays and offers the option \nto schedule in selected clinics on holidays as a second step in the clinic\nset up process (includes education day).\n \nThe clinic day is initially set as a holiday. Then, to be able to \nschedule on a selected holiday such as Education Day, Doreen or Michelle\nwould go back in and answer "yes" to the question in VistA "Schedule on\nholidays?" to be able to subsequently go in and open up slots to be\nwith this one. Below is a list of all the applications involved in this\nscheduled into on particular holidays. VistA allows this without opening\nup ALL holidays. It seems, however, that VSE does NOT. In VSE, this opens\nup ALL holidays to scheduling, ie. it shows the clinics as open for\nscheduling. \n \nResolution:\n----------\nThe VSE GUI Client has been corrected to check that the slot is available \nbefore attempting to book a holiday appointment.\n \nbundle along with their patch number:\n2. R16256976FY17 VS GUI 2.0.0.12 - New Issue? - Error pop up indicating \ncounty does not belong in state - OVAC Edit \n \nProblem:\n-------\nWhen you enter the zip code, the state/county populate correctly, but when\nyou click OK, you get "County GREEN does not belong to state GREEN."\n \nResolution:\n----------\n \nThe code that looks up the county ID in the state has been corrected so \nthat it no longer encounters this error when one county's name (in this\ninstance Green county) is contained in another (in this instance, Green\nLake county).\nIn addition, the error message has been corrected so that the actual state\nname is displayed rather than displaying the county name a second time.\n \n3. I16857061FY18 Consults are showing activities out of order in CPRS; \n VistA FM shows activities in correct chronological order\n \n APPLICATION/VERSION PATCH\nProblem:\n-------\nOur site is experiencing issues with Consults where the activities being \nrecorded are out of order. I originally thought this was a result of the \nCONSULT TOOLBOX tool, but there are multiple sites reporting this issue, \nand the consensus is that this is being caused by VSE.\n \nResolution:\n----------\nThe code that saves the SCHEDULED or STATUS CHANGE event when the \n ---------------------------------------------------------------\nappointment is scheduled or canceled was corrected to save the timestamp\ncorrectly.\n \n \nTest Sites:\n----------\nTBA\n \n \nDocumentation Retrieval Instructions\n SCHEDULING (SD) V. 5.3 SD*5.3*679\n------------------------------------ \nUpdated documentation describing the new functionality introduced by this \npatch is available.\n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/.\nThis transmits the files from the first available FTP server. Sites may \nalso elect to retrieve software directly from a specific server as \nfollows:\n \n CONSULT/REQUEST TRACKING (GMRC) V. 3.0 GMRC*3.0*98\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n--------------------------------------------------------------------------\nVistA Scheduling Enhancements GUI User Guide VSE_VA_GUI_UG.PDF Binary\n \nVistA Scheduling Enhancements Technical Manual VSE_TM.PDF Binary\n \n \nPatch Installation:\n \n \nPre/Post Installation Overview\n------------------------------\nThis patch should take less than 5 minutes to install.\n \nfollowing issues:\nPatch Components\nThis patch should not be installed with VistA Scheduling GUI users on the\nsystem and it is recommended that it be installed during non-peak hours to\nminimize potential disruption to other users.\n \nThis patch contains no PRE Installation processing.\n \nThe other patch bundled with this one (GMRC*3.0*98) contains a \npost-install routine that will repair bad data created by the consult\ncomment issue.\n \n================\n \nInstallation Instructions\n-------------------------\nThis installation will update routines that support VistA Scheduling GUI \nApplication Programming Interfaces (APIs).\n \n1. OBTAIN PATCHES\n --------------\n Obtain the host file SD_GMRC_VSE_BUNDLE_1_5.KID, which contains the\n following patches:\n \n \n SD*5.3*679\n GMRC*3.0*98\n \n Sites can retrieve VistA software from the following FTP addresses.\n The preferred method is to FTP the files from:\n \n download.vista.domain.ext\n \n This will transmit the files from the first available FTP server.\nFiles & Fields Associated:\n Sites may also elect to retrieve software directly from a specific\n server as follows:\n \n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n The SD_GMRC_VSE_BUNDLE_1_5.KID host file is located in the\n anonymous.software directory. Use the American Standard Code for \n Information Interchange (ASCII) Mode when downloading the file.\n \n \n \n 2. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu option\n [XPD MAIN]:\n \n Edits and Distribution ...\n Utilities ...\n Installation ...\n \nFile Name (#) New/Modified/\n Select Kernel Installation & Distribution System Option: \nInstallation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Sub-file Name (#) Field Name (Number) Deleted\n Backup a Transport Global\n \n Select Installation Option:\n \n3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD\n -------------------------------------\n From the Installation menu, select the Load a Distribution option.\n \n When prompted for "Enter a Host File:", enter the full directory path\n where you saved the host file SD_GMRC_VSE_BUNDLE_1_5.KID (e.g.,\n------------------- --------------------------------- -------------\n SYS$SYSDEVICE:[ANONYMOUS]SD_GMRC_VSE_BUNDLE_1_5.KID).\n \n When prompted for "OK to continue with Load? NO//", enter "YES."\n \n The following will display:\n \n Loading Distribution...\n \n SD GMRC VSE BUNDLE 1.5\n SD*5.3*679\nN/A\n GMRC*3.0*98\n \n Use INSTALL NAME: SD GMRC VSE BUNDLE 1.5 to install this\n distribution.\n \n4. RUN OPTIONAL INSTALLATION OPTIONS FOR MULTI-BUILD\n -------------------------------------------------\n From the Installation menu, you may select to use the following\n options (when prompted for the INSTALL NAME, enter\n SD GMRC VSE BUNDLE 1.5):\n \n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as data dictionaries or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, data dictionaries, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n \nBulletins Associated:\n transport global.\n \n5. INSTALL MULTI-BUILD\n -------------------\n This is the step to start the installation of this KIDS patch. This\n will need to be run for the SD GMRC VSE BUNDLE 1.5 build.\n \n a. Choose the Install Package(s) option to start the patch\n install.\n b. When prompted for the "Select INSTALL NAME:", enter \n New/Modified/\n SD GMRC VSE BUNDLE 1.5\n c. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//", enter NO.\n d. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//", enter NO.\n e. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \nand\n Protocols? NO//' \n Respond with 'YES'\n Options to mark as out of order:\nBulletin Name Deleted \n Clinical Scheduling Procedure Calls [SDECRPC]\n Scheduling Manager's Menu [SDMGR]\n Supervisor Menu [SDSUP]\n Scheduling Menu [SDUSER]\n Clinic Letter Report [SDRR CLINIC LETTER \nREPORT]\n f. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0. \n \n \nPost-Installation Instructions\n------------- -------------\n------------------------------\nIn order to verify the patch post-installation routine was run \nsuccessfully, please examine the Install File for this patch and \nreport any error messages to Product Support.\nN/A\n \n \n \nDialogs Associated:\n New/Modified/\n1. I15980703FY17 - If user has begun to schedule an appointment on a \nDialog Name Deleted \n----------- -------------\nN/A\n \n \n \nForms Associated:\n New/Modified/\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\n holiday and ability to book appointments on holidays \nN/A\n \n \n \nFunctions Associated:\n New/Modified/\nFunction Name Deleted \n------------- -------------\nN/A\n \n is turned off in the meantime, the appointment can be\n \n \nHL Logical Link:\n New/Modified/\nHL Logical Name Deleted \n--------------- -------------\nN/A\n \n \n \n booked.\nHL7 Application Parameters:\n New/Modified/\nHL7 Parameter Name Deleted \n------------------ -------------\nN/A\n \n \n \nHLO Application Registry:\n New/Modified/\n2. R16256976FY17 - If user enters a zip code in the Veteran's permanent\nHLO Registry Name Deleted \n----------------- -------------\nN/A\n \n \n \nHelp Frames Associated:\n New/Modified/\nHelp Frame Name Deleted \n--------------- -------------\n\n
\nThis patch addresses the following 2 issues:\n \n 1. Clinic availabilities with future start dates display as available \n prior to the future requested date.\n \n 2. The Clinic Utilization & Capacity Data transmissions to Austin\n should no longer be transmitted.\n\n
\nThis build contians the routines necessary to correct xeveral problems\nwith the deletion of Add/Edits.\n\n
\nPatch SD*5.3*689 corrects a missing date of the clinic issue on the \nNo-Show Report.\n\n
\nPatch SD*5.3*685 corrects an undefined error when selecting 'Print Cards\nby Team' from the Clinic Recall Print Menu [SDRR PRINT MENU] option.\n \nThis patch also corrects an indent issue when printing patient's \nconfidential address for recall letters and cards.\n\n
\nSD*5.3*696 provides Fiscal Year 2019 updates to the CLINIC STOP file \n(#40.7) as requested by the Office of Finance, Managerial Cost Accounting \nOffice (MCAO).\n\n
\nThis patch release contains the shutdown of the HL7 Ambulatory Care \ntransmitted from VistA instances to Data Management Interface (DMI) at \nAITC.\nnightly transmission (ACRP) that goes out from each VistA instance \neach day to the National Patient Care Database (NPCDB). The NPCDB is being\nshut down in Austin and the Corporate Data Warehouse (CDW) is replacing \nthe database as the authoritative source. The VistA extracts done to \npopulate the CDW will replace the need for the HL7 transmission.\n \nAustin Information Technology Center (AITC) has also requested the Monthly\nAdditional Performance Monitors HL7 data transmissions stop being \n\n
\nThis patch will include code changes for several routines for two New \ndisplay the Primary Care provider, Associate Provider and team, as well \nas the physical location for an appointment. Clinic appointments were \nscreened for administrative clinics, and finally, output of Social \nSecurity Number(SSN) was truncated to four digits instead of outputting \nthe entire SSN.\nService Requests (NSRs) that were approved by the Software Modification \nWaiver Committee associated with Scheduling Package in VistA.\nThe following will be addressed in this patch:\n1) Add A Blank Line Between Appointments in Print Scheduling \nLetters[SDPRLETTERS].\n2) Modifications to Patient Scheduling Letters - modifications were made \nto VistA Scheduling option Display Appointments[SDDISPPEND] to add the \nphysical address of the site in the header. Changes were also made to \n\n
\nThis patch will include code changes for several routines for three NSR's \nthat were approved by the Software Modification Waiver Committee \nassociated with Scheduling Package in VistA.\n\n
\nThis patch addresses the following issue(s):\nthe affected end user (AEU) to determine the appointment type\nfor computer generated appointments.\n \n1. An undefined error occurs when running the Edit Computer\nGenerated Appointment Type [SDACS CGEDIT] option with the\nOUTPATIENT ENCOUNTER (#409.68) file entry is missing the\nPATIENT (#.02) field.\n \n2. The Edit Computer Generated Appointment Type [SDACS CGEDIT]\noption does not contain the necessary patient information for\n\n
\nThis patch addresses one issue:\n \n1. Sites are getting an <UNDEFINED>MORE+2^SDC error when they attempt to\n cancel a clinic availability.\n\n
\nThis patch address's duplicate encounters being added to the transmitted\noutpatient encounter file, encounters in the transmitted file by error,\nand missing checked out encounters.\n \nThis patch creates a Supervisor Ambulatory Care Menu on the Ambulatory\ncare reporting menu.\n\n
\nSD*5.3*713 - Please refer to the patch description in Forum for \ninstallation instructions.\n\n
\nThis patch addresses one issue:\n \n1. when queuing Recall Clinic Letter Report, an <UNDEFINED>SORT+14^SDRRREP\n error occurred.\n\n
\nCCRA-HSRM Scheduling HL7 Interfaces for processing Make\nAppointment: SIU-S12, CANCEL: SIU-S15, and NOSHOW: SIU-S26 messages.\n\n
\nThis patch corrects the problem of appointment processing in VistA\nthe GUI. (However, this patch does not require a GUI update.)\n-------------\nN/A\n \n \n \nParameter Definitions:\n New/Modified/\nParameter Name Deleted \n-------------- -------------\nN/A\n \n \n \n \nParameter Template:\n New/Modified/\nTemplate Name Deleted \n------------- -------------\nN/A\n \n \nPatch Components\n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\nN/A\n \n \n \nRemote Procedures Associated:\n================\n New/Modified/\nRemote Procedure Name Deleted \n--------------------- -------------\nN/A\n \n \n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n \n----------------- -------------\nN/A\n \n \n \nTemplates, Input Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\nFiles & Fields Associated:\n \n \n \nTemplates, List Associated:\n New/Modified/\nTemplate Name Type Deleted \n------------- ---- -------------\nN/A\n \n \n \n \nTemplates, Print Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nTemplates, Sort Associated:\nFile Name (#) New/Modified/\n \nNew/Modified/\nTemplate Name Type File Name (Number) \nDeleted \n------------- ---- ------------------ \n-------------\nN/A\n \n \nAdditional Information:\n Sub-file Name (#) Field Name (Number) Deleted\nN/A\n \n \nNew Service Requests (NSRs)\n---------------------------- \nN/A\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\n------------------- --------------------------------- -------------\nN/A\n \n \nServiceNow Ticket(s) & Overview\n-----------------------------------------------\nI17005764FY18 Pyxis and EDIS are not recognizing clinic check in actions\n \nProblem:\n-------\nWhen a user performs appointment actions in VS GUI, downstream systems \nScheduling (VS) GUI not invoking the event driver protocol (SDAM \nN/A\nsuch\nas Pyxis (or other unit dosing devices, such as Omnicell) and EDIS are not\nupdated, whereas they are when the appointment actions are taken in legacy\nVistA.\n \nResolution:\n----------\nThe GUI now invokes the SDAM APPOINTMENT EVENTS protocol just like legacy\nVistA, meaning that the downstream systems will be notified in the same\nway whether actions are taken on them in GUI or legacy.\n \n \nTest Sites:\n----------\nTBA\n \nSoftware and Documentation Retrieval Instructions:\n----------------------------------------------------\n \nSoftware being released as a host file and/or documentation describing\nthe new functionality introduced by this patch are available.\nBulletins Associated:\n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may\nalso elect to retrieve files directly from a specific server. \n \nSites may retrieve the software and/or documentation directly using \nSecure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE\ndirectory at the following OI Field Offices:\n \n Hines: fo-hines.domain.ext\n New/Modified/\n Salt Lake City: fo-slc.domain.ext\n \n \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n--------------------------------------------------------------------------\nVistA Scheduling Enhancements GUI User Guide SCHEDULING_UG.PDF Binary\nBulletin Name Deleted \nVistA Scheduling Enhancements Technical Manual SCHEDULING_TM.PDF Binary\n \n \nPatch Installation:\n \n \nPre/Post Installation Overview\n------------------------------\nThere are no pre- or post-installation tasks for this patch.\n \n------------- -------------\nInstallation Instructions\n-------------------------\nInstall Time - less than 5 minutes.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. From this menu, you may select to use the following options\nN/A\n (when prompted for INSTALL NAME, enter SD*5.3*717):\n a. Verify Checksums in Transport Global - This option will \nallow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option \nwill\n allow you to view all changes that will be made when this \n \n patch is installed. It compares all components of this\n patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will \nnot\n backup any other changes such as DD's or templates.\n \n 4. Use the Install Package(s) option and select the package SD*5.3*717.\n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//"\n \n respond NO.\n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//", respond NO\n \nBack-Out/Roll Back Plan:\n------------------------\nIn the event of a catastrophic failure, the Facility Chief Information \nOfficer may make the decision to back-out the patch.\n \nIt is imperative that you have performed a backup of the routines and\n \nthe routines included matches the pre-patch checksum from the patch\ndescription.\n \nThis patch only contains routine updates. To back-out the patch please\nrestore the backup message from the patch installation process.\nAPPOINTMENT\nDialogs Associated:\n New/Modified/\nDialog Name Deleted \n----------- -------------\nN/A\n \n \n \nForms Associated:\n New/Modified/\nEVENTS) that roll and scroll VistA does. This protocol allows other apps\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\nN/A\n \n \n \nFunctions Associated:\n New/Modified/\nFunction Name Deleted \n------------- -------------\nto tie functionality, including interfaces to external systems such as\nN/A\n \n \n \nHL Logical Link:\n New/Modified/\nHL Logical Name Deleted \n--------------- -------------\nN/A\n \nPyxis, Omnicell, and EDIS,to appointment events. Actions currently being\n \n \nHL7 Application Parameters:\n New/Modified/\nHL7 Parameter Name Deleted \n------------------ -------------\nN/A\n \n \n \nexecuted for appointment events in legacy VistA will also be executed for\nHLO Application Registry:\n New/Modified/\nHLO Registry Name Deleted \n----------------- -------------\nN/A\n \n \n \nHelp Frames Associated:\n New/Modified/\nappointments when those events (make appointment, check in, undo check in,\nHelp Frame Name Deleted \n--------------- -------------\nN/A\n \n \n \nMail Groups Associated:\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\ncheck out, undo check out, cancel appointment, no show) are triggered by\nN/A\n \n \n \nOptions Associated:\n \nNew/Modified/\nOption Name Type \nDeleted \n----------- ---- \n\n
\nSD*5.3*728 provides Fiscal Year 2020 updates to the CLINIC STOP (#40.7)\nfile as requested by the Office of Finance, Managerial Cost Accounting\nOffice (MCAO).\n\n
\nLarge Processing Job fix\n\n
\n Refer to National Patch Module for complete details\n that do not have a valid pointer to the Outpatient Encounter\n file (#409.68) or the Deleted Outpatient Encounter file\n (#409.74) are deleted.\n \n (2) Entries in the Transmitted Outpatient Encounter file that have\n been rejected by the Austin Automation Center and do not have an\n entry in the Transmitted Outpatient Encounter Error file\n (#409.75) are marked for re-transmission.\n \n (3) Entries in the Deleted Outpatient Encounter file that do not\n\n have a corresponding entry in the Transmitted Outpatient\n Encounter file are deleted.\n \n (4) Entries in the Transmitted Outpatient Encounter Error file that\n do not have a valid pointer to the Transmitted Outpatient\n Encounter file are deleted.\n \n The entry point SCAN^SD53105A should be used to scan for errors and\n print what would have been done.\n \n Clean up of the ACRP transmission files\n The entry point FIX^SD53105A should be used to fix the errors.\n Although nothing is printed, a summary of what was done is sent to\n the user queueing the fix and recipients of the SCDX AMBCARE TO\n NPCDB SUMMARY bulletin.\n \n \n Clean up of the Scheduling Visits file and Clinic Stop Code multiple\n --------------------------------------------------------------------\n The second clean up routine, SD53105B, will clean up missing pointers\n and stub entries in the Scheduling Visits file. The following\n ---------------------------------------\n actions/checks will be performed:\n \n (1) Performs a search for entries in the Clinic Stop Code multiple\n (#10) of the Scheduling Visits file (#409.5) that do not point\n to an entry in the Outpatient Encounter file (#409.68). For\n those found, an existing Outpatient Encounter that matches the\n clinic stop will be attached to the entry or a new Outpatient\n Encounter will be created for it.\n \n (2) Stub entries in the Clinic Stop Code multiple are deleted.\n The first clean up routine, SD53105A, will clean up dangling pointers\n \n (3) Entries in the Scheduling Visits file with no clinic stops are\n deleted.\n \n The entry point SCAN^SD53105B should be used to scan for errors and\n print what would have been done.\n \n The entry point FIX^SD53105B should be used to fix the errors.\n Although nothing is printed, a summary of what was done is sent to\n the user queueing the fix and recipients of the SCDX AMBCARE TO\n and orphan entries within the ACRP transmission files. The following\n NPCDB SUMMARY bulletin.\n\n actions/checks will be performed:\n \n (1) Entries in the Transmitted Outpatient Encounter file (409.73)\n\n
\nPatch 722 used an encounter lookup utility that created new encounters \nentries, inquire, create or edit Resource file (#409.831) and inquire \nEncounter file (#409.68) entries. \nwhen one did not already exist. This resulted in new encounters being \ncreated for old appointments. A modification was made to SDEC50 that\nremoved the call to the encounter lookup utility. A modification to the \nencounter lookup utility (SDVSIT2) is also included, documenting the code \nso that developers do not inadvertently use it improperly.\n \nSix (6) new options are also part of this patch so that users do not need \nto have FileMan access to inquire or edit Appointment file (#409.84) \n\n
\nPatch 731 enhances the appointment fixing routine used by the manual fix\ntest data available to the development team. The relaxation of these \n 1. RTC 1087933 - Appointment fix options (manual and automatic) do not \n fix appointments that are cancelled in the patient (#2) and location \n (#44) files but not in the appointment file (#409.84). Also to\n activate a cancelled appointment file entry if the patient file entry\n is active.\n \n Problem:\n -------\n The appointment fixing routine developed for patch 723 does not repair \n active appointment file (#409.84) entries when the patient file (#2) \nrestrictions resulted from experience with production data in the IOC \n appointment is cancelled and vice versa. This problem was discovered \n during production IOC testing.\n \n Resolution:\n ----------\n The appointment fixing routine was modifed to change appointment data \n from active to cancelled and cancelled to active.\n \n The instructions for using the two appointment fixing options are \n described in detail in patch 723.\nsites.\n \n 2. INC6787649 - Cancels wrong pt. appointment when original appointment \n was made through self scheduling.\n \n Problem:\n -------\n When a VAOS-created appointment is cancelled in VSE, the appointment \n for the previously scheduled appointment, for another patient, is \n cancelled instead.\n \n \n Resolution:\n ----------\n Appointment cancellation can be performed from the appointment context \n menu associated with the appointment from either the Pending\n Appointments list or the calendar. A change was made to a MUMPS routine\n (SDECEPT) that blocked access to the cancel appointment option on the\n calendar. The block resulted from time being filed along with date in\n the CID field by VAOS. SDECEPT strips off time when it returns data to\n VS GUI. The presence of time resulted in an "unhandled exception" error\n in VS GUI blocking access to the cancel appointment option.\nThe new version can flag an appointment file (#409.84) entry as cancelled\n \n Note: This code change does not correct the error in the cancel option \n on the Pending Appointments list. That correction will require a change\n to VS GUI and will appear in a future release of the software.\n \n==========================================================================\n \n Test Sites:\n ----------\n North Texas\nand will copy the corresponding cancellation data into it from the patient\n Fayetteville, NC\n \n Software and Documentation Retrieval Instructions:\n ---------------------------------------------------- \n Software being released as a host file and/or documentation describing \n the new functionality introduced by this patch are available.\n \n The preferred method is to retrieve files from \n download.vista.domain.ext. This transmits the files from the first\n available server. Sites may also elect to retrieve files directly from a\nfile entry. It can also change an appointment file (#409.84) entry from\n specific server. \n \n Sites may retrieve the software and/or documentation directly using \n Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE\n directory at the following OI Field Offices:\n \n Hines: fo-hines.domain.ext \n Salt Lake City: fo-slc.domain.ext\n \n Documentation can also be found on the VA Software Documentation \ncancelled to active and will remove the cancellation data. The enhanced \n Library at: http://www4.domain.ext/vdl/\n \n \n Title File Name FTP Mode\n--------------------------------------------------------------------------\n VistA Scheduling Enhancements User Guide VSE_UG.PDF Binary\n \n Patch Installation:\n \n \nversion also compares appointments in the patient and location file to \n Pre/Post Installation Overview:\n -------------------------------\n \n Pre-Installation Instructions:\n \n This patch may be installed with users on the system although it is\n recommended that it be installed during non-peak hours to minimize\n potential disruption to users. This patch should take less than 5\n minutes to install.\n \nensure consistency before between them so that VSE and VistA Scheduling \n No pre- or post-installation steps are required.\n \n Installation Instructions:\n --------------------------\n \n 1. Choose the PackMan message containing this patch.\n \n 2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n 3. From the Kernel Installation and Distribution System Menu, select the\noption (SDEC NO RES APPT FIX) and automatic fix option (SDEC NO RES APPT\ncan function properly.\n Installation Menu. From this menu, you may elect to use the following\n options. When prompted for the INSTALL NAME enter the patch number (ex. \n SD*5.3*731):\n \n a. Backup a Transport Global - This option will create a backup message \n of any routines exported with this patch. It will not backup any other\n changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - This option will (allow \n you to view all changes that will be made when this patch is installed.\n \n It compares all components of this patch routines, DDs, templates,\n etc.).\n \n c. Verify Checksums in Transport Global - This option will allow you to\n ensure the integrity of the routines that are in the transport global.\n \n 4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \n 5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\nPatch 731 also adds a new option "Appointments with no resource report" \n Install? YES//', respond YES.\n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//',\n respond NO.\n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//', respond NO.\n \n 8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n[SDEC NO RES APPT REPORT], that operates the same as the "Automatically\n \n Back-Out Plan:\n --------------------\n In order to back out this patch, restore the transport global that was \n saved in Step 3.a. of the installation. Delete the options that \n were included in the patch except SDSUP. Edit the SDSUP option to remove\n the new option.\nFix Appointments with No Resource" [SDEC NO RES APPT AUTO FIX] option\nexcept that it only lists the differences. It makes no changes. Use the\noption to review the discrepancies betweenn the patient, location and\nappointment files.\n \n Patch Components:\nAUTO FIX). It also has a tweak to the SDEC EP WAIT LIST RPC code to strip\n -----------------\n \n Files & Fields Associated:\n \n File Name (Number) Field Name (Number) New/Modified/Deleted\n ------------------ ------------------- --------------------\n N/A\n \n \n Forms Associated:\ntime from the CID date if it is present. This tweak allows schedulers to \n \n Form Name File # New/Modified/Deleted\n --------- ------ --------------------\n N/A\n \n \n Mail Groups Associated:\n \n Mail Group Name New/Modified/Deleted\n --------------- --------------------\ncancel VAOS appointments from the VSE calendar without error.\n N/A\n \n \n Options Associated:\n \n Option Name Type New/Modified/\n Deleted \n ----------- ---- -------------\n Appointments with No Resource Report \n [SDEC NO RES APPT REPORT] Routine NEW\n \n \n Supervisor Menu [SDSUP] Menu MODIFIED\n \n \n Protocols Associated:\n \n Protocol Name New/Modified/Deleted\n ------------- -------------------- \n N/A\n \nPreviously (patch 723), the fixing routine would not repair appointments\n \n Security Keys Associated:\n \n Security Key Name\n -----------------\n N/A\n \n \n Templates Associated:\n \n(#409.84) where the current state (active or cancelled) was different from\n New/Modified/\n Template Name Type File Name (Number) Deleted \n ------------- ---- ------------------ -------------\n \n Additional Information:\n N/A\n \n \n New Service Requests (NSRs):\n ---------------------------- \nthe appointment in the patient file (#2). This restriction was based on \n N/A\n \n \n Patient Safety Issues (PSIs):\n -----------------------------\n HITPS-6559\n \n \n Defect Tracking System Ticket(s) & Overview:\n --------------------------------------------\n\n
\n**************************************************************************\nwork *\n----------- -------------\nN/A\n \n \n \nForms Associated:\n New/Modified/\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\nN/A\n* with no problems after this patch has been installed. However, if \n \n \n \nFunctions Associated:\n New/Modified/\nFunction Name Deleted \n------------- -------------\nN/A\n \n \nthe *\n \nHL Logical Link:\n New/Modified/\nHL Logical Name Deleted \n--------------- -------------\nN/A\n \n \n \nHL7 Application Parameters:\n* 1.5.1 version is used without this patch, then all fields for \n New/Modified/\nHL7 Parameter Name Deleted \n------------------ -------------\nN/A\n \n \n \nHLO Application Registry:\n New/Modified/\nHLO Registry Name Deleted \nselecting *\n----------------- -------------\nN/A\n \n \n \nHelp Frames Associated:\n New/Modified/\nHelp Frame Name Deleted \n--------------- -------------\nN/A\n* clinics, as well as the Audit Report, will not work \n \n \n \nMail Groups Associated:\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\nN/A\n \n \nproperly. *\n \nOptions Associated:\n \nNew/Modified/\nOption Name Type \nDeleted \n----------- ---- \n-------------\nCLINICAL SCHEDULING PROCEDURE CALLS [SDECRPC] Broker MODIFIED\nCOMPILE AUDIT REPORT FOR A SELECTED Routine NEW\n**************************************************************************\n DATE [SDEC COMPILE AUDIT REPORT]\nCOMPILE YESTERDAY'S AUDIT REPORT [SDEC AUDIT REPORT JOB] Routine NEW\nRELEASE APPOINTMENT REQUEST LOCKS[SDEC RELEASE LOCKS] Routine NEW\nSUPERVISOR MENU [SDSUP] Menu MODIFIED\n \n \n \nParameter Definitions:\n New/Modified/\nParameter Name Deleted \n**\n-------------- -------------\nN/A\n \n \n \nParameter Template:\n New/Modified/\nTemplate Name Deleted \n------------- -------------\nN/A\n \n \n \n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\nN/A\n \n \n**\nThis patch contains the VistA components necessary to support the 1.5.1 \n \nRemote Procedures Associated:\n New/Modified/\nRemote Procedure Name Deleted \n--------------------- -------------\nSDEC ARGET MODIFIED\nSDEC ARSET MODIFIED\nSDEC RESCE NEW\nSDEC SUMMGET2 NEW\n \nrelease of VistA Scheduling Enhancements (VSE) as well as addressing the\n \n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n----------------- -------------\nN/A\n \n \n \nfollowing issues:\nTemplates, Input Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nTemplates, List Associated:\n New/Modified/\n \nTemplate Name Type Deleted \n------------- ---- -------------\nN/A\n \n \n \nTemplates, Print Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\n1. R18120703FY18 - The VS GUI application freezes when the Audit Report \nSDEC AUDIT DATE PRINT Print SDEC AUDIT STATISTICS (#409.97) NEW\n \n \n \nTemplates, Sort Associated:\n \nNew/Modified/\nTemplate Name Type File Name (Number) \nDeleted \n------------- ---- ------------------ \nis\n-------------\nSDEC AUDIT REPORT BY DATE Sort SDEC AUDIT STATISTICS (#409.97) NEW\n \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\n---------------------------- \n run for all schedulers due to performance issues.\nN/A\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nService Desk Manager (SDM) Ticket(s) & Overview\n-----------------------------------------------\n \n1. R18120703FY18 Cancel Audit Data Error after selecting ALL in Audit \nReport\n \nProblem:\n-------\nIn the Audit Report, when the user chooses ALL in order to run the report \nfor\nall schedulers, the system hangs for several minutes attempting to load \ndata,\nthen finally returns an RPCException when the connection times out. This \n2. R17856900FY18, - If an appointment had been scheduled for a consult, \nalso\nterminate's the user's connection to VistA until they close and reopen VS \nGUI. \n \nResolution:\n----------\nThe data for the Audit Report is now compiled by a nightly job so that \nmuch\nless data needs to be transmitted to the client in order to use the \nreport.\n R18564968FY18, then that consult was completed, and finally the\nUsers will now be able to run the report for all schedulers without\nencountering the timeout.\n \n2. R17856900FY18, R18564968FY18, R18648321FY18 Reactivating completed \nconsults\n \nProblem:\n-------\nIf an appointment is created for a consult, then the consult is marked as\ncomplete, then finally the appointment is canceled, the consult returns \n* GUI UPDATE \n R18648321FY18 appointment was canceled, the consult will be marked\nto the\nactive status instead of remaining complete. \n \nResolution:\n----------\nIn this situation, the consult will now remain in the complete status.\n \n3. R17415367FY18 Incorrect lock handling in RM Grid\n \nProblem:\n as active, even though it should remain as complete.\n-------\nWhen a user selects a request in the RM grid, the request is locked until\nanother request is selected. If the user exits the program, the lock is \nnot\nreleased. If a VistA user tries to use the previously locked request, they\nwill be prevented from doing so. (To exacerbate this, the GUI was not \nhandling\nlocks correctly and would give the lock to any user that tried to get it \neven\nif another user held the lock, so this issue was not visible to GUI\n \nusers.)\n \nResolution:\n----------\nThe request that a user had locked when they log out is now unlocked\ncorrectly. In addition, if a user tries to work a request in the GUI that\nanother user has locked, they will receive a message that the request is\nlocked and which user holds the lock. Finally, a VistA option on the\nSupervisor menu has been added that will release all locks held by a user.\n \n3. R17415367FY18 - If a user locks an appointment request (in this case,\n4. R17039175FY18 Consult lookup interaction errors\n \nProblem:\n-------\nWhen using clinic lookup in the VS GUI, if the user pauses typing, the \ninput \nis wiped out and has to be re-entered. A pop-up window appears if the \nuser's \ninput results in more than 50 matches and the input is erased. In \naddtion, \n a consult request in particular) by selecting it in \nthe user cannot refine the list of clinics returned by typing additional \ncharacters.\n \nResolution:\n----------\nGUI changes made, eliminating the pop-up window and responding to the \nuser's\ninput including narrowing the list of returned values when each additional\ncharacter is entered. A new RPC was created for the GUI to support this\nchange. The new RPC returns a more limited amount of data so that the\nthe\nGUI can respond more quickly to the user's input.\n \n5. R18477670FY18 Remote facility not updated when appointments made for \nIFCs\n \nProblem:\n-------\nWhen scheduling an appointment for an IFC, the remote facility is not \nnotified.\nRPC code for VS GUI did not include functionality in VistA Scheduling for \n RM grid, then exits the GUI with it still locked, a \nthe \ngeneration of IFC notifications.\n \nResolution:\n----------\nModified the RPC code to call a VistA Scheduling API that generates IFC \nnotifications.\n \nTest Sites:\n----------\nuser\nTBA\n \n \nDocumentation Retrieval Instructions\n------------------------------------ \nUpdated documentation describing the new functionality introduced by this \npatch is available.\n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/.\n in VistA will be unable to select the same request,\nThis transmits the files from the first available FTP server. Sites may \nalso elect to retrieve software directly from a specific server as \nfollows:\n \n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n instead receiving a message stating that the request \n \nTitle File Name FTP Mode\n--------------------------------------------------------------------------\nVistA Scheduling Enhancements GUI User Guide VSE_VA_GUI_UG.PDF Binary\nVistA Scheduling Enhancements Technical Manual VSE_TM.PDF Binary\n \n \nPatch Installation:\n \n \nNOTICE *\nis\nPre/Post Installation Overview\n------------------------------\nPost-installation, there are 3 tasks: 1) re-index the SDEC CONTACT file,\n2) schedule the audit statistics compiler to run early each morning in \nTaskMan and 3) compile enough previous audit statistics for reporting \nusers.\nThese tasks will be detailed in the Post-Installation Instructions \nsection.\n \nInstallation Instructions\n locked.\n-------------------------\nInstall Time - less than 5 minutes.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter SD*5.3*686):\n \n a. Verify Checksums in Transport Global - This option will \nallow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option \nwill\n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this\n4. R17039175FY18 - When using clinic lookup, if the user pauses the input\n patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will \nnot\n backup any other changes such as DD's or templates.\n \n 4. Use the Install Package(s) option and select the package SD*5.3*686.\n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//"\n respond NO.\n is wiped out and has to be re-entered.\n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//", respond NO\n \nPost-Installation Instructions\n------------------------------\n1. RE-INDEX THE SDEC CONTACT FILE\n ------------------------------\n VA FileMan 22.2\n \n Select OPTION: UTILITY FUNCTIONS \n \n ----\n \n Select UTILITY OPTION: 4 RE-INDEX FILE\n -\n \n MODIFY WHAT FILE: SD Audit Statistics// 409.86 SDEC CONTACT\n ------\n (0 entries)\n \n THERE ARE 3 INDICES WITHIN THIS FILE\n5. R18477670FY18 - When scheduling an appointment for an Inter-Facility\n DO YOU WISH TO RE-CROSS-REFERENCE ONE PARTICULAR INDEX? No// Y (Yes)\n -\n \n What type of cross-reference (Traditional or New)? Traditional// NEW\n ---\n \n File: SDEC CONTACT (#409.86)\n Select Subfile: 3 DATE/TIME of CONTACT (Subfile #409.863)\n -\n \n Consult (IFC), the remote facility is not \n Current Indexes on subfile #409.863:\n 1404 'AD' whole file index (resides on file #409.86)\n \n Which Index do you wish to re-cross-reference? 1404// AD\n --\n \n Do you want to delete the existing 'AD' cross-reference? YES\n ---\n Do you want to re-build the 'AD' cross reference? YES ...DONE! \n ---\nnotified.\n \n2. SCHEDULE THE AUDIT REPORT JOB\n -----------------------------\n Access the TASKMAN MANAGEMENT option then select Schedule/Unschedule \n options. Schedule the SDEC AUDIT REPORT JOB option to run at some \npoint \n in the early morning tomorrow (such as 1:00 am) with a rescheduling\n frequency of one day (1D).\n \n3. COMPILE DATA FOR THE AUDIT REPORT\n \n ---------------------------------\n Access the SDEC COMPILE AUDIT REPORT option. Enter the date range \nthat \n you want to be able to report statistics for. \n \n NOTE: You can run the option as many times as needed to compile the\n report statistics. Compiling will be skipped if it has already been \ndone\n for a day. It is recommended that you compile a single day the first \ntime\n*-------------------------------------------------------------------------\nThis patch also contains modifications to routines (SDECAR1 and SDECAR2)\n you use the option to gauge the amount of time required at your \nfacility.\n Compiling audit statistics can be done at any time after installation \nthat\n is convenient, but users will only be able to get data on the audit\n report that has been compiled.\nand RPCs (SDEC ARGET and SDEC ARSET) as well changes to FileMan files\n(Appointment Request #409.85) related to a future enhancement - the \nintegration of Scheduling Manager functionality into the VS GUI.\n \n \n \nPatch Components\n================\n \n-*\nFiles & Fields Associated:\n \nFile Name (#) New/Modified/\n Sub-file Name (#) Field Name (Number) Deleted\n------------------- --------------------------------- -------------\nSDEC APPT REQUEST (#409.85) MODIFIED\n VAOS GUID (#5) \nNEW\n \nSDEC CONTACT (#409.86) MODIFIED\n* This patch MUST be installed before the GUI update for release \n \nSD AUDIT STATISTICS (#409.97) NEW\n SCHEDULER (#.01) NEW\n DATE (#1) NEW\n PATIENT CONTACTS (#2) NEW\n APPT REQUESTS (#3) NEW\n APPT APPOINTMENTS MADE (#4) NEW\n APPT CLOSED (#5) NEW\n MRTC OPENED (#6) NEW\n MRTC CLOSED (#7) NEW\n1.5.1 * \n EWL ENTRIES (#8) NEW\n EWL APPOINTMENTS MADE (#9) NEW\n EWL CLOSED (#10) NEW\n PtCSch ENTRIES (#11) NEW\n PtCSch APPOINTMENTS MADE (#12) NEW\n CONSULT APPOINTMENTS MADE (#13) NEW\n APPOINTMENTS CANCELLED (#14) NEW\n TOTAL ACTIONS (#15) NEW\n \nBulletins Associated:\n* of VistA Scheduling GUI is installed. The previous 1.5 release will \n New/Modified/\nBulletin Name Deleted \n------------- -------------\nN/A\n \n \n \nDialogs Associated:\n New/Modified/\nDialog Name Deleted \n\n
\nThis patch addresses issues within a Scheduling RPC where the Cache/MUMPS\nTSTART, TCOMMIT, and TROLLBACK commands are currently being used. These \ncommands are not used in standard VistA code. These commands are being\nremoved and the code rewritten to adhere to standard VistA coding.\n\n
\nPending appointments list in VSE does not show CHECKED IN status if \nappointment checked in using VPS Kiosks. This occurs because VPS code \nonly updates the appointment in the Location file (#44). It does not \ncall the VSE check-in API.\n \nCode change made to SDEC50 to look in Location file for check-in \ndate/time if not found in the Appointment file (#409.84).\n\n
\nSD*5.3*736 provides Fiscal Year 2020 Mid-Year updates to the CLINIC STOP\n(#40.7) file as requested by the Office of Finance, Managerial Cost\nAccounting Office (MCAO).\n\n
\nThis patch is to correct a problem after patch SD*5.3*722 was released\nDepartment Information System (EDIS), to appointment events. Actions\ncurrently being executed for appointment events in legacy VistA will also\nbe executed for appointments when those events.\n \nOnly the make appointment and cancel appointment have been affected.\nand overlayed previous code released in patch SD*5.3*717 for two routines \n(SDEC07B and SDEC08 only).\n \nThis patch corrects the problem of appointment processing in VistA\nScheduling (VS) Graphical User Interface (GUI) not invoking the event\ndriver protocol (SDAM APPOINTMENT EVENTS) that roll and scroll VistA \ndoes. This protocol allows other apps to tie functionality, including\ninterfaces to external systems such as Pyxis, Omnicell, and Emergency\n\n
\nThis patch addresses the following issue:\n \n1. Patients with an EMERGENCY RESPONSE INDICATOR (#.181) in the \n PATIENT (#2) file equal to Pandemic ("P") are displaying on the\n Incomplete Encounter Error Report [SCENI IEMM ERROR REPORT] with an \n error code of 3400 (Invalid Emergency Response Indicator).\n\n\nThis patch provides two cleanup actions: 1) clean-up bad radiology\nadd/edits in the SCHEDULING VISITS File, #409.5; 2) provide a utility for\nusers to redesignate appointment types for Occassion of Service encounters\nthat received a 'regular' appointment type inappropriately in the\nSCHEDULING VISITS File, #409.5.\n\n
\nThis patch addresses the following issue:\n3. The VistA clinic grid displays the wrong date when appointments are\nscheduled prior to the HOUR CLINIC DISPLAY BEGINS (#1914) field in the\nHOSPITAL LOCATION (#44) file and clinic is remapped.\n \n1. Active clinic grid availabilities are disappearing, and other \navailabilities are displaying with open slots when patients are already\nscheduled.\n \n2. Clinic availability disappears after remapping for a clinic with a\nfuture inactivation date.\n \n\n
\nPatch to set APP PROXY ALLOWED for Visual Scheduling Enhancment RPCs\n\n
\nPatch SD*5.3*748 addresses the following issue:\n \n1. Create new option to update missing Unique Visit IDs in Encounters\n and update software to also update TIU Documents when the Visit ID\n is missing.\n\n
\nPatch SD*5.3*739 addresses two issues:\n \n1. Resolves an issue that was causing an UNDEFINED error when running\n Display Appointments [SDDISPPEND] if EXCLUDE ADMIN CLINICS is YES\n in the Scheduling Parameters [SD PARAM PARAMETERS] option.\n \n2. Fixes an issue that could prevent user override a block time from \n making an appointment in appointment management.\n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*754.\n\n
\nUpdate the VistA Scheduling (VS) Graphical User Interface (GUI) to version\n1.7.0.1 R1 to match a new GUI version that must be created.\n\n
\nThis patch addresses a problem raised in NOIS ISA-0197-12151, where the\nposition of the data for two fields is reversed on the PCMM Team's\nPatients report. See NPM for complete description.\n\n
\nPatch SD*5.3*753 addresses the following issues:\n least one appointment canceled will display as fully available\n after the clinic is remapped.\n \n1. The Multiple Appointment Book [SDMULTICLINIC] option does not\n allow unlimited overbooks.\n \n2. Clinic Grids which have all availability canceled will not\n display in Vista after remapping.\n \n3. Clinic Grids which have all availability canceled and have at\n\n
\nSD*5.3*752 provides Fiscal Year 2021 updates to the CLINIC STOP (#40.7) \nfile as requested by the Office of Finance, Managerial Cost Accounting \nOffice (MCAO).\n \nWhen inactivating stop codes in the CLINIC STOP (#40.7) file, the DSS \nUNITS (#724) file also needs to be updated. Therefore, this patch is\nbeing released along with Event Capture patch EC*2.0*151 that inactivates\nthe DSS Units. Both patches will be bundled together with this Scheduling\npatch being the primary.\n\n
\nPatch SD*5.3*766 addresses the following issue:\n \n1. The Correct Unique Visit ID [SCENI IEMM VISIT CORRECTION] \n option updates all child visits to the parent visit automatically.\n Also, it only updates the first TIU Document associated with a Visit.\n\n
\nPlease refer to the patch description for details regarding this patch.\n\n
\nPatch SD*5.3*758 addresses the following issue:\n \n3. When blocking a clinic grid for a partial day, the block\n displays incorrectly (early) when it is for less than 1 hour,\n and after the scheduled availability.\n \n1. Return to Clinic (RTC) orders are moving to "active" status\n after the appointment is moved and the clinic availability \n cancelled.\n \n2. Appointments that were canceled by the patient show as\n "Canceled by Clinic" after the clinic availability \n is cancelled.\n\n
\nPatch SD*5.3*771 marks the Enter/Edit Wait List (Sch/PCMM) [SD WAIT LIST\nENTER/EDIT] option Out of Order, and marks the Wait List Entry [SD WAIT\nLIST ENTRY] protocol Disabled, ahead of the Electronic Wait List (EWL)\ndecommission.\n\n
\nThis patch will update the Patient Centered Management Module (PCMM Web) \nserver entries in the VistA HealtheVet Web Services Client (HWSC).\n\n
\nPlease see the detailed patch description on Forum.\n\n
\nBackup of SD*5.3*770 on Mar 15, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis is a replacement to SD*5.3*87, which was entered in error. In\naddition to fixing the problem introduced with SD*5.3*87 (problems with\ncertain Room-Beds) this patch does the following:\n \nFixes non-printing of Inpatient Provider in Inpatient MailMan messages.\nFixes subjects for PCMM MailMan messages removes full name and full SSN\nfrom message subject. For complete description, see NPM.\n\n
\nPatch SD*5.3*770 provides Fiscal Year 2021 Mid Year updates to the CLINIC \nSTOP (#40.7) file as requested by the Office of Finance, Managerial Cost \nAccounting Office (MCAO).\n\n
\nBackup of SD*5.3*774 on Mar 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of SD*5.3*769 on Mar 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch SD*5.3*769 handles phase 2 of the Electronic Wait List (EWL)\ndecommission. This patch will mark all remaining EWL options Out of\nOrder. The patch will also disable all remaining EWL protocols, and\nRemove any additional Electronic Wait List functionality.\n\n
\nBackup of SD*5.3*765 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module\nunder SD*5.3*765.\n\n
\nBackup of SD*5.3*783 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch SD*5.3*783 will prevent SD WAIT LIST (#409.3) entries from being\nre-opened when a Wait List Appointment is Canceled by Clinic is VistA. \n\n
\nBackup of SD*5.3*781 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis build contains the two routines, menu options, file changes and\nbulletin needed to clean up the deletion errors.\n\n
\nFILES:\n SDEC1 VSE-513\n SDEC32 VSE-552\n SDEC63 VSE-580\n SDECAR1A VSE-582\n SDECCON VSE-513, VSE-563\n SDECVVS VSE-561\n SDNACT VSE-159, VSE-517, VSE-518\n SDNACT1 VSE-159, VSE-517, VSE-518\n SDREACT VSE-159, VSE-517, VSE-518\n SDEC781P VSE-447, VSE-513, VSE-563\nPartial DD: subDD: 409.84 fld: .24\n SDEC08 VSE-399\n \nOPTION:\n SDECRPC VSE-513, VSE-561, VSE-563\n \nREMOTE PROCEDURE:\n SDEC CLINSET - VSE-552\n SDEC CONTACT DISPLAY SINGLE - VSE-513\n SDEC CONTACT NEW - VSE-441\n SDEC CONTACT SEQUENCE SINGLE - VSE-563\n fld: .25 VSE-519 added 2 new fields\n SDEC GETVVSMAKEINFO - VSE-561\n SDEC SEARCH VVS PROVIDERS - VSE-561\n SDEC SPACEBAR VVS PRO - VSE-561\n SDEC VVS DELETE ID - VSE-561\n SDEC VVS GET ID - VSE-561\n SDEC VVS SAVE ID - VSE-561\n fld: 2 VSE-561\nPartial DD: subDD: 409.86 fld: 2.3 VSE-513 changed name to be more \n descriptive.\n VSE-548 created new SRP x-ref\n \nROUTINES:\n\n
\nBackup of SD*5.3*777, PX*1.0*227 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nScheduling patch SD*5.3*777 modifies the software to account for\nBlue Water Navy changes introduced in patch DG*5.3*1018.\n\n
\nBackup of SD*5.3*784 on Jun 02, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n \nROUTINES:\n SDEC1: VSE-554, VSE-555, VSE-556\n SDECAR4: VSE-554\n SDECVVS:\n \nOPTIONS:\n SDECRPC: VSE-554, VSE-555, VSE-556\n \nREMOTE PROCEDURES:\n SDEC PATIENT APP REQ GET: VSE-554\n \nFor tracking purposes, please add component and note the associated Jira \ntask(s) out to the right on the same line.\n \nFILES:\nAdded new MAX RECS ACCUMULATED (#5) field in SDEC SETTINGS (#409.98) \nfile: VSE-552\n \n\n
\nBackup of SD*5.3*741 on Jun 10, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nTime zone fixes, $Q error, and date format error in NEWTIME, TMP New SD \nTools Menu and items.\n\n
\nBackup of SD*5.3*785 on Jul 07, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nFor tracking purposes, please add component and note the associated Jira \n SDEC1: VSE-634, VSE-635, VSE-663, VSE-664, VSE-717, VSE-724, \nThe VS GUI is being updated to utilize RPCs returning data in JSON\nformat. Create new, trimmed version of SDEC RECGET in JSON format. \n \nResolution:\nThe new SDEC GET PATIENT RECALLS JSON RPC was created to return the 20\nkey fields needed to help populate the VS GUI screens related to the\nreview and processing of Recalls.\n \n5) Jira #VSE-724 - Create new RPC to return a single Appointment Request \nin JSON format.\n VSE-734\n \nProblem:\nThe VS GUI is being updated to utilize RPCs returning data in JSON\nformat. Create new SDEC GET APPT REQ BY IEN JSON format.\n \nResolution:\nThe new SDEC GET APPT REQ BY IEN JSON RPC was created to return the 39\nkey fields needed to help populate the VS GUI screens related to the\nreview and processing of the Appointment Requests.\n \n SDEC28: VSE-168/664\n6) Jira #VSE-634 - Create new RPC that will return a single recall \n \nProblem: The VS GUI is in need of an RPC that will return a single Recall \nbased on the IEN being passed to Vista.\n \nResolution:\nThe new SDEC GET PATIENT RECALL BY IEN was created to return the 20\nkey fields needed to help populate the VS GUI screens related to the\nreview and processing of a single Recall.\n \n SDEC28L: VSE-664\n7) Jira #VSE-684 - Pending RTC Order Cleanup Option Enhancement:\nConfirmation Message\n \nProblem:\nRequest an enhancement to the RTC Cleanup tool to have it present with \nuser with a confirmation message before it runs. This will allow the \nuser to change their mind after selecting the OPTION.\n \nResolution: \nBoth SDEC PENDING RTC - FULL and SDEC PENDING RTC - DATE options were \n SDEC40: VSE-693\nmodified to include a confirmation message to ensure that the user wants \nto run the cleanup tool.\n \n8) Jira #VSE-685 - Pending RTC Order Cleanup Option Enhancement: Date \nClarification\n \nProblem:\nRequest an enhancement to the RTC Cleanup tool (SDEC PENDING RTC - DATE) \nto define that the date being prompted for is the Create date.\n \n SDEC51B: VSE-635\nResolution: \nSDEC PENDING RTC - DATE was modified to present the user with a prompt \nfor what SDEC REQUEST Create dates should be searched on. The \ninformation prior to the prompt also informs the user that the Cleanup \nTool will select RTCs based on create date.\n \n9) Jira # VSE-686 - Pending RTC Order Cleanup Option Enhancement: Print \nResults\n \nProblem:\n SDEC52C: VSE-634, VSE-556\nRequest an enhancement for the RTC Order Cleanup Options to return a \nreport of the RTC and Orders that were updated via the tool.\n \nResolution:\nAdded a report to both the SDEC PENDING RTC - FULL and SDEC PENDING RTC - \nDATE OPTION. The user will now be prompted for a DEVICE and a report \nwith information regarding both the ORDER and the RTC will be printed for \nany RTC that was selected and cleaned up.\n \n10) Jira # VSE-734 - Create new RPC that will return, in JSON format, a \n SDEC52CJSON: VSE-663, VSE-734\nsingle recall based on the IEN being passed to Vista.\n \nProblem: VS GUI is in need of an RPC that will return a single Recall \nin JSON format based on the IEN being passed into Vista. \n \nResolution: The new SDEC GET PATIENT RECALL BY IEN JSON RPC was created to\nreturn the 20 key fields needed to help populate the VS GUI screens\nrelated to the review and processing of Recalls. This RPC passes back a \nsingle record to the GUI based on the IEN being passed into Vista.\n \n SDECCONSJSON: VSE-717 \n11) Jira #VSE-728 - Correct defect with new contact creation\n \nProblem:\nIf a Service (Field 1.1) is passed into the RPC SDEC NEW CONTACT, it will \nbe concatenated with the Main Sequence (Field 2.2).\n \nResolution:\nWhen setting into the global, include the system delimiter (^) in front \nof the service.\n \n SDECAR4: VSE-724\n12) Jira #VSE-730 - Prevent appointment cancelation if it is in a\nChecked-In status.\n \nProblem:\nWhen canceling an appointment, the Appointment file (409.84) would have \nits status changed to Cancel prior to performing all validation. This \nwould cause the appointment to become stuck.\n \nResolution:\nEnsure all validation is complete prior to updating any files.\ntask(s) out to the right on the same line.\n SDECCON: VSE-728\n \n13) Jira #VSE-693 - Modify Patient Letter to Remove Title (Mr/Ms)\n \nProblem: \nRequested modification to patient letters printed from VS GUI to \nprint name only (with no title/prefix) in the salutation\n \nResolution:\nModifications were completed to eliminate the Title of Mr/Ms from the \nfollowing letters: Pre-appointment, No-Show, Cancellation by Patient, and\n SDECRTCF: VSE-684,685,686\nCancellation by Clinic\n \n14) Jira #VSE-800 - VS GUI crashing when cancelling VVS Appointment\n \nProblem:\nWhen cancelling a VVS Appointment using Access/Verify when challenged for \nAuthentication and choosing cancel, the VS GUI could crash.\n \nResolution:\nVerify authentication was completed before proceeding and if not, return \n SDEC08: VSE-730\nto the previous process.\n \n15) Jira #VSE-168 - Tasks Tab - Patient Search Functionality\n \nProblem:\nPatient Search was not 508 compliant.\n \nResolution:\nReplaced Patient Search function with pop-up search. Addressed all 508 \nrequirements for the Patient Search function in the tasks tab.\n \n \n16) Jira #VSE-188 - New Appointment - Remediate 508 findings in New \nAppointment form\n \nProblem:\nNew Appointment Form was not 508 compliant. \n \nResolution:\nAddressed all 508 findings in the New Appointment form in VS GUI.\n \nOPTIONS:\n17) Jira #VSE-562 - Edit a VVS Appointment from VS GUI\n \nProblem:\nI want to be able to edit a VVS appointment from VS GUI, so that I do not \nhave to use multiple applications to modify a single appointment.\n \nResolution:\nA button was added on the edit Appointment Form that allows users to edit \nthe corresponding video appointment.\n \n========\n18) Jira #VSE-688 - View a VVS Appointment\n \nProblem:\nI want to view an existing VVS appointment from VS GUI, so that I can \naccess VVS appointment details without using multiple applications.\n \nResolution:\nA button was added to the View Appointment Form that allows users to view \nthe corresponding video appointment.\n \n SDECRPC: VSE-634, VSE-635, VSE-664, VSE-717, VSE-724, VSE-734\n19) Jira #VSE-689 - Resend VVS Appointment Link\n \nProblem:\nAs a scheduler, I want the ability to resend the VVS appointment link to \nvideo visit participants from VS GUI, so that I can ensure all \nparticipants have the link available at appointment time without using \nmultiple applications.\n \nResolution:\nA button was added to the VVS Appointment Form to allow users to re-send \n VSE-556, VSE-663\nthe VVS appointment link.\n \n20) Jira #VSE-718 - Update GUI to use new SDEC GET PAT CONSULT BY IEN RPC\n \nProblem:\nGUI needed to be updated to use new SDEC GET PAT CONSULT BY IEN RPC.\n \nResolution:\nUpdated the GUI to use SDEC GET PAT CONSULT BY IEN RPC when selecting an \nappointment from the pending appointments list. \n \n \n21) Jira #VSE-719 - Update GUI to use new SDEC GET PAT CONSULT RPC\n \nProblem:\nGUI needed to be updated to use new SDEC GET PAT CONSUL RPC.\n \nResolution:\nUpdated the GUI to use SDEC GET PAT CONSUL RPC. \n \n22) Jira #VSE-725 - Remove unnecessary RPC calls\nREMOTE PROCEDURES:\n \nProblem:\nThere are 4 RPC calls made every time the context menu is opened in the \npending appointments list. Remove these calls, as they are unnecessary.\n \nResolution:\nRemoved the 4 unnecessary RPC calls made when opening the context menu in \nthe pending appointments list.\n \n23) Jira #VSE-726 - Updates to GUI to support new SDEC ARGET RPC\n \n==================\n \nProblem:\nUpdate GUI to use the new SDEC ARGET RPC that returns only needed data \nfor a specific appointment and incorporate into LSD service.\n \nResolution: \nThe GUI was updated to include the new SDEC ARGET RPC.\n \n24) Jira #VSE-735 - Update GUI to use new SDEC GET PATIENT RECALL BY IEN \nRPC\n SDEC GET PAT CONSULT BY IEN: VSE-635\n \nProblem:\nUpdate the GUI to use the new SDEC GET PATIENT RECALL BY IEN RPC.\n \nResolution:\nThe GUI was updated to include the new SDEC GET PATIENT RECALL BY IEN RPC.\n \n25) Jira #VSE-741 - Update GUI to use new SDEC GET PATIENT RECALL RPC\n \nProblem:\n SDEC GET PATIENT CONSULT JSON: VSE-717\nUpdate the GUI to use the new SDEC GET PATIENT RECALL RPC.\n \nResolution:\nThe GUI was updated to include the new SDEC GET PATIENT RECALL RPC.\n \n26) Jira #VSE-786 - Speed up processing of JSON RPC\n \nProblem:\nCurrent VSE Broker code that processes JSON responses from RPCs is slow. \nIf the JSON response contains a few hundred records, it can take minutes \n SDEC GET PATIENT DEMOG: VSE-664\nto parse all the data. That is because instead of parsing the data stream \nas an array of strings, which is how VistA returns JSON, the VSE Broker \nuses the code intended for single string value RPCs, which checks each \ncharacter for the end of transmission.\n SDEC GET PATIENT RECALL BY IEN: VSE-634\n SDEC GET PATIENT RECALLS JSON: VSE-663\n SDEC GET APPT REQ BY IEN JSON: VSE-724\n SDEC GET RECALL BY IEN JSON: VSE-734\n SDEC GET PATIENT RECALLS: VSE-556\n \nFILES:\n \nJIRA tasks:\n-----------\n1) Jira #VSE-635 - Review Consults/Procedure RPCs\n \nProblem:\nThe VS GUIs RPCs related to Consults/Procedures need to be reviewed to\ndetermine what optimizations can be made to help improve the response time\nof the VS GUI while processing these records.\n \n======\nResolution:\nThe VS GUI Trace Logs were reviewed and the new SDEC GET PAT CONSULT BY \nInternal Entry Number (IEN) RPC was created to return 17 key fields needed\nto help populate the VS GUI screens related to the review and processing\nof the Consults and Procedures.\n \n2) Jira #VSE-717 - Create new RPC to return a single Consult in \nJavaScript Object Notation (JSON) format.\n \nProblem:\n \nThe VS GUI is being updated to utilize RPCs returning data in JSON\nformat. Create new SDEC GET PAT CONSULT BY IEN RPC in JSON format.\n \nResolution:\nThe new SDEC GET PATIENT CONSULT JSON RPC was created to return the 17\nkey fields needed to help populate the VS GUI screens related to the\nreview and processing of the Consults and Procedures.\n \n3) Jira #VSE-664 - Create Patient Search RPC to return basic Patient \ninformation\n \n \nProblem: \n a) While the Passed in Social Security Number (SSN) 9N format identifier\n was properly executed, those SSNs that contained Hyphens ("-") were\n not being recognized properly (i.e. nnn-nn-nnnn)\n b) Modification was needed to only allow four numerics (4D) to be passed \n in with Alpha last name. \n c) Patients with a SENSITIVE data flag were not being Masked with the \n "Sensitive" message.\n d) A space was missing between the type of letter and the "Letter not\nROUTINES:\n defined" message.\n \nResolution:\n a) Modifications were made to recognize the hyphen within the SSN.\n b) The passing in of a format of First Alpha of Last Name concatenated\n with Numerics has changed from its prior functionality. Now, only A4N\n format is valid, as we have invalidated the A1N, A2N, A3N formatted\n type entries.\n c) Modifications were made to add the Patient Sensitivity Flag as the\n 8th piece of data in the returned string of the RPC SDEC GET PATIENT \n=========\n DEMOG.\n d) Added a missing "space" in the Warning message for "letter not\n defined"(i.e. from "Pre-AppointmentLetter not defined for Clinic VSE\n OG CLINIC."to "Pre-Appointment Letter not defined for Clinic VSE OG\n CLINIC.")\n \n4) Jira #VSE-663 - Create new RPC in JSON format to send the list of\nrecalls associated with a given patient.\n \nProblem:\n\n\nThis patch corrects a problem in the creation/editing/printing of\nencounter forms. A PCMM API related to current practitioner was incorrect\nand is patched here. See NPM for complete description.\n\n
\nBackup of SD*5.3*786 on Jul 07, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch SD*5.3*786 will unschedule and mark out of order the\nSD EWL Background Job [SD EWL BACKGROUND JOB].\n\n
\nVS GUI v. 1.7.8 Release\n \n4) Jira #VSE-777 - Create RPC SDES Get Appointment.\n \nProblem:\nNeed to create a new SDES RPC to get a single appointment by SDEC \nAPPOINTMENT IEN.\n \nResolution:\nThe new SDES GET APPT JSON was created and will return it data in JSON\nformat. Returned data includes:\nAppointment fields to return:\nROUTINES:\nstring ResourceName (Clinic name)\nstring Notes\nstring Duration\nstring StartTime (appointment date time)\nstring EndTime\nstring AppointmentID\nstring AppointmentTypeIEN\n bool IsOverbook\n \n5) Jira #VSE-787: Prompt scheduler to verify patient contact information.\n=========\n \nProblem:\nPrompt the schedule to verify auto-filled patient contact information \nwhen creating a video appointment from VS, so that appointment \ninformation is sent to the right email/number.\n \nResolution:\nScheduler is prompted to confirm that the auto-filled email address/phone \nnumber(s) in the Make Video Visit window is correct.\n \nSDEC07 VSE-863\n6) Jira #VSE-788: Add zip code field to Make Video Visit screen.\n \nProblem:\nDisplay patient's zip code on the Make Video Visit screen to know \npatient's location.\n \nResolution:\nPatient's zip code is displayed on the Make Video Visit screen.\n \n7) Jira #VSE-789: Include option to receive Video Visit Service (VVS)\nSDEC52CJSON VSE-886\nlink via text.\n \nProblem:\nIndicate when making a video appointment from VS that the \npatient/provider prefers to receive the video link via email, text \nmessage, or both.\n \nResolution:\nAdded ability to indicate a patient's preferred contact method (email or \nSMS).\nSDECAR4 VSE-886\n \n8) Jira #VSE-792: Update tooltips to reflect most-used name for RM Grid.\n \nProblem:\nTool buttons tooltips display "Wait List" instead of "RM Grid" or \n"Facility/Default View" (e.g. "Export Wait List")\n \nResolution:\nRenamed each to accurate label.\n \nSDECCONSJSON VSE-886\n9) Jira #VSE-793: Consolidate Appointment window to one tab.\n \nProblem:\nView/New Appointment modal dialog displays a single tab.\n \nResolution:\nConsolidated Appointment window to one tab.\n \n10) Jira #VSE-794: Update expand/collapse icon on time slot viewer.\n \nSDECRTCF2 VSE-876\nProblem:\nTime Slot Viewer expand/collapse icon opposes behavior.\n \nResolution:\nDisplay correct icons when collapsed and expanded.\n \n11) Jira #VSE-795: Loading dialog has duplicate word.\n \nProblem:\nClicking a Pending Appointment displays "Loading Clinic Schedule\nSDECVVS VSE-863\nSchedule". \n \nResolution:\nRenamed to "Loading Clinic Schedule".\n \n12) Jira #VSE-801: Improve error handling on Make VVS Appointment.\n \nProblem:\nImprove error handling for ICN Error, Access Error, and Timeout/VVS \nsystem down error.\nSDESCHECKIN VSE-1017\n \nResolution:\nA window was created to handle errors so that the system message box is \nnot required to display errors to users.\n \n13) Jira #VSE-802: Error Window.\n \nProblem:\nCreate a window to handle errors so that the system message box is not \nrequired to display errors to users.\n \nSDESJSON VSE-886\n \nResolution:\nA window was created to handle errors so that the system message box is \nnot required to display errors to users.\n \n14) Jira #VSE-804: Add contact method preferences to VVS Make Appointment \nscreen - Patient.\n \nProblem:\nAdd ability to indicate a patient's preferred contact method (email or \nSDES VSE-1128, VSE-1129, VSE-1130\nSMS).\n \nResolution:\nEmail for patient is no longer required. Email or SMS is acceptable. Add \na message explaining that email and/or SMS will be sent if contact info \nis provided.\n \n15) Jira #VSE-805: Add contact method preferences to VVS make appointment \nscreen - Provider.\n \nSDESAPPT VSE-1128, VSE-1129, VSE-1130\nProblem:\nAdd ability to indicate a provider's preferred contact method (email or \nSMS).\n \nResolution:\nFor providers, email is the required method of communication. If there is \na cell phone number, then an SMS will be sent in addition to the email. \nThis behavior will be described in a text label.\n \n16) Jira #VSE-861: Formalize JSON Return Errors.\nSDESAPPTDATA VSE-1128, VSE-1129, VSE-1130\n \nProblem:\nFix JSON returns to follow new JSON return pattern.\n \nResolution:\nJSON returns follow new JSON return pattern.\n \n17) Jira #VSE-863 - Updates/corrections to PtCSch code.\n \nProblem:\nSDESCLINICDATA VSE-1128, VSE-1129, VSE-1130\nUpdates/corrections to PtCSch code based on work done as part of VSE-737\n \nResolution:\nVS GUI was updated to utilize the optimized VistA RPCs associated with the\nwork done in a prior sprint related to VSE-737 and released in SD*5.3*785.\n \n18) Jira #VSE-876: Develop option to identify stuck MRTCs and disposition.\n \nProblem: \nA new menu option is needed to clean up those MRTC children where the \nSDESPATIENTDATA VSE-1128, VSE-1129, VSE-1130\nparent has been dispositioned and closed, but the child was left open.\n \nResolution:\nA new menu option, SDEC MRTC CHILD CLEANUP ("Stuck MRTC child cleanup \ntool") was created. The tool will go through all open return to clinic \nrequests that are MRTCs with a PID less than or equal to the date-90 days \n(or user entered date which is no sooner than -90 days). If the Parent \nis closed and dispositioned the child request will be closed and \nassigned the disposition based on the parents disposition.\n \n \n19) Jira #VSE-875: Update GUI logic for MRTC PIDs so that they are static \nbased on parent PID.\n \nProblem:\nMRTC PID dates should NOT be based on appointment made. PID should be \nstatic.\n \nResolution:\nMRTC PIDs are static based on parent PID.\n \nOPTIONS:\n20) Jira #VSE-876 - Develop option to identify stuck MRTCs and \ndisposition.\n \nProblem:\nA new menu option is needed to clean up those Multiple Return to Clinic \n(MRTC) children where the parent has been dispositioned and closed, but \nthe child was left open.\n \nResolution:\nA new menu option, SDEC MRTC CHILD CLEANUP ("Stuck MRTC child cleanup \n========\ntool") was created. The Tool will go through all open return to clinic \nrequests that are MRTCs with a PID less than or equal to the date-90 days \n(or user entered date which is no sooner than -90 days). If the Parent \n \n21) Jira #VSE-877: Update screens where buttons/fields/words are cut off.\n \nProblem:\nContent is cut off in GUI screens.\n \nResolution:\nSDSUP VSE-876\nUpdated screens where content was cut off.\n \n22) Jira #VSE-884: Update GUI so that request already \ndispositioned/canceled is not dispositioned again.\n \nProblem:\nUpdate GUI so that an MRTC request already dispositioned is not \ndispositioned again when MRTCs are dispositioned in bulk.\n \nResolution:\nFor tracking purposes, please add component(s) and note the associated\nSDEC MRTC CHILD CLEANUP VSE-876\nGUI was updated so that an already dispositioned MRTC request is not \ndispositioned again.\n \n23) Jira #VSE-886 - Formalize JSON Return Errors - SDEC RPCs.\n \nProblem:\nThere needs to be a unified way to log errors and return JSON \nformatted data objects to the VS GUI.\n \nResolution:\nSDECRPC VSE-1017, 1114, 1020, 1115, 1116, 1117, 1118, \nTwo new Application Program Interfaces (APIs) were created in VistA. One\nif for logging errors and the other for reporting back data. The Error API\nstandardized the text for the return messages and also allows additional\ninformation to be added to the standard messages if needed. The Data API\nwill always return and object, even if there were no corresponding records\nfound.\n \n24) Jira #VSE-942: Fix null reference error when using Hotkeys for \nswitching Calendar's View style.\n \n 1128, 1129, 1130\nProblem:\nThe GUI occasionally crashes when trying to update the calendar after a \nuser enters shift + either D, W, M or T. These correspond to the hotkeys \nused in the GUI for quickly switching the calendar between the Day, Week, \nMonth and Timeline views. \n \nResolution:\nAdded null check to the HotKeyEvents method to avoid null reference \nexception.\n \n \n25) Jira #VSE-946: Formalize JSON Return Errors.\n \nProblem: Fix JSON returns created over last several sprints to follow new \nJSON return pattern.\n \nResolution:\nUpdated error messages for JSON RPC calls to use new VSE error window.\n \n26) Jira #VSE-1016 - Add CHECK-IN STEP STATUS field to 409.84.\n \n \nProblem:\nTo support CTO's work on VSIP, we need to add a check-in step status \nfield to the appointment file.\n \nResolution:\nThe new CHECK-IN STEP STATUS (#3) multiple was added to the SDEC \nAPPOINTMENT (#409.84) file. This multiple has 2 fields: CHECK-IN STEP \nSTATUS (#.01) and DATE/TIME ENTERED (#1).\n \n27) Jira #VSE-1017 - Create SDES RPC to set value CS(IEN, value).\nREMOTE PROCEDURES:\n \nProblem:\nCreate a SDES RPC to set the check-in step status in the newly created \ncheck-in step status file (VSE-1016) by SDEC APPOINTMENT file IEN. Ensure \nthis can only be done for non-cancelled appointments.\n \nResolution:\nThe new SDES EDIT CHECK-IN ENTRY RPC was created and will return it data \nin JSON format.\n \n==================\n28) Jira #VSE-1020 - Create SDES RPC to get value CS(IEN).\n \nProblem:\nCreate a SDES RPC to get the check-in step status in the newly created \ncheck-in step status multiple (VSE-1016) by SDEC APPOINTMENT file IEN and \nthe check-in step status IEN. Return JSON of the check-in step status \nentry and date/time entry. If it doesn't exist in that multiple, return \nnull/0.\n \nResolution:\nSDES CREATE CHECK-IN ENTRY VSE-1115\nThe new SDES GET CHECK-IN STATUS RPC was created and will return it data \nin JSON format.\n \n29) Jira #VSE-1022 - Create new pre-checkin status file.\n \nProblem:\nCreate new check-in step status file with a field to track the check in \nstatuses.\n \nResolution:\nSDES EDIT CHECK-IN ENTRY VSE-1116\nThe new SDEC CHECK-IN STEP STATUS (#409.842) file was created to store \nthe necessary statuses related to checkins.\n \n30) Jira #VSE-1128 - Update RPC SDES Get Appointment List By Patient.\n \nProblem:\nAdditional pieces of data need to be returned to assist processing in the \nVS GUI.\n \nResolution:\nSDES GET ALL CHECK-IN ENTRIES VSE-1117\nThe needed data was identified in VistA and the SDES GET APPT LIST BY PAT \nJSON was updated to include this data in the JSON object returned to VS\nGUI.\n \n31) Jira #VSE-1129 - Update RPC SDES Get Appointment List By Clinic.\n \nProblem:\nAdditional pieces of data need to be returned to assist processing in the \nVS GUI.\n \nJira task(s) out to the right on the same line.\nSDES GET CHECK-IN ENTRY VSE-1118\nResolution:\nThe needed data was identified in VistA and the SDES APPT BY CLINIC JSON \nwas updated to include this data in the JSON object returned to VS GUI.\n \n32) Jira #VSE-1130 - Update RPC SDES Get Appointment.\n \nProblem:\nAdditional pieces of data need to be returned to assist processing in the \nVS GUI.\n \nSDES GET CHECK-IN STATUS VSE-1020\nResolution:\nThe needed data was identified in VistA and the SDES GET APPT JSON was\nupdated to include this data in the JSON object returned to VS GUI.\n \n33) Jira #VSE-1114 - Ad-hoc execution for Test Save Multiple User\nPreference Configurations.\n \nProblem:\nCreate RPC to get all check-in statuses for an appt in the check-in step\nstatus multiple.\nSDES GET CHECK-IN STATUSES VSE-1114\n \nResolution:\nA new RPC, SDES GET CHECK-IN STATUSES, has been created to retrieve all\ncheck-in statuses associated with an appointment.\n \n34) Jira #VSE-1115 - Ad-hoc execution for Test Updates/corrections to \nPtCSch code.\n \nProblem:\nCreate RPC to add a new entry to the new check-in step status file\nSDES SET CHECK-IN STATUS VSE-1017\n(409.842).\n \nResolution:\nA new RPC, SDES CREATE CHECK-IN ENTRY, has been created to add a new\nentry(status) to the new check-in step status file.\n \n35) Jira #VSE-1116 - Add CHECK-IN STEP STATUS field to 409.84.\n \nProblem:\nCreate RPC to edit entry in 409.842 (check-in step status file).\nSDES GET APPT JSON VSE-777, VSE-1130\n \nResolution: \nA new RPC, SDES EDIT CHECK-IN ENTRY, has been created to edit\nentries(statuses) in the new check-in step status file.\n \n36) Jira #VSE-1117 - Create SDES RPC to set value CS(IEN, value).\n \nProblem:\nCreate RPC to get all check-in entries in the check-in step status file.\n \nSDES GET APPT LIST BY PAT JSON VSE-775, VSE-1128\nResolution:\nA new RPC, SDES GET ALL CHECK-IN ENTRIES, has been created to retrieve\nall the entries from the new check-in step status file.\n \n37) Jira #VSE-1118 - Update "Print the Patient Letter." message to new \nformat.\n \nProblem:\nCreate RPC to get a single entry from the check-in step status file\n(409.842).\nSDES APPT BY CLINIC JSON VSE-776, VSE-1129\n \nResolution:\nA new RPC, SDES GET CHECK-IN ENTRY, has been created to retrieve a single\nentry from the new check-in step status file.\n \n \nJIRA tasks:\n \n-----------\n1) Jira #VSE-57: Changes made to User Preferences are not updating in \nthe RM Grid.\n \nProblem:\nChanges made to User Preferences are not updating in the RM Grid.\n \nResolution:\nThe data in the RM Grid will match the User Preference setting. Changes \nwill be saved and updated in the User Preference menu. The Clear button \nFILES:\nresets User Preferences and the RM Grid columns to the default sort order.\n \n2) Jira #VSE-775 Create Remote Procedure Call (RPC) SDES Get Appointment\nList By Patient.\n \nProblem:\nNeed to create a new SDES RPC to return an appointment list by patient and\nstart/end date.\n \nResolution:\n======\nThe new SDES APPT BY CLINIC JSON was created and will return it data in\nJSON format. Returned data includes:\nstring ResourceName (Clinic name)\nstring Notes\nstring Duration\nstring StartTime (appointment date time)\nstring EndTime\nstring AppointmentID\nstring AppointmentTypeIEN\n bool IsOverbook\n409.84 VSE-1016\n \n3) Jira #VSE-776 - Create RPC SDES Get Appointment List By Clinic.\n \nProblem:\nNeed to create a new SDES RPC to return an appointment list by clinic and \nstart/end date.\n \nResolution:\nThe new SDES APPT BY CLINIC JSON was created and will return it data in\nJSON format. Returned data includes:\n409.842 VSE-1022\nAppointment fields to return:\nstring ResourceName (Clinic name)\nstring Notes\nstring Duration\nstring StartTime (appointment date time)\nstring EndTime\nstring AppointmentID\nstring AppointmentTypeIEN\n bool IsOverbook\n \n\n\nBackup of SD*5.3*775 on Aug 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch SD*5.3*775 corrects the following Issues:\n \n1. A large number of Overbooks for a single slot will cause\n the clinic grid to not display in VistA.\n \n2. Variable Length Appointments are showing up incorrectly in \n the VistA Scheduling Graphical User Interface (GUI).\n\n
\nBackup of SD*5.3*782 on Aug 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nScheduling patch SD*5.3*782 modifies the screen for the SDAM MENU\nProtocol and corrects an error which occurs when an appointment is\ncanceled via Telehealth which creates an Incomplete Encounter Error.\n\n
\nBackup of SD*5.3*790 on Aug 16, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n \n VSE-979\n \n4) Jira #VSE-1094\n \nProblem: When scheduling an future appointment using VistA for a clinic \nthat has a future re-activation date, the resource is not linked to the \nappointment.\n \nResolution: When adding the resource, do not check the inactivation \nstatus.\n \n VSE-1127\n5) Jira #VSE-1127\n \nProblem/Task:\n The RECALL REMINDER (#403.5) file data, may sometimes be unavailable \n because it was removed upon making an appointment.\n \nResolution:\n Created an RPC (SDEC RECALLRMV BY DFN JSON) to retrieve the needed data \n from the RECALL RMINDER REMOVED (#403.56) file.\n \n \n6) Jira #VSE-1144\n \nProblem:\n \nResolution:\n \n7) Jira #VSE-1146\n \nProblem: Eligibility code is not returned when an appointment does not \nhave resource.\nSprint 15:\n \nResolution: When no resource is found, get Hospital Location from the \nAppointment sub file of the Patient file. Use the Hospital Location to \nget the Enrollment Code and Resource.\n \n8) Jira #VSE-1154\n \nProblem:\n \nResolution:\n VSE-985\n \n9) Jira #VSE-1155\n \nProblem:\n \nResolution:\n \n10) Jira #VSE-1157\n \nProblem:\n VSE-1037\nEnsure Contact Attempts for Recall Requests are included when converted \nto APPT\n \n \nResolution:\nModified the Request Pointer in SDEC CONTACT (#409.86) file to reflect \nthe appropriate SDEC APPOINTMENT (#409.84) file entry.\n \n \n11) Jira #VSE-1171\n VSE-1087\n \nProblem:\nBased on the Research performed in VSE-235 it was determine that a check \non the Appt Status needs to be added to the SDEC APPADD RPC to prevent it \nfrom returning the original Appt for the Same Patient, Date and Clinic \nwhen the original Appt has a status of Cancelled.\n \nResolution:\nUpdated APPTGET^SDECUTL to include a status check for the following \nstatuses:\n VSE-1094\n \nC:CANCELLED BY CLINIC\nCA:CANCELLED BY CLINIC & AUTO RE-BOOK\nN:NO-SHOW\nNA:NO-SHOW & AUTO RE-BOOK\nPC:CANCELLED BY PATIENT\nPCA:CANCELLED BY PATIENT & AUTO-REBOOK\n \n12) Jira #VSE-1172\n \n VSE-1144\nProblem:\nThere were 2 issues identified during the analysis on VSE-235:\n 1. Locking/Unlocking of ^SDEC(409.84 was using variable DFN instead of\n SDECAPPTID.\n 2. A more efficient cross reference could be used for the \n APPTGET^SDECUTL subroutine.\n \nResolution:\n 1. Routine SDEC07 was updated to use SDECAPPTID when locking or \n unlocking #409.84.\n VSE-1146\n 2. Routine SDECUTL was updated to use the APTDT x-ref.\n \n \n) Jira #VSE-\n \nProblem:\n \nResolution:\n \n) Jira #VSE-\nVS GUI v. 1.7.9 Release\n VSE-1154\n \nProblem:\n \nResolution:\n \n) Jira #VSE-\n \nProblem:\n \nResolution:\n VSE-1155\n \n) Jira #VSE-\n \nProblem:\n \nResolution:\n \n) Jira #VSE-\n \nProblem:\n VSE-1157\n \nResolution:\n VSE-1171\n VSE-1172\n \nFILES:\n======\n \n \n \nROUTINES:\n=========\n VSE-1171 - updated to add a check for\nCancelled Appts to the\n SDEC APPADD RPC\nSDEC07 - VSE-1172 - updated to address Locking/Unlocking issue from\n VSE-235\nSDEC52CRMVJSON - VSE-1127 - Added logic to retrieve the RECALL REMINDER \n data from the RECALL REMINDER REMOVED (#403.56) file.\nSDEC55A VSE-1146\nFor tracking purposes, please add component(s) and note the associated\nSDESAPPTUTIL VSE-1146\nSDESCHECKIN VSE-985\nSDEC50 VSE-985\nSDEC08 VSE-1157\n \n \n \nOPTIONS:\n========\n \nJira task(s) out to the right on the same line.\n \n \nREMOTE PROCEDURES:\n==================\n \nSDEC GET RECALLRMV BY DFN JSON- VSE-1127 Retrieve RECALL REMINDER data \n from RECALL REMINDER REMOVED (#403.56) file.\n \n \n \n \n \nJIRA tasks:\n-----------\n1) Jira #VSE-???(979)\n \nProblem/Task:\n When doing a drag and drop with a recall appointment, the request is \n created on the RM Grid and not removed when the appointment is made. \n \n This should be a behind the scene action...it shouldn't display on the \nSprint & Associated Tasks:\n RM Grid.\n \nResolution:\n \n \n2) Jira #VSE-985\n \nProblem: Display a visual indicator for Pre-Checkin Step in VS GUI.\n \nResolution: Update SDEC FAPPSGET RPC to include a new field that will \n==========================\nindicate if the patient has completed pre-checkin step for the \nappointment.\n \n2) Jira #VSE-1037\n \nProblem: The job SDRR CLEANUP needs to be disabled so that it cannot be \nset up to run as a nightly job at sites. Follow the same pattern that \nBrian Rene did for the EWL option.\n \nResolution: Update OPTION SDRR CLEAN-UP to include OUT OF ORDER MESSAGE \nSprint 14:\nso that it will not be available. Also update routine SDRRCLR to QUIT \nat the top of the routine so that it will not run. These updates \ndisable the menu option from being run manually or called from the \nnightly Schedule/Unschedule Option under the TASKMAN MANAGEMENT option.\n \n3) Jira #VSE-1087\n \nProblem:\n \nResolution:\n\n
\nVS GUI v. 1.7.10 Release\n VSE-1112 - VistA: Update so that appointment requests are only reopened\n for certain cancellation reasons\n VSE-1199 - .NET: Add Failure to Respond as disposition reason for SDEC \n requests\n VSE-1207 - .NET VS GUI: Display most recent checkin step status\n VSE-1211 - .NET: Update Code to Open APPT Request when PtCSch \n Appointment is No-Showed\n VSE-1214 - .NET: Update so that appt requests are only reopened for \n certain cancellation reasons\n VSE-1218 - VistA: Recall comments are not being carried over to APPT \n \n request created on cancellation\n VSE-1219 - VistA: Update Code to Open APPT Request when PtCSch \n Appointment is No-Showed\n VSE-1220 - VistA: Add Failure to Respond as disposition reason for SDEC \n requests\n VSE-???? - NEW RPD TO INDICATE IF INSURANCE VERIFICATION IS NEEDED\n VSE-1305 - VistA: CAs displaying as green when they are not current for \n APPTs created based on PtCSch\n VSE-1303 - Create RPC to return insurance verification info\n VSE-1123 - VistA: Update Code to show last selected Provider used.\nFor tracking purposes, please add component(s) and note the associated\n \nFILES:\n======\nVSE-1220\n SDEC APPT REQUEST (#409.85) updated DISPOSITION (#21) field to a pointer\n SDEC DISPOSITION REASON - New file to hold Dispostion Reasons\n \n \nROUTINES:\n========= \nJira task(s) out to the right on the same line.\nSDEC08 - VSE-1305; Rectify FALSE/TRUE CURRENT data in Contact Attempts for\n proper GREEN/BEIGE color display\n VSE-1219; Moved code to new routine SDECRECREQ due to size limits\n VSE-1218; Define NEWPID variable\nSDECRECREQ - VSE-1219; Moved code from SDEC08 due to rtn size limits\n VSE-1112: Don't open a new Appt Request for 4 Cancellation\n Reasons\n VSE-1218: Rectify transfer of Recall Comments upon \n Appointment Cancellation\n VSE-1220: VistA: Add Failure to Respond as disposition \n \n reason for SDEC requests\nSDECAR - VSE-1112: Don't open a new Appt Request for 4 Cancellation \n Reasons\n - VSE-1220: Updated mapping of Dispostions to pointer value\n Added new Disposition FAILURE TO RESPOND\nSDEC31 - VSE-1219: Recall Request Appt NOSHOW\nSDEC50 - VSE-1207: Display most recent checkin step status\nSDEC792P - VSE-1220: VistA: Add Failure to Respond as disposition \n reason for SDEC requests\nSDES - VSE 1303: Create RPC to return insurance verification info\nSprint & Associated Tasks:\nSDESCKNSTEP - VSE-1207: Display most recent checkin step status\nSDESPATRPC - VSE 1303: Create RPC to return insurance verification info\nSDM1A - VSE 1094: VistA: Correct code to prevent appts with no resource\n \nOPTIONS:\n=======\nSDECRPC - VSE - ????\n \nREMOTE PROCEDURE:\n================\n==========================\nSDES GET INSRUANCE VERIFY REQ - VSE - ????\nSprint 16:\n VSE-1094 - VistA: Correct code to prevent appts with no resource\n\n
\nRefer to National Patch Module for details.\n\n
\nThis patch provides fiscal year 2022 annual updates to the CLINIC STOP \n(#40.7) file as requested by the Office of Finance, Managerial Cost \nAccounting Office (MCAO).\n\n
\n \nVSE-1278: VistA: CONSULT - NO SHOW- Undoing No Show request still on RM \n Grid\nVSE-1307: .NET: CONSULT - NO SHOW- Undoing No Show request still on RM \n Grid\nVSE-1328: INC18922837 - ConsultIEN does not belong to Table Error\n \nStory\nVSE-1240: .NET GUI: Display all checkin steps for an appointment\nVSE-1327: .NET: Redundant data on no show for Consults/Procedures\nVSE-1367: VistA: Update data returned/displayed in expand entry for appts \nVersion VS GUI R1.7.11 w SD*5.3*794\n at same date/time\nVSE-1368: .NET: Expand entry - display error message when appt data is no \n longer available\nVSE-1370: VistA: SDES RPC to create appointment request entry\nVSE-1371: VistA: SDES RPC to read an appointment request entry\nVSE-1372: VistA: SDES RPC to update an appointment request entry\nVSE-1373: VistA: SDES RPC to disposition an appointment request entry \n \nFiles:\n======\n \n \nRoutines:\n=========\nSDECEPT - VSE-1367 Update GETDEM to determine if Appt can be expanded.\n \nOptions:\n========\n \nRPCs:\n=====\nDefect\nSDEC EP DEMOGRAPHICS - VSE-1367 add optional 3rd parameter for IEN of Appt\nVSE-761: VistA: VVS - Cancellation of a VVS appointment from \n "SDCANCEL/SDAM" VistA, VVS appointment ID field is not deleting\n from the SDEC APPOINTMENT file\nVSE-1267: RECALL - Editing an Appt Request that was previously a Recall \n you have to add Provider\n\n
\nVersion VS GUI R1.7.12 w SD*5.3*796\n wrong provider\nVSE-1282: .NET: Update editing an appointment request to not reference \n the type specific wait list tables in Key\nVSE-1306: VistA: Post Install Routine to correct Recalls with incorrect\n provider.\nVSE-1340: VistA: No-Showing Child MRTC results in lost parent link\nVSE-1353: .NET GUI: Print medication list\nVSE-1355: VistA: VSIP - Create E-Checkin Allowed field in clinic setup\nVSE-1375: VistA: Create Post-install Routine (Clean up CID)\nVSE-1395: VistA: Prevent Back-Dating PID\n \nVSE-1405: Test VSE report features after removal of report file\nVSE-1406: .NET sanitize user input in patient search\nVSE-1409: .NET MVC: Pop-Up Window to Display Med Sheet\nVSE-1437: VistA: User Preferences - Post Install routine to clear old \n user preferences\n \nFiles:\n======\n44.20 - VSE-1355 Created field 20\n44.21 - VSE-1355 Created field 21\n \n \nRoutines:\n=========\nSDEC08 : VSE-761\nSDEC796P : VSE-1375,1437,1306\nSDEC52B : VSE-1267\nSDEC32 : VSE-1459 \n \nOptions:\n========\nVSE- 761: VistA: VVS - Cancellation of a VVS appointment from \n \nRPCs:\n=====\n \nInput Template:\n===============\nSDB - VSE-1355 Added field 20 and field 21\n "SDCANCEL/SDAM" VistA, VVS appointment ID field is not deleted\n from the SDEC APPOINTMENT file\nVSE-1006: VS GUI: Display Checkin Indicators View Model\nVSE-1203: 508 - .NET: Tabbing on Make Appt Request screen skips PID field\nVSE-1267: VistA: APPT request from canceled Recall appointment displays \n\n
\n \n displaying in search\nVSE-1509: VistA: Create new RPC based on SDEC SEARCH VVS PROVIDERS RPC \n to return JSON\nVSE-1559: VistA: Update SDES RPCs to follow standard naming convention\nVSE-1600: VistA: Research on Disposition Codes\n \n \nROUTINE:\n========\nSDES: VSE-1463\nVSE-1431: .NET: Cannot Schedule VVC in VS GUI - Must Schedule in VCM - \nSDESBLKANDMOVE: VSE-1463\nSDESJSON: VSE-1463\nSDECAR: VSE-1600\nSDEC797P: VSE-1464\n \nRPC:\n====\nSDEC GETVVSMAKEINFO JSON: VSE-1431, VSE-1434\nSDEC SEARCH VVS PROVIDERS JSON: VSE-1474, VSE-1509\nSDES MAKE APPT BLOCK AND MOVE: VSE-1463\n use new RPC returning JSON\nSDES SEARCH CLINIC \n \nOPTION:\n=======\nSDECRPC: VSE-1434, VSE-1474, VSE-1509, VSE-1559\nSDESRPC: VSE-1463\nVSE-1434: VistA: SDEC GETVVSMAKEINFO Contains -1\nVSE-1444: 508 - .NET: Tabbing Incorrect Function on Make PtCSch Request\nVSE-1463: VistA: Create Block and Move RPC\nVSE-1464: VistA: Add "Block and Move" Cancellation Reason\nVSE-1465: .NET: Block and Move context menu\nVSE-1474: .NET: -1 in provider phone number results in provider not \n\n
\n \n (44)\n Todd Wise\nVSE-1563: VistA: Create RPC to modify existing clinic in HOSPITAL LOCATION\n file (44)\n Todd Wise\nVSE-1564: VistA: Create RPC to get clinic information from HOSPITAL \n LOCATION file (44)\n Anuradha Paturi\nVSE-1565: VistA: Create RPC to remove a clinic from HOSPITAL LOCATION file\n (44)\n \n Anuradha Paturi\nVSE-1580: VistA: Create EAS Tracking Number field\n Kathryn Leyva\nVSE-1581: VistA: Adjust current SDES RPCs to accept EAS transaction ID\n Brandon Butler\nVSE-1592: .NET GUI: Update Certificate Selection on VS GUI Login\n Ryan Johnson\nVSE-1599: .NET MVC: Demographics indicator on appointment list\n Unassigned\nVSE-1606: VistA: Create new RPC based on SDEC GETREGA\nVSE-1411: .NET GUI: Demographics indicator on check-in screen\n Lori Barber\n \n \nFiles:\n======\n409.84 - VSE-1580 created field 100\n409.85 - VSE-1580 Created field 100\n403.5 - VSE-1580 Created field 100\n403.56 - VSE-1580 Created field 100\n \n Carter Reynolds\nRoutines:\n=========\nSDRRISRU - VSE-1581 include EAS# when building 403.56 entry upon \n recall delete\nSDEC07 - VSE-1581 include EAS# as input in RPC \nSDEC08 - VSE-1581 include EAS# as input in RPC\nSDEC52A - VSE-1581 include EAS# as input in RPC\nSDEC52CJSON - VSE-1581 include EAS# in SDRECALL array\n VSE-1562 1563 create / update clinic\n \nVSE-1539: .NET Use AssemblyInfo version string for everything\nSDEC52CRMVJSON -VSE-1581 include EAS# in SDRECALLRMV array\nSDECAR2 - VSE-1581 include EAS# in APPT REQ\nSDESAPTREQSET - VSE-1581 include EAS# in APPT REQ\nSDESARCLOSE - VSE-1581 include EAS# in DISP REQ\nSDESBLKANDMOVE - VSE-1581 include EAS# as input in RPC/APIs\nSDESARGET - VSE-1581 add EAS# to returned array\nSDES - VSE-1606 new RPC to return patient registration\n VSE-1581 add EAS# as input parameter in DISPOSITION, APPT REQ\n CREATE, APP REQ UPDATE, and BLOCK and MOVE\n VSE - 1562 1563 create / update clinic\n David Earnshaw\nSDEC - VSE-1581 add EAS# as input parameter in APPDEL\nSDESGETREGA - VSE-1606 new RPC to return patient registration\nSDESCLINICSET - VSE-1562 1563 create / update clinic\nSDESCLINICSET2 - VSE-1562 1523 create / update clinic \n \nRemote Procedures:\n==================\nSDES GET PATIENT REGISTRATION - VSE-1606 new RPC to return patient regist\nSDES CREATE CLINIC - VSE-1562 create clinic\nSDES EDIT CLINIC - VSE-1563 update clinic\nVSE-1540: .NET: Simplify and standardize usage of VSEMessageWindow\nSDES DISPOSITION APPT REQ - VSE-1581 add EAS Tracking Number as input \n parameter\nSDES SET APPT REQ CREATE - VSE-1581 add EAS Tracking Number as input \n parameter\nSDES SET APPT REQ UPDATE - VSE-1581 add EAS Tracking Number as input \n parameter\nSDES MAKE APPT BLOCK AND MOVE - VSE-1581 add EAS Tracking Number as input\n parameter\nSDEC APPADD - VSE-1581 add EAS Tracking Number as input parameter\nSDEC APPDEL - VSE-1581 add EAS Tracking Number as input parameter\n Stephen Mammay\nSDEC RECSET - VSE-1581 updated the input parameter INP array\nVSE-1562: VistA: Create RPC to add new clinic to HOSPITAL LOCATION file\n\n
\nVSE-1457: Parent MRTC is removing from the rm grid, when child request \n LOCATION file (44) - Unassigned\nVSE-1568: VistA: Create RPC to view/get availability for a clinic in \n HOSPITAL LOCATION file (44) - Rose\nVSE-1569: VistA: Create RPC to cancel availability for a clinic in \n HOSPITAL LOCATION file (44) - Anu\nVSE-1598: .NET GUI: Implement new JSON mapping model on appt request LSD \n Services\nVSE-1616: VistA: Wrap VPS Patient Registration RPC in SDEC RPC - Brandon\nVSE-1629: .NET: Check For and Fix Orphaned MRTC Children\nVSE-1630: VistA: Check in patient when E-checkin is complete - Brandon\n associated with that parent are still in the rm grid.\nVSE-1652: VistA: INC19671287 Coding Change Incorrect Provider Email in - \n VVC Appt - Lori\nVSE-1670: .NET: Update VVS Provider Search to display email address\nVSE-1742: update the VVC STOP CODE multiple for VS GUI NATIONAL entry; add\n codes 648 and 679; delete code 225 - Kathryn\nVSE-1777: VistA: Add EAS Transaction ID to Check-In RPCs \n \n========= \nRoutines:\nSDEC800P: VSE-1742; update VVC STOP CODE multiple with new codes 648 and \nVSE-1463: VistA: Create Block and Move RPC - Todd & Matt\n 679; and delete existing code 225\nSDESCLNSETAVAIL: VSE-1566 Create new RPC for Clinic Availability\nSDES: VSE-1566 Updated to add SETCLINAVAIL entry point\nSDESJSON: VSE-1566 Updated to add new error messages\nSDECUPDPATPREREG: VSE-1616 - Wrap VPS Patient Registration RPC in SDEC RPC\nSDECVVS: VSE-1652 - Corrected to include all records with same name\nSDECPRVSRCHJSON: VSE-1652 - corrected to include all records w/ same name\nSDESCLINICAVAIL: VSE-1568 This is a new routine that retrieve availability\n for a clinic in HOSPITAL LOCATION file (44)\nSDEC25: VSE-1630 - Modified to prevent errors upon checkin in patient\nVSE-1465: .NET: Block and Move context menu\nSDESCKNSTEP: VSE-1630 - Modified to call SDEC CHECKIN upon an appointment \n receiving a check-in step status of "E-CHECK-IN COMPLETE"\nSDESBLKANDMOVE: VSE-1463 - Updated routine based on unit testing errors.\nSDESCKNSTEP: VSE-1777 - Updated routine to include EAS Tracking Number. \nSDESCCAVAIL: VSE-1569 - New routine to Cancel Clinic Availability\n \nRPCs:\n=====\nSDES CREATE CLIN AVAILABILITY: VSE-1566 Set Clinic Availability\nSDEC EDIT PAT PRE-REGISTRATION: VSE-1616 Update patient pre-registration\nVSE-1495: .NET: View/Edit Appointment not Displaying Eligibility for \nSDES GET CLINIC AVAILABILITY: VSE-1568 This is a new RPC that returns \n back available appointment slots within a\n given timeframe for a given clinic.\nSDES MAKE APPT BLOCK AND MOVE: VSE-1463 Removed extra spaces from \n description.\nSDES CANCEL CLINIC AVAILABLITY: New RPC to Cancel Clinic Availbility \nOptions:\nSDECRPC\nSDESRPC\n Appointments at Inactive Clinics\nVSE-1566: VistA: Create RPC to add availability for a clinic in HOSPITAL \n LOCATION file (44) - Matt & Todd\nVSE-1567: VistA: Create RPC to edit availability for a clinic in HOSPITAL \n\n
\nThis patch will send non-clinic days, holidays and blocked clinic hours \nto TMP via HL-7 messaging. It will send additional station information to \nassist in locating the correct clinic for sending transactions. It moves \nthe SD TELE TOOLS menu from SDSUP to SDMGR. It adds security key SDTOOL.\n\n
\nPatch SD*5.3*793 will inactivate all Veterans Choice Program (VCP) \nand Veterans Choice List (VCL) clinics, and any corresponding\nWait List clinics. It will also disposition any VCL or VCP Wait\nList entries.\n\n
\nVSE-197: Add Clinic Group - Remediate 508 findings in Add Clinic Group \nVSE-1206: VistA: Rewrite SDEC APPDEL in SDES \nVSE-2070: VistA: Update Block and Move functionality to account for PtCSch\nVSE-2093: VistA: Incorrect location defaults in Integrated VistA sites \n for VVS appts\nVSE-2098: VistA: Canceling of VVS appointment should not delete VVS \n Appointment ID\n \nRoutines:\n=========\nSDCNP0 - VSE-1886 added REOPEN parameter to formal list at CAN+8\n form (Felix)\nSDEC07 - VSE-1893 updated logic to prevent all records as overbooks\nSDEC08 - VSE-1886 removed out-dated comment from SDECCAN+45 to support the\n change made at CAN+8^SDCNP0\n VSE-2098 removed logic that was deleting VVS appointment ID\nSDEC09 - 1902 - Added Preferred Gender to the end of the return parameter\nSDESBLKANDMOVE - VSE-1893 - Block & Move\n VSE-2070 - Block & Move\nSDESBLKANDMOVE1 - VSE-1893 - Block & Move\nSDESUTIL - VSE-1893 - SDES Utilities\nSDESCLINICUTIL - VSE-1893 - Block & Move\nVSE-1813: SDES RPC to return VPID (or IEN and Station ID), user name, \nSDESCANCELAPPT - VSE-1206\nSDESJSON - VSE-1206,VSE-1813\nSDES - VSE-1206,VSE-1813\nSDESGETUD - VSE-1813\nSDECVVS - VSE-2093\nSDECVVSJSON - VSE-2093 \n \nRPCs:\n====\nSDES CANCEL APPT - VSE-1206\n scheduling options and keys for VSE GUI user.\nSDEC GETREGA - VSE-1902 - Get Basic registration/demographic information\nSDES GET USRPROFILE - VSE-1813 - RPC TO GET SD USER PROFILE\nVSE-1886: VistA: Update VistA to reopen appointment request when \n canceling (Kathryn)\nVSE-1893: VistA: Updates to Block and Move (Matt & Todd)\nVSE-1901: .NET GUI: Update to display preferred gender (Matt P)\nVSE-1902: VistA: Update patient info RPC to return preferred gender (Lori)\n\n
\nAccess Performance Measure \n\n
\nPlease see the National Patch Module.\n\n
\n \n LOCATION file (44)\nVSE-2011: VistA: Pending RTC Order Cleanup Tool incorrectly dispositions \n pending orders - Lori Ann\nVSE-2046: VistA: Create SDEC RPC to return a user's Station ID\n \nIncrement 2 Sprint 3\n \nVSE-1937: SDES PtCSch CRUD RPCs - Create - Lori Ann\n \nVSE-1938: Create SDES RPC to Read a Recall request\nVSE-1948: ABLE TO CANCEL CHECKED IN APPT. DEFECT.\n \nVSE-1939: Create SDES RPC to Update a PtCSch request - Lori Ann\n \nVSE-1940: Create SDES RPC to delete (disposition) a PtCSch request - \nKathryn\n \nVSE-2046: VistA: Create SDEC RPC to return a user's Station ID\n \nVSE-2049: Update system to count established patients at 3 years\n \nVSE-189 - Print Letter Message - Remediate 508 findings in Print Letter \nVSE-2185: VistA: Block and Move on Clinics Starting at Midnight freezes\n GUI\n \nRoutines:\n========\nSDEC1 - VSE-2046\nSDECDUZ - VSE-2046\nSDECRTCF - VSE-2011\nSDESCLNSETAVAIL - VSE-1567\nSDESJSON - VSE-1937, VSE-1939,VSE-1940\n for.\nSDESUPDRECREQ - VSE-1937, VSE-1939\nSDEC07 - VSE-1893\nSDESGETRECALL - VSE-1938\nSDEC50 - VSE-2049\nSDES - VSE-1937,VSE-1938,VSE-1939,VSE-1940\nSDESDISPRECALL - VSE-1940\nSDESBLKANDMOVE - VSE-2185\nSDESBLKANDMOVE1 - VSE-2185\n \nRPCs:\nVSE-207: .NET: Midnight timestamp for DateTime fields in SDEC APPOINTMENT\n=====\nSDES EDIT CLINIC AVAILABILITY - VSE-1567\nSDEC GET STATION ID JSON - VSE-2046\nSDES GET RECALL BY IEN - VSE-1938\nSDES GET RECALLS BY DFN - VSE-1938\nSDES DISPOSITION RECALL REQ - VSE-1940\nSDES CREATE RECALL REQ - VSE-1937\nSDES EDIT RECALL REQ - VSE-1939\n \nOptions:\n file causes error in VS GUI.\n========\nSDECRPC - VSE-1567,2046,1938\nSDESRPC - VSE-1937,VSE-1939,VSE-1940\nVSE-1467: VVC - Arizona time zone is not an option when creating a VVC \n appointment, resulting in links sent at the incorrect time.\nVSE-1567: VistA: Create RPC to edit availability for a clinic in HOSPITAL\n\n
\nVSE-2074: .NET: Allow user to update PID when rescheduling an appointment \nVSE-2121: .NET GUI; VVS crashing if Web Service to cancel VVS fails.\nVSE-2123: Swap methods in CancelApptPresentationModel lines 200/201 so \n that VVS ID is removed from VistA AFTER the VVS appointment is\n cancelled.\nVSE-2124: Log VVS Web Service call when cancelling an appt.\nVSE-2126: Vista: Update roll and scroll to move injected code for deleting\n VVSID to after the SDCAN comes back with success and not error.\nVSE-2143: VistA: Provider does not show up in lookup\nVSE-2208: VistA: RPCs need to return station number \n \n that was canceled by patient\n \n \nFILES:\n======\n \n \nROUTINES:\n=========\nSDCNP0 - VSE-2109\nSDES - VSE-2108\nVSE-2095: VistA: Update RPC SDES GET PATIENT REGISTRATION\nSDESCANCELAPPT - VSE-2126\nSDESGETREGA - VSE-2095\nSDECPRVSRCHJSON - VSE-2143\nSDECDUZ - VSE-2208 \nSDECVVS - VSE-2208\nSDECVVSJSON - VSE-2208\n \nREMOTE PROCEDURES:\n==================\nSDES CREATE CLINIC - VSE-2201 \nVSE-2096: VistA: Assign SDES RPCs to appropriate menu options\n \nOPTIONS:\n========\nSDESRPC - VSE-2096\nVSE-2106: .NET GUI: VVS Appointment cancellation during Block and\n Move/Drag and Drop\nVSE-2108: VistA: Create SDES Create RPC wrapper to send null SDIEN\nVSE-2109: Vista: Update SDES CANCEL RPC to not remove VVS link\nVSE-2114: .NET GUI; VVS appointments converting to incorrect time zones.\n\n
\nEMERGENCY PATCH TO CORRECT ERROR IN RESTORE CLINIC AVAILABILITY FROM \nPATCH SD*5.3*780\n\n
\nVSE-175: Tasks Tab - Help section\n (#44)\nSDES GET APPT BY IEN - VSE-2107\nSDES GET APPT CHECK-IN STEP - VSE-2107\nSDES GET APPT CHECK-IN STEPS - VSE-2107\nSDES GET APPT REQ BY IEN - VSE-2107\nSDES GET APPT REQ BY PATIENT - VSE-2107\nSDES GET APPTS BY CLINIC - VSE-2107\nSDES GET APPTS BY PATIENT - VSE-2107\nSDES GET APPTS BY RESOURCE - VSE-2107\nSDES GET CHECK-IN STEP - VSE-2107\nSDES GET CHECK-IN STEPS - VSE-2107\nVSE-1944: VistA: SDES RPC to delete appointment in HOSPITAL LOCATION \nSDES GET CLIN AVAILABILITY - VSE-2107\nSDES GET CLINIC INFO - VSE-2107\nSDES GET INSURANCE VERIFY REQ - VSE-2107\nSDES GET PATIENT REGISTRATION - VSE-2107\nSDES GET RECALL BY IEN - VSE-2107\nSDES GET RECALLS BY DFN - VSE-2107\nSDES GET USRPROFILE - VSE-2107,VSE-2223\nSDES INACTIVATE/ZZ CLINIC - VSE-2107\nSDES SET APPT CHECK-IN STEP - VSE-2107\nSDES SET CHECK-IN STEP - VSE-2107\n file (#44)\n \n \nOPTIONS:\n========\nSDESRPC - VSE-2107\nVSE-1945: Allow users to update PID when no-showing an appointment\nVSE-2074: .NET: Allow user to update PID when rescheduling an \n appointment that was canceled by patient\nVSE-2107: VistA: Add EAS Tracking Number to all SDES RPCs\nVSE-2114: .NET GUI: VVS appointments are converting to incorrect time\n zones.\nVSE-2223: - VistA: Update SDES Get User Profile RPC to receive SECID\nVSE-191: Pending Appointment Letter - Remediate 508 findings in Pending\n rather than VPID\nVSE-2226: VistA: Updates to support VVS timezone correction\nVSE-2231: VistA: Update the Insurance Verification Logic in the SDES \n GET INSURANCE VERIFY REQ RPC.\nVSE-2333: VistA: RPC SDES CREATE CLINIC defaults clinic start time to\n Midnight when editing and clinic start time not answered\nVSE-2264: VistA: Block and Move requires cancel reason.\nVSE-2333: VistA: RPC SDES CREATE CLINIC defaults clinic start time to \n Midnight when editing and clinic start time not answered.\n \n Appointment Letter form\nFILES:\n======\nRECALL REMINDERS (#403.5) EAS TRACKING NUMBER (#100) - VSE-2107\nRECALL REMINDERS REMOVED (#403.56) EAS TRACKING NUMBER (#100) - VSE-2107\nSDEC APPOINTMENT (#409.84) EAS TRACKING NUMBER (#100) - VSE-2107\nSDEC APPT REQUEST (#409.85) EAS TRACKING NUMBER (#100) - VSE-2107\n (#409.85) PID CHANGE ALLOWED (#49)\nPID HISTORY (#409.854) PID HISTORY (#50) \nSDEC CONSULT PID HISTORY (#409.87) FULL FILE\n \nVSE-201: Reports Tab - Remediate 508 findings in Reports Tab form\nROUTINES:\n=========\nSDEC07 - VSE-2107,2074\nSDEC08 - VSE-2107\nSDES - VSE-2107,VSE-2223,VSE-1943\nSDESAPPT - VSE-2107\nSDESAPPTDATA - VSE-2097\nSDESAPTREQSET - VSE-2097\nSDESBLKANDMOVE - VSE-2107,VSE-2264\nSDESCANCELAPPT - VSE-2107\nVSE-1941: VistA: SDES RPC to create appointment in HOSPITAL LOCATION \nSDESCCAVAIL - VSE-2107\nSDESCKNSTEP - VSE-2107\nSDESCLINICAVAIL - VSE-2107\nSDESCLINICSET - VSE-2107,VSE-2333\nSDESCLNSETAVAIL - VSE-2107\nSDESDISPRECALL - VSE-2107\nSDESARCLOSE - VSE-2107\nSDESARGET - VSE-2107\nSDESGETRECALL - VSE-2107\nSDESGETREGA - VSE-2107\n file (#44)\nSDESGETUD - VSE-2107,VSE-2223\nSDESINACTCLINIC - VSE-2107\nSDESJSON - VSE-2107,VSE-2223\nSDESPATRPC - VSE-2107,VSE-2231\nSDESRTVCLN - VSE-2107\nSDESUPDRECREQ - VSE-2107\nSDECDUZ - VSE-2226\nSDECVVS - VSE-2226\nSDESVVSJSON - VSE-2226\nSDESUTIL - VSE-2107,VSE-2226 \nVSE-1942: VistA: SDES RPC to update/edit appointment in HOSPITAL \nSDECDATE - VSE-2226\nSDAMUTDT - VSE-2226\nSDEC - VSE-2074\nSDEC07 - VSE-2074\nSDEC08 - VSE-2074\nSDEC31 - VSE-2074\nSDECAR2 - VSE-2074\nSDECAR4 - VSE-2074\nSDECCONSJSON - VSE-2074\nSDECRECREQ - VSE-2074\n LOCATION file (#44)\nSDECAR - VSE-2074\nSDESGETCLINAPPT - VSE-1943\n \n \nREMOTE PROCEDURES:\n==================\nSDES CANCEL APPT - VSE-2107\nSDES CANCEL CLIN AVAILABILITY - VSE-2107\nSDES CREATE APPT BLK AND MOVE - VSE-2107\nSDES CREATE APPT REQ - VSE-2107\nVSE-1943: VistA: SDES RPC to read appointment in HOSPITAL LOCATION file \nSDES CREATE CLIN AVAILABILITY - VSE-2107\nSDES CREATE CLINIC - VSE-2107\nSDES CREATE RECALL REQ - VSE-2107\nSDES DISPOSITION RECALL REQ - VSE-2107\nSDES DISPOSITION APPT REQ - VSE-2107\nSDES EDIT APPT REQ - VSE-2107\nSDES EDIT CHECK-IN STEP - VSE-2107\nSDES EDIT CLINIC - VSE-2107\nSDES EDIT CLINIC AVAILABILITY - VSE-2107\nSDES EDIT RECALL REQ - VSE-2107\n\n
\n VSE-178: - Tasks Tab - Appointment Calendar\nVSE-1705: - VistA: INC19650386 Issue with Clinic Activation/Reactivation \n Dates\nVSE-2262: - VistA: Create READ RPC for Credit Stop File\nVSE-2263: - VistA: Update SDES GET APPTS BY PATIENT RPC\nVSE-2312: - VistA: Update SDEC GETVVSMAKEINFO JSON to return single \n offset for time zone\nVSE-2315: - .NET: Update front end to use SDEC GETVVSMAKEINFO JSON single \n offset for time zone\nVSE-2319: - VistA: Update SDES GET INSURANCE VERIFY REQ RPC\nVSE-2327: - VistA: Add SDES GET USER INFO to SDECRPC menu option\n VSE-179: - Tasks Tab - Calendar Appointment Selected Item\nVSE-2341: - VistA: Update SDES SET APPT CHECK-IN STEP\nVSE-2350: - VistA: RPCs should return empty array\nVSE-2351: - VistA: Create an SDES RPC to return current patch number \nVSE-2354: - VistA: Create new RPC to get User Profile by DUZ \nVSE-2552: - Block and Move - Expand Entry of New APPT shows incorrect PID\n \nROUTINES:\n=========\nSDEC1 - VSE-2312\nSDEC03 - VSE-1705\n VSE-182: - .NET: Patient Information - Remediate 508 findings in Patient \nSDECVVSJSON - VSE-2312\nSDESAPPT - VSE-2263\nSDESCKNSTEP - VSE-2341\nSDESJSON - VSE-2341\nSDESPATRPC - VSE-2319\nSDES - VSE-2351;VSE-2262;VSE-2354\nSDES01C - VSE-2350\nSDESGETSTOPCODE - VSE-2262\nSDESPATCHINFO - VSE-2351\nSDESBLKANDMOVE - VSE-2552\n Information form\n \n \nOPTIONS:\n========\nSDECRPC\n \nRPCs:\n=====\nSDEC EDIT PAT PRE-REGISTRATION\nSDEC GETVVSMAKEINFO JSON\n VSE-183: - .NET: Patient Eligibility - Remediate 508 findings in Patient \nSDES GET STOPCD DETAIL\nSDES GET PATCH NUMBER\n Eligibility form\n VSE-264: - .NET Discovery: Special Needs/Preferences not updating\n VSE-294: - .NET Discovery: Null Reference Exception when using Trace Log \n Viewer Search\n\n
\nCorrections to Time zone computation and other fixes.\n\n
\nVSE-2396 VistA: Update SDES RPCs to change to ISO8601 Standard for \nVSE-2373 Discovery: Can incorrect disposition dates be identified and \n corrected. No development involved.\nVSE-1991 VistA: Create an RPC to Delete Appt from Patient File#2\nVSE-1992 VistA: Create an RPC to Update Appt from Patient File#2\nVSE-1993 VistA: Create an RPC to Create Appt in Patient File#2 \nVSE-1990 VistA: SDES RPC to read appointment entry in Patient file\nVSE-2387 VistA: VistA: Verify RPCs are assigned to the correct menu \n options\nVSE-2399 VistA: Create remote application entry\nVSE-2410 VistA: Add Preferred Name to Patient Info in VS GUI\n date/time\nVSE-2460 VistA: Add timestamp to SDES GET PATIENT REGISTRATION\nVSE-2482 VistA: Update SDES GET INSURANCE VERIFY REQ based on findings \n in VSE-2386\nVSE-2502 VistA: Add an array of all Divisions assigned to the ser and if \n no Divisions assigned it should return default DUZ(2) value.\n \nVSE-2540 VistA: Update SD44AUDI to increase max characters from 18 to 30 \n (3 fields)\nVSE-2576 Vista: Update SDES GET APPT BY CLINIC\nVSE-2574 Vista: New RPC SDES GET APPTS BY CLINIC LIST\nVSE-2500 VistA: Update SDES RPCs to change to ISO8601 Standard for \nVSE-2509 Vista: Timezone display\nVSE-2709 VistA: Refactor SDES GET INSURANCE VERIFY REG for shorter \n processing time\n \nROUTINES:\n---------\nSDEC50 - VSE-2391 VSE 2509\nSDEC01A - VSE 2509\nSDESAPPT - VSE 2574 and VSE 2576\nSDESAPPTREQ2,SDES,SDESJSON - VSE 1992 AND VSE 1993\n date/time\nSDESCANCELAPPT2,SDES,SDESJSON - VSE 1991\nSDECEPT - VSE-2406\nSDESCANCELAPPT44 - VSE-2396 \nSDESAPTREQ44 - VSE-2396\nSDAMUTDT - VSE-2442\nSDM1A - VSE-2372\nSDESGETPATAPPT - VSE-1990 \nSDESAPTREQSET - VSE-2396\nSDESARCLOSE - VSE-2396\nSDESUPDRECEQ - VSE-2396\nVSE-2442 VistA: Defect found in the function that converts ISO 8601 to \nSDESCLNSETAVAIL - VSE-2396 \nSDESCCAVAIL - VSE-2396\nSDEC809P - VSE-2399\nSDESGETUDDUZ,SDESGETUD - VSE-2502\nSDESARGET - VSE-2500\nSDESPATRPC - VSE-2482,VSE-2709\nSDEC09 - VSE-2460, 2410\nSDEC53 - VSE-2460\nSDESGETREGA -VSE-2460,VSE-2500\nSDESCLINICAVAIL - VSE-2500\n FileMan date/time\nSDESGETRECALL - VSE-2500\nSD44AUDI - VSE-2540 \nSDESJSON - VSE-2502,VSE-2500\n \nREMOTE PROCEDURE CALLS:\n------------------------\nSDES GET PAT APPT BY IEN #2\nSDES GET PAT APPTS BY DFN #2\nSDES CANCEL APPT #2 - VSE-1991\nSDES EDIT APPT #2 - CSE-1992\nVSE-2372 Vista: A defect was identified where the disposition date in \nSDES CREATE APPT #2 - VSE-1993\nSDES GET APPT #44 - vse-2414\nSDES CREATE APPT #44 - VSE-2396\nSDES CANCEL APPT #44 - VSE-2396\nSDES EDIT APPT #44 - VSE-2396\nSDES CREATE APPT REQ - VSE-2396\nSDES EDIT APPT REQ - VSE-2396 \nSDES DISPOSITION APPT REQ - VSE-2396\nSDES CREATE RECALL REQ - VSE-2396\nSDES EDIT RECALL REQ - VSE-2396\n File 409.85 is the date of the appointment when the\nSDES EDIT CLINIC AVAILABILITY - VSE-2396\nSDES CANCEL CLIN AVAILABILITY - VSE-2396 \nSDES GET APPT REQ BY IEN - VSE-2500 \nSDES GET APPT REQ BY PATIENT - VSE-2500\nSDEC GETREGA - VSE-2460\nSDES GET PATIENT REGISTRATION - VSE-2460\nSDES GET CLIN AVAILABILITY - VSE-2500\nSDES GET RECALL BY IEN - VSE-2500\nSDES GET RECALLS BY DFN - VSE-2500\nSDES GET USRPROFILE -VSE-2502\n appointment was made using the Scheduler in VistA (SDAM)\nSDES GET USER PROFILE BY DUZ - VSE-2502\nSDES GET PATCH NUMBER - VSE-2500 \nSDES GET APPTS BY CLINIC LIST\nSDES FAPPTGET - VSE-2391 VSE 2509\nSDES RESOURCE - VSE 2509\n \nOPTIONS:\n--------\nSDECRPC - VSE-2387\nSDESRPC - VSE-2387\n\n
\nRoutine SDHLAPT2 is corrected at label JSONTFM to orrectly translate JSON \nno one knows why it was used back in patch *714 and SDECAR2 has cahnged \nsince that time. TMP-1449 error reported by PrePod.\ndates to FileMan dates.\n \nAdded routines SDHL7APT & SDHL7APU for TMP-1449 PreProd reported null \nsubscript ien. Also call ARSET^SDECAR2 instead of ARSET^SDHLAPT1 (which \nwas an old copy at one time ofr SDECAR2. No one knows why the copy was \nused since patch *714.\nsubscript. Also use ARSET^SDECAR2 INSTFEAD OF AREST^SDHLAPT1, AN OLD COPY \nOF SDECAR2 copy that\n\n
\nVSE-2645 VistA: Update SDAMUTDT to return error on a bad date\nROUTINES:\n---------\nSDESRTVCLN - VSE 2612\nSDEC40 - 2610\nSDECEPT - 2610\nSDES - 2664\nSDAMUTDT - VSE-2645\nSDESAPPTEDIT - VSE-1899 \nSDES - VSE-1899,VSE-2621 \nSDEC51 - VSE-2606\nVSE-1899 VistA: Create routine and RPC to update appointment in 409.84 \nSDEC52 -VSE-2606\nSDECAR1 - VSE-2606\nSDECAR4 - VSE-2606\nSDEC52CRMVJSON - VSE-2606\nSDEC52CJSON - VSE-2606\nSDECCONSJSON - VSE-2606\nSDECAR1A - VSE-2606\nSDESPRINTPATAPPT - VSE-2621 (NEW ROUTINE)\nSDES, SDESJSON, SDESAPPTREQ40984 - VSE-1898\nSDESARGET - VSE-2606 \nVSE-1898 VistA: Create RPC to add an Appointment to file#409.84 \nSDESGETRECALL - VSE-2606\nSDESCCAVAIL - VSE-2645\nSDESCLINICSET2 - VSE-2769\n \nREMOTE PROCEDURE CALLS:\n------------------------\nSDES EDIT APPT #409.84 - VSE-1899\nSDES REQGET - VSE-2606\nSDEC RECGET - VSE-2606\nSDEC ARGET - VSE-2606\nVSE-2610 VistA: Add Time Zone Entry to Print Letter and Expand Entry\nSDEC GET PATIENT APPT BY REQ JSON - VSE-2606\nSDEC GET RECALLRMV BY DFN JSON - VSE-2606\nSDEC GET PATIENT RECALLS JSON - VSE-2606\nSDEC GET PATIENT CONSULT JSON - VSE-2606\nSDES PRINT PATIENT APPTS - VSE-2606\nSDES CREATE APPT #409.84 - VSE-1898\n \nOPTIONS:\n--------\nSDECRPC\nVSE-2612 VistA: Update SDES GET CLINIC INFO to return time zone\nVSE-2664 VistA: Add QUITS to SDES\nVSE-2769 VistA: Update SDEC RESOURCE file when a clinic is created using \n SDES namespace\n \n\n
\nThis patch corrects three problems: 1) Corrects the patient classification\nquestions in check-out to use the API calls to determine whether to ask\nor not, instead of hitting the patient file; 2) The comparison of PCE \nwith SD data during inpatient appoinment checkouts is skipped; 3) This\npatch also includes modifications to SCDXFU02-03 to prevent the creation\nof orphan entries in the Deleted Outpatient Encounter file.\n\n
\nVSE-2642 - VistA: Update the SDES routine to place $G around all input\nVSE-2705 - Vista: Eastern European Time Zone offset is not returning valid\n times\nVSE-2794 - VistA: Modify routine SDECDATE to correct offset validation\nVSE-2795 - VistA: Create a new RPC that accepts a list of patient DFNs \n and returns insurance indicators.\nVSE-2748 - VistA: Update SDES CREATE APPT #409.84 RPC\nVSE-2754 - VistA: Update SDES CREATE APPT #44\nVSE-2432 - VistA: Create wrapper RPC for adding an appointment\nVSE-2933 - VistA: Update SDEC EDIT PAT PRE-REGISTRATION RPC\n \n params\nROUTINES:\n=========\nSDES - VSE-2642;VSE-2433;VSE-2432\nSDEC1 - VSE-2726\nSDEC46 - VSE-2726\nSDEC07C - VSE-2587\nSDESBLKANDMOVE1 - VSE-2587\nSDESMISSIONELG, SDES, SDESJSON - VSE-2268\nSDESGETUD, SDESGETUDDUZ - VSE-2695\nSDESAPPTDATA - VSE-2433 (Modified)\nVSE-2648 - VistA: TMP change exposed error\nSDESGETAPPTWRAP - VSE-2433 (New)\nSDESUTIL - VSE-2705, VSE-2432\nSDECDATE - VSE-2794\nSDESPATRPC - VSE-2795\nSDUDC - VSE-2648\nSDESJSON - VSE-2432\nSDESCRTAPPTWRAP - VSE-2432\nSDESCREATEAPPT - VSE-2432;VSE-2748\nSDESCREATEAPPT44- VSE-2432;VSE-2754\nSDESCREATEAPPT2 - VSE-2432\nVSE-2726 - VistA: Support for UI change to display institution name on top\n \nOPTIONS:\n========\nSDECRPC - VSE-2726;2268\nSDESRPC - VSE-2268;VSE-2433\n \nREMOTE PROCEDURES:\n==================\nSDEC GET INSTITUTION - VSE-2726\nSDEC EDIT PAT PRE-REGISTRATION - VSE-2933\n banner\nSDES GET MISSION ACT ELIG - VSE-2268\nSDES GET APPTS BY PATIENT DFN - VSE-2433\nSDES GET APPTS BY CLIN IEN - VSE-2433\nSDES GET INSURANCE VERIFY LIST - VSE-2796\nSDES CREATE APPOINTMENTS - VSE-2432\nVSE-2695 - VistA: VistA: Update SDES GET USRPROFILE and SDES GET USER \n PROFILE BY DUZ RPCs Return Division Id\nVSE-2268 - VistA: Create RPC to calculate Mission Act Eligibility\nVSE-2433 - Vista: Create wrapper for viewing an appointment\n\n
\nVSE-1936: AP - VistA: Create SDES get consult request RPCs\n stop codes\nVSE-2850: RM - VistA: SDES Wrapper RPC to return a single appointment by\n IEN\nVSE-2851: BB - VistA: Update create appointment request RPC to use stop \n code number rather than IEN of stop code\nVSE-2852: KL - VistA: Add patient self-cancel disposition reason for \n appointment requests\nVSE-2853: KL - VistA: Create new field for patient comments in 409.85\nVSE-2860: MD - Disposition recall appointment returns empty set/string.\nVSE-2862: MD - Narrow down the parameter names for EAS tracking number.\nVSE-2687: KL- VistA: Code PSO Patch to support RX REFILL RPC Wrapper\nVSE-2881: MD - VistA: ApptReq: return the provider SecID.\nVSE-2882: MD - VistA: Appt: return the provider SecID \n \n \nFILES:\n======\nSDEC DISPOSITION REASON file (#409.853) - VSE-2852\nDELETE REASON field (#403.56,203) - VSE-2852\nCANCELLATION REASONS file (#409.2) - VSE-2781 \nPATIENT COMMENTS (#409.85,60) - VSE-2853 \nVSE-2781: KL - VistA: Add VEText Cancellation Reasons\nSDEC STOP CODE FILE (#409.89) - VSE-2843 \n \nROUTINES:\n=========\nSDEC52A - VSE-2852\nSDECAR - VSE-2781, VSE-2852\nSDECRECREQ - VSE-2781\nSDES - VSE-2821,VSE-2850 (Modified),VSE-2853,VSE-2804\nSDESARGET - VSE-2881\nSDESGETAPPTREQ - VSE-2881\nVSE-2799: BF- VistA: Create RPC to return appointment object when given \nSDESGETAPPTWRAP2 - VSE-2821,VSE-2850 (New)\nSDESGETAPPTWRAP3 -VSE-2821,VSE-2850 (New)\nSDESMISSIONELG - VSE-2843 (Modified)\nSDESGETCONSULTS - VSE-1936 (New)\nSDESAPTREQSET - VSE-2853\nSDESARCLOSE - VSE-2852, VSE-2853\nSDESDISPRECALL - VSE-2852\nSDESGETRECALL - VSE-2804\nSDESGETCONSULTS - VSE-2804\nSDESGETAPPTREQ - VSE-2804\n request IEN and appointment type\nSDESGETREQWRAPPR - VSE-2804\nSDESJSON - VSE-2804\nSDESAPTREQSET - VSE-2851\n \nRPCS:\n=====\nSDES CANCEL APPT - VSE-9\nSDES DISPOSITION RECALL REQ - VSE-6, VSE-9, VSE-2852\nSDES EDIT RECALL REQ - VSE-9\nSDES SET APPT CHECK-IN STEP - VSE-9\nVSE-2804: BB - VistA: SDES Wrapper RPC for getting appointment requests\nSDES GET APPTS BY CLIN IEN 2 - VSE-2821 (New)\nSDES GET APPTS BY PATIENT DFN2 - VSE-2821 (New)\nSDES GET APPTS BY IEN - VSE-2850 (New)\nSDES CREATE APPT REQ - VSE-2853\nSDES EDIT APPT REQ - VSE-2853\nSDES DISPOSITION APPT REQ - VSE-2852, VSE-2853 \nSDEC RECDSET - VSE-2852\nSDES GET RECALL BY IEN\nSDES GET RECALLS BY DFN\nSDES GET CONSULTS BY IEN\nVSE-2821: RM - VistA: Define combined appointment object and update SDES \nSDES GET CONSULTS BY DFN\nSDES GET APPT REQ BY IEN\nSDES GET APPT REQ BY PATIENT\nSDES GET APPT REQ LIST BY DFN\nSDES GET APPTS BY RESOURCE - VSE-2882 \nSDES GET APPTS BY PATIENT - VSE-2882\n \nOPTIONS:\n========\nSDESRPC - VSE-2821,VSE-2850,VSE-2804 (Modified)\n GET APPT wrapper RPC\nVSE-2843: AP - VistA: Create a file to contain Primary Care/Mental Health \n\n
\nVSE-2352: KL - Update SDEC APPADD to check for lock on Orders file. \n requirement.\nVSE-2996: BB - VistA: Add ORDER lock checks on SDES CREATE APPOINTMENTS.\n \n \nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-2900 \n \nRoutines:\n=========\nVSE-2859: MD - VistA: SDES GET CLIN AVAILABILITY Can this be converted to\nSDEC07 - VSE-2352\nSDEC07C - VSE-2352\nSDES2 - VSE-2913\nSDESCHECKINSTEP - VSE-2913\nSDESCLINICAVAIL - VSE-2859\nSDESCRTAPPTWRAP - VSE-2996\nSDESJSON - VSE-2900\nSDESPATRPC - VSE-2957\nSDESUTIL - VSE-2913\n \n a real JSON object structure.\nRPCs:\n=====\nSDES CANCEL APPT - REMOVE - VSE-2910\nSDES CANCEL APPT #2 - REMOVE - VSE-2910\nSDES CANCEL APPT #44 - REMOVE - VSE-2910\nSDES CREATE APPT #2 - REMOVE - VSE-2910\nSDES CREATE APPT #409.84 - REMOVE - VSE-2910\nSDES CREATE APPT #44 - REMOVE - VSE-2910\nSDES EDIT APPT #2 - REMOVE - VSE-2910\nSDES EDIT APPT #409.84 - REMOVE - VSE-2910\nVSE-2900: BF - VistA: Convert SDESJSON routine to store errors in file.\nSDES EDIT APPT #44 - REMOVE - VSE-2910\nSDES GET APPT #44 - REMOVE - VSE-2910\nSDES GET APPT CHECK-IN STEP 2 - VSE-2913\nSDES GET APPT CHECK-IN STEPS 2 - VSE-2913\nSDES GET CLIN AVAILABILITY - VSE-2859\n \nOptions:\n========\nSDESRPC - VSE-2910\nVSE-2910: LAB - VistA: Define and remove all SDES RPCs that should not be \n used\nVSE-2913: LAB - VistA: Create new RPCs to replace existing RPCs to use \n ISO 8601\nVSE 2957: AP - Update insurance SDES RPC to account for 365-day\n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*812.\n\n
\nVSE-2435: BB VistA: Create wrapper RPC to cancel an appointment\nVSE-2885: RM VistA: Modify SDES CREATE and EDIT APPT REQ RPC's to add a\n new input parameter 'secondary stop code'. Create a\n new field in File #409.85 that will capture the\n secondary stop code.\n Update SDES GET APPT REQ RPC's to include the\n secondary stop code into the JSON return array\nVSE-2922: MD VistA: SDES DISPOSITION APPT REQ Default to current user DUZ \n if one isn't provided\nVSE-2924: MD VistA ApptReq Return request disposition reason\nVSE-2956: BB VistA: Create patient date preference 1, date preference 2, \nVSE-2558: BF VistA: Create new RPC to retrieve all national flags and the \n date preference 3 fields\nVSE-2991: DS VistA: Update SDES GET USER PROFILE BY DUZ to return Station \n number for divisions\nVSE-3066: BF VistA: Implement solution for linking 409.84 to 403.56\nVSE-3095: BF VistA: Address sensitive patient functionality when using VS \nGUI\nVSE-3113: DR VistA: Add 2 RPCs to the SDESRPC Menu Option\nVSE-3118: DR VistA: Medical Center Division field to be required\nVSE-3157: RM VistA: Create a new JSON output utility.\nVSE-3159: LB VistA: Phoenix Time zone\n fugitive felon flag (SDES GET PATIENT FLAGS)\nVSE-3172: LB VistA: Update Mission Act Eligibility Calculation\n \n \nFiles:\n======\nREQ SECONDARY STOP CODE (409.85,8.6) - VSE-2885\nSDES ERROR CODES (409.93) - VSE-3172\n \nRoutines:\n=========\nVSE-2868: MD VistA: Error with clinic not having the appointment length \nSDES - VSE-2876,VSE-2435,VSE-2885\nSDESCLNSETAVAIL - VSE-2868\nSDESAPTREQSET - VSE-2876,VSE-2956,VSE-2885\nSDESGETAPPTREQ - VSE-2876,VSE-2885,VSE-2924\nSDESPATFLAGS\nSDESCANCELAPPTS - VSE-2435\nSDECVVS - VSE-3159\nSDESUTIL - VSE-3159\nSDESMISSIONELG - VSE-3172 \nSDESARCLOSE - VSE-2922\n field set\n \nRPCs:\n=====\nSDES CREATE APPT REQ - VSE-2876,VSE-2885\nSDES EDIT APPT REQ - VSE-2876,VSE-2885,VSE-2884\nSDES GET APPT REQ BY IEN - VSE-2876,VSE-2885,VSE-2924\nSDES GET APPT REQ BY PATIENT - VSE-2876,VSE-2885,VSE-2924,VSE-2884\nSDES GET APPTS BY PATIENT - VSE-3131\nSDES GET APPTS BY RESOURCE - VSE-3131\nSDES GET PATIENT FLAGS - VSE-2558\nVSE-2876: MD VistA: ApptReq: add new "station number" parameter when \nSDES CANCEL APPOITMENT - VSE-2435 \nSDES GET APPT REQ LIST BY DFN - VSE-2884,VSE-2885 \nSDES GET MISSION ACT ELIG - VSE-3172\nSDES GET APPT REQ BY PAT ALL - VSE-2884\nSDES GET APPT REQ BY PAT OPEN - VSE-2884\n \n \nOptions:\n========\nSDECRPC\n creating appointment requests\nSDESRPC - VSE-2884,VSE-3131\nVSE-2884: MD VistA: ApptReq update SDES GET APPT REQ RPCs to return \n ScheduledDateOfApptI in external format\n\n
\nVSE-2865: VistA - LB - SDES GET USRPROFILE missing security keys and menu \nVSE-3198: VistA - BF - Create a search RPC for Letter\nVSE-3199: VistA - KL - Create RPC to search for Provider\nVSE-3211: VistA - RM - Create a new RPC for privileged user search\nVSE-3212: VistA - BF - Create new RPC to get Division\nVSE-3231: VistA - BB - Rewrite SDES EDIT APPT REQ RPC\nVSE-3244: VistA - Unassigned - Create a new field for MRTC child \n appointment requests sequence number\nVSE-3245: VistA - Unassigned - Create a post install routine to correct \n MRTC child request sequence numbers\nVSE-3337: VistA: Add RPCs to the SDECRPC menu option.\n options\n============================\n \nFiles\n-----\nSDES ERROR CODES (#409.93) - VSE-3198, VSE-3212, VSE-3211, VSE-3127\n \nRoutines\n--------\nSDES - VSE-3155,VSE-2865\nSDES2 - VSE-3199, VSE-3212, VSE-3198\nVSE-2869: VistA - MD - Error Processing EAS Tracking Number\nSDESPROVSEARCH - VSE-3199\nSDEC07 - VSE-2869\nSDEC08 - VSE-2869\nSDESAPPT - VSE-2869\nSDESAPPTREQ40984 - VSE-2869\nSDESAPTREQSET - VSE-2869; VSE-3155\nSDESARCLOSE - VSE-2869\nSDESGETAPPTREQ - VSE-2869; VSE-3155\nSDESBLKANDMOVE - VSE-2869\nSDESCANCELAPPT - VSE-2869\nVSE-3127: VistA - AP - Fix slowness caused by large list of privileged \nSDESCCAVAIL - VSE-2869\nSDESCHECKINSTEP - VSE-2869\nSDESCKNSTEP - VSE-2869\nSDESDISPRECALL - VSE-2869\nSDESGETDIVISION - VSE-3212\nSDESGETLETTERS - VSE-3198\nSDESGETUD - VSE-2869\nSDESMISSIONELG - VSE-2869\nSDESARSETDESC - VSE-3155\nSDESINPUTVALUTL - VSE-3155 \n users for a restricted clinic\nSDESPRIVUSRSRCH - VSE-3211\nSDESLOC, SDES - VSE-3127\n \nRemote Procedures\n-----------------\nSDES SEARCH PROVIDERS - VSE-3199\nSDES CREATE APPT REQ - VSE-3155\nSDES EDIT APPT REQ - VSE-3155\nSDES GET APPT REQ BY IEN - VSE-3155\nSDES GET APPT REQ BY PATIENT - VSE-3155\nVSE-3155: VistA - RM - Create a new "modality" field in SDEC APPT REQUEST \nSDES GET APPT REQ LIST BY DFN - VSE-3155\nSDES GET APPT REQ BY PAT OPEN - VSE-3155\nSDES GET APPT REQ BY PAT ALL - VSE-3155\nSDES SEARCH PRIVILEGED USER - VSE-3211\nSDES ADD PRIV USER - VSE-3127\nSDES DELETE PRIV USER - VSE-3127\nSDES READ PRIV USERS - VSE-3127\nSDES DELETE PRIV USERS - VSE-3127\nSDES GET LETTER TYPE - VSE-3198\nSDES GET LETTERS BY TYPE - VSE-3198\n (#409.85) file.\nSDES GET LETTER BY IEN - VSE-3198\nSDES GET DIVISION LIST - VSE-3212\n \nOptions\n-------\nSDECRPC - VSE-3127, VSE-3337\nSDESRPC - VSE-3199, VSE-3211, VSE-3127, VSE-3198, VSE-3212\nVSE-3156: VistA - LB - Create a new "Appointment Site" field in SDEC \n APPOINTMENT (#409.84) file.\n\n
\nVSE-3454: BB - Change check on order lock in APPADD to look for a lock on \nVSE-3079: BF - VistA: Update appointment object to include appointment\n status logic\nVSE-3263: MD - VistA: Create a read RPC to return the Clinic Object \n including CHAR4 field from file #724.\nVSE-3275: RM - VistA: Create RPC that will create APPT request and then \n schedule the appointment (VAOS)\nVSE-3321: AP - VistA: Create a new RPC to check for overlapping \n appointments\nVSE-3326: MD - Vista Error Processing EAS Tracking Number\nVSE-3349: LB - VistA: Update description and return parameter for SDES \nthe order number instead of the patient. \n GET USRPROFILE\nVSE-3393: BF - VistA: Update SDES GET APPTS BY CLINIC LIST\n \nFiles:\n======\n409.85,43.1 - new field - MULT CHILD SEQUENCE NUMBER \n \nRoutines:\n=========\nSDEC07C - VSE-3454\nVSE-3245: BB - VistA: Correct MRTC child sequence issue\nSDECAR2 - VSE-3245\nSDESAPTREQSET - VSE-3245\nSDESGETREGA - VSE-3326\nSDESRTVCLN - VSE-3263\nSDESUTIL - VSE-3263\nSDESPATRPC - VSE-3326\nSDESCHKAPPTOVP, SDES2 - VSE-3321\nSDESAPTREQSET - VSE-3326\nSDESAPPT - VSE-3326\nSDESAPPTDATA - VSE-3079/3393\nVSE-3244: BB - VistA: Create a post install routine to correct MRTC child \nSDESARCLOSE - VSE-3326\nSDESBLKANDMOVE - VSE-3326\nSDESGETUD - VSE-3326\nSDESCANCELAPPTS - VSE-3326\nSDESCCAVAIL - VSE-3326 \nSDESCKNSTEP - VSE-3326\nSDESCLINICAVAIL - VSE-3326 \nSDESCLINICSET - VSE-3326\nSDESCLNSETAVAIL - VSE-3326\nSDESDISPRECALL - VSE-3326 \nrequest sequence numbers\nSDESGETAPPTWRAP2 - VSE-3326\nSDESGETCONSULTS - VSE-3326\nSDESGETRECALL - VSE-3326\nSDESGETREQWRAPPR - VSE-3326 \nSDESINACTCLINIC - VSE-3326\nSDESMISSIONELG - VSE-3326\nSDESUPDRECREQ - VSE-3326\nSDESPRINTPATAPPT - VSE-3326 \n \nRPCs:\nVSE-3250: FF - VS GUI: Update GUI logic to correct MRTC child request \n=====\nSDES GET USRPROFILE - VSE-3349\n \nOptions:\n========\nsequence numbers\nVSE-3334: BF - VistA: Create a Post-Install Routine to Clean Up VetLink \n Check-in Issue\n\n
\nVSE-3152: BB - VistA: Refactor SDES create appointment request RPC.\n 4 of SSN.\nSDES GET APPTS BY CLIN IEN 2 - VSE-3395 & VSE-3396\nSDES GET APPT BY REQ/APPT TYPE - VSE-3396\nSDES CREATE WALKIN APPT - VSE-3310\nSDEC CREATE WALKIN APPT JSON - VSE-3310\nSDES GET APPT BY REQ/APPT TYP2 - VSE-3484\nSDES GET APPTS BY IEN 2 - VSE-3484\nSDES GET APPTS BY CLIN IEN 3 - VSE-3484\nSDES GET APPTS BY PATIENT DFN3 - VSE-3484\nSDES GET PATIENT REGISTRATION2 - VSE-3322\nSDES GET APPTS BY CLINIC LIST - VSE-3322\nVSE-3385: AP - VistA: Update SDES GET CLIN INFO.\nSDES CREATE APPT REQ - VSE-3152\nSDES EDIT APPT REQ - VSE-3231\nSDES SEARCH RECALL CLINICS - VSE-3524\nSDES SEARCH RECALL PROVIDERS - VSE-3525\nSDES CREATE RECALL REQ 2 - VSE-3527\nSDES EDIT RECALL REQ 2 - VSE-3527\nSDES GET APPT REQ BY APPT IEN - VSE-3528, VSE-3564\nSDES GET APPT REQ BY IEN - VSE-3528, VSE-3564\nSDES GET APPT REQ BY PAT ALL - VSE-3528, VSE-3564\nSDES GET APPT REQ BY PAT OPEN - VSE-3528, VSE-3564\nVSE-3387: RM - VistA: Create a new RPC to reactivate a clinic.\nSDES GET APPT REQ BY PATIENT - VSE-3528, VSE-3564\nSDES GET ALL CLINIC HASHES - VSE-3306\nSDES GET CLINIC STORED HASH - VSE-3306\nSDES UPDATE CLINIC HASH - VSE-3306\nSDES GET CLIN AVAILABILITY - VSE-3389 \n \n \n \n \nOptions:\nVSE-3389: BF - VistA: Update SDES GET CLIN AVAILABILITY.\n========\nSDESRPC - VSE-3524,VSE-3525,VSE-3527,VSE-3534\nSDECRPC - VSE-3534\nVSE-3395: DS - VistA: Update SDES GET APPTS BY CLIN IEN 2.\nVSE-3396: MD - VistA: Update all appointment RPCs.\nVSE-3463: DS - VistA: VAR Filing Error.\nVSE-3484: RM - VistA: Modify SDES RPCs that return full SSN to only\n return last 4 of SSN.\nVSE-3496: BF - VistA: Establish connectivity from FORUM to IRIS Cloud.\nVSE-3231: BB - Rewrite SDES EDIT APPT REQ\nVSE-3524: MD - VistA: SDES Recall Clinic search RPC.\nVSE-3525: MD - VistA: SDES Recall Provider search RPC.\nVSE-3527: RM - VistA: Update SDES CREATE RECALL REQ and SDES EDIT RECALL \n REQ RPCs--bring to SDES standards\nVSE-3528: BB - VistA: Prerequisites--update SDES get appointment request \n routine to return.\nVSE-3564: MD - VistA: Modify SDES GET APPT REQ BY IEN\nVSE-3534: AP - VistA: Modify SDES GET CLINIC INFO\nVSE-3493: BF - VistA: Get List of Potential Appointment Statuses\nVSE-3672: LB - VistA: Fix the issue with MRTC being stuck in pending\nVSE-3275: RM - VistA: Create RPC that will create APPT request and then \n status\nVSE-3654: MD - VistA: Modify SDES GET APPT REQ BY IEN\n \n==========================================================================\n \nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-3387\nCANCELLATION REASON (#409.2) - VSE-3310\nHOSPITAL LOCATION (#44) fields 2900 and 2901 - VSE-3306 \n schedule the appointment (VAOS).\n \nRoutines:\n=========\nSDESGETAPPTWRAP3 - VSE-3395, VSE-3396, VSE-3484\nSDESUTIL - VSE-3395, VSE-3396\nSDESCLINICAVAIL - VSE-3389\nSDESCLINICDATA - VSE-3395, VSE-3396\nSDESREQAPPCREATE - VSE-3275\nSDESINPUTVALUTL - VSE-3275,VSE-3387,VSE-3484\nSDESAPPT3 - VSE-3484\nVSE-3306: LB - VistA: Create a hash on clinics in Hospital Locations file \nSDESGETAPPTWRAP4 - VSE-3484\nSDESGETAPPTWRAP5 - VSE-3484\nSDESAPPTDATA - VSE-3484\nSDESREACTVTCLIN - VSE-3387 \nSDESRTVCLN - VSE-3385\nSDEC09 - VSE-3322\nSDEC28 - VSE-3322\nSDEC28L - VSE-3322\nSDECEPT - VSE-3322\nSDECPTCX - VSE-3322\n #44\nSDECVVS - VSE-3322\nSDECU3 - VSE-3322\nSDESCRTWALKIN - VSE-3310\nSDESAPPT - VSE-3322\nSDESPATIENTDATA2 - VSE-3322\nSDESGETREGA - VSE-3322\nSDESGETREGA1 - VSE-3322 \nSDESCREATEAPPREQ - VSE 3152,VSE 3231\nSDESEDITAPPTREQ - VSE 3152,VSE 3231\nSDESCRTAPPTWRAP - VSE 3152,VSE 3231\nVSE-3310: LB - VistA: Create RPC for Walk-in Created Appointment Type to \nSDESCREATEAPPT - VSE 3152,VSE 3231\nSDESCREATEAPPT2 - VSE 3152,VSE 3231\nSDESCREATEAPPT44 - VSE 3152,VSE 3231 \nSDESRECCLINSRCH - VSE-3524\nSDESRECPROVSRCH - VSE-3525\nSDESUPDRECREQ2 - VSE-3527\nSDESGETAPPTREQ - VSE-3528, VSE-3564\nSDESHASHCLIN - VSE-3306\nSDESRTVCLN2 - VSE-3534\nSDES2 - VSE-3534\n Automatically Generate Appointment Request.\nSDECAR2 - VSE-3672\nSDESAPPT - VSE-3322\n \nRPCs:\n=====\nSDES CREATE VET REQ SCHED APPT - VSE-3275\nSDES REACTIVATE CLINIC - VSE-3387\nSDES GET CLINIC INFO - VSE-3385\nSDES GET CLINIC INFO2 - VSE-3534 \nSDEC GETREGA - VSE-3322\nVSE-3322: LB - VistA: Modify RPCs that return full SSN to only return last\nSDEC PTLOOKRS - VSE-3322\nSDEC GET PATIENT DEMOG - VSE-3322\nSDEC REQGET - VSE-3322\nSDECRMG RMG - VSE-3322\nSDEC ARGET - VSE-3322\nSDEC EP DEMOGRAPHICS - VSE-3322\nSDEC EP PT INFO - VSE-3322\nSDEC RECGET - VSE-3322\nSDES GET APPTS BY PATIENT DFN2 - VSE-3396\nSDES GET APPTS BY IEN - VSE-3396\n\n
\n \n \n \n==========================================================================\n \nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-3557, VSE-3388 \n \nRoutines:\n=========\nVSE-3388: BF - VistA: Update SDES CANCEL CLIN AVAILABILITY\nSDEC02 - VSE-3658\nSDESAPPT - VSE-3648\nSDESAPPT4 - VSE-3643\nSDESAPPT3 - VSE-3648\nSDESAPPTLETTERS - VSE-3388\nSDESCCAVAIL - VSE-3388\nSDESCCAVAIL2 - VSE-3388\nSDESCLINPRECAN - VSE-3388\nSDESGETAPPTREQ - VSE-3648\nSDESGETAPPTWRAP3 - VSE-3648\nVSE-3557: LB - VistA: Modify SDES EDIT CLINIC\nSDESGETAPPTWRAP5 - VSE-3648\nSDESGETCONSULTS - VSE-3648\nSDESGETRECALL - VSE-3648\nSDESGETREGA - VSE-3648\nSDESGETREG1 - VSE-3648\nSDESINPUTVALUTL - VSE-3648\nSDESPATIENTDATA2 - VSE-3648\nSDESPATRPC - VSE-3648\nSDESHASHCLIN - VSE-3675\nSDESCLINICSET - VSE-3557\nVSE-3643: DS - VistA: Modify SDES GET APPTS BY CLINIC LIST\nSDESUTIL - VSE-3680\nSDESCLNSEARCH - VSE-3680 \nSDES - VSE-3557 \nRPCs:\n=====\nSDEC CRSCHED - VSE-3658\nSDES CANCEL CLIN AVAILABILITY - VSE-3388\nSDES CANCEL CLIN PRECAN LIST - VSE-3388\nSDES GET APPT BY REQ/APPT TYP2 - VSE-3648\nSDES GET APPT REQ BY IEN - VSE-3648\nVSE-3648: RM - VistA: Add ICN variable everywhere DFN is returned\nSDES GET APPT REQ BY PAT ALL - VSE-3648\nSDES GET APPT REQ BY PAT OPEN - VSE-3648\nSDES GET APPT REQ BY PATIENT - VSE-3648\nSDES GET APPT REQ LIST BY DFN - VSE-3648\nSDES GET APPTS BY CLIN IEN 2 - VSE-3648\nSDES GET APPTS BY CLIN IEN 3 - VSE-3648\nSDES GET APPTS BY CLINIC LIST - VSE-3648\nSDES GET APPTS BY CLIN LIST2 - VSE-3643\nSDES GET APPTS BY IEN 2 - VSE-3648\nSDES GET APPTS BY PATIENT DFN2 - VSE-3648\nVSE-3658: MD - VistA: Retrieve appointment request type\nSDES GET APPTS BY PATIENT DFN3 - VSE-3648\nSDES GET APPTS BY RESOURCE - VSE-3648\nSDES GET CONSULTS BY DFN - VSE-3648\nSDES GET CONSULTS BY IEN - VSE-3648\nSDES GET INSURANCE VERIFY LIST - VSE-3648\nSDES GET PATIENT REGISTRATION - VSE-3648\nSDES GET PATIENT REGISTRATION2 - VSE-3648\nSDES GET RECALL BY IEN - VSE-3648\nSDES GET RECALLS BY DFN - VSE-3648\nSDES GET CLINIC STORED HASH - VSE-3675\nVSE-3675: LB - VistA: Modify OPTION: SDES HASH ALL CLINIC\nSDES EDIT CLINIC - VSE-3675 \nSDES PRINT APPT LETTER - VSE-3388\nSDES PRINT APPT LETTERS - VSE-3388\nSDES SEARCH CLINIC ATTRIBUTES - VSE-3680\n \nOptions:\n========\nSDESRPC - VSE-3680, VSE-3388, VSE-3643\nSDECRPC - VSE-3643\nVSE-3680: MD - VistA: Create a new RPC to return a small subset of clinic \n attributes\n\n
\nThis patch corrects a problem with the cancellation of the PCMM Patient\nw/Team Assignments report. See NPM for complete details.\n\n
\nVSE-2856 - RM - Vista: SDES GET APPT BY *: Requesting the addition of the \n Availability option (SDES)\nVSE-3768 - BF - INC23935053: <SUBSCRIPT>DOB+58^SDEC28L\nVSE-3738 - MD - VistA: Update SDES CREATE CLINIC and SDES EDIT CLINIC\nVSE-3757 - AP - VistA: SDES RPC to Create Clinic Group\nVSE-3759 - AP - VistA: SDES Search Clinic Group RPC\nVSE-3761 - DS - VistA: Update SDES DISPOSITION APPT REQ - Change Error \n Message Returned\nVSE-3762 - RM - VistA: Ensure FM datetime is not being appended to \n cancelled by clinic status\n \n division STATION NUMBER in the Appointment object.\nVSE-3790 - MD - VistA: Add 2 comment fields from file 409.85 to the JSON \n return\nVSE-3846 - BF - VistA: Fix null results in SDES CANCEL CLIN PRECAN LIST\nVSE-3847 - BF - VistA: Fix incorrect file number reference to master \n pattern (44.08).\n \nFiles:\n========\n409.93 - VSE-3584, VSE-3738, VSE-3704, VSE-3757, VSE-3759, VSE-3761\n \nVSE-3428 - DS - VistA: Add eCheck-in Allowed, Pre-Checkin Allowed, and\nOptions:\n=========\nSDESRPC\n \nRoutines:\n==========\nSDEC28L - VSE-3768\nSDES - VSE-3738\nSDESAPPTLETTERSV - VSE-3704\nSDESCLINICSET - VSE-3738\n time zone to SDEC RESCE\nSDESGETDEVICES - VSE-3704\nSDESUTIL - VSE-3738\nSDESGETAPPTREQ - VSE-3790\nSDES2 - VSE-3584,VSE-3634,VSE-3757,VSE-3759\nSDESCLNGRP - VSE-3759\nSDESADDGRP - VSE-3757\nSDESRTVCLN2 - VSE-3584,VSE-3634\nSDESCLINICDATA - VSE-2856\nSDESGETAPPTWRAP3 - VSE-3762\nSDESGETAPPTWRAP5 - VSE-3762\nVSE-3584 - LB - VistA: Modify SDES GET CLINIC INFO2 to trigger update to \nSDEC01C VSE-3428\nSDESARCLOSE - VSE-3761\nSDESCCAVAIL - VSE-3847\nSDESCLINPRECAN - VSE-3846\nSDESGETREQWRAPPR - VSE-3790\n \nRemote Procedure Calls:\n==================\nSDES GET CLINIC INFO2 - VSE-3584,VSE-3634\nSDES GET APPT BY IEN - VSE-2856,VSE-3762\n hash file\nSDES GET APPT BY REQ/APPT TYPE - VSE-2856,VSE-3762\nSDES GET APPT BY REQ/APPT TYP2 - VSE-2856,VSE-3762\nSDES GET APPTS BY CLIN IEN - VSE-2856,VSE-3762\nSDES GET APPTS BY CLIN IEN 2 - VSE-2856,VSE-3762\nSDES GET APPTS BY CLIN IEN 3 - VSE-2856,VSE-3762\nSDES GET APPTS BY CLINIC LIST - VSE-2856,VSE-3762\nSDES GET APPTS BY CLINIC - VSE-2856,VSE-3762\nSDES GET APPTS BY IEN - VSE-2856,VSE-3762\nSDES GET APPTS BY IEN 2 - VSE-2856,VSE-3762\nSDES GET APPTS BY PATIENT - VSE-2856,VSE-3762\nVSE-3634 - LB - VistA: Modify SDES GET CLINIC INFO2\nSDES GET APPTS BY PATIEN DFN - VSE-2856,VSE-3762\nSDES GET APPTS BY PATIENT DFN2 - VSE-2856,VSE-3762\nSDES GET APPTS BY PATIENT DFN3 - VSE-2856,VSE-3762\nSDES GET APPTS BY RESOURCE - VSE-2856,VSE-3762\nSDES GET VISTA DEVICES - VSE-3704\nSDES CREATE CLINIC - VSE-3738\nSDES EDIT CLINIC - VSE-3738\nSDES GET APPT REQ BY IEN - VSE-3790\nSDES GET APPT REQ BY PAT ALL - VSE-3790\nSDES GET APPT REQ BY PAT OPEN - VSE-3790\nVSE-3669 - BB - VistA: Convert SDEC Appointment Slots to SDES\nSDES GET APPT REQ BY PATIENT - VSE-3790\nSDES GET APPT REQ LIST BY DFN - VSE-3790\nSDES PRINT APPT LETTER VISTA - VSE-3704\nSDES PRINT APPT LETTERS VISTA - VSE-3704\nSDES SEARCH CLINIC GRP - VSE-3759\nSDES ADDEDIT CLINIC GRP - VSE-3757\nSDEC RESCE - VSE-3428\nSDES CANCEL CLIN PRECAN LIST - VSE-3846\nVSE-3704 - BF - VistA: Add VistA print capability to the Cancel Clinic \n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*817.\n\n
\n \nVSE-3852 - BF - VistA: Create a SDES RPC to Check-Out an appointment\nVSE-3856 - AP - VistA: Create a SDES RPC to remove a clinic group\nVSE-3861 - DS - VistA: Create post install routine to cleanup check-ins in\n VPS\nVSE-3871 - MD - VistA: Modify SDES GET CLIN AVAILABILITY to return an \n empty data element\nVSE-3874 - AP - VistA: Defect SDES ADDEDIT CLINIC GROUP RPC - Incorrect \n length of Name\nVSE-3962 - MD - VistA: Modify SDES GET CLIN AVAILABILITY to accept dates\n in the past\nVSE-3767 - MD - VistA: Update SDES CREATE APPT REQ to accept a 409.1 \nVSE-4066 - MD - VistA: Update SDES CREATE APPT REQ to add AMIS Primary and\n Secondary stop codes\nVSE-4181 - LB - VistA: Modify SDEC GET APPT REQ BY IEN JSON to return \n patient comments.\nVSE-4007 - AP - Please modify SDES GET MISSION ACT ELIG to include the \n "VETERAN" appointment request type as a possible input.\nVSE-4283 - LB - Modify RPC to add required input parameter "CLINIC", and \n modify routine to no longer pull CLINIC from requests.\n \n \n APPOINTMENT TYPE Name\nFiles:\n=====\nSDES ERROR CODES (#409.93) - VSE-3767\n \nOptions:\n========\nSDESRPC - VSE-3852\n \nRoutines:\n=========\nVSE-3787 - MD - VistA: Modify RPCs to return an empty data element rather \nSDECAR4 - VSE-4181\nSDES2 - VSE-3848, VSE-3849, VSE-3850, VSE-3856\nSDESCLINICAVAIL - VSE-3781\nSDESCREATEAPPREQ - VSE-3767 ,VSE-4066\nSDESCREATEAPPT - VSE-3767\nSDESCREATEAPPT2 - VSE-3767\nSDESCRTAPPTWRAP - VSE-3767\nSDESEDITAPPTREQ - VSE-3767\nSDESEDITAPPTREQ2 - VSE-3767\nSDESREQAPPCREATE - VSE-3767\n than an error\nSDESPRIVUSRSRCH - VSE-3787\nSDESPROVSEARCH - VSE-3787\nSDESADDRG - VSE-3856,VSE-3874\nSDESRTNRG - VSE-3849\nSDESADDDELCGI - VSE-3848; VSE-3850 \nSDESCHECKOUT - VSE-3852\nSDESVALUTIL - VSE-3852\nSDES - VSE-4283\nSDESMISSIONELG - VSE-4007,VSE-4283 \n \nVSE-3848 - AP - VistA: Create SDES RPC to add clinic to clinic group\nRemote Procedure Calls:\n=======================\nSDES CREATE APPT REQ - VSE-3767\nSDES EDIT APPT REQ - VSE-3767\nSDES CREATE VET REQ SCHED APPT - VSE-3767\nSDES GET CLIN AVAILABILITY - VSE-3962\nSDES ADD CLNGRP ITEM\nSDES DELETE CLNGRP ITEM\nSDES DELETE CLINIC GROUP\nSDES READ CLINIC GROUP\nVSE-3849 - AP - VistA: Create a SDES RPC to read a single clinic group\nSDES CHECKOUT\nSDES GET MISSION ACT ELIG - VSE-4007,VSE-4283\nVSE-3850 - AP - VistA: Create a SDES RPC to remove a clinic from a clinic \n group\n\n
\nVSE-2857 - AP - VistA: The Appointment object does not contain a field \nVSE-3881 - AP - VistA:Modify SDEC RECPRGET and SDES SEARCH RECALL \n PROVIDERS\nVSE-3935 - RM - VistA: Update contact attempt RPCs to account for\n "VETERAN" appointment requests\nVSE-3937 - DS - VistA: Modify SDES CREATE APPOINTMENTS to schedule in the\n past\nVSE-3964 - MD - VistA: Add hash to SDES CREATE CLINIC\nVSE-3972 - AP - VistA:Mission Act Discovery\nVSE-3998 - RM - VistA: RPC for Mobile to use that returns Clinic Name and \n Clinic ID\n linking to a video visit appointment\nVSE-4004 - MD - VistA: Modify SDES GET CLIN AVAILABILITY\nVSE-4014 - BF - VistA: Fix error <UNDEFINED>GET1+6^SDEC52\nVSE-4044 - BB - Add local/national flags, registration date, sensitive \n record, and insurance verification to GET APPTS BY CLINIC\n LIST\nVSE-4061 - AP - VistA:Modify SDES GET APPTS BY CLIN IEN 3 to return\n check-in entered date\nVSE-4286 - LB - VistA: Modify SDEC GET PATIENT APPT REQ JSON to return \n Contact Attempts\n \nVSE-2883 - BB - Copy PATIENT COMMENTS from appt request into new PATIENT \nFiles:\n=====\n409.93 - VSE-3851;VSE-3998;VSE-3853\n409.84,6 - VSE-2883 \n \nOptions:\n========\nSDESRPC - VSE-3851;VSE-3853\n \n \n COMMENTS field in 409.84 upon generating a new appointment\nRoutines:\n=========\nSDESCRTAPPTWRAP - VSE-2883\nSDESPATIENTDATA2 - VSE-4044\nSDESCLINICSET2 - VSE-3964\nSDESRTVCLN2 - VSE-3964\nSDECCON - VSE-3935\nSDECAR1A - VSE-3935,VSE-4286\nSDESGETTIUDOC - VSE-3998\nSDESCLINICAVAIL - VSE-4004\n (SDES).\nSDESCHECKIN - VSE-3851 \nSDESCANCHECKIN - VSE-3853\nSDESCHECKOUT - VSE-3852\nSDESAPPTDATA - VSE-4061, VSE-2857\nSDEC52 - VSE-4014\nSDEC52B,SDESRECPROVSRCH - VSE-3881 \nSDESCREATEAPPT,SDESCREATEAPPT2,SDESCREATEAPPT44 - VSE-3937\nSDESINPUTVALUTL - VSE-3998\n \n \nVSE-3851 - LB - VistA: Create a SDES RPC to Check-in for an appointment\nRemote Procedure Calls:\n=======================\nSDES GET CLIN AVAILABILITY - VSE-4004\nSDES GET TIU DOC BY CONTEXT\nSDES CHECKIN - VSE-3851\nSDES CANCEL CHECKIN - VSE-3853\nSDES GET APPTS BY IEN2 - VSE2857\nSDES GET APPT BY REQ/APPT TYP2 - VSE2857\nVSE-3852 - BF - VistA: Create a SDES RPC to Check-Out an appointment\nVSE-3853 - BF - VistA: Create a SDES RPC to undo Check-In for an\n appointment\n\n
\n1) TMP-1479: Add CHAR4 to Telehealth Management Toolbox - Clinic \n2) TMP-1546: Improve the default appointment length\n3) TMP-1750: Add Stop Codes 497 and 498\n4) TMP-1734: Appointment Availability\n5) TMP-1720: Waiting For Response Vista Integration error\n6) TMP-1487: Add DEA Info. to the Medical Center Division Inquiry \n7) TMP-1770: The Facility Exp. Date displays in FileMan format\n8) TMP-1709: Add VistA Clinic Special Instructions to the Clinic Inquiry\n\n
\nThis patch will address two issues: \n \n 1. Staff search results in Patient Centered Management Module \n (PCMM) Web do not include all staff members.\n \n 2. <UNDEFINED>AFTERTP+9^SCMCDD1 *SCTMAF error in error trap at multiple\n VistA sites.\n\n
\nVSE-3539: AP - VistA: Create a new version of SDES GET APPT BY CLIN LIST2\nVSE-4144: DS - VistA: Modify SDES GET CLINIC AVAILABILITY\nVSE-4145: MD - VistA: Retire RPCs post release of SD*5.3*815 and \n SD*5.3*816\nVSE-4154: DS - VistA: Create VVS RPCs in the SDES menu option\nVSE-4217: AP - VistA: Modify SDES GET CLINIC INFO 2 to return privileged \n user list\nVSE-4220: MD - VistA: Update Clinic Hash to include privileged users list\nVSE-4268: DR - VistA: Add SDBUILD key to VistA\n \n \nVSE-3594: LB - VistA: Create a new RPC to replace SDES GET APPTS BY IEN 2]\nFiles:\n=====\n409.93 - VSE-3750,VSE-4142\n44 - VSE-4141 \n \nOptions:\n========\nSDESRPC - VSE-4142,VSE-3594,VSE-3539\nSDECRPC - VSE-3594\n \nVSE-3596: DS - VistA: Modify SDES GET APPT REQ BY IEN\nRoutines:\n=========\nSDESCLINICSET2 - VSE-3750\nSDESINPUTVALUTL - VSE-3750\nSDESHASHCLIN - VSE-4220 \nSDESCLINICDATA - VSE-3636\nSDESCLINICAVAIL - VSE-4144\nSDESGETAPPTREQ - VSE-3596\nSDESCREATEAPPT - VSE-3622\nSDESCANCELAPPTS - VSE-3622\nVSE-3622: BB - VistA: Modify SDES CANCEL APPOINTMENT RPC\nSDESCRTAPPTWRAP - VSE-3622\nSDESRTVCLN2 - VSE-4217\nSDESAPPT4 - VSE-3539 \nSDESPRVSRCHJSON - VSE-4154\nSDESVVC - VSE-4154\nSDESVVS - VSE-4154\nSDESVVSJSON - VSE-4154\n \nRemote Procedure Calls:\n=======================\nVSE-3636: CP - VistA: Modify SDES GET APPTS BY IEN\nSDES GET APPTS BY CLIN IEN - VSE-4145\nSDES GET APPTS BY PATIENT DFN - VSE-4145\nSDES GET APPT BY IEN - VSE-4145\nSDES GET APPTS BY IEN - VSE-4145\nSDES GET APPTS BY PATIENT - VSE-4145\nSDES GET APPTS BY CLINIC - VSE-4145\nSDES GET PAT APPT BY IEN #2 - VSE-4145\nSDES GET PAT APPTS BY DFN #2 - VSE-4145\nSDES GET APPT CHECK-IN STEP - VSE-4145\nSDES GET APPT CHECK-IN STEPS - VSE-4145\nVSE-3750: RM - VistA: Modify SDES EDIT CLINIC\nSDES SEARCH VVS PROVIDERS - VSE-4154\nSDES SEARCH VVS PROVIDERS JSON- VSE-4154\nSDES SPACEBAR VVS PRO - VSE-4154\nSDES VVS SAVE ID - VSE-4154\nSDES VVS GET ID - VSE-4154\nSDES VVS DELETE ID - VSE-4154\nSDES VVC APPT - VSE-4154 \nSDES GETVVSMAKEINFO - VSE-4154\nSDES GETVVSMAKEINFO JSON - VSE-4154\nSDES GET APPTS BY CLINIEN LIST- VSE-3539 (NEW)\nVSE-4141: DR - VistA: Create new field in file #44 IsPBSP Clinic (bool)\nSDES GET CLINIC INFO2 - VSE-4217\nSDES PCESAVE - VSE-4142 (NEW)\nSDES GET APPT BY APPT IEN - VSE-3594 (NEW)\n \nSecurity Keys:\n==============\nSDBUILD - VSE-4268\nVSE-4142: BF - VistA: Implement a copy of VIABPCE SAVE RPC as an \n SDES* RPC.\n\n
\nVSE-3017: BF - VistA: Add clinic time zone field to appointment object\nVSE-4299: LB - VistA: Create a tool to clean up stuck order\nVSE-4588: LB - VistA: Modify SDES EDITAPPT to send an error that \n appointment length cannot be edited.\nVSE-4480: AP - VistA: Modify SDES GET CLIN AVAILABILITY to return an \n error when clinic institution does not have a timezone set\nVSE-4477: AP - Create an SDES version of SDEC CANCMT to return national \n and local cancellation comments\nVSE-4449: BB - Add service connected percentage to SDES GET APPT REQ BY \n RPCS.\nVSE-3854: BB - Rewrite SDES UNDO CHECKOUT.\nVSE-4118: DS - VistA: Modify SDES GET PATIENT FLAGS to add local flags\n \n \n \nFiles:\n=====\n409.93 - VSE-4152,VSE-4477\n \nOptions:\n========\nSDESRPC\nVSE-4148: AP - VistA: Write SDES RPCs for profile service gaps\nSDSUP - VSE-4299\nSDES STUCK ORDER CLEANUP - VSE-4299\n \nRoutines:\n=========\nSDCODEL - VSE-4149,VSE-4150\nSDESCLINICDATA - VSE-3017\nSDESCLINICSET - VSE-4152\nSDESNOSHOW - VSE-4149,VSE-4150 \nSDESGETPRFGAPS - VSE4148\nVSE-4149: BF - VistA: Create SDES RPC to mark appt as No Show\nSDES2 - VSE4148, VSE4477\nSDESUTIL - VSE-4152,VSE-4480\nSDEC26 - VSE-4558\nSDESCLINICAVAIL - VSE-4480\nSDESGETCANCMT - VSE-4477\nSDESPATFLAGS - VSE-4118\nSDESGETAPPTREQ - VSE-4449\nSDESGETREQWRAPPR - VSE-4449\nSDESUNDOCHECKOUT - VSE-3854\nSDESGETCLINSIEN - VSE-4267\nVSE-4150: BF - VistA: Create SDES RPC to Undo No Show\nSDESORDCLEAN - VSE-4299\n \nRemote Procedure Calls:\n=======================\nSDES NOSHOW - VSE-4149 \nSDES UNDO NOSHOW - VSE-4150\nSDES GET PATIENT PREF - VSE-4148\nSDES GET PATIENT WARD - VSE-4148\nSDES EDITAPPT - VSE-4558\nSDES GET CANCMTS - VSE-4477\nVSE-4152: MD - VistA: Modify RPCs that utilize stop codes to put AMIS\nSDES GET PATIENT FLAGS - VSE-4118\nSDES GET APPT BY REQ/APPT TYP2 - VSE-3017\nSDES GET APPTS BY CLIN IEN 3 - VSE-3017\nSDES GET APPTS BY CLIN LIST2 - VSE-3017\nSDES GET APPTS BY IEN 2 - VSE-3017\nSDES GET APPTS BY PATIENT DFN3 - VSE-3017\nSDES GET APPTS BY RESOURCE - VSE-3017\n logic into a tag\nVSE-4267: CP - VistA: Create an SDES RPC to batch retrieve clinic\n information\n\n
\nFixes several problems with the 'Visit Report by Transmitted Outpatient\nEncounter'. See NPM for complete description.\n\n
\n \nVSE-4622: BB - VistA: RPC to return "VETERAN" type APPT requests\nVSE-4671: BB - VistA: Create Check for Contact Type\nVSE-4598: BB - VistA: Correct error in SDES CREATE APPT REQ when setting\n priority to FUTURE\nVSE-4700: LB - VistA: Correct issue with SDES EDIT CLINIC AVAILABILITY \n \nFiles:\n======\nSDEC APPT REQUEST - VSE-4622\nSDES ERROR FILE - 409.93 \nVSE-2404: BB - VistA: Create SDES RPC to Search Patient\n \n \nOptions:\n========\nSDECRPC - VSE-2404, VSE-4156, VSE-4525\nSDESRPC - VSE-2404, VSE-4156, VSE-4525\n \nRoutines:\n=========\nSDESRTVCLN2 - VSE-4556, VSE-4592\nVSE-4156: DS - VistA: Retire RPCs post release of SD*5.3*823\nSDESVVC - VSE-4525\nSDESVVS - VSE-4525\nSDESGETAPPTREQ - VSE-4622, VSE-4671\nSDESCREATEAPPREQ - VSE-4598\nSDECAR - VSE-4605\nSDECAR4 - VSE-4605\nSDESPATSEARCH - VSE-2404\nSDESCLNSETAVAIL - VSE-4700\n \nRemote Procedure Calls:\nVSE-4525: AP - VistA: Modify SDES VVS RPCs to return JSON output\n=======================\nSDES CREATE CLIN AVAILABILITY - VSE-4700\nSDES CREATE RECALL REQ - VSE-4156\nSDES DELETE VVS ID - VSE-4525\nSDES EDIT CLINIC AVAILABILITY - VSE-4700\nSDES EDIT RECALL REQ - VSE-4156 \nSDES GET APPT BY REQ/APPT TYPE - VSE-4156\nSDES GET APPT REQ BY TYPE VET\nSDES GET APPTS BY CLIN IEN 2 - VSE-4156 \nSDES GET CLINIC INFO - VSE-4156 \nVSE-4556: JS - VistA: Modify SDES GET CLINIC INFO2 and SDES GET CLINICS \nSDES GET CLINIC INFO2 - VSE-4556, VSE-4592\nSDES GET CLINICS BY CLIN LIST - VSE-4556, VSE-4592\nSDES GET PATIENT REGISTRATION - VSE-4156\nSDES GET VVS APPT - VSE-4525\nSDES GET VVS ID - VSE-4525 \nSDES PATIENT SEARCH - VSE-2404\nSDES SAVE VVS ID - VSE-4525 \nSDES SPACEBAR VVS PRO - VSE-4525\nSDES VVC APPT - VSE-4525 \nSDES VVS DELETE ID - VSE-4525\n BY CLIN LIST to include #4 INSTITUTION field 802\nSDES VVS GET ID - VSE-4525 \nSDES VVS SAVE ID - VSE-4525 \nVSE-4592: JS - VistA: Modify SDES GET CLINIC INFO2 to include IEN and \n stop code\nVSE-4605: BB - VistA: Return MRTC sequence number to GUI\n\n
\nVSE-4155: BF - VistA: Rewrite Contact Attempts RPC's in the SDES menu \nVSE-4695: AP - VistA: Create a new RPC to fetch open appointment requests\nVSE-4699: BB - Modify SDES GET APPT REQ BY TYPE VET\nVSE-4737: LB - Revise MISSION Act Eligibility Logic for Availability \n \nFiles:\n======\n409.93 - VSE-4695,VSE-4691 \n409.86 - VSE-4155\n \nOptions:\n option\n========\nSDECRPC - VSE-4313,VSE-4622\nSDESRPC - VSE-4691, VSE-4699\n \nRoutines:\n=========\nSDESGETAREQINST- VSE-4695\nSDESMISSIONELG - VSE-4737\nSDESCANCELAPPTS - VSE-4155\nSDESCLINICSET - VSE-4691\nVSE-4313: CP - VistA: Create RPC for Service/Specialty Mental Health Stop \nSDESCONSULTUPD - VSE-4155\nSDESCONTACTS - VSE-4155\nSDESCREATEAPPREQ - VSE-4155\nSDESGETMHCODE - VSE-4313\nSDESNOSHOW - VSE-4155\nSDESRECALLREQ - VSE-4155\nSDESVALUTIL - VSE-4691 \nSDECAR4 - VSE-4622\n \n \n Codes\nRemote Procedure Calls:\n=======================\nSDES GET APPTREQ BY INST - VSE-4695\nSDES CONTACT ADD/UPDATE - VSE-4155\nSDES CONTACT DISPLAY - VSE-4155\nSDEC RETURN MENTAL HEALTHJSON - VSE-4313\nSDEC GET REQ BY TYPE VETERAN - 4622\nVSE-4622: BB - SDEC RPC to return the first 200 appointment requests with \n a type of vet.\nVSE-4691: BF - VistA: Modify SDES EDIT CLINIC AVAILABILITY to not allow\n start and end times to be changed if existing appointments will\n be affected\n\n
\n \n require the SD SUPERVISOR key\nVSE-4711: AP - VistA: Rewrite SDEC CLINSTOP in the SDES namespace\nVSE-4723: JS - VistA: Rewrite SDEC CANREAS in the SDES menu option\nVSE-4735: BF - VistA: Rewrite SDECCAP GET in SDES namespace\nVSE-4736: BF - VistA: Rewrite SDECCAP SET in the SDES namespace\nVSE-4779: LB - VistA: Modify SDES SEARCH RECALL CLINICS\nVSE-4855: LB - VistA: When viewing list of VETERAN Requests and there are \n none GUI is returning an error\nVSE-4874: LB - VistA: Update SDES GET APPTS BY CLIN LIST2 and SDES GET\n APPTS BY CLINIEN LIST\nVSE-4159: CP - VistA: Retire RPCs post release of SD*5.3*824\nVSE-4907: LB - VistA: Modify SDES CREATE CLINIC and SDES EDIT CLINIC to \n specify the telephone extension\nVSE-4908: LB - VistA: Modify SDES GET CLINIC INFO2 to return clinic phone \n extension\n \nFiles:\n======\nSDES ERROR CODES (409.93)\n \nOptions:\nVSE-4162: BB - VistA: Display original clinic availability once some or \n=========\nSDECRPC - VSE-4159\nSDESRPC - VSE-4159, VSE-4711, VSE-4735, VSE-4736 \nSDBUILD - VSE-4559 \n \nRoutines:\n==========\nSDES - VSE-4907\nSDESCAR4 - VSE-4855\nSDESCHECKOUT - VSE-4706\n all availability is consumed\nSDESCLINICSET - VSE-4907\nSDESCOMPPEN - VSE-4735, VSE-4736 (new)\nSDESUNDOCHECKOUT - VSE-4706\nSDESSEARCHRCLN - VSE-4779 (new) \nSDESCANCELRSNS - VSE-4723 (new)\nSDESUTIL - VSE-4701\nSDESCLINDAILYSCH - VSE-4162\nSDESGETSTOPCD - VSE-4711\nSDESAPPT4 - VSE-4874\nSDESRTVCLN2 - VSE-4908 \nVSE-4559: DR - VistA: Lock down the VistA menu options with the new \n \nRemote Procedure Calls:\n========================\nSDES CREATE CLINIC - VSE-4907 (Modified)\nSDES EDIT CLINIC - VSE-4907 (Modified)\nSDES GET CLINIC INFO2 - VSE-4908 (Modified)\nSDES GET CLINIC ORIGINAL AVAIL - VSE-4162\nSDES GET APPTS BY CLINIC LIST - VSE-4159\nSDES GET APPTS BY PATIENT DFN2 - VSE-4159\nSDES SEARCH RECALL CLINICS - VSE-4779 (modified)\n SDBUILD key\nSDES GET CANCEL REASONS - VSE-4723 (new)\nSDES GET CLINIC STOPCD - VSE-4711(new)\nSDES GET COMP/PEN 2507 - VSE-4735(new)\nSDES SET COMP/PEN AMIE TRKNG - VSE-4736(new)\nSDES GET APPTS BY CLIN LIST2 - VSE-4874\nSDES GET APPTS BY CLINIEN LIST - VSE-4874\nVSE-4701: DS - VistA: Modify SDES SEARCH CLINIC to add additional fields \n in return\nVSE-4706: CP - VistA: Modify SDES CHECKOUT and SDES UNDO CHECKOUT to not\n\n
\n \n check for lock on the order.\nVSE-4734: BF - VistA: Rewrite SDECCAP CAN in the SDES menu option\nVSE-4782: AP - VistA: Add 3 missing cancellation related fields to SDES\n GET APPTS BY IEN2\nVSE-4815: AP - VistA: Modify SDES GET APPT * to return WALKIN flag\nVSE-4816: BF - VistA: Contact Attempts do not work with Recalls\nVSE-4818: MD - VistA: Modify SDES CREATE APPT REQ\nVSE-4833: JS - VistA: Rewrite routine SDES01C to standards\nVSE-4860: BF - VistA: Modify SDES GET APPT REQ * and SDES GET RECALLS* \n RPCs\n \nVSE-4869: DR - VistA: Remove Scheduling Manager from the Links in SDEC \n settings\nVSE-4903: BB - VistA: Create a new RPC to return all clinics for which \n the new person name is a PROVIDER.\nVSE-4937: BB - VistA: Modify SDES GET CANCMTS to return both national and \n local comments.\nVSE-4949: LB - VistA: Modify SDES CREATE APPT REQ RPC and SDES CREATE \n APPOINTMENT to correct saving child MRTC requests\n \nFiles:\n \n======\nSDES ERROR CODES (#409.93)\n \nOptions:\n========\nSDESRPC - VSE-4903, VSE-4907\n \nRoutines:\n=========\nSDEC57 - VSE-2644\nVSE Increment 4.7 - SD*5.3*837 - GUI v 1.7.39\nSDECAR - VSE-4589\nSDEC07C - VSE-4589\nSDESAPPTDATA -VSE4815, VSE-4782 \nSDES01C - VSE-4833\nSDESEDITAPPTREQ - VSE-4949\nSDESCREATEAPPREQ - VSE-4818 \nSDESCOMPPEN - VSE-4734\nSDESCANCELAPPTS - VSE-4734\nSDESCONTACTS - VSE-4860\nSDESGETAPPTREQ - VSE-4860\n=============================================\nSDESGETCONSULTS - VSE-4860\nSDESGETRECALL - VSE-4860\nSDESGETALLCANCOM - VSE-4937\nSDESPROVCLINSRCH - VSE-4903 \n \nRemote Procedure Call:\n======================\nSDEC ARCLOSE - VSE-4589\nSDES GET ALL CANCEL COMMENTS - VSE-4937\nSDES GET APPTS BY CLIN IEN 3 - VSE 4815, VSE 4782\n \nSDES GET APPTS BY CLIN LIST2 - VSE 4815\nSDES GET APPTS BY CLINIEN LIST - VSE 4815, VSE 4782\nSDES GET APPTS BY IEN 2 - VSE 4815, VSE 4782\nSDES GET APPTS BY PATIENT DFN3 - VSE 4815, VSE 4782\nSDES GET CLINICS BY PROVIDER - VSE-4903\nVSE-2644: BB - VistA: SDEC APPSLOTS creates availability where none has\n been defined.\nVSE-4589: LB - VistA: Any time VS GUI sends hl7 to update order, first\n\n
\nVSE Increment 4.8 - SD*5.3*838\n type and IEN for each entry\nVSE-4902: MD - VistA: Update SDES SAVE VVS ID RPC to save IEN and VVS ID \n to only that appointment\nVSE-4928: LB - VistA: Add Service Connected indicator and eligibility to \n appointment object in the SDES RPCs\nVSE-4932: CP - VistA: Create a new SDES RPC to get appointments for a \n list of IENs as input\nVSE-4933: JS - VistA: Create a new RPC to get appointment requests for a \n list of IENs as input\nVSE-4938: DS - VistA: New version of SDES Cancellation RPC\n==============================\nVSE-5042: BB - VistA: Modify SDES GET APPT REQ BY * RPCs to return the \n current status field from 409.85.\nVSE-5044: BB - VistA: Modify SDES PATIENT SEARCH RPC to return the Date \n of Death.\n \nFiles:\n======\n409.93 - VSE-4902 \n \nOptions:\n \n========\nSDESRPC - VSE-4873 \n \n \nRoutines:\n=========\nSDESAPPTDATA - VSE-4928\nSDESVVS - VSE-4902\nSDESGETAPPTWRAP5 - VSE-4928\nSDESGETCLINAPPT - VSE-4928\nJira Tickets:\nSDESGETREQSIEN - VSE-4933 \nSDESMISSIONAVL - VSE-4873\nSDESUTIL - VSE-4933\nSDESGETAPPTSIEN - VSE 4932\nSDESCANAPPT2 - VSE-4938\nSDESRTNRG - VSE-4901 \nSDESGETCLNSCHEDS - VSE-4861\nSDESGETAPPTREQ - VSE-5042\nSDESGETREQWRAPPR - VSE-5042\nSDESPATSEARCH - VSE-5044 \n=============\n \nRemote Procedure Call:\n======================\nSDES SAVE VVS ID - VSE-4902 (Modified)\nSDES GET APPT BY APPT IEN - VSE-4928 (Modified)\nSDES GET APPT BY REQ/APPT TYP2 - VSE-4928 (Modified)\nSDES GET APPTS BY CLIN IEN 3 - VSE-4928 (Modified)\nSDES GET APPTS BY CLIN LIST2 - VSE-4928 (Modified)\nSDES GET APPTS BY CLINIEN LIST - VSE-4928 (Modified) \nSDES GET APPTS BY PATIENT DFN3 - VSE-4928 (Modified)\nVSE-4861: BB - VistA: Create a new SDES RPC to retrieve schedule for \nSDES GET APPTS BY IENS - VSE-4932 (New)\nSDES CANCEL APPOINTMENT 2 - VSE-4938 (New)\nSDES READ CLINIC GROUP - VSE-4901 (Modified)\nSDES GET APPT REQ BY IEN - VSE-5042 (Modified)\nSDES GET APPT REQ BY PATIENT - VSE-5042 (Modified)\nSDES GET APPT REQ BY PAT ALL - VSE-5042 (Modified)\nSDES GET APPT REQ BY PAT OPEN - VSE-5042 (Modified)\nSDES GET APPT REQ BY TYPE VET - VSE-5042 (Modified)\nSDES PATIENT SEARCH - VSE-5044 (Modified)\nSDES GET MISSION ACT AVAIL - VSE-4873 (New)\n multiple clinics\nSDES GET AVAIL BY CLIN LIST - VSE-4861 (New)\nSDES GET APPT REQS BY IENS - VSE-4933 (New)\nVSE-4873: BF - VistA: Create a new RPC for expanded Mission Act\nVSE-4901: AP - VistA: Modify SDES READ CLINIC GROUP to return resource \n\n
\nVSE Increment 4.9 - SD*5.3*840 - Mid Year Stop Codes\n======\n \n \nOptions:\n========\n \n \nRoutines:\n=========\n \n====================================================\n \nRemote Procedure Call:\n======================\n \nJira Tickets:\n=============\nVSE-4298: DR - VistA: FY 23 Mid-Year Stop Code Changes\n \n \nFiles:\n\n
\nVSE Increment 4.8 - SD*5.3*839\n in ISO 8601 format\n \n \nFiles:\n======\n \n \nOptions:\n========\n \n==============================\n \n \nRoutines:\n=========\nSDES2 - VSE-5011\nSDESAPPTDATA - VSE-4875\nSDESCOMPPEN - VSE-5013\nSDESGETAPPTREQ - VSE-5011\nSDESGETAPPTREQ2 - VSE-5011 \n \n \nRemote Procedure Call:\n======================\nSDES GET APPT REQ BY PAT ALL - VSE-5011\nSDES GET COMP/PEN 2507 - VSE-5013\nJira Tickets:\n=============\nVSE-4875: DS - VistA: Modify SDESGETAPPTWRAP3\nVSE-5011: CP - VistA: Modify SDES GET APPT REQ BY PAT ALL to accept a date\n range for Appt Req Create Date\nVSE-5013: BF - VistA: Modify SDES GET COMP/PEN 2507 to format all dates \n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*848.\n\n
\nVSE Increment 4.9 - SD*5.3*842 - VS GUI 1.7.40.0\n to return additional fields\nSDES EDIT RECALL REQ 2 - VSE-5037\nSDES GET CONSULTS BY DFN - VSE-4924\nSDES GET CONSULTS BY IEN - VSE-4924\nSDES CREATE APPOINTMENTS - VSE-5073\nSDES CREATE CLIN AVAILABILITY - VSE-5164\nSDES EDIT CLINIC AVAILABILITY - VSE-5164\nVSE-4956: BB - Create a new RPC in the SDES namespace to return a boolean\n indicating demographics needs update\nVSE-5016: LB - Modify SDES CANCEL APPOINTMENT 2 to remove appointment IEN\n from MRTC APPT MADE sub-file\nVSE-5026: BF - Modify SDES GET APPT REQ LIST BY DFN, SDES GET RECALLS\n BY DFN, and SDES GET RECALL BY IEN to return recall reminder\n appt type\nVSE-5037: AP - Modify SDES CREATE RECALL REQ 2 to accept the recall \n reminder type name\n================================================\nVSE-5043: MD - Please create a new Appointment Request Disposition Reason,\n post install routine, and update the code to not reopen the \n request\nVSE-5073: DS - Modify SDES CREATE APPOINTMENTS to make the SDEC RESOURCE\n parameter optional\nVSE-5103: BB - Create SDES GET APPT TYPES RPC for SAS team\nVSE-5105: BB - Create a new SDES GET SPEC NEEDS AND PREFS RPC for the SAS\n team\nVSE-5106: BB - Create a new SDES GET CONSULT DETAILS RPC for the SAS team\nVSE-5107: BB - Create a new SDES GET PATIENT INQUIRY RPC for the SAS team\n \nVSE-5144: DR - Create a new field in 409.84 called MISSION ACT ELIGIBLE\nVSE-5145: BF - Make a copy of SDES GET MISSION ACT ELIG and rename one\n copy for EAS\nVSE-5146: BF - Modify SDES GET MISSION ACT ELIG to return if an \n appointment is Mission Act Eligible across multiple clinics with\n the same stop code\nVSE-5148: BF - Modify APPADD to set the new field in 409.84 to Y if \n appointment is Mission Act Eligible\nVSE-5164: LB - VistA - Modify SDES EDIT CLINIC AVAILABILITY to not require\n times and slots\nJira Tickets:\nVSE-5197: BF - VistA: Modify SDES GET MISSION ACT ELIG to not display \n availability pop up when both PID and target appointment are\n within WTS\nVSE-5216: LB - Create post-install routine to report pending appointments\n and requests that have different patient DFN.\nVSE-5260: BF - VistA: Modify SDES GET MISSION ACT ELIG RPC.\nVSE-5263: BF - VistA: Create new RPC to return MISSION Act Eligibility for\n Block&Move for Recalls\nVSE-5337: BB - VistA: Need to address <UNDEFINED>H+1^SDEC57\nVSE-5338: MD - VistA: GETIEN^SDEC51 - to prevent leaking of the X and Y \n=============\n variables.\n \n \nFiles:\n======\nSDEC APPOINTMENT (#409.84) - VSE-5144\nSDEC DISPOSITION REASON (#409.853) - VSE-5088\nSDES ERROR CODES (#409.93) - VSE-5146,5263\n \nOptions:\nVSE-4498: CP - Retire SDES GET APPTS BY IEN 2 post release patch 828\n========\nSDESRPC - VSE 4498,5103,5105,5106,5107,5145,5263\nSDECRPC - VSE 4498,5263 \n \nRoutines:\n=========\nSDESGETRECALL - VSE-4923, VSE-5026\nSDESGETREQWRAPPR - VSE-4923, VSE-5026\nSDESMISSIONELG - VSE-5146, VSE-5197, VSE-5260, VSE-5263\nSDEC07 - VSE-5148\nVSE-4923: JS - Modify SDES GET RECALLS BY DFN, SDES GET RECALL BY IEN, and\nSDESGETAVAILSC - VSE-5145 \nSDESUPDRECREQ2 - VSE-5037\nSDEC08 - VSE-5043\nSDESCANCELAPPTS - VSE-5016, VSE-5043\nSDESCANAPPT2 - VSE-5016, VSE-5043 \nSDESGETAPPTTYPE - VSE-5103\nSDESGETCONDETAIL - VSE-5106\nSDESGETPATINQUIR - VSE-5107\nSDESPATSEARCH - VSE-4956\nSDESNEEDSPREFS - VSE-5105 \n SDES GET APPT REQ LIST BY DFN to return additional fields\nSDESGETCONSULTS - VSE-4924 \nSDESCLNSETAVAIL - VSE-5164\nSDEC57 - VSE-5337\nSDEC51 - VSE-5338\n \nRemote Procedure Call:\n======================\nSDES GET APPT REQ LIST BY DFN - VSE-4923, VSE-5026\nSDES GET RECALL BY IEN - VSE-4923, VSE-5026\nSDES GET RECALLS BY DFN - VSE-4923, VSE-5026\nVSE-4924: CP - Modify SDES GET CONSULTS BY DFN and SDES GET CONSULT BY IEN\nSDES GET APPT REQS BY IENS - (updated Ret Desc - no story)\nSDES GET AVAIL BY STOP CODE - VSE-5145\nSDES GET MISSION ACT ELIG - VSE-5146, VSE-5260\nSDES GET MISSION ACT ELIG FEDT - VSE-5263\nSDES GET PATIENT INQUIRY - VSE-5107\nSDES PATIENT SEARCH - VSE-4956\nSDES GET CONSULT DETAILS - VSE-5106\nSDES GET APPT TYPES - VSE-5103\nSDES GET SPEC NEEDS AND PREFS - VSE-5105\nSDES CREATE RECALL REQ 2 - VSE-5037\n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*832.\n\n
\nRefer to National Patch Module\n\n
\nVSE Increment 8.3 - SD_5_3_852\nSDES852P - VSE-5544\n \nJira Tickets:\n=============\nVSE-5544: BF - VistA: Correct cancelled consult data and produce report \n of corrected data\n \nRoutines:\n=========\n\n
\nVSE Increment 4.10 - SD*5.3*843 - VS GUI 1.7.41.0\nVSE-5038: BF - VistA: Modify SDBUILD to not allow a user to delete clinic \n availability if there are existing appointments\n *** SD*5.3*843 v4 - Deployed to revert to a Pre-843 status. ***\nVSE-5100: JS - VistA: Close open requests for deceased veterans\nVSE-5109: MD - VistA: Modify SDES CREATE VET SCHED APPT to set the request\n institution to the clinic institution\nVSE-5160: JS - I-0001568 VistA Option for Open Veteran Requests\nVSE-5163: BB - VistA: Modify SDES CREATE APPOINTMENTS to set the Mission\n Act Eligible flag \nVSE-5170: AP - VistA: Update SDES GET PATIENT FLAGS to return only flags \n=================================================\n in active status\nVSE-5180: BB - VistA: Modify SDES PATIENT SEARCH RPC to return Local, \n National, and Sensitive Patient flags\nVSE-5189: LB - VistA: Modify SDES EDIT CLINIC AVAILABILITY to return an\n error if the user does not enter a date\nVSE-5281: JS - VistA: Add EAS Tracking Number to the appointment request \n object for consults\nVSE-5282: BF - VistA: Modify SDES GET MISSION ACT ELIG RPC to point to \n SDESMISSIONELG\nVSE-5249: LB - RTC order in CPRS has been discontinued by Provider and \n \n the RTC remains in VSE\nVSE-5339: LB - VistA: VetText & TMP: Check the Validation of the \n Appointment Request\nVSE-5451: LB - VistA: Block & Move of Recall Appointment returns invalid \n appointment type\nVSE-5455: LB - VistA: VistA: Create a post install routine to report on \n Block & Move appointments or RECALL type\n \nFiles:\n======\nJira Tickets:\nSDES ERROR CODES - VSE-4496 \n \nOptions:\n========\nSDEC DECEASED RECORD CLEANUP - (new) - VSE-5100\nSDEC DECEASED RECORD MENU - (new) - VSE-5100\nSDEC DECEASED RECORD REPORT - (new) - VSE-5100 \nSDES OPEN VET REQUESTS RPT - (new) - VSE-5160\nSDSUP - (modified) - VSE-5100\nSDMGR - (modified) - VSE-5160\n============= \n \nRoutines:\n=========\nSDB1 - VSE-5038\nSDEC07 - VSE-5249,VSE-5339\nSDECAR - VSE-5249\nSDESBLKANDMOVE - VSE-5451\nSDESCLNSETAVAIL - VSE-5189 \nSDESCREATEAPPREQ - VSE-5109\nSDESREQAPPCREATE - VSE-5109\nVSE-4496: AP - VistA: Modify SDES CREATE APPOINTMENTS to not allow\nSDESCRTAPPTWRAP - VSE-4961,VSE-5163\nSDESPATSEARCH - VSE-5180\nSDECDTHCLNUP2 - VSE-5100 \nSDESOPENVETREQS - VSE-5160\nSDESCREATEAPPT - VSE-4496\nSDESPATFLAGS - VSE-5170 \nSDESGETREQWRAPPR - VSE-5281\nSDES843P - VSE-5455\n \n \n creation of appointment from a dispositioned appointment request\nRemote Procedure Call:\n======================\nSDES GET PATIENT FLAGS - VSE-5170\nSDES GET MISSION ACT ELIG - VSE-5282\nSDES PATIENT SEARCH - VSE-5180\nVSE-4961: BB - VistA: Remove the lock on Clinics when trying to schedule \n appointments\n\n
\nVSE Increment 4.11 - SD_5_3_844 - GUI v 1.7.42\nVSE-5177: BF - VistA: Create SDES GET RESOURCE BY CLINIC to return 409.831\n SDEC RESOURCE entry for the HOSPITAL LOCATION\nVSE-5178: BF - VistA: Create SDES GET RESOURCE BY DUZ to return 409.831\n SDEC RESOURCE entry for the NEW PERSON\nVSE-5238: BB - VistA: Modify SDES PATIENT SEARCH RPC to accept patient\n name with 1 or 2 characters\nVSE-5243: BB - VistA: Modify SDES GET PATIENT FLAGS and SDES PATIENT\n SEARCH to Return Additional Fields\nVSE-5252: DS - VistA: Recalls (PtCSch) are not showing up in VISTA once\n they've been dispositioned\nVSE Increment 8.1 - SD_5_3_844 - GUI v 1.7.42\nVSE-5255: AP - VistA: Return additional clinic data for SDES GET APPTS* \n RPCs\nVSE-5280: TB - VistA: Changes to SDEC APPSDGET\nVSE-5283: JS - VistA: Modify SDES CREATE APPT REQ\nVSE-5287: BF - VistA: Ensure input variables are protected when calling \n into SDES GET MISSION ACT ELIG\nVSE-5329: BF - VistA: Create a new RPC to retrieve the entries in the \n holiday file\nVSE-5340: DS - VistA: Create Cancelled by clinic appointment reason that \n does not reopen the appointment request\n==============================================\nVSE-5483: BF - VistA: Correct error <PARAMETER>REQSET^SDESCONSULTUPD \nVSE-5608: BF - VistA: Modify SDES CANCEL APPOINTMENT2 RPC to temporarily \n use the SDEC logic\n \n \nFiles:\n======\nCANCELLATION REASONS (#409.2) - VSE-5340 \n \nOptions:\n \n========\nSDESRPC - VSE-5177 ,VSE-5178, VSE-5025, VSE-5329\nSDECRPC - VSE-5025 \n \nRoutines:\n=========\nSDESGETRESOURCE - VSE-5177,VSE-5178 \nSDESPATSEARCH - VSE-5238,VSE-5243\nSDESPATFLAGS - VSE-5243\nSDRRINQ - VSE-5252\nJira Tickets:\nSDES844P - VSE-5101\nSDESCHECKLOCK - VSE-5025\nSDESCREATEAPPREQ - VSE-5283\nSDEC55A - VSE-5280 \nSDESCLINICDATA - VSE-5255\nSDESHOLIDAY - VSE-5329\nSDESMISSIONELG - VSE-5287\nSDESCANAPPT2 - VSE-5483,VSE-5608\nSDESCANCELAPPTS - VSE-5483\n \n=============\nRemote Procedure Call:\n======================\nSDES GET RESOURCE BY DUZ - VSE-5178\nSDES GET RESOURCE BY CLINIC - VSE-5177\nSDES PATIENT SEARCH - VSE-5238,VSE-5243\nSDES GET PATIENT FLAGS - VSE-5243\nSDES CHECK ORDER LOCK - VSE-5025\nSDES CREATE APPT REQ - VSE-5283\nSDES GET APPTS BY PATIENT DFN3 - VSE-5255\nSDES GET APPTS BY IENS - VSE-5255\nVSE-5025: LB - VistA: Issues with Block and Move and Drag and Drop with\nSDES GET APPTS BY CLIN LIST2 - VSE-5255\nSDES GET APPTS BY CLINIEN LIST - VSE-5255\nSDES GET APPT BY APPT IEN - VSE-5255\nSDES GET HOLIDAYS - VSE-5329\n locking.\nVSE-5101: TB - VistA: Close appointment requests for stop code 669\n\n
\nVSE Increment 8.2 - SD_5_3_845 - GUI v 1.7.43\n REQ* RPCs\nVSE-5264: JS - VistA: Modify SDES SEARCH RECALL PROVIDERS to add the \n #403.54 IEN to the return\nVSE-5324: BF - VistA: Modify/New Version SDES CONTACT ADD/UPDATE to not \n require a Clinic\nVSE-5375: JS - VistA: Modify CANCELLATION REASONS file to add SYSTEM USE \n ONLY field\nVSE-5396: TB - VistA: Issue with SDES EDIT APPT REQ\nVSE-5431: BB - VistA: Update SDES GET MISSION ACT ELIG to not return \n error message if PID is outside the WTS\n \nVSE-5432: BB - VistA: Create SDES RPC for Creating Special Needs and \n Preferences\nVSE-5433: BB - VistA: Create RPC for Editing Special Needs and \n Preferences\nVSE-5656: BF - When SDES CANCEL APPOINTMENT RPC is called, Parent MRTC \n request is Closed and does not return to RM Grid.\n \nFiles:\n======\nCANCELLATION REASONS (#409.2) - VSE-5375\nJira Tickets:\nSDES ERROR CODES (#409.93) - VSE-5432,VSE-5433 \n \n \nOptions:\n========\nSDESRPC - VSE-5111,VSE-5324\n \n \nRoutines:\n=========\n=============\nSDESRECPROVSRCH - VSE-5264\nSDEC45 - VSE-5375\nSDESCANAPPT2 - VSE-5656\nSDESCANCELRSNS - VSE-5375 \nSDESEDITAPPTREQ - VSE-5396\nSDESCONTACTS - VSE-5324\nSCRPW3 - VSE-5162\nSDESGETAPPTREQ - VSE-5256\nSDESGETRECALL - VSE-5256\nSDESGREQSIENS - VSE-5111\nVSE-5111: AP - VistA: Modify SDES GET APPT REQS BY IENS to normalize \nSDESEDITNEEDPREF - VSE-5433\nSDESCRTNEEDPREFS - VSE-5432\nSDESMISSIONELG - VSE-5431\nSDESUTIL - VSE-5432,VSE-5433 \n \nRemote Procedure Call:\n======================\nSDEC CANREAS - VSE-5375\nSDES GET CANCEL REASONS - VSE-5375\nSDES DISPLAY CONTACT - VSE-5324\n responses\nSDES ADD/UPDATE CONTACT - VSE-5324\nSDES GET APPT REQ BY PAT ALL - VSE-5256\nSDES GET APPT REQ BY PAT OPEN - VSE-5256\nSDES GET APPT REQ BY IEN - VSE-5256\nSDES GET APPT REQS BY IENS2 - VSE-5256, VSE-5111\nSDES GET APPT REQ BY TYPE VET - VSE-5256 \nSDES GET APPT REQ LIST BY DFN - VSE-5256\nSDES GET RECALL BY IEN - VSE-5256\nSDES GET RECALLS BY DFN - VSE-5256\nSDES CREATE SPEC NEEDS PREFS - VSE-5432\nVSE-5162: BF - VistA: Modify SCRPW3 routine to use an additional variable \nSDES EDIT SPEC NEEDS PREFS - VSE-5433\nSDES SEARCH RECALL PROVIDERS - VSE-5264\n when searching the patient file, appointment sub-file\nVSE-5256: AP - VistA: Return additional clinic data for SDES GET APPT \n\n
\n \nVSE-5435: BB - VistA: Create SDES RPC to Return Last Selected Patient by \n User\nVSE-5436: MD - VistA: SDES EDIT CLINIC Not Updating Privileged Users\nVSE-5437: MD - VistA: Clinic Privileged Users not DINUMed correctly\nVSE-5463: BF - VistA: Modify SDES EDIT APPT REQ to resolve issues with \n PRIORITY, REQUESTED BY, COMMENTS, and Appt Request Type\nVSE-5495: LB - VistA: Create a tool to clean up appointments attached to \n an incorrect request\n \n \nVSE Increment 8.3 - SD_5_3_846 - GUI v 1.7.44\n============================================= \nVSE Increment 8.4 - SD_5_3_846 - GUI v 1.7.44\n \nJira Tickets:\n=============\nVSE-5062: DR - VistA: Retire RPCs 90 days post release of patch 838\nVSE-5248: TB - VistA: Modify SDES GET DIVISION LIST or create a new RPC\nVSE-5424: DS - VistA: Modify SDES CREATE WALKIN APPT\nVSE-5532: AP - VistA: Update SDEC EP DEMOGRAPHICS to return "patient \n comments" field (4) from 409.84\n \nVSE-5534: AP - VistA: Return patient entered comments from 409.84 field 4 \n in the appointment object\nVSE-5571: BB - VistA: Rewrite SDEC EDITAPPT in the SDES Namespace\nVSE-5573: JS - VistA: Modify Mission Act WTS calculation from T+19 and \n T+27to then equal 20/28 days\nVSE-5592: TB - VistA: Create a new SDES RPC to return the 409.853 SDEC \n DISPOSITION REASONS\nVSE-5603: JS - VistA: Modify SDES PATIENT SEARCH to Return Additional \n Fields\nVSE-5640: BF - VistA - Write a post install routine to clean up encounters\nJira Tickets:\n left open after Appointment was closed\nVSE-5643: BB - VistA: Modify SDES PATIENT SEARCH RPC to find patients \n when first name included with 2 character last name\nVSE-5664: MD - VistA: Modify patch 842 post install routine to address\n issue with SD*5.3*627 not being installed\n \nFiles:\n======\nSDES ERROR CODES - VSE-5463,VSE-5424\n \n=============\nOptions:\n========\nSDESRPC - VSE-5592,VSE-5532,VSE-5062\n \nRoutines:\n=========\nSDESCREATEAPPREQ - VSE-5385 (Modified)\nSDESCLINICSET2 - VSE-5436\nSDESGETAPPTSIEN2 - VSE-5370 \nSDES846P - VSE-5437, VSE-5664, VSE-5495, VSE-5640\nVSE-5370: DS - VistA: Modify SDES GET APPTS BY IENS to normalize response\nSDESSTOREPATIENT - VSE-5434\nSDESGETSTOREDPAT - VSE-5435\nSDESEDITAPPTREQ - VSE-5463\nSDESPATSEARCH - VSE-5603/VSE-5643 (Modified)\nSDESCRTWALKIN - VSE-5424\nSDESCREATEAPPT - VSE-5424\nSDESGETDIVISION - VSE-5248 (Modified)\nSDESGETDISPREASN - VSE-5592 (New)\nSDESMISSIONELG - VSE-5573 (Modified)\nSDESAPPTDATA - VSE-5534 (Modified)\nVSE-5385: JS - VistA: Modify SDES CREATE APPT REQ to validate Provider IEN\nSDECEPT - VSE-5532 (Modified)\nSDESPATCMMTS - VSE-5532 (New)\nSDESEDITAPPT - VSE-5571\nSDES846PENC - VSE-5640 (New)\n \nRemote Procedure Call:\n======================\nSDES GET APPTS BY IENS VSE-5534 (Modified)\nSDES GET LAST SELECTED PAT - VSE - 5435 (NEW)\nSDES EDIT APPOINTMENT - VSE - 5571 (NEW)\nVSE-5434: BB - VistA: Create SDES RPC to Store Last Selected Patient by \nSDES PATIENT SEARCH - VSE-5603/VSE-5643 (Modified)\nSDES CREATE WALKIN APPT - VSE-5424 (Modified)\nSDES GET DIVISION LIST - VSE-5248 (Modified)\nSDES GET DISPOSITION REASONS - VSE-5592 (New)\nSDES GET APPT BY APPT IEN - VSE-5534 (Modified)\nSDES GET APPT BY REQ/APPT TYP2 - VSE-5534 (Modified) \nSDES GET APPTS BY CLIN IEN 3 - VSE-5534 (Modified)\nSDES GET APPTS BY CLIN LIST2 - VSE-5534 (Modified)\nSDES GET APPTS BY CLINIEN LIST - VSE-5534 (Modified)\nSDES GET APPTS BY IENS2 - VSE-5370,VSE-5534 (New)\n User\nSDES GET APPTS BY PATIENT DFN3 - VSE-5534 (Modified)\nSDES GET APPTS BY RESOURCE - VSE-5534 (Modified)\nSDES GET PATIENT CMMTS - VSE-5532 (New)\nSDEC EP DEMOGRAPHICS - VSE-5532 (Modified)\nSDES CREATE LAST SELECTED PAT - VSE-5435 (New)\nSDES CANCEL APPOINTMENT - VSE-5062 (Deleted)\n\n
\nVSE Increment 8.5 - SD*5.3*847 - No VS GUI\n appointment\nVSE-5609: VistA - BB - Correct SDES CANCEL APPOINTMENT2 RPC to update all \n data elements in the SDEC APPDEL RPC\nVSE-5623: TB - VistA - Modify SDES CREATE APPOINTMENT to remove the array \n field 20\nVSE-5732: BB - VistA - Changes to PIDDATE added to SDEC need to be added \n to SDES\nVSE-5740: LB - VistA - Correct SdecContactNumber calculations\n \n \n==========================================\nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-5549,VSE-5609,VSE-5732\n \nOptions:\n========\n \n \nRoutines:\n=========\n \nSDEC07 - VSE-5549\nSDESGETAPPTREQ - VSE-5740\nSDESGETAPPTREQ2 - VSE-5740 \nSDESGETREQWRAPPR - VSE-5740\nSDESGREQSIENS - VSE-5740\nSDESCANAPPT2 - VSE-5609/VSE-5732\nSDESRECALLREQ - VSE-5732\nSDESCREATEAPPT - VSE-5732/VSE-5549\nSDESCREATEAPPREQ - VSE-5732\nSDESCRTAPPTWRAP - VSE-5732/VSE-5623\nJira Tickets:\nSDESNOSHOW - VSE-5732\nSDESGETAPPTREQ - VSE-5732\nSDESGETCONSULTS - VSE-5732\nSDESCLINICDATA - VSE-5569\nSDESAPPTDATA - VSE-5515\nSDESGETPATAPPT - VSE-5515\nSDESEDITAPPTREQ - VSE-5623\n \nRemote Procedure Call:\n======================\n=============\nSDES GET APPTS BY PATIENT DFN3 - VSE-5515, VSE-5569\nSDES GET APPTS BY RESOURCE - VSE-5515, VSE-5569\nSDES GET APPT BY APPT IEN - VSE-5515, VSE-5569\nSDES GET APPTS BY IENS - VSE-5515, VSE-5569\nSDES GET APPTS BY IENS2 - VSE-5515, VSE-5569\nSDES GET APPTS BY CLIN IEN - VSE-5515, VSE-5569\nSDES GET APPTS BY CLIN LIST2 - VSE-5515, VSE-5569\nSDES GET APPTS BY CLINIEN LIST - VSE-5515, VSE-5569\nSDES CREATE APPOINTMENTS - VSE-5623\nSDES CANCEL APPOINTMENTS 2 - VSE-5732\nVSE-5515: AP - VistA - Modify SDES GET APPT * RPCs to pull the\n CurrentStatus from 409.84\nVSE-5549: TB - VistA - Modify SDEC APPADD and SDES CREATE APPOINTMENTS \n RPCs to ensure pt on request matches the patient on the\n\n
\nEMERGENCY BUILD TO STOP MRTC REQUESTS TO BE RETURNED TO TMP\n\n
\nVSE Increment 8.6 - SD_5_3_851 - GUI v 1.7.45\nVSE-5792: AP - VistA: Modify SDES GET PATIENT REGISTRATION2 to return \n eligibility codes\n \n \nVSE Increment 8.7 - SD_5_3_851 - GUI v 1.7.45\n=============================================\nVSE-5565: TB - VistA: Modify SDES GET APPT REQ RPCs to return PID CHANGE \n ALLOWED (#49) field value\nVSE-5670: BF - VistA: Modify SDES SEARCH CLINIC ATTRIBUTES to return \n clinic abbreviation and array of provider names\n=============================================\nVSE-5736: TB - Update SDES SEARCH CLINIC to return correct Resource Status\nVSE-5775: AP - VistA: Modify VistA open Veteran requests report to remove\n Patient Comments column\nVSE-5818: BB - VistA: Update the slot logic within SDES CANCEL \n APPOINTMENT 2 and SDES CREATE APPOINTMENTS RPCs\nVSE-5896: JS - VistA: SDES GET APPTS BY PATIENT DFN3 is giving errors\nVSE-5941: BF - VistA: Contact attempts are being returned for incorrect \n appointment request\n \n \n \nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-5670, VSE-5819\n \nOptions:\n========\nSDESRPC - VSE-5819\n \nRoutines:\n=========\nJira Tickets:\nSDESGETREGA1 - VSE-5792\nSDEC07 - VSE-5570\nSDEC08 - VSE-5570 \nSDESRTVCLN2 - VSE-5545\nSDESCONTACTS - VSE-5941\nSDESCLNSEARCH - VSE-5670\nSDESGETAPPTWRAP5 - VSE-5896 \nSDES01C - VSE-5736\nSDESGETAPPTREQ - VSE-5536\nSDESGETREQWRAPPR - VSE-5536\n=============\nSDESGETREGA2 - VSE-5819\nSDESOPENVETREQS - VSE-5775 \nSDESBLOCKANDMOVE - VSE-5564\nSDESCREATEAPPT44 - VSE-5818\nSDESCANAPPT2 - VSE-5818\nSDESCREATEAPPT - VSE-5818\nSDESUTIL - VSE - 5818\n \nRemote Procedure Call:\n======================\nVSE-5545: DS - VistA: Modify SDES GET CLINIC INFO2 and SDES GET CLINICS \nSDES GET PATIENT REGISTRATION2 - VSE-5792\nSDES GET CLINIC INFO2 - VSE-5545\nSDES GET CLINICS BY CLIN LIST - VSE-5545\nSDES SEARCH CLINIC ATTRIBUTES - VSE-5670\nSDES GET APPT REQ BY IEN - VSE-5536\nSDES GET APPT REQ BY PAT ALL - VSE-5536\nSDES GET APPT REQ BY PAT OPEN - VSE-5536\nSDES GET APPT REQ BY PATIENT - VSE-5536\nSDES GET APPT REQ BY TYPE VET - VSE-5536\nSDES GET APPT REQ LIST BY DFN - VSE-5536\n BY CLIN LIST to return clinic status\nSDES GET APPT REQS BY IENS - VSE-5536\nSDES GET APPT REQS BY IENS2 - VSE-5536\nSDES GET CONSULTS BY DFN - VSE-5536\nSDES GET CONSULTS BY IEN - VSE-5536\nVSE-5770: BB - VistA: Do not allow the PID to be edited in VistA and VSE \n GUI for a consult or procedure\n\n
\nVSE Increment 8.8 - SD*5.3*853 - GUI v 1.7.46\nVSE-5564: BB - VistA: Rewrite SDES CREATE APPT BLK AND MOVE to accept a \n clinic IEN\nVSE-5566: JS - VistA: Create a new SDES2 RPC to get the medication list\nVSE-5576: BF - VistA: Create RPC to return all open appt requests, \n consults, and recall reminders for a given institution\nVSE-5620: LB - VistA: Create new versions of SDES CONTACT ADD/UPDATE and \n SDES CONTACT DISPLAY RPCs to include a context/metadata\n array as the first input parameter\nVSE-5701: TB - VSE Error when scheduling walk in appts between 12a-1am\nVSE-5742: BF - VistA: Create a new SDES2 GET HOLIDAYS to allow for an \n---------------------------------------------\n optional end date\nVSE-5819: AP - VistA: Create a new RPC to return patient registration \n data for the ids passed in\nVSE-5873: AP - VistA: Modify SDESCHECKOUT routine to lock/unlock record \n in SDE file\nVSE-5889: DS - VistA: Modify SDES GET PATIENT REGISTRATION2 to return the \n Date of Death\n \n \nFiles:\n \n======\nSDES ERROR CODES (#409.93) - VSE-5873,VSE-5523,VSE-5742\n \nOptions:\n========\nSDESRPC - VSE-5522,VSE-5566,VSE-5819,VSE-5523,VSE-5576\n \n \nInput Templates:\n================\nJira Tickets:\n \n \nRoutines:\n=========\nSDES2CLINUT - VSE-5523\nSDES2CREATECLIN - VSE-5522\nSDES2EDITCLIN - VSE-5523\nSDES2GETHOLIDAYS - VSE-5742\nSDES2GREQSINST - VSE-5576 \nSDES2VALCONTEXT - VSE-5522\n=============\nSDES2VALCRTCLIN1 - VSE-5522\nSDES2VAL2 - VSE-5522\nSDES2VAL200 - VSE-5522\nSDES2VAL44 - VSE-5522,VSE-5523\nSDES2VALISODTTM - VSE-5742\nSDES2VALUTIL - VSE-5576\nSDES2JSON - VSE-5522\nSDES2UTIL - VSE-5522\nSDESCREATEAPPT - VSE-5701\nSDES2GETMEDLIST - VSE-5566 \nVSE-5522: MD - VistA: Create a new version of the SDES CREATE CLINIC RPC \nSDESGETREGA2 - VSE-5819\nSDESCHECKOUT, SDESNOSHOW - VSE-5873\nSDESBLOCKANDMOVE - VSE-5564\n \n \nRemote Procedure Call:\n======================\nSDES2 CREATE CLINIC - VSE-5522\nSDES2 GET HOLIDAYS - VSE-5742\nSDES2 GET PATIENT MED LIST - VSE-5566\n that adheres to SDES standards\nSDES GET PATREG BY DFNICN - VSE-5819\nSDES2 GET REQUESTS BY INST - VSE-5576\nSDES BLOCK AND MOVE - VSE-5564\nVSE-5523: BF - VistA: Create a new version of SDES EDIT CLINIC RPC that \n adheres to SDES standards\n\n
\nThis patch provides a clean-up action for non 900 (Special Service) stop\ncodes in the SCHEDULING VISITS File, #409.5 \n\n
\nVSE Increment 8.7 - SD_5_3_856\n======\nN/A\n \nOptions:\n========\nN/A\n \nRoutines:\n=========\nN/A\n==============================\n \nRemote Procedure Call:\n======================\nN/A\n \nJira Tickets:\n=============\nVSE-5452: VistA: Update the Stop Code file #40.7 with the attached stop \n codes.\n \nFiles:\n\n
\nVSE Increment 8.9 - SD_5_3_857 - GUI v 1.7.47\n input parameter\nVSE-6158: MD - VistA: Modify SDES2 CREATE CLINIC to only accept active\n stop codes.\nVSE-6159: BF - VistA: Modify SDES2 EDIT CLINIC to only accept active stop \n codes.\n \n \nFiles:\n======\n---------------------------------------------\n \nInput Templates:\n================\nSDB - VSE-5823\n \nRoutines:\n=========\nSDESGETCONSULT -VSE-5982\nSDES2CLINUT - VSE-6159\nSDES2EDITCLIN - VSE-6159 \n \nSDES2VAL44 - VSE-6159\nSDES2VAL44A - VSE-6159\nSDESCLINICSET - VSE-5872\nSDES2UTIL - VSE-6159\nSDES2VALCRTCLIN1 - VSE-6158\n \n \nRemote Procedure Call:\n======================\nSDES GET APPT REQS BY IENS - VSE-5499\nJira Tickets:\nSDES CONTACT ADD/UPDATE - VSE-5499\nSDES CONTACT DISPLAY - VSE-5499\nSDES GET APPTS BY IENS - VSE-5499\nSDES2 EDIT CLINIC - VSE-6159\n=============\nVSE-5499: AP - VistA: Retire RPCs 90 days post release of patch 845\nVSE-5823: MD - Update SDBUILD to have default values for auto rebook, \n consecutive no-shows\nVSE-5982: AP - VistA: Calling SDESGETCONSULTS expects REQUEST as 1st \n\n
\nVSE Increment 8.10 - SD*5.3*860 - GUI v 1.7.48\n the first input parameter.\nVSE-6013: BB - VistA: Modify SDES GET CLINIC ORIGINAL AVAIL to correct \n defects.\nVSE-6060: DS - VistA: Modify the description for SDES SEARCH CLINIC \n ATTRIBUTES.\nVSE-6061: BF - VistA: Return Request Type in the SDES GET APPT */SDES GET \n APPTS * RPCs.\nVSE-6147: AP - VistA: Inactive stop codes can be sent into SDES EDIT \n CLINIC and SDES CREATE CLINIC RPCs.\nVSE-6177: BF - VistA: Update SDES2 GET HOLIDAYS RPC definition.\n----------------------------------------------\nVSE-6219: MD - VistA: Modify RPC definition in File #8994 for SDES2 \n CREATE CLINIC.\nVSE-6220: BF - VistA: Modify RPC definition in file #8994 for SDES2 EDIT \n CLINIC RPC.\nVSE-6305: MD - Fix bug in the SDES2 CREATE CLINIC filing logic for the \n multiple fields.\n \nFiles:\n======\n409.93 - VSE-5620 \n \n \nOptions:\n========\nSDESRPC - VSE-5620\n \n \nInput Templates:\n================\n \n \nJira Tickets:\nRoutines:\n=========\nSD53P860 - VSE-5537\nSDES2CONTACTS - VSE-5620\nSDES2VALCONTEXT - VSE-5620\nSDESAPPTDATA - VSE-6061\nSDESCLINDAILYSCH - VSE-6013\nSDESCLINICSET - VSE-6147\nSDESCLINICDATA - VSE-6061\nSDES2CREATECLIN - VSE-6305\n=============\nSDES2VALCRTCLIN1 - VSE-6305 \n \nRemote Procedure Call:\n======================\nSDES GET APPT BY APPT IEN - VSE-6061\nSDES GET APPTS BY CLIN IEN 3 - VSE-6061\nSDES GET APPTS BY IENS 2 - VSE-6061\nSDES GET APPTS BY PATIENT DFN3 - VSE-6061\nSDES2 ADD CONTACT ATTEMPT - VSE-5620\nSDES2 GET CONTACT ATTEMPTS - VSE-5620\nVSE-5537: AP - VistA: Post-install to update null e-checkin allowed and \nSDES2 GET HOLIDAYS - VSE-6177\nSDES2 GET REQUESTS BY INST - VSE-6177\nSDES2 CREATE CLINIC - VSE-6219\nSDES2 EDIT CLINIC - VSE-6220\n pre-checkin allowed to "No".\nVSE-5620: LB - VistA: Create new versions of SDES CONTACT ADD/UPDATE and \n SDES CONTACT DISPLAY RPCs to include a context/metadata array as\n\n
\nJira Tickets:\nOptions:\n========\nN/A\n \nInput Templates:\n================\nN/A\n \nRoutines:\n=========\n=============\nSDESCLNSETAVAIL - VSE-6614 (Modified)\n \nRemote Procedure Call:\n======================\nSDES CREATE CLIN AVAILABILITY - VSE-6614 (Modified)\nSDES EDIT CLINIC AVAILABILITY - VSE-6614 (Modified)\nVSE-6614: BB - VistA: Modify SDES CREATE CLIN AVAILABILITY and SDES EDIT \n CLINIC AVAILABILITY to create indefinite availability.\n \nFiles:\n======\nN/A\n \n\n
\nVSE Increment 8.16 - SD_5_3_870\nFiles:\n======\n409.93 - VSE-6301\n \nOptions:\n========\nSDESRPC - VSE-6301\n \nRoutines:\n=========\n \nSDES2CLNSEARCH - VSE-6301, VSE-6723\nSDES2VAL4 - VSE-6723 \nSDES2UTIL1 - VSE-6301 \nRemote Procedure Calls:\n=======================\nSDES2 SEARCH CLINIC ATTRIBUTES - VSE-6301, VSE-6723\nJira Tickets\n============\nVSE-6301: MD - VistA: Modify SDES SEARCH CLINIC ATTRIBUTES to return both \n Active and Inactive clinics\nVSE-6723: MD - VistA: Modify SDES SEARCH CLINIC to include type, type \n extension, and occasion of service in the return object\n \n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*859.\n\n
\nVSE Increment 8.11 - SD*5.3*861 - GUI v 1.7.49\nVSE-6127: BF - VistA - Possible defect in SDES CREATE RECALL REQ 2\nVSE-6143: JS- VistA: Create a new RPC in the SDES2 namespace to record \n demographics verified date\nVSE-6176: TB - VistA - Modify appointment request object to return the \n clinic stop code\nVSE-6201: AP - VistA - Rewrite SDEC EP PT INFO in the SDES2 namespace\nVSE-6276: BF - VistA - Fix <UNDEFINED> error in SDES2VALUTIL\n \n \nVSE Increment 8.12 - SD*5.3*861 - GUI v 1.7.49\n----------------------------------------------\n----------------------------------------------\n \nJira Tickets:\n=============\nVSE-5530: AP - VistA: Create a new version of SDES GET APPTREQ BY INST to \n retrieve appointment requests for Consults and Recall Reminders\nVSE-6141: BB - VistA: Add the patient search return to SDES2 GET LAST \n SELECTED PAT\nVSE-6205: TB - VistA: Rewrite SDES REACTIVATE CLINIC in SDES2 namespace\n to return an error if a duplicate clinic will be created\n \nVSE-6206: BF - VistA: Modify SDES SEARCH CLINIC ATTRIBUTES to search for \n a clinic by abbreviation\nVSE-6279: LB - VistA: Create a new RPC in the SDES2 namespace to restore \n clinic availability\nVSE-6294: BB - VistA: Create a new RPC in the SDES2 namespace to return \n Expanded Entry Fields\nVSE-6328: JS - VistA: Modify SDES2 GET PATIENT MED LIST\n \n \nFiles:\nJira Tickets:\n======\nSDES ERROR CODES (409.93) - VSE-6276, VSE-6143\nOptions:\n========\nSDESRPC - VSE-6201, VSE-5546, VSE-6143, VSE-6279, VSE-6205, VSE-5530\n \nInput Templates:\n================\n \n \n=============\nRoutines:\n=========\nSDES2RSTCAVAIL - VSE-6279\nSDES2VALUTIL - VSE-6276\nSDESUPDRECREQ2 - VSE-6127\nSDES2EPT - VSE-6201\nSDES2GETLINKS - VSE-5546\nSDESCLNSEARCH - VSE-6206\nSDESGETAPPTREQ - VSE-6176 \nSDESGETAPPTREQ2 - VSE-6176\nVSE-5546: TB - VistA - Create a new RPC in the SDES2 namespace to return\nSDES2EDITPREREG - VSE-6143 (New)\nSDES2GETMEDLIST - VSE-6328 (Modified)\nSDES2REACTTCLIN - VSE-6205 (New)\nSDES2UTIL1 - VSE-6205 (Modified)\nSDESGETAREQINST2 - VSE-5530\n \nRemote Procedure Call:\n======================\nSDES CREATE RECALL REQ 2 - VSE-6127 (Modified)\nSDES2 GET PATIENT EP - VSE-6201 (New)\n the national and local help links\nSDES2 GET HELP LINKS - VSE-5546 (New)\nSDES2 EDIT PAT PRE-REG - VSE-6143 (New)\nSDES2 GET PATIENT MED LIST - VSE-6328 (Modified)\nSDES2 RESTORE CLIN AVAIL - VSE-6279 (New)\nSDES2 REACTIVATE CLINIC - VSE-6205 (New)\nSDES GET APPTREQ BY INST2 - VSE-5530 (New)\nSDES2 GET EXPANDED ENTRY - VSE-6294 (New)\nSDES2 GET LAST SELECTED PAT - VSE-6141 (New)\nVSE-5829: BB - VistA is duplicating appointments in PCE and \n disassociating progress notes from the original encounter (Guam)\n\n
\nVSE Increment 8.13 - SD*5.3*862 - GUI v 1.7.50\nVSE-6310: AP - VistA: Refactor SDES PATIENT SEARCH RPC in the SDES2 \nSDES2CREATESNAPS - VSE-6208 (NEW)\nSDES2EDITSNAPS - VSE-6208 (NEW)\nSDES2GETSNAPS - VSE-6208 (NEW)\nSDES2RECLDIPREAS - VSE-6509 (New) \nSDES2STOREPAT - VSE-6424 (New)\nSDESCANAPPT2 - VSE-6428\nSDESCLINICAVAIL - VSE-6386 (Modified)\nSDESCLINICSET - VSE-6399\nSDESCRTAPPTWRAP - VSE-6425\nSDESEDITAPPTREQ - VSE-6425\n namespace\nSDESMISSIONELG - VSE-6608\nSDESNOSHOW - VSE -6429, VSE-6435\nSDESRTVCLN2 - VSE-6405 (Modified) \nSDESGETCLINSIEN - VSE-6836 (Modified)\nSDES2VAL44 - VSE-6978 (Modified) \nSDES2EDITCLIN - VSE-6977 (Modified)\n \nRemote Procedure Calls:\n=======================\nSDES CREATE APPT REQ - VSE-6365 (Updated)\nVSE-6316: VS GUI: Select patient from patient search should not open \nSDES GET APPT TYPES - VSE-6372 (Updated)\nSDES2 GET APPT TYPES BY DFN - VSE-6329 (NEW)\nSDES2 GET VVC STOP CODES - VSE-6351 (NEW)\nSDES2 INACTIVATE CLINIC - VSE-6204 (NEW)\nSDES2 PATIENT SEARCH - VSE-6310 (NEW)\n \n \nSDES DISPOSITION APPT REQ - VSE-6421 (Modified)\nSDES GET CLINIC INFO2 - VSE-6405 (Modified) \nSDES2 CREATE LAST SELECTED PAT - VSE-6424 (New)\n multiple dialogs if the user multi clicks\nSDES2 CREATE SPEC NEEDS PREFS - VSE-6208 (NEW)\nSDES2 EDIT SPEC NEEDS PREFS - VSE-6208 (NEW) \nSDES2 GET RECALL DELETE REASON - VSE-6509 (New)\nSDES2 GET SPEC NEEDS PREFS - VSE-6208 (NEW)\nSDES2 EDIT CLINIC VSE-6977 (Modified)\nVSE-6317: DR - VistA: Update SCMSVUT3 to account for new Agent Orange \n exposure locales\nVSE-6329: TB - VistA: Create a new RPC to return active appointment types \n for a selected patient\nVSE-6335: BB - VistA: SDESCANAPPT2 throws an error when using cancel \n reasons that don't reopen the request\n----------------------------------------------\nVSE-6343: AP - VistA: Modify Appointment Object to return Last 4 SSN, \n DOB, and Date of Death\nVSE-6351: JW - VistA: Return the VVC STOP CODE values from SDEC SETTINGS\nVSE-6365: MD - VistA: Default Priority to ASAP in SDES CREATE APPT REQ.\nVSE-6372: TB - VistA: Modify SDES GET APPTYPES to return only Active \n appointment types\nVSE-6571: LB - Invalid Error Message displaying if the date/time is \n missing during Cancel Restore\nVSE-6584: TB - Modify SDES2 REACTIVATE CLINIC\nVSE-6614: BB - VistA: Modify SDES CREATE CLIN AVAILABILITY and SDES EDIT \n \n \n \nVSE Increment 8.14 - SD_5_3_864 - GUI v 1.7.51\n==============================================\n \nJira Tickets:\n=============\nVSE-6208: BB - VistA - Updating Special Needs and Preferences is saving \n the proxy user instead of the original requestor\nVSE-6386: MD - VistA - Correct issue where SDES GET CLIN AVAILABILITY \nJira Tickets\n does not return a time zone offset\nVSE-6399: DS - VistA - Modify SDES CREATE CLINIC and SDES EDIT CLINIC to \n specify which stop code is inactive\nVSE-6405: JS - VistA - Modify SDES GET CLINIC INFO2 to return Provider \n IEN as an output object\nVSE-6421: BF - VistA - Modify documentation for SDES DISPOSITION APPT REQ \n to update DISPBY to the User IEN\nVSE-6424: TB - VistA - Rewrite SDES CREATE LAST SELECTED PAT in the SDES2 \n namespace\nVSE-6425: LB VistA - Modify SDES CREATE APPOINTMENTS to pull PID from the \n============\n request if there is no PID sent in\nVSE-6428: AP - VistA - Modify SDES CANCEL APPOINTMENT 2 to store "O" not \n "OPEN"\nVSE-6429: AP - VistA - Modify SDES UNDO NOSHOW to update the status with \n "C" for Closed\nVSE-6435: AP - VistA - Modify SDES NOSHOW to store "O" instead of OPEN\nVSE-6438: LB - VistA - The SDCANCEL option needs to be modified to \n prevent the "ST" record from being created when user erroneously\n enters a date that is not defined in the availability.\nVSE-6443: JS - Modify the GETDPROIEN Tag of SDECVVS to pull the default \nVSE-6204: TB - VistA: Rewrite SDES INACTIVATE/ZZ CLINIC to add a cancel \n provider from provider multiple of the HOSPITAL LOCATION.\nVSE-6509: TB - VistA: Create a new RPC to get recall disposition\n reasons from 403.56 \nVSE-6608: LB - VistA: Modify Wait Time Standard calculations \nVSE-6836: MD - VistA: SDES GET CLINICS BY CLIN LIST is throwing an error\nVSE-6977: BF - VistA: Modify SDES2 EDIT CLINIC to allow editing of length\n of appointment.\nVSE-6978: BF - VistA: Correct SDES2 CREATE CLINIC to allow length of\n appt in multiples of 10 up to 240\n \n date in the SDES2 namespace\n \nFiles:\n======\n409.93 - VSE-6399\n \nOptions:\n========\nSDESRPC\n \n \nVSE-6280: LB - VistA: Fix issue where CA do not display in RM Grid for \nRoutines:\n=========\nSCMSVUT3 - VSE-6317 (MODIFIED)\nSDECAR1A - VSE-6280 (MODIFIED)\nSDES2APPTYPES - VSE-6329 (NEW)\nSDES2GETVVCCODES - VSE-6351 (NEW)\nSDES2INACTCLIN - VSE-6204 (NEW)\nSDES2PATSEARCH - VSE-6310 (NEW)\nSDES2REACTTCLIN - VSE-6584 (MODIFIED)\nSDES2RSTCAVAIL - VSE-6571 (MODIFIED)\n cancelled appointments\nSDES2UTIL - VSE-6310 (MODIFIED)\nSDESAPPTDATA - VSE-6343 (NEW)\nSDESCANAPPT2 - VSE-6335 (MODIFIED)\nSDESCREATEAPPREQ - VSE-6365 (MODIFIED)\nSDESGETAPPTTYPE - VSE-6372 (MODIFIED) \nSDESUPDRECREQ2 - VSE-6308 (MODIFIED) \n \n \nSDC - VSE-6438\nSDECVVS - VSE-6443 (Modified)\n\n
\nVSE Increment 8.15 - SD*5*3*866 - GUI v 1.7.52\nVSE-6470: TB - VistA: Rewrite SDES CREATE RECALL REQ 2 in the SDES2 \n namespace\nVSE-6474: TB - VistA: Rewrite SDES EDIT RECALL REQ 2 in the SDES2 \n namespace\nVSE-6475: AP - VistA: Rewrite SDES DISPOSITION APPT REQ in the SDES2 \n namespace\nVSE-6479: BF - Vista: Rewrite SDES DISPOSITION RECALL REQ in the SDES\n namespace\nVSE-6484: BB - SDES2 Priority 10: Rewrite SDES CREATE APPOINTMENTS in the\n SDES2 namespace\n==============================================\nVSE-6485: TB - VistA: Rewrite SDES CHECKIN in the SDES2 namespace\nVSE-6552: BB - VistA: Modify SDES READ CLINIC GROUP to return CLINIC IEN \n or PROVIDER IEN based on the RESOURCE TYPE\nVSE-6589: BB - VistA: Create SDES2 RPC for Patient Information\nVSE-6591: LB - VistA: Modify SDES CREATE WALKIN APPT to call new check in \n routine\nVSE-6593: LB - VistA: New SDES2 RPC return back - has the given clinic \n ever had any availability defined?\nVSE-6606: MD - VistA: Update SDES2 EDIT CLINIC to allow for the editing \n of the holiday field\n \nVSE-6673: LB - VistA: Modify SDES2 GET LAST SELECTED PAT to use SDCONTEXT \n USER DUZ\nVSE-6906: MD - VistA: Create a new SDES2 RPC to return all future canceled\n slots given a clinic ID.\nVSE-7001: BF - VistA: Update SDES2 EDIT CLINIC to allow removal of default\n designation from both provider and diagnosis.\nVSE-7021: VistA: Correct issue with neurology service not saving on \n creation or edit.\n \nFiles:\nVSE-6406: BB - Clinic Special Instructions are alphabetized, rather than \n======\nSDES ERROR CODES (#409.93) - VSE-6469, VSE-6473, VSE-6469\n \nOptions:\n========\nSDESRPC - VSE-6593, VSE-6470, VSE-6474, VSE-6475, VSE-6484\n VSE-6479, VSE-6485, VSE-6593, VSE-6906\n \nRoutines:\n=========\n being saved sequentially\nSDECAPI - VSE-6485 (New)\nSDES2APPTUTIL - VSE-6484 (NEW)\nSDES2ARCLOSE - VSE-6475 (New)\nSDES2CHECKIN - VSE-6485 (New)\nSDES2CHKCAVAIL - VSE-6593 (new)\nSDES2CLINUT - VSE-7001 (Mod)\nSDES2CREATEAPPT - VSE-6484 (NEW)\nSDES2DISPRECALL - VSE-6479 (New)\nSDES2EDITCLIN - VSE-6606 (Mod) \nSDES2GETCANSLOTS - VSE-6906 (New) \nVSE-6456: BB - VistA: Modify SDES BLOCK AND MOVE to send output as \nSDES2GETPATINFO - VSE-6589 (NEW) \nSDES2GETRESGROUP - VSE-6552 (NEW)\nSDES2GETSTORDPAT - VSE-6673 (mod)\nSDES2PATSEARCH - VSE-6589 (MOD)\nSDES2RECLLREQ - VSE-6470 (New), VSE-6474 (New)\nSDES2SEARCHCLNAT - VSE-6457 (NEW)\nSDES2VAL44 - VSE-6606 (Mod)\nSDES2VALUTIL - VSE-6473 (Mod)\nSDESBLOCKANDMOVE - VSE-6456 (MOD)\nSDESCRTWALKIN - VSE-6591 (mod)\n properly formatted JSON\nSDRRISRU - VSE-6479 (Mod) \nSDESRTVCLN2 - VSE-6406 (Mod) \n \n \nRemote Procedures:\n==================\nSDES BLOCK AND MOVE - VSE-6456 (Mod)\nSDES GET CLINIC INFO3 - VSE-6406 (New)\nSDES2 CHECK CLIN AVAIL DEFINED - VSE-6593 (new)\nSDES2 CHECKIN - VSE-6485 (New)\nVSE-6457: BB - VistA: Modify SDES SEARCH CLINIC ATTRIBUTES to have an \nSDES2 CREATE APPOINTMENT - VSE-6484 (NEW)\nSDES2 CREATE RECALL REQUEST - VSE-6470 (New)\nSDES2 DISPOSITION APPT REQ - VSE-6475 (New)\nSDES2 DISPOSITION RECALL REQ - VSE-6479 (New)\nSDES2 EDIT CLINIC - VSE-6606 (Mod)\nSDES2 EDIT RECALL REQUEST - VSE-6474 (New)\nSDES2 GET CANCELLED SLOTS - VSE-6906 (New)\nSDES2 GET LAST SELECTED PAT - VSE-6673 (mod)\nSDES2 GET RESOURCE GROUP - VSE-6552 (New)\n optional input parameter\n\n
\nVSE Increment 8.17 - SD*5*3*867 - GUI v 1.7.53\nVSE-6487: BB - SDES2 Priority 13: Rewrite SDES CREATE VET REQ SCHED APPT \n in the SDES2 namespace.\nVSE-6550: LB - VistA: Create a new SDES2 RPC that accepts a Resource Type \n and IEN and returns RESOURCE IEN\nVSE-6682: AP - VistA: Modify SDES2 GET PATIENT EP to return all dates in \n ISO 8601 format.\nVSE-6725: LB - VistA: Modify SDES GET APPT REQ* RPCs and SDES2 GET \n REQUESTS BY INST to return stop codes for consults and\n procedures.\nVSE-6726: AP - VistA: Modify SDES01C routine to remove lines 58 though 61 \n==============================================\n and skip looking at abbreviations in the C cross reference.\nVSE-6791: MD - VistA: Update the RPC definition for SDES CREATE APPT REQ\n in FileMan to add the properly formatted JSON return.\nVSE-6817: LB - VistA: Modify SDES GET CLINIC INFO2 to return the Resource \n IEN to the return object\nVSE-6831: LB - VistA: Modify SDES GET CANCEL REASONS to return back the \n REOPEN UPON CANCELLATION field\nVSE-6835: BB - VistA: Modify SDES2 GET EXPANDED ENTRY to return the \n diagnostic code with the diagnosis\nVSE-6840: LB - VistA: Modify SDAMUTDT routine to correctly recognize a \n \n "zero offset" clinic\nVSE-6877: LB - VistA: Issue with block and move\nVSE-7054: BB - VistA: Modify SDES2 GET RESOURCE GROUP to include resources\n that have been inactivated in the past\n \nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-6487 \n \nOptions:\nTickets:\n========\nSDESRPC - VSE-6487, VSE-6482, VSE-6550, VSE-6835, VSE-6486\n \nRoutines:\n=========\nSDAMUTDT - VSE-6480 (mod)\nSDES01C - VSE-6726 (new)\nSDES2APPTCLNLST - VSE-6482 (New)\nSDES2CRTAPPT - VSE-6778 (mod)\nSDES2CRTVETAPPT - VSE-6487 (new)\n========\nSDES2EPT - VSE-6682 (new)\nSDES2GETRESIEN - VSE-6550 (New)\nSDES2GETXPENTRY2 - VSE-6835 (new)\nSDES2PATDATA - VSE-6482 (New)\nSDES2SETCHECKOUT - VSE-6486 (New)\nSDESBLOCKANDMOVE - VSE-6877 (mod)\nSDESCANCELRSNS -VSE-6831 (mod)\nSDESCHECKOUT - VSE-6486 (mod) \nSDESGETCONSULTS - VSE-6725 (mod)\nSDESRTVCLN2 - VSE-6817 (mod)\nVSE-6482: TB - SDES2 Priority 8: Rewrite SDES GET APPTS BY CLINIEN LIST \nSDES2GETRESGROUP - VSE-7054 (mod) \n \nRemote Procedures:\n==================\nSDES CREATE APPT REQ (mod)\nSDES GET APPT REQ LIST BY DFN - VSE-6725 (mod)\nSDES GET CANCEL REASONS - VSE-6831 (mod)\nSDES GET CLINIC INFO2 - VSE-6817 (mod)\nSDES GET CONSULTS BY DFN - VSE-6725 (mod)\nSDES GET CONSULTS BY IEN - VSE-6725 (mod)\n in the SDES2 namespace.\nSDES SEARCH CLINIC - VSE-6726 (mod)\nSDES2 CREATE VET REQ AND APPT - VSE-6487 (new)\nSDES2 GET APPTS CLINIEN LIST - VSE-6482 (New)\nSDES2 GET EXPANDED ENTRY 2 - VSE-6835 (new)\nSDES2 GET PATIENT EP - VSE-6682 (mod)\nSDES2 GET RESOURCE IEN - VSE-6550 (New)\nSDES2 SET APPT CHECKOUT - VSE-6486 (New)\nVSE-6486: JS - SDES2 Priority 12: Rewrite SDES CHECKOUT in the SDES2 \n namespace.\n\n
\nFixes a problem with PCMM team name changes not correctly updating\nSC("TEAM" xref in file 44. See NPM for complete description.\n\n\nVSE Increment 8.18 - SD_5_3_869 - GUI v 1.7.53\nVSE-6481: TB - SDES2 Priority 7: Rewrite SDES GET APPTS BY CLIN LIST2 in \nSDES GET HOLIDAYS - VSE-6139 set to delete at site\nSDES SEARCH PROVIDERS - VSE-6988 (MOD)\nSDES2 CANCEL APPOINTMENT - VSE-6494 (NEW)\nSDES2 CANCEL CLINIC AVAIL - VSE-6495 (NEW)\nSDES2 CREATE APPT REQ - VSE-6469 (NEW)\nSDES2 CREATE PROVIDER RESOURCE - VSE-6989 (NEW)\nSDES2 CREATE WALKIN APPT - VSE-6488 (NEW)\nSDES2 EDIT APPT REQ - VSE-6473 (NEW)\nSDES2 EDIT PROVIDER RESOURCE - VSE-6990 (NEW)\nSDES2 GET APPTS BY CLIN LIST - VSE-6481 (NEW)\n the SDES2 namespace.\nSDES2 GET ELIGIBILITY CODES - VSE-7037 (NEW)\nSDES2 GET PATIENT CLIN STATUS - VSE-6884 (NEW)\nSDES2 QUERY APPT REQUESTS - VSE-6418 (NEW)\nSDES2 SET APPT CHECKIN - VSE-6492 (NEW)\nSDES2 SET CHECK-IN STEP - VSE-6493 (NEW)\nSDES2 GET APPTS CLINIEN LIST - VSE-6481 (MOD)\nVSE-6492: AP - SDES2 Priority 18: Rewrite SDES SET APPT CHECK-IN STEP in \n the SDES2 namespace.\nVSE-6493: AP - SDES2 Priority 19: Rewrite SDES SET CHECK-IN STEP in the \n SDES2 namespace.\nVSE-6494: JS - SDES2 Priority 20: Rewrite SDES CANCEL APPOINTMENT 2 in \n the SDES2 namespace.\nVSE-6878: BB - VistA: Fix issues in SDES CREATE APPOINTMENTS RPC and SDEC \n APPADD.\n \n \n \nVSE Increment 8.19 - SD_5_3_869 - GUI v 1.7.53\n==============================================\nVSE-6418: BF - VistA: Create an RPC in the SDES2 namespace to add\n additional fields to the Query Search Tool\nVSE-6488: JS - SDES2 Priority 14: Rewrite SDES CREATE WALKIN APPT in \n the SDES2 namespace\nVSE-6495: BB - SDES2 Priority 21: Rewrite SDES CANCEL CLIN AVAILABILITY in\n the SDES2 namespace\nTickets:\nVSE-6624: JJ - VistA: Modify SDES CREATE APPT REQ to verify the patient \n DFN on both the child request and parent request match\nVSE-6821: MD - VistA: Modify SDES2 EDIT CLINIC to allow removal of \n inactive diagnostic codes\n APPADD\nVSE-6884: BB - VistA: Create a new RPC in the SDES2 namespace to look back\n 36 months to determine established patients\nVSE-6988: MB - VistA: Correct spelling mistakes in the Remote Procedures\n file for SDES ADD CLNGRP ITEM and SDES SEARCH PROVIDER\nVSE-6989: LB - VistA: Create a new RPC in the SDES2 namespace to create\n========\n a provider resource\nVSE-6990: LB - VistA: Create a new RPC in the SDES2 namespace to edit a \n provider resource\nVSE-7007: AP - VistA: SDES CHECKOUT is working intermittently\nVSE-7024: MD - VistA: Add appropriate fields to VistA files\nVSE-7037: LB - VistA: Create a new RPC that returns back Eligibility of\n Visits values from file #8\nVSE-7065: LB - VistA: Modify SDES2 CHECK CLIN AVAIL DEFINED RPC to not \n return an undefined error\nVSE-7138: BB - VistA: Modify SDES2 CREATE APPOINTMENT to convert start \nVSE-6139: TB - VistA: Retire RPCs 90 days post patch 853\n date to ISO format correctly\nVSE-7151: BB - VistA: Modify the return error response in SDES2 CREATE \n VET REQ AND APPT.\n \n \nFiles:\n======\nSDES ERROR CODES (#409.93) - VSE-6469, VSE-6473,VSE-6990\n \nOptions:\nVSE-6469: BF - SDES2 Priority 1: Rewrite SDES CREATE APPT REQ in the \n========\nSDECRPC - VSE-6139, VSE-6481, VSE-6488, VSE-6492, VSE-6493\nSDESRPC - VSE-6139, VSE-6494, VSE-6481, VSE-6469, VSE-6473, VSE-6989, \n VSE-6990, VSE-6488, VSE-7037, VSE-6418, VSE-6884, VSE-6495,\n VSE-6492, VSE-6493\n \nRoutines:\n=========\nSDEC07 - VSE-6878 (MODIFIED)\nSDES2APPTCKNSTEP - VSE-6492 (NEW)\n SDES2 namespace.\nSDES2CANCELAPPT - VSE-6494 (NEW)\nSDES2CANCLNAVAIL - VSE-6495 (NEW)\nSDES2CHKCAVAIL - VSE-7065 (MODIFIED)\nSDES2CKNSTEP - VSE-6493 (NEW)\nSDES2CLINICLIST - VSE-6481 (NEW)\nSDES2CREATEAPPT - VSE-7138 (MODIFIED)\nSDES2CRTAPREQ - VSE-6469 (NEW)\nSDES2CRTPRVRES - VSE-6989 (NEW)\nSDES2CRTVETAPPT - VSE-7151 (MODIFIED)\nSDES2CRTWALKIN - VSE-6488 (NEW)\nVSE-6473: BF - SDES2 Priority 3: Rewrite SDES EDIT APPT REQ in the SDES2 \nSDES2EDITAPREQ - VSE-6473 (NEW)\nSDES2EDITPRVRES - VSE-6990 (NEW)\nSDES2GETELIGCD - VSE-7037 (NEW)\nSDES2GETPATSTAT - VSE-6884 (NEW)\nSDES2QRYAPREQS - VSE-6418 (NEW)\nSDES2QRYAPREQSA - VSE-6418 (NEW)\nSDES2QRYAPREQSB - VSE-6418 (NEW)\nSDES2GETPATSTAT - VSE-6884 (NEW)\nSDES2CANCLNAVAIL - VSE-6495 (NEW)\nSDESCHECKOUT - VSE-7007 (MODIFIED)\n namespace.\nSDESCREATEAPPREQ - VSE-6624 (MODIFIED)\nSDESCREATEAPPT - VSE-6878 (MODIFIED)\nSDES2PATDATA - VSE-6481 (MODIFIED) \n \nRemote Procedures:\n==================\nSDES ADD CLNGRP ITEM - VSE-6988 (MOD)\nSDES CLINIC RSC SEARCH JSON - VSE-6139 set to delete at site\nSDES CREATE CLINIC - VSE-6139 set to delete at site\nSDES EDIT CLINIC - VSE-6139 set to delete at site\n\n
\nVSE Increment 8.20 - SD_5_3_871 - GUI v 1.7.54\nVSE-6490: BB - SDES2 Priority 16: Rewrite SDES UNDO NOSHOW in the SDES2 \nSDESCLINICDATA - VSE-7102 (MODIFIED)\nSDESCREATEAPPREQ - VSE-6883 (Modified)\nSDESCRTAPPREQVAL - VSE-6883 (NEW)\nSDESEDITAPPTREQ - VSE-6883 (Modified)\nSDESHASHCLIN - VSE-7100/7025 (MODIFIED)\nSDESPROVCLINSRCH - VSE-7100 (MODIFIED)\nSDESRTVCLN2 - VSE-7100 (MODIFIED)\nSDESRTVCLN3 - VSE-7100 (MODIFIED)\nSDESSEARCHRCLN - VSE-7100 (MODIFIED)\n \n namespace.\nRemote Procedures:\n==================\nSDES GET ALL CLINIC HASHES - VSE-7100 (MODIFIED)\nSDES GET APPTS BY RESOURCE - VSE-7102 (MODIFIED)\nSDES GET CLINIC INFO2 - VSE-7100 (MODIFIED)\nSDES GET CLINIC INFO3 - VSE-7100 (MODIFIED)\nSDES GET CLINIC STORED HASH - VSE-7100 (MODIFIED)\nSDES GET CLINICS BY CLIN LIST - VSE-7100 (MODIFIED)\nSDES GET CLINICS BY PROVIDER - VSE-7100 (MODIFIED)\nSDES SEARCH CLINIC - VSE-7100 (MODIFIED)\nVSE-6491: BB - SDES2 Priority 17: Rewrite SDES NOSHOW in the SDES2 \nSDES SEARCH RECALL CLINICS - VSE-7100 (MODIFIED)\nSDES2 CANCEL APPOINTMENT - VSE-7344 (MODIFIED)\nSDES2 CREATE CLINIC - VSE-7025 (MODIFIED)\nSDES2 CREATE WALKIN APPT - VSE-7345 (MODIFIED)\nSDES2 CREATE VET REQ AND APPT - VSE-7346 (MODIFIED)\nSDES2 EDIT CLINIC - VSE-7025 (MODIFIED)\nSDES2 BLOCK AND MOVE - VSE-6497 (NEW)\nSDES2 GET APPT BY APPT IEN - VSE-6278 (NEW)\nSDES2 GET APPTS BY APPT IENS - VSE-6278 (NEW)\nSDES2 GET APPTS BY CLIN LIST - VSE-7102 (MODIFIED)\n namespace.\nSDES2 GET APPTS BY CLINIC IEN - VSE-6278 (NEW)\nSDES2 GET APPTS BY PATIENT DFN - VSE-6278 (NEW)\nSDES2 GET PATIENT CLIN STATUS - VSE-7326 (MODIFIED)\nSDES2 GET RECALL BY IEN - VSE-6824 (NEW)\nSDES2 GET RECALLS BY DFN - VSE-6824 (NEW)\nSDES2 GET SCHEDULING USERS - VSE-7014 (NEW)\nSDES2 GET INFO FOR VIDEO VISIT - VSE-6500 (NEW)\nSDES2 NO-SHOW - VSE-6491 (NEW)\nSDES2 SEARCH CLINIC ATTRIBUTES - VSE-7100 (MODIFIED)\nSDES2 SET APPT CHECKIN - VSE-7245 (MODIFIED)\nVSE-6497: TB - SDES2 Priority 22: Rewrite SDES BLOCK AND MOVE in the \nSDES2 GET VIDEO VISIT PROV - VSE-6499 (NEW)\nSDES2 UNDO NO-SHOW - VSE-6490 (NEW) \n SDES2 namespace.\nVSE-6499: AP - SDES2 Priority 24: Rewrite SDES SPACEBAR VVS PRO in the \n SDES2 namespace.\nVSE-6500: AP - SDES2 Priority 25: Rewrite SDES GETVVSMAKEINFO JSON in the \n SDES2 namespace.\n==============================================\nVSE-6824: TB - SDES2 Priority 28: Rewrite SDES GET RECALL BY IEN in the \n SDES2 namespace to address sensitive patient records.\nVSE-6883: JS - VistA: Correct incorrect filing of the MRTC CALC PREF DATE \n onto the child request.\nVSE-7008: MB - VistA: Modify function $$GET44RECORDIENS^SDESCANCELAPPTS \n to filter past cancelled appointments.\nVSE-7011: BF - VistA: Discovery: The SDAM background job is creating \n appointments the next day.\nVSE-7014: LB - VistA: Rewrite SDEC SCHUSR RPC in the SDES2 namespace\nVSE-7025: BB - VistA: Update the appropriate RPCs to incorporate new\n \n fields to support PBSP.\nVSE-7076: JJ - VistA: SDES CANCEL CLINIC AVAILABILITY results in creating \n erroneous availability.\nVSE-7100: BF - VistA: Update the appropriate RPCs to incorporate new\n fields to support PBSP.\nVSE-7101: LB - VistA: Update the appropriate RPCs to incorporate new \n fields to support PBSP.\nVSE-7102: VistA: Update the appropriate RPCs to incorporate new fields to \n support PBSP.\nVSE-7161: LB - VistA: Modify SDES2 CREATE PROVIDER RESOURCE so that the \nVSE-5278: JS - Update the code to add ENDDATE to the list of variables to \n clinic IEN is no longer required\nVSE-7218: LB - VistA: Fixes an issue with SDES2 GET RESOURCE IEN \n returning an empty "ResourceIEN" field instead of the correct\n field, "Resource"\nVSE-7245: LB - VistA: Change input parameter "SDIEN" to "APPPOINTMENT IEN"\n in SDES2 SET APPT CHECKIN and correct logic to accept status\n name\nVSE-7310: TB - VistA: Fix issue with Undefined variable CLINICIEN in \n SDES2APPTUTIL.\nVSE-7326: BB - VistA: Correct the tag for the SDES2 GET PATIENT CLIN \n save.\n STATUS RPC.\nVSE-7344: JS - VistA: Modify SDES2 Cancel Appointment to utilize the \n "Acheron Audit ID" instead of "EAS"\nVSE-7345: JS - VistA: Modify SDES2 CREATE WALKIN APPT to utilize the \n "Acheron Audit ID" and verify all INPUT parameters exist\nVSE-7346: BB - VistA: Correct SDES2 CREATE VET REQ AND APPT definition to \n remove the EAS input parameter\n \nFiles:\n======\nVSE-6278: LB - VistA: Modify the appointment object to return a flag if \nSDES ERROR CODES - VSE-6278 \n \nOptions:\n========\nSDECRPC - VSE-6499, VSE-6500, VSE-7100 \nSDESRPC - VSE-7014, VSE-6824, VSE-6490, VSE-6491, VSE-6430, VSE-6278,\n VSE-6499, VSE-6500, VSE-6497\n \nRoutines:\n=========\n the appointment was created from an MRTC request, add the\nSDD - VSE-5278 (Modified)\nSDES01C - VSE-7100 (MODIFIED)\nSDES2APPTCKNSTEP - VSE-7245 (Modified)\nSDES2APPTUTIL - VSE-7310 (Modified)\nSDES2BLDAPPT2 - VSE-6278 (NEW)\nSDES2BLDAPPT44 - VSE-6278 (NEW)\nSDES2BLDAPPTOBJ - VSE-6278 (NEW)\nSDES2BLOCKMOVE - VSE-6497 (NEW)\nSDES2CANCELAPPT - VSE-6883, VSE-7008, VSE-7344 (MODIFIED)\nSDES2CLNSEARCH - VSE-7100 (MODIFIED)\n patient Ward, and do not return a subscript error when variable\nSDES2CREATECLIN - VSE-7025 (MODIFIED)\nSDES2CRTAPREQ - VSE-6883 (Modified)\nSDES2CRTPRVRES - VSE-7161 (Modified)\nSDES2CRTWALKIN - VSE-7345 (Modified)\nSDES2EDITAPREQ - VSE-6883 (Modified)\nSDES2EDITCLIN - VSE-7025 (MODIFIED)\nSDES2GETAPPTRPCS - VSE-6278 (NEW)\nSDES2GETRECALL - VSE-6824 (NEW)\nSDES2GETRESIEN - VSE-7218 (MODIFIED)\nSDES2GETSCDUSRS - VSE-7014 (NEW)\n DFN is used.\nSDES2GETSTATUS - VSE-6278 (NEW)\nSDES2NOSHOW - VSE-6491 (NEW)\nSDES2SPACEBAR - VSE-6500 (NEW)\nSDES2UNDONOSHOW - VS3-6430 (NEW)\nSDES2VAL44 - VSE-7025 (MODIFIED)\nSDES2VALCRTCLIN1 - VSE-7025 (MODIFIED)\nSDES2VVSJSON - VSE-6499 (NEW)\nSDESCANAPPT2 - VSE-7008 (MODIFIED)\nSDESCANCELAPPTS - VSE-7008 (MODIFIED)\nSDESCCAVAIL - VSE-7076 (MODIFIED)\n\n
\nVSE Increment 9.1 - SD*5.3*873\n in the SDES2 namespace to address sensitive patient records.\nVSE-6848: BF - SDES2 Priority 35: Rewrite SDES GET APPT REQ LIST BY DFN, \n SDES GET CONSULTS BY DFN, SDES GET CONSULTS BY IEN, SDES GET\n APPT REQ BY DFN, and SDES GET APPT REQ BY IEN in the SDES2\n namespace to address sensitive patient records.\nVSE-6887: JS - VistA: Modify SDEC and SDES code to return an error when \n MRTC child request has a duplicate PID.\nVSE-7118: BB - VistA: Modify SDES GET APPT REQ RPCs to return child \n sequence field.\nVSE-7306: LB - VistA: Modify SDES2 GET CONTACT ATTEMPTS to quit out when \n==============================\n no contact is found.\nVSE-7451: BF - VistA: Modify SDES2 QUERY APPT REQUESTS and associated \n SDES2 RPCs\nVSE-7465: BB - VistA: Fix issue with SDES2 CREATE APPOINTMENT where \n Inpatients are not idenified\nVSE-7466: BB - VistA: Fix issue with SDES2 CANCEL CLINC AVAIL to prevent \n <UNDEFINED> error\n \nFiles:\n======\n \n \n \nOptions:\n======== \nSDECRPC - VSE-6837, VSE-6483\nSDESRPC - VSE-6483, VSE-6848, VSE-6837\n \nRoutines:\n=========\nSDEC08 - VSE-6887 (MODIFIED)\n \nSDES2ARCLOSE - VSE-7118 (MODIFIED)\nSDES2CANCELAPPT - VSE-6887/7118 (MODIFIED)\nSDES2CONTACTS - VSE-7306\nSDES2EDITAPREQ - VSE-6887 (MODIFIED)\nSDES2GETAPPTREQ - VSE-6848/7118/7451 (NEW)\nSDES2GETAPPTRPCS - VSE-6483\nSDES2GETCONSULTS - VSE-6848/7451 (NEW)\nSDES2GETRECALL - VSE-6848/7451 (MODIFIED)\nSDES2GETREGS - VSE-6837 (NEW)\nSDES2GETREQS - VSE-6848/7451 (NEW)\nJira Tickets:\nSDES2UTIL1 - VSE-6837 (MODIFIED)\nSDESCANAPPT2 - VSE-6887 (MODIFIED)\nSDESEDITAPPTREQ - VSE-6887 (MODIFIED)\nSDESEDITAPREQVAL - VSE-6887 (NEW)\nSDESGETAPPTREQ - VSE-7118 (MODIFIED)\nSDESGETREQWRAPPR - VSE-7118 (MODIFIED)\nSDES2CREATEAPPT - VSE-7465 (MODIFIED) \nSDES2CANCLNAVAIL - VSE-7466 (MODIFIED)\nSDES2QRYAPREQS - VSE-7451 (MODIFIED)\nSDES2QRYAPREQSB - VSE-7451 (MODIFIED)\n=============\n \nRemote Procedure Call:\n======================\nSDES2 GET APPT REQ BY DFN - VSE-6848/7451 (NEW)\nSDES2 GET APPT REQ BY IEN - VSE-6848/7451 (NEW)\nSDES2 GET APPT REQ LIST BY DFN - VSE-6848/7451 (NEW)\nSDES2 GET APPTS BY CLN RES IEN - VSE-6483 (NEW)\nSDES2 GET CONSULT BY IEN - VSE-6848/7451 (NEW)\nSDES2 GET CONSULTS BY DFN - VSE-6848/7451 (NEW)\nSDES2 GET PATIENT REGISTRATION - VSE-6837 (NEW)\nVSE-6483: LB - SDES2 Priority 9: Rewrite SDES GET APPTS BY RESOURCE in \nSDES2 GET RECALL BY IEN - VSE-6848/7451 (MODIFIED)\nSDES2 GET RECALLS BY DFN - VSE-6848/7451 (MODIFIED)\nSDES2 QUERY APPT REQUESTS - VSE-7451 (NEW)\n the SDES2 namespace.\nVSE-6837: TB - SDES2 Priority 32: Rewrite SDES GET PATIENT REGISTRATION2 \n\n
\nVSE Increment 9.2 - SD*5.3*874\n==============================\n \nJira Tickets:\n=============\nVSE-6618: MD - VistA: FY 24 Mid-Year Stop Code Changes.\n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*863.\n\n
\nStop Codes to be updated in accordance with the MCAO FY24 (April 2024) \nUpdates: \n \nStop Code 355 - Headache Center of Excellence (HCoE) is in the SD TELE\nHEALTH STOP CODE FILE file (#40.6).\n \nStop Code 656 - DoD Non-VA Care is not in the SD TELE HEALTH STOP CODE \nFILE file (#40.6).\n\n
\nVSE Increment 9.2 - SD*5.3*875\nVSE-7115: BB - VistA - Modify the appointment request object to return \nSDESMISSIONAVL - VSE-7140 (Modified)\nSDESRECALLREQ - VSE-7552 (Modified)\n \n \nRemote Procedure Call:\n======================\nSDES CREATE APPT REQ - VSE-7647 (Modified)\nSDES EDIT APPT REQ - VSE-7647 (Modified)\nSDES GET APPT REQ BY IEN - VSE-7115 (Modified)\nSDES GET APPT REQ BY PAT ALL - VSE-7115 (Modified)\n last 4 of SSN\nSDES GET APPT REQ BY PAT OPEN - VSE-7115 (Modified)\nSDES GET APPT REQ BY PATIENT - VSE-7115 (Modified)\nSDES GET APPT REQ BY TYPE VET - VSE-7115 (Modified)\nSDES GET APPT REQ LIST BY DFN - VSE-7115 (Modified)\nSDES GET APPT REQS BY IENS2 - VSE-7115 (Modified)\nSDES GET APPTREQ BY INST - VSE-7115 (Modified)\nSDES GET APPTREQ BY INST2 - VSE-7115 (Modified)\nSDES GET CLINICS BY CLIN LIST - VSE-7384 (Modified)\nSDES GET CONSULTS BY DFN - VSE-7115 (Modified)\nSDES GET CONSULTS BY IEN - VSE-7115 (Modified)\nVSE-7140: AP - VistA - Modify SDES GET MISSION ACT AVAIL to return the \nSDES GET MISSION ACT AVAIL - VSE-7140 (Modified)\nSDES GET RECALL BY IEN - VSE-7115 (Modified)\nSDES GET RECALLS BY DFN - VSE-7115 (Modified)\nSDES SEARCH CLINIC - VSE-7413 (Modified)\nSDES2 BLOCK AND MOVE - VSE-7683 (Modified)\nSDES2 BLOCK PBSP SLOTS - VSE-7091 (New)\nSDES2 CREATE APPT REQ - VSE-7512, VSE-7647 (Modified)\nSDES2 EDIT APPT REQ - VSE-7647 (Modified)\nSDES2 GET URGENCY LIST - VSE-7513 (New)\nSDES2 QUERY APPT REQUESTS - VSE-7525 (Modified)\n Provider ID, and clinic timezone\nSDES2 SEARCH CLINIC ATTRIBUTES - VSE-7046 (Modified)\nVSE-7288: MD - VistA - Create a cross-reference for the field, PBSP ID , \n in the HOSPITAL LOCATION file\nVSE-7384: BF - VistA - Modify SDES GET CLINICS BY CLIN LIST to return the \n properly formatted JSON\nVSE-7413: LB - VistA - Modify SDES SEARCH CLINIC\nVSE-7470: LB - VistA - Modify SDES2 UNDO NOSHOW to only close the parent \n==============================\n when all children requests are closed\nVSE-7485: BB - VistA - Modify SDES2 EDIT CLINIC so that the Proxy user \n (SDESOITEAS,SRV) is able to modify the privileged user\nVSE-7495: BF - VistA - Modify SDES2 QUERY APPT REQUESTS RPC to update the \n wait time calculation for recalls\nVSE-7510: LB - VistA - Modify SDES2 GET APPTS BY CLINIC IEN to return an \n error message instead of a hard error\nVSE-7512: TB - VistA - Update SDES2 CREATE APPT REQ to recognize when the \n parent request associated with the RTC being created has an\n ORDER ID\n \nVSE-7513: BF - VistA - Rewrite SDECRMG2 URGENCY into the SDES2 namespace\nVSE-7525: BF - VistA - Modify SDES2 QUERY APPT REQUESTS RPC to change the \n input parameter to accept the AMIS stop code and convert\n the AMIS stop code to the stop code IEN for filtering\n records\nVSE-7529: TB - VistA - SDEC07 Error: invalid provider ID when trying to \n schedule Recall (PtCSch) appointment\nVSE-7550: BB - VistA - Modify SDEC and SDES2 code to not re-sequence the \n MRTC children on a cancel where the cancellation reason\n does not reopen the children.\n \nVSE-7552: JS - VistA - Modify SDES2 NO-SHOW RPC to add a flag that will \n identify the No-Show as a Recall Appt as opposed to a\n regular appt\nVSE-7553: LB - VistA - Modify SDES2 DISPOSITION APPT REQ RPC logic to\n store SDDUZ when calling into the HL7 logic\nVSE-7554: JS - VistA - Modify SDES2 CREATE APPOINTMENT RPC to fulfill the \n parent when all children are dispositioned\nVSE-7558: TB - VistA - Modify SDES2APPTUTIL to convert FM date to NET \n date before calling REQSET^SDEC07A\nVSE-7647: JS - VistA: Modify SDES2 CREATE APPT REQUEST and SDES Versions \nJira Tickets:\nVSE-7660: LB - VistA: Update SDES2 CANCEL CLINIC AVAILABILITY to quit out \n when DATETIME greater than or equal to ENDDATETIME\nVSE-7662: DR - VistA: Update data dictionary to allow length of Appt up \n to 240\nVSE-7667: TB - Modify SDES2 CREATE APPOINTMENT\nVSE-7683: BB - VistA: Rewrite SDES BLOCK AND MOVE in the SDES2 namespace\n \n \nFiles:\n======\n=============\n44 - PBXP X-ref - VSE-7288 (New)\n409.84 - LENGTH OF APPT - VSE-7662 (Modified)\n409.93 - ERROR FILE - VSE-7091 (Modified)\n \n \nOptions:\n======== \nSDESRPC - VSE-7091,VSE-7513 \n \nRoutines:\nVSE-7046: JS - VistA - Modify SDES2 SEARCH CLINIC ATTRIBUTES RPCs to \n=========\nSDEC07 - VSE-7529 (Modified)\nSDEC08 - VSE-7550 (Modified)\nSDECHL7 - VSE-7553 (Modified)\nSDES01C - VSE-7413 (Modified)\nSDES2APPTUTIL - VSE-7558 (Modified)\nSDES2ARCLOSE - VSE-7553 (Modified)\nSDES2BLOCKANDMOV - VSE-7683 (New)\nSDES2BLOCKPBSP - VSE-7091 (New) \nSDES2CANCELAPPT - VSE-7550 (Modified)\n return active flag for providers and prohibited clinic flag\nSDES2CANCLNAVAIL - VSE-7660 (Modified)\nSDES2CLNSEARCH - VSE-7046 (Modified)\nSDES2CREATEAPPT - VSE-7667 (Modified)\nSDES2CRTAPREQ - VSE-7512, VSE-7647 (Modified) \nSDES2EDITAPREQ - VSE-7512, VSE-7554, VSE-7647 (Modified)\nSDES2GETAPPTRPCS - VSE-7510 (Modified)\nSDES2GETURGENCY - VSE-7513 (New)\nSDES2QRYAPREQS - VSE-7513, VSE-7525 (Modified)\nSDES2QRYAPREQSA - VSE-7513 (Modified)\nSDES2QRYAPREQSB - VSE-7513 (Modified)\nVSE-7091: BB - VistA - Create an RPC to block PBSP clinic availability\nSDES2NOSHOW - VSE-7552 (Modified)\nSDES2RSTCAVAIL - VSE-7528 (Modified)\nSDES2UNDONOSHOW - VSE-7470 (Modified)\nSDES2VAL200 - VSE-7485 (Modified)\nSDESCREATEAPPREQ - VSE-7647 (Modified)\nSDESEDITAPPTREQ - VSE-7554, VSE-7647 (Modified)\nSDESGETAPPTREQ - VSE-7115 (Modified)\nSDESGETCLINSIEN - VSE-7384 (Modified)\nSDESGETCONSULTS - VSE-7115 (Modified)\nSDESGETRECALL - VSE-7115 (Modified)\n\n
\n \nVSE-6995: ME - VistA: SCMCMHTC routine needs to be remediated\nSDES2INACTCLIN - VSE-7362 (Modified)\nSDES2QRYAPREQS - VSE-7665 (MODIFIED)\nSDES2QRYAPREQSB - VSE-7665 (MODIFIED)\nSDES2REACTTCLIN - VSE-7362 (Modified)\nSDES2SETCHECKOUT - VSE-7594 (Modified)\nSDES2STOREPAT - VSE-7699 (MODIFIED)\nSDES2UNBLOCKPBSP - VSE-7171 (NEW) \nSDES2UNDOCHKOUT - VSE-7630 (NEW)\nSDES2UTIL - VSE-7664 (MODIFIED)\nSDESCANAPPT2 - VSE-7389 (MODIFIED)\nVSE-7171: BB - VistA: Create a new RPC to unblock PBSP clinic availability\nSDESCLINPRECAN - VSE-7514 (MODIFIED)\nSDESCREATEAPPT - VSE-7389, VSE-7684, VSE-7700 (MODIFIED)\nSDESCREATEAPPT44 - VSE-7789 (MODIFIED)\nSDESCRTAPPTWRAP - VSE-7700 (MODIFIED)\nSDESEDITAPPTREQ - VSE-7601, VSE-7700 (MODIFIED)\nSDESGETCONSULTS - VSE-7389 (MODIFIED)\nSDESGETPATINQUIR - VSE-7711 (MODIFIED)\nSDESPROVSEARCH - VSE-7649 (MODIFIED)\nSDESRECALLREQ - VSE-7682 (MODIFIED)\nSDESRECPROCSRCH - VSE-7657 (MODIFIED)\nVSE-7362: MD - VistA: Modify SDES2 INACTIVATE CLINIC RPC and SDES2 \nSDESUTIL - VSE-6810 (MODIFIED)\nSDMHPRO1 - VSE-6642 (Modified)\nSDUPDATECONSPID - VSE-7389 (NEW)\n \n \nRemote Procedure Call:\n======================\nSDES CANCEL CLIN PRECAN LIST - VSE-7514 (MODIFIED)\nSDES CREATE APPOINTMENTS - VSE-7700 (MODIFIED)\nSDES GET PATIENT INQUIRY - VSE-7711 (MODIFIED)\n REACTIVATE RPC to allow the user to modify the date that the\nSDES SEARCH PROVIDERS - VSE-7649 (MODIFIED)\nSDES2 CREATE APPOINTMENT - VSE-7700 (MODIFIED)\nSDES2 CREATE SPEC NEEDS PREFS - VSE-7469 (MODIFIED)\nSDES2 EDIT PAT DEMOGRAPHICS - VSE-7701 (NEW)\nSDES2 EDIT SPEC NEEDS PREFS - VSE-7469 (MODIFIED)\nSDES2 GET APPT BY APPT IEN - VSE-7713, VSE-7853 (MODIFIED)\nSDES2 GET APPT REQ BY DFN - VSE-7690 (MODIFIED)\nSDES2 GET APPT REQ BY IEN - VSE-7690 (MODIFIED)\nSDES2 GET APPT REQ LIST BY DFN - VSE-7690 (MODIFIED)\nSDES2 GET APPTS BY APPT IENS - VSE-7713, VSE-7853 (MODIFIED)\n clinic is set to be inactivated, even if the clinic date is\nSDES2 GET APPTS BY CLINIC IEN - VSE-7713, VSE-7853 (MODIFIED)\nSDES2 GET APPTS BY CLN RES IEN - VSE-7713, VSE-7853 (MODIFIED)\nSDES2 GET APPTS BY PATIENT DFN - VSE-7713, VSE-7853 (MODIFIED)\nSDES2 GET CONSULT BY IEN - VSE-7690 (MODIFIED)\nSDES2 GET CONSULTS BY DFN - VSE-7690 (MODIFIED)\nSDES2 GET DEMOGRAPHICS - VSE-7701 (NEW)\nSDES2 GET PAT DEMOGRAPHICS - VSE-7701 (NEW)\nSDES2 GET PATIENT EP - VSE-7595 (MODIFIED)\nSDES2 GET RECALL APPT TYPES - VSE-7823 (NEW)\nSDES2 GET RECALL BY IEN - VSE-7690 (MODIFIED)\n already set to be inactivated\nSDES2 GET RECALLS BY DFN - VSE-7690 (MODIFIED)\nSDES2 GET REQUESTS BY INST - VSE-7447, VSE-7690 (MODIFIED)\nSDES2 GET SPEC NEEDS PREFS - VSE-7469 (MODIFIED)\nSDES2 QUERY APPT REQUESTS - VSE-7665 (MODIFIED)\nSDES2 UNBLOCK PBSP SLOTS - VSE-7171 (NEW)\nSDES2 UNDO CHECKOUT - VSE-7630 (NEW)\n \n \nProtocol:\n=========\nVSE-7389: BB - VistA: Update CID when provider changes the CID in CPRS\nGMRC EVSEND OR VSE-7389 (MODIFIED)\nSD PID/CID UPDATE OR VSE-7389 (NEW)\nVSE-7447: BF - VistA: Identify and change the SDES2 routines that are \n calling GETREQUEST^SDESGETAPPTREQ, and 2 others to call the new\n SDES2 versions of these routines\n \n SPEC NEEDS to allow remarks for each preference\nVSE-7469: BB - VistA: Modify SDES2 CREATE SPEC NEEDS PREFS and SDES2 EDIT\n SPEC NEEDS to allow remarks for each preference\nVSE-7514: MB - VistA: Modify SDES CANCEL CLIN PRECAN LIST RPC to work\n during a date range and return all the appointments within it\nVSE-7594: LB - VistA: Update User DUZ in file 409.68 and the VISIT file\nVSE-7595: BB - VistA: Modify SDES2 GET PATIENT EP to return the Last\n Disch./Lodger Date\nVSE-7601: AP - VistA: Modify SDES2 CREATE APPOINTMENT to correct the user\n being stored when the request is being dispositioned\nVSE Increment 9.3/9.4 - SD*5.3*877 - GUI v 1.7.55\nVSE-7626: MD - VistA: Modify SDES2 CREATE VET REQ AND APPT RPC to return\n a date instead of a date/time\nVSE-7630: TB - VistA: Add SDES2 UNDO CHECKOUT to the SDESRPC menu option\nVSE-7649: JS - VistA: Modify SDES2 CREATE APPT REQ error message so that \n it says "Provider is inactive"\nVSE-7657: TB - Discovery/Fix issue with Recall provider list not \n including all providers\nVSE-7664: BF - VistA: Modify SDES2UTIL to recognize that there may be \n times when there are both active and inactive AMIS stop codes\nVSE-7665: BF - Vista: Modify SDES2 QUERY APPT REQUESTS to accept a SubType\n \n for APPT appointment request types\nVSE-7682: BB - VistA: Modify SDES2 CANCEL APPOINTMENT to ensure the \n requesting user is stored in the database\nVSE-7684: TB - VistA Discovery and Code 409.84 field .09 should store\n Date and Time\nVSE-7690: JS - VistA: Modify all SDES2 GET REQ RPCs to return the \n telephone number\nVSE-7699: JS - VistA: Modify SDES2 CREATE LAST SELECTED PAT\nVSE-7700: LB - The order file is not being populated correctly when an \n appointment is being created Using an RTC Request\nJira Tickets:\nVSE-7701: BB - VistA: Create a new SDES2 RPC to read demographics data\nVSE-7711: JS - VistA: SDES GET PATIENT INQUIRY is returning full SSN\nVSE-7713: JS - VistA: Add sensitive patient flag to SDES2 GET APPTS BY \n PATIENT DFN\nVSE-7732: LB - SDES2 CREATE APPOINTMENT does not count after hours slot \n correctly\nVSE-7789: TB - Code file 44 APPOINTMENT (field 1900) multiple sub file \n 44.003 - field 8 to store the date and time for when the\n appointment was made\nVSE-7823: BF - VistA: Rewrite SDEC RECAPGET in the SDES2 namespace\n=============\nVSE-7853: BF - Vista: Correct an issue with time zone in expanded entry\n \nFiles:\n======\n409.93 - VSE-7649, VSE-7665, VSE-7701 \n \nOptions:\n======== \nSDESRPC - VSE-7823\n \nVSE-6642: JS - VistA: <SUBSCRIPT>EN+17^SDMHPRO1 at Connecticut/\n \nRoutines:\n=========\nSCMCMHTC - VSE-6995 (MODIFIED)\nSDEC07 - VSE-7389, VSE-7684 (MODIFIED)\nSDEC08 - VSE-7389 (MODIFIED)\nSDEC52B - VSE-7657 (MODIFIED)\nSDECCONSJSON - VSE-7389 (MODIFIED)\nSDES2APPTUTIL - VSE-7389, VSE-7601, VSE-7700 (MODIFIED)\nSDES2BLDAPPT2 - VSE-7713 (MODIFIED)\n West-Haven(689)\nSDES2BLDAPPT44 - VSE-7789 (MODIFIED)\nSDES2BLDAPPTOBJ - VSE-7713, VSE-7853 (MODIFIED)\nSDES2CANCELAPPT - VSE-7389, VSE-7682 (MODIFIED)\nSDES2CREATEAPPT - VSE-7389, VSE-7684, VSE-7700, VSE-7594, VSE-7732 \n VSE-7789 (MODIFIED)\nSDES2CREATESNAPS - VSE-7469 (MODIFIED)\nSDES2CRTAPREQ - VSE-7649 (MODIFIED)\nSDES2CRTVETAPPT - VSE-7626 (MODIFIED)\nSDES2EDITPATDEMO - VSE-7701 (NEW)\nSDES2EDITSNAPS - VSE-7469 (MODIFIED)\nVSE-6810: AP - VistA: Modify logic within SDESUTIL\nSDES2EPT - VSE-7595 (MODIFIED)\nSDES2GETAPPTREQ - VSE-7690 (MODIFIED)\nSDES2GETAPPTRPCS - VSE-7713 (MODIFIED)\nSDES2GETCONSULTS - VSE-7389, VSE-7690 (MODIFIED)\nSDES2GETDEMOS - VSE-7701 (NEW)\nSDES2GETPATDEMO - VSE-7701 (NEW)\nSDES2GETRECALL - VSE-7690 (MODIFIED)\nSDES2GRECAPTYPE - VSE-7823 (NEW)\nSDES2GETSNAPS - VSE-7469 (MODIFIED)\nSDES2GREQSINST - VSE-7447 (Modified)\n\n
\nVSE Increment 9.4 - SD*5.3*878 - GUI v 1.7.56\n Yes/No/NA for IsClassificationActive\nVSE-7666: BF - VistA: Modify SDESUTIL to recognize that there may be \n times when there are both active and inactive AMIS stop\n codes\nVSE-7680: JS - VistA: Create 2 new routines in the SDES2 namespace\nVSE-7692: BB - VistA: Modify SDEC07A routine to rewrite the logic around \n consults\nVSE-7712: BF - VistA: Fix an issue with the query tool \nVSE-7739: BF - VistA: Backup SD PURGE menu option and then remove it \n form the menu\n=============================================\nVSE-7862: BF - VistA: Rewrite SDES GET APPT REQ BY TYPE VET into the SDES2\n namespace\nVSE-7867: TB - VistA: Modify SDES2 ADD CONTACT ATTEMPT and SDES2 GET\n CONTACT ATTEMPTS so that date time entered is in system\n time\nVSE-7869: LB - VistA: Modify SDES2 CANCEL APPOINTMENT RPC to correctly \n update recall request pointers\nVSE-7876: MD - VistA: Update the Privileged User validation in routine \n SDES2VAL44A\nVSE-7943: BF - VistA: Modify SDES2 GET DEMOGRAPHICS to only send active \n \n race and ethnicity values\n \nFiles:\n======\nSDES ERROR CODES \n \nOptions:\n======== \nSD PURGE - VSE-7739 (delete at site)\nSDESRPC - VSE-7862\nJira Tickets:\n \n \nRoutines:\n=========\nSDES2CANCELAPPT - VSE-7869 (modified)\nSDES2CHECKIN - VSE-7680 (modified)\nSDES2CONTACTS - VSE-7631 VSE-7867 (modified)\nSDES2CRTVISIT - VSE-7680 (new)\nSDES2EDITPATDEMO - VSE-7900 (modified)\nSDES2GETAPPTREQ - VSE-7862\n=============\nSDES2GETVISIT - VSE-7680 (new) \nSDES2QRYAPREQSB - VSE-7712 (modified)\nSDES2APPTUTIL - VSE-7692 (modified)\nSDES2EDITPATDEMO - VSE-7943 (modified)\nSDES2GETDEMOS - VSE-7943 (modified)\nSDES2GETXPENTRY2 - VSE-7648 (modified) \nSDES2VAL44A - VSE-7876 (modified) \nSDESUTIL - VSE-7666 (modified)\n \n \n \nRemote Procedure Calls: \n=======================\nSDES2 GET APPT REQ BY TYP VET - VSE-7862 (new)\nVSE-7631: MB - VistA: Modify SDES2 GET CONTACT ATTEMPT RPC to correct an \n issue with the error return \nVSE-7648: AP - VistA: Modify SDES2 GET EXPANDED ENTRY 2 to return \n\n
\nPCMM GUI fixes - This is a combined client server patch. Client software\nis contained in SD_53_51.exe.\n\n
\nVSE Increment 9.7 & 9.8 * 10.0 - SD_5_3_880 - VS GUI 1.7.57\n parameter flag for inactive clinic\nSDES2 GET CANCELLED SLOTS - VSE-7856 (Modified) \nSDES2 GET CLINIC AVAIL BY SVC - VSE-7807 (New)\nSDES2 GET CLINICS BY PROVIDER - VSE-7706 (NEW)\nSDES2 GET PATIENT EP - VSE-7918 (Modified)\nSDES2 GET PAT DEMOGRAPHICS - VSE-7944 (Modified)\nSDES2 GET RESOURCE GROUP - VSE-7707 (Modified)\nSDES2 SEARCH RECALL PROVIDERS - VSE-7911 (NEW)\n \n \nProtocol:\nVSE-7763: AP - VistA: Modification to SDES2 CREATE APPOINTMENT to update \n=========\n MRTC PARENT logic.\n \nJira Tickets 9.8:\n=================\nVSE-7775: TB - Blocked slot reopened on remapping clinic availability.\nVSE-7807: BF - VistA: Create a new RPC to return open availability for a\n given service type\nVSE-7856: JS - VistA: Discovery and Code if possible Modify SDES2 GET \n \n CANCELLED SLOTS RPC so that it also pass back the reason\n that a particular slot was cancelled in the first place\nVSE-7866: AP - VistA: Modify SDES2SETCHECKOUT.INT so that the data we are \n trying to file will pass the input transform\nVSE-7911: TB - VistA: Create an SDES2 version of SDES SEARCH RECALL \n PROVIDER's RPC and change the way search is done\nVSE-7924: LB - VistA: Create a new SDES2 GET APPTS BY CLINIC LIST RPC so \n that it returns back the full "Appointment" object\nVSE-7963: BF - VistA: Modify SDES GET CLINIC STOPCD to add 'Restriction \n Type'\n \nVSE-8049: BB - VistA: Modify SDES2 CANCEL CLINIC AVAILBILITY validation\n to add an equal sign to logic so that it doesn't check the\n next time slot.\n \nJira Tickets 10.0:\n==================\nVSE-7546: FF - VS GUI: Time zone dropdown not working when creating VVC \n appointments\nVSE-7885: BB - VistA: The system is allowing two appointments that are \n converted to the same FileMan date.time to be entered in for a\nJira Tickets 9.7:\n patient\nVSE-7918: MB - VistA: Modify SDES2 GET PATIENT EP RPC to fix a typo \n "uknown"\nVSE-7944: JJ - VistA: Modify SDES2 GET PATIENT DEMOGRAPHICS to update the \n object when there is no race defined\nVSE-7961: BF - VistA: A data clean up is needed to add the "MES" node to \n the clinic for time slots canceled via SDES/SDES2 code.\nVSE-7983: TB - VistA: Fix the logic to prevent <UNDEFINED> error in \n SDESCLNSETAVAIL\nVSE-8061: BB - VistA: Correct logic in SDES2CANCELAPPT to correctly \n=================\n remove all encounters created for an appointment when\n appointment is being cancelled\nVSE-8062: BF - VistA: Correct logic in SDES2 GET APPT REQ BY TYP VET to \n handle SDDUZ and pass it through to the GETREQUEST call\n \nFiles:\n======\n409.93 - VSE-7885 \n \nOptions:\nVSE-7567: LB - VistA: Modify SDES GET APPTS and SDES2 GET APPTS RPCs\n======== \nSDESRPC VSE-7924, VSE-7807\n \nRoutines:\n=========\nSDESGETAPPTRPCS - VSE-7567 (NEW)\nSDES2BLDAPPT2 - VSE-7567 (Modified), VSE-7924\nSDES2BLDAPPT44 - VSE-7567 (Modified)\nSDES2BLDAPPTOBJ - VSE-7567 (Modified)\nSDES2BLOCKANDMOV - VSE-7775 (Modified)\nVSE-7706: TB - VistA: Create an SDES2 version of SDES GET CLINICS BY \nSDES2CANCLNAVAIL - VSE-7775 (Modified)\nSDES2CREATEAPPT - VSE-7763 (Modified) \nSDES2EPT - VSE-7918 (Modified)\nSDES2GETAPPTREQ - VSE-8062 (Modified)\nSDES2GETAPPTRPCS - VSE-7567 (Modified), VSE-7924\nSDES2GETCANSLOTS - VSE-7856 (Modified)\nSDES2GETCLINAVL - VSE-7807 (New)\nSDES2GETRESGROUP - VSE-7707 (Modified)\nSDES2GETPATDEMO - VSE-7944 (Modified)\nSDES2PRVCLINSRC - VSE-7706 (NEW)\n PROVIDER to add an input parameter flag for Inactive Clinic\nSDES2RECPRVSRCH - VSE-7911 (NEW)\nSDES2SETCHECKOUT - VSE-7866 (Modified)\nSDESGETSTOPCD - VSE-7963 (Modified)\nSDES2CANCLNAVAIL - VSE-8049 (Modified)\nSDES2CREATEAPPT - VSE-7885 (Modified)\nSDES2APPTUTIL - VSE-7885 (Modified) \nSDESCLNSETAVAIL - VSE-7983 (Modified)\nSDES2CANCELAPPT - VSE-8061 (Modified)\n \nRemote Procedure Calls:\nVSE-7707: LB - VistA: Modify SDES2 GET RESOURCE GOUP to add an input\n=======================\nSDES GET APPTS BY CLIN IEN 3 - VSE-7567 (Modified) ,VSE-7924\nSDES GET APPTS BY PATIENT DFN3 - VSE-7567 (Modified), VSE-7924\nSDES GET CLINIC STOPCD - VSE-7963 (Modified)\nSDES2 GET APPT BY APPT IEN - VSE-7924 (Modified)\nSDES2 GET APPTS BY APPT IENS - VSE-7924 (Modified)\nSDES2 GET APPTS BY CLINIC IEN - VSE-7924 (Modified)\nSDES2 GET APPTS BY CLINIC LIST - VSE-7924 (NEW)\nSDES2 GET APPTS BY CLN RES IEN - VSE-7924 (Modified)\nSDES2 GET APPTS BY PATIENT DFN - VSE-7924 (Modified)\n\n
\nVSE Increment 10.1 - SD*5.3*881 - GUI v 1.7.58\nVSE-8074: MD - VistA: Update existing SDES2 RPCs so that the ACHERON\n AUDIT ID is in the input parameter description\nVSE-8079: BF - VistA: Update Patient Search RPC to return -1 to 4\nVSE-8080: TB - VistA: Modify create appointment RPCs to change the\n validation on the maximum appointment length from 120 to\n 240\nVSE-8095: MD - VistA: Update SDES GETVVSMAKEINFO JSON and SDES SEARCH \n VVS PROVIDERS JSON so that the APP PROXY ALLOWED field is\n set to Yes\nVSE-8106: JS - VistA: Discovery and fix if possible - figure out why \n \n SDESCLINICAVAIL is not returning back the midnight\n timeslots for the clinic for Monday\nVSE-8156: MD - VistA: Modify SDES GET VISTA DEVICES RPC to be updated to \n return all matches for the search string passed in.\nVSE-8226: BB - VistA: Modify the check in SDES2 CREATE APPOINTMENT RPC to \n verify that appointment is not cancelled\n \nFiles:\n======\n \n \n \nRoutines:\n=========\nSDESGETDEVICES - VSE-8156 (Modified)\nSDES2APPTUTIL - VSE-8226 (Modified)\nSDES2CREATEAPPT - VSE-8080 (Modified)\nSDES2CRTVETAPPT - VSE-8080 (Modified)\nSDES2EDITPATDEMO - VSE-8050 (Modified)\nSDES2GETVISIT - VSE-8080 (Modified)\nSDES2PATSEARCH - VSE-8079 (Modified)\nJira Tickets:\nSDES2RECLLREQ - VSE-8080 (Modified)\nSDESCHKAPPTOVP - VSE-8080 (Modified)\nSDESCLINICAVAIL - VSE-8106 (Modified)\nSDESCREATEAPPT - VSE-8080 (Modified)\nSDESCREATEAPPT44 - VSE-8080 (Modified)\n \nRemote Procedure Call:\n======================\nSDES GET APPT TYPES - VSE-7988 (Modified)\nSDES GET VISTA DEVICES - VSE-8156 (Modified)\n=============\nSDES GETVVSMAKEINFO JSON - VSE-8095 (Modified)\nSDES SEARCH VVS PROVIDERS JSON - VSE-8095 (Modified)\nSDES2 PATIENT SEARCH - VSE-8079 (Modified)\nSDES2 ADD CONTACT ATTEMPT - VSE-8074 (Modified)\nSDES2 BLOCK AND MOVE - VSE-8074 (Modified)\nSDES2 CANCEL CLINIC AVAIL - VSE-8074 (Modified)\nSDES2 CHECK CLIN AVAIL DEFINED - VSE-8074 (Modified)\nSDES2 CREATE CLINIC - VSE-8074 (Modified)\nSDES2 CREATE PROVIDER RESOURCE - VSE-8074 (Modified)\nSDES2 CREATE SPEC NEEDS PREFS - VSE-8074 (Modified)\n \nSDES2 EDIT PAT DEMOGRAPHICS - VSE-8074 (Modified)\nSDES2 EDIT PROVIDER RESOURCE - VSE-8074 (Modified)\nSDES2 EDIT SPEC NEEDS PREFS - VSE-8074 (Modified)\nSDES2 GET APPTS BY CLN RES IEN - VSE-8074 (Modified)\nSDES2 GET CONSULT CLINIC INFO - VSE-8074 (Modified)\nSDES2 GET CONTACT ATTEMPTS - VSE-8074 (Modified)\nSDES2 GET DEMOGRAPHICS - VSE-8074 (Modified)\nSDES2 GET ELIGIBILITY CODES - VSE-8074 (Modified)\nSDES2 GET PATIENT CLIN STATUS - VSE-8074 (Modified)\nSDES2 GET PATIENT INFO - VSE-8074 (Modified)\nVSE-7988: BF - VistA: Create a new appointment type, World War II\nSDES2 GET RESOURCE IEN - VSE-8074 (Modified)\nSDES2 GET SCHEDULING USERS - VSE-8074 (Modified)\nSDES2 GET SPEC NEEDS PREFS - VSE-8074 (Modified)\nSDES2 INACTIVATE CLINIC - VSE-8074 (Modified)\nSDES2 NO-SHOW - VSE-8074 (Modified)\nSDES2 REACTIVATE CLINIC - VSE-8074 (Modified)\nSDES2 RESTORE CLIN AVAIL - VSE-8074 (Modified)\nSDES2 UNDO NO-SHOW - VSE-8074 (Modified)\nVSE-8050: JJ - VistA: Modify SDES2 EDIT PAT DEMOGRAPHICS to fix an\n inconsistent response\n\n
\nVSE Increment 9.8 - SD*5.3*884\nSDESCANCELVVS - VSE-6833 (New)\n \nJira Tickets:\n=============\nVSE-6833: MD - VistA: Create a web service call to cancel VVC appointments\n \nRoutines:\n=========\nSDCNP0 - VSE-6833 (Modified)\n\n
\nJira Tickets Sprint 10.2 - VS GUI 1.7.59 - SD*5.3*885\nVSE-8101: JJ - VistA: Update to SDECAUD for change from date to date.time\nVSE-8172: BF - VistA: Modify SDES2QRYAPREQSA to use the new index, only \n looking at 'open' records. \nVSE-8196: BB - VistA: Wrong PID Is being displayed after cancelling an \n appointment\n \nFiles:\n=========\nHOSPITAL LOCATION (#44) - VSE-8036\nSDEC APPT REQUEST (#409.85) - VSE-8172\n======================================================\nSDES ERROR CODES (#409.93) - VSE-8036\n \nInput Templates:\n================\nSDB - VSE-8036 (MODIFIED)\n \nOptions:\n=========\nSDESRPC - VSE-7966 (MODIFIED)\n \n \nRoutines: \n=========\nSDECAUD - VSE-8101 (MODIFIED)\nSDES2CLINUT - VSE-8036 (MODIFIED)\nSDES2CREATECLIN - VSE-8036 (MODIFIED)\nSDES2EDITCLIN - VSE-8036 (MODIFIED)\nSDES2GETDISPCONS - VSE-7966 (NEW)\nSDES2QRYAPREQSA - VSE-8172 (MODIFIED) \nSDES2VALCRTCLIN1 - VSE-8036 (MODIFIED) \nSDUPDATECONSPID - VSE-8196 (MODIFIED) \nVSE-7966: JS - VistA: Create a new SDES2 RPC to return all contact \n \n \nRemote Procedures:\n==================\nSDEC SUMMGET2 - VSE-8101 (MODIFIED)\nSDES2 CREATE CLINIC - VSE-8036 (MODIFIED)\nSDES2 EDIT CLINIC - VSE-8036 (MODIFIED)\nSDES2 GET DISP CONT ATTEMPTS - VSE-7966 (NEW)\n attempts per patient not per appointment or request\nVSE-8036: BF - VistA: Create a new field for Veteran Self Cancel and add \n create/edit clinic\nVSE-8063: FF - VS GUI: Issue between GUI and ISS when creating and \n editing VVS appointments\n\n
\nJira Tickets Sprint 10.3 - VS GUI 1.7.60 - SD*5.3*886\n discovered defects\nVSE-8187: VistA: BB - DISCOVERY - Identify consecutive blocks of times \n for scheduling bases on predetermined intervals\nVSE-8188: FF - VSE GUI: New PID erroneously entered in original \n appointment\nVSE-8205: TB - VistA: Modify SDES2 GET PATIENT EP to return back an \n external date string for fields that allow no day\nVSE-8250: BF - VistA: Modify SDES2GETSTATUS to fix the status of a \n cancelled inpatient appointment\nVSE-8254: BB - VistA: Modify SDES2 GET PATIENT INFO to use the\n=====================================================\n SDCONTEXT("USER DUZ") to pass into POPULATE^SDES2PATSEARCH\nVSE-8280: BB - VistA: PID not editable when rebooking a cancelled \n appointment and the incorrect status on an inpatient appt\n \nJira Tickets Sprint 10.4 - VS GUI 1.7.60 - SD*5.3*886\n======================================================\n \nVSE-3869: BB - VistA: Modify SDES CREATE APPT BLK AND MOVE to call new \n SDES2 version\nVSE-7395: TB - VistA: Modify SCMSVUT3 routine tag RADMTHD to allow \n \n additional radiation values\nVSE-7967: JJ - VistA: Add an "Other" option to the preference file\nVSE-8038: FF - VS GUI: Determine if veteran has successfully participated \n in a remote visit\nVSE-8143: BF - VistA: Modify SDES CLIN PRECAN to correct date range \n validation\nVSE-8177: TB - VistA: Create a new version of SDES2 GET APPTS BY PATIENT \n DFN and deprecate the current one\nVSE-8197: BF - VistA: Modify SDES2 CANCEL APPOINTMENT to check for a lock \n in the order vs the lock on the patient\nVSE-7951: BF - VistA: Create a new RPC in the SDES2 namespace to get \n VSE-8221: FF - VS GUI: Add "Other" to SNAP\nVSE-8281: BF - VistA: Fix an issue where SDEC APPDEL is sometimes causing\n mis-matched status values in 409.84 and 2.98\nVSE-8300: JS - VistA: Modify SDES2 GET DISP CONT ATTEMPTS to add new \n fields\n \n \nFiles:\n=========\nSDES ERROR CODES - VSE-8067, VSE-8173 (Modified)\n clinics by station number\nSDEC PREFERENCES AND SPECIAL NEEDS - VSE-7967 (Modified) \n \nInput Templates:\n================\n \n \nOptions:\n=========\nSDESRPC - VSE-7951, VSE8067, VSE-8177 \nSDECRPC - VSE-8177\nVSE-7967: JDJ - VistA: Add an "Other" option to the preference file\n \nRoutines: \n=========\nSDEC08A - VSE-8281 (Modified)\nSDECCONSJSON - VSE-8280 (Modified) \nSDES2CANCELPPT - VSE-8197 (Modified)\nSDES2CANCELPPT1 - VSE-8197 (Modified)\nSDES2CANCLNAVAIL - VSE-8173 (Modified)\nSDES2EPT - VSE-8205 (Modified) \nSDES2GETCLNSTA - VSE-7951 (New)\nVSE-8067: JS - VistA: Create a new SDES2 RPC to retrieve clinic data by \nSDES2GETCONSULTS - VSE-8280 (Modified)\nSDES2GETDISPCONS - VSE-8300 (Modified)\nSDES2GETPATINFO - VSE-8254 (Modified) \nSDES2GETSTATUS - VSE-8250 (Modified)\nSDES2SRCHCLNBYSC - VSE-8067 (NEW)\nSDESGETCONSULTS - VSE-8280 (Modified)\nSDES2GETAPPTRPCS - VSE-8177 (Modified)\nSCMSVUT3 - VSE-7395 (Modified)\nSDES2SDECBLKMOVE - VSE-3869 (New) \nSDES2CREATEAPPT - VSE-3869 (Modified) \n division and stop code ranges\n \nRemote Procedures:\n================== \nSDES2 CANCEL CLINIC AVAIL - VSE-8173 (Modified)\nSDES2 GET CLINICS BY STATION - VSE-7951 (New)\nSDES2 GET DISP CONT ATTEMPTS - VSE-8300 (Modified)\nSDES2 SEARCH CLIN BY STOP CODE - VSE-8067 (NEW)\nSDES2 GET APPTS BY PAT DFN2 - VSE-8177 (NEW)\nSDES CREATE APPT BLK AND MOVE - VSE-3869 (Modified)\nVSE-8173: JS - VistA: Modify SDES2 CANCEL CLINIC AVAILABILITY to correct \n\n\nThis patch fixes an issue that causes an error in the VistA error trap\nwhen an appointment for a consult can't be made because the consult status\nis not either active or pending. The appointment is rejected and an HL7 \nNAK message is returned to HSRM, but then the code doesn't quit as it\nshould. As a result, the code continues into a block of code that should\nJnot run and that code results in the error: <UNDEFINED>MAKE+39^SDCCRSEN1\n\n
\nJira Tickets Sprint 10.5 - VS GUI 1.7.61 - SD*5.3*887\nVSE-8234: TB - VistA: Modify $$INACTIVE^SDESUTIL to call \n $$INACTIVE^SDES2UTIL\nVSE-8246: JJ - VistA: Modify SDES2 SEARCH CLINIC ATTRIBUTES to correct\n the empty object name and routine documentation\nVSE-8259: BF - VistA: Modify SDES2 GET CLINIC AVAIL BY SVC to adjust the \n way the Maximum records returned is calculated\nVSE-8402: JS - VistA: Modify SDES2 GET DISP CONT ATTEMPTS to fix an \n erroneous service IEN value\n \nFiles:\n======================================================\n=========\n \n \nInput Templates:\n================\n \n \nOptions:\n=========\n \n \n \nRoutines: \n=========\nSDES2BLDAPPT44 - VSE-8230 (Modified)\nSDES2CLNSEARCH - VSE-8246 (Modified)\nSDES2CONTACTS - VSE-8402 (Modified)\nSDES2GETCLINAVL - VSE-8259 (Modified)\nSDES2GETDISPCONS - VSE-8402 (Modified)\nSDES2PRVCLINSRC - VSE-8228 (Modified)\nSDES2UTIL - VSE-8234 (Modified) \nVSE-8228: JS - VistA: Modify GET CLIN* RPCs to return the new Veteran \nSDESCONTACTS - VSE-8402 (Modified)\nSDESPROVCLINSRCH - VSE-8228 (Modified)\nSDESRTVCLN3 - VSE-8228 (Modified), VSE-8234 (Modified)\nSDESUTIL - VSE-8234 (Modified) \n \nRemote Procedures:\n================== \nSDES ADD/UPDATE CONTACT - VSE-8402 (Modified)\nSDES DISPLAY CONTACT - VSE-8402 (Modified)\nSDES GET CLINIC INFO3 - VSE-8228 (Modified)\n Self Cancel field.\nSDES GET CLINICS BY PROVIDER - VSE-8228 (Modified)\nSDES2 ADD CONTACT ATTEMPT - VSE-8402 (Modified)\nSDES2 GET APPT BY APPT IEN - VSE-8230 (Modified)\nSDES2 GET APPTS BY APPT IENS - VSE-8230 (Modified)\nSDES2 GET APPTS BY CLINIC IEN - VSE-8230 (Modified)\nSDES2 GET APPTS BY CLINIC LIST - VSE-8230 (Modified) \nSDES2 GET APPTS BY CLN RES IEN - VSE-8230 (Modified)\nSDES2 GET APPTS BY PAT DFN2 - VSE-8230 (Modified)\nSDES2 GET CLINIC AVAIL BY SVC - VSE-8259 (Modified)\nSDES2 GET CLINICS BY PROVIDER - VSE-8228 (Modified)\nVSE-8230: JS - VistA: Add Veteran self-cancel to the clinic object \nSDES2 GET CONTACT ATTEMPTS - VSE-8402 (Modified)\n returned by SDES2 GET APPT* RPC's\nVSE-8231: JS - VistA: Create a post-install routine that will set the \n Veteran self-cancel flag for clinics\n\n
\nJira Tickets Sprint VSE Increment 10.5 - SD*5.3*883\n================\n \nOptions:\n=========\n \nRoutines: \n=========\nSDES883P - VSE-7865 (New)\n \nRemote Procedures:\n===================================================\n================== \n \nVSE-7865: MD - VistA: FY25 Stop Code Changes\n \nFiles:\n=========\n \nInput Templates:\n\n
\nJira Tickets Sprint 10.6 - VS GUI 1.7.62 - SD*5.3*889\nVSE-8367: BF - VistA: Correct issues in the SDEC appointment request file\nVSE-8472: BF - VistA: Modify SDESCLINICAVAIL so that it calls the existing\n function $$GETRES^SDES2UTIL1\nVSE-8509: BB - VistA: Modify SDES2 NO-SHOW to update the contact attempt \n with the new Appointment request IEN\n \n \nFiles:\n=========\n409.85 - VSE-8367 (modified) \n======================================================\n409.93 - VSE-8000 (modified)\n \nInput Templates:\n================\n \nOptions:\n=========\nSDESRPC - VSE-7997\n \nRoutines: \n \n=========\nSDES2BLOCKANDMOV - VSE-8509 (Modified)\nSDES2GETREGS - VSE-8348 (Modified)\nSDES2NOSHOW - VSE-8012 (Modified)\nSDES2SEARCHRCLN - VSE-7997 (New)\nSDESCLINICAVAIL - VSE-8472 (Modified)\nSDESSEARCHRCLN - VSE-7997 (Modified)\n \nRemote Procedures:\n================== \nVSE-7997: JJ - VistA: Modify SDES SEARCH RECALL CLINICS to remove a\nSDES2 SEARCH RECALL CLINICS - VSE-7997 (New)\n trailing blank on a 3 character search string\nVSE-8012: MD - VistA: Modify SDES2 NO SHOW to update the contact attempt\n with the new Appointment request IEN\nVSE-8348: JS - VistA: Modify SDES2 GET PATIENT REGISTRATION to fix \n Category8GFlag field that is incorrect\n\n
\nThe description of this build can be found in the National Patch Module \nunder SD*5.3*888.\n\n
\nRefer to National Patch Module for details\n\n
\n \n message for inactive users for all User Profile RPCs.\nVSE-8406: BF - VistA: Create a new RPC that sends back the set of code \n stored in the HOSPITAL LOCATION (#44) file, SERVICE (#9) field\n and the description for those codes\nVSE-8408: BF - VistA: Create a Post init routine that would compare the \n Gold Standard for HOSPITAL LOCATION (#44), SERVICE (#9) field\nVSE-8409: BF - VistA: lock down File 44 to prevent third party changes to \n the file\nVSE-8610: JDJ - VistA: PtCSch request creation failed: Modify SDES2 CREATE\n RECALL REQUEST to correct and error with APPOINTMENT TYPE\nJira Tickets Sprint 10.7 - VS GUI 1.7.63 - SD*5.3*890\n \n \nJira Tickets Sprint 11.1 - VS GUI 1.7.63 - SD*5.3*890\n======================================================\nVSE-8441: BF - VistA: Add new text field DUPLICATE REASON to the SDEC\n APPT REQUEST file\nVSE-8478: TB - VistA: Modify SDES2 INACTIVATE CLINIC to check to see if \n there is a current reactivate date on the clinic that is less\n than or equal to the passed in inactivate date\nVSE-8728: LB - VistA: Modifications to SDES2APPTUTIL to fix a leaking \n======================================================\n variable\n \nFiles:\n=========\nSDEC APPT REQUEST (#409.85) - VSE-8441 (Modified)\nSDES ERROR CODES (#409.93) - VSE-8441,VSE-7980,VSE-8000 (Modified) \n \nInput Templates:\n================\n \n \nOptions:\n=========\nSDESRPC - VSE-8310,VSE-8406,VSE-8000 (Modified)\n \nRoutines:\n========= \nSDES2APPTUTIL - VSE-8728 (Modified)\nSDES2CRTCLNAVAIL - VSE-8000 (New)\nSDES2EDITAPREQ - VSE-8441 (Modified)\nSDES2EDITCLIN - VSE-7980 (Modified)\nVSE-7980: BB - VistA: Support re-opening length of appointment field as \nSDES2GETAPPTREQ - VSE-8441 (Modified)\nSDES2GETCLINSVC - VSE-8406 (New)\nSDES2GETREQS - VSE-8441 (Modified)\nSDES2GETUSRPROF - VSE-8310 (New)\nSDES2INACTCLIN - VSE-8478 (Modified) \nSDES2PROVSEARCH - VSE-8310 (New)\nSDES2RECLLREQ - VSE-8610 (Modified)\nSDES2UTIL1 - VSE-8000 (Modified)\nSDES2VAL44 - VSE-7980 (Modified)\nSDES2VALCRTCLIN1 - VSE-7980 (Modified)\n needed\nSDESGETUD - VSE-8310 (Modified)\n \n \nRemote Procedures: \n================== \nSDES GET USER PROFILE BY DUZ - VSE-8310 (Modified)\nSDES GET USRPROFILE - VSE-8310 (Modified)\nSDES2 CREATE CLINIC AVAIL - VSE-8000 (New)\nSDES2 CREATE RECALL REQUEST - VSE-8610 (Modified)\nSDES2 EDIT APPT REQ - VSE-8441 (Modified)\nVSE-8000: BB - VistA: Keep previously canceled timeslots in place when \nSDES2 GET APPT REQ BY DFN - VSE-8441 (Modified)\nSDES2 GET APPT REQ BY IEN - VSE-8441 (Modified)\nSDES2 GET APPT REQ BY TYP VET - VSE-8441 (Modified)\nSDES2 GET APPT REQ LIST BY DFN - VSE-8441 (Modified)\nSDES2 GET CONSULT BY IEN - VSE-8441 (Modified)\nSDES2 GET CONSULTS BY DFN - VSE-8441 (Modified)\nSDES2 GET RECALL BY IEN - VSE-8441 (Modified)\nSDES2 GET RECALLS BY DFN - VSE-8441 (Modified)\nSDES2 GET REQUESTS BY INST - VSE-8441 (Modified)\nSDES2 GET SERVICES FOR CLINICS - VSE-8406 (New)\n overwriting new clinic availability\nSDES2 GET USER PROF BY SECID - VSE-8310 (New)\nSDES2 GET USER PROFILE BY DUZ - VSE-8310 (New)\nSDES2 SEARCH PROVIDERS - VSE-8310 (New)\nVSE-8310: JS - VistA: Write 3 RPCs into SDES2 namespace and return error \n\n
\nThe code flow in routine SCMCWS1 is changed. After the first query to \nof DFN to find assignments. Any positive results from the secondary query \nusing the ICN would be any remote assignments. The remote assignments \nfound in PCMM will added to the Outpatient Profile File (#404.41), CPRS PC\nWINDOW CACHE Field (#.07), and displayed in the CPRS PCMM Details Popup \nwindow. If the secondary query using the ICN does not return results then \n"no remote assignments" will be added to the Outpatient Profile File \n(#404.41), CPRS PC WINDOW CACHE Field (#.07) and displayed in the CPRS\nPCMM Details Popup\n \nThe CPRS PCMM HEADER and the CPRS PCMM DETAIL Popup window display \nPCMM is unsuccessful using the DFN and Site number. The SCVALUE variable \nmessage will be changed to better reflect no PACT assignments. If there \nare no results from the secondary query. The CPRS PCMM Header currently \ndisplays the message "No PACT assigned at any VA location". This default \ninformation comes from routine SCMCSW1 and will be changed to "No PACT \nassigned at this VA location(Click for more) ". The CPRS PCMM Details \npopup will reflect "There is no local or remote assignment for this \npatient at this time. Please contact local PCMM Coordinator to\nreview." \nwill be returned as false. Then the current ICN on file in VistA for the \npatient is found and sent to PCMM for other PACT assignments. These will \nlikely be remote assignments and will be stored in the Outpatient Profile \nFile(#404.41), CPRS PC WINDOW CACHE Field (#.07) . If nothing is found \nusing the ICN the SCVALUE variable is returned as false and the popup \nreflects.\nA secondary query will use the Integration Control Number (ICN) instead \n\n
\nJira Tickets Sprint 11.2 - VS GUI 1.7.62 - SD*5.3*893\nVSE-8614: MB - VistA: WWII Appointment Type is showing as non-billable\nVSE-8723: BF - VistA: Fix an issue with user erroneously receiving \n "Patient has an appointment at this time in another time \n zone.\nVSE-8799: BB - VistA: Update SDES2 CANCEL CLIN AVAILABILITY to cancel \n appointments before cancel availability\n \nFiles/Fields:\n=============\n#44 - Sub-file #44.1902 - VSE-8448 (New)\n======================================================\n - Sub-file field #.01\n - Sub-file field #.02\n \n#409.84 - Field #1 - VSE-8567 (Modified)\n Sub-file #409.847 - VSE-8567 (New)\n \n#409.85 - Field #25 - VSE-8567 (Modified)\n Sub-file #409.8527 - VSE-8567 (New)\n \n \n \nInput Templates:\n================\n \n \nOptions:\n=========\nSDESRPC - VSE-8567 (Modified), VSE-8574 (Modified) \n \nRoutines:\n=========\nVSE-8448: BB - VistA: Need Full Day Cancel Reason text to be returned \nSDC - VSE-8448 (Modified)\nSDEC07 - VSE-8567 (Modified)\nSDEC26 - VSE-8567 (Modified)\nSDECAR2 - VSE-8567 (Modified)\nSDECAR3 - VSE-8567 (Modified)\nSDES2APPTUTIL - VSE-8723 (Modified)\nSDES2BLDAPPTOBJ - VSE-8567 (Modified)\nSDES2CANCLNAVAIL - VSE-8448/8449 (Modified)\nSDES2CLININFO - VSE-8574 (New)\nSDES2CREATEAPPT - VSE-8567 (Modified)\n from VSE\nSDES2CREATECLIN - VSE-8574 (Modified)\nSDES2CRTAPREQ - VSE-8567 (Modified)\nSDES2EDITAPPT - VSE-8567 (New)\nSDES2EDITAPREQ - VSE-8567 (Modified)\nSDES2EDITCLIN - VSE-8574 (Modified)\nSDES2GETAPPTREQ - VSE-8567 (Modified)\nSDES2GETCANSLOTS - VSE-8448/8449 (Modified)\nSDES2RSTCAVAIL - VSE-8448 (Modified)\nSDES2VAL44A - VSE-8574 (Modified)\nSDES2VALCRTCLIN1 - VSE-8574 (Modified)\nVSE-8449: BB - VistA: need to remove language seen in the Add/Modify pop \nSDESEDITAPPT - VSE-8567 (Modified) \nSDUNC - VSE-8448 (Modified)\n \n \nRemote Procedures:\n==================\nSDES2 EDIT APPOINTMENT - VSE-8567 (New)\nSDES2 GET APPT BY APPT IEN - VSE-8567 (Modified)\nSDES2 GET APPT REQ BY DFN - VSE-8567 (Modified)\nSDES2 GET APPT REQ BY IEN - VSE-8567 (Modified)\n up modal window "Cancelled Until xxxxxxx.xxx"\nSDES2 GET APPT REQ BY TYP VET - VSE-8567 (Modified)\nSDES2 GET APPT REQ LIST BY DFN - VSE-8567 (Modified)\nSDES2 GET APPTS BY APPT IENS - VSE-8567 (Modified)\nSDES2 GET APPTS BY CLINIC IEN - VSE-8567 (Modified)\nSDES2 GET APPTS BY CLINIC LIST - VSE-8567 (Modified)\nSDES2 GET APPTS BY CLN RES IEN - VSE-8567 (Modified)\nSDES2 GET APPTS BY PAT DFN2 - VSE-8567 (Modified)\nSDES2 GET APPTS BY PATIENT DFN - VSE-8567 (Modified)\nSDES2 GET CLINIC INFO - VSE-8574 (New)\nSDES2 GET CLINICS BY CLIN LIST - VSE-8574 (New)\nVSE-8567: JS - VistA: User Comment Tracking\nVSE-8574: TB - VistA: Modify the new VET SELF CANCEL flag\n\n
\nJira Tickets Sprint 11.3 - SD*5.3*895\nVSE-8674: JJ - VistA: Modify SDES2BLDAPPT44 to prevent ISS from failing \nSDES2VALCRTCLIN1 - VSE-8451 (Modified) \nSDES896P - VSE-8781,VSE-8885 (New)\nSDESAPPTLETTERS - VSE-8704 (Modified)\nSDESCLNSEARCH - VSE-8451 (Modified)\nSDESRTVCLN3 - VSE-8451 (Modified)\nSDM4 - VSE-6586 (Modified)\nSDRRISRU - VSE-8933 (Modified) \n \nRemote Procedure Call:\n======================\n when pulling up the patient appointments.\n \nSDEC PREFGET - VSE-8649 (Modified)\nSDEC PREFSET - VSE-8649 (Modified)\nSDES GET CLINIC INFO3 - VSE-8451 (Modified)\nSDES SEARCH CLINIC ATTRIBUTES - VSE-8451 (Modified)\nSDES2 CREATE CLINIC - VSE-8451 (Modified)\nSDES2 EDIT CLINIC - VSE-8451 (Modified)\nSDES2 GET CLINIC INFO - VSE-8451 (Modified)\nSDES2 GET RECALL BY IEN - VSE-8933 (Modified)\nSDES2 GET RECALLS BY DFN - VSE-8933 (Modified)\nVSE-8726: BB - Vista: SDES2 BLOCK AND MOVE erroneously returns back the \nSDES2 PRINT APPT LETTER - VSE-8704 (New)\nSDES2 PRINT APPT LETTERS - VSE-8704 (New)\nSDES2 QUERY APPT REQUESTS - VSE-8672 (Modified)\nSDES2 SEARCH CLINIC ATTRIBUTES - VSE-8451 (Modified) \n error: "Cannot block and move from slots that originated\n with more than 1 available appointment slot"\nVSE-8732: LB -VistA: User information being sent in the SDCONTEXT array \n is finding issues with the ASECID cross reference \n \n \nJira Tickets Sprint 11.4 - SD*5.3*896\n======================================================\n=====================================\n \nVSE-6586: MD - VistA: Modify SDAMEP1, SDAMEP2, and SDM4 routines to \n include a call to PXCOMPACT\nVSE-8451: JS - VistA: Create a sub specialty and a sub sub specialty\nVSE-8704: TB - VistA: Create SDES2 PRINT APPT LETTER and SDES2 PRINT APPT \n LETTERS to send parts of the letter\nVSE-8802: BB - VistA: DATA CLEAN UP - "Update SDES2 CANCEL CLIN\n AVAILABILITY to cancel appointments before cancel availability"\nVSE-8885: JS - VistA: Modify SDEC EDITAPPT, SDES2 EDIT\n \n APPOINTMENT, SDEC ARSET, SDES2 EDIT APPT REQ (User Comment\n tracking - coding change)\nVSE-8933: JS - VistA: Update PtCSch create and edit to audit comments\n \n \nFiles/Fields\n============\n#44 - Field #1 - VSE-8451 (Modified)\n - Sub-file #44.0301 (New)\n - Sub-file #44.0302 (New)\nVSE-8649: TB - VistA: Fix an issue so that GUI and ISS work the same with \n \n#403.5 - Field #.01 - VSE-8933 (Modified)\n - Sub=file #403.57 (New)\n \n#403.56 - Field #.01 - VSE-8933 (Modified)\n - Sub-file #403.58 (New)\n \n#409.8451 - VSE-8649 (Modified)\n \n#409.93 - VSE-8451 (Modified)\n special needs and preferences\n \n#409.94 - VSE-8451 (New)\n \n \nInput Templates:\n================\n \n \nOptions:\n=========\nVSE-8650: FF - VS GUI: User facing change in VS GUI so that SNAP works \nSDESRPC - VSE-8704 (Modified)\n \n \nPost Install:\n=============\nVS GUI - 1.7.62\nVSE-8451\nVSE-8802\nVSE-8885\nVSE-8933 \n the same with GUI and ISS\n \n \nRoutines:\n=========\nSDAMEP1 - VSE-6586 (Modified)\nSDAMEP2 - VSE-6586 (Modified)\nSDEC07 - VSE-8885 (Modified)\nSDEC26 - VSE-8885 (Modified)\nSDEC49 - VSE-8649 (Modified)\nSDEC52A - VSE-8933 (Modified)\nVSE-8672: BF - VistA: Modify SDES2 QUERY APPT REQ to increase the total \nSDECAR2 - VSE-8885 (Modified)\nSDES2APTLETTER - VSE-8704 (New)\nSDES2BLDAPPT44 - VSE-8674 (Modified)\nSDES2BLOCKANDMOV - VSE-8726 (Modified)\nSDES2CLININFO - VSE-8451 (Modified)\nSDES2CLINUT - VSE-8451 (Modified)\nSDES2CLNSEARCH - VSE-8451 (Modified)\nSDES2CREATEAPPT - VSE-8885 (Modified)\nSDES2CREATECLIN - VSE-8451 (Modified)\nSDES2CRTAPREQ - VSE-8885 (Modified)\n number of records searched to 201\nSDES2DISPRECALL - VSE-8933 (Modified)\nSDES2EDITAPPT - VSE-8885 (Modified)\nSDES2EDITAPREQ - VSE-8885 (Modified)\nSDES2EDITCLIN - VSE-8451 (Modified) \nSDES2GETRECALL - VSE-8933 (Modified)\nSDES2GETREQS - VSE-8933 (Modified)\nSDES2QRYAPREQS - VSE-8672 (Modified)\nSDES2RECLLREQ - VSE-8933 (Modified) \nSDES2VAL44A - VSE-8451 (Modified) \nSDES2VALCONTEXT - VSE-8732 (Modified)\n\n
\nJira Tickets Sprint 11.5 - VS GUI 1.7.63 - SD*5.3*895\nVSE-8819: BF - VistA: Modify SDES2 CREATE CLIN AVAILABILITY to add an \n error check\nVSE-8820: FF - VS GUI: Modify the call to SDES GET MISSION ACT ELIG so \n that the system is passing the FileEntryDate date instead of the\n PID date\nVSE-8857: BF - VistA: Modify block and move functionality to allow a \n variable length appointment to be moved to another variable\n length clinic\nVSE-8923: JS - VistA: User is receiving a 500 error when pulling up a \n specific patient and has to restart ISS\n=====================================================\nVSE-8956: JS - VistA: Create a Post install to cleanup control characters\n \n \nFiles:\n======\nSDES ERROR CODES - 409.93\n \n \nInput Templates:\n================\n \n \n \nOptions:\n========\nSDESRPC - VSE-8421 \n \nRoutines:\n=========\nSDES2BLOCKANDMOV (Modified) - VSE-8857 \nSDES2CANCELAPPT (Modified) - VSE-8923\nVSE-8421: BB - VistA: VistA: Create a new RPC to return the consecutive \nSDES2CRTAPREQ (Modified) - VSE-8783 \nSDES2CRTCLNAVAIL (Modified) - VSE-8819\nSDESUTIL (Modified) - VSE-8773\nSDES2UTIL (Modified) - VSE-8773\nSDES2SEARCHSLOTS (New) - VSE-8421\n \nRemote Procedure Call:\n======================\nSDES2 SEARCH CLINIC SLOTS (New) - VSE-8421\nSDES2 CREATE APPT REQ (Modified) - VSE-8783\n timeslots to ISS\nVSE-8773: MB - VistA: Time zone offset issue on last day of daylight\n savings\nVSE-8783: BF - VistA: Modify SDES2 CREATE APPT REQUEST to update the new \n duplicate reason\n\n
\nJira Tickets Sprint 11.7 - VS GUI 1.7.64 - SD*5.3*898\n all clinics IENs in the CLINIC array\nVSE-9045: JS - VistA: Create 3 new SDES2 RPC's - SDES2 CREATE LETTER, \n SDES2 EDIT LETTER and SDES2 DELETE LETTER\nVSE-9067: MB - VistA: The end user is receiving an error when trying to \n schedule in ISS- {"Appointment": {"IEN":""}\nVSE-9071: JS - VistA: Create an SDES2 SEARCH LETTER RPC to return back \n the IEN and names of letters\nVSE-9076: BF - VistA: Block and move error validation\nVSE-9077: TB - VistA: The SDES2 print appointment letters does not print \n a temporary address that is active on a patient record\n===================================================== \n \n \nFiles:\n======\nSDES ERROR CODES - VSE-9045 (620-630)\n - VSE-9071 (631\n \n \nInput Templates:\n================\n \n \n \nOptions:\n========\nSDESRPC - VSE-9045, VSE-9071 \n \nRoutines:\n=========\nSDES2APTLETTER - VSE-9077 (MODIFIED)\nSDES2BLOCKANDMOV - VSE-9076\nVSE-7857: TB - VistA: Return both provider name and title in the clinic \nSDES2CANCLNAVAIL - VSE-8858\nSDES2CLININFO - VSE-7857 & VSE-9000 \nSDES2CLNSEARCH - VSE-7857\nSDES2CREATEAPPT - VSE-9067 (MODIFIED)\nSDES2ENTERLETTER - VSE-9045, VSE-9071 (NEW)\nSDES2GETCLINAVL - VSE-7857 (MODIFIED)\nSDES2REACTTCLIN - VSE-8958 (MODIFIED)\n \n \nRemote Procedure Call:\n object\n======================\nSDES2 CREATE LETTER - VSE-9045 (NEW)\nSDES2 DELETE LETTER - VSE-9045 (NEW)\nSDES2 EDIT LETTER - VSE-9045 (NEW)\nSDES2 GET CLINIC AVAIL BY SVC - VSE-7857 (MODIFIED)\nSDES2 GET CLINIC INFO - VSE-7857 & VSE-9000 (MODIFIED)\nSDES2 GET CLINICS BY CLIN LIST - VSE-7857 (MODIFIED)\nSDES2 SEARCH CLINIC ATTRIBUTES - VSE-7857 (MODIFIED)\nSDES2 SEARCH LETTER - VSE-9071 (NEW)\nVSE-8858: BF - Vista: User is unable to cancel entire day of timeslots for\n a second time.\nVSE-8958: JJ - VistA: Modify SDES2 REACTIVATE CLINIC to allow todays date\nVSE-9000: TB - VistA: Modify SDES2 GET CLINICS BY CLIN LIST to process \n\n\nJira Tickets Sprint 12.1 - SD*5.3*899\n DATE/TIME ENTERED (field 9.5)\nVSE-9281: MB - VistA: Long search strings are sometime erroneously sent \n in and causing a <SUBSCRIPT>error\nVSE-9296: JJ - VistA: Modify SDES2 CREATE CLINIC AVAIL to quit error and \n quit out if length of appointment is missing\nVSE-9340: BF - VistA: Create SDES2 version of SDES GET DIVISION LIST \nVSE-9348: BB - VistA: When multiple clinics are searched the results are \n including incomplete results from the previous clinic.\nVSE-9349: TB - VistA: Last name initial missing from letter\nVSE-9364: LB - VistA: Banner for decommissioning Set Up A Clinic option\n=====================================================\n \nFiles:\n======\n \n \nInput Templates:\n================\n \n \nOptions:\n \n========\nSDESRPC - VSE-9340\nSDBUILD - VSE-9364\n \n \nRoutines:\n=========\nSDES2APTLETTER - VSE-9349 (MODIFIED)\nSDES2BLOCKANDMOV - VSE-9042 (MODIFIED)\nSDES2CREATECLIN - VSE-8975 (MODIFIED)\nVSE-8975: TB - VistA: Modify SDES2CREATECLIN to correctly return an error \nSDES2CRTAPREQ - VSE-9156 (MODIFIED) \nSDES2CRTCLNAVAIL - VSE-9296 (MODIFIED)\nSDES2GETDIVLIST - VSE-9340 (New) \nSDES2PATSEARCH - VSE-9218 (MODIFIED)\nSDES2SEARCHSLOTS - VSE-9348 (MODIFIED)\n \n \nRemote Procedure Call:\n======================\nSDES2 EDIT CLINIC VSE-9024 (MODIFIED)\n when saving the clinic fails \nSDES2 GET DIVISION LIST VSE-9340 (NEW)\nVSE-9024 JV - VistA: Modify the RPC documentation for SDES2 EDIT CLINIC \nVSE-9042: MB - VistA: Blocking and moving without a appointment IEN is \n causing an error\nVSE-9156: JJ - VistA: Modify SDES2 CREATE APPT REQ to update the \n\n
\nJira Tickets Sprint 12.3 - SD*5.3*910\nFiles:\n======\n \n \nInput Templates:\n================\n \n \nOptions:\n========\n=====================================\n \n \nRoutines:\n=========\nSDESUTIL -VSE-9425 (MODIFIED)\nSDES2UTIL -VSE-9425,VSE-9464 (MODIFIED)\n \n \n \nRemote Procedure Call:\n \n======================\nVSE-9425: MB - VistA: Daylight savings date calculated incorrectly for \n March 2026\nVSE-9464: JV - VistA: <MAXNUMBER>GETSUB+5^SDES2UTIL When Conducting a \n Patient Search\n \n \n\n
\nJira Tickets Sprint 12.2 - SD*5.3*901\nVSE-9353: JV - VistA: Update all SDES RPCs for restrictions\nSDES GET APPTREQ BY INST2 - VSE-9353 (Modified)\nSDES GET APPTS BY CLIN IEN 3 - VSE-9353 (Modified)\nSDES GET APPTS BY CLIN LIST2 - VSE-9353 (Modified)\nSDES GET APPTS BY CLINIEN LIST - VSE-9353 (Modified)\nSDES GET APPTS BY IENS2 - VSE-9353 (Modified)\nSDES GET APPTS BY PATIENT DFN3 - VSE-9353 (Modified)\nSDES GET APPTS BY RESOURCE - VSE-9353 (Modified)\nSDES GET AVAIL BY CLIN LIST - VSE-9353 (Modified)\nSDES GET AVAIL BY STOP CODE - VSE-9353 (Modified)\nSDES GET CANCEL REASONS - VSE-9353 (Modified)\nVSE-9356: JC - VistA: Update all SDES2 RPCs for restrictions\nSDES GET CANCMTS - VSE-9353 (Modified)\nSDES GET CHECK-IN STEP - VSE-9353 (Modified)\nSDES GET CHECK-IN STEPS - VSE-9353 (Modified)\nSDES GET CLIN AVAILABILITY - VSE-9353 (Modified)\nSDES GET CLINIC INFO2 - VSE-9353 (Modified)\nSDES GET CLINIC INFO3 - VSE-9353 (Modified)\nSDES GET CLINIC ORIGINAL AVAIL - VSE-9353 (Modified)\nSDES GET CLINIC STOPCD - VSE-9353 (Modified)\nSDES GET CLINIC STORED HASH - VSE-9353 (Modified)\nSDES GET CLINICS BY CLIN LIST - VSE-9353 (Modified)\nVSE-9373: JJ - VistA: Prevent null comment/note audit logs for Create and \nSDES GET CLINICS BY PROVIDER - VSE-9353 (Modified)\nSDES GET COMP/PEN 2507 - VSE-9353 (Modified)\nSDES GET CONSULT DETAILS - VSE-9353 (Modified)\nSDES GET CONSULTS BY DFN - VSE-9353 (Modified)\nSDES GET CONSULTS BY IEN - VSE-9353 (Modified)\nSDES GET DISPOSITION REASONS - VSE-9353 (Modified)\nSDES GET DIVISION LIST - VSE-9353 (Modified)\nSDES GET INSURANCE VERIFY LIST - VSE-9353 (Modified)\nSDES GET INSURANCE VERIFY REQ - VSE-9353 (Modified)\nSDES GET LAST SELECTED PAT - VSE-9353 (Modified)\n Edit Recall/Appt Request and Appointments for SDES/SDES2\nSDES GET LETTER BY IEN - VSE-9353 (Modified)\nSDES GET LETTER TYPES - VSE-9353 (Modified)\nSDES GET LETTERS BY TYPE - VSE-9353 (Modified)\nSDES GET MISSION ACT AVAIL - VSE-9353 (Modified)\nSDES GET MISSION ACT ELIG - VSE-9353 (Modified)\nSDES GET MISSION ACT ELIG FEDT - VSE-9353 (Modified)\nSDES GET PATCH NUMBER - VSE-9353 (Modified)\nSDES GET PATIENT CMMTS - VSE-9353 (Modified)\nSDES GET PATIENT FLAGS - VSE-9353 (Modified)\nSDES GET PATIENT INQUIRY - VSE-9353 (Modified)\nVSE-9384: JV - VistA: Modify SDES2 GET CLINIC AVAIL BY SVC to only return \nSDES GET PATIENT PREF - VSE-9353 (Modified)\nSDES GET PATIENT REGISTRATION2 - VSE-9353 (Modified)\nSDES GET PATIENT WARD - VSE-9353 (Modified)\nSDES GET PATREG BY DFNICN - VSE-9353 (Modified)\nSDES GET RECALL BY IEN - VSE-9353 (Modified)\nSDES GET RECALLS BY DFN - VSE-9353 (Modified)\nSDES GET RESOURCE BY CLINIC - VSE-9353 (Modified)\nSDES GET RESOURCE BY DUZ - VSE-9353 (Modified)\nSDES GET SPEC NEEDS AND PREFS - VSE-9353 (Modified)\nSDES GET STOPCD DETAIL - VSE-9353 (Modified)\n on exact matches\nSDES GET TIU DOC BY CONTEXT - VSE-9353 (Modified)\nSDES GET USER PROFILE BY DUZ - VSE-9353 (Modified)\nSDES GET USRPROFILE - VSE-9353 (Modified)\nSDES GET VISTA DEVICES - VSE-9353 (Modified)\nSDES GET VVS APPT - VSE-9353 (Modified)\nSDES GET VVS ID - VSE-9353 (Modified)\nSDES GETVVSMAKEINFO JSON - VSE-9353 (Modified)\nSDES INACTIVATE/ZZ CLINIC - VSE-9353 (Modified)\nSDES NOSHOW - VSE-9353 (Modified)\nSDES PATIENT SEARCH - VSE-9353 (Modified)\nVSE-9466: LB - VistA: Remove SDES2 GET CONSULT CLINIC INFO from production\nSDES PRINT APPT LETTER - VSE-9353 (Modified)\nSDES PRINT APPT LETTER VISTA - VSE-9353 (Modified)\nSDES PRINT APPT LETTERS - VSE-9353 (Modified)\nSDES PRINT APPT LETTERS VISTA - VSE-9353 (Modified)\nSDES PRINT PATIENT APPTS - VSE-9353 (Modified)\nSDES REACTIVATE CLINIC - VSE-9353 (Modified)\nSDES READ CLINIC GROUP - VSE-9353 (Modified)\nSDES READ PRIV USERS - VSE-9353 (Modified)\nSDES SAVE VVS ID - VSE-9353 (Modified)\nSDES SEARCH CLINIC - VSE-9353 (Modified)\n as it was never released\nSDES SEARCH CLINIC ATTRIBUTES - VSE-9353 (Modified)\nSDES SEARCH CLINIC GRP - VSE-9353 (Modified)\nSDES SEARCH PRIVILEGED USER - VSE-9353 (Modified)\nSDES SEARCH PROVIDERS - VSE-9353 (Modified)\nSDES SEARCH RECALL CLINICS - VSE-9353 (Modified)\nSDES SEARCH RECALL PROVIDERS - VSE-9353 (Modified)\nSDES SEARCH VVS PROVIDERS JSON - VSE-9353 (Modified)\nSDES SET APPT CHECK-IN STEP - VSE-9353 (Modified)\nSDES SET CHECK-IN STEP - VSE-9353 (Modified)\nSDES SET COMP/PEN AMIE TRKNG - VSE-9353 (Modified)\n \nSDES SPACEBAR VVS PRO - VSE-9353 (Modified)\nSDES UNDO CHECKOUT - VSE-9353 (Modified)\nSDES UNDO NOSHOW - VSE-9353 (Modified)\nSDES UPDATE CLINIC HASH - VSE-9353 (Modified)\nSDES2 ADD CONTACT ATTEMPT - VSE-9356 (Modified)\nSDES2 BLOCK AND MOVE - VSE-9356 (Modified)\nSDES2 BLOCK PBSP SLOTS - VSE-9356 (Modified)\nSDES2 CANCEL APPOINTMENT - VSE-9356 (Modified)\nSDES2 CANCEL CLINIC AVAIL - VSE-9356 (Modified)\nSDES2 CHECK CLIN AVAIL DEFINED - VSE-9356 (Modified)\n \nSDES2 CHECKIN - VSE-9356 (Modified)\nSDES2 CREATE APPOINTMENT - VSE-9356 (Modified)\nSDES2 CREATE APPT REQ - VSE-9356 (Modified)\nSDES2 CREATE CLINIC - VSE-9356 (Modified)\nSDES2 CREATE CLINIC AVAIL - VSE-9356 (Modified)\nSDES2 CREATE LAST SELECTED PAT - VSE-9356 (Modified)\nSDES2 CREATE LETTER - VSE-9356 (Modified)\nSDES2 CREATE PROVIDER RESOURCE - VSE-9356 (Modified)\nSDES2 CREATE RECALL REQUEST - VSE-9356 (Modified)\nSDES2 CREATE SPEC NEEDS PREFS - VSE-9356 (Modified)\n===================================================== \nFiles:\nSDES2 CREATE VET REQ AND APPT - VSE-9356 (Modified)\nSDES2 CREATE WALKIN APPT - VSE-9356 (Modified)\nSDES2 DELETE LETTER - VSE-9356 (Modified)\nSDES2 DISPOSITION APPT REQ - VSE-9356 (Modified)\nSDES2 DISPOSITION RECALL REQ - VSE-9356 (Modified)\nSDES2 EDIT APPOINTMENT - VSE-9356 (Modified)\nSDES2 EDIT APPT REQ - VSE-9356 (Modified)\nSDES2 EDIT CLINIC - VSE-9356 (Modified)\nSDES2 EDIT LETTER - VSE-9356 (Modified)\nSDES2 EDIT PAT DEMOGRAPHICS - VSE-9356 (Modified)\n======\nSDES2 EDIT PAT PRE-REG - VSE-9356 (Modified)\nSDES2 EDIT PROVIDER RESOURCE - VSE-9356 (Modified)\nSDES2 EDIT RECALL REQUEST - VSE-9356 (Modified)\nSDES2 EDIT SPEC NEEDS PREFS - VSE-9356 (Modified)\nSDES2 EDIT TEMP ADDRESS - VSE-9106 (New)\nSDES2 GET APPT BY APPT IEN - VSE-9356 (Modified)\nSDES2 GET APPT REQ BY DFN - VSE-9356 (Modified)\nSDES2 GET APPT REQ BY IEN - VSE-9356 (Modified)\nSDES2 GET APPT REQ BY TYP VET - VSE-9356 (Modified)\nSDES2 GET APPT REQ LIST BY DFN - VSE-9356 (Modified)\nSDES ERROR CODES - VSE-9106 \nSDES2 GET APPT TYPES BY DFN - VSE-9356 (Modified)\nSDES2 GET APPTS BY APPT IENS - VSE-9356 (Modified)\nSDES2 GET APPTS BY CLIN LIST - VSE-9356 (Modified)\nSDES2 GET APPTS BY CLINIC IEN - VSE-9356 (Modified)\nSDES2 GET APPTS BY CLINIC LIST - VSE-9356 (Modified)\nSDES2 GET APPTS BY CLN RES IEN - VSE-9356 (Modified)\nSDES2 GET APPTS BY PAT DFN2 - VSE-9356 (Modified)\nSDES2 GET APPTS BY PATIENT DFN - VSE-9356 (Modified)\nSDES2 GET APPTS CLINIEN LIST - VSE-9356 (Modified)\nSDES2 GET CANCELLED SLOTS - VSE-9356 (Modified)\n \nSDES2 GET CLINIC AVAIL BY SVC - VSE-9356 (Modified)\nSDES2 GET CLINIC INFO - VSE-9356 (Modified)\nSDES2 GET CLINICS BY CLIN LIST - VSE-9356 (Modified)\nSDES2 GET CLINICS BY PROVIDER - VSE-9356 (Modified)\nSDES2 GET CLINICS BY STATION - VSE-9356 (Modified)\nSDES2 GET CONSULT BY IEN - VSE-9356 (Modified)\nSDES2 GET CONSULT CLINIC INFO - VSE-9466 (Modified)\nSDES2 GET CONSULTS BY DFN - VSE-9356 (Modified)\nSDES2 GET CONTACT ATTEMPTS - VSE-9356 (Modified)\nSDES2 GET DEMOGRAPHICS - VSE-9356 (Modified)\n \nSDES2 GET DISP CONT ATTEMPTS - VSE-9356 (Modified)\nSDES2 GET ELIGIBILITY CODES - VSE-9356 (Modified)\nSDES2 GET EXPANDED ENTRY - VSE-9356 (Modified)\nSDES2 GET EXPANDED ENTRY 2 - VSE-9356 (Modified)\nSDES2 GET HELP LINKS - VSE-9356 (Modified)\nSDES2 GET HOLIDAYS - VSE-9356 (Modified)\nSDES2 GET INFO FOR VIDEO VISIT - VSE-9356 (Modified)\nSDES2 GET LAST SELECTED PAT - VSE-9356 (Modified)\nSDES2 GET LETTER TYPES - VSE-9301,VSE-9356 (New)\nSDES2 GET PAT DEMOGRAPHICS - VSE-9356 (Modified)\nInput Templates:\nSDES2 GET PATIENT CLIN STATUS - VSE-9356 (Modified)\nSDES2 GET PATIENT EP - VSE-9356 (Modified)\nSDES2 GET PATIENT INFO - VSE-9356 (Modified)\nSDES2 GET PATIENT MED LIST - VSE-9356 (Modified)\nSDES2 GET PATIENT REGISTRATION - VSE-9106,VSE-9356 (Modified)\nSDES2 GET RECALL APPT TYPES - VSE-9356 (Modified)\nSDES2 GET RECALL BY IEN - VSE-9356 (Modified)\nSDES2 GET RECALL DELETE REASON - VSE-9356 (Modified)\nSDES2 GET RECALLS BY DFN - VSE-9356 (Modified)\nSDES2 GET REQUESTS BY INST - VSE-9356 (Modified)\n================\nSDES2 GET RESOURCE GROUP - VSE-9356 (Modified)\nSDES2 GET RESOURCE IEN - VSE-9356 (Modified)\nSDES2 GET SCHEDULING USERS - VSE-9356 (Modified)\nSDES2 GET SERVICES FOR CLINICS - VSE-9356 (Modified)\nSDES2 GET SPEC NEEDS PREFS - VSE-9356 (Modified)\nSDES2 GET URGENCY LIST - VSE-9356 (Modified)\nSDES2 GET USER PROF BY SECID - VSE-9356 (Modified)\nSDES2 GET USER PROFILE BY DUZ - VSE-9356 (Modified)\nSDES2 GET VIDEO VISIT PROV - VSE-9356 (Modified)\nSDES2 GET VVC STOP CODES - VSE-9356 (Modified)\n \nSDES2 INACTIVATE CLINIC - VSE-9356 (Modified)\nSDES2 NO-SHOW - VSE-9356 (Modified)\nSDES2 PATIENT SEARCH - VSE-9356 (Modified)\nSDES2 PRINT APPT LETTER - VSE-9356 (Modified)\nSDES2 PRINT APPT LETTERS - VSE-9356 (Modified)\nSDES2 QUERY APPT REQUESTS - VSE-9356 (Modified)\nSDES2 REACTIVATE CLINIC - VSE-9356 (Modified)\nSDES2 RESTORE CLIN AVAIL - VSE-9356 (Modified)\nSDES2 SEARCH CLIN BY STOP CODE - VSE-9356 (Modified)\nSDES2 SEARCH CLINIC ATTRIBUTES - VSE-9356 (Modified)\n \nSDES2 SEARCH CLINIC SLOTS - VSE-9356 (Modified)\nSDES2 SEARCH LETTER - VSE-9356 (Modified)\nSDES2 SEARCH PROVIDERS - VSE-9356 (Modified)\nSDES2 SEARCH RECALL CLINICS - VSE-9356 (Modified)\nSDES2 SEARCH RECALL PROVIDERS - VSE-9356 (Modified)\nSDES2 SET APPT CHECKIN - VSE-9356 (Modified)\nSDES2 SET APPT CHECKOUT - VSE-9356 (Modified)\nSDES2 SET CHECK-IN STEP - VSE-9356 (Modified)\nSDES2 UNBLOCK PBSP SLOTS - VSE-9356 (Modified)\nSDES2 UNDO CHECKOUT - VSE-9356 (Modified)\nOptions:\nSDES2 UNDO NO-SHOW - VSE-9356 (Modified)\nVSE-9049: MB - VistA: Update the SDES2 PRINT APPT LETTERS RPC to process \n========\nSDESRPC - VSE-9106, VSE-9301 \n \n \nRoutines:\n=========\nSDES2APTLETTER - VSE-9049 (Modified)\nSDES2CREATEAPPT - VSE-9373 (Modified)\nSDES2CRTAPREQ - VSE-9373 (Modified)\nSDES2EDITAPREQ - VSE-9373 (Modified) \n all Appointment IENs in the SDINPUT("Appointment IEN") array\nSDES2EDITTEMPADD - VSE-9106 (New) \nSDES2ENTERLETTER - VSE-9301 (Modified)\nSDES2GETCLINAVL - VSE-9384 (Modified)\nSDES2GETLETRTYPE - VSE-9301 (Modified)\nSDES2GETREGS - VSE-9106 (Modified)\nSDES2RECLLREQ - VSE-9373 (Modified)\n \n \nRemote Procedure Call:\n======================\nVSE-9106: JS - VistA: Modify SDES2 EDIT PAT DEMOGRAPHICS to update \nSDES ADD CLNGRP ITEM - VSE-9353 (Modified)\nSDES ADD PRIV USER - VSE-9353 (Modified)\nSDES ADD/UPDATE CONTACT - VSE-9353 (Modified)\nSDES ADDEDIT CLINIC GRP - VSE-9353 (Modified)\nSDES BLOCK AND MOVE - VSE-9353 (Modified)\nSDES CANCEL APPOINTMENT 2 - VSE-9353 (Modified)\nSDES CANCEL CHECKIN - VSE-9353 (Modified)\nSDES CANCEL CLIN AVAILABILITY - VSE-9353 (Modified)\nSDES CANCEL CLIN PRECAN LIST - VSE-9353 (Modified)\nSDES CHECK ORDER LOCK - VSE-9353 (Modified)\n temporary address fields\nSDES CHECKIN - VSE-9353 (Modified)\nSDES CHECKOUT - VSE-9353 (Modified)\nSDES CREATE APPOINTMENTS - VSE-9353 (Modified)\nSDES CREATE APPT BLK AND MOVE - VSE-9353 (Modified)\nSDES CREATE APPT REQ - VSE-9353 (Modified)\nSDES CREATE CLIN AVAILABILITY - VSE-9353 (Modified)\nSDES CREATE LAST SELECTED PAT - VSE-9353 (Modified)\nSDES CREATE RECALL REQ 2 - VSE-9353 (Modified)\nSDES CREATE SPEC NEEDS PREFS - VSE-9353 (Modified)\nSDES CREATE VET REQ SCHED APPT - VSE-9353 (Modified)\nVSE-9301: BB - VistA: Create a new SDES2 RPC that returns the letter \nSDES CREATE WALKIN APPT - VSE-9353 (Modified)\nSDES DELETE CLINIC GROUP - VSE-9353 (Modified)\nSDES DELETE CLNGRP ITEM - VSE-9353 (Modified)\nSDES DELETE PRIV USER - VSE-9353 (Modified)\nSDES DELETE PRIV USERS - VSE-9353 (Modified)\nSDES DELETE VVS ID - VSE-9353 (Modified)\nSDES DISPLAY CONTACT - VSE-9353 (Modified)\nSDES DISPOSITION APPT REQ - VSE-9353 (Modified)\nSDES DISPOSITION RECALL REQ - VSE-9353 (Modified)\nSDES EDIT APPOINTMENT - VSE-9353 (Modified)\n types and modify SDES2ENTERLETTER routine to not use $$FIND1\nSDES EDIT APPT REQ - VSE-9353 (Modified)\nSDES EDIT CHECK-IN STEP - VSE-9353 (Modified)\nSDES EDIT CLINIC AVAILABILITY - VSE-9353 (Modified)\nSDES EDIT RECALL REQ 2 - VSE-9353 (Modified)\nSDES EDIT SPEC NEEDS PREFS - VSE-9353 (Modified)\nSDES GET ALL CANCEL COMMENTS - VSE-9353 (Modified)\nSDES GET ALL CLINIC HASHES - VSE-9353 (Modified)\nSDES GET APPT BY APPT IEN - VSE-9353 (Modified)\nSDES GET APPT BY REQ/APPT TYP2 - VSE-9353 (Modified)\nSDES GET APPT CHECK-IN STEP 2 - VSE-9353 (Modified)\n when finding letter type\nSDES GET APPT CHECK-IN STEPS 2 - VSE-9353 (Modified)\nSDES GET APPT REQ BY IEN - VSE-9353 (Modified)\nSDES GET APPT REQ BY PAT ALL - VSE-9353 (Modified)\nSDES GET APPT REQ BY PAT OPEN - VSE-9353 (Modified)\nSDES GET APPT REQ BY PATIENT - VSE-9353 (Modified)\nSDES GET APPT REQ BY TYPE VET - VSE-9353 (Modified)\nSDES GET APPT REQ LIST BY DFN - VSE-9353 (Modified)\nSDES GET APPT REQS BY IENS2 - VSE-9353 (Modified)\nSDES GET APPT TYPES - VSE-9353 (Modified)\nSDES GET APPTREQ BY INST - VSE-9353 (Modified)\n\n\nJira Tickets Sprint 12.3 - SD*5.3*902\n results were returned\nVSE-9421: BB - VistA: Update HELP-PROMPT text in 44.1902, .02\nVSE-9426: BB - VistA: Correct cancellation reason to be BLOCK & MOVE when \n blocking and moving an appointment\n \n \nFiles/Fields:\n=============\nFiles/Fields\n#44 - Sub-file #44.1902 - VSE-9421 (modification)\n=====================================\n - Sub-file field #.01\n - Sub-file field #.02\n \n \nInput Templates:\n================\n \n \nOptions:\n========\n \n \n \nRoutines:\n=========\nSDES2CANCLNAVAIL - VSE-9426 (Modified)\nSDES2GETCLINAVL - VSE-9370 (Modified)\nSDES2INACTCLIN - VSE-9300 (Modified)\nSDESHASHCLIN - VSE-9242 (Modified)\n \n \nVSE-9242: BB - VistA: Removal of the provider name when a clinic is \nRemote Procedure Call:\n======================\nSDES2 GET CLINIC AVAIL BY SVC -VSE-9370 (MODIFIED)\n inactivated\nVSE-9300: TB - VistA: When inactivating a clinic the availability grid is \n not being removed\nVSE-9370: JV - VistA: Modify SDES2 GET CLINIC AVAIL BY SVC RPC to \n determine if there are more than 500 records and not all search\n\n
\nSee National Patch Module for description.\n\n
\nJira Tickets Sprint 12.1 - SD*5.3*900\n \n \nInput Templates:\n================\n \n \nOptions:\n========\n \n \n=====================================\nRoutines:\n=========\nSDES900P - VSE-8989, VSE-9462 (New)\n \n \nRemote Procedure Call:\n======================\n \nVSE-8989: MD - VistA: FY 25 Mid-Year Stop Code Changes\nVSE-9462: MD - VistA: Update the clinic stop file to comply with the \n administration's related EO\n \nFiles:\n======\n\n
\n Jira Tickets Sprint 12.4 - SD*5.3*903\n quit out of the validation\nVSE-9492: TB - VistA: SDES2 CREATE CLINIC AVAIL is incorrectly setting \n the first timeslot of a day's availability\nVSE-9521: JC - VistA: Modify all SDES and SDES2 print appointment \n letter(s) to not use $$FIND1 when validating the letter type\n \n \nFiles:\n======\nAPPOINTMENT TYPE MODIFIED VSE-9111\n===================================================== \nSDES ERROR CODES MODIFIED VSE-9302 \n \nInput Templates:\n================\n \nOptions:\n========\nSDESRPC MODIFIED VSE-9302\n \nRoutines:\nVSE-9111: TB - VistA: Implement HUD/VASH, Registry Exam, and Allied \n=========\nSDES2APTLETTER MODIFIED VSE-9521\nSDES2INACTCLIN MODIFIED VSE-9302\nSDES2PATPATSEARCH MODIFIED VSE-9424\nSDES2REACTTCLIN2 NEW VSE-9302\nSDESAPPTLETTERS MODIFIED VSE-9521 \n \nRemote Procedure Call:\n======================\nSDES2 REACTIVATE CLINIC 2 NEW VSE-9302\n Veteran Appointment Type\nVSE-9248: RH - VistA: SQA TESTING - Implement HUD/VASH, Registry Exam, \n and Allied Veteran Appointment Type\nVSE-9302: JS - VistA: Update SDES2 INACTIVATE CLINIC and Create a new \n version of SDES2 REACTIVATE CLINIC\nVSE-9424: JJ - VistA: Modify SDES2PATSEARCH routine so that it does not \n\n
\nJira Tickets Sprint 12.5 - SD*5.3*904\n the Temporary Address work being done by ISS\nVSE-9529: JV - VistA: Create a Post install report of all Appointments\n made prior to the installation of patch 910 that were \n booked for 3/1/2026 and after\nVSE-9586: MD - VistA: Patient is not being found when the SSN starts with \n a leading zero\n \n \nFiles:\n======\n=====================================\n \n \nInput Templates:\n================\n \n \nOptions:\n========\nSDESRPC MODIFIED VSE-9228 \n \n \n \nRoutines:\n=========\nSDES2CLONESLOTS NEW VSE-9228\nSDES2CRTCLNAVAL2 NEW VSE-9228\nSDES2EDITAPREQ MODIFIED VSE-9410\nSDES2EDITTEMPADD MODIFIED VSE-9515 \nSDES2PATSEARCH MODIFIED VSE-9586\nSDES904P NEW VSE-9529,VSE-9410\n \nVSE-9228: BB - VistA: Create Copy Clinic Availability RPC 2/2\n \nRemote Procedure Call:\n======================\nSDES2 CLONE CLINIC SLOTS NEW VSE-9228\nSDES2 CREATE CLINIC AVAIL 2 NEW VSE-9228\nVSE-9366: BF - VistA: Create POST-INIT Routine to grant them the SDECVIEW\n key\nVSE-9410: JS - VistA: Delete any comment or note audit records in files \n 403.5, 409.84, and 409.85\nVSE-9515: JS - VistA: Modify SDES2 GET PATIENT REGISTRATION to support \n\n
\nJira Tickets Sprint 12.6 - SD*5.3*905\n date/time with existing appts\n \nFiles:\n======\n \n \nOptions:\n---------\n \n \n=====================================\nRoutine:\n--------\nSDES2APPTUTIL - VSE-9643\nSDES2CREATEAPPT - VSE-9643\n \nRemote Procedures:\n-------------------\nSDES2 INACTIVATE CLINIC VSE-8789 (MODIFIED) \n \nVSE-8789: TB - VistA: Modify SDES2 INACTIVATION CLINIC to allow the \n inactivation date to be removed\nVSE-9576: MD - VistA: Clean up SDES ERROR CODES ERROR CODE file #409.93\nVSE-9630: MB - VistA: Remove link from the SDEC SETTINGS>VS GUI NATIONAL \n file\nVSE-9643: JS - VistA: Validation issue when comparing the desired \n\n
\nJira Tickets Sprint 12.7 - SD*5.3*906\n future date for the day of the week.\nVSE-9713: LB - VistA: Modify SDES SEARCH PROVIDER to increase performance\n \n \nFiles:\n======\n \n \nInput Templates:\n================\n=====================================================\n \n \nOptions:\n========\nSDESRPC - VSE-9639 (Modified)\n \nRoutines:\n=========\nSDESPROVSEARCH - VSE-9713 (Modified)\nSDES2GETCLNSLOT - VSE-9639 (New)\nVSE-9105: MB - VistA: When the patient's alias is similar to their name, \nSDES2PATSEARCH - VSE-9105 (Modified)\nSDESCLINDAILYSCH - VSE-9624 (Modified)\nSDES2CLONESLOTS - VSE-9656 (Modified)\n \nRemote Procedure Call:\n======================\nSDES GET CLINIC ORIGINAL AVAIL - VSE-9624 (Modified)\nSDES2 GET CLINIC CANCEL SLOTS - VSE-9639 (New)\n it displays the name twice in ISS\nVSE-9624: BB - VistA: Modify SDES GET CLINIC ORIGINAL AVAIL to correct \n calculations of original availability\nVSE-9639: TB - VistA: Create a new SDES2 RPC to return back the time \n slots that have been cancelled for a clinic\nVSE-9656: BB - VistA: SDES2 CLONE CLINIC SLOTS to return back the first \n\n
\nThe description of this build can be found in the National Patch Module\nunder SD*5.3*894.\n\n
\n \nVSE-9691: TB - VistA: The SDES REACTIVATE CLINIC has logic to check for\n an error returned by FileMan but it is flawed\nVSE-9700: JJ - VistA: Modify the SDES2 SEARCH CLIN BY STOP CODE RPC to \n prevent the return of a null return, which causes a 500\n error in CCMM\nVSE-9701: JV - VistA: MRTC parent requests were left open even though \n all the children requests have been dispositioned\nVSE-9702: JS - VistA: Update SDES2 EDIT APPOINTMENT RPC to prevent null \n Note values in the Note Audit section\nVSE-9711: MB - VistA: Users are unable to inactivate a clinic at the \n Jira Tickets Sprint 12.8 - SD*5.3*907\n exact 6 month mark\nVSE-9747: LB - VistA: Modify FMTISO API to no longer use the kernel \n logic to convert date\nVSE-9995: LB - VistA: Modify SDES2 GET CANCELLED SLOTS RPC to return\n back a Boolean fullDayCancelled flag \n \n \nFiles:\n======\n \n===================================================== \n \nInput Templates:\n================\n \nOptions:\n========\nSDESRPC - VSE-9575 (Modified) \n \nRoutines:\n=========\nVSE-9509: JJ - VistA: Update the veteran crisis line telephone number to\nSDAMUTDT - VSE-9747 (Modified)\nSDES2APPTUTIL - VSE-9702 (Modified)\nSDES2CLININFO - VSE-9574 (Modified) \nSDES2CREATEAPPT - VSE-9702 (Modified)\nSDES2CRTAPREQ - VSE-9702 (Modified)\nSDES2EDITAPPT - VSE-9702 (Modified)\nSDES2EDITAPREQ - VSE-9702 (Modified)\nSDES2GETCANSLOTS - VSE-9995 (Modified)\nSDES2GETDEVICES - VSE-9575 (New)\nSDES2INACTCLIN - VSE-9711 (Modified)\n "988 x 1", so that ISS reflects the preference set from\nSDES2REACTTCLIN2 - VSE-9691 (Modified)\nSDES2RECLLREQ - VSE-9702 (Modified)\nSDES2SRCHCLNBYSC - VSE-9700 (Modified)\nSDES2UTIL - VSE-9747 (Modified)\nSDES907P - VSE-9701,VSE-9702,VSE-9509 (New - post install)\n \n \nRemote Procedure Call:\n======================\nSDES2 GET CANCELLED SLOTS - VSE-9995 (Modified)\nVSE-9574: MB - VistA: Modify SDES2 GET CLINIC INFO to include the \nSDES2 GET CLINIC INFO - VSE-9574 (Modified)\nSDES2 GET VISTA DEVICES - VSE-9575 (New)\n diagnosis multiple and privileged user multiple IVC.\nVSE-9575: JC - VistA: Create a new SDES2 RPC to replace SDES GET VISTA \n DEVICES \n\n
\n \nOptions:\n==========\nSDESRPC - VSE-8457\n \nRoutines: \n===========\nSDES2GETAPPTREQ - VSE-10090 (MODIFIED)\nSDES2REMAP - VSE-8457 (NEW)\nSDES2REMAPUTIL - VSE-8457 (NEW)\nSDES2SEARCHSLOTS - VSE-9748 (MODIFIED)\nJira Tickets Sprint 12.IP - SD*5.3*908\n \nRemote Procedures:\n====================\nSDES2 REMAP CLINIC/DIVISION - VSE-8457 (NEW)\n===================================================== \nVSE-8457: JS - VistA: Create a new RPC to remap clinics\nVSE-9748: BB - VistA: Modify SDES2 SEARCH CLINIC SLOTS to return the \n first found match and then the pattern after that.\nVSE-10090: LB - VistA: Modify SDES2 GET APPT REQ BY IEN on invalid error\n message\n \n\n
\nJira Tickets Sprint 13.1 - SD*5.3*913\n being saved on the first day of the range\n \nFiles:\n======\nHOSPITAL LOCATION (#44) - VSE-10133 (MODIFIED)\n EAS TRACKING NUMBER (#100) (NEW)\n \nInput Templates:\n================\n \n=====================================\nOptions:\n========\nSDESRPC - VSE-8255 (MODIFIED)\n \nRoutines:\n=========\nSDES2CANCLNAVAIL - VSE-10188 (MODIFIED)\nSDES2CLINUT - VSE-10133 (MODIFIED)\nSDES2CREATECLIN - VSE-10133 (MODIFIED)\nSDES2CRTCLNAVAL2 - VSE-10078 (MODIFIED)\nVSE-8255: TB - VistA: Create a new SDES2 RPC in order to support VAOS\nSDES2EDITCLIN - VSE-10133 (MODIFIED) \nSDES2GETCLINST - VSE-8255 (NEW) \nSDES2VAL44 - VSE-10012 (MODIFIED)\nSDESHASHCLIN - VSE-10133 (MODIFIED)\n \nRemote Procedure Call:\n======================\nSDES2 GET CLINIC BY STOP CODE - VSE-8255 (NEW)\nVSE-10012: TW - VistA: Modify SDES2 EDIT CLINIC to allow for LOA decrease\n and Increment change\nVSE-10078: JJ - VistA: Clinic availability cannot be deleted using the\n SDES2 CREATE CLINIC AVAIL 2 RPC, Updated validation\nVSE-10133: MD - VistA: HOSPITAL LOCATION file needs EAS Field added\nVSE-10188: MB -VistA: When a range of dates are sent in the remark is only\n\n
\nJira Tickets Sprint 13.2 - SD*5.3*914\n child and parent MRTCs\nVSE-10278: TB - VistA: Create a post install to identify duplicate clinic \n resources\nVSE-10342: MB - VistA: Update SDES2 GET CLINIC BY STOP CODE to return \n empty JSON object when no matching data is found.\n \nFiles:\n======\n \n \n=====================================\nInput Templates:\n================\n \n \nOptions:\n========\nSDESRPC - VSE-10134 (Modify) \n \nRoutines:\n=========\nVSE-9998: BB - VistA: Modify SDES2NOSHOW to no longer call \nSDECAR2 - VSE-10257\nSDES917P - VSE-10065, VSE-10278 (New)\nSDES2CRTAPREQ2 - VSE-10134 (New)\nSDES2GETCLINST - VSE-1-342 (Modified \nSDES2NOSHOW - VSE-9998 (Modified)\n \nRemote Procedure Call:\n======================\nSDES2 CREATE APPT REQ2 - VSE-10134 (New)\nSDES2 GET CLINIC BY STOP CODE - VSE-10342 (Modified)\n $$GETAPT^SDESCHECKOUT\nVSE-10065: TW - VistA: Create a post install to update the "DIRECT \n PATIENT SCHEDULING?" field for clinics with specific stop code\nVSE-10134: TW - VistA: Create a new version of SDES2 CREATE APPT REQUEST \n to return back object.\nVSE-10257: TB - VistA: Modify SDEC APPDEL logic to keep link between \n\n
\nSee National Patch Module for a description of the changes incorporated in\nthis patch.\n\n
\nThis patch creates a new ACRP option to count and report on bad pointers\nin the patient and outpatient encounter files. See NPM for complete\ndescription.\n\n
\nEnhancing the ability to fully use and support multi-RTC appointment \nprocessing (MRTC) patterned after how VSE's ability.\n\n
\nJira Tickets Sprint 13.6 - SD*5.3*925\nSDES2CREATEAPPT - VSE-10512 (MODIFIED)\n=====================================\n \nVSE-10512: LB - VistA: Patients VA online appointment request appeared as \n appointment comments in a different patients appointment\n \nRoutines:\n=========\nSDES925P - VSE-10512 (NEW)\n\n
\nJira Tickets Sprint 13.4 - SD*5.3*917\n \nOption:\n=======\n \nRoutines:\n=========\nSDES2CRTAPREQ - VSE-10321 (MODIFIED)\nSDES2REMAP - VSE-10184 (MODIFIED)\nSDESAPPTLETTERSV - VSE-10252 (MODIFIED)\nSDES2CONTACTS - VSE-9958 (MODIFIED)\n=====================================\nSDLT - VSE-10252 (MODIFIED)\n \nRemote Procedure:\n================\nVSE-9958: MB - VistA: Fix Leaking Variables in SDES2 ADD CONTACT ATTEMPT\nVSE-10184: TB - VistA: Modify SDES2 REMAP CLINIC/DIVISION to only send an\n HL7 message for holidays that were actually entered\nVSE-10252: TB - VistA: When printing pre-appointment letters In VistA, \n the timezone does not always show up\nVSE-10321: MB - VistA: When creating a request the PID is being converted \n based on the clinic\n\n
\nThis patch adds additional comments to a consult when a Community Care \nConsult appointment is scheduled or canceled.\n\n
\nPlease see National Patch Module\n\n
\nPlease see National Patch Module.\n\n
\nSEE NATIONAL PATCH MODULE\n\n
\nThis patch corrects a problem with the Appointment Status Update\nbackground job hanging when no disposition clinic is found in an\nencounter. See NPM for complete description.\n\n
\nPlease see National Patch Module.\n\n
\nRefer to National Patch Module for details\n\n
\nSee National Patch Module for description.\n\n
\nSee patch description in the Patch Module for patch SD*5.3*134.\n\n
\n KIDS distribution of the Scheduling portion of the Ambulatory Care\n Reporting Project.\n \n The changes included in this patch are described in the description of\n patch SD*5.3*44 in the National Patch Module.\n\n
\nSee NPM for description.\n\n
\nSee NPM for description.\n\n
\nAmbulatory Care Reporting Project - Transmission Management Module\n\n
\nRefer to the National Patch Module\n\n
\nPlease see National Patch Module.\n\n
\nThis patch corrects a problem with the selection of encounter dates in\nthe option [SCDX AMBCAR EDIT ENC APPT TYPE]. See NPM for complete\ndescription.\n\n
\nPlease see National Patch Module.\n\n
\nSee National Patch Module for patch description.\n\n
\nIncomplete Encounter Management\n\n
\n **** ACRP Interface Toolkit ****\n - diagnoses\n - provider\n - general administrative \n\nRefer to National Patch Module for more details on patch SD*5.3*131.\n \n This build contains the ACRP Interface Toolkit (AIT) supported by scheduling\n that provides access to ACRP encounter data. Use of the AIT does not\n require an integration agreement. \n\n National and local developers should use the AIT to obtain the following\n ACRP encounter related data:\n - procedures\n\n
\nSee NPM for description.\n\n
\nThis build contains the changes as a result of three NOIS issues. The\nfollowing is a listing of the problems it will fix.\n-up-arrow not being recognized in the summary report.\n-Extra questions appearing in question 4 of screen one of load/edit. They\nwill be removed.\n-A020 errors appearing on duplicate stop codes.\n\n
\nVA Health Services R&D Alzheimer's Project\n\n
\nThe changes included in this patch are described in the description\nof patch SD*5.3*138 in the National Patch Module.\n\n
\nACRP Reports Module (phase 1)\n\n
\nThis patch makes the necessary modifications to Scheduling/PCMM\nrotuines to meet the Year 2000 compliancy standards for date handling and\ndisplay. See the patch description SD*5.3*140 for detailed information.\n\n
\nFix for NOIS issue AUG-0398-32205 UNDEFINED VARIABLE WHEN RUNNING\nREPORT related to the 'Outpatient Encounter Workload Statistics'.\n\n
\nPrevent PC question when d/c is death.\n\n
\nNEW variables for DIR call in IEMM report option.\n\n
\nRefer to National Patch Module for details\n\n
\nThe DHCP Scheduling package allows a user to Schedule appointments for\nand pre-appointment. There is an additional capability where additional\nclinic stop credits can be directly entered and associated with a particular\npatient and date. AMIS reporting is handled via a set of extract routines\nthat summarize the data found by reading through the appointments and\nadditional clinic stops and the 10/10 and unscheduled visits (outpatient\ncredit given to Admitting/Screening) and storing the information by patient\nand visit date in the OCP File. The AMIS 223 report and the OPC\nfile to be sent to the Austin DPC are generated using this file.\nthe following types of appointments:\n Scheduled\n C&P\n Collateral\nIt also allows entry of an unscheduled appointment at any time during a day\non which the clinic being scheduled into meets. From these appointments,\nvarious output reports are produced such as, but not limited to, file room\nlist, appointment list, routing slips, letters for cancellations, no-shows,\n\n
\nPatch IB*2*55 for Integrated Billing adds the ability to flag Stop Codes\nand Clinics as non-billable or non-auto billable for Third Party Billing.\n \nPlease see the National Patch Module description for this patch for more\ndetailed information.\n\n
\nPatch IB*2*69 contains the Diagnostic Measures reports and includes a new\nmenu which is designed for the MCCR Coordinator.\n\n
\nCorrects bad EDI IDs in insurance company file.\n\n
\nPatch IB*2*176 was created to implement the Long Term Care (LTC) \nCopayment requirements.\n\n
\nThis is an emergency patch to fix the problem of batches not being found \nwhen a confirmation message is received by the EDI server from Austin.\n\n
\nHold all Inpatient MT bills for GMT.\n\n
\nVisit Copay Phase 2 project.\n\n
\nEDI Maintenance patch.\n\n
\nOn July 31st, 2002 the EDI system's method of identifying EDI routing ids \nof patch 189 may have been sent to the wrong payers.\n \nIn an effort to help the sites identify and resubmit these claims, this \npatch was created. The options included in this patch must be run by the\nIRM staff as the elements of this patch are used solely to correct this\nspecific problem and will not become part of official VistA software. \nIntegrated Billing must be involved to review the report of misrouted\nclaims to indicate the ones the site does NOT want to automatically\nresubmit.\nfor insurance companies in Vista was changed. As a result of this \nchange, a problem occurred in Vista whereby the text PAYID was \nerroneously inserted into some insurance company EDI routing ids.\n \nPatch IB*2*189 corrected the problem of the bad id being stored and\ndeleted the text PAYID from the EDI routing id fields. Any claims\nsubmitted after this patch was installed would not have been affected by\nthis problem, but claims submitted between July 31st and the installation\n\n
\nThe patch resolves the following issues:\n NOIS NJH-0102-22792\n NOIS MAN-0802-10732\n\n
\nAPI CHANGE AND CLEAN UP DATE\n\n
\nModifications for CPT v6.0 update.\n\n
\nThis patch fixes the problem when prescriptions billed through the RNA\nengine are rejected with a error of 'NDC is not covered' for claims sent\nto the Fiscal Intermediary.\nResubmitting a pharmacy claim to the Fiscal Intermediary allows the user\nto choose a product selection reason code which will allow the correct\ncode to be submitted to the Fiscal Intermediary for billing acceptance.\n\n
\nLTC PHASE III\n\n
\nGEOGRAPHIC MEANS TEST, IB PART 2\n\n
\nThis patch deletes obsolete options from IB menus and from the IB package.\nIt will also make some changes to the List Manager screens for the \nInsurance Co Edit.\n\n
\nGMT IB Clean-up patch.\n\n
\nThis patch corrects minor issues related to the EDI claims transmission\nand opens up the use of the Output Formatter for the CURRENT INS CO\nPROVIDER NUMBER.\n\n
\nREGIONAL COUNSEL ENHANCEMENT\n\n
\nCancel ClaimsManager Bill Bug Fix\n\n
\nHartford/USAA Settlement\n\n
\nThis patch provides a means of batch entry for provider ID's and a quick \nmethod of manually entering provider ID's.\n\n
\nThis patch adds pre-registration as a new source of information\nfor patient insurance policies.\n\n
\nREMOVE SSN FROM COPAY EXEMPT LETTERS\n\n
\nThis patch modifies the output transforms of four fields in the \nBILL/CLAIMS (#399) file, to resolve an issue with <UNDEF> errors when\nusing this file directly through FileMan.\n\n
\nAR PRODUCTIVITY/UNBILLED AMOUNTS REPORT FIXES\n\n
\nThe IB part of the HIPAA Confidential Communication project.\n\n
\nThis patch modifies two entries in file 364.7 - IB FORM FIELD CONTENT\nto address issues with Medicare rejections and Admit/Discharge dates.\nIt also modifies the way box 24K is filled when billing secondary\ncoverage on a claim where Medicare is primary.\n\n
\nInterface between IB and QuadraMed.\n\n
\nReasonable Charges v1.4\n\n
\nThis patch changes the value of SOURCE LEVEL MINIMUM for\nthe CHAMPUS ID record in the IB PROVIDER ID # TYPE (#355.97) file.\nThe new value will be "NONE".\n\n
\nChanges to suppress PATIENT file fuzzy lookups.\n\n
\nREMOVE HARTFORD SETTLEMENT SOFTWARE\n\n
\nThis patch fixes a problem whereby an illegal number error may occur\nwhen using the 'SC Vets w/ NSC Episodes of Care Not Billed (Inpt)' option\nwhen the BILL NUMBER field (.01) in the BILL/CLAIMS file (399) contains\nan E, such as 5E1345.\n~\n\n
\nREMOTE INSURANCE QUERY \n\n
\nThis patch will cover OKL-0303-72052.\n\n
\nFixes assorted NOIS calls (10).\n\n
\nREASONS NOT BILLABLE/FOLLOW-UP/VETS WITH UNVERIFIED ELIG. REPORTS\n\n
\nThis patch corrects a problem with the range selection in the\n[IBJD FOLLOW-UP FIRST PARTY] option. \n \n OKL-1001-73313 [IBJD FOLLOW-UP FIRST PARTY] incorrect Data (0 to n Range)\n\n
\nREMOTE INSURANCE QUERY FIX/UPDATE\n\n
\nThis patch adds new Occurence Codes and Occurrence Span Codes\nto file 399.1.\n\n
\nThis patch updates the Information/Warning records in file #361.\nRef. NOIS FGH-0203-31133\nRoutine: IB20P229, a database conversion routine.\n \nThis patch also fixes a display problem with the Contact Date\nand Call Ref. No. on the IBCN PATIENT INSURANCE screens.\nRef. NOIS BAY-0403-32311\nRoutine: IBCNSP0\n\n
\nThis patch adds some error trapping code to avoid a problem in the\n \nTECHNICAL:\n==========\n1. Changes are made to routines IBCIUT3 and IBCIUT4.\n IBCIUT3\n A new subroutine, ERRTRP, releases the tcp/ip port and creates the\n message "A SYSTEM ERROR HAS BEEN DETECTED AT THE FOLLOWING LOCATION".\n A new level is pushed on the error trap stack and the $ETRAP system\n variable is set to call the new ERRTRP subroutine.\n IBCIUT4\nClaims Manager interface that could cause users to be forcibly logged\n A new error type, "Fatal System Error" is added to the P1 function.\nout. \n \nASSOCIATED NOIS:\n================\n1. PRE-0902-60489 Claims Manager freezing screen \n DUB-0303-31898 <READ>READ+27^IBCIUT3\n ASH-0103-30446 ib error when going to claimsmanager\n\n
\nSpecial Mid-Year FY03 Stop Codes Update\n684 NONVIDEO HOME TELEHEALTH INTERVENTION N\n\n* N = Nonbillable\n=======================================\n\nCODE DESCRIPTIONS BILLABLE TYPE * \n---- ---------------------------------------- -------------\n161 PHARMACY TRANSITION CARE N\n179 HOME TELEVIDEO CARE N\n220 VISOR (VISUAL IMPAIRMENT OUTPATIENT PROGRAM) N\n683 NONVIDEO HOME TELEHEALTH MONITOR ONLY (NONCOUNT) N\n\n
\nPROBLEM WITH IBARXEC4\n\n
\nThis patch addresses an issue where the ELECTRONIC PLAN TYPE field was not\navailable for editing in the Move Subscribers to a Different Plan option.\nASSOCIATED NOIS:\n================\n \n1. PUG-0403-50885 Electronic Type not included when moving Ins Plans\n \nRoutine: IBCNSUR2\n\n
\nThis patch updates the unbilled amounts report to generate according to \nthe new EOAM schedule. Changes in routines IBJDE, IBTUBO and IBTUBOU have\nbeen made to accommodate the changes as well as changes to the INPUT VARIABLE\nsection of file 351.7 DIAGNOSTIC MEASURES REPORTS.\n\n
\nThis is the build for the electronic Insurance Identification and \nVerification project (also referred to as eIIV and IIV).\n\n
\nCode Set Versioning, the IB part. Phase 1.\n \nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nThis patch adds an additional prompt to the Third Party Follow-up report\nto allow the generation of the report from the date of care to the date\nthe report is run.\n\n
\nThird Party EDI Lockbox patch IB*2.0*135 (Integrated Billing component)\n \nThis patch is being released as part of a build that also includes patch\nPRCA*4.5*173. Please refer to the patch description in the National Patch\nmodule and the users documentation for patch PRCA*4.5*173 for detailed\ninformation about this patch.\n\n
\nINTERIM ADDRESS ENHANCEMENT\n\n
\nIIV Update for Individually Accept method in the Insurance Buffer \n \n* NOTE: This patch must be installed by October 7, 2003, in order to meet \n* the HIPAA compliance date for use of the software by October 16, 2003. \nacceptance process.\n \nThis patch fixes a problem identified in the IB Insurance Buffer \nIndividually Accept action. Under certain circumstances the problem may \nresult in incorrect filing of information from the Insurance Buffer. \nThis \naction was released with IB*2*184, therefore this patch should be \ninstalled as soon after IB*2*184 as is practicable.\n\n
\nThis patch corrects the unbilled amounts report from generating\nagain on the first of the month with the other DM reports. It also\ncorrects the IBT RE-GENERATE UNBILLED AMOUNTS REPORT. The end date for\nthe report for months prior to September 2003 will display as the last day\nof the calendar month. Those months after September 2003 will use the\nEOAM date for that month.\n\n
\n \nPatch for output formatter utility, Charge Master, and Tri-care.\n\n
\nCOMBAT VETERANS INTERIM SOLUTION - PHASE I\n\n
\nThis patch fixes the transmission of the Diagnostic Measures reports\nfor future runs.\n\n
\nThis patch corrects the problem of bills reflecting that they are \nreferred to Regional Counsel, when they are no longer referred, on the \nThird Party Follow-up Report.\n\n
\nThis patch corrects a problem with Means Test reminder letters, fixes\nN/A\nTECHNICAL:\n==========\n \n1. SHE-0801-51284 Cat C reminder letters printing\n Changes are made to routines: IBARXEL, IBARXEL1\n The function $$BIL^DGMTUB(X,Y) is called and the veteran is\n either sent a letter or not sent a letter based on the result.\n \n2. COA-0403-21056 <UNDEF> MAIN+2^IBTOSUM2 in MCCR/UR SUMMARY REPORT\n The initialization of the IBCNT array is modified in the RPT section\n \n of routine IBTOSUM. The code S IBCNT(3,0)=0 is added.\n \n3. SBY-0403-30897 Claims Waiting Austin Acknowledgement\n The SUPRESS BULLETIN field (#224) of the OPTION file (#19) for\n option IBCE MESSAGES SERVER is set to the value Y.\n \n4. BRX-0403-12417 BULL1+4^IBTUBUL:1, %DSM-E-UNDEF, undefined variable\n The TESTV subroutine of IBTUBUL is modified to contain the line:\n S IBUNB("EPISM-A")=11111. \n \nASSOCIATED NOIS:\n \nPARTICIPATING TEST SITES:\n=========================\nTBD\n \nROUTINE SUMMARY \n===============\nThe following is a list of the routines included in this patch. \nThe second line of each of these routines now looks like: \n \n================\n <tab>;;2.0;INTEGRATED BILLING;**[PATCH LIST]**;21-MAR-94\n \n CHECK^XTSUMBLD results\nRoutine name Before Patch After Patch Patch List\n============ ============ =========== ===========\nIB20P217 N/A 1138089 217\nIBARXEL 5496758 5804553 34,139,206,217\nIBARXEL1 7127873 7529363 34,199,217\nIBTOSUM 8582961 8533948 118,133,217\nIBTUBUL 6667983 6686239 19,123,159,217\n \n \n \nINSTALLATION INSTRUCTIONS\n=========================\n \n This patch can be installed at any time, however, the IB MT NIGHT COMP\n job should not be running.\n \n If installed during the normal workday it is recommended that the\n following menu options (File #19) be disabled to prevent possible\n1. SHE-0801-51284 Cat C reminder letters printing\n conflicts while running the KIDS Install. Other VISTA users will not\n be affected.\n \n Reprint Single Income Test Reminder Letter [IB RX REPRINT REMINDER]\n MCCR/UR Summary Report [IBT OUTPUT MCCR/UR SUMMARY]\n Send Test Unbilled Amounts Bulletin [IBT SEND TEST UNBILLED MESS]\n \n Install time - less than 2 minutes.\n \n \n2. COA-0403-21056 <UNDEF> MAIN+2^IBTOSUM2 in MCCR/UR SUMMARY REPORT\n 1. LOAD TRANSPORT GLOBAL \n ---------------------\n Choose the PackMan message containing this patch and invoke the \n INSTALL/CHECK MESSAGE PackMan option. \n \n 2. DISABLE ROUTINE MAPPING (DSM for open VMS sites only)\n -----------------------\n Disable routine mapping on all systems for the routines listed in\n the routine summary\n NOTE: If the routines included in this patch are not currently in\n3. SBY-0403-30897 Claims Waiting Austin Acknowledgement\n your mapped routine set, please skip this step.\n \n 3. START UP KIDS \n -------------\n Start up the Kernel Installation and Distribution System Menu \n [XPD MAIN]: \n \n Edits and Distribution ... \n Utilities ...\n Installation ... \n4. BRX-0403-12417 BULL1+4^IBTUBUL:1, %DSM-E-UNDEF, undefined variable\n \n Select Kernel Installation & Distribution System Option: INStallation\n ---\n \n 1 Load a Distribution\n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n \n Restart Install of Package(s)\n Unload a Distribution\n \n 4. From this menu, you may elect to use the following options\n (When prompted for the INSTALL NAME, enter IB*2.0*217):\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will\n not backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option\nan <UNDEF> error which could occur in IBT OUTPUT MCCR/UR SUMMARY, modifies\nNOIS OVERVIEW:\n will allow you to view all changes that will be made when\n this patch is installed. It compares all components of this\n patch (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will\n allow you to ensure the integrity of the routines that are\n in the transport global.\n \n 5. Use the Install Package(s) option and select the package IB*2.0*217.\n \n a. When prompted 'Want KIDS to INHIBIT LOGONs during the\n==============\n install? YES//', answer NO.\n b. When prompted 'Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//' answer YES.\n c. When prompted 'Enter options you wish to mark as 'Out of\n Order':' Enter the following: \n IB RX REPRINT REMINDER\n IBT OUTPUT MCCR/UR SUMMARY\n IBT SEND TEST UNBILLED MESS\n \n d. When prompted 'Enter protocols you wish to mark as 'Out of\n \n Order': Enter the following: (press return) \n \n 7. REBUILD MAPPED ROUTINES(S) (DSM for Open VMS sites only)\n --------------------------\n Optional - Include the routines distributed with this patch in the\n mapped routine set.\n \n NOTE: This step is only necessary if you performed step 2 or if you \n wish to include the routines in your mapped set.\n \n1. SHE-0801-51284 Cat C reminder letters printing \n 8. DELETE PRE-INIT ROUTINE\n ------------------------\n You may delete the IB20P217 routine from your system after successful\n installation of this patch.\n \nINSTALLATION EXAMPLE:\n---------------------\n \n Problem:\n --------\n With DG*5.3*326, Category C veterans and those Pending Adjudication and \n having agreed to pay the deductible, and whose Means Test is more recent\n than 10/5/99, will no longer be subject to an annual MT. However, if the\nthe SUPRESS BULLETIN field of the IBCE MESSAGES SERVER option and fixes\n site has the Income Test Reminder Letters option turned on, these now\n exempt patients are included in the output. Since they are no longer\n subject to MT, their copay status will remain unchanged. As such, they\n should no longer be included in those patients due for a reminder. \n \n Resolution:\n -----------\n This patch corrects the issue by checking the veteran's status and \n removing them from the Means Test reminder list if they meet the\n criteria mentioned above.\nan <UNDEF> error in the IBT SEND TEST UNBILLED MESS option. \n \n \n2. COA-0403-21056 <UNDEF> MAIN+2^IBTOSUM2 in MCCR/UR SUMMARY REPORT\n \n Problem:\n --------\n When running the IBT OUTPUT MCCR/UR SUMMARY option for a date range that\n contains no Claims Tracking entry that is ACTIVE, INSURED and BILLABLE,\n an undefined error would occur. The printing function expected to find\n a value in the counter IBCNT(3,0) but if no records were selected \n \n during the search, the counter was never set.\n \n Resolution:\n -----------\n The counter array variable IBCNT(3,0) is initialized to zero prior\n to the record search.\n \n \n3. SBY-0403-30897 Claims Waiting Austin Acknowledgement\n \n \n Problem:\n --------\n When acknowledgment messages or status update messages are received\n from Austin, they are delivered to the S.IBCE MESSAGES SERVER\n option. Because there is no specific SERVER MAIL GROUP defined for \n this option, and the SUPRESS BULLETIN field is NULL (the default is\n to send), a message is sent to the default MAIL GROUP defined in the\n XQSERVER Bulletin (file 3.6). This is GENERALLY a mail group called \n XQSERVER but it may have some other name. If this MAIL GROUP \n specified in the XQSERVER Bulletin suddenly has NO active members (for \nASSOCIATED E3R(s):\n whatever reason), the incoming messages will be RECEIVED, but the IBCE \n MESSAGES SERVER is not served. The server option is listed as a\n recipient but server action was not processed due to a security\n violation.\n \n Resolution:\n -----------\n The issue could be resolved on a local basis by making sure that there\n is always a member of whichever mail group is specified by the XQSERVER\n bulletin. However, to avoid the problem altogether, this patch will\n==================\n set the SUPRESS BULLETIN field of the S.IBCE MESSAGES SERVER option\n to YES. The bulletin only announces that there has been server\n activity. It is not necessary for actual distribution of the incoming\n reports so suppressing the bulletin will have no detrimental effect.\n \n \n 4. BRX-0403-12417 BULL1+4^IBTUBUL:1, %DSM-E-UNDEF, undefined variable\n \n Problem:\n --------\n \n When running the option IBT SEND TEST UNBILLED MESS, a software error\n is logged because the TESTV subroutine fails to initialize the \n IBUNB("EPISM-A") variable. This problem only occurs for the TEST\n messages and not for the real messages.\n \n Resolution:\n -----------\n The missing variable is initialized so that the TEST message\n function can be utilized.\n \n\n\nThis patch changes the value in the print preview screen, BILL TOTAL \nfield and the TOTAL CHARGE field in the printed form. The value is \nchanged from the amount due to the total charges not including any \noffset. \n\n
\nIB*2.0*256 IB INSURANCE API TEST VERSION 6\n\n
\nThis patch does an automatic update of the CY 2004 Medicare Deductible\nand the Pension Copay Threshold amounts.\n\n
\nFIX RX COPAY EXEMPTION FOR IVM - The upload of an IVM Converted Means \nTest (ORU~Z06) will be modified to no longer re-calculate the COPAY \nINCOME EXEMPTION STATUS (#.04) field in the BILLING PATIENT (#354) File.\n\n
\nOIG/IVM 60-DAY BILL DROP\n\n
\nFIX FOR AUG-0103-31330, ADMIT/DISCHARGE HOUR FOR OUTPATIENT BILLS\n\n
\nCharge Item File (363.2) and the post init to add the Tort and Interagency\nRates.\n\n
\nThis patch adds patient information to an INTEGRATED BILLING BACKGROUND\nERROR message.\n\n
\nThis patch addresses the following NOIS message(s):\n---------------------------------------------------\nPOR-0903-52494 BUFFER FILE PROBLEMS\nBAY-1003-30706 Critical Message received from IIV\nLOU-0903-42302 IIV Payer Link Report /column\nUNY-1003-12260 <NULLSUBSCR>VALID+5^IBCNEUT4\n\n
\nReasonable Charges version 2.0. Charge effective date 12/19/03.\n\n
\nAdd Tortiously Liable and Interagency Rates for January 2004.\n\n
\nCare Units are displaying incorrectly on the Insurance Company Provider\nID Maintenance screen.\n\n
\nThis patch implements the following change to the Integrated Billing\npackage: Plan comments will now carry over when subscribers are moved\nfrom one insurance plan to another.\n\n
\nENHANCEMENT FOR BILLING AWARENESS PTF\n\n
\nThis patch resolves the problem reported in LEB-0104-20959\nIncorrect total in PATIENT PHARMACY COPAY CAP REPORT.\nThe improper formatting of numbers larger than 999.99 was\ncausing inaccurate data to be displayed to the user.\nThe code is modified to format and display correctly now.\n\n
\nThis build contains changes to add and populate fields in the EXPLANATION\nOF BENEFITS file (#361.1) needed for e-payments Phase II processing.\n\n
\nThis patch fixes a problem whereby the Earliest Auto Bill Date is being\nchanged to a date beyond the end of the billing cycle when the end\nof the billing cycle is greater than the date the auto biller is running.\nAs a result, the episode is not included on a bill until the next\nbilling cycle. This problem occurs with both prescription refills\nand outpatient visits.\n\n
\nReasonable Charges v2.1\n\n
\nThis KIDS Build will transport patch IB*2.0*259, The Pharmacy Co-pay Cap \nSummary Report, to the field.\n\n
\nThis patch addresses two issues: the Hospital Reviews [IBT EDIT REVIEWS] \noption has been modified so that the ward is displayed even if the \npatient is admitted and discharged on the same day, and the Queue Means\nTest Compilation of Charges [IB MT NIGHT COMP] option has been modified to\nrespect both date and time.\n\n
\nThis patch corrects a problem in the CLAIMS STATUS AWAITING RESOLUTION\noption where a <NULSUBSCR> error ocurred when trying to view an EOB\nand none existed.\nSee NOIS SBY-0104-30665.\nThis patch also corrects a second issue where active insurance\ncompany names were not listed when entering data into the\ninsurance buffer.\nSee NOIS MIN-0104-41017\n\n
\nCOMBAT VETERAN PHASE II\n\n
\nThe Type of Visit file (357.69) holds a list of E&M codes (a subset of \nCPT codes). Generally a quantity of 1 is all that is allowed for these \ncodes. There are cases, however, when this quantity should not be limited \nto one. Therefore, there needs to be a field that will serve as a flag. \nThe field being added is the .06 field. It will have a value of 0 if the \nquantity is to be restricted to one and a value of 1 if it allows a \nquantity of greater than one. Using the flag this way means that current \nentries that do not have a value for this flag will default to allowing a \nquantity of only 1.\n\n
\nPatch IB*2.0*243 fixes 3 items.\nThis patch announces a correction to the manual.\n(1) Two separate fields in the BILL/CLAIMS file (#399), #204 and #450,\nare both named FORM LOCATOR 2. The fields are renamed and two input\ntemplates (IB SCREEN8, IB SCREEN82) are recompiled.\n(2) If a user selects a bill to cancel but changes their mind and enters\n"no" at the end, a message displays "<NO ACTION TAKEN>" but the "DATE\nBILL CANCELLED" and "BILL CANCELLED BY" fields are populated anyway.\n(3) A user noted that the Integrated Billing Technical Manual did not\ninclude the IBAM and IBAT globals in the journalling instructions.\n\n
\nThis patch corrects a situation which allows the IB DM EXTRACT DATE file\nto become corrupted. It also corrects a situation where the Subscriber ID\nis saved with hyphens still embedded in the number.\n\n
\n Error handling code was added to the IB CANCEL BILL process to \n These will be added with the post init routine IBYP241.\n recognize the error indicator being passed back by AR and to display \n the following warning message: "Please note: PRCA was unable to determine\n if a payment has been posted"\n \nA new RATE TYPE of INELIGIBLE is added to the RATE TYPE file \n(#399.3) pointing to the ACCOUNTS RECEIVABLE CATEGORY: INELIGIBLE HOSP.\nNew Rate Schedules of INELIG-OPT and INELIG-INPT are added to file\n#363 - RATE SCHEDULE.\n\n
\nAdd ability to process IVM close case/converted Pharmacy Exemption tests \nvia Z06 transmissions from the EDB.\n\n
\nOUTPUT FORMATTER PROBLEMS\n\n
\nRemove references to CHAMPUS.\nFix <UNDEFINED>YR+6^IBAECU by correcting code in IBECEA3.\n\n
\nMEANS TEST DATE PROBLEM\n\n
\nThis patch will implement CBOC data extraction logic for\nthe Boston Allocation Resource Center.\n\n
\nThis patch will use the NEW command to limit the scope of the\nDIQUIET variable.\n\n
\nSeveral Trigger type cross references throughout IB files have\nan old Mumps function $Next. This is an outdated form and needs\nto be revised. By recompiling the trigger code with FileMan v22\nthe old code will be replaced with current standards.\n\n
\nThis patch will add one new entry to file 361.2.\nThe entry is: R0S0 - PRF GVT WEBMD/PAYER INFO/EDIT\n\n
\nContains the EDI Enhancements (HIPAA) provider ID worksheet.\n\n
\nThis patch modifies the 'Sender' name used by the IIV STATISTICAL REPORT\nwhen mailing the report to the IBCNE IIV MESSAGE mail group.\nThe name is changed from "IB IIV INTERFACE" to "IIV INTERFACE (IB)".\n\n
\nEDI/ENHANCEMENTS HIPAA COMPLIANCE\n\n
\nThis is a coordinated patch between the Integrated Billing and Accounts\nPRCA*4.5*84.\n \nThis coordinated patch fixes a problem whereby AR bills with an AMENDED\nBILL status were not being cancelled when the associated IB bill was\ncancelled.\nReceivable packages. Patch IB*2.0*77 contains two modified routines,\none for Integrated Billing and one for Accounts Receivable. Both are\nbeing released under the IB*2.0*77 patch namespace to assure installation\nat the same time, as one routine is dependent upon the other. The\nassociated AR patch is PRCA*4.5*84, and is listed in the National Patch\nModule as an information only patch. A post-init routine is also sent\nwith this patch. As part of the post-init process, the Accounts Receivable\npackage file will be updated to indicate successful installation of patch\n\n
\nFollow up patch for problems found late in testing patch IB*2.0*232\nfor EDI Enhancements.\n\n
\nCODE TEXT DESCRIPTORS\n\n
\nCSA screen performance enhancements and improve message handling of \nentries in file 361 - IB BILL STATUS MESSAGE.\n\n
\nPATCH OVERVIEW\nintroduced in a phased implementation strategy. This deployment strategy \nschedule adjustment is entered. These are optional and will be sent in \nthe NCPDP transmission.\n \n7. To assist with the posting of payments, the API used to look \nup bills to post payments in the Accounts Receivable package has \nbeen updated to allow for input of the ECME number.\n \n \nTechnical Description\n---------------------\nwas utilized due to the complexity of the functionality and the number of \nIB20P223 is an environment check to ensure that the site has 4 national \nrate types defined. If the rate types are not defined, a site will need \nto defined them prior to install. The 4 rate types are:\n CHAMPUS (or TRICARE)\n CHAMPUS REIMB. INS. (or TRICARE REIMB. INS.)\n CHAMPVA\n CHAMPVA REIMB. INS.\nIf your site does not have the exact spelling as shown above, you should \ncontact EVS for assistance. Your site may have them defined but the \nnames may have been changed.\nproduct line dependencies.\n \nThis routine also has a post install that will add two reasons not \nbillable. They are:\n HEAD/NECK CANCER\n COMBAT VETERAN\n \nIBCRCC has an optional parameter in the RATECHG line tag of FEE. If this \nparameter is passed by reference, the API will return any Administrative \nFee and Dispensing Fee amounts for the Rate Schedule.\n \n \nIBCREE has been modified to capture the Administrative Fee and Dispensing \nFee, if appropriate. The Rate Schedule adjustment must have an amount \nadded in the calculation of the adjustment for the fee questions to be \nasked.\n \nIBCRU3 has been modified to add a new entry point to look up the event \npointer based on a rate type.\n \nIBJTCA1 is included to add enhancements to the Third Party Joint Inquiry \nto display new information that relates to ECME claims.\nThe first release of this two part implementation is BPS*1*0, comprised \n \nIBNCPDP is the main API routine to be used by Outpatient Pharmacy. All \nnew APIs will be supported with this routine.\n \nIBNCPDP1 will handle the initial call by Outpatient Pharmacy. This \nroutine will load the prescription information to Claims Tracking, look \nup insurance information, verify active pharmacy coverage and return the \nnecessary billing information so that a NCPDP claim can be produced.\n \nIBNCPDP2 will handle all response information sent from Outpatient \nof the new Electronic Claims Management Engine (ECME) package (in the BPS \nPharmacy. This routine will create bills, authorize bills, audit bills, \nadjust bills, cancel bills and ensure that the claims are updated in \nClaims Tracking.\n \nIBNCPDP3 will handle Average Wholesale Pricing updates.\n \nIBNCPCPU will be a utility routine for all the NCPDP billing needs in IB.\n \nIBRFN has been updated to allow for input of an ECME number when posting \npayments in the Accounts Receivable package. The API for AR will now \nnamespace), plus the patches PSS*1*81, IB*2.0*223, IB*2.0*251, and \nreturn the type of lookup found.\n \nIBRUTL is being included to suppress the third party billing bulletin when\na first party bill goes on hold for third party billing and the bill has\nalready been billed using the ECME software.\n \nIBTUTL1 has been modified to accept an additional optional parameter in \nthe REFILL line tag for the EARLIEST AUTOBILL DATE. If the new parameter \nis specified in the call, that date will be used instead of the existing \nfunctionality.\nPRCA*4.5*202, which are listed here in order of installation. BPS*1*0 is \n \n \nCOMPONENTS SENT WITH PATCH\n--------------------------\n The following is a list of the routine(s) included in this patch. \n The second line of each of these routine(s) will look like:\n \n <tab>;;2.0;INTEGRATED BILLING;**[patch list]**;21-MAR-94\n \n CHECK^XTSUMBLD results\na dormant release that only allows each site to perform preliminary setup \n \n Routine Before Patch After Patch Patch List\n ------- ------------ ----------- ----------\n * IB20P223 N/A 2185163 223\n IBCRCC 7424137 7476482 52,80,106,138,245,223\n IBCREE 20456836 21593159 52,106,115,223\n IBCRU3 5450420 6652039 52,106,223\n IBJTCA1 16164807 16640403 39,80,106,137,223\n IBNCPDP N/A 355298 223\n IBNCPDP1 N/A 13353250 223\nwork and to confirm that the software does not adversely affect other \n IBNCPDP2 N/A 16386559 223\n IBNCPDP3 N/A 758252 223\n IBNCPDPU N/A 8111193 223\n IBRFN 4021093 6787815 52,130,183,223\n IBRUTL 3925983 4993649 70,82,132,142,176,179,202,223\n IBTUTL1 5460777 6092014 13,223\n \n Total number of routines - 13\n \n \n---------------\npackages.\n * NOTE: THIS ROUTINE WILL BE AUTOMATICALLY DELETED AFTER INSTALL.\n \n \n Data Dictionary Changes:\n \n UP SEND DATA USER\n DATE SEC. COMES SITE RSLV OVER\nFILE # NAME DD CODE W/FILE DATA PTS RIDE\n------------------------------------------------------------------------------\n \n \n361.1 EXPLANATION OF BENEFITS YES NO NO NO\nPartial DD: subDD: 361.1 fld: .14\n \n DATA SCREEN:\n \n363 RATE SCHEDULE YES NO NO NO\nPartial DD: subDD: 363 fld: 1.01\n fld: 1.02\n DATA SCREEN: \n \nThere are two main areas addressed by BPS*1*0:\n399 BILL/CLAIMS YES NO NO NO\nPartial DD: subDD: 399 fld: 460\n fld: 461\n DATA SCREEN: \n \n \nSOFTWARE AND DOCUMENTATION RETRIEVAL\n====================================\nThe software for this patch is being distributed in host file \nBPS_1_0.KID. The host file will contain seven KIDS builds.\n \nThe builds contained in the BPS 1.0 multi-package distribution are:\n \n Package Patches\n ------- ----------------------\n ECME BPS*1.0*1\n Pharmacy Data Management PSS*1.0*81\n Integrated Billing IB*2.0*223, IB*2.0*251\n Accounts Receivable PRCA*4.5*202\n \n \na. Registration of the Pharmacy with the Vitria BusinessWare IE.\nPlease refer to the 'Software and Documentation Retrieval' section of the \nBPS*1.0*1 patch description for instructions on how to acquire the patch \nsoftware and documentation.\n \n \nINSTALLATION INSTRUCTIONS\n==========================\n \n1. Use VA FileMan to add the new domain, EPHARMACY.VITRIA-EDI.AAC.DOMAIN.EXT, \nto the DOMAIN file (#4.2). The installation instructions are included in \nb. The Insurance Matching of Group Plans with Pharmacy Plans\nthe patch description for the XM*DBA*160 patch. This domain must be in \nplace before the installation of the IB*2*251 patch that is included in \nthe BPS 1.0 Master Build.\n \n2. Download the KIDS file BPS_1_0.KID via FTP. This file needs to be \nretrieved in ASCII format.\n \n3. Review mapped sets for the PSS*, IB*, and PRCA*namespaces. If the \nroutines are mapped, they should be removed from the mapped set at this \ntime.\n \n \n4. From the Kernel Installation & Distribution System menu, select the \nInstallation menu.\n \n5. From this menu, select the Load a Distribution option. When prompted \nfor a file name, enter \nthe directory name where you FTPd the build, followed by BPS_1_0. In our \nexample, the file name is USER$:[ANONYMOUS]BPS_1_0.KID. Determine the \nlocation where you stored your build to decide the correct file name \nentry.\nFollowing the installation of BPS*1*0, each site must register their \n \n6. At the "Want to Continue with Load? YES//" prompt, enter YES.\n \n7. At the "Want to RUN the Environment Check Routine: YES//" prompt, \nanswer YES.\n \n8. From this menu, the installer may select to use the following options:\n \n(When prompted for INSTALL NAME, enter BPS 1.0)\n \npharmacy with Vitria and match applicable insurance group plans using the \n a. Backup a Transport Global - This option will create a backup \nmessage of any routines exported with the patch. It will NOT backup any \nother changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - This option will \nallow you to view all changes that will be made when the patch is \ninstalled. It compares all components of the patch (routines, DDs, \ntemplates, etc.).\n \n c. Verify Checksums in Transport Global - This option will ensure the \ninsurance matching screens. These processes are detailed in the HIPAA \nintegrity of the routines that are in the transport global.\n \n9. At the "Select Installation Option:" prompt, enter 6 Install Package(s)\n \n10. At the "Select INSTALL NAME:" prompt, enter BPS 1.0.\n \n11. When prompted, "Want KIDS to Rebuild Menu Trees Upon Completion of \nInstall? YES//" respond NO.\n \n12. When prompted, "Want KIDS to INHIBIT LOGONs during the install? \n \nNCPDP CONNECTION FOR EDI PHARMACY INSTALLATION GUIDE and the MATCH GROUP \nYES//" respond NO.\n \n13. When prompted, "Want to DISABLE Scheduled Options, Menu Options, and \nProtocols? YES//" respond NO.\n \n14. When prompted, "Device:Home//" respond with the correct device and DO \nNOT queue this to P-Message.\n \n15. If routines were unmapped as part of step 3, they should be returned \nto the mapped set once the installation has run to completion. \nPLANS WITH PHARMACY PLANS document. Both of these documents are located \non the anonymous directory. It is very important that the IRM or person \ninstalling the patch at each facility provide a copy of these documents \nto its ADPAC(s) and any other relevant staff who will be responsible for \nregistering their pharmacy with Vitria and completing the insurance \nmatching process.\n \nAt a later date, additional HIPAA NCPDP patches will be released to \nactivate all of the HIPAA NCPDP functionality. Until that time, sites \nThe Healthcare Insurance Portability and Accountability Act National \nwill not be able to electronically submit claims utilizing this new \nfunctionality.\n \nThe HIPAA NCPDP project was created in response to a Chief Business \nOffice (CBO) request for modifications to several Veterans Health \nInformation Systems and Technology Architecture (VistA) software \napplications in accordance with HIPAA Electronic Data Interchange (EDI) \ntransactions and NCPDP mandated format standards, specifically the NCPDP \nTelecommunication Standard v.5.1.\n \nCouncil for Prescription Drug Programs (HIPAA NCPDP) initiative, whose \nThe specific functionality for this patch is listed below.\n \n \nFunctional Description\n----------------------\nThis patch adds the necessary enhancements to the Integrated Billing \npackage to support NCPDP (National Council for Prescription Drug Programs)\nbilling of pharmacy claims via the Outpatient Pharmacy package.\n \nThe features are:\nultimate goal is to provide functionality allowing electronic \n \n1. When a patient is issued medication via Outpatient Pharmacy, \nOutpatient Pharmacy will check with Integrated Billing (IB) to determine \nif the prescription is NCPDP billable to a third party payer. The patient\nmust have active, reimbursable insurance that covers prescriptions as\nspecified in the patient's group policy coverage limitations. The \nprescription must not be for OTC or research medications and must not be \nrelated to SC (Service Connected), AO (Agent Orange), IR (Ionizing\nRadiation), EC (Environmental Contaminants), HNC (Head/Neck Cancer), CV\n(Combat Veteran), or MST (Military Sexual Trauma).\ntransmission of Outpatient Pharmacy (OP) prescription claims to payers \n \n2. A check will be done to see if the site's Claims Tracking module is \nturned on for prescriptions. When it is, the appropriate information \nwill be entered into that module in IB. To ensure that the Autobiller \ndoes not bill the prescription on a paper claim until the electronic \ntransmission can be processed, the EARLIEST AUTOBILL DATE will be set for \n60 days into the future. If the claim is not processed or resolved in \npharmacy within 60 days, then a paper claim will be automatically \ngenerated.\n \nand the receipt of claim responses (including drug utilization review \n3. If the bill for the prescription is approved by the third party \ninsurance carrier for payment, Outpatient Pharmacy will make a second \ncall to IB. At that time, IB will create a bill in the BILL/CLAIMS \n(#399) file for the amount of the total charge. The bill will be \nautomatically authorized and passed to Accounts Receivable (AR). IB will \nhave AR automatically audit the receivable and post a decrease adjustment \nso that the amount of the outstanding receivable will be equal to the \namount of payment expected from the payer.\n \n4. If a prescription bill is rejected, Outpatient Pharmacy will make a \nresponses and warnings) on a real-time basis, is being developed and \nsecond call to IB. Assuming Claims Tracking is active for prescriptions, \nIB will check to make sure the prescription is in Claims Tracking. The \nClaims Tracking entry will be picked up by the Autobiller to ensure \nproper follow-up is done.\n \n5. If a prescription bill is reversed in Outpatient Pharmacy, both the \nbill and receivable will be cancelled.\n \n6. To support claims other than Reimbursable Insurance for Veterans, IB \nwill ask for both the Administrative Fee and Dispensing Fee when a rate \n\n
\nThe Healthcare Insurance Portability and Accountability Act National \n \nThe first release of this two part implementation is BPS*1*0, comprised of\nthe new Electronic Claims Management Engine (ECME) package (in the BPS \nnamespace), plus the patches PSS*1*81, IB*2.0*223, IB*2.0*251, and \nPRCA*4.5*202, which are listed here in order of installation. BPS*1*0 is a\ndormant release that only allows each site to perform preliminary setup \nwork and to confirm that the software does not adversely affect other \npackages.\n \nThis is the IB*2.0*251 patch and it provides modified and new components \nCouncil for Prescription Drug Programs (HIPAA NCPDP) initiative, whose \nassociated with the following specific requirements:\n* Send Interface Version Number in e-IIV Registration Message.\n* Update Pharmacy Benefits Manager (PBM) Table\n* Update NCPDP Processor Table\n* Update Payer Table\n* Update Plan Table\n* Update Pharmacy Plan Table\n* Provide Pharmacy Plan NCPDP Claim Submission Status and Information via\nCallable Routine\n* Display Pharmacy Plan Information Based on User Selected Sort Criteria\nultimate goal is to provide functionality allowing electronic transmission\n* Display Qualified Group Plans to Help Link Pharmacy Plan to Group\nInsurance Plan\n* Link Pharmacy Plan to Group Insurance Plan\n* Link Pharmacy Plan to Multiple Group Insurance Plan\n* Link Test Payer Sheet to Pharmacy Plan\n* Edit Pharmacy Benefits Manager (PBM) Local Active Flag\n* Edit NCPDP Processor Local Active Flag\n* Edit Payer Local Active Flag\n* Edit Plan / Pharmacy Plan Local Active Flag\n* Edit HIPAA NCPDP Flag\nof Outpatient Pharmacy (OP) prescription claims to payers and the receipt \n* Store and Track Banking Identification Numbers (BIN) and Processing\nControl Numbers (PCN) From Patient Insurance Cards\n \nThe Vitria Interface Engine (IE) BusinessWare product will be utilized in \nthis project. The IE will provide:\n* HL7 message routing tables for directing incoming and outgoing VistA\nHL7 messages\n* HL7 message translation mechanisms for handling various versions of\nVistA compatible HL7 messages\n* HL7 message error handling capability\nof claim responses (including drug utilization review responses and \n* Data mapping utility\nwarnings) on a real-time basis, is being developed and introduced in a \nphased implementation strategy. This deployment strategy was utilized due \nto the complexity of the functionality and the number of product line \ndependencies.\n\n
\nThis patch contains the functionality to begin electronically requesting\nand receiving MEDICARE REMITTANCE ADVICE (MRA) from MEDICARE for those\npatients who have MEDICARE coverage as well as other coverage that is\nsecondary to MEDICARE. See the patch module and release notes that\naccompany this patch for further documentation.\n\n
\nThis patch removes the printing of the SSN from the UB92 and the HCFA\n1500 claim forms when they are printed locally.\n\n
\nMRA (Medicare Remittance Advice) Enhancements\n6. Remove redundant code; Fix state for license # extract for Non-VA \nproviders (IBCEF71)\n7. Move the Medicare assigned number 670899 hospital provider number and \nprofessional provider number to the new location in file 355.92. Only \nthe MEDICARE (WNR) entry is modified.\n8. Restore changes to billing screen 5 when the principle diagnosis is \nmissing. The field prompt will tell the users if the diagnosis code is \nrequired or not. It will say either UNSPECIFIED or UNSPECIFIED [NOT \nREQUIRED].\n9. Set the 837 test transmission queue to be "MCT".\n \n10. Add a new IB edit so that the subscriber's date of birth must exist \nfor all insurances on the claim.\n11. When cloning an MRA bill and manually changing the payer sequence to \nbe secondary, update the CLAIM MRA STATUS field to indicate that an MRA \nis not needed for this new claim.\n12. Fix a hard error when accessing the non-VA provider add/edit\nfunctionality using the option NON-VA Facility Data [IBCE PRVNVA FAC EDIT].\nThe error occurs because the code is used by both list manager and option\nfunctions and the list manager variables are not set in the option call.\nThe fix is to make the calls to the list manager specific code conditional\n1. Allow Medicare to populate the "AE" x-ref in the Bill/Claims file\non it being called via a list manager action. (IBCEP8)\n13. Cancelled claims cannot appear on the CSA screen.\n2. Allow Denied MRAs for duplicate claim/service to be screened off of \nthe MRA management worklist\n3. Correct the MRA Statistics report for the auto-generated claim data\n4. Fix the person/non-person indicator for Fee Basis providers (File \n364.7/ien's 1034-1037)\n5. Fix the period in names to correct suffix problem (IBCEFG1)\n\n
\nThis patch is a re-release of IB*2.0*256 to standardize existing\nVistA Integrated Billing calls. All direct IB touch points will\nbe replaced with standard API's available to all VistA packages.\nThis patch is enhancing the API call INSUR^IBBAPI that\nreturns Insurance information.\n\n
\nThis is patch IB*2*60 for the Integrated Billing package. This patch\nsupports the Ambulatory Data Capture requirements for 10/1/96, as well as\nthe release of PCE.\n \nPlease see the National Patch Module description for this patch for more\ndetailed information.\n\n
\nSTOP CHARGING CHAMPVA SUBSISTENCE\n\n
\nThis patch installs the CY-2005 Medicare Deductible rate and the\nbase pension rates for determining co-pay exemption.\n\n
\nUpdate to insurance API and Insurance Clean Up\n\n
\nThis patch contains the following changes:\nproviders.\n \n1. Adds a parameter to the insurance company to specify whether the\nprovider's SSN is to print on the HCFA and the UB92.\n \n2. Adds the capability to override the GROUP# field on transmitted claims.\n \n3. Fixes a problem where the ?ID action on screen 8 of the edit bill\nscreens displays the wrong provider type for other than attending/rendering\n\n
\nMRA ISSUES RESOLUTIONS AND BUG FIXES\n range are included in this report.\n \n2. If a professional claim already exists, prevent the creation of a new\nprofessional claim when requesting an MRA for an institutional claim. \nThe payer sequence of the existing professional claim was changed to be a \nsecondary claim and thus VistA was not detecting it. The change in this \npatch removes the check on the payer sequence in the case of MRA claims.\n \n1. MRA statistics report changes.\n 1a. Include totals for all divisions or all selected divisions when\n more than 1 division is included in the report.\n 1b. Corrected a bug in which MRA request transmissions on the same date\n as the ending date for the report were not being counted.\n 1c. Corrected a bug in which MRA secondary transmissions were being \n counted. Now, only MRA request transmissions during the report date\n\n
\nThis patch addresses the following NOIS messages:\n------------------------------------------------\nBAY-0204-31962 IIV inquiries are increasing\nFGH-0304-32103 Important IIV Msg-Monetary Amount\nUNY-0204-11346 ERROR - CHK+23^IBCNEHLQ\nWPB-0904-32212 ERROR - EN+43^IBCNEDE2:1, %DSM-E-NULLSUBSCR\n \nThis patch also includes several enhancements for the IIV interface.\n\n
\nThis patch distributes the latest DRG Reasonable Charges files.\nThis is Version 2.3 with an effective date of 01/01/2005.\n\n
\nReasonable Charges v2.2. Enhancements only, no charges.\n\n
\nPatch IB*2.0*298 is the release of the Reasonable Charges v2.4 update.\nThese charges are effective 04/11/2005.\n\n
\nThis patch corrects invalid Care Unit combination pointers if any exist.\n\n
\nInsurance updates and changes.\n\n
\nThe purpose of this patch is to update VistA DSS Stop Codes for outpatient\n Clinic Stop Description Effective Billable Override\n Code Date Type Flag\n ----------- --------------------- ---------- ------------ ---------\n 533707 SMOKING CESSATION IND 05/02/2005 Non-Billable Y\n 566707 SMOKING CESSATION GRP 05/02/2005 Non-Billable Y\n 707 SMOKING CESSATION 05/02/2005 Non-Billable Y\ncopay in the IB CLINIC STOP CODE BILLABLE TYPES file (#352.5), which \nbegins May 2, 2005. The required copay for the smoking cessation\ncounseling (individual and group) codes will be changed to a non-copay\nstatus.\n \nThe patch will update the billable type for the following stop codes in\nthe file.\n \n\n
\nCMAC 2005\n\n
\nCBO Data Extract enhancements\n \nRoutine IBJVDEQ\nMake sure the claim has been authorized before proceeding with the \nextract.\n \nRoutine IBRFN4\nProvide a callable API for IB information.\n\n
\nRoutines: IBCE837, IBCE837A\n Allows selection of existing batches or individual claims to be\n #1006 (changed data element, ins type OI1-17)\n #1015 (changed data element, version info GEN-7)\n #1039 (new entry for current payer sequence CI1-14)\n #1040 (new entry for MRA secondary indicator CI1-15)\n \nEntries modified in file 364.6:\n #1321 (new entry for current payer sequence CI1-14)\n #1322 (new entry for MRA secondary indicator CI1-15)\n \nNew File: 361.4 EDI TEST CLAIM STATUS MESSAGE\n re-submitted as test claims from the original EDI resubmit bill/batch\n Holds the test transmission and all test status messages received in\n the test queue (MCT) for claims resubmitted as test.\n \nNOIS ENTRIES INCLUDED:\nUNY-0205-10041 SYNTAX ERROR 1/31 -MISSING LCOB-02\nLEX-0205-40005 SYNTAX ERROR 1/27 - LCOB/LCAS Prob.\n options.\n \nRoutine: IBCNSGE\n Insurance Company EDI Parameter Report\n \nRoutine: IBCEF2\n Pull the id from the insurance company file if the claim is an MRA \n secondary and the id exists. If there is no id, force PPRNT or IPRNT. \n Changes to allow test claims to be resubmitted from previously\n \nRoutine IBCEF21\n Two procedures moved out of IBCEF2 and into IBCEF21 for space.\n \nRoutine: IBCEF31\n Ensure that the electronic insurance type field for the Medicare (WNR) \n entry is always 3:MEDICARE. This is the 3.09 field in file 36.\n \nRoutine: IBCEF4\n Change to return a true value if the claim is being resubmitted as a\n transmitted claims.\n test claim.\n \nRoutine: IBCEF\n Bug fix to the $$NOPUNCT function. Allow the exclusions parameter to \n function properly.\n \nRoutine: IBCBB2\n Change to allow 8 diagnoses codes. \n \nRoutine: IBY296PR (new) (pre-install)\n \n Pre-install changes the data element for entry #1015 in file 364.7\n \nRoutine: IBCERPT\n Changed to output " * * TEST RESULTS * * " on reports from the MCT queue\n \nRoutine: IBCEPTU (new)\n Utility code added to allow lookup of last transmitted date when a\n transmission entry is deleted for an entry in file 361.4\n \nRoutine: IBCEPTR\nRoutines: IBCESRV\n Report of data stored in file 361.4.\n \nRoutine: IBCESRV, IBCESRV2\n Changed to capture the MCT messages for claims resubmitted for test and\n send them to be stored in the new test claim message file\n \nRoutine: IBCEPTM (new)\n Stores the transmission and test status message data in file 361.4\n \nRoutines: IBCEPTC, IBCEPTC1, IBCEPTC2 (new)\n Changes server logic for reports to send test message flag if msg\n New routines for the list manager display and resubmission of\n previously transmitted claims as test claims.\n \nRoutine IBCE\n Modify the IB nightly job section to call the Purge routine for file \n 361.4.\n \nRoutines IBCEU0, IBCEU1\n Fix LCOB segment pieces (modifiers and payer id)\n \n received in test queue.\nRoutine IBCEOB1\n Fix split MRA filing problem. Keep track of VistA line numbers across \n multiple split MRAs in file 361.1.\n \nRoutine IBCCC2\n Remove the code which deletes the BILL COPIED FROM field when \n processing an MRA claim into a secondary MRA claim.\n \nRoutine IBCEP0B\n Added a new parameter to the call PARAMS^IBCNSC1 to fix an undefined \n \n variable error that was occuring as a result of Patch 291. \n \nRoutine IBCERP3\n Report of bill batches waiting Austin receipt more than 1 day. \n Modification to routine to make it more similar to routine IBCEBUL by \n checking to see if there are any bills in the batch before including it \n on this report.\n \nRoutine IBCERP5\n Modify the batch status detail report to show claims from test batches \nRoutines: IBCEM01, IBCEM02, IBCEM03\n stored in file 361.4.\n \nNew field FILE 364.2:\n .14 CLAIM RESUBMITTED TEST\n \nEntries modified in file 364.7:\n #136 (changed entry for group #/group name exclusion CI3-3)\n #137 (changed entry for group #/group name exclusion CI3-4)\n #830 (changed to fix problem with LCOB records)\n #985 (changed to fix problem with LCOB records)\n\n
\nClinical Indicator Data Capture IB support.\n\n
\nThis patch will replace all the direct global references to Pharmacy data\nin the Integrated Billing package. The direct references will be replaced\nwith API calls to the Pharmacy package.\n\n
\nCLAIMS TRACKING ENHANCEMENT\n\n
\nThis patch will address two issues;\n1. The Re-Generated Unbilled Amounts Report that is printing the CPT IEN \ninstead of the CPT Code.\n2. The Undefined error received while using Assign Reason Not Billable \n[IBT EDIT REASON NOT BILLABLE] option.\n\n
\nPFSS ACCOUNT FILE\n\n
\nWhen 'ACCEPTING' entries from the insurance buffer, it was discovered\nthat some of the GROUP/PLAN fields (#.04 thru # .09) in the INSURANCE\nBUFFER (#355.33) were not being updated in the INSURANCE file (#355.3).\nUpon further review, a coding problem was found and corrected in the\nINSURANCE BUFFER routine IBCNBMI.\n\n
\nThis is the first in a series of patches to address changes that must be\nmade to MCCR software (Integrated Billing and Accounts Receivable) in\norder to implement General Counsel opinion VAOPGCPREC 3-96. \n\n
\nThis patch will install the October 2005 Tortiously Liable, Cost-Based\nand, Interagency rates into the Charge Master, with an effective date \nof 10/01/05.\n\n
\nThis patch updates the Reasonable Charges files and distributes them with \na new version number and new effective date.\n\n
\nTHIS PATCH WILL CHANGE THE MEDICATION COPAY TO $8 AND THE ANNUAL CAP\nTO $960 EFFECTIVE JANUARY 1, 2006\n\n
\nVISTA-OFFICE EHR FILE ENHANCEMENT\n\n
\nThis patch will install the November 2005 Tortiously Liable, Cost-Based\nand, Interagency rates into the Charge Master, with an effective date \nof 11/03/2005.\n\n
\nCMAC 2005 update for 'Non-Facility' charges.\n\n
\nPatch attends to the following issues:\n \n3) Based on a decision from the VA Chief Business Office, it was decided \nthat the most popular payer function should be removed. Any mention of \nthis functionality should be eradicated from the IIV system.\n \n4) IIV routines will automatically disable and enable journaling itself \nwhile doing the purge. A log of purges will now be kept in global ^ \nXTMP("IBCNEKIT".\n \n1) To help protect the users from sending out too many IIV inquiries in a \ngiven day, the HL7 MAXIMUM NUMBER field has been modified to be a \nrequired field.\n \n2) To help protect the users from extracting too many IIV inquiries in a \ngiven day for a given IIV data extract, the MAXIMUM EXTRACT NUMBER field \nhas been modified to be a required field.\n\n\nAdd SERVICE CONNECTED BILLABLE APPOINTMENT TYPE (#352.1) to correspond \nto the new SERVICE CONNECTED APPOINTMENT TYPE (#409.1) released by \nSD*5.3*394.\n\n
\nThis patch is the IB part of PFSS.\n\n
\nCoordination of Benefits patch.\n\n
\nThe main purpose of this build is to restructure the way the HL7 messages\nare created for IIV. In addition to encoding and decoding of HL7\ndelimiters, asterisks will be removed from the data prior to transmission\nof the HL7 messages since asterisks are X12 delimiters. The build also\nremoves the application dependency of the IIV interface on the IP address\nand port number for routing. Thus, making DBIA #4241 obsolete.\n\n
\nPatch IB*2.0*334 is the release of the Reasonable Charges v2.6 update.\nThese charges are effective 01/01/2006.\n\n
\nIn preparation for the e-Pharmacy software package, insurance\nstaff need to match their pharmacy group plans to the appropriate\nVA National Plan. (For more detailed background information\nregarding this matching process, please refer to the web site\nhttp://vaww.vistau.domain.ext/VistaU/e-bp/e-pharmacy.htm and\ndownload the e-Pharmacy Claims Insurance Process User Guide\nThere is other information available at this web site that you\nwill find helpful regarding the e-Pharmacy project.)\n\n
\nThis patch modifies the Claims Tracking software to accept same date/time \nentries.\n\n
\nPharmacy Claims Tracking fix related to CIDC (patch IB*2.0*260)\nReason Not Billable will now be assigned appropriately for items\nentered prior to the CIDC patch.\n\n
\nPatch IB*2*340 contains a single routine that supports the\nimplementation of patch PRCA*4.5*241. This AR patch is the\nlast in a series of patches that adjusts the accounts of\nveterans affected by Hurricane Katrina. Please refer to the\npatch description for more specific information on patch\nIB*2*340.\n\n
\nTHIS PATCH WILL ADDRESS SEVERAL BUGS RELATED TO E-MRA.\nTHESE BUGS ARE INCLUDED IN THE PATCH DESCRIPTION WITH THEIR RESPECTIVE\nREMEDY TICKETS.\n\n
\nHIPAA NCPDP Global project\n \nsupports the electronic transmission outpatient prescription claims and \nbilling collection and management.\n\n
\nThis patch is the inter-facility copay part of the PFSS project.\n\n
\nYear 2000 changes.\n\n
\nThe purpose of this patch is to add a value code of 'A0' (Special Zip\nCode Reporting) to the MCCR Utility file (#399.1).\n\n
\nWhen the site executes the [IB COPY AND CANCEL] option, an undefined error\ngenerates at line <UNDEFINED>OUTPT+89^IBCEF11.\n\n
\nModify IB to handle the billing of the new and updated Treating Specialties\nbeing released, primarily for NHCU. This patch supports DG*5.3*683.\n\n
\nThe Chief Business Office has requested to update the DSS Stop Codes\nto reflect the FY 06 Co-pay rates.\n\n
\nThis patch addresses one issue. The issue is about the batch which \ndidn't process through the outside trading partner WebMD when the claim\nwas missing the procedure for the modifier on the institutional service\nline.\n\n
\nPrevents a claim from being an MRA request claim when Medicare (WNR) is \nthe secondary insurance and prevents the deletion of MRA secondary \ninsurance.\n\n
\nIB SUNSETTING OF OPTIONS\n\n
\nADD NEW ADJUSTMENT CODE TO AUTO BILL GENERATION LIST\n\n
\neClaims Plus Iteration 2\n\n
\nCompanion patch for PRCA*4.5*232 - Vista AR IB extract -phase II -part II.\n\n
\nRequired for special processing of file 351.1 for patient merge.\n\n
\nThis patch will correct a problem where the nightly billing job\nwas failing when voice activated records from Radiology had\ntriggered an entry into billing file #350 and had left the \nUSER ADDING ENTRY field null. The changes in this patch will\ntrap that condition and store the Postmaster DUZ rather than null.\n\n
\nThis patch supports the National Council for Prescription Drug Programs \nthat will enable the user to reopen a closed Electronic Claims Management\nEngine (ECME) claim; updates to the Rx Activity Log; and permanent storage\nof Claims activity information as reported by the ECME Billing Events\nReport.\n(NCPDP) standard which was adopted under the Healthcare Insurance\nPortability and Accountability Act (HIPAA) for pharmacy claims. This patch\nis one of six to be released. Three patches will be released in a KIDS\nmulti-build distribution containing: BPS*1*3, PSO*7*247, and IB*2*342. \nThree patches will be released individually and they are: PRCA*4.5*247,\nPSX*2*62, and PSS*1*115.\n \nEnhancements included in the release of the six patches are a new option \n\n
\nUPDATE VALID GROUP NUMBER VALUES & ADD NEW ADJUSTMENT CODE TO AUTO\nBILL LIST\n\n
\nREASONABLE CHARGES V2.7 UPDATE\n\n
\nThis patch addresses two issues. The first issue is regarding the \nAutomated Biller not billing the legitimate Claims Tracking entry when \nthe answer to the NEED RELATED TO OCCUPATION or the NEED RELATED TO AN \nACCIDENT field for the patient is UNKNOWN or NULL.\n \nThe second issue is about a syntax error that site encountered when they\nwere trying to compile routine IBCSC4B in Cache.\n\n
\nThis patch addresses 2 issues. The first is that site requested to change\nthe heading "Last test date" to "Last RX Copayment Exemption date" in the\nDG Patient Inquiry option to match up to the data. The second issue is\nabout a bug behind discovered in the IB's IVM backbilling functionality.\nIf the veteran has an appointment in a billable clinic but also has a non\nbillable stop code added, charges are not being generated.\n\n
\nREASONABLE CHARGES V2.8 UPDATE\n\n
\nThis patch will distribute 3 DSS Stop Codes:\n197 - POLYTRAUMA INDIVIDUAL\n198 - POLYTRAUMA GROUP\n199 - TELEPHONE/POLYTRAUMA\nwhich will be added to IB CLINIC STOP CODE BILLABLE TYPES [#352.5].\n\n
\nIB*2.0*61 Regional Counsel Interface\n\n
\nThe Chief Business Office has requested to update the DSS Stop Codes\nto reflect the FY 07 Co-pay rates.\n\n
\nNPI Modifications for the IB Package\n\n
\nNew CMS-1500 claim form\n\n
\nReasonable Charges v2.9\n\n
\nThis Maintenance Update addresses the following issues reported in Remedy:\n 9) HD118376 - MRA Filing Error\n 123700 - Message storage errors on bill.\n10) HD131138 - Missing Mail Group - CMOP transmissions fail.\n11) HD134835 - Insurance Buffer Error\n 131701 - Error <UNDEF>BR+1^DIE0\n12) HD137911 - <UNDEFINED>BULL1+5^IBTUBUL\n 145085 - Error Running Send Test Unbilled Amounts Bulletin option\n 1) HD63676 - Non Providers Not Screened in Procedures Multiple\n 2) HD64317 - IB315 entry file 350.8/*232\n 3) HD64380 - Held Charges Report (PTH-1104-20448)\n 4) HD64425 - PROVIDER ID QUERY REPORT - TOTAL IS WRONG\n 5) HD64697 - ADD OUTSIDE LAB CHARGES TO MAP\n 6) HD64863 - IBJDF51 Spreadsheet (Trans # creates problem)\n 7) HD65904 - Problem with Miscellaneous Bills Follow-up Reports\n 8) HD117969 - CHAMPVA/TRICARE Follow-Up Report Detail vs. Summary problem\n\n
\n1. Additional Source of Information Codes in Insurance Buffer and \n4. Reduce the number of blank inquires being sent via Remote Query.\n \n5. Auto-Populate the Patient Insurance file with the patient's DOB & \nSSN information at processing time.\n \n6. Replace Payer ID with Payer Name to improve readability of the \nBuffer entry error information.\n \n7. Correct the totals for companies without National IDs in the eIV \nStatistical Report.\nPatient Insurance File.\n \n8. Bypass new buffer entry creation upon message response by \nverifying if the buffer entry has been previously accepted.\n \n9. The CBO extract was modified to transmit SOI codes with a value\ngreater than '4' without resetting them to a value of '1' (Interview).\n \n10. Modify Response Report to Display Benefit Status as well as all\nnotes associated with benefit.\n \n2. Modifications to existing Pre-Registration Report to remove \nhard-coding and allow SOI Code selection.\n \n3. Include missing patient name in buffer file when processing \nmessage responses.\n \n\n
\nIB implementation of Project 112/SHAD Classification.\n\n
\nUB-04 claim form.\n\n
\nThis patch is being released in conjunction with the Pharmacy \nReengineering Encapsulation effort. While no new functionality for \nIntegrated Billing package is released with this patch all direct global \nreferences to the Outpatient Pharmacy files have been replaced by this \neffort.\n\n
\nThis patch adds and modifies Stop Codes to the IB CLINIC STOP CODE\nBILLABLE TYPES (#352.5) file, fixes a SUBSCRIPT error in the\nElectronic Error Report and fixes problems in billing where the RX\nCOPAY status is incorrectly flipping from NON-EXEMPT to EXEMPT.\n\n
\nScheduling Conversion Software changes: Integrated Billing's changes to\naccomodate the removal of the Scheduling Visits, Outpatient Diagnosis,\nOutpatient Provider files and their transfer to PCE and the Outpatient\nEncounter file. For more detailed information, refer to the patch\ndescription in the National Patch Module.\n\n
\nThe CBO has requested that these three things be done by this patch. \nFirst, it will automatically update the transmission status for certain \nEDI bills that are authorized but not yet transmitted. Second, the \nCLAIM MRA STATUS field will be updated to 'NO MRA NEEDED' for authorized \nbills if there are no MRAs on file. Third, a list will be produced for \nsites to deal with individually: this list will be of authorized claims \nwith the AR status of other than an active status.\n\n
\nIB*2*364 is being released to support the Treating Specialty changes \nreleased in patch: DG*5.3*729 (Project: PTF Fields No Longer Needed).\n \nTreating Specialties file (#42.4) is being updated by patch DG*5.3*729.\nThis patch IB*2*364 will update Integrated Billing to properly handle the \nbilling of the new and changed Treating Specialties.\n\n
\nThis patch adds a new field for INSURED'S SEX to both the PATIENT file\nand the INSURANCE BUFFER file. A post-init routine will auto-populate\nthis field for existing insurance policies to the best of its ability.\nAll screens that allow adding/editing/displaying of policy holder\ninformation will be modified to use the new field.\n\n
\nThis patch insures that while navigating in the Claims\nTracking Edit Option after the user switches patients \nwhile in the View Patient (VP) menu and returns to the \nlist of the patients claims that the claims that are \nlisted are actually the indicated patients claims. It\nalso adds adjustment code CO 194 to the list of codes\nautomatically processed and modifies function call\nGETWNR^IBCNSMM1 to return only Part A or Part B\nMedicare plans like it is supposed to.\n\n
\nIB API'S to support the SD ASCD (SCAM) project.\n\n
\nIB ENHANCEMENTS\n\n
\nUpdate Stop Codes to reflect Fiscal Year 2008 changes.\n\n
\nThis patch addresses one issue. The Edit Returned Bill option on the \nReturn Bill Menu [IB RETURN BILL MENU] has been modified to only allow \nthe editing of a returned bill if it is not an "electronically\ntransmittable" bill. For returned electronically transmittable \nbills/claims the IB COPY AND CANCEL option will need to be used.\n\n
\nThe general purpose of this patch is to meet the requirements for the \nVistA Integrated Billing (IB) software application in support of the Phase\n4 ePharmacy enhancements, Iteration 1.\n\n
\nPHARMACY ENCAPSULATION API AND EPHARMACY FOLLOW UP PATCH\n\n
\nBILLING LAG TIME REPORT MODIFICATIONS\n\n
\nPatch to enable the processing of new Emdeon reports.\n\n
\nE-CLAIMS PLUS ITERATION 3, PART 1\n\n
\nReasonable Charges v2.11. Charges are effective 10/01/07.\n\n
\n \nUpdate Stop Codes 695 and 696 to add an override flag to prevent charges\nfrom being incurred when they are selected as secondary codes.\n\n
\nPHARMACY NPI FIX\n\n
\n \nAdd the Diabetic Retinal Screening STOP CODE (718) to the IB CLINIC\nSTOP CODE BILLABLE TYPES (#352.5) file.\n\n
\nReasonable Charges v3.1\n\n
\nThis patch includes the Medicare Remittance Advice Survey designed to\nprovide a one time national rollup of back billing potential of Medicare\nSupplimental Carriers.\n\n
\nReasonable Charges v3.0: Remove RC Discounts\n\n
\nPHARMACY NPI FIX (REPLACES IB*2*388)\n\n
\nModifications in this patch will allow users to continue to send out \nnon-fatal warnings when Other, Operating, Supervising, Billing Provider, \nPurchased Service or Lab/Facility taxonomies are missing.\nclaims without taxonomies for type 1 and type 2 providers where the \ntaxonomies are not sent in the 837 transmission from the Financial \nServices Center (FSC) in Austin to the clearinghouse. There is currently \ncode in Vista that will change the warnings that users receive when \ntaxonomies are missing to fatal edits for all providers effective \n05/23/2008, and hence prevent the claims from being submitted. This \npatch will produce fatal edits when the Attending, Rendering or Referring \nProvider taxonomies are missing on or after 5/23/2008. It will produce \n\n
\neClaims Plus Iteration 3, phase 2\n\n
\n \nUpdate Stop Codes 372 and 373 from BASIC CARE ($15 copay) to\nNON-BILLABLE (no copay).\n\n
\nProsthetics Item Replacement.\n\n
\nThis patch is addressing an issue regarding bills not automatically \naudited by the Auto Audit process in Accounts Receivable package.\n\n
\nModifications to allow NPI to be ACTIVE in both the #200 file and the \n#355.93 file at the same time.\n\n
\nThe Chief Business Office has requested to revert the fatal errors\nfor the NPI of the Division and the Service Facility to a warning\nmessage, and also to change a missing Taxonomy of the Billing Provider\nback to a fatal error.\n\n
\nThis is patch IB*2*62 for the Integrated Billing package. This patch\naddresses various nois messages for the package.\n \nPlease see the National Patch Module description for the patch for more\ndetailed information.\n\n
\nSee the National Patch Module for patch details.\n\n
\nUpdate Stop Codes to reflect Fiscal Year 2009 changes.\n\n
\nUpdate the IB CLINIC STOP CODE BILLABLE TYPES file (#352.5) for STOP CODE \n351 with an effective date of 10/10/08 to reflect no copay.\n\n
\nePHARMACY TRICARE/'N'/CT FIX\n\n
\nReasonable Charges v3.2\n\n
\n \nrejection.\nThere are three fixes in this patch: The first issue concerns an undefined\nerror in the Enter/Edit Billing Information [IB EDIT BILLING INFO] option\nwhen site entered a number greater than the default procedure unit which\nis 1. The second issue is that user cannot add charges for FEE LTC OPT\nRESPITE charge in the Cancel/Edit/Add Patient Charges [IB CANCEL/EDIT/ADD\nCHARGES] option. The last issue is when a provider was inactivated in the\nNEW PERSON (#200) file and his person class was no longer valid, IB sent\nan ATT/REND PROV SPECIALTY value of 99 for the provider causing the claim\n\n
\nIn cases where outpatient encounter dates have no time recorded\nit will default to 00.00 to prevent subscript errors.\n\n
\neClaims Plus - Diagnosis Present on Admission (POA) Indicator.\n\n
\nReasonable Charges v3.3\n\n
\nThis patch allows 9 digit zip codes to be transmitted on bills sent\nelectronically to Trailblazers so they will no longer be rejected. \n\n
\nThis patch fixes a number of problems in IB.\nIt fixes a string too long error, print status of a bill, output formatter\nshort timeout on a read command and a post init that does a cleanup\nof file 364.7.\n\n
\nE-PHARMACY ENHANCEMENTS\n\n
\nReasonable Charges Billing Enhancements II\n\n
\nAdd the Disability Evaluation System (DES) exam STOP CODE (488) to the\nIB CLINIC STOP CODE BILLABLE TYPES (#352.5) file.\n\n
\neClaims Additional Claim Form and Transmission Data (EAD)\n\n
\nFee Basis Billing Provider\n\n
\nThis patch is to exclude the MRA's filing errors from the MRA patient\nresponsibility calculation.\n\n
\nIB*2.0*422 is being released to support the Treating Specialty changes \nreleased in patch: DG*5.3*813.\n \nTreating Specialties in the SPECIALTY (#42.4) file are being updated by \npatch DG*5.3*813. This patch (IB*2.0*422) updates Integrated Billing to \nproperly handle the billing of the new Treating Specialties.\n\n
\nThis patch addresses the issue regarding site not receiving the Medicare \nRemittance Advice (MRA) payments as noted on the Bill Status Report. Site\nruns the report on a daily to weekly basis to generate a summary of bill\nrate types and statuses.\n\n
\nThis patch modifies the extract code for the Date Of Similar\nIllness and adds a cross reference to update the "ON\nHOLD DATE" cross reference after a patient merge to stay\nconsistent with the new patients info.\n\n
\nUpdate Stop Codes to reflect Fiscal Year 2010 changes.\n\n
\nChange input transform so that PAST DATES are assumed when entering\nINSURED'S DOB.\n\n
\nReasonable Charges v3.4\n\n
\nThe purpose of this patch is to update the MCCR Utility file and the\nRevenue Code file.\n\n
\nThis build provides three new APIs for the Insurance Capture Buffer \n Group Insurance Plan (#355.3) file\n Patient Insurance Type (#2.312) subfile\n \nThere is also an API (UPDTICB) which will allow for fields that are not \nstored in the insurance buffer to be updated into the IB Insurance Files.\n \nThese APIs are documented in Integration Control Registration (ICR) \n#5353, (Accept/Reject Insurance Buffer data APIs).\n \nThe three new APIs are:\napplication. There are two APIs that are to be used to move Insurance \n \n \n ACCEPAPI^IBCNICB(RESULT,IBBUFDA,DFN,IBINSDA,IBGRPDA,IBPOLDA,IBMVINS,\n IBMVGRP,IBMVPOL,IBNEWINS,IBNEWGRP,IBNEWPOL,IVMREPTR)\n REJECAPI^IBCNICB(RESULT,IBBUFDA,IVMREPTR) \n UPDTICB^IBCNICB (RESULT,DFN,IBPOLDA,IBGRPDA,IBPOLCOM,IBPOLBIL,IBPLAN,\n IBELEC,IBGPCOM,IBFTF,IBFTFVAL)\n \nThis patch removes the Traditional Regular type "B" cross-reference on the\nTYPE OF PLAN (#355.1) file since this cross-reference only contains the\nBuffer (#355.33) file data to other Integrated Billing files or reject \nfirst 30 characters of the NAME (#.01) field. This cross-reference\nlimitation may create problems when using the Fileman DBS calls. A New\nStyle Regular "B" cross-reference will be added that will contain all\ncharacters to the field limit of 40 characters. In a post install the\npatch will build the new "B" cross-reference on the file.\nthis data. These APIs provide a front end into the existing ACCEPT and \nREJECT Insurance Buffer APIs which suppresses all write statements and \ninteractive fileman calls within the existing code.\n \nThe Insurance Buffer (#355.33) file data is moved to the following files: \n Insurance Company (#36) file\n\n
\n2010 RX COPAY THRESHOLDS UPDATE\n\n
\nThere are two fixes in this patch: First, in the Enter/Edit Billing\nInformation [IB EDIT BILLING INFO] option on screen #3, all of the valid \nSUBSCRIBER PRIMARY IDs are now allowed (one that wasn't was the letter \n"A" followed by 6 numbers). Second, there is a fix for a bad\ncross-reference in the GROUP INSURANCE PLAN (#355.3) file.\n\n
\nCorrection to the 2010 Medicare Deductible\n\n
\nIB*2.0*426 is being released to support the Treating Specialty changes \nreleased in patch: DG*5.3*819.\n \nTreating Specialties in the SPECIALTY (#42.4) file are being updated by \npatch DG*5.3*819. This patch IB*2.0*426 updates Integrated Billing to \nproperly handle the billing of the new Treating Specialties.\n\n
\nReasonable Charges v3.5\n\n
\nThis patch addresses one issue regarding new Rate Schedules for the Rate\nTypes of CHAMPVA and CHAMPVA REIMB. INS..\n\n
\nRX COPAY PRIORITY GROUP 7&8 INCREASE\n\n
\nThis build contains the correction to the TOP form on UB92 using output\nformatter.\n\n
\nUPDATE PLACE OF SERVICE FILE (#353.1) WITH 16 NEW ENTRIES.\n\n
\nThis patch addressed two issues. The first issue is to change the\nassignment benefits code for Tricare claims. The second issue concerns a\nprescription charge attaching to a wrong patient.\n\n
\nThis patch contains the ePharmacy enhancements to accomodate\nCoordination of Benefits (COB).\n\n
\nUpdate Stop Codes to reflect Fiscal Year 2011 changes.\n\n
\neIV Phase 3, Iteration 1\n\n
\nReasonable Charges v3.6\n\n
\n2010 RX COPAY THRESHOLDS UPDATE\n\n
\nHIPAA 5010 effort: enhancements 7, 9, and 11\n\n
\nInsurance Buffer File.\n\n
\nAdd Third Party Pharmacy Prescription administrative fee charge to the\npatient bill with the following only Rate Type names of Rate Type File #399.3:\n Reimbursable Ins.\n No Fault Ins.\n Tort Feasor\n Workers' Comp.\n\n
\nUpdate Stop Codes to reflect Fiscal Year 2010 Supplemental changes as \nwell as Fiscal Year 2011 Midyear changes.\n\n
\nReasonable Charges v3.7\n\n
\nThis patch will a include change to routine IBBFAPI (Insurance API \n$$INSUR^IBBAPI) and IBBDOC to add two new additional fields from \nInsurance Company file (#36). These fields are the STREET ADDRESS [LINE \n2] and STREET ADDRESS [LINE 3].\n\n
\nThis patch contains updates to the MCCR Utility (#399.1) file, the Revenue\nCode (#399.2) file and the Place of Service (#353.1) file.\n\n
\nThis patch modifies DSS Stop Codes contained in the Integrated Billing \nClinic Stop Code Billable Type file <#352.5>.\n\n
\nE-billing Iteration 4, Enhancement 6: Preserve Claim Number\n\n
\nFY 2012 DSS STOP CODE UPDATES\n\n
\nFMS 5010 CHANGES\n\n
\nDIAGNOSTIC MEASURES PHASE I/INTAKE REPORTS\n\n
\nCD PATIENT COPAY EXEMPTION\n\n
\nThis patch will install the Tortiously Liable, Cost-Based and Interagency\nrates into the Charge Master, with an effective date of 07/11/2011.\n\n
\nePharmacy Phase 5 - NCPDP D.0\n\n
\nThis patch is about the administrative charge update based on a new\ndispensing fee $12.39 for third party pharmacy prescription claims with\nan effective date of January 1st, 2012.\n\n
\nReasonable Charges v3.8\n\n
\nThis patch contains two issues. The first issue is about the unit price\nof the drug cost with zero resulting in an error message of 'Not ECME\nBillable: Cannot find price for Item'. This error message prevents\nIB from generating third party bills for outpatient prescriptions. The\nsecond issue concerns payment amounts on e-Pharmacy claims which are more\nthan the billed amounts.\n\n
\nThis patch addresses system enhancements to the Integrated Billing \nsoftware as requested by the VA's Chief Business Office (CBO).\n\n
\nVeterans w/Insurance and Opt. Visits option fix for <SUBSCRIPT> error.\n\n
\nFY2012 MIDYEAR DSS STOP CODE UPDATES\n\n
\nePharmacy Phase 6\n\n
\nThis Integrated Billing (IB) patch expands the HIPAA 5010 enhancements \n were bill to the secondary payers on the MRA Statistics Report\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nIB OUTPUT menu Modified\nMANAGEMENT REPORTS \n \nIBCEM NON-MRA run routine New\nREPORT \n \nIB OUTPUT PATIENT menu Modified\n option [IBCEM MRA STATISTICS REPORT].\nREPORT MENU \n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\n \nIB SCREEN5 INPUT BILL/CLAIMS(399) Modified\n \n \nIB SCREEN7 INPUT BILL/CLAIMS(399) Modified\n \nIB SCREEN8 INPUT BILL/CLAIMS(399) Modified\n \nIB SCREEN9 INPUT BILL/CLAIMS(399) New\n \n \nAdditional Information:\n<Additional information sections can be added alphabetically if needed.>\n \n 3. Modify the outbound 837 Heath Care Claims transmissions to \n \nNew Service Requests (NSRs)\n---------------------------- \nNo New Service Requests \n \nPatient Safety Issues (PSIs)\n-----------------------------\nNo Patient Safety Issues \n \nRemedy Ticket(s) & Overview\n incorporate the additional/modified data elements that may be\n---------------------------\nNo Remedy Tickets \n \nTest Sites:\n----------\n<List test sites that actually participated in testing and signed off on \nthe patch. A copy and paste from NOIS displaying the test sites in\nproduction can be used.>\n \n \n added to a claim.\nDocumentation Retrieval Instructions\n------------------------------------ \nUpdated documentation describing the new functionality introduced by this \npatch is available.\n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/. This transmits the files from the first\navailable FTP server. Sites may also elect to retrieve software directly\nfrom a specific server as follows:\n \n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \nDocumentation can also be found on the VA Software Documentation Library \nat: http://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n-----------------------------------------------------------------------\n<Documentation title> \n 4. Modify the printing process for outpatient, UB04 claims to print \n \n \nPatch Installation:\n \n \nPre/Post Installation Overview\n------------------------------\n<Provide a brief overview of what the pre/post installation entails. The\nactual instructions will be listed below in the Installation Instructions\nsection. Note whether pre/post installation routines can be deleted after\n the Priority (Type) of Admission.\nthey run or whether they are automatically deleted.>\n \n \nInstallation Instructions\n------------------------- \n \n ******************************************************************\n * You should install this patch during non-peak hours, when no *\n * Integrated Billing or Accounts Receivable users are on the *\n * system. *\n \n ******************************************************************\n \nThere are no options to disable. \n \nPre-Installation Instructions\n-----------------------------\n<Provide a brief description of what the pre-installation will be doing. \nList pre-installation instructions (i.e., links, filers, or batch\ntransmissions that need to be stopped, jobs unscheduled, etc.), if\napplicable.>\nintroduced in patch IB*2.0*432.\n 5. Modify the printing process for UB04 and CMS-1500 claims to allow \n \n1. Obtain the Patch.\n Obtain the host file PRCA_275_IB_447_16.KID, which contains the\n following two patch installs:\n \n PRCA*4.5*275\n IB*2.0*447\n \n Sites can retrieve VistA software from the following FTP addresses.\n The preferred method is to FTP the files from:\n the printing of Revenue/Procedure codes with zero dollar amounts.\n \n download.vista.domain.ext\n \n This will transmit the files from the first available FTP server.\n Sites may also elect to retrieve software directly from a specific\n server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n \n The PRCA_275_IB_447_16.KID host file is located in the\n anonymous.software directory. Use ASCII Mode when downloading the\n file.\n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following option. When prompted for the INSTALL enter the patch #(ex.\n PRCA*4.5*275):\n \n 6. Modify The Insurance Company Enter/Edit option [IBCN INSURANCE CO \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n EDIT] to allow users to assign additional MEDIGAP policies as Type\n \n4. From the Installation Menu, select the Install Package(s) option and\n choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' \n <Provide the installer with guidance on whether or not menu trees need\n to be rebuilt. For instance the menu trees do not need rebuilt if \n there are no menus involved in the patch or their system rebuilds menu\n trees nightly using TaskMan. If they must answering YES to rebuild\n of Plan for an Insurance Company.\n the menu trees warn them that it could affect users on the system and\n installation times will increase.>\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n \n <to inhibit logons.>\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO// \n \n \n <Provide the installer with guidance on whether or not to disable\n scheduled Options, menu options, and protocols.>\n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0// respond 0.\n \n9. When prompted "Enter the Coordinator for Mail Group 'MDA'"\n \n Enter: \n \n 7. Create a new option called the Non-MRA Productivity Report option \nPost-Installation Instructions\n------------------------------\n \n<Provide a brief description of what the pre-installation will be doing. \nList pre-installation instructions (i.e., links, filers, or batch\ntransmissions that need to be stopped, jobs unscheduled, etc.), if\napplicable.>\n [IBCEM NON-MRA REPORT].\n \n \n 8. Modify the mnemonic for the Third Party Billing Menu [IB THIRD \n PARTY BILLING MENU].\n \n 9. Modify the Insurance Payment Trend Report option [IB OUTPUT TREND \n REPORT] to display the Insurance Plan Group Number.\n \n 10. Modify the Correct a Rejected/Denied Bill option [IB CORRECT \n REJECTED/DENIED] to allow the correction of claims to\n non-accruing funds such as TRICARE claims.\n \nThe intent of this patch is to:\nPatch Components\n================\n<Additional patch components can be added alphabetically if needed.>\n \n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nBILL FORM LOCAL BILLING Modified\n 1. Add new fields to the Enter/Edit Billing Information option [IB\nTYPE(#353) SCREEN(#2.09)\n \nEXPLANATION OF EOB TYPE(#.04) New\nBENEFITS(#361.1) \n \nEXPLANATION OF ENTRY New\nBENEFITS(#361.1) DATE/TIME(#.05) \n \nBILL/CLAIMS(#399) BILL New\n CLASSIFICATION(#.05)\n EDIT BILLING INFO] to allow users to enter additional data\n \nBILL/CLAIMS(#399) BILL CHARGE New\n TYPE(#.27) \n \nBILL/CLAIMS(#399) PATIENT WEIGHT New\n (LB)(#287) \n \nBILL/CLAIMS(#399) TRANSPORT REASON New\n CODE(#288) \n \n elements to claims for health care services provided to patients.\nBILL/CLAIMS(#399) AMBULANCE TRANSPORT New\n DISTANCE(#289)\n \nBILL/CLAIMS(#399) ROUND TRIP PURPOSE New\n DESCRIPTION(#290) \n \nBILL/CLAIMS(#399) STRETCHER PURPOSE New\n DESCRIPTION(#291) \n \nAMBULANCE CONDITION New\n \nINDICATOR(#399.0292)\n \nPROCEDURES(#399.0304) PROCEDURES(#.01) Modified\n \nPROCEDURES(#399.0304) DIVISION(#5) Modified\n \nREVENUE CHARGES(#.02) Modified\nCODE(#399.042) \n \nREVENUE MANUALLY New\n 2. Modify the logic which calculates what the monetary amounts that \nCODE(#399.042) EDITED(#.16) \n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\n \n \nOptions Associated:\n\n
\nReasonable Charges v3.9\n\n
\nHIPAA 5010 maintenance support patch.\n\n
\nFY2012 ADDITIONAL DSS STOP CODE UPDATE\n\n
\nThe purpose of this patch is to update the MCCR Utility file and the\nRevenue Code file for FY2012.\n\n
\nINSTITUTIONAL LTC CD PATIENT EXEMPTION\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2013 changes.\n\n
\nAdd Evaluation and Management codes to the Type of Visit file <#357.69>.\n\n
\nCorrects <UNDEFINED>ALL+24^IBCNS1 error, also changes help text for REFILL\nDATE (.1) field of file (356).\n\n
\nReasonable Charges v3.11\n\n
\nThis patch contains the TCP/IP address update of the HL7 Logical Link \n'IIV EC' connected to a new technical server located at the Financial\nService Center (FSC) in Austin, Texas.\n\n
\nAdd CAMP LEJEUNE TREATMENT as a new entry in the CLAIMS TRACKING \nNON-BILLABLE REASONS file (#356.8).\n\n
\nIB*2.0*476 t1 build contains the first iteratin of the IB portion\nof the deliverables for the 5010 VistA Fee Basis phase II project.\n\n
\nThis patch addresses two issues. The first issue is regarding the Claims\nMatching report [RCDP CLAIMS MATCH] not display the corresponding first\nparty debts. The second issue is about the incorrect charge type NURSING\nHOME CARE (NSC) showing on the patient's bill.\n\n
\nReasonable Charges v3.12\n\n
\nFY2013 MIDYEAR STOP CODE UPDATES\n\n
\nTHIS PATCH MAKES MODIFICATIONS TO THE FUNCTION THAT DETERMINES THE\nSTART OF CARE DATE. THIS WILL ALLOW THE CORRECT START OF CARE DATE\nTO BE DISPLAYED WHEN AN OUTPATIENT EVENT TAKES PLACE ON A DATE THAT\nOCCURS BETWEEN THE ADMIT AND DISCHARGE DATES OF AN INPATIENT EVENT.\n\n
\nThis patch contains two issues. The first issue is about some non billable\nHCPCS codes for prosthetic items which need to be filtered out of the\nClaims Tracking module. The second issue concerns the '^' key which is\nentered and does not exit out of the [IBCR ADJUSTMENT ENTER/EDIT] option\nas expected.\n\n
\nThis is the KIDS build for Integrated Billing patch IB*2*116. The\npurpose of this patch is to develop a list of all third party\ninsurance carriers based on claims that were developed from\n10/1/97 through 12/31/98 (the last five fiscal quarters). This\nlist will be compiled to develop a national list of third party\npayers which is required for the National EDI initiative.\n \nPlease see the National Patch Module description for this patch for\nmore detailed information.\n\n
\nThis patch addresses two issues. The first issue is about the Technical\nComponent (TC) Modifier added to the procedure on the institutional bill.\n \nThe second issue is about the 'Modifier 26 Deleted from Procedures (1)'\nmessage is mistakenly displayed for Modifier 58 in the [IB EDIT BILLING\nINFO] option.\n\n
\nThis patch is about the administrative charge update based on a new\ndispensing fee $13.18 for third party pharmacy prescription claims with\nan effective date of January 1st, 2013.\n\n
\nReasonable Charges Billing Enhancements 2013.\n\n
\nThis patch addresses two issues. The first issue contains a new source of\ninsurance information added to the SOURCE OF INFORMATION file (#355.12).\nThe second issue is about a typo on the help prompt of the CLAIMS (RX) \nSTATE field (#.185) in the INSURANCE file (#36).\n\n
\nThe purpose of this patch is to update the MCCR Utility file and the\nRevenue Code file and the Place of Service file for FY2013.\n\n
\nUpdate for unsupported ICD fields.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2014 changes and corrects the selection logic used to \nvalidate stop codes.\n\n
\nThis patch addresses 3 issues. The first issue concerns a large number of\nrated disabilities repeatedly displaying without providing the SC AT TIME\nOF CARE prompt in order for the user to edit.\n \nThe second issue is about a typo in the '(Enter '6' to list disabilites)'\nmessage following the 'SC Care: YES' field on screen <1> in the Enter/Edit\nBilling Information option. The last issue is about a misspelled word in\nthe 'CHARGE PENDING REIVEW PASSED TO AR' bulletin subject line.\n\n
\nReasonable Charges v3.13\n\n
\nThis patch addresses several problems identified within the On Hold\nfunctionality contained in Integrated Billing v2.0. These problems were\nreported using the Nois system. \n\n
\nAdd Evaluation and Management codes to the Type of Visit file <#357.69>.\n\n
\n ***NOTICE***\n Registration system (DG), Fee Basis System (FB), and Integrated Billing\n Files & Fields Associated:\n \n \n File Name (#) Field Name (#) New/Modified/Deleted\n ------------- -------------- -----------------\n SPONSOR RELATIONSHIP (#355.81) FAMILY PREFIX (#.03) Modified help text\n ***File not included in the FILE LIST. Help text modified by post-install\n routine ^IB499PO.\n \n Forms Associated:\n (IB).\n \n Form Name File # New/Modified/Deleted\n --------- ------ --------------------\n N/A\n \n Mail Groups Associated:\n \n Mail Group Name New/Modified/Deleted\n --------------- --------------------\n N/A\n \n \n Options Associated:\n \n Option Name Type New/Modified/Deleted\n ----------- ---- --------------------\n N/A\n \n Protocols Associated:\n \n Protocol Name New/Modified/Deleted\n Below is a list of all the applications involved in this project along with\n ------------- --------------------\n N/A\n \n Security Keys Associated:\n \n Security Key Name\n -----------------\n N/A\n \n Templates Associated:\n their patch number:\n \n Template Name Type File Name (#) New/Modified/Deleted\n ------------- ---- ------------- --------------------\n \n \n Additional Information:\n \n \n New Service Requests (NSRs):\n -----------------------------\n \n NSR 20100901\n \n Patient Safety Issues (PSIs):\n ------------------------------\n N/A\n \n Remedy Ticket(s) & Overviews:\n -----------------------------\n N/A\n \n APPLICATION/VERSION PATCH\n \n Test Sites:\n -----------\n \n LEXINGTON\n PUGET SOUND\n \n \n Documentation Retrieval Instructions:\n -------------------------------------\n ---------------------------------------------------------------\n Updated documentation describing the new functionality introduced by this\n patch is available.\n \n The preferred method is to FTP the files from ftp://download.vista.domain.ext/\n This transmits the files from the first available FTP server. Sites may also\n elect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n PATIENT REGISTRATION (DG) V 5.3 DG*5.3*867\n \n The documentation will be in the form of Adobe Acrobat files.\n \n Documentation can also be found on the VA Software Documentation Library\n at: http://www4.domain.ext/vdl/\n \n File Description File Name FTP Mode\n --------------------------------------------------------------------------\n Fee Basis User Manual fb3_5um.pdf Binary\n PIMS v5.3 ADT User Manual Registration dg_5_3_reg_um.pdf Binary\n FEE BASIS (FB) V 3.5 FB*3.5*146\n \n The procedure guide, Care for Newborn of Women Veterans, located at\n http://nonvacare.hac.domain.ext/policy-programs/procedure-guides.asp,\n should be distributed to those personnel registering newborns and/or\n processing newborn claims.\n \n \n \n Patch Installation:\n \n Users should be made aware that processing of Newborn claims must ONLY be\n INTEGRATED BILLING (IB) 2.0 IB*2.0*499\n \n Pre/Post Installation Overview\n ------------------------------\n There are three post installation routines associated with this patch\n DG867PO, FB146PO, and IB499PO. These routines primarily serve as filters for\n the data transmitted to the appropriate files listed above, so that only the\n intended data is delivered. The only exception is the IB499PO routine which\n programmatically makes an addition to the help text of the FAMILY PREFIX\n field(#.03) in the SPONSOR RELATIONSHIP file (#355.81). These post\n installation routines may be deleted after successful installation of the\n \n NEWBORN DG FB IB BUNDLE 1.0.\n \n Installation Instructions\n -------------------------\n This patch may be installed with users on the system although it is\n recommended that it be installed during non-peak hours to minimize potential\n disruption to users. This patch should take less than 5 minutes to install.\n \n FB*3.5*147 is a required patch and must be installed before DG*5.3*867.\n \n The patches (DG*5.3*867, FB*3.5*146, and IB*2.0*499) are being released in\n DG*5.3*867 is one of three patches for this release (including FB*3.5*146 and\n IB*2.0*499). The patches will be installed as a bundle in the following order:\n \n \n 1) DG*5.3*867\n 2) FB*3.5*146\n 3) IB*2.0*499\n \n \n Pre-Installation Instructions\n the Kernel Installation and Distribution System (KIDS) multi-build\n -----------------------------\n 1. OBTAIN PATCHES\n --------------\n Obtain the host file NEWBORN_1_2_DG_FB_IB.KID which contains the following\n patches:\n \n DG*5.3*867\n FB*3.5*146\n IB*2.0*499\n \n distribution NEWBORN DG FB IB BUNDLE 1.0.\n Sites can retrieve VistA software from the following FTP addresses. The\n preferred method is to FTP the files from:\n \n download.vista.domain.ext\n \n This will transmit the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n \n Salt Lake City ftp.fo-slc.domain.ext\n \n The NEWBORN_1_2_DG_FB_IB.KID host file is located in the anonymous.software\n directory. Use ASCII Mode when downloading the file.\n \n 2. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu option\n [XPD MAIN]:\n \n The purpose of the Caregivers: Newborn Claims Processing Enhancement Project\n Edits and Distribution ...\n Utilities ...\n Installation ...\n \n Select Kernel Installation & Distribution System Option: Installation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n is to enhance VistA Fee Basis application in support of compliance with\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\n \n Select Installation Option:\n \n 3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD\n -------------------------------------\n From the Installation menu, select the Load a Distribution option.\n Public Law 111-163, the Caregiver and Veterans Omnibus Health Services Act\n \n When prompted for "Enter a Host File:" Enter the full directory path\n where you saved the host file NEWBORN_1_2_DG_FB_IB.KID\n (e.g., SYS$SYSDEVICE:[ANONYMOUS]NEWBORN_1_2_DG_FB_IB.KID)\n \n When prompted for "OK to continue with Load? NO//", Enter "YES."\n \n The following will display:\n \n Loading Distribution...\n of 2010. This law makes changes to sections of Title 38, United States Code\n \n NEWBORN DG FB IB BUNDLE 1.0\n DG*5.3*867\n FB*3.5*146\n IB*2.0*499\n Use INSTALL NAME: NEWBORN DG FB IB BUNDLE 1.0 to install this\n distribution.\n \n 4. RUN OPTIONAL INSTALLATION OPTIONS FOR MULTI-BUILD\n -------------------------------------------------\n entered in VistA. No entry in FBCS should be performed.\n to furnish health care services to a newborn child of a Woman Veteran who\n From the Installation menu, you may select to use the following options\n (when prompted for the INSTALL NAME, enter NEWBORN DG FB IB BUNDLE 1.0\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as data dictionaries or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, data dictionaries, templates, etc.).\n is receiving maternity care furnished by the Department of Veterans Affairs\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n 5. INSTALL MULTI-BUILD\n -------------------\n This is the step to start the installation of this KIDS patch. This will\n need to be run for the NEWBORN DG FB IB BUNDLE 1.0\n \n a. Choose the Install Package(s) option to start the patch\n (VA) for not more than seven days after the birth of the child.\n install.\n b. When prompted for the "Select INSTALL NAME:" enter\n NEWBORN DG FB IB BUNDLE 1.0\n c. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n NO//", answer NO\n d. When prompted "Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? NO//", answer NO\n e. When prompted "Device: HOME//", enter HOME\n to display the Install message on the screen (or enter the device\n you want to print the Install message). You may queue the\n \n install if you wish.\n \n \n Post-Installation Instructions\n ------------------------------\n \n *** IMPORTANT NOTE ***\n Please note there are three post installation routines that may be deleted\n after successful installation of the NEWBORN DG FB IB BUNDLE 1.0. These are:\n \n The scope of these enhancements is to capture information on healthcare\n DG867PO\n FB146PO\n IB499PO\n services provided to newborn children of Women Veterans. Affected functions\n include eligibility determination, enrollment and registration, documentation\n of referrals and authorization for care, claims processing, and payment. Only\n modification to the Fee Basis (FB) and the Registration (DG) packages are\n necessary to meet the requirements of this enhancement. The Integrated\n ***********\n Billing (IB) Patch is included to provide required data for the Fee Basis\n install to reference.\n \n \n The primary purpose of this enhancement is to allow the Electronic Filing of\n Newborn claims.\n \n Functional Description\n ------------------------------\n The following features and functions have been added to the Fee Basis\n This patch, along with DG*5.3*867 and FB*3.5*146, is being released as a\n workflow process applying to both Civil Hospital and Medical Fee:\n \n 1. A new Patient Type of NEWBORN OF VETERAN has been added to the TYPE OF\n PATIENT file (#391). This new selection will be available on Registration\n Screen <7>.\n \n 2. A sponsor is required for all Newborns determined by having the DOB less\n than one (1) year from the present date. An inconsistency check has been\n added to check the presence of a sponsor. If an inconsistency is found the\n inconsistency check will prompt the user to return to Screen <15> in\n bundle, and all three will be automatically installed in the correct order.\n registration to enter a Sponsor.\n \n 3. All Sponsors for Newborns must be listed as eligible for care. An\n inconsistency check will check the status of the Sponsors Eligibility. The\n check will trigger if the Sponsor has no Eligibility status.\n \n All other statuses (i.e. Pending Verification, Verified, and Pending\n Re-verification) are acceptable.\n \n 4. Fee Authorization dates associated with Newborns have checks in place to\n \n not allow Authorization dates that fall outside the accepted range of Newborn\n Authorization. The range is DOB to DOB+7. The system will warn the user and\n not accept an Authorization date that falls outside the appropriate range\n for a Newborn.\n \n 5. When a Veteran Mother of a Sponsored Newborn is reviewed in the\n Registration screens, Screen <15> will display the Newborn(s), with the\n additional header of "Sponsored Newborn".\n \n 6. The FAMILY PREFIX "NB Newborn of Vet" has been added to the Help text in\n This patch has enhancements that extend the capabilities of the Veterans\n the FAMILY PREFIX field (#.03) in the SPONSOR RELATIONSHIP file (#355.81)\n \n 7. "NON-VA FOR FEMALE VET+NEWBORN 17.38" was added to the VA ADMITTING\n REGULATION file (#43.4). This new Admitting Regulation is available when\n editing the 7078.\n \n 8. The following default values were added when entering a Newborn with a\n date of birth of less than one (1) year from present date. Defaults will only\n be assigned when specified screens are accessed during the registration\n process:\n Health Information Systems and Technology Architecture (VistA) Patient\n PATIENT DATA, SCREEN <2> Marital field is defaulted to NEVER MARRIED.\n APPLICANT/SPOUSE EMPLOYMENT DATA, SCREEN <4> Status field is defaulted to NOT\n EMPLOYED. FAMILY DEMOGRAPHIC DATA, SCREEN <8> Married Last Year field is\n defaulted to NO.\n \n \n Patch Components\n ================\n \n \n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2014 changes (Mid Year).\n\n
\nEPHARMACY OPERATING RULES\n\n
\nThis patch addresses two issues. The first issue is about the extract name\ndisplaying incorrectly for IV section in the MCCR Site Parameter Display/\nEdit option. The second issue concerns the CPT codes on an inpatient bill \nduplicated thousands of times in the Enter/Edit Billing Information\noption.\n\n
\nThis patch addresses two issues. The first issue is about the update of \nthe administrative charge based on a new dispensing fee $13.18 for rate \ntypes: Humanitarian and Ineligible on third party pharmacy prescription \nclaims. The second issue is to inactivate the non-billable reason code:\nCV25 HDHP PLAN NOT BILLED for the Claims Tracking module.\n\n
\nThis patch addresses two issues. This first issue is about the \nupdate of the administrative charge for the rate types based on \na new dispensing fee and adjustments for third party pharmacy \nprescription claims with an effective date of January 1st, 2014.\nThe second issue concerns that there is no space between the line item\nnumber and the bill from date to display if a patient has more than 99\ncharges in the Cancel/Edit/Add Patient Charges [IB CANCEL/EDIT/ADD\nCHARGES] option.\n\n
\nThis patch will update the following HL LOGICAL LINK (#870) entries with \nnew IP addresses:\n \nBPS NCPDP\nEPHARM OUT\n\n
\nReasonable Charges v3.14\n\n
\nThis build is to be installed in conjunction with PRCA*4.5*136 to set the\nREVENUE SOURCE CODE correctly for TRICARE bills.\n\n
\nRevised Reasonable Charges v3.14\n\n
\nThis patch contains two issues. The first issue is about three \nnon-billable HCPCS (Healthcare Common Procedure Coding System) codes for\nprosthetic items that need to be filtered out of the Claims Tracking \nmodule. The second issue is about CHAMPVA & CHAMPVA REIMBURSEMENT \nINSURANCE rate schedules linking to RC charge sets are not automatically\nupdated in the Rate Schedule file (#363).\n\n
\nThe purpose of this patch is to update the MCCR Utility file and the\nRevenue Code file and the Place of Service file for 2014.\n\n
\nThis patch addresses two issues. This first issue is about duplicate \nencounters for the outpatient care added to the Claims Tracking when the\n'REPORTS ADD TO CLAIMS TRACKING' site parameter set to 'YES'. The second \nissue is the line items which are not listed under the appropriate \nheading in the [IBJ THIRD PARTY JOINT INQUIRY] option.\n\n
\neInsurance System Modification effort\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2015 changes.\n\n
\nThe HIPAA 5010 D.0 Level II Phase 2 project includes the following\n PRINT'. Selections 0 'NO FORCED PRINT' and 1 'FORCE LOCAL PRINT' still\n remain and function as they always have: if this field\n [Force to Print?] is set to 0, the claim will be transmitted\n electronically to the payer; otherwise, if this field is set to 1, the\n claim will be printed locally.\n \n2. Prevent Creation of Claims with PAYER ID of HPRNT/SPRNT\n -------------------------------------------------------\n Modified VistA IB so that claims with Payer ID HPRNT/SPRNT display\n a fatal error message and force the removal of the HPRNT/SPRNT\nmodifications to the Electronic Billing V. 2.0 application:\n Payer ID from the Insurance Company file (#36).\n \n3. Prevent Creation of Claims with Zero Procedures\n -----------------------------------------------\n Modified VistA IB to prevent the creation of claims with no procedures.\n IB validation logic has been incorporated to ensure a claim that is\n being created or edited cannot be submitted unless it contains at least\n one procedure. If there are no procedures on the created or edited\n claim, a fatal error message will display to the user notifying them of\n this condition and will not allow the claim to be submitted. Claims\n \n will continue to allow $0 line item(s) but these will also be required\n to have at least one procedure. The only exception to this is that\n UB-04 Inpatient claims with no procedures may still be created.\n \n4. Modify the Provider Contact Field Names for Property & Casualty Claims\n ----------------------------------------------------------------------\n Modified the Contact Name, Phone and Extension field names in the\n IB NON/OTHER VA BILLING PROVIDER(#355.93) file so that users will see\n the following prompts/labels while in the PROVIDER ID MAINTENANCE\n [IBCE PROVIDER MAINT] option: P&C Contact Name, P&C Contact Phone\n1. Remove Ability to Print Claim at Clearinghouse\n Number and P&C Contact Phone Extension. The P&C Contact Phone Number\n field was also updated to require a minimum of 10 digits.\n \n5. Modify the Non-VA Facility Street Address & Zip Code Fields\n -----------------------------------------------------------\n Modified VistA so that the STREET ADDRESS field (#355.93,#.05) will no\n longer accept PO Box and other variations of post office box as a\n valid street address. This validation does not apply to the STREET\n ADDRESS LINE 2 field (#355.93,#.1). The ZIP CODE field (#355.93,#.08)\n has been modified so that only 9 digit ZIP codes are valid. Entering\n ----------------------------------------------\n "0000" as the last four digits of a ZIP code is not acceptable.\n \n6. Modify Third Party Joint Inquiry [IBJ THIRD PARTY JOINT INQUIRY]\n ----------------------------------------------------------------\n \n Modified VistA to improve the readability of ERA data in the Third \n Party Joint Inquiry [IBJ THIRD PARTY JOINT INQUIRY] option that \n display when the BC "Billing Charges" action is selected. The\n display was modified to remove the RAW DATA display for those EOBs\n that contained "Message Storage Errors" and make the reported\n Modified VistA IB to remove the user's ability to force the claim to\n error(s) more readable. The formerly known "MESSAGE STORAGE ERRORS"\n are now known as "DATA MISMATCH ERRORS".\n \n7. Include ERAs with errors on the Medicare Remittance Advice Worklist \n -------------------------------------------------------------------\n Modified VistA so that claims containing an error condition from\n processing the 835 will now display on the Medicare Remittance\n Advice Worklist (MRW), which is accessed via the option MRA\n Management WorkList [IBCE MRA MANAGEMENT]. These specific claims\n will be identified on the MRW with an "!" exclamation point\n print at the clearinghouse. The capability to force a claim to print\n displayed immediately in front of the claim number.\n \nThe routine IBCEP8 was added to this patch to reintroduce the changes\nthat were previouly introduced by patch IB*2.0*447 which were subsequently\ninadvertently omitted by the patch IB*2.0*476.\n at the clearinghouse was REMOVED. Screen 10, Section 6 was modified\n by removing the ability to view and select 2 'FORCE CLEARINGHOUSE\n\n
\nIntegrated Billing (IB) update for ICD-10 Diagnosis and Procedures.\n\n
\nThis is the KIDS distribution for patch IB*2*109, Expanded Type of Bill.\n\n
\nThis patch addresses two issues. The first issue is about the tricare\nexpress bills being rejected due to the approving official is undefined.\nThe second issue is the update to the Occurrence Span Code 72 in the MCCR\nUtility file (#399.1).\n\n
\nThis patch addresses two issues. The first issue contains updates to the \nIB Action Type file (#350.1) and the IB Action Charge file (#350.2).\nThe second issue involves the IBJD Billing Lag Time report showing the\nlast patient with blank information on the first page and the name then\nrepeated on the top of the next page with the associated claim activity\ndata.\n\n
\nThe Health Plan Identifier (HPID) project implements a new national \nstore these new HPIDs and OEIDs, and to associate the entries in the local\nInsurance Company file (#36) with a new National Insurance File (NIF),\nowned by the Financial Services Center (FSC), which will centrally manage\ndistribution of HPID/OEID data.\n \nIn order to accomplish this, this patch introduces a new HL7 interface\nfor exchanging insurance information with the NIF. Included with this new\ninterface is a logging function which generates (periodically purged)\ntransaction records, allowing troubleshooting.\n \nstandard of having a single identifier to use on electronic transmissions\nWhen installed, this patch will create a flat-file extract that can be\nsent to the FSC in order to assist in setup of the NIF.\npertaining to health care. All entities that are financially responsible\nfor care are assigned a HPID or Other Entity Identifier (OEID), used for\nentities that aren't traditional health plans. This new standard increases\ninteroperability by replacing clearinghouse-specific identifiers for \nhealth plans.\n \nThis patch updates the Integrated Billing (IB) package to enable it to\n\n
\n2015 RX COPAY THRESHOLDS\n\n
\nThis patch fixes issues where incorrect data is being transmitted in \nthe PID segment for billing records and appointment generated \ninquiries are getting stuck. \n\n
\nThis patch addresses two issues. \n \nThe first issue is about a new entry - LABORATRY SERVICES PROVIDED TO\nNON-PATIENTS added to the MCCR Utility file (#399.1) for UB-04 Bill \nClassification on the second digit type of bill.\n \nThe second issue concerns several misspellings in the display messages \nfor the chiropractic-related dates and the statement covers dates in the \n[IB EDIT BILLING INFO] Enter/Edit Billing Information option.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2015 mid-year changes.\n\n
\nReasonable Charges v3.15\n\n
\nThis patch will update the pharmacy administrative charge based on a new \ndispensing fee of $11.16 for Tricare and Tricare Reimbursement Insurance \nprescription claims with an effective date of February 20, 2015.\n\n
\nDIAGNOSTIC MEASURES PHASE II ROUTINES/FILES\n\n
\nThis patch addresses two issues.\n Interagency with an effective date of January 1st, 2015.\n \n1. The administrative charge $13.07 needs to be added to the prescription\n cost for the rate type: Interagency with an effective date of January\n 1st, 2014.\n \n2. The administrative charge $13.10 needs to be added to the prescription\n cost for the rate types: Reimbursable Insurance, No Fault Insurance,\n Workers' Compensation, Tort Feasor, Humanitarian, Ineligible and\n\n
\nThis patch will install the Cost-Based and Inter-agency billing rates\ninto the Charge Item file (#363.2), with an effective date of 11/04/2014.\n\n
\nReasonable Charges v3.16\n\n
\neBilling Build 3\n\n
\nThis patch addresses 2 issues.\n1. The first issue is to update the MCCR Utility file and the Revenue Code\nfile and the Place of Service file for 2015. \n \n2. The second issue concerns ICD10 procedure codes being truncated on\npage 2 of the printed bill when they contain 7 characters in length.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2016 changes.\n\n
\nIntegrated Billing update for PTF Diagnosis and Procedure code expansion.\n\n
\nThis patch will fix an issue identified while running the Queue Means\nTest Compilation of Charges [IB MT NIGHT COMP] background job that\nleads to a runaway alert process where hundreds of thousands of \nalerts are generated for a single record/instance.\n\n
\nThe purpose of this patch is to update the names of the Occurrence Span\nCodes to the MCCR UTILITY (#399.1) file.\n\n
\n \n file: 364.5 IB DATA ELEMENT entries: N-MAILING ADDRESS FULL\n N-CURR INS. CO FULL ADDRESS\n \nAlso this patch fixes and undefined error found in $ZE=CANCH+6^IBECEAU4:1.\n \nHCFA 1500 and UB-92 bills for Sharing agreement patients when printed \nhave and extra dash in the zip code.\n \nFields in the following files have also been edited to strip out \nthe dash in the zip codes if present.\n \n file: 399 BILLING/CLAIMS field: 109 MAILING ADDRESS ZIP CODE\n \n\n
\nThis patch addresses an issue concerning payment amounts on e-Pharmacy\nclaims where the bill amount is different than what is shown via the ECME\nBilling Events Report [IB ECME BILLING EVENTS] option.\n\n
\nThis patch, IB*2.0*557, is one of three VistA 2016 threshold patches. It \naddresses the annual updates for the Pharmacy Copay Thresholds. Patch \nDG*5.3*922 will update the thresholds for the Means Tests and the Maximum\nAnnual Pension Rate. Patch EAS*1.0*134 will address the annual updates for\nthe GMT Thresholds.\n\n
\nIn preparation for the VA's transition from IPv4 to IPv6 the IB package \nwill require modifications to make it IPv6 ready.\n\n
\nReasonable Charges v3.17\n\n
\nHAPE EDI Revenue project - NCPDP Continuous Maintenance Standards\n\n
\nThis patch addresses two issues. The first issue contains the TRICARE\npharmacy administrative fee update based on a new dispensing fee of $12.19\nwith an effective date of January 1st, 2016. The second issue is about\nthe update of the Place of Service file (#353.1).\n\n
\nReasonable Charges v3.18\n\n
\nThis patch fixes issues during MESSAGE CHECKSUM calculations leading\nto <MAXNUMBER> errors and the potential for the back billing process\nto bill a negative amount.\n\n
\nThis patch addresses two issues. The first issue contains two new \nIneligible Dental for Cost-Based and Inter-agency billing rates for FY\n2015. The second issue is about the [IB OUTPUT DAYS ON HOLD] Days On Hold\nReport in the running process which is never complete.\n\n
\nMCCF ENHANCEMENTS PROJECT - EIV\n \nThis patch implements changes to VistA's Integrated Billing (IB), \nInsurance Company, and Patient Insurance File modules are requested by \nthe Veterans Health Administration (VHA) Chief Business Office (CBO)\neBusiness Solutions Department to comply with the legislative\nchanges mandated by the Health Insurance Portability and Accountability \nAct of 1996 (HIPAA).\n\n
\nThis patch corrects the following problem:\n \n \n The Pharmacy user gets the following error:\n \n The bill number in the parent IB ACTION entry is missing.\n Error in processing...No action taken.\n \n The coding changes in routines IBARX and IBARX1 has resolved the\n problem. When the user returns the medication to stock, and the copay\n charge status is "HOLD", the charge will be cancelled.\n \n \n ** Special Note **\n The option that is affected belongs to Pharmacy.\n The changed routines belong to Integrated Billing.\n NOIS: DUB-0698-32098 / DUB-0698-31443\n OPTION: Return Medication to Stock [PSO RETURNED STOCK]\n \n Prior to installation of IB*2*70, when a Rx was returned to stock a\n bulletin was generated stating charges were removed. The problem is\n charges are not removed. The bills are not showing because they are\n still on hold if the patient has insurance with Rx coverage.\n\n
\nThis patch implements changes to VistA's Integrated Billing (IB) module \nas requested by the Veterans Health Administration (VHA) Chief Business \nOffice (CBO) eBusiness Solutions Department to comply with the \nlegislative changes mandated by the Health Insurance Portability and \nAccountability Act of 1996 (HIPAA).\n\n
\nThe patch contains the fix for the patch IB*2.0*528. It is replacing \nreferences to the old security key IBCNE IIV AUTO MATCH with IBCNE EIV\nMAINTENANCE in two routines IBCNEAMC and IBCNEUT6.\n\n
\nMCCF ENHANCEMENTS PROJECT - CARC/RARC\nremittances can be used by VA, reducing the level of open accounts \nreceivable and allowing claim denials to be more quickly addressed; and \nstandardizes EFT & ERA enrollment, reducing workload burden on VA staff. \n \nThis patch contains changes to the ePayments (835 and EFT) program area \nto ensure compliance. Specifically, enhancements to the VistA Third Party \nEDI Lockbox module to increase timely and accurate processing of payments \nfor electronic pharmacy claims in compliance with HIPAA and VHA Fiscal \nAccounting policies will also be required. The ePayments system is used \nby AR staff to process payments from third party payers for both medical \n \nand pharmacy claims. The objectives of the requested ePayments software \nmodifications are to expedite accurate payments by enhancing the \nePayments software to streamline the user's ability to process the \npharmacy 835 while:\n \nComplying with HIPAA legislative requirements to meet patient needs and \nsecure Protected Health Information (PHI).\n \nConducting payment accounting in accordance with the Office of Management \nand Budget (OMB) directives.\nVA's compliance with Electronic Funds Transfer (EFT) & Electronic \n \nSystematically enforcing VHA Fiscal Accounting policy.\n \nProviding software tools in support of efficient business models to\nmaximize the volume of electronic data received from third party \npayers to increase revenue and save productive dollars.\nRemittance Advice (ERA) Operating Rules and enables VA to more \neffectively use ERA data, resulting in better revenue and cash flow \nmanagement; provides the infrastructure foundation for electronic \nexchange of claim payment information and promotes an interoperable \nsystem; reduces the time elapsed between receipt of the 835 and receipt \nof the CCD+ transaction; ensures that trace numbers between payments and \n\n
\nMEDICAL CARE COLLECTION FUND (MCCF) ENHANCEMENTS PROJECT - ePAYMENTS\n\n
\nThis patch is part of the Pharmacy Safety Updates project which was \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444\n INTEGRATED BILLING (IB) V. 2.0 IB*2*545\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429\n INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313\n \n \nThe following New service Requests (NSR) are related to this patch:\nestablished to address specific New Service Requests (NSRs) as well as a\n \n NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply\n ---------------------------------------------------------------------------\n The Outpatient Pharmacy and supporting VistA applications are being modified\n to allow dispensing of more than 90 day supply fill for outpatient \n prescriptions. The new limit will be 365 days and will be set for each drug\n individually. See below for more information on specific menu \n options related to this enhancement. \n \n NSR 20110308 Addition of a STRENGTH Property to IV ADDITIVES and Premixed \nRemedy Ticket and a Patient Safety Issue (PSI) related to the VistA Pharmacy\n IV SOLUTIONS\n ----------------------------------------------------------------------------\n Although patches PSJ*5*289 and PSS*1*174 introduced quite a few enhancements\n to the IV Additives and IV Solutions ordering functionality they did not go\n far enough in addressing all the issues originally in the NSR. Patches \n PSJ*5*313 and PSS*1*189 will extend the display of the IV Additive strength\n to other parts of the Inpatient Medications and Pharmacy Data Management \n applications. In addition, it will also impose a new rule where an Orderable\n Item can only have one IV Solution for a specific volume when it is marked\n to be used in the CPRS IV Fluid Order Entry. \napplications as approved by the Health Systems Enterprise Systems Manager\n \nThe following Integrated Billing copay functionality was modified:\n \n1. Cancel/Edit/Add Patient Charges [IB CANCEL/EDIT/ADD CHARGES] option\n This menu option was modified to allow up to 12 copay units to be added\n for a patient. Before the maximum limit was 3, given that 90 days supply\n corresponded to 3 copay units (1 unit for each 30 days supply)\n \n2. The upper limit for the value allowed for the DAYS SUPPLY field (#.06) in\n the IB BILL/CLAIMS PRESCRIPTION REFILL file (#362.4) was changed from 90\n(ESM).\n to 365 in order to accommodate the new limit for this field in the\n Outpatient Pharmacy application.\n \nThis project is comprised of patches from five different applications, as\nshown below:\n \n\n
\nThis patch addresses the request to default the revenue code to 124 \n(PSYCHIATRIC) for five Mental Health Diagnosis Related Groups (DRGs)\nin the Charge Item file (#363.2).\n\n
\nPatch IB*2.0*562 addresses 1 issue:\n \n1.) Numerous sites have reported an issue with intermittent records \nof the Special Inpatient Billing Cases File (#351.2) not having discharge \ndates when this information is present in the Patient Movement File \n(#405). \n\n
\nMCCF ePharmacy Compliance Phase 3\n\n
\nThis patch will update the administrative charge based on a new\ndispensing fee $14.29 for third party pharmacy prescription claims with\nan effective date of January 1st, 2016.\n\n
\nIntegrated Billing, Reasonable Charges.\n\n
\nPreviously released patch IB*2.0*561 applied default revenue code 124 \n(PSYCHIATRIC) to five Mental Health Diagnosis Related Groups (DRGs) 881, \n882, 883, 885 and 886. These charge items included R&B (Room & Board)\n101, Intensive Care Unit 200, and Ancillary Services 240 in the CHARGE\nITEM file (#363.2).\n \nThis patch will still apply default code 124 to R&B but remove it for\nIntensive Care Unit 200, and Ancillary Services 240.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Year 2017 changes.\n\n
\nThis patch contains two updates:\n \n* 68 Cost Based and Inter-Agency billing rates with an effective date of \n 07/07/2016 in the CHARGE ITEM file (#363.2).\n \n* 1 Condition Code in the MCCR UTILITY file (#399.1).\n\n
\nThis patch will update the PAYER file (#365.12) with any missing\nentries.\n\n
\nThis patch will correct the cost based and interagency charge rates for\nPolytrauma and PM&RS (Physical Medicine & Rehabilitation Service)\nbeing reversed with the release of IB*2.0*570.\n\n
\nReasonable Charges v3.19\n\n
\nThis patch addresses two issues. The first issue contains a PARAMETER \nerror related to a group plan's comment in the Move Subscribers to a\nDifferent Plan [IBCN MOVE SUBSCRIB TO PLAN] option. The second issue is\nregarding numerous claim tracking entries incorrectly filled with the\nvisit date/time for inpatient events in the Admit a Patient [DG ADMIT\nPATIENT] option.\n\n
\nUpdate Revenue Codes.\n\n
\nDescription:\nIBCSC10 released in IB*2.0*547 does not handle this scenario correctly.\n---------------------------\nNSD Ticket# I10841525FY16\n \nProblem:\n-------\nWhen testing with FSC, customer reported that they are not able to enter a \nprofessional alternate payer ID on Bill Screen 10 when the charge type is \ninstitutional and the form type is a CMS-1500.\n \nResolution:\nThis warranty patch corrects this defect in routine IBCSC10.\n----------\nModified screen 10 to be consistent with the screening logic on\nfields #140, #142 & #144 in file #399. Screen 10 will now use form-type \ninstead of charge type to determine alternate payer ID.\n \n \nTest Sites:\n----------\nPittsburgh\nSouth Texas\n \nNorthern Indiana\nIlliana\n \nDocumentation Retrieval Instructions\n------------------------------------\nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may also \nelect to retrieve files directly from a specific server.\n \nSites may retrieve the documentation directly using Secure File Transfer\nIn addition, requirements defects were also discovered. There were \nProtocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI\nField Offices:\n \n Albany: fo-albany.domain.ext\n Hines: fo-hines.domain.ext \n Salt Lake City: fo-slc.domain.ext\n \nDocumentation can also be found on the VA Software Documentation Library \nat: \nhttp://www.domain.ext/vdl/\nseveral changes made in patch 547 to remove the printing and transmission \n \nTitle File Name Transfer Mode\n--------------------------------------------------------------------------\nRelease Notes/Installation Guide ib_2_0_p547_rn.pdf Binary\nEDI User Guide edi_user_guide.pdf Binary\nIntegrated Billing (IB) V.2.0\nTechnical/Security Manual ib_2_0_tm.pdf Binary\n \nPatch Installation:\n \nof admission dates on all outpatient claims. During the warranty period \nPre/Post Installation Overview\n------------------------------\nN/A \n \n \nPre-Installation Instructions\n-----------------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users entering and editing IB claims. \nit was discovered that Outpatient Home Health and Outpatient Hospice \nThis patch should take less than 5 minutes to install\n \nNo options need to be disabled.\n \nInstallation Instructions\n-------------------------\nThis patch may be installed with users on the system although it is \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users entering and editing IB claims. This \npatch should take less than 5 minutes to install.\nclaims still require the admission date and time or they will be rejected. \n \n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will not\n \n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch \n is installed. It compares all components of this patch\n (routines, DDs, templates, etc.).\n c. Verify Checksums in Transport Global - this option will allow\n you to ensure the integrity of the routines that are in\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\nA function ($$HHLTH) was added to routine IBCEF1 to determine if a claim is \n choose the patch to install. (ex. IB*2.0*574)\n \n5. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//', enter NO\n \n6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? NO//, respond NO\n \n7. When prompted "DEVICE: HOME//", enter HOME\n \n===========\nHome Health or Hospice. This function was inserted into entries #77, 98 \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0.\n \n \nPost-Installation Instructions\n------------------------------\n \nThere are no special post-installation instructions for this patch.\n \n \nRoutine Information:\nand #1305 of file 364.7 to output the date for all inpatient claims AND \n====================\nall Outpatient home health and hospice claims.\n \nThe purpose of this patch is to meet the requirements for the MCCF \neBilling Compliance Phase 3 project related to Integrated Billing (IB).\nIntegrated Billing is a software module within Veterans Health Information\nSystems and Technology Architecture (VistA) that provides the ability for\nbilling personnel to submit claims in either a paper or electronic format\nto third-party payers. \nMCCF (Medical Care Collection Fund) warranty fix for the FY15 eBilling \n \n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (#) New/Modified/\n Sub-file Name (#) Field Name (Number) Deleted\n------------------- --------------------------------- -------------\nCompliance Phase 3 project.\nIB FORM FIELD CONTENT (#364.7)\n Screen: I $$INCLUDE^IBY547PR(7,Y)\n \n \nForms Associated:\n New/Modified/\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\nN/A\n \n \n \nMail Groups Associated:\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\n \n \nOptions Associated:\n New/Modified/\nOption Name Type Deleted \nThis patch contains a fix for the installed patch IB*2.0*547. When \n----------- ---- -------------\nN/A\n \n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\nN/A\n \ntesting with FSC, customer reported that they are not able to enter a \n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n----------------- -------------\nN/A\n \n \nTemplates Associated:\n New/Modified/\nprofessional alternate payer ID on Bill Screen 10 when the charge type is \nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \nAdditional Information:\nN/A \n \nNew Service Requests (NSRs)\n---------------------------- \ninstitutional and the form type is a CMS-1500. The version of routine \nNSR 20140414 - Medical Care Collection Fund (MCCF) eBilling Compliance \nPhase 3\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview\n\n
\nThis is a patch for build IB*2.0*549 containing two routines. Routine \nIBCNEUT7 is being modified in the DEATH2 subroutine to also set the \nCOVERED BY HEALTH INSURANCE field (file 2, field .3192) to 'N' when \nterminating all active policies for a deceased patient. It also contains \na post-installation routine which will change the COVERED BY HEALTH \nINSURANCE field for all deceased patients who don't have active patient \npolicies and the current value of the COVERED BY HEALTH INSURANCE field \nIS 'Y'.\n\n
\nThis patch will update the administrative charge based on different rate \ntyes of new dispensing fees for third party pharmacy prescription claims\nwith an effective date of January 1st, 2017.\n\n
\nThis patch, IB*2.0*583, is one of three VistA 2017 threshold patches. It \naddresses the annual updates for the Pharmacy Copay Thresholds. Patch \nDG*5.3*930 will update the thresholds for the Means Tests and the Maximum\nAnnual Pension Rate. Patch EAS*1.0*144 will address the annual updates for\nthe GMT Thresholds.\n\n
\nReasonable Charges v3.21\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes in response to the\nComprehensive Addiction and Recovery Act (CARA) of 2016 and the \nVeterans Affairs opioid safety initiative.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal Mid-Year 2017 changes.\n\n
\nThe Chief Business Office (CBO) is requesting system enhancements to the\nHealth Administration (VHA) healthcare facilities, which makes it\ndifficult to determine whether all monies due VA for Non-VA care services\nare being billed and collected from Third Party insurance carriers, where\napplicable. The current process is a resource intensive, manual process\nwith no assurance that all applicable Non-VA charges have been billed and\ncollected.\nVeterans Health Information Systems and Technology Architecture (VistA)\nIntegrated Billing (IB), Accounts Receivable (AR), and Fee Basis software\nmodules that would allow segregating all billing and collection\nactivities for Non-Department of Veterans Affairs (VA), Care Third Party\nInsurance carriers' reimbursement.\nCurrent Medical Care Collections Fund (MCCF) Third Party billing and\ncollections applications in the VistA information system do not segregate\nthe Non-VA care claims from those claims for service rendered at Veterans\n\n
\nThis patch involves updates to the MCCR UTILITY (#399.1) file, the REVENUE\nCODE (#399.2) file, the PLACE OF SERVICE (#353.1) file and the CLAIMS\nTRACKING NON-BILLABLE REASONS (#356.8) file for 2017.\n\n
\nMinor IB DD updates.\n\n
\nThis patch will restore functionality to screen 10 of the Enter/Edit\nBilling Information option that was accidently removed with the release\nof IB*2.0*554.\n\n
\nThis patch will prevent the Onset of Current Illness date from defaulting \nillness not allowed on same bill' to 'Occ. codes Onset of Illness (11) \nand LMP (10) not allowed on same bill.'. This dictionary entry will be \nmodified, if it exists, via the IBY576PO post-install routine and if the \nentry does not exist IBY576PO will create it.\nto the Date of Service. If there is an Occ Code 10 (LMP) on the bill \nthen the Onset Date should default to the code 10 date. iF there is an \nOcc Code 11 (Onset of illness) on the bill then the Onset date defaults \nto the code 11 date. Code 11 takes priority over code 10, but since \nthese are not supposed to be on the same bill the following modified \nerror message will display: 'Occ. codes Onset of Illness (11) and LMP \n(10) not allowed on same bill.' This is the error message for IB Error \n'IB099' which is being changed from 'Occ. codes for accident, LMP, \n\n
\nRoutine IB20P599 copied from IB20P586 for Stop Code Updates effective \n10/1/2017.\n\n
\nECME won't submit a claim with a Service-Connected (SC) issue, even\nafter the user indicates that the issue has been resolved. Same \nissue is reset again and again, with RNB (Reason Not Billed) \nmessage of "Needs SC Determination". This occurs with any of the \npossible SC conditions. This patch corrects this issue, and also \nupdates line 3 with the newer VA Directive reference.\n\n
\nThis patch contains one update:\n \n* 68 Cost Based and Inter-Agency billing rates with an effective date of \n 08/29/2017 in the CHARGE ITEM file (#363.2).\n\n
\nEach year, the government sets new values for the Medicare deductible and\nfor the pension threshold rates. These values need to be updated in the\nassociated billing files for accurate and legal billing. The purpose of\nthis patch is to assist sites in the entry of the Basic Pension Threshold\nrates and the Medicare Deductible value for Calendar Year 2018.\n\n
\nReasonable Charges v3.22\n\n
\nVeterans w/Insurance reports and Claims Tracking.\n\n
\nThis patch addresses two issues.\nEnter/Edit Billing information [IB EDIT BILLING INFO] option.\n \nThe first issue is about missing timeframe of bill data in the associated\ndisplay field when 'O NON-PAY/ZERO CLAIM' is selected in the Enter/Edit\nBilling information [IB EDIT BILLING INFO] option.\n \nThe second issue concerns the Technical Component (TC) modifier which\ndoesn't automatically populate to any procedure on an institutional bill\nif the only professional charge on the procedure is 26 modified in the\n\n
\nThis patch will update the administrative charge based on different rate \n NO FAULT INS. 16.64\n REIMBURSABLE INS. 16.64\n TORT FEASOR 16.64\n WORKERS' COMP. 16.64\n TRICARE REIMB. INS. 13.91\n TRICARE 13.91\ntypes with new dispensing fees for third party pharmacy prescription\nclaims with an effective date of January 1st, 2018.\n \n Rate Type Dispensing Fee\n ------------------- --------------\n HUMANITARIAN 16.64\n INELIGIBLE 16.64\n INTERAGENCY 16.64\n\n
\nThis patch implements Payers domain changes required by the\nCollaborative Terminology Tooling & Data Management (CTT & DM) Native\nDomain Standardization (NDS) project. \n \nPlease see FORUM for full patch description and installation instructions.\n\n
\n This patch addresses 3 issues:\n IBZDATA(1) variable is undefined which is supposed to hold formatting\n data for the bill line.\n \n 1. Update the Integrated Billing option Correct Rejected/Denied Bill [IB\n CORRECT REJECTED/DENIED] to address a missing lock issue.\n \n 2. Correct the summary totals of the THIRD PARTY FOLLOW-UP SUMMARY in the\n View/Print Extracted Reports [IBJD DM VIEW/PRINT EXTRACTS] option.\n \n 3. The FINDLN+64 and FINDLN+118 undefined errors occur when the \n\n
\n This patch will address 4 issues:\n option. This ensures that an original prescription with a fill date \n that differs from the date the bill was created will be included in \n the report.\n \n 3. This patch changes the process of searching for clerks when using the\n Workload Assignment Enter/Edit [IBJD FOLLOW-UP WORKLOAD] option so \n that new entries cannot be made to the NEW PERSON (#200) file. The \n option has been changed to search the NAME (#.01) field of the NEW \n PERSON (#200) file, instead of searching the IB DM WORKLOAD PARAMETERS\n (#351.73) file. The entry found in the NEW PERSON (#200) file is then \n \n used to search the IB DM WORKLOAD PARAMETERS (#351.73) file, and will\n allow a new entry to be made if a match is not found.\n \n 4. For certain Clinical Procedure Terminology (CPT) codes we need \n to enter a procedure description- for CPT J1566 we do not have \n this option in V2. Other Vista sites allow you to enter the \n appropriate information. Can an update be done to V2 to have this\n option for this CPT code- it is causing claims to deny.\n 1. The medication profile screen should show \n the co-payment indicator for non-service connected patients.\n \n 2. This patch adds a check for the FILL NUMBER (#.1) field in the\n IB BILL/CLAIMS PRESCRIPTION REFILL (#362.4) file when searching\n for third party bills with matching first party prescription \n copayments using the Claims Matching Report [RCDP CLAIMS MATCH] \n\n
\nRoutine IB20P615 copied from IB20P599 for Stop Code Updates effective \n04/1/2018.\n\n
\nReasonable Charges v3.23\n\n
\nIB*2.0*601 -- see patch description for implementation details. \n\n
\nThis patch addresses three issues.\nThe third issue as a post-init routine that will update the MCCR Utility \nfile (#399.1) and Specialty file (#42.4) to prevent unwanted Hospice and \nFirst Party charges.\n \nThe first issue is about the Clinical Information header overlapping the\nthe special conditions in the expanded claims tracking entry screen in the\nthe Claims Tracking Edit [IBT EDIT BI TRACKING ENTRY] option.\n \nThe second issue is requested to add the bundled procedures 0295T, 0296T,\n0297T and 0298T to the procedures split structure.\n \n\n
\nThis patch addresses two issues.\n \n- Fix an undefined error occurred at line MRA2+40^IBJTBA1 in the Third\nParty Joint Inquiry [IBJ THIRD PARTY JOINT INQUIRY] option.\n \n- Update to Condition/Occurrence/Value codes of the MCCR UTILITY (#399.1)\nfile for 2018.\n\n
\nUpdate three Y2K issues.\n\n
\nThe patch will re-instate the 2017 BILLING THRESHOLD (#354.3) values.\n\n
\n \nDescription\n10.) A new warning message will print to the screen in the Enter/Edit \nBilling Information option if an ATTENDING, REFERRING or RENDERING \nProvider has a PERSON CLASS - NEW PERSON file (#200) - that was \nexpirated at the time of the Date of Service.\n \n11.) On the Third Party Joint Inquiry screen, one (1) character space \nshall be added to the "Type" field so that it will accommodate five \ncharacters (a one-character classification indicator, a forward slash \n(/), a one-character component indicator, a forward slash (/), and a \none-character care type) ("X/X/X"). If a bill contains prescriptions, \n-----------\nthen an "R" shall be concatenated to the fifth character sub-type \nposition of the "Type" field. If a bill contains prosthetics, then a \n"P" shall be concatenated to fifth character sub-type position of the \n"Type" field.The "Type" field shall contain five (5) characters as \nfollows:\n1. "I" for Inpatient or "O" for Outpatient,\n2. "/" forward slash character\n3. "P" for Professional or "I" for Institutional\n4. "/" forward slash character\n5. "P" for Prosthetics or "R" for Prescriptions\nThe Chief Business Office (CBO) is requesting system enhancements to\n \n12.) Three new Third Party Insurance Rate Types shall be created in \nthe VistA IB Suite for the billers to choose from when billing for \nencounters. They are as follows:\n HUMANITARIAN REIMB. INS. \n DENTAL REIMB. INS.\n INELIGIBLE REIMB. INS.\n \n13.) Each of the new rate types above will have the 'Insurer' as the \nresponsible party.\nThe Veterans Health Information Systems and Technology Architecture\n \n14.) Billers (revenue staff) should be able to identify any remaining \ncharges to the patient after the Third Party payments are received for \nEmergency Humanitarian, Ineligible and Dental services so they can \naccomplish balance billing. \n \n \n \nConcurrent Development / Dependencies:\n--------------------------------------\n(VistA) Integrated Billing (IB), Accounts Receivable (AR), and \nN/A\n \n \nPatch Components:\n-----------------\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nOutpatient Pharmacy (PSO) software modules. \nN/A\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nIBT SUP MANUALLY QUE PRSTHTCS ROUTINE NEW\n \nProtocols Associated:\n \n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Mod/Del\n------------- ---- ------------------ -----------\nIBJT ACTIVE LIST LIST NEW\nIBJT INACTIVE LIST LIST NEW\nThe mission of the Department of Veterans Affairs (VA), Office of \n \nNew Service Requests (NSRs):\n----------------------------\n20150505 - Revenue Reporting Enhancements\n20150506 - Revenue Eligibility Enhancements\n20150507 - Revenue Operations Enhancements\n \n \nPatient Safety Issues (PSIs):\n------------------------------\nInformation & Technology (OI&T), is to provide benefits and services \nN/A\n \n \nRemedy Ticket(s) & Overviews:\n-----------------------------\nN/A \n \nTest Sites:\n----------\nDurham VAMC\nto veterans of the United States Armed Forces. In meeting these \n \n \nSoftware and Documentation Retrieval Instructions:\n----------------------------------------------------\nPatches for this installation are combined in host file \nIB_2_568_PRCA_PSO_BUNDLE_T1.KID\n \nInstallation of this host file should be coordinated among the packages \naffected since only one installation is necessary.\n \nIMPORTANT INSTALLATION NOTE:\ngoals, OIT strives to provide high quality, effective, and efficient \nThe patches are:\n \n IB*2.0*568\n PRCA*4.5*315\n PSO*7.0*463\n \n \nSites may retrieve the KIDS build in one of the following ways:\n \n(1) The preferred method is to FTP the files from \nInformation Technology (IT) services to those responsible for \ndownload.vista.domain.ext which will transmit the files from the first \navailable FTP server.\n \n(2) Sites may also elect to retrieve the patch directly from a specific\nserver as follows:\n \n OIFO FTP ADDRESS DIRECTORY\n -------------- ------------------------ ------------------\n Albany ftp.fo-albany.domain.ext anonymous.software\n Hines ftp.fo-hines.domain.ext anonymous.software\nproviding care to the veterans at the point-of-care, as well as \n Salt Lake City ftp.fo-slc.domain.ext anonymous.software\n \n \nSites may retrieve documentation directly using Secure File Transfer \nProtocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following\nOI Field Offices:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext\nSalt Lake City: fo-slc.domain.ext\nthroughout all the points of the veterans' health care. The VA depends\n \nDocumentation can also be found on the VA Software Documentation \nLibrary at:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n-----------------------------------------------------------------------\nIntegrated Billing User Guide ib_2_0_um.doc Binary\nIntegrated Billing Technical Manual/Security Guide ib_2_0_tm.doc Binary\nIntegrated Billing Deployment, Installation, \non Information Management/Information Technology (IM/IT) systems to \n Back-Out, and Rollback Guide \n FY16RevenueIBVIP_Deployment_Installation_Guide.doc Binary \n \n \n \nPatch Installation:\n \nPre/Post Installation Overview:\n-------------------------------\nThe post installation routine, IBY568PO, is not automatically deleted\nmeet mission goals.\nas part of the installation process. You may delete it after\ninstallation if you desire.\n \nPre-Installation Instructions:\n------------------------------\nN/A\n \nInstallation Instructions:\n--------------------------\nThis process will install new and updated routines and other \n \ncomponents listed above. There is a post-install routine that will add \nentries to a number of files.\n \nThe patch will be released in conjunction with an Accounts Receivable\npatch, PRCA*4.5*315 and an Outpatient Pharmacy patch, PSO*7.0*463.\n \n ************************ NOTE ************************\n IF A USER IS ON THE SYSTEM AND USING THESE PROGRAMS \n AN EDITED ERROR WILL OCCUR. \n The patch should be installed when NO Outpatient \nThe overall FY16 HAPE Revenue Enhancement project has been further \n Pharmacy users are on the system.\n ******************************************************\n \n Installation will take less than 1 minute.\n \n Suggested time to install: non-peak requirement hours.\n \n \n 1. Obtain the file IB_2_568_PRCA_PSO_BUNDLE_T1.KID.\n \ndivided into three sub-projects:\n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. Use Load a Distribution using IB_2_568_PRCA_PSO_BUNDLE_T1.KID when\n prompted to Enter a Host File name. You may need to append a\n directory name.\n \n 4. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter IB*2.0*568):\n a. Verify Checksums in Transport Global - This option will \n \n allow you to ensure the integrity of the routines that \n are in the transport global.\n b. Print Transport Global - This option will allow you to \n view the components of the KIDS build.\n c. Compare Transport Global to Current System - This option \n will allow you to view all changes that will be made when \n this patch is installed. It compares all components of \n this patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a \n backup message of any routines exported with this patch. \n----------------------------\nNSR #20150506\n It will not backup any other changes such as DD's or \n templates.\n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? \n NO//" respond NO.\n \n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//" respond NO. \n \n \nThe Revenue Eligibility Enhancements Project effort for the Chief \n \nPost-Installation Instructions:\n-------------------------------\nThere are no special tasks to perform after this patch installation.\nBusiness Office (CBO), bundles several NSRs with similar business \nneeds into a single requirements document. Successfully addressing \nthe requirements contained within this document will enable the \nDepartment of Veterans Affairs (VA) to appropriately bill certain \nsubsets of billable events by correcting, automating, or enhancing \ncurrent Veterans Health Information Systems and Technology \nArchitecture (VistA) systems.\n \nThis patch is part of a multi-package build. There are three patches \nNSR #20150507\nThe Revenue Operations Enhancements Project combines serveral NSRs, \nas well. This effort enables the Department of Veterans Affairs (VA)\nto improve revenue operation functionality related to repayment plans, \nlate charge capture, bill suspension reasons, the billing of \ndeactivated providers, and the display of appeal rights and \nresponsibilities on the Veterans Beneficiary travel Bill of Collections\nform. Implementation of the proposed enhancements will make a \nsignificant positive impact on stakeholders and target users.\n \nassociated with the FY16 HAPE Revenue Enhancement project - \nNSR #20150505\nThe Revenue Reporting Enhancements Project will enable the VA to \nimprove tracking and reporting of revenue, and will support revenue \nreporting business rules and guidelines.\n \n \nIB*2.0*568 patch enhancements, pertinent to the above NSRs, include:\n \n1.) When generating the RNB (Reasons Not Billable) report, the \nIntegrated Billing system shall populate the charges for all types \nIB*2.0*568,PRCA*4.5*315 and PSO*7.0*463. All three patches are to be \nof services provided. Charges will not be screened by any billable \ncriteria but willindicate the full amount as if the care was to be \nbilled.\n \n2.) The sub-option Claims Tracking Parameter Edit [IBT EDIT TRACKING \nPARAMETERS], that currently has no key, will be locked with a new \nSecurity Key called IB PARAMETER EDIT. \n \n3.) The option MCCR Site Parameter Display/Edit [IBJ MCCR SITE \nPARAMETERS], which is currently locked with the IB SUPERVISOR Security\ninstalled together as a bundle, IB_2_568_PRCA_PSO_BUNDLE_T1.KID\nKey, will be instead locked with the new key.\n \n4.) The Integrated Billing system shall create claims tracking entries\nfor previously unbilled Prosthetics/DME items when new billable \ninsurance is entered into the patient's insurance file. \n \n5.) A new coverage limitation field shall be created in the insurance \nfile for Prosthetics. Like the other existing coverage limitation \nfields in the insurance file (Inpatient, Outpatient, Pharmacy etc.), \nthis field will have the following options:\n \n 0=NOT COVERED\n 1=COVERED\n 2=CONDITIONALCOVERAGE\nOnce selected, they will show in the patient insurance file as Yes, \nNo, or Conditional.\n \n6.) The system shall automatically assign an RNB [NO PROSTHETIC \nCOVERAGE (CV22)] for Prosthetics/DME items if the patient has no \ncoverage for Prosthetics in his/her insurance file.\n \n \n7.) The system shall have a new option to add Prosthetics items to \nManual and Nightly Claims Tracking. \n \n8.) Users will be able to select Suspended Type from the menu to \ndisplay in the First Party Follow- Up [IBJD FOLLOW-UP FIRST PARTY] \nreport. \n \n9.) First Party Follow- Up [IBJD FOLLOW-UP FIRST PARTY] report shall \nbe modified to incorporate reason for suspension.\n \n\n\nThis patch addresses the Technical Component (TC) modifier which \nneeds to be automatically removed from any procedure on institutional\nbills for Medicare in the Enter/Edit Billing Information [IB EDIT BILLING \nINFO] option.\n\n
\nThis patch addresses the following 2 issues:\n \n1. An undefined error occurs when running the Held Charges Report\nLM [IB OUTPUT HELD CHARGES LM] option.\n \n2. When running the Enter/Edit Billing Information [IB EDIT BILLING INFO]\noption, the user will not be prompted for the PROCEDURE DESCRIPTION field\nwhen they enter a partial match CPT code.\n\n
\nMCCF EDI TAS EPHARMACY BUILDS 3 & 4\n\n
\nThis patch addresses one issue.\n \n-Fix an undefined error at line IBCSCH+7 in routine IBCSCH in the \n Enter/Edit Billing Information [IB EDIT BILLING INFO] option. \n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal year 2019 changes, effective 10/01/2018.\n\n
\n The Mental Health Suicide Prevention - Suicide High Risk Patient \n in enhanced care, which includes more frequent contacts and dispensing\n medications in smaller amounts more frequently, as safety precautions. \n The Display PRF effort enhances the current VistA system and Delphi\n graphical user interface to address deficiencies in the functionality of\n the existing PRF package that interfere with effective management of \n coordination of care for high risk individuals. \n Enhancements effort incorporates the Modifying High Risk patient\n Copayments and the Display Patient Record Flag (PRF) effort and ownership\n management and transfer initiatives. The goal of this effort is to\n improve the delivery of targeted Mental Health care for individuals at\n high risk for suicide. Modification of copayments for Veterans assessed\n as being at high risk for suicide involves making changes to the existing\n VistA and payment systems to support regulatory change processes aimed at\n removing financial barriers that may prevent these Veterans from engaging\n\n
\nThis is patch IB*2*64 for the Integrated Billing package. This patch\ncaptures insurance carrier statistics for fiscal year 1996 for the\nMCCR program office.\n \nPlease see the National Patch Module description for this patch for more\ndetailed information.\n\n
\nThis patch changes the co-pay exemption message for patients\nwho decline to give means test info, who are Cat C from\n"There is insufficient income data on file for the prior year"\nto "Patients income is greater than Copay Income Threshold"\n \nThis also changes the automatic co-pay exemption for patients\ngoing from Cat C to Cat A, claiming a hardship.\n \n\n
\n \nMCCF EDI TAS EBILLING BUILD 3 DENTAL\n\n
\nThis patch addresses updates of Cost Based and Inter Agency rates with an\neffective date of 08/28/2018 in the CHARGE ITEM file (#363.2).\n\n
\nThis patch, IB*2.0*635, is one of three VistA 2019 threshold patches. It \naddresses the annual updates for the Pharmacy Copay Thresholds. Patch \nDG*5.3*973 will update the thresholds for the Means Tests and the Maximum\nAnnual Pension Rate. Patch EAS*1.0*170 will address the annual updates for\nthe GMT Thresholds.\n\n
\nReasonable Charges v3.24\n\n
\nThis is IB Build-7\n\n
\nThis patch will update the administrative charge based on different rate\n INELIGIBLE 17.66\n INELIGIBLE REIMB. INS. 17.66\n INTERAGENCY 17.66\n NO FAULT INS. 17.66\n REIMBURSABLE INS. 17.66\n TORT FEASOR 17.66\n WORKERS' COMP. 17.66\n TRICARE 14.73\n TRICARE REIMB. INS. 14.73\ntypes with new dispensing fee for third party pharmacy prescription\nclaims with an effective date of January 1st, 2019.\n \n Rate Type Dispensing Fee\n ------------------- --------------\n DENTAL REIMB. INS. 17.66\n HUMANITARIAN 17.66\n HUMANITARIAN REIMB. INS. 17.66\n\n
\nMCCF EDI TAS EPHARMACY BUILDS 5 & 6\n\n
\nThis patch addresses the following issues:\n \n- Update the MCCR UTILITY (#399.1) file for 2019.\n- Fix an undefined error at line A+7 in routine IBARXMP in the Push Rx \n Copay Cap Transactions [IBARXM CAP TRANS PUSH] option. \n\n
\nThis is the KIDS build for Integrated Billing patch IB*2*89. This\nreturn the external value of the prescription number, an undefined error\nwill occur when attempting to write that number to the error handler.\nThis patch will resolve the undefined error by checking for the existence\nof the prescription number prior to writing it to the error handler. If the\nnumber does not exist, it will be output as 'unknown'.\n \nREN-0299-61013\nCache systems do not interpret ascii character 13 as a carriage return,\nand thus READ statements are not terminated as expected. A change was\nmade to interpret the values of the variables 'read' by the system to\npatch resolves three nois calls:\ndetermine if the READ statement was terminated as expected.\n \nREN-0799-61875\nThe Tricare fiscal intermediary is not accepting electronic transactions\nwith prescription numbers that contain a trailing alpha character. A\nchange was made to strip trailing alpha characters from the\nprescription number.\n \nLOM-0997-62248\nThe 'IB - CHAMPUS Primary Billing Task' is queued off as a result of the\n'Start the Champus Rx Billing Engine' [IB CHAMP ENGINE START] option. One\nof its tasks is to process all prescriptions queued for billing. An\ninterface exists between IB and the Pharmacy package, to return necessary\ninformation about the prescription. If the Pharmacy interface fails to\n\n
\nTEST v\n\n
\nREASONABLE CHARGES V3.25; REVENUE CODE #124 FOR 5 MH MS-DRGS OF R&B CHARGE\nITEMS\n\n
\nThis patch addresses the following issues:\n \n-Insurance claims with multiple service line items/dates on the bill were\n not transmitted electronically properly.\n-The BILLING FACILITY NAME (#200) field in the INSTITUTION (#4) file was \n not correctly populated on the uniform billing form UB-04 FL-1.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal year 2020 changes, effective 10/01/2019.\n\n
\nDIAGNOSTIC MEASURES-PHASE III\n\n
\nThis patch addresses updates of Cost Based and Inter Agency rates with an\neffective date of 10/01/2019 in the CHARGE ITEM file (#363.2).\n\n
\nPlease see the IB*2.0*627 patch description for detailed information \nregarding this patch.\n\n
\nThis patch, IB*2.0*661, is one of three VistA 2020 threshold patches. It \naddresses the annual updates for the Pharmacy Copay Thresholds. Patch \nDG*5.3*995 will update the thresholds for the Means Tests and the Maximum\nAnnual Pension Rate. Patch EAS*1.0*182 will address the annual updates for\nthe GMT Thresholds.\n\n
\nIB TAS Build 7/8/9 Port of 837 transaction to TAS Core platform\n\n
\nThis patch will update the administrative charge based on the \n CC TORT FEASOR 18.38\n CC WORKERS' COMP 18.38\n CCN NO-FAULT AUTO 18.38\n CCN REIMB INS 18.38\n CCN TORT FEASOR 18.38\n CCN WORKERS' COMP 18.38\n CHOICE NO-FAULT AUTO 18.38\n CHOICE REIMB INS 18.38\n CHOICE TORT FEASOR 18.38\n CHOICE WORKERS' COMP 18.38\nfollowing rate types with new dispensing fee for third party pharmacy\n DENTAL REIMB. INS. 18.38\n HUMANITARIAN 18.38\n HUMANITARIAN REIMB. INS. 18.38\n INELIGIBLE 18.38\n INELIGIBLE REIMB. INS. 18.38\n INTERAGENCY 18.38\n NO FAULT INS. 18.38\n REIMBURSABLE INS. 18.38\n TORT FEASOR 18.38\n WORKERS' COMP. 18.38\nprescription claims with an effective date of January 1st, 2020.\n TRICARE 15.45\n TRICARE PHARMACY 15.45\n TRICARE REIMB. INS. 15.45\n \n Rate Type Dispensing Fee\n -------------------- -------------\n CC MTF REIMB INS 18.38\n CC NO-FAULT AUTO 18.38\n CC REIMB INS 18.38\n\n
\nREASONABLE CHARGES V3.26\n\n
\nNOIS Resolution and Minor Updates\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal mid-year 2020 changes, effective 04/01/2020.\n\n
\nREASONABLE CHARGES V3.27; PROVIDER PERSON CLASS VA080100\n\n
\n(1)This patch fixes CLAIMS TRACKING EDIT [IBT EDIT TRACKING ENTRY when \nfield ITEM (#4) does not exist in file RECORD OF PROS APPLIANCE/REPAIR \n(#660).\n \n(2)This patch fixes Add/Edit Pts. Continuously Hospitalized Since 1986 \n[IB FLAG CONTINUOUS PATIENTS] to use correct FileMan date variable.\n\n
\nMCCF EDI TAS EPHARMACY BUILD 13\n\n
\nThis patch addresses the following issue:\n \n1. Users cannot remove an incorrect Sponsor on screen 15 of the\n Load/Edit Patient Data [DG LOAD PATIENT DATA] option if Sponsor is in \n the PATIENT (#2) file.\n\n
\nThis patch contains a routine to update the parameter "NUMBER OF\nDAYS PATIENT CHARGES HELD" from 90 to 150 in file (350.9).\n\n
\nNew calculations for Rx copayment if HRfS flag is active.\n\n
\nThis patch involves updates to the MCCR UTILITY (#399.1) file, the REVENUE\nCODE (#399.2) file and the CLAIMS TRACKING NON-BILLABLE REASONS (#356.8)\nfile for 2020.\n\n
\nThe patch will reactivate 11 Reasons Not Billable (RNBs) that were \nrequested to be deactivated with IB*2.0*673 in the CLAIMS TRACKING\nNON-BILLABLE REASONS (#356.8) file.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal year 2021 changes, effective 10/01/2020.\n\n
\nThis patch updates the Cost Based and Inter Agency rates with an effective\ndate of 10/01/2020 in the CHARGE ITEM file (#363.2).\n\n
\nePayments build 9\n\n
\nFIXES TO DIAGNOSTIC MEASURES REPORTS\n\n
\nMCCF EDI TAS EBILLING BUILD 10/11 277STAT PORT\n\n
\nIB*2.0*685 (Integrated Billing) is bundled with DG*5.3*1025 \n \nThe billing users of the [IB OUTPUT PATIENT REPORT MENU] menu need access \nto REGISTRATION menu options [DG OTH FSM ELIG. CHANGE REPORT] and [DG OTH \nFSM DETAIL REPORT] from patch DG*5.3*1025.\n(Registration) in host file.\n \nThe SHRPE product makes enhancements to the Registration (patch \nDG*5.3*1025) to implement reports that would help Registration and Billing\nusers to identify patients that were treated under Other Than Honorable\nauthority and provide details about eligibility changes and VA care\nprovided to these patients. The reports are developed in DG namespace but\nneed to be available to both Registration and Integrated billing users.\n\n
\nPatch IB*2.0*692 addresses the annual updates for the Pharmacy Copay\nThresholds.\n\n
\nThis patch will update the administrative charge based on TRICARE\n TRICARE REIMB. INS. 16.11\nrate types with new dispensing fee for third party pharmacy prescription \nclaims with an effective date of January 1st, 2021.\n \n \n Rate Type Dispensing Fee\n -------------------- --------------\n TRICARE 16.11\n TRICARE PHARMACY 16.11\n\n
\nREASONABLE CHARGES V4.21\n\n
\nThis patch will update the administrative charge based on the following\n CC TORT FEASOR 20.71\n CC WORKERS' COMP 20.71\n CCN NO-FAULT AUTO 20.71\n CCN REIMB INS 20.71\n CCN TORT FEASOR 20.71\n CCN WORKERS' COMP 20.71\n CHOICE NO-FAULT AUTO 20.71\n CHOICE REIMB INS 20.71\n CHOICE TORT FEASOR 20.71\n CHOICE WORKERS' COMP 20.71\nrate types, with new dispensing fee for third party pharmacy prescription \n DENTAL REIMB. INS. 20.71\n HUMANITARIAN 20.71\n HUMANITARIAN REIMB. INS. 20.71\n INELIGIBLE 20.71\n INELIGIBLE REIMB. INS. 20.71\n INTERAGENCY 20.71\n NO FAULT INS. 20.71\n REIMBURSABLE INS. 20.71\n TORT FEASOR 20.71\n WORKERS' COMP. 20.71\nclaims, with an effective date of January 1st, 2021.\n \n Rate Type Dispensing Fee\n -------------------- -------------\n CC MTF REIMB INS 20.71\n CC NO-FAULT AUTO 20.71\n CC REIMB INS 20.71\n\n
\nBackup of IB*2.0*695 on Apr 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nMedicare Insurance Intake\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect \nFiscal mid-year 2021 changes, effective 04/01/2021.\n\n
\nBackup of IB*2.0*668 on Apr 05, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of IB*2.0*693 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nREASONABLE CHARGES V4.215\n\n
\nBackup of IB*2.0*696 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of IB*2.0*688, DG*5.3*1034 on Apr 29, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nIB*2.0*688 (Integrated Billing) is bundled with DG*5.3*1034 (Registration)\nin host file IB_2_0_P688.KID .\n \nThis patch introduces the API to provide IB data to Presumptive Psychosis \nand OTH billing reports designed within the Registration application.\n \nThe Integration Control Registration #7202 was entered to allow the\nRegistration application to use the API in Integration Billing application\n\n
\nBackup of BPS PSO IB BUNDLE 16.0, BPS*1.0*28, PSO*7.0*560, IB*2\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nCPT MODIFIERS Initiative: Update transfer of CPT Modifiers to/from PCE.\n\n
\nIB*2*697 (Integrated Billing) is bundled with DG*5.3*1035 (Registration) \nand OR*3.0*546 (Order Entry/Results Reporting) in host file\nIB_2_0_P697.KID.\n \nThis patch modifies the IBEFSMUT routine to include the partial fill \nprescription of the return array.\n\n
\nBackup of IB*2.0*703 on Jun 21, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of IB*2.0*700 on Jul 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses an undefined error at line THRESQ \nin routine IBARXEU1 when entering a beneficiary travel claim in the\nClaim Enter/Edit [DGBT BENE TRAVEL SCREEN] option.\n\n
\nBackup of IB*2.0*676 on Aug 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe INTEGRATED BILLING package needs to run the REGISTRATION report \nimplemented as MAIN^DGOTHFSM modified in the patch DG*5.3*1047 to display\ninformation for INTEGRATED BILLING (IB) users. This report identifies\nFormer Service Members whose Primary Eligibility changed from EXPANDED MH\nCARE NON-ENROLLEE to a new Primary Eligibility with a VERIFIED eligibility\nstatus. These patients are no longer treated under the Other Than\nHonorable (OTH) authority (VHA Directive 1601A.02).\n\n
\nBackup of IB*2.0*650 on Aug 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nIB*2.0*124: Miscellaneous updates and NOIS resolution\n \nUpdates to Output Formater: Pre-init: 364.6 - 618,763,764\n Install: 364.7 - 496,641,642,789\n 364.5 - 114,116,117,118,119,155\n\n
\nBackup of IB*2.0*706 on Aug 24, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch updates Integrated Billing Clinic Stop Codes to reflect fiscal \n2022 changes, effective 10/01/2021.\n\n
\nWhen the PC Process COB action is performed to the secondary payer and \nthe secondary bill already defined for the series error\nis found for the claim, the system just goes back to the WorkList in the\nMRA Management WorkList [IBCE MRA MANAGEMENT] option.\n\n
\nThis patch addresses updates of Cost Based and Inter-Agency rates with an\neffective date of 10/01/2021 in the CHARGE ITEM file (#363.2).\n\n
\nThe purpose of this patch is to update and file the new fiscal year \nthreshold rates for the Maximum Annual Rate of Pension which\nis required for use in the Integrated Billing software application.\nIn addition, a new TYPE (.02) of "Basic Pension" has been added\nto the BILLING THRESHOLDS file (354.3) to lessen the confusion\nwhen entering the default basic threshold rates. Minor software changes\nhave also been made to accommodate this new field type. \n \n\n
\nREASONABLE CHARGES V4.22\n\n
\nMCCF EDI TAS EINSURANCE 18\n\n
\nPatch IB*2.0*723 addresses the annual updates for the Pharmacy Copay\nThresholds.\n\n
\nThis patch will update the administrative charge based on TRICARE\n TRICARE REIMB. INS. 11.79\nrate types with new dispensing fee for third party pharmacy prescription \nclaims with an effective date of January 1st, 2022.\n \n \n Rate Type Dispensing Fee\n -------------------- --------------\n TRICARE 11.79\n TRICARE PHARMACY 11.79\n\n
\nREASONABLE CHARGES V4.225\n\n
\nThis patch will update the administrative charge based on the following\n CC TORT FEASOR 13.26\n CC WORKERS' COMP 13.26\n CCN NO-FAULT AUTO 13.26\n CCN REIMB INS 13.26\n CCN TORT FEASOR 13.26\n CCN WORKERS' COMP 13.26\n CHOICE NO-FAULT AUTO 13.26\n CHOICE REIMB INS 13.26\n CHOICE TORT FEASOR 13.26\n CHOICE WORKERS' COMP 13.26\nrate types, with new dispensing fee for third party pharmacy prescription \n DENTAL REIMB. INS. 13.26\n HUMANITARIAN 13.26\n HUMANITARIAN REIMB. INS. 13.26\n INELIGIBLE 13.26\n INELIGIBLE REIMB. INS. 13.26\n INTERAGENCY 13.26\n NO FAULT INS. 13.26\n REIMBURSABLE INS. 13.26\n TORT FEASOR 13.26\n WORKERS' COMP. 13.26\nclaims, with an effective date of January 1st, 2022.\n \n Rate Type Dispensing Fee\n -------------------- -------------\n CC MTF REIMB INS 13.26\n CC NO-FAULT AUTO 13.26\n CC REIMB INS 13.26\n\n
\nInitial Patch Description for IB*2.0*665\n\n
\nEnhancements to the Vets with Insurance Reports\n\n
\nUpdate Provider Discount groups and add 2 Revenue Codes.\n\n
\nThis patch addresses an undefined error at line BLD+26 in routine IBTODD \nin the Days Denied Report [IBT OUTPUT DENIED DAYS REPORT] option.\n\n
\nThis patch involves updates of the MCCR UTILITY (#399.1) file, the REVENUE\nRevenue Code\n============\n161 RM AND BRD-OTHER-HOSPITAL@HOME (new)\n \nPlace of Service Code\n======================\n10 TELEHEALTH PROVIDED IN PATIENT'S HOME (new)\nCODE (#399.2) file and the PLACE OF SERVICE (#353.1) with the following\ncodes for 2022.\n \n \nOccurrence Span Code\n====================\n82 HOSP AT HOME CARE DATES (update)\n \n\n
\n \nEMERGENCY STOP CODE UPDATE RELATED TO PACT ACT FOR FY 2023\n\n
\nRAI/MDS Support: add cross references to fields so they may be monitored.\n\n
\nCOST BASED/INTER AGENCY Rate (CBIAR) UPDATE FY23\n\n
\nIntegrated Billing patch, IB*2.0*753 addresses the annual updates\nfor the Pharmacy Copay Thresholds.\n\n
\nREASONABLE CHARGES V4.23\n\n
\nIntegrated Billing patch, IB*2.0*750, will update the administrative\ncharge based on TRICARE rate types with new dispensing fee for third party\npharmacy prescription claims with an effective date of January 1st, 2023.\n\n
\nIntegrated Billing patch, IB*2.0*754, updates the administrative\ncharge based on the following rate types, with new dispensing fee for\nthird party pharmacy prescription claims, with an effective date of\nJanuary 1st, 2023. The following rate types will be created:\n\n
\nREASONABLE CHARGES V4.235\n\n
\nMinor updates and NOIS resolution.\n\n
\nThis patch updates two options that allow for the releasing of copay \ncharges with a status of On Hold to include a check for duplicate copays.\n \nThis same duplicate copay check has also been added to the nightly\nbackground job to perform those same checks for charges that are being\nreleased due to hitting the end of the 90-day window for On Hold charges.\n\n
\nIB MID YEAR STOP CODE UPDATE FY23\n\n
\nTransfer Pricing\n\n
\nIB STOP CODE UPDATE FY24\n\n
\n \nThis patch creates a new system that will use HL7 messages sent \nand then processed by the Data Access Service (DAS) to synchronize\nthe MEANS TEST BILLING CLOCK (#351) file across the VA Enterprise.\n\n
\nCBIAR FY24 Update\n\n
\nCPT 2000 Replacement Charges for RC v1.\n\n
\nePayments Build 19\n\n
\nIntegrated Billing patch, IB*2.0*780 addresses the annual updates\nfor the Pharmacy Copay Thresholds.\n\n
\nIf a non-exempt patient has a previous year Means Test on file, with the \nIncome Verification Match (IVM) Center as the source of the \ndetermination, the new RX copay exemption is not being entered in the \nBILLING EXEMPTIONS (#354.1) file.\n\n
\nIntegrated Billing patch, IB*2.0*774, will update the administrative\ncharge based on TRICARE rate types with new dispensing fee for third party\npharmacy prescription claims with an effective date of January 1st, 2024.\n\n
\nIntegrated Billing patch, IB*2.0*781, updates the administrative\ncharge based on the following rate types, with new dispensing fee for\nthird party pharmacy prescription claims, with an effective date of\nJanuary 1st, 2024. The following rate types will be created:\n\n
\nCY2024 Reasonable Charges Update V5.24\n\n
\nPatient Billing Enhancements:\n \n \n This is the Patient Billing Enhancement KID's Distribution for Patch\nIB*2.0*132. For specific information relating to the installation of this\nKID's distribution please see the National Patch Module section Patch\nDescription subsection Installation Instructions.\n\n
\nIB STOP CODE UPDATE MID YEAR 2024\n\n
\n RNB FILE UPDATE 2024\n\n
\n2024 UPDATES OF CONDITION CODES & PLACE OF SERVICE CODES\n\n
\n RNB ADDITIONAL UPDATE 2024\n\n
\nReasonable Charges v1.1 and related updates.\n\n
\nFY25 STOP CODE CHANGES\n\n
\nV1 \n\n
\nIntegrated Billing patch, IB*2.0*780 addresses the annual updates\nfor the Pharmacy Copay Thresholds.\n\n
\nFY25 REASONABLE CHARGES UPDATE\n\n
\nIntegrated Billing patch, IB*2.0*810, updates the administrative\ncharge based on the following rate types, with new dispensing fee for\nthird party pharmacy prescription claims, with an effective date of\nJanuary 1st, 2025. The following rate types will be created:\n\n
\nTRANSFER PRICING UPDATE\n\n
\n*** Please Note: This patch has a shortened compliance date of 7 days. ***\n -------------------- -------------\n TRICARE 14.78\n TRICARE PHARMACY 14.78\n TRICARE REIMB. INS. 14.78\n \nIntegrated Billing patch, IB*2.0*815, will update the administrative\ncharge based on TRICARE rate types with new dispensing fee for third party\npharmacy prescription claims with an effective date of January 1st, 2025.\n \n \n \n Rate Type Dispensing Fee\n\n
\nIB*2.0*814\n\n
\nIntegrated Billing patch, IB*2.0*818, is a fix for the annual updates\nfor the Pharmacy Copay Thresholds patch IB*2.0*808 after receiving \nincorrect rates from business.\n\n
\nThis patch fixes a potential undefined error that occurs when creating \na bill with at least 16 diagnosis codes.\n\n
\nFY25 Mid Year Stop Code Changes for Veteran Copays \n\n
\nHospice IB Error Encountered Message Issue\n\n
\nThis patch fixes the List Plans by Insurance Company option. \nCharge Master.\nThe SHORT ID was not listing for those patients that \nhad an Eligibility of Tricare/Champus. This patch also fixes \nthe updating of the COVERED BY HEALTH INSURANCE\nfields in the patient file when the verify coverage of insurance\nprompt is answered. This patch also fixes the due date for the \npatients Means Test. After the leap year date of 2/29 the due dates \nfor the means test are off by 1. This patch fixes this.\nThis patch also adds the new Outpatient Co-pay Rate of $50.80 into the\n\n
\nV1\n\n
\nThe purpose of the patch is to remove the HEADER code from the List \nTemplate IBNCPDP LSTMN CT. The Current code in this field is D \nHDR^IBNCPDPC this line in the routine IBNCPDPC no longer exists. The call \nreplacing this in D HDR^IBTRED, which is the current header call for \nclaims tracking. The error occurs in the worklflow of a user \nprocessingclaims in the 'ECME User Screen' option, then the call the \n'IBNCPDP LSTMNCT' from this option to add comments then tries to return \nto the 'ECMEUser Screen'\n\n
\nWhen an attempt to assign an NPI to a Non/Other VA Provider using the \nIBCE PROVIDER MAINT option. And a previous record in the Institution File \n#4 used the NPI has no effective date yet retains the "ANPI" cross\nreference in file four, an incorrect error is presented and the user is \nnot allowed to assign the NPI again. This remediation now checks for an \neffective date before allowing the message to present and denial of \nre-assignment of the NPI.\n\n
\nUtilizing the existing infrastructure put into place with\nIB*2.0*704, this patch facilitates the exchange of Copay Information\nbetween existing copay interfaces within Vista that will be\nsynchronized to create a bi-directional integrated Copay Accumulators\nplatform with Oracle. Previously this interface utilized Data Access\nService (DAS) as the middleware, but updates will be made to use Veterans\nData Integration and Federation (VDIF) to facilitate the communication\nbetween VistA and Oracle Health. \n\n
\nThis patch fixes two data related problems with sending \nat some sites because the fiscal intermediary is requiring \nmore specific data values for these two fields.\nSome sites are not having any problems with this and do \nnot want to change and send more specific values for these \ntwo fields. Two new fields have been added to \nthe IB SITE PARAMETERS file so the sites can choose \nto send the DEA# vs the Prescriber ID, and choose \nto send the more specific 1 or 2 for the compound code \nas opposed to a zero.\nspecific data to the fiscal intermediary for billing \nTricare patients. The fiscal intermediary is requiring \nthe DEA# be sent in place of Prescriber ID for a \nprovider reference. For the drug, a zero was being \nsent to the fiscal intermediary as the number of\ningredients in a prescription. The fiscal intermediary \nis requiring a 1 (non-compound drug) or a 2 (compound drug)\nfor the number of ingredients. Claims are being rejected \n\n
\nINSURANCE TREND REPORT PROBLEM\n\n
\nSupport for AR Third Party Payments report.\n\n
\nFix for Insurance Buffer delay problem.\n\n
\nIB Insurance Buffer API for 1010EZ.\n\n
\nMRA Extract patch.\n\n
\nBILLING ENHANCEMENTS FOR EDI\n\n
\nThis patch corrects two problems.\nautomatic copy from the institutional to the professional bill is done.\n1. The first problem affects HCFA-1500 bills that were created\nprior to the installation of patch IB*2.0*51. If there was already data\nin the BLOCK 31 data field (screen 8 of the ENTER/EDIT BILLING SCREENS),\nbut not in the provider multiple, there should have been an error on\nauthorization of this bill, but the edit check was erroneously passing.\n2. The second problem affects institutional claims that have professional\ncomponents that require a separate HCFA 1500 bill to be produced. The TC\nmodifier should not be copied over to the professional bill when the\n\n
\nChanges have been made to routines IBOMTC and IBOMTC1 to\nstarting date is defaulted to November 30, 1999.\nidentify Purple Heart patients. When the Cat C Activities report is run,\nthe PH indicator is checked and Purple Heart patients are flagged on\nthe report. Purple Heart patients will be identified by an '*' in\nfront of their name. \n \nThe report has also been edited to give the user a choice of listing only\nPurple Heart recipients or both Purple Heart and non recipients. \nIf the user chooses to list only Purple Heart recipients, the report\n\n
\nThis is the KIDS distribution for patch IB*2*123, Diagnostic\nMeasures Phase IV. The accompanying Accounts Receivable patch\nis PRCA*4.5*167. This patch also fixes the problem reported in\nthe Third Party Follow-up Report - NOIS #OKL-0100-72387.\n\n
\nThis patch updates the ACCOUNTS RECEIVABLE CATEGORY (#.06) in the RATE TYPE\n(#399.3) file for the DENTAL entry from "INELIGIBLE HOSP" to "EMERGENCY/\nHUMANITARIAN".\n\n
\nIB*2*150 OUTPATIENT MEDICATION COPAY CAP PHASE 1, PATCH 1\n\n
\nINSURANCE MODULE PROBLEMS\n\n
\nReasonable Charges v1.2\n\n
\nThis patch contains fixes to minor problems introduced by patch IB*2*51\n \nALT-0501-20830 Sites with a marital status file whose internal entry\nnumbers differ from the national standard are getting erroneous data on\nthe HCFA 1500 and UB92 bills.\n \nLOM-0401-62250 Multiple page UB92's printed an extra page if the\ndescription portion of box 44 exceeded one page.\n \nLOM-0401-61961 The patient's name was not printing in boxes 12 and 13\non the HCFA 1500 if the bill was for other than reimbursable insurance.\nNOIS entries fixed include:\n \nLOM-0501-61752: The treatment authorization code was not printing in\nbox 63 of the UB92 if the bill was for other than reimbursable insurance.\nThis same problem was found with the INSURANCE CO NUMBER (box 60),\nRELEASE OF INFORMATION (box 52) and ASSIGNMENT OF BENEFITS (box 53).\n \nSLC-0501-51272: The help text on the PERFORMED BY field of the PROVIDERS\nmultiple (#222) of the BILL CLAIMS file (#399) should not reference\nSLF000 as a valid entry. This can be seen on screen 8 of the BILLING\nSCREENS in the PROVIDERS edit group.\n \n \nSTC-0501-42551: Most Commonly Used Outpt CPT Codes Rpt is missing the\nprocedure short name.\n \nCHY-0501-52377: The insured's id number was not printing in box 1A o\nthe HCFA 1500 if the bill was for other than reimbursable insurance.\nSPO-0501-50868 If there is a print order on duplicate procedures for a\nHCFA 1500 bill, only the first duplicate procedure prints, although the\ntotal charges reflect the total of the duplicate procedures.\n \nDUR-0501-30976 There was a hard error encountered when duplicate\nprocedures existed with different box 24 free text or box 24K data.\n\n
\n \nPASSING OF REASON CANCEL TO AR:\n===============================\n \n \nThis is the Passing Of Reason Cancel to AR KID's Distribution for Patch\nIB*2.0*142. For specific information relating to the installation of this\nKID's distribution please see the National Patch Module section Patch\nDescription subsection Installation Instructions.\n\n
\nFIX RX COPAY RESET/REMOVE CHARGES\n\n
\nUpdate Claims Tracking to accept the original fill of a Prescription.\n\n
\nELIMINATE MEANS TEST CATEGORY\n\n
\nThis is the KIDS distribution for patch IB*2*159, Diagnostic Measures\nUpdates.\n\n
\nThis patch changes the NUMBER OF DAYS PT CHARGES HELD field (#7.04)\nin the IB SITE PARAMETERS file #350.9 from 150 to 90.\n\n
\nThis is the first phase of the LTC COPAYMENTS project. This software\nchange will not become effective until the LTC REG is passed into law,\nwhich is expected in DEC 2001. Once the law is passed, another patch\nwill be sent to the field which will ACTIVATED this software change.\n\n
\nSTOP OUTPATIENT COPAY BILLING PENDING IMPLEMENTATION\n\n
\nSPECIAL CONDITION (SC) PROBLEM\n\n
\nOUTPATIENT MEDICATION COPAY CAP PHASE 1, PATCH 2 AND PHASE 2\n\n
\nThis patch implements functionality to support the outpatient\nvisit co-payment regulation.\n\n
\nIB update due to Prosthetics Encounter changes (RMPR*3*62).\n\n
\nThis patch contains the functionality to begin electronic billing through\nthe clearinghouse WebMD. See the patch module and release notes that\naccompany this patch for further documentation.\n \nINCLUDES NOIS: RIC-0501-22630 \n ROS-0601-52681\n\n
\nUpdate of visit copay tiers.\n\n
\nIB*2*171 MILL BILL LTC, PHASE 2, PATCH 1\n\n
\nThe patch contains modification of Outpatient Copay (RX) software to \n \nThe patch resolves NOIS # BUT-0502-21665.\nlimit execution of RPC "IBARXM QUERY ONLY" with VAMC, M&ROC and RO-OC\nfacilities only.\nBesides this, the patch also contains a new RPC, "IBARXM QUERY SUPPRESS\nUSER" to replace "IBARXM QUERY ONLY". The new RPC does not transmit user\ndata to remote side. Two existing calls have been modified to suppress\nsending user data to remote side:\nIBARXM TRANS BILL\nIBARXM TRANS DATA\n\n
\nClaimsManager Interface\n\n
\nThis patch contains maintenance fixes and updates for Electronic Billing \n(EDI) Patch IB*2*137.\n\n
\nThis patch fixes problems that the 'Flow Chart from Entry Point' option\nwas having with parameter passing.\nThis problem was reported in NOIS: ISB-0594-30120\n \nroutine new checksum\nXTFC1 14453171\nXTFCE 5996229\nXTFCE1 6490782\n\n
\nPatch XT*7.3*137 addresses 4 issues:\n \n 1. Fields failing validation and preventing patient merge\n 2. Patient file pointer, .01 DINUMed fields that are new style \n xrefs are not merging properly on patient merge\n 3. Aliases duplicated on patient merge\n 4. 'Test patient Indicator' field being copied on patient merge\n\n
\nSubject: Update XINDEX to support SACWG changes\n 1. Patch XT*7.3*140\n \nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 1 minutes\nto install. TaskMan doesn't need to be stopped or paused\n \nInstallation Instructions:\n \n 1. From the Kernel Installation and Distribution System (KIDS) menu select\n Installation Menu.\n a) Contains 14 XINDEX routines\n \n 2. Use the Load a Distribution option to load the TOOLKIT_XINDEX_73.KID file\n \n 3. You may select the following options:\n \n A. Select the Verify Checksums in Transport Global option to confirm \n the integrity of the routines that are in the transport global. When \n prompted for the INSTALL NAME enter XT*7.3*140\n \n NOTE: Using <spacebar><enter> will not bring up a Multi-Package build \n b) Will update the XINDEX utility to support the new changes to the\n even if it was loaded immediately before this step. It will only \n bring up the last patch in the build.\n \n B. Select the Backup a Transport Global option to create a backup message\n of any routines exported with this patch. It will not backup any other\n changes such as DDs or templates. \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n Standards and Conventions (SAC). The following changes have been\n ii. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all of the components of this patch,\n such as routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the patch to install. \n \n Select Installation Option: Install Package(s)\n Select INSTALL NAME: XT*7.3*140\n \n approved by SAC Committee:\n Want KIDS to INHIBIT LOGONs during the install? NO//\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// \n \n \n Post-Installation Instructions:\n -------------------------------\n none\n \n \n 1) Routine name and labels can be 16 uppercase characters\n Backout and Rollback Procedure:\n ------------------------------- \n If rollback/backout is required, the installer can restore the routines\n using the MailMan message that were saved prior to installing the\n patch. The Data Dictionary changes are backwards compatible and can stay\n in production.\n \n \n Routine Information:\n====================\n 2) Local variable names can be 16 characters. \n \nThe second line of each of these routines now looks like:\n ;;7.3;TOOLKIT;**[Patch List]**;Apr 25, 1995;Build 38\n \nThe checksums below are new checksums, and\n can be checked with CHECK1^XTSUMBLD.\n \nRoutine Name: XINDX1\n Before: B20704192 After: B21263152 **20,61,66,68,110,121,128,133,140**\nRoutine Name: XINDX11\n 3) Namespaced variables must be all uppercase.\n Before: B11308547 After: B37513284 **20,27,121,132,140**\nRoutine Name: XINDX12\n Before: n/a After: B86657332 **140**\nRoutine Name: XINDX13\n Before: n/a After:B306834020 **140**\nRoutine Name: XINDX2\n Before: B28042462 After: B28369536 **20,27,48,110,121,133,140**\nRoutine Name: XINDX3\n Before: B15082410 After: B15493765 **20,27,61,68,110,121,128,132,\n 133,140**\n 2. Patch XU*8*661\nRoutine Name: XINDX5\n Before: B11294544 After: B11300370 **20,27,61,121,133,140**\nRoutine Name: XINDX51\n Before: B26771263 After: B32298369 **20,48,61,110,133,140**\nRoutine Name: XINDX52\n Before: B2709275 After: B2792889 **20,140**\nRoutine Name: XINDX53\n Before: B6321698 After: B6801223 **20,140**\nRoutine Name: XINDX6\n Before: B20048257 After: B20500720 **20,27,66,110,132,140**\n a) The ZOSFONT routine\nRoutine Name: XINDX7\n Before: B10829991 After: B11070196 **20,27,48,68,110,140**\nRoutine Name: XINDX8\n Before: B15029849 After: B15758649 **20,27,61,140**\nRoutine Name: XINDX9\n Before: B32506175 After: B33427538 **20,27,48,61,66,68,110,121,\n 132,133,140**\n \nRoutine list of preceding patches: 133\n \n \n b) 14 fields from 8 files that references a routine or tag \n \nPatch Components\n================\n none\n \n \nBlood Bank Clearance\n====================\nEFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XT*7.3*140 contains\nCategory: ROUTINE\nchanges to a package referenced in ProPath standard titled: BBM Team\nReview of VistA Patches. This patch does not alter or modify any VistA\nBlood Bank software design safeguards or safety critical elements\nfunctions.\n \nRISK ANALYSIS: Changes made by patch XT*7.3*140 have no effect on Blood\nBank software functionality, therefore RISK is none.\n \n \nDefect Tracking System Ticket(s) & Overview:\n \n============================================ \nTicket: I9055002FY16 - XINDEX doesn't support SACC changes to routine\n names and tags\n \nProblem:\n XINDEX utility needs to support routine name and labels to 16 characters\n and local variables names to 16 characters. Add support for all areas in\n VA FileMan that can contain M code.\n \nResolution:\n \n Change the following routines to support 16 characters and other M code:\n XINDX1\n XINDX11\n XINDX12\n XINDX13\n XINDX2\n XINDX3\n XINDX5\n XINDX51\n XINDX52\nDescription:\n XINDX53\n XINDX6\n XINDX7\n XINDX8\n XINDX9 \n \n \nTest Site:\n==========\nFargo, ND\n============\nSouth Texas, TX\n \n \nSoftware and Documentation Retrieve Instructions:\n=================================================\nNo changes have been made to Kernel documentation as a result of this\npatch. However, the most up-to-date VA Kernel documentation is\navailable on the VHA Software Documentation Library (VDL) at the\nfollowing:\n http://www.domain.ext/vdl/application.asp?appid=10\nThis build deploys changes to XINDEX and the ZOSF routine via 2 patches\n \nAn updated copy of the SAC is available at:\n http://go.domain.ext/sacc\n \nDownload TOOLKIT_XINDEX_73.KID from the ftp site. The preferred method is\nto SFTP the file from sftp://download.vista.domain.ext/. This transmits the\nfile from the first available SFTP server. Sites may also elect to retrieve\nsoftware directly from a specific server as follows:\n \nHines sftp://ftp.fo-hines.domain.ext\nbeing released in HOST file TOOLKIT_XINDEX_73.KID\nSalt Lake City sftp://ftp.fo-slc.domain.ext\n \nThe necessary file is TOOLKIT_XINDEX_73.KID, which is an ASCII file.\nMake a note of the directory name where the file was saved.\n \n \nPatch Installation:\n===================\n \nPre-Installation Instructions:\n\n
\nUse description on Forum.\n\n
\nThis is Toolkit patch XT*7.3*142 to support CPRS. Please reference to the \nNation Patch Module of this patch for more detail.\n\n
\nBackup of XT*7.3*148 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nBackup of XT*7.3*143 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis build is the initial installation release of the Kernel Toolkit \nVistA Package Utility.\n\n
\nBackup of XT*7.3*149 on Jun 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPlease see the description on Forum\n\n
\nBackup of XT*7.3*150 on Jul 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nToolkit patch XT*7.3*150 - FIX [XTPM NIGHTLY PATCH MONITOR] OPTION. \nPlease refer to National Patch Module for detail information.\n\n
\nPlease see Patch Description on Forum\n\n
\nPlease see Patch Description on Forum\n\n
\nPlease see Patch Description on Forum\n\n
\nTOOLKIT PATCH XT*7.3*154 - This patch fixes <SUBSCRIPT>SHOW+6^XDRDSHOW \nerror. Please refer to the National Patch Module for more information.\n\n
\nSee Patch Description for XT*7.3*152 on Forum Patch module.\n\n
\nPatch XT*7.3*158 implements a usability modification in XINDEX to allow\nit to read the entirety of a routine beyond what may be blank lines.\n\n
\nAllow routine names of up to 16 characters in routine compare (as per \nSAC).\n\n
\nF#25580312 XINDX10 Was getting a UNDEF when XINDEXing a Build\n\nISA-0698-11515 XINDX11 The KIDS build pre/post install routines were\n not included.\n\nLocal Error log XTRMON Incorrect starting value when monitoring ALL\n routines.\n\nMessage from Ed @ Micronetics about changes they made to use with MSM.\nOnly updates to the standard and general fixes were included.\n\nISW-0698-21653 with a partial file send.\nMessage from Pat Redington @ SLC about a problem running XINDEX on a\npartial file build.\n\n Checksum\nRoutine Old New 2nd Line\nXINDEX 8229005 8423982 **20,27**\nXINDX10 13440865 13730836 **20,27**\nXINDX11 7648100 7252133 **20,27**\nXINDX2 5457656 5618431 **20,27**\nXINDX3 3946423 4134014 **20,27**\n \nXINDX5 7001485 6939608 **20,27**\nXINDX6 10238332 10371813 **20,27**\nXINDX7 7680200 7896227 **20,27**\nXINDX8 6232391 6601958 **20,27**\nXINDX9 4248028 4321464 **20,27**\nXTRMON 2510222 2618426 **27**\n\nList of preceding patches: 20, 27\n\n========================================================================= \nISH-1197-40901 XINDX10 When doing a XINDEX of a BUILD the count of\nInstallation:\n 1. DSM sites- These routines aren't usually mapped \n so you will probably not have to disable mapping.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\nISA-0698-11515 routines indexed was wrong. The count of\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n routines now lists anything that starts with\n option:\n Install Package(s) 'XT*7.3*27'\n =========\n \n 6. DSM Sites, after patch has installed, rebuild your map set, If needed.\n\n=========================================================================\n\n a '|' as a Faux Routines.\n i.e. Routines: 11 Faux Routines: 5\n\n\n
\nThis build contains files, routines, and options in support of generic\nparameters functionality exported with patch XT*7.3*26.\n\n
\nThis patch fixes two NOIS's for the XPAR package.\n could run into each other. Moved columns apart\n and use a $E to limit the size. \n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;7.3;TOOLKIT;<patchlist>;Apr 25, 1995\n\n Checksum\nRoutine Old New 2nd Line\n \nXPARDD 7153031 7342389 **26,35**\nXPAREDT2 6057876 6104530 **26,35**\n\nList of preceding patches: 26\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines maybe mapped,\nNOIS RTN Description\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n This patch can be queued for install at non-peak hours.\n\n\nIND-1298-71717 XPARDD When making a call to EN^XPAR and the data is \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XT*7.3*35'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n a set of codes, sometimes it would talk. This\n 6. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\n unwanted behavior has been fixed. \n\nPUG-0399-51652 XPAREDT2 When displaying some types of data, the two columns \n\n
\nHans found that when doing a save or move in the ^%Z editor if the\nending point passed a second TAG then the save or move would never end.\n \nroutine new checksum\nZTEDIT2 12127551\n\n
\nThis patch updates two Kernel tools to make use of the KIDS build file\nfield CHECKSUM VALUE. \nXTRUTL also has other entry points:\n DO UPDATE^XTRUTL will update the checksum field for all the routines in a\n build. Used after a patch has been released to capture the current checksum\n values.\n UD1^XTRUTL(routine) will update the checksum for just one routine.\n SHOW^XTRUTL(routine) will show the saved checksum and the current checksum.\n\n \nThe patch also fixes an error that was reported in OR*3.0*10 PATCH TRACKER\nand adds menu options for them to the KIDS Edit and Distribution menu.\n (#29934111) No quit value, at OUT+2^XPARDD. \n\nThe patch also addresses NOIS ISL-1199-51331 Add Device file as a Parameter\n entity. To do this the patch has the DD for file 8989.5 field .01.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;7.3;TOOLKIT;<patchlist>;Apr 25, 1995\n\nThe two routines are XTRUTL and XTVNUM.\n Checksum\nRoutine Old New 2nd Line\nXPARDD 7342389 7348385 **26,35,39**\nXTRUTL 3298825 5471022 **20,39**\nXTVNUM 9944358 9971672 **20,39**\n\nList of preceding patches: 20, 35\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \n\nInstallation:\n\n>>>Users may remain on the system.\n\n 1. DSM sites - Some of these routines may be mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \nXTVNUM will set the second line for each routine of a build. It loads the\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nVersion number for packages or adds the patch number for patches.\n 4. Users can remain on the system. This patch can be loaded any\n non-peakpeak time.\n This patch can be queued for install at non-peak hours.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XT*7.3*39'\n =========\n \n\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n\n==============================================================================\nXTRUTL is used to provide the Routine Summary list that needs to be included\nin patch descriptions. It keeps the old checksum in the routine file in \n\n
\nISD-0200-72703 XINDX51 If run against a build that deleted PRE/POST INIT\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;7.3;TOOLKIT;<patchlist>;Apr 25, 1995\n\n Checksum\nRoutine Old New 2nd Line\nXINDEX 8423982 8426779 **20,27**\nXINDX2 5618431 5844260 **20,27,48**\nXINDX51 9238490 9410365 **20,48**\n routines it would get and error.\nXINDX7 7896227 7580120 **20,27,48**\nXINDX9 4321464 4637748 **20,27,48**\n\nList of preceding patches: 27\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n========================================================================= \nInstallation:\n\n>>>Users may remain on the system.\n Fixed to check that each routine exisits first.\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n \n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peakpeak time. Taskman can continue to run.\n\nTAM-0599-32232 XINDX9 Fixed to correctly ID this bad code.\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XT*7.3*48'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\nWPB-0498-32337\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n =========================================================================\nHOU-0400-72028 XINDX2 Fixed. Was looking at code as a pattern match.\nAlbany ISC XINDX7 Didn't allow use of two argument form of $QUERY. \n \n\n
\n ** Only MSM sites need to install this patch **\nFrom: MPM in 'DAILY MPM' basket. Page 1\n deal with reports, <CLOBR> errors could be reported if someone is running\n a report.\n \n 1. Use TaskMan's Schedule/Unschedule to *unschedule* the following\n option: [XUCSTASK PURGE CM DATA] 'Auto Purge of CM Data'. See\n Enhancement #5 above.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'\n--------------------------------------------------------------------------\n 4. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 5. On the KIDS menu, under the 'Installation' menu, use the option\n 'Verify Checksum in Transport Global' and verify that all routines\n have the correct checksums.\n 6. On the KIDS menu, under the 'Installation' menu, use the option\n 'Install Package(s)'. Select the package 'XT*7.3*14' and proceed\n with install.\n 7. Move the routines to the other Compute/Print servers only.\n \n=========================================================================\n ====================================================================\n \n ROUTINES:\n \n Name Before After Patch List\n XUCS2E 5426963 5731962 14\n XUCS4E 1556880 1693814 14\n XUCS4R 11613596 12001291 6,14\n XUCS4RB 9713051 10100746 6,14\n XUCSRV 5969322 5755562 14\nCLARKSBURG, WV MPM Summary for FEB 16, 1996 to FEB 16, 1996 (AM&PM)\n XUCSTME 13223145 13388433 14\n XUCSUTL3 11346798 11524190 6,12,14\n XUCSXCD *new* 6351363 14\n XUCSXDR *new* 11901373 14\n XUCSXGR *new* 7068507 14\n XUCSXRT *new* 5016229 14\n XUCSXST *new* 5797377 14\n=========================================================================\n Node 540CSA 540CSB 540FSA 540FSB 540FSC 540PSA\n CPU Usage % 61 58 8 4 11 37\n Disk Usage % 30 26 47 28 50 14\n Response Time Sec 0.56 0.62\n RTs<2 Seconds % 96 96\n There are no known NOIS's associated with this patch\n Responses/S 9.9 10.9\n Ave. # Jobs 51 51 10 10 10 26\n Term InChar/S 19 17 24\n Term OutChar/S 971 894 0 0 457\n M Commands/S 5958 5917 341 206 982 4059\n Global Gets/S 1139 1116 41 23 35 1089\n Global S&Ks/S 58 55 9 9 39 46\n Disk Reads/S 50 45 21 9 11 19\n Disk Writes/S 5 4 2 2 8 6\n Read Cache % 93 93 92 93 96 96\n \n Write Cache % 86 86 51 67 67 81\n DDP Requests/S 18 17 4 3 14\n RVG Requests/S 545 568 443\n RVG Cache % 93 94 93\n RTH Sessions 2 2 2 2 2 2\n \n Routines affected - XUCSTME, XUCSRV\n \n Enhancement #2 - The routines that are used nationally to compile\n monthly comparisons can now be used locally. One menu, with five\n Enhancement #1 - As suggested both by the field and 486 Customer\n options, and one option have been added to the CM REPORTS menu - they\n are:\n \n [XUCSX DAILY REPORT] (option)\n [XUCSX LOCAL XSITE REPORTS] (menu)\n [XUCSX LOCAL XSTE PREF] (option)\n [XUCSX LOCAL XSITE RT] (option)\n [XUCSX LOCAL XSITE SYSSTATS] (option)\n [XUCSXGR LOCAL XSITE GREF ALL] (option)\n [XUCSXGR LOCAL XSITE GREF VG] (option)\nService Team, a "Morning Report" in the form of a mail message, will be\n New Routines - XUCSXCD, XUCSXDR, XUCSXGR, XUCSXRT, XUCSXST\n \n Enhancement #3 - A new field was added to the RAW STATISTICS multiple of\n file #8987.2. This field is called RVG HITS and represents the number of\n RVG cache hits. By using the following formula you can now calculate the\n RVG cache efficiency. RVG HITS/TOTAL RVG REUESTS*100=%eff.\n Routines affected - XUCS4E, XUCS4R, and XUCS4RB, XUCSTME\n \n Enhancement #4 - A new field was added to the GLOBAL REFERENCES multiple\n of file #8987.2. This field is called GLOBAL LOCATION, and it contains\nsent to the person(s) listed in the LOCAL CMP RECIPIENTS multiple of the\n the Volume Group where a particular global is located, i.e. FDA, CSA, etc.\n Routine affected - XUCS2E\n \n Enhancement #5 - It is no longer necessary to schedule separately\nthe purge of file #8987.2. The purge is now done during the up date of\nfile #8987.2. The option [XUCSTASK PURGE CM DATA] should be\n*Unscheduled*.\n Routine affected - XUCSTME\n \n Enhancement #6 - The option XUCSTASK FILE UPDATE AUTO\nsite parameter file #8987.1. The following is a sample report:\n (routine: XUCSTME) will now do the following functions:\n 1. Load the raw RTHIST data into file #8987.2\n 2. Create the MPM Morning Report and mail it to the\n LOCAL CMP RECIPIENTS.\n 3. Create the server message and mail it to the National Data Base.\n 4. Purge old data from file #8987.2.\n \n Unreported Bug Fix - When asking for a date range for reports, the\n user would always be asked for volume sets. A new variable can now be\npassed to entry point A3^XUCSUTL3 called XUCSNOA2 - when set\n \n(i.e. $D(XUCSNOA2)>0) then the volume set questions will not be asked.\nAlso, when getting the last date for data in file #8987.2, it was always\nassumed to be T-1, this has been corrected to display the true last date\nin file #8987.2.\n \n Test Sites:\n ===========\n Erie, PA\n Muskogee, OK\n Beckley, WV\nSubj: MPM Morning Report for 2/16/96 [#1508125] 17 Feb 96 02:13 23 Lines\n White River Junction, VT\n Lincoln, NE\n White-City, OR\n \n ======================================================================\n \n INSTALLATION:\n **Installation Notes: This patch can be queued to run at anytime\n *except* when the option [XUCSTASK FILE UPDATE AUTO] 'Tasked CM File\n Update' is running. Of course since some of the routines being changed\n\n
\nDescription:\nNOTE: The Response Time (RT) options are NOT part of the Resource Usage\n Monitor (RUM) package. The Response Time (RT) options do NOT\n interface with the monitoring for the RUM package. Use the RUM\n Manager Menu [KMPR RUM MANAGER MENU] to manage the RUM package.\n \n \nRoutine Summary:\n===============\n \nThe following routines are included in this patch. The second line of\n===========\neach of these routines now looks like:\n \n ;;7.3;TOOLKIT;<patchlist>;September 6, 2001\n \n Checksum\nRoutine Old New 2nd Line \n \nXURTL 7949393 5734386 **19**\nXURTL1 7623474 7983257 **19**\nXURTL2 5911591 4634037 **19**\n \nXURTL3 9463174 1339279 **19**\nXURTLC 3647421 3261936 **19**\nXURTLK 5622442 4991557 **53,19**\n \nList of preceding patches: 53\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n \nInstallation:\n============\nThis patch will correct problems reported with the Response Time (RT)\n \n>>>Users may remain on the system.\n>>>TaskMan does not need to be stopped.\n \n 1. DSM sites - Some of the routines may be mapped so you may need to\n disable mapping for the routines listed within this patch.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \noptions of the Kernel Toolkit. This patch includes all options and\n 3. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the following \n options: \n \n Verify Checksums in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \nroutines (excluding routine XURTL4) for the RT options. In addition, an\n \n 4. You do not need to inhibit users from login into the system.\n TaskMan can remain running.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the 'Install\n Package(s)' option and select the package \n \n XT*7.3*19 \n ========= \n \nupdated data dictionary with no data for the RT RAWDATA (#3.094) file has\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n 7. DSM sites: After patch has installed, rebuild your map set if\n necessary.\n \nbeen included.\n \n \nNOIS fixed:\n==========\n \nCOS-0596-40601 Fix 'Enable/Disable RT Logging' [XURTL] option to point to\n the LOG SYSTEM RT? field under the VOLUME SET multiple\n field in the KERNEL SYSTEM PARAMETERS file.\n \nBRX-0598-10869 Fix the division by zero error in the 'Graphic RT Report\n \n Print' [XURTLPG] option.\n\n
\nTest sites: CPRS (ANDERSON,CURTIS)\nroot to accept the data.\n \nMake the new call is like this: D ENVAL^XPAR($NA(^TMP($J)),206,,.XERR,1)\nNote the Closed Global Root in the first parameter and the new fifth parameter.\n \n2. Problem: Parameter entries in file 8989.5 for a individual user are not \ndeleted when the user is terminated.\n \nFix: New entry point DELUSR^XPAR3(ien) that will be called from XUSTERM.\nThis will start working when both patch XU*8*222 and XT*7.3*60 are installed.\n \n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;7.3;TOOLKIT;<patchlist>;Apr 25, 1995\n \n Checksum\nRoutine Old New 2nd Line\nXPAR 4083493 4223213 **26,60**\nXPAR3 n/a 236816 **60**\nNOIS: CHA-0701-32256, WRJ-0199-12466, UNY-0202-12683, NOIS: ISL-0499-52452\n \nList of preceding patches: 26\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n=========================================================================\nInstallation:\n \n>>>Do not allow users to log in to the system during installation.\n>>>If you accept a slight risk of jobs getting a CLOBER/EDITED error\n>>>users and TaskMan may remain running. Otherwise stop all other\n \n>>>jobs on the system.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n1. Problem: Allocation errors in ENVAR^XPAR. This call returns all parameter \n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Inhibit users from login into the system. (If you install when few\n users are on the system and the possibility of some CLOBER/NOSOURCE\ninstances.\n errors is acceptable, then users can stay on the system.)\n TaskMan can remain running.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XT*7.3*60'\n =========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// YES\n \n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n \n=========================================================================\nFix: An additional parameter was added to the call. The new parameter, if \ndefined changes the first parameter from a return array to a closed global \n\n
\nFORUM # 18670217 This message asked for the return of the routine\n \nThe CS ALPHA team asked for a change to the XTLATSET routine to change the\nsetup of the LAT device from /noqueue to /queue.\n \nUnder the new error trapping in DSM the VMS EDT editor call was getting\nerrors if the input file was null and there was no text added. This\nhas been fixed in XTEDTVXD\n \nroutine new checksum\nXTEDTVXD 1531100\nchecksum. It turned out that this was a local mod, but one that was\nXTLATSET 6400569\nXTSUMBLD 11338949\nZTPP 7877336\n \n \n========================================================================= \nInstallation:\n \n 1. These routines are usually mapped on systems that allow mapping,\n so you will need to disable mapping for the effected routines.\nusefull to all. This change has been incorporated in this patch to the\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n%ZTPP routine. The checksum value was found to have a weakness in that it\n Install Package(s)\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n 6. After installing this patch, you need to move the following\n routine from your productions account to the manager account:\n ZTPP and rename to %ZTPP\n Example: ZL ZTPP ZS %ZTPP\n 7. On MSM move the routines to the other servers. \n AXP Sites, after patch has installed, rebuild your map set.\n========================================================================= \nwouldn't catch if the order of lines changed. KIDS uses a new version\nthat will catch this kind of change. Because of this the patch will\ncalculate both the old and new checksum values and displays them in the\nfollowing way RSUM 7921662/11772536 so that both values are printed at the\ntop of the first page. It is not a crytographic hash.\n\n
\nThis patch releases a XML parser that was commissioned by the VA architects.\n^TMP($J,3) = <BOOK>\n ==========\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n=========================================================================\n\n^TMP($J,4) = <TITLE>Design Patterns</TITLE>\n^TMP($J,5) = <AUTHOR>Gamma</AUTHOR>\n^TMP($J,6) = <AUTHOR>Helm</AUTHOR>\n^TMP($J,7) = <AUTHOR>Johnson</AUTHOR>\n^TMP($J,8) = <AUTHOR>Vlissides</AUTHOR>\n^TMP($J,9) = </BOOK>\n\nInvoke the SAX interface:\nD EN^MXMLTEST($NA(^TMP($J)),"V")\nDeveloper documentation can be found on the VistA Documentation Library\n\n. . . See what happens.\n\nCheck the DOM interface:\n>S HDL=$$EN^MXMLDOM($NA(^TMP($J)))\n>W $$NAME^MXMLDOM(HDL,1) <<Write the name of the first node\nBOOK\n>S CHD=$$CHILD^MXMLDOM(HDL,1) <<Get the child of the node\n\n>W $$NAME^MXMLDOM(HDL,CHD) <<Write the child name\nunder Infrastructure in the Kernel ToolKit session.\nTITLE\nW $$TEXT^MXMLDOM(HDL,CHD,$NA(VV)) <<Get the text of the child\n>ZW VV\nVV(1)=Design Patterns\n\nList all the sibling nodes\n>S CHD=$$CHILD^MXMLDOM(HDL,1)\n\n>S SIB=CHD\nHere is the URL: http://vista.domain.ext/vdl/#App12\n\n>F S SIB=$$SIBLING^MXMLDOM(HDL,SIB) Q:SIB'>0 W !,SIB,?4,$$NAME^MXMLDOM(HDL,SIB)\n3 AUTHOR\n4 AUTHOR\n5 AUTHOR\n6 AUTHOR\n>\n\nSome notes, Defined values are case sensitive, In the first line, <?xml must \nbe in lowercase.\n\nLines can only be broken at whitespace.\nHere is a URL for more data from Microsoft and their XML notepad:\nhttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxml/html/xmlpadrun.asp\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;7.3;TOOLKIT;<patchlist>;Apr 25, 1995\n\n Checksum\nSample Use: \nRoutine Old New 2nd Line\nMXMLDOM n/a 2273946 **58**\nMXMLPRS0 n/a 7296844 **58**\nMXMLPRS1 n/a 4193331 **58**\nMXMLPRSE n/a 7947708 **58**\nMXMLTEST n/a 1892022 **58**\n\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n=========================================================================\nCreate a XML file:\nInstallation:\n\n>>>Users may remain on the system.\n>>>TaskMan does *not* need to be stopped.\n\n 1. DSM sites - These are new routines.\n\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n^TMP($J,1) = <?xml version='1.0'?>\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n^TMP($J,2) = <!DOCTYPE BOOK>\n 4. Users can remain on the system. This patch can be loaded any\n time.\n This patch can be queued and installed at any time.\n This patch can be queued for install at non-peak hours.\n TaskMan can remain running.\n\n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n\n Install Package(s) 'XT*7.3*58'\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nXT*7.3*66 Missing Patch number fix.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nPatch XT*7.3*67.\n\n
\nPATCH XT*7.3*72 Fix Parameter Option Without Column Headings.\nPlease refer to the description in Forum Module for details.\n\n
\nThis *KIDS* patch contains updates to the VAX/ALPHA PERFORMANCE MONITOR\nthe start of the next read. Response time is the average of the response\nevents for a given period of measurment. As with other VPM metrics,\nresponse time raw data will be stored for each session and a daily average\nfor the workday will be computed and stored in file 8986.6, tolerance\nlimits will be computed, data will be included in the morning summary\nreport, and events outside of your expected range will be identified.\n \n a. Bernstein Response Time Monitor options will be deleted.\n b. The file CM BERNSTEIN DATA (8986.098) will be replaced with a\nnew file to support VPM response time data.\n(VPM).\n c. Two new metrics will be added to the CM METRICS FILE:\n RTM-VPM Response Time\n RSP-Response Events/second\n \n2) This updates the VMS PERFORMANCE MONITOR to use Kernel 8's host file\nmanagment utilities in ^%ZISH. \n \n \nNew Checksums:\nXUCMNIT value = 15387419\n \nXUCMNIT2 value = 17426297\nXUCMNIT4 value = 12158370\nXUCMNT3A value = 10755761\nXUCMVPI value = 6254847\nXUCMVPM value = 4073012\nXUCMVPM1 value = 11910365 \n \n \nInstallation:\n 1. These routines may be mapped on systems that allow mapping, \nMake sure you have installed the Kernel patch, XU*8.0*35 (containing\n so you will need to disable mapping for the effected routines. \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package in this message onto your system.\n 3. Answer NO to the question:\n 'Shall I preserve what is on disk in a separate back-up message ?'\n 4. From the 'Installation Menu' of the KIDS menu, run the option\n 'Verify Checksums in Transport Global' and verify that all routines\n have the correct checksum.\n 5. This patch can be installed with users on the system.\n 6. Disable VPM using the option, ENABLE/DISABLE VPM. In MGR, enter the\nZOSV2VXD).\nRTH Utilities (D ^RTH) and stop RTHIST if it is running. Repeat this on\nall nodes.\n 7. Use the KIDS menu to complete the installation.\n 8. In the vms directory containing VPM files, delete files using the\ncommand, "DELETE XUCM*.COM.*"\n 9. Sign back in to DSM and run the option, SETUP PERFORMANCE MONITOR.\nThis will create a new set of VMS MONITOR and RTHIST drivers.\n10. Re-enable VPM.\n11. Using Taskman's ONE TIME OPTION QUEUE, run the option, XUCM\nTASK NIT. This will restart RTHIST data collections on all nodes.\n \n1) It introduces a new algorithm permitting VPM to compute and store\nsystem RESPONSE TIME. A response event is defined as the elapsed time\nbeginning at the moment a user presses the RETURN/ENTER key and ending at\n\n
\nXT*7.3*74\ncolumn widths accordingly.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires Kernel Toolkit patch XT*7.3*52.\n============================================================================ \n\nROUTINES:\nThe second line of the routine now looks like:\n ;;7.3;TOOLKIT;**[patch list]**;Apr 25, 1995\n\n\n Before After\nName Checksum Checksum Patch List\n------------------------------------------------------------------\nXPAREDT2 6094939 6370056 26,35,52,74\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n===========================================================================\n \nINSTALLATION:\nNOIS: PUG-0600-50377, PUG-0101-50486\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires Kernel Toolkit patch XT*7.3*52.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the \n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option. This loads \n the patch into a Transport Global on your system. \n4. Users may be on the system. You do not need to stop TaskMan.\n5. On the KIDS:Installation menu, use the following options to install the\n Transport Global:\nTest Sites: Puget Sound\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: XT*7.3*74 Loaded from Distribution <date/time>\n ==========\n Install Questions for XT*7.3*74\n\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nBlood Bank Team Clearance: 4/9/03\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n\n DEVICE: HOME// <You may queue it if you wish>\n ------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if necessary.\n\nThe help listing in Parameter Tools displays two columns of data, each the\nsame width. The data being displayed, though, can vary in width require-\nments. This patch will check the data it needs to display, and adjust the\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nPatch XT*7.3*69.\n\n
\nView complete information on patch XT*7.3*76 in the National Patch Module\non FORUM.\n\n
\nPlease refer to the Description in FORUM Patch Module for details.\nPatch XT*7.3*79.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XT*7.3*75.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XT*7.3*68\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XT*7.3*82.\n\n
\nPatch #86 for the Kernel Tool kit. Applies to the National CPRS Response \ntime monitor.\n\n
\n \nMSM is aware of the problem (MSM call #30546) and there is no indication\nas of yet when the problem will be fixed.\n \n- This patch also increases the maximum number of TOTAL MUMPS COMMANDS\nthat can be stored. The current maximum value is 99999999, the new value\nis 9999999999. The problem was if a "run away" job was running during the\nRTHIST run the TOTAL MUMPS COMMANDS would exceed the maximum value and all\nof the RAW STATISTICS would fail to be filed.\n \n- This patch also replaces the OS checks in %ZOSV2 with standard Kernel\n * Only MSM Sites need to install this Patch *\nchecks:\n$$OSTYPE^%ZOSV\n$$VERSION^%ZOSV\n \n- Fixes problem in NOIS LAS-0796-60351\n \n \nThanks to the following Test Sites:\n===================================\nMuskogee, Ok\n \nGrand Island, Ne\nLas Vegas, Nv\nBoston Developement Center\n \nRoutine List (CHECK^XTSUMBLD values):\n=====================================\nName Before After Patch List\nXUCS1E 5744464 5869170 15\nXUCS2E 5731962 5888536 14,15\nXUCS8E 2709944 2718707 15\n- NT/UNIX support\nXUCSCDE 3642152 4091741 15\nXUCSCDG 6508203 6570082 6,13,15\nXUCSPRG 4520058 4828057 15\nXUCSTM 6488785 6674638 3,15\nXUCSTME 13388433 13548298 14,15\nXUCSUTL3 11524190 11581338 6,12,14,15\n \n======================================================================\nINSTALLATION NOTE:\n**Installation Notes: This patch can be Queued to run at anytime\n NOIS# GRI-0396-40902\n *except* when options:\n [XUCSTASK AM RTHIST] 'AM MSM RTHIST Task Option'\n [XUCSTASK FILE UPDATE AUTO] 'Tasked CM File Update'\n [XUCSTASK PM RTHIST] 'PM MSM RTHIST Task Option'\n [XUCSTASK PURGE CM DATA] 'Auto Purge of CM Data'\n are scheduled to run or would be running.\n=======================================================================\n INSTALLATION:\n 1. The installation of this patch takes less than 2 minutes.\n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n BDC-1296-N1654\n option will load the KIDS package onto your system.\n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 4. On the KIDS menu, under the 'Installation' menu, use the following\n options:\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Backup a Transport Global\n Install Package(s)\nThe problem was a <DIVER> error in routine XUCSCDE. In investigating the\n 5. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\nproblem it was discovered that MSM's RTHIST does not sample the system\nfor CPU and DISK usage and number of jobs running at the sample time.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XT*7.3*83.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XT*7.3*70.\n\n\n
\nPatch XT*7.3*91 Fix Option [XU FIRST LINE PRINT].\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease see the patch description on Forum, in the National Patch Module.\n\n
\nKernel Toolkit patch XT*7.3*94 New CheckSum. Please refer\nto the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*90\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XT*7.3*89 XML parser fix.\n\n
\nKernel Toolkit patch XT*7.3.*98 VistA Patch Monitor. Please refer to\nthe Description in Forum Patch Module for details.\n\n
\nThis patch fixes most of the problems that have been raised with XINDEX.\n \n ZL ZTPP ZS %ZTPP\n\n =========================================================================\n\n \nFORUM messages:\n%INDEX & Undetected Error [#11969353]\nXINDEX mistakes [#17602138]\nUndefined in XINDEX [#19627074]\nXINDEX and $TRANSLATE [#19927226]\nJust in case [#20070553]\nUNDEF IN XINDEX [#20406560]\nFixed problem with not checking for partial file sends. [#22935874]\nThe use of root indirection still causes some problems:\nFixed problem with not checking call's to missing tags in \nroutines not XINDEXed. [#24687607]\n \n \nXTSUMBLD: \nHas been updated to include the PRE, POST, and ENV check routines\nfrom a BUILD when using the CHECK entry point. [NOIS ISB-0896-31782]\nFixed a bug if a BUILD didn't have a package file link. \nFixed a bug if a routine in the BUILD doesn't exist in the UCI.\n \n(i.e. $O(@ABC(XYZ)@(123))\nXTVNUM:\nWill see that each routine from a build has the patch number\non the second line.\n \n%ZTPP:\nFixes problems with not printing lines like\nlabel<linestart><cr>. [NOIS HOU-0297-71103]\n \nBUILT^XTRUTL:\nTakes the routines in a KIDS BUILD and generates the following \n \nlist.\n\n Checksum\nRoutine Old New 2nd Line\nXINDEX 7227772 8229005 **20**\nXINDX1 6096231 6091882 **20**\nXINDX10 12585180 13440865 **20**\nXINDX11 7471101 7648100 **20**\nXINDX2 5054188 5457656 **20**\nXINDX3 3897455 3946423 **20**\nNOIS:\nXINDX4 4711071 5192692 **20**\nXINDX5 6259999 7001485 **20**\nXINDX51 9529173 9238490 **20**\nXINDX52 2298647 2275540 **20**\nXINDX53 4122188 4208616 **20**\nXINDX6 10179476 10238332 **20**\nXINDX7 7575886 7680200 **20**\nXINDX8 6101428 6232391 **20**\nXINDX9 4045898 4248028 **20**\nXTRUTL 3298585 3298825 **20**\nISB-0494-30070 \nXTRUTL1 728450 **20**\nXTRUTL2 361405 **20**\nXTSUMBLD 11338949 12015543 **11,20**\nXTVNUM 7898211 9944358 **20**\nZTP1 11606940 8017158 **20**\nZTPP 7869052 **4,11,20**\n========================================================================= \nInstallation:\n 1. DSM sites- These routines aren't usually mapped \n so you will probably not have to disable mapping.\nBRX-1296-10244 \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\nISA-0497-11864 Fix entries in the ROUTINE file that have a blank type if\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. \n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XU*8.0*??'\n =========\n XINDEX does a save into the ROUTINE file.\n\n 6. DSM/MSM Sites - Move the following two routines to the MGR account.\n ZTP1\n ZTPP\n In the MGR account rename the routines.\n ZL ZTP1 ZS %ZTP1\n ZL ZTPP ZS %ZTPP\n\n 7. OpenM Sites - Just rename the routines.\n ZL ZTP1 ZS %ZTP1\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*92 Fix TAPE~XTRCMP for Cache.\n\n
\nKernel Toolkit patch XT*7.3*100 VistA Patch Monitor. Please \nrefer to the Description in Forum Patch Module for details.\n\n
\nRemove RTM.\n\n
\nPatch #103 for the Kernel Tool kit and applies to the National CPRS\nResponse time monitor.\n \nSee patch XT*7.3*103 in the National Patch Module on FORUM for complete\ninformation on this patch.\n\n
\nToolkit patch XT*7.3*104 fixes 'Rerun the Nightly Patch Monitor' option.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3* 105 %ZTP1 to print 3rd line.\n\n
\nSee patch XT*7.3*80 in the National Patch Module for complete\ninformation on this patch.\n\n
\n\n\n\n
\nToolkit patch XT*7.3*106; PATCH MONITOR DATE INSTALL COMPUTED FIELD.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*116 Update XML parser to handle long Attributes.\n\n
\nVPM-MISC FIXES; SEE PATCH MODULE FOR DETAILS\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*110 XINDEX Update for new SAC.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*109 XPARLIST errors out\n\n
\n \nSee patch XT*7.3*114 in the National Patch Module for complete \ninformation on this patch.\n\n
\nFor a full description, please see the National Patch Module for complete\ninstructions on this patch, XT*7.3*108.\n\n
\nIDENTITY HUB CHANGES FOR DUPLICATE RECORD MERGE\n \nChanges to the Duplicate Record Merge routines to support the new PSIM \nProbabilistic Search.\n \nPlease see FORUM patch module for details.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n
\nE-MAIL REGARDING FILE 15 ADDS NOT SHOWING PSUEDO-SSN \nRefer to patch XT*7.3*124 in the FORUM Patch Module for a\ncomplete description.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*123 HTTP Client.\n\n
\nCHECK MPI DO NOT LINK FILE BEFORE ADDING TO FILE #15\nRefer to patch XT*7.3*125 in the National Patch Module on FORUM for a \ncomplete description.\n\n
\nAssociated patches: DI*21*41\n \nXDR PRELIMINARY SCAN LIST\nXDR PRINT LIST\nXDR PURGE\nXDR PURGE2\nXDR RESTART MERGE PROCESS\nXDR SCAN POSSIBLE DUPLICATES\nXDR SEARCH ALL\nXDR STOP MERGE PROCESS\nXDR TALLY STATUS FIELDS\nXDR UTILITIES MENU\nSubject: XT*7.3*23 Duplicate Record Merge: Patient Merge\nXDR VALID CHECK\nXDR VERIFY ALL\nXDR VIEW DUPLICATE RECORD\n \nThe menu option Duplicate Resolution System [XDR MAIN MENU] will appear as\na sub-menu on the Application Utilities menu [XTMENU].\nThe menu option Operations [XDR OPERATIONS MENU] will appear as a sub-menu\non the [XDR MAIN MENU].\nThe menu option Utilities [XDR UTILITIES MENU] will appear as a sub-menu\non the [XDR MAIN MENU].\n \nThe menu option Manager Utilities [XDR MANAGER UTILITIES] will appear as a\nsub-menu on the [XDR MAIN MENU].\n \nPost-init information:\n================\nThis patch does not contain a post-init routine.\n \nNOIS Messages Covered:\n====================\nThere are three NOIS calls, all with a Referred, Awaiting Patch status.\nCategory:\nThese all have to do with sites wanting to merge patient records. The\nrelease of this patch will serve to close these calls. The NOIS calls\nare:\n CAS-0797-12438, duplicate pts and pt demo missing\n SPO-0298-51628, HOW TO MERGE DUPLICATE ENTRIES\n NYN-0398-11634, Site needs help with Duplicate Resolution\n \nPrint Templates\n============\nXDR BRIEF LIST FILE #15 \n - Enhancement (Mandatory)\nXDR MERGED LIST FILE #15\n \nSort Templates\n============\nXDR MERGED LIST FILE #15\nXDR NOT READY TO MERGE LIST FILE #15\nXDR POTENTIAL DUPLICATE LIST FILE #15\nXDR READY TO MERGE LIST FILE #15\n \nForms\n \n=====\nXDR RESFILE FORM FILE #15.1\n \nRoutine Summary:\n===============\n \nThe following is a list of routines included in this patch.\n \nThe second line of each of these routines will look like:\n <tab>;;7.3;;TOOLKIT;**[patch list]**; Apr 25, 1995\nDescription:\n \n CHECK^XTSUMBLD results\nRoutine name Before Patch After Patch Patch List\n=========== ========== ========= ========\nXDR2NULL N/A 213286 23\nXDRCNT 7651887 7742313 23\nXDRDADD 8133407 8530927 23\nXDRDCOMP 4431965 4873221 23\nXDRDDATA N/A 893537 23\nXDRDEDT N/A 9827533 23\n=========\nXDRDLIST 7786460 9241915 23\nXDRDMAIN 5700890 6747860 23\nXDRDPICK N/A 17800586 23\nXDRDPRE1 N/A 5745643 23\nXDRDPREL N/A 5988721 23\nXDRDPRG2 N/A 1096260 23\nXDRDPRGE 3959904 3975142 23\nXDRDQUE 9275556 9693871 23\nXDRDSHOW N/A 7608889 23\nXDRDSTAT 2676366 5551016 23\nPatient Merge provides an automated method to eliminate duplicate patient\nXDRDUP 3547600 4515332 23\nXDRDVAL N/A 8556766 23\nXDRDVAL1 N/A 12083072 23\nXDRDVAL2 N/A 12453467 23\nXDREMSG 4302480 4339222 23\nXDRMADD 6382715 12378004 23\nXDRMAIN 7563507 8572792 23\nXDRMAINI 14611797 15245931 23\nXDRMERG N/A 11028391 23\nXDRMERG0 N/A 11419853 23\nrecords within the VISTA database. It is an operational implementation of\nXDRMERG1 N/A 5837142 23\nXDRMERG2 N/A 15382760 23\nXDRMERGA N/A 17080288 23\nXDRMERGB N/A 16160853 23\nXDRMVFY 1318075 1157832 23\nXDRPREL1 N/A 766751 23\nXDRPTCAN N/A 7251504 23\nXDRPTCLN N/A 1819429 23\nXDRPTDOB N/A 1857839 23\nXDRPTDOD N/A 498220 23\n DI*21*42 \nthe Duplicate Resolution Utilities released to the field with Toolkit\nXDRPTLSD N/A 803980 23\nXDRPTMMN N/A 1478218 23\nXDRPTN N/A 6440837 23\nXDRPTSSN N/A 3615316 23\nXDRPTSX N/A 573526 23\nXDRRMRG0 N/A 4444660 23\nXDRRMRG1 N/A 19616376 23\nXDRRMRG2 N/A 5315420 23\nXDRUTL N/A 927605 23\nXDRVCHEK N/A 4108217 23\nversion 7.2. The overall process consists of the search for potential\n \n \nInstallation Instructions:\n==================\n1. Recommend the patch installer review the Installation Guide\ndocumentation for detailed installation and implementation information.\n \n2. This patch can be loaded with users on the system. Installation will\ntake less than 1 minute.\n \nduplicate record pairs, review and verification of those pairs, and the\n3. Review your mapped set. If any of the routines listed in the ROUTINE\nSUMMARY section are mapped, they should be removed from the mapped set at\nthis time.\n \n4. Impacts of files:\n a. The size of File 15 is dependent upon the number of potential\nduplicates found and is thus also dependent upon the size of the Patient\nFile. It may be purged using the application options, however note that\ninformation regarding those pairs already merged will not be purged.\n \nmerge process. The search and identification of potential duplicate\n b. The size of File 15.1 is minimal. This file contains the\nworking components of Duplicate Resolution as they pertain to a primary\nfile. It will expand as additional primary files are added.\n \n c. The size of File 15.2 is minimal. It may be purged using the\napplication options.\n \n d. The size of File 15.3 is minimal. The number of entries is\ndependent upon the number of record pairs merged.\n \nrecords performs comparisons on key fields in the PATIENT file. (This is\n e. The size of File 15.4 is dependent upon the number of record\npairs merged and their associated data. Note that not all associated data\nis retained, but rather pointer values. This is an independent global\nwith the intent that it can be saved off to a static environment for\narchive purposes.\n \n5. This patch contains 46 routines. The following routines are necessary\nfor the operation of Patient Merge, but are not included with this patch\nas they were previously released as part of Toolkit:\n XDRDADJ XDRDFPD XDRDPDTI XDRDSCOR\na long process and can exceed 100 hours.) When evaluated as a potential\n XDRMPACK XDRMRG XDRMRG1 XDRMSG\n XDRU1\n \n6. From the Kernel Installation and Distribution System Menu, select the\nInstallation menu.\n \n7. From this menu, you may elect to use the following options (when\nprompted for the INSTALL NAME, enter XT*7.3*23):\n \n a. Backup a Transport Global - this option will create a backup\nduplicate, the pair is entered into file 15 (Duplicate Record File) and is\nmessage of any routines exported with the patch. It will NOT backup any\nof the other changes.\n \n b. Compare Transport Global to Current System - this option will\nallow you to view all changes that will be made when the patch is\ninstalled. It compares all components of the patch (routines and\noptions).\n \n c. Verify Checksums in Transport Global - this option will allow\nyou to ensure the integrity of the routines that are in the transport\navailable for review and verification. The review allows for two levels\nglobal.\n \n8. Use the Install Package(s) option and select the package XT*7.3*23.\n \n9. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\nProtocols? YES//" respond "NO".\n \n10. If any routines were unmapped as a part of step 3, they should be\nreturned to the mapped set once the installation has run to completion.\nof review; a primary reviewer - focussing on patient demographics - and an\nancillary reviewer - focussing on ancillary service data. Once verified,\n PSJ*4.5*43\nthe merge process can be initiated. (This is a long process and can\nexceed 15 hours.)\n \nSoftware and a complete set of documentation (Release Notes, Installation\nGuide, User Manual, and Technical Manual) may be obtained using FTP from\nthe appropriate Customer Service directory:\n \n IRM FIELD OFFICE FTP ADDRESS DIRECTORY\n =============================================================\n ALBANY 152.127.1.5 anonymous.software\n DG*5.3*156\n HINES 152.129.1.110 anonymous.software\n SALT LAKE 152.131.2.1 anonymous.software\n \nRelease Notes file name: xt_73_p23_rn.pdf\nInstallation Guide file name: xt_73_p23_ig.pdf\nUser Manual file name: xt_73_p23_um.pdf\nTechnical Manual file name: xt_73_p23_tm.pdf\nSoftware file name: XT73_23.KID\n \nFile Information:\n IMR*2.1*2\n============\nThis patch contains three new files and changes to the existing files.\n \nDUPLICATE RECORD ^VA(15,\nThis file contains information about duplicate records in any file defined\nin the two variable pointer fields; RECORD1 and RECORD2 (.01 and .02).\nThe status of an entry in this file may be 'potential duplicate,\nunverified', 'verified, not a duplicate', or 'verified duplicate'.\n \nDUPLICATE RESOLUTION ^VA(15.1,\n IB*2*94\nThis file is used to handle duplicate checking and merging of files that\nhave entries in the Duplicate Record File. It is meant to provide the\noverall control information that would be used to first identify\nduplicates within a file, e.g. Patient File, and then to merge the\nentries.\n \nXDR MERGE PROCESS ^VA(15.2, New file.\nWhen a merge process is set up, all its information is stored in this\nfile. Once a merge process has completed, that entry may be purged using\nthe Purge Merge Process File option in the managers menu.\n IB*2*97\n \nXDR REPOINTED ENTRY ^VA(15.3, New file.\nThis file is used to record the entry number of the FROM record that is\nmerged into the TO record. This can be used for FileMan to determine\nwhich entries were merged, so the IEN of the FROM record will not be\nreused.\n \nMERGE IMAGES ^XDRM New file.\nFile 15.4 stores an image of the pairs of entries in files that were\nmerged immediately prior to the actual merge. In addition, there is also\n LR*5.2*205\na record of the locations of pointer values that were changed during the\nmerge process.\n \nOption Information:\n===============\nThis patch contains 27 options:\nXDR ADD VERIFIED DUPS\nXDR ANCILLARY REVIEW\nXDR APPROVE FOR MERGE\nXDR CHECK MERGE PROCESS STATUS\nAssociated package: NDBI v 1.0\nXDR CHECK PAIR\nXDR DISPLAY SEARCH STATUS\nXDR EDIT DUP RECORD STATUS\nXDR EDIT DUP RESOLUTION FILE\nXDR FIND POTENTIAL DUPLICATES\nXDR MAIN MENU (Locked with XDR key)\nXDR MANAGER UTILITIES (Locked with XDRMGR key)\nXDR MERGE READY DUPLICATES\nXDR OPERATIONS MENU\nXDR PRELIMINARY SCAN\n\n
\nCLEAN UP OF THE DUPLICATE RECORD (#15) FILE\nRefer to patch XT*7.3*129 in the FORUM Patch Module for a complete\ndescription.\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nToolkit patch XT*7.3*130; Fix: 'Patch Statistics by Compliance Date'.\nPlease refer to the Description in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXT*7.3*122 Kermit fix.\n\n\n
\nToolkit patch XT*7.3*127; Fix: 'Patches Due in the Next Seven Days', and\n'Last Routine Change Date Recorded' options. Please refer to the\nDescription in Forum Patch Module for details.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\n\n
\nPlease see the patch description on FORUM, in the National\n Patch Module.\n\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nfrom Platinum account. includes patches\n\n
\nThe KERNEL TOOLKIT can only be installed on a system already running\nVA KERNEL V7.1.\n\n
\nPatch routine to update file 2100.1 entries from TRANSMITTED to ACCEPTED\nthat have a date entered before March 1st, 1996.\n\n
\nThis patch is being issued to extract data from the Vendor file (#440) at\neach facility and forward that data to Dunn & Bradstreet to obtain Dun and\nBradstreet Numbers (#18.3) for each vendor\n\n
\nPurchase Order Print/Display Fixes\n\n
\nCorrect 3 fields in file 421 and file 410 that use ^DIC in their input\ntransform. Made changes to find out if user selected something before\nworking with returned data (it might not be available).\n\n
\nCorrection for display of PC orders to be selected for reconciliation.\n\n
\n1358 PRINT AND DAILY ACTIVITY ISSUES\n\n
\nCertified Invoice payment fixes\n\n
\nGIP PHYSICAL COUNT FORM\n\n
\nThis build contains all the modified components for this patch.\n\n
\nPURCHASE CARD DELINQUENT REPORTS\n\n
\nGeneral Post Fund/CP Approval Queueing & Printing Fixes\n\n
\nPRINT/DISPLAY FIXES ON REQUISITIONS/PO'S\n\n
\nThis patch will prevent placing into file 442 '-2' as the 2237 internal\nrecord number.\n\n
\nGIP INVENTORY POINT FIXES\n\n
\nBuild for Disputed Purchase Card Orders.\n\n
\nGIP Printing Ticket Fixes\n\n
\nAs part of the VISN/Integration Enhancement initiative, this patch adds\nthe questions asked in option Add/Edit Supply Personnel [PRCH EMPLOYEE\nEDIT].\nfax numbers and e-mail addresses to IFCAP documents, due to their\nincreasing use in communications between Purchasing Agents and vendors.\nSpecifically, this patch adds the Purchasing Agent's fax and the vendor's\nfax to the Purchase Order (Form 2138) and Amendment Form (SF-30). In\naddition, it adds the Purchasing Agent's e-mail address to the Request for\nQuotation (SF-18), Purchase Order (Form 2138), and Amendment Form (SF-30).\nTo support these enhancements, this patch adds the FAX NUMBER field\n(#.136) and EMAIL ADDRESS field (#.151) of the NEW PERSON file (#200) to\n\n
\nBuild for correction of service name in purchase card options, and clean\nup of the "AB" cross references in file #442.\n\n
\nThis patch contains the Purchase Card Registration option, the\nPRCH PURCHASE CARD input template, the PRCHUSER routine, and\nthe data dictionary for file 440.5\n\n
\nThis will add 2 fields to the edit of a 441 item, within the VENDOR\nmultiple.\n \nThis will also allow the template to continue after entering 2237s into\nthe P.O. rather than going to the end.\n\n
\nHOME OXYGEN MODULE/IFCAP API\n\n
\nThis patch corrects an <ENDOFFILE> error that may occur during Carry\nForward processing.\n\n
\nThis is a build for patch PRC*5*227\n\n
\nSub-Control Point Y2K Fix Allows "00" in Fiscal Year Field\n\n
\nUpdate patch 150 changes to speed up response time, eliminate unnecessary\nprompts and restore old functionality.\n\n
\nExamine integrity of file 442.3\n\n
\nUndelivered Orders Reports\n\n
\nThis patch resolves NOIS ISW-0999-20400 FMS EXCEPTION RPT NOT Y2K\nand resolves NOIS ISW-1299-22783 TRANS DATE ON FMS TRANSACTION\nNOTIFICATION NOT Y2K.\n\n
\nSecond line formatting corrections and the deletion of PRCUCOM\n\n
\nThe logical limit to the partial numbering system is 974 partials. Once\nthis limit is exceeded (i.e. partial 975 and beyond) the PV document that\nis created during invoice payment processing is incorrect. A duplication\nof PV numbers results and can cause errors to occur. Currently, there are\nno checks to see if the partial number has reached or exceeded its limit.\n\n
\n \n \n1 Create AR transactions.\n2 Allow prior year SO transactions to be sent as AR, when desired.\n3 Prohibit the deletion of PO Date in file 442 when the original 1358 SO\nis rebuilt.\n\n
\nBuild for patch PRC*5*201.\n\n
\nSpecial remarks on PC orders\n\n
\no Allows multiple primary inventory points to share the same FCP.\no Permits conversion of existing secondaries into primaries.\no Users are now required to select Inventory Points manually in some\n cases. When there is only one possible choice, the system will select it\n automatically. In cases where the FCP is serving more than one Inventory\n Point, users will be prompted unless the system can determine the\n Inventory Point on the basis of context.\n\n
\nBuild for the first patch of a series for correction of ^UTILITY use by\nIFCAP.\n\n
\nUndef PRCSA2. From 1358 Print menu.\n\n
\nPICKING TICKET FIXES\n\n
\nAudit Transaction List Y2K\n\n
\nWhile using the Generate FMS Budget Documents option\nare passed to the routine %DT. The "M" parameter specifies\nthat only the month and year are allowed for input. Only\nFileMan 22 uses this parameter. It was this version that\nintroduced this parameter. Other FileMan versions ignore\nthe "M" which is believed to be a typo in the date utility\nroutine PRC0B2.\n[PRCB GENERATE CODE SHEETS], the user gets prompted\nfor an FMS Transaction Date. The default date consists\nof the month and the year, but the user gets the message\n"Enter precise date!" This problem occurs with any\nsite that has FileMan 22. \n\nThe date utility routine PRC0B2 has been modified. It\nsets the %DT variable to "FMPT". These format parameters\n\n
\nSuppress the printing of an "@" on the Running Balance when a manual\nadjustment has been entered against a Purchase Card Order.\n\n
\nBuild for PRC*5*245, SAC UTILITY CORRECTIONS - ORDERS AND REQUISITIONS.\n\n
\nThis will allow vendors to be found even if they were entered in mixed\ncase.\n\n
\nBuild for Complete Order Received in Reconciliation.\n\n
\nThis patch corrects a problem after PRC*5*197 with the Change Existing\nTransaction Number option.\n\n
\n1358 BALANCE DISPLAY; ERROR DURING CREATE NEW BILL ACTIVITY\n\n
\n \nFIX SAC LOCK VIOLATIONS IN MULTIPLE TRANSACTIONS, SINGLE TRANSFER,\nAND CARRY FORWARD OPTIONS\n\n
\nFMS EOY EMERGENCY CHANGES\n \nFunctionality Provided\n----------------------\n \n1. To implement an OMB decision, only revolving funds are automatically\ncarried forward.\n \n2. To sychronize IFCAP with Austin, the IFCAP PARAMETERS Cross-reference\nfor the ADMIN. ACTIVITY SITE PARAMETER file (#411) is created to contain\nnon-site specific data. The cross-reference is NOT record oriented and\n \nwill initially have only one entry:\n \n ^PRC(411,"A IFCAP-Wide Parameters","SO 2 AR Date") = date\n \nbeing that date on which Austin will convert "this year's unpaid POs" to\n"Last Year's", i.e. that date on which IFCAP must convert to "SO"s and\n"AR"s -- SO TO AR DATE (#2).\n \nThe option Enter the "SO" to "AR" Shift Date for Austin/IFCAP\nSychronization [PRCB SO TO AR] is provided to enter that date.\nThis patch is being issued to sychronize IFCAP with the End-of-the-Year\nprocessing at Austin and to implement the OMB decision to prohibit Carry \nForward of non-revolving (multi-year) funds.\n \nThis patch must be installed prior to the Sept 30, 1996 to ensure that\npayments between 10/1 and 10/11 are able to be processed in a timely and\nuninterrupted manner.\n\n
\nBuild for PRC*5*244, SAC UTILITY CORRECTIONS- AMENDMENTS.\n\n
\nBuild for ADMINISTRATIVE CERTIFICATIONS ON PURCHASE ORDERS.\n\n
\nBuild for PRC*5*251, SAC LOCK CORRECTIONS - BUILD LISTS\n\n
\nThis patch corrects SAC locking violations.\n\n
\nCarry Forward 3rd-4th Qtr Running Balance - Canceled Obligations\n\n
\nThis patch address the following NOIS:\n\nThis patch also addresses a SAC LOCK violation in routine\nPRCFARR.\n\n1. PHI-1099-21187 \n2. DAY-1099-42326\n\nWhile running the Electronic Receiving Batch Statistics\nReport, a null subscript error occurs. This is because\nthe ELEC RECEIVING REPORT BATCH file (442.9) has no data\nin the Purchase Order Number field (#1).\n\n
\nAdded the "**" in line 2 for routine PRCHEI.\n \nModified routine PRCHEC. This routine gets call from "New Requisition"\nMenu Option.\n\n
\nThis patch cleans up documents in file 442 that are left over after an\nArchive/Purge is run. These documents include Accounts Receivable\ndocuments and Purchase Orders without a P.O. Date. Two routines and a\nmenu option are installed.\n\n
\nProblems with amendment obligation.\n\n
\nUpdate EDI/RFQ REPORTS option. This update will allow a user to select\nanswering NO to the select all question.\n\nDuring testing, one of the sites found an error that is not related to\nthis patch. It is a separate issue. This patch also resolves NOIS\nDEN-0999-50592 (EDI/RFQ Reports Option Errors Out).\none sender (someone who entered a PHA, RFQ or TXT transaction into the\nlocal IFCAP system) from among all the senders in file 443.75. All\nreports and the initial screen will display only those records entered by\nthe selected sender.\n \nIf the user is a SUPPLY MANAGER then the user can view all senders at one\ntime. All reports, as well as the initial screen(s), will display without\nany sender sorting. The SUPPLY MANAGER user can select one sender by\n\n
\nFirst build for patch 255. Duplicate 2237 on File #410.\n\n
\nThis patch cleans up documents in file 410 that are left over after an\nArchive/Purge is run. It purges, based on a date the user enters, items\nin file 410 that have no established connection or relationship to an\nentry in file 442. Two routines and a menu option are installed.\n\n
\nBuild for correction of the Delinquent Approvals Report, of the Purchase\nCard module.\n\n
\nThis patch corrects an <UNDEFINED> error that occurs when printing a\nPurchase Order form and the Purchasing Agent/Contracting Officer on the PO\ndoes not exist in the New Person file (#200).\n\n
\nCost Center not stuffed if user times out.\n\n
\nUpdate input transforms, .01 field of files #442 & 443.6.\n\n
\nVendor File DD Cleanup.\n\n
\nThis KIDS distribution will allow FISCAL to review any VRQs.\n\n
\nPurchase Card and Delivery Order functionality.\n\n
\nAppropriation Summary Totals Report fix.\n\n
\nFix UNDEF at READ+2^PRCHMSE.\n\n
\nA fixes to couple of nois messages and an E3R regarding print/display\nof a P.O./R.R. scrolls off the screen, and Unobligated Amendment\nprints to a Wrong Printer.\nAnd the last one also in Amendments Module regarding a '?' entered\nin response to AUTHORITY prompt which displayed a couple of\nconflicting help messages. \n\n
\nThis is the new Request for Quotation module of IFCAP 5.0.\n\n
\nMinor bugs in single routines.\n\n
\nVarious fixes to Control Point module.\n\n
\n \nThis Build contains the KIDS Installation for PRC*5*85.\n\n
\nThis patch will correct routine PRCOPHA1 to include '1' as the sixth\nparameter in the call to TRANSMIT^PRCPSMCS. When this parameter is\nincluded, during the EDI Retransmit option the version number in the PHA\ntransaction's ISM segment will be '001', the correct version, rather than\n'040', the default but here incorrect version.\n\n
\nPURCHASE CARD CHANGES\n\n
\nPatch PRC*5*55 for carry forward enhancement.\n\n
\n820 PROCESSING FIX\n\n
\nThis patch corrects the logic for calculating the Current Fiscal Year\nduring the building of the PV transaction for transmission to FMS.\n \nThis patch also backs out the changes to routine PRCB1E1 which were\nintroduced with patch PRC*5*96 affecting Carry Forward.\n\n
\nFor Kernel Sort/ Patch 97.\n\n
\nAccrual (Monthly) Option Enhancement.\n\n
\nPROBLEMS COPYING TRANSACTIONS\n\n
\nChanges to data definition in different files.\nThe help frames have been added to a Vendor Type field(#44)\nin Vendor File(#440).\n\n
\nPURCHASE CARD RELATED PATCH.\n\n
\nFurther changes for purchase card module.\n\n
\nThis package contains the routines and files necessary to\n support the functions of archive and purge within the IFCAP package \n\n
\nENTER FCP ADJUSTMENT AND CARRY FORWARD ENHANCEMENT\n\n
\nCreation of PRCS REINSTATE option.\nNOIS fixes.\n\n
\n \nEnhancement to create purchase card order from temporary request.\n\n
\nVarious purchase card fixes.\n\n
\nThis patch is being issued to distribute direct delivery functionality\nfor purchase cards, and to create the IMPAC Account Information report.\n\n
\nThis KIDS install will remove all references to files 3-6-16-20 from IFCAP\n5.0.\n\n
\nThis will update the IFCAP ISMS, EDI and FMS servers to present more and\nbetter error messages to the user. Since these servers run in the\nbackground the error messages will be sent to ISM or FMS mail group. If\nthe mail group isn't available then the message will go to POSTMASTER.\n\n
\n \nIFCAP Patch PRC*5*106\n\n
\nFiscal Budget Related Patch\n\n
\nThis patch will increase the number of amendments that can be entered to a\nPurchase Order from 99 to 999, a ten-fold increase in the number of\namendments able to be entered.\n\n
\nThis patch will check your file 442.3 and report its status to FORUM.\n\n
\nPROSTHETIC/IFCAP AMENDMENT AND RECONCILIATION ENHANCEMENT\n\n
\nNew Janus Barcode Functionality\n\n\n
\nThis patch will allow users to Re-transmit the IRS PRE-OFFSET\ncode sheet Batch.\n\n
\nIFCAP Patch PRC*5*104.\n\n
\nThis patch deals with Federal Procurement Data System(FPDS) reporting\nrequirements data and how IFCAP collates procurement data in the Summary\nof Actions of $25,000 or less.\nTwo nois(s) ALT-0792-20001 and CMO-0797-41042 are also addressed in this\npatch.\n\n
\nALL ET-RECORDS WITH ACTION CODE 'E'\n\n
\nGENERAL LEDGER CHANGES\n\n
\nTwo issues are addressed.\n \n1. The Supply Fund Requests and Orders were missing a value in the BOC\n field.\n \n2. The discount was miscalculated when users entered a '$' sign and a\n comma in field 'Percent/Dollar Amount'.\n\n
\nSlave device handling fixes.\n\n
\n2237 FIXES - APPROVAL LOOP & REQUESTOR NAME CHANGES\n\n
\nNEW OPTIONS FOR UNREG. CARD CHARGES.\n\n
\nCorrections to patch PRC*5*66.\n\n
\nWhen ceiling transactions are entered via Create Multiple Transactions,\nthese transactions do not appear on the Transaction reports. At one time,\nthe transactions generated a non-standard appropriation number and so\nappeared under a second heading (ergo the complaint that the summary gives\n2 totals). However, the code to set up the appropriation number had been\ncommented out.\n \nAlso, there was a request to display the transaction numbers generated, so\nthis functionality was added. \n\n
\n \nVARIOUS PURCHASE CARD REPORT ENHANCEMENTS\n\n
\nThis patch fixes numerous bugs related to delivery schedule.\n\n
\nPREVENT TERMINATED USERS IN FCP\n\n
\nREPORT SPOOLER PROBLEMS\n\n
\nFCP REPORT FIXES\n\n
\nNEW OPTS: DETAIL ACCRUAL, CHARGE COUNT, AUDIT\n\n
\nThis change will correct 3 NOIS entries.\n42 didn't display. After the change all the cards display.\n HAC-1197-50154\n COS-1297-40227\n NOP-0397-11470\n \nThis change will now display all cards a user holds. If a user has 67\ncards the display of the cards, when a ? was entered, displayed cards 1-20\non the first screen, cards 22-40 on the second screen, cards 43-60 on the\nthird screen and 61-67 on the fourth screen. Note that cards 21, 41 and\n\n
\nThis patch fixes NOIS ISH-0495-40396 and SDH-1196-N0212.\n\n
\n1358 PROCESSING\n\n
\nY2K Renovations\n\n
\no Removes hard sets of COST CENTER 600000 into control point activity\no Inserts time delay into an IRL download routine so that downloads to\n Janus portable bar code readers will be more reliable. Also displays\n download and upload times, preserves data that was uploaded\n unsuccessfully (for diagnostic purposes), and corrects documentation\n errors.\n documents involving the Supply Fund.\no Clarifies error messages presented to users who do not have proper\n access for autogeneration of repetitive item lists.\no Causes inventory adjustments to appear correctly on Stock Status\n Reports.\no Insures that local variables PRC("SITE") and PRC("CP") are set p[roperly\n for repetitive item lists, so that budget fiscal years and other\n accounting data will be correct.\n\n\nBLOCK TERMINATED USERS FROM FCP\n\n
\nThis patch will fix a couple of E3Rs and NOISs.\n\n
\nCancelled Supply P.O. does not return funds.\nUndefined string.\n\n
\nUndef errors in Transaction Report\n\n
\nPayment/Invoice Tracking fixes.\n\n
\nIFCAP PATCH PRC*5*166\n\n
\nIFCAP PATCH PRC*5.0*136\n\n
\nResolution of Purchase Card problems and multiple access to Amendments.\n\n
\nThis patch will eliminate different parts of a multipart MailMan message\nfrom being placed into different records in file 423.6.\n\n
\nMISSING BBFY AND PC RR AT FICSCAL OFFICE\n\n
\nThis patch addresses several E3R and NOIS. Issues addressed include 1) \nillegal number errors when contract number or ACC contains embedded 'E'\nand system was evaluating them as exponential notation numbers.\nImporting Purchase Card information into BI segment of PHA and on hard\ncopy Purchase Orders for use in EDI Orders where Method of Processing is\nPurchase Card. Purchase Card Number and Expiration Date are to be\nencrypted while Purchase Card Holder is unencrypted in the PHA. Only\nnon-sensitive information Purchase Card Holder and Purchase Card Name,\nboth unencrypted, are to be included on the hard copy PO. 2) Adding a\nmechanism for suppressing the EDI order to EDI registered vendors. 3)\nActivating the printing of Imprest Fund orders in supply. 4) Fixes for\n\n
\nIFCAP Patch PRC*5.0*140\n\n
\nTEMPORARY EMPLOYEES AS FCP USERS\n\n
\nGeneral Post Fund Fixes\n\n
\nIn Amendments module this patch will fix the logic to display the original\ndollar amount correctly and print discount information of amendments that\nare obligated in Fiscal.\n \nIt fixes a couple of NOIS as listed. \n \n 1. LOU-0896-42124\n 2. GAI-0296-30038\n\n
\nThis KIDS build deals with various Purchase Card Reports which may be\nfound in the following menus: Approving Official Menu, Purchase Card\nCoordinator's Menu, and Purchase Card Reports Menu.\n\n
\nBlock FCP# edits, change rollover date, and fix typos\n\n
\nERROR WHEN COPYING A TEMPORARY TRANSACTION\n\n
\nThis patch will upgrade the ARCHIVE and PURGE process.\n\n
\nFixes to several un-related nois messages.\n\n
\nThis patch will set up an Extrinsic Function to allow an AR user to select\nan IFCAP vendor.\nIf the vendor has FMS VENDOR CODE present, nothing else is done to it.\nIf the vendor is missing the FMS VENDOR CODE but has all\nthe other required fields necessary to create a VRQ, one will be created.\nIf the vendor is missing the FMS VENDOR CODE and other required fields, it\nwill be edited to fill in the missing fields needed to be vendorized.\n\n
\no Prevents queueing a task to a virtual terminal.\no Checks for and ignores blank lines when user is attempting to upload\n data from a portable bar code reader to the central processor. This is a\n common problem at Open-M sites.\no Remove inappropriate post-conditional from WRITE command in ^PRCTLAB.\n\n
\nAUTO SET BBFY IN PURCHASE CARD REQUEST\n\n
\nItem Master File updates and related E3R's.\n \nE3Rs: 2349 - Make Package Multiple Field on Item Master File mandatory.\n (Cancelled because covered by E3R 5673.)\n 5673 - Make Package Multiple & Unit Conversion Factor mandatory\n before allowing completion of PO.\n 2558 - Make Drug Type Code pull fm Item Master File & mandatory.\n 3344 - Control Point Item History Does Not Go Back Far Enough.\n 10365- Procurement Item History Does Not Go Back Far Enough.\n 10230- Add Synonym field to Item Master File.\n \nThis patch covers several E3Rs. They all involve Entry, Editing\nor Printing associated with the Item Master, Procurement & Accounting\nTransactions, Amendments and Control Point Activity files.\nThe patch includes changes to routines, a new routine, edit and sort\nand print templates, and a new field added to the 'Item Master' file.\n \nThis patch addresses the following E3R's:\n\n
\nNEW CHARGE CARD VENDOR (CITI BANK)\n\n
\nEDITING INVALID PURCHASE CARD DEMOGRAPHIC DATA\n\n
\nThis patch will fix a few NOIS(s) and E3R(s) related to Request For\nQuotation Bid (RFQ) module.\n\n
\nFIX PRINTING PROBLEMS\n\n
\nThis patch resolves various problems associated with Purchase Orders and\nthe use of vendors on those orders. It also addresses shortcomings in\nVendor entry/edit as well as device selection during the printing of\nPurchase Orders. NOIS addressed are ISW-1000-20548, UNY-0500-12573,\nSPO-0200-52561 and POR-0600-50419.\n\n
\nBuild for patch PRC*5.1*20.\n\n
\nAssociated Remedy Ticket issues:\n \n1. TEST PATCH PRC*5.1*114v3\n \n2. FSC code addition to file 441.2 [FEDERAL SUPPLY CLASSIFICATION]\n \n3. Entries remaining in File 423 \n\n
\n1. Option allows PC Orders to avoid Approving Official review\n\n
\nNEW CHARGE CARD VENDOR (US BANK)\n - Increase field length for Field 4 (Bank's Vendor ID) in File 440.6\n from 9 to 11. \n - Modify Inactivate Expired Charge cards option task for card\n 4486 inactivation\n - Create miscellaneous PC reports:\n Citibank cards on file with no US Bank replacement card\n All active Citibank cards with NO new US Bank replacement #\n All inactive Citibank cards with new US Bank replacement #\n - Modify Purchase Card Registration to allow entry of \n replacement card # if card replacing subsequent card.\n\n
\n1. Can't run Carry Forward option\n \n2. Impossible Cost Center in Purchase Order\n \n3. 424.1 for FY 08 data hanging after archive/purge of 98 and 99\n\n
\n1. PRCP MAIN MENU prompts for Primary Inventory Point twice.\n \n2. Undefined TOT+1^PRCHSF3 \n\n
\n1. Prosthetics GUI does not release lock on file 442.6 if maximum\n Common Number is reached.\n\n
\n1. FGH - QT Adjustment for GIP Item - Reason Text\n \n2. Purchase Card Information List Menu Option not working\n \n3. <SUBSCRPT>ST+6^PRCHDP3 \n\n
\n1. GIP Issue - Zero QTY on hand\n \n2. FGH - Fiscal Pending Report incomplete\n \n3. Issue with cancelling a Purchase Card Order that has been reconciled \n\n
\nThis patch introduces enhancements to facilitate monitoring of\n1358 usage.\n\n
\n1. GIP Transaction Register Report print limitation\n \n2. GIP Issue\n \n3. PRCB MONTHLY ACCRUAL\n\n
\nThis patch will fix the problem with Item Display menu option.\n\n
\nThe new Patch displays CPT (Current Procedural Terminology) code \nof field #.01 and its Short Name (Versioned) of Multiple Field #61 (it \ndepends on date) of File #81 in General Inventory/Distribution related\noptions and reports.\n \nBefore the Patch the IFCAP displays the IEN (Internal Entry Number) of\nthe CPT code and its Short Name of Field #2 (it is date independent) in\nFile #81. The Filed #2 will be phased out soon.\n\n
\n1. <UNDEFINED>DT442+7^PRCFFUD1\n \n2. Unable to process IFCAP requests\n\n
\n1. NIF Filer Error Messages - change to send to Mail Group\n \n2. Receiving error when using Logistics GUI Tool \n \n3. <UNDEFINED>AAC+151^PRCHAAC\n\n
\n1. Jumping to History of Item Display/Print\n \n2. Order Form [PRCP CATALOG/ORDER FORM PRINT] problem\n \n3. Report Issue \n\n
\n1. FGH - duplicate 'RB' xref in file 410\n\n
\n1. Simplied or Detailed PO question\n \n2. Partials with fractions unable to receive in inventory\n \n3. Purchasing Agents Statistics report prints for all users \n\n
\n \n1. File 421.9 - included in annual purge \n \n2. Control Point dollar amount errors\n \n3. Purchase Order Display - multiple amendments show description text\n for only last amendment\n\n
\nThis patch will address the following issues:\n \n1. No CLRS data feed\n \n2. Contract Number on original 1358 but dropped on adjustments\n \n3. Option PRCSR1358 has wrong line label in routine \n\n
\n1. IFCAP NIF maint errors mail message (to Outlook)\n \n2. Running Balance report and FCP recalculations\n\n
\nThis patch will address the following 3 issues:\n3. SHIP TO ADDRESS inconsistent between information entered during\n Prosthetics GUI order entry and reprinting order in IFCAP using \n options REPRINT PURCHASE CARD ORDER or DISPLAY PURCHASE \n ORDER/REQUISITION.\n \n1. When site transfers funds from one Control Point to another they \n receive the message "'No Records To Print' when trying to review \n the entry.\n \n2. When user edits an incomplete detailed Purchase Card Order, the \n existing Cost Center value may not be displayed.\n \n\n
\nBuild for PRC*5.1*8, DDC and SAMS access to Purchase Card information.\n\n
\n1. Amendment to decrease line item quantity to less than delivery\n schedule causes infinite error message loop.\n\n
\n1. Duplicate feeds of CLRS data to Austin when testing on the \n test/mirror account.\n \n2. Ceiling Transactions out of numbers \n\n
\nEnhancement for 1358 miscellaneous obligations:\n o enforce segregation of duties\n o enter additional data on a 1358 request\n o require mandatory fields to be populated\n o include the new authority/sub-authority codes on the SO code sheet \n\n
\n1. SPD - Special Inventory Point type\n \n2. IFCAP archiving problem\n \n3. Invalid routine referenced, ^PRC(410)\n\n
\n This patch adds eight new fields to the F20 CLRS extract and the\n - Subauthority Description\n - Service End Date\n - Service Start Date\nControl Point Activities - F20 extract validation template.\n \nThe eight new fields are:\n - IEN of Authority Code\n - Authority Code\n - Authority Description\n - IEN of Subauthority Code\n - Subauthority Code\n\n
\nProsthetics GUI Required date field does not transfer to Purchase Card \norder.\n\n
\nThis enhancement patch provides new APIs to enable the Fee Basis\napplication to enforce and report on segregation of duties for the\nCertifier of a Fee payment batch. Per segregation of duties a Certifier\ncannot have previously acted in the role of Requestor, Approver or\nObligator on the 1358 that is linked to the payment batch.\n\n
\nReplacement patch for PRC*5.1*127 Entered in Error.\n \n1. GIP Transaction Register Report print limitation\n \n2. GIP Issue\n \n3. PRCB MONTHLY ACCRUAL\n\n
\nThis patch implements Segregation of Duties for 1358s in the\nInvoice Tracking module, such that a Requestor, Approver, or\nObligator may not be the Certifier for Payment of an invoice\nagainst the same 1358. It also enhances the CLRS (NLD) extract\nto include data from the Invoice Tracking file (#421.5).\n\n
\nThis patch provides a one-way data exchange of Miscellaneous Obligations \ndata from IFCAP to the On-Line Certification System (OLCS) at the \nFinancial Services Center (FSC) in Austin.\n\n
\nExtract IFCAP user counts by roles.\n\n
\n1. Site found that during Reconciliation processing it was possible to \n3. Site reports that running 'Summary report of Unpaid Purchase Card \n Transactions' under LINUX OS (print queuing is required) results in\n system error.\n mark more than one charge as 'FINAL CHARGE' which should not be allowed\n as it causes the Approving Official to be delinquent on the Delinquent\n Approval Report.\n \n2. Site reports that Carry Forward processing takes a long time and \n purchase order finalization through Prosthetics GUI will time out \n without completing the order processing.\n \n\n
\nThis patch resolves ticket HD341117 and corrects a problem where\ncertain invalid Vendor Update records caused a program crash.\n \nThis patch resolves ticket HD126460 and disallows certain users\nfrom entering an Adjustment Voucher on a P/C order.\n \nThis patch resolves ticket HD249121 where an FPDS question was \nreflecting a wrong dollar amount for a contract.\n\n
\nThis patch modifies IFCAP to remove the reference "Miscellaneous" or\n"MISC." from 1358 Obligations.\n\n
\n1. PRCH Purchase Card Adjustment Security Error in error display\n\n
\n1. Discount entries are not properly linking to item entries which is\n causing amendment processing errors to occur.\n \n2. The option 'Load IFCAP File 417 Data into PurgeMaster' there is a\n misspelling of the word, "reconciliation'. Currently, it reads as \n "reconilliation".\n\n
\n1. Clinical Logistics Report Server (CLRS) being relocated effective\n 03/01/2012.\n\n
\n1. Tasking the option 'Inactivate Expired Charge Cards' does not work as\n the processing asks for STATION which cannot be answered once tasked.\n \n2. Option, New Purchase Order [PRCHPC PO ADD], must have query INVOICE \n ADDRESS default 'FMS' changed to "VA FSC'.\n \n3. Routine PRCHNPO6 is not in compliance with SACC (VistA Programming \n Standards and Conventions) since lock ':0' is less than the value of\n the kernel variable "DILOCKTM". \n\n
\n \n1. Duplicate 'AB' cross references exist in file 442 [PROCUREMENT & \n ACCOUNTING TRANSACTIONS.\n \n2. Modify IFCAP security key PRCSCPO 'Keep at Terminate' setting to 'NO'.\n \n3. Option PRCB MONTHLY ACCRUAL creating multiple monthly accrual nodes in\n file 440.7 [MONTHLY ACCRUAL].\n\n
\n1. Option 'Convert a Temporary 2237 request to a Purchase Order' results \n in duplicate entries reported in Running Balance report\n \n2. Entering Purchase Order for succeeding fiscal year results in \n requisition with current fiscal year\n\n
\n1. Site reported that they were able to cancel a Purchase Card order \n before the reconciliation charges were removed.\n \n2. In File Description information for file #410 [CONTROL POINT ACTIVITY],\n #442 [PROCUREMENT & ACCOUNTING TRANSACTIONS] AND #443.6 [AMENDMENTS] \n add informational warning: *********DO NOT RE-INDEX THIS FILE**********\n\n
\n12/08/2000:\nThis patch will fix the problem with Selected Control Points Menu Option.\n\n
\nThis patch will establish bidirectional communication (HL7 \nInterface) between IFCAP and the commercial Electronic Contract\nManagement System (eCMS) in Austin, in order to capitalize on the\nabilities of eCMS to consolidate multiple requests, electronically\nprepare and issue solicitation documents, receive electronic offers,\nautomate contract administration, and provide interfaces to the Integrated\nAcquisition Environment initiatives.\n\n
\n1. Clinical Logistics CLRS TRANSMISSION processing update for those sites\n that have migrated to Full LINUX OS.\n\n
\n1. RUNAWAY JOURNALING WHEN CANCELLING A PROSTHETICS PURCHASE ORDER\n\n
\nVistA Fee Automation Enhancement\n o modify PRCS58CC to conditionally skip the control point access check\n o delete accounting technician options used to process 994 code sheets\n\n
\n1. Add the ability to review a 1358 during Obligating process.\n \n2. Option PRCF PRINT FROM LIST causing disk free space warning\n \n3. Documentation issue with CPO User's Guide\n\n
\n1. EDI (Electronic Data Interchange) flagged orders via Fund Control Point\n and Vendor do not appear on UNOBL Running Balance when not passed \n through fiscal.\n \n2. When Fund Control Point flag 'FCP ALL/DELIVERY ORDER SWITCH' is set to\n (A)ll Orders or (D)elivery orders, orders automatically get obligated\n which affect the Running Balance Report.\n\n
\n1. Requisition deletions causing filing errors.\n \n2. Temporary requests being changed to a new transaction number do not \n clear the temporary request cross reference pointers.\n \n3. Changing the description on a Fund Control Point will cause previous\n temporary transactions to fall off the Temporary Transaction Listing.\n\n
\n1. COST CENTER modification for SUB COST CENTER in MOA HL7 segment for FMS\n DOCUMENT TRANSMISSION.\n\n
\n1. Items falling below emergency stock level are not showing on Auto-Gen\n suggested orders.\n \n2. Amendment problem where user is not authorized to amend order.\n \n3. User encountered subscript error while running option 'APPROVE \n REQUESTS'.\n\n
\n1. Entering invalid quantity when receiving order can result in incorrect\n quantity received.\n \n2. Cancel Imprest Funds Purchase Order must be for unobligated order.\n \n3. Testing Cache 2011 found compile error with routine PRCBR1.\n\n
\nThis patch will correct the problem of being able to edit a substation in\nthe Site Parameters menu option. It also contains a change that will not\nallow a user to enter a different station ID at the STATION NUMBER and\nSTATION prompt in the same menu option.\n\n
\n1. Display/print for 1358 prints out of sequence when more than 999\n transactions.\n \n2. Modify IFCAP security key PRCFA SUPERVISOR 'Keep at Terminate' setting\n to 'NO'.\n\n
\n1. Distribution Order Processing option is not scrolling correctly when\n using Enter/Edit Inventory Items.\n \n2. Remove option 'Enter/Edit Control Point Users' to keep user assignment \n solely under Fiscal control.\n \n3. Delivery Orders create obligated amount on Running Balance with auto \n obligate turned off.\n\n
\nThis patch delivers Phase 2, Increment 1 of the IFCAP/eCMS Interface\nproject.\n\n
\n1. Monthly Accrual Document Cost Center issue\n \n2. Audit/control File 442 Internal Entry number (IEN) setting\n \n3. 1358 Adjustments causing FMS SO Document error\n\n
\n1. Incorrect site when adding new secondary inventory point\n \n2. 2237 Request Display missing comments\n \n3. Purchase Order Issue - Obligations not showing on Running Balance\n\n
\n \n1. Add new sub authority to Authority 3.\n \n2. Amendment for Delivery Date with Document transmission to FMS\n \n3. Daily 1358 record entry cannot be entered\n\n
\n1. Non Supply Personnel able to enter/sign off on P.O.\n \n2. Cannot access Inventory Point using Abbreviated Name\n \n3. Full Purchase Card number appears under two display options\n\n
\n \n \n1. Purchase Card Orders - duplicate transction numbers occur \n \n2. Amendment of purchase order for Prompt Pay Type creates incorrect FCP \n adjustment as seen on Running Balance report\n\n
\n1. Amendment error - undefined PCT+2^PRCHSF3\n \n2. Inquire Purchase Card surrogate add error\n\n
\nThis Patch Addresses 2 issues:\n \n1. A duplicate 1358 is created if 2 people are obligating a request\nat the same time.\n \n2. Invalid entries in the "B" and "C" cross references in the BUDGET\nOBJECT CODE (#420.2) file are causing the wrong BOC code \nDescription to display when using the ADD/EDIT BOC [PRCB BOC\nADD/EDIT] option.\n\n
\nBuild for New Socioeconomic Groups.\n\n
\n1. Remove 8243 from Control Point Listing w/Cost Center Exceptions\n \n2. Site references need to be removed from IFCAP Technical Manual\n \n3. Prevent fractional quantities being entered on inventory item receipts\n\n
\n1. 1358 Authorization maximum entry warning\n \n2. Site was able to receive same order multiple times\n \n3. Prompt Pay processing issues \n\n
\n1. Update FSC/PSC codes from current national master file\n\n
\n1. Direct sets causing duplicate entries in file 443. \n \n2. Fiscal Pending Action report not showing approved amendments.\n \n3. All/Delivery orders not auto obligating for Delivery Orders.\n\n
\n1. Do not ask Delivery Date when cancelling order via amendment\n \n2. Subscript error when cleansing/purging files 424/424.1\n \n3. Vendor lookup by DUN & Bradstreet number fails \n\n
\n \n1. Purchase Card and Delivery orders reaching 2237 max on backend filing\n \n2. Purchase Card accrual issue from one quarter to next with Carry Forward\n \n3. Documentation error in Control Point Official's Manual\n\n
\n1. Modify the Annual IFCAP Purge process to be controlled by a\n universal date process\n\n
\n1. 1358 Authorization maximum entry warning\n \n2. Site was able to receive same order multiple times\n \n3. Prompt Pay processing issues \n\n
\n1. Delivery Orders not reflecting the Prompt Pay %\n \n2. Raise order limit to $3500 for Simplified orders\n \n3. Insure correct Fund Control Point (FCP) adjusted for FMS deposits \n received by IFCAP\n\n
\n1. FMS Exception Report not working due to Fileman date call.\n \n2. Prosthetics GUI times out when entering order against FCP with multiple\n Inventory Points attached.\n\n
\nBuild for 'AMENDING A PC ORDER STATUS'.\n\n
\n1. Keep Perpetual Inventory not working correctly for inventory \n distribution of items to the Secondary Inventory Point.\n\n
\nThis patch will address the following 3 issues:\n \n1. Option PRCHLO CLO PROCUREMENT maintenance\n \n2. Error when entering 2237 in new FY\n\n
\n1. Add new Transaction (Ceiling) may have endless loop at times\n \n2. Auto obligation of Delivery Orders ignores Overcommit (off).\n \n3. Next FY 1358s, 2237s and orders rejected by FMS in that FY.\n\n
\nThis patch will fix two issues:\n \n1) When a Receiving Report is deleted the default status is not a valid\nentry, so when it times out the status is set to an invalid status\n \n2) A message is served for POA, PRJ, and ACT the ISMS/FMS TRANS (#423.6) \n file is not cleared\n\n
\nWhen the user enters a "^^" into Copy Control Point User and Profiles\n[PRCB FCP USER COPY] option to exit out and then enters a "^" it receives \nand error.\n\n
\nResolves four issues:\n \n4) When entering a new 2237 if the user "jumps" at the "PRIORITY OF \nREQUEST" field to the "COMMENTS" field then exits an error occurs.\n \n5) If a fund has a multi-approriation the beginning budget fiscal year\nmay not match the fiscal year.\n \n1) When a user enters a temporary transaction, exits out of the session \nand then tries to edit that request there will be an undefined error.\n \n2) If a user exits while creating a 2237, then edits that same 2237, but \ntimes out at the field "DATE OF REQUEST" an error will occur.\n \n3) An error will occur if a temporary transaction is edited in the 2237.\n\n
\nThis patch addresses an issue with the Distribution Order Processing\n[PRCP DIST ORDER PROCESSING] option when an item quantity is null or 0 \nwhich leads to an undefined error.\n\n
\nModify $3500 limit to be $10000 for micro-purchase threshold for goods \nand services. Also, the SPL was increased to $10000 for all PCards for \nsimplified orders.\n\n
\n1. Vendor VR code sheets (document file) are not flagged as accepted\n when FMS passes back the VUP vendor confirmation to Vista\n\n
\n1) If there is not a unique Appropriation Code for a Fund Control Point \n(FCP) an error will be prompted warning that it is not unique. \n \n2) When an appropriation in a no-year fund has the incorrect value for \nthe Fiscal Year, it will prompt the user with an error saying it is the \nwrong fiscal year. \n\n
\nExtended receipt totals; Delivery Order errors\n\n
\nThis patch adds the national option IFCAP USERS BY ROLES COUNTS [PRCHUSER \nROLE COUNTS], which can be scheduled to run quarterly. \n\n
\n1. All Cost Centers link to a Fund Control Point are not presented for\n selection (the current limit is 70 cost centers compiled)\n\n
\nThis patch enhances the NIF/IFCAP ITEM MASTER file (#441) interface \nby implementing the import of new item file entries and the population\nof additional fields. The interface also supports updates to existing \nitem entries in station specific transactions when supplied the IMF#\nfor the item at that site. The MANUFACTURER file (#440.4) is introduced,\nas well as, a means to populate the file through a batch load or\ninteractive user edit. It also sets up restricted vendor and item ien\nranges for only privileged users to edit entries controlled by the\nProcurement & Logistic Office (P&LO).\n\n
\n1) This patch updates the AUTHORITY OF REQUEST (#410.9) file.\n\n
\n1) This patch fixes an infinite loop in the Reconciliation Menu [PRCH \nRECONCILE MENU] when two cards have replaced each other\n \n2) This patch also adds a help prompt in field VENDOR (#5) in file \nPROCUREMENT & ACCOUNTING TRANSACTIONS (#442), and modifies the input \ntemplate PRCHVENDOR to prompt for field FEDERAL SOURCE (.06) in file \nVENDOR (#440) when adding a new vendor.\n\n
\n1) This patch fixes an issue when a Delivery Order fails because it was \noriginally a Purchase Order which was converted. In file PROCUREMENT & \nACCOUNTING TRANSACTIONS (#442) field PROCESSING REQUIRED IN FISCAL (#63) \nexists when it should not. \n \n2) This patch fixes printing formatting issues with the option Fiscal \nPending Action [PRCB RPT FISCAL PENDING ACTION].\n\n
\nBackup of PRC*5.1*221 on Jul 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n1. IFCAP Edit Inventory item for $0 Total Value and On-hand>0 \n \n2. Ensure Order Item description does not violate order printability\n \n3. Prevent <undefined> error when an order is displayed at the same time\n the order amendment is approved\n\n
\nBackup of PRC*5.1*223 on Jul 28, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will correct the following issues:\n \n1. APAR missing due-in orders from Vista\n \n2. Correct FMS Transaction date handling in Invoice Processing for Payment\n \n3. Modify fiscal receipt handling/transmission \n \n4. Add a new Sub-Authority to 1358 handling\n\n
\nBuild for PRC*5.1*25, 'Purchase Card Transactions on Build Lists'.\n\n
\nBackup of PRC*5.1*220 on Jul 28, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThere is one incident corrected in this patch:\n \n1. STOP FPDS MESSAGE TRANSMISSION TO AAC\n\n
\nPatch PRC*5.1*224 will update line item internal entry numbers (IENs)\nand remove associated discounts when a line item is deleted using the\nEdit an Incomplete Purchase Order [PRCHPC PO EDIT] option.\n\n
\nThis patch creates a Purchase Card Order accrual data extract in support\nof the FMBT (Financial Management Business Transformation) initiative.\n\n
\nThis patch changes the default directory for the "Enter the file's \ndirectory: " prompts for the item and manufacturer bulk load options. It \nalso provides a default file name for the manufacturer bulk load option.\n\n
\nThis patch creates fields in the VENDOR (#440) File and the VENDOR EDIT\n(#440.3) File to store the GSA SAM Unique Entity Identifier (UEI). It\nalso adds the UEI to the VENDOR File's Identifier. It also adds the UEI\nto Input Templates so that the value can be entered into the VENDOR File\nentries. Additionally, this patch adds the UEI field to the OMN^O07 HL7\nmessage sending 2237 data from IFCAP to eCMS.\n\n
\n1. Usage Demand Analysis Report time period calculation is off by 1 month\n\n
\nPatch PRC*5.1*230 addresses an issue where 1st and 2nd digits of 4 digit\nyear were used for fiscal year instead of 3rd and 4th digits of 4 digit \nyear for fiscal year.\n\n
\nREMOVE SEMI-COLONS BEFORE SENDING TO FILEMAN\n\n
\nBackup of PRC*5.1*232 on Nov 22, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch resolves the following 2 NOIS:\n did not display on the PO.\n\nSOLUTION:\n Modify routine PRCHAMYA\n\n======================================================================\n\nPROBLEM:\nNCH-0998-41392 (undef QQ^PRCHAMYA)\n Undefined error occurred because the array DIR(A) does not exist.\n 1. CTX-0296-70401 (Amendment for Line Item Edit)\n\nSOLUTION:\n The DIR(A) array should be DIR("A").\n 2. NCH-0998-41392 (undef QQ^PRCHAMYA)\n\n======================================================================\n\nPROBLEM:\nCTX-0296-70401 (Amendment for Line Item Edit)\n PO item descriptions were amended, but the new description\n\n\nThis patch resolves a variety of print issues: adjustment voucher printing\nproblems, <UNDEFINED> errors and print device handling at integrated sites\nutilizing substation functionality.\n\n
\nREMOVE SEMI-COLONS BEFORE SENDING TO FILEMAN\n\n
\nCLEAR BAD DATA NODES IN THE FUND CONTROL POINT (#420) FILE\n\n
\nPatch PRC*5.1*236 adds FORTY (40) federal supply classification numbers\nto the FEDERAL SUPPLY CLASSIFICATION (#441.2) file.\n\n
\nThe purpose of this patch is to count the description and comment fields \ncharacter size accumulated for transmission and limit those fields output \nfor transmission to 210 characters.\nWhen an entry in the PROCUREMENT & ACCOUNTING TRANSACTIONS FILE \nDescription field or COMMENTS contain more than 210 characters the \nVISTA/IFCAP receiving reports do not transmitt to the VA accounting \nsystem due to oversize transaction.\n\n
\nIFCAP-GIP Users are currently prompted to respond to Federal Procurement\nData System (FPDS) questions during order entry. However, answers have not\nbeen sent to the Austin Accounting Center (AAC) since the interface was \nshutdown via IFCAP patch PRC*5.1*220 (STOP FPDS MESSAGE TRANSMISSION) \nthat was nationally released in July 2021. \n \nSupply chain users are prompted to provide responses to FPDS, this patch\nis removing the FPDS questions.\n\n
\nPATIENT DISTRIBUTION COST REPORT FIX\n\n
\nFIX LAST DATE RECEIVED IN POST\n\n
\nFIXES FOR USAGE DEMAND ITEM REPORT AND NO PROGRAM ERRORS; ADD PAGE BREAK\nBETWEEN CASE CARTS AND INSTRUMENT KITS\n\n
\nThis patch will fix the problem with PPM Status of Transaction Report\nand problem with selected Fund Control Point menu option.\n\n
\nThis patch contains enhancements and bug fixes to the Point of Use\ninterface. It enhances the interface by allowing GIP on-hand totals to\nautomatically match what is in the supply station. This functionality\nrequires a single request per one-time adjustment.\n \nThe fixes are to an undef error in PRCPHLPO occuring when the order is\ndeleted prior to its refill transaction updating the GIP files and to\nenable the item update transactions to build 'add' transactions when they\nare requested.\n\n
\nBuild for patch PRC*5.1*35, Unapproved Reconciliations.\n\n
\nThis patch resolves a problem created by IFCAP patch PRC*5.1*28. At the\n'STATION NUMBER:' prompt in the Site Parameters [PRCH SITE EDIT] menu\noption, if a user enters "???" or any combination thereof, a list of\navailable station numbers does not display. Instead, the only data that\ndisplays is the help text. Patch PRC*5.1*39 corrects this so that the\navailable station numbers will now display when "?" or "??" or "???" is\nentered.\n\n
\nThis is a patch that limits the display of the warning message that was a\npart of PRC*5.1*22.\n\n
\nThis patch will fix the problem with the Purchase Order shipping amount.\nIf user creates a Purchase Card Order with a Shipping amount, the system\ndoes not add the shipping amount to the total amount. This will allow the\nuser to exceed the Single Purchase limit amount.\n\n
\nThis patch restores the link between the Deactivate a User [XUSERDEACT]\noption, and the IFCAP application. This link was severed by Kernel patch\nXU*8*117. A new action type option named PRCS TERMINATE was created.\nIt has been linked with the Kernel 'extended action' option XU USER TERMINATE.\nThis link is needed so that a terminated user is removed from all IFCAP\ncontrol points.\n\nThis patch also ensures that deactivated users within multiple stations are\nremoved from all control points.\n\n
\nThis patch increases the maximum length of the IFCAP Vendor Payment\nAddress fields from 23 characters to 30 characters. This change is in\naccordance with the IFCAP FMS Address Information project. There are no\nNOIS associated with this patch.\n\n
\nThis patch corrects the problem where using the Change Existing\nTransaction Number [PRCSANTN] menu option can result in dollar amounts\ndoubling on the Year to Date Accrual [PRCB YEAR TO DATE ACCRUAL].\n\n
\nThis patch addresses the following problems:\n vendor specific line item information.\n\nProblem 4: Change in source code and the deletion of the contract\n number was not reflected in the purchase order display.\n\n\n\nProblem 1: The purchase order does not appear under the vendor\n name listing if the vendor has been changed.\n\nProblem 2: Contract number does not show in block 14 of the\n Amendment.\n\nProblem 3: Change in vendor does not prompt the user to change\n\n
\nThis patch will fix the problem with Due-ins not updating in inventory\npoints. It also add a new functionality to the 'Purchase Order Receiving\nTo Inventory Point' menu option.\n\n
\nThis patch resolves a problem that EDI orders cannot be released to\nvendors without Fiscal Review.\n\n
\nThe option, IMPAC Account Information [PRCH IMPACT], is not displaying\ninformation for approving officials whose last names begin with Z. The\nsort template [PRCH IMPAC SORT] has been modified to go from A to ZZ.\n\n
\nThis patch eliminates the hanging of List Distribution Orders To/From\nInventory Points [PRCP DIST ORDER LIST TO/FROM] when one of the\ndistribution orders to be released is being edited at the same time the\noption is run.\n\n
\nThis patch addresses 2 issues:\n(#200) and that user attempts to access the menu option EDI/RFQ Reports\n[PRCO EDI REPORTS], an <UNDEFINED> error is generated.\n \n(1) If the Fund Control Point (FCP) on a purchase order is a Supply Fund\nFCP and the purchase order is being sent EDI, the BI segment in the EDI\ntransaction will not contain the value the user entered in the INVOICE\nADDRESS field (#.04) in the PROCURMENT & ACCOUNTING TRANSACTIONS file\n(#442) on the purchase order.\n \n(2) If a user is not flagged as a Supply employee in the NEW PERSON file\n\n
\nThis patch addresses the following problems:\n Creating a Purchase Card Order from a RIL. The error occurred\n because 2 of the vendors have the same name.\n\nProblem 1: An undefined error occurred in routine PRCSUT2, while the user was\n in the Generating Request from Repetitive Item List option.\n\nProblem 2: While creating a purchase card order from a repetitive item list,\n the item information fails to appear in the enter/edit template.\n\nProblem 3: An undefined error in routine PRCH442A, while the user was\n\n
\nThis patch addessess the following problems:\n\nPROBLEM 1: Purchase Order Display is not consistant using the fund\n control point. (FCP)\n\nPROBLEM 2: The appropriation date is missing from the purchase card order.\n\n
\nThis patch contains all of the components necessary to add the inventory\ninterface that allows GIP to communicate with purchased/rented supply\nstations.\n\n
\nThis patch contains fixes for edits made to items in supply station \nsecondary inventory points and bulletins regarding deleted distribution \norders.\n\n
\nThis patch will give users enhanced control over EDI transmission of \norders.\n\n
\nWhile entering new 1358's, a message is appearing in error. The message\nreads:\n "This is not a new 1358. Adjustments may only be entered through the\n adjustment option."\n \nWhen entering a new 1358 number, the common numbering series is not being\nverified. Routine, PRCHPAT, does not check for common numbering series. \n \nBoth of these issues are being fixed.\n\n
\nThis patch addresses 5 separate issues:\n(4) MAC-0300-61151, Variable Y undefined in routine PRCEADJ1 when\nprocessing AR rebuild.\n \n(5) BIR-1000-32436, Rebuild incorrect document total.\n \n(1) MWV-1200-20958, Incorrect 1358 mail message.\n \n(2) ANC-0201-51570, Unable to exit Edit 1358 Request .\n \n(3) BRX-1099-10192 & DUR-0500-30008, Over Commit Switch is not\nworking.\n \n\n
\nWhen two users use the option Selected Control Points [PRCB PRINT \nSELECTED FCP] at the same time, one of them will error out.\n \nUndefined error, EN2+12^PRCBP, Undefined variable NOLCK\n\n
\nSites have reported misleading information printing in the Receiving \nReport. When an adjustment voucher is used to back out the receipt of \nitems, the person approving the adjustment voucher is not displayed in \nthe Receiving Report. Procurement documents are legal documents and \nshould display the person who actually signed and processed the entry.\n\n
\nThis patch fixes NOIS HEH-0502-40043.\n\n
\nThis patch will allow IFCAP to look for amendment fund in the correct \nfiscal quarter.\n\n
\n \nThis patch will ensure an item under an FCP that has a leading zero appears\nin both formats of the Item History report.\n\n
\nThis patch is in support of the site preparation steps for CoreFLS \nThe compile option examines the IFCAP VENDOR FILE (#440) and other files \nto determine which vendor records will be converted into the CoreFLS \nsystem. Once the compile has been done, various reports may be run to \nshow in summary or detail format the data fields that do not conform to \nthe established CoreFLS data cleansing guidelines.\ndeployment. It contains a new menu, option, and security key. During\nthe installation, the CoreFLS Data Cleansing Menu [PRCL COREFLS DATA \nCLEANSING] is attached to the IFCAP Application Coordinator Menu\n[PRCHUSER COORDINATOR]. Do not assign the security key to any users\nuntil directed to do so by a future official CoreFLS Action Request.\nInstructions for the use of this option will also be included with\nthe CoreFLS Action Request.\n \n\n
\nUpdate for clause 52.219-1 (Oct. 2000)\n \n12/20/2000: Modified routine PRCHP184 to reformat the clause 52.219-1.\n \n01/08/2001: Modified routine PRCHP184 to reformat the clause 52.219-1.\n \n02/27/2001: Added "**" to the 2nd line.\n\n
\nChange overlap for EOAM from four days to one.\n\n
\nFIX FOR CASE CART/INSTRUMENT KIT PRINTS.\n\n
\nThis report has been modified to ensure that the information provided\n\nis move useful to the user community. The following changes have been\nimplemented.\n\n1. Purchase Card Orders with the following status will NOT appear\n on this report:\n a. Order not completely prepared\n\n2. A date range has been added.\n\n
\nRemove 'Do you want to send this EDI?:' prompt.\n\n
\nThis patch addresses 2 NOIS(s). The 1st NOIS deals with a type 12 amendment\nfor a purchase order. In a type 12 amendment, a new purchase order is created,\nand the old purchase order is cancelled. Currently, if a type 12 amendment is\nperformed, the new [PRCH DISPLAY PO] option. In the second NOIS, users have\ndifficulty editing the socio-economic group for a vendor.\n\n\n
\nThis patch will change the way the transmission date gets assigned on the \nSV code sheet generated by the Accrual (Monthly) [PRCB MONTHLY ACCRUAL] \noption.\n\n
\nThis patch is in support of the site preparation steps for CoreFLS\nthat do not conform to the established CoreFLS data cleansing guidelines.\ndeployment. It should be installed as a normal patch. A new option will\nbe installed under the CoreFLS Data Cleansing menu [PRCL COREFLS DATA\nCLEANSING] with the same security key as the other options. Instructions\nfor the use of this option will be included in an official CoreFLS Action\nRequest.\n \nThis option contains various reports that show in summary or detail\nformat the data fields for records in the GENERIC INVENTORY file (#445)\n\n
\nThis patch is in support of the site preparation steps for CoreFLS\nTRANSACTIONS file (#442) that do not conform to the established CoreFLS\ndata cleansing guidelines.\ndeployment. It should be installed as a normal patch. A new option will\nbe installed under the CoreFLS Data Cleansing menu [PRCL COREFLS DATA\nCLEANSING] with the same security key as the other options. Instructions\nfor the use of this option will be included in an official CoreFLS Action\nRequest.\n \nThis option contains various reports that show in summary or detail\nformat the data fields for records in the PROCUREMENT & ACCOUNTING\n\n
\nThis patch is in support of the site preparation steps for CoreFLS\npurchasing records will be converted into the CoreFLS system. Once \nthe compile has been done, various reports may be run to show, in \nsummary or detail format, the open POs for current or previous \nfiscal years.\ndeployment. A new option, Local Vendor Data Cleansing Reports [PRCL\nLOCAL VENDOR], is added to the CoreFLS Data Cleansing [PRCL COREFLS\nDATA CLEANSING] menu as part of the installation of this patch.\nInstructions for the use of this option will be included with the \nCoreFLS Action Request.\n \nThe compile routine examines the IFCAP PROCUREMENT & ACCOUNTING\nTRANSACTIONS FILE (#442) to determine which local vendor \n\n
\nCHANGING OVERLAP DAYS AT END OF ACCOUNTING MONTH TO ZERO.\n\n
\nThis patch resolves the following two NOIS(s).\n the New Purchase Order option before an authorized buyer\n is entered, then the PO will not appear an the Incomplete\n Purchase Orders Report.\n\n\nNOIS DESCRIPTION\n---- -----------\nPRO-1100-12536 If 2 new purchase orders are entered for the same item on\n the same day with the same control point, only one of these\n purchase orders will appear on the HISTORY OF ITEM DISPLAY\n1. GRJ-1199-52228\n report.\n==============================================================================\n\n2. PRO-1100-12536\n\n==============================================================================\n\nNOIS DESCRIPTION\n---- -----------\nGRJ-1199-52228 Problem with Incomplete Purchase Orders. If a user exits\n\n
\nMISLEADING OPTION HELP TEXT/MISPELLED VARIABLE\n\n
\nThe purpose of this patch is to modify the Funds Distribution module\nThe new funding will be implemented April 1, 2004, and is retroactive\nto October 1, 2003.\nof IFCAP allowing the VHA (Veterans Health Administration) to comply\nwith the FY2004 Omnibus Appropriations Bill.\n \n \nRationale\n---------\nThe Fiscal Year 2004 Omnibus Appropriations bill, mandated by Congress,\nhas reclassified VHA funds for distribution, obligations, and expenses.\n\n
\nThis patch will ensure that the "D" cross reference for the PROCUREMENT\n& ACCOUNTING TRANSACTIONS file (#442) gets updated when amending a P.O.\nwith multiple edits.\n\nThere is also a Post-Install routine that removes a non-namespaced\nglobal introduced by PRC*5.1*76. The name of the global is ^NIXON.\n\n
\nUNDEFINED VARIABLE 'LNCT'/INVALID CLASSIFICATION OF REQUEST\n\n
\nThe operational test site using CoreFLS was reverted to its pre-CoreFLS \nstate and the CoreFLS project was suspended. Consequently halting data \ncleansing efforts and requiring that components of the data cleansing \npatches (PRC*5.1*60, PRC*5.1*61, PRC*5.1*66, PRC*5.1*69) be removed at \neach site.\n\n
\nThis software extracts from IFCAP for National Item File (NIF) processing\nvendor data to a host file in a record format mutually agreed upon with\nthe NIF contractor.\nthose active items which have been purchased within the previous 12 \nmonths, which have been received, issued, assembled, or manually adjusted\nin a Generic Inventory Package (GIP) inventory point within the previous \n12 months, which are flagged in the ITEM MASTER file (#441) as reusable,\nor which are active components of active case carts or active instrument\nkits. At the user's option, GIP physical inventory count transactions \nwithin the previous 12 months are also included in the analysis of \nitems to export. The software then writes item data and associated last\n\n
\nThis patch contains the software required to run the DynaMed-IFCAP \nInterface.\n\n
\nThis patch corrects some inconsistencies and M errors associated with\nthe date range selection for some of the Generic Inventory reports.\n\n
\nProsthetics to IFCAP interface routines.\n\n
\nADJUSTMENT VOUCHER SCROLLING PROBLEM\n\n
\nFix error in [PRCP UNDO CONVERSION]\n\n
\nThis patch installs software in support of the National Item File - Phase \n'IT' segment of the PHA transaction for inclusion in OA&MM's Procurement \nHistory database at the Austin Automation Center (AAC).\n1 initiative, as defined by IT Service Request #20020708.\n \nIFCAP has been enhanced to receive via an X12 Item Maintenance 888 \ntransaction, the National Item File (NIF)'s item number, short description\nand extended description and store them in the corresponding entry of the\nlocal IFCAP system's ITEM MASTER file (#441). The NIF item number now is \na write identifier for this file. One can now also select entries using \nthe NIF item number. In addition, the NIF item number is now sent in the \n\n
\nThis patch modifies the PRCS APPROVE REQUEST print template to resolve\nan issue which was causing the APPROVE REQUEST option to fail when an\nitem description contained a vertical bar (pipe) character. It also \ndistributes a new copy of PRCPSFSV which contains a new set of FMS \ntransmission codes.\n\n
\n This patch corrects two issues related to the interface between the\n DynaMed inventory system and IFCAP.\n The first issue relates to the inappropriate use of BOC 2696 and the \n second to a problem that occurs when a Receiving Report is deleted\n prior to being signed.\n\n
\nThis patch updates the PRCPPOLM routine to correct a problem with \nPurchase Card orders. The patch also changes the data type of the HL7 \nTRANSACTION NUMBERS field in file #447.1 and modifies the input transform \nfor that field.\n\n
\nThis patchs corrects a problem with the PUBLIC LAW 100-322 REPORT.\nThe report failed with a Null Subscript error if there were no\nrecords to report.\n\n
\n<NULLSUBSCR> CP+12^PRCSUT\n\n
\nThis patch will correct a coding error in which invalid entries were \nbeing added to the "C" cross reference of file #442. This had the \npotential to cause problems with the PURCHASE ORDER DISPLAY option.\n\n
\nThis patch will enhance the Integrated Funds Distribution, Control Point \nActivity, Accounting, and Procurement (IFCAP) package to capture \nPurchase Order (PO) Activity and Generic Inventory Package (GIP) module\ndata so the data can be rolled up at the Veterans Integrated Services\nNetwork (VISN) and national levels for analysis by the Prosthetic and\nClinical Logistics Office (PCLO).\n\n
\nThis patch will address new requirements for reporting VISTA procurement \ninformation to the FPDS system at the Austin Automation Center (AAC).\n \nNew Product Service Codes (PSC) and Federal Supply Classification \n(FSC) codes with corresponding "groups" are added to files #441.2 and\n#441.3. \n\n
\nThis patch corrects a Null Subscript error that can occur when a user \nprocesses multiple Purchase Order amendments without exiting the option \nprior to each amendment.\n\n
\nISSUE BOOK SOFTWARE CHANGES\n\n
\nGIP, CASE CART AND INSTRUMENT KIT FIXES\n\n
\nThere are two issues being addressed with this patch, the first is an\nerror in the code that ran the option PRCB CPA RUNNING BALANCE. The error\nwas involves the setting of the DIC screen when certain conditions are \nmet. The current code causes a runtime syntax error. The second issue \ninvolves a change in functionality that will allow users of the option\n'AMENDMENT TO PURCHASE ORDER' to exit the user prompts while performing a\n'Line Item Add'. The user will be able to use the standard '^' to exit \nthe prompts. If the user did not enter a value for the Quantity field, \nthe line item is deleted.\n\n
\nThis patch addresses issues with the new functionality introduced by the \npatch PRC*5.1*79 and reported via the Remedy system.\n\n
\nThis patch corrects an issue with FMS transactions that have a Transcode \nof PR (payroll). The issue occurs when payroll transactions use the same \ncommon number series for transaction numbers as Purchase Orders. The \ncode initially look at file 442 to find a transaction number match, if \none did not exist it then searched for payroll transactions. \nUnfortunately, if the same common number series was used to create both \ntypes of transactions there are instances where two separate transactions \nhave the same exact transaction number causing an incorrect posting of \npayroll data to Purchase Order transactions.\n\n
\nMaking a change to how data is extracted from file 442. Originally the \nextracts were run from the first of the month and at least 45 days prior \nto the extract date. The change will now run the extract from the\nbeginning of the Fiscal Year until the date of the extract (NOW).\n\n
\nThis patch corrects two issues. The first involves the inability of the \nDisplay/Print 1358 option to find an obligation number when the user had \npreviously used this option and then backed completely \nout. \n \nThe second issue involves the Running Balances option. A blank page \nprecedes the printing of the report and the page number is wrapping to \nthe next line.\n\n
\nThis patch addresses three issues. The first issue is with the option\nPRCH CREATE PURCHASE CARD which creates a purchase card order from a\nRepetitive Item List (RIL). An undefined error occurs when one user\ndeletes an RIL that is being used by another user. The second issue is an\n<undefined> error when running the option Mandatory Sources 850\nUndelivered Orders when there are 0 records to report. The third issue \nis a <undefined> error when the user tries to quit the report display \nwith an '^' at the start of a new page.\n\n
\nThis patch corrects two issues. The first issue involves a FRAMESTACK \nerror in running the BOC Totals report when the number of obligations in \na selected quarter approaches 3,000. The second issue occurs when \nrunning the option Generate Requests From Repetitive Item List Entry \n[PRCSRI GENERATE]. An Undefined Error occurs when the default device for \nthe station selected for the given type of order (example: Supply) is \neither out-of-date or is non-existent. \n\n
\nCLEANUP IFCAP ARCHIVE/PURGE PROCESS\n\n
\nThis patch addresses an enhancement request to modify IFCAP to properly \nclassify On Demand Items (ODI).\n\n
\nLINKS FSC TO STOCK STATUS REPORT\n\n
\nTHIS IFCAP PATCH WILL DISPLAY DATA FROM IFCAP FILES #441 AND #442\nAND FROM PROSTHETICS FILE #664. DBIA #4345 AUTHORIZES READ ACCESS TO\nFILE #664.\n\n
\nThis patch addresses three issues. The first issue involves contract\nnumbers not being sent in the FPDS HL7 message of Amendments to Delivery\nOrders. Because the contract number is not sent the orders are being\ninterpreted as an open market order causing problems in Austin.\n \nThe second and third issues are related to the DUN & Bradstreet DUNS#'s \nchanging format. Formerly DUNS#'s used the 9th digit as a check \ndigit and lengths were variable. Now the 9th digit will no longer be \nused as a check digit and valid lengths are either 9 or 13 numbers only.\n\n
\nThe first issue involves the input transform of the \nThe fourth item fixes a problem that could occur when editing the\nCONTRACT/BOA # field on an amendment.\n \nThe fifth item fixes a problem with ^-jumping at the CONTRACT/BOA #\nfield in the Edit an Incomplete Purchase Order option.\n \nThe sixth item updates the Purchase Card limit to $3,000.\n \nThe seventh item corrects two spelling errors in an\nIFCAP Option File entry.\nAppropriation field in the Fund Distribution file (#421).\n \nThe second issue involves allowing all users of the New Detailed Purchase \nCard Order option to enter an Item Discount.\n \nThe third item is a fix to the help text display at the prompt:\n"Do you want to request a refresh of the supply station QOH?"\n \n\n
\n Updates the 'Stock On Hand Report Greater Than Range' from 90 to 270.\n\n
\n1. Involves the addition of a new Federal Supply Classification (FSC) \n cleanup old data. \n Code to the FEDERAL SUPPLY CLASSIFICATION (#441.2) file.\n \n2. A correction to an improper reference to the Vendor Product Number\n during the transmission of the Electronic Request for Quotation (RFQ).\n \n3. The creation of a new option that cleans out all record types in \n CALM/LOG CODE SHEET (#423) file and CALM/LOG TRANSMISSION\n RECORD (#421.2) file for a given time frame. This is needed to \n\n
\n1. Issue involves the inability of the Approving Official or Alternate \n \n3. Issue is with a Source Code Amendment to a purchase order. When the\n Source Code is amended to Federal Contract there is no screen in \n place to make sure the item on the purchase order has a contract \n associated with it before approving the amendment. \n \n4. Issue involves the ability to select inactive Fund Control Point\n (FCP) when creating Purchase Card Orders.\n Approving Official to cancel incomplete PC orders. Currently, only \n the individual who placed the order can cancel the order. If the user\n who placed the order has left the VA there is no proper way to handle\n the canceling of the order. \n \n2. A correction to edits of the Edit/Remove Reconciliation \n [RECONCILIATION PRCH P.C.O. ED/REMO RECONCILE] option which was\n affecting the Delinquent Approval Report.\n\n
\n1. Involves the phone number extension in ELECTRONIC SIGNATURE \n3. Problem updating the Prompt Pay Type (#4) field in the INVOICE \n TRACKING (#421.5) file. This Prompt Pay Type needs to match the\n Financial Management System (FMS) PPAY Table. Currently it \n does not.\n \n4. Involves the inability to delete partial orders in a given state. The \n problem is not with the functionality, but with the error message that\n is displayed. Currently when the user tries to delete they get a beep\n and "??". The user should see a valid error message properly\n explaining the issue.\n BLOCKS. IFCAP software is set up to display a 4 digit extension,\n but some sites now have a 5 digit extension. The new 5 digit \n extension causes the number to not be displayed.\n \n2. Problem with adding a Generic Inventory point through the Manager\n For Supply Warehouse Inventory Point Menu [MANAGER FOR SUPPLY\n WAREHOUSE I] option.\n \n\n
\n1) Resolves <FRAMESTACK> error in PRCPUSEL by eliminating the\n possibility of an infinite loop which had occurred at some sites.\n \n2) Corrects a problem with "Generate 2237 Requests from Repetitive\n Item List Entry" (RIL) for a DynaMed RIL.\n \n3) Alters the PRCHNREQ Input Template to look for the new VA FSC\n address rather than the old FMS address.\n\n
\nPatch PRC*5.1*112 fixes the following:\na) A rounding problem with some of the numbers in the CLO GIP\n REPORTS (CLRS) report.\nb) A <SYNTAX> error when a line item list doesn't exactly match\n the requested format.\nc) A cross reference in file 420.14 (PRCD FUND) which was causing\n wrong records to be pulled up.\n\n
\nDescription:\n===========\n \nThis patch is addressing the issue regarding an <UNDEFINED> error that\noccurred in the Bay Pines' DynaMed/IFCAP interface. Bay Pines is the only\nsite that is running the DynaMed/IFCAP interface. With the help from the\nVistA Interface Engine (VIE) group and DynaMed, a test link between \nDynaMed and IFCAP was created to complete the secondary review test in \nthe Bay Pines test environment.\n\n
\nThis KIDS Build contains the definition for maintenance release IFCAP\nv 5.1.\n\n
\nThis package distributes the IFCAP Data Dictionaries for: CONTROL POINT\nACTIVITY, FISCAL and SUPPLY.\n\n
\nThese are the routines for patch 41, which produces Bill and Transaction\nreports for the IG office.\n\n
\n \nInit and routines for PRCA*4.5*39\n\n
\nThis patch is a follow up patch to the lockbox patch 114.\n\n
\nThis patch fixes the problem with the lockbox automatic processing\ngenerating a checksum error if the sequences are received out of order.\n\n
\nThis build addresses several NOIS entries in patch PRCA*4.5*149. For more\ninformation please see NPM.\n\n
\nPatient accounts under $25 and over 180 days old.\n\n
\nPatch for transmitting TOP 'close-out' documents to close out IRS records\nsent to TOP.\n\n
\nTest version - 6/19/2000\n\n
\nThis patch corrects a problem with assigning billing numbers. It\nalso removes an option in conjunction with the removal of the IRS\ncode sheets in patch PRCA*4.5*155.\n\n
\nThis patch changes the logic used to add and exempt interest,\nadmin, and penalty charges. It corrects problems with the\npayment posting module.\n\n
\nThis patch will send Interest, Administrative, Marshal Fee, and\nCourt Cost Charges to FMS on the SV and WR documents.\n\n
\nThis patch changes the fund for ineligible hospital bills. If\nan ineligible bill is created before Oct 1, 1992 or after\nSep 30, 2000, the ineligible bill will be recorded in fund 3220.\nOtherwise, it will be treated as a non-accrued bill and recorded\nin fund 5287.\n\n
\nDSM-E-LEVEL ERROR IN PRCARFD\n\n
\nCCPC patient statement problems and amount of deposit field in 344.1 fixes\n\n
\nThis patch will correct problems with patient account discrepancies.\n\n
\nThis patch will remove the duplicated posting of deposit 269296\nmade on November 14, 2000.\n\n
\nPatch to screen out Pseudo-SSN's from being referred to DMC.\n\n
\nPatch to stop interest and admin for sites whose statements were delayed\nby the duplicate lockbox receipt problem.\n\n
\nTOP (Treasury Offset Program) Referral: Patch PRCA*4.5*141\n\n
\nThis build is for various NOISes corrected by PRCA*4.5*165\n\n
\nThis build introduces the CLAIMS MATCHING REPORT which lists third party\nbills for a specified date range or single bill with the matching first\nparty debts.\n\n
\nThis patch will fix a problem with the way write offs store the\ninterest and admin charges written off.\n\n
\nThis is the KIDS distribution for patch PRCA*4.5*167, Diagnostic \nMeasures Phase IV. This is an accompanying patch. The main patch\nfor this project is IB*2.0*123 (Integrated Billing).\n\n
\nBecause of a recent general counsel decision, the IRS offset sotware is\nbeing modified to remove all bills, for which the patient has reimbursable\ninsurance. A screen has been added in routine PRCAOFF2 to accomplish\nthis.\n\n
\nThis patch will fix account discrepancies caused by the wrong\ndate being used on exemption transactions.\n\n
\nThis is the KIDS distribution for patch PRCA*4.5*171, Diagnostic Measures\nUpdates. This is an accompanying patch. The main patch for this release is\nIB*2.0*159 (Integrated Billing).\n\n
\nThis patch will fix several discrepancies within the AR package.\n\n
\nThis patch contains functionality to implement the HSIF Fund for\nthe Millenium Bill.\n\n
\nThis patch fixes the problem with the AR Data Collections Report and FMS\nquarterly month.\nrejecting the data due to a negative value being sent by the HSIFVALUE.\nThis is due to old bills being included in the calculation of the report. \nThis patch fix, ignores the old bills and they are not included in the\ncalculations, avoiding the negative balance in HSIFVALUE.\n \nOther problems fixed with this patch are correction of the Domain name \nwhen sending AR reports, incorrect amount displaying on the Agent Cashier's\nscreen and the ability to regenerate the OIG report if it is not a \n\n
\nThis patch will reverse the duplicate deposits processed by Lockbox.\nThe following deposits will be removed:\n Deposit: 269623 Transmission Date: 3/14/02\n Deposit: 269624 Transmission Date: 3/14/02\n Deposit: 269625 Transmission Date: 3/14/02\n Deposit: 269626 Transmission Date: 3/14/02\n Deposit: 269630 Transmission Date: 3/15/02\n Deposit: 269631 Transmission Date: 3/15/02\n\n
\nThis patch fixes the MCCF/HSIF TR documents from being rejected in FMS due\nto the AR package not sending a valid transaction category that is\nacceptable by the FMS programs.\n\n
\nCHANGES IN 430.2 FILE REQUIRED BY IB PACKAGE\nMODIFICATION OF TRANDESC^RCCPCPS1 API CALL\n\n
\nNDB Collections are not being updated with the HSIF dollar amounts from \nthe sites. This patch modifies the monthly AR data collection process so \nthat the HSIF amounts are included in the data sent to the NDB.\n\n
\nGEOGRAPHIC MEANS TEST, PART 2\n\n
\n \nroutine for joint inquiry fix\n\n
\nREGIONAL COUNSEL ENHANCEMENT\n\n
\nAPI FOR IB IN SETTLEMENT\n\n
\n \nIRO-0502-40037 Claims Matching Report Subscript Error - the error \noccurred every time the patient was not in the debtor file. Code\nwas modified to check to see if the patient was in the debtor file.\n \nCHY-0502-52969 W+8~DIR error when using P-MESSAGE - the problem existed \nin the option Claims Matching Report [RCDP CLAIMS MATCH] if the report is \nqueued. The Taskman variable ZTQUEUED was being Killed in RCDPRTP.\n \nThe variable ZTQUEUED is used to check whether or not a job is running in \nthe background (IF $D(ZTQUEUED)). It is controlled within Taskman and\nThis patch addresses the following NOISs:\nshould not be killed in a routine.\n \nMON-0202-51360 <UNDEF> BILL+3^RCDPRTP0 ERROR while using the Claims\nMatching Report Option.\n \nSLC-0602-52580 ERROR: BILL+3^RCDPRTP0 while using the Claims Matching\nReport Option.\n \n\n
\n \n1. OKL-0902-70880 ACCOUNT REFERRING TO TOP/NO STATEMENTS\n2. MAR-1102-20444 CCPC-Failed Trans. Station 641 Perry Point. MD\n3. LON-0103-60496 Military Bills referred to TOP\n\n
\nHIPAA Confidential Communications, the AR part.\n\n
\n \n1. TUC-1102-60505 EDITING FMS ACCTG ELEMENTS\n2. WAS-0802-21469 Error ~%DSM-E-STRLEN~\n\n
\n \nThis emergency patch addresses one issue. The issue is pertaining to new\nbehavior introduced in patch PRCA*4.5*188 which prevented the entry of\nsome Fund codes based on the category of a bill.\n\n
\nAccounts Receivable API for My HealtheVet\n\n
\n \nThis patch addresses 2 issues. The first issue is regarding the \n"Bad Debt Write-Off (Plus)" line in the Bad Debt report not updating\ncorrectly. The second issue concerns patient balance discrepancies\nthat appear on the Statement Discrepancy Listing report even though\nthe accounts are actually in balance.\n\n
\nChange logic to generate 1 mailman message to ALL recipients of the AR \nSupervisor List, rather than a separate mailman message for each \nrecipient.\n\n
\nThis is patch 54, which is a patch to correct a problem encountered with\npatch 43, when test data was inadvertantly sent with the patch.\n\n
\nThis patch contains all of the date changes to comply with the new End\nof Month EOAM for the ARDC, Bad Debt, and OIG reports.\n\n
\nThis patch adds the functionality of holding transmissions to FMS of new \ndocuments created after the EOAM.\n\n
\nThe patch enables support for the new Point Accounts.\n\n
\nSets effective date of the Point Accounts changes to 9/26/03 (except the\neffective date for the ARDC functionality which remains 10/1/03).\n \nFMS Documents, resubmitted before 10/1/03 will also not contain Point \nAccounts funds.\n\n
\nThird Party EDI Lockbox Patch PRCA*4.5*173 (Accounts Receivable component)\n \nPlease refer to the patch description in the National Patch module and\nthe users documentation for detailed information about this patch.\n\n
\n \nThis patch addresses 2 issues. The first issue is regarding no \ntransmission received for station #641, VA Maryland Health Care dated\n03/15/2003 after they ran the Transmit CCPC Messages [RCCPC TRANSMIT] \noption. The second issue is that site receives the same transmission error\nmessage T404W almost every single month from Austin when they attempt \nto transmit a build file that takes over 24 hours to complete.\n\n
\nThis patch creates a header record for the AR electronic message\nwhich gets transmitted to the OIG.\n \nThe header record will include the following:\n1. The total number of extract messages that will be transmitted to Austin.\n2. The sequential message number of the message itself\n (i.e., "message 5 of 21").\n\n
\nMY HEALTH-E-VET ENHANCEMENT\n\n
\n \nfunds for the New Point Accounts and they print in the 215 report.\nA site reported that there have been three issues found since the install\nof PRCA*4.5*203. The first issue is that the Revenue Sources Code for\nPharmacy bills don't print and it appears to happen when the category is\nRX CO-PAYMENT/NSC VET. The second issue indicates that Pharmacy First \nParty bills are being deposited into a fund of 5287.3 while the patch\ndescription in PRCA*4.5*203 states that the New Point Accounts for \npharmacy bill should be 5287.1. The third issue is that the old closed\nreceipts (FY03) prior to the installation of PRCA*4.5*203 are reporting\n\n
\n \nThis patch addresses two issues. The first issue is regarding two\nusers who were able to exempt interest/admin. charges on the same bill\nat the same time through the Administrative Cost Adjustment [PRCAF ADJ\nADMIN] option. The second issue is about the receipt profile that\ndidn't show the last person's initials when he/she edited the receipt\nby using EP Edit Payment under the Receipt Processing.\n\n
\nThe Patient Name Standardization patch DG*5.3*244 introduces changes \nof fuzzy lookups in DG*5.3*244. A flag variable DPTNOFZK has been added\nto prevent the flag variable DPTNOFZY from being killed within the AR\nprocess in DG*5.3*541. Patch PRCA*4.5*198 has been created to set the\nflag variables at the various points where selection of bill numbers or\npatients occurs.\nto the patient look up logic which implement "fuzzy" lookup functionality.\nThis allows pick lists to return entries beyond those that match the \nuser's input exactly. With the fuzzy lookups in place a bill number\nsuch as K301EL2 may also return patients whose names begin with KEL.\nThis had an unexpected result on the AR options when the user\nentered bill numbers.\n \nA flag variable DPTNOFZY has been implemented to allow the suppression\n\n
\nThis patch addresses two issues. The first issue is regarding the payment\namount listed in the Electronic Remittance Advices (ERA) messages that is\nnot equal to the amount for the Electronic Funds Transfer (EFT). The EFT\ncan be referenced for the ERA payment that the payer has paid for a bill.\nThe second issue concerns an undefined error when processing an EDI\nLOCKBOX receipt.\n\n
\nThis build contains the code to store the patient name in the ELECTRONIC\nREMITTANCE FILE (#344.4) for both valid and invalid bills. Previously,\nonly invalid bills would store this data. This change is needed to\nsupport automatic payment verification in the e-Payment Phase 2 patch.\n\n
\nBAD DEBT REPORT CORRECTION\n\n
\nThis patch modifies Patient Statements that are transmitted from the\nsites to the Austin Automation Center (AAC). The account number on\nthese statements currently contains the patient's SSN. The patch\nreplaces the SSN portion of the account number with the patient's DNF.\n\n
\nThe first issue is regarding an Electronic Remittance Advice (ERA) for \nthe Electronic Funds Transfer (EFT) deposits appearing on the Unapplied\nEFT Deposits Report which indicated it was not being processed although \nthe receipt document showed it was entered on line.\n \nThe second issue shows the [PRCAD MAS COMPLETE] option and the\n[PRCAD MAS INCOMPLETE] option working incorrectly. Site received the \noutput which appeared that it found all the bills without screening\nout their services. \n\n
\nChange references to CHAMPUS to TRICARE.\n\n
\nThis patch will implement CBO data extraction logic for\nthe Boston Allocation Resource Center.\n\n
\nContains small fixes to problems found in the later stages of testing for\ne-Payments enhancements patch PRCA*4.5*208.\n\n
\nBill of Collection with Multiple Fiscal Years\n\n
\nThis patch implements new point accounts 528705-528709 and 528710\nIt also changes point accounts 5287.1 to 528701, 5287.3 to 528704 and\n5287.4 to 528704.\n\n
\nPATCH OVERVIEW\nintroduced in a phased implementation strategy. This deployment strategy \nIs this prescription number - 123456? No//\nIs this ECME Rx reference number - 123456? No//\n \n \nTechnical Description\n----------------------\nThe patch modifies the procedure PNORBILL^RCDPURED, which is called from \nthe Data Dictionary of the file #344 (sub-file #344.01). It calls the IB \nprocedure REC^IBRFN, which was also modified by this project (patch \nIB*2.0*223) to support ECME Numbers.\nwas utilized due to the complexity of the functionality and the number of \nTo provide a more clear users interface, the IB procedure REC^IBRFN will \nbe returning a flag - the second formal parameter by reference,\nindicating, how the users input was recognized: Tricare Authorization \nNumber, Prescription Number, or the ECME Number. The consequent users \nprompt will indicate that. \n \nRoutine RCDPESR1 modifies the EDI LockBox AR functionality to \nadd capability of matching ECME number to IB bill automatically.\n \n \nproduct line dependencies.\nROUTINES SENT WITH PATCH\n------------------------\nThe following is a list of the routines included in this patch.\nThe second line of each of these routines now looks like:\n \n ;;4.5;Accounts Receivable;**[patch list]**;Mar 20, 1995\n \n CHECK^XTSUMBLD results\n \n Routine Before Patch After Patch Patch List\n \n ------- ------------ ----------- ----------\n PRCASVC3 1629668 1748043 158,202\n RCDPESR1 13660919 14225614 173,214,208,202\n RCDPURED 8549824 9425617 114,169,174,196,202\n \n Total number of routines - 3\n \n \nDATA DICTIONARIES SUMMARY\n-------------------------\nThe first release of this two part implementation is BPS*1*0, comprised \n \nThe following is a list of the DD changes included in this patch.\n \n File # Field # Name\n ---------- ------- ------------------------------\n 344 AR BATCH PAYMENT\n 344.01 TRANSACTION (sub-file)\n .09 PATIENT NAME OR BILL NUMBER\n \n Total number of modified files - 1\nof the new Electronic Claims Management Engine (ECME) package (in the BPS \n \n \nSOFTWARE AND DOCUMENTATION RETRIEVAL\n====================================\nThe software for this patch is being distributed in host file \nBPS_1_0.KID. The host file will contain seven KIDS builds.\nThe builds contained in the BPS 1.0 multi-package distribution are:\n \n Package Patches\n ------- ----------------------\nnamespace), plus the patches PSS*1*81, IB*2.0*223, IB*2.0*251, and \n ECME BPS*1.0*1\n Pharmacy Data Management PSS*1.0*81\n Integrated Billing IB*2.0*223, IB*2.0*251\n Accounts Receivable PRCA*4.5*202\n \n \nINSTALLATION INSTRUCTIONS\n==========================\n \n1. Use VA FileMan to add the new domain, EPHARMACY.VITRIA-EDI.AAC.DOMAIN.EXT, \nPRCA*4.5*202, which are listed here in order of installation. BPS*1*0 is \nto the DOMAIN file (#4.2). The installation instructions are included in \nthe patch description for the XM*DBA*160 patch. This domain must be in \nplace before the installation of the IB*2*251 patch that is included in \nthe BPS 1.0 Master Build.\n \n2. Download the KIDS file BPS_1_0.KID via FTP. This file needs to be \nretrieved in ASCII format.\n \n3. Review mapped sets for the PSS*, IB*, and PRCA*namespaces. If the \nroutines are mapped, they should be removed from the mapped set at this \na dormant release that only allows each site to perform preliminary setup \ntime.\n \n4. From the Kernel Installation & Distribution System menu, select the \nInstallation menu.\n \n5. From this menu, select the Load a Distribution option. When prompted \nfor a file name, enter \nthe directory name where you FTPd the build, followed by BPS_1_0. In our \nexample, the file name is USER$:[ANONYMOUS]BPS_1_0.KID. Determine the \nlocation where you stored your build to decide the correct file name \nwork and to confirm that the software does not adversely affect other \nentry.\n \n6. At the "Want to Continue with Load? YES//" prompt, enter YES.\n \n7. At the "Want to RUN the Environment Check Routine: YES//" prompt, \nanswer YES.\n \n8. From this menu, the installer may select to use the following options:\n \n(When prompted for INSTALL NAME, enter BPS 1.0)\n---------------\npackages.\n \n a. Backup a Transport Global - This option will create a backup \nmessage of any routines exported with the patch. It will NOT backup any \nother changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - This option will \nallow you to view all changes that will be made when the patch is \ninstalled. It compares all components of the patch (routines, DDs, \ntemplates, etc.).\n \n \n c. Verify Checksums in Transport Global - This option will ensure the \nintegrity of the routines that are in the transport global.\n \n9. At the "Select Installation Option:" prompt, enter 6 Install Package(s)\n \n10. At the "Select INSTALL NAME:" prompt, enter BPS 1.0.\n \n11. When prompted, "Want KIDS to Rebuild Menu Trees Upon Completion of \nInstall? YES//" respond NO.\n \nThere are two main areas addressed by BPS*1*0:\n12. When prompted, "Want KIDS to INHIBIT LOGONs during the install? \nYES//" respond NO.\n \n13. When prompted, "Want to DISABLE Scheduled Options, Menu Options, and \nProtocols? YES//" respond NO.\n \n14. When prompted, "Device:Home//" respond with the correct device and DO \nNOT queue this to P-Message.\n \n15. If routines were unmapped as part of step 3, they should be returned \n \nto the mapped set once the installation has run to completion. \na. Registration of the Pharmacy with the Vitria BusinessWare IE.\nb. The Insurance Matching of Group Plans with Pharmacy Plans\n \nFollowing the installation of BPS*1*0, each site must register their \npharmacy with Vitria and match applicable insurance group plans using the \ninsurance matching screens. These processes are detailed in the HIPAA \n \nNCPDP CONNECTION FOR EDI PHARMACY INSTALLATION GUIDE and the MATCH GROUP \nPLANS WITH PHARMACY PLANS document. Both of these documents are located \non the anonymous directory. It is very important that the IRM or person \ninstalling the patch at each facility provide a copy of these documents \nto its ADPAC(s) and any other relevant staff who will be responsible for \nregistering their pharmacy with Vitria and completing the insurance \nmatching process.\n \nAt a later date, additional HIPAA NCPDP patches will be released to \nactivate all of the HIPAA NCPDP functionality. Until that time, sites \nThe Healthcare Insurance Portability and Accountability Act National \nwill not be able to electronically submit claims utilizing this new \nfunctionality.\n \nThe HIPAA NCPDP project was created in response to a Chief Business \nOffice (CBO) request for modifications to several Veterans Health \nInformation Systems and Technology Architecture (VistA) software \napplications in accordance with HIPAA Electronic Data Interchange (EDI) \ntransactions and NCPDP mandated format standards, specifically the NCPDP \nTelecommunication Standard v.5.1.\n \nCouncil for Prescription Drug Programs (HIPAA NCPDP) initiative, whose \nThe specific functionality for this patch is listed below.\n \n \nFunctional Description\n-----------------------\n \nThe patch PRCA*4.5*202 represents the Accounts Receivable portion of the \nNCPDP-Pharmacy Connection project. It modifies the EDI Lockbox \nfunctionality by adding the ability to manually process EOB related to\nNCPDP claims.\nultimate goal is to provide functionality allowing electronic \n \nThe patch modifies Accounts Receivable (AR) users interface to make it\npossible to select bills by entering NCPDP Prescription/Service Reference\nNumbers.\n \nWhen working with "Receipt Processing" [RCDP RECEIPT PROCESSING] and \n"Link Payment to Account" [RCDP LINK PAYMENT TO ACCOUNT] menu options,\nusers normally enter the Bill Number or the Patient Name corresponding to\nthe processed payment.\n \ntransmission of Outpatient Pharmacy (OP) prescription claims to payers \nThe users prompt to that input is:\n \nPATIENT NAME OR BILL NUMBER:\n \nAlthough the prompt is asking for a Patient Name or a Bill Number, \nthere are some other types of data that may be entered to identify \nthe corresponding bill. Previously the choices were:\n \n- Tricare Authorization Number;\n- Prescription Number. \nand the receipt of claim responses (including drug utilization review \n \nThis patch adds one more type of data that can be entered to identify a \nBill. The "ECME Number", the Prescription/Service Reference Number, \nindicated in the NCPDP Electronic Claim, can now be entered to identify \nthe bill.\n \nThe help text for the above user's prompt has been modified to provide \na better explanation of the expected input:\n \nPATIENT NAME OR BILL NUMBER: ?\nresponses and warnings) on a real-time basis, is being developed and \n Enter one of following: Patient Name, Bill No, Tricare Authorization \nNo,\n ECME Rx Reference Number or Prescription Number.\nPATIENT NAME OR BILL NUMBER: \n \nIf the users input is not a Bill Number and not a Patient Name, and is \nrecognized as a Tricare Authorization Number, Prescription Number or a\nECME Number, the subsequent user's prompt will be respectively:\n \nIs this TRICARE reference number - 123456? No//\n\n
\nMedicare Remittance Advice (MRA) - AR patch.\nThis patch defines two new data elements in file PRCA(430,D0,13). Field \n131: Medicare Contractual Adjustment and field 132: Medicare \nUnreimbursable Expense. \nIn addition this patch makes changes to the Bad Debt Report and to the \nFMS SV document.\n\n
\nHVE III AR PATCH\n\n
\nThis patch addresses 2 issues.\n \nThe first issue is regarding the Customizing option under the Agent Cashier\nReceipt Processing Option that was losing the customization features when\na user was at site running a multi-node system.\n \nThe second issue is regarding a subscript error occurred at line\nEN+14^RCCPCBJ when there is no any AR CCPC statement available for\ntransmission.\n\n
\nThis patch addresses 2 issues. The first issue is regarding a problem when\na bill was entered in lowercase letters, it would pull up the incorrect \npatient and not the bill that site entered.\n \nThe second issue is regarding an undefined error when the payment on a\nreceipt has an EEOB Worklist decrease adjustment associated with it in the\nReceipt Processing [RCDP RECEIPT PROCESSING] option.\n\n
\nThis patch addresses 2 issues.\nmade, a Modified Billing Document is being sent to FMS instead of the\ncorrect Write Off Document. This problem only affects bills with a \ncategory of 30 (tricare) or 32 (tricare third party) AND using a \ncontractual adjustment.\n \nThe first issue is incorrect coding in routine RCBEUBIL. This is not\ncausing an error and it doesn't appear to have caused any incorrect data\nin the past but the change is needed to safeguard against any future\nproblems.\n \nThe second issue is incorrect coding in routine RCBEUTR1. The code is\nlooking at file #433 instead of #430. If a contractual adjustment is\n\n
\nPatch to fix errors caused by bad records.\n\n
\n \nThis patch will allow integrated sites to have multiple domains for\nregional counsels.\nThis redirects Vista transmissions to Regional Counsel to new RC addresses\nfor regular transmissions and Death Notifications.\n \nThis patch also fixes and undefined error in routine RCRCREC.\n\n
\nPhase II, Part 1 of IB/AR Data Extract. Changes as of 6/23/05.\n\n
\nCCPC patient statements\n\n
\nThis patch fixes the problem of setting the correct fiscal year for the \nfirst few days of the new FY that fall in September. This patch also sets\nthe beginning Fiscal Year (BFY) for all 528701 - 528710 transactions\nto "05". This will be the BFY for all 5287 funds regardless or the FY.\nThis patch also fixes the reversal date for the Account Receivable End\nof Accounting Month processing and some misc. documentation changes.\n\n
\nThis patch addresses 2 issues. The first issue is about the letters for\nthe CWT PROCEEDS and PARKING FEES bills which are not being generated so\nvendors can not receive the notices about their bills. The second issue is\nabout the letter format which the address is printing too low to appear in\nthe envelope window.\n\n
\nDescription:\nDescription of enhancements:\n---------------------------\n1. Remove the "In Part" and "In Full" wording from the patient statements. \n2. Identify patients to the AAC with will require larger print (font) on\n their billing statement.\n \n \n\nThis patch addresses the following NOIS message(s):\n---------------------------------------------------\n===========\n1. WIM-0402-20728\n \nThis patch contains 2 enhancements and resolves 1 NOIS.\n \nThe Chief Business Office has requested additional enhancements to the\nsoftware that transmits the Patient Statements from the VAMC to the AAC.\n \n \n\n
\nThis patch addresses one issues. The problem is that valid debts in\npatient accounts which are not referred to TOP (Treasury Offset Program)\nfor collection when a repayment plan is established for one or more bills \nbut not all bills.\n\n
\nThis patch reschedules the historical CBO extracts as one month of data \nper extract.\n\n
\nThis patch suspends new DMC and TOP referrals, through 2/28/06, for those\nveterans affected by Hurricane Katrina.\n\n
\nThis patch exempts interest and administrative charges \nare generated.\nfor Katrina affected veterans, calculated from 9/1/05\nto patch installation. It also suspends the addition of\nnew interest and administrative charges for Katrina\naffected patients. It also suspends the printing of CCPC\nstatements for those affected by Katrina.\nThis patch also adds code to run the postinit to exempt \ninterest and administrative charges for newly flagged Katrina\npatients. This will run prior to the TOP, DMC and CCPC statements\n\n
\nThis patch addresses two issues. The first is regarding the current fiscal\nyear 06 setting to the 5287 accounts which caused TR and OP documents \nto be rejected in FMS. The second is about an undefined error at line \nDEC+8 in routine RCXFMST1 when processing receipts for EDI Lockbox.\n\n
\nPatch PRCA*4.5*239 contains modifications to the Bad Debt Report.\nThese modifications were recommended by a management audit conducted\nby the Systems Quality Assurance Service at the Austin\nAutomation Center. Please refer to the patch description for\na concise list of enhancements included in this patch.\n\n
\nThis patch contains a new option, the Emergency Response Report.\namounts of all of the affected veterans, the number of affected\nveterans and the average amount suspended per veteran.\nThe detailed listing will display, by affected veteran, the bills\nwhose payments are currently suspended until Feb 28, 2006\nthe principle amount, the interest and administrative amounts,\nand the total amount per bill and total amount per patient.\n \nThis report has been placed under the Management Reports ... [PRCAD MANAGEMENT REPORT MENU] menu, located under the Report Menu\nfor Accounts Receivable ... [PRCAD REPORT MENU] menu option,\nwhich is under the Clerk's AR Menu ... [PRCA CLERK MENU].\n \nSites should run this report to get a detailed or summary display\nof the amount of funds that will be suspended due to Katrina\naffected patients at their sites. The summary report will list, for the\nsite, the total balance (principle + Interest + administrative)\n\n
\nDD changes required for PRCA*4.5*56\n\n
\nThis patch fixes 2 errors:\n \n 1.An error in routine RCXVDC5 that caused the refill date of\n prescriptions to not transmit.\n 2.An error in routine RCXVDEQ that prevented some transactions and\n bills from transmitting to the ARC.\n \nIt also queues the Active Bill transmission to the ARC at 8pm on the \ndate of the installation.\n\n
\nThis patch addresses 1 issue. This change will allow the Revenue Source \ncode to contain alphanumeric characters as well as numbers in any of the\nfour positions. The code is entered using the Enter/Edit Revenue Source\nCode [PRCA FMS RSC ENTER/EDIT] option.\n\n
\nPatch PRCA*4.5*241 is the last in a series of patches that will\nadjust the accounts of veterans affected by Hurricane Katrina.\nThis patch will exempt interest charges added to these veterans'\naccounts between 8/29/06 and 2/28/06, and cancel all co-payment\ncharges billed to these veterans in this same period. Integrated\nBilling patch IB*2*340 must be installed before this patch can be\ninstalled.\n\n
\nHIPAA NCPDP Global project\n \nsupports the electronic transmission outpatient prescription claims and \nbilling collection and management.\n\n
\nPatch PRCA*4.5*246 re-enables two Katrina-related functions\nthat became inactive on 4/30/06. They are the option\nEmergency Response Report and the patch PRCA*4.5*241\npost-initialization process.\n\n
\nThis patch adds four new fields to the VISTA IB-AR extract.\nIt also fixes a subscript error when using the option:\n[PRCAF ADJ ADMIN] Admisistrative Cost Adjustment.\n\n
\nAR IB EXTRACT PHASE II PART 2\n\n
\nThe Chief Business Office has requested a patch to correct the audit\nproblem when billing CHAMPVA Other Health Insurance.\n\n
\nThis patch supports the National Council for Prescription Drug Programs \nthat will enable the user to reopen a closed Electronic Claims Management\nEngine (ECME) claim; updates to the Rx Activity Log; and permanent storage\nof Claims activity information as reported by the ECME Billing Events\nReport.\n(NCPDP) standard which was adopted under the Healthcare Insurance\nPortability and Accountability Act (HIPAA) for pharmacy claims. This patch\nis one of six to be released. Three patches will be released in a KIDS\nmulti-build distribution containing: BPS*1*3, PSO*7*247, and IB*2*342. \nThree patches will be released individually and they are: PRCA*4.5*247,\nPSX*2*62, and PSS*1*115.\n \nEnhancements included in the release of the six patches are a new option \n\n
\n After installing this patch the system will correctly determine whether a\n Workman's Comp bill is summary or detail when there is no value in the\n FUND field.\n\n
\nThis patch addresses 4 issues. The first issue is that site requested to\nThe fourth issue contains the same error occurring in the same report \nabove when site queued the report to a spool.\nlimit the credit card number which is printed on the patient's receipt\nfor security issue. The second issue is about the software that calculates\nan estimate for what a patient will be charged for prescriptions that are\nawaiting release was not updated to correctly reflect the new $8 copay\namount.\n \nThe third issue indicates an undefined error that site received when they\nqueued the report to P-MESSAGE in the EFT Deposit Reconciliation Report.\n\n
\nCBO Data Extract NPI enhancement\n\n
\nThis patch is being released in conjunction with the Pharmacy \nReengineering Encapsulation effort. While no new functionality for the \nIntegrated Billing package is released with this patch, all direct global \nreferences to the Outpatient Pharmacy files have been replaced by this \neffort.\n\n
\nThis patch is being implemented in support of the Automated Service \nConnected Designation (ASCD) project. The ASCD project has a Recovered \nCost Report where they want to look for bills and payments for encounters \nthat have had their Service Connected status changed by the ASCD options. \nThis project has requested access to the Accounts Receivable (AR) package \ndata in support of this report.\n\n
\nThis patch will update the deposit ticket number series with\n"569"xxx for the EDI Lockbox process.\n\n
\nThis patch is addressing the issue regarding all the Third Party bills\nassociated with only revenue codes for pharmacy that are missed in\nthe CBO AR Data Extract process.\n\n
\nThis patch addresses 5 issues. The first issue is regarding the OBR\n(AR/FMS) data that has been incorrectly deleted in the OBR Reconciliation\nreport. The secondary issue is about the coding error in routine RCDPEX32.\nThe third issue is regarding the billing information that was missing in\nthe transmission message that is sent to the department of Justice or\nRegional Counsel. The fourth issue is regarding the <UNDEFINED> error at\nline Q3+2^PRCASVC when returns a bill's FMS fund code. The last issue\nis about the SSN showing on the reprint of the statements at site.\n\n
\neClaims Plus Iteration 3, phase 2 (the AR part of phase 2)\n\n
\nUpdates to the EEOB Worklist.\n\n
\nThis build is for the PRCA*4.5*253 patch which is for the "Hold Debt to\n b. Introduce a new "DMC Debt Valid" field in the Accounts Receivable\n application.\n c. Create a new report option in AR for Veterans who are SC 50% to\n 100% or in receipt of a VA pension.\n d. Create a new report option in AR to assist the AR Supervisors in\n reviewing the processing of the bills for Veterans who are SC 50%\n to 100% or in receipt of VA pension.\n e. Create a new report option in AR to assist users in focusing on\n reviewing the legitimacy of bills where the veteran has a Rated\n Disability change during a given time period and is neither SC 50%\nDMC" project. This will provide an enhancement to help avoid inappropriate\n to 100% nor in receipt of VA Pension.\ndebt referrals to Debt Management Center (DMC) for veterans who are either\nService Connection (SC) 50% to 100% or in receipt of a VA pension.\n \nThis patch will modify the existing VistA AR application to:\n a. Enhance the existing VistA software DMC logic to exclude DMC\n eligible debts associated with veterans who are SC 50% to 100% or\n in receipt of VA pension from being referred to the DMC.\n\n
\nThis patch is being implemented in support of the "AR Changes for Deposit\nthe Treasury contracted bank. This is a high priority project to prevent\nloss of revenue and ensure veteran satisfaction by continuing to allow\nthem to pay their first party bills using credit cards\n \nThis patch will modify the existing VistA AR application to do the\nfollowing:\n a. Expand field length to 9 digits for deposit ticket number to\n accommodate new unique sequence to prevent duplication of deposit\n ticket numbers.\n \nTicket Number" project. This is an enhancement to the Accounts Receivable\n Note: 9-digit deposit ticket numbers will only be allowed for\n payments processed through the AR Automatic Payment Processing\n Server. Manual entry will continue to be limited to 6 digits.\n \n b. Remove the ability for sites to create local deposit tickets that\n begin with the 669 prefix as it is reserved for electronic check\n deposit tickets.\n \nNo changes were required to allow the 9-digit deposit ticket numbers to be\ndisplayed in the AR Options and Report, or for the interface which send\n(AR) System to allow for 9 Digit Deposit Ticket Numbers and to prevent\nthis data to the FMS system.\n \nAdditional documentation on this project can be found in the project\nnotebook for "AR Changes for Deposit Ticket Number" which is in the VA\nHealth IT (VHIT) Project Repository (TSPR). The link is:\n \n http://tspr.vista.domain.ext/warboard/anotebk.asp?proj=1274\nusers from entering Deposit Ticket Numbers beginning with 669.\n \nThis change is a result of a mandate by the Department of Treasury to use\ntheir contracted bank for all credit card processing. To prevent a loss\nin revenue for these credit card transactions, the VA must comply with the\nTreasury mandate and be able to accept the new deposit number schema from\n\n
\nThis patch addresses two related issues that involve the patient statement\nprint functionality. First, the third statement is now printed when\nnecessary even if there has been no activity except interest/admin\ncharges. Second, the messages from option [PRCA ACCOUNT CHECK] have\nbeen adjusted to be consistent with the above.\n\n
\nThis patch addresses 1 issue.\nThe issue pertains to ex-employee bills that are not sent to TOP\nbecause the third letter is not printed if the bill is less than $25.\n\n
\nThis patch addresses two issues. The first is about that site requested to\nenter a bill for more than the unit cost limit of 999999 in the NEW BILL\n(ENTER) option. The second is about that site asked to remove the veteran\nname and a portion of SSN from the message subject line due to the new\nsecurity posture of the VA.\n\n
\nESTIMATED RX COPAY FIX\n\n
\nWarning for unapplied amount.\nNOIS PRO-0998-10071\n\n
\nThis patch addresses 1 issue:\n1. Some bills in the Office of the Inspector General (OIG) extract \n of the Accounts Receivable Data Collector (ARDC) are reported \n in the wrong General Ledger (GL) number and need to be corrected.\n\n
\nIncorrect Station Numbers on Tricare claims are leading to rejections at\nFinancial Management System (FMS).\n\n
\nThis patch addresses 2 issues. The first issue is regarding missing\nbatches when running the CBO Data Extract process. The second issue is\nabout a local array not being killed properly in the RCDPE Exception\nProcess option.\n\n
\nThis patch will correct references for Revenue Codes charges and \nProsthetics data information when transmitting bills to Regional Counsel \n(RC).\n \nThis patch will also fix a display format problem for the Transactions \nsection of the Profile of Accounts Receivable option. The changes will \nlet the display easier to read by the viewer.\n\n
\nThis patch will fix a line tag with a wrong routine name when queuing an \nAR - Print ERA Discrepancy Report from the EEOB Worklist [RCDPE EDI \nLOCKBOX WORKLIST].\n\n
\nThis patch addresses two issues. The first issue is regarding the EEOB\nWORKLIST option showing the unrelated Explanation of Benefit (EOB) results\non a selected electronic remittance advice (ERA).\n \nThe second issue is about the "***Trans # xxxxxxxx REQUST QUEUED ***"\nmessage incorrectly appearing in the Brief Account Profile option.\n\n
\nE-Billing Iteration 4, enhancement 6, Preserve claim#\n\n
\nFMS 5010 CHANGES\n\n
\nePharmacy Phase 5 - NCPDP D.0\n\n
\nThis Integrated Billing (IB) patch expands the HIPAA 5010 \n2. Modify the Full Account Profile option [PRCAY FULL ACCOUNT PROFILE] to\n---------------------------- \n<List each NSR and its subject. If there are none, then list N/A>\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\n<List PSI number and brief description.>\n \n \nRemedy Ticket(s) & Overview\n allow up to 10 characters of an inactive claim number to display.\n---------------------------\n<List each Remedy Ticket, and include a description of the problem and the\nresolution.>\n \n1. <Remedy Ticket #> <Subject>\n \nProblem:\n-------\n<Enter a brief description of problem reported.>\n \n \nResolution:\n----------\n<Enter a brief description of the resolution.>\n \n \nTest Sites:\n----------\n<List test sites that actually participated in testing and signed off on \nthe patch. A copy and paste from NOIS displaying the test sites in\nproduction can be used.>\n3. Create the processes to support the receipt, storage and display of\n \n \nDocumentation Retrieval Instructions\n------------------------------------ \nUpdated documentation describing the new functionality introduced by this \npatch is available.\n \nThe preferred method is to FTP the files from \nftp://download.vista.domain.ext/.\nThis transmits the files from the first available FTP server. Sites may \n Medicare deductible information from Trailblazer Health care\nalso elect to retrieve software directly from a specific server as \nfollows:\n \n Albany ftp.fo-albany.domain.ext <ftp://ftp.fo-albany.domain.ext>\n Hines ftp.fo-hines.domain.ext <ftp://ftp.fo-hines.domain.ext>\n Salt Lake City ftp.fo-slc.domain.ext <ftp://ftp.fo-slc.domain.ext>\n \nDocumentation can also be found on the VA Software Documentation Library \nat: http://www4.domain.ext/vdl/\n \n Enterprise.\nTitle File Name FTP Mode\n-----------------------------------------------------------------------\n<Documentation title> \n \n \nPatch Installation:\n \n \nPre/Post Installation Overview\n------------------------------\n \n<Provide a brief overview of what the pre/post installation entails. The\nactual instructions will be listed below in the Installation Instructions\nsection. Note whether pre/post installation routines can be deleted after\nthey run or whether they are automatically deleted.>\n \n**** Please note, if you select the option below, Compare Transport Global\n to Current System, and select #1 Full Comparison, you will get a\n system error: <UNDEFINED>S+1^DIQ ^IBA(364.6,1937,0) due to a known\n issue with the KIDS Full Compare option (see Remedy Ticket\n HD0000000449128). You can run any of the other 3 compare options\n4. Create a new option called the Medicare Deductible Alert Worklist [PRCA\n without issue.\n \nInstallation Instructions\n-------------------------\n ******************************************************************\n * You should install this patch during non-peak hours, when no *\n * Integrated Billing or Accounts Receivable users are on the *\n * system. *\n ******************************************************************\n \n MDA Worklist] from which users can view Medicare deductible \nThere are no options to disable.\n \nPre-Installation Instructions\n-----------------------------\n<Provide a brief description of what the pre-installation will be doing. \nList pre-installation instructions (i.e., links, filers, or batch\ntransmissions that need to be stopped, jobs unscheduled, etc.), if\napplicable.>\n \n1. Choose the PackMan message containing this patch.\n information.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select\n the Installation Menu. From this menu, you may elect to use the\n following option. When prompted for the INSTALL enter the patch #(ex.\n XXX*X.X*XX):\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\nenhancements \n \n backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \n4. From the Installation Menu, select the Install Package(s) option and\n \n choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO//' \n <Provide the installer with guidance on whether or not menu trees need\n to be rebuilt. For instance the menu trees do not need rebuilt if \n there are no menus involved in the patch or their system rebuilds menu\n trees nightly using TaskMan. If they must answering YES to rebuild \n the menu trees warn them that it could affect users on the system and\n installation times will increase.>\nPatch Components\n \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?\n NO//'\n \n <to inhibit logons.>\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO// \n \n <Provide the installer with guidance on whether or not to disable \n================\n scheduled Options, menu options, and protocols.>\n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0// respond 0.\n \n \nPost-Installation Instructions\n------------------------------\n \n<Provide a brief description of what the pre-installation will be doing. \nList pre-installation instructions (i.e., links, filers, or batch\n<Additional patch components can be added alphabetically if needed.>\ntransmissions that need to be stopped, jobs unscheduled, etc.), if\napplicable.>\n \n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\nintroduced in patch IB*2.0*432.\n------------------ ------------------- --------------------\n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\n \n \nMail Groups Associated:\n \n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\n \nMDA \n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\nThe intent of this patch is to:\n----------- ---- --------------------\n \nPRCA MDA WORKLIST run routine\n \nPRCAL LIST MENU menu\n \nPRCA MDA SERVER server\n \n \nProtocols Associated:\n1. Modify the Third Party Joint Inquiry option [IBJ THIRD PARTY JOINT\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\n \nPRCA MDA COMMENT\nEXIT \n \nPRCA MDA ENTER\nCOMMENT \n \n INQUIRY] to allow up to 10 characters of an inactive claim number to\nPRCA MDA ENTER/VIEW\nCOMMENTS \n \nPRCA MDA EXIT \n \nPRCA MDA MANAGEMENT \n \nPRCA MDA REVIEW\nSTATUS \n \n display.\nPRCA MDA TPJI \n \n \nSecurity Keys Associated:\n \nSecurity Key Name New/Modified/Deleted\n----------------- --------------------\n \n \nTemplates Associated:\n \n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\n \n \nAdditional Information:\n<Additional information sections can be added alphabetically if needed.>\n \n \nNew Service Requests (NSRs)\n\n
\nThis patch fixes an undefined error that occurs after installing\nPRCA*4.5*60.\n\n
\n5010 EPAY ENHANCEMENTS\n\n
\nThis patch fixes an issue found in the Accounts Receivable Bad Debt \nreport. This defect causes "No Fault Auto" receivables to be incorrectly \naccounted for on the Bad Debt Report.\n\n
\nThis patch resolves the following three issues:\n3. Four reports have been modified to display all of the 9-digit deposit \n number. They are EFT Deposit Reconciliation Report, Daily Activity\n Report, EFT Unmatched Aging Report, and Unapplied EFT Deposits Report.\n \n1. For manual creation of deposits, AR must be changed to allow users to \n create a deposit record with a Deposit Ticket Number that is six digits\n long, with no restrictions on the first three digits. \n \n2. For the Third Party EDI Lockbox process, AR must be changed to accept\n any nine-digit deposit number.\n \n\n
\nVeterans Health Administration (VHA) Chief Financial Officer - Office \nResources Management has requested to inactivate one (1) existing revenue \nsource code and add five (5) new revenue source codes to the REVENUE \nSOURCE CODE file (#347.3).\n \nThis update will be effective October 1, 2012.\n\n
\n \nThis patch addresses one issue about the incorrect charge type NURSING\nHOME CARE (NSC) showing on the patient's bill.\n\n
\nThis patch will support those sites that have migrated to full Linux \noperating system for transmitting their CBO Data Extract files.\n\n
\nThe HIPAA 5010 D.0 Level II Phase 2 project includes the following\n data because VistA did not recognize the duplicate receipt number\n until later in the creation of receipt process.\n \n2. Manual Receipts - EFT Selection\n -------------------------------\n Modified VistA so that the user is unable to select a MATCHED EFT\n when performing the Manual Match EFT-ERA. Due to this modification the\n user will NOT be able to see or select a MATCHED EFT when using the\n option MANUALLY MATCH EFT-ERA.\n \nmodifications to the Electronic Payments V. 4.5 application:\n Once the match is made, the EFT will NOT be listed on the Unmatched\n Aging Report.\n \n3. EFT Unmatched Aging Report & ERA Unmatched Aging Reports\n --------------------------------------------------------\n Modified VistA so that only non-duplicate EFTs that are unmatched and\n have a payment amount greater than zero appear on the EFT Unmatched\n Aging Report. VistA was also modified so that only non-duplicate ERAs\n that are unmatched and have a payment amount greater than zero appear\n on the ERA Unmatched Aging Report.\n \n \n4. Unapplied EFT Deposit Report\n ---------------------------\n Modified VistA to prevent duplicate EFTs from displaying on the\n Unapplied EFT Deposit Report. \n1. Duplicate Receipt Numbers\n -------------------------\n Modified VistA to create a unique receipt number for the user when\n creating a receipt in order to post payments without manual\n intervention. Previously, it was possible for VistA to create an\n already used receipt number and this would cause the user to re-enter\n\n
\nThis patch addresses two issues.\nin the same manner as cash/check payments.\n \nThe second issue is about the account lookup keys which will be included\nin the new Treasury and Compensation & Pension (C&P) withholding deposit\nfiles to identify the correct veteran in VistA.\n \nThe first issue implements two changes to the Automatic Payment Process\nServer [RCDP AUTOMATIC PAYMENTS] option that processes deposit files\ncontaining records of veterans' cash and check payments of their copayment\nbills to the national Lockbox. Vista Accounts Receivable (AR) will begin\nto receive new types of deposit files that represent withholdings of VA\nCompensation and Pension (C&P) benefits or amounts owed to the veteran by \nthe US Treasury, which must be applied to veteran's delinquent accounts \n\n
\nEPHARMACY OPERATING RULES\n\n
\nThis patch will add "THANK YOU FOR YOUR PAYMENT" to the bottom of the \npayment receipt.\n \nThe second item this patch will fix is replacing special characters in \nthe transaction description of the PD segment that caused the CCPC \ntransmission rejected by AAC.\n\n
\nROUTINES FOR PRCA*4.5*65\n\n
\nAfter VistA changed Deposit Ticket numbers to be retained for seven (7) \nyears, site users are experiencing issues with duplicate deposit numbers. \nThis is causing an increasing number of Deposit Ticket have to be manually\nreconciled and there is no workaround for this issue.\n \nThis patch will fix this issue.\n\n
\nThis patch addresses two issues. The first issue involves the criteria\nchecks to identify a bill for VA care or non-VA care in the CBO Data\nExtract process. The second issue is about the DMC Referred Report Print \n[PRCA RCDMC REFERRED RPT] option that opens the device twice resulted\nin the user being prompted twice for a message subject.\n\n
\nThis patch contains three issues. The first issue is about the patient\nstatements not successfully transmitting in Austin for printing. The \nsecond issue is regarding some erroneous admission and ending dates\nappearing on the patient statements.\n \nThe third issue concerns an undefined error when running the [RCDPE EOB\nTRANSFER REPORTS] option.\n \n.\n\n
\nReverse DMC deposit\n\n
\nThe purpose of this patch is to replace direct global reads into the ICD\nftp the data directly to the Boston Allocation Resource Center (ARC).\nOPERATION/PROCEDURE file (#80.1) and the ICD DIAGNOSIS file (#80) with a\nDRG API $$CODEC^ICDEX instead.\n \nThis patch updates one routine in the CBO Data Extract process. A DRG\nGrouper API is being used to retrieve the ICD-9/ICD-10 procedure code\nor ICD-9/ICD-10 diagnosis code for the data extract process to format\nand place them in a flat file via a nightly process. The nightly process\nin the Accounts Receivable Nightly Process Background Job option will then\n\n
\nTEST\n\n
\nThe purpose of this patch is to (1) add the additional suspense types to\nthe Suspension Type field (#90) of the AR Transaction file (#433) for the\nSuspend an AR bill [PRCAC TR SUSPENDED] option, and (2) use a function to\nautomatically generate the 'Brief Comment' for the selective suspension\ntype in the Brief Account Profile [PRCAY ACCOUNT PROFILE] option.\n\n
\nMCCF (Medical Care Collection Fund) Enhancement for uniform use of\n1996 (HIPAA) as amended by Public Law (P.L.) 111-148, The Patient\nProtection and Affordable Care Act (PPACA), Section 1104.\n \nThis patch implements the following:\nCARC/RARC (Claims Adjustment Rason Codes/Remittance Advice\nReason Codes) Codes\n \nThis patch implements changes to the Veterans Health Information Systems \nand Technology Architecture (VistA) Accounts Receivable (AR) software\nrequested by the Veterans Health Administration (VHA) Chief Business\nOffice (CBO) business Solutions to comply with legislative changes\nmandated by the Health Insurance Portability and Accountability Act of\n\n
\nPROCESSING ERROR MESSAGE AND PROBLEM\n\n
\nMEDICAL CARE COLLECTION FUND (MCCF) ENHANCEMENTS PROJECT - ePAYMENTS\n\n
\nThis patch addresses the request about Phase II algorithm adjustments\nthat determine whether an episode of care is identified as VA CARE vs.\nNON-VA CARE in the Vista CBO Data Extract (VDE) process.\n\n
\nThis patch contains VistA changes to support technology and\nbusiness changes that are occurring with the implementation of\nthe Treasury Cross Servicing project.\n\n
\n1. Insure the Implied bill# entered in Receipt Processing payment entry\n posts to the intended implied bill first.\n\n
\n1. Reject transmission processing: Clear CS flag for '3E' reject code, \n absolute value check that is causing reject batches being tossed aside \n and adding new reject reasons to file 348.5\n\n
\n1. Modify internal resolution of reject reason display on profile view of \n bills.\n\n
\nRoutine required to prevent an <UNDEF> in ^XTMP.\n\n
\nConsolidated Patient Statement\n\n
\nConvert all scripts for handling Treasury Cross Service Project (TCSP)\nexceptions between Vista and Treasury to user option with improved\ncontrols. These scripts were provided to sites by the TCSP developers\nto handle mismatched Vista debtor/bills with the Treasury status for\nthe same debtor/bills. \n \nThe sites are currently running these unwieldly scripts that need IT\nintervention to execute in programmer mode.\n\n
\nThis patch is listed as an Emergency patch only due to install timing \nissues for data collection for the DATA Act.\n\n
\nThis patch addresses the following two issues:\n \n1) The weekly TCSP (Treasury Cross Service) batch run at site will error\n when the debtor is not defined in the debtor file.\n \n2) AR/RC Reconcile Roll-up emails have single mail address no longer\n used.\n\n
\nThe weekly TCSP (Treasury Cross Service) batch run at site does not set \nthe correct address information in the C2CA message segment for veterans \nliving in a foreign country.\n\n
\nPatch PRCA*4.5*319 addresses the following Accounts Receivable issues:\n \n1. The ERA Worklist [RCDPE EDI LOCKBOX WORKLIST] option produces error:\n <UNDEFINED>GETPHARM+21^RCDPEWLP.\n \n2. When using the Receipt Processing [RCDP RECEIPT PROCESSING] option to \n reprocess an auto posted receipt, the message "This receipt cannot be\n processed - the receipt total does not match the EFT total for this EDI\n Lockbox receipt" is received when an EFT/ERA spans several receipts.\n\n
\nModify TOP bills foreign address handling\n\n
\nROUTINES FOR PRCA*4.5*67. PROVIDES AUDIT TRAIL FOR ALL DELETED\nTRANSACTIONS AND BILLS.\n\n
\n \nDescription\n \n12.) Status Listing For Bills [PRCAL STATUS LIST] report shall be \nmodified to incorporate reason for suspension.\n \n13.) Provide the ability to lock the option to update late payment \ncharges (Interest/Admin/Penalty Rates [PRCAF U ADMIN.RATE]) with a new\nsecurity key. \n \n14.) The system will allow the user to identify if the Bill of \nCollections letter applies to Veterans Beneficiary Travel (Form 1114).\n-----------\n \n15.) The system will print the Notice of Rights and Responsibilities \nwhen the Bill of Collections pertains to Veterans Beneficiary Travel.\n \n16.) VistA AR Software Package shall discontinue generation of the \nMailman message/bulletin, "ARDC Detail Report for MON/ YYYY", without \ninterrupting any other transfer data within ARDC.\n \n17.) The VistA AR Software Package shall allow the generation of a \nreport of bills containing the same information as the discontinued \nThe Chief Business Office (CBO) is requesting system enhancements to\n"ARDC Detail Report for MON/YYYY" with the following exceptions/ \nadditions:\n The report shall include current status bills (New Bill, Active, \n Returned for Amendment, Amended Bill, Open, and Suspended bills) \n only;\n \n The report shall include a column for the Fund number associated \n with each line item on the report; and \n \n The report shall include a column for the RSC associated with \nThe Veterans Health Information Systems and Technology Architecture\n each line item on the report.\n \n18.) Currently, when non-healthcare debt of $25 or greater is in a \ndelinquent status for 180 days, VistA transmits this debt to TOP \n(via AITC and DMC) for initiation of the standard collection process.\nTo maintain compliance with The DATA Act of 2014, the 180-day date \nparameter shall be changed to 120 days.\n \n19.) A new audit trail is needed for detailing events or transactions \nthat have occurred on healthcare debts referred for debt collection, to \n(VistA) Integrated Billing (IB), Accounts Receivable (AR), and \neffectively support Veterans and reconcile accounts.\n \n20.) VistA shall provide enhanced reporting capability, usability \nfeatures, and additional data elements for managing healthcare debts \nreferred for debt collection to improve VHA's ability to provide support \nto Veterans and manage accounts.\n \n21.) Create report to track stop/reactivate debts. VistA shall provide \na Stop/Reactivate report to identify healthcare debts that are placed \nin the corresponding status.\nOutpatient Pharmacy (PSO) software modules. \n \n22.) Improve automation in management of debt collection. VistA shall \nutilize existing functionality, such as List Manager, and other \nautomation capabilities to improve debt collection management"\n \n23.) The existing Medication Co-Pay Exemption Report [PRCAX CO-PAY \nEXEMPTION REPORT] shall be modified with the following field changes:\n Change PT ID from full Social Security Number (SSN) to LastN + \n 4SSN\n Add Rx#\n \n Add Drug Name (first 10 to 12 characters)\n Add Fill/Refill Date\n Add Effective Date of Exemption\n \n24.) A new Third Party Accounts Receivable category called \n'EMERGENCY/HUMANITARIAN REIMB.' shall be created in Accounts Receivables \nwith the insurer as the responsible party. \n \n25.) A new Third Party Accounts Receivable category called 'INELIGIBLE \nHOSP. REIMB' shall be created in Accounts Receivables with the insurer \nThe mission of the Department of Veterans Affairs (VA), Office of \nas the responsible party. \n \n26.) A one-character "Type" field shall be added to the Claims Matching \nReport that will indicate the third-party claim care-type ("I" for \nInpatient, "O" for Outpatient, "P" for Prosthetics, and "R" for \nPrescription\n[Rx]) on the report of third-party bills.\n \n27.) When a user generates a Claims Matching Report for a patient, all \nrecords for that patient are currently produced on the report. At \nInformation & Technology (OI&T), is to provide benefits and services \ntimes, users need to generate information regarding only certain types \nof care for a patient. The system shall allow the user to choose \nbetween producing a Claims Matching Report containing (1) all records \nfor a patient, or (2) only records of a certain care type ("I" for \nInpatient, "O" for Outpatient, "P" for Prosthetics, or "R" for \nPrescription [Rx]).\n \n28.) The Claims Matching Report, when exported, shall be in a line \nformat so that information on the report may be easily exported to \nMicrosoft Excel.\nto veterans of the United States Armed Forces. In meeting these goals, \n \n \n \nConcurrent Development / Dependencies:\n--------------------------------------\nN/A\n \n \nPatch Components:\n-----------------\nIMPORTANT INSTALLATION NOTE:\nOIT strives to provide high quality, effective, and efficient \n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\nInformation Technology (IT) services to those responsible for \n----------- ---- --------------------\nPRCA ARDC REPORT ROUTINE NEW\n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \nTemplates Associated:\nproviding care to the veterans at the point-of-care, as well as \n \nTemplate Name Type File Name (Number) New/Mod/Del\n------------- ---- ------------------ -----------\nN/A\n \nNew Service Requests (NSRs):\n----------------------------\n20150505 - Revenue Reporting Enhancements\n20150506 - Revenue Eligibility Enhancements\n20150507 - Revenue Operations Enhancements\nthroughout all the points of the veterans' health care. The VA depends\n \n \nPatient Safety Issues (PSIs):\n------------------------------\nN/A\n \n \nRemedy Ticket(s) & Overviews:\n-----------------------------\nN/A \non Information Management/InformationTechnology (IM/IT) systems to meet\n \nTest Sites:\n----------\nDurham VAMC\n \n \nSoftware and Documentation Retrieval Instructions:\n----------------------------------------------------\nPatches for this installation are combined in host file \nIB_2_568_PRCA_PSO_BUNDLE_T1.KID\nmission goals.\n \nInstallation of this host file should be coordinated among the packages \naffected since only one installation is necessary.\n \nThe patches are:\n \n IB*2.0*568\n PRCA*4.5*315\n PSO*7.0*463\n \n \n \nSites may retrieve the KIDS build in one of the following ways:\n \n(1) The preferred method is to FTP the files from \ndownload.vista.domain.ext\nwhich will transmit the files from the first available FTP server.\n \n(2) Sites may also elect to retrieve the patch directly from a specific\nserver as follows:\n \nThe overall FY16 HAPE Revenue Enhancement project has been further \n OIFO FTP ADDRESS DIRECTORY\n -------------- ------------------------ ------------------\n Albany ftp.fo-albany.domain.ext anonymous.software\n Hines ftp.fo-hines.domain.ext anonymous.software\n Salt Lake City ftp.fo-slc.domain.ext anonymous.software\n \n \nSites may retrieve documentation directly using Secure File Transfer \nProtocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following\nOI Field Offices:\ndivided into three sub-projects:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext\nSalt Lake City: fo-slc.domain.ext\n \nDocumentation can also be found on the VA Software Documentation \nLibrary at:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n \n-----------------------------------------------------------------------\nAccounts Receivable Technical Manual/Security Guide \n prca_4_5_tm+r0515.doc Binary\nAccounts Receivable Deployment, Installation, \n Back-Out, and Rollback Guide \n FY16RevenueARVIP_Deployment_Installation_Guide.doc Binary \n \n \n \nPatch Installation:\n----------------------------\nNSR #20150506\n \nPre/Post Installation Overview:\n-------------------------------\nThe post installation routine, PRCA315P, is not automatically deleted\nas part of the installation process. You may delete it after\ninstallation if you desire.\n \nPre-Installation Instructions:\n------------------------------\nN/A\nThe Revenue Eligibility Enhancements Project effort for the Chief \n \nInstallation Instructions:\n--------------------------\nThis process will install new and updated routines and other \ncomponents listed above. There is a post-install routine that will add \nentries to a number of files.\n \nThe patch will be released in conjunction with an Integrated Billing\npatch, IB*4.5*568, and an Outpatient Pharmacy patch, PSO*7.0*463.\n \nBusiness Office (CBO), bundles several NSRs with similar business \n ************************ NOTE ************************\n IF A USER IS ON THE SYSTEM AND USING THESE PROGRAMS \n AN EDITED ERROR WILL OCCUR. \n The patch should be installed when NO Outpatient \n Pharmacy users are on the system.\n ******************************************************\n \n Installation will take less than 1 minute.\n \n Suggested time to install: non-peak requirement hours.\nneeds into a single requirements document. Successfully addressing \n \n \n 1. Obtain the file IB_2_568_PRCA_PSO_BUNDLE_T1.KID\n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. Use Load a Distribution using IB_2_568_PRCA_PSO_BUNDLE_T1.KID when\n prompted to Enter a Host File name. You may need to append a\n directory name.\nthe requirements contained within this document will enable the \n \n 4. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter IB*2.0*568):\n a. Verify Checksums in Transport Global - This option will \n allow you to ensure the integrity of the routines that are \n in the transport global.\n b. Print Transport Global - This option will allow you to \n view the components of the KIDS build.\n c. Compare Transport Global to Current System - This option \n will allow you to view all changes that will be made when \nDepartment of Veterans Affairs (VA) to appropriately bill certain \n this patch is installed. It compares all components of \n this patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a \n backup message of any routines exported with this patch. \n It will not backup any other changes such as DD's or \n templates.\n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? \n NO//" respond NO.\n \nsubsets of billable events by correcting, automating, or enhancing \n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//" respond NO. \n \n \n \nPost-Installation Instructions:\n-------------------------------\nThere are no special tasks to perform after this patch installation.\ncurrent Veterans Health Information Systems and Technology Architecture\n(VistA) systems.\n \nThis patch is part of a multi-package build. There are three patches \nNSR #20150507\nThe Revenue Operations Enhancements Project combines serveral NSRs, \nas well. This effort enables the Department of Veterans Affairs (VA) \nto improve revenue operation functionality related to repayment plans, \nlate charge capture, bill suspension reasons, the billing of \ndeactivated providers, and the display of appeal rights and \nresponsibilities on the Veterans Beneficiary travel Bill of Collections\nform. Implementation of the proposed enhancements will make a \nsignificant positive impact on stakeholders and target users.\n \nassociated with the FY16 HAPE Revenue Enhancement project - IB*2.0*568,\nNSR #20150505\nThe Revenue Reporting Enhancements Project will enable the VA to \nimprove tracking and reporting of revenue, and will support revenue \nreporting business rules and guidelines.\n \n \nPRCA*4.5*315 patch enhancements, pertinent to the above NSRs, include:\n \n1.) By means of the new Enter / Edit Repayment Plan option, the user \nwill create the Repayment Plan by debtor. Note: The 'Enter / Edit \nPRCA*4.5*315 and PSO*7.0*463. All three patches are to be installed \nRepayment Plan' menu option name will replace the 'Set up Repayment \nPlan' menu option name.\n \n2.) On the Enter / Edit Repayment Plan option, if the AR Debtor has \nActive bills, the system will now display a selectable list of bills \nfor the debtor.\n \n3.) On the Enter / Edit Repayment Plan option, when displaying a list \nof Active bills for the Debtor, the system will display steps to the \nuser to set up the Repayment Plan.\ntogether as a bundle, IB_2_568_PRCA_PSO_BUNDLE_T1.KID\n \n4.) On the Enter /Edit Repayment Plan option, once a Repayment Plan \nhas been created or modified, the summary of the Repayment Plan is \ndisplayed.\n \n5.) On the Enter / Edit Repayment Plan option, the system checks to \nsee if a Repayment Plan has already been created for the Veteran. \n \n6.) On the Enter / Edit Repayment Plan option, when choosing to Edit \nthe Repayment Plan, all Active bills for the debtor will be displayed\n \nallowing the user to add new Active bills to the Repayment Plan as well\nas change the due date of first payment and/or the repayment amount due \non the Repayment Plan. \n \n7.) On the Enter / Edit Repayment Plan option, if the Debtor does not \nhave new Active bills that can be added to the Repayment Plan, the user \nwill proceed to identify the repayment amount due and/or repayment \namount due date on the Repayment Plan.\n \n8.) On the Enter / Edit Repayment Plan option, a designated identifier \n \nwill signify when an Active bill is part of a Repayment Plan. \n \n9.) On the Enter / Edit Repayment Plan option, the system will display \npreviously made payments to the Repayment Plan.\n \n10.) On the Enter / Edit Repayment Plan option, the User has the option \nto enter Debtor Comments during the setup process. \n \n11.) The AR Clerk will be able to select Suspended Type from the menu \nto display in the Status Listing For Bills [PRCAL STATUS LIST] report.\n\n\nThis patch addresses the following two issues:\n \n1. Ensure Tier Rate decreases do not flag non Tier Rate charges as\n duplicate\n \n2. Modify purging criteria for the weekly TCSP batch run\n \n3. Modify purging criteria for the weekly TOP batch run\n\n
\nPatch for builds 4 and 5 of ePayments MCCF project.\n\n
\n1. CS BATCH RUN: 5B MAIL MESSAGE HANDLING\n\n
\nThis patch addresses the following issue(s):\nhave any associated transactions in the AR TRANSACTION (#433) file.\n \n1. A <PARAMETER> error occurs when running the Accounts Receivable Nightly\nProcess Background Job [PRCA NIGHTLY PROCESS] when one of the records \nprocessed is locked.\n \n2. A <SUBSCRIPT> error occurs while running the Status Listing\nFor Bills [PRCAL STATUS LIST] option when an ACCOUNTS RECEIVABLE\n(#430) bill has a CURRENT STATUS (#8) of SUSPENDED and does not\n\n
\nThis patch addresses the following issues:\n \n3. Modify served messages from Treasury to not use the same work space as\n weekly batch run\n \n4. Ensure the cross-service date is reset for rejected recalls by Treasury\n \n5. Ensure TCSP bill scrub sets address node in file 430\n \n6. Ensure CS flag set for debtor is only cleared if deceased or scrubbed\n \n \n7. Ensure 5B records are sent to Treasury in every case except when \n Recall status is set on bill\n \n8. Fix CS reporting for IOP setup affecting other print options\n \n9. Update the Error Code file #348.5 with code additions/changes\n \n10. Correct bill Category codes to reflect 47 & 49 to skip bill processing\n1. Modify Cross-service bill foreign address handling\n \n2. Ensure that the telephone number in the IAI C2CA (Debtor Contact\n Information) adheres to the AITC and Artiva guidelines that the\n phone number (position 261-270) be 10 numeric and, if not, leave \n the field blank and also leave positions 260 (Contact Phone Type)\n and 275 (Contact Primary Phone) blank.\n\n
\nRegional Counsel Reconciliation\n\n
\n1. Bad Debt report (Allowance for Bad Debt and Contract Allowance)\n does not print for Fund due to incorrect entry in compiler\n\n
\nMCCF EDI TAS EPAYMENTS BUILD 3\n\n
\nAR Cross Servicing Patch. Contains two new reports, 2 new options to \nrun them and 4 new routines\n \n0-40 Percent SC Change Reconciliation Report (RCDMCR4A and RCDMCR4B)\nFirst Party Charge IB Cancellation Recon Report (RCDMCR5A and RCDMC5B)\n\n
\n1. Patient statement compilation issue\n \n2. Option 'Build CCPC Transmission batch' queued start time control\n\n
\nThis patch addresses an undefined error CARE+99^RCXVUTIL in the CBO Data\nExtract process of the Accounts Receivable Nightly Process Background\n[PRCA NIGHTLY PROCESS] option.\n\n
\nStatement Schedule Update:\nmonth.\nAs an Accounts Receivable Business Owner...\nI want To modify the day of the month that 16 specific sites are assigned \nin VistA.\n \nSites: 438, 501, 504, 542, 562, 565, 568, 621, 649, 656, 658, 664, 671, \n688, 740, and 756 ...\n \nSo that The workload is redistributed more evenly across the days of the \n\n
\nThis patch to Accounts Receivable contains new cross references and\na post init which fixes problems with a bills status and last date\nupdated (status).\n\n
\nAR Cross Servicing Patch. Contains two new reports, 2 new options to \nrun them and 4 new routines. Also will contain more things as B2 goes \nunderway\n\n
\nWhen a bill principal balance is auto-decreased to zero, any \nremaining Interest Balance, Administrative Cost Balance, Court Cost \nand Marshall Fee should be adjusted to zero.\n \nAlso, when a cancelled charge (decrease) from IB updates an AR bill that\nhas a 'SUSPENSED' status, the charge should be posted to the bill.\n\n
\n1. Modify Cost Center selection to pull from work file that ensures\n all cost centers related to a Fund Control Point are available for \n selection.\n \n2. All Cost Centers linked to a Fund Control Point are not checked for \n inactive status.\n\n
\nAccounts Receivable patch, PRCA*4.5*359, address the following issues:\n \n1. A subscript error, <SUBSCRIPT>UPDTMPB+12^RCDPENR1, is impacting the \n weekly Accounts Receivable (AR) Diagnostic Measures Statistical\n Reports for users.\n \n2. When editing debtor address information in the option Address \n Display/Edit [PRCA VEN BIL], the formatting of the phone number\n and zip code displayed is incorrect. \n\n
\nThis patch will address one issue:\n \n1. Failed text transaction setup in FILE 433\n\n
\nThis patch will address two issues:\n \n1. Bills were sent to TOP after the cross-service cutoff date 08/01/15.\n \n2. Ensure Exempt transaction for cancelled bill has DATE & TIME for Date \n Entered.\n\n
\nThere is one issue being fixed.\n \n1. The option 'PRCAL STATUS LIST' at times shows incorrect info for \n status type equals suspended.\n\n
\nThis patch will fix two issues: \n \n1. A patient name with two middle names do not appear correctly on\n a patient statement printed at CCPC.\n \n2. The weekly cross-service batch run does not create a proper text \n transaction for auto recalls for bills <$25.\n\n
\nePayments build 9\nupdated December 18, 2018\n\n
\nThis report captures detailed 1st party bill information for a specific\nveteran, within a user specified range of dates of service. This report\noutput requires screen size of 256 characters wide.\n\n
\nBackup of PRCA*4.5*377 on May 05, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of PRCA*4.5*375 on May 19, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe purpose of this patch is to address issues arising with\n1. Receipt transactions for a debit type EFT will be marked with\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\nN/A \n \n \n \nParameter Definitions Associated:\n \nParameter Name New/Modified/Deleted\n a new debit flag. These transactions will be subtracted from the\n-------------- --------------------\nN/A\n \n \nAdditional Information:\n-----------------------\n \nNew Service Requests (NSRs):\nN/A\n \n calculated receipt total, which may result in a negative receipt total.\n \nPatient Safety Issues (PSIs):\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\nN/A\n \n \nTest Sites:\n \n----------\n \n \n \nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\nN/A\n \nPre/Post Installation Overview:\n-------------------------------\n \n** IMPORTANT: Do not install this patch while the "Accounts Receivable \nNightly Process Background Job" [PRCA NIGHTLY PROCESS] is running **\n \nThis patch may be installed with users on the system although it is \nrecommended it be queued to run after normal business hours, but before \nthe Accounts Receivable Nightly Process Background Job starts, to minimize\npotential disruption to users. This patch will take less than 5 minutes to\ninstall. \n \nPre-Installation Instructions:\n2. When an EFT is removed from the system using the menu option\n------------------------------\nN/A\n \nInstallation Instructions:\n--------------------------\n \n 1. Choose the PackMan message containing this patch.\n \n 2. Choose the INSTALL/CHECK MESSAGE PackMan option.\n \n Remove Duplicate EFT Deposits, [RCDPE REMOVE DUP DEPOSITS], the\n 3. From the Kernel Installation & Distribution System Menu, select the\n Installation Menu. From this menu, you may select to use the\n following options. When prompted for the INSTALL NAME, enter\n the patch PRCA*4.5*364:\n a. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option will\n new field REMOVAL TYPE [.2] will be entered, after the removal reason \n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message containing the components of this patch. When \n prompted, select 'B' for Build, to back-up the routines and\n other components affected by this patch.\n \n \n 4. From the Installation Menu, select the Install Package(s) option\n text. The user must enter one of two codes from the set:\n and choose the patch to install.\n \n 5. When Prompted "Want KIDS to INHIBIT LOGONs during the install? \n NO//" respond NO. \n \n 6. When Prompted "Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//" respond NO.\n \n \nPost-Installation Instructions:\n \n-------------------------------\nN/A\n \nBack-Out/Roll Back Plan:\n------------------------\nPrior to installing the updated KIDS package, the site/region should have \nsaved a backup of the build in a mail message using the Backup a \nTransport Global [XPD BACKUP] menu option. The message containing the \nbacked-up build can be loaded with the "Xtract PackMan" function at \nthe Message Action prompt. The PackMan function INSTALL/CHECK MESSAGE is \nElectronic Fund Transfers (EFTs), received into VistA, that have been\n D DUPLICATE EFT\nthen used to install the backed-up build onto the VistA system.\n M MILLENIUM EFT\n \n The new field will show on the Duplicate EFT Deposits Audit report\n [RCDPE EFT AUDIT REPORT].\n \n \nThis patch will have no significant impact on disk space or journal file \nusage.\n \nsplit between VistA and CERNER as a result of the EHMR implementation.\nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n Sub-file Name (#) \n------------------------ ------------------------- --------------------\nAR BATCH PAYMENT (#344)\n TRANSACTION (#344.01) DEBIT/CREDIT FLAG (#9) NEW\nThis process may result in the receipt of debit EFTs, which need to be\n \nEDI THIRD PARTY EFT DETAIL (#344.31)\n REMOVAL TYPE NEW \n \nBulletins Associated:\n \nBulletin Name New/Modified/Deleted\n------------- --------------------\nN/A\n \ncorrectly identified and passed to the Financial Management System (FMS). \n \nDialogs Associated:\n \nDialog Name New/Modified/Deleted\n----------- --------------------\nN/A \n \n \nForms Associated:\n \n \nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\nN/A\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\nThe following features of the PRCA software will be affected by this \n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nN/A\n \n \nProtocols Associated:\npatch:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \n \nSecurity Keys Associated: \n \nSecurity Key Name\n-----------------\n \nN/A\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\n \n \nRemote Procedures Associated:\n\n
\nBackup of PRCA*4.5*382 on Jun 21, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n<Null subscript> error in RCRCREC2\n\n
\nBackup of PRCA*4.5*381 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of PRCA*4.5*387 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nBackup of PRCA*4.5*379 on Aug 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch implements the report that allows CPAC users to view first\nparty charges for patients with the High Risk of Suicide patient \nrecord flag.\n\n
\nE-Payments builds 10, 13 and 14. Accounts receivable patch.\n\n
\n This patch fixes two problems:\n help so it states 6 digits.\n \n NOIS CLE-0197-40420\n - When waiving part of a 5014/2431 bill's balance using the Partial\n Waiver option [PRCAC WAIVED PART], the software generates a Billing\n Document to be transmitted to FMS. Since only detailed bill transactions\n should be sent to FMS, this patch ensures that summary bill's waivers do\n not get transmitted to FMS.\n \n NOIS ISH-0297-40249\n - When creating a deposit ticket using the option, Create Deposit Ticket\n [PRCA CREATE DEPOSIT], the help text for entering a "?" at the prompt is\n inconsistent with the help text displayed when the user enters an invalid\n deposit ticket. When entering a "?" the help text states the ticket\n number must be 6 digits. When entering an invalid ticket number the help\n text states the ticket must be 6 characters. The patch has changed the\n\n
\n This patch will address 7 issues:\n to Treasury.\n \n 3. Weekly cross-service batch run is resending re-established bills to\n Treasury.\n \n 4. Control the rejection of a Vista bill recall transaction to Treasury \n to not reset the date sent to Treasury if bill not active status.\n \n 5. Correct the teleplone number format appearing on profile views.\n \n \n 6. The entry of all zeroes for telephone number is sending all\n zeroes to CS and rejecting.\n \n 7. Ensure re-established bills are sent if there is also an active Refer\n Return transaction on bill.\n 1. This patch will change the fields and number of days used in the debt\n referral calculations for Debt Management Center (DMC), Treasury\n Cross-Servicing Program (TCSP), and Treasury Offset Program (TOP) to \n ensure the debt time line is compliant with Veterans Health \n Administration (VHA) Policy and Statues.\n \n 2. Control the resending of recurrent rejected cross-service transactions\n\n
\nPatch PRCA*4.5*386 will address three issues: \n \n1. Cancelled charges should NOT appear on Exempt Reports\n \n2. The date of service for any I/P type of copayment should be \n based on the Admit date on Exempt Reports\n \n3. Urgent Care copayment charges should NOT appear on Exempt \n Reports\n\n
\nThe A&A Pension, Housebound Exempt Charge Reconciliation Report shows all \nbills containing charges with a distinct date of service on or after the\nco-payment exemption effective date for Veterans\n \nThe report captures any charges WITHOUT an IB status of cancelled, and \nWITHOUT an AR category of CC URGENT CARE and with an AR Status of Active,\nOpen, Suspended, Write-Off, or Collected/ Closed or ALL of these status'\nwith a date of service on or after the exemption effective date.\n\n
\nThis patch fixes the multiple "PRCA" entries in "C"\ncross-reference of the package file. There should be only\none PRCA prefix for the Accounts Receivable package. Nothing\ngets updated if there is only one package that has the PRCA\nprefix. Those packages that have the PRCA prefix and should\nnot, will have the prefix changed to PRCZ.\n\n
\nePayments release 16\n\n
\nPatch PRCA*4.5*402 fixes TRICARE Pharmacy Financial Management System \n(FMS) error issue.\n \nSites claimed that decrease adjustments for TRICARE Pharmacy bills cannot \nbe transmitted to FMS since no Billing Document (BD) code sheet is being \ngenerated.\n\n
\n1. Reset the 'hanging' bills sent to TOP after TCSP cutoff date 8-15-2015\n\n
\nPatch PRCA*4.5*411 will address one issue: \n \n1. Ensure ERA Worklist does not error when 'Deleted' Prescription \n encountered during ERA processing\n\n
\nPatch PRCA*4.5*395 UPDATES THE ARC INTERFACE FROM FTP TO SFTP\n\n
\nePayments release 18\n\n
\nPatch PRCA*4.5*408 will address two issues: \n \n1. Ensure re-referrals of rejected bills are sent to TCSP correctly\n \n2. Ensure all SSN# C2 U changes are not rejected by TCSP\n\n
\nThis patch fixes the multiple "PRCA" entries in "C"\ncross-reference of the package file. There should be only\none PRCA prefix for the Accounts Receivable package. Nothing\ngets updated if there is only one package that has the PRCA\nprefix. Those packages that have the PRCA prefix and should\nnot, will have the prefix changed to PRCZ.\n\n
\nCORRECTING REFUND/REIBURSMENT VALUE;CT BILLS\n\n
\nPatch PRCA*4.5*417 will address two issues: \n \n1. Ensure re-referrals of rejected bills are sent to TCSP correctly\n \n2. Ensure all SSN# C2 U changes are not rejected by TCSP\n\n
\nThis patch provides support for the Tricare billing program.\n\n
\nPatch PRCA*4.5*427 updates the Annual Interest Rate in the AR SITE \nPARAMETER(#342) file\n\n
\nePayments Build 19\n\n
\nUPDATE AR SO CHAMPVA 3RD PARTY CREATE BDS IN FMS\n\n
\nPatch PRCA*4.5*434 updates the Annual Interest Rate in the AR SITE \nPARAMETER(#342) file\n\n
\nePayments Build 20\n\n
\nPatch PRCA*4.5*435 addresses an issue where the fund and revenue source \ncode is not auto-populating for manual bills of collection.\n\n
\nThis patch addresses several E3Rs.\n\n
\nMCCF EDI TAS EPAYMENTS RELEASE 21\n\n
\n2025 Update for Annual Interest Rate in File #342 AR SITE PARAMETER\n\n
\nPatch PRCA*4.5*452 Addresses an issue where when using the Link Debtor To \nVendor (PRCA VENDOR LINK) option the returned value is erroneously \nstuffed into the wrong field/s of the VENDOR LINK(#340) file \n\n
\nThis patch will affect the accrual of interest/admin by charging\nthe interest/admin after the CCPC patient statements are printed in\nAustin instead of five days in advance.\n\n
\nUpdate to Cross-Servicing Stop Reactivate Report.\n\n
\nDisable CBO Extract which has been sunsetted.\n\n
\nRC RECONCILIATION/RCCPC SERVER ERRORS\n\n
\nThis Build contains the routines for PRCA*4.5*73\n\n
\nThe receivable code field will automatically be set to 'federal' for\n1080 and 1081 bills, and the user will be allowed to edit the receivable\ncode field during the audit process.\n\n
\nAccounts Receivable patch #39\n\n
\nWR06 TRICARE REJECTS\n\n
\nTAB IN CCPC PATIENT ADDRESS\n\n
\nThis patch will correct a problem with multi-divisional site's control\npoint selection. It will also remove the double prompting for control\npoint.\n\n
\nAR patch 95 - IRS Code Sheet Rejects\n\n
\nThis patch will correct a problem with the Category Listing for Bills\nreport.\n\n
\nPatch routine PRCAUDT to fix LEVEL error at AUDT+3.\n\n
\n90 DAY DMC SOFTWARE - QA VERSION #1\n\n
\nThis patch contains functionality for the new MCCF 5287 fund.\n\n
\nThis is the second patch for the new fund 5287. This is a followup\nto patch PRCA*4.5*90.\n\n
\ntest v4 of patch PRCA*4.5*43\n\n
\nNO COMPILED PROGRAM ERROR\n\n
\nThis patch will fix several problems with the enhancements to the new\nMCCR fund.\n\n
\nDATE SORTED PAYMENT REPORT\nThis patch contains the new 'Date Sorted Payment Report' [PRCAD DATE\nSORTED] option which is found on the 'Reconciliation Reports' [PRCAD\nRECONCILE MENU] menu. The report can be run as summary or detailed. \n\n
\nFISCAL YEAR NOT CHANGED IN AR\n\n
\nYear 2000 changes.\n\n
\nPATCH 100 - TEST VERSION 1\n\n
\nThis corrects the <UNDEF> error in V+4^PRCABP2\nthat occurs when a user tries to queue a 1080 to print.\nIt also corrects <UNDEF> error in V+4^PRCABP1 when a\nuser tries to queue a 1081 to print.\nThe following options will error:\nNew Bill (Enter), Display Pending Bill, and Approve/Print Pending Bill.\n\n
\nThis patch changes the Patient Transaction History to show 'Debtor\nComments' even if there had been no other activity on the account. (NOIS\nNJH-0198-20836)\n\n
\nRegional Counsel Interface\n \n\n
\nThis patch contains functionality for the Bad Debt Report and new\nMCCR fund 5287.\n\n
\nPatch 40 routine modifications\n\n
\nWrong appropriation for CHAMPVA on 215 report.\nAppropriation should be 3220 for CHAMPVA SUBSISTENCE\nand CHAMPVA THIRD PARTY.\n\n
\nPenalty charge will now be added to non-benefit debt that are delinquent.\nAlso, interest will not be decreased off of bills it was just added to.\n\n
\nQuantity (units) required in New Bill (Enter)\n\n
\nPRCA*4.5*117\n\n
\nNew IRS OFFSET LETTER 9/1/98\n\n
\nDecrease adjustments to CHAMPVA bills\n\n
\nWrite-off documents for tort feasor were being reported under \ntransaction type 04. It should be reported under transaction\ntype 23.\n \nWhen using the function $$CLO^PRCAFN to see when a bill has been closed \nout, that the "close-out" date gets changed to the date of the\nnew transaction if an old closed-out bill has been updated.\n\n
\nThis enhancement will exclude DMC referrals from the IRS offset process.\n\n
\nThis patch corrects the following error when transmitting CCPC statements:\n<UNDEF>ERROR+6^RCCPCML\n\n
\nThis build fixes the problem with adjustments to CHAMPVA THIRD PARTY not\ngoing to FMS.\n\n
\nRegional Counsel transmission problems.\n\n
\nThis patch will remove MISC vendor codes from the FMS Billing Documents\n(BDs). They will be replaced by either a vendor ID or a newly defined\ngeneric vendor ID, depending on the type of bill.\n\n
\nCCPC transmission problem and added disclaimer\n\n
\nCHAMPUS THIRD PARTY DECREASES\n\n
\nPatch for DMC functionality\n\n
\nThis patch will change the fiscal year on the WR and SV documents\ngenerated by the AR Data Collector on October 1 of each year.\n \nIt will also change the default fund of 0160A1 displayed on the\n215 report to the fund the user enters during the audit process.\n\n
\nThis build addresses two separate problems.\n1. DMC transmissions missing state.\n2. CCPC transmission message exceeding 32 k in size.\n\n
\nThis build will cause a warning message to appear when the user is\nentering a payment on a receipt and the payment amount is greater than the\noutstanding balance on a bill.\n\n
\n(AR) package: when a user views a 1081 vendor bill with multiple\nitems via the Display Pending Bill [PRCA BIL PRNT] option,\nthe date for each item doesn't show, and instead of showing\nthe total amount for each item, the total amount of the bill\nis displayed for each item.\n \n\n
\nPayments in full on bills referred to Regional Counsel.\n\n
\nThis patch fixes the following two problems:\n statement? NO// \n \nII. AR PRINT PROFILE GENERATES AN ERROR\n A. NOIS: BIG-1298-7023 / STX-1098-70478\n B. OPTION: Profile of Accounts Receivable [PRCAC PROFILE]\n C. ROUTINE: PRCAPRO\n D. DESCRIPTION/RESOLUTION\n 1. Users reported errors when printing from Profiles of Account\n Receivables after the instillation of PRCA*4.5*108. This occurs\n only when the reports are queued.\n \n 2. The variable PRCABN is not defined when the report is \n queued to print. This UNDEF occurs in routine PRCADR2.\n The variable PRCABN has been added to the ZTSAVE array.\n I. TYPO IN BILL COMMENT LOG MENU\n A. NOIS: WPB-0798-3028\n B. OPTION: Bill Comment Log [PRCA BILL COMMENT]\n C. ROUTINE: PRCAM\n D. DESCRIPTION/RESOLUTION\n 1. The word 'BREIF' has been changed to 'BRIEF'\n 2. Are you SURE this BREIF COMMENT should appear on the patient\n\n
\n This patch corrects a problem with AR Transaction Listing Report [PRCA\n REPT AR TRANSACTION LIST] option where 'terminated by fiscal office',\n 'terminate by compromise' and 'waived in full' types of transactions were\n showing the wrong amounts.\n\n
\nThis patch will add a new mail group that will receive the electronic\nreports generated by the AR Data Collector.\n \nThis patch will also change the logic in the Bad Debt Report to roll\nover the totals from the prior fiscal year instead of resetting the\nvalues to 0 at the start of each fiscal year.\n\n
\nThis BUILD corrects a problem with the revenue source code for CHAMPUS\nPATIENT, CHAMPUS THIRD PARTY and CHAMPUS bills. With these changes, the\nrevenue source code will be set correctly for inpatient, outpatient and\nother CHAMPUS bills.\n \nThis BUILD also changes the data dictionary for the FISCAL YEAR field in\nfile 433.\n\n
\nRECEIVABLE CODES PROMPT IS SUPPOSED TO APPEAR ON 1080/1081 BILLS ONLY\n\n
\nFixes the following:\n \n1. Account forwarded to DMC display in Account Profile.\n2. Status Listing for Bills option showing bills referred to regional\ncounsel on all statuses.\n3. When auditing a bill and bill is rejected for the FMS Vendor ID,\nfollowing bill will display same error.\n\n
\nPatch PRCA*4.5*130- Interest and Administration Charges Enhancement\n\n
\nThis build contains the changes to include the DFN in the CCPC\ntransmission.\n\n
\nThis build corrects several Y2K problems reported during testing.\n\n
\nAdd the vendor id MCCFVALUE to the CR, SV, and WR documents sent to\nFMS.\n\n
\nRoutine required for PRCA*4.5*49\n\n
\nThis patch will correct the problem with building the IRS pre-offset\ncode sheets.\n \n\n
\nThis build contains changes to RCAMINS1 for NOIS MEM-0699-71134 and PRCAFN\n PATIENT NAME OR BILL NUMBER (#.09) in the TRANSACTION multiple of the\n \n AR BATCH PAYMENT file (#344)\nfor NOIS RIC-0299-21543. It also updated the data dictionary for the\nfollowing fields:\n ORIGINAL AMOUNT (#3) in the ACCOUNTS RECEIVABLE file (#430)\n \n FY ORIGINAL AMOUNT (#430.01,7) in the ACCOUNTS RECEIVABLE fle (#430)\n \n BILL NUMBER (#.03) in the AR TRANSACTIONS file (#433)\n \n\n
\nThis patch merges the OIG extract with the AR Data Collector.\n\n
\nPatch install must be coordinated with changes to DMC/AAC databases.\nThird fix is to no longer exclude bills where the patient has active \ninsurance on the day that the receivable was created.\nSee line PROC(DEBTOR,QUIT)+37 in routine RCDMC90.\n\nFourth fix in routine RCDMC90 is an extrinsic function to check whether\nthe debtor's address is unknown or invalid. Based off of this check, an\nerror message is created indicating if the account was referred on the\nMonthly or Weekly updates to DMC. A zero balance is sent to DMC if the\nWeekly update was created. See line TOTAL+8.\n\nChange will extend the length of field separator called HOSPITAL ID on\nFifth fix in routine RCDMC90 is to check the validity of the phone number\nand to correct the phone number if it contains anything other than 7 or 10\nnumeric. See line TOTAL+17.\n\nRoutine RCDMC90S: beginning in PROC+8, added extrinsic function to check the \nvalidity of the debtor and code to generate an error MailMan message.\n\nRoutine RCDMC90U: At COMPILE+32, added a conditional quit in the FOR\nloop to ensure a proper end of file encounter.\n\nmonthly transmission from 6 characters to 10 characters. (The DMC field\nSecond change to RCDMC90U: Added ERROR subroutine section to generate a\nMailMan message that is called from routine RCDMC90 fourth fix.\n\ncalled HOSPITAL ID = ien of VistA's AR DEBTOR file [#340].)\n\nSecond fix is made to correct undefined error that can occur during the\nbuilding of the weekly transmission message. See line UPDATE+2 in routine\nRCDMC90.\n\n\n
\nThis is a maintenance patch resolving several AR NOIS entries.\n\n
\nAR cleanup of pointers to file 442.\nThis patch will clean up the data in the PAT REF # subfield of the\nFISCAL YEAR fields of files 430 Accounts Receivable and 433 AR Trans-\naction. It will also clean up the PAT REF # cross references.\nThe patch will queue the job in the background and will\nsend the patch installer a message when the job has run to completion.\n\n
\nThis patch addresses several NOIS messages.\n will have the mispelling of UNKNOWN corrected. \n NOIS COS-0499-43134\n \n 3. The loop in option Audit an Electronic Bill [PRCAA AUDIT] will not\nexit\n when an error is encountered due to FMS accounting elements or VENDOR ID\n missing. Instead, the loop through the bills will continue.\n NOIS WPB-1198-31810\n \n 4. The OBR report will not error with an UNDEF at BUILDRPT^RCFMOBR2 when\n \n looking for the Institution file entry for the site.\n MAR-0599-22714\n \n 5. The TRANSACTION PROFILE [PRCAC TRANS PROFILE] will show the correct\nperson in the PROCESSED BY field.\n GNH-0598-40732\n 1. RC Possible Referral Listing [PRCAL REFER DC] option with patch can\nnow\n be queued through TASKMAN if the option has the SCHEDULING RECOMMENDED\n field set in the option.\n NOIS MWV-1098-20422\n \n 2. The List of Patients with ADDRESS UKNOWN [RCAM ADDRESS UNKNOWN] option\n\n
\nThis patch contains functionality for the lockbox and the new\ndeposit/payment processing projects.\n\n
\nPatch to link AR debtor file (#340) with Patient Merge software.\n\n
\nThis KIDS build addresses NOIS MUR-0699-32403 REGIONAL COUNSEL SERVER\nPROBLEMS. It also addresses a problem with the date for the IRS code\nsheets identified in Y2K testing. It also addresses a problem with the\ncontrol point in the Set Up Old Bills option.\n\n
\nEnhancements to the A/R package to support FMS.\n\n
\nNATIONAL DRUG FILE V. 3.15 MAINTENANCE RELEASE\n\n
\nThis patch installs the data dictionary for the MEDICATION INSTRUCTION SHEETS\nfile (#54.7). It also installs the option to print an instruction sheet.\nData for the file is NOT included with the patch.\n\n
\nThis patch installs changes to the software to print Patient Medication\n \n 3. When being prompted for a drug, drugs that are inactive and\n drugs that are not linked to a Medication Instruction Sheet\n are not shown.\n \nInstruction Sheets.\n \n 1. Once a Medication Instruction Sheet is printed, the user is\n prompted for another drug rather than being returned to the\n menu system.\n \n 2. When being prompted for the number of copies, the default of\n one is shown.\n\n
\nThis patch installs changes to the National Drug File so that\nPatient Medication Instruction Sheets with incorrect information\nwill not be able to be selected for printing.\n\n
\nThis patch installs the mail group NDF DATA. This group will\nreceive messages as updates are made to the National Drug File.\nMembers of this group should include all people responsible\nfor maintaining the links between the local Drug file and the\nNational Drug File.\n\n
\nThis patch disables the printing of two Medication Instruction Sheets.\n\n
\n This patch will delete field #2 (*ROUTINE) from the MEDICATION ROUTES\n FILE #51.2. Also, data associated with this field will be deleted\n from the entries in file #51.2.\n\n
\nNATIONAL DRUG FILE V. 3.16 MAINTENANCE RELEASE\n\n
\nThis patch updates the links between NDF and Patient Medication Instruction\nSheets. Updates for the Medication Instruction Sheets are not included\nwith this patch.\n\n
\nThis patch contains the routine PSNPPIP, used to print Medication\nInformation Sheets. Enhancements to this routine provide the ability to\nprint Medication Information Sheets from within the List Manager actions\ncontained in Outpatient Pharmacy V. 7.0.\n\n
\nThis patch corrects a problem with some Drug-Drug Interactions\nnot being flagged or alerted to the user.\n\n
\nThis patch contains corrections to the routine ^PSNMRG, used to merge\ninformation from the NATIONAL DRUG file (50.6) into the DRUG file (#50).\nIt also contains a post install routine which corrects the data stored\nincorrectly due to the problem.\n\n
\nNATIONAL DRUG FILE V. 3.17 MAINTENANCE RELEASE\n\n
\nThis patch contains corrections to the routine ^PSNMRG, used to merge\ninformation from the NATIONAL DRUG file (50.6) into the DRUG file (#50).\nIt also contains a post install routine which corrects the data stored\nincorrectly due to the problem.\n\n
\nThis patch adds three new products: PRECISION Q-I-D (GLUCOSE) TEST\nSTRIP, PRECISION LINK, and PRECISION Q-I-D SENSOR,HAND HELD to the\nNATIONAL DRUG file (#50.6). This patch also updates the DRUG\nINGREDIENTS file (#50.416) to reflect these additional products.\n\n
\nThis patch updates the links between NDF and Patient Medication Instruction\nSheets. Updates for the Medication Instruction Sheets are not included\nwith this patch.\n\n
\nThis patch consists of a single routine PSNAPIS which contains several\nApplication Programmer Interfaces (APIs) for the NATIONAL DRUG file (#$50.6)\n \nThis file is being redesigned and these APIs are intended to allow a smooth\ntransition to the new structure.\n\n
\nThis patch consists of a single routine PSNAPIS which contains several\nApplication Programmer Interfaces (APIs) for the NATIONAL DRUG file (#$50.6)\n \nThis file is being redesigned and these APIs are intended to allow a smooth\ntransition to the new structure.\n\n
\nThis patch PSN*3.18*4 serves two purposes. First, it will put back\na VA Product Name in the VA PRODUCT NAMES multiple (#50.68) of NATIONAL\nDRUG file (#50.6) which was inadvertently missing in National Drug File\n(NDF) V. 3.18. It will put two entries in the DRUG INGREDIENTS file\n(#50.416) and will re-index the appropriate entries in files NATIONAL DRUG\n(#50.6), DRUG INGREDIENTS (#50.416), and DRUG INTERACTIONS (#56). The\nsecond problem this patch will fix will be to reset the third and fourth\npieces of each multiple level in 50.6 to prevent possible NDF matching\nerrors.\n\n
\nThis patch consists of a single routine PSNAPIS which contains several\nApplication Programmer Interfaces (APIs) for the NATIONAL DRUG file (#50.6).\n \nThis file is being redesigned and these APIs are intended to allow a smooth\ntransition to the new structure.\n\n
\nNATIONAL DRUG FILE V. 3.18 MAINTENANCE RELEASE\n\n
\nThis build contains patch PSN*4.0*2 which replaces seven routines\nthat were originally released with National Drug File (NDF) V. 4.0.\nThis patch also adds Inactivation Date fields to files 50.607, 50.608,\n50.609, 50.416, and 55.95. The data dictionary for a field in file 50.67\nwill change.\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \nThe input transform on the VUID field (#99.99) in the DRUG INGREDIENTS file\n(#50.416) became corrupted in such a way that editing that field would cause\na syntax error. That field is not edited at VAMCs. This patch corrects\nthe syntax of that input transform.\n \n\n
\n \nUnder certain circumstances, if an entry in the VA PRODUCT file (#50.68)\nwas reactivated - that is if the INACTIVATION DATE field (#21) was deleted -\nthis deletion was not captured in the VA FileMan audits and therefore was\nnot transmitted to the field. The cause of this problem has been removed.\nThis patch corrects those entries which have an inactivation date but\nshould not.\n\n
\n \nDRUG INTERACTION file (#56) involving these locally added ingredients.\nIf the locally added ingredients have been overwritten, these interactions\nwill check for ingredients other than those indicated by the name of the\ninteraction.\n \nThis patch performs six functions.\n \n1. It creates a new style cross-reference on the NAME field (#.01) and the\n PRIMARY INGREDIENT field (#2) of the DRUG INGREDIENTS file (#50.416). \n This new cross-reference replaces the old "P" cross-reference on the\n \n NAME field (#.01). The "P" cross reference was not working properly\n and included entries that should not have been referenced. This\n corrects the Patient Safety Issue PSI-05-008.\n \n2. Any entries in the DRUG INGREDIENTS file (#50.416) with an internal\n entry number (IEN) greater than that of the last nationally entered\n ingredient will be deleted. These would be locally entered ingredients\n that would eventually be overwritten with national ingredients released\n with NDF Data Updates.\n \nIt has been noted that several sites have made local entries in the DRUG\n3. Any entries in the DRUG INTERACTIONS file (#56) which have ingredients\n pointing to these deleted locally entered ingredients will be deleted.\n \n4. Any entries in the DRUG INTERACTIONS file (#56) which point to ingredients\n other than those indicated by the name will be deleted. These would \n be interactions created with a locally entered ingredient that was\n subsequently overwritten by a national ingredient.\n \n5. A mail message with the subject INGREDIENTS AND INTERACTIONS DELETED\n will be sent from NDF MANAGER to members of the mail group NDF DATA,\nINGREDIENTS file (#50.416). This should not have been done. Patch\n holders of the PSNMGR security key, and the person installing the\n patch. This message lists deleted ingredients, interactions deleted\n because they pointed to deleted ingredients, and interactions which\n pointed to ingredients other than those indicated in the name. In\n the last case, both the name (containing the original ingredients)\n and the current ingredients are displayed.\n \n6. The GMR ALLERGY field (#1) and the DRUG INGREDIENT field (#.01)\n of the DRUG INGREDIENTS multiple field (#2) in the PATIENT ALLERGIES file\n (#120.8) and the DRUG INGREDIENT field (#.01) of the DRUG INGREDIENTS\nPSN*4*89 changed the data dictionary of that file to prevent further\n multiple field (#2) in the GMR ALLERGIES file (#120.82) point to the\n DRUG INGREDIENTS file (#50.416). Any entries in these fields that\n point to ingredients that were deleted as described in item 2 above\n will be deleted. In addition, the selection of drug ingredients in the\n PATIENT ALLERGIES file (#120.8) should allow the selection of only\n primary ingredients. Any entries that point to ingredients that are\n not primary ingredients will be repointed to the proper primary\n ingredient.\nadditions. Some of these local entries may have already been overwritten\nby national entries.\n \nIt has also been noted that some sites have added local entries in the\n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe post-install routine for this patch, PSN106P, deletes existing\nentries in these files, loads the new data, and rematches entries in\nthe VA PRODUCT file (#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nDuring the installation of patch PSN*4*107, certain cross references in\nthe DRUG INTERACTION file (#56) were not properly deleted. This has\ncaused some problems with the installation of day update patch PSN*4*114.\nThis patch corrects that problem.\n\n
\nDRUG INTERACTION REPORT NOT SHOWING INACTIVATION DATE\n\n
\nThis NATIONAL DRUG FILE (NDF) patch is part of the Patient Financial\nreplacement system. The project consists of the implementation of the\nbilling replacement system, business process improvements, and\nenhancements to VistA to support integration with the COTS billing\nreplacement system. Significant changes to VistA legacy systems and\nancillary packages are necessary.\n \nSome of the PFSS software components are not operational until the PFSS\nOn/Off Switch, distributed with patch IB*2*260, is set to "ON". The\nability for the local site to set the switch to "ON" will be provided at\nthe appropriate time with the release of a subsequent Integrated Billing\nServices System (PFSS) project. PFSS patches are being released on various\npatch.\n \nFor more information about the PFSS project, review the documentation\naccompanying this patch and refer to the following website:\nhttp://vista.domain.ext/billreplace/.\n \n \nFunctional Description:\n=======================\nThe Charge Description Master (CDM) is an industry standard financial tool\nschedules. Some patch functionality will not be active until a new PFSS\ncommon to all commercial billing systems and used in virtually every\nprivate hospital. The CDM is a comprehensive listing of all services\nperformed, drugs supplied, or supplies provided in a particular hospital\nalong with the value of those services/drugs/items, or charge amounts.\nEach of these entries are represented by a Charge Code, and the Charge\nCode is made up of a Department Code and Service Code. The Charge Code for\nPharmacy will be the Department Code 160 concatenated with the assigned\nService Code for the drug. The Department Code 160 will not be stored in\nany files and the Service Code will be established/approved by a central\nCDM Change Control Board (CCB). The implementation of the COTS billing\nswitch is activated during final implementation. PFSS will initially be\nsystem requires the VA PRODUCT file (#50.68) to link the service master\nService Code to every Pharmacy prescription fill or refill. Pharmacy will\ncreate and populate a Service Code (in the 600,001 - 699,999 range) for\neach entry in the VA PRODUCT file (#50.68). Initially, the Service Code\nwill be populated by this patch and subsequently the CDM CCB assigned\nService Codes will be distributed as data update patches within the NDF\nreleases.\n \n \nTechnical Description:\nimplemented at select pilot sites ONLY.\n======================\nThis NDF patch PSN*4*103 provides the following functionality needed to\nsupport the PFSS project:\n \n1. A new SERVICE CODE field (#2000) was added to the VA PRODUCT file\n (#50.68).\n2. A Post-install routine that initially populates the new SERVICE\n CODE field (#2000) for every entry in the VA PRODUCT file (#50.68) with\n a six digit number to be within the range 600001-699999. The logic\n comprises of the Internal Entry number (IEN) padding it with zeroes as\n \n needed and adding a "6" on the front to make up a six digit number.\nThe purpose of the PFSS project is to prepare the Veterans Health\nInformation Systems and Technology Architecture (VistA) environment for\nthe implementation of a commercial off-the-shelf (COTS) billing\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates three mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis patch updates data for the national drug file application.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates three mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates three mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n change those entries to the corresponding primary ingredients.\n \n********************************NOTE***********************************\nThe routine included in this patch will not be run when the patch is\ninstalled. It will be called as part of the post-install during future\ndata update patches.\n***********************************************************************\n \n \n1. Certain entries in the DRUG INTERACTION file (#56) may have been\n created using ingredients that are no longer primary ingredients.\n The routine included in this patch will replace those ingredients\n with the corresponding primary ingredients.\n \n2. Certain entries in the PATIENT ALLERGIES file (#120.8) may include\n non-primary ingredients. The routine included in this patch will\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nAPAP 500MG/DM 10MG/DOXYLAMINE 6.25MG/PSEUDEFED 30MG/15ML LIQUID\nATROPINE 2MG/PRALIDOXIME CL 300MG AUTO INJECTOR (MARK I)\nCHLORHEXIDINE GLUCONATE 0.12% RINSE,ORAL\nCLOVE OIL\nCOBRA POWERFUL MEN'S PREFORMANCE ENHANCER CAP/TAB\nDRESSING,AQUACEL AG 2IN X 2IN C#403706\nHYDROXYCUT ADVANCED WEIGHT LOSS FORMULA, EPHEDRA-FREE\nMONONESSA TAB,28\nRELACORE STRESS REDUCER/MOOD ELEVATOR\nTABACCO\nUnder certain circumstances, entries in the ACTIVE INGREDIENTS multiple\nTOTAL LEAN EPHEDRA-FREE CAP/TAB\nTRACE METALS ADDITIVE INJ\n \nThis patch also makes the VUID field (#99.99) in the DRUG INGREDIENTS\nfile (#50.416) uneditable.\nfield (#14) in the VA PRODUCT file (#50.68) were not being deleted when\nthey should have been. Patch PSN*4*78 corrected the flaw in the data\nupdate process for subsequent releases. This patch deletes those entries\nthat should have been deleted by updates prior to patch PSN*4*58.\n \nThe products involved are\n4-MIXED TRACE ELEMENTS INJ\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\nThe option Inquire to VA Product Info For Local Drug [PSNLOOK] displays\nthe associated Patient Medication Information Sheet (PMIS) entry. If a\ndrug is selected that does not have a link to a PMIS, the PMIS information\nfrom the previous drug is displayed. This patch eliminates the problem by\ndeleting the appropriate variable prior to gathering PMIS information.\nThis patch also corrects the spelling of the MANUFACTURER field (#3) in\nthe NDC/UPN file (#50.67).\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nThe "T" cross reference on the TRADE NAME field (#4) in the NDC/UPN file\n(#50.67) currently stores only the first thirty characters of the field.\nDevelopers of the ADVERSE REACTION TRACKING application have requested\nthat this cross reference store the entire field. This patch accomplishes\nthat change.\n\n
\n \nNDF DATA mail group, holders of the PSNMGR security key, and the\ninstaller of the patch.\nNOTE: The message is not sent across the network from a test account. It\nis sent only to local recipients.\nThe option Enter/Edit Local Drug Interaction [PSS INTERACTION LOCAL ADD]\nallows sites to make local entries in the DRUG INTERACTION file (#56).\nWhen this option is invoked a message is sent to the mail group\nG.NDF SUPPORT@ISCPNDF.ISC-BIRM.DOMAIN.EXT. During the period 26 October 2006\nthrough 27 February 2007, a problem with the network configuration caused\nthese messages not to be transmitted. This problem has been corrected.\nThis patch transmits a list of all interactions that were entered locally\nduring that time period. That list is also send to members of the\n\n
\nThe words information and page in the header of patient medication\ninstruction sheets (PMIs) contain improper characters when printed in\nSpanish. This patch corrects that defect.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\nPatch PSN*4*148 inadvertently deleted the GCNSEQNO field (#11) for four\nThis patch restores those fields.\nentries in the VA PRODUCT file (#50.68). This field provides mapping to\npatient medication instructions sheets. The four entries involved are:\n \nDIGOXIN (LANOXIN) 0.125MG TAB\nDIGOXIN (LANOXIN) 0.25MG TAB\nDIGOXIN 0.125MG TAB,UD\nDIGOXIN 0.25MG TAB,UD\n \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nUndefined error occurs when running the Local Formulary Report \n[PSNFRMLY]. This happens when there is erroneous data in the Drug file \n(#50).\n\n
\nThis patch updates the data for patient medication instruction sheets.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nUnder some circumstances inactivation dates for entries in the DRUG\nINGREDIENTS file (#50.416) were not being transmitted to the field. This\npatch updates entries in those fields with the proper inactivation dates.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nindicate that according to VHA Directive 2005-044 the data dictionaries\nof these files must not be changed.\n"AMASTERVUID" cross references were created on the MASTER ENTRY FOR VUID\nfield (#99.98) in the DRUG INGREDIENTS (#50.416), VA DRUG CLASS (#50.605),\nVA GENERIC (#50.6), and VA PRODUCT (#50.68) files. These cross\nreferences were not properly created. New style cross references were\ncreated to correct the problem. This patch removes the obsolete cross\nreferences and deletes the incorrect entries in the cross reference.\n \nThis patch also changes the file description for these four files to\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis patch updates data for the national drug file application.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis patch will fix an issue where the Local Formulary Report\ncannot be sent to a spooled device. \nIt will also fix the NDF option of the Inquire to National \nFile so it displays Exclude Drg-Drg Interaction Ck.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nholders of the PSNMGR key, members of the NDF DATA mail group, and the\ninstaller of the update.\nThis patch creates a protocol, PSN NEW CLASS, which will be invoked during a\ndata update if any entries in the VA PRODUCT file (#50.68) have\nbeen assigned a new VA DRUG CLASS.\n \nThe protocol will be used to update ancillary applications when a change\nis made to the VA Drug Class assigned to a VA Product.\n \nThe protocol also sends a message titled "Products with changed classes" to\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch enhances the functionality of two components (DIC and IX) in\n VA DRUG CLASS (#50.605)\n \nThis patch adds these two files to the supported file list:\n \n NDC/UPN (#50.67)\n VA GENERIC (#50.6)\n \nInactivation Date screening logic for the standardized files (DRUG \nINGREDIENTS (#50.416), VA GENERIC (#50.6), and VA DRUG CLASS (#50.605))\nwill now use the SCREEN^XTID call, which utilizes the VUID inactivation\nthe PSNDI routine.\ndate. The Inactivation Date screening for the non-standardized files\n(NDC/UPN (#50.67) and DRUG INTERACTION (#56)) will be based on their\nVistA inactivation date fields. Prior to this patch, the screening for the\nDRUG INGREDIENTS (#50.416) File was based on the VistA inactivation date\nfield, and prior to this patch there was no Inactivation Date screening \nfor the VA DRUG CLASS (#50.605) file.\n \nFor further information regarding this API, please see FORUM DBIA (Data \nBase Integration Agreement) 4554.\n \n \n**NOTE** These APIs kill DIC("S") upon entry. Also, DIC("S") will remain\ndefined after a call if the calling application passes in an inactive\ndate.\nPSNDI is an existing API (Application Programmer Interface) for \nreplicating FileMan calls. Prior to this patch, this API supported these\nfiles:\n \n DRUG INGREDIENTS (#50.416)\n DRUG INTERACTION (#56)\n\n\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nNOTE: This patch is part of NDF Data Update FY09 #5, which is comprised\nof two patches, PSN*4*190 and PSN*4*191.\n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch is being released in conjunction with Pharmacy Data Management\nThis patch makes some changes to the National Drug File package that must \nbe in place prior to the install of patch PSS*1.0*129. The National Drug\nFile changes included in this patch are:\n \n1) Exports the Data Dictionary for the new OVERRIDE DF DOSE CHK EXCLUSION\n (#31) Field of the VA PRODUCT (#50.68) File.\n2) Populates the new OVERRIDE DF DOSE CHK EXCLUSION (#31) Field of the\n VA PRODUCT (#50.68) File with data.\n3) Modifies the PSNAPIS Application Programmer Interface (API) to return\n data from the new OVERRIDE DF DOSE CHK EXCLUSION (#31) Field of the\npatch PSS*1.0*129. Together, these patches provide the functionality\n VA PRODUCT (#50.68) File. A new OVRIDE Line Tag has been added to\n return this information. See Database Integration Agreement (DBIA) 2531\n for more information.\n4) Modifies the INQUIRE TO VA PRODUCT INFO FOR LOCAL DRUG [PSNLOOK] option\n and the INQUIRE TO NATIONAL FILES [PSNACT] option to display the data\n in the new OVERRIDE DF DOSE CHK EXCLUSION (#31) Field of the VA PRODUCT\n (#50.68) File. If the value of the new field is "YES", a message will\n be displayed to inform the user of the override significance. This\n field works in conjunction with the new EXCLUDE FROM DOSAGE CHECKS\n (#11) Field of the DOSAGE FORM (#50.606) File, which is being released\nneeded to prepare for the release of Pharmacy Re-Engineering (PRE) V. 0.5,\n in patch PSS*1.0*129.\n5) This patch makes these corrections to the INQUIRE TO VA PRODUCT\n INFO FOR LOCAL DRUG [PSNLOOK] option:\n a) Sometimes the Active Ingredients would not display.\n b) When the Active Ingredients did display, the Strength\n that displayed next to the Active Ingredient was not the\n Strength of the Active Ingredient, it was the Strength\n of the VA Product.\n c) The Drug Unit was not always displaying.\n d) Only the CS FEDERAL SCHEDULE code was displaying, and not\nwhich will change the current Pharmacy Order Checking system from using\n the text.\n e) When displaying the Active Ingredients, the text (Primary)\n will no longer display next to an Active Ingredient that is a\n Primary Ingredient, and the Primary Ingredient will now display\n if the Ingredient of the VA Product has a Primary Ingredient.\n6) This patch makes these corrections to the Inquire to National Files \n [PSNACT] option:\n a) Only the CS FEDERAL SCHEDULE code was displaying, and not\n the text.\n b) The National Formulary Restriction display was being truncated\nthe data stored in VistA to using data from the First DataBank (FDB)\n after one line if was two or more lines in length.\ncommercial database system. All of the new functionality needed to do the \nset-up work is included in patch PSS*1.0*129. The PSS*1.0*129 patch also \nreferences the documentation needed for the set-up work.\n \n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \nNOTE: This patch is part of NDF Data Update FY09 #5, which is comprised\nof two patches, PSN*4*190 and PSN*4*191.\n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n This patch corrects an undefined error in the Local Drug File Report\n [PSNLDG] option.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis build contains the National Drug File enhancement patch. It\nincludes routines, a partial data dictionary, as well as print templates.\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n \n2. In some cases, the header node of the ACTIVE INGREDIENTS multiple\nfield (#14) in the VA PRODUCT file (#50.68) was not being set. This\npatch sets those nodes.\n \n3. The write and delete protection on the DRUG UNITS file (#50.607) was\nnot set. This patch sets those protections.\n1. National Drug File data update patches make a call to an ADVERSE REACTION\nTRACKING routine, UPDATE^GMRAUTL2, to update the PATIENT ALLERGIES file\n(#120.8) when entries in the VA PRODUCT file (#50.68) are assigned to a\nnew class. Consolidated Mail Outpatient Pharmacies (CMOPs) typically do\nnot have the ADVERSE REACTION TRACKING application installed, so this call\ngenerates a <NOROUTINE> error. It causes no problems with the update\nprocess but it is an irritation. This patch adds a check before\ncalling this routine.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis patch is part of FY09-Q1 Enhancement release and should be installed\n - Hidden action (OTH) - MI Print Medication Instructions.\nalong with OUTPATIENT PHARMACY (OP) V. 7.0 patch PSO*7*326. It is a\nrequired patch for PSO*7*326.\n \nThis Enhancement is related to Patient Safety Issue PSI-07-090 (PSPO #543)\nand Remedy Ticket #189923. The Social Security Number (SSN) was removed\nfrom the Integration Control Registration (ICR) #2261, which is related to\nthe following OP report option:\n Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nCMOP, and products for which the national formulary restriction has\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\n\n
\n \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis patch provides updates to data in several of the files associated\nUPDATED INTERACTIONS, lists interactions that have been added, edited, or\ninactivated. The third, with the subject DRUGS UNMATCHED FROM NATIONAL\nDRUG FILE, lists entries in the DRUG file (#50) which have been unmatched\nfrom NDF. The fourth, with the subject INTERACTIONS and ALLERGIES\nUPDATED, lists interactions and allergies which have been changed because\nthey were created with ingredients that are no longer primary ingredients.\nwith the National Drug File (NDF) application. This patch generates four\nmail messages. All are sent from NDF MANAGER to members of the NDF DATA\nmail group, holders of the PSNMGR security key, and the person installing\nthe patch. The first message, with the subject DATA UPDATE FOR NDF, lists\nnew products, CMOP ID (if one exists), dispense units, and associated\nNDCs, products for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which the\nnational formulary restriction has changed. The second, with the subject\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch corrects erroneous drug interaction names.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch will create the "AC" cross reference on the PARENT CLASS field \n(#2) of the VA DRUG CLASS file (#50.605).\n \nThe new cross reference is utilized by the Patients on Specific Drug(s) \nMultidivisional Enhancements patch PSJ*5*214, a Class III to Class I \nconversion project.\n \nWith the "AC" cross reference, a user can identify all child drug classes \nthat belong to a selected parent class.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis build contains routines and options for the National Formulary\nIndicator enhancement patch.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nIn preparation for printing FDA Medication Guides, this patch adds a new\nNational Drug File application (NDF) to return an FDA Medication Guide link.\nThe call is S <variable>=$$FDAMG^PSNAPIS(ien).\n \nThis patch also provides a new Remote Procedure Call that will be used by\nsubsequent Outpatient Pharmacy and NDF functions to display FDA Medication\nGuides. The functions to utilize the new RPC will be provided in patches\nplanned for release at a later date. The RPC is named\nPSN FDA MED GUIDE PRINT QUEUE.\nfield, FDA MED GUIDE (#100) to the VA PRODUCT FILE (#50.68).\nThis patch does not enter data into this field. Data is entered into this\nfield as part of the monthly NDF Data Update patches. \n \nThis patch also adds a new option, Display FDA Medication Guide\n[PSN MED GUIDE], to the National Drug File Menu [PSNMGR].\n \nThis patch also creates a new application programmer interface (API) for the\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch is being released in preparation for the Supra-Therapeutic\n Dosage Form/Dispense Unit (Default) or if you want to control the\n Possible Dosage auto-creation process for the Dispense Drugs\n matched/re-matched to this VA Product.\n \n YES - Possible Dosages will be auto-created based upon Dosage\n Form/Dispense Unit combination (Default).\n NO - Possible Dosages will be auto-created according to the rule set\n by the POSSIBLE DOSAGES TO CREATE (#41) and PACKAGE (#42) fields.\n \n2. POSSIBLE DOSAGES TO CREATE field (#41)\nDosages project. It contains the following 3 new fields that are being\n \n Field Description:\n -----------------\n Indicate which Possible Dosages or if no Possible Dosages should be\n auto-created for Dispense Drugs matched/re-matched to this VA Product.\n This field is used only if the CREATE DEFAULT POSSIBLE DOSAGE field\n (#40) is set to 'NO'.\n \n N - No Possible Dosages are auto-created for Dispense Drugs matched\n to this VA PRODUCT entry during the match/re-match process.\nadded to the VA PRODUCT file (#50.68):\n O - Only 1x Possible Dosage is auto-created for Dispense Drugs\n matched to this VA PRODUCT entry during the match/re-match\n process.\n B - Both 1x and 2x Possible Dosages are auto-created for Dispense\n Drugs matched to this VA PRODUCT entry during the\n match/re-match process.\n \n3. PACKAGE (#42)\n \n Field Description:\n \n -----------------\n Indicate the Package(s) use for the Possible Dosage(s) auto-created.\n This field is used only if the CREATE DEFAULT POSSIBLE DOSAGE field\n (#40) is set to 'NO' and the POSSIBLE DOSAGES TO CREATE field (#41) is\n either set to 'O' or 'B'.\n \n I - Possible Dosages auto-created for Dispense Drugs\n matched/re-matched to this VA PRODUCT entry will be available\n for the Inpatient application only.\n O - Possible Dosages auto-created for Dispense Drugs\n1. CREATE DEFAULT POSSIBLE DOSAGE field (#40)\n matched/re-matched to this VA PRODUCT entry will be available\n for the Outpatient application only.\n IO - Possible Dosages auto-created for Dispense Drugs\n matched/re-matched to this VA PRODUCT entry will be available\n for both, Inpatient and Outpatient applications.\n \nIn addition, a post-install routine will run to update the CREATE DEFAULT\nPOSSIBLE DOSAGE field (#40) for every entry in the VA PRODUCT file \n(#50.68) with the default value of YES. The post-install routine will be\nautomatically deleted from the system upon completion of the installation.\n \n \nUpdates to these new fields will happen automatically via the monthly\nNational Drug File (NDF) Data Update patches.\n Field Description:\n -----------------\n Indicate whether Possible Dosages should be auto-created based on\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch corrects null subscript errors reported in NOIS PTH-0300-20463.\nThis patch corrects false NDF matching information reported in NOIS\nPTH-0300-20981.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch corrects erroneous entries in the DRUG IDENTIFIER field (#1)\nin the DRUG INGREDIENTS File (#50.416).\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch contains software modifications to the National Drug File (NDF)\n . Patient decision-making should be advised by information about a known\n \n Please wait... \n \n The system is unable to display FDA Med Guide automatically.\n \n The FDA Medication Guide will not automatically open on Thin Client and some\n types of encrypted sessions. If you do not believe this is the reason contact\n your local technical support for assistance.\n \n You can copy/paste the link above into your browser's address bar to retrieve\n serious side effect with a product, or \n the FDA Medication Guide.\n \n Enter RETURN to continue, '?' for HELP, or '^' to exit: ?\n \n When unable to get the FDA Medication Guide to display, review the following\n suggestion(s) for troubleshooting potential problems:\n \n 1) The browser did not open automatically. This may be due to the following:\n - You might be connected to VistA via Thin Client or an encrypted session\n that prevents the FDA Med Guide from automatically displaying. Please\n . Patient adherence to directions for the use of a product is essential\n copy and paste the URL link below into your browser's address bar to\n retrieve the FDA Medication Guide:\n \n vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_Lotion_(Generic)_(2008).pdf\n \n - The computer might not have the required Java software component\n installed or the software might not be functioning properly. Please,\n contact technical support for assistance.\n \n 2) When doing a copy/paste of the link into the browser's address and an HTTP\n to its effectiveness. \n 404 - File Not Found error is received. This may be due to the following:\n - A common issue exists when the link is displayed in two lines in the\n terminal screen. When you copy both lines at the same time and paste it\n into the browser's address, the second line is ignored by the browser\n resulting in a 'broken' link. To resolve this issue, copy and paste one\n line at a time from the terminal screen into the browser's address to\n make sure the complete link is used.\n - The FDA Medication Guide Server may be down at the moment. Please, wait\n a few minutes and try again. If the problem persists, contact technical\n support for assistance.\n \n \n 3) The browser opened automatically, however you receive an HTTP 404 - File\n Not Found error. This may be due to the following:\n - The FDA Medication Guide Server may be down at the moment. Please, wait\n a few minutes and try again. If the problem persists, contact technical\n support for assistance.\n \n \n If a user tries to use this option for a medication that does not have an FDA\n Medication Guide on file, the following message will display:\nThe features in the FDA Medication Guides project are being delivered in\n \n Select VA PRODUCT NAME: ALLO\n 1 ALLOPURINOL 100MG TAB \n 2 ALLOPURINOL 100MG TAB,UD \n 3 ALLOPURINOL 300MG TAB \n 4 ALLOPURINOL 300MG TAB,UD \n 5 ALLOPURINOL NA 500MG/VIL INJ \n CHOOSE 1-5: 1 ALLOPURINOL 100MG TAB \n \n There is no FDA Medication Guide associated with this medication.\nincremental releases. This patch is part of the Increment 2 release. The \n \n Enter RETURN to continue, '?' for HELP, or '^' to exit: ?\n \n When unable to get the FDA Medication Guide to display, review the following\n suggestion(s) for troubleshooting potential problems:\n \n 1) If no FDA Medication Guide exists for a product that you believe should\n have one, confirm that one is required by visiting the FDA website\n (www.fda.gov). If one is required, log a support ticket to request its\n addition. Please understand that there may be a delay between the time\nfeatures included in this release are:\n that a new Medication Guide is posted to the FDA website and when it is\n made available in VistA through a National Drug File data update patch.\n \n \n Note: This option requires a Java software component to be installed on\n ---- the user's computer. This software will be released as part of this\n project. Please, refer to the project Release Notes and Installation\n Guide documentation for further information.\n \n \n \n B. The length of the FDA MED GUIDE field (#100) in the VA PRODUCT file\n (#50.68) is being modified from 245 characters to 100 characters. The \n field will now be used to store only the PDF file name of the FDA \n Medication Guide rather than the complete link, which also had the web\n server URL. The web server URL is now being stored on a new field called \n FDA MED GUIDE SERVER URL (#100) in the PHARMACY SYSTEM (#59.7) file,\n which is introduced by patch PSS*1*158.\n . Establishment of a Server Repository for FDA Medication Guides within \nV. 4.0 application to support the FDA Medication Guides project. The \n the VA network.\n \n . Updates to 900+ entries in the VA PRODUCT file (#50.68) to store the \n corresponding FDA Medication Guide document name will be provided via\n the NDF Monthly Data Update patches.\n \n . Introduction of a PC based Java software component to enable the\n automatic retrieval of an FDA Medication Guide from within VistA. The\n software does not require any direct user interaction. It works as a \n bridge between VistA and the PC where it is installed. The software \nproject objective is to allow pharmacy staff to retrieve the FDA Medication \n identifies a request from VistA for a specific FDA Medication Guide and\n automatically retrieves it from the Server Repository and displays to the\n user via the Internet Explorer browser. \n \n . Introduction of a new option called Display FDA Medication Guide [PSN MED\n GUIDE] to the National Drug File V. 4.0 application for retrieving and \n displaying the FDA Medication Guide for a specific VA Product.\n \n . Introduction of new functionality to the Patient Prescription Processing\n [PSO LM BACKDOOR] option in the Outpatient Pharmacy V. 7.0 application\nGuide for prescription items that contain FDA approved information that\n for retrieving and displaying the FDA Medication Guide for a specific \n prescription.\n \nBelow is a list of all the applications involved in this release along\nwith their patch number:\n \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*158\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*263\ncan help patients avoid adverse events. The FDA requires that Medication\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*343\n \nThe FDA Medication Guides project is expected to complete in three\nincrements. Among other features, the next Increment will automate the\nprinting of FDA Medication Guides for prescriptions dispensed by the VA\nvia Outpatient Pharmacy application when the prescription label is printed.\n \nThe following modifications are included in this patch (PSN*4*263):\n \n A. FDA Display FDA Medication Guide [PSN MED GUIDE] option\nGuides be included with certain prescribed drugs and biological products \n \n Users will be able to retrieve an FDA Medication Guide for a specific VA\n Product by invoking this option. A Java software component running at the\n user's PC will then display the FDA Medication Guide Adobe Acrobat \n document (.pdf) by automatically opening it via the user's default web\n browser, which will allow the users to print it to any printer available\n to them, as seen below:\n \n Select VA PRODUCT NAME: LINDAINE\n 1 LINDANE 1% CREAM,TOP \nwhen the Agency determines that: \n 2 LINDANE 1% LIQUID,TOP \n 3 LINDANE 1% LOTION \n 4 LINDANE 1% SHAMPOO \n CHOOSE 1-4: 3 LINDANE 1% LOTION \n \n The following URL provides the link to the FDA Medication Guide associated\n with this medication. Thin Client users: copy/paste the URL below into a\n browser to access the FDA Medication Guide for this drug:\n \n vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_(Generic)_(2008).pdf\n \n \n [FDA Medication Guide .pdf document opens on the web browser]\n \n \n If a user tries to use this option from a computer which does not have\n the required Java software component installed, the following message\n will display:\n \n Select VA PRODUCT NAME: LINDAINE\n 1 LINDANE 1% CREAM,TOP \n . Certain information is necessary to prevent serious adverse effects \n 2 LINDANE 1% LIQUID,TOP \n 3 LINDANE 1% LOTION \n 4 LINDANE 1% SHAMPOO \n CHOOSE 1-4: 3 LINDANE 1% LOTION \n \n The following URL provides the link to the FDA Medication Guide associated\n with this medication. Thin Client users: copy/paste the URL below into a\n browser to access the FDA Medication Guide for this drug:\n \n vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_(Generic)_(2008).pdf\n\n
\nThis patch addresses the New Service Request (NSR) #20070434 to prevent\n \n CREATE DEFAULT POSSIBLE DOSAGE (#40)\n POSSIBLE DOSAGES TO CREATE (#41)\n PACKAGE (#42)\n \nPatch PSN*4*262 is being released in conjunction with PDM patch PSS*1*155,\nwhich has the functionality in place to determine if possible dosages\nshould be auto-created or not during the match/re-match process.\n \nThis patch contains changes to the Inquire to National Files [PSNACT]\nthe inadvertent creation of supra-therapeutic possible dosages for high\nand Inquire to VA Product Info For Local Drug [PSNLOOK] options to include\nthe display of the new fields. Below are some screen captures of how the\nnew fields will display to the screen for both options:\n \n Example #1:\n ...\n \n Override DF Exclude from Dosage Checks: No\n \n Auto-Create Default Possible Dosage? Yes\nrisk medications during dosage creation performed during the matching and\n \n \n Example #2:\n ...\n Auto-Create Default Possible Dosage? No\n Possible Dosages To Auto-Create: No Possible Dosages\n \n \n Example #3:\n ...\nre-matching of dispense drugs to National Drug File (NDF) entries within\n \n Override DF Exclude from Dosage Checks: No\n \n Auto-Create Default Possible Dosage? No\n Possible Dosages To Auto-Create: 1x and 2x Possible Dosages\n Package: Inpatient\n \n \nNOTE: For more information about the new fields, please refer to the patch\n PSN*4*261. For information on how the new fields affect\nthe Pharmacy Data Management (PDM) V. 1.0 application.\n auto-creation of possible dosages during match and re-match\n process, refer to patch PSS*1*155.\n \nAlso, this patch adds the component $$POSDOS to the routine PSNAPIS,\nsupported by Integration Control Registration (ICR) #2153, to retrieve the\ncontent of these 3 new fields.\n \nIn addition, a post-install routine will run to update the CREATE DEFAULT\nPOSSIBLE DOSAGE field (#40) with the default value of "YES" for entries\nadded to the VA PRODUCT file (#50.68) after patch PSN*4*261 was installed.\n \nThe post-install routine will be automatically deleted from the system\nupon completion of the installation.\nPatch PSN*4*261 has been previously released in preparation for this\nproject. It added the following 3 new fields to the VA PRODUCT file\n(#50.68):\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch allows printing of the PMIS in two styles.\nSee Patch PSN*4*30 in the National Patch Module for description of the\nBuild.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch is part of the Copayment enhancement project and it will be \n Example #1:\n ...\n Reduced Co-pay: None \n \n Example #2:\n ...\n Reduced Co-pay: Start Date: 01/01/2012 Stop Date: 06/30/2012\n Start Date: 01/01/2013 Stop Date: \n \n \nreleased along with the Integrated Billing patch IB*2*456 and the Accounts\nAlso, this patch adds the component $$REDCOP to the routine PSNAPIS, \nsupported by Integration Control Registration (ICR) #2531, to return the\nexistence of reduced copayment for a VA Product on a given date.\n \nUpdates to these new fields will happen automatically via the monthly \nNational Drug File (NDF) Data Update patches.\nReceivable package (PRCA*4.5*278). \n \nThis patch contains changes to the Inquire to National Files [PSNACT] and \nInquire to VA Product Info For Local Drug [PSNLOOK] options to include\nthe display of the new fields. Below are some screen captures of how the \nnew fields will display to the screen for both options:\n \n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nVistA Patch PSN*4*304 released November 10, 2011 created a new VA drug \nA facility reported that the drug-allergy order check in VistA/CPRS did\nnot trigger appropriately when a patient was ordered a fluroquinolone type\nantibiotic that the patient had a known allergy to. The drug allergy was\nproperly documented in the VistA Adverse Reaction Tracking (ART) System. \n \nThis patch contains a post-install routine that will loop through all the\npatient allergies entries for quinolones and will correctly update such \nentries with the new class "AM400 QUINOLONES", which should trigger the\ndrug-allergy order check when the patient is ordered a medication under\nthis drug class. Once completed, the post-install routine will generate\nclass "AM400 QUINOLONES". The quinolone antibiotics were previously \nand send the Mailman message below to the person who installed the patch,\nto the mail group 'NDF DATA' and to all the 'PSNMGR' security key holders.\n \n Subj: Post-install results from patch PSN*4*297 [#110557] 02/02/12\n From: NDF MANAGER In 'IN' basket. Page 1\n ---------------------------------------------------------------------\n Number of Patient Allergy entries by class:\n \n Before update:\n AM900 - ANTI-INFECTIVES,OTHER: 1601\nlocated under VA drug class "AM900 ANTI-INFECTIVES,OTHER". Existing\n AM400 - QUINOLONES : 11\n \n After update:\n AM900 - ANTI-INFECTIVES,OTHER: 919\n AM400 - QUINOLONES : 693\n \n Enter message action (in IN basket): Ignore//\n \nThe results above will vary from site to site. Some sites might even have\nthe exact same number 'Before' and 'After' the update, which means the\npatient allergies in the PATIENT ALLERGIES file (#120.8) to antibiotics \nsite had not been affected by the problem in PSN*4*304 when it was \ninstalled.\nin the quinolone class were not automatically updated to the new VA drug\nclassification with the release of PSN*4*304. Consequently the entry of\na new order for an antibiotic in the Quinolone VA drug class will not\ntrigger a drug allergy alert.\n \n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch performs the following data dictionary update in the VA \n \n Requested changes:\n \n HELP-PROMPT : Answer must be 1-100 characters in length.\n TECHNICAL DESCR: This field is used for storing the FDA Medication\n Guide filename associated with this VA Product. The \n file is physically stored in the repository indicated\n in the FDA MED GUIDE SERVER URL field (#100) in the\n PHARMACY SYSTEM file (#59.7). \nPRODUCT file (#50.68). The HELP-PROMPT and TECHNICAL DESCR for the FDA MED\nGUIDE field (#100) is being modified as show below:\n \n Current: \n \n HELP PROMPT : Answer must be 1-100 characters in length\n TECHNICAL DESCR: This field is used for storing the FDA Medication\n Guide file name associated \n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nNOTE: This patch is part of NDF Data Update FY13 #2, which is comprised \nproduct file. There should not be any unmatched entries for the VA \nPharmacy ADPAC to rematch. \n \nThis patch will generate four e-mail messages but the messages should not \ncontain any data that the Pharmacy ADPAC to act on. But due to system \ndesign the patch will send the following patch messages.\n \nDATA UPDATE FOR NDF\nUPDATED DRUG INTERACTIONS\nDRUG UNMATCHED FROM NATIONAL DRUG FILE\nof one patch, PSN*4*339.\nALLERGIES UPDATE.\n \nIf there is information found in these messages, contact NDF Support at \nVHAPBH NDF in MS Outlook.\n \nThis patch consists of NDC updates to NDC/UPN file (#50.67). This patch \nwill transition The National Drug File Management system away from a \nmanually maintained NDC file to a system that is supported by a \ncommercial vendor. \n \nThis patch will add new NDC data but will not make changes to the VA \n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch corrects the display of erroneous routes.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThese changes are being sent out in preparation for the release of the\nincluded in this patch.\nPharmacy Ordering Enhancements patches. The changes in this patch will\nnot affect National Drug File functionality until the Auto Create Dosages\n[PSS DOSAGE CONVERSION] option that is released with Pharmacy Data\nManagement patch PSS*1*34 is run. After that option is run, dosage\ninformation will be created and stored in the DRUG file (#50). Then when\ndrugs are matched through the National Drug File options, the dosage\ninformation may need to be automatically updated based on the new National\nDrug File match. The functionality to update the dosage information is\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch corrects possibly mis-matched items in the drug file.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates dats for PMI sheets.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch restores data that was deleted from the NATIONAL DRUG\nCLASS field (#25) in the DRUG file (#50).\nIt also corrects the "AND", "VAPN", "APN", "VAC", and "AQ1" cross references\nin the DRUG file (#50).\nIt also verifies that data for the CMOP ID field (#27) and the NATIONAL\nFORMULARY INDICATOR field (#29) in the DRUG file (#50) are in the\ncorrect locations.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch removes remote members from the mail group NDF DATA.\n\n
\nThis patch unmatches improperly matched drugs.\nThis patch also unmarks drugs for CMOP if they are not matched to\na VA product or if they are matched to a VA product which is not\nmarked for CMOP.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch updates data for medication instruction sheets.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nPatch PSN*4.0*365 addresses the following four issues:\n \n1. INC000000864913 - Subscript error when sorting by name printing \nproducts marked for CMOP\n2. INC000000744810 - Drug Identifier Data Dictionary description \nchange\n3. INC000000812050 - Invalid entries on Merge report (Additives and \nSolutions needing to be re-matched to Orderable Items)\n4. INC000000610447 - Incorrect drug identifier included under Varenicline\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nPatch PSN*4.0*406 addresses the following issue:\n \n1. When entering allergies for patients the software allows for\nassigning inactive Drug Ingredients from the Drug Ingredients file \n(#50.416) as Causative Agents.\n\n
\nThis patch updates data for the National Drug File application.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nPatch PSN*4.0*430 addresses the following issue:\n \nUnable to enter new national drug interactions into Drug Interactions \nfile (#56). \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nPatch PSN*4.0*441 addresses the following issue:\n \n1. INC000001243262 - Tramadol, Clonazepam, and Diazepam patient allergies \nwith a Trade Name in the Reactant field need to be updated to account for \nVA DRUG CLASS changes distributed with the September National Drug File \nData Update\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch cleans up data in the DRUG file (#50). Certain fields were\nnot being properly set when entries were unmatched from National Drug\nFile (NDF) data updates.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nSee Patch PSN*4*48 in the National Patch Module for description of the\nbuild.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\n1. Entries in the local DRUG file (#50) can be matched to the National Drug\n Management (PDM) as this option calls those routines through\n supported DBIA # 2080.\n \n 2. Currently the Inquire to National Files [PSNACT] option, does not\n display any information regarding the inactivation date of the VA\n PRODUCT file (#50.68) entries and the NDC/UPN file (#50.67) entries.\n The display of the inactivation date is now included in this patch.\n File VA PRODUCT file (#50.68) by selecting an entry in that file or by\n selecting an entry from the NDC/UPN file (#50.67). If the entry in either\n file is inactive, the current dialog is misleading. It appears that a match\n has been found, but in actuality it does not. This patch will affect the\n following options:\n \n - The Rematch / Match Single Drugs [PSNDRUG] option in NDF.\n - The Drug Enter/Edit [PSS DRUG ENTER/EDIT] option in Pharmacy Data\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nPatch PSN*4.0*471 addresses the following issue:\n \n1. I7357301FY16 - Alfuzosin patient allergies with a Trade Name in the\nReactant field need to be updated to remove VA Drug Class\nHORMONES/SYNTHETICS/MODIFIERS,OTHER (HS900)\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch is part of the Pharmacy Safety Updates project which was \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444\n INTEGRATED BILLING (IB) V. 2.0 IB*2*545\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429\n INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313\n \n \nThe following New service Requests (NSRs) are being addressed by this patch:\nestablished to address specific New Service Requests (NSRs) as well as a\n \n NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply\n ---------------------------------------------------------------------------\n The Outpatient Pharmacy and supporting VistA applications are being modified\n to allow dispensing of more than 90 day supply fill for outpatient \n prescriptions. The new limit will be 365 days and will be set for each drug\n individually. See below for more information on specific menu \n options related to this enhancement. \n \n \nRemedy Ticket and a Patient Safety Issue (PSI) related to the VistA Pharmacy\nThe following National Drug File (NDF) functionality was modified:\n \n1. A new field called MAXIMUM DAYS SUPPLY (#32) was added to the VA PRODUCT\n file (#50.68) for storing the national maximum day supply value for a\n medication in an outpatient prescription. This field will not be populated\n initially by Pharmacy Product System - National (PPS-N) as changes will be\n required to that application to edit and export this new field. \n \n2. Inquire to VA Product Info For Local Drug [PSNLOOK] option\n This option was modified to display the new field as seen below:\napplications as approved by the Health Systems Enterprise Systems Manager\n \n ...\n \n Override DF Exclude from Dosage Checks: No\n \n Auto-Create Default Possible Dosage? Yes\n Reduced Co-pay: None\n Maximum Days Supply: 360\n \n ...\n(ESM).\n \n3. Inquire to National Files [PSNACT] option\n This option was also modified to display the new field as seen below:\n \n ...\n \n Auto-Create Default Possible Dosage? No\n Possible Dosages To Auto-Create: 1x Possible Dosage\n Package: Both Inpatient and Outpatient\n \n \n Reduced Co-pay: None\n Maximum Days Supply: 360\n \n Press return to continue or '^' to exit: \n ...\nThis project is comprised of patches from five different applications, as\nshown below:\n \n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nPatch PSN*4.0*437 addresses the following issue:\n \nIn preparation for the VA's transition from IPv4 to IPv6 the National \nDrug File (NDF) package will require modifications to make it IPv6 ready.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch updates data for the national drug file application.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis change is being sent out in preparation for the release of the\nPharmacy Ordering Enhancements patches. The change in this patch will\npopulate dosages that are stored in DRUG file (#50) when completing a\nmatch in National Drug File (NDF). This data stored in DRUG file (#50)\ncomes from the match in NDF.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch adds three components to the routine PSNAPIS, supported by \nIntegration Control Registration (ICR) #2531, to provide additional\naccess to the NDC/UPN file (#50.67).\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch updates data for the National Drug FIle application.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch updates data for the national drug file application.\n\n
\nWhen using the Patients on Specific Drug(s) [PSJ PDV] option of the\nInpatient Medications V. 5.0 package for a given VA Class, the generated\nreport did not have all drugs included. This was due to bad "AOC"\ncross-reference associated with the VA CLASSIFICATION field (#2) in the\nDRUG file (#50) which is not maintained properly by the National Drug File\n(NDF) package. This patch fixes this problem.\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch updates data for the National Drug File application.\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThis patch adds a cross-reference to the PRIMARY INGREDIENT field (#2)\n being properly set. This caused the APD cross-reference on the\n INGREDIENT 1 field (#1) and the INGREDIENT 2 field (#2) in the DRUG\n INTERACTION file (#56) to be improperly set. Certain interactions\n were not being properly tracked.\n \n This patch corrects that defect. It also includes a post-install\n routine to reset existing cross-references.\n \n 2. In the data update patch PSN*4*53, the units for the VA Product\n INTERFERON BETA-1B,RECOMBINANT 9.6 MILLION UNT/VIL INJ (entry number\nin the DRUG INGREDIENTS file (#50.416). This patch also corrects the\n 11809 in the VA PRODUCT file (#50.68)) was changed. This should have\n caused all entries in the DRUG file (#50) matched to that product to\n be unmatched. That unmatching did not take place. This patch causes\n that unmatching.\n \nAfter the patch is installed, the routines PSNJP54 and PSNOP54 should\nbe run from programmer mode. These routines will generate list of\npatients who received combinations of drugs which should have caused\nan interaction warning but did not. These routines MUST be run\nwithin 60 days of the install of this patch, Once the routines have\nincorrectly set APS cross-reference in that file and the APD cross-\nbeen run, they may be deleted.\nreference in the DRUG INTERACTION file (#56).\n \nThis patch also corrects two problems.\n \n 1. Under certain circumstances, the APS cross-reference on the PRIMARY\n INGREDIENT field (#2) in the DRUG INGREDIENTS file (#50.416) was not\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nThis patch provides updates to data in several of the files associated\n 50.627 WARNING LABEL MAP \n \nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch deletes existing entries in these\nfiles, loads the new data, and rematches entries in the VA PRODUCT file \n(#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n 50.626 WARNING LABEL-SPANISH \n\n
\nThis patch provides updates to data in several of the files associated\nchanged. The second, with the subject UPDATED INTERACTIONS, lists\ninteractions that have been added, edited, or inactivated. The third, with\nthe subject DRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the\nDRUG file (#50) which have been unmatched from NDF. The fourth, with the\nsubject INTERACTIONS and ALLERGIES UPDATED, lists interactions and allergies\nwhich have been changed because they were created with ingredients that\nare no longer primary ingredients.\nwith the National Drug File (NDF) application.\nThis patch generates four mail messages. All are sent from NDF MANAGER\nto members of the NDF DATA mail group, holders of the PSNMGR security \nkey, and the person installing the patch. The first message, with the\nsubject DATA UPDATE FOR NDF, lists new products, CMOP ID (if one exists),\ndispense units, and associated NDCs, products for which the national\nformulary indicator has changed, products that have been unmatched from\nCMOP, and products for which the national formulary restriction has\n\n
\nThe environment check routine for this patch checks to see that the\ninstaller is a valid user.\nThe post-install routine for this patch matches entries in the VA PRODUCT \nfile (#50.68) to the proper PMIs.\n\n
\nUnder certain circumstances, the AND cross reference in the DRUG file\n(#50) was not being properly set. This patch corrects that problem.\nA post-install routine PSN4P59P corrects any existing problems.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSN*4*563.\n\n
\nThis patch has the following enhancements for Clinical Ancillary Services\n(CAS) Enhancements (RXSU2).\n \n1. Manage Lookup List Inactive Entries\n \n The following files have added a new field identifier to their data\n dictionaries to indicate if they are marked as Inactive entries.\n \n a. VA PRODUCT file (#50.68) the INACTIVATION DATE field (#21).\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSN*4*565.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSN*4*566.\n\n
\nThe purpose of this patch is to distribute the data dictionary for the VA \nDRUG CLASS file (#50.605) in order to set the APPLICATION GROUP of GMTS \nto allow selection in Health Summary.\n \nIn addition, a new API is being distributed to allow selection of drug \nclasses in Ad Hoc reporting as well as Health Summary collections.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSN*4*568.\n\n
\nThis patch, along with patch PSS*1*243 will address the following ePrescribing\n--------------------------------------------\n1. INC9317643 - We have noticed a number of drugs that do not auto match for\n inbound eRx orders\n \n DUPLICATE - INC9105989 - erx software auto-matched wrong drug product\n \nProblem: \n--------\nThe VA Health Administration Center Denver reported and issue with incoming\nePrescribing orders (eRx) not automatically matching the ordered drug with a\n(eRx) issue: \nVistA corresponding Dispense Drug, even when the NDC received matches 1 to 1\nwith a specific VA Product entry. They also noticed the issue to be more\nprevalent with dispense drugs that have been recently re-matched to a \ndifferent VA Product entry due to changes from MG to MGC in the strength. \nAfter researching this issue it was determined that the root cause of the\nproblem was a 'corruption' of the "APR" cross-reference in the DRUG file (#50)\nwhich was not properly set or killed after Dispense Drugs were matched,\nun-matched or re-matched to VA Product entries. Such cross-reference is used\nby the eRx drug auto-matching processing and that's the reason it failed\nfor some drugs. It turned out that two other cross-references "AND" and "APN"\n \nalso had the same issue. No user functionality side-effects have been\nreported related to these other two cross-references though.\n \n \nResolution: \n-----------\nThe setting and killing of the "APR", "AND" and "APN" cross-reference have\nbeen completely reviewed at every point where a Dispense Drug is matched,\nun-matched or re-matched to a VA Product and after this patch is installed\nthey should be properly maintained. Furthermore, a post-install routine\n1. INC9317643 - We have noticed a number of drugs that do not auto match for\nwill completely kill off the 3 cross-references and re-build them completely.\nThe patch PSS*1*243 is also being released along with this patch because the\nNDF (National Drug File) matching functionality is available in both\napplications, NDF and PDM (Pharmacy Data Management). \n \n \nTechnical Resolution: \n---------------------\nChanged the routines PSNHELP1, PSNMRG, PSNPPSNU and PSNPPSNW to kill and set\nthe cross-references "AND", "APN" and "APR" properly.\n inbound eRx orders\n \n DUPLICATE - INC9105989 - erx software auto-matched wrong drug product\n \nDefect Tracking System Ticket(s) & Overview: \n\n
\nThis patch will address the following issue: \n--------\nThe Clinical Product Support Team 1 (Clin 1) reported that after the release\nof PPS-N file #62 they received communication that the VA PRODUCT file\n(#50.68) contained additional entries that did not look correct. Most of the\nproblems reported, if not all, seem to be related to non-production accounts\nbut not all non-production accounts presented the problem.\n \nResolution: \n-----------\nAfter some extensive research it was determined that the cause of the specific\n \nproblem reported is related to concurrent (grouped) installation of PPS-N\nfile #62 and #63. Residual/temporary data from the file #62 installation is\nnot properly cleaned up before proceeding to the installation of file #63 and\nit throws off the installation causing it to add thousands of corrupted \nrecords to the VA PRODUCT file (#50.68).\n \nTechnical Resolution: \n---------------------\nLine tag CKDIR+15^PSNPPSNF was using variable X22 instead of X2 in order to \ndetermine whether it should kill the ^TMP nodes used during installation of\n1. INC12620504 - Requesting Assistance with an issue with PPS NEW 62\neach file or not. Because of the wrong variable was used the software was\nnot killing off the ^TMP nodes before starting installation of the next file. \nThe solution applied was to ALWAYS kill off the ^TMP nodes after each file\ninstallation when multiple files are being installed at once.\n \nData Clean-Up:\n--------------\nThe corrupted records will be removed from the VA PRODUCT file (#50.68) \nthrough a post-install routine with the following criteria:\n \n \n 1) The latest released PPS-N file was #70 released on 10/26/2020 and the\n last VA PRODUCT file (#50.68) record IEN was 30495.\n \n 2) A post-install routine will start looking at records with an IEN greater\n than 32900 as the first corrupted record was assigned the IEN 32926 as\n shown below:\n \n Global ^PSNDF(50.68,32000:,0 -- NOTE: translation in effect\n ^PSNDF(50.68,32926,0)="6610,1,1^3200624.15171^43,.02,.01^360^A"\n ^PSNDF(50.68,33094,0)="16647,1,1^3200624.15713^43,.02,.01^360^A"\nDefect Tracking System Ticket(s) & Overview: \n ^PSNDF(50.68,59087,0)="7647,1,1^3200624.15153^43,.02,.01^360^A"\n ...\n \n 3) For each record with an IEN greater than 32900 the post-install will\n check if each of the following required fields below has a valid value\n (numeric value corresponding to a valid entry in the file it points to). \n If at least one field is found to be valid, the record will be skipped,\n otherwise it will be deleted from the VA PRODUCT file (#50.68).\n \n Field # Field Name Points to\n--------------------------------------------\n ----------------------------------------------------------------\n .05 VA GENERIC NAME VA GENERIC (#50.6)\n 1 DOSAGE FORM DOSAGE FORM (#50.606)\n 3 UNITS DRUG UNITS (#50.607)\n \n 4) All deleted records will be backed up to ^XTMP("PSN571PI") global and\n will set to remain on the database for 365 days.\n1. INC12620504 - Requesting Assistance with an issue with PPS NEW 62\n \nProblem: \n\n\nBackup of PSN*4.0*573 on Mar 26, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch PSN*4*54 creates a list of combinations of drug products that should\n** PSNJP54 must be run within 45 days of the installation of PSN*4*54. **\n \nRoutine PSNJP54 should be run from programmer mode after this patch is\ninstalled. The user will be prompted for a date to start the search and an\noutput format (report or spread sheet). The default starting date for\nPSNJP54 is 365 days ago. The report produces a list of patients who\nreceived combinations of drugs that should have generated an interaction\nwarning but did not.\n \nOn a DSM system with no users and choosing the default start dates,\nhave generated an interaction warning but did not. Routine PSNJP54 is\nPSNJP54 ran in about 20 minutes. On a larger system or on a system with\nmany users, running time may be longer.\n \nAfter the report has been reviewed by pharmacy personnel, PSNJP54 may be\ndeleted from your system.\n \nAll NOIS associated with this patch are associated with this item.\nincluded in PSN*4*54 to generate a report of patients who may have been at\nrisk.\nSites have reported an error that may occur during the execution of this\nreport. The code responsible for the potential error may also display\nincorrect schedule types for IV orders. This patch corrects both of these\nissues.\n \n\n
\nSites transitioning from Cache to Iris - NOL \n \nThis patch will resolve the following issue:\n \nINC11884678 - Sites transitioning from CACHE to IRIS \n\n
\nThe On-demand functionality of the FDA Med Guides is being retired. \nInstead of automatically opening the guide in the user's browser if they \nhave the required software now all users will need to copy the link given \nin the Med Guide option to their own browser.\n\n
\nThis patch addresses the following issue:\n \nWhen an allergy is entered to a Coflex product, the allergy is incorrectly\ninterpreted as being to "orphenadrine".\n\n
\nThis patch addresses the following issue:\n------------------\nfor the PPS-N application. Support for RSA keys are anticipated to be \ndeprecated in the future, so to maintain Vista's security posture and \nensure continuous operation of required Vista processes, software \nutilizing SSH PKI user keys must be updated to support the stronger ECDSA \nencryption key. \n \nThe modification should allow the creation of any ECDSA keys to be forward\ncompatible when Red Hat Enterprise Linux (RHEL 8) is implemented.\n \nResolution:\nN/A\n-----------\nFile PPS-N UPDATE CONTROL (#57.23) field SFTP SSH KEY ENCRYPTION (#41) is \nmodified to add code ECDSA (Elliptic Curve Digital Signature Algorithm).\n \nModify PSNOSKEY to allow the ECDSA key to be created, viewed, \ndeleted, and update the help text.\n \nRoutine PSNPARM is modified to use new field ECDSA (#11) in the \nPPS-N UPDATE CONTROL FILE (#57.23) in option PPS-N Site Parameters \n(Enter/Edit) to set if ECDSA keys are allowed to be created.\n \nPatch Components:\n-----------------\n \n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n \n------------------ ------------------- --------------------\nPPS-N UPDATE CONTROL SFTP SSH KEY ENCRYPTION Modified\n(#57.23) (#41)\n \nPPS-N UPDATE CONTROL ECDSA New\n(57.23) (#11)\n \n \nForms Associated:\n \nECDSA/EDDSA Key creation\nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\nN/A\n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nN/A\n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nDefect Tracking System Ticket(s) & Overview:\nN/A\n \nSecurity Keys Associated: \n \nSecurity Key Name\n-----------------\nN/A\n \nTemplates Associated:\n \n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\nN/A\n \n1. INC26749697 - ECDSA KEY CREATION\nParameter Definitions Associated:\n \nParameter Name New/Modified/Deleted\n-------------- --------------------\nN/A\n \nAdditional Information:\n-----------------------\nNew Service Requests (NSRs):\nN/A\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nProblem:\n--------\nWith the implementation of Red Hat Enterprise Linux (RHEL 8) stronger \nencryption key ECDSA is now available and supported. PPS-N \nAssociated NSR(s):\napplication at this time is using RSA type SSH key for connecting to the \nPPS-N server to receive the dat file that is used for updating Nation \nDrug files.\n \nNew keys added:\nElliptic Curve Digital Signature Algorithm (ECDSA)\n \nECDSA keys can created for encryption length of 256, 384 or 521 bits.\n \nNecessary changes are required to allow creation of ECDSA key \n\n
\nThis patch, along with other patches, adds Pharmacogenomic (PGx) order\nchecking to medication orders entered through Inpatient Medications,\nOutpatient Pharmacy and Computerized Patient Record System (CPRS). A \npatient's genomic test results will be retrieved from the Health Data\nRepository (HDR), and along with the prospective drug(s) of a medication\norder is sent to the vendor to retrieve interactions between the patient's\ngenes and the prospective drug(s).\n\n
\nThis patch updates data for the National Drug File application.\nI also makes changes to the data dictionary for the UNITS multiple\nfield (#8) and the DISPENSE UNITS PER DOSE multiple field (#9) in the\nDOSAGE FORM file (#50.606).\n\n
\nSites have reported patients' Social Security Numbers display\n \nRoutine PSNJP54 should be run from programmer mode after this patch is\ninstalled. The user will be prompted for a date to start the search and an\noutput format (report or spread sheet). The default starting date for\nPSNJP54 is 365 days ago. The report produces a list of patients who\nreceived combinations of drugs that should have generated an interaction\nwarning but did not.\n \nOn a DSM system with no users and choosing the default start dates,\nPSNJP54 ran in about 40 minutes. On a larger system or on a system with\nincorrectly when running report routine PSNJP54. This patch corrects this\nmany users, running time may be longer.\n \nAfter the report has been reviewed by pharmacy personnel, PSNJP54 may be\ndeleted from your system.\n \nAll NOIS associated with this patch are associated with this item.\nby displaying the proper SSN.\n \nNo problems have been reported with PSN*4*54 other than this report\nroutine. PSN*4*54 itself is not an emergency patch and its installation\nschedule does not need to be accelerated.\n \n** PSNJP54 must be run within 45 days of the installation of PSN*4*54. **\n\n
\nHUI/VHA CIO SD&D PHARMACY DATA INTERCHANGE.\n \nThis Hui/VHA CIO SD&D Pharmacy Data Interchangeproject. The project provides\na method for the one-way electronic transferof prescription orders from an \nexternal system to VistA.\n\n
\nThis patch updates data for the National Drug File application.\n\n
\n \nCMOP ID (if one exists), dispense units, and associated NDCs,\nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\n \n \nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\n\n
\nThis patch corrects several problems.\n \n 3. This patch adds help text when selecting a National Drug Code (NDC)\n using the option NDC/UPN Inquiry [PSNUPN].\n \n 4. The option Local Formulary Report [PSNFRMLY] was leaving the variable\n DIR defined upon exit. This could cause erroneous prompts under certain\n circumstances. This patch eliminates that problem.\n \n 1. An error may occur when using the Pharmacy Data Management (PDM)\n Drug Enter/Edit option [PSS DRUG ENTER/EDIT]. The routine PSNSTCK was not\n cleaning up all local variables.\n \n 2. This patch also corrects a possible error in a few cases when using\n the Inquire to VA Product Info For Local Drug option [PSNLOOK]. The\n routine PSNLOOK was not checking properly for the (non)existence of data.\n\n
\n \nCMOP ID (if one exists), dispense units, and associated NDCs,\nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\n \n \nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\n\n
\nThis patch installs new software and data dictionaries to print Patient\nMedication Information Sheets (PMIs). It will delete the present file\nMEDICATION INSTRUCTION SHEETS (#54.7) stored in the global PSPPI. The\nnew files are stored in the PS global and the seven new file numbers\nrange from ^PS(50.621 - ^PS(50.627. The new data source is First Data\nBank.\n\n
\nIn support of the Outpatient Pharmacy V. 7.0 laser labels enhancement a \nnew Application Program Interface (API) was created. National Drug File \nV. 4.0 will supply the Patient Medication Information (PMI) data in ^TMP \nfor use in printing on laser labels. This patch supplies this API.\n\n
\nThis patch changes the read access for four files associated with the\npharmacy files.\nNational Drug File application.\n VA GENERIC file (#50.6)\n VA DISPENSE UNIT file (#50.64)\n NDC/UPN file (#50.67)\n VA PRODUCT file (#50.68)\n \nThese files were originally sent with a read access of @. This patch\nchanges the read access to Pp which is similar to that found on other\n\n
\n 1 This patch installs a new field in the VA PRODUCT file (#50.68).\n patch, PSN4P69P, corrects that problem.\n The post-install routine creates a mail message from NDF MANAGER with\n the subject DRUGS UNMARKED FOR CMOP which lists the items which were\n unmarked. That message is sent to the mail group NDF DATA, holders of\n the PSNMGR security key, and the person installing the patch.\n The new field (#23) is named EXCLUDE DRG-DRG INTERACTION CK and is\n defined as a set of codes. This field will be used in pharmacy order\n checking to bypass drug-drug interaction checking on specific VA\n Products IN THE FUTURE. This patch does not populate the new field.\n \n 2. Under certain circumstances if an entry in the VA PRODUCT file\n (#50.68) was unmarked for CMOP, entries in the DRUG file (#50) matched\n to that item were not unmarked. The post-install routine for this\n\n
\n \nCMOP ID (if one exists), dispense units, and associated NDCs,\nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\n \n \nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\n\n
\n \nCMOP ID (if one exists), dispense units, and associated NDCs,\nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\n \n \nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\n\n
\n \nCMOP ID (if one exists), dispense units, and associated NDCs,\nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\n \n \nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\n\n
\nPharmacy Benefits Management (PBM) Strategic Healthcare Group in\nKernel V. 8.0\nComputerized Patient Record System (CPRS) V. 1.0\nPharmacy Data Management (PDM) V. 1.0\nOutpatient Pharmacy (OP) V. 7.0\nControlled Substances (CS) V. 3.0\n \nThe National Drug File data update patches PSN*4*64 and PSN*4*66 assign a\nCS Federal Schedule to controlled substances and identify controlled\nsubstances as narcotics or non-narcotics by populating the CS FEDERAL\nSCHEDULE field (#19) of the VA PRODUCT file (#50.68).\ncollaboration with the Drug Enforcement Administration (DEA), requested\n \nThis is the NDF patch that provides the following new functionalities:\n \n1. This patch includes the Data Dictionary (DD) changes for CS FEDERAL\nSCHEDULE field (#19) of the VA PRODUCT file (#50.68)\n \n2. When using the Merge National Drug File Data Into Local File\n[PSNMRG] option, the software will now check to see if the CS FEDERAL\nSCHEDULE field (#19) of the VA PRODUCT file (#50.68) has data and the DEA,\nSPECIAL HDLG field (#3) of the DRUG file (#50) does not have data. If both\nthe development of the first Public Key Infrastructure (PKI) VistA pilot\nare true, then the DEA, SPECIAL HDLG field will be populated with the CS\nFEDERAL SCHEDULE code mapped to the corresponding DEA, SPECIAL HDLG code\nusing the following table:\n \n CS FEDERAL SCHEDULE DEA, SPECIAL HDLG Code\nSchedule I narcotics 1 1\nSchedule II narcotics 2 2A\nSchedule II non-narcotics 2n 2C\nSchedule III narcotics 3 3A\nSchedule III non-narcotics 3n 3C\nproject, named Electronic Prescription Order Entry for Schedule II\nSchedule IV narcotics 4 4\nSchedule V narcotics 5 5\n \n3. This patch ensures that the newly populated CS FEDERAL SCHEDULE field\n(#19) of the VA PRODUCT file (#50.68) is also included as part of the\nNational Drug file details in Inquire to National Files [PSNACT], NDF\nInfo From Your Local Drug File [PSNRPT], Verify Matches [PSNVFY] and\nVerify Single Match [PSNVER] options.\n \n4. When using Rematch / Match Single Drugs [PSNDRUG] option, if the CS\nControlled Substances. The objective is to develop an electronic order\nFEDERAL SCHEDULE field (#19) of the VA PRODUCT file (#50.68) and the DEA\nSPECIAL HDLG field (#3) of the DRUG file (#50) have a discrepancy, then\nthis patch displays a warning message, "The CS Federal Schedule associated\nwith this drug in the VA Product file represents a DEA, Special Handling\ncode of XX", where XX is the CS FEDERAL SCHEDULE code mapped to the\ncorresponding DEA SPECIAL HDLG code using the table listed under item 2.\nentry system for Schedule II controlled substances using digital\nsignatures. To make this project viable, modifications to the following\npackages were identified:\nNational Drug File (NDF) V. 4.0\n\n
\nThis Build builds on the foundation to identify VA Products from the VA\nPRODUCT file (#50.68) as EXCLUDE from drug-drug interaction checking.\nTwo new menu options are included to print marked VA Products. Two existing\noptions have been enhanced to display the new field to the user. A enhanced\nAPI routine PSNAPIS is also included.\n\n
\nThis patch updates the data for patient medication instruction sheets.\n\n
\n \nCMOP ID (if one exists), dispense units, and associated NDCs,\nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\n \n \nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\n\n
\nRe-index the APD cross reference in File 56.\n\n
\n This patch lays the foundation for future Patient Medication Information\n \n Sheets (PMI) data updates. It creates the Delete Patient Medication\n Information Sheets [PSNDELTE] option.This new stand-alone option should\n only be used as part of future Patient Medication Information Sheet update\n patches. Because it deletes ALL PMI related DATA files, it should not be\n used at any other time.\n \n IMPORTANT: Do NOT use this option until instructed to do so in future PMI\n Update patches.\n\n
\nIt is imperative that you follow the proper sequence of loading and\nPatient Medication Information Sheets. This patch will reset fields\nin the VA PRODUCT file (#50.68). These fields are GCNSEQNO field (#11),\nPREVIOUS GCNSEQNO field (#12), and NDC LINK TO GCNSEQNO field (#13). This\nis accomplished by data stored in a transport global included in this\npatch. The source for the Patient Medication Information (PMI) Sheet data\nis First Data Bank.\ninstalling this patch along with the new global file. If not done in the\ncorrect sequence, errors could occur when attempting to print Patient\nMedication Information (PMI) Sheets.\n \n \n \nThis patch requires patches PSN*4*74 and PSN*4*75. This patch is required\nto provide updates to data in several files in order to print the latest\n\n
\n \nUnder certain conditions, if a National Drug File (NDF) data update patch\ndeleted an ingredient from an entry in the VA PRODUCT file (#50.68),\ncross-references in the DRUG INTERACTION file (#56) for other\ningredients in that product were inappropriately deleted. Patch\nPSN*4*77 corrected existing problems. This patch will prevent further\noccurrences.\n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\nRe-index the APD cross reference in File 56.\n\n
\n \nand are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nMISSING INTERACTIONS, lists items that were added in patch PSN*4*79\nfor which an interaction warning should have been triggered but was not.\nIt also lists the interactions. The message with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE is not generated by this patch\nThis patch provides updates to data in several of the files associated\nsince none of the data elements in this patch cause entries in the \nDRUG file (#50) to be unmatched from NDF.\n \nThis patch also creates ^XTMP("PSNINT") that contains a list of\ncombinations of products that should have generated an interaction\nwarning but did not. The size of ^XTMP("PSNINT) is about 120 DSM blocks.\n \nA subsequent patch will be created which will data in ^XTMP to generate\nlists of patients who had received combinations of orders which should\nhave caused an interaction warning but did not.\nwith the National Drug File (NDF) application.\nNot all the data elements entered for patch PSN*4*79 were transmitted\nto the sites. This patch corrects that deficiency. It also corrects the\ninteraction problem reported in NOIS HWH-0204-41872 and the matching\nproblem reported in NOIS PTH-0204-21559 and TUA-0204-30133.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\n\n\nTHIS PATCH WILL CORRECT THE PROBLEM OF INGREDIENTS NOT DISPLAYING DURING \nTHE VERIFY PROCESS.\n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe post-install routine for this patch, PSN4P86P, deletes existing\nentries in these files, loads the new data, and rematches entries in\nthe VA PRODUCT file (#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\n **********************************************************************\n \n There are three patches that support the Outpatient Pharmacy Automation\n Interface project. These patches should be installed separately in the\n following order:\n PSO*7*156 Outpatient Pharmacy\n PSS*1*82 Pharmacy Data Management\n PSN*4*84 National Drug File\n \n They contain routines, templates, options, and data dictionary changes to\n implement the Outpatient Pharmacy Automation Interface features. Please\n * This patch is part of the Outpatient Pharmacy Automated Dispense *\n refer to the individual patch description of the other patches to get the\n names of the documentation files.\n \n Each patch will share the same starting description with more detail\n for each patch in the corresponding namespace patch number. There is\n only one installation guide. It can be found on the anonymous \n directory. The name of the installation guide is PSO_7_P156_IG.PDF.\n \n The patch enhances the current Health Level Seven (HL7) interface to\n ensure that the interface is compatible with all current Outpatient\n * Project and must be installed at all sites by *\n Pharmacy V. 7.0 automation systems used by the Veterans Affairs\n Medical Centers (VAMCs). The current national VISTA HL7 interface is\n written to HL7 standard V. 2.2. Automated dispensing systems, such as\n the Baker APS Pharmacy 2000, are currently using an interface written to\n V. 2.3.1. standard using locally developed software. The automated\n dispensing systems have committed to be HL7 V. 2.4 compliant.\n \n This patch includes the following new features:\n 1. Enhance the current National Drug File V. 1.0 package HL7 interface\n to the current HL7 V. 2.4 standard.\n * December 31, 2004 *\n \n 2. The interface transmits drug data to multiple vendor systems\n utilized by VAMCs whenever the following options are selected:\n A. Rematch / Match Single Drugs [PSNDRUG] option.\n B. Merge National Drug File Data Into Local File [PSNMRG] option.\n * *\n * Please review the Installation heading of this patch for *\n * Installation Guide retrieval information *\n * *\n **********************************************************************\n\n
\nThis patch contains Application Program Interface's (API's) that will\nenough to retrieve the requested data from the vendor product, when the \ntime comes.\n \nThese are the files that are affected. If any application is making \ndirect global reads or writes to any of these files, they must be \nreplaced by using the API's exported with this patch.\n \nFile Name: File Number:\nDRUG INGREDIENTS 50.416\nVA GENERIC 50.6\nbe used by calling applications that currently do direct global reads or\nVA DRUG CLASS 50.605\nDRUG UNITS 50.607\nNATIONAL DRUG TRANSLATION 50.612\nWARNING LABEL-ENGLISH 50.625\nWARNING LABEL-SPANISH 50.626\nWARNING LABEL MAP 50.627\nVA PRODUCT 50.68\nDRUG INTERACTION 56\nwrites to the National Drug File (NDF) files. Since the VA GENERIC file\n(#50.6), and other NDF-related files are being replaced by a vendor\nproduct, any direct M-based global reads or writes to these files must be\nreplaced by calling the API's provided in this patch.\n \nWhen the new data source is in place, the calling applications will not \nbe required to make any changes, because these API's will be flexible \n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\nThis patch contains updated Application Program Interfaces (APIs) that \nActive status. The API manual has been modified since the original version\nto indicate Active and Inactive APIs. If the API(s) you need have an\nInactive status, please contact the Pharmacy Re-Engineering team at the\nBirmingham Field Office.\nwill be used by calling applications that currently do direct global \nreads or writes to the National Drug File files. A review of the \npreviously released APIs showed several entry points where additional \npieces of data were required to be returned.\n \nIf you have already made code modifications, or have made plans to make\ncode modifications to use any of the new APIs, please check the latest\nversion of the API manual to verify that the API(s) in question have an\n\n
\nThis patch fixes the undefined error reported in NOIS ISH-1004-41307 when\nusing the Rematch / Match Single Drugs [PSNDRUG] option.\n\n
\n \nCertain of the warning labels associated with the Patient Medication\nInstruction Sheet (PMI) portion of the National Drug File (NDF) application\nare gender specific. This patch adds a new field, SPECIFIC TO GENDER (#2),\nto files WARNING LABEL-ENGLISH (#50.625) and WARNING LABEL-SPANISH (#50.626).\nThese fields are populated with the release of PMI updates.\nThe source of the data in these fields is First Data Bank.\n\n
\n \nUnder certain circumstances the matching process aborted with an undefined\nerror. Specifically, this error would occur when tying to match to a\nVA Product that began with a number. This patch corrects that problem.\n\n
\n \nproblem. Some of these locally added ingredients may have been\noverwritten by nationally entered ingredients.\nThis patch modifies the data dictionary of this file so that local\nentries can no longer be made.\n \n3. It has also been noted that over 1250 entries in the DRUG INTERACTION\nfile (#56) involving these locally added ingredients have been added.\nIf the locally added ingredients have been overwritten, these interactions\nwill be interactions involving the national ingredients.\n \n1. Under certain circumstances the APD cross-reference in the DRUG\nSites are strongly urged to review locally added interactions to verify\nthat they have not been changed. Sites are also strongly urged to\ninactivate any interactions involving local ingredients. Finally, sites\nare urged to review any allergies entered for drug ingredients to verify\nthat they have not been changed.\nINGREDIENT file (#50.416) was not being properly set. This patch remedies\nthat defect and creates those entries which were not properly set in the\npast.\n \n2. It has been noted that some sites have made local entries to the DRUG\nINGREDIENT file. This should not have been done. While this was not the\nproximal cause of the problem noted in item 1, it may have exacerbated the\n\n
\nThis patch updates data for the national drug file application.\n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\n \n with new entries. This patch makes corrections to several files in multiple\n applications that use the VA DRUG CLASS file (#50.605).\n \n The patch will correct entries in the DRUG file (#50) so that the VA \n CLASSIFICATION field (2) matches the entry in the NATIONAL DRUG CLASS \n field (#25).\n \n The patch also updates pointers in the PATIENT ALLERGIES file (#120.8),\n the GMR ALLERGIES file (#120.82) so that allergy relationships created prior\n to the NDF DATA Update PSN*4*95 continue to function correctly and display\n \n warnings appropriately.\n \n The patch updates the FH SITE PARAMETERS file (#119.9). Entries in the \n DRUG CLASSIFICATIONS field (85) will be updated so that they link to the \n appropriate entry in the VA DRUG CLASS file (50.605) after installation of\n the NDF Data Update PSN*4*97.\n \n \n The patch updates the REMINDER EXTRACT SUMMARY file (#810.3), the REMINDER \n TERM file (#811.5), and the REMINDER DEFINITION file (#811.9). Changes in\n IMPORTANT\n PSN*4*99 ensure that relationships created prior to installation of the NDF \n Data Update Patch PSN*4*95 continue to function appropriately after \n installation of the NDF Data Update patch PSN*4*97.\n \n This patch generates a mail message with the subject DRUG CLASS CHANGES\n from NDF MANAGER. This message lists drugs for which the class was changed\n and the old class and the new class. This message is delivered to members\n of the NDF DATA mail group, holders of the PSNMGR security key, and the\n person installing the patch.\n \n This patch must be installed immediately after patch PSN*4*95 and PSN*4*97 \n are installed. All three patches should be installed at the same time and \n in sequence.\n \n The names of several entries in the VA DRUG CLASS file (#50.605) have been\n changed. Other entries in this file have been inactivated and replaced\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe post-install routine for this patch, PSN4P98P, deletes existing\nentries in these files, loads the new data, and rematches entries in\nthe VA PRODUCT file (#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\nThis Build contains patch PSN*4*101 which is Pharmacy Data Standardization.\n\n
\nThis patch will modify the DATA component of DBIA 4545, which returns data\nfrom the VA PRODUCT file (#50.68). Added to the output will be the VA\nGENERIC NAME field (#.05) of the VA PRODUCT file (#50.68), along with the\nNAME field (#.01) of that VA GENERIC file (#50.6) entry.\n\n
\nThis patch will contain enhancements to the cycle 1 encapsulation APIs.\n \nA change has been made to the DIC^PSNDI and IX^PSNDI components of DBIA \n4554. DIC("S") will be killed within these components. If the file you \nare passing in has an Inactivation Date field, and you want to screen on \nthat field, a new date input parameter is being added to the components, \nand if a date is passed in, a screen will be set for the calling \napplication.\n \nA new API is added with this patch that returns information from the\nNDC/UPN file (#50.67). See DBIA 4829 for complete information.\n \nA new field has been added to the return data of DATA^PSN50P68 component \nof DBIA 4545. It is the SERVICE CODE field (#2000) of the VA PRODUCT file\n(#50.68). The field is being sent out in National Drug File patch\nPSN*4*103.\n\n\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\n \n 50.626 WARNING LABEL-SPANISH \n 50.627 WARNING LABEL MAP \n \nThe post-install routine for this patch, PSN106P, deletes existing\nentries in these files, loads the new data, and rematches entries in\nthe VA PRODUCT file (#50.68) to the proper PMIs.\nThe source of the data for the PMIs is First Data Bank.\nThis patch provides updates to data in several of the files associated\nwith the Patient Medication Instruction Sheet (PMI) portion of the\nNational Drug File (NDF) application. The seven files are:\n 50.621 PMI-ENGLISH \n 50.622 PMI-SPANISH \n 50.623 PMI MAP-ENGLISH \n 50.624 PMI MAP-SPANISH \n 50.625 WARNING LABEL-ENGLISH \n\n
\n \nproducts for which the national formulary indicator has changed,\nproducts that have been unmatched from CMOP, and products for which\nthe national formulary restriction has changed. The second,\nwith the subject UPDATED INTERACTIONS, lists interactions that\nhave been added, edited, or inactivated. The third, with the subject\nDRUGS UNMATCHED FROM NATIONAL DRUG FILE, lists entries in the DRUG file\n(#50) which have been unmatched from NDF.\nThis patch provides updates to data in several of the files associated\nwith the National Drug File (NDF) application.\n \nThis patch generates three mail messages. All are sent from NDF MANAGER\nand all are sent to members of the NDF DATA mail group, holders of the\nPSNMGR security key, and the person installing the patch. The first\nmessage, with the subject DATA UPDATE FOR NDF, lists new products,\nCMOP ID (if one exists), dispense units, and associated NDCs,\n\n
\nNATIONAL DRUG FILE VERSION 4.0\n\n
\nPSO*6*153 patch transort the routine PSOHELP1 whaich was omitted in\nPSO*6*102. \n\n
\nSee the patch description PSO*6*163.\n\n
\nSee the patch description PSO*6*164.\n\n
\nSee the patch description PSO*6*165.\n\n
\nSee the patch description PSO*6*166.\n\n
\nSee the patch description PSO*6*167.\n\n
\nSee the patch description PSO*6*168.\n\n
\nSee the patch description PSO*6*169.\n\n
\nSee the patch description PSO*6*170.\n\n
\n \nThis patch contains modifications required by the implementation of the\nNATIONAL DRUG FILE (NDF) package's APIs and the MailMan package's file\nchanges contained in patch XM*7.1*50.\n\n
\nSee the patch description PSO*6*174.\n\n
\nThis is the build for Patch PSO*6.0*154.\n\n
\nThis patch corrects a problem created by PSO*6*174. If an Rx with at\nleast one refill is placed on hold, an undifined error will occur.\n\n
\nThis patch addresses several problems reported via NOIS: \n involved did not include a necessary CMOP cross reference. The cross\n reference has been included.\n \n3) NAN-0498-41811 depicts a condition where an Rx written for a\n controlled substance had a one year expiration date rather than the\n required limit of 6 months. A check has been inserted and the\n expiration date of 6 months is forced on controlled substances.\n \n4) A medical center using Outpatient Version 7.0 noticed that the cancel\n date from an Rx being renewed was transferred to the renewed Rx.\n 1) CLE-0397-41373 describes a situation where editing the QTY field (#7)\n Research disclosed (also for V 6.0) that this was only happening if\n the Rx being renewed was already canceled before the renewing action\n was taken. If, as is normal, the Rx status was changed to cancel\n DURING the renewing action, the cancel date was not transferred to the\n new Rx. The code was modified to delete the old cancel date during\n renewals.\n or the QTY field (# 52.1,1 refill quantity) results in an update of\n the CURRENT INVENTORY field (#50) in the DRUG file (#50). The software\n was modified to prevent updating the CURRENT INVENTORY during edit.\n \n 2) GNH-0298-42078 reports that when attempting to change the suspense\n date for a patient's Rxs using the Change Suspense Date [PSO PNDCHG]\n option, the lookup fails to find the patient's name. The lookup\n\n
\nPSO*6.0*156 provides an interface between Outpatient Pharmacy V 6.0 and\nCIRN V 1.0. The event points within the OP software calls an entry point\nprovided by the CIRN package, EN^RGEQ("RX",IRXN).\n\n\nThis patch makes a functional change to the Partial Prescription [PSO\nRXPAR] option. Partial prescriptions will be prohibited if a prescription\nhas a "canceled", "non-verified", or "pending" status. \n \nThis change is consistent with updated functionality\nincluded in Outpatient Pharmacy V. 7.0.\n\n
\nMiscellaneous patch.\n1) Allow users to reprint Rx's filled at CMOP facilities.\n2) Fix Refill Quantities in Drug Acct\n3)This patch fixes a problem that could occur after processing Rx's in the\nProcess Drug/Drug Interactions option. If any Rx's are processed in this\noption, and the user then goes directly to the New Prescription Entry\noption and enters new Rx's, a duplicate label of the Rx processed in the\nProcess Drug/Drug Interactions option could possibly print. This patch\nfixes the problem.\n\n
\nCMOP/OUTPATIENT PHARMACY enhancement patch to allow users to designate, at\nthe patient level, mailing criteria.\n\n
\nSee the patch description PSO*6*159.\n\n
\nSee the patch description PSO*6*160.\n\n
\n \nThis is the CHAMPUS Billing patch for Outpatient Pharmacy (PSO*6*152).\n\n
\nSee the patch description PSO*6*161.\n\n
\nSee the patch description PSO*6*162.\n\n
\nPSO*7.0*1 - 1.26.97\nmodified. They are: PSOHLNE1, PSOHLNE2, PSOHLNEW, PSOHLSIG, PSOHLSIH,\nPSOHLSN, PSOHLSN1, PSOORUT1, PSON52, PSORN52, and PSORN52C.\n \nPSOREF: Fixed problem on speed refill of invalid Fill Date selection prompts\nif the 1st Rx in the list is expired. In this routine there's an entry\npoint that's used by CPRS to help determine if an Rx is refillable.\nThere's a potential problem when refill requests are made and the Pharmacy\nOrderable Item are missing from the Rx. In order to prevent a\npossible undefined error from occurring an addition check was added to\ndetermine if there's an orderable item is for that drug in the Rx.\n \n \nWhen a refill was in suspense, some cross references were being corrupted\nin the Rx Suspense File. These changes fix that problem. Also added a\ncross reference to the Fill Date field. What this does is if an Original\nFill is in suspense and has not yet been printed, if the Fill Date is\nedited, then we now update the suspense date with the new Fill Date.\nRoutines: PSOUTL, PSOUTLA. The Fill Date field (#22) in the Rx file (#52)\nwill be sent out in this patch.\n \nAdded addition code to prevent refills from being deleted when removing\nPSOCLO1: A problem was reported about Clozapine Rxs and when there are\nRxs from Hold, Routines: PSOUTL, PSOHLD\nvalid lab results. The problem has to do with the lab results being\nreturned as zero when a number should be returned.\n \nAfter the installation of version 7.0 in Washington's production account\na number of allocation errors begin to occur. In an attempt to manage\nthe number of variables in the partition several routines have been\n\n
\n \n \n3. Corrected a possible problem of barcode on and off sequences being changed\nand made invalid for label printers. This could happen if a label device is\nselected, then an Action Profile device is selected, and the site parameter\nis set to print barcodes on action profiles. If there are Rx labels to print\nagain the Barcode On and Barcode Off sequences for the Action Profile printer\nbecome the sequences for the Label printer, which may not work if the printers\nselected are different types. Routines PSOSD, PSOSD1, PSOSDP\n \n 4. Corrected a problem reported when using the Delete a Prescription\n1. Corrected problems with the nightly cost compile jobs. The problems are\n[PSO RXDL] option. If an original fill is released, and a refill is\nentered but not yet released, the user can mark the prescription as\ndeleted without first returning to stock the original fill. Routine PSORXDL\n \nthat the number of requests by patient was not being counted correctly and \na problem with the nightly compile where data for the previous day was being\nreset. Routines: PSOCSTD, PSOCSTM\n \n2. Corrected a problem with the nightly job that compiles the AMIS data. The\nproblem is that all partials was not being counted correctly.\nRoutine: PSOAMIS0\n\n
\n1. If a site has the External Interface outpatient site parameter set to\n will make that correction.\n \n2. This patch will fix errors that can possibly occur when the external\n interface encounters bad prescription data.\n \n3. It was reported by some sites that if the site has multiple dispensing\n machines, when the prescription is entered at one of these machines,\n the same prescription gets transmitted to the other machines. This\n patch is setting the HLL("LINKS") array to dynamically specify one or\n more recipients for the HL7 message to insure that the prescription\n either "2:SEND ALL ORDERS AND DON'T PRINT LABEL" or "3:SEND MARKED \n entered at one of the devices will not be transmitted to the others.\n \n \n ***** NOTE *****\nThe new software design will be using the Dynamic Addressing setup as\ndescribed in the following steps:\n \n1. It is recommended for the site to have only one Client and one Server\n Protocol, and to delete the LOGICAL LINK (LL) field (#770.7) of the\n PROTOCOL file (#101) for those Client and Server Protocols. Then the\n ORDERS AND DON'T PRINT", a problem can occur when issuing a partial\n site would need to create a LL for every "machine" that it has.\n \n2. Deriving the LL for each prescription using the following methods:\n \n a) The software will use the LL entry from the CPRS ORDERING INSTITUTION\n subfile (#59.08) multiple of the OUTPATIENT SITE file (#59) if there\n is a Clinic associated with the prescription, and the Institution\n derived from that Clinic has an entry in this CPRS ORDERING\n INSTITUTION subfile (#59.08) multiple of the OUTPATIENT SITE file \n (#59) with an associated LL.\n prescription. If there is already an original fill or refill suspended \n \n b) The LL on the top level will be used for the prescription in\n the following cases:\n - If there is no Clinic associated with the prescription.\n - If there is a Clinic associated with the prescription, but the\n Institution derived from that Clinic does not have an entry in the\n CPRS ORDERING INSTITUTION subfile (#59.08) multiple of the \n OUTPATIENT SITE file (#59) with an associated LL for that Outpatient\n Site entry.\n \n for a prescription, and a partial prescription is issued, the suspended\n c) If the LL can't be derived through the previous steps then it's\n defaulted to "PSO LLP1" (sent out with Outpatient Pharmacy package).\n fill will be removed from suspense, and the status of the prescription\n will be set to Active when the partial prescription is sent to the \n external interface. The prescription fill should remain in suspense,\n and the status of the prescription should remain Suspended. This patch\n\n\nThis patch replaces all occurrences of *13 with $C(13) in the Outpatient\nPharmacy V. 7.0 package in order to make it vendor independent as per\nSOP 192-104.\n\n
\n1. When finishing a pending order entered through Computerized Patient\nwith the order contains a 2, 3, 4, or 5. This patch makes this change. A\nmessage has also been added that will be displayed during the finish\nprocess only when the quantity is automatically updated by the software,\ndue to edits of any of these fields.\n \n2. There are occurrences throughout the Outpatient Pharmacy package where \nPossible Dosages and Dispense Units per Dose are displayed, and if that \nnumeric data begins with a decimal point, such as ".5," then that is how\nit is displayed, as ".5". This patch will make change to add a leading\nzero to these displays, so ".5" will now be displayed as "0.5". This\nRecord System (CPRS), and fields are edited during the finish process that\nchange will not apply to Local Possible Dosages. It will only apply to\nPossible Dosages and Dispense Units per Dose.\n \n3. When prescriptions are entered that contain Possible Dosages, the Noun \nthat is applied to the Dosing Instruction comes from the DOSAGE FORM file \n(#50.606). If that Noun ends in "(S)" or "(s)", such as TABLET(S) or \nCAPSULE(S), the software will adjust the Noun based on the Dispense Units \nper Dose. For example, if the Noun is TABLET(S), then the software will \nchange the Noun to TABLET if the Dispense Units per Dose is one or \nless, and the software will change the Noun to TABLETS if the Dispense \nare used in the automatic Quantity calculation such as Days Supply or\nUnits per Dose is greater than one. When prescriptions and pending orders \nare edited, this conversion of the Noun does not always take place. This \npatch makes the change to convert the Noun to it's proper form when edits \nare made.\n \n4. When finishing a pending order using either the Patient Prescription \nProcessing [PSO LM BACKDOOR ORDERS] option, or the Complete Orders from\nOERR [PSO LMOE FINISH] option, an undefined error could occur if the\nListMan action "EA Enter/Edit Allergy/ADR Data" is selected to add or edit\nallergy information. This patch fixes this problem.\nSchedule, a recalculation is done on the Quantity of the prescription,\n \n5. There is an order check for drugs with data entered in the MAXIMUM DOSE\nPER DAY field (#4) of the DRUG file (#50), that divides Quantity by Days\nSupply, and if that's greater than the MAXIMUM DOSE PER DAY, an order\ncheck is given. A problem occurred when this order check was given when\nfinishing an order entered through Computerized Patient Record System\n(CPRS). If an '^' is entered at the 'Do You Want to Edit Days Supply and\nQuantity Fields?' prompt, the user will exit the process, but the\nsubsequent prompts for that order are still given, even though the order\nwill not be finished because of the '^' that was entered. This patch will\nwhether the edits created a new order or not. A request has been made to\nsuppress those remaining prompts after the '^' is entered.\n \n6. When an active prescription is copied using the CO Copy (OP) hidden\naction in Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,\nand if the CONJUNCTION field (#5) of the MEDICATION INSTRUCTIONS sub-file\n(#52.0113) of the PRESCRIPTION file (#52) is deleted using the @ key, then\nthe software does not trigger the duplicate drug check and as a result\nduplicate active prescriptions are created. Also it was observed that\ndeleting this field by using the @ key during the process of\ncreating/editing a prescription, the software prompts the question\nnot recalculate the Quantity based on these edits when finishing a pending\n"Deleting this conjunction will delete the dosing sequence that follows!",\neven when no conjunctions are defined. In such a situation this patch will\ndisplay a message "Invalid Entry - nothing to delete" and will loop back\nto the CONJUNCTION field (#5) of the MEDICATION INSTRUCTIONS sub-file \n(#52.0113) of the PRESCRIPTION file (#52) prompt.\norder from CPRS if any of the Schedules associated with the order contain\nPRN, or if the drug is a Schedule 2, 3, 4, or 5, meaning the DEA,\nSPECIAL HDLG field (#3) of the DRUG file (#50) for the drug associated\n\n
\n1. A site reported a problem with the maximum refills calculation for an \nof 7 days even if the pending order had 14 days supply. This patch ensures\nthat the DAYS SUPPLY field (#8) is set to a maximum of 7 or 14 days \ndepending on the DISPENSE FREQUENCY field (#2) of the CLOZAPINE PATIENT\nLIST file (#603.01). NOIS TUA-0302-31000\n \n3. In Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option, if \nthe CO Copy (OP) hidden action is used first and then if a pending order \nis completed, the software displays the clinic name of the CLINIC field \n(#5) of the PRESCRIPTION file (#52) that was in the previous prescription \nthat was copied. This patch corrects this problem. NOIS CON-0602-11684\norder placed through the Computerized Patient Records System (CPRS) V. \n1.0. The problem occurred if a free-text dosage was used. This patch \ncorrects this problem. NOIS UNY-0302-12906\n \n2. When finishing a pending order for a Clozapine drug using either the \nPatient Prescription Processing [PSO LM BACKDOOR ORDERS] option, or the\nComplete Orders from OERR [PSO LMOE FINISH] option, the software sets the\ndefault DAYS SUPPLY field (#8) of the PRESCRIPTION file (#52) to a maximum\n\n
\n1. A potential patient safety issue is being addressed in this patch.\n \n2. This patch corrects a problem where prescriptions are automatically\ndiscontinued by a date of death entry or 3 days after a patient has been\nadmitted to the medical center. The problem occurred when the\nprescriptions are reinstated. The fill dates are not being reset correctly\nto the dates prior to being automatically discontinued.\nCurrently when a date of death is entered into the Date Of Death field\n(#.351) in the Patient file (#2), all active prescriptions are automatically\ndiscontinued. The patient safety issue is when a date of death is entered\nin error, which can cause the patient to missed their next fill because the\nOutpatient Pharmacy system has no way of determining which prescriptions were\nDiscontinued and which ones should be reinstated. This patch and the\nDG*5.3*455 patch will correct this.\n \n\n
\nThis patch is in support of the HUI/VHA CIO SD&D Pharmacy Data \nthis functionality, nothing needs to be done besides installing the \npatch. If sites want to utilize this functionality, more information on \nthe setup and the data elements are documented at:\n \n \nThis patch also fixes a problem of an undefined error that can occur \nwhen entering a new prescription. At the PATIENT INSTRUCTIONS prompt, if \ntext is entered greater than 32 characters in length, without any spaces,\nan error will occur. This patch will fix the error, and the user will now \nbe re-prompted for PATIENT INSTRUCTIONS when this occurs.\nInterchange project. The project provides a method for the one-way \nelectronic transfer of prescription orders from an external system to \nVistA.\n \nThis patch exports the PSO RECEIVE ORDER Protocol, the PSO RECEIVE HL7 \nApplication Parameter, and the PSO LLPO HL Logical Link. These can be \nused to recieve new orders and cancel orders from an outside source into \nthe Outpatient Pharmacy Vista database. If sites do not wish to utilize \n\n
\n \n2. If a prescription is put on HOLD and later on is UNHELD, the user is\n always prompted for "FILL (or REFILL) DATE" and "MAIL/WINDOW". This \n was allowing the user to overwrite the original fill/refill date on\n file, even after the prescription had already been released. This \n was misleading, giving users the impression that the prescription\n would be filled and the labels would print. Since the prescription\n had already been released, the fill and the label print did not \n happen. Once this patch is installed, these two fields will only be\n asked if the prescription (or refill) has NOT yet been released.\n \n1. If a returned to stock prescription is put on HOLD, then UNHELD and a\n3. If one of the copay exemption questions applies to a patient, but has\n never been answered, under the RESET COPAY STATUS/CANCEL CHARGES\n [PSOCP RESET COPAY STATUS] option, the default for the question: "Do\n you want to enter/edit any copay exemption flags? N//" will be changed\n from N to Y.\n \n4. The MailMan message which is generated when a copay exemption question\n applies but has not been answered generated errors at at least one\n site when there was no provider in the prescription. This patch adds a\n check for the provider field being null and if so, does not attempt to\n label prints, the label is not marked as a reprint, so the\n queue the MailMan message to a non-existent provider.\n \n5. When using Backdoor Orders, if the user selected to edit the 'PATIENT\n STATUS' and '# OF REFILLS' (5,11) of a prescription, the possible \n range for number of refills was showing as '(0-999999999999)'. This \n allowed the user to enter any value between '0' and '999999999999'.\n Once this patch is installed this problem will be corrected and the\n actual maximum number of refills will be shown as the maximum value \n for the range.\n \n prescription cannot be released until the label reprint option is used.\n6. When the user tried to delete a single dosage from a set of 4 or more\n dosages (complex dosage), the system was not deleting. It would accept\n the deletion, but when the user tried to accept the changes, it would \n block with the message "dosage missing!". This patch will fix this \n problem and the user will be able to delete such dosages.\n \n7. When an order entered through Computerized Patient Record System\n (CPRS) is finished in Pharmacy, and an edit is made that generates an\n automatic recalculation of the quantity of the prescription, a message\n is displayed to the screen indicating that the quantity has been\n This patch will mark the label as being a reprint and also will set the\n updated. There are also occurrences when the quantity is updated\n automatically and that message is not displayed, such as editing after\n a Copy, or editing after entering a new prescription but prior to\n accepting, or editing after accepting an edit that creates a new order.\n With this patch, the quantity update message will display every time an\n edit is made and a new quantity is automatically calculated.\n \n8. When entering a new prescription, at the PATIENT INSTRUCTIONS prompt,\n if text is entered greater than 32 characters in length, without any\n spaces, an error will occur. This patch will fix the error, and the\n reprinted label indicator in the prescription file so that a returned\n user will now be re-prompted for PATIENT INSTRUCTIONS when this occurs.\n to stock prescription can be released when unheld.\n \n \n\n
\nAssociated patches: (v)PSO*7*95 <<= must be installed BEFORE `PSO*7*115'\nin the PHARMACY PATIENT file (#55)).\n2) Then place an order from CPRS for an outpatient pharmacy patient\nalready in the PHARMACY PATIENT file (#55), but is missing the PATIENT\nSTATUS field (#3) in that file.\n3) Then finish the orders in outpatient pharmacy for the patients in 1)\nand 2) in that order, entering "^" for the Patient Status prompt for the\nsecond patient. The entire entries for the second patient will be deleted\nfrom the PHARMACY PATIENT file (#55), because a local variable from the \nlast new patient still existed.\n \n \nThis patch ensures that the local variable is killed between each patient.\n \nSince the PHARMACY PATIENT file (#55) can contain both inpatient and\noutpatient pharmacy information, the post-install routine will handle\nrebuilding both types. It will send a MailMan message upon completion\nindicating whether any missing entries were found and rebuilt for the\nInpatient Medications V. 5.0 orders or Outpatient Pharmacy V. 7.0\ncross-references. The message will also show the global(s) that contain\nthe affected entries.\nPSO*7*115 fixes a problem which may have caused some entries from the\nPHARMACY PATIENT file (#55) to be deleted. This patch also provides a\npost-install clean-up routine to rebuild any missing entries.\n \n \nBefore this patch, an example of how this problem could happen is:\n1) Place an order in CPRS for a brand new outpatient pharmacy patient (not\n\n
\n \n \n \nPatch PSO*7*129 will create a MailMan message containing a list by patient\nname of any cross references that were rebuilt by PSO*7*115. The subject\nof the MailMan message will be one of the following:\n \nSubj: PHARMACY PATIENT File (#55) NO ENTRIES TO LIST\nSubj: PHARMACY PATIENT File (#55) LIST IN USE\nSubj: PHARMACY PATIENT File (#55) listing of rebuilt entries\n \nPSO*7*115 fixed a problem which may have caused some entries from the\nA MailMan message with the first subject would occur if there was nothing\nin the temporary global created by patch PSO*7*115. That temporary global\nis kept for 30 days. The second subject would occur if the post-install\njob for patch PSO*7*115 is currently running. In this case, the\npost-install job for patch PSO*7*129 can be queued later by running\n^PSOPOST8 from programmers mode.\n \nThe MailMan message is sent to the installer of the patch and holders of\nthe PSNMGR key.\nPHARMACY PATIENT file (#55) to be deleted and a post-installation routine\nin that patch reset the missing entries.\n \nPatch PSO*7*129 should not be installed until the post-install job of\npatch PSO*7*115 has run to completion. When it is complete, a MailMan\nmessage is sent to the installer of PSO*7*115 with a subject line of:\nSubj: PHARMACY PATIENT File (#55) search for missing entries\n\n
\nThe Deputy Undersecretary for Health for Operations and Management (10N) \naudits to discover and correct any patterns of inappropriate address\nchanges. An option created with this patch will facilitate the review of\nthe audits.\n \nAudits consume disk space on the VistA system so audit results cannot be \nstored indefinitely. Pharmacy Managers should negotiate a timeframe for \nthe regular review of the audits so that the audits can be purged from \nthe system when no longer needed. The suggested fields for auditing are:\n \nSTREET ADDRESS [LINE 1] (#.111)\nconvened a task force in April 2002 to review the controlled substance \nSTREET ADDRESS [LINE 2] (#.112)\nSTREET ADDRESS [LINE 3] (#.113)\nCITY (#.114)\nSTATE (#.115)\nZIP CODE (#.116)\nZIP+4 (#.1112)\nTEMPORARY STREET [LINE 1] (#.1211)\nTEMPORARY STREET [LINE 2] (#.1212)\nTEMPORARY STREET [LINE 3] (#.1213)\nTEMPORARY CITY (#.1214)\nprocess in VHA. The task force returned several recommendations. One of \nTEMPORARY STATE (#.1215)\nTEMPORARY ZIP CODE (#.1216)\nTEMPORARY ZIP+4 (#.12112)\n \n \nThe new option exported with this patch is named Patient Address Changes\nReport [PSO ADDRESS CHANGE REPORT], and will be placed under the\nSupervisor Functions [PSO SUPERVISOR] menu option. This option prints a\nreport that shows changes made to the various address fields listed above\nfrom the PATIENT file (#2), over the date range specified. The report can\nthe recommendations was to modify the Outpatient Pharmacy package to \nbe run for one patient, or for all patients. A field can only be tracked\nand shown on this report if the VA FileMan AUDIT function was turned on\nfor the field at the time the field was edited.\nprovide a record of all address changes.\n \nMedical Center Pharmacy Managers are encouraged to contact their IRM and \narrange the regular auditing of changes to address and temporary address \nfields in the Patient file (#2). Pharmacy Managers should monitor these\n\n
\nFixed problem reported in Tuscaloosa, local NOIS PHA-0198-N0090. If a\nand PSODIR3.\n \nIn the Outpatient package there's a Listman action that allows the user to\nprint medication instruction sheets. This action when used does not turn off\nthe Listman screen controls. This patch corrects that. Routine: PSOHELP.\n \nFixed problem reported in Tuscaloosa, local nois PHA-0198-N0104.\nWhen the Autocancel on Admission job ran, it was not canceling\nprescriptions that were issued on the same day as the admission, but\nit should have been canceling them.\nreprint was done in Listman on one Rx in the Patient Prescription\nProcessing option, then the user finished some Rx's in the Complete\nOrders from OERR option, the comments from the reprint would carry over\nto the Label Log entries for the Rx's finished in the Complete option.\nRoutine: PSORXRPT\n \nSAC 2.2.1.1 prohibits parameter passing on the first line.3 routines\nhave formal lists on the first line. Routines: PSOORDRG, PSODIR2,\n\n
\nThe Edit Data for a Patient in the Clozapine Program [PSOL EDIT] option \nand the Register Clozapine Patient [PSOL REGISTER PATIENT] option will no \nlonger check for race, sex, or zip code for Outpatient Pharmacy in the\nClozapine Program. All three checks are no longer necessary.\n\n
\nDescription:\n The primary problem is that when these prescriptions were being\n transmitted to the CMOPs and they were behind on dispensing, the\n prescriptions were being rejected because the prescriptions had\n already expired. The default of 5 is being changed to 30 to\n accommodate the CMOPs and to allow the patients to receive their\n medications in a timely manner. Prescriptions will no longer expire\n before 30 days elapses from the Issue Date when the day supply is\n less than 30 days and there are no refills. If a minimum of 1 refill\n is entered the one year/six month rule still applies.\n \n===========\n \n2. This patch also includes a correction to initialize the line \ncounter for the "SIG1" entries in the PRESCRIPTION file (#52). Before \nthis fix, the count could be incorrect sometimes which could cause\nproblems for external interfaces.\n \n3. This patch corrects a problem that caused a null subscript error. \nThis would happen if records were being created in the PENDING OUTPATIENT\nORDERS file (#52.41) and an attempt was made to pull up the patient's\nmedications in the Computerized Patient Record System (CPRS) at the same\n \nmoment.\n \n1. Currently, if a non-controlled substance prescription is entered with\n a day supply less than 5 days and there are no refills, the expiration\n date defaults to 5 days from the issue date. If a controlled substance\n prescription is entered with a day supply less than 5 days without\n refills, the expiration date is the Issue Date plus the Days Supply.\n\n
\n1) When an order entered through Computerized Patient Record System \nincludes default and maximum values for various fields during the order\nentry process, whether the order is being entered through CPRS V. 3.0 or \nOutpatient Pharmacy V. 7.0. A request has been made to not update the\nPATIENT STATUS field (#3) of the PHARMACY PATIENT file (#55) when the\nPatient Status is edited during the finish process if ADMINISTERED IN\nCLINIC was entered as the Pick Up for the order in CPRS V. 3.0.\n \n2) Outpatient Pharmacy V. 7.0 patch PSO*7*111 introduced new functionality\nthat enables the Outpatient Pharmacy V. 7.0 package to receive New and\nDiscontinue Pharmacy orders from an external system. When these orders are\n(CPRS) V. 3.0 is finished in Outpatient Pharmacy V. 7.0, fields can be\nreceived, an immediate update is then sent from Outpatient Pharmacy V. 7.0\nto CPRS V. 3.0. A problem has been reported on the Discontinue orders,\nwhen the update is sent from Outpatient Pharmacy V. 7.0 to CPRS V. 3.0. In\nsome cases, CPRS V. 3.0 will enter the current user into the DC'ed BY\nfield (#62) in the ORDER file (#100). Since the only defined user on the\nsystem for this process could be the person who started the HL7 filers,\nthis patch makes the change to send the requesting provider as the current\nuser when the discontinue messages are sent to CPRS V. 3.0. This fix will\nonly affect orders received from an external system using the interface\nintroduced in patch PSO*7*111.\nedited during that finish process. One of those fields is the PATIENT\nSTATUS field (#3) of the PRESCRIPTION file (#52). When this field is\nedited during the finish process, not only does that field get updated for\nthat prescription, but the PATIENT STATUS field (#3) of the PHARMACY\nPATIENT file (#55) also gets updated. Then when the next prescription is\nentered for that patient, the PATIENT STATUS field (#3) of the PHARMACY\nPATIENT file (#55) is used as the default Patient Status, and that\n\n
\nAfter installing patch PSO*7*107, some sites have reported problems in\nBaker 2000, etc. If your site is using any class 3 software, please get\nthe corrections for these dispensing machines before installing this\npatch.\nprinting labels, notably when there are bar codes in the label. In patch\nPSO*7*107, we replaced the carriage return control code *13 with $C(13) to\nmake it vendor independent. The problem is that the $C(13) under DSM/VMS\ndoes not initialize the column position to zero. This patch fixes this\nproblem.\n \nPlease note: This patch and the associated patch PSO*7*107 are not \ncompatible with class 3 software for automated dispensing machines such as\n\n
\nThe purpose of this patch is to support the implementation of Internet \nPrescription Refill for Outpatient Pharmacy V. 7.0. This request has links\nto the Health eVet project that will provide a mechanism to obtain copies\nof key portions of their medical record, personalize that record with\nrelevant educational information and provide links to electronic service\ndelivery capabilities, such as prescription refills. The veteran will be\nable to request a prescription refill and review his prescription profile\nby using a web based interface on the internet.\n\n
\nWhen performing drug lookups, two issues were identified. First, the user\n \n Select DRUG: hep\n Lookup: VA DRUG CLASS CLASSIFICATION\n HEPARIN ANTAGONISTS BL200\n HEPARIN ANTAGONISTS\n Lookup: DRUG NATIONAL DRUG CLASS\n PROTAMINE SULFATE 5ML INJ BL200\n ...OK? Yes// N (No)\n \n Lookup: DRUG GENERIC NAME\nwas not aware of which item was being matched. For example, was the match\n \n 1 HEPARIN 1,000 UNIT/ML 10ML INJ BL100\n 2 HEPARIN 1,000 UNITS/ML 30ML BL100\n 3 HEPARIN 10,000 UNITS 4ML BL100\n 4 HEPARIN BEEF 1,000 UNITS/ML 30ML BL100\n 5 HEPARIN, LOCK 100 UNIT/ML 1ML BL100\n Press <RETURN> to see more, '^' to exit this list, OR\n CHOOSE 1-5:\n 6 HEPATITIS-B IMMUNE GLOBULIN IM500\n CHOOSE 1-6:\nfor the GENERIC NAME of the drug or was it the SYNONYM. The second issue\nhad to do with the search matching to the NATIONAL DRUG CLASS NAME first,\nbefore checking for a GENERIC NAME. This patch makes two changes to the\ndrug lookup. First, the search will display the item being searched on.\nSecond, if one or more matches are found on an item, but the user doesn't\nselect one of the matches displayed, the search will continue through all\nother items. A sample screen display follows:\n\n
\n1. When Pharmacy orders are entered through Computerized Patient Record \nSystem (CPRS), certain order checks are performed by Pharmacy during \nthis process. One of the order checks is the duplicate drug class order\ncheck. The software is currently looking for an exact match of the 5\ncharacters that make up the drug class. It should only look for a match of\nthe first 4 characters. This patch corrects the problem.\n\n
\n1. When actions are not allowed to be taken on a specific order in\n \n2. When completing renewal orders entered through Computerized Patient\n Record System (CPRS), there is a possibility of getting an undefined\n variable PSOX("STATUS") error. This error occurs if the prescription \n was originally entered through Outpatient Pharmacy, and the DEA,\n SPECIAL HDLG field (#3) of the DRUG file (#50) of the drug made it\n renewable, but not refillable. Then if that order is renewed through\n CPRS, the error can occur when Pharmacy finishes that order. This patch\n fixes this problem.\n \n Outpatient Pharmacy because that order is being acted upon by another\n3. Duplicate active prescriptions are being found in Outpatient Pharmacy,\n due to an order being renewed through CPRS at the same time a fill for\n that prescription is being transmitted to Consolidated Mail Outpatient\n Pharmacy (CMOP). A check is being added with this patch to not allow\n the renewal of an Outpatient order through CPRS if that order has a\n fill being loaded for transmission to the CMOP. The message that will\n show to the provider will be "Rx is loading into a CMOP transmission".\n user, a message is sometimes displayed that does not say who the other\n user is that has that order locked. This patch will change the message,\n wherever possible, to display the name of the user that has that order\n locked. All of the places where this message is displayed within the\n Outpatient Pharmacy package could not be fixed with this patch, because\n some of the routines were already in other patches. The changes will be\n made in those other places by those other patches.\n\n\n1. One site has reported an excessive number of prescriptions getting\n \nThis patch corrects the problem but will not do any back-billing.\nInformation gathered from the results of this patch will be used by the\nVHA Central Office to determine whether back-billing will be done for\nthese fills. A subsequent patch may be released to perform this\nback-billing.\n \n a. At release of a fill, if the Service Connected flag has a "Yes"\nanswer, a call will be made to Integrated Billing to see if the Service\nConnected question even applies for this patient anymore. If not, the\nautomatically (incorrectly) changed at release from Copay to No Copay\nanswer will be set to null in Outpatient Pharmacy and an update\ntransaction will be sent to CPRS to change their copy of the answer to\nnull.\n \n b. A post-install job will loop through all released prescriptions\nstarting from 02/04/2002 (the date that the $7 copay amount went into\neffect) and will tally the number of fills that could have been billed.\nThe results of this patch will be maintained in a temporary location for\na limited time in order to speed the processing of any eventual\nback-billing.\nwith a reason of "Service Connected". It was determined that this is\n \n \nA MailMan message with a subject of "Subj: Patch PSO*7*137 Copay tally"\nwill be sent to the patch installer and holders of the PSO COPAY key\nindicating the number of fills that have a potential for being\nback-billed.\n \nA second MailMan message will be sent to developers of the patch on FORUM\nwith a subject of "Subj: 'institution' - COUNTS. This message will\ncontain formatted tallies of fills eligible to be back-billed for 2002\nhappening because the Service Connected question does not apply for the\nand 2003.\n \nThe MailMan messages will not contain any patient information.\n \n2. A problem was encountered when a patient who had previously reached\nhis annual copay cap had activity that brought his copay amount below the\nannual cap. When that happens, Integrated Billing (IB) will look for any\nprevious fills that weren't billed because of the cap and will attempt to\nbill for those. The problem occurred when the previous unbilled fill had\nbeen returned to stock, Outpatient Pharmacy had an error in the process\npatient anymore, but the Computerized Patient Record System V. 1.0(CPRS)\nthat should have sent a cancel for those "potential bills" (fills that\nwould have been billed if the patient had not already reached his annual\ncopay cap), so IB attempted to initiate a charge for those. On returned to\nstock refills, the refill level is removed from the prescription file, so\nfiling the IB-initiated charge caused undefined errors.\n \nSolution:\nThe canceling portion of the return to stock processing was corrected to\nhandle "potential charges".\npasses the Service Connected question's answer from the renewed from or\ncopied from prescription to Outpatient Pharmacy V. 7.0.\n \nSolution:\n\n
\nThe purpose of this patch is to provide the ability to print Outpatient \nPharmacy V. 7.0 prescription labels on laser printers. The output will \ninclude the Patient Medication Information sheets.\n \nThe new functionality will only be available on printers properly defined \nin the TERMINAL TYPE file (#3.2).\n\n
\n1. This patch will attempt to make more POSSIBLE SIGS acceptable when\n3. This patch also fixes a problem of the Log of Suspended Rx's report not\nalways showing the correct routing.\n \nfinishing CPRS entered orders in Outpatient Pharmacy. It will cut down\non the number of POSSIBLE SIGS that start "TAKE TAKE", and also cut down\nthe number of times the Dose Form noun is repeated, "TABLETS TABLETS".\n \n2. This patch fixes the problem of the last refill being deleted when an\nRx is canceled or expired, after that refill had been transmitted to the\nCMOP.\n \n\n
\n \nthey should have been.\n \nSolution:\nThe post-install job for patch PSO*7*137 identified potential prescription\nfills that should have charged a copay. The starting date for examining\nwhether the released fills should have been charged a copay was\n02/04/2002 (the date that the $7 copay amount went into effect). A\npost-install job for this patch will use the global created by patch\nPSO*7*137 to do the back-billing for the identified fills. If the global\nhas been removed from the system, the identification portion will be done\nOne site reported an excessive number of prescriptions getting\nagain by the post-install of this patch before doing the back-billing.\n \nA MailMan message with a subject of "Subj: Outpatient Pharmacy Copay\nClean-up" will be sent to the patch installer and holders of the PSO COPAY\nkey indicating the number of fills that were successfully billed. If any\nfills were billed, the MailMan message will contain information on how to\nprint a report by patient name of prescription fills that were billed.\n \nA second MailMan message will be sent back to FORUM to some outpatient\npharmacy developers. This MailMan message's information will be compiled\nautomatically (incorrectly) changed at release from Copay to No Copay\nwith messages from other sites and forwarded to the Austin Automation\nCenter for their use in addressing a mail-out to the veterans affected by\nthe back-billing.\nwith a reason of "Service Connected". It was determined that this was\nhappening because the Service Connected question does not apply for the\npatient anymore, but the Computerized Patient Record System (CPRS) V. 3.0\nsends the Service Connected question's answer from the renewed from or\ncopied from prescription. For non-service connected veterans, prescription\nfills that were flagged as Service Connected were not charged a copay when\n\n
\n1. This patch contains a post-install job, which will correct a status\n \n For deleted Outpatient Pharmacy V. 7.0 orders, the post-install \n job will change CPRS V. 1.0 orders with an active status to a status of\n deleted and will also change the stop date in CPRS V. 1.0 to the date\n deleted if the CPRS V. 1.0 status is Discontinued by Provider.\n \n2. This patch also corrects the problem of an extra delimiter being\n stored in the PRESCRIPTION file (#52) if an up-arrow (^) was entered\n for the LOT# field (#24) when editing a prescription. A symptom of this\n problem is a null subscript error when trying to access the DIVISION\n mismatch between Outpatient Pharmacy V. 7.0 orders which have been\n field (#20) of the PRESCRIPTION file (#52).\n \n The post-install job will look for any entries with a null division and\n if the positions of the date fields appear to be shifted, it will\n remove the extra delimiter from the PRESCRIPTION file (#52).\n \n \n Upon completion of the post-install job a MailMan message will be sent\n to the patch installer with a subject of "Subj: Outpatient/CPRS Status\n clean-up". The message will indicate how many mismatched statuses were\n deleted and the corresponding orders in the Computerized Patient Record\n corrected and how many prescriptions with missing divisions were\n corrected.\n \n \n 3. During the building of the Patient Profile through the Patient \n Prescription Processing [PSO LM BACKDOOR] option, one of the \n criteria for forcing the Status to SUSPENDED of prescriptions \n that had an entry in the RX SUSPENSE file (#52.5) was at times\n found to be incorrect. If the entry in the RX SUSPENSE file\n (#52.5) was flagged as not printed, the software would force the\n System (CPRS) V. 1.0. The initial problem could have occurred if the\n prescription status to SUSPENDED. After this patch is installed,\n the software will also check if the prescription has already been\n transmitted to Consolidated Mail Outpatient Pharmacy (CMOP) V. 2.0\n system, and if so, the status will not be changed.\n \n4. When trying to edit a prescription, and the edit is not allowed \n because either the order or patient is locked by another user, the \n message indicating that the order or patient is locked will not always \n contain the person's name that has the lock. This patch corrects the \n problem.\n Outpatient Pharmacy V. 7.0 package mistakenly sent an "active" message\n \n5. When the user edited a prescription in such a way that caused a new\n prescription to be created, the new prescription was not being \n displayed in the Bingo Board. This patch corrects the problem.\n The prescription number from the previous edit could be associated to\n the next patient's list of prescriptions to be listed on the Bingo\n Board. This patch also corrects this problem.\n to CPRS V. 1.0 on an old order, making it active in CPRS V. 1.0 when it\n should be Discontinued, Expired, or Canceled. Patch PSO*7*86 updated\n the status in CPRS V. 1.0 for orders that were Canceled or\n Discontinued.\n\n
\n1. During testing of PSO*7*120, it was discovered that there was a \n3. In preparation for future enhancements to language handling within \nlabel print, a change was necessary to allow the bottle label information \nto print in a different language from the one on the pharmacy fill \ndocument. This patch makes this change.\n \n4. The final contract award for the laser label stock made a slight \nmodification to the location of the perforation about the fill document. \nThis patch makes the modification to the printer setup routine to \naccomodate this change.\nproblem with the entry of 'y' at the prompt "Print adhesive portion of \nlabel only? ". The lowercase 'y' was being treated as a NO response. This \npatch corrects this problem by handling either upper or lower case YES, \nYE or Y as yes.\n \n2. A problem was found with the documentation of the Integration \nAgreements in routine PSOLLU2. This patch corrects this problem.\n \n\n
\n1. This patch provides new functionality that allows the Veteran Affairs \n2. This patch also addresses the following NOIS issues: \n \na) ISB-0702-32646 \n \nFor drugs that have possible dosages, if the dosage is edited using Patient\nPrescription Processing [PSO LM BACKDOOR ORDERS] option, the software\ncalculates the new DISPENSE UNITS PER DOSE field (#1) of the MEDICATION\nINSTRUCTIONS sub-file (#113) of the PRESCRIPTION file (#52), accordingly. At\nthe confirmation prompt that follows immediately if you respond "NO",\nmeaning not to accept the new value, the software does not revert the\nMedical Centers to print a patient's prescription bottle label in another \nDISPENSE UNITS PER DOSE field (#1) back to it's original value. This patch\nfixes this issue. \n \nb) CAH-0402-31866 \n \nWhen entering a new prescription using the Patient Prescription Processing\n[PSO LM BACKDOOR ORDERS] option, if that prescription is discontinued before\nit goes to the label queue prompt, currently, the label "LABEL QUEUE/CHANGE\nPRINTER/SUSPEND or '^' to bypass Q//" is prompted. If this is the only order\nin that session then there is no label to print and therefore the label queue\nlanguage. This functionality is accomplished by identifying which patients\nprompt should not be displayed. This patch fixes this problem. \n \nc) ISH-0902-40182 \n \nBetween the time an order was placed in Computerized Patient Record System\n(CPRS) V.1.0 and the time the order is processed in the backdoor pharmacy,\nif the dispense drug is made inactive, then there is a possibility of\ngetting an undefined error if a "?" is entered when editing the dosage\nprompt . Since the drug is inactive the software does not gather the\navailable dosages and as a result the undefined error. In order to process\nhave another language preference. To identify patients as having another\nsuch an order (avoiding the undefined error), this patch will provide the\nuser the option of making a free text dosage entry. \n \nd) LIT-1102-71356 \n \nWhen a site merges two patients together, the PHARMACY PATIENT file (#55)\ncontains all of the prescriptions from the "merged from" patient and the\n"merged to" patient under the internal entry number of the "merged to"\npatient. The old patient's internal entry number is kept in the PRESCRIPTION\nfile (#52) for any prescriptions that were originally filed with that\nlanguage preference use the Update Patient Record [PSO PAT] option and the\nnumber. If a new prescription is ordered for a drug that is already in the\nprescription profile, the order entry process will discontinue the old\nprescription correctly. The problem is that if the discontinued order\nbelongs to the old patient internal entry number, the new prescription order\nis filed with the old patient's internal entry number in the PHARMACY\nPATIENT file (#55) and the PRESCRIPTION file (#52) and doesn't appear on the\nprescription profile. This patch corrects this problem. \n \n3. A more descriptive message will now be given to the user when an order is\naccessed, and that order is locked by another user, when copying a \nPatient Record Update [PSO PATIENT RECORD UPDATE] protocol action and enter\nprescription, selecting a pending order, discontinuing a prescription, and\nprocessing a non-verified prescription. \n \n4. If pre-POE prescriptions are renewed or edited to create a new prescription,\nthe resulting prescription may have a missing SIG. This patch corrects the\nproblem. \nYes in the new field OTHER LANGUAGE PREFERENCE field (#106) in the PHARMACY\nPATIENT file (#55). \n \n\n
\nThis patch is a partner patch with the Consolidated Mail Outpatient\n \nSolution: Several steps have been taken to reduce the time needed for\ntransmissions. A special index built with 'type' and 'division' has been\nadded to CMOP INDICATOR field (#3) in the RX SUSPENSE file (#52.5) that\noptimizes the picking of prescriptions for each transmission.\n \n2. Problem: In support of the Hawaii DoD project, Pharmacy Data \nManagement (PDM) needs to know when changes are made to entries in the \nDRUG file (#50). To meet this need a call needs to be made to PDM V. 1.0 \nroutine PSSHUIDG at line tag DRG whenever an edit is made to the DRUG \nPharmacy V. 2.0 (CMOP) patch PSX*2*41. PSO*7*126 must be installed before\nfile (#50).\n \nSolution: The routine PSOCMOP has been modified to call the PDM routine \nPSSHUIDG\nwhen an edit is made to the DRUG file (#50).\n \nEnvironmental Check:\n====================\nAn environmental check routine will run to check if the RX # (#.01) field\nin the RX SUSPSENSE file (#52.5) is populated before continuing with\nthe CMOP patch at remote facilities. This patch will be adding new data \ninstall. If this field is missing, the following message will appear:\n \nChecking the RX Suspense file for missing .01 fields.\n \n667 (A list of entry numbers that are missing the #.01 field)\n...\n \nThe Suspense file #52.5 has been found to have entries without a .01\nfield.\nPlease call NVS to clear this problem.\ndictionaries to be used in conjunction with the CMOP patch PSX*2*41.\n<CR> - to continue:\n \nYou will need to log a NOIS to National Vista Support (NVS) to have this\nproblem resolved before the installation can continue.\n \n1. Problem: VISNs have been combining facilities and the running time of\ntransmissions is becoming very long. The number of divisions has grown\nto about fifty in the largest VISN. This means 100 transmissions must be\nprocessed each day.\n\n
\n \nthe copay charge is held for 90 days before going out in the patient\nstatement. If the patient had coverage on the release date, the copay\nbills and insurance bills should be reviewed to determine if the\ncopayment charge is applicable because of possible insurance payment.\n \nIf the copay charge should be credited, it can be removed by using the\nReset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS] option.\n \nThe temporary global ^XTMP("PSOCPIB3" from the patch PSO*7*123 install is\nkept for 90 days, so this report must be run within that time frame. To\nThis patch provides a report listing all back-billed patients from patch\nrun the report, enter D ^PSOCPIB5 from the programmer's prompt. It prints\nin 80-column format and can be queued to print.\nPSO*7*123. For each back-billed copay fill it indicates whether the\npatient had prescription insurance coverage as of the release date and/or\nbilled date for the fill. If the copay charge has been cancelled since\npatch PSO*7*123 was installed, that information appears instead of the\ninsurance information.\n \nIf the patient had prescription insurance coverage on the billed date,\n\n\nPharmacy Benefits Management (PBM) Strategic Healthcare Group in \nKernel V. 8.0\nComputerized Patient Record System (CPRS) V. 1.0\nPharmacy Data Management (PDM) V. 1.0\nOutpatient Pharmacy (OP) V. 7.0\nControlled Substances (CS) V. 3.0\n \nThis is the PSO patch that provides the following new functionality.\n \n1. This Outpatient Pharmacy patch contains the software changes to process\n digitally signed orders entered via the Computerized Patient Record\ncollaboration with the Drug Enforcement Administration (DEA), requested\n System (CPRS) V. 1.0 for schedule II controlled substances. This patch\n lays the foundation for the future implementation of the Public Key\n Infrastructure (PKI) once the Drug Enforcement Administration's (DEA)\n regulations are revised and published, and will not be fully functional\n in this patch.\n \n2. This patch will ensure that no refills will be allowed for any\n Outpatient Pharmacy prescription for a drug that contains an "F" in the\n DEA SPECIAL HDLG field (#3) of the DRUG file (#50). This NON REFILLABLE\n ("F") code was introduced by the Pharmacy Data Management (PDM) V. 1.0\nthe development of the first Public Key Infrastructure (PKI) VistA pilot\n patch PSS*1*61.\nproject, named Electronic Prescription Order Entry for Schedule II\nControlled Substances. The objective is to develop an electronic order\nentry system for Schedule II controlled substances using digital\nsignatures. To make this project viable, modifications to the following\npackages were identified:\nNational Drug File (NDF) V. 4.0\n\n\nThis is the Phase I patch of the Transitional Pharmacy Benefit Project\n1) The patient must be a veteran.\n(3) Documentation can also be retrieved from VISTA Documentation Library\n(VDL) on the Internet at the following address,\nhttp://www.domain.ext/vdl.\n \n2) The veteran must be enrolled for VA health care system before\n July 25, 2003.\n \n3) Before July 25,2003, the veteran must have requested their first \n primary care appointment with the VA.\n \n4) The veteran must have no active prescriptions dispensed by the local \n VHA pharmacy, excluding Supply and Investigational items, for the past \n(TPB). This project provides functionality for the "Medication Prescribed \n 485 days from October 22, 2003.\n \n5) The veteran must be waiting more than 30 days for their first \n appointment with a Primary Care Physician on or after October 22, \n 2003, or the veteran is deemed eligible via an Electronic Wait\n List/Scheduling extract run at each local site.\n \n \n \nThis patch is being sent out as a combined build, along with patch \nby Non-VA Physicians" to accommodate the Veterans Health Administration \nSD*5.3*300.\n \n \nOutpatient Pharmacy will provide the following functionality in this \npatch:\n \n1. A Post-Install routine will scan through the PATIENT file (#2)\nand the SD WAIT LIST file (#409.3), and will populate the new Outpatient\nPharmacy TPB ELIGIBILITY file (#52.91) with patients eligible for the\nTransitional Pharmacy Benefit. Patients will either be entered into the\n(VHA) Directive 2003-047 that allows Department of Veterans Affairs (VA) \nfile as eligible, or ineligible. If they are entered into the file as\nineligible, an exclusion reason will also be entered into the file. Please\nrefer to the documentation for more details.\n \nThe average run time of the Post-Install at the test sites was 1 hour.\n \n \n2. The following new options are provided in this patch:\n a. A new report option, TPB Patient Report [PSO TPB PATIENT REPORT], \n will be provided to display the patients in the TPB ELIGIBILITY file\nto furnish medications from non-VA physicians. It mandates that for\n (#52.91). Various sort criteria are provided.\n b. The Transitional Pharmacy Benefit Patient Enter/Edit [PSO TPB \n PATIENT ENTER/EDIT] option will allow sites to add new patients, and\n edit existing patients. Note: This option will be set initially to\n "Out of Order", until the post-install runs to completion.\n c. The TPB Institution Letter Enter/Edit [PSO TPB INSTITUTION LETTERS]\n option allows the user to edit each TPB institution's information\n elements that are to be printed on the letters to be sent to the\n patients.\n d. The Report TPB Patients Letters Printed/NOT Printed [PSO TPB LETTERS\neligible veterans that meet certain criteria, VHA will fill prescriptions\n PRINTED REPORT] option provides the user the ability to generate a\n report of patients' letters printed or not printed.\n e. The Print TPB Patient Letter(s) [PSO TPB PRINT LETTERS] option\n provides the ability to print TPB letters to be sent to patients.\n \n \nKIDS Build and Documentation Retrieval:\n======================================================\n \nThe KIDS Build and VISTA documentation are available on the \nwritten by non-VA physicians and dentists. To determine eligibility, a\nANONYMOUS.SOFTWARE directory at one of the following Office of Information\n(OI) Field Offices.\n \n \nSites may retrieve documentation in one of the following ways:\n \n(1) The preferred method is to FTP the files from\n download.vista.domain.ext, which will transmit the files from the \n first available FTP server.\n \npatient must meet the following criteria:\n(2) Sites may also elect to retrieve documentation directly from a\n specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n \nThe software distribution includes: \n \n \n FILE NAMES DESCRIPTION\n \n PSO_TPB_ELIGIBILITY_1_0.KID KIDS Build \n PSO_7_P145_IG.PDF Installation Guide\n PSO_7_UM_R0803.PDF User Manual\n PSO_7_P145_UM_CP.PDF User Manual Change Page Document\n PSO_7_TM_R0803.PDF Technical Manual\n PSO_7_P145_TM_CP.PDF Technical Manual Change Page Document\n PSO_7_P145_RN.PDF Release Notes\n \n\n
\nThis patch contains enhancements in support of drug-drug interaction\norder check exclusions. In addition, the National Drug File patch PSN*4*70\nis required to support this function. When both patches are installed,\ndrug-drug interactions will be excluded for specifically identified drugs.\nThe list of drugs and VA products flagged for exclusion can be found using\nthe options Local Drugs Excluded from Drug-Drug Interactions and VA Products\nExcluded from Drug-Drug Interactions contained on the National Drug File\nReports menu within the National Drug File.\n\n
\nThis is the Outpatient Pharmacy patch, (Phase II), for the Transitional\ndomain is needed for the Health Level Seven (HL7).\nin the NEW PERSON file (#200) must be set to 'No'. Any prescription\nentered, verified, or completed through this option will be flagged as a\nTPB RX.\n \n \n8. When patients or prescriptions are selected or presented in the \nfollowing options, and the patient is eligible for the TPB benefit, a \nwarning will be given that this patient is eligible for the Transitional \nPharmacy Benefit. This warning is given because any new order created \nthrough these options for a patient eligible for the TPB benefit will not \nextracts of the TPB Patient information.\nbe flagged as a TPB prescription, since the new option, PSO TPB RX ENTRY\n[TPB Rx (Prescription) Entry] was not used:\n \nPatient Prescription Processing [PSO LM BACKDOOR ORDERS]\nComplete Orders from OERR [PSO LMOE FINISH]\nEdit Prescriptions [PSO RXEDIT]\nBarcode Batch Prescription Entry [PSO BATCH BARCODE]\n \n \n9. Anytime a prescription is discontinued, a check will be done on that \n \nprescription and patient. If the prescription is a TPB prescription, and \nthe patient is still eligible for the Transitional Pharmacy Benefit, and\nthat patient has no more active TPB prescriptions, then the INACTIVATION\nOF BENEFIT DATE field (#2) of the TPB ELIGIBILITY file (#52.91) will\nautomatically be set to the current date, making that patient ineligible\nfor the benefit. Also, the INACTIVATION REASON CODE field (#3) of the TPB\nELIGIBILITY file (#52.91) will automatically be set to 'ALL RX'S \nINACTIVE'.\n \n \n \n10. Anytime a patient is inactivated in the TPB ELIGIBILITY file \n(#52.91), a check will be done on the default Rx Patient Status for that \npatient on the PATIENT STATUS field (#3) of the PHARMACY PATIENT file \n(#55), and if that Rx Patient Status is 'NON-VA', it will be set to null.\n \n \n11. When entering new prescriptions through either the Patient \nPrescription Processing [PSO LM BACKDOOR ORDERS] or the Complete Orders \nfrom OERR [PSO LMOE FINISH], the Rx Patient Status of 'NON-VA' will not \nbe selectable, since these orders cannot be flagged as TPB prescriptions.\n2. A Post-Install routine is included that will scan the TPB ELIGIBILITY\nfile (#52.91) and check each patient to see if that patient is flagged\nwith a DATE OF DEATH entry in the PATIENT file (#2). If that patient has a\nDATE OF DEATH entry, and the patient is still active in the TPB\nELIGIBILITY file (#52.91), that patient will be marked inactive in the TPB\nELIGIBILITY file (#52.91).\nPharmacy Benefit Project (TPB).\n \n \n3. A new 'NVA' code has been added to the SC/A&A/OTHER/INPATIENT field\n(#6) of the RX PATIENT STATUS file (#53), to distinguish prescriptions \nentered as part of the TPB project. The field will now be named\nSC/A&A/OTHER/INPATIENT/NVA. The 'NVA' code will automatically be assigned \nto the 'NON-VA' Rx Patient Status entry that is being exported with this \npatch.\n \n \n \n4. A new field named TPB RX, field (#201), has been added to the \nPRESCRIPTION file (#52). The software will automatically set this field \nto 'Yes' for any prescription that meets all of the TPB requirements.\n \n \n5. The following fields were added to the NEW PERSON file (#200) by Kernel\npatch XU*8.0*311:\n \n53.91 NON-VA PRESCRIBER\n53.92 TAX ID\n1. An Environment check routine is included in the patch, and the install \n53.93 EXCLUSIONARY CHECK PERFORMED\n53.94 DATE EXCLUSIONARY LIST CHECKED\n53.95 ON EXCLUSIONARY LIST\n53.96 EXCLUSIONARY CHECKED BY\n \nThe following Outpatient Pharmacy options have been modified to allow the \nediting of these new fields in the NEW PERSON file (#200):\n \nAdd New Providers [PSO PROVIDER ADD]\nEdit Provider [PROVIDER EDIT]\nwill be aborted if either of the following 2 conditions are met. If you\nView Provider [PSO PROVIDER INQUIRE] \n \n \n6. The following fields have been added to the PHARMACY SYSTEM file \n(#59.7). These fields will be used by the HL7 extracts of TPB Patient \ninformation:\n \n46.1 TRANSMISSION START DATE\n46.2 TRANSMISSION END DATE\n46.3 BATCH CONTROL ID\nalready have an entry named 'NON-VA' in the RX PATIENT STATUS file (#53),\n46.4 NUMBER OF MSH COUNT\n46.5 NUMBER OF LINES COUNT\n \nThe HL7 extract will automatically be done on all patients upon initial \npatch install, then the job will be automatically queued to run every \nevening at 6:00pm, and the extract will check the day of the week, and \nonly send data on Sundays. In addition to the fields listed above, the \npatch also exports the following to enable the HL7 extracts:\n \nOPTION:\nthe install will be aborted, because this patch exports an entry with that\n PSO AUTOQUEUE JOBS \n PSO TPB HL7 EXTRACT\n \nPROTOCOL:\n PSO TPB EV \n PSO TPB SUB\n \nHL7 APPLICATION PARAMETER:\n PSO TPB-AAC \n PSO TPB-PHARM\nsame name. If you have not created an entry in the DOMAIN file (#4.2) \n \nHL LOGICAL LINK:\n PSOTPBAAC \n \n \nThe TPB HL7 Data Extract/Transmission [PSO TPB HL7 EXTRACT] option has \nbeen added to the jobs that can be requeued from the Queue Background \nJobs [PSO AUTOQUEUE JOBS] option.\n \n \nnamed "TPB-AUSTIN.DOMAIN.EXT", the install will be aborted, because that\n7. A new stand-alone option, PSO TPB RX ENTRY [TPB Rx (Prescription)\nEntry], is being exported with this patch. This option will provide the\ncapability to enter TPB prescriptions for TPB eligible patients. Included\nin this option will be the ability to enter/edit Provider Information, \nand the ability to enter/edit Allergy information. Only patients eligible\nfor the TPB benefit will be selectable through this option. When entering\nthe prescription information, the RX Patient Status must be 'NON-VA', and\nthe Provider that is selected for the prescription must meet the following\n2 criteria: the NON-VA PRESCRIBER field (#53.91) in the NEW PERSON file\n(#200) must be set to 'Yes', and the ON EXCLUSIONARY LIST field (#53.95)\n\n
\nThis patch is being issued to bring the critical documents into compliance\nwith the Year 2000 mandate. Some of the key documents are Rx labels and\naction profiles.\n\n
\n Problem: \n The Patient Merge patch XT*7.3*73 fixed this problem to appropriately\n update the PATIENT field (#2) in the PRESCRIPTION file (#52) for\n future patient merges. Patch PSO*7*136 has a environment check routine\n PSOPI136 to update this field with the correct patient's internal\n entry number ("merged to"). At the completion of this job, a MailMan\n message with the subject "PSO*7*136 PRESCRIPTION file (#52) - Patient\n Merge clean up", will be sent to the installer notifying the start\n time and time of completion. The message will provide a list of\n prescriptions with the corrected patient's internal entry number.\n It will also list prescriptions that had the CPRS status adjusted to\n ========\n match the Pharmacy status.\n \n The Patient Merge process was not updating entries in the PRESCRIPTION \n file (#52) with the new patient's internal entry number (IEN).\n \n Solution:\n =========\n \n\n\n \n exist.\n \n NTE|3|\n :\n \n7. WIM-0603-20338\n The Print from Suspense File [PSO PNDLBL] option allows an user\n to queue the printing of the labels at a later time by Taskman. A\n problem was found when the original task was re-queued through the\n Taskman Requeue Tasks [XUTM REQ] option by a different user. Once\n the labels printed, the label print activity log for the prescription\n \n was recorded as being performed by the second user, the one who\n re-queued the Taskman task, which is wrong. This patch makes the\n correction to keep the user who queued the label print through the\n Print from Suspense File [PSO PNDLBL] option in the label print\n activity log.\n \n8. MAC-0603-60315\n Patch PSO*7*124 introduced the following change:\n \n Currently, if a non-controlled substance prescription is entered\n \n with a day supply less than 5 days and there are no refills, the\n expiration date defaults to 5 days from the issue date. If a\n controlled substance prescription is entered with a day supply\n less than 5 days without refills, the expiration date is the\n Issue Date plus the Days Supply. The primary problem is that\n when these prescriptions were being transmitted to the CMOPs and\n they were behind on dispensing, the prescriptions were being\n rejected because the prescriptions had already expired. The\n default of 5 is being changed to 30 to accommodate the CMOPs and\n to allow the patients to receive their medications in a timely\n2. CLA-0303-20198\n manner. Prescriptions will no longer expire before 30 days\n elapses from the Issue Date when the day supply is less than 30\n days and there are no refills. If a minimum of 1 refill is\n entered the one year/six month rule still applies.\n \n This created a problem for some sites with a rehab unit where some\n patients go out on Authorized Absence every weekend. The site then\n enters a prescription with a patient status of AUTHORIZED ABSENCE and\n no refills and a small number for days supply (3 or 4 days). Before,\n such prescriptions expired within 5 days from the issue date and no\n The Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] option was\n longer showed on the Medication Profile screen. Now, after PSO*7*124\n was installed, such prescriptions remain active for at least 30 days.\n The result is that multiple prescriptions for a single drug are listed\n in the Medication Profile screen. Active prescriptions with a patient\n status of AUTHORIZED ABSENCE can contain the same drug already in\n another active prescription for the same patient.\n Once this patch is installed, prescriptions with a patient status of\n AUTHORIZED ABSENCE and no refills will have the expiration date\n calculation reversed to a minimum of 5 days from the issue date,\n instead of the 30 days introduced by patch PSO*7*124.\n initially provided to synchronize the expired order status between\n \n9. PUG-0603-50491\n This NOIS call reported a problem with the patient security check for\n the Complete Orders from OERR [PSO LMOE FINISH] option. An example of\n a patient security check is when an employee tries to get access to\n his own medical record and is denied. In the case of the menu option\n mentioned above, such security checks were not being performed when\n the user selected to process ALL the patients with pending orders.\n Also, when processing by clinic, route or priority, there were no\n security checks performed. The only time the security checks were\n Outpatient Pharmacy prescriptions and Computerized Patient Record\n performed was when the user selected to process a single patient.\n When this patch is installed, this problem will be resolved and the\n Complete Orders from OERR [PSO LMOE FINISH] option will perform the\n security checks consistently for all the possible selections when\n finishing pending orders.\n \n10. CON-0703-11685, MAR-0703-21567 & SBY-0703-31538\n When trying to reinstate discontinued prescriptions for a patient that\n had the DATE OF DEATH field (#.351) in the PATIENT file (#2) entered\n and then deleted, the user was getting an "Undefined variable DA"\n System (CPRS) V. 1.0 order entries. And as such, the start date was set\n error. This problem was introduced by patch PSO*7*117, more\n specifically by the changes described in item #2b which was made to\n address NOIS call CAH-0402-31866. This patch corrects the problem\n with the use of that variable.\n \n11. MIN-1202-40079, FRE-0303-60233 & RIC-0603-21344\n In some situations where a patient is being accessed by Inpatient\n Pharmacy Version 5.0, if an attempt is made to finish orders in\n Outpatient Pharmacy Version 7.0, a message is received that the\n patient is in use. Then if an "^" is entered for the PATIENT STATUS\n to the date Outpatient Pharmacy Version 7.0 was installed minus 120\n prompt, the cross-reference entries in the PHARMACY PATIENT file (#55)\n could be deleted for that patient. This patch corrects the problem. A\n follow-up patch will provide a clean up to rebuild missing\n cross-references.\n \n12. HUN-0603-21419 & WPB-0803-30273\n There has been some instances where a prescription from one patient\n was being displayed on the Bingo Board for a different patient. This\n patch kills a variable that could accidentally get carried over \n between patients.\n days. A few sites have reported that some of the very old\n1. BIR-0203-30502\n prescriptions, specifically those that are 120 days prior to the date\n Outpatient Pharmacy Version 7.0 was installed, show an active status\n when viewed via FileMan. In order to scan the PRESCRIPTION file (#52)\n and flag such orders as expired, this option has been modified to\n provide the user the flexibility to select a start date and the default\n is set to the date Outpatient Pharmacy Version 7.0 was installed minus\n 120 days.\n \n3. CLE-0303-42391\n This NOIS call reported that the PROVIDER COMMENTS field (#39) of the\n This NOIS call reported the following software error that happened\n PRESCRIPTION file (#52) was being lost when a prescription was renewed\n from Outpatient Pharmacy. A correction was made to send the comments to\n CPRS when the prescription is renewed from Outpatient Pharmacy.\n \n4. ISB-0403-31630\n This NOIS call reported a problem in the display of Allergy severity\n in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n option, on the Detailed Allergy Display screen. The content of the\n field "Severity:" was limited to one, and only one, value. The possible\n values were: MILD, MODERATE or SEVERE. The first Severity on file was\n with a FastFill machine:\n displayed. Since it is possible to have more than one Severity per\n Allergy, this display was changed to show all the Severities on file,\n along with the dates on which each one was observed. See example below:\n \n Before: Severity: MODERATE\n \n Now: Severity: 04/07/03 MODERATE\n 04/15/03 MILD\n 04/17/03 SEVERE\n \n \n Besides the changes to this display, the HL7 message for External\n Interfaces was also changed. The ZAL segment will have one for each\n severity observed. Before, it would have only one entry for the\n oldest severity observed. Furthermore, the date the severity was\n observed is being added as field #8 of this segment. From the same\n example from above, here is how the ZAL segment will look:\n \n Before:\n ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MODERATE\n \n $ZE= ACK+2^PSOHLSG:1, %DSM-E-UNDEF, undefined variable HL("APAT"),\n Now:\n ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MODERATE|20030407|\n ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MILD|20030415|\n ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|SEVERE|20030417|\n \n5. ANN-0902-40951\n An undefined error was reported when using the Patient Prescription\n Processing [PSO LM BACKDOOR ORDERS] option. If the drug of an active\n order is edited, but the user quits without saving the changes and a\n new order for the same drug is placed immediately afterwards, the error\n -DSM-I-ECODE, MUMPS error code: M6\n could occur. This patch fixes this issue.\n \n6. LAS-0503-60830 & BRX-0603-11755\n The "NTE|2|" segment in the HL7 message generated for external\n interfaces is composed by the concatenation of the following Freetext\n fields from the OUTPATIENT SITE file (#59) in this order:\n \n Field # Name\n ------------------------------------------\n 1005 NARRATIVE FOR REFILLABLE RX\n \n 1006 NARRATIVE FOR NON-REFILLABLE RX\n 1004 NARRATIVE FOR COPAY DOCUMENT\n \n When building this segment, the routine PSOHLSG2 was skipping one line\n between the content of each field. This line is being interpreted by\n some external interfaces, such as Optifill, as the end of the "NTE|2|"\n segment, because all it contains is a carriage return character. This\n caused the external interface to reject messages with only a carriage\n return in the line. To solve this problem a blank space will be\n inserted between the content of each field. In the example below, the\n The routine was corrected to reinitialize the variable if it does not\n blank space will be added where the arrow ("->") is pointing.\n \n :\n NTE|2|\n Call in your refill on your touch-tone phone.\n Outside the metropolitan area: 1-800-123-4567.\n ->\n The copay required is $7.00 for every 30 day or less supply of\n medication or $21.00 for a 90-day supply. Be sure to indicate your\n complete SSN on your check.\n\n\n1. If pre-Pharmacy Ordering Enhancements prescriptions are renewed or\nedited to create a new prescription, the resulting prescription may have a\nmissing SIG. This patch corrects the problem for edited prescriptions.\nOther Pharmacy V. 7.0 patches have made the correction for renewals.\n \n2. This patch also corrects a null subscript error that happens if the\nfull patient name is entered in the Bingo Board User [PSO BINGO USER]\noption.\nNOIS - SBY-0803-31924\n\n
\n1. A site reported a problem with printing labels with long SIGs. If \ncontained SIG instructions that ran over one label. On the 2-n copies, \nnot all of the SIG printed correctly. This patch corrects this problem by \nappropriately printing all of the SIG information on all copies.\nNOIS: MON-0703-50217, MAD-0603-41794, SPO-0603-50792, MAC-0803-60872\n \n3. A site reported a problem that long mailing addresses were being \ntruncated on the mailing label. This patch corrects this problem by \nadjusting the font size lower until the entire address will print. \nNOIS: NIN-0803-40514\n \nthere were no spaces in the SIG, the label print would get into an \n4. A site reported a problem with a long drug name overflowing onto the \nwarning label section. This patch corrects this problem by adjusting the \nfont size down until the drug name fits on the bottle label. In addition, \na utility is included to build the information into the TERMINAL TYPE \nfile (#3.2) for bolding the drug name at different fonts. Once the patch\nis installed, run the routine PSOLLU3 in programmer mode. Once you have\nupdated all current laser label devices, the routine may be deleted.\nNOIS: TOM-0503-41452 \n \n5. A site reported a problem with receiving an error if there was a TAB \ninfinite loop. This patch corrects this problem by making the SIG print \ncharacter in the SIG text. This patch corrects this problem by handling \nthe entry of non-visible characters. NOIS: BRX-0703-12341, \nWPB-0703-32079, SBY-0703-30153\n \n6. A site reported a problem with the printing of the Method of Pickup \ninformation. It was being truncated if it was over about 20 characters. \nThis patch corrects this problem by adjusting the font and allowing this \ninformation to print on multiple lines. NOIS: ANN-0503-42213 \n \n7. A problem was discovered with printing the narrative information on \nbreak on spaces and commas. If there are no spaces and no commas, the SIG \nthe label. Under certain conditions, the text would not wrap correctly. \nThis patch corrects this problem by wrapping on the character size if the \ntext between spaces is too long for the allocated area on the label.\n \n8. A site reported a problem with adjusting the left margin of the laser \nlabel print. The 'Qty' header wouldn't properly adjust. This patch \ncorrects this problem by adding the ability to move the line that prints \nquantity information. NOIS: IRO-0503-40327\n \n9. A site reported a problem of no physician name or an incorrect name \nprint will break on a character basis. \nprinting on the bottle label. This happened if the SIG was too long to \nfit on the bottle label, but was not too long to fit on the filling \ndocument. This patch corrects the problem. NOIS: SHR-0703-72297, \nCLL-0803-41010\nNOIS: SAM-0703-21864, SAM-0703-21873, IND-0703-41198, FAV-0603-70287, \nMUS-0603-70207, SBY-0503-32205, CTX-0803-71468\n \n2. A site reported a problem when printing multiple copies of labels that \n\n
\n \nScripTalk(R) Talking Prescriptions will provide the ability for VA points\nof care to purchase and distribute adaptive equipment to patients who are\nunable to read the traditional label on prescription bottles. This patch \nprovides a way to print to a microchip-embedded label that can be applied \nto a medication bottle. When the label is held next to a ScripTalk(R) \nreader, the reader will read the contents of the label aloud to the \npatient. This improves patient safety for patients with substantial loss \nof vision as it allows them to safely determine the contents and \nadministration schedules of their medications.\n \nThis patch contains routines, new options, new Data Dictionary fields, and\nScripTalk(R) is a registered trademark of En-Vision America.\n \nIn addition to the ScripTalk changes, this patch corrects some laser\nlabels formatting problems in the warning label and method of pick-up\nsections. \n \nNOTE: As part of the laser labels corrections, the utility routine that \nwas used in patch PSO*7*141 has been modified. A correction for the return\nmail initialization control code in the TERMINAL TYPE file (#3.2) has been\nadded. Once the patch is installed, run the routine PSOLLU3 in programmer\ndocumentation for implementing the ScripTalk(R) 'talking' prescription\nmode. Once you have updated all current laser label devices, the routine\nmay be deleted.\nlabels functionality, which will greatly benefit visually impaired\nveterans.\n \nThanks to Rob Silverman at Hines for his extensive research and\ndevelopment work for a class III solution, upon which this patch is based.\n \n\n
\n1. A new code has been added to the INACTIVATION REASON CODE field (#3)\nin an HL7 message to Austin. This patch exports a new mail group, PSO TPB\nHL7 EXTRACT. Members of this mail group will receive weekly mail messages\nconcerning the HL7 extract of TPB patient information. These messages\nwill either display information that the message generation was\nsuccessful, or display information that the message generation was\nunsuccessful, along with a reason why it was unsuccessful. Upon install,\nthe installer will be prompted for the coordinator of the mail group. The\nPost-Install routine of this patch will automatically add the patch\ninstaller as a member of the mail group.\n \nof the TPB ELIGIBILITY file (#52.91). The code is PATIENT UNREACHABLE.\nThe Post-Install routine PSO153PS will also set the AUTOSTART field (#4.5)\nof the HL LOGICAL LINK file (#870) of the PSOTPBAAC HL Logical Link to\n"Enabled".\n \nA correction has been made to the HL7 message to distinguish between\na new record and an edited record.\n \n3. The weekly HL7 transmission to Austin is found to cause problems at few\nsites due to some bad "AX" cross-references of the TPB ELIGIBILITY file\n(#52.91). This patch fixes this issue.\nThis code will now be selectable when manually inactivating a patient\n \n4. There is a possibility of getting a null subscript error when using the\nView Provider [PSO PROVIDER INQUIRE] option to view the provider details\nafter either of the following circumstances:\n \na. When a new provider was added using the Add New Providers [PSO PROVIDER\n ADD] option, and "No" was the response to the NON-VA PRESCRIBER field\n (#53.91) of NEW PERSON file (#200).\nb. When a Provider was edited using the Edit Provider [PSO PROVIDER EDIT]\n option, and "No" was the response to the NON-VA PRESCRIBER field\nfrom the TPB ELIGIBILITY file (#52.91). It will also display, when\n (#53.91) of NEW PERSON file (#200), and then an "^" was entered prior\n to responding to the prompts for these fields of the NEW PERSON file\n (#200):\n TAX ID field (#53.92)\n EXCLUSIONARY CHECK PERFORMED field (#53.93)\n DATE EXCLUSIONARY LIST CHECKED field (#53.94)\n ON EXCLUSIONARY LIST field (#53.95)\n EXCLUSIONARY CHECKED BY field (#53.96)\n \nThis patch corrects the error.\nappropriate, on the reports generated by the Report TPB Patients Letters\n \n5. When selecting a provider using the TPB Rx (Prescription) Entry [PSO\nTPB RXENTRY] option, if the provider is unauthorized to write med orders\nor flagged as inactive, there are currently no alerts or warnings\nindicating that the provider cannot be selected. This patch will provide\none of the following messages during provider selection if such conditions\nare encountered:\n \na. This Provider is not Authorized to Write Med Orders. Use the Edit\n Provider [PSO PROVIDER EDIT] option to change the Authorization flag.\nPrinted/NOT Printed [PSO TPB LETTERS PRINTED REPORT] option, and the TPB\n \nb. This Provider is flagged as Inactive. Use the Edit Provider\n [PSO PROVIDER EDIT] option to change the Inactive Date.\n \nc. This Provider is not Authorized to Write Med Orders and flagged as\n Inactive. Use the Edit Provider [PSO PROVIDER EDIT] option to change\n them.\n \n6. The FAX NUMBER field (#.136) of the NEW PERSON file (#200) has been\nadded to the following options, for display and for editing:\nPatient Report [PSO TPB PATIENT REPORT] option.\nAdd New Providers [PSO PROVIDER ADD] option\nEdit Provider [PSO PROVIDER EDIT] option\nView Provider [PSO PROVIDER INQUIRE] option\n \nThis enhancement is requested by E3R 18457.\n \n7. This patch provides an API to the Scheduling V. 5.3 package that\nreturns a list of all patients eligible for the TPB, to be used for\nreporting purposes.\n \n2. Every Sunday, Transitional Pharmacy Benefit (TPB) patient data is sent\n\n
\n1. Currently, the HealtheVet system invokes the Outpatient Pharmacy\nenhancement.\n \nFurthermore, besides the information that Outpatient Pharmacy V. 7.0 \ncurrently returns to the HealtheVet system, it is also requested that two\nnew fields be made available to them: Outpatient Pharmacy Division and\nPrescription Refill Status. This patch provides this information in the\nrequested format.\n \n2. The HealtheVet team has requested an additional Outpatient Pharmacy\nV. 7.0 Application Program Interface (API) to provide Outpatient Pharmacy\nV. 7.0 application to order a prescription refill and to check the status\ndivision information. The information requested is Inactive Status,\nDivision Name, Area Code, Phone Number, and Refill Narrative Text. This\npatch makes the required information available.\n \nNote: Sites installing this patch will not notice any changes unless they\nare using the HealtheVet Internet Prescription Refill system.\nof the prescription refill process. The required input parameters include\nIntegration Control Number (ICN), Social Security Number (SSN), and\nPrescription number (Rx #). This has caused a duplication in functionality\nand slow response time. To help speed up the process, a minor enhancement\nhas been requested that will eliminate the use of ICN and remove the cross\nchecking of SSN because the HealtheVet system itself verifies the accuracy\nof the SSN and supplies the patient number. This patch would provide this\n\n
\nSince the release of patch PSO*7*146, Transitional Pharmacy Benefits \nPharmacy's AMIS Report option [PSO AMIS] and Daily AMIS Report option \n[PSO DAILY AMIS] will be modified to display this field in a new NVA \ncolumn.\n \nIf you install this patch and wish to include all past prescriptions with \na Patient Status of Non-VA for past dates, you must run the Recompile \nAMIS Data option [PSO AMIS RECOMPILE].\n \nKeep in mind that if you ran the AMIS report in the past, the counts will \nbe different when you re-run the report for that past date, since the \n(TPB), there has been an increase in the number of prescriptions which \ncompile will now include prescriptions with a pharmacy patient status of \nNon-VA. Also note that the recompile is system intensive and should be \nrun after hours.\nhave a pharmacy patient status of Non-VA. Pharmacy's current AMIS Report \noption [PSO AMIS] and Daily AMIS Report option [PSO DAILY AMIS] do not \ninclude Non-VA prescriptions in any of their counts. \nThis patch will modify the Compile AMIS Data (NIGHT JOB) option [PSO AMIS \nCOMPILE] and the Recompile AMIS Data option [PSO AMIS RECOMPILE] to \ninclude the Non-VA prescription counts in a new NVA field (#17) in the \nDIVISION multiple (#59.11) of the OUTPATIENT AMIS DATA file (#59.1). \n\n
\nThis is the Outpatient Pharmacy patch for the Transitional Pharmacy Benefit\n wrong Outpatient Pharmacy prescription processing options, such as\n provider the patient was not prescribed any medication, his/her\n TPB eligibility remained active, when in reality it should have \n been inactivated.\n \n Solution: A Post-Install process will search for TPB eligible patients \n and automatically inactivate the TPB eligibility of the \n patients that fulfill both of the following\n requisites:\n \n a) Patient does not have any "active" TPB prescription(s) on\n the Patient Prescription Processing [PSO LM BACKDOOR] option and Complete\n file. The prescription statuses considered as "active"\n are the following:\n ACTIVE, NON-VERIFIED, HOLD, DRUG INTERACTIONS, SUSPENDED\n and PROVIDER HOLD. \n \n AND\n \n b) Patient has had an appointment at a designated TPB Clinic\n (determined through a set of clinic stop codes) since the\n date his/her TPB benefit began.\n Orders from OERR [PSO LMOE FINISH] option.\n \n Report: At the end of this process, a Mailman message will be sent to\n the new mail group PSO TPB GROUP. The patients reported on this \n message were inactivated as TPB patients by the Post-Install\n process The fields reported on this message are: PATIENT NAME,\n LAST 4 DIGITS OF SSN, APPOINTMENT DATE/TIME, VA CLINIC NAME.\n \n 3) PATIENT'S TPB BENEFIT INACTIVATION (ENHANCEMENT - CONTINUOUS PROCESS)\n ---------------------------------------------------------------------\n Outpatient Pharmacy software will be notified by the Scheduling software\n \n every time a patient has an appointment at a VA clinic. If the patient\n is eligible for the TPB benefit, the appointment was at a designated TPB \n Clinic (determined through a set of clinic stop codes) AND the patient\n does not have any "active" (see list of statuses on item #2a above) TPB \n prescription(s) on file, this patient will have the TPB eligibility \n automatically inactivated. A Mailman message will be sent to the PSO TPB\n GROUP mail group with the following information:\n \n The following patient had the TPB (Transitional Pharmacy Benefit)\n Benefit automatically inactivated because the following appointment\n b) Patients who did not wish to take advantage of the TPB benefit or who are\n was found: \n \n Patient : LAST,FIRST(9999)\n VA Clinic : EAST MIDWAY CLINIC\n Appointment Date: DEC 02, 2003@11:15\n \n 4) REPORT OF PATIENTS WITH TPB AND NON-TPB Rx's (NEW REPORT)\n [PSO TPB PATIENT RX REPORT]\n ---------------------------------------------------------\n This new report is being released as a stand-alone option. It will \n not prescribed medication after a VA appointment are still active for\n print a list of TPB eligible patients that have "active" TPB and\n Non-TPB prescriptions on file. The report can be for ALL or selected \n institutions, as well as for ALL or selected TPB patients. It will be\n sorted by the INSTITUTION NAME first, then by the PATIENT NAME. There\n will be a page-break for each individual institution. The column\n headings on the report are: PATIENT NAME (LAST4SSN), VA Rx#, TPB Rx#, \n DRUG NAME. This report should be assigned to the site TPB Coordinator,\n Pharmacy ADPAC and any other individual deemed appropriate by the site.\n \nIn order to allow the unflagging of TPB prescriptions as described in 1) \n the TPB benefit in the system. The inactivation of the TPB benefit is \nabove, the TPB RX (#201) field in the PRESCRIPTION (#52) file is being \nchanged from "UNEDITABLE" to "EDITABLE". \n automatic when the last active TPB prescription is discontinued either \n through an Outpatient Pharmacy package action or through an action taken\n in CPRS. The entry of a prescription/order will not inactivate the \n(TPB) project. This phase consists of automated processes and additional\n benefit unless the result is that the last active TPB prescription is\n discontinued as a result of the new entry. \n \nThis patch is comprised of four components that will help the sites identify\nand fix the data discrepancies described above. It will also provide them \nwith new tools to monitor events that could have an impact on patient's TPB\neligibility. And in some cases the patient's TPB eligibity will be updated\nautomatically.\n \nBelow is a detailed description of each component:\ntools designed to assist the sites for which Transitional Pharmacy Benefit\n \n 1) MARKING TPB PATIENT Rx's AS TPB (ONE-TIME PROCESS - POST INSTALL)\n -----------------------------------------------------------------\n Problem: Because some prescriptions have been entered through the\n wrong menu options (see item a) above), these Rx's have not \n been correctly identified as TPB prescriptions. In other \n words, they have a different patient status than "NON-VA" AND\n do not contain a TPB flag in PRESCRIPTION file (#52), and \n therefore, are not identifiable as prescriptions filled\n under the TPB program.\ndata have not been accurately reported.\n \n Solution: A Post-Install process will search for prescriptions filled\n under the TPB program which are not marked as such and\n will mark these prescriptions as TPB. The two requisites \n that must be fulfilled for a prescription to be marked as \n TPB, are:\n \n a) The prescription was entered during the period that\n the patient's TPB benefit was active.\n \n \n AND\n \n b) The provider for the prescription is a "NON-VA"\n provider.\n \n If the requisites above are fulfilled, the following \n updates will be done for the prescription:\n \n a) Patient status will be changed to "NON-VA".\n b) If an UNIQUE TPB clinic is identified (STOP CODE\nTwo of the most common events that have contributed to the discrepancies\n equals 161) for the site, clinic will be changed to\n this clinic.\n c) The TPB flag will be set in PRESCRIPTION file (#52).\n \n Report: At the end of this process, a Mailman message will be sent\n to the newly created mail group called PSO TPB GROUP. The \n patients reported on this message had at least one Prescription\n edited by the Post-Install process. The sites will have the\n ability to enter the coordinator of this new mail group at time\n of installation of this patch. Even if the coordinator is not\nin the TPB data are:\n entered, this patch assures that at least the installer of the\n patch is a member of the mail group. The fields reported on this\n Mailman message are: PATIENT NAME(LAST4SSN), Rx#, DRUG NAME, \n PROVIDER NAME, CLINIC (Old and New) and the Rx PATIENT STATUS\n (Old and New).\n \n Important: If the site identifies prescriptions on this report that\n have been wrongly flagged as TPB, it is possible to manually\n remove the TPB flag from such prescriptions through FileMan.\n Just repeat the steps below for each prescription you wish\n \n to remove the TPB flag (as in this example):\n \n VA FileMan 22.0\n \n Select OPTION: ENTER OR EDIT FILE ENTRIES \n \n INPUT TO WHAT FILE: PRESCRIPTION\n EDIT WHICH FIELD: ALL// TPB RX \n THEN EDIT FIELD:\n \n a) TPB prescriptions have been entered for TPB eligible patients via the\n Select PRESCRIPTION RX #: 123457690A TYLENOL 250MG\n TPB RX: YES// @\n SURE YOU WANT TO DELETE? Y (Yes)\n \n \n \n 2) INACTIVATING PATIENT'S TPB BENEFIT (ONE-TIME PROCESS - POST INSTALL)\n --------------------------------------------------------------------\n Problem: Since not all patients eligible for the TPB program chose to\n take advantage of the TPB benefit or, after seeing the VA \n\n
\nSBY-1003-30858\n Outpatient Pharmacy Version 7.0, a message is received that the\n patient is in use. Then if an "^" is entered for the PATIENT STATUS\n prompt, the cross-reference entries in the PHARMACY PATIENT file (#55)\n could be deleted for that patient.\n \nThis patch has a post install clean-up routine that will:\n \n1. Look for entries in the PHARMACY PATIENT file (#55) affected by the\n problem above and will rebuild the missing cross-references.\n \nPrescriptions are not seen in Patient Prescription Processing \n2. Once the cross-reference is rebuilt for a specific patient, the post\n install will check if the patient has been merged and in case the\n patient's prescriptions still contain the old patient internal entry \n number, it will correct them with the new patient number in the \n PRESCRIPTION file (#52). The database problems caused by\n patient merges have been fixed by PSO*7*136, however, patient entries\n in the PHARMACY PATIENT file (#55) with the problem above, could have\n been missed by PSO*7*136 cleanup job. \n This step of this cleanup will make sure these entries are fixed.\n \n[PSO LM BACKDOOR ORDERS] option and in Computerized Patient Record System \nDuring Installation of this patch the user will be asked: "Queue the\nPost-Install to run at what Date@Time: ". If the prompt is not \nanswered, the patch WILL NOT be installed. After the post install\nroutine is run to completion at the time the user indicated, a MailMan\nmessage with the subject "PHARMACY PATIENT File (#55) missing entries"\ncontaining the list of prescription cross-references rebuilt will be sent\nto the person installing the patch. The prescriptions will then appear in\nthe Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option and\nthe CPRS Meds Tab if they are not past their expiration date.\n(CPRS) Meds Tab but are seen in View Prescriptions [PSO VIEW] option and \nCPRS Orders Tab.\n \nPSO*7*139 corrected the following problem:\n In some situations where a patient is being accessed by Inpatient\n Medications Version 5.0, if an attempt is made to finish orders in\n\n
\n1. When using the Patient Record Update [PSO PATIENT RECORD UPDATE]\n \ninstalled, that prescription will show on the unreleased report, even\nthough a Filling label never printed.\n \n12. This patch fixes an error that involves incorrect medications showing\nup on a Medication profile for a patient. This can occur if there is\ninvalid data in the PHARMACY PATIENT file (#55). A patient validation\ncheck is being added to prevent this problem. Also in the Medication\nprofile, an error could occur if a profile is run on a patient, and the\norders for that patient have not yet been backfilled to CPRS. This error\ncan only occur shortly after the installation of Outpatient Pharmacy\n3. Corrected a problem reported in NOIS ALB-0498-50730 associated with\nversion 7.0.\nthe Medication Profile [PSO P] option. The problem happens when the\nreport is sorted to print by Class or Medication and a cutoff date (number\nof days) is entered, the Rxs that have been canceled print beyond the\nselected number of days. Routine: PSOP2\n \nCorrected another problem reported in NOIS CON-0798-11780 when printing\nthe Med profile by a selected date range. The problem is that when a date\nrange is entered the first time and the user attempts to run the report\naction, the site parameter that controls the editing of Patient\nagain and chooses a date range earlier that the initial date, the user is\nnot allowed to do so. Routine: PSOP1\n \n4. Corrected a problem where a possible undefined error could occur when\nthe cross reference on the DATE OF DEATH field (#.351) on the PATIENT file\n(#2) is executed. The problem could occur when the APOSD cross reference\nis executed. Routine: PSOCAN3\n \n5. Added a 'Press Return to Continue' prompt when using the Speed Release\naction. The problem was when there were many Rx's to be released, the Rx\nInformation Management System (PIMS) patient data was being ignored.\nnumber scrolled off the screen. For users without scroll back\ncapabilities, this caused users to question as to what Rx's were being\nreleased. Routine: PSODISP3\n \n6.When editing the original Fill Date of a prescription that is in\nsuspense and queued for Consolidated Mail Outpatient Pharmacy (CMOP)\ntransmission, it is possible that duplicate "AQ" cross references will\nexist for that suspense entry. This could cause the prescription to be\nsent to the CMOP twice. In addition to fixing this problem, any invalid\n"AQ" cross references will be deleted by this patch. Routines: PSOUTLA,\nRoutine: PSOLMPAT\nPSOPOST3\n \n7.This patch addresses a problem reported by some sites concerning the\nComplete Orders from OERR [PSO LMOE FINISH] option. Currently under this\noption, the site will only see Pending Outpatient orders that have a\nRelated Institution that matches the Related Institution for the\nOutpatient Site that the user is signed in under. The problem occurs when\nan order is received from Computerized Patient Record System (CPRS) from a\nClinic that is related to an Institution that is not found as a Related\nInstitution for any of the Outpatient Pharmacy sites. When this happens,\n \nthe only way for those orders to be completed is for the user to select\nthat patient under the Patient Prescription Processing [PSO LM BACKDOOR\nORDERS] option.\n \nTo fix this problem, this patch adds a new field to the OUTPATIENT SITE\nfile (#59) called CPRS ORDERING INSTITUTION (#8). Multiple entries can be\nentered in this field. This can be done using the Site Parameter\nEnter/Edit [PSO SITE PARAMETERS] option. Upon installation of this patch,\na conversion is done to move the Institution that is currently in the\nRelated Institution field for each Outpatient Site to the first entry in\n2. This patch will enable the interface between Outpatient Pharmacy\nthis new field. After the installation of the patch, if there is still\nonly one entry in the new CPRS ORDERING INSTITUTION field (#8) for an\nOutpatient Site, then the Complete Orders from OERR [PSO LMOE FINISH]\noption will not change for the user. However, sites can now enter multiple\nInstitutions in this field for an Outpatient Pharmacy site, and if a site\ndoes this, the user will be prompted for an Institution when entering the\nComplete Orders from OERR [PSO LMOE FINISH] option. After the user selects\nan Institution, then the Pending Orders that will be shown to the user for\ncompleting will be those Pending Orders from Clinics that are associated\nwith that Institution selected.\nversion 7.0 and the Clinical Information Resource Network (CIRN) once CIRN\n \n8. A problem has been reported concerning the Order Summary that is\ndisplayed after selecting the RX (Prescriptions) [PSO RX] option. The\nfirst number displayed is the "Orders to be completed for all divisions".\nThen the user can choose to view an order summary, which breaks down all\nof the orders by Routing, (Window, Mail, and Clinic). The problem is that\nthe total of the "Orders to be completed for all divisions" does not\nalways match the total of the breakdown by routing. The reason is that not\nall Renewals that are received from CPRS have an associated routing. To\nresolve this, when Outpatient Pharmacy receives a Renewal from CPRS with\nis installed. There will be no change in functionality for Outpatient\nno routing, a Mail routing will automatically be entered for the Renewal.\nThis patch will also automatically update any current Pending Renewals\nwith no routing to a Mail routing.\n \n9. This patch fixes a problem of the patient not always being displayed\non the Bingo Board automatically when using the Release Medication\n[PSO RELEASE] option.\n \n10. This patch provides a new sort capability when using the Complete\nOrders from OERR [PSO LMOE FINISH] option. Orders can now be Finished by\nPharmacy sites that do not have CIRN installed.\nClinic, or by Clinic Sort Group. Within either of these sorts, orders will\nbe Finished on a first in/first out basis by Patient. Clinic Sort Groups\ncan be added/edited in the Enter/Edit Clinic Sort Groups [PSO SETUP\nCLINIC GROUPS] option, which is found under the Maintenance (Outpatient\nPharmacy) [PSO MAINTENANCE] menu option.\n \n11. This patch fixes a problem of a prescription showing up on the\nunreleased report, when only an Interaction label printed, and not a\nFilling label. If a prescription is entered before the version 7.0\ninstall, and a Drug Interaction label printed, then version 7.0 is\n\n
\nThere is one occasion where in the Outpatient Pharmacy application\n are entered through through CPRS, Rx B and Rx C. Rx B is a \n duplicate of Rx A. When finishing Rx B, an order check happens\n and Rx A is DC'd. Select Rx C and select to edit the Patient \n Instructions field. If this field was NULL before, it will now\n show a default value, which is the content of the Patient \n Instruction field from Rx A ("FOR ALLERGIES").\n \nThis problem will be corrected by installing this patch. \nwhere the PATIENT INSTRUCTIONS field content from one prescription \ncan be carried over to another prescription automatically. This \nproblem was identified in the Complete Orders from OERR [PSO LMOE\nFINISH] and Patient Prescription Processing [PSO LM BACKDOOR] menu \noptions. The scenario that this problem happens is the following:\n \n Patient has Rx A, which is active and the Patient Instructions \n field is not NULL (e.g. "FOR ALLERGIES"). Two new prescriptions\n\n\n1. Scheduling V. 5.3 package is moving the patient appointment information\nthe patient appointment information in the Action Profile (132 COLUMN\nPRINTOUT) [PSO ACTION PROFILE ] option, with the new APIs.\n \n2. NOIS OKL-0204-7052\nThe Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE ] option is\nsupposed to list only the active med orders if zero is entered for the\nprompt "Profile Expiration/Discontinued Cutoff: (0-9999): 120//", but\nit also shows discontinued med orders. This patch ensures that if the\ncutoff days is zero, only the active med orders will be listed. For\nall other cutoff days the report will show the discontinued and expired\nstored in the APPOINTMENT sub-file (#2.98) of the PATIENT file (#2) and \nmed orders.\nthe APPOINTMENT sub-file (#44.001) of the HOSPITAL LOCATION file (#44) to\nthe Government Off-the-Shelf (GOTS) database. Eventually, these sub-files\nwill be deleted from the Scheduling files. As part of the Scheduling\nReplacement Project, Scheduling V. 5.3 package is providing a series of\nApplication Programmer Interface calls (APIs) that will be used to get the\npatient appointment information from the new GOTS database. This is the\nOutpatient Pharmacy V. 7.0 patch that replaces all direct references to\n\n
\n1. OKL-1202-71318\n Yes//'. When selecting 'Yes', the software does not update the changes.\n This patch fixes this problem.\n \n2. MOU-1202-31080\n Using Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,\n when the drug of an active order is edited, the software checks for the\n change and prompts 'Do You want to Edit the SIG? NO//' and accordingly\n alerts the user with the message 'This change will create a new\n prescription!'. During the completion process of new orders entered\n through Computerized Patient Record System (CPRS), if the drug is\n When using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n edited, the software currently does not make any such checks on the\n edited drug. This patch ensures that the same functionality that is\n provided to the drug edits of an active order, is incorporated into the\n drug edits during the completion of orders entered through CPRS.\n Also the completion of pending order process is enhanced in this patch\n to display the message "Pending Order Not Updated!" in the message box\n when an up-arrow (^) is entered at any of the dosage prompts to quit\n the process. This is similar to "Prescription Not Updated!" message\n that is provided when quitting during an edit of an active order with\n an up-arrow (^).\n option to edit the dispensed drug on an active order, if there is more\n \n3. CLL-0403-41585\n When using the Patient Prescription Processing [PSO LM BACKDOOR\n ORDERS] or the Complete Orders from OERR [PSO LMOE FINISH] option, to\n complete orders entered through Computerized Patient Record System\n (CPRS), you cannot edit the Orderable Item using the synonym of that\n Orderable Item. This patch corrects this problem.\n \n4. HWH-0303-40364\n When entering complex orders using Patient Prescription Processing\n than one drug tied to that Orderable item, if a different drug is\n [PSO LM BACKDOOR ORDERS] option, if an up-arrow (^) and 3 characters\n are entered at the conjunction prompt in order to correct one of the\n dosage fields, the software goes into an endless loop going back to the\n beginning of the complex dosage. This happens only if the 3 characters\n entered do not point to one of the dosage fields. This patch fixes this\n problem. We also fixed the following related issue: Currently, to jump\n to the Limited Duration field within the dosage edit, you need to enter\n "^DUR" or "^dur", not "^LIM" or "^lim", as expected by many users. This\n patch provides the option of entering "^LIM" or "^lim" or "^DUR" or \n "^dur", to jump to the Limited Duration field.\n selected from the displayed drug list, the software prompts 'Do You\n \n5. SBY-0503-30615\n Using Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,\n when the Orderable Item of an active order is edited to a different\n item, this will alert the user with the message 'New Orderable Item\n selected. This edit will create a new prescription!', and it will do \n the order checking. During order checking process if it encounters any\n drug interactions with other active prescriptions, it will display the\n following:\n \n want to Edit the SIG? NO//'. On selecting 'Yes' you are prompted for\n '***CRITICAL*** Drug Interaction with RX #9999999'\n 'DRUG: ASPIRIN BUFFERED 325MG TAB' (the drug it had interaction with)\n 'Do you want to Continue? Y// '.\n \n At this prompt if you enter 'No' or up-arrow (^), or you enter 'Yes'\n and for the next prompt 'Do you want to Process medication METHOTREXATE\n 2.5MG TAB: P// ?', (drug that is tied to the Orderable Item you\n selected to), if you enter '0' or '^' to Abort, there is a possibility\n of getting an undefined variable error PSODRUG("OIN"). This patch\n corrects this problem.\n these fields: dosage, verb, dispense unit, noun, route, schedule,\n \n6. MAC-0503-60991\n Using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n option, when the drug of an active order is edited to a drug that is\n tied to a different Orderable Item, the software prompts 'Do You want\n to Edit the SIG? NO//'. On selecting 'No', you are alerted with the\n message 'This change will create a new prescription!'. When you accept\n the new order, since the dosage information is incomplete you will be\n forced to enter the dosage information. At the prompts; Verb, Schedule,\n Limited Duration or Conjunction, if you enter up-arrow (^) with the\n duration or the conjunction. If changes are made to any of these\n intention of quitting the order process, you are prompted to fill the\n rest of the fields. When it prompts you 'Is this correct? YES//', on\n selecting 'Yes', there is a possibility of getting an undefined\n variable error PSOX("ENT"). This patch corrects this error.\n fields, you are prompted 'Are You Sure You Want to Update Rx 999999?\n\n\n \n2. CLE-0203-40018\n When trying to refill a drug that is unmarked for Outpatient Pharmacy use,\n the options Refill [PSO REFILL] and Refill (OP) [PSO SPEED REFILL] act\n differently. The Refill [PSO REFILL] option does not allow this and the\n Refill (OP) [PSO SPEED REFILL] does allow this, and should not. This\n patch will correct the Refill (OP) [PSO SPEED REFILL] option to not allow\n refills of a drug that is unmarked for Outpatient Pharmacy Use.\n \n3. CMC-0602-30921\n National Drug Codes (NDC) starting with non-numeric characters were not\n1. CPH-0203-41084 \n being displayed under the "Comments" column on the CMOP Event Log section\n of the View Prescription [PSO VIEW] option. This patch corrects this issue\n by modifying the display to accommodate these National Drug Codes (NDC).\n \n4. NYH-0903-12478\n When a Health Level Seven (HL7) message is generated, the ZRL segment\n Sequence 13 (Non-Refillable), Sequence 14 (Refill Status) and Sequence\n 20 (Fill Number) are not populated even though there are refills for the\n prescription. This patch will correct this issue by populating these\n Sequences for the ZRL segment.\n When using the options Patient Prescription Processing [PSO LM BACKDOOR\n \n5. ISB-0203-32155\n This patch resolves compliance issues with the Standards and Conventions\n Committee's (SACC) standard regarding the documentation of Database\n Integration Agreements (DBIA). This patch will correct this issue by\n adding this documentation.\n \n6. ISB-0903-31952\n This patch resolves compliance issues with the Standards and Conventions\n Committee's (SACC) standard regarding the format of the first line of a\n ORDERS] and Complete Orders from OERR [PSO LMOE FINISH] to complete a \n routine. In this case, there was an extra space before the date. This\n space has been removed to comply with the standard.\n \n7. PSO*7*152 TRACKER MESSAGE [#37406428] Response #8\n During the testing of this patch in Oklahoma City an undefined error\n occurred. This error has been corrected in this patch.\n pending order, if the number of refills is five and the days supply is 60,\n the current logic calculates the maximum number of refills to two instead\n of five. This patch corrects this issue by modifying the maximum refills\n calculation to account for this scenario.\n \n\n
\nNOIS TOM-0104-41317\n \n1. Look for entries in PRESCRIPTION SUSPENSE file #(52.5) affected by \n the problem above and will reset the "CMP" cross-reference for entries\n within 6 months from the date of install that have not been printed.\n If there are any "CMP" entries existing that do not have a\n corresponding internal entry number in the PRESCRIPTION\n SUSPENSE file (#52.5), the "CMP" entry will be deleted.\n \n2. During Installation of this patch the user will be asked: "Queue the\n Post-Install to run at what Date@Time: ". If the prompt is not answered,\nWhen using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] \n the patch WILL NOT be installed. After the post install routine \n is run to completion at the time the user indicated, a MailMan message \n with the subject "PRESCRIPTION SUSPENSE File (#52.5) reset "CMP" XRef" \n containing the list of prescriptions will be sent to the person installing \n the patch.\n \n3. It is possible that an old prescription in a non-transmitted state might\n be reset to a current division and be set up for transmission to CMOP.\n Please review the mailman report and make modifications if necessary \n before turning the CMOP transmission back on.\noption to edit the division on an original prescription or refill that \n \nNOTE: ** THE POST-INSTALL SHOULD BE QUEUED TO RUN AT OFF-PEAK HOURS NOT\n INTERFERING WITH CMOP TRANSMISSION TIMES AT YOUR SITE. **\nis suspended for CMOP, the possibility exists that the prescription will \nnot be sent to CMOP due to an invalid cross-reference. \nThis patch will fix this issue by maintaining the CMOP compound index \nin the PRESCRIPTION SUSPENSE file (#52.5) correctly.\n \nThis patch has a post install clean-up routine that will :\n\n
\nThe Chief Business Office (CBO) is requesting modifications to several\nSoftware to support the Combat Veteran (CV) initiative is being developed\n \nIn the event that a patient is eligible for more than one copay\nexemption, the CV prompt will be presented to the pharmacist first.\n \nA 'YES' or 'NO' response will be stored in the COMBAT VETERAN field\n(#122) of the PRESCRIPTION file (#52). This is a new field introduced in\nthis patch.\n \n2. The Integration Agreement (IA) 2534 provides CPRS the copay related\nquestions that need to be asked during the outpatient medication order\nand introduced in a phased implementation strategy. The reason for this\nentry process. This IA is modified to include the CV copay classification,\nif applicable.\n \n3. The PENDING OUTPATIENT ORDERS file (#52.41) that stores the pharmacy\norders (new/renew) entered via CPRS is modified to include the provider\nresponse to the CV question. The provider response will be stored in the\nCOMBAT VETERAN field (#110.1) of the PENDING OUTPATIENT ORDERS file\n(#52.41). The COMBAT VETERAN field (#110.1) is a new field introduced in\nthis patch.\n \ntype of deployment is due to the complexity of the functionality and the\n4. During the release of a prescription, medication copay exemptions are\nre-evaluated to see if there is a change in the billing status. This logic\nis modified to include the CV copay classification. If a copay exemption\nquestion applies and is unanswered, a MailMan message is generated. This\nmessage is sent to the pharmacist, ordering provider, and holders of the\nPSO COPAY key, to get answers to the exemption questions and reset the\nprescription copay status if needed, using the Reset Copay Status/Cancel\nCharges [PSOCP RESET COPAY STATUS] option .\n \n5. The Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS] option\nnumber of product line dependencies. Phase I: Combat Veteran Interim\nis modified to include the CV copay classification wherever applicable.\n \n6. During label printing of a prescription, if a prescription is deemed\nbillable then the software does a check on the following copay exemption\nfields of the PRESCRIPTION file (#52):\n117 MILITARY SEXUAL TRAUMA\n118 AGENT ORANGE EXPOSURE\n119 IONIZING RADIATION EXPOSURE\n120 ENVIRONMENTAL CONTAMINANT\n121 HEAD AND/OR NECK CANCER\nSolution (CVIS) was a VistA only solution that involved development in\n122 COMBAT VETERAN\nIf the prescription is identified as copay exempt, the software will\nprint "NO COPAY".\nthe Integrated Billing (IB) and Registration/Enrollment product lines.\nIt provided the logic to identify those veterans who met the criteria for\nthe combat veteran eligibility and provided billing reports\ncross-referenced against this identifier to aid in the copayment billing\nprocess. Phase II of this initiative will involve multiple product lines\nVeterans Health Information Systems and Technology Architecture (VistA)\nand additional VistA only development. The main goals of Phase II will be\nto fully automate the copayment billing processing of combat vets based on\nepisode of care by providing the appropriate questions at check-out as\nsupplied by CPRS.\n \nProduct lines that have a stake in Phase II development include\nEnrollment/Registration (VistA), IB, Outpatient Pharmacy, Consolidated\nMail Outpatient Pharmacy (CMOP), CPRS/TIU, Patient Care Encounter (PCE),\nAmbulatory Care, Event Capture, Scheduling and PTF. The National Patient\nCare Database (NPCD) will also require modifications to capture workload\npackages to support implementation of VHA Directive 2002-049 - "Combat\nreporting. The patches are listed below in the order that they must be\ninstalled:\nOutpatient Pharmacy\n PSO*7*157\n PSX*2*50\nPCE/PTF/Event Capture/Scheduling - PIMS Host file\n PX*1.0*130\n SD*5.3*325\n DG*5.3*565\n EC*2.0*54\nVeterans Are Eligible For Medical Services For 2-Years After Separation\nIntegrated Billing\n IB*2.0*247\nCPRS\n OR*3.0*190\nProduct Features\nThere are three main areas addressed by this enhancement:\na. Identification/Notification of a CV Status veteran seeking medical care\n - The clinical applications shall obtain the CV Status for those\n veterans who qualify as such per the directive.\n - The CV Status identification shall be displayed to the appropriate\nFrom Military Service Notwithstanding Lack Of Evidence For Service\n audience (pharmacist, clinician providing care, intake personnel,\n schedulers, etc.).\n - Provider shall be able to identify whether care provided CV veteran\n was for a condition potentially related to combat service in the same\n manner as identification of exposure related care; care for SC\n conditions, etc.\nb. Assistance in the communication of a treatment being determined as\n Combat Related\n - Provide a means for the billing and pharmacy software package to\n identify these patients and services provided care for a combat\nConnection", which iterates VA's policy to provide medical care and other\n related condition.\nc. Automatically precludes inpatient and outpatient medical care,\n prescription and Long-term care copayments for CV Status veterans whose\n treatment/service has been deemed combat related.\n \nThis is the Outpatient Pharmacy patch PSO*7*157 that provides the\nfunctionality changes to accommodate the new copay classification called\n"Combat Veteran".\n \n1. For the following options, when creating a new order, renewing an\nmedical services to combat veterans despite the absence of proof of\nexisting order, copying an existing order to a new order, or editing an\nexisting order that results in a new order, the copay status of the\nprescription needs to be determined for billing purposes.\n \na. Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\nb. TPB Rx (Prescription) Entry [PSO TPB RX ENTRY]\nc. Barcode Batch Prescription Entry [PSO BATCH BARCODE]\nd. Complete Orders from OERR [PSO LMOE FINISH]\n \nDepending on the patient eligibility, the software currently provides\nservice connection.\nthe following copay exemption questions to the pharmacist during\nprescription finishing process:\n \n"Is this Rx for treatment of Vietnam-Era Herbicide (Agent Orange)\nexposure?"\n \n"Is this Rx for treatment of ionizing radiation exposure?"\n \n"Is this Rx for treatment of environmental contaminant exposure during the\nPersian Gulf War?"\n \n \n"Is this Rx for treatment of Military Sexual Trauma?"\n \n"Is this Rx related to treatment of Head and/or Neck Cancer?"\nand/or Neck Cancer veterans;\n \nTo fulfill the Directive 2002-049, this patch will add the following\nCombat Veteran (CV) copay exemption question to the current copay list:\n \n"Is this Rx potentially for treatment related to Combat?"\n\n
\nThis patch will fix two similar issues regarding missing text\n was previously truncated will now be moved to a new line.\n \n2. When printing prescription labels there is a potential that some \n lines will be skipped from printing on the prescription in the\n warning label section. This issue was happening in rare cases\n when lines in the warning label had been deleted and new lines\n were added. Modifications have been made to print the warning\n labels lines when this scenario is encountered.\non the printed prescription labels.\n \nThe two issues this patch resolves are:\n \n1. When printing prescription labels there is a potential that part \n of the Narrative Text lines will be truncated. Modifications\n have been made to resolve this problem while preserving the \n narrative text format entered by the customer. The text that \n\n
\n1. DAY-1202-41933\n \n2. SPO-0104-50404\n An internal problem in the software was causing an error during the\n Renewal process. This error occurred when a Transitional Pharmacy\n Benefit prescription was renewed and the PATIENT STATUS field (#3)\n of the PHARMACY PATIENT file (#55) had not previously been set.\n Once this patch is installed this problem will be resolved.\n An internal problem in the software was causing the content of the\n comment field, entered when a prescription was discontinued, to be \n replaced by a 0 (zero). This problem was detected when printing the\n Activity Log for the discontinued prescription. The comment field for\n the DISCONTINUED activity was displaying a 0 (zero) instead of the \n original comments entered by the user who discontinued the\n prescription. Once this patch is installed this problem will be\n resolved.\n\n
\nJoint Commission for Accreditation of Healthcare Organizations (JCAHO)\nSystem (CPRS), Outpatient Pharmacy, Pharmacy Data Management, Inpatient\nMedications and National Drug File (NDF).\nrequires that patients' use of OTC medications, Herbal supplements,\nmedications prescribed by the VA but purchased by the patient at an\noutside pharmacy, and medications prescribed by providers outside the VA\nbe documented in patients' medical records. These four categories of\nmedications will hereafter be referred to as Non-VA Meds. In September\n2002, a team with members from different applications was put together to\ncome up with a national solution to address this requirement. The\napplications involved in this project are Computerized Patient Record\n\n
\nThis patch addresses the problem introduced by the Outpatient Pharmacy\nintroduced by patch PSO*7*155.\npatch PSO*7*155.\n \nIn the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] option,\nthe print by 'Clinic' function was not working correctly after installing\nthe patch PSO*7*155. One of the problems was related to queuing the report\nto the printer. The report would show on the screen instead of the\nprinter. It also resolves the problem "device or file not open" reported\nin NOISs LEB-0404-21298 and NCH-0404-41348. This patch fixes all problems\n\n
\n1. This patch fixes an error that can occur in the Change Suspense Date \nPharmacy can return a flag to CPRS that tells CPRS to not ask the Service\nConnected question for that particular Outpatient Pharmacy order.\n \n3. A new input transform for the QTY (#.04) field of the PARTIAL DATE\nsubfile (#52.2) of the PRESCRIPTION file (#52) is being sent out in this\npatch. It changes a Write statement to a VA FileMan call to comply with\ncurrent standards. \n \n4. This patch corrects a problem with discontinuing multiple Rx's at one\ntime. NOIS CON-0698-12208. \n[PSO PNDCHG] option. When using this option, if "YES" is entered at the\n \n5. In the medication procedure call that returns inpatient and outpatient \ndetailed information, new data elements were added. NOIS PUG-0298-51400.\n \n6. Corrected a problem with editing drugs in prescriptions and the cost\nfor the drug not being updated properly. NOIS TUA-0798-32558.\n \n7. This patch corrects a problem of a possible incorrect CLINIC (#5)\nfield entry for a prescription. If a prescription is renewed from CPRS,\nthen Finished in Pharmacy, the Clinic for that prescription is the\n"Do you want to delete Rx's from suspense for this patient" prompt, and\noriginal Clinic for the "Renewed from" prescription, but is should be the\nClinic where the prescription was Renewed. NOIS: CON-0998-10826\n \n8. This patch corrects a problem when a drug is changed in an Rx, but does\nnot create a new order, the cost for that Rx did not update.\nNOIS: TUA-0798-32558 \n \n9. Enhanced the Cost Management Cost compile to use the release date and \ninclude partials. This change allows the management report to be\nconsistent with the Cost and AMIS reports. NOIS: NCH-0698-40147\nthat patient has an unreleased refill that has printed from suspense,\n \n10. Added new option to allow cost of an Rx for a specific drug to be\nupdated after the cost has been updated in the DRUG file (#50). NOIS:\nNCH-0698-42420 and NYN-0998-11680.\n \n11. This patch corrects a problem reported in NOIS CAH-1198-32272. The \nproblem happens when using the speed renew action, the incorrect number of\nrefills for controlled substances was being stored and displayed.\n \n12. Added a newing statement to the supported reference PSOORDER to try\nan error could occur. NOIS STX-0898-71717. \nto protect variables of other packages.\n \n2. This patch exports an entry point that can be called by Computerized\nPatient Record System (CPRS) during Outpatient Order Entry. Based on the\npatient and the Dispense Drug selected (when applicable), Outpatient\n\n
\n If a Pharmacist selects Multiple prescriptions in the Patient\n other pharmacist, once it is removed, the next entry added to the \n ending file will contain the same internal entry number. If this new\n entry is a new order (instead of a discontinued order or something\n else), when the first pharmacist gets to that item from his selection\n list, the information that is displayed is from the "New" order. So the\n pharmacist could unknowingly finish the prescription thinking it was\n for the patient that he is viewing on the profile . The order does get\n filed under the correct patient, just not the patient that the 1st\n pharmacist was processing. This patch corrects this problem by\n verifying that the pending order is for the same patient that the\n Prescription option ([PSO LM BACKDOOR ORDERS]) and one or more of these\n pharmacist is viewing.\n prescriptions are 'Pending', the possibility exists that another\n Pharmacist could have previously run the Complete Orders from OERR\n ([PSO LMOE FINISH]) option and already selected one of these orders to\n finish. Locking on the pending order does not occur until the\n pharmacist pulls up that order to edit it. Once an order is finished,\n it is removed from the PENDING OUTPATIENT ORDERS file (#54.21). If the\n very last entry in the pending file is the one being finished by the\n\n
\nThe VistA Fee Basis Package will be replaced by a new application in a \nfile (#52), and the local VistA FEE BASIS PHARMACY INVOICE file (#162.1)\nfor fee basis patients. Accessing the FEE BASIS PHARMACY INVOICE file\n(#162.1) by Outpatient Pharmacy is provided by Integration Agreement (IA)\n203. With the VistA Fee Basis Package migrating to a new platform, the Fee\nBasis Encapsulation project is replacing IA 203 with IA 4395. IA 4395 will\nprovide Outpatient Pharmacy with the fee basis prescription count and cost\ndata either from the local VistA Fee Basis file or from the Fee \nReplacement system. This will isolate the Outpatient Pharmacy from future\nchanges as the fee replacement system is implemented. This patch will\nmodify the Nightly Management Data Compile Job [PSO MGMT NIGHTLY COMPILE]\nphased approach. The new application will be hosted by the Health \noption, to make a call to the new API, $$RXSUM^FBRXUTL(), documented by IA\n4395 that provides the fee basis prescription count and cost for a given\ndate.\nAs the VistA Fee Basis Package is moving towards a National database, the\nnew API may also return a string value of \n"-1^exception_number^exception_text", indicating an exception has \noccurred. To accommodate this exception, this patch will also generate a\nnew mail message to the holders of the PSORPH security key. Following is\nan example of this mail message:\n \nAdministration Center, which is located at Denver, CO. A future phase of \nSubj: FEE Basis Cost Data - Incomplete Nightly Job [#156131]\n04/29/04@18:41 9 lines\nFrom: OUTPATIENT PHARMACY PACKAGE In 'IN' basket. Page 1 *New*\n-------------------------------------------------------------------\n**************************************************\n*** FEE Basis Cost data was not collected for ***\n*** the period 04/26/04 to 04/29/04. ***\n*** ***\n*** The reason reported was: ***\n*** Valid station number not specified ***\nthe VistA Fee replacement project will have the pharmacy invoices entered \n*** ***\n*** You may have to manually recompile this ***\n*** data at a later date. ***\n**************************************************\n \nThis message will help in the future for site to manually recompile the\nmissing fee basis prescription count and cost for the noted dates from the\nFee Replacement system.\n \nNote:\nand processed using the Fee replacement system.\nThe Cost of Prescriptions [PSO MGMT REPORT RX COSTS] option and the Cost\nof Prescriptions [PSO MGMT MONTHLY RX COSTS] option, provides the daily\nand monthly prescription cost report. While testing this patch it was\nobserved that the average participating pharmacy prescription cost under\nthe column heading "AVG PARTIC PHARM RX", was incorrect and displays a\nzero value even with data present. This patch fixes this problem.\n \nThe Nightly Management Data Compile Job [PSO MGMT NIGHTLY COMPILE] option\nis scheduled to run nightly. This option populates the OUTPATIENT PHARMACY\nMANAGEMENT DATA file (#59.12) with cost related data from the PRESCRIPTION\n\n
\n1. CHA-0204-30749\n2. CAH-1203-31567, DUB-0204-30722, NYH-120311822, WPB-1203-31609\n The functionality exists to modify the DEA, SPECIAL HDLG (#3) field\n of the DRUG (#50) file to contain an "F". This code signifies that\n this drug in not refillable. If the # OF REFILLS (#9) field of the\n PRESCRIPTION (#52) file is modified after the DEA, SPECIAL HDLG (#3)\n field has been changed to an "F", the # OF REFILLS (#9) field for\n the prescription is automatically reset to 0. This is causing the\n prescription display to show the 'Refills Remaining' as a negative\n number. This patch will change how this situation is handled. If a\n prescription has refills and the DEA, SPECIAL HDLG (#3) field has been\n Currently, if the NARCOTICS NUMBERED DIFFERENTLY (#1000) field in the\n changed to include an "F", the # OF REFILLS (#9) field will be changed to\n the actual number of refills given and the following message will be\n displayed:\n "The drug has been changed and no longer allows refills."\n If no refills had been given, the # OF REFILLS (#9) field will be set to\n 0 and the following message will be displayed:\n "No refills allowed on this drug."\n \n3. FGH-1203-31351\n If a prescription was transmitted to CMOP, then put on hold, it\n OUTPATIENT SITE (#59) file is set to Yes, all prescriptions that have\n removes the fill date. It is then released and when the hold is\n removed, it does not prompt for a fill date since it is released,\n therefore the possibility exists that if the Fill Date is blank the\n subsequent fills will be rejected by the CMOP transmission.\n This patch will prompt the user for a fill date with a default of\n the released date if a prescription is unheld after it is released\n and fill date field is blank.\n a drug with a DEA, SPECIAL HDLG (#3) field if file DRUG (#50) that contains\n an "A" (Narcotics) are numbered differently than other prescriptions. This\n patch will change the check of the DEA, SPECIAL HDLG (#3) field in\n the DRUG (#50) file to check for all Schedule II drugs, denoted by\n a "2" in the DEA, SPECIAL HDLG (#3) field, instead of just an "A".\n \n\n
\n 1. LEX-0303-42244 & CTX-0504-70229\n possibility exists that a carriage return could be included in\n the NTE2 segment. This will cause the Optifill machine to reject\n the entire HL7 message. This patch will resolve this problem.\n \n 3. CLE-0404-40219\n When a pharmacist finishes an order using the Patient Prescription\n Processing option (PSO LM BACKDOOR ORDERS) for a patient and does\n not exit back to the menu prompt, the possibility exists that the\n patients order could still be locked. This would prevent other\n pharmacists from accessing this order until the original pharmacist\n While finishing a prescription using the Patient Prescription\n exits back to to the menu prompt. This patch will resolve this\n problem.\n Processing option (PSO LM BACKDOOR ORDERS) for a controlled\n substance the number of refills could be set to eleven instead\n the maximum aloud, which is five. This patch will resolve this\n problem.\n \n 2. HOU-0404-71083\n When transmitting an HL7 message to the Optifill machine, the\n\n
\n When using the option Print from Suspense File (PSO PNDLBL) the\n possibility exists that duplicate labels could be printed if\n this option was used previously and is still running. This patch\n will resolve this issue by delaying the second job until the first\n job finishes.\n\n
\n If a drug has been unmarked for Outpatient Pharmacy use by using the\n option Drug Enter/Edit [PSS DRUG ENTER/EDIT] then a pharmacist tries to\n refill a prescription that uses this drug, they will not be allowed.\n This patch will modify this behavior by allowing a prescription to be\n refilled even after the drug has been unmarked for Outpatient Pharmacy\n use.\n\n
\n There are three patches to support the Outpatient Pharmacy Automation \n refer to the individual patch description of the other patches to get the \n names of the documentation files. \n \n Each patch will share the same starting description with more detail \n for each patch in the corresponding namespace patch number. There is \n only one installation guide. It can be found on the anonymous \n directory. The name of the installation guide is \n PS_OUTPATIENT_AUTOMATION_INTERFACE_IG.doc. \n \n \n Interface project. These patches should be installed separately in the \n The patch enhances the current Health Level Seven (HL7) interface to \n ensure that the interface is compatible with all current Outpatient \n Pharmacy V. 7.0 automation systems used by the Veterans Affairs \n Medical Centers (VAMCs). The current national VISTA HL7 interface is \n written to HL7 standard V. 2.2. Automated dispensing systems, such as \n the Baker APS Pharmacy 2000, are currently using an interface written to \n V. 2.3.1 standard using locally developed software. The automated \n dispensing systems have committed to be HL7 V. 2.4 compliant. \n \n This patch includes the following new features: \n following order: \n 1. Enhance the current Outpatient Pharmacy V. 7.0 HL7 interface to \n the current HL7 V. 2.4 standard. \n 2. Creates a bi-directional interface. The interface transmits \n outpatient pharmacy data to multiple vendor systems utilized by VAMCs \n and receives dispensed prescription data from the vendor systems. \n 3. The dispense completion message received back from the vendor will \n automatically release the prescription in VISTA if the FILE RELEASE \n DATE/TIME field (#105.1) is set to YES in the PRESCRIPTION file (#52). \n 4. The interface sends outpatient pharmacy prescription release \n information to the vendor once a prescription is manually released. \n PSO*7*156 Outpatient Pharmacy \n 5. The BusinessWare interface engine at each medical center is used \n to pass the HL7 data through from VISTA to the dispensing system. \n There is no data manipulation on BusinessWare's part. \n 6. Enhance the activity log entries for the sequence of events for a \n prescription's activity in the PRESCRIPTION file (#52). \n 7. Add a fourth selection to the OUTPATIENT SITE file (#59), EXTERNAL \n INTERFACE field (#5). This selection is titled 'SEND MARKED ORDERS \n AND PRINT LABEL'. \n 8. This patch allows dispensing system printer(s) to be entered and used\n when selected, and the interface is in use, sending an HL7 message\n PSS*1*82 Pharmacy Data Management \n to the dispensing system.\n 9. This patch added new functionality for reprinting Rxs and using the \n external interface. If a reprint of an Rx is requested the user is \n asked if they want to resend the Rx to the external interface.\n PSN*4*84 National Drug File \n \n They contain routines, templates, options, and data dictionary changes to \n implement the Outpatient Pharmacy Automation Interface features. Please \n\n
\n1. PSO*7*156 provided a two-way interface that returns a dispensing\nthe prescription labels that follows.\nNOISs: SAM-0604-21393, BAC-1203-40321, WIM-0604-20277\n \n3. When pulling an original fill early from suspense and printing\nprescription labels using a laser printer the last dispense date is not\nbeing updated correctly. When prescription are pulled from suspense the\nfill date and the last dispense date should always reflect the date the fill\nwas pulled from suspense. NOISs: HON-0904-62008, SAJ-0804-70774\nmessage to VistA from the dispensing machine that indicates\ndispensing of medication has completed. When this dispensing message\nis returned the first entry in the activity log for the prescription is\noverwritten. This patch corrects this problem.\n \n2. When printing a prescription using a laser printer, the patient has a\nlanguage preference other than English, and more than one prescription is\nentered and printed, text from the first prescription label is printing on\n\n
\n 1. FAV-0501-71064, FGH-1199-32693, WIM-0704-21673, WPB-0604-31928\n \n 2. SBY-0504-30082\n During a routine edit of a prescription using the option\n [PSO LM BACKDOOR ORDERS] (Patient Prescription Processing) the\n possibility exists to receive an 'undefined variable' error in\n the program PSOORED2 at line VER+4. This patch will resolve this\n issue.\n and MAD-0504-40315\n When making an appointment using the [SDAM APPT MGT] Appointment\n Management or [SDMULTICLINIC] Multiple Clinic Display/Book options\n the possibility exists that an error could be generated in the\n program SDAMEVT or SDMUTL1. This error is caused by the\n Outpatient Pharmacy programs responsible for returning\n prescription information in the Appointment options. This patch\n will resolve this issue.\n\n
\nWPB-0304-31149\nSolution: For a Scriptalk patient, if the sig is greater than 196 \ncharacters and the scriptalk label is printed, the human readable section \nwill print in English and its Spanish translation as follows:\n \n"SIG IS TOO LONG. REPRINT A NON-VOIDED VISTA LABEL AND PLACE OVER THIS \nSCRIPTALK LABEL"\n \n"INDICACIONES MUY LARGAS. IMPRIMA UNA ETIQUETA DE VISTA VALIDA Y \nAPLIQUELA SOBRE ESTA ETIQUETA DE SCRIPTALK EN LA BOTELLA."\n \nWhen a partial is processed for a Scriptalk patient, the scriptalk \nHIN-0104-41546\nWhen using [PSO SCRIPTALK PATIENT ENROLL ] option, the message displayed \nis offset and incomplete. This patch will display the full message.\n \nBIG-0404-70352\n1. When a patient has more than one eligibility code defined and the \npatient profile is accessed using the [PSO LM BACKDOOR ORDERS] option, it \nonly displays one eligibility.\n \n2. When the patient status is not defined, and the patient is accessed, it\nprinter label generated prints with the full quantity instead of the \nonly displays one eligibility. \n \nThis patch will display multiple eligibilities defined for the patient.\npartial quantity. This issue is resolved with this patch.\n \nCLE-0304-40723\nProblem: For a Scriptalk patient, if the sig is greater than 196 \ncharacters and the scriptalk label is printed, it truncates the sig.\n \n\n
\n1. Prior to the installation of this patch, if a new prescription is\nCMOP criteria. Because the routing gets changed from Window to Mail, the\nprescription will be suspended for CMOP, instead of suspended locally.\n \n2. This patch provides the Controlled Substances package an entry point to\ncall that will delete the last refill of a prescription. When posting\nand releasing a prescription in Controlled Substances, if that\nprescription has been discontinued, it will not be released and the refill\nwill be deleted. This functionality will be available when patches\nPSO*7*21 and PSD*3*11 are installed, though the patches are not dependent\non each other for installation.\nentered at a site running the Consolidated Mail Outpatient Pharmacy (CMOP)\n \n3. This patch fixes an error that could occur when putting a prescription\non Hold through the Patient Prescription Processing [PSO LM BACKDOOR\nORDERS] option. If the prescription has refills, and the user enters an\n'^' at the PHARMACIST NAME prompt, an error could occur. A change has also\nbeen made to the Activity Log comments when putting a prescription on\nHold. Currently, if the prescription has an entry in the RX SUSPENSE file\n(#52.5), the comments always end in "removed from SUSPENSE", regardless of\nwhether or not the fill has been printed from suspense. This patch makes\nthe change to only add those comments if the suspense fill has not yet\npackage, and that prescription is for a CMOP drug and is given a future\nbeen printed. NOIS OKL-1098-71710\n \n4. This patch enhances the functionality of editing prescriptions. An\noption is being added under the Rx (Prescriptions) [PSO RX] menu option\ncalled Edit Prescriptions [PSO RXEDIT]. This option will allow editing of\nprescriptions by entering prescription number(s). Editing will still be\navailable through the Patient Prescription Processing [PSO LM BACKDOOR\nORDERS] option, but this new option provides an alternative editing\ncapability. In addition, if a key field of a prescription is edited (field\nthat generates a Reprint label request), and the field edited is a field\nFill Date and marked as Window for the routing, that prescription will not\nof the last fill that has been released, a prompt will now be given that\nasks if a Reprint label should be printed. If a key field is edited of a\nfill that is not the last fill, and that key field is contained in the\nlast fill, a Reprint label will not be generated.\n \n5. This patch fixes a problem of an incorrect refill date possibly being\nassigned to a refill. After suspending a new prescription to the future,\nif a refill is then done and a refill date of today is entered, the\nfuture fill date from the new prescription can possibly be assigned to\nthe refill date. NOIS ALX-1198-71519\nbe suspended for CMOP. Even if all of the other CMOP criteria are met, it\n \n6. This patch provides a new Order Summary of Pending Outpatient orders.\nThis new summary is by Clinic. To have this functionality, the\nverified patch PSO*7*15 must also be installed. Patch PSO*7*15 is not\nrequired for installation of this patch, but the new Order Summary by\nClinic will not be available until that patch is installed.\n \n7. This patch fixes a problem reported for sites running Tricare. Partial\nprescriptions are being sent for Tricare billing, but they should not.\nThis patches fixes the problem.\nwill be suspended locally because of the Window Routing. Because of\n \n8. A problem has been reported that occurs when a Pharmacist verifies a\nprescription entered by a Technician. If the Pharmacist edits the\nprescription after it is accepted, but before the Label prompt, it can\npossibly be flagged as a Reprint prescription, when it should not be.\nAlso, if it is a CMOP prescription, it may print locally instead of\ngoing to the CMOP because of the Reprint status.\nnumerous requests to change this functionality, this patch will\nautomatically change a Window routing to Mail for new prescriptions\nentered with a Future Fill Date that get suspended, and meet all of the\n\n
\nThis project consists of 12 patches that work together to create a new\n GMPL*2*27\n GMRV*4*15\n LR*5.2*295\n OR*3*157\n PSS*1.0*62\n PSJ*5.0*90\n PSO*7*118\n PX*1.0*119\n RA*5*33\n YS*5.01*77\nClinical Reminders index global. The purpose of this index is to provide\n \nThe purpose of this patch (PSO*7*118) is to lay the groundwork for these\nchanges by creating new cross-references in the PRESCRIPTION file (#52)\nthat will be responsible for updating the new Clinical Reminders index\nglobal. These are the new cross-references added to the PRESCRIPTION \nfile (#52) and the fields used as the trigger-points. The type of these\ncross-references is 'New', not 'Traditional'.\n \n X-ref File/Sub-file Trigger-point field(s)\n ----------------------------------------------------------\nrapid access to clinical data. All of the standard Clinical Reminders\n ACRO PRESCRIPTION (#52) DAYS SUPPLY (#8) \n RELEASED DATE/TIME (#31) \n \n ACRR REFILL (#52.1) DAYS SUPPLY (#1.1)\n RELEASED DATE/TIME (#17)\n \n ACRP PARTIAL (#52.2) DAYS SUPPLY (#.041) \n RELEASED DATE/TIME (#8)\nfinding types are included in the index.\n \nThe 12 patches that comprise this project are:\n \n PXRM*1.5*12\n DG*5.3*478\n\n
\n***********************************NOTE***********************************\n(HDR) to receive clinical data about patients the patient must have an\nIntegration Control Number (ICN) and Treating Facility (TF) List. VistA\nunder certain circumstances allows backdoor entry of clinical activity to\nbe recorded for a patient without "requiring" a patient to have an ICN.\nThe immediate needs of the HDR have identified several issues within the\nexisting PIM to uniquely identify patients through the ICN enumeration\nprocess. PIM services are tied into VistA at several points. In the\ncurrent VistA structure, up front identity management is done only within\nRegistration via several different menu options, as that has been the\ntraditional entry point of patients into the system. In addition, there\nThis patch does NOT conflict with CoreFLS and can be installed at CoreFLS\nare "hooks" within Appointment Management, which assign a local ICN after\nthe patient has received care. Subsequently, the national ICN is obtained\nthrough a nightly job or via manual resolution of the local ICN. The\nrequester states that the current method does not support good business\npractices for updating patient identity traits at appropriate entry points\nand does not provide the full functionality of the benefit of the ICN in\nlinking all patient data together.\n \nThis is the Outpatient Pharmacy patch PSO*7*185 that places the ICN check\n(hooks) within the Outpatient Pharmacy V. 7.0 options, to dynamically\nsites.\nassign a local ICN for a patient if one was not found.\n \nOutpatient Pharmacy will not make any changes to options where the\npatient look up is done via the FileMan DIC call on the PATIENT file\n(#2). As part of the PIM project, the Master Patient Index V. 1.0 package\nwill send out a separate patch that will have the ICN "hooks" in place.\n \nIn Outpatient Pharmacy, the following options do not use the standard\npatient lookup (FileMan DIC call on the PATIENT file (#2)), as the\nprimary input for selecting orders.\n**************************************************************************\n \nRelease Medication [PSO RELEASE]\nReturn Medication to Stock [PSO RETURNED STOCK]\nReset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]\nComplete Orders from OERR [PSO LMOE FINISH]\nBarcode Batch Prescription Entry [PSO BATCH BARCODE]\nDiscontinue Prescription(s) [PSO C]\nEdit Prescriptions [PSO RXEDIT]\nReprint an Outpatient Rx Label [PSO RXRPT]\nView Prescriptions [PSO VIEW]\n \nPull Early from Suspense [PSO PNDRX]\n \nFor these options, a check is put in place to see if the INTEGRATION\nCONTROL NUMBER (ICN) field (#991.01) of the PATIENT file (#2) is populated\nby calling the API #2701, $$GETICN^MPIF001(DFN). If it is not populated\nthen a call is made to the API #3300, $$MPIQQ^MPIFAPI(DFN) that will\npopulate the INTEGRATION CONTROL NUMBER (ICN) field (#991.01) of the\nPATIENT file (#2).\n \nNote: This patch also carries a fix for NOIS PAL-0804-60841.\nPATCH OVERVIEW\nPatch PSO*7*175 - FEE REPLACEMENT ENCAPSULATION PROJECT, calls the API\n#4395, $$RXSUM^FBRXUTL(DATE,STATION_NUMBER), to collect the fee basis\nprescription count and cost for a given date and the approving Veterans\nAffairs Medical Center (VAMC) station number. The station number that is\npassed to the API is the STATION NUMBER field (#99) of the INSTITUTION\nfile (#4), which constitutes a 3 digit station number plus any modifiers.\nThe API #4395 requires only the first 3 digits of the station number\notherwise it will return an error message, "Valid station number not\nspecified". This patch fixes this problem.\nGail Graham, Director of Information Assurance requested that a process\nof Patient Identity Management (PIM) be created that uniquely identifies a\npatient prior to providing care. In order for the Health Data Repository\n\n
\nThis patch supports the VistA Data Extraction Framework (VDEF)\neffort, allowing changes to the PRESCRIPTION file (#52) to be transmitted\nto the Health Data Repository (HDR). The activation of the transmission \nwill be handled with the sites on an individual basis. Until that \nactivation occurs, the changes included in this patch will not affect \nany Pharmacy functionality.\n\n
\nThis patch is phase 2 of the patches that support the VistA Data\nPROTOCOL:\n PSO VDEF RDE O11 OP PHARM PRES HR\n PSO VDEF RDE O11 OP PHARM PRES VS\n PSO VDEF RDS O13 OP PHARM PPAR HR\n PSO VDEF RDS O13 OP PHARM PPAR VS\n PSO VDEF RDS O13 OP PHARM PREF HR\n PSO VDEF RDS O13 OP PHARM PREF VS\n \nHL7 APPLICATION PARAMETER:\n HDRPPAR\nExtraction Framework (VDEF) effort, allowing changes to the PRESCRIPTION\n HDRPREF\n HDRPRES\n PSO VDEF IE SIDE \n \nThe routine PSOVDFK is used as the KIDS Post-Install routine to install \nspecific components for the Outpatient Pharmacy package in several VDEF\nnamespace globals that VDEF uses to construct a message. It uses the VDEF\nAPI POSTKID^VDEFVU to do this. The specific components that are sent to\nPost-install routine are:\n \nfile (#52) to be transmitted to the Health Data Repository (HDR). The\n1. HL7 Message Type\n2. HL7 Event Type\n3. VistA Domain Subtype\n4. HL7 Protocol Event Driver name\n5. Application's Custodial Package name\n6. Name of the routine that does the message extraction\n7. VDEF Event Description\n8. VDEF Event Subtype description\n \nThe POSTKID^VDEFVU routine uses the components to create event-specific\nactivation of the transmission will be handled with the sites on an\nparameters in VDEF files.\n \nThe patch cannot be installed until VDEF 1.00 is installed. \n \n \n** IMPORTANT **\n \nSites should not install this software prior to your assigned HDR\ninstallation date; doing so may cause complications with your BCMA\napplication with versions prior to PSB*3*4. You will be contacted\nindividual basis. Until that activation occurs, the changes included in\napproximately two weeks prior to your HDR installation date and provided\nwith instructions on when and in what order to install these patches and\nthe VDEF software. Additionally, sites should not configure or attempt to\nutilize the VDEF software associated with these patches prior to your\nassigned HDR installation date, at which time Technical Support Office\npersonnel will work with you to activate that application and start your\ndata transmissions to the HDR database. (If you do not know your HDR\ninstallation date, you can find that information by going to \n<http://vaww.teamshare.domain.ext/hdr_implementation/> and selecting \n"Implementation Schedule" from the Quick Launch panel on the left side of \nthis patch will not affect any Outpatient Pharmacy functionality.\nthe page.) \n \nThe following build components are being exported with this patch:\n \n\n
\n \nThe Label/Profile monitor field has 250 as the minimum value, but the \nsoftware that uses that field sets the minimum value to 1000.\nEach time the printer is used, an entry is made in the Label/Profile \nmonitor and if the monitor holds more entries than specified by this \nparameter, the oldest entry is deleted.\nThe documentation and field specifications for Label/Profile monitor \nallows you to enter a minimum value of 250. The field specification and \nfile manager documentation will be changed to allow a minimum value of \n1000.\nWhile going through the option to finish an outpatient pharmacy order\n[PSO LMOE FINISH], if the patient status field is left blank the first \ntime it is asked for, the program will ask for the patient status again.\nIf the user doesn't enter the patient status the second time, an error is\ngenerated.\nThis patch will resolve this problem.\n \n2)HUN-0304-21898\n\n
\n1. PSO*7*156 provided a two-way interface that returns dispensing\ninformation to VistA from the dispensing machine that updates the \nPRESCRIPTION file (#52) when dispensing of medication is completed.\nSince being released to the field, it has been determined that additional\ndata validation checks were needed on the data being returned.\nThis patch includes those additional data validation checks.\n \n3. When viewing a prescription using the View Prescriptions [PSO VIEW]\noption, the initiator of activity does not display, however, if viewing from\nthe profile, it does display. NOIS: MAC-1104-61559\ninformation to VistA from the dispensing machine that updates the \nPRESCRIPTION file (#52) when dispensing of medication is completed.\nWhen developing this new two-way interface the Label/Profile Monitor\nReprint [PSO B] option was not enhanced to send label reprints to the\nexternal interface. BRX-0803-10283\n \n \n2. PSO*7*156 provided a two-way interface that returns dispensing\n\n
\n \n \n 2. SHE-0404-51324\n The potential exists to modify the number of refills for a\n controlled substance from a maximum of 5 to 11. This can happen\n in the Patient Processing Option [PSO LM BACKDOOR ORDERS] while\n finishing a renewed order.\n \n 3. DAY-0604-41287\n An issue was identified in the Imaging software that allowed the\n software to automatically select a patient based on name even if\n 1. MOU-1203-30359\n multiple patients existed with the same name. A fix is being\n included in Pharmacy to kill an internal variable to not allow\n this behavior. This change does not affect the pharmacy application\n in any way.\n \n 4. CLL-0604-40968\n When using the Return Medication to Stock [PSO RETURNED STOCK]\n option it is possible to get the following message:\n \n Original Fill CANNOT be Returned!\n When using the Return Medication to Stock [PSO RETURNED STOCK]\n This fill entered before installation of version 6. There are no\n refills.\n \n This message is generated when the pharmacist try's to return a\n medication to stock for a prescription that has a fill date that\n is less than the date Version 6.0 of the Outpatient Pharmacy\n application was installed. This message will be removed.\n option for a controlled substance, the pharmacist is allowed to\n up-arrow ("^") out of the comments field even though it is a\n required field. When this happens, some Controlled Substance\n files are partially updated and will cause the medication to be\n returned twice. This patch will resolve this issue by not allowing\n the pharmacist to up-arrow out of the comments field.\n\n\n During order entry in backdoor Outpatient Pharmacy, Order checks are\n exists for the same drugs.\n not being performed on Non-VA medications if other medications exist.\n The possibility also exists that when a 'critical interaction'\n exists and is displayed, this critical interaction could be displayed\n for subsequent orders even though a 'critical interaction' does not\n exist on the order currently being entered.\n \n When entering an order via backdoor Outpatient Pharmacy or CPRS, a\n critical interaction could be skipped if a significant interaction\n\n
\nSPELLING ERROR AND QUANTITY CHANGING\n\n
\n \nand will not auto-suspend to the next scheduled refill date.\nRoutine: PSOREF0\n \n3. Fixed Null Subscript error reported in NOIS WAS-0498-21833. The error\noccurs when Outpatient Pharmacy receives a Discontinue message from CPRS on\nan entry in the PENDING OUTPATIENT ORDERS File (#52.41) with missing\ndata. Changed messaging to recognize the UR order control code.\nRoutine PSOORUTL\n \n4. In the View Prescriptions option, the help text given to the user at the\n1. This patch fixes a possible undefined error that could occur when\nVIEW PRESCRIPTION prompt if the user enters a "?" is misleading. The\nhelp text says that Patient Name can be entered, but it can't. This patch\nwill remove the "M" from the DIC(0) variable. Routine PSORXVW\na new Outpatient Pharmacy division is added and the Daily and/or Monthly\nManagement Cost Reports are run.\nRoutines: PSOMGMN1, PSOMGMN2, PSOMGMN3, PSOMGRP1, PSOMGRP2, PSOMGRP3\n \n2. If an OP Rx is filled on 6/5 and the patient quickly returns the refill\nform for processing, on 6/13, before the scheduled refill date 6/26. The\nbar code option [PSO BATCH BARCODED] will not accept the refill request\n\n
\n This patch will correct two DEA (Drug Enforcement Agency) Special\n Handling issues, one while completing the prescription via the PSO LM\n BACKDOOR ORDERS option, and one while refilling a prescription via the\n Barcode Batch Prescription Entry option on the PSO BARCODE MENU. This\n patch will also correct a null subscript error while verifying a\n prescription via the PSO LM BACKDOOR ORDERS option.\n\n
\nThis supported #1878 has been updated to include new data elements at the\n FINISHING PERSON\n MEDICATION INSTRUCTION sub-file fields:\n DOSAGE INSTRUCTION, DISPENSE UNITS PER DOSE, UNITS, NOUN, \n DURATION, CONJUNCTION, ROUTE, SCHEDULE, VERB\nrequest of Pharmacy Benefit Management (PBM). See DBIA #1878 for\ncomplete description.\n \nThe follow data elements from the Prescription file (#52) were added.\n NDC (original, refill, partial)\n LOGIN DATE (original, refill, partial)\n TPB RX\n EXPANDED PATIENT INSTRUCTIONS \n\n
\nThe routine PSOORDER, which supported DBIA #1878 has been updated to \n LOGIN DATE (original, refill, partial)\n TPB RX\n EXPANDED PATIENT INSTRUCTIONS \n FINISHING PERSON\n MEDICATION INSTRUCTION sub-file fields:\n DOSAGE INSTRUCTION, DISPENSE UNITS PER DOSE, UNITS, NOUN, \n DURATION, CONJUNCTION, ROUTE, SCHEDULE, VERB\ninclude new data elements at the request of Pharmacy Benefit Management \n(PBM). See DBIA #1878 for complete details.\n \n \n \n \nThe following data elements from the Prescription file (#52) were added.\n NDC (original, refill, partial)\n\n
\nThis patch is part of the Outpatient Pharmacy V. 7.0 Laser Labels\n 2. Contact your vendor to make adjustments based on the new data stream.\nlastname,firstname.\n 4. When the routing is "Window", the word "Window" will be bolded.\n \nPharmacy fill card section changes:\n==================================\n 1. Seconds will be removed from the label date/time.\n 2. A new API will return the text for the DRUG WARNING list. The DRUG \nWARNING entries will be separated by commas. If an entry in the list does \nnot have an "N" (for "New"), it is from the RX CONSULT file (#54).\nOtherwise it is from the WARNING LABEL-ENGLISH (#50.625) or the \n \nWARNING LABEL-SPANISH (#50.626) file.\n 3. A new line containing the patient location and status is being added\nbeneath the DRUG WARNING list, so the list is being moved up slightly on\nthe label.\n 4. Patient name and last portion of the social security number are \nbolded.\n 5. If the bottle cap is "non-safety", it will be bolded.\n 6. Currently long SIG's that do not fit on one pharmacy fill card label\nprint only 4 lines of SIG on the first label and up to 4 lines on each\ncontinuation label. This patch increases the number of lines of the SIG \nAlthough implementing OPAI is not mandated at this time, it is expected \nthat print on each pharmacy fill card label to reduce the total number of\nlabels needed.\n 7. The words "3rd Party Rx" and the NDC number are added when that \ninformation is available. (Added for HIPAA/NCPDP).\n \nPatient fill section changes:\n============================\n 1. The barcode will print every time even if there are no refills.\n 2. The site telephone number will print when the "PHONE IN OR MAIL THIS \nREFILL REQUEST" prints.\nto be in the future, so option 1 is the preferred solution. By \n 3. The text "n refills left until MMM DD,YYYY is changed to "May refill \nnX by MMM DD,YYYY".\n \nPrescription Document PMI section changes:\n=========================================\n 1. The PMI will print in the patient's language preference.\n 2. The white spaces between sections of the PMI document will be \nreduced to result in a few more lines fitting on the page.\n 3. If there are more than 5 warning labels, the additional warnings \nwill print at the top of the PMI section.\nimplementing OPAI, future changes to the label format will not affect the \n \nTrailing document changes:\n=========================\n 1. The patient's phone number followed by an underline will print on \nthe address change form.\n 2. In the Allergies/ADR section, the name and last six digits of the \nsocial security number will be made larger and will be bolded.\n 3. In the Allergies/ADR section, if the HOSPITAL LOCATION file (#44), \nTYPE field (#2) type equals "W" for any prescription printed for this \npatient in the current print job, then the word "INPATIENT" will print \ndispensing equipment interface.\non the line following the patient name.\n 4. In the Allergies/ADR section, if some sections do not have data, the \nheader will not print. If no information exists, "No Assessment Made" \nwill print after the Verified Allergies heading.\n 5. In the refill narrative or copay narrative sections, if there are \nmore than seven lines from the original text, only the first seven lines \nwill print. (They could appear as more than seven lines if there is some \nwrapping of the text).\n 6. If the Multi-Rx refill section is blank, the SITE NUMBER field \n(#.06) from the OUTPATIENT SITE file (#59) will print bottom right\n*************************************************************************\njustified.\n \nA utility routine is included in this patch to change some of the control\ncodes in the TERMINAL TYPE file (#3.2). \nOnce the patch is installed, running the routine PSOLLU4 in programmer\nmode will make slight adjustments to PATIENT FILL INITIALIZATION, \nPHARMACY FILL DOCUMENT WARNING, MAILING LABEL INITIALIZATION, and RETURN \nMAIL INITIALIZATION settings.\nNote: you must have your FileMan access set to '@' to run the routine. \n \nTo fully implement all portions of the new functionality, the \nfollowing are needed:\nPhase II project for printing prescription labels.\n 1. Patch PSS*1*87 from Pharmacy Data Management V. 1.0 (PDM),to provide \nan API for retrieving warning labels from the new data source.\n 2. Patches PSN*4*86 and PSN*4*88 from the National Drug File V. 4.0\n(NDF) to create and populate a new gender field in the WARNING\nLABEL-ENGLISH file (#50.625) and the WARNING LABEL-SPANISH file (#50.626).\n 3. Patch PSX*2*54 from the Consolidated Mail Outpatient Pharmacy V. 2.0\n(CMOP) to modify the way warnings are sent to CMOP.\n \n \n This patch includes:\n \n 1. Referencing a new commercial data source for printing prescription \nwarning labels. \n 2. Printing warning labels and Patient Information Sheets (PMI) by the\npatient's PMI language preference setting.\n 3. A new MAILING COMMENTS field (#.081) is added to the OUTPATIENT SITE\nfile (#59.7) to be used for a site to enter anything they would like to \nshow on the Mail Address label. (i.e. whether mailing is "Forwarding \nservice requested" or "Address service requested"). The PSO SITE INPUT \nTEMPLATE for the OUTPATIENT SITE file (#59.7) is changed to allow the \ninput of data into the new mailing comments.\n***** NOTE TO SITES USING AUTOMATED FILLING EQUIPMENT *****\n 4. A new Manual Print of Multi-Rx Forms [PSO LM MULTI-RX PRINT] option\nis added under the Rx (Prescriptions) [PSO RX] option as well as under \nthe OTH hidden action while in the patient's profile to reprint the \nMulti-Rx Refill Request form on laser label stock without having to\nreprint the entire prescription's labels. The functionality is also\nchanged to stop printing the Multi-Rx refill form on reprints.\n 5. Various changes to the content/format of the labels - detailed below\nunder each label section.\n 6. Correction to only print one ScripTalk label when SIG is continued.\n(NOIS CLE-0304-40723. (The other part of this NOIS is addressed in patch\nThis patch changes the format and content of the laser labels print \nPSO*7*182, so this NOIS is not included in the associated patch list \nbelow)).\n 7. A new Signature Log Reprint [PSO SIGLOG REPRINT] option is added\nunder the Rx (Prescriptions) [PSO RX] option. (Added for HIPAA/NCPDP).\n 8. A change was made to not keep exact duplicates of the control code \nsettings (e.g. when running the set-up routine as a test site and again \nwhen the patch is installed in production). NOIS PUG-1103-52110\n 9. The other NOIS's listed below were for items already included in the\nLaser Labels Phase II specifications.\n \nstream. If you are using automated dispensing equipment that relies on \nBottle label section changes:\n============================\n 1. Currently long SIG's that do not fit on one bottle label print only 4\nlines of SIG on the first bottle label and up to 4 lines on each \ncontinuation label. This patch increases the number of lines of the SIG \nthat print on each bottle label to reduce the total number of labels\nneeded. This also will allow the overlapping of the multiple labels on the\nbottle to eliminate the need for cutting the labels to make them fit.\n 2. The text "Mfr_________" will print for all prescriptions on the same \nline as the "Discard after" information.\nthe data stream sent to the laser labels port, you have 2 options:\n 3. The text "May refill nX by MMM DD,YYYY" or "NO REFILLS LEFT" or "NO \nREFILL" was added between the "Discard after..." line and the Qty: line.\n 4. On the trailing documents, a signature log will print in the bottle \nlabel section for the patient to sign for the medications received. \n(Added for HIPAA/NCPDP).\n \nWarning label section changes:\n=============================\n 1. A new API will be called to determine which warnings to print.\n 2. Warnings will print in English or Spanish depending on the patient's \n 1. Implement the Outpatient Automation Interface (OPAI) (available with\nPMI preference.\n 3. If there are fewer than five warning labels, the warning labels will \nbe bottom-justified.\n 4. If the DEA, SPECIAL HDLG field (#3) in the DRUG file (#50) begins\nwith numbers 1,2,3,4 or 5. The NO TRANSFER warning label from the RX\nCONSULT file (#54) entry number 20 will print in the appropriate \nlanguage.\n 5. The new data source contains some lengthy warnings, especially the \nSpanish translation. For the smallest font, this patch allows a 4th line\nof text to print, if needed.\n released patch PSO*7*156) or \n 6. The top warning label was sometimes printing on or over the \nperforated line. For some fonts, this patch reduces the white space \nbetween the lines of the first warning to make it fit.\n \nMail address section changes:\n============================\n 1. The current date will print in the upper right corner.\n 2. If there are any mailing comments defined, they will print after the \nMAIL field (#.03) of the PHARMACY PATIENT file (#55).\n 3. Patient name will print first name first instead of \n\n
\nDisplay Patient Record Flag consistently when finishing outpatient \npharmacy orders via the Complete Orders from OERR [PSO LMOE FINISH]\noption.\n\n
\nIf a user runs option Return Medication to Stock in the Outpatient \nPharmacy menu and then goes into the Controlled Substances option\nBalance Adjustments, the dispensing site defaults to the one chosen when\ndoing the Return Medication to Stock option.\n\n
\nThis patch corrects the duplicate medication checking of meds that were\nordered initially as both a NON-VA and an Outpatient med. This occurs in\nPatient Prescription Processing [PSO LM BACKDOOR ORDERS] option when you\nverify a Non-Verified med\n\n
\nDEATH ENTRY PROBLEM\n\n
\n1. Partial deletion causing error. This patch fixes this problem.\n2. Methadone drug being the only drug released when the Nightly\nManagement Data Compile Job is run causing error.\nThis patch fixes this problem.\n\n
\nCorrect error when trying to add a NON-VA Med order to the PHARMACY \nPATIENT file #55 in the "NVA" multiple file #55.05.\n\n
\nPatch to Patch for PSO*7*15.\n\n
\nThis patch adds the VUID (VHA Unique Identifiers) from the VA PRODUCT file\n(#50.68) to the Outpatient Pharmacy VDEF (Vista Data Extraction Framework)\nmessage that sends prescription information to the HDR (Health Data\nRepository). It also replaces Set of Code fields in the message with\nVUIDs. It also adds a check to screen out prescription information for\ntest patients from being sent to the HDR.\n\n
\nCorrect a word wrapping problem with Provider Comments and Patient \nInstructions when there is a very large word, greater than 30 characters.\nUsually the word is a list seperated by commas with no spaces.\n\n
\n1. My HealtheVet team in preparation for the My HealtyVet V. 1.0\n \n Calling AP1 component will return the following status:\n \n -5 DFN does not match RX\n -4 Unable to resolve patient\n -3 Unable to resolve prescription\n -2 Status is pending\n -1 Result is back but not picked up\n 0 Other error\n 1 Filed in PRESCRIPTION REFILL REQUEST file (#52.43)\n package (Internet Prescription Refill project), requested an\n \n Calling AP2 component will return the following status:\n \n -6 RX not in file #52.43\n -5 DFN does not match RX\n -4 Unable to resolve patient\n -3 Unable to resolve prescription\n -2 Status is pending\n -1 Result is back but not picked up\n 1 Filled\n additional Outpatient Pharmacy V. 7.0 Application Program Interface\n 2 Not Filled\n n^x n - Date the refill request was processed.\n x - The result of the processing. This will be either FILLED or\n NOT FILLED.\n \n Calling AP5 component will return the following status:\n \n -6 RX not in file #52.43\n -4 Unable to resolve patient\n -3 Unable to resolve prescription\n (API) #4687, to provide details of all (active, verified, on hold,\n -2 Status is pending\n 0 The update was not successful. This will occur if any of the\n information provided (DFN, RX #) are invalid.\n 1 The update was successful.\n \n 3. A new PATIENT field (#9) was added to the PRESCRIPTION REFILL REQUEST\n file (#52.43) that is a pointer to the PAITENT file (#2). A new\n "AC" cross reference was added, to index the file by PATIENT field\n (#9) and PRESCRIPTION IEN field (#8). The existing "AA", and "AB"\n cross references were removed.\n suspended, discontinued, pending and expired), prescriptions for a\n \n Note: This patch carries a Pre-install routine that will delete the\n Data Dictionary (DD) of the PRESCRIPTION REFILL REQUEST file (#52.43)\n before the install of the new DD. This file is not in use currently,\n however, it will not destroy any data in the test systems.\n For more details, please refer to the installation guide or the technical\n manual of the My HealthyVet V. 1.0 package.\n patient within a given date.\n \n 2. Also the existing API #3768 has been modified to provide the following\n status for Internet refill requests (used internally):\n\n
\nCorrects the following problems: 1) OPAI does not have an interface to \nthe Drug Accountability package. 2) OPAI when a code comes back to \nindicate it did not dispense the drug, VistA Outpatient Pharmacy \nindicates on the acitivity log that it did not, but actually does release \nthe drug, 3) On a refill from OPAI, the Copay is not billed correclty.\n\n
\nProduce a Tally message & report of all Outpatient Pharmacy refills that \nwere released via the OPAI 2.4 automated interface since the install of \npatch PSO*7*156.\n\n
\nPSO*7.0*143 = Outpatient Pharmacy Clinical Indicator Data Capture (CIDC) KIDS\n\n
\nCorrect partially built NTE6 segment sent via OPAI, correct run-on words \nin the PMI segment in HL7 messages sent via OPAI, and correct PSO \nManagement Reports from skipping Released RX's with date and no times.\n\n
\nPrompt for a Tally or Back-Bill run and based on this response either \nproduce a Tally or Back-Billing message & report of all Outpatient\nPharmacy refills that were released via the OPAI 2.4 automated interface\nsince the install of patch PSO*7*156.\n\n
\nPFP PSO*7.0*221 UPDATE TO PSO*7.0*174\n\n
\nThis patch is a follow up for Outpatient Pharmacy Clinical Indicator Data\nand environmental indicator (EI) questions was not set correctly for non\ncharge to the patient's insurance carrier.\n \nNote: The SC question is now asked for Veterans who are SC>49% in order to\ndetermine if the Rx can be billed to a third party insurance. These \nVeterans will NOT be charged a VA copay.\n \nSupply and investigational drugs are not charged a VA copay but could be\nreimbursable by third party insurance.\n \nEnter message action (in IN basket): Ignore// \nservice connected (NSC) patients, as a result the following issues were\n \nc. In CPRS, SC/EI related questions were not asked for supply items \nand investigational drugs (remedy ticket 11421). CPRS and backdoor \nOutpatient Pharmacy users will be required to complete SC/EI questions for\nsupplies and investigational drugs. Supply items and investigational drugs\ncould be reimbursable by third party insurance. Also, a VA copay will not\nbe charged for these.\n \n2. During use of Complete Orders from OERR option [PSO LMOE FINISH], the\ndefault answers for SC/EI's for CPRS SC>50% renewed orders were\nreported:\noccasionally displaying the previous orders answers during the finish\nprocess. A modification was made to display the SC/EI information entered\nduring the CPRS renewal process. This anomaly was encountered during\nunit testing, and there is no associated remedy ticket.\n \n3. For renewal orders in Complete Orders from OERR option [PSO LMOE \nFINISH] and Patient Prescription Processing option [PSO LM BACKDOOR \nORDERS], a message was erroneously displayed after the SC/EI prompts for\nSC>50% prescriptions. The following is an example of the message\ndisplayed when eligibility is changed or the user enters an up arrows (^)\n \nat an outpatient classification prompt. Note that the bracketed\ninformation can be SERVICE CONNECTED or NON SERVICE CONNECTED depending\nupon the user's response to the question. Or if the user up arrows (^)\nout of the prompt, the default answer determines the value.\n \n Was treatment for a Service Connected condition? YES// ^\n This Renewal has been designated as [SERVICE CONNECTED]\n Please use the 'Reset Copay Status/Cancel Charges' option to\n make corrections.\n \na. In CPRS, the SC related questions were incorrectly prompted for NSC\nThe "Please use the 'Reset Copay Status/Cancel Charges' option to make\ncorrections" sentence will no longer be displayed for supply items,\ninvestigational drugs, and SC>50% patients. The first sentence will\nremain in order to continue to inform the user of the answer stored for\nthe prompt. Note that similar messages are displayed for environmental\nindicator prompts and this change applies to them. The associated remedy\ntickets are 11393 and 113931.\n \n4. For CPRS prescription orders finished using the Complete Orders from\nOERR option [PSO LMOE FINISH] or the Patient Prescription Processing\npatients, and it should not have done so. It should prompt SC/EI question\noption [PSO LM BACKDOOR ORDERS], a copay related message was displayed for\nSC>50% patients, supply items and investigational drugs. The following is\nan example, and please note that bracketed information can be either COPAY\nor NO COPAY depending on the providers response to the clinical indicator.\n \n Do you want to enter a Progress Note? No// NO\n \n SC Percent: 40%\n Disabilities: NONE STATED\n \nonly if applicable.(remedy ticket 114219).\n This Rx has been flagged by the provider as: [NO COPAY]\n \n Was treatment for Service Connected condition? YES\n \nThe "This Rx has been flagged by the provider as: [COPAY/NO COPAY]"\nmessage will no longer be displayed for SC>50% patients, supply items, \nand investigational drugs. There is no associated remedy ticket.\n \n5. When an edit that creates a new order is performed in Outpatient \nPharmacy, a message is displayed to notate that the orderable item was\n \nchanged. This message is displayed in the Complete Orders from OERR\n[PSO LMOE FINISH] option and the Patient Prescription Processing option\n[PSO LM BACKDOOR ORDERS]. The following is an example:\n \n CARBAMAZEPINE 100MG TAB\n PROVIDER,NAME PROVIDER,NAME\n # of Refills: 3\n \n The Pharmacy Orderable Item has changed for this order. Please\n review any existing medication copay exemption defaults carefully\nb. Holders of the PSO COPAY key, the ordering provider, and the finishing\n for appropriateness.\n \n SC Percent: 40%\n Disabilities: NONE STATED\n \n Was treatment for Service Connected condition? YES// \n \nThe above message has been modified to the following:\n \n The Pharmacy Orderable Item has changed for this order. Please\npharmacist were receiving increased volumes of mailman messages in \n review any existing SC or Environmental Indicator defaults carefully\n for appropriateness.\n \nTechnical Description:\n----------------------\nThe following correlates to each sequence in the Functional Description \nabove and the routines modified are shown in parentheses by each function:\n \n1. The SCNEW^PSOCP API was returning PSOTG("SC")="" variable for NSC\npatients which caused CPRS to erroneously prompt for them. Also due to\nCapture (CIDC) patch PSO*7*143.\nOutpatient Pharmacy. Mailman messages were incorrectly sent for NSC\nthis, Mailman messages for "RX COPAY STATUS REVIEW NEEDED" information was\nsent in error for NSC prescriptions at release of the prescription. These\nissues were corrected, and the PSOCPE routine was modified to show the\npatient's eligibilities and disabilities as well as impart more accurate\ninformation.\n \n 2. Modified renewal routines to always pull SC/EI information from the\ndata passed on the renewed order from CPRS (PSORENW1, PSORN52, PSORN52D).\nThis change affects renewals from CPRS and backdoor Outpatient Pharmacy\norders.\npatients upon refill, new, and renewed orders (remedy ticket 114219).\n \n3. For SC>50% prescriptions, supply items and investigational drugs,\neliminated the display of "Please use the 'Reset Copay Status/Cancel\nCharges' option to make corrections." sentence (PSOCPB, PSOMLLD2,\nPSOMLLDT), but it will continue to be displayed for SC<50% prescriptions.\n \n4. For SC>50% prescriptions, supply items and investigational drugs,\neliminated the display of "This Rx has been flagged by the provider as:\n[COPAY/NO COPAY]" (PSOCPB, PSONEWF, PSORN52). This message will continue\nto be displayed for SC<50% patients.\nThese messages have been eliminated. Mailman messages will still be\n \n5. For SC 0-100%, supply items and investigational drugs, modified the \nwording of the message displayed when a prescription edit that creates a \nnew order is performed (PSOCPB, PSONEWF, PSONEWG).\ngenerated for the following scenarios:\n \n SC percentage\n - age changed E/I question\n Type to >0% added? Mailman Message sent?\n --------- -------------- ------------- -------------------------\n NSC N N N \n \n \n NSC N Y Y only if question was\n not answered before\n the prescription is\n released\n \n NSC Y N/A Y if question was not\n answered before the\n prescription is\n released\nFunctional Description:\n \n SC=>0%<50% N/A Y Y however, NO mailman\n message will be sent\n if any SC/EI = YES\n on the original\n prescription \n \n For SC>50% prescriptions and if patient has a new SC/EI added, the\n appropriate questions will be asked upon RENEW or COPY of the\n original prescription. At release, a MailMan message will not be sent\n----------------------\n if the patient, patient status, or drug is exempt from copay.\n \nBecause the information requested by these Mailman messages are used to \ndetermine the final VA copay and/or insurance billable status, the text \nand format has changed. The subject line was changed from "RX COPAY \nSTATUS REVIEW NEEDED" to "PRESCRIPTION QUESTIONS REVIEW NEEDED" and the\nbody of the message has additional information. Also, the eligibility and\ndisability information is now included after the patient name. The\nfollowing is an example:\n \nThis Outpatient Pharmacy patch PSO*7*219 corrects the following issues:\nSubj: PRESCRIPTION QUESTIONS REVIEW NEEDED (800) [#164897] 10/07/05@13:39\n37 lines\nFrom: OUTPATIENT PHARMACY PACKAGE In 'IN' basket. Page 1 *New*\n-------------------------------------------------------------------------\n \nPATIENT,TEST (XXXX) \nEligibility: SC LESS THAN 50% SC%: 10\n REIMBURSABLE INSURANCE\n \nDisabilities: ARTHRITIS-10%(SC), FOREARM CONDITION-5%(NSC), \n \n FOREARM CONDITION-4%(NSC), BENIGN EYE GROWTH-0%(NSC), \n LOSS OF FIELD OF VISION-20%(SC), \n \nRx# #######B (1) NO COPAY\nAMITRIPTYLINE 100MG\n \nDue to a change in criteria, additional information listed below is needed\nto determine the final VA copay and/or insurance billable status for this \nRx so that appropriate action can be taken by pharmacy personnel.\n \n1. The Application Program Interface (API) that is provided to \nIs this Rx for a Service Connected Condition?\n \n \nEnter RETURN to continue or '^' to exit: \n \n \nSubj: PRESCRIPTION QUESTIONS REVIEW NEEDED (800) [#164897] Page 2\n--------------------------------------------------------------------------\n \nThis message has been sent to the provider of record, the pharmacist who\nComputerized Patient Record System (CPRS) with the service connection (SC)\nfinished the prescription order, and all holders of the PSO COPAY key.\n \nProviders:\nPlease respond with your answer to the question(s) as a reply to this\nmessage. The prescription will be updated by the appropriate staff.\n \nStaff assigned to update the Prescription responses:\nPlease use the RESET COPAY STATUS/CANCEL CHARGES option to enter the \nresponses to the questions above, which may result in a Rx copay status\nchange and/or the need to remove VA copay charges or may result in a\n\n\n 1. Changed code at STRX+2^PSOBINGO to prevent long response time when "??" is\nthis happens is that the protocol PSO Cancel has three (3) synonyms attached to\nit, DC, Discontinue, and Cancel. The PSO Cancel synonym will be removed from\nthe protocol. The patch PSO*7*12 will delete the protocol PSO CANCEL and then\nre-install it. NOIS: WNY-0398-11863 \n \n3. When "DN" (down one line) is entered, or down arrow on the keyboard is \npressed to navigate down a line in ListManager on the OP Medications profile\nscreen, a message states that "DN is not a valid selection". NOIS:\nWNY-0398-11862 \n \nentered at the "Enter Rx #:" prompt. This option lists a patient's \n4. Restored functionality that allows sites to use separate monitors to display\nthe same display group data multiple times. In V.6.0, sites could start each\nmonitor by selecting the same display group by using the Start Bingo Board\nDisplay [PSO BINGO START] option. Functionality in V.7.0 was inadvertently \nremoved. When a site attempts to start multiple monitors the message that \n"Board has already been started!" is displayed. \n \nSites that have bingo board setup to auto-start using a dedicated device will\nnot be allowed to start the same display group multiple times. This would\nresult in a <Device Not Available> error message. Routine: PSOBGMGR. NOIS:\nprescriptions after selecting the patient. The problem is that the screen \nWNY-0398-12812. \nlooped through the entire PRESCRIPTION file (#52). Routine: PSOBINGO NOIS:\nWNY-0498-10082 \n \n2. When the "C" is entered to copy a prescription, the computer response is \n"DC", and then the "Are you sure you want to discontinue? No//" prompt is \ndisplayed. "C" should call the "COPY" action, not "Discontinue". The reason\n\n
\nPREVENT THE Monthly Rx Cost Compilation OPTION FROM RUNNING MORE THAN \nONCE CON-CURRENTLY USING VARIBALE LOCKING TECHNIQUES.\n\n
\nThis patch will modify the order process to require a physician to have a \nDEA# or VA# to order controlled substances.\nIt will also modify Script Talk label so if the instructions are more than\nthree lines, the message that the signature is too long will print \ninstead.\n\n
\n \nspreadsheet provided for this project dated 2/11/05.\n \nThe PSO SITE INPUT TEMPLATE is changed to include the new field. Through\nthe PSO SITE PARAMETERS [Site Parameter Enter/Edit] option, the user can\nadd, edit, or delete the NCPDP assigned licensed pharmacy number.\n \nWhen the patch is installed, a post-install job will be queued to\npopulate the NCPDP number and a MailMan message will be sent indicating\nthe NCPDP numbers for each active division and site. If there is already\na value in the NCPDP number field, this patch will not overwrite it.\nThis patch will create and populate a new NCPDP NUMBER field (#1008) in\n \nExample MailMan message:\nSubj: NCPDP NUMBER POPULATION [#164410] 08/30/05@21:55 10 lines\nFrom: PATCH PSO*7*216 In 'IN' basket. Page 1\n--------------------------------------------------------------------------\n-----\nPatch PSO*7*216 - POPULATE NCPDP NUMBER FIELD POST-INSTALL\nThis message is being sent to the installer of the patch and holders of\nthe PSORPH key.\n \nthe OUTPATIENT SITE file (#59). This field is needed for the Remote Data\nPlease validate that the NCPDP number is correct for each active DIVISION \nand\nSITE NUMBER. If missing or incorrect, enter the correct number using the\nSite Parameter Enter/Edit option.\n \nDIVISION: EXT SITE NUMBER: 500 NCPDP NUMBER: 0000001\nDIVISION: TROY SITE NUMBER: 514 NCPDP NUMBER: NO NUMBER FOUND\n-------------------------------\nThis\npatch will create and populate the NCPDP NUMBER field (#1008) in the\nInteroperability Department of Defense (DoD) Clinical/Health Data \nOUTPATIENT SITE file (#59). This field is needed for the Remote Data \nInteroperability Department of Defense (DoD) CHDR application.\n \nNCPDP stands for the National Council for Prescription Drug Programs\nformerly referred to as the National Association of Boards of Pharmacy \nNumber (NABP).\n \nThe PSO SITE INPUT TEMPLATE is changed to include the new field. Through\nthe PSO SITE PARAMETERS [Site Parameter Enter/Edit] option, the user can\nadd, edit, or delete the NCPDP assigned licensed pharmacy number.\nRepository (CHDR) application.\n \nWhen the patch is installed, a post-install job will be queued to \npopulate the NCPDP number and a MailMan message will be sent indicating \nthe NCPDP numbers for each active division and site. If there is already \na value in the NCPDP number field, this patch will not overwrite it. \n \nExample MailMan message:\nSubj: NCPDP NUMBER POPULATION [#164410] 08/30/05@21:55 10 lines\nFrom: PATCH PSO*7*216 In 'IN' basket. Page 1\n--------------------------------------------------------------------------\n \n-----\nPatch PSO*7*216 - POPULATE NCPDP NUMBER FIELD POST-INSTALL\nThis message is being sent to the installer of the patch and holders of\nthe PSORPH key.\n \nPlease validate that the NCPDP number is correct for each active DIVISION \nand\nSITE NUMBER. If missing or incorrect, enter the correct number using the\nSite Parameter Enter/Edit option.\n \nNCPDP stands for the National Council for Prescription Drug Programs\nDIVISION: EXT SITE NUMBER: 500 NCPDP NUMBER: 0000001\nDIVISION: TROY SITE NUMBER: 514 NCPDP NUMBER: NO NUMBER FOUND\nformerly referred to as the National Association of Boards of Pharmacy\nNumber (NABP). The numbers being used to populate the field come from a\n\n
\nThis patch adds the NCPDP (National Council for Prescription Drug \nTransaction Service) application.\nPrograms) number from the OUTPATIENT SITE file (#59) to the Outpatient\nPharmacy VDEF (Vista Data Extraction Framework) message that sends\nprescription information to the HDR (Health Data Repository). VistA must\ncollect and maintain this information and make this number readily \navailable for application interfaces to store and forward to meet \nrequirements for the CHDR (Clinical Data Repository / Health Data\nRepository) project to provide this number to the DoD (Department of\nDefense). This is a required field in the DoD PDTS (Pharmacy Data\n\n
\nThis patch contains Application Program Interfaces (APIs) that will be \nplace, the calling applications will not be required to make any changes, \nbecause these APIs will be flexible enough to retrieve the requested data \nfrom the new data source, when the time comes.\n \nThese are the files that are affected. If any application is making \ndirect global reads or writes to any of these files, they must be \nreplaced by using the APIs exported with this patch.\n \nFile Name: File Number:\nPRESCRIPTION 52\nused by calling applications that currently do direct global reads or \nPENDING OUTPATIENT ORDERS 52.41\nRX SUSPENSE 52.5\nCLOZAPINE PRESCRIPTION OVERRIDES 52.52\nTPB ELIGIBILITY 52.91\nRX PATIENT STATUS 53\nOUTPATIENT SITE 59\nwrites to the Outpatient Pharmacy files. Since the PRESCRIPTION file \n(#52), PENDING OUTPATIENT ORDERS file (#52.41), RX SUSPENSE file (#52.5), \nCLOZAPINE PRESCRIPTION OVERRIDES file (#52.52), TPB ELIGIBILITY file \n(#52.91), RX PATIENT STATUS file (#53), and OUTPATIENT SITE file (#59) \nare being replaced as part of the Pharmacy Re-engineering project, any \ndirect M-based global reads or writes to these files must be replaced by \ncalling the APIs provided in this patch. When the new data source is in \n\n
\nIssue a warning message and do not allow a refill to be deleted when the \nrefill was sent to an external dispense machine is is still pending\nrelease from that machine.\n\n
\nThis patch adds the capability of doing order checking between local VA \nto occur. When turned on, the remote order checking includes checks for\nduplicate drugs, duplicate drug classes, drug interactions, and drug\nallergies.\n \nIn addition to the new functionality, there are several help desk tickets\nrelated to erroneous drug interactions with non-VA meds. The problem\nand fix have been identified as a variable being carried over from prior \ndrug checks that should have been killed in between. Because the routine\nthat needs to be fixed is already being changed as part of the RDI\nproject, the change to kill the variable at the end of the interaction \nfacilities and remote VA or Department of Defense (DoD) facilities where \nchecking will be included in this RDI patch.\nveterans have received prescriptions. This Remote Data Interoperability \n(RDI) functionality includes receiving data from the Health Data\nRepository (HDR) in order to perform the order checking against remote\ndata.\n \nAfter the release of this patch, a Computerized Patient Record System\n(CPRS) patch will turn on a flag which enables the remote order checking\n\n
\nThis is the second follow up patch for Outpatient Pharmacy Clinical\n \nreleased, total un-released, and total cancelled copays.\n \n2. A summary Mailman message will be sent to Management for their \nreview. It can be cut and pasted into a .TXT file.\n \n3. A detailed report by Veteran and fill number can be produced on \ndemand by entering D RPT^PSOCIDC3 at the programmers prompt. \n \n4. To check the status of the COPAY CANCEL background job while it is\nrunning, then type from the direct programmers prompt the command \n1. For only edited prescriptions ordered prior to patch PSO*7*143 being \nD STATUS^PSOCIDC1.\n \n5. If you need to stop the COPAY CANCEL background job for any reason,\nthen from the direct programmers prompt, type the command D STOP^PSOCIDC1.\ninstalled, the routine that passes information from Outpatient Pharmacy to\nCPRS was passing an extra value and was not passing the Combat Veteran\nindicator. An edit to days supply, quantity, etc. on a prescription \nresults in a background transmission of data to CRPS. This type of data\nwas passed and updated in CRPS correctly. Because CPRS does not \ncurrently update SC/EI's for edited prescriptions, there were no adverse\naffects. However, Outpatient Pharmacy sends all data for consistency, and\nthis was corrected. There are no associated remedy tickets for this\nIndicator Data Capture (CIDC) patch PSO*7*143. The first follow-up patch\nchange.\n \n2. A dollar sign ($) was being displayed for exempt from copay\nprescriptions, and it was being displayed up until the prescription was\nreleased. Also, 'COPAY' was being printed on the label for this type \nof prescription.\n \n3. Copays were erroneously being charged for non-service connected (NSC)\nprescriptions fills that had an environmental indicator flagged as\n"Yes". And, copays were charged for some service connected (SC) <50%\nwas PSO*7*219, and the follow-up patches were split into two patches in\nprescriptions, and this was due to a "RX COPAY STATUS REVIEW NEEDED"\nMailman message being sent instead of prompting the user for the SC/EI\ninformation. Patch PSO*7*219 corrected this issue, but PSO*7*226 cancels\nthe erroneously billed copay(s) as well as restores the copay related\nfields in PRESCRIPTION file (#52).\n \nWhen installing this patch, the 'copay correction' portion of this patch\nis optional. Each site can determine if they would be better suited to\nrun this automated process or correct them manually. If you answer N (No)\nto running the copay correction process and change your mind later, then\norder to quickly get the issues resolved by patch PSO*7*219 into the field\nhave your IRM run ^PSOCIDC1 from the programmers prompt. Please keep in \nmind that by not running the copay correction process that those\nprescriptions where the IBQ node was not stored correctly will continue to\ngenerate a copay until the fill is copied or renewed.\n \n \nTechnical Description:\n======================\nThe following correlates to each sequence in the Functional Description:\n \nimmediately.\n1. In background processing, the PSOHLSN2 routine passes information from\nOutpatient Pharmacy to CPRS when orders are created, edited, copied or\nrenewed from backdoor order entry. Even though CPRS does not \ncurrently update SC/EI information for edited prescriptions, Outpatient\nPharmacy passes them for consistency. The code that handles pre-CIDC\nedited prescriptions passed an extra value and did not pass the Combat\nVeteran indicator. Because CPRS does not update SC/EI's for edited\nprescriptions, there were no adverse affects. A change was made to pass\nthe Combat Veteran indicator and not pass the extra value.\n \n \n2. Because a value denoting copay was allowed to remain in the COPAY \nTRANSACTION TYPE field (#105) for exempt from copay prescriptions, the\n$ sign was incorrectly being displayed and "COPAY was being printed on \nthe prescription label. Modifications were made to eliminate the display\nof the $ sign for exempt from copay fills which in turn eliminates the\nprinting of 'COPAY' on the label. Also, modifications were made to\neliminate this value for NSC and SC<50% prescriptions for all affected\nfills finished between the installation date of patch PSO*7*143 until\npresent. This patch re-examines the PRESCRIPTION file (#52) for any NSC\nand SC<50% prescription that has an ICD node and does not have an IBQ\nFunctional Description:\nnode. Using the SC/EI answers stored on the ICD node, the IBQ node is\ndefined and the COPAY TRANSACTION TYPE field (#105) is defined\nappropriately.\n \n3. For those prescriptions that were erroneously billed a copay from \nthe installation of PSO*7*143 until present, this patch evaluates any\nprescription that was billed, that has an ICD node, but does not have an\nIBQ node. Using the SC/EI answers stored on the ICD node, the IBQ node is\ndefined. Then, if a yes answer is defined for any SC or EI, IB is\nnotified to cancel copay for the fill.\n=======================\n \nThis patch prompts the user during installation when to run the copay\ncorrection process. The job name for this process is 'CANCEL COPAY'. It\nprovides summary Mailman messages, and a detailed Results Report by\nVeteran that can be run from Programmer mode. Also, a Query Status of Job\nfunction as well as a Stop Job Command function is provided. See the\nreports and samples section below for details and images of these\nfeatures.\n \n \nThis patch PSO*7*226 corrects the following:\nReports Section:\n================\n \n* See the sample section below for images of these features.\n \n1. The CANCEL COPAY process will produce a summary mail message of its \nfindings and display instructions on how to print a detailed report by \nVeteran. This MailMan message will be sent to all users that hold the \n'PSO COPAY' security key and the installer of the patch. This message \ncontains results by year and 30, 60, and 90 day fills for total \n\n
\nThe Transitional Pharmacy Benefit (TPB) project that was providing\nStep II-The installation of this patch will automatically inactivate all\n5. This patch will set the AUTOSTART field (#4.5) of the HL LOGICAL LINK\n file (#870) of the PSOTPBAAC Logical Link to "Disabled", to prevent\n restarting of the PSOTPBAAC logical link by TaskMan after a system\n reboot.\n \n6. The TPB data extraction job is queued to run daily and transmit\n data to the AAC every Sunday. This patch will remove the TPB HL7 Data\n Extract/Transmission [PSO TPB HL7 EXTRACT] option from the Task\n Manager.\n \n the TPB functionality.\nNote:\n - The post install routine (PSO227PO) included in this patch\n addresses all items in step II except #3.\n - Most of the TPB routines that are transported in this patch are\n modified to "QUIT" if they are ever called by any other routine.\n \n***********************************************************************\n*** Step I - Manual Step ***\n***********************************************************************\nThe data transmission of TPB eligible patient from the TPB ELIGIBILITY\nfile (#52.91) is performed by the PSOTPBACC HL7 logical link.\nBy now most of the sites would have shut down this link. To check\nwhether this link is enabled or shutdown, do the following:\nfunctionality to furnish medications prescribed by Non-VA Physicians\n \n a) Use the HL7 Main Menu [HL MAIN MENU] option and select the\n Systems Link Monitor [HL MESSAGE MONITOR] option, you should see the\n following screen:\n \n SYSTEM LINK MONITOR for BIRMINGHAM, AL. (Test System)\n MESSAGES MESSAGES MESSAGES MESSAGES DEVICE\n NODE RECEIVED PROCESSED TO SEND SENT TYPE STATE\n \n LL2VISN 51 51 85 51 NC Open\nneeds to be shut down as the period for its eligibility expired on\n NPTF 0 0 163 0 N Halting\n PSBCOTS1 2397 Shutdown\n PSD HLLP 38 N Halting\n PSO DISP 1380 1380 10130 1380 NC Openfail\n PSO LLP1 238 N Halting\n PSOTPBAA 28 Enabled\n PSU SEND 13\n TEST 21 21 21 21 SS Idle\n \n Incoming filers running => Zero TaskMan running\nOctober 22, 2004. Inactivation of the TPB functionality will be done in 2\n Outgoing filers running => Zero ***LINK MANAGER NOT RUNNING!!!***\n Monitor OVERDUE\n Select a Command:\n \n b) If the PSOTPBAAC logical link is enabled then you need to shut down\n the link by doing the following:\n - Use the HL7 Main Menu Option [HL MAIN]\n - Select the Filer and Link Management Options\n [HL MENU FILER LINK MGT]\n - Select the 'Start/Stop Links' option [HL START]\nsteps, a manual step and a automatic step.\n - At the 'Select HL LOGICAL LINK NODE: ' prompt, type PSOTPBAAC and\n press enter. The system will prompt 'Okay to shut down this job?',\n answer 'YES' and press enter.\n The system will display the following message:\n 'The job for the PSOTPBAAC Lower Level Protocol will be shut down.'\n - To ensure the link is shut down use the Systems Link Monitor [HL\n MESSAGE MONITOR] option and make sure the status is 'Shutdown'\n (step a. above).\n*************************************************************************\n*** Step II - Automated Step ***\n \n*************************************************************************\n1. This patch disables the following menu options by placing them to\n be out of order:\n - TPB HL7 Data Extract/Transmission [PSO TPB HL7 EXTRACT]\n - TPB Institution Letter Enter/Edit [PSO TPB INSTITUTION LETTERS]\n - Report TPB Patients Letters Printed/NOT Printed\n [PSO TPB LETTERS PRINTED REPORT]\n - Transitional Pharmacy Benefit Patient Enter/Edit\n [PSO TPB PATIENT ENTER/EDIT]\n - TPB Patient Report [PSO TPB PATIENT REPORT]\nStep I-To make sure that the Health Level Seven (HL7) data transmission\n - Report of Patients with TPB and Non-TPB Rx's\n [PSO TPB PATIENT RX REPORT]\n - Print TPB Patient Letter(s) [PSO TPB PRINT LETTERS]\n - TPB Rx (Prescription) Entry [PSO TPB RX ENTRY]\n \n2. Inactivation of all active TPB patients\n This patch will scan all the entries in the TPB ELIGIBILITY file\n (#52.91) and will stuff the INACTIVATION OF BENEFIT DATE field (#2)\n of the active patients with today's date and the INACTIVATION REASON\n CODE field (#3) with the code "10-PROGRAM ENDED".\n of TPB eligible patients to the Austin Automation Center (AAC) is\n \n3. When a prescription is discontinued, routine PSOTPCAN is called to\n check if that's the last active TPB prescription for an Active TPB\n patient, and if so, the patient TPB patient is inactivated from TPB\n ELIGIBILITY file (#52.91). Based on the fact that there will be no\n active TPB patient upon installing of this patch, routine PSOTPCAN is\n modified to quit without checking for last active TPB prescription.\n \n4. Prior to this patch, Outpatient Pharmacy software used to be notified\n by the Scheduling software every time a patient has an appointment at a\n shutdown.\n VA clinic. If the patient is eligible for the TPB benefit, the\n appointment was at a clinic defined as primary care for the TPB program\n (determined through a set of clinic stop codes) AND the patient does\n not have any "active" TPB prescription(s) on file, this patient will\n have the TPB eligibility automatically inactivated (introduced by\n PSO*7*160). As all active TPB patient's will be inactivated (item #2\n above), there is no need for this functionality to continue. This patch\n will stop this functionality by removing the PSO TPB SD SUB protocol\n entry from the SDAM APPOINTMENT EVENTS Scheduling protocol.\n \n\n
\nThis is a follow-up patch to PHARMACY REENGINEERING ENCAPSULATION\nDBIA 4822 (PSO525AP) is updated to include omitted fields, Printed (#2) and \nCMOP INDICATOR (#3) from the RX SUSPENSE file (#52.5). \n \nDBIA 4827 (PSO59) is updated to include omitted fields, SITE DEA NUMBER (#1)\nand SITE (NATIONAL NAME) (#2) from the OUTPATIENT SITE file (#59).\nCYCLE 2 APIS FOR OUTPATIENT PHARMACY patch (PSO*7*213).\n \nThe following changes are made in this path to the following application \nprogram interfaces (APIs): \n \nDBIA 4820 (PSO52API) is updated with newing of variable to prevent possible \nundefinded errors. \n \n\n
\nPSO*7.0*1 (1.26.98)\nMedication profiles. The problem is that prescriptions that had been marked\nas deleted were printing on the short and long profiles. Routine: PSOP\n \nFixed problem of incorrect message given to user on the Listman status\nbar saying "Label will Reprint due to edit!", when no data was\nactually changed during the editing of the Rx, and no label will be\nprinted. Routines: PSORXED, PSORXED1.\n \nA NOIS was entered on the Tuscaloosa VAMC local NOIS system describing the\nwording in a prompt as misleading. The prompt appeared to allow users to \n \nselect multiple entries. However, this select prompt is meant to allow a \nsingle selection and not multiple. The wording will be changed from 'Select \nRefill' to 'Select a Refill'. Routine: PSOORED2.\n \nWhen prescriptions are returned as not dispensed by CMOP Host, and edited\nby Pharmacy, they are not automatically re-suspended back to CMOP for \ntransmission. Routines: PSOCMOP, PSOCMOPC, PSORXED, PSORXED1\nThis patch installs new functionality that allows the action profile to be\nprinted in an 80 column format. When there's an attached DUE questionnaire\nit too prints in an 80 column format.\nRoutines: PSOSD, PSOSD0, PSOSD1, PSOSD2, PSOSD3, PSOSDP, and PSODACT,\nPSOBMST, PSODEDT.\n \nThis patch corrects a problem in the compiling of the data for the\n\n
\n1. This patch makes a change to the Barcode Batch Prescription Entry\nfor one prescription at the same time, trying to queue the first one and\nsuspend the second one to a later date. If this is done, the label that\nprints for the first refill will indicate that it is for the suspended\nrefill, instead of the first refill. This patch corrects the problem.\n \n3. This patch fixes an undefined error that can occur when processing\ntelephone refill requests for sites that use the Mumps Audiofax software.\nThe problem occurs because a required Outpatient Pharmacy site variable can\npossibly be killed in the Action Profiles. Then if the Mumps Audiofax\ntelephone refill requests are processed, an error could occur.\n[PSO BATCH BARCODE] option. Prior to this patch, if Renewals were\n \n4. A problem has been reported concerning the PSO EXPIRE PRESCRIPTIONS\njob. This is the daily job that sets prescriptions to an expired status\nthe day after the expiration date. The job is initialized using the Expire\nPrescriptions [PSO EXPIRE INITIALIZE] option. A situation could occur\nwhere the last refill gets deleted if a label has printed and the fill has\nnot yet been released. The refill should only get deleted if no label has\nprinted for that prescription refill. This patch fixes the problem.\n \n5. A problem has been reported by sites that involves lines overwriting\nprocessed through this option, and if the first three prompts (Fill Date,\none another on a terminal. This was caused by the Outpatient Pharmacy\nversion 7.0 package making a call to List Manager when the call should not\nhave been made. This patch corrects the problem.\n \n6. This patch fixes an undefined error that can occur on the Bingo Board\ndisplay, as a result of an invalid cross-reference.\nMail/Window, and Queue/Suspend) were answered Today for Fill Date, Mail,\nand Queue, any Consolidated Mail Outpatient Pharmacy (CMOP) prescriptions\nwould print locally. This patch makes the change to suspend these\nprescriptions for CMOP.\n \n2. This patch fixes a problem that can occur when processing two refills\n\n
\nNO ASSESSMENT MADE FOR ALLERGY PRINTING.\n\n
\nINACCURATE OR NO DATA POPULATING THE CANCEL DATE FIELD\n\n
\nThis patch adds the proper escape sequences to the Outpatient Pharmacy\nmessages. This patch fixes that problem.\n \nA request has also been made add two new trigger events, those being when\nthe status of a prescription changes from Active to Suspended, and from\nSuspended to Active. This patch add those trigger events.\n \nThe name of the Institution has also been added to the message.\nVDEF (Vista Data Extraction Framework) message that sends prescription\ninformation to the HDR (Health Data Repository). This will help avoid \nerrors that can occur when special delimiting characters are found in \nVista fields.\n \nThis patch also makes modifications to the trigger events that send \nprescription information to the HDR, using the VDEF. A problem was\nreported where the Clinical ID information was not being sent in some\n\n
\nCORRECT THE OPTION PSO INTERNET REFILL, THE "Q" OPTION FROM SENDING\nMULTIPLE RX #'S FROM DIFFERENT PATIENTS TO THE LABEL PRINT ROUTINES. ALSO\nCHANGE THE DEFAULT "Q" OPTION TO "S" FOR SUSPEND.\n\n
\nA site reported a problem with the Outpatient prescription status of \nSUSPENDED. In some cases, it was being interpreted as being \nnon-refillable. A patient safety incident was entered regarding this \nproblem. The interim solution is to modify the Outpatient Pharmacy V. 7.0 \n(OP) Applications Program Interface (API) that returns the prescription\nstatus. Instead of returning SUSPENDED, the API will return ACTIVE/SUSP. \nThere will be no change to the display in the OP application.\nRemedy Ticket: HD67681\n\n
\nThe National Council for Prescription Drug Programs (NCPDP) standard was\n \n the payer's response and move on with the filling process; override\n the reject by resubmitting the claim or postpone the processing of the\n prescription by taking no action when the reject is received. For\n prescriptions that have been electronically submitted to the third\n party payer, an indicator is displayed on the Patient Prescription\n Processing screen. This indicator will take the form of "e" next to\n the prescription number (e.g.,"2090303$e"). \n \n A new section called REFILL TOO SOON/DUR REJECTS (Third Party) has\n been created in the Medication Profile screen to single out\n APPLICATION/VERSION PATCH\n prescription that had an electronic claim rejected by third party\n payers for REFILL TOO SOON or DUR reasons. Prescriptions under this\n section have certain restrictions. Basically, they cannot be renewed,\n refilled, reprinted, copied or released until the REJECT is resolved.\n When an individual prescription is selected, the user will have a new\n hidden option called REJ - View Reject, which will allow them to\n resolve the REJECT and remove it from the REFILL TOO SOON/DUR REJECTS\n (Third Party) section.\n \n The prescription release option was modified to perform NDC (National\n -----------------------------------------------------------------\n Drug Code) validation for electronically billable prescriptions. When\n the user selects a new NDC a new claim is submitted to the payer\n before the prescription is released.\n \n In the OP Medications screen, a new DAW CODE field (#81) of the \n PRESCRIPTION file (#52) was created for electronically billable\n prescriptions and can be edited by selecting '21' at the 'Select\n Action' prompt. For non-electronically billable prescriptions this\n field is not displayed at all.\n \n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*148\n When the electronically billable prescription is released, this option\n will allow the user to edit the NDC code for the prescription. In the\n OP Medications screen the NDC field is listed under the Drug field\n and can be edited by selecting '2' to edit the drug at the 'Select\n Action' prompt. For sites that do not allow Drug editing, the option\n '2' will allow editing of the NDC only.\n \n2. Return Medication to Stock [PSO RETURNED STOCK] option \n \n The Return Medication to Stock function was modified to notify the\n INTEGRATED BILLING (IB) V. 2.0 IB*2*276\n third party payer that a previously billed prescription was not\n actually filled. If the prescription was previously billed to a third\n party payer and a payable response was received, the claim will be\n reversed, and the pharmacy user will see messaging stating that the\n third party claim was submitted for reversal. If a claim for the\n prescription was previously rejected by the third party payer, the\n user will see a message indicating that no reversal was required. If\n the prescription was not previously billed to a third party payer, no\n message regarding electronic billing will be displayed.\n \n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*90\n3. Delete a Prescription [PSO RXDL] option \n \n The message for Delete a Prescription was modified to perform in the \n same manner as the Return Medication to Stock function described\n above.\n \n4. Pull Early from Suspense [PSO PNDRX] option \n \n The Pull Early from Suspense function was modified to submit a third \n party claim for the prescription. A message will display to notify the\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*48\n user of the status of the claim as it is going through the submission \n process. \n \n5. Print from Suspense File [PSO PNDLBL] option \n \n This option was modified to submit third party claims in the same\n manner as stated above except the Print from Suspense File function\n will be performed in the background. No user interaction will occur.\n \n6. ePharmacy Menu [PSO EPHARMACY MENU] menu\n ACCOUNTS RECEIVABLE (AR) V. 4.5 PRCA*4.5*230\n \n This new menu was created for electronic billing related options. It\n is being placed under the Rx (Prescriptions) [PSO RX] menu. Two new\n options are being added under this new menu:\n \n 6.1 Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] option\n \n This option is used to process third party payer rejects that have\n clinical significance. For now, only DUR (Drug Utilization Review)\n and REFILL TOO SOON rejects are being considered as having\n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*1\n clinical significance.\n \n 6.2 Third Party Payer Rejects - View/Process [PSO REJECTS \n VIEW/PROCESS] option\n \n This option performs the same functionality as the option above.\n However, the user has more filtering capabilities through this\n option. In addition, closed/resolved rejects can only be viewed by\n using this option.\n \n \n7. Release Medication [PSO RELEASE] option \n \n The prescription release process was modified to perform NDC (National\n Drug Code) validation for electronically billable prescriptions. When\n the user selects a new NDC, a new claim is submitted to the payer\n before the prescription is released. Besides this option, the \n prescription can be released from the Medication Profile screen and\n from the Outpatient Rx's [PSD OUTPATIENT] option in the Controlled\n Substances application.\n \nadopted under the Healthcare Insurance Portability and Accountability Act\nVeterans Health Information Systems and Technology Architecture (VistA)\n8. View Prescriptions [PSO VIEW] option\n \n This option was changed to include two new sections: ECME Log and ECME\n REJECT Log. Information about third party payer submission and rejects\n will be displayed under these sections.\n \n9. Edit Prescriptions [PSO RXEDIT] option\n \n The new DAW CODE field (#81) of the PRESCRIPTION file (#52) was\n created for electronically billable prescriptions and can be edited\nsoftware applications and infrastructure were enhanced, in order to allow the\n through this option. For non-electronically billable prescriptions,\n the field is not displayed at all.\n \n Once an electronically billable prescription is released, this option\n will allow the user to edit the NDC code. The NDC code is displayed on\n the screen just below the Drug field, and can be edited by selecting\n field '2' to edit the Drug. For sites that do not allow Drug editing,\n the field '2' can be used to edit the NDC code only.\n \n10. The NDC field (#4) under the CMOP EVENT multiple (#52.01) of the\nelectronic transmission of outpatient pharmacy prescription claims (WINDOW\n PRESCRIPTION file (#52) has been renamed to NDC RECEIVED. This field\n holds the NDC that was received from the CMOP facility with the\n dispensing message. The renaming was necessary due to the addition of \n the NDC SENT field (#12) under the same multiple that is being created\n by this project (see below item 11).\n \n11. A new NDC SENT field (#12) is being created under the CMOP EVENT \n multiple (#52.01) of the PRESCRIPTION file (#52), to store the NDC\n that was transmission to CMOP. This field is used for electronic \n billing purposes to analyze the difference between the NDC sent to\nand MAIL fills) to third party payers via the network connections available\n CMOP and the actual dispensed NDC by the CMOP facility.\n \n12. A new DAW CODE field (#81) is being created on the PRESCRIPTION\n file (#52) and also under the REFILL multiple (#52.1) of the\n PRESCRIPTION file (#52). This field contains the NCPDP DAW used in the\n electronic claims submission to third party payers (insurance\n companies).\n \n13. A new RE-TRANSMIT FLAG field (#82) is being created on the \n PRESCRIPTION file (#52) and also under the REFILL multiple (#52.1) of \nthrough the Austin Automation Center (AAC). VistA will be enhanced to receive\n the PRESCRIPTION file (#52). This field is used to indicate that a\n claim should be electronically re-transmitted to the 3rd party payer\n (insurance company). It will be primarily used by CMOP and local mail\n prescriptions.\n \n14. A new multiple REJECT INFO field (#52.25) has been created on the\n PRESCRIPTION file (#52) to store information about DUR and Refill Too\n Soon Rejects returned by 3rd party payers. \n The following fields are part of this multiple:\n \nelectronic adjudicated responses from the third party payers, which include\n .01 NCPDP REJECT CODE \n 1 DATE/TIME DETECTED \n 2 PAYER MESSAGE \n 3 REASON \n 4 PHARMACIST \n 5 FILL NUMBER \n 6 GROUP NAME \n 7 PLAN CONTACT \n 8 PLAN PREVIOUS FILL DATE\n 9 STATUS \nreal-time processing for Drug Review Utilization and Refill Too Soon rejects.\n 10 CLOSED DATE/TIME \n 11 CLOSED BY\n 12 CLOSE REASON\n 13 CLOSE COMMENTS\n 14 REASON FOR SERVICE CODE\n 15 PROFESSIONAL SERVICE CODE\n 16 RESPONSE ID\n 17 OTHER REJECTS \n 18 DUR TEXT \n 19 RESULT OF SERVICE CODE\nReject information will be displayed to the pharmacist as the prescription is\n 20 INSURANCE NAME \n 21 GROUP NUMBER \n 22 CARDHOLDER ID \n 23 RE-OPENED\n \n Two new cross-references named "REJDAT" and "REJSTS" were created for\n this multiple in the PRESCRIPTION file (#52). The "REJDAT" uses the\n DATE/TIME DETECTED field (#1) and the "REJSTS" uses the STATUS field\n (#9).\nbeing processed. The pharmacist will have the capability to take the\nappropriate action to ensure patient safety or to override the reject and\n(HIPAA) for pharmacy claims. The HIPAA NCPDP - GLOBAL project involves six\nresubmit the claim to the payer for payment. When a status of "PAYABLE" is\nreturned by the payer for a released prescription, VistA will automatically\ncreate the bill in IB, authorize it and immediately create the receivable in\nthe AR application. Since the exact amount being paid by the payer is known,\na decrease adjustment will be automatically generated and applied so that the\nreceivable is equal to the net amount due from the payer.\n \nThe system also provides electronic payment matching capability (for\nelectronically billable outpatient pharmacy prescriptions) using the existing\nElectronic Data Interchange (EDI) Lockbox functionality which processes other\ndifferent applications that have been significantly changed to enable VA\nelectronic payments from third party payers. This real-time electronic claims\nprocessing capability will be provided in accordance with the HIPAA, EDI\nand the NCPDP mandated format standards, specifically NCPDP Telecommunication\nStandard V. 5.1. Additional functionality delivered with this project \nincludes:\n \n . Auto-Release/Outpatient Pharmacy Automation Interface (OPAI) Integration.\n . Back-billing capability to allow electronic billing of claims from within\n the IB application.\n . Capability to MOVE a group of subscribers from one insurance plan to\nMedical Centers to perform third party electronic billing for prescriptions\n another while automatically "expiring" the old plan, which is a major\n time saver.\n . Pharmacy Dispensed As Written (DAW) prescription processing.\n \nOverview of the Process:\n \nWhen a prescription is about to be filled and dispensed by the pharmacy, the\nOP application submits the prescription to the new ECME application. ECME then\ncontacts IB to verify whether or not the prescription is electronically\nbillable. If so, ECME gathers the information necessary to generate a NCPDP\nusing the NCPDP standard. \nclaim. The claim information is passed to the VistA Health Level Seven (HL7)\npackage. The HL7 package then sends the billing information to the AAC, where\nit is routed to the corresponding third party insurance via Emdeon (formerly\nWebMD).\n \nOnce the payer processes the information, the response coming back from the\npayer is passed back to the site that made the request, and the information\nis stored in the ECME package. If the third party payer accepted the claim,\nthe adjudicated information is passed along to IB. If the claim was rejected\nthe problem can be worked on and a new claim can be submitted to the payer.\n \n \nFor electronically billable CMOP prescription processing, the third party\nclaim is sent before the prescription information is transmitted to the\nCMOP facility to be filled. Once the adjudicating response is electronically\nreceived from the third party payer, if there are no Drug Utilization Review\nor Refill Too Soon rejects, the prescription is then transmitted to the CMOP\nfacility. When the CMOP center sends the dispensing information back to VistA,\nthe National Drug Code (NDC) information is checked against the NDC sent to\nthe third party payer and, if different, a new claim is generated in the\nbackground and is sent to the third party payer. In case the CMOP facility\nBelow is a list of all the applications involved in this project along with\nindicates that it is unable to fill a "PAYABLE" prescription fill, a reversal\nis automatically submitted to the third party payer for the corresponding\nfill.\n \nThis patch modifies the OP application to perform real-time electronic claim\nsubmission to third party payers. It will also enable OP users to see and act\non third party payer rejects such as Drug Utilization Review (DUR) and Refill\nToo Soon rejects along with their daily normal prescription processing \nactivities. The following areas of OP have been changed:\n \ntheir patch number:\n1. Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option \n \n At the point that the prescription is verified, the New Order, Edit,\n Renew, Refill, and Pull Early from Suspense functions will begin the\n third party billing evaluations. If IB determines that the\n prescription is third party billable, a message will be displayed on\n the user's screen stating that the claim is being submitted to ECME\n and it will also show the progress of the claim. If the payer rejects\n the claim for DUR or Refill Too Soon, the payer's information will be\n displayed, and the user will be given the opportunity to either ignore\n\n
\nThe Registration application has released enhancements designed to\nfunctionality made available by the Registration application. More\n IMPORTANT FUNCTIONALITY CHANGE:\n ==============================\n - A new prompt "Do you want to update the Permanent address/phone?\n //N" will be displayed before editing the permanent address/phone\n information to give the user a chance to skip it. If the user\n responds with "N", the control will go to the CNH CURRENT field\n prompt. Otherwise, the user will go through editing the\n address/phone information fields.\n \n - When entering a new or updating an existing patient permanent\nspecifically, the update of the patient permanent address through the\n address, the information is not saved to the database until the\n prompt above "Are you sure that you want to save the above changes?"\n is answered YES. If the application times out or an '^' (up-arrow)\n is entered in any of the permanent address fields above, the changes\n are NOT saved.\nOutpatient Pharmacy application will be enhanced with the new \nfunctionality that was recently released by the Registration application\nwith the patch DG*5.3*522.\n \nFor sites that have patch IVM*2*108 installed, the address history will\ncaptured in the IVM ADDRESS UPDATE LOG File (#301.7).\n \nTwo places in the Outpatient Pharmacy application will be affected by\nprovide a more accurate and cleaner update of the patient address. One\nthis change:\n \n 1) Menu option: Update Patient Record [PSO PAT]\n 2) Patient Information screen, option PU - Patient Record Update\n \n Note: The Patient Information screen can be reached through the menu \n options Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n and Complete Orders from OERR [PSO LMOE FINISH].\n \nThe examples below show how the patient permanent address edit was before\nof the things included in the enhancements is the automatic population\nand how it is going to be changed after this patch is installed:\n \n BEFORE THIS PATCH:\n =================\n : : : :\n : : : :\n STREET ADDRESS [LINE 1]: 123 FAKE ST <RET>\n STREET ADDRESS [LINE 2]: <RET>\n STREET ADDRESS [LINE 3]: <RET>\n CITY: PLANO <RET>\nof city, state, and county based on entry of a zip code. For more\n STATE: TEXAS <RET>\n ZIP+4: 75024 <RET>\n COUNTY: COLLIN <RET>\n 1 COLLIN 085\n 2 COLLINGSWORTH 087\n CHOOSE 1-2: 1 <RET> COLLIN 085\n PHONE NUMBER [RESIDENCE]: 972-555-1234 <RET>\n CNH CURRENT:\n : : : :\n : : : :\ndetailed information about this and the other enhancements recently \n \n AFTER THIS PATCH:\n ================\n : : : :\n : : : :\n Do you want to update the Permanent address/phone? NO// YES\n STREET ADDRESS [LINE 1]: 123 FAKE ST <RET>\n STREET ADDRESS [LINE 2]: <RET>\n ZIP+4: 75024 <RET>\n \nreleased by the Registration application, please refer to the patch \n Select one of the following:\n \n 1 PLANO*\n 99 FREE TEXT\n \n CITY: // 1 <RET> PLANO*\n STATE: TEXAS <DISPLAY>\n COUNTY: COLLIN <DISPLAY>\n PHONE NUMBER [RESIDENCE]: 972-555-1234 <RET>\n PHONE NUMBER [WORK]: 972-555-4321 <RET>\ndescription of DG*5.3*522.\n BAD ADDRESS INDICATOR: ? <RET>\n \n Please enter 1 if the address is 'UNDELIVERABLE', 2 if the patient\n is 'HOMELESS', or 3 for 'OTHER' bad address reasons.\n Choose from: \n 1 UNDELIVERABLE\n 2 HOMELESS\n 3 OTHER\n \n \n \n BAD ADDRESS INDICATOR: <RET>\n Are you sure that you want to save the above changes? NO// YES <RET>\n Change saved.\n \n CNH CURRENT:\n : : : :\n : : : :\n \n \n NOTES:\nThis patch is responsible for updating Outpatient Pharmacy with the new\n =====\n 1) Multiple ":"'s above indicate that other fields have been \n suppressed to abbreviate the example.\n 2) <RET> indicates the <RETURN> key.\n 3) <DISPLAY> indicates that the field was displayed and was not \n editable.\n 4) BAD ADDRESS INDICATOR is a new field introduced by the \n Registration application. For more information on this field,\n please refer to the documentation for that application.\n \n\n
\nCORRECT SEVERAL PROBLEMS INCLUDING AMIS COMPILER TO FIND AND INCLUDE RX'S \nTHAT HAVE A DATE WITH NO TIME FOR RELEASE/DATE FIELD IN PRESCRIPTION FILE,\nA NULL SUBSCRIPT ERROR DURING BINGO BOARD STARTUP, DO NOT MAIL ISSUE WHEN\nOPAI SENDS HL7 MESSAGE, AND INCREASE DNS PORT NUMBER FIELD IN OUTPATIENT\nSITE FILE.\n\n
\nCORRECT CLOZAPINE OVERRRIDE LIST ERROR AND CORRECT FINISHING OF PENDING \nORDERS THAT ARE OLDER THAN A YEAR AND ARE BASICALLY EXPIRED.\n\n
\nPrevent newly Discontinued Rx's due to edit from being sent to the\nExternal Dispense Machines.\n\n
\n1. This patch makes it possible to exempt certain Ward Locations from the\nAutocancel Rx's on Admission [PSO AUTOCANCEL1] option.\n \n2. This patch adds a Requesting PROVIDER prompt to the discontinue\nand speed discontinue dialogue. When an order is discontinued, this new\nprompt will be asked after the Nature of Order prompt. The requesting\nprovider information will be used to update the Computerized Patient\nRecord System (CPRS) order. The CPRS order will now reflect the correct\nprovider that requested the discontinue of the order. This new prompt\nwill only be given when an order is discontinued through one of\nthe Discontinue ListMan actions, or the Discontinue Prescription(s) [PSO\nAutocancel Rx's on Admission [PSO AUTOCANCEL1] option. When that job runs,\nC] option.\n \n3. This patch fixes a problem that can occur when removing a prescription\nfrom Hold in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\noption. This problem can only occur for sites that are using vendor\nsoftware to bill prescriptions for Tricare. When removing a prescription\nfrom Hold, the software currently checks to see if the prescription\nis eligible for Tricare billing, and can possibly resubmit the\nprescription for Tricare billing. A problem can occur if it continues\nto be rejected by Tricare. This causes the prescription to remain in a\nand it comes across a patient that is on a Ward Location designated as\nHold status, and there is no way to print a filling label for that\nprescription. After this patch is installed, any prescription that is\nremoved from Hold will not automatically go through the Tricare process.\nThese prescriptions will either print locally or suspend. Then it would\nbe possible to manually resubmit billing for that prescription, but now\na filling label will first print for these prescriptions.\n \n4.This patch fixes an undefined error that can occur when trying to\nreinstate a prescription for a deceased patient.\nexempt from the Autocancel Rx's on Admission [PSO AUTOCANCEL1] option, the\nprescriptions for that patient will not be canceled. To designate a Ward\nLocation as exempt from this job, use the Site Parameter Enter/Edit [PSO\nSITE PARAMETERS] option. Under the Outpatient System Parameters section of\nthat option, there is a field called EXEMPT WARD FROM AUTOCANCEL (#40.19),\nand here you can designate any number of Ward Locations as exempt from the\n\n
\nThis patch supports the National Council for Prescription Drug Programs (NCPDP) \ninstructions please refer to the installation steps provided in each of the \nstand-alone patches.\n \nEnhancements included in the release of the six patches are a new option that \nwill enable the user to reopen a closed Electronic Claims Management Engine\n(ECME) claim; updates to the Rx Activity Log; and permanent storage of Claims\nactivity information as reported by the ECME Billing Events Report. \n \nThis patch modifies the Outpatient Pharmacy (OP) V. 7.0 application in the\nfollowing areas: \nstandard which was adopted under the Healthcare Insurance Portability and \n \n1. When the DAW CODE was edited on a released Consolidated Mail Outpatient \n Pharmacy (CMOP) prescription it was not triggering an automatic claim \n reversal/re-submit to the third party payer. This patch corrects the \n problem. Editing the DAW CODE on a released CMOP prescription will work\n similar to editing a WINDOW prescription, it will reverse/re-submit a\n claim.\n \n2. The ECME Reject section of the prescription activity log was changed in\n the following ways: \nAccountability Act (HIPAA) for pharmacy claims. This patch is one of six to be\n \n 2.1) The column header "Date/Time" was changed to "Date/Time Rcvd" because\n a new column is being created (see 2.3).\n 2.2) "DRUG UTILIZATION REVIEW" in the "Reject" column will now display as\n "DUR" for space saving purposes.\n 2.3) A new column is being created called "Date/Time Resolved" on the\n right hand side to display the Date/Time the reject was resolved.\n \n3. The option Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST]\n is being changed to allow the user to print a label for window\nreleased. Three patches will be released in a KIDS multi-build distribution \n prescriptions after a reject is resolved. The label print prompt will only\n be available if the prescription is active and no label was printed for\n the fill which reject was resolved. The following prompts will be \n presented to the user:\n \n Print Label? YES // YES\n \n Select LABEL DEVICE:\n \n4. When the user resolved a third party reject using the 'Override Reject'\ncontaining: BPS*1*3, PSO*7*247, and IB*2*342. Three patches will be released\n action from the Third Party Payer Rejects - Worklist [PSO REJECTS \n WORKLIST] option, the entry in the Prescription activity log \n corresponding to this event was not displaying the NCPDP override codes\n entered by the user. Before this fix the comment displayed as \n 'Submitted to ECME:REJECT WORKLIST-E PAYABLE'. After this patch is\n installed the comment will be logged as 'Submitted to ECME:REJECT \n WORKLIST-DUR OVERRIDE CODES(NN/AS/1B)-E PAYABLE', as an example.\nindividually and they are: PRCA*4.5*247, PSX*2*62, and PSS*1*115. There is no \nrecommended order to installing the stand-alone patches and they can be \ninstalled independently of the multi-build as there is no dependency between \nthe multi-build distribution and the stand-alone patches. For more specific \n\n
\nThe Department of Veterans Affairs National Clozapine Coordinating Center\nread the patch description of YS*5.01*90 for complete details of this new\nenhancement.\n \nThis Outpatient Pharmacy patch PSO*7*222 contains the following\nmust-do-work enhancements for Clozapine dispensing:\n \n1. Adjust the business rules to disallow prescription processing without\n override if 3500/mm3>WBC>3000/mm3 and 2000/mm3>ANC>1500/mm3.\n These levels require twice weekly blood testing until the WBC\n stabilizes above 3500/mm3 and ANC above 2000/mm3 with no signs of\n(NCCC), is requesting modifications to Veterans Health Information Systems\n infection.\n2. Modify routine logic to recognize the new monthly status and apply the\n appropriate restrictions for lab draw checks.\n3. Add a new field to the PRESCRIPTION file (#52) to store ANC value and\n modify routine logic to require both a WBC and ANC be drawn and\n reported before drug dispensing is allowed.\n4. Modify routine logic to prevent local users from editing the Patient\n Status within Clozapine module.\n \nThis patch transports the following fields:\nand Technology Architecture (VistA) Outpatient Pharmacy and Mental Health\n1. The field length of the WBC RESULT field (#302) of the PRESCRIPTION\n file (#52) is modified from 3 to 5 digits to accommodate values up to\n 99999 as these values will be stored in 1000s.\n2. A new field ANC RESULTS field (#304) is added to the PRESCRIPTION file\n (#52) to store the ANC test value.\n3. The field name of REASON FOR LOCKOUT field (#4) of the CLOZAPINE\n PRESCRIPTION OVERRIDES file (#52.52) is changed to REASON FOR OVERRIDE.\n The set of codes have been modified and three new codes were added. The\n modified Data Dictionary (DD) is as follows:\n \napplications to meet revisions in the Food and Drug Administration (FDA)\n 52.52,4 REASON FOR OVERRIDE 0;5 SET (Required)\n '1' FOR NO WBC IN LAST 7 DAYS;\n '2' FOR NO VERIFIED WBC;\n '3' FOR LAST WBC RESULT < 3500;\n '4' FOR 3 SEQ. WBC DECREASE;\n '5' FOR LAST ANC RESULT < 2000;\n '6' FOR 3 SEQ. ANC DECREASE ;\n '7' FOR NCCC AUTHORIZED;\n \n \nmonitoring requirements for blood monitoring in patients being treated\nThe Outpatient Pharmacy patch PSO*7*227, TRANSITIONAL PHARMACY BENEFIT\n(TPB) inactivation, was placing the TPB HL7 Data Extract/Transmission [PSO\nTPB HL7 EXTRACT] option out of order. Sites testing patch PSO*7*227\nrecommended that we remove this task totally from the OPTION SCHEDULING\nfile (#19.2). Therefore, a post-install routine (PSOP222) is included in\nthis patch PSO*7*222 to delete the TPB HL7 Data Extract/Transmission [PSO\nTPB HL7 EXTRACT] option from the OPTION SCHEDULING file (#19.2).\nThe post-install routine will also provide the following changes:\n1. As the patch PSO*7*227 inactivated the TPB functionality, the security\n access codes for the TPB ELIGIBILITY file (#52.91) still remains open.\nwith Clozapine.\n These codes will be changed to "@" sign restricting access to\n programmers only.\n2. The read access code of the PRESCRIPTION REFILL REQUEST file (#52.43)\n is currently set to "@" sign (programmer access). As per the\n Electronic, Error and Enhancement Report (E3R) 19725 request, this will\n be changed to "Pp" (Pharmacy Package) access.\n \nThis patch PSO*7*222 is associated with the MENTAL HEALTH V. 5.01 patch\nYS*5.01*90 and patch YS*5.01*90 is a required patch for PSO*7*222. Please\n\n
\nThis patch enhances the usage of Application Program Interfaces (APIs) to\nthe patient's address when appropriate. If the patient has the BAD ADDRESS\ntime the label printed.\n \n6. In the Complete Orders from OERR [PSO LMOE FINISH] option, after the \nprompt to display the medication profile and after the patient name and \nsocial security number are shown, if the patient's address is flagged \nwith a Bad Address Indicator, a warning message is displayed. If the \ntemporary address is active, that information is displayed. The user\nwill not be prompted to update the address.\n \nExample:\nINDICATOR field set and no active temporary address, this is referred to\nDo you want to see Medication Profile? Yes// NO\n \n PERPATNM,FRED (666-00-0777)\n \n WARNING: The patient address is indicated as a bad\n address (UNDELIVERABLE).\n * Temporary address is active *\n \nPress Return to continue: \n \nas a BAI condition in this description.\n7. The Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] option \nis modified to display **BAD ADDRESS INDICATED-(REASON)" where REASON is \nUNDELIVERABLE, HOMELESS, or OTHER.\n \n8. Although the Transitional Pharmacy Benefits (TPB) options have been \ndisabled, to keep the changes consistent, the routine to print TPB letters\nis modified to look at the BAI condition and print "** BAD ADDRESS\nINDICATED ** if applicable.\n \n9.The Patient Address Changes Report [PSO ADDRESS CHANGE REPORT] option \n \nis modified to display additional mailing address-related fields from the\nPATIENT file (#2) and some fields related to the mail setting from the\nPHARMACY PATIENT file (#55). The user should use FileMan to turn \non auditing for the following fields in order for them to be displayed \nin this report. (Fields added to this report by this patch are indicated\nwith a "*" in front of the field name).\n \na. For the PATIENT file (#2), turn on auditing for:\n \nSTREET ADDRESS [LINE 1] field (#.111)\nNote: Related changes for the Outpatient Pharmacy Automation Interface\nZIP+4 field (#.1112)\nSTREET ADDRESS [LINE 2] field (#.112)\nSTREET ADDRESS [LINE 3] field (#.113)\nCITY field (#.114)\nSTATE field (#.115)\nZIP CODE field (#.116)\n* BAD ADDRESS INDICATOR field (#.121)\n* TEMPORARY ADDRESS ACTIVE? field (#.12105)\nTEMPORARY STREET [LINE 1] field (#.1211)\nTEMPORARY ZIP+4 field (#.12112)\n(OPAI) and Consolidated Mail Outpatient Pharmacy (CMOP) will be done in\nTEMPORARY STREET [LINE 2] field (#.1212)\nTEMPORARY STREET [LINE 3] field (#.1213)\nTEMPORARY CITY field (#.1214)\nTEMPORARY STATE field (#.1215)\nTEMPORARY ZIP CODE field (#.1216)\n* TEMPORARY ADDRESS START DATE field (#.1217)\n* TEMPORARY ADDRESS END DATE field (#.1218)\n \nb. For the PHARMACY PATIENT file (#55), turn on auditing for:\n* MAIL field (#.03)\npatches PSO*7*200 and PSX*2*54.\n* MAIL STATUS EXPIRATION DATE field (#.05)\n \n10. By request of a pharmacy workgroup, two new codes were added to the\nPRESCRIPTION file (#52) HOLD REASON field (#99):\n '7' FOR BAD ADDRESS; \n '8' FOR PER PATIENT REQUEST; \n \n \n11. A Bad Address Reporting Main Menu [PSO BAI REPORT] option is added \nunder the Output Reports [PSO OUTPUTS] option which includes the\n \nfollowing:\na. Bad Address Suspended List [PSO BAI SUSPENDED] option\nThis option identifies prescriptions for veterans with a BAI Condition\ngiving the opportunity to be proactive regarding prescriptions that when\nPrinted or Pulled Early from Suspense, would be unable to be mailed.\n \nb. List Prescriptions Not Mailed [PSO BAI NOT MAILED] option \nThis option provides a report of prescriptions with a routing of Mail that\nwere not mailed due to a bad address. This is based on the last label\nactivity entry being flagged as a bad address and a route other than\n \n"WINDOW". If the address is corrected and a label reprinted, this\nprescription would no longer show on the report.\n \n12. The View Prescriptions [PSO VIEW] option is changed to show Bad \nAddress Indicated if BAI flag is set and no active temporary address. \nExample:\nVIEW PRESCRIPTION: 713449A ACETAMINOPHEN 325MG TAB \n \n \nRx View (Active) Aug 30, 2006@18:44:09 Page: 1 \nThe following changes are made in this patch:\nof 5 \nOUTPATIENT,ONE ** BAD ADDRESS INDICATED-(UNDELIVERABLE)\n PID: 666-00-0146 Ht(cm): _______ \n(______) \n DOB: DEC 00,1953 (52) Wt(kg): _______ \n(______) \nthe Registration Package V. 5.3 to check the setting of the BAD ADDRESS\n \n1. A new security key PSO ADDRESS UPDATE is added. Either the EDIT \nPATIENT DATA field (#.123) in the PSO SITE file (#59) must be set to \n"Yes" or the user must have this new security key in order to be\nprompted to update the address (permanent and/or temporary addresses).\n \n2. When selecting a patient name in the Patient Prescription Processing \n[PSO LM BACKDOOR ORDERS] option, if the patient's address is flagged with\na Bad Address Indicator, then a warning message is displayed. If the \nEDIT PATIENT DATA is set to Yes or the user holds the new\nINDICATOR field (#.121) in the PATIENT file (#2) and to update the\nPSO ADDRESS UPDATE security key, he will be asked if he wants to update\nthe patient's address. If there is a valid temporary address, a message to\nthat effect is displayed before the prompt to update the address.\n \nExample:\n PSOOUTPATIENT,ONE (000-00-0777)\n \n WARNING: The patient address is indicated as a bad\n address (UNDELIVERABLE).\n * Temporary address is active *\npermanent and temporary addresses. The BAD ADDRESS INDICATOR (referred to\nDo you want to update the address/phone? N// YES\nUpdate (P)ermanent address, (T)emporary, or (B)oth: BOTH// \n \n3. In the Medication Profile [PSO P] option, the Patient Prescription \nProcessing [PSO LM BACKDOOR ORDERS] option, and the Complete Orders from\nOERR [PSO LMOE FINISH] option, the following changes were made:\na. When the medication profile is displayed, the letter "B" (for bad\naddress) is added to the status column if the last label activity for that\nprescription indicated a BAI condition. If the address is corrected and\nlabel reprinted, "B" no longer appears on the profile.\nas BAI in this description) is one of the fields presented when using the\n \nExample:\n \n Medication Profile Sorted by ISSUE DATE\n REF\n Rx# Drug ST REM Issued \nLast Fill\n--------------------------------------------------------------------------\n-----\n$300920A ACETIC ACID 2% OTIC SOL 15 ML DCB 5 07-20-06 \nAPI to update permanent address fields.\n07-20-06\n QTY: 1 SIG: INSTILL 2 DROPS AD AS NEEDED \n$100002514C SIMVASTATIN S 5 06-29-06 \n12-10-06\n QTY: 150 SIG: ONE IV TWICE A DAY\n$300927 UREA 10% LOTION AB 5 06-29-06 \n06-29-06\n QTY: 1 SIG: APPLY SPARINGLY TO AFFECTED AREA AS NEEDED\n \nb. If there is no ending date for the temporary address, the fact that the\n \naddress was temporary was not being displayed in the patient profile.\nThis patch adds the temporary indication including the text "(no end\ndate)" if no ending temporary date exists.\n \nExample:\n \nDisabilities: \n \n (Temp Address from AUG 28,2006 till (no end date))\nLINE1 \nOutpatient Pharmacy V. 7.0 options are modified to not print the \nANYTOWN PHONE: \n555-1212 \nTEXAS \n77379 \n \n \n4. The Input Template [PSO OUTPT] is modified to remove temporary\naddress update prompts. Instead, a new API to the Registration Package \nV. 5.3 is used for updating temporary address for the Update Patient\nRecord [PSO PAT] option and the Patient Record Update [PU] action (within\npatient's address if a bad address is indicated and to prompt to update\nthe patient profile). This option and action are also changed to check for\nthe user holding the PSO ADDRESS UPDATE security key or the EDIT PATIENT\nDATA field is set to "Yes" before the user is prompted to update the\naddresses.\n \n5. The following changes are made to laser label printing:\na. If BAD ADDRESS INDICATOR is set and there is no active temporary\naddress, the Mailing label prints ** BAD ADDRESS INDICATED ** and does not\nprint the rest of the mailing address.\nb. An additional label log entry added for bad address indicated at the\n\n
\nThe following describes all of the changes included in this patch:\nactivity log entry was created with a reason of "RETURNED". For those\n \nC. For a patient defined as SC<50 but had a null SC percentage value \ndefined, backdoor Outpatient Pharmacy was asking the SC prompt but not\nstoring the answers. The SC prompt is only displayed for those\nprescriptions that the Scheduling DBIA #1579 and/or the Integrated \nBilling (IB) DBIA #125 determines that it should be asked. Upon release\nof the fill, a "PRESCRIPTION QUESTIONS REVIEW NEEDED" mailman message\nrequesting entry of the SC field was sent to holders of the PSO COPAY\nkey. Because this functionality uses the same checking mechanism as\nnon-exempt new orders, the following functions were affected by this\nprescriptions where copay was cancelled, a copay activity log was\nchange: copies, renews and edits that create a new order. This patch will\nstore the SC answer for null SC percentage values.\n \nD. The SC prompt was not asked in Computerized Patient Record System \n(CPRS), but was asked in backdoor Outpatient Pharmacy. No default answer\nwas shown in backdoor due to the question not being asked in CRPS. This\noccurred for any SC percentage that the SDCO22 API (#1579) returned a\nvalue that indicated to not ask the SC question but IB returned a flag\nthat indicated that the SC question should be asked. This problem occurs\nfor a variety of SC percentages based on how the patient's eligibility is\ngenerated. The following are examples of those types of entries made by\ndefined in enrollment. This patch will tell CPRS to ask SC for this\nscenario.\n \nE. It was found that edits made to SC and/or EI's during COMPLETE ORDERS\nFROM OERR [PSO LMOE FINISH] option and the finish function in the PATIENT\nPRESCRIPTION PROCESSING [PSO LM BACKDOOR ORDERS] option were not reflected\nin CPRS. With the CIDC patches, a new standardized segment was created to\npass SC, EI's and ICD-9 diagnosis codes and use of the old segment was\ndiscontinued. When the CPRS CIDC switch is off, CPRS is looking at the old\nsegment for updated orders. This patch adds the functionality to send both\nPSO*7*226.\nZSC and ZCL segments.\n \nF. When using the edit function in the PATIENT PRESCRIPTION PROCESSING\noption [PSO LM BACKDOOR ORDERS], the total number of entries in the ICD\nDIAGNOSIS multiple (#52311) was being defined as one number less than it\nshould have been. For example, eight diagnosis codes entered but the \nmultiple shows seven as the total number of entries for the multiple. The\ndiagnosis codes were displayed correctly to the user. This patch will\nstore the correct number of entries when edits are performed.\n \n \nG. The PSOHLNE3 API IA (#4666) was defining an activity log entry that \nstated "Clinical Indicators and SC/EI's were updated from a CPRS e-sig \nedit..." for all prescriptions passed through the API. Also, it was \nneedlessly defining a copay activity log entry for supply items and\ninvestigational drugs. Last, it was storing a copay activity log entry\n(copay to no copay) that was set erroneously when the provider edits\nSC/EI's during sign of a verbal/telephone order leaving the prescription\nas no copay. This API is used to pass data from CPRS to OP when a verbal\nor telephone order is signed in CPRS when the CPRS CIDC Switch is on. \nThis patch limits the setting of the activity log to only those\nActivity Log Example:\nprescriptions where SC, EI's and/or ICD's were changed during sign order.\nAnd, it eliminates setting the copay activity log for supply items and\ninvestigational drugs as well as eliminating the erroneous "copay to no \ncopay" activity log entry.\n \nH. The RESET COPAY STATUS/CANCEL CHARGES option [PSOCP RESET COPAY \nSTATUS] was overlaying the previously stored diagnosis code when storing\nupdated information. Also, the default answer for SC was not being\ndisplayed for SC<50% patients. This patch corrects these issues.\n \n \nI. When the CPRS CIDC switch is turned on, the B cross reference was \nnot being defined in the ICD DIAGNOSIS field (#311) in PENDING OUTPATIENT\nORDERS file (#52.41). For telephone/verbal orders signed in CPRS and \nCPRS renewals, the B cross reference was not being defined in the ICD\nDIAGNOSIS field (#52311) in PRESCRIPTION file (#52). This was not\nreported as an issue, but the correction is being made in this patch.\n \n \nTechnical Descriptions:\n=======================\n 1 11/28/05 X-INTERFACE ORIGINAL PHARMACIST,ONE\n1. For Remedy Ticket 130112:\n \nA. A snapshot of the ACTIVITY LOG sub-file (#40) and the COPAY \nACTIVITY LOG sub-file (#107) will be stored in ^XTMP("PSOCIDC7") node,\nand will be available for 90 days.\n \nB. The "BKGD CIDC UPDATE" activity log entry will be removed and the \nACTIVITY LOG sub-file (#40) will be re-subscripted to eliminate the\nmissing node. The removed entry will be inserted in the COPAY ACTIVITY LOG\nsub-file (#107). The date given in the old activity log entry will be\n Comments: Prescription sent to external interface.\nused as the COPAY ACTIVITY LOG field (#.01) for the new entry. The copay\nactivity log will be sorted by dates within the existing entries and\nincluding the new entry, then they will be stored back into the COPAY\nACTIVITY LOG sub-file (#107). The comment for the new copay activity log\nentry as well as any existing copay activity log entries will be changed\nto state "CIDC CLEANUP" instead of "BKGD CIDC UPDATE".\n \nC. Because the copay to no copay or vice versa information was not \nrecorded in the old Activity log entry, those values can only reflect the \ncurrent state of the prescription, and it's thought that they should not\n 2 11/28/05 RETURNED ORIGINAL POSTMASTER\nbe stored on the new entry.\n \nD. To print the report of all prescriptions updated by the Clean-up \nroutine, type the following from the programmer's prompt using the print \ndevice that you prefer.\n \n >D RPT^PSOCIDC9\n DEVICE: HOME// UCX/TELNET RIGHT MARGIN:80//\n \n Patch PSO*7*239 - Corrected Activity and Copay Activity logs\n \n Comments: BKGD CIDC UPDATE\n \n Note that this report reflects all prescriptions where the activity\n and/or copay activity logs were corrected. For detailed information,\n please view the activity and copay activity log on the prescription.\n \n Date printed: MAR 6,2006@14:09:25 Page: 1\n ===============================================================\n PATIENT NAME (SSN) DIV RX# \n --------------- ------- -------------- ------------\n PATIENT,ONE (B3453) TROY, NY 200037\n 3 11/29/05 X-INTERFACE REFILL 1 PHARMACIST,TWO\n BPATIENT,TWO (B0033) TROY, NY 200049\n BPATIENT,TWO (B0033) TROY, NY 200050\n \nE. The following is an example of a status query for the Clean-up \nroutine, and it must be run from programmer's mode:\n \n >D STATUS^PSOCIDC7\n \n Currently processing:\n Date being processed > Nov 3, 2005\n Comments: Prescription sent to external interface.\n RX # > 1375666\n \nF. A stop function has been provided in case the system needs to be\nshut down for an emergency or other reason. Then when the system is back\nup and you are ready you may restart the job, it will resume where it\nleft off. You may restart by entering D ^PSOCIDC7 at the programmer's\nprompt. The following is an example:\n \n >D STOP^PSOCIDC7\n \n \n Outpatient Activity Logs Correction Job - set to STOP Soon\n \n Check Status to be sure it has stopped and is not running...\n \n (D STATUS^PSOCIDC7)\n \nG. The Clean-up routine can be executed from the programmer's \nprompt instead of through the patch installation. Also, restarting the\nClean-up routine after using the stop function described above is \nperformed in the same manner. Below is an example how to perform this \nCopay Activity Log Example:\nfunction:\n \n >D ^PSOCIDC7\n \n ****************** SELECT RUN OPTION ******************\n Do you want to run the activity logs correction process? Y or N// YES\n Enter when to Queue the CIDC ACTIVITY LOGS CORRECTION job to run in \n date@time format: NOW//\n \n ===================================================\n \n Queuing background job for CIDC ACTIVITY LOGS CORRECTION...\n Start time: Month day, year@time\n ===================================================\n *** Task #NNNNN Queued! ***\n \n \n2. The following correlates to the items described in number two in the\nFunctional Description section:\n \nA. The renew process has been modified to store the changed value\n 1 02/01/06 COPAY RESET ORIGINAL PHARMACIST,ONE\nfor SC in the PRESCRIPTION file (#52).\n \nB. This patch will remove all of the functionality that stored the\nunnecessary IBQ node.\n \nC. Outpatient was modified to store the SC value for patients with a null\nSC percentage which eliminates the sending of a "PRESCRIPTION QUESTIONS\nREVIEW NEEDED" Mailman message.\n \nD. The check for the PSOSCMX variable was restored to the PSOCP\n Comment:-BKGD CIDC COPAY CANCEL Old value=Copay New value=No Copay\nroutine. \n \nE. This patch adds the functionality to send both ZSC and ZCL segments to\nCPRS. The ZSC passes SC/EI's only. The ZCL node passes SC, EI's, and\nICD-9 Diagnosis codes.\n \nF. This patch will correctly store the third and fourth piece of the zero\nnode of the ICD DIAGNOSIS multiple (#52311) of PRESCRIPTION file (#52).\n \nG. The PSOHLNE3 API IA (#4666) was changed to only store entries in the \n 2 02/01/06 REMOVE COPAY CHARGE ORIGINAL PHARMACIST,ONE\nACTIVITY LOG multiple (#40) when SC, EI's, and/or ICD's were edited. \nFor supply items and investigational drugs, no copay activity log entries \nwill be stored. Also, it was modified to prevent storage of a copay\nactivity log entry (copay to no copay) that was set erroneously when the\nprovider edits SC/EI's during sign of a verbal/telephone order leaving the\nprescription as no copay.\n \nH. The RESET COPAY STATUS/CANCEL CHARGES [PSOCP RESET COPAY STATUS] \noption has been modified to not overlay the previously stored \nICD-9 Diagnosis code with a null value and to display previously entered\n Comment: RX EDITED -BKGD CIDC COPAY CANCEL\nSC values as a default answer.\n \nI. The B cross reference will be set for the ICD DIAGNOSIS field (#311)\nin PENDING OUTPATIENT ORDERS file (#52.41) and in the ICD DIAGNOSIS field\n(#52311) in PRESCRIPTION file (#52) for CPRS renewals/verbal/telephone \norders.\n1. For Remedy Ticket 130112:\n \nTo eliminate any confusion, patch PSO*7*239 provides an Activity Log \nCorrection process/Clean-up routine. This routine will take the activity\nlog entries created by patch PSO*7*226, move them to the copay activity\nlog, and then subsequently will delete the activity log entries. Also,\nthe comment on the copay activity log entries where copay was cancelled as\nwell as those entries moved to the copay activity log will be changed to\n"CIDC CLEANUP". The activity log will be resequenced to eliminate any\nmissing nodes, and the copay activity log will be resequenced to insert\nthe new entries by date and time. The following are examples of the\n \nupdated entries:\n \n -Note that sequence two from the above example was removed and the\n third sequence was moved up.\n \n 1 11/28/05 X-INTERFACE ORIGINAL PHARMACIST,ONE\n Comments: Prescription sent to external interface.\n 2 11/28/05 X-INTERFACE REFILL 1 PHARMACIST,TWO\n Comments: Prescription sent to external interface.\n \nAfter installation of patch PSO*7*226, it was reported that the activity\n -The next entry shows an Activity log entry moved to Copay Activity log:\n \n 1 11/28/05 COPAY RESET ORIGINAL POSTMASTER\n Comment: CIDC CLEANUP\n \n -The following shows a cancelled Copay Activity Log entry comment\n updated to "CIDC CLEANUP:\n \n 1 02/01/06 COPAY RESET ORIGINAL POSTMASTER\n Comment: CIDC CLEANUP Old value=Copay New value=No Copay\nlog entries generated by the patch were confusing. A large part of patch\n 2 02/01/06 REMOVE COPAY CHARGE ORIGINAL POSTMASTER\n Comment: CIDC CLEANUP \n \nThis patch provides a listing of all prescriptions where the activity log\nwas updated by the Clean-up routine, a means of checking the status of the\nClean-up routine, and a means of stopping the Clean-up job if needed. A\ndetailed description of these functions is located in the Technical\ndescription.\n \nWhen installing this patch, the activity log Clean-up portion of this\nPSO*7*226 was to cancel any erroneously billed copays and to define any\npatch is optional. However, it is highly recommended that it be run for \nconsistency and maintainability.\n \nOnce the Clean-up routine has completed a mailman message will be sent to \nthe user who installed the patch. The following is an example:\n \n Subj: Outpatient Pharmacy PSO*7*239 CIDC ACTIVITY LOGS CORRECTION \n [#200121] 03/06/06@13:56 4 lines\n From: PSO*7*239 CIDC ACTIVITY LOGS CORRECTION In 'IN' basket. Page\n 1 *New*\nmissing IBQ nodes on the prescription using the SC/EI answers stored on\n \n-------------------------------------------------------------------------\n The CIDC ACTIVITY LOGS CORRECTION job for the Outpatient Pharmacy\n patch (PSO*7*239) started MAR 06, 2006@13:56:04\n and completed MAR 06, 2006@13:56:04.\n \n Enter message action (in IN basket): Ignore//\n \n2. The following issues were found during unit testing for backdoor \nOutpatient Pharmacy orders, and the corrections are included in this\nthe ICD node. For those prescriptions where the IBQ node was defined, an\npatch. \n \nA. When a prescriptions with an exempt patient status is renewed and the\nuser changes the value of service connected (SC), the default value was\nstored instead of the changed value. This only occurred for the SC\nprompt. The renew process has been modified to store the changed value.\n \nB. When prescription information was stored when the RX Patient Status \nwas exempt from copay, the IBQ node was being stored needlessly. This\npatch will remove the functionality that stored this node.\n\n\nTHIS PATCH WILL FIX TWO PROBLEMS.\n \nPROBLEM 1: AN ERROR OCCURS WHEN DISCONTINUING ALL PRESCRIPTIONS FOR A\nPATIENT.\nPROBLEM 2: REINSTATED DRUG DOSAGES DISPLAY ON OTHER PRESCRIPTION\n\n
\nThis Outpatient Pharmacy patch is part of the Patient Financial Services\nreplacement system. The project consists of the implementation of the \ndefined, that value will be passed to the COTS billing system for all \ndivision having prescriptions filled. If the CHARGE LOCATION is not\ndefined for any division and the PFSS switch is turned on, the\nprescription information will not pass to IB or the COTS billing system.\n \n \nTechnical Description:\n======================\n \nAt FINISH of the prescription fill:\nbilling replacement system, business process improvements, and \n \n1. The new IB API #4664 GETACCT^IBBAPI will be called to request a PFSS\nACCOUNT REFERENCE and it will be stored in the PRESCRIPTION file (#52) on\nthe fill level. For original fills, it will be stored in the PFSS ACCOUNT\nREFERENCE field (#125), and for refills it will be stored in the PFSS\nACCOUNT REFERENCE field (#21). These references uniquely identify the\nprescription to the COTS billing system.\n \n2. The array of data passed using the GETACCT^IBBAPI call encompasses all \nof the minimum required data elements as stated in the PFSS SRS-SDD IBB \nenhancements to VistA to support integration with the COTS billing\nGeneric API document. The following outlines data passed from \nOutpatient Pharmacy:\n \n $$GETACCT^IBBAPI(VAR1,VAR2,VAR3,VAR4,.ARR1,,,.ARR4,.ARR5,VAR5,,)\n Where: \n VAR1 = Patient Identifier (Patient IEN) \n VAR2 = PFSS Account Reference \n VAR3 = HL7 Event Code \n VAR4 = Application Location Reference\n ARR1 = ARR1(2) Patient Class, ARR1(3) Patient Location,\nreplacement system. Significant changes to VistA legacy systems and \n ARR1(7) Attending Physician, ARR1(44) Admit \n Date/Time (Fill Date), ARR1(50) Alternant Visit\n ID (Prescription IEN)\n ARR4 = ARR4(n,3) Diagnoses Code, ARR4(n,6) Diagnosis Type \n ARR5 = ARR5(n,2) Type\n VAR5 = Medical Center Division\n \n3. After IB returns the PFSS ACCOUNT REFERENCE to Outpatient Pharmacy,\nIB will pass the GETACCT information to the COTS billing system via the\nVistA Data Extraction Framework (VDEF) and will store the returned PFSS\nancillary packages are necessary.\nAccount Number external value in the PFSS ACCOUNT file (#375).\n \n \nAt RELEASE of the prescription fill:\n \n1. The new IB API # 4665 GETCHGID^IBBAPI will be called to request a PFSS\nCHARGE ID. This information is used to uniquely identify the fill in the\nIB and will be stored in Prescription file (#52) on the fill level. For\noriginal fills, it will be stored in the PFSS CHARGE ID field (#126), and\nfor refills it will be stored in the PFSS CHARGE ID field (#22). No data\n \nis passed using this API.\n \n2. Next, the new IB API #4665 CHARGE^IBBAPI will be called to pass\nprescription and copay information. This information will be stored in\nthe PFSS CHARGE CACHE file (#373). IB will batch the charge information\nand pass it on to the COTS billing system via VDEF.\n \n3. The array of data passed using the CHARGE^IBBAPI call encompasses all \nof the minimum required data elements as stated in the PFSS SRS-SDD IBB \nGeneric API document. The following outlines data passed from Outpatient\nSome of the PFSS software components are not operational until the PFSS \nPharmacy:\n \n $$CHARGE^IBBAPI(VAR1,VAR2,VAR3,VAR4,.ARR1,,.ARR3,.ARR4,.ARR5,,,)\n Where:\n VAR1 = Patient Identifier (Patient IEN) \n VAR2 = PFSS Account Reference \n VAR3 = Charge Type \n VAR4 = Unique Charge ID (PFSS Charge ID)\n ARR1 = ARR1(4) Transaction Date (Fill Date), ARR1(7) Transaction\n Code, ARR1(10) Transaction Quantity, ARR1(13) Department\nOn/Off Switch, distributed with patch IB*2*260, is set to "ON". The \n Code, ARR1(18) Patient Copay Status, ARR1(21) Ordered by\n Code, ARR1(22) Unit Cost, ARR1(29) NDC_";"_Generic\n Name, ARR1(31) Copay Transaction Type\n ARR3 = ARR3(n,3) Diagnoses Code, ARR3(n,6) Diagnosis Type\n ARR4 = ARR4(n,2) Type\n ARR5 = ARR5(1) Quantity_";;"_Days Supply, ARR5(17) Refills \n Dispensed (Fill Number), ARR5(18) Date of Most Recent\n Fill (Release Date), ARR5(31) DEA, Special Handling\n \n4. There will be no return messaging from the COTS billing system to \nability for the local site to set the switch to "ON" will be provided at \nOutpatient Pharmacy. Note that IB will combine the data passed in the\nGETACCT and CHARGE APIs to form the charge message that will ultimately\nbe passed to the COTS billing system via VDEF.\n \n \nCHARGE LOCATION additions:\n \n1. In the OUTPATIENT SITE file (#59), a new CHARGE LOCATION field \n(#1007) was added, and this field is a pointer to HOSPITAL LOCATION file \n(#44).\nthe appropriate time with the release of a subsequent Integrated Billing \n \n2. The Site Parameter Enter/Edit [PSO SITE PARAMETERS] option input\ntemplate PSO SITE was modified to accommodate entry of the new CHARGE\nLOCATION field (#1007).\n \n3. If a CHARGE LOCATION is not defined for a particular division, the \nsystem will loop through all divisions in the OUTPATIENT SITE file (#59) \nand will use the first CHARGE LOCATION it finds. When none of the\ndivisions have a CHARGE LOCATION defined, the prescription will not be \npassed to IB or the COTS billing system. This issue will be addressed in\nSystem (PFSS) project. PFSS patches are being released on various\npatch.\na subsequent phase of the PFSS project. Until that time, it is imperative\nthat CHARGE LOCATION are defined for each division.\n \nThe Integration Agreement (IA) #4732 was created to facilitate \nmodifications being made by IB for interfacility copay. It will be used \nin the background to return the pharmacist, person who last edited the \nprescription fill, and the value of the IB SERVICE/SECTION field (#1003) \nfrom the OUTPATIENT SITE file (#59).\n \nFor more information about the PFSS project, review the documentation \naccompanying this patch and refer to the following website: \nhttp://vista.domain.ext/billreplace/.\n \nThis Outpatient Pharmacy patch, PSO*7*201 provides the functionality\nneeded to support the PFSS project. Note that this patch depends on\npatches PSN*4*103 and PSS*1*92 to provide the new Charge Description\nMaster (CDM) functionality. The CDM provides Service Codes for each drug,\nschedules. Some patch functionality will not be active until a new PFSS\nsupply item, etc. to uniquely identify them to the new COTS billing\nsystem. This information is passed via IB Application Program Interface\n(API) calls, which is explained in the Technical Description.\n \nFunctional Description:\n=======================\n \nOutpatient Pharmacy was modified to check the status of the PFSS \nswitch. If the PFSS switch is not activated, the current Integrated \nBilling (IB) billing process will continue. If the PFSS switch is\nswitch is activated during final implementation. PFSS will initially be\nactivated, prescription and copay information will be passed to the new\nCOTS billing system for final copay assessments and billing via IB.\nAs is currently the case with IB, the exchange of information will take\nplace in the background with no user impact.\n \nUpon entering a new prescription order, copying, renewing, or editing \nan order that causes a new order to be created, a PFSS Account Reference\nwill be requested at finish from IB. This reference is used to uniquely\nidentify the prescription in the COTS billing system.\n \nimplemented at select pilot sites ONLY.\nAt prescription release, a unique charge identifier will be requested \nfrom IB, and it will serve to uniquely identify the fill in IB. Next, a\ncharge message will be sent to the COTS billing system via IB. This\nincludes the release of Consolidated Mail Outpatient Pharmacy (CMOP)\nprescriptions and prescriptions released by the Outpatient Pharmacy\nAutomation Interface (OPAI) functionality.\n \nFor return to stocks, and deletes that perform a return to stock, a charge\ncredit message will be sent. \n \n \nWhen Service Connection and/or Environmental Indicators are modified\nwithout a change in copay using the Reset Copay Status/Cancel Charges\n[PSOCP RESET COPAY STATUS] option, a charge update message will be sent. \nA charge credit message will be sent when copay charges are cancelled. \nWhen the fill is changed to copay, no message will be sent because this\nchange is considered to be for the future fills.\n \nNo messaging will take place for discontinued orders. When a \ndiscontinued order is reinstated, the previously obtained PFSS Account \nReference will be used.\nThe purpose of the PFSS project is to prepare the Veterans Health \n \nIn order to maintain the display of the "$" sign on the Medication \nProfile screen that indicates the prescription is eligible for copay, IB\nwill continue to be utilized for the copay eligibility assessment that is\nperformed at finish. Also, the Outpatient Pharmacy and IB copay\nevaluations performed at release for Service Connection, Environmental \nIndicators, Drug Enforcement Agency (DEA) special handling (supply items\nand investigational drugs), income exempt, and RX Patient Status checks\nhave not changed and will continue to be used. However, the final copay\nbilling determination will be performed by the COTS billing system, and\nInformation Systems and Technology Architecture (VistA) environment for\nthe final decision is based on the above information, interfacility copay\ninformation, and current IB billing rules. There will be no return\nmessaging from the COTS billing system to Outpatient Pharmacy.\n \nWhen Days Supply is edited on a released prescription, a charge update\nmessage will be sent to the COTS billing system, and it is understood that\nthe COTS billing system will pick up the latest charge update.\n \nLast, a new CHARGE LOCATION field (#1007) was added to the OUTPATIENT \nSITE file (#59). This field will be used by the COTS billing system \nthe implementation of a Commercial Off-The-Shelf (COTS) billing \nto group charges by division. Upon installation and before the PFSS \nswitch is turned on, the user will need to enter an Outpatient Pharmacy\ncharge location in the HOSPITAL LOCATION file (#44), and afterward define\nthis location in the new CHARGE LOCATION field (#1007) in the OUTPATIENT\nSITE file (#59). The Site Parameter Enter/Edit [PSO SITE PARAMETERS]\noption may be used to define the CHARGE LOCATION in the OUTPATIENT \nSITE file (#59). A charge location should be defined for each division in\nthe OUTPATIENT SITE file (#59). It is suggested that this field be\ncoordinated with the Medical Center's billing office and the activation of\nthe PFSS functionality. If at least one division has a CHARGE LOCATION\n\n
\nThis patch adds three new Outpatient Pharmacy Application Programming\nfrom the STATUS field (#100) from the PRESCRIPTION file (#52) is\nreturned. This API will invoke the FIELD^DID FileMan call and data will\nbe returned to the calling application as specified in the FIELD^DID\nFileMan documentation.\n \nThe third API (DIC) has three parameters and retrieves information \nspecific to the PRESCRIPTION file (#52). This API will invoke the ^DIC \nFileMan call and data will be returned to the calling application as \nspecified in the ^DIC FileMan documentation.\n \nInterfaces (APIs).\nFor more information, please see Forum DBIA 4858, or the Pharmacy\nRe-Engineering (PRE) API Manual.\n \nThis patch also corrects a problem with the PROF^PSO52API API. The first\nnode of data returned is meant to return both the PRESCRIPTION NUMBER and\nit's IEN. Currently, the IEN is not returned. This patch will correct\nthe problem.\n \nThis patch also corrects a problem with the PSO^PSO53 API. Currently \nthere is an undefined error when the API is run. This patch will correct \n \nthe problem and ensure the functionality of the PSO^PSO53 API call.\nThe first API (DIQ) requires five parameters to be passed in and data\nfrom the PRESCRIPTION file (#52) will be returned. This API will invoke\nthe EN^DIQ1 FileMan call and data will be returned to the calling\napplication as specified in the EN^DIQ1 FileMan documentation.\n \nThe second API (STATUS) requires three parameters to be passed in and data\n\n
\n1) HD149502 - Patient instructions from the first patient will incorrectly\ndisplay for the second patient when you are about to delete the patient\ninstructions for the second patient.\n \n2) HD147655 - Reinstate Issue:\nWhen you have 2 Clozapine drugs ordered, one as active and one as \ndiscontinued, you wish to reinstate the discontinued drug. At this point \nthe active drug will incorrectly become discontinued when you have \ndecided to "^" out of the application.\n\n
\nThis patch will produce a tally report in the form of a Mailman message \n \nmessage will be displayed that no corrections are needed. Each\nprescription completed is notated as such and reprinting the\nLOCKED^PSOCIDC9 report will show "completed" after each one.\n \n \nB. It was reported that an error occurred when the RPT^PSOCIDC9 report\nwas queued to a printer. This patch corrects the queuing of the report to\na printer. To generate the report of all prescriptions affected by the\nclean-up process, enter the following at the programmer's prompt:\n \nDuring installation of this patch, the user may select to run the tally \n >D RPT^PSOCIDC9\nimmediately or queue it to run at a later date and time. Should it be \nnecessary to stop the job for emergency or to know the status of the job,\na status and stop function is provided.\n \nTo stop the job, log into programmer's mode and type the D STOP^PSOTEXP1 \nat the command prompt. The following is an example:\n \n >D STOP^PSOTEXP1 \nfor all prescriptions with missing expiration dates and prescriptions that\n \n TALLY MISSING EXPIRATION DATES Job - set to STOP Soon\n \n Check Status to be sure it has stopped and is not running...\n (D STATUS^PSOTEXP1)\n \nTo check the status of the TALLY MISSING EXPIRATION DATES job, log \ninto programmer's mode and type D STATUS^PSOTEXP1 at the command prompt. \nThe following is an example:\n \nare past their expiration dates but have an active status. It also \n >D STATUS^PSOTEXP1 \n \n Currently processing:\n Date being processed > Dec 09, 2005\n RX # > 3011493\n \nTo restart the job, the patch must be re-installed.\n \nThe following is an example of the MailMan message that will be sent to\nmanagement and the user who installs the patch:\ncontains corrections for two remedy tickets.\n \nSubj: Outpatient Pharmacy PSO*7*250 TALLY MISSING EXPIRATION DATES\n[#144218]\n10/25/06@09:55 12 lines\nFrom: PSO*7*250 TALLY MISSING EXPIRATION DATES In 'IN' basket. Page 1 \n*New*\n------------------------------------------------------------------------\n \nThe TALLY MISSING EXPIRATION DATES job for the Outpatient Pharmacy\npatch (PSO*7*250) started OCT 25, 2006@09:55:22\n \nand completed OCT 25, 2006@09:55:27.\n \nExcel comma delimited data below, five headings, one data line\nNote that an institution of 999999999 denotes one was not found during \nrun.\n,,,,,,Total Active Rx's\n,Before v7 Install,Before v7 Install,After v7 Install,After v7 \nInstall,,With\n,Tot Active Rx's,Tot Inactive,Tot Active,Tot Inactive,Total \nRx's,Expiration\n1. The tally report will be sent to the person who installs the patch at \n,Missing Expired,Rx's Missing,Rx's Missing,Rx's Missing,Missing,Date of \nT-1\nInstitution,Date,Expired Date,Expired Date,Expired Date,Expired Date,Day\n500,1,4,1,2,8,340 \n \nEnter message action (in IN basket): Ignore//\n \n2. Remedy tickets 166505 and 166485 related to patch PSO*7*239:\n \nA. It was reported that for two sites the CIDC Activity Log Clean-up\nthe site and to management on FORUM via the MailMan utility. It will be\nprocess did not complete, no error was recorded, and no MailMan message\nwas received stating the job completed. It was found that the problem\nresulted from a prescription being locked by another process for an\nextended amount of time which resulted in the CIDC Clean-up process\nstopping. For consistency in the routines at all sites, the modification\nto correct this issue is being included in this patch. If your site \nreceived the MailMan message stating that the CIDC ACTIVITY LOGS \nCORRECTION job completed, no action should be taken. Otherwise after \ninstallation of this patch, run the CIDC Clean-up routine from\nprogrammer's mode to complete the process:\nused to determine if a national patch needs to be created for correcting\n \n >D ^PSOCIDC7\n \nThe clean-up routine will store any prescription that cannot be locked\nfor correction. The completion mailman message was modified to notate \nwhether such problems occurred. If there is not a notation stating \nprescriptions were locked, no further action is needed. Otherwise \nfrom the programmer's prompt type the following to print a report:\n \n >D LOCKED^PSOCIDC9\nthis issue.\n \nThe prescriptions on the locked prescription report may be individually \ncorrected manually by typing the following at the programmer's prompt:\n \n >D FIXONE^PSOCIDC9\n \nThe prescription number will be prompted, and a message stating that the\nactivity logs were corrected will be displayed. If the manual clean-up\nprocess still cannot lock the prescription in order to correct the\nactivity logs, a message stating such will be displayed. Otherwise, a\n\n
\nThis patch contains the first quarter enhancements for the Outpatient\n "Active/Susp". This change is also shared with the Application\n Program Interface (API) number 1281, provided to Computerized\n Patient Record System (CPRS) V. 1.0 to return "Active/Susp" instead\n of "Suspended".\n c. As a result of the installation of patch PSO*7*233, if a bad address\n is indicated, "BAD ADDRESS INDICATED-" followed by the reason\n ("UNDELIVERABLE", "HOMELESS", or "OTHER") was being printed. Once\n PSO*7*258 is installed, "**BAD ADDRESS INDICATED**" will be printed\n but will not be followed by the reason.\n \nPharmacy V. 7.0 package. It provides the following updates to\n2. The Medication Profile [PSO P] option will now print the last 4 digits\nof the SSN instead of the full 9 digits.\n \n3. When finishing a pending order using the Patient Prescription\nProcessing [PSO LM BACKDOOR ORDERS] option or using the Complete Orders\nfrom OERR [PSO LMOE FINISH] option, the following changes were\nmade:\n a. The provider comments are displayed in the first screen. When the\n following prompt is displayed:\n \nfunctionality:\n Copy Provider Comments into the Patient Instructions? No//\n \n the user has to scroll the screen up to know what the provider\n comments are. To avoid this problem, the provider comments are\n displayed along with this prompt.\n \n b. A problem was reported with the calculated quantity for the drug\n Clozapine. A patient safety incident (PSI-06-146) was entered. The\n solution provided is as follows:\n If the drug has possible dosages defined, a quantity can be\n \n calculated. If this quantity is less than the quantity placed in\n CPRS, the calculated quantity will be displayed. Otherwise, the\n quantity placed in CPRS will be displayed. If there are no possible\n dosages defined then a quantity cannot be calculated and the message\n "Unable to calculate the quantity, enter a quantity" is displayed to\n the user in the ListMan message bar as a warning of a possible\n quantity issue. For Clozapine orders, since Outpatient Pharmacy\n might change the days supply and quantity placed in CPRS, the days\n supply and quantity have been added to the existing refill message.\n Here is an example of an order placed in CPRS with a days supply\n1. The Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] option is\n of 60 and a quantity of 60 for a patient eligible for 28 days\n supply:\n \n (6) Issue Date: OCT 26,2006 (7) Fill Date: OCT 27,2006\n Patient Eligible for 28 Day Sup. or 14 Day with 1 refill or 7 Day\n with 3 refill\n (8) Days Supply: 28 (9) QTY (TAB): 28\n Provider ordered 0 refills, days supply of 60 and a qty of 60\n \n \nmodified to provide the following functionality:\n4. After the release of patch PSO*7*233 some issues were identified and\nare being corrected in this patch:\n a. If a hold reason of "8 (PER PATIENT REQUEST)" or "99 (OTHER--SEE\n COMMENTS)" was entered, some options were displaying reason "7 (BAD\n ADDRESS)" instead. This patch corrects that problem.\n \n b. The function call $$CHKRX^PSOBAI was missing a value on some quit\n statements. Although the affected lines of code should never be\n encountered, this patch corrects the problem.\n a. It will print only the last 4 digits of the Social Security Number\n (SSN) instead of the full 9 digits.\n b. The Prescription status of "Suspended" will now print as\n\n\n1. This patch provides new functionality for the Return Medication to\noption. Previously, you would have needed to go to the Return Medication\nto Stock [PSO RETURNED STOCK] option, return the medication to stock, then\ngo back to the Delete a Prescription [PSO RXDL] option to mark the\nprescription deleted.\n \n2. This patch fixes a problem of a possible incorrect FILL DATE default\nwhen entering a new prescription in the Patient Prescription Processing\n[PSO LM BACKDOOR ORDERS] option. If a past ISSUE DATE is entered, and\nbased on the other information entered for the prescription the\nEXPIRATION DATE calculates to a past date, then the FILL DATE default\nStock [PSO RETURNED STOCK] option and the Delete a Prescription [PSO RXDL]\ncould be incorrect.\n \n3. This patch makes changes to the data returned from Outpatient\nPharmacy detailed in DBIA 1878. Piece 16 of the zero node will contain the\npatient name. Also, the DFN input variable is now optional, but a null\nvalue must be passed in if the DFN is not defined.\n \n4. This patch makes a change to return Fill Date information to\nComputerized Patient Record System (CPRS) for display purposes.\n \noption. In the Return Medication to Stock [PSO RETURNED STOCK] option,\n5. This patch fixes an error that can occur when finishing an order\nentered through Computerized Patient Record System (CPRS), and that\norder was entered as a complex order with multiple sets of instructions.\n \n6. This patch fixes a problem of partial prescriptions not being released\nwhen that same prescription has a regular fill in suspense.\nprescriptions that have been filled and released at the Consolidated Mail\nOutpatient Pharmacy (CMOP) can now be returned to stock. In the Delete a\nPrescription [PSO RXDL] option, prescriptions that have been filled and\nreleased at the CMOP can now be marked for deletion. In addition, if a\nprescription has been released, you can now return that prescription to\nstock and mark it for deletion from the Delete a Prescription [PSO RXDL]\n\n
\nThis patch will correct certain scenarios where bottle labels printed \nthrough the OPAI External Dispense machines have a slightly different \ndrug name than when sent to CMOP or printed locally. Two new drug name \nfields, VA LABEL NAME & VA PRINT NAME, will be sent in the OPAI HL7 \nsegments to the External Dispense Machines.\n \nAlso will correct the Method of Pickup field in RXE.8 to send when all\nalpha characters.\n\n
\nThis patch will correct 5 problems.\nProblem 5: Prevent OPAI from updating a refill node via Auto-Release\n when the refill node was deleted.\n \nProblem 1: Users are able to delete released refills without returning to\n stock.\nProblem 2: A released refill may still allow for deletion.\nProblem 3: Error occurs when deleting suspended refills using menu option\n Change Suspense Date.\nProblem 4: The Return Medication to Stock option is not deleting the\n refill.\n\n
\nFor the Health Insurance Portability and Accountability Act (HIPAA)\n ...\n \n Select CPRS ORDERING INSTITUTION:\n RELATED INSTITUTION: ALBANY// \n NPI INSTITUTION: ALBANY// \n \n ...\n \nWhen this patch is installed, the information in this field will be \nautomatically populated through a post-install routine. The correct\nNational Provider Identifier (NPI) project, this patch will create and\ninstitution will be identified using the existing NCPDP NUMBER field\n(#1008) in the OUTPATIENT SITE file (#59), along with a list of\npre-defined NPI numbers, which should match to NPI numbers previously \nassigned to each institution by the KERNEL V. 8.0 patch XU*8*410.\n \nThe PSO SITE input template is being changed to include this new field.\nTherefore, the user will be able to manually add/edit/delete the NPI\nINSTITUTION field through the Site Parameter Enter/Edit [PSO SITE\nPARAMETERS] option.\n \npopulate the new NPI INSTITUTION field (#101) in the OUTPATIENT SITE file\n**************************************************************************\nNOTE: All active outpatient sites MUST have an NPI INSTITUTION assigned.\nThis is very important for sites currently performing third party\nelectronic billing (ePharmacy) because the NPI number will replace the \nprevious NCPDP (National Council for Prescription Drug Programs) number \nused to identify the dispensing pharmacy. \n**************************************************************************\n \nFor active sites that do not have an NPI INSTITUTION assigned after the\ninstallation of this patch, using the Site Parameter Enter/Edit [PSO SITE\n(#59). This patch will also change the Site Parameter Enter/Edi [PSO SITE\nPARAMETERS] option enter the correct institution for each site. In order\nto help you identify which sites have and which ones have not been \nassigned an NPI INSTITUTION, the post-install routine will generate a \nMailman message which will be sent to the user installing the patch as \nwell as all the holders of the PSORPH security key. Below is an example\nof the Mailman message:\n \nSubj: NPI INSTITUTION POPULATION [#93686] 08/01/06@16:16 20 lines\nFrom: PATCH PSO*7*254 In 'IN' basket. Page 1 *New*\n-----------------------------------------------------------------------\nPARAMETERS] option to allow the user to edit this new field as shown\nPSO*7*254 POST-INSTALL - POPULATES NPI INSTITUTION FIELD (#101)\n IN THE OUTPATIENT SITE FILE (#59)\n \nPlease, validate that the NPI INSTITUTION assignment below is correct for \neach active DIVISION. If not, please use the Site Parameter Enter/Edit [PSO\nSITE PARAMETERS] option and assign the correct NPI INSTITUTION.\n \n------------------------------------------------------------------------\nDIVISION(SITE#) NPI# NPI INSTITUTION\n------------------------------------------------------------------------\nbelow:\nALBANY(500) 9999854880 ALBANY\nLEAVENWORTH(686) 9999813538 LEAVENWORTH, KS\nSIDNEY CLINIC(442GC) NO SITE# OR NCPDP# FOUND FOR DIVISION\nTROY(514) NO NPI# FOUND FOR THIS DIVISION\nGREELEY CLINIC(442GD) 9999591232 GREELEY CBOC\n \nTOTAL: 5 Division(s).\n \n NAME: ALBANY// \n \n\n
\nThis patch includes two new routines, PSO52EX and PSO52B. It also\n^TMP global. Once these values are set by the user, EXTRACT will then\nextract all original fill information. If a selected patient also has\nrefill or partial fill information on record, that information will also\nbe returned and subscripted accordingly. The output is stored on the ^TMP\nglobal. The second API is named REF. REF also requires the same three\nparameters: SDATE, EDATE, and LIST. It will retrieve information stored\non the "AD" cross reference in the PRESCRIPTION file (#52) and return it\nto the ^TMP global. Refer to Forum DBIA 4902 for complete information.\n \nPSO52B is a new routine that contains a number of subroutines that have \nenhances functionality and resolves two problems in PSO52API.\nbeen moved from PSO52API. This was done to ensure that PSO52API will \ncontinue to be within Programming Standards and Conventions (SAC) routine \nsize limits. PSO52B also enhances the RX^PSO52API component by retrieving\nInternational Classification of Diseases (ICD) information from the\nPRESCRIPTION file (#52). The user now has the option to pass in "ICD" in\nthe NODE parameter of the RX^PSO52API call and retrieve information\nspecific to the patient(s) concerning their ICD. Refer to the Application\nProgrammer Interface (API) manual for further instruction on the use of\nthis API.\n \n \nThis patch also corrects two other issues within PSO52API. Currently if\nthe user passes in only an end date, the API will error. This patch will\ncorrect this problem. Also, when "O" is passed in the NODE parameter to\nretrieve the ORDERABLE ITEM field (#39.2) from the PRESCRIPTION file\n(#52), the code will now return data as stated in the API manual without\nrepresenting the field number in its ^TMP global subscript.\nPSO52EX is a new routine containing two Application Programmer Interfaces\n(APIs). The first API is named EXTRACT. EXTRACT retrieves data from the\n"AL" and "AM" cross references within the PRESCRIPTION file (#52). \nEXTRACT requires three parameters: SDATE, EDATE, and LIST. SDATE is the\nstart date to retrieve data from. EDATE is the end date to retrieve data\nfrom. LIST is the name that is used to subscript the returned data into a\n\n
\nRemote Data Interoperability (RDI) functionality includes receiving data\n \n \nThis patch contains the following changes for RDI order checking:\n \n1. Prescriptions with a status of "DELETED" in the STATUS field (#100) in\nthe PRESCRIPTION file (#52) from a remote facility should not be included\nin order checks. This patch filters out DELETED remote prescriptions.\n \n2. Some older prescriptions do not have an expiration date in the \nEXPIRATION DATE field (#26) of the PRESCRIPTION file (#52). This patch\nfrom the Health Data Repository (HDR) in order to perform order checking\nrestricts prescriptions with a missing expiration date from being used in\nremote order checks unless the ISSUE DATE (#1) field of the PRESCRIPTION\nfile (#52) is within the past year.\n \n3. Drugs not matched to the National Drug file were not performing remote \norder checks. These drugs could have a drug class defined. This patch \nadds the remote order check for drug class when orders are placed for \nlocally defined drugs.\n \n4. When Adverse Reaction Tracking (ART) patch GMRA*4*26 is installed at a\nagainst outpatient prescription and allergy data from remote VA or\nsite, this patch adds the display of LOCAL, REMOTE SITE(S), or LOCAL AND\nREMOTE SITE(S) to allergy order checks to indicate whether the allergy\nentry originated at the local site or it came from a remote site. For\nbackdoor outpatient pharmacy, currently only the drug class code and not\nthe drug class name is displayed for an allergy drug class order check.\nThis patch adds the display of the class name.\n \nExample:\n \nA Drug-Allergy Reaction exists for this medication and/or class!\nDepartment of Defense (DoD) facilities.\n \nDrug: AMOXICILLIN 250MG CAP\nDrug Class: AM110 PENICILLIN-G RELATED PENICILLINS (LOCAL)\n \n \n5. When the VUID field (#99.99) of the VA PRODUCT file (#50.68) of a\nremote prescription is inactive, every order being placed incorrectly\ndisplayed a duplicate drug order check. This patch corrects that problem.\n \n6. Remote order checking against remote discontinued or expired outpatient\n \nprescriptions is changed to perform the order check if the remote \nprescription was expired or discontinued in the last 30 days instead of \nwithin the last 120 days.\n \n7. During testing of RDI, a problem was discovered with the order checks\ninvolving remote allergy classes. Not all of the remote allergies were\nbeing retrieved from the HDR. A change was made to use a different\nApplication Program Interface (API) to the allergy package that does \nretrieve the remote data.\n \nWhen RDI is turned on (by the Computerized Patient Record System (CPRS)\n8. An issue with too many false positive order checks was discovered when \ndoing allergy order checks on certain drug classes. Analgesics, as a\nclass, were performing order checks across all members. For example: class\nCN101 was generating an order check for class CN102. This patch corrects\nthis problem by ensuring that allergy Analgesic class order checks only\nmatch against the specific 5-character class if the class begins with \n"CN10".\n \n9. One feature of RDI is the notification to the user when processing \norders that only local data is being used if the remote data is \npatch OR*3*238), the RDI order checking checks the current drug being \nunavailable. Several sites reported issues with this mechanism. This \npatch corrects this problem by performing the check for remote data \navailability upon entering the patient's chart, rather than on each order.\n \n10. The list of remote allergies is added to allergy/adverse reaction \nportion of the Medication Profile. If a patient has the same allergy\ninformation from several remote sites, it will only be listed once.\nordered for duplicate drugs, duplicate drug classes, drug-drug\ninteractions, and drug allergies.\n\n
\n This patch contains the FY 2007 Quarter 2 Outpatient Pharmacy V. 7.0\n \n profile screen.\n g. While printing original labels (not reprint of the signature log), \n if all of the fills have a routing of mail, the signature log will\n not be printed.\n h. The line "Relationship_________________ Counseled? _____" is changed\n to "Relation_____ Counseling Refused__ Accepted__".\n \n \n5. When a fill is released, if the BAI is no longer set or there is an \nactive temporary address, the "B" is removed from the status column of \nIf you are using automated dispensing equipment that relies on \nthe patient profile. (This is removed by making an additional entry in \nthe label log. The "B" comes from the "last" entry having a bad address \ncondition at the time the label printed).\n \n \n \nTo address E3R 19820, the following code changes are included in this \npatch:\n \n1. Add the capability to tie a ScripTalk printer to regular Pharmacy\nthe data stream sent to the laser labels port, you have 2 options:\nlabel printer(s) to control where the ScripTalk labels print for\nmulti-divisional sites. The new SCRIPTALK PRINT DEVICE MAPPING multiple\n(#47) in PHARMACY SYSTEM file (#59.7) has been created to store this\ninformation in Pharmacy Data Management patch PSS*1*122. The multiple\ncontains PRINTER TO BE MAPPED field (#.01) and SCRIPTALK DEVICE field\n(#.02).\n \nThe added functionality works in conjunction with the existing ScripTalk \ndivisional functionality, so a divisional ScripTalk device must be\ndefined. If no mapping is defined in the new fields, ScripTalk labels\n 1. Implement the Outpatient Automation Interface (OPAI) (available with\nwill continue to print on the printer defined for the division. If\na pharmacy printer is mapped to a ScripTalk printer, the ScripTalk label\nwill automatically be printed on the mapped ScripTalk printer.\n \n \n2. Modify the ScripTalk Device Definition Enter/Edit [PSO SCRIPTALK\nDEVICE DEF'N] option to allow definition of printer mapping for \nScripTalk devices. The user will be prompted to define the ScripTalk \nprinter by division or by printer mapping. After selecting D for \ndivision, the divisional definition has not changed. After selecting \n released patch PSO*7*156) or \nP for printer mapping, the user will be prompted "LABEL PRINTER TO BE\nMAPPED". The device entered into this field corresponds to the label\nprinter selected during Pharmacy login and/or the printer selected during\nprint from suspense functions. Next, "SCRIPTALK DEVICE" will be prompted,\nand this field should contain the ScripTalk printer to be mapped to the\nregular label printer.\n \n \nMISCELLANEOUS ENHANCEMENTS:\n---------------------------\n 2. Contact your vendor to make adjustments based on the new data stream.\n1. A new field FINISH DATE/TIME field (#38.3) is added to the\nPRESCRIPTION file (#52).\n \n2. When using the Print from Suspense File [PSO PNDLBL] option, if the\nrouting is not WINDOW and the BAD ADDRESS INDICATOR (#.121) field of the\nPATIENT file (#2) is set (value of 1=UNDELIVERABLE, 2=HOMELESS, 3=OTHER)\nand the patient does not have an active temporary address, the\nprescription fill will not be sent to automated filling equipment and/or\nto the label printer. Also, if the fill's routing is mail and the \npatient's MAIL field (#.03) in the PHARMACY PATIENT file (#55) is set to\n \n"DO NOT MAIL" and the current date is before the MAIL STATUS EXPIRATION\nDATE field (#.05) in the PHARMACY PATIENT file (#55), the label will not\nprint and the fill will not be sent to the automated filling equipment.\n \nThe first time a prescription is not sent/label printed, a MailMan message\nwill be generated to the user who queued the print from suspense and the\nmembers of the PSO EXTERNAL DISPENSE ALERTS mail group. An entry will also\nbe set in the PRESCRIPTION file (#52) activity log.\n \nExample activity log entry:\n \n---------------------------\nActivity Log:\n# Date Reason Rx Ref Initiator Of Activity\n=====================================================================\n1 02/19/07 SUSPENSE ORIGINAL OPPHARMACIST,ONE\nComments: RX not printed from suspense due to BAD ADDRESS INDICATOR\n \n- or -\nComments: RX not printed from suspense due to DO NOT MAIL\n \nOutpatient Pharmacy Automation Interface (OPAI) enhancements: \nExample MailMan message:\n------------------------\nSubj: 500 BAD ADDRESS SUSPENSE NOT PRINTED [#169828] 02/26/07@07:30 11\nlines\nFrom: OUTPATIENT PHARMACY PACKAGE In 'IN' basket. Page 1\n--------------------------------------------------------------------------\n-----\nThe following prescriptions with a routing of mail were not printed/sent \nto\nexternal interface due to the BAD ADDRESS INDICATOR being set and no \n-------------------------------------------------------------\nactive\ntemporary address or patient has an active MAIL status of DO NOT MAIL:\n \nOPPATIENT,ONE 000001234 (BAD ADDRESS INDICATOR)\n 100002608 (1) A AND Z OINTMENT\n 100002609 (0) ASPIRIN 325MG TABS\n \nOPPATIENT,FOUR 000004321 (DO NOT MAIL)\n 100002654A (0) BACITRACIN OINTMENT 1OZ\n \nenhancements. \n1. Modified to use the new commercial warning label source to send the\n \n3. Modify the report from the Bad Address Suspended List [PSO BAI \nSUSPENDED] option to allow printing by more than one division and also \ninclude prescriptions suspended for Consolidated Mail Outpatient Pharmacy \n(CMOP). This report was also changed to not prompt for a start date.\n \nExample:\n--------\nSelect OPTION NAME: PSO BAI SUSPENDED Bad Address Suspended List\nBad Address Suspended List\nwarning label text to the automated filling equipment. The OPAI WARNING\n \nThis option shows unprinted suspended prescriptions for patients who have \nthe\nBAD ADDRESS INDICATOR set in the PATIENT file and no active temporary \naddress.\n \n \nEnding suspense date: T+3 (MAR 01, 2007)\nOutpatient Pharmacy software - Version 7.0\n \nLABEL SOURCE field (#16.2) in the PHARMACY SYSTEM file (#59.7) must be set\nDivision: EXT 500 \n \n You are logged on under the EXT division.\n \nSelect LABEL PRINTER: HOME// GENERIC INCOMING TELNET\n \nOK to assume label alignment is correct? YES// \n \nBingo Board Display: OUTPATIENT// \n \nto "N" for "New" to send the warning labels from the new commercial data\n You are logged in under the EXT division.\n \nPrint only those Rx's suspended for this division? Yes// NO\nDEVICE: HOME// GENERIC INCOMING TELNET\n \n \nSuspense bad address report - division = ALL PAGE: 1\nfor suspense dates through MAR 01, 2007\n--------------------------------------------------------------------------\n \nsource to OPAI. It can be set by using the Pharmacy System Parameters Edit\nOPPATIENT,TEN (00-0187) \nMAR 01, 2007 Rx#: 301054 CIMETIDINE 200MG TAB\nMAR 01, 2007 Rx#: 301055 COAL TAR 5% GEL 3 OZ TUBE\n \nOPPATIENT,FIVE (00-0773) \nFEB 27, 2007 Rx#: 100002655 BACITRACIN OINTMENT 1OZ\n \nEnd of Report.\nPress Return to continue: \n \n[PSS SYS EDIT] option.\n4. As per the request of Computerized Patient Record System (CPRS)\npackage the following were added to the Applications Program Interface\n(API) PSOHCSUM:\n a. PLACER ORDER # field (#39.3) of the PRESCRIPTION file (#52).\n b. Letter "R" when the original fill is returned to stock.\nFor more details please see the IA (Integration Agreement) #330.\n Example:\n \nSelect OPTION NAME: PSS SYS EDIT Pharmacy System Parameters Edit\nPharmacy System Parameters Edit\n \n \nPMIS PRINTER: L8150$PRT// \nPMIS LANGUAGE: English// \nWARNING LABEL SOURCE: NEW// \nCMOP WARNING LABEL SOURCE: NEW//\nOPAI WARNING LABEL SOURCE: ?\n Enter "N" for NEW to use commercial data source for OPAI warning \nlabels.\n Choose from: \n N NEW\n \nOPAI WARNING LABEL SOURCE: N NEW\n \n a. The warning text is sent as one record per warning.\n b. The text is sent in English or Spanish depending on the patient's\n other language settings. \n c. If the DEA, SPECIAL HDLG field (#3) in the DRUG file (#50) begins\n with numbers 1,2,3,4, or 5, the NO TRANSFER warning text from the RX\n CONSULT file (#54) entry number 20 is automatically sent as one of\n the first 5 warnings when the OPAI WARNING LABEL SOURCE is set to \n "New".\n***** NOTE TO SITES USING AUTOMATED FILLING EQUIPMENT *****\n \n \n2. If the BAD ADDRESS INDICATOR (BAI) field (#.121) of the PATIENT file\n(#2) is set and the routing is WINDOW, the text "VAB" concatenated with\nthe BAI code is sent in the Address field of the PID segment of the HL7\nmessage to the filling equipment.\n \nHere are some examples of this field:\n \nWhen the permanent address is active:\nPlease ensure that your vendor is aware of the changes being made by this \nPADD-1~PADD-2~SPRING~TX~77379~~P~PADD-3~201^~~""~""~~~N|""|||||||\n|\n \nWhen the temporary address is active:\nPADD-1~PADD-2~SPRING~TX~77379~~P~PADD-3~201^~~""~""~~~N^TADD-1~TADD-2 \nTADD-3~PLANO~TX~12345~~C~~""~~~\n^HL(772,10388,"IN",2,0)=20070223&""|""|||||||||\n \nWhen the address is flagged as BAI:\nPADD-1~PADD-2~SPRING~TX~77379~~VAB1~PADD-3~201^~~""~""~~~N|""||||||\npatch. There are changes (described below) that affect both the HEALTH \n|||\n \n"VAB1" - indicates Bad Address Indicator and 1 is for UNDELIVERABLE (2 for\nHOMELESS, 3 for OTHER)\n \n \nLaser Label enhancements:\n-------------------------\n1. Print the last 4 digits of the Social Security Number (SSN) instead of\nthe last 6 digits.\nLEVEL SEVEN (HL7) messages (content of fields only - no new fields are\n \n2. Change the name on the mailing label back to Last name,First name\nformat.\n \n3. On the Pharmacy Fill Card portion of the label, replace the text \n"Mfr ___________________" with:\n a. NDC/MFR_______________ for non-ePharmacy sites\n b. NDC nnnnn-nnnn-nn for ePharmacy sites \n \n4. Signature log enhancements:\nadded) and the laser label stream.\n a. Print current date at top\n b. Do not print user name (if more than 1 prescription was included to\n be signed, the user name could be different for each one).\n c. Correct the spacing and continuation paging issues if one or more \n of the prescriptions has been discontinued before printing the \n signature log.\n d. Add a barcode to enable scanning to remove the patient's name from \n the Bingo Board.\n e. Add as much of the drug name as will fit on the label.\n f. Add hidden action "RS" for Reprint Signature log to the prescription\n\n
\nThis patch will correct the following issues.\nthe EDIT PROVIDER option does not allow editing of SERVICE/SECTION or \nPERSON CLASS for Fee Basis providers.\n \nProblem: HD158732\n------------------\nThere is a discrepancy between fields in EDIT PROVIDER and VIEW PROVIDER.\n \nProblem: HD15266\n------------------\nAn undefined error occurs when a single character is entered in the \nPSO RESET COPAY option.\n \nProblem: HD151887\n------------------\n\n
\nThis patch is part of the third quarter enhancements release for\nany functional changes.\n \nFor more information on the addition of the thirteen new data fields,\nplease refer to Appendix D of the Outpatient Pharmacy V. 7.0 Technical\nManual / Security Guide that is being updated with this patch.\n \nThis patch also corrects the problem of a VDEF message not being sent to\nthe HDR when a refill is deleted from a prescription as a result of the\nrefill being returned to stock.\n \nthe Outpatient Pharmacy V. 7.0 package.\n**** VERY IMPORTANT ****\n \nYou must suspend the VDEF Request Queue before installing this patch and\nthen re-enable it after installation of the patch. Keep in mind that the\nsuspension of the VDEF Request Queue will not prevent any new requests in\nOutpatient Pharmacy VDEF Domain application from being added to the VDEF\nRequest Queue, it will only delay the building of these VDEF HL7 messages\nuntil the VDEF Request Queue is enabled again. The steps for doing that\nare outlined in the Installation Instructions section.\n \n \n \nMISCELLANEOUS FIXES:\n--------------------\n1. The hidden action "RS" for Reprint Signature log that was sent in\npatch PSO*7*200, was overwriting the action "OTH" for Other OP Actions,\nmaking the OTH action unavailable. The post-install routine PSOP261\nincluded in this patch (PSO*7*261) fixes this.\n \n2. An undefined error was identified by a site that went live with Remote\nData Interoperability (RDI) patches. A common variable was being killed by\nAs per the Health Data Repository (HDR) request, thirteen new data fields\nanother package. The fix is to save the value of the variable before\nmaking the call to retrieve remote allergy data and to restore the\nvariable to the saved value once control is returned to the calling\nroutine.\nwere added to the current Outpatient Pharmacy Vista Data Extraction\nFramework (VDEF) HEALTH LEVEL SEVEN (HL7) message that sends prescription\ninformation to the HDR.\n \nThis patch affects the background HL7 processing only; users will not see\n\n
\nPSI-07-029 patch fix\n \nCorrects undefined filing errors for NON-VA Meds when an embedded\nsemi-colon is entered in either the Dosag field or the Schedule field in\nCPRS as free form text.\n\n
\nCancel date\nScriptalk issue\nFileman API\n\n
\n1. This patch contains new DEA requirements for Clozapine dispensing. The\nwill be one test within the CBC panel.\n \nAfter the installation of this patch the Drug Enter/Edit [PSS DRUG\nENTER/EDIT] option in the Pharmacy Data Management (PDM) package should be\nused to add this second test to the drug(s) that are identified as being\nused for Clozapine/Clozaril dispensing. For existing entries in the DRUG\nfile (#50) the first test WBC should already be defined from previous setup\nof identifying drugs for Clozapine/Clozaril dispensing. For new drugs added\nfor Clozapine/Clozaril dispensing both the WBC and ANC test must be\nidentified. If this second test is not added the user will get a message\nnew requirements are that there will be two tests instead of one required\nwhen trying to dispense a Clozapine Rx, "Invalid Number of Tests (1) entered.\n \n Cannot dispense Clozapine Prescription. You must have TWO test identified\nfor this drug. Rx Deleted."\n \nThough this patch allows the dispensing of 14-day Clozapine/Clozaril Rxs,\nthe eligibility of the patient is determined by the Mental Health package.\nThere is no setup required by Outpatient Pharmacy. If you have a\nquestion about a patient's eligibility, please contact The National\nClozapine Center.\nfor Clozapine dispensing. The two tests are White Blood Count (WBC) and\n \nThese two patches are required, Mental Health patch YS*5.01*47, and PDM\npatch PSS*1*19.\n \n2. This patch corrects a problem where Rx's with controlled substances\nare being given a maximum expiration date of one year instead on six months.\n \n3. This patch corrects a problem reported in MON-0199-51550. The problem\nis that when using the Speed Refill action if the Rx's selected are all\nexpired no message is given to the user that the Rx's selected are expired.\nAbsolute Neutrophil Count (ANC). The ANC test at some sites is called the,\n \n \n%Neutrophil, %Neut, %Gran or something to this effect. The exact name of\nthis test should be coordinated with Lab Service. The %Neutrophil results\nused in this order check are the result returned by the automated lab\ninstruments and not the manual entry. The specimen collection sample must be\nidentified as well, in most cases that will be blood. The %Neutrophil test\n\n
\nThis patch enhances the functionality of PSODI, PSO59, and PSO52EX.\n PSOFLAGS: CONTROLS THE PROCESSING OF DATA RETURNED [OPTIONAL] \n PSOWORD: RETURN OF WORD PROCESSING FIELDS [REQUIRED only with word \n processing fields]\n \nIf a file access error is encountered, the calling application will have\n"0^FILE ACCESS ERROR" returned. If a FileMan error has occurred, the\ncalling application will have "0^FILEMAN UNABLE TO PROCESS REQUEST"\nreturned. A successful data retrieval will return in the format "1^(FIELD\nDATA)". When retrieving data from a word processing field, an array name\nmust be passed in to PSOWORD. Once the word processing field is returned,\n \nit will then populate an array as defined by PSOWORD and the calling\napplication will have "1^(PSOWORD)" returned. If there is no data in the\nWord Processing field, the calling application will have "1^" returned,\nand the array defined by PSOWORD will be empty.\n \nPlease see the VA FileMan Programmer Manual V. 22.0 for $$GET1^DIQ input\ndefinitions and DBIA 4858 for further description.\n \nPSO59 retrieves data from the OUTPATIENT SITE file (#59) and has three \nparameters: PSOIEN (optional), PSOTXT (optional), and LIST (required). \nPSODI contains a new Application Programmer Interface (API) named GET1.\nWhile PSOIEN and PSOTXT are both labeled as optional, PSO59 requires that \neither parameter be passed in or no data will be returned. PSOIEN is the \ninternal entry number (IEN) of a site, PSOTXT is a free text entry that \nworks as a search parameter, and LIST is the subscript name used in the \n^TMP global. The new functionality now allows the user to pass in "??" to \nretrieve all divisions in the file and subscripts them accordingly. If \nboth an IEN and "??" are passed in, PSO59 will ignore the "??" and return\ndata specific to the IEN. \n \nPlease refer to DBIA 4827 for further description on PSO59.\nThis API will invoke the $$GET1^DIQ FileMan Database Server (DBS) call and\n \nPSO52EX contains a new Application Programmer Interface (API) named \nARXREF. This API is to be used as an extrinsic function call and requires\nthree parameters: PSODATE, PSOIEN, and PSOFILL. PSODATE is the RELEASED \nDATE/TIME field (#31) and PSOIEN is the internal entry number from the \nPRESCRIPTION file (#52). PSOFILL is the fill number of prescription (0 \nfor Original Fill, 1 for Refill #1, 2 for Refill #2, etc.). The user can\nset a local variable equal to the return value of ARXREF. If the return\nvalue equals:\n \nis to be used as an extrinsic function. GET1 has five parameters:\n 0 (zero) = Data does not exist in the "AR" cross reference, indicating\n the fill was not dispensed from the Consolidated Mail Outpatient\n Pharmacy (CMOP).\n \n 1 (one) = Data does exist in the "AR" cross reference, indicating the\n fill was dispensed from the CMOP.\n \nPlease refer to DBIA 4902 for further description on PSO52EX.\n \n PSOFILE: FILE OR SUBFILE NUMBER TO RETRIEVE DATA FROM [REQUIRED]\n PSOIEN: IEN TO RETRIEVE DATA FROM [REQUIRED] \n PSOFIELD: FIELD TO RETRIEVE DATA FROM [REQUIRED] \n\n
\nThis patch is part of the third quarter enhancements release for the\n on a global node setting of ^DD("DILOCKTM")=3.\n \nExample 1 - Patient Prescription Processing:\nSelect Action: Next Screen// NO New Order\n \nEligibility: SERVICE CONNECTED 50% to 100% SC%: 60\nRX PATIENT STATUS: AUTH ABS -96//\n \nExample 2 - Complete Orders from OERR:\nSelect By: (PA/RT/PR/CL/E): PATIENT// ROUTE\nRoute: (W/M/C/E): WINDOW// MAIL\n \n \n \n \n OPPATIENT,ONE (666-00-0777)\n No Allergy Assessment!\n \nEligibility: NSC\nRX PATIENT STATUS: OPT NSC//\n \n6. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n In order to avoid the lock issue in Outpatient Pharmacy, this patch\n option, if the Patient Update "PU" action is chosen and the PATIENT\n STATUS is changed to a new one, when returning to the option and\n choosing "NO" for New Order, the default PATIENT STATUS displayed is\n the one before the PU change was done. This patch makes a correction\n to refresh the PATIENT STATUS before displaying the default.\n \n7. When selecting a patient in the Patient Prescription Processing [PSO\n LM BACKDOOR ORDERS] option or the Complete Orders from OERR [PSO LMOE\n FINISH] option, if Remote Data Interoperability (RDI) is turned on, a\n check has been added to check for the ability to access remote data.\n modifies all routines that currently use a lock timeout value of less\n If a problem has been detected with accessing remote data, the patient\n selection will display "Remote data not available - Only local order\n checks processed." once per patient rather than for each individual\n order.\n \n8. If the MAIL STATUS EXPIRATION DATE field (#.05) in the PHARMACY PATIENT\n file (#55) is less than today, the MAIL field (#.03) displays on\n the patient profile as if it is still active. This patch adds the\n display of the MAIL STATUS EXPIRATION DATE field next to the MAIL\n field on the patient profile for MAIL settings of Do Not Mail, Local -\n than 3 seconds to check for the node ^DD("DILOCKTM") and to use the\n Regular Mail and Local - Certified Mail if the mail status is expired.\n \n9. Following the installation of patch PSO*7*200, a site noticed that 6\n digits of the social security number were printing when using the new\n hidden "RS" action to reprint the signature log. This patch changes it\n to 4 digits to match the rest of the labels.\n \n10. In patch PSO*7*200, functionality was provided to use the new\n commercial warning label to send prescriptions to the automated\n filling equipment. One site reported a problem when using the old\n value defined there, otherwise the lock timeout value is set to a\n warning labels, that the HEALTH LEVEL SEVEN (HL7) message sent to\n Optifill was causing an error. This happens when the label text length\n is greater than 512 characters. To prevent this error, this patch\n ensures that the label text length sent does not exceed 245 \n characters. If the label text length exceeds 245 characters, then the\n additional text will be parsed and sent in additional messages.\n default value of 3 seconds.\n \n2. PSI-06-186 - Changing dispense drug and SIG\n When finishing a new order using the Patient Prescription Processing\nOutpatient Pharmacy V. 7.0 package.\n [PSO LM BACKDOOR ORDERS] option, and answering "NO" to the prompt\n "Is this correct? YES//", the software allows the option to edit\n the dispense drug. It allows you to select any active drug from the\n DRUG file (#50) and accept the order even though the entered SIG is\n incorrect. This patch will not list all the active drugs for selection\n during dispense drug edit, but will list only those drugs that are tied\n to that orderable item in the DRUG file (#50).\n \n When the dispense drug is changed the software prompts "Do You want to\n Edit the SIG? NO//." To read the current SIG you may have to scroll\n \n the screen up. This patch will now display the current SIG along with\n the prompt "Do You want to Edit the SIG? YES//."\n \n A similar modification is also done in this patch for editing an\n existing prescription and the dispense drug is changed, to display the\n current SIG along with the prompt "Do You want to Edit the SIG? YES//."\n \n When finishing a pending order through the backdoor, the software\n allows the option to edit the orderable item and select a different\n dispense drug, but does not prompt you to change the SIG. This can\n1. With the deployment of Cache version 5, it was discovered that the\n lead to incorrect SIG. This patch will now prompt the question\n "Do You want to Edit the SIG? YES//."\n \n3. This patch adds SERVICE REJECT to the current list of selection for\n the Nature of Order prompt.\n Example:\n \n Nature of Order: WRITTEN// ?\n Choose from:\n 1 WRITTEN W\n short lock timeout values could generate a lock failure. Patch\n 2 VERBAL V\n 3 TELEPHONED P\n 4 SERVICE CORRECTION S\n 5 POLICY I\n 6 DUPLICATE D\n 12 SERVICE REJECT R\n \n4. PSI-06-184 - Enhancements for No Allergy Assessment\n The following changes are included to make the pharmacist aware/act on\n prescriptions if they're being entered/finished for a patient with no\n DI*22*147, which has already been released, provided a solution to\n allergy assessment:\n a. Within the profile information, display "No Allergy Assessment"\n next to the allergy header (like "NKA" currently shows)\n \n b. At the same spot where checking for bad address, add a check for\n no allergy assessment and provide a message to the user. (When the\n user continues on, he could choose EA to enter allergy information,\n stop with that patient, or continue on with ordering or finishing).\n \n c. On the profile header, on the right side of the line with patient\n resolve this issue and future lock issues.\n name where <A> currently shows in reverse video if the patient has\n any allergy/adverse reaction information on file, show <NO ALLERGY\n ASSESSMENT> in reverse video if no assessment has been done.\n \n d. If the pharmacist proceeds with drug entry for a patient with no\n allergy assessment, prompt to intervene just as if there had been an\n allergy reaction and treat this like a critical interaction. (i.e.\n require them to choose to continue processing and if so, prompt for\n an intervention.\n \n \n Note: When flagging is available in backdoor Outpatient Pharmacy for\n pending orders, procedurally sites can choose to flag pending orders\n for patients awaiting an allergy assessment.\n \n5. The patient's eligibility will be displayed before prompting for\n patient status when finishing prescriptions or entering new orders (to\n ensure that the proper entry from the RX PATIENT STATUS file (#53) is\n being selected. This is stored in the PATIENT STATUS field (#3) of the\n PHARMACY PATIENT file (#55)):\n a. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n This patch instituted a new default lock timeout of three seconds based\n option, redisplay the eligibility just before prompting for patient\n status.\n \n b. In the Complete Orders from OERR [PSO LMOE FINISH] option, after\n displaying patient name, display eligibility and prompt for patient\n status.\n \n c. In both options, use RX PATIENT STATUS: for the prompt instead of\n PATIENT STATUS:\n \n\n\nThis patch enhances the functionality of PSO59.\nINSTITUTION field (#101) and NCPDP NUMBER field (#1008) from the \nOUTPATIENT SITE file (#59).\n \nPlease refer to DBIA 4827 for further description on PSO59.\n \nPSO59 retrieves data from the OUTPATIENT SITE file (#59) and has three \nparameters: PSOIEN (optional), PSOTXT (optional), and LIST (required). \nWhile PSOIEN and PSOTXT are both labeled as optional, PSO59 requires that \neither parameter be passed in or no data will be returned. PSOIEN is the \ninternal entry number (IEN) of a site, PSOTXT is a free text entry that \nworks as a search parameter, and LIST is the subscript name used in the \n^TMP global. This routine will now return field values for the NPI \n\n
\nIn backdoor pharmacy, when placing a new order, renewing an existing\nCV question will remain the same, i.e., the default answer will be set to\neither 'Yes' or 'No' depending on what is being marked by the provider.\nOrder, or copying an order to a new order, if a patient is eligible for\nCOMBAT VET (CV), the default answer to the prompt "Was treatment related\nto Combat" is currently presented as Null. This patch will change the\ndefault answer, currently Null, to 'Yes'.\n \nNote:\n \nWhen finishing a pending order the current functionality related to the\n\n
\nThe FY07 Q4 Enhancement Release includes the following PSO enhancements:\n to holders of the PSOAUTRF key with details of Not-Filled refills,\n Example:\n \n Patient Information Aug 10, 2007@10:04:09 Page: 1 of 2\n OPPATIENT,SEVEN\n <A>\n PID: 000-12-3456 Ht(cm): _______ (______)\n DOB: DEC 1,1950 (56) Wt(kg): _______ (______)\n SEX: MALE\n \n Eligibility: NSC, VA PENSION\n unsuccessful runs, count of refills processed successfully, etc.\n RX PATIENT STATUS: OPT NSC\n \n Disabilities: POST-TRAUMATIC STRESS DISORDER-100% (SC),\n \n 2222 CENTRAL AVE\n HOME PHONE:\n ALBANY CELL PHONE:\n WORK PHONE:\n Prescription Mail Delivery: Regular Mail\n Cannot use safety caps.\n \n \n Allergies\n Verified: PENICILLIN,\n + Enter ?? for more actions\n EA Enter/Edit Allergy/ADR Data PU Patient Record Update\n DD Detailed Allergy/ADR List EX Exit Patient List\n Select Action: Next Screen//\n \n b. Change the existing 'PHONE:' label to 'HOME PHONE:', and also display\n the PHONE NUMBER [CELLULAR] field (#.134) and the PHONE NUMBER [WORK]\n Note: The new PSOAUTRF security key is transported in this patch and\n field (#.132) of the PATIENT file (#2). The work and cell phone\n fields can be maintained via the PATIENT UPDATE (PU) action and the\n Update Patient Record [PSO PAT] option.\n \n8. Added a new hidden ListMan 'CM' action to the Medication Profile called\n Manual Queue to CMOP [PSO LM QUEUE TO CMOP] to the PSO HIDDEN ACTIONS\n #2 PROTOCOL, to manually queue selected prescriptions to CMOP.\n \n9. Added a new column showing the B/D/F (Bad Address Indicator/ Do Not\n Mail/ Foreign Address) to the Log of Suspended Rx's by Day (this\n should be assigned to the appropriate personnel to setup the\n Division) [PSO PNDLOG] option.\n \n10. Modified Bad Address Suspended List [PSO BAI SUSPENDED] option to\n include the prompt either B/D/F or 'ALL' in the unprinted suspended\n prescriptions report.\n \n \nMISCELLANEOUS FIXES:\n-------------------\n \n above job.\n1. With the release of PSO*7*260, a line of code was missing from the\n View Prescription [PSO VIEW] option that displays Dosage, Verb,\n Dispense Unit, Noun, Route, and Schedule. This patch restores this\n functionality.\n \n2. The field description of the REFILL INACTIVE DRUG RXS field (#.111) of\n the OUTPATIENT SITE file (#59) has a typo. It is corrected to\n 'prescription'.\n \n \n Example: If the patient is marked as dead, the following message is\n generated:\n \n \n Subj: ALBANY Internet Refills Not Processed List, [#104161]\n 08/10/07@09:12 11 lines\n From: POSTMASTER In 'IN' basket. Page 1 *New*\n ------------------------------------------------------------------\n Internet Refills Not Processed Report for the ALBANY Division.\n \n The following refill requests were not processed:\n \n Patient: OPPATIENT,SEVEN SSN: 0000\n1. Internet Refill Automation and Reporting\n \n Rx #: 100002461 (REF #1) Qty: 2\n Drug: ASPIRIN 650MG SUPPOSITORIES\n Reason: Patient Died on AUG 10, 2007\n \n \n b. Added two new fields, PROCESS AUTO REFILLS FOR INPAT field (#2030)\n and PROCESS AUTO REFILLS FOR CNH field (#2035), to the OUTPATIENT\n SITE file (#59) to allow the sites to process/not to process refills\n for inpatients and CNH patients for the scheduled job defined in\n a. Internet Refill Automation Job\n item 1.a above. It will process these refills only if the site has\n flagged these fields as YES.\n \n The Site Parameter Enter/Edit [PSO SITE PARAMETERS] option is also\n modified to include these two new fields.\n \n c. Added a new LOGIN DATE field (#11) to the PRESCRIPTION REFILL\n REQUEST file (#52.43) to capture the date and time the refill\n request was made.\n \n Added a new Automate Internet Refill [PSO AUTO REFILL INITIALIZE]\n d. Added a new Internet Refill Report [PSO INTERNET REFILL REPORT]\n option, to the Output Reports [PSO OUTPUTS] menu that generates\n reports by division, detail, or summary of internet refills sorted\n by Patient, Date, or Result.\n \n2. Modified the Barcode Batch Prescription Entry [PSO BATCH BARCODE] and\n Process Internet Refills [PSO INTERNET REFILLS] options to provide\n separate prompts to Allow refills for inpatient and Allow refills for\n Contract Nursing Home (CNH) instead of a single prompt that applies to\n both.\n option to the Maintenance (Outpatient Pharmacy) [PSO MAINTENANCE]\n \n3. If the REGISTRATION package V. 5.3 patch DG*5.3*688 that introduces the\n COUNTRY field to the PATIENT file (#2) is installed, then:\n a. for Local Mail-outs with foreign addresses, the address information\n on the laser label mailing label is replaced with\n *** FOREIGN ADDRESS ***.\n \n b. In print from suspense, if the address is foreign and the routing is\n not "window", the label will not print nor will the prescription be\n sent to automated filling equipment. The fill will remain on suspense\n menu that allows the sites to schedule/un-schedule a background job\n until it is pulled early, or the routing is changed to window, or the\n address is changed.\n \n4. Added a new Queue CMOP Prescription [PSO RX QUEUE CMOP] option to the\n Suspense Functions [PSO PND] menu, Pharmacist Menu [PSO USER1] and\n Pharmacy Technician's Menu [PSO USER2] menu, to manually queue\n prescription to Consolidated Mail Outpatient Pharmacy (CMOP).\n \n5. The software is modified to check if the Provider has a DEA number in\n the DEA# field (#53.2) or a VA number in the VA# field (#53.3) of the\n to automatically process refill requests placed via the Internet. It\n NEW PERSON file (#200) and the YSCL AUTHORIZED key to order clozapine\n drug. Previously, the check was only for the DEA#. If the ordering\n provider does not have the DEA# or the VA#, the order cannot be placed\n and user will see the message 'Provider must have a DEA# or VA# to\n write prescriptions for clozapine'. Also, if the provider does not hold\n the YSCL AUTHORIZED key, the message 'Provider must hold YSCL\n AUTHORIZED key to write prescriptions for clozapine' is displayed.\n \n Note: The YSCL AUTHORIZED key was transported in the MENTAL HEALTH V.\n 5.01 patch YS*5.01*90 and should be assigned to the appropriate\n requires the PSOAUTRF key and generates MailMan messages by division\n provider to write prescriptions for clozapine.\n \n6. The View Provider [PSO PROVIDER INQUIRE] option is modified to display\n the NPI field (#41.99) of the NEW PERSON file (#200).\n \n7. Changes to the Patient Information (Profile) Screen\n a. The PATIENT STATUS field (#3) of the PHARMACY PATIENT file (#55) is\n added to the Patient Information screen. It will be displayed after\n the patient's eligibility.\n \n\n
\nThis patch has enhancements which extend the capabilities of the Veterans\nfor Print List is changed to PT for consistency with other Outpatient \nPharmacy options. \n \n2. The ePharmacy Medication Profile (View Only) [PSO PMP] option is \nchanged to display discontinued prescriptions that do not have a cancel \ndate defined.\nHealth Information Systems and Technology Architecture (VistA) electronic\npharmacy (ePharmacy) system. \n \nThis patch modifies the Outpatient Pharmacy (OP) V. 7.0 application in the\nfollowing areas:\n \n1. For the Reject Information screen under the Third Party Payer \nRejects - Worklist [PSO REJECTS WORKLIST] option, the hidden action PL \n\n
\nProblems have been reported with the expiration date of prescriptions.\nprescriptions.\n \nUp-arrow ('^') separated values (patients WITHOUT ICN#):\nSITE NAME VAMC (999)^158^0^0^0^0^0^0^0^0^0^247^3585^6653607\n \nRun Log:\n--------------------------------------------------------------------------\n----\nSEQ DATE/TIME INITIATOR ACTION\n--------------------------------------------------------------------------\n-----\n \n 1 10/21/07@12:01:25 USER1,TEST PATCH INSTALLATION\n 3 10/21/07@12:01:27 USER1,TEST QUEUED\n 4 10/21/07@12:01:29 USER1,TEST STARTED\n 5 10/21/07@18:12:29 USER1,TEST COMPLETED\n<END>\n \n \nOnce the tally process is completed, the same information above will be \nsent\nvia Mailman message on FORUM to the user who installed the patch and to \nThe count of prescriptions with this problem will be broken down into five\nthe\nfollowing support personnel:\n \n \n NAME Role\n -----------------------------------------------\n Barron, LuAnne EPS\n Mohamed, Anwer Developer\n Rocha, Marcelo Developer\n Ruzbacki, Ron Developer\ndifferent groups:\n Willette, Candice Implementation Manager\n Williamson, Eric Project Manager\n \nGROUP 1: Prescriptions with a null expiration date.\n \nGROUP 2: Expired prescriptions that are active in CPRS or with an \n expiration date greater than 366 days.\n \nIn some cases the date is not present and other cases have a wrong date.\nGROUP 3: Prescriptions past their expiration date that are active in\n Outpatient Pharmacy.\n \nGROUP 4: Deleted prescriptions. These prescriptions don't necessarily\n have a problem, however they will be resend to HDR.\n \nOTHER : Prescriptions with database inconsistencies, such as NO PATIENT,\n NO DRUG or NO ISSUE DATE are being counted for informational \n purpose only.\n \nFurthermore, most of the prescriptions with such problem are not in sync\nThe process to count these prescriptions will start right after the patch\nis installed. If it is necessary to stop, restart the job or to know the\nstatus of the job, run the following command in programmer mode:\n \n>D ^PSO283PI \n \nExpiration Date problem tally patch for Outpatient Pharmacy prescriptions\n=========================================================================\n Current status: RUNNING (Last Rx IEN: 2587430)\n \nwith Computerized Patient Record System (CPRS) V. 3.0 and/or Health \n Select one of the following:\n \n SP STOP TALLY JOB\n VW VIEW PARTIAL TALLY JOB RESULTS\n QT QUIT\n \n(SP)Stop,(VW)View,(QT)Quit: VIEW// VIEW PARTIAL TALLY JOB RESULTS\n \n \nExpiration Date clean up job for Outpatient Pharmacy prescriptions\nData Repository (HDR) in regards to their status. This patch will \n==================================================================\nCurrent status: COMPLETED ON Nov 06, 2007@17:03:36\n \n1. Institution : SITE NAME VAMC (999)\n PATIENT\n WITH ICN# \nW/NO ICN#\nGroup 1: RX'S WITH NO EXPIRATION DATE ---------- \n----------\n-------------------------------------\nidentify \n2. Calc exp date > CUTOFF (update HDR) \n363 158\n3. Calc exp date < CUTOFF,CPRS active (update HDR/CPRS) \n0 0\n4. Calc exp date < CUTOFF,CPRS non-active (update HDR) \n0 0\n5. No CPRS order# (Update HDR) \n0 0\n \nGroup 2: RX'S IN EXPIRED STATUS\nand report a tally of how many prescriptions have such problem. A \n-------------------------------\n6. CPRS active (update CPRS/HDR) \n5,400 0\n7. Exp>366 days,reset date,CPRS order# (update CPRS/HDR) \n0 0\n8. Exp>366 days,reset date,no CPRS order# (update HDR) \n18 0\n \nGroup 3: RX'S PAST EXPIRATION DATE BUT STILL ACTIVE\n---------------------------------------------------\nfollow-up\n9. CPRS active (update CPRS/HDR) \n0 0\n10. CPRS DC'd or expired (update HDR) \n0 0\n11. No CPRS order# (HDR will run own update) \n0 0\n \nGroup 4: RX's IN DELETED STATUS\n-------------------------------\n12. No CPRS order# (update HDR) \npatch (PSO*7*293) will subsequently be released to fix these \n2,275 247\n \nOTHER\n-----\n13. BAD RX's: NO PATIENT,DRUG or ISSUE DT (NO UPDATES): 3,585\n \n14. TOTAL NUMBER OF PRESCRIPTIONS ANALYZED: 6,653,607\n \nUp-arrow ('^') separated values (patients WITH ICN#):\nSITE NAME VAMC (999)^363^0^0^0^5400^0^18^0^0^0^2275^3585^6653607\n\n\nThis patch corrects the following issues.\n \nHD204891 - trade name error (PSI-07-155)\n\n
\nThis patch contains corrections for the following Issues\nHD94995 - I have recieved a complaint from the Pharmacy that the \n Pharmacist field in the prescription file is being filled in\n during the prescription entry process.\nHD176910 - Outpatient Pharmacy Activity Log Problem\n HD161861.\nHD176910 - Outpatient Pharmacy Activity Log Problem.\n\n
\nThis patch resolves several issues. \n3. The site parameter EDIT PATIENT DATA is not working properly.\nWhen set to "YES", it should prohibit editing SSN and DOB. The input\ntemplates [PSO OUTPT] and [PSO OUTPTA] contained in the PATIENT\nfile (#2) have been updated. \n \n4. After archiving prescriptions, the archived prescription number may be \nreused. This had created the potential to have two series of prescriptions \nusing the same number. Added check for new prescriptions for existing\nnumbers. \n \n \n \n5. Two erroneous ^DD nodes are deleted from the PHARMACY PATIENT \nfile (#55). They are ^DD(55,0,"P") and ^DD(55,0,"PS"). \n \n \n6. Updated the DD(52,0,"ID",6) with correct reference to new field location. \n1. The routine PSOAMIS0 used the variable DFN to represent a value\nother than the internal file number in the PATIENT file (#2). This variable\nname was changed to PSODFN to comply with standards. \n \n2. It fixes a potential error when running the nightly tasked job, Compile\nAMISData (NIGHT JOB) [PSO AMIS COMPILE]. \n \n\n
\nSite reported that the incorrect Orderable Item was selected when the\nentry was entered in "lowercase". This caused the incorrect medication\nto be given.\n\n
\nPSO*7.0*206 \nHD68224 - DEA Code handling changes.\n HD68648- dup HD68224\n HD85385- dup HD68224\n HD179790- dup HD68224\nHD186713 - Label shows Certified after mail status.\nHD156961 - Medication status of renewed for meds past stop date.\nHD161968 - Max refill issue for monthly clozapine patient\n\n
\nThis patch will correct the following issues:\n \nHD206713 Activity Log issues\nHD170652 - <UNDEFINED>PAT+1^PSOSD\n\n
\nPROBLEM:\n1. If expiring or discontinuing a prescription that also has a pending\nrenewal, the "renewed from" CPRS order's status is changed to expired or\ndiscontinued instead of staying as "renewed".\n \n2. If cancel a pending renewal for a previously expired (or \ndiscontinued) prescription that had been renewed after expired, the \n"renewed from" CPRS order should go back to "expired" (or "discontinued")\ninstead of remaining as "renewed".\n \nRESOLUTION:\n--------\n-----------\n1. PSOHLSN1 - If expiring or discontinuing a prescription that also has a\npending renewal, keep the "renewed from" CPRS order's status as "renewed".\n \n2. PSOHLSN: - If cancel a pending renewal for a previously expired (or \ndiscontinued) prescription that had been renewed after expired (or \ndiscontinued), set CPRS order's status back to expired (or discontinued).\nHD214867 - Renewed orders remaining active\n \n \nPSI-06-177 - RENEWED ORDERS REMAINING ACTIVE\n(Note: Other scenarios related to renewed orders are being corrected in\npatch PSO*7*257).\n \n\n
\nPatch PSO*7.0*275 will correct the following issues\nHD122245 Editing Provider Comments/patient instructions\n d-HD154492 Leading punctiation prevents editing Patient \n Instructions\nHD179234 Issue with selecting service related option.\nHD196315 Error - <UNDEFINED>SETNEW^PSOBINGO\n\n
\nEmergency patch to disable PSO SPEED RENEW PROTOCOL.\n\n
\nThis patch addresses PSI-06-177 - MED STATUS RENEWED PAST STOP DATE\n DISCONTINUED\n SPECIAL QUEUEING: \n________________________________________________________________________\nExit Save Next Page Refresh\n \nEnter a command or '^' followed by a caption to jump to a specific field.\n \nCOMMAND: Save \n \n \nEnd Capture ********** \n CANCELLED\n DISCONTINUED/EDIT\n EXPIRED\n \nThis patch corrects an additional issue with mis-calculating the default \nvalue for the start date prompt for the Manual Auto Expire Rxs [PSO MANUAL\nAUTO EXPIRE] option. \n \nThis patch fixes an error received when running the Compile AMIS Data\n \n(NIGHT JOB) [PSO AMIS COMPILE]. When the Expire Prescriptions [PSO EXPIRE\nPRESCRIPTIONS] or Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] process\nruns at the same time the CMOP transmission is running bad data can be\ncreated. The Expire Prescriptions and Manual Auto Expire Rxs processes\nwill delete the last refill data if the refill does not have a label\nprinted (CMOP fills do not have this) and does not have a Release\nDate/Time which they do not if CMOP has not yet released the refill. The\nrefill node is deleted and then when CMOP does release the refill it only\nsets the Released Date/Time and Dispensed Date so this will be the only\ndata set for the refill which causes the error in the AMIS compile.\nThis patch will modify the Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE]\n \n==================\n** IMPORTANT!! **:\n================== \nPlease check that the nightly expire - PSO EXPIRE PRESCRIPTIONS job is\ntasked to run on a 24 hour rescheduling frequency. This is very important,\nas it relates to the HDR, because this job sets the status of a\nprescription to Expired the day after the prescription expiration date,\nand also updates CPRS and the HDR with this information. If this job is\nnot running, prescriptions could show as Active in the HDR, when the\noption and the Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option to\nexpiration date is in the past.\n \nThe job in TaskMan would look something like this:\n \n2478948: PSO EXPIRE PRESCRIPTIONS - Expire Prescriptions. No device.\n CHYSQA,ROU. From Today at 1:11, By you. Scheduled for \nToday at 23:00\n \n \n \ncheck for more values of the STATUS field (#5) in the ORDER file (#100) in\nPlease check to see if this job is tasked to run on a 24 hour \nrescheduling frequency. To access the set-up of this job in Outpatient \nPharmacy, follow these steps:\n \n \nBegin Capture **********\n \n \nSelect OPTION NAME: PSO MANAGER Outpatient Pharmacy Manager\nOutpatient Pharmacy software - Version 7.0\nthe Computerized Patient Record System (CPRS) before deciding whether to \n \nDivision: ALBANY 500 \n \n You are logged on under the ALBANY division.\n \nSelect PROFILE PRINTER: HOME// COMPUTER ROOM\n \nSelect LABEL PRINTER: HOME// COMPUTER ROOM\n \nOK to assume label alignment is correct? YES// \nsend the expire transaction. Before, the expire transaction was sent if \n \nBingo Board Display: OUTPATIENT// \n \n \nSelect Outpatient Pharmacy Manager Option: MAintenance (Outpatient \nPharmacy)\n \n \nSelect Maintenance (Outpatient Pharmacy) Option: EXPire Prescriptions\n \nthe STATUS field was "ACTIVE". This patch checks for the CPRS status not\nNOTE:\n(The only fields that need to be filled in are the "QUEUED TO RUN AT \nWHAT TIME" field to what time you want the job to run, and the \n"RESCHEDULING FREQUENCY" field, which should be set to 24H.)\n \n Edit Option Schedule\n Option Name: PSO EXPIRE PRESCRIPTIONS \n Menu Text: Expire Prescriptions TASK ID: 74539 \n _______________________________________________________________________\n \nbeing any of the following and if not, will send the expire transaction:\n QUEUED TO RUN AT WHAT TIME: MAR 23,2006@19:00 \n \nDEVICE FOR QUEUED JOB OUTPUT:\n \n QUEUED TO RUN ON VOLUME SET:\n \n RESCHEDULING FREQUENCY: 24H \n \n TASK PARAMETERS:\n \n\n
\nThis patch has enhancements which extend the capabilities of the Veterans \n1. EPHARMACY MEDICATION PROFILE (VIEW ONLY) [PSO PMP] option has been\nmodified in the following manner:\n \n a. Patients flagged with the Bad Address indicator will display the\n same warning messages as PATIENT PRESCRIPTION PROCESSING [PSO LM\n BACKDOOR ORDERS] option. If the user holds the PSO ADDRESS UPDATE\n key, a prompt to update the address/phone will be displayed.\n \n b. The PU - Patient Record Update action has been added to the\n Patient Medication Profile screen. To achieve this, the \nHealth Information Systems and Technology Architecture (VistA) electronic \n PU action was added to the PATIENT MEDICATION PROFILE protocol\n menu [PSO PMP MENU].\n \n The following actions have been removed from the Patient \n Medication Profile screen by removing them from the PATIENT\n MEDICATION PROFILE protocol menu [PSO PMP MENU]:\n \n DR Sort By Drug\n ID Sort By Issue Date\n LF Sort By Last Fill Date\npharmacy (ePharmacy) system that supports the Electronic Claims \n RX Sort By Prescription\n \n c. The above removed actions have been added to the hidden actions\n menu by adding them to the ePharmacy Medication Profile Hidden \n Actions [PSO PMP HIDDEN ACTIONS MENU] protocol.\n \n d. The REJ View Reject action was added to the hidden menu on the Rx\n View screen. The ePharmacy Hidden Actions Menu #2 [PSO PMP HIDDEN\n ACTIONS MENU #2] protocol was added to contain this new action,\n and this protocol is also used by the VIEW PRESCRIPTION option\nManagement Engine (ECME). It is the first of four stand alone patches\n [PSO VIEW].\n \n \n2. The default answer of (I)gnore on the Reject Processing Screen has \nbeen changed to (Q)uit which automatically sends the claim rejection \ninformation to the Pharmacy Reject Worklist (i.e. re-instate discontinued \norder, unhold, refill, PP - pull early from suspense, edit that doesn't \ncreate a new order, and release with NDC edits). Due to conflicting patch\nrelease schedules and shared routines with another Pharmacy patch, the new\norder, copy, edits that create new orders, and renewal functions will\nthat will fulfill the requirements of ePharmcy/ECME Enhancements Phase 4 \nremain with a default answer of (I)gnore for reject processing screens\ndisplayed prior to label print. These functions will be updated in a\nsubsequent ePharmacy Iteration II patch when the conflict no longer\nexists.\n \n3. The VIEW PRESCRIPTION [PSO VIEW] option has been modified to give \ncomprehensive help text for the VIEW PRESCRIPTION prompt. The REJ View\nReject action was added to the ePharmacy Hidden Actions Menu\n# 2 [PSO PMP HIDDEN ACTIONS MENU # 2].\n \nIteration II. It modifies the Outpatient Pharmacy V. 7.0 application as\n4. The ECME LOG was recording the routing of WINDOW for all original \nfills and refills. A modification was made to correctly state the route \nfor each fill that is processed after this patch is installed. The \nPATIENT PRESCRIPTION PROCESSING [PSO LM BACKDOOR ORDERS] option, VIEW\nPRESCRIPTION [PSO VIEW] option, and EPHARMACY MEDICATION PROFILE (VIEW \nONLY) [PSO PMP] option is affected by this change.\n \n5. The ECME Log entry that is stored when a prescription is printed\nfrom suspense has been changed from stating ECME:SUSP LABEL PRINTED to \nECME:PRINTED FROM SUSPENSE. This change will affect fills processed \ndescribed below:\nafter this patch has been installed. \n \n6. A change was made to allow the user to edit Dispensed As Written (DAW)\nand National Drug Code (NDC) fields for expired and discontinued ePharmacy\nprescriptions and refills.\n \n7. A modification was made to store the last used NDC for payable \nprescriptions that were pulled early from suspense. This change affects\nthe PULL EARLY FROM SUSPENSE [PSO PNDRX] option and the PP Pull RX action\nof the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option.\n \n \n8. A post intall routine (PSO260PI) from PSO*7.0*260 will be deleted \nwith this patch.\n \n\n
\n \nnext prompt for prescription, if an @ is entered, an undefined error \noccurs. (HD210092)\n \n2. In the Prescription Cost Update [PSO RXCOST UPDATE] option, unless the \noriginal fill date for the prescription is included in the requested date \nrange, the cost will not be updated in the PRESCRIPTION file (#52) for\nany of the fills. If the user selects to update refills and partials \nalso, it updates all fills on the prescription regardless of whether \nthey were within the requested date range. This patch makes a correction\nto update fills only within the requested range without having to \nThis patch corrects the following issues:\ninclude the original fill in that range. If the user selects an end fill\ndate of today or in the future, this option will update the cost for all\nexisting and suspended fills that have a fill date in the future. \n(HD213587)\n \n3. Older data in the Health Data Repository (HDR) could contain\nnon-numeric data in the quantity field for some prescriptions. The data\ndefinition was changed in patch PSO*7*29 to no longer allow alpha\ncharacters. The following was added to the technical description for\n 1. QTY field (#7) in the PRESCRIPTION file (#52)\n \n 2. QTY field (#1) in the PRESCRIPTION file REFILL multiple (#52.1)\n 3. QTY field (#.04) in the PRESCRIPTION file PARTIAL multiple (#52.2)\n \n NOTE: QTY values that were on file prior to patch PSO*7*29 (released\n 2/17/00) may contain alpha characters.\n(HD211759)\n1. In the Delete a Prescription [PSO RXDL] option:\n a. If entering a prescription number that has previously been deleted \nand then pressing enter when prompted for a prescription again, an\nundefined error occurs. (HD212690)\n b. If enter a character like ! at the prescription prompt, 2 question\nmarks are displayed because it is an invalid prescription. Then at the\n\n
\nMODIFY PSO COST TO IGNORE BAD XREFS IN FILE 52\n \nAn Undefined error occurs when editing a large number of prescriptions.\n \nCorrect OPAI option 4 in file #59 field #28 (send marked drugs and\nprint labels)\n \nLocking Issue\n\n
\n1. This patch fixes the problem of the allergy warning label document\nCopayment [PSOCP EXEMPTION] option. When setting a status from No to\nYes, a warning will now be given, and a mail message will be sent to\nall PSORPH key holders informing them of this change.\n \n4. This patch fixes a problem of messages not being exchanged successfully\nbetween Outpatient Pharmacy and an external application. This problem\nwould occur for sites that have the EXTERNAL INTERFACE site parameter set\nto 1 (SEND ALL ORDERS AND PRINT LABEL), 2 (SEND ALL ORDERS AND DON'T PRINT\nLABEL), or 3 (SEND MARKED ORDERS AND DON'T PRINT). Also fixed some\nformatting problems with reports related to the external interface\npossibly printing prior to the filling label for a prescription,\nfunctions.\n \n5. This patch fixes a problem of an invalid Initiator of Activity being\nstored and displayed in the ACTIVITY LOG REASON (#53.3) file for an edit\nof a prescription.\n \n6. This patch fixes an undefined error that could occur if an invalid\nbarcode is entered while in the Change Suspense Date [PSO PNDCHG] option.\n \n7. This patch corrects a problem that can occur when entering a refill\nwhen there is no allergy entered to that drug for the patient.\ndate for a refillable controlled substance prescription. The date range\ndisplayed should be the issue date to the expiration date, normally\nfollowed by a default of Today. The date range ending date will sometimes\nshow beyond six months, which is invalid for a refillable controlled\nsubstance prescription. This patch corrects this problem.\n \n2. Currently, when entering a new prescription, a non-numeric entry can\nbe entered for the quantity. This patch makes a leading numeric required\nfor the quantity.\n \n3. This patch makes a change to the Exempt Rx Patient Status from\n\n
\nThis patch performs the actual prescription clean up for prescriptions \nmessages to CPRS and HDR so these two applications can update the \nPrescriptions with an expiration date on or before the CUTOFF DATE with\na Pharmacy 'ACTIVE' status\n \n a) Set the STATUS field (#100) in the PRESCRIPTION file (#52) to \n EXPIRED.\n b) If the CPRS order status is 'ACTIVE'\n b1) Update CPRS*\n b2) Update HDR (if CPRS is updated).\n c) If the CPRS order status is 'NON-ACTIVE' \n c1) Update HDR\ncorresponding order with the expired status on their systems. This patch\n \n NOTE: If the prescription does not have a corresponding CPRS Order\n Number, the counter for this specific problem will be \n incremented. However, the HDR will not be updated. HDR will\n perform their own clean up for these cases.\n \nGROUP 4:\n-------\nDeleted prescriptions for patients.\n \nwill address these problems. Below is a detailed description on this\n a) Update HDR\n \n \n * CPRS will only be updated if the prescription contains the \n corresponding CPRS Order Number for the prescription being cleaned\n up. Furthermore, CPRS will not be updated if the corresponding \n CPRS order is on a 'NON-ACTIVE' status.\n \n \nThe clean up process will start right after the patch is installed. If \nprocess:\nit is necessary to stop, restart the job or to know the status of the\njob, do the following:\n \n \n>D ^PSO293PI \n \n Expiration Date clean up job for Outpatient Pharamcy prescriptions\n ==================================================================\n Current status: RUNNING (Last Rx IEN: 2587430)\n \n \n Select one of the following:\n \n SP STOP CLEAN UP JOB\n VW VIEW PARTIAL CLEAN UP JOB RESULTS\n QT QUIT\n \n(SP)Stop,(VW)View,(QT)Quit: VIEW// VIEW PARTIAL CLEAN UP JOB RESULTS\n \n \nExpiration Date clean up job for Outpatient Pharmacy prescriptions\nExpiration post-install job clean-up flow:\n==================================================================\nCurrent status: COMPLETED ON Nov 06, 2007@17:03:36\nDATE AUTO-EXPIRE COMPLETED field: \n \n1. Institution : SITE NAME VAMC (999)\n # of Rx's\nGroup 1: RX'S WITH NO EXPIRATION DATE cleaned up\n------------------------------------- ----------\n2. Calc exp date > CUTOFF (update HDR) 363\n3. Calc exp date < CUTOFF,CPRS active (update HDR/CPRS) 0\n------------------------------------------\n4. Calc exp date < CUTOFF,CPRS non-active (update HDR) 0\n5. No CPRS order# (Update HDR) 0\n \nGroup 2: RX'S IN EXPIRED STATUS\n-------------------------------\n6. CPRS active (update CPRS/HDR) 5,400\n7. Exp>366 days,reset date,CPRS order# (update CPRS/HDR) 0\n8. Exp>366 days,reset date,no CPRS order# (update HDR) 18\n \nGroup 3: RX'S PAST EXPIRATION DATE BUT STILL ACTIVE\nIn order to explain the process to clean up these prescriptions the\n---------------------------------------------------\n9. CPRS active (update CPRS/HDR) 0\n10. CPRS DC'd or expired (update HDR) 0\n11. No CPRS order# (HDR will run own update) 0\n \nGroup 4: RX's IN DELETED STATUS\n-------------------------------\n12. No CPRS order# (update HDR) 2,275\n \n13. TOTAL NUMBER OF PRESCRIPTIONS ANALYZED: 6,653,607\nfollowing terms will be mentioned below:\n \nUp-arrow ('^') separated values:\nSITE NAME VAMC (999)^363^0^0^0^5400^0^18^0^0^0^2275^6653607\n \nRun Log:\n--------------------------------------------------------------------------\nSEQ DATE/TIME INITIATOR ACTION\n--------------------------------------------------------------------------\n 1 10/21/07@12:01:25 USER1,TEST PATCH INSTALLATION\n 2 10/21/07@12:01:25 USER1,TEST DATE AUTO-EXPIRE set: 01/19/08\n \n 3 10/21/07@12:01:27 USER1,TEST QUEUED\n 4 10/21/07@12:01:29 USER1,TEST STARTED\n 5 10/21/07@18:12:29 USER1,TEST COMPLETED\n<END>\n \n \nOnce the clean up process is completed, the same information above will be\nsent via Mailman message on FORUM to the user who installed the patch and\nto the following support personnel below:\n \nidentified by patch PSO*7*283. Patch PSO*7*283 performed a tally, while \nCUTOFF DATE: \n \n NAME Role\n -----------------------------------------------\n Bruun, Jesse HDR\n Consentino, Albert EPS\n Mohamed, Anwer Developer\n Rocha, Marcelo Developer\n Ruzbacki, Ron Developer\n Willette, Candice Implementation Analyst\n Williamson, Eric Project Manager\n-----------\n \n \nNote: The sites will not have to take any action once they receive the\n result message above generated by the post-install. \nThe message \n will not be generated from non-production accounts (e.g., test\n account).\n \nBesides the clean up process, this patch introduces a change intended to\naddress a sporadic scenario where a prescription does not contain a \nThis is the date last processed by the Auto Expiration Background Job.\npointer to the corresponding CPRS order # and it goes through a status\nchange (e.g. from Active to Expired). Currently, such status change event\nis not communicated to HDR. This patch contains a fix to notify HDR of\nthe status change event for such prescriptions.\nThis background job is supposed to be run nightly by every site. This date\nis stored in the field DATE AUTO-EXPIRE COMPLETED (#49.95) in PHARMACY\nSYSTEM file (#59.7) and it was introduced by the patch PSS*1*128 and it \nshould be populated with a valid date in all site. In case this field is\nnull, the post-install routine in this patch will set it to to the date\ncorresponding to 2 days in the past from this patch installation date. For\nexample, if the patch is installed on March 5, 2008 and the field is null,\nthis patch will correct the prescriptions with the expiration date and/or\nit will be set to March 3, 2008 (in the correct Fileman date format).\n \nCALCULATED EXPIRATION DATE:\n--------------------------\nThe expiration date for prescription with a null expiration date is\ncalculated by the following formula:\n \n For Rx with no refills: \n \n NUMBER OF DAYS SUPPLY FROM Rx ISSUE DATE (MININUM: 30 DAYS)\nstatus issues. In some cases the date is not present and other cases have \n \n Rx with 1 or more refills: \n \n Non-controlled Substances: \nRx ISSUE DATE + 366 DAYS \n \n Controlled Substances : Rx ISSUE DATE + 184 DAYS \n \nCPRS 'NON-ACTIVE' STATUS:\n------------------------\na \nThe following CPRS statuses: DISCONTINUED, EXPIRED, DISCONTINUED/EDIT and \nCANCELLED are considered 'NON-ACTIVE' by Pharmacy in this clean up \nprocess.\nThis means that Pharmacy will not send a prescription expiration event to \nCPRS if the CPRS order status is set to one of these.\n \nPHARMACY 'NON-ACTIVE' STATUS:\n---------------------------\nThe following Pharmacy statuses: EXPIRED, DISCONTINUED, DELETED, \nDISCONTINUED BY PROVIDER, DISCONTINUED (EDIT) are considered 'NON-ACTIVE'\nwrong date. Furthermore, most of the prescriptions with such problems are\nby Pharmacy in this clean up process.\n \n \nCLEAN UP PROCESS DESCRIPTION:\n---------------------------- \nPrescriptions with an expiration date problem are being analyzed and\ncleaned up differently, depending on which GROUP\n below they fall under:\n \n \nnot in sync with Computerized Patient Record System (CPRS) V. 3.0 and/or\nGROUP 1:\n-------\nPrescriptions with a null expiration date for patients.\n \n a) Set the CALCULATED EXPIRATION DATE in the EXPIRATION DATE\n field (#26) of the PRESCRIPTION file (#52).\n b) If the expiration date is on or before the CUTOFF DATE \n b1) If the prescription is not already in a Pharmacy 'NON-ACTIVE'\n status, set the STATUS field (#100) in the PRESCRIPTION\n file (#52) to EXPIRED.\nHealth Data Repository (HDR) in regards to their status. This patch makes\n b2) Update CPRS*\n b3) Update HDR\n c) If the expiration date is past the CUTOFF DATE\n c1) Update HDR\n \nGROUP 2:\n-------\nExpired prescriptions for patients.\n \n a) If the prescription expiration date is GREATER than 366 days\nthe correction to the expiration date of these prescriptions and send \n a1) A new expiration date will be calculated and set in the \n EXPIRATION DATE field (#26) of the PRESCRIPTION file (#52).\n a2) Update CPRS*\n a3) Update HDR\n b) If the prescription expiration date is LESS than 366 days\n b1) Update CPRS*\n b2) Update HDR (if CPRS is updated)\n \nGROUP 3:\n-------\n\n\nThis patch introduces the components necessary to build four tools\norders that need to be changed.\n \nTool 2 is a Medication Chart health summary component. This report\nprovides a grid-formatted list of active and pending medications suitable\nfor giving to a patient at a clinic visit or upon discharge from the hospital.\n \nTool 3 is a TIU data object provided as an alternative to the Medication\nChart health summary process. The unique aspect of this object is that\nthe list, generated for the patient,includes recently expired\nmedications but not recently discontinued medications.\nuseful for medication reconciliation.\n \nTool 4 is a series of TIU data objects and health summary components that\nretrieve remote active medications and remote allergy/ADR data.\n \n \nTool 1 is a Medication Reconciliation Profile health summary component.\nThis report creates an alphabetical list of outpatient prescriptions,\nunit dose medications, documented non-VA medications, and remote VA\nmedications. This summary can be used at transition points in a patient's\ncare, (admission, discharge, etc.) to identify medications that need to\nbe continued, new items to be ordered, old items to be discontinued, or\n\n
\nSUBSCRIPT ERROR WHEN RUNNING THE HEALTH SUMMARY\n\n
\nThis patch will correct the following\n \nHD216000 - PSOAUTRF Key\nHD226478 - Field missing in NTE segment of HL7 for PMI\nHD214848 - Incorrect wording: Division used to describe Institution\n\n
\nThe Enrollment VistA Changes (EVC) project is being undertaken to support\nThis patch provides the functionality changes to determine, process and\n VIEW 2 - This provides the medication list sorted by prescription\n Status Group, Status, and Drug Name.\n Active group:\n Active\n Hold\n Pending group\n Non-Verified\n Pending\n Discontinued\n Discontinued by Provider\ndisseminate the newly added Environmental Indicator (EI) called Project\n Discontinued (Edit)\n \n VIEW 3 - This provides the medication list sorted by Drug Name,\n active/suspended and Stop Date/Expiration Date.\n \n c. Flag/Un-Flag functionality (PSI-06-041)\n It was requested in the Remedy ticket #133716 that the flagging\n capability that is available in CPRS be made available for\n Outpatient Pharmacy use. This patch provides the flagging\n functionality for Pending orders only.\n112/SHAD Exposure (a.k.a SHAD), where applicable.\n \n d. As per the E3R numbers 19973 and 19876, to improve communication\n between the provider and the pharmacist, Outpatient Pharmacy will now\n send the actual comments made by the pharmacist to CPRS when a\n prescription is put on Hold, Discontinued, and Returned to Stock\n replacing the generic "per pharmacy request" text.\n \n e. When the DC-Discontinue ListMan option is used to discontinue a\n pending "renewal" order, the software will now check for an active\n prescription for the same drug. If found it will prompt the following:\n \n "There is an active Rx for this pending order, Discontinue both\n (Y/N)".\n This will provide the user with the option to discontinue both pending\n and the active order.\n \n f. A problem was reported in one of the error messages displayed on CPRS\n side when a provider tries to discontinue an Outpatient Pharmacy\n order from the Orders Tab and that order for some reason is\n not found in the PRESCRIPTION file (#52). The solution provided is to\n replace the error message "Unable to locate order" with "Invalid\nThis patch also changed the EI, "Environmental Contaminant" to read\n Pharmacy order number" to be in consistent with the Inpatient\n Medications V. 5.0 error messages.\n \n g. At the request of CPRS active calls to obsolete routine OR3CONV have\n been removed from Outpatient Pharmacy V. 7.0.\n \n h. When finishing a pending order placed in CPRS, it was reported that\n the patient instructions sent across to CPRS was getting truncated.\n This patch fixes the problem.\n \nas "Southwest Asia Conditions".\n i. PSI-07-057 - Potential of inappropriate or misleading provider\n comments to be automatically included on new medication orders.\n To fix this problem CPRS is dropping (will not carry over) the\n original provider comments during renewals of Outpatient Pharmacy\n medications.\n To follow suit with CPRS, Outpatient Pharmacy is also dropping the\n original provider comments from all backdoor renewals.\n \n 1. For the following options, when creating a new order, renewing an\n existing order, copying an existing order to a new order, or editing\n an existing order that results in a new order, the copay status of the\ntechnology and business changes that are occurring with the implementation\n prescription needs to be determined for billing purposes.\n \n a. Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n b. Barcode Batch Prescription Entry [PSO BATCH BARCODE]\n c. Complete Orders from OERR [PSO LMOE FINISH]\n \n If a patient is found eligible for SHAD then the prompt\n "Was treatment related to PROJ 112/SHAD?" will be presented to the\n pharmacist.\n \nof the Health Eligibility Center (HEC) Enrollment System Redesign (ESR)\n A "YES" or "NO" response will be stored in the new fields, PROJ\n 112/SHAD field (#122.01) of the PRESCRIPTION file (#52) and in the PROJ\n 112/SHAD field (#8) of the ICD DIAGNOSIS sub-file (#52.052311) of the\n PRESCRIPTION file (#52).\n \n 2. The Integration Control Registration (ICR) #2534, provides\n Computerized Patient Record System V. 3.0 (CPRS) with all the eligible\n EI questions that will be prompted during the pharmacy order entry\n process. This ICR is modified to include the SHAD prompt.\n \nproject. Some modified and new business functionality is being included in\n 3. When a verbal or telephone order is placed in backdoor pharmacy, it\n requires an electronic signature from the provider. During the\n signature entry process in CPRS, the provider may update the SC, EI,\n or the ICD diagnosis information. This updated information is passed\n back to pharmacy via the ICR #4666, which is modified to include the\n SHAD changes.\n \n 4. The PENDING OUTPATIENT ORDERS file (#52.41) that stores the pharmacy\n orders entered via CPRS is modified to include the provider's response\n to the SHAD question. The provider's response will be stored in the\nthe new system and corresponding changes are necessary in VistA for\n new fields, PROJ 112/SHAD field (#110.2) of the PENDING OUTPATIENT\n ORDERS file (#52.41) and the PROJ 112/SHAD field (#8) of the DIAGNOSIS\n sub-file (#52.41311) of the PENDING OUTPATIENT ORDERS file (#52.41).\n \n 5. During the release of a prescription, if the SHAD question applies and\n is unanswered, the MailMan message that is sent to the finishing\n pharmacist, ordering provider, and holders of the PSO COPAY key, to\n get answers to the EI questions will have the SHAD question if\n applicable.\n \npreliminary determination of veterans Enrollment and Eligibility status.\n 6. The Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]\n option is modified to include the SHAD question wherever applicable.\n \n 7. During label printing, if the prescription is flagged as SHAD then the\n text "NO COPAY" will be printed in the label.\n \nUnrelated to the Enrollment VistA Changes (EVC) features, this patch also\nprovides the following changes to support CPRS v27.\n \n a. To add the proper escape sequences to the standard HEALTH LEVEL\nThe EVC project has been rolled out in three phases. This release\n SEVEN (HL7) encoding characters to messages sent to CPRS / remove\n escape sequences received from CPRS and replace them with standard HL7\n encoding characters. This will help avoid errors that can occur if\n special delimiting characters are encountered during parsing of the\n HL7 messages.\n \n b. Integration Control Registration (ICR) #2400, will be modified to\n provide new sorting sequences of the patient medication profile that\n is viewed under the CPRS-Meds Tab including the Non-VA medications.\n \nrepresents the third and last phase called EVC Release 2.\n VIEW 0 or null - This provides the medication list as it was prior to\n GUI 27 so that other applications calling this API will not\n see any changes.\n VIEW 1 - This provides the medication list sorted by prescription\n Status Group and Stop Date/Expiration Date. Following is the\n order:\n Pending group\n Non-Verified\n Pending\n Active group:\n \n Active\n Hold\n Suspended (Active/Susp)\n Provider Hold\n Expired group\n Expired\n Discontinued/Deleted group\n Discontinued by Provider\n Discontinued (Edit)\n \n\n
\nOrder checks are not generated when editing the dose of a prescription.\n\n
\nThis patch is one of four patches that enhance the ePharmacy software to \n \n \n \n3. (Dormant except for item C.) - The Third Party Payer Rejects -\nWorklist [PSO REJECTS WORKLIST] option and the Third Party Payer Rejects -\nView/Process [PSO REJECTS VIEW/PROCESS] options have been modified in the\nfollowing manner:\n \n A. Non-DUR/RTS Tricare rejections will be segregated at the end of\n the displayed information. They will be denoted with a "TRICARE -\n Non-DUR/RTS" header. This header will remain regardless of\n APPLICATION/VERSION PATCH\n whether the GI - Group by Insurance action is toggled on or off. \n The Tricare section will sort in the same manner as the main sort\n for non-Tricare prescriptions (i.e. by Rx, drug, patient, etc.).\n \n B. Tricare DUR/RTS rejects will be displayed with all other DUR/RTS\n rejects. When GI - Group by Insurance action is toggled on, the\n header "TRICARE" will be displayed, and this "TRICARE" section\n will sort alphabetically within the other insurances. This\n Tricare section is separate from the Non-DUR/RTS section that\n displays at the end of the listing. When GI is toggled off, these\n --------------------------------------------------------------\n rejects will sorted in the same section as all other DUR/RTS\n rejects.\n \n C. (Not dormant) - The new TRI - Show/Hide Tricare toggle action has\n been added to the hidden menu on the Insurance Rejects screen. \n When toggled to Show, Tricare Non-DUR/RTS reject will be\n automatically displayed at the end of the listing. Toggling the\n TRI action to Hide will remove them from the screen.\n \n D. The Reject Information screen has been modified to display TRICARE\n 1. CONSOLIDATED MAIL OUTPATIENT PHARMCY (CMOP) V. 2.0 PSX*2*66\n in the header for the Reject Information section. For DUR/RTS\n Tricare rejects, the IGN - Ignore Reject action will be shown but\n will not be selectable. For Non-DUR/RTS Tricare rejects, the FIL -\n Fill Rx action will be displayed. If the prescription is payable,\n the user will be allowed to fill the prescription and print the\n label. If not payable, a message will be displayed stating that\n the prescription must have a payable status to be filled.\n \n E. For rejects that remain in suspense, the user will be allowed to\n process the rejection as indicated above, however no labels will\n 2. OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*287\n be printed until the prescription is pulled early or printed from\n suspense. Upon resolving the reject, the user will be notified\n of this information. CMOP prescriptions will function in the same\n manner.\n \n4. In preparation for a future ePharmacy patch the following fields are \nbeing added to PRESCRIPTION file (#52) for original fills and refills:\nDATE NDC VALIDATED field (#83) and NDC VALIDATED BY field (#84). \n \n5. For ePharmacy prescriptions, the price per dispense unit for the\n 3. ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*6\nNDC will be saved in PRESCRIPTION file (#52). For original fills, the \nUNIT PRICE OF DRUG field (#17) will be updated. For refills, the CURRENT\nUNIT PRICE OF DRUG field (#1.2) of REFILL multiple (#52.1) will be\nupdated. If the NDC chosen is the default NDC, the value stored will be\ntaken from PRICE PER DISPENSE UNIT field (#16) of DRUG file (#50). If the\nNDC selected is a synonym, the PRICE PER DISPENSE UNIT field (#404) of\nSYNONYM multiple (#9) of DRUG file (#50) will be saved. In the case of\nCMOP fills, only the default NDC price will be stored which is taken from\nPRICE PER DISPENSE UNIT field (#16) of DRUG file (#50).\n \n 4. INTEGRATED BILLING (IB) V. 2.0 IB*2*383\n6. (Dormant) - If ECME's status on the claim remains in an "In Progress"\nstate past the processing time out during finish of the prescription,\nTricare prescriptions will not be allowed to be filled and must be\ndiscontinued.\n \n7. (Dormant) - If the pharmacy is active for ePharmacy processing but the\ninsurance plan is not linked or not active, Tricare prescription will be\nallowed to be filled normally. The phrase "Inactive ECME Tricare" will be\ndisplayed during Finish.\n \nAll four patches are being released separately with a requirement that \nthey be installed in the order outlined above. There are no other \nprovide the framework to support Tricare and Active Duty outpatient\ndependencies between these patches, except that Tricare/Active Duty \nbilling will not be supported by ePharmacy until all 4 patches are \ninstalled.\n \nAll sites should install these patches regardless of whether or not they \nhave been activated for ePharmacy by the CBO or are providing outpatient\npharmacy services to Tricare or Active Duty patients. After the\ninstallation of these patches, the activation status of the site will not\nbe impacted. As before, activation of the ePharmacy product will require\ninstructions provided by the CBO, and sites are not to activate ePharmacy\npharmacy billing. The Tricare/Active Duty portions of this software\nunless instructed specifically by the CBO. Also, sites should not start\nto provide outpatient pharmacy services to Tricare patients without\ndiscussions with the CBO.\n \nThis patch modifies the Outpatient Pharmacy v7.0 application as described\nbelow. The modifications labeled dormant in the software and will remain\ninactive until the future Tricare patch is released.\n \n1. (Dormant) - Prescriptions where the patient is Tricare eligible will\nbe submitted to ECME for third party insurance processing in the same\nenhancement will not be active until a future patch is released. The\nmanner as all other insurance types. Tricare eligibility is determined by\nIntegrated Billing (IB). An indicator is returned to Outpatient Pharmacy\nPRESCRIPTION file (#52) and REFILL multiple (#52.1) to be stored in the\nnew BILLING ELIGIBILITY INDICATOR field (#85). Because this is a set of\ncodes field, the internal value will be T, V or C. These values will be\ndisplayed respectively to the user as TRICARE, VETERAN, or CHAMPVA. Note\nthat CHAMPVA will not be addressed in this patch. Prescriptions with only\na 'VETERAN' eligibility flag are what is currently processed through ECME.\n \n2. (Dormant) - When a Tricare prescription has a third party rejection,\nrelease of the additional patch is pending Central Business Office (CBO)\nthe same reject notification screen will be displayed to the user as is\ncurrently done for the Veteran eligibility. Tricare Rejections will be\nstored in the same manner as Drug Utilization Review (DUR) and\nRefill-too-soon (RTS) prescription reject are currently stored.\n \nThe following exceptions will apply for Tricare prescriptions:\n \n A. All Tricare rejections will be denoted as Tricare in the REJECT \n Information header on the Reject Information screen.\n \ncontracting with the Tricare Fiscal Intermediary.\n B. Where DUR or RTS are one of the reject codes, the user will be\n able to select from (D)iscontinue the prescription, submit \n (O)verride codes, or (Q)uit which sends the rejection to the Third\n Party Payer Rejects - Worklist. Tricare rejection may not be\n (I)gnored.\n \n C. For prescription rejections that have non-DUR/RTS rejects, the\n user will be able to select from (D)iscontinue the prescription or\n (Q)uit which sends it to the Third Party Payer Rejects - Worklist.\n \n \n D. For non-billable Tricare prescriptions, an abbreviated version of\n the reject notification screen will be displayed. Because the\n prescriptions is non-billable, the insurance and ECME information\n that's currently provided for DUR/RTS rejects will not be\n displayed (i.e. insurance, group name, group #, ECME #, contact,\n cardholder ID). In this case, the user will only be able to\n (D)iscontinue the prescription due to the business rule that OP\n cannot fill Tricare prescriptions that are non-billable.\n \n E. Labels will not print for discontinued Tricare prescriptions.\nBelow is a list of all the applications involved in this project along \n Reprint labels will not be allowed to be printed for Tricare\n rejected prescriptions. The reject notification screen will be\n displayed during reprint in the same manner as non-Tricare\n prescription currently are displayed with the exception of the\n available actions listed above for Tricare prescriptions.\n \n F. Suspended prescriptions will remain on suspense when a reject\n occurs, when the Rx is non-billable, or when the third party claim\n remains in an 'IN PROGRESS' status in ECME. Labels will not\n print. Once the reject is resolved, the user may pull the Rx \nwith their associated patch number:\n early from suspense or wait for the next scheduled print from\n suspense runs at which time labels will print accordingly. This\n includes CMOP and local suspense.\n \n G. Rejected Tricare prescription may not have a partial fill ordered \n until the reject is resolved.\n \n H. When the Pull Early from Suspense [PSO PNDRX] option is used, \n Tricare prescriptions will be processed in the foreground and\n rejections will be displayed for user intervention.\n\n
\nSCRIPTALK DISPLAYING LAST 6 OF SSN\n\n
\nCPRS GUI V27 FOLLOW UP ISSUES: \n \n \n .D PP S ORD=0 D @PSRT S PAT(PAT)=PAT\n ^\n <NOLINE>PRI+15^PSOORFI5\n \nThis patch will correct this issue.\n=============================\n \nThe Complete Orders From OERR option [PSO LMOE FINISH] breaks when the\nuser selects to process pending orders via Priority status and when they\nanswer "NO" to the prompt "Do you want to see Medication Profile? Yes//"\nNO. \n \nBelow is a screen capture of the hard error:\n\n
\nThis patch contains two APIs for extracting data from the PRESCRIPTION\n(#52) file. The APIs are in the routine PSOCLINR, the APIs are:\n \nSTAT(PSO) ;Returns Status (#100) external format from Prescription (#52)\n file\nNEPSRX() ;Returns the number of prescriptions in the file\n\n
\n1) This patch, in conjunction with patches from Inpatient Medications and\npatient. Additionally, CPRS users will no longer be locked out of entering\norders for a patient, when orders for that patient are being finished in\nthe Outpatient Pharmacy package.\n \n2) A change has been made in the messaging that takes place when\nprescriptions are released or returned to stock. This change will not\neffect the Outpatient Pharmacy user.\n \n3) This patch fixes a problem when a prescription is Renewed, and the\nprovider renewing the prescription required a cosigner when the\nComputerized Patient Record System (CPRS), will enhance the way that\nprescription that is being renewed was originally entered, but no longer\nrequires a cosigner. The cosigning physician was being carried over to the\nnew prescription, and printing on the Action Profile, even though the\nprovider no longer required a cosigner. This patch will fix this problem.\n \n4) A problem was reported that involves the prescription numbering\nsequence. If a prescription is entered for a controlled substance, then\nthe drug is edited to a non-controlled substance after answering "No" to\nthe "Is this Correct" prompt, then the prescription will still be assigned\na number from the controlled substance sequence of prescription numbers.\nlocking is done at the order level and at the patient level among these\nThis patch corrects this problem.\n \n5) This patch corrects a problem of the Non-Formulary warning printing\nnext to the dispense drug on the order screen in Outpatient Pharmacy, at\ntimes when it is not appropriate to print. This can result from an order\nbeing entered with a dispense drug that has a valid Non-Formulary status,\nthen that drug is edited to a drug that should not have a Non-Formulary\nstatus, but the Non-Formulary indicator still prints next to the dispense\ndrug.\n \npackages. Anytime an order is acted upon in the Outpatient Pharmacy\n6) This patch corrects a problem of a user in CPRS being able to enter a\nrefill request that comes to the Outpatient Pharmacy package, even if the\nrefill request is beyond the expiration date of the prescription.\n \n7) This patch corrects a problem that can occur in the Complete Orders\nfrom OERR [PSO LMOE FINISH] option for sites with multiple CPRS ordering\ninstitutions. At the "Select CPRS ORDERING INSTITUTION" prompt, sometimes\nthe default will not be accepted if the user enters return. The user is\nforced to type in the institution name. This patch corrects the problem.\n \npackage, locks will now take place within the Outpatient Pharmacy package\n8) This patch will bring back the functionality of doing drug interaction\nchecks on Renewals.\n \n9) This patch fixes a problem encountered when finishing orders in\nOutpatient Pharmacy that were entered through CPRS before the day the\norder is finished. These orders were being treated as future fills and\nbeing suspended, since the order had been entered on a previous day\nthrough CPRS. This patch makes a change where these will no longer\nbe seen as future fills, as long as the order is being filled for today.\n \nat that order level, and the order will also be locked in CPRS. A Pharmacy\n10) This patch addresses an issue that occurs when removing\na prescription from a pharmacy hold status. Prior to this patch, this\naction would always generate a label request, regardless of whether or not\nthe last fill of the prescription had been released. This patch makes a\nchange to not print a label when removing a prescription from hold if the\nlast fill of the prescription has been released.\n \n11) When editing the Drug of a prescription, if the new Drug is matched\nto the same Pharmacy Orderable Item, and there are synonyms in the\nPharmacy Orderable Item file (#50.7) that contain numbers in the\nPatient lock has also been created. When actions on orders take place in\nsynonym name, it is possible that after editing the Drug, the\nPharmacy Orderable Item will change to an incorrect Pharmacy Orderable\nItem. This patch corrects the problem.\n \n12) Currently, a prescription that is on Provider Hold should not be\nacted upon through the Outpatient Pharmacy package. If you are entering a\nnew prescription and get a duplicate drug or duplicate class check on\na prescription that is on provider hold, you are currently able\nto discontinue the prescription that is on provider hold. This patch will\nprevent that prescription on provider hold from being discontinued, so the\nOutpatient Pharmacy that could result in a change in the order, all other\nnew prescription entry will not be allowed, since the discontinue action\nis not allowed.\nPharmacy users will be locked out of acting on any orders for that same\n\n
\nThis patch modifies the Outpatient Pharmacy v7.0 application as described\nbelow:\n \n \n1. After release of an ePharmacy Phase 4 patch (PSO*7*287), it was found\nthat the PSOORED6 routine was erring or causing a DIE error due to a\nvariable being killed in a called routine. This patch corrects this\nerror.\n\n
\nThe "stop date" for complex Outpatient prescriptions do not display in \nthe Computerized Patient Record System (CPRS). This patch resolves this \nissue. The resolution implemented by this patch is not retroactive. \nOnly Outpatient prescriptions entered after patch installation will \ndisplay the "stop date" in CPRS.\n\n
\nThis patch has enhancements which extend the capabilities of the Veterans \nactivate unless instructed specifically by the CBO.\n \nThis patch is being released along with PSS*1*139 and IB*2*405. These\npatches can be installed in any order but the full functionality \nfor Nutritional Supplement additions contained within these patches will\nnot be available until all 3 patches are installed.\n \nThis patch modifies the Outpatient Pharmacy v7.0 application as described\nbelow:\n \nHealth Information Systems and Technology Architecture (VistA) electronic \n1. Modifications to change the default answer of (I)gnore on the Reject \nProcessing Screen to (Q)uit which automatically sends the claim rejection \ninformation to the Pharmacy Reject Worklist for new orders, copies, edits \nthat create new orders, and renewal functions. This patch, PSO*7*303, \nincludes the modifications for these functions.\n \n2. Additional software to handle the new "N for Nutritional Supplement\nDEA special handling code added in patch PSS*1*139. This new "N" code\nwill be treated the same as supply items and investigational drugs in\nOutpatient Pharmacy. Copay will not be charged, and third party billing \npharmacy (ePharmacy) billing system.\nfor these type drugs will only occur when the drug is also marked with \n"E" for Electronically Billable. When the drug is not defined to be \nelectronically billable, the ECME Log will reflect drug not billable. \nFor prescriptions where the eligibility changed since the last refill, a \n"PRESCRIPTION QUESTIONS REVIEW NEEDED" MailMan message is sent. The last \nparagraph of this message will be changed to include nutritional drugs:\n \n Supply, nutritional and investigational drugs are not charged a VA\n copay but could be reimbursable by third party insurance.\n \n \n3. For the ePharmacy Medication Profile (VIEW ONLY) [PSO PMP] option,\nflagged pending orders will be notated on the medication profile screen by\nhighlighting the sequence number shown on the left side of the screen. \nNote that the "Flagged by..." information shown once the prescription is\nselected is already present with the PSO*7*225 release.\n \n4. For Tricare Reversal/Resubmit actions sent to ECME with NDC changes,\nthe text for the ECME activity log was too large to fit in the field\nwithout being truncated. The log entry text "Reversal/Re-submit sent"\nhas been abbreviated to "Rev/Resubmit" to ensure the entire NDC is \nAll sites should install this patches regardless of whether or not they \nviewable in the log entry.\nhave been activated for ePharmacy by the Central Business Office (CBO). \nAfter the installation of these patches, the activation status of the \nsite will not be impacted. As before, activation of the ePharmacy \nproduct will require instructions provided by the CBO. Sites are not to \n\n
\nThis patch will fix the issue where the incorrect patient is \nprinted on the label. \n\n
\nThe Pharmacy Prescription Practices V.1.0 package is being retired per\nPSI-07-114. Therefore, calls to the PPP package within Outpatient\nPharmacy V.7.0 need to be removed.\n\n
\n \n \n \nThis patch addresses a subscript error in routine: PSOHLSN\nHD0000000291680 - <SUBSCRIPT>SEGPARX+4^PSOHLSN\n\n
\nASSOCIATED REMEDY:\n==================\nHD220858 - PSI-07-227 - Error Filling Prescriptions in Outpatient Pharmacy\nd HD231034 - Wrong script information\nd HD237297 - HL7 prescription issue\n\n
\nThe FY08 Q4 Enhancement Release includes the following enhancements.\nThis patch adds a new NTE8 segment that has the VA Notice of Privacy\nPractices, IB 10-163 narrative to the content of the laser labels print\nstream. If you are using automated dispensing equipment that relies on\nthe data stream sent to the laser labels port, you have to contact your\nvendor to make adjustments to the trailer page as defined in item #4\nbelow.\n \n1. Automate CPRS Refill Processing\n==================================\nThis patch provides functionality to automatically process refills placed\n \nby the provider via CPRS. A new system parameter, AUTOMATE CPRS REFILLS\nfield (#40.16), has been added to the PHARMACY SYSTEM file (#59.7) by the\nPharmacy Data Management V. 1.0, patch PSS*1*137 to support this\nfunctionality.\n \nPlease refer to patch PSS*1*137 for more details.\n \nThe auto refill process will occur only if the new AUTOMATE CPRS REFILLS\nfield (#40.16) of the PHARMACY SYSTEM file (#59.7) is set to YES and the\nsecurity key, PSOAUTRF, has been assigned to at least one user; otherwise\n1. Automate Computerized Patient Record System V. 1.0 (CPRS) Refill\nthe current process will continue where the orders have to be finished\nmanually. Orders processed automatically will have the refill date\ncalculated by the refill process to the next possible fill date and the\nrouting will be set to Mail.\n \nDuring the auto refill process, if the criteria for refilling fails, then\nthe order will not be processed but will be stored in the PENDING\nOUTPATIENT ORDERS file (#52.41) for manual processing. Also, a MailMan\nmessage, with the reason for not filling the auto refill, will be sent to\nholders of the PSOAUTRF security key. This should be very rare since CPRS\n Processing.\nwill allow refills only if they are refillable.\n \n2. Display of both the Fill Date and the Release Date\n=====================================================\nOn the Patient Medication Profile screen, new functionality was\nimplemented to allow users to have the option of viewing either the FILL\nDATE or the RELEASE DATE information. This is done by using a hidden\nListMan action called RDD to invoke the RELEASE DATE display and will\nremain for that session. Using the RDD action again will display the FILL\nDATE.\n2. Display of both the Fill Date and the Release Date.\n \n3. Duplicate Drugs Message Enhancements\n=======================================\nThis enhancement is related to patient safety issue PSI-07-236 and remedy\nticket RT223633. When a duplicate drug message is displayed, the heading\n"CMOP Status" is currently shown for CMOP drugs only. This heading is\nbeing renamed to "Processing Status" and it will appear on every duplicate\ndrug message along with the release status.\n \n4. Notice of Privacy Practice Reminder on Laser Labels\n3. Duplicate Drugs Message Enhancements.\n======================================================\nWhen the labels are printed for a patient's prescriptions, the\nfollowing narrative will be printed on the trailer page in either English\nor Spanish, depending on the patient's language preference.\n \nThe English version reads as follows.\n \n The VA Notice of Privacy Practices, IB 10-163, which outlines your\n privacy rights, is available online at http://www1.domain.ext/Health/ or you\n may obtain a copy by writing the VHA Privacy Office (19F2), 810 Vermont\n4. Notice of Privacy Practice Reminder on Laser Labels.\n Avenue NW, Washington DC 20420.\n \nThe Spanish language translation for the Privacy Notification reads as\nfollows.\n \n La Notificacion relacionada con las Politicas de Privacidad del\n Departamento de Asuntos del Veterano, IB-10-163, contiene los\n detalles acerca de sus derechos de privacidad y esta disponible\n electronicamente en la siguiente direccion:\n http://www1.domain.ext/Health/. Usted tambien puede conseguir una copia\n \n escribiendo a la Oficina de Privacidad del Departamento de Asuntos de\n Salud del Veterano, (19F2), 810 Vermont Avenue NW, Washington, DC 20420.\n***** NOTE TO SITES USING AUTOMATED FILLING EQUIPMENT *****\n\n
\nDThis patch has enhancements which extend the capabilities of the Veterans\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*289\nThe system will not hold a prescription for 3/4 days supply when:\n \n - the previous fill was not ECME billable\n - the Rx is flagged for SC or EI\n - the DEA special Handling code is non billable (i.e. has M or 0 \n (zero) or (I, S, N, and/or 9)) without and E.\n - the Rx is a zero fill on a renewal\n - the patient does not currently have insurance\n \n6. A modification was made to PRESCRIPTION file (#52), REJECT INFO \n INTEGRATED BILLING (IB) V. 2.0 IB*2*384\nsub-file (#52.25), CLARIFICATION CODE field (#24). This was a set of codes\nfield. It is now a pointer to file #9002313.25 (BPS NCPDP CLARIFICATION\nCODE). A post install routine will go through the reject info subfile and\nconvert the old set of code values to the appropriate new pointer values.\nThe post install will send a mail message to the person installing the\nbuild which details the affected rejected prescriptions. The 'Submit\nClarif. Code' protocol [PSO REJECT DISPLAY CLARIFICATION CODE] has been\naltered to use the new pointer value.\n \n7. The 'Edit NDC and DAW Code of Discontinued/Expired Prescriptions' \n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*7\nfunctionality introduced in PSO*7.0*281 has been extended to also allow \nedits of prescriptions with a status of DISCONTINUED BY PROVIDER and \nDISCONTINUED (EDIT).\n \n8. New functionality was added to create a nightly background mail \nmessage regarding open/unresolved rejects on the reject worklist. The \n'Third Party Payer Rejects - Nightly Message' option [PSO REJECTS \nBACKGROUND MESSAGE] will be queued to run every 24 hours by the post \ninstall routine. This option is intended to be a stand alone option and \nshould not be placed on any menu. The message will be delivered to the \n \n'PSO REJECTS BACKGROUND MESSAGE' mailgroup; this mailgroup should be \npopulated with appropriate ePharmacy users to receive the information. \nMail messages are generated for each division. Sites may alter EPHARMACY\nSITE PARAMETERS file (#52.86) REJECT WORKLIST DAYS field (#4) for each \ndivision using the ePharmacy Site Parameters option [PSO EPHARM SITE \nPARAMETERS] of the ePharmacy Menu. If no sites are defined in the \nEPHARMACY SITE PARAMETERS file (#52.86), no message will be generated. \nThis parameter may be defined to be 1 to 30 days that an uncommented\nreject can remain on the reject worklist without being included in the\nnightly reject worklist alert mail message. The following are the\nThe last three patches (PSO*7*289, IB*2*384 and BPS*1*7) will be released \ncriteria for a reject to be included in the mail message:\n \n a. The prescription is active, suspensed, expired, or on hold.\n b. The prescription is unreleased.\n c. The claim has been on the Reject Worklist for more days than the\n value in the REJECT WORKLIST DAYS field for the division.\n d. The claim has no comments added within the date range.\n \n9. New functionality was added to allow NDC validation of third party\npayable prescriptions by pharmacy technicians. Current functionality\nin the Kernel Installation and Distribution System (KIDS) multi-build \nrequires a pharmacist to perform this task. In addition, for the\nPRESCRIPTION file(#52) and the REFILL sub-file (#52.1), the DATE NDC\nVALIDATED field (#83) and NDC VALIDATED BY field (#84) will be captured\nwhen the NDC is validated for a prescription or refill; this validation\ninformation will be displayed when prescriptions are released; if the NDCs\nhave not been validated, that information will be displayed instead. The\n'NDC Validation' option [PSO NDC VALIDATE] has been added to the ePharmacy\nMenu for use by technicians. The option will work as follows:\n \n a. The technician will be prompted to scan or enter a prescription \ndistribution BPS PSO IB BUNDLE 3.0. Patches PSX*2*65 and PSS*1*131 will \n number. An '^' may be entered to halt the option.\n b. The system will evaluate the Rx. If the Rx NDC has already been \n validated, the technician will be prompted if they wish to\n revalidate. If the answer is yes, the technician will be allowed to\n proceed. If the answer is no, the technician will be returned to\n the select a prescription prompt.\n c. If the Rx is CMOP, external interface or released, the user will\n not be allowed to verify the Rx.\n d. The system will display information about the Rx, notate that the\n Rx has not been previously verified and will prompt for PRODUCT \nbe released as stand-alone patches. Since there is an implementation \n NDC. A valid PRODUCT NDC must be entered for this prompt. Valid\n PRODUCT NDC's are those defined for the drug in Drug file (#50) as\n an NDC of a synonym or the default NDC.\n e. The system will compare the Rx NDC to the PRODUCT NDC submitted on\n the ePharmacy claim. If the NDCs do not match, the system will\n reverse and resubmit a third party claim with the new NDC and \n store the new NDC on the fill.\n f. If the prescription is defined as TRICARE and is not payable, the \n system will display an appropriate message and the technician will \n be returned to the select a prescription prompt.\ndependency between the multi-build distribution and the stand-alone \n g. If the prescription is defined as TRICARE and the reversed claim \n returns not payable, the system will display an appropriate \n message and the technician will be returned to the select a\n prescription prompt.\n h. Otherwise, the system will update the NDC validation fields for the\n Rx/Fill, and the technician will be returned to the select a\n prescription prompt.\n \n10. The RES - Resubmit Claim action was added to the Reject Information\n(TRICARE) screen of the Third Party Payer Rejects - Worklist [PSO REJECTS\npatches, PSX*2*65 and PSS*1*131 must be installed prior to the \nWORKLIST] option.\n \n11. The following functionality will work only if the REGISTRATION\npackage V.5.3 patch DG*5.3*688 that introduces the COUNTRY field to the\nPATIENT file (#2) is installed:\n \n When using the Print from Suspense File [PSO PNDLBL] option, if the\n routing is MAIL and the address is Foreign, it will be treated just\n like the BAD ADDRESS INDICATOR or DO NOT MAIL order where:\n \nHealth Information Systems and Technology Architecture (VistA) electronic \ninstallation of the multi-build. For more specific instructions please \n a. The prescription will not be sent to the automated filling equipment\n and/or to the label printer. The fill will remain on suspense until\n it is pulled early, the routing is changed to window, or the address\n is changed.\n \n b. For the first time attempt to print from suspense, an entry will be\n added to the activity log and a MailMan message will be generated to\n the user who queued the job to print from suspense and the members\n of the PSO EXTERNAL DISPENSE ALERTS mail group.\n \nrefer to the installation steps provided in each of the patches.\n12. When the NDC changes during auto-release of the prescription for CMOP\nor OPAI fills, the fill date on the fill be updated to become the same as\nthe release date. An entry will be made in the activity log for the fill \nto denote the changed date.\n \nThis patch modifies the Outpatient Pharmacy v7.0 application as described\nbelow:\n \n1. A modification was made to prevent users from entering a suspense date\nthat is greater than the fill date plus 90 days. Dates where the fill\ndate plus 90 days is greater than the expiration date will not be allowed.\n \npharmacy (ePharmacy) billing system. Below is a list of all the \n2. Functionality to allow non-DUR/RTS reject to be placed on Third Party \nPayer Rejects - Worklist [PSO REJECTS WORKLIST] option was added. To \naccomplish this the following additions were made:\n \n a. A new EPHARMACY SITE PARAMETERS FILE (#52.86) was added to store\n ePharmacy specific parameters by division. Along with this file, \n a new EPHARMACY SITE PARAMETERS [PSO ePHARM SITE PARAMATERS]\n option was added for entry/edit of parameters. Regardless of any\n parameters defined in this new file, Refill-Too-Soon (RTS), Drug\n Utilization Review(DUR) and Tricare rejects will always be placed\napplications involved in this project along with their patch number:\n on the Pharmacy Reject Worklist.\n \n Sites will have the ability to select to allow all third party \n rejects to pass to the the Third Party Payer Rejects - Worklist\n which is also referred to as the Pharmacy Reject Worklist or they\n can choose to specify individual reject codes. Individual third\n party reject codes can be defined to be automatically placed on\n the worklist or defined to require OPECC intervention. If the site\n chooses to allow all rejects to be placed on the worklist,\n individual codes are overridden but not deleted from the file.\n \n \n b. For display of non-DUR/RTS rejects for the Third Party Payer\n Rejects - Worklist [PSO REJECTS WORKLIST] option, rejects passed\n via OPECC manual intervention will be denoted in the comment\n section of the Reject Information screen as:\n \n - JUN 09, 2008@14:04:18 - Transferred by OPECC. (user,name)\n \n \n Rejects passed automatically will be denoted in the comments \n APPLICATION/VERSION PATCH\n section of the Reject Information Screen as \n \n - JUN 09, 2008@16:00:09 - Automatically transferred due to override\n for reject code. (user,name)\n \n All rejects other than Refill-Too-Soon, DUR, and Tricare will be \n displayed at the end of the listing under "OTHER REJECTS"\n header. The "OTHER REJECTS" header will be displayed regardless of\n whether the GI - Group Insurance action is toggled on or off. \n \n --------------------------------------------------------------\n Non-DUR/RTS rejections will be resolved with the existing\n functionality and will be resubmitted to ECME in the same manner\n as DUR/RTS rejections.\n \n3. A modification was made to not allow a claim to be reversed through \nECME for an unreleased CMOP fill when the prescription/fill is \ndiscontinued. If the fill is either a CMOP released or Non-CMOP released \nfill the reversal will be performed. Because the software already \nperforms a reversal for unsuccessful/not dispensed claims, no changes are \nneeded for reversing discontinued non-dispensed fills. Also, no changes \n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*65\nare needed when the NDC from CMOP differs from the NDC on the claim \nbecause this function is already performed by existing software.\n \n4. New functionality was added to prevent prescriptions from being \nfilled/sent to CMOP when a host processing error occurs when a claim is \nsubmitted through ECME. The host processing errors are identified by \nreject codes M6, M8, NN, and 99. The following conditions apply when this \nscenario occurs.\n \n a. The transmission of the Rx/fill will be delayed 1 day in hopes\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*131\n that the host processing issues will be resolved.\n b. An activity log entry will be defined to state the date/time \n along with a comment stating that the Rx/fill was left in suspense\n hold due to a host processing error.\n c. This added functionality does not include the Pull Early from \n Suspense function.\n \n5. New functionality was added to the Print from Suspense File [PSO \nPNDLBL] option to prevent ePharmacy prescriptions from being pulled early\nfrom suspense until 3/4 of the days supply of the Rx/fill has elapsed. \n\n
\nREMOVE TEMPORARY MENU OPTIONS\n\n
\n1. This patch fixes a problem that can occur when editing a prescription\nMfg______Exp______ will print on the labels after the quantity and\ndispense unit. The patch makes a change to also look at the COMMUNITY\nNURSING HOME field (#40) of the PHARMACY PATIENT file (#55), so if a\npatient is flagged as YES in either of these 2 fields, the text\nMfg_____Exp_____, will print on the labels.\n \n3. This patch fixes a problem that can occur when a pending renewal order\nfrom Computerized Patient Record System (CPRS) is discontinued by Pharmacy\nwithout renewing the original order. If this occurs, and that same\noriginal order is renewed again in CPRS, the user in CPRS will receive a\nthat is suspended for local filling. If the patient is flagged as DO NOT\nmessage saying that it is a duplicate renewal request, and will not be\nallowed to process the renewal, even though the original renewal was\ndiscontinued. This patch will allow that subsequent renewal to be sent to\npharmacy for completion. A post-init routine in this build will run that\nwill kill an invalid cross reference in the PENDING OUTPATIENT ORDERS file\n(#52.41). This will allow for the functionality to be in place for all\nprevious orders.\n \n4. This patch fixes a problem of "NKA" sometimes printing when it\nshouldn't in the Allergy section of the labels, and in the HL7 message to\nMAIL in the MAIL field (#.03) of the PHARMACY PATIENT file (#55), and\nexternal applications.\n \n5. A renewal problem can occur when renewing a prescription that has been\ncanceled by the Autocancel Rx's on Admission [PSO AUTOCANCEL1] option. If\nthat canceled prescription was never filled, then the new prescription\ncould be suspended too far in the future. This patch corrects the problem.\n \n6. This patch fixes an undefined error that can occur in the Patient\nPrescription Processing [PSO LM BACKDOOR ORDERS] option, when viewing\nthe medication profile. The error would only occur for a drug name that\nthat suspended prescription is edited, it can possibly be removed from\nis greater than 40 characters in length, which is prohibited by the\nnationally exported data dictionaries.\n \n7. This patch fixes a problem of a prescription label printing for a\nrefill when it should not print. If a refill is processed for a\nprescription and the label is queued to print, and that refill is\ndeleted before the label prints, a label will print for the\nlast fill documented in the prescription. This patch changes the\nfunctionality to not print a label for a prescription if the refill\nassociated with the label request is deleted before the label prints.\nlocal suspense and suspended for Consolidated Mail Outpatient Pharmacy\n(CMOP), even though the patient is flagged as DO NOT MAIL.\n \n2. On Outpatient Pharmacy labels, if a patient is flagged as YES in\nthe CNH CURRENT field (#148) of the PATIENT file (#2), then the text\n\n
\nThe following issues are addressed in this patch:\nis updated for a patient, an entry is queued for retransmission.\n \n \n2. During internal testing, it was discovered that the FIRST SERVICE DATE\nfield (#.07) and the ACTUAL/HISTORICAL FLAG field (#.08) were not being\nset appropriately when the user exited out of label print. This patch\ncorrects this problem.\n1. This patch addresses a request which support the Pharmacy Benefits\nManagement (PBM) Extracts Enhancement #3 project. In order to allow the\nretransmission of only those patients who have had demographic updates,\nOutpatient Pharmacy V. 7.0, Inpatient Medications V. 5.0, Registration\nV. 5.3 and Pharmacy Data Management V. 1.0 were modified to build an entry\nfor re-transmission in PBM PATIENT DEMOGRAPHICS File #59.9.\n \nWhen the FIRST SERVICE DATE field (#.07) in the PHARMACY PATIENT file #55\n\n
\nPSO*7*266 will correct the following remedy tickets\nHD153822 90 day supply with 11 refills allowed.\n Dupe: HD186337 Drug Change And No Refills.\nHD129050 Allowable Refills\nHD198754 BINGO BOARD DISPLAYING INCORRECT RX #\nHD120910 Incorrect Suspend Date \n\n
\nThis patch will fix the issue where the Lot # is carried over\nis set to Today instead of the same date as the original refill.\nto the new prescription during a renewal.\nIt will also fix an issue with the Refill Date when a prescription\nis suspended.\nIf a user creates a prescription with a Fill Date of Today and then a \nrefill is requested for Today, the prescription is put into suspense for\na future date.\nIf the refill is deleted and then re-added without exiting the OP\nMedication screen, the suspense date for the newly requested refill\n\n
\nThe FY09 Q2 Enhancement Release includes the following.\n if a patient has remote prescription(s), then the user will be prompted\n FOR PATTESTING FOR PATIENT TESTING FOR PATTESTING\n FOR PATIENTENT INTRUCT ION ON SIG1 TESTING FOR\n PATIENT INTRUCTION ON SIG1 TESTING FOR PATIENT\n REPLACE IENT WITH IENT TESTING FOR PATIENT\n INTRUCTION ON SIG1 TESTING FOR PATI\n PROVIDER: PSOPROVIDER,ONE\n \n5. In the Pull Early from Suspense [PSO PNDRX] and Print from Suspense\n File [PSO PNDLBL] options, if the patient has remote prescriptions, then\n the text "THIS PATIENT HAS PRESCRIPTIONS AT OTHER FACILITIES" will be\n with the following question.\n displayed on the report as shown in the following example.\n \n PRESCRIPTION PROFILE AS OF 12/30/2008\n \n NAME: PSOPATIENT,ONE\n ID# : 000-00-0000\n \n THIS PATIENT HAS PRESCRIPTIONS AT OTHER FACILITIES\n \n PHARMACIST: __________________ DATE: ________\n \n \n \n \n6. Three new protocols were added: PSO RDI VISITS MENU, PSO RDI BOTH, and\n PSO RDI REMOTE.\n \n7. Two new list templates were added: PSO RDI VISITS and PSO RDI VISITS\n DETAIL.\n\n\n REMOTE PRESCRIPTIONS AVAILABLE!\n\n Display Remote Data? N//\n \n If the response is "No", then there are no changes to the existing\n functionality. If the response is "Yes" then it provides a new screen\n to view the remote data as shown in the following example.\n \n \nRemote Facilities Visited Dec 30, 2008@17:26:47 Page: 1 of 1\n \nPatient: PSOPATIENT,ONE (000-00-0000) DOB: 01/02/1967\n \n Station\n HDR CHEYENNE\n \n \n \n Enter ?? for more actions\nThis patch provides the ability to view a patient's remote prescription\nDR Display Remote Pharmacy Data DB Display Both Pharmacy Data\nAction:Quit//DR\n \nMedication Profile - Remote Dec 30, 2008@17:29:43 Page: 1 of 2\n \nPatient: PSOPATIENT,ONE (000-00-0000) DOB: 01/02/1967\n \n RX# DRUG ST QTY ISSUED LAST FILLED\nHDR CHEYENNE\n712885 AMOXICILLIN TRIHYDRATE 250MG CAP A 90 11/06/08 11/06/08\ndata within Outpatient Pharmacy V. 7.0 using the Remote Data\n SIG: TAKE ONE CAPSULE BY MOUTH THREE TIMES A DAY\n PROVIDER: PSOPROVIDER,TEN\n712886 DILTIAZEM (INWOOD) 240MG CAP,SA A 30 11/28/08 11/28/08\n SIG: TAKE ONE CAPSULE BY MOUTH EVERY DAY\n PROVIDER: PSOPROVIDER,TEN\n712888 LABETALOL HCL 200MG TAB A 60 12/30/08 12/30/08\n SIG: TAKE ONE TABLET BY MOUTH TWICE A DAY\n PROVIDER: PSOPROVIDER,TEN\n712887 SIMVASTATIN 20MG TAB A 15 12/09/08 12/09/08\n SIG: TAKE ONE-HALF TABLET BY MOUTH EVERY EVENING TESTING\nInteroperability (RDI) interface to retrieve data from the Health Data\n FOR PATTESTING FOR PATIENT TESTING FOR PATTESTING\n FOR PATIENTENT INTRUCTION ON SIG1 TESTING FOR\n PATIENT INTRUCTION ON SIG1 TESTING FOR PATIENT\n REPLACE IENT WITH IENT TESTING FOR PATIENT\n+ Enter ?? for more actions\n \nSelect Action:Next Screen//\n \n2. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,\n on the Patient Medication Profile screen, a new hidden ListMan action\nRepository (HDR).\n called DR [DISPLAY REMOTE] was added to display a patient's remote\n prescriptions.\n \n3. In the Complete Orders from OERR [PSO LMOE FINISH] option, if a user\n answer "Yes" to the prompt 'Do you want to see Medication Profile?',\n then if a patient has remote prescription(s), the user will be\n prompted with the following question.\n \n REMOTE PRESCRIPTIONS AVAILABLE!\n Display Remote Data? N//\n \n \n If the response is "No", then there are no changes to the existing\n functionality. If the response is "Yes", then it provides a new screen\n as shown in item #1.\n \n4. In the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] COLUMN\n option, if a patient has remote prescription(s) then they are printed\n at the end of the report as shown in the following example.\n \n MEDICATION PROFILE FROM OTHER VAMC(s) Page: 4\nThe following changes were made.\n Date Printed: 12/22/2008\n \nPatient: PSOPATIENT,ONE DOB: 05/01/1955\n===============================================================================\n \n RX # DRUG ST QTY ISSUED LAST\nFILLED\n===============================================================================\nHDR CHEYENNE\n \n1. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,\n712885 AMOXICILLIN TRIHYDRATE 250MG CAP A 90 11/06/08 11/06/08\n SIG: TAKE ONE CAPSULE BY MOUTH THREE TIMES A DAY\n PROVIDER: PSOPROVIDER,ONE\n \n712886 DILTIAZEM (INWOOD) 240MG CAP,SA A 30 11/28/08 11/28/08\n SIG: TAKE ONE CAPSULE BY MOUTH EVERY DAY\n PROVIDER: PSOPROVIDER,ONE\n \n712887 SIMVASTATIN 20MG TAB A 15 12/09/08 12/09/08\n SIG: TAKE ONE-HALF TABLET BY MOUTH EVERY EVENING TESTING\n\n
\n1. Undefined error in routine PSOATRF.\n2. DUZ variable being reset.\n3. Replace direct call to data dictionary with Pharmacy API\n\n
\nThe FY09 Q1 Enhancement Release is related to PSI-07-090 (PSPO #543) and\n (addressed in patch PSN*4*181)\n Complete Orders from OERR [PSO LMOE FINISH]\n Pull Early from Suspense [PSO PNDRX]\n Print from Suspense File [PSO PNDLBL]\n - 5 Standard Print from Suspense\n Reprint a non-voided Outpatient Rx Label [PSO SCRIPTALK REPRINT\n VISTA LB] \n Queue ScripTalk Label by Barcode [PSO SCRIPTALK MANUAL INTERNAL]\n Queue ScripTalk Label by Rx# [PSO SCRIPTALK MANUAL EXTERNAL] \n \nRemedy Ticket #189923. The Social Security Number (SSN) was removed from\nAdditionally, the ability to lookup by prescription number or wand a\nbarcode with the prescription was added to the patient lookup prompt on\nthe following options.\n Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n Medication Profile [PSO P]\n Rx (Prescriptions) [PSO RX]\n Update Patient Record [PSO PAT]\n Manual Print of Multi-Rx Forms [PSO LM MULTI-RX PRINT]\n ScripTalk Patient Enter/Edit [PSO SCRIPTALK PATIENT ENROLL]\n Patient Address Changes Report [PSO ADDRESS CHANGE REPORT]\nthe print out given to the patient from the following options.\n List Prescriptions Not Mailed [PSO BAI NOT MAILED]\n Non-VA Meds Usage Report [PSO NON-VA MEDS USAGE REPORT]\n Enter New Patient [PSO BINGO NEW PATIENT]\n Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE]\n Poly Pharmacy Report [PSOPOLY].\n \nThe help text for patient lookup was modified and will display the\nfollowing.\n Enter the prescription number prefixed by a # (ex. #XXXXXXX) or\n Wand the barcode of the prescription. The format of the barcode is\n Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE]\n NNN-NNNNNNN where the first 3 digits are your station number.\n - OR -\n Answer with PATIENT NAME, or SOCIAL SECURITY NUMBER, or last 4 digits\n of SOCIAL SECURITY NUMBER, or first initial of last name with last 4\n digits of SOCIAL SECURITY NUMBER\n Do you want the entire NNNNNNNN-Entry PATIENT List?\n Medication Profile [PSO P]\n Printing/Reprinting prescription labels using these options:\n Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n - ListMan hidden action (RP) - Reprint (OP)\n - ListMan hidden action (OTH) - MI Print Medication Instructions\n\n
\nThis patch will fix an error that is caused by a long provider comment \n(more than 32 characters with no spaces) that is entered in CPRS and\ncopied when the pending order is processed in Outpatient Pharmacy.\n\n
\nThis patch will resolve the issue where another patient's \nprescription is printing on the label log.\n\n
\nCARRIAGE RETURNS IN HL7 MESSAGES SENT TO HDR\n\n
\nThe FY09 Q3 Enhancement Release includes the following.\n"No Allergy Assessment - Do you want to duplicate Intervention? Yes//"\n \nIf the answer is "No," then it will prompt for a new intervention.\n \nIf the answer is "Yes," then it will display the last intervention\nentered. The following is an example.\n \nINTERVENTION DATE: DEC 11, 2008 PATIENT: PSOPAT,NAME\nPROVIDER: PSOPROV, NAME PHARMACIST: PSOPHARM, NAME\nDRUG: "current order drug name" INSTITUTED BY: PHARMACY\n \nINTERVENTION: ALLERGY RECOMMENDATION: OTHER\nORIGINATING PACKAGE: OUTPATIENT DIVISION: OKLAHOMA CITY VAMC\n \nWould you like to edit this Intervention? No//\n \nIf "No," then the system accepts the intervention and continues.\nIf "Yes," then the system allows editing of the intervention.\n \n \n2. PSI-07-181 (PSPO# 865) - Remedy Ticket # HD208961\n1. PSI-07-134 (PSPO #771) - Remedy Ticket # HD200301/HD217962\n \nA prescription's strength was changed in Computerized Patient Record\nSystem V. 1.0 (CPRS) creating a new Rx. The original Rx had been\ntransmitted to Consolidated Mail Outpatient Pharmacy (CMOP) on the\nprevious day. When finishing, the pharmacist missed the previous day's\ntransmission to CMOP of the original prescription. Both Rxs were mailed\nto the patient in the same package from the CMOP.\n \nWhen a CMOP prescription with a status of Transmitted or Retransmitted is\ndiscontinued by a background process to the Outpatient Pharmacy options,\n \ne.g. CPRS or Registration V. 5.3 packages, then an email notifying that a\nprescription was just discontinued for that Rx will be sent to the new PSX\nEXTERNAL DISPENSE ALERTS mail group created by patch PSX*2*68 (see\nPSX*2*68 patch description for details). If no recipients are defined in\nthe new mail group, then it will be sent to PSXCMOPMGR key holders. The\nemail alert will inform the group that the CMOP status for the Rx just\ndiscontinued was either Transmitted or Retransmitted as seen in the\nexample below.\n \n Subj: TROY - DC Alert on CMOP Rx 123456789 TRANSMITTED [#90494]\nIn Outpatient Pharmacy during order entry when there is no allergy\n 03/03/09@17:37 8 lines\n From: POSTMASTER In 'IN' basket. Page 1 *New*\n ------------------------------------------------------------------------\n Rx #: 123456789 Fill: 0\n Patient: OUTPATIENT,DCONE (6660)\n Drug: TAMOXIFEN CITRATE 10MG TABS\n Rx Status: DISCONTINUED BY PROVIDER\n Processing Status: TRANSMITTED to CMOP on 02/27/09\n Provider: OPPROVIDER, PROV\n \nassessment on file for a patient, the user will be given the ability to\n ******** Please contact CMOP or take appropriate action ********\n \n Enter message action (in IN basket): Ignore//\n ------------------------------------------------------------------------\n \nWhen a CMOP prescription with a status of Transmitted or Retransmitted is\ndiscontinued by a foreground Pharmacy process due to a duplicate drug\nscenario that would trigger the duplicate to be discontinued, then the\nProcessing Status field of the duplicate drug message is highlighted to\nalert the user. Below is an example.\nduplicate the allergy intervention data filed for the last drug.\n \n ------------------------------------------------------------------------\n Duplicate Drug A AND Z OINTMENT in Prescription: 123456789\n \n Status: Active Issued: 03/03/09\n<<BOLD>> Processing Status: Transmitted to CMOP on 03/04/09 <<BOLD>>\n SIG: APPLY 1 TUBE TO AFFECTED AREA TWICE A DAY\n QTY: 1 # of refills: 5\n Provider: OPPROVIDER, PROV Refills remaining: 5\n Last filled on: 03/04/09\nIn order to provide this functionality, during subsequent allergy\n Days Supply: 5\n ------------------------------------------------------------------------\n \nDiscontinue RX # 123456789?\nintervention, this patch will now prompt\n\n
\n1) E3R #12579: If an edit is done on a pending order, which results in the\npharmacist. If the Verification field (#.12) is set to no the pharmacy tech\nwill not be able to finish medication orders from CPRS. \n \n3) E3R #10287: This E3R request was to move the actual discontinuation of a\nprescription when a duplicate drug or class order check occurs.\nPrescriptions will no longer be discontinued when the user says yes to\ndiscontinue duplicate drugs or drug classes during new order entry but when\nthe user answers yes to the prescription is correct. \n \n4) Modified software to allow medication orders put on hold through CPRS to\ncreation of a new order, the following text will be automatically entered in\nbe discontinued by Outpatient Pharmacy. \n \n5) E3R #11810: The name of the printer device shall be displayed at the\nlabel prompt along with an additional action of 'CHANGE PRINTER'. The same \nfunctionality as provided by the Change Label Printer [PSO CHANGE PRINTER] \noption will be used. \n \n6) E3R #11658: The existence of a release date shall be used to determine \nwhether the fill date for the original or refill is deleted or retained. If\nthe original fill for a prescription has been released, the fill date will\nthe REMARKS field (#12) of the PRESCRIPTION file (#52), "CPRS Order #nnnn\nnot be deleted when put on hold. The fill date will be shown as the last\nfill date. If the original fill has not been released the current\nfunctionality will be retained and the fill date deleted. The same will hold\ntrue for refills. If the last refill has been released when a prescription\nis placed on hold, that fill shall be retained as the last fill. If the last\nrefill has not been released, the prior fill date will be used. \n \n7) E3R #11294: The speed renewing functionality will be modified to: \n a. Remove the DAYS SUPPLY and # of Refill prompts from the speed renew \nprocess. \nEdited." \n b. The original Rx days supply, # of refills and quantity values will be\nused as defaults for the prescriptions renewed through the SPEED RENEW\nactions. \n \n8) This patch corrects a problem where provider comment from a finished \nprescription medication order could be carried over to a subsequent \nprescription medication order. \n \n9) E3R # 11309: There is a future development project that involves both \nPharmacy and CPRS medication ordering that should address the inaccurate \n \ncalculation of the days supply. In the meantime, in order to help determine\nthe appropriate value for the DAYS SUPPLY field (#8) and to somewhat help \ndistinguish what was entered by the provider versus pharmacy software\ndefaults, pharmacy software will be modified to show the number of refills\nentered by the provider. Below the number of refills prompt displayed on the\nscreen when finishing an order a statement such as (11 refills ordered by\nprovider) will be also displayed. \n \n10) A problem was reported when finishing orders by Clinic or Clinic Sort\nGroup in the Complete Orders from OERR [PSO LMOE FINISH] option. If a\n2) This patch corrects a problem that allows pharmacy technicians to finish\npatient has a pending order for the Clinic or Clinic Sort Group chosen, and\nthat order is discontinued, the Patient Information screen would still\nappear for that patient, even though there are no orders to finish. This\npatch resolves the problem.\n \n11) This patch corrects a potential problem of duplicate prescriptions. The \nproblem can occur when variables are not cleaned up preventing duplicate\norder checks from occurring. \n \n12) Corrected a problem when a duplicate drug class has been entered and\nprescription medication orders from Computerize Patient Record System (CPRS).\nthe other duplicate has been put on provider hold. User is not prompted to\ndiscontinue provider held prescription. \n \n13) E3R #12827: This E3R request that only numeric quantities be allowed\nwhen finishing orders from CPRS. \n \n14) E3R 12850: This E3R requests that functionality be added to allow the\ninactivation of outpatient divisions. A new field, INACTIVE DATE (#2004),\nwill be used to inactive outpatient divisions in the OUTPATIENT SITE file\n(#59). \nThe problem was that if a site did not have the site parameter Verification\n \n15) A new field, DAYS TO PULL SUSPENDED CS CMOP field (#3.1), in the\nOUTPATIENT SITE file (#59) will be installed with patch. This field will be\nused with future CMOP functionality. \n \n16) This patch corrects a possible null subscript error when marking\nnon-verified prescriptions as deleted.\n \n17) This patch corrects a possible subscript error when finishing orders\nfrom CPRS.\nfield (#.12) set to yes, the prescription label printed without review by a\n\n
\nIn the Batch Barcode option a non-pharmacist can renew a prescription \nwithout a pharmacist review. \nThe Refill option works fine.\n\n
\nPROBLEMS WITH PSO INTERNET REFILL REPORT\n\n
\nThe FY10 Q1 Enhancement Release includes the following.\n b. At the prompt, "Select By: (PA/RT/PR/CL/FL/E): PATIENT//", the help\n text "FL FLAG" was changed to "FL FLAGGED".\n \n2. PSPO #1101 - Remedy Ticket #275487\n The following enhancements were made to the prescription laser label.\n a. The current title "Additional Warning Labels" that is printed at\n the top of the PMI section was renamed to "Additional Warnings".\n \n b. If the warning label is lengthy, requiring more than the four\n provided lines, the label is truncated so the text "... See printed\n \n Additional Warnings." can be added to the end of the fourth line.\n \n c. The truncated warning label and its code are printed in their\n entirety at the top of the PMI section under the "Additional\n Warnings" section.\n \n3. Remedy Ticket #345084\n The warning message "<There are ## flagged orders for INSTITUTION>" is not\n displayed when there is only one associated CPRS ordering institution\n with an outpatient site. Routine PSOORFI2 was corrected to fix this\n1. PSPO #1167\n problem.\n\n The following enhancements were made for the Flagged Pending Orders.\n a. When using the Complete Orders from OERR [PSO LMOE FINISH] option,\n the message "<There are ## flagged orders for INSTITUTION>" is\n displayed in reverse video to alert the user that there are\n flagged pending orders.\n \n\n
\nThis patch will modify the dispensing machine releasing so \nthe Message Server ID field (#10) of the Pharmacy External \nInterface file (#52.51) does not get overwritten for previous \nfills with the latest Message Server Id.\n\n
\nThis patch will correct the following issues\n \n \nHD0000000206768 - Activity Log - Sig Edits\nHD0000000219618 - Rx Fill Date Missing\nHD0000000303117 - 2 "Sorry bout that. $ZERROR=" error message\n\n
\nThis patch will resolve the issue where the pharmacist is kicked out of \nthe system after they flag pending orders from a list of orders. Added \nto this is a fix for the Ignored Rejects Report [PSO IGNORED REJECTS \nREPORT], where an error occurs if only one patient is selected in the \nsorting option.\n\n
\nThis patch will resolve the Patient Safety issue (PSPO-1424)\nwhere CMOP prescriptions are not suspending.\n\n
\nA duplicate NTE 8 was inadvertently created via patch PSO*7.0*305 to add \nthe VA Notice of Privacy Practices.\nIf the patient has other language preference then the Spanish patient \ninstructions are already being sent in the\nNTE 8 segment.\n\n
\nThis patch resolves an UNDEFINED error in routine PSO52PAI. \nThis error occurred while users were loading IB patch IB*2*400.\nThe error resulted from processing invalid ePharmacy data in\nthe Pharmacy file (#52).\n\n
\nThis patch will fix the issue where multiple labels are printed.\n\n
\n 1. This patch corrects the problems with the Cost Management Cost compile\n patch as the print template is modified to accommodate this new piece.\n \n 3. This patch fixes a possible undefined variable error that may occur\n during Bingo Board Display.\n \n 4. This patch fixes a possible stack overflow error of a local variable\n array by using the ^TMP global.\n \n 5. This patch fixes a problem where patients were not being registered\n completely into the Clozapine program.\n that was enhanced in PSO*7*20. The nightly cost compile job was\n \n 6. In the Monthly Rx Cost Compilation [PSO COSTMONTH] option, "the AL"\n cross reference node is used for accumulating cost related information.\n There are times this node has more than one record logged for the same\n date and time. This patch ensures that the cost compile routine does not\n skip any of the logged records.\n \n 7. In the Print Bingo Board Wait Time [PSO BINGO REPORT WAIT TIME]\n option, it was reported that the wait time for prescriptions filled at\n 10:00am or released at 10:00am were showing very high wait time. This\n calculating the averages incorrectly.\n patch corrects this problem by fixing the trailing zeroes to the\n canonical value that is returned from the Fileman API call NOW^%DTC.\n \n 8. In the Print Bingo Board Statistics [PSO BINGO REPORT PRINT] option,\n it was reported that the divisions total page is generated when one or a\n range of divisions are selected, but does not generate the total page\n when all divisions are selected. This patch fixes this problem.\n \n 2. In Drug Costs by Division [PSO COST BY DIVISION], this patch fixes the\n REQUESTS column that was showing the same figure for all divisions (which\n was the total patient count of the pharmacy), instead of breakdown by\n divisions by introducing a new piece in File# 50.9006.\n The sort and print templates PSO COST STAT, are also sent out with this\n\n
\nThe Clinical Reminders Order Check project will introduce the\n ARRAY("ISSUE DATE")=ISSUE DATE field (#1)\n ARRAY("PROVIDER")=PROVIDER field (#4) (internal and external format)\n ARRAY("CLINIC")=CLINIC field (#5) (internal and external format)\n ARRAY("DISPENSE DRUG")=DRUG field (#6) (internal and external format)\n ARRAY("PHARMACIST")=PHARMACIST field (#23) (added external format)\n ARRAY("LAST DISPENSED DATE")=LAST DISPENSED DATE field (#101)\n ARRAY("QTY")=QTY field (#7)\n \nFrom the REFILL sub-file (#52.1):\n ARRAY("PHARMACIST")=PHARMACIST NAME field (#4) (added external format)\nfunctionality for a site to create order checks using Clinical Reminder\n ARRAY("QTY")=QTY field (#1)\n \nFrom the PARTIAL DATE sub-file (#52.2):\n ARRAY("PHARMACIST")=PHARMACIST NAME field (#.05) (added external format)\n ARRAY("QTY")=QTY field (#.04)\n \nFrom the DRUG file (#50):\n ARRAY("DEA SPECIAL HDLG")=DEA, SPECIAL HDLG field (#3)\nTerms and Definitions. Additional data elements to be used in conditional\nevaluation of those terms/definitions can only be provided by changes to\nthe Outpatient Pharmacy Application Program Interface (API), PSOPXRM1.\nThis patch will add the following data elements to the array returned\nby the API.\n \nFrom the PRESCRIPTION file (#52):\n\n\nThe FY10 Q2 Enhancement Release includes the following two enhancements.\n \n \nVA Generic Name: PREDNISONE \n \n Dispense Drugs\n ---------------\n 1 - PREDNISONE 1MG TAB\n 2 - PREDNISONE 5MG TAB\n 3 - PREDNISONE 20MG S.T.\n \nEnter a list or range of numbers (1-3): 1-3\nThis new option has been placed under the Output Reports [PSO OUTPUTS]\n \nVA Generic Name: \n \nExclude Deceased Patients? YES// NO\n \n \n ** To avoid undesired wrapping of the output data, **\n ** please enter '0;256;999' at the 'DEVICE:' prompt. **\n \n \nmenu and uses a sort template PSO DRUG WARNINGS.\n \nDEVICE: HOME// ;0;256;999 GENERIC INCOMING TELNET\n \n \n Before continuing, please set up your terminal to capture the\n detailed report data. On some terminals, this can be done by\n clicking on the 'Tools' menu above, then click on 'Capture\n Incoming Data' to save to Desktop. This report may take a\n while to run.\n \n \n \nPress Return to Continue: \n \nThe output of this report is in a delimited output format suitable for \nexport to MS Excel and includes data from original prescription fills,\nrefills and partial fills. The report output is sorted primarily by\npatient name and secondarily by prescription number.\n \nEach fill of the prescription is printed on a separate line. Each \nprescription detail line starts with a double backslash followed by an\n \nidentifier to denote the type of fill (ORIGINAL, REFILL, PARTIAL). \nEach line contains 38 fields separated by up-arrow ("^") as described \nbelow:\n \n 1. FILL TYPE (e.g.,\\\\ORIGINAL\\) 2. RX #\n 3. DRUG NAME 4. PATIENT NAME\n 5. SSN 6. ADDRESS 1\n 7. ADDRESS 2 8. ADDRESS 3\n 9. CITY 10. STATE\n 11. ZIP 12. PHONE (HOME)\nExample of Input Prompts:\n 13. PHONE (WORK) 14. PHONE (CELL)\n 15. DECEASED? 16. FILL #\n 17. ISSUE DATE 18. FILL DATE\n 19. RELEASED DATE/TIME 20. EXPIRATION DATE\n 21. LOT # 22. NDC\n 23. DIVISION 24. PHARMACIST\n 25. PROVIDER 26. PATIENT STATUS\n 27. QTY 28. DAYS SUPPLY\n 29. # OF REFILLS 30. MAIL/WINDOW\n 31. CMOP? 32. PARTIAL REMARKS\n \n 33. TRANSMISSION NUMBER 34. SEQUENCE #\n 35. CMOP NDC 36. DATE SHIPPED\n 37. CARRIER 38. PACKAGE ID\n \nExample of Output:\n \n\\\\FILL TYPE\\^RX #^DRUG NAME^PATIENT NAME^SSN^ADDRESS 1^ADDRESS 2^\nADDRESS 3^CITY^STATE^ZIP^PHONE (HOME)^PHONE (WORK)^PHONE (CELL)^\nDECEASED?^FILL #^ISSUE DATE^FILL DATE^RELEASED DATE/TIME^EXPIRATION\nDATE^LOT #^NDC^DIVISION^PHARMACIST^PROVIDER^PATIENT STATUS^QTY^DAYS\n ** To avoid undesired wrapping of the output data, **\nSUPPLY^# OF REFILLS^MAIL/WINDOW^CMOP?^PARTIAL REMARKS^TRANSMISSION\nNUMBER^SEQUENCE #^CMOP NDC^DATE SHIPPED^CARRIER^PACKAGE ID\n\\\\ORIGINAL\\^100002236A^AMPICILLIN 250MG^WHIPATNM,PATIENT^666-00-0248^\n164 FRIENDSHIP DRIVE^^^TROY^NEW YORK^12180^271-1112^^^Y^0^8/22/03^\n8/22/03^12/23/03 13:36:40^2/22/04^^839-5087-06^EXT (500)^RPH,NAME^\nDOCTOR,NAME^SC LESS THAN 50%^1^30^5^MAIL^N^^^^^^^\n\\\\REFILL\\^100001423^IBUPROFEN 600MG^WILPATNM,TEST3^000-00-3333^HERE\n^^^TROY^NEW YORK^10000^^^^N^1^4/1/96^2/5/97^2/5/97 14:40:41^4/2/97^\n123123123^00615-2526-05^EXT (500)^TEST,PHARM F^TEST,PROVIDER L^\n^SC LESS THAN 50%^90^30^5^MAIL^N^^^^^^^\n ** please enter '0;256;999' at the 'DEVICE:' prompt. **\n\\\\PARTIAL\\^100002236A^AMPICILLIN 250MG^TEST2,PATIENT^666-00-0248^\n164 FRIENDSHIP DRIVE^^^TROY^NEW YORK^12180^271-1112^^^Y^1^8/22/03^\n12/4/03^12/23/03 13:36:42^2/22/04^^00839-5087-06^TROY (514)^RPH,NAME^\nDOCTOR,NAME^SC LESS THAN 50%^1^1^5^WINDOW^N^PARTIAL REMARKS TEST^^^^^^\n \nMISCELLANEOUS FIX:\n------------------\n \nThe recently released patch PSO*7*326 provided the enhanced functionality\nto look up patient by prescription number in backdoor pharmacy. After\n \ninstalling this patch, four sites reported that they were unable to\nretrieve patient information by swiping the Veterans Identity Card (VIC),\nwhich had not been a problem before patch 326 installation. \n \nThe output of this particular card reader is in the format:\n"%99999999^XXXXXXXXXXXXXXXX^99999999^^^^N^9999999999?"\n \nThe code change that was made to retrieve patient by prescription number \nin patch 326 was not allowing the use of up-arrow ("^") characters as \npart of the input data, hence the failure. This patch 348 addresses the \n \n \nissue.\nEXCLUDE DECEASED PATIENTS (Y/N) Y// ES\nSTART WITH DIVISION: FIRST//\n START WITH DRUG: FIRST//\n * Previous selection: FINISH DATE/TIME from Oct 25,2009 to Oct \n 27,2009@24:00\n START WITH FINISH DATE/TIME: Oct 25,2009// (OCT 25, 2009)\n GO TO FINISH DATE/TIME: Oct 27,2009// (OCT 27, 2009)\nDEVICE: GENERIC INCOMING TELNET\n \n1. Canned Report for Outpatient Prescription Activity (NSR #20081114)\n \n Before continuing, please set up your terminal to capture the\n detailed report data. On some terminals, this can be done by\n clicking on the 'Tools' menu above, then click on 'Capture\n Incoming Data' to save to Desktop. This report may take a\n while to run.\n \nPress Return to Continue:\n \nThe report output will be generated by print templates PSO DRUG WARNINGS\n \nand PSO DRUG WARNINGS HEADER in a delimited output format suitable for\nexport to Microsoft (MS) Excel. The report will contain patient\ndemographic and prescription information.\n \nOutput Example:\n \n\\\\^PATIENT^SSN^ADDRESS 1^ADDRESS 2^ADDRESS 3^CITY^STATE^ZIP^PHONE \n(HOME)^PHONE (WORK)^PHONE (CELL)^DECEASED?^RX #^DRUG^FINISH D/T^QTY PER \nDAY^STATUS^REF REM^PRO VIDER^LAST DISPENSED DATE^RETURNED TO STOCK?\n\\\\^OUTPATNM,BARRY^666000198^1 SPRING ST^BLDG 2^APT 3^SPRINGFIELD^MO^65801^\nA new option named Prescription List for Drug Warnings [PSO RX LIST]\n456-6789^^^^301129^DOXEPIN 25MG CAP^03/22/07^1^DISCONTINUED^10^PHARMA,\nOUTPT^04/12/07^\n\\\\^TESTPATNM,MICHELLE^666000770^MAIN ST^^^CLEARWATER^FLORIDA^33762^\n444-5532^345-1234^^^800024A^DOXEPIN 25MG CAP^02/14/07^2^DISCONTINUED^5^\n^PHARMA,INPT^02/18/07^\n \n \n2. Reports to Identify Patients/Prescriptions for Recall Notices \n(NSR #20081115)\n \nprovides a report capable of identifying all patients that have \nA new option called List of Patients/Prescriptions for Recall Notice [PSO\nRECALL LIST] has been provided to identify prescriptions containing\nmedications associated with specific recall criteria, such as lot numbers\nand/or National Drug Code (NDC) numbers.\n \nThis new option has been placed under the Output Reports [PSO OUTPUTS]\nmenu and prompts the user for the following criteria: \n Division \n Prescription Release Date Range\n Medication Identifier \nbeen dispensed a particular medication(s). This report was developed by\n Inclusion/Exclusion of Deceased Patients\n \nOne of the following four medication identifiers may be selected:\n 1-NDC code\n 2-Dispense Drug and Lot #\n 3-Dispense Drug only\n 4-VA Generic Name\n 5-Orderable Item\n \n \nconverting Class III functionality to a standardized, nationally released\nExample of input prompts:\n \nYou may select a single or multiple Divisions,\nor enter ^ALL to select all Divisions.\n \nDivision: ^ALL\n \nFrom Release Date: T-90// (JAN 20, 2010)\n \nTo Release Date: T// (APR 20, 2010)\nreport.\n \n Select one of the following:\n \n 1 NDC\n 2 DISPENSE DRUG AND LOT NUMBER\n 3 DISPENSE DRUG\n 4 VA GENERIC NAME\n 5 ORDERABLE ITEM\n \nSelect 1-5 : 4 VA GENERIC NAME\n\n\n1. When a non-suspended refill is deleted there is no entry added into the\n Activity Log to reflect this.\n2. ePharmacy Medication Profile (View Only) shows a prescription as copay\n even after the copay has been removed.\n3. Undefined error when printing Medication Instructions.\n4. UNDEFINED error at h+7^IBCSCU\n\n
\nThis patch will correct the following issues.\n \nHD0000000344080 2 CMOP is getting wrong refill text (3 of 2) and the \n refill # is a negative\n\n
\n1. A modification was made to the Reject Information screen under the \n INSURANCE Information\n Insurance : OPP INSURANCE Coord. Of Benefits: PRIMARY\n Contact :\n Group Name : D-GROUP1\n Group Number : D00001\n Cardholder ID :\n \n2. A COB field(#27) was added to the PRESCRIPTION file (#52),\nREJECT INFO sub-file (#52.25) to store the COB for the Third Party \nInsurance Rejects for the fill. The Set of Codes will be stored as "1" for\nThird Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] option and the\nPrimary, "2" for Secondary, and "3" for Tertiary. Tertiary billing will \nnot be implemented with this patch group, but is included for future use.\n \nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n--------------------------------------------------------------------------\n52.25,27 COB 2;7 SET\n \n '1' FOR PRIMARY; \n '2' FOR SECONDARY; \nThird Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] option\n '3' FOR TERTIARY; \n LAST EDITED: JAN 20, 2009 \n DESCRIPTION: This field contains the Coordination of \n Benefits indicator for the third party \n insurance rejection for the fill. This \n field can contain 1 for Primary, 2 for\n Secondary, or 3 for Tertiary.\n \n3. A modification was made to the Patient Medication Profile screen \nunder the ePharmacy Medication Profile (View Only) [PSO PMP] option to\nto incorporate the Coordination of Benefits (COB) indicator to be \nmodify the ECME LOG section to change the "Comments:" preface from\n"Submitted to ECME:" to "ECME:" for non reversals. Second modification was\nmade to add the COB indicator with insurance provider to the suffix of the\n"Comments:." The COB indicator will be denoted with a lower case "p" for\nPrimary, "s" for Secondary and a "t" for Tertiary, which will be followed\nby the name of the insurance provider in capital letters.\n \nExample: \n \n ECME Log:\ndisplayed in the insurance section. The indicator will be displayed as\n \n # Date/Time Rx Ref Initiator Of Activity\n==========================================================================\n 1 1/28/09@11:37:56 ORIGINAL OPUSER,ONE\n Comments: ECME:WINDOW FILL(NDC:00046-1066-05)-E PAYABLE-pOPP INSURANCE\n"Coord. Of Benefits:" followed by either PRIMARY, SECONDARY, or TERTIARY.\n \nExample:\n \n\n
\n 1. The Drug Transaction History [PSA DRUG DISPLAY] menu option is not \n showing the outpatient prescriptions that are dispensed for all\n pharmacy locations when the prescription is dispensed through\n the Outpatient Pharmacy Automation Interface (OPAI).\n \n 2. The mailman message that gets generated when the release of a\n discontinued prescription is attempted does not make the distinction\n between a regular and a partial fill. \n\n
\nThis patch will resolve the 3 issues.\nshould always display.\n1. If a prescription has only a date, no time, for Released Date.Timeme\nit will not show up on the Hi Cost Report.\n2. When selecting the 'Sort by Drug (alphabetically), status active,\nstatus recent expired' view on the Meds Tab, prescriptions that have\na status of Hold or Provider Hold are not displayed.\n3. Non-VA med orders, that have been Discontinued, are showing up in\nthe Meds tab in CPRS. Active Non-VA meds, if they have a start date\nolder than the ORCH CONTEXT MEDS date are not displayed. Active meds \n\n
\nThis patch will resolve the issue where the Ignored Rejects Report [PSO \nIGNORED REJECTS REPORT] abends when sorting on PATIENT and only one\npatient is selected.\n\n
\nA VAMC has requested both a date and time stamp for prescription activity\nlog entries displayed by FileMan.\n\n
\n1. Fixed errors reported in Tuscaloosa, local NOIS PHA-0198-N0089 and\n \n3. Added a check to screen out pending refill order when doing order checks.\nRoutine PSODRDU1\n \n4. Made Site parameters required in the Delete Rx option. NOIS: PUG-0198-52050\nRoutine PSORXDL\n \n5. Fixed an error that occurred in Tuscaloosa on a Health Summary. It came upon\na prescription with missing data, (No drug, provider, or patient pointer).\nA check was added to look for missing data. Routine PSOHCSUM\nPHA-0198-N0076. An undefined error occurred if the user selected to edit\n \n6. Fixed error that occurred in Tuscaloosa in PSOORRL routine, returning\na Med profile to CPRS. The error occurred because of an invalid provider\nentry in a prescription. Modified code to check for invalid and\nmissing data in the provider field and the drug field. Routine PSOORRL\nboth the Pharmacy Orderable Item and the Dispense Drug, and entered a\nDuplicate Drug of another Rx for that patient, and did not Discontinue\nthat duplicate Rx when prompted to Discontinue. Routine: PSOOREDT\n \n2. Corrected a problem where a possible invalid cross reference existed. Which\ncould cause an undefined error when cost data is being compiled.\nRoutine: PSOCSTM, PSOCSTD\n\n
\n1. For a drug marked for lab monitor, if text is entered for the results\n3. Fixed a possible undefined variable error that may occur during the\nrenewal of certain drugs in certain sites. (START+15^PSORENW1:2,\n%DSM-E-UNDEF, undefined variable PSODRUG("DEA"))\n \n4. For clinics that had inactive sites, one particular management report\nwas giving empty pages even though there were other active sites with\ndata. This patch fixes this problem.\n \n5. Made data dictionary changes to the following fields in PRESCRIPTION\nfile (#52):\ninstead of a numeric value, the Action Profile reports the result as zero\n a. UNIT PRICE OF DRUG field (#17)\n b. CURRENT UNIT PRICE OF DRUG field (#1.2) of REFILL sub-file (#52.1),\n c. CURRENT UNIT PRICE OF DRUG field (#.042) of PARTIAL DATE sub-file\n (#52.2).\n \nThese fields currently set to the 99.999 format, need to be changed to the\n999.9999 format, in order to maintain the same format as that of PRICE PER\nDISPENSE UNIT field (#16) of the DRUG file (#50) which is of the format\n999.9999. During an original/refill/partial fill an exact unit cost will\nbe maintained in the respective fields without getting truncated. This\nrather than displaying the text. This problem is fixed in this patch.\nchange will also eliminate the possibility of reporting zero cost for\ncertain low cost dispensed items as reported in numerous NOISs.\n \nThis patch also makes a Data Dictionary change to the NDC field (#11), an \nunused field by Outpatient Pharmacy V. 7.0 package in REFILL sub-file\n(#52.1) from piece 13 of node 0 to piece 3 of node 1. There is an optional\nbackground job that will move the data from its old location to its new\nlocation. The date/time is site selectable and can be queued to run during\nthe installation of the patch or at another time by using the entry point\nNDCQ^PSOPOST1. \n \n \n6. Fixed a possible undefined variable error (%DSM-I-ATLABEL,\nSTART+2^PSOCST5:7) that may arise while using the OPTION: Provider by Drug\nCosts [PSO COST PROVIDER BY DRUG] on exiting using "^" in response to the\n"(Enter ^ to Halt)" during viewing of the report on the screen.\n \n7. When a medication information sheet is printed using the Rx\n(Prescriptions) [PSO RX] option, under the Patient Prescription\nProcessing [PSO LM BACKDOOR ORDERS] option, Medication Profile, the\npatient's name does not print on the medication sheet. (This fix is in\n2. When UNITS field (#6) of SITE/SPECIMEN sub-file (#100) of\nreference to an E3R# 12659).\n \n8. A change has been made to the input transforms of the quantity fields\nof the PRESCRIPTION file (#52). The change will prevent alpha characters\nfrom being entered for quantity through the pharmacy options.\nLABORATORY TEST file (#60) is not defined, the Display Lab Tests and\nResults [PSOLAB LIST] option displays "Specimen data missing !!". This\npatch fixes the problem.\n \n\n\nThis patch is part of a combined build, made up of the following three \nDrug Information Framework (DIF) interfaces and database. The VistA Drug \nInteraction module will be replaced by the FDB Drug-Drug Interaction \nModule (DDIM). The VistA Duplicate Class module will be replaced by the \nFDB Enhanced Therapeutic Classification (ETC) System.\n \nIn addition, the following three order checks that use VistA data have\nbeen added to Inpatient Medications and Outpatient Pharmacy. These checks\ncurrently occur in Computerized Patient Record System (CPRS), but will be\nnew to Pharmacy with the installation of these patches:\n Aminoglycoside Ordered\npatches:\n Dangerous Meds for Patients > 64\n Glucophage - Lab Results\n \nA new Graphical User Interface (GUI) module is also being introduced \ncalled Pharmacy Enterprise Customization System (PECS), to be used only \nby members of Pharmacy Benefits Management (PBM). It will allow PBM to \ncustomize the data provided by FDB for use in VistA.\n \nThe following three patient safety issues have also been addressed in \nthese patches:\n OR*3.0*272 (Computerized Patient Record System)\n Order Checks on PreMix IV Solutions (PSI-06-012)\n Order Check display sequence changes (PSI-07-080)\n Eliminating confusion in Inpatient Medications Order Check display \n and processing (PSI-07-080)\n PSJ*5.0*181 (Inpatient Medications)\n PSO*7.0*251 (Outpatient Pharmacy)\n \nThese patches will replace most of current VistA medication order \nchecking system with version 1.0 of the new Medication Order Check \nHealthcare Application (MOCHA) system that uses the First DataBank (FDB) \n\n
\n1. This patch corrects a problem when a tech/clerk reinstates a prescription\ndiscontinued did not display when it should have displayed.\n \n3. This patch corrects a problem where the SIG for med orders did not\nformat and display correctly (ccr3803).\n \n4. Corrects a problem when Ctopying an Rx and the duplicate therapy Rx list\nselected for deletion does not re-displays the complete list of Rxs to be\ndeleted as a duplicate therapy.\n \n5. OP Intervention Hidden Action When viewing interventions via the View\nfrom previously being discontinued. The problem occurs when the site\nIntervention prompt data does not display correctly. Data is displayed until\nscreen has filled and then overlaps on bottom few lines. The user cannot\nview the intervention due to scrolling issue. \n \n6. Corrected order check sequence. (ccr 3832). \n \n7. IP REQ 3.8.10.28 Failing - no TD messages for OP TD Discontinued Meds\n(ccr 3837).\n \n8. Hard error during clerk reinstate of an rx with a duplicate drug non-va\nparameter VERIFICATION (FILE #59; Field #.12) is set to 'No' and a user\nmed (ccr 3851).\n \n9. IP Remote Rx display in Therapeutic Duplication warning does not match\nthe SRS and FR 3.8.10.16 (ccr 3853).\n \n10. Hard error during clerk reinstate of an rx with a duplicate drug non-va\nmed (ccr 3551).\ndoes not hold the PSORPH key and reinstates a prescription, the prescription\ngets put into a 'NON-VERIFIED' status. In this situation the prescription\nshould have a status of 'ACTIVE'.\n \n2. This patch corrects a problem when a tech/clerk enters a new duplicate\ndrug and the confirmation message that the duplicate drug order was\n\n
\nThis patch contains software modifications to the Outpatient Pharmacy (OP)\n . Patient decision-making should be advised by information about a known\n \n Please wait... \n \n The system is unable to display FDA Med Guide automatically.\n \n Please, contact your local technical support for assistance to\n resolve this problem. In the meantime, you can copy/paste the\n link above into your browser's address bar to retrieve the\n FDA Medication Guide.\n \n serious side effect with a product, or \n Enter RETURN to continue, '?' for HELP, or '^' to exit: \n \n \n If a user tries to use this option for a medication that does not have\n an FDA Medication Guide on file, the following message will display:\n \n \n Select Item(s): MG Display FDA Medication Guide \n \n There is no FDA Medication Guide associated with this medication.\n . Patient adherence to directions for the use of a product is essential\n \n Press RETURN to continue\n \n \n Note: This option requires a Java software component to be installed on\n ---- the user's computer. This software will be released as part of this\n project. Please, refer to the project Release Notes and Installation\n Guide documentation for further information.\n to its effectiveness. \n \nThe features in the FDA Medication Guides project are being delivered in\nincremental releases. This patch is part of the Increment 2 release. The \nfeatures included in this release are:\n \n . Establishment of a Server Repository for FDA Medication Guides within \nV. 7.0 application to support the FDA Medication Guides project. The \n the VA network.\n \n . Updates to 900+ entries in the VA PRODUCT file (#50.68) to store the \n corresponding FDA Medication Guide document name will be provided via\n the NDF Monthly Data Update patches.\n \n . Introduction of a PC based Java software component to enable the\n automatic retrieval of an FDA Medication Guide from within VistA. The\n software does not require any direct user interaction. It works as a \n bridge between VistA and the PC where it is installed. The software \nproject objective is to allow pharmacy staff to retrieve the FDA Medication \n identifies a request from VistA for a specific FDA Medication Guide and\n automatically retrieves it from the Server Repository and displays to the\n user via the Internet Explorer browser. \n \n . Introduction of a new option called Display FDA Medication Guide [PSN MED\n GUIDE] to the National Drug File V. 4.0 application for retrieving and \n displaying the FDA Medication Guide for a specific VA Product.\n \n . Introduction of new functionality to the Patient Prescription Processing\n [PSO LM BACKDOOR] option in the Outpatient Pharmacy V. 7.0 application\nGuide for prescriptions that contain FDA approved information that can help\n for retrieving and displaying the FDA Medication Guide for a specific \n prescription.\n \nBelow is a list of all the applications involved in this release along\nwith their patch number:\n \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*343\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*263\npatients avoid serious adverse events. The FDA requires that Medication\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*158\n \nThe FDA Medication Guides project is expected to complete in three \nincrements. Among other features, the next Increment will automate the \nprinting of FDA Medication Guides for prescriptions dispensed by the VA\nvia Outpatient Pharmacy application when the prescription label is printed.\n \nThe following modification is inclued in this patch (PSO*7*343):\n \nPatient Prescription Processing [PSO LM BACKDOOR ORDERS] option\nGuides be included with certain prescribed drugs and biological products \n \n Pharmacists will be able to retrieve an FDA Medication Guide for a \n specific prescription by selecting the prescription and invoking the OTH\n (Other OP Actions) hidden action and choosing the new item MG Display FDA\n Medication Guide. A Java software component running at the user's PC will \n then display the FDA Medication Guide Adobe Acrobat document (.pdf) by \n automatically opening it via the user's default web browser, which will\n allow the users to print it to any printer available to them, as seen \n below:\n \nwhen the Agency determines that: \n --- Other OP Actions ---\n PN Progress Note (OP)\n AP Action Profile (OP)\n MI Print Medication Instructions\n DO Display Orders' Statuses\n MG Display FDA Medication Guide\n \n Select Item(s): MG Display FDA Medication Guide \n \n The following URL provides the link to the FDA Medication Guide \n \n associated with this medication.\n \n vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_(Generic)_(2008).pdf\n \n Please wait... \n \n [FDA Medication Guide .pdf document opens on the web browser]\n \n Enter RETURN to continue, '?' for HELP, or '^' to exit: \n \n . Certain information is necessary to prevent serious adverse effects \n If a user tries to use this option from a computer which does not have the \n required Java software component installed, the following message will \n display:\n \n Select Item(s): MG Display FDA Medication Guide \n \n The following URL provides the link to the FDA Medication Guide \n associated with this medication.\n \n vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_(Generic)_(2008).pdf\n\n
\nPatches PSO*7*316 and GMTS*2.7*92 correct issues reported with the \n--------\nRoutine PSS^PSO59 returns data about the demographics of outpatient \npharmacy divisions, such as site name and address. The existing API did \nnot return the division's assigned area code and phone number, which are \npresent in the format of Tool #2: Medication Worksheet.\n \nResolution:\n-----------\nThis patch modifies routine PSO59 to return the AREA CODE field (#.03)\nand PHONE NUMBER field (#.04) as part of the target array.\nTool #2: Medication Worksheet. The Health Summary patch GMTS*2.7*92\n \n2. Routine PSOQUAP distributed with patch PSO*7*294 is not used.\n \nProblem:\n--------\nDuring testing of patch PSO*7*294, changes were made that resulted in \nroutine PSOQUAP being no longer required. The routine was left in the \npatch at the time in order to reduce the remaining testing time required.\n \nResolution:\nwill require patch PSO*7*316 and will create a national entry in the\n-----------\nThis patch removes routine PSOQUAP. There are no known programs that \ncall this routine.\n \n3. PSO*7*294 was noncompliant with Programming Standards and \n Conventions (SAC) for VistA applications.\n \nProblem:\n--------\nDuring the internal review of some of the routines distributed with \nHEALTH SUMMARY COMPONENT file (#142.1) for Tool #2: Medication Worksheet.\nPSO*7*294 findings uncovered some SAC standard violations.\n \nResolution:\n-----------\nRoutines PSOQ0186 and PSOQMCAL are being replaced with GMTSPST2. \nCorresponding Health Summary patch GMTS*2.7*92 creates a national Health\nSummary component for Tool #2: Medication Worksheet to utilize the\nreplacement routines.\n \n1. The existing Application Program Interface (API) #4827 did not\n return fields required by Tool #2: Medication Worksheet.\n \nProblem:\n\n
\nThis patch will resolve the issue where the incorrect message is displayed\nto the user. This is PSPO1744.\n\n
\nUser receives an undefined error when accessing the Non VA Meds Report.\n\n
\nThis patch is a follow-up to MEDICATION ORDER CHECK HEALTHCARE \nApplication Program Interface (API) that retrieves order check\ninformation. This API returns a value of -1 for error of some type\noccurred, 0 (zero) for order checks complete with no issues found, or 1\nfor interactions found. Outpatient Pharmacy was not checking for -1. \nThis patch adds the check for -1, and displays a message when -1 is\nreturned.\n \n2. A misspelling of the word "Interoperability" was corrected in the \nfirst line of routine PSOORRD2.\n \nAPPLICATION (MOCHA) 1.0 group of patches.\n3. An undefined error was corrected. Using the Rx Verification by Clerk \noption, a subscript error occurs after an unsuccessful request to First \nData Bank (FDB) is recieved. The variable DFN is undefined and the error\nis displayed around the "Verify for" prompt. The error can present itself\nin the following ways:\n \n a. When a page feed occurs just prior to the "Verify for" prompt: \n <UNDEFINED> VERIFY+2^PSOVER1 *DFN. \n \n b. During the order check process just before the PDM API is called: \n \n <UNDEFINED> OBX+3^PSODDPRE ^TMP(547819387,"PSOPEPS","OUT",0). \n \n4. For a technician entered order, the message "Remote data not available\n- Only local order checks processed" was rolling off the screen. This \nmessage is displayed in when remote data isn't available just before\ntherapeutic duplications during the prescription order process. This has \nbeen corrected by adding an "Enter to continue" prompt after the message \nis displayed when the user is a technician.\n1. A correction was made to address an occurrence reported in a\ntest account where Order Checks did not occur and no message was\ndisplayed to the user. \n \nAfter the message "Now Processing Enhanced Order Checks! Please wait..."\nis displayed, the system calls a Pharmacy Data Management (PDM) \n\n
\nThis patch will resolve two issues with the List of Patients/Prescriptions\nfor Recall Notices.\n \n1) List of Patients/Prescriptions for Recall Notices is wrapping\n incorrectly.\n \n2) PSO RECALL LIST Report needs End-of-Record Identifier.\n\n
\n \n \nThis patch will resolve the issue where the REFILL DATE shows a past date \nwhen the Rx is taken off hold.\n\n
\nThis patch addresses a request made by the Health Resource Center (HRC) \n1. The calculation of remaining refills on the medication profile screen. \n Routine PSOPMP1 was modified to fix the issue.\n \n2. When selecting multiple items to be displayed from the medication \n profile list, only the first selection is displayed. Routine PSOPMP0\n was modified so that all selected items are displayed.\n \nIntegration Control Registration #4595 was modified to grant the CAPRI \npackage access to the Medication Profile and Refill [PSO HRC PROFILE/\nREFILL] option.\nto Outpatient Pharmacy V. 7.0 to provide a new standalone option similar\nto that of ePharmacy Medication Profile (View Only) [PSO PMP] option for\nthe Compensation and Record Interchange (CAPRI) system. The Medication\nProfile and Refill [PSO HRC PROFILE/REFILL] option will allow users both\nto view a patient's medication profile and to refill prescriptions.\n \nThe patch also corrects the following two issues found in ePharmacy \nMedication Profile (View Only) [PSO PMP] option.\n\n
\n1) This patch fixes a problem that can occur when processing refills\nListman action, a problem can occur with the METHOD OF PICK-UP field\n(#35). If the routing is WINDOW, and no METHOD OF PICK-UP is entered, and\nthe prescription has a previous METHOD OF PICK-UP entered, the previous\nMETHOD OF PICK-UP will print on the label, even though a METHOD OF PICK-UP\nwas not entered when pulling from suspense. This patch makes the change to\nprint whatever was entered when pulling from suspense, and if the prompt\nwas bypassed, the METHOD OF PICK-UP will be deleted from the prescription,\nand will not appear on the label.\n \n3) When pulling a prescription from suspense, the fill date or refill\nin the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option. The\ndate field is updated with the date that the pull action occurs. Then\nwhen that prescription is refilled, the next possible fill date is\ncalculated based on that last fill date. The problem occurs when the\nlabel that is pulled from suspense is a reprint label. This patch makes\nthe change to only update the fill date or refill date if the label\nbeing pulled from suspense is not a reprint label.\n \n4) A problem can occur in the Patient Prescription Processing [PSO LM\nBACKDOOR ORDERS] option when a reprint request is made for a prescription\nthat cannot be reprinted, such as an expired or discontinued prescription.\npatient record is sometimes getting locked during this process, and not\nIf other valid labels are also requested for the patient, the valid\nlabels will sometimes not print. This patch resolves the problem.\n \n5) This patch will modify the call that returns prescription information\nto Computerized Patient Record System (CPRS). The release date of the\noriginal fill is being added for display purposes in CPRS.\n \n6) When processing refills through the Barcode Batch Prescription\nEntry [PSO BATCH BARCODE] option, and when processing refills phoned\nin through the MUMPS AudioFax software, the patient name and last four\nalways getting unlocked. This patch makes the change to only lock at the\ndigits of the SSN will display if the refills can't be processed because\n"Yes" was the response for the "Allow fills for inpatient and CNH?"\nprompt, and the patient is an inpatient or is CNH Current.\norder level when processing refills in this option. When processing\nrenewals through this option, the lock will remain for the patient record,\nand will also remain at the order level.\n \n2) When pulling a prescription from suspense using the Pull Rx (OP)\n\n
\nUser received an error while completing an order enterd via CPRS\n\n
\nPharmacy inventory not updated when medication is returned to stock.\n\n
\nePharmacy Phase 5 - NCPDP D.0\n\n
\nWhen running menu option Signature Log Reprint [PSO SIGLOG REPRINT] or \nthe Speed option RS Reprint Sig Log no output is printed.\nIt will also resolve an issue where a label that should print does not \nand a label that should not be printed does.\n\n
\nThis patch will resolve the issue where Active Non-VA meds with a \nStart Date do no display on the Meds Tab when no Stop Date is defined in\nthe ORCH CONTEXT MEDS parameter.\n \nparameter.\n\n
\nThis patch will resolve the issue where the incorrect Pharmacist is \nappearing on prescription.\n\n
\nThis patch will resolve the issue where the ROUTE from the previous \nprescription is displayed on the screen for the next prescription when \nthere is no ROUTE associated with it.\n\n
\nePharmacy Phase 6\n\n
\nThis patch is being released as part of Pharmacy Legacy Enhancements \none division to have more than one Automated Dispensing Device (ADD)\ncommunicating with Veterans Health Information Systems and Technology\nArchitecture (VistA) through the OPAI.\n \n1. A new file named PHARMACY AUTOMATED DISPENSING DEVICES file (#52.53)\n was created. Entries in this file are required only if the site wants \n to utilize the multiple dispensing functionality. The new file \n contains the following fields:\n \n NAME - A free-text field that is between 3-30 characters in length. \nFiscal Year 2011 to address the Outpatient Pharmacy Automation Interface\n It is the name given to the automated dispensing device.\n DNS - A free-text field that is between 1-50 characters in length. It\n stores the DNS name or IP address of the automated dispensing \n device.\n PORT - This field is a numeric between 1 and 65535 with no decimal \n places. It stores the port associated with the automated\n dispensing device.\n INACTIVE \n DATE - This is a date field, not required, but is used to inactivate \n the OPAI connection to an automated dispensing device.\n(OPAI) Enhancements. The Pharmacy Data Management patch PSS*1*156 is also\n \n2. A new menu option named Enter/Edit Automated Dispensing Devices [PSO \n AUTO DISPENSING DEVICE] was created to maintain the PHARMACY \n AUTOMATED DISPENSING DEVICES file (#52.53). The option is located\n under the Maintenance (Outpatient Pharmacy) [PSO MAINTENANCE] menu.\n Only sites planning to use the multiple automated dispensing devices\n for an outpatient division should use this option.\n \n3. A new sub-file (#59.20081) multiple named OPAI was added to the \n DISPENSING SYSTEM PRINTER sub-file (#59.02008) in the OUTPATIENT SITE \nbeing released as part of this enhancement.\n file (#59). The sub-file contains the following new fields:\n \n DNS NAME - This field is a pointer to the PHARMACY AUTOMATED \n DISPENSING DEVICES file (#52.53).\n CATEGORY - Categories provide the flexibility of routing RXs to\n different ADDs. This field contains the following set\n of codes:\n MCS MAIL - CS\n MNCS MAIL - NCS\n MAIL MAIL\n \n WCS WINDOW - CS\n WNCS WINDOW - NCS\n WIND WINDOW\n CS CONTROLLED SUBSTANCE\n NCS NONCONTROLLED SUBSTANCE\n A ANY\n S STORAGE\n \n4. The Site Parameter Enter/Edit [PSO SITE PARAMETERS] option was \n modified for addition of the new fields in the OPAI multiple\nVeterans Affairs Medical Center (VAMC) facilities have moved to using \n (#59.20081) in the OUTPATIENT SITE file (#59).\n \n5. During prescription processing, if the label printer selected has \n ADDs defined then Rx will be routed to the appropriate ADDs. A message\n will be displayed indicating the ADDs where the Rx will be routed.\n Below is an example of the routing message.\n \n PRESCRIPTIONS SENT TO:\n OPTIFILL1\n 100002815 ACETAMINOPHEN 325MG C.T.\nmultiple vendors for automated medication dispensing systems to improve\n 100002816 AMOXICILLIN 250MG CAP\n 100002824 AMOXAPINE 50MG TAB\n \n SCRIPTPRO1\n 100002844 CIMETIDINE 200MG TAB\n \n6. During testing a problem was discovered in the Print from Suspense\n File [PSO PNDLBL] and Reprint Batches from Suspense [PSO PNDRPT] \n options. The ZTIO variable, which stores the label printer, was being\n reset to null after processing each patient prescription. As a result \nthe efficiency of outpatient pharmacy operations. The following\n a printer defined with multiple ADDs was not routing prescriptions \n properly. Routines PSOSULBL and PSOSUSRP were modified to address this\n problem.\n \n7. A new Integration Control Registration (ICR) #5579 was created to \n grant the Pharmacy Data Management package read access to the PHARMACY\n AUTOMATED DISPENSING DEVICES file (#52.53).\n \n8. As per the User Group request, when a dispense complete message is \n received by VistA from the external dispensing interface and if the \nenhancements were made to the Outpatient Pharmacy software to allow any\n mail tracking information is included in the 13th piece of the RXD \n segment, then the activity log will be updated with this information.\n\n
\n1. This patch corrects a problem when compiling the Health Summary component\nto be acted upon (renew, refill, etc.). \n \nA new option, Backfill Prescriptions to CPRS [PSO BACKFILL PRESCRIPTIONS]\nwill be distributed as a stand alone option and may be given to the user(s) \nresponsible for backfilling prescriptions to CPRS. \n \n3. This patch updates the View Prescriptions [PSO VIEW] option to include\nthe provider comments and instructions from CPRS entered orders. \n \nfor Outpatient Pharmacy data. With the new prescription statuses added for \nversion 7 discontinued prescriptions were printing when they should not\nhave. \n \n2. The CPRS Workgroup members requested that the Outpatient Pharmacy package\nprovide the capability to backfill prescriptions for a date range into CPRS \n(only 18 months of prescriptions are backfilled upon installation of CPRS). \nThis will be an optional tool for sites and none of the orders will be able\n\n
\nThis patch will resolve the following issues:\n1) The message 'There is no refill data to be edited' incorrectly\n displays when editing a prescription that does have refills\n \n2) Due to a change in system printing a modification needs to be made to\n the device setup for the Daily Amis Report [PSO DAILY AMIS].\n\n
\nThe RXD-3 segment for a "partial" in Outpatient Pharmacy has a date missing.\n\n
\nhis patch contains software modifications to the Outpatient Pharmacy (OP)\n . Patient decision-making should be advised by information about a known\n however the user will be able to select other printers as well. The\n HOME and NULL DEVICE are selectable at this point.\n \n Select OPTION NAME: PSO MANAGER Outpatient Pharmacy Manager\n Outpatient Pharmacy software - Version \n \n Division: DIVISION 999 \n \n You are logged on under the DIVISION division.\n \n serious side effect with a product, or \n Select PROFILE PRINTER: HOME// GENERIC INCOMING TELNET\n \n Select LABEL PRINTER: HOME// GENERIC INCOMING TELNET\n \n OK to assume label alignment is correct? YES// \n \n DIVISIONS's FDA Medication Guide Printer(s) on file:\n \n FDA MED GUIDE PRINTER (Default)\n \n . Patient adherence to directions for the use of a product is essential\n Select FDA MED GUIDE PRINTER: FDA MED GUIDE PRINTER//\n \n3. Complete Orders from [OERR PSO LMOE FINISH] option\n Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option\n ---------------------------------------------------------------\n There are a few enhancements being added to the prescription processing\n options regarding the printing of FDA Medication Guides. Among them:\n \n a) The FDA Medication Guide document will print automatically for\n prescriptions, if there is one available.\n to its effectiveness. \n \n b) Users will have the ability to change the FDA Medication Guide \n printer in the same way they change the label and profile printers\n today.\n \n c) When queuing labels to print, if there is at least one prescription\n with an FDA Medication Guide associated, it will require a valid FDA\n Medication Guide printer to be entered. This is similar to requiring\n a valid printer for the label printer.\n \n \n d) The actual label document will contain a note under the barcode,\n before the PMI document, that says "Read FDA MED Guide". Such note\n should indicate to the pharmacist that an FDA Medication Guide\n document has been printed for the prescription and should be handed\n to the patient.\n \n e) The Label Log and CMOP Event Log will both list the FDA Medication\n Guide document name (.pdf) associated with each fill.\n \n f) Users will have the ability to reprint the FDA Medication Guide for\nThe features in the FDA Medication Guides project are being delivered in\n past prescription fills or the latest FDA Medication Guide available\n for the prescription via a new action RM - Reprint FDA Medication\n Guide under the OTH - Other OP Actions menu.\n \n4. Print from Suspense File [PSO PNDLBL] option\n --------------------------------------------\n In order to run this option users will be required to enter a valid FDA\n Medication Guide printer. All prescriptions that prints a label via\n this option and that have an FDA Medication Guide associated will have\n the documente printed as well in the designated printer.\nincremental releases. This patch is part of the Increment 3 release, which\n \n5. Pull Early from Suspense [PSO PNDRX] option\n -------------------------------------------\n If the prescription being pulled from suspense has an FDA Medication\n Guide associated the user will be required to enter a valid FDA\n Medication Guide printer to where the document will be printed for\n the prescription.\n \n6. Change Label Printer [PSO CHANGE PRINTER] option\n ------------------------------------------------\nis the last planned release. The features included in this release are:\n This option is used by users to change the profile and label printers\n after having logged on to a pharmacy division. It is being modified to\n allow users to change the FDA Medication Guide printer as well.\n \n7. Reprint an Outpatient Rx Label [PSO RXRPT] option\n -------------------------------------------------\n If the prescription selected to reprinted the label has an FDA \n Medication Guide associated, this option will ask whether the user also\n wants to reprint the FDA Medication Guide. If they answer YES, a valid\n FDA Medication Guide printer will be required for the user to proceed\n \n with the reprinting of the label and FDA Medication Guide.\n \n8. Label/Profile Monitor Reprint [PSO B] option\n Reprint External Batches [PSO INTERFACE REPRINT] option\n Reprint Batches from Suspense [PSO PNDRPT] option\n -------------------------------------------------------\n These options are used for reprinting batches of labels that may have \n jammed on the printer. When reprinting labels via one of these options\n users will be prompted if they also want to reprint the FDA Medication\n Guide. If they answer YES, a valid FDA Medication Guide printer will be\n . Ability to create and maintain a list of FDA Medication Guide printers\n required for the user to proceed with the reprinting of the label and\n FDA Medication Guide, if one is available.\n \n9. The background process that calculates suspense days now rounds any\n partial day to the next full day. This modification was moved from \n patch PSO*7*385 into this patch due to routine overlap and to avoid\n patch dependency.\nV. 7.0 application to support the Food and Drug Administration (FDA) \n for a specific pharmacy division.\n \n . Automatic printing of FDA Medication Guide along with prescription \n labels.\n \n . Ability to reprint the FDA Medication Guide when reprinting a \n prescription label.\n \n . Ability to change the FDA Medication Guide printer at any point of the\n dispensing process, similar to changing the label printer.\nMedication Guides - Increment 3 project. The project objective is to allow\n \n . Ability to reprint the FDA Medication Guide for any given prescription\n fill or the latest FDA Mediation Guide available for the medication on\n the prescription.\n \n . Identification on the label document that an FDA Medication Guide was\n printed as well and needs to be collated to the documentation before\n being handed over to the patient.\n \n . Changes to the prescription label activity logs showing which specific\npharmacy staff to retrieve the FDA Medication Guide for prescription items\n FDA Medication Guide document printed along with the label.\n \n . Changes to the Consolidated Mail Outpatient Pharmacy (CMOP) Event log\n showing which specific FDA Medication Guide document was available \n for the medication when the prescription fill was transmitted to CMOP.\n \n . Introduction of a PC based Java software component to enable the\n automatic printing of an FDA Medication Guide from within VistA. The\n software does not require any direct user interaction. The software \n identifies a request from VistA for a specific FDA Medication Guide\nthat contain FDA approved information that can help patients avoid adverse\n and automatically sends it to the FDA Medication Guide printer\n selected by the user within VistA when dispensing the medication.\n \n . Ability to update the Windows network printer name for a specific\n device through the Kernel application. Once the pharmacist selects a\n printer to print the FDA Medication Guide Vista will retrieve the \n Windows name for the printer and will pass it on to the Java\n application responsible for printing the document.\n \nBelow is a list of all the applications involved in this release along\nevents. The FDA requires that Medication Guides be included with certain\nwith their patch number:\n \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*70\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*264\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*367\n KERNEL V. 8.0 XU*8*566\n \nThe following modifications are included in this patch (PSO*7*367):\nprescribed drugs and biological products when the Agency determines that:\n \n1. Site Parameter Enter/Edit [PSO SITE PARAMETERS] option\n ------------------------------------------------------\n Two new parameters are being introduced in this option: \n a) FDA MED GUIDE PRINT SERVER URL: this field is used to store the\n Uniform Resource Locator (URL) for the Print Server where the Java\n application responsible for automatically printing of the FDA\n Medication Guides for the division was installed \n (e.g.,'http://127.0.0.1/'). This field is required for the FDA\n Medication Guide functionality to work properly.\n \n b) FDA MED GUIDE PRINTER: This is a multiple field used to store a\n list of printers used for printing FDA Medication Guide document \n for the division. There are two fields in the multiple: 1) FDA\n MED GUIDE PRINTER, which is a pointer to the DEVICE file (#3.5).\n Only devices with a content in the WINDOWS NETWORK PRINTER NAME\n field (#75) are selectable, and 2) DEFAULT PRINTER, which \n indicates whether the printer selected is to be used as the \n default printer for the division. Only one printer can be set as\n default printer for each division. This field is not required.\n The printers in this multiple will be displayed for selection\n . Certain information is necessary to prevent serious adverse effects \n when the user logs into a division. If there is a printer set as\n the default printer, it will be set as the default printer.\n \n \n2. Outpatient Pharmacy Manager [PSO MANAGER] option\n ------------------------------------------------\n When logging into a division, after selecting the Profile and Label\n printers, the user will be prompt to select an FDA Medication Guide\n printer for the current session. If the division selected has a list\n of FDA Medication Guide printers they will be displayed (see below),\n\n
\nThis patch will fix an issue that was discovered in PSOSD1 \nwhere the variable LINE is not being renewed.\n\n
\nHIPAA 5010 MAINTENANCE\n\n
\nThis patch resolves the following two issues:\n \n1) Provide users a more accurate description as to as to why a refill is \nnot allowed.\n \n \n \n2) Correct a misspelling of the word "prescription" in a CPRS pop-up \nbox.\n\n
\nWhen the Date of Death is deleted from a patient, a mailman message is \ngenerated that contains the patient's full name and last four digits of \ntheir Social Security Number in the subject line.\nReturn to Stock for the original fill and partials do not trigger a VDEF\ncall to update the HDR.\nWhen a prescription is auto-DC'ed, if the pharmacist reinstates the \nprescription, the Last Fill Date gets set to today's date rather than \nreverting back to the actual Last Fill Date.\n\n
\nThis patch addresses the following two issues.\n1 - Presciptions re-instated in error.\n2 - The EXCLUSIONARY CHECKED BY field is not getting updated.\n3 - The PSO HI COST report is not exiting when the "^" is used.\n\n
\nNeed to replace the direct global read for the Major Diagnostic Category\nof the ICD Diagnosis file (#80) with the API $$ICDDX^ICDCODE and the \nDescription of the ICD Diagnosis file (#80) with the API $$ICDD^ICDCODE.\n\n
\nCMOP MESSAGE IN ACTIVITY LOG IS CUT-OFF.\nVIEW PRESCRIPTIONS MENU OPTION DOES NOT SHOW CONJUNCTION OF EXCEPT FOR \nCOMPLEX ORDERS.\n\n
\n 1. When using the following cost related report options:\n Provider Costs [PSO COST PER PROVIDER]\n \n it was reported that when a period was specified in different date\n formats (i.e., MMYY or MMDDYY) of any past months then differing reports\n were being produced. This patch fixes this problem. This patch also\n enhances the routines to use common calls, improves the output formats,\n and enhances the user interactive help messages. A new routine named\n PSOCSTX contains all the common calls.\n \n 2. This patch fixes the High Cost Rx Report [PSO HI COST] order sequence\n Clinic Costs [PSO CLINIC COSTS]\n so that it generates reports based on the release date order sequence.\n Division Costs by Drug [PSO DIV COSTS BY DRUG]\n Drug Costs [PSO DRUG COSTS]\n Drug Costs by Division [PSO COST BY DIVISION]\n Drug Costs by Division by Provider [PSO COST DIVISION BY PROVIDER]\n Drug Costs by Provider [PSO COST BY PROVIDER]\n Patient Status Costs [PSO COST BY PATIENT STATUS]\n Provider by Drug Costs [PSO COST PROVIDER BY DRUG]\n\n
\nError occurs when the Drug Class is not defined in the VA DRUG CLASS \nfile (#50.605).\n\n
\nThis patch will resolve the following 3 tickets:\nHD0000000498138 - Date of Death cancelled prescriptions reinstated does not\n show correct Last Fill dates.\n \nHD0000000601013 - Print issues with TRICARE prescriptions\n \nHD0000000586028 - Refills are clogging CPRS\n (CPRS refills were not processing automatically)\n\n
\nThe Pharmacy Legacy Enhancements (PLE) Increment 9 Release includes the \n '1 INSUFFICIENT QTY IN STOCK'\n+---------------------------------------------------------------------+\n \n \n2. Flagging/Unflagging of a pending renewal order\n ----------------------------------------------\n The flagging/unflagging functionality was limited to new pending orders\n only from Computerized Patient Record System (CPRS) V. 3.0. Changes\n were made to extend this functionality to pending renewal orders from\n CPRS as well.\n Note: Flagging/Unflagging is a functionality for the pharmacist (PSORPH\n '2 DRUG-DRUG INTERACTION'\n key holders) only.\n \n3. Non-holders of PSORPH key were able to unflag pending orders\n ------------------------------------------------------------\n The action FL (Flag/Unflag) is blocked for users without the PSORPH\n key when finishing a new pending order. However, if the user selected \n FN (Finish) to finish a new flagged pending order the software was\n allowing the user to unflag the pending order. This has been changed\n to no longer allow non-holders of the PSORPH key to unflag pending \n orders.\n '3 PATIENT REACTION'\n \n4. Non PSORPH key holder access to Edit/DC actions\n -----------------------------------------------\n When processing pending new/renewal orders from CPRS, a non PSORPH key\n holder could use the actions 'Edit' or 'Discontinue' on the order, \n which should not be allowed. This functionality has been disabled.\n \n5. COMMENT field (#.05) in the ACTIVITY LOG sub-file (#52.3) of the \n PRESCRIPTION file (#52)\n ----------------------------------------------------------------\n '4 PHYSICIAN TO BE CONTACTED'\n The length of this field has been increased from 75 to 100 characters\n long to accommodate HOLD and UNHOLD comments.\n \n6. PSO52API API (Application Programming Interface)\n ------------------------------------------------\n This API was modified to check if the prescription's expiration date \n is in the past. If it is and the current prescription status is not\n DISCONTINUED, DELETED, or EXPIRED, the API will update the prescription\n status to EXPIRED. The API will also send updates to CPRS and Health\n Data Repository (HDR) of the status change.\n '5 ALLERGY REACTIONS'\n '6 DRUG REACTION'\n '7 BAD ADDRESS'\n '8 PER PATIENT REQUEST'\n '99 OTHER--SEE COMMENTS'\n \nfollowing modifications to the Outpatient Pharmacy V. 7.0 application:\n As per the recommendation of the Pharmacy User Group the \n following changes were made to the set of codes:\n \n The following new codes were added:\n '9 CONSULT/PRIOR APPROVAL NEEDED'\n '98 OTHER/TECH (NON-CLINICAL)'\n \n The following code descriptions were modified:\n '4 PHYSICIAN TO BE CONTACTED' to '4 PROVIDER TO BE CONTACTED'\n '6 DRUG REACTION' to '6 ADVERSE DRUG REACTION'\n \n '99 OTHER--SEE COMMENTS' to 'OTHER/RPH (CLINICAL)'\n \n The following codes were removed as they were redundant and code\n '6 ADVERSE DRUG REACTION' to be used in its place:\n '3 PATIENT REACTION' \n '5 ALLERGY REACTIONS' \n \n Note:\n A post-install routine has been included in this patch that will\n convert the historical data of codes '3' and '5' to code '6'. \n1. Prescription HOLD/UNHOLD Functionality\n \n On complete installation of this patch, the HOLD REASON field \n (#99) of the PRESCRIPTION file (#52) will have the following set\n of codes:\n '1 INSUFFICIENT QTY IN STOCK'\n '2 DRUG-DRUG INTERACTION'\n '4 PROVIDER TO BE CONTACTED'\n '6 ADVERSE DRUG REACTION'\n '7 BAD ADDRESS'\n '8 PER PATIENT REQUEST'\n --------------------------------------\n '9 CONSULT/PRIOR APPROVAL NEEDED'\n '98 OTHER/TECH (NON-CLINICAL)'\n '99 OTHER/RPH (CLINICAL)'\n \n b. New Security Key PSO TECH ADV for pharmacy technicians\n A new security key called PSO TECH ADV has been created, which \n will allow a user to HOLD a prescription using one of the following\n HOLD reasons, which are a subset of the hold reasons that are\n available to the PSORPH key holders in item (a) above:\n \n a. The HOLD REASON field (#99) of the PRESCRIPTION file (#52) has the\n '1 INSUFFICIENT QTY IN STOCK'\n '7 BAD ADDRESS'\n '8 PER PATIENT REQUEST'\n '98 OTHER/TECH (NON-CLINICAL)'\n \n The PSO TECH ADV key holders will be able to remove a prescription\n from HOLD only for the above hold reasons whether they were put \n on HOLD by the PSORPH key holder or by the PSO TECH ADV key holder.\n \n c. UNHOLD Comments\n following set of codes, which is presented to the PSORPH key holder\n The UNHOLD action has been modified to display the original hold \n reason along with the hold comments (if any) as seen in the example\n below:\n \n+---------------------------------------------------------------------+\n| Select Action: Next Screen// UH UH UNHOLD |\n| Nature of Order: WRITTEN// W |\n| |\n| HOLD COMMENTS: HOLD COMMENTS ENTERED BY THE USER MANUALLY. (REASON: |\n| BAD ADDRESS) on MAY 10, 2012 |\n during prescription 'HOLD' process:\n| |\n| UNHOLD COMMENTS: |\n+---------------------------------------------------------------------+\n \n d. Rx Activity Log\n All activities related to HOLD/UNHOLD action on a prescription will\n be captured in the activity log as seen below:\n \n \n+---------------------------------------------------------------------+\n \n| Activity Log: |\n| # Date Reason Rx Ref Initiator Of Activity |\n| ... |\n| 8 05/10/12 HOLD REFILL 1 USER,PHARMACY |\n| Comments: Rx placed on HOLD (Reason: BAD ADDRESS) and removed from |\n| SUSPENSE - HOLD COMMENTS ENTERED BY THE USER MANUALLY. |\n| ... |\n| 9 05/10/12 UNHOLD REFILL 1 USER,PHARMACY |\n| Comments: Rx Removed from HOLD - UNHOLD COMMENTS ENTERED BY THE USER|\n| WHEN REMOVING THE RX FROM HOLD. |\n\n
\nThis patch resolves the following issue:\n \nUsers receive a message in error while entering the dosage in Patient\nPrescription Processing.\n\n
\nThe same last 4 digits of the SSN prints for every patient with Non-VA \nmeds and no prescriptions when running the Poly Pharmacy Report for ALL \npatients.\nAn undefined error occurs when running the Poly Pharmacy Report for one \npatient that has Non-VA Meds and no prescriptions.\nThe display of the CMOP suspense date is truncated on a reinstate.\n\n
\nThis build is to be installed immediately after PSO*7.0*390 to\n3. Corrected a potential SUBSCRIPT error reported by test site (Boston) \n (CCR6212). \ncorrect a potential undefined error when renewing prescriptions\nwithout drug allergies. CCR6153.\n \n2. Updated the second lines of the following routines: \n a. Added patch number 388 to 2nd line of PSORENW and fixed typo. \n b. Added patch number 387 to 2nd line PSORXI (no code changes needed). \n (CCR6213). \n \n\n
\nAn incorrect message diplays in the message box while viewing a prescription\nin the following option: PSO VIEW.\n\n
\nThis patch will resolve the issue where the LAST LOCAL NDC code is being \nstored in the NDC BY OUTPATIENT SITE sub-file of the DRUG file for non\nE-PAYABLE drugs.\n\n
\nThis patch contains a fix for the issues summarized below:\n 1. Undefined error during OPAI HL7 generation for Other Language Sig.\n 2. Noun missing from sig on label when Print from Suspense\n\n
\n \nensures that in this case, the second user will get the duplicate drug\ncheck, and will only be allowed to continue if the first prescription\nis discontinued.\n \n2) This patch fixes a problem that can occur when using the Pull Early\nfrom Suspense [PSO PNDRX] option. If a specific prescription is pulled,\nand the prescription number entered is also the same internal entry\nnumber for another prescription that is also suspended, the entry\nthat matched the internal number will be pulled from suspense, instead\nof the entry that matched the external number. This patch fixes the\n \nproblem.\n \n3) A problem has been reported with the Queue Background Jobs [PSO\nAUTOQUEUE JOBS] option. There are times when some of the options that\nthis option presents for scheduling or re-scheduling will not appear. This\npatch fixes the problem, so now all of the options will appear for\nscheduling or re-scheduling.\n \n4) This patch addresses some problems that can occur when processing\ntwo or more refills for the same prescription in the same ListMan\n1) This patch fixes a problem of a patient possibly having two active\nsession while using the Patient Prescription Processing [PSO LM\nBACKDOOR ORDERS] option.\n \n a) If two or more refills are requested for the same prescription and\n none of the fills are auto-suspended, and the labels are queued to\n print, all of the labels will indicate that it is a label for the\n last fill, and that last fill information will print on the label.\n This patch will fix this problem by printing the appropriate fill\n information on the labels.\n \nprescriptions for the same drug. If two Outpatient Pharmacy users have\n b) If two or more refills are requested for the same prescription, and\n the last fill is auto-suspended prior to exiting the session, then\n "S" for Suspend is entered at the label prompt, the fill that is\n currently suspended will be overwritten in suspense, and only that\n last fill will print from Suspense. With this patch, a warning will\n be given after "S" is entered at the label prompt for each duplicate\n request, and the user will be given the opportunity to print each of\n those fills locally.\n \n c) If the first fill of a prescription is requested, and it does not\nthe same patient profile on the screen in the Patient Prescription\n get auto-suspended at the time of the request, but eventually will\n be auto-suspended for Consolidated Mail Outpatient Pharmacy\n (CMOP) upon exiting the session for that patient,\n and then another fill is requested and it is auto-suspended for CMOP,\n then upon exiting the session, the first fill request will then be\n auto-suspended for CMOP, overwriting the second request, and a\n fill will be bypassed. With this patch, the second fill will\n not be allowed, since the first fill will be auto-suspended for\n CMOP upon exiting the session.\n \nProcessing [PSO LM BACKDOOR ORDERS] option, the first user can enter a\n5) When a prescription is renewed through Pharmacy, if the prescription\nthat is being renewed has a suspended refill that has not yet printed\nfrom suspense, in addition to that prescription being marked discontinued,\nthat refill also gets deleted. If that same prescription would have been\nrenewed through Computerized Patient Record System (CPRS), when that\nrenewal is finished in Pharmacy, the renewed prescription would be\nmarked discontinued, but the refill would not be deleted. This patch\nprovides the functionality to delete the refill in this case, which\nmakes it consistent with renewals initiated through Pharmacy.\n \nprescription then exit the option, then the second user can enter a\n6) When a prescription is discontinued, if that prescription was never\nfilled locally, but filled only through CMOP, it's possible that when\nviewing that discontinued prescription, the Last Fill Date is incorrect.\nThis patch resolves the problem.\nprescription for the same drug and not get the duplicate drug check,\nthereby creating two active prescriptions for the same drug. This patch\n\n
\nThis patch deals the following issue:\nCS vault updates more than once if the user fails to enter a\nreason for removing the Rx copay\n\n
\nUsers get an "end of file" error after running the TRICARE CHAMPVA\n Bypass/Override Report\n\n
\nWhen processing Pending Orders in Outpatient Pharmacy, the system hangs\nif any word in the Provider Comments is longer than 60 characters and\nhas a special delimiter (;,=:) after character position 57. If this \nprocess continues to run, a <FILEFULL> error will occur.\n\n
\nThe DISCONTINUE PRESCRIPTION(S) option aborts when a prescription is \nprocessed on a deceased patient.\n \nUser is able to discontinue a prescription that has been "marked for \ndeletion". This should not be allowed.\n\n
\nThis patch will resolve the issue when a user edits the first ROUTE of a \ncomplex prescription from ORAL to SUBLINGUAL, prior to accepting, the \nUNDER THE TOUGUE will echo to the second occurrence.\n\n
\nThis patch is being released as part of the DEA e-Prescribing of\n -----------------------------------------------------------------\n \n Data Name CPRS File Pharmacy Pending File\n --------- --------- ---------------------\n QTY PRESCRIBED 15 30\n \n \n If the error code is related to 'certificate expired', the pending \n order will be processed (will not be auto discontinued) and a \n notification will be sent to the provider with the message, "DEA\n certificate expired. Renew your certificate."\n KERNEL V. 8.0 XU*8*580\n \n2. When finishing a pending CS order, if the user does not hold the new \n PSDRPH security key, the order will be marked as 'Non-Verified'.\n \n3. To verify a 'Non-Verified' CS order, PSDRPH security key is now\n required.\n \n4. To discontinue a pending CS order, PSDRPH security key is now required.\n \n5. The pending order screen will now display the provider's DEA/VA #, the \n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*166\n DETOX# (if available) and the site address.\n \n6. When finishing a new pending CS order, the orderable item, dosage, \n provider name, or the number of refills will not be allowed to be \n edited. Also, if the changes to the dispense drug would result in\n a new order being created, this will not be allowed for digitally \n signed orders. The user WILL be allowed to select other dispense drugs \n for the same Orderable Item as long as it does not change the \n prescribed dosage.\n \n COMPUTERIZED PATIENT RECORD SYSTEM (CPRS) V. 3.0 OR*3*306\n7. When finishing a new pending CS order, the days supply or the quantity\n will not be allowed to increase, but can be decreased. If the days\n supply is decreased, the number of refills will also be adjusted \n accordingly depending on the drug setup (maximum refills, not \n refillable etc).\n \n8. In patch PSO*7*99, a change was made for pending orders not to \n recalculate the quantity for CS drugs on selecting a different strength\n of the same drug and resulting in the same prescribed dosage. This\n change is removed in this patch.\n CONTROLLED SUBSTANCES (CS) V. 3.0 PSD*3*73\n \n9. When finishing a pending CS order or verifying a CS order by the PSDRPH\n key holder, any edit to some of the key fields like dispense drug,\n dosage, dispense units, issue date, day's supply, quantity or number of\n refills, will now be captured and stored in the activity log.\n \n10. In the Complete Orders From OERR [PSO LMOE FINISH] option, a new sort \n selection, 'CS' is included to select digitally signed CS orders \n separately.\n \n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*391\n11. A new field BACKDOOR SIGNATURE STATUS (#311) is being added to the \n PRESCRIPTION file (#52) and will be set to '1' to indicate that the CS\n order was entered via pharmacy backdoor and was not digitally signed.\n \n12. A new field, DIRECTIONS FOR USE (#120) is being added to the PENDING\n OUTPATIENT ORDERS file (#52.41) to store the raw HEALTH LEVEL SEVEN\n (HL7) dosage data as sent from CPRS. This will be used to validate the\n integrity (hash count) against the CPRS digitally signed orders.\n \n13. Currently, the pending order screen displays only the number of \n \n refills ordered by the provider. For digitally signed orders, this\n is modified to include the days supply and the quantity. Here is a\n screen capture:\n (6) Issue Date: SEP 17,2012 (7) Fill Date: SEP 17,2012\n (8) Days Supply: 45 (9) QTY ( ): 45\n Provider ordered: days supply 45, quantity 45 & refills 1 \n (10) # of Refills: 1 (11) Routing: WINDOW\n \n14. The protocols PSO LM ACCEPT and PSO LM RENEW MENU are being modified\n to add code to the SCREEN field (#24) and the HEADER field (#26) of\nNote:\n the PROTOCOL file (#101) to ensure users are limited to ListMan\n actions based on their security key.\n \n15. As part of this project, Kernel patch XU*8*580 introduced the \n following new fields to the NEW PERSON file (#200). Apart from the \n DEA#/VA# requirement, DEA further classifies what CS schedule a\n provider is authorized to write. \n \n 55.1 SCHEDULE II NARCOTIC (S), [PS3;1]\n 55.2 SCHEDULE II NON-NARCOTIC (S), [PS3;2]\n1. A new security key named "PSDRPH", has been sent out in the Controlled\n 55.3 SCHEDULE III NARCOTIC (S), [PS3;3]\n 55.4 SCHEDULE III NON-NARCOTIC (S), [PS3;4]\n 55.5 SCHEDULE IV (S), [PS3;5]\n 55.6 SCHEDULE V (S), [PS3;6]\n \n If any one of the above fields are populated for a provider then when\n placing a new order in backdoor pharmacy, the software will now check\n for the drug schedule with the provider privileges. If the provider\n does not have the credentials to write such orders then the software\n will display a message (as shown below) and will not allow the \n Substances patch PSD*3*76, which is a required patch for this patch.\n selection that provider.\n Example: When the provider does not have schedule 2 privileges, this\n message is displayed: \n "Provider not authorized to write Federal Schedule 2 prescriptions."\n \n16. When placing an order for a CS Detoxification drug, the software will \n now check for a valid Detoxification number for the provider. If the \n provider does not have a Detoxification number then the software will \n display a message "Provider must have a DETOX# to order this drug."\n \nControlled Substances (CS) project using Public Key Infrastructure (PKI)\n This key authorizes pharmacists to finish/verify a digitally signed\n17. The Released and Unreleased Prescription Report [PSO RELEASE REPORT] \n is being modified to include CS as a selection to the input. The drug\n name and CS schedule is being added to the output. Here are the\n changes: \n \nYou are currently logged in under the CHEYENNE VAM&ROC division.\nDo you want to select a different division? NO// \n \nDo you want ONLY Unreleased Prescriptions? NO// \nInclude (C)S Rx only, (N)on CS Rx only, or (B)oth (C/N/B): B// Controlled \n Schedule II-V CS orders placed via CPRS and should be assigned to\nSubstances Rxs Only\n \nSelect controlled substance schedules\n \n Select one of the following:\n \n 1 SCHEDULES I - II\n 2 SCHEDULES III - V\n 3 SCHEDULES I - V\n \n registered pharmacists working with Schedule II-V drugs.\nSelect Schedule(s): 3// \n \nThe report currently shows the count of unreleased and copay\nprescriptions, but not the count of released prescriptions. The report is\nmodified with this patch to include the count of released prescriptions.\n \n18. The following options are being modified to include the\n DETOX/MAINTENANCE ID NUMBER field (#53.11) and the DEA EXPIRATION DATE\n field (#747.44) of the NEW PERSON file (#200) as part of the screen. \n The DEA EXPIRATION DATE field will be prompted only if the PROVIDER\n \n TYPE field (#53.6) of the NEW PERSON file (#200) is marked as "FEE \n BASIS".\n \n Add New Providers [PSO PROVIDER ADD]\n Edit Provider [PSO PROVIDER EDIT]\n View Provider [PSO PROVIDER INQUIRE]\n \n19. Currently, the default days supply for all drugs is set from the DAYS \n SUPPLY field (#3) of the RX PATIENT STATUS file (#53) up to a maximum\n of 90. With this project, the default for CS schedule II-V drugs will\n2. Patches PSO*7*391 and PSD*3*73 are being released in the Kernel \n be set to 30 or from the DAYS SUPPLY field (#3) of the RX PATIENT\n STATUS file (#53) if it is less than 30. Also, the Integration Control\n Registration #3278 that returns days supply (DSUP^PSOSIGDS) to CPRS is\n modified to return 30 or from the DAYS SUPPLY field (#3) of the RX\n PATIENT STATUS file (#53) if it is less than 30 for CS schedule II-V\n drugs.\n \n20. The pharmacy release slip portion of the Laser Label is being \n modified to include the text "(DSIG)" or "(NOT DSIG)" after the\n patient's name to indicate that the prescription is digitally signed\n Installation and Distribution System (KIDS) multi-build distribution\n or not digitally signed.\n \n21. This patch addresses the issue reported in REMEDY ticket #595795, to\n ensure that when editing an orderable item/dispensed drug, the \n instruction field is displayed only when editing the pending order \n and not when editing an active or non-verified order.\n \n22. The Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option that \n currently runs as a nightly job is being modified to check for the\n Institutional DEA 'expiration date'. If the expiration date is within\n CPRSV29_PSO_PSD. \n 30 calendar days or past expiration then a mail message will be\n generated and sent to PSDMGR key holders. Here is an example when the\n expiration date is within 30 days:\n \nSubj: 500:Institutional DEA Expiration Date is about to expire [#140331]\n03/20/12@11:57 3 lines\nFrom: POSTMASTER In 'IN' basket. Page 1 *New*\n-----------------------------------------------------------------------\n \nPlease update Institutional DEA Certification Date. Will expire on \n \n3/24/12.\n \n******************************\n \nHere is an example when the DEA Expiration Date is past expiration date:\n \n \nSubj: 500:Institutional DEA Expiration Date has expired [#140333]\n03/20/12@12:08 3 lines\nFrom: POSTMASTER In 'IN' basket. Page 1 *New*\nThe following modifications and enhancements are included in this patch \n----------------------------------------------------------------------\n \nPlease update Institutional DEA Certification Date. Expired on 2/19/12.\n \n**********************************\n(PSO*7*391):\nto satisfy requirements requested by the Drug Enforcement Administration\n \n1. When processing a digitally signed pending order, the integrity of the \noriginal order placed in CPRS is now being checked to ensure that the data\nfields listed below are not altered from the time the order is signed in\nCPRS and later selected for processing in backdoor pharmacy. This is done\nby passing the data elements listed below to a Kernel Application\nProgramming Interface (API), Integration Control Registration (ICR) #3539,\nalong with the CPRS hash count, provided by ICR #5709. The Kernel API\ncompares these two hash values and returns an "OK" if the pending order is\nunaltered or otherwise, returns a "-1^error code^error message."\n(DEA).\n \nExample: "-1^89802016^Mismatched digital signature hash values."\n \nThese are the fields used in the hash check:\n Date of Issuance\n Full Name and Address of the Patient\n Drug Name\n Quantity Prescribed \n Directions for Use\n Prescriber Name \nThe applications involved in this project along with their patch numbers \n Prescriber Address (site address) \n Prescriber DEA / VA Registration Number\n Order Number (CPRS)\n \nThe Kernel API will also check for the validity of the DEA certificate. If\nthe certificate is revoked or expired then the API will return the\nappropriate error code.\nIf the error code is related to hash mismatch or the DEA certificate is\nrevoked then the following events will be triggered during pending order\nprocessing:\nare listed below and the same order should be followed when installing \n The order will be auto discontinued.\n First line of the pending order screen will have the message "Digital\n Signature Failed: Corrupted (Hash mismatch)" or "Certificate revoked"\n concatenated with "Order Auto Discontinued", and the message will be\n highlighted in reverse video.\n The status bar of the screen will have the message "Signature Failed: \n Corrupted (Hash mismatch)" or Certificate revoked."\n A mail message will be generated to the holders of the PSDMGR key \n notifying that the order has been auto discontinued (similar to the \n example listed below).\nthe patches.\n If the discontinuation is due to a hash mismatch as a result of altering\n one of the fields listed above then the mail message will show the\n altered fields with the discrepancies. Here is an example:\n \n Subj: DIGITALLY SIGNED NEW ORDER AUTO DISCONTINUED [#196353] \n 03/20/12@17:1024 lines\n From: POSTMASTER In 'IN' basket. Page 1 *New*\n \n -----------------------------------------------------------------------\n \n \n Following order was auto discontinued when finishing a pending order \n due to Corrupted (Hash mismatch) - 89802016\n \n Division : GREELEY CLINIC\n CPRS Order # : 5587651\n Issue Date : MAR 7,2012\n Patient : TEST,PATIENT (0908)\n Address : P.O. BOX 31\n LAPORTE, CA 95981\n Drug : CODEINE SULFATE 60MG TAB\n APPLICATION PATCH\n Dosage Ordered: 120(MG)\n Dosage Form : TABLETS\n Quantity : 54\n Provider : TEST,PROVIDER\n DEA# : TA1234563\n Site Address : 2360 E PERSHING BLVD\n 2360 East Pershing Boulevard\n CHEYENNE\n \n Differences in CPRS and Pharmacy Pending File\n\n
\nThis is a follow-up patch for PSO*7*391 that was part of Computerized \n"L" as "M" when "L" is found in the duration field.\nPatient Record System (CPRS) Graphic User Interface (GUI) v29. CPRS GUI \nv29 will be a phased implementation and therefore, this patch, PSO*7*426,\nshould be installed after CPRS GUI v29 bundle is installed.\n \nHines reported that when finishing a complex pending order if 'month' is\npart of duration then the order is discontinued due to hash mismatch. This\nis due to pharmacy storing 'month' as "L" and CPRS storing as "M". This\npatch resolves this problem by tweaking the hash check code to represent\n\n
\n1. This build is to be installed immediately after PSO*7.0*390 to \n correct an issue where allergy labels are printing each time an allergy\n order check occurs. The allergy label should only print when a user\n has not been assigned the PSORPH key. (CCR6452). \n\n
\nThis patch will resolve the following issues: \n1) DUZ is printing on the label instead of co-signer.\n2) To change the USPS forwarding terminology on labels in Vista.\n3) Remove "REGULAR MAIL" from the shipping portion of laser labels in\n VistA.\n\n
\nEPHARMACY OPERATING RULES\n\n
\nThis patch is part of the CMOP - Controlled Substance Rxs enhancements.\nThe Installation Guide for the CMOP - Controlled Substance Rxs project can\nbe obtained on the VISTA Consolidated Mail Outpatient \nPharmacy web page. The address is http://vista2.domain.ext/cmop/.\n \nThe Installation Guide is also available on the ANONYMOUS.SOFTWARE\ndirectory at one of the following Office ofInformation (OI) Field Offices.\nThe file name is CMOPCS_IG.PDF.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\nIt modifies functions within the Outpatient Pharmacy application to\n Albany 152.127.1.5 anonymous.software\n Hines 152.129.1.110 anonymous.software\n Salt Lake City 152.131.2.1 anonymous.software\n \nNOTE: Since future patches may be dependent on this patch, it should be\ninstalled even if you are not using the CMOP software or planning to\ntransmit controlled substances to the CMOP facilities. The installation\ninstructions will provide further guidance for this situation.\n \n \nsupport the transmission of controlled substance prescriptions to the\n1. This patch adds Controlled Substance functionality to the Released and\nUnreleased Prescription Report[PSO RELEASE REPORT]. The user is now also\npresented with sorting criteria to sort by:\n \n'C' 'Controlled Substance Rxs Only'\n'N' 'Non Controlled Substance Rxs only'\n'B' 'Both Controlled Substance and Non Controlled Substance Rxs'\n \n2. This patch adds a new menu option CMOP Controlled Substance Rx\nDispense Report[PSO CMOP CS RX DISPENSE REPORT] as a part of the Output\nConsolidated Mail Outpatient Pharmacy facilities.\nReports [PSO OUTPUTS] menu of Outpatient Pharmacy. The user is prompted\nfor criteria concerning:\n \n \n[Single division sites will not see the following question.]\nPrint for (A)ll or a (S)ingle division? (A/S) S//\n \nSelect one of the following: 1//\n1. Sort by Release Date\n2. Sort by Drug\n \nStart Date:\nEnd Date:\n \nThe new report sorts by division and prints out the following fields:\nRelease date, RX #, Fill #, Drug, Patient with SSN(last four), CMOP\nStatus, and CMOP Facility.\n \nPRESCRIPTION File (#52)\n \nRelease Date RELEASED DATE/TIME (#31) for Original RX\nThis patch will be installed in conjunction with three other patches\n or\n REFILL multiple (#52) for Refills\n RELEASED DATE/TIME (#17)\n \nRX # RX # (.01)\n \nFILL # 0 for Original RX\n IEN of refill for\nRefills\n \n(PSX*2*23, PSD*3*21, and PSS*1*28). Refer to the CMOP - Controlled\nDRUG DRUG (#6)\n \nPatient with SSN PATIENT (#2)\n \nCMOP Status CMOP EVENT multiple (#400)\n STATUS (#3)\n \nCMOP Facility CMOP EVENT multiple (#400)\n TRANSMISSION NUMBER (#01) :\n CMOP TRANSMISSION FILE #550.2\nSubstance Rxs Installation Guide for installation instructions. \n CMOP SYSTEM (#3)\n \n \n3. This patch adds the display of the PRESCRIPTION file (#52) CMOP EVENT\nmultiple (#400) fields CARRIER (#10) and PACKAGE ID (#11) to the View\nPrescriptions [PSO VIEW] option of Outpatient Pharmacy.\n \n4. This patch also corrects the following problem reported.\n \nProblem: The CMOP Event Log in the View Prescriptions [PSO VIEW]\n \noption displays the release of a previous event when the current even has\nno release date.\n \nResolution: The code has been changed to clear the previous value and\ndisplay "Not Released" when the prescription is yet to be released.\n\n
\nThe Causative Agent showing in the Allergy Order check in Outpatient\nPharmacy is not correct.\n\n
\nVIC CARD ENHANCEMENT\nRefer to patch PSO*7*434 in the FORUM Patch Module for a complete\ndescription.\n\n
\nThis patch is part of a combined build that makes up the release of \nfunctionality, the Single Dose information will be displayed to\nthe user. The following scenarios describe the types of messaging added: \n \n 1. If the dosage entered passes the dosing checks, no message will be\n displayed.\n 2. If the dosage entered is too high or too low, the Single Dose warning\n message will be displayed.\n 3. If the dose checks were not able to be performed, a generic message\n will be displayed notifying the user that a manual check needs to be\n completed to verify appropriate dosing.\nMEDICATION ORDER CHECK HEALTHCARE APPLICATION (MOCHA) 2.0.\n \nMOCHA 2.0 encompasses Pharmacy Data Management (PDM) patch PSS*1*160\nand a combined build for Outpatient Pharmacy patch PSO*7*372 and \nInpatient Medications patch PSJ*5*252.\n \nThis patch group adds dosing checks that implements a new system that uses\ndata from First DataBank (FDB). In this initial phase of dosing\n\n
\n \nOutpatient Pharmacy for a pending order scrolls off the screen. Examples\nof the message would be "FDB dosing information is not available for this\ndrug" or "Drug not matched to NDF".\n \nFor Max Single Dose messages, the pharmacist is correctly required to sign\nthe order and enter an intervention. Pharmacists do have the opportunity\nto see the CPRS dosing message when the pending order is first opened in\nOutpatient Pharmacy. The CPRS message is the same message the scrolls off\nthe screen.\n \nThis patch is a MOCHA 2.0 fast track release patch to correct an issue \nTo correct this, an "Enter to continue" will be displayed to keep the \ndose message from scrolling off the screen when the number of \ndisabilities to be displayed exceeds the screen length.\nfound late in IOC testing process for MOCHA 2.0. The following is the \nneeded modification:\n \n \n1. For order level dosing order check messages that do not require the\npharmacist to enter a signature code on the order and where there are more\nthan three disabilities defined for the patient, the dose message in\n\n
\nThis patch resolves the following issues:\nPrevent labels for patients whose mail is routed from being marked as a\nforeign address.\n \nA patient's prescription is changing from Co-pay to No Co-pay when\nit is released.\n \nThe Sig does not match between the prescription and the order.\n\n
\nThis patch resolves the following 3 issues:\n1. Detailed display in CPRS for an IV shows data from another\n prescription.\n \n2. The algorithm used to determine the # of refills for a pending order\n does not take into account the "Rx patient status".\n \n \n3. Label is incorrectly designated a REPRINT after printing from suspense.\n\n
\nThis patch PSO*7*313 includes the following enhancements:\nThe Outpatient Pharmacy application currently allows the entry of a \n have the letter 't' postfix to the RX # as seen below (entry #1): \n \n : : :\n ISSUE LAST REF DAY \n # RX # DRUG QTY ST DATE FILL REM SUP \n -------------------------------ACTIVE------------------------------- \n 1 100005024t AMOXAPINE 50MG TAB 30 S 09-26 09-26 2 30 \n 2 100005022 AMOXICILLIN 250MG CAP 30 A 08-18 08-18 11 30 \n 3 100005035 KALETRA 3 A 09-29 09-29 0 3 \n : : :\ncomplex order, which contains a "THEN" conjunction. This type of order is\n \n Note: A prescription can be unmarked as Titration/Maintenance by \n invoking the same TM action on an already marked prescription. \n \n \nb. A new hidden action is being introduced in the Patient Prescription \n Processing [LM BACKDOOR ORDERS] option called TR (Convert \n Titration Rx). This action will populate the new field MAINTENANCE \n DOSE RX (#45.2) in the PRESCRIPTION File (#52). \n When a titration to maintenance prescription needs to be \nallowed to leave the Duration field preceding the "THEN" conjunction \n refilled so the patient can continue on the Maintenance Dose \n this option will allow the users to create a new prescription with \n the maintenance dose only. The process works similar to copying an \n existing prescription, however it can only be used on prescriptions \n with the following characteristics: \n \n - Rx is a complex order with a THEN conjunction\n - Rx was not digitally signed\n - Rx is released \n - Rx status is ACTIVE \nas null. This null duration field is causing issues when the Outpatient\n - Rx does not have refills previously ordered \n - Rx # Of Refills is greater than 0 (zero) \n \n Before the new Maintenance Rx can be accepted the Pharmacist is \n prompted to validate the QTY field for the new Rx, which may or may not\n be automatically re-calculated. Only the last dose from the original\n prescription is carried over to the new Maintenance Rx and the # of \n Refills field is decreased by 1 because the new Maintenance Rx counts \n as a fill. The Fill Date for the new Maintenance prescription is \n automatically set with the next possible fill date from the existing\nPharmacy order was being transferred to an Inpatient Medication Order(s).\n prescription, which can be changed by the pharmacist.\n Once the pharmacist verifies the information for the Maintenance Rx is \n accurate they can accept the Maintenance Rx. This action will trigger \n a Duplicate Drug check against the original complex order, which must \n be discontinued before the new Maintenance Rx can be accepted. \n After the new Maintenance Rx is accepted it will have the new \n indicator 'm' on the right side of the Rx # in the patient's Medication\n Profile as seen below (entry #1):\n \n : : :\nThe default stop dates were for thirty (30) days for the two (2) new\n ISSUE LAST REF DAY \n # RX # DRUG QTY ST DATE FILL REM SUP \n -------------------------------ACTIVE------------------------------- \n 1 100005436m AMOXAPINE 50MG TAB 30 S 09-26 09-26 1 30 \n 2 100005022 AMOXICILLIN 250MG CAP 30 A 08-18 08-18 11 30 \n 3 100005035 KALETRA 3 A 09-29 09-29 0 3 \n : : :\n \nc. The new Titration/Maintenance indicator (t/m) will be included in the \n following menu options where the prescription number is displayed: \ninpatient orders created and the Start/Stop dates in the sequence were\n \n View Prescriptions [PSO VIEW] \n Patient Prescription Processing [PSO LM BACKDOOR ORDERS] \n Complete Orders from OERR [PSO LMOE FINISH] \n ePharmacy Medication Profile (View Only) [PSO PMP] \n Medication Profile [PSO P] \n \nd. External refill requests such as from AudioFax and Internet will not \n be processed for Titration/Maintenance marked prescriptions. \n \nincorrect. The pharmacist did not notice the incorrect dates and finished\n Subj: ALBANY External Application Refills: Not processed List \n [#101509] 01/28/09@13:52 11 lines\n From: POSTMASTER In 'IN' basket. Page 1 \n \n-------------------------------------------------------------------------\n Refills Not Processed Report for the ALBANY Division. \n \n The following refill requests were not processed: \n \n Patient: OPPATIENT,TWO (9999) \noff the orders. Upon transfer of a complex order from Outpatient Pharmacy\n \n Rx #: 100005122 (REF #1) Qty: 55 \n Drug: ZINC SULFATE 66MG TAB \n Reason: 'Titration/Maintenance Rx' cannot be refilled. \n \ne. CPRS refill requests will not be automatically processed for\n Titration/Maintenance marked prescriptions. The refill request will\n remain in the patient's Medication Profile as PENDING and the mailman\n message above (item d) will also be sent to PSOAUTRF security key\n holders. \nto Inpatient Medication order(s), the resulting order will start at the\n \nf. The activity logs for both Titration and Maintenance Rx's will record \n the corresponding Titration and Maintenance Rx # if they exist as seen \n below: \n \nTitration Rx: \n------------\n# Date Reason Rx Ref Initiator of Activity \n====================================================================== \n1 09/29/08 EDIT ORIGINAL OPUSER,ONE Comments: \n 1. Complex Orders Duration Field \nfirst step rather than continue at the step the patient was at as an\nMaintenance\nDose Rx: 100005130 \n \n \nMaintenance Rx: \n--------------\n# Date Reason Rx Ref Initiator of Activity \n====================================================================== \n1 09/29/08 EDIT ORIGINAL OPUSER,TWO Comments: \nTitration Dose Rx: 100005392\nOutpatient. It looks like a new complex order to the finishing pharmacist,\n \n \ng. The VistA Integration Control Registration (ICR) #2398 provided to \n Computerized Patient Record System V. 1.0 (CPRS) was modified to \n prevent the renewal of a Titration dose order with the following \n message: \n \n "Prescription was marked as Titration to Maintenance Dose by Pharmacy \n and cannot be renewed. To repeat the titration, enter a new prescription\n or copy the prior titration order. To continue the maintenance dose, \nsince the Start date is populated with the date of finishing so that the\n refill this prescription if refills are available or enter a new\n prescription for the maintenance dose."\n \n \nh. When using the Barcode Batch Prescription Entry option \n [PSO BATCH BARCODE], if the prescription has been marked \n as a Titration/Maintenance Rx, and the user attempts to \n renew or refill the prescription, the following message \n will display: \n \npatient would be started on the first step, which may not be correct.\n For a renewal: \n "Rx# XXXXXX is marked as Titration Rx and cannot be renewed." \n \n For a refill: \n "Rx# XXXXXX is marked as Titration Rx and cannot be refilled." \n \n \ni. The PSO HIDDEN ACTIONS Protocol in the PROTOCOL File (#101) \n will be modified to include the two new Hidden Actions \n introduced by this enhancement. PSO LM BACKDOOR MARK AS \nThis would pertain to complex orders that taper or titrate doses up or\n TITRATION and PSO LM BACKDOOR TITRATION RX REFILL are both \n new protocols added to the PROTOCOL File (#101). \n \n \n \n ****************************** IMPORTANT ******************************\n The enhancements related to Titration/Maintenance dose Rx are made only \n for Outpatient Pharmacy package. The corresponding changes to CPRS \n package are not included at this time. Therefore, the CPRS Order Copy and\n Order Change functionalities will continue to function as is. \ndown and potentially impacts patients by receiving too much or too little\n Furthermore, there will be no indication of a Titration/Maintenance order\n in the CPRS application.\n *************************************************************************\n \n3. Remedy Ticket #1022059 \n This patch fixes an issue that could create duplicate prescriptions on \n a patient profile. When a complex order is copied and the duration \n field is edited, upon accepting the order, the message to discontinue\n the original order is not triggered. This causes duplicate \n prescriptions to appear on the patient profile. This patch corrects\nmedication. \n this problem by prompting the user to discontinue the original order.\n \nThe Outpatient Pharmacy is being modified to require the entry of a \nduration for a dose preceding a THEN conjunction if the schedule for such\n 2. Titration/Maintenance Rx \ndose is not a ONE-TIME type schedule. If the dose preceding the THEN\nconjunction is a ONE-TIME type schedule the software will continue to\nallow the Duration field to be left blank (optional). The corresponding\nchange to CPRS will be done in a future CPRS patch.\n \nExample of an acceptable SIG ('NOW' is ONE-TIME type schedule): \n--------------------------------------------------------------\nTAKE ONE TABLET BY MOUTH NOW THEN TAKE TWO TABLETS EVERY 8 HOURS \n \nNo longer acceptable SIG ('Q4H' is not ONE-TIME type schedule): \n \n--------------------------------------------------------------\nTAKE ONE TABLET BY MOUTH EVERY 4 HOURS THEN TAKE TWO TABLETS EVERY 8 \nHOURS \n \nNote: The SIG above is not acceptable because it does not have a \n Duration for the first dose. In order to be acceptable the \n SIG above would have to have a duration like the one below: \n \n TAKE ONE TABLET BY MOUTH EVERY 4 HOURS FOR 3 DAYS THEN TAKE TWO \n TABLETS EVERY 8 HOURS \n1. Complex Orders Duration Field \n \nThe Duration field is not required for the dose following the last "THEN"\nconjunction. \n \nBelow is an example of a complex order being entered via Patient \nPrescription\nProcessing [PSO LM BACKDOOR ORDERS] \n \n : :\n VERB: APPLY \n================================\n ROUTE: PO// PO ORAL \n Schedule: QD (EVERY DAY) \n \n LIMITED DURATION (IN DAYS, HOURS OR MINUTES): \n CONJUNCTION: THEN \n \n Duration field required for the dosage entered prior to this THEN \n conjunction. \n \n \nThis Enhancement is related to Patient Safety Issue PSI-07-167 and Remedy \n LIMITED DURATION (IN DAYS, HOURS OR MINUTES): \n : :\n \n2. Titration/Maintenance Rx \n===========================\nThis Enhancement is related to PSI-06-176 and Remedy Ticket #168928. \n \nThe Outpatient Pharmacy (OP) application was modified to accommodate \nTitration/Maintenance prescription functionality. The existing software \npresented patient safety risks when prescriptions dispensed with a \nTicket # 203088. \ntitrating dose followed by a maintenance dose were being copied, renewed\nor refilled. The issue was that refills as well as the new prescriptions\n(derived from copy, renewals or edits) automatically carried over the\ninitial titrating dose into the new fill/prescription, which was not\nalways the user's intention. \n \nThe new functionality provides two steps for processing Titration/ \nMaintenance prescriptions.\n \na. First, the user will have the ability to mark prescriptions as \n \n 'Titration to Maintenance' when finishing prescriptions from CPRS as \n well as via the Patient Prescription Processing [PSO LM BACKDOOR \n ORDERS] option by invoking the new hidden action 'TM' - Mark Rx \n as Titration. This action will result in preventing the following \n actions to be taken on the prescription: Refill, Renewal (including \n via CPRS), Copy and editing of any field that requires a new Rx to be \n created. This action will also set the new field TITRATION RX FLAG \n (#45.3) in the PRESCRIPTION File (#52) as well as the new field \n TITRATION DOSE RX (#45.1) in the PRESCRIPTION File (#52). \n Prescriptions that are marked as Titration/Maintenance will \n\n\nThe Safety Updates for the Medication Prescription Management (SUMPM)\ninformation for purposes of their profession. The information must be\n9. Queue Background Jobs [PSO AUTOQUEUE JOBS]\n ------------------------------------------\n The Scheduled Batch Export [PSO SPMP SCHEDUED EXPORT] option mentioned\n above will be added to the list of options that can be edited via this\n option.\nreported using the American Society for Automation in Pharmacy (ASAP) data\nformat, which was developed by the Alliance of States with Prescription\nMonitoring Programs and the National Association of State Controlled\nSubstances Authorities.\n \nThe new menu called State Prescription Monitoring Program Menu [PSO SPMP\nMENU] can be found under the Supervisor Functions [PSO SUPERVISOR]\nmenu option. The following options will be available under this new menu:\n \nproject adds a new module to the Outpatient Pharmacy V. 7.0 application,\n1. View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] \n -----------------------------------------------------------\n This option is used for viewing or editing the SPMP parameters for a \n specific state. The following fields can be updated via this option:\n \n ASAP VERSION\n TRANSMIT RETURN TO STOCK*\n INCLUDE NON-VETERAN PATIENTS\n REPORTING FREQUENCY IN DAYS\n VMS LOCAL DIRECTORY\nwhich will be used for enabling the Veterans Health Administration (VHA)\n UNIX/LINUX LOCAL DIRECTORY\n WINDOWS/NT LOCAL DIRECTORY\n FILE NAME PREFIX\n FILE EXTENSION\n STATE FTP SERVER IP ADDRESS\n STATE FTP SERVER USERNAME\n STATE FTP SERVER PORT #\n STATE FTP SERVER PASSWORD\n STATE FTP SERVER DIRECTORY\n SFTP TRANSMISSION MODE\npharmacies to comply with Mandatory Reporting to State Controlled\n SFTP PRIVATE KEY TEXT**\n SFTP PUBLIC KEY TEXT**\n \n * Visible only if ASAP VERSION is 1995\n ** Visible only if SFTP TRANSMISSION MODE is set to A - AUTOMATIC \n \n2. View ASAP Definitions [PSO SPMP VIEW ASAP DEFINITIONS]\n ------------------------------------------------------\n This option allows the user to visualize the ASAP data format and the\n data elements reported to the states. It provides detailed information\nSubstance Rx Databases required by Consolidated Appropriations Act, 2012,\n about each segment and field for the ASAP format versions 4.0, 4.1 and\n 4.2.\n \n3. View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT]\n ----------------------------------------------------------------\n This option is used for visualizing a specific prescription and the\n data related to a specific fill that is transmitted to the state in the\n ASAP format.\n \n4. View Export Batch [PSO SPMP BATCH VIEW/EXPORT]\nPL 112-74. Also known as State Prescription Monitoring Program (SPMP), the\n ----------------------------------------------\n The information reported to the states are first compiled into a batch,\n which can be for a single prescription or a collection of prescriptions\n for a determined date range. This option allows the user to visualize \n information contained in one batch as well as the list of prescriptions\n in the batch. This option also allows the user to manually export the\n batch to the state.\n \n5. Export Batch Processing [PSO SPMP BATCH PROCESSING]\n ---------------------------------------------------\nprogram is a state electronic database which collects designated data on\n This option is used to monitor all the batches used to transmit data to\n the states. The user selects a date range and a list of batches is\n presented where the user can select to perform different actions on a\n specific batch.\n \n6. Scheduled Batch Export [PSO SPMP SCHEDULED EXPORT]\n --------------------------------------------------\n This option is used for running the automatic transmission to the\n states and should not be executed by the end-user directly. It will be\n automatically scheduled to run nightly and it will decide when to\ncontrolled substances dispensed. The states then distribute data from the\n transmit the data to the state based on the REPORTING FREQUENCY IN DAYS\n field (#3) of the SPMP STATE PARAMETERS file (#58.41) value for the\n state, which can be updated via the View/Edit SPMP State Parameters\n [PSO SPMP STATE PARAMETERS] option.\n \n7. Accounting Of Disclosures Report [PSO SPMP DISCLOSURE REPORT]\n -------------------------------------------------------------\n This option is used for generating a list of prescriptions transmitted\n to states. This option allows for a date range selection as well as\n one, multiple or all states and one, multiple or all patients. The list\ndatabase to individuals who are authorized under state law to receive the\n is sorted by state and then by patient. \n \n8. Unmark Rx Fill as Administered In Clinic [PSO SPMP UNMARK ADMIN CLINIC]\n -----------------------------------------------------------------------\n This option is used to unmark prescriptions as 'Administered In\n Clinic'. Administered in clinic prescription fills are not transmitted\n to the states. This option enables the user to unmark fills that have\n been mistakenly marked as 'Administered In Clinic' and subsequently\n transmit them to the state.\n \n\n
\n 1. Site reports that inactive orderable items are showing up as a choice for \n \n3. This patch corrects a problem where pharmacists without the PSOLOCKCLOZ key\nare not allowed to override Clozapine medication orders from CPRS when there\nare no recent lab data available. \n \n4. This patch corrects a problem when renewing prescriptions with cosigning \nproviders and the cosigning provider has changed from the previous renewed \nprescription. \n \n5. This patch corrects a problem where the Nature of Order retains an incorrect\nthe pharmacist when editing of verified or pending prescriptions. It does not\ndefault when discontinuing active orders while using the Copy (OP) [PSO LM BACKDOOR\nCOPY] action. \n \n6. This patch adds an order check for valid providers when the Copy (OP) [PSO\nLM BACKDOOR COPY] action. \n \n7. This patch corrects a problem when using the Discontinue Prescription(s) \n[PSO C] option to discontinue individual prescriptions. \n \n8. This patch corrects a possible %DSM-E-NUMBER, ILLEGAL NUMBER error. \neven distinguish active/inactive. This is creating confusion because the\n \npharmacist does not know which to choose. \n \n2. In the Clozapine ordering software an invalid check is done to determine if\nthe site is registered with the National Clozapine Center. The fields, *SITE\nDEA NUMBER (#1) and *SITE (NATIONAL NAME) (#2), in the OUTPATIENT SITE file\n(#59) are marked for deletion and should not be used. \n\n
\nThis patch addresses the following:\n2. Patch PSO*7*313, had this verbiage:\n "The Outpatient Pharmacy is being modified to require the entry of a \n duration for a dose preceding a THEN conjunction if the schedule for\n such dose is not a ONE-TIME type schedule. If the dose preceding the\n THEN conjunction is a ONE-TIME type schedule the software will continue\n to allow the Duration field to be left blank (optional)".\n \n It was supposed to allow a ONE-TIME type schedule to proceed without\n the duration, but it did not. This patch corrects this issue.\n \n1. New Jersey had an issue with the setup after the installation of\n patch PSO*7*408. When they tried to transmit Controlled Substances\n prescriptions to the State Prescription Monitoring Program (SPMP),\n there was an issue with the VMS local directory, "USER$:[EXTRACT.SPMP]"\n conversion to the Unix/Linux format, "/USER$/EXTRACT/SPMP". This patch\n fixes this issue.\n \n\n
\nThe new universal member ID# is not included in the description of\nacceptable criteria to select a patient at the VistA Outpatient\nselection prompt.\nDrug-Drug Interaction is not occurring with Non-VA Meds\n\n
\nThis patch will resolve the following issues.\nA foreign address is triggered for the Philippines when printing\nsuspense labels with a Routing of Mail.\nThe Help Prompt for the Label Date/Time in the Prescription file is \nincorrect.\nWhen editing the Refill Date on a prescription, the internal Fileman\ndate is stored in the Activity Log entry.\nUser without PSORPH key can put rx on hold using pharmacist reasons.\nThe finishing pharmacist's name appears in the released pharmacist's entry\n\n
\nA prescription that has been transmitted to the CMOP can be put on HOld.\n\n
\nThis patch is part of the Pharmacy Safety Updates project which was \n APPLICATION/VERSION PATCH\n SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66)\n in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA\n PRODUCT (#50.68) file. If alternate maximum values exist, the current\n limits will remain the same.\n \n3. Edit Prescriptions [PSO RXEDIT] option\n This option was also modified to accept the new maximum value for the DAYS\n SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66)\n in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA\n PRODUCT (#50.68) file. If alternate maximum values exist, the current \n -----------------------------------------------------------------\n limits will remain the same.\n \n4. Barcode Batch Prescription Entry [PSO BATCH BARCODE] option\n The renewal functionality within this option was also modified to accept\n the new maximum value for the DAYS SUPPLY field based on the limit set by\n the MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) or the MAXIMUM\n DAYS SUPPLY field (#32) in the VA PRODUCT (#50.68) file. If alternate\n maximum values exist, the current limits will remain the same.\n \n5. Prescription Management Data Compilation \n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444\n The algorithm used to compile prescription management data was modified to\n account for prescriptions with greater than 90 days supply. The OVER 90\n DAYS (#8) field in the OUTPATIENT PHARMACY MANAGEMENT DATA file (#59.12), \n which is used as a counter for the number of prescription fills with DAYS\n SUPPLY value greater than 90, will now be populated.\n \n6. Count of Prescriptions [PSO MGMT REPORT RX COUNTS] option &\n Count of Prescriptions [PSO MGMT MONTHLY RX COUNTS] option\n These daily and monthly reports have been modified to include a new column\n called ">90 DAY", as seen below. This column will display the total number\n INTEGRATED BILLING (IB) V. 2.0 IB*2*545\n of prescription fills with a DAYS SUPPLY value greater than 90, as shown\n below.\n \n 30 60 90 >90 EQ TOT TOT\n DAY DAY DAY DAY FLS METH RX EQ FL\n ...===========================================================...\n 1 3 0 1 11 0 5 11\n 0 0 1 2 14 0 3 14\n 0 0 0 0 0 0 0 0\n 0 0 0 0 0 0 0 0\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189\n ...=== ======= ======= ======= ======= ======= ======= =======...\n 1 3 1 3 25 3 8 25\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429\n INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313\n \n \nThe following New service Requests (NSRs), Remedy Ticket and Patient Safety\nestablished to address specific New Service Requests (NSRs) as well as a\nIssue (PSI) are being addressed by this patch:\n \n NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply\n ---------------------------------------------------------------------------\n The Outpatient Pharmacy and supporting VistA applications are being modified\n to allow dispensing of more than 90 day supply fill for outpatient \n prescriptions. The new limit will be 365 days and will be set for each drug\n individually. See below for more information on specific menu \n options related to this enhancement. \n \nRemedy Ticket and a Patient Safety Issue (PSI) related to the VistA Pharmacy\n PSI PSPO00002793 Patient Prescription Processing error, truncating the \n second character of the Days Supply\n Remedy 387051 Patient Medication Profile Bad Address Indicator display\n ----------------------------------------------------------------------------\n The Outpatient Pharmacy Medication Profile has a display problem for a\n prescription with the following characteristics: 2-letter status (e.g., DC), \n drug marked for Consolidated Mailout Outpatient Pharmacy (CMOP) and Bad\n Address Indicator. When a prescription with all three features is displayed\n the DAY SUP column value is being truncated as illustrated below where the\n Day Supply value is actually 90 and it displays as 9.\napplications as approved by the Health Systems Enterprise Systems Manager\n \n ISSUE LAST REF DAY\n # RX # DRUG QTY ST DATE FILL REM SUP\n --------------------------------DISCONTINUED--------------------------------\n 1 100005604$ TOBRAMYCIN 80MG/2ML INJ 100 DC>B01-21 01-21 0 9\n \n \nThis patch modifies the Outpatient Pharmacy application regarding the\nenhancements and issues listed above:\n \n(ESM).\n1. Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option \n a) The backdoor pharmacy was modified to accept the new maximum value for\n the DAYS SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY\n field (#66) in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32)\n in the VA PRODUCT (#50.68) file. If alternate maximum values do not\n exist, the current limits will remain the same.\n \n Note: The MAXIMUM DAYS SUPPLY field (#32) added to the VA PRODUCT file\n (#50.68) is being introduced by patch PSN*4*429, however it will\n not be populated initially by the Pharmacy Product System -\n \n National (PPS-N) as changes will be required to that application to\n edit and export this new field. \n \n b) The medication profile was modified to display the Bad Address Indicator\n in a different line in order to address the Remedy Ticket 387051 and \n Patient Safety Issue PSPO00002793 mentioned above. The indicator will be\n placed in the next line, as seen below.\n \n ----------------------------------ACTIVE---------------------------------\n 1 100005598 ALSEROXYLON 2MG TAB 400 A> 12-11 03-01 2 90\nThis project is comprised of patches from five different applications, as\n **Bad Address** \n 2 100005596 DESIPRAMINE 25MG TAB 90 DC 11-01 11-01 11 30\n **Bad Address** \n 3 100005601A NAPROXEN 250MG S.T. 170 HP>12-17 12-17 5 30\n **Bad Address** \n 4 100005595 TIMOLOL 0.25% OPTH SOL 10ML 90 S> 11-01 11-21 10 30\n \n \n c) The calculation of the number of refills for a prescription was modified \n to take into account the new maximum value allowed for the DAYS SUPPLY\nshown below:\n field. The current calculation (up to 90 days supply) will remain the\n same and a new formula will be introduced to calculate the number of\n refills for days supply values of 91 up to 365. The table below shows\n the number of refills allowed based on the days supply value:\n \n ---------------------------------+------------------------------------\n NON-CONTROLLED SUBSTANCES | CONTROLLED SUBSTANCES (NO CHANGE)\n ---------------+-----------------+------------------+-----------------\n DAYS SUPPLY | # OF REFILLS | DAYS SUPPLY | # OF REFILLS \n ---------------+-----------------+------------------+-----------------\n \n 1 - 59 | 11 | 1 - 59 | 5\n 60 - 89 | 5 | 60 - 89 | 2\n 90 - 91 | 3 | 90 | 1\n 92 - 121 | 2 | | \n 122 - 182 | 1 | | \n 183 - 365 | 0 | |\n ---------------+-----------------+------------------+----------------\n \n2. Complete Orders From OERR [PSO LMOE FINISH] option\n This option was modified to accept the new maximum value for the DAYS\n\n
\nME2 Follow Up build for known minor defects.\n\n
\n1) This patch will add functionality to the drug/class orders check to\nwas suspended locally instead of transmission to CMOP. PSO*7*39. \n \n'List of Rxs with CMOP Drugs Printed From Suspense'\n Option name: PSO SUCMOP \nPRINT REPORT\nThis utility will print a report of everything that has printed \nlocally that has a CMOP drug. This report is by start and end dates. The\nreport will list the Rx#, patient name, date printed from suspense, and the\ndrug. This report is printed by the division you have signed in under. \n \ndisplay the CMOP status of an Rx when entering new Rxs. \n PSO*7*39.\n \n'Re-Suspend Printed Rxs with CMOP Drugs'\n Option name: PSO SUCMOP RE-SUSLOCALCMOPPRI\nThis utility will allow sites to re-suspend those Rxs that list on the \nList of Rxs with CMOP Drugs Printed From Suspense report [PSO SUCMOP\nPRINT REPORT]. This utility will re-suspend to the date that it was originally\nsuspended to. It should not be necessary to edit the suspended date \nbecause all Rxs queued for CMOP transmission will be transmitted.\n \n \n PSO*7*39\n \n'Unprinted/Non-Transmitted Rxs Re-Suspend'\n Option name: PSO SUCMOP RESUSPENDNOTPRI\nThis utility will allow sites to re-suspend everything that has not printed\nand not already queued for CMOP. This utility can be queued to run in the\nbackground or while you wait. \n \n PSO*7*39\n2) This patch corrects a problem where an incorrect CMOP status is displayed\nnext to the Release date on the order display screen. \n \nCMOP Utilities Option name: PSO SUCMOP MENU \n \nThis menu will contain utilities to help the sites re-suspend those Rxs that\n\n
\nThis patch addresses 3 issues.\n \n 3) When editing a RX and allow to time out at Noun Prompt, nothing\n will be saved prior to the prompt.\n \n 1) When adding a new order via PSO LM BACKDOOR, if a user edits\n the data for the new order and then enters "^" to exit editing,\n the system cancels the order\n \n 2) In PSO PROVIDER EDIT, the user sometimes accesses fields which \n they should not be accessing. Additionally, using UP-ARROW\n jump does not always work.\n\n
\nThe State Prescription Monitoring Program (SPMP) Enhancement project was\nAfter PSO*7*408 was released it was identified during the implementation\n also to delete an existing SSH key pair. In addition, this new option will\n provide an extensive help text on how the SSH keys are used in the \n transmission process, which is shown below:\n \n Select one of the following:\n \n V View Public SSH Key\n N Create New SSH Key Pair\n D Delete SSH Key Pair\n H Help with SSH Keys\nphase that some states PDMPs had unique requirements that could not be\n \n Action: V// H Help with SSH Keys\n \n Secure SHell (SSH) Encryption Keys are used to automate the data \n transmission to the State Prescription Monitoring Programs (SPMPs). Follow\n the steps below to successfully setup SPMP transmissions from VistA to the\n state/vendor server:\n \n Step 1: Select the 'N' (Create New SSH Key Pair) Action and follow the\n prompts to create a new pair of SSH keys. If you already have an\nfulfilled by the functionality released in PSO*7*408 which caused the SPMP\n existing SSH Key Pair you can skip this step. You can check\n whether you already have an existing SSH Key Pair through the 'V'\n (View Public SSH Key) Action.\n \n Encryption Type: DSA or RSA?\n ----------------------------\n Digital Signature Algorithm (DSA) and Rivest, Shamir & Adleman (RSA)\n are two of the most common encryption algorithms used by the IT\n industry for securely sharing data. The majority of SPMP servers can\n handle either type; however there are vendors that accept only one\ntransmissions from sites in such states to be rejected. This patch\n specific type. You will need to contact the SPMP vendor support to\n determine which type to select.\n \n Step 2: Share the Public SSH Key content with the state/vendor. In order\n to successfully establish SPMP transmissions the state/vendor will\n have to install/configure the new SSH Key created in step 1 for\n the user id they assigned to your site. Use the 'V' (View Public\n SSH Key) Action to retrieve the content of the Public SSH key. The\n Public SSH Key should not contain line-feed characters, therefore\n after you copy & paste it from the terminal emulator into an email\n(PSO*7*451) will enhance the SPMP functionality to allow VHA to fulfill\n or text editor make sure it contains only one line of text (no \n wrapping).\n \n4. View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option\n -----------------------------------------------------------------------\n This option was modified to highlight custom Data Elements and Segments\n by changing the font color as well as by adding an '*' (asterisk) to the\n right of the Data Element or Segment ID.\n \n5. View/Export Batch [PSO SPMP BATCH VIEW/EXPORT] and Export Batch Processing\nspecific state requirements and successfully transmit data to those states\n [PSO SPMP BATCH PROCESSING] options\n --------------------------------------------------------------------------\n When exporting a batch through one of these two options the users will now\n have three different choices to execute the transmission: 'B' for \n Background (via TaskMan), which queues the transmission to be performed in\n the background through TaskMan; 'F' for Foreground, which executes the\n transmission in the foreground as it did before this patch and 'D' for\n Debug Mode (Foreground), which will execute the transmission in the\n foreground however it will display the sFTP debug steps, which can be very\n helpful for troubleshooting transmission problems. \nPDMPs. This patch also enhances the security of Secure SHell (SSH) Keys \n Before this patch the transmission was always executed in the foreground\n which made it difficult to troubleshoot issues with the transmissions, \n especially the scheduled transmissions, which are always executed in the\n background. Below is a screen capture of the prompt for choosing the\n transmission execution mode:\n \n Select Item(s): Quit// EXP Export Batch \n \n Indicate whether the transmission should be queued to run on the\n Background via TaskMan, on the Foreground (Terminal Screen) or in Debug\nmanagement by streamlining the SSH Key creating and restricting user access\n Mode (Foreground)\n \n Select one of the following:\n \n B Background\n F Foreground\n D Debug Mode (Foreground)\n \n Running Mode: F// \n \nto the Private SSH Key content. In addition, a few smaller miscellaneous\n6. PSO SPMP NOTIFICATIONS Mail Group\n ---------------------------------\n The existing mail group PSO SPMP NOTIFICATIONS released by PSO*7*408 will\n be modified from type PRIVATE to PUBLIC.\n \n7. SPMP Transmission Failed MailMan Message\n ----------------------------------------\n The Mailman message generated by the SPMP Scheduled Background Job as well\n as by the (B)ackground option mentioned above for exporting a batch to the\n state was modified to include Operating System sFTP Log Information, as in\nissues have also been addressed, which are described below.\n this example from an OpenVMS environment:\n \n Subj: NEW YORK Prescription Monitoring Program Transmission Failed [#99999]\n 02/29/16@12:44 26 lines\n From: SPMP TRANSMISSION In 'IN' basket. Page 1\n --------------------------------------------------------------------------\n There was a problem with the transmission of information about Controlled\n Substance prescriptions to the NEW YORK State Prescription Monitoring\n Program (SPMP).\n \nestablished to further enhance the VistA SPMP functionality released by patch\n \n Batch #: 41\n Period : 02/29/16 thru 02/29/16\n Error : Secure FTP Transmission failed.\n \n Please, use the option Export Batch Processing [PSO SPMP BATCH PROCESSING]\n to manually transmit this batch to the state.\n \n sFTP Log:\n ========\n $ SET VERIFY=(PROCEDURE,IMAGE)\nAll the changes introduced by this patch were related to the options under\n $ SET DEFAULT USER$:[SPMP]\n $ sftp -"D3" -oIdentityFile="/USER$/SPMP/VMSSSHID." -"B" SPMP_FTP_201606021\n 6.INP -oUser=VATEST 54.175.203.159\n debug( 2-JUN-2016 17:37:28.02): Ssh2/SSH2.C:1896: CRTL version (SYS$SHARE:D\n SHR.EXE ident) is V8.3-01\n debug( 2-JUN-2016 17:37:28.04): SshAppCommon/SSHAPPCOMMON.C:313: Allocating\n bal SshRegex context.\n debug( 2-JUN-2016 17:37:28.05): SshConfig/SSHCONFIG.C:3482: Metaconfig pars\n stopped at line 4.\n debug( 2-JUN-2016 17:37:28.05): SshConfig/SSHCONFIG.C:890: Setting variable\nthe State Prescription Monitoring Program (SPMP) Menu [PSO SPMP MENU] which\n rboseMode' to 'FALSE'.\n debug( 2-JUN-2016 17:37:28.06): SshConfig/SSHCONFIG.C:3390: Unable to open \n /ssh2_config\n debug( 2-JUN-2016 17:37:28.07): Connecting to 54.175.203.159, port 22... \n not used)\n debug( 2-JUN-2016 17:37:28.07): Ssh2/SSH2.C:2881: Entering event loop.\n debug( 2-JUN-2016 17:37:28.12): Ssh2Client/SSHCLIENT.C:1655: Creating tra\n protocol\n debug( 2-JUN-2016 17:37:28.12): SshAuthMethodClient/SSHAUTHMETHODC.C:104:\n "publickey" to usable methods. \nis located under the Supervisor Functions [PSO SUPERVISOR] menu option. \n %TCPIP-E-SSH_FC_ERR_DEST, destination is not directory or does not exist\n \n ...\n \n debug( 2-JUN-2016 17:37:35.66): Ssh2/SSH2.C:327: locally_generated = TRUE\n Disconnected; no more authentication methods available (No further authent\n on methods available.).\n debug( 2-JUN-2016 17:37:35.66): Ssh2Client/SSHCLIENT.C:1731: Destroying \n debug( 2-JUN-2016 17:37:35.66): SshConfig/SSHCONFIG.C:2888: Freeing pki. \n pki != NULL, user_pki = NULL)\n \n debug( 2-JUN-2016 17:37:35.66): SshConnection/SSHCONN.C:2636: Destroying\n debug( 2-JUN-2016 17:37:35.66): Ssh2Client/SSHCLIENT.C:1799: Destroying \n completed.\n debug( 2-JUN-2016 17:37:35.66): SshAuthMethodClient/SSHAUTHMETHODC.C:109: \n oying authentication method array.\n %TCPIP-F-SSH_FATAL, non-specific fatal error condition \n \n8. PSO SPMP ADMIN Security Key\n ---------------------------\n A new security key was created to restrict access to the following SPMP\nThe following functionality enhancements will be delivered by this patch:\n functionalities:\n \n - ASAP Definition Customization updates through the option View/Edit\n ASAP Definitions [PSO SPMP ASAP DEFINITIONS]. Visualization of the\n current ASAP Definition is not restricted.\n \n - SPMP Parameters value updates through the option View/Edit SPMP State\n Parameters [PSO SPMP STATE PARAMETERS]. Visualization of the current\n SPMP parameters is not restricted.\n \n \n - SSH Key generation or replacement through the option Manage Secure\n SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT]. Visualization of the\n current public key is not restricted.\n \n9. Misleading "File Successfully Transmitted" message for Linux OS\n ---------------------------------------------------------------\n The previous algorithm used to identify whether the SPMP sFTP data\n transmission was successful was not 100% accurate for Linux Operating\n Systems. A new algorithm has been created and it should reflect the\n transmission status with much greater accuracy when transmitting data\n1. View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option\n from a Linux based environment.\n \n10.SPMP Files Access Restrictions\n ------------------------------\n The FILE ACCESS setting for the SPMP files below will be opened up so\n users can use FileMan to view and search their content. The files were\n unintentionally released in PSO*7*408 as restricted.\n \n - SPMP ASAP RECORD DEFINITION (#58.4)\n - SPMP EXPORT BATCH (#58.42)\n -------------------------------------------------------------\n \n11. Pharmacy DEA Number (ASAP Data Element PHA03)\n ---------------------------------------------\n The Pharmacy DEA# was previously retrieved from the INSTITUTION file\n (#4) through the RELATED INSTITUTION field (#100) in the OUTPATIENT\n SITE file (#59). Now, the software will look for a DEA# for the\n institution in NPI INSTITUTION field (#101) in the OUTPATIENT SITE\n file (#59). If the DEA# for the NPI Institution is blank the software\n will retrieve the DEA# for the Related Institution, like it was doing\n before this patch.\n Some extensive enhancements have been made to this option to allow full \nPSO*7*408 back in September 2014. The SPMP VistA functionality is used to\n user customization of the American Society for Automation in Pharmacy\n (ASAP) data definition format (protocol) used to report outpatient\n controlled substance prescription data to the states.\n \n a) The term '/Edit' has been added to the external name of this option\n and the term 'VIEW' was removed from the internal option name.\n \n b) This option has been modified to include full customization capability \n for the ASAP definitions 3.0 and later versions, which will allow sites \n to fulfill states PDMPs' specific requirements. Moreover, sites will be\nidentify prescriptions for controlled substance drugs, Schedule 2 through 5,\n able to create new ASAP versions by copying an existing one, which\n will hopefully allow them to continue transmissions well into the\n future as new ASAP versions are released and adopted by the states\n PDMPs.\n \n Below is a list of actions that have been added to this option:\n \n CV Copy ASAP Version CE Customize Element ED Edit Delimiters\n CS Customize Segment DC Delete Customization \n \ndispensed by the Veterans Health Administration (VHA) Outpatient Pharmacy\n For more information on these new actions see the Outpatient Pharmacy\n Manager's User Manual in the State Prescription Monitoring Program\n (SPMP) section.\n \n c) Customized Data Elements and Segments will be identified by an '*' \n (asterisk) displayed to the right of the Data Element or Segment ID.\n \n2. View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option\n ------------------------------------------------------------------\n A few modifications have been made to this option to support the new \nfacilities and to create and transmit an export file containing this\n functionality released by this patch.\n \n a) The parameter WINDOWS/NT LOCAL DIRECTORY was removed from this option\n because this module no longer supports this operating system due to\n the increase in the complexity for handling SSH Keys and the fact that \n VHA does not use WINDOWS/NT operating system for VistA database at any\n of its sites.\n \n b) The parameter REPORTING FREQUENCY IN DAYS was modified to allow a\n maximum value of 30 days. Before this field allowed a maximum value of\ninformation to the Prescription Drug Monitoring Program (PDMP) of each state\n 99 days.\n \n c) A new parameter called RENAME FILE AFTER UPLOAD was added right after\n the 'FILE EXTENSION' parameter. The current transmission creates and\n sends the data file with the ".UP" file extension (for "upload"); once\n the file is transmitted a command within sFTP (Secure File Transfer \n Protocol) is issued to rename the file to ".DAT" (or ".TXT") file\n extension. This new parameter will allow the site to control whether\n they want to keep the existing functionality by setting this parameter\n to 'YES' or if they would like to create and transmit the file without\non a daily basis.\n renaming it by setting this parameter to 'NO'. The parameter will be\n initially exported with a default value of 'YES', which is consistent\n with the existing released functionality.\n \n d) The parameters STATE SFTP SERVER IP ADDRESS and STATE SFTP SERVER\n USERNAME had their maximum value lengths increased from 30 to 60 and\n 50 characters respectively to accommodate longer PDMP's DNS (Domain\n Name System) names and the usernames they assign to VHA sites.\n \n e) For security reasons the parameters SFTP PRIVATE KEY TEXT and SFTP\n \n PUBLIC KEY TEXT have been removed from this option as the SSH\n encryption keys content will be handled by a new option called Manage\n Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT], which is\n described below.\n \n3. Manage Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT] option \n -------------------------------------------------------------------\n This new option was created to automate the management of SSH encryption\n keys and to improve the security regarding their content. This new option\n will allow sites to view the public SSH key, create a new SSH key pair and\n\n
\nMCCF ePharmacy Compliance Phase 3\n\n
\n This patch is part of the Pharmacy Safety Updates project and will \n \n CA Service Desk I10102695FY16\n -----------------------------\n Pharmacy Technician not able to edit # of refills data field.\n address Patient Safety Issue (PSI) #PSPO00003291 and CA Service \n Desk ticket I10102695FY16.\n \n PSI PSPO00003291 is CA Service Desk Ticket I10020812FY16\n --------------------------------------------------------\n When processing outpatient medication orders, and no dispense drug \n is selected, the range values for the # of refills prompt is\n defaulting to zero.\n\n
\nThis patch addresses five issues:\nmedications that have a sig longer than 3 words will not display in the \nmeds tab.\n \n 4. If a Health Level 7 (HL7) delimiter character is inserted\ninto the comment field for Non-VA meds, the escape character is \nincorrectly stored in the global.\n \n 5. Non-VA meds do not display on the Meds Tab in CPRS if the\nStart Date is set to NOW when creating the Non-VA med.\n 1. The calculation of the dosage of a prescription will not \npopulate when creating an order and entering the schedule in all lower \ncase. \n 2. Schedules are not expanding to SPANISH. The labels aren't \nprinting in Spanish translated from English as necessary when creating a \nprescription in outpatient pharmacy. \n \n 3. In the Computerized Patient Record System (CPRS) Non-VA \n\n
\nOne VA Pharmacy remote prescription enhancements.\n\n
\nFIXED MEDICATION COPAYMENT TIER (FMCT)\n\n
\nThis patch resolves a problem where a pharmacy user is not prompted for a \nlabel device. This occurs when the host site does not generate label data \nfor a remote refill or partial fill request.\n\n
\nFIXED MEDICATION COPAYMENT TIER (FMCT)\n\n
\nThis patch will fix the issue where a suspended prescription\nis being transmitted to CMOP too soon.\n\n
\n1) In V. 6.0 of Outpatient Pharmacy when a medication was returned to stock \nprescription is returned to stock. This functionality becomes fully\nfunctional when PSD*3*24 is installed. \n \n2) With the release of PSO*7*32, functionality was added to allow the \ninactivating of Outpatient Pharmacy divisions in the OUTPATIENT SITE file \n(#59). The DIC("S") that was added prevented these inactive divisions from \nselection when processing Audiofax prescriptions. This patch will allow \ninactive divisions to be selected when processing Audiofax fill requests. \n \nFor this part of the patch to be completely functional the latest version \nfor a refill (nothing has really changed for original fill), the patient \nof VEXREX must be installed. Please see PSO*7*38 for details.\n \n3) With the installation of V. 7.0 of the Outpatient Pharmacy package, the\nbackground utility, Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS], that\nautomatically expires prescriptions daily was not queued to run at many\nsites. Because this utility was not queued, prescriptions with a status\nof active were showing on the Orders tab in CPRS option and on some\nprintouts when they should actually show as expired. A new option Manual\nAuto Expire Rxs [PSO MANUAL AUTO EXPIRE] is added to the Maintenance \n(Outpatient Pharmacy) [PSO MAINTENANCE] menu option. This new option\nessentially lost that refill. In v. 7.0 this was fixed for refills, so that \nallows sites to back expire all prescriptions from the date Outpatient\nPharmacy package V. 7.0 was installed until the current date minus one day\n(T-1).\n \n4) When printng the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION\nPROFILE], to the screen the screen pauses and breaks do not work\ncorrectly. This patch corrects this problem.\n \n5) When printing the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION\nPROFILE] using the entry point DFN^PSOSD1 the header text states that the\nwhen a refill is returned to stock, the refill is deleted. The problem is \nprofile is printing for the last 45 days when it is actually printing for\n120 days. This patch corrects the header text to 120 days which is the\ncorrect number of days that the profile is being printed for.\nthe Controlled Substances package is not aware of the deletion. \n \nA patch is to be released by both the Outpatient Pharmacy and Controlled \nSubstance (PSD*3*24) packages. The Outpatient Pharmacy portion of the patch \nwill send notification to the Controlled Substances package each time an \n\n\nThere are multiple variables used for determining whether a patient will \nbe billed copay in Outpatient Pharmacy (i.e. Supply Item, Investigational \nDrug, Nutritional Supplement, service connection, environment indicators, \nIB billable flags, etc.). They are used separately or in conjunction \nwith one another to determine if the prescription is billable. For the \nDomiciliary patients, IB has a specific check for Domiciliary and returns \nthe exempt status; however, OP did not have one of three flags defined \ncorrectly to exempt prescriptions from copay.\n\n
\n The patch addresses (2) issues:\n 1. Duplicate orders are erroneously allowed and duplicate warning \n messages do not appear after patient status is updated from \n "authorized absence" to another status.\n 2. Duplicate warning messages are absent when copying an order if the \n previous order attempt was terminated in the same session.\n\n
\nThis patch will fix the following issues:\n1. The CMOP transmission stopped due to an Undefined\n error\n2. Update the Technical Manual/Security Guide for\n the HL7 record sent to the dispensing machines\n\n
\nThe patch addresses three (3) issues:\n division on the retransmission from the correct division to the \n division the user is signed on to at the time the option is run.\n This really affects integrated sites.\n \n1) INC000000954036 - SUSPEND HOLD ISSUE\n When a Rx on suspense goes on hold, it should be restored to the \n suspended status when unhold.\n2) INC000000736122 - RX renewal date\n Renewed script date becomes "ISSUE" date\n3) INC000001180597 - Division Change with Transmission \n The option Unprinted/Non-Transmitted Rxs Re-Suspend, changes the \n\n
\nThis is a follow-up patch for Fixed Medication Copayment Tier (FMCT) \npatch PSO*7*460, where the mail message, "PRESCRIPTION QUESTIONS REVIEW \nNEEDED" was not generating.\n\n
\nThis patch will fix the following issue:\nUser attempts to '^' at the Device prompts, the fill is still processed\n\n
\nThis patch will fix the following issue:\n1. Drug Interaction Order Checks\n\n
\nThe patch addresses two (3) issues:\n Outpatient Rx, the Rx Expiration Date is reset to an incorrect date.\n Rx #100001973 STERI-STRIPS^401962 will be discontinued after the\n acceptance of the new order. \n \n Now doing allergy checks. Please wait...\n \n Now processing Clinical Reminder Order Checks. Please wait ...\n Now Processing Enhanced Order Checks! Please wait...\n \n \n Press return to continue: ^ <<< [This up (^) character causes the problem] \n \n \n Rx # 100001977 06/26/17\n TESTATNM,CLETUS #8\n APPLY 1 BANDAGE OVER AFFECTED AREA THREE TIMES A DAY\n \n ACER BANDAGE\n ROCHA,MARCELO ROCHA,MARCELO\n # of Refills: 0\n \n SC Percent: 30%\n3. R15046343FY17 - A drug with same tab strength did NOT discontinue after\n Disabilities: \n \n Was treatment for Service Connected condition? NO// \n \n Are you sure you want to Accept this Order? NO// YES\n ...\n \nResolution:\n--------\nChanged PSOORNEW routine to initialize the array variable PSORX("DFLG") \n duplicate (new order) processing. This created a duplicate active order in\nright before the call to file the new order and subsequent DC of the existing\nduplicate order. This initialization will cause the code responsible for \ndiscontinuing the existing order (DCORD^PSONEW2) to perform the DCing of the\nexisting order without skipping it, like it was doing before this fix.\n the patient's profile.\n \nAssociated NSR(s):\n=================\nN/A\n \n \nAssociated CA SDM Ticket(s):\n============================\n1. R10380204FY16 - When entering a new outpatient Rx, the Rx is Deleted on\n editing the dosage and entering an up (^) character to exit.\n2. R9361753FY16 - When editing/modifying the Issue Date or Fill Date of an\n Outpatient Rx, the Rx expires on an incorrect date.\n3. R15046343FY17 - A drug with same tab strength did NOT discontinue after\n duplicate (new order) processing.\n \nParticipating Test Sites:\n1. R10380204FY16 - when entering a new Rx using the Patient Prescription \n========================\nOKLAHOMA CITY\nTAMPA BAY\n \nTicket Overview:\n===============\n1. R10380204FY16- When entering a new RX using LM BACKDOOR ORDERS, the RX\n is Deleted on editing the dosage and entering an up (^) character to \n exit. \n \n Processing [PSO LM BACKDOOR ORDERS], and then editing the dosage and \nProblem:\n--------\nWhen user enters a new Outpatient prescription and answers "NO" to the prompt\n"Is this correct? YES//" and then user edits the dosage and enter an up (^)\ncharacter to exit the prompt "Dosage:" and accepts Rx then new Rx will be\ndeleted. \n \nResolution:\n--------\nCorrect routine code ASK^PSOORED5 to call line tag EXE instead EX to escape \n entering an up (^) character to exit, the Rx will be deleted as user\nkilling required data before saving.\n \n \n2. R9361753FY16 - Outpatient Rx expired on an incorrect date, when Issue Date\n or Fill Date is modified.\n \nProblem:\n--------\nWhen editing/modifying the Issue Date or Fill Date of an Outpatient Rx using\nthe backdoor pharmacy, the Rx expiration date is reset to an incorrect Date.\n accepts the Rx.\n \nResolution:\n--------\nCorrected A^PSOEXDT to set up expiration date for prescription without\nrefills not less than 30 days after issue date unless it is a Clozapine\nprescription. In addition, if the newly calculated Rx Expiration Date is\nearlier than the Rx Fill Date the Rx Expiration Date will be re-calculated\nto be the Rx Fill Date plus the Days Supply value.\n \n \n \n3. R15046343FY17 - A drug with same tab strength did NOT discontinue after\n duplicate (new order) processing. This created a duplicate active order\n in patient's profile.\n \nProblem: \n--------\nWhen using the options Patient Prescription Processing [PSO LM BACKDOOR\nORDERS] or Complete Orders from OERR [PSO LMOE FINISH] for finishing \npending orders there was a scenario where duplicate active orders could\nremain on the patient profile as ACTIVE. The screen capture example below\n2. R9361753FY16 - Using the Patient Prescription Processing [PSO LM BACKDOOR\nshows the prompt "Press return to continue:" where if the user entered an\nup (^) character at this prompt, the duplicate existing order would not be\nDC'd.\n \n ...\n --------------------------------------------------------------------------\n Duplicate Drug in Local Rx:\n \n Rx: 100001973\n Drug: ACER BANDAGE\n ORDERS] option, when users edit/modify the Issue Date or Fill Date of an\n SIG: APPLY 1 BANDAGE OVER AFFECTED AREA THREE TIMES A DAY\n QTY: 9 Refills remaining: 1\n Provider: ROCHA,MARCELO Issued: 06/25/17\n Status: Active Last filled: 06/26/17\n Processing Status: Not released locally (Window)\n Days Supply: 9\n --------------------------------------------------------------------------\n \n Discontinue RX # 100001973 STERI-STRIPS Y/N? YES \n \n\n\nThis patch will correct the following issues: \n \n3) The option Print from Suspense File might erroneously skip printing\n some labels for orders which previously had labels printed but were put\n back on suspense and do need new labels.\n \n1) When invoking the CK action in the Outpatient Pharmacy Medication \n Profile screen, Non-VA and pending orders which do not contain dispense\n drugs do not receive allergy checks.\n \n2) When invoking the CK action in the Outpatient Pharmacy Medication \n Profile screen, the business rule for performing allergy checks on\n discontinued orders is not being followed.\n\n
\nThe patch addresses three (3) issues:\n Fill Date issue \n \n \n ROUTINE:\n =======\n Added new code to DT+1^PSON52 to check if the patient is not a clozapine \n patient, # of Refills is zero and the Expiration Date is < Filled Date,\n then to set the expiration date.\n The Expiration Date will normally be set to (Fill Date + Day Supply). \n However, it will be adjusted to comply with the following restrictions:\n - For controlled substances, the maximum Expiration Date allowable is \n \n (Issue Date + 184 days)\n - For non-controlled substances, the maximum Expiration Date allowable \n is (Issue Date + 366 days)\n - If the Expiration Date is less than the Fill Date, it will be set to \n the same as the Fill Date\n Associated PSPO(s):\n ===================\n N/A\n \n Associated NSR(s):\n =================\n N/A \n \n \n Participating Test Sites:\n ========================\n TBD\n \n Ticket Overview:\n ================\n 1. I8924763FY16 - When a Maintenance Rx was created as the result of\n converting a Titration marked Rx instead of retaining the Expiration Date\n from the Titration Rx it was wrongly being assigned a new Expiration\n Date.\n Associated CA ticket(s):\n \n Problem:\n =======\n When using the Patient Prescription Processing [PSO LM BACKDOOR] option\n and using the hidden action Convert Titration Rx (TR) to create a new\n Maintenance dose prescription from a Titration Rx the user noticed that the\n Expiration Date associated with the new Maintenance Rx was calculated 366\n days in the future instead of being assigned the exact same Expiration Data\n from the Titration Rx.\n \n ========================\n Resolution:\n =========\n Changed the routine PSON52 responsible for creating the new Maintenance Rx\n to overwrite the calculated Expiration Date with the Expiration Date from\n the original Titration Rx.\n \n ROUTINE:\n =======\n Added code at DT+1^PSON52 to set the array variable PSOX("STOP DATE") with \n the Titration Rx Expiration, if a Titration Rx To Maintenance Rx conversion\n 1. I8924763FY16 - Expiration date changed for prescription marked as a\n is taking place.\n \n \n 2. I9667491FY16 -The site would like to use the PSO BATCH BARCODE option to\n renew prescriptions. When this is attempted the renewal appears to\n succeed and there is a prompt to edit the renewal. If yes is selected the\n session will crash with an undefined variable (hard error).\n \n Problem:\n =======\n titration script.\n When using the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option\n for renewals the users received a hard error and were logged out of the\n system when they answered YES to the "Edit renewed Rx ?" prompt (before\n accepting it).\n \n Resolution:\n =========\n The root cause of this problem was due to the fact that the PSOACT variable\n that controls which action a specific user can perform on an order, based on\n the user security keys as well as whether the order was digitally signed or\n 2. I9667491FY16 - Renewing a script using PSO BATCH BARCODE causes crash\n not. The routine PSOBBC was modified to initialize the PSOACT variable,\n which will prevent the hard error.\n \n ROUTINE:\n =======\n Added code at NEW+9^PSOBBC to initialized the PSOACT variable according to \n the type of order, user's security keys and system parameters.\n \n \n 3. We would like to request for assistance in the identification and \n \n deployment of the VistA patch used at VHA station #663 (Seattle\n division) that enables pharmacy staff resolves the Fill Date issue and\n generates the error message described below\n \n "The earliest fill date allowed is determined by the Issue Date, the\n Fill Date cannot be before the Issue Date or past the Expiration\n Date. Both the month and day are required."\n \n Problem:\n =======\n 3. R8247671FY16 - VistA patch used at VHA station #663 that resolves the \n When using the speed renewal hidden action in Patient Prescription \n Processing [PSO LM BACKDOOR] option, it was reported that when the # of \n refills is zero, there are times the expiration date is set to a date\n earlier than the filled date.\n \n Resolution:\n ==========\n In a situation where the # of refill is zero, patient is not a clozapine \n patient and the expiration date is < fill date, added new logic to \n calculate the most appropriate expiration date.\n\n\n1. It was reported that patient instruction information is appearing\nprescription is filled and the user enters "^" at the label prompt thus\nterminating the label print process. This patch resolves these issues by\ncreating new activity logs in the respective prescription entry.\n \n3. With the release of PSO*7*40 an interface was added for the Controlled\nSubstance package (PSD*3*24). This interface sends notification to the\nControlled Substance package when a fill, refill or partial is returned\nto stock. It was discovered that the interface was done incorrectly and\ncaused an undefined error. The interface was added to the routine\nPSORESK. This patch corrects the problem.\nrandomly on prescriptions that were created through the back door. This\n \n4. Selecting 'HOLD' at the label prompt for a mail prescription with a\nCMOP drug receives a reply of "HAS BEEN SUSPENDED FOR CMOP UNTIL xxxx".\nThis patch ensures that the 'HOLD' process prevents the Rx going into\nCMOP.\nwas found to be due to some of the variables not getting killed prior to\nusing the option Patient Prescription Processing [PSO LM BACKDOOR ORDERS].\nThis patch fixes this problem.\n \n2. When a prescription label is requested, and if between the time it was\nrequested and the time the label actually prints it got discontinued or\nit was put on hold, the label does not get printed. Also when a new\n\n
\nThis patch will resolve the following issues.\n1. I9899883FY16 Drug Enter/edit option issue\n2. I6126024FY16 Patient name does not come up on the Bingo Board\n\n
\nThis patch will resolve the following issues:\n1. If patient has Other Language Preference set to Yes and medication\ninstructions are entered into Other Patient Instructions, this\ninformation will not print on the pharmacy fill part of the label.\n2. Duplicate Prescriptions are active on a patients profile\n3. Pharmacy staff can process their own prescriptions\n4. When editing the Drug on a Prescription and answering NO to Edit \nthe SIG prompt, the Dosage is not updated to match the Drug and SIG.\n\n
\n \nactive prescription containing the duplicate class drug but does not \ndiscontinue the drug when "Y" is entered at the prompt.\n3. The Outpatient Pharmacy ScripTalk label process is using %ZTIO \nvariable to write to the Prescription file's Device field. The ZTIO \nvariable is used to hold the Scrip Talk device not %ZTIO. \n \nThe patch addresses the following issues:\n \n1. Users report that when a Window Partial is filled, the Patient \nNotification (Rx Ready) file entry (52.11) is showing the Fill Type as \nfull instead of partial.\n2. The PSO RX Discontinue Prescription(s) reinstate process displays \na Therapeutic Duplication warning message then prompts to discontinue the \n\n
\nThis patch will resolve the following issues. \n4. When editing day supply for controlled orders calculating (PSPO \nthe prescriber would be carried over to the next pending orders for that\nsame patient.\n \nResolution: \n-----------\nThe array variable PSORX("PROVIDER NAME") that stores information about \nthe provider was not being properly initialized between the processing\neach of the patient's pending orders. The code was modified to kill the\narray variable PSORX before processing each of the patient's pending\norder. \n #2580) supply incorrect.\n \nTechnical Resolution: \n---------------------\nModified the routine PSOORFIN at tags SUCC+4 and PSOORFIN+19 to kill \narray variable PSORX("PROVIDER NAME")\n \n \n3. I9898461FY16 - Comment placed in "REMARKS" prompt is not visible if Rx \n is on HOLD \n \n \nProblem: \n--------\nComments entered into the REMARKS field (#15) were not being displayed\nwhen a prescription was put on hold. Once the prescription was removed\nfrom hold, the remarks would become visible again.\n \nResolution: \n-----------\nModified routine PSOORNE2 so the comments entered into the REMARKS field \n(#15) display when the prescription is put on hold. \n5. When editing the field QTY (#9) of a Pending Order the system will auto\n \nTechnical Resolution: \n---------------------\nModified the routine ACT+2^PSOORNE2 to set just $P(RX3,"^") instead of \nthe entire RX3 variable, as shown below:\n \nI 'RX3 S RX3=$P(RX2,"^",2),$P(^PSRX(RXN,3),"^")=$P(RX2,"^",2) \n \n \n4. I10167818FY16 - Editing day's supply incorrect\n calculate if Schedule not marked PRN\n \nPSPO #2580 \n \nProblem: \n--------\nFor pending orders with a dispense drug where the quantity can be\nautomatically calculated based on the dosage and days supply there was a\nproblem for certain situations where the automatic calculation was not\ndesirable. For example, the prescriber would order 10 tablets of a \ncontrolled substance medication with a 30 days supply PRN (As Needed) to\n \nbe taken no more than twice a day. When the Outpatient Pharmacy user\nedited the DAYS SUPPLY field (#8) for such order and changed it from 30 to\n28, as an example, the software would automatically update the quantity\nfrom 10 to 56, which is clearly inconsistent with the prescriber's initial\nintention. \n \nResolution: \n-----------\nA new logic has been introduced related to the editing the DAYS SUPPLY \nfield (#8) of a pending order:\n \n \n 1. For single dose order the software will not automatically recalculate \n the Quantity field if the current Quantity value on the order is not\n the result of a calculation based on the current Day Supply value\n (before the edit), which suggests the Quantity was previously manually\n entered (not calculated).\n 2. The software will not take into account whether the Schedule is marked\n PRN (As Needed) or not when deciding to automatically recalculate the\n QTY field (#9).\n 3. For a Controlled Substance pending order the system will not \nAssociated NSR(s): \n automatically recalculate the Quantity field (#9) if it will cause the\n current Quantity value to be increased.\n 4. For a Complex Controlled Substance pending order the system will not \n automatically recalculate the Quantity field (#9).\n 5. For a pending order that qualify for a Quantity recalculation that did\n not happen because of one of the rules above (1, 3 and 4), the system\n will display the following message to the user editing the DAYS SUPPLY\n field (#8): \n \n The QTY (99) has not been changed. \n==================\n Please, review and update it if necessary. \n \nAdditionally, a modification was introduced to prevent any automatic\ncalculation/update of the QTY field (#9) for a new, pending or existing\norder when the user selects to specifically edit the QTY field (#9)\nitself.\n \nTechnical Resolution: \n---------------------\nModified routines PSODIR1, PSOSIG, PSOSIGCX and PSOSIGTX to implement the \nN/A \nnew rules above.\n \n5. I14933412FY17 - When editing the QTY field (#9) of a Pending Order the \n system will auto calculate if Schedule not marked PRN\n \nProblem: \n--------\nWhen using the options Patient Prescription Processing [PSO LM BACKDOOR\nORDERS] or Complete Orders from OERR [PSO LMOE FINISH] if the user tries \nto edit the QTY field (#9) of the pending order and if the quantity can be\n \n \nautomatically calculated and the current value does not match the \ncalculated value the software will automatically replace the current value\nwith the calculated value before prompting the user for the QTY field (#9)\nfor the order.\n \nAs seen on the example below:\n \n Pending OP Orders (ROUTINE) Jun 06, 2017@15:13:57 Page: 2 of 3 \n TESPATNM,ROB <A> \n PID: 666-00-0258 Ht(cm): _______ (______) \nPatient Safety Issues (PSIs):\n DOB: JUL 21,1963 (53) Wt(kg): _______ (______) \n +---------------------------------------------------------------------\n (4) Pat Instruct: \n Provider Comments: \n Instructions: TAKE ONE TABLET PO QDAY \n SIG: TAKE ONE TABLET BY BY MOUTH EVERY DAY \n (5) Patient Status: SC \n (6) Issue Date: JUN 6,2017 (7) Fill Date: JUN 6,2017 \n (8) Days Supply: 30 (9) QTY (TAB): 10 \n Provider ordered: days supply 30, quantity 10 & refills 0 \n=============================\n (10) # of Refills: 0 (11) Routing: MAIL \n (12) Clinic: NHCU \n (13) Provider: ROCHA,MARCELO \n (14) Copies: 1 \n (15) Remarks: \n Entry By: ROCHA,MARCELO Entry Date: 06/06/17 12:07:24 \n -------Digitally Signed Order---------------------------------------- \n BY Bypass DC Discontinue FL Flag/Unflag \n ED Edit FN Finish \n Select Item(s): Quit// 9 \nPSPO #2696 - When finishing pending orders from CPRS using the Complete \n \n Quantity has been changed from 10 to 30 \n \n Press Return to Continue: \n \n QTY ( TAB ) : 30// \n \nResolution: \n-----------\nA change was introduced to the code responsible for handling the editing \nOrders from OERR[PSO LMOE FINISH] option, if the user selects not to \nof the QTY field (#9) of a pending order to prevent any automatic\nrecalculation and update of the quantity value from happening before the\nuser is prompted for the QTY prompt. Also, when entering a new order the\nsoftware will not try to auto update the QTY value if a value already is\ndefined and the user is chooses to edit the QTY field (#9).\n \nTechnical Resolution: \n---------------------\nModified the routine PSODIR1 at the QTY line tag that handles the QTY \nediting logic to not call QTY^PSOSIG (responsible for recalculating the\ndisplay the patient profile and start processing pending orders a problem \nquantity) when a quantity already exists for the order.\nwould occur for patients with orders issued by more than one single \nprovider.\n \nPSPO #2580 - For pending orders with a dispense drug where the quantity \n1. Messages from PSO EXTERNAL DISPENSE do not specify site location \ncan be automatically calculated based on the dosage and day's supply \nthere was a problem for certain situations where the automatic calculation\nwas not desirable.\n \nTest Sites: \n===========\nOrlando VAMC\nErie VAMC\n \nAssociated CA SDM Ticket(s):\n \n============================\n1.I9896500FY16 - Request for site ID in subject line/PSO EXTERNAL \n DISPENSE Message\n \n2.I9897580FY16 - Wrong authorization provider is listed on prescription \n in CPRS and Outpatient Pharmacy\n \n3.I9898461FY16 - Comment placed in "REMARKS" prompt is not visible if Rx \n is on hold\n \n2. Wrong authorization provider is listed on prescription in (PSPO \n4.I10167818FY16 - Editing day's supply incorrect\n \n5 I14933412FY17 - When editing the QTY field (#9) of a Pending Order the \n system will auto calculate if Schedule not marked PRN\n \nDefect Tracking System Ticket(s) Overview:\n==========================================\n1. I9896500FY16 - Request for site ID in subject line/PSO EXTERNAL \n DISPENSE Message\n \n #2696) CPRS and Outpatient Pharmacy\nProblem: \n--------\nWhen OPAI (Outpatient Pharmacy Automated Interface) tries to release a \nprescription and it is unable to match the release information with a \nprescription fill on file it will create a Mailman message alerting users\nabout the issue. The problem for integrated sites with multiple sites \nusing OPAI is that the Mailman message does not identify which site the\nrelease information was for, prompting all the sites to lookup the Rx\nrecord to find out whether it belongs to them or not.\n \n \nCurrent message subject: "External Dispense - Rx Release Attempted" \n \nResolution: \n-----------\nThe Mailman message subject was modified to include the Site Number at the\nbeginning. This will be consistent with other mailman messages that \nalready identify the Rx site in the message subject.\n \nNew message subject: "500 External Dispense - Rx Release Attempted" \n \n3. Remarks entered do not display when prescription is placed on Hold \nTechnical Resolution: \n---------------------\nModify routine PSOHLDI1 at tag MAIL+13: add the following code: \n \nS XMSUB=$S($G(PSOSITE):$$GET1^DIQ(59,PSOSITE,.06)_" ",1:"")_"External \nDispense - Rx Release Attempted"\n \n \n2. I9897580FY16 - The Wrong authorization provider is listed on \n prescription in CPRS and Outpatient Pharmacy\n \n \nPSPO #2696\n \nProblem: \n--------\nWhen finishing pending orders from CPRS using the Complete Orders from \nOERR [PSO LMOE FINISH] option, if the user selects not to display the\npatient profile and start processing pending orders a problem would occur\nfor patients with orders issued by more than one single provider. If the\nuser selected the Provider field (#13) and merely confirmed it,\n\n\nMCCF EDI TAS EPHARMACY BUILD 2\n\n
\nThis patch will resolve the following issues.\n \n Defect Tracking System Ticket(s) & Overview: \n ===========================================\n \n 1. I8213786FY16 - Using Option RESET COPAY STATUS/CANCEL displays\n ALL copay exemption flags after edit.\n \n Problem:\n =======\n While using option RESET COPAY STATUS/CANCEL to edit copay exemption\n \n flags, when a person is automatically Exempt from Copay (such as Service\n Connected 70%) the output displays ALL copay exemption flag end states \n rather than only those copay exemptions that have changed. \n \n Resolution:\n ==========\n The logic that determined whether the new exemption value was different\n from the old was based off a node in the prescription file that may not \n exist. The routine for this option now compares the user's response to\n the value stored in the prescription file to determine if the value has\n 1. I8213786FY16 - Using Option RESET COPAY STATUS/CANCEL displays \n changed.\n \n 2. I15627556FY17 - HARD ERROR DURING VERIFYING A DIGITALLY SIGNED \n PENDING ORDER \n \n Problem:\n =======\n When processing a digitally signed pending order, if that order is \n auto discontinued due to an address mismatch, there is a possibility of\n getting a hard error while generating the auto discontinued mail message.\n ALL copay exemption flags after edit.\n This can happen for a patient who has a non verified allergy and if the\n patient address was changed using the PU Patient Record Update ListMan\n action prior to processing the pending order.\n \n Resolution:\n ==========\n When the PU Patient Record Update ListMan action is used, it kills the \n DFN variable. Modified routine PSOPKIV2 to reset variable DFN if found \n missing and to make a call to VADPT.\n \n 2. I15627556FY17 - HARD ERROR DURING VERIFYING A DIGITALLY SIGNED \n ROUTINE:\n =======\n At line tag ADCMAIL+1, added code,\n S:'$G(DFN) DFN=PSODFN D ^VADPT,ADD^VADPT\n At line tag PADAD+1, removed the call VADPT and ADD^VADPT as it's moved\n to ADCMAIL+1\n \n 3. I11377620FY17 - Controlled substance prescription hash mismatch.\n \n Problem:\n PENDING ORDER \n =======\n Site reports that when a controlled substance prescription hash \n mismatch status the vista email that is generated has the incorrect \n last four the the ssn. \n \n Resolution:\n ==========\n When generating the auto discontinued mail message, variable VA("BID") \n that has the last 4 of the SSN is being used, which in this case happens \n to be from a previous patient. \n 3. I11377620FY17 - Controlled substance prescription hash mismatch. \n Modified routine PSOPKIV2 to ensure that the variable VA("BID") is for \n that patient by making a call to VADPT.\n \n 4. I9662455FY16 - Corrupted hash mismatch has a patient's last 4 \n of SSN incorrect.\n \n Problem:\n =======\n Site reports that a corrupted hash mismatch has a patient's last 4 \n of SSN incorrect.\n 4. I9662455FY16 - Corrupted hash mismatch has a patient's last 4 \n \n Resolution:\n ==========\n When generating the auto discontinued mail message, variable VA("BID") \n that has the last 4 of the SSN is being used, which in this case happens \n to be from a previous patient. \n Modified routine PSOPKIV2 to ensure that the variable VA("BID") is for\n of SSN incorrect. \n\n\nThis patch will fix the following issue.\n I9914094FY16 OTH, PRO, OP screen flashes by within seconds\n\n
\n===========\nThe patch addresses (2) issues:\n1. Other than CMOP prescription not printed when used manual mail-out CM\n2. Controlled substance auto-discontinued when signed and released days \n are different.\n\n
\nInbound electronic prescribing enhancements.\n\n
\nThis patch will resolve the following issues.\n \n 1. Speed refill message displays too quickly to be read. \n 2. Pharmacist Enter/Edit option display issue.\n\n
\n \nchanged to delete the entry when an up-arrow is entered at the prompt.\nThe software will now display a message indicating that the "Bingo\nrecord is incomplete!" and "Bingo record removed. Routine: PSOBING1\n \n3. Fixed error reported by Puget Sound in NOIS PUG-0198-51767. An undefined\nerror occurred when editing a prescription that created a new\nprescription, and there were no numbers left in the numbering sequence\nfor prescriptions. Errors could also occur if a site was manually\nassigning the prescription numbers, and nothing was entered at the\n"Select New Rx #" prompt when creating a new prescription due to an Edit.\n1. Made change to Allergy/Adverse Reaction display on labels and screen\nRoutines: PSONRXN, PSOORED1\n \n4. Fixed an error reported by San Francisco, NOIS SFC-0298-60681. The\nerror occurred in the daily cost compilation background job. \nWhen the patient is accessed during the compilation routine, an error could\noccur if that patient has both Outpatient and Inpatient orders to be\nbackfilled. After the backfilling, upon returning to the cost compilation\nroutine, an undefined error could occur. Routine: PSOHLUP\n \n \nprofiles. The software was referencing an incorrect piece of data, which\ncaused us to possibly display an Allergy under the Adverse Reaction heading,\nwhen it really should be displayed under the Allergy heading.\nRoutines: PSODEM, PSOLBLN1, PSOLBLS, PSOORUT3\n \n2. Fix a problem reported in NOIS SFC-0298-60679. Entering an up-arrow (^)\nat the Ticket # prompt could cause an undefined error. The software was\n\n
\n1) When the Print a PMI Sheet [PSNPMIS PRINT] option is selected\nPrescription Processing [PSO LM BACKDOOR ORDERS] option, it was erring out\ndue to an 'Undefined PSOID' error. This patch carries a fix for this\nproblem.\n \n3) The INACTIVATION DATE field (#7) of DRUG INTERACTION file (#56) is\nbeing populated by Pharmacy Data Management module, Enter/Edit Local Drug\nInteraction [PSS INTERACTION LOCAL ADD] option, to inactivate a\nparticular set of drugs that was once set up as interactive. During the\norder entry process when using Patient Prescription Processing [PSO LM\nBACKDOOR ORDERS] option, currently the drug-drug interaction by routine\nimmediately after using the Patient Prescription Processing\nPSODGDGI does not check for this inactivation date. This patch ensures\nthat the inactivation date is now being checked.\n[PSO LM BACKDOOR ORDERS] option, the patient medication sheet that is\nprinted for a particular drug also has the name of the patient that was\npreviously accessed under the Patient Prescription Processing [PSO LM\nBACKDOOR ORDERS] option. This patch fixes this problem.\n \n2) While selecting a certain patient related title during the progress\nnotes entry when placing a medication order using the Patient\n\n
\nThis patch will fix the following issue.\n1. I9914421FY16 all prescription information is not displayed\n on the Pharmacy verification screen\n\n
\nEmergency patch to resolve hard error during drug validation.\n\n
\nThis patch will resolve the following issues.\n \n1. I12011023FY17 - One-VA partial functionality does not restrict\n quantity\n2. I12010975FY17 - One-VA displaying inconsistent information\n in VistA options\n3. I12150112FY17 - OneVA Pharmacy Selection of Drugs by the\n Dispensing Site\n\n
\nThis patch will resolve the following issues.\n \n1. I17894075FY18 - Pharmacist not showing up for renewal in \n View Prescription; typo in HELP-PROMPT\n \n2. I18165455FY18 - OneVA issue for Refill and Partial\n\n
\nThis patch will resolve the following issues.\n \nInformation Processing Standard (FIPS) code for Canada is "CA", however the\nSPMP standard requires "CN" for Canada. \n \nResolution:\n-----------\nChanged the retrieval of the patient's state and postal code fields to\nfirst check for the country. For foreign countries (non-US) it will\nretrieve the Province and Postal Codes values returned in the VAPA(23)\nand VAPA(24) return array from the ADD^VADPT API. Also changed it to send\n"CN" for PAT22 (Country of Non-US Resident) for Canada.\nAssociated NSR(s)\n \nTechnical Resolution:\n---------------------\nModified the routines PSOASAP and PSOASAP0 to check whether the country is\nnon-US (foreign). If so, it will use the value in VAPA(24) and VAPA(23) for\nthe fields PAT15 and PAT16 respectively. Also, changed the line tag PAT22 \non the PSOASAP0 routine to return "CN" instead of "CA" for Canada.\n=================\n N/A \n \nTest Sites:\n==========\n \nAssociated CA SDM Ticket(s):\n============================\n \n1. I10127879FY16 - It is possible to suspend a script past the expiration\n date. \n2. I16514233FY17 - Vista transmits two instances of the same prescription\n to the external interface. \n R14795402FY17(d) - Vista is sending over prescription data twice for \n SOME prescriptions, resulting in duplicates showing\n up in ScriptPro\n3. I11517650FY17 - Need assistance with SPMP Patient Address errors \n \n \n1. It is possible to suspend a script past the expiration date.\nDefect Tracking System Ticket(s) & Overview:\n============================================\n1. I10127879FY16 - It is possible to suspend a script past the expiration\n date. \nProblem:\n--------\nCurrently in Outpatient Pharmacy the users are able to enter a REFILL DATE \nthat is past the Rx EXPIRATION DATE. The software should not allow a refill\ndate that is past the expiration date because it is an invalid date and the\nprescription will be expired before it can be dispensed.\n \n \nResolution:\n-----------\nThe Data Dictionary for the PRESCRIPTION file (#52) was modified to include \nrestrictions on the following fields: FILL DATE (#22) and REFILL DATE (#.01)\nin the REFILL sub-file (#52.1). The restrictions will require that the value\nentered for either one of these two fields cannot be before the Rx ISSUE\nDATE or after the Rx EXPIRATION DATE.\n \nTechnical Resolution:\n2. Vista transmits two instances of the same prescription to the external\n---------------------\nCreated new INPUT TRANSFORM code (FLDTINTR^PSOUTLA(Fill_Type)) and new \nEXECUTABLE HELP code (FLDTHELP^PSOUTLA(Fill_Type)) and modified the fields\nmentioned above to replace the current M code with calls to these two new\nentry points in the PSOUTLA routine.\n \nFiles & Fields Associated:\n------------------------- \nFile Name (#) Field Name (#) New/Modified/Deleted\n----------------- -------------------------------------- --------------------\n interface. \nPRESCRIPTION(#52) FILL DATE (#22) Modified \n REFILL (#52.1)\n -REFILL DATE (#.01) Modified\n \n \n2. I16514233FY17 - Vista transmits two instances of the same prescription\n to the external interface. \n R14795402FY17(d) - Vista is sending over prescription data twice for SOME\n prescriptions, resulting in duplicates showing up in\n ScriptPro\n \n \nProblem: \n--------\nThere is at least one scenario in Outpatient Pharmacy that will cause a \nprescription fill to be sent twice to the external interface. This happens\nbecause sometimes when the user pulls a CMOP prescription from suspense to \nprint locally it will be sent to the print queue twice and consequently it\nwas also being sent to the external interface twice.\n \nResolution:\n3. Need assistance with SPMP Patient Address errors \n-----------\nAdded a check in the routine that handles the pull from suspense to prevent\nit from adding a prescription to the print queue if the prescription is\nalready on the queue.\n \nTechnical Resolution:\n---------------------\nModified the routine PSOSUPOE to prevent it from setting the variable PPL\nwith the same prescription twice.\n \n \n \n3. I11517650FY17 - Need assistance with SPMP Patient Address errors \n \nProblem: \n--------\nThe State Prescription Monitoring Program (SPMP) module did not retrieve the\ncorrect State/Province (SPMP field PAT15 - State Address) and Postal Code \n(SPMP field PAT16 - ZIP Code Address) for patients that have a foreign\naddress on file. The software was retrieving the US state and Zip Code \nfields, which were both blank for such patients. In addition, the Federal\n\n
\nMocha 2.1, dosing only scope.\n\n
\nTHIS IS A FOLLOW UP PATCH.\n \nThis patch incorporates routine changes introduced into PSOORED5 in \nPSO*7.0*486 and merges them with routine changes in PSO*7.0*402.\n \nRefer to the install guide for installation instructions.\n\n
\nThis patch will correct 2 hard errors that are present in PSO*7.0*500, \nThe functions where the errors occur are:\n- Editing the Schedule while finishing a Pending order from CPRS\n- Editing a Schedule of an existing prescription\n- Editing a Schedule while Verifying a Non-verified Prescription using \n either the ListMan verification action or the 'Rx Verification by \n Clerk' option\n- Editing a Schedule while using the 'Process Order Checks' option\n \nThis patch will also correct an issue presented with the release version \nof PSO*7.0*500 where multiple word schedule expansions are not echoed to \nwhich is part of the MOCHA 2.1B COMBINED BUILD and is due for national \nthe screen. This defect does not affect the patient sig section were \nmultiple word schedules continue to be expanded appropriately, only the \nimmediate echo response functionality at the time of entry.\nrelease.\n \nThe following two errors have been addressed in this patch:\n \n<UNDEFINED>SCH+3^PSOORED3 *SCHEX\n<UNDEFINED>SCH+3^PSOORED4 *SCHEX\n \n\n
\nThis patch will resolve the following issues:\n4. I17185111FY18 - Error when changing routing from Window to Mail\n \n1. I15848129FY17 - Buprenorphine/naloxone prescription went through when\n the DEA expiration date was in the past \n \n2. R16854127FY18 - FILL DATE prompt range incorrect\n \n3. I5855290FY15 - CK Hidden Option and Remote Order Checks\n \n\n
\n1) When using the Detailed Allergy/ADR List action under the Patient\nof the patient who was last accessed prior to this patient using the\noption Complete Orders from OERR [PSO LMOE FINISH]. This could result in\ndispensing the wrong drug to the patient. This problem was found to be\ndue to some of the variables not being cleaned up properly. This patch\nensures that all such variables are killed appropriately.\nNOISs SLC-0200-50488, NJH-0600-21694 and PRO-0700-10326\n \n3) When a new prescription was created using the option Patient\nPrescription Processing [PSO LM BACKDOOR ORDERS], it was reported that the\npatient instruction was appearing randomly. This was the patient\nPrescription Processing [PSO LM BACKDOOR ORDERS] option, there is a\ninstruction of the patient who was last accessed prior to this patient\nusing the option Complete Orders from OERR [PSO LMOE FINISH]. This again\nwas due to some of the variables not being killed properly. This patch\nensures that all such variables are killed. NOISs MAR-0500-21140 and\nBIL-0700-31212\npossibility of getting a <STRLEN> (string too long) error when displaying\nthe comments from the Adverse Reaction Tracking package. This patch fixes\nthis problem.\n \n2) If the option Edit Prescriptions [PSO RXEDIT] is used to edit the SIG,\nthis function generates a new order. It was reported that the new order\ncreated had changed the dispensed drug totally. It had picked up the drug\n\n
\nThis patch will resolve the following issues.\n \n1. I18715588FY18 - Undefined error when ^ out of prompt\n2. INC0023405 - Set prompt default to NO instead of YES\n\n
\nIMPORTANT INSTALLATION NOTE:\n-----------\nRESET COPAY STATUS LM ROUTINE NEW\n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted Action\n------------- -------------------- ------\nPSO PATIENT MED ACC PRO NEW\nPSO PATIENT MED BILL PRO NEW\nPSO PATIENT MED CANCEL NEW\nPSO PATIENT MED EXPORT NEW\nThe Chief Business Office (CBO) is requesting system enhancements to\nPSO PATIENT MED PAT INQ NEW\nPSO PATIENT MED RESET NEW\nPSO PATIENT MED TPJI NEW\nPSO PATIENT MEDICATION MENU MODIFIED\n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) \nNew/Mod/Del------------- ---- ------------------ \n-----------\nThe Veterans Health Information Systems and Technology Architecture\nPSO PATIENT MEDICATION LIST LIST N/A NEW\n \nNew Service Requests (NSRs):----------------------------\n20150505 - Revenue Reporting Enhancements\n20150506 - Revenue Eligibility Enhancements\n20150507 - Revenue Operations Enhancements\n \n \nPatient Safety Issues (PSIs):\n------------------------------N/A\n(VistA) Integrated Billing (IB), Accounts Receivable (AR), and\n \n \nRemedy Ticket(s) & Overviews:\n-----------------------------\nN/A\n \nTest Sites:----------\nDurham VAMC\n \n \nOutpatient Pharmacy (PSO) software modules.\nSoftware and Documentation Retrieval Instructions:\n----------------------------------------------------\nPatches for this installation are combined in host file\nIB_2_568_PRCA_PSO_BUNDLE_T1.KID\n \nInstallation of this host file should be coordinated among the packages\naffected since only one installation is necessary.\n \nThe patches are:\n \n \n IB*2.0*568\n PRCA*4.5*315\n PSO*7.0*463\n \n Software and Documentation Retrieval Instructions\n-------------------------------------------------\nSoftware being released as a host file and/or documentation describingthe \nnew functionality introduced by these patches are available.\n The preferred method is to retrieve files from \ndownload.vista.domain.ext.\nThe mission of the Department of Veterans Affairs (VA), Office of\nThis transmits the files from the first available server. Sites may \nalso elect to retrieve files directly from a specific server. \n\nSites may retrieve the software and/or documentation directly using \nSecure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE \ndirectory at the following OI Field Offices:\n \nOI FIELD OFFICE FTP ADDRESS DIRECTORY \n--------------- -------------------- ------------------ \nAlbany: fo-albany.domain.ext anonymous.software\nInformation & Technology (OI&T), is to provide benefits and services to\nHines: fo-hines.domain.ext anonymous.software \nSalt Lake City: fo-slc.domain.ext anonymous.software\n The host file is located in the anonymous.software directory.\n Use ASCII Mode when downloading the file.\n \nDocumentation can also be found on the VA Software Documentation Library \nat: http://www4.domain.ext/vdl/\n \n--------------------------------------------------------------------------\nTitle File Name FTP Mode\nveterans of the United States Armed Forces. In meeting these goals,\n-------------------------------------------------------------------------\nOutpatient Pharmacy Technical\n Manual/Security Guide pso_7_ TM_R0417.PDF binary\nOutpatient Pharmacy \nBack-out, and Rollback Guide \n FY16RevenuePSOVIP_Deployment_Installation_Guide\n binary\n \n Sites may retrieve documentation directly using Secure File \nTransferProtocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the \nOIT strives to provide high quality, effective, and efficient\nfollowing\nOI Field Offices:\n \nAlbany: fo-albany.domain.ext\nHines: fo-hines.domain.ext\nSalt Lake City: fo-slc.domain.ext\n \nDocumentation can also be found on the VA Software Documentation Library\nat:\nhttp://www4.domain.ext/vdl/\n----------------------------\nInformation Technology (IT) services to those responsible for providing\n \nTitle File Name FTP Mode\n---------------------------------------------------------------------\nOutpatient Pharmacy Technical Manual/Security \nGuide pso_7_tm.doc Binary\nOutpatient Pharmacy Deployment, Installation,\n Back-Out, and Rollback Guide\n FY16RevenuePSOVIP_Deployment_Installation_Guide.doc\n Binary\n \ncare to the veterans at the point-of-care, as well as throughout all\n \n \nPatch Installation:\n \nPre/Post Installation Overview:\n-------------------------------\nN/A\n \nPre-Installation Instructions:\n------------------------------\nthe points of the veterans' health care. The VA depends on \nN/A\n \nInstallation Instructions:\n--------------------------\nThis process will install new and updated routines and other\ncomponents listed above. There is a post-install routine that will add\nentries to a number of files.\n \nThe patch will be released in conjunction with Integrated Billing\npatch, IB*4.5*568, and Accounts Receivable, PRCA*4.5*315.\nInformationManagement/Information Technology (IM/IT) systems to meet \n \n ************************ NOTE ************************\n IF A USER IS ON THE SYSTEM AND USING THESE PROGRAMS\n AN EDITED ERROR WILL OCCUR.\n The patch should be installed when NO Outpatient\n Pharmacy users are on the system.\n ******************************************************\n \n Installation will take less than 1 minute.\n \nmission\n Suggested time to install: non-peak requirement hours.\n \n \n 1. Obtain the host file IB_2_568_PRCA_PSO_BUNDLE.KIDS which contains\n the following patches:\n IB*4.5*568\n PRCA*4.5*315\n PSO*7.0*463\n \n 2. Startup KIDS\ngoals.\n ------------- Start up the Kernel Installation and Distribution \nSystem Menu option\n [XPD MAIN]:\n \n Edits and Distribution ...\n Utilities ...\n Installation ...\n \n Select Kernel Installation & Distribution System Option: \nINStallation \n \n---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n Unload a Distribution\n Backup a Transport Global\n \nThe overall FY16 HAPE Revenue Enhancement project has been further\n Select Installation Option: \n \n 3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD IB_2_568_PRCA_PSO_BUNDLE.KID\n -------------------------------------------------------------\n From the Installation menu, select the Load a Distribution option.\n \n When prompted for "Enter a Host File:", enter the full directory path\n where you saved the host file IB_2_568_PRCA_PSO_BUNDLE.KID (e.g.,\n SYS$SYSDEVICE:[ANONYMOUS] IB_2_568_PRCA_PSO_BUNDLE.KID).\n \ndivided into three sub-projects:\n When prompted for "OK to continue with Load? NO//", enter "YES." \n The following will display:\n \n Loading Distribution...\n \n IB*2.0*568\n PRCA*4.5*315\n PSO*7.0*463\n \n Use INSTALL NAME: IB*2.0*568to install this\n \n IB_2_568_PRCA_PSO_BUNDLE.KID distribution. \n \n 4. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter IB*2.0*568):\n a. Verify Checksums in Transport Global - This option will\n allow you to ensure the integrity of the routines that\n are in the transport global.\n b. Print Transport Global - This option will allow you to\n view the components of the KIDS build.\n c. Compare Transport Global to Current System - This \nThis patch is part of a multi-package build. There are three patches\nNSR #20150506\noption will allow you to view all changes that will be made \nwhen\n this patch is installed. It compares all components of\n this patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a\n backup message of any routines exported with this patch.\n It will not backup any other changes such as DD's or\n templates.\n \n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install?\nThe Revenue Eligibility Enhancements Project effort for the Chief\n NO//" respond NO.\n \n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? NO//" respond NO.\n \n \n \nPost-Installation Instructions:\n-------------------------------\nThere are no special tasks to perform after this patch installation.\nBusiness Office (CBO), bundles several NSRs with similar business\nneeds into a single requirements document. Successfully addressing\nthe requirements contained within this document will enable the\nDepartment of Veterans Affairs (VA) to appropriately bill certain\nsubsets of billable events by correcting, automating, or enhancing\ncurrent Veterans Health Information Systems and Technology\nArchitecture (VistA) systems.\n \nassociated with the FY16 HAPE Revenue Enhancement project - IB*2.0*568,\nNSR #20150507\nThe Revenue Operations Enhancements Project combines several NSRs, as\nwell. This effort enables the Department of Veterans Affairs (VA) to\nimprove revenue operation functionality related to repayment plans,\nlate charge capture, bill suspension reasons, the billing of\ndeactivated providers, and the display of appeal rights and\nresponsibilities on the Veterans Beneficiary travel Bill of \nCollectionsform. Implementation of the proposed enhancements will make a\nsignificant positive impact on stakeholders and target users.\n \nPRCA*4.5*315 and PSO*7.0*463. All three patches are to be installed\nNSR #20150505\nThe Revenue Reporting Enhancements Project will enable the VA to\nimprove tracking and reporting of revenue, and will support \nrevenuereporting business rules and guidelines.\n \n \nPSO*7.0*463 patch enhancements, pertinent to the above NSRs, include:\n \n1.) In the event of a Prescription Reset Status/Cancel Charges action,\nall automatic prepayment generation shall be\ntogether as a bundle, IB_2_568_PRCA_PSO_BUNDLE_T1.KID\neliminated.\n \n2.) All "credit balances" that are automatically generated in the event\nof a Prescription Reset Status/Cancel Charges action exemption to stop.\n \n3.) A new on-demand List Manager report will be made available for\nidentification of Prescription resets.\n 4.) The new on-demand report for processing Prescription Resets \nwillprovide an option to generate a Summary Report and/or Detailed Report.\n \n \n \n \nAssociated Patches:\n-------------------\nIB*2.0*568\nPRCA*4.5*315\n \nConcurrent Development / Dependencies:\n--------------------------------------\nN/A\n \n \nCategory\n--------\nRoutine\nTemplate\nOther\n \n \nPatch Components:\n----------------- \nDescription\nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------PSOCP \n\n
\nThis patch will resolve the following issues.\n \nINC0105896 - <SYNTAX> error\nINC0320678 - <UNDEFINED> Error\n\n
\nMedication Prescribing and Dispensing Updates.\n\n
\nMCCF EDI TAS EPHARMACY BUILDS 3 & 4\n\n
\nPSO*7*45 provides an API for the Clinical Reminders package. The API\nprovides patient and prescription information, based on a specified date\nrange and a specified list of medications, as it relates to the Hepatitis\nC Initiative. This patch will not affect users of the Outpatient Pharmacy\npackage. The PSOORAPI routine in patch PSO*7*45 provides an entry point\nthat returns patient and prescription information in a ^TMP global to the\nClinical Reminders package, based on the criteria passed into the call. \n\n
\n*************\n At the bottom of the report there is a section that displays other \noutpatient prescriptions dispensed in the previous year. The combination \nof long drug names and the status "DISCONTINUED/EDIT" would cause the \nreport to lose data at the right margin when printed. This patch \nreformats lines in the affected section to maintain spacing within the \nprinted margins.\n \nTool #1 - Medication Reconciliation\n Inpatient orders that do not have additional order text (such as large \nvolume IVs) are inadvertently skipping the BCMA LAST ACTION line. This \nTHIS ENTIRE PATCH DESCRIPTION NEEDS TO BE REVISED. RMS 3-12-12\npatch will include that line more consistently on all inpatient orders.\n \nTool #1 - Medication Reconciliation\n The display of previously expired and discontinued orders at the bottom \nof the report was selecting the LAST RELEASED DATE based on the \nprescription that had the latest expiration date. This patch corrects \nthat selection to display the proper release date that is most recent for \na given medication.\n \nTool #1 - Medication Reconciliation\n*************\n The listing of medications entered as "clinic medications" through the \nInpatient Medications for Outpatient (IMO) process was incorrectly labeled\nas an INP (Inpatient) Medication. This patch will display that category \nof medications as CLN, identified in the legend as Clinic Medications.\n \nTool #1 - Medication Reconciliation and Tool #4 - Remote Active Medications\n The statuses of remote outpatient medications shown in the Medication \nReconciliation profile and the Remote Active Medications health summary \ncomponent will now include "HOLD" medications.\n \n \nTool #2 - Medication Worksheet\n The hard-coded display of a the patient's last four digits of the SSN in\nthe body of the work sheet is removed. The release of health summary patch\nGMTS*2.7*85 now permits the removal of the patient SSN from the health\nsummary overall header, but this change permits the worksheet to be\nprinted with no SSN references remaining.\n \nTool #2 - Medication Worksheet\n The internal programming that selects the name of the pharmacy\ndivision shown at the top of the worksheet and the pharmacy phone\nThis patch corrects issues that have been reported with Medication \nnumber associated with it has been revised. The impact of this correction\nwill be seen mostly at legacy integrated systems.\n \nAlso included in this patch is the removal of routine PSOQUAP. This\nroutine was orphaned during the final testing of patch PSO*7*294. Its\nfunctionality is fully incorporated into routine PSOQUAP2 which is\nreferenced in the implementation guide.\nReconciliation Tool #1 (Medication Reconciliation Health Summary) and \nMedication Reconciliation Tool #2 (Medication Worksheet).\n \nTool #1 - Medication Reconciliation\n\n
\nThis patch will resolve the following issues.\n \n1. I9914421FY16 - all prescription information is not displayed on the\n Pharmacy verification screen\n2. R18151128FY18 - QTY Recalculation when Drug Changed\n\n
\nOne VA Pharmacy, redirect HL7 link PSORRXSEND from EMI to VIERS.\n\n
\nThis patch will resolve the following issue:\nINC0998874 - LON Cannot Print to suspense/ clear old records from RX suspense\n(Duplicate) file death causing suspense print to error out.\nINC0785349 - suspense function in Vista is not working \n(Duplicate) \nINC0411672 - PSO OPTION NOT WORKING\n(Duplicate) \nINC0301071 - TUA - prescriptions not printing\n(Duplicate) \nINC0190642 - CA SDM Ticket I18597371FY18 moved to SN. UNABLE TO RUN FULL LIST\n(Duplicate) SUSPENSE FUNCTION\n \n \nProblem: \n--------\nThe Marion VA Medical Center reported getting an <UNDEFINED> error when trying\nto print local labels in the RX SUSPENSE file (#52.5). Upon further analysis\nit was determined that a bad "AC" cross-reference entry in the RX SUSPENSE\nfile (#52.5) is causing the problem. Although the cross-reference is set, the\nrecord it is pointing to is no longer present on the file which consequently\ncauses the routine PSOSULBL to error out with an <UNDEFINED> error at BEG+6.\n \nINC1866048 - Suspense not printing, previously entered ticket INC1658361 which\nResolution:\n-----------\nThe reason why the "AC" cross-reference entry was not deleted along with the\noriginal record could not be identified. However, this patch modifies the\nroutine PSOSULBL to prevent the <UNDEFINED> error from happening when the\ncorrupted "AC" cross-reference is present. Furthermore, the PSOSULBL routine\nwas also modified to clean up the corrupt "AC" cross-reference.\n \nTechnical Resolution:\n---------------------\n was closed without assistance\nChanged the routine PSOSULBL at line tag BEG and TMP to prevent the\n<UNDEFINED> error and to kill off the corrupt "AC" cross-reference entry.\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC1866048 - Suspense not printing, previously entered ticket INC1658361 which\n was closed without assistance\n\n
\nThis patch will fix the following issue:\n1. Able to DC non-verified Rx order when another user is editing\nit in CPRS\n\n
\nThis patch has the following enhancements for Clinical Ancillary Services\n editing the Listman screen field "3) *Schedule:". Upon typing a ?\n at that prompt and selecting "A" for Administration Schedule File, the\n entries displayed will now include the Inactive text.\n \n \n2. Manage Hidden Icons (Actions) Outpatient\n \n Two new hidden actions are provided for Outpatient Pharmacy's menu \n option Patient Prescription Processing [PSO LM BACKDOOR ORDERS].\n \n(CAS) Enhancements (RXSU2).\n a. New hidden action "DM" for displaying dispense drug information \n during data entry. This hidden action will display key information\n about the order to help aid in the verification process of an order\n and also allow user to Enter another drug if desired. Key\n information includes:\n \n Example:\n \n DRUG NAME: xxxxxxxxxxxxxxxxxxx (IEN: 3)\n ORDERABLE ITEM TEXT:\n \n xxx xx xxxxx xxxxx xx xxxxx\n x xxxxxxxx xx xxxxxxxxxxxx\n \n MESSAGE: xxxx xxx xx xxxxx x xxxxxxxx\n QTY DISP MESSAGE: x xxxxxxxx xx xxxxxxxxx xxxx\n \n Return to continue or\n Select DRUG GENERIC NAME:\n \n b. New hidden action "VP" for displaying Provider information during \n \n data entry. This hidden action will display key information about\n the PROVIDER to help aid in the verification process of an order and\n also allow user to enter another provider if desired. Key \n information includes:\n \n Example:\n \n PROVIDER TITLE: xxxxxxxx\n \n PROVIDER REMARKS: xxx xxxxx xxxx\n1. Manage Lookup List Inactive Entries \n \n PROVIDER SPECIALTY: xxxxxx\n \n Return to continue or\n Select NEW PERSON NAME: \n \n \n3. Suppress Duplicate - Therapy Alerts\n \n Duplicate Therapy order check is suppressed in CPRS if the same\n \n provider is ordering the same drug within the last 25% of the\n medications' calculated days supply. All 3 above criteria must be\n met for this order check to be suppressed.\n Modified Pharmacy Backdoor menu option Patient Prescription Processing \n [PSO LM BACKDOOR ORDERS]. Added the text "** INACTIVE **" to the end \n the display of the ADMINISTRATION SCHEDULE file (#51.1) entries during\n\n
\nMPDU - MEDICATION PERMISSIONS/DISPENSING UPDATES - Build 3\n order items are not able to be marked for titrate.\n4. Outpatient Medication Controlled Substance order edit, unnecessary \n code removed.\n5. Manilla Phillippines unique address is stopping controlled substance\n orders from finishing.\n6. Undefined Error at ACP+21^PSOORNEW\n7. Patient address, risk of carryover information between patients in \n VAPA array.\n8. Allow "# of refills" entry to be edited on Controlled Substance orders\n \nThis patch will address the following issues:\n \n1. The PHARMACY PATIENT file (#55) should have only one logical data \n piece corresponding to RX PATIENT STATUS on the "PS" node.\n2. Display in the Patient's Medication Profile there is a leading zero \n in the quantity if it is a fractional quantity.\n3. An intermittent issue was found that some Non-Controlled Substance \n\n
\nInbound eRx Version 3 updates.\n\n
\nPatch PSO*7*452 is part of a Multi Build with patch PSS*1.0*215.\nPSO*7.0*452 contains the routine changes.\nPSS*1.0*215 contains the DD changes.\n \nThe NSRs involved in this build are:\nNSR20150311 High Cost Rx Report; NSR20151109 Pharmacy Print from Suspense\nby Category; NSR20150512 Early Warning Advisory for Approaching the \nend of Rx Number Ranges; and NSR20151001 Pharmacy Patient Demographics.\n\n
\nAs part of the Clinical Ancillary Services project (CAS) - Medication \n--------\nAs a pharmacist using the List of Patients/Prescriptions for Recall \nNotice Report, I need the system to correctly identify the Lot # of each \nindividual prescription fill (original or refill and locally dispensed or \nCMOP) so that all prescriptions fills with that Lot # are accurately \nreported.\n \n1. I want the report to pull the Lot # that corresponds to the \n individual fill represented by a line of data (original or refill or \n partial).\nPermission/Dispensing Updates (MPDU), the Outpatient package has been\n2. I want the report to pull the Lot # that corresponds to the \n manner in which the prescription was dispensed (VAMC-local or CMOP\n fill).\n3. I want the structure and header of the report to remain unchanged.\n \n \nResolution:\n-----------\nLine tag LOT^PSORLST2 has been modified to also check the CMOP node \nfor a CMOP fill (original or refill) and include it in the report.\nmodified to address the following:\n \n \nItem #2:\n--------\nAs a pharmacist entering an outpatient prescription through VistA, I want \nonly medication routes that are appropriate for use with the medication I \nselect displayed so that I am prevented from selecting the incorrect \nroute subsequently increasing patient safety.\n \n1. When entering an outpatient prescription into VistA, I only want \n \n medication routes associated with the medication dosage form for the \n medication selected displayed as available for selection. \n2. If I enter a medication route that is not associated with the \n medication's dosage form, I want the route entered matched to the \n available routes as an exact full-text match.\n a. If I enter a route that is only a partial match, I want the \n standard FileMan response of "??" to alert me that a match was not\n found.\n b. If I enter a complete and exact-match route, I want that route \n selected for use with that medication order.\n1. Modify the List of Patients/Prescriptions for Recall Notice Report\n \n \nResolution:\n-----------\nRoutines PSOORED5 and PSOBKDED were modified with the following:\n1. If a default med route is not defined, "PO" will not be displayed; a\n null value will be displayed as default.\n2. Med routes that are exact matches or abbreviated matches will be \n allowed.\n3. A single "?" will show a short list of med routes that are defined\n2. Limit the Display of Medication Routes for Outpatient Order Dialogs\n under the orderable item.\n4. Partial matches will be allowed if found in the short list, but not\n otherwise.\n3. Check dosage form to determine appropriate default route\n \nItem #1:\n\n
\n1) When using the call DFN^PSOSD1 provided by DBIA #1281, an undefined\nchecks for the inactivation date before building the drug-drug\ninteractions.\n \n3) The following NOISs, CON-0300-11493, DUB-0400-31698, and NCH-0800-41306\nreported a problem when editing prescriptions in a certain sequence was\nbeing saved with the name of the patient from a previously edited\nprescription. This error did not occur every time a prescription was\nedited, but after using certain options and actions together where\nvariables were not being cleaned up appropriately. With the release of\nPSO*7*36 and PSO*7*37 to the field the name-changing problem has no longer\nvariable error was reported (HD+11^PSOSD1:1, %DSM-E-UNDEF, undefined\nbeen reported. In an effort to try an identify any possible prescriptions\nwhere the patient name may have been changed inappropriately a new option,\nSearch For Mismatched Patient Orders [PSO RX SEARCH] will be sent out in\nthis patch. This new option will search the PRESCRIPTION file (#52) and\nproduce a report with any possible problem prescriptions. This new option\nwill not be attached to any menu, but can be assigned to anyone Pharmacy\nand IRM deems appropriate.\nvariable PSOBAR4). This patch fixes this problem.\n \n2) The INACTIVATION DATE field (#7) of DRUG INTERACTION file (#56) is\nbeing populated by Pharmacy Data Management module, Enter/Edit Local Drug\nInteraction [PSS INTERACTION LOCAL ADD] option, to inactivate a\nparticular set of drugs that was once set up as interactive. This patch\nensures that the call to the routine EN^PSOORDRG provided by DBIA #2190,\n\n
\nRestoration of changes introduced in patch PSO*7*504. The changes made to \nPSORENW and PSORENW4 were inadvertently left out of patch PSO*7*508.\n\n
\nMCCF EDI TAS EPHARMACY BUILDS 5 & 6\n\n
\nThis patch will resolve the following issue.\nINC2842893 - Removed from CMOP Suspense, returned to OP Suspense - outpatient\n prescriptions not suspending to CMOP after PSO*7*482 SEQ #435\n \nProblem: \n--------\nOutpatient pharmacists at Louis Stokes Cleveland VA Medical Center reported a\nglitch where a suspended Rx is edited and re-suspended appropriately but they\nare not being sent to CMOP. This problem happens when a new CMOP prescription\nis entered/finished and immediately after (without leaving the patient's\nprofile) the user requests a partial fill on the same prescription and\n \nperforms and edit on any field (e.g., QTY, FILL DATE, DAYS SUPPLY, etc.).\nThese steps wrongly caused the prescription to be removed from the CMOP\nSuspense queue and placed on the Local Suspense queue.\n \nResolution:\n-----------\nOutpatient Pharmacy will now check whether a partial was entered for a CMOP\nsuspended prescription and it will not move it from the CMOP Suspense queue\ninto the Local Suspense queue if that's the case.\n \nINC2842893 - Removed from CMOP Suspense, returned to OP Suspense - outpatient\nTechnical Resolution:\n---------------------\nChanged the line UNSUS+1^PSOCMOPC to check whether a partial was placed by\nchecking the variable RXPR and PSOFROM and it will not move the CMOP\nSuspended prescription into the Local Suspense queue.\n \nINC2882730 - Erroneous SC conditions are being displayed during pharmacy\n prescription processing\n \nProblem: \n prescriptions not suspending to CMOP after PSO*7*482 SEQ #435\n--------\nOutpatient pharmacists at St. Cloud VA Health Care System reported a glitch\nthat started happening after patch PSO*7*514 was installed. They noticed that\nnumerous male patients were showing up in outpatient pharmacy prescription\nprocessing as having SC conditions for ovarian disease or gynecological\nissues. When checking back to the patient information screen in VISTA\npharmacy prescription processing or CPRS, the pharmacists discovered in many\ncases the patient was only SC for tinnitus, yet a big list of other \ndisabilities were listed at the very end of pharmacy prescription processing\nwhen it lists the patient's SC conditions, often with the gynecological \nINC2882730 - Erroneous SC conditions are being displayed during pharmacy\ncondition. After investigating the issue it was discovered PSO*7*514 changes\ndid not clear the list of disabilities from the previous patient worked on\nby the user and carried them over to the subsequent patient worked on the\nsame session before exiting the Patient Prescription Processing [PSO LM \nBACKDOOR ORDERS] option.\n \nResolution:\n-----------\nThe Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option was \nchanged to properly reset the list of disabilities every time the user \n prescription processing\nselects a new patient.\n \nTechnical Resolution:\n---------------------\nAdded the command K PSODISAR at CHKPAG+1^PSOMLLD2 in order to reset the\nlist of disabilities before retrieving it from the PATIENT file (#2).\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n
\nWhen users are entering a new complex order using option PSO LM BACKDOOR \nORDERS and afterwards are editing the dosage fields and they jump out of\ncertain fields, the medication's SIG is truncated after the first THEN\nconjunction of the medication profile.\n\n
\nThis patch will resolve the following issues:\n1. INC0698370 - OneVA Can't see patient's remote RX's\n2. INC0908814 - Last Fill Date shows incorrect MAIL/WINDOW value\n3. INC1033035 - Documentation changes needed\n\n
\nThis patch will upload "new" providers for a site into the New Person \nThe law creates a new paradigm for providing health care, set forth in the\nVeterans Choice program provisions within Title I Section 101 of VACAA. VA\nis utilizing a Contractor to provide health care and third party\nadministrative (TPA) services set forth through VACAA Section 101. \n \nAs a result of this law, VA must upload a list of non-VA medical care\nproviders into the VistA system in order to maintain an accurate and\nupdated list of non-VA providers in the Choice program. Refer to the\nNon-VA Care Provider SharePoint site for further information:\nhttps://vaww.dwh.cdw.portal.domain.ext/sites/Non-VA%20Care%20PC3%20and%20Choic\n(#200) file. A "new" provider is defined as a provider whose National \ne/SitePages/Home.aspx.\n \nCA-SDM Ticket: I12935021FY17\n \nNOTE: The providers loaded by this patch are not eligible to be selected \nas ordering providers in CPRS. Use is restricted to the option "PSO LM \nBACKDOOR ORDERS" ("Patient Prescription Processing").\nProvider Identifier (NPI) is not on file yet at a site.\n \nOn August 7, 2014, the President signed into law PL 113-146, the Veterans \nAccess, Choice, and Accountability Act of 2014 (VACAA). The law offers an \nadditional authority for VHA to expand current capacity and ensure that \nVeterans have timely access to high-quality care. \n \n\n\nThis patch will address the following two issues:\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n \n1. INC2091135 - Incorrect drug on label for OneVA refill request\n \nProblem: \n--------\nA pharmacist refilled a OneVA Rx and verified the correct local drug \nmatched to the remote site drug. \nThe labels printed with a different drug that was on the patient's \n \nprofile. This happened with 5 prescriptions. Some did print correct. \nPartials were done and some came through in the same erroneous way.\n \nResolution:\n-----------\nResolve this with the following:\n- A 3 second hang will be added prior to reading the HL7 response\nwith the label information from the Host site\n- Once the HL7 message is read, the Rx number selected at the\nRemote site will be compared to the Rx number returned in the HL7 label\n1. Incorrect drug on label for OneVA refill request\nmessage from the Host site and if this is a match, processing will\ncontinue as normal\n- If the two Rx's do not match, the message below will be displayed\nand processing will cease \n 'Label interrupted due to HL7 message corruption.'\n 'Please request a Partial Fill in order to generate a reprint label.'\n- In the background, invisible to the user, an error trap entry\nwill be made so more research can be done to find the root cause of this\nhappening. The error in the error trap will show as 'MISMATCH RX'\nModify the following routines: PSORRX2, PSORWRAP \n2. OneVA prescription error\n \n2. INC2394703 - OneVA prescription error\n \nProblem: \n--------\nThe Saginaw VA Medical Center reported that a OneVA prescription fill\nrequest appears to have prompted ScripTalk label to print at host site. The\nHost site requeued Vista label and it appears prescription was filled twice.\n \nResolution:\n \n-----------\nThe OneVA Pharmacy functionality did not prevent a ScripTalk label from\nprinting at the host site when a refill/partial was requested by the patient\nat a remote site. A fix is being introduced by this patch to prevent the\nScripTalk label from printing at the host site when a OneVA prescription\nrefill/partial is requested is filed.\n \nTechnical Resolution:\n---------------------\nChanged the routine PSORWRAP to set the variable PSOONEVA before calling the\nPatient Safety Issues (PSIs):\nlabel printing routines (DQ^PSOLBL) and then changed the routine PSOTALK to\nQUIT if the label being printed is a OneVA Pharmacy label at the remote site.\n-----------------------------\nHITPS-6386 - INC2091135\n \n\n
\nThis patch addresses one (1) VistA Outpatient Pharmacy issue:\n \nThe installment of patch PSO*7*537 introduced an error that occurs \nafter a user edits a dosage.\n\n
\nCORRECT INAPPROPRIATE DATE ENTRY IN COPY FUNCTION\n\n
\nINBOUND ERX MAINTENANCE PATCH 1\n\n
\nThe Outpatient Pharmacy package utilizes a field in the NOUN (#50.6066)\nSubfile of the DOSAGE FORM (#50.606) File called NOUN. It is used to\nbuild Possible Sigs for Outpatient orders entered through Computerized\nPatient Record System (CPRS). The use of that field will be expanded upon\nin the Pharmacy Ordering Enhancements project. The changes in this patch\nwill not affect any of the current Outpatient Pharmacy functionality, but\nthis patch will be a requirement of the Pharmacy Ordering Enhancements\nproject.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7*543.\n\n
\nWhen finishing a non-controlled drug order immediately after finishing a\nrenewal of a controlled drug, an incorrect expiration date occurs. The\nnon-controlled drugs are finished with the expiration date of the\ncontrolled drug.\n\n
\nThis patch will fix an issue where NON-VA medications are being returned \nin the VPR XML results when they are dated outside of the entered date \nrange for resulting.\n\n
\nThis patch will address the following two issues:\n--------\nAnn Arbor VAMC reported about 5 or 6 entries in their error trap related to\nOneVA Pharmacy functionality. After some research it was determined that the\nerror was happening because OneVA Pharmacy HL7 messages were being sent to\nthe Ann Arbor VAMC erroneously. The prescription number in the HL7 message\nrequest did not exist in the Ann Arbor site as it was probably supposed to\nbe sent to a different site. That was what caused the hard error reported.\nAt this point it is not clear why HL7 messages have been routed the wrong\nsite.\n \n \nResolution:\n-----------\nThe processing of incoming HL7 messages for OneVA Pharmacy fill requests\nis being changed to check whether the prescription in the request actually\nbelongs to the site it arrived. If the prescription does not exist at the\nsite the message below will be displayed to the dispensing site user that\nis requesting the OneVA fill:\n \n Processing refill request. Please be patient as it may take a moment\n for the host site to respond and generate your label data...\n1. $ZE= <UNDEFINED>PROCESS+24^PSORWRAP *MW\n \n Unable to complete transaction. \n \n The Rx #999999 does not belong to this facility (REMOTE SITE NAME). Please,\n try to place the fill request again. It may take up to 4 attempts to get a\n successful response. If the issue continues, please contact IT Support for\n assistance.\n \n Press RETURN to continue: \n \n \nTechnical Resolution:\n---------------------\nChanged the routine PSORWRAP at REMOTE+21 to verify that the prescription \nnumber in the incoming OneVA HL7 message actually belongs to the site\nreceiving the message. If it does not, stop processing and respond back to\nthe sending site with the message above. \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC5310207 - $ZE= <UNDEFINED>PROCESS+24^PSORWRAP *MW\n \nProblem: \n\n
\nThis patch will address the following two issues:\n1. INC6047771 - ERX not including info after patch PSO*7*551\n (d)INC6131517 - Recommendations for improvements to new eRx system\n (d)INC6087293 - Inbound eRx prescriptions not showing quantity, days\n supply and refills under the\n \nProblem: \n--------\nVA Sierra Nevada Health Care System reported that after the installation of \nthe patch PSO*7*551 they noticed that some fields related to the eRx \nprescription (Qty, Days Supply and Refills) were no longer being displayed\n \nwhen viewing the corresponding VistA Pending Order or Active Prescription. \nIt was confirmed that this issue was indeed caused by the patch PSO*7*551.\n \nResolution:\n-----------\nThis patch will restore the functionality accidently removed by the patch\nPSO*7*551 by restoring the display of the fields Qty, Days Supply and \nRefills from the original external prescription (eRx).\n \nTechnical Resolution:\nINC6047771 - ERX not including info after patch PSO*7*551\n---------------------\nChanged the routine PSOERXU1 at line tag DERX1+95 to re-include the line \nbelow that was removed by PSO*7*551:\n \n S IEN=IEN+1,@GL@(IEN,0)=LINETXT\n(d)INC6131517 - Recommendations for improvements to new eRx system\n(d)INC6087293 - Inbound eRx prescriptions not showing quantity, days supply\n and refills under the\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7*567.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7*564.\n\n
\nMENTAL HEALTH NCC PROJECT 5.01\n\n
\nThe following NOISs, NJH-0600-21694, SLC-0200-50488, PRO-0700-10326 \n In an effort to try and identify any possible prescriptions where the drug \n name may have been changed inappropriately, a new option Search for \n Mismatched Drug Orders [PSO RX DRUG SEARCH] will be sent out in this patch. \n This new option will search the PRESCRIPTION file (#52) and produce a \n report with any possible problem prescriptions. This new option will not \n be attached to any menu, but can be assigned to anyone Pharmacy and \n Information Resources Management (IRM) deems appropriate. \n reported the following problem. When editing prescriptions in a certain \n sequence they were being saved with the name of the patient from a \n previously edited prescription. This error did not occur every time \n a prescription was edited, but after using certain options and \n actions together where variables were not being cleaned up appropriately. \n With the release of PSO*7*44 to the field, the drug name-changing problem \n has no longer been reported. \n \n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7*569.\n\n
\nWhen entering a duplicate prescription, if the original prescription was\nsent to CMOP, rejected and filled locally, then the discontinue message\nwill report that the original prescription was not filled.\n\n
\nWhen choosing a primary sort of PATIENT or ROUTE and secondary sort of \nFLAGGED, the no orders are displayed. Also, when changing orderable item \non a prescription, if the units are omitted from the dose, the DISPENSE \nUNITS PER DOSE field in computed incorrectly.\n\n
\nDUPLICATE RX CREATED IN PSO LM BACKDOOR ORDERS\n\n
\nHPS patch to address overwritten error messages and deleted providers in\nPSO LM BACKDOOR, and an index error in PSO COPAY RESET.\n\n
\nThis patch will address the following issue: \n(d)INC7720939 - Inbound eRx 2 prescriptions with fatal errors\n(d)INC7774257 - Inbound eRx - Fatal Errors\n(d)INC7793995 - Inbound eRx fatal error on one prescription in Corpus Christi\n Outpatient Clinic Pharmacy\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \n \nDefect Tracking System Ticket(s) & Overview: \n--------------------------------------------\nINC7463016 - Septra SS prescription - Inbound eRx (CORPUS CHRISTI) received\n an Rx and an error message was generated\n(d)INC7463169 - Ammonium Lactate prescription - Inbound eRx (CORPUS CHRISTI)\n received an Rx and an error message was generated Detailed\n Description \n(d)INC7216102 - Inbound eRx (CORPUS CHRISTI) received an Rx and an error\n message was generated\n(d)INC7720939 - Inbound eRx 2 prescriptions with fatal errors\nINC7463016 - Septra SS prescription - Inbound eRx (CORPUS CHRISTI) received\n(d)INC7774257 - Inbound eRx - Fatal Errors\n(d)INC7793995 - Inbound eRx fatal error on one prescription in Corpus Christi\n Outpatient Clinic Pharmacy\n \nProblem: \n--------\nCorpus Christi VA Specialty Outpatient Clinic reported a fatal error \n(<SUBSCRIPT> error) when trying to validate the Drug/SIG for an eRx record\nwhen using the Complete Orders from eRx [PSO ERX FINISH] option. The same\nerror was reported by McAllen Outpatient Clinic. The error happens due to a\n an Rx and an error message was generated\nmissing "B" cross-reference entry in the PHARMACY PATIENT file (#55) for the\npatient being processed. It is unknown the reason why the "B" cross-reference\nentry is missing for certain patients.\n \nResolution: \n-----------\nThis patch will prevent the error from happening for patients that have the\n"B" cross-reference entry missing by ignoring it. The missing "B" cross-\nreference entry will have no negative impact in the processing of eRx \nprescriptions for such patient because its use in the code was unnecessary\n(d)INC7463169 - Ammonium Lactate prescription - Inbound eRx (CORPUS CHRISTI)\nfor the option to work properly.\n \nTechnical Resolution: \n---------------------\nModified the line tag DU+1^PSOERXD1 to instead of using the "B" cross-\nreference to retrieve the patient IEN (Internal Entry Number) and set the \nPSODFN variable to set the variable PSODFN directly with the PATIEN content.\n received an Rx and an error message was generated Detailed\n Description \n(d)INC7216102 - Inbound eRx (CORPUS CHRISTI) received an Rx and an error\n message was generated\n\n
\nThis patch will fix the following issue:\n \nThe incorrect fill is marked as dispensed and released if two fills for\none prescription is sent to the dispensing machine.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7*570.\n\n
\nThis patch will address the following issue: \nDefect Tracking System Ticket(s) & Overview: \n--------------------------------------------\nINC6715041 - software problem - instructions (#TABS PER DOSE) got altered on\n prescriptions with renewals. RX 4879200 -TO RX 487920A,B,C\n \nProblem: \n--------\nThe CPRS patch OR*3*440 was released Back in 2017 to address a problem with\nthe Ward Clerk Menu [OR MAIN MENU WARD CLERK] option that was causing some\nOutpatient Pharmacy orders and prescriptions to have the wrong dispense units.\n \nAlthough the patch seems to have resolved the problem by preventing new orders\nwith this issue from being created it did not go far enough to prevent that\nexisting orders with the issue could be copied or renewed and pass the problem\nforward the problem to newly created orders.\n \nResolution: \n-----------\nThe patch will generate a list (see example below) of potential outpatient\nprescriptions and will send it via Mailman message to all users that hold the\nPSNMGR security key. These entries on this list should be analyzed one by one\nINC6715041 - software problem -- instructions (#TABS PER DOSE) got altered on\nby the Pharmacy ADPAC and a determination should be made as to whether the\noutpatient prescription dose and dispense units are correct for the dispense\ndrug or not. If it is determined that the prescription dose and dispense unit\nare incorrect the Outpatient Pharmacy staff should discontinue the prescription\nand re-renter it with the correct dosing and dispense unit information. \n \nList example:\n---------------------------------------------------------------------------\nPATIENT (L4SSN)\n RX # DISPENSE DRUG DOSE ORD. UNITS STRENGTH\n prescriptions with renewals. RX 4879200 -TO RX 487920A,B,C\n---------------------------------------------------------------------------\nDivision: CHEYENNE VAM&ROC \nPSOPATIENT,ONE (3202)\n 2298748 ACETAMINOPHEN 325MG TAB 325 1 999\nPSOPATIENT,THREE (7894)\n 2298875 ACETAMINOPHEN 325MG TAB 325 1 999\n \nDivision: GREELEY CLINIC \nPSOPATIENT,TWO (1234)\n 2298877 ACETAMINOPHEN 325MG TAB 325 1 999\n \n \n3 prescriptions found. \n \nTechnical Resolution: \n---------------------\nCreated post-install routine PSO583PI loop through the PRESCRIPTION file (#52)\nand check the dose for current prescriptions and the dispense unit and\nstrength of the dispense drug. If a discrepancy is found a prescription is\nincluded on the Mailman message sent to the PSSMGR security key holders.\nPatient Safety Issues (PSIs):\n-----------------------------\nHITPS-6775\n \n\n
\nThis patch will address the following eRx issues: \n \n list of status screened out for "Refill Response" type records, which will\n drop the erroneously RRP records from the Work Queue as soon as the patch\n is installed.\n2) Changed the routine PSOERX1B at line tag ADD+64 and the routine at line tag\n AUTODC+38 to only update the record status to RRP if the record type is a\n "Refill Request". This will prevent "Refill Response" records from being \n wrongly updated to RRP.\nPatient Safety Issues (PSIs):\n-----------------------------\nN/A \n \nDefect Tracking System Ticket(s) & Overview: \n--------------------------------------------\n1. INC7957997 - Grammar error in eRx processing screen\n \nProblem: \n \n--------\nAlaska VA Healthcare System reported a grammar issue while accepting an eRx\nprescription into VistA via the Complete Orders from eRx [PSO ERX FINISH]\noption. After validating a patient via this option the software checks whether\nthe same patient has other eRx prescriptions waiting to be validated and if\nany additional are found it will issue the following message/prompt (example):\n \n This patient has other prescriptions for: Dec 04, 2019\n Patient: XXXXXX,XXXXXXX\n \n1. INC7957997 - Grammar error in eRx processing screen\n DRUG PROVIDER REC DATE\n --------------------------------------------------------------------------\n 1.) GABAPENTIN 300 MG ORAL CAPSUSMITH,KATELON JAN 04, 2020\n 2.) METOPROLOL SUCCINATE ER 100 SMITH,KATELON JAN 04, 2020\n \n Would you like apply the above validation to these prescriptions?\n Enter Yes or No: N//\n \nThe issue is with "...like apply..." which should read "...like to apply..."\n \n \nResolution: \n-----------\nInserted "to" between "like" and "apply".\n \nTechnical Resolution: \n---------------------\nChanged the routine PSOERX1B at line tag BPROC+41 to include "to" between\n"like" and "apply".\n \n \n2. INC6442610 - inbound eRx issue - order stuck in queue\n2. INC6442610 - inbound eRx issue - order stuck in queue\n INC6659074(d) - Wrong erx status code generated in VistA inbound erx\n software version 3.0\n INC6245922(d) - eRX issue with acknowledging messages in RRD status that\n change to RRP status for 1 patient\n \nProblem: \n--------\nVA Puget Sound Health Care System reported that Refill Response eRx records\nwith a status of RRP (REFILL REQUEST PROCESSED) are accumulating on their eRx\n INC6659074(d) - Wrong erx status code generated in VistA inbound erx\nWork Queue and the users do not have a mechanism to remove them. This problem\ninterferes with their work because these types of records fills up pages and\nof their Work Queue and there is no further processing needed to be performed\non them. Upon extensive research it was determined that RXA (REFILL RESPONSE\nACKNOWLEDGED) Refill Request records were erroneously being updated to RRP\nonce a new prescription was accepted via eRx for the same medication that was\npreviously designed. To illustrate a little further the sequence of events\nhappened the following way:\n \n 1) Patient had eRx 'A' that had already been previously filled and did not\n software version 3.0\n have any more refills left. \n 2) The VA Pharmacist uses the RR (eRx Refill Request) through the Patient\n Prescription Processing [PSO LM BACKDOOR ORDERS] option and a message is\n sent out to the Dr's Office. \n 3) The Dr's Office denies the Refill/Renewal by sending a new eRx record to\n VistA which create a Refill Request records with a status of RXD (REFILL\n RESPONSE DENIED/DNTF).\n 4) The VA Pharmacist then acknowledges the RXD record through the Complete\n Orders from eRx [PSO ERX FINISH] option, which changes the status of the\n Refill Response from RXD to RXA successfully removing it from the eRx\n INC6245922(d) - eRX issue with acknowledging messages in RRD status that\n Work Queue.\n 5) Later, the Dr's Office sends to VistA a new prescription for the patient \n with the same medication\n 6) The VA Pharmacist processes the new eRx prescription and Accepts it. \n This action creates the problem because it mistakenly changes the status\n of the previously updated Refill Response from RXA to RRP, bringing it\n back to the eRx Work Queue which does not offer any means for the users\n to remove such records from the Work Queue.\n \nResolution: \n change to RRP status for 1 patient\n-----------\nThis patch will stop the status update from RXA to RRP described in the step\n#6 above. Furthermore, it will remove all RRP records from the eRx Work Queue.\nThe RRP records will still be visible if users intentionally are looking for\nthem through the SR (Search Queue) action, which is how the Work Queue was\ndesigned to work originally.\n \nTechnical Resolution: \n---------------------\n1) Changed the routine PSOERX at line tag BLDITEM+22 to include "RRP" in the \n\n
\n1. Pharmacy Benefits Management (PBM) has requested that Technical\nthe ordering processes by entry of the IEN.\nServices develop a software patch that would disable the DRUG file (#50)\nlookup by Internal Entry Number (IEN) during order entry\nprocesses. The pharmacy software has always allowed IEN lookup and quick\ncode lookups at the request of field users. A quick code is a\nuser-defined synonym for a drug (i.e., A325->Acetaminophen 325mg Tab). PBM\nprovided guidance to VA Medical Centers in the past to not use low numbers\nfor quick codes and to inactivate the first 50 entries in the drug file to\nreduce the chances of error. This patch would eliminate drug selection in\n\n
\nINC8357891 - Inbound eRX drug incorrectly filtered.\nThe detailed description of this build can be found in the National Patch \nModule under PSO*7*586.\n\n
\nCPRS patch OR*3*397 allowed a user with ORSUPPLY key to release supply \nitem orders. In backdoor pharmacy, when finishing a pending renewal \nsupply item order that was released by ORSUPPLY/ORELSE key holders (not \nauthorized to write med orders), a hard error is generated. This issue is \naddressed in this patch. Jazz #1203196\n\n
\nIDENTIFY USER EDITING NEW PROVIDER\n\n
\nINC9101449 - Errors encountered when running List of Override \nPrescriptions Report\n\n
\n \n(NCCC). The NCCC is responsible for VA's compliance with the clozapine \n--------\nAt least one site has reported temporary registration starting with the \nletter "R" when they were expecting it to start with "Z".\n \nResolution:\n-----------\nThe PSO574P pre-init routine also updates the CLOZAPINE WEEKEND \nREGISTRATION list that is stored in ^XTMP("PSJ CLOZ"). This will ensure \nthat any temporary registration numbers that were generated during IOC \ntests and were not used will be recovered. This issue was revealed in \nRisk Evaluation and Mitigation Strategy (REMS), which is mandated by the \nthe MailMan messages sent to the CLOZAPINE ROLL-UP Mail Group in Forum.\n \n6. Ensure "Expires:" Date is Correct\nDefect 1132368\n \nProblem:\n--------\nThe CPRS team found a typo in routine PSODIR2. The code had a comma \nwhere it should have a less than sign. Only clozapine prescriptions \nwould have been affected. This logic is used to create the value for the \nFood and Drug Administration (FDA) for tracking clozapine patients. \n"Expires:" prompt in Patient Prescription Processing.\n \nResolution:\n-----------\nRoutine PSODIR2 was corrected.\n \n7. Dose default is missing for active or pending prescriptions.\nDefect 1106891\n \nProblem:\n \n--------\nThe default dose is missing when editing all prescriptions in Pharmacy \nbackdoor orders. It should be there for non-clozapine prescriptions. \nThe prior fix removed this for all prescriptions.\n \nResolution:\n-----------\nThe logic in routines PSOBKDED and PSONEW1 was modified to only remove \nthe default dose for Clozapine prescriptions.\n \nThe multi-build contains the Mental Health patch YS*5.01*154 and the \n \n8. Remove the "Quantity Being Changed" message displaying during backdoor \npharmacy processing of a Clozapine Outpatient 4 Day Override Order.\nDefect 1155637\n \nProblem:\n--------\nThe "Quantity Being Changed" message was being displayed when a \npharmacist was editing a 4 day temporary override Clozapine \nprescription. Users at the IOC sites found this to be confusing wand \nOutpatient Pharmacy patch PSO*7.0*574. The list of defects and their \nwanted it removed.\n \nResolution:\n-----------\nThe routine PSOSIG was modified to display this message ONLY for \nnon-clozapine prescriptions.\n \n9. CPRS Complex Order Default Dose Incorrect\nDefect 1180952\n \nresolution is below.\nProblem:\n--------\nComplex orders which have multiple dosages were not displaying the \ncorrect defaults during dosage edit.\n \nResolution:\n-----------\nRoutine PSOBKDED was modified to add the default dose.\n \n10. Missing Unit Price of Drug\n \nDefect 1181628\n \nProblem:\n--------\nPrescriptions for certain medications were not storing the UNIT PRICE OF \nDRUG field. This occurred when the DRUG had a REORDER LEVEL field (#11) \nvalue of zero or null.\n \nResolution:\n-----------\nDefect Tracking System Ticket(s) & Overview:\nThe branching logic in the SET^PSODRG subroutine was corrected.\n \n \n11. Temporary numbers generated off the date\nDefect 1181858\n \nProblem:\n--------\nThe logic to generate a temporary clozapine registration number was not \nalways generating a sequential counter.\n--------------------------------------------\n \nResolution:\n-----------\nThe logic in FINDNEXT^PSOCLUTL was modified.\n \n \n12. ^XTMP("PSJ CLOZ",0) purge date\nDefect 1181868\n \nProblem:\nThe MENTAL HEALTH NCC WARRANTY RELEASE 5.01 multi-build is a warranty \n \n--------\nThe purge date in the ^XTMP("PSJ CLOZ",0) global node was not always set \nto the same number of days in the future. This is a matter of programming \nstyle. No error was generated; no functionality was affected. The \ndevelopment accepted this as a defect to end the discussion. The change \ncannot be seen by users and there is no way to test this.\n \nResolution:\n-----------\nRoutine PSOCLO1 was changed to call the line tag XTMPZRO^PSOCLOU.\nPatch PSO*7.0*574 contains the following fixes:\n \n13. Expiration Date Calculated Incorrectly\nDefect 1182728\n \nProblem:\n--------\nWhen a Clozapine prescription was being edited the expiration date may \nnot have been computed correctly. This was related to editing the \nquantity and days supply values.\n \n \n \nResolution:\n-----------\nRoutines PSOCLO1, PSODIR1, and PSOORED6 were modified. The logic to \ncompute the expiration was moved to the new subroutine EXPDT^PSOCLO1.\n \n14. Patient Lookup in Register Clozapine Patient [PSOL REGISTER PATIENT]\nDefect 1210946\n \nProblem:\n1. Incorrect computation of drug costs\n--------\nThe Patient Lookup in the Register Clozapine Patient [PSOL REGISTER \nPATIENT] option doesn't allow a user to enter the last initial and last 4 \ndigits of the patient's Social Security Number (SSN).\n \nResolution:\n-----------\nRoutine PSOCLUTL was modified in the REG subroutine to add an "M" to the \nDIC(0) value to allow a patient lookup on multiple cross-references.\n \n Defect 1132310\n15. Error on Clozapine Inpatient Medication\nDefect 1227862\n \nProblem:\n--------\nWhen a user enters the Inpatient Order Entry [PSJ OE] option for \nClozapine patients an <UNDEFINED> error occurs. The PSODFN variable is \nundefined,\n \nResolution:\n INC7277287 - East Bay Division - Martinez Outpatient Clinic\n-----------\nRoutine PSOCLO1 was modified to set PSODFN if it's undefined, based on \nthe value in DFN.\n \n * * * * * *\n \nTest Sites:\n----------\n - West Los Angeles VAMC (691)\n - N. Florida /S. Georgia VAMC (573)\n INC7340377 - VA Connecticut Healthcare System West Haven Campus\n - VA Connecticut Healthcare System - West Haven Division (689)\n \nThere are no documentation updates associated with this patch.\n \nPatch Installation:\n \nPre/Post Installation Overview:\n-------------------------------\nThere are no tasks to be performed before the installation of this \nmulti-build. Note that the routines should be backed up to a PackMan \n \nmessage before installing the build.\n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 minutes\nto install. It should not be installed when the YSCL DAILY TRANSMISION \noption is running. If unsure when that is check the OPTION SCHEDULING \nfile (#19.2) using FileMan:\nProblem:\n \nSelect VA FileMan Option: Inquire to File Entries\n \nOutput from what File: OPTION SCHEDULING// (17 entries)\nSelect OPTION SCHEDULING NAME: YSCL DAILY TRANSMISSION\nAnother one: \nStandard Captioned Output? Yes// (Yes)\nInclude COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no \nComputed Fields\n \n--------\nNAME: YSCL DAILY TRANSMISSION\n QUEUED TO RUN AT WHAT TIME: OCT 05, 2019@01:30\n RESCHEDULING FREQUENCY: 1D TASK ID: 2577736\n \nInstallation Instructions:\n--------------------------\n1. The KIDS multi-build can be found in the VistA software repository at \ndownload.vista.domain.ext\n \n ANON$:[ANONYMOUS.ANONYMOUS]MH_NCC_WARRANTY_5_01_T06.KID\nrelease for the National Clozapine Registry (NCR) software. This release \nUsers would see incorrect values for the costs of prescriptions.\n \nPlace the KIDS multi-build file into a local directory and use the KIDS \noption Load a Distribution option to load it into the transport global.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option.\n \n3. From the Kernel Installation and Distribution System Menu, select the\nInstallation Menu. From this menu, you may elect to use the following\noptions. When prompted for the INSTALL NAME enter:\n MENTAL HEALTH NCC WARRANTY RELEASE 5.01\n \n \na. Backup a Transport Global - This option will create a backup message\nof any routines exported with this patch.\n \nb. Compare Transport Global to Current System - This option will (allow\nyou to view all changes that will be made when this patch is installed. \nIt compares all components of this patch routines, DDs, templates, etc.).\n \nc. Verify Checksums in Transport Global - This option will allow you to\nensure the integrity of the routines that are in the transport global.\nResolution:\n \n4. From the Installation Menu, select the Install Package(s) option and\nchoose the patch to install (MENTAL HEALTH NCC WARRANTY RELEASE 5.01).\n \n5. Accept the default when prompted 'Want KIDS to Rebuild Menu Trees Upon \nCompletion of Install? NO//'\n \n6. Accept the default when prompted 'Want KIDS to INHIBIT LOGONs during \nthe install? NO//'\n \n-----------\n7. Accept the default when prompted 'Want to DISABLE Scheduled Options, \nMenu Options, and Protocols? NO//'\n \n8. If prompted 'Delay Install (Minutes): (0 - 60): 0// enter 0 (zero).\n \nBackout /Rollback Strategy:\n---------------------------\nBackout will be done only with the concurrence and participation of\ndevelopment team and appropriate VA site/region personnel. The decision to\nbackout the software will be a joint decision between development\nThe PSODRG routine has been updated to fix the problem with incorrect \nteam, VA site and regional personnel, and other appropriate VA \npersonnel. Rollback applies to data only and is not applicable to this \nmulti-build.\n \nPrior to installing the KIDS multi-build, the site/region should have\nsaved a backup of the routines in a PackMan message using the Backup a\nTransport Global [XPD BACKUP] menu option (this is done at time of\ninstall). The message containing the backed-up routines can be loaded with\nthe "Xtract PackMan" function at the Message Action prompt. The PackMan\nfunction "INSTALL/CHECK MESSAGE" is then used to install the backed up\ncomputation for prescription costs.\nroutines onto the VistA System.\n \nValidation of Backout Procedure\n-------------------------------\nThe backout Procedure can be verified by printing the first 2 lines of\nthe PSO* and YS* Routines contained in the MENTAL HEALTH NCC WARRANTY \nRELEASE 5.01 multi-build using the option First Line Routine Print [XU \nFIRST LINE PRINT]. Once the old routines listed in the multi-build patch \nhave been restored, the first two lines of the Routines will no longer \ncontain the designation of patch 574 (for Outpatient Pharmacy PSO* \n \nroutines) and patch 154 (for Mental Health YS* routines) in the patch \nlist section on line 2 of the routines.\nThe PSODRG routine was incorrectly referencing this field for the drug \ncost:\n 50,15 DISPENSE UNITS PER ORDER UNIT 660;5 NUMBER\nwill fix the defects and incidents reported by the sites to the \nIt has been changed to this field:\n 50,16 PRICE PER DISPENSE UNIT 660;6 NUMBER\n \n2. During backdoor pharmacy process of Outpatient 4 Day Override order, a \nfield called LIMITED DURATION appears.\nDefect 981761\n \nProblem:\n--------\nWhen entering a clozapine prescription for an Outpatient 4 Day Override \ndevelopers of the National Clozapine Coordination (NCC) Project. The \norder, a field called LIMITED DURATION is presented. The IOC sites \nstated that this may be misleading to the pharmacy staff and want it \nremoved.\n \nResolution:\n-----------\nThe logic in routine PSOORED5 was modified to remove the LIMITED DURATION \nfield for clozapine prescriptions. Routine PSONEW1 was modified to \ncorrect the sig for the clozapine prescription.\n \nproject is also referred to as the Clozapine Modernization (ClozMod) \n3. Patients who are actively receiving clozapine (e.g. had a prescription \nlast month) are discontinued.\nDefect 1132329\n \nProblem:\n--------\nThe YSCL DAILY TRANSMISSION option checks for clozapine patients who \nshould be discontinued. The code uses a Mail Group and an ^XTMP storage \nlocation that are in the Pharmacy namespace.\n \nProject.\nResolution:\n-----------\nThe PSO574P pre-init routine was created to ensure that the PSOCLOZ Mail \nGroup TYPE is set to "PUBLIC" and ALLOW SELF ENROLLMENT? is set to "NO". \nThis will prevent any issues when email messages are sent to that Mail \nGroup.\n \nNote: There are routines in the YS*5.01*154 patch that also address this \ndefect.\n \n \n4. The Register Clozapine Patient option needs a restriction to only \nallow registered patients.\n Defect 1133724\n \nProblem:\n--------\nThe Register Clozapine Patient [PSOL REGISTER PATIENT] option needs a \nrestriction to only allow patients that have a CLOZAPINE REGISTRATION \nNUMBER in the CLOZAPINE PATIENT LIST file (#603.01). The option updates \nfields in the PHARMACY PATIENT file (#55).\nThe NCR is maintained by the National Clozapine Coordinating Center \n \nResolution:\n-----------\nThe PSOCLUTL routine was modified to only allow patients who have a \nregistration number to be updated in the PHARMACY PATIENT file (#55).\n \n5. Temporary Clozapine Authorization Number not in correct format\n Defect 1132422\n \nProblem:\n\n\nMCCF EDI TAS EPHARMACY BUILD 13\n\n
\nThis patch changes the upper limit of the DAYS TO PULL FROM SUSPENSE Field\ntransmission, then the software will add the number of days from this\nparameter to the print through date and process any other prescriptions it\nfinds in that extended print through date for that patient.\n \nThe DAYS TO PULL SUSPENDED CS CMOP Field (#3.1) controls the bundling of \ncontrolled substances for CMOP transmissions. So, if a patient has at\nleast one prescription that falls within the print through date for the\ncontrolled substances CMOP transmission, then the software will add the\nnumber of days from this parameter to the print through date and process\nany other prescriptions it finds in that extended print through date for\n(#3) and the DAYS TO PULL SUSPENDED CS CMOP Field (#3.1) of the OUTPATIENT\nthat patient.\n \nThe field name DAYS TO PULL SUSPENDED CS CMOP has been changed to DAYS TO \nPULL SUSPENSE CMOP CS.\n \n \n****NOTE****\nThe change to the DAYS TO PULL FROM SUSPENSE Field (#3) and DAYS TO PULL \nSUSPENSE CMOP CS Field (#3.1) of the OUTPATIENT SITE File (#3) may lead to\nNCPDP Reject 79 Refill Too Soon (RTS) claims.\nSITE File (#59) from 10 to 15 days.\n \nIf the claim submission returns a Refill Too Soon (79) reject, the label \nis NOT printed for the prescription and it is moved to the Refill Too \nSoon/DUR section of the patient Medication Profile screen until the user \nresolves the reject. The prescription will also display on the Third-Party\nPayer Reject Worklist. If the claim submission returns a Reject Resolution\nRequired reject, the label is NOT printed for the prescription and it is\nmoved to the Reject Resolution Required section of the Third-Party Payer\nReject - Worklist.\n \n \nPlease search for additional guidance on the eRevenue Resources main \nlanding page for Refill Too Soon. Guidance documents for COVID-19 Refill \nToo Soon Override. The landing page may be accessed at: \nhttps://vaww.vashare.domain.ext/sites/eRevenueResources/Pages/HomePage.asp\nx\nThe DAYS TO PULL FROM SUSPENSE Field (#3) controls the bundling of all \nprescriptions for local dispensing suspense batches and for non-controlled\nsubstances for Consolidated Mail Outpatient Pharmacy (CMOP) transmissions.\nSo, if a patient has at least one prescription that falls within the print\nthrough date for the local batch or non-controlled substances CMOP\n\n
\nThis patch adds data to output for some existing encapsualtion APIs, and \nalso creates a new API to return Non-VA Med information.\n\n
\nThis patch is part of CPRS v31 updates. It includes changes to the Outpatient\n Complete Orders from OERR [PSO LMOE FINISH]\n -------------------------------------------------------------\n When trying to finish an order if the Outpatient Pharmacy user selects a\n dispense drug that has a maximum days supply limit lower than the value\n that was entered in the order by CPRS, the software will inform the user\n that the current value for DAYS SUPPLY is invalid and it will prompt the\n user to enter a new value within the maximum value allowed for the \n dispense drug chosen, as shown in the example below:\n \n Pending OP Orders (ROUTINE) Jan 11, 2017@13:52:45 Page: 1 of 2 \nPharmacy application related to DAYS SUPPLY values over 90 days verification\n TEST,PATIENT <A> \n PID: 666-66-6666 Ht(cm): _______ (______)\n DOB: DEC 02,1900 (116) Wt(kg): _______ (______)\n ------------------------------------------------------------------------\n *(1) Orderable Item: FUROSEMIDE TAB <DIN> \n (2) Drug: No Dispense Drug Selected \n Verb: TAKE \n (3) *Dosage: 40MG \n *Route: BY MOUTH \n *Schedule: DAILY \nwhen a specific dispense drug is not defined in the pending order from CPRS.\n (4) Pat Instruct: \n Provider Comments: \n Instructions: TAKE 1 TABLET BY MOUTH DAILY \n (5) Patient Status: NBC \n (6) Issue Date: JAN 5,2017 (7) Fill Date: JAN 11,2017 \n (8) Days Supply: 180 (9) QTY ( ): 180 \n ------------------------------------------------------------------------\n + Enter ?? for more actions \n Select Item(s): Next Screen// FN Finish \n \nThis patch also contains a new function for CPRS to call before authorizing\n DRUG NAME REQUIRED\n \n Instructions: TAKE 1 TABLET BY MOUTH DAILY\n \n The following Drug(s) are available for selection:\n 1. FUROSEMIDE 40MG TAB\n 2. FUROSEMIDE 20 MG\n 3. FUROSEMIDE 40MG 60'S\n 4. FUROSEMIDE 20MG TABS \n \nthe user to copy an Outpatient Pharmacy order.\n Select Drug by number: (1-4): 1\n \n Invalid DAYS SUPPLY value (180), resetting it to 90 (maximum allowed).\n \n DAYS SUPPLY: (1-90): 90// \n \n2. A new Outpatient Pharmacy API called $$ORCOPY^PSOORCPY was created for\n Computerized Patient Record System (CPRS) to call in order to verify\n whether an Outpatient Pharmacy order can be copied or not. It will check\n to verify the dispense drug is still active and still marked for the\n \n outpatient application. The new API returns the following \n \n "-1^Not a Valid Outpatient Medication Order." - The prescription record\n cannot be found. \n \n "0^<Reason>" - O indicates the order cannot be copied and the <Reason> why\n it cannot be copied (e.g., "0^This Drug has been Inactivated.") \n \n "1" - Order can be copied.\n \nBelow Are some details regarding the two changes in this patch:\n3. A new VistA Integration Control Registration (ICR) #6719 was created to \n allow the Computerized Patient Record System V. 1.0 (CPRS) to call the new\n Outpatient Pharmacy API $$ORCOPY^PSOORCPY (see #2 above) in order to\n prevent the copy of Outpatient Pharmacy order in certain situations, such\n as dispense drug is inactive or the dispense drug is no longer marked for\n outpatient pharmacy use.\n \n1. Patient Prescription Processing [PSO LM BACKDOOR]\n\n
\nThis patch addresses one (1) issue:\n \nStatus mismatches might occur between the ORDERS (#100) file and the \nassociated medication file - PRESCRIPTION (#52) or PHARMACY PATIENT (#55).\n\n
\n1. Clinical Reminders has requested the addition of the last RELEASED\nexpanded version of the SIG as displayed by the Action/Information Profile\nin Outpatient Pharmacy. Many physicians do not know some of the\nabbreviations used by Pharmacy. This patch addresses this issue. \n \n3. A problem has been reported that can occur when a pending Outpatient\norder is transferred from Outpatient Pharmacy to Inpatient Medications in\nComputerized Patient Record System (CPRS). It is possible that an\nincorrect dispense drug is assigned to the order. This patch resolves the\nproblem.\n \nDATE/TIME and the associated DAYS SUPPLY to the ^TMP("PS",$J,D0,0) node\n4. When selecting from the Drug file (#50), the user entered lowercase\nletters and was returned a drug based on the VA Drug Class lookup and was\nnot offered a choice of drugs starting with the letters entered. This\npatch corrects this problem. \nreturned by the OCL^PSOORRL API. This will allow the developers to rewrite\nthe way Clinical Reminders handles drug findings providing a speed-up of\nsomewhere between 5 and 10 times. IA 2400. This patch addresses this issue.\n \n2. E3R #15111 has requested the SIG be expanded on the Health Summary \nComponent RXOP. The RXOP component displays the shorthand version of the SIG\nfor backdoor enter prescriptions. The physicians would like to see the\n\n\nINC7454020 - PRN schedules calculating erroneous default quantity\nINC7698142 - Duplicate HL7 messages sent to OPAI device INC7444486 - Drug\nCosts report is incorrect\n\n
\nRelease of Controlled Substance (CS) after Return to Stock issue.\n\n
\nThis patch will address the following issue: \n(d)INC9792380 - Scriptpro not releasing partial filled rx since PSO*7*531\n INSTALL\n(d)INC9744639 - kb0107373 - GLA PARTIALS NOT RELEASING/SCRIPTPRO\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nHITPS-6704 - INC9398751/INC9586108/INC9663815/INC9768476/INC9792380/INC9744639\n \n \n \nDefect Tracking System Ticket(s) & Overview: \n--------------------------------------------\n1. INC9398751 - Partialed RXs are not releasing automatically from VISTA\n (d)INC9586108 - outpatient partial Rxs not releasing after PSO*7*531\n (d)INC9663815 - VistA: Outpatient Pharmacy: Rx Won't Go to CMOP Because of\n Local Partial?\n (d)INC9768476 - Issue with VistA option PSO LM BACKDOOR ORDERS - Refill is\n released instead of partial then Rx cannot be suspended to\n CMOP\n (d)INC9792380 - Scriptpro not releasing partial filled rx since PSO*7*531\nINC9398751 - Partialed RXs are not releasing automatically from VISTA\n INSTALL\n (d)INC9744639 - kb0107373 - GLA PARTIALS NOT RELEASING/SCRIPTPRO\n \nProblem: \n--------\nVA New Jersey Health Care System reported that after the installation of the\npatch PSO*7*531 partial fills are no longer being automatically released when\nthe dispense message is received from the OPAI (Outpatient Pharmacy Automated\nInterface) dispensing machines. The issue happens because incoming messages\nfrom OPAI don't identify whether a fill was a partial or a regular fill. It\n(d)INC9586108 - outpatient partial Rxs not releasing after PSO*7*531\nwas confirmed that this issue was indeed caused by the patch PSO*7*531. \n \nResolution: \n-----------\nThis patch changes the logic for matching incoming HL7 message from OPAI \ndispensing machines by matching it with the outgoing HL7 message via the\nMESSAGE SERVER ID field (#10) in the PHARMACY EXTERNAL INTERFACE file \n(#52.51) first. This logic should always find a match, however if for some\nreason the matching fails it will resort to matching the Rx# along with the\nfill, which should work as well. \n(d)INC9663815 - VistA: Outpatient Pharmacy: Rx Won't Go to CMOP Because of\n \nTechnical Resolution: \n---------------------\nChanged the routine PSOHLDS at line tag FACK2 to re-write the logic for \nmatching an incoming HL7 OPAI message with a record in the PHARMACY EXTERNAL \nINTERFACE file (#52.51). The old logic was improved and left in place in case\nthe new logic fails for any reason. The change will assure an accurate\nmatching of an incoming HL7 OPAI message to the corresponding record in the\nPHARMACY EXTERNAL INTERFACE file (#52.51).\n Local Partial?\n(d)INC9768476 - Issue with VistA option PSO LM BACKDOOR ORDERS - Refill is\n released instead of partial then Rx cannot be suspended to\n CMOP\n\n
\nUsing ONEVA remote data requires choosing local drug file entry to fill \nprescriptions for traveling vets. Only part of drug name/dose is visible.\n\n
\nCorrect display defect in Reset Copay Status\n\n
\nThis patch will address the following issue: \n \nProblem: \n--------\nThe Veterans Health Care System of the Ozarks reported that at the final step\nwhen verifying a non-verified prescription through the Patient Prescription \nProcessing [PSO LM BACKDOOR ORDERS] option it displays the incorrect\nprescription number, as shown below:\n ...\n Now Processing Enhanced Order Checks! Please wait...\n \n \n Press return to continue: \n \n TEST,PATIENT ID#:999-99-9999 RX#: 9999999 <<<< Wrong #\n SIMVASTATIN 5MG TAB\n \n VERIFY FOR MFR,OUTPATFOUR? (Y/N/Delete/Quit): Y// \n ... \n \nResolution: \n-----------\n1. INC9129002 - At the final step when verifying a non-verified prescription,\nIt was determined that if a pharmacist first tries to verify a prescription\nentered by a pharmacy technician that had a significant order check and \ninstead of verifying the prescription s/he enters "Q" to quit and move on to\na different patient, when s/he tried to verify a prescription for the newly\nselected patient the RX# field displayed the number of the prescription from\nthe previous patient, the one with the significant order check. The problem \nwas addressed by resetting the variable that held the Rx# information every\ntime the user selects to verify a prescription.\n \nTechnical Resolution: \n VistA displays the incorrect prescription number. \n---------------------\nThe problem was happening because the variable INT was being used and it was\nnot properly NEWed or KILLed. So, the variable INT was added to the list of\nvariables being NEWed at the line tag OERR+1 in the PSOVER routine.\n \nDefect Tracking System Ticket(s) & Overview: \n--------------------------------------------\n1. INC9129002 - At the final step when verifying a non-verified prescription,\n VistA displays the incorrect prescription number. \n\n
\nThis patch will resolve the following issue(s)\n \n1) When entering outpatient prescriptions and attempt to edit the issue \ndate, the system will allow you to change the issue date to more than 6\nmonths in the past.\n \n2) When inbound eRx prescriptions are processed duplicate entries in the \nERX EXTERNAL PERSON file [#52.48] can occur. \n\n
\nWhen a user changes the Days Supply for a Clozapine Rx the user is now \nalso prompted to select the appropriate Refills #. See the patch \ndesciption on FORUM for more details.\n\n
\nWhen attempting to print a patient's outpatient medication profile from \nVISTA, only one page prints (the page that includes only the patient \ninformation). Subsequent pages do not print. Additionally, on the second \npage of the Medication Profile [PSO P] report there is an additional Page \n2 header printed in the middle of the page and not at a page break.\n\n
\nThis patch addresses the following issue:\n \n Digits \n DESCRIPTION: Price per dispense unit. \n \n TECHNICAL DESCR: This is the price per dispense unit (per ML/MG\n etc.) that is calculated when entering the\n price per order unit, e.g. Price per order unit\n (bottle) =$0.49, dispense unit is ML & the\n bottle has 1000ML. Price per dispense unit =\n $(0.49/1000) = $0.00049 = $0.0005 (rounded to\n the 4th decimal). \n \n \n \nPre-Installation Instructions:\n=============================\nThis patch may be loaded with users on the system. You may wish to \ninstall it during non-peak hours. Installation will take less than 1 \nminute. \n \n \nInstallation Instructions:\nFiles & Fields Associated:\n=========================\n 1. Choose the PackMan message containing this patch.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This\n option will load the KIDS patch onto your system.\n \n 3. On the 'Kernel Installation & Distribution System' Menu (KIDS),\n select the 'Installation' menu.\n \n 4. From this menu, you may elect to use the following option. When \n \n prompted for the INSTALL NAME select the package 'PSO*7.0*602':\n \n a. Print Transport Global - This option will allow you to print \n only a summary of the patch, to print a summary of the patch and\n the routines in the transport global, or to print only the\n routines in the transport global.\n \n b. Compare Transport Global to Current System - This option will \n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch (routines,\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n DDs, templates, etc.).\n \n 5. From the Installation Menu, select Backup a Transport Global - This \n option will create a backup message of any routines exported with \n this patch. It will not backup any other changes such as DDs or\n templates.\n \n 6. Use the 'Install Package(s)' option under the 'Installation' menu \n and select the package 'PSO*7.0*602'.\n \n------------------ -------------------------- --------------------\n 7. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//', choose 'NO'.\n \n 8. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO//', choose 'NO'.\n \n \nInstallation Verification:\n=========================\nReview the Data Dictionary changes listed above using VA FileMan. \nPRESCRIPTION (#52) UNIT PRICE OF DRUG (#17) Modified\n \nSelect OPTION: 8 DATA DICTIONARY UTILITIES\nSelect DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES\n START WITH What File: PRESCRIPTION// (1863777 entries)\n GO TO What File: PRESCRIPTION// (1863777 entries)\n Select SUB-FILE: \nSelect LISTING FORMAT: STANDARD// \nStart with field: FIRST// 17 UNIT PRICE OF DRUG\nGo to field: 17 UNIT PRICE OF DRUG\n \n \n \nBack-out/Rollback Strategy:\n==========================\nIn the event of a catastrophic failure, the Facility CIO may make the \ndecision to back-out the patch.\n \nThe back-out plan is to edit the Data Dictionaries returning them to\noriginal pre-install state.\n \nTo verify the back-out completed successfully, ensure the INPUT \n \nTRANSFORMS have been edited as follows.\n \nUsing FileMan, go to UTILITY FUNCTIONS, INPUT TRANSFORM (SYNTAX)\n \nSelect OPTION: 6 UTILITY FUNCTIONS\nSelect UTILITY OPTION: 5 INPUT TRANSFORM (SYNTAX)\n \nModify what File: PRESCRIPTION// (1863777 entries)\nSelect FIELD: 17 UNIT PRICE OF DRUG\nUNIT PRICE OF DRUG INPUT TRANSFORM: \nAssociated ticket(s):\nK:+X'=X!(X>999999)!(X<0)!(X?.E1"."5N.N) X\n Replace 999999 With 9999 Replace \n K:+X'=X!(X>9999)!(X<0)!(X?.E1"."5N.N) X\n'HELP'-PROMPT: Type a Number between 0 and 999999, 4 Decimal Digits\n Replace 999999 With 9999 Replace \n Type a Number between 0 and 9999, 4 Decimal Digits\nXECUTABLE 'HELP': \n \n=====================\n \n1. INC9558577 Sites' seeing Not ECME Billable: Cannot find price for Item\n \n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n1. When the UNIT PRICE OF DRUG in the Drug file (#50) is set to a higher\n=========================\nTBD\n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. INC9558577 Sites' seeing Not ECME Billable: Cannot find price for Item\n \n Problem:\nvalue than 9999.00 then when a RX is entered the value is not filed into\n -------\n \n When the UNIT PRICE OF DRUG in the Drug file (#50) is set to a higher\n value than 9999.00 then when a RX is entered the value is not filed\n into the Prescription file and (if ECME is setup) the message 'Cannot\n find price for Item' is also displayed during the RX entry process\n (Patient Prescription Processing). The Input Transform of the UNIT\n PRICE OF DRUG field in file 52 prevents a value from being stored when\n it is greater than 9999.0000. During testing it was also found that \n the field CURRENT UNIT PRICE OF DRUG (#1.2) in the Refill sub record\nthe Prescription file and (if ECME is setup) the message 'Cannot find\n allowed the price of the drug to be filled with a value greater than\n the input transform was defined to allow.\n \n \n Resolution:\n ----------\n The input Transform of the UNIT PRICE OF DRUG in the Prescription file\n (#52) is modified to allow a maximum value of 999999.0000. This \n matches the maximum values in fields PRICE PER ORDER UNIT, PRICE PER\n DISPENSE UNIT, and PRICE PER DISPENSE UNIT in the Drug File (#50)\nprice for Item' is also displayed during the RX entry process (Patient\n The input Transform of the CURRENT UNIT PRICE OF DRUG (#1.2) in the \n Prescription file (#52) is also modified to allow a maximum value of \n 999999.0000. Routine PSOR52 is also modified to not stuff the price of\n the drug into the refill field which avoided the input transform\n specifications. \n \n \n \nTest Sites:\n==========\nPrescription Processing). The Input Transform of the UNIT PRICE OF DRUG\n \n \nData Dictionaries Before:\n========================\n \n52,17 UNIT PRICE OF DRUG 0;17 NUMBER (Required)\n \n INPUT TRANSFORM: K:+X'=X!(X>9999)!(X<0)!(X?.E1"."5N.N) X\n LAST EDITED: FEB 27, 2020 \n HELP-PROMPT: Type a Number between 0 and 9999, 4 Decimal \nfield in file 52 prevents a value from being stored when it is greater\n Digits \n DESCRIPTION: Price per dispense unit. \n \n TECHNICAL DESCR: This is the price per dispense unit (per ML/MG\n etc.) that is calculated when entering the\n price per order unit, e.g. Price per order unit\n (bottle) =$0.49, dispense unit is ML & the\n bottle has 1000ML. Price per dispense unit =\n $(0.49/1000) = $0.00049 = $0.0005 (rounded to\n the 4th decimal). \nthan 9999.0000\n \n \nData Dictionaries After:\n=======================\n \n52,17 UNIT PRICE OF DRUG 0;17 NUMBER (Required)\n \n INPUT TRANSFORM: K:+X'=X!(X>999999)!(X<0)!(X?.E1"."5N.N) X\n LAST EDITED: FEB 27, 2020 \n HELP-PROMPT: Type a Number between 0 and 999999, 4 Decimal \n\n
\n1. When returning a prescription using Return Medication to Stock [PSO\nproblem.\n \n3. The Most Commonly Dispensed Drugs report obtained by using Commonly\nDispensed Drugs [PSO COMMON] option, is skipping printing some sites even\nthough there are valid records. This patch fixes this problem.\n \n4. A problem can occur when a prescription is placed on hold through the\nOutpatient Pharmacy options, and then taken off hold through these same\noptions. The prescription will not display correctly on the orders tab\nin CPRS. The order text is not being updated appropriately. The status\nRETURNED STOCK] option, it was reported that the NEXT POSSIBLE FILL field\nwill show as active, but the word "Hold" will still show on the left side\nof the order text. This patch corrects this problem.\n \n5. Additional data has been added to the routine that returns prescription\nand drug information to the Integrated Billing package, for Tricare\nbilling purposes. This has been done for future enhancements.\n \n6. With the release of PSO*7*40 an interface was added for the Controlled \nSubstances V. 3.0 package (PSD*3*24). This interface sends notification\nto the Controlled Substances V. 3.0 package when a fill, refill or partial\n(#102) of PRESCRIPTION file (#52) was not getting reset to what it was\nis returned to stock. This patch further enhances the interface by\npreventing users who do not hold the PSDMGR key from updating vault\nbalances and returning controlled substances to stock. For this new\nenhancement to be completely functional PSD*3*30 must be installed.\nprior to the refill. This patch fixes this problem.\n \n2. When using Complete Orders from OERR [PSO LMOE FINISH] option,\nfinishing orders entered through Computerized Patient Record System\n(CPRS), it was reported that the number of refills did not always update\nappropriately when Days Supply was edited. This patch corrects this\n\n
\n The Health Integration & Modernization (HI&M) CLOZAPINE NCCC OVRD \n \n used as an initial test to allow the patient to be selected for\n registration; existing code will still prevent the patient from being \n selected due to previous registration, but the correct message will now \n display regarding the patient's registration status.\n \n \n 3. Requirement 2 Defect 1 - Patient with Temp Registration and an NCCC \n Authorization and NCCC Override Date, but day supply limited to 4.\n \n INC9951972: COVID-19 VistA PSO defect - Clozapine National Override \n The multi-build contains the Mental Health patch YS*5.01*166 and the \n patient's prescription limited to 4 days.\n \n Problem:\n --------\n A Patient initially receives a 4-day emergency authorization, and later\n an NCCC Authorization and an NCCC Override Date. While the NCCC Override\n Date is still active, the Day Supply (for Outpatient Pharmacy) or Order\n Duration (for Inpatient Medications) continues to be limited to 4 days.\n Inpatient Medications Order Duration is defined as the number of days\n between the order's Start Date/Time and Stop Date/Time.\n Outpatient Pharmacy patch PSO*7.0*612. The list of defects and their \n \n Resolution:\n -----------\n If a NCCC Authorized National Override Date is in effect following an\n initial local override, the system shall process an active clozapine \n patient's clozapine prescription under national override processes \n allowing the patient to be provided with the approved quantity associated\n with their individual dispensing frequency from the DISPENSE FREQUENCY \n field (#2) in the CLOZAPINE PATIENT LIST file (#603.01). The approved \n quantity is determined by the order's Days Supply for Outpatient Pharmacy\n resolution is below.\n orders, and the Order Duration (days between Start Date/Time and Stop \n Date/Time) for Inpatient Medications orders.\n \n Technical Resolution:\n ---------------------\n A change was made in several routines to look in the PHARMACY PATIENT \n file (#55) for the patient's active clozapine authorization number before\n searching for the value in the patient's DISPENSE FREQUENCY field (#3) of\n the CLOZAPINE PATIENT LIST file (#603.01). This enables the clozapine \n processing logic to any temporary initial local authorization on file \n \n that have been replaced by a permanent NCCC authorization numbers.\n \n - To address backdoor entry of outpatient orders, routine DAYSEN^PSODIR1\n was changed to find the patient's registered clozapine \n authorization number.\n \n - To address backdoor entry of inpatient orders, routine ^PSOCLO1 \n was changed to find the patient's registered clozapine authorization \n number.\n \n This patch is also being released with informational patch PSJ*5*403 that\n - To properly calculate days supply during the finishing of pending \n orders, routine CLOZ^PSOORFI2 was changed to find the patient's \n registered clozapine authorization number.\n \n - To properly calculate days supply during the back door editing of \n active orders, routine ACT^PSOORNE2 was changed to find the patient's \n registered clozapine authorization number.\n \n - To properly calculate default Days Supply in CPRS, change \n DSUP^PSOSIGDS was changed to find the patient's registered clozapine \n documents changes to Inpatient Medications' processing of clozapine\n authorization number. This changed routine is used by the ORWDPS1\n DFLTSPLY Remote Procedure Call (RPC) to calculate default Days Supply.\n \n \n 4. Requirement 2 Defect 2 - Patient with NCCC Authorization receives a \n Special Condition Fill, and later an NCCC Authorization and Override \n Date, but day supply limited to 4.\n \n INC9951972: COVID-19 VistA PSO defect - Clozapine National Override \n patient's prescription limited to 4 days \n overrides that are a result of the defect fixes in PSO*7.0*612 and\n \n Problem:\n --------\n A patient with an initial NCCC Authorization receives a Special Condition\n override, followed by an NCCC override, is limited to a Day Supply\n (Outpatient Pharmacy orders) or an Order Duration (Inpatient Medications\n orders) limited to 4 for clozapine orders. The NCCC national clozapine\n override and the patient's regular clozapine dispense frequency are\n ignored.\n \n YS*5.01*166. \n Resolution:\n -----------\n A patient with an initial NCCC clozapine authorization receiving a\n Special Condition override, followed by an NCCC override, shall be \n processed under national override rules allowing the patient to be \n provided with the approved quantity associated with their individual \n dispensing frequency from the DISPENSE FREQUENCY field (#2) in the \n CLOZAPINE PATIENT LIST file (#603.01). The approved quantity is reflected\n in the order's Days Supply for Outpatient Pharmacy orders, and the Order \n Duration (days between Start Date/Time and Stop Date/Time) for Inpatient \n \n Medications orders.\n \n Technical Resolution:\n ---------------------\n To address backdoor entry of outpatient orders, routine DAYSEN^PSODIR1\n was changed to find the patient's registered clozapine authorization\n number.\n \n To address backdoor entry of inpatient orders, routine ^PSOCLO1 was\n changed to find the patient's registered clozapine authorization \n COVID-19 multi-build is an emergency patch to the National Clozapine \n Defect Tracking System Ticket(s) & Overview: \n number.\n \n \n 5. Requirement 2 Defect 3 - Local Special Condition Override followed\n by valid lab results limits orders to 4-day supply.\n \n Problem:\n --------\n When a patient with an active NCCC clozapine registration and no \n current clozapine lab results receives a Local Special Condition \n --------------------------------------------\n override, followed by the entry of valid clozapine lab results, \n subsequent pharmacy orders continue to be limited to a 4-day supply.\n \n Resolution:\n -----------\n When a patient with an active NCCC clozapine registration and no \n current clozapine lab results receives a Local Special Condition \n override, followed by the entry of valid clozapine lab results, \n the Local Special Condition override is no longer in effect and should\n be ignored for new orders. New pharmacy orders should be processed \n \n using the days supply associated with their individual dispense\n frequency. The patient's dispense frequency is reflected in the order's \n Days Supply for Outpatient Pharmacy orders, and the Order Duration \n (days between Start Date/Time and Stop Date/Time) for Inpatient \n Medications orders.\n \n Technical Resolution:\n ---------------------\n Routine ^PSOCLO1 was modified to KILL the ^XTMP globals associated\n with the patient's local override when an active NCCC clozapine \n Patch PSO*7.0*612 contains the following changes: \n registration and valid clozapine lab results exist. This prevents the \n obsolete Local Special Condition override from interfering with the \n patient's regular clozapine dispense frequency.\n \n \n 6. Requirement 2 Defect 4 - Emergency Temp Override followed by new\n NCCC authorization limits orders to 4-day supply.\n \n Problem:\n --------\n \n When a patient with a discontinued clozapine registration and current\n valid lab results receives a Local Emergency Temp Override, followed\n by a new NCCC clozapine authorization number and registration, \n subsequent pharmacy orders continue to be limited to a 4-day supply.\n \n Resolution:\n -----------\n When a patient with a discontinued clozapine registration and current\n valid lab results receives a Local Emergency Temp Override, followed\n by a new NCCC clozapine authorization number and registration, the Local\n 1. Requirement 1 Enhancement - Automate the Pharmacy Registration of NCCC\n Emergency Temp override is no longer in effect and should\n be ignored for new orders. New pharmacy orders should be processed \n using the days supply associated with the patient's dispense frequency.\n The patient's dispense frequency is reflected in the order's Days \n Supply for Outpatient Pharmacy orders, and the Order Duration (days \n between Start Date/Time and Stop Date/Time) for Inpatient Medications \n orders.\n \n Technical Resolution:\n ---------------------\n Clozapine Authorizations.\n Modify routines PSOCLUTL and PSOCLADD to KILL the ^XTMP globals\n associated with the patient's local override at the time an NCCC\n clozapine authorization number is registered to the patient. This\n prevents an obsolete local override from interfering with order entry\n routines' calculation of the days supply based on the patient's regular \n clozapine dispense frequency.\n \n \n Patch Components\n ================\n \n Files & Fields Associated:\n \n File Name (Number) Field Name (Number) New/Modified/Deleted \n ------------------ ---------------------- -------------------- \n N/A (See YS*5.01*166 Patch Description related for Files/Fields)\n \n Forms Associated:\n Form Name File # New/Modified/Deleted\n --------- ------ --------------------\n N/A\n Problem:\n \n Mail Groups Associated:\n Mail Group Name New/Modified/Deleted\n --------------- --------------------\n N/A\n \n Options Associated:\n Option Name Type New/Modified/Deleted\n ----------- ---- --------------------\n N/A\n --------\n \n Protocols Associated:\n Protocol Name New/Modified/Deleted\n ------------- --------------------\n N/A\n \n Security Keys Associated:\n Security Key Name New/Modified/Deleted\n ---------------------- --------------------\n N/A\n Registry (NCR) software to correct defects to Clozapine National \n Currently, national clozapine authorization numbers are sent by the \n \n Templates Associated:\n Template Name Type File Name (Number) New/Modified/Deleted\n ------------- ---- ------------------ --------------------\n N/A\n \n * * * * * * * * * * *\n \n Test Sites: \n ----------\n National Clozapine Coordinating Center (NCCC) and filed into the \n New Jersey Health Care System (561)\n VA Connecticut Health Care System (689)\n Boise VA Medication Center (531)\n \n \n Software and Documentation Retrieval Instructions:\n --------------------------------------------------\n The software for this patch is being released as a host file.\n \n The host file is available at the following location: \n CLOZAPINE PATIENT LIST file (#603.01). Later, a pharmacy user must\n /srv/vista/patches/SOFTWARE/PSO_YS_CLOZ_COVID.KID \n \n Documentation describing the new functionality is included in this\n release. Documentation can be found on the VA Software Documentation \n Library at: https://www.domain.ext/vdl/\n \n -------------------------------------------------------------------------\n Title File Name \n -------------------------------------------------------------------------\n Technical Manual/Security Guide pso_7_p612_tm.docx\n manually execute Vista option Register Clozapine Patient [PSOL REGISTER\n - Outpatient Pharmacy V.7.0 pso_7_p612_tm.pdf\n \n User Manual - Manager - Outpatient pso_7_man_um.docx\n Pharmacy V.7.0 pso_7_man_um.pdf\n \n Deployment Installation Back-Out pso_7_p612_ys_501_p166_dibr.docx\n and Rollback Guide - HI&M pso_7_p612_ys_501_p166_dibr.pdf\n Clozapine Overrides \n \n Release Notes - HI&M Clozapine pso_7_p612_ys_501_p166_rn.docx\n PATIENT] (for new patients), or Edit Data for a Patient in the Clozapine\n Overrides pso_7_p612_ys_501_p166_rn.pdf\n \n \n Patch Installation: \n \n Pre/Post Installation Overview: \n -------------------------------\n There are no tasks to be performed before the installation of this \n multi-build. Note that the routines should be backed up to a PackMan\n message before installing the build.\n Program PSOL [EDIT] (for previously registered patients). \n \n Pre-Installation Instructions: \n ------------------------------\n This patch may be installed with users on the system although it is \n recommended that it be installed during non-peak hours to minimize\n potential disruption to users. This patch should take less than 5 \n minutes to install. It should not be installed when the YSCL DAILY\n TRANSMISION option is running. If unsure when that is check the OPTION\n SCHEDULING file (#19.2) using FileMan:\n \n \n Select VA FileMan Option: Inquire to File Entries \n \n Output from what File: OPTION SCHEDULING// (17 entries) Select OPTION\n SCHEDULING NAME: YSCL DAILY TRANSMISSION Another one: Standard Captioned\n Output? Yes// (Yes) Include COMPUTED fields: (N/Y/R/B): NO// - No \n record\n number (IEN), no Computed Fields \n \n NAME: YSCL DAILY TRANSMISSION \n QUEUED TO RUN AT WHAT TIME: OCT 05, 2019@01:30 \n Resolution:\n RESCHEDULING FREQUENCY: 1D TASK ID: 2577736 \n \n Installation Instructions: \n --------------------------\n1. Place the KIDS multi-build file PSO_YS_CLOZ_COVID.KID into a \nlocal directory and use the KIDS option Load a Distribution option to \nload it into the transport global.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n ---------- \n3. From the Kernel Installation and Distribution System Menu, select \nthe Installation Menu. From this menu, you may elect to use the \nfollowing options. When prompted for the INSTALL NAME enter:\n PSO*7.0*612\n \n a. Backup a Transport Global - This option will create a backup message\n of any routines exported with this patch.\n \n b. Compare Transport Global to Current System - This option will (allow \n you to view all changes that will be made when this patch \n Automate the clozapine registration process by automatically updating the\n is installed. It compares all components of this patch \n (routines, DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - This option allows you to \n ensure the integrity of the routines that are in the transport \n global.\n \n 4. From the Installation Menu, select the Install Package(s) option and \n choose the patch to install (PSO*7*612).\n \n Clozapine Coordinating Center (NCCC) Override functionality.\n patient's clozapine registration number and status when a new National \n 5. Accept the default when prompted 'Want KIDS to Rebuild Menu Trees \n Upon Completion of Install? NO//'\n \n 6. Accept the default when prompted 'Want KIDS to INHIBIT LOGONs during \n the install? NO//'\n \n 7. Accept the default when prompted 'Want to DISABLE Scheduled Options, \n Menu Options, and Protocols? NO//'\n \n 8. If prompted 'Delay Install (Minutes): (0 - 60): 0// enter 0 (zero). \n Clozapine number is received from the NCCC.\n \n Backout /Rollback Strategy: \n ---------------------------\n Backout will be done only with the concurrence and participation of \n development team and appropriate VA site/region personnel. The decision \n to backout the software will be a joint decision between development\n team, VA site and regional personnel, and other appropriate VA personnel.\n Rollback applies to data only and is not applicable to this multi-build.\n \n Prior to installing the KIDS multi-build, the site/region should have \n \n saved a backup of the routines in a PackMan message using the Backup a\n Transport Global [XPD BACKUP] menu option (this is done at time of\n install). The message containing the backed-up routines can be loaded \n with the "Xtract PackMan" function at the Message Action prompt. The\n PackMan function "INSTALL/CHECK MESSAGE" is then used to install the\n backed up routines onto the VistA System.\n \n The new "AC" mumps cross reference for the CLOZAPINE PATIENT LIST file \n (#603.01) must be manually deleted via FileMan prior to restoring the \n backed up routines. \n Technical Resolution:\n \n The steps to delete the cross reference:\n 1. Access VA FileMan option Cross-Reference A Field via the VA FileMan \n Utility Functions [DIUTILITY] menu.\n 2. At the prompt, "What type of cross-reference (Traditional or New)?" \n enter NEW.\n 3. At the prompt, "Modify What File:" enter 603.01.\n 4. The new "AC" cross reference should be selected by default.\n 5. At the prompt "Choose E (Edit)/D (Delete)/C (Create):" enter DELETE.\n 6. At the prompt "Are you sure you want to delete the index \n ---------------------\n definition? NO// YES"\n \n Example deletion of new "AC" index if backout is required:\n \n VA FileMan 22.2 \n \n Select OPTION: UTILITY FUNCTIONS \n Select UTILITY OPTION: CROSS-REFERENCE A FIELD OR FILE \n What type of cross-reference (Traditional or New)? Traditional// NEW\n Modify what File: REMOTE PROCEDURE// 603.01 CLOZAPINE PATIENT LIST\n New Pharmacy API PSOCLADD has been created that accepts Patient DFN and \n (74 entries)\n Current Indexes on file #603.01:\n 1589 'AC' index\n Choose E (Edit)/D (Delete)/C (Create): DELETE \n \n Which Index do you wish to delete? 1589// AC\n Are you sure you want to delete the index definition? NO// YES \n \n Index definition deleted.\n \n NCCC Clozapine Authorization number as input and files the number into \n \n \n \n Validation of Backout Procedure \n -------------------------------\n The backout Procedure can be verified by printing the first 2 lines of \n the PSO* and YS* routines contained in the HI&M CLOZAPINE NCCC OVRD \n COVID-19 multi- build using the option First Line Routine Print [XU FIRST\n LINE PRINT]. Once the old routines listed in the multi-build patch have\n been restored, the first two lines of the Routines will no longer contain\n the CLOZAPINE REGISTRATION NUMBER field (#53) in the PHARAMCY PATIENT \n the designation of patch 612 in the patch list section on line 2 of the\n routines.\n \n The backout of the new "AC" cross reference on the CLOZAPINE PATIENT \n LIST file (#603.01) can be verified by repeating the backout steps and \n verifying that there is no longer a selectable "AC" cross reference to \n delete.\n file (#55), and updates the CLOZAPINE STATUS field (#54) to 'A' for \n Active. This API is executed when a new clozapine authorization is filed \n \n into the CLOZAPINE PATIENT LIST (#603.01) file via a mumps action cross \n reference.\n \n \n 2. Requirement 1 Defect 1 - Incorrect Messages Displayed in Clozapine \n Vista Options\n \n Problem:\n --------\n When more than one clozapine authorization number exists for a patient,\n The NCR is maintained by the NCCC. The NCCC is responsible for VA's \n the "Register Clozapine Patient" option currently displays the incorrect\n message, "Patient,Name has not been authorized for Clozapine by the NCCC\n (National Clozapine Coordinating Center). This option is only available\n for known NCCC-registered patients." when more than one entry in file\n 603.01 for the patient. This message displays regardless of patient's\n Clozapine Status in file 55. \n \n When more than one clozapine authorization number exists for a patient,\n the "Edit Data for a Patient in the Clozapine Program" option currently\n displays the incorrect message, "Patient,Name has not been authorized for\n compliance with the clozapine Risk Evaluation and Mitigation Strategy \n Clozapine by the NCCC in Dallas. Contact the NCCC in Dallas for\n authorization." The patient cannot be selected.\n \n Resolution:\n ----------- \n The code associated with the 'Register a Clozapine Patient' option and\n the "Edit Data for a Patient in the Clozapine Program" shall be modified\n to display correct information about the patient's Clozapine registration\n status regardless of the number of clozapine numbers on file for the\n patient.\n (REMS), which is mandated by the Food and Drug Administration (FDA) for \n \n The "Register Clozapine Patient" option shall display "Patient,Name is\n already registered with number CL99999. Use the edit option to change\n registration data, or contact your supervisor" when more than one entry \n in file 603.01 for the patient. No other change in functionality to this \n option.\n \n The "Edit Data for a Patient in the Clozapine Program" option shall \n not display the incorrect message "Patient,Name has not been authorized \n for Clozapine by the NCCC in Dallas. Contact the NCCC in Dallas for \n tracking clozapine patients.\n authorization". The option will allow the selection of a patient with \n more than one entry in file 603.01. No other change in functionality to \n this option.\n \n Technical Resolution:\n ---------------------\n Correct routine PSOCLUTL's lookups by patient into the CLOZAPINE PATIENT\n LIST file (#603.01) from $$FIND1^DIC, which fails when there is more than\n one clozapine authorization number on file for a patient, to D FIND^DIC,\n which finds all clozapine authorization numbers. The defective lookup is\n\n
\nThis patch will address the following ePrescribing (eRx) issues: \n \nProblem: \n-------\nVA Black Hills Health Care System reported a stack error causing VistA to\nterminate the user's session when they used the Class III VistA option\nInpatient Pending Orders Display [PSOZ INPATIENT PENDING ORDERS]. Although\nthe HPS (Health Portfolio Software) Sustainment Team does not support Class\nIII software, it was determined that the root cause of the problem was the\nfact that the LOGIN DATE field (#15) in the PENDING OUTPATIENT ORDERS file\n(#52.41) was being populated with only the date (YYYMMDD) and not the time\n \n(YYYMMDD.HHMMSS) by the new eRx functionality. Although the field allows\nfor date only content, every other function that creates a new entry in\nthe PENDING OUTPATIENT ORDERS file (#52.41) also sets the timestamp along\nwith the date.\n \nResolution: \n----------\nThis patch will modify the setting of the LOGIN DATE field (#15) in the\nPENDING OUTPATIENT ORDERS file (#52.41) for eRx pending orders to include\nthe date and timestamp (YYYMMDD.HHMMSS) of when the order was created.\nINC8108373 - Inbound eRx - Outpatient pharmacy bingo board causing stack error\nThis will prevent the error users are getting when running the Class III\noption mentioned above.\n \nNote: This fix will apply to future orders only, filed after the patch is\n installed.\n \nTechnical Resolution: \n--------------------\nThe setting of the array PSOHY("EDT") at SETUP+72^PSOERX1B and \nPSOHY+34^PSOERXU3 was changed from PSOHY("EDT")=DT (DT holds the current\nINC10596781 - e-prescription missing SIG or patient instruction\ndate in the YYYMMDD format) to PSOHY("EDT)=$$NOW^XLFDT() (the $$NOW^XLFDT()\nfunction returns the current date and time in the YYYMMDD.HHMMSS format).\n \n2. INC10596781 - e-prescription missing SIG or patient instruction\n \nProblem: \n-------\nThe VA Health Administration Center Denver reported that when viewing a \nRefillResponse type record in the Complete Orders from eRx [PSO ERX FINISH]\noption the field 'Vista Sig' under the MEDICATION DISPENSED section was being\n \nsuppressed as indicated in the screen capture example below:\n \n ****************************MEDICATION DISPENSED************************* \n Vista Drug: CHLORAMBUCIL 2MG TAB \n Vista Qty: 30 Vista Refills: 3 Vista Days Supply: 30 \n >>> 'Vista Sig' field should be displayed here.\n VA Rx#: Unable to resolve. \n \n \nResolution: \nDefect Tracking System Ticket(s) & Overview: \n----------\nIt was confirmed that the software was hiding the 'Vista Sig' field because\nof an error in the code. The defect is being addressed by this patch and it\ndisplay the 'Vista Sig' correctly, as shown in the example below:\n \n ****************************MEDICATION DISPENSED************************* \n Vista Drug: CHLORAMBUCIL 2MG TAB \n Vista Qty: 30 Vista Refills: 3 Vista Days Supply: 30 \n Vista Sig: TAKE ONE-HALF TABLE BY MOUTH TWICE A DAY FOR 30 DAYS ON A FULL \n STOMACH \n===========================================\n VA Rx#: Unable to resolve. \n \n \nTechnical Resolution: \n--------------------\nThe array variable DIRARY was misspelled at line MEDDIS+37^PSOERXU3 and at\nline MEDDIS+39^PSOERXU3 it was using the variable DIRECT instead of the \nDIRARY array. Both issues were resolved.\n \n \n1. INC8108373 - Inbound eRx - Outpatient pharmacy bingo board causing stack\n error\n\n\nWhen a user changes the DAYS SUPPLY for only a Clozapine flagged drug with\nat least one registered lab test, the user will also be prompted to select\nthe appropriate # OF REILLS. See the patch desciption on FORUM for more\ndetails.\n\n
\n1. EPharmacy prescriptions that are pulled from suspense using the action\nVariable RX0 is set during the speed refill and is not killed if the Rx\nis suspended when the speed refill process is done nor is it killed \nwhen starting a New Order.\nPP in the PSO LM BACKDOOR ORDERS option remain suspended after a\nsubsequent refill action of another prescription. \n \n2. During processing of Outpatient Pharmacy order, user was kicked out\nof VistA session with an undefined error DSPL+3^PSOORNE3 *PSLSTL.\nAfter doing a speed refill for a prescription that results in it \nbeing suspended, the error occurs when entering a new order for a supply\nitem and answering No to the final prompt 'Is this correct?'\n\n
\nThis patch will address the following issues: \n--------------------------------------------\n1. INC11549905 - when you enter a new prescription the QTY rounds up unless\n you change the days supply.\n \nProblem: \n--------\nThe Oscar G. Johnson VA Medical Center reported that when editing the Days \nSupply fields for a Clozapine prescription that the QTY field value is not\nrounding up, instead it remains a factional value, forcing the user to fix\nit mannually.\n \n \nResolution: \n-----------\nThe issue was confimed and the calculation of the QTY value was fixed to\nround any fractional value up. So, if the automatic calculation results in\na value such 4.2, for example, it will be rounded up to 5. \n \nTechnical Resolution: \n---------------------\nChanged the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of\n1. INC11549905 - when you enter a new prescription the QTY rounds up unless\nthe variable QTY up.\n \n S:QTY PSORXARY("QTY")=(QTY+.99)\\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\\1\n \n2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill -\n Expiration date calculation \n \nProblem: \n--------\nAfter the installation of patch PSO*7*574 the expiration date calculation for\n you change the days supply.\nclozapine prescriptions is wrong for some scenarios after editing the # of\nRefills or Days Supply fields. For example, when you edited a prescription\nwith 28-day supply and 0 refills, with an expiration date of 28 past the issue\ndate, to 14-day supply and 1 refill it was setting the expiration to 14 days\npast the issue date, instead of keeping the 28 days.\n \nResolution: \n-----------\nThe calculation of the expiration date for clozapine prescriptions was resolved\nto correctly calculate the total number of days supply of the entire \n2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill -\nprescription, including the refills.\n \nTechnical Resolution: \n---------------------\nRemoved a line of code in the PSOEXDT routine (shown below) introduced by\nPSO*7*574 that was preventing the expiration date from being calculated\ncorrectly for clozapine prescriptions.\n \n ; Added Clozapine check to not modify Expires date ; PSO*574\n A Q:+$G(PSORXED("CLOZ EDIT")) \n Expiration date calculation \n \n3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program\n \nProblem: \n--------\nAfter the installation of patch PSO*7*574 the option Edit Data for A Patient in\nthe Clozapine Program [PSOL EDIT] started resetting the REGISTRATION DATE field\n(#58) in the PHARMACY PATIENT file (#55) even after the user simply returns\nthrough the 3 fields in the option without modifying any of them. The\nREGISTRATION DATE field should only be reset when the user changes the value of\n3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program\nthe CLOZAPINE REGISTRATION NUMBER.\n \n Edit Data for a Patient in the Clozapine Program [PSOL EDIT]\n \n Edit Data for a Patient in the Clozapine Program\n Select clozapine patient : CLOZPAT,TEST\n CLOZAPINE REGISTRATION NUMBER: MR12345// MR12345\n CLOZAPINE STATUS: ACTIVE TREATMENT\n RESPONSIBLE PROVIDER: TEST,PROVIDER// TEST,PROVIDER\n \n \nResolution: \n-----------\nThe Clozapine REGISTRATION DATE will only be reset when the value of the \nCLOZAPINE REGISTRATION NUMBER is modified.The issue was confimed and the calculation of the QTY value was fixed to\nround any fractional value up. So, if the automatic calculation results in\na value such 4.2, for example, it will be rounded up to 5. \n \nTechnical Resolution: \n---------------------\nChanged the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of\nDefect Tracking System Ticket(s) & Overview: \nthe variable QTY up.\n \n S:QTY PSORXARY("QTY")=(QTY+.99)\\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\\1\n\n\nThis patch addresses the following issues:\n \nAssociated ticket(s):\n=====================\n \n1. INC11453884 - Reset Copay Status List Manager Start with Fill Date \n should be a required response \n \n2. INC11646025 - Issues with the Reset Copay Status List Manager Display \n Option\n \n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nBay Pines VAMC\nWashington DC VAMC\n \n \n1. Reset Copay Status List Manager Start with Fill Date should be \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. INC11453884 - Reset Copay Status List Manager Start with Fill Date \n should be a required response\n \n Problem:\n -------\n Running option RESET COPAY STATUS LIST MANAGER [PSOCP RESET COPAY \n STATUS LM] will encounter a subscript error if no date is entered at\na required response.\n the Start with Fill Dates: prompt\n \n Resolution:\n ----------\n Modify PSOCPF to exit from the option when no date is entered for the \n Start with Fill Dates: prompt. \n \n2. INC11646025 - Issues with the Reset Copay Status List Manager Display \n Option\n \n \n Problem:\n -------\n Up carat out should gracefully exit. Report doesn't allow an up\n carat at several prompts\n \n Resolution:\n ---------------\n Modify PSOCPF to exit from the option when up carat ^ is entered on\n the Start with Fill Dates, Go to Fill Dates, and the Select(A)ll or\n (S)elected Prescription(s) prompts. It was also found during testing \n2. Up carat (^) out should gracefully exit. Report doesn't allow \n that the Change Patient (CP) function within the List Manager screen \n had the same issues with ^ not working as it should and that is being \n addressed with updates to routine PSOCPF2. The patinet name was also \n added to the List Manager screen when NO DATA FOUND FOR ENTERED \n CRITERIA is displayed. \nan up carat at several prompts\n \n \n\n
\nThis patch addresses the following issues in setting the "status" field \nof the ORC segment which is sent to Optifill or ScriptPro:\n \n1. The "Print from Suspense File" option sends a status of "NEW" instead \n of "REFILL" for refills.\n \n2. The "Reprint Batches from Suspense" option sends a status of "NEW" \n instead of "REPRINT" when reprinting original (i.e. not refills) \n prescriptions.\n\n
\n \nDisconnect between order file discontinue action and \nprescription file (prescription was filled multiple times after \ndiscontinuation\n\n
\nWhen editing the drug of a prescription using the Patient Prescription\norderable item with active/suspended status.\nThese occurrences are very rare and it could lead to the following:\n1. As reported in NOIS MAN-1200-11563, the patient profile could change\nto that of another patient and result in dispensing drugs to the wrong\npatient (action 1 above).\n2. As reported in NOIS MAN-0101-10680, it could end up patients having\nduplicate drugs in their medical profile (action 2 above).\nThis patch ensures that the TMP("PSORXDC",$J) global is killed\naccordingly.\nProcessing [PSO LM BACKDOOR ORDERS] option, the TMP("PSORXDC",$J) global\ncreated to store the duplicate prescription(s) that was requested to be\ndiscontinued does not get deleted if either of the following action was\ntaken:\n1. If the edit was terminated by up-arrowing at the point of accepting\na new prescription.\n2. If the dispensed drug is changed to a drug which already exists in\nthe medical profile (in another prescription) that is tied to the same\n\n\nOPAI NOT UTILIZING MAIL PREF 4-LOCAL CERTIFIED MAIL\nPrescription Dispense HL7 records for the OPAI (Out Patient \nAutomated Interface) \n \n \nThis patch will resolve the following issue:\n \nWhen using Menu Option PSO LM BACKDOOR ORDERS \nand the user selects PU (Patient Update), if the user selects \noption #4 LOCAL CERTIFIED MAIL for at the MAIL: prompt\nthe selection will not be reflected in the RXD segment of the \n\n
\nIt was reported that the Return to Stock indicator not cleared after \noriginal fill of a CS rx if returned to stock and later filled and \nreleased.\n\n
\nRx entries always had a T-6M limit. Copy+Edit had a loophole that allowed\nany date into the past which created an error when a 19th century date was\nentered. The fix was done to match the new Rx-entry T-6M limit. However, \nby removing the loophole of the previous code the sites that developed a\nconversion workflow based on Copy+Edit and backdating non-CS Rx's between\n6 and 12 months lost that capability.\n\n
\nSee FORUM for patch description.\n\n
\nFile #52 Label multiple created with a missing header node\n\n
\nBackup of PSO*7.0*625 on Apr 05, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7.0*625.\n\n
\nBackup of PSO*7.0*635 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nInbound eRx version 4.0 defect remediation.\n\n
\nBackup of BPS PSO IB BUNDLE 16.0, BPS*1.0*28, PSO*7.0*560, IB*2\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis KIDS build fixes a problem when pending orders are received from CPRS. \nprofile screen, hit return at the action prompt an undefined error occurred.\nNOIS: HUN-0398-20933\n \nRoutines: PSOORFI1, PSOORFI2, PSOORFIN, PSOPOST3, PSOPTPST, PSORN52C, PSORX1 \nPSOHLNE2, PSOHLNEW, PSOHLSN\nThey are not finished in a first in first out order. Added "AD" cross \nreference to Login Date field (#15) from the Pending Outpatient Orders file \n(#52.41). Added an 'AE' xref to the Related Institution field.\n NOIS: WAS-0298-21178 \n \nError generated when pharmacist was finishing outpatient med orders for an\ninpatient. From the medication profile screen, she typed IP to view the\ninpatient profile and after the review, she went back to the medication\n\n
\nProblem: The CMOP Controlled Substance Rx Dispense Report generates an\nundefined error when it is trying to report on a prescription refill that\nwas filled locally and not sent to CMOP.\n \nResolution:\n \nThe CMOP coding has been changed to handle the case when a refill was\nfilled locally and not by CMOP.\n\n
\nBackup of PSO*7.0*631 on Jun 04, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will address the following issues: \n INC15788649 - RxRenewal Response - Replace status get assigned wrong \nto be marked with the RRX (RXRENEWAL REQUEST EXPIRED) status after 14 days\nwithout a response.\n ...\n Select one of the following:\n \n PT PATIENT(Grouped)\n RX PRESCRIPTION RECEIVED DATE\n E EXIT\n \n Select By: (PT/RX): PT// RX PRESCRIPTION RECEIVED DATE\n status code\n ...\n \nTechnical Resolution: \n--------------------\nThe functionality responsible for the auto expiration of CRN and RRN records\nin the PSOERX routine lines BLDITEM+11 thru BLDITEM+14 for the RX view were\ncopied over to the PSOERXC1 routine which is used by the PT view. This way\nno matter which way the user enters the option it will always check and mark\neligible CRN and RRN records as expired.\n \n \n \nTest Sites: \n-----------\nTBD\n \nDocumentation Retrieval Instructions:\n-------------------------------------\nN/A (No documentation changes)\n \nInstallation Instructions: \n2. INC12814745 - Rx Sig Not Upper-cased when processing inbound eRX\n--------------------------\nThis patch may be installed with users on the system although it is recommended\nthat it be installed during non-peak hours to minimize potential disruption to\nusers. Staff should not be processing prescriptions while patch is being\ninstalled. This patch should take less than 5 minutes to install. \n \n 1. Choose the PackMan message containing this patch. \n \n 2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n \n 3. From the Kernel Installation & Distribution System menu, select \n the Installation menu. From this menu, select Backup a Transport \n Global. This option will create a backup message of any routines\n exported with this patch. It will not backup any other changes such\n as DD's or templates. When prompted for INSTALL NAME, enter the\n patch #, PSO*7.0*631.\n \n 4. From the Kernel Installation & Distribution System menu, select \n the Installation menu. From this menu, you may select to use the \n following options: \n3. INC16106925 - Pharmacy messages not assigned appropriate status by\n when prompted for INSTALL NAME, enter the patch #, PSO*7.0*631: \n a. Compare Transport Global to Current System - This option will \n allow you to view all changes that will be made when this patch \n is installed. It compares all components of this patch \n routines, DDs, templates, etc. \n \n b. Verify Checksums in Transport Global - This option will allow \n you to ensure the integrity of the routines that are in the \n transport global. \n \n software\n 5. From the Installation menu, select the Install Package(s) option and\n choose the patch to install. \n \n 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO//', respond NO. \n \n 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? NO//', respond NO. \n \n 8. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0. \n \n \n \nBack-out/Rollback Strategy:\n---------------------------\nBack-out will be done only with the concurrence and participation of\ndevelopment team and appropriate VA site/region personnel. The decision to\nback-out or rollback software will be a joint decision between development\nteam, VA site/region personnel and other appropriate VA personnel. \n \nPrior to installing an updated KIDS package, the site/region should have saved\nDefect Tracking System Ticket(s) & Overview: \na backup of the routines in a mail message using the Backup a Transport Global\n[XPD BACKUP] menu option (this is done at time of install). The message\ncontaining the backed up routines can be loaded with the "Xtract PackMan"\nfunction at the Message Action prompt. The Packman function "INSTALL/CHECK\nMESSAGE" is then used to install the backed up routines onto the VistA System. \n \nThe back-out plan is to restore the routines from the backup created.\n \nNo data was modified by this patch installation and, therefore, no \nrollback strategy is required.\n--------------------------------------------\n \n \nValidation of Roll Back Procedure \n---------------------------------\nThe Roll Back Procedure can be verified by printing the first 2 lines of the\nPSO Routines contained in this patch using the option First Line Routine Print\n[XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*631 patch\nhave been rolled back, the first two lines of the Routines will no longer\ncontain the designation of patch PSO*7.0*631 in the patch list section on line\n2.\n \n1. INC13163644 - Assist with deleting eRx order on inbound eRx queue\n \nProblem: \n--------\nThe Fresno VA Medical Center reported that 'Denied' incoming eRx response\nrecords were sitting in their eRx Holding Queue (Complete Orders from eRx\n[PSO ERX FINISH] option) for months because they do not have any way to\nremove them. This issue usually happens when the sites manually renews a\nprescription after placing an eRx refill/renewal request for the eRx\nprescription. Once the incoming response is received the software is unable\n1. INC13163644 - Assist with deleting eRx order on inbound eRx queue\nto process the renewal because the eRx is already renewed and files the\nrecord with an RXN (RXRENEWAL RESPONSE - NEW) status instead of assigning it\na more appropriate status such as RXF RXN (RXRENEWAL RESPONSE - FAILED), \nwhich is removed from the eRx Holding Queue once the user acknowledges it.\n \nResolution: \n-----------\nThe eRx incoming response processing code was changed to automatically assign\na status of RXF to an incoming renewal eRx response if the prescription has\nalready been manually renewed. This will allow users to successfully remove\n Duplicates:\nsuch records from their by using the hidden action ACK (Acknowledge).\n \nTechnical Resolution: \n---------------------\nThe line of code below was inserted at REFRESP+24 in the PSOERXA5 routine. \n \n .D UPDSTAT^PSOERXU1(ERXIEN,"RXF","eRx already Renewed.")\n \nIt will ensure that when an Denied incoming eRx response is received for an\nalready renewed prescription the status will be set to RXF instead of RXN. \n -----------\nFurthermore, another potential code for leaving records in the RXN was \nidentified in the use of the API $$FIND1^DIC because it did not require an\nexact match of the related eRx when the incoming eRx response arrived. The\nthird parameter was changed to include "O", which will force an exact match\nin order to identify the related eRx record.\n \n2. INC12814745 - Rx Sig Not Upper-cased when processing inbound eRX\n \nProblem: \n--------\n INC15788594 - RxRenewal Response was assigned wrong status flag\nThe Tucson VA Medical Center reported that when using the eRx Holding Queue\n(Complete Orders from eRx [PSO ERX FINISH] option) the user added a patient\ninstruction (code) with a lower case text to the eRx and the medication\ninstruction expanded as expected however it did not convert to upper case in\nthe Inbound ERX Holding queue. The text was appended to the SIG and remained in\nlower case through the finishing process in the Patient Prescription Processing\n[PSO LM BACKDOOR ORDERS] option. \n \nResolution: \n-----------\n INC15794278 - RxRenewal Response - Processing Error (RXE) message is not \nIt was confirmed that the eRx Holding Queue was not converting the medication\ninstruction text to upper case when it was retrieved from the MEDICATION \nINSTRUCTION file (#51). This patch addresses this problem by always converting\nthe medication instruction text to upper case.\n \nTechnical Resolution: \n---------------------\nThe line tag LSIG in the routines PSOERXU6 and PSOQUTIL was modified to always\nconvert the medication instruction text to upper case before returning it to\nthe calling routine. \n INC15788861 - RxRenewal Response - Approved failed to generate renewed\n \n3. INC16106925 - Pharmacy messages not assigned appropriate status by software\n patch PSO*7*581\n \nProblem: \n-------\nThe VA Health Administration Center Denver reported that the CRN (RXCHANGE\nREQUEST - NEW) status of some old (older than 14 days) RxChange request\nrecords without a response were not being assigned the appropriate status CRX\n(RXCHANGE REQUEST EXPIRED) as described in the user manual.\n order\n \nResolution: \n----------\nAfter some research it was determined that the functionality for automatically\nmarking the records mentioned above as expired worked when the user selected\nRX (PRESCRIPTION RECEIVED DATE) in the prompt below when entering the eRx\nHolding queue (Complete Orders from eRx [PSO ERX FINISH] option). However,\nif they select PT (PATIENT(Grouped)) the software did NOT check for records\nCRN elegible for expiration to mark them as expired. Furthermore, the issue\nalso seem affect RRN (RENEWAL REQUEST - NEW) records which are also supposed\n\n
\nSee patch description for PSO*7.0*449.\n\n
\nBackup of PSO*7.0*639 on Jul 07, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will address the following issues: \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC17106168 - Cincinnati VISTA application is not allowing me to renew\n prescription orders.\n INC17248638 - Speed renewal function in HAC back door VistA is kicking\n (Duplicate) all our users out of VistA.\n \nProblem:\n-------\nThe Dayton VA Medical Center reported an <UNDEFINED> error with the Speed\n \nRenew action in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\noption. It was confirmed that this issue was introduced by patch PSO*7.0*626.\n \nResolution:\n----------\nThe patch address the <UNDEFINED> error and also allows the user to enter an\nISSUE DATE up to 1 year in the past for speed renewals. Before the users were\nlimited to a date no greater than 6 months. Then, it will screen out any CS\nprescriptions if the ISSUE DATE entered is greater than 6 months with the\nfollowing message:\n1. INC17106168 - Cincinnati VISTA application is not allowing me to renew\n \n Rx# 2299064 - Rx is for a CS Drug and the Issue Date entered (Jul 17, 2020)\n is greater than 6 months.\n \n Type <Enter> to continue or '^' to exit: \n \nTechnical Resolution:\n--------------------\nChanged the code under line tags CID and CIDH to allow and ISSUE DATE value \nof up to 366 days in the past if the variable DA is defined and the Rx is\n prescription orders.\nnon-CS or if the variable DA is not defined. And restrict a date up to 184\ndays in the past if the variable DA is defined and the Rx is CS. Introduced\ncode at PROCESS+22 in the routine PSORENW4 to screen out CS prescriptions if\nthe ISSUE DATE value is greater than 184 days.\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A \n \n\n
\nBackup of PSO*7.0*636 on Jul 08, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nRESET COPAY LIST MANAGER UPDATES\n\n
\nBackup of PSO*7.0*524 on Jul 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7.0*524.\n\n
\n1) When filling pending orders either using Complete Orders from OERR\nthis type of routing pharmacy should see the routing as window, but was\ndisplaying as mail causing prescriptions to be mailed to the patient.\n \n3) When a refill is created for an active order with a fill date of today\nusing the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\noption, and in the same session if this refill is deleted, it was observed\nthat the label print routine was trying to process this refill even though\nit had been deleted. This patch fixes this problem.\n[PSO LMOE FINISH] option or through Patient Prescription Processing \n[PSO LM BACKDOOR ORDERS] option, the issue date does not show the correct\nentry date, instead it shows the filling date. This patch fixes this\nproblem.\n \n2) This patch corrects a problem when renewing prescriptions through the\nComputerize Patient Record System (CPRS) package and the routing is\nentered as administered in clinic. When prescriptions are entered with\n\n
\nBackup of PSO*7.0*630 on Aug 09, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7.0*630.\n\n
\nBackup of PSO*7.0*503 on Aug 24, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSO*7.0*503.\n\n
\n1. INC17334684 - When doing a speed reprint on a suspended Rx, it is not \n BE PRINTED using this option, use SUSPENSE FUNCTIONS Options.'\n \n Resolution:\n ----------\n Modify routine PSORXRP1 to display the message:\n #2 Rx 2297932 MAY NOT BE PRINTED using this option\n use SUSPENSE FUNCTIONS Options.\n \n Type <Enter> to continue or '^' to exit:\ngiving you a warning message\n \n Problem:\n -------\n When doing a reprint from the Medication Profile and doing a reprint \n of a suspended RX, the label doesn't print and no warning message is\n displayed to the user. Conversely, when doing a reprint on the single\n RX (OP Medications) screen, a warning message is displayed; 'RX MAY NOT\n\n
\nThis patch will fix the following:\n \nThe Rx reference of an original fill that is displayed on an activity log \nrecord is incorrect when the CMOP site reports a change in the Rx's \nNational Drug Code (NDC). This occurs when the Rx has a suspended refill \nand the original fill's fill date is changed. \n\n
\nThe Inbound Electronic Prescribing (eRx) v5.0 enhancements include updates to\nprescriptions for controlled substance medications.\n Patient Centric View\n ERX LOOK-BACK DAYS: Default value 365 (Feb 27, 2020)\n ERX PATIENT DOB ED LOCKED BY NW WT IP HD CCR OTH TOT\n ---------------------------------------------------------------------------\n 1] TESTONE,ONE 08/12/1956 12 0 0 4 0 0 0 4\n 2] TESTTWO,TWO 08/12/1956 12 0 0 7 1 0 0 8\n 3. TESTSIX,SIX 09/30/1938 6 0 0 1 1 0 0 2\n 4. TESTFOUR,FOUR 11/10/1965 3 0 0 4 0 0 0 4\n 5] TESTNINE,NINE 12/18/2014 1 1 0 2 0 0 0 3\n ...\n \n \n In the example above lines 1, 2 and 5 have a ']' indicating that those \n patients have at least one controlled substance medication prescription.\n \n d) In the Prescription View the prescriptions for controlled substance \n medication will also be marked with ']' as shown below:\n \n ---------------------------------------------------------------------------\n PSO ERX HOLDING QUEUE Feb 26, 2021@14:26:24 Page: 1 of 1\n PSO ERX HOLDING QUEUE\nBelow is a list of all the applications involved in this project along with\n ERX LOOK-BACK DAYS: Default value 365 (Feb 27, 2020)\n Patient DOB Drug Provider STA Rec Date\n ---------------------------------------------------------------------------\n 1] TESTONE,ONE 8/12/56 ALPRAZOLAM 1MG TAB PROV,TEST I 02/28/21\n 2] TESTONE,ONE 8/12/56 TESTOSTERONE PATCH PROV,TEST I 02/12/21\n 3] TESTONE,ONE 8/12/56 METHYLPHENIDATE 5MG T PROV,TEST I 01/31/21\n 4. TESTONE,ONE 8/12/56 ALBUTEROL INHALER PROV,TEST I 01/29/21\n ...\n \n In the example above lines 1, 2 and 3 have a ']' indicating that the\ntheir patch number:\n prescription is for a controlled substance.\n \n e) In the Patient Centric View the SORT ENTRIES (SO) action was modified to\n add a new option to sort: ELAPSED DAYS (ED). The action was also changed\n to allow the user to separate the sorted prescriptions into two groups: \n Controlled and Non-Controlled Substances. Independently of which option\n the user picks they will be prompted whether they want to group the list\n by controlled substance or not as shown in the example below:\n \n Select Item(s): Next Screen// SO SORT ENTRIES \n \n \n 1.) PATIENT NAME\n 2.) DATE OF BIRTH\n 3.) ELAPSED DAYS (ED)\n \n Select one of the following sort criteria: \n \n Enter response: 3 ELAPSED DAYS (ED)\n \n Do you want to group by controlled substance? \n APPLICATION/VERSION PATCH\n \n Enter Yes or No: YES// \n \n If the user answers YES the patients with at least one prescriptions for\n a controlled substance medication will be moved to the top of the list \n while the others will be moved to the bottom as shown below:\n \n ---------------------------------------------------------------------------\n 1] TESTONE,ONE 08/12/1956 6 0 0 4 0 0 0 4\n 2] TESTTWO,TWO 08/12/1956 5 0 0 7 1 0 0 8\n -----------------------------------------------------------------\n 3] TESTNINE,NINE 12/18/2014 2 1 0 2 0 0 0 3\n 3. TESTSIX,SIX 09/30/1938 3 0 0 1 1 0 0 2\n 5. TESTFOUR,FOUR 11/10/1965 0 0 0 4 0 0 0 4\n ...\n \n f) When a DO NOT FILL marked record is received in the eRx Holding Queue it\n will be identified in the header with the text below (in reverse video)\n when the user is view viewing such record, as shown below:\n \n eRx Holding Queue Display Apr 01, 2021@09:58:15 Page: 1 of 3\n OUTPATIENT PHARMACY (PSO) V. 7.0 PSO*7*617\n eRx Patient: TEST,PATIENT\n eRx Reference #: 2002894 ERX HAS DO NOT FILL INDICATOR PER PROVIDER\n eRx HT: (cm)() eRx WT: (kg)()\n ---------------------------------------------------------------------------\n ...\n \n Note: The only two actions that can be performed on a DO NOT FILL record are \n REJECT and REMOVE.\n \n g) When viewing an eRx record the DEA# will be displayed along with the\n CONTROLLED SUBSTANCE (PSD) V. 3.0 PSD*3*89\n other information about the Provider (eRx and VistA) as shown below:\n \n ...\n eRx Provider Primary Telephone: 555-220-0303 \n eRx Provider: TEST,PROVIDER\n DEA#: TP1234568 NPI: 123456789\n Vista Provider: TEST, PROVIDER F.\n DEA#: TP1234568 NPI: 123456789\n ...\n \n \n h) For controlled substance medication eRx records the DEA Schedule will\n be displayed right after the drug name (eRx and Vista) in the following\n format:\n \n eRx Holding Queue Display Apr 06, 2021@10:22:57 Page: 1 of 3\n eRx Patient: CS-ONLY,ONE\n eRx Reference #: 4928403\n eRx HT: (cm)() eRx WT: (kg)()\n ---------------------------------------------------------------------------\n eRx Drug: MEPHOBARBITAL 100MG TABLET [C-IV] \nthe current eRx functionality to allow the VA to receive and dispense \nBelow is a list of new and changed functionality delivered by this patch to\n eRx Qty: 30 eRx Refills: 0 eRx Days Supply: 30 eRx Date: APR 06, 2021\n eRx Sig: TAKE ONE TABLET BY MOUTH ONCE DAILY \n \n Vista Drug: MEPHOBARBITAL 100MG TAB [C-IV] \n Vista Qty: 30 Vista Refills: 0 Vista Days Supply: 30\n ...\n \n i) The VistA Patient selection/validation for controlled substance\n medication eRx records will perform a check whether the selected VistA\n patient has a ZIP CODE on file or not. If the VistA patient does not\nsatisfy the DEA requirements for receiving, processing and dispensing\n have a ZIP CODE on file the following message will be displayed: \n \n i1. VistA Patient Selection/Edit (user will be allowed to proceed):\n \n **************************** WARNING(S) *****************************\n Patient does not have a current mailing or residential address on file.\n ************************************************************************\n \n i2. VistA Patient Validation (user will not be allowed to proceed):\n \nelectronic prescriptions for controlled substance medications.\n Unable to validate - VistA Patient does not have a current mailing\n or residential address on file.\n \n j) The VistA Provider selection/validation for controlled substance\n medication eRx records will perform a few checks to validate whether the\n selected VistA Provider is eligible to write the prescription:\n \n j1. Provider does not have a valid not expired DEA# on file:\n \n ***************************INVALID PROVIDER*****************************\n \n Missing VistA Provider DEA#\n ************************************************************************\n \n j2. The VistA Drug was previously selected and VistA Provider is not\n authorized to write to the VistA drug DEA schedule:\n \n ***************************INVALID PROVIDER*****************************\n VistA Provider TEST,PROVIDER is NOT authorized to write to the schedule\n (C-II) of the VistA drug selected.\n ************************************************************************\n1. New HOLD, REJECT and REMOVE codes\n \n j3. VistA Provider's DEA # expires prior to eRx written/issue date:\n \n ***************************INVALID PROVIDER*****************************\n eRx Written Date/Issue Date is after the VistA Provider DEA expiration\n date (MM/DD/YY).\n ************************************************************************\n \n j4. eRx Provider's DEA # does not match VistA Provider DEA # (allows \n selecting the provider with a warning but blocks validation)\n ---------------------------------------------------------------------------\n \n *********** WARNING (edit) / INVALID PROVIDER (validation) *************\n Provider DEA mismatch (eRx: TP123456 | VistA: TP654321)\n ************************************************************************\n \n j5. The VistA Drug was previously selected and is a DETOX drug and VistA\n Provider does not have a valid not expired DETOX # on file (VistA\n drug must be previously selected):\n \n *********** WARNING (edit) / INVALID PROVIDER (validation) *************\n The following new codes have been added:\n VistA Provider TEST,PROVIDER does not have a valid DETOX#\n ************************************************************************\n \n j6. During Provider validation the functionality that allows the user to\n assign the same provider to other prescriptions that match the eRx\n provider was changed to check whether the VistA provider is \n authorized to write each prescription if they are for a controlled \n substance or detox medication. If the VistA provider is not \n authorized a message will be displayed for the eRx and it will not\n be selected/validated for the prescription.\n \n \n k) The VistA Drug selection/validation for controlled substance medication\n eRx records will perform a few checks to validate whether the selected \n VistA Drug can be used for the prescription:\n \n k1. When the user selects the VALIDATE DRUG/SIG (VD) action and then\n selects the Edit (E) action to select the VistA dispense drug to\n associate it with the eRx record the prompt 'Select GENERIC DRUG\n NAME:' will now allow the selection of a drug marked as Controlled\n Substance. Before, CS drugs were not allowed to be selected.\n HOLD Codes:\n \n k2. VistA Drug selected is NOT marked as a controlled substance \n medication the eRx record is for a controlled substance (user will\n be allowed to proceed with a warning):\n \n **********************************WARNING*******************************\n eRx Drug is indicated by the prescriber as CS ([C-IV]) and VistA Drug\n selected is Non-CS. Please, review and make sure you selected the\n correct drug.\n ************************************************************************\n -----------\n \n k3. The VistA Drug selected is locally (not NDF matched) marked as a \n controlled substance medication and the eRx record is not for a\n controlled substance (does not have a digital signature). User will\n not be able to select the drug:\n \n *******************************INVALID DRUG*****************************\n eRx is not digitally signed and VistA drug is non-CS and VistA drug is\n not matched to an NDF item marked with a CS Federal Schedule but is\n locally marked as a controlled substance ([C-II]).\nelectronic prescriptions for controlled substance medications. Up until now\n HCR - PRESCRIBER'S CS CREDENTIAL IS NOT APPROPRIATE (New)\n ************************************************************************\n \n k4. The VistA Drug selected is matched to and NDF item marked as a\n controlled substance medication and the eRx record is not eligible\n for a controlled substance (does not have a digital signature). User\n will not be able to select the drug:\n \n *******************************INVALID DRUG*****************************\n eRx is not digitally signed and VistA Drug is marked as CS ([C-III]).\n ************************************************************************\n HWR - CS PRESCRIPTION WRITTEN/ISSUE DATE HAS PROBLEMS (New)\n \n k5. The VistA Provider was previously selected and is not authorized to\n write to prescription for the DEA schedule of the VistA Drug :\n \n ******************************INVALID DRUG******************************\n VistA Provider TEST,PROVIDER is NOT authorized to write to the schedule\n (C-II) of the VistA drug selected.\n ************************************************************************\n \n k6. The VistA Provider was previously selected and does not have a valid\n HIS - PROVIDER DEA# ISSUE (New)\n not expired DETOX # and the VistA Drug selected is a DETOX drug.\n \n *********** WARNING (edit) / INVALID PROVIDER (validation) **************\n VistA Provider TEST,PROVIDER does not have a valid DETOX#\n *************************************************************************\n \n l) In the eRx Holding Queue Display where a single prescription is displayed\n a new hidden action called View Audit Log (AU) was introduced. This new\n functionality will allow the user to track every edit made to the eRx\n during the transcription of the eRx data to match the VistA corresponding\n HRX - HOLD FOR RX EDIT (New)\n entries. The log looks like the screen below and can be sorted by \n DATE/TIME, FIELD NAME or EDITED BY columns.\n \n eRx Audit Log May 14, 2021@15:27:57 Page: 1 of 2 \n -------------------------------------------------------------------------\n eRx Patient: TEST,OUTPONE F\n eRx Reference #: 494949\n -------------------------------------------------------------------------\n DATE/TIME [^] FIELD NAME EDITED BY\n -------------------------------------------------------------------------\n HDE - DRUG USE EVALUATION (New)\n Jan 28, 2021@09:47:45 PATIENT TEST,USER F\n Old Value:\n New Value: TEST,OUTPONE (L4SSN: 7944 | DOB: DEC 18,2014)\n \n Jan 28, 2021@09:48:06 DRUG TEST,USER F \n Old Value: \n New Value: LOESTRIN FE 1/20 TAB,28 (NDC#: 51285-0080-70)\n \n Jan 28, 2021@09:48:13 SIG TEST,USER F \n Old Value: \n HTI - THERAPUTIC INTERCHANGE (New)\n New Value: TAKE ONE TABLET PO ONCE DAILY \n \n Jan 28, 2021@09:48:18 QTY TEST,USER F \n Old Value: \n New Value: 30 \n -------------------------------------------------------------------------\n + Enter ?? for more actions \n DT Sort by DATE/TIME EB Sort by EDITED BY\n FN Sort by FIELD SH Show/Hide eRx Value\n Select Item(s): Next Screen// \n HSC - SCRIPT CLARIFICATION (New)\n \n l1) The actions DT, FN and EB are used to sort the list by the columns \n DATE/TIME, FIELD NAME and EDITED BY respectively. The SH action will\n show o hide the original prescription value for the field from the\n eRx record as shown below: \n ...\n Jan 28, 2021@09:47:45 PATIENT TEST,USER F\n eRx Value: TEST,OUTPONE F (L4SSN: 7944 | DOB: DEC 18, 2014) \n Old Value: \n New Value: TEST,OUTPONE (L4SSN: 7944 | DOB: DEC 18,2014) \n HGS - GENERIC SUBSTITUTION (New)\n ...\n \n m) Besides the "]" (closing square bracket) described in the letter d)\n above to identify CS (digitally signed) eRx records once you select a\n specific record it will display on the top right corner of the\n scrollable are the following note (in reverse video) "EPCS DEA\n VALIDATED" to indicate to the user processing the record that the \n electronic digital signature has been validate and also to comply with\n SureScripts requirements for CS prescriptions. In addition, these \n records will also contains the foot note:\n \n \n This prescription meets the requirements of the Drug Enforcement\n Administration (DEA) electronic prescribing for controlled substances\n rules (21 CFR Parts 1300,1304, 1306, & 1311).\n \n n) When the user selects the action EC (eRx Change Request) for a CS eRx\n record they will be limited to selecting only one of the following two\n values below (P or U):\n \n Select RX change message request code: ?\n REJECT Codes:\n Answer with ERX SERVICE REASON CODES, or NUMBER, or BRIEF DESCRIPTION,\n or CODE TYPE ABBREVIATION, or NCIT SUBTYPE\n Do you want the entire ERX SERVICE REASON CODES List? y (Yes)\n Choose from:\n 9999 P Prior Authorization Required\n 9999 U Prescriber Authorization\n \n Select RX change message request code:\n \n o) When a Pending Order is un-accepted (see 5a below) a new entry will be\nthe eRx Holding Queue restricted the selection of a controlled substance VA\n -------------\n added to the Status History for the related eRx record to indicate that\n it was un-accepted and sent back to the eRx Holding Queue. Below is an\n example how it will display:\n \n Select Action:Next Screen// SH Status History \n -------------------------------------------------------------------------\n ...\n 07/17/20@10:48:50 PR PROCESSED\n Entered By: USER, NAME F\n Comments: \n PVD03 - Missing/bad digital signature on inbound CS ERX (New)\n \n 07/18/21@14:17:30 HRX HOLD FOR RX EDIT (eRx Un-Accepted)\n Entered By: USER, NAME F\n Comments: Wrong Patient associated with Rx\n \n Type <Enter> to continue or '^' to exit: \n \n5. Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n Complete Orders from OERR [PSO LMOE FINISH]\n ---------------------------------------------------------------------------\n PVD04 - Prescriber's CS credential is not appropriate (New)\n A few changes have been made to the Pharmacy Backdoor options listed above\n to comply and facilitate the processing of controlled substance medication\n prescriptions:\n \n a) When viewing a Pending eRx Order the user will have the available a new\n hidden action called 'Un Accept eRx' (UA) which after answering a few\n prompts the record will be sent back to the eRx Holding Queue for\n further processing there, as shown below:\n \n ...\n PTT03 - Patient's mailing address is missing/mismatched (New)\n Select Item(s): Next Screen// UA UA \n \n Select HOLD reason code: HOLD FOR RX EDIT// HRX HOLD FOR RX EDIT\n Comments (Optional): Wrong Patient associated with Rx\n \n This eRx will be Un-Accepted and sent back to the eRx Holding Queue.\n \n Confirm? N// YES Please wait...\n \n eRx successfully un-accepted and placed back on the eRx Holding Queue.\n DRU06 - Controlled Substances are disallowed (Renamed)\n \n Type <Enter> to continue or '^' to exit:\n \n b) When viewing a digitally signed eRx pending order the first line of the\n scrollable area will display the text "Processing Digitally Signed eRx\n Order" in reverse video to indicate to the user the they are processing\n a prescription for a controlled substance medication.\n \n c) Also, for digitally signed eRx pending orders at the end of the\n scrollable area there will be a foot note that says:\n DRU06 - CS prescription written/issue date has problems (New name)\n \n This prescription meets the requirements of the Drug Enforcement\n Administration (DEA) electronic prescribing for controlled substances\n rules (21 CFR Parts 1300,1304, 1306, & 1311).\n \n d) Digitally signed eRx pending orders cannot be edited. In order to edit\n any field on this type of pending orders they user would have to either\n Un-Accept the pending order, edit it in the eRx Holding Queue and then\n Re-Accept it; or finish the pending order and then edit the Active or\n Suspended prescription.\n ERR99 - Other\n \n e) A new hidden action called Jump to eRx (JE) was included in the list of\n hidden actions available for an eRx pending order or an eRx active \n prescription. When a user viewing a pending order or an active\n prescription types JE it will take them to the eRx Holding queue to\n the screen showing the corresponding eRx record. Once they quit out of\n eRx record they will return them back to pending order or active\n prescription.\n \n f) When a new CS eRx is finished and becomes an ACTIVE prescription it will\n \n display "Digitally Signed eRx Order" on the message bar right above the\n actions.\n \n g) The trailing document of the prescription label will have the "(DSIG)"\n to indicate that the prescription was digitally signed.\n \n h) The 30th piece of the ORC segment in the HL7 message sent over to OPAI (Outpatient Pharmacy Automated Interface) will contain "EL" for \n Digitally Signed eRx Controlled Substance prescriptions.\n \n6. HPS Sustaintment issues\n REMOVE Codes:\n ---------------------------------------------------------------------------\n The Inbound eRx JAVA application is a component of the PRE IEP program that\n provides the capability to receive inbound eRx's from an external provider.\n The JAVA application provides a user interface that allows end users to \n manage and monitor eRx processing from external sources. \n \n This patch resolves the incomplete users list displayed by the User \n Management screen in the Inbound eRx web-based application.\n \n Defect Tracking System Ticket(s) & Overview:\n -------------\n ============================================\n INC11772378 - Inbound eRX web application not displaying correctly\n INC18070242 - Inbound eRX web application not displaying correctly\n \n Problem:\n --------\n The User Management screen allows Administrators to add new users to one or\n more sites (Station ID), enable users, disable users, modify user roles and\n existing user records by assigning them to one or more sites. This screen\n will only display for users with Administrator access. However, User \ndispense drug for any incoming electronic prescription due to the fact that\n REM09 - ERX Issue not resolved-Provider contacted (New)\n Management screen is currently displaying limited number of users, not the\n entire list of users.\n \n Resolution:\n ----------\n Refactored Java code in order to fix the User Management component of the \n Inbound eRx application. After the fix is implemented, complete list of users\n is displayed on the User Management screen.\n \n \n \nPatch Components\n================\nFiles & Fields Associated:\n \nFile Name (#) Field Name (#) New/Modified/Deleted\n----------------- -------------------------------------- --------------------\nERX HOLDING QUEUE (#52.49) Modified \n DO NOT FILL (#10.5) Modified\n STATUS HISTORY sub-file (#19) Modified\n - UN-ACCEPTED ERX FLAG (#.04) New\n2. CMOP Controlled Substance Rx Dispense Report [PSO CMOP CS RX DISPENSE\n AUDIT LOG sub-file (#20) New\n - EDIT DATE/TIME (#.01) New\n - FIELD NAME (#.02) New\n - EDITED BY (#.03) New\n - NEW VALUE (#.04) New\n CONTROLLED SUBSTANCE INDICATOR (#95.1) New\n CS DIG SIGNATURE DIGEST METHOD (#95.2) New\n CS DIG SIGNATURE DIGEST VALUE (#95.3) New\n CS DIG SIGNATURE VALUE (#95.4) New\n CS DIG SIGNATURE X509 DATA (#95.5) New\n REPORT]\n \nPRESCRIPTION (#52) ERX SIGNATURE STATUS (#312) New\n \nProtocols Associated:\n \nProtocol Name Type New/Modified/Deleted\n------------- ------- --------------------\nPSO ERX ACCEPT ERX Action Modified\nPSO ERX AUDIT LOG MENU Menu New\nPSO ERX AUDIT LOG SHOW/HIDE ERX VALUE Action New\n ---------------------------------------------------------------------------\nPSO ERX AUDIT LOG SORT BY DATE/TIME Action New\nPSO ERX AUDIT LOG SORT BY EDITED BY Action New\nPSO ERX AUDIT LOG SORT BY FIELD NAME Action New\nPSO ERX HIDDEN ACTIONS Menu Modified\nPSO ERX JUMP TO ERX Action New\nPSO ERX UN-ACCEPT Action New\nPSO ERX VIEW AUDIT LOG Action New\nPSO HIDDEN ACTIONS Menu Modified\nPSO HIDDEN ACTIONS #3 Menu Modified\nPSO PMP HIDDEN ACTIONS MENU #2 Menu Modified\n The report option above was modified to include the ampersand sign (&)\n \nTemplates Associated:\n \nTemplate Name Type File Name (#) New/Modified/Deleted\n------------- ---- ------------- --------------------\nPSO ERX AUDIT LOG List N/A New\n before the Rx # to indicate the prescription is an eRx prescription (e.g.,\n &29039001A)\n \n3. Released and Unreleased Prescription Report [PSO RELEASE REPORT]\nthe functionality was not 100% compliant with the DEA requirements (21 CFR\n ---------------------------------------------------------------------------\n The report option above was modified to include the ampersand sign (&)\n before the Rx # to indicate the prescription is an eRx prescription (e.g.,\n &29039001A)\n \n4. Complete Orders from eRx [PSO ERX FINISH]\n ---------------------------------------------------------------------------\n A few changes have bene made to the eRx Holding queue option above to\n comply and facilitate the processing of controlled substance medication\n prescriptions.\nPart 1311 Subpart C) for receiving, processing and dispensing controlled\n \n a) A new filter was introduced to allow the user to select the type of\n prescriptions to be loaded on the eRx Holding Queue as shown below:\n \n Select one of the following:\n \n Non-CS Non-Controlled Substance\n CS Controlled Substance\n B Both\n \nsubstance electronic prescriptions. This project addresses all the DEA\n Select eRx Record Type: B// \n \n b) If the selection above is either CS or B, a new filter prompt was added\n to allow the user to further filter based on the CS Schedule of the \n controlled substance medication as shown below:\n \n Select one of the following:\n \n 1 Schedule II\n 2 Schedules III - V\nrequirements and enables the eRx Holding Queue to process incoming electronic\n 3 Schedules II - V\n \n Select Schedule(s): 3// \n \n c) In the Patient Centric View if a patient has a prescription for a \n controlled substance medication the line item will be marked with a \n closing square bracket (]) following the line number as shown below:\n \n ---------------------------------------------------------------------------\n PSO ERX PATIENT CENTRIC VIEW Feb 26, 2021@14:19:30 Page: 1 of 2\n\n
\nSee the Forum patch description.\n\n
\nThe description for PSO*7*653 can be found in the National Patch Module.\n\n
\n1. Problem: Consolidated Mail Outpatient Pharmacy fills that have been\n2. Problem: Prescriptions that have a faulty status of 'Suspended' error\nout in CMOP code trying to update the prescription suspense comments.\n \nResolution:\n \nThe Outpatient code has been changed to test for the existence of the\nprescription in the RX SUSPENSE file (#52.5) prior to performing a CMOP\nupdate.\n \n3. Problem: New prescriptions with drugs that have been marked for CMOP\nreturned to stock are being allowed to be re-suspended to CMOP\nbut have drug warnings greater than 11 characters are being dropped into\nnormal suspense without any message to the user. The intent is to have\nthese prescriptions go to CMOP. \n \nResolution:\n \nThe Outpatient code has been modified to send an appropriate message to\nG.CMOP Managers regarding the prescription and the drug warning length\nproblem.\n \nResolution:\n \nThe Outpatient coding has been changed to test the prescription fill's\nCMOP activity and will not allow it to go to CMOP suspense if the status\nis not proper.\n \n\n
\nThis patch will address the following issue: \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC18871441 - Patient has duplicate Rx in Vista Outpatient package\n HITPS-8075\n Duplicates: \n -----------\n \n INC18557780 - VISTA Pharmacy Display Issue - route to Clinical\n Ancillary Product Line, EPMO Health per their request\n \nProblem:\n-------\nThe WM. Jennings Bryan Dorn VA Medical Center reported the patient had the\nsame Rx with identical Rx number showing twice Patient Medication Profile when\nviewing the patient in the Patient Prescription Processing [PSO LM BACKDOOR\nORDERS] option. This issue is also being considered a Patient Safety Issue\n(PSI) and the number assigned by the Patient Safety team is HITPS-8075.\n1. INC18871441 - Patient has duplicate Rx in Vista Outpatient package\n \nWhile researching the problem 2 different issues were also identified that\nactually led to the issue described by the site:\n 1) When the user use the option TR (Convert Titration Rx) to create a \n Maintenance Rx from the Titration Rx the Issue Date assigned to the\n new Maintenance Rx was the current date. The correct Issue Date for\n the Maintenance Rx should be the same as the original Titration Rx. The\n Expiration Date was correctly copied from the Titration Rx to the \n Maintenance Rx.\n 2) When the user select the new Maintenance Rx and chose ED (Edit) and\n HITPS-8075\n entered 6 (Issue Date) and just <RET> trough the field without changing\n the date the software was re-calculating the Expiration Date based on the\n Issue Date which was originally set with the wrong value (issue #1).\n 3) The edit performed on issue #2 failed to correctly update the cross-\n reference "P"/"A" in the PHARMACY PATIENT file (#55). Instead of killing\n off the existing cross-reference for the previous Expiration Date and\n setting a new entry for the recalculated Expiration Date it was only\n setting the additional entry causing the prescription to have two entries\n in the "P"/"A" cross-reference and that is what caused the duplicate\n listing of the prescription in the Patient Medication Profile.\n Duplicates: \n \nResolution:\n-------------\nTwo changes had to be done to address the problem which will fully address the\nthree issues listed above:\n 1) The Issue Date from the Titration Rx will be copied to the Maintenance Rx\n when the user select the option TR (Convert Titration Rx).\n 2) The software was changed to correctly kill off re-set he "P"/"A" cross-\n reference for when the Expiration Date is changed.\n \n -----------\nTechnical Resolution:\n--------------------\nTwo changes were made to address the problems:\n 1) Added code at DT+11 in the routine PSOEXDT to reset the "P"/"A" cross-\n reference in the PHARMACY PATIENT file (#55) every time the expiration\n date is changed.\n 2) Added code at RFN+5 in the routine PSOORED1 to copy the Issue Date value\n from the Titration Rx to the newly created Maintenance Rx.\n \n \n INC18557780 - VISTA Pharmacy Display Issue - route to Clinical\nPatient Safety Issues (PSIs):\n-----------------------------\nHITPS-8075\n Ancillary Product Line, EPMO Health per their request\n \n\n
\nThis patch will fix the following issue:\n \nThere is a recurring error when utilizing the option PSO ERX FINISH \n(Complete Orders from eRx). This option is used to process prescriptions\nin the PSO ERX HOLDING QUEUE. The error occurs when a user selects the \nPrint action and enters yes to have the print queued to run in the\nbackground. \n\n
\nThis patch will resolve the following issues:\n2. INC18243915 - Incomplete SPMP error message. When users delete state \nparameter(s) in the View/Edit SPMP State Parameters [PSO SPMP STATE \nPARAMETERS] option, the View/Export Single Prescription [PSO SPMP SINGLE\nRX VIEW/EXPORT] displays an incomplete error message without the state\nname: "PMP Parameters missing for".\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \n \nAdditional Information:\n-----------------------\nDefect Tracking System Ticket(s) & Overview:\n \nINC19435178 (parent) and INC19726930 (child)\nINC18243915\n \n \n1. INC19435178 (parent) and INC19726930 (child) - SPMP voids from the new \nProblem:\n--------\nDurham VA Medical Center reported that the voids created with the new\nView/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] option\nintroduced with patch PSO*7*625, were rejected due to missing required\nfields for the state. The missing fields are DSP05 (Date Filled), DSP09\n(Quantity Dispensed) and DSP10 (Days Supply).\n \nAlvin C. York VA Medical Center reported that the user deleted a state \nparameter in the View/Edit SPMP State Parameters [PSO SPMP STATE \nView/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] option are\nPARAMETERS] option, the View/Export Single Prescription [PSO SPMP SINGLE\nRX VIEW/EXPORT] option displays an incomplete error message missing the \nstate name: "PMP Parameters missing for".\n \n \nResolution:\n-----------\nThe following changes were made to address the issues listed above:\n1) Update the logic for the View/Export Void Prescriptions [PSO SPMP \nVOID RX VIEW/EXPORT] option to send the missing required fields\nmissing required fields for the state. The View/Export Void Prescriptions\n(DSP05, DSP09, and DSP10).\n \n2) Update the logic for the View/Export Single Prescription [PSO SPMP \nSINGLE RX VIEW/EXPORT] option to display the complete error message when \nstate parameters are not set up.\n \n \nTechnical Resolution:\n---------------------\nThe following changes were made to address the issues listed above:\n[PSO SPMP VOID RX VIEW/EXPORT] option was introduced by patch PSO*7*625, \n1) Routine PSOASAP0 was updated in the DSP05, DSP09, and DSP10 tags to \nsend the DSP05, DSP09, and DSP10 fields for the new "RX" void batch type.\n \n2) Routine PSOSPML4 was updated in the EXPORT+9 tag to display the \nappropriate state parameter error message.\nand the voids are missing the DSP05 (Date Filled), DSP09 (Quantity\nDispensed) and DSP10 (Days Supply) fields.\n \n\n
\nINC19182976 - Remote Data Interoperability (RDI) displays incorrect\n number of refills remaining for remote prescriptions\n\n
\nThis patch addresses the following issue:\n \nDuplicate order checking might display an incorrect dispense drug against \npending clinic medications.\n\n
\nSee the patch description for detailed information.\n\n
\nThis patch will resolve the following issues:\n \nProblem:\n--------\nIt was reported that the PAGE counter on the Extended Patient \nDemographics page was not getting reset when going between Complete \nOrders from OERR [PSO LMOE FINISH] option and the View Prescriptions [PSO \nVIEW] option within the RX (Prescription) [PSO RX] menu.\n \n \nResolution:\n \n-----------\nThe following changes were made to address the issue:\nReset the page number for Extended Patient Demographics only when\nswitching between Complete Orders from OERR [PSO LMOE FINISH] option and\nthe View Prescriptions [PSO VIEW] option within the RX (Prescription) [PSO\nRX] menu.\n \n \nTechnical Resolution:\n---------------------\n1. INC20140218 - Page Number keeps counting in Extended Patient \nThe following changes were made to address the issue:\nRoutine PSODEMSB was updated in the HDR tag to reset the page counter \nfor Extended Patient Demographics only when going between the Complete\nOrders from OERR [PSO LMOE FINISH] option and the View Prescriptions [PSO\nVIEW] option within the RX (Prescription) [PSO RX] menu.\nDemographics\n \nDefect Tracking System Ticket(s) & Overview:\n \n1. INC20140218 - Page Number keeps counting in Extended Patient \nDemographics\n\n
\nThis patch will resolve the following issue:\n \n \nAdditional Information:\n-----------------------\nDefect Tracking System Ticket(s) & Overview:\n \n1. INC18606996 - Prescriptions (RXs) being queued and suspended twice in\n VistA Outpatient package.\n \n \n \nProblem:\n--------\nThe Orlando VA Medical Center (FL) reported that the same prescription\nis being queued and suspended twice in the Patient Medication Profile when\nediting and refilling a single prescription in the Patient Prescription \nProcessing [PSO LM BACKDOOR ORDERS] option.\n \nResolution:\n-----------\nThe following changes were made to address the issue listed above:\n1. INC18606996 - Prescriptions (RXs) being queued and suspended twice in \n1) Check the array that contains the prescriptions for duplicates.\n \nTechnical Resolution:\n---------------------\nThe following changes were made to address the issue listed above:\n1) Added code starting at FINISH+33 in the PSOR52 routine to check for\n duplicate RX numbers in the PSORX("PSOL",N) array variable.\n VistA Outpatient package.\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n\n\n \nINC14294718 - An issue is occurring when processing orders resulting in an\n infinite loop of 'Press return to Continue' prompts.\n\n
\n1) During the order entry process using Patient Prescription Processing\nOutpatient Pharmacy when requested from Computerized Patient Record\nSystem (CPRS). This problem only occurs when invalid data is found in the\nPENDING OUTPATIENT ORDERS file (#52.41).\n \n3) When renewing a prescription using Patient Prescription Processing\n[PSO LM BACKDOOR ORDERS] option, it was observed by some sites (set for\nauto suspend), that the renewed prescription is getting suspended to the\nwrong date. The renewal process calculates the FILL DATE field (#22)\nbased on the NEXT POSSIBLE FILL field (#102) of PRESCRIPTION file (#52).\nIt also checks to see if a record exits in RX SUSPENSE file (#52.5)\n[PSO LM BACKDOOR ORDERS] option, if the user opts to address more than\nand its PRINTED field (#2) is set. For some reason (timing delay/system\nproblems), this field is not being set for CMOP drugs even when the drug\nwas released. In such situations the renewal process tends to set the FILL\nDATE field (#22) to the LAST DISPENSED DATE field (#101) of PRESCRIPTION\nfile (#52). This patch ensures that, for these situations, if the\ncalculated FILL DATE field (#22) of PRESCRIPTION file (#52) is less than\nthe current date then it gets set to the current date unless a lesser date\nthan the current date is requested by the users.\none prescription at a time simultaneously, the word "Release" is being\ndisplayed along with the routing type (Mail/Window) for each prescription\neven though it is not released. It had picked up the release status of a\nprior prescription. This is due to one of the variables not being killed.\nThis patch fixes this problem.\n \n2) This patch corrects a problem of a refill request not being seen in\n\n
\n \n-----------------------------\nN/A\n \n \nAdditional Information:\n-----------------------\nDefect Tracking System Ticket(s) & Overview:\n \nINC15468023 (parent) and INC16381883 (child)\n \nThis patch will resolve the following issue:\n \nProblem:\n--------\nRalph H. Johnson Department of Veterans Affairs Medical Center in \nCharleston SC reported that Vista is creating duplicate prescriptions \nwhen the user is disconnected while finishing a pending renewal \nOutpatient Pharmacy.\n \n \nResolution:\n \n-----------\nThe following changes were made to address the issue listed above:\n1) Update the logic for finishing a pending renewal in [PSO LM BACKDOOR \nORDERS] to wait to file data into File #55 (Pharmacy Patient) and File #52\n(Prescription) until all prompts are answered. So if the user is\ndisconnected, the pending renewal will remain pending. In addition, when\nthe pending renewal has been completed a new message will display on the\nscreen notifying the user that the order has been renewed \n(i.e. "...ORDER RENEWED.")\n \n1. INC15468023 (parent) and INC16381883 (child) - Duplicate RX when \n \nTechnical Resolution:\n---------------------\nThe following changes were made to address the issue listed above:\n1) Routine PSORN52A was updated in the F55 tag to wait to file data into \nFile #55 (Pharmacy Patient) and File #52 (Prescription) until all prompts \nare answered.\n \n2) Routine PSOORNE4 was updated in the PKI tag to display "...ORDER \nRENEWED." when the renewal process is complete in [PSO LM BACKDOOR \nfinishing pending renewal in Outpatient Pharmacy [PSO LM BACKDOOR \nORDERS].\nORDERS] and user gets disconnected.\n \n \nPatient Safety Issues (PSIs):\n\n
\n1. INC19108358- HL7 field ORC-13 is sometimes blank when \n PP (Pull Rx (OP)) from the Outpatient Medications screen in Patient\n Prescription Processing the issue does not occur and ORC-13 is\n populated with the selected LABEL PRINTER.\n \n Resolution:\n ----------\n Routine PSORXL is modified to pass variable PSOLAP to the background \n processing job unconditionally. Prior to this patch the variable \n PSOLAP was only passed when variable SUSPT was false, when SUSPT was\n true it attempted to pass PFION which doesn't exist anywhere in Vista.\n transmitting from VistA to ScriptPro\n \n Technical Resolution:\n --------------------\n Prior to this patch QLBL+7^PSORXL used the following condition to send \n either variable PFION or PSOLAP depending on the existence of variable \n SUSPT: $S($G(SUSPT):"PFION",1:"PSOLAP")\n \n This patch modifies QLBL^PSORXL to remove the condition and reference \n to "PFION" and unconditionally send "PSOLAP" the same as occurs when PP\n is used in Patient Prescription Processing.\n \n \n Problem:\n -------\n ScriptPro states that ORC-13 is sometimes blank, causing the system\n to default to the wrong inventory center. It was found that this \n occurs when the option PULL EARLY FROM SUSPENSE is used. When running\n\n
\nThe Clinical Ancillary Services (CAS) - Medication Permission/Dispensing \n************************** ATTENTION ********************************\nThis enhancement also includes a new Graphical User Interface (GUI) \nexecutable, ePCSDataEntryforPrescriber.exe (ePCS GUI), which allows setup \nof users to write controlled substances. For retrieval and installation\ninstructions, please see the Documentation Retrieval Instructions section.\n \nThis patch PSO*7*529 has the following enhancements:\n \n1. Create a web service client to be used during installation to retrieve\n the provider information from the VA Maintained DOJ/DEA web server.\nUpdates (MPDU) project provides the ability to support multiple Drug \n This information will be stored in the DEA NUMBERS FILE (#8991.9), and\n linked to the NEW PERSON FILE (#200), NEW DEA #'S (#53.21) multiple.\n \n2. An environment check routine PSO7E529 is included in this patch that\n will provide the following VistA environment options:\n \n \n Select one of the following:\n \n P PRODUCTION\nEnforcement Administration (DEA) Numbers for a user.\n D PRE-PROD\n S SQA\n \n ENVIRONMENT TYPE: \n \n Site can select the appropriate environment and accordingly the \n software will setup the DOJ/DEA web server and the web service. It will\n check the availability of the DOJ/DEA web service and will continue the\n patch installation. If the web service is available, it will display a\n message, "The Environmental Check Routine finished Successfully" and\n \n will continue with the patch installation. If the web service is not\n available then it will abort the installation with the following\n message:\n \n *******************************************************\n WARNING: The WEB SERVER/SERVICE SETUP FAILED\n Please try again after few minutes. Failed to install,\n please submit a Service Now ticket.\n >>>> Installation aborted <<<<"\n *******************************************************\nThis patch PSO*7*529 is part of a group of patches for this enhancement\n \n3. A post-install routine PSO7P529 included in this patch will migrate\n all DEA's from the NEW PERSON FILE (#200) and will utilize the\n DOJ/DEA web service to create entries in the DEA NUMBERS FILE \n (#8991.9). Providers that cannot be linked will be recorded in a\n Migration Exception Log and will be sent in an email with the subject;\n DEA Migration Exception Report 11/28/2018 (run date) to PSDMGR key\n holders. These entries can be reviewed and corrected using the ePCS GUI\n executable that will be sent separately as part of this project.\n \nand must be installed after XU*8*688. The following other patches will be\n These migrated provider entries in the DEA NUMBERS FILE (#8991.9) will\n be marked as USE FOR INPATIENT ORDERS. The Detox # will be derived \n from the business activity code/sub code.\n \n4. Create Remote Procedure Calls to support the entry and maintenance of\n the information stored in the DEA NUMBERS FILE (#8991.9) using the ePCS\n GUI. This functionality will utilize the DOJ/DEA web service to get\n near real-time updates.\nreleased in the future and includes: OR*3*506, XU*8*689, PSO*7*545,\nPSJ*5*372, OR*3*488 and OR*3*499.\n \n\n
\nSee FORUM patch description.\n\n
\nINC19990362: eRx allows selecting providers before complete creation via \nPSO PROVIDER ADD\n \n \ners before complete creation via PSO PROVIDER \n\n
\nFollowing is the description of this issue:\n \nThere is a recurring error when utilizing the option PROCESS INTERNET \nREFILLS (PSO INTERNET REFILLS). The issue occurs after user jumps out of \noption PROCESS TELEPHONE REFILLS (PSO PROCESS TELEPHONE REFILLS) by \nentering '^' at the DIVISION prompt and then subsequently runs the \ninternet refill option, which then aborts due to an <UNDEFINED> error.\n\n
\nThis patch addresses the following issue:\n \nThe 'JUMP TO ORDER' (JO) action in the Inbound eRx system could state\n"Patient has no pending prescriptions" even though the patient does have \npending prescriptions.\n\n
\nSee FORUM patch description for details.\n\n
\nThis patch addresses the following issue:\n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. INC22416223 - VISTA: OUPATIENT PHARMACY: INBOUND ERX QUEUE ERROR\n \n Problem:\n -------\nWhile processing the INBOUND ERX QUEUE, a user erroneously entered '^E' \nat the Days Supply prompt which caused a hard error to occur. The \nproblem is that eRX processing is not written to allow jumping to other \nOUTPATIENT PHARMACY SPEED RENEW OF RX STATUS DISCONTINUED BY PROVIDER\nprompts. \n \n \n Resolution:\n ----------\nThe logic is updated to handle input that starts with a caret (^) the \nsame as when only a caret (^) is entered and exit. This change affects \nthe prompts handled by QTYDSRFL^PSOERXU4, which are DAYS SUPPLY, \nQUANTITY, and REFILLS. The error was not seen for other prompts.\n \n \n Technical Resolution:\n --------------------\nThis line at DIR+7^PSODIR1 is added:\nI $E(X,1)=U S PSODIR("DFLG")=1 G DIRX ;p686\nThis will cause the process to exit when the first character entered is a \ncaret (^).\n \nAssociated ticket(s):\n=====================\n \n1. INC22416223 - VISTA: OUPATIENT PHARMACY: INBOUND ERX QUEUE ERROR\n\n\n1) It was reported that the PATIENT STATUS field (#3) in PRESCRIPTION\n \n3) This patch corrects a problem when editing CLOZAPINE STATUS field\n(#54) of PHARMACY PATIENT file (#55) using Edit Data for a Patient in the\nClozapine Program [PSOL EDIT] option.\n \n4) During an edit of a partial prescription, up-arrowing at any fields\nother than the partial date, causes that record to be killed instead of\nquitting the edit process. This patch fixes this problem.\n \n5) When finishing orders entered through Computerized Patient Record\nfile (#52) randomly gets changed to the bingo board wait time when using\nSystem (CPRS), it was reported that for a patient status of value AUTH ABS\n+96 or AUTH ABS -96, it triggers the duplicate drug alert check when\nduplicates are found. This patch corrects this problem.\n \n6) This patch fixes a spelling error found in the report that is being\ngenerated when using the High Cost Rx Report [PSO HI COST] option.\n \n7) When renewing orders entered through CPRS or backdoor, the warning\nmessage that is being displayed during the duplicate drug/same class check\nagainst other pending orders was found to have incorrect data on the\nthe Display Patient's Name on Monitor [PSO BINGO DISPLAY PATIENT] option.\ninstruction field and the provider comments field. Also the data on these\ntwo fields were transposed. This patch fixes these problems.\n \n8) When entering the first refill using Patient Prescription Processing\n[PSO LM BACKDOOR ORDERS] option, if the user edits any field on the\noriginal prescription, it was reported that the refill is getting\nsuspended (sites having auto suspense flag set) to the original fill date\ninstead of the last dispensed date. This patch corrects this problem.\nThis patch corrects this problem.\n \n2) This patch contains a fix for the HL7 messaging routine PSOHLSG1,\nwhich is provided to transmit Outpatient Pharmacy prescriptions to\nOptifil, (an automated dispensing unit) to include a patient's temporary\naddress functionality if made active.\n\n
\nIt was reported that the Meds by Mail logic added to the State \n2. INC19848615 - View/Export Single Prescription [PSO SPMP SINGLE RX\noption to display the appropriate state.\n \nTechnical Resolution:\n---------------------\nRoutine PSOSPML4 in the EN tag, change the STATEIEN variable lookup so the\nappropriate state displays.\n \n4. INC21661107 - the View/Export Void Prescriptions [PSO SPMP VOID RX\nVIEW/EXPORT] option only transmits to the dispensing pharmacy's state.\n \nVIEW/EXPORT] option only sends to state of dispensing pharmacy\nProblem:\n--------\nThe View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT]\noption only transmits to the dispensing pharmacy's state.\n \nResolution:\n-----------\nFix the logic for the View/Export Void Prescriptions [PSO SPMP VOID RX\nVIEW/EXPORT] option to look at the dispensing pharmacy state and the\npatient state, and then look at the SEND EXPORT STATE PARAMETER (#21) \n \nfield in the SPMP STATE PARAMETERS (#58.41) file to determine what \nstate(s) the batch needs to be sent.\n \nTechnical Resolution:\n---------------------\nRoutine PSOSPMV in the RXLOOP tag, change the logic to look at the\ndispensing pharmacy state and the patient address state, and then look at \nthe SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS\n(#58.41) file to determine what state(s) the batch needs to be sent.\n3. INC19851935 - Export Batch Processing [PSO SPMP BATCH PROCESSING] \noption only displays ASAP version of the dispensing state\n \n4. INC21661107 - Manual Voids sent to state of dispensing pharmacy, not \npatient's home state\n \n \nPrescription Monitoring Program (SPMP) patch, PSO*7.0*630, was not working\nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview: \n \n1. INC19848427 - the Scheduled SPMP Data Export [PSO SPMP SCHEDULED\nEXPORT] option and CS Prescriptions Not Transmitted [PSO SPMP RX\nNOT TRANSMITTED] option are both gathering prescriptions for incorrect\ncorrectly for some of the SPMP options. This patch will resolve the\nstates.\n \nProblem:\n--------\nA single prescription can incorrectly be sent to multiple states. This \nhappens if the state being transmitted has a state IEN which is a single \ndigit, and the patient's home state has a state IEN that contains that \ntransmitting state's IEN. This will affect both the transmission for the \nprevious day (including return to stock) and the 30 day look back.\n \nfollowing SPMP issues:\nResolution:\n-----------\nFix the logic for the Scheduled SPMP Data Export [PSO SPMP SCHEDULED\nEXPORT] option and CS Prescriptions Not Transmitted [PSO SPMP RX NOT\nTRANSMITTED] option to look at the dispensing pharmacy state and the\npatient state, and then look at the SEND EXPORT STATE PARAMETER (#21) \nfield in the SPMP STATE PARAMETERS (#58.41) file to determine what\nstate(s) the batch needs to be sent.\n \nTechnical Resolution:\n \n---------------------\nRoutine PSOSPMU1 in the GATHER tag, change the contains from "'[STATE" to\n"'[("^"_STATE_"^")" when checking for the STATE variable. This will fix\nthe issue with the prescriptions being sent to incorrect states.\n \n2. INC19848615 - the View/Export Single Prescription [PSO SPMP SINGLE RX\nVIEW/EXPORT] option only transmits to the dispensing pharmacy's state.\n \nProblem:\n--------\n1. INC19848427 - The same RX fills are being transmitted in multiple \nPatch PSO*7.0*630 added functionality to allow Meds By Mail to transmit \ncontrol substance prescriptions to the SPMP state of the patient's \ngeographic state. However, when using View/Export Single Prescription \n[PSO SPMP SINGLE RX VIEW/EXPORT] option\nto send a single RX, it will only send to the state of the dispensing \npharmacy and cannot be changed to transmit to the patient's geographical \nstate.\n \nResolution:\n-----------\nbatches and also to states not associated with the patient or dispensing \nFix the logic for the View/Export Single Prescription [PSO SPMP SINGLE RX\nVIEW/EXPORT] option to look at the dispensing pharmacy state and the\npatient state, and then look at the SEND EXPORT STATE PARAMETER (#21) \nfield in the SPMP STATE PARAMETERS (#58.41) file to determine what\nstate(s) the batch needs to be sent.\n \nTechnical Resolution:\n---------------------\nRoutine PSOSPML4 in the EXPORT tag, look at the dispensing pharmacy state\nand the patient state, and then look at the SEND EXPORT STATE PARAMETER \npharmacy\n(#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what\nstate(s) the batch needs to be sent.\n \n3. INC19851935 - the Export Batch Processing [PSO SPMP BATCH PROCESSING] \noption reverts to dispensing pharmacy's state.\n \nProblem:\n--------\nPatch PSO*7.0*630 added functionality to allow Meds By Mail to transmit \ncontrol substance prescriptions to the SPMP state of the patient's \n \ngeographic state. However, when using Export Batch Processing [PSO SPMP \nBATCH PROCESSING] option to view transmissions for states other than the \ndispensing pharmacy's state, then the prescription details will display \nthe ASAP version for the dispensing pharmacy's state. As the user backs \nout of the option, the state changes away from what the state the user \ninitially picked and instead changes to the dispensing pharmacy's state.\n \nResolution:\n-----------\nFix the logic for the Export Batch Processing [PSO SPMP BATCH PROCESSING]\n\n\nSee the patch description for PSO*7.0*684\n\n
\nThis patch will address the following issue: \n \nProblem:\n-------\nMeds-By-Mail (MbM) reported that electronic prescriptions (eRx) are received\nseveral hours after the outside prescriber transmitted them. The problem seems\nto be caused by a increasing traffic handled by the eRx Hub which centralizes\nall nationwide incoming eRx prescriptions into the VA. One part of the \nprocessing by the eRx Hub is the auto-matching of patient, provider and drug.\nIn other words, the eRx Hub tries to pre-emptively find a VistA corresponding\nfor these three fields before forwarding the incoming prescription to the\n \nVistA site. The auto-matching for the provider and drug is accomplished by the\neRx Hub through two VistALink calls (one for the provider and one for the\ndrug) to the VistA site and if a match is found at the VistA site it returns\nthe IENs (Internal Entry Number) back to the eRx Hub which in turn records the\nsuccess/failure for an auto-match statistics reporting purpose and then sends\nthe matched IENs back to the VistA site along with the complete eRx\nprescription. Although not 100% confirmed, the suspicion is that such calls to\nVistA have become quite costly as the volume of incoming eRx increased\ndrastically in the past few months and are likely to be partially responsible\nfor the processing delays.\n1. INC23078077 - Delayed delivery of electronic doctor orders through VHA\n \nResolution:\n-------------\nThe solution to this problem is two-fold:\n \n 1) A change is being made in VistA through this patch to the processing of\n the incoming eRx to check if the eRx Hub provider and drug auto-matches\n were successful or not ("fail"). If not, using the incoming data from the\n outside prescriber VistA will utilize the exact same VistA code currently\n used by the eRx Hub to try to auto-match these locally and if it succeeds\n Inbound eRx hub\n it will auto populate VistA Provider and/or VistA Drug fields.\n \n 2) Once the this patch has been released and installed nationally at every\n VistA site an update will then be made at the eRx Hub to shut off the\n auto-match processing for provider and drug. This will consist of\n stopping the two VistALink calls made to the VistA site and always\n sending to VistA a "fail" result with a "Auto-match not performed"\n reason.\n \nTechnical Resolution:\n \n--------------------\nA new routine (PSOERUT) was created to parse an XML message into a local array\nand code was added to INCERX+29^PSOERXI1 and INCERX+48^PSOERXI1 to call the\nnew API XML2GBL in the new routine to parse the incoming XML message, retrieve\nthe provider and drug information and call the same code the eRx Hub was\ncalling (via RPC calls) to perform the auto-match for provider and drug\n(PRVMTCH^PSOERXA0 and DRGMTCH^PSOERXA0). Furthermore, it was determined that\nthe array variable (PSODRUG("IEN")) used at CSID+9^PSOUTL, used to check if\na drug is a controlled substance or not was wrong and was replaced with\nDRGIEN.\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC23078077 - Delayed delivery of electronic doctor orders through VHA\n Inbound eRx hub\n\n\nPlease refer to the patch description for contents and detailed \ninformation.\n\n
\nSee FORUM patch description.\n\n
\nThis patch will resolve the following issues:\n \nThe Rx reference of an original fill that is displayed on an activity log \nrecord is incorrect when the CMOP host site reports a change in the Rx's \nNational Drug Code (NDC). This occurs when the Rx has a suspended refill \nand the original fill's fill date is changed. \n \nThis patch will also fix a <SUBSCRIPT> error caused by the code of the\noriginal patch PSO*7*638 that was created to fix the original issue.\n\n
\nThis patch will address the following issue: \n \nProblem:\n-------\nPatch PSO*7*706 was released on September 21st, 2022 to address this issue.\nHowever, an issue was discovered with the logic to auto-match Prescriber and\nDrug in VistA once the eRx XML message is received from the eRx Hub.\n \nResolution:\n-------------\nThis patch corrects the auto-match VistA algorithm to addresses this issue.\n \n \nTechnical Resolution:\n--------------------\nPatch PSO*7*706 assumed that the XML parameter in the PSOERXI1 INCERX RPC\nBroker call (responsible for processing incoming eRx from the eRx Hub)\ncontained the entire eRx XML record. However, during tests with the updated\neRx Hub it turned out that the incoming XML message is fragmented in 3 \nparameters: XML, XML2 and XML3. Information about Prescriber and Drug seems\nto be sent on XML2 and that's why the logic in PSO*7*706 failed. This patch\nnow checks the parsed information stored in the ^TMP($J,"PSOERXO1") global,\n1. INC23078077 - Delayed delivery of electronic doctor orders through VHA\nwhich is supposed to contain the complete incoming XML information from XML,\nXML2 and XML3.\n Inbound eRx hub\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC23078077 - Delayed delivery of electronic doctor orders through VHA\n Inbound eRx hub\n\n
\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC22865486 - This patch will address the issue described in \nServiceNow Incident INC22865486, regarding the <UNDEFINED>ACLOG+5^PSON52 \nerror when converting a Titration RX to a Maintenance RX. In addition, \nThis patch will resolve the following issue:\nthis patch will resolve the incorrect RX reference in the remarks field.\n \n \nProblem 1: \n---------\nIf a patient has an active titration RX and a pending controlled substance\nRX from CPRS, and the patient's orders are finished via COMPLETE ORDERS\nFROM OERR option [PSO LMOE FINISH]. If the primary filter "CS" controlled\nsubstances is used, and the pharmacist first converts the Titration\nprescription to a Maintenance order. After accepting the order, a hard\n \nerror occurs: <UNDEFINED>ACLOG+5^PSON52 *PSOCSP("NAME"). In addition,\nthe remarks field for the renewed titration corrrectly refers to the\nMaintenance RX, but incorrectly refers to the CPRS controlled substance RX\nas being edited.\n \n \nResolution 1:\n------------\nIt was discovered that when the user selects the "CS" controlled \nsubstances as the primary filter when finishing a patient's\n1) INC22865486 - This patch will address the issue described in \norders via COMPLETE ORDERS FROM OERR option [PSO LMOE FINISH],\nthe logic pulls the data for any pending controlled substances for the\npatient selected. This causes the data to be set to the pending CS, even\nif the pharmacist chooses a non-controlled substance, in this case the\nTitration RX. Most of the variables are newed in the logic, except for\nthe OR0 variable which is not cleared out when the CS RX is not\nselected. This is the reason for the <UNDEFINED>ACLOG+5^PSON52 \n*PSOCSP("NAME") error, and why the remarks contains the CS data.\nThis fix for this issue is to new the OR0 variable in the SEL\nand NEWSEL tags of PSOORNE2.\nServiceNow Incident INC22865486, regarding the <UNDEFINED>ACLOG+5^PSON52 \nerror when converting a Titration RX to a Maintenance RX. In addition, \nthis patch will resolve the incorrect RX reference in the remarks field.\n \n \n\n\n1) When discontinuing a prescription entered through Computerized Patient\n"YES". This error was introduced by patch PSO*7*56. Routine PSODRDU1 was\nmodified to correct multiple issues, with some of the redundant code\nremoved. This patch fixes this problem.\nRecord System (CPRS), if an up-arrow is entered at the "Nature of Order:"\ndialog and if the default entries are accepted for the remainder of the\ndialogs without entering an up-arrow, the discontinue process errors out.\nThis patch corrects this problem.\n \n2) When renewing orders entered through CPRS or backdoor, the duplicate\ndrug check against other pending refill orders was found to error out if\nthe entry to the dialog "Discontinue Pending Order?" was entered as\n\n
\nVSE-2687 VistA: Modify PSO VCC REFILL rpc to support REFILL SOURCE input \nREMOTE PROCEDURES\n=================\nPSO VCC REFILL\nparameter.\n \nROUTINES\n========\nPSOATRFV\nPSOVCCA\nPSO679P\n \n\n
\nThis patch corrects two issues identified after the installation of \nThe Spanish Sig label layout should be the same as the English Sig label \nlayout.\nCPRS32B regarding the printing of the Sig label in Spanish.\n \n1. When the user selects 'No' to Copy INDICATION into the Sig? the \nSpanish label continues to print out the Indication on the Spanish Sig \nlabel.\n \n2. When the user selects 'Yes' to Copy INDICATION into the Sig? the \nIndication is printed after the Patient Instructions instead of before. \n\n
\nThis patch will resolve the following issue:\n \nTwo sites have reported separate incidents where the release date and \ntime of an Rx's CMOP event are being overwritten when a reprint of a \nrefill is executed locally. Since the refill's reprint is executed \nlocally the CMOP event's released date and time should not change.\n\n
\nThis patch will address the following issues: \n \nbeginning of a Pending Order or an Active prescription. This problem happens\nonly for incoming eRx records where the SSN contains '-' (dashes).\n \nResolution:\n-----------\nThe size of the eRx field SSN was expanded to display the entire SSN when it\ncontains '-'. \n \nTechnical Resolution:\n---------------------\n4. INC19419044 - Acknowledge option deficiency within RxRenewal and RxChange\nThe size of the field SSN was changed from 15 to 20 in the line of code at\nDERX1+72^PSOERXU1, which should accommodate an SSN with '-' in it.\n \n4. INC19419044 - Acknowledge option deficiency within RxRenewal and RxChange\n Request and Response messages\nProblem:\n--------\nMeds-by-Mail (MbM) reported that users were able to choose the ACK\n(Acknowledge) action multiple times on the same record, which in some cases\nwould trigger a 'Verify' message to be sent back to the eRx prescriber\n Request and Response messages\nmultiple times.\n \nResolution:\n-----------\nA change was made to the ACK action to block the execution if the eRx record\nis in one of the following status (already acknowledged):\n \n CAA CANCEL REQUEST ACKNOWLEDGED\n CXA RXCHANGE RESPONSE ACKNOWLEDGED\n ICA INBOUND RXCHANGE ERROR ACKNOWLEDGED\n \n IEA INBOUND ERROR ACKNOWLEDGED\n IRA INBOUND RXRENEWAL ERROR ACKNOWLEDGED\n RXA RXRENEWAL RESPONSE ACKNOWLEDGED\n \nThe following message will be displayed if the user now tries to acknowledge\nan eRx record twice: \n \n Record already acknowledged!\n \n Type <Enter> to continue or '^' to exit: \n5. INC19287772 - HAC VistA eRx 4.0 sorting issue\n \nTechnical Resolution:\n---------------------\nAdded the line of code below at CANACK+7^PSOERXU5:\n \n I ",CAA,CXA,ICA,IEA,IRA,RXA,"[ERXSTAT W !!,"Record already acknowledged!"\n ,!,$C(7) D DIRE^PSOERXX1 Q\n \n5. INC19287772 - HAC VistA eRx 4.0 sorting issue\n \n \nProblem:\n-------\nMeds-by-Mail (MbM) reported that the SO (SORT ENTRIES) action did not work\nafter selecting a patient and trying to sort by drug name. After selecting to\nsort by drug name the software lost previous patient selection and would \ndisplay all patients on the list.\n \nResolution:\n-------------\nChanged the software to preserve the previously selected patient after the\n6. INC19647182 - Refill 6 shows as Partial in ECME log\nuser selects to sort the patient's records by a different sort criteria (e.g.,\ndrug name).\n \nTechnical Resolution:\n--------------------\nAdded the line of code below at SORT+10^PSOERX:\n \n I $D(SRCH) D EN(.SRCH,STYP,1) Q\n \n6. INC19647182 - Refill 6 shows as Partial in ECME log\n \n \nProblem:\n--------\nThe Marion VA Medical Center (IL) reported that entries in the ECME Log \nrelated to Refill #6 displayed in Patient Prescription Processing [PSO LM\nBACKDOOR ORDERS] option wrongly showed as 'PARTIAL' fills (Rx Ref column).\n \nResolution:\n------------\nCorrect the display of the entry for Refill #6 to show as 'REFILL #6' instead\n7. INC20086630 - Pharmacists are blocked from editing conjunction and duration\nof 'PARTIAL' in the under the Rx Ref column in the ECME Log.\n \nTechnical Resolution:\n---------------------\nMove the code for the Output Transform for the RX REFERENCE field (#.04) in\nthe ACTIVITY LOG (#52.3) sub-file in the PRESCRIPTION file (#52) to \nALFILNUM^PSOUTLA and included an exception for ECME entries to not interpret\nvalue 6 as a PARTIAL fill.\n \n7. INC20086630 - Pharmacists are blocked from editing conjunction and duration\n prompts for complex orders on eRx holding queue screen\n prompts for complex orders on eRx holding queue screen\n \nProblem:\n-------\nThere is no functionality in the eRx Holding Queue (Complete Orders from eRx\nPSO ERX FINISH]) to allow the user to create a complex order dosage. This \ncreates a problem particular for processing Controlled Substance (CS) Complex\neRx prescriptions because they cannot be edited on the Pharmacy Backdoor\nPending Queue or even after they become an Active prescription because of the\nrestrictions for editing CS prescription. The receiving of CS eRx prescription\n \n \nhave been recently enabled by PSO*7*617, which did not include this\nfunctionality. Furthermore, when entering the dosage information for an eRx in\nthe eRx Holding queue the user is not automatically presented with a default\nvalue for the ROUTE field. This requires the pharmacist to always type and\nchose the appropriate medication route for the dispense drug selected which\nmay lead to a mistake that could be easily mitigated by the addition of a\ndefault value.\n \nResolution:\n-------------\n8. INC20420672 - Audit Log (AU) option in eRx holding queue fails to capture\nThis patch adds the ability for the user to create a Complex dosage for any\nprescription in the eRx Holding Queue option [PSO ERX FINISH]. When entering\na dosage information the users will be prompt with two new fields: LIMITED \nDURATION and CONJUNCTION after the Schedule Prompt:\n \n ...\n Schedule: QD// \n Now searching ADMINISTRATION SCHEDULE (#51.1) file...\n QD EVERY DAY\n ...OK? Yes// (Yes)\n original eRx SIG\n LIMITED DURATION (IN DAYS, HOURS OR MINUTES): 10 (DAYS)\n CONJUNCTION: THEN\n \n There are 2 Available Dosage(s):\n 1. 15MG\n 2. 30MG\n ...\n \nSelect from list of Available Dosages (1-1), Enter Free Text Dose\nor Enter a Question Mark (?) to view list: 7.5// \n \nAn addition functionality was added to provide a default value for the ROUTE\nprompt to assist the user in selecting the appropriate medication route for\nthe medication on the prescription while reducing the chance for \nadministration errors by the patient.\n \nTechnical Resolution:\n---------------------\nComplex Order: \n The routine PSOERXD2 was changed to add two new fields: LIMITED DURATION\n (line tag DUR) and CONJUNCTION (line tag CON). Data dictionary fields\n9. INC20842304 - EPCS software detox# validation capability fails\n already existed to accommodate complex dosages so no new DD fields were\n necessary to be created.\nDefault Med Route:\n A new function called DEFROUTE that returns a default medication route for \n an specific Orderable Item was added to the routine PSOERXUT and a call to\n this function was added to RTE2^PSOERXD2. If the function returns a value\n and there is no previous value entered for the ROUTE the returned value is\n used as the default value for the ROUTE field.\n \n8. INC20420672 - Audit Log (AU) option in eRx holding queue fails to capture\n \n original eRx SIG\nProblem:\n--------\nMeds-by-Mail (MbM) reported that the AU (Audit Log) action did not show the\neRx value for the SIG field after the SH (Show/Hide eRx Value) action was\nselected.\n \nResolution:\n------------\nThe Audit Log functionality introduced by the patch PSO*7*617 did not take\n10.INC20591567 - RxRenewalRequest messages are blocked at hub due to missing\ninto account that after the patch PSO*7*581 was released to upgrade the NCPDP\nversion from 10.6 to 2017 the SIG was stored in a different field. The code\nwas changed to first check the NCPDP version for the record and then retrieve\nthe eRx SIG information from the correct field.\n \nTechnical Resolution:\n---------------------\nFor eRx records with NCPDP version 10.6 (received before PSO*7*581) the eRx\nSIG is stored in the DIRECTIONS field (#7) in the ERX HOLDING QUEUE file\n(#52.49). For eRx records with NCPDP version 2017 (received after PSO*7*581)\n Pharmacy Data\nthe eRx SIG is stored in the SIG TEXT field (#8) within the 2017 MEDICATIONS\nsub-file (#52.49311) in the ERX HOLDING QUEUE file (#52.49). A new API \n$$ERXSIG was added to the PSOERXUT routine to return the eRx SIG. It will\ncheck whether the eRx record is NCPDP version 2017 by checking the\nfield SCRIPT VERSION NUMBER (#312.1). If so, it will retrieve the value from\nthe SIG TEXT field (#8) otherwise it will retrieve it from the DIRECTIONS\nfield (#7). Then, the routine PSOERXAU was changed to use this new API \ninstead of retrieving it from the DIRECTIONS field (#7).\n \n9. INC20842304 - EPCS software detox# validation capability fails\n \n \nProblem:\n--------\nCentral Texas VAMC reported a problem when trying to validate the provider\nfor an eRx prescription for BUPRENORPHINE (Detox Drug). Although the VistA \nprovider had a valid DETOX # on file (e.g., VX1234567) the user got the\nmessage below:\n \n VistA Provider XXXXX,XXXXXXXX X does not have a valid DETOX #.\n \n11.INC20591582 - RxRenewalRequest blocked at VA routing hub due to missing\nIt was determined that the software was checking for "X" as the first letter\non the DETOX # in order to consider it valid, which is incorrect. This issue\naffected also other actions for internal VA outpatient prescriptions. If the\nuser tried copy or renew a VA prescription for BUPRENORPHINE and the VA\nProvider did not have a Detox # that started with an "X".\n \nResolution:\n------------\nThe DETOX # validation code was changed to remove the requirement for the \nfirst letter to be an "X". It will now only look for 2 letters followed by\n1. INC19910756 - Duplicated entries of drug code number in VistA NDC file\n Observation \na 7-digit number.\n \nTechnical Resolution:\n---------------------\nThe validation code at PRVDETOX+4^PSOUTIL, PRDRVAL+43^PSOERXUT and \nPRDRVAL+94^PSOERXUT were changed from ...?1"X"1A7N... to ...?2A7N...\n \n10.INC20591567 - RxRenewalRequest messages are blocked at hub due to missing\n Pharmacy Data\nProblem:\n \n--------\nMeds-by-Mail (MbM) reported that outbound Renewal or Change Request messages\nwere being dropped by the eRx Hub because they were missing the Pharmacy\naddress and/or the communication number. A sample XML message from the Hub\nconfirmed that the Pharmacy address was missing, as seen below:\n ...\n <Pharmacy>\n <Identification>\n <NCPDPID>5204437</NCPDPID>\n <NPI>1538421110</NPI>\n12.INC20730418 - Non-Controlled Substance eRx was blocked from being edited by\n </Identification>\n <BusinessName>MEDS BY MAIL CHAMPVA</BusinessName>\n <Address>\n <CountryCode>US</CountryCode>\n </Address>\n <<< <CommunicationNumbers> segment was missing here\n </Pharmacy>\n ...\n \nResolution:\n Electronic Prescribing for Controlled Substance mechanism\n------------\nWhen the new NCPDP version (2017) was implemented by patch PSO*7*581 it did\nnot keep existing 'failsafe's' mechanism from 10.6 version at the time the\nuser requested a Change or Renewal Request to the outside provider. One of\nthem retrieved address information from the OUTPATIENT SITE file (#59) in\ncase the ERX EXTERNAL PHARMACY file (#52.47) record did not contain a valid\naddress. The other one was to send "0000000000" as a Primary Telefone number\nif one could not be found for the pharmacy. This patch adds these\n'failsafe's' for NCPDP v2017 eRx records.\n \n \nTechnical Resolution:\n--------------------- \nAddress\n-------\nNew code was added at OPHARM+31^PSOERXOD to check if the ADDRESS LINE 1 field\nin the ERX EXTERNAL PHARMACY file (#52.47) for the eRx record being renewed/\nchanged was blank. If so, it will retrieve the complete address from the \ncorresponding pharmacy record in the OUTPATIENT SITE file (#59).\n \nCommunication Number\n13.INC21240944 - received eRX type CS for non-CS drug\n--------------------\nNew code was added at OCOMM+3^PSOERXOU to make sure that the \n<CommunicationNubmers> XML segment is always included in the outbound eRx \nRenewal or Change request messages. \n \n11.INC20591582 - RxRenewalRequest blocked at VA routing hub due to missing\n Observation \nProblem:\n--------\nMeds-by-Mail (MbM) reported that outbound Renewal or Change Request messages\n \nwere being dropped by the eRx Hub because the Observation/Measurement segment\ndid not contain the required <ObservationDate> field. A sample XML message\nfrom the Hub confirmed that the problem, as seen below:\n \n <Observation>\n <Measurement>\n <VitalSign>29463-7</VitalSign>\n <LOINCVersion>2.42</LOINCVersion>\n <Value>178.4</Value>\n <UnitOfMeasure>[lb_av]</UnitOfMeasure>\n14.INC22031884 - eRx pending order screen does not display original\n <UCUMVersion>1.8.2</UCUMVersion>\n <<< <ObservationDate> segment was missing here\n </Measurement>\n </Observation>\n \nResolution:\n------------\nFor an unknown reason some incoming Observation/Measurement records saved to\nthe 2017 OBSERVATION sub-file (#52.49306) in the ERX HOLDING QUEUE file\n(#52.49) failed to save a valid date in the OBSERVATION DATE field (#6). Since\n physician's instruction and relevant drug dose strength\nit cannot be determined the cause of the incomplete Observation/Measurement\ninformation stored it was decided to not include such information in the\nChange or Renewal request messages if the Observation Date value is not\npopulated.\n \nTechnical Resolution:\n--------------------- \nNew code was added at OBSERVE+2^PSOERXOB to make sure that the in order for\nand Observation/Measurement to be included in the outbound eRx Renewal or \nChange request it must have a valid Observation Date value, otherwise it is\n \nskipped. \n \n12.INC20730418 - Non-Controlled Substance eRx was blocked from being edited by\n Electronic Prescribing for Controlled Substance mechanism\n \nProblem:\n--------\nMeds-by-Mail (MbM) reported that the users were unable to edit a Digitally\nSigned eRx Pending Order record even if the drug selected for the prescription\nis not marked as a Controlled Substance (non-CS). When the CS eRx Project was\n caused erroneous drug auto-match\nDefect Tracking System Ticket(s) & Overview:\nreleased with patch PSO*7*617 it included functionality to prevent any\nfield in a CS eRx Pending Order record from being edited before the order was\nfinished. The reason is because DEA (Drug Enforcement Agency) requires all\nPharmacy software applications to audit all edits to a CS prescription record\nand the Pending Queue edits are not audited. However, a few incoming Digitally\nSigned eRx records will be matched with a dispense drug that is not considered\nto be a Controlled Substance by the VA and in such cases the edit should be \npermitted.\n \nResolution:\n--------------------------------------------\n------------\nInstead of checking whether the eRx record was digitally signed or not to\ndetermine if the eRx Pending Order record can be edited or not the software\nwill now check if the dispense drug in the Pending Order is marked as a CS or\nnon-CS. If the drug is not marked as CS the editing of the eRx Pending Order\nrecord will be allowed. In addition, the messages "Processing Digitally\nSigned eRx Order" displayed at the top of the Pending eRx as well as the DEA\nnote (see below) at the end of the order will not display the dispense drug in\nthe Pending Order is not marked as CS.\n \n1. INC19910756 - Duplicated entries of drug code number in VistA NDC file\n This prescription meets the requirements of the Drug Enforcement \n Administration (DEA) electronic prescribing for controlled substances rules\n (21 CFR Parts 1300, 1304, 1306, & 1311).\n \nTechnical Resolution:\n--------------------- \nThe code at CSERX+1^PSOORNEW was changed from checking whether the CONTROLLED\nSUBSTANCE INDICATOR field (#95.1) in the ERX HOLDING QUEUE file (#52.49) was\nset to check if the dispense drug associated with the Pending order is marked\nas CS by calling the local $$CSDRG API. In addition, the line tag DERX1+66 in\n caused erroneous drug auto-match\nthe PSOERXU1 routine was changed to add a check if the dispense drug is marked\nas CS before setting the variable PKIE with the message that the eRx was \ndigitally signed. And the code at PST+48 in the routine PSOORFI1 was also\nmodified not display the DEA message above unless the drug is marked as CS.\n \n13.INC21240944 - received eRX type CS for non-CS drug\n \nProblem:\n--------\nWest Palm Beach VA Medical Center (FL) reported that the users were unable to\nProblem:\naccept a Digitally Signed eRx Pending Order record even if the drug selected\nfor the prescription is not marked as a Controlled Substance (non-CS). When\nthe CS eRx Project was released with patch PSO*7*617 it assumed that a\ndigitally signed order would certainly translate into a CS VistA prescription.\nHowever, in some cases, digitally signed prescription are for medications not\nconsidered by the VA to be controlled substance. A good example is GABAPENTIN\nmedication, which in some states is classified as a controlled substance but\nnot by the Drug Enforcement Agency (DEA). So, a prescriber in such states will\ndigitally sign prescriptions before transmitting prescriptions for this\nmedication to the VA however the VA will not process such eRx prescriptions as\n--------\ncontrolled substances. Therefore it will not require that the VistA provider\nassigned to the eRx prescription has a valid DEA# on file.\n \nResolution:\n------------\nInstead of checking whether the eRx record was digitally signed or not to\ndetermine if the eRx can be accepted the software will now check if the\ndispense drug associated with the eRx order is marked as a CS or non-CS.\nIf the drug is not marked as CS the accepting of the eRx order will be \npermitted even though the provider does not have a valid DEA# on file. A\nMeds-by-Mail (MbM) encountered a problem with eRx auto-matching functionality\nwarning message will still be displayed.\n \nTechnical Resolution:\n--------------------- \nThe code at PRDRVAL+49^PSOERXUT was changed to check solely whether the VistA\ndrug selected for the prescription is marked as CS or not. If not marked as CS\nand the Accept functionality will only warn the user about not assigning a CS\ndrug to a digitally signed order but it will not block them from proceeding.\n \n14.INC22031884 - eRx pending order screen does not display original\nperformed by the eRx Hub web-application. For the incoming NDC 000185060510\n physician's instruction and relevant drug dose strength\n \nMeds-by-Mail (MbM) reported that the users were unable to view the eRx SIG\nin the "Instructions" field (above the VistA SIG) while processing a pending\norder. Furthermore, they requested that the eRx Drug is also displayed in the\nline above the "Instructions" field. This change would only impact eRx pending\norders.\n \nResolution:\n------------\nthe software was wrongly auto-matching to CHLORDIAZEPOXIDE HCL 5MG CAP and\nIn order to address this issue the software was changed to save the eRx SIG\nin the PROVIDER COMMENTS field (#9) in the PENDING ORDERS file (#52.41) when\nthe record is crated after the eRx is accepted. In Addition, when displaying\nthe "Instructions" field for eRx pending order the field will now be \ndisplayed as "eRx Instructions" and the a new field called "eRx Drug" will be\nadded above this "eRx Instructions" field and it will display the original\neRx drug name that was sent it by the outside provider software.\n \nTechnical Resolution:\n--------------------- \npre-populating the matched VistA Drug for the incoming eRx record.\nReplaced the code at ADD+67^PSOERX1F to use the eRx SIG information in the\nfield mentioned above. Additionally, changed the routines PSOORFI1 (PST+5)\nand PSOORNEW (PT+4) to add the word "eRx" in front of "Instructions" field\nfor eRx originated Pending orders. Also, added a line above for such orders\nto display the actual eRx Drug sent in by the outside prescriber.\n \n \nResolution:\n-----------\nThe eRx dispense drug auto-matching functionality was changed to skip Inactive \nNDC/UPN entries while trying to match the eRx incoming NDC with an existing\nVistA dispense drug.\n \nTechnical Resolution:\n---------------------\nThe existing code at DRGMTCH+29^PSOERXA0 was reading the first NDC/UPN entry\n2. INC17880583 - Pharmacist cannot process e-prescribers' RXRENEWALRESPONSE\nthat matched the incoming NDC to find a match in the DRUG file (#50) without\nchecking whether the entry was Inactive or not. The code was changed to loop\nthrough all the entries in the "NDC" cross-reference in the NDC/UPN file \n(#50.67), skipping Inactive entries, until it can find a unique match to a\ndispense drug. If more than one possible match is found then it will not\nauto-match the dispense drug.\n \n2. INC17880583 - Pharmacist cannot process e-prescribers' RXRENEWALRESPONSE\n \nProblem:\n \n--------\nMeds-by-Mail (MbM) reported a problem with certain incoming RxRenewalResponse\nrecords that were assigned an RXN (RXRENEWAL RESPONSE - NEW) status but could\nnot be processed because they did not have a corresponding eRx record. This \ncaused this records to remain on their 'to-do' eRx Queue until they 'aged out'.\nThe ACK (Acknowledge) action is not available for such records. MbM referred\nto such records as 'orphaned' records.\n \nResolution:\n-----------\n3. INC19246636 - eRx SSN gets truncated on vistA screen (OERR and pharmacy \nThe processing of incoming eRx records was changed to automatically assign a\nstatus of RXF (RXRENEWAL RESPONSE FAILED) to records without a corresponding\neRx record. In addition it automatically adds the following comment to the\nStatus History for the 'orphaned' record: Response received was 'Denied' -\nNo corresponding eRx Record found.\n \nTechnical Resolution:\n---------------------\nIntroduced new code at REFRESP+20^PSOERXA5 to check whether the incoming eRx\nresponse record has a corresponding eRx record. If not, the status of the\n backdoor)\nincoming response record will be changed to RXF and a comment will be logged\nto Status History log.\n \n3. INC19246636 - eRx SSN gets truncated on vistA screen (OERR and pharmacy \n backdoor)\nProblem:\n--------\nMeds-by-Mail (MbM) reported a problem with the patient SSN (Social Security\nNumber) last digit being truncated in the Patient Prescription Processing [PSO\nLM BACKDOOR] option. The problem is with in the eRx information listed at the\n\n
\nDefect Tracking System Ticket(s) & Overview:\nprescriptions with a status of DISCONTINUED BY PROVIDER. Renewing a \nprescription with this status is not allowed when renewing for a single \nRX selected from the Medication Profile or when doing Barcode Batch \nPrescription Entry.\n \n Resolution:\n ----------\nRoutine PSORENW4 is modified to check if any RXs selected \nfor speed renew are discontinued. If any are they are removed from list \nof RXs to renew and the message 'Cannot renew Rx # #######, Rx is in \n===========================================\nDISCONTINUED BY PROVIDER status.' is displayed.\n \n Technical Resolution:\n --------------------\n ;PSO 683 skip discontinued by provider RXs\n S (ORD,PSOLCNT)=0\n I $G(LST)]"" D\n . ; count remaining orders in LST\n . F ORD=1:1:$L(LST,",")-1 D\n .. Q:$P(LST,",",ORD)'>0\n \n .. S PSOLCNT=PSOLCNT+1,ORN=$P(LST,",",ORD)\n .. I (+PSOLST(ORN)=52&(^PSRX($P(PSOLST(ORN),U,2),"STA")=14)) D\n ... S \nPSOSKIP($P(PSOLST(ORN),U,2))="",$P(LST,",",ORD)=0,PSOLCNT=PSOLCNT-1 ; \norder removed from LST\n .I $O(PSOSKIP(0)) D\n .. W !\n .. S ORD=0 F S ORD=$O(PSOSKIP(ORD)) Q:'ORD D\n ... S PSOSTA=$$GET1^DIQ(52,ORD,100)\n ... W $C(7),!," Cannot renew Rx # "_$$GET1^DIQ(52,ORD,.01)_", Rx is in \n1. INC21813625 - OUTPATIENT PHARMACY SPEED RENEW OF RX STATUS \n"_PSOSTA_" status."\n .. D PAUSE^VALM1\n ;END PSO 683\nDISCONTINUED BY PROVIDER\n \n Problem:\n -------\nSpeed renew allows an outpatient prescription to be renewed for \n\n
\n1. INC22631577 - ISSUES REFILLING PRESCRIPTIONS\nprinted instead of the fill entered. The ECME Log correctly shows the \nfill. If the prescription drug is a controlled substance, the refill \ncannot be released from the vault until the label is reprinted. \n \n \n Resolution:\n ----------\nThe issue is due to the variable RXFL not getting updated with the \ncurrent fill number in routine PSOR52.\n \n \n Technical Resolution:\n --------------------\nAt line FINISH+36^SPOR52, the logic is modified to not jump to FINISHX \nbut to only execute the next two lines that prevent a duplicate label \nfrom being printed and allowing RXFL to be reset with the current fill \nnumber.\n \nLine FINISH+36^SPOR52 is changed from:\n I PSODUP G FINISHX\nTo:\n \n I 'PSODUP D\nAnd the next two lines are added into the Do dot structure:\n \n I 'PSODUP D ;p699\n . I $L(PSORX("PSOL",PSOX2))+$L(PSOX("IRXN"))<220 S \n PSORX("PSOL",PSOX2)=PSORX("PSOL",PSOX2)_PSOX("IRXN")_","\n . E S PSORX("PSOL",PSOX2+1)=PSOX("IRXN")_","\n S RXFL(PSOX("IRXN"))=PSOX("NUMBER")\n Problem:\n -------\nWhen a prescription is edited before it is refilled in Patient \nPrescription Processing, the label will print for the previous fill. The \nActivity Log incorrectly displays that the previous fill was sent to \nX-INTERFACE and the Label Log incorrectly displays the previous fill was \n\n\nThis patch will resolve the following issue:\n--------\nIf a patient has an active titration RX and a pending controlled \nsubstance RX from CPRS, and then a new order is placed for the patient\nvia COMPLETE ORDERS FROM OERR [PSO LMOE FINISH] option, a hard error can\noccur. After placing the new order and accepting, a hard error occurs:\n<UNDEFINED>ACLOG+5^PSON52 *PSOCSP("NAME"). In addition, the remarks field\nfor new order incorrectly refers to the CPRS controlled substance RX as\nbeing edited.\n \nResolution:\n \n-----------\nIt was discovered that when the user selects the "CS" controlled \nsubstances as the primary filter when finishing a patient's\norders via COMPLETE ORDERS FROM OERR [PSO LMOE FINISH] option,\nthe logic pulls the data for any pending controlled substances for the\npatient selected. This causes the data to be set to the pending \ncontrolled substance, even if the pharmacist chooses to place a new \norder. Most of the variables are newed in the logic except for the OR0\nvariable which is not cleared out when the a new order is placed. This is\nthe reason for the <UNDEFINED>ACLOG+5^PSON52 *PSOCSP("NAME") error and why\n1) INC24967678 - This patch will address the issue described in \nthe remarks contain the controlled substance data.\n \nTechnical Resolution:\n---------------------\nThe fix for this issue is to new the OR0 variable in the AGAIN tag of \nPSONEW.\nServiceNow Incident INC22865486, regarding the <UNDEFINED>ACLOG+5^PSON52 \nerror when creating a new order in the COMPLETE ORDERS FROM OERR \n[PSO LMOE FINISH] option. In addition, this patch will resolve the \nincorrect RX reference in the remarks field.\n \nProblem: \n\n\nDefect Tracking System Ticket(s) & Overview:\ninactive account in a local VistA system, VistA is picking the last \nprovider used on a previously finished prescription. This problem is not \nisolated to eRX processing. The same issue occurs if any pending \noutpatient order has a provider that is inactive or no longer authorized \nto write orders when it is finished in Patient Prescription Processing \n[PSO LM BACKDOOR ORDERS]. If a new order is entered in Patient \nPrescription Processing [PSO LM BACKDOOR ORDERS] prior to processing the \npending order that is for an inactive or invalid provider during the \nfinishing process a message displays indicating the provider is inactive \nor invalid and prompts for a new provider and populates the provider \n===========================================\nprompt with the provider from the new order. The prompt should default \nto the provider associated with the PENDING OUTPATIENT ORDERS FILE \n(#52.41).\n \n Resolution:\n ----------\nRoutine PSODIR is modified to use the provider from the PENDING \nOUTPATIENT ORDERS FILE (#52.41) as the default for the provider prompt \nand not allow it to be overwritten.\n \n \n \n Technical Resolution:\n --------------------\nThere is already code to set the default to the provider from the PENDING \nOUTPATIENT ORDERS FILE (#52.41) but when PSORX("PROVIDER NAME") exists it \noverwrites the default. PSORX("PROVIDER NAME") is set to the provider \nselected during entering a new order for defaulting when entering \nmultiple orders for the same patient.\n \nThe default is set from the PENDING OUTPATIENT ORDERS FILE (#52.41) \n1. INC21921117 - INBOUND ERX PENDING ORDER SELECTING WRONG PROVIDER\nPROVIDER field (#5) at line PROVEN+1^PSODIR: \nDIC("B")=$P(^VA(200,$P($G(OR0),"^",5),0),"^") and is not changed with \nthis patch. At line PROVEN+9^PSODIR, the default, DIC("B"), is \noverwritten by PSORX("PROVIDER NAME") if it exists: S:$G(PSORX("PROVIDER \nNAME"))]"" DIC("B")=PSORX("PROVIDER NAME"), this line is changed to:\nS DIC("B")=$S($G(DIC("B"))]"":DIC("B"),1:$G(PSORX("PROVIDER NAME")))\nThis change allows the default from the PENDING OUTPATIENT ORDERS FILE \n(#52.41) to be used while not affecting other processing that also uses \nPROVEN^PSODIR for prompting for the provider.\n \n Problem:\n -------\nOnce an eRX order is validated and moved to the PENDING OUTPATIENT ORDERS \nFILE (#52.41), in the finishing process, if a validated provider has an \n\n\nThis patch addresses the following issue:\ndisplay when matching them\n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. INC22708310 eRx - Requesting the formulary status of VistA drugs \ndisplay when matching them\n \n \n Problem:\n -------\neRx - Requesting the formulary status of VistA drugs display when \nFayetteville VA Medical Center (AR) s requesting non-Formulary identifier \nto show after auto drug match and a previous manual validation. This \ncould be a patient safety issue and is a cost issue. Non-formulary drugs \nare slipping through that probably should not. This would help efficiency \nwhile processing prescriptions from the inbound eRX queue.\n \n Resolution:\n ----------\nIn option Complete Orders from eRx [PSO ERX FINISH], on the second screen \nof the eRx Holding Queue Display and the second screen of PSO ERX DRUG \nmatching them\nVALIDATION, the non-Formulary identifier (***N/F***) is added to the \nright of the Vista Drug. In addition, when validating the drug/sig, the \nnon-Formulary identifier (***N/F***) will be added in two places; to the \nright of the drug on the prompts 'Current Vista Drug:' and 'You have \nselected:'. \n \n Technical Resolution:\n --------------------\nRoutine PSOERX1G is modified to display the non-Formulary identifier \n(***N/F***) on line DISPRX+4^PSOERX1G\n \n \n Before patch\n .S LINE=LINE+1 D SET^VALM10(LINE,"Vista Drug"_$S(DRMANVAL:"[v]",1:"")_": \n"_VADRG_" "_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3))\n After patch\n .S PSONF="" I $G(VADRGIEN) S \nPSONF=$S($P(^PSDRUG(VADRGIEN,0),"^",9):"***(N/F)***",1:"") ;p689\n .S LINE=LINE+1 D SET^VALM10(LINE,"Vista Drug"_$S(DRMANVAL:"[v]",1:"")_": \n"_VADRG_" "_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3)_PSONF)\n \nAssociated ticket(s):\nRoutine PSOERXD1 is modified to display the non-Formulary identifier \n(***N/F***) on line INIT+109^PSOERXD1\n \n Before the patch\n S LINE=LINE+1 D SET^VALM10(LINE," (1) Vista Drug: "_VADRG_" \n"_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3))\n After the patch\n S PSONF="" I $G(VADRGIEN) S \nPSONF=$S($P(^PSDRUG(VADRGIEN,0),"^",9):"***(N/F)***",1:"") ;p689\n S LINE=LINE+1 D SET^VALM10(LINE," (1) Vista Drug: "_VADRG_" \n=====================\n"_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3)_PSONF)\n \nRoutine PSOERXD2 is modified to display the non-Formulary identifier \n(***N/F***) on lines VDRG1+9^PSOERXD2 & VDRG1+23^PSOERXD2. \n \nVDRG1+9^PSOERXD2 \n Before the patch:\nI VAODRG W !,"Current Vista Drug: "_$$GET1^DIQ(50,VAODRG,.01,"E")_" \n"_$P($$VADRSCH^PSOERXUT(VAODRG),"^",3)\n After the patch\n \nI VAODRG W !,"Current Vista Drug: "_$$GET1^DIQ(50,VAODRG,.01,"E")_" \n"_$P($$VADRSCH^PSOERXUT(VAODRG),"^",3)_$S($P(^PSDRUG(VAODRG,0),"^",9):" \n ***(N/F)***",1:"")\n \nVDRG1+23^PSOERXD2\n Before the patch:\nW !!,"You have selected: "_$P(Y,U,2),!,"Would you like to use this\ndrug/supply?" S DIR(0)="YO" D ^DIR K DIR\n After the patch:\nW !!,"You have selected: "_$P(Y,U,2)_ )_$S($P(^PSDRUG(+Y,0),"^",9):" \n1. INC22708310 eRx - Requesting the formulary status of VistA drugs \n***(N/F)***",1:""),!,"Would you like to use this \ndrug/supply?" S DIR(0)="YO" D ^DIR K DIR\n\n
\n1. When using the Start Bingo Board Display [PSO BINGO START] option, to\nis not always being built into the DISPENSING INSTRUCTIONS field (#.01) of\nthe DISPENSING INSTRUCTIONS sub-file (#52.4124) of the PENDING OUTPATIENT\nORDERS file (#52.41) when the order comes to the OP package. This is the\ninformation that displays as the Possible SIG on the OP finish screen.\nThis patch resolves that problem.\n \n3. This patch fixes a problem when using the Label/Profile Monitor Reprint\n[PSO B] option, to reprint labels onto another printer. It was using the\ncontrol codes of the original printer instead of the selected printer.\nrestart a stopped bingo board, a task number is assigned by the Task\nManager to queue this task. The assigned task number is not being set in\nthe TASK # field (#15) of GROUP DISPLAY FILE (#59.3), for the selected\nbingo board display. This patch fixes this problem.\n \n2. When an order is transferred in Computerized Patient Record System\n(CPRS) from Inpatient Medications to Outpatient Pharmacy (OP), or a change\nis done on an OP order in CPRS, the Noun that is associated with the order\n\n
\n \nuse this field. In particular, this affects SPMP functionality. When file \n101.52 field 10 is null, this may cause the Vista SPMP transmissions to \nsubmit an incorrect DEA Number for the provider.\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nThis patch will resolve the following issue:\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nProblem:\n--------\n1) INC23385693 - It was discovered that when a provider's DEA number \nexpires on the same date as the issue/written date, field #10 DEA NUMBER\ncan be null in the Order DEA Archive file (#101.52). When this happens,\nthe SPMP transmission should still send the provider's DEA number, but\ninstead it will send either null or the Facility DEA# which is incorrect.\n \n \n \nResolution 1:\n-------------\nTo fix the issue for the SPMP transmission, the routine PSOASAP0 tag \nPRE02 will be modified to pass the issue/written date to the $$DEA^XUSER\ncall, so the provider's DEA number will be sent even though it expires on\nthe same day as the RX issue/written date.\n1) INC23385693 - Controlled substance eRx prescriptions can be finished \nin VistA on a day after the authorizing provider's DEA Number expires as \nlong as the Issue/Written Date of the eRX is before or equal to the \nprovider's DEA expiration date. This is by design. However, when this \nhappens, it causes field #10 DEA NUMBER to be null in the Order DEA \nArchive file (#101.52). This will have side effects in functionality that \n\n
\nDefect Tracking System Ticket(s) & Overview:\nassociated with it is not displaying the order check warning:\nEnhanced Order Checks cannot be performed for Orderable Item: \nXXXXXXXXXXXX Reason(s): No Dispense Drug found.\n \nThe order check warning is displayed for an inpatient order for the same \nOrderable Item.\n \nResolution:\n-----------\nNVATST^PSODDPRE is modified to initialize variable PSONVTFL to 0 instead \n \nof 1\n \nTechnical Resolution:\n---------------------\nNVATST+2^PSODDPRE is changed from S PSONVTFL=1 to S PSONVTFL=0\n1. INC25627893 - Enhanced Order Checks cannot be performed for \nOrderable Item: XXXXXXXXXX Reason(s): No Dispense Drug found.\n \n \nProblem:\n--------\nOutpatient prescription for an orderable item that has no active drugs \n\n
\nThis patch will resolve the following issues:\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nProblem:\n--------\n \n1) INC19851999 - This patch will address the issue described in \nServiceNow, regarding when the Scheduled SPMP Data Export is run [PSO SPMP\nSCHEDULED EXPORT], Zero Reports are only being generated to the \ndispensing pharmacy's state. Meds by Mail states are not receiving Zero \nReports.\n \n2) INC23242505 - This patch will address the issue described in \nServiceNow, regarding the use of the View/Export Void Prescriptions \noption [PSO SPMP VOID RX VIEW/EXPORT] for Meds by Mail states, the single \nRX void batch was sent to the state that is contained in the patient's \n1) INC19851999 - When the Scheduled SPMP Data Export is run [PSO SPMP \ncurrently active address on profile. If the patient moved or was using a \ntemporary address after the original batch was sent, the void may go to \nthe wrong state.\n \n \nResolution 1:\n-------------\nIt was discovered that when the Scheduled SPMP Data Export is run [PSO \nSPMP SCHEDULED EXPORT], Zero Reports are only generated for the \ndispensing pharmacy state. The Meds by Mail states are not receiving \nSCHEDULED EXPORT], Meds by Mail states are not receiving Zero Reports.\nZero Reports. This is due to Meds by Mail states not having an Outpatient \nSite (File #59) defined, since the medication was not dispensed from the \nstate. However, the Outpatient Site is required to pull the DEA# which \nis a required field for the State Prescription Monitoring Program. So a \nnew state parameter field will be added to the View/Edit SPMP State \nParameters option [PSO SPMP STATE PARAMETERS] with this patch (File \n#58.41 Field #22). The new state parameter, "ZERO REPORT DEFAULT \nDIVISION:", will only display for states that are set to Meds by Mail \n(i.e. Send Export State Parameter = 2 Send to state of Patient \nDelivery). The Meds by Mail states will be able to select a Meds by Mail \n \ndivision that points to the appropriate DEA number. Routine PSOSPMSP will \nbe modified to add the new state parameter. Routine PSOSPML0 will have a \nnew temp global to store all states that had prescriptions either \ndispensed or mailed to them.\n \nResolution 2:\n-------------\nIt was discovered that when the View/Export Void Prescriptions option \n[PSO SPMP VOID RX VIEW/EXPORT] was used for Meds by Mail states, the \nsingle RX void batch was sent to the state that is contained in the \n2) INC23242505 - When using the View/Export Void Prescriptions option \npatient's currently active address on profile. If the patient moved or \nwas using a temporary address after the original batch was sent, the void \nmay go to the wrong state. Logic will be added to the View/Export Void\nPrescriptions option [PSO SPMP VOID RX VIEW/EXPORT] and the Scheduled SPMP\nData Export option [PSO SPMP SCHEDULED EXPORT] for voids, to check what\nstate the original RX was sent and send the void to the same state.\nChanges were made to the RXLOOP tag of PSOSPMV routine and the addition \nof the VOIDST tag in the PSOSPMV routine. Changes were also made to the \nGATHER tag of the PSOSPMU1 routine.\n[PSO SPMP VOID RX VIEW/EXPORT] for Meds by Mail states, the single RX \nvoid batch was sent to the wrong state. \n \n\n
\nThis OneVA Enhancement Patch will provide the following enhancements:\n \n . No changes to the current external interface parameters or setup is \n required. The same parameter setup used for the sending of local \n prescriptions to the OPAI will be utilized.\n \n . New activity log entries have been created to provide an audit trail\n for OneVA refills and OneVA partial fills sent through the OPAI to an\n ADD for dispensing. These new entries can be viewed through the Patient\n Prescription Processing [PSO LM BACKDOOR ORDERS] and View Prescriptions\n [PSO VIEW] options.\n \n \n . Enhancements to current activity log entries have been made to document\n the facility name and station number where the OneVA refill/partial\n fill was dispensed. These entries can be viewed through the Patient\n Prescription Processing [PSO LM BACKDOOR ORDERS] and View Prescriptions\n [PSO VIEW] options.\n \n . The 'REPRINT' notation printed on the label log when there's no reprint\n capability for OneVA refill/partial fill. The reprint notation has been\n removed.\n . The OneVA Pharmacy Rx Report [PSO REMOTE RX REPORT] on the Rx \n \n . HL7 Messaging changes were made to retrieve more data when\n retrieving patient/prescription information from the host facility, \n and to send more dispensing information to the host facility.\n \n . New fields have been added to the refill/partial sub-files in the\n PRESCRIPTION File (#52) and the REMOTE PRESCRIPTION LOG File (#52.09)\n to ensure that the correct entries in the PRESCRIPTION File (#52) and\n REMOTE PRESCRIPTION LOG File (#52.09) are updated.\n \n (Prescriptions) [PSO RX] menu has been updated to include new \n . The device prompt for a OneVA fill will no longer force a selection of \n a laser label device.\n \nThis patch also corrects a typo "REFIL" that was introduced by PSO*7*651\npatch when it modified the ECME activity log.\n fields added to the REMOTE PRESCRIPTION LOG File (#52.09).\n \n . Dispensing sites will now be able to send a OneVA refill or a OneVA \n partial fill through the Outpatient Pharmacy Automation Interface \n (OPAI) to an Automated Dispensing Device (ADD) for dispensing.\n\n
\nDefect Tracking System Ticket(s) & Overview:\nto print. The scenario is that multiple prescriptions are entered in \n routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the \n patch to install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//', answer NO\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \n install? NO//', answer NO\nCPRS and signed. In Pharmacy Prescription Processing, finish one of the \n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//', answer NO\n \n \nBack-out/Rollback Strategy:\n---------------------------\nBack-out will be done only with the concurrence and participation of\ndevelopment team and appropriate VA site/region personnel. The decision to\nback-out or rollback software will be a joint decision between development\norders and then, in a second Vista session, place that prescription on \nteam, VA site/region personnel and other appropriate VA personnel.\n \nPrior to installing an updated KIDS package, the site/region should have\nsaved a backup of the build in a mail message using the Backup a\nTransport Global [XPD BACKUP] menu option (this is done at time of\ninstall). The message containing the backed-up build can be loaded with\nthe "Xtract PackMan" function at the Message Action prompt. The Packman\nfunction "INSTALL/CHECK MESSAGE" is then used to install the backed up\nroutines onto the VistA System. \n \nhold. Back in the first Vista Session, finish the remaining \nThe back-out plan is to restore the build from the backup created.\n \nNo data was modified by this patch installation and, therefore, no \nrollback strategy is required.\n \n \nValidation of Back-out Procedure:\n---------------------------------\nThe Back-out Procedure can be verified by printing the first 2 lines of\nthe routines contained in this patch using the option First Line Routine \nprescriptions and queue the labels. When you go back into Pharmacy \nPrint [XU FIRST LINE PRINT]. Once the build contained in the \nPSO*7.0*717 patch has been backed out, the first two lines of\nthe routine will no longer contain the designation of this patch in the\npatch list section on line 2.\nPrescription Processing and view the Activity Logs, you will notice that \nthe prescription on hold was sent to external interface (or Script Pro) \neven though it was on hold.\n \nResolution:\n \n-----------\nModify routine PSORXL1 to add the status of hold to the conditions that \ncause the prescription# to be removed from variable PPL that contains a \nstring of prescriptions to print.\n \nTechnical Resolution:\n---------------------\nAt ECME+8^PSORXL1 ADD PSOSTA=3 TO THE CONDITIONS:\n . . I PSOSTA=12!(PSOSTA=11)!(PSOSTA=3)!((PSOSTA=5)&(ESTAT'="")) D ;p717 \nadd HOLD status\n1. INC25835278 - PRESCRIPTIONS SENT TO SCRIPT PRO AFTER BEING HELD\n \nTest Sites:\n-----------\nTBD\n \nPatch Installation:\n------------------- \n \nPre-Installation Instructions:\nThis patch may be installed with users on the system although it is\n \nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \nminutes to install. \n \n \nInstallation Instructions:\n1. Choose the PackMan message containing this build. Then select the \n INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n2. From the Kernel Installation and Distribution System Menu, \n \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter the patch or build name (ex. PSO*7.0*717) \n \n NOTE: Using <spacebar><enter> will not bring up a \n Multi-Package build even if it was loaded \n immediately before this step. It will only \nProblem:\n bring up the last patch in the build.\n \n B. Select the Backup a Transport Global option to create\n a backup message. You must use this option and specify \n what to backup; the entire Build or just Routines.\n The backup message can be used to restore the routines\n and components of the build to the pre-patch condition.\n \n \n i. At the Installation option menu, select Backup \n--------\n a Transport Global\n ii. At the Select INSTALL NAME prompt, enter your \n build PSO*7.0*717\n iii. When prompted for the following, enter "R" for \n Routines or "B" for Build.\n \n Select one of the following:\n \n B Build\n R Routines\nA prescription was placed on hold in a Vista session separate from the \n \n Enter response: Build\n \n iv. When prompted "Do you wish to secure your build? \n NO//", press <enter> and take the default response \n of "NO".\n v. When prompted with, "Send mail to: Last name, First \n Name", press <enter> to take default recipient. Add \n any additional recipients.\n vi. When prompted with "Select basket to send to: IN//", \nsession where the prescription was finished and before labels were queued \n press <enter> and take the default IN mailbox or select \n a different mailbox.\n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n all of the components of this patch, such as \n\n
\nDefect Tracking System Ticket(s) & Overview:\nhappen. The message included a last dispense date that was not actually \ndispensed which caused some confusion.\n \nResolution:\n-----------\nRoutines PSOERXU6 & PSOERXO1 are modified to send the most recent \nRELEASED DATE/TIME field (#31) of the Prescription file (#52) in the \nCurrent Status Details line of the message that reads 'First Fill: \n##/##/##, Last Fill: ##/##/##, Refills Remaining:11'. If there is no \nrelease date it will have spaces after Last Fill.\n \n \n \nTechnical Resolution:\n---------------------\nIn routine PSOERXU6, at entry point BLDRESP+3 the code is changed to the \nfollowing:\n; p715 Use last release date instead of last dispense date\nS LRDATE=$$RXRLDT^PSOBPSUT(RXIEN),LRDATE=$$FMTE^XLFDT(LRDATE,"2D")\nS FFILL=$$GET1^DIQ(52,RXIEN,22,"I"),FFILL=$$FMTE^XLFDT(FFILL,"2D")\nS ACOM="First Fill:"_FFILL_", Last Fill:"_$S(LRDATE:LRDATE,1:" ")_", \n1. INC24578457 - NCPDP CancelRxResponse message communicates incorrect \nRefills Remaining:"_REFL \n \nIn routine PSOERXO1, at entry point CANDC+57 the code is changed to the \nfollowing:\n..; p715 Use last release date instead of last dispense date\n..S LRDATE=$$RXRLDT^PSOBPSUT(RXIEN),LRDATE=$$FMTE^XLFDT(LRDATE,"2D")\n..S RESPONSE="First Fill:"_FFILL_", Last fill:"_$S(LRDATE:LRDATE,1:" \n")_", Refills remaining:"_REFL\nmedication fill status to e-prescribers\n \nProblem:\n--------\nVistA eRx pharmacy software sent CancelRxResponse messages that \nmisinformed electronic prescribers about medication fills that did not \n\n
\nDefect Tracking System Ticket(s) & Overview:\neRx queue. This is preventing us from processing these orders if the \ncommunity prescriber does not submit their DEA number. The problem is \nthat the inbound eRX contains a digital signature and the provider does \nnot have a DEA# sent in the eRX message and the drug is not a controlled \ndrug. This causes an error to be encountered when processing it in PSO \nERX FINISH. The error is 'eRx Provider does not have a valid DEA#.'\n \nResolution:\n-----------\nRoutine PSOERXUT is modified to not return an error when the eRX drug is \n \nnot a controlled drug and the provider doesn't have a DEA# and the eRX is \ndigitally signed.\n \nTechnical Resolution:\n---------------------\nPSOERXUT is modified at line PRDRVAL+58^PSOERXUT to add the condition \nACTION=-"AC"\n \nLine PRDRVAL+58^PSOERXUT after the code change:\n . I ACTION="EP"!(ACTION="VP")!(ACTION="AC"),'VACSDRUG D Q ;p718 add \n1. INC25956349 - INBOUND ERX FOR NON-CONTROLLED SUBSTANCES COMING \naccept action\nTHROUGH AS CONTROLLED\n \nProblem:\n--------\nSite is receiving several inbound eRx for non-controlled substance \nmedications that are designated as controlled substances in the inbound \n\n
\nThis patch addresses the following issue:\n \nThe VistA option View Prescriptions does not display the eRx indicator "&"\nif the prescription is an inbound eRx prescription.\n\n
\nThis patch will resolve the following issue:\n \nThe date format printed to the activity log for an edited ISSUE DATE or \nFILL DATE is printed using the Fileman date format. The date format used \nshould be more consistent to what is already being used by VistA.\n\n
\nWhen a prescription is reinstated using the Discontinue Prescription(s)\nDiscontinue Prescription(s) [PSO C] option.\n[PSO C] option, and immediately afterwards the Patient Prescription\nProcessing [PSO LM BACKDOOR ORDERS] option is used to edit the SIG of a\nprescription, the change of SIG creates a new order. The generated order\nhas a different dispensed drug. It contains the drug of the prescription\nthat was most recently reinstated using the Discontinue Prescription(s)\n[PSO C] option. This could result in dispensing the wrong drug to the\npatient. In order to correct this problem this patch insures that all\nrelated variables are killed appropriately when quitting from the\n\n
\nSee FORUM patch description.\n\n
\nINC22168250 - PROTOCOL "PSO LM HIDDEN OTHER #2" contain duplication "RR" \n\n
\nThis patch will resolve the following issue:\n \nThere is an issue reported of an incorrect status being displayed on the \nCMOP Event Log for a CMOP dispensed refill that was subsequently returned\nto stock, refilled again and then it's label queued for printing. In this\ncase, the status is being displayed as 'DISP',however, once a refill is\nreturned to stock the status should be displayed as 'Disp Refill Deleted'.\n\n
\nDefect Tracking System Ticket(s) & Overview:\nWhen processing telephone refills using the option Process Telephone \nRefills [PSO PROCESS TELEPHONE REFILLS] and answering, 'Process telephone \nrefills for all divisions?' with YES, any refills that are not for the \ndivision selected at the start of the Process Telephone Refills option \nand has a drug setup in the DRUG file (#50) with CMOP DISPENSE field \n(#213) not set to Yes, the drug will be refilled with the wrong division \nin the refill record of the PRESCRIPTION file (#52). It will mark the \nrefill for the division selected in the option instead of the division \nfor which the original RX was created.\nThe problem is due to variable PSOSITE being set to the IEN of the \n===========================================\nOUTPATIENT SITE (#59) selected at the Division: prompt when running the \nProcess Telephone Refills [PSO PROCESS TELEPHONE REFILLS] option. \nThis variable is then used during processing and creation of the refill \nwhich results in the incorrect division to be filed into the DIVISION \nfield (#8) in the REFILL sub record (#52.1D) of the PRESCRIPTION file \n(#52) when Process telephone refills for all divisions? // is answered \nYes and a refill is encountered for a division not matching the division \nselected.\n \n Resolution:\n \n ----------\nVariable PSOSITE is used extensively in PSO code, so this patch is only \nmaking a change to PSOSITE's value within routine PSOVEXRX.\n \nWhen a RX is being processed in Process Telephone Refills and the \noriginal fill is for a division that is different than the division \nselected at the Division: prompt, the variable is newed and reset to the \nIEN for the division and variable PSOBBC("PSOVEXRX") is also set before \nREFILL^PSOBBC is called to process the fill for that RX, the variable is \nreset to original value afterwards. PSOBBC("PSOVEXRX") is used \n1. INC21810787 - TELEPHONE REFILLS - Processing all divisions \nconditionally to determine to display the message 'RX # 1234567 is for \n(XXXXXXXXXXX) division.' On the output at the end of running Process \nTelephone Refills.\n \n \n Technical Resolution:\n --------------------\nRoutine PSOVEXRX\n \nLine PSO6+13^PSOVEXRX is commented out and replaced with:\npotential error in routine\n ;p677 handle multi division\n ;S PSOBBC("DONE")=PSOBBC("IRXN")_"," D REFILL^PSOBBC\n I '$P($G(PSOSYS),"^",2) D REFILL^PSOBBC I 1\n E D\n . I PSOSITE'=$P(^PSRX(PSORXIEN,2),U,9) S PSOBBC("PSOVEXRX")=PSOSITE N \nPSOSITE S PSOSITE=$P(^PSRX(PSORXIEN,2),U,9)\n . D REFILL^PSOBBC\n . K PSOBBC("PSOVEXRX")\n S PSOBBC("DONE")=PSOBBC("IRXN")_","\n \n \nRoutine PSOREF0\n \nCHKDIV^PSOREF0 is changed to:\nCHKDIV G:$P(PSOREF("RX2"),"^",9)=+PSOSITE&'$G(PSOBBC("PSOVEXRX")) CHKDIVX \n;p677 multi division update for telephone refill process \n \n Problem:\n -------\n\n\nThe PSO*7.0*707 patch delivers the necessary components for the support of\nPharmacy, as well as individual patient-related requests.\nPSO ACTIVITY LOG New\nPSO ACTIVITY LIST New\nPSO CMOP LOG New\nPSO CMOP M New\nPSO COPAY LOG New\nPSO COPAY LIST New\nPSO ECME LOG New\nPSO ECME M New\nPSO eRX LOG New\nPSO eRX M New \n \nPSO GET TEMPORARY ADDRESS New\nPSO LABEL LOG New\nPSO LABELS LIST New\nPSO LOT EXP New\nPSO LOT EXP M New\nPSO PARTIALS LOG New\nPSO PARTIALS LIST New\nPSO REFILL LOG New\nPSO REFILL LIST New\nPSO TEMP ADDRESS UPDATE New\nIn addition, there is a post-install routine that will add the PSO WEB\n \n \nAdditional Information:\n-----------------------\n \n \nBlood Bank Team Coordination:\n-----------------------------\nN/A\n \nCHART menu context to the connector proxy user.\n \nNew Service Requests (NSRs):\n----------------------------\nN/A \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nN/A\n \n \n \nTest Sites:\n-----------\nMiami VAMC, FL\nWest Palm Beach VAMC, FL\n****NOTE**** There are post-install instructions for setting up the \n \n \nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\nThe software for this patch is being released in a PackMan message.\n \n \nDocumentation describing the new functionality is included in this \nrelease. Documentation can be found on the VA Software Documentation \nLibrary at: https://www.domain.ext/vdl/. Documentation can also be \nconnector proxy user. These MUST be completed for these patch components\nobtained at https://download.vista.domain.ext/index.html/SOFTWARE. \n \n \nDocumentation Title File \nName \n---------------------------------------------------------------------\n \n \n \nPatch Installation:\nto function. These instructions were also included in patch PSO*7.0*642.\n-------------------\n \n \nPre/Post Installation Overview:\n-------------------------------\n \n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is\nIf completed during installation of patch PSO*7.0*642, the\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \n \n \n \nInstallation Instructions:\n \n1. Choose the PackMan message containing this build. Then select \nPost-installation instructions in this patch may be ignored.\n the INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n \n2. From the Kernel Installation and Distribution System Menu, \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter the patch or build name. \nthe SalesForce Customer Relations Management (CRM) project, Outpatient\n \n PSO*7.0*707\n \n NOTE: Using <spacebar><enter> will not bring up a \n Multi-Package build even if it was loaded \n immediately before this step. It will only \n bring up the last patch in the build.\n \n B. Select the Backup a Transport Global option to create \n a backup message. You must use this option for each\n patch contained in the Host File. For each patch you\nPatch Components:\n can specify what to backup; the entire Build or just\n Routines. The backup message can be used to restore\n just the routines or everything that will restore your \n system to pre-patch condition.\n \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n-----------------\n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n all of the components of this patch, such as \n routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the \n patch to install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//', answer NO.\n \n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \n install? NO//', answer NO.\n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//', answer NO.\n \n \nPost-Installation Instructions:\n-------------------------------\nPatch Components:\nNOTE: The below instructions, for adding the PROXY USER, were included\nin the previous PSO patch POS*7.0*642. If the procedures to add the\nPROXY user were completed after the installation of PSO*7.0*642,\nyou may skip these post-installation steps below.\n \n******************************* MANDATORY *******************************\nThe designated site representative must contact the deployment team\nthrough the VHAEKH PSO-7-6-42 mail distribution list in Outlook to get the\naccess/verify code for the CONNECTOR PROXY for your site. This will be\nsent encrypted via Outlook.\n-----------------\n************************************************************************* \n \n \nHOW TO SET UP CONNECTOR PROXY USER THROUGH FOUNDATIONS:\n=======================================================\nUsing Vista Option FOUNDATIONS MANAGEMENT [XOBU SITE SETUP MENU]:\n \n <<< VistALink Parameters >>>\n \n VistALink Version: 1.6 Heartbeat Rate: 180 Latency Delta: 180\n \n \n <<< VistALink Listener Status Log >>>\n ID Box-Volume Port Status Status Date/Time \nConfiguration \n \n \n \n \n \n Enter ?? for more actions\n \nSP Site Parameters SL Start Listener\nCFG Manage Configurations STP Stop Listener\nCP Enter/Edit Connector Proxy User SB Start Box\nRE Refresh CU Clean Up Log\nCM Connection Manager\nSelect Action:Quit// CP Enter/Edit Connector Proxy User \nEnter NPF CONNECTOR PROXY name : PSO,CONNECTOR PROXY\n Are you adding PSO,CONNECTOR PROXY as a new NEW PERSON (the\n198970TH)? No// Y (Yes)\n \nFiles & Fields Associated:\nChecking SOUNDEX for matches.\n \n. <different potential matches for each site>\n \nType <Enter> to continue or '^' to exit: \nDo you still want to add this entry: NO//Y\nWant to edit ACCESS CODE (Y/N): Y\nEnter a new ACCESS CODE <Hidden>: *********** <Use ACCESS CODE provided \nto your site> \nPlease re-type the new code to show that I have it right: ***********\n \nOK, Access code has been changed!\nThe VERIFY CODE has been deleted as a security measure.\nYou will need to enter a new VERIFY code so the user can sign-on.\n \nWant to edit VERIFY CODE (Y/N): Y\n \nEnter a new VERIFY CODE: ************ <Use VERIFY CODE provided to your \nsite>\n \nPlease re-type the new code to show that I have it right: ************\nPharmacy requirements, on the VistA level. It has been designed to\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n \n \n \nBack-Out/Roll Back Plan:\n------------------------\nDue to the complexity of this patch, it is not recommended for back-out,\nand a restore from a backup of the Transport Global should not be\nattempted. In the event that this patch needs to be backed out, the patch\ninstaller should enter a ServiceNow Ticket. The development team will need\nto issue a follow-up patch in order to comprehensively back-out this \n------------------ ------------------- --------------------\npatch.\n \nRoutine Information:\n====================\n \n \nThe second line of each of these routines now looks like:\n ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build\n \nThe checksums below are new checksums, and\nN/A\n can be checked with CHECK1^XTSUMBLD.\n \nForms Associated:\n \nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\nN/A\n \nprovide REST services for the Java scripted calls used by the SalesForce\nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nUser Interface.\nCRMS WEB CHART Broker New\n \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \n \n \nSecurity Keys Associated: \n \nSecurity Key Name\n-----------------\nN/A\n \n \nTemplates Associated:\n \nThe patch releases the necessary Remote Procedure Calls (RPCs) and ENTITY\nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\nPSO ACTIVITY LOG New\nPSO CMOP LOG New\n(#1.5) file entries for retrieval of VistA data from a VistA instance. \nPSO COPAY LOG New\nPSO ECME LOG New\nPSO ERX LOG New \nPSO GET TEMPORARY ADDRESS New\nPSO LABEL LOG New\nPSO LOT EXPIRATION New\nPSO PARTIALS LOG New\nPSO REFILL LOG New\nPSO TEMP ADDRESS UPDATE New\n \nThe patch supports the operations of the Virtual Care Centers, Outpatient\nParameter Definitions Associated:\n \nParameter Name New/Modified/Deleted\n-------------- --------------------\nN/A\n \nEntities Associated:\n \nEntity Name New/Modified/Deleted\n----------- --------------------\n\n
\nThis patch will resolve the following issues:\nwording in the Zero Report should be corrected to not indicate the \ntransmission status, thereby avoiding contradicting with the preceding \n"transmission failed" email. \n \n2) PSO*7*696 IOC follow-up issues:\n \nFour issues were identified regarding the new SPMP State Parameter for \nZERO REPORT DEFAULT DIVISON during IOC for previous patch PSO*7*696.\nAll of the items deal with the View/Edit SPMP State Parameters option\n[PSO SPMP STATE PARAMETERS].\n \n \n 1. When the SEND EXPORT STATE PARAMETER="2" but the ZERO REPORT \n DEFAULT DIVISION State Parameter is not set, then no Zero Report \n is generated. However, currently the ZERO REPORT DEFAULT DIVISION is\n not a required field when using the View/Edit SPMP State Parameters\n option [PSO SPMP STATE PARAMETERS]. It should be made required \n within the View/Edit SPMP State Parameters option [PSO SPMP STATE\n PARAMETERS] for SEND=2 to ensure that Zero reports will be sent.\n \n 2. The Help Text for the ZERO REPORT DEFAULT DIVISION State \n1) Zero Report email verbiage:\n Parameter does not clearly indicate it is required when the \n SEND EXPORT STATE PARAMETER="2". \n \n 3. When using the SEND EXPORT STATE PARAMETER, the State Parameter \n ZERO REPORT DEFAULT DIVISION shows "//" even when it's blank. \n This is not normal behavior since empty fields should not have "//".\n This is only cosmetic and does not affect functionality of the\n Zero Report, but it should be fixed.\n \n 4. The Technical Description of the ZERO REPORT DEFAULT DIVISION \n \n State Parameter wording is a little confusing by saying it's used\n for "MbM states that do not dispense controlled substances".\n It should be clarified to say this is used when a state has\n State Parameter SEND EXPORT STATE PARAMETER=2.\n \n \nAssociated ticket(s):\n---------------------\nINC26586596 - Zero Report verbiage\nINC27015594 - PSO*7*696 IOC follow-up issues\nWhen the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] job fails\nto transmit a Zero Report batch, two emails for the Zero Report\nbatch are generated with contradicting wording. First sent is an email \nsaying the transmission failed; then a second email is sent saying that \nthe Zero Report was transmitted. To reduce confusion at the sites, the \n\n
\nWhen processing a OneVA fill (refill or partial), the user is prompted for\nget a View Alert. If a laser label device is selected at the label prompt,\nthe laser label will still print without issues.\n \nWhen sending a OneVA fill (refill or partial) to the OPAI, the routing\n(WINDOW or MAIL) is based on previous routing information for the\nprescription from the Host Site. This patch will now set the routing to\nWINDOW for all OneVA fills.\n \nWhen a OneVA fill is processed and sent to the OPAI, filling information \nis sent from the dispensing site back to host site in an HL7 message. The \na label device. After device selection, the software will first send the\nproblem is even if the message was successful, the VistA HL7 message will \ndisplay a Status of "ERROR", and an Err Type of "Message was NAK'ed". \nThis patch resolves the issue so these messages will now show as\nsuccessfully transmitted.\nfill to the Outpatient Pharmacy Automated Interface (OPAI), if applicable,\nthen attempt to print a label. But if the user selected a device that is\nnot designated as a laser label device, an error occurs when the label \nprints because only laser labels can print for a OneVA fill. And the user\nwill get a View Alert regarding this error. The resolution if a non\nlaser label device was selected is to not make the attempt to print the\nlabel, so no error will be logged in the error trap and the user will not\n\n
\nThis patch addresses the following issue:\nProblem:\n--------\nWhen editing an active prescription which has INJECT as a verb, and \nfinishing that Rx appropriately, the pharmacist then moves to another \npatient and enters a new Rx, and the verb moves inappropriately to that \nnew Rx. The problem is seen when the verb for each RX is different.\n \nResolution:\n-----------\nThe problem is caused by the variable VERB not getting deleted when \n \nquitting from routine PSOORED3. At MW+9^PSOORED3, the processing quits \nout without killing any variables. All other places that quit out of the \nroutine quit via EX or EX1 that kill variables before quitting out of the \nroutine. \n \nTechnical Resolution:\n---------------------\nMW+9^PSOORED3 is changed from\n K QTYHLD Q:$G(PSOVER)!($G(PSOREEDQ))\nTo\nNEW RX IS ERRONEOUSLY GETTING SIG BUILT WITH VERB FROM LAST EDITED RX\n K QTYHLD G:$G(PSOVER)!($G(PSOREEDQ)) EX1\n \nDefect Tracking System Ticket(s) & Overview:\n \n1. INC27051655 - NEW RX IS ERRONEOUSLY GETTING SIG BUILT WITH VERB \n FROM LAST EDITED RX\n \n\n
\nSee FORUM for patch description details.\n\n
\nBackup of PSO*7.0*716 on Mar 23, 2023\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\n1) Currently when a prescription is renewed either using the Patient\n \n2) This patch corrects a problem of an undefined variable error that\ncan occur during the speed renewal process within the Patient Prescription\nProcessing [PSO LM BACKDOOR ORDERS] option.\nPrescription Processing [PSO LM BACKDOOR ORDERS] or Complete Orders from\nOERR [PSO LMOE FINISH] option, the FILL DATE field (#22) of the\nPRESCRIPTION file (#52) in the renewed prescription is calculated based on\nthe LAST DISPENSED DATE field (#101) of the PRESCRIPTION file (#52). The\nrenewal process does not check whether the last refill was released or a\nlabel has been printed. If such a refill existed, the FILL DATE field\n(#22) of the PRESCRIPTION file (#52) of the renewed prescription was being\nset to a date far into the future. This patch corrects this problem.\n\n
\nThis patch resolves the following issue:\n \nINC25021154 - If the PSO EPCS PSDRPH KEY option is assigned to a custom \nmenu, the user may see the "Enter User Name:" prompt again unexpectedly \nupon exiting the option or entering a different one. \n\n
\nThis patch addresses the following issue:\nMed List for Review will now be able to display "Active/Parked"\nwhen the prescription is in a Parked status.\n \nThis patch also modifies the logic related to refilling a Parked\nPrescription. If the original fill or the refill is not released, or \nlabel not printed or not processed by CMOP then that fill will be \nprocessed, and the prescription will be placed in suspended status. \nOtherwise, the current logic in refilling the prescription will be \nfollowed.\n \nWith the introduction of PARK functionality (CPRS 32B release), and\nonce the Park functionality is enabled, the Health Summary Type of\nEssential Med List for Review needs to be able to display "Active/Parked"\nas a status. The Application Program Interface (API), PSO52API, which\nprovides the prescription details for this report has been modified to\nreturn a status of ACTIVE/PARKED if the calling package is HEALTH\nSUMMARY (GMTS). Along with changes in patch GMTS*2.7*145, the Essential\n\n
\nSee FORUM patch description.\n\n
\nThe Inbound Electronic Prescribing (eRx) enhancements delivered in this\n The LOCK timeout was intentionally changed to 0.01 seconds for MbM for the\n5. VistA Provider Suggestion\n ---------------------------------------------------------------------------\n When matching eRx Provider to a corresponding VistA Provider before the \n user is prompted for the VistA entry it will first be presented with \n suggestion (if any) based on the following logic:\n \n - Once a VistA Provider is matched and later validated to an eRx Provider it\n is then "remembered"\n \n - When a new eRx prescription is received for the same eRx Provider the\n following options in order to assist MbM in the processing of high-volume\n "remembered" VistA Provider(s) are then presented as suggestions for the\n user to select, as shown below (Validate Patient Screen - Edit action):\n \n Select Item(s): Next Screen// E Edit \n \n - Below is an example for the Provider matching (Validate Provider Screen -\n Edit action):\n \n |Sugg. 1 of 1 - 08/08/23|\n ERX PROVIDER VISTA PROVIDER|From eRx#: 123123 |\n incoming eRx's:\n __________________________________________________________________________\n Name:AEXRFGRI,APSKACWHZ |Name:AEXRFGRI,APSKACWHZ\n NPI :1144286097 |NPI :1073579710\n DEA#:AA1216680 |DEA#:AA1216680\n Phone #: 555-220-0303 |Phone #: (555) 220-0303\n Address: |Address:\n 123 INTERNATIONAL RD |123 INTERNATIONAL RD\n GREENVILLE, IL 66024 |GREENVILLE, IL 66024\n __________________________________|_______________________________________\n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (E)XIT: EXIT// \n \n \n - When presented with a suggestion the user is given 3 options: (A)ccept,\n (F)orget or (E)xit:\n \n ACCEPT - Accepts the suggested VistA Provider and matches it to the eRx\n FORGET - Forgets this suggested VistA Provider so that it is not \n presented again in the future to any user\n EXIT - Exits and proceed to match the VistA Provider manually\n \n If more than one suggestion exists, then a 4th option is included: (N)ext:\n Complete Orders from eRx [PSO ERX FINISH]\n \n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (N)EXT (E)XIT: EXIT// \n \n NEXT - Ignores the current suggestion and view the next one"\n \n6. VistA Medication (Drug, Dosage, Qty, etc...) Suggestion\n ---------------------------------------------------------------------------\n When matching the eRx Drug to a corresponding VistA Drug before the \n user is prompted for the VistA entry it will first be presented with \n suggestion (if any) based on the following logic:\n eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING]\n \n - Once an eRx is accepted, it moves to the Pending Queue as a Pending Order.\n After the Pending Order is finished it becomes an Active prescription. At\n this point the software will "create a memory" of how the prescription was\n entered (Drug, Dosage, Days Supply, Qty, # of refills, etc). \n \n - When a new eRx prescription is received for the same eRx Drug, NDC\n Code, SIG, Qty, Days Supply, # of Refills and Substitution allowance. the\n "remembered" VistA fields are then presented as suggestions for the\n user to select, as shown below (Validate Drug Screen - Edit action):\n Complete Orders from OERR [PSO LMOE FINISH]\n \n Select Item(s): Next Screen// E Edit \n \n - Below is an example for the Provider matching (Validate Provider Screen -\n Edit action):\n \n |Sugg. 1 of 1 - 06/11/23|\n RX MED VISTA MED |From Rx#: 2297913 |\n ____________________________________________________________________________\n Drug: Meloxicam 15mg Tablet |Drug: MELOXICAM 15MG TAB\n \n Substitution? YES Renewals? YES |Drug Message:\n | NATL FORM (2/10)\n ____________________________________|_______________________________________\n SIG: |SIG:\n TAKE ONE TABLET PO EVERY SIX HOURS | TAKE ONE TABLET BY MOUTH ONCE DAILY\n AS NEEDED | DAILY\n ____________________________________|_______________________________________\n Provider Notes/Comments: |Provider Comments:\n | \n ____________________________________|_______________________________________\n2. eRx Provider Auto-Validation (MbM ONLY)\n Quantity: 90 |Quantity: 180\n Dispense Unit: |Dispense Unit: TAB\n Qty Qualifier: Original Quantity |\n ____________________________________|_______________________________________\n Days Supply: 23 Refills: 5 |Days Supply: 30 Refills: 11\n ____________________________________|_______________________________________\n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (E)XIT: EXIT// \n \n - When presented with a suggestion the user is given 3 options: (A)ccept,\n (F)orget or (E)xit:\n ---------------------------------------------------------------------------\n \n ACCEPT - Accepts the suggested VistA data and matches it to the eRx\n FORGET - Forgets this suggested VistA Provider so that it is not \n presented again in the future to any user\n EXIT - Exits and proceed to match the VistA Provider manually\n \n If more than one suggestion exists, then a 4th option is included: (N)ext:\n \n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (N)EXT (E)XIT: EXIT// \n \npatch include updates to the current eRx functionality to convert all\n a) A new logic for auto-validating a VistA Providers for MbM sites is being\n NEXT - Ignores the current suggestion and view the next one"\n \n7. Patient Validation Screen\n ---------------------------------------------------------------------------\n The content of the Patient Validation screen was completely re-arranged to\n show the eRx Patient and the VistA Patient side-by-side. In addition, the\n eRx Patient allergy list (received from the outside prescriber) will be\n displayed as well as the ChampVA Rx Benefit eligibility (MBM sites only).\n Besides displaying the patients side-by-side, a few other features were\n introduced to make the screen more user friendly, such as:\n added by this patch to assist MbM in the processing of high-volume\n a) When there is a mismatch for field (e.g., Name, DOB, etc.) the content\n of such field will display in reverse video in for both records, eRx\n and VistA Patients.\n b) The content will display in highlight in order to stand from the field\n label. \n \n Obs) These features depend on the terminal display settings being set\n differently for reverse video and highlighted font in order for it\n to work.\n \n incoming eRx's. In order to auto-validate a provider the following \n Below is an example of how the new screen will be displayed (without the\n reverse or highlighted video features):\n _________________________________________________________________________\n eRx Reference #: 916 ChampVA Rx Benefit: ELIGIBLE\n Status: AUTO-MATCHED/EDITED & VALIDATED by TEST,USER on 1/28/23@14:52:29\n ERX PATIENT VISTA PATIENT \n _________________________________________________________________________\n Name: TEST,PATIENT BETA |Name: TEST,PATIENT BETA \n DOB : APR 21, 1990 |DOB : APR 21,1990 \n SSN : 345781234 |SSN : 345-78-1234 \n conditions must be fulfilled:\n Sex : MALE |Sex : MALE \n Address: |Address: \n 123 PATIENT WAY | 123 PATIENT WAY \n CHEYENNE,WY 82001 | CHEYENNE,WY 82001 \n Home Phone: 2172234567 |Home Phone: 217-223-4567 \n _______________________________________|_________________________________\n Allergy: |Allergy: \n NO ALLERGY ASSESSMENT | NO KNOWN ALLERGIES \n _______________________________________|_________________________________\n |Pharmacy Narrative: \n \n _______________________________________|_________________________________\n Weight(Kg): |Weight(Kg): \n Height(cm): |Height(cm): \n _______________________________________|_________________________________\n \n8. Provider Validation Screen\n ---------------------------------------------------------------------------\n The content of the Provider Validation screen was completely re-arranged to\n show the eRx Provider and the VistA Provider side-by-side. In addition, the\n Besides displaying the providers side-by-side, a few other features were\n - eRx Providers was auto-matched to a VistA Provider\n introduced to make the screen more user friendly, such as:\n a) When there is a mismatch for field (e.g., Name, DEA#, etc.) the \n content of such field will display in reverse video in for both\n records, eRx and VistA providers.\n b) The content will display in highlight in order to stand from the field\n label. \n \n Obs) These features depend on the terminal display settings being set\n differently for reverse video and highlighted font in order for it\n to work.\n - eRx Provider last name matches VistA Provider last name\n \n Below is an example of how the new screen will be displayed (without the\n reverse or highlighted video features):\n _________________________________________________________________________\n Provider Validation Apr 16, 2023@17:52:07 Page: 1 of 1 \n eRx Reference #: 344422 eRx Patient: TEST,PATIENT\n Status: AUTO-MATCHED \n ERX PROVIDER VISTA PROVIDER \n _________________________________________________________________________\n Name: TEST,PROVIDER |Name: TEST,PROVIDER \n - First letter of eRx Provider first name matches first letter of VistA\n NPI : 1073579710 |NPI : 1073579710 \n DEA : AV4538419 |DEA : CC4796237 DEA EXP: 12/23/20\n | \n Address: |Address: \n 123 FAKE STREET SOUTH |123 FAKE STREET NORTH\n FRISCO,TX 75033 |FRISCO,TX 75033 \n Tel: 555-222-3344 |Tel: (555) 222-3344\n Fax: |Fax: \n ______________________________________|__________________________________\n \n Provider first name\n9. Drug Validation Screen\n ---------------------------------------------------------------------------\n The content of the Drug Validation screen was completely re-arranged to\n show the eRx Drug information and the VistA corresponding fields in a \n side-by-side arrangement. In addition, the eRx Patient allergy list \n (received from the outside prescriber) will be displayed as well as the\n list of allergies from the VistA patient.\n \n Besides displaying the information side-by-side, a few other features were\n introduced to make the screen more user friendly, such as:\n - Zip code for the eRx Provider matches the zip code for the VistA\n a) When there is a mismatch for field (e.g., Drug Name, Qty, etc.) the \n content of such field will display in reverse video for both fields,\n eRx and VistA.\n b) The content will display in highlight in order to stand from the field\n label. \n \n Obs) These features depend on the terminal display settings being set\n differently for reverse video and highlighted font in order for it\n to work.\n \nof the MbM Class 3 modifications into Class 1. Below is summary of the\n Provider\n Below is an example of how the new screen will be displayed (without the\n reverse or highlighted video features):\n \n Drug Validation Aug 18, 2023@13:58:45 Page: 1 of 3 \n eRx Reference #: 123211 Date Written: 8/10/23 Effective Date: \n Status: MANUALLY-MATCHED \n ERX MED | VISTA MED \n Allergy: |Allergy: \n NO ALLERGY INFORMATION RECEIVED| NO KNOWN ALLERGIES \n ________________________________|_____________________________________\n - eRx is not electronically signed (CS eRx)\n Drug: BREZTRI AEROSPHERE 160 MCG|1)Drug: BREZTRI AEROSPHERE 160 MCG \n -9MCG-4.8MCG/ACTUATION HFA| \n AEROSOL INHALER | \n Substitution? YES Renewals? YES|Drug Message: \n | NATL FORM (10-01) (NDC) \n ________________________________|_____________________________________\n SIG: |SIG: \n Inhale 2 puffs twice a day by | INHALE 1 PUFF PSIV EVERY MORNING \n inhalation route for 30 days. | \n ________________________________|_____________________________________\n \n |2) Dosage: 1 PUFF \n | Verb: INHALE\n |Disp. Units: \n | Noun: \n | Route: NASAL\n | Schedule: QAM \n ________________________________|_____________________________________\n |3)Patient Instructions: \n | \n ________________________________|_____________________________________\n b) The Audit Log will display "AUTO-VALIDATED" to indicate that a provider\n Provider Notes/Comments: |4)Provider Comments: \n | TEST \n ________________________________|_____________________________________\n |5)Pat. Status: OTHER FEDERAL \n ________________________________|_____________________________________\n Quantity: 30 |6)Quantity: 30 \n Dispense Unit: | Dispense Unit: BX \n Qty Qualifier: Original Quantity| \n ________________________________|_____________________________________\n Days Supply: 30 Refills: 5 |7)Days Supply: 30 8)Refills: 5 \n was auto-validated, as seen in the example below:\n ________________________________|_____________________________________\n |9)Routing: MAIL \n ________________________________|_____________________________________\n |10)Clinic: \n ________________________________|_____________________________________\n \n10. New action View History Log (HL)\n ---------------------------------------------------------------------------\n This new action added eRx Holding Queue Display screen will allow the user\n to view a comprehensive history of the eRx as it moves through the OP\n \n application, including activities in Backdoor Pharmacy. Please, refer to\n the user documentation for more information about this new option.\n \n11. Batch Hold and Un-Hold Functionality\n ---------------------------------------------------------------------------\n The current Hold and Un-Hold actions were modified to perform the following \n additional function: every time a prescription is put on Hold or removed\n from Hold, the software will check other prescriptions exist for that\n patient that were sent by the same prescriber on the same day. If any is\n found, the software will ask the user if they want to Hold (or Un-Hold)\n New Value: PROVIDER,NAME(DEA#: AX1212543) - AUTO-VALIDATED\n those additional eRx records as well, as shown below:\n ...\n Select Action: Next Screen// H Hold \n \n Select HOLD reason code: HAL NO ALLERGY ASSESSMENT\n Additional Comments (Optional): TESTING BATCH HOLD\n Updating...done.\n \n The following prescriptions are from the same provider and received on the\n same day:\n \n \n PROVIDER: TEST,PROVIDER eRx RECEIVED DATE: JAN 28, 2023@10:57:14\n ERX ID DRUG NAME PROVIDER STATUS\n --------------------------------------------------------------------------\n 123011 GABAPENTIN 300MG CAP TEST,PROVIDER N\n 123012 CITALOPRAM HYDROBROMIDE 20MG T TEST,PROVIDER N\n 123013 IBUPROFEN 400MG TAB TEST,PROVIDER N\n 123014 ACETAMINOPHEN 325MG TAB TEST,PROVIDER N\n \n Do you want to put them on HOLD-HAL? No// YES Updating...done.\n c) The Single Patient list will identify such event (auto-validation) by\n \n12. New Allergy Functionality Enhancements\n ---------------------------------------------------------------------------\n Functionality related allergies is being improved through the following\n modifications:\n \n a) When matching or accepting validation of a VistA patient it will display\n in the warnings if the VistA patient selected has no Allergy Assessment:\n \n ******************************* WARNING(S) *************************\n by highlighting the letter "V" under the MATCHING/PR column.\n VistA Patient does not have an Allergy Assessment.\n ***********************************************************************\n \n MbM sites only:\n -------------- \n i) User won't be able to accept validation of a VistA Patient that\n does not have an Allergy Assessment.\n ii) All the actionable records for the same eRx patient will be\n automatically be put on Hold with the code HAL - NO ALLERGY\n ASSESSMENT, the user will be notified as shown below:\nchange being delivered in this patch. For a more comprehensive description of\n \n \n The following eRx record(s) have been put on Hold (HAL) because the \n VistA Patient selected (OUTPATIENT,JLG ONE) does not have an Allergy\n Assessment:\n ERX ID DRUG NAME PROVIDER STATUS\n -----------------------------------------------------------------------\n 123010 CETIRIZINE HCL 10MG TAB TEST,PROVIDER HAL\n 123011 GABAPENTIN 300MG CAP TEST,PROVIDER HAL\n 123012 CITALOPRAM HYDROBROMIDE 20MG T TEST,PROVIDER HAL\n 123013 IBUPROFEN 400MG TAB TEST,PROVIDER HAL\n3. VistA Patient and VistA Provider Look-up (MbM ONLY)\n 123014 ACETAMINOPHEN 325MG TAB TEST,PROVIDER HAL\n \n Type <Enter> to continue or '^' to exit: \n \n b) A new screen titled 'Patient Allergies' was created to show the eRx\n Patient allergies side-by-side with the VistA Patient allergies in\n detail. This new Screen can be invoked by using the PA (Patient\n Allergy) hidden action from the following screens:\n \n - eRx Holding Queue Display Screen (eRx Holding Queue)\n ---------------------------------------------------------------------------\n - Patient Validation Screen (eRx Holding Queue)\n - Drug Validation Screen (eRx Holding Queue)\n - Pending Order Orders Screen (Backdoor OP)\n \n This new screen contains an action called VPA (VistA Patient Allergies),\n which allows the user to update the VistA Patient Allegies without \n leaving the option. \n Note: In order to use the VPA action the VistA Patient has to have been\n previously matched.\n \n The VistA Patient and Provider lookup prompts have been modified to display\n13.New Eligibility Functionality (MbM sites only)\n ---------------------------------------------------------------------------\n Functionality related ChampVA Rx Benefit Eligibility is being improved\n through the following modifications:\n \n a) ChampVA Rx Benefit eligibility information will be displayed in the new\n Patient Validation Screen in the Header section. It will have one of \n these 3 possible Values: ELIGIBLE, NOT ELIGIBLE or SB (Spine Bifida).\n b) When matching a VistA patient it will display in the warnings if the\n VistA patient selected is not eligible for ChampVA Rx Benefit (soft-\n different information for MbM sites only:\n stop):\n \n ******************************* WARNING(S) *************************\n VistA Patient is not eligible for ChampVA Rx Benefit.\n ***********************************************************************\n \n c) It will not allow accepting validation of a matched VistA patient that\n is not eligible for ChampVA Rx Benefit (hard-stop):\n \n *******************************INVALID PATIENT*************************\n - For the VistA Patient it displays:\n VistA Patient is not eligible for ChampVA Rx Benefit.\n ***********************************************************************\n \n d) When matching or accepting validation fo a VistA patient that is not\n eligible for ChampVA Rx Benefit all the actionable records for the same\n eRx patient will be automatically be put on Hold with the code HEL - \n ELIGIBILITY ISSUES, the user will be notified as shown below:\n \n The following eRx record(s) have been put on Hold (HEL) because the \n VistA Patient selected (OUTPATIENT,JLG ONE) is not Eligible for ChampVA\n Name, DOB, SSN, City and State\n Rx Benefit:\n \n ERX ID DRUG NAME PROVIDER STATUS\n -----------------------------------------------------------------------\n 123010 CETIRIZINE HCL 10MG TAB TEST,PROVIDER HEL\n 123011 GABAPENTIN 300MG CAP TEST,PROVIDER HEL\n 123012 CITALOPRAM HYDROBROMIDE 20MG T TEST,PROVIDER HEL\n 123013 IBUPROFEN 400MG TAB TEST,PROVIDER HEL\n 123014 ACETAMINOPHEN 325MG TAB TEST,PROVIDER HEL\n \n (e.g., AAQDY,BUDT LUSER 08/04/1954 101058613 PADDLETON,MD)\n Type <Enter> to continue or '^' to exit: \n \n14.Duplicate VistA Patient Check (MbM sites only)\n ---------------------------------------------------------------------------\n A new check will be performed when the users selects a patient (Edit) or\n Accept Validation of a previously selected patient. The software will check\n whether potential duplicate VistA patients exist and if so it will warn the\n user about it, as seen below (Patient Validation Screen):\n \n Edit Patient (Soft Stop):\n - For the VistA Provider it displays:\n ------------------------\n ... \n P Print H Hold UH Un Hold\n E Edit AV Accept Validation RJ Reject\n Select Item(s): Edit// e Edit \n \n VISTA PATIENT: PHWWDY,QLYJH H\n 1 PHWWDY,QLYJH H 01/31/1952 101021512 TOMBSTONE,ID\n 2 PHWWDY,QLYJH H 09/30/1930 101097105 CASA GRANDA,FL\n 3 PHWWDY,QLYJH H 05/04/1934 101068053 SHADY GROVE,DE\n Name, City, State, DEA# and Exp. (if any)\n CHOOSE 1-3: 1 PHWWDY,QLYJH H 01/31/1952 101021512 TOMBSTONE,ID\n Enrollment Priority: Category: IN PROCESS End Date: \n \n ****************************** WARNING(S) *****************************\n The following VistA Patient(s) has been identified as potential \n duplicate(s):\n 42211-PHWWDY,QLYJH H 09/30/1930 101097105 CASA GRANDA,FL\n 42737-PHWWDY,QLYJH H 05/04/1934 101068053 SHADY GROVE,DE\n **************************************************************************\n eRx Patient VistA Patient\nthe changes please refer to the documents listed in the Documentation section\n (e.g., AEXRFGRI,APSKACWHZ TORRINGTON,WY DEA#: AA4729919 (Exp: 01/01/24)\n ---------------------------------------+----------------------------------\n Name:MAT1,TEST8 |Name:PHWWDY,QLYJH H\n DOB :DEC 18, 2014 |DOB :JAN 31,1952\n Sex :MALE |Sex :MALE\n SSN :101127944 |SSN :101-02-1512\n Phone #: 2251230718 |Phone #: \n Address: |Address:\n 123 FAKE STREET #101 |3301 MC CONNELL DRIVE\n PLANO,TX 75025 |TOMBSTONE,ID 12345 \n ---------------------------------------+----------------------------------\n \n Would you like to use this patient? NO// \n \n \n Accept Validation (Soft Stop):\n -----------------------------\n ...\n Select Item(s): Next Screen// AV Accept Validation \n \n ******************************* WARNING(S) ***************************\n The following VistA Patient(s) has been identified as potential\n4. VistA Patient Suggestion\n duplicate(s):\n 42211-PHWWDY,QLYJH H 09/30/1930 101097105 CASA GRANDA,FL\n 42737-PHWWDY,QLYJH H 05/04/1934 101068053 SHADY GROVE,DE\n *************************************************************************\n Would you like to mark this patient as VALIDATED?\n Enter Yes or No: NO// \n \n15.New option: eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING] \n ---------------------------------------------------------------------------\n This new option was created to replace the option Complete Orders from eRx\n ---------------------------------------------------------------------------\n [PSO ERX FINISH]. The new option will have 100% of the functionality of the\n replaced option and some additional feature such as:\n \n a)Most of the prompts when entering the option have been converted into\n User Preferences changed after loading the list and can be saved by each\n user as their preferred View\n \n b)The header part of the option was modified to display information about\n the parameters used to compose the list, such as LOOK BACK DAYS, MAX.\n QUEUE SIZE, ERX STATUS, etc.\n When matching eRx Patient to a corresponding VistA Patient before the user\n \n c)The Grouping by CS (Controlled Substances) have a new format, which\n separates entries in the queue.\n \n d)The user will be able to more easily switch views between the Patient\n Centric and the Rx Medication queues via the PC and RX actions.\n \n e)Queue Search/Filter adds 3 new options in the Patient Centric View: RX#,\n VISTA PATIENT and MATCH STATUS.\n In addition, the interface for performing searches was changed to display\n is prompted for the VistA entry it will first be presented with suggestion\n information about the selected filters, including in the header part of \n the list. The current filters can easily be reset via the RF (Remove\n Filters) action.\n \n f)Queue Search/Filter adds 4 new options in the Medication View: RX#,\n VISTA PATIENT, VISTA PROVIDER and MATCH STATUS.\n \n g)The MATCH STATUS filter was added to the Patient Centric and Medication\n View and it has 4 different choices shown below:\n \n (if any) based on the following logic:\n 1 PATIENT FAIL - PATIENT NOT MATCHED\n 2 PROVIDER FAIL - PROVIDER NOT MATCHED\n 3 DRUG FAIL - DRUG NOT MATCHED\n 4 BASIC - PATIENT, PROVIDER AND DRUG MATCHED\n \n 1: Includes records where the patient has not been matched\n 2: Includes records where the provider has not been matched yet, but the \n patient is matched\n 3: Includes records where the drug has not been matched yet, but the\n patient and the provider are matched\n \n 4: Includes records with the patient, provider and drug matched\n \n Note: For a VA Medical Center site the list of choice will display \n differently:\n \n 1 PATIENT NOT MATCHED\n 2 PROVIDER NOT MATCHED\n 3 DRUG NOT MATCHED\n 4 PATIENT, PROVIDER AND DRUG MATCHED\n \n - Once a VistA Patient is matched and later validated to an eRx Patient it\n h)The header in the Patient Centric and Medication views will display\n information about the selected filters, as shown below: \n \n Rx Medication Queue Jan 28, 2023@15:46:17 Page: 1 of 1 \n LOOK BACK DAYS: 200 CS/NON-CS: BOTH (II-V) MAX. QUEUE SIZE: 999\n FILTERED BY: 01/08/23-01/18/23|PATIENT(TEST,PATIENT)\n _________________________________________________________________________\n # PATIENT DOB DRUG PROVIDER STA REC.DAT\n ...\n \n is then "remembered"\n Note: The current filters can easily be reset via the RF (Remove Filters)\n action.\n \n i)Queue Sorting was streamlined to allow the user to quickly sort the list\n through specific actions for each column and also allows for Descending\n Sorting (not available in the replaced option).\n \n j)The Change View (CV) action allows the user to reconfigure the way the\n list is displayed and allows them to save the configuration to be applied\n to que queue when they re-enter the option.\nof this description.\n \n \n k)A new action called Refresh (REF) was added to allow the user to\n re-display the queue. This feature allows the user view the latest\n 'locks' from other users that have been placed since the queue was last\n built.\n \n l)A new action called Change Look Back Days (LBD) was created to quickly\n allow the user to change the number of days to look back for records.\n \n m)A new action called Next Patient (NP) was created to assist users in\n - When a new eRx prescription is received for the same eRx Patient the\n selecting the next eRx Patient on the queue to be worked on without too\n many key strokes.\n \n n)A new action called Show/Hide Details (DET) under the Single Patient \n list will show/hide additional information about each one of the\n eRx on the list. It will display Qty, # of Refills, Days Supply and the\n SIG (medication instructions).\n \n o)A new action called Include All Statuses (IAS) under the Single Patient \n list will show/hide non-actionable statuses like Processed (PR), \n "remembered" VistA Patient(s) are then presented as suggestions for the\n Removed (RM), etc. Furthermore, a field on the header will indicate\n which statuses are being displayed: ALL or ACTIONABLE only.\n \n p)A new option is being added to the initial selection before entering the\n The new option is called Workload Processing (WP) and it is designed for\n processing the current workload in a FIFO (First In First Out) method.\n Instead of loading a list of patients (PC Centric Queue) or Prescriptions\n (Rx View), this option will automatically choose the patient with the\n oldest record to be worked on and will load it for the user to process\n their prescriptions. Once the user finishes processing the prescription\n user to select, as shown below (Validate Patient Screen - Edit action):\n for the first patient loaded they can choose the Next Patient (NP) action\n to move on to the next patient. This option will use the ERX DEFAULT\n LOOKBACK DAYS field (#10.2) in the OUTPATIENT SITE file (#59) to\n determine which one is the patient with the oldest record on file that\n needs to be worked on next. The record must be in one of these 3 \n statuses: New, In-Process or Wait.\n Additionally, this option allows the user to work on patients with\n specific records that match the criteria below (see g bullet above for\n more information on each filter):\n \n \n 1 PATIENT FAIL - PATIENT NOT MATCHED\n 2 PROVIDER FAIL - PROVIDER NOT MATCHED\n 3 DRUG FAIL - DRUG NOT MATCHED\n 4 BASIC - PATIENT, PROVIDER AND DRUG MATCHED\n 5 ALL (NO FILTERS) \n \n q)A new option was added to the Single Patient Queue: JB (Jump to\n Backdoor). Instead of jumping to the Complete Orders from OERR [PSO LMO\n FINISH] option it will jump to the Patient Prescription Processing [PSO\n LM BACKDOOR ORDERS option.\n Select Item(s): Next Screen// E Edit \n \n r)Within the Rx Medication Screen (or Rx List View Screen) the user will\n have the ability to easily filter the list by Message Type by selecting\n one of the following hidden actions.\n \n NEW New Rx's Only\n CR Change Request Only \n RXF Rx Refill Only \n IE Inbound Errors Only \n OE Outbound Errors Only\n |Sugg. 1 of 1 - 08/08/23|\n CA Cancel Rx's Only \n CN Cancel Response Only\n CX Change Response Only\n RRQ Renewal Request Only \n RRP Renewal Response Only\n ALL All Message Types\n \n Note: The same result can be accomplished via the SQ (Search Queue)\n action and selecting #7 and then the specific message type.\n \n ERX PATIENT VISTA PATIENT |From eRx#: 123123 |\n s)The NDC code will now be printed under the eRx Drug in the output print\n from the Print eRx action, as shown below:\n ...\n ***************PRESCRIPTION INFORMATION******************\n eRx Drug: MELOXICAM 15MG TAB \n NDC: 00378108901\n eRx Written Date: MAR 17, 2023 eRx Issue Date: \n ...\n \n t)The Remove eRx (RM) action will now work for eRx records that are \n ___________________________________________________________________________\n currently on Hold. Before, the user had to Un-Hold the record before\n removing it.\n \n u)The Jump to OP (JO) action only allowed the user to 'jump' to Backdoor\n Pharmacy option if the patient had pending orders to be finished. This\n restriction is being removed by this patch.\n \n16.INC25762338 - Broken eRx drug auto-match on RxRenewalResponses\n ---------------------------------------------------------------------------\n The ticket above will be addressed by this patch. This issue was caused by\n Name:OPEKXAQDY,XUISCSD |Name:OPEKXAQDY,XUISCSD F\n PSO*7*706 released on December 12th, 2022. This patch moved the\n auto-matching functionality of provider and drug from the Hub to VistA. \n However, the VistA did not implement drug auto-matching for \n RxRenewalResponse records forcing the users to match the VistA dispense\n drug manually. This patch will fix the issue by extending the VistA \n auto-matching functionality to RxRenewalResponse records as well.\n \n17.Routing field edit enabled for CS eRx orders\n ---------------------------------------------------------------------------\n Users will now be allowed to edit the Routing (Mail/Window) field for a CS\n \n DOB :DEC 18, 1970 |DOB :DEC 18, 1970\n eRx Pending order. Before, all field were un-editable in the OP Pending\n Order Queue because an audit is not captured. However, the Remarks field\n does not exist until created by the user in the OP Pending Order Queue.\n \n18.New Pending Order side-by-side interface for eRx orders\n ---------------------------------------------------------------------------\n Similar to the eRx Drug Validation screen shown above the view of a pending\n order that originated from an eRx will be displayed differently in the \n Patient Prescription Processing [PSO LM BACKDOOR ORDERS] and Complete\n Orders from OERR [PSO LMOE FINISH] options. When these option identify the\n Sex :MALE |Sex :MALE\n pending order an eRx prescription it will automatically switch the display\n of the data to a side-by-side viewing where the left side shows the eRx \n prescription information (from the outside doctor) while the right-side\n shows the VistA corresponding information.\n \n Besides displaying the information side-by-side, a few other features were\n introduced to make the screen more user friendly, such as:\n a) When there is a mismatch for field (e.g., Drug Name, Qty, etc.) the \n content of such field will display in reverse video for both fields,\n eRx and VistA.\n SSN :101127944 |SSN :101-13-4021\n b) The content will display in highlight in order to stand from the field\n label. \n \n Obs) These features depend on the terminal display settings being set\n differently for reverse video and highlighted font in order for it\n to work.\n \n Below is an example of how the new screen will be displayed (without the\n reverse or highlighted video features) for a new eRx Pending Order:\n \n Address: |Address:\n Pending OP Orders (ROUTINE) Aug 18, 2023@14:22:27 Page: 1 of 6 \n SPLYFX,KUNLYS JELUAHT\n PID: 101-02-4809 Ht(cm): 187.96 (12/28/2010)\n DOB: APR 28,1947 (76) Wt(kg): 112.94 (01/07/2011)\n SEX: MALE Non-VA Meds on File Last entry on 06/24/23\n CrCL: 53.8(est.) (CREAT: 1.51mg/dL 12/16/10) BSA (m2): 2.39 \n -------------------------------------------------------------------------\n ERX (123360) | VISTA PENDING ORDER \n -------------------------------------------------------------------------\n PATIENT MANUALLY-MATCHED | VALIDATED by TESTONE,USER01 on 8/17/23@14:51:21 \n 123 FAKE STREET #101 | 123 FLAKE ST SUITE 101\n Name: SPLYFX,KUNLYS JELUAHT |Name: SPLYFX,KUNLYS JELUAHT \n DOB : APR 28, 1947 |DOB : APR 28,1947 \n SSN : 101024809 |SSN : 101-02-4809 \n Sex : MALE |Sex : MALE \n __________________________________|_____________________________________\n |Pharmacy Narrative: \n |terbinafine ok x 90 days (5/06); \n |ROSIGLITAZONE; PANTOPRAZOLE; ZOLPIDEM \n __________________________________|_____________________________________\n Allergy: |Allergy: \n PLANO,TX 75025 | PLANO,TX 75025\n NO ALLERGY INFORMATION RECEIVED | NO KNOWN ALLERGIES \n __________________________________|_____________________________________\n PROVIDER AUTO-MATCHED | VALIDATED by TESTONE,USER01 on 8/17/23@14:51:40 \n Name: BLACKSTAD,GONZALO |Name: BLACKSTAD,GONZALO W \n NPI : 1891745550 |NPI : 1891745550 \n DEA : AV4538419 |DEA : \n __________________________________|_____________________________________\n DRUG MANUALLY-MATCHED | VALIDATED by TESTONE,USER01 on 8/17/23@14:51:55 \n Substitution? YES |1) Orderable Item: ***(N/F)*** \n Renewals? YES | PANTOPRAZOLE NA TAB,EC \n Primary Phone: 0236663417 |\n __________________________________|_____________________________________\n Drug: |2) Drug: ***(N/F)*** \n PANTOPRAZOLE NA 40MG EC TAB | PANTOPRAZOLE NA 40MG EC TAB UD \n |Drug Message: \n | NATL N/F; INCREMENT OF 100s \n __________________________________|_____________________________________\n SIG: |SIG: \n TAKE ONE TABLET BY MOUTH EVERY DAY| TAKE ONE TABLET BY MOUTH ONCE DAILY \n __________________________________|_____________________________________\n |3) *Dosage: 40 (MG) \n __________________________________|_______________________________________\n | Verb: TAKE \n | Disp. Units: 1 \n | Noun: TABLET \n | *Route: ORAL \n | *Schedule: ONCE DAILY \n __________________________________|_____________________________________\n |4)Patient Instruction: \n | \n __________________________________|_____________________________________\n Provider Notes/Comments: |Provider Comments: \n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (E)XIT: EXIT// \n __________________________________|_____________________________________\n |5) Pat.Status: OUTPATIENT CARE \n __________________________________|_____________________________________\n Date Written: AUG 10, 2023 |6) Issue Date: AUG 10,2023 \n Effective Date: |7) Fill Date: Sep 12, 2023 \n __________________________________|_____________________________________\n Days Supply: 30 |8) Days Supply: 30 \n __________________________________|_____________________________________\n Quantity: 30 |9) QTY (TAB): 30 \n Dispense Unit: | \n \n Qty Qualifier: Original Quantity | \n __________________________________|_____________________________________\n Refills: 5 |10) Refills: 5 \n __________________________________|_____________________________________\n |11) Routing: MAIL \n __________________________________|_____________________________________\n |12) Clinic: \n __________________________________|_____________________________________\n Provider: PROVIDER, TEST W |13)Provider: PROVIDER,TEST W \n __________________________________|_____________________________________\n1. Lock Timeout Change (MbM ONLY)\n - The left column has information about the eRx Patient while the right\n |14)Copies: 1 \n __________________________________|_____________________________________\n |15)Remarks: \n __________________________________|_____________________________________\n eRx Received on 9/20/23@11:44 | Accepted by TEST,USER on 9/26/23@10:30\n \n Below is an example of how the new screen will be displayed (without the\n reverse or highlighted video features) for a renewal eRx Pending Order:\n ---------------------------------------------------------------------------\n \n column has information about the VistA Patient. The 'Last Match' field\n Prescription Renew Sep 12, 2023@14:28:50 Page: 1 of 1 \n OUTDYX,JALN ILAH <A> \n PID: 101-16-5191 Ht(cm): 182.88 (02/24/2011)\n DOB: JUN 21,1954 (69) Wt(kg): 93.44 (02/24/2011) \n +--------------------------------------------------------------------------\n PATIENT MANUALLY-MATCHED | VALIDATED by TESTONE,USER01 on 8/11/23@14:31:33\n Name: VAMC,PATIENT8 |Name: OUTDYX,JALN ILAH\n DOB : JUN 21, 1954 |DOB : JUN 21,1954\n SSN : 101165191 |SSN : 101-16-5191\n Sex : MALE |Sex : MALE\n indicates the last time the VistA Patient was matched to the eRx Patient\n _______________________________________|___________________________________\n |Pharmacy Narrative: \n _______________________________________|___________________________________\n Allergy: |Allergy:\n NO ALLERGY INFORMATION RECEIVED | Verified:\n | IBUPROFEN,PERCODAN,VALIUM\n _______________________________________|___________________________________\n PROVIDER AUTO-MATCHED/EDITED | VALIDATED by TESTONE,USER01 on 8/16/23@14:49\n Name: TESTONE,USER02 |Name: TESTONE,USER01\n NPI : 1033270160 |NPI : \n and validated. When a corresponding field does not match it will display\n DEA : AV4538419 |DEA : \n _______________________________________|___________________________________\n DRUG MANUALLY-MATCHED | VALIDATED by TESTONE,USER01 on 8/16/23@14:50:55\n Substitution? YES |Orderable Item: \n Renewals? YES | MELOXICAM TAB\n _______________________________________|___________________________________\n Drug: |CMOP Drug: \n MELOXICAM 7.5MG TAB | MELOXICAM 7.5MG TAB\n |Drug Message:\n | NATL FORM (2/10)\n in reverse video.\n _______________________________________|___________________________________\n SIG: |SIG:\n TAKE 1 TABS ORALLY ONCE DAILY | TAKE ONE TABLET BY BY MOUTH ONCE \n | DAILY WITH FOOD - IF SPLITTING \n | TABLET, SPLIT JUST PRIOR TO USE\n _______________________________________|___________________________________\n | *Dosage: 15 (MG)\n | Verb: TAKE\n | Disp. Units: 1\n | Noun: TABLET\n \n | *Route: ORAL\n | *Schedule: ONCE DAILY-WITH FOOD\n _______________________________________|___________________________________\n |Patient Instruction:\n | - IF SPLITTING TABLET, SPLIT JUST\n | PRIOR TO USE\n _______________________________________|___________________________________\n Provider Notes/Comments: |Provider Comments:\n _______________________________________|___________________________________\n |Pat.Status: OUTPATIENT CARE\n - When presented with a suggestion the user is given 3 options: (A)ccept,\n _______________________________________|___________________________________\n Date Written: AUG 09, 2023 |1) Issue Date: Aug 09, 2023\n Effective Date: |2) Fill Date: Sep 12, 2023\n _______________________________________|___________________________________\n Days Supply: 30 |Days Supply: 30\n _______________________________________|___________________________________\n Quantity: 30 |QTY (TAB): 30\n Dispense Unit: |\n Qty Qualifier: Original Quantity |\n _______________________________________|___________________________________\n (F)orget or (E)xit:\n Refills: 11 |3) Refills: 11\n _______________________________________|___________________________________\n |4) Routing: MAIL\n _______________________________________|___________________________________\n |5) Clinic: \n _______________________________________|___________________________________\n Provider: TESTONE,USER02 |6) Provider: TESTONE,USER02\n _______________________________________|___________________________________\n |7) Copies: 1\n _______________________________________|___________________________________\n \n |8) Remarks: \n | RENEWED FROM RX # 2297959\n _______________________________________|___________________________________\n eRx Received on 9/20/23@11:44 | Accepted by TESTONE,USER01 on 9/26/23@10:30 \n \n19.Ticket INC28342622 - PSOERXR1 - DEA # display\n ---------------------------------------------------------------------------\n After the release of patch PSO*7*545 it was reported that the VistA \n Provider DEA# was no long being displayed on the eRx Holding Queue Display\n screen. This addresses the problem.\n ACCEPT - Accepts the suggested VistA Provider and matches it to the eRx\n \n20.Ticket INC28554236 - Un-Accept/EC/HC Hold Issue\n ---------------------------------------------------------------------------\n It was reported that an eRx record was wrongly automatically being marked\n as PR (PROCESSED) after the user un-accepted an order from the Pending \n Queue back into the eRx Holding Queue and a placed a Change Request for it.\n The PR status was assigned as soon as the user removed the eRx record from\n Hold.\n ---------------------------------------------------------------------------\n FORGET - Forgets this suggested VistA Provider so that it is not \n presented again in the future to any user\n EXIT - Exits and proceed to match the VistA Provider manually\n \n If more than one suggestion exists, then a 4th option is included: (N)ext:\n \n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (N)EXT (E)XIT: EXIT// \n \n NEXT - Ignores the current suggestion and view the next one" \n \n\n
\nThis patch addresses the following issue:\n-----------------\nSSH\n Key Pair you can skip this step. You can check whether you already\n have an existing SSH Key Pair through the 'V' (View Public SSH \nKey)\n Action.\n \n Encryption Type: DSA, RSA, ECDSA or EDDSA?\n -----------------------------------\n Digital Signature Algorithm (DSA) (No longer supported) and \nRivest,\n \n Shamir & Adleman (RSA) have been two of the most common encryption\n algorithms used by the IT industry for securely sharing data. \n Elliptic Curve Digital Signature Algorithm (ECDSA) and \nEdward-curve\n Digital Signature Algorithm (ed25519) are more complex public key\n cryptography encryption algorithms that are now supported by the \nVA.\n Many of SPMP servers can handle all types; however there are \nvendors\n that accept only one specific type. You will need to contact the \nFiles & Fields Associated:\nSPMP\n vendor support to determine which type to select.\n \nStep 2: Share the Public SSH Key content with the state/vendor. In order \nto\n successfully establish SPMP transmissions the state/vendor will \nhave\n to install/configure the new SSH Key created in step 1 for the\n user id they assigned to your site. Use the 'V' (View Public SSH \nKey)\n \n Action to retrieve the content of the Public SSH key. The Public \nSSH\n Key should not contain line-feed characters, therefore after you \ncopy\n & paste it from the terminal emulator into an email or text editor\n make sure it contains only one line of text (no wrapping).\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nSPMP STATE PARAMETERS SFTP SSH KEY ENCRYPTION Modified\n(#58.41) (#19) \n \nProblem:\n \n--------\nWith the implementation of Red Hat Enterprise Linux (RHEL 8) stronger \nencryption keys ECDSA & EDDSA are now available and supported. SPMP \napplication currently is using RSA type SSH key for connecting to the \nSPMP server to send data. \n \nNew keys added:\nElliptic Curve Digital Signature Algorithm (ECDSA)\nEdward-curve Digital Signature Algorithm (ed25519)\n \nECDSA Key creation\nEDDSA is also known as ed25519 \n \nNecessary changes are required to allow creation of ECDSA & EDDSA keys \nfor the SPMP application. Support for RSA keys are anticipated to be \ndeprecated in the future, so to maintain Vista's security posture and \nensure continuous operation of required Vista processes, software \nutilizing SSH PKI user keys must be updated to support the stronger ECDSA \n& EDDSA encryption keys. \n \nThe modification should allow the creation of any ECDSA & EDDSA keys to \n \nbe \nforward compatible when Red Hat Enterprise Linux (RHEL 8) is implemented.\n \nResolution:\n-----------\nFile SPMP STATE PARAMETERS (#58.41) field SFTP SSH KEY ENCRYPTION (#19) is\nmodified to add code ECDSA (Elliptic Curve Digital Signature Algorithm) & \nEDDSA (Edward-curve Digital Signature Algorithm).\n \nModify PSOSPMKY to allow ECDSA or EDDSA (ed25519) key to be created,\nDefect Tracking System Ticket(s) & Overview:\nviewed, deleted, and update the help text.\n \n \nTechnical Resolution:\n---------------------\nAdd Code ECDSA (Elliptic Curve Digital Signature Algorithm) & EDDSA \n(Edward-curve Digital Signature Algorithm) to the set of codes for field \n#19 in file #58.41\n \nRoutine PSOSPMKY is modified as follows\n \n \nACTION+24 is changed from\n . S DIR(0)="S^DSA:Digital Signature Algorithm (DSA);RSA:Rivest, Shamir \n& Adleman (RSA)"\nTo\n . S DIR(0)="S^RSA:Rivest, Shamir & Adleman (RSA);DSA:Digital Signature \nAlgorithm (DSA);ECDSA:Elliptic Curve Digital Signature Algorithm \n(ECDSA);EDDSA:Edward-curve Digital Signature Algorithm (ed25519)" ;p723\n \nACTION+26 changed from\n1. INC26749697 - ECDSA KEY CREATION\n .S ENCRTYPE=Y\nTo\n .S ENCRTYPE=Y I Y="DSA" D Q\n .. W !!,$G(IOBON),"WARNING:",$G(IOBOFF)," 'DSA' SSH keys are no longer \nsupported.",$C(7) \n \nNEWKEY+9 is changed from\n I $G(ENCRTYPE)'="DSA",$G(ENCRTYPE)'="RSA" S ENCRTYPE="RSA"\nTo\n S \n \nENCRTYPE=$S($G(ENCRTYPE)="ECDSA":"ECDSA",$G(ENCRTYPE)="EDDSA":"ed25519",1:\n"RSA")\n \nNEWKEY+63 is changed from\n S DR="18///"_$S(PSOOS["VMS":"SSH2",1:"OSSH")_";19///"_ENCRTYPE D ^DIE\nTo \n S DR="18///"_$S(PSOOS["VMS":"SSH2",1:"OSSH")_";19////"_ENCRTYPE D ^DIE\n \nThe Help text is change to:\n \nPatch Components:\nSecure SHell (SSH) Encryption Keys are used to automate the data \ntransmission\nto the State Prescription Monitoring Programs (SPMPs). Follow the steps \nbelow\nto successfully setup SPMP transmissions from VistA to the state/vendor \nserver:\n \nStep 1: Select the 'N' (Create New SSH Key Pair) Action and follow the \nprompts\n to create a new pair of SSH keys. If you already have an existing \n\n
\nThis patch addresses the following issue:\n Duplicate: INC26949869\n Outpatient, not linked to Pharmacy orderable item, & not a \n controlled substance in #50.\n I '$D(DRGARY(LDIEN)) S DRGARY(LDIEN)="",DRLCNT=DRLCNT+1\n - At this point if DRLCNT>0, I send all matched drugs in DRGARY \n (minus the drug already presented to the user) to ^DIR and prompt to\n Select Drug from list (#-#) or <enter> to make a new selection: \n - If a drug is selected then ask, Would you like to use this drug?\n If the answer is Y, then that drug IEN is returned \n - If the user answers N or DRLCNT=0 after all the matching logic,\n call SELECT and prompt to 'Select Drug:' and do not offer any that are\n \n inactive, not for outpatient use, not associated with a Pharmacy \n Orderable Item or a controlled drug (DEA Schedules 2-5) in file #50.\n \nProblem:\n--------\nThe original reported issue was that the drug matching logic \nforced an incorrect drug selection. The OneVA Rx sent dose for Nasal \nSpray. The pharmacist inadvertently accepted the bad drug with dose form\ntablet, likely because it was the only choice offered.\n \n \n \nResolution:\n-----------\nThis patch will enhance the drug lookup logic. The pharmacist will be \npresented with local Drug file lookup. Routine PSORRX1 is modified \nto mostly rewrite the DRUGMTCH subroutine.\n \n \nHere is a list of requirements that are requested\n 1. If VA Product Identifier is received from HDR, the user is \nINCORRECT DRUG LINKED IN AUTOMATED DISPENSING SYSTEM FROM ONEVA\n presented with the message:\n \n Remote site VA PRODUCT IDENTIFIER: VA Product Identifier *** NOT\n FOUND ***"\n 2. The VA Product Identifier that is returned from the HDR for then\n host site drug item is used to identify the VA Product that the host\n site drug is matched to. If the VA PRODUCT ID matches a product in \n file VA PRODUCT (#50.68) that is marked as a controlled substance in\n field CS FEDERAL SCHEDULE (#19) (1-5), a message indicates that\n Controlled substances are not allowed for ONEVA dispensing, and\n \n processing stops.\n 3. If there is a single drug match using the Drug name returned from \n HDR and the VA PRODUCT ID, that is active, for outpatient use,\n associated with a Pharmacy Orderable Item, and and not a \n controlled substance in file #50, it is presented to the\n user, with the prompt, 'Would you like to use the system matched drug\n for this refill/partial fill? NO//' If the drug presented is not\n accepted or there was more than one drug found that was a match,\n processing will continue to step 3.\n 4. Next through the "APR" cross-reference in the Drug File which is on \n \n the PSNDF VA PRODUCT NAME ENTRY Field (#22) is used to find all drug\n entries at the dispensing site that are matched to the same VA\n Product as the host site drug selected for OneVA processing. \n Eliminate any that are inactive, not marked for outpatient use, does\n not have a Pharmacy Orderable Item or is a controlled substance in \n file #50. Present the drugs and prompt the user to 'Select \n drug from list (#-#) or <enter> to make a new selection:'\n 5. If no matching drug could be located, a drug wasn't selected or \n no drugs were found, the user is presented the message:\n \nDefect Tracking System Ticket(s) & Overview:\n No other local match could be found for DRUG NAME\n You may need to update your Drug file to process this order"\n \n Type <Enter> to continue or '^' to exit:\n \n NOTE: If no VA Product Identifier is received from HDR this message\n will display after the message in step 1.\n \n \n \n \nTechnical Resolution:\n---------------------\nRoutine PSORRX1 is modified to mostly rewrite the DRUGMTCH subroutine.\nHere is how the logic will function after the patch: \n - Look for VAPID in ^PSNDF(50.68,"C" index and \n S VAPIEN=$O(^PSNDF(50.68,"C",VAPID,0))\n - Check if the product found in file 50.68 is for a controlled \n substance. Using field CS FEDERAL SCHEDULE (#19). If the field\n contains any value less then 6 and greater than 0, display message\n and quit:\n1. INC27427008 - INCORRECT DRUG LINKED IN AUTOMATED DISPENSING \n S CSSCH=$$GET1^DIQ(50.68,VAPIEN,19,"I")\n I +CSSCH>0,+CSSCH<6 D Q 0\n . W !!,"Controlled substances are not allowed for ONEVA dispensing.",!\n . D PAUSE^VALM1\n - If the received VA PRODUCT ID is not found, display "Remote site\n VA PRODUCT IDENTIFIER: xxxxxxx *** NOT FOUND ***" (processing will\n quit out when VAPID not found after skipping over the )\n - Then use DRGNM and loop thru ^PSDRUG("B",DRGNM) and save\n any entries found into DRGARY(LDIEN) and increment counter DRLCNT. \n filter out drugs that are inactive, not for outpatient, not \n SYSTEM FROM ONEVA\n associated with a Pharmacy Orderable Item, not linked to the VA\n Product ID, and is not a controlled in file #50.\n - If only one product is found matching the above criteria, present \n it to the user with the prompt 'Would you like to use the system\n matched drug for this refill/partial fill? NO//'\n - If the user answers Yes processing ends by returning the product's \n IEN to the calling process.\n \nThe following are only done when VAPIEN exists:\n - Loop thru the APR index of file 50 and filter out inactive, not for \n\n\nBackup of PSO*7.0*729 on Jan 25, 2024\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses one issue:\n \nWhen editing the drug on a prescription, the drug is not saved if more \nthan one prescription was specified at the start of the editing process.\n\n
\nThis patch is being released to address a few small eRx related issues\n \n1. eRx statuses CAH (CANCEL COMPLETED IN HOLDING QUEUE) and CAO (CANCEL\n PROCESS COMPLETE) not being treated as 'Actionable' in the new eRx Holding\n Queue Processing option [PSO ERX QUEUE PROCESSING]\n ---------------------------------------------------------------------------\n The new eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING] option was\n not considering eRx records with the statuses CAH and CAO as actionable.\n This caused patients not to be listed on the Patient Centric view when they\n only had these types of actionable records. This patch fixes this problem\n by treating CAH and CAO statuses as actionable.\nencountered after the patch PSO*7*700 was released:\n \n2. Hidden Action RR (RxRenewal Request) under OTH disappeared\n ---------------------------------------------------------------------------\n After the installation of PSO*7*700 the hidden action RR (RxRenewal\n Request) was unintentionally removed from the Other OP Action (OTH hidden\n action) when the user was viewing a single prescription in Backdoor \n Pharmacy (options PSO LM BACKDOOR ORDERS and PSO LMOE FINISH). This patch\n adds the RR hidden action back.\n \n3. <UNDEFINED> error at VIDEO+4^PSOERUT0\n \n ---------------------------------------------------------------------------\n An <UNDEFINED> was being recorded when the user ran the Complete Orders\n from OERR and selected NO at the prompt 'Do you want to see Medication\n Profile?' when there were patient with eRx pending orders to be finished.\n This patch will fix this issue and the error will no longer happen.\n \n4. CPRS ORDERING INSTITUTION prompt\n ---------------------------------------------------------------------------\n Upon entering the new eRx Holding Queue Processing [PSO ERX QUEUE\n PROCESSING] option the users of some sites were being prompt for the CPRS\n - eRx statuses CAH (CANCEL COMPLETED IN HOLDING QUEUE) and CAO (CANCEL\n ORDERSING INSTITUTION as shown below.\n \n There are multiple Institutions associated with this Outpatient Site for\n finishing orders entered through CPRS. Select the Institution for which\n to finish orders from. Enter '?' to see all choices.\n \n Select CPRS ORDERING INSTITUTION: BEDFORD VAMC// \n \n This prompt was accidentally added to this option and it will be removed\n with this patch.\n PROCESS COMPLETE) not being treated as 'Actionable' in the new eRx Holding\n Queue Processing option [PSO ERX QUEUE PROCESSING]\n - Hidden Action RR (RxRenewal Request) under OTH disappeared\n - <UNDEFINED> error at VIDEO+4^PSOERUT0\n - CPRS ORDERING INSTITUTION prompt\n\n
\nThis patch corrects the following problems when using the Site Parameter\nNAME: ALBANY//. Deleting a site could lead to an "undefined error" problem\nas reported in NOIS AMA-0700-71379. This patch prevents the users from\ndeleting a site.\n \nThis patch also updates the Data Dictionary of the NAME field (#.01) of\nthe OUTPATIENT SITE file (#59).\nEnter/Edit [PSO SITE PARAMETERS] option:\n \n1) The dialog "Would you like to see all site parameters for this\ndivision? Y//", only responds to upper case "Y". Now the routine is\npatched to accept both upper and lower case responses of "y".\n \n2) Currently the users have the option of deleting a site from the\nOUTPATIENT SITE file (#59) by entering "@" key at the dialog\n\n
\nThis patch will resolve the following issue:\n \nAn error is preventing users from finishing pending CPRS orders on VistA \nwhen utilizing option 'Complete Orders from OERR' (PSO LMOE FINISH).\n \nThe error occurs when the user selects controlled substances as a \nsecondary filter along with one of the schedule options.\n\n
\nBackup of PSO*7.0*671 on Mar 25, 2024\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will resolve the following issue:\n \nA site reported that when they fill some OneVA prescriptions from other \nVA host sites into their ScriptPro via OPAI interface, the dispense drug\ncomes across as UNKNOWN in ScriptPro. \n\n
\nThe OneVA Pharmacy application provides the Veterans Health \npatient's active and refillable prescriptions. The HDR/CDS provides a\npatient's active and refillable prescriptions. The OneVA Pharmacy message\nflow enables the secure, bi-directional exchange of electronic health\nrecords between local/remote VistA Servers, and between VistA servers and\nHDR.\n \nThe OneVA software currently uses IBM Websphere as the messaging system. \nThe IBM Websphere messaging system is being decommissioned. This patch \nprovides the move from using IBM Websphere to using the Veterans Data \nInformation Exchange (VDIF).\nAdministration (VHA) with the capability to allow Veterans travelling \n \nThe software changes include the following:\n1. Routine PSORRX1 - DNS value modified at REMOTERX+18\n2. Routine PSORRX1 - modified argument list and corresponding references \n to the DRUGMTCH function\n3. Routine PSORRX1 - modified to handle HL7 messages with possible \n overflow nodes at RXPRSE+4\n4. Routine PSOHLDS6 - modified to handle HL7 messages with possible\n overflow nodes at HOST+2 \n5. Routine PSOORUT1 - modified "PROVIDER HOLD" status abbreviation from \nacross the United States to refill/partial fill their active VA\n "PH" to "HP" at SHOWREM+13\n6. Routine PSOORUT1 - added "DISCONTINUED BY PROVIDER", "DISCONTINUED\n (EDIT)", and "NON-VERIFIED" status abbreviations at SHOWREM+13\n7. HL LOGICAL LINK entry - the post-install routine POST^PSO736PO updates\n the PSORRXSEND entry of the HL LOGICAL LINK (#870) file. The following\n fields will be updated to reflect VDIF production IP address and port \n values when installed in the site's production account: DNS DOMAIN,\n TCP/IP ADDRESS, and TCP/IP PORT\nprescription at any VA Pharmacy regardless of where the prescription\noriginated. The OneVA Pharmacy application design consists of 3 main\ncomponents: VistA Medication Profile screen, Health Data Record Clinical\nData Service (HDR/CDS), and OneVA Pharmacy message flow. The VistA\nMedication Profile screen expands available pharmacy information in VistA\nto provide pharmacists direct access to query, and refill/partial fill\n\n
\nDefect Tracking System Ticket(s) & Overview:\nrecord in the file DEA NUMBERS (#8991,9) is encountered that has no value \nfor the NAME (PROVIDER OR INSTITUTION) field (#1.1). This error can occur \nwhen running the report as a Delimited File. The error does not happen \nwhen the report is run as a Report.\n \n \nResolution:\n-----------\nThe error occurs because the Delimited File output uses the NAME field \n1.1 in the DEA NUMBERS file #8991.9, which can be null. The Report \n \noutput uses the NAME field #.01 in the NEW PERSON file which is always \npopulated. This patch prevents the error by modifying routine PSODEARV \nto use the NAME field #.01 in the NEW PERSON file when building the \ndelimited output.\n1. INC28842900 - <SUBSCRIPT>COMPILE+24^PSODEARV\n \n \nProblem:\n--------\nWhen running the report DEA Expiration Date Report [PSO EPCS EXPIRE DATE \nREPORT] a subscript error <SUBSCRIPT>COMPILE+24^PSODEARV can occur when a \n\n
\nThe Application Programmer Interface (API PSOVCCA) used by CRM/VSE for\nrefilling a prescription, there is a rare possibility that the \nprescription may be locked in VistA, which means updates aren't \npermitted at that time. This is not properly communicated back to the\ncalling program. This patch will now return "-8 - Prescription unavailable\n- try again later".\n\n
\nSee FORUM patch description.\n\n
\nThis patch addresses the following incident ticket:\n \nProblem(s):\n-----------\nFor eRx prescriptions, the ORDER DEA ARCHIVE file (#101.52) DEA # field \n(#10) is missing. When an eRx order is accepted in the eRx Holding \nQueue, the DEA # is not populated when sending the data to file \n(#101.52). The logic currently does not populate the DEA # when the\nProvider's expiration date is the same date as the eRx prescription's\nwritten date. \n \n \n \nResolution:\n-----------\nThis will need to be addressed with changes to Outpatient Pharmacy code\nroutine PSOHLSNC is modified to send the DEA# in the RXE segment piece 14,\nwhich is already mapped on the CPRS side (according to the ORDEA Routine).\n \n \nTechnical Resolution:\n---------------------\nINC24400778 - Missing DEA number in Order DEA Archive the ORDER DEA \nRoutine PSOHLSNC is modified starting at RXE tag line 12:\n \nNew logic added:\n I $$GET1^DIQ(52.49,PSOIEN,95.1,"I"),$$CS^PSOERXA0(PSOHNDD) D\n . S PSOWRDT=$$GET1^DIQ(52.49,PSOIEN,5.9,"I") S \nPSOXFLD(13)=$P($$DEA^XUSER(0,PSOHPRO,PSOWRDT),"-",1)\nARCHIVE file (#101.52).\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC24400778 - Missing DEA number in Order DEA Archive File #101.52.\n \n\n
\nThis patch addresses the following issue:\n \nProblem:\n--------\nWhen copying a titration order, at the duration prompt, which was 2W \n(2weeks). It did not honor the defaults. It kept on repeating no more \nthan 2 days. And the user is stuck on the Limited Duration prompt.\n \nThe problem was found to be due to code from patch PSO*7*457, which was \npart of a clozapine enhancement that is no longer valid and was only \nmeant for a clozapine order. Patch PSO*7*574 added logic that skips the \n \nlogic added by PSO*7*457, unfortunately, it causes problems when copying \nan order defined with a limited duration.\n \nResolution:\n-----------\nThe resolution is to comment out the logic from PSO*7*457 in DUR^PSOORED5.\n \n \nTechnical Resolution:\n---------------------\nISSUE WITH COPYING A LIMITED DURATION ORDER\nThe code found at line DUR+8^PSOORED5 through line DUR+17^PSOORED5 is \ncommented out.\n \nThe code is changed from:\n \n \n;/RBN Begin modification for #326 ;/MZR Added a message and correct \nchecking for Hours/Minutes\n I $G(DIR("B"))!$G(PSORXED("DURATION",ENT)) N Z,MAX D I Z>MAX S \nPSORXED("DURATION",$G(PSORXED("ENT")))=MAX G DUR\n \n .I X=+X S Z=X\n .E S \nZ=$E(X,$L(X)),Z=$S(Z="L":30*X,Z="W":7*X,Z="H":X/24,Z="M":X/1440,1:+X)\n .S MAX=$S($G(DIR("B")):+DIR("B"),1:$G(PSORXED("DURATION",ENT)))\n .I Z>MAX D\n ..W " \n("_$S(X["L":"MONTHS",X["W":"WEEKS",X["H":"HOURS",X["M":"MINUTES",1:"DAYS")\n_")"\n ..W !,"NOT MORE THAN ",MAX," DAYS"\n ;; END NCC REMEDIATION << 457*RJS\n \n \nTo:\n \n ;PSO*7*754 comment out code added with PSO*7*457\n ;; START NCC REMEDIATION >> 457*RJS - ADJUST FOR 4 DAY SUPPLY\n ;/RBN Begin modification for #326 ;/MZR Added a message and correct \nchecking for Hours/Minutes\n ;I $G(DIR("B"))!$G(PSORXED("DURATION",ENT)) N Z,MAX D I Z>MAX S \nPSORXED("DURATION",$G(PSORXED("ENT")))=MAX G DUR\n ;.I X=+X S Z=X\nDefect Tracking System Ticket(s) & Overview:\n ;.E S \nZ=$E(X,$L(X)),Z=$S(Z="L":30*X,Z="W":7*X,Z="H":X/24,Z="M":X/1440,1:+X)\n ;.S MAX=$S($G(DIR("B")):+DIR("B"),1:$G(PSORXED("DURATION",ENT)))\n ;.I Z>MAX D\n ;..W " \n("_$S(X["L":"MONTHS",X["W":"WEEKS",X["H":"HOURS",X["M":"MINUTES",1:"DAYS")\n_")"\n ;..W !,"NOT MORE THAN ",MAX," DAYS"\n ;; END NCC REMEDIATION << 457*RJS\n \n1. INC31444921 - ISSUE WITH COPYING A LIMITED DURATION ORDER\n \n\n\n \n2. Another problem occurred when using the Pull Early from Suspense option.\nIf the routing was changed while pulling a prescription from suspense,\nthen a "^" was entered at the Label prompt, the original routing was\nnot restored to the prescription, which caused prescriptions that\nwere originally intended to be filled at the CMOP to be printed locally.\n \nRoutines: PSOLBL, PSORXL, PSOSUPAT, PSOSUPOE, PSOSUPRX\n \n3. When sites have install the CMOP package but are not actively transmitting\nto a host facility and reinstates discontinued prescriptions with a drug that\n1. This patch fixes problems involving pulling prescriptions from suspense\nhas been marked for use for CMOP they are being suspended for transmission to a\nCMOP host facility. Routine: PSOCAN2\n \n4. A problem occurred when trying to discontinue Pending orders for a patient\nby using the Discontinue Prescription(s) option. Routine: PSOCAN1\nto fill locally that were originally suspended for CMOP. If a prescription\nis suspended for CMOP, and is pulled from suspense using the Patient\nPrescription Processing option, then an up-arrow is entered when the user\nis prompted for a label action, the CMOP INDICATOR field in the RX SUSPENSE\nFile would have been set to "P", for PRINTED LOCALLY, although the label\nnever printed\n \n\n
\n1) When using the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION\nprovided by the Integration Agreement (IA) 1281. Currently this entry\npoint does a form feed at the beginning of the report. The AICS\npackage requests that this form feed be suppressed. Now the routine is\npatched to suppress a form feed at the beginning of the report when the\npassing variable PSONOPG (as per IA 1281) is set to 2.\nPROFILE] option, the FILL DATE field (#22) of the PRESCRIPTION file (#52) \nin the report, at times shows the date as "--1700". This is because the\nFILL DATE field (#22) of the PRESCRIPTION file (#52) is set to null when\nthe original prescription is on HOLD status. This patch fixes this\nproblem.\n \n2) The AUTOMATED INFO COLLECTION SYS (AICS) package requests a\nmodification to routine PSOSD1. Access to the entry point DFN^PSOSD1 is\n\n
\nSee FORUM for patch description.\n\n
\nThe Inbound Electronic Prescribing (eRx) Phase 2 Enhancements delivered in this\n \n \n1. (HDSO-7262) New eRx RX CHANGE REQUEST user interface\n ---------------------------------------------------------------------------\n The current eRx Change Request (EC) is being significantly improved to \n facilitate the submission of RX CHANGE REQUEST messages to the prescriber.\n Below is a list of modifications delivered in this patch: \n \n a)When the user selects the CHANGE REQUEST CODE D - DUE (Drug Use \n Evaluation), they will be prompt to select a CHANGE REQUEST SUB-CODE as \n shown below: \nFile Name (#) Field Name (#) New/Modified/Deleted \n . . .\n Select one of the following: \n \n D DUE (Drug Use Evaluation) \n G Generic Substitution \n OS Out of Stock \n P Prior Authorization Required \n S Script Clarification \n T Therapeutic Interchange/Substitution \n U Prescriber Authorization \n----------------- ---------------- --------------------\n \n CHANGE REQUEST CODE: d DUE (Drug Use Evaluation) \n \n Select one of the following: \n \n AR - Adverse Drug Reaction \n DA - Drug-Allergy \n DD - Drug-Drug Interaction \n DI - Drug Incompatibility \n DR - Dose Range Conflict \nERX SERVICE REASON CODES (#52.45) Modified \n HD - High Dose \n ID - Ingredient Duplication \n LD - Low Dose \n MS - Missing Information/Clarification \n PS - Product Selection Opportunity \n SX - Drug-Gender \n TD - Therapeutic \n TP - Payer/Processor \n UD - Duplicate Drug \n \n CHANGE REQUEST REASON TEXT (#20) New \n Type '?' for the full list. \n . . .\n \n b)The code G - Generic Substitution will always be available for selection \n and in case the user selects this code for an eRx that already allows \n substitution the following message will display: \n . . . \n CHANGE REQUEST CODE: G Generic Substitution \n \n Substitutions are already allowed by prescriber for this eRx. \n \n \n CHANGE REQUEST CODE: \n . . .\n \n c)A new field called NOTE TO PROVIDER will be presented to the user after \n the code (and sub-code) is answered. It's a word-processing field and it\n will be pre-populated for most codes/sub-codes selected with a \n pre-defined template text. Some pre-defined texts contains place holders\n such as [ADD_TEXT_HERE] and [DRUG_NAME] that must be replaced with the \n actual information before proceeding. \nERX HOLDING QUEUE (#52.49) Modified \n . . .\n CHANGE REQUEST CODE: s Script Clarification \n \n =[ WRAP ]=[INSERT ]======< NOTE TO PROVIDER >=[Press <PF1>H for help]====\n The eRx is missing or unclear on [ADD_TEXT_HERE], Please edit and respond\n or cancel Rx and send a new prescription with the requested information. \n \n =======T=======T=======T=======T=======T=======T=======T=======T=======T=\n Saving Text... \n \n FUTURE FILL HOLD DATE (#6.7) New\n The place holder [ADD_TEXT_HERE] must be replaced before proceeding. \n \n Press Return to continue: \n \n =[ WRAP ]=[INSERT ]======< NOTE TO PROVIDER >=[Press <PF1>H for help]====\n The eRx is missing or unclear on [ADD_TEXT_HERE], Please edit and respond\n or cancel Rx and send a new prescription with the requested information.\n \n =======T=======T=======T=======T=======T=======T=======T=======T=======T=\n \n CHANGE REQUEST REASON TEXT (#317) New \n d)Users will now be allowed to send more than one change request for the \n same eRx. The software will inform the user that one (or more) Change \n Request(s) has already been sent for the eRx right after they select EC\n (eRx Change Request) and will allow them to proceed, as shown below: \n \n 2 Rx Change Requests have already been sent for this eRx. \n \n e)Users will be able to enter up to 9 different drug suggestions, before\n it was limited to a maximum 3 entries. \n \n CH REQ PROGRESS NOTE REF # (#320.1) New\n f)The interface for entering drug suggestion was improved to easily allow \n the user to view, edit and delete entries before submitting the RX CHANGE\n REQUEST to the prescriber, as shown below: \n ... \n Select Drug Suggestion Option: (N)EW (F)INISH: NEW \n \n Select one of the following: \n \n E USE ERX DRUG \n V CHOOSE A VISTA DRUG \npatch is a continuation effort to convert all of the MbM Class 3 modifications\n CH REQ PROGRESS NOTE COMMENT (#320.2) New\n \n DRUG SELECTION: E USE ERX DRUG \n \n eRx Drug: ACETAMINOPHEN 325MG TAB UPN: 00069306030 \n \n SUBSTITUTIONS? YES// \n QUANTITY: 120// \n \n Select one of the following: \n \n \n 38 Original Quantity \n 40 Remaining Quantity \n 87 Quantity Received \n QS Quantity sufficient as determined by the disp. pharmacy\n QT Quantity Transferred \n CF Compound Final Quantity \n UQ Central Fill Unit of Use Quantity \n \n QTY QUALIFIER: 38// Original Quantity \n QTY UNIT OF MEASURE: TABLET DOSING UNIT C48542 TABLET DOSING UNIT \nSTATUS HISTORY Sub file (#52.4919) Modified\n DAYS SUPPLY: (1-365): 30// \n # OF REFILLS: (0-11): 0// \n SIG Text: .. \n ==[ WRAP ]==[INSERT ]========< SIG Text >=====[Press <PF1>H for help]====\n TAKE ONE TABLET PO Q4H PRN FOR 10 DAYS \n \n =======T=======T=======T=======T=======T=======T=======T=======T=======T=\n \n ADDITIONAL NOTE TO PROVIDER: NOTE TO PRESCRIBER \n Updating...OK\n FUTURE FILL HOLD DATE (#.05) New\n # DRUG QTY # REFS DAYS SUPPLY SUBS\n --------------------------------------------------------------------------\n 1 (E)ACETAMINOPHEN 325MG TAB 120 0 30 YES\n Sig : TAKE ONE TABLET PO Q4H PRN FOR 10 DAYS \n Note: NOTE TO PRESCRIBER \n \n Select Drug Suggestion Option: (N)EW (E)DIT (D)ELETE (F)INISH: \n \n g) After entering the suggested medications the user will be prompted to \n enter a comment for the field VA PROGRESS NOTE COMMENTS (Optional). \n \n The input from the user will be appended to the patient progress note \n automatically created after the Change Request is submitted to the \n prescriber. \n \n h) A Summary will be displayed to the user and a prompt asking if they \n want to edit the Change Request before submitting to the prescriber, as\n show below: \n RX CHANGE REQUEST SUMMARY \n ------------------------------------------------------------------------\n Change Request Reason Code: D - DUE (Drug Use Evaluation) \nForms Associated: \n Change Request Reason Sub-Code: AR - Adverse Drug Reaction \n Note to Provider: \n Patient has an adverse drug reaction to medication/component of\n medication prescribed. To fill as is, send denial to this request with\n note stating reason fill is acceptable. If med should not be filled-\n Cancel RX and send a replacement. \n \n # DRUG QTY # REFS DAYS SUPPLY SUBS\n -------------------------------------------------------------------------\n 1 (E)OMEPRAZOLE 20MG EC CAP 90 11 30 YES \n \n Sig : TAKE ONE CAPSULE BY MOUTH ONCE DAILY BEFORE MEAL \n Note: NOTE TO COMMUNITY PRESCRIBER REGARDING THIS DRUG \n \n VA Progress Note Comment: NOTE TO INCLUDE IN THE PROGRESS NOTE \n \n Would you like to edit this Rx Change Request before sending it? NO// \n \n i)Once the user submits the Change Request to the prescriber a Progress \n Note will be automatically created for the patient. The content of the \n Progress Note created will be same text from the eRx Change Request \nForm Name File Number New/Modified/Deleted \n Display record addition of the VA PROGRESS NOTE COMMENT field mentioned \n above: \n \n Would you like to edit this Rx Change Request before sending it? NO// \n \n Would you like to send this Rx Change Request? YES// YES \n \n Sending Request to Provider...Done.\n Creating a new Progress Note...Done.\n \n--------- ----------- --------------------\n Type <Enter> to continue or '^' to exit: \n \n j)When the response is received from the prescriber for the submitted \n Change Request an addendum to Progress Note created for the Request will\n be automatically created with the Change Response content.\n \n2. (HDSO-7263) eRx Holding Queue Display Conversion (Patient Summary \n Display) \n ---------------------------------------------------------------------------\n The new Single eRx View/Display option will replace the existing eRx \nN/A \n Holding Queue Display. The header will contain the following information \n (without the reverse or highlighted video features): \n \n Single eRx View/Display Mar 04, 2024@15:49:40 Page: 1 of 3 \n eRx Patient: LASTNAME,FIRSTNAME Y eRx Reference #: 999998 \n eRx Message Type: NEWRX \n eRx Status: HC - HOLD DUE TO CHANGE \n \n The eRx Hold Reason will be displayed on the first line or row of the \n Single eRx View/Display list area. \ninto Class 1. Below is a summary of the changes being delivered in this patch.\n \n \n Only display the eRx Hold Reason if it contains data. In the event that the\n user put the eRx on hold but did not enter any reason, the eRx Hold Reason \n will not be displayed. \n \n Note: If the on-hold reason is longer than 60 characters, the eRx Hold \n Reason will be truncated. The last three characters will be replaced \n with three dots (...). \n \n Within the Single eRx View/Display body/list area, the following will no \nMail Groups Associated: \n longer be displayed. \n * Hold Status \n * Hold Reason \n * Placed on hold by \n \n a)If the message type is NEWRX, the display will be in a side-by-side\n format. Below is an example of the before conversion and how the new\n screen will be displayed. \n \n Side-by-Side Format (without the reverse or highlighted video features):\n \n ------------------------------------------------------------------------\n Single eRx View/Display Mar 04, 2024@15:49:40 Page: 1 of 3\n eRx Patient: LASTNAME,FIRSTNAME Y eRx Reference #: 999998\n eRx Message Type: NEWRX \n eRx Status: HC - HOLD DUE TO CHANGE \n ERX | VISTA\n ------------------------------------------------------------------------\n PATIENT AUTO-MATCHED | VALIDATED by NAME,TEST on 3/3/24@15:08:08\n ------------------------------------------------------------------------\n Name: LASTNAME,FIRSTNAME Y |Name: TESTPATIENT,PATIENT\nMail Group Name New/Modified/Deleted \n DOB : NOV 20, 1965 |DOB : NOV 20,1965\n Cell Phone: |Cell Phone: (222) 222-2222\n PROVIDER AUTO-MATCHED \n ------------------------------------------------------------------------\n Name: PROVIDER,PROVIDERNAME |Name: PROVIDER,TESTONE\n NPI : 1902127376 |NPI : 1144228248\n DEA : |DEA :\n DRUG AUTO-MATCHED | VALIDATED by NAME,TEST on 3/6/24@12:42:58\n ------------------------------------------------------------------------\n Drug: predniSONE 20 mg tablet |Drug: PREDNISONE 20MG TAB\n--------------- --------------------\n (DELTASONE) \n Substitution? YES Renewals? YES |Drug Message:\n | NATL FORM\n SIG: |SIG:\n Take 3 tablets (60 mg total) by | TAKE ONE TABLET BY MOUTH ONCE\n mouth daily. for 5 days | DAILY FOR 6 HOURS, THEN TAKE\n | ONE-HALF TABLET ONCE DAILY\n Prescriber Drug Use Evaluation: | FOR 4 HOURS WITH FOOD\n None | FOR INFLAMMATION\n | Dosage: 20 (MG)\nN/A \n | Verb: TAKE\n |Disp. Units: 1\n | Noun: TABLET\n | Route: ORAL (BY MOUTH)\n | Schedule: ONCE DAILY\n | Duration: 6H (HOURS)\n |Conjunction: THEN\n | Dosage: 10 (MG)\n | Verb: TAKE\n |Disp. Units: 0.5\n \n | Noun: TABLET\n | Route: ORAL (BY MOUTH)\n | Schedule: ONCE DAILY\n | Duration: 4H (HOURS)\n |Patient Instructions:\n | WITH FOOD FOR INFLAMMATION\n Provider Notes/Comments: |Provider Comments:\n | TESTING\n Quantity: 15 |Quantity: 15\n Dispense Unit: | Dispense Unit: TAB\nOptions Associated: \n Qty Qualifier: Original Quantity |\n Days Supply: Refills: 0 |Days Supply: 1 Refills: 0\n |Routing: MAIL\n |Clinic: CHY TEST CLINIC 2\n Written: 12/12/23 Effective: |\n Allergy: |Allergy:\n NO ALLERGY INFORMATION RECEIVED | NO KNOWN ALLERGIES\n _____________________________________|__________________________________\n eRx Received on 12/12/23@15:47 \n \n \n b)If the message type is one of the following (see below), the display \n will not be in side-by-side format, but the data entered will have a \n reverse video display and highlighted and bolded fonts. \n These features depend on the terminal display settings being set \n differently for reverse video and highlighted font in order for them \n to work. \n Below is an example of how the new screen will be displayed (without \n the reverse or highlighted video features). \n \n 'RR' FOR RXRENEWALREQUEST; \nOption Name Type New/Modified/Deleted \n 'RE' FOR RXRENEWALRESPONSE; \n 'CR' FOR RXCHANGEREQUEST; \n 'RXF' FOR RXFILL; \n 'IE' FOR INBOUND ERROR; \n 'OE' FOR OUTBOUND ERROR; \n 'CA' FOR CANCELRX; \n 'CN' FOR CANCELRXRESPONSE; \n 'CX' FOR RXCHANGERESPONSE; \n \n On your screen, the data entered will have a reverse video display \nFor a more comprehensive description of the changes please refer to the\n----------- ---- --------------------\n and a highlighted and bolded fonts: \n --------------------------------------------------------------------\n \n Single eRx View/Display Mar 04, 2024@16:06:51 Page: 1 of 3 \n eRx Patient: TESTMAN,TEST eRx Reference #: 123456789 \n eRx Message Type: RXRENEWALRESPONSE - APPROVED WITH CHANGES \n eRx Status: HWR - CS PRESCRIPTION WRITTEN/ISSUE DATE HAS PROBLEMS \n ________________________________________________________________________\n eRx Hold Reason: HOLD REASON COMMENT\n MEDICATION PRESCRIBED \nPSO ERX FINISH Action Modified\n ------------------------------------------------------------------------\n eRx Patient Primary Telephone: 1111111111 \n eRx Patient: TESTMAN,TEST DOB: 99/99/99 \n Vista Patient[v]: TESTMAN,TESTTWO DOB: 99/99/99 \n ________________________________________________________________________\n eRx Provider: PROVIDER,PROVIDERNAME DEA#: XX9999999 NPI: 9999999999\n Vista Provider[v]: PROVIDER,TESTONE DEA#: NPI: 9999999999\n ________________________________________________________________________\n eRx Drug: CLONIDINE 0.2MG/24HR PATCH \n eRx Qty: 13 eRx Refills: 0 eRx Days Supply: \n \n eRx Written Date: JAN 30, 2024 eRx Issue Date: \n eRx Notes: TEST COMING FROM XML SIMULATOR \n Allergies \n Verified: LISINOPRIL, TESTOSTERONE, \n Remote: No remote data available \n Adverse Reactions \n RXRENEWAL RESPONSE INFORMATION \n ------------------------------------------------------------------------\n APPROVED WITH CHANGES \n Response Date/Time: JAN 30, 2024@11:25:58 \n \n Note: \n RxRenewal Response Comments: \n Comments By: \n Comments Date/Time: \n MEDICATION DISPENSED \n ------------------------------------------------------------------------\n VA Rx#: Unable to resolve. \n RXRENEWAL REQUEST INFORMATION\n ------------------------------------------------------------------------\n Requested By: \nProtocols Associated: \n Request Date/Time: \n # of Refills Requested: \n RxRenewal Request Comments: \n Comments By: \n Comments Date/Time: \n MESSAGE HISTORY \n ------------------------------------------------------------------------\n Request Reference #: \n New eRx Reference #: \n Response eRx Reference #: 123456789\n \n ________________________________________________________________________\n eRx Received on 1/30/24@11:25 \n \n c)At the end of the Single eRx View/Display, users will find the eRx \n received time stamp. \n Below is an example of how the new screen will be displayed (without the \n reverse or highlighted video features). \n \n Single eRx View/Display Mar 04, 2024@16:22:37 Page: 3 of 3\n eRx Patient: TESTMAN,TEST eRx Reference #: 123456789\nProtocol Name Type New/Modified/Deleted \n eRx Message Type: RXRENEWALRESPONSE - APPROVED WITH CHANGES \n eRx Status: HWR - CS PRESCRIPTION WRITTEN/ISSUE DATE HAS PROBLEMS \n _________________________________________________________________________\n Request Date/Time: \n # of Refills Requested: \n RxRenewal Request Comments: \n Comments By: \n Comments Date/Time: \n MESSAGE HISTORY \n -------------------------------------------------------------------------\n------------- ----- --------------------\n Request Reference #: \n New eRx Reference #: \n Response eRx Reference #: 123456789\n _________________________________________________________________________\n eRx Received on 1/30/24@11:25 \n \n 3. (HDSO-7266) Batch eRx Remove and Un-Remove Functionality \n ---------------------------------------------------------------------------\n The current Remove and Un-Remove actions were modified to now allow users \n to perform a batch Remove and Un-Remove of eRx for a patient. \nPSO ERX CHANGE REQUEST Action Modified\n Every time a prescription is Remove or Un-Remove, the software will check \n if other prescriptions exist for that patient that were sent by the same \n prescriber on the same day. \n If any are found, the software will ask the user if they want to Remove \n (or Un-Remove) those additional eRx records as well, as shown below: \n \n 3.1 Batch eRx Remove Functionality: \n ------------------------------\n Select Action: Next Screen// RM Remove eRx \n \nPSO ERX DISPLAY MENU Menu Modified \n Select REMOVAL reason code: REM01 Drug out of stock or on backorder and un \n available for processing \n Additional Comments (Optional): TESTING REMOVE \n \n Would you like to 'Remove' eRx #12345678901236? Y// ES \n \n The following prescriptions are from the same provider and received on the\n same day: \n \n PROVIDER: PROVIDER,PROVIDERNAME eRx RECEIVED DATE: FEB 07, 2024@11:11:54\ndocuments listed in the Documentation section of this description. \nPSO ERX DRUG VALIDATION HIDDEN MENU Menu Modified \n ERX ID DRUG NAME PROVIDER STS\n --------------------------------------------------------------------------\n 12345678901235 ASPIRIN 325MG EC TAB PROVIDER,PROVIDERNAME HUR\n 12345678901237 LISINOPRIL 20MG TAB PROVIDER,PROVIDERNAME HUR\n 12345678901238 NAPROXEN 500MG TAB PROVIDER,PROVIDERNAME HUR\n \n Do you want to 'Remove' them - REM01? No// YES \n Updating...done. \n \n 3.2 Batch eRx Un-Remove Functionality: \nPSO ERX HIDDEN ACTIONS Menu Modified \n ---------------------------------\n \n Select Action: Next Screen// UR UR \n \n Select HOLD reason code: HUR// UN-REMOVED \n Additional Comments (Optional): TESTING UN-REMOVED \n Would you like to 'Un-Remove' eRx #12345678901235? Y// ES \n \n The following prescriptions are from the same provider and received on the\n same day: \nPSO ERX JUMP TO ERX PATIENT Action New\n \n PROVIDER: PROVIDER,PROVIDERNAME eRx RECEIVED DATE: FEB 07, 2024@11:09:39\n ERX ID DRUG NAME PROVIDER STS\n --------------------------------------------------------------------------\n 12345678901236 IBUPROFEN 800MG TAB PROVIDER,PROVIDERNAME REM03\n 12345678901237 LISINOPRIL 20MG TAB PROVIDER,PROVIDERNAME REM03\n 12345678901238 NAPROXEN 500MG TAB PROVIDER,PROVIDERNAME REM03\n \n Do you want to 'Un-Remove' them? No// YES \n Updating...done. \nPSO ERX PATIENT VALIDATION HIDDEN MENU Menu Modified \n \n4. (HDSO-7264) Pending Order Suggested Fill Date auto calculation \n ---------------------------------------------------------------------------\n Currently, the Fill Date field for an eRx Pending Order is always set to \n the current date. In some cases this is not ideal because the patient might\n still have enough medication to last a few more days and a future fill \n date, based on the last fill for the medication might be more appropriate. \n \n The algorithm will auto calculate the suggested Fill Date using the \n following logic: \nPSO ERX PROVIDER VALIDATION HIDDEN MENU Menu Modified \n Requirement: \n - A previous prescription for the exact same drug must be found on the\n patient's profile \n - The SIG from the previous prescription must match exactly with the \n SIG for the new eRx Pending Order (excluding Patient Instructions)\n \n Suggested Future Fill Date: \n - If Last Fill is Released and the Release Date + Days Supply results \n in a future date, this futures date suggested as the Fill Date for \n the eRx Pending Order. \nPSO ERX RESEND CHANGE REQUEST Action New\n - If the CMOP Transmission status for the Last Fill is TRANSMITTED or\n RE-TRANSMITTED, the Fill Date for the eRx Pending Order will be\n today's date + Days Supply for the Suspended fill. \n - If Last Fill is Suspended with a future Fill Date this future date\n will be suggested as the Fill Date for the eRx Pending Order. \n \n5. (HDSO-7380) Removal of VistA Drug Selection Restriction \n ---------------------------------------------------------------------------\n Currently, when they user tries to select a VistA Drug to match to the eRx \n they are not able to select drugs that are marked as INVESTIGATIONAL, BULK \nPSO ERX VIEW DRUG SUGGESTIONS Action New\n COMPOUND or MANUFACTURED IN PHARMACY (DEA SPECIAL HDLG field contains "I", \n "M" or "0"). This patch removes such restriction. \n \n6. (HDSO-7449) Provider Auto-Validation for VAMCs\n ---------------------------------------------------------------------------\n The Provider Auto-Validation functionality released with patch PSO*7*700, \n will now work at VA Medical Centers as well. In order for the provider to\n be auto-validated the following conditions must be fulfilled:\n \n - eRx Providers was auto-matched to a VistA Provider\nPSO ERX VIEW ORIGINAL ERX Action New\n - eRx Provider last name matches VistA Provider last name\n - First letter of eRx Provider first name matches first letter of VistA\n Provider first name\n - Zip code for the eRx Provider matches the zip code for the VistA\n Provider\n - eRx is not electronically signed (CS eRx) \n \n7. (HDSO-7450) Clinic name in the Validate Provider Screen\n ---------------------------------------------------------------------------\n The field Clinic is being added to the Provider Validation Screen. It will\nPSO ERX VIEW PATIENT SUGGESTIONS Action New\n display the eRx Provider Business Name when there is one. There will be no\n corresponding information on the VistA side of the side-by-side screen.\n This information will also display on the eRx Summary Display screen:\n ______________________________________________________________________\n ERX PROVIDER | VISTA PROVIDER \n Name: TEST,PROVIDER |Name: TEST, PROVIDER MD \n NPI : 9999999999 |NPI : 9999999999 \n DEA : XX9999999 |DEA : XX9999999 \n Clinic: BUSINESS NAME | \n ______________________________________________________________________\nPSO ERX VIEW PROVIDER SUGGESTIONS Action New\n \n8. (HDSO-7768) Hold for Future Fill Functionality\n ---------------------------------------------------------------------------\n A new hold code named HOLD FOR FUTURE FILL (HFF) is being added. This new\n hold code will work differently than all other hold codes. Once the user\n selects this code, the software will prompt the user to enter a future fill\n date. If there is an effective fill date on file for the eRx, this date\n will be used as the default date, as seen below:\n ...\n Select Action:Next Screen// H Hold \n \nPSO ERX VIEW REQUEST ERX Action New\n \n Select HOLD reason code: HFF HOLD FOR FUTURE FILL\n \n The eRx will be un-held automatically on the date you enter below and\n placed in 'IN PROCESS' status.\n \n Future Fill Hold Date: MM/DD/YY//\n \n The Status History (SH) and History Log (HL) actions will display the\n the hold date.\nPSO ERX VIEW RESPONSE ERX Action New\n \n Status History:\n 05/02/24@15:01:06 HFF HOLD FOR FUTURE FILL (MAY 12, 2024)\n Entered By: ROCHA,MARCELO\n Comments: COMMENT...\n \n History Log:\n Status History: \n Date/Time Status Entered By\n ---------------------------------------------------------------------\nPSO HIDDEN ACTIONS #1 Menu Modified \n 05/02/24@15:01:06 HFF-HOLD FOR FUTURE FILL (May 12, 2024) USER,NAME\n Comments: COMMENT...\n \n On the date the eRx was held for it will be automatically un-held and\n and placed on the eRx Holding Queue as In-Process or Wait status.\n \n9. (HDSO-7769) Manually Hold and Un-Hold with HC hold code\n ---------------------------------------------------------------------------\n The hold code HOLD FOR CHANGE (HC) was used solely for Change Requests,\n which was assigned automatically after the users sent a Change Request to\nPSO HIDDEN ACTIONS #2 Menu Modified \n the prescriber. This is being changed to allow the user to manually use\n this code to place eRx's on hold and also to un-hold eRx's held with this\n code.\n \n10.(HDSO-7770) Prescriber Drug Use Evaluation (DUE) Information\n ---------------------------------------------------------------------------\n The prescriber DUE information will be included in the Single eRx View/\n Display Screen for New Rx, Change Response, Renewal Response records as\n well as in the Validate Drug Screen, Pending order (OP) screen and CPRS\n Progress Notes Addendum, as shown below:\n \n New Rx:\n ------\n ... \n SIG: |SIG: \n TAKE 1 CAP PO 3X DAILY | TAKE ONE CAPSULE BY MOUTH THREE\n | TIMES A DAY WITH FOOD \n | PATIENT INSTRUCTIONS \n Prescriber Drug Use Evaluation: | Dosage: 300 (MG) \n Co-Agent: Nsaids (Non-Steroidal Anti-In| Verb: TAKE \n flammatory Drug) |Disp. Units: 1 \nSecurity Keys Associated: \n Reason: Drug-Allergy | Noun: CAPSULE \n Result: Prescribed w/ acknowledgements | Route: ORAL \n Acknowledgement: Previously Tolerated | Schedule: BID-WITH FOOD \n ...\n \n Change Response/Renewal Response/CPRS Progress Notes Addendum:\n -------------------------------------------------------------\n ...\n Prescriber Drug Use Evaluation: \n Co-Agent: Ibuprofen \n \n Reason: Drug-Allergy \n Result: Prescribed w/ acknowledgements\n Acknowledgement: Previously Tolerated \n ...........................................................................\n Co-Agent: Nsaids (Non-Steroidal Anti-Inflammatory Drug)\n Reason: Drug-Allergy \n Result: Prescribed w/ acknowledgements \n Acknowledgement: Previously Tolerated \n ...\n Validate Drug Screen:\nSecurity Key Name \n --------------------\n _______________________________________|__________________________________\n Prescriber Drug Use Evaluation: |2) Dosage: 300 (MG) \n Co-Agent: Ibuprofen | Verb: TAKE \n Reason: Drug-Allergy |Disp. Units: 1 \n Result: Prescribed w/ acknowledgements | Noun: CAPSULE \n Acknowledgement: Previously Tolerated | Route: ORAL \n ...................................... | Schedule: BID-WITH FOOD \n Co-Agent: Nsaids (Non-Steroidal Anti-In|__________________________________\n flammatory Drug) |3)Patient Instructions: \n-----------------\n Reason: Drug-Allergy | \n Result: Prescribed w/ acknowledgements | \n Acknowledgement: Previously Tolerated | \n _______________________________________|__________________________________\n \n Pending Order:\n -------------\n _______________________________________|__________________________________\n Prescriber Drug Use Evaluation: |3) Dosage: 300 (MG) \n Co-Agent: Ibuprofen | Verb: TAKE \nN/A \n Reason: Drug-Allergy |Disp. Units: 1 \n Result: Prescribed w/ acknowledgements | Noun: CAPSULE \n Acknowledgement: Previously Tolerated | Route: ORAL \n ...................................... | Schedule: BID-WITH FOOD \n Co-Agent: Nsaids (Non-Steroidal Anti-In|__________________________________\n flammatory Drug) |4)Patient Instructions: \n Reason: Drug-Allergy | \n Result: Prescribed w/ acknowledgements | \n Acknowledgement: Previously Tolerated | \n _______________________________________|__________________________________\nPatch Components \n \n \n11.(HDSO-7771) eRx Meds on File notitifcation\n ---------------------------------------------------------------------------\n A note "eRx Meds on File" is being added to the Patient Prescription \n Processing [PSO LM BACKDOOR ORDERS] option header when the patient has at\n least one 'actionable' eRx in the eRx Holding Queue, as shown below:\n \n Patient Information May 02, 2024@17:19:54 Page: 1 of 2 \n TEST,NAME\n PID: 999-99-9999 Ht(cm): _______ (______)\nTemplates Associated: \n DOB: XXX 99,9999 (99) Wt(kg): _______ (______)\n SEX: MALE eRx Meds on File\n CrCL: <Not Found> (CREAT: Not Found) BSA (m2): _______ \n ... \n \n12.(HDSO-7772) Jump to eRx Patient from Backdoor\n ---------------------------------------------------------------------------\n A new hidden action called Jump to eRx Patient (JE) is being added to the\n Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option. It will be\n available in the Patient Information screen as well as in the Medication \n \n Profile screen. This option will allow the user to jump to the eRx Holding\n Queue in the eRx Single Patient Queue. \n \n13.(HDSO-7773) View Suggestions for Patient, Provider and Drug\n ---------------------------------------------------------------------------\n A new hidden action called View Suggestion(s) (VS) is being added to the\n Validate Patient, Validate Provider and Validate Drug screens. This feature\n will allow users to view and manage suggestions at any time, before or\n after the eRx has been accepted/processed. Below are some examples for each\n screen:\nTemplate Name Type File Name (#) New/Modified/Deleted \n Validate Patient:\n ----------------\n ...\n Select Item(s): Next Screen// VS \n |Sugg. 1 of 1 - 03/07/24|\n ERX PATIENT VISTA PATIENT |From eRx#: 111001 |\n __________________________________________________________________________\n Name: TEST,PATIENT A |Name: TEST,PATIENT A\n DOB : XXX 99, 9999 |DOB : XXX 99, 9999\n SSN : 999999999 |SSN : 999-99-9999\n------------- ---- ------------ --------------------\n Sex : MALE |Sex : MALE\n Address: |Address:\n 123 FAKE AVE | 123 FAKE ST \n XXXXXXXXX, XX 999999 | XXXXXXXXX, XX 999999\n Primary Phone: 5184724307 |\n ___________________________________|______________________________________\n ACTION on SUGGESTION: (F)ORGET (E)XIT: EXIT// \n ... \n \n Validate Provider:\nPSO ERX SINGLE ERX DISPLAY List N/A New \n -----------------\n ...\n Select Item(s): Quit// VS \n |Sugg. 1 of 1 - 05/02/24|\n ERX PROVIDER VISTA PROVIDER|From eRx#: 123431 |\n ___________________________________________________________________________\n Name: PROVIDER,TEST |Name: PROVIDER,TEST\n NPI : 9999999999 |NPI : 9999999999\n DEA : XX9999999 |DEA : XX9999999\n Clinic: TEST CLINIC NAME |\nPSO ERX PROVIDER VALIDATION List N/A Modified\n ___________________________________|_______________________________________\n Address: |Address:\n 9876 HEALTH CIR | 9876 HEALTH CIR\n XXXXXXXXXXXX,XX 99999 | XXXXXXXXXXXX,XX 99999\n Tel: 999-999-9999 |Tel: 999-999-9999\n ___________________________________|_______________________________________\n ACTION on SUGGESTION: (F)ORGET (E)XIT: EXIT// \n \n Validate Drug:\n -------------\n \n ...\n Select Item(s): Next Screen// VS \n |Sugg. 1 of 1 - 03/19/24|\n ERX MED VISTA MED |From Rx#: 2298007 |\n ___________________________________________________________________________\n Drug: DOCUSATE CA 240MG CAP |Drug: DOCUSATE CA 240MG CAP\n Substitution? YES Renewals? YES |Drug Message:\n | NATL FORM (09/01) (INCREMENT OF\n | 100s)\n ___________________________________|_______________________________________\nRemote Procedures Associated: \n SIG: |SIG:\n 1 CAP PO DAILY | TAKE ONE CAPSULE BY MOUTH ONCE DAILY\n ___________________________________|_______________________________________\n Provider Notes/Comments: |Provider Comments:\n | \n ___________________________________|_______________________________________\n Quantity: 30 |Quantity: 30\n Dispense Unit: |Dispense Unit: CAP\n Qty Qualifier: Original Quantity |QTY Dispense Message:\n | CAP (INCREMENTS OF 100)\n \n ___________________________________|_______________________________________\n Days Supply: 30 Refills: 11 |Days Supply: 30 Refills: 11\n ___________________________________|_______________________________________\n ACTION on SUGGESTION: (F)ORGET (E)XIT: EXIT// \n ...\n \n14.(HDSO-7774) RESEND eRx Change Request\n ---------------------------------------------------------------------------\n The new action called Resend Change Request (REC) will now allow the user\n to send the previously sent eRx Change Request to the prescriber. Right\n================\nRemote Procedure Name New/Modified/Deleted \n after user enters REC in the Select Action:Next Screen// prompt, the\n software will display the RX CHANGE REQUEST SUMMARY. This allows the user\n to review the previously sent eRx Change Request. The user can edit the\n existing eRx Change Request or just leave them as is, as shown below:\n \n Single eRx View/Display May 03, 2024@10:41:48 Page: 1 of 4 \n eRx Patient: LASTNAME,FIRSTNAME TEST\n eRx Message Type: RXCHANGEREQUEST\n eRx Status: CRX - RXCHANGE REQUEST EXPIRED\n _______________________________________________________________________\n--------------------- --------------------\n Change Request Type: DUE (Drug Use Evaluation) \n Change Request Sub Type: Missing Information/Clarification \n Change Request Reason Text: \n The eRx is missing or unclear on RESENDING EXISTING ERX CHANGE REQUEST\n WITH A V record. Please edit and respond or cancel Rx and send a new\n prescription with the requested information. \n MEDICATION PRESCRIBED \n _______________________________________________________________________\n eRx Patient Primary Telephone: 555-555-5555 \n eRx Patient: LASTNAME,FIRSTNAME TEST DOB: 3/1/70\nN/A \n Vista Patient: NOT LINKED DOB: N/A \n _______________________________________________________________________\n eRx Provider: PROVIDER,PROVIDERNAME DEA#: FB1234567 NPI: 1234567890\n Vista Provider: NOT LINKED DEA#: N/A NPI: N/A \n _______________________________________________________________________\n + Enter ?? for more actions \n VP (VALIDATE PATIENT) VM (VALIDATE PROVIDER) VD (VALIDATE DRUG/SIG)\n P Print RJ (Reject) AC (Accept eRx)\n H (Hold) UH (Un Hold) RM (Remove eRx)\n Select Action:Next Screen// REC REC \n \n \n RX CHANGE REQUEST SUMMARY \n _______________________________________________________________________\n Change Request Reason Code: D - DUE (Drug Use Evaluation) \n Change Request Reason Sub-Code: MS - Missing Information/Clarification\n Note to Provider: \n The eRx is missing or unclear on RESENDING EXISTING ERX CHANGE REQUEST\n WITH A V record. Please edit and respond or cancel Rx and send a new\n prescription with the requested information.\n \nParameter Definitions Associated: \n # DRUG QTY # REFS DAYS SUPPLY SUBS\n _______________________________________________________________________\n 1 (E)LISINOPRIL 40MG TAB 20 3 30 YES\n Sig : TAKE ONE TABLET A DAY ON AN EMPTY STOMACH. \n Note: Testing REC.\n 2 (V)RIBOFLAVIN 100MG TAB 90 1 90 NO\n Sig : TAKE 1 TABLET ORALLY EACH DAY FOR 90 DAYS. \n Note: Testing REC.\n \n VA Progress Note Comment: \n \n TEST VA PROGRESS NOTE COMMENT\n _______________________________________________________________________\n \n Would you like to edit this Rx Change Request before sending it? NO// \n \n Would you like to send this Rx Change Request? YES// YES \n \n Sending Request to Provider...Done.\n Creating a new Progress Note...Done.\n \nParameter Name New/Modified/Deleted \n15.(HDSO-????) Diagnosis and Drug Use Evaluation (DUE) info on eRx Print\n ---------------------------------------------------------------------------\n The eRx Print action in the eRx Holding Queue was changed to include two\n new sections: Diagnosis and DUE information. These sections will only be\n included when the information exists in the eRx. They will look like the\n examples below:\n \n *************************DIAGNOSIS INFORMATION**************************\n Primary Dx:\n ICD-10 A01.01 TYPHOID MENINGITIS\n-------------- --------------------\n Typhoid meningitis_Test primary diagnosis\n ........................................................................\n Secondary Dx:\n ICD-10 E11.21 TYPE 2 DIABETES MELLITUS WITH DIABETIC NEPHROPATHY\n Test secondary Diagnosis\n \n *********************PRESCRIBER DRUG USE EVALUATION*********************\n Co-Agent: Nsaids (Non-Steroidal Anti-Inflammatory Drug)\n Reason: Drug-Allergy\n Result: Prescribed w/ acknowledgements\nN/A \n Override: Previously Tolerated\n ************************************************************************\n \n16. INC26069186 - eRx Prescription # wrong in file ###.## Order DEA Archive\n ---------------------------------------------------------------------------\n For eRx prescriptions, file #101.52 ORDER DEA ARCHIVE field #1 \n PRESCRIPTION NUMBER is storing the wrong value. The value stored is the \n IEN of the eRx's pending order from file 52.41 OUTPATIENT PENDING ORDER \n before it is finished. \n \n \n When viewed from a global listing, the node 0 piece 2 shows an IEN \n appended with an "S", which is how file 100 stores a PACKAGE REFERENCE to \n a PENDING OUTPATIENT ORDERS file #52.41.\n \n This erroneous display occurs when completing the eRX order in Complete \n Orders from eRx [PSO ERX FINISH] and can be viewed both before and after \n finishing the prescription in Patient Prescription Processing [PSO LM \n BACKDOOR ORDERS].\n \n Resolution:\nFiles & Fields Associated: \nAdditional Information: \n -----------\n This will need to be addressed with changes to Pharmacy code as well as \n CPRS code. This patch will address the pharmacy changes. This patch \n does not address the existing PENDING OUTPATIENT ORDERS file #52.41 that\n exist in ORDER DEA ARCHIVE INFO file #101.52, that will be addressed by\n a follow up patch from CPRS. This patch corrects the field value going \n forward.\n \n Routine PSOORFI1 is modified to allow array PSOCSP to be setup for eRX \n orders the same as they are for pending orders signed in CPRS. This \n-----------------------\n array is needed in the Patient Prescription Processing finishing process.\n \n Routine PSON52 is modified to allow eRX orders that do not have a \n SIGNATURE STATUS field #117 set in PENDING OUTPATIENT ORDERS file \n #52.41. This will allow the process to flow into code that allows the \n PRESCRIPTION file #52 IEN to be set into the PRESCRIPTION NUMBER field\n #1 of the ORDER DEA ARCHIVE INFO file #101.52\n \n Routine PSOERX1F is modified to delete the PRESCRIPTION NUMBER field #1\n of the ORDER DEA ARCHIVE INFO file #101.52 after processing returns from \nNew Service Requests (NSRs): N/A \n calling protocol PS EVSEND OR via routine EN^PSOHLSNC during PSO ERX \n FINISH processing. This removes the #52.41 IEN and thus allows PSON52 to \n update it with the correct IEN to file #52. This change will likely not \n be released but is necessary for testing this patch until the CPRS \n release is ready.\n \nPatient Safety Issues (PSIs): \n-----------------------------\nN/A \n \nDefect Tracking System Ticket(s) & Overview: \n============================================\n\n
\nProblem:\nModify routine PSOPRVW and change the calculation used to determine if \nprinting has reached the bottom of the page. This will allow the \nprovider name to be displayed on each page of the output. Data for 2 DEA \nnumbers will be displayed on each page.\n--------\nWhen running options Add New Providers [PSO PROVIDER], Edit Provider [PSO \nPROVIDER EDIT], or View Provider [PSO PROVIDER INQUIRE], the heading for \nthe provider scrolls off the page when the provider has more than 2 DEA \nnumbers.\n \nResolution:\n-----------\n\n
\nThis patch addresses the following issues:\nProblem 3 - Activity Log Header node not updated on a Dosage Edit in\nPatient Prescription Processing [PSO LM BACKDOOR ORDERS]. \n \nTicket INC28706897:\n-------------------\nProblem 1 - Missing Activity Log Header Node for old prescriptions.\n \nProblem 2 - ATP+4^PSO52API error occurring for MyHealtheVet queries for\nprescriptions missing the Activity Log Header node.\n \n\n
\nSee FORUM patch description.\n\n
\nSee FORUM for patch description.\n\n
\nThis patch is being released to address a few small eRx related issues\n6. NDC code included in the Requested Medication section of the eRx Rx Change\n Note: Aware of Allergy. Patient Tolerates \n Qty: 30 Refills: 5 Days Supply: 180 \n Quantity Unit Of Measure: TABLET DOSING UNIT \n Sig: TAKE 1 TAB PO DAILY \n ------------------------------------------------------------------------\n \n7. Complete Orders from eRx [PSO ERX FINISH] option removal\n --------------------------------------------------------------------------\n The Complete Orders from eRx [PSO ERX FINISH] option was put Out-of-Order \n by the PSO*7*746 patch because its functionality has been fully replaced\n Request\n by the eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING] option. \n This patch will now remove/delete this obsolete option from your menu.\n \n8. SIG over 512 characters cause a <SUBSRCIPT> error\n --------------------------------------------------------------------------\n When the user tried to select the VistA drug to match the eRx drug and\n a VistA suggestion exists with a SIG that is longer than 512 characters\n they software throws a <SUBSCRIPT> error, which will be addressed by this\n patch.\n7. Complete Orders from eRx [PSO ERX FINISH] option removal\n8. SIG over 512 characters cause a <SUBSRCIPT> error\n \n1. Written Date with Time display issue\n --------------------------------------------------------------------------\n Some prescribers send eRx's with a timestamp for the Written Date and \n this causes a display issue which overwrites the 'eRx Status' label as \n shown below:\nencountered after the patch PSO*7*746 was released:\n \n Single eRx View/Display Aug 10, 2024@10:28:15 Page: 1 of 2\n eRx Patient: PATIENT,TEST eRx Reference #: 999999999\n eRx Msg Type: NEWRX Written: 08/23/24\n @11:11:11s: W - WAIT\n ^^^^^^^^^\n \n2. Changed ADDITIONAL NOTE TO PROVIDER prompt to SUGGESTED PROVIDER NOTE\n (FOR RESPONSE RX) + Default for eRx drug selection\n --------------------------------------------------------------------------\n \n After verifying data from several Rx Responses from the prescriber it \n was determined that the prompt ADDITIONAL NOTE TO PROVIDER was wrongly\n worded. This field is not supposed to be used by Pharmacy to \n communicate with the prescriber, the correct use is for pharmacy to\n enter a suggested Provider Note content that the prescriber will then \n decide to keep, change or delete when adopting the requested medication.\n Additionally, when the user is building the requested medication, if the\n user selects E (use eRx Drug) the Provider Notes content (if any) will\n be given as default for the Provider Notes in the medication requested,\n as shown below:\n1. Written Date with Time display issue\n \n SUGGESTED PROVIDER NOTE (FOR RESPONSE RX): Suggested Packaging: 2.0 \n Milliliters syringe. Replace ??\n \n This is the suggested Provider Note that will be sent back with Rx \n Response if this drug option is selected by the outside Provider. It\n may be edited/removed by the Provider before sending the response\n back.\n \n3. View Suggestion(s) action fix\n2. Changed ADDITIONAL NOTE TO PROVIDER prompt to SUGGESTED PROVIDER NOTE \n --------------------------------------------------------------------------\n Sometimes the VS (View Suggestion(s)) action does not show any suggestions\n and does not say 'No suggestions found' either. This is being fixed with\n this patch.\n \n4. DUE (Drug Use Evaluation) Override Reason display issue\n --------------------------------------------------------------------------\n When the Override field from a DUE is longer than 28 characters it\n 'spills' over into the next section (VistA), as shown below: \n \n (FOR RESPONSE RX) + Default for eRx drug selection\n Prescriber Drug Use Evaluation: |________________________________\n Co-Agent: |3)Patient Instructions: \n Reason: Product Selection Opportunity | \n Result: | \n Override: Substitute as necessary, ple | \n ase provide documentat|on to \n patient for assistanc| \n \n After fix:\n --------- \n3. View Suggestion(s) action fix\n Prescriber Drug Use Evaluation: |________________________________\n Co-Agent: |3)Patient Instructions: \n Reason: Product Selection Opportunity | \n Result: | \n Override: Substitute as necessary, plea| \n se provide documentation to p| \n atient for assistance | \n \n5. Print action fixes\n --------------------------------------------------------------------------\n4. DUE (Drug Use Evaluation) Override Reason display issue\n Two small changes were made to the Print action in the PATIENT INFORMATION\n section:\n - Fixed a misspelling of the label 'Nane:' to 'Name:'\n - Changed label 'Primary Telephone' to 'Primary Phone'\n \n6. NDC code included in the Requested Medication section of the eRx Rx Change\n Request\n --------------------------------------------------------------------------\n Sometimes when an RX Change Request is sent the outside prescriber \n software returns an error saying the drug suggested is not recognized.\n5. Print action fixes\n This issue happens when the user selects a VistA drug for the Requested \n Medication and the VistA NDC for this drug is not recognized by the \n prescriber software. In order to facilitate the troubleshooting of such\n issue the NDC sent to the prescriber for the Requested Medication will \n now be displayed in the Requested Medication of the Rx Change Request\n section, as shown below:\n \n --------------------------MEDICATION REQUESTED 1-------------------------\n Drug: NAPROXEN 250MG TAB \n Substitutions: YES NDC: 77771-0434-05\n\n
\nSee FORUM for patch description details.\n\n
\n1. Problem: Prescriptions that need to be resubmitted to CMOP with a CMOP\n2. Problem: A concurrent window and a mail fill for a single prescription\nare being allowed to be processed with the mail fill going into CMOP\nsuspense. \n \nResolution:\n \nThe code has been changed to test for and block a request of a multiple\nfill for the same prescription being sent to CMOP.\nstatus of 'Not Dispensed' are failing internal testing and are blocked\nfrom being transmitted to CMOP.\n \nResolution:\n \nThe internal testing code has been corrected to allow resubmission of\nprescriptions to CMOP.\n \n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\n \nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\n \nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nThis patch distributes the Remote Procedure Call (RPC), routine, and\nflag.\n----------------------------\nN/A \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nThe patch also removes the now defunct RPC's PSO GET TEMPORARY ADDRESS and\nN/A\n \n \n \nTest Sites:\n-----------\nMiami VAMC, FL\nWest Palm Beach VAMC, FL\n \n \nPSO TEMP ADDRESS UPDATE which have been superseded by PSO GET ADDRESS and\nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\nThe software for this patch is being released in a PackMan message.\n \n \nDocumentation describing the new functionality is included in this \nrelease. Documentation can be found on the VA Software Documentation \nLibrary at: https://www.domain.ext/vdl/. Documentation can also be \nobtained at https://download.vista.domain.ext/index.html/SOFTWARE. \n \nPSO ADDRESS UPDATE respectively.\n \nDocumentation Title File \nName \n---------------------------------------------------------------------\n \n \n \nPatch Installation:\n-------------------\n \n \n \nPre/Post Installation Overview:\n-------------------------------\n \n \nPre-Installation Instructions:\n------------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \n \nminutes to install.\n \n \n \n \nInstallation Instructions:\n \n1. Choose the PackMan message containing this build. Then select \n the INSTALL/CHECK MESSAGE PackMan option to load the build.\n \nPatch Components:\n \n2. From the Kernel Installation and Distribution System Menu, \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter the patch or build name. \n PSO*7.0*722\n \n-----------------\n NOTE: Using <spacebar><enter> will not bring up a \n Multi-Package build even if it was loaded \n immediately before this step. It will only \n bring up the last patch in the build.\n \n B. Select the Backup a Transport Global option to create \n a backup message. You must use this option for each\n patch contained in the Host File. For each patch you\n can specify what to backup; the entire Build or just\n Routines. The backup message can be used to restore\n \n just the routines or everything that will restore your \n system to pre-patch condition.\n \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n \n all of the components of this patch, such as \n routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the \n patch to install. \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//', answer NO.\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \ncomponent updates that facilitate temporary and mailing address changes\nFiles & Fields Associated:\n install? NO//', answer NO.\n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//', answer NO.\n \n \nPost-Installation Instructions:\n-------------------------------\nN/A\n \n \n \n \nBack-Out/Roll Back Plan:\n------------------------ \nPlease refer to the Deployment, Installation, Back-out, and Rollback \n document associated with this patch.\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \nForms Associated:\n \nForm Name File Number New/Modified/Deleted\n--------- ----------- --------------------\nto the PATIENT FILE (#2). These components support the VA Health Connect\nN/A\n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \nOptions Associated:\n \nCustomer Relations Management (VAHC CRM) pharmacy project.\nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nPSO WEB CHART Broker Modified\n \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\n \nN/A\n \n \nSecurity Keys Associated: \n \nSecurity Key Name\n-----------------\nN/A\n \n \nThe RPC's provide functionality to retrieve and update the temporary and \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- --------------------\nmailing addresses. The RPC's also provide the functionality to delete the\nPSO ADDRESS UPDATE New\nPSO GET ADDRESS New\nPSO TEMP ADDRESS ACTIVE FLAG New\nPSO DEL TEMPORARY ADDDRESS New\nPSO GET TEMPORARY ADDRESS Deleted\nPSO TEMP ADDRESS UPDATE Deleted\n \n \nParameter Definitions Associated:\n \ntemporary address and update the TEMPORARY ADDRESS ACTIVE? (FILE \nParameter Name New/Modified/Deleted\n-------------- --------------------\nN/A\n \nEntities Associated:\n \nEntity Name New/Modified/Deleted\n----------- --------------------\nPSO MAILING ADDRESS New \n \n#2,.12105)\nAdditional Information:\n-----------------------\n \n \nBlood Bank Team Coordination:\n-----------------------------\nN/A\n \n \nNew Service Requests (NSRs):\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\n 1. During the completion process of renewing a prescription, the\n leading 3 digits as numeric, otherwise it reports an undefined error\n when using the Archive CMOP Data [PSX ARCHIVE] option.\n \n 3. When using the All Reports [PSO MGMT MONTHLY ALL REPORTS] option,\n the date entry for the prompt "Beginning MONTH/YEAR :", accepts only\n the full name of the month and the 4 digit year. This patch corrects this\n problem to allow any valid month/year format.\n software gathers the co-pay information for patient status SC LESS THAN\n 50%. During this process, there is a possibility of getting an undefined\n error. This patch fixes this problem.\n \n 2. This patch modifies the Input Template of the SITE NUMBER field (#.06)\n of the OUTPATIENT SITE file (#59) from eight free text characters to\n three numeric and five alphanumeric characters. The Consolidated Mail\n Outpatient Pharmacy (CMOP) V. 2.0 package expects this field to have the\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nThe Inbound Electronic Prescribing (eRx) Phase 3 Enhancements delivered in\nThis patch can be installed at all sites, including EHRM converted sites.\nPSO ERX VIEW ORIGINAL ERX Action Modified\n37.eRx Prescriber Phone # displayed on Pending Order and Active Rx\n ---------------------------------------------------------------------------\n The eRx Prescriber Phone # will now be displayed for the eRx Pending Order\n as well as for an ACTIVE eRx prescription.\n Pending order:\n -------------\n Name: TEST,PROVIDER MD |Name: TEST,PROVIDER \n NPI : xxxxxxxxxx Phone: 9999999999 |NPI : xxxxxxxxxxx Phone: 9999999999\n DEA : XX9999999 |DEA : \n Clinic: BFS - Gastroenterology |Class: NURSE PRACTITIONER \nPSO ERX VIEW REQUEST ERX Action Modified\n Active order:\n ------------\n eRx HT: (cm)() eRx WT: (kg)() \n \n eRx Provider: xxxxxxxxxxxxxx DEA: xxxxxxxxxx\n eRx Phone: xxxxxxxxxx NPI: xxxxxxxxxx\n \n38.VistA Drug Edit capability on the Single eRx View/Display screen\n ---------------------------------------------------------------------------\n When viewing the eRx int he Single eRx View/Display screen the users will\nPSO ERX VIEW RESPONSE ERX Action Modified\n now be able to edit the drug fields. Before, this capability was only\n available in the Validate Drug (VD action) screen. This will allow users\n to do quick edits such as Indication or Patient Instructions field without\n having to go into the Validate Drug screen. The edit can be done \n exclusively by typing the # of the field the user intends to edit, if #1\n (Drug) is selected the user will be prompt to edit all other fields as\n well. This sample shows #'s before each editable field:\n ...\n DRUG AUTO-MATCHED | VALIDATED by rrrrrrr on 11/2/24@14:55:54\n __________________________________________________________________________\nPSO ERX VIEW SUGGESTED RX Action Modified\n Drug: Suprep Bowel Prep Kit 1.6 g-17|1)Drug: COLON ELECTROLYTE LAVAGE ORAL\n g-17.5 g/177 mL liquid | SOLN KIT \n \n Drug Form: LIQUID DOSAGE FORM | *** NON-FORMULARY *** \n Substitution? YES Renewals? YES | \n SIG: |SIG: \n 354 ml orally 177 ml evening before| TAKE 1 KIT BY MOUTH EVERY MORNING \n and 177 morning of colonoscopy | \n Prescriber Drug Use Evaluation: | Verb: TAKE \n None |2) Dosage: 1 KIT \nPSO HIDDEN ACTIONS #2 Menu Modified\n | Route: ORAL \n | Schedule: QAM \n | \n |3)Patient Instructions: \n | \n Provider Notes/Comments: |4)Provider Comments: \n | \n |5)Pat. Status: SC \n | \n Quantity: 354 |6)Quantity: 33 \nPSO LM BACKDOOR PRTCL USRSCR VERIFY Action Modified\n Dispense Unit: MILLILITER | Dispense Unit: TAB \n Qty Qualifier: Original Quantity | \n Days Supply: 1 Refills: 0 |7)Days Supply: 33 8)Refills: 11 \n |9)Routing: MAIL \n |10)Clinic: CWM/NO/PHARM/INBOUND ERX \n Written: 07/23/24 Effective: | \n Primary Dx: |11)Indications: \n ...\n \n39.After AV it will go back to Single eRx View/Display (VAMC's only)\nPSO LM EXIT2 Action Modified\n ---------------------------------------------------------------------------\n A small change was made to streamline the processing of eRx's. Once the\n user accepts validation (AV action) for a patient, provider or drug, the\n software will take them automatically to the Single eRx View/Display\n screen. This ways they don't have to type "^" or <ENTER>'s in order to\n go back to the Single eRx View/Display screen.\n \n40.Default for Copy PATIENT INSTRUCTIONS from Rx#12345? Y// changed to 'NO'\n ---------------------------------------------------------------------------\n When accepting a VistA Drug suggestion for an eRx, the software prompts the\nPSO LMOE MOVE TO NEXT PATIENT Action Modified\n user if they also want to copy the Patient Instructions from the suggested\n VistA Rx if it has this field populated. The default for this prompt was\n 'YES' and it is being changed to 'NO'.\n \n41.Jump to eRx (JE) action modification at the Patient level\n ---------------------------------------------------------------------------\n The Jump to eRx (JE) action used to jump from Backdoor Pharmacy back to the\n eRx Holding Queue is being modified to included all variations of the eRx\n Patient that are matched to the same VistA Patient. Instead of jumping to\n the eRx Single Patient Queue the user will now be taken to the eRx\n \n Medication Queue with the VistA Patient filter automatically set with the\n patient that was selected in Backdoor Pharmacy. Therefore, the list items\n will include all eRx's from all eRx Patients that have been matched to the\n VistA Patient. \n \n42.DEA Nightly Update Job w/ Data from DEA/DOJ\n ---------------------------------------------------------------------------\n A new menu option called DEA Number Nightly Update with DEA/DOJ Data [PSO\n DEA/DOJ NIGHTLY DATA UPD] is being created by this patch. This option is\n used for automatically updating the Kernel DEA NUMBERS file (#8991.9) with\nSecurity Keys Associated: \n the latest prescriber DEA information from DEA/DOJ database. It will run\n nightly and it will update DEA data for entries that are 30 days or less\n from expiring. This new option will be added to the list of options that\n can be edited via the existing Queue Background Jobs [PSO AUTOQUEUE JOBS]\n option.\n \n43.Patient address will ignore differences between similar words\n ---------------------------------------------------------------------------\n The patient address comparison between eRx and VistA patients is being \n enhanced to recognize and ignore these differences listed below by not\n \n \n reversing the video if these are the only difference between the addresses:\n \n DR = DRIVE APT = APARTMENT STE = SUITE\n AVE = AVENUE W = WEST S = SOUTH\n ST = STREET NW = NORTHWEST SW = SOUTHWEST\n HGWY = HIGHWAY NE = NORTHEAST SE = SOUTHEAST\n BLVD = BOULEVARD CT = COURT RD = ROAD\n TER = TERRACE PKY = PARKWAY\n \n44.Conversion issue with Patient Weight when prescriber sent in g (grams)\nSecurity Key Name New/Modified/Deleted \n ---------------------------------------------------------------------------\n When the outside prescriber sent in a patient weight in grams (g) the\n software was not making the proper conversion to kilograms and it was\n displaying the value in grams with a 'kg' indication in the Patient\n Validation scree, as shown below:\n ...\n Weight(kg): 107161.2 |Weight(kg): 107.95 \n \n ...\n After fix:\n----------------- --------------------\n ...\n Weight(kg): 107.16 |Weight(kg): 107.95 \n ...\n \n45.HFF (Hold for Future Fill) will now set the Effective Date if none\n ---------------------------------------------------------------------------\n If an eRx is received without an Effective Date value and No Refills and\n the user decides to hold it with a future fill date (HFF), if the date \n entered by the user is more than 30 days from eRx Written Date the software\n will set the Effective Date on the eRx with the future date entered by the\nPSO ERX WORKLOAD RPH New\n user when placing the eRx on Hold with the HFF code.\n \n46.CAO status will automatically be set with CAA (MbM only)\n ---------------------------------------------------------------------------\n When a cancelation is received from the outside prescriber and the eRx\n status is set to CAO (CANCEL PROCESS COMPLETE) the software will \n automatically set it to CAA (CANCEL REQUEST ACKNOWLEDGED) for Meds-by-Mail\n sites. The reason is because the volume of CAO records at Meds-by-Mail\n makes it impossible to acknowledge them manually one by one.\n \nPSO ERX WORKLOAD TECH Modified\n47.Cancelations of RxRenewal and RxChange were not DCing Pending/Active Order\n ---------------------------------------------------------------------------\n When a RxRenewal or Rx Change response had been processed from the eRx \n Holding queue and were either on the Pending or Active order queue and the\n outside prescriber sent in a cancellation for the renewal or accepted\n change request the software was failing to proper cancel (DC) the pending\n or active order for the corresponding medication. This issue is being \n addressed by this patch.\n \n48.Allergies compare between eRx and VistA were Case Sensitive\n \n ---------------------------------------------------------------------------\n When comparing incoming list of allergies from the external prescriber with\n the list of VistA allergies the software was performing a case sensitive\n comparison. In other words, if the outside prescriber sent in 'Tomato' and\n in VistA we had 'TOMATO' it would reverse the video on both because it\n assumed them to be different. This issue is being addressed by this patch.\n \n49.Update to the Pharmacist Enter/Edit [PSO RPH] option\n ---------------------------------------------------------------------------\n Previously this option was used to allocated and de-allocate the PSORPH key\nTemplates Associated: \n that identifies a user as a pharmacist on the system. It is now being \n modified to allow allocation and de-allocation of the following eRx keys:\n \n PSO ERX WORKLOAD TECH \n PSO ERX WORKLOAD RPH \n \n These keys are mostly used by MbM to flag a user as a workload processing\n technician or pharmacist, which prevents them from skipping orders, \n effectively imposing a FIFO (First-In-First-Out) processing of incoming\n eRx and Pending orders.\n \n \n50.New option for Batch Change Request and VistA Drug Replacement\n ---------------------------------------------------------------------------\n The new option Batch eRx Change Request/VistA Drug Replacement [PSO ERX \n BATCH CH REQ/DRUG SWAP] placed under the Supervisor Functions [PSO\n SUPERVISOR] menu option. It is used to perform two distinct tasks:\n \n Submission of Multiple eRx Change Requests\n Replacement of the Vista Dispense Drug on finished prescriptions (MbM only)\n \nTemplate Name Type File Name (#) New/Modified/Deleted \n The user will respond few prompts, specific to the task they want to\n perform, a list will be presented before the user actually perform the\n update. The Replacement of the VistA Dispense Drug is available to MbM \n (Meds-by-Mail) only users. For more information about this option please\n review the user documentation released along with this patch.\n \n51.eRx Pending Order Suggested FILL DATE auto calculation \n ---------------------------------------------------------------------------\n Currently, the Fill Date field for an eRx Pending Order is always set to \n the current date. In some cases this is not ideal because the patient might \n------------- ---- ------------ --------------------\n still have enough medication to last a few more days and a future fill \n date, based on the last fill for the medication might be more appropriate. \n \n The algorithm will auto calculate the suggested Fill Date using the \n following logic: \n Requirement: \n - A previous prescription for the exact same drug must be found on the \n patient's profile \n - The SIG from the previous prescription must match exactly with the \n SIG for the new eRx Pending Order \nPatch Components \nPSO ERX ALL RXS QUEUE List 52.49 Modified\n \n Suggested Future Fill Date: \n - If Last Fill is Released and the Release Date + Days Supply results \n in a future date, this futures date suggested as the Fill Date for \n the eRx Pending Order. \n - If the CMOP Transmission status for the Last Fill is TRANSMITTED or\n RE-TRANSMITTED, the Fill Date for the eRx Pending Order will be\n today's date + Days Supply for the Suspended fill. \n - If Last Fill is Suspended with a future Fill Date this future date\n will be suggested as the Fill Date for the eRx Pending Order. \nPSO ERX BATCH ERX CHANGE List 52 New\n \n52.Added three (3) Remove Reason codes to the ERX SERVICE REASON CODES \n FILE #52.45.\n -----------------------------------------------------------------------\n The three codes are:\n REM81 Prior Authorization Denied\n REM82 No Community Care Authorization for this Prescription\n REM83 Patient Not Found in Local VA Database\n \n \nPSO ERX SINGLE ERX DISPLAY List 52.49 Modified\nTest Sites: \n----------\nCentral Texas VAMC, Temple TX\nMeds-By-Mail\nPSO ERX SINGLE PATIENT QUEUE List 52.49 Modified\nPSO LM ACTIVE ORDERS List 52 Modified\n \nRemote Procedures Associated: \n \nRemote Procedure Name New/Modified/Deleted \n--------------------- --------------------\n================\nN/A \n \nParameter Definitions Associated: \n \nParameter Name New/Modified/Deleted \n-------------- --------------------\nN/A \n \nAdditional Information: \n-----------------------\nFiles & Fields Associated: \nNew Service Requests (NSRs): N/A \n \nPatient Safety Issues (PSIs): \n-----------------------------\nN/A\n \nDefect Tracking System Ticket(s) & Overview: \n============================================\n \n1. Patient address and primary phone displayed on the Single eRx View screen\n \n ---------------------------------------------------------------------------\n To easily confirm the patient's identity, the patient's address and\n phone number are included on both the eRx and VistA sides of the Single\n eRx View/Display landing page, as shown below (without the reverse or\n highlighted video features).\n \n Single eRx View/Display Oct 25, 2024@10:49:03 Page: 1 of 3\n ---------------------------------------------------------------------------\n eRx Patient: TESTONE,MBMONE eRx Reference #: 19176255\n eRx Msg Type: NEWRX Written: 04/16/21\nFile Name (#) Field Name (#) New/Modified/Deleted \n eRx Status: I - IN PROCESS\n ---------------------------------------------------------------------------\n ERX | VISTA \n ---------------------------------------------------------------------------\n PATIENT MANUALLY-MATCHED | VALIDATED by USER,USER on 4/16/24@10:53:08 \n ---------------------------------------------------------------------------\n Name: TESTONE,MBMONE |Name: MBMONE,TESTONE \n DOB : FEB 99, 9999 SSN : |DOB : FEB 99, 9999 SSN : 000-00-0000\n Phone: 2222222222 |Phone: (222) 222-2222 \n 1234 FAKE ADDRESS LINELIN... 82240 | 1234 FAKE ADDRESS LINELIN... 82240\n----------------- ---------------- --------------------\n .\n .\n .\n ---------------------------------------------------------------------------\n + Enter ?? for more actions \n VP VALIDATE PATIENT VM VALIDATE PROVIDER VD VALIDATE DRUG/SIG\n Select Action: Next Screen// \n \n2. Patient Pharmacy Narrative displayed on the Single eRx View screen\n ---------------------------------------------------------------------------\nERX HOLDING QUEUE (#52.49)\n If the VistA patient is matched and it contains text in the Pharmacy \n Narrative field, it will be displayed in the eRx Single View/Display Screen\n across the screen at the bottom of the Patient section and just above the\n Provider section, as shown below:\n \n Single eRx View/Display Oct 25, 2024@10:49:03 Page: 1 of 3\n ---------------------------------------------------------------------------\n eRx Patient: TESTONE,MBMONE eRx Reference #: 19176255\n eRx Msg Type: NEWRX Written: 04/16/21\n eRx Status: I - IN PROCESS\n SUGGESTED VISTA RX (#.15) New\n ---------------------------------------------------------------------------\n ERX | VISTA \n ---------------------------------------------------------------------------\n PATIENT MANUALLY-MATCHED | VALIDATED by USER,USER on 4/16/24@10:53:08 \n ---------------------------------------------------------------------------\n Name: TESTONE,MBMONE |Name: MBMONE,TESTONE \n DOB : FEB 99, 9999 SSN : |DOB : FEB 99, 9999 SSN : 000-00-0000\n Phone: 2222222222 |Phone: (222) 222-2222 \n 1234 FAKE ADDRESS LINELIN... 82240 | 1234 FAKE ADDRESS LINELIN... 82240\n VistA Narrative: PATIENT PREFER SAFETY CAPS\nthis patch is a continuation effort to convert all of the MbM Class 3\n MATCHED DRUG/SUPPLY (#3.2) Modified\n PROVIDER AUTO-MATCHED | VALIDATED by USER,USER F on 10/21/24@16:45:28 \n ... \n \n3. eRx and VistA Patient SSN display\n ---------------------------------------------------------------------------\n To quickly verify the patient's identity, the full SSN is displayed on the\n eRx and VistA sections of the Single eRx View/Display landing page, aligned\n with the DOB, as shown below (without the reverse or highlighted video\n features).\n \n VISTA ROUTING (#20.4) Modified\n Single eRx View/Display Oct 25, 2024@10:49:03 Page: 1 of 3\n ---------------------------------------------------------------------------\n eRx Patient: TESTONE,MBMONE eRx Reference #: 19176255\n eRx Msg Type: NEWRX Written: 04/16/21\n eRx Status: I - IN PROCESS\n ---------------------------------------------------------------------------\n ERX | VISTA \n ---------------------------------------------------------------------------\n PATIENT MANUALLY-MATCHED | VALIDATED by USER,USER on 4/16/24@10:53:08 \n ---------------------------------------------------------------------------\n \n Name: TESTONE,MBMONE |Name: MBMONE,TESTONE \n DOB : FEB 99, 9999 SSN : |DOB : FEB 99, 9999 SSN : 000-00-0000\n Phone: 2222222222 |Phone: (222) 222-2222 \n 1234 FAKE ADDRESS LINELIN... 82240 | 1234 FAKE ADDRESS LINELIN... 82240\n ...\n ---------------------------------------------------------------------------\n + Enter ?? for more actions \n VP VALIDATE PATIENT VM VALIDATE PROVIDER VD VALIDATE DRUG/SIG\n Select Action: Next Screen// \n \nERX SERVICE REASON CODES file (#52.45) Modified\n4. Provider phone displayed on the Single eRx View screen\n ---------------------------------------------------------------------------\n To quickly verify the Provider, the provider's phone number is included\n and shown on both the eRx and VistA portions of the Single eRx View/Display\n landing page alongside the NPI, as shown below (without the reverse or\n highlighted video features).\n \n Single eRx View/Display Oct 25, 2024@10:49:03 Page: 1 of 3\n ---------------------------------------------------------------------------\n eRx Patient: TESTONE,MBMONE eRx Reference #: 19176255\n CH REQ REASON TEXT BY DIVISION sub-file (#52.4521) New\n eRx Msg Type: NEWRX Written: 04/16/21\n eRx Status: I - IN PROCESS\n ---------------------------------------------------------------------------\n ERX | VISTA \n ---------------------------------------------------------------------------\n PATIENT MANUALLY-MATCHED | VALIDATED by USER,USER on 4/16/24@10:53:08 \n ---------------------------------------------------------------------------\n Name: TESTONE,MBMONE |Name: MBMONE,TESTONE \n DOB : FEB 99, 9999 SSN : |DOB : FEB 99, 9999 SSN : 000-00-0000\n Phone: 2222222222 |Phone: (222) 222-2222 \n OUTPATIENT DIVISION (#.01) New\n 1234 FAKE ADDRESS LINELIN... 82240| 1234 FAKE ADDRESS LINELIN... 82240\n ---------------------------------------------------------------------------\n PROVIDER MANUALLY-MATCHED | VALIDATED by USER,USER on 4/16/24@11:42:03 \n ---------------------------------------------------------------------------\n Name: PROVIDER,NAME |Name: PROVIDER,NAME \n NPI : xxxxxxxxx Phone: xxxxxxxxxxx |NPI : xxxxxxxxxxx Phone: (000)\n DEA : xxxxxxxxx DEA :\n Clinic: TEST CLINIC \n ...\n ---------------------------------------------------------------------------\n CHANGE REQUEST REASON TEXT (#1) New\n + Enter ?? for more actions \n VP VALIDATE PATIENT VM VALIDATE PROVIDER VD VALIDATE DRUG/SIG\n Select Action: Next Screen// \n \n5. Missing Patient Instruction alert\n ---------------------------------------------------------------------------\n After accepting the suggested Rx on the eRx Drug Validation Edit action\n screen, the user will be prompted whether they want to copy the patient\n instructions from the suggested Rx into the eRx, as shown below (without\n the reverse or highlighted video features)\n CHANGE REQUEST REASON TEXT (#.01) New\n \n Select Item(s): Next Screen// E Edit \n |Sugg. 1 of 1 - 04/16/21|\n ERX MED VISTA MED |From Rx#: 3004815 |\n ___________________________________________________________________________\n Drug: Sinemet 25 mg-100 mg oral tablet |Drug: CARBIDOPA 25/LEVODOPA 100MG\n Substitution? YES Renewals? YES |Drug Message:\n | NATL FORM\n ________________________________________|__________________________________\n SIG: |SIG:\n \n 1 1/2 tab Oral TID | TAKE ONE AND ONE-HALF TABLETS (OF\n | 25/100) BY MOUTH THREE TIMES A DAY\n ________________________________________|__________________________________\n Quantity: 135 |Quantity: 135\n Dispense Unit: TABLET DOSING UNIT |Dispense Unit: TAB\n ________________________________________|__________________________________\n Days Supply: Refills: 6 |Days Supply: 30 Refills: 6\n ________________________________________|__________________________________\n ACTION on SUGGESTION: (A)CCEPT (F)ORGET (E)XIT: EXIT// ACCEPT\n \nForms Associated: \n Rx #3004815 PATIENT INSTRUCTIONS:\n FOR PARKINSON'S DISEASE\n \n Copy PATIENT INSTRUCTIONS from Rx #3004815? YES// \n \n a)If YES is chosen by the user, all fields on the eRx Drug Validation screen\n will have its fields updated with any available data.\n \n b)If NO is chosen by the user, all fields on the eRx Drug Validation screen\n will have its fields updated with any available data, with the exception\nmodifications into Class 1. Below is a summary of the changes being\n \n of the Patient Instruction field. The user can manually edit the field as\n they currently do.\n \n c)When the user inputs the up-caret symbol (^), no changes are made.\n \n6. RxChangeRequest 'Script Clarification' reason message templates\n ---------------------------------------------------------------------------\n The CHANGE REQUEST CODE for 'Script Clarification' has been updated to\n allow the pharmacist/technician to choose a reason code linked to a\n pre-made question template in the <RxChangeRequest> <ReasonText> field. The\nForm Name File Number New/Modified/Deleted \n user will be prompted to choose a CHANGE REQUEST SUB-CODE from the options\n provided, as shown below.\n . . .\n Select Action: Next Screen// EC EC \n ---------------------------------------------------------------------------\n ORIGINAL ERX \n ---------------------------------------------------------------------------\n eRx Drug : IBUPROFEN 200MG TAB\n eRx SIG : TAKE ONE TABLET A DAY ON AN EMPTY STOMACH\n eRx Notes: This is a TEST NOTE.\n--------- ----------- --------------------\n Drug Form: Strength: \n Qty Qualifier: Original Quantity Qty Unit of Measure: \n Qty: 20 Days Supply: 30 Refills: 3 Substitutions: YES\n ---------------------------------------------------------------------------\n \n Select one of the following:\n \n D DUE (Drug Use Evaluation) \n G Generic Substitution\n OS Out of Stock\nN/A \n P Prior Authorization Required\n S Script Clarification\n T Therapeutic Interchange/Substitution\n U Prescriber Authorization\n \n CHANGE REQUEST CODE: s Script Clarification\n \n Select one of the following:\n \n PRN - PRN Directions\n \n UDD - As Directed Directions\n COD - Conflicting Directions\n MSD - Missing Directions\n RIJ - Route of Injection\n VEF - Verify Formulation\n VLQ - Verify Low Quantity\n VPQ - Verify Package Quantity\n AUT - Prescriber Not Authorized\n \n CHANGE REQUEST SUB-CODE: PRN Directions\nMail Groups Associated: \n \n NOTE TO PROVIDER:....\n \n ==[ WRAP ]==[INSERT ]======< NOTE TO PROVIDER >=[Press <PF1>H for help]===\n VA policy prohibits filling prescriptions with only "AS DIRECTED" for\n directions. Please indicate frequency of administration.\n \n \n \n <=======T=======T=======T======T======T=======T=======T======T=====T>=====\n \n \n7. Option to Edit RxChangeRequest Reason Template Text\n ---------------------------------------------------------------------------\n In the eRx Patient Centric Queue screen, a new hidden action called 'CRT CR\n Default Text Edit' has been added to enable users who hold the PSDMGR \n security key to modify the default RxChangeRequest Reason template. Please,\n refer to the user documentation for more information about this new option.\n \n eRx Patient Centric Queue Oct 25, 2024@14:58:15 Page: 1 of 1\n ---------------------------------------------------------------------------\nMail Group Name New/Modified/Deleted \n LOOK BACK DAYS: 365 CS/NON-CS: BOTH (II-V) MAX. QUEUE SIZE: 999\n ERX STATUS: ALL\n ---------------------------------------------------------------------------\n # PATIENT DOB SSN EDv NW WT IP HD CCR OTH TOT\n ---------------------------------------------------------------------------\n 1. TESTMAN,ONE 11/13/1986 000-00-0000 269 0 1 0 0 0 0 1\n 2. TESTMBMTWO,TWO 01/23/1934 111-00-0000 262 0 0 0 1 0 0 1\n ---------------------------------------------------------------------------\n + Enter ?? for more actions \n SPAT Sort By Patient SQ Search Queue LBD Change Look Back Days\n--------------- --------------------\n RX Rx List View RAF Remove All Filters REF Refresh List\n Select Item(s): Next Screen// ??\n \n The following actions are also available:\n CS Group By CS + Next Screen GO Go to Page\n SDOB Sort By DOB - Previous Screen PS Print Screen\n SED Sort By Elapsed Days UP Up a Line PT Print List\n NP Next Patient DN Down a Line SL Search List\n CV Change View FS First Screen QU Quit\n CRT CR Default Text Edit LS Last Screen\nN/A \n \n8. Full drug name display when user selects the DET hidden action\n ---------------------------------------------------------------------------\n For the eRx Single Patient Queue and the eRx Medication Queue when the user\n selects the DET (Show/Hide Details) action it will display the complete \n eRx Drug name as shown below.\n \n eRx Single Patient Queue Oct 25, 2024@15:10:29 Page: 1 of 1\n ---------------------------------------------------------------------------\n eRx PATIENT: Ttttttttttttt SEX: M DOB: 01/05/60(64)\ndelivered in this patch. For a more comprehensive description of the changes\n \n LOOK BACK DAYS: 365 STATUS: ACTIONABLE SSN: xxxxxxxxx MATCHING\n ---------------------------------------------------------------------------\n # ERX ID DRUG NAME PROVIDER NAME REC.DATE^STA PT PR DR\n ---------------------------------------------------------------------------\n 1. 4452 OXYMETAZOLINE HCL 0.05 PROVIDER,ONE 03/21/24 W MV AV MV\n 2. 5992 FLURANDRENOLIDE 4MCG/S PROVIDER,ONE 03/22/24 I MV AV \n 3. 33456 AMPHETAMINE/DEXTROAMPH PROVIDERS,TWO 03/22/24 I MV A \n 4. 55555 DEXTROAMPHETAMINE SULF PROVIDER,ONE 03/22/24 I MV AV \n 5. 66662345 BUPRENORPHINE 2MG/NALO PROVIDER,ONE 03/22/24 I MV AV \n \nOptions Associated: \n \n _________________________________________________________________________ \n Select the entry # to view or ?? for more actions \n DET Show/Hide Details IAS Include All Statuses LBD Change Look Back Days\n Select: Quit// DET\n \n eRx Single Patient Queue Oct 25, 2024@15:15:30 Page: 1 of 4\n --------------------------------------------------------------------------\n eRx PATIENT: Tttttttttttt SEX: M DOB: 01/05/60(64)\n LOOK BACK DAYS: 365 STATUS: ACTIONABLE SSN: xxxxxxxxxx MATCHING\n \n --------------------------------------------------------------------------\n # ERX ID PROVIDER NAME REC.DATE^STA PT PR DR\n --------------------------------------------------------------------------\n 1. 4452 PROVIDER,ONE 03/21/24 W MV AV MV\n eRx Drug: OXYMETAZOLINE HCL 0.05% NASAL SPRAY \n eRx Qty: 120 eRx # of Refills: 3 eRx Days Supply: 90\n SIG: 1 tablet Orally Once a day 90 day(s).This is a recommended dosage.\n 2. 5992 PROVIDER,ONE 03/22/24 I MV AV\n eRx Drug: FLURANDRENOLIDE 4MCG/SQCM TAPE,8 \n eRx Qty: 120 eRx # of Refills: 3 eRx Days Supply: 90\nOption Name Type New/Modified/Deleted \n SIG: 1 tablet Orally Once a day 90 day(s).This is a recommended dosage.\n 3. 33456 PROVIDERS,TWO 03/22/24 I MV A\n eRx Drug: AMPHETAMINE/DEXTROAMPHETAMINE 20mg \n eRx Qty: 120 eRx # of Refills: 3 eRx Days Supply: 90\n _________________________________________________________________________\n + Select the entry # to view or ?? for more actions \n DET Show/Hide Details IAS Include All Statuses LBD Change Look Back Days\n Select: Next Screen// \n \n9. VistA Drug Search\n----------- ---- --------------------\n ---------------------------------------------------------------------------\n A new search option called 'VISTA DRUG' has been added in the SQ Search\n Queue action, enabling users to search for eRx's by VistA Drug already\n matched/linked to the eRx drug as shown below.\n \n Select Item(s): Next Screen// sq Search Queue \n \n Select one of the following:\n \n 1 ERX PATIENT\nPSO DEA/DOJ NIGHTLY DATA UPD New\n 2 ERX DATE OF BIRTH\n 3 RECEIVED DATE RANGE\n 4 ERX PROVIDER\n 5 ERX STATUS\n 6 DRUG NAME\n 7 MESSAGE TYPE\n 8 ERX REFERENCE NUMBER\n 9 VISTA RX #\n 10 VISTA PATIENT\n 11 VISTA PROVIDER\nPSO ERX BATCH CH REQ/DRUG SWAP New\n 12 MATCH STATUS\n 13 VISTA DRUG\n \n SEARCH BY: 13 VISTA DRUG\n \n VISTA DRUG: ROSUVASTATIN\n 1 ROSUVASTATIN CA 10MG TAB CV350 NATL FORM \n 2 ROSUVASTATIN CA 2.5MG (1/2 X 5MG) TAB CV350 NATL FORM\n (INPT USE ONLY) \n 3 ROSUVASTATIN CA 20MG TAB CV350 NATL FORM *TABS SPLIT*\nPSO RPH Modified\n 4 ROSUVASTATIN CA 40MG TAB CV350 NATL FORM *TABS SPLIT*\n 5 ROSUVASTATIN CA 5MG TAB CV350 NATL FORM *TABS SPLIT*\n \n CHOOSE 1-5: 4 ROSUVASTATIN CA 40MG TAB CV350 NATL FORM *TABS SPLIT*\n \n Select one of the following:\n \n 1 ERX PATIENT\n 2 ERX DATE OF BIRTH\n 3 RECEIVED DATE RANGE\nPSO SUPERVISOR Modified\n 4 ERX PROVIDER\n 5 ERX STATUS\n 6 DRUG NAME\n 7 MESSAGE TYPE\n 8 ERX REFERENCE NUMBER\n 9 VISTA RX #\n 10 VISTA PATIENT\n 11 VISTA PROVIDER\n 12 MATCH STATUS\n 13 VISTA DRUG (ROSUVASTATIN CA 40MG TAB)\n \n \n SEARCH BY: \n \n eRx Medication Queue Oct 25, 2024@15:35:36 Page: 1 of 1\n --------------------------------------------------------------------------\n LOOK BACK DAYS: 365 CS/NON-CS: BOTH (II-V) MAX. QUEUE SIZE: 999\n FILTERED BY: DRUG(ROSUVASTATIN CA 40MG TAB)\n --------------------------------------------------------------------------\n # PATIENT DOB DRUG PROVIDER STA REC.DAT^\n 1. TESTMBMTWO,TWO T 06/99/46 ROSUVASTATIN PROVIDER,ONE HC 02/29/24\nplease refer to the documents listed in the Documentation section of this\nProtocols Associated: \n 2. TESTER,TEST1 A 07/99/48 rosuvastatin 40 PROVIDER,TWO I 03/15/24\n 3. TESTMBMONE,ONE A 01/99/60 ROSUVASTATIN CA PROVIDER,THREE HC 04/08/24\n \n \n \n \n Select the entry # to view or ?? for more actions \n SPAT Sort By Patient SQ Search Queue LBD Change Look Back Days\n PC Patient Centric View RAF Remove All Filters REF Refresh List\n Select Item(s): Next Screen// \n \n \n10. RxRenewalResponse Message Types under SQ\n ---------------------------------------------------------------------------\n The search query option MESSAGE TYPE has been modified. Upon entering\n certain message types (RE and CX) as listed below, the user will be\n prompted to enter the corresponding RESPONSE TYPE as indicated. In this\n prompt, users have the option to choose ALL to view all response types for\n the message type selected or select a specific response type as shown below.\n For additional details on this new change, please refer to the user manual\n documentation.\nProtocol Name Type New/Modified/Deleted \n \n SEARCH BY: 7 MESSAGE TYPE\n \n MESSAGE TYPE: RE RXRENEWALRESPONSE\n \n RESPONSE TYPE: ALL// ?\n \n Enter a response type from the list.\n \n Select one of the following:\n------------- ----- --------------------\n \n ALL ALL\n A APPROVED\n AWC APPROVED WITH CHANGES\n D DENIED\n DNP DENIED, NEW RX TO FOLLOW\n R REPLACE\n \n . . .\n \nPSO ERX ACCEPT ERX Action Modified\n MESSAGE TYPE: CX RXCHANGERESPONSE\n \n RESPONSE TYPE: ALL// ?\n \n Enter a response type from the list.\n \n Select one of the following:\n \n ALL ALL\n A APPROVED\nPSO ERX ACCEPT VALIDATION Action Modified\n AWC APPROVED WITH CHANGES\n D DENIED\n V VALIDATED\n \n Furthermore, the RXCHANGEREQUEST MESSAGE TYPE search has been altered. \n When the user inputs CR (RXCHANGEREQUEST) in the message type prompt, \n they will be prompted to enter the CHANGE REQUEST CODE. In this prompt,\n users can choose to either view all CHANGE REQUEST CODE or pick a\n specific CHANGE REQUEST CODE as shown below. Please refer the user manual\n documentation for further information regarding this new change.\nPSO ERX ACKNOWLEDGE Action Modified\n \n MESSAGE TYPE: CR RXCHANGEREQUEST\n \n Select one of the following:\n \n ALL ALL\n D DUE (Drug Use Evaluation) \n G Generic Substitution\n OS Out of Stock\n P Prior Authorization Required\nPSO ERX ADD COMMENT Action Modified\n S Script Clarification\n T Therapeutic Interchange/Substitution\n U Prescriber Authorization\n \n CHANGE REQUEST CODE: ALL//\n \n11.Search by Remove Reason codes\n ---------------------------------------------------------------------------\n The search query option MESSAGE TYPE has been modified. Upon entering\n certain eRx Status (RM and RJ) as listed below, the user will be prompted\nPSO ERX ALL PATIENTS CR DEFAULT TEXT EDIT Action New\n to enter the corresponding REMOVAL or REJECT REASON CODE as indicated. In\n this prompt, users have the option to choose ALL to view all REMOVAL or\n REJECT REASON CODE or select a specific response type as shown below. For\n additional details on this new change, please refer to the user manual \n documentation.\n \n . . .\n SEARCH BY: 5 ERX STATUS\n \n ERX STATUS: RM REMOVED\nPSO ERX ALL PATIENTS QUEUE HIDDEN ACTIONS Menu Modified\n \n REMOVAL REASON CODE: ALL// ?\n \n Enter the code associated with this action. Answer must be 1-10 \n characters in length.\n \n Answer with ERX SERVICE REASON CODES, or NUMBER\n Do you want the entire ERX SERVICE REASON CODES List? Y (Yes)\n Choose from:\n 216 REM01 Drug out of stock or on backorder and unavailable for \ndescription.\n MENU MERGE MENU ITEMS\n processing\n 217 REM02 Patient was not able to pick up\n 218 REM03 Prescription canceled by Provider\n 219 REM04 Prescription processed manually\n 220 REM05 Provider will cancel this eRx and submit another\n 221 REM06 Unable to mail prescription and patient unable to pick up\n 222 REM07 Unable to contact patient\n 223 REM08 Unable to contact provider\n 224 REM91 Undefined system error\n 225 REM92 Other\nPSO ERX ALL RXS INCLUDE ALL STATUSES Action New\n 1556 REM09 ERX Issue not resolved-Provider contacted\n \n REMOVAL REASON CODE: ALL// \n \n . . .\n SEARCH BY: 5 ERX STATUS\n \n ERX STATUS: RJ REJECTED\n \n REJECT REASON CODE: ALL// ?\nPSO ERX ALL RXS QUEUE HIDDEN ACTIONS MENU Menu Modified\n \n Enter the code associated with this action. Answer must be 1-10 \n characters in length.\n \n Answer with ERX SERVICE REASON CODES, or NUMBER\n Do you want the entire ERX SERVICE REASON CODES List? Y (Yes)\n Choose from:\n 203 PTT01 Patient not eligible\n 204 PTT02 Cannot resolve Patient\n 205 PVD01 Provider not eligible\nPSO ERX ALL RXS REMOVE FILTERS Action Modified\n 206 PVD02 Cannot resolve Provider\n 207 DRU01 Not eligible for refills\n 208 DRU02 Non-formulary drug\n 209 DRU03 Duplicate Prescription found for this Patient\n 210 DRU04 Invalid Quantity\n 211 DRU05 Duplicate therapeutic class\n 212 DRU06 CS prescription written/issue date has problems\n 213 ERR01 Multiple errors, please contact the Pharmacy \n 214 ERR02 Incorrect Pharmacy\n 215 ERR03 Issues with prescription, please contact the pharmacy\nPSO ERX BATCH CHANGE REQUEST MENU Menu New\n 1557 PVD03 Missing/bad digital signature on inbound CS ERX\n 1558 PVD04 Prescriber's CS credential is not appropriate\n 1559 PTT03 Patient's mailing address is missing/mismatched\n 1560 ERR99 Other\n \n REJECT REASON CODE: ALL// \n \n12.Provider Auto-Validation for CS Drugs\n ---------------------------------------------------------------------------\n The Provider Auto-Validation functionality released with patch PSO*7*700\nPSO ERX BATCH CHANGE REQUEST SELECT Action New\n (see item #5) will now be extended to digitally signed (indicating \n Controlled Substance) eRx's as well. The only additional check performed\n for auto-validating is that the VA provider must have a valid DEA# on file\n that matches the DEA# sent with the eRx. \n \n13.Ability to Un-Process VistA Rx with a DELETED status\n ---------------------------------------------------------------------------\n Sometimes an eRx prescriptions that have already been transmitted to CMOP\n must be un-processed so it can go back to the eRx Holding Queue. Therefore,\n an exception was implemented in the software to allow non-CS eRx \nPSO ERX BATCH CHANGE REQUEST SUBMISSION Action New\n prescriptions with a DELETED status to be un-processed even after they have\n been transmitted to CMOP.\n \n14.Allow Un-Accept and Re-Accept of Approved eRx Renewals\n ---------------------------------------------------------------------------\n When a Renewal request is Approved by the outside prescriber the eRx will \n got straight to the Pending Order without stopping at the eRx Holding Queue\n first. The software will now allow the user to Un-Accept such records and \n send them back to the eRx Holding Queue so an issue (e.g., Eligibility\n verification, etc.) can be worked on there. Once the issue has been \nPSO ERX BATCH INCLUDE ALL STATUSES Action New\n resolved the user will be able to re-accept the record without having to\n perform any matches or validations.\n \n15.Park Functionality in the eRx Holding Queue\n ---------------------------------------------------------------------------\n The Park functionality released by the patch PSO*7*441, released back in\n September of 2022 has now been implemented in the eRx Holding Queue. If the\n site has the Park functionality turned ON the user will be able to select\n PARK as an option for the PICKUP ROUTING besides MAIL or WINDOW, as shown\n below:\nPSO ERX BATCH VISTA DRUG REPLACEMENT Action New\n ...\n eRx Refills: 3\n # OF REFILLS: (0-3): 3// \n \n Select one of the following:\n \n M MAIL\n W WINDOW\n P PARK\n \nPSO ERX CHANGE REQUEST Action Modified\n PICKUP ROUTING: M//\n \n16.No auto-match if Provider is inactive\n ---------------------------------------------------------------------------\n A check was added to prevent an inactive VistA provider from being auto-\n matched to the eRx even if the NPI matches. Furthermore, if the inactive\n VistA Provider is a suggestion it will be automatically forgotten.\n \n17.Patient, Provider and Drug/SIG auto-matching based on suggestions\n ---------------------------------------------------------------------------\n \nPSO ERX DISPLAY MENU Menu Modified\n The auto-matching functionality is being further enhanced to utilize \n current VistA suggestions for Patient, Provider and Drug/SIG. For Patient \n and Provider if no auto-match was found the software will look for any \n existing suggestion and will auto-match to the latest VistA suggestion on\n file. In the case of Drug/SIG it will be greatly improved by matching not\n only the dispense drug but all fields from the suggested VistA Rx (if one\n exists), exactly as if the user accepted the suggestion manually.\n \n18.Updates to existing Accept(AC) action in Single eRx View/Display screen\n ---------------------------------------------------------------------------\nPSO ERX DRUG EDIT FROM SINGLE ERX VIEW Action New\n The existing Accept(AC) action in the Single eRx View/Display screen will\n automatically try perform the validation (AV) for Patient (except for MbM),\n Provider and Drug as well, if needed, before accepting the eRx. This\n action will still perform all the checks necessary by each individual\n record match and will display the result for validating each match\n separately.\n \n Note: Please, refer to the user documentation for more detailed \n information about this new functionality.\n \nPSO ERX DRUG VALIDATION HIDDEN MENU Menu Modified\n19.Ability to change the Hold code w/out Un-holding an eRx\n ---------------------------------------------------------------------------\n Users will now be able to switch the Hold code for an eRx on Hold for a\n different Hold code without having to un-hold the eRx. Once the user\n selects the Hold (H) action to hold an eRx already on software will inform\n them the eRx is already on hold and will ask if they want to change the\n Hold code, as shown below:\n \n Select Action: Next Screen// H Hold \n \nPSO ERX EDIT Action Modified\n This eRx is already in a 'HOLD' status.\n Would you like to change the hold status and comments? NO// YES\n \n Select HOLD reason code: HAL NO PATIENT ALLERGY ASSESSMENT\n Additional Comments (Optional): ASSIGNING CORRECT HOLD CODE\n \n20.First-In-First-Out (FIFO) processing for Complete Orders from OERR [PSO \n LMOE FINISH] option\n ---------------------------------------------------------------------------\n A FIFO order algorithm has been implemented for this option for users that\nPSO ERX ENTER PROGRESS NOTES Action Modified\n hold the newly created PSO ERX WORKLOAD RPH security key. Once the user \n holding this key enters the option they will be prompted for the Clinic\n they want to finish Pending Orders for and then if they want to process\n Flagged orders only. After answering these two prompts the option will \n automatically select the patient with the oldest record for the user to work\n on. The user will not be able to move to the next patient unless all the\n current patient's pending orders are either finished or flagged. \n \n Note: Please, refer to the user documentation for more detailed \n information about this new functionality.\nPSO ERX HIDDEN ACTIONS Action Modified\n \n21.eRx Prescriber Order Number in the Print\n ---------------------------------------------------------------------------\n The incoming prescriber order number will be displayed in Print (P) under\n the PRESCRIPTION INFORMATION section, as shown below:\n ... \n *************************PRESCRIPTION INFORMATION*************************\n Prescriber Order #: ECWIA-9382026-211005-828\n ...\n \nPSO ERX HOLD Action Modified\n22.Page breaking in the Print\n ---------------------------------------------------------------------------\n The Print (P) action will now page break one page at time instead of\n displaying the entire information, which forced the user to scroll up using\n the terminal scrolling capability.\n \n23.Allow Change Requests for eRx currently on Hold and Responses\n ---------------------------------------------------------------------------\n Two changes are being made to the Change Request (EC Action) functionality:\n \nPSO ERX JUMP TO ERX Action Modified\n a) The Change Request (EC) action will be allowed to be run on eRx's that\n are currently on Hold. \n \n b) The Change Request (EC) action will be allowed to be run Response eRx's.\n Before, the EC action was restricted to the NewRx records only. \n \n24. RxChangeRequest 'Therapeutic Interchange/Subst.' reason message templates\n ---------------------------------------------------------------------------\n The CHANGE REQUEST CODE for 'Therapeutic Interchange/Substitution' has been\n updated to allow the pharmacist/technician to choose a reason code linked\nPSO ERX JUMP TO ERX PATIENT Action Modified\n to a pre-made question template in the <RxChangeRequest> <ReasonText>\n field. The user will be prompted to choose a CHANGE REQUEST SUB-CODE from\n the options provided, as shown below.\n . . .\n Select one of the following:\n \n D DUE (Drug Use Evaluation) \n G Generic Substitution\n OS Out of Stock\n P Prior Authorization Required\nPSO ERX JUMP TO OP Action Modified\n S Script Clarification\n T Therapeutic Interchange/Substitution\n U Prescriber Authorization\n \n CHANGE REQUEST CODE: T Therapeutic Interchange/Substitution\n \n DSC - Days Supply Change\n FMC - Formulary Change\n \n CHANGE REQUEST SUB-CODE: DSC Days Supply Change\nEHRM Impact Statement:\nPSO ERX PATIENT ALLERGIES VIEW Action Modified\n \n ==[ WRAP ]==[INSERT ]======< NOTE TO PROVIDER >=[Press <PF1>H for help]===\n Pharmacy would like to dispense this medication for 90 days of supply\n instead 30 days. Please approve the 90-days option below or Cancel Rx and\n send a replacement.\n \n \n <=======T=======T=======T======T======T=======T=======T======T=====T>=====\n \n25.MbM Only: Auto-Holds for Pt. Eligibility and Non-Allergy Assessment \nPSO ERX PRINT Action Modified\n ---------------------------------------------------------------------------\n Upon arrival from the eRx Hub the eRx will be checked whether the VistA\n Patient was auto-matched or not. If it was successfully matched, the \n software will then check if the patient is eligible for ChampVA Rx\n benefit, if not, the software will automatically hold the eRx with an HEL \n (PATIENT ELIGIBILITY ISSUE). If eligible, the software will then check if\n the patient has an Allergy Assessment on file, if not, the software will\n automatically hold the eRx with an HAL (NO PATIENT ALLERGY ASSESSMENT).\n \n26.Menu changes to the Single eRx View/Display Screen \nPSO ERX REJECT Action Delete\n ---------------------------------------------------------------------------\n The bottom menu for the eRx Single eRx View/Display Screen was modified\n to increase the listing area by 2 lines. Only 3 actions will be available\n in the main menu: VD-VALIDATE PATIENT, VM-VALIDATE PROVIDER AND VD-VALIDATE\n DRUG/SIG. The actions P-Print, RJ-Reject and UH-Un Hold eRx were move to\n the Hidden actions section, as seen below:\n \n Main actions menu:\n -----------------\n + Enter ?? for more actions \nPSO ERX REMOVE Action Modified\n \n VP VALIDATE PATIENT VM VALIDATE PROVIDER VD VALIDATE DRUG/SIG\n H Hold RM Remove eRx AC Validate & Accept eRx\n Select Action: Next Screen// \n \n Hidden actions menu:\n -------------------\n Select Action: Next Screen// ??\n The following actions are also available:\n + Next Screen Q Quit VO View Original eRx\nPSO ERX RESEND CHANGE REQUEST Action Modified\n - Previous Screen AD Add Comment VRQ View Request eRx\n UP Up a Line ACK Acknowledge VRE View Response eRx\n DN Down a Line SH Status History REC Resend Change Request\n FS First Screen HL View History Log AC Validate & Accept eRx\n LS Last Screen EC eRx Change Request H Hold\n GO Go to Page PA Patient Allergies P Print\n RD Re Display Screen UR Un Remove eRx RJ Reject\n PS Print Screen JO Jump to OP RM Remove eRx\n PL Print List UX Un Process eRx UH Un Hold\n SL Search List PN Patient Progr. Note VSR View Suggested Rx\nPSO ERX SINGLE PATIENT NEXT DRUG Action Modified\n ADPL Auto Display(On/Off) AU View Audit Log\n \n27.New View Suggested Rx (VSR) action\n ---------------------------------------------------------------------------\n A new hidden action VSR was added to the eRx Single eRx View/Display hidden\n menu. This option will allow the user to view the VistA Rx that was used\n to suggest populate the prescription information for the current eRx. It \n will invoke the same layout from the View Prescription [PSO VIEW] option.\n Once the user selects VSR and there's a Suggested VistA Rx that was used\n to populate the eRx, the user will receive the following notice before\nPSO ERX SINGLE PATIENT QUEUE HIDDEN Menu Modified\n their are taken to viewing the suggested VistA Rx:\n \n Select Action: Next Screen// VSR \n \n _____________________________NOTICE______________________________________ \n \n You will be taken to the VistA prescription that was used to pre-populate\n the Drug fields (Product/SIG/Qty/Days Supply/# of Refills/Substitution)\n for this eRx (aka, 'Suggested VistA Rx'). This VistA Rx may or may not be\n for the same patient in this eRx being processed.\n ACTIONS MENU \n _________________________________________________________________________\n Type <Enter> to continue or '^' to exit: \n \n \n28.New value for ACTION on SUGGESTION prompt: (V) VIEW RX\n ---------------------------------------------------------------------------\n The suggestion prompt for the Drug/Sig will now offer a new option VIEW RX\n (V) to allow the user to view the VistA Rx information before accepting it.\n If the user select V a notice will be displayed before taking the user to\n view the Suggested VistA Rx detail, as shown below:\nPSO ERX STATUS HISTORY Action Modified\n \n |Sugg. 1 of 1 - 12/12/24|\n ERX MED VISTA MED |From Rx#: 9999999 |\n ___________________________________________________________________________\n Drug: DOXYCYCLINE HYCLATE 100MG TAB |Drug: DOXYCYCLINE HYCLATE 100MG TAB\n Substitution? YES Renewals? YES |\n _______________________________________|___________________________________\n SIG: |SIG:\n TAKE ONE TABLET BY MOUTH TWICE DAILY | TAKE ONE TABLET BY MOUTH TWICE \n AS DIRECTED BY PROVIDER AFTER SURGERY | DAILY\nPSO ERX UN-ACCEPT Action Modified\n _______________________________________|___________________________________\n Quantity: 28 |Quantity: 28\n Dispense Unit: |Dispense Unit: TAB\n _______________________________________|__________________________________\n Days Supply: 14 Refills: 0 |Days Supply: 14 Refills: 11\n _______________________________________|__________________________________\n ACTION on SUGGESTION: (A)CCEPT (V)IEW RX (F)ORGET (E)XIT: EXIT// V\n \n _____________________________NOTICE______________________________________ \n \n----------------------\nPSO ERX UN-PROCESS Action Modified\n You will be taken to the VistA Rx#9999999 that was entered in the past \n for the same Product (NDC/SIG/Qty/Days Supply/# of Refills/Substitution) \n for a different eRx. This VistA Rx may or may not be for the same patient\n in this eRx being processed.\n _________________________________________________________________________\n Type <Enter> to continue or '^' to exit: \n \n29.VistA Prescriber Class displayed on Single eRx and Pending Order\n ---------------------------------------------------------------------------\n The VistA Provider Class will now be displayed in the eRx Holding Queue\nPSO ERX UN-REMOVE Action Modified\n as well as when viewing an eRx Pending Order, as shown below:\n \n Name: TEST,PROVIDER MD |Name: TEST,PROVIDER \n NPI : 123456789 Phone: 9999999999 |NPI : 123456789 Phone: 9999999999 \n DEA : XX9999999 |DEA : \n Clinic: Wellness Clinic Inc. |Class: PHYSICIAN \n \n30.New Next Drug (ND) hidden action\n ---------------------------------------------------------------------------\n The Next Drug (ND) hidden action was introduced to facilitate the user \nPSO ERX UNHOLD Action Modified\n navigation to the Drug Validation screen for the actionable eRx from a \n single patient. This new action will work from two different screens in the\n eRx Holding Queue:\n \n a) eRx Single Patient Queue: if the user types "ND" in this screen it \n will take the user to the Drug Validation directly for the first \n actionable eRx for the current patient.\n \n b) Drug Validation: if the user types "ND" in this screen it will\n take the user to the Drug Validation screen for the next (based on\nPSO ERX VALIDATE DRUG Action Modified\n eRx Received Date/Time) actionable eRx for the patient. If the \n patient has only one actionable eRx it will stay in the same eRx.\n If they current eRx is the last eRx on file for the patient it will\n loop back to the first eRx.\n \n31.Indication functionality added to eRx Holding Queue\n ---------------------------------------------------------------------------\n When matching the VistA Drug the user will now be prompted to also enter\n the Indication. This functionality was only available in CPRS, Complete\n Orders from OERR [PSO LMOE FINISH] and Patient Prescription Processing\nPSO ERX VALIDATE PATIENT Action Modified\n [PSO LM BACKDOOR ORDERS] options and it is now being extended to the eRx\n Holding Queue Processing [PSO ERX QUEUE PROCESSING] option as well. \n If the patient record includes Indication, the user will now see the\n Indication shown on the Single eRx View/Display landing page.\n The Indication field will be displayed in the Single eRx View/Display\n screen as well as in the Drug Validation screen, where it can be edited.\n \n Note: Please, refer to the user documentation for more detailed \n information about this new functionality.\n \nPSO ERX VALIDATE PROVIDER Action Modified\n32.Added RRE and CRE error codes under CCR Filter\n ---------------------------------------------------------------------------\n The two error codes listed below have been added under CCR Filter. This\n will enable technicians to monitor and examine the RxChangeRequest/\n RxRenewalRequest sent either by the VA eRx hub software or by the outside\n prescribers.\n \n CRE RxChangeRequest Inbound Error \n RRE RxRenewalRequest Inbound Error\n \nPSO ERX VALIDATION MENU Menu Modified\n33.Patient DOB check on Edit and Accept Validation warning\n ---------------------------------------------------------------------------\n When editing or accepting validating the VistA patient, if there the DOB of\n the eRx Patient does not match the DOB of the VistA Patient, the warning \n below will be displayed:\n \n Editing:\n ***************************** WARNING(S) *****************************\n Patient DOB mismatch (eRx: 01/01/1950 | VistA: 06/16/1936)\n *************************************************************************\nPSO ERX VIEW AUDIT LOG Action Modified\n Would you like to use this patient? NO// \n \n Validating:\n ***************************** WARNING(S) *****************************\n Patient DOB mismatch (eRx: 01/01/1950 | VistA: 06/16/1936)\n *************************************************************************\n Would you like to mark this patient as VALIDATED?\n \n34.Memorize the VistA patient when eRx is selected (<SPACE BAR>)\n ---------------------------------------------------------------------------\nPSO ERX VIEW DRUG SUGGESTIONS Action New\n When the user selects an eRx that has a VistA Patient matched to it, the \n VistA patient will now be memorized as the last patient accessed by the\n user, therefore when the user type <SPACE BAR> at a VistA PATIENT prompt,\n it will automatically select the VistA Patient matched to the eRx.\n \n35.HFF for Un-Accept and Un-Remove will now ask for Future Fill Date\n ---------------------------------------------------------------------------\n When Un-Accepting or Un-Removing an eRx and selecting the hold code HFF \n (HOLD FOR FUTURE FILL) the software was not prompting the user to select\n a 'Future Fill Hold Date', which indicates when the eRx should be\nPSO ERX VIEW HISTORY LOG Action Modified\n automatically be un-held. This was causing the eRx to be unheld immediately\n after being put on hold. This will be fixed with this patch.\n \n36.IAS (Include All Statuses) action extended to Rx Medication Queue as well\n ---------------------------------------------------------------------------\n The IAS action that was only available at the eRx Single Patient Queue will\n now be available in the Rx Medication Queue as well. This action is used to\n indicate that all eRx statuses should be included in the list and it will\n behave as such for the Rx Medication Queue as well.\n \n\n
\n--------------------------------------------------------------------- \n^PS(58.4,1,0)="STANDARD ASAP DEFINITION"\n^PS(58.4,1,"VER",+1,0)="5.0"\n \nRoutines\n--------\nPSOASAP\nPSOASAP0 \nPSOASAP1\n \nPost-Install routine that adds the 5.0 Standard version to "VER" subfile\n(#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4).\n^PS(58.4,1,"VER",0)="^58.4001^n^n"\n \n--------------------------------------------------------------------------\nPOP-11120 SPMP 5.0: Add new Zero Report to View/Edit ASAP Definitions \nOption\n--------------------------------------------------------------------------\n \nDDs/Data\n---------\nno DD modifications but an additional entry at the VER multiple (58.4001) \nstored at the 1 subscript (for the Baseline or STANDARD definition) e.g.,\n^PS(58.4,1,"VER",+1,0)="4.2A"\n^PS(58.4,1,0)="STANDARD ASAP DEFINITION"\n^PS(58.4,1,"VER",0)="^58.4001^10^9"\n^PS(58.4,1,"VER",+1,0)="5.0Z"\n \nRoutines\n--------\nPSOASAP\nPSOASAP0 \nPSOASAP1\n \n \nPost-Install routine that adds the 5.0Z Zero Report version to "VER"\nsubfile (#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4).\n \n------------------------------------------------------------------------- \n POP-10847 View/Edit ASAP Definitions: Remove ability to edit Baseline\nversion\n-------------------------------------------------------------------------\n \nDDs\n------\nRoutines\nLOCKED? field (#58.4001, .07) - NEW field\n \nProtocol\n--------\nPSO SPMP3 MENU - MODIFIED\n \nRoutines\n--------\nPSOSPMA3 \nPSOSPMB3\n--------\nPSOSPML3\nPSOSPMU2\nPSOSPMU0\n \nPost-Install routine that populates the new field with 1 (YES).\n \n--------------------------------------------------------------------------\nPOP-10737 Modify Customization Indication Feature\n---------------------------------------------------------------------\n \nPSOASAP\nDDs\n---\nCOPIED FROM ASAP VERSION field (#58.4001, .06) - NEW field\n \nRoutines\n--------\nPSOSPMA3 \nPSOSPMB3\nPSOSPML3\nPSOSPMU0\nPSOASAP0 \nPSOSPMU2\nPSOSPMU3\n \n--------------------------------------------------------------------------\nPOP-10815 Export Batch Processing for 5.0 Baseline Version\nPOP-10708 4.2A Export Batch Processing\nPOP-10763 5.0Z Export Batch Processing\nPOP-10762 4.2B Export Batch Processing\nPOP-11260 4.2AZ Export Batch Processing\nPOP-01816 4.2BZ Export Batch Processing\nPSOASAP1\n--------------------------------------------------------------------------\n \n \nRoutines\n--------\nPSOASAP\nPSOASAP0\nPSOASAP1\nPSOASAP2\n \n \n--------------------------------------------------------------------------\nPOP-11763 Add display of "Copied From ASAP Version" to PSO SPMP ASAP \nDefinitions screen\n--------------------------------------------------------------------------\n \nDDs\n---\nCOPIED FROM ASAP VERSION field (#58.4001, .06) - NEW field\n \nList Template\nPOP-10707 4.2A: Add Baseline Standard Version to View/Edit ASAP\nPost-Install routine that adds the 4.2A Standard version to "VER" subfile\n--------------\nPSO SPMP VIEW ASAP DEFINITION\n \nRoutines\n--------\nPSOSPML3\n \n--------------------------------------------------------------------------\nPOP-11750 Add Ability to delete Custom ASAP Version Definition\n--------------------------------------------------------------------------\n(#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4).\n \nRoutines\n---------\nPSOSPMB3\nPSOSPMU3\n \n--------------------------------------------------------------------------\nRemove Copied (Custom) ASAP Definitions in Restore (Backout) Process\n--------------------------------------------------------------------------\nPSO77244\n \n \n--------------------------------------------------------------------------\nChange "Version" to "Ver" in PSO SPMP ASAP DEFINITIONS Screen Title\n-------------------------------------------------------------------\n The Screen Title in the View/Edit ASAP Definitions [PSO SPMP ASAP \n DEFINITIONS] option has been changed to display the word "Ver" instead of\n "Version" to accomodate long ASAP definition names, and to avoid \n truncating the ASAP definition name or the asterisk indicating the \n definition is a custom copied version.\n \n------------------------------------------------------------------------\n--------------------------------------------------------------------------\nEnvironment Check\n--------------------------------------------------------------------------\nAn environment check runs during the loading of this patch (prior to \ninstallation) to verify there are no custom versions of ASAP definitions \n4.2A, 4.2B, or 5.0 in the STANDARD sub-file (#58.4001) of the SPMP ASAP\nRECORD DEFINITION file (#58.4). If custom versions of any of these ASAP \ndefinitions are found, the installation is halted and the installer is \ninstructed to have the definitions removed or renamed prior to installing \nthe patch.\nPOP-10722 SPMP 4.2A: Add new Zero Report to View/Edit ASAP Definitions \nOption\n-----------------------------------------------------------------------\n \nDDs/Data\n---------\nDefinitions Option\nno DD modifications but an additional entry at the VER multiple (58.4001) \nstored at the 1 subscript (for the Baseline or STANDARD definition) e.g.,\n^PS(58.4,1,0)="STANDARD ASAP DEFINITION"\n^PS(58.4,1,"VER",0)="^58.4001^n^n"\n^PS(58.4,1,"VER",+1,0)="4.2AZ"\n \nRoutines\n--------\nPSOASAP\nPSOASAP0 \n-----------------------------------------------------------------------\nPSOASAP1\n \nPost-Install routine that adds the 4.2AZ Zero Report version to "VER"\nsubfile (#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4).\n \n---------------------------------------------------------------------\nPOP-10817 SPMP 4.2B: Add Baseline Standard Version to View/Edit ASAP \nDefinitions Option\n---------------------------------------------------------------------\n \n \nDDs/Data\n---------\nno DD modifications but an additional entry at the VER multiple (58.4001) \nstored at the 1 subscript (for the Baseline or STANDARD definition) e.g.,\n^PS(58.4,1,0)="STANDARD ASAP DEFINITION"\n^PS(58.4,1,"VER",0)="^58.4001^n^n"\n^PS(58.4,1,"VER",+1,0)="4.2B"\n \nRoutines\n--------\nDDs/Data\nPSOASAP\nPSOASAP0 \nPSOASAP1\n \nPost-Install routine that adds the 4.2B Standard version to "VER" subfile\n(#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4).\n \n----------------------------------------------------------------------\nPOP-11327 SPMP 4.2B: Add New Zero Report to View/Edit ASAP Definitions \nOption\n---------\n---------------------------------------------------------------------\n \nDDs/Data\n---------\nno DD modifications but an additional entry at the VER multiple (58.4001) \nstored at the 1 subscript (for the Baseline or STANDARD definition) e.g.,\n^PS(58.4,1,0)="STANDARD ASAP DEFINITION"\n^PS(58.4,1,"VER",0)="^58.4001^n^n"\n^PS(58.4,1,"VER",+1,0)="4.2BZ"\n \nno DD modifications but an additional entry at the VER multiple (58.4001) \nRoutines\n--------\nPSOASAP\nPSOASAP0 \nPSOASAP1\n \nPost-Install routine that adds the 4.2BZ Zero Report version to "VER"\nsubfile (#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4).\n \n---------------------------------------------------------------------\nstored at the 1 subscript (for the Baseline or STANDARD definition) e.g.,\nPOP-10814 Add 5.0 Baseline (Standard) version to the SPMP ASAP RECORD \nDEFINITION FILE (#58.4)\n---------------------------------------------------------------------\n \nDDs/Data\n---------\nno DD modifications but an additional entry at the VER multiple (58.4001) \nstored at the 1 subscript (for the Baseline or STANDARD definition) e.g.,\n^PS(58.4,1,0)="STANDARD ASAP DEFINITION"\n^PS(58.4,1,"VER",0)="^58.4001^9^8"\n\n
\nSee FORUM for patch description details.\n\n
\nThis patch, along with other patches, adds Pharmacogenomic (PGx) order\nchecking to medication orders entered through Inpatient Medications,\nOutpatient Pharmacy and Computerized Patient Record System (CPRS). A \npatient's genomic test results will be retrieved from the Health Data\nRepository (HDR), and along with the prospective drug(s) of a medication\norder is sent to the vendor to retrieve interactions between the patient's\ngenes and the prospective drug(s).\n\n
\n This is an emergency patch and should be installed as soon as possible.\n patients. When the software displays a profile it uses the field and\n cross-references to gather the prescriptions to be listed. If a corrupted\n node pointed to a prescription for a different patient, the wrong\n prescription would display on the profile. In some cases, a prescription\n may have been discontinued because a Date of Death or an Admission was\n entered for the patient with a corrupt cross-reference. This patch\n ensures that all bad entries in the sub-file and corresponding "A",\n cross-references are deleted. During this process, it generates a mail\n message to the installer for each Outpatient Site entry, listing those\n patients that may have had a prescription discontinued because a Date of\n \n Death or an Admission was entered for the patient with a corrupt cross-\n reference. These prescriptions must be manually reviewed and if\n appropriate reinstated. The patch installer should forward the mail\n message to the Pharmacy Application Coordinator, or the appropriate\n Outpatient Pharmacy Personnel, for their review and correction. It will\n send summary information to G.PL2 PATCH TRACKING group on FORUM so that\n counts of bad nodes by site can be collected. This patch will also scan\n through the PRESCRIPTION file (#52) using the "AD" cross-reference and\n will check if a corresponding entry exists in the PHARMACY PATIENT file\n (#55). The software will provide a count of missing entries in a separate\n The Upstate New York HealthCare System reported a problem concerning\n mail message that will be sent to G.PL2 PATCH TRACKING on FORUM for their\n review.\n \n We recommend re-indexing the "B" cross-reference of the PHARMACY\n PATIENT file (#55), during non-peak hours or when the number of pharmacy\n users on the system is at a minimum any time after completion of this\n job.\n \n A subsequent patch will be released to provide additional safeguards in\n the event that the cross-reference gets corrupted in the future.\n outpatient pharmacy profiles containing prescriptions for patients other\n than the patient selected. The problem happened as a result of corrupted\n data in the PRESCRIPTION PROFILE sub-file (#55.03) of the PHARMACY\n PATIENT file (#55). This field links the PHARMACY PATIENT file (#55) to\n the PRESCRIPTION file (#52). The link to the PRESCRIPTION file (#52) and\n the "A", cross-reference on this sub-file were corrupted for some\n\n
\nProblem: Prescriptions can be edited from mail to window and then released\nwhile the prescription still has an active Consolidated Mail Outpatient\nPharmacy (CMOP) status. Those statuses are Transmitted, Dispensed, and\nRetransmitted.\n \nResolution:\n \nThe internal code has been corrected to block the facilities from\nreleasing prescriptions that have an active CMOP status.\n\n
\n1) The Pharmacy Ordering Enhancements (POE) project provides enhancements\nInpatient Medications and Outpatient Pharmacy applications. This project\ndirectly supports Computerized Patient Record System (CPRS), which is a\nkey component of Veterans Health Administration's (VHA) plan to expand\nsupport for clinical operations. Additionally, order checks will be\nprovided for medication orders for which a dispense drug has not been\nselected during the CPRS order entry process. It is also intended as a way\nto help meet the goal outlined in Objective 8, Action 1 in the\nPrescription for Change, which outlines the need to coordinate\nnational/Veterans Integrated Service Network (VISN) formularies and share\ndrug treatment guideline information. This project will promote system-\nto Pharmacy Data Management (PDM) V. 1.0, Inpatient Medications\nwide sharing of drug reviews and treatment guidelines thereby enhancing\npatient safety.\n \nThis project consists of four patches that work together to accomplish\nthese goals listed in order of install:\n \n PSO*7*46\n OR*3*94\n PSS*1*38\n PSJ*5*50\nV. 5.0, Outpatient Pharmacy V. 7.0, and Order Entry/Results Reporting\n \n 2) This patch corrects a problem as reported in CON-0300-11347.\nWhen reinstating a Prescription an order alert was displayed for a\nduplicate drug. The alert was occurring incorrectly for the Prescription\nthat was being reinstated.\n \n 3) As reported in NYH-0300-12247 and BIL-1100-30086 the NSC/SC prompt is\nnot asked consistently between Outpatient Pharmacy and Computerized\nPatient Record System (CPRS) packages. This patch provided an enhanced\ninterface for both packages to use when placing orders. \n(OE/RR) V. 3.0 medication ordering dialogues to eliminate redundant entry\n \n 4) As reported in SAG-0500-41497 when renewing prescription request from\nCPRS the screen was not displaying correctly. This patch corrects this\nproblem.\n \n 5) As reported in AMA-0900-71796 when renewing prescriptions that had\na cosigner tied to the provider and the cosigning provider changed the\ncosigner was not being updated to show the new cosigning provider.\n \n 6) As reported in NYH-0900-10553 cost in the PRESCRIPTION file (#52) for\nof drug information during medication order entry, provide a more\nthe drug would not allow a cost higher than 999 with 4 decimals. This\npatch will allow cost to be entered for all fills to be 9999 with 4\ndecimals.\n \n \nconsistent medication order entry process, provide expanded order\nchecking, display documented drug formulary statuses and corresponding\nrestriction/guidelines to the provider and pharmacist at the time of order\nentry, and improve the process of medication order transfer between\n\n
\n \nwhen finishing pending orders.\n \n3. This patch runs a post-install routine to look for pre-POE pending orders\nwithout dispense drugs and remove data stored on the wrong node.\n1. When entering new outpatients into the Pharmacy Patient file (#55), the\npatient's prescription status is a required data element. When entering\nthis data element into the Pharmacy Patient file (#55) eligibility and\ndisabilities will display to help the pharmacy user answer this prompt.\n \nThis patch also corrects a typo.\n \n2. This patch corrects a problem where a missing dosage check did not work\n\n
\nThis patch is an enhancement to the Outpatient Pharmacy routine that\ngathers and returns patient and prescription information for the Hepatitis\nC Extract project. Prior to this patch, data was returned without\nintegrated site consideration. With the release of this patch, a check\nwill now be done on original fill prescriptions. If the original fill\nprescription information has been moved to another site, that finding will\nnot be included in the extract.\n\n
\nA problem has been found where it is possible for an Outpatient Pharmacy\n \nAs part of the Pharmacy Ordering Enhancements (POE) project (patch\nPSO*7*46 for Outpatient Pharmacy) a change will be made to assign Routine\nas the priority to an order received from CPRS that does not have a\npriority.\n \nWhat this patch will do is run a Post-Install routine that will look for\nPending Outpatient Orders that do not have a Priority assigned. A list of \nPatients with these orders will be sent in a mail message to the person\ninstalling the patch. This mail message should then be forwarded by the\norder to be entered through Computerized Patient Record System (CPRS), and\npatch installer to the Pharmacy Application Coordinator, or the\nappropriate Outpatient Pharmacy Personnel, for their review.\nthe priority of the order to be deleted in CPRS, before the order is sent\nto Outpatient Pharmacy. When finishing orders in Outpatient Pharmacy using\nthe Complete Orders from OERR [PSO LMOE FINISH] option, Priority is one of\nthe sort selections. It has been reported that orders were not being\nfinished because orders had been sent without a priority, and all\nfinishing in Outpatient Pharmacy was done by priority, and not by any\nother means of sorting.\n\n
\n1. This patch corrects an undefined error that could occur when trying to \ndefaulting for the second order. \n \n4. When speed renewing POE orders the SIG does not display. \n \n5. Site reported not being able to edit the verb when finishing pending\nrenewals for phase 2 of POE. The site was instructed to select the field for\ndosage and then type ^VERB to jump to the Verb field. In doing this you\nare prompted twice for schedule, duration and conjunction. \ndisplay Special Instructions (SIG) for a prescription entered before\nPSO*7*46. \n \n2. Added check for missing SIG before filing a renewal. \n \n3. When speed renewing through Outpatient Pharmacy and the first order is a\npre-POE order with a possible dosage and the second order is a pre-POE order\nwith a local possible dosage, the quantity from the first order is\n\n
\nThis patch corrects the finding as reported by the QA review. Most if not\n \n PSOARCLT\n PSOARCTG\n PSOARX\n PSOB\n PSOBGMG1\n PSOBGMG2\n PSOBSET\n PSOCPC\n PSOCPTRI\nall changes will be transparent to the user.\n PSOCST11\n PSOCST2\n PSOCST4\n PSODELI\n PSODGDGI\n PSOHLEXP\n PSOHLSG1\n PSOHLSN1\n PSOHLUP1\n PSOLSET\n \n PSOORCPY\n PSOORNW2\n PSOR52\n PSOSTART\n PSOSULB1\n PSOSUP\n PSOSURST\n PSOSUTL\n \nAlso added NDF file structure changes to routines PSOHLSN1, PSOHLSG1, and\n Removal of nonstandard reference to ^DPT(.\nPSOHLSN.\n Removal of naked global references at the start of lines.\n Added timeouts to locking global.\n Removal of nonstandard reference to ^%ZIS(1, and ^%ZIS(2,.\n Write commands in data dictionaries changed to EN^DDIOL.\n Variable DT sets were changed to supported $$DT^XLFDT.\n\n
\n When Pharmacy is finishing a Renewal entered through Computerized Patient\n Record System (CPRS), for Consolidated Mail Outpatient Pharmacy (CMOP)\n sites, if the Routing, MAIL/WINDOW field (#11) of the PRESCRIPTION file\n (#52) is edited from "Mail" to "Window" when having the LOGIN DATE field\n (#21) a date prior to the current date and the FILL DATE field (#22) of\n the PRESCRIPTION file (#52) set for today's date with the intention of\n dispensing the prescription locally, there is a possibility of such a\n prescription getting suspended for CMOP. This patch fixes this problem.\n\n
\n 1) This patch makes the DAYS SUPPLY field (#.041) of the PARTIAL DATE\n possibility of viewing prescriptions belonging to other patients. This\n patch fixes this problem.\n \n 3) When deleting a device from the DEVICE file (#3.5), using FileMan and\n requesting the software either to delete all pointers or changing its\n pointers to point to a different device, it was found to error out at\n times. During the process of re-pointing the device, FileMan would\n encounter an orphaned multiple (#59.30001). This multiple may have been\n used by Outpatient Pharmacy at some time, but they are no longer needed.\n This patch removes this multiple.\n multiple (#52.2) of the PRESCRIPTION file (#52), a required field as\n requested by the NOIS ISH-0401-40089. The Data Dictionary is not changed\n here. The fix is made in the routine PSORXPA1.\n \n 2) When using the Status of Patient's Order [PSO BINGO STATUS] option,\n or using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]\n option, and selecting the OTH (Other OP Actions) hidden action, and then\n selecting the DO (Display Orders' Statuses) option, there is a\n\n
\n This patch adds the Free Text Dosage Report [PSO DOSAGE REPORT] option,\n Dosages selectable instead of requiring it to be typed in, during the\n medication order entry process.\n as an addition to the Output Reports [PSO OUTPUTS] menu option. It\n provides a list of drugs for those prescriptions where the DOSAGE ORDERED\n field (#.01) of the MEDICATION INSTRUCTION sub-file (#52.0113) of the\n PRESCRIPTION file (#52), has a free text entry or a dosage that results\n in the calculation of the number of tablets. This report is designed to\n help in the identification of all such entries so that the sites can\n determine if these dosages should be added to the LOCAL POSSIBLE DOSAGE\n sub-file (#50.0904) of the DRUG file (#50), making the Local Possible\n\n
\nThis patch reflects changes made to copay charges by Public Law 106-117, \npriority groups 2-6. Provisions are included to automatically increase \nthe copayment and the cap amount under certain conditions. \n \nEffective on January 1, 2002, a medication is exempt from copay charges \nif it is used to treat the following conditions:\n \n Vietnam-era herbicide (Agent Orange) exposure\n Radiation exposure\n Exposure to environmental contaminants during Persian Gulf War Service\n Military Sexual Trauma \nThe Veterans Millennium Health Care and Benefits Act. Public Law 106-117 \n Cancer of the Head and/or Neck \n \nThe Outpatient Pharmacy patch PSO*7*71 and Consolidated Mail Outpatient\nPharmacy (CMOP) patch PSX*2*35 must be installed and implemented by\nfacilities no later than December 31, 2001. On January 1, 2002, the new\nmedication copay exemptions provided by patch PSO*7*71 will go into\neffect. Changes to increase the amount of medication copay and to\nestablish the annual copay cap will go into effect when the law is\napproved and signed.\n \nwill not go into effect until early 2002. The exact effective date is not \n \nA post-installation routine is included in patch PSO*7*71 to review \nprescriptions entered over the last year and to populate, whenever \npossible, the new SERVICE CONNECTED field (#116) of the PRESCRIPTION\nfile (#52). This routine queues a background task to look at all\nprescriptions entered over the last year and to attempt to populate the\nnew SERVICE CONNECTED field (#116) of the PRESCRIPTION file (#52) based on\nthe prescription data. If the COPAY TRANSACTION TYPE field (#105) of the\nPRESCRIPTION file (#52) is set to "2," this indicates that the Service\nConnected question was asked for this prescription, and the response was\nknown at this time. Prior to the changes that will be implemented with \n"NO." In these cases, the software will set the new SERVICE CONNECTED\nfield (#116) to "NO." If the COPAY TRANSACTION TYPE field (#105) of the\nPRESCRIPTION file (#52) is null, and the drug is not marked as a supply or\nas an investigational drug, and the Rx Patient Status of the prescription\ncontains "50," and either the "<" character or the words "LESS THAN" (for\n'SC LESS THAN 50%'), and the COPAY INCOME EXEMPTION STATUS field (#.04) of\nthe BILLING PATIENT file (#354) is set to "NON-EXEMPT, " then the software\nwill set the new SERVICE CONNECTED field to "YES."\n \nWhen the job is complete, a mail message will be sent to the person who \nPublic Law 106-117, certain veterans paid a $2 copayment for each 30-day \ninstalled the patch.\n \n \nComplete information for all the changes included in this patch can be \nfound in the Outpatient Medication Copay Release Notes document. In \naddition to the Release Notes, there are changes to the Outpatient \nPharmacy Technical Manual and the Outpatient Pharmacy User Manual.\n \n \nSites may retrieve documentation in one of the following ways:\nor less supply of medication furnished for the outpatient treatment of a \n \n(1) The preferred method is to FTP the files from\n download.vista.domain.ext, which will transmit the files from the\n first available FTP server.\n \n(2) Sites may also elect to retrieve documentation directly from a\n specific server as follows:\n \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\nnonservice-connected disability or condition. With Public Law 106-117, \n Salt Lake City ftp.fo-slc.domain.ext\n \n \nThe documentation distribution includes: \n \n FILE NAMES DESCRIPTION\n \n OP_Med_Copay_RN.pdf Release Notes\n OP_7_0_P71_UM_CP.pdf User Manual (change pages)\n OP_7_0_P71_TM_CP.pdf Technical Manual (change pages)\nthe copayment amount will increase from $2 to $7. An annual copayment cap \n OP_7_0_UM_R1101.pdf User Manual (updated)\n OP_7_0_TM_R1101.pdf Technical Manual (updated)\n \n \n(3) Documentation can also be retrieved from VISTA Document Library (VDL)\n on the VA Intranet at the following address,\n http://vista.domain.ext/vdl.\nof $840 will be set through calendar year 2002 for veterans in enrollment \n\n
\nProblem: The testing for duplicate drugs is bringing back false \nduplicates from the Consolidated Mail Outpatient Pharmacy (CMOP) module \nwhen the PSO LM BACKDOOR ORDERS option is used.\n \nResolution: The code has been corrected by clearing a variable prior to \ntesting the prescription.\n\n
\n 1) When the PP Pull Rx (OP) protocol (hidden action) is used in the\n prescription).\n \n 2) When entering a new prescription through backdoor pharmacy and if the\n prescription is put on hold then the label LABEL QUEUE/CHANGE\n PRINTER/SUSPEND or '^' to bypass Q// prompt is displayed. If the new\n prescription is the only order in the session then no label is required\n therefore, this prompt should not be displayed. This patch fixes this\n problem.\n \n 3) In the API's OCL^PSOORRL and OEL^PSOORRL, provided by Outpatient\n backdoor pharmacy to fill a suspended prescription early, it sometimes\n Pharmacy V. 7.0, there is a possibility of an undefined error occurring\n when the "SIG" node of the PRESCRIPTION file (#52) for the prescription\n in process is missing. This patch corrects this problem.\n errors out. This is due to a bad "B" cross-reference entry for that\n prescription in the RX SUSPENSE file (#52.5). This patch will ensure that\n the corresponding entries of such a prescription in the RX SUSPENSE file\n (#52.5) are complete when building the patient medical profile. If\n the entries are incomplete this patch will clean up the bad "B"\n cross-reference entry in the RX SUSPENSE file (#52.5) and change the\n STATUS field (#100) of the PRESCRIPTION file (#52) to 0 (an active\n\n
\n \ncomplaints from patients about their full Social Security Number (SSN)\nprinting on their prescription reorder documents. Currently the SSN at\nthe top of the refill document shows the last 6 digits, however the full SSN\nshows next to the patient's name on the last page, just above the\nNARRATIVE REFILLABLE RX document. This patch will change all\ninstances of the patient's SSN on the reorder documents to display only the\nlast 6 digits. \n \n \n \nThis patch addresses the following concerns:\n \n1. When entering an outpatient pharmacy prescription a schedule \nis required to complete the order. If the user should enter a question\nmark at the schedule field prompt to list the available choices, a list is\nnot displayed as expected. This patch corrects this problem.\n \n2. Central Texas Veterans Health Care System has received multiple\n\n
\n When editing a prescription through the pharmacy backdoor, if the\n Prescriptions [PSO EXPIRE PRESCRIPTIONS] and the Manual Auto Expire Rxs\n [PSO MANUAL AUTO EXPIRE] options both use the "AG" cross-reference to\n flag prescriptions past the expiration date as expired and they do\n not flag those prescriptions that had a missing "AG" cross-reference\n entry. Hence, the expired prescriptions show as active, especially when\n using the Orders Tab protocol from the Computerized Patient Record System\n (CPRS) package. This patch ensures that the "AG" cross-reference is reset\n only when the expiration date changes.\n \n The Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] and the Manual Auto\n following fields are edited: QTY field (#7), DAYS SUPPLY field (#8) or #\n Expire Rxs [PSO MANUAL AUTO EXPIRE] options are patched to have an\n additional check to ensure that the expiration date subscript in the\n "AG" cross-reference is equal to the EXPIRATION DATE field (#26) of the\n PRESCRIPTION file (#52), and to flag those prescriptions that have\n expired in Outpatient Pharmacy but show as active in the CPRS Orders Tab\n as expired.\n \n The Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option flags\n prescriptions that have passed the expire date as expired and sends an\n HL7 message across to CPRS to flag those prescriptions as expired.\n OF REFILLS field (#9), of the PRESCRIPTION file (#52), the software\n Currently, this functionality not only sends the expire message for\n expired prescriptions but also for discontinued prescriptions, and as a\n result in CPRS the discontinued prescriptions are flagged as expired,\n which is incorrect. This patch will ensure that only expired\n prescriptions are sent across to CPRS to be flagged as expired.\n \n Note: There is an optional site selectable post-install background job\n included in this patch. This job will make sure that the "AG"\n cross-reference of the EXPIRATION DATE field (#26) of the PRESCRIPTION\n file (#52) is properly set, starting from the date Outpatient Pharmacy V.\n recalculates the EXPIRATION DATE field (#26) of the PRESCRIPTION file\n 7.0 was installed. It will also reset the statuses of all those\n discontinued prescriptions which were flagged as expired in CPRS by the\n Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option back to\n discontinued statuses. At the completion of this job, a MailMan message\n with the subject "PATCH PSO*7*73 - 'AG' Cross-reference Cleanup\n Information", will be sent to the installer notifying the time of\n completion. The date/time to queue this job is site selectable and can be\n queued to run during the installation of the patch or at another time by\n calling the entry point BEG^PSOPOST from programmer mode. Also the site\n could use this entry point at any time to re-start the cleanup process in\n (#52) and also kills the corresponding "AG" cross-reference entry of the\n case the job was interrupted for any reason.\n \n For sites experiencing the problem reported above, i.e., prescriptions\n past the expiration date appearing as active, it is recommended that\n they also run the Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] option\n any time after the completion of the Post-Install run of this patch.\n PRESCRIPTION file (#52). In the case when the expiration date remains the\n same after the edit process, it does not reset the "AG" cross-reference\n entry and therefore the link to the PRESCRIPTION file (#52) for that\n prescription from the "AG" cross-reference is lost. The Expire\n\n
\n The routine PSOORDRG contains an Application Programmer Interface\n patch by itself will produce no changes, visible or otherwise. The\n original NOIS submitted to CPRS is DUR-0801-32713.\n \n \n Associated NOISs:\n =================\n DUR-0801-32713\n (API), IA #2190, used by the Computerized Patient Record System\n (CPRS). This API requires modification to accommodate changes to the\n incoming data passed in by CPRS. The intended effect of this change is to\n improve CPRS order checking functionality, specifically, to help CPRS\n distinguish between Inpatient orders and Outpatient orders when\n performing order checks. The changes described will not be implemented\n until OR*3*123 and PSJ*5*56 are also installed. However, this patch does\n not formally require OR*3*123 or PSJ*5*56, and installation of this\n\n
\n \nSITE file (#59) parameter 'BARCODES ON ACTION PROFILES' for any\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time.\n \n 3. If the estimated number of prescription fills that will be billed as\n part of this clean up is extremely high, you may want to disable\n journaling for Integrated Billing and Accounts Receivable globals ^IB\n and ^PRCA.\noutpatient pharmacy site is set to "NO" or is null, all copay eligible\n \n 4. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 5. From this menu, you may select to use the following options:\n (when prompted for INSTALL NAME, enter PSO*7.0*93)\n \n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\nprescription fills released by CMOP for that outpatient pharmacy site,\n \n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch (routines,\n DDs, templates, etc.).\n \n c. Verify Checksums in Transport Global - this option will ensure\n the integrity of the routines that are in the transport global.\n \n 6. Use the Install Package(s) option and select the package PSO*7.0*93.\nafter the installation of patch PSX*2*35, would not have been billed. This\n \n 7. When Prompted "Want KIDS to INHIBIT LOGONs during the install?\n YES//" respond NO.\n \n 8. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//" respond NO.\n \n 9. When Prompted "Queue copay clean-up Job to run Date/Time:" respond\n with the date/time to queue the cleanup background job or "NOW".\n \npatch identifies all such prescriptions and reprocesses them so that the\n 10. If Routines were unmapped as part of step 2, they should be returned\n to completion.\n \n 11. If journaling was disabled for globals ^IB and ^PRCA in step 3, it\n should be re-enabled upon completion of the post-installation job.\n \n \n \n Example Installation:\n =====================\nappropriate copay charges are generated.\nChecking Install for Package PSO*7.0*93\n \nInstall Questions for PSO*7.0*93\n \n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n \n \n Install Started for PSO*7.0*93 :\n Jan 18, 2002@14:39:49\n \nBuild Distribution Date: Jan 18, 2002\n \n Installing Routines:\n Jan 18, 2002@14:39:49\n \n Running Post-Install Routine: ^PSOCPIBF\nThe background job to clean up unbilled, released CMOP prescription fills\n \nmust\nbe queued to run and complete before 02/01/2002 when tracking for the\nannual copay cap begins.\n \nIf no start date/time is entered when prompted, the background job will be\nqueued to run NOW.\n \nCMOP patch PSX*2*35 was first installed at your facility on SEP 15,\n2001@14:15:4\n Resolution: This patch will identify all copay eligible released CMOP\n \nThe Outpatient Site (File #59) parameter, 'BARCODES ON ACTION PROFILES'\nfor one or more outpatient sites is either not defined or set to 'No'.\nAll copay eligible, released CMOP prescription fills from those outpatient\nsites would not have been billed since the installation of PSX*2*35.\n \nNOTE: If the estimated number of CMOP prescriptions involved is high\nbased\non when the patch was first installed and the number of outpatient sites\ninvolved, you may want to disable journaling for Integrated Billing and\nprescription fills that were not billed since the installation of patch\nAccounts Receivable globals ^IB and ^PRCA while the clean up job\nis running.\n \nWhen the background job is complete, a MailMan message will be sent to the\ninstaller indicating how many copay eligible CMOP prescription fills were\nsuccessfully billed.\n \nBackground job must be queued to start by Jan 30, 2002 or before.\n \nAt the following prompt, enter a starting date/time after JAN 18,\n \nPSX*2*35 and reprocess them so that appropriate copay charges are\n2002@14:39:49\nand before Jan 31, 2002 or enter NOW to queue the job immediately.\nIf this prompting is during patch installation, you will not see what you\ntype.\n \n PSO*7.0*93\n--------------------------------------------------------------------------\n------\nQueue copay clean-up Job to run Date/Time: (JAN 18, 2002@10:00) ??\nQueue copay clean-up Job to run Date/Time: (JAN 18, 2002@15:00)\ngenerated. A MailMan message with a Subject of 'Outpatient Pharmacy\n \nTask will be queued to run JAN 18, 2002@15:00 Is that correct? :\n \nQueuing background job to reprocess unbilled copay CMOP Prescription\nfills...\n \nTask Queued !\n \n \n Updating Routine file...\nCopay Clean-up' will be sent to the patch installer and holders of the PSO\n \n Updating KIDS files...\n \n PSO*7.0*93 Installed.\n Jan 18, 2002@14:40:20\n \n Install Message sent #41853\n--------------------------------------------------------------------------\n------\n [------------------------------------------------------------]\nCOPAY key documenting the number of CMOP prescription fills that were\n 100% | 25 50 75 |\nComplete [------------------------------------------------------------]\n \n \n \nInstall Completed\nsuccessfully billed.\n \n \nThis patch will look at all CMOP prescription fills released since patch\nPSX*2*35 was installed at your facility. If the prescription is copay\neligible and no charge has been generated, the fill will be reprocessed.\nThis is an EMERGENCY patch and must be installed within 24 hours.\nWhen determining whether a copy charge was missed for a CMOP prescription\ndone after the release of patch PSX*2*35, we check the patient's current\ncopay status. If the patient's status changed from "no copay" to "copay"\nsince the installation of patch PSX*2*35 at the site, it is possible that\nthe patient could be billed for prescription fills that were not marked as\ncopay at the time they were originally released.\n \n \nNote: This clean up is done in a post-install background job. It MUST be\nqueued to run and complete before 02/01/2002 as tracking for the annual\n \ncopay cap goes into effect then. If the background job has not been queued\nto run by January 30, 2002 or if the background job has not completed by\nJanuary 31, 2002 @ 2359, the MailMan message generated will indicate that\nthe background job was stopped before completing the clean up.\n \nWhen queuing the background job, the date that patch PSX*2*35 was first\ninstalled at your facility will be displayed along with information as to\nwhether any OUTPATIENT SITE file (#59) has the parameter 'BARCODES ON\nACTION PROFILES' set to null or "NO". If so, and the estimated number of\nCMOP prescription fills released during that time frame is high, you may\nCMOP patch PSX*2*39 is required before the installation of this patch.\nwant to consider disabling journaling on the Integrated Billing and\nAccounts Receivable globals ^IB and ^PRCA before starting the background\njob.\n \n \n \n Associated NOISs:\n =================\n CHS-0102-40707\n ERI-0102-21090\n \n MAC-0102-60932\n BRX-0102-11833\n \n Test Sites:\n ===========\n Erie, PA\n Prescott, AZ\n Oklahoma City, OK\n Chicago HCS, IL\n Martinez, CA\n \n Chicago Hines, IL\n \n Routine Summary:\n ================\n The second line now reads as follows:\n \n <TAB>;;7.0;OUTPATIENT PHARMACY;**[patch list]**;DEC 1997\n \n CHECK^XTSUMBLD results:\n \n Problem: The release of the Consolidated Mail Outpatient Pharmacy\n Routine Before Patch After Patch Patch List\n =============================================================\n PSOCPIBC N/A 13213614 93\n PSOCPIBF N/A 18167555 93\n \n \n Installation Instructions:\n ==========================\n Installation should take no longer than 5 minutes. Please do not queue\n the job of installing this patch. There is a post-install background\n(CMOP) patch PSX*2*35 introduced a potential problem. If the OUTPATIENT\n job that will prompt for a date/time to run the clean up. You MUST\n respond with a date and time or NOW to queue the job. You will not\n be able to see what you are answering for the prompt, but will be given\n an opportunity to see what was entered before the clean up job queues.\n This post-install job can be run again at a later time by calling the\n entry point ^PSOCPIBF from programmer mode.\n \n An example of the install process is included here under the title\n "Example Installation". This must be run and finished before 02/01/02.\n \n\n
\n \n4. Removed commented out code. Routine: PSOBKDED, PSOORNEW. Also in the routine PSOORNEW, fixed an undefined error. NOIS: HUN-0298-22095\n \n5. Added Prescription Delivery to Patient Information screen. Routine: PSOORUT2\n \n6. Added timed lock to globals. Routine: PSOPRVW, PSONEW\n \n7. Newed PSODRUG variable in routine PSOCAN\n \n8. In the supported reference PSOORDER which returns prescription data, the external value of the Rx Patient Status was added. Added $G around global reference to prevent a possible undefined error. Routine: PSOORDER.\n \n1. Second line of routine has incorrect package release month and year. Second line of all routine should read as follows prior to any patches being applied: <tab>;;7.0UTPATIENT PHARMACY;;DEC 1997\n9. Changed a $Select statement to make it consistent with other displays when showing method of pick up. Routine: PSOBGMG3\n \n10. Added additional data validation checks for prescription being renewed.\nRoutine: PSOORNE5, PSORENW, PSORENW0, PSORENW4\n \n11. As determined by the Programming Conventions and Standards, no line can\nstart with a naked global reference. Routines: PSORXPA1, PSORXRP1.\n \n12. When requesting a reprint of a prescription label and the prescription\nwas entered through CPRS there's the possibility that the SIG will not\nRoutines: PSOCMOPB, PSOCPDUP, PSODRDUP, PSOLMRN, PSONGR, and PSORDS\ndisplay to the screen. Routine: PSORXRP2\n \n13. Added code to removed date an Rx was canceled when renewed.\nRoutine: PSORN52\n \n14. Fixed problem of CMOP barcoded refills from being printed locally.\n \n15. Fixed duplicate active drug problem.\n \n16. Along with PSO*7*7, will now show Provider Instruction enter through\n \nCPRS in the Pharmacy options.\n \n17. Added # of refills prompt for speed renewing.\n \n18. Added a PSNDF reference change to comply with new file structure.\n2. Added a 'Press to Continue' prompt for the Order Summary list.\n NOIS: WNY-0398-11868. Routine: PSOORNE1\n \n3. Added check for on the fly conversion when using the Batch Barcode Refill/Renew option. Routine: PSOBBC. NOIS: CTX-0398-70637\n \n\n
\n 1) When finishing pending orders using the Complete Orders from OERR [PSO\n ORDERS file (#52.41) is missing. This patch corrects these problems.\n \n 2) When finishing pending orders through the backdoor or using the\n Complete Orders from OERR [PSO LMOE FINISH] option, if multiple orders\n are selected, the BY Bypass ListMan action goes back to the patient\n profile instead of going to the next order in the selection list. This\n patch fixes this problem.\n LMOE FINISH] option, if PATIENT is selected for the sort prompt "Select\n By:", and ALL is selected for the prompt "All Patients or Single\n Patient:", it was found that the software does not show the medication\n profile of every patient who has pending orders. The problem is that if\n the software encounters a renewal and if that order is skipped by the\n user without completing it, then the process will quit instead of\n continuing with the rest of the patients. Also there is a possibility of\n getting an undefined error if the zero node of the PENDING OUTPATIENT\n\n
\n1. When using the Free Text Dosage Report [PSO DOSAGE REPORT] option, \n[PSO RX] option when it puts you back to the VMS prompt. This patch \ncorrects this problem.\n \n3. When multiple edits are done while finishing a pending order, there is \na possibility of an undefined variable error occurring. This patch fixes\nthis problem.\n \n4. When using the Rx Verification by Clerk [PSO VR] option, for pre POE \norders that do not have a SIG, there is a possibility of the patient \ninstructions not getting appended to the constructed SIG. This patch\nthere is a possibility of a "string too long" error occurring when the \ncorrects this problem.\ndate range selected is for a long period. This patch corrects this \nproblem.\n \n2. With programmer access only, most Outpatient Pharmacy options can be \nexecuted by entering the option name at the XUP routine's, "Select OPTION \nNAME:" prompt. On quitting from these options the software takes you back \nto the MUMPS programmer prompt except when using the Rx (Prescriptions) \n\n
\nThis patch addresses the following concerns: \n \n1. When entering an outpatient pharmacy prescription a schedule is required\nto complete the order. If the user enters a question mark at the "Schedule:"\nprompt to list the available choices, a list is not displayed as expected.\nThis patch corrects this problem. \n \n2. This patch corrects a possible undefined error when entering new\nOutpatient Backdoor Pharmacy orders. \n\n
\n1. There is the potential for an undefined error to occur when renewing \nIn addition to correcting the problem, this install will loop through the \nentire PRESCRIPTION file (#52) and look for the ^PSRX(DA,"SIG") node\nthat has only an up-arrow (^), is a renewal, and has a pointer to the prescription\nthat was renewed and then copy the SIG to the prescription with the missing SIG. \nThis looping that is a post-install routine could take up to an hour or more. \nIt is recommended that this install be queued to a printer so a terminal is\navailable during the install. \n \n2. With the release of the Pharmacy Ordering Enhancement (POE) patch the List\nManager action, Other OP Actions [PSO LM HIDDEN OTHER] was mistakenly\nprescriptions that were entered using the Outpatient Pharmacy v.7.0\nRemoved from the List Manager Protocol, Outpatient Pharmacy Hidden Actions #2\n[PSO HIDDEN ACTIONS #2]. This patch restores Other OP Actions [PSO LM HIDDEN\nOTHER] protocol as an item to the Outpatient Pharmacy Hidden Actions #2 [PSO \nHIDDEN ACTIONS #2] protocol. \npackage prior to installing the Pharmacy Ordering Enhancement (POE)\npatch. After POE has been installed and renewing these prescriptions from \nthe PRESCRIPTION file (#52), the SIG field (#10) could be blank which causes\nan undefined error when the software attempts to display these prescriptions to\nthe screen. This error does not affect prescriptions entered using Computerized\nPatient Record System (CPRS). \n \n\n
\nThis patch addresses the following concerns:\n \nWhen running the following options: Nightly Rx Cost Compile [PSO COSTDAY \nNIGHTJOB], Monthly Rx Cost Compilation [PSO COSTMONTH], and Daily Rx Cost [PSO\nCOSTDAY], a possible undefined error could happen if there is a bad \ncross-reference in the REFILL DATE sub-file (#52.1) on the REFILL DATE field\n(#.01). This patch corrects this potential error. \n \n\n
\n1. When renewing a prescription and editing it before finishing the order,\nproblem.\n \n3. Prior to the Pharmacy Ordering Enhancements patches, the Dispense \nDrug of a prescription could be edited and not create a new order. This\nwould happen if the new Dispense Drug was matched to the same Pharmacy\nOrderable Item as the old Dispense Drug. When this occurred, the drug was\nnot updated in Computerized Record Patient System (CPRS). If the order is\nthen renewed through CPRS after the install of the Pharmacy Ordering \nEnhancements patches, and if this order can have Possible Dosages, it is \npossible that Dosages are automatically assigned to the order by CPRS \nand if the nature of order was marked as "Verbal", there is a possibility\nbased on the original order information. When the Pending Renewal is \ndisplayed in Pharmacy, the Dispense Drug is always replaced with the \ncurrent Dispense Drug of the order. This could lead to the Possible \nDosages not matching the Dispense Drug on the Pending Renewal.\n \nTo fix this problem, when the Renewal is done in CPRS, Pharmacy will \ncheck the Drug from the PRESCRIPTION file (#52) against the Drug in the\nORDER file (#100), and if it is different, the order will be\nNon-Renewable through CPRS.\n \nof the renewed order not triggering an alert to the provider for his \nThis functionality of this patch will not be seen until both this patch \n(PSO*7*96) and the CPRS patch (OR*3*134) are installed. It will not cause\nany problems if the Outpatient Pharmacy patch is installed without the \nCPRS patch, it's just that the functionality will not be seen until both\nare installed.\n \n4. When Renewing prescriptions that were entered prior to the \ninstallation of the Pharmacy Ordering Enhancements patches, it is\npossible that the Verb from one Renewal is carried over to the next\nRenewal. This patch will fix this problem.\nsignature. This patch fixes this problem.\n \n5. A problem has been reported when finishing renewals entered through \nCPRS, and when processing renewals through Outpatient Pharmacy. The\nInstructions field sometimes displays with incorrect Instructions. This \nis a result of a data problem that occurred prior to the Pharmacy\nOrdering Enhancements project, and has since been fixed. But there is no\nway to clean up any of the invalid data, so these invalid Instructions\nstill appear on the pending renewal screen. Since the Sig now shows on\nthe pending renewal screen, the software no longer needs to show the\nInstructions, so the Instructions will now be removed from the display.\n \n2. When finishing a renewal entered through Computerized Patient Record \nSystem (CPRS) in Outpatient Pharmacy and answering YES to the prompt "Do\nyou want to enter a Progress Note? No//", the software does not present\nthe pharmacist with the progress notes template. This patch fixes this\n\n
\nA problem has been reported of a status mismatch between Outpatient \nPharmacy orders and the corresponding order in Computerized Patient \nRecord System (CPRS).The specific problem would be that an order would be \nDiscontinued or Expired in Pharmacy, but Active in CPRS. This patch will \nidentify those orders, and update the CPRS order with the correct status.\n\n
\n1. With the release of the Pharmacy Ordering Enhancement patch (POE), \nreduced from 100 to 90. The correction to the software is that the quantity\nfor all renewals will not be calculated, but use the quantity already\nentered for the prescription being renewed. \n \n2. The prescription editing functionality that allows prescriptions to be \nedited has been enhanced to process all fields selected for editing and\nverify that the edits do not cause a new prescription (order) to be created\nbefore updating the PRESCRIPTION file (#52) and CPRS ORDERS file (#100).\nCurrently the software will update the prescription being edited and the\nchanges to the new prescription. \nfunctionality was added to compute the quantity for prescriptions for\n \n3. An additional order check was added when entering backdoor prescriptions\nand finishing prescriptions entered by the provider. If maximum dispense\nunits per day is entered in the MAXIMUM DOSE PER DAY field (#4), in the DRUG\nfile (#50) it is used as an order check when the day supply is entered for\nbackdoor prescriptions. The problem is that the order check is not done\nwhen the quantity is entered or when finishing orders entered using CPRS.\nThis patch now checks for maximum dispense units per day when the quantity\nis entered through Backdoor Outpatient Pharmacy and when finishing\nprescriptions entered by a provider. \npossible dosages. During the testing phase for POE the computation of\n \n4. When entering prescriptions using the Outpatient Pharmacy package or the\nComputerize Patient Record System (CPRS) for schedule 2 through 5 drugs the\nmaximum number of refills of 5 was being allowed. A problem was discovered\nthat schedule 2 drugs should not allow any refills. This patch corrects\nthis problem. \n \n5. When finishing orders from the Computerize Patient Record System (CPRS)\nthat have a dosage greater than 60 characters, pharmacy cannot finish those\norders without editing the dosage down to 60 characters or less. When the\nquantity for CMOP prescriptions was not identified as being a problem. The\ndosage was edited the software was getting into a loop, which prevented the\nedited order from being accepted. This patch corrects this problem. \n \n6. When entering a backdoor order and an up-arrow is entered in the Route\nfield, the order entry process should abort but does not, which causes an\nundefined error. This patch corrects this. \n \n7. It appears that when a pharmacist is finishing orders and one is for a\npossible dose, which would have units in parenthesis, and the second order\nis for a local possible dosage, the units pointer variable is not killed\nproblem for the CMOP prescription happens when, for instance a prescription\nfrom the previous order and is displaying on the screen, but is not added\nto the order. \nhas a medication instruction that states to "TAKE 1 TABLET FOR 90 DAYS".\nFor non-CMOP prescriptions a quantity of 90 tablets would normally be\ndispensed, but for CMOP prescriptions the quantity often times should be a\nquantity of 100. When the CMOP prescriptions are renewed the quantity is\n\n
\nAs a part of the Pharmacy Benefits Management (PBM) Extract enhancement \npackages affected since only one installation is necessary. The patches, in\norder of install, are: \n \n PSS*1*52 PHARMACY DATA MANAGEMENT V. 1.0 \n PSJ*5*68 INPATIENT MEDICATIONS V. 5.0 \n PSO*7*95 OUTPATIENT PHARMACY V. 7.0 \n \nUpon completion of the installation of these three patches, the master build\nwill start a routine that will build the two new fields from historical data\nin the PHARMACY PATIENT file (#55). When the build is complete, the user\nproject, two new fields were added to the PHARMACY PATIENT file (#55). \nwho initiated the install and the members of the PSU PBM mail group will\nreceive a message with a subject of BUILD OF FIRST PHARMACY SERVICE INFO\nCOMPLETE.\nThey are FIRST SERVICE DATE (#.07) and ACTUAL/HISTORICAL FLAG (#.08).\nWith the addition of these two fields, Inpatient Medications V. 5.0 and\nOutpatient Pharmacy V. 7.0 have been modified to set this information when\nthe first order for a patient becomes active. \n \nThis project consists of three patches combined in a master build. \nInstallation of this master build should be coordinated among the three \n\n
\n1) When orders entered prior to the Pharmacy Ordering Enhancements patches\nwith a Sig that can be valid, since it is from the previous order. The\nproblem occurs when that order is renewed again, because the Sig from that\npoint on is built from the Dosing information, which could produce an\ninvalid Sig.\n \n \nTo fix this problem, CPRS patch OR*3*134 will identify these orders to\nPharmacy in a mail message. Pharmacy should then go and act accordingly on\nthese orders. Please refer to patch OR*3*134 for complete information.\n \nare renewed through Computerized Patient Record System (CPRS), CPRS will\nAs an added precaution, this patch, PSO*7*100, is being released. This \npatch will check the dosages associated with an order when that order is \nrenewed or copied through Outpatient Pharmacy, and if a Dosage is found in\nthe order that contains "0..", the process will not continue, and a\nmessage will be given to the user giving the reason. In addition, when a\nrenewal of an Outpatient order is entered through CPRS, a call is made to\nOutpatient Pharmacy that determines whether or not the order is renewable.\nWhen this occurs, a check will now be in place to look for dosages that\ncontain "0..", and if found, the renewal will not be allowed through\nCPRS. And to prevent any other invalid Sigs from being created as a \nsometimes automatically assign Possible Dosages to these orders, based on\nresult of invalid Dosing information automatically assigned to pre-POE\norders, this patch makes the change to the renewal process to always carry\nover the Sig from the prescription being renewed, instead of building the\nSig from the Dosing information that could have been assigned improperly\nwhen that prescription was originally renewed as a Pre-POE order.\n \nSince the change has been made to always populate the Sig from the \nprevious prescription on Renewals, a check will now be in place for a\nmissing Sig when prescriptions are renewed. If a prescription is renewed,\nand that prescription is missing the Sig, the prescription will not be \nprior order information. A problem was reported in that process that\nrenewable, and a message will be given to the user giving the reason.\n \n \n \n2) When using the Speed Renew function in Outpatient Pharmacy, after \nselecting the orders to renew, a number of prompts appear, one of those \nprompts being PATIENT STATUS. The response to that prompt is entered as \nthe Patient Status in the PHARMACY PATIENT (#55) file, but the \nprescriptions that are renewed still have the same Patient Status of the \nprescriptions being renewed. This patch will make the change to update \ninvolved CPRS passing an invalid dosage that began with "0..5", or another\nall of the renewals with the Patient Status entered at the PATIENT STATUS \nprompt.\ndosage that started with "0..", to Pharmacy when the Dispense Units per\nDose contained a decimal point. When these pre-POE orders are renewed, the\nSig is brought into the order from the order being renewed. If this \ninvalid dosage information is not edited, it stays with the order, along\n\n
\n \nfrom hold. Routines: PSOHLD, PSOLBLN\n \nAlso added a check in the routine PSOLBLN to check for the barcode on and\noff sequences being defined for Rx label printing.\n \n3. Added a check for site parameters being defined when using the Rx\nVerification by Clerk option [PSO VR]. Routine: PSOVER\n \n4. Corrected a problem where inventory deduction from the Drug file (#50)\ncould happen unnecessarily. Routine: PSORXED, PSORXED1.\n1. When Controlled Rxs are renewed, the expiration date was defaulting to\n \n5. Added a site parameter, VERIFYING PHARMACIST ON LABELS, that will allow\nsites to print the Verifying Pharmacist number on the 2nd line of labels.\n \n6. Fixed problem of refilling an Rx, and the refill suspending to the\noriginal Fill Date, instead of the Refill Date. Routine PSORXED\n \n7. Fixed problem of Editing a released Rx, and that Rx then suspending for\nCMOP instead of suspending locally. Routine PSOCMOP.\n \none year instead of six months. Routine: PSON52\n8. On line 2 of the labels, the first number printed after the phone\nnumber for CPRS entered orders has been the internal entry number of the\nperson entering the order in CPRS. This patch changes that number to the\nperson who Finishes the order in Pharmacy.\n \n2. When prescriptions are removed from Hold the user can reprint the label\nif they want. In the activity multiple events are recorded (placed on,\nremoved from hold). If a label is printed the label log does not show that\nthe label was printed because the Rx was removed from hold. This patch will\nrecord in the label log that the label was printed because an Rx was removed\n\n
\n1) A problem was reported where a Pending Outpatient Pharmacy Order did \n generate a mail message to the patch installer, and to all holders of\n the PSNMGR key. This message should be reviewed by the appropriate\n pharmacy personnel. The orders will not automatically be fixed to show\n up in the Complete Orders from OERR [PSO LMOE FINISH] option, since\n some of the orders may be old orders. But Pharmacy can review these\n orders from the mail message using the Patient Prescription Processing\n [PSO LM BACKDOOR ORDERS] option to determine the appropriate action.\n \n2) When a renewal is entered through CPRS for an outpatient pharmacy\n order, and that renewal is signed and sent to the Outpatient Pharmacy\n not show up in the Complete Orders from OERR [PSO LMOE FINISH] option.\n package, there are validation checks done on the renewal before the\n Outpatient Pharmacy package accepts the renewal. This patch will add\n two more validation checks.\n \n When the renewal is received in Outpatient Pharmacy, the software will\n now check the patient in the message against the patient in the\n PRESCRIPTION file (#52) from the previous pharmacy order number sent in\n the message, and if the patient does not match, then renewal will not\n be accepted by the Outpatient Pharmacy package. A previous order number\n check will also be added to this process. When the renewal is received,\n The problem occurs when the order is a "change" order from Computerized\n if the previous CPRS number does not match the CPRS number stored in\n the previous pharmacy order, then the renewal will not be accepted by\n the Outpatient Pharmacy package.\n \n3) This patch fixes two problems with the Medication Profile [PSO P]\n option. If a profile is printed for a patient who has pending\n outpatient pharmacy orders, those pending orders print at the end of\n the report, but the patient name is not at the top of these pages. This\n patch adds the patient name to the top of those pages. Also, if a\n patient only had pending outpatient orders, and no prescriptions, the\n Patient Record System (CPRS), and it is a complex order with very long \n pending outpatient orders would not display. This patch fixes the \n problem.\n Dosing Instructions. The order would show up in the Patient\n Prescription Processing [PSO LM BACKDOOR ORDERS] option, but would not\n always show up in the Complete Orders from OERR [PSO LMOE FINISH]\n option. This patch fixes the problem, and also as part of a post-init,\n will find all of these Pending Outpatient orders, if there are any, and\n\n
\nA problem was reported where certain Outpatient Pharmacy orders displayed \ninstaller of this patch. Other than installing these two patches, IRM \ndoes not need to take any additional action.\nin Computerized Patient Record System (CPRS) with a truncated Sig. This \nproblem only happens on complex Outpatient Pharmacy orders. CPRS patch \nOR*3*134 contains a fix that will prevent the problem for occurring. \nFor the currents orders that already have this problem, this patch,\nPSO*7*101, will search for all Outpatient Pharmacy orders with complex\nDosing Instructions. A background job will synchronize the medication \ninstructions between CPRS and Pharmacy so the displays will be correct. \nWhen the post install completes, a Mailman message will be sent to the \n\n
\n1. With the release of PSO*7*78 and editing of the PHARMACIST field (#20) or\nshould be zero (0) refills remaining, but if a user were to edit the # OF\nREFILLS field (#9) to 2 after dispensing 3, the refills remaining would show -1\nrefills remaining. This patch will prevent a total number of refills entered\nto be less than the number of refills already dispensed. \n \n3. When editing # OF REFILLS field (#9) in the PRESCRIPTION file (#52) an \nundefined error could occur when doing a VA FileMan lookup on the DRUG file\n(#50). This patch corrects this problem.\nthe DIVISION field (#23) in the PRESCRIPTION file (#52) data can become \ncorrupted by storing extra characters. This patch prevents further corruption. \n \n \n2. Currently when editing the # OF REFILLS field (#9) in the PRESCRIPTION file\n(#52) there is not currently a check to prevent a number from being entered\nless than the number of refills already dispensed. If the prescription was\noriginally entered with a total of 3 refills and 3 refills are dispensed, there\n\n
\n 1. When placing a new order through Outpatient Pharmacy that generates a \n Orderable Item has Drug Text associated with it, then an error would \n occur if the ListMan hidden action "DIN Drug Restr/Guide (OP)" is used. \n This patch prevents the error from occurring.\n \n 3. This patch fixes the problem of patient names sometimes not displaying\n on the bingo board when the patient has window prescriptions released \n through the Outpatient Pharmacy package.\n \n 4. This patch changes the default Nature of Order response from WRITTEN\n to SERVICE CORRECTION when edits are made to pending orders and\n duplicate drug check on another active order, if that new order is viewed\n prescriptions that create a new order. (E3R 16682)\n \n 5. When using the Complete Orders from OERR [PSO LMOE FINISH] option, it\n is possible that the METHOD OF PICK-UP entered for one patient's\n prescription can be carried over as the default response to the METHOD OF\n PICK-UP prompt for the next patient's prescription. This patches fixes\n this problem.\n \n 6. When a Renewal is done through Outpatient Pharmacy, a Nature of Order\n is prompted. The response to the Nature of Order prompt is sent to CPRS\n through Computerized Patient Record System (CPRS) utilizing the Detailed \n as the nature of Order for the new prescription, and also for the \n prescription that was discontinued because of the Renewal. Sending the\n Nature of Order for the discontinued order can possibly require a\n signature for the original provider in CPRS. This patch makes the change \n to not send the Nature of Order on the discontinued prescription.\n Display, the nature of order will show as "Duplicate", regardless of what\n nature of order was entered during the prescription entry process. This \n patch corrects this problem.\n \n 2. When finishing an order entered through CPRS in Outpatient Pharmacy, \n and there is no Dispense Drug associated with the order, and the Pharmacy\n\n
\nPatch PSO*7*71 is required before the installation of this patch.\ncancellation that have already been cancelled.\n b. Use the current value of the SERVICE CONNECTED field (#116) of the\nPRESCRIPTION file (#52) instead of attempting to derive it from\ninformation from a call to Integrated Billing.\n c. Added patient name on the line following the prompt "Select\nPRESCRIPTION RX #:".\n d. Made correction to display the released date for the original fill\nif it is present in the selection list for cancels.\n e. Display (RTS) beside original fills that have been Returned to Stock\nsince there will not be a released date.\n \n f. When choosing from the selection list for cancels, validate that the\nresponse only includes items that are on the list.\n \n2. At release of a fill changes were made to:\n a. Use the current value of the SERVICE CONNECTED field (#116) of the\nPRESCRIPTION file (#52) instead of attempting to derive it from\ninformation from a call to Integrated Billing.\n b. Unless the prescription is already exempt, always call Integrated\nBilling to check for income exemption. (Before this change, some\nprescriptions may appear in the copay activity log as being changed from\n \nno copay to copay and then immediately changed back from copay to no\ncopay).\n \n3. For the RETURN MEDICATION TO STOCK option changes were made for:\n a. If the last fill of a copay prescription has previously been\ncancelled, a message to that effect is displayed instead of prompting\nfor the CHARGE REMOVAL REASON.\n b. If the last fill of a copay prescription has previously been\ncancelled, Integrated Billing is not called to cancel the charge.\nThis will prevent an error message from IB.\nThis patch is a follow-up to patch PSO*7*71 for the Mill Bill Medication\n c. When an original fill for a copay prescription is returned to stock,\nthe IB node contains the IB cancellation number. Now that a new call to\nIntegrated Billing is available to check whether an IB number is a bill\nnumber or a cancel number, a change was made to call IB to bill if the\nfill is released again when the IB number present is a cancellation\nnumber.\n d. Messages were changed from "No Action Taken!" to "Prescription Not\nReturned to Stock!" if the return to stock action is not completed.\n e. Correction was made to cancel "potential charge" (charge exceeding\nannual cap) if it exists for the fill being returned to stock.\nCopay functionality. Items included in this patch are:\n \n4. The site number was added to the subject line of the MailMan message\ngenerated when one or more copay exemption questions has never been\nanswered. e.g. Subj: RX COPAY STATUS REVIEW NEEDED (7121). Also a change\nwas made to the MailMan message to clarify. The "Providers:" section was\nadded and "Staff assigned to update the Prescription Copay Status:" was\nadded just before the instructions for follow-up. The new text appears as:\n \n \nProviders:\n \nPlease respond with your answer to the question(s) as a reply to this\nmessage. The prescription will be updated by the appropriate staff.\n \nStaff assigned to update the Prescription Copay Status:\nPlease use the RESET COPAY STATUS/CANCEL CHARGES option to enter the\nresponses to the questions above, which may result in a Rx copay status\nchange and/or the need to remove copay charges.\n1. Under the Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]\noption changes were made to:\n a. Display an informative message for any fills selected for\n\n
\nBefore the release of the Pharmacy Ordering Enhancement patch (POE) pharmacy\nusers entered the patient medication instructions (SIG) using quick codes that\nexpand into readable instructions for the patient. There are some reported\ninstances where the quick codes are missing and an undefined error occurs. \nThis patch corrects this problem.\n\n
\nThis patch addresses the following concerns: \nprescription to ask the user, "Are You Sure You Want to Update Rx\n#? Yes//", if the edits did not create a new prescription. Updates\nto the prescription do not occur now until after the user finishes making\nchanges to the fields selected for editing and accepts the changes at the\nnew prompt. A problem was introduced with this patch in that when editing\nfree text fields and the input data contains a semi-colon (;), an error would\noccur when trying to update the PRESCRIPTION file (#52) entry.\nThis patch corrects this problem. \n \n3. When editing prescriptions that cause new prescriptions to be created,\n \nprescription numbers were being skipped. For example, if the last number\nused for a prescription was 5 and the next number to be used was 6. A\nprescription is edited in that it causes a new prescription to be created, the\nnext number was defaulting to 7 instead 6. This patch corrects this problem.\n1. This patch corrects an undefined error that occurs when all the dosage \ninformation is not asked for by the software when entering new\nprescriptions. This was a random error that only happened on occasion.\nWhen this error occurred it caused incomplete data to be added to the\nPRESCRIPTION file (#52).\n \n2. With the release of PSO*7*78 a prompt was added after editing a\n\n
\nBoth Computerized Patient Record System (CPRS) V. 1.0 and Inpatient \nMedications V. 5.0 packages were inappropriately display order check with \nan Inaction Date entered in the Inaction Date field (#7) of the Drug \nInteraction file (#56).\n\n
\nCentral Texas Veterans Health Care System has received multiple complaints\nonly the last 6 digits. \n \nPlease Note: If your site is using any class 3 software that requires the\nfull social security number, it may be necessary to make that this patch will\nnot cause that software to malfunction if installed. \nfrom patients about their full Social Security Number (SSN) printing on\ntheir prescription reorder documents. Currently the SSN at the top of the\nrefill document shows the last 6 digits, however the full SSN shows next to\nthe patient's name on the last page, just above the NARRATIVE REFILLABLE RX\ndocument. This patch will change all instances of the patient's SSN on the\nreorder documents to display only the last 6 digits. This patch will change\nall instances of the patient's SSN on the reorder documents and to the\nsection that shows any possible allergies and adverse reactions to display\n\n
\n1. When a user who does not possess the PSORPH key finishes a pending \nprompt for the rest of the prescriptions on the same patient. This patch\nfixes this problem. \norder using the Complete Orders from OERR [PSO LMOE FINISH] option, the \norder is flagged as active instead of non-verified. This patch corrects\nthis problem.\n \n2. When finishing a pending order using either the Patient Prescription \nProcessing [PSO LM BACKDOOR ORDERS] option, or the Complete Orders from\nOERR [PSO LMOE FINISH] option, the METHOD OF PICK-UP entered for one\nprescription is not carried over as the default response to the same\n\n
\nVersion 7.0 of Outpatient Pharmacy will interface with version 1.0 of\nOERR/CPRS.\n \n\n
\nThis distribution contains all the server code and data for the Remote\nProcedure Call (RPC) Broker version 1.0.\n\n
\nThis patch fixes some small problems that were discovered after release.\nXWBTCP 8888247 9081629 **1**\nXWBTCPL 8380513 8215020 **1**\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the effected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nXWBTCPL Remove the SYMBOL_TABLE from the VAX DSM JOB command.\n Backup a Transport Global\n \n 4. Users can remain on the system but,\n The Listener must be stopped before installing this patch.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*1'\n =========\n \nXWBTCP When stopping the Broker, Catch a failure to open a socket.\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\n \n 7. DSM Sites, after patch has installed, rebuild your map set.\n \n 8. Restart the Broker Listener\n =========================================================================\n\n\nXWB BROKER EXAMPLE option was missing its type field.\n\n Checksum\nRoutine Old New 2nd Line\n\n
\n** Y2K WAIVER - #Y2K0001 **\n \nGuide.\n1. Packman message containing the XWB*1.1*11 KIDS build. The packman\nmessage simply updates the version multiple of the package.\n \n2. Updated BDK (programmer client workstation software). All sites doing\nBroker development are encouraged to retrieve the patched BDK. This\nversion of the BDK supports Delphi 5, Delphi 4, and Delphi 3.\n \nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE AT END-USER\nCLIENT WORKSTATIONS. If you are not using the BDK in any local or\n \nnational development, you do not need to retrieve the Broker's programmer\nclient workstation software. The software does not update the Broker\nsoftware that is running at end-user client workstations.\n \nThe software distribution includes:\n \nFILE NAMES DESCRIPTION Bytes\nXWB1_1P11PG.EXE BDK Self-Installing Executable 2,200,099\nXWB1_1P11IG.PDF Installation Guide 185,092\nXWB1_1RM.TXT Readme text file 13,915*\nThis patch updates the Broker's programmer client workstation software --\nThe size of this file will change in the future as additions are made.\n \nNote: Use Binary mode for .PDF, and .EXE files\n Use ASCII mode for .TXT file.\n \nTo obtain the updated BDK, use FTP to retrieve the software from one of\nthe following CIO Field Offices' ANONYMOUS.SOFTWARE directories:\n \n CIO FIELD OFFICE FTP Address \n Hines 152.129.1.110 (isc-chicago.domain.ext)\nalso known as the Broker Development Kit (BDK) -- adding support for\n Albany 152.127.1.5 (isc-albany.domain.ext)\n Salt Lake City 152.131.2.1 (isc-slc.domain.ext)\n \nBROKER-DEPENDENT COMPONENTS:\n \nThe following comments apply only to those developing applications with\nthe BDK (programmer workstation software). They are not relevant to\nserver operation.\n \nWarning:\nDelphi 5 development.\nSome components, such as the FileMan Delphi Components, reference the\nTRPCBroker component. If you use such components for development, be\naware that installing a new version of the TRPCBroker component (i.e. a\nnew BDK) may cause incompatibilities in Delphi, resulting in a compile\nfailure of the unit containing the Broker-dependent component and the\nfollowing compilation error:\n \n Unit <unit1> was compiled with a different version of <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\n \nthat, with regards to the version of the BDK you are about to install:\n \na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible.\n \nc) You have the source (.pas, .dfm, .dpk, etc.) files available so that\nthe component can be recompiled successfully.\n \nIf you're using the FileMan Delphi Components (FMDC), please note that the\nIMPORTANT NOTES:\nFMDC source code includes references to RPC Broker Development Kit (BDK)\ncode. When you install a new version of the BDK, you will need to\nrecompile the FMDC.\n \nAs of patch FMDC*1.0*1, source code for FMDC is provided, allowing you\nto recompile FMDC if necessary. For instructions on how to recompile FMDC,\nplease refer to FMDC*1.0*2.\n \nINSTALLATION:\n \n \nServer Side:\n============\n \nUse the following instructions in installing this server-side RPC Broker\npatch. Do NOT follow the M Server Installation Instructions in the RPC\nBroker Installation Guide to install the server portion of this patch.\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS (Kernel Installation and Distribution System)\npackage onto your system. \nThis patch consists of 2 parts:\n \n2. On the KIDS menu, under the 'Installation' menu, use the following\noption:\n Install Package(s) 'XWB*1.1*11'\n ============\n \nClient Side:\n============\n \nPlease follow the instructions in the most recent Broker 1.1 Installation\n\n
\nALL SITES SHOULD INSTALL THIS PATCH!\n WCO-0300-51724\n WRJ-1299-10856\n MPI-1299-60581\n FTL-0200-51217\n BOI-0300-50946\n \nRoutine Summary:\n \nThe following routine is included in this patch. The second line of this\nroutine now looks like:\n \n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n \n Checksum\n Routine Old New 2nd Line\n XWBTCPL 8934371 9128997 **1,7,9,15**\n \n List of preceding patches: 9\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nThis patch should correct a problem on Cache sites with the Broker looping\n \nInstallation:\n \n 1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\n PCMM) during the installation. No Broker-based client/server \n software should be running while installing this patch on the \n server. To identify these jobs, check the system status and verify\n if any XWBTCPC routines are running (i.e., Broker Handler). Once \n identified, notify users to logoff or forcex the jobs. Active \n users may get NOSOURCE or CLOBBER errors. \nwith COMMAND errors. This error is caused when the Broker tries to open\n \n 2. Stop the Broker Listener on the server. Check the system status \n and verify if the XWBTCPL routine is running (i.e., Broker \n Listener). If it is running stop it. To stop the Listener, do the\n following: \n \n a. Log into your M server. \n b. Enter the following at the M prompt: \n \n >D STOP^XWBTCP(Listener port) \nthe TCP port and the port is already open by the broker.\n (Typically, the Listener port is 9200) \n \n 3. Broker routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n \n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n option:\nThis patch resolves the following NOIS calls: \n Install Package(s) 'XWB*1.1*15'\n =========\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 7. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n \n 8. Restart the Broker Listener on the Server:\n SPO-0300-51693\n a. Log into your M server\n b. Enter the following at the M prompt:\n \n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n MUR-0300-32581\n\n
\nThis patch gives greater information about and control of RPCs. Specific\n2. Assuring that an RPC is at least a specified version when it is run\npackage onto your system. \n \n 5. The patch has now been loaded into a Transport global on your system.\n On the KIDS menu, select the 'Installation' menu, use the following\noptions: \n Verify Checksum's in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \nremotely* by setting a value in the new VERSION field of the Remote\n 6. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n Install Package(s) 'XWB*1.1*10' \n ==========\n \n 7. When asked, answer these questions NO:\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols?\nProcedure file.\n YES// NO\n ==\n \n 8. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Enter the names of your Compute and Print server(s). \n AXP Sites - Answer NO to this question. \n \n 9. If the routines were unmapped as part of step 3, the mapped set\nshould be rebuilt once the installation has run to completion. \n \n \n 10. Restart the Broker Listener on the Server: see the current RPC Broker\nSystem Manual for details.\n3. Querying a server regarding the status of RPCs by using new Remote\nProcedures: XWB IS RPC AVAILABLE and XWB ARE RPCS AVAILABLE.\n \nPlease see the on-line descriptions of the INACTIVE and VERSION fields in\nthe Remote Procedure file and of the XWB IS RPC AVAILABLE and XWB ARE RPCS\nAVAILABLE Remote Procedure file entries for details of the use of the new\nnew abilities are:\nfunctionality.\n \nIn addition, this patch stops M errors from occurring when a client\napplication 1) attempts to create a context that does not exist on the\nserver or 2) attempts to run a remote procedure that does not exist on the\nserver. With this patch in both these situations, the user is shown a\nspecific error message explaining the problem. Several developers have\nrequested this fix, and the following NOIS calls are resolved:\n \nISP-0399-N2813 Broker Error When Client Calls Non-Existent RPC\n \nMWV-1099-20408 Error encountered with XWBBRK\nMWV-0499-21483 broker error since *169\nSLC-1298-50740 NULL SUBSCRIPT ERROR\nTOM-0798-41277 RPC ERRORS\nDES-1296-40252 ERROR AT PRSA+18^XWBBRK\nDAY-1196-42040 Error when PCMM not installed in the environment\n \n--------\n*'Locally' means an RPC is being run at the site which the user is logged\non to; 'remotely' means an RPC is being run at a site the user is not\n1. Blocking an RPC either locally*, remotely*, or in both contexts by\ndirectly logged on to.\n \n \nNOTES: \n=====\n \n1. The packman message containing the XWB*1.1*10 KIDS build installs 3\nmodified XWB* routines, one modified and one new field in the Remote\nProcedure file, and two new RPCs (entries in the Remote Procedure file). \n \nsetting a value in the INACTIVE field of the Remote Procedure file. The\nRoutine Summary: \n======= ========\n \nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like: \n \n<tab>;;1.1;RPC BROKER;[patch list];date \n \nCHECK^XTSUMBLD results: \n \nfield can be set either by a package developer and exported by KIDS or by\nRoutine Name Before Patch After Patch Patch List \nXWBBRK 4567623 5912545 2,4,10\nXWBLIB 720789 3253016 6,10 \nXWBSEC 2113752 2425405 3,6,10\n \nFields in Remote Procedure file (#8994):\n====== == ====== ========= ==== \n \nINACTIVE (#.06) is modified\nVERSION (#.09) is new\na site manager using FileMan. (Prior to this patch, values in this field\n \nRemote Procedure:\n====== =========\n \nXWB IS RPC AVAILABLE is new\nXWB ARE RPCS AVAILABLE is new\n \n2. There is no client portion of this patch.\n \n \nhad no effect.)\nINSTALLATION: \n============\n \n1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\nPCMM) during the installation. No Broker-based client/server software\nshould be running while installing this patch on the server. To identify\nthese jobs, check the system status and see if any XWBTCPC routine is\nrunning (i.e., Broker Handler). Once identified, notify users to logoff\nor forcex the jobs. Active users may get NOSOURCE or CLOBBER errors. \n \n \n 2. Stop the Broker Listener(s) on the server. Check the system status\nand see if the XWBTCPL routine is running (i.e., Broker Listener). If it\nis running stop it. There are several ways to stop the Listeners -- see\nthe current version of the RPC Broker System Manual for details.\n \n 3. These routines are not usually mapped on systems that support\nmapping; so, you will probably not have to disable mapping. \n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS (Kernel Installation and Distribution System)\n\n
\nThis patch is in support of the CPRS Remote Data Views project. The\nHL*1.6*57 \nHL*1.6*58 \nXU*8.0*131 \nXU*8.0*165 \nXWB*1.1*10\n \nTo facilitate the running of server to server RPCs, new RPCs are sent\nout in this patch. The documentation on how to use these RPCs can be\nfound on Forum's DBA menu. Please reference the following Integration\nAgreements:\nRPC Broker is used to facilitate invocation of Remote Procedure calls on a\n \n #3032 Direct RPCs - controlled subscription\n #3031 Remote RPCs - controlled subscription\n #3033 Deferred RPCs - supported\n \nNew Remote Procedure entries: \n 1. XWB REMOTE RPC \n 2. XWB REMOTE STATUS CHECK \n 3. XWB REMOTE GETDATA \n 4. XWB REMOTE CLEAR\nremote server. The RPC Broker uses Vista HL7 as the vehicle to pass RPC\n 5. XWB DEFERRED CLEAR\n 6. XWB DEFERRED CLEARALL\n 7. XWB DEFERRED RPC \n 8. XWB DEFERRED GETDATA \n 9. XWB DEFERRED STATUS \n 10. XWB DIRECT RPC \n \nNew Protocol entries: \n 1. XWB RPC EVENT \n 2. XWB RPC SUBSCRIBER \nname and parameters from a local server to a remote server. On the return\n \nNew HL7 Application Parameter entries: \n 1. XWB RECEIVER \n 2. XWB SENDER \n \nThis 'Server to Server RPC' functionality is currently limited to sites\nthat have implemented CIRN. CIRN makes it possible for an application to\nknow a patient's current list of treating facilities. Furthermore, CIRN\nhas assumed responsibility for supervising the proper configuration and\nactivation of the VA network nodes that will be used for HL7 message\npath, Vista HL7 is also used to send results from the remote server back\nexchange.\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n \n Checksum\nRoutine Old New 2nd Line\nXWB2HL7 9722375 **12**\nto the local server.\nXWB2HL7A 6313853 **12**\nXWB2HL7B 9424236 **12**\nXWBDRPC 4972286 **12**\n \nSites should use CHECK^XTSUMBLD to verify checksums.\n \n========================================================================= \nInstallation:\n \n>>>Users may remain on the system.\n \n This patch brings in new functionality.\n No existing package is affected by the installation\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\nThe following is the list of required patches: \n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 3. Users can remain on the system.\n This patch can be queued and installed at any time.\n \n 4. On the KIDS menu, under the 'Installation' menu, use the following\nHL*1.6*54 \n option:\n Install Package(s) 'XWB*1.1*12'\n ==========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n =========================================================================\n\n
\nLOM-0800-62301 XWB2HL7 If there are problems associated with the remote \nof these routines now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n\n Checksum\nRoutine Old New 2nd Line\nXWB2HL7 9722375 9756388 **12,18**\n\nList of preceding patches: 12\nSites should use CHECK^XTSUMBLD to verify checksums.\n\nPRO-0800-12778 site's HL7 definitions -- specifically the receiving \n=========================================================================\nInstallation:\n\n 1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\n PCMM) during the installation. No Broker-based client/server \n software should be running while installing this patch on the \n server. To identify these jobs, check the system status and verify\n if any XWBTCPC routines are running (i.e., Broker Handler). Once \n identified, notify users to logoff or forcex the jobs. Active \n users may get NOSOURCE or CLOBBER errors. \n application. \n \n 2. Stop the Broker Listener on the server. Check the system status \n and verify if the XWBTCPL routine is running (i.e., Broker \n Listener). If it is running stop it. To stop the Listener, do the\n following: \n \n a. Log into your M server. \n b. Enter the following at the M prompt: \n \n >D STOP^XWBTCP(Listener port) \n Then the RPC XWB REMOTE STATUS CHECK will get a \n (Typically, the Listener port is 9200) \n\n 3. Broker routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping.\n\n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n\n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n UNDEF error on the variable Z. This has been fixed.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 6. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n \n Install Package(s) 'XWB*1.1*18'\n ==========\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n 7. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n\n 8. Restart the Broker Listener on the Server:\n\n a. Log into your M server\n b. Enter the following at the M prompt:\n\n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n\n============================================================================\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\n\n
\nThis patch updates the Broker's programmer client workstation software --\n \naware that installing a new version of the TRPCBroker component (i.e. a\nnew BDK) may cause incompatibilities in Delphi, resulting in a compile\nfailure of the unit containing the Broker-dependent component and the\nfollowing compilation error:\n \n Unit <unit1> was compiled with a different version of <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\nthat, with regards to the version of the BDK you are about to install:\n \nThe release of the source code does not affect how a developer uses the\na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible.\n \nc) You have the source (.pas, .dfm, .dpk, etc.) files available so that\nthe component can be recompiled successfully. If you're using the\nFileMan Delphi Components (FMDC), please note that the FMDC source code\nincludes references to RPC Broker Development Kit (BDK) code. When you\ninstall a new version of the BDK, you will need to recompile the FMDC.\n As of patch FMDC*1.0*1, source code for FMDC is provided, allowing you\nBroker Component or other parts of the BDK. Modified BDK source code\nto recompile FMDC if necessary. For instructions on how to recompile FMDC,\nplease refer to FMDC*1.0*2.\n \nINSTALLATION:\n \nServer Side: \n============\n \nUse the following instructions in installing this server-side RPC Broker\npatch. Do NOT follow the M Server Installation Instructions in the RPC\nshould NOT be used to create VistA GUI applications. Suggestions for\nBroker Installation Guide to install the server portion of this patch.\n \nNo routines or other package components are added or modified on the\nserver by this patch.\n \n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option\nwill load the KIDS (Kernel Installation and Distribution System) package\nonto your system. \n \n2. On the KIDS menu, under the 'Installation' menu, use the following\nchanges to the BDK should be done via NOIS (for bugs ) or E3R (for\noption:\nInstall Package(s) 'XWB*1.1*14'\n ==========\n \nAnswer the install questions like this:\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\nenhancements) for review and possible inclusion in another patch.\n \n \nClient Side: \n============\n \nPlease follow the instructions in the most recent Broker 1.1 Installation\nGuide. \n \nThe BDK now has separate run-time and design-time packages. There is no\nlonger a VistaBroker package. The new packages are XWB_Dxx and XWB_Rxx,\nwhere D means Design-time and R means Run-time and where xx is two digits\nalso known as the Broker Development Kit (BDK). It adds no new\nindicating the version of Delphi with which it should be used (e.g.,\nXWB_D50 is the design-time package for Delphi 5.0). Splitting the BDK\ninto separate packages resolves certain compatibility problems that arose\nfrom having a single run- and design-time package. It also eliminates a\ncertain problem with Delphi 5.0's dsgnintf unit that prevented users of\nthe Standard edition of Delphi 5.0 from using the Broker.\n \nThe run-time package should not be used to create executables that depend\non a separate XWB_Rxx.bpl installed on client workstations. There is no\nprocedure in place at this time to reliably install the correct version of\nfunctionality.\nthe run-time bpl on client workstations. Do NOT compile your project so\nthat it relies on dynamic linking with the BDK's run-time package; that\nis, do NOT check the 'Build with runtime packages' box on the Packages tab\nof the Project Options dialog. \n \nThis patch addresses issues raised in the following NOISs:\n \nPOR-0200-51902 Can't install CPRSDTTM package in Delphi 4\nPOR-0200-50554 When is the source code being distributed ?\nPOR-0400-51704 RPC Broker Source Code\n \n \n \nIMPORTANT NOTES:\n \nThis patch consists of 2 parts:\n \n1. Packman message containing the XWB*1.1*14 KIDS build. The packman\nmessage simply updates the version multiple of the package.\n \n2. Updated BDK (programmer client workstation software). This version of\nThis patch:\nthe BDK supports Delphi 5, Delphi 4, and Delphi 3. \n \nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE ON END-USER\nCLIENT WORKSTATIONS. If you are not using the BDK in any local or\nnational development, you do not need to retrieve the Broker's programmer\nclient workstation software. The software does not update the Broker\nsoftware that is running at end-user client workstations. Further, since\nno new functionality is added to the BDK by this patch, you do not have to\nretrieve and install it on programmer workstations unless you either want\nto see the BDK source code or need to use separate run- and design-time\n \npackages.\n \nThe software distribution includes:\n \nFILE NAMES DESCRIPTION Bytes \nXWB1_1P14PG.EXE BDK Self-Installing Executable 2,905,311\nXWB1_1P14IG.PDF Installation Guide 171,945\nXWB1_1RM.TXT Readme text file 15,686*\n*The size of this file will change in the future as additions are made.\n \n- releases the source code for the BDK\nNote: Use Binary mode for .PDF, and .EXE files. \n Use ASCII mode for .TXT file.\n \nTo obtain the updated BDK, use FTP to retrieve the software from one of\nthe following CIO Field Offices' ANONYMOUS.SOFTWARE directories:\n \n CIO FIELD OFFICE FTP Address \nHines 152.129.1.110 (isc-chicago.domain.ext)\nAlbany 152.127.1.5 (isc-albany.domain.ext) \nSalt Lake City 152.131.2.1 (isc-slc.domain.ext)\n- splits the VistaBroker package into separate design- and run-time\n \nPACKAGE DEPENDENCIES:\n \nA Package may have been defined to require the Broker package. Patch\nXWB*1.1*14 changes the identity of the Broker design-time package. If you\ntry to install a package into the Delphi IDE that requires the Broker, you\nmay receive an error message like:\n \n Can't load package <Package1>.\n One of the library files needed to run this package cannot be found.\npackages.\n \nTo resolve this problem, Open the dpk file associated with that package;\ndelete the reference to the old version of the Broker in the Requires\nsection; add a reference to the new design-time Broker package (XWB_Dxx)\ninto the Requires section; recompile and install the package.\n \nBROKER-DEPENDENT COMPONENTS:\n \nWarning: Some components, such as the FileMan Delphi Components, reference\nthe TRPCBroker component. If you use such components for development, be\n\n
\nNOIS Calls: LAS-1000-62717\nto .5 just before the call to the RPC. This was done because the code to set\nup the user at the remote site wasn't ready. When the code was fixed to \nproperly set the DUZ, the old code was never removed. This has been fixed \nin the routine XWB2HL7. If data was left in the ^XUTL("XQ",$J,"IO")node it \ncould cause problems when HOME^%ZIS is called by some RPC's, so this ^XUTL \nnode is killed off before the RPC is called.\n \nIn a E-mail message from CPRS developers: The global that may be used to \npass data back to the RPC was not killed before its use. This was fixed in \nthe routine XWBDRPC.\n BOI-1000-52970\n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n \n Checksum\nRoutine Old New 2nd Line\nXWB2HL7 9756388 9762168 **12,18,20**\nXWBDRPC 4972286 5069845 **12,20**\n LOM-1200-62234\n \nList of preceding patches: 12, 18\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n=========================================================================\nInstallation:\n \n 1. Do not run any RPC-Broker-based Remote Data View software \n (e.g., CPRS, PCMM) during the installation. Do not allow any \n incoming HL7 RDV messages. To identify these jobs, check the \n ANN-1200-41924\n system status and verify if any XWBTCPC routines are running \n (i.e., Broker Handler). Once identified, notify users to logoff \n or forcex the jobs. Active users may get NOSOURCE or CLOBBER \n error messages . \n \n 2. Stop the Broker Listener on the server. Check the system status \n and verify if the XWBTCPL routine is running (i.e., Broker \n Listener). If it is running stop it. To stop the Listener, do the\n following: \n \n WRJ-1100-11904\n a. Log into your M server. \n b. Enter the following at the M prompt: \n \n >D STOP^XWBTCP(Listener port) \n (Typically, the Listener port is 9200) \n \n 3. Broker routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n BEC-1100-20841\n option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n \n Backup a Transport Global\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*20'\n ==========\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \nROUTINE: XWB2HL7 \n 7. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n \n 8. Restart the Broker Listener on the Server:\n a. Log into your M server\n b. Enter the following at the M prompt:\n \n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n \nDuring the early testing of RDV (Remote Data View), the DUZ value was hard set \n============================================================================\n \n \n\n\nNOIS: BRX-0401-12377, ISA-0401-12369\nBecause the error occurred before RDV was setup to handle an error, it caused\nthe calling site to keep sending the same message repeatedly. This has been \nfixed by setting an error trap at the beginning of RDV. \n \nIf the application does not set some data into the return variable,\nXWB2HL7 will return a string starting with "-1^".\n \nThe XWB EXAMPLE option, RPC's and routine (XWBEXMPL) are included to\nadd an entry point for testing that will record the symbol table in the error\ntrap.\nThe calling site had a New Person File entry with a phone number containing a \n \nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n \n Checksum\nRoutine Old New 2nd Line\nXWB2HL7 9762168 10783627 **12,18,20,22**\nXWB2HL7B 9424236 9524542 **12,22**\ntrailing backslash (\\). As part of Remote Data Views (RDV) this data was then \nXWBEXMPL 1244483 1441211 **22**\n \nList of preceding patches: 20\nSites should use CHECK^XTSUMBLD to verify checksums.\n=========================================================================\nInstallation:\n \n 1. Do not run any RPC-Broker-based Remote Data View software \n (e.g., CPRS, PCMM) during the installation. Do not allow any \n incoming HL7 RDV messages. To identify these jobs, check the \nencoded and sent to the remote site.\n system status and verify if any XWBTCPC routines are running \n (i.e., Broker Handler). Once identified, notify users to logoff \n or forcex the jobs. Active users may get NOSOURCE or CLOBBER \n error messages . \n \n 2. Stop the Broker Listener on the server. Check the system status \n and verify if the XWBTCPL routine is running (i.e., Broker \n Listener). If it is running stop it. To stop the Listener, do the\n following: \n \n \n a. Log into your M server. \n b. Enter the following at the M prompt: \n \n >D STOP^XWBTCP(Listener port) \n (Typically, the Listener port is 9200) \n \n 3. Broker routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\nAt the remote site, a bug caused the backslash (\\) to be appended to the \n option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nend of several other strings, which then caused the reported error. This was \n Backup a Transport Global\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*22'\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES//\n \n No Options or Protocols need to be placed out-of-order.\nfixed by correcting the decoding routine.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 7. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n \n 8. Restart the Broker Listener on the Server:\n a. Log into your M server\n b. Enter the following at the M prompt:\n \n \n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n \n============================================================================\n \n\n
\nThis patch supports only Delphi V. 4 and Delphi V. 5. Although Delphi V.\nlimited privileges, preventing their ability to read data from the\n \nBROKER-DEPENDENT COMPONENTS:\n \nWarning: Some components, such as the FileMan Delphi Components (FMDC),\nreference the TRPCBroker component. If you use such components for\ndevelopment, be aware that installing a new version of the TRPCBroker\ncomponent (i.e., a new BDK) may cause incompatibilities in Delphi,\nresulting in a compile failure of the unit containing the Broker-dependent\ncomponent and the following compilation error:\n \nregistry. This has been observed when a user with limited NT privileges\n Unit <unit1> was compiled with a different version of \n <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\nthat, with regards to the version of the BDK you are about to install:\n \na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible.\n \nattempts to select a location for the RPC Broker connection, and it\nc) You have the source (.pas, .dfm, .dpk, etc.) files available so that\nthe component can be recompiled successfully. If you're using the FileMan\nDelphi Components (FMDC), please note that the FMDC source code includes\nreferences to RPC Broker Development Kit (BDK) code. When you install a\nnew version of the BDK, you will need to recompile the FMDC.\n \n As of patch FMDC*1.0*1, source code for FMDC is provided, allowing you\nto recompile FMDC if necessary. For instructions on how to recompile FMDC,\nplease refer to FMDC*1.0*2.\n \nresults in the use of the default BrokerServer/9200. However, users with\n \nINSTALLATION:\n \nServer Side:\n============\n \nUse the following instructions in installing this server-side RPC Broker\npatch. Do NOT follow the M Server Installation Instructions in the RPC\nBroker Installation Guide to install the server portion of this patch.\n \nhigher levels of NT access do not see this problem.\nNo routines or other package components are added or modified on the\nserver by this patch.\n \n1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. This option\nwill load the KIDS (Kernel Installation and Distribution System) package\nonto your system.\n \n2. On the KIDS menu, under the Installation menu, use the following\noption:\n \n \nInstall Package(s) "XWB*1.1*24"\n ==========\n \nAnswer the install questions like this:\n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n \nThe BDK now has separate run-time and design-time packages. There is no\n \nClient Side:\n============\n \nPlease follow the instructions in the most recent Broker 1.1 Installation\nGuide.\n \n \nClient Routine Information:\n==========================\nlonger a VistaBroker package. The new packages are XWB_Dxx and XWB_Rxx,\n \n \nThe following information is based on the LOG file for a complete\ninstallation (i.e., all options checked). A line shows the directory\ninvolved, based on the default installation directory. Each file is shown\non a separate line, with data shown for:\n \nfilename file file version bytes CRC32\n date time if present\n \nwhere "D" means Design-time, "R" means Run-time and "xx" represents two\nfile_date, file_time and bytes can be obtained from looking at NT or\nWindows Explorer (or similar file management program) or from examining\nProperties for the file.\n \n \nC:\\Program Files\\VISTA\\BDK32\\D5\n \nfrmSignonMessage.dcu | 04-06-2000 | 16:49:16 | | 3575 | 7ebbde9c\nfrmSignonMessage.dfm | 03-24-1999 | 16:30:38 | | 2503 | c99d9a3f\nHash.dcu | 04-06-2000 | 16:49:16 | | 3407 | 6e11e4db\ndigits indicating the version of Delphi with which it should be used\nLoginfrm.dcu | 04-06-2000 | 16:49:16 | | 10278 | e6ea9af7\nLoginfrm.dfm | 03-30-2000 | 15:09:42 | | 10723 | 189eb9ab\nMfunstr.dcu | 04-06-2000 | 16:49:16 | | 1278 | 519212c6\nRpcbedtr.dcu | 07-26-2001 | 10:36:46 | | 5759 | d229eed1\nRpcberr.dcu | 04-06-2000 | 16:49:16 | | 11018 | 8793213f\nRpcberr.dfm | 03-24-1999 | 16:30:36 | | 936 | 75e6c84e\nRpcConf1.dcu | 04-06-2000 | 16:49:16 | | 7144 | 84b170e8\nRpcConf1.dfm | 02-03-2000 | 14:46:52 | | 4089 | 15e6bd20\nrpcnet.dcu | 07-11-2001 | 10:33:16 | | 11330 | c97560a2\nrpcnet.dfm | 04-06-2000 | 09:55:28 | | 281 | 8b878eb9\n3 is no longer supported, the code written for Delphi V. 3 is correct and\n(e.g., XWB_D50 is the design-time package for Delphi V. 5.0).\nSelDiv.dcu | 04-06-2000 | 16:49:16 | | 5944 | 5adb9cf3\nSelDiv.dfm | 02-03-2000 | 14:47:52 | | 3221 | ad28ebb1\nSgnoncnf.dcu | 04-06-2000 | 16:49:16 | | 8613 | ddad2542\nSgnoncnf.dfm | 03-30-2000 | 15:39:26 | | 2170 | 8eada139\nSplVista.dcu | 07-11-2001 | 10:33:16 | | 4176 | a42aa664\nSplVista.dfm | 03-24-1999 | 16:30:36 | | 231724 | a522e10c\nTrpcb.dcr | 06-25-1999 | 15:23:18 | | 476 | 9fd8bd12\nTrpcb.dcu | 07-11-2001 | 10:33:16 | | 19285 | 4450b0f9\nVcedit.dcu | 04-06-2000 | 16:49:16 | | 8554 | d39d5985\nVcedit.dfm | 03-24-1999 | 16:30:36 | | 2906 | 8737a896\n \nWSockc.dcu | 07-26-2001 | 11:03:13 | | 12800 | 18d2baf6\nXWBReg.dcu | 07-26-2001 | 10:36:46 | | 918 | 8b64f583\nXwbut1.dcu | 07-11-2001 | 10:33:16 | | 6854 | 7a2cb48e\nXWB_D50.bpl | 07-26-2001 | 11:03:17 | 1.1.24.0 | 23040 | 7994c60e\nXWB_D50.dcp | 07-26-2001 | 11:03:17 | | 8957 | f3516d9b\nXWB_D50.dcu | 07-26-2001 | 11:03:17 | | 3223 | f77ebfab\nXWB_R50.bpl | 07-26-2001 | 11:03:17 | 1.1.24.0 | 375296 | 25d95d54\nXWB_R50.dcp | 07-26-2001 | 11:03:17 | | 78880 | 93424a1d\nXWB_R50.dcu | 07-26-2001 | 11:03:17 | | 2897 | cf59e7be\nBroker.cnt | 10-10-1997 | 10:08:52 | | 5005 | 557466bd\nThe run-time package should not be used to create executables that depend\nBroker.hlp | 10-10-1997 | 09:46:20 | | 2019500 | 142de115\nBrokerSM.cnt | 10-09-1997 | 17:53:54 | | 1787 | a79a3faa\nBrokerSM.hlp | 10-09-1997 | 16:37:42 | | 2444328 | a1743e99\n \n \nC:\\WINNT\\system32\\\n \nXWB_R50.bpl | 07-26-2001 | 11:03:17 | 1.1.24.0 | 375296 | 25d95d54\n \n \non a separate XWB_Rxx.bpl installed on client workstations. There is no\nC:\\Program Files\\VISTA\\BDK32\\D5\\Source\n \nBapi.pas | 04-05-2000 | 13:22:08 | | 16143 | b2f0a4c6\nBapi32.dpr | 03-24-1999 | 16:30:36 | | 297 | 5695f186\nfrmSignonMessage.dfm | 03-24-1999 | 16:30:38 | | 2503 | c99d9a3f\nfrmSignonMessage.pas | 04-05-2000 | 13:23:02 | | 1104 | 6becf6c6\nHash.pas | 04-05-2000 | 13:24:10 | | 3642 | 15f82810\nLoginfrm.dfm | 03-30-2000 | 15:09:42 | | 10723 | 189eb9ab\nLoginfrm.pas | 04-05-2000 | 13:24:52 | | 9010 | 8a3180b5\nMfunstr.pas | 04-05-2000 | 13:25:16 | | 2428 | 5c7d87d\nprocedure in place at this time to reliably install the correct version of\nRpcbedtr.pas | 04-05-2000 | 13:25:48 | | 5244 | 554eab2d\nRpcberr.dfm | 03-24-1999 | 16:30:36 | | 936 | 75e6c84e\nRpcberr.pas | 04-05-2000 | 13:35:18 | | 7085 | db5e1d1d\nRpcConf1.dfm | 02-03-2000 | 14:46:52 | | 4089 | 15e6bd20\nRpcConf1.pas | 04-05-2000 | 13:37:30 | | 4969 | ba6f63e8\nrpcnet.dfm | 04-06-2000 | 09:55:28 | | 281 | 8b878eb9\nrpcnet.pas | 07-11-2001 | 10:17:10 | | 11279 | 76cba96f\nSelDiv.dfm | 02-03-2000 | 14:47:52 | | 3221 | ad28ebb1\nSelDiv.pas | 04-05-2000 | 13:38:46 | | 5103 | ac237cad\nSgnoncnf.dfm | 03-30-2000 | 15:39:26 | | 2170 | 8eada139\nthe run-time bpl on client workstations. Do NOT compile your project so\nSgnoncnf.pas | 04-05-2000 | 13:39:06 | | 5824 | 698571b5\nSplVista.dfm | 03-24-1999 | 16:30:36 | | 231724 | a522e10c\nSplVista.pas | 07-11-2001 | 10:17:02 | | 2537 | 946d0504\nTrpcb.dcr | 06-25-1999 | 15:23:18 | | 476 | 9fd8bd12\nTrpcb.pas | 07-11-2001 | 10:16:52 | | 41668 | e0f2050d\nVcedit.dfm | 03-24-1999 | 16:30:36 | | 2906 | 8737a896\nVcedit.pas | 04-05-2000 | 13:40:54 | | 5918 | 8e86170d\nWSockc.pas | 07-26-2001 | 11:02:24 | | 26275 | f76aa165\nXWBReg.pas | 04-05-2000 | 13:42:50 | | 912 | 8e286b55\nXwbut1.pas | 07-11-2001 | 10:20:54 | | 9977 | 2f69588c\nthat it relies on dynamic linking with the BDK's run-time package; that\nXWB_D50.dpk | 07-09-2001 | 12:06:06 | | 658 | 441496c\nXWB_D50.res | 07-09-2001 | 12:06:04 | | 1684 | d15c2bc2\nXWB_R50.dpk | 07-09-2001 | 12:07:46 | | 1113 | ce020a2b\nXWB_R50.res | 07-09-2001 | 12:07:44 | | 1680 | 9888b151\n \n \nC:\\Program Files\\VISTA\\BDK32\\D4\n \nfrmSignonMessage.dcu | 04-06-2000 | 16:38:26 | | 3474 | 5171af7e\nfrmSignonMessage.dfm | 03-24-1999 | 16:30:38 | | 2503 | c99d9a3f\nis, do NOT check the "Build with runtime packages" box on the Packages tab\nHash.dcu | 04-06-2000 | 16:38:26 | | 3445 | d44d04b0\nLoginfrm.dcu | 04-06-2000 | 16:38:26 | | 10116 | f295f963\nLoginfrm.dfm | 03-30-2000 | 15:09:42 | | 10723 | 189eb9ab\nMfunstr.dcu | 04-06-2000 | 16:38:26 | | 1287 | cea6bdf5\nRpcbedtr.dcu | 04-06-2000 | 16:40:36 | | 5722 | c9f7bed3\nRpcberr.dcu | 04-06-2000 | 16:38:26 | | 10915 | 48821c37\nRpcberr.dfm | 03-24-1999 | 16:30:36 | | 936 | 75e6c84e\nRpcconf1.dcu | 04-06-2000 | 16:38:26 | | 7020 | fc3cd7b5\nRpcConf1.dfm | 02-03-2000 | 14:46:52 | | 4089 | 15e6bd20\nRpcnet.dcu | 07-20-2001 | 11:30:38 | | 11294 | f35f63d8\nof the Project Options dialog.\nrpcnet.dfm | 04-06-2000 | 09:55:28 | | 281 | 8b878eb9\nSelDiv.dcu | 04-06-2000 | 16:38:26 | | 5841 | 6a2587fb\nSelDiv.dfm | 02-03-2000 | 14:47:52 | | 3221 | ad28ebb1\nSgnoncnf.dcu | 04-06-2000 | 16:38:26 | | 8478 | 38775bc7\nSgnoncnf.dfm | 03-30-2000 | 15:39:26 | | 2170 | 8eada139\nSplvista.dcu | 07-20-2001 | 11:30:38 | | 4075 | 9e88d03c\nSplVista.dfm | 03-24-1999 | 16:30:36 | | 231724 | a522e10c\nTrpcb.dcr | 06-25-1999 | 15:23:18 | | 476 | 9fd8bd12\nTrpcb.dcu | 07-20-2001 | 11:30:38 | | 19539 | 388d1409\nVcedit.dcu | 04-06-2000 | 16:38:26 | | 8389 | d509b09f\n \nVcedit.dfm | 03-24-1999 | 16:30:36 | | 2906 | 8737a896\nWSockc.dcu | 07-26-2001 | 11:33:21 | | 12752 | bd7988d2\nXWBReg.dcu | 04-06-2000 | 16:40:36 | | 926 | 20433d5c\nXwbut1.dcu | 07-20-2001 | 11:30:38 | | 6842 | 5a9b68c1\nXWB_D40.bpl | 07-26-2001 | 11:33:21 | 1.1.24.0 | 22016 | 08d182df\nXWB_D40.dcp | 07-26-2001 | 11:33:21 | | 8727 | 2edd32c6\nXWB_D40.dcu | 07-26-2001 | 11:33:21 | | 2900 | de2fe0d1\nXWB_R40.bpl | 07-26-2001 | 11:33:21 | 1.1.24.0 | 373760 | 3e08ae56\nXWB_R40.dcp | 07-26-2001 | 11:33:21 | | 78344 | c88f66d4\nXWB_R40.dcu | 07-26-2001 | 11:33:21 | | 2623 | 29d300ad\nthis patch does not affect that code.\n \nBroker.cnt | 10-10-1997 | 10:08:52 | | 5005 | 557466bd\nBroker.hlp | 10-10-1997 | 09:46:20 | | 2019500 | 142de115\nBrokerSM.cnt | 10-09-1997 | 17:53:54 | | 1787 | a79a3faa\nBrokerSM.hlp | 10-09-1997 | 16:37:42 | | 2444328 | a1743e99\n \n \n \nC:\\WINNT\\system32\\\n \nXWB_R40.bpl | 07-26-2001 | 11:33:21 | 1.1.24.0 | 373760 | 3e08ae56\nThis patch addresses issues raised in the following NOISs:\n \n \nC:\\Program Files\\VISTA\\BDK32\\D4\\Source\n \nBapi.pas | 04-05-2000 | 13:22:08 | | 16143 | b2f0a4c6\nBapi32.dpr | 03-24-1999 | 16:30:36 | | 297 | 5695f186\nfrmSignonMessage.dfm | 03-24-1999 | 16:30:38 | | 2503 | c99d9a3f\nfrmSignonMessage.pas | 04-05-2000 | 13:23:02 | | 1104 | 6becf6c6\nHash.pas | 04-05-2000 | 13:24:10 | | 3642 | 15f82810\nLoginfrm.dfm | 03-30-2000 | 15:09:42 | | 10723 | 189eb9ab\n \nLoginfrm.pas | 04-05-2000 | 13:24:52 | | 9010 | 8a3180b5\nMfunstr.pas | 04-05-2000 | 13:25:16 | | 2428 | 5c7d87d\nRpcbedtr.pas | 04-05-2000 | 13:25:48 | | 5244 | 554eab2d\nRpcberr.dfm | 03-24-1999 | 16:30:36 | | 936 | 75e6c84e\nRpcberr.pas | 04-05-2000 | 13:35:18 | | 7085 | db5e1d1d\nRpcConf1.dfm | 02-03-2000 | 14:46:52 | | 4089 | 15e6bd20\nRpcConf1.pas | 04-05-2000 | 13:37:30 | | 4969 | ba6f63e8\nrpcnet.dfm | 04-06-2000 | 09:55:28 | | 281 | 8b878eb9\nrpcnet.pas | 07-11-2001 | 10:23:46 | | 11210 | d02eb245\nSelDiv.dfm | 02-03-2000 | 14:47:52 | | 3221 | ad28ebb1\nMAC-0601-62549 Broker host list from CPRS\nSelDiv.pas | 04-05-2000 | 13:38:46 | | 5103 | ac237cad\nSgnoncnf.dfm | 03-30-2000 | 15:39:26 | | 2170 | 8eada139\nSgnoncnf.pas | 04-05-2000 | 13:39:06 | | 5824 | 698571b5\nSplVista.dfm | 03-24-1999 | 16:30:36 | | 231724 | a522e10c\nSplVista.pas | 07-11-2001 | 10:25:22 | | 2528 | e133f2a\nTrpcb.dcr | 06-25-1999 | 15:23:18 | | 476 | 9fd8bd12\nTrpcb.pas | 07-11-2001 | 10:25:12 | | 41667 | 2499a80d\nVcedit.dfm | 03-24-1999 | 16:30:36 | | 2906 | 8737a896\nVcedit.pas | 04-05-2000 | 13:40:54 | | 5918 | 8e86170d\nWSockc.pas | 07-26-2001 | 11:31:18 | | 26275 | f76aa165\nMIW-0601-41984 Host not found error\nXWBReg.pas | 04-05-2000 | 13:42:50 | | 912 | 8e286b55\nXwbut1.pas | 07-11-2001 | 10:27:04 | | 9980 | 44563118\nXWB_D40.dpk | 07-09-2001 | 11:31:34 | | 659 | cd4c3678\nXWB_D40.res | 07-09-2001 | 11:31:32 | | 1688 | b1a4fa3d\nXWB_R40.dpk | 07-09-2001 | 11:32:12 | | 1118 | f71dd4e9\nXWB_R40.res | 07-09-2001 | 11:32:10 | | 1680 | a41a750d\n \n \nC:\\Program Files\\VISTA\\BDK32\\\n \nMOU-0601-32241 CPRS GUI and serverlist.exe file\nBrokerProgPref.exe | 03-24-1999 | 09:03:34 | | 327680 | d13c4bce\nBROKERPROGPREF.HLP | 09-16-1997 | 15:39:10 | | 22500 | 72cc929d\nServerList.exe | 01-26-1999 | 11:47:56 | | 513536 | 324b2f34\nSERVERLIST.HLP | 09-16-1997 | 10:28:02 | | 8341 | 6ff7a68b\n \n \nC:\\Program Files\\VISTA\\BDK32\\HEADERS\n \nBAPI32.bas | 08-20-1997 | 17:50:44 | | 1899 | 3f2f8fe1\nBapi32.h | 08-25-1997 | 10:59:16 | | 980 | 683a80df\n \nBapi32.hpp | 08-25-1997 | 11:05:48 | | 4842 | b53def20\n \n \nMade Dir: C:\\Program Files\\VISTA\\BDK32\\SAMPLES\\BROKEREX\n \nBrokerExample.dpr | 09-05-1997 | 17:37:48 | | 640 | b2da3256\nBrokerExampleAboutFrm.dfm | 09-17-1997 | 17:54:00 | | 2212 | 5602350d\nBrokerExampleAboutFrm.PAS | 09-17-1997 | 17:54:00 | | 883 | a61f16f0\nBrokerExampleFrm.dfm | 09-17-1997 | 18:13:10 | | 7266 | a3e77c7b\nBrokerExampleFrm.PAS | 09-17-1997 | 18:13:12 | | 8746 | 7db22f31\n \n \n \nC:\\Program Files\\VISTA\\BDK32\\SAMPLES\\VB5EGCHO\n \nBAPI32.bas | 08-20-1997 | 17:50:44 | | 1899 | 3f2f8fe1\negcho.bas | 08-11-1997 | 11:03:44 | | 148 | 3dce23c9\nEgcho.frm | 08-11-1997 | 11:30:50 | | 28311 | 6a6e4e98\negcho.vbp | 08-14-1997 | 11:08:26 | | 1831 | 1c61491a\n \nend of file list\nIMPORTANT NOTES:\n \n \nThis patch consists of two parts:\n \n1. Packman message containing the XWB*1.1*24 KIDS build. The packman\nmessage simply updates the version multiple of the package.\n \n2. Updated BDK (programmer client workstation software). This version of\nthe BDK supports Delphi V. 5 and Delphi V. 4. DELPHI V. 3 IS NO LONGER\nSUPPORTED.\n \nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE ON END-USER\nDue to version-dependent code, a problem was recently encountered that is\nCLIENT WORKSTATIONS. If you are not using the BDK in any local or\nnational development, you do not need to retrieve the Broker's programmer\nclient workstation software. The software does not update the Broker\nsoftware that is running on end-user client workstations. Further, no new\nfunctionality is added to the BDK by this patch.\n \nThe software distribution includes:\n \nFILE NAMES DESCRIPTION Bytes \nXWB1_1P24PG.EXE BDK Self-Installing Executable 2,117,952\nassociated with reading the Window's registry in programs compiled with\nXWB1_1P14IG.PDF Installation Guide 171,945\nXWB1_1RM.TXT Readme text file 16,213*\n \n*The size of this file will change in the future as additions are made.\n \nNote: Use Binary mode for .PDF, and .EXE files.\n Use ASCII mode for .TXT file.\n \nTo obtain the updated BDK, use FTP to retrieve the software from one of\nthe following OI Field Offices' ANONYMOUS.SOFTWARE directories:\nDelphi V. 5. Because a conditional test was specifically looking for\n \n OI FIELD OFFICE FTP Address \nHines 152.129.1.110 (isc-chicago.domain.ext)\nAlbany 152.127.1.5 (isc-albany.domain.ext) \nSalt Lake City 152.131.2.1 (isc-slc.domain.ext)\n \n \nPACKAGE DEPENDENCIES:\n \nA Package may have been defined to require the Broker package. Patch\nDelphi V. 4-based applications, Delphi V. 5-based applications ended up\nXWB*1.1*24 changes the identity of the Broker design-time package. If you\ntry to install a package into the Delphi IDE that requires the Broker, you\nmay receive an error message like:\n \n Can't load package <Package1>.\n One of the library files needed to run this package cannot\n be found.\n \nTo resolve this problem:\n \nusing Broker code for Delphi V. 3. This can result in users having\n1. Open the dpk file associated with that package.\n \n2. Delete the reference to the old version of the Broker in the Requires\nsection.\n \n3. Add a reference to the new design-time Broker package (XWB_Dxx) into\nthe Requires section.\n \n4. Recompile and install the package.\n \n\n
\nNOIS: WCO-0300-50643\n \n Want KIDS to INHIBIT LOGONs during the install? YES//\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n\n 8. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n\n 9. Restart the Broker Listener on the Server:\n The calls to RTL were remove from logging the broker code. If Response Time \n a. Log into your M server\n b. Enter the following at the M prompt:\n\n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n\n============================================================================\n\n Logging is on, then the RPC will still be logged.\n\n Worked with the NVS to use the correct call to see that Broker connection\n got registered as client server so they all connections from one IP address\n could share Cache one licenses.\n \n A change was made to check the IP address of the PEER and to use that if\n different than the IP address in the header. This allows the use of NAT\n XWBTCPC\n translation.\n\nNOIS: CLL-0301-40678\n JAC-0301-70277\n XWBTCPC\n If an application Newed the XWBOS variable and then experienced an error,\n it would cause a second error in the error module of the Broker. This \n has been fixed by setting the value of XWBOS in the error trap module.\n\nNOIS: KAN-0201-40992\n Under Cache 3.2 error trapping conditions, the return of control wouldn't go \n XWBTCPL\n If a connection was made to the RPC Broker listener port that failed to \n send the correct information, this could cause the listener to fail to \n detect other connection requests. This has been fixed by changing the \n timeout on the read and resetting the port if this happens.\n\nRoutine Summary\nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n to the correct routine, resulting in a run-away job. Fixed by being explicit \n\n Checksum\nRoutine Old New 2nd Line\nXWBBRK 5912545 5552318 **2,4,10,16**\nXWBTCPC 7568523 7379419 **2,5,4,6,9,16**\nXWBTCPL 9128997 10414009 **1,7,9,15,16**\n\nList of preceding patches: 10, 15\nSites should use CHECK^XTSUMBLD to verify checksums.\n\n about the routine to return to.\n=========================================================================\nInstallation:\n\n 1. During the installation, do not run any RPC-Broker-based Client/Server\n software (e.g., CPRS, PCMM, BCMA). No Broker-based client/server \n software should be running while installing this patch on the \n server. You can identify these jobs by checking the system status \n and verifying if any XWBTCPC routines are running (i.e., Broker \n Handler). If you find any of these jobs running on the system, \n notify users to logoff or FORCEX the jobs. Active users may get \n \n NOSOURCE or CLOBBER errors. \n \n 2. Stop the Broker Listener on the server. Do this by first \n checking the system status, then verifying if the XWBTCPL \n routine is running (i.e., Broker Listener). If you find this \n routine running on your system, STOP IT. To stop the Broker \n Listener, do the following: \n \n a. Log into your M server. \n b. Enter the following command at the M prompt: \n When a READ or WRITE error occurs, the error trap code was trying to send \n \n >D STOP^XWBTCP(Listener port) \n (Typically, the Listener port is 9200) \n\n 3. Stop any users that are using Broker applications. This applies\n to any job in XWBTCPC or in CPRS.\n \n 4. Broker routines are not usually mapped on systems that allow mapping.\n So, you will probably not have to disable mapping.\n\n an error message to the client. This caused an error, which resulted in a \n 5. Use the Kernel Option 'INSTALL/CHECK MESSAGE' located on the \n PackMan menu. This option will load the KIDS package onto your \n system.\n\n 6. The patch has now been loaded into a Transport global on your\n system. Now you need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n second error being logged.\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 7. On the KIDS Installation menu, use the option Install Package(s).\n Respond to the prompts as follows:\n \n Select INSTALL NAME: XWB*1.1*16\n ==========\n \n\n
\nSubject: Encryption, Data Collection, Agent\n \nRoutine Information:\n====================\nRoutine Name:\n \n - XWBBRK\n \nRoutine Checksum:\nOLD: 4495672\nNEW: 4562161\n \nThis patch addresses 3 problems with RPC Broker v1.1\n \nRoutine Name:\n - XWBTCPC\n \nRoutine Checksum:\nOLD: 8204793\nNEW: 8099567\n \n \nRoutine Name:\n \n - XWBCAGNT\n \nRoutine Checksum:\nOLD: 2022848\nNEW: 2022488\n \nEncrypted Literal:\n A leading period (".") in a LITERAL parameter can cause a pattern match\n failure in RPCs. This type of literal is common when data is encrypted.\n The failure only occurs with RPCs which combine multiple literals and an\n array. This fix addresses the needs of NOIS WAS-0398-22800\n \n \n \n \nData Collection Switch:\n The original version of the broker automatically collected Response Time\n data. This was done to fulfill a request from Capacity Management since\n at the time, no baseline data existed for Vista client-server\n Applications. The broker will not do this any longer. Collection will\n be ontrolled by the use of the Capacity Management tools, allowing the\n site to decide when to turn data collection on or off. This fix addresses\n the needs of NOIS BRX-0498-11768 and HUN-0498-21137.\nCategory: \n \n***NOTE:\n The Capacity Management option "Enable/Disable RT Logging" looks at the\n old Kernel Site Parameters file instead of the new Kernel System\n Parameters file. So, using this option will not enable/disable the RTM.\n The Capacity Management team is aware of this and are going to issue a\n patch. In the meantime, a site has to use FileMan to manually turn the\n RTM on/off in file 8989.3 (Kernel System Parameter). The field is the\n LOG SYSTEM RT and its within the VOLUME SET multiple.\n Example:\n \n \n Select OPTION: ENTER OR EDIT FILE ENTRIES \n Select KERNEL SYSTEM PARAMETERS DOMAIN NAME: 1 KERNEL.ISC-SF.DOMAIN.EXT\n Select VOLUME SET: KDE// \n LOG SYSTEM RT?: NO// Y YES <<==\n \n \n \n10 Second Network Timeout in Client Agent:\n A 30 second timeout is being switched to 10 for network communications\n - Routine\n with client agent. In the event of network problems, this should prevent\n delays to exceed minutes in communications between the server and the\n workstation client agent. No current NOIS addresses this, this effect\n was discovered by the SF CIOFO.\n \n \n==========================================================================\n INSTALLATION:\n \n \n \n 1. DSM sites - Some of these routines MAY BE mapped, so you will need\n to disable mapping for the effected routines. Broker routines do not\n need to be mapped.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n \n options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n 4. All RPC Broker users should log off.\n Since no changes are made to the main server routines, sites do not\nDESCRIPTION:\n need to shut down the listener jobs, BUT sites may choose to do if it\n make it easier to control users trying to log on during the routine\n update.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*2'\n =========\n \n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n=============\n other CPUs?'. Enter the names of your Compute and Print server(s).\n \n 7. DSM Sites, after patch has installed, rebuild your map set.\n \n 8. Restart the Broker Listener if necessary.\n \n==========================================================================\n \n \n \n\n\nTest sites: San Diego, Seattle, and El Paso\ndata views" are available to the user showing patient information\n \n 3. AXP/DSM SITES: Review your mapped routine set. If any of the\n routines patched by XWB*1.1*27 are mapped, they should be\n removed from the mapped set at this time.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu to\n load the KIDS package onto your system.\n \n 5. Step 4 loads a transport global on your system. Before actually\n installing the software contained in this transport global, you\ncollected real-time from remote sites. The collection of real-time data\n should take the time to review what will happen when the\n software is installed, and take other actions such as backing\n up the software that is about to be overwritten. The menu options\n shown below should be used when performing review and backup tasks.\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \nfrom remote sites also occurs from other sites such as the Government\n 6. Patch XWB*1.1*27 is now loaded into a transport global on your\n system. The next step is to use KIDS to install the\n transport global. This is done using the 'Installation' menu's\n 'Install Package(s) [XPD INSTALL BUILD]' menu option. When\n using this menu option to install the patch build, you will be\n asked several questions. The questions, and the answers you\n should supply, are shown below.\n \n INSTALL NAME: <XWB*1.1*27>\n Want KIDS to INHIBIT LOGONS during the install? <NO>\nComputer-based Patient Record (GCPR), and other packages such as Bar-code\n Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? <NO>\n \n 7. AXP/DSM SITES: After the patch has been installed, rebuild\n your map set, if necessary.\n \n 8. Restart the Broker Listener on the Server. From the M prompt,\n enter the following command:\n \n >D STRT^XWBTCP(LISTENER-PORT)\nMedication Administration (BCMA), and Integrated Billing (IB). This data\n \n Remember to substitute the actual port number for\n 'LISTENER-PORT'. (See step #2 above.)\ncollection occurs as the result of calls to a RPC Broker - HL7 bridge\nroutine.\n \nWhen calls for remote site data are made by these packages to the HL7\npackage, the requests are placed in a message queue awaiting processing.\n \nA background job processes the entries in the message queue, collects the\ndata from the remote site, and makes the remote site's data available to\nlocal users.\n \nPresently, there is only one message queue to a given site. When users\nmake multiple calls to the same remote site, the messages are processed\nin the order they were queued, each one finishing before the next request\nis started and processed. If any of the requests in a processing queue\ntake a long time to process, or if there are a large number of requests\nwaiting processing, inordinately high delays are seen before the remote\nNOIS: None\ndata is available to local users.\n \nPrior to this patch, processing of requests to the HL7 package for\nremote data made by GCPR and CPRS, was performed synchronously - in order\nof time of request - each job finishing before the next job started. This\npatch enables asynchronous processing - multiple jobs running at the same\ntime.\n \n \nREQUEST TIMEOUTS\n \n \nWhen requests are made to remote sites for data, there is a limit to how\nlong the calling procedure will wait for a reply. When a request for\nremote data is not returned within the length of time specified in the\nACK TIMEOUT field of the logical link used for the remote request, the\ncall fails. If your site experiences this problem, you may need to\nincrease the value of the ACK TIMEOUT field for the involved logical\nlink in increments of 30 to 60 seconds until the problem stops. (VACIO\nis one link that has shown a need for a longer timeout.) Refer to 'How\nto edit Links', section 2.2 in the Health Level Seven Site Manager\nRequired builds: XWB*1.1*22\nDeveloper manual, for additional help in editing links.\n \n \nThe routines XWB2HL7 and XWB2HL7C are included in this patch. The first\nand second lines of these routines are shown below.\n \n XWB2HL7 ;ISF/RWF - Remote RPC via HL7 ;8/27/01 09:31\n ;;1.1;RPC BROKER;**12,18,20,22,27**;Mar 28, 1997\n XWB2HL7C ;ISF/RWF - Remote RPC via HL7 ;12/27/01 15:33\n ;;1.1;RPC BROKER;**27**;Mar 28, 1997\n \n \nThe VA Kernel checksums for the routines included in this patch\n(calculated using CHECK^XTSUMBLD) are listed below.\n \n Checksum Checksum\n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== =====================\n XWB2HL7 10783627 10960487 12,18,20,22,27\n XWB2HL7C -------- 1022701 27\n \nPATCH DESCRIPTION\nSites should use CHECK^XTSUMBLD to verify checksums after patch\ninstallation.\n \n Installation Instructions:\n ==========================\n 1. Do not run any RPC Broker-based Remote Data View (RDV) software\n (e.g., CPRS, PCMM) during the installation of this patch, and do\n do not allow any incoming HL7 RDV messages. To identify these jobs,\n check the system status, locating all running XWBTCPC (Broker\n Handler) routines. If any XWBTCPC routines are running,\n \n notify the users associated with the running routines to log off.\n If it is not possible to contact users, it will be necessary to\n stop the jobs manually, using a utility such as FORCEX on VMS\n systems, or RESJOB on Cache systems. (Users may get NOSOURCE or\n CLOBBER error messages if this patch is installed while they are\n working.)\n \n 2. Stop the Broker Listener on the server. Check the system status\n and verify if the XWBTCPL routine is running. (i.e., Broker\n Listener). If it is running, stop it using the command shown\nWhen using the GUI Computerized Patient Record System (CPRS), "remote\n below.\n \n From the M prompt, enter:\n \n >D STOP^XWBTCP(LISTENER-PORT)\n \n When stopping the listener using the above command, substitute\n the actual port number for 'LISTENER-PORT'. Typically, the\n listener port is 9200. (If the listener port is 9200, the\n actual command would be 'D STOP^XWBTCP(9200)'.)\n\n
\nThis Patch Addresses the Following NOIS Call:\nsites' local NEW PERSON files (#200).\n\nPatch Solution:\n---------------\n\nA new field named SUPPRESS RDV USER SETUP (#.1) has been added to the REMOTE \nPROCEDURE file (#8994). It regulates the addition of Remote Users to sites' \nlocal NEW PERSON files for the RDV-based RPCs. This new field contains either \none of the following two values:\n\n=============================================\n 1. NO (default value) -- The Remote User will be added to the site's local \n NEW PERSON file.\n \n 2. YES -- The Remote User will NOT be added to the NEW PERSON file and the \n DUZ will be set to the Postmaster.\n \n \nRoutine XWB2HL7 was changed with patch XWB*1.1*22.\n\n=========================================================================\n1. WIC-0701-42695\nInstallation:\n \n 1. There are no routines in this patch. The Broker does NOT\n need to be stopped. Users can remain on the system.\n\n 2. Use the Kernel Option 'INSTALL/CHECK MESSAGE' located on the \n PackMan menu. This option will load the KIDS package onto your \n system.\n\n 3. The patch has now been loaded into a Transport global on your\n\n system. Now you need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n\n 4. On the KIDS Installation menu, use the option Install Package(s).\nProblem Statement:\n Respond to the prompts as follows:\n \n Select INSTALL NAME: XWB*1.1*25\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n------------------\n\n============================================================================\n\nIntegrated Billing (IB) has released a patch that uses the RPC Broker Remote \nData View (RDV) RPCs to collect data from remote systems. This caused a \nsignificant increase in the number of Remote Users (i.e., visitors) added to \n\n
\nThis patch provides silent login functionality in the Broker. Any GUI\nby the current application.\n Unit <unit1> was compiled with a different version of <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\nthat, with regards to the version of the BDK you are about to install:\n \na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible.\n \nc) You have the source (.pas, .dfm, .dpk, etc.) files available so that\n \nthe component can be recompiled successfully. If you're using the\nFileMan Delphi Components (FMDC), please note that the FMDC source code\nincludes references to RPC Broker Development Kit (BDK) code. When you\ninstall a new version of the BDK, you will need to recompile the FMDC.\n As of patch FMDC*1.0*1, source code for FMDC is provided, allowing you\nto recompile FMDC if necessary. For instructions on how to recompile FMDC,\nplease refer to FMDC*1.0*2.\n \nINSTALLATION:\n \n This patch also provides support for Enterprise Single Sign-On using an\nServer Side:\n============\n \nUse the following instructions in installing this server-side RPC Broker\npatch. Do NOT follow the M Server Installation Instructions in the RPC\nBroker Installation Guide to install the server portion of this patch.\n \nNo routines or other package components are added or modified on the\nserver by this patch.\n \nAuthentication Proxy when it becomes available.\n1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option\nwill load the KIDS (Kernel Installation and Distribution System) package\nonto your system. \n \n2. On the KIDS menu, under the 'Installation' menu, use the following\noption:\n Install Package(s) 'XWB*1.1*13'\n ==========\n \nAnswer the install questions like this:\n \n \nWant KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nClient Side:\n============\n \nPlease follow the instructions in the most recent Broker 1.1 Installation\nGuide.\n Since mechanisms are provided for a silent (dialog free) sign-on for the\n \nThe following list gives the specific attributes including size\nand CRC-32 for all of the files installed on the client\nusing the installation program XWB1_1P13PG.EXE.\n \n \n Date Time Attrib Bytes CRC-32 Filename\n---------- -------- ------ ----------- -------- --------\n \nC:\\Program Files\\vista\\BDK32\nRPCBroker, it may be used in situations where dialogs are not desirable. \n03/24/1999 09:03:34 A----- 327,680 D13C4BCE BrokerProgPref.exe\n08/28/2001 14:47:48 A----- 61,357 053E8CD1 Brokerprogpref.hlp\n01/26/1999 11:47:56 A----- 513,536 324B2F34 ServerList.exe\n09/16/1997 10:28:02 A----- 8,341 6FF7A68B Serverlist.hlp\n \nC:\\Program Files\\vista\\BDK32\\D4\n05/03/2002 11:41:38 A----- 3,211 7EBB75C6 AddServer.dcu\n03/01/2002 12:42:38 A----- 1,060 5A4B54B0 AddServer.dfm\n05/03/2002 11:41:38 A----- 5,554 1502199A APi.dcu\n05/03/2002 11:41:38 A----- 3,118 8CF3150A fConfirmMapping.dcu\nTo further support this, control of whether dialogs are shown for errors\n04/02/2002 11:43:32 A----- 1,006 E055A556 fConfirmMapping.dfm\n05/03/2002 11:41:38 A----- 3,504 CA35111D frmSignonMessage.dcu\n03/05/2002 17:48:52 A----- 2,805 A2BCFA3C frmSignonMessage.dfm\n05/03/2002 11:41:38 A----- 3,337 5D120C0B fRPCBErrMsg.dcu\n01/24/2002 18:21:20 A----- 495 85FF429E fRPCBErrMsg.dfm\n05/03/2002 11:41:38 A----- 4,500 86ACB9BD fRPCBTimer.dcu\n01/23/2002 14:45:04 A----- 1,130 B880B883 fRPCBTimer.dfm\n05/03/2002 11:41:38 A----- 3,445 170F31B4 Hash.dcu\n05/03/2002 11:41:38 A----- 17,584 19C9A091 Loginfrm.dcu\n02/15/2002 10:24:00 A----- 11,849 E398882A Loginfrm.dfm\ndetected is also supported with the property ShowErrorMsgs. The default\n05/03/2002 11:41:38 A----- 1,287 FD26D493 MFunStr.dcu\n05/03/2002 11:42:14 A----- 4,860 B65899DB RpcbEdtr.dcu\n05/03/2002 11:41:38 A----- 10,935 29B2836D Rpcberr.dcu\n07/18/2001 13:10:26 A----- 999 407D7B76 Rpcberr.dfm\n05/03/2002 11:41:38 A----- 8,748 E64FAADB Rpcconf1.dcu\n07/18/2001 13:10:26 A----- 4,198 B1EDACB5 Rpcconf1.dfm\n05/03/2002 11:41:38 A----- 11,340 7608F41E RpcNet.dcu\n07/18/2001 13:10:26 A----- 281 8B878EB9 Rpcnet.dfm\n05/03/2002 11:41:38 A----- 5,473 7D124F20 RpcSLogin.dcu\n05/03/2002 11:41:38 A----- 7,460 402A5C02 seldiv.dcu\nvalue for this property is semRaise which will raise an error message in a\n08/14/2001 14:50:26 A----- 3,355 DEE29911 SelDiv.dfm\n05/03/2002 11:41:38 A----- 9,751 F36A8BF3 Sgnoncnf.dcu\n07/18/2001 13:10:28 A----- 2,170 8EADA139 Sgnoncnf.dfm\n05/03/2002 11:41:38 A----- 4,075 837E23BB Splvista.dcu\n07/18/2001 13:10:30 A----- 231,571 9BAF7C4E Splvista.dfm\n05/03/2002 11:41:38 A----- 26,988 A3327CA3 Trpcb.dcu\n05/03/2002 11:41:38 A----- 9,604 D145A271 VCEdit.dcu\n07/18/2001 13:10:30 A----- 2,939 53C32B50 Vcedit.dfm\n05/03/2002 11:41:38 A----- 12,836 7317C056 WSockc.dcu\n05/03/2002 11:41:38 A----- 3,211 332A7436 xuesap_TLB.dcu\napplication that uses the Broker may now be able to login to an M Server\ndialog box. If this is not desirable, the value should be set to\n05/03/2002 11:42:14 A----- 900 169D53F5 XWBReg.dcu\n05/03/2002 11:41:38 A----- 38,806 03477064 XWBRich20.dcu\n05/03/2002 11:41:38 A----- 6,842 C00E694E Xwbut1.dcu\n05/03/2002 11:42:28 A----- 3,946 59384EB0 XWB_D40.dcu\n05/03/2002 11:41:38 A----- 3,594 A9DE995C XWB_R40.dcu\n \nC:\\Program Files\\vista\\BDK32\\D5\n05/03/2002 10:57:44 A----- 3,312 7157FA1E AddServer.dcu\n03/01/2002 12:42:38 A----- 1,060 5A4B54B0 AddServer.dfm\n05/03/2002 10:57:44 A----- 5,516 FCB56F2B APi.dcu\nsemQuiet. However, if this value is chosen, the application MUST check\n05/03/2002 10:57:44 A----- 3,219 2B54D0F7 fConfirmMapping.dcu\n04/02/2002 11:43:32 A----- 1,006 E055A556 fConfirmMapping.dfm\n05/03/2002 10:57:44 A----- 3,605 912BE386 frmSignonMessage.dcu\n03/05/2002 17:48:52 A----- 2,805 A2BCFA3C frmSignonMessage.dfm\n05/03/2002 10:57:44 A----- 3,438 05361234 fRPCBErrMsg.dcu\n01/24/2002 18:21:20 A----- 495 85FF429E fRPCBErrMsg.dfm\n05/03/2002 10:57:44 A----- 4,601 F674C379 fRPCBTimer.dcu\n01/23/2002 14:45:04 A----- 1,130 B880B883 fRPCBTimer.dfm\n05/03/2002 10:57:44 A----- 3,407 A7BD03D4 Hash.dcu\n05/03/2002 10:57:44 A----- 17,574 6E917952 Loginfrm.dcu\nthe RPCBError property for information about any errors encountered\n02/15/2002 10:24:00 A----- 11,849 E398882A Loginfrm.dfm\n05/03/2002 10:57:44 A----- 1,278 22543969 Mfunstr.dcu\n05/03/2002 10:58:46 A----- 4,905 6B78EED7 Rpcbedtr.dcu\n05/03/2002 10:57:44 A----- 11,038 6AC4DDC4 Rpcberr.dcu\n07/18/2001 13:10:26 A----- 999 407D7B76 Rpcberr.dfm\n05/03/2002 10:57:44 A----- 8,854 426E7C06 Rpcconf1.dcu\n07/18/2001 13:10:26 A----- 4,198 B1EDACB5 Rpcconf1.dfm\n05/03/2002 10:57:44 A----- 11,375 7440A453 Rpcnet.dcu\n07/18/2001 13:10:26 A----- 281 8B878EB9 Rpcnet.dfm\n05/03/2002 10:57:44 A----- 5,600 FCCAAFBE RpcSLogin.dcu\nfollowing EVERY broker call. The application may also set the\n05/03/2002 10:57:44 A----- 7,580 304030AE SelDiv.dcu\n08/14/2001 14:50:26 A----- 3,355 DEE29911 SelDiv.dfm\n05/03/2002 10:57:44 A----- 9,884 F5A23097 Sgnoncnf.dcu\n07/18/2001 13:10:28 A----- 2,170 8EADA139 Sgnoncnf.dfm\n05/03/2002 10:57:44 A----- 4,176 F09335F0 Splvista.dcu\n07/18/2001 13:10:30 A----- 231,571 9BAF7C4E Splvista.dfm\n05/03/2002 10:57:44 A----- 26,741 DA37941B Trpcb.dcu\n05/03/2002 10:57:44 A----- 9,776 C32D8E3E VCEdit.dcu\n07/18/2001 13:10:30 A----- 2,939 53C32B50 Vcedit.dfm\n05/03/2002 10:57:44 A----- 12,884 36051FFD WSockc.dcu\nOnRPCBFailure property with a method to be called in the event an error is\n05/03/2002 10:57:44 A----- 3,203 E9A3B39E xuesap_TLB.dcu\n05/03/2002 10:58:46 A----- 892 EF9D7E60 XWBReg.dcu\n05/03/2002 10:57:44 A----- 38,761 4109D6D2 XWBRich20.dcu\n05/03/2002 10:57:44 A----- 6,854 BA592D46 Xwbut1.dcu\n05/03/2002 10:58:50 A----- 4,229 17A82F92 XWB_D50.dcu\n05/03/2002 10:57:44 A----- 3,810 B80172F1 XWB_R50.dcu\n \nC:\\Program Files\\vista\\BDK32\\D6\n05/03/2002 11:46:36 A----- 3,470 0BAC17B5 AddServer.dcu\n03/01/2002 12:42:38 A----- 1,060 5A4B54B0 AddServer.dfm\nencountered. This method accepts an RPCBroker instance as an argument so\n05/03/2002 11:46:36 A----- 5,764 211F36D8 APi.dcu\n05/03/2002 11:46:36 A----- 3,377 619EF0D7 fConfirmMapping.dcu\n04/02/2002 11:43:32 A----- 1,006 E055A556 fConfirmMapping.dfm\n05/03/2002 11:46:36 A----- 3,763 F2B0B888 frmSignonMessage.dcu\n03/05/2002 17:48:52 A----- 2,805 A2BCFA3C frmSignonMessage.dfm\n05/03/2002 11:46:36 A----- 3,596 5FF3BB8F fRPCBErrMsg.dcu\n01/24/2002 18:21:20 A----- 495 85FF429E fRPCBErrMsg.dfm\n05/03/2002 11:46:36 A----- 4,765 3BF1C6A4 fRPCBTimer.dcu\n01/23/2002 14:45:04 A----- 1,130 B880B883 fRPCBTimer.dfm\n05/03/2002 11:46:36 A----- 3,513 254D85AA Hash.dcu\nthat it may obtain the information in the RPCBError property.\n05/03/2002 11:46:36 A----- 17,956 1C54586E Loginfrm.dcu\n02/15/2002 10:24:00 A----- 11,849 E398882A Loginfrm.dfm\n05/03/2002 11:46:36 A----- 1,422 68CE9C83 Mfunstr.dcu\n05/03/2002 11:46:54 A----- 5,176 35722506 Rpcbedtr.dcu\n05/03/2002 11:46:36 A----- 11,240 0CF2DEFA Rpcberr.dcu\n07/18/2001 13:10:26 A----- 999 407D7B76 Rpcberr.dfm\n05/03/2002 11:46:36 A----- 9,114 A4B5C2D4 Rpcconf1.dcu\n07/18/2001 13:10:26 A----- 4,198 B1EDACB5 Rpcconf1.dfm\n05/03/2002 11:46:36 A----- 11,832 36D0D0D7 Rpcnet.dcu\n07/18/2001 13:10:26 A----- 281 8B878EB9 Rpcnet.dfm\n \n05/03/2002 11:46:36 A----- 5,812 6A83D8D0 RpcSLogin.dcu\n05/03/2002 11:46:36 A----- 7,766 61179F74 SelDiv.dcu\n08/14/2001 14:50:26 A----- 3,355 DEE29911 SelDiv.dfm\n05/03/2002 11:46:36 A----- 10,107 B6DDFE46 Sgnoncnf.dcu\n07/18/2001 13:10:28 A----- 2,170 8EADA139 Sgnoncnf.dfm\n05/03/2002 11:46:36 A----- 4,334 D16DC224 Splvista.dcu\n07/18/2001 13:10:30 A----- 231,571 9BAF7C4E Splvista.dfm\n05/03/2002 11:46:36 A----- 27,400 3A115982 Trpcb.dcu\n05/03/2002 11:46:36 A----- 10,048 04A28CC8 Vcedit.dcu\n07/18/2001 13:10:30 A----- 2,939 53C32B50 Vcedit.dfm\nThis patch also fulfills the following E3Rs:\n05/03/2002 11:46:36 A----- 14,008 3BBAA3BE WSockc.dcu\n05/03/2002 11:46:36 A----- 3,232 50BCB332 xuesap_TLB.dcu\n05/03/2002 11:46:54 A----- 934 EA790E07 XWBReg.dcu\n05/03/2002 11:46:36 A----- 41,783 E2E9B7C1 XWBRich20.dcu\n05/03/2002 11:46:36 A----- 7,250 EF42A89C Xwbut1.dcu\n05/03/2002 11:47:02 A----- 4,936 3AD2612D XWB_D60.dcu\n05/03/2002 11:47:02 A----- 4,311 993C794A XWB_R60.dcu\n \nC:\\Program Files\\vista\\BDK32\\Help\n05/06/2002 11:01:42 A----- 2,733 003146A6 broker.als\n 11265, Allowing Access and Verify Codes to be Passed\n05/06/2002 10:22:22 A----- 175 6FD0E64D broker.cnt\n05/01/2002 13:07:56 A----- 1,371,098 59078E96 Broker.hlp\n05/06/2002 10:21:48 A----- 5,895 584D535E broker.toc\n \n \nC:\\Program Files\\vista\\BDK32\\Samples\\BrokerEx\n12/17/2001 14:13:32 A----- 1,427 5A02EFAC BrokerExample.dof\n09/05/1997 17:37:48 A----- 640 B2DA3256 BrokerExample.dpr\n05/02/2002 15:47:28 A----- 792,576 564C54CC BrokerExample.exe\n12/17/2001 14:13:14 A----- 876 483416C3 BrokerExample.res\nsilently (i.e. without any user dialog). The logins supported via the GUI\n 10668, Auto Signon for Instrument\n09/17/1997 17:54:00 A----- 2,212 5602350D BrokerExampleAboutFrm.dfm\n09/17/1997 17:54:00 A----- 883 A61F16F0 BrokerExampleAboutFrm.PAS\n03/26/2002 14:33:20 A----- 7,539 B2C0B964 BrokerExampleFrm.dfm\n03/26/2002 14:33:20 A----- 8,923 8A5BB648 BrokerExampleFrm.PAS\n \nC:\\Program Files\\vista\\BDK32\\Samples\\SilentSignOn (p13)\n11/29/2001 15:56:26 A----- 36,358 CA226130 frmVistAAbout.dfm\n11/29/2001 15:56:40 A----- 9,165 9886C601 frmVistAAbout.pas\n02/20/2002 11:48:12 A----- 2,123 113C64A2 fXWBAppHandle1.dfm\n02/20/2002 11:47:22 A----- 2,158 CAA37588 fXWBAppHandle1.pas\n 12800, Programmatic Login\n02/20/2002 11:55:14 A----- 1,493 DDE5120E fXWBAppHandle2.dfm\n02/20/2002 11:53:24 A----- 2,387 E509BF8F fXWBAppHandle2.pas\n02/20/2002 11:30:46 A----- 3,101 D18D7FEB fXWBAVCodes.dfm\n02/20/2002 11:34:48 A----- 2,962 E868A418 fXWBAVCodes.pas\n02/20/2002 11:37:52 A----- 3,532 0342E8B4 fXWBOnFail.dfm\n02/20/2002 11:38:22 A----- 2,815 21A7384C fXWBOnFail.pas\n09/24/2001 09:12:30 A----- 2,179 B175057C ReadMeForSamples.txt\n02/20/2002 11:47:22 A----- 1,382 5B3428BA XWBAppHandle1.dof\n09/24/2001 08:55:02 A----- 211 569EEF61 XWBAppHandle1.dpr\n04/02/2002 12:07:56 A----- 638,464 62E61FE8 XWBAppHandle1.exe\n \n02/20/2002 11:53:24 A----- 1,373 C262DAD6 XWBAppHandle2.dof\n09/24/2001 08:56:20 A----- 211 3795C783 XWBAppHandle2.dpr\n04/02/2002 12:08:12 A----- 638,976 49DBE496 XWBAppHandle2.exe\n02/20/2002 11:33:28 A----- 1,457 141A1A7B XWBAVCodes.dof\n02/20/2002 11:29:58 A----- 298 7BD8DA83 XWBAVCodes.dpr\n04/02/2002 12:08:24 A----- 618,496 280ACDED XWBAVCodes.exe\n02/20/2002 11:33:18 A----- 1,732 704ABF98 XWBAVCodes.res\n02/20/2002 11:42:06 A----- 1,480 A5F32F63 XWBOnFail.dof\n09/24/2001 08:41:32 A----- 220 7A9C940F XWBOnFail.dpr\n04/02/2002 12:08:40 A----- 640,000 A404A20F XWBOnFail.exe\nThe patch also resolves the following NOIS calls:\n \nC:\\Program Files\\vista\\BDK32\\Samples\\Vb5Egcho\n08/20/1997 17:50:44 A----- 1,899 3F2F8FE1 BAPI32.bas\n08/11/1997 11:03:44 A----- 148 3DCE23C9 egcho.bas\n08/11/1997 11:30:50 A----- 28,311 6A6E4E98 Egcho.frm\n04/29/2002 11:29:16 A----- 1,268 03E3DC91 egcho.vbp\n \nC:\\Program Files\\vista\\BDK32\\Source\n03/01/2002 12:42:38 A----- 1,060 5A4B54B0 AddServer.dfm\n01/30/2002 11:52:22 A----- 496 43B76701 AddServer.pas\n HIN-0300-41574, PROBLEM WITH F1 SHORTCUT FOR HELP IN GUI\n03/08/2002 17:20:18 A----- 6,720 87361A13 APi.pas\n04/02/2002 11:43:32 A----- 1,006 E055A556 fConfirmMapping.dfm\n04/02/2002 11:18:06 A----- 444 FF52F074 fConfirmMapping.pas\n03/05/2002 17:48:52 A----- 2,805 A2BCFA3C frmSignonMessage.dfm\n12/19/2001 13:18:02 A----- 1,122 0490D6BF frmSignonMessage.pas\n01/24/2002 18:21:20 A----- 495 85FF429E fRPCBErrMsg.dfm\n01/25/2002 11:06:48 A----- 631 3FC90CC6 fRPCBErrMsg.pas\n01/23/2002 14:45:04 A----- 1,130 B880B883 fRPCBTimer.dfm\n01/25/2002 14:48:52 A----- 1,691 ABDDBAD6 fRPCBTimer.pas\n07/18/2001 13:10:24 A----- 3,642 15F82810 Hash.pas\n HOU-0399-72697, Signing on via Broker\n11/05/2001 10:37:48 A----- 2,701 81304061 IISBase.inc\n02/15/2002 10:24:00 A----- 11,867 CC8CA856 Loginfrm.dfm\n04/30/2002 14:43:40 A----- 17,793 B3BD3B47 Loginfrm.pas\n07/18/2001 13:10:26 A----- 2,430 79AAC9E8 Mfunstr.pas\n11/05/2001 11:32:34 A----- 4,241 17C7491F Rpcbedtr.pas\n07/18/2001 13:10:26 A----- 999 407D7B76 Rpcberr.dfm\n01/25/2002 11:27:20 A----- 7,097 CC57B9CB Rpcberr.pas\n07/18/2001 13:10:26 A----- 4,198 B1EDACB5 Rpcconf1.dfm\n05/02/2002 13:20:14 A----- 7,373 EE6F6EB9 Rpcconf1.pas\n07/18/2001 13:10:26 A----- 281 8B878EB9 Rpcnet.dfm\n ISW-1299-22382, CPRS W/XWB*1.1*8\n08/27/2001 11:20:48 A----- 11,669 672990EF Rpcnet.pas\n08/17/2001 09:55:02 A----- 8,857 5181563A RpcSLogin.pas\n08/14/2001 14:50:26 A----- 3,355 DEE29911 SelDiv.dfm\n01/18/2002 14:52:28 A----- 7,570 893C9B76 SelDiv.pas\n07/18/2001 13:10:28 A----- 2,170 8EADA139 Sgnoncnf.dfm\n11/26/2001 11:52:44 A----- 7,294 D2536776 Sgnoncnf.pas\n12/27/2001 09:45:12 A----- 1,405 056B2027 ShowApp.pas\n07/18/2001 13:10:30 A----- 231,571 9BAF7C4E Splvista.dfm\n07/18/2001 13:10:30 A----- 2,373 AF07D43F Splvista.pas\n04/30/2002 14:41:18 A----- 55,442 3C6D2198 Trpcb.pas\n ISW-1299-21488, CPRS W/XWB*1.1*8\n07/18/2001 13:10:30 A----- 2,939 53C32B50 VCEdit.dfm\n11/21/2001 15:52:36 A----- 8,191 0781D595 VCEdit.pas\n05/01/2002 14:17:44 A----- 27,555 1C3B503E WSockc.pas\n08/30/2001 10:41:42 A----- 2,820 74887B7B Xuesap.tlb\n01/23/2002 14:03:38 A----- 7,404 E98BBBC3 xuesap_TLB.pas\n11/05/2001 11:35:12 A----- 939 69783674 XWBReg.pas\n07/18/2001 13:10:34 A----- 47,867 951FE0BD XWBRich20.PAS\n08/14/2001 14:23:38 A----- 9,764 3788FC47 Xwbut1.pas\n07/18/2001 13:10:30 A----- 924 35CE723F XWB_D40.dcr\n05/03/2002 11:42:36 A----- 1,409 9DF0350B XWB_D40.dof\n \n05/03/2002 11:42:08 A----- 690 3198F765 XWB_D40.dpk\n05/03/2002 11:42:06 A----- 1,700 139B5A20 XWB_D40.res\n07/18/2001 13:10:32 A----- 924 35CE723F XWB_D50.dcr\n05/03/2002 10:58:58 A----- 1,344 A4C42D47 XWB_D50.dof\n05/03/2002 10:58:42 A----- 687 7084EF60 XWB_D50.dpk\n05/03/2002 10:58:40 A----- 1,700 D699F3BC XWB_D50.res\n07/18/2001 13:10:32 A----- 924 35CE723F XWB_D60.dcr\n03/11/2002 13:29:54 A----- 1,412 5C4B00F4 XWB_D60.dof\n01/28/2002 10:15:52 A----- 690 7E3E24AC XWB_D60.dpk\n01/30/2002 08:30:16 A----- 1,680 BDAB593D XWB_D60.res\nIMPORTANT NOTES:\n05/03/2002 11:41:44 A----- 1,435 A08B013B XWB_R40.dof\n05/03/2002 11:41:28 A----- 1,630 45167A2B XWB_R40.dpk\n05/03/2002 11:41:26 A----- 1,700 331F3D38 XWB_R40.res\n05/03/2002 10:57:54 A----- 1,360 A3CD6F7F XWB_R50.dof\n05/03/2002 10:57:36 A----- 1,592 D52BFC75 XWB_R50.dpk\n05/03/2002 10:57:34 A----- 1,700 03A7F6F4 XWB_R50.res\n03/11/2002 13:29:28 A----- 1,530 75C50861 XWB_R60.dof\n03/11/2002 13:29:06 A----- 1,601 E7D594E6 XWB_R60.dpk\n01/30/2002 09:17:44 A----- 1,680 AAAB51DE XWB_R60.res\n \nare:\n \n \n \nIn the following $(DELPHI4), $(DELPHI5) and $(DELPHI6) represent the\nparent directory for Delphi4, Delphi5, and Delphi6 respectively, for which\nthe default would be C:\\Program Files\\Borland\\Delphi4 or Delphi5 or\nDelphi6.\n \n$(DELPHI4)\\Bin\n05/03/2002 11:42:28 A----- 24,576 BEE33AA5 XWB_D40.bpl\n05/03/2002 11:41:38 A----- 459,776 86E9CB85 XWB_R40.bpl\nThis patch consists of 2 parts:\n \n$(DELPHI4)\\Lib\n05/03/2002 11:42:28 A----- 8,587 F26659D6 XWB_D40.dcp\n05/03/2002 11:41:38 A----- 152,044 134854B1 XWB_R40.dcp\n \n$(DELPHI5)\\Programs\\Bpl\n05/03/2002 10:58:50 A----- 25,600 C96A468F XWB_D50.bpl\n05/03/2002 10:58:50 A----- 8,788 F1923ED5 XWB_D50.dcp\n05/03/2002 10:57:46 A----- 460,800 E7989BC6 XWB_R50.bpl\n05/03/2002 10:57:46 A----- 152,574 77306E5F XWB_R50.dcp\n \n \n$(DELPHI6)\\Programs\\Bpl\n05/03/2002 11:47:02 A----- 26,624 B088E557 XWB_D60.bpl\n05/03/2002 11:47:02 A----- 9,634 F003B974 XWB_D60.dcp\n05/03/2002 11:46:36 A----- 416,768 CFF242F6 XWB_R60.bpl\n05/03/2002 11:46:36 A----- 162,457 C4396637 XWB_R60.dcp\n \n \n \nThe following file, needed for correct display of help files\n1. Packman message containing the XWB*1.1*13 KIDS build. The packman\ngenerated with Robohelp, may be installed if it is not already\npresent. (WINNT may be replaced by WINDOWS)\n \nC:\\WINNT\\System32\n06/30/2000 14:47:16 A----- 1,048,576 641895FF roboex32.dll\n \n \n \nThe following files are installed by the Wise installer and may\nvary in size, CRC, etc., depending upon the selections made during\nmessage simply updates the version multiple of the package.\nthe installation.\n \n05/06/2002 14:44:32 A----- 26,779 B81F32D4 INSTALL.LOG\n06/25/1999 11:55:30 A----- 149,504 30FDD633 UNWISE.EXE\n \n2. Updated BDK (programmer client workstation software). This version of\nthe BDK supports Delphi 4, Delphi 5, and Delphi 6. \n \nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE ON END-USER\n1) setting the access code and verify code properties of the USER object\nCLIENT WORKSTATIONS. If you are not using the BDK in any local or\nnational development, you do not need to retrieve the Broker's programmer\nclient workstation software. The software does not update the Broker\nsoftware that is running at end-user client workstations.\n \nThe software distribution includes:\n \n FILE NAMES DESCRIPTION Bytes\n XWB1_1P13PG.EXE BDK Self-Installing Executable 4,416,873 \n XWB1_1P13IG.PDF Installation Guide 453,899 \nfor the RPCBroker so that no sign-on dialog displays (if the user is\n XWB1_1P13RM.TXT Readme text file 21,688\n XWB1_1P13DG.PDF Developer's Guide 502,143\n XWB1_1P13SM.PDF Systems Manual 708,711\n XWB1_1P13TM.PDF Technical Manual 350,314 \n \nNote: Use Binary mode for .PDF, and .EXE files. \n Use ASCII mode for .TXT file.\n \nTo obtain the updated BDK, use FTP to retrieve the software from one of\nthe following CIO Field Offices' ANONYMOUS.SOFTWARE directories:\nMulti-divisional, a division property may also be set); \n \n CIO FIELD OFFICE FTP Address \n Hines 152.129.1.110 (isc-chicago.domain.ext)\n Albany 152.127.1.5 (isc-albany.domain.ext)\n Salt Lake City 152.131.2.1 (isc-slc.domain.ext)\n \nPACKAGE DEPENDENCIES:\n \nA Package may have been defined to require the Broker package. Patch\nXWB*1.1*13 changes the identity of the Broker design-time package. If you\nand \ntry to install a package into the Delphi IDE that requires the Broker, you\nmay receive an error message like:\n \n Can't load package <Package1>.\n One of the library files needed to run this package cannot be found.\n \nTo resolve this problem, Open the dpk file associated with that package;\ndelete the reference to the old version of the Broker in the Requires\nsection; add a reference to the new design-time Broker package (XWB_Dxx)\ninto the Requires section; recompile and install the package.\n2) Obtaining a token which may be passed to an application being started \n \nBROKER-DEPENDENT COMPONENTS:\n \nWarning: Some components, such as the FileMan Delphi Components, reference\nthe TRPCBroker component. If you use such components for development, be\naware that installing a new version of the TRPCBroker component (i.e. a\nnew BDK) may cause incompatibilities in Delphi, resulting in a compile\nfailure of the unit containing the Broker-dependent component and the\nfollowing compilation error:\n \n\n
\nThe description for this patch may be found in the patch message or in \nthe patch module on Forum.\n\n
\nThe patch description may be found in the packman message or on Forum in\nthe patch module.\n\n
\nAssociated Patches:\n===========\nline of each of these routines now looks like:\n \n <tab>;;1.1;RPC BROKER;**[patch list]**; Mar 28, 1997\n \n \nRemote Procedure Calls\n======================\n \nTwo new RPCs will be exported with this package to be used as examples \nfor the purposes of testing the M-to-M Broker.\nThe M-to-M Broker provides a new implementation of the RPC Broker \n \n XWB M2M EXAMPLE LARRY \n XWB M2M EXAMPLE REF\n \n \nChecksums\n=========\nSites should use CHECK^XTSUMBLD to verify checksums. \n \n Routine Name Before Patch After Patch Patch List\nenabling the exchange of VISTA M-based data and business rules between \n ============ ============ =========== ==========\n XWBM2MC None 6758340 28\n XWBM2MS None 160268 28\n XWBM2MT None 7883957 28\n XWBRL None 3848552 28\n XWBRM None 3795059 28\n XWBRMX None 3053319 28\n XWBRPC None 10961081 28\n XWBRPCC None 5907709 28\n XWBUTL None 3238078 28\ntwo VISTA M servers, where both servers reside on the same, or on \n XWBVL None 1814637 28\n XWBVLC None 1920009 28\n XWBVLL None 3018372 28\n \n \n \nInstallation Instructions\n=========================\n \n>>>Users may remain on the system.\ndifferent VISTA M systems. It has been developed to provide Client/Server \n>>>TaskMan does *not* need to be stopped.\n \n 1. DSM sites - Some of these routines are usually mapped,\n so you will need to disable mapping for the affected routines.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\nfunctionality resident solely within the VISTA environment. The \n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\nrequesting server functions in the capacity of a "client." The server \n This patch can be queued and installed at any time.\n TaskMan can remain running.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*28'\n ==========\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n \nreceiving that request functions in the capacity of a "server." The \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\nClient/Server roles of each server can change depending on at what point \nin time each VISTA M server is making the request for data from it's \n \ncounterpart VISTA M server. \n \nThe requesting server and the receiving server can reside on the same, or \non different VISTA M systems. All M-to-M Broker client and server \nroutines are packaged in one KIDS build. This build will need to be \ninstalled on each VISTA system required for M-to-M Broker processing. \n \nFurther information is provided in a separate document, "M-to-M BROKER \nSupplemental Documentation, Patch XWB*1.1*28" This document can be \nobtained by using FTP from the appropriate Customer Service directory:\nXT*7.3*58 <<= must be installed BEFORE `XWB*1.1*28'\n \n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n ======================================================\n Albany 127.0.0.1 (ftp.fo-albany.domain.ext)\n Hines 127.0.0.1 (ftp.fo-chicago.domain.ext)\n Salt Lake City 152.131.2.1 (ftp.fo-slc.domain.ext)\n \n Host File Name: XWB1_1P28SP.PDF\n \nXU*8.0*225 <<= **ONLY FOR CACHE SITES** must be installed BEFORE \nThis document can also be downloaded from the Infrastructure \nDocumentation center web page:\n \n http://vista.domain.ext/vdl/#App128\n \n \nBackground\n==========\n \nVISTA Imaging requested the development of the M-to-M Broker to be used \n `XWB*1.1*28'\nto communicate between the M client on the VISTA Imaging Digital Imaging \nand Communications in Medicine (DICOM) Gateway and the M server on the \nmain VISTA Hospital Information System.\n \nThe VISTA Imaging DICOM Gateway architecture uses M software on a \nworkstation to create associations between newly acquired images and the \ncomputerized patient record. Previous to the development of the M-to-M \nBroker, the gateway system communicated with the main Hospital \nInformation System using the Distributed Data Processing (DDP) protocol, \nstored the acquired images on NT file servers and set database entries to \nXU*8.0*238 <<= must be installed BEFORE `XWB*1.1*28'\nreference them.\n \nProblems with DDP\n \n* Causes database inconsistencies.\n* Complete lack of security.\n* DDP is bound to MAC addresses.\n* DDP can be very slow on a busy HIS and/or network.\n* DDP runs very slowly in a WAN environment because of inherent network \n latencies.\n \n \nBecause of the database inconsistency problem, incidents of matching \nimages to the wrong patient occurred at one particular site.\n \nDDP doesn't have any security. M-to-M Broker uses many of the robust \nsecurity features implemented by the VISTA RPC Broker and Kernel \nsoftware. These security features are transparent to the end user and \nwithout additional impact on IRM.\n \nFor the VISTA Imaging DICOM Gateway, the M applications on separate VISTA \n \nsystems will be converted to use this new M-to-M Broker software to \ncommunicate to the main HIS. This will then eliminate the need for DDP \nwhere it is used.\n \n \nList of Test Sites\n==================\n \nVISTA Imaging System Team, Washington Office of Information Field Office \n(OIFO)\nDESCRIPTION\nVAMC San Francisco\n \nBlood Bank Team Coordination\n============================\nClearance = August 21, 2002 \n \n \nRoutine Summary\n===============\nThe following routines are included in this patch. The second\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XWB*1.1*32.\n\n
\nThere are two fixes included in this patch:\n2) A new TCP/IP entry point to start the M2M listener on a Cache/VMS \n \nInstallation Instructions\n=========================\n>>>Users may remain on the system.\n>>>TaskMan does *not* need to be stopped.\n \n 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 2. DSM sites - These routines should not be in any mapping.\nsystem in now available. The entry point is CACHEVMS^XWBVLL. This entry \n \n 3. The patch has now been loaded into a Transport global on your\n system. Now you need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nshould replace the entry point "UCX^XWBVLL" in the VMS-command file \n \n 4. Users can remain on the system. This patch can be loaded any\n non-peak time.\n TaskMan can remain running.\n \n 5. Installation will take less than 2 minutes.\n On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*41'\n ==========\n(refer to patch XWB*1.1*28 for more information on the VMS-command file \n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n \n 6. For Cache/VMS sites ONLY - Update the VMS-command file with this \n new entry for Cache/VMS. The following should be all on one line:\n $ccontrol session <configname> "-U" "<namespace>" "CACHEVMS^XWBVLL"\nand TCP/IP service to support the M2M listener). \n \nFor Cache/VMS sites: \n$ccontrol session "<configname>" "-U" "<namespace>" "CACHEVMS^XWBVLL"\n \nNotice above, that "configname" is the name of the configuration in the \n \nConfiguration manager that you start from the Cache cube. It is \nrecommended to enclose configname with double quotes ("). For example: \n$ccontrol session "ISFVA1" "-U" "VAH" "CACHEVMS^XWBVLL"\n \nThere are various ways to accomplish this for multiple nodes in a \ncluster, depending on how your site is set up. Here are two \npossibilities:\na. You can have different .com files for each node with each file \ncontaining its specific configname.\n \n1) The server-side code of the M2M Broker was not using the error \nb. Write some code so you can use the same .com file for all nodes. For \nexample: \n$ NODE=F$EDIT(F$GETSYI("SCSNODE"),"COLLAPSE,TRIM")\n$ assign 'f$trnlnm("SYS$NET")' SYS$NET\n$ ccontrol session "''NODE'" "-U" "VAH" "CACHEVMS^XWBVLL"\n \nNote: The NODE is enclosed with a double quotes ("), two single quotes \n(') then ending with one single quote (') and a double quote (").\n \nThis is assuming that the namespace is standard in the production nodes. \ntrapping correctly. The special variable $ETRAP is NEWed when it should \nFor test nodes that have a different namespace, it is recommended to use \nit's own .com file. \n \n \nPatch Tracking #: #37876991\n \n \nDocumentation for M-to-M Broker update, Patch XWB*1.1*41, is provided in \nthis patch description. In addition to this, the complete documentation \nsupplement for the M-to-M Broker, Patch XWB*1.1*28, can be found in the \nnot be (in routine XWBVLL). As a result the error logger can get into an\nVistA Anonymous directories and on the VistA Documentation Library (VDL) \nin the following two formats:\n \n XWB1_1P28SP.PDF XWB1_1P28SP.DOC\n \nThe preferred retrieval method to download the documentation for Patch \nXWB*1.1*28 is to FTP from the ANONYMOUS.SOFTWARE directory at: \n \n DOWNLOAD.VISTA.DOMAIN.EXT.\n \ninfinite loop. The error is caused when the socket between the client and\nThis transmits the file from the first available FTP server. Sites may \nalso elect to retrieve software directly from one of the following \nservers.\n \n OI Field Office FTP Address Directory\n ------------------------------------------------------------------\n Albany ftp.fo-albany.domain.ext ANONYMOUS.SOFTWARE\n Hines ftp.fo-hines.domain.ext ANONYMOUS.SOFTWARE\n Salt Lake City ftp.fo-slc.domain.ext ANONYMOUS.SOFTWARE\n \nthe server gets "broken". To resolve this issue $ETRAP is removed from \n Note: These files must be transferred in binary or IMAGE, not\n ASCII, mode. The VistA Documentation Library (VDL) contains\n all end-user manuals.\n \nThe Web address for the VistA Documentation Library (VDL), where you can \nalso obtain the documentation for M-to-M Broker, Patch XWB*1.1*28, is as \nfollows:\n \n http://www.domain.ext/vdl/Infrastructure.asp?appID=128\n \nthe list of NEWed variables in this instance.\n \n \n \nList of Test Sites\n==================\nVISTA Imaging System Team, Washington Office of Information Field Office \n(OIFO)\n \nRoutine Summary\nThe following routines are included in this patch. The second line of \n \neach of these routines now looks like:\n ;;1.1;RPC BROKER;**[Patch List]**;Mar 28, 1997\n \nChecksums:\nSites should use CHECK^XTSUMBLD to verify checksums\n \nRoutine Name Before Patch After Patch Patch List\n============ ============ =========== ==========\nXWBVLL 3018372 3252550 28,41\n \n\n\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XWB*1.1*35.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XWB*1.1*34.\n\n
\nDAY-0898-41587 XWBSEC Under CPRS when the DG routines call OP^XQCHK\nChecksum's calculated by CHECK^XTSUMBLD\n\n========================================================================= \nInstallation:\n\n 1. DSM sites - This routines is usually mapped,\n so you will need to disable mapping for the affected routines. \n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n to record what option is used it was getting\n \n 3. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n back "unknown". The broker created context\n \n 4. Users can remain on the system. \n Stop the Broker server(s), Stop any broker clients. \n (Each RPC call passes through this routine.)\n\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n Install Package(s) 'XWB*1.1*3'\n =========\n needed to set the variable XQY.\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 6. DSM Sites, after patch has installed, rebuild your map set.\n=========================================================================\n\n \n Checksum\nRoutine Old New 2nd Line\nXWBSEC 1126915 1317713 **3**\n\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nPatch XWB*1.1*39.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXWB*1.1*43 New broker long timeout fix.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXWB*1.1*46 Remove string length limit.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details\n\non patch XWB*1.1*45.\nThis patch is part of the Broker Security Enhancement (in conjunction \nwith patch XU*8*404).\n \n************************** NOTE ***************************************\n This Patch must be installed before XU*8*404.\n \n*************************************************************************\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXWB*1.1*49 Improve support for Linux.\n\n
\nPlease refer to the Description in the FORUM Patch Module for details.\nXWB*1.1*54 Handle long parameters in RDV.\n\n
\nXWB*1.1*53. See the patch description on Forum.\n\n
\nHandles timing for coversheet loads in the foreground.\n\n
\nRefer to the patch description on Forum.\n\n\n
\nPlease see the patch description on FORUM, in the National Patch Module.\n\n\n
\nThis patch is for the support of RUM. This will allow the trapping of\n INSTALLATION:\n \n 1. DSM sites - The Broker routines are not usually mapped. Disable\nmapping if necessary.\n \n 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS package onto your system.\n \n 3. The patch has now been loaded into a Transport global on your\nsystem. You now need to use KIDS to install the Transport global. On the\ndata for Remote Procedure Calls (RPCs) and the RPCBroker handler.\nKIDS menu, under the 'Installation' menu, use the following options:\n \n Verify Checksum's in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 4. All RPC Broker users should log off. Since no changes are made to\nthe main server routines, sites do not need to shut down the listener\njobs, BUT sites may choose to do if it makes it easier to control users\n \ntrying to log on during the routine update. Every RPC call passes through\nthese routines.\n \n 5. On the KIDS menu, under the 'Installation' menu, use the following\noption:\n Install Package(s) 'XWB*1.1*5'\n =========\n 6. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Enter the names of your Compute and Print server(s).\n \n Checksum\n 7. DSM Sites - Rebuild your map set if necessary.\n \n 8. Restart the Broker Listener if necessary.\n Routine Old New 2nd Line\n XWBBRK2 2982680 3134294 **5**\n XWBTCPC 8099567 8239171 **2,5**\n \n \n\n
\nSee Forum for the description\n\n\n\n\n\n
\nRPC Broker IPv6 and Security Updates\n \nPlease see full patch description of XWB*1.1*64 on FORUM.\n\n
\n \nSee full patch description of XWB*1.1*67 on Forum.\n\n
\nSee FORUM patch description.\n\n
\nBackup of XWB*1.1*76 on Feb 04, 2025\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses two problems:\nKERNEL SYSTEM PARAMETERS file, the same one used by Kernel logon. This\n \n======================================================================\nfix is also in XWBTCPL.\n \n <<THIS IS A SERVER SIDE PATCH ONLY.>>\n \n \n NOISs:\n =====\n MRN-1198-42547 - Broker Listener\n WIC-0399-42263 - Broker Listener\nA command error occuring at RESTART+17^XWBTCPL when the Broker tries to\n MAR-0499-20186 - Broker Listener\n CHY-1298-52305 - Broker Listener\n CTX-0499-70598 - Available Slots\n PUG-0399-51484 - Available Slots\n \n \n Routine Summary:\n The following routine is included in this patch. The second line of\n this routine now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\nreopen a device that is not closed. This seems to be a problem with Cache\n \n Checksum\n Routine Old New 2nd Line\n XWBTCPL 8215020 8850625 **1,7**\n \n List of preceeding patches: 1\n Sites should use CHECK^XTSUMBLD to verify checksums.\n \n =========================================================================\n Installation:\nsites only. The result of this error causes the Broker Listener to stop.\n \n \n 1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\n PCMM) during the installation. No Broker-based client/server\n software should be running while installing this patch on the\n server. To identify these jobs, check the system status and verify\n if any XWBTCPC routines are running (i.e., Broker Handler). Once\n identified, notify users to logoff or forcex the jobs. Active\n users may get NOSOURCE or CLOBBER errors.\n \nThis fix is in XWBTCPL routine.\n 2. Stop the Broker Listener on the server. Check the system status\n and verify if the XWBTCPL routine is running (i.e., Broker\n Listener). If it is running stop it. To stop the Listener, do the\n following:\n \n a. Log into your M server. \n b. Enter the following at the M prompt:\n \n >D STOP^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n \n \n 3. Broker routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n On the KIDS menu, under the 'Installation' menu, use the following\nThe other problem deals with available slots. The listener doesn't check\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n option:\nfor available slots before starting a new process. The listener will now\n Install Package(s) 'XWB*1.1*7'\n =========\n \n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n \n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\n other CPUs?'. Enter the names of your Compute and Print server(s).\ncheck the MAX SIGNON ALLOWED field of the VOLUME SET multiple in the\n \n 8. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n \n 9. Restart the Broker Listener on the Server:\n a. Log into your M server\n b. Enter the following at the M prompt:\n \n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n\n
\nThis patch:\nduring login.\nBroker Installation Guide to install the server portion of this patch. The\ninstructions in the Installation Guide are for virgin server installations\nand server version upgrades only.\n \n 1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\nPCMM) during the installation. No Broker-based client/server software\nshould be running while installing this patch on the server. To identify\nthese jobs, check the system status and verify if any XWBTCPC routine is\nrunning (i.e., Broker Handler). Once identified, notify users to logoff\nor forcex the jobs. Active users may get NOSOURCE or CLOBBER errors.\n \n \n 2. Stop the Broker Listener on the server. Check the system status and\nverify if the XWBTCPL routine is running (i.e., Broker Listener). If it\nis running stop it. To stop the Listener, do the following:\n a. Log into your M server.\n b. Enter the following at the M prompt:\n \n >D STOP^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\n \n2. Updates the Broker's programmer client workstation software -- also\n 3. These routines are not usually mapped on systems that allow it, so\nyou will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS (Kernel Installation and Distribution System)\npackage onto your system.\n \n 5. The patch has now been loaded into a Transport global on your system.\nOn the KIDS menu, select the 'Installation' menu, use the following\noptions:\nknown as the Broker Development Kit (BDK) -- adding support for Delphi 4\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\noption:\n Install Package(s) 'XWB*1.1*4'\n =========\n \ndevelopment.\n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Enter the names of your Compute and Print server(s).\n AXP Sites - Answer NO to this question.\n \n 8. If the routines were unmapped as part of step 3, the mapped set\nshould be rebuilt once the installation has run to completion.\n \n 9. Restart the Broker Listener on the Server:\n a. Log into your M server\n b. Enter the following at the M prompt:\n \n \n >D STRT^XWBTCP(Listener port)\n \nClient Side:\n============\n \nPlease follow the 'Programmer Client Workstation Installation\nInstructions' in the RPC Broker Installation Guide (XWB1_1P4IG.PDF).\n3. Fixes a bug in which the title bar of the Kernel login form was being\nchanged when a user started entering their access code.\n \nIMPORTANT NOTES:\n \n \nThis patch consists of 2 parts:\n \n - Packman message containing the XWB*1.1*4 KIDS build.\n - An updated BDK (programmer client workstation software).\n \n1. Packman message containing the XWB*1.1*4 KIDS build. It installs 2\nmodified XWB* routines used by the Broker server. This part of the patch\nis mandatory.\n \n1. Introduces a shorter timeout when logging in via any GUI application\n ROUTINE SUMMARY:\n ================\n The following is a list of the routines included in this patch. The\n second line of each of these routines now looks like:\n \n <tab>;;1.1;RPC BROKER;[patch list];date\n \n CHECK^XTSUMBLD results:\n \n Routine Name Before Patch After Patch Patch List\nthat is using the Broker. The server listener process will timeout after\n XWBBRK 4562161 4567623 2,4\n XWBTCPC 8239171 7518635 2,5,4\n \n2. Updated BDK (programmer client workstation software). All sites\ndoing Broker development are encouraged to retrieve the patched BDK. Note\nthat this version of the BDK only supports Delphi 4 and Delphi 3.\n \nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE AT\nEND-USER CLIENT WORKSTATIONS. If you are not using the BDK in any local\nor national development, you do not need to retrieve the Broker's\n90 seconds if the user has not passed in his/her access and verify codes.\nprogrammer client workstation software. The software does not update the\nBroker software that is running at end-user client workstations.\n \nThe software distribution includes:\n \nFILE NAMES DESCRIPTION Blocks Bytes\nXWB1_1P4PG.EXE BDK Self-Installing Executable 2944 1507118\nXWB1_1P4IG.PDF Installation Guide 382 195583\nXWB1_1RM.TXT Readme text file 15 7355\n \nUsers of existing GUI applications which were compiled under an older\nNote: Use Binary mode for .PDF, and .EXE files\n Use ASCII mode for .TXT file.\n \nTo access the updated BDK, use FTP to retrieve the software from one of\nthe following CIO Field Offices' ANONYMOUS.SOFTWARE directories:\n \n CIO FIELD OFFICE FTP Address\n Hines 152.129.1.110\n Albany 152.127.1.5\n Salt Lake City 152.131.2.1\nversion of the BDK will not see the shorter timeout unless the GUI\n \nBROKER-DEPENDENT COMPONENTS:\n \nSome components, such as the FileMan Delphi Components, reference the\nTRPCBroker component. If you use such components for development, be\naware that installing a new version of the TRPCBroker component (i.e. a\nnew BDK) may cause incompatibilities in Delphi, resulting in a compile\nfailure of the unit containing the Broker-dependent component and the\nfollowing compilation error:\n \napplication is recompiled. It is highly recommended that applications be\n Unit <unit1> was compiled with a different version of <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\nthat, with regards to the version of the BDK you are about to install:\n \na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible.\n \nFor the FileMan Delphi Components (FMDC), patch FMDC*1.0*1 brings in a new\nrecompiled using the new BDK to take advantage of the shorter timeout\nversion of FMDC compatible with the updated BDK. Please refer to the\nPatch Module for more information on this FMDC patch.\n \nINSTALLATION:\n \nServer Side:\n============\n \nUse the following instructions in installing this server-side RPC Broker\npatch. Do NOT follow the M Server Installation Instructions in the RPC\n\n
\nThis patch eliminates server Broker jobs for which there is no client\nnot been upgraded.\nXWB1_1P4IG.PDF Installation Guide 195,583\nXWB1_1RM.TXT Readme text file 13,428*\n*The size of this file will change in the future as additions are made.\n \nNote: Use Binary mode to retrieve .PDF, and .EXE files \n Use ASCII mode to retrieve .TXT file. \n \nTo obtain the updated BDK, use FTP to retrieve the software from one of\nthe following CIO Field Offices' ANONYMOUS.SOFTWARE directories: \n \n \n CIO FIELD OFFICE FTP Address \n Hines 152.129.1.110 (isc-chicago.domain.ext)\n Albany 152.127.1.5 (isc-albany.domain.ext)\n Salt Lake City 152.131.2.1 (isc-slc.domain.ext)\n \n \nCOMPATIBILITY WITH PRIOR VERSIONS\n============= ==== ===== ========\n \nThe server portion of this patch is backwards compatible with client\nPrior to this patch, these jobs would wait for 10 hours to receive data\napplications compiled with previous versions of the Broker. So, client\napplications do not have to be recompiled when this patch is installed on\nthe server. The server retains a 10 hour timeout for those client\napplications compiled with previous Broker versions; that is, they\ncontinue to work as they did before the patch is installed.\n \nIf an application is compiled with the BDK for XWB*1.1*6, the server\nXWB*1.1*6 patch MUST be installed for that application to run. That is,\nclient portion of this patch requires that the server portion be\ninstalled.\nfrom the client application that no longer exists. Two significant\n \n \nBROKER-DEPENDENT COMPONENTS\n================ ==========\n \nThe following comments apply only to those developing applications with\nthe BDK (programmer workstation software). They are not relevant to\nserver operation.\n \nSome components, such as the FileMan Delphi Components, reference the\nnegative effects of the ghost jobs are 1) consumption of a licensed\nTRPCBroker component. If you use such components for development, be\naware that installing a new version of the TRPCBroker component (i.e., a\nnew BDK) may cause incompatibilities in Delphi, resulting in a compile\nfailure of the unit containing the Broker-dependent component and the\nfollowing compilation error:\n \n Unit <unit1> was compiled with a different version of <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\nthat, with regards to the version of the BDK you are about to install:\nprocess, reducing the available number of user jobs and 2) retention of\n \na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible, or\n \nc) You have the source (.pas, .dfm, .dpk, etc.) files available so that\nthe component can be recompiled successfully.\n \nFor the FileMan Delphi Components (FMDC), patch FMDC*1.0*1 brings in a new\nversion of the FMDC that includes the source files. Please refer to the\napplication resources (particularly LOCKs) that interferes with subsequent\nPatch Module for more information on this FMDC patch. Additional\ninstructions regarding installing and recompiling FMDC when the Broker is\nupgraded are in XWB1_1RM.TXT found in the ANONYMOUS.SOFTWARE directories\nmentioned above and on the FMDC web page.\n \nINSTALLATION: \n============\n \nServer Side: \n====== ====\nuser actions. Other than waiting 10 hours for these jobs to finally\n \nThe following are the installation instructions for the KIDS distribution\nfor XWB*1.1*6: \n \n 1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\nPCMM) during the installation. No Broker-based client/server software\nshould be running while installing this patch on the server. To identify\nthese jobs, check the system status and see if any XWBTCPC routine is\nrunning (i.e., Broker Handler). Once identified, notify users to logoff\nor forcex the jobs. Active users may get NOSOURCE or CLOBBER errors. \ntimeout, the only way to get rid of the ghost jobs was for IRM to manually\n \n 2. Stop the Broker Listener on the server. Check the system status and\nsee if the XWBTCPL routine is running (i.e., Broker Listener). If it is\nrunning stop it. To stop the Listener, do the following: \n a. Log into your M server. \n b. Enter the following at the M prompt: \n \n >D STOP^XWBTCP(Listener port) \n (Typically, the Listener port is 9200\n \nkill them.\n 3. These routines are not usually mapped on systems that support\nmapping; so, you will probably not have to disable mapping. \n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\noption will load the KIDS (Kernel Installation and Distribution System)\npackage onto your system. \n \n 5. The patch has now been loaded into a Transport global on your system.\n On the KIDS menu, select the 'Installation' menu, use the following\noptions: \napplication. These 'ghost' jobs have occurred when client processes are\n \n Verify Checksum's in Transport Global \n Print Transport Global \n Compare Transport Global to Current System \n Backup a Transport Global \n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\noption: \n Install Package(s) 'XWB*1.1*6' \n =========\n \nThis patch changes the time that the server waits for the client to\n 7. MSM Sites - Answer YES to the question 'Want to MOVE routines to\nother CPUs?'. Enter the names of your Compute and Print server(s). \n AXP Sites - Answer NO to this question. \n \n 8. If the routines were unmapped as part of step 3, the mapped set\nshould be rebuilt once the installation has run to completion. \n \n 9. Restart the Broker Listener on the Server: \n a. Log into your M server \n b. Enter the following at the M prompt: \ncontact it. The length of the timeout is controlled by a new field in the\n \n >D STRT^XWBTCP(Listener port) \n \n \nClient Side: \n \nPlease follow the instructions in the most recent Broker 1.1 Installation\nGuide.\nKernel System Parameters file: BROKER ACTIVITY TIMEOUT. That field is\ndistributed by Kernel patch XU*8.0*115 with a default value of\napproximately 3 minutes. By setting the timeout to a duration much\nshorter than 10 hours, the ghost jobs are eliminated quickly if the client\napplication is no longer running. See the help for the BROKER ACTIVITY\nTIMEOUT field for advice regarding changing the value for this field.\n \nended in a non-standard way - for example, by pressing the PC's reset\nIn order to let the server know that the client application is still\nactive, the client portion of this patch initiates a periodic, background\ncontact with the server. This 'polling' of the server by the client\nresets the timeout so that the server job is not stopped when the client\nstill exists. Any client application compiled with the RPCBroker\ncomponent distributed with this patch automatically polls. No developer\nor user intervention is necessary, and this polling activity affects\nneither the application nor the user.\n \nThis patch specifically resolves problems raised in the following NOISs:\nbutton. \n \nBIR-0399-32032 GUI LOCKES UP ON USERS\nOKL-1298-70542 LOCKOUT FROM GUI\nHUN-0898-21008 Providers are locked out of record\nSAG-0898-40564 TIMEOUT MANAGMENT ON GUI\nDAY-0798-40953 No DTIME in XWBTCPC\nTUA-0598-30739 GUI JOBS HANGING AROUND\nWAS-0198-20958 SYSTEM NOT RELEASING USER AFTER CLOSING CHART\nBIR-0699-31167 BROKER TIMEOUT\nSDC-0499-62471 PATIENT RECORDS LOCKED UP\n \nALB-0499-52063 Patient Record Locked\nHIN-0599-42485 CPRS CONNECTIONS REMAIN ACTIVE AFTER LOGOUT\n \n \nIt also fulfills a request made in the following E3R:\n \n9646 CHANGE OF MAIN TIMED READ FOR BROKER\n \n \nIMPORTANT NOTES: \nNote: The server side of this patch is effective only for client\n========= =====\n \nThis patch consists of 2 parts: \n \n - Packman message containing the XWB*1.1*6 KIDS build. \n - An updated Broker Development Kit (programmer workstation software). \n \n1. The packman message containing the XWB*1.1*6 KIDS build installs 3\nmodified XWB* routines and a new RPC (entry in the Remote Procedure file)\nused by the Broker server. This part of the patch is mandatory. \napplications (like CPRS-GUI) that have been recompiled with the Broker\n \nRoutine Summary: \n======= ========\n \nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like: \n \n<tab>;;1.1;RPC BROKER;[patch list];date \n \nCHECK^XTSUMBLD results: \nDevelopment Kit portion of the patch. So, installing the server patch\n \nRoutine Name Before Patch After Patch Patch List \nXWBTCPC 7518635 7635440 2,5,4,6 \nXWBLIB 674092 720789 6 \nXWBSEC 1317713 2113752 3,6 \n \n2. Updated BDK (programmer client workstation software). All sites doing\nBroker development are encouraged to retrieve the patched BDK. Note that\nthis version of the BDK only supports Delphi 4 and Delphi 3. \n \nalone will not eliminate the ghost jobs for client applications that have\nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE ON END-USER\nCLIENT WORKSTATIONS. If you are not using the BDK in any local or\nnational development, you do not need to retrieve the Broker's programmer\nclient workstation software. The patch does not update the Broker\nsoftware that is running at end-user client workstations. \n \nThe software distribution includes: \n \nFILE NAMES DESCRIPTION BYTES\nXWB1_1P6PG.EXE BDK Self-Installing Executable 1,500,607\n\n
\n** Y2K WAIVER - #Y2KW0001 **\n EKH-1298-40440 Divisional Parameters\n EKH-0399-40543 WHEN ENTERING THROUGH THE GUI the submit request\n HVH-0699-12732 GUI ONLY USES PRIMARY SITE FIELDS: IC LAB ORDERS\n FGH-0299-32563 MultiDivisional Capabilities\n BHH-0799-41993 Lab Collection Printing Problem for Integrated Sites\n \n \nIMPORTANT NOTES: \n=================\n \n \nThis patch consists of 1 part ONLY: \n- An updated Broker Development Kit (BDK), the programmer workstation\nsoftware. All sites doing Broker development are encouraged to retrieve\nthe patched BDK. Note that this version of the BDK only supports Delphi 4\nand Delphi 3. This patch doesn't support Delphi 5.\n \nDO NOT INSTALL THIS PROGRAMMER CLIENT WORKSTATION SOFTWARE ON END-USER\nCLIENT WORKSTATIONS. If you are not using the BDK in any local or\nnational development, you do not need to retrieve the Broker's programmer\nclient workstation software. The patch does not update the Broker\nThis patch supports GUI Multi-Divisional signon. If a user has more\nsoftware that is running at end-user client workstations. \n \nThe software distribution includes: \n \nFILE NAMES DESCRIPTION Bytes \nXWB1_1P8PG.EXE BDK Self-Installing Executable 1,636,409\nXWB1_1P4IG.PDF Installation Guide 195,583 \nXWB1_1RM.TXT Readme text file 13,428*\n*The size of this file will change in the future as additions are made.\n \nthan one division to choose from, the user must select one before\nNote: Use Binary mode to retrieve .PDF, and .EXE files \n Use ASCII mode to retrieve .TXT file. \n \nTo obtain the updated BDK, use FTP to retrieve the software from one of\nthe following CIO Field Offices' ANONYMOUS.SOFTWARE directories: \n \n CIO FIELD OFFICE FTP Address \n Hines 152.129.1.110 (isc-chicago.domain.ext)\n Albany 152.127.1.5 (isc-albany.domain.ext)\n Salt Lake City 152.131.2.1 (isc-slc.domain.ext)\ncontinuing with signon. If the user has only one division in file 200,\n \nBROKER-DEPENDENT COMPONENTS\n===========================\n \nThe following comments apply only to those developing applications with\nthe BDK (programmer workstation software). They are not relevant to\nserver operation.\n \nWARNING:\nSome components, such as the FileMan Delphi Components, reference the\nthis division will be used; else, the default institution in the\nTRPCBroker component. If you use such components for development, be\naware that installing a new version of the TRPCBroker component (i.e., a\nnew BDK) may cause incompatibilities in Delphi, resulting in a compile\nfailure of the unit containing the Broker-dependent component and the\nfollowing compilation error:\n \n Unit <unit1> was compiled with a different version of <unit2>.\n \nCheck with the creators of the Broker-dependent component to make sure\nthat, with regards to the version of the BDK you are about to install:\nKernel System Parameters file will be used.\n \na) Your current component is compatible, or\n \nb) You can obtain a new version of the component that is compatible, or\n \nc) You have the source (.pas) files available so that the component can be\nrecompiled successfully.\n \nFor the FileMan Delphi Components (FMDC), patch FMDC*1.0*1 brings in a new\nversion of the FMDC that includes the source files. Please refer to the\n \nPatch Module for more information on this FMDC patch. Additional\ninstructions regarding installing and recompiling FMDC when the Broker is\nupgraded are in XWB1_1RM.TXT found in the ANONYMOUS.SOFTWARE directories\nmentioned above and on the FMDC web page.\n \nCLIENT SIDE INSTALLATION: \n========================\n \nTHIS IS A CLIENT SIDE PATCH ONLY. Please follow the instructions in the\nmost recent Broker 1.1 Installation Guide.\nThis patch specifically resolves problems reported in the following NOISs:\n\n
\nThis patch fixes the following: \nfor starting Broker listeners.\n Checksum\nRoutine Old New 2nd Line\nXWBTCP 9081629 10677300 **1,9**\nXWBTCPC 7635440 7568523 **2,5,4,6,9**\nXWBTCPL 8850625 8934371 **1,7,9**\n \nList of preceding patches: 6, 7\nSites should use CHECK^XTSUMBLD to verify checksums.\n \n=========================================================================\n \n \nInstallation:\n \n 1. Do not run any RPC-Broker-based Client/Server software (e.g., CPRS,\n PCMM) during the installation. No Broker-based client/server \n software should be running while installing this patch on the \n server. To identify these jobs, check the system status and verify\n if any XWBTCPC routines are running (i.e., Broker Handler). Once \n identified, notify users to logoff or forcex the jobs. Active \n users may get NOSOURCE or CLOBBER errors. \nThese changes fulfill the functionality requested in the following E3Rs:\n \n 2. Stop the Broker Listener on the server. Check the system status \n and verify if the XWBTCPL routine is running (i.e., Broker \n Listener). If it is running stop it. To stop the Listener, do the\n following: \n \n a. Log into your M server. \n b. Enter the following at the M prompt: \n \n >D STOP^XWBTCP(Listener port) \n 11934, RPC BROKER FILE SHOWS RUNNING ON OPENM FAILOVER\n (Typically, the Listener port is 9200) \n \n 3. Broker routines are not usually mapped on systems that allow it, so\n you will probably not have to disable mapping.\n \n 4. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n \n 5. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 10705, LISTENERS NOT STOPPED WILL NOT START UP\n On the KIDS menu, under the 'Installation' menu, use the following\n options:\n \n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n 6. On the KIDS menu, under the 'Installation' menu, use the following\n option:\n 8789, CREATE MENU STARTUP AND SHUTDOWN OPTIONS\n Install Package(s) 'XWB*1.1*9'\n =========\n No Options or Protocols need to be placed out-of-order.\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n 7. If the routines were unmapped as part of step 3, the mapped set\n should be rebuilt once the installation has run to completion. \n \n 8. Restart the Broker Listener on the Server:\n \n a. Log into your M server\n b. Enter the following at the M prompt:\n \n >D STRT^XWBTCP(Listener port)\n (Typically, the Listener port is 9200)\nThe changes also resolve the problems reported in the following NOIS\ncalls:\n DAY-0796-40646, Startup Queue of Listener\n \n FRE-0299-60491, Broker Not Starting Automatically\n \nHere are the definitions of the options:\n \nNAME: XWB LISTENER STARTER MENU TEXT: Start All RPC Broker Listeners\n TYPE: run routine CREATOR: \n PACKAGE: RPC BROKER DELEGABLE: YES\n DESCRIPTION: This option will Start/Restart all the RPC Broker\nlisteners under the control of the RPC BROKER SITE PARAMETERS file. It is\nnormally setup as a STARTUP type option in the taskman option scheduling\n1. Intersystems License. This is the patch that works with patch\nfile. This option will first STOP ALL listeners and then START ALL the\nlisteners through Taskman. (VMS sites need to be running Taskman in DCL\ncontext). The XWB LISTENER STARTER cannot be used to start one particular\nlistener. To do this, in programmer mode, use STRT^XWBTCP(portnumber) on\nthe node the listener needs to run on. Or use the XWB LISTENER EDIT option\nto change the status of the one listener.\n ROUTINE: RESTART^XWBTCP SCHEDULING RECOMMENDED: STARTUP\n UPPERCASE MENU TEXT: START ALL RPC BROKER LISTENERS\n \nNAME: XWB LISTENER STOP ALL MENU TEXT: Stop All RPC Broker Listeners\nXU*8*118. The code to share licenses when GUI and Telnet users from the\n TYPE: run routine CREATOR: \n PACKAGE: RPC BROKER DELEGABLE: YES\n DESCRIPTION: This option will Stop all the RPC Broker listeners under\nthe control of the RPC BROKER SITE PARAMETERS file.\n ROUTINE: STOPALL^XWBTCP\n UPPERCASE MENU TEXT: STOP ALL RPC BROKER LISTENERS\n \n3. The code called by the XWB LISTENER STARTER option had a bug that\ncaused it to start the listeners on the default port of 9000. This\nproblem is fixed. The following NOIS calls reported the bug.\nsame workstation are connected is in place and ZU now calls it. This\n \n BEC-0999-21188 XWB LISTENER STARTER \n STX-0999-71581 BROKER STARTING 9000 IGNORING PARAME \n \n4. A new menu option, XWB MAIN MENU, is included in this patch. Another\noption, XWB LISTENER EDIT, is also included. Here are the option\ndefinitions:\n \nNAME: XWB MENU MENU TEXT: RPC Broker Management Menu\n TYPE: menu CREATOR: \npatch adds a similar call from XWBTCPC. \n PACKAGE: RPC BROKER DELEGABLE: NO\n DESCRIPTION: This is the main menu for RPC Broker. \nITEM: XWB LISTENER STOP ALL DISPLAY ORDER: 3\nITEM: XWB LISTENER EDIT DISPLAY ORDER: 1\nITEM: XWB LISTENER STARTER DISPLAY ORDER: 2\n TIMESTAMP: 58079,48431\n UPPERCASE MENU TEXT: RPC BROKER MANAGEMENT MENU\n \nNAME: XWB LISTENER EDIT MENU TEXT: RPC Listener Edit\n TYPE: edit CREATOR:\n \n PACKAGE: RPC BROKER DELEGABLE: NO\n DESCRIPTION: This option allows for editing the RPC BROKER SITE\nPARAMETERS file (#8994.1).\n DIC {DIC}: XWB(8994.1, DIC(0): AEMQ\n DIE: XWB(8994.1, DR {DIE}: [XWB LISTENER EDIT]\n TIMESTAMP OF PRIMARY MENU: 58078,56469\n UPPERCASE MENU TEXT: RPC LISTENER EDIT\n \n <<<<<<THIS IS A SERVER SIDE ONLY PATCH>>>>>>\n \n2. This patch brings a new XWB LISTENER STOP ALL option for shutting down\nThe updated Broker Systems Manual and the Broker Technical Manual may be\nretrieved at the following CIO Field Offices' ANONYMOUS.SOFTWARE\ndirectories:\n \n Hines 152.129.1.110 (isc-chicago.domain.ext)\n Albany 152.127.1.5 (isc-albany.domain.ext)\n Salt Lake City 152.131.2.1 (isc-slc.domain.ext)\n \nUse Binary mode for these .PDF files:\n \nmultiple listeners. It also brings a modified option XWB LISTENER STARTER\nXWB1_1P9SM.PDF Broker Systems Manual See patch desc.\nXWB1_1P9TM.PDF Broker Technical Manual See patch desc.\n \nRoutine Summary:\n================\n \nThe following routines are included in this patch. The second line of each\nof these routines now looks like:\n ;;1.1;RPC BROKER;<patchlist>;Mar 28, 1997\n \n\n\nRPC BROKER version 1.1\n\n
\nRemote Procedure Call (RPC) Broker is the software that provides Decentralized\nHospital Computer Program (DHCP) its client/server architecture. The RPC\nBroker allows workstations running client applications to access DHCP data and\nmethods. \n\nRPC Broker has a client module which runs on the workstation and a server\nmodule which runs on the host computer where the data and business rules \nreside. On the client side the Broker works between the applications and the\ntransport protocol. \n\n
\nThis Build:\n array in the routine GMRAPTB.\n \n4) fixes the problem reported in NOIS NOP-0596-12146. A user presses\n RETURN or enters an up-arrow at the Causative Agent prompt and is\n prompted to enter another causative agent.\n \n5) fixes the problem reported in NOIS ISH-0596-42277. Under certain\n instances the 'Sign-off' event point is not being executed.\n \n6) modifies the field description for the REQUIRE ORIGINATOR COMMENTS\n \n field (#4) in the GMR ALLERGY SITE PARAMETERS file (#120.84).\n NOIS CLA-0696-20854.\n \n7) fixes a problem where the REACTION ASSESSMENT field (#1) in the ADVERSE\n REACTION ASSESSMENT file (#120.86) is marked 1 (yes), but the patient\n does not have any active entries (i.e., entries that have not been\n entered-in-error) in the PATIENT ALLERGIES file (#120.8).\n NOIS: CMO-0696-40833.\n \n8) identifies the patient (e.g., T1234), suspect medication and event date\n1) deletes the Soundex cross-reference from the NAME field (#.01) of the\n on the Attachment page of the MedWatch form. NOIS: BRX-0696-11081.\n \n9) modifies the GMRADPT utility to return "unsigned" reactions in the\n GMRAL array.\n \n10) changes the ORCHK^GMRAOR utility call. If the calling routine is\n checking for Contrast Media Reactions and the patient is not in the\n ART database, then the utility will return a null value instead of a\n 0 (zero).\n \n GMR ALLERGIES file (#120.82).\n11) fixes a bug in the GMRADPT utility which returns a GMRAL array node\n stating the person has No Known Allergies if the person is not in the\n ART database.\n \n12) fixes a bug in the GMRANKA routine which may enter the wrong value in\n the ADVERSE REACTION ASSESSMENT file (#120.86), REACTION ASSESSMENT\n field (#1). NOIS: MAR-0696-21799.\n \n2) fixes a possible undefined variable error (GMRAREC) in the routine\n GMRASIG1.\n \n3) fixes a FOR loop which uses the wrong variable to loop through an\n\n
\nAllergies entered via CPRS were being entered into the ART database as\nunverified even if they met the criteria to be auto-verified in the ART\nsite parameters. This patch will auto-verify those allergies entered via\nCPRS that meet the criteria as defined at the site.\n\n
\nThis patch will make the ARTS software compatible with the National Drug\nFile regardless of version.\n\n
\nThe METHOD OF NOTIFICATION field in file 120.84 is used to determine the\n \nDBIA #1471 has been retired which allowed ART to call ALLERGY^RAUTL3 in\nThis patch corrects this error by changing the reference to use file 12d\nRADIOLOGY/NUCLEAR MEDICINE v 4.5 to retrieve and store information\nrelating to allergies to radiologic contrast media. This reference is\nbeing removed from the ART software.\nusers that should receive the chart and ID band marking bulletin. If this\nfield is set to OE/RR TEAMS, the code made reference to PCMM team lists.\nCPRS has ceased use of PCMM teams for list functionality. The errant\nreference to PCMM caused an error when a patient with data in the ADVERSE\nREACTION TRACKING (ART) database was admitted. The same error can be\ngenerated when a new adverse reaction is entered and the charts and/or ID\nbands have not been marked. patch corrects this error by changing the\nreference to use the OE/RR LIST (#100.21) file.\n\n
\nThis patch includes a utility for updating free text entries. Please see\nthe FORUM patch description for a detailed explanation of this patch.\n\n
\nUpdate to allergy tracking package consisting of changes to the free text \nutility distributed in patch GMRA*4*17 as well as updates to send \nbulletins from CPRS GUI upon new allergy entry. Please see the FORUM \nmodule for complete details.\n\n
\nThis patch will install new cross-references on files 120.8, 120.85\nand 120.86 in support of the health data repository. See the\npatch description on FORUM for complete details.\n\n
\nHDR related changes. Please see FORUM patch description\nfor details regarding this patch.\n\n
\nAllergy updates required to support the removal of allergies\nas orders. After installation of this patch and CPRS GUI v25,\nallergies will no longer be treated as orders.\n \nPlease see the FORUM patch module for a complete description.\n\n
\nThis patch includes changes required for continued support\nof the Health Data Repository project. Please see the national\npatch module for a full description of this patch.\n\n
\nThis Build addresses the following problems:\nknown allergies or adverse reactions?" prompt and does not enter a\ncausative agent the software assesses the patient as having a reaction on\nfile in the database. It should not.\n \n3) The GMRA PRINT-COMPLETE LISTING option does not distinguish between\npatients who not in the ART database and those patients who are assessed\nas NKA (No Known Allergies).\n \n4) The ART package calls an Outpatient Pharmacy utility to get and display\nany outpatient medications for a patient. The SIG code value for the\n \nprescription return is changing in size from one line of text to one plus\nlines of text. The ART package will store the first 30 characters of the\nSIG code for its SUSPECT and CONCOMITANT drug entries in File 120.85.\n \n5) Changes the description for the GMRA PRINT-FDA EXCEPT BY PT option so\nthat it accurately describes what that option does.\n \n6) Changes the description for the GMRA PRINT-EXCEPT BY DATe option so\nthat it accurately describes what that option does.\n \n1) Corrects a bug introduced by the GMRA*4.0*2 patch. Users are not being\nFor more detailed information please see the GMRA*4*5 patch description on\nFORUM.\nasked to sign-off on autoverified reactions in the enter/edit reaction\nprocess if they answer YES to the "Enter another Causative Agent?" prompt,\nbut do not enter another causative agent. This results in the reaction not\nbe considered as autoverified.\n \n2) When a user mistakenly answers YES to the "Does this patient have any\n\n
\nSee FORUM patch module for a full description. Updates HDR related\ntrigger code.\n\n
\nUpdate to fix blank sign/symptom issue. Please see FORUM for the\ncomplete description of this patch.\n\n
\nThis patch will correct the reported problem of the allergy bulletin\nnot being fired if the contrast media has a VA DRUG CLASS of DX109.\n\n
\nRemedy ticket HD67463 was logged because the site noticed that deceased \npatients were appearing on the [GMRA PRINT-PATIENT NOT ASKED] report. \nThis report lists patients who have not been given an allergy/adverse \nreaction assessment. The sites then use this list and contact the \npatients in an attempt to get the assessment information from them. It \nis not desirable for the VA to inadvertently contact the family of a \ndeceased individual in an attempt to get the allergy/adverse reaction \ninformation for that person.\n\n
\nUpdates to HL7 messaging for HDR. See FORUM for a complete\ndescription.\n\n
\nPOSSIBLE PROBLEM WITH LIST BY LOCATION UNASSESSED ALLERGIES.\n\n
\nThis patch updates the clean up utility to include ingredient based\nand drug class based allergies. Please see FORUM for the complete\ndescription of this patch.\n\n
\nRemoves ability to delete existing allergy entries from the\nroll and scroll environment.\nPlease see the FORUM patch module for a complete description.\n\n
\nRemote Data Interoperability updates. Please see FORUM for a full \ndescription of the updates.\n\n
\nUpdates for RDI and contrast media\nPlease see the FORUM patch description for full details.\n\n
\nGMRA*4.0*7 See National patch module for a description of the changes\nincorporated in this patch.\n\n
\nProvides an auto-update for existing free text allergies\n\n
\nThis patch reviews updates made in patch GMRA*4*29 related\nto terms that begin with the text ANGIOTEN and assures that\nthey were correctly updated. A few ANGIOTEN entries were\nincorrectly updated to the wrong drug class and need to be\nupdated to the correct drug class.\n\n
\nThis patch addresses Remedy ticket, HD67403. The site reported\nThis patch will also correct a problem with the bulletin generation during\nentry of Adverse Reactions described in Remedy ticket HD85125.\n \nThe problem occurs when the user answers "No" to verify an observed/drug \nadverse reaction when it is first entered. If the user skips the \nverification step but then uses the GMRA PATIENT A/AR EDIT option and \nedits the existing observed/drug allergy and then verifies it (with or \nwithout making changes) an additional NOTIFICATION OF OBSERVED DRUG \nREACTION bulletin is triggered.\n \nthat test patients entered in production are appearing on the\nThis patch will modify the logic in the code so that, if the user \nre-enters the adverse reaction and then verifies it, a second \nNOTIFICATION OF OBSERVED DRUG REACTION bulletin will not be triggered.\nAdverse Reaction Tracking reports, and are also being included in\nreport counts.\n \nThis patch will update the Adverse Reaction Tracking reports that \ndisplay the patient name and/or SSN, and reports that produce counts\nof reaction data so that they all exclude test patients.\n \n\n
\nSee GMRA*4*41 in the National Patch Module\n\n
\nFixes issue with historical allergy entries being associated with\na progress note when the historical entry follows the entry of\nan observed drug reaction.\nAlso, fixes issue with 0 node not being set correctly on XTMP node\nand provides failsafe for sending data to HDR.\n\n
\nThis is a companion patch to the Order Entry/Results Reporting (OE/RR) \nversion 3.0 software patch number 345 (OR*3.0*345). See the patch message\nfor a full listing of issues addressed and installation instructions.\n\n
\nThe patch is to create a merge routine to check for allergy assessments \nin Patients before the merge occurs.\n\n
\nThis build fixes several problems in the ART portion of the ART-CPRS\n GMRAOR4\n The ART EP asked the CPRS developers to include the OBSERVER field\n value for all new reactions CPRS sends to the ART package. This routine\n was changed to recognize this piece of data when it is passed to ART.\n \n GMRAOR5\n Fixes a syntax error.\n \n Simplifies some code used to check for duplicate patient reactions.\n \ninterface.\n Fixes a bug where the reaction was not completely filed if the reaction\n value pointer and file was not recognized as one of the five pointed-to\n files used by the ART package.\n \n Modifies the code to call GMRAOR9 to store any drug ingredients or drug\n classes if the reaction was of a drug type.\n \n Modifies the code to add an entry to File 120.85 only if the patient\n reaction was an observed drug reaction.\n \n \n Sends the reaction as unverified so it will appear on the\n list of reactions to be verified.\n \n GMRAOR7\n The sign/symptom data was not being stored in File 120.85 because a\n call to SIGN^GMRAOR6 was passing the variable GMRAL when it should send\n the array GMRAL.\n \n GMRAOR8\n This routine was modified to correct subfile numbers being set\nRoutine changes:\n in fileman.\n \n GMRAOR9 \n This is a new routine which stores drug ingredients and/or drug classes\n for a patient drug reaction.\n \n GMRAOR0\n The DUPCHK entry point was quitting prematurely and therefore not\n accurately checking for duplicate entries.\n \n\n
\nThis patch installs a tool that will assist sites in ensuring that the \nADVERSE REACTION ASSESSMENT file (#120.86) is synced with the PATIENT \nALLERGIES file (#120.8). See the associated patch description for \nadditional details and installation instructions.\n\n
\nUPDATES ADVERSE REACTION TRACKING TO RETURN SIGN/SYMPTOM DATA WITH \nCOMPUTERIZED PATIENT RECORD SYSTEM (CPRS) ORDER CHECK MESSAGES AND TO \nINLUCDE HEALTH DATA REPOSITORY (HDR) DATA WITH THE EN1^GMRADPT \nAPPLICATION PROGRAMMING INTERFACE (API). REFER TO THE PATCH DESCRIPTION \nFOR ADDITIONAL INFORMATION.\n\n
\nThis patch is a follow-up patch to GMRA*4*46. See the associated patch \ndescription for details on this patch.\n\n
\nPatch GMRA*4.0*49 addresses the following two issues:\n \n1. Excessive number of entries in the PATIENT ALLERGIES file (#120.8)\n causes issues with the allergy HL7 messages.\n \n2. Embedded carriage returns in some old allergy HL7 messages prevented \n the messages from being sent.\n\n
\nSee National Patch Module for details.\n\n
\nPatch GMRA*4.0*54 addresses the following three issues:\n \n1. FDA report SUBSCRIPT error with non-VA drugs \n \n2. Adverse Reaction Assessment update when no previous Reaction \n Assessment value\n \n3. Allergy file allows MECHANISM to be null\n\n
\nThis patch has the following enhancements for Clinical Ancillary Services\n the Drug code of "D", as no action was needed to be taken for this\n scenario.\n(CAS) Enhancements (RXSU2).\n \n1. Suppress Non-Drug Ingredient-Level Alert\n \n Previously released patch GMRA*4*50 added a new alert when the DRUG \n CLASSES field (#3) in the PATIENT ALLERGIES file (#120.8) is empty. \n This patch will add a filter, to ignore those alerts, where ALLERGY\n TYPE field (#3.1) in PATIENT ALLERGIES file (#120.8), does not contain\n\n
\nThis patch addresses NSR 20171203. See the Forum patch description for\nadditional details.\n\n
\nIEN MISMATCH ISSUE\n\n
\nThe Description of this build can be found in the Nation Patch Module\nunder patch GMRA*4.0*6\n\n
\nThis patch resolves issues identified during the testing of CPRS v31 as \nwell as post-release issues with recently released patches. See the patch \ndescription for the list of issues resolved.\n\n
\nThis patch addresses the following issue:\n \n1. INC9435820 - WRONG URL IN AN ALLERGY OPTION\n When utilizing Menu Option GMRA ALLERGY FILE EDIT the user is\n presented with an incorrect URL (Uniform Resource Locator) or Web\n Page to be used when making their request.\n\n
\nThis patch will resolve the following issue in the Clinical Procedures \n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1. INC8167520 - Cannot enter NKDA into the patient's allergy assessment.\n(CP) Flowsheet application.\n \nProblem 1:\n----------\nIf the user "up carats out" of the GMRA assessment utility prior to the \nreport running, the next time a user enters the utility it will appears \nas though the report ran, even though it did not.\n \nResolution 1:\n-------------\nRoutine GMRAFA was modified to kill the ^XTMP("GMRAFAL") global if the \n \nuser exits before running the report. This will reset the option, \nallowing the user to run the report.\n1. INC8167520 - Cannot enter NKDA into the patient's allergy assessment.\n \n \nNew Service Requests (NSRs):\n---------------------------- \nN/A\n\n\nThis patch addresses a post-release issue identified with patch \nGMRA*4*53, part of the CPRS v31b release. See the patch description for a \nfull explanation of the issue.\n\n
\nBackup of GMRA*4.0*66 on Jul 01, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will resolve the following issue:\n that cannot be resolved with the Modify Assessment tool.\n INC17041569 - CPRS ERROR_unable to update allergies for ONE patient\n INC17069709 - Adverse Reaction Tracking - Allergy Assessment\n INC17072229 - Adverse Reaction Tracking - Allergy Assessment\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC11926924 - MAD: GMRA*#*### not resolve: order appeared verified by nurse\n in BCMA but CPRS it was found not to be. \nProblem: \n \n-------\nThe Captain James A. Lovell Federal Health Care Center reported that they were\nunable to modify an allergy assessment for a specific patient using the\nAssessment clean up utility option [GMRA ASSESSMENT UTILITY]. After some \nresearch it was discovered that when two patients were merged and the 'TO'\npatient (remaining patient after them merge) had not Allergy assessment while\n'FROM' patient (deleted after the merge) a corrupt record was being created\nfor the 'TO' patient. These records could not be fixed using the Assessment\nclean utility option [GMRA ASSESSMENT UTILITY].\n \n1) INC17497887 - UNABLE TO MODIFY AN ALLERGY ASSESSMENT USING THE VISTA\nResolution:\n----------\nThe root of the problem is within the Kernel Patient Merge module. However we\nwere able to address the problem by modifying GMR code specifically designed\nto run right before two patients are merged. The solution applied consisted of\ncopying the 'FROM' Allergy assessment information to 'TO' before the patient\nmerge were performed by the Kernel Patient Merge utility. In addition to\nfixing this problem so no new entries are affected this patch also fixes the\nexisting entries with the problem through a post-install routine that is\ndescribed below.\n (HITPS-7808) ASSESSMENT CLEANUP UTILITY ECN 74075\n \nTechnical Resolution:\n--------------------\nModified the routine XMRAMRG by adding right at the beginning of the ASSESS\ntag code to identify whether the 'FROM' patient had an allergy assessment in\nthe ADVERSE REACTION ASSESSMENT file (#120.86) and the 'TO' patient did not.\nIf that's the case for the patient par being merged the new code will copy the\n'FROM' patient allergy assessment and create an identical assessment for the\n'TO' patient in the ADVERSE REACTION ASSESSMENT file (#120.86). This will\neffectively prevent the Kernel Patient Merge Utility from creating a corrupt\n Duplicate:\nentry for the 'TO' patient. \n -----------\n INC16946767 - allergy info being displayed differently (incorrectly) in\n different areas of Vista/CPRS\n INC17041102 - Adverse Reaction Tracking-Allergy Assessment; 3 Discrepancies\n\n
\nPlease refer to the patch description for contents and detailed \ninformation.\n\n
\nThis patch will resolve the following issue:\n \n<SUBSCRIPT>DRUG+95^GMRAOR *ITEMS() Subscript 1 > 511\n \nIt was reported that a hard error was encountered when the reporting \nsite, using CPRS, placed an inpatient medication order for hydroxyzine \nfor a patient that has noted severe allergic reactions to hydroxyzine. \nThe error caused CPRS to shut down and prevented the user from further \nprocessing the order. \n \nThe error encountered is as follows: \n\n
\nPlease see forum for a complete description of patch GMRA*4.0*68.\n\n
\nThis patch addresses the following issue:\n \nINC30029401 - Inactive GMRA Allergy items found the Patient Allergies \nfile need to be cleaned up.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nThis patch will update the mark chart/id band option to use\nthe new ACRP APIs that become available with patch SD*5.3*131.\nPlease see the national patch module for a full description of\nthis patch as well as patch 131.\n\n
\nSee Description in the National Patch Module for Patch GMRA*4*10.\n\n
\nThe description of this build can be found in the National Patch Module \nwithin the patch description of GMRA*4*11.\n\n
\nThe Adverse Reaction Tracking package tracks patient allergies/adverse\nreactions.\n\n
\nThis package permits clinical users to track and report patient allergies\nand adverse reactions. The intended users are physicians, nurses, other\nclinicians and clerks.\n\n
\nSee National Patch Module for details on changes included in this build.\n\n
\nWhen printing the CONSOLIDATED HEALTH RECORD INQUIRY report, dates are \nprinted in internal format, but should be printed in external format.\n\n
\nThis patch modifies the the if condition at WHOTO^RTTR1 from 'OR' to \n'AND'.\n\n
\nTo correct the scanning problem, routine RTDPA will be modified to look \nfor a match if the barcode scanned cannot be found. The program will \ndisplay the possible match with general patient information and prompt \nthe user to confirm the match. If the user accepts the match, the \nprogram will store the barcode information scanned in field 300 OLD \nBARCODE of RECORDS file (#190) to be referenced later.\n\n
\nThis build modifies routines RTSYS and RTP3 to correct problems reported \nin NOIS calls:\nSTC-0403-42187 Borrower Set Up Option\nUNY-0303-11769 C&P Records are getting requested on a regular Pull List\n\n
\n \nRecord Tracking NOIS\n\n
\n \nRecord Tracking Clinic Request Initializer Mail Message Fix\n\n
\nPROBLEMS CREATED BY RT*2.0*37\n\n
\nDelete Record Tracking menu option and correct an undefined error when \nusing the [RT SM-CLINIC REQUESTS] option.\n\n
\n This patch addresses an issue reported in the Record Tracking (RT)\n package. This issue is that the software allows the user to enter\n the Record Tracking Total System Menu [RT OVERALL] menu option \n without setting the INSTITUTION parameters. When users try to use \n the Charge Out Pull List Records [RT PULL-CHARGE-OUT] menu option \n they receive the following message: "This function requires the \n user to be signed onto the system with INSTITUTION parameters defined."\n They are then bumped out and are returned to the original menu.\n\n
\nResets IO to home device. In response to NOIS SLC-0496-51149.\n\n
\nThe purpose of this patch is to edit TERM^RTSM7 and avoid a run-away \nissue caused by occasional bad nodes in the New Person File VA(200\n\n
\nBe sure patch RT*2*4 has been installed before installing this patch.\nSee the National Patch Module for more details on this patch.\n\n
\n See the patch description for RT*2*32 in the patch module.\n\n
\nThis patch fixes problems related to trace movement history\nand new volumes.\n\n
\nThis build changes two routines to improve and correct the \n'Generate Record Retirement Pull Lists' option. \nSee patch description for more details. \n\n
\nThis build reintroduces the patient sensitivity/security check \nand fixes other misc. problems.\n\n
\nChecks that device can be queued to and fixes other NOISes.\n\n
\nThis package is mainly used for medical records tracking and film\njacket tracking. However, it is design to be used to track most\nany kind of record, such as dental.\n\n
\n 4 routines have been modified in this patch:\n 2. AFJXWCP8 The routine AFJXWCP8 was found to contain references to\n be removed from the Mapped set at this time. \n \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n \n 4. From the Installation menu, you may elect to use the following \n options (when prompted for the install name, enter AFJX*5.1*5): \n ==========\n a. Backup a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \n file 6 and to file 16. The pointers are now properly referenced to\n backup any other changes such as DDs or templates. \n b. Compare Transport Global to the Current System - this option \n will allow you to view all changes that will be made when the \n patch is installed. It compares all components of the patch \n (routines, DDs, templates, etc.). \n c. Verify checksums in the Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the Transport Global. \n \n 5. Use the Install Package(s) options and select the package:\n file 200. \n AFJX*5.1*5.\n ==========\n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? Yes// <return>, respond YES. When prompted to select the\n ===\n option(s) you would like to place out of order, enter the\n following: \n \n AFJXNHEX REQUEST \n \n ================\n AFJX PURGE NIGHTLY \n ==================\n \n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate\n CPUs. Alternatively, you can wait until the installation is\n complete and move the routines listed in the Routine Summary\n Section to all systems. \n \n 3. AFJXADHD It was reported that the security alert bulletin on\n 8. If the routines were unmapped as part of step 2, they should be\n returned to the Mapped set once the installation has run to\n completion. \n sensitive data access occasionally was not generated. A secondary\n access path was discovered through routine AFJXADHD. AFJXADHD is\n now modified to handle the generation of bulletins the same as in\n routine AFJXALRT (which was previously modified to handle this\n problem).\n \n \n 4. AFJXWCPM A site has reported a problem with BOLD being undefined at\n line OPTION in routine AFJXWCPM. This results from IOST(0) either\n being undefined or more probably set to null. Examination shows\n that in such cases BOLD and BOLF are equally apt to cause problems.\n The modification made to clear this problem is to hard set BOLD AND\n BOLF to null before IOST(0) is checked and BOLD and BOLF are\n updated. \n \n NOIS HISTORY: \n 1. AFJXPNHX Multiple sites have reported problems in routine AFJXPNHX\n =============\n The AFJXPNHX problem (undefined in the nightly purge) was reported in\n NOIS ATG-0996-31958, BUT-0896-22000, and FHM-0896-51544.\n \n There has been an access to restricted data problem uncovered in\n routine AFJXADHD (NOIS SBY-1296-30637).\n \n A site has reported a problem with BOLD being undefined at line OPTION\n in routine AFJXWCPM (NOIS DAY-0197-40124). This results from IOST(0)\n either being undefined or more probably set to null.\n at QNEW+2. It appears that multiple jobs, not necessarily the NHE\n \n PATCH HISTORY: \n ==============\n \n This patch clears the undefined in the nightly purge problems by\n presetting variables used in setting up VA FileMan multiple nodes to\n null. An environmental routine was added to ensure a proper\n sequencing. \n \n The AFJXPNHX changes in this patch were originally issued as\n purge, are running at the same time. These routines are\n AFJX*5.1*4 which was made entered in error due to an error in\n selection of routines contained (NOIS LEA-1196-41840). This has been\n updated correctly in AFJX*5.1*5.\n \n In the previous AFJX patches the Patch to Package file link was not\n included. As a reult, the package patch history is incomplete. The\n sites are requested to manually update the patch history in the\n Package File to indicate that patches 1 through 3 for AFJX are entered\n into the production routines. Patch 4 was declared to have been\n entered in error, hence need not be entered.\n manipulating and deleting messages in the mailboxes and mail\n \n \n Routine Summary: \n ================\n \n The following is a list of the routines included in this patch. The\n second line value of each of these routines will look like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;date \n * *\n global. This patch is generated to remove the effects of the\n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n \n AFJXPNHX 3809052 3887585 1,5 \n AFJXWCP8 6965692 6959884 5 \n AFJXADHD 15132754 15482706 5 \n AFJXWCPM 7335889 7680509 5 \n AFJXEN4 N/A 8495220 5 \n \n * From CHECK^XTSUMBLD \n unwanted job interference. \n \n Environmental Check Routine \n ===========================\n \n The environmental check routine is AFJXEN4 which checks the version \n and patch levels of the NHE package installed. Routine AFJXEN4 may be \n removed by the station upon successful installation of this patch. \n \n Installation Instructions: \n ==========================\n \n WHEN?: Anytime. This patch is so brief (only four routines and an \n environmental check routine) that it should not be queued. \n \n HOW LONG?: Installation will take less than 2 minutes. \n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan and respond \n YES at the prompt 'Want to Continue with load? YES// <return>. \n ===\n 2. Review your Mapped Routine set. If any of the routines listed in \n the ROUTINE SUMMARY section are mapped on your system, they should \n\n
\n \n \n \n Description:\n ============\n NOIS MAD-0300-41149: Madison reported that they are not\n receiving any Outpatient Pharmacy information when they\n selected 'Brief (12 Months) Pharmacy' from the Network Health\n Exchange menu. Routine AFJXREW and AFJXTRF were modified to\n correct this problem.\n \n Subject:\n \n \n List of Test Sites:\n ==================\n Madison, Hines, Salt-Lake, Tomah, N-Chicago\n \n \n \n ROUTINE SUMMARY \n =============== \n Correcting no display of Outpatient Pharmacy information\n \n The following routines are included in this patch. The\n second line of each of these routines now looks like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXREW 8174307 8173723 15,17,18\n AFJXTRF 5380483 5221348 17,18\n on NHE request.\n \n * From CHECK^XTSUMBLD\n \n \n \n \n Installation Instructions:\n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n \n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n INSTALL NAME: AFJX*5.1*18\n ===========\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n ================\n Category:\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n Routine\n \n.\n\n
\n \n Description:\n ============\n NOIS COA-0899-20344, TOM-0400-41371\n This patch corrects mismatch display. NHE menu Option\n #6 (print by type) is not displaying some of the\n components due to the mismatch between the header and\n the entries from file 537015. This patch modified some\n entries in File# 537015 to correct the problem.\n \n \n Subject:\n \n Test Sites:\n ===========\n Tomah, Coatsville, Fargo, Fayetteville\n \n \n Routine Summary:\n ================\n \n The following is a list of the routines included in this patch.\n Correction of mismatch component and removal \n The second line of each of these routines will look like:\n \n <tab>;;5.1;Network Health Exchange;*<<patch list>>**;date\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXUPD << NEW >> 765466 16\n \n * From CHECK^XTSUMBLD\n \n of additional unrelated information\n \n \n \n Installation Instructions:\n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n \n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Category:\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n INSTALL NAME: AFJX*5.1*16\n ===========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n Other\n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n \n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n.\n \n\n
\n \n \n \n Description:\n ============\n NOIS STC-0600-40949, CMO-0600-40937, BEC-0600-20733\n Number of sites reported that their Network Health\n Exchange Nightly Purge option was not working. Old records\n were accumulated and never gets purged. Routine AFJXPNHX was\n modified to correct this problem.\n \n \n \n \n \n List of Test Sites:\n ==================\n St. Cloud, Columbia, Beckley\n \n \n \n ROUTINE SUMMARY \n Subject:\n =============== \n \n The following routines are included in this patch. The\n second line of each of these routines now looks like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXPNHX 4205029 4214109 1,6,11,17,20\n Correcting Nightly Purge option\n \n \n * From CHECK^XTSUMBLD\n \n \n \n \n Installation Instructions:\n ==========================\n \n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n INSTALL NAME: AFJX*5.1*20\n Category:\n ===========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n Routine\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n \n \n.\n\n
\n NOIS SDC-0999-62404, MAN-0799-11140\n List of Test Sites:\n ==================\n San Diego, Philadelphia\n \n \n \n ROUTINE SUMMARY \n =============== \n \n The following routines are included in this patch. The\n Since Network Health Exchange has interfaced\n second line of each of these routines now looks like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXWCPM 7563694 4871774 6,22\n \n \n * From CHECK^XTSUMBLD\n with Health Summary package, the information\n \n \n \n \n Installation Instructions:\n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n indicating that NHE is running independently\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n with HS is considered invalid. Modified\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n INSTALL NAME: AFJX*5.1*22\n ===========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n routine AFJXWCPM to delete this information.\n ==== \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n\n
\n \n Routine\n \n \n Description:\n ============\n NOIS: NAS-0700-32185, TAM-0600-30805\n It was reported that there were times that sites\n had received incorrect data for a patient; however,\n when the user tries to make another NHE request for the\n same patient, the user gets the correct result.\n \n This problem is intermittent. Routines were modified\n to ensure that data being transferred from the spooler\n would be unique for each patient.\n \n \n \n List of Test Sites:\n ==================\n Nasville, Tampa\n \n \n \n \n ROUTINE SUMMARY \n =============== \n \n The following routines are included in this patch. The\n second line of each of these routines now looks like:\n \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXALRT 13885935 14041415 6,15,17,23\n AFJXPATS 3676275 3869099 23\n AFJXREW 8173723 8438064 15,17,18,23\n AFJXTRF 5221348 5666922 17,18,23\n \n * From CHECK^XTSUMBLD\n \n Subject:\n \n \n \n Installation Instructions:\n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n Correcting wrong data on the report\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n \n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n INSTALL NAME: AFJX*5.1*23\n ===========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n Category:\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n.\n\n
\n \n \n \n Description:\n ============\n BIG-1100-72033, COS-1000-42266, OKL-1199-70066\n Number of sites reported that Old messages of\n Postmaster baskets have been accumulating and not being\n deleted. This patch would clean up these 3 server\n baskets (AFJXSERVER, AFJXNHDONE and AFJXNETP) and would\n only leave the 7 day most current messages.\n \n \n \n \n \n List of Test Sites:\n ==================\n Columbus, Big Spring, Oklahoma\n \n \n \n Subject:\n ROUTINE SUMMARY \n =============== \n \n The following routines are included in this patch. The\n second line of each of these routines now looks like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n Deletion of Old messages in postmaster baskets\n AFJXPNHX 4214109 5367061 1,6,11,17,20,24\n \n \n * From CHECK^XTSUMBLD\n \n \n \n \n Installation Instructions:\n ==========================\n \n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n Category:\n INSTALL NAME: AFJX*5.1*24\n ===========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Routine\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n \n \n.\n\n
\n \n \n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \nCategory\n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s)\n INSTALL NAME: AFJX*5.1*26\n ===========\n--------\n \n Want KIDS to Rebuild Menu Tree Upon Completion of Install?? Yes//\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ====\n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Routine\n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n \n to completion.\n \n \n \n 8. Create a Mail Group called AFJX PATID FILTER BLOCK\n from the Mailman Menu.\n \n Select MailMan Option: 6 PERSONAL MAIL GROUP EDIT\n \n Select MAIL GROUP NAME: AFJX PATID FILTER BLOCK\n \n Are you adding 'AFJX PATID FILTER BLOCK' as a\n new MAIL GROUP? No// Y (Yes)\n MAIL GROUP NUMBER: <<DEFAULT NUMBER//>>\n MAIL GROUP COORDINATOR:\n MAIL GROUP NAME: AFJX PATID FILTER BLOCK Replace\n \n Select MEMBER: << YOUR NAME HERE!! >>\n \n \n \nDescription:\n 9. If you wish to display the report providing the numbers\n of incorrect information, you have to choose the option\n AFJX PATID REPORT from the menu option.\n \n \n ---------- SAMPLE OF OUTPUT -------------------\n \n \n \n \n-----------\nDEVICE: HOME// NETWORK\n \n \nNetwork Health Exchange Data Message report\n for PORTLAND.DOMAIN.EXT\n on Feb 16, 2001@13:56\n \nChecking NETWORK,HEALTH EXCHANGE messages...\n Checking WASTE basket...\n Checking IN basket........\n NOIS FAR-1200-40490 \n \nMessage count\n 20 messages in the 'IN' basket.\n 0 messages in the 'WASTE' basket.\n \n Site NV V T\n \n ALBUQUERQUE.DOMAIN.EXT 0 6 6\n ANN-ARBOR.DOMAIN.EXT 0 13 13\n .\n Fargo VAMC reported that they have received data on\n .\n .\n \n FRESNO.DOMAIN.EXT 0 14 14\n FT-HARRISON.DOMAIN.EXT 0 2 2\n GRAND-JUNCT.DOMAIN.EXT 0 3 3\n HONOLULU.DOMAIN.EXT 0 4 4\n KANSAS-CITY.DOMAIN.EXT 0 2 2\n \n \n \n the wrong patient when they received NHE requests from\n.\n Minneapolis. This patch will install a patient\n identification filter (PATID) that will match the patient\n identity on each Health Summary segment with the patient\n identifier (Name, Date of birth, Social Security Number) of\n the patient requested. If any of the Health Summary\n segments do not return data for the patient requested, then\n none of the data will be returned to the requestor. A\n message that instructs the requestor to resend the request\n is sent instead.\n \n \n This patch also includes an option for the receiving site\n that will report on the number of possible bad data\n messages that have been received by the site.\n \n This option works by comparing the patient's age with the\n age calculated from the Date of Birth that was reported in\n the Demographics segment of the NHE request. Note that if\n the request is made within a few weeks of the patient's\n birthday, and the age calculated by the Date of Birth\nSubject\n differs by one year from the patient's actual age, then\n this report option may falsly indicate that the record was\n invalid when in fact it was valid (data is for the correct\n patient).\n \n Since the server filter uses three data elements (Name,\n Social Security Number, and Date of birth), it is much more\n accurate than the report option at catching NHE data\n messages for the wrong patient. If the server site has\n loaded this patch then you can assume that the patient is\n-------\n correct regardless of what this report displays.\n \n How to tell if the server site has loaded this patch:\n \n Messages will have a line inserted after the patient ID:\n \n Subj: Reply for <TOTAL> Patient,A 111111111 MADISON.DOMAIN.EXT [#93164]\n 1 Feb 2001 15:05:05 -0600 (CST) 1936 lines\n From: <POSTMASTER@MADISON.DOMAIN.EXT> In 'IN' basket. Page 1\n ------------------------------------------------------------------------\n Install a Patient Identification (PATID) filter that matches\n 111111111^11744^SPIVEY,RICK^3010201.113723^SMA.ISC-ALBANY.DOMAIN.EXT^TOTAL\n *********CONFIDENTIAL Patient Data from MADISON.DOMAIN.EXT********* 02/01/01\n Patient,A 111-11-1111 DOB: SEP 3,1936\n \n -Patient ID verified on all data segments- <- This line is added to\n messages from server\n sites that have loaded\n the PATID filter patch. \n -------------------------- DEM - Demographics --------------------------\n \n the patient on each Health Summary segment with the patient\n \n \n List of Test Sites:\n ==================\n Fargo, Madison, Minneapolis, Clarksburg\n \n \n \n ROUTINE SUMMARY \n =============== \n requested.\n \n The following routines are included in this patch. The\n second line of each of these routines now looks like:\n \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXREW 8438064 8632159 15,17,18,23,26\n \n AFJXTRF 5666922 11122176 17,18,23,26\n AFJXVER NEW 19085828 26\n \n * From CHECK^XTSUMBLD\n \n \n Installation Instructions:\n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n\n
\n \n--------\n Routine\n \n \nDescription:\n-----------\n IT Service Request #20010603\n Headquarters requested to add Oncology component to the\n NHE report to provide essential information to doctors.\n \n \n \n Routine AFJ51P29 is a Post-init routine to add the Oncology\n component to file #537015. \n \n \n \n \n List of Test Sites:\n ==================\n Portland, Indianapolis, Philadelphia\nSubject\n \n \n \n ROUTINE SUMMARY \n =============== \n \n The following routines are included in this patch. The\n second line of each of these routines now looks like:\n \n \n-------\n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXREW 8632159 9153487 15,17,18,23,26,29\n AFJ51P29 << New >> 871747 29\n \n \n * From CHECK^XTSUMBLD\n \n Add Oncology component to the NHE report\n \n Installation Instructions:\n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n \n Backup a Transport Global\n \n Install Package(s)\n INSTALL NAME: AFJX*5.1*29\n ===========\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ====\n Want to DISABLE Scheduled Options, Menu Options, and\n \n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\nCategory\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n.\n\n
\nPatch AFJX*5.1*30\ncorrectly. The person who installs this patch is added as a member.\n necessary.\n==========================================================================\nYou are free to change the ORGANIZER, COORDINATOR, and MEMBER fields\nafterwards. Here's the group:\n\n--------------------------------------------------------------------------\nNAME: AFJX PATID FILTER BLOCK TYPE: public\n COORDINATOR: <someone>\nMEMBER: <someone>\nDESCRIPTION: If the patient ID filter blocks an incoming data request\nbecause it detected possible invalid health summary data, a warning is sent\n\nto members of this group.\n ORGANIZER: <someone>\n--------------------------------------------------------------------------\n\n\nNOIS CHA-0701-30431, TOG-0701-10186\nTest Site: Charleston, SC\nThe option AFJX PATID REPORT is included to correct any omissions.\nHere's the option:\n\nThis patch fixes some problems in patch AFJX*5.1*26.\n--------------------------------------------------------------------------\nNAME: AFJX PATID REPORT\n MENU TEXT: Network Health Exchange Check Messages\n TYPE: run routine CREATOR: <someone>\n PACKAGE: NETWORK HEALTH EXCHANGE\nDESCRIPTION: This option goes through all the messages in the Mailbox\nbelonging to NETWORK,HEALTH EXCHANGE, and checks to see if any contain "bad\ndata". Among the things checked is patient age, in an attempt to ensure\nthat the message contains data from the correct requested patient.\n \n \nA report on the results is produced.\n \nNote that this option is only needed to check messages received at your site\nbefore you installed patch AFJX*5.1*26. Messages received afterwards are\nchecked as they are received.\n ROUTINE: AFJXVER\n UPPERCASE MENU TEXT: NETWORK HEALTH EXCHANGE CHECK\n--------------------------------------------------------------------------\n\nNOTE: This patch should be installed during off hours, when user activity\nNOIS FTL-0701-51047\nis at a minimum. It requires patch AFJX*5.1*26.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nTest Site: Charleston, SC\nAFJXPRE * NEW * 2315825 30\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces the following new routine:\nAFJXPRE - This pre-init has no user-callable entry points.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*26.\nThe mail group AFJX PATID FILTER BLOCK should be PUBLIC. The pre-init\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\nin this patch checks for the existence of the mail group. If it's not\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: AFJX*5.1*30 Loaded from Distribution <date/time>\n ===========\n Install Questions:\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// YES\n ===\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nthere, it creates it. If it is there, it makes sure it's defined\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n\n
\nPatch AFJX*5.1*31\nsites. (See NOIS TUC-1001-60741, TUC-1001-60737, COA-1201-22358,\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nAFJXALRT 14041415 12200940 6,15,17,23,31\nAFJXPATL 6030128 295973 31\nAFJXPATS 3869099 299773 23,31\nAFJXPNHA 3165623 3584849 31\nAFJXPNHT 8297725 3201383 1,2,31\nAFJXPNHX 5367061 3073916 1,6,11,17,20,24,31\nAFJXPRE 2315825 8018806 30,31\nAFJXREW 9153487 2406 15,17,18,23,26,29,31\nWPB-1201-31089, and HUN-0701-22217.) Any closed sites in file 537025,\nAFJXSFAL 1759052 2271216 31\nAFJXTEMA 2294720 369080 31\nAFJXTRF 11122176 4969582 17,18,23,26,31\nAFJXVER 19085828 9198043 26,31\nAFJXWCBP 11230472 2912 1,31\nAFJXWCP1 11042104 6240335 1,31\nAFJXWCPB 10734470 2898 1,2,31\nAFJXWCPM 4871774 1802119 6,22,31\nAFJXWCPY 10927672 3082 1,31\n* Checksums produced by CHECK^XTSUMBLD\nNHE AUTHORIZED SITES file, will be ignored, and will not be selectable\n \nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*29 and *30.\nThe post-init for this patch will take approximately 1/2 hour for every\n400,000 records in file ^AFJ(537010.\n1. Users may be on the system during installation of this patch.\nwhen requests are being created.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: AFJX*5.1*31 Loaded from Distribution <date/time>\n ===========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n- Solves the undefined BOLD variable problem by no longer "bolding" output\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\non the menu. (See NOIS DAY-0797-41839.)\n\n- Solves the problem which occurred when Hudson Valley HCS changed option\nS.AFJXSERVER to use a resource device to limit it to running only one job\n\nat a time. (See NOIS HVH-1000-12729.)\n\nAdditionally,\n- Routines are rewritten to incorporate good programming practices.\n- Routine AFJXVER is modified to check both the B and C xrefs in file 4.2,\ninstead of just the B xref, when looking up a domain name.\n- Routine AFJXPNHX is modified to use MailMan APIs to delete messages from\nthe NHE user's mailbox, instead of using direct global edits.\n- The Identifiers in file 537000 are changed to "Write" Identifiers. The\nPost-Init, ^AFJXPRE, will effect the change.\nNOIS TUC-1001-60741, TUC-1001-60737, HUN-0701-22217, DAY-0797-41839,\n- The DDs of fields in files 537000 and 537025, which are free-text domain\nnames, are changed to pointer-type fields, pointing to file 4.2. The DD\nof the field in file 537010 which points to file 537025 is changed to\npoint to file 4.2. It is necessary to do this because domain names can,\nand do, change. The Post-Init, ^AFJXPRE, will go through the records in\nthose files and change the data in the affected fields to pointers to file\n4.2. It will take approximately 1/2 hour for every 400,000 records in file\n^AFJ(537010. Here are the new definitions for the affected fields:\n\nSTANDARD DATA DICTIONARY #537000 -- VAMC NETWORK HEALTH EXCHANGE FILE\n HVH-1000-12729, HOU-0801-70115, COA-1201-22358, WPB-1201-31089\nSTORED IN ^AFJ(537000, (VERSION 5.1)\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n537000,8 REQUESTING PLACE 1;1 POINTER TO DOMAIN FILE (#4.2)\n LAST EDITED: NOV 15, 2001\n HELP-PROMPT: Enter the domain where the request originated.\n DESCRIPTION:\n FACILITY REQUESTING DATA\n CROSS-REFERENCE: 537000^C\nTest Site: Huntington, WV; Houston, TX\n 1)= S ^AFJ(537000,"C",$E(X,1,30),DA)=""\n 2)= K ^AFJ(537000,"C",$E(X,1,30),DA)\n REQUESTING PLACE FOR PATIENT DATA\n\nSTANDARD DATA DICTIONARY #537010 -- VAMC NETWORK PATIENT FILE\nSTORED IN ^AFJ(537010, (VERSION 5.1)\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n537010,3 Records Available At 1;0 POINTER Multiple #537010.04\n\n\n537010.04,.01 Records Available At 0;1 POINTER TO DOMAIN FILE (#4.2)\n LAST EDITED: NOV 15, 2001\n HELP-PROMPT: Enter a domain which has records on the\n patient.\n CROSS-REFERENCE: 537010.04^B\n 1)= S ^AFJ(537010,DA(1),1,"B",$E(X,1,30),DA)=""\n 2)= K ^AFJ(537010,DA(1),1,"B",$E(X,1,30),DA)\n\nSTANDARD DATA DICTIONARY #537025 -- VAMC NETWORK HEALTH AUTHORIZED SITES FILE \nThis patch does the following:\nSTORED IN ^AFJ(537025, (VERSION 5.1)\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n---------------------------------------------------------------------------\n537025,.01 NAME 0;1 POINTER TO DOMAIN FILE (#4.2)\n (Required)\n INPUT TRANSFORM: S DIC("S")="I $P(^(0),U,2)'[""C""" D ^DIC\n K DIC S DIC=DIE,X=+Y K:Y<0 X\n LAST EDITED: NOV 15, 2001 \n HELP-PROMPT: Enter the name of an authorized site. \n\n DESCRIPTION: Enter the name of the sites that you will send\n data requests to and receive data from. \n (Include your own site). \n SCREEN: S DIC("S")="I $P(^(0),U,2)'[""C"""\n EXPLANATION: You may not select closed domains.\n CROSS-REFERENCE: 537025^B \n 1)= S ^AFJ(537025,"B",$E(X,1,30),DA)=""\n 2)= K ^AFJ(537025,"B",$E(X,1,30),DA)\n\nNOTE: This patch should be installed during off hours, when user activity\n- Prevents NHE from accepting requests from or sending requests to closed\nis at a minimum. It requires patch AFJX*5.1*29 and *30.\nThe post-init for this patch will take approximately 1/2 hour for every\n400,000 records in file ^AFJ(537010.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \n Before After\n\n\n \n 7 routines (AFJXADHD, AFJXALRT, AFJXPNHX, AFJXWCL1, AFJXWCP8, \n \n The following is a list of the routines included in this patch. The \n second line value of each of these routines will look like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;date \n * *\n Routine Name Before Patch After Patch Patch List \n ============ ============ =========== ==========\n \n AFJXADHD 15132754 15812358 6 \n AFJXWCPM, and AFJXWPR2) are modified in this patch. \n AFJXALRT 16599231 16928883 6 \n AFJXPNHX 3809052 3887585 1,6 \n AFJXWCL1 10604702 10819424 6\n AFJXWCP8 6965692 6959884 6 \n AFJXWCPM 7335889 7563694 6 \n AFJXWPR2 6734179 6949871 6 \n AFJXEN6 N/A 8495682 6 \n \n * From CHECK^XTSUMBLD \n \n \n To test if the transport has been corrupted, you can use the \n "Verify Package Integrity" option. This option is under Utilities \n under the KIDS menu. It will compare the checksums in the build \n with the current checksums and list any that differ. \n \n Environmental Check Routine \n ===========================\n \n The environmental check routine is AFJXEN6 which checks the version \n and patch levels of the NHE package installed. Routine AFJXEN6 may be \nNOIS: \n removed by the station upon successful installation of this patch. \n \nInstallation Instructions: \n==========================\n \n WHEN? Anytime. This patch is so brief (only seven routines) that it \n should not be queued. \n \n HOW LONG? Installation will take less than 2 minutes. \n \n====\n Use the INSTALL/CHECK MESSAGE option on the PackMan and respond \n YES at the prompt 'Want to Continue with load? YES// <return>. \n ===\n \n 1. Users are allowed to be on the system during the installation. \n 2. It is not necessary to place TaskMan in a WAIT/STOP state. \n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? Yes// <return>, respond YES or <return>. When\n ===\n prompted to select the option(s) you would like to place out of\n NOIS: REN-0297-60708, BAN-0297-11202, and ATG-0297-31510\n order, enter the following:\n \n AFJXNHEX REQUEST \n ================\n AFJX PURGE NIGHTLY \n ==================\n \n 4. Review your Mapped Routine set. If any of the routines listed in \n the ROUTINE SUMMARY section are mapped on your system, they \n should be unmapped at this time. \n AFJXWCLI - DK RES errors reported in the above NOISs are repaired\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This \n option will load the KIDS package onto your system. \n 6. The patch has now been loaded into a Transport global on your \n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. On the KIDS Installation menu, you may elect\n to use the following options: \n a. Verify checksums in the Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the Transport Global. \n by this patch's changes in routine AFJXWCLI.\n b. Compare Transport Global to the Current System - this option \n will allow you to view all changes that will be made when the \n patch is installed. It compares all components of the patch \n (routines, DDs, templates, etc.). \n c. Back up a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \n back up any other changes such as DDs or templates. \n Use the Install Package(s) options and select the package: \n \n AFJX*5.1*6. \n Multiple sites reported unexplained DK RES and similar errors \n ==========\n \n 8. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n CPUs. Alternatively, you can wait until the installation is \n complete and move the routines listed in the Routine Summary \n Section to all systems. \n 9. If the routines were unmapped as part of step 4, they should be \n returned to the mapped set once the installation has run to \n completion. \n with NHE over the last year. The problem was located in \nPrerequisites: \n routine AFJXWCL1, where, in module INTRP, the variable \n GMJ was used as a variable in a FOR loop. First the module \n RDNODE was called, then module WRTGRM was called, \n which hard SET the variable GMJ to "GRAM" without any \n scoping of the variable. If there were any nodes that collated\n after "GRAM," an endless loop resulted. In this loop the \n global ^TMP("AFHS",$J,CT,0) was set with CT incremented\n each time. \n The routine was modified to change the program flow so that \n the original sequencing of data was maintained, but the\n============== \n offending hard SET of the variable GMJ was avoided.\n \n NOIS: ATG-0996-31958, BUT-0896-22000, FHM-0896-51544, and LEA-1196-41840\n AFJXPNHX - Multiple sites have reported problems in routine AFJXPNHX at\n QNEW+2. It appears that multiple jobs, not necessarily the\n NHE purge, are running at the same time. These routines are\n manipulating and deleting messages in the mailboxes and mail \n global. This patch is generated to remove the effects of the\n unwanted job interference. (The changes in AFJXPNHX were\n originally issued in AFJX*5.1*4 which was marked 'Entered in\n \n Error' due to an error in selection of routines contained.)\n \n AFJXWCP8 - The routine AFJXWCP8 was found to contain references to file\n 6 and to file 16. The pointers are now properly referenced to\n file 200. \n \n NOIS: SBY-1296-30637\n AFJXADHD - It was reported that the security alert bulletin on sensitive\n data access occasionally was not generated. A secondary\n access path was discovered through routine AFJXADHD. AFJXADHD\n Install patch AFJX*5.1*1 prior to the installation of this patch. \n is now modified to handle the generation of bulletins the\n same as in routine AFJXALRT (which was previously modified to\n handle this problem).\n \n NOIS: DAY-0297-40622\n AFJXADHD and AFJXALRT - Dayton reported that a spurious global node \n ^AFJ(537000,-1,0) was being set when a FILE^DICN failed and \n S DA=+Y returned a -1. Then S ^AFJ(537000,DA,1) was performed.\n A condition was added in routines AFJXADHD and AFJXALRT to\n that SET to make it S:DA>0 and thus corrected the problem. \n \n \n NOIS: DAY-0197-40124\n AFJXWCPM - A site has reported a problem with BOLD being undefined at\n line OPTION in routine AFJXWCPM. This results from IOST(0)\n either being undefined or set to null.\n Examination shows that in such cases BOLD and BOLF are\n equally apt to cause problems. The modification made to clear\n this problem is to hard SET BOLD and BOLF to null before\n IOST(0) is checked and BOLD and BOLF are updated.\n \nDescriptive Text:\n NOIS: HOU-0197-72340\n AFJXWPR2 - Houston reported that there was a syntax error in \n routine AFJXWPR2 that caused problems with SOAP entries. This\n is corrected.\n \n PATCH HISTORY: \n ==============\n \n The AFJXPNHX changes in this patch were originally issued as \n AFJX*5.1*5 which was declared to have been 'Entered in Error' due\n=================\n to an error in selection of routines contained (NOIS CIN-0397-40969).\n \n This has been updated correctly in AFJX*5.1*6. \n \n In the previous AFJX patches, the Patch to Package file link was not \n included. As a result, the package patch history is incomplete. The \n sites are requested to manually update the patch history in the \n Package File to indicate that patches 1 through 3 for AFJX are entered\n into the production routines. Patches 4 and 5 were declared to have \n been 'Entered in Error,' hence need not be entered. (This patch will\n \n update the package patch history for AFJX*5.1*6 only.)\n \nTest Sites: \n===========\n \n Bath, Reno, Houston, Dayton \n \n \nRoutine Summary: \n================\n\n\nPatch AFJX*5.1*32\nInstead of sending two messages in response to a user query (one with the\nrequested information to the NETWORK,HEALTH EXCHANGE user; the other to a\nserver which alerts the requesting user to it), this patch sends just one\nmessage to both. The process is thus simplified.\n\nThe two-message process also sometimes causes problems because of timing\nissues. A user can be alerted that the request has been completed, but\nwhen the user tries to view the results, it can't be found. This is\nbecause MailMan hasn't yet delivered the first message to the\nNETWORK,HEALTH EXCHANGE user. This patch and its one-message process\n \nmakes it impossible for this to happen.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*31.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \nNOIS CAH-0602-31615 (Remedy Ticket HD8220/CHG2653)\n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nAFJXALRT 12200940 11647156 6,15,17,23,31,32\nAFJXSFAL 2271216 2275636 31,32\nAFJXWCPD 5587435 2914 32\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n==========================================================================\nTest Site: Central Alabama HCS; Birmingham, AL\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*31.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: AFJX*5.1*32 Loaded from Distribution <date/time>\n ===========\nIf the NETWORK,HEALTH EXCHANGE user has been terminated, the requesting\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nuser never sees the results of a query after processing the alert. This\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\npatch makes it possible for the requesting user to see the results.\n\n\n
\nPatch AFJX*5.1*33\nbe made of the status of the NETWORK,HEALTH EXCHANGE user every time a\nuser enters option AFJXNHEX REQUEST (Network Health Exchange Options ...),\nand if the NETWORK,HEALTH EXCHANGE user is terminated, the option will not\nbe usable.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*32.\n==========================================================================\n \nROUTINES:\n \nThe second line of the routine now looks like:\n ;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nAFJXPNHI 7299167 2929 2,7,33\nAFJXSFAL 2275636 1844361 31,32,33\nAFJXWCPM 1802119 3332319 6,22,31,33\n* Checksums produced by CHECK^XTSUMBLD\nNOIS: FNC-0103-30068\n \nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*32.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \nTest Site: Fayetteville, NC\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan. Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: AFJX*5.1*33 Loaded from Distribution <date/time>\n ===========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nIf the NETWORK,HEALTH EXCHANGE user has been terminated, requests that\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nusers make are not delivered to the NETWORK,HEALTH EXCHANGE user.\nConsequently, it is not possible to print or view completed requests\nwhich were made after termination. In order to remedy this, a check will\n\n
\nPatch AFJX*5.1*34\nAFJXADD1, AFJXPNHF, AFJXPNHI, AFJXREW, AFJXWCBP, AFJXWCPB, AFJXWCPD, AFJXWCPY\n\nThis patch also changes the check for a printer from IOST["C-" to\n$E(IOST,1,2)="C-".\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*33.\n==========================================================================\n \nROUTINES:\n \nThe second line of the routine now looks like:\n ;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nAFJXADD1 452636 none - deleted\nAFJXMABX 13418618 4042833 1,2,10,11,15,34\nAFJXMBOX 13056481 2108840 2,11,34\nAFJXPNHF 12346036 none - deleted\nNOIS: TOM-0303-40892\nAFJXPNHI 2929 none - deleted\nAFJXREW 2406 none - deleted\nAFJXSFAL 1844361 1758614 31,32,33,34\nAFJXWCBP 2912 none - deleted\nAFJXWCP1 6240335 6240234 1,31,34\nAFJXWCPB 2898 none - deleted\nAFJXWCPD 2914 none - deleted\nAFJXWCPM 3332319 3244105 6,22,31,33,34\nAFJXWCPY 3082 none - deleted\n* Checksums produced by CHECK^XTSUMBLD\nTest Site: Tomah, WI\n \nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*33.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan. Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\nAt some prompts, there are no time-outs. At other prompts, time-outs may\n Select INSTALL NAME: AFJX*5.1*34 Loaded from Distribution <date/time>\n ===========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nresult in infinite prompt loops. This patch fixes that.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\n\nThis patch also deletes obsolete routines:\n\n
\nPatch AFJX*5.1*35\n=====================================================================\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\n Select one of the following:\n\n 1 Brief (12 months) Medical Record Information\n 2 Total Medical Record Information\n 3 Brief (12 months) Pharmacy Information\n 4 Total Pharmacy Information\n 5 Print (Completed Requests Only)\n 6 Print By Type of Information (Completed Requests)\n\n \nOption #6 chops off "Discharge Summary" and "Progress Notes" before\ndisplaying them completely. They can be fully seen in option #5.\nThis patch fixes the problem.\n\nAs an added bonus, we are adding a cross reference to the NAME (#.01)\nfield of the VAMC NETWORK HEALTH TYPES (#537015) file. The new C cross\nreference will be all upper-case, so that the user doesn't have to enter\nthe exact mixed case component name during ^DIC lookups. The post-init,\nPOST^AFJXYP35, will create the new cross reference.\n\nNOIS: WRJ-0403-11925, SFC-0403-61371\nSTANDARD DATA DICTIONARY #537015 -- VAMC NETWORK HEALTH TYPES FILE\nSTORED IN ^AFJ(537015, (VERSION 5.1)\n\nDATA NAME GLOBAL DATA\nELEMENT TITLE LOCATION TYPE\n----------------------------------------------------------------------------\n537015,.01 NAME 0;1 FREE TEXT (Required)\n INPUT TRANSFORM: K:$L(X)>30!(X?.N)!($L(X)<3)!'(X'?1P.E) X\n LAST EDITED: APR 30, 2003\n HELP-PROMPT: NAME MUST BE 3-30 CHARACTERS, NOT NUMERIC OR\nTest Sites: White River Junction, VT; San Francisco VAMC; Erie, PA\n STARTING WITH PUNCTUATION\n CROSS-REFERENCE: 537015^B\n 1)= S ^AFJ(537015,"B",$E(X,1,30),DA)=""\n 2)= K ^AFJ(537015,"B",$E(X,1,30),DA)\n\n FIELD INDEX: C (#30) REGULAR IR LOOKUP & SORTING\n Short Descr: All upper-case\n Description: This xref is all upper-case to ease DIC\n lookups.\n Set Logic: S ^AFJ(537015,"C",$E(X,1,30),DA)=""\n\n Kill Logic: K ^AFJ(537015,"C",$E(X,1,30),DA)\n Whole Kill: K ^AFJ(537015,"C")\n X(1): NAME (537015,.01) (Subscr 1) (Len 30)\n (forwards)\n Transform (Storage): S X=$$UP^XLFSTR(X)\n Transform (Lookup): S X=$$UP^XLFSTR(X)\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*34.\n==========================================================================\nThe problem concerns the following menu in option [AFJXNHEX REQUEST]\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nAFJXMABX 4042833 4533362 1,2,10,11,15,34,35\nAFJXYP35 * NEW * 45221 35\nNetwork Health Exchange Options:\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces the following new routine:\nAFJXYP35 is a post-init, which will be deleted once it's run.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch AFJX*5.1*34.\n1. Users may be on the system during installation of this patch.\n\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan. Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\nVistA Network Health Exchange Menu TRUSTED,USER\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: AFJX*5.1*35 Loaded from Distribution <date/time>\n ===========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n\n
\nSubject: Missing and undefined data\n \n 1. Users are allowed to be on the system during the installation.\n 2. It is not necessary to place TaskMan in a WAIT/STOP state.\n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? Yes// <return>, respond YES. When prompted\n ===\n to select the option(s) you would like to place out of order,\n enter the following:\n \n AFJXNHEX REQUEST\n ================\n \n \n 4. Review your Mapped Routine set. If any of the routines listed in\n the ROUTINE SUMMARY section are mapped on your system, they\n should be unmapped at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System Menu, select\n the Installation menu. On the KIDS Installation menu, you may\nPrerequisites:\n elect to use the following options:\n a. Verify checksums in the Transport Global - this option will\n allow you to ensure the integrity of the routines that are in\n the Transport Global.\n b. Compare Transport Global to the Current System - this option\n will allow you to view all changes that will be made when the\n patch is installed. It compares all components of the patch\n (routines, DDs, templates, etc.).\n c. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n==============\n backup any other changes such as DDs or templates.\n Use the Install Package(s) options and select the package:\n \n AFJX*5.1*7.\n ==========\n \n 8. If the routines were unmapped as part of step 4, they should be\n returned to the mapped set once the installation has run to\n completion.\n \n Install patch AFJX*5.1*6 prior to the installation of this patch.\n \n \nNOIS:\n====\n \n \nNOIS: MIW-0397-31028\nAFJXWCPL - An uncoordinated addition of a new cross-reference in Lab\nPackage resulted in an undefined at NXTST+2^AFJXWCPL. The code at\nCHSET+7 was modified to exclude the handling of the new\ncross-reference.\n \nNOIS: CLL-0397-42751\nAFJXPNHI - The variable I was reported to be undefined at\nPART2^AFJXPNHI. This variable was used as a dummy index for a For\nCategory: \nLoop and was not used elsewhere. The For Loop was changed to an\nargumentless one.\n \nNOIS: DAN-0497-41347\nAFJXPNHI - The site was reporting that NHE reports were not being\nfound by the alerts mechanism. Investigation found two problems.\n \nThe first was that the parsing mechanism that parsed the titles in\nthe Alerts Message was using spaces in locating data. Since the\nspaces were used the data after the patient name was mis-parsed if\n - Routine\nthere was a third item present in the name (such as Jr/Sr. a number,\netc). The code in AFJXPNHI was modified to use other characteristics\nto allow a proper parsing.\n \nThe second is that if the patients name is spelled differently at\nthe server and client the Alerts will not display the messages since\na built in check (the two names are the same) fails. Since this is a\ndesign feature a decision or how to handle this is still open\n(Follow the completed reports model where this is available, or\nextend the security to the complete report).\n \n \nTest Sites:\n===========\n \n Milwaukee, Chillicothe, Danville\n \n \nRoutine Summary:\n================\n \nDescription: \n The following is a list of the routines included in this patch.\n The second line value of each of these routines will look like:\n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;date\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXEN7 N/A 6822968 7\n AFJXPNHI 6813365 7299167 2,7\n AFJXWCPL 7386440 7733101 7\n============\n \n * From CHECK^XTSUMBLD\n \n To test if the transport has been corrupted, you can use the\n "Verify Package Integrity" option. This option is under\n Utilities under the KIDS menu. It will compare the checksums in\n the build with the current checksums and list any that differ.\n \nEnvironment Check Routine:\n=========================\n \n \n The routine AFJXEN7 checks to see if NHE version 5.1 with patch\n 6 is installed before installation proceeds. On failure, a\n message is sent to the user detailing the problems encountered.\n The routine AFJXEN7 may be removed upon successful patch 7\n installation.\n \n \nInstallation Instructions:\n==========================\n 2 routines (AFJXPNHI, AFJXWCPL) are modified in this patch.\n \n WHEN? Anytime. This patch is so brief (only two routines) that it\n should not be queued.\n \n HOW LONG? Installation will take less than 2 minutes.\n \n Use the INSTALL/CHECK MESSAGE option on the PackMan and respond\n YES at the prompt 'Want to Continue with load? YES// <return>.\n ===\n \n\n
\n Subject:\n ============\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n Use the Install Package(s) options and select the package:\n \n AFJX*5.1*8.\n ==========\n \n 8. If the routines were unmapped as part of step 4, the mapped set\n should be rebuilt once the installation has run to completion.\n \n Results of a lab test performed at the site are obtained via\n \n .\n Network Health Exchange. NHE has been providing only 4 digits\n instead of 6 digits or more. This patch will rectify this\n truncation of data.\n \n Facilities should undertake a review of whether clinicians\n have looked up viral load results using NHE, and whether\n clinical judgments have been based on these values rather than\n looking up the results in VistA directly. If this has happened\n Resolving truncation of data\n then it must be determined whether a patient's treatment\n protocol is accurate and that the laboratory values were not\n truncated resulting in inappropriate treatment. Corrective\n actions should be taken immediately.\n \n \n NOIS: CIN-0698-41578\n Delay in the treatment of a patient being followed in\n the Extended Infectious Disease Clinic at a tertiary VISN\n facility. Patient was prescribed a single antiretroviral\n \n medication based on a viral load value of 3,090 obtained\n through the Network Health Exchange (NHE). Three\n antiretroviral agents should have been prescribed based on\n the actual value of 30,090. The NHE viral load value field\n only allowed for a 4 digit value to be transmitted, when in\n fact, the value is often 6 digits long or more.\n \n \n Test Sites:\n ===========\n \n \n Dayton, Cincinnati, Columbus, Wilkesbarre, Birmingham, Dublin\n \n \n \n Routine Summary:\n ================\n \n The following is a list of the routines included in this patch. The\n second line value of each of these routines will look like:\n Category:\n \n <tab>;;5.1;Network Health Exchange;**8**;Jan 23, 1996\n \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXCAH 5679268 5679688 8\n AFJXCAHS 6214244 6214664 8\n \n \n - Routine\n \n * From CHECK^XTSUMBLD\n \n \n Installation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation; \n however, it is highly recommended to do the installation \n when a minimal number of users are on the system.\n \n 2. It is not necessary to place TaskMan in a WAIT/STOP state.\n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? Yes// <return>, respond YES. When prompted to select\n ===\n the option(s) you would like to place out of order, enter the\n following:\n \n AFJXNHEX REQUEST\n ================\n \n \n 4. Review your Mapped Routine set. If any of the routines listed in\n the ROUTINE SUMMARY section are mapped on your system, they\n should be unmapped at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System Menu, select\n the Installation menu. On the KIDS Installation menu, you may elect\n to use the following options:\n Description:\n a. Verify checksums in the Transport Global - this option will\n allow you to ensure the integrity of the routines that are in\n the Transport Global.\n b. Print Transport Global and Compare Transport Global to the\n Current System - this option will allow you to view all\n changes that will be made when the patch is installed. It\n compares all components of the patch (routines, DDs,\n templates, etc.).\n \n c. Backup a Transport Global - this option will create a backup\n\n
\n \n \n should be rebuilt once the installation has run to completion.\n Description:\n ============\n This patch was created to reformat the Chem & Hematology\n section of the Network Health Exchange report (without\n exceeding more than 80 characters per line). Previously,\n the lab results on the report would only display a maximum\n of seven characters. This code has been changed to\n display a maximum of 16 characters.\n \n Subject:\n \n \n NOIS: HAM-0798-21999\n Sites have requested that Network Health Exchange\n accomodate more than 7 characters on the lab\n results. \n \n \n \n Test Sites:\n Reformatting report to accomodate maximum of\n ===========\n \n Cincinnati, Columbus, Wilkes Barre, Dublin, Richmond\n \n \n \n Routine Summary:\n ================\n \n The following is a list of the routines included in this patch.\n 16 characters of Lab Results\n The second line value of each of these routines will look like:\n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Jan 23, 1996\n \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXCAH 5679688 5571442 8,10\n AFJXCAHB 2928193 2909852 10\n AFJXCAHS 6214664 6106418 8,10\n \n AFJXMABX 12595367 12990713 1,2,10\n \n \n * From CHECK^XTSUMBLD\n \n \n Installation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation;\n \n however, it is highly recommended to do the installation\n when a minimal number of users are on the system.\n 2. It is not necessary to place TaskMan in a WAIT/STOP state.\n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? Yes// <return>, respond YES. When prompted to select\n ===\n the option(s) you would like to place out of order, enter the\n following:\n \n AFJXNHEX REQUEST\n Category:\n ================\n \n 4. Review your Mapped Routine set. If any of the routines listed in\n the ROUTINE SUMMARY section are mapped on your system, they\n should be unmapped at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System Menu, select\n - Routine\n the Installation menu. On the KIDS Installation menu, you may elect\n to use the following options:\n a. Verify checksums in the Transport Global - this option will\n allow you to ensure the integrity of the routines that are in\n the Transport Global.\n b. Print Transport Global and Compare Transport Global to the\n Current System - this option will allow you to view all\n changes that will be made when the patch is installed. It\n compares all components of the patch (routines, DDs,\n templates, etc.).\n \n \n c. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n Use the Install Package(s) options and select the package:\n \n AFJX*5.1*10.\n ===========\n \n 8. If the routines were unmapped as part of step 4, the mapped set\n\n
\nSubject:\n ============\n Revision of Network Health Exchange to comform with the\n new person file.\n \n \n NOIS: FNC-1098-32619\n Testing site for deletion of file 3,6,1,6,20 reported that NHE\n was bombing out. This problem was caused by NHE pointing at\n file #6. Routines were modified to resolve this problem.\n \n New person file compliance\n \n \n Test Sites:\n ===========\n Fayetteville\n \n \n \n Routine Summary:\n ================\n \n \n The following is a list of the routines included in this patch.\n The second line value of each of these routines will look like:\n \n <tab>;;5.1;Network Health Exchange;*<<patch list>>**;date\n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXRADI 5617774 5630558 14\n AFJXWCP9 7495089 7502091 14\n \n \n * From CHECK^XTSUMBLD\n \n \n \n Installation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation;\n however, it is highly recommended to do the installation\n Category:\n when a minimal number of users are on the system.\n 2. It is not necessary to place TaskMan in a WAIT/STOP state.\n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? Yes// <return>, respond YES. When prompted to select\n ===\n the option(s) you would like to place out of order, enter the\n following:\n \n AFJXNHEX REQUEST\n ================\n - Routine\n \n 4. Review your Mapped Routine set. If any of the routines listed in\n the ROUTINE SUMMARY section are mapped on your system, they\n should be unmapped at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System Menu, select\n the Installation menu. On the KIDS Installation menu, you may elect\n \n to use the following options:\n a. Verify checksums in the Transport Global - this option will\n allow you to ensure the integrity of the routines that are in\n the Transport Global.\n b. Print Transport Global and Compare Transport Global to the\n Current System - this option will allow you to view all\n changes that will be made when the patch is installed. It\n compares all components of the patch (routines, DDs,\n templates, etc.).\n c. Backup a Transport Global - this option will create a backup\n \n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n Use the Install Package(s) options and select the package:\n \n AFJX*5.1*14.\n ===========\n \n 8. If the routines were unmapped as part of step 4, the mapped set\n should be rebuilt once the installation has run to completion.\n Description:\n\n
\n \n Description:\n.\n ============\n Due to patches for Y2K compliance, Network Health Exchange is\nchanging its code. Currently, NHE is reading the dates\nincorrectly. Routines were modified to resolve the extraction of\ndates from the records correctly.\n \n \n \n NOIS: SBY-0598-30445, CMO-0698-42277\n Subject:\n Sites reported that valid records were purged by the Network\nHealth Exchange Nightly Purge. Due to NHE is reading incorrect\ndates, valid records were deleted. Records that are 7 days old\nare to be kept not purged.\n \n \n \n Test Sites:\n ===========\n Columbia, Salisbury\n Correcting dates to prevent records getting purged\n \n \n \n Routine Summary:\n ================\n \n The following is a list of the routines included in this patch.\n The second line value of each of these routines will look like:\n \n <tab>;;5.1;Network Health Exchange;*<<patch list>>**;date\n \n \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXMABX 12990713 13034650 1,2,10,11\n AFJXMBOX 13034280 13056481 2,11\n AFJXPNHF 12324580 12346036 2,11\n AFJXPNHX 3887585 2605376 1,6,11\n \n \n \n * From CHECK^XTSUMBLD\n \n \n Installation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation;\n however, it is highly recommended to do the installation\n when a minimal number of users are on the system.\n 2. It is not necessary to place TaskMan in a WAIT/STOP state.\n Category:\n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? Yes// <return>, respond YES. When prompted to select\n ===\n the option(s) you would like to place out of order, enter the\n following:\n \n AFJXNHEX REQUEST\n ================\n \n 4. Review your Mapped Routine set. If any of the routines listed in\n - Routine\n the ROUTINE SUMMARY section are mapped on your system, they\n should be unmapped at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System Menu, select\n the Installation menu. On the KIDS Installation menu, you may elect\n to use the following options:\n a. Verify checksums in the Transport Global - this option will\n \n allow you to ensure the integrity of the routines that are in\n the Transport Global.\n b. Print Transport Global and Compare Transport Global to the\n Current System - this option will allow you to view all\n changes that will be made when the patch is installed. It\n compares all components of the patch (routines, DDs,\n templates, etc.).\n \n c. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n \n backup any other changes such as DDs or templates.\n Use the Install Package(s) options and select the package:\n \n AFJX*5.1*11.\n ==========\n \n 8. If the routines were unmapped as part of step 4, the mapped set\n should be rebuilt once the installation has run to completion.\n \n \n\n
\n \n \n Use the Install Package(s) options and select the package:\n \n AFJX*5.1*15.\n ===========\n \n 8. If the routines were unmapped as part of step 4, the mapped set\n should be rebuilt once the installation has run to completion.\n \n \n 9. The following routines would automatically be deleted:\n Description:\n \n AFJXADHB AFJXEN7 AFJXSPTH AFJXWCP8\n AFJXADHD AFJXEN9 AFJXSURY AFJXWCP9\n AFJXADPB AFJXEND AFJXUNDS AFJXWCPA\n AFJXALER AFJXFIX AFJXUNIT AFJXWCPC\n AFJXBLOO AFJXGMR1 AFJXVISI AFJXWCPE\n AFJXCAH AFJXLABO AFJXVITA AFJXWCPF\n AFJXCAHB AFJXLRM AFJXVITS AFJXWCPG\n AFJXCAHS AFJXLRM1 AFJXWCCW AFJXWCPH\n AFJXCYTO AFJXLROC AFJXWCL1 AFJXWCPJ\n ============\n AFJXDCS1 AFJXMEDI AFJXWCL2 AFJXWCPL\n AFJXDCSU AFJXNTEG AFJXWCL4 AFJXWCPN\n AFJXDIE2 AFJXORDR AFJXWCL5 AFJXWCPR\n AFJXDIET AFJXPHCY AFJXWCL7 AFJXWCPZ\n AFJXDISA AFJXPHIV AFJXWCL8 AFJXWPN\n AFJXDM1 AFJXPUL2 AFJXWCL9 AFJXWPN1\n AFJXEN2 AFJXPULM AFJXWCP3 AFJXWPR2\n AFJXEN3 AFJXRADI AFJXWCP4 AFJXWPRG\n AFJXEN4 AFJXRALT AFJXWCP5\n AFJXEN6 AFJXRATS AFJXWCP6\n \n AFJXRIMP AFJXWCP7\n \n \n.\n This patch provides for NHE to call into the Health Summary\n package and retrieve the same information and display the\n same data to the NHE users as provided by Health Summary.\n \n This patch makes the software Health Summary and Y2K\n compliant.\n \n \n Since this software now uses the spooling device, it is\n important to note that a spool device to which Health\n Summary output may be directed, should be entered in the\n Health Summary Parameters File (142.99). The spooling\n device should be a legal device in the Device File which\n points to a directory and file on the host system.\n \n AFJXADD1 - routine to put 3 additional Type entries (Current\n Order, Surgery Non Or Procedures & Compensation & Pension\n Subject:\n Exams) into file #537015.\n \n This patch will delete all the NHE routines that are no\n longer used for collecting data.\n \n \n \n Test Sites:\n ===========\n Clarksburg, Wilkes-Barre, Long Beach\n Network Health Exchange interface with Health Summary\n \n \n \n Routine Summary:\n ================\n \n The following is a list of the routines included in this patch.\n The second line of each of these routines will look like:\n \n <tab>;;5.1;Network Health Exchange;*<<patch list>>**;date\n \n \n Routine Name Before Patch After Patch Patch List\n ============ ============ =========== ==========\n AFJXADD1 << NEW >> 469389 15\n AFJXALRT 16928883 13284766 6,15\n AFJXMABX 13034650 13418618 1,2,10,11,15\n AFJXREW << NEW >> 5392938 15\n \n \n * From CHECK^XTSUMBLD\n \n \n \n \n Installation Instructions:\n ==========================\n \n 1. Users are allowed to be on the system during the installation;\n however, it is highly recommended to do the installation\n when a minimal number of users are on the system.\n 2. It is not necessary to place TaskMan in a WAIT/STOP state.\n Category:\n 3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? Yes// <return>, respond YES. When prompted to select\n ===\n the option(s) you would like to place out of order, enter the\n following:\n \n AFJXNHEX REQUEST\n ================\n \n 4. Review your Mapped Routine set. If any of the routines listed in\n Routine\n the ROUTINE SUMMARY section are mapped on your system, they\n should be unmapped at this time.\n 5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This\n option will load the KIDS package onto your system.\n 6. The patch has now been loaded into a Transport global on your\n system. You now need to use KIDS to install the Transport global.\n 7. From the Kernel Installation and Distribution System (KIDS) Menu,\n select the Installation menu. On the KIDS Installation menu,\n you may elect to use the following options:\n a. Verify checksums in the Transport Global - this option will\n \n allow you to ensure the integrity of the routines that are in\n the Transport Global.\n b. Print Transport Global and Compare Transport Global to the\n Current System - this option will allow you to view all\n changes that will be made when the patch is installed. It\n compares all components of the patch (routines, DDs,\n templates, etc.).\n c. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n\n
\n \n \n Description:\n ============\n This patch corrects the problem of multiple jobs that are\n getting caught in an infinite loop in GMTSPDX. It also\n corrects the problem of getting View Alerts with no patient\n information included. In addition, this patch speeds up the\n retrieval of the patient's information.\n \n \n Subject:\n \n List of Test Sites:\n ==================\n New York, Madison, Coatesville, Lebanon, Clarksburg,\n Wilkes-Barre, Long Beach, Los Angeles, Philadelphia, Mountain Home,\n White-City\n \n \n \n ROUTINE SUMMARY \n Correcting hanging jobs (going thru an infinite \n =============== \n \n The following routines are included in this patch. The\n second line of each of these routines now looks like: \n \n <tab>;;5.1;Network Health Exchange;**[patch list]**;Date\n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n AFJXALRT 13284766 13885935 6,15,17\n loop) and not receiving any data\n AFJXPNHX 2605376 4205029 1,6,11,17\n AFJXREW 5392938 8174307 15,17\n AFJXTRF << NEW >> 5380483 17\n \n * From CHECK^XTSUMBLD\n \n \n \n Installation Instructions:\n ==========================\n \n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Install Package(s) \n Category:\n INSTALL NAME: AFJX*5.1*17\n ===========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//\n ====\n \n Enter options you wish to mark as 'Out\n Routine\n Of Order': AFJXNHEX REQUEST\n ================\n \n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n \n \n.\n\n
\nThe Network Health Exchange Software Package allows individual\nsites in a network area to request total and/or pharmacy\nhealth summarys (complete or last 12 months of data) via a\nserver that will return the data from the facility, and set an\nalert that allows the user to print the information received\nfrom the sending site.\n\n
\nThis is patch IBD*2.1*1. This patch corrects all known problems with\nmay be causing problems for sites when printing large numbers of\nencounter forms.\ncopying subcolumns and selections from both the conversion and editing\nencounter forms.\n \nThis patch includes 6 routines that clean up the variable DR that is\nleft lying around and causes unexpected prompts when editing.\n \nIn routine ^IBDF1BA the global ^UTILITY is misspelled in the kill logic\nleaving the global. This occurs during printing of encounter forms and\n\n
\nPatch IBD*2.1*14 \nThis patch includes KIDS post-install routine IBDY214.\n\n
\npatch routine IBDFQB for AICS v2.1\n\n
\nModification to code that interfaces with PCE to accept expanded\nreturn values.\n \nFixes to MDE options for CPT code narrative and clinical lexicon\nselection.\n\n
\nEmergency patch IBD*2.1*18\n\n
\nfix for 1010T print from Registration, released in conjunction with\nDG*5.3*108.\n\n
\n \n\n
\nThis is the AICS Data Entry System, patch IBD*2.1*2. See Patch description\nfor details.\n\n
\nPATCH FOR 'UNKNOWN' DIVISION ON AICS v2.1 REPORTS\n\n
\nFIX FOR PRINT QUEUES\n\n
\nIBD*2.1*7 TEST v2\n \nPartial DD Description field update and new Identifier for PAGE\nINFORMATION multiple for Encounter Form file (357).\n\n
\nPATCH IBD*2.1*13 v1 (routine IBDFDE6)\n\n
\nTEST PATCH v1 IBD*2.1*9\n \nThe current data in this field contains a Provider Screen on the\n'AK.PROVIDER'. This patch modifies the screen to use API call\n$$GET^XUA4A72(IEN) to check if the ^VA(200 entry has a PERSON CLASS\nentered prior to adding the entry as a Provider.\n=======================\n \n \nThis patch is in response to NOIS SBY-1096-30662.\n \nThis KIDS build contains routine IBDFDE5 which will run as a\npost-install routine to update the Package Interface entry INPUT PROVIDER\n(#61) MANUAL DATA ENTRY ROUTINE field (#18).\n\n
\nIBD*2.1*8 TEST v2\n \nROUTINES: IBDF18E IBDFDE IBDFDE1 IBDFDE21 IBDFDE7 IBDFDE8 IBDFDE9\n \nTEST SITES: IOWA-CITY, DES-MOINES, BLACK HILLS, SEPULVEDA\n\n
\nThis patch fixes the sites inability to exit out of the provider prompt,\nas well as a problem whereby duplicate diagnoses were being added to\nthe V POV file (#9000010.07).\n\n
\n \nPatch IBD*3.0*12 - files 357.6, 359.1 updates\n routines IBDFBK3, IBDFN12, IBDFN14, IBDFQS\n\n
\nModification to routine IBDF4 in support of Lexicon Utility v2.0.\n\n
\nAICS scanning patch to fix duplex scanning and anchor location.\n\n
\nPatched routine IBDFM1 to translate quote '"' and backslash '\\' characters\nfor Paper Keyboard.\n\n
\n \nThis patch fixes some misc. Forms Tracking items...\nWhen a new clinic is created and has appts., encounter\nforms print but they are not included on Forms Tracking\nlist for a single division facility without the division\nfield filled in.\nFixes Forms Tracking action SS Status Select for \nPending Pages and Error Detected, Not Transmitted.\n\n
\nThis patch corrects a problem with AICS printing Pharmacy\nAction/Informational Profile reports and associated DUE sheets. Prior\nto this patch, Pharmacy DUE sheets were not printing with the profiles.\n \nThis patch includes routine IBDFN3.\n\n
\nAICS changes to accommodate the ACRP conversion changes for outpatient\nencounter retrieval. Refer to the national patch module for more detailed\ninformation.\n\n
\nThis patch will print NKA (no known allergies) in the allergies block on\nEncounter Forms. A change to IBDFN2 was necessary because patch GMRA*4*10\nno longer sets the GMRAL array if the patient is unassessed or NKA.\n\n
\nAutomatic sending of Forms Tracking entries in a Pending Pages status\nTime Queued field of the Encounter Form Parameters file #357.09.\nto PCE.\n \nAdd a new package interface and toolkit component to display clinical\nreminders on an encounter form\n \nThis patch fixes the IBDF Background Job for the printing of\nEncounter Forms ignoring the time queued (starting time ) for\nprint jobs. It also allows only numerics to be entered in the\n\n
\nThis patch comprises a change to the recognition of encounter form anchors.\nIt includes a new routine that causes the formspec files that do the actual\nrecognition to function correctly. We used to use all 4 anchors printed one\nin each corner. With this new functionality we will first use the left pair\nof anchors and if those aren't found we will use the right pair.\n\n
\n \nIBDF18E1\nIBDF2A\nIBDFRPC\n\n
\nThis patch will eliminate an <UNDEF> MUMPS error at line OUT1+14^IBDFUTL\nby using a $G() of the variable "DIC.", $Gets have been placed around \nvariable IBDFCODE in ^IBDFUTL1. The choices presented to users when\nrunning the Maintenance Utility Option have been limited to valid choices.\n\n
\nWhen AICS users print encounter forms that contain\n3. CLA-0399-22584\n4. NJH-1198-20059\n'an overflow list' of problems, a null subscript\nerror occurs.\n\nIBD*3.0*39 resolves this problem, and addresses the\nfollowing NOIS(s):\n\n1. RIC-0599-20455\n2. DAY-1298-40380\n\n
\nAICS provides the packages PCE and CPRS the ability to display\n1. It was possible that the display order for groups of items\n on encounter forms did not necessarily match the display order\n in other patckages, especially CPRS. This was due to using\n the internal entry number to sort groups rather that the user\n specified display order.\n \n2. If the first character in a group had a code value of that\n began with an alpha character then it was possible for the\n header to not appear. If the entire group consisted of items\n with codes that began with alpha characters then the whole\nto users the lists of items that are printed on encounter forms.\n group may not appear. \n \n3. If an item was in a long list twice with exactly the same\n code and description then it would not appear in other packages\n after the first display.\n \n4. Occasionally there were Allocation errors generated when long\n (generally a full page) lists were processed.\nThis functionality then provides some consistency to all the \nAmbulatory Care data capture for sites that use encounter forms.\n \nA number of problems have been reported that relate to the display\nof this data in these packages. This patch corrects the following\nproblems:\n \n\n
\nSee patch description on NPM for complete details of this patch.\n\n
\nThis patch cleans up AICS DATA QUALIFIERS that may be causing problems with\nscanning.\n\n
\nINACTIVE HEALTH FACTORS NOT SCREENING\n\n
\nMISCELLANEOUS FIXES\n\n
\nPatch IBD*3*36 adds the Military Sexual Trauma (MST) indicator to AICS\nencounter form blocks and AICS manual data entry processes. See the\nNPM on FORUM for complete information.\n\n
\nPrinter Setup in [IBDF AUTO CLINIC PRINT]\n\n
\nFixes problems with 2nd and 3rd diagnosis codes.\n\n
\nWhen using the 'Pre-printed Form Data entry' option to add a stand alone\nencounter for a service connected patient, the service connected questions\nare not being asked if the patient has multiple stand alone encounters\nfor that day. This patch will allow the service connected questions\nto be asked regardless of the number of stand alone encounters for the day.\n\n
\nWhile using Clinic Setup/Edit Forms option and printing an Encounter form,\nthe option errors if a slave device is selected.\n\n
\nWhen AICS is used for checkout on patients who are being treated for an SC\ncondition and have reported MST, the encounter STATUS results in ACTION \nREQUIRED. Both the SC/MST Classification and Hidden Classification (V3.0\nMST) blocks ask the appropriate SC question but if answered YES, the MST\nquestion is not presented.\n\n
\nExport new encounter form blocks with Enrollment Priority instead of \nMeans Test Category.\n\n
\nWhen printing Action Profiles with Encounter Forms, an extra page feed is\nprinted. Either a page is wasted or the Action Profile is printed on the \nback of a duplexed page. \n\n
\nSample distribution to all allocation of encounter forms for wards. Done in\nsupport of changes to CPRS.\n\n
\nThis project is to allow for the input and data capture of GAF scores\nwhile using AICS.\n\n
\nProblems with printing Encounter Forms to a VMS Queue using Host Files.\nNOIS(s): \nATG-0701-32125, LEX-1200-40929, HVH-0900-10840, UNY-0800-12067,\nALN-0600-10776, DEN-0600-51325\nWhen the first Encounter Form is printed and the print is "reset" to the\noriginal settings in the specified terminal type, a second VMS file is\nopened. When the final printing is completed, the first VMS file is\nclosed leaving the second VMS file open. Therefore, unless the second VMS\nfile is manual close or forced to print, it will not print. This problem\nis resolved by resetting the printer with a direct call to %ZIS global\ninstead of a call to ^%ZIS routine.\n \n\n
\nThis patch is a means to distribute National Mental Health Encounter\n DATE SEC. COMES SITE RSLV\nOVER\nFILE # NAME DD CODE W/FILE DATA PTS\nRIDE\n--------------------------------------------------------------------------\n \n \n \n UP SEND DATA USER\n DATE SEC. COMES SITE RSLV OVER\nForms to the field in accordance to "Veterans Health Administration\nFILE # NAME DD CODE W/FILE DATA PTS RIDE\n-------------------------------------------------------------------------\n \n358 IMP/EXP ENCOUNTER FORM YES YES YES OVER NO NO\n \n358.1 IMP/EXP ENCOUNTER FORM BLOCK YES YES YES OVER NO NO\n \n358.2 IMP/EXP SELECTION LIST YES YES YES OVER NO NO\n \n358.3 IMP/EXP SELECTION YES YES YES OVER NO NO\nRevenue Cycle Improvement Plan", Final Report, September 2001.\n \n358.4 IMP/EXP SELECTION GROUP YES YES YES OVER NO NO\n \n358.6 IMP/EXP PACKAGE INTERFACE YES YES YES OVER NO NO\n \n358.91 IMP/EXP MARKING AREA YES YES YES OVER NO NO\n \n358.98 IMP/EXP AICS DATA QUALIFIERS YES YES YES OVER NO NO\n \n358.99 IMP/EXP AICS DATA ELEMENTS YES YES YES OVER NO NO \n \nThis build includes the following files.\n \n \n UP SEND DATA\nUSER\n\n
\nThis patch is a means to distribute National Encounter Forms to the field.\n\n
\n 1 NATIONAL CARD CATH/INTERV RAD National Cardiac Cath/Interventional\n 9 NATIONAL PROSTHETIC National Prosthetic Form 11/2002\n Rad 8/\n 2 NATIONAL CARDIOLOGY National Cardiology/EKG/Echo 8/2002 \n 3 NATIONAL DERMATOLOGY National Derm encounter form 8/2002 \n 4 NATIONAL ONCOLOGY National Hem/Onc 10/2002 \n 5 NATIONAL ORTHOPEDICS National Orthopedics 10/2002 \n 6 NATIONAL PM&R National PM&R 10/2002 \n 7 NATIONAL SURG MINOR PROCEDS National Minor Procedures 10/2002 \n 8 NATIONAL SURGERY CLINIC National Surgery 10/2002 \n\n
\nThis KIDS build sends the routines IBDF18C and IBDF18D which\nresolves a problem with exclusive locks not being unlocked when\nprinting encounter forms. A lock is set on the Forms Tracking global\n^IBD(357.96, and the Form Definition global ^IBD(357.95. When the locks\nare not cleared, an entry remains in the lock table for each file.\nThis KIDS build resolves this problem by releasing the locks from each\nfile after successful filing of the data.\n\n
\nSEND EF'S VIA KIDS\n\n
\n 1 NATIONAL CARD CATH/INTERV RAD National Cardiac Cath/Interventional\n 9 NATIONAL PROSTHETIC National Prosthetic Form 11/2002\n Rad 8/\n 2 NATIONAL CARDIOLOGY National Cardiology/EKG/Echo 8/2002 \n 3 NATIONAL DERMATOLOGY National Derm encounter form 8/2002 \n 4 NATIONAL ONCOLOGY National Hem/Onc 10/2002 \n 5 NATIONAL ORTHOPEDICS National Orthopedics 10/2002 \n 6 NATIONAL PM&R National PM&R 10/2002 \n 7 NATIONAL SURG MINOR PROCEDS National Minor Procedures 10/2002 \n 8 NATIONAL SURGERY CLINIC National Surgery 10/2002 \n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nCORRECT VITAMIN B12 INJECTION DOSAGE IN ENCOUNTER FORM USING ATTACHED \nPRE-INSTALL ROUTIEN IBDY358\n\n
\nSEND EF'S VIA KIDS\n\n
\nSEND EF'S VIA KIDS\n\n
\nEncounter Forms update.\n\n
\nThis KIDS build sends the routines IBDF18C and IBDF18D which\nresolves a problem with exclusive locks not being unlocked when\nprinting encounter forms. A lock is set on the Forms Tracking global\n^IBD(357.96, and the Form Definition global ^IBD(357.95. When the locks\nare not cleared, an entry remains in the lock table for each file.\nThis KIDS build resolves this problem by releasing the locks from each\nfile after successful filing of the data.\n\n
\nUPDATE FOR UNSUPPORTED ICD FIELDS\n\n
\nAICS ICD-10 CLASS 1 REMEDIATION\n\n
\nA request was made to update the SHORT NAME (field #.015) in the \nTYPE OF VISIT (#357.69) file. This field is computed using a pointer to \nthe SHORT NAME (#2) field in the CPT (#81) file; a field that is being \nremoved by patch ICPT*6.0*46. This patch will redefine the computed \nexpression used in the .015 field to use an API to populate the SHORT \nNAME data.\n\n
\n(1) This patch fixes the field QUANTITY (#.09) in file SELECTION (#357.3) \nnot being pushed to CPRS when added through the option Edit Encounter \nForms [IBDF EDIT ENCOUNTER FORMS].\n\n
\nBackup of IBD*3.0*70 on May 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch updates the Maintenance Utility for Active/Inactive Codes \n[IBDF UTIL MAINTENANCE UTILITY] option. It update the software to store \nthe report run for future use within the next 30 days. Also, the software\nhas been modified to allow the user to delete or replace a single inactive\ncode across all forms.\n\n
\nPatch IBD*3*72 Removes GAF functionality from AICS.\n\n
\nThis patch fixes a syntax error on field .09\nSUPPLMNTL FORM #3 ALL PATIENTS of the file\n409.95 PRINT MANAGER CLINIC SETUP. There is a \ncomma missing between U4. It should be\nU,4 in the screen for that field. \n\n
\nWhen editing a form that is used by more than 4 clinics, it is possible\nto have the clinic listing scroll off of the view screen. This patch\nwill limit the viewing of clinics to four at a time, so the display does\nnot scroll off of the viewing area.\n \nAdditionally, entering an '^' at the completion of the first screen of\nclinics does not exit the display. This patch will allow the clinic listing\nto abort appropriately upon entering an '^' at the 'Enter RETURN to\ncontinue or '^' to exit:' prompt.\n\n
\nThis patch contains multiple fixes for AICS v3.0 reported by NOIS entries.\n\n
\n \nAICS v3.0 patch IBD*3*11 - AICS MULTIPLE OPTION FIXES\n\n
\nAICS v3.0, including scannable encounter form support.\n\n
\nThe Automated Info Collection Sys consists of a set of utilities for\ndesigning, printing, tracking, maintaining, and scanning encounter forms.\n\n
\nThis build includes changes to address problems where Provider\nthe Provider Comments from a recently edited order from being added to an\norder currently being edited. This would occur only if the user edited an\norder containing Provider Comments, queued an MAR that included that\norder, and then edited another order at the exact moment when the 1st\norder is printed on the MAR.\nComments were being inappropriately copied from one order to another.\n \nChanges are included in PSIVORA1 to prevent the variable ON55 from\nremaining in the partition after taking action on an IV Fluid order\nthrough OE/RR 2.5. This allowed the Provider Comments from the order\ndefined by ON55 to be copied into new orders under certain conditions.\n \nChanges are included in PSGMIV, PSGMMIV, PSGMMIVC, and PSJMIV to prevent\n\n
\nA problem has been reported where an Inpatient IV order was d/c'd and then\na new IV Fluid order was placed and the provider comments from the\nd/c'd order were showing up in the order text of the new order.\n \nThis patch will correct this problem.\n\n
\nIn order for Drug Accountability/Inventory Interface (DA) to collect Unit\nDose dispensing, returns, extras, and pre-exchange needs data from\nInpatient Medications the routines included in this patch had to be\nmodified to call the DA routine EN^PSAPSI5. This functionality did not\nexist in v2.0 of DA. This patch should be installed prior to installation\nof v3.0 of DA.\n \nAll sites should install this patch. Drug Accountability/Inventory\nInterface v3.0 is not required to install this patch.\n\n
\n NOIS: REN-0397-60175 reported the following problems: \n orders with a day of week schedule (MO-FR). \n \nThis patch will correct these problems. \n \n1. If an IV order has only one solution and no additive, the admin time \n does not print on the 24 Hour MAR. \n \n2. The 24 Hour MAR printed an admin time on the wrong date for orders with\n day of week schedule (MO-FR). \n \n3. The 7 Day MAR did not print the **** on the date not to be given for \n\n
\nThe "APSJD" cross-reference on DATE OF DEATH field (#.351) of the PATIENT\nsurfaced with the Merge testing.\n \nMerge is tentatively scheduled for national release in August, 1997.\nfile (#2) calls routine PSJADT, which leaves the local variable D0\nundefined. The San Francisco Office of the Chief Information Officer\n(OCIO) Field Office requested that D0, D1, and D2 be added to the list of\nvariables NEWed at line END+1.\n \nThe FileMan compatibility issue centers around the variable D0 being\ndefined. Cross-references may set D0 equal to DA but should not otherwise\nalter ordelete D0. This issue has not been documented in the past but\n\n
\nInpatient Medications is updating the use of it's call to ^GMRADPT to look\nat piece G instead of piece C for type of reaction, to be in compliance\nwith the supported call. Piece C is no longer supported after 9/1/97.\n\n
\nA problem was reported where a site was getting an undefined error at\nDCOR+2^PSGOECS. The problem occurs because the code is not checking for\nthe variable PSGORD to contain an "O" and being routed to the wrong file\nto check for the order.\n \nThis patch corrects this problem\n\n
\n 1. A problem was discovered during the installation of Inpatient\n 2. An additional problem was discovered at one of our V. 5.0 test sites.\nWhen a patient had only IV orders and these orders were auto discontinued\ndue to a patient movement and the movement was later deleted, the IV\norders were not auto reinstated.\n \n This patch will correct these problems.\nMedications V. 5.0 at a test site where IV orders had a status of DC'ed in\nPharmacy, but had a future stop date and a status of active in Order\nEntry/Results Reporting (OE/RR). This was found to be the result of a call\nmade to DCOR^PSIVACT by the Surgery package. There is an existing\nintegration agreement with Surgery to allow them to call this entry point.\nHowever, the entry point was never updated to call OE/RR to change the\norder's stop date and status.\n \n\n
\nA problem was reported with the default Start/Stop date/time on IV\nDate was Jan 14, 1841 24:00. This error occurs when log in time is the\nsame as the admin time. \n \nThis patch corrects these problems.\norders logged in between midnight and 12:30AM. On an order with a\nschedule of NOW that was logged in at 00:09 the Start Date and the Stop\nDate showed 1699 for the default. On an order with a schedule of Q6HR\nthat was logged in at 00:10 the Start Date showed a default of 1699 and\nthe Stop Date showed a default of JAN 7,1841 24:00.\n \nWhen an order entered thru Order Entry by a Provider was finished by\npharmacy, the default Start Date came up as "1699" and the default Stop\n\n
\nThis patch supports OR*2.5*49, which is the pre-release patch for\nComputerized Patient Record System (CPRS) V. 1.0. This patch provides\nseveral entry points which are used by CPRS in their pre-release\npatch.\n\n
\n 1. A problem was discovered during the installation of Inpatient\n 2. An additional problem was discovered at one of our V. 5.0 test sites.\nWhen a patient had only IV orders and these orders were auto discontinued\ndue to a patient movement and the movement was later deleted, the IV\norders were not auto reinstated.\n \n This patch will correct these problems.\nMedications V. 5.0 at a test site where IV orders had a status of DC'ed in\nPharmacy, but had a future stop date and a status of active in Order\nEntry/Results Reporting (OE/RR). This was found to be the result of a call\nmade to DCOR^PSIVACT by the Surgery package. There is an existing\nintegration agreement with Surgery to allow them to call this entry point.\nHowever, the entry point was never updated to call OE/RR to change the\norder's stop date and status.\n \n\n
\nPartial DD's for ATC CANISTER field 212 of Drug file (#50) and sub-fields\n \nThe changes to IV Solutions file (#52.7) are for NOIS CLE-0696-41676.\n.01 (WARD GROUP FOR ATC CANISTER) and 1 (ATC CANISTER), QUICK CODE field 6\nof IV Additives file (#52.6) sub field 6 USUAL IV SOLUTION, and AVERAGE\nDRUG COST field 7 of IV Solutions file (#52.7).\n \nThe changes to Drug file (#50) are for NOIS BRK-0197-10549 and\nNAS-0197-30947.\n \nThe changes to IV Additives file (#52.6) are for NOIS NCH-0496-40049.\n\n
\nA problem was reported where when finishing an IV order the site was not\nbeing prompted with all the fields that should have been available for\nedit. The problem was reported after the site installed Pharmacy Data\nManagement. The problem was due to the routine PSIVORC2 looking at piece\n11 of the zero node of the additive or solution to identify if the\nadditive or solution was marked for use with IV Fluid orders. The routine\nhas been updated to look at piece 13.\n \nThis patch corrects this problem\n\n
\nA problem was reported at a site where when the physician used the\nnon-standard schedule of QH during order entry the system would hang\nand IRM would have to go in and kill off the job.\n \nThis patch will correct this problem.\n\n
\nA problem was reported where a site was seeing:\nThis resulted from a pharmacy user choosing the dc'd order through\npharmacy options and at the ACTION (L N)? prompt choosing N. Then the\nuser was prompted:\n DO YOU WANT TO MARK THIS ORDER AS 'NOT TO BE GIVEN'? No//.\nThe user took the default of no, but the call to RETURN^ORX was still\nmade.\n \nThis patch corrects this problem.\n \n R X A L L O R D E R S 12 orders\n \nHUFF,PUFF 321-11-3322 1S/328-D MAY 25,1945 (52) Wt \n Item Ordered Start date\n--------------------------------------------------------------------------\n1 dc NOT TO BE GIVEN |12/19/97\n \n\n
\nA problem was reported at a site where the initials of the person entering\nan IV order would sometimes appear on the MAR and sometimes they would\nnot. The IV orders were being entered by Technicians who did not hold the\nPSJ RPHARM security key.\n \nThis patch will correct this problem.\n\n
\nAn Illegal or invalid argument error at EDIT+2^PSIVEDT was received by a\nsite.\n \nThis patch will correct this problem.\n\n
\nThis patch makes changes to address Y2K issues.\n\n
\nWhen testing Y2K patch, noticed the following problem on Action profiles 1\n \n- - - - - - - - - - - - - - - -A C T I V E - - - - - - - - - - - - - - - -\n 1 R D N in 0.9% SODIUM CHLORIDE INJ 1000 ML 100 ml/hrC03/2503/28A\n \n \n 2 R D N ACETAMINOPHEN TABLET C 03/25 04/08 A\n Give: 650MG PO Q6HR \n \nSolution, schedule type, start and stop dates jams together.\nand 2 (problem occurs on both Action profiles).\n \n UNIT DOSE ACTION PROFILE #1 Page: 2\n \nDOE,JOHN NNN-NN-NNNN 01/01/1965\n \n \nNo. Action Drug ST Start Stop Status/Info\n\n
\nThis patch will add the option PSJI IVCATEGORY back to the PSJI\nSUPERVISOR's menu. This option was inadvertently deleted with the\ninstall of PHARMACY DATA MANAGEMENT (PDM) V. 1.0.\n\n
\nA problem was reported with the Action Profile #1 where if the patient had\n5-6 active orders no lines for Additional Medication Orders were printed.\nThis patch corrects this problem.\n\n
\nA problem was reported with the report generated by the option [PSJ PDV]\nPatients on Specific Drug(s). If the name of the first drug in the order\nwas longer than 34 characters it would cause the name, start date, and\nstop date columns of data to jam together.\n\n
\nThis build will fix the problems reported below:\n3) Divide by Zero error at MN+1^PSGPL0. This error occurs\nwhen field #42 (FREQUENCY) of the sub file Unit Dose (#55.06) of\nthe Pharmacy Patient File (#55) is a zero. (CON-0796-10063,\nWHC-0795-10480)\n \n4) Pick List hangs when sent to ATC. The site has the parameter ATC SORT\nPARAMETER=ADMIN TIME, the orders causing the pick list to hang are orders\nwith a schedule type of On Call which have no admin times.\n(WNY-0197-12396)\n \n \n5) Pick List not calculating correct units needed when orders have a\nnon-standard schedule (e.g. QAM&NOON). (CTX-0996-70760, NCH-0197-42095)\nAnother problem reported was when the schedule q.0.d was entered, where\nzero is entered instead of the letter o, the software would get stuck in a\nloop. (MAT-1294-70289)\n1) Extra Units Dispensed Report [PSJU EUDD] including information outside\nof the date range. (MGY-0996-31463)\n \n2) Unable to enter units dispensed using Enter Units Dispensed [PSJU PLDP]\nfor pick lists with a future start date/time when all pick list except\nones with a future start date/time have been filed away. (LAK-0696-30468)\n \n\n
\nThis patch is designed to make use of the Application Programmer\nInterfaces (APIs) provided by the National Drug file (NDF) application.\n\n
\nPharmacy Data Management (PDM) creates the "AUDS" cross-reference on the\nSTART DATE/TIME field (#10) of the UNIT DOSE subfile (#55.06) of the\nPHARMACY PATIENT file (#55). This patch will ensure that cross-reference\nis set when new Unit Dose orders are created and re-index the "AUDS"\ncross-reference for existing orders.\n\n
\nIn the routine PSGBRJ, in the section which kills off old labels,\nthe variable which checks for the type of order was only being set to a 1\nor a 2 so IV orders were not being checked to see if old labels should\nbe killed. This patch corrects this problem.\n\n
\nThis patch adds functionality requested in E3R #9551. \n* A mail group named PSJ-ORDERS REINSTATED is created by the patch KIDS\nbuild. The members of this mail group should be providers, nurses,\npharmacist, etc. who need patient's medication orders have been\nautomatically reinstated. \n \n* When the medication orders are automatically reinstated due to deletion\nof a patient movement, a mail message will be sent to the PSJ-ORDERS\nREINSTATED mail group.\n \n* The mail message will contain the patient's name, last four digits of\n \nthe patient's social security number, current ward location, reason the\norders were reinstated, and a list of orders that were reinstated. The\norders will be listed in the mail message in exact format as a patient\nprofile.\n When the Patient Information Management System (PIMS) deletes a\npatient movement, the medication orders that were discontinued due to the\ndeletion are automatically reinstated. A mail message will be sent to\nnotify affected parties that a patient's medications have been\nreinstated. Inpatient Medications V. 4.5 has been modified to include\nthis functionality.\n \n\n
\nDecision Support System (DSS) software has made provisions for inclusion\nis returned after the label is printed.\n \nDSS loads this data into a DSS file for later extraction by the vendor.\nWith the installation of this patch, Inpatient Medications V. 4.5 will\nbegin prompting for the CLINIC LOCATION for Outpatient IV orders entered\nfrom the Inpatient Medications package, storing the clinic location with\nthe order as it is entered through either Order Entry/Results Reporting\n(OE/RR) or Inpatient Medications, and passing this data, when available,\nto DSS.\nof the stop code field from outpatient clinic's intravenous dispensing\nwhen it is available. The stop code is derived by DSS from the clinic\nlocation field. Inpatient Medications V. 4.5 is being modified to pass\nthe clinic location field to DSS.\n \nThe Inpatient Medications software currently passes intravenous dispensing\ndata to DSS for DSS extraction, but does not include the clinic location\nfield. The passing of this data occurs when an IV label is printed or it\n\n
\nCurrently the 7 and 14 day MARs assume a year in the future when the\nEnter START DATE/TIME for 7 day MAR: 1 1 97 (JAN 01, 2097)\n \nSelect Reports Menu Option: 14 14 Day MAR\n \nPrint BLANK MARs? No// (No)\n \nSelect TYPE OF SHEETS TO PRINT: BOTH// \n \nEnter START DATE/TIME for 14 day MAR: 1 1 97 (JAN 01, 2097)\n \ndate is entered as shown below:\nAfter this patch is installed the date will be returned as a date in the\ncurrent century:\n \nSelect Reports Menu Option: 7 7 Day MAR\n \nPrint BLANK MARs? No// (No)\n \nSelect TYPE OF SHEETS TO PRINT: BOTH// \n \nEnter START DATE/TIME for 7 day MAR: 1 1 97 (JAN 01, 1997)\n \n \nSelect Reports Menu Option: 14 14 Day MAR\n \nPrint BLANK MARs? No// (No)\n \nSelect TYPE OF SHEETS TO PRINT: BOTH// \n \nEnter START DATE/TIME for 14 day MAR: 1 1 97 (JAN 01, 1997)\nSelect Reports Menu Option: 7 Day MAR\n \nPrint BLANK MARs? No// (No)\n \nSelect TYPE OF SHEETS TO PRINT: BOTH// \n \n\n
\nA problem was reported where orders entered, verified, and placed on hold\nby the nurse that were then taken off hold by the pharmacist were being\nautomatically verified at that time even though the pharmacist didn't have\nauto verify on. This patch corrects this problem.\n\n
\nThis patch adds functionality requested in E3R 11366. \n \nThe institution name has been added to the following reports:\n 7 Day MAR\n 14 Day MAR\n 24 Hour MAR\n Action Profile #1\n Action Profile #2\n Patient Profile (Extended)\n\n
\nThis patch corrects an undefined error that could occur when orders were\nauto-reinstated due to a movement being deleted.\n\n
\nThe original IV Solution's volume has an upper limit of 4000ml. This\npatch will increase the volume to 9999ml to meet the needs of the sites to\nenter solutions with a volume of greater than 4000ml.\n\n
\nThis patch will correct the problems reported below:\n BAY-0596-31907)\n \n1) Use @0, but scheduled labels still print on renewed orders.\n (SFC-0296-61455)\n2) Additive in wrong bottle on labels. (BAY-1095-32359, GAI-0196-31585,\n ANN-0895-40322)\n3) Q36 IVPB gives labels 12-36-12-36 schedule. (FAR-0596-40861,\n ATG-0796-32093)\n4) Incorrect information printing on label. (FRE-0896-60620,\n\n
\n1. Patch PSJ*4.5*66 added the institution name to several reports as\nrequested in E3R #11366. For integrated sites the institution name\nappearing on the reports was the primary institution's name. After\ninstallation of this patch integrated sites will see the name which was\nentered in field INTEGRATED SITE NAME (#17000) from the STATION NUMBER\n(TIME SENSITIVE) file (#389.9) on these reports. There will be no change\nfor non-integrated sites.\n\n
\nThis patch will correct the problem where Inpatient Medication orders\nfor a patient were not D/C'd when the patient was admitted to the\nhospital, if the patient had never been admitted before. (HUN-0197-21624,\nSFC-0297-61806)\n\n
\nThis patch will remove the references to the following files:\nlisting their inactivation date from file 6, inactivation date from file\n200, and if the provider was authorized to write med. orders in file 200.\n \nROUTINE SUMMARY:\n================\n \nThe following routines are included in this patch. The second line\nof these routines will look like:\n \n ;;4.5; Inpatient Medications ;**[patch list]**;7 OCT 94\nPROVIDER (#16)\n \nRoutine Name Before Patch After Patch Patch List\n PSGDCCM 3084929 2683467 38\n PSJPRE49 6565728 1604873 38\nPERSON (#6)\nUSER (#3)\n \nOnce this patch is installed the option [PSJV PROVIDER PRINT] Active\nProvider Report will no longer be available. This option was provided to\nassist sites in making the transition from using the PROVIDER file (#6) to\nusing the NEW PERSON file (#200) by identifying providers from file 6 and\n\n
\nThis build will fix the problems reported below:\n \n 1) A problem was reported after the installation of patch PSJ*4.5*34\n where the OE/RR pointer was not updated when an active IV order was\n edited so that a new IV order was created. The new IV order retained\n the OE/RR pointer from the edited order.\n\n
\nAssociated Patches: (v)OR*2.5*52. Needs to be installed prior to\ninstallation of PSJ*4.5*40.\n \nThis build will fix the problem reported below:\n \n1) The site reported changing the Requesting Clinician on a Pharmacy IV\norder, however the order retained the original requesting clinician's name\nas the requestor. (NOIS: WPB-0597-32252)\n\n
\nThis build will fix the problem reported below:\n \n Start and stop dates not calculating correctly when user goes to finish\npending orders. Orders were placed through OE/RR between 23:00 and 01:00\nand default start date/time for the wards was set to closest admin time or\nnext admin time.\n\n
\n \nwas assigned to a room-bed named numberEnumber-number. This problem also\nexisted in previous versions of Inpatient Medications. Changes are\nincluded to correct this error.\n \n3. An undefined error at NEWIV+4^PSJORUT2 can occur when multiple\nsolutions are entered for a Hyperal type IV order. This patch will correct\nthis error.\n \n4. When there are multiple duplicate drugs found while entering a new\norder, the duplicate drugs scroll off the screen. A pause was added so\n1. A problem was reported at a site when the physician used the\nthe user will have a chance to see the warning.\n \n5. When an IV order had been renewed through Computerized Patient Record\nSystem , the admin time from the original order should be copied over to\nthe new order. This will now function the same as Unit Dose.\n \n6. When the IV order's login time is the same as the admin time, the start\ndate of the order was not calculated in the correct format (West Palm\nBeach reported this). When the login time is between midnight and 12:30\nand the schedule is now, the start time was not calculated in the correct\nnon-standard schedule of QH during order entry. The system would hang and\nformat. This patch will correct this problem.\n \n7. The MAR sometimes printed the pharmacy tech's initials for IV orders.\nThe MAR will now print the initials of the person who completed the IV\norder.\n \n8. A change was made to print the <A> on the right of the patient name and\nward to indicate the patient has verified or non-verified allergy/adverse\nreactions.\n \nIRM would have to go in and off the job. A routine change corrects this\n9. When a field is edited in a non-verified Unit Dose order that does not\ncause a new order to be created, the order was not redisplayed for\nverification. This patch will cause the non-verified orders to be\nredisplayed after editing a field that does not cause a new order to be\ncreated.\n \n10. When a pending Unit Dose order with a priority of STAT was displayed\non the Unit Dose profile the "->" was not shown next to the order number\nidentifying the order as not verified. This patch will cause the "->" to\nbe displayed for pending stat orders.\nproblem.\n \n11. San Francisco reported an illegal or invalid argument at\nEDIT+2^PSIVEDT. This error occurred when the Med route field was edited.\nRoutine PSIVEDT was changed to correct this error.\n \n2. A problem was found where an Illegal Number error could occur in PSGDS0\nwhen an Authorized Absence/Discharge Summary was generated. The error\nwould occur only if the patient for which the report was being generated\n\n
\n1. This patch corrects a problem where the current date/time was used to\n \n3. A problem was found where a expired renewed order could be listed on\nthe pick list and then again if an update was run for that pick list. If a\nUnit Dose order was renewed with a future start date the original order\nwould be shown on the pick list as expired and then again as expired if an\nupdate was run for that pick list. This patch will cause the order to only\nbe listed on the original pick list.\n \n4. A problem was found where the previous order number was not returned to\nComputerized Patient Record System (CPRS) when a pending Inpatient Med\ncalculate the default start date/time when the order was speed finished by\norder was edited by pharmacy during the finish process. This change will\ncause the previous order number to be returned in all situations where a\nnew order is created due to edit by pharmacy.\n \n5. This patch corrects an error which would occur when a pharmacy\nsupported reference call was invoked by the CPRS Graphic User Interface\n(GUI). After installation of this patch the call to TERM^VALM0 will not be\nperformed if the call was issued by the Broker.\n \n6. If the Dosage Ordered field is edited on an active order and the user\npharmacy. These changes will cause the login date/time of the first order \njust hits <RET> and didn't change the value, the order would incorrectly\nbe flagged as having a change and a new order would be created. This\npatch will correct this problem.\n \n7. CPRS requested that the order control code be changed from OC to UR\nwhen an order cannot be removed from hold through CPRS. This change will\nallow CPRS to display the reason the action could not be taken to the\nuser.\nselected in the group to be finished to be used instead. \n \n2. An error would sometimes occur when renewing a Unit Dose order if the\nOrderable Item for the order contained a day or dose limit. These changes\nwill prevent the error and allow the day/dose limit entered to be used in\ncalculating the stop date for the new renewal order. \n\n
\nA problem was reported with the Automatic Pharmacy Statistics [PSU \nre-admission to the hospital via an application programmer interface (API)\nto Inpatient Medications. This patch corrects this API to only allow a\nnumeric value for the LAST WARD field to be passed in this API.\nPBM AUTO] option receiving an undefined variable error. The problem was\nthat the LAST WARD field (#68) of the UNIT DOSE multiple (#62) of the\nPHARMACY PATIENT file (#55) had a text value instead of a numeric value.\nThe patients where the problem occurred all had been admitted to\nobservation and then discharged and re-admitted to the hospital. New\nfunctionality was added to the Computerized Patient Record System (CPRS)\nto allow the orders that had been discontinued by the patient's discharge\nfrom observation to be automatically re-instated upon the patient's later\n\n
\n1. Several sites reported that the default start/stop dates for complex\ninformational purposes. NOIS: ATG-0202-32014, SPO-0302-51163, and\nBHS-0103-10826.\n \n2. The EXPIRE ALL ORDERS ON SAME DAY field (#.105) in the IV ROOM file\n(#59.5) is currently not evaluated in determining stop dates for IV\norders. This patch corrects this problem by evaluating the field and\ncalculating the appropriate stop date. NOIS: ISB-0502-32152.\n \n3. For schedules with long intervals, such as 48 hours, there was a\nproblem with the calculation of the first dose when orders were entered in\norders were causing confusion. The confusion is caused by the fact that\nCPRS. This caused an inconsistency between the expected first dose\ndisplayed to the provider and the actual time the order became available\nfor administration. This patch corrects this problem.\nNOIS: ATG-0402-31444, LOM-1201-62023, REN-1101-61894.\n \n4. A site reported a problem when entering orders with an admin time of\n23 and a schedule interval greater than 23 hours. The start time/expected\nfirst dose was being changed to 24. This patch corrects this problem.\nNOIS: BAY-0102-32400\n \nthe current stop/start dates don't reflect the duration for the order\n5. A site reported a problem with the calculation of the stop date on a\nrenewal order. If the start date of the order was greater than the current\ndate, the SAME STOP DATE ON ALL ORDERS field (#.04) in the INPATIENT WARD\nPARAMETERS file (#59.6) was ignored and the patient's default stop date\nwas calculated too far in the future. This patch corrects this problem by\nchanging the default stop date calculation to be based on the current\ndate, rather than the start date of the order. The patient's default stop\ndate will now be updated when an order is finished/accepted rather than\nwaiting until after it is verified. NOIS: CTX-0502-70557\n \nentered in Computerized Patient Record System (CPRS) V. 1.0. The dates\n6. E3R 12716 requested a change to the way an IV order's Stop Date is\ncalculated. The DAY (nD) or DOSE (nL) LIMIT field (#.05) in the PHARMACY\nORDERABLE ITEM file (#50.7) was not previously evaluated during the\ncalculation of an IV order's Stop Date. This patch will include this field\nwhen calculating an IV order's Stop Date. The Stop Date will continue to\nbe calculated by finding the shortest duration between the appropriate\nparameters contained in PHARMACY ORDERABLE ITEM file (#50.7), IV ADDITIVES\nfile (#52.6), and the IV ROOM file (#59.5). E3R: 12716\n \n7. A site reported an intermittent problem in which Provider Comments\nthat reflect the duration are currently displayed on the screen as the\nwould incorrectly copy from one order to another during the finishing\nprocess. This patch corrects the problem by ensuring that the order\nfrom which Provider Comments are retrieved is the same as the order being\nfinished. IND-0502-41166\n \n8. A site reported a problem that occurred during the finishing process.\nFinishing an order with an IV Quick Code that did not contain a schedule\ncould cause an error, which would abruptly halt the user's process. This\npatch corrects this problem. MAD-0402-42408\n \nrequested dates, but they are not the defaults. This patch corrects this\n9. In the past, a user was allowed to renew a Unit Dose order from the\nInpatient Medications V. 5.0 without an active Orderable Item tied to the\norder. This patch will inform the user that the order could not be\nrenewed.\n \n10. A site reported a problem with a report that displays orders verified\nduring a given time period. Some orders did not appear on the report due\nto trailing zeroes on the DATE VERIFIED BY PHARMACIST sub-field (#141) in\nthe IV multiple (#100) of the PHARMACY PATIENT file (#55). This patch\ncorrects the problem by removing the trailing zeroes from the internal\nproblem by using the requested start/stop dates as the defaults for\ndate. NOIS: CLL-0103-40447\n \n11. A site reported they were unable to discontinue IV orders from the\nComputerized Patient Record System (CPRS) V. 1.0. The problem was caused\nby an interaction with test patch DI*22*121. This patch will prevent the\nproblem from occurring. NOIS: TAM-0303-30859\n \n12. During internal testing a problem was discovered with the way Nurse\nVerification was recorded in the Activity Log when the verification was\ndone from the Computerized Patient Record System (CPRS) V. 1.0. This\ncomplex orders, and adding the duration to the patient profile display.\npatch corrects the problem by accurately recording the event in the\nActivity Log.\n \n13. A site reported an undefined error in the Inpatient Order Entry [PSJ\nOE] option that was the result of an interaction with Class III McKesson\nsoftware. This patch corrects the problem. NOIS: MIW-0503-40707.\nThe system calculated dates are still displayed on the screen for\n\n
\n 1. A site reported a problem with the manual reinstatement of\n PARAMETERS] option. The default label device is not loaded from the\n IV Room that is selected for edit, it is loaded from the IV Room that the\n user enters when initially logging in. If the user does not change the\n label device, this incorrect default label device value will be stored\n with the edited IV Room. This patch corrects the problem by ensuring the\n label device and report device are loaded from the IV Room that was\n selected for edit. NOIS: CLE-0203-40814.\n \n3. When a patient movement is deleted and orders are reinstated, a mail\n message is sent to a user group to inform the users of reinstated orders\n auto-discontinued inpatient IV orders. A pharmacist was not able to\n and those that were not reinstated. This patch changes the type of\n message that is sent when order reinstatement is attempted in Bar Code\n Medication Administration (BCMA) V. 2.0 from regular to priority.\n NOIS: WPB-0902-30314.\n \n 4. A site reported a problem with the Inpatient Profile [PSJ PR] option.\n The Special Instructions incorrectly displayed as an internal numeric\n date. Example: Special Instructions: 3030219.204644. This patch\n corrects the problem by properly displaying the Special Instructions.\n NOIS: BAY-0203-31638.\n manually reinstate an order if the patient had an active order with the\n \n 5. A site has identified a potential problem with the Barcode ID - Return\n and Destroy (IV) [PSJI RETURN BY BARCODE ID] option. It appears that this\n option is adding to the dispensed total, rather than the appropriate\n returned, recycled and destroyed totals. This patch corrects the problem\n by correctly recording the action, enabling the action to be accurately\n reported in the Drug Cost Report (132 COLUMNS) (IV)\n [PSJI DRUG COST REPORT] option. NOIS: CLL-0403-40228.\n \n 6. A site reported a problem with the Scheduled Labels (IV) [PSJI LBLS]\n same IV additive. This patch corrects the problem by allowing orders\n option. The background job that prints the labels occasionally becomes\n stuck in a loop when the print process encounters a patient with active\n IV orders but no labels to print. The background job processes data and\n writes NO PIGGYBACK DATA or NO ADMIXTURE DATA to a spool file, but no\n labels print. The print process eventually must be killed. This patch\n corrects the problem by allowing the print process to generate the NO\n PIGGYBACK DATA and NO ADMIXTURE DATA messages without entering an\n infinite loop. NOIS: MEM-0403-71631.\n \n 7. A site reported an error that occurred when an additive with an IV\n with duplicate additives to be reinstated manually. The software will\n Quick Code was added to an IV order that already contained multiple\n additives. This patch corrects the problem by properly processing IV\n Quick Codes when multiple additives are present. NOIS: BRX-0503-10289.\n \n 8. Several sites reported the screen would hang indefinitely when trying\n to open a patient's record in BCMA V. 2.0. This patch corrects the\n problem. NOIS: PAL-1102-61818.\n \n 9. A site reported a problem with additives printing on IV Admixture\n labels. Additives that were flagged to print on only one label per day\n continue to prevent orders with duplicate IV additives from being\n were printing on multiple labels each day. This patch corrects the\n problem. NOIS: NCH-0103-41471.\n \n 10. A site reported that the exclamation point, which is used to flag\n Special Instructions, is not removed from BCMA V. 2.0 when a patient's\n Special Instructions are changed from flagged to not flagged.\n NOIS: CLL-0503-41858.\n automatically reinstated. NOIS: TNV-0103-31207.\n \n 2. A site reported a problem with the SIte Parameters (IV) [PSJI SITE\n\n
\n 1. Several sites have reported Unit Dose labels do not always print. The\n units. This patch will round up the units needed on the Pre-Exchange\n Report to match the format of the pick list. BRX-0503-11875.\n problem occurs during verification of Unit Dose orders from the\n Non-Verified/Pending Orders [PSJU VBW] option when pre-exchange units are\n needed. In some instances, an error was logged indicating some ward\n parameters were not defined. This patch corrects the problem by ensuring\n the labels print, and the ward parameters are defined, regardless of the\n pre-exchange needs. CLL-0703-42086 and MIW-0503-40707.\n \n 2. A site reported that the Pre-Exchange Report was displaying fractional\n\n
\nReprinted IV TPN labels did not display the correct additives and \nsolutions on the labels. Sometime the electrolytes tied to the \nadditives/solutions were not appeared on the reprinted labels at all. \nThis patch will correct this problem. NOIS: #ROS-1102-50810.\n\n
\n1. A site using the CPRS Med Order Button in Bar Code Medication \n option. The error occurred when an update of the order was sent to the \n Computerized Patient Record System (CPRS) V. 2.0. This patch corrects the\n problem by adding data validation prior to attempting the update. \n NOIS: BRX-0403-11828\n \n 3. A site reported an error that occurred while using the Inpatient Order\n Entry [PSJ OE] option. The error occurred when the patient profile\n attempted to access an IV order with a status of renewed and a stop date\n that had passed since the last time the order was viewed. This patch\n corrects the problem by changing the variable names to remove conflicts.\n Administration (BCMA) V. 2.0 reported a problem where the dosage ordered\n NOIS: SFC-0403-61950.\n \n 4. A site reported an error that occurred while attempting to print a\n pick list. The error occurred during a cleanup of old pick list data,\n and the error message indicated the process had been locking the data as\n it cleaned it, but it did not unlock the data. This patch corrects the\n problem by ensuring the data lock is removed when it is no longer needed.\n was not displaying correctly on the order in Inpatient Medications V 5.0.\nThe problem occurred for orders with local possible dosages, where the\n strength and unit were defined. This patch corrects this problem by \n sending the local possible dosage information, if available.\n \n 2. A site reported receiving an error while attempting to discontinue \n a renewal IV order from the Non-Verified/Pending Orders [PSJU VBW]\n\n
\n Sites have reported problems with the way Inpatient Medications V. 5.0 \n that is associated with a non-standard schedule by displaying a warning \n message along with the calculated frequency at the time an order is \n finished, and when the schedule edited. NOIS PTH-0703-20552.\n interprets non-standard schedules. These schedules, which are not defined\n in the ADMINISTRATION SCHEDULE file (#51.1), may contain a pattern of \n characters that are not always translating into the expected\n administration frequency. For example, Q9AM is translated to a schedule\n of every nine days, and a schedule of EVERY NIGHT is translated to a\n schedule of every hour. \n \n This patch will help to clarify the actual calculated schedule frequency\n\n
\nA site reported a problem that occurs when the pick list is sent to the \nATC. It does not round up and the ATC will not accept fractional units so\nthe drug does not go to the ATC. This patch corrects this situation by\nproviding an optional system parameter to allow rounding of fractional\ndoses before sending to the ATC. NOIS ALT-0403-20970\n\n
\nThis project consists of 12 patches that work together to create a new\n GMPL*2*27\n GMRV*4*15\n LR*5.2*295\n OR*3*157\n PSS*1*62\n PSJ*5*90\n PSO*7*118\n PX*1*119\n RA*5*33\n YS*5.01*77\nClinical Reminders index global. The purpose of this index is to provide\n \n The purpose of this patch (PSJ*5*90) is to lay the groundwork for these \n changes by modifying the Inpatient Medications V. 5.0 routines to set the\n cross-references to create the new indices if PXRM*1.5*12 has been\n installed. If patch PXRM*1.5*12 has not been installed the index will not\n be built.\n \n This patch can be installed independently of the other patches. The \n documentation describing the new functionality will be available when all\n associated patches are released.\nrapid access to clinical data. All of the standard Clinical Reminders\nfinding types are included in the index.\n \nThe 12 patches that comprise this project are:\n \n PXRM*1.5*12\n DG*5.3*478\n\n
\nThis patch is designed to make use of the Application Programmer\nInterfaces (APIs) provided by the National Drug file (NDF) application.\n\n
\nA site reported a problem with the DOSAGE field (#120) in the UNIT DOSE\nmultiple (#62) of the PHARMACY PATIENT file (#55) not being deleted when\nan orderable item is changed. This patch corrects this problem by \nremoving the data when the orderable item is changed. NOIS UNY-0603-10652\n\n
\nSite reported a problem with the display of flagged pending IV order with\nno additive in the profile view. This patch corrects this problem by\nappropriately displaying the flag for pending IV orders with no additive.\n(NOIS: MAR-0703-21163)\n\n
\n1. Joint Commission for Accreditation of Healthcare Organizations (JCAHO)\n2. To accommodate Billing Awareness, it was necessary to modify the \ncommunication between CPRS and Outpatient Pharmacy V. 7.0 to include \nnew diagnosis codes. Inpatient Medications V. 5.0 routes all pharmacy\norders to the appropriate package. This patch makes the changes necessary \nto pass the new diagnosis codes to the appropriate package.\nrequires that patients' use of Over-The-Counter (OTC) medications, Herbal\nsupplements, medications prescribed by Veterans Health Administration \n(VHA) but purchased by the patient at an outside pharmacy, and medications\nprescribed by providers outside VHA be documented in patients' medical\nrecords. These four categories of medications will hereafter be referred\nto as Non-VA Meds. This patch makes the changes necessary to Inpatient \nMedications V. 5.0 to support Non-VA Meds.\n \n\n
\n The inclusion of a non-standard variable (&) in the Medication Schedule\n resulted in errors when the Bar Code Medication Administration \n Contingency program decoded the Inpatient Medications HL7 messages.\n This patch modifies these messages utilized by the BCMA Contingency to\n send administration time in another message segment.\n NOIS NJH-1203-21889\n\n
\n1. Modifications are being made to Inpatient Medications V. 5.0 to no \nNON-STANDARD SCHEDULES IN QUICK CODES, NON-STANDARD SCHEDULES IN ORDER\nSETS and NON-STANDARD SCHEDULE IN ORDERABLE ITEMS. The search routine can\nbe run multiple times. This can be used to help show the progress being\nmade in correcting issues. In addition, the report will show active orders\nin the search period. Please note: the default schedules in the PHARMACY \nORDERABLE ITEM file (#50.7) are for both inpatient and outpatient orders.\n \n2. Based on the upcoming requirement from the Joint Commission on \nAccreditation of Hospital Organizations, schedule names that are\nconsidered dangerous will no longer be allowed. This patch provides a \nlonger allow non-standard schedules to be used. This patch provides a \nmenu option to allow users to identify schedules that are considered \ndangerous. This option will search through Order Sets, Quick Codes, the \nADMINISTRATION SCHEDULE file (#51.1), the PHARMACY ORDERABLE ITEM file \n(#50.7) and all orders for the timeframe specified by the user. The person\nrunning the option will receive a series of email messages identifying the\ndangerous schedules. The email message subjects will be: DANGEROUS\nSCHEDULES IN 51.1, DANGEROUS SCHEDULES IN ORDERS, DANGEROUS SCHEDULES IN\nQUICK CODES, DANGEROUS SCHEDULES IN ORDER SETS and DANGEROUS SCHEDULES IN \nORDERABLE ITEMS.\n \nmenu option to allow users to identify non-standard schedules\n3. To facilitate the iterative process of running the search and report \nmultiple times, two new options are being added to the system. They are \nthe Non-Standard Schedule Search [PSJU NSS SEARCH] option and the\nNon-Standard Schedule Report [PSJU NSS REPORT] option. \nthat are currently in use. This option will search through Order Sets,\nQuick Codes, the ADMINISTRATION SCHEDULE file (#51.1), the PHARMACY \nORDERABLE ITEM file (#50.7) and all orders for the timeframe specified by\nthe user. The person running the option will receive a series of email\nmessages identifying the non-standard schedules. The email message\nsubjects will be: ADMIN SCHEDULES, ADMIN SCHEDULES NOT IN 51.1,\n\n
\n Phase I of the Inpatient Medications Requirements for the Special Focus\n OR*3*213 ORDER ENTRY/RESULTS REPORTING V. 1.0\n PSU*3*34 PHARMACY BENEFITS MANAGEMENT V. 3.0\n \n Patches PSS*1*79, OR*3*213, and PSU*3*34 contain changes to support the\n following enhancements in PSJ*5*110:\n \n 1. The Extend Stop Date on Renewal enhancements will allow an order to be\n renewed without creating a new order. Editing of the start date will no\n longer be allowed during the renewal process. In addition, limits have\n been set on the length of time after an order expires that it may be\n Group IRA project consists of four patches. The patches are combined in\n renewed. This is outlined in the BCMA 2001 Special Focus Report,\n Requirement #11.\n \n 2. The Complex Order enhancements will change the way complex orders are\n handled by linking complex components (child orders) together. If the\n actions Finish, Verify, Discontinue, or Renew are taken on one child\n order, the user will be alerted that the action must be taken on all of\n the complex component orders in the set. The user will then be prompted\n to take the appropriate action on each child order in the complex order\n set. This is outlined in BCMA 2001 Special Focus Report, Requirement #8.\n host file PSJ_PSS_OR_PSU_110.KID in order to simplify installation at VHA\n \n 3. The STAT and NOW Order Notification enhancements will alert users\n subscribing to new mail group PSJ STAT NOW PENDING ORDER when a pending\n STAT or NOW order has been received from Computerized Patient Record\n System (CPRS) V. 1.0. Users subscribing to the new mail group PSJ STAT\n NOW ACTIVE ORDER will receive an alert when a STAT or NOW order is made\n active. This is outlined in BCMA 2001 Special Focus Report, Requirement\n #12.\n \n PSJ*5*110 contains repairs for the following defects:\n facilities. Installation of this host file should be coordinated among\n \n 1. A site reported a problem with the non-standard schedule messages that\n display in the order view and during finishing. IV orders with Pro Re\n Nata (PRN) schedules displayed the messages but Unit Dose orders with PRN\n schedules did not. This patch corrects the problem by including the base\n PRN schedule in the non-standard check and making Unit Dose and IV orders\n consistent. NOIS: MIN-1203-40699.\n \n 2. A scheduled IV order could be created without a schedule interval when\n created using an IV quick code with a schedule and admin times, but no\n the four packages affected since only one installation is necessary. The\n infusion rate. In this scenario, if an infusion rate is then entered\n during the finish process, the order is filed with no schedule interval,\n which is necessary to calculate when doses are due.\n NOIS: SFC-0603-61122.\n patches, in order of install, are:\n \n PSS*1*79 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*110 INPATIENT MEDICATIONS V. 5.0\n\n
\n1. The Inpatient Medication Orders for Outpatients project will allow a\n \n3. Drug selection lookup was using an old cross reference. This patch\ncorrects the program to use the correct one. NOIS: ISB-0803-30450\n \n4. To accommodate Billing Awareness, it was necessary to modify the\ncommunication between CPRS and Outpatient Pharmacy V. 7.0 to include\nnew diagnosis codes. Inpatient Medications V. 5.0 routes all pharmacy\norders to the appropriate package. This patch makes the changes necessary\nto pass the new diagnosis codes to the appropriate package.\n \nuser the ability to order unit dose medications for outpatients. This is\n5. A provider entering an order into Computerized Patient Record System\n(CPRS) V. 1.0 must be permitted to place a limitation on the duration of\nan inpatient medication order. This capability exists for Unit Dose orders\nand Inpatient IV orders, but not for IV Fluid orders. This patch makes\nthe change necessary to receive a duration or dosage limit on an IV Fluid\norder placed in CPRS. The limitation will be in hours, days, milliliters,\nor liters.\n \n6. A site reported a problem with the default start date and time for\norders created between 11pm and midnight. The default start date for these\naccomplished through modifications to Inpatient Medications V. 5.0,\norders may default to 11pm the following day. This patch corrects the\nproblem by calculating and displaying the correct default start date and\ntime. NOIS: BRX-0803-12080.\n \n7. Two sites reported a problem with IV labels not printing correctly with\nDay-of-Week schedules that had Sunday in the list. This patch corrects\nthis problem. NOIS: PHO-0903-60884, MIN-1003-41071 and MIN-0204-41197.\n \n8. A request was made to modify the Non-Verified/Pending Orders option \n[PSJU VBW] to show the clinic for Outpatient IV orders. This patch makes \nComputerized Patient Record System (CPRS) V.1.0 and Scheduling V. 5.3.\nthis modification. E3R: 17357\n \n9. A description has been added to the ACX cross-reference in the ORDERS\nFILE PARENT ORDER field (#125), in the NON-VERIFIED ORDERS file (#53.1) \nat the request of the database administrator.\n \n10. A site reported a problem with the display of dosage information \nunder certain circumstances. Specifically, there was no spacing between \nthe number and the dosage form. This patch works with changes in Pharmacy \nData Management V. 1.0 to correct this problem. NOIS: BRX-1004-10173 and \nThis patch provides the changes for Inpatient Medications.\nSFC-1003-62552\n \n11. To accomodate the Scheduling Encapsulation project, a change has been\nmade to the retrieval of appointment information. When a specific error\ncode is returned, the following message will display in place of the\nappointment: "Scheduling database is unavailable". NOIS: ISB-0903-31960\n \n12. A site reported that the finishing pharmacist is incorrectly saved as\nthe provider when the SF - Speed Finish action is used to finish a pending\nrenewal order. This patch corrects the problem by saving the provider \n \nthat renewed the order with the finished and verified order. \nNOIS: AMA-1004-71742 and CPH-1004-41922\n \n13. Orders with Day of Week (DOW) schedules may be created with an \ninappropriate dose frequency which prevents the scheduled doses from \nappearing on the Virtual Due List (VDL) in Bar Code Medication \nAdministration (BCMA) V. 3.0. A frequency value appropriate for DOW \nschedules will be stored for orders containing this type of schedule to \nensure they display correctly in BCMA. NOIS: HIN-0503-41736\n \n2. Provider Comments are not being saved with active IV orders. This patch\n14. Orders created in CPRS V. 1.0 between 2300 and 2400 may, during the \nfinishing process, incorrectly default to a start date and time that is 24\nhours later than the correct default start date and time. Orders created \nbetween 2300 and 2400 will now default to the correct start date and time.\nNOIS: PAL-1203-62062.\ncorrects this by saving Provider Comments when IV orders become active.\nNOIS: ASH-0803-31967, ERI-0303-20187 and ISB-0702-30889. \n\n
\n 1. A site reports that when a nurse verifies a renewed order, the nurse's\n by removing the original order's verifying pharmacist from the copied\n This cross reference is created each time a\n component of a complex order, or child\n order, is received from CPRS. This cross\n reference will not be created for orders\n with a schedule of NOW, effectively\n disassociating the NOW order from the other\n child orders in the complex order.\n order. NOIS# CLA-1004-22199\n \n 3. A site reports that after discontinuing a complex IV order, a user \n may be prevented from creating a new IV order until first exiting and \n then returning to the option. The software treats the new IV order like \n a complex order and prevents entry of some required fields. This patch \n corrects the problem by improving the check that determines whether or \n not the current order is a complex order. NOIS# SAG-1004-41795.\n \n initials do not consistently appear in BCMA. This patch corrects the\n 4. When using the SF (Speed Finish) action to finish pending renewal\n orders in the Unit Dose Order Entry [PSJU NE] option, the name of the \n finishing pharmacist is incorrectly saved as the provider for the order.\n This patch corrects this problem by properly saving the ordering provider\n with the order when SF (Speed Finish) is used. NOIS# AMA-1004-71742.\n \n 5. When a component, or child order, of a complex order is created from \n Computerized Patient Record System (CPRS) V. 1.0 with a schedule of NOW \n and NOW does not exist in the ADMINISTRATION SCHEDULE (#51.1) file, the \n order does not appear in the patient's profile in Inpatient Medications \n problem by saving the verifying nurse information if the nurse \n V. 5.0. This patch corrects the problem by ensuring child orders with a \n schedule of NOW appear in Inpatient Medications V. 5.0.\n \n 6. Renewed Unit Dose orders do not appear on the updated pick list\n printed using the Update Pick List [PSJU PLUP] option. With this patch\n renewed orders will appear on the updated pick list when appropriate.\n NOIS: NCH-1104-40147\n \n 7. When finishing a complex order that was renewed from CPRS, there is a\n prompt for Pre-Exchange Doses, but there is no prompt to print the\n verification occurred after the renewal action. NOIS# NCH-1004-40487.\n Pre-Exchange Report. A prompt has been added to allow the Pre-Exchange\n report to be printed for renewed complex orders. NOIS: MAR-1004-21942.\n \n 8. The SF Speed Finish action in the Unit Dose Order Entry [PSJU NE]\n option prompts for Pre-Exchange Doses, but there is no prompt to print\n the Pre-Exchange Report when finishing a pending renewal order. A prompt\n has been added to allow the Pre-Exchange Report to be printed for orders\n that are finished using the SF Speed Finish action. NOIS: CLE-1004-42151.\n \n 9. The initial label printed for renewed continuous IV orders indicates\n \n it is due at the date and time that the order was renewed, rather than\n at the next scheduled infusion date and time. With this patch, the first\n label printed for this type of order will be due at the next scheduled\n infusion date and time. IND-1104-40485.\n \n 10. After finishing IV scripts, the user is prompted for the number of\n labels to print. The label print code does not limit the user input, so\n if the user enters an excessive number of labels, then this can lead to\n system performance problems. This patch will apply the limit of 99\n labels at the number of labels prompt. SFC-0603-61734.\n 2. A site reports that IV orders copied using the CO (Copy) action in\n \n 11. Complex Orders are not showing on the VDL in BCMA when the order\n initially contains a schedule without a frequency, regardless of edits\n made during finishing. With this patch, the schedule changes made during\n finish will update the complex orders schedule frequency, enabling the\n orders to display in BCMA at the appropriate times. SBY-1104-31772\n \n 12. The stop date of a pending renewal order containing a non-standard\n schedule and an orderable item with a day/dose limit cannot be edited\n until after the order is made active. Also, Schedule Type and Unit\n Inpatient Medications V. 5.0 retain the original order's verifying \n Per Dose edits made during finish of a pending renewal are not applied\n when the order is made active. With this patch, changes made to these\n fields during the finish proces will be applied to the active order.\n ERI-1204-20679\n \n 13. One-time orders that are not part of a complex order may be renewed\n from CPRS V.1.0, even after they are given. This patch will prevent this\n problem by preventing all non-complex one-time orders from being renewed.\n Restriction of the renewal of complex one-time orders will be addressed\n in a future CPRS V.1.0 patch. PSI-04-056.\n pharmacist, so that an unverified copied IV order may incorrectly appear\n \n 14. This patch modifies the Data Dictionary of the NON-VERIFIED ORDERS\n FILE (#53.1) for the ORDERS FILE PARENT ORDER field (#125). The change\n removes Inpatient Medications from the process of stripping NOW orders\n from Complex Orders. This process is handled exclusively by CPRS.\n \n 53.1,125 ORDERS FILE PARENT ORDER .2;8 POINTER TO ORDER FILE (#100)\n \n \n \n to have been verified by a pharmacist. This patch corrects the problem \n LAST EDITED: DEC 13, 2004\n HELP-PROMPT: Enter the parent order, if this order is\n its child order.\n DESCRIPTION: This is the parent of a CPRS order that\n may have a parent/child relationship in\n CPRS.\n \n CROSS-REFERENCE: 53.1^ACX\n 1)= S ^PS(53.1,"ACX",$E(X,1,30),DA)=""\n 2)= K ^PS(53.1,"ACX",$E(X,1,30),DA)\n\n
\n 1. PHO-0803-61519 If finishing an order as a syringe and the volume is\n strength calculation if the value is less than zero(0). A change\n has also been made during the entry process of strength to add a\n leading zero(0) if the user does not.\n less than 1ml, when entering the decimal it will not allow a leading\n zero(0). The correction for this problem will allow the input of a\n leading zero(0). If the user does not enter a leading zero(0), the\n software will add it.\n \n 2. HEH-1004-40163 When pharmacy prints a label for a TPN order mix, the\n leading zero(0) in 0.5 GM of magnesium sulfate does not print. The \n correction for this problem will add the leading zero(0) to the \n\n
\nThis patch fixes the 5 missing Pharmacy Intervention menu selections and \nallows output to P-MESSAGE from routine PSGDCTP.\n\n
\n1. A problem was reported with the LABEL PRINTER field (#.07) in the\nLists will not be sent correctly to the ATC device. \n \nThis patch will create and populate new fields that are Pointer data types\nby converting the old device names stored in the old fields to their\ninternal entry values in the DEVICE file (#3.5). This will permit the\ndevice names to be changed without any disruption to the printing of\npharmacy labels. \n \n2. A change to address NOIS WNY-0197-12396 was not included in version\n5.0. The ATC-212 device will hang if an 'ON CALL' order is sent to it.\nINPATIENT USER PARAMETERS file (#53.45), WARD LABEL PRINTER field (#.13)\nThis was reported in NOIS WNY-0598-10164. This patch will make the\ncorrect change to routine PSGTAP1 and PSGPLR.\nand PHARMACY LABEL PRINTER field (#.14) in the INPATIENT WARD PARAMETERS\nfile (#59.6), and the BAXTER ATC DEVICE field (#30) in the WARD GROUP file\n(#57.5). These fields store the name of entries in the DEVICE file\n(#3.5). The fields currently have the data type of Free Text. This\ncauses problems if the device name is ever changed in the DEVICE file\n(#3.5). Until the new name is entered into these fields in the Inpatient\nMedications package, the pharmacy order labels will not print or Pick\n\n
\n 1. CON-0404-10937 Site reported dispensing a ONE TIME unit dose\n maintain the schedule from the start date.\n medication as a Pre-Exchange dose, the medication also showed up on\n the following PICK LIST requesting a dose-to-dispense of one (1)\n instead of zero (0). This patch will determine if the SCHEDULE TYPE\n is ONE-TIME and if a dosage was dispensed as PRE-EXCHANGE and not\n request a dosage on the PICK LIST.\n 2. PHO-1204-60861 Renewal of QOD (every other day) schedules causes the\n Pick List to restart the QOD schedule from the renewal date instead \n of the start date. This routine change will cause the Pick List to\n\n
\n Currently the printed MAR does not show that an Inpatient Medication is\n on hold. This patch will update the 14 day, 7 day, and 24 hour MAR\n reports to display "hold" on the report in place of the admin time.\n This change will affect the following options:\n PSJU 14D MAR - 14 Day MAR\n PSJU 7D MAR - 7 Day MAR\n PSJU 24H MAR - 24 Hour MAR\n\n
\n1. A request has been made to allow sites to define inpatient orders for \n to the CLINIC DEFINITION file (#53.46).\nc. Remove the Clinic Stop Dates option [PSJ CSD].\nd. Add the Clinic Definition option [PSJ CD].\n \n2. A problem was reported with inpatient orders for outpatients \ndisplaying in the incorrect display group on the Orders tab in the \nComputerized Patient Record System (CPRS) V. 1.0. This patch corrects this\nproblem by modifying the HL7 messaging as well as the order editing \nprocess to correctly define the appointment date and time for the\ninpatient order.\noutpatients' behavior on a clinic-by-clinic basis. The two changes would \n \n3. It was discovered during internal review that the STAT NOW MAIL GROUP \nfield (#5) of the INPATIENT WARD PARAMETERS file (#59.6) had been omitted \nfrom the appropriate distribution. This patch corrects this problem by \nexporting the field.\n \n4. A problem was identified with the display order on the meds tab in \nCPRS. The problem was related to information being passed from Inpatient \nMedications V. 5.0 to identify inpatient orders for outpatients. This \npatch corrects this problem by modifying the data pass to CPRS.\nadd the ability to control auto-dc of orders and whether or not they\nNOIS: WAS-0205-20562\nappear in the Bar Code Medication Administration V. 3.0 package. This\npatch helps to accomplish this goal by doing the following:\n \na. Rename the CLINIC STOP DATES file (#53.46) to be the CLINIC DEFINITION \n file (#53.46).\nb. Add the AUTO-DC IMO ORDERS field (#2) and the SEND TO BCMA? field (#3) \n\n
\n 1. TNV-1104-30671 Pharmacy is reporting that they do not see the\n "Patient Record Flags" when using the Inpatient Pharmacy option\n "Inpatient Order Entry [PSJ OE]". This patch will add a \n reference to DISPPRF^DGPFAPI that is designed to display the\n "Patient Record Flags".\n\n
\n PSI-04-061: Expected First Dose\n Start Date, Stop Date and/or Admin Times fields are edited. During the \n edit process it is possible to edit one or all of these fields in any \n order. This could cause the "Expected First Dose" to be displayed \n multiple times. This will be handled by determining the last field\n that was edited and displaying the "Expected first dose" only after that\n field.\n \n \n PSI-04-071: Provider Comments Display\n -------------------------------------\n -------------------------------\n When the pharmacist is presented with the question to "Copy provider \n comments", the provider comments do not appear on the screen. A change\n will be made to display the provider comments prior to asking the \n question "Copy the Provider Comments into Special Instructions?".\n \n \n PSI-05-005: Administration Time being over written on child orders\n ------------------------------------------------------------------\n When finishing a renewed complex order from Inpatient Order Entry [PSJ \n OE] option, the administration times for the second and subsequent child \n During order entry in CPRS the provider is presented with the "Expected \n orders in the series are changed to the administration time of the first \n order in the series. A change will be made to preserve the \n administration time for all orders within a complex order.\n First Dose" for the order. The Pharmacist's have requested that the \n "Expected First Dose" be displayed in Backdoor pharmacy when Start Date, \n Stop Date and Admin Times are entered or edited.\n \n This change will require the "Expected First Dose" to be displayed after \n the Stop Date is entered in New or Renewed orders as well as when the \n\n
\nUpon installation of this patch, the following Inpatient \nMedications corrections will occur:\n \n \n \n1. A null subscript error (due to undefined variable) will\n not occur when pick list cross references are killed.\n2. The word 'domiciliary' will be spelled correctly in the\n PSJI Site Parameters option.\n\n
\n 1. A site reported an error that occurred during Speed Finish of pending \n day-of-week schedules.\n \n 3. An undefined error may occur when viewing a pending IV renewal order\n from the Medications Tab in Computerized Patient Record System (CPRS) V.\n 1.0. This patch will correct the problem by preventing the error from\n occurring. MIN-1204-41611.\n \n 4. When renewing an Inpatient IV order from the Inpatient Order Entry\n [PSJ OE] option, an edit to the Provider is not reflected in the order\n when viewed from CPRS V.1.0. This patch will correct the problem by\n renewals orders. The error occurred after an unsuccessful lock of the\n ensuring the updated provider information is transmitted to CPRS V.1.0.\n IND-0105-40153.\n \n 5. There is no prompt for output device for the PRE-EXCHANGE UNITS REPORT\n after copying a Unit Dose order using the CO Copy action in Inpatient\n Order Entry [PSJ OE] option. This patch will add a device prompt for the\n Pre-Exchange Units Report to the Unit Dose copy action. HWH-1204-41654.\n \n 6. When finishing a pending unit dose renewal order, the default \n administration times associated with the administration schedule will \n original renewed order. This patch will prevent this error by ensuring a \n always default into the order, overwriting the order's existing\n administration time. With this patch, renewal orders will retain the\n original order's administration times. BHS-0105-10562.\n \n 7. When the schedule type is edited during the finish of a unit dose\n order that was renewed from CPRS V.1.0, the order appears twice in the\n Patient Profile (Unit Dose) [PSJU PR] option. This patch corrects the\n problem by removing the display associated with the previous schedule\n type before adding the display associated with the new schedule type.\n FRE-0105-60387, MAC-0205-61020.\n graceful exit when a lock is not successful. CLE-1204-41459\n \n 8. Multiple identically named schedules in the ADMINISTRATION SCHEDULE\n file (#51.1) may cause an invalid schedule warning message to appear\n inappropriately. This patch corrects the problem by preventing the\n invalid warning message from appearing if the schedule name is defined in\n the file, even if duplicates are present. HD0000000085881.\n \n 9. A non-standard Day of Week schedule entered without administration\n times using the schedule builder in CPRS V. 3.0 may default to a\n different schedule in Inpatient Medications V. 5.0 if the non-standard\n \n schedule is a partial match to a unique Day of Week schedule in the\n ADMINISTRATION SCHEDULE file (#51.1). For example, if the non-standard\n schedule SU-MO-TU-WE is entered without admin times using the CPRS V.\n 3.0 schedule builder, and the schedule SU-MO-TU-WE-TH@09 exists in the\n ADMINISTRATION SCHEDULE file (#51.1), and there are no other schedules in\n the ADMINISTRATION SCHEDULE file (#51.1) that begin with SU-MO-TU-WE, the\n order's schedule will default to SU-MO-TU-WE-TH@09 when the order is\n selected for finishing. HD0000000087120, PSI-05-025.\n \n 10. A non-standard Day of Week schedule entered using the schedule\n 2. The administration schedule validation process causes an error if a \n builder in CPRS V. 3.0 defaults to the wrong Expected First Dose if the\n schedule is a partial match to exactly one schedule in the ADMINISTRATION\n SCHEDULE file (#51.1), and that schedule that was found contains an\n administration time. HD0000000087028 PSI-05-026.\n day-of-week PRN schedule is used that contains days that are out of \n order, for example, "WE-MO PRN". This patch will prevent this error and \n make the validation of this type of schedule consistent with non-PRN\n\n
\n HD0000000086717 - Multiple active Orders Appearing in BCBU\n records as "Pending" until all child orders are verified. Then a final \n HL7 transaction will be sent telling the BCBU that the entire order has \n been verified.\n ----------------------------------------------------------\n A problem has been identified that will cause the BCBU to contain\n multiple active orders for the same order. This issue happens in the\n PSJ OE (Inpatient Medications) option. After a pharmacist finishes and\n accepts a complex order, then edits and verifies each order in sequence,\n multiple HL7 records are sent to the BCBU signifying the order has been\n verified. The BCBU should only receive 1 record signifying the order is\n verified. This patch will modify this behavior by sending the HL7 \n\n
\nThe "undefined variable DIFLD(1)" error is being caused by the\n \nThis patch changes the routines so that they use the\nDBS FILE^DIE function that is designed to be used recursively\nand within FileMan cross references.\nrecursive use of the ^DIE call in a FileMan cross reference.\nThe "DATE OF DEATH" field of the "PATIENT" file triggers many\ncross reference procedures and routines.\n \nThe purpose of this patch is to make changes to the Inpatient\nMedications routines associated with the "DATE OF DEATH" APSJD\ncross reference. There are six tag/program locations that\nuse the ^DIE call when this cross reference is triggered.\n\n
\n HUN-1003-22262 - Med Order Button\n ---------------------------------\n While testing CPRS V25, it was discovered that not all Allergy checks\n were being displayed. This could occur if there were multiple VA DRUG\n CLASS entries entered for a patient. A change will be made to loop all\n VA DRUG CLASS entries for the patient to correctly identify potential\n drug allergies.\n \n \n PUG-0205-50079 - Report printer length\n --------------------------------------\n ---------------------------------\n There is an inconsistency between the length of the IV ROOM (59.5) file\n fields LABEL DEVICE (13) and REPORT DEVICE (14) and the corresponding\n entry in the DEVICE (3.5) file. The IV ROOM fields only allows 20\n characters and the DEVICE file allows 30 characters. The IV ROOM file\n fields LABEL DEVICE and REPORT DEVICE will be changed to allow 30\n characters.\n If a nurse enters an order via the Med Order Button on the BCMA\n application, and this is the only order for that patient, the order\n will not show up on the Non-Verified/Pending Order (PSJU VBW) option if\n selected by Group, Ward or Clinic. This patch will resolve this issue.\n \n \n ERI-0205-20902 - Allergy Checking\n\n
\nThis patch adds functionality requested in E3R #9551. \n* A mail group named PSJ-ORDERS REINSTATED is created by the patch KIDS\nbuild. The members of this mail group should be providers, nurses,\npharmacist, etc. who need to know that the patient's medication orders\nhave been automatically reinstated. \n \n* When the medication orders are automatically reinstated due to deletion\nof a patient movement, a mail message will be sent to the PSJ-ORDERS\nREINSTATED mail group. \n \n* The mail message will contain the patient's name, last four digits of\n \nthe patient's social security number, current ward location, reason the\norders were reinstated, and a list of orders that were reinstated. The\norders will be listed in the mail message in exact format as a patient\nprofile.\nWhen the Patient Information Management System (PIMS) deletes a patient\nmovement, the medication orders that were discontinued due to the deletion\nare automatically reinstated. A mail message will be sent to notify\naffected parties that a patient's medications have been reinstated.\nInpatient Medications V. 5.0 has been modified to include this\nfunctionality. \n \n\n
\n 1. From NOIS call BED-1004-10719, Regarding the reinstated \n medications notification email message, "It doesn't look\n like the ordering clinician gets any notification." This\n patch will add the ordering physician to the list of\n email recipients.\n \n 2. BAY-0205-30845, Syntax Error at WRD+1^PSIVRNL.\n This patch will correct the syntax error included in this\n routine.\n\n
\n HD0000000086021 - IV Renewal Issue\n HD0000000068894 - PSJOE Error\n -----------------------------------\n The following error has appeared in the error trap at various sites:\n \n <UNDEFINED>DISACTIO+36^PSJOE\n \n This patch will resolve this issue by re-initializing the variable in\n question.\n -----------------------------------\n When finishing a renewed IV order via Inpatient Order Entry [PSJ OE]\n it is possible to enter the same stop date as the original for\n the renewed order. This will cause the database to improperly\n index the renewal. This causes the wrong number of labels to print as\n well as not printing this order on the Ward List report. This patch\n will resolve this issue by correcting indexing the renewal.\n \n\n
\n * WARNING - Prior to installing this patch, please check for local Class\n correction locks the newly created order until the pharmacist has\n completed editing.\n III modifications that may be overwritten upon installation. Failure\n to reinstall Class III modifications after installation of this patch\n may prevent the Class III changes from functioning properly.\n \n 1. When finishing a CPRS-entered IV Medication order, if the user\n makes a change to the order that causes a new order to be created,\n the new order is not locked and allows the provider to change the\n order while the pharmacist is still working on the order. The\n\n
\n 1. When a provider enters an IV order and the Pharmacist finishes the\n screen captures that the pharmacist was using lower case. The system\n responded differently because of the lower case letters. The changes\n included in this patch will cause the system to function equally for\n upper and lower case letters in the standard VISTA operation.\n order and tries to delete an additive and make changes in the solution\n field the additive shows as deleted. When the order is accepted, the\n order re-displays shows with the same additive that was deleted. This\n correction makes the needed code changes so that the deleted additive\n will actually be deleted as requested.\n \n 2. The pharmacist is unable to edit the solution field of a newly entered\n TPN order. It was noted in the original NOIS report and supporting\n\n
\n 1. When finishing a CPRS-entered order for a syringe, if the user\n trigger to the picklist.\n indicates "NO" at the intermittent syringe prompt, the syringe \n size field is required and causes a loop back to the patient's\n profile if it is not filled in. This patch will allow the user\n to "carriage return" past the SYRINGE SIZE prompt and continue\n finishing the order.\n \n 2. Currently when field "(12) Dispense Drug" of an order is edited an\n updated picklist is not triggered. This change will cause an update\n\n
\n 1. PSI-05-062: When the site has the Inpatient Medication site parameter\n DATE/TIME" and correctly calculate the default stop date for the \n first order.\n "SAME STOP DATE ON ALL ORDERS:" set to "YES", and the patient's \n "DEFAULT STOP DATE/TIME" is set to TODAY. When a physician "RENEWS" \n orders, the default stop date gets calculated as TODAY for the first\n order. The patient's "DEFAULT STOP DATE/TIME" is extended when the\n first order is accepted and the default stop date for following orders\n is calculated correctly.\n \n This patch is designed to extend the patient's "DEFAULT STOP \n\n
\nIn support of the Decision Support System (DSS) FY2006 Extract\nverified by a nurse or if that is not present, the login date of the \norder.\nEnhancement project two changes have been requested in Inpatient\nMedications V. 5.0.\n \nFirst, add the order number to the list of data being sent to DSS Extracts\nV. 3.0.\n \nSecond, add the IV room and order date to the list of data being sent to \nDSS Extracts V. 3.0. The order date will be the date the order was \n\n
\n This patch addresses two separate issues. In the first issue,\n the original order to be discontinued, backdoor currently will.\n if the ward group or ward location is not properly defined, or\n if the administration team is not properly defined, patients and\n or medications can be left off of the Action Profile-2 Report\n [PSJU AP-2].\n \n The second issue addressed by this patch will make CPRS and backdoor\n pharmacy function consistently with respect to discontinuing an\n original order while it has a pending renewal. CPRS will not allow\n\n
\n 1. When finishing a pending renewal order, if the order is edited\n \n 2. Updated pick lists display doses for renewed orders that may already\n have been dispensed prior to the renewal. With this patch, doses for a\n renewed order will appear on the pick list update beginning with doses\n due after the latter of the renew date and the order's stop date prior\n to renewal. TNV-0205-31276.\n such that the number of dispense drugs associated with the order after\n verification is less than the number of dispense drugs associated with\n the order prior to renew, an index used by the pick list incorrectly\n retains entries associated with the old dispense drugs. This may cause\n problems with pick lists and extracts. With this patch, the correct\n number of dispense drugs will be stored with renewal orders for which the\n number of dispense drugs was reduced during the finish of the order.\n AMA-1204-71370.\n\n
\nInpatient Medications has been requested to send the clinic location's\nInternal Entry Number (IEN) to Decision Support System (DSS) along with\nthe IV data currently sent. DSS loads this data into a DSS file for later\nextract to the vendor. With this change, Inpatient Medications V.5.0 will\nprompt for the CLINIC LOCATION for Outpatient IV orders enter from the\nInpatient Medications package. The clinic location will be stored in\nInpatient Medications and Order Entry/Results Reporting (OE/RR) packages.\n\n
\nThis patch adds the capability of doing order checking between local VA \nfacilities and remote VA or Department of Defense (DoD) facilities where \nveterans have received prescriptions.\n \nThe order checking includes checking for duplicate drugs, duplicate drug \nclasses, drug interactions, and drug allergies.\n\n
\nIt has been discovered that the Extra Units Dispensed [PSJU EUD] option\nwas not communicating properly with the ATC machine after the \ninstallation of CPRS version 25. This patch will resolve this \ncommunication issue.\n\n
\n 1. An undefined variable error occurs when an attempt is made to print a\n is edited, administration times and schedule frequency from the new\n schedule do not default into the copied order. This patch corrects this \n issue by using the administration times and schedule frequency from the \n newly entered schedule. \n HD0000000102178 \n \n 3. When changing an IV order's schedule from a continuous schedule to a \n one-time schedule with no frequency defined in the ADMINISTRATION \n SCHEDULE file (#51.1), the order's schedule interval is not updated, \n resulting in the order's IV labels printing based on the frequency of\n MAR label for a non-verified order. The error occurs when the software\n the original schedule. For example, if an IV order's schedule is changed \n from Q6H to ONCE, IV labels will continue to print based on the Q6H \n schedule, or 4 labels per day. This patch will require an order's \n schedule interval to be updated with the frequency from the new schedule.\n HD0000000092412\n attempts to retrieve clinic appointment information from the non-verified\n order. Once the order is verified the MAR label prints without producing\n the error. This patch corrects this issue by correctly processing\n non-verified orders without appointment information.\n HD0000000068851\n \n 2. Immediately after copying a unit dose order, if the order's schedule\n\n
\n1. The addition of two new DRUG UNITS to the Inpatient Medication IV\n package has been requested. The two requested units are MG-PE and \n NANOGRAM.\n\n
\n HD0000000106439 - Non-Verified Pending Report showing patients at the\n ------------------------------------------------------------------------\nIf an order is placed "on hold" and then expires before being "taken \nOff hold" the order will appear on the medication profile's "Active"\nList of medications. If the Rph attempts to "unhold" this order the\nmessage "this order has expired" will be displayed and the order will\nremain on the list of Active medications. This patch will resolve this\nissue by allowing the Rph to remove the order from hold. After the\norder is removed from hold, it will immediately be removed from the\nactive medications list.\n \n Wrong location.\n HD0000000108826 - Undefined error when exiting Pick list\n ------------------------------------------------------------------------\nIf you attempt to exit the "Requested Start Time:" prompt in the Pick\nList option (PSJU PLUP) you may receive the following error:\n<UNDEFINED>UP+6^PSGPLUP\nThis patch will resolve this issue.\n ------------------------------------------------------------------------\nIt has been discovered that the Non-Verified Pending report (PSJU VBW)\nis showing patients still under the clinic after being admitted to a\nward. This issue will be resolved by correctly searching the proper\nindexes used to determine the patient's current location. \n \n HD0000000108102 - Expired on hold order cannot be removed\n\n
\n 1. When a pick list contains one or more orders for which there is \n The following items from your DRUG file were found to have NO DATA in\n their PRICE PER DISPENSE UNIT field:\n 1234567,123,1\n \n Any PICK LIST with any of these items will NOT be completely FILED\n AWAY until the PRICE PER DISPENSE UNIT field has been entered into \n for these items.\n Even if there is no cost for these items, a zero (0) must be \n entered into the PRICE PER DISPENSE UNIT field so the package knows\n it is not an error or an omission. UNTIL THIS IS DONE, NO COST\n an inconsistency between the number of dispense drugs associated with \n REPORT WILL BE ACCURATE, AND ANY PICK LIST WITH THESE ITEMS CANNOT BE\n PURGED.\n \n With this patch, this MailMan message will not be generated due to an\n extraneous or 'orphan' dispense drug index entry associated with an\n order. HD0000000068561. \n \n 2. To assist in preventing problems with dispense drugs of active \n orders, the ability to delete dispense drugs from a pending renewal will \n be removed. Functionality will be added to allow dispense drugs to be \n the order and the number of dispense drug index entries associated with \n inactivated for pending renewal orders. HD0000000068561. \n the order, a MailMan message is generated incorrectly stating that a \n problem exists with a DRUG file (#50) entry. A message generated in \n this way may be identified by the display of numbers separated by\n commas, rather than the name of the drug.\n \n Example:\n\n
\nThis patch addresses two issues contained in two Remedy tickets, \nThe second issue addressed involves an incorrect display of the dispense \ndrug units in backdoor pharmacy. If the dispense drug units per dose are \nchanged (editing field 12 backdoor), and one of the drugs' units \ndispensed becomes 0, backdoor pharmacy will still display a value of 1 \nfor that drug. BCMA and CPRS show the correct dispense drug units, and \nthe correct units are stored in the ^PS(55) file.\nHD118307 and HD108011.\n \nThe first issue addressed by this patch is an undefined variable error \nwhen the user attempts to run the menu option [PSJU EUD]. If the user \nselects a patient who has never been admitted, then presses the carriage \nreturn again at the Select Patient prompt, an undefined variable error \noccurs.\n \n\n
\n Pending complex orders cannot be verified when the complex order is also\n the clinic associated with the order is not a valid IMO clinic, the order\n may not be finished in Inpatient Medications.\n HD115420\n an Inpatient Orders for Outpatients (IMO) order. This patch corrects this\n issue by allowing the verification of complex IMO orders if the IMO\n functionality is active and the clinic is a valid IMO clinic.\n \n Complex Inpatient orders may only be created if the Inpatient Orders for\n Outpatients (IMO) functionality has been activated. The same criteria\n used to determine if a simple IMO order may be selected for finishing in\n Inpatient Medications will be used for Complex Orders; for instance, if\n\n
\nThis patch addresses two issues in two Remedy tickets. \nrenewing provider to be displayed.\nThe first issue addressed by this patch arose when the site\nused the ATZERO (@0) flag on IV Piggybacks to prevent labels\nfrom printing. Labels printed despite the flag being set.\n \nThe second issue involves the wrong provider being displayed\nby CPRS and backdoor pharmacy when an order is renewed. \nCurrently, CPRS and backdoor pharmacy are still displaying the\noriginal provider. The sites are expecting to see the \n\n
\n 1. The Inpatient Medication Package patient name lookup routine is not\n correctly looking up patient's using the partial match functionality\n that is standard with other packages. This patch will correct this by\n replacing the lookup call to ^DIC with the DPTLK API designed for\n patient lookup.\n\n
\n1. An error was reported that occurred when a unit dose order set was\nRecord System (CPRS) and pharmacy. These changes prevent the entry of\nthese in the schedule field through pharmacy and will reject any orders\nsent from CPRS with these type of schedules.\n \n3. The ONE-TIME/PRN MAR prints 10 blank lines for initials and notes at\nbottom half of the MAR sheet. At the sites request, this patch will print\n20 blank lines as in previous version of Inpatient Medications.\n \n4. A problem was reported with Service (Total Cost per) [PSJU SCT]\nreport. Patch 3 introduced a problem that caused the report to not total\nbeing entered. A variable was not being cleaned up between the processing\ninformation correctly by service. This patch corrects this problem. \n \n5. A problem was reported with IV labels not getting cleaned up\nappropriately in the MAR LABELS file (#53.41). The MAR labels for these\ndiscontinued or expired orders were sometimes incorrectly printing on the\nwards. This patch corrects this problem. \n \n6. A problem was reported with the Patients on Specific Drug(s) [PSJ PDV]\noption. If the user chooses to print the report by VA Drug Class, IV\norders were not printing correctly. This patch corrects this problem. .\nof one order to the next in the order set. If the user edited a field but\ndidn't change the value, this variable would cause an error when the\nfollowing order in the set was being processed. This patch makes a change\nto routine PSGOES to correct this error. \n \n2. A problem was found where a single or leading space was being entered\nin the schedule field of a Unit Dose order through Computerized Patient\n\n
\nSeveral sites reported a problem with the sort for the Inpatient Profile \noption [PSJ PR]. The sort by patient and room-bed was no longer \nfunctioning. This patch corrects this problem. HD68431, HD68690, HD68981, \nHD89922, HD94618, HD94785, HD95473, HD96140, HD96553, HD97042, HD98398, \nHD106136, HD131842\n\n
\n 1. PSI-05-051: A priority status of ASAP is not easily seen by the \n the three for notification via the STAT NOW MAIL GROUP functionality.\n \n 2. Remedy Ticket #106018: Stat IV orders are not highlighted and \n flashing like Stat Unit Dose orders. This patch adds the code\n required to make Stat IV orders highlighted and flash like Stat Unit\n Dose orders.\n finishing pharmacist. A STAT order is displayed as blinking and \n highlighted, but a ASAP order does not have any special visual\n effects. \n \n In order to avoid adding more special visual effects to the screen \n this patch is designed to offer a Site Ward Parameter that will allow\n the site a choice of what orders are sent to the STAT NOW MAIL GROUP.\n The site can select STAT, ASAP, or NOW orders, or any combination of \n\n
\nA provider entered a medication through CPRS with the intent of the order \nschedule type to override the incoming CPRS schedule type if the backdoor\ndefault is "Fill on Request".\nbeing administered on a QD0600 continuous schedule. The medication \nordered, however, had a default schedule type of PRN. Therefore, when \nthe pharmacist finished the order backdoor, the default schedule type of \nPRN overrode the Provider's intent of a continuous schedule. Because the \nmedication was finished as PRN, the patient missed a dose of the \nmedication.\n \nThis patch addresses this issue by only allowing the backdoor default\n\n
\n1. CPRS IV Orders currently select the first of multiple IV Additives by\n \n*** The software included in this patch is designed to exclude an IV\n Additive from the selection process only if the "USED IN IV FLUID \n ORDER ENTRY" field is set to "NO".\n \n*** If the "USED IN IV FLUID ORDER ENTRY" field is set to "YES" or \n blank, then the IV Additive will be selected in IEN order.\n \n2. This patch is also designed to correct a programming error in routine\n PSJPXRM1 that is to be used by CPRS to return Inpatient Medications\n IEN associated with the Pharmacy Orderable Item selected in CPRS by\n order information. This is a routine that is not currently in use,\n and will be tested at the programmer prompt.\n \n3. If the user enters a start date/time in the future and then enters \n the number of doses at the stop date/time prompt, the software\n calculates the stop date/time from the current date/time instead of\n the entered start date/time.\n the Provider. The software checks to determine if the IV Additive \n is Inactive, but does not check the "USED IN IV FLUID ORDER ENTRY" \n field to determine if the additive should be used.\n \n This patch will change the software to add a check of the "USED \n IN IV FLUID ORDER ENTRY" field and exclude the additive from selection\n based on that field.\n\n
\nThis patch contains Application Program Interfaces (APIs) that will be \nwhen the time comes.\n \nThis API replaces the following integration agreements:\n \nDBIA # Affected Package(s)\n------ -------------------\n1884 DSS EXTRACTS,DRUG ACCOUNTABILITY\n2907 TEXT INTEGRATION UTILITIES\n534 HEALTH SUMMARY\n \nused by calling applications that currently do direct global reads or \nThis patch enhances an original INPATIENT MEDICATIONS API call \nALL^PSJ59P5. This enhancement allows a double question mark ("??") to be\npassed in to the second parameter PSJFT. PSJFT represents the free-text\nname a user wishes to retrieve from this file. Passing "??" to the PSJFT\nparameter will cause the API to return all entries from the IV ROOM FILE \n(#59.5). Specifications for this API can be found in the Pharmacy\nRe-Engineering (PRE) API Manual. Reference to MEDICAL CENTER \nDIVISION FILE (#40.8) is supported by DBIA 2269.\nwrites to the Inpatient Medications files. Since the IV ROOM file \n(#59.5) and the NON-VERIFIED ORDERS file (#53.1) are being replaced as part\nof the Pharmacy Re-engineering project, any direct M-based global reads\nor writes to this file must be replaced by calling the APIs provided in \nthis patch. When the new data source is in place, the calling applications \nwill not be required to make any changes, because these APIs will be \nflexible enough to retrieve the requested data from the new data source, \n\n\n1. This problem happens when multiple complex orders are selected\n \n2. Currently in file #55, PHARMACY PATIENT, the UNIT DOSE multiple \n field, the ACTIVITY LOG multiple field, the file number of node #14 is\n sometimes being written incorrectly as 55,09.\n \n This patch includes the correction to the routines that are writing \n this information and a post init routine to correct the existing\n information.\n together to be finished or verified. If the first order is partially \n finished or verified. The system notifies the user that if all orders\n are not finished or verified, then none of the orders will be finished\n or verified, but leaves the order in a "corrupted" state.\n \n This patch makes changes to the routine to clean up the temporary\n variables so the process can loop through multiple complex orders \n without causing the "corrupted" state.\n\n
\nThis patch addresses Remedy ticket HD158508 (PSI 06 125) and its \nbut no pop-up box appeared, and the medication was not marked as given on \nthe VDL. The underlying issue was that while the order had the Special \nInstructions deleted, the flag to display/not display the message box in \nBCMA was not cleared.\nduplicate tickets. An order with Special Instructions was entered, and \nwhen prompted, the order was finished so that the BCMA Message Box flag \nwas set. Therefore, when the medication was to be administered in BCMA, \na pop-up box was to display to show the nurse the Special Instructions. \nThe order was renewed via CPRS, and the order was FINISHED backdoor and \nthen had the Special Instructions were deleted before accepting the order \nand verifying. When the nurse entered BCMA to administer the medication \non the renewed order, BCMA behaved as though the medication was given, \n\n
\nThis patch addresses Remedy ticket HD101591.\n \nHD101591, will show the pharmacist an expected first \ndose date/time for IV orders during the finishing process. Currently, \nfor IV's ordered either backdoor or through the CPRS IV Meds Dialog, no \n"Expected First Dose" is displayed. Unit dose orders, and IV's ordered \nthrough the Inpatient Meds dialog on CPRS do display an expected first \ndose. An Expected First dose will not display if the schedule type for\nthe order is ON CALL or PRN.\n\n
\nHD000000104291 - Stop Date calculation can be in the Past\nmakes the Stop Date/Time calculation that occurs during edits to the \nAdditives and Solutions fields consistent with edits to other fields).\n \nDuring the Testing of the solution above a new issue has been found.\n \nNew Issue 1: Editing the Additive or Solution for non-renewed orders\n------------------------------------------------------------------------\nThis is the same issue as the Original issue but it can also apply to a \nNon-renewed Active order.\n \n------------------------------------------------------------------------\nThe solution for the New issue is to Modify the Inpatient Meds IV Order \nCheck logic to Display the warning message "The Stop Date/Time is in the \nPast. This order will automatically expire upon verification", anytime \nthe stop date calculation returns a Stop Date/Time in the past. The \nPharmacist will then be asked if they still wish to continue. If they \ncontinue, the order will automatically expire immediately upon \nverification If they select to not continue, they may go back to the \nprofile and edit the Stop Date/Time.\nWhen editing the Additive or Solution of an active order that was \npreviously renewed, the stop date/time can be re-calculated in the Past. \nThis will cause the order to be expired immediately upon verification. \nThe solution to this issue is to modify the Stop Date/Time calculation to \nuse the "Last Renewed" date as a starting point, instead of the \n"Original" Start Date/Time of the order, when editing the Additive or \nSolution of an active IV order that has been previously renewed. (this \n\n
\n1. After Finishing and Verifying a complex Outpatient IV order, the\n system was treating the New Order entered afterwards as a complex\n order.\n \n This patch makes a correction to the software that cleans up \n information from a previous order before moving on to a New Order.\n\n
\n1. If the user chose a printer device and did not wish to queue the\norders was selected, the order view did not display on the screen. This\npatch will display the order view before prompting for the number labels\nneeded.\n \n4. When a pick list update was ran and an order had been discontinued, the\ndosage ordered was not printing on the discontinued order. This patch\ncorrects this problem.\n \n5. An undefined variable XRT0 error was sometimes occurring when using the\nhidden actions and trying to print an individual label. This patch\noutput, the MAR was printed to the screen. This patch will send the\ncorrects this problem.\n \n6. The hidden action to print the MAR from the Inpatient Order Entry [PSJ\nOE] option did not use the default set in the INPATIENT WARD PARAMETERS\nfile (#59.6) when promping for the MAR's medication types. After\ninstallation of this patch the default set in the INPATIENT WARD\nPARAMETERS file (#59.6) will be used.\nreport to the correct device.\n \n2. When renewing IVs, the default stop date and time is the same as the\nrenewed order. This patch will calculate the default stop date according\nto the IV Site Parameter.\n \n3. When the Update Daily Ward List (IV) [PSJI UP] option for Hyperal\n\n
\n1. The function [Patient Profile (Extended)] isn't displaying complex\n \n2. Remedy Ticket HD127723 reported the problem that the system did not\n correctly handle the Q5MINUTES schedule during the finish process. It\n would not accept the users input when prompted for a schedule after\n selecting to FN(Finish) the order. According to the Inpatient \n Medication developers the system should not be prompting for a \n schedule with an exact match at this point in the FN(Finish)\n process. This patch makes the correction to prevent the schedule\n prompts for an exact match.\n orders correctly.\n \n Before the patch this function displays each individual pending\n complex order with a selection number for viewing.\n \n This patch is designed to display the entire complex order with a \n single selection number and display the full complex order when that\n number is selected for view.\n\n
\n** WARNING - After installing this patch, a location AND ad appointment \nhours. When the pharmacist finished the order, it was not noticed that \nthe stop date was 24 hours, not the normal default stop date for an \ninpatient's medication orders. As a result, the patient did not receive \nhis/her medication as prescribed. The inpatient meds code in VistA \nassumed the order was an IMO (Inpatient Medications for Outpatients) \norder because it had a clinic location. The code will be updated to \nrecognize a unit dose.\ndate & time will be required before IMO logic is executed!\n \nThis patch addresses the issue of an inpatient's medication's stop time \nbeing inadvertently set to 24 hours.\n \nA medical student at a site erroneously changed the location of an \ninpatient while ordering a unit dose medication in CPRS. The clinic \nlocation the student chose had a default stop time on orders of 24 \n\n
\nA site reported a problem with the fact that medication route did not\nup. They are:\n \nSM Start Med Route\nEM End Med Route\nSMF Start Med Route field\nEMF End Med Route field\n \nThese control codes are defined by using FileMan V. 22.0 and editing the\nCONTROL CODES multiple (#3.2055) of the TERMINAL TYPE file (#3.2).\n \nappear on the IV label. This patch corrects this problem by adding the\nEach printer can have different values required in order to properly\nprint the route. Please note that it may be necessary to adjust the \nlabel length through the SITE PARAMETERS (IV) option in order for the \nlabel to print correctly.\n \nThe following is one example of the setup for a Zebra 105SL printer.\n \n \nNUMBER: 12 CTRL CODE ABBREVIATION: SM\n FULL NAME: START MED ROUTE\nmedication route to the IV label. PSI-05-107, HD115653\n CONTROL CODE: W "^FO",PSJBARX,",",PSJBARY,"^A0N,36,30",!!\nNUMBER: 13 CTRL CODE ABBREVIATION: EM\n FULL NAME: END MED ROUTE CONTROL CODE: S PSJBARY=PSJBARY+40\nNUMBER: 14 CTRL CODE ABBREVIATION: SMF\n FULL NAME: START MED ROUTE FIELD CONTROL CODE: W "^FD"\nNUMBER: 15 CTRL CODE ABBREVIATION: EMF\n FULL NAME: END MED ROUTE FIELD CONTROL CODE: W "^FS",!\n \nThe resulting Bar Code IV Label Example, which includes Medication Route\nis shown:\n \n \n *520V452*\n[65] 9111 ONE EAST 03/19/02\nPSJPATIENT1,ONE B-12\n \nACETAMINOPHEN 100 MEQ\n0.9% SODIUM CHLORIDE 100 ML\n \nDose due at: ________\nROUTE: INTRAVENOUS\n****Important Note****\n100 ml/hr\nFld by: ____ Chkd by: ____\n1[1]\nThe decision of the workgroup was that the medication route should appear\nin a larger font than the remaining text. If you do not define the\nfollowing correctly, the medication route will not be in a larger font.\nIn order to allow this functionality, four new control codes must be set\n\n
\n1. During testing of Remote Data Interoperability (RDI), a problem was \nproblem by ensuring that Analgesic order checks only match against the \nspecific class: CN101 to CN101. HD0000000161499\n \n3. One feature of RDI is the notification to the user when processing \norders that only local data is being used - if the remote data is \nunavailable. Several sites reported issues with this mechanism. This \npatch corrects this problem by performing the check for remote data \navailability upon entering the patient's chart, rather than on each order.\n \n4. The list of remote allergies has been added to Patient Information \ndiscovered with the order checks involving remote allergies. Not all of \nscreen. If a patient has the same allergy information from several remote\nsites, it will only be listed once.\nthe remote allergies were being included when doing order checks using VA \nDrug Class. This patch corrects this problem.\n \n2. An issue with too many false positive order checks was discovered when \ndoing order checks on certain drug classes. Analgesics, as a class, were \nperforming order checks across all members. For example: class CN101 was \ngenerating an order check for class CN102. This patch corrects this \n\n
\nThis patch will correct three problems with the Action Profile reports \n[PSJU AP-1] and [PSJU AP-2] would vary from patient to patient. It was \ndecided by the Inpatient Medications Workgroup that the number of lines \nprinted for this section should be standardized to 10 lines.\n \nThe second problem occurs only with the Action Profile 2 report, [PSJU \nAP-2]. The problem only occurs if the report is printed to the screen. \nThe report prints properly if printed to a printer. If the patient has a \nverified allergy, a verified adverse reaction, or one of each, the \nAllergy and Adverse Reaction section of the report is printing "No \nAllergy Assessment". This patch will correct this problem so the AP-2 \nfrom three Remedy tickets, HD118347 HD120274, and HD68707, as well as one \nreport is consistent with the AP-1 report, and shows the correct allergy \nand adverse reaction information for the patient.\n \nThe third Action Profile Report issue was logged because one-time orders \nare appearing on the Action Profile-1 [PSJU AP-1] and Action Profile-2 \n[PSJU AP-2] reports with the option available to the provider to RENEW \nthe orders. The ability to renew one-time orders was removed due to a \npatient safety issue. Having the renew option available to the provider \ncould lead to a reoccurrence of the patient safety issue.\n \nundefined variable error with the Patient Profile, [PSJU PR], in ticket \nThe Undefined Variable Error occurs with the Patient Profile, [PSJU PR]. \nWhen attempting to filter the profile at any WARD prompt, if the user \npresses ENTER or the up-carat (^), instead of being taken to the previous \nfilter choices or the main menu, the user is taken to a prompt to filter \nby Room/Bed or Patient. If the user again presses ENTER or ^, an \nundefined variable error occurs.\nHD120176.\n \nThe first Action Profile Report problem was a result of internal testing \nwith patch PSJ*5*157, wherein it was noted that if a device used for \nprinting did not have a standard page length, the number of lines printed \nin the Additional Medication Orders section of the Action Profile reports \n\n
\nUser reported that when they edited the Schedule from a "continuous Type" \nto a one-time type, the Schedule type remained "continuous". This caused\nBCMA to not display the order on the Missed Medications Report.\n \nIt was also found during the internal testing of this patch, it was \nnoticed that the "administration times" could be automatically updated\nbased on the Schedule being entered. While this logic is correct, it did\nnot display the "highlighting" of the administration times as is the\nstandard when a field is changed.\n\n
\nThis patch addresses one Patient Safety Issue contained in one Remedy \nthis on their end with patch OR*3*254. Because of the CPRS fix, \nInpatient Meds should never receive an invalid duration/limit from CPRS. \nHowever, it was discussed with the Inpatient Meds workgroup, and they \nagreed that Inpatient Meds should make a contingency plan fix just in \ncase some future CPRS project removes the fixes in place from OR*3*254. \nAs a result, Inpatient Meds will now be able to handle an invalid \nduration/limit should one ever be received from CPRS.\n \nThe fix agreed upon by the Inpatient Meds workgroup will do three \nthings. First, it will NOT allow the pharmacist to FINISH the order. \nticket.\nSecond, the duration/limit field displayed to the pharmacist will read \n*INVALID DURATION/LIMIT*. Third, the Stop Date for the order will read \n"CANNOT CALCULATE".\n \nOR*3*254 is an independent CPRS patch, and is not required for this \nInpatient Meds patch.\n \nPSI 06 066\nThis addresses Remedy ticket HD146661.\n \nThe site reported an issue that if they used a leading zero for the \nlimit/duration of an IV, in this case 0.5L, the stop date calculated for \nthe order was 6 minutes after the start date/time. CPRS has addressed \n\n
\n1. A site reported a problem with the new duration field that was added to\n \nIn order to assist in communications with the provider, an alert will be \nsent to the ordering provider whenever the duration they entered is not \nused to calculate the stop date of the order. HD0000000111592\n \n2. Several sites reported an error occuring when entering an IV order \nthat contained an allergy order-check. This patch corrects this problem. \nHD0000000186397, HD0000000187239, HD0000000187452, HD0000000187507.\nCPRS GUI v25. In response to a patient safety issue, this field was added \nto the IV Fluid order dialog. In addition, Inpatient Medications V. 5.0 \nwas modified to always have the duration field be used for the stop date \ncalculation. This has caused problems in sites where they have policies \nthat say certain medications can only be written for a certain period of \ntime. This patch corrects this problem by modifying Inpatient Medications \nV. 5.0 to consider the duration the same way as all other stop date \nparameters, rather than as an override.\n\n
\n \nall orders for a patient are grouped together by the patient's name\nregardless of location. HD84581, HD94525, HD94701, HD94753,HD94951, \nHD9500, HD95644, HD96287, HD97627, HD99007, HD101172, HD121955,\nHD127037, HD130450, HD133140, HD133726, HD151842, HD152395, HD152987,\nHD153754, HD154263, HD155098, HD155822, HD157154, HD166444, HD176045, \nHD181032, HD181254, HD184077 \n \nThe following prompts are included when printing by Ward, Ward Group, \nClinic, or Clinic Group.\n \n1. Sites reported that location designation for inpatients who received \nSelect by GROUP (G), WARD (W), CLINIC (C), or PATIENT (P): WARD\nInclude Clinic Orders? Y/N\nIf Yes is selected, both ward and clinic orders are printed for\npatients on a ward.\nIf No is selected, only the ward orders are printed.\n \nSelect by GROUP (G), WARD (W), CLINIC (C), or PATIENT (P): GROUP\nSelect by WARD GROUP (W) or CLINIC GROUP (C): WARD\nInclude Clinic Orders? Y/N\nIf Yes is selected, both ward and clinic orders are printed for\norders in a clinic was incorrect. In some cases the clinic location was \npatients in a Ward Group.\nIf No is selected, only the ward orders are printed for patients in a\nWard Group.\n \nSelect by GROUP (G), WARD (W), CLINIC (C), or PATIENT (P): CLINIC\nInclude Ward Orders? Y/N\nIf Yes is selected, both clinic and ward orders are printed for\npatients in a clinic.\nIf No is selected, only the clinic orders are printed.\n \noverwriting the ward location designation. In many instances an error \nSelect by GROUP (G), WARD (W), CLINIC (C), or PATIENT (P): GROUP\nSelect by WARD GROUP (W) or CLINIC GROUP (C): CLINIC\nInclude Ward Orders? Y/N\nIf Yes is selected, both clinic and ward orders are printed for\npatients in a Clinic Group.\nIf No is selected, only the clinic orders are printed for patients in a\nClinic Group.\n \n \n2. After the installation of PSJ*5.0*111 and PSJ*5.0*131, the formatting \nappeared in the routine PSGMAR1 for printing the 24 hr MAR.\non the MAR reports was adversely affected. Sites reported pagination was \noff, pages displayed too much empty space, and the signature block no \nlonger appeared at the bottom of each page.\n \nCode modifications have been made in the MAR routines to correct the \nformatting problems. Page numbering has been corrected. The signature \nblock prints at the end of each page. Pending orders, non-clinic and \nclinic orders will display in the correct location on\nthe MAR report. Orders with a stop date/time greater than or equal to the \nselected 24 Hour MAR start date/time will print out correctly. HD94303, \n \nHD94836, HD95397, HD97108, HD107645, HD114937, PSI-06-002\nThis patch corrects this issue by adding new prompts to aid in printing \nout orders for both ward locations and clinics. No location designations \nare overwritten. When printing by Ward Group/Patient, or by Ward/Patient, \n\n
\n \nThis patch will correct an error which can occur for any IV Drug order\ntype which uses an Administration Schedule but the Administration Schedule\nused does not have a Package Prefix = 'PSJ'. The error occurs when a user\nattempts to view the Long profile of the order in PSJ OE [Inpatient Order\nEntry].\n\n
\n1. When non-pharmacist users enter unit dose drug orders they cannot\n complete the order without entering a dispense drug. This patch will\n allow non-pharmacist users to accept unit dose orders without a\n dispense drug.\n\n
\n1. A site reported a problem with the medication route being blank on the\nBCMA field (#8) from the MEDICATION ROUTE file (#51.2) will now be sent in\nthe API. HD0000000166204, HD0000000164890, PSI-06-152, PSI-06-158\n \n2. In support of the BCMA V. 3.0 project BCMA HSC-III, two changes are \nrequired to the APIs that supply information to BCMA. First, the flag \ninformation for both Unit Dose and IV orders has been added to both the \nsummary and detail APIs. Second, an indicator has been added that will \ntell BCMA that this order would have triggered a notification to the \nSTAT/NOW mail group.\n \nBar Code Medication Administration (BCMA) V. 3.0 Virtual Due List. During\n3. During testing of the BCMA V. 3.0 project BCMA HSC-III, a problem was \ndiscovered with the API that determines if an order should trigger a \nnotification to the STAT/NOW mail group. If the parameter which controls \nthe trigger was not defined, all orders would be flagged. This patch \ncorrects this problem. However, it is important to note that if the \nparameter PRIORITIES FOR ACTIVE NOTIFY is not defined, no order will be \nflagged as stat for the purposes of BCMA.\ninvestigation of possible corrections for this, it was determined that\nanother issue needed to be addressed with how to determine when to prompt\nfor an injection site.\n \nThis patch assists to correct these problems by adding two new items to \nthe Application Programming Interface (API) from Inpatient Medications V. \n5.0 to BCMA. The NAME field (.01) as well as the PROMPT FOR INJ. SITE IN \n\n
\nSite reported that the incorrect Orderable Item was selected when the\nentry was entered in "lowercase". This caused the incorrect medication\nto be given.\n\n
\nThis patch will provide a temporary fix as detailed in Patient safety \nduplication when the order does not file.\n \nThis patch will modify the error message to make it more noticeable and \nrobust.\nissue PSI-07-075 for BCMA. \n \nWhen using the CPRS Med Order Button (MOB), it was discovered that certain\nhardware configurations allow a "virtual" IP address. This causes a\nsingle user to be logged into two physical nodes simultaneously. When\nthis happens, the order placed in CPRS MOB cannot be filed. The user\nreceives an error box which states "Missing data, unable to file." The\norder does not show up on the VDL. It was determined that there is risk of\n\n
\nCurrent functionality concerning the duplicate order checks displays all\naddition, all duplicate Outpatient orders found, are grouped together and\ndisplayed prior to all other order check results and will be used for\ninformation purposes only. The current process will be modified so that\nwhen a duplicate order check is performed, the duplicate Inpatient orders\nare displayed in a numbered list. The user will then be prompted to select\nwhich, if any, of the listed duplicate orders should be discontinued. The\nuser may choose to select none, thus leaving all orders intact. The \nresults from both duplicate order checks, Duplicate Drug and Duplicate\nDrug Class, will be presented together. Duplicate order checks occur at\nseveral points in the ordering process, including, when entering a new\nduplicate drug and duplicate drug class orders found, but does not allow\nmedication order, when renewing an existing medication order, when\nfinishing an order, and when editing an order's drug.\nthe user to select these for discontinuation. If the user wishes to\ndiscontinue any of the presented duplicates, they must wait until after\nthey are done with the current order process in which the duplicate order\nchecks presented their results. The major functionality change to the\nInpatient Medications software will consist of allowing users to select\nfor discontinuation any duplicate Inpatient orders found, at the time\nthese duplicates are presented by the duplicate order checks. In\n\n
\nA site reported a problem with renewed pending orders. The\ndose limit exists for the selected Orderable Item, and the limit is less\nthan the default stop date, the earlier stop date and time will be\ndisplayed."\n \nThe way the screen defaults in pharmacy for finishing would lead the\npharmacist to finish the new order prior to finishing the renewals.\nThis creates the potential for medication orders to default to an\n"incorrect" stop date/time. This problem caused a patient to completely\nmiss receiving a newly ordered medication, as the new order expired prior\nto the first scheduled dose time.\nPharmacist's User Manual states:\n \nThe following example shows the way the screen displays the orders from\nthe PENDING/NON-VERIFIED option:\n \n- - - - - - - - - - - - - - - - - A C T I V E - - - - - - - - - - - - - -\n 1 MULTIVITAMINS TAB C 04/01 04/08 R\n Give: 1 TABLET PO QAM (07)\n - - - - - - - - - - - - - - - - P E N D I N G - - - - - - - - - - - -\n 2 CAPTOPRIL TAB ? ***** *****\n Give: 25MG PO QAM (07)\n"When the SAME STOP DATE ON ALL ORDERS parameter is set to\n - - - - - - - - - - - - P E N D I N G R E N E W A L S - - - - - - - -\n 3 MULTIVITAMINS TAB ? ***** ***** P 04/06\n Give: 1 TABLET PO QAM (07)\n \n \n \nThis patch corrects the problem by reversing the order in which the\nPENDING and PENDING RENEWALS are displayed. With the entries reversed\nthe user will finish the PENDING RENEWAL order first, followed by the\nPENDING order, and the correct stop date/time will be displayed.\nyes, the module will assign a default stop date for each patient. This\nHD0000000138249, PSI-06-043\ndate is initially set when the first order is entered for the patient. A\nnew default stop date is assigned for the patient when an order is\nrenewed and the order's stop date plus three days is greater than the\ncurrent default stop date. This date is shown as the default value for\nthe stop date of each order entered for the patient. However, if a day or\n\n
\nDuring testing of the Bar Code Medication Administration (BCMA) project \nDOSE sub-file (#55.06) of the PHARMACY PATIENT file (#55) which will be \nexported in a Pharmacy Data Management V1.0 patch.\nBCMA-HSC Phase III, an issue was discovered with the order flag comments \nfor unit dose orders. There is not enough space to store the entire \ncomment, so the text is truncated. This patch corrects this problem for \nBCMA by storing the most recent text in an additional location. The \ncomment will still be stored in the current location. It will also be in \nthe MOST RECEMT FLAG COMMENT field (#129) of the NON-VERIFIED/PENDING file\n(#53.1) which is exported in this patch. For active unit dose orders, it\nwill be stored in the MOST RECENT FLAG COMMENT field (#128) of the UNIT\n\n
\nRemove all PSJ*5*175 changes.\n\n
\n \nThis patch will correct 2 problems and remove 1 obsolete menu option \nwithin the Inpatient Medications package.\n\n
\nWhen an order from CPRS is processed in the Inpatient Medications\napplication the Comments field is automatically checked to verify that it\ndoes not contain multiple spaces. If it does, the software will remove\nthese spaces. When this happens, a Change Action is generated in CPRS.\nThis Change Action will cause CPRS to recalculate the Instructions. In\nsome cases, the recalculation of the Instructions will result in the\nstrength being added to the instuctions. This may result in the patient\nreceiving an incorrect dose.\n\n
\nThis patch contains changes in support of Computerized Patient\n medication route, that route will be used as the default. If there are\n any differences, there will be no default medication route.\n \n- Inpatient Medications V. 5.0 will send to BCMA V. 3.0 the full\n medication route name for display on the Virtual Due List (VDL).\n \n2. INFUSION RATE CHANGES\n-------------------------\n- Inpatient Medications V. 5.0 now accepts infusion rate from CPRS in both\n ml/hour and as 'infuse over time'.\nRecord System (CPRS) V. 1.0 GUI v27 release.\n \n- In the order view screen for an order with an intermittent IV type, the\n infusion rate now displays as "Infuse Over" followed by the time. For\n example, "Infuse Over 30 minutes".\n \n The infusion rate for an intermittent IV order can be null.\n \n3. IV TYPE CHANGES\n-------------------\n- Inpatient Medications V. 5.0 shall accept an IV type of "I"\n \n (Intermittent) or "C" (Continuous) from CPRS V. 1.0. When an IV type of\n CONTINUOUS is received, Inpatient Medications V. 5.0 defaults to an IV\n type of Admixture. When IV type of INTERMITTENT is received, \n Inpatient Medications V. 5.0 defaults to an IV type of Piggyback.\n Inpatient Medications V. 5.0 sends to CPRS V. 1.0 updates to an order's\n IV type.\n \n- Inpatient Medications V. 5.0 now accepts schedule information from\n CPRS V. 1.0 for intermittent IV orders entered via the IV Fluid\n Ordering Dialog. Inpatient Medications V. 5.0 also sends to\n1. MEDICATION ROUTE CHANGES\n CPRS V. 1.0 any schedule changes for intermittent IV orders.\n \n- A new field, IV TYPE CATEGORY (#128) is being added to the NON-\n VERIFIED ORDERS file (#53.1). The IV TYPE CATEGORY will be "C"\n (Continuous) for orders with an IV TYPE of Admixture, Hyperal,\n Non-Intermittent Syringe, or Chemotherapy with a CHEMOTHERAPY TYPE\n of Admixture, Hyperal, or Non-Intermittent Syringe. The IV TYPE\n CATEGORY will be "I" (Intermittent) for orders with an IV TYPE of\n Piggyback, Intermittent Syringe, or Chemotherapy with a CHEMOTHERAPY\n TYPE of Piggyback or Intermittent Syringe.\n----------------------------\n \n4. RENEWED ORDER CHANGES\n-------------------------\n- When discontinuing pending renewal orders, Inpatient Medications V. 5.0\n will provide the user an option to discontinue the pending renewal\n order and/or the original orders. The pharmacist shall be given the\n option to discontinue the pending order, both orders, or exit the\n discontinue function.\n \n5. REMOVE CALLS TO OBSOLETE ROUTINE\n- Inpatient Medications V. 5.0 will use the medication route received from\n------------------------------------\n- At the request of CPRS V. 1.0, active calls to obsolete routine OR3CONV\n have been removed from Inpatient Medications V. 5.0. \n \n6. EXPECTED FIRST DOSE FOR ONE-TIME ORDERS (HD 98365)\n------------------------------------------------------\nProblem:\n During testing of the CPRS V. 1.0 GUI v26 release, sites reported a\n problem with an incorrect display of expected first dose for orders\n with a schedule type of "ONE TIME".\n CPRS V. 1.0 as the default when finishing an IV order entered via CPRS\nResolution:\n If the schedule type is "ONE TIME", do not display an Expected\n First Dose for the order.\n \n7. CORRECT ABBREVIATION OF MILLIMOLE (HD 145562)\n-------------------------------------------\nProblem:\n The correct abbreviation for the word MILLIMOLE, which is MMOL\n is not available in the system.\nResolution:\n V. 1.0. For new orders entered via Inpatient Medications V. 5.0, if all\n The abbreviation for Millimole, "MMOL", will be included in\n this patch.\n of the orderable items associated with an order contain the same default\n\n
\n1. If the order's START DATE/TIME was the same as the ADMIN TIME, an\n \n3. Orders were being rejected with a message Invalid patient class. This\npatch corrects this problem.\n \n4. An undefined variable P(17) was sometimes occurring when returning from\nhidden menu options when finishing an order. This patch corrects this\nproblem.\n \n5. When using the Individual Labels (IV) [PSJI LBLI] option, the first\npatient's Allergies/Reactions and Narratives were displayed for all\nextra dose was calculated when the user entered the number of doses in the\npatients selected while still in this option. This patch will correct this\nproblem.\n \n6. The variable PSIVSITE was undefined when IV orders were edited by the\nnursing staff in the Non-Verified/Pending Orders [PSJU VBW] option.\nShowing IV orders in this option is new functionality added to Inpatient\nMedications V. 5.0. Actions taken on IV orders have always been controlled\nby the Menu option and not from any pharmacy keys. After installation of\nthis patch users without the Pharmacist key will not be allowed to take\naction on IV orders from the Non-Verified/Pending Orders [PSJU VBW]\nSTOP DATE/TIME field. After installation of this patch the dosage will\noption.\n \n7. A problem was reported with the Non-Verified/Pending Orders [PSJU VBW]\noption where when the user selected pending orders, Unit Dose orders, and\nthen Ward or Ward group patients with only pending IV orders were being\nincluded in the list of patients. This patch will correct this problem.\ncalculate correctly for this situation.\n \n2. If an order was placed on hold and then taken off of hold the Inpatient\nprofile printed by the pharmacist showed the order as active while the\nsame profile printed by the nurse showed the order as marked to be placed\non hold. This patch corrects this problem.\n\n
\nThis patch addresses one Patient Safety Issue, PSI-08-008 for remedy \nticket HD228442.\n\n
\nThis patch corrects the typographical error in 2 routines within \n \nOverview of Remedy ticket(s):\n------------------------------------------------------------------\nHD219677:\nThere is typographical error in line tag ENHEAD+21^PSJHEAD and \nH1+15^PSGCAPP0 that should be a plus sign instead of underscore.\n \nHD234014:\nWhen an IV Admixture has a rate of less than 10ml/hr the calculation of \nbags needed till the next scheduled IV batch run is inaccurate.\nInpatient Medication package, and the calculation of IV labels when\n \nProblem (219677)\n------------------------------------------------------------------\nThere is typographical error in line tag ENHEAD+21^PSJHEAD and \nH1+15^PSGCAPP0. It should be a plus sign instead of underscore\n \nResolution (219677)\nThis does appear to be a typographical error, it would never result in a \nfunctional defect. EN+3^PSJHEAD and H1+15^PSGCAPP0 is modified to replace \nthe underscore ("_") with a plus sign ("+"). \ninfusion rate is less than 10ml/hr\n \nProblem (234014)\n------------------------------------------------------------------\nIf the infusion rate is less than 10ml/hr the number of IV bags needed is \ncalculated incorrectly.\n \n \nResolution (234014)\nThe pattern match for infusion rate in line tag EN+3^PSIVORE is looking \nfor at least 1 digit, with a period as optional and at least 1 digit \n \nafter the period. This only works if the infusion rate is 2 digit or \nmore. The pattern match in EN+3^PSIVORE is modified to make the digit \nafter the period as optional so the pattern match can also be used when \nthe infusion rate is a single digit.\nThis patch addresses the following Remedy ticket(s):\n------------------------------------------------------------------\nHD219677 (Original) Potential typographical error.\nHD234014 (Original) IV ADMIX rate under 10ml/hr calculates \n bags wrong\n\n\nThis patch Will correct the following Remedy tickets.\nHD245298 - PSI-08-060 - 1 IV order retaining original Duration/Total \nVolume\n\n
\nThis patch resolves two issues in the Inpatient Medications package.\nif the location is a clinic, and then set using the same variable as ward.\n \n2. After the release of Patch PSJ*5*110, MAR labels do include the\norder/renewal date on the left side of the label, which is attached\nto the MAR. It only appears on the right side, which is discarded.\nThe date has been placed on left side as well as the right side.\n\nRoutine PSGLOI was modified to correct this problem. If the order is not\npending, the order/renewal date is set at the left hand side of the label.\n\n\n\n1. When stat medications are ordered using Inpatient Medications for\nOutpatients (IMO), the resulting notification email lacked the\nname of the clinic. Ward names were included correctly. Clinic names\nwere added. The mail group receiving the notification is PSJ STAT NOW\nACTIVE or PSJ STAT NOW PENDING.\n \nThe routines PSJHL4 and PSJHL4A were modified to establish a value for CLINIC\n\n
\nThis patch allows the DSS IV extract to be recreated.\n\n
\nDESCRIPTION\n PSGRFOUR variable\nHD210106 - Meds on extended profile do not match CPRS orders tab.\n============\n \nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nHD200323 - <UNDEFINED>COPY+10^PSIVOD\nHD193154 - Inappropriate Remote Order Check message\nHD211655 - Nurse finishes order and its active \nHD216471 - Renew single order routine setting the wrong node for the\n\n
\nThis Patch will disable the SPEED FINISH and SPEED VERIFY protocols.\n\n
\nThis patch will correct the following tickets:\nHD0000000193031 - Incorrect diet information on MAR header\nHD0000000169943 - Clinic Group not showing up on Non Verified/Pending \n report\nHD0000000258201 - 6 IV REPORT DIFFERENT FOR LOWER CASE\nHD0000000225877 - IV duration on CPRS order not calculated correctly as \n stop date\n\n
\nDescription:\nschedules entered for IV Piggyback orders via the CPRS IV Fluids Dialog.\npresents the user with the error message, "Your infusion rate is in an\ninvalid format", and the order cannot be completed.\n \nResolution:\n-----------\nIf the order has a fractional infusion rate < 1 ml/hr, the order must\ncontain a leading zero, and the system will view the infusion rate as\nvalid. (example - infusion rate must be 0.9 ml/hr to be valid)\nThe coding will affect routines PSIVSP, PSIVCHK, and PSIVORE.\nIf the user creates a schedule using the schedule builder, and uses the\nnew format of Day of Week@Schedule (example: MO-WE-FR@BID), and if the\nroot schedule (MO-WE-FR) exists in the ADMINISTRATION SCHEDULE File \n(#51.1), when the order is viewed in backdoor pharmacy, the\nadministration time(s) for the order will be null.\n \nProblem:\n--------\nAdmin times are null if a Day of Week schedule created via the schedule\n===========\nbuilder in CPRS exists in the ADMINISTRATION SCHEDULE File (#51.1).\n \nResolution:\n-----------\nIn PSGS0, do not QUIT before the admin times are set if the schedule\nis a Day of Week schedule, even if it exists in the schedule file.\n \n \n2. The second issue, Remedy Ticket HD246438 and its duplicates, is also \nlogged as Patient Safety Issue PSI-08-068,PSPO #782. This is an issue\n \nwith an invalid frequency for IV Piggyback orders. This issue has existed\nprior to the release of CPRS GUI v27, but the sites are reporting an\nincrease in the occurrence of the problem after the install of CPRS GUI \nv27. For unknown reasons, the frequency of some IV Piggyback orders is \nnull when it should contain a value.\n \nNo site or developer has been able to \nreproduce this issue at-will, and there does not appear to be any\npattern to the processes or procedures that precede the occurrence of this\nproblem. With this patch, if the frequency for an IV Piggyback order is\nThis patch contains four Inpatient Medications V. 5.0 fixes that sites\nnull, and it should contain a value, the code will attempt to directly\nset an appropriate frequency into the PHARMACY PATIENT File (#55) upon\nverification of the order, and upon the order becoming active.\n \nProblem:\n--------\nThe frequency is being set to null very sporadically for IV Piggyback\norders. No root cause is known.\n \nResolution:\nlogged during the compliance date period for the CPRS (Computerized \n-----------\nDuring the verification process, if the IV is intermittent, and the\nfrequency is null, attempt to re-set the frequency based on the name\nof the schedule as well as other variables that should\ncontain the value of the frequency. These changes are in routine \nPSIVORFB.\n \n3. The third issue, Remedy Ticket HD274682 and its duplicates, is an\nundefined variable error in the new Meds Tab sort for CPRS. The root\ncause of the problem is that a pointer to the PHARMACY ORDERABLE ITEM File\nPatient Record System) GUI v27 release.\n(#50.7) is missing in either the NON-VERIFIED ORDERS File (#53.1) or the\nPHARMACY PATIENT File (#55). Because the pointer does not exist, when\na temporary global is being built to display the orders for the patient, \nan undefined variable error occurs.\n \n \nProblem:\n--------\nVery old orders exist in the system that do not contain a pointer to\nthe orderable item. When the new Meds Tab sort routines attempt to\n \nuse the pointer value as a subscript in a ^TMP global setting, and the\npointer's value is null, a null subscript error occurs. This causes\na hard error in CPRS and shuts CPRS down.\n \nResolution:\n-----------\nIf the pointer to the orderable item does not exist, the routines will\nuse the phrase "Orderable Item Not Found" as the subscript value in place\nof what should be the name of the orderable item. This allows the Meds\nTab sort routines to process without error, and the patient's medications\n \nappear without problems on the CPRS Meds tab. The updated routines are\nPSJORRO, PSJORRN, and PSJORRN1.\n \n4. The fourth issue addressed by this patch is Remedy Ticket HD280040, \nwhich deals with an inconsistency between CPRS and backdoor pharmacy\nwith respect to continuous IV orders. \n \nIf the IV order originates from CPRS, a\nfractional infusion rate of < 1 ml/hr (0.9 ml/hr for example), backdoor\npharmacy allows the infusion rate, and the order can be finished and\n1. The first issue, Remedy Ticket HD280022, pertains to Day of Week\nverified without issue. However, if the order originates from backdoor\npharmacy, a fractional infusion rate < 1 ml/hr is not accepted, and the\nuser is presented a message "Invalid Infusion Rate", and they cannot\nfinish and verify the order. This patch will make backdoor pharmacy\nbehave consistently with CPRS.\n \nProblem:\n--------\nIf an order is entered via backdoor pharmacy for a continuous IV, and the\norder is created with a fractional infusion rate of < 1 ml/hr, the system\n\n
\nThis PSI patch addresses the following problem(s):\n \nWhen a lab order is entered in CPRS with only a date in the Collection \nDate/Time, the midnight draw times do not display.\n\n
\n1. IVPB orders had asterisks across all the dated boxes on the MAR even\n Action Profile #2\n Patient Profile (Extended)\n \n3. The MAR will be able to be sorted by the orders schedule type or\n alphabetically by the medication names. The following are steps to use\n to set the sorting of the MAR:\n \nSelect OPTION NAME: PSJU MGR Unit Dose Medications\n \n(Inpatient Medications - Version 5.0 //)\n though the orders were still acitve. After the installation of this\n \nWELCOME, PHARMACIST,ABC! (PHARMACIST)\n \n \n Align Labels (Unit Dose)\n Discontinue All of a Patient's Orders\n EUP Edit Inpatient User Parameters\n Hold All of a Patient's Orders\n IOE Inpatient Order Entry\n IPF Inpatient Profile\n patch the asterisks will print on the correct dates.\n INQuiries Menu ...\n Label Print/Reprint\n Non-Verified/Pending Orders\n Order Entry\n PAtient Profile (Unit Dose)\n Reports Menu ...\n Supervisor's Menu ...\n \n \nSelect Unit Dose Medications Option: SUPervisor's Menu\n \n \n \n Administering Teams\n MANagement Reports Menu ...\n Order Set Enter/Edit\n PARameters Edit Menu ...\n PATient Order Purge\n PIck List Menu ...\n Ward Groups\n \n2. Add the institution name to the following reports (E3R#11366):\n \nSelect Supervisor's Menu Option: PARameters Edit Menu\n \n \n AUto-Discontinue Set-Up\n IUP Inpatient User Parameters Edit\n IWP Inpatient Ward Parameters Edit\n Systems Parameters Edit\n \n \n 7 Day MAR\nSelect PARameters Edit Menu Option: SYStems Parameters Edit\n \nNON-FORMULARY MESSAGE:\n 1>This is the Non formulary message!!!\nEDIT Option: \nPRINT 6 BLOCKS FOR THE PRN MAR: \nPRINT DIET ABBR LABEL ON MAR: \nMAR SORT: ?\n Choose from: \n 0 Sort by order's Schedule Type and then Medication Names.\n 14 Day MAR\n 1 Sort by order's Medication Names.\nMAR SORT: 1 Sort by order's Medication Names.\n 24 Hour MAR\n Action Profile #1\n\n
\nThis is part 2 of the Frequency correction. This patch will re-enable \nPSJU LM SPEED FINISH and PSJU LM SPEED VERIFY.\nand correct the following tickets.\n PSPO# 1221 HD297810 - 1 Orders did not show in BCMA.\n d - HD289777 - 4 Q14 coming up to be given every 2 days for one order\n d - HD289086 - 6 BCMA -Order Problem Schedule Frequency Issue\n PSPO# 1274 HD302185 - 1 Possible patient safety issue with med order\n PSPO# 1278 HD302727 - 1 Bar Code Med Admin issue - Admin Times\n\n
\n I M P O R T A N T\n This patch description includes only the informational portion of\n PSJ*5*161. Please refer to the "Software Retrieval Instructions" and\n "Installation Instructions" sections of the PSU*4*5 patch description\nfor instructions on how to acquire and install the patch software.\n \n*************************************************************************\n \n \n ********************* WARNING *********************\n *****************************************************\n \n If your facility has the Pyxis/Omnicell/McKesson interface \n from ILC this patch will overwrite any "local" modifications \n in routine PSGOETO. This could affect certain orders being \n sent across this interface. The modifications will have to \n be reintroduced following installation of this patch.\n *****************************************************\n *****************************************************\n \n \nThis patch addresses a request which supports the Pharmacy Benefits\n*************************************************************************\nManagement (PBM) Extracts Enhancement #3 project. In order to allow the\nretransmission of only those patients who have had demographic updates,\nOutpatient Pharmacy V. 7.0, Inpatient Medications V. 5.0, Registration\nv. 5.3 and Pharmacy Data Management V. 1.0 were modified to build an\nentry for re-transmission in PBM PATIENT DEMOGRAPHICS File #59.9.\n \nWhenever the FIRST SERVICE DATE field (#.07) in the PHARMACY PATIENT \nfile #55 is updated for a patient, an entry is queued for retransmission.\n This Inpatient Medications patch PSJ*5*161 along with PSU*4*5, PSO*7*170\n and DG*5.3*671 is being released in a single KIDS software distribution \n host file, PSU_4_P5.KID as part of the Pharmacy Benefits Management (PBM)\n Extracts Enhancement #3 project. PSS*1*99 which is also part of this\n enhancement is being released separately.\n \n\n
\nThis patch wil resolve the following issues:\n \n1) CPRS displayed -1 in the Start and Stop times of the order\n2) Subscript error in the missed mediciton report \n\n
\nOrder Checks During Order Edits\n\n
\nThis patch contains a partial resolution for Patient Safety Issue\nActivity Log for the order that reflects this change. Medication\nerrors have happened due to edited dispense drugs, and there is\ncurrently no audit trail to help track the information.\n \nResolution:\n-----------\nThis enhancement will compare the original dispense drug(s) for\nthe order with the edited value for the dispense drug(s). If\nthere is a difference between the values, the modified code in\nroutine PSGOE92 will call the routine that logs entries into the\nPSI 07-073, PSPO #526, and is outlined in Remedy Ticket HD67749.\nActivity Log for the order.\n \nThe structure for the activity log entry will be:\nDATE^DUZ^6000^FIELD^OLD\n \nDATE = Timestamp date/time of the edit.\nDUZ = The system DUZ of the person making the edit.\n6000 = A code denoting that a field was edited.\nFIELD = The name of the field that was edited.\nOLD = Old data before the field was edited. This contains the\nAnother portion of this PSI is being addressed by the Vista\n dispense drug IEN, dispense drug name, and units per dose.\nMaintenance Team in a separate patch, PSJ*5.0*216.\n \nProblem:\n--------\nIf the pharmacist must edit the dispense drug(s) for an active\nUnit Dose order, there is currently no entry made in the\n\n
\n HD0000000139263 involves multiple additives with values in the MESSAGE \n Dose report's status field. The problem is due to Inpatient Meds not \n sending CPRS the complete information for the status if the order was \n discontinued due to edit.\n \n HD0000000159948 Within Parameters Edit Menu [PSJ PARAM EDIT MENU], the \n option Clinic Definition [PSJ CD] asks the user for a CLINIC GROUP \n NAME. This prompt is in error and the option should end if no new \n clinic is chosen for edit. This issue has no negative impact on the \n patient but is an inconvenience to the user of the option.\n \n field (#14) of the IV ADDITIVES file (#52.6). When an IV label \n HD0000000168525 When exiting the option by typing an "^" up-arrow at the \n Report/Label device prompt in Site Parameters (IV) [PSJI SITE PARAMETERS]\n option, the system will default "TELNET" into the field even though a \n value already exists. The software should retain the existing \n report/label device at this prompt and not change the default device. \n This issue has caused the user to print reports and labels to \n unintended devices.\n \n HD0000000175185 concerns the Pick List Warning Message. A user created \n a pick list with a stop date which was far into the future. This made \n prints, and the IV order contains multiple additives, if more than one \n the pick list inaccessible, and the list could not be deleted. A \n warning message will be displayed to the pharmacist if the pick list \n stop date is more than 7 days into the future.\n additive has a MESSAGE field value, only the message of the first \n additive in the IV order will display on the label. \n \n HD0000000139800 The CPRS Unit Dose report shows the status of the unit \n dose orders for a given patient. If an order has the status \n "Discontinued due to Edit", nothing is displaying in the CPRS Unit \n\n
\nThis patch addresses one Patient Safety Issue, PSI 06 101, contained\ngiven in Bar Code Medication Administration (BCMA) Version 3.0. As a\nresult, the medication was given multiple times, despite the ordering\nprovider's intent to allow only one optional dose. In this scenario, ONE\nTIME is the name of a schedule defined in the Administration Schedule\nfile with a type of One Time.\n \nBased on workgroup feedback, the issue will be addressed by treating any\norder containing a One Time schedule (i.e., a schedule defined in the\nAdministration Schedule File with a type of One Time) as a order that is\nto be given only once, regardless of the order's Schedule Type, or the\nin two Remedy tickets: HD153724 and HD166076.\npresence of the PRN modifier appended to the order's schedule. The\nletters PRN are appended to the schedule name when the PRN check box is\nchecked during order entry, from the ordering dialog in CPRS. The PRN may\nalso be appended to the schedule name manually from Inpatient Medications\nVersion 5.0 order entry options.\n \nThis patch constitutes the Inpatient Pharmacy portion of a multi-package\nbuild. It addresses Remedy ticket HD153724. The BCMA patch PSB*3*33\naddresses the BCMA portion, Remedy ticket HD166076.\n \nThe site reported Unit Dose medication orders entered with a schedule\nof ONE TIME PRN were not automatically discontinued after being\n\n
\nThis patch will be released as the Inpatient Medications portion of\nCurrently, for complex unit dose orders that contain an "AND" conjunction,\nthere is a possibility of the child orders containing overlapping\nadministration (admin) times. If the admin times overlap, it is possible\nfor a patient to receive too much of the medication at the overlapping\nadmin time.\n \nResolution\n----------\nThis enhanced functionality will compare the admin time string of the\nchild orders on either side of the "AND" conjunction and will capture\nthe Pharmacy Legacy Quarterly Enhancements team's FY09 Q4 effort.\nany overlapping admin times. If any overlapping admin times are\nfound, a warning message will be displayed to the pharmacist who is\nfinishing the order. The warning message will read:\n \n**WARNING**\n \nThe highlighted admin times for these portions of this complex order \noverlap.\n \nPart 1 has a schedule of BID and admin time(s) of 10-22.\n \nPart 2 has a schedule of QDAY and admin time(s) of 10.\n \nPlease ensure the schedules and administration times are appropriate.\nThis enhancement will address Patient Safety Issue PSI-07-055,\nPSPO #508, Remedy Ticket #180596, and was approved by the Inpatient\nMedications Workgroup.\n \nProblem\n-------\n\n
\nPatches PSJ*5*214 and PSN*4*193 are being released as part of the Class\n \n1. The option would quit prematurely after the user entered an up-arrow to\nexit a previous attempt to generate the report.\n \nProblem:\n--------\nThe variable QFLG used to denote the user's attempt to quit the option was\nleft defined following the aborted report attempt.\n \nResolution:\nIII to Class I conversion process. In combination, the two \n-----------\nRoutine PSJPDV updated to NEW variable QFLG.\n \n2. To generate a report for all drugs within a parent drug class required \nentry of each child class when specifying the report parameters.\n \nProblem:\n--------\nThere was no cross-reference in the VA DRUG CLASS file (#50.605) to\ndetermine the relationship between parent drug classes and \npatches address the need to provide multidivisional functionality within\nchild drug classes.\n \nResolution:\n-----------\nPatch PSN*4*193 introduces the necessary cross-reference, which is \nutilized by this patch to allow a user to enter a parent drug class. The \nsystem will then select all of the drugs in the hierarchy of that parent \nclass.\n \n3. The default response for the Number of Matches prompt did not \nthe Inpatient Medications package's Patients on Specific Drug(s) [PSJ\nreflect the most common answer to that question.\n \nProblem:\n--------\nCurrent functionality would count the number of unique entries selected \nby the user and present that number as a default response to the Number \nof Matches prompt. This assumed that a patient had to have all of the \nselected drugs in their profile in order to be listed in the final report.\n \nResolution:\nPDV] option. PSN*4*193 provides support within the National Drug File\n-----------\nThe default is changed to 1, reflecting a report in which the patient can \nbe on any of the selected drugs in order to be listed on the report. The \nuser can still enter a higher number to employ the previously defaulted \nfunctionality.\n \n4. The existing program did not include functionality to support the \nreporting needs of integrated or multidivisional facilities.\n \nProblem:\npackage and PSJ*5*214 delivers the enhanced functionality of the Patients\n--------\nThe report parameters do not ask for limitation of the output to \nspecified divisions, wards, or ward groups. The resulting list always \nincluded all patients meeting the criteria across an entire VistA \ndatabase.\n \nResolution:\n-----------\nA prompt is added to allow the user to select the DIVISION(s)\nfrom which patients will be reported. Sites that have only 1 division\non Specific Drug(s) [PSJ PDV] option.\nassociated with all of their inpatient wards will not see this new prompt.\n \nA prompt is added to allow the user to select the WARDS(s) from which\npatients will be reported.\n \nIf no selection is made for the division or ward prompt, the user will \nbe allowed to select one WARD GROUP from which patients will be reported.\n \nThis patch contains the following items:\n\n
\nThe purpose of this patch is to provide software enhancements for Order\nto improve the data that is displayed on the VDL. These order\nvalidation requirements will apply to Unit Dose Medications and applied\nto intermittent IV orders schedules (IV orders do not have Schedule\nType).\n \nThese enhancements are:\n \n1. Order Validation Check One\nFor Intermittent IV orders, references to an order's Schedule Type will\nrefer to either the TYPE OF SCHEDULE from the Administration Schedule\nValidation defined by the BCMA-Inpatient Medications Request for\nfile (#51.1), or PRN for schedule names in PRN format, or CONTINUOUS\nfor schedule names in Day of Week format.\n \n2. Order Validation Check Two\nIf an order has the Schedule Type of Continuous and the Schedule\nentered is NOT in Day of Week (Ex. MO-FR) or PRN (Ex. TID PC PRN)\nformat, then the system shall prevent the number of administration\ntimes associated with the order from being greater than the number of\nadministration times for that frequency, if the orders frequency is\nnumeric (minutes). The number of administration times can be less than\nSpecial Focus Group (SFG) Initial Request Analysis (IRA)\nbut not equal to zero administration times.\n \n3. Order Validation Check Three\nIf an order has a Schedule Type of Continuous and is an Odd Schedule, a\nschedule whose frequency is not evenly divisible by or into 1440\nminutes (1 day), then the system shall prevent the entry of\nadministration times.\n \n4. Order Validation Check Four\nIf an order has a Schedule Type of Continuous with a non-odd frequency\n \nof greater than of 1 day (1440 minutes) then the system shall prevent\nmore than one administration time.\n \n5. Order Validation Check Five\nIf an order has a Schedule Type of One Time or if an order is entered\nwith a schedule that is defined in the schedule file as One Time then\nthe system shall prevent the user from entering more than one\nadministration time.\n \n6. Order Validation Check Six\nCurrently, Inpatient Medications allows orders to be created with\nFor an order with a Schedule Type of Continuous where no\ndoses/administration times are scheduled between the order's Start\nDate/Time and the Stop Date/Time, then the system shall present a\nwarning message to the user and not allow the order to be accepted or\nverified until the Start/Stop Date Times, schedule, and/or\nadministration times are adjusted so that at least one dose is\nscheduled to be given.\n \n7. Change the Sequence of the Schedule Type and Schedule Prompts\nCurrently the order of the prompts in inpatient meds order entry is\nconflicting administration times, frequencies, schedules, and schedule\nSchedule Type followed by Schedule. The sequence of the prompts will\nbe changed so that the Schedule prompt falls before the Schedule Type\nprompt.\n \n8. Schedule Validation Requirement One\nWhen a schedule is selected at the Schedule Field the system shall\ndefault the Schedule Type for the schedule entered from the Schedule\nFile into the order.\n \n9. Schedule Validation Requirement Two\ntypes such that orders may not always display correctly on the Virtual\nIf the user changes the schedule, they will be given a warning message\nthat the administration times and the schedule type for the schedule\nselected will be defaulted to this order.\n \n10. Schedule Validation Check Three\nIf the schedule type is changed from Continuous to PRN the system shall\nautomatically remove any administration times that were associated with\nthe schedule so that the order will not include administration times.\n \n11. Modify VistA Help Text\nDue List (VDL) in the Barcode Medication Administration (BCMA)\nThe Help Text in Inpatient Order Entry was modified to add additional\ntext so the user is able to see the added constraints when entering\nAdministration Times.\napplication. This enhancement adds several new order validation checks\n\n
\n \n \n3. When using Inpatient Order Entry, the user should not be allowed to\nfinish an order entered as an IV Fluid in Unit Dose. This patch will\nprevent Fluid orders from being transferred to Unit Dose during the finish\nprocess. \n \n4. A change was made to prevent the deletion of a dispense drug from an\nactive unit dose order. The user may enter an inactive date for the\ndispense drug that is no longer to be used.\n \n1. An error would occur when printing a MAR label through CPRS if the\n5. When editing the SELF MED prompt for an order, an undefined error would\noccur if the user entered "1" instead of "Y" for yes. The software will\nnow recognize "1" for YES and "0" for NO at this prompt.\n \n6. An error was occurring when the user entered a leading zero when\nchoosing fields 1-9 in a Unit Dose order. This patch will prevent this\noccurence. (NOIS SFC-0198-61889, SFC-0198-61890)\n \n7. In the Inpatient Medications 5.0 KIDS build, three routines were\nmistakenly left out of this build. PSJORMA1,PSJORMA2, and PSJORMAR are\norder contained missing data. This patch will prevent this error. (NOIS\ncorrectly reinstalled by this patch. (NOIS CTX-0398-70640)\nCTX-0198-71417) \n \n2. If a Unit Dose order had a Schedule that contained "PRN", the Schedule\ntype would automatically default to CONTINUOUS if the user was using the\nAbbreviated Order Entry process. This patch will change the default\nSchedule Type to PRN if the order's schedule contains "PRN".\n\n
\n1. The original IV Solution's volume has an upper limit of 4000ml.\n NAME {2} field (#.02) defined in the IV SOLUTIONS file\n (#52.7) and print the MAR label, and the MAR.\n \n3. When entering a new IV order the user edits the Stop date, the\n default Stop date for the next IV order will be blank. This patch\n will make sure the default Stop date is displayed correctly.\n TO TEST: Enter a nw IV order, change the Stop date to a different\n value than the default date, accept the order. Enter another\n new IV order, the Stop date should have a default value\n instead of being blank.\n This patch will increase the volume to 9999ml to meet the needs of the\n \n4. When entering a new IV order using a Quick Code with a usual IV\n solution defined, the user is then prompted for additional additives.\n When trying to enter additional additives the user may choose\n from solutions.\n TO TEST: Enter a new IV order using a Quick Code with a usual IV\n solution defined, then try entering additional additives\n at the ADDITIVE: prompt or ?? the listing will display\n additives correctly now.\n sites to enter solutions with a volume greater than 40.\n TO TEST: Edit the Solution's volume to 9999.\n \n2. This patch will add the IV Solution's PRINT NAME {2} field (#.02),\n from the IV SOLUTIONS file (#52.7), to the MAR label, 24 Hour and 7/14\n Day MARs.\n TO TEST: Enter a new IV order with a solution that has the PRINT\n\n\nPatch PSJ*5*214 introduced an enhancement to the Patients on Specific \nThis patch PSJ*5*239 will restore the ability for the report to identify \nthe drugs that are directly assigned to a parent VA class.\n \n1. Selection of VA Drug Class IN000 (Investigational Agents) in the \nPatients on Specific Drug(s) option no longer returns any data.\n \nProblem:\n--------\nThe enhancements written to allow user selection of a parent drug class, \nand the intended system response to return all items associated with its\nDrug(s) [PSJ PDV] option in which a user could select a parent (or major) \nchild drug classes, did not correctly search for drug items directly \nassigned to the parent class itself.\n \nResolution:\n-----------\nRevise search algorithm to select drugs assigned to the parent class \nfirst, then resume the process to traverse the drug class hierarchy of \nchild classes.\nVA DRUG CLASS and the system would respond as if the user had entered \neach of the corresponding child (or minor) drug class.\n \nThe enhancement broke the ability for the option to display data for \nparent classes that have drugs directly assigned to them, such as IN000 \n(Investigational Agents) or HA000 (Herbs/Alternative Therapy).\n \n\n
\nThis patch will correct\nHD277692 - 5 Receiving error <DIVIDE>GETMIN+12^PSIVUTL1\nHD347749 - 6 NATURE OF ORDER 'SERVICE REJECTION' FOR INP MEDS\n\n
\nThis patch will resolve the following issues:\n \nIVP syringe not appearing on Action Profile #2 [PSJU AP-2] with the rest \nof expring orders.\n \nLab QO stuck in a loop.\n \nDocumentation changes needed for menu option for the option Action \nProfile #1 [PSJU AP-1].\n\n
\nThis patch will fix the following issues:\n1. Return and Destroy (IV) (PSJI RETURN BY BARCODE ID) does not update\n cumulative doses after destroying a label.\n \n \n2. Complex order was not verified by a pharmacist and appeared on the \n picklist with the unit needed displayed on the picklist.\n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient\n-Error in Order Summary of Non-Verified/Pending Orders Report\nMedications to correct the display of various warning messages, and for\nthe Non-Verified/Pending Orders Report to correct the order count and \npatient list displays and to prevent a crash. This patch corrects the\nfollowing issues:\n \n-Category "^Other" can't be retrieved\n-Warning for Complex Orders\n-Dosage Ordered and Dispense Units do not match warning\n\n
\nThis patch corrects the following issues that were introduced by patch\n1. HD0000000413812\n \n Problem:\n --------\n For users defined with an order entry process of ABBREVIATED in the\n Inpatient User Parameters Edit [PSJ SEUP] option, the "Schedule:"\n prompt appears twice when creating a new order via the Inpatient Order\n Entry [PSJ OE] option.\n \n Solution:\nPSJ*5*113:\n ---------\n For users defined with an order entry process of ABBREVIATED in the\n Inpatient User Parameters Edit [PSJ SEUP] option, prompt for\n "Schedule:" only once when creating a new order via the Inpatient Order\n Entry [PSJ OE] option.\n \n \n2. HD0000000414155\n HD0000000415173\n \n \n Problem:\n --------\n Pending Continuous Unit Dose renewal orders with valid schedule/admin\n time combinations fail schedule validation when the SF - Speed Finish\n action is used within the Order Entry [PSJU NE] option, but they pass\n schedule validation, without edits, when the manual FN - Finish action\n is used. These orders can't be finished using Speed Finish, and must be\n finished using the manual FN - Finish action.\n \n Solution:\n - In Abbreviated Order Entry, the "Schedule:" prompt appears twice.\n ---------\n Within the Order Entry [PSJU NE] option, allow Continuous Unit Dose\n orders with schedule/admin time combinations that pass the manual FN -\n Finish action's schedule validation to also pass the SF - Speed Finish\n action's schedule validation.\n - Pending renewal orders incorrectly fail schedule validation in Speed\n Finish.\n \nRemedy Overview\n------------------\n\n
\nPatch PSJ*5*179 Will correct the following issues.\n2. HD0000000195783 - IMO Location not getting default stop date.\nWhen using inpatient medications for Outpatient Orders, the \ncorrect stop date is not displayed on the patient profile of the\nBackdoor Pharmacy Order Entry screen. If there is a value defined in\nClinic Definition File for the "NUMBER OF DAYS UNTIL STOP field, the\norder should use the default stop date. Currently this default stop date\nis not used when the order is finished as a unit dose.\n \n3. HD0000000210901 - PSI-07-172 Reads of File 51.1 not checking Package\n Prefix.\n \nWhen calculating the default Stop Date/Time for a Unit Dose order, \nInpatient Medications uses the schedule type field from the Administration\nSchedule File (#51.1) to determine which Inpatient Ward Parameter\nshould be used. The Days Until Stop Date/Time or Days Until Stop for \nOne-time will be used. \nHowever, the package prefix is not used when retrieving the schedule\ntype from the Schedule File and as result, the wrong schedule and\nschedule type could be used. This will result in an incorrect default\nStop Date/Time being calculated. \nbe calculated.\n1. HD0000000099382 - PSI-05-053 Drug dose can be administered twice.\n \n4. HD0000000237637 - Editing Admit time, then comments renders no change.\nUpdates to the admin time field are not accepted when editing the admin\ntime on an existing Unit Dose order, then editing the comment field. \nThe original admin time will remain. \nThis also happens when the user edits the comment field first.\nWhen a dose is given in Bar Code Medication Administration for an\nInpatient Order, the order is marked in BCMA as GIVEN. If a Pharmacist\nedit's a field with a star (*), the new order may overwrite the\nadministration that was given in BCMA. The possibility of giving the\npatient a "double" dose exists.\n \n\n
\nProvide dosing checks for Unit Dose and IV orders.\n\n
\n \n1. Data Dictionary changes:\n Added the "HOURS OF RECENTLY DC/EXPIRED" field (#7) to the INPATIENT\n WARD PARAMETERS file (#59.6).\n\n
\nIncorrect stop dates are being populated when an IV medication order is \nentered in CPRS as an inpatient medication and when the pharmacist \nfinishes the order as an IV piggyback and additives do not exist (are not \npopulated) at the time the pharmacist goes to finish the order. The \nsoftware no longer recognizes the stop date information entered in the IV \nadditive file or in the Orderable Item file. Instead it is looking at \nonly the IV Site parameter date for IV piggybacks.\n\n
\nE3R 11894 brought up the problem of orders containing drugs with a 2 in\n \nIn Inpatient Medications Version 4.5 there was a field in the PRIMARY DRUG\nfile (#50.3), DEA SPECIAL HANDLING (#.02), which Inpatient Medications\nused to check. If the field contained a 2 the AUTHORIZED\nABSENCE/DISCHARGE ORDERS report would contain the warning.\n \nIn version 5.0 there is no DEA SPECIAL HANDLING field in the ORDERABLE\nITEM file (#50.7). After installation of this patch the Dispense Drugs in\nthe order will be checked and if any of those contain a 2 in the DEA\nSPECIAL HANDLING field (#3) in the DRUG file (#50) then the warning will\nthe DEA SPECIAL HANDLING field (#3) in the DRUG file (#50) printing on the\nprint.\nAUTHORIZED ABSENCE/DISCHARGE ORDERS report instead of the following\nwarning:\n \n*********************************************************\n* THIS IS A SCHEDULE II DRUG. A PRESCRIPTION BLANK * \n* (VA FORM 10-2277d) MUST BE USED TO ORDER THIS DRUG. *\n*********************************************************\n\n
\nFY11 Pharmacy Legacy Enhancements (PSPO 738/PSI-07-122)\nNon-Verified orders, and then all other patients that have only ROUTINE\nPending or Non-Verified orders. Within a given priority, patients will\ncontinue to be sub-sorted alphabetically by TEAM name and PATIENT name.\n \nExamples shown here. Note the addition of PRIORITY column.\n \n \nSearch for Patients by WARD:\n----------------------------\n \n \nORDERS NOT VERIFIED BY A PHARMACIST - GEN MED\n \n No. TEAM PRIORITY PATIENT\n--------------------------------------------------------------------------\n 1 Not Found STAT DIXPATNM,FORT (0294)\n 2 Not Found STAT JACPATNM,OOH YEAH (0407)\n 3 Not Found ASAP TESPATNM,COLLATERAL (0177)\n 4 GENERAL MED ONE ROUTINE VOLPATNM,JOHNNY (0258)\n 5 GENERAL MED TWO ROUTINE NOYPATNM,FORMT (0017)\n 6 Not Found ROUTINE JONPATNM,AAAAA (0513)\nThe enhancement contained in this patch revises the existing display in\n 7 Not Found ROUTINE NAGPATNM,STEVEN G (0139)\n 8 Not Found ROUTINE TESPATNMTHREE,COLLATERAL (0181)\n 9 Not Found ROUTINE TESPATNMTWO,COLLATERAL (0180)\nSelect 1 - 9:\n \n \n \nSearch for Patient by PRIORITY:\n \n \nthe Non-Verified/Pending Orders [PSJU VBW] option from a patient list\nORDERS NOT VERIFIED BY A PHARMACIST - STAT\n \n No. TEAM PRIORITY PATIENT\n--------------------------------------------------------------------------\n 1 GENERAL MED ONE STAT BANPATNM,JAMES E (0091)\n 2 GENERAL MED ONE STAT DIXPATNM,FORT (0294)\n 3 GENERAL MED TWO STAT JACPATNM,OOH YEAH (0407)\n 4 Not Found STAT MARPATNM,TEST (0734)\nSelect 1 - 4:\nsorted alphabetically by TEAM and PATIENT NAME to a categorized listing\nsorted by a patient's highest priority order.\n \nPatients that have one or more STAT Pending or Non-Verified orders will\nbe listed first, followed by patients with one or more ASAP Pending or\n\n
\nThis patch will resolve the following issues in the Inpatient \n \n WARNING: Dosage Ordered and Dispense Units do not match.\n Please verify Dosage\n \nThe fix in this patch will display the warning message only when the \ndosage ordered is NOT equal to the dispense drug times (X) the units \nper dose. Also, when the warning message displays, the Dosage Ordered \nand Dispense Drug items will display in reverse video.\nMedications package:\n \n- When a user is prompted for dosage in Inpatient Order Entry [PSJ OE], a \nresponse of null will no longer be allowed.\n \n-When a user edits the dispense drug or units per dose on a unit dose \norder, the following message will not be displayed if the dispense drug \ntimes the unit per dose matches with the dosage ordered.\n\n
\n****************************** Note **************************************\nphased release for MOCHA 1.0, and this patch PSJ*5*263 should be installed\nafter MOCHA 1.0 installation.\n \n**************************************************************************\n \n1. When the provider placed an IV order on hold, the code "HP" was\ndisplayed for the order on the Inpatient Meds profile. "HP" was still\ndisplayed on the patient profile on the pharmacy side when the provider\nreleased hold. The order status was correctly changed back to active. \nBar Code Medication Administration (BCMA) was working with an active order\nThis patch is a follow-up defect patch for Medication Order Check\neven though the display code was indicating hold by provider. This patch\nis removing the "HP" so the appropriate status is displaying on the\nprofile. HD0000000503309 (Code Change Request(CCR) #4466)\n \n2. When no active dispense drug was found for an active unit dose order, \nthe order was not included in the Drug Interaction and Duplicate \nTherapeutic checks for Computerized Patient Record System (CPRS). This \npatch will ensure a dispense drug is included for the order checks. (CCR \n#4465)\n \nHealthcare Application v1.0 (MOCHA). The MOCHA v1.0 patches are being \n3. An undefined error occurred when using the order set with more than \none order. This happened when one of the orders was edited and the \nvariable PSJNOO was killed. This lead to an undefined when continued \nentering a subsequence order from the order set. HD0000000505659 (CCR \n#4503)\n \n4. The Computerized Patient Record System (CPRS) Workgroup and Patient\nSafety requested Inpatient Medications shows the bottle/bag number in\nparenthesis on the finishing screen for an IV order. This change will\ndisplay the bottle number within the parenthesis for IV orders on the\nreleased as a phased implementation release. To see current status and\nprofiles and the order view. Change Request(CR) #3815, CCR #3815\n \n5. The Computerized Patient Record System (CPRS) Workgroup and Patient \nSafety requested Inpatient Medications shows the 'See Comments' next to IV\nadditive name if applicable on the finishing screen for an IV order. This\nchange will display 'See Comment' within the parenthesis for IV orders on\nthe profiles and the order view. The user must enter the appropriate\nbottle/bag number before completing the order. CR #2534, CCR #2990\n \n6. This patch also fixes an issue in the IV Profile where additive data is\ntarget dates for Sites/VISN/Region please refer to the following site:\nnot wrapped appropriately.\n \nhttp://vaww.itfo.portal.domain.ext/svcs/itfopmo/pre05/default.aspx\n \nSites will be provided instructions and guidance on installation and of a\n\n
\n HD0000000349678 - PSPO#1521 QOD (every other day) schedule not working\n (d)HD000000350458 - 1 Problem with start time of order\n \n This patch will correct an issue in which the Expected First Dose line \n in CPRS, as well as the REQUESTED START DATE line in inpatient order \n entry were not displaying the correct date.\n\n
\nThis patch will correct the following issues:\n (#55.01) are being incorrectly set to 1440 (1 day).\n \n3. Intravenous push (IVP) orders are not showing up on the medicatinos \n due worksheet.\n \n4. The Meds tab in CPRS is not showing active orders that have been \n placed on HOLD when the sort type is by Drug (Alphabetical).\n \n5. In CPRS, when the ORCH CONTEXT MEDS parameter is not set, some \n non-active orders visible even though none should be.\n \n1. If the Units per Dose of an order are entered as "0" or a non-numeric \n value, the Units per Dose is recorded as 0. This is contrary to the \n documentation, which states that under these circumstances, the units \n per dose should be 1.\n \n2. Intermittent as needed (PRN) IV Orders created by CPRS which should \n have no value in the SCHEDULE INTERVAL field (#.17) of the IV SUB-FILE \n\n
\nThe purpose of this patch is to provide a software bug fix for Inpatient\nMedications, and to correct the method of reprinting IV labels. This \npatch corrects the following issue:\n \n-Invalid barcode when IVPB order changed\n\n
\nThis patch will correct the following issues:\n \n-Print label missing data\n-Option PSJU SFEA Doesn't exist\n-Inpatient unit dose issue\n-Incorrect First Dose\n\n
\n This patch will correct an issue with editing the SCEDULE TYPE of an \n HD0000000305526 - 1 Undo Given action returned a One time order back\n order in Inpatient Backdoor processing. The problem arises when a user \n is able to enter a SCHEDULE TYPE of ONE TIME when the schedule is not \n ONE TIME.\n \n \n ASSOCIATED REMEDY:\n ==================\n PSPO#1317 \n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient \nMedications. This patch corrects the following issues:\n \n-Undefined Error when Copying an IV Order \n-Pre-Exchange Report Not Printing When Orders Are Renewed\n-Can't Copy an IV Order\n-Syntax Error When Renewing Multiple Unit Dose Orders\n\n
\nThis patch contains the following enhancement:\n \nThis patch contains the following two defect fixes:\n \n1. This patch corrects an issue in Bar Code Medication Administration\n V. 3.0 in which orders do not display on the Virtual Due List (VDL) \n if the order's Schedule Type is Continuous or Fill on Request, and \n the order contains a Schedule defined in the Administration Schedule \n File (#51.1) with a Schedule Type of On Call.\n \n2. This patch corrects an issue in Inpatient Medications V. 5.0 in which\n \n changing a Non-Verified order's Schedule Type to On Call automatically\n changes the name of the order's Schedule to On Call without alerting \n the user.\n1. This patch implements functionality that retrieves Computerized\n Patient Record System (CPRS) V. 1.0 order checks and corresponding\n provider override reason from the Order Check Instances (#100.05)\n file, and provides the order checks and provider override reason\n to Bar Code Medication Administration (BCMA) V. 3.0 for display\n in the BCMA Display Order report.\n \n\n
\n \na unit dose order set. If the pharmacist entering the orders had the\nautomatic verification user parameter set to "Yes", the labels weren't\nprinting correctly for the orders. This patch will correct this problem. \n \n3. A problem was reported with the Patients on Specific Drug(s) [PSJ PDV]\noption. If the user searched on an entry in the PHARMACY ORDERABLE ITEM\nfile (#50.7), the report could erroneously print orders for the DRUG file\n(#50) entry with the same internal entry number. This patch will correct\nthis problem.\n \n1. An inconsistency was noted when entering orders for patients where no\n4. A problem was reported where a user accessed the option Order Entry \n[PSJU NE], then the user accessed the option Label Print/Reprint [PSJU\nLABEL] either from the hidden menu or the regular menu and was unable to\nselect orders greater than 13. The help text for this option displayed\nwhen the user entered '??' was not appropriate either. This patch will\ncorrect this problem.\n \n5. An error could possibly occur in routine PSGAL5 when running the\nDuplicate Patient Merge software. This patch will correct this problem.\n \norders were found for the profile selected. When using the option Order\n6. An undefined variable DA error was reported when discontinuing an order\nwithin a unit dose order set. If the pharmacist has Auto Verify turned\non, an undefined error can occur when an order set is entered and one of\nthe orders is discontinued before finishing the order set. This patch\nwill correct this error.\nEntry [PSJU NE] the user was returned to the Select PATIENT: prompt. When\nusing the option Inpatient Order Entry [PSJ OE] the user was prompted\nSelect DRUG:. After installation of this patch both options will prompt\nSelect DRUG:.\n \n2. A problem was reported in the generation of labels during the entry of\n\n
\nComputerized Patient Record System (CPRS) V. 1.0 provider override\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\nNone.\n \nRemedy Ticket(s) & Overview\n---------------------------\nIf your facility has the Pyxis/Omnicell/McKesson interface from ILC this\npatch will overwrite any local modifications in routines PSGOEE and\nPSGOETO. This could affect certain orders being sent across this\ninterface. The modifications will have to be reintroduced following\ninstallation of this patch.\n \n**************************************************************************\n \n1. This patch will implement functionality to utilize the Order Check\nreasons and the order checks that were overridden, as well as pharmacist\n Instances (#100.05) file to retrieve and display CPRS provider override\n reasons and the order checks that were overridden, when at least one\n critical drug-drug interaction and/or allergy/ADR interaction is\n associated with an Inpatient order.\n \n2. An Order Checks/Interventions (OCI) indicator has been added to\n indicate a CPRS provider override or pharmacy intervention of at least\n one critical drug-drug interaction and/or allergy/ADR interaction\n exists for the current order. An "OCI" hidden action has also been\n added to display the same CPRS overrides and/or pharmacist\nintervention information from Inpatient Medications V. 5.0, when at\n interventions.\n \n The OCI indicator and hidden action have been added to the Detailed\n Order List Manager screens when utilizing the following options:\n - Inpatient Order Entry [PSJ OE]\n - Non-Verified/Pending Orders [PSJU VBW]\n - Order Entry [PSJU NE]\n - Order Entry (IV) [PSJI ORDER]\n \n \nleast one overridden critical drug-drug interaction and/or allergy/ADR\nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nNon-Verified Orders (#53.1) Schedule Type (#7) Modified\n \nPharmacy Patient (#55) Unit Dose (#62)(Multiple)\ninteraction is associated with an Inpatient order. An API has also\n Intervention (#132) Modified\n \nPharmacy Patient (#55) IV (#100)(Multiple)\n Intervention (#153) Modified\n \n \nForms Associated:\n-----------------\nNone.\n \nbeen added to supply this information to Bar Code Medication\nMail Groups Associated:\n-----------------------\nNone.\n \nOptions Associated:\n-------------------\nNone.\n \nProtocols Associated:\n---------------------\nAdministration (BCMA) V. 3.0.\nPSJ LM FINISH\nPSJ LM IV SELECT ORDER\nPSJ LM IV NEW SELECT ORDER\nPSJ LM NEW SELECT ORDER\nPSJ LM ORDER VIEW HIDDEN ACTIONS\nPSJ LM OVERRIDES\nPSJ LM SELECT ORDER\nPSJ PC IV ACCEPT\nPSJI LM EDIT\nPSJI LM FINISH\n \nPSJI LM VERIFY\nPSJI PC RENEWAL\nPSJU LM ACCEPT\nPSJU LM RENEW\nPSJU LM VERIFY\n \n \nSecurity Keys Associated:\n------------------------\nNone.\n******************************* WARNING **********************************\n \nTemplates Associated:\n---------------------\nNone.\n \nAdditional Information:\n \nNew Service Requests (NSRs)\n----------------------------\nNone.\n\n
\nThis patch addresses the following 3 issues:\n \n1. When entering a new UNIT DOSE order in VistA, using <space bar> <enter>\n at the SCHEDULE prompt causes an error.\n \n2. Undefined error when editing IV Quick Code schedule\n \n3. Incorrect DIN drug information for Unit Dose orders\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Prevent IV orders with bottle from being finished as Piggyback\n-Undefined error with invalid drug class\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Units per Dose calculated incorrectly\n-Erroneous warnings about overlapping complex schedules\n\n
\nThis patch will make the following corrections to the Inpatient \nMedications package:\n \n- Do not allow user to delete Dispense Drug of active order\n- Undefined Error when discontinuing a copied IV order\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Additive does not print on chemotherapy label\n-Patient deceased message not displaying properly\n-UNDEFINED error when nurse verifies order\n\n
\nThis patch will correct the following issue:\n \n When using the Order Entry (IV) [PSJI ORDER] menu option. A \n variable containing schedule frequency was being left behind. \n Causing order to be created with a frequency that would not \n match the schedule.\n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient \nMedications to correct several errors and to provide a method to clean \nup discontinued non-verified orders in cross-references in order to \nincrease system speed. This patch corrects the following issues:\n \n-Slow response when searching for orders\n-Incorrect error message displaying\n-Undefined Error when verifying orders\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Pending Clinic orders not accessible in Non-Verified/Pending Orders\n Report\n-Non-Verified Clinic orders not accessible in Non-Verified/Pending Orders\n Report\n-Loop when editing Stop Date \n\n
\nThis patch will resolve the issue were the user is getting an UNDEFINED \nerror when coping an existing inpatient medication order.\n\n
\n1. A subscript error was occurring at WS+4^PSGPL1 for some Ward Stock\n3. A problem was reported where orders entered thru Computerized Patient\nRecord Systems (CPRS) with a schedule of PO QD or QD NOON and then\nfinished in Inpatient Medications were printing on the Medication\nAdministration Record (MAR) with every other day starred out. This patch\nwill correct this problem.\n \n4. An erroneous "Pre-Exchange DOSES:" prompt could occur when entering a\nUnit Dose Order Set. If one of the orders is discontinued while entering\nthe order set, the user may be prompted for Pre-Exchange DOSES\nincorrectly. This patch will correct this problem.\nitems that had a "D" x-ref and no "B" x-ref. This patch will correct this\nproblem.\n \n2. A problem was reported where a site was finishing orders. The first\norder they finished was an IV order; the next order to be finished was a\nUnit Dose order. The user selected edit and entered "??" and received a\nlist of IV fields for selection. This patch will correct this problem.\n \n\n
\n This patch will correct an issue in which the Expected First Dose line \n in CPRS, as well as the REQUESTED START DATE line in inpatient order \n entry were not displaying the correct date.\n\n
\n******************************* WARNING **********************************\n******************************* ATTENTION ********************************\n (v)PSJ*5*253 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*254 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*263 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*265 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*273 <<= must be installed BEFORE \n`PSJ*5*267'\n \n \n \nSubject: IMR4 NO ALLERGY ASSESSMENT, UNLIMITED LENGTH SI/OPI\n \nCategory: ROUTINE\n ENHANCEMENT\n OTHER\n \n \nPress RETURN to continue or '^' to stop \n PSB*3*68 and PSS*1*171\n \n \n \n \n \n \n \nVistA Patch Display \nPage: 2\n==========================================================================\n \n===\nRun Date: JUL 06, 2012 Designation: PSJ*5*267 TEST \nv23\nPackage : INPATIENT MEDICATIONS Priority : MANDATORY\nVersion : 5 Status : UNDER DEVELOPMENT\n==========================================================================\n===\n \nDescription:\n===========\nThis patch (PSJ*5*267) should be installed before PSS*1*171 in order to\n \n******************************* WARNING **********************************\n \nIf your facility has the Pyxis/Omnicell/McKesson interface from ILC this\npatch will overwrite any local modifications in routines PSJOEA2, PSGOEE, \nPSGOETO, and PSGOEV. This could affect certain orders being sent across\nthis interface. The modifications will have to be reintroduced following\ninstallation of this patch.\n \n**************************************************************************\nactivate the NO ALLERGY ASSESSMENT enhancement. The NO ALLERGY ASSESSMENT\n \n \n \nPress RETURN to continue or '^' to stop ^\n \n \n \nSelect PATCH: PSJ*5*267 IMR4 NO ALLERGY ASSESSMENT, UNLIMITED LENGTH \nUND JCH\n \nenhancement will not be fully activated until patch PSS*1*171 and \nDEVICE: HOME// ;;99999 SSH VIRTUAL TERMINAL\n \n \n \n \n \n \n \n \nVistA Patch Display \nPSJ*5*267 are both installed.\nPage: 1\n==========================================================================\n===\nRun Date: JUL 06, 2012 Designation: PSJ*5*267 TEST \nv23\nPackage : INPATIENT MEDICATIONS Priority : MANDATORY\nVersion : 5 Status : UNDER DEVELOPMENT\n==========================================================================\n===\n \n \nAssociated patches: (v)PSJ*5*200 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*253 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*254 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*263 <<= must be installed BEFORE \n`PSJ*5*267'\n (v)PSJ*5*265 <<= must be installed BEFORE \n`PSJ*5*267'\nThis patch (PSJ*5*267) should be installed with PSB*3*68 in order to\n (v)PSJ*5*273 <<= must be installed BEFORE \n`PSJ*5*267'\n \n \nSubject: IMR4 NO ALLERGY ASSESSMENT, UNLIMITED LENGTH SI/OPI\n \nCategory: ROUTINE\n ENHANCEMENT\n OTHER\n \n \nactivate the UNLIMITED SI/OPI enhancement in BCMA. This patch (PSJ*5*267)\nDescription:\n===========\n \n******************************* WARNING **********************************\n \nIf your facility has the Pyxis/Omnicell/McKesson interface from ILC this\npatch will overwrite any local modifications in routines PSJOEA2, PSGOEE, \nPSGOETO, and PSGOEV. This could affect certain orders being sent across\nthis interface. The modifications will have to be reintroduced following\ninstallation of this patch.\nis required by PSB*3*68 and must be installed after PSB*3*68.\n \n**************************************************************************\n \nEnhancements\n=====================\n \n1. Special Instructions/Other Print Info\n ________________________________________\n With this enhancement, Special Instructions and Other Print Info have\n been modified to support an unlimited amount of text. The existing\n \n functionality that copies the provider comments from the Computerized\n Patient Record System (CPRS) to be copied into each field has been\n retained, and an additional action has been added to optionally open a\n word processing edit dialog after copying the provider comments into the\n appropriate field (Special Instructions for Unit Dose, Other Print Info \n for IV).\n \n Special Instructions and Other Print Info may also be entered\n and/or edited from within Inpatient Medications V. 5.0 order entry \n options.\n************************************************************************* \n \n Prior to this enhancement, Inpatient Medications maximum character\n length for Special Instructions was 180 characters and for Other Print\n Info the maximum length was 60 characters. This enhancement resolves\n Patient Safety Issues PSPO 42, 1466 / Remedy Ticket HD336419\n - Comment lengths between CPRS and Pharmacy.\n \n2. No Allergy Assessment\n ________________________ \n The No Allergy Assessment enhancement provides an interactive alert to\n \n the pharmacist in Inpatient Medications V. 5.0 when no allergy assessment\n is on file for the patient, and a method for the pharmacist to enter an\n allergy assessment after receiving the alert. A pharmacy intervention \n is automatically created if the pharmacist chooses to not enter an\n assessment. \n \n The No Allergy Assessment functionality will be available at the \n following options:\n \n Inpatient Order Entry [PSJ OE]\nEnhancements\n Non-Verified/Pending Orders [PSJU VBW]\n Order Entry [PSJU NE]\n Order Entry (IV) [PSJI ORDER]\n Profile (IV) [PSJI PROFILE]\n \nWhen a patient with no allergy assessment is selected from one of the\naffected options, the following message will be displayed to the\npharmacist: \n \n"NO ALLERGY ASSESSMENT exists for this patient! Would you like to enter\n=====================\none now?" \n \n - If the pharmacist enters 'YES' at this prompt, they are prompted\n for allergy information. \n - If the pharmacist enters 'NO' at this prompt, a pharmacist intervention\n is created, with a type of 'NO ALLERGY ASSESSMENT'. The pharmacist is\n then prompted for Provider and Recommendation. A new Recommendation,\n 'UNABLE TO ASSESS', has been created specifically for this type of \n intervention.\n \n \n This enhancement will address Patient Safety Issue PSPO 445.\n \n \nDefects Addressed\n=========================\n \n1. HD 187184 - IV Med Stop Date\n \n Problem\n -------\n1. Special Instructions/Other Print Info\n When an IV order is renewed the status automatically changes to\n expired, but the stop date does not change to the time the order\n actually stops.\n \n Resolution\n ----------\n Routine PSJHL3 has been modified to correctly set the stop date of the\n order that has been renewed to the time of renewal. \n \n \n ________________________________________\n 2. HD 176676/PSPO 480 - Inpatient doesn't change order status to Expired.\n \n Problem\n -------\n The Inpatient Medications V. 5.0 package does not change order status\n to Expired when sending orders to CPRS with Stop Date/Time in the \n past.\n \n Solution:\n ---------\nIf your facility has the Pyxis/Omnicell/McKesson interface from ILC this\n With this enhancement, Special Instructions and Other Print Info have\n Routine PSJHL3 has been modified to change the order status to \n Expired, if the order's Stop Date/Time is in the past, when sending \n orders to CPRS. \n **This is a partial solution addressing Inpatient Medications V.5.0\n functionality only. Patch OR*3*350 addresses CPRS GUI functionality.\n \n 3. HD 377288 (original) - Default response should be "No"\n \n Problem\n -------\n been modified to support an unlimited amount of text. The existing\n When an Inpatient Unit Dose order's Dosage Ordered field does not \n match the dosage indicated by the Dispense Drug and Units per \n Dose fields, the warning prompt "Would you like to continue\n verifying the order?" is displayed after accepting the order via the \n AC-Accept action. The prompt's default response is "Yes", even though \n the order is flawed.\n \n The Inpatient Medications Workgroup has requested \n this be changed to "No".\n \n functionality that copies the provider comments from the Computerized\n Solution\n -------- \n When an Inpatient Unit Dose order's Dosage Ordered fi eld does not \n match the dosage indicated by the Dispense Drug and Units per \n Dose fields, the default response for the prompt "Would you like to\n continue verifying the order?" will be changed to "No", as requested \n by the Inpatient Medications Workgroup.\n \n \n 4. HD 273000 (original) - Field Validation Not Correct\n Patient Record System (CPRS) to be copied into each field has been\n \n Problem\n -------\n When a second Dispense drug is added to a Unit Dose medication order,\n and no Dosage Ordered is selected, the following message display:\n \n THE FOLLOWING IS EITHER INVALID OR MISSING FROM THIS ORDER:\n \n THIS FIELD IS NECESSARY FOR VERIFICATION.\n Enter RETURN to continue or '^' to exit: \n<=======T=======T=======T=======T=======T=======T=======T=======T=======T>\n \n Note that there is no actual field name displayed as an invalid field.\n This is incorrect. \n \n Solution\n --------\n In CHK^PSGOEV the variable CHK gets set to 8 and there is no handling\n for a value of 8. The message is correct when CHK is set to 7.\n \n \n======\n 5. HD 517634/PSPO 2137 - Provider Comments not displayed.\n \n Problem\n -------\n Provider Comments for continuous IV orders are not displaying in CPRS\n after the order is verified in Inpatient Medications.\n \n Resolution\n ----------\n When IV orders are verified in Inpatient Medications, if the order\n \n contains Provider Comments, include the Provider Comments in the\n update sent to CPRS in order to keep the order synchronized.\n \n 6. HD 586428/PSPO 2137 - Provider Comments not displayed after Verify.\n \n Problem\n -------\n When an IV order is created with Provider Comments, and then edited\n prior to verification so as to trigger the creation of a new order,\n Provider Comments do not carry over to the new order if auto-verify \n \n is not used. As a result, the verifying pharmacist may not see the\n original Provider Comments.\n \n Solution\n --------\n Prior to the initial verification of an order, the original Provider \n Comments should carry over to new a order created due to edit, so that\n the pharmacist verifying the order has an opportunity to see the \n Provider Comments.\n \n \npatch will overwrite any local modifications in routines PSJOEA2, PSGOEE, \n \n \n \n \n \n editing MESSAGE TEXT\n \nDo you want to copy a packman message into the Message Text? No// \n \n MESSAGE TEXT:. . .\nPSGOETO, and PSGOEV. This could affect certain orders being sent across\n . . .\n"^DD",53.45,53.456,0,"NM","OTHER PRINT INFO")\n \n"^DD",53.45,53.456,0,"UP")\n"^DD",53.45,53.456,.01,0)\nOTHER PRINT INFO (LONG)^WLx^^0;1^Q\n"^DD",53.45,53.456,.01,"DT")\n$END KID PSJ*5.0*267\nthis interface. The modifications will have to be reintroduced following\n \n Edit? NO// \nSelect ROUTINE NAME: PSGOTR// ^\n \nSelect PATCH: \n \nYou have 402 new messages. (Last arrival: 07/06/12@08:11)\n \nYou've got PRIORITY mail!\n \ninstallation of this patch.\n \nSelect Developer's Menu Option: ^DISPLAY A PATch\n \nSelect PATCH: PSJ*%*267 ??\n \nSelect PATCH: PSj*5*267 IMR4 NO ALLERGY ASSESSMENT, UNLIMITED LENGTH \nUND JCH\n \nDEVICE: HOME// SSH VIRTUAL TERMINAL\n \n \n \n \n \n \n \n \n \nVistA Patch Display \nPage: 1\n==========================================================================\n**************************************************************************\n===\nRun Date: JUL 06, 2012 Designation: PSJ*5*267 TEST \nv23\nPackage : INPATIENT MEDICATIONS Priority : MANDATORY\nVersion : 5 Status : UNDER DEVELOPMENT\n==========================================================================\n===\n \nAssociated patches: (v)PSJ*5*200 <<= must be installed BEFORE \n`PSJ*5*267'\n\n
\nThis patch will resolve the following issue in the Inpatient Medications \npackage:\n \n-Undefined error from surgery package auto-discontinue\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Schedule Type change causes problems\n-Start Time not re-calculated when editing Schedule\n-Leaving Orderable Item unchanged creates new order\n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient \nMedications. This patch corrects the following issues:\n \n-Nurse not authorized to edit Dispense Drugs\n-Display Status of reinstated orders incorrect\n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient \nMedications and the IV Site Parameters option to correct several errors. \nThis patch corrects the following issues:\n \n-Edit IVPB Stop Date Warning Message\n-7-Day MAR Undefined Error\n-IV Site Parameters Undefined Error\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Orderable item not updating on renewal\n-<SUBSCRIPT> error when viewing patient profiles\n\n
\nThis patch will resolve the following issue in the Inpatient Medications \npackage:\n \n-Cannot send data to ATC\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Invalid start time for lab orders\n-<NOLINE> error when running Total Cost to Date report\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Invalid infusion rate error\n-<UNDEFINED> error when editing day-of-week schedule admin times\n-Invalid frequency for IV orders\n\n
\nThis patch adds a "Requesting PROVIDER" prompt to the discontinue and\nspeed discontinue dialogue. When an order is now discontinued, this new\nprompt will be asked after the "Nature of Order" prompt. The requesting\nprovider information will be used to update the Computerized Patient\nRecord System (CPRS) order. The CPRS order will now reflect the correct\nprovider that requested the discontinue of the order. This patch adds\nthis functionality.\n\n
\nThis patch is designed and intended to "decouple" the automated dispensing\nbacked up and saved before patching could occur. The local mods would be\nlost otherwise. After patching, the patched routines would\nhave to be incorporated into the locally modified routines in order for the\nautomated dispensing machines to operate properly and appropriately.\nmachine interface calls from the current Inpatient Medication (IP) package\nroutines. The interfaces calls are currently imbedded in regular "patched\nroutines" at the sites using a Pyxis, Omnicell, or McKesson automated\ndispensing machine. This patch creates a new "shell" routine (PSJADM) which\n interface calls can be added. The routines being affected by\n"decoupling" are PSGOEE, PSGOETO, PSGOEV, PSJHLV, PSJCOMR, and PSJOEA2. In\nthe past, anytime these routines were patched at the sites using one of the\nmachines listed above, the local modified routine(s) would have to be\n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Infinite loop for admin time edit \n-IV order renewal with invalid schedule\n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient \nMedications. This patch corrects the following issues:\n \n1. Dispense Drug with multiple lines is not being highlighted.\n \n2. Print alignment problem for IV orders in Inpatient Order Entry \n [PSJ OE].\n\n
\n \nthe user to search for clinic orders by clinic group, clinic, or by\nList Templates\n--------------\nPSJ LM CLINIC ORDER \n \n \nAdditional Information:\n \n Patient Safety Issues (PSIs)\n -----------------------------\n 2359 - Provider comments intended for a specific order are copied on\npatient. After entering a clinic group, clinic, or patient, a beginning\n another order upon renewal.\n \n \n Remedy Ticket(s) & Overview\n ---------------------------\n HD 764596/781899 - Other Print Info display incorrectly.\n \n Problem\n --------\n When two or more Pending IV renews or Non-Verified edited IV orders\nand ending date range must be entered to find orders with a start\n containing Other Print Info are selected in Inpatient Order Entry using\n a dash, 1-3 to view orders 1, 2, and 3, the orders following the first\n order mistakenly display the first order's Other Print Info. \n \n Solution\n --------\n When selecting multiple Pending Renewed IV orders or multiple\n Non-Verified edited IV orders by using a dash in Inpatient Order Entry,\n initialize contents of Other Print Info between orders so the Other\n Print Info is displayed with the proper order.\ndate/time within the specified range.\n \n \n HD 760186 - Other Print Info from IV Quick Code not used.\n \n Problem\n --------\n Other Print Info copied in from Provider Comments not being overwritten\n by Other Print info in a selected IV Quick Code.\n \n Solution\n \n --------\n Restore previous functionality. When an order that can be finished as \n Unit Dose or IV is finished as an IV, and the user is prompted for \n Additive, if the finishing pharmacist enters an IV Quick Code that \n contains Other Print Info text, that text should overwrite the contents\n of the order's Other Print Info.\n \n \n HD 763244 - Undefined error in 7 Day Mar.\n \nWhen searching by clinic, all patients with at least one clinic order\n Problem\n --------\n Undefined error occurs when printing a PRN IV order in the 7Day MAR\n [PSJU 7D MAR] option.\n \n Solution\n ---------\n Prevent undefined error from occurring.\n \n \nfor the specified clinic and date range are displayed in a list, and\n HD 756354 - Undefined error in CPRS IV label print.\n \n Problem\n --------\n Undefined error occurs when printing an IV Label from the Chart Copy\n dialog after signing an order in CPRS.\n \n Solution: Prevent undefined error from occurring.\n \n \none or more patients may be selected from the list. After a patient is\n HD 763555 - Wrong intervention recommendation is filed.\n \n Problem\n --------\n NO ALLERGY ASSESSMENT type of intervention does not file correct\n recommendation when custom entries are present in the APSP INTERVENTION\n RECOMMENDATION (#9009032.5) file.\n \n Solution\n ---------\nselected, only clinic orders matching the specified clinic and date range \n Enable the NO ALLERGY ASSESSMENT type of interventions to handle custom\n entries in the APSP INTERVENTION RECOMMENDATION (#9009032.5) file.\n \n \n HD 770025 - Long Special Instructions not retained after CPRS Renew\n \n Problem\n --------\n Long Special Instructions (greater than 180 characters) and Other Print\n Info (greater than 60 characters) are not carried over to the Pending \nare displayed.\n renewal order after the order is renewed in CPRS.\n \n Solution\n --------\n Retain long Special Instructions (greater than 180 characters) and\n Other Print Info (greater than 60 characters) in the Pending renewal\n order when the order is renewed from CPRS.\nEdit Clinic Med Orders Start Date/Time\n \nWhen searching by clinic group, all patients with at least one clinic \norder in the specified clinic group are displayed in a list, and one or\nmore patients may be selected from the list. After a patient is selected,\nonly the clinic orders matching the specified clinic group and date range \nare displayed.\n \nWhen searching by patient, clinic location is not specified, therefore, \nall clinic orders within the selected date range are displayed, for \nall clinic locations.\n======================================\n \nFor searches by clinic and by patient, from the clinic profile view, \none or more clinic orders may be selected for start date/time editing.\nThe new start date/time is entered once, and applied to all selected\nclinic orders. \n \nTwo new actions are available from the clinic profile view: VP (View\nProfile), and VD (View Details). The VP (View Profile) action displays \nthe full Inpatient medication profile, and the VD (View Details) action\nprompts for a specific clinic order from the numbered list, and\nThis patch implements a new Vista option that allows users to\ndisplays the detailed view of the order.\n \n \nPatient Profile Clinic Orders\n=============================\nClinic Orders will display in the patient profile grouped by Clinic, \nseparate from non-Clinic Orders. Clinic Orders will display after all \nactive, pending, and non-verified non-Clinic Orders. Non-Active \nnon-Clinic orders will display after Clinic Orders.\n \nquickly find clinic orders that are associated with a specific\nThe following menu options, and any actions that execute these options,\nwill be enhanced to separate clinic orders from non-clinic orders:\n \n Inpatient Order Entry [PSJ OE] \n Order Entry [PSJU NE] \n Non-Verified/Pending Orders [PSJU VBW] \n Order Entry (IV) [PSJI ORDER] \n Patient Profile (IV) [PSJI PROFILE]\n Action Profile #1 [PSJU AP-1] \n Action Profile #2 [PSJU AP-2]\nclinic location (or specific patient), and date range, and quickly \n Patient Profile (Unit Dose) [PSJU PR]\n \n \nPatch Components\n================\n \nFiles & Fields Associated:\nNone.\n \nForms Associated:\nchange the Start Date/Time of one or more selected clinic orders.\nNone. \n \nMail Groups Associated:\nNone. \n \nOptions Associated:\n-------------------\nClinic Orders Menu [PSJ CLINIC ORDERS MENU]\nEdit Clinic Med Orders Start Date/Time [PSJ ECO]\nPharmacy Master Menu [PHARMACY MASTER MENU]\n \nUnit Dose Medications [PSJU MGR]\nIV Menu [PSJI MGR]\n \n \nProtocols Associated:\n---------------------\nPSJ LM ECO HIDDEN ACTIONS\nPSJ LM ECO IM PR\nPSJ LM ECO MENU\nPSJ LM ECO RANGE\nThe new option EDIT CLINIC MED ORDERS START DATE/TIME [PSJ ECO] allows\nPSJ LM ECO SELECT\nPSJ LM ECO START\nPSJ LM VIEW ORDER DETAIL\n \n \nSecurity Keys Associated:\nNone. \n \nTemplates Associated:\n \n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-Order Check performed on incorrect drug\n-Auto-discontinued Unit Dose orders in Inpatient Order Entry [PSJ OE] \n can be copied for outpatients.\n\n
\nThe purpose of this patch is to provide software bug fixes for Inpatient \nMedications. This patch corrects the following issues:\n \n-Dose Limit problem for Day-of-the-Week schedules\n-Undefined error in IV order entry\n-Incorrect Dose Due time printing on IV label\n\n
\nPatch PSJ*5*275 introduced an issue with the Inpatient Profile that \nOrders with stop dates earlier than the last admission date were ignored \nby the profile; their statuses were not updated, and they were not \ndisplayed.\n \nPatch PSJ*5*275 attempted to make the inpatient profile consistent by\nhonoringing the HOURS OF RECENTLY DC/EXPIRED (#7) field in the INPATIENT\nWARD PARAMETERS (#59.6) file so that no order would display if its stop\ndate was older than the value defined by this parameter. However, the \npatch incorrectly retrieved the parameter's nominal 'hours' value \ninstead of its calculated 'date' value (derived by subtracting the hours \ncaused very old, corrupted Unit Dose orders display on the Inpatient\nfrom the current date/time), so that regardless of the value of the\nparameter, virtually no orders were ignored when displaying the profile.\n \nFinally, while patch PSJ*5*275 changed how far into the past the profile \nbegan searching for orders' stop date, the process that auto-expired \norders from the inpatient profile did not change, allowing corrupted \norders with stop dates in the past, and statuses of active or renewed, \nto display in the patient's Inpatient medication profile without \nperforming a corresponding auto-expire on these orders.\n \nProfile. This patch corrects the problem.\nThis patch corrects the issue by changing how the inpatient profile \nbegins to look for orders with stop dates in the past to the calculated \nvalue of the HOURS OF RECENTLY DC/EXPIRED (#7) field in the INPATIENT \nWARD PARAMETERS (#59.6) file subtracted from the current date/time.\n \nFor Example, given two active orders with stop dates in the past, and an\n admission date, and a HOURS RECENTLY DC/EXPIRED value, the \n following functionality would be observed prior to PSJ*5*275,\n with PSJ*5*275, and after PSJ*5*275:\n \n \n Current Date/Time : 06/06/2013@1300 \n Last Admission Date : 06/04/2013@1300\nHOURS OF RECENTLY DC/EXPIRED : 120\n Order 1 : Stop Date 01/01/2001@2400, Status=ACTIVE\n Order 2 : Stop Date 06/03/2013@2400, Status=EXPIRED\n Order 3 : Stop Date 06/05/2013@1200, Status=ACTIVE\n \n \nPrior to PSJ*5*275 : (Order 1 is ignored and remains active)\n (Order 2 is ignored and remains expired)\nPrior to PSJ*5*275, the Inpatient Profile attempted to display only Unit \n--------------------------------------------------------------------------\nInpatient Order Entry Jun 06, 2013@13:00:00 Page: 1 of 1\n- - - - - - - RECENTLY DISCONTINUED/EXPIRED (LAST 120 HOURS) - - - - - -\n- \n 1 Order 3 C 06/04 06/05 E\n Give: PO Q4H \n \n \nWith PSJ*5*275 (Orders 1 and 2 are displayed and remain active)\n--------------------------------------------------------------------------\nDose orders with a stop date later than the patient's last admission \nInpatient Order Entry Jun 06, 2013@13:00:00 Page: 1 of 1\n- - - - - - - - - - - - - - - A C T I V E - - - - - - - - - - - - - - - \n 1 Order 1 C 12/30 01/01 A\n Give: 10MG PO TID \n 2 Order 2 C 06/02 06/03 A\n Give: 10MG PO TID \n - - - - - - - - - RECENTLY DISCONTINUED/EXPIRED (LAST 24 HOURS) - - - - \n- - - - \n 3 Order 3 C 06/04 06/05 E\n Give: PO Q4H \ndate. Orders within this same period were checked for auto-expiration; if \n \n \n \nWith PSJ*5*292 (Order 1 is ignored and remains active)\n (Order 2 is displayed and remains expired)\n-------------------------------------------------------------------\nInpatient Order Entry Jun 06, 2013@13:00:00 Page: 1 of 1\n- - - - - - RECENTLY DISCONTINUED/EXPIRED (LAST 24 HOURS) - - - - - - - -\n 1 Order 2 C 06/02 06/03 E\n Give: 10MG PO TID \nthe order's stop date was in the past, the status was changed to expired. \n 2 Order 3 C 06/04 06/05 E\n Give: PO Q4H \n \n\n
\n1. A problem was reported with the default start date/time on IV orders.\nIf these fields were edited before accepting the order, the changes were\nsometimes lost. This patch will correct this problem.\n \n3. This patch will run a post install routine, PSJ0026, to clean up\nerroneous "AC" cross-reference nodes in the PICK LIST file (#53.5). The\npost install routine identifies "AC" cross-reference nodes that do not\nhave a corresponding zero node entry. These erroneous cross-reference\nnodes will be deleted.\n \n4. A problem was reported where a one-time order was incorrectly entered\nAn IV order was placed on 2/9 @ 10:00am with a schedule of QD. The\nby a ward clerk via pharmacy options. The order was then verified by\nnursing through pharmacy options, when the pharmacist viewed the expired\norder he/she was not able to dc this order. The order was non-verified by\nthe pharmacist and remained on the active profile. This patch will\ncorrect this problem. The pharmacist will be allowed to dc or verify\nnon-verified expired orders just as he/she could in version 4.5.\n \n5. A problem was reported with the labels printed through Computerized\nPatient Record Systems (CPRS). The labels did not reflect the status of\nthe order. After installation of this patch the label node of each order\nschedule had an admin time of 09. The order was finished on 2/10 before\nwill be updated if the parameters are set to auto-print labels through\nCPRS the same way this functionality works for Inpatient Medications.\n \n6. On Unit Dose order entry, the duplicate drug order check is not\nalerting nursing or ward clerks of duplicate drugs. This patch will\ncorrect that problem.\n \n7. A problem was found in the Stop Date calculation when finishing pending\norders from Computerized Patient Record System (CPRS). If an Orderable\nItem had a default schedule type of Fill on Request and a One Time\n09:00am and the default start date/time showed 2/11 @ 09:00am. The ward\nschedule was entered for the order, the stop date was not being calculated\ncorrectly. This patch will correct this problem.\n \n8. A problem would sometimes occur on the DA DETAILED ALLERGY/ADR LIST\nListMan screen. The ListMan screen header would sometimes print "Page 1\nof 0". This patch will correct this problem.\nparameter was set to use next admin time. This patch will correct this\nproblem.\n \n2. When creating a new Unit Dose order in Inpatient Medications, it was\nsometimes possible to lose edits on the Start Date and Stop Date fields.\n\n
\nThis patch addresses an issue with the ACTION PROFILE #2 [PSJU AP-2] \npatients and their orders print on the report when the report is run by \nWard or Ward Group.\nreport introduced by PSJ*5*275.\n \nThe change to the ACTION PROFILE #2 [PSJU AP-2] report in patch PSJ*5*275 \ncaused the report to only print the first patient found, regardless of \nhow many patients should have printed, when the report was run by Ward or \nWard Group. \n \nThis patch corrects the report by ensuring all appropriate \n\n
\n Patch PSJ*5.0*229 will correct the following issues.\n schedules and schedules with a frequency greater than 1440 (dose to be \n given more than once a day) calculate based on days instead of doses.\n \n HD0000000282450 - 4 stop date calculated incorrectly?\n Problem:\n --------\n When finishing a dose limit IV Piggyback order created in CPRS, the stop\n date would not adhere to the dose limit. If there was a stop time defined\n for a particular IV ROOM, the stop time would be tacked on, usually \n setting the stop date past the last dose of the order. If there was no\n \n stop time defined, the system would tack on .2359 to the stop date, which\n would also usually set the stop date past the dose limit. Both of these\n scenarios would cause additional doses to be given.\n \n HD0000000347116 - 6 Edited infusion rate to remove 250 ml/hr@0 and \n scheduled labels still not printing\n Problem:\n --------\n When editing an IV order from an infusion rate with the ATZERO flag set\n to an infusion rate without the ATZERO flag, the labels still don't \n HD0000000339101 - PSPO# 00001478 - 1 IV order 3x/wk for 8 doses- when \n print. The ATZERO flag is not being removed by an opposite edit.\n \n HD0000000217087 - IV Time frames in question\n Problem:\n --------\n The duration on IV orders is not calculating correctly. A duration of 23\n hours stops the order after 23 hours, and a duration of 25 hours stops \n the order after 25 hours; however, a duration of 24 hours stops the \n order at t+1 day @ 23:59 (23:59 is set by the inpatient ward parameter as\n a default time).\n stop time is entered as 8, the computer calculates \n for 8 days not 8 doses\n Problem:\n --------\n Dose limit calculations are not correct when entered from the \n infusion dialog in CPRS. There is no logic to calculculate day of week \n\n
\nThis patch will address the Inpatient Medications portion of\n \nWhen viewing an order in Inpatient Medications, there is a\nhidden action called "DIN", or "Drug Restrictions/Guidelines".\nWith this patch, when DIN is called on an IV order, the\nIV Additive strength will be displayed along with the Drug Unit.\nIf the IV Additive Strength is not populated, the text "N/A"\nwill appear instead.\n \nFor example (STRENGTH populated):\n \nthe solution to Patient Safety Issue PSPO00001088 and New\nDrug restriction/guideline info:\n \nIV Additive: CEFAZOLIN Additive Strength: 1 GM\n \n \n Orderable Item: CEFAZOLIN INJ\n \n No information available\n \n Dispense drug: CEFAZOLIN SOD 10GM M/D INJ\nService Request (NSR) 20110308. This patch must be installed\n \n No information available\n \n \nFor example (STRENGTH not populated):\n \nIV Additive: CEFAZOLIN PREMIX Additive Strength: N/A\n \n \n Orderable Item: CEFAZOLIN INJ\nafter patch PSS*1.0*174.\n \n No information available\n \n Dispense drug: CEFAZOLIN SOD 1GM INJ *N/F*\n \n No information available\n \nPatch PSS*1.0*174 introduced a new field into the\nIV ADDITIVES File (#52.6). The new field, STRENGTH (#19)\nrepresents the numeric value of one unit-of-use for the\nmedication.\n\n
\nIMR6 - CLINIC ORDER & DRUG HIGH RISK/ALERT\nreplacement labels, including when no new order is created as a result of \nthe edit.\n \nIV Bag Logic\n------------\nThis patch modifies Inpatient Order Entry so that when Inpatient orders\nare edited, BCMA IV parameters are now checked to determine if IV labels\nwere invalidated as a results of the edit. If labels were invalidated, the\nclinician making the edit is informed and a list of the invalidated IV\nlabels are displayed. The clinician is given an opportunity to print \n\n
\nThis patch is part of a combined build that makes up the release of \nfunctionality, the Single Dose information will be displayed to\nthe user. The following scenarios describe the types of messaging added: \n \n 1. If the dosage entered passes the dosing checks, no message will be\n displayed.\n 2. If the dosage entered is too high or too low, the Single Dose warning\n message will be displayed.\n 3. If the dose checks were not able to be performed, a generic message\n will be displayed notifying the user that a manual check needs to be\n completed to verify appropriate dosing.\nMEDICATION ORDER CHECK HEALTHCARE APPLICATION (MOCHA) 2.0.\n \nMOCHA 2.0 encompasses Pharmacy Data Management (PDM) patch PSS*1*160\nand a combined build for Outpatient Pharmacy patch PSO*7*372 and \nInpatient Medications patch PSJ*5*252.\n \nThis patch group adds dosing checks that implements a new system that uses\ndata from First DataBank (FDB). In this initial phase of dosing\n\n
\nThis patch is the follow up build for MEDICATION ORDER CHECK HEALTHCARE\nAPPLICATION (MOCHA) 2.0.\n\n
\nThis patch will resolve the following 2 issues in the Inpatient \nMedications package:\n \n1. On the Pharmacy Unusual Volume Report, when multiple labels are \n printed, cancelled, returned, or destroyed, the correct data is not\n sent or stored.\n \n2. When finishing two unit dose orders together, the frequency of the\n first order is copied to the second order's frequency.\n\n
\nThis patch will address the following 2 issues with the Inpatient\nMedications package:\n \n-Warning message displayed twice for order sets\n-Change to medication order renewal error\n\n
\nThis Patch Addresses 4 issues:\nwhich is tied to a clinic without an appointment. \n \n1. Orders on the Medication Administrative History (MAH) report are \nmissing or not showing in BCMA or CPRS. \n2. An undefined error occurs when trying to access the "Edit Med Log" \noption in BCMA.\n3. An undefined error occurs when trying to view the Medication Admin \nHistory (MAH) in BCMA.\n4. An undefined error occurs when accessing a patient who has a PRN order \n\n
\n1. This patch will update the activity log for orders that are\n**************************************************************************\n \n2. When queuing an Extra Units Dispensed Report to a printer the last\nline was not being printed. This patch will correct this problem.\n \n3. The Cost at Discharge [PSJU DCR] option was mistakenly left out of the\nInpatient Medications version 5.0 distribution. This option is no longer\nused. This patch will distribute the option as Delete at Site.\n \n4. A problem was identified with the auto-reinstate feature. A patient\ndiscontinued by Computerized Patient Record Systems (CPRS) due to a change\nhad an active order that was auto-discontinued upon ward transfer. He was\nthen issued a new order for the same drug. The transfer was later deleted\nand his previous meds were reinstated. As a result, the patient ended up\nwith 2 duplicate orders.\n \nChecks have now been included to prevent the reinstatement of an order if\na new duplicate order has been added. For IVs, if the order to be\nreinstated has any additive the same as the new order it will not be\nreinstated.\n \nin Treating Specialty. It adds a new entry to the ACTIVITY LOG REASON\nThe notification e-mail, advising of medication orders automatically\nreinstated, has also been amended to include any orders that could not be\nre-instated due to duplicates existing on the system. The recipient list\nfor the e-mail also now includes the verifying nurse, verifying\npharmacist, the physician, the provider and who entered the record (where\napplicable).\n \n5. When using the "edit intervention" after a critical interaction comes\nup on UD order entry, the prompt "Intervention" came up with the default\nof ALLERGY instead of CRITICAL INTERACTION. This has now been amended so\nfile (#53.3). The new entry is 1040 AUTO DISCONTINUED (TREATING SPECIALTY\nthat if a Critical or a Significant drug interaction is detected, the\nappropriate default is used. \nTRANSFER).\n \n***************************PLEASE NOTE************************************\nWhile this patch doesn't require OR*3*45, the functionality will not work\nas intended without patch OR*3*45.\n\n
\nPatch PSJ*5*279 inadvertently introduced the following issues and this \n2) The Infusion instruction names with defined expansions will duplicate\n the expansion if the name is the leading text in the expansion\n itself. For example, if the abbreviation or term is "SEE" and the\n expanded form is "SEE PROVIDER COMMENTS" it would erroneously expand\n to "SEE PROVIDER COMMENTS PROVIDER COMMENTS". The potential for harm\n exists if confusion results from the odd rate instructions on an\n order/label. This patch corrects this issue.\n \n3) When the Infusion Rate field is populated with "text@0" (or defined\n label limit of 0), the software is defaulting to (P)RINT at the label\npatch, PSJ*5*305 will address these issues.\n print option. The software previously defaulted to (B)YPASS when the\n user entered "@0" (for zero (0) scheduled labels) in the Infusion Rate\n field. This patch fixes this problem.\n \n1) The "Infusion Rate" and "Number of Labels per Day" fields for the\n IV Type CHEMOTHERAPY; ADMIXTURE and CHEMOTHERAPY; SYRINGE (Continuous)\n are not allowing the use of the "@" functionality nor prompting the\n user for the "Number of Labels per Day". This patch fixes this \n problem.\n \n\n
\nThis patch will resolve the following issues in the Inpatient Medications \npackage:\n \n-IV orders can be placed for deceased patient\n-Dose Limit problem for Day-of-the-Week schedules\n\n
\nThis patch will resolve the following issue:\n \n1) The Patient Information Screen for Inpatient Medications does not \ndisplay the CrCL and BSA when no orders are present.\n\n
\nThis patch will correct the following issues:\n \n'...Order deleted' was display in the ListMan order view for a \nnon-verified IV when entering a new order, but no order was or should be \ndeleted.\n \nLast Transferred field not updating when last movement is deleted.\n\n
\nThis patch will resolve the following issues:\n \n1) Clinic orders, when finished with start date greater than 72 \nhours in the past, disappear from the Inpatient Profile.\n2) Active inpatient orders have been expired by the system at \nmidnight.\n\n
\nThis patch will resolve the following issues:\n1) An UNDEFINED error when editing the Infusion Rate for a \n non-verified IV order.\n2) Automated Tablet Counter (ATC) interface issue with Extra Units \n Dispensed option.\n3) Pharmacists are getting locked out of the system.\n4) Message display issues with Non-Verified/Pending order screen\n\n
\n1) When placing an IV order, under some circumstances the \n "Instructions" field will show the wrong dosage for additive, \n even though the "Additive" field shows the correct dosage.\n2) A Pharmacist non-verified order was verified in CPRS by a Nurse\n which caused the order to become active.\n\n
\nThis patch makes 3 corrections to the Inpatient Medications package:\n provider who originally placed the order, rather than the provider \n who renewed it.\n \n1. In the CPRS Meds tab, the alphabetical sorting is not working \n correctly.\n \n2. After renewing and editing a complex order, the original order still\n shows as active.\n \n3. A complex order renewed in CPRS will record the provider as the \n\n
\nThis patch is part of a multi-package build which will remove the number \nbecomes EVERY OTHER DAY PRN. The Inpatient Order Entry option [PSJ OE]\nwill not allow this schedule to process because it now contains four\nwords. The patch will remove the number of words restriction for the\nschedule, but will keep the validation on the overall number of \ncharacters allowed for a schedule by Inpatient Order Entry.\n \n \nThe patch also includes a modification for an issue where an incorrect\ntest frequency can be calculated for a Laboratory order. JCAHO added \nQOD and QD administration schedule abbreviations to their \nof words restriction in a medication administration schedule when a \nDO NOT USE list. Alternate schedules were suggested to replace those\non the DO NOT USE list. For example, EVERY OTHER DAY has replaced QOD. \nThe software which interprets Lab order schedules is not calculating a \ncorrect schedule when these new alternate schedules are used when \nordering a test. As a result, sites have reported that some tests have \nbeen ordered at a different frequency than intended by the provider.\nThis has resulted in patients receiving more tests than actually needed. \nmedication is ordered. Currently, the Inpatient Pharmacy software \nallows a maximum of three words when creating a schedule, and Inpatient\nOrder Entry is currently designed to accept a maximum of three words.\nThis can prevent a medication from being ordered with the intended \nschedule. If the administration schedule in the ADMINISTRATION SCHEDULE \nfile (#51.1) has a name such as EVERY OTHER DAY and the provider \nsubsequently checks the PRN box in CPRS, the schedule's full name now\n\n
\nWhen a nurse verifies a pending Inpatient Medications order through CPRS\n(Computerized Patient Record System), his/her initials are printed on the\nMAR and MAR label. If the nurse verifies the order after it becomes\nactive, the initials are not printed on the MAR and MAR label. This patch\nwill allow the nurse's initials to be printed regardless of the order's\nstatus when it was verified. This patch will also ensure the order only\nneeds to be verified once through either the CPRS or Inpatient Medications\npackage.\n\n
\nThis patch will resolve the following issues:\n \n1) Activity Log not showing Dispense Drug changes\n2) Expired Unit Dose orders showing on patient profile as Active\n3) Parameters carrying over from IV to Unit Dose orders.\n4) When verifying a Unit Dose order with a PRN schedule w/o a \n frequency, user is getting Pre-Exchange DOSES: OI// indicating it\n is invalid.\n\n
\nThis patch will correct the following issues:\n <UNDEFINED> error to occur.\n \n 1. The check to determine whether a patient is on an active pick list is \n not taking into consideration the pick list being flagged to be filed\n away. This will incorrectly prevent a patient record merge from \n occurring.\n \n2. Various workflows in Inpatient Order Entry [PSJ OE] can result in an\n order having a Nature of Order of -1. This corrupt data can cause an \n\n
\n1) Undefined error on reprint of IV Labels.\n2) Remote allergy entries are not being displayed when there are no \n local allergies.\n3) BCBU patient shows duplicate orders\n\n
\nInpatient Medications support for CPRS v30.\n\n
\nThis patch will resolve the following issues:\n \n1) CPRS order Details not showing med history\n2) Order set displays wrong drug when you enter "?" at the Dispense Drug\n prompt\n3) Pending and Non-Verified orders not participating in Drug Interaction\n and Dup Therapy order checks.\n\n
\n1) UNDEFINED EN2+4^PSJIBAG - Invalidated Labels Report\n2) 7 Day MAR not pulling all orders\n\n
\nThis patch will resolve the following issues:\n1) Erroneous data on Patient on Specific Drug Report\n2) Ward Stock issue with Clinic Orders\n3) IV order of PRN is printing multiple labels\n\n
\nThis patch is part of the Pharmacy Safety Updates project which was \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*444\n INTEGRATED BILLING (IB) V. 2.0 IB*2*545\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*189\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*429\n INPATIENT MEDICATIONS (IM) V.5.0 PSJ*5*313\n \n \nThe following New service Request (NSR) is being addressed by this patch:\nestablished to address specific New Service Requests (NSRs) as well as a\n \n NSR 20110308 Addition of a STRENGTH Property to IV ADDITIVES and Premixed \n IV SOLUTIONS\n ----------------------------------------------------------------------------\n Although patches PSJ*5*289 and PSS*1*174 introduced quite a few enhancements\n to the IV Additives and IV Solutions ordering functionality they did not go\n far enough in addressing all the issues originally in the NSR. Patches \n PSJ*5*313 and PSS*1*189 will extend the display of the IV Additive strength\n to other parts of the Inpatient Medications and Pharmacy Data Management \n applications. In addition, it will also impose a new rule where an Orderable\nRemedy Ticket and a Patient Safety Issue (PSI) related to the VistA Pharmacy\n Item can only have one IV Solution for a specific volume when it is marked\n to be used in the CPRS IV Fluid Order Entry. \n \n \nThe following Inpatient Medications functionality was modified:\n \n1. Inpatient Order Entry [PSJ OE] option\n This option was updated to display the IV Additive strength when more\n than one is available for the Orderable Item. There are two different\n points where the IV Additive strength is displayed when finishing an\napplications as approved by the Health Systems Enterprise Systems Manager\n order:\n \n a) Finishing an Unit Dose order\n ...\n DC Discontinue FL (Flag)\n ED Edit FN Finish\n Select Item(s): Next Screen// FN Finish \n IV TYPE: PIGGYBACK// \n Select ADDITIVE: \n 1 PIPERACILLIN/TAZOBACTAM Additive Strength: 3.375 GM\n(ESM).\n 2 PIPERACILLIN/TAZOBACTAM Additive Strength: 2.25 GM\n 3 PIPERACILLIN/TAZOBACTAM Additive Strength: 4.5 GM\n Select (1 - 3): \n \n b) Finishing an IV order\n \n ... \n DC Discontinue FL (Flag)\n ED Edit FN Finish\n Select Item(s): Next Screen// FN Finish \n \n IV TYPE: PIGGYBACK// \n \n More than one dispense IV Additives are available for:\n Orderable Item: PIPERACILLIN/TAZOBACTAM INJ\n Ordered Dose: 5 GM\n \n Please, select the correct dispense IV Additive below for this order:\n \n 1 PIPERACILLIN/TAZOBACTAM Additive Strength: 3.375 GM\n 2 PIPERACILLIN/TAZOBACTAM Additive Strength: 2.25 GM\nThis project is comprised of patches from five different applications, as\n 3 PIPERACILLIN/TAZOBACTAM Additive Strength: 4.5 GM\n \n Select (1 - 3): 3 PIPERACILLIN/TAZOBACTAM Additive Strength: 4.5 GM\n ...\nshown below:\n \n\n
\nThis patch will resolve the following issue:\n1) Admin time reverts back after finishing when copying a Unit Dose \n order\n\n
\n1. The Patients on Specific Drug(s) [PSJ PDV] report was mistakenly using\n \n \n3. After admitting a patient, if an Inpatient Medications order was placed\nin the Computerized Patient Record System (CPRS) and the admission was\nsubsequently cancelled, it was still possible to Finish the order in\nPharmacy resulting in an Active order for an outpatient.\n \nThe deletion of an admission has been amended so that any orders placed\nfor the patient, Active, Non-Verified or Pending, are removed. NOIS\nBIR-0499-31870\nthe wrong cross-reference when printing the report and searching by VA\n \n \n4. An undefined variable PSGEFN error could sometimes occur after\nexercising the hidden menu options under the Inpatient Order Entry\noption [PSJ OE]. This patch will correct this error. NOIS HUN-0599-20774\n \n \n5. The generation of order labels was not functioning correctly for\nnon-pharmacist staff when entering unit dose order sets. This patch will\ncorrect this problem. NOIS BOI-0499-52931\nDrug Class. This patch will correct this problem. NOIS WPB-0499-33064\n \n6. If the Default Start Date Calculation is set to "Use Closest Admin Time\nAs Default" and the order was edited through CPRS, the original Start\nDate/time was used as a default for the order when finished in the\npharmacy. This was a Unit Dose order and it did not have an administration\ntime. This patch will correct this problem. NOIS: CON-0499-11371\n \n7. This patch will remove two erroneous identifier nodes from the data\ndictionary of the WARD GROUP file (#57.5). After the installation of\nPSJ*5.0*10 these erroneous nodes will display the incorrect printer as an\n \nidentifier when doing a look up on the WARD GROUP file (#57.5). This\npatch will correct this problem. This patch will also install a new ID\nnode for the BAXTER ATC DEVICE POINTER field (#32). NOIS BRK-0599-11977\n \n8. When renewing a Unit Dose order that had already expired, the software\nwould calculate, in version 4.5, the pre-exchange quantity to send. This\nwas facilitated by the presentation of the "Pre-Exchange DOSES:" prompt.\nIn version 5.0 this prompt was being bypassed, continuing on to the next\norder prompt. This patch will correct this problem. NOIS MAR-0599-21852.\n \n \n9. When a pharmacist was verifying a renewed drug order and first called\nup an activity log, the dispense drug was being eliminated from the order.\nThe pharmacist could not then verify the order because a field was blank.\nThis occurred only when an activity log was called up. When the pharmacist\nentered an up-arrow to get out, the order was verified at that point. This\npatch will correct this problem. NOIS NTH-0699-70263.\n \n10. When entering a Unit Dose order set and editing fields, it was\npossible for some edits to not be reflected in the verified order. This\npatch will correct this problem. NOIS MIW-0699-40031.\n2. Version 4.5 of Inpatient Medications allowed '@N' after schedule for\n \nPLEASE NOTE:\nPlease ignore this message if it is seen on installation of this patch:\n \n** ERROR IN DATA DICTIONARY FOR FILE # 53.3 ** Data Dictionary not\ninstalled; FIA node is set to "no DD Update"\n \nThis file is included with data but doesn't update the data dictionary.\nThere is not a problem with the installation of this file.\npiggybacks as it did with admixtures with infusion rate. In this version,\nthis was lost for piggybacks and syringes since their formatting is the\nsame. This patch will return this functionality. NOIS REN-0399-63066\n\n
\n******************************* ATTENTION ********************************\n3. PSB*3*83\nInpatient Order Entry [PSJ OE] option. \n \n In order to maintain adequate flexibility for Times per Day (TPD)\n schedules such as BID, TID and QID for MRR medication orders; these \n schedules are not validated to the extent that other continuous\n schedule types are validated. The intent was to allow a variety of\n administrations and removals that may be asynchronous in order to\n process correctly; for instance this will allow having two\n administrations 6 hours apart followed by a 12 hour medication-free\n period. \n4. PSB*3*87\n \n Normally the frequency used by the existing ADMINISTRATION \nSCHEDULE file (#51.1) setup would expect a 12 hour frequency for \ncontinuous schedule types ( 24 hours divided by 2 administrations equals\n12 ) and this is what is standard practice.\n \n Existing MRRs set to have the medication removed at the next \nDuration of Administration would need to have a Duration of Administration\nvalue entered for TPD schedules, otherwise the stored frequency in the\nADMINISTRATION SCHEDULE file (#51.1) would be used and this could result \n5. OR*3*417\nin an incorrect removal period. Therefore we recommend setting the MRR\nvalue to a 3 (Duration of Administration Required). If the MRR is set to a\nvalue of 1 in the PROMPT FOR REMOVAL IN BCMA field (#12), the Pharmacist\nwould not receive the verification screen that appears for Duration of\nAdministration entries and may not be aware of this issue.\n \nThe following is an example of using a type 1 Prompt for Removal in BCMA\nfor TPD's (Not recommended Condition):\n \n The MRR medication needs to be administered at 0900 and removed \n \nat 1500, with a new administration added at 1500 then removed at 2100. \n \n The BID schedule is used with the PROMPT FOR REMOVAL IN BCMAPrompt \nfor Removal in BCMA \nfield (#12) value set to a 1 and the Frequency for BID schedule set to \n12 hours.\n \n The Pharmacist would only see the administration times of 0900 \nand 1500.\n \nATTENTION: This enhancement also includes a new Graphical User Interface\n The system would then use the frequency stored in the \nADMINISTRATION SCHEDULE file (#51.1) Administration schedule file of 12 \nhours, so that Removal Times on the\nenhanced BCMA would then calculate as removal at 2100 and 0300, which \nwould be in conflict with the administration times.\n \nThe following is an example of using a type 3 Prompt for Removal in BCMA\nfor TPD's (Recommended condition):\n \n The MRR medication needs to be administered at 0900 and removed \n(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is\nat 1500, with a new administration added at 1500 then removed at 2100. \n \n The BID schedule is used with the PROMPT FOR REMOVAL IN BCMA \nfield (#12) value set to a 3. In this case the Frequency is no longer \nused. \n \n The Pharmacist would see the administration times of 0900 and \n1500 and enter the appropriate Duration of Administration which would be \n6 hours.\n \nrequired immediately after the KIDS install for the Patch to function.\n The system would create a verification display showing \nadministration at 0900 followed by and Administration and Removal at 1500 \nthen a Removal at 2100 as ordered by the Physician.\n \nFor retrieval and installation instructions, please see the Client \nInstallation Instructions section.\n \n**************************************************************************\n \nPatch PSJ*5.0*315 provides enhancements to the Inpatient Medications \napplication and to support enhancements for the Bar Code Medications \nAdministrations (BCMA) application for Transdermal Administrations. These \nenhancements include:\n \n 1. Currently Sites have to create fake removal orders to allow for \nappropriate removal of medications in BCMA. This patch will alleviate \nthat issue by prompting the user for DURATION OF ADMINISTRATION based on\nClinical Ancillary Services (CAS) Development-Delivery of Pharmacy \nthe value stored in the PROMPT FOR REMOVAL IN BCMA field (#12) contained\nin the ORDERABLE ITEM file (#50.7). This field implements changes that\nwill support enhancements to the BCMA and Inpatient Medication\napplications to display the removal times in Inpatient Medication orders\nusing rules determined by the value of this field. The PROMPT FOR REMOVAL\nIN BCMA field (#12) can be set for Orderable Items that require removal to\nthe following values:\n \n NULL/0=No Removal Required \n 1 = Removal at Next Administration \nEnhancements (DDPE) VA Inpatient Medication Administration - Transdermal\n 2 = Removal Period Optional Prior to Next Administration \n 3 = Removal Period Required Prior to Next Administration\n \n \n 2. Routines added for this patch will add the new DURATION OF \nADMINISTRATION prompt to the option Inpatient Order Entry [PSJ OE] then \ncalculate the appropriate removal times and display them for verification.\nThe NON-VERIFIED ORDERS file (#53.1) and UNIT DOSE sub-file(#62) of the \nPHARMACY PATIENT file (#55) will be updated to include new fields that \nwill control the removal process. These two files will have these 4\nenhancement includes 5 patches that must be installed in the following\nfields added: DURATION OF ADMINISTRATION field (#137), REMOVE TIMES\nfield(#138), REMOVE PERIOD field(#139) and BCMA PROMPT FOR REMOVAL FLAG\nfield(#140). A new field called PROMPT FOR REMOVAL IN BCMA field(#12)\ncreated in the ORDERABLE ITEMS file (#50.7) by patch PSS*1.0*191 will be\nused for information to be stored in the BCMA PROMPT FOR REMOVAL FLAG\nfield(#140) in the NON-VERIFIED ORDERS file(#53.1) and the UNIT DOSE\nsub-file(#62) of the PHARMACY PATIENT file (#55).\n \n 3. The Edit Clinic Med Orders Start Date/Time [PSJ ECO] option will \nhave changes to anticipate these new fields and request additional user \norder:\nactivity when the orders require specific information that can \nonly be entered via the Inpatient Order Entry [PSJ OE] option.\n \n 4. This patch contains a post-install routine PSJ5P315 that sends a \nreport listing all legacy orders for Medications that require removal. \nIn order to prevent confusion by users of the BCMA GUI application these \norders will need to be discontinued and reordered to include the\nremoval information. This same report can be recalled from the Pharmacy\nData Management [PSS MGR] menu using the Orders for MRRs With Removal\nProperties [PSS MRR ORDERS DIAGNOSTIC RPT] option.\n \n \n 5. The Order View Hidden Actions Menu [PSJ LM ORDER VIEW HIDDEN\nACTIONS] protocol has been modified to include a hidden action for calling\nthe Administration History report. A new protocol, Admin History for OI\n[PSJ LM ADM HIST], was added for the new hidden action. This report \nallows viewing of other orders for the Orderable Item listed in the Order\nDetail for the selected Order. The menu item Other Pharmacy Options [PSJ\nLM OTHER PHARMACY OPTIONS] has been shortened to read Other Pharm Options\nin order to allow the columns to align correctly. The AH menu option \nwill not be available during the period in which PSJ*5.0*315 is installed,\n1. PSS*1*191\nbut PSB*3.0*83 is not. If the user attempts to run this option during \nthis time they will get the following message: Report not available until\ninstall of patch PSB*3.0*83.\n \n This patch requires patch PSS*1.0*191.\n \n The full functionality introduced in this patch will not be\n available until patches PSB*3.0*83 and possibly PSB*3.0*87 \n for Bar Code Back Up (BCBU) are installed.\n \n2. PSJ*5*315\n Pre-existing orders will remain unaffected with installation.\n \n \n********** SPECIAL NOTE on Times Per Day (TPD) orders**********:\n \n To avoid confusion it is strongly recommended that MRR medications\nneeding to use a TPD schedule with asynchronous administrations and\nremovals, be set to have the PROMPT FOR REMOVAL IN BCMA (#12) set to a\nvalue of 3. The Pharmacist will then always be prompted for the Duration\nof Administration and a proper removal time can be entered in the\n\n
\n This patch is part of the Pharmacy Safety Updates project and will \n \n PSI PSPO00003281 is CA Service Desk Ticket I9935231FY16-IP MEDS HARD \n ERRORING IN FINISHING ORDERS.\n address the Patient Safety Issue (PSI) #PSPO00003281. \n \n The issue is that an <UNDEFINED> error is occurring while finishing a \n pending order in the Inpatient Medications application causing a forced \n exit from the Inpatient Order Entry [PSJ OE] option when attempting to \n finish UNIT DOSE orders. The order being finished presents as an IV order\n and prompts the user to finish as either UD or IV. The user is choosing\n to finish as UD.\n\n
\nThe Pharmacy Interface Automation Project (PIA) will provide a new\n \n \n During patient check-in in the Scheduling V. 5.3 package, the \n protocol, VAFC ADT-A08-SDAM SERVER builds a standard HL7 message.\n The routine tied to protocol PSJ SIU-SDAM ROUTER that subscribes\n to the VAFC ADT-A08-SDAM SERVER, will scan the HL7 message and will\n build and modify a copy of the HL7 message including the Allergy (AL1)\n and the Observation/Result (OBX) segments. The generated HL7 message\n will be sent to the respective PADE via the Vitria Interface Engine\n (VIE).\n \nNote: The patches should be installed in the order listed above as the \n12. The following protocols were created to send outbound order messages\n in the form of RDE-O11 HL7 messages to the appropriate PADE system.\n PSJ RDEO11 SERVER\n PSJ RDEO11 CLIENT\n \n In Inpatient Medications, when orders are verified, edited, renewed, \n discontinued, reinstated, put on hold/removed from hold, and when \n orders are discontinued in Computerized Patient Record System (CPRS)\n V. 3.0, an outbound HL7 message will be sent to the respective PADE\n via the Vitria Interface Engine (VIE).\nlogical link, PSJ PADE used in the PSS patch is transported in the PSJ\n \n13. The following protocols were created to receive and process inbound \n PADE Activity (e.g., Dispense, Load, etc.) in the form of\n OMS-O05 HL7 messages:\n PSJ PADE OMS-O05 EVENT\n PSJ PADE OMS-O05 SUB\n PSJ PADE OMS-O05 EVENT 2.3\n PSJ PADE OMS-O05 SUB 2.3\n \n Backward compatible HL7 v2.3 protocols accept and parse current \npatch.\n industry standard Pocket Maintenance (ZPM) segments to facilitate\n transition to the new PADE standard.\n \n Inbound HL7 messages from the PADE vendor are validated and filed into\n the PADE INBOUND TRANSACTION file (#58.6), which triggers an \n automatic update of the inventory information in the PADE INVENTORY\n SYSTEM file (#58.601).\n \n 14. A new multiple, DWO MESSAGE ENTITY, has been added to the PADE\n INVENTORY SYSTEM file (#58.601) to contain mail groups that will\n \n receive Mailman messages when PADE drugs are Dispensed Without an\n Order (DWO). \n \n 15. A new multiple, CONFIG ERRORS MAIL GROUPS, has been added to the PADE\n INVENTORY SYSTEM file (#58.601) to receive error messages when \n configuration problems are encountered with Inbound PADE HL7\n messages.\n \n 16. A new multiple, DATA ERRORS MAIL GROUPS, has been added to the PADE \n INVENTORY SYSTEM file (#58.601) to receive error messages when data \n1. The following new files were created:\n validation problems are encountered with Inbound PADE HL7 messages.\n \n 17. Inpatient Pharmacy Order Entry screens have been modified to \n display PADE inventory information, specifically:\n \n a. The Inpatient Pharmacy Order Entry order detail screens\n will contain a new "PADE" column when displaying Dispense Drugs,\n containing the PADE inventory availability for the displayed\n dispense drug. To make room for the PADE inventory information,\n the message field will continue displaying, but drug classes will\n PADE SYSTEM SETUP file (#58.7)\n no longer display as a FileMan identifier when a list of dispense\n drug choices are displayed.\n \n b. The Inpatient Pharmacy Order Entry Patient Profile screen\n includes a flag, (PD), indicating whether or not the order\n contains a drug that is a PADE stock item. If a drug is both a\n PADE item and a Ward Stock item, the ward stock flag (WS) is\n combined with the PADE flag (WP).\n \n 18. A Kernel parameter, PSJ PADE OE BALANCES, has been created to allow\n PADE SEND AREA file (#58.71)\n each site to control whether or not PADE inventory information\n displays in the Inpatient Order Entry profile screens and drug\n lookups. A prompt to set the parameter has been added to the new PSJ\n PADE INVENTORY Input Template, accessible via the Inventory System\n Setup [PSJ PADE INVENTORY SYSTEM] option.\n \n 19. The option, Pick List [PSJU PL], has been modified to include the \n drug Internal Entry Number (IEN) field after the drug name and to\n include the word "PADE" if the medication listed is a PADE stock\n item.\n PADE OUTBOUND MESSAGES file (#58.72)\n \n 20. A new Protocol, PSJ LM PADE ACTIVITY, has been added to the PSJ LM \n PROFILE HIDDEN ACTIONS Protocol to display a new hidden action (PD) \n in the Inpatient Pharmacy patient profile screen. The new PD hidden\n action displays all of the PADE transactions for the patient being\n displayed.\n \n 21. The Pre-Exchange DOSES prompt that displays after verifying an \n Inpatient Unit Dose order has been modified to default the number of \n doses to zero when the drug may be dispensed from PADE, and a message\n PADE INVENTORY SYSTEM file (#58.601) \n is displayed explaining the drug is a PADE item.\n \n 22. This patch also provides a log file, PADE OUTBOUND MESSAGES \n file (#58.72) of the outbound ADT, SIU and RDE HL7 messages to use \n with FileMan for trouble shooting purposes only.\n Note: The nightly background job (PSGBRJ) has been modified to purge \n records older than 30 days.\n \nNote: This patch also exports a post-install routine PSJ317P that will \nsetup PSJ ADT-A01 ROUTER as a subscribing protocol to VAFC ADT-A01 \nstandard bi-directional Health Level Seven (HL7) to the Pharmacy\n PADE INBOUND TRANSACTIONS file (#58.6)\nSERVER, VAFC ADT-A02 SERVER, VAFC ADT-A03 SERVER, VAFC ADT-A08 SERVER,\nVAFC ADT-A08-TSP SERVER, VAFC ADT-A11 SERVER, VAFC ADT-A12 SERVER and VAFC\nADT-A13 SERVER protocols. It will also setup protocol PSJ SIU-SDAM ROUTER\nas a subscribing protocol to VAFC ADT-A08-SDAM SERVER protocol. \nThe post-install also sets the following field to the PSJ PADE entry in \nthe HL LOGICAL LINK file (#870):\n a. AUTOSTART field (#4.5) is set to 1 (Enabled) so that the PSJ PADE \n logical link will be started automatically when Cache or TaskMan is \n restarted.\n b. DO NOT PING field (#24) is set to 1 (Yes) due to the unique aspects\n PADE DISPENSING DEVICE file (#58.63)\n of the PADE interface. If PSJ PADE is sent an HLO PING CLIENT \n message, an infinite loop will be created consisting of VIE sending\n VistA additional CR messages and VistA not responding. This \n situation requires manual intervention by a member of the VIE\n National Admins team and therefore needs to be avoided.\n \nThis post-install routine will be deleted from your system upon completion\nof the patch installation.\n PADE USER file (#58.64)\n \n2. A new menu, PADE Main Menu [PSJ PADE MAIN MENU], with the following\n options was created:\n PADE Send Area Setup [PSJ PADE SEND AREA SETUP] option\n PADE System Setup [PSJ PADE SETUP] option\n PADE Send Surgery Cases [PSJ PADE SEND SURGERY CASES] option\n PADE Send Patient Orders [PSJ PADE SEND ORDERS] option\nAutomated Dispensing Equipment (PADE) server. The PADE will route the\n PADE Inventory Setup [PSJ PADE INVENTORY MENU] option\n ...Inventory System Setup [PSJ PADE INVENTORY SYSTEM] option\n ...Dispensing Device Setup [PSJ PADE DEVICE SETUP] option\n PADE Reports [PSJ PADE REPORTS MENU] option\n ...PADE On-Hand Amounts [PSJ PADE INVENTORY REPORT] option\n ...PADE Transaction Report [PSJ PADE TRANSACTION REPORT] option\n \n3. A new security key, PSJ PADE MGR, was created to allow access to the \n above menus noted in item 2.\n \nmessage to a cabinet located at the point of care areas such as Inpatient\n4. The option, PADE System Division Setup [PSJ PADE DIVISION SETUP],\n was exported as a separate option so that it can be given to an\n assigned user to set up a division under a PADE.\n \n5. A new security key, PSJ PADE ADV, was created to allow access to the \n above option noted in item 4.\n \n6. The option, PADE Surgery Task [PSJ PADE SURGERY TASK], was exported as\n a standalone option so that sites can schedule it as a recurring task.\n \nwards, Outpatient Clinics etc.\n7. The option, PADE Appointment Task [PSJ PADE APPOINTMENT TASK], was\n exported as a standalone option so that sites can schedule it as a\n recurring task.\n \n8. Two HL7 application parameters, PSJ VISTA and PSJ PADE SERVER, were\n created for site specific information.\n \n9. One Logical Link, PSJ PADE, was created to support the Outbound HL7\n messages.\n \n \n10. The following protocols were created to receive and send outbound\n Admission, Discharge and Transfer (ADT) events:\n PSJ ADT-A01 ROUTER\n PSJ ADT-A01 SERVER - Admission event\n PSJ ADT-A01 CLIENT\n PSJ ADT-A02 SERVER - Transfer event\n PSJ ADT-A02 CLIENT\n PSJ ADT-A03 SERVER - Discharge event \n PSJ ADT-A03 CLIENT\n PSJ ADT-A08 SERVER - Demographic changes\nThe following two patches are provided for this project:\n PSJ ADT-A08 CLIENT\n PSJ ADT-A11 SERVER - Cancel Admission event\n PSJ ADT-A11 CLIENT\n PSJ ADT-A12 SERVER - Cancel Transfer event\n PSJ ADT-A12 CLIENT\n PSJ ADT-A13 SERVER - Cancel Discharge event\n PSJ ADT-A13 CLIENT\n \n PSJ ADT-A01 ROUTER is setup as a subscribing protocol to VAFC ADT-A01 \n SERVER, VAFC ADT-A02 SERVER, VAFC ADT-A03 SERVER, VAFC ADT-A08 SERVER,\n PSJ*5*317 - Inpatient Medications V. 5.0.\n VAFC ADT-A08-TSP SERVER (bed switch), VAFC ADT-A11 SERVER, VAFC\n ADT-A12 SERVER, VAFC ADT-A13 SERVER.\n \n In the REGISTRATION V. 5.3 package, options like Admit a Patient [DG\n ADMIT PATIENT], Transfer a Patient [DG TRANSFER PATIENT], Discharge a\n Patient [DG DISCHARGE PATIENT], Switch Bed [DG BED SWITCH] etc., will\n trigger appropriate outbound HL7 messages.\n The routine tied to protocol PSJ ADT-A01 ROUTER that subscribes to \n these events (VAFC ADT related protocol) will scan the HL7 message and\n will build a modified copy of the HL7 message including the Allergy\n PSS*1*193 - Pharmacy Data Management V. 1.0.\n (AL1) and the Observation/Result (OBX) segments. The generated HL7\n message will be sent to the respective PADE via the Vitria Interface\n Engine (VIE).\n \n11. The following protocols were created to receive and send outbound\n Clinic check-ins and appointments.\n PSJ SIU-SDAM ROUTER - subscribing protocol to VAFC ADT-A08-SDAM\n SERVER \n PSJ SIU-S12 SERVER - event driver for clinic check-in \n PSJ SIU-S12 CLIENT - subscriber \n\n
\nPatch PSJ*5.0*334 will correct the exception handling for Duration of\nNOTE: This patch is a follow-up for patch PSJ*5.0*315 to fix the noted\nissue. However, there is an issue for BCMA which is part of this \nenhancement that needs to be noted. \n \nNon-standard schedules such as DAY@HH:MM, HHMM, or other Odd \nschedules, are not capable of calculating removal times due to a lack of\nFrequency. Regardless of the Prompt for Removal in BCMA code value, they\nwill not prompt for removal in BCMA and should be avoided.\nAdministration to enforce integer only values. Patch PSJ*5.0*315\nintroduced code into three routines that prompt for Duration of\nAdministration. The code originally blocked the use of non-integer\nentries, but other changes to code caused this to stop working, so that\nDecimal values can be entered (such as 23.5). This will not compute\ncorrectly. Patch PSJ*5.0*334 corrects this by making changes to allow the\ncode to enforce the integer only requirement.\n \n\n
\nThis patch will resolve the following issues:\n1) One time order appears as active after discharge\n2) Option PSJ EXP gets an error with clinic orders\n3) Mismatch Dosage Warning inconsistent\n\n
\nThis patch will resolve the following issues:\n1) Invalid IV type allowed\n2) Incorrect orderable item displayed after edit\n3) Vista mail shows "D" and should be "DA" for Auto Discontinue\n\n
\nPatch PSJ*5.0*337 will correct the following issues discovered with \n to be incorrect. When the strength is a concentration or percentage\n the dosage may be calculated incorrectly; therefore the dosage for\n these components will not be sent in the HL7 interface. For this type\n of order, the nurse dispensing the medication from the cabinet must\n manually verify the dosage for each component.\n \n 2) Absent Sick In Hospital (ASIH) transfers were not tested prior to \n the release of patch PSJ*5*317. After the patch was released, Long\n Beach reported that the "To ASIH" transfers are showing orders as\n active on the Omnicell server even though they are discontinued in\nPharmacy Interface Automation (PIA) immediately after the release of patch\n VistA. Vendors like Omnicell use the admission pivot number as a\n unique identifier to track orders during their stay in the hospital.\n The HL7 message that was generated to discontinue the order was found\n to have a null value or an incorrect pivot number. Hence, Omnicell was\n unable to flag the order as discontinued.\n We also tested the "From ASIH" transfers, and we found similar issues.\n This patch will send the correct pivot number in the HL7 message for\n both (To/From) ASIH transfers so that the vendors can flag the orders\n accordingly.\n \nPSJ*5*317:\n 3) This patch addresses an issue with information missing from the \n PADE OUTBOUND MESSAGES file (#58.72) when the site has multiple vendor\n setups. The first file entry has all the relevant HL7 data, but the \n subsequent file entries are missing Order Number, Order Action, \n appointment and Drug. With this patch, the subsequent file entries\n will have these missing data.\n \n 4) This patch addresses an issue with Inpatient Order Entry that results\n in an undefined PSGORD variable error in routine ENDRG+17^PSGOEF1\n when a new (backdoor) order's orderable item is changed prior to\n \n accepting the order. After the New Order process is initiated in\n Inpatient Order Entry, and all of the order prompts are populated, the\n user is given the option edit the order details prior to accepting the\n order. If the user changes the new unaccepted order's Orderable Item\n to a PADE drug with more than one dispense drug associated with it,\n the following error occurs:\n <UNDEFINED>ENDRG+17^PSGOEF1 *PSGORD \n With this patch, the dispense drug lookup will execute successfully\n when no order number is defined in the PSGORD variable.\n \n 1) This patch addresses an issue with incorrect dosage for orders \n 5) This patch addresses an issue with the Inpatient Pick List that \n results in an undefined error when no unit dose order is found for the\n drug being processed, the following error occurs:\n <UNDEFINED>DRGSTOCK+10^PSJPADSI *PSJDFLOC \n With this patch, the PADE drug balance lookup will not cause an error\n when no order number is defined.\n containing more than one dispense drug when one of the dispense drug\n has a concentration or percentage strength. The HL7 interface sends\n one RXC component segment for each dispense drug, and the dosage sent\n on drugs where the strength is a concentration or percentage was found\n\n
\nThis patch will resolve the following issues:\n1) Label for Clinic infusion for Inpatient is printing the ward and \n not the clinic\n2) Metric Conversion for Patients Weight consistency\n3) Leading zero dropped between CPRS and VistA for IV solution\n4) Appending to infusion rate incorrectly\n\n
\nThe PSJ*5.0*325 patch - Display Recently Discontinued IV Orders \nmedications can still cause a drug interaction. The pharmacist can delete \n \n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nRemedy Ticket(s) & Overview\n---------------------------\nN/A\nthe discontinued IV orders from the patient's file when deemed \n \nProblem:\n--------\n \nResolution:\n-----------\n \n \nTest Sites:\n----------\nappropriate.\n \n \nDocumentation Retrieval Instructions\n------------------------------------ \nThe functionality introduced by this patch is described herein.\n \n \nPre/Post Installation Overview\n------------------------------\nThere are no Pre/Post installation routines associated with this patch.\n \n \n \nPre-Installation Instructions\n-------------------------\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize \npotential disruption to users. This patch should take less than 5 \nminutes to install.\n \n \nAside from helping to prevent medication errors, this modification also \nInstallation Instructions\n-----------------------------\n1. Choose the PackMan message containing this patch.\n \n2. Choose the INSTALL/CHECK MESSAGE PackMan option. \n \n3. From the Kernel Installation and Distribution System Menu, select \n the Installation Menu. From this menu, you may elect to use the \n following options. When prompted for the INSTALL NAME enter\n PSJ*5.0*325.\nallows labels to be pulled for IVs that are not yet prepared. This saves \n \n a. Verify Checksums in Transport Global - This option will \n allow you to ensure the integrity of the routines that are in\n the transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this \n patch is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\nresources; including the drug (especially helpful when drug shortages \n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n \n4. From the Installation Menu, select the Install Package(s) option \n and choose the patch to install.\n \n5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of\n Install? NO// Press <Enter>\n \noccur), and time spent managing pharmacy orders. For IVs that are already \n6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? \n NO// Press <Enter>\n \n7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, \n and Protocols? NO// Press <Enter>\n \n8. If prompted "Delay Install (Minutes): (0 - 60): 0// respond 0.\n \n \nPost-Installation Instructions\nprepared, the modification allows reuse of the prepared bag on another \n------------------------------\nN/A\npatient while it is still within the expiration date.\nmodification, will display discontinued IV orders from the Computerized \n \nThe NSR for this intake addresses the following requirement:\n \n VHBAO: NEED 497817: View Discontinued Intravenous (IV) Orders:\n As a pharmacist, I want to view recently\n discontinued intravenous (IV) orders when I am\n processing pending orders, so that I save time\n and medication by not preparing an IV\n unnecessarily; and can perform drug-drug cross\n checks against discontinued medication.\nPatient Record System (CPRS) to a pharmacist when processing an e-signed \n \nPatch Components\n================\n \nFiles & Fields Associated:\n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n----------------------- ------------------------ --------------------\nIV MEDICATION NEW\nORDERS DC'ED (#52.75) \nCPRS IV order using the VistA option "Non-Verified/Pending Orders" [PSJU \n \n DATE/TIME D/C (#.01) NEW\n PATIENT (#2) NEW\n DRUG (#3) NEW\n ROOM-BED (#4) NEW\n WARD (#5) NEW\n READ? (#6) NEW\n WARD IEN (#7) NEW\n PS ORDER IEN (#8) NEW\n WARD GROUP (#9) NEW\nVBW]. The discontinued IV orders will display prior to taking action to \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nMail Groups Associated:\n \nfinish or edit the pending order. This will allow the pharmacist to pull \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- --------------------\nN/A\nIVs that are discontinued and prevent them from being sent to the patient \n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\n------------- --------------------\nN/A\n \n \nSecurity Keys Associated:\nward and potentially be given in error. It also allows the pharmacist to \n \nSecurity Key Name\n-----------------\nN/A\n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted \n------------- ---- ------------------ --------------------\nperform a drug-drug interaction check, since recently discontinued \nN/A\n \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\n----------------------------\n20131203 DISPLAY RECENTLY DISCONTINUED IV ORDERS\n\n
\nThis patch will resolve the following issue:\n \n1. Orders in the Inpatient Pharmacy package may not get their status \nupdated to expired if the order's STOP DATE/TIME value matches the start\ntime of the ORMTIME RUN background job. This is happening because ORMTIME\nRUN and the pharmacy code compare the expiration time differently. This\nis happening for all inpatient pharmacy package orders, but is\nparticularly prevalent with clinic medication and clinic infusion orders.\n\n
\nThis patch distributes routines that support the Application Package\n \n2829 The entry point EN^PSJBCMA1 is provided by Inpatient Medications\n to return detailed information on a patient's order for BCMA.\n \n2830 The entry point EN^PSJBCMA2 is provided by Inpatient Medications\n to return a patient order's activity logs for BCMA.\nInterfaces (APIs) between Inpatient Medications and Bar Code Medication\nAdministration (BCMA).\n \nThe following Database Integration Agreements (DBIA) describe these APIs:\n \n2828 The entry point EN^PSJBCMA is provided by Inpatient Medications\n to return a patient's active orders to BCMA to be used in\n administering medications at a patient's bedside.\n\n
\nThis patch will resolve the following issue:\n \n1) Pre-Exchange doses are incorrect when using Speed Finish\n\n
\nThis patch will resolve the following issues:\n \n1) Admin History report has wrong data (New opton AH)\n2) DOW VI order is printing one label too many\n3) Hard error when deleting AUTH ABS transfer\n4) Scheduled IV labels sometimes do not print\n\n
\nThis patch will resolve the following issues:\n Associated Ticket(s):\n \nIssue 4:\n--------\nI12228956FY17 "^" at Duration of Admin still allows order to \n continue\n \nProblem:\n========\nA user went to edit an active Transdermal Inpatient order, and the \nPharmacy Orderable Item is marked for PROMPT FOR REMOVAL IN BCMA (value \n============================\n2 or 3) and the Dosage form is Patch. During the edit of the verified \norder the user aborts ("^") at the Duration of Administration prompt \nafter entering the admin times. The system will allow the creation of \nthe new order without the Duration of Administration being entered.\n \nResolution:\n===========\nA modification to PSGOEE to prevent the user from continuing to create\na new order without the required Duration of Administration value.\n \nI9190964FY16 UNDEFINED error when renew is changed to copy an order\n \nIssue 5:\n---------\nI15018816FY17 UNDEFINED error in PSJDOSE when modifying Dosage.\n \nProblem:\n========\nAn active unit dose order in VistA was modified by changing the Dosage\nOrdered field. When the dosage options/selections appeared, the user\nopted to enter a free text dosage that exceeded 15 characters. This\nR11878202FY17 Unit dose order has zero for dosage.\nresulted in the UNDEFINED error.\n \nResolution:\n===========\nA modification was made to routine PSJDOSE to ensure that the user will\nno longer receive the UNDEFINED error. \n \nThis modification will send the user back to the dosage prompt if the value\nexceeds 15 characters.\n \nI8405721FY16 Copied UD order with >1 dispense drug, one inactive,\nIssue 6:\n---------\nI13103401FY17 Dispense drug not deleting correctly while finishing\n complex orders\n \nProblem: \n========\nAn Inpatient Med complex order was created in CPRS. While fiishing the order\nin Vista, the Pharmacist adds a new Dispense Drug (12) to the order then\ndeletes the original Dispense Drug. Once the order is completed and you \n copies incorrectly\ngo back into the order, both the new and deleted Dispense Drugs are displayed.\n \nResolution:\n===========\nA modification is needed in routine PSJCOM to update the NON-VERIFIED ORDERS\nFILE (53.1) with the new Dispense Drug information.\nI12228956FY17 "^" at Duration of Administration still allows\n order to continue.\nI15018816FY17 UNDEFINED error in PSJDOSE when modifying Dosage.\nI13103401FY17 Dispense drug not deleting correctly while finishing\n1) UNDEFINED error when renew is changed to copy of an order\n complex orders.\n \nAssociated NSR(s):\n==================\nN/A\n \nPSPO(s):\n========\nPSPO3491 - I13103401FY17\nTest Sites:\n2) Unit Dose order has zero for dosage\n===========\nTBD\n \nOverview:\n================\nIssue 1\n--------\nI9190964FY16 UNDEFINED error when renew is changed to copy an order\n \nProblem: \n3) Copied UD order with >1 dispense drug, one inactive, \n========\nA unit dose inpatient order in Vista was selected to be renewed (RN). At the\nSTOP DATE/TIME display the user realized they didn't want to renew the order\nbut to copy it. Entering an up-carat (^) at this point will take the user back\nto the originally selected order with no changes made. The user then enters CO\n(copy) and attempts to copy the order. During the copying process the user\nreceives the <UNDEFINED>INIT+58^PSJLMUDE error and is taken out of Vista. \n \nDuring the RENEW process some of the values in the INPATIENT USER PARAMETERS\nFILE (#53.45), which contain information about the displayed order, are killed\n copies incorrectly\noff. When the user decided/realized they wanted the order copied and not\nrenewed, some of the pertinent information that was removed was not getting set\nback into this file. This is the reason the user received the UNDEFINED error.\n \nResolution:\n===========\nA modification was made to MOVE^PSGOER to ensure that the INPATIENT USER\nPARAMETERS FILE (#53.45) is populated with all the correct information for\nprocessing.\n \n4) "^" at Duration of Admin still allows order to continue\nIssue 2\n--------\nR11878202FY17 Unit dose order has zero for dosage.\n \nProblem: \n========\nAn active unit dose order in Vista was modified by changing the Orderable\nItem. When this is done, both the Orderable Item and Dosage Ordered are \ndeleted. When entering the new Orderable Item, the user is not prompted \nfor the Dosage Ordered and is able to accept the order. This results in\n5) UNDEFINED AGAIN+26^PSJDOSE *PSJCONT\nthe new order being created without a Dosage Ordered.\n \nResolution:\n===========\nModifications were made to 4 routines, PSGOE8, PSGOE9, PSJDOSE & PSGOEE.\nThese modifications will prompt the user to enter a Dosage Ordered when\nthey change the Orderable Item.\n \n \nIssue 3\n6) Dispense drug not deleting correctly while finishing complex orders\n--------\nI8405721FY16 Copied UD order with >1 dispense drug, one\n inactive, copies incorrectly.\n \nProblem:\n========\nA Unit Dose order that has more than one Dispense Drug associated\nwith it, one being inactive, will not copy correctly. \n \nWhen the order is copies, the inactive Dispense Drug(s) are not\n \nsupposed to be copied to the new order. If the inactive Dispense\nDrug is the first one then the second Dispense Drug will show\non the new copied order twice. If the inactive Dispense Drug is\nlast it will show on the copied order.\n \nResolution:\n===========\nA modification was made to routine PSGOD to remove the inactive\nDispense Drug from the INPATIENT USER PARAMETERS FILE (#53.45).\n \n\n\nThis patch will resolve the following issues:\n \n1. Pending renewal shows dose of original order\n2. Clinic Order cross-references not being set correctly\n3. Major latency when running PSJ EXP on Clinics\n4. PADE TRANSACTION REPORTS WONT FIND CS DRUG TRANSACTIONS THAT ARE\n UNMATCHED TO THE NDF\n\n
\nThis patch will resolve the following ISSUE:\n \n When the PSJI BACKGROUND JOB runs, no report is produced.\n\n
\n1) Admin History report has wrong data (New opton AH)\n2) Hard error when deleting AUTH ABS transfer\n3) Scheduled IV labels sometimes do not print\n4) Scheduled IV labels are printing past the WL Stop date/time\n\n
\nThis patch addresses one (1) issue:\n be undertaken to place the old/stopped orders into expired status.\n \n1. Orders in the Inpatient Pharmacy package may not have had their \n status updated to "EXPIRED", in the past, if the order STOP DATE/\n TIME value matched the start time of the ORMTIME RUN background\n job. This happened because ORMTIME RUN and the pharmacy code \n compared the expiration time differently.\n \n This was corrected with patch PSJ*5*339, but a clean-up effort must\n\n
\nThis patch will resolve the following Issues:\n \n1) I9190253FY16 Order displayed twice after edit if you press return at\n QUIT.\n2) I11117041FY17 Accept order prompt duplicated on IV orders\n\n
\n1) There is an issue where the drug name is being stored for an \n intervention for Clinical Reminder and not the drug IEN.\n2) "Next Dose Due:" is displaying incorrectly when changing START \n DATE/TIME to NOW on an active order.\n\n
\n<UNDEFINED>109+1^PSGOE9\n\n
\n \nWPB-0398-3258\n1. This patch includes routines to reduce the number of variables in the\nuser's partition at the time order changes are communicated between\npharmacy and Computerized Patient Record System. These changes should\nreduce the likelihood of the user encountering an Allocation error during\nthe order processing functions.\n \n2. A change was made to correct an undefined variable error that occurred\nwhen finishing an order that was entered through the CPRS GUI. NOIS\n\n
\n1. This patch introduces changes to the patient and single order locking\n \nThe software will be modified to lock all external applications at the\norder level when an order is selected through Inpatient Medications for\nany action (Renew, Discontinue, Edit, Finish, Verify, Hold, Unhold, On\nCall, Mark Not to be Given, Mark Incomplete, New Order Entry, Copy, Speed\nFinish, Speed Renew, Speed Verify or Speed Discontinue).\n \nThe software will be modified to provide identification of any external\napplication users who are entering orders into the same patient record\naccessed by an Inpatient Medications application user processing orders\nbetween Inpatient Medications V. 5.0, Outpatient Pharmacy V. 7.0, and\nthrough Inpatient Medications V. 5.0 for actions generating a new order.\n \n \n2. Currently, Inpatient Medications V. 5.0 software performs order checks\nwhen a new medication order is placed through either the Inpatient\nMedications or Computerized Patient Record System (CPRS) applications.\nThe Pharmacy Benefits Management group requested that the Inpatient\nMedications application provide order checking for orders renewed through\nInpatient Medications or CPRS packages. This functionality will ensure the\nuser is alerted to possible adverse reactions and will reduce the\nComputerized Patient Record System (CPRS) V. 1.0.\npossibility of a medication error due to the omission of an order check\nwhen a non-active medication order is renewed. This patch will add this\nfunctionality.\n \nThe software will be modified to lock Pharmacy application users at the\npatient level when a medication order is selected through the Inpatient\nMedication V. 5.0 Unit Dose or IV menu options. This will prevent\nmultiple Pharmacy application users from processing medication orders for\nthe same patient at the same time.\n\n
\nMOCHA 2.1 Dosing Enhancements.\n\n
\nFollow up build to MOCHA 2.1b\n\n
\nThis patch addresses two (2) issues:\n Strength:400 MG"\n \n2. The "Expected First Dose" prompt in the Inpatient Pharmacy package \n New Order Entry option will display the incorrect calculated value if\n it is the second or subsequent order processed in a session when the \n second or subsequent order has a schedule greater than daily and the\n Start Date is in the future.\n \n1. The IV Additive Quick Code is not display the dosage and is showing \n up during process as Additive Strength: QC when it should be \n displaying as a Quick Code strength:nnn MG (where nnn is the strength\n of the quick code)\n \n Currently a quick code is showing up, for example, "Additive Strength:\n QC 1" The Quick Code, for example, should be displayed as "Quick Code \n\n
\nThis patch will resolve the following issue.\n \nI17870223FY18 - FRAMESTACK error\n\n
\n1) Special Instructions on edit not copying correctly\n2) Next Dose Due not displaying correctly\n\n
\nWard Stock display issues when there are multiple dispense drugs,\nnot all ward stock items.\n\n
\nThis patch will address 2 Inpatient Medications issues:\n1) <UNDEFINED> error when purging PRE-EXCHANGE NEEDS file.\n2) Ward field set to zero in Patient Pharmacy file for IV orders. \n\n
\nUNDEFINED error when running the PADE On-Hand Amounts or the PADE \nTransaction Reports\n\n
\nEmergency Patch to back out and replace VistA routine that\n \n1) INC1037196 \n \nEditing of verified inpatient medication orders with LONG special \ninstructions results in new order with missing special instructions.\n \nProblem: \n========\nEditing of verified inpatient medication orders that create new \nmedication order will replace any existing, long special instructions \ncaused an issue with long special instructions.\nwith text, "Instructions too long. See Order View or BCMA for full \ntext." Had patch installed this week that may be causing this new \nproblem, PSJ*5*361.\n \n \nResolution:\n===========\nCA-SDM I18645262FY18 fixed an issue whereby Special Instructions on\nedited orders were not copying correctly. It introduced this issue,\nhowever. The purpose of this patch is to return routine ^PSJBCMA5 to\n \npre-361 code.\nPatient Safety Issues (PSIs):\n-----------------------------\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n
\n1. The routine PSGOETO was issuing a lock command with a 0-second wait\nissued. This patch corrects this problem. NOIS MWV-0699-22220.\n \n3. Unit Dose orders were entered through Computerized Patient Record\nSystem (CPRS), but not signed or released. The patient was discharged,\nthen these Unit Dose orders were signed and released to the Inpatient\nMedications package. These orders were showing in the\nNon-Verified/Pending Orders [PSJU VBW] option when an order summary was\ndone under the ward group ^OTHER. The site could take no action on these\norders through the Inpatient Medications options. This patch will prevent\nthese orders from being accepted by the Inpatient Medications package and\nperiod. This resulted in a 100% CPU usage by the command because it was\nprevent this problem from taking place. NOIS MON-0699-52149.\n \n4. Medication orders were Dc'd on transfer, the transfer was deleted.\nThe orders were reinstated with the MailMan message going to the group\nand the pharmacist. Some duplicate orders were not reinstated. The\npharmacist tried to reinstate using the RN function in the long profile.\nThe user got the message that the order was reinstated, but it wasn't.\nThis patch corrects this problem. NOIS CON-0799-10709.\n \n5. A problem was reported with some reports when they were queued to the\nunable to attain the lock required. The CPU usage meant that other\nspooler. The following IV reports: \n \nACtive Order Report by Ward/Drug (IV) [PSJI AOR]\nAMIS (IV) [PSJI AMIS]\nDrug Cost Report (132 COLUMNS) (IV) [PSJI DRUG COST REPORT]\nPatient Cost Report (132 COLUMNS) (IV) [PSJI PATIENT COST]\nPRovider Drug Cost Report (132 COLUMNS) (IV) [PSJI PROVIDER REPORT]\nWard/Drug Usage Report (132 COLUMNS) (IV)[ PSJI WARD/DRUG USAGE REPORT]\n \nand the following Unit Dose reports\nroutines were prevented from processing. The timeout period for the lock\n \nExtra Units Dispensed Report [PSJU EUDD]\nMedications Due Worksheet [PSJ MDWS]\n \nwere not being processed to completion, resulting in the files never\nbecoming available to print. This patch corrects this problem. NOIS\nBRX-0398-12645, POR-0699-52667 and OKL-0899-70364.\n \n6. When printing the 7 Day MAR [PSJU 7D MAR] and the 14 Day MAR [PSJU 14D\nMAR] reports, the text for the Other Print Info was sometimes appearing in\nhas been amended to 1 second, this will allow other procedures to share\nthe Notes column. There was also a problem whereby the text of the Other\nPrint Info was not wrapping correctly if the text length was greater than\n47 characters. Also, if the order did not have a solution defined the\nlines were not wrapping correctly. This patch corrects these problems.\nNOIS IOW-0599-41089, MWV-0799-20528 and PUG-0899-52623.\n \n7. A problem was reported where a user accessed the option Extra Units\nDispensed [PSJU EUD] or Report Returns [PSJU RET] from the hidden menu\nand was unable to select orders greater then 13. The Help text for this\noption displayed when the user entered '??' was not appropriate either.\nthe system resources. NOIS SUX-0699-40661.\nThis patch will correct this problem. NOIS NHM-0699-10837.\n \n8. A problem was reported by a site where when running the option Extra\nUnits Dispensed [PSJU EUD] they were getting a message THIS DRUG IS AN ATC\nITEM. BUT THE ATC DEVICE CANNOT BE FOUND! This was happening on a ward\nthey had recently set up. This patch will correct this problem. NOIS\nCLE-0899-40919.\n \n9. A problem was identified whereby the option Patient Profile (Extended)\n[PSJ EXTP] was not displaying the full activity logs for orders. This\n \npatch will now correct this problem. NOIS SDC-0899-60673.\n2. When using the option Label Print/Reprint [PSJU LABEL] a line of text\nwould sometimes scroll off the screen when the prompt '^' TO QUIT was\n\n
\nFollow up build to MOCHA 2.1b\n\n
\nPatch reference and additional information may be found on Forum for \nPSJ*5*374.\n\n
\nThis patch addresses four (4) issues:\n \n3. A Non-Verified IV order was modified, a non-starred field, then \n another non-starred field was selected but the user cancelled the\n action (^). After the user Accepted the change the screen displayed\n the patient profile and not the accepted order to be verified.\n \n4. The verify action is not enabled immediately when a user accepts a \n unit dose order after verifying an iv fluid order for a different \n patient. Instead, the profile screen is displayed without the verify\n action.\n \n1. An UNDEFINED error is happening when copying a UD order, the user\n changes the Orderable Item but "^" out at the dispense drug selection\n all the way back to the profile, then picks another order to copy.\n \n2. A Clinic IMO order could not be processed. The site was turned off\n for Inpatient Meds between the time the order was placed and when it\n was processed by pharmacy.\n\n
\nThis patch will resolve the following issue.\nINC1065553 - BCBU MAR display NON transdermal patch orders with Removal\n times discharged/deceased\nINC0608952 - *TEST ACCOUNT-BCMA listing all admins as a patch-TEST ACCOUNT*\n(Duplicate)\n \nProblem: \n--------\nWhen Inpatient Pharmacy users use the option Inpatient Order Entry [PSJ OE]\nand instead of ordering a single medication choose an order set, there is a\npotential mix up between patch medications with other medications with a \n \ndifferent form of administration. Orders sets are created via the Order Set\nEnter/Edit [PSJU OSE] option. In some circumstances patch medications will\nnot have a field for entering removal times and other times medication with\nother forms of administration will prompt BMCA users for an application\nsite, which is required only for patch medications.\n \nResolution:\n-----------\nReset variables that identify patch medication versus non patch medication\nbefore processing each order within the order set. This will prevent orders\nINC1065553 - BCBU MAR display NON transdermal patch orders with Removal\nfollowing a patch medication order from being flagged as patch as well.\n \nTechnical Resolution:\n---------------------\nNEWed the variable PSGRF and ND2P1 variables at GND+1^PSGOES and set the \nvariable PSGRF with the content of the PROMPT FOR REMOVAL IN BCMA field (#12)\nin the PHARMACY ORDERABLE ITEM (#50.7) file, which is used to identify \nwhether form of application for the medication being entered is a patch.\n times discharged/deceased\nINC0608952 - *TEST ACCOUNT-BCMA listing all admins as a patch-TEST ACCOUNT*\n(Duplicate)\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n
\n1) Incomplete Medication Order Information\n2) Special Instructions lost when new order is created due to edit\n\n
\nThis patch will address three (3) INPATIENT MEDICATIONS issues:\n \n1)Users are encountering an UNDEFINED error when an active order is \ncopied and one of the order's fields is modified and the new order \nis made active.\n2)Complex orders are still locked after verification of all the child \norders.\n3)Complex orders are still locked when user is at SELECT ACTION QUIT \nprompt.\n\n
\nThis patch has the following enhancements for Clinical Ancillary Services\n \n2. Manage Hidden Icons (Actions) Inpatient \n \n Two new hidden actions are provided for Inptient Pharmacy's menu option\n Inpatient Order Entry [PSJ OE].\n \n a. New hidden action "DM" for displaying dispense drug information \n during data entry. This hidden action will display key information\n about the order to help aid in the verification process of an order\n and also allow user to Enter another drug if desired. Key\n(CAS) Enhancements (RXSU2).\n information includes:\n \n Example:\n \n DRUG NAME: xxxxxxxxxxxxxxxxxxx (IEN: 3)\n ORDERABLE ITEM TEXT:\n xxx xx xxxxx xxxxx xx xxxxx\n x xxxxxxxx xx xxxxxxxxxxxx\n \n MESSAGE: xxxx xxx xx xxxxx x xxxxxxxx\n \n QTY DISP MESSAGE: x xxxxxxxx xx xxxxxxxxx xxxx\n \n Return to continue or\n Select DRUG GENERIC NAME:\n \n b. New hidden action "VP" for displaying Provider information during \n data entry. This hidden action will display key information about\n the PROVIDER to help aid in the verification process of an order and\n also allow user to enter another provider if desired. Key \n information includes:\n1. Manage Lookup List Inactive Entries \n \n Example:\n \n PROVIDER TITLE: xxxxxx\n \n PROVIDER REMARKS: xxx xx xxxxxxx xxxx\n \n PROVIDER SPECIALTY: xxxxxx\n \n Return to continue or\n \n Select NEW PERSON NAME: \n \n \n3. View Provider Information\n \n Inpatient Pharmacy menu option Inpatient Order Entry [PSJ OE] header \n Listman areas were changed to add two new fields, 1) ATTENDING\n PHYSICIAN field (#.1041) and 2) TREATING SPECIALTY field (#.103) for\n both the Patient Information and Inpatient Order Entry Listman screens.\n \n Added the text "** INACTIVE **" to the end the display of\n Example Listman header screens:\n \n Inpatient Order Entry Jan 22, 2018@15:16:14 Page: 1 of 1\n INPATIENT,FIRSTNAME Ward: xxx xxxx\n PID: xxx-xx-xxxx Room-Bed: x-xxx Ht(cm): _____ (_____)\n DOB: xx/xx/xx (xx) Att: Physician,Attend S Wt(kg): _____ (_____)\n Sex: MALE TrSp: NEUROLOGY Admitted: xx/xx/xx\n Dx: TEST ICD CODE Last transferred: ********\n CrCL: <Not Found> BSA (m2): __________ \n -------------------------------------------------------------------------\n ADMINISTRATION SCHEDULE file (#51.1) entires while editting the Listman\n \n \n Patient Information Jan 25, 2018@15:09:18 Page: 1 of 1\n INPATIENT,FIRSTNAME Ward: xxx xxxx\n PID: xxx-xx-xxxx Room-Bed: x-xxx Ht(cm): _____ (_____)\n DOB: xx/xx/xx (xx) Att: Physician,Attend S Wt(kg): _____ (_____)\n Sex: MALE TrSp: NEUROLOGY Admitted: xx/xx/xx\n Dx: TEST ICD CODE Last transferred: ********\n CrCL: <Not Found> BSA (m2): __________ \n -------------------------------------------------------------------------\n screen field "8) Schedule:" during Finishing an order or adding a New\n Order in Pharmacy backdoor operations.\n\n
\nThis patch addresses one issue:\n \nPADE Dispense Without Order VistA Mailman messages not being received\n\n
\nMPDU - MEDICATION PERMISSIONS/DISPENSING UPDATES - Build 3\n 3. Prohibit Unintentional Reactivation/Inactivation of PADE Devices.\n \n \nItem 1\n------ \nProblem:\n-------\nI want the VistA system to use the exact time sent from the vendor system\nas long as it is no longer than 2 hours off of the time in VistA.\n \n \nResolution:\n----------\nLine tag FILETRAN^PSJPAD7I has been modified to allow a time gap of up to\n2 hours in the future, and if it is >2 hours then the transaction\ndate/time will be set to NOW Date/Time.\n \nItem 2\n------ \nProblem:\n-------\nThis patch will address the following issues.\nAs a PADE user, I want the value of the SEND CHECKIN/SURG HL7 FOR INPT to \nbe honored for admitted inpatients only so that check-in messages will \nalways be sent for non-admitted patients regardless of the parameter's \nvalue.\n \n \nResolution:\n----------\nLine tag CLCI^PSJPDCLA has been modified to block check-in/Surg HL7 \nmessages only if the patient is an inpatient and the flag SEND \n \nCHECKIN/SURG HL7 FOR INPT is not set to "Y".\n \n \nItem 3\n------ \nProblem:\n-------\nAs a user of the VistA PADE interface, I need the DISPLAY PADE INDICATORS \nIN IOE? prompt edit, through option 'PADE Inventory System Setup '(PSJ \nPADE INVENTORY SYSTEM), to not automatically reactivate devices that are \n 1. Timestamp Differential in VistA.\ncurrently inactive, or to inactivate devices that are currently active.\n \n \nResolution:\n----------\nLine tag PSJOE^PSJPADSI has been modified to not to execute the code (D\nDEVONOFF^PSJPDRU1) to reactivate/activate the devices automatically when\nstepping over the prompt DISPLAY PADE INDICATORS IN IOE? \nThe user will have the control to reactivate/inactivate a device.\n \n 2. Honor Value of SEND CHECKIN/SURG HL7 FOR INPT for Admitted patients \n only.\n \n\n
\n1. A problem was reported with the Patients on Specific Drugs report where\nof the other information from the quick code was entered into the order.\nThis patch corrects this problem. NOIS SDC-0699-61236\n \n3. A problem was reported when editing orders that are entered via unit\ndose order sets. During the order set entry, edits made after the order\nbecomes non-verified status are not being reflected in the CPRS order.\nThis patch will make changes to allow the edits of a non-verified order to\nbe reflected in the CPRS order if the edits are made before the\nnon-verified order is accepted. NOIS MIW-0899-40617\nif the patient received an outpatient IV order it would print the order\nwith the ward location and room-bed of their last admission. This patch\ncorrects this problem. NOIS MIW-0899-41313\n \n2. A problem was reported with the pharmacist finishing an order entered\nthrough Computerized Patient Record System (CPRS) Inpatient Medications\ndialogue. The pharmacist elected to finish the order as an IV and entered\na quick code at the additive prompt. The additive name was set, but none\n\n
\nThis patch addresses one issue:\n \nVistA IV Quick Code schedule issue\n\n
\nAs part of the Clinical Ancillary Services project (CAS) - Medication \n3. Check dosage form to determine appropriate default route\n4. Validate Termination of a Provider \n5. Addresses the defect reported in INC2806789 \nPermission/Dispensing Updates (MPDU), the Inpatient Medications package\nhas been modified to address the following:\n \nThis patch will address the following issues.\n \n1. Limit the Display of Medication Routes for Infusion Order Dialogs\n2. Limit the Display of Medication Routes for Inpatient Unit Dose Order\n Dialogs\n\n
\nThis patch addresses a PADE ROOM-BED/WARD issue.\n\n
\nThis patch will resolve the following issue.\n \nProblem: \n--------\nThe Robley Rex VA Medical Center reported that medication orders are showing\nstart date/times BEFORE the signature date/time of the order. This causes\nmeds to be due for administration in BCMA for a past time when the order did\nnot even exist. It appears as though patients are missing meds. Thus far\norders have been isolated to our 4S MED hospital ward and all identified\norders have been in the Unit Dose package.\n \n \nResolution:\n-----------\nThe primary reason the Robley Rex VAMC experienced this problem is because\nthe 4S MED was not configured in the Inpatient Ward Parameters Edit [PSJ IWP\nEDIT] option where the parameter DEFAULT START DATE CALCULATION used to\ncalculate the default start date/time for an order is set. The other reason\nis that once they processed two orders at the same time for the same ward\nthe default value for the parameter was getting overwritten when they tried\nto finish the second order. This patch corrects this issue. \n \nINC2264488 - Medication order start times and BCMA admin times are before the\nTechnical Resolution:\n---------------------\nChanged the line ENSD+99^PSGNE3 to check only the 5th piece of the PSJSYSW0\nvariable since it contains all ward parameters and after the user finished\nthe first order it was getting set with multiple up-carets ("^^^^^^^^^^"). \n date/time the order was signed\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC2264488 - Medication order start times and BCMA admin times are before the\n date/time the order was signed\n\n\nThis patch addresses the following.\n \nResults from LA7POC1 and LA7POC2 for iSTAT and \n Glucose testing are not going over to VISTA\n\n
\nCopied provider comments no longer display on the orders tab in CPRS when \npharmacist edits starred (*) field with Auto-Verify ON\n\n
\nWhen a user enters a complex order as a clinic order for an outpatient \nand edits a part (child) of the order after finishing that part of the \norder, the order displays as an inpatient medication instead of \ndisplaying as a clinic order.\n\n
\nThis patch addresses an issue where next cart exchange may be displayed \nalong with a value for Pre-Exchange DOSES erroneously with Clinic orders.\n\n
\nThis patch will put option PSJI DELETE ORDER out of order and correct an \nissue with NATURE OF ORDER for IV orders.\n\n
\n1. A problem was reported with a site that had pending order numbers\ngreater the 999999. This was causing a problem with the display and\nselection of the orders through Order Entry (IV) [PSJI ORDER]. This patch\ncorrects this problem. NOIS DEN-1299-50190.\n \n2. An undefined error occurred when reprinting IV labels. This error is\ndue to the change in FileMan patch DI*22.0*17 which returns a 0 to $T\nwhen using the ^DIC call. This patch will correct this problem. NOIS:\nIOW-1299-41969.\n\n
\nThe description of this build can be found in the National Patch Module\nunder PSJ*5*389.\n\n
\nMENTAL HEALTH NCC PROJECT 5.01\n\n
\nThis patch addresses 2 issues. 1) An issue with the Pre-Exchange\nDOSES for a clinic order when the clinic and the medication are tied to a\nPADE device. 2) Upon the entry of a date of death for a patient \nthe patient's active clinical orders (IMO) are not discontinued.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSJ*5*380.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSJ*5*392.\n\n
\nThis patch will fix the following issues:\n1) Correct an issue that occurs when the MED ROUTE is \n modified. It causes the ADMIN TIMES to disappear.\n2) Correct an issue that occurs when a starred field is\n edited in a complex order. User is getting knocked\n out of the system with a hard error.\n\n
\nThis patch will resolve the following issue.\nINC8364590 - VISTA option [PSJ PDV] "Patients on Specific Drug(s)" generates\n(Duplicate) hard error <SUBSCRIPT>IVSET+7^PSJPDV0 ^SC("")\n \nProblem: \n--------\nThe Syracuse VAMC Inpatient Pharmacy reported getting a hard error when\nrunning the Patients on Specific Drug(s) [PSJ PDV] report option for a \nspecific Division. It was reported as well that the error started happening\nafter the installation of patch PSJ*5*380. The HPS Sustainment Team confirmed\nthe problem to be caused by the code introduced by PSJ*5*380 to resolve a\n \ndifferent problem in the same report. The code did not take into account that\nnot all inpatient orders have a clinic associated with it and that is why the\nsoftware was throwing a <SUBSCRIPT> error.\n \nResolution:\n-----------\nThis patch fixes the code by skipping orders without a clinic when the user\nruns the report for a specific Division.\n \nTechnical Resolution:\nINC8260675 - New Patch PSJ*5*380 causing M error when running PSD report\n---------------------\nChanged the lines IVSET+7 and UDSET+7 in the PSJPDV0 routine to skip the order\nif the value of the field CLINIC (#130) in the UNIT DOSE sub-file (#55.06) or\nthe value of the field CLINIC (#136) in the IV sub-file (#55.01), both in the\nPHARMACY PATIENT file (#55), are blank and the report is being run for a\nspecific Division. \nINC8364590 - VISTA option [PSJ PDV] "Patients on Specific Drug(s)" generates\n(Duplicate) hard error <SUBSCRIPT>IVSET+7^PSJPDV0 ^SC("")\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC8260675 - New Patch PSJ*5*380 causing M error when running PSD report\n\n\nInpatient Med One-time Order not Discontinuing after Administering of \nMedication\n\n
\nThis patch will resolve the following issues:\n1) INC6081255 - BCMA scanning IV medication as invalid lookup\n \nProblem: \n-------\nThe VA Sierra Nevada Health Care System reported that BCMA IV piggyback label\nscanned as invalid look up when they should be valid. This happened when, for\nexample, an edit on the Volume of the solution on the order should have caused\nthe previously printed label(s) to be invalidated and new label(s) generated \naccording to the BCMA Parameters. New label(s) were generated for the edited\norder, however all labels (old and new) were being erroneously invalidated.\n \n \nResolution:\n----------\nThis problem happened because the software performs a date/time comparison\nbetween the Volume edit and the label creation to determine whether a label\nis valid or not. If the label was printed before the Volume edit the label is\nconsidered invalid. The problem is that it was using the format YYYMMDD.HHMMSS\nfor the Volume edit date/time and the format YYYMMDD.HHMM for the Label\ncreation date/time. So, if the new label(s) where printed within the same\nminute of the Volume edit the software mistakenly assumed the new labels were\nINC6081255 - BCMA scanning IV medication as invalid lookup\nprinted before the Volume edit.\n \nTechnical Resolution:\n--------------------\nChanged the code at EN+61 in the routine PSIVBCID to truncate the order edit\ndate/time to YYYMMDD.HHMM format when doing the comparison with the label\nprint date/time. This way labels printed after the order edit should never be\nconsidered invalid.\n \n \nINC6231181 - Over the last several months, there has been at least 5 times\nINC6231181 - Over the last several months, there has been at least 5 times\n that I am aware of where CPRS and BCMA aren't communicating on\n verification of order.\n \nProblem: \n-------\nThe Madison VA Hospital reported that the BCMA nurse verification information\nwas not being properly reset (removed) after the field SPECIAL INSTRUCTIONS\nwas edited by Inpatient Pharmacy users through the Inpatient Order Entry [PSJ\nOE] option. In CPRS the nurse verification is correctly being reset (removed)\nHITPS-6742 that I am aware of where CPRS and BCMA aren't communicating on\nafter this field is edited in Inpatient Pharmacy. According to the site this\nposes the risk of medication being administered through BCMA without the\nproper re-review and re-verification. This issue is also being considered a\nPatient Safety Issue (PSI) and the number assigned by the Patient Safety team\nis HITPS-6742.\n \nResolution:\n----------\nEvery time the SPECIAL INSTRUCTIONS field is edited for an inpatient unit dose\norder the nurse verification information (if any) will be invalidated/removed,\n verification of order.\nwhich will be reflected in the BCMA application. Depending on how the site \nBCMA parameters is set it will require a re-verification of the order in CPRS\nbefore it can be administered through the BCMA application.\n \nTechnical Resolution:\n--------------------\nCreated a new line tag in the routine PSJBCMA2 called RESETNV responsible for\nremoving the nurse verification information in the PHARMACY PATIENT file (#55),\nUNIT DOSE sub-file (#55.06), fields VERIFYING NURSE (#16) DATE VERIFIED BY\nNURSE (#17) and setting the NV FLAG field (#51) to 0 (NO). These fields are\n \nused by BCMA to determine whether an order have been verified or not by a\nnurse.\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n\n
\nThis patch will fix an issue where a subcomponent separator is not being\nconverted, by HL7 Standards, from & to \\T\\ when sending HL7 messages to \noutgoing PADE HL7 messages.\n \nPatch will also fix, when finishing a pending order from CPRS, as an IV \nmedication with no additive and a single solution that has Dose Limits\napplied to the Orderable Item file, that it honor that Dose limit and\ncalculate the correct Stop date/time for the order.\n\n
\n1. When entering unit dose orders through the pharmacy back door with an\n3. When printing a Medications Due Worksheet through the Medications Due\nWorksheet [PSJ MDWS] option, the user was receiving a divide by zero\nerror. This patch will correct this problem. NOIS NJH-0999-20805.\n \n4. An inconsistency was identified with the way in which Inpatient\nMedications was handling orders placed on hold through pharmacy options.\nOutpatient Pharmacy does not allow orders placed on hold through pharmacy\noptions to be released from hold using Computerized Patient Record System\n(CPRS) options. With the installation of this patch the same will be true\nfor Inpatient Medications.\norder set, 2 sets of labels were printed after the order is verified.\n \n5. The possibility exists for orders placed on hold to not have their\nstatus updated to expired and still show on the Inpatient Medications\nprofile and on the Active Orders tab through Computerized Patient Record\nSystem (CPRS) after the patient has been discharged from the hospital.\nThis patch will correct this problem. NOIS HUN-0999-22147.\n \n6. When entering a new Unit Dose order that contained a drug that is\nmarked for Unit Dose and Outpatient, an error was occurring when checking\nthe medical center's formulary. The drug was being checked to determine\nThis was incorrect, only one set of labels should be produced. This patch\nif the dispense drug was valid for the order but was using an invalid date\ncomparison. This patch will correct this problem. NOIS PUG-0999-51369.\n \n7. A site was assigning long room-bed names to their beds, the names were\nreaching 11 characters, the room-bed names were running into the patient\nnames when the site printed their pick list using the Pick List [PSJU PL]\noption. This patch corrects this problem. NOIS WNY-1099-10002.\n \n8. When finishing an IV order for the first time, the default for the\nadditive was display and the Stop date was calculated from the NUMBER OF\ncorrects that problem. NOIS MIW-0999-41081.\nDAYS FOR IV ORDER field (#3) in the IV ADDITIVES file (#52.6). If the\nuser did not accept the order and exited all the way to the patient prompt\nand selected the same order to finish again, the default additive will not\ndisplay and the Stop date was calculated from the IV ROOM file (#59.5).\nThis patch corrects this problem. NOIS: HUN-1099-20146. \n \n9. When finishing a Unit Dose order as an IV, the additive linked to the\ncorresponding IV Orderable did not display as a defaulted. This patch\nwill place a correct additive in the order. NOIS: RIC-1099-20942.\n \n2. Providers were unable to discontinue orders placed on-call through\npharmacy back door options using Computerized Patient Record System\n(CPRS) options. This patch corrects this problem. E3R 12975 and 12832.\n \n\n
\nPatch PSJ*5*366 introduced checks to verify that a user had sufficient \nprivileges to perform certain tasks. After the release of PSJ*5*366 \nan exception was discovered that prevented qualified users from \nperforming those tasks.\n\n
\nDosage changed on warfarin from 5mg to 3mg didn't fire a warning\nto the pharmacist finishing the order.\n \nClozapine complex order issue with stop date/time.\n \nBCMA Missed Med Report by CLINIC Gives Error Message "Unable to Reach \nVista"\n \nVista hard error with Unit Dose hidden option "OCI"\n\n
\nCorrect two routines so PADE HL7 messsages will be sent when complex \nmulti-line orders with "and" conjunctions are renewed by CPRS and \nfinished by VistA PSJ OE backdoor option.\n\n
\nIt was discovered that, in certain instances, when executing the option \nthat sends a clinic's patient orders to PADE (PADE Send Patient Orders), \na user receives the message 'Clinic is not setup for this PADE' for an\nactive client that is qualified to be selected.\n\n
\nThis patch, in conjunction with PSB*3*127, will resolve the following issue:\n \nProblem: \n--------\nThe VA North Texas Health Care System reported that when displaying and\nprinting patient order the print out includes removal times for medications\nthat does not require removal. The source of the problem was identified in\nthe schedule used for these orders. If it contains the ampersand character\n(&), e.g. AC&HS, it shifts fields within the HL7 message communicated between\nthe main VistA system and the BCBU workstation, which causes it to populate\nthe REMOVE TIMING field (#7.4) within the ORDER NUMBER sub-file (#53.701) in\n \nthe BCMA BACKUP DATA file (#53.7).\n \nSolution:\n--------\nChanged the building of the outbound order HL7 message from VistA to the BCBU\nworkstation to escape the schedule field value before including it in the HL7\nmessage and also changed the processing of the incoming message to un-scape\nthe schedule field value before parsing it at the BCBU workstation. \n \nTechnical Resolution:\n1) INC11397447 - BCMA Backup workstation patient print out and order display\n---------------------\nThis patch changes the routine PSJHL3 at line tag RXE+39 and IVRXE+7 to escape\nthe schedule field value before including it in the outbound HL7 message sent\nto the BCBU workstation. \n removal times for INHALATION Medications\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC11397447 - BCMA Backup workstation patient print out and order display\n removal times for INHALATION Medications\n\n
\n \n \n 'Out Of Order':', press the Enter key.\n \n b. When prompted 'Enter protocols you wish to mark as \n 'Out Of Order':', press the Enter key.\n \n c. When prompted 'Delay Install (Minutes): (0 - 60): 0//',\n answer 0.\n \n \n \n \nBack-Out/Roll Back Plan:\n------------------------\n \nPost Installation Instructions:\n-------------------------------\nNone.\n \nInstallation Verification:\n--------------------------\nSuccessful installation can be verified by reviewing the first 2 lines \n \nof the routines contained in the patch. The second line will contain the \npatch number (413) in the [PATCH LIST] section.\n \n ;;5.0;INPATIENT MEDICATIONS;**[PATCH LIST]**;16 DEC 97;[BUILD #]\n \nThe option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run \nto compare the routine checksums to what is documented in the patch\ndescription.\n \nBack-out/Rollback Strategy:\n \n---------------------------\nBack-out will be done only with the concurrence and participation\nof development team and appropriate VA site/region personnel. The\ndecision to back-out or rollback software will be a joint decision\nbetween development team, VA site/region personnel and other\nappropriate VA personnel.\n \nPrior to installing an updated KIDS package, the site/region should\nhave saved a backup of the routines in a mail message using the\nBackup a Transport Global [XPD BACKUP] menu option (this is done at\n \ntime of install). The message containing the backed-up routines can\nbe loaded with the "Xtract PackMan" function at the Message Action\nprompt. The Packman function "INSTALL/CHECK MESSAGE" is then used\nto install the backed-up routines onto the VistA System. \nNo data was modified by this patch installation and, therefore, no \nrollback strategy is required.\n \nValidation of Back-out Procedure\n---------------------------------\nThe Back-out Procedure can be verified by printing the first 2\n \nlines of the PSJ Routines contained in this patch using the option\nFirst Line Routine Print [XU FIRST LINE PRINT]. Once the routines\ncontained in the PSJ*5.0*413 patch have been rolled back, the first\ntwo lines of the Routines will no longer contain the designation\nof patch PSJ*5.0*413 in the patch list section on line 2\n \n \nWhen changing the clinic location in CPRS and then renewing a clinic \norder, PRS and backdoor Inpatient Pharmacy is still displaying the old\nThis patch will resolve the following issue:\nclinic order. This is incorrect. The clinic is updated in File #53.1 \nbut not in File #55\n \nResolution:\n-----------\n \nA modification was made in routine PSGOTR to update FILE 55 from FILE \n53.1 during the verification process, this will display the correct \nClinic location in CPRS and backdoor Inpatient Pharmacy. \n \n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nPHARMACY PATIENT (55) CLINIC(130) Modified\n \nTest Sites:\n-----------\nTBD\n \nSoftware and Documentation Retrieval Instructions:\n--------------------------------------------------\nINC12424796 - Renewing a clinic order still showing the old clinic \nThe software for this patch is being released in a PackMan message.\n \n \nPatch Installation:\n-------------------\n \nPre-Installation Instructions:\nThis patch may be installed with users on the system although it is\nrecommended that it be installed during non-peak hours to minimize\npotential disruption to users. This patch should take less than 5 \nlocation\nminutes to install.\n \n \nInstallation Instructions:\n \n1. Choose the PackMan message containing this build. Then select \n the INSTALL/CHECK MESSAGE PackMan option to load the build.\n \n \n2. From the Kernel Installation and Distribution System Menu, \n in CPRS and backdoor Inpatient Pharmacy \n select the Installation Menu. From this menu, \n \n A. Select the Verify Checksums in Transport Global \n option to confirm the integrity of the routines that \n are in the transport global. When prompted for the \n INSTALL NAME enter the patch or build name. \n (ex. <PSJ*5.0*413)\n \n NOTE: Using <spacebar><enter> will not bring up a \n Multi-Package build even if it was loaded \n \n immediately before this step. It will only \n bring up the last patch in the build.\n \n B. Select the Backup a Transport Global option to create a \n backup message of any routines exported with this patch. \n It will not backup any other changes such as DDs or \n templates. \n \n C. You may also elect to use the following options: \n i. Print Transport Global - This option will allow \n \n you to view the components of the KIDS build.\n ii. Compare Transport Global to Current System - This \n option will allow you to view all changes that will \n be made when this patch is installed. It compares \n all of the components of this patch, such as \n routines, DDs, templates, etc.\n \n D. Select the Install Package(s) option and choose the \n patch to install. \n \n \n i. If prompted 'Want KIDS to Rebuild Menu Trees Upon \n Completion of Install? NO//', answer NO.\n \n ii. When prompted 'Want KIDS to INHIBIT LOGONs during the \n install? NO//', answer NO.\n \n iii. When prompted 'Want to DISABLE Scheduled Options, Menu \n Options, and Protocols? NO//', answer NO \n \n a. When prompted 'Enter options you wish to mark as \n\n
\nSee patch description for PSJ*5.0*411.\n\n
\nWhen a provider chooses a schedule of WEEKLY or MONTHLY in VistA the \nHL7 data sent to the Omnicell reflects that this drug should be given on \nWednesday or Monday instead of the actual day the order was entered. See\nthe patch description on FORUM for more details.\n\n
\n1. When printing MARs on a DSM system, a problem was encountered with the\n \n3. Currently, if a unit dose order has multiple dispense drugs, the order\ncheck is performed for the first dispense drug only. With this patch, any\nadditional dispense drugs entered for the order will be checked for\nallergies and drug-drug interactions. This will apply to new orders\nentered using the Inpatient Order Entry [PSJ OE] or Order Entry [PSJU NE]\noptions and when finishing pending unit dose orders or renewing unit dose\norders.\n \n4. A problem was reported with trying to enter a new intervention from\nuse of the positioning command (?) and the subsequent layout of the MAR\nthe Pharmacy Intervention Menu [PSO INTERVENTION MENU] through List\nManager. The user selected the Enter Pharmacy Intervention [PSO\nINTERVENTION NEW ENTRY] option, tried to enter a new intervention,\nreceived two question marks and was unable to do so. On the protocol [PSJ\nLM INTERVENTION NEW ENTRY],in the entry action, DLAYGO was being set to\nthe wrong file number. This patch corrects this problem. \nNOIS BHH-1099-42026.\n \n5. The user was required to enter an IV room when using the IV options\neven though there is only one active IV room defined. This patch will\ndata. This patch resolves that problem. NOIS MOU-1099-31155.\nautomatically select the active IV room. NOIS HUN-1099-22843.\n \n6. If the field DAYS TO RETAIN IV STATISTICS (#31)is not set in the \nPHARMACY SYSTEM file (#59.7), the stop date is not calculated correctly\nwhen finishing the order as a Chemotherapy IV TYPE. This patch will fix\nthis problem.\n \n2. A problem was reported with the display of a pending order when using\nthe option Patient Profile (Extended) [PSJ EXTP]. The order would display\nwith the patient's name and the status of Not Verified, the rest of the\norder information would display as NOT FOUND or *s. This patch corrects\nthis problem. NOIS ISH-1099-41686.\n\n
\nThis patch will resolve the following issue:\n-------\nThe Dallas Field Office reported that BCMA MEDICATION LOG file (#53.79) does\nnot get updated properly when 2 patients are merged. More specifically, the\nORDER REFERENCE NUMBER field (#.11), which contains a pointer to UNIT DOSE\n(#55.06) and IV (#55.01) sub-files in the PHARMACY PATIENT file (#55) does \nnot get updated with the new pointers when the entries in these two sub-files\nare moved to a different IEN (Internal Entry Number). In some rare cases, this\nwill cause the BCMA Medication History Reports to hide one of the orders for \nthe newly merged patients if both patients had the orders of the same type\n(UD/IV) with the same pointer and were administered on the same day.\n \n \nResolution:\n----------\nIt was confirmed that the patient merge updates did not update the BCMA\nMEDICATION LOG file (#53.79) entries when the IENs for UD/IV orders in the\nPHARMACY PATIENT file (#55) were changed. The code was correct to correctly\nupdate the BCMA MEDICATION LOG file (#53.79), ORDER REFERENCE NUMBER (#.11)\nwhen two patients are merged.\n \nTechnical Resolution:\nINC9104304 - Patient Merge is incorrectly merging BCMA MED LOGS\n--------------------\nAdded a new line tag at the end of the routine PAJPATMR called UPDBML to\nupdated the ORDER REFERENCE NUMBER field (#.11) on the BCMA MEDICATION LOG\nfile (#53.79) file for all administrations right after the new IEN is assigned\nto UD/IV orders. In addition, the code in UPDBML will kill the old (From) and\nset the new (To) cross-references "AADT", "AEDT" and "AOIP" because it was\ndetermined that the Patient Merge routines did not update them either.\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC9104304 - Patient Merge is incorrectly merging BCMA MED LOGS\n \nProblem: \n\n
\nBackup of PSJ*5.0*415 on Jun 17, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will address the following INPATIENT MEDICATIONS issues:\n \n 1) INC16500339 - PADE WILDCARD CLINIC NAME SEARCH ISSUE\n 2) INC16774550 - PADE ON HAND QTY NOT DISPLAYING \n\n
\nBackup of PSJ*5.0*414 on Jun 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses the following issue:\n \nOrder status mismatch between CPRS and Inpatient Order Entry (PSJ OE)\nafter order verified\n\n
\nBackup of PSJ*5.0*364 on Jul 13, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSJ*5.0*364.\n\n
\nBackup of PSJ*5.0*418 on Jul 16, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will resolve the following issue:\n \nProblem: \n-------\nThe Togus VA Medical Center reported a problem with the Activity Log after\nediting the Stop Date/Time on an IV order using the Inpatient Order Entry [PSJ\nOE] option. After they edited the Stop Date/Time field if correctly created a\nnew order, however the Activity log for the original/discontinued order showed\na 'Changed From' value equal to the new Stop Date/Time entered by the user\ninstead of the original Stop Date/Time before the order was edited. Below is a\ncapture of the Activity Log display showing the problem:\n \n \n ...\n # MMM DD,YYYY HH:MM:SS EDIT USER,NAME\n Comment: Order discontinued due to edit\n \n Field: 'STOP DATE/TIME'\n Changed from: 'MMM DD,YYYY HH:MM' <<< New Stop Date/Time (wrong)\n To: 'MMM DD,YYYY HH:MM' <<< Current Date/Time (correct)\n ...\n \n1) INC16771491 - Activity Log shows wrong 'Changed from' value when Stop\nResolution:\n----------\nAfter a few tests it was identified that the software was indeed using the\nwrong value for the Stop Date/Time when recording the 'Changed From' value in\nthe Activity log of the original/discontinued order when the Stop Date/Time\nwas edited by the user. A change was made to use the original Stop Date/Time\nvalue from the orignial order instead of using the new Stop Date/Time entered\nby the user for the new order.\n \nTechnical Resolution:\n Date/Time field is edited and Order is DC'd\n--------------------\nThe Activity Log entry is recorded by the code in STOP^PSIVORAL. It used the\nvalue in the P(3) array variable to compare against the value in the order to\nidentify whether the field had been changed or not and also used this value to\nrecord the 'Changed from' value in case it determines it was changed. The\nproblem happened because the value in the P(3) array variable contained the\nStop Date/Time value for the new order and not the original value (before the\nuser edited). The code was changed to use the value from the ORIGINAL STOP\nDATE field (#116) in the IV sub-file (#55.01) in the PHARMACY PATIENT file\n(#55) for DC'd orders as the 'Changed From' value instead of the value in the\n \nP(3) array variable.\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC16771491 - Activity Log shows wrong 'Changed From' value when Stop\n Date/Time field is edited and Order is DC'd\n\n
\nBackup of PSJ*5.0*417 on Aug 12, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nY2K Waiver Exemption ID#: Y2KWE0026\nand IV multiples. In order for this patch to function as intended the\nsite will need to load the Kernel Toolkit patch XT*7.3*45.\n \n \n \n \n********************************NOTE**************************************\nWithout the Kernel Toolkit patch XT*7.3*45 nothing will be done to clear\nup these data exceptions in the PHARMACY PATIENT file (#55) specifically\nthe Unit Dose and IV multiples.\n==> This patch may be installed during the Y2K Moratorium.\n**************************************************************************\n \n This patch addresses unique issues involved in the patient merge\nprocess. Some sites were unable to merge duplicate patients due to data\nexceptions. This patch provides the patient merge software with an API to\ncall before the package begins it data validation of the FROM and TO\nrecords of the duplicate patients to clear up some of these data\nexceptions in the PHARMACY PATIENT file (#55) specifically the Unit Dose\n\n
\nDefect Tracking System Ticket(s) & Overview:\n The function to specify number of doses in the stop date field is \n Calculating incorrect; it is one dose short. \n \n When entering a dose limit for an outpatient unit dose clinic \n medication, the stop date calculated is at the date/time of the last\n dose to be administered. That last dose cannot be administered at the\n time the order is defined to stop. The stop date/time should be\n calculated to be after the last dose to be administered.\n \n Resolution:\n===========================================\n ----------\n Modify routines PSGDL & PSJORP2 so that the date/time of the first \n dose is used to determine the stop date/time using the dose limit \n entered. Prior to this patch the outpatient clinic order was using \n the current time to calculate the dose limit entered to get the stop \n date/time which would come up with one dose less than the dose limit \n entered. This patch makes the outpatient dose limit function the \n same as for an inpatient clinic med is entered when the INPATIENT \n WARD PARAMETERS (File #59.6) field DEFAULT START DATE CALCULATION \n is set to 2. With this patch inpatient clinic meds will calculate \n \n out the to the correct dose limit entered regardless of the DEFAULT \n START DATE CALCULATION parameter value.\n1. INC17067067 VISTA Inpatient Pharmacy error with clinic orders and \nstop dates\n \n Problem:\n -------\n The issue is seen with "outpatients" and unit dose clinic medications. \n\n
\nBackup of PSJ*5.0*419 on Aug 23, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will resolve the following issues:\n Medication Administration (PSB)\n Duplicate:\n -----------\n INC17559434 - IV bolus orders showing verified in CPRS but not BCMA\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC11926924 - MAD: PSJ*#*### not resolve: order appeared verified by nurse\n in BCMA but CPRS it was found not to be. \nProblem: \n \n-------\nThe William S. Middleton Memorial Veterans Medical Center Affairs Hospital \nreported that the BCMA nurse verification information was not being properly\nreset (removed) after the field DISPENSE DRUG was edited by Inpatient Pharmacy\nusers through the Inpatient Order Entry [PSJ OE] option. In CPRS the nurse\nverification is correctly being reset (removed) after any of the Dispense Drug\nfield is modified. There was an expectation from the site that PSJ*5*397 would\naddress this problem, however that patch addressed only edits to the SPECIAL\nINSTRUCTIONS field, not the DISPENSE DRUG field. This issue is also being\nconsidered a Patient Safety Issue (PSI) and the number assigned by the Patient\n1) INC11926924 - MAD: PSJ*#*### not resolve: order appeared verified by nurse\nSafety team is HITPS-7361.\n \nResolution:\n----------\nEvery time an order update is received from CPRS by Inpatient Pharmacy the\nNurse Verification information (if any) will be invalidated/removed before\nupdating the incoming data from CPRS. In case CPRS sends new Nurse Verification\ninformation with the order the information will be updated in Pharmacy order \nfiles, which will be reflected in the BCMA application. Depending on how the \nsite BCMA parameters is set it will require a re-verification of the order in\n HITPS-7361 in BCMA but CPRS it was found not to be.\nCPRS before it can be administered through the BCMA application.\n \nTechnical Resolution:\n--------------------\nChanged the routine PSJHL4 at line tag ORC+6 and included code to delete/remove\nthe nurse verification information from the PHARMACY PATIENT file (#55) every\ntime an update is received from CPRS. Also, the changes introduced in the\nroutine PSJBCMA2 by PSJ*5*397 to address the incident INC6231181 (HITPS-6742)\nhave been removed because this new change will better address that issue as\nwell. A global hard-setting approach was used to avoid some updates from\n \noccurring through Mumps trigger cross-references.\n \n2) INC12777528 - BCMA shows medication as not nurse verified, CPRS shows it as\n verified \nProblem: \n-------\nThe Minneapolis VA Health Care System reported that a medication order shows\nas requiring nurse verification in BCMA while CPRS shows the order have been\nnurse verified. After some research it was determined that the BCMA and CPRS\nwere out of sync regarding the nurse verification due to a hard error <SYNTAX>\n2) INC12777528 - BCMA shows medication as not nurse verified, CPRS shows it as\nthat happened when the Special Instructions field is edited for a complex\norder and a semi-colon character (;) was included in the instructions.\n \nResolution:\n----------\nThe code was changed to prevent the hard error <SYNTAX> whenever the user\nincludes a semi-colon (;) in the Special Instructions field for complex \norders.\n \nTechnical Resolution:\n verified \n--------------------\nChanged the routine PSGOEE at line tag UPD+23 to perform a direct global set\nfor the content of the SPECIAL INSTRUCTIONS file (#8) in the UNIT DOSE sub-\nfile (#55.06) in the PHARMACY PATIENT file (#55) instead of using the Fileman\nDIE API. This code is used to copy the Special Instructions field content\nfrom one order to the other orders after edits in the case of complex orders.\n \n3) INC17553085 - Error in MIN VistA: RPC+##^PSBCHKIV *PSBIVCHG BarCode\n Medication Administration (PSB)\nProblem: \n \n-------\nBoth test sites for PSJ*5*409 (Minneapolis and Madison) reported a hard error\nafter the patch was released. It was confirmed the error was a direct side\neffect of the changes in PSJ*5*409 and that's the reason that patch was\nrecalled (marked ENTERED IN ERROR on FORUM). It created some incomplete \nActivity Log records in the IV ORDER multiple (#55.01) of the PHARMACY \nPATINT file (#55) and that's what caused the error. \n \nResolution:\n----------\n3) INC17553085 - Error in MIN VistA: RPC+##^PSBCHKIV *PSBIVCHG BarCode\nThe code in the routine PSJHL4 added by PSJ*4*409 was changed from using\nFileman ^DIE API call to doing a direct (hard-setting) global setting which\nprevents some Mumps cross-references from setting the corrupt entries in the\nIV Activity Log.\n \nTechnical Resolution:\n--------------------\nThe code in the line tag ORC+6 was changed from using a ^DIE call to \nperforming direct sets to remove the nurse verification for the order.\n\n
\nThis patch will resolve the following issue:\n \nProblem: \n--------\nThe West Haven VA Medical Center reported that whenever they tried to finish\nan Intravenous (IV) clinic order for an patient not admitted (outpatient)\nusing the Inpatient Order Entry [PSJ OE] option it did not warn the user that\nthe clinic for the order is not setup for BCMA (shown below). For a Unit Dose\n(UD) clinic order the option properly displayed the warning below:\n \n Clinic CHY AQUATIC EXERCISE is not defined in the CLINIC DEFINITION\n \n (#53.46) file.\n \n This order will NOT display in BCMA, unless the clinic is defined in the\n CLINIC DEFINITION (#53.46) file, and the SEND TO BCMA (#3) field is set\n to YES.\n \n Please contact your Pharmacy ADPAC.\n \n Note: This issue is also being considered a Patient Safety Issue (PSI) and\n the number assigned by the Patient Safety team is HITPS-8005.\n1) INC18070852 - Clinic Not Setup for BCMA Issue not firing for IV orders\n \nResolution:\n----------\nIt was confirmed that the warning only displayed for UD clinic orders and not\nfor IV clinic orders. The code was changed to also perform the check for IV\nclinic orders during finish and it will now display the message above when\nnecessary.\n \nTechnical Resolution:\n--------------------\n HITPS-8005 \nThe ENTRY ACTION field for the protocol PSJI LM FINISH did not contain a call\nto the API CWARN^PSJBCMA6 responsible for performing the check mentioned\nabove. The ENTRY ACTION field was modified the following way:\n \n Before:\n -------\n S PSJINFIN=1 K ^TMP("PSJINTER",$J) D OVRDISF^PSGSICH2($G(DFN),$G(PSJORD),2)\n D FINISH^PSJLIFN D SETIVINT^PSGSICH1\n \n After:\n \n ------\n S PSJINFIN=1 K ^TMP("PSJINTER",$J) D CWARN^PSJBCMA6($G(DFN),$G(PSJORD)),\n OVRDISF^PSGSICH2($G(DFN),$G(PSJORD),2) D FINISH^PSJLIFN D SETIVINT^PSGSICH1\n \nPatient Safety Issues (PSIs):\n-----------------------------\nHITPS-8005\nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC18070852 - Clinic Not Setup for BCMA Issue not firing for IV orders\n HITPS-8005 \n\n\nThe description of this build can be found in the National Patch Module \nunder PSJ*5.0*425.\n\n
\n \nINC1167333 Issue with Editing/Coping Other Print Info (field 11) of the \nComplex Order in PSJ OE\n\n
\nThis patch will resolve the following issues:\n1) INC17689657 - Schedule of SUPPER looks correct in Vista, but the HL7\n ===========================================================================\n This patient is already receiving the following INPATIENT and/or OUTPATIENT\n order(s) for a drug in the same therapeutic class(es) as WARFARIN 2MG TAB\n U/D: \n \n Clinic Order: WARFARIN TAB (PENDING)\n Schedule: BID\n Dosage: 7MG\n Requested Start Date: JUN 05, 2021@09:00\n Stop Date: ********\n HITPS-7946 message for medication order is for Sundays only instead\n \n Class(es) Involved in Therapeutic Duplication(s): Oral Anticoagulants,\n Antiplatelet Drugs-excluding ASA 325 mg and below, Antiplatelet\n and Antithrombotic Drugs (Selected Group 2) \n ===========================================================================\n ...\n \nTechnical Resolution:\n--------------------\nCreated a local API called $$CLNORDDN in the routine PSJCLNOC to return the\n of daily\ndrug name for a pending clinic order. If the clinic order has a selected \ndispense drug selected the name for the dispense drug will be returned by the\nAPI, if not, the API will retrieve the orderable item name and dosage form\nand will concatenate them and return as the name to be used for drug-drug or\nduplicate order check messages. Then changed code in DISP2+13 to use this API\nfor displaying the clinic order drug name.\n \nPatient Safety Issues (PSIs):\n-----------------------------\nHITPS-7946 (INC17689657)\nProblem: \n--------\nThe WM Jennings Bryan Dorn VA Medical Center reported that whenever they \nentered an inpatient order with the schedule SUPPER it looked and behaved\ncorrectly in VistA, however the HL7 message sent to PADE contained the wrong\nvalue for the 8th (~) field in the RXE segment which is used for 'Day-of-Week'\nschedules. Each digit represents one day of the week starting with Sunday thru\n \nSaturday. The code wrongly interpreted SUPPER as SU (short for Sunday) and\nset the first digit to 1 which was interpreted by the automated dispensing\ncabinets as once every Sunday. This issue is also being considered a Patient\nSafety Issue (PSI) and the number assigned by the Patient Safety team is\nHITPS-7946.\n \n ...\n ORC|NW|100034|27U||CM||||202105280839|520824666~TEST~OUTPAT~F|520824666~TESO\n RXE|240~SUPPER&1900~~2021052808~20210627180~~0~10000000|841~DOCUSATE CA 240M\n RXR|PO~ORAL~99PSR\n1) INC17689657 - Schedule of SUPPER looks correct in Vista, but the HL7\n ...\n \nResolution:\n----------\nPatch PSO*7*405 addressed a similar issues for schedules WEEKLY and MONTHLY,\nwhich were both interpreted as WE (Wed) and MO (Monday). Instead of fixing\njust specific instances of samples that can create the problem the solution\nwill not try to translate any other schedule that does not match one of the\nfollowing: SU, MO, TU, WE, TH, FR and SA. In addition, it will require for\nall schedules separated by dashes (e.g., MO-WE-FR) that all pieces match one\n HITPS-7946 message for medication order is for Sundays only instead\nof the week days abbreviation. If this condition is not met, the software will\nsend all zeros (00000000) to PADE for the order.\n \nTechnical Resolution:\n--------------------\nThe logic for the $$DOWSTR API in the routine PSJPDCLV was completely\nre-written to exclude any schedule as day-of-week schedule unless all the\ndash (-) pieces in the schedule match one of the seven days abbreviation: SU,\nMO, TU, WE, TH, FR and SA. If any value is different than one of these \nabbreviations the processing stops and 00000000 is returned.\n of daily\n \n2) INC17223279 - clinic order allergy alert choosing dispense drug\n \nProblem: \n-------\nThe Martinez VA Medical Center reported that When finishing a clinic order\nwithout a chosen dispense drug the duplicate drug alert is randomly selecting\na dispense drug associated with the Orderable Item and displaying it as the\ndispensed drug associated with the pending order, which is incorrect. In other \nwords, when you have a pending clinic order without a dispense drug selected\n2) INC17223279 - clinic order allergy alert choosing dispense drug\nand you try to finish or enter a new order through the Inpatient Order Entry\n[PSJ OE] option or that will cause a duplicate order check or a drug-drug\norder check the drug name displayed for the pending clinic order is misleading\nbecause it arbitrarily selects one of the drugs associated with the Orderable\nItem on the order (apparently the last one) and displays it as the actual drug\nfor the clinic order. In the example below, when the user tried to enter or\nfinish an order for WARFARIN 2MG TAB the pending clinic order in the duplicate\ndrug check below shows the dispense drug WARFARIN 7.5MG TAB U/D, however the\npending clinic order does not have any dispense drug selected.\n ...\n \n Now Processing Enhanced Order Checks! Please wait...\n \n Press Return to continue...\n ===========================================================================\n This patient is already receiving the following INPATIENT and/or OUTPATIENT\n order(s) for a drug in the same therapeutic class(es) as WARFARIN 2MG TAB\n U/D: \n \n Clinic Order: WARFARIN 7.5MG TAB U/D (PENDING)\n Schedule: BID\nDefect Tracking System Ticket(s) & Overview:\n Dosage: 7MG\n Requested Start Date: JUN 05, 2021@09:00\n Stop Date: ********\n \n Class(es) Involved in Therapeutic Duplication(s): Oral Anticoagulants,\n Antiplatelet Drugs-excluding ASA 325 mg and below, Antiplatelet\n and Antithrombotic Drugs (Selected Group 2) \n ===========================================================================\n ...\n \n--------------------------------------------\nResolution:\n----------\nThe displaying of a pending clinic order was changed to display only the \nOrderable Item name and its dosage form when the order does not have a\ndispense drug selected. Below is how the same duplicate order check above\nwill display after the patch is installed:\n ...\n Now Processing Enhanced Order Checks! Please wait...\n \n Press Return to continue...\n\n
\nDescription:\n inpatient medication order queue\n (Non-Verified/Pending Orders)\n INC17772912 (Duplicate) - delays with Pending Inpatient Orders \n2. INC17835358 - Non-verified/pending orders summary not accurate\n3. INC17835358 - Clinic Meds are not being counted under Clinic \n location\n============\n \nThis patch addresses the following issues:\n \nAssociated ticket(s):\n=====================\n \n1. INC15531625 - Pharmacy Package Delay in pulling up the pending \n\n
\nThis patch addresses the following issue:\n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \nPatient Safety Issues (PSIs):\n \n=============================\nHITPS-8027\n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. Patch Medication Renewal Issue\n \n Problem:\n1. Patch Medication Renewal Issue\n -------\nInpatient patch medication renewals display an incorrect administration \ntime. When renewing an order in CPRS that has a schedule to give every x \nnumber of days, the expected first dose may display the incorrect date. \nThe issue is seen when renewing in CPRS and when processing the order in \nInpatient Order Entry, the user selects to edit the Admin Time before \naccepting it. \n \n \n Resolution:\n \n ----------\nThe problem is that the start date of the original order doesn't exist \nduring pharmacy processing. This is due to the original start in the \nNON-VERIFIED ORDERS file #53.1 not being filed correctly when renewing in \nCPRS. The order is finished correctly with appropriate start and stop \ndates and the only issue appears to be that the expected first dose \ndisplays with a wrong date. The issue is also only seen when renewing \nthe order at a time of day prior to the admin time. The correction is to \nmodify routine PSJHL7 so that the original start date and stop time is \nfiled to the NON-VERIFIED ORDERS file #53.1. Previous to this patch the \nAssociated ticket(s):\nSTART DATE/TIME & STOP DATE/TIME were set to null by RENEW^PSJHL7.\n \n \n Technical Resolution:\n ---------------------\nCode changes to PSJHL7:\n - Added newing of PSGNESD & PSGNEFD at RENEW+1\n - Set PSGNESD to $P(ND2,U,2) and PSGNEFD=$P(ND2,U,4) at RENEW+6\n - Removed setting PSGNESD & PSGNEFD to null at RENEW+12\n=====================\n \n1. INC18413351 - Patch Medication Renewal Issue\n \n\n
\n \nfluid order. "ADMIXTURE" will be the default IV TYPE. E3R #11576.\n \n3. The "*" sometime displayed next to the Start and Stop dates even\nthough no new order is created. This patch will correct this problem.\n \n4. For IV orders entered with schedules like QOD, Q48H and Q72H, labels\nwere being printing daily when scheduled labels were run. The frequency\nof the printing of the labels should reflect the schedule entered. This\npatch corrects this problem. NOIS REN-1199-61217.\n \n1. A problem was reported where a site admitted a patient and the patient\n5. A problem was reported where a pharmacist edited the rate on an IV\norder and when the changed order was viewed in Computerized Patient Record\nSystem (CPRS) the rate would show without the ml/hr. CPRS will issue a\npatch to begin picking up the ml/hr from the messages sent by\npharmacy. This patch makes changes to the rate validation entry point\nORINF^PSIVSP Inpatient Medications provides to CPRS to help resolve this\nissue and to allow the infusion rate with the ml/hr to pass the validation\nchecks in this entry point for orders that may be renewed or changed\nthrough CPRS. NOIS WIC-0199-40011.\n \ndidn't show up and was discharged. The patient later showed up and was\n6. A problem was reported where a site needed to enter a number greater\nthan 99 at the "Pre-Exchange DOSES:" prompt. This patch will increase the\nallowable number to 9999. NOIS REN-1299-62274.\nadmitted to the hospital. When Medical Administration Service (MAS) later\nreviewed the record and deleted the first admission Inpatient Medication\norders placed for the second admission were auto dc'd. This patch will\ncorrect this problem. NOIS SLC-1199-51222.\n \n2. With this patch, the IV TYPE will be prompted when finishing an IV\n\n
\nDescription:\n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC21365566 - Issue with the quit command (i.e. up carat "^")\n not working as expected in Backdoor Pharmacy\n===========\n PSJ OE for IV order.\n \nProblem 1: \n---------\nIt was discovered when entering an IV order in Backdoor Pharmacy in\nPSJ OE, some of the prompts are not working as expected when the user\ntries to quit using the up carat "^". There are 3 prompts that have been\nidentified as not working as expected when the user tries to quit. All\nother prompts are working as expected when the user quits, which is to\nreturn the user to the "Select IV TYPE:" prompt. The 3 prompts that are\n \nnot working as expected when the user tries to quit using the up carat\n"^", occur immediately after the "REMARKS:" prompt. \nSee below:\n \n \n ***************************** WARNING *******************************\n ** If OTHER PRINT INFO exceeds 60 characters, **\n ** 'Instructions too long. See Order View or BCMA for full text.' **\n ** will print on the IV label instead of the full text. **\n *********************************************************************\n \n \n \n \nType <Enter> to continue or '^' to exit: ("^" does not work)\n \nOTHER PRINT INFO:\n Edit? NO// ("^" does not work)\n \n \n \nThis patch will resolve the following issue:\n Select one of the following:\n \n Y Yes\n N No\n \nFlag the Other Print Info (Yes/No): ("^" does not work)\n \n \nResolution 1:\n------------\n \nIt was discovered that the logic for these prompts did not contain the\ncheck to see if the user entered the up carat "^" to quit. Two routines\nrequired modifications; PSJBCMA5 and PSJUTL:\n \nPSJBCMA5 in the EDITOPI+5 and EDITOPI+7 tag was modified to check for the \nquit. PSJUTL in the ENBCMA+5 tag was modified to check for the quit.\n1) INC21365566 - Issue with the quit command (i.e. up carat "^")\n not working as expected in Backdoor Pharmacy\n PSJ OE for IV order.\n\n\nThis patch addresses the following issue:\n \nDuring patient merge, if the "TO" entry in the PHARMACY PATIENT (#55) \nfile has no prior intravenous (IV) or unit dose (UD) orders, the "zero" \nnode for each will be built without the sub-file number. \n\n
\nThe Computerized Patient Record System (CPRS) Graphical User Interface \nFor a complete listing of patches included in this release, please refer \nto the CPRS GUI v32 Release Notes.\n(GUI) v32 is an enhancement release. This patch (PSJ*5*399) is a part of\nthat enhancement release.\n \nThis patch provides the needed functionalities to support the following \nNSR:\n \n20100101: Indication on all Prescriptions and Medication Orders\n \n\n
\nThis patch addresses the following issue:\n \nComments do not display in the delimited format of the PADE\nTransaction Report.\n\n
\n1. INC20912180 - COPYING IV ORDER AND ADJUSTING START/STOP DELETES \n \n \n Resolution:\n ----------\nEditing the start or stop date drops processing logic into DEL55^PSIVORE2\nand deletes the order stub from the Pharmacy Patient file (#55). The\n'order deleted' message is conditionally filtered out from displaying if\nthis is a stubbed record so the first time the start or stop date is\nedited no message is displayed. Editing the start or stop date again\nfails to determine that the message should not be displayed. \n THE ORDER\n \nThe delete message should not be displayed during this copy process. \n \nThe logic in DEL55^PSIVORE2 is modified to quit out when there is no \nstub, this occurs after the stub has already been deleted by a previous \nedit to the start or stop date. This prevents any delete messages from \ndisplaying while copying an order. Without this conditional quit the \nonly thing that occurred was the delete message, no other process took \nplace.\n \n \n \n Technical Resolution:\n ---------------------\nThe following line of code is added at DEL55+2^PSIVORE2 \nI $D(^PS(55,DFN,"IV",+ON55,0))=0 Q \n Problem:\n -------\nWhen copying an IV order and editing the stop date, the message 'Order \ndeleted.' can be displayed and once the stop date is edited, the message \n...copying......Order deleted. is displayed at the end of Accepting the \norder. It makes it seem like the order has been deleted but it is not.\n\n
\nThis patch will resolve the following issues:\n pharmacy.\nThe lines DRUGERR+8 and DRUGERR+18 were modified to remove the condition that\nthe position had to be at the bottom of the screen for the [Press Return to\ncontinue...] prompt to be displayed. The command to wipe off the screen was \nalso removed at both lines. Furthermore, the line tag PAUSE^PSJLMUT1 was \nmodified to remove the setting of the DIR("?") because it was causing the\n"Press Return to continue..." to display 3 times after the user typed\nanything different than <RET> or "^".\n \n3) INC23152064 - MOCHA alert scrolled off the screen when a med with no\n GCNSEQNO\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1) INC20355923-HITP-8866 - Medication order activated by pharmacy and\n verified by nursing, but not able to give in BCMA as it is acting like\n it isn't after Renewal Complex Order\n \n \n INC22900561(d)-HITPS-8861\n \nProblem:\n--------\nThe Togus VA Medical Center reported that nurse verification was reset in BCMA\nafter the order expired. It was confirmed that once an inpatient order expired\nthe software was removing the BCMA verification information while in CPRS the\norder remained verified.\n \n1) INC20355923-HITP-8866 - Medication order activated by pharmacy and\nResolution:\n----------\nThe software was changed to not remove the nurse verification in BCMA when the\norder is expired.\n \nTechnical Resolution:\n--------------------\nThe line of code at ORC+8^PSJHL4 was modified to avoid resetting the Nurse\nVerification information when a expiration messages (PSOC="SS") is received\nfrom CPRS. In addition, a new API was created in PSJUTL3 called DELNV to \n verified by nursing, but not able to give in BCMA as it is acting like\nremove the BCMA Nurse verification because it was used to address the issue\nbelow.\n \n2) INC20555433 - Pharmacy Hold not setting Nurse Verify when ON/OFF action in\n pharmacy.\n \nProblem:\n--------\nIt was reported that nurse verification was reset in CPRS when an order is\nplaced or removed from hold through the Inpatient Pharmacy application\n it isn't after Renewal Complex Order\nwhile in BCMA the order remains nurse verified.\n \nResolution:\n----------\nThe software was changed to remove the nurse verification in BCMA when the\norder is placed or removed from Hold.\n \nTechnical Resolution:\n--------------------\nIncluded code at HOK+7^PSGOEH1 and HOK+11^PSGOEH0 (for Unit Dose orders), and\n \nHOLD+4^PSIVOE (for IV orders) to remove the BCMA Nurse verification (call to\nDELNV^PSJUTL3) when an order is placed or removed from hold.\n \n3) INC23152064 - MOCHA alert scrolled off the screen when a med with no\n GCNSEQNO\n \nProblem:\n--------\nRocky Mountain Regional VA Medical Center reported that sometimes the Order\nChecks alerts (example below) displayed on the screen does not present a\n INC22900561(d)-HITPS-8861\nprompt for the user to hit <RET> continue, for example, after reading the\nalert. Instead, it hangs for 2 seconds and disappears from the screen, which\nrequires the user to scroll up on the terminal emulator in order to view\nthe error message. It was observed by the reporting user that this happened\nwhen the dispense drug was matched to an NDF VA Product without and GCNSEQNO\nfield with no value.\n \n Order Check Message Example:\n ---------------------------\n Order Checks could not be done for Drug: FERROUS BISGLYCINATE 90MG CAP,ORAL,\n \n please complete a manual check for Drug Interactions, Duplicate Therapy and\n appropriate Dosing. \n \nResolution:\n----------\nThe software was written to only pause when the display of the alert message\nabove would display at the bottom of the screen. A change was made to always\npause (as shown below) after the message above is displayed independently\nwhere in the screen the message is displayed. T\n \n2) INC20555433 - Pharmacy Hold not setting Nurse Verify when ON/OFF action in\n Order Check Message Example:\n ---------------------------\n Order Checks could not be done for Drug: FERROUS BISGLYCINATE 90MG CAP,ORAL,\n please complete a manual check for Drug Interactions, Duplicate Therapy and\n appropriate Dosing. \n \n Press Return to continue...\n \nTechnical Resolution:\n--------------------\n\n\n1. CLINIC MEDICATIONS ORDER SENT TO IV PACKAGE\nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \nPatient Safety Issues (PSIs):\n=============================\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n1. INC22909170 - Order placed in an outpatient clinic location sent \n erroneously to IV medications package \n \n Problem:\n -------\nAssociated ticket(s):\n A complex Clinic Medications order using an IV medication is entered in\n CPRS and finished and accepted in Inpatient Order Entry. The orders\n are now flagged as inpatient Infusion orders instead of Clinic Infusion\n orders. After accepting the second part of the complex order the Visit\n Location is missing in Vista, the finished orders are now in the IV \n Package, the orders no longer appear under the Clinic location on the \n profile and Visit File #100 now shows the Orders with DIALOG PSJI OR\n PAT FLUID OE. The issue was found to be due to the APPOINTMENT\n DATE/TIME field (#139) of the IV multiple (#55.01) in the PHARMACY\n PATIENT file (#55). This appears to only be an issue with complex\n=====================\n clinic medication orders for an IV medication. Noncomplex clinic\n medication orders for an IV medication does have the field populated\n and correctly displays as a Clinic Infusion in CPRS and on the\n Inpatient Medication profile under the Clinic.\n \n \n Resolution:\n ----------\n Routine PSJCOMV is modified to populate the APPOINTMENT DATE/TIME field\n (#139) of the IV multiple (#55.01) in the PHARMACY PATIENT file (#55). \n \n \n \n \n \n Technical Resolution:\n ---------------------\n The following code is added at line IV+8^PSJCOMV:\n \n S:+$G(P("APPT")) $P(^TMP("PSJCOM",$J,+ON,"DSS"),U,2)=P("APPT")\n \n1. INC22909170 - Order placed in an outpatient clinic location sent \n This will populate the DSS node piece 2 of the ^TMP "PSJCOM" global \n that will end up in the APPOINTMENT DATE/TIME field (#139) of the IV\n multiple (#55.01) in the PHARMACY PATIENT file (#55) and in variable\n ORAPPT where it is used (in routine IV^ORMPS1) to determine the DIALOG\n for the order.\n erroneously to IV medications package\n \n \n\n\nINC21176679: Error in complex orders related to Self-Med edit field (7)\n\n
\nINC11595511 - Unauthorized Access to IV Room File (#59.5)\n---------------------------------------------------------\nIf the Coverage Timing for any IV Type (Admixtures, Chemotherapy, \nHyperal, Piggyback or Syringe) in the IV Room file (#59.5) and a user is \nusing that IV Room in backdoor pharmacy-related functionality, they may \nbe warned "Manufacturing Time(s) missing for 'IV type'" and then asked \n"Would you like to edit this IV room?". If user answers "yes", they are \nallowed to edit/update that IV Room without the requirement for the PSJI \nMGR security key. See the Patch Description on FORUM for more details.\n\n
\nDefect Tracking System Ticket(s) & Overview:\nprocessing it in Inpatient Pharmacy and editing the STOP DATE before \naccepting any order in the complex set of orders, the STOP DATE does not \nget updated in CPRS. The problem is that an HL7 message is not sent to \nCPRS after the STOP DATE is filed into PHARMACY PATIENT file #55. \nSeveral lines after an HL7 message is sent to CPRS from routine PSJOEA1, \nthere is a call to UPDREN^PSGOER made where the following fields can be \nupdated in file #55; VERIFYING NURSE (#16), DATE VERIFIED BY NURSE (#17), \nSTATUS (#28), STOP DATE/TIME (#34), ADMIN TIMES (#41), FOLLOWING ORDER \n(#105), REASON FOR FOLLOWING ORDER (#107), ORDERABLE ITEM (#108), and sub \nrecord LAST RENEW [55.6114DA]. After UPDREN^PSGOER completes, another \n===========================================\ncall to send updates via HL7 message to CPRS does not occur. Any of \nthese fields that are needed in CPRS may not be up to date in the ORDER \nfile (#100), most notably fields STATUS (#5) and STOP DATE (#22)\n \n \n Resolution:\n ----------\nA new call to send an HL7 message to CPRS is added after UPDREN^PSGOER \ncompletes. This allows all the data in PHARMACY PATIENT file (#55) to be \nupdated when this HL7 message is sent for the current order.\n \n \n \n Technical Resolution:\n ---------------------\nIn routine PSJOEA1, the call to routine UNL^PSSLOCK that unlocks the \nORDER file (#100) is moved from after the HL7 message is sent at line \nCHK+30\n ....D EN1^PSJHL2(DFN,"SC",PSGORDR) ;,UNL^PSSLOCK(DFN,PSGORDR) move below \np433\nThis is necessary so that the call to EN1^PSJHL2 at line CHK+38^PSJOEA1 \n1. INC21776729 - Complex order renewal Stop Date not matching \nwill have the ORDER file (#100) locked after UPDREN^PSGOER is called at \nline CHK+37^PSJOEA1\n ...D \nUPDREN^PSGOER(DA,$P(ND14,U),$P(ND14,U,3),$P(ND14,U,4),$P($G(^PS(53.1,+PSJO\n,.2)),U,3),$P(ND14,U,2))\n ...D EN1^PSJHL2(DFN,"SC",PSGORDR) ;p433\nThe unlock of the ORDER file (#100) is now at line CHK+42^PSJOEA1\n .. D UNL^PSSLOCK(DFN,PSGORDR) ;Move unlock to here p433\n between CPRS and Inpatient Pharmacy\n \n Problem:\n -------\nWhen renewing a complex order with the AND conjunction in CPRS and \n\n
\n1. A site without 24-hour pharmacy coverage entered an E3R requesting\nTUA-0999-32647.\n \n2. In the Non-Verified/Pending Orders [PSJU VBW] option, the order was\nnot locked correctly if the user chose "NO Profile" at the "SHORT, LONG,\nor NO Profile? SHORT//" prompt. This patch will correct this problem.\n \n3. Within the LBL Label Print/Reprint hidden action, if the user selected\nthe ILIV Individual Labels (IV) option, a new order may be entered. This\npatch will prevent any new orders from being entered from the hidden menu.\n \nthat Inpatient Medications allow users holding the PSJ RNURSE key be\n4. When a pending order had a schedule of "ONE TIME", "ONE-TIME", "ONCE"\nor "STAT", the Schedule Type is not defaulted to "ONE TIME". This patch\nwill set the Schedule Type to "ONE TIME" for these types of schedule. NOIS\nHUN-1199-20125. \n \n5. A site reported receiving an undefined error when the pharmacist\nfinishing a Unit Dose order had the PSJ RNURSE, PSJ RNFINSH keys as well\nas the regular pharmacist keys and auto verify turned on. This patch\ncorrects this problem. NOIS AMA-0200-72006.\nallowed to finish and verify orders placed through Computerized Patient\nRecord System (CPRS). This would put the orders in an active status, so\nthey would be available to the Bar Code Med Admin (BCMA) software. The\nE3R# is 11620. With the installation of this patch, users who hold the PSJ\nRNFINSH key will have the option to finish and verify orders placed\nthrough CPRS. It was decided by the workgroup that a new key should be\ncreated to control this additional functionality. E3R# 11620, and NOIS\n\n
\nINC25661636 - Certain IV orders not displaying correctly in CPRS and VistA\n--------------------------------------------------------------------------\nWhen a continuous IV order is entered in CPRS with a free text infusion\nrate that has a decimal with or without a preceding 0, the system thinks\nthat this is a numeric infusion rate for some reason and adds the "ml/hr"\nsuffix. This causes issues when we're also trying to designate the number\nof labels to print with the "@" sign because it does not recognize this in\npharmacy finishing and removes the "@" along with the number that follows.\nSee the Patch Description on FORUM for more details.\n\n
\nThis patch will resolve the following issue:\n \nThe VistA PADE HL7 interface is sending a zero for the priority on all IV\norders instead of the actual priority from the pharmacy patient file. \nThis, in turn, prevents differentiation of routine and stat/asap orders\nvia the interface feed.\n\n
\nINC26226397 - Vista inpatient orders in Renewed status are able to be \nmarked as "Not to be Given" which then in turn marks the pending new \norder to also be marked as "Not to be Given". Only orders in an Expired \nor Discontinued status should be able to be marked as "Not to be Given".\n\n
\nSee FORUM for patch description.\n\n
\nThis patch will resolve the following issue:\n \nIt was reported that when using the Day-of-the-Week (DOW) schedule builder\nin CPRS when ordering an inpatient medication, CPRS properly displays the\nward administration time after entering and accepting the order. However,\nafter the order is signed, the ward administration time is being \noverwritten by the standard administration time.\n\n
\nThis patch addresses one issue:\n \nWhen editing a unit dose order which has a duration and attempting to \nexit with "^", the user is given an erroneous "Is this correct" prompt \nand not allowed to answer "Y" or "N".\n\n
\nINC27709580 - CPRS continuous infusion orders with a rate of less than \none create an improperly formatted rate ending in "ml/hr ml/hr"\n\n
\nThis patch addresses one issue:\n \nAn incorrect units per dose value might be saved for a unit dose order if \nthe dosage was edited before verifying the order.\n\n
\n \n \nProblem(s):\n-----------\n1. INC30646734 - Albany VA Medical Center (NY) reported an undefined \nerror that occurs in VistA backdoor pharmacy (inpatient order entry), \nwhen you copy an active unit dose order, that has a transdermal patch \norderable item field "Prompt for removal in BCMA", set to "Removal \nPeriod Required Prior to Next Administration", edit the start date/time, \nand then choose to edit the admin time, say NO to the prompt "Is this \ncorrect", then enter in a new ADMIN time. The system hard errors and \nThis patch addresses the following two incident tickets:\nkicks you out of Vista. Hard error is <UNDEFINED>DONE+3^PSGOE91 \n*PSGOEEF(41).\n \n2. INC31233823 - Albany VA Medical Center (NY) reported an undefined \nerror that occurs in VistA backdoor pharmacy (inpatient order entry) when \nediting the start date before accepting an active unit dose order \n(without a copy). Hard error is <UNDEFINED>DONE+3^PSGOE81 *PSGOEEF(39).\n \n \nResolution:\n \n-----------\n1. INC30646734 - Adding a check for data in the PSGOE91 routine DONE tag \nfor the PSGOEEF(PSGF2) variable. In some cases, there is no data and the \nvariable is not defined therefore causing a hard error and kicking the \nuser out. Adding the check will allow the logic to continue to process \nthe UD order without a hard error. Also adding a change to the PSGOE91 \nroutine A10 tag, so the date/time will display appropriately. Currently \nit shows the correct date and then an up caret with the internal date.\n \n2. INC31233823 - Adding a check for data in the PSGOE81 routine for the \n1. INC30646734 - VISTA PSJ UNDEFINED ERROR AFTER COPYING UD ORDER WITH \nPSGOEEF(PSGF2) variable. In some cases, there is no data and the \nvariable is not defined therefore causing a hard error and kicking the \nuser out. Adding the check will allow the logic to continue to process \nthe UD order without a hard error.\n \n \nTechnical Resolution:\n---------------------\n1. INC30646734 - Routine PSGOE91 is modified at line to check for data in \nthe variable causing the undefined error, and correcting the format of \nREMOVAL REQUIRED.\nthe date.\n \nLine DONE+3\n I PSGOEE G:'PSGOEEF(PSGF2) @BACK S PSGOEE=PSGOEEF(PSGF2)\nTo\n I PSGOEE G:'$G(PSGOEEF(PSGF2)) @BACK S PSGOEE=PSGOEEF(PSGF2)\n \nLine A10+6\n I X="",PSGSD W " "_PSGSDN G DONE\nTo\n \n I X="",PSGSD W " "_$P(PSGSDN,"^") G DONE\n \n \n2. INC31233823 - Routine PSGOE81 is modified to check for data in the \nvariable causing the undefined error.\n \nLine DONE+3\n I PSGOEE G:'PSGOEEF(PSGF2) @BACK S PSGOEE=PSGOEEF(PSGF2)\nTo\n I PSGOEE G:'$G(PSGOEEF(PSGF2)) @BACK S PSGOEE=PSGOEEF(PSGF2)\n2. INC31233823 - VISTA PSJ UNDEFINED ERROR AFTER EDITING START TIME \nBEFORE ACCEPTING UD ORDER REQUIRING REMOVAL.\n \n\n
\n \nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\n1. A problem was reported by a site when trying to finish an order with a\nthe pending order before allowing actions on pending orders.\n \n3. A problem was reported where a site was trying to renew an IV order\nthrough CPRS and was receiving the message Invalid Infusion Rate. The\nproblem was that when finishing the order Pharmacy changed the infusion\nrate to the format Text@# and this was not being passed back to CPRS when\nthe new order was created. This patch corrects this problem. \nNOIS HIN-0100-41126.\n \n4. E3R# 11771, Change Nature of Order auto prompt requested that the\nLog-in date of midnight 01/04/00 and the ward parameter set to Use Closest\ndefault for orders changed in pharmacy due to edit should be Service\nCorrection rather than Written. This patch changes this functionality.\n \n5. A problem was reported by a site when using the option Inpatient Order\nEntry [PSJ OE] to enter new orders. At the 'SCHEDULE: ' prompt the user\nwould enter a question mark and answer 'yes' to the prompt 'Do you want\nthe entire ADMINISTRATION SCHEDULE List?'. Part of the resulting list\nwould scroll off the top part of the screen; the user was using a CRT and\ncouldn't scroll back to see the data. This patch will correct this\nproblem. NOIS MUR-0100-31928.\nAdmin Time. The start date/time was incorrectly displayed as ******** and\n \n6. A problem was reported by a site on a Unit Dose order which was\noriginally placed through Inpatient Medication options. The order had\ndispense drugs entered when it was ordered and these were not passed to\nCPRS. When the order was copied through the CPRS option, no default\ndispense drug was displayed to the user and no order checks took place.\nCPRS does not allow more than one dispense drug per Unit Dose order. This\npatch will correct this problem for orders where there is one dispense\ndrug for the order, but not more than one. NOIS MAC-0200-62454.\nthe stop date/time was incorrectly displayed as 59/00/23 0:00. This\npatch will correct this problem. NOIS CON-0100-10187.\n \n2. Additional functionality is included in this patch to change the PSJHL\nroutines to do an additional check to ensure that the patient IEN received\nfrom Computerized Patient Record System (CPRS) matches the IEN stored in\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch.\n\n
\nPlease refer to the patch description for a full description of the \ncontents.\n\n
\nPlease review FORUM's Patch Module description and installation \ninstructions before installing this patch\n\n
\nThe description of this build can be found in the National Patch Module \nunder PSJ*5*423.\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nThis patch, along with other patches, adds Pharmacogenomic (PGx) order\nchecking to medication orders entered through Inpatient Medications,\nOutpatient Pharmacy and Computerized Patient Record System (CPRS). A \npatient's genomic test results will be retrieved from the Health Data\nRepository (HDR), and along with the prospective drug(s) of a medication\norder is sent to the vendor to retrieve interactions between the patient's\ngenes and the prospective drug(s).\n\n
\nPlease review FORUM's Patch Module description and installation\ninstructions before installing this patch.\n\n
\nThis patch includes routines, options, and partial Data Dictionary\n- Removal of nonstandard reference to global ^DGPM(.\n- Write commands in the Data Dictionary were converted to EN^DDIOL calls.\n- Removal of variable kills of % variables.\n- Variable DT sets were changed to supported $$DT^XLFDT calls.\n- References to ^DD were changed to FileMan supported D FIELD^DID calls.\n- Many routines that are no longer used were deleted in the Version 5.0\n install. This patch deletes the corresponding options.\n- Removal of nonstandard reference to ^DIC(9.4. These were changed to\n supported $$VERSION^XPDUTL calls.\ncomponents that address Software Quality Assurance issues found for\nversion 5. This patch corrects these issues.\n \n \nSome of the QA issues resolved:\n \n- Removal of nonstandard reference to global ^DISV(.\n- Removal of nonstandard reference to global ^XUTL(.\n\n
\n1. E3R# 12551, Dispense Extra Unit Default, requested that the default for\nICU was used as a service. This is not one of the services defined in the\nWARD LOCATION file (#42). ICU has been replaced with Surgery. NOIS\nPHO-0100-62836.\n \n3. A problem was reported where pending IV orders were being discontinued\nthrough the Inpatient Medications options and no Nature of Order was being\npassed to Computerized Patient Record System (CPRS). This patch corrects\nthis problem. NOIS PTH-0300-21183.\n \n4. A problem was reported that when using the Unit Dose/Pick List option\nthe prompt "Do you want to dispense these extra units through the ATC:\nEXtra Units Dispensed [PSJU EUD], when saying YES to have the drug\ndispensed through the ATC machine, it was not packaged. The problem is\ncaused by the Extra Units Dispensed using a field that is set to be\ndeleted for the ATC device. This patch corrects the problem. NOIS\nUNY-0400-12501.\n \n5. If a schedule "ONE-TIME" is not defined in the Administration Schedule\nfile (#51.1), it does not recognize in the IV piggyback order and the\nStart and Stop date/times are not set appropriately. With this patch\nOne-Time will be given the Start and Stop date/time as in the unit dose\nYes//" be changed to No. This default is presented to the user when\nfunctionality. NOIS SDC-0300-60125.\n \n6. The nurse's initials for verifying IV orders in CPRS are not passing\nto the Bar Code Medication Administration (BCMA) package to display on the\nVDL. This patch will correct this problem.\n \n7. This patch adds the FREQUENCY field (#41) to the 11th piece in\n^TMP("PSJ",$J,4). This becomes a part of the information returned by the\nAPI provided in the PSJBCMA1 routine to the Bar Code Medication\nAdministration (BCMA) package.\nrunning the option EXtra Units Dispensed [PSJU EUD] if the drug is set up\n \n8. A problem was reported where a site was unable to enter an infusion\nrate in the format FREE TEXT@NUMBER OF LABELS PER DAY through CPRS. This\npatch corrects this problem by updating the entry point ORINF^PSIVSP.\nNOIS DEN-0400-52116.\n \n9. A problem was reported where a site had IV Fluid orders entered via\nComputerized Patient Record System (CPRS). The orders were finished\nthrough the backdoor pharmacy options as piggyback orders and the ward\nspecific administration times were not presented as the default for the\nto be dispensed through the ATC. This patch will change the default for\npharmacy user finishing the orders. This patch corrects this problem.\nNOIS CLL-0500-41826.\n \n10. This patch also modifieds the API routines PSJBCMA1 and PSJBCMA2 to\nuse ^TMP("PSJ1" and ^TMP("PSJ2", respectively, to make a distinction\nbetween the two different sets of data returned to the Bar Code Medication\nAdministration (BCMA) package.\nthis prompt to No.\n \n2. A site had questions about the documentation for the option\nAUto-Discontinue Set-Up [PSJ AC SET-UP]. In the on-line documentation,\n\n\n1. Several sites have reported a problem related to medication orders\nDFN of the patient in the pending order being updated. This should keep\nthe problem from occurring.\n \n2. A site reported a problem with an undefined error when attempting to\nprocess an order. This patch is to correct the program to prevent the\nundefined error. NOIS: BRX-0200-10119.\ngetting mixed up. The problem most frequently reported is that a Unit\nDose order is being changed to an IV order. The development team has been\nunable to recreate this problem, but thinks the problem may be a result of\nusing the variable DFN in the PSJHL messaging routines. With the\ninstallation of this patch the variable DFN will be changed to PSJHLDFN in\nthe PSJHL messaging routines. Additionally checks have been added to PSJOE\nand PSJLIFN to be sure that the order number being finished is the order\nnumber being updated and that the DFN of the patient selected matches the\n\n
\nPSJ*5*48 provides an API for the Clinical Reminders package. The API\nprovides patient and order information, based on a specified date range\nand a specified list of medications, as it relates to the Hepatitis C\nInitiative. This patch will not affect users of the Inpatient Medications\npackage. The PSJORAPI routine in patch PSJ*5*48 provides an entry point\nthat returns patient and order information in a ^TMP global to the\nClinical Reminders package, based on the criteria passed into the call.\n\n
\n1. When an Orderable Item has a Schedule Type defined as "Fill on\nNOIS: HUN-0400-22176\n \n3. A site reported a problem with an inconsistency in calculating the\nstop date of a renewal order. When finishing a renewal from the\nComputerized Patient Record System (CPRS) the least of all the stop dates\nwas used. However, in backdoor pharmacy, the stop date for the orderable\nitem was always used, if it existed. This patch corrects this problem by\nmodifying the backdoor pharmacy function to behave the same as the\nfinishing process. NOIS: EKH-0600-41622\n \nRequest" and the pending order has a Schedule of "NOW", the Schedule Type\n4. Two sites reported a problem with an inconsistency with the handling\nof the stop date for One-Time orders. When finishing a One-Time order\nentered in the Computerized Patient Record System (CPRS), if the stop date\nwas edited, the start date was also changed. However, in backdoor\npharmacy, this was not the case. This patch corrects this problem by\nmodifying the finishing process to work the same as backdoor pharmacy.\nNOIS: WPB-0500-32018 and HIN-0300-43237\nis not converted to "ONE TIME" during the finishing process. This patch\nwill correct this problem. NOIS: EKH-0600-40188.\n \n2. A site reported a problem with an inconsistency between orders placed\nfrom the Computerized Patient Record System (CPRS) and backdoor pharmacy.\nThe problem was with orders entered in CPRS as On Call and then finished\nas On Call being immediately expired. This patch corrects this problem.\n\n
\nThis patch makes the following changes to the APIs between Inpatient\n(#53.1) and #66 of the PHARMACY PATIENT file (#55)) to piece 9 of\n^TMP("PSJ",$J,Index,0) and ^TMP("PSJ1",$J,0)\nMedications and Bar Code Medication Administration (BCMA) (Integration\nAgreement #s 2828 and 2829):\n a. put the SCHEDULE INTERVAL field (#.17) from the IV sub-file (#55.01)\nof the PHARMACY PATIENT file (#55) in the 11th piece of ^TMP("PSJ1",$J,4)\n b. add the IV TYPE field (#.04), INTERMITTENT SYRINGE field (#108) and\nthe CHEMOTHERAPY TYPE field (#106) from the PHARMACY PATIENT file (#55) to\npieces 6-8, respectively, of ^TMP("PSJ",$J,Index,0) and ^TMP("PSJ1",$J,0)\n c. add the ORDERS FILE ENTRY field (#49 of the NON-VERIFIED ORDERS file\n\n\n1. Several sites have reported a problem with the ACTIVITY LOG REASON file\ndispensing of medications through the Bar Code Med Admin (BCMA)\nsoftware. The sites have reported receiving the following error:\n \n 1. Data Validation Error: 701: The value 'AC' for field DOSES ORDERED in\n DISPENSE DRUG SUB-FIELD in file BCMA MEDICATION LOG is not valid.\n \nThe problem was with the input transform on the UNITS PER DOSE field\n(#.02) in the DISPENSE DRUG sub-file (#53.4502) of the INPATIENT USER\nPARAMETERS file (#53.45) and the DISPENSE DRUG sub-file (#53.11) of the\nNON-VERIFIED ORDERS file (#53.1). The problem with the input transform\n(#53.3). The sites have entry numbers 1 - 75, a "B" x-ref, and are\nalso exists in the PHARMACY PATIENT file (#55), UNIT DOSE sub-file\n(#55.06), DISPENSE DRUG sub-file (#55.07), UNITS PER DOSE field (#.02).\nPatch PSS*1*35 corrects this problem in the PHARMACY PATIENT file (#55)\nand this patch corrects the problem in the INPATIENT USER PARAMETERS file\n(#53.45) and the NON-VERIFIED ORDERS file (#53.1). NOIS#s NOL-0300-71473,\nHOU-0300-71626, and CMO-0300-43187.\n \n3. Site reported a problem where they entered an infusion rate of @x and\nx labels didn't print. Only 1 label printed. The issue is that only one\nadministration time was specified. The administration time overrides\nmissing entry numbers 1035 and 1040. This patch will delete the current\nthe entry of @x when determining how many labels will print. This patch\nmodifies the field description and documentation for INFUSION RATE in\norder to clarify which field determines the number of labels. Modified\nthe INFUSION RATE field (#59) in the NON-VERIFIED ORDERS file (#53.1).\n \n4. This patch modifies the following fields to remove references to the\ncompany name of Baxter: PICK LIST file (#53.5), DATA/TIME LIST SENT TO\nTHE ATC field (#.13), UNIT DOSE/ATC MEDS file (#53.55), PICK LIST field\n(#.01), UNIT DOSE/ATC MEDS file (#53.55), LAST RECORD SENT field (#1),\nUNIT DOSE/ATC MEDS file (#53.55), DATA RECORDS field (#10), UNIT DOSE/ATC\nData Dictionary (DD) and data for this file at the site and bring in the\nMEDS file (#53.55), DATA RECORDS sub-file (#10), DATA RECORDS field\n(#.01), WARD GROUP file (#57.5), BAXTER ATC DEVICE POINTER field (#32) and\nthe description of the UNIT DOSE/ATC MEDS file (#53.55).\n \n5. This patch removes the references to the specific model 212 ATC\ndispensing system from the description of the UNIT DOSE/ATC MEDS file\n(#53.55).\n \n6. This patch modifies the following menu options to remove references to\nthe company name of Baxter: Send Pick List to ATC [PSJU PLATCS] and\ncorrect DD and data. The pre-init routine PSJ0043 accomplishes the\nDispense Drug/ATC Set Up [PSSJU DRUG/ATC SET UP].\ndeletion of the DD and the data and will be automatically deleted once\nthe installation is complete. NOIS# HAM-0300-21499.\n \n2. Several sites have reported a problem when trying to document the\n\n
\n1. A problem was reported by a site where one time Unit Dose orders\nUnit Dose orders when selecting NO PROFILE. E3R# 11834.\n \n3. A problem was reported by a site that when finishing a Unit Dose\npending renewal a change was made that caused a new order to be created.\nThe original order retained the renewed status and the stop date/time was\nnot updated so that it would expire when the new order's start date/time\nwas reached. This patch corrects this problem. NOIS# HIN-0300-41916.\n \n4. An inconsistency was discovered between the Computerized Patient Record\nSystem (CPRS) and the Inpatient Medications validation of Provider\nentered through Computerized Patient Record System (CPRS) after hours,\nComments/Special Instructions. CPRS allows entry of text with no spaces\nwhile Inpatient Medications requires spaces. This patch corrects this\nproblem. Inpatient Medications will now allow entry of Special\nInstructions with no spaces. NOIS# ASH-0500-30650.\n \n5. A problem was reported with label print if the Provider Comments\nentered in Computerized Patient Record System (CPRS) contained no spaces.\nThis patch modifies label print to correctly print the information even if\nno spaces are present. NOIS# NAS-0400-32349.\nfinished by a nurse with the PSJ RNFINISH key, and verified by the nurse\non the ward, were not appearing on the summary of non-verified orders for\nthe Pharmacist using the Non-Verified/Pending Orders [PSJU VBW] option.\nThis patch corrects this problem. NOIS# CLL-0500-41728.\n \n2. An E3R was entered requesting that nurses using the\nNon-Verified/Pending Orders [PSJU VBW] option see expired non-verified\n\n
\n1. Pharmacy Benefits Management (PBM) has requested that Technical\nthe ordering processes by entry of the Internal Entry Number.\n \n2. Order check warning does not display in back door order entry for\nusers with the "ALLOW AUTO-VERIFY FOR USER" set to yes. This patch will\ncorrect this problem. NOIS# POR-0900-50194.\nServices develop a software patch that would disable the Drug file (#50)\nInternal Entry Number (IEN) (.001 field) lookup during order entry\nprocesses. The pharmacy software has always allowed IEN lookup and quick\ncode lookups at the request of field users. A quick code is a\nuser-defined synonym for a drug (i.e. A325->Acetaminophen 325mg Tab). PBM\nprovided guidance to VA Medical Centers in the past to not use low numbers\nfor quick codes and to inactivate the first 50 entries in the drug file to\nreduce the chances of error. This patch would eliminate drug selection in\n\n
\n1. A problem was reported where a site edited a pending IV order deleting\n3. A site reported receiving an error when trying to queue the\nPAtient Profile (Unit Dose) [PSJU PR] option. This patch corrects this\nproblem. NOIS# ANN-0800-41860.\nthe additive or solution and then adding a different additive or solution\nto the order, this change did not cause a new order to be created. This\npatch corrects this problem. NOIS# REN-0500-60972.\n \n2. A problem was reported where the duplicate order check scrolled off the\nscreen when the pharmacist was entering a new order. This patch will\ncorrect this problem. NOIS# PHO-0500-61993.\n \n\n
\nA site reported a problem with the display of sensitive information in\nInpatient Medications. During patient lookup, social security numbers and\ndates of birth for sensitive patients should display *SENSITIVE* on the\nscreen. In Inpatient Medications, the actual social security number and\ndate of birth are displaying. This patch corrects this problem by\ncombining the sensitive patient handling and the special formatting from\nInpatient Medications.\n\n
\n1. In Inpatient Medications V. 4.5 and Order Entry Results Reporting\nsearches for Unit Dose orders that were entered for outpatients through\nOERR V. 2.5. The orders would normally be discontinued if the patient is\nadmitted again. This task finds the patients that have never admitted\nagain since these orders were entered. The pending orders will have their\nstatus changed to Discontinued.\n \n3. A second job is also queued for the same time that corrects a problem\nfound in the Unit Dose Verification fields cross-references in the\nNON-VERIFIED ORDERS file (#53.1). Some orders that were verified by a\nPharmacist or Nurse were not having the corresponding Pharmacist or Nurse\n(OERR) V. 2.5, orders for outpatient IVs could be entered for a patient in\ncross-reference set correctly for the order. This task will go through\nthese cross-references checking each one. When one is found to be\nerroneous it will be corrected.\n \n4. This patch also includes a change to correct an error that can occur\nduring the Pick List Conversion. Changes were made to prevent bad pick\nlist entries from causing an error when the pick list is reindexed. When\nthe pick list is purged, the bad entries will be deleted.\n \nNOTE: You will see the KIDS Install question only if the Computerized\nOERR. These IV orders were then finished in pharmacy. If a Unit Dose\nPatient Record System (CPRS) Patient Order conversion has finished. These\ntwo tasks can only run after the CPRS Order conversion has completed. This\ncan be checked by D STATUS^OR3CONV1. If the CPRS Order conversion has not\nfinished, the post install routine for this patch will not run. The\nchange to routine PSJIPST3 will allow these two tasks to be queued up\nautomatically when the CPRS conversion finishes.\n \nIt is recommended that this job be queued to run at a non-peak hour.\norder was mistakenly entered for an Outpatient, the pharmacist would\nnotice this and discontinue the order. In Inpatient Medications V. 5.0,\nthe pharmacist can no longer Discontinue these erroneous Outpatient Unit\nDose orders.\n \n2. This patch allows the installer to queue a background task that\n\n
\n1. Several sites have reported a problem with the start date/time on Unit\n \n2. When selecting from the Orderable Item file(#50.7), the SYNONYM lookup\nwas allowed and patch PSJ*5.0*52 removed this capability. This patch will\nrestore the ability of entering a SYNONYM at the "Select Drug:" prompt.\nNOIS# REN-1100-62137.\n \n3. When selecting from the Drug file (#50), the user entered lowercase\nletters and was returned a drug based on the VA Drug Class lookup and was\nnot offered a choice of drugs starting with the letters entered. This\npatch corrects this problem. NOIS# CMS-1200-30893.\nDose orders placed through Computerized Patient Record System (CPRS)\ndefaulting in as "********" and the stop date/time defaulting in as\n"00/00/24 :". If the pharmacist finishing the order doesn't catch this\ndiscrepancy in the start and stop date/time, the order can be finished\nwithout a start and stop date/time. Then the order is visible in CPRS on\nthe orders tab, but not on the meds tab, and not in Inpatient Medications.\nThis patch corrects this problem. NOIS# DAN-1200-41606, UNY-1200-11451,\nBEC-1200-20932.\n\n
\n1. E3R# 14641 requested that the UD Default Stop Date/Time be reset to\nNOIS# NAS-0700-30575 and DEN-0700-50863.\n \n3. A problem was reported by a site where they were doing a detailed\ndisplay of a unit dose medication order on the meds tab through CPRS and\nthe field Units/Dose was displayed as null and through Inpatient\nMedications the UNITS PER DOSE field (#.02) of the Dispense Drug sub-file\nwas displayed as 1. In Inpatient Medications if the UNITS PER DOSE field\nis null it is assumed that 1 unit is to be dispensed and a 1 is displayed.\nThis patch makes changes to the API that CPRS calls to make the\ninformation display consistently. NOIS# PUG-1000-51002.\nnull when Inpatient Medication orders are discontinued due to a Treating\n *****PLEASE NOTE THE FOLLOWING INFO*****\n If a unit dose order contains more than one dispense drug only dosage\nordered will be returned to CPRS and no units per dose. If a unit dose\norder has a status of pending and the units per dose field is null, no\nunits per dose will be returned.\n \n4. A problem was reported by a site where a medications order placed on\nhold through Inpatient Medications options and then taken off hold through\nthese same options was not displaying correctly on the orders tab in CPRS.\nThe order text was not being updated appropriately. The status showed as\nSpecialty Change. This patch will accomplish this request.\nactive, but the word hold still showed on the left side of the order text.\nThis patch corrects this problem. NOIS# ROS-0900-52226.\n \n2. A problem was reported where a nurse entered an order through the\nComputerized Patient Record System (CPRS) options using verbal or\ntelephoned as the nature of order. When the order was finished and a\ndetailed view of the order was done on the meds tab in CPRS the nurse was\nshowing as the Pharmacist. This patch corrects this problem. \n\n
\n1. A site reported a problem in the PAtient Profile (Unit Dose) [PSJU PR]\nMedication Administration (BCMA) when attempting to access the pharmacy\npatient activity log. This patch modifies the API to BCMA by adding the\ninternal entry number of the person who performs an action on a unit dose\norder to the information passed back to BCMA. In addition, the API has\nbeen changed to send all activities for the IV orders, even if no data was\nedited.\n \n4. A site reported a problem with MAR labels not printing when a nurse\nverified the order in the Computerized Patient Record System (CPRS). This\npatch corrects this problem.\noption. When entering '^^' at the 'View ORDERS' prompt, an error was\n \n5. A site reported a problem with the Inpatient Profile [PSJ PR] option\nwhen attempting to print certain patients. If a patient had an order with\nmore than six activity log entries, the option would go into an infinite\nloop when printing to a printer. This patch corrects this problem.\n \n6. A problem was discovered with the handling of date/time validations in\nInpatient Order Entry [PSJ OE]. There was a problem with the way the\noption was verifying that a time had been entered. This patch corrects\nthis problem.\nreceived. This patch corrects this problem.\n \n2. A site reported a problem with the number of labels printing after an\ninfusion rate of xxx@0 was entered. Even though they entered 0 for the\nnumber of labels, labels still printed. This patch corrects this problem.\n \n3. A site reported a problem with receiving an error in Bar Code\n\n
\n1. A problem was reported by a site where after using the Inpatient Order\nAction Profile #2 [PSJU AP-2], and AUthorized Absence/Discharge Summary\n[PSJU DS] options where the signature block states Physician's Signature.\nThis patch changes this to Provider's Signature. NOIS# REN-0301-62349.\nEntry [PSJ OE] option the user then jumped to the Patients on Specific\nDrug(s) [PSJ PDV] option and after selecting the start date, stop date,\ntype of orders, sort by, and list by the user was returned to the top\nlevel menu without the report running. This patch corrects this problem.\nNOIS# KAN-0401-40002.\n \n2. A site reported a problem where nurse practitioners and other providers\nwere signing the reports generated by the Action Profile #1 [PSJU AP-1],\n\n
\n1. A site reported a problem where they got a null subscript error when\nPharmacy Technician or Nurse will be prompted after selecting the\nNon-Verified/Pending Orders [PSJU VBW] option for the IV ROOM NAME, if the\nuser returns past the prompt or enters an up-arrow the user will be\nreturned to the main menu. Users will only be prompted if there is more\nthan one active IV ROOM in the IV ROOM file (#59.5). This patch corrects\nthis problem. NOIS# BRX-0301-10962.\n \n3. After the release of patch PSJ*5*51, several sites reported a problem\nthat occurred while using the OR GUA EVENT PROCESSOR protocol on the DGPM\nMOVEMENT EVENTS protocol an error would occur. Sites were advised to\ntrying to run the option Extra Units Dispensed Report [PSJU EUDD] by\nswitch to the OR GUA EVENT PROCESSOR NOTASK, this corrected the error, but\nsites began reporting problems with the release of time delayed orders.\nThis patch will correct this problem and allow sites to begin using the OR\nGUA EVENT PROCESSOR protocol again without an error. NOIS#s\nLAH-0201-61581, ANN-0301-40951, ALT-0301-20287, and MIW-0201-42370.\npatient. This patch corrects this problem. NOIS# HUN-0700-22263.\n \n2. A site reported a problem where the user received an undefined error\nwhen a Pharmacy Technician or Nurse was using the Non-Verified/Pending\nOrders [PSJU VBW] option and viewing pending IV orders. The user was\nprompted "Select IV ROOM NAME:", the user entered a return or an up-arrow\nand received the undefined error. With the installation of this patch the\n\n
\n1. Several sites reported errors when attempting to evaluate clinical\nKILLPC^PXRMPINF(PXRMDFN) where PXRMDFN = "PXRMDFN"_DFN. You can identify\nthe patients DFN from the error.\n \n$ZE= LDATE+8^PXRMDRUG:1, %DSM-E-UNDEF, undefined variable\n^XTMP("PXRMDFN6762","PSDRUG","INSULIN NOVOLIN N-HUMAN NPH\n100U/ML",3001214.10445), -DSM-I-ECODE, MUMPS error code: M7 \n \nFor example, in this case you would type D KILLPC^PXRMPINF("PXRMDFN6762").\n \nWhile the patch corrects the errors in the dates, the ^XTMP global built\nreminders. The problem was caused by dates in the PHARMACY PATIENT file\nby the Clinical Reminders software only gets rebuilt if it is more than 24\nhours old and may not have been rebuilt before the software evaluates the\nnext clinical reminder. The above entry point will force the rebuilding\nof the ^XTMP for the patient that generated the error.\n(#55) that were in the wrong format. This patch corrects the format of\nthose dates. NOIS# BUT-0401-21836, MON-0401-52179, EKH-0401-42360,\nSDC-0401-62568.\n \nIf after installing and running PSJ*5*61 your site is still receiving the\n<UNDEFINED>LDATE+8~PXRMDRUG error, it may be necessary to call the\nfollowing entry point within the Clinical Reminders software\n\n\n1. There have been several requests that the information in the SPECIAL\nin that field was being presented as the default provider in backdoor\npharmacy order entry even though the provider was no longer active.\nThis patch corrects this problem. NOIS# BRX-0700-10937.\n \n3. A problem was reported where a cross-reference was left around which\nshould have been killed. This caused it to appear as though the patient\nhad an order that needed processing when there was no order. When the\norder was selected the user received an undefined error. This patch\ncorrects this problem. NOIS# NJH-0800-20230.\n \nINSTRUCTIONS field (#8) and the OTHER PRINT INFO field (#31) from the\n4. A problem was reported by a site where the infusion rate on an order\nwas not being returned to CPRS appropriately. The problem was in the\nmessaging routines, which always expected there to be a space between the\nnumeric rate and the text of the rate. This patch corrects this problem.\nNOIS# CON-0900-11408.\n \n5. A site reported a problem when editing the orderable item in the\nInpatient Order Entry [PSJ OE] option. The stop date is not being set\ncorrectly. This patch corrects this problem by recalculating the stop date\nfor an order if the orderable item is changed. NOIS# BOI-1299-51410.\nPHARMACY PATIENT file (#55) be passed to Computerized Patient Record\n \n6. A site reported a problem where editing an order caused a new order\nto be generated with a new stop date, but the user had no indication that\na new stop date was calculated. This patch corrects this problem by\nchanging the display of the stop date to indicate the entry was modified\n(for unit dose orders only). NOIS# NAS-0600-31201.\n \n7. There are two cases where a prompt can be modified when editing an\nactive order and the display will not highlight the change before asking\nthe user to accept the changes. The two prompts are "Admin Times:" and\nSystem (CPRS) to be displayed on the Orders Tab. With the installation of\n"Stop:". This patch corrects this problem by modifying the display\nroutine to highlight these fields if they are modified (for unit dose\norders only).\n \n8. When editing either the stop date or the start date for a one-time\norder, under most conditions, the other entry will also be changed. This\npatch corrects this problem by modifying the entry process to only edit\nthe field selected, not both the stop and start date. Note: one of the\nrequirements to correct this was to delete the triggers from the\nNON-VERIFIED ORDERS file (#53.1), START DATE/TIME field (#10).\nthis patch Inpatient Medications will begin passing this information to\nNOIS# BOI-1299-51410.\n \n9. Several sites have reported issues with the calculation of the start\ndate when an order is renewed. Specifically, dealing with displaying\norders on the Bar Code Medication Administration (BCMA) Virtual Due List.\nThis patch changes the calculation of the start date for a renewed order\nto use the following logic: If BCMA has marked the drug as given against\na scheduled administration time, take the administration time and add the\nfrequency. If the time is in the future, use this as the start date for\nthe order. This will be true even for a non-standard schedule if the\nCPRS. NOIS# BHH-0700-42241.\nuser enters administration times. If the drug is marked as given, but\nthere is no associated scheduled administration time, take the time the\ndrug was given, add the frequency and round up to the next hour. If the\ntime is in the future, use this as the start date for the order. If the\ntime calculated in either case, is in the past, if the drug was never\ngiven or the drug was marked as held, the current calculation logic will\nbe used and the start date will be determined by the ward parameters.\nPlease note: this logic will apply to regular renew and regular finish.\nSpeed renew and speed finish will not be effected. NOIS# NCH-0700-41081.\n \n \n10. A site reported a problem with editing multiple one-time orders for a\npatient. The problem was that the edit of the stop date on the first\norder was stored correctly, but not on the following orders. This patch\ncorrects this problem. NOIS# BOI-0700-51308.\n \n11. A problem was reported where a pharmacist was finishing an order for a\npatient and specifying that the order was a self-med. When the pharmacist\nreviewed the order afterwards the self-med designation was not showing.\nThe pharmacist then had to go back and edit the order again and designate\nit as self-med. This patch corrects this problem.\n2. A problem was reported by a site where the UD PROVIDER field (#62.02)\nNOIS# LEB-0700-21514.\n \n12. A problem was reported where a site was unable to renew IV Fluid\norders thru CPRS. These orders originated from backdoor Inpatient\nMedications options. The provider would receive a message that the\ninfusion rate was invalid. This patch corrects this problem.\nNOIS# ANN-0900-40829.\n \n13. A site reported a problem with the calculation of the start date for\nan order with a schedule such as QOD. If the order was placed after the\nof the PHARMACY PATIENT file (#55) was not being updated or the provider\nadministration time for the day had passed, and the start date was set to\nbegin at the next administration time, the order was scheduled to start in\ntwo days. This patch corrects this problem by making the start date be\nthe next day at the scheduled administration time. NOIS# MAR-1000-20645.\n \n14. A site reported a problem with the MAR labels printing when a pharmacy\ntechnician edited an order even though labels were only supposed to print\non pharmacist verification. This patch corrects this problem.\nNOIS# CTX-1199-72489.\n\n
\n1. A problem was reported by a site where the Medication Administration\nschedule type and IM was determining a pseudo schedule type for IV orders,\nif the start and stop date/times were the same it was a one time order, if\nthe schedule contained "PRN" it was a PRN order, otherwise it was\ncontinuous. Now IM will also set IV orders with a schedule of TODAY,\nONCE, NOW, ONE TIME, ONE-TIME, 1 TIME, 1TIME, 1-TIME, and STAT as one time\norders. NOIS# WPB-0101-30986.\n \n3. On the BCMA Workgroup call, it was requested that IM start returning an\nadditional pseudo schedule type for IV orders. The new pseudo schedule\ntype will be ON CALL. IV orders with ON CALL, ON-CALL, or ONCALL in the\nHistory (MAH) in Bar Code Medication Administration (BCMA) was showing the\nschedule field will be returned to BCMA in the API with a pseudo schedule\ntype of 'OC'.\n \n4. An obsolete reference to a variable pointer definition was found in the\nMARS LABELS file (#53.41). This patch corrects this problem by removing\nthe obsolete reference from the data dictionary.\nwrong initials for the pharmacist. This patch will correct this problem.\nNOIS# HUN-0900-21331.\n \n2. A problem was reported by a site where they were receiving emails from\nthe BCMA software regarding IV orders which were not being displayed on\nthe Virtual Due List (VDL). The problem was with the API routines that\nInpatient Medications (IM) supplies to BCMA. IV orders don't have a\n\n
\n1. A problem was reported by sites where, under certain circumstances,\nundefined errors. This patch corrects this problem by defining the\nvariable if it has not already been defined.\nNOIS# LAH-0401-61509, BRX-0600-12114, and LIT-0600-71001.\nIV orders which are finished using the Non-Verified/Pending Orders [PSJU\nVBW] option cause an undefined P(17) error to occur. Since the problem\ncannot be reproduced on demand, this patch will address this problem by\ninforming the user an error occurred and that their changes will not be\nsaved, and then allowing the user to exit the option gracefully.\nNOIS #LAH-0401-61827, PAL-0701-60050.\n \n2. Three sites reported a problem with the date variable PSGDT causing\n\n
\n1. The Pharmacy Ordering Enhancements (POE) project provides enhancements\nInpatient Medications and Outpatient Pharmacy applications. This project\ndirectly supports Computerized Patient Record System (CPRS), which is a\nkey component of Veterans Health Administration's (VHA) plan to expand\nsupport for clinical operations. Additionally, order checks will be\nprovided for medication orders for which a dispense drug has not been\nselected during the CPRS order entry process. It is also intended as a way\nto help meet the goal outlined in Objective 8, Action 1 in the\nPrescription for Change, which outlines the need to coordinate\nnational/Veterans Integrated Service Network (VISN) formularies and share\ndrug treatment guideline information. This project will promote system-\nto Pharmacy Data Management (PDM) V. 1.0, Inpatient Medications V. 5.0,\nwide sharing of drug reviews and treatment guidelines thereby enhancing\npatient safety.\n \nThis project consists of four patches that work together to accomplish\nthese goals listed in order of install:\n \n PSO*7*46\n OR*3*94\n PSS*1*38\n PSJ*5*50\nOutpatient Pharmacy V. 7.0, and Order Entry/Results Reporting (OE/RR) V.\n \n2. A problem was reported by a site when an order was placed through the\nInpatient Medications dialogue. When pharmacy finished the order, they\nwere prompted to finish as either IV or Unit Dose. If the user chose to\nfinish this as an IV, a new order was created. With the installation of\nthe POE project a new order will no longer be created. This patch corrects\nthis problem. NOIS# WNY-0498-10040.\n \n3. A problem was found when entering a "P" at the Start Date/Time prompt\nfor a Unit Dose order. The user always received the message "No other\n3.0 medication ordering dialogues to eliminate redundant entry of drug\norder found with this drug.", even if there was another order with the\nsame orderable item. This patch corrects this problem.\n \n4. Inpatient Medications will be adding a new parameter to the PHARMACY\nSYSTEM file (#59.7). The parameter will be 'CALC UNITS NEEDED PRN ORDERS'.\nThe parameter will allow for the calculation of UNITS NEEDED on the Pick\nList for orders with PRN in the schedule. Currently orders with PRN in\nthe schedule are shown on the Pick List with a UNITS NEEDED of 0. This\nfunctionality was requested in E3R #12078, which had been reviewed and\napproved by the Inpatient Medications E3R Workgroup and assigned a\ninformation during medication order entry, provide a more consistent\npriority of low. With the changes in CPRS for the POE project to include\nthe PRN button, it was felt that this should be addressed now since the\npotential exists for Inpatient Medications to receive more orders with PRN\nin the schedule.\n \n5. A problem was reported by a site where they had a schedule of\nAPPLY@09/REMOVE@21 in their ADMINISTRATION SCHEDULE file (#51.1) and the\nadmin times were not defaulting into the order when it was finished. This\npatch corrects this problem. NOIS# SPO-0101-50812.\n \nmedication order entry process, provide expanded order checking, display\n6. A problem was reported by a site where they had a schedule of Q3MONTHS\nin the ADMINISTRATION SCHEDULE file (#51.1) and the frequency was\ncalculated as 1440, which would be a daily schedule. Changes were made in\nPharmacy Data Management (PDM), Bar Code Medication Administration (BCMA),\nand Inpatient Medications to tighten up the code, which calculates the\nfrequency of the orders. This patch corrects the Inpatient Medications\nportion of the problem. PSS*1*38 addresses the same issue in PDM. NOIS#\nSHE-1200-51826.\n \n7. E3R# 15571 asks that the Pick List round up the units per dose to the\ndocumented drug formulary statuses and corresponding\nnext whole number if it is not a whole number and use this to calculate\nthe number of doses needed for an order.\nrestriction/guidelines to the provider and pharmacist at the time of order\nentry, and improve the process of medication order transfer between\n\n
\n1. This patch makes changes to print a four digit year on all MARS, Action\n \n3. An undefined variable error was occurring on the Action Profile #1\nreport if the patient didn't have a room/bed assignment. This patch makes\na change to routine PSGAP0 to correct this.\n \n4. A problem was reported on the 14 Day MAR report. If MARs for multiple\npatients were being printed, the patient's initials in the order label\nwere sometimes printing incorrectly. This patch makes a change to routine\nPSGMAR1 and PSGMMAR1 to correct this.\n \nprofile 1 and 2, and Authorized Absense/Discharge Summary report. This\n5. A problem was reported that after installation of Adverse Reaction\nTracking patch GMRA*4*10, the No Known Allergies (NKA) message was not\nprinting correctly on the MAR sheets. This patch makes a change so that\nthe NKA message will print appropriately with or without GMRA*4*10 being\ninstalled.\naction is taken to prepare for the year 2000.\n \n2. A problem was reported in Inpatient Medications version 4.5 for the\nAction Profile #1 report. If only five or six orders printed for a\npatient, extra lines didn't print in the "Additional Medication Orders"\nsection for the physician to enter notes or additional orders. This patch\nwill correct this for Inpatient Medications version 5.0.\n\n
\n1. A site reported a problem where a one-time order could not be\nsystem parameter is not defined, the system will use the continuous order\nparameters to determine the stop date, rather than the start and stop date\nbeing equal. Then, when BCMA marks the medication as 'Given', Inpatient\nMedications will expire the order. NOIS# BUT-0501-20609\n \n2. Inpatient Medications has been asked to add the BCMA Last Action to the\norder view screen. Users will begin to see BCMA ORDER LAST ACTION\nMM/DD/YY HH:MM BCMA ACTION upon installation of this patch on the line\nfollowing the Med Route information. If the line ends with an * that\nmeans that the BCMA Last Action was not made against this order, but\ndiscontinued by the provider because it was expired due to the start and\nagainst the previous order this order was created from due to a change or\nrenewal.\n \n3. A problem was found with the date calculation for the start date for\nrenewal orders in PSJ*5*47. Please note: PSJ*5*47 should not be removed.\nIf the frequency for the order was a time other than an even number of\nhours and the expected time for the new order to start was either 10am or\n8pm, the date/time format stored internally contained a trailing 0. This\nis an invalid date format. This patch corrects this problem. In addition\nto correcting the date calculation, there is a cleanup routine to correct\nstop date being the same. However, the medication still displayed in Bar\nany problems in the current data. The cleanup has two phases. First, the\ndata is analyzed to determine if there are any problems. When the\nanalysis is complete, the person who installed the patch will receive a\nmail message, "INPATIENT MEDS ORDER CHECK COMPLETED", indicating the check\nhas completed. If errors are found, the cleanup is performed and a second\nmessage, "INPATIENT MEDS ORDER CLEANUP COMPLETED", is sent to the\ninstaller indicating that cleanup is complete. The messages are\ninformational only. No action is required. NOIS# DAY-0701-41935\n \n4. With the release of the Pharmacy Ordering Enhancements patches, two\nCode Medication Administration (BCMA) V. 1.0 because of the 12-hour rule\nspaces were allowed in the schedule field. In testing, it was discovered\nthat a user could enter the two spaces at the end of the schedule and it\nwas accepted by the software. The software was not intended to work this\nway. Upon installation of this patch, the trailing spaces will be\nstripped off the text the user enters at the schedule prompt.\nfor displaying one-time orders on the Virtual Due List. This patch\ncorrects this problem by changing the way the stop date for one-time\norders is calculated. There will be a ward parameter, system parameter and\nthe standard calculation. The hierarchy will be to check the one-time ward\nparameter first, if not defined, check the system parameter. If the\n\n
\n1. A site reported a problem with the calculation of the start date for\nproblems. When the analysis is complete, the person who installed the\npatch will receive a MailMan message, "INPATIENT MEDS ORDER CHECK\nCOMPLETED", indicating the check has completed. If errors are found, the\ncleanup is performed and a second message, "INPATIENT MEDS ORDER CLEANUP\nCOMPLETED", is sent to the installer indicating that cleanup is complete\nwith a listing of the effected patients and the orders. The list is\nprovided so that personnel can ensure the patients received their\nmedications.\n \n2. During testing of the changes for one-time orders it was discovered\nrenewal orders. If the start date/time calculated fell between midnight\nthat the schedule was overriding the schedule type on Unit Dose orders.\nFor Unit Dose orders, the schedule type should take precedence. This\npatch corrects this problem.\nand 1:00am, the time was truncated from the VA FileMan date and time. The\nproblem with these orders is that they will not appear on the Bar Code\nMedication Administration (BCMA) V. 1.0 Virtual Due List (VDL) nor will\nthey appear on the Missed Medications Report. In addition to correcting\nthe date calculation, there is a cleanup routine to correct any problems\nin the current data. The cleanup has two phases. First, the orders with a\nstop date no older than 30 days are analyzed to determine if there are any\n\n
\n****************************************************************\norder to select a new patient. Justification is that it works this way in\nOutpatient Pharmacy V. 7.0 and should work similarly in Inpatient\nMedications V. 5.0. This patch will implement the requested functionality.\nNOIS# ISL-0800-50420.\n \n2. E3R #12370 - FORCE SECOND SCREEN TO DISPLAY WHEN FINISHING ORDERS WITH\nORDER CHECKS. The E3R describes forcing the view of Computerized Patient\nRecord System (CPRS) V. 1.0 order checks, when present, on screen two of\norder finishing regardless of backdoor pharmacy order checks. This patch\nwill implement the requested functionality.\n**** Pharmacy Ordering Enhancements (POE) ****\n \n3. The Inpatient Order Entry [PSJ OE] option, following the completion of \nan order, does not perform patient locking at the "Select DRUG:" prompt.\nThe option continues processing orders for the patient previously selected\nbut does not maintain a lock on the patient, allowing a pharmacist and\nclinician to order meds on the same patient at the same time. This\npatch resolves this problem by removing the "Select Drug:" prompt and\nforcing users to use the New Order Entry action. NOIS# ISL-0800-50420.\n \n4. Several sites have reported problems with the entry of the infusion\n**** MUST BE INSTALLED ****\nrate through CPRS V. 1.0 and the infusion rate returned to CPRS V. 1.0 by\nInpatient Medications V. 5.0. This patch will correct these problems.\nNOIS# LOU-0501-42191 and DAY-1298-40645.\n \n5. An undefined error, <UNDEFINED>EN+2^PSJO1 occurs during the Order Entry\n[PSJU NE] option when a patient name is entered, then New Order Entry\naction is selected at the "Select Action:" prompt, then a drug is entered,\nthen "^" is entered at the "DOSAGE ORDERED:" prompt, and either "^" or ""\nare entered at the "Select DRUG:" prompt. This patch fixes this problem by\nensuring required variables are set up regardless of whether the New Order\n**** prior to installing this patch. ****\nEntry action is selected before or after the View Profile action.\n \n6. A problem was reported with the API that returns the activity log\ninformation to BCMA for Unit Dose orders. The first entry in the activity\nlog was not being returned. This patch corrects this problem.\n \n7. A site reported a problem with the display of Restriction Guidelines\nduring Order Entry in Inpatient Medications V. 5.0. The change will allow\nthe user to abort the display with '^' when the display is more than one\npage. Platinum project 3R211M-04-180. (PSJDIN)\n****************************************************************\n \n8. A site reported a problem with the display in the DOSAGE ORDERED\ncolumn on the BCMA Virtual Due List. For certain IV orders, it was\ndisplaying an incorrect amount. DOSAGE ORDERED is not used for IV\norders; in fact, the field cannot be accessed from the IV view of the\npatient's orders. However, when a provider enters an order in CPRS V. 1.0\nas a unit dose order, there is a DOSAGE field. If that order is then\nfinished in pharmacy as an IV, the data remains in the global but is no\nlonger accessible. However, it was still being sent to BCMA in the API.\nThis patch resolves this problem by no longer sending this in the API.\n \nNOIS# SLC-0801-50680\n \n9. A request was made by the Computerized Patient Record System (CPRS) to\nmodify an Inpatient Medications V. 5.0 procedure call that returns order\nchecking information. The modification contained in this patch will help\nCPRS accurately associate the CPRS order with its corresponding order\nchecks and identify the order as having originated from either Inpatient\nMedications V. 5.0 or Outpatient Pharmacy V. 7.0. Patches OR*3*123 and\nPSO*7.0*81 must also be installed for this change to go into effect.\nThe original NOIS submitted to CPRS is DUR-0801-32713. \n1. E3R #11794 - RETURN TO MED PROFILE AFTER ORDER ENTRY- The E3R suggests\n \n10. During the testing of the Pharmacy Order Enhancement patches a site \nreported a problem on their IV Fluid orders that were placed through CPRS.\nThere were times when the additive or solution defaulted in the order \nwere inactive. An additional check was added to PSJHL4 to screen out \ninactive additives and solutions from the ones defaulted into the order.\n \n11. A site reported a problem with the validation of day of week\nschedules for IV orders. This patch corrects this problem.\nNOIS# MIN-1001-41563 \nthe following: after order entry, return the user to the profile view of\nthe patient's orders and require that they quit out of the profile in\n\n
\n1. A site reported receiving an error when attempting to print a\nediting the original order, not the newly copied order. This patch\ncorrects the problem by preserving the original order's dispense drug.\nNOIS# ANN-1201-40453\n \n3. A site reported a problem when running the Patients on Specific\nDrug(s) [PSJ PDV] option and selecting List by (O)rderable Item. The\nInactive Date for the Orderable Item was no longer being displayed as an\nidentifier. This patch corrects this problem. NOIS# PAL-1101-62555.\n \n4. A site reported a problem with the Pick List [PSJU PL] option. After\nMedication Administration Record (MAR) for an IV order that contained\ninstalling the Pharmacy Ordering Enhancements, each order's Special\nInstructions no longer appear on the Pick List. This patch corrects the\nproblem by displaying the Special Instructions on the Pick List.\nNOIS# WRJ-1201-11762.\n \n5. A site reported a problem with the stop date calculation when\nfinishing IV orders. The stop date for the one-time orders was being\nused for all following orders. This patch corrects this problem by\nexcluding one-time orders from the stop date calculation when the IV site\nparameter specifies that all orders should have the same stop date.\nadministration times. This patch corrects this problem by modifying MAR\nNOIS# SAG-1201-40283.\n \n6. A site reported a problem with the editing of an order's dispense drug.\nMultiple dispense drugs can be added to the order, but the ability to edit\nor delete incorrect dispense drugs no longer exists. This patch corrects\nthis problem by allowing dispense drugs to be edited and deleted.\nNOIS# UNY-1001-12315.\n \n7. If a pending order can be finished as either Unit Dose or IV, user\nwith the PSJ RNFINISH key can't finish the order as Unit Dose. This\nprint to ignore administration times for IV orders, unless they are\npatch will allow the nurses to finish Inpatient Med orders as Unit Dose\norders. NOIS: BHH-0102-40058.\nPiggyback, Chemotherapy Piggyback or Intermittent Syringe orders.\nNOIS# CLE-0901-41216\n \n2. A site reported receiving an error when attempting to edit an order\nimmediately after copying it to a new order. The error only occurs when\n\n
\n1. A site reported a problem when editing the orderable item in the\nprint history to a printer. NOIS# ALB-0501-50053.\n \n3. A site reported a problem where inactive dispense drugs were displayed\nduring a '?' lookup at the Inpatient Order Entry [PSJ OE] option. This\npatch will correct the problem by removing drugs from the display that\nhave an inactive date prior to the current date.\nNOIS# WPB-0901-32173.\n \n4. A site reported a problem with the SPECIAL INSTRUCTIONS sub-field (#8)\nwithin the UNIT DOSE multiple (#62) in the PHARMACY PATIENT file (#55).\nInpatient Order Entry [PSJ OE] option. The stop date is not being set\nEdits to this field are not sent properly to the Computerized Patient\nRecord System (CPRS) V. 1.0 under the following circumstances:\n 1) user holds the PSJ RNURSE key and no other pharmacy keys\n 2) place a new order with special instructions and accept and verify it\n 3) go back in and edit the special instructions (verify option inactive)\nThe resulting order's special instructions display differently on the Meds\ntab and Orders tab in CPRS. This patch corrects the problem.\nNOIS# BOI-0901-51460.\n \n5. The Inpatient Medications E3R Workgroup approved a change to the\ncorrectly. This patch corrects this problem by recalculating the stop date\nInpatient Order Entry [PSJ OE] option View Profile activity that would\ncontinue to support placing the DISPENSE DRUG multiple (#2) within the\nUNIT DOSE multiple (#62) in the PHARMACY PATIENT file (#55) on screen 1 of\nthe order view if it is a single entry. If multiple dispense drugs\nare entered, all the dispense drugs will be displayed on the second\nscreen. This patch will implement the requested change.\nE3R# 16130.\n \n6. During internal testing, it was discovered that there was a problem\nwith the entry of MED ROUTE in Abbreviated Order Entry. Even if the\nfor an order if the orderable item is changed.\ndefault is accepted for MED ROUTE, a lookup is still shown and a\nselection is required. This has been corrected in this patch.\n \n7. A site reported a problem with being allowed to edit an order and make\nthe start date after the stop date. This patch corrects this problem.\nNOIS# WIM-0801-20934\n \n8. A site reported a problem with a variable name in the routine\nPSJLIVFD being misspelled. This patch corrects this problem.\nNOIS# PUG-1101-50620\nNOIS# BOI-1299-51410.\n \n9. During internal testing, it was discovered that in backdoor order\nentry, if a one-time schedule was entered, the schedule type was changed\nto one-time, but the display didn't reflect the change until after the\nuser accepted the order. This patch corrects this problem.\n \n2. A site reported receiving an error when attempting to print history to\na printer from the Activity Logs (AL) action of the Inpatient Order Entry\n[PSJ OE] option. This patch corrects this problem and allows the user to\n\n
\n1. A site reported inappropriately receiving the error message, "Dosage\ncriteria will be a range of dates. Included in the report is the total\nnumber of times the particular free text dosage occurred during the\nselected time period, the name of the provider or providers responsible\nfor entering the free text dosage, and the number of occurrences for each\nprovider. The Free Text Dosage Report [PSJU DOSAGE REPORT] option has been\nadded to the Reports Menu [PSJU REPORTS] option.\n \n3. A site reported a problem with the Inpatient Medications V. 5.0 labels\nprinted through Computerized Patient Record System (CPRS) V. 1.0. If the\nUnit Dose order had a schedule type of Fill On Request, the admin times\nOrdered and Dispense Drug are not compatible" while attempting to finish\nwere not printing on the label printed by CPRS. This patch corrects this\nproblem. NOIS# MAN-0200-11846.\n \n4. A site reported a problem with the schedule type when finishing\norders. The problem was that there was an inconsistency between\nfinishing orders and backdoor order entry. This patch corrects this\nproblem. NOIS# BIG-0901-71799\n \n5. Several sites have reported, after the installation of Pharmacy\nOrdering Enhancements, that they are unable to use their Quick Codes to\nan order. This message displayed when the order's dosage contained a\nfinish IV orders placed through CPRS. This patch corrects this problem.\nNOIS# MIW-1101-41809 and POR-1101-52536.\n \n6. A technician gets the following message: "...Order deleted....Order\ndeleted." when trying to enter IV orders at the Inpatient Order Entry [PSJ\nOE] option. The problem occurs if "^" is entered to stop the VA FileMan\nlisting of solutions at the "Select SOLUTION:" prompt. Upon receiving "^"\nas input, the option behaves as if the "^" was entered at the "SOLUTION:"\nprompt and deletes the order. This patch will correct this problem by only\nallowing deletion of the order if "^" is entered at the "SOLUTION:"\nnumeric value that appeared in the dose more than once. For example:\nprompt. Entering "^" at the "'^' TO STOP:" prompt will only abort the VA\nFileMan listing. NOIS# AMA-0801-70377.\n \n7. In finishing a unit dose order, if the pharmacist edited Dispense\nDrug and Dosage Ordered at the same time, a warning message was displayed\nstating the dosage did not match, the available dosages list displayed,\nand the user became stuck in a loop. This patch will correct this problem.\nNOIS# PTH-0102-21320.\n \n8. A site reported a problem with administration times when Quick Codes\n1MG/1ML, 2ML/2VIAL, and 3MG/33ML. This patch corrects the problem. NOIS#\nwere used for IV Piggyback orders in the Inpatient Order Entry [PSJ OE]\noption. If a schedule is defined for the Quick Code, but no administration\ntimes are defined, and appropriate administration times cannot be derived\nfrom the IV additive, administration times should default from the ward\nparameters. The administration times were not defaulting properly from the\nward parameters. This patch corrects the problem. \nNOIS# HWH-0102-41454 and NOIS# HWH-0102-41770\nMAC-1101-60243.\n \n2. A site has requested a report that lists orders containing free\ntext dosages. The report will be sorted by drug, and the selection\n\n
\nA site reported a problem with IV orders that were using non-standard\nmessage, "INPATIENT MEDS ORDER CHECK COMPLETED", indicating the check has\ncompleted. If errors are found, the cleanup is performed and a second\nmessage, "INPATIENT MEDS ORDER CLEANUP COMPLETED", is sent to the\ninstaller indicating that cleanup is complete with a listing of the\neffected patients and the orders. The list is provided so that personnel\ncan ensure the patients received their medications appropriately.\nNOIS: IND-0202-40345 \nschedules. If a schedule was Q18H or Q36H, it would appear as due every\n24 hours, rather than 18 or 36, respectively. This would only happen on\nIV orders placed through the Computerized Patient Record System V. 1.0\n(CPRS). This patch corrects this problem. In addition to correcting the\nfrequency calculation, there is a cleanup routine to correct any problems\nin the current data. The cleanup has two phases. First, the orders with a\nstart date after the installation of PSJ*5*50. When the analysis is\ncomplete, the person who installed the patch will receive a MailMan\n\n
\n1. If the Orderable Item within a unit dose order is re-matched to a new \nchanged for IV orders to return a 0 for a non-renewable order and a 1 for\na renewable order. The Unit Dose functionality will not be affected.\n \n3. A problem was reported where a site was discontinuing IV and Unit Dose \norders with a Nature of Order of Duplicate. When the user viewed the \norders on the CPRS Orders Tab, the Reason for DC was showing on some \norders as ORDER CANCELED, ORDER DISCONTINUED, or DUPLICATE. With the\ninstallation of this patch, the Reason for DC should show as DUPLICATE for\nall orders discontinued where the Nature of Order selected is Duplicate.\nNOIS# BHH-0202-40835.\nOrderable Item due to dosage form change or any other reason, the new \nOrderable Item will replace the existing Orderable Item in the order when\nthe current order is renewed. NOIS# ISB-0202-30541.\n \n2. Currently, Inpatient Medications V. 5.0 supplies an API #3243,\nsupporting the call $$ACTIVE^PSJORREN, to Computerized Patient Record\nSystem (CPRS) V. 1.0, which enables them to determine whether an \nInpatient Medications order is renewable. This functionality will be\n\n
\n1. A problem was reported where orders entered via Computerized Patient \ndisplay, the user is prompted to enter a new patient without being given\nthe opportunity to continue to edit the current patient. This patch\ncorrects this problem by returning the user to the Patient Information\nscreen after displaying the 'NO ORDERS FOUND' message.\nNOIS # REN-0202-61475.\n \n3. A site reported a problem with the Inpatient Order Entry [PSJ OE]\noption. If the Orderable Item was edited, a message was displayed\ninforming the user that the Dispense Drug and Dosage would be deleted if\nthe user continued to edit the order, while nothing would change if the\nRecord System (CPRS) were not always being filed in the appropriate \nuser cancelled the edit. This message was in error as the Dispense Drug\nand Dosage were deleted regardless of the user's actions. This patch\ncorrects this problem by displaying the warning message earlier in the\nedit to allow the user to cancel the edit before the order is changed.\nNOIS # OKL-0202-72069. \n \n4. A site reported a problem with the Inpatient Order Entry [PSJ OE]\noption. Under certain circumstances, the patient's order profile could not\nbe viewed because the VP View Profile action was not selectable. This\npatch corrects this problem by allowing the profile view of the patient's\nmanner in the NON-VERIFIED ORDERS file (#53.1). The orders were being \norders to be viewed when appropriate.\nNOIS # STX-0202-72021.\n \n5. A site reported a problem with the strength of the drug displaying on \nthe Orders Tab in CPRS for orders that had been renewed. The problem \nresulted from message segments longer than 245 characters not being split \nappropriately. This patch will correct this problem.\nNOIS LOU-0202-42178.\n \n6. If the user answers "NO" at the "Do you want to copy this order? No//"\nfiled in such a way that the pharmacist couldn't finish them to be \nprompt when using the hidden action COPY, the variable PSGPDRG became \nundefined when the user accepting the original order after it was edited.\nNOIS OKL-0202-72417.\ndispensed from the IV or Unit Dose package. This patch will correct this\nproblem. NOIS # BEC-0202-20544 & PAL-0202-61440.\n \n2. A site reported a problem with the Inpatient Order Entry [PSJ OE]\noption. When viewing a patient's profile, if the patient has no orders to\n\n
\n1. When using the Standard Schedule Edit [PSS SCHEDULE EDIT] option, the \nNOIS# REN-0302-60743.\n \n3. A site reported a problem that occurred during the finishing process\nin the Inpatient Order Entry [PSJ OE] option. When an IV Quick Code was\nused to finish an IV Piggyback order, an error occurred that prevented\nthe user from finishing the order. This patch corrects the problem.\nNOIS# MAR-0302-20770.\nsoftware is not allowing the users to set the "TYPE OF SCHEDULE" to "Day\nOf Week" for entries such as "MO-WE-FR@09". The time on the end of the\nschedule name was causing the problem. This patch fixes this problem. \nNOIS# BUT-0202-21128, CLE-0202-40858, and ASH-0202-30433.\n \n2. A site reported a problem with the Free Text Dosage Report [PSJU\nDOSAGE REPORT] option. An error caused the report to halt prior to\ncompletion. This patch corrects the problem.\n\n
\n1. If an order contained a dispense drug marked as inactive in the DRUG\norder, it was still checked for validity. After installing this patch\ndrugs marked as inactive within an order are not checked.\n \n \n3. If a pharmacist or nurse who had AUTO-VERIFY disabled renewed a Unit\nDose order, the order was created as non-verified. This patch will cause\norders created due to renew by a pharmacist or nurse in pharmacy to be\ncreated as active. \n \n4. An error would occur if an order containing an inactive dispense drug\nfile (#50), a message stating "(ONE OR ALL DISPENSE DRUGS ARE CURRENTLY\nwas completed using the Speed Finish action in pharmacy. This patch\neliminates the error. \n \n \n5. A ListMan variable (VALMCNT) was getting killed during the Patient\nRecord Update action on a patient's profile screen. If the profile had\nmore that one screen, upon exiting the Patient Record Update edit the\nprofile screen length would be incorrectly reduced.\n \n \nLISTED AS INACTIVE OR DO NOT MATCH THE ORDERABLE ITEM FOR THIS ORDER.)"\n6. When the user chose a range of orders to finish from any profile\nscreen a "^" or "^^" entered at any order would not let the user exit from\nthis list. A change was made to ensure that the user can exit at any time\nfrom their chosen list of orders by entering "^^" or "^".\n \n \n7. If an order entered through Computerized Patient Record System (CPRS)\nmet the criteria:\na) The Orderable Item has a default Schedule Type entered. \nb) An order entered through CPRS contains "PRN" in the SCHEDULE field.\nwas displayed twice. This patch eliminates this message and instead\nWhen this order was finished the SCHEDULE field containing "PRN" was\ncausing the default Schedule Type from the PHARMACY ORDERABLE ITEM file\n(#50.7) to be overwritten with a Schedule Type of "PRN". This patch will\ncorrect this.\n \n \n8. An error occurred when a "-" character was entered at the\nAdministration time prompt when finishing an order. \n \n \ndisplays "INVALID DISPENSE DRUG" or "INVALID ORDERABLE ITEM" in the\n9. A problem occurred when a user's INPATIENT PROFILE ORDER SORT parameter\nwas set to START DATE OF ORDER. Orders that were pending renewals could\nnot be chosen correctly from the profile for Speed Finish.\n \n \n10. A change was made that displays all order check descriptions from CPRS\non the screen when finishing an IV order.\n \n \n11. When finishing a Unit Dose pending order, the Comments field is not\nmessage field of the order display. \ndisplayed on the screen. This patch will display the Comments field and\nallow user to edit this field while finishing order.\n \n \n12. If a non-verified Unit Dose order was edited by a pharmacist and MAR\nlabels were to be generated, an incorrect ^(7) node would be created in\nthe NON-VERIFIED ORDERS file (#53.1). Also, the label generated for the\nnew order would show a reason of "ORDER" instead of "NEW ORDER (EDIT)".\nThis patch corrects these problems and deletes the erroneous ^(7) nodes.\n \n \n13. When finishing a Unit Dose pending order without a dispense drug, the\nuser can only enter one dispense drug and must edit the order to enter\nextra dispense drug. This patch will allow user to enter multiple\ndispense drugs without having to edit the order.\n \n14. Variable XT was undefined when finishing an IV pending order. This\npatch will correct this problem.\n \n2. If a dispense drug was assigned a past inactive date in a Unit Dose\n\n
\n1. A site reported a problem with an inconsistency in the the calculation\n3. A site reported a problem with renewing IV orders. If the original \norder was expired and the Start Date on the new order was edited, the \nStop Date on the original order was also changed. This patch corrects \nthis problem. NOIS# HUN-0102-20878\n \n4. A site reported a problem with one-time IV labels printing in the\nscheduled label job every day, rather than only one time. This patch\ncorrects this problem by only allowing reprints once the label has been\nprinted for a one-time IV order. NOIS# ALB-0102-51931, PHO-0202-60736\n \nof stop dates for one-time Outpatient IV orders. This patch corrects \n5. A site reported a problem with finishing IV orders using the Order\nEntry (IV) [PSJI ORDER] option. If a new order was created as a result of\nedits made during finishing, the "Instructions:" prompt continued to\ndisplay the instructions from the old order. The new order is unique, and\ninstructions from the old order may not apply to the new order. This\npatch corrects the problem by removing the old instructions.\nNOIS# SFC-0102-62594.\n \n6. A site reported a problem with finishing Inpatient IV\nPiggyback orders using the Order Entry (IV) [PSJI ORDER] option. The\nthis problem. NOIS# SPO-0102-50221\nOrderable Item was selectable, but not editable. This patch fixes the\nproblem by allowing the Orderable Item to be edited.\nNOIS# SFC-0102-62594.\n \n7. A site reported a problem with the way IV orders were displayed in the\nprofile view of a patient's orders within the Inpatient Order Entry [PSJ\nOE] option. When an IV order with more than one solution was displayed,\neach solution showed the infusion rate for the order, incorrectly making\nit appear each solution would be infused at that rate. This patch\ncorrects this problem by only displaying the infusion rate next to the\n \nfirst solution.\nNOIS# MIW-0202-41045\n2. During internal testing it was discovered that an IV schedule of \nONETIME was not being marked as a one-time order when sent to Bar Code \nMedication Administration V. 1.0 (BCMA). This patch corrects this \nproblem.\n \n\n
\nAs a part of the Pharmacy Benefits Management (PBM) Extract enhancement\npackages affected since only one installation is necessary. The patches,\nin order of install, are:\n \n PSS*1*52 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*68 INPATIENT MEDICATIONS V. 5.0\n PSO*7*95 OUTPATIENT PHARMACY V. 7.0\n \nUpon completion of the installation of these three patches, the master\nbuild will start a routine that will build the two new fields from\nhistorical data in the PHARMACY PATIENT file (#55). When the build is\nproject, two new fields were added to the PHARMACY PATIENT file (#55).\ncomplete, the user who initiated the install and the members of the\nPSU PBM mail group will receive a message with a subject of BUILD OF FIRST\nPHARMACY SERVICE INFO COMPLETE.\nThey are FIRST SERVICE DATE (#.07) and ACTUAL/HISTORICAL FLAG (#.08).\nWith the addition of these two fields, Inpatient Medications V. 5.0 and\nOutpatient Pharmacy V. 7.0 have been modified to set this information\nwhen the first order for a patient becomes active.\n \nThis project consists of three patches combined in a master build.\nInstallation of this master build should be coordinated among the three\n\n
\n1. A problem was reported by a site where the free text dosage ordered\nentered into an order in Computerized Patient Record System (CPRS) was not\nshowing in the dosage ordered field in Inpatient Medications. The problem\nwas that Inpatient was checking for the free text dosage ordered to be 20\ncharacters or less, this was not compatible with what is allowed in CPRS.\nThe Inpatient Medications check was changed to accept 60 characters or\nless, which is compatible with CPRS. NOIS # DDC-0402-50270.\n\n
\n 1. The Bar Code Medication Administration (BCMA) V. 2.0 release provides \n Med Order button in BCMA V. 2.0.\n names. The subject of this message will be: PSJ*5*58 IV Verification.\n \n Once all of the unresolved names are resolved, another MailMan message \n is generated. This message will instruct the user who ran the Correct\n Change User Names in IV activity log [PSJI ACTIVITY LOG VA200] option to\n contact IRM to remove the option. The subject of this message is Changed\n names in IV orders.\n \n An entry is made in the ACTIVITY LOG multiple (#40) of the IV\n multiple (#100) of the PHARMACY PATIENT file (#55) to indicate the\n \n verification action was performed during the installation of this patch. \n The user in the log entry is the verifying pharmacist determined during\n the conversion.\n This project consists of two patches and a new version of BCMA that work\n together to accomplish these goals listed in order of install:\n \n PSS*1*46 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*58 INPATIENT MEDICATIONS V. 5.0\n BAR CODE MED ADMIN 2.0 BAR CODE MEDICATION ADMINISTRATION V. 2.0\n \n 2. Two sites reported a problem with comments from one IV order\n enhancements to Pharmacy Data Management (PDM) V. 1.0, and Inpatient \n showing up on a different IV order. Since edits to provider comments are\n no longer allowed interactively from within Inpatient Order Entry [PSJ\n OE] option, this patch corrects the problem by removing the code that\n performs updates to provider comments. NOIS# MOU-0100-30945 and\n MAC-1100-61760.\n \n 3. A site reported a problem with an IV order appearing on the profile \n view as a Continuous order when it was a One-time order. This patch \n corrects this problem. NOIS# DUB-0102-32272.\n \n Medications V. 5.0. The BCMA V. 2.0 release expands and improves the\n 4. A correction was made to only allow nurse and pharmacist users to \n Speed Discontinue IV orders. \n \n 5. A correction was made to allow Speed Discontinue Unit Dose orders if \n the status was not "Discontinued", "Discontinued (Edit)" or "Expired".\n \n 6. If a technician or a ward clerk edited a Unit Dose order and caused a\n Non-Verified order to be created, the user was able to discontinue the \n Non-Verified order even if the user parameter "ALLOW USER TO D/C ORDERS:"\n was set to NO, which means the user should only be allowed to mark orders\n process of medication administration, especially in the area of IV\n to be discontinued. This patch corrects this problem.\n \n 7. A site reported an error occurred when copying a Unit Dose order.\n If the user parameter "ORDER ENTRY PROCESS:" was set to WARD and an edit\n was made during copy, the user would error out while accepting the \n change. This patch corrects this problem.\n \n 8. The Test Control Codes (IV) [PSJI CONTROL CODES] option has been added\n to the Label Menu (IV) [PSJI LBLMENU] option. This option allows the user\n to print an IV label for the purpose of verifying their control code\n medications.\n definition. An entire label is not printed, simply a bar code and one\n line of underscores.\n \n 9. A couple of sites reported that the schedule did not display on the\n profile for IV orders when using the Inpatient Profile [PSJ PR] option.\n This patch corrects this problem. NOIS# CON-0302-12151 and \n MAR-0402-21639.\n \n 10. A site reported receiving a null subscript error when an IV order \n came from Computerized Patient Record System (CPRS) V. 1.0 and Inpatient\n \n Medications V. 5.0 was unable to determine the correct solution to place\n in the pending order. The order created had a volume but no solution.\n NOIS# WAS-0402-21482.\n \n 11. While trying to reproduce a problem reported by a site with the \n display of Special Instructions we discovered a problem that could occur\n on orders placed through CPRS when copying Provider Comments into the\n Special Instructions field. If the Provider Comments contained a\n character string that exceeded 70 characters without having a space in \n it the user couldn't see the last several characters on the screen. This\n In support of this, Inpatient Medications V. 5.0 and PDM V. 1.0 have \n patch corrects this problem.\n \n 12. Post-Install will do the following:\n IV verification is now required with the PSJ*5*58 patch. For orders that \n were entered prior to the installation of this patch, an algorithm was \n designed to determine the verifying pharmacist. The verifying user IEN \n is stored in the VERIFYING PHARMACIST sub-field (#140) of the IV multiple\n (#100) of the PHARMACY PATIENT file (#55), which was added with patch \n PSS*1*46. The DATE VERIFIED BY PHARMACIST sub-field (#141)\n of the IV multiple (#100) of the PHARMACY PATIENT file (#55), which has\n added the ability to print barcode identifiers on IV labels, IV order\n also been added with patch PSS*1*46, will reflect the installation date\n and time.\n \n The Activity Log for the IV Order stored the user name in free text.\n During this conversion, the free text user name is compared to the NEW\n PERSON file (#200). If there is an exact and unique match, then the IEN\n for this person is stored in the USER sub-field (#.06) of the ACTIVITY \n LOG multiple (#40) of the IV multiple (#100) of the PHARMACY PATIENT file\n (#55) that was added with patch PSS*1*46.\n \n verification and the ability to receive done priority orders via the CPRS\n If the software is able to determine the user's IEN, for all affected IV \n orders, and no intervention is required, the MailMan message generated \n by the conversion will contain only the conversion information. The\n subject of this message will be: PSJ*5*58 IV Verification.\n \n When the software is unable to determine the user's IEN, the MailMan\n message generated by this conversion will instruct the installer\n to assign the Correct Change User Names in IV activity log [PSJI ACTIVITY\n LOG VA200] option to a holder of the PSJI MGR security key who is \n familiar with the Pharmacy users to allow them to correct the unresolved\n\n
\n1. A site reported a problem with the finish of IV Piggyback orders in the\nthe Inpatient Order Entry [PSJ OE] option. In the past, entry of a two\ndigit or four digit number between 0 and 24 was permitted, but this format\nis currently invalid. This patch corrects the problem by restoring the\npreviously allowed format.\nNOIS # BIG-0302-72850.\n \n3. A site reported a problem with the Patients on Specific Drugs [PSJ\nPDV] report. Orders appeared on the report that were outside the selected\ndate range. This patch corrects the problem by correcting invalid start\nand stop dates if possible. Orders with dates that cannot be corrected\nInpatient Order Entry [PSJ OE] option. The calculation of the default stop\nwill be reported via mail message to the person installing the patch.\nNOIS # MON-0202-52165.\ndate did not recognize the additive's number of days for an IV order. This\ncaused incorrect stop dates to be calculated and displayed. This patch\ncorrects the problem by using the correct parameter to calculate the\ndefault stop date.\nNOIS # CHA-0302-31253.\n \n2. A site reported a problem entering time-based administration times in\n\n
\nDuring testing of Bar Code Medication Administration V. 2.0, it was\ndiscovered that the SIte Parameters (IV) [PSJI SITE PARAMETERS] option did\nnot allow device lookup at the Label Device and Report Device prompts.\nThis patch corrects this problem by using the standard device\nhandling routines to perform device lookup. One side effect is that\nyou can no longer jump to these questions. NOIS# ISB-0302-32189\n\n
\n1. During internal testing, a problem was discovered with the way\nInpatient Order Entry [PSJ OE] option. When an IV Quick Code was used to\nfinish an order, the Provider Comments did not appear in the Other Print\nInfo when the prompt "Copy the Provider Comments into Other Print Info\n(Yes/No/!):" was answered in an affirmative manner. This patch corrects\nthe problem by retaining copied Provider Comments in the Other Print Info\nif the IV Quick Code has no Other Print Info. If the IV Quick Code does\ncontain Other Print Info, it will appear in the order's Other Print Info.\nNOIS # MIN-1101-42563\n \n3. A site reported a problem with IV Quick Codes in IV Piggyback orders.\nRestriction/Guideline(s) were displayed in the Inpatient Order Entry [PSJ\nIf there are no administration times present in the Quick Code, Additive,\nor Ward Parameters, the user is prompted for a schedule with associated\nadministration times. In this instance, the user selected a schedule, but\nthe selected schedule's administration times were not saved with the\norder. This patch corrects the problem by using the administration times\nassociated with the selected schedule when appropriate.\nNOIS # HWH-0102-41454\n \n4. A site reported a problem with the Free Text Dosage Report [PSJU\nDOSAGE REPORT] option. When a free text dosage was encountered that had\nOE] option. The screen was not refreshed after displaying the Restriction/\nbeen ordered by over thirty different physicians, the report did not run\nto completion. This patch corrects the problem by allowing an unlimited\nnumber of physicians to appear for each on dosage the report.\nNOIS # BAY-0402-30987\nGuideline(s), and as a result, drug interactions appeared to scroll under\nthe Restriction/Guideline(s). This patch corrects the problem by clearing\nthe screen before the drug interactions are displayed.\nNOIS # BIR-0302-32554\n \n2. A site reported a problem with finishing IV Quick Code orders in the\n\n
\n1. This patch will make sure active Unit Dose orders are created with a\nINPATIENT MEDS ORDER CLEANUP COMPLETED will inform sites of any unresolved\norders. The user will get the second message if there are any orders with\nno Dispense Drugs. If the first message says there are 0 orders with no\nDispense Drugs, the second message will not be generated.\nDispense Drug in the orders. NOIS: MOU-0102-32301, ANN-0202-42365,\nSPO-0302-51657, MWV-0302-20778, OKL-0402-72901, MIN-0502-40440.\n \n2. A clean-up routine will identify orders without a Dispense Drug and \nmake corrections, if appropriate. The person installing this patch will \nreceive two MailMan messages, the first with the subject: PSJ*5*77\nINPATIENT MEDS ORDER CHECK COMPLETED will tell the user how many orders\nexist with no Dispense Drug, the second with the subject: PSJ*5*77\n\n
\n1. This patch will make sure active Unit Dose orders are created with a\n[PSJI MGR] option. When the user selected the PATIENT: and then tried to\nview the SHORT PROFILE, they would get caught in a loop. NOIS\nMIN-0802-40347.\n \n3. A clean-up routine will identify orders without a Dispense Drug and \nmake corrections, if appropriate. The person installing this patch will \nreceive two MailMan messages, the first with the subject: \nPSJ*5*78 INPATIENT MEDS DISPENSE DRUG ORDER CHECK COMPLETED will tell the \nuser how many orders exist with no Dispense Drug, the second with the \nsubject: PSJ*5*78 INPATIENT MEDS DISPENSE DRUG ORDER CLEANUP COMPLETED \nDispense Drug in the orders. \nwill inform sites of any unresolved orders. The user will get the second \nmessage if there are any orders with no Dispense Drugs. If the first \nmessage says there are 0 orders with no Dispense Drugs, the second \nmessage will not be generated. An additional MailMan message is generated \nwhen Inpatient Medications orders are checked for start, stop, or nurse \nverification dates with trailing zeros. The subject is PSJ*5*78 INPATIENT \nMEDS STOP DATE ORDER CHECK COMPLETED. This message will tell the user how \nmany orders exist with invalid stop dates. The user will get a second \nmessage with the subject PSJ*5*78 INPATIENT MEDS STOP DATE ORDER CLEANUP \nCOMPLETED if there are any orders with invalid stop dates. If the first \n \nmessage says there are 0 orders with invalid stop dates, the second \nmessage will not be generated.\n \n4. When a nurse verified a pending IV order in Computerized Patient \nRecord System (CPRS) V. 1.0, the order was not filed as an IV order in \nInpatient Medications V. 5.0. This patch will update the order \nappropriately in the IV multiple (#100) of the PHARMACY PATIENT file \n(#55).\n2. This patch will ensure that Inpatient Medications orders entered via\nthe Computerized Patient Record System (CPRS) Med Order Button in Bar Code\nMedication Administration (BCMA) V. 2.0 have start, stop, and nurse\nverification dates without trailing zeros. The trailing zeros in the stop\ndate caused users problems when using the Individual Label (IV) [PSJI\nLBLI] option on the Label Menu (IV) [PSJI LBLMENU] option on the IV Menu\n\n
\n1. A site reported a problem with IVPB labels for orders with Day-of-Week \n3. A site reported a problem with IVPB labels for one-time orders. If the \nlabel had already printed, it wouldn't print, but it would still appear \non the manufacturing list. This patch corrects the problem. \nNOIS: UNY-0602-12797 \n \n4. Inpatient Medications was requested by Decision Support System (DSS) to\ninclude a new data element in the array of data that is currently sent to \nDSS. The new data element is the order start date/time. This should be \ntransparent to Inpatient Medications users.\n \nschedules. The problem was that labels were printing even on days when \n5. A potential problem was discovered by developers, where data nodes \ncould be set inappropriately in the Unit Dose multiple of the PHARMACY \nPATIENT file (# 55). This patch corrects this problem.\nthe medication wasn't due. This patch corrects this problem. \nNOIS# MIN-0402-42144\n \n2. A site reported a problem that occurred periodically when an IV order\nwas edited during the finish process. This patch corrects the problem.\nNOIS: MWV-0502-22511\n \n\n
\n1. A request was made to change the default to "No" for the prompt "Is \n \n \n3. A change was made to correct an undefined variable error that \ncould occur when the protocol PSJ OR PAT PR (Inpatient Medications \nProfile) was accessed from the Computerized Patient Record System (CPRS)\noptions.\n \n \n4. A change was made to display the possible IV Identifier when \nchoosing Orderable Items on the Patients on Specific Drug(s) and the \nthe Formulary Alternative acceptable". This will prevent the order \nDrug (Cost and/or Amount) reports.\n \n \n5. The option CAtegory File (IV) [PSJI IVCATEGORY] was mistakenly \nremoved from the SUPervisor's Menu (IV) [PSJI SUPERVISOR] menu \nfor Inpatient Medications 5.0. This option will be reinstalled in this \npatch.\n \n \n6. A change was made on the Action Profile reports. If the IV order \nfrom being finished if an accidental return is hit for this prompt.\ncontains no additives, a blank line will print for the additive and the \nsolutions will print on the following line.\n \n \n2. A change was made to incorporate the expansion text of a schedule \nin the Special Instructions for an order. If the schedule has an \nexpansion text and is used in the Special Instructions, it will now be\ndisplayed in the Special Instructions.\n\n
\n1. During the process of finishing an order, re-entering the same\nupdate. NOIS: ANN-0502-40709\n \n3. A patient that has been transferred to Absent Sick In Hospital (ASIH)\nmay have active orders with start dates prior to the transfer date. If the\ndate and time of the transfer is edited, inpatient orders are\nautomatically discontinued. This causes valid, active orders to be\nimproperly discontinued. This patch corrects the problem. NOIS:\nPAL-0402-61286\n \n4. During internal testing, it was discovered that there were differences\nschedule causes the frequency of the order to be removed. This causes the\nin schedule validation between Unit Dose and IV orders. This patch\ncorrects this problem.\n \n5. It was discovered that there were some inconsistencies with schedule\nvalidation between Inpatient Medications V. 5.0 and Pharmacy Data\nManagement V. 1.0. This patch corrects this problem.\n \n6. A problem occurs if a patient is transferred and new orders are added\n(and orders are not set up to auto-discontinue upon transfer). When the\nupdate is run, the patient appears both on Ward A and Ward B, with old\norder to not display correctly on the Bar Code Medication Administration\norders on the Ward A update and new orders on Ward B update. This patch \ncorrects the problem. E3R: 15221\nVirtual Due List. This patch corrects this problem. NOIS: CMS-0502-32446\n \n2. After an interward transfer, a patient's orders are not displayed in\nthe Update Pick List [PSJU PLUP] option. These transferred orders are\ndisplayed in the regular Pick List [PSJU PL] option. This patch corrects\nthis problem by allowing previously existing orders to display on the\n\n
\nThis patch contains the API to allow Computerized Patient Record System \n(CPRS) to automatically reinstate Inpatient Medication orders that were \nauto discontinued.\n\n
\n1. When a one-time IV order is entered in advance, the scheduled label \n \n4. The Non-Verified/Pending Orders [PSJU VBW] option includes patients \nwith inactive non-verified/pending IV orders. This patch will display \npatients with non-verified/pending IV orders that have future stop dates.\n \n5. When using the Order Entry (IV) [PSJI ORDER] option on an outpatient \nand the second screen was displayed, the user was forced to enter an '^' \nto continue with the order. This patch corrects this problem. NOIS: \nSPO-0302-52679.\n \ndue on the start date is not being printed. This patch will correct this \n6. When a user enters an order through Pharmacy backdoor and answers the\nfollowing question "Is this O.K.: NO//" with a NO, the user will receive a\nnull subscript error. This patch will correct this problem. NOIS: \nAAA-0502-N2276.\n \n7. The PRINT NAME {2} (#.02) field of the IV SOLUTIONS file (#52.7) is not\nbeing sent to Computerized Patient Record System (CPRS) and Bar Code \nMedication Administration (BCMA). This patch will correct this issue. \nNOIS: LEX-0502-41218.\n \nproblem. NOIS: ASH-0402-32138.\n8. A site reported a problem with a one-time order that didn't expire \nafter it had been administered. The problem occurred because the schedule\ntype was Fill on Request. This patch corrects this problem. NOIS: \nNCH-0602-41182.\n \n9. During internal testing, it was discovered that the BCMA API that \nreturns Activity Log information was not sending the user's internal \nentry number for IV orders. This patch corrects this problem.\n \n10. When the ADMINISTRATION SCHEDULE file (#51.1) has a schedule \n \ncontained "PRN", the Unit Dose and IV orders will not display on the Bar \nCode Medication Administration (BCMA) V. 2.0 if the Virtual Due List \n(VDL) had only the PRN box checked. This patch will send the correct \ninformation to BCMA to display the order in the PRN session. NOIS: \nSAM-0702-22338.\n \n11. A site reported a problem with being able to see BCMA ORDER LAST \nACTION on active renewed orders. The BCMA ORDER LAST ACTION was \navailable on the old order, but not on the newly created order. This \npatch will correct this problem. NOIS: MWV-0902-21008.\n2. Code changes were made due to the expiration of IA 903.\n \n3. The Non-Verified/Pending Orders [PSJU VBW] option errors out when \naccessed by users without any pharmacy keys. This patch will correct \nthis problem. NOIS: LOM-0502-62027.\n\n\n1. A site reported a problem with the Order Entry [PSJ NE] option. A new\nE3R 17161.\n \n3. A site reported a problem with not being able to view a renewed \nTotal Parenteral Nutrition (TPN) IV order using the Non-Verified/Pending\nOrders [PSJU VBW] option. This patch will correct this problem.\nNOIS BIR-0602-31411.\n \n4. Labels incorrectly defaulted as Bypass instead of Print when entering a\nOne-Time IVPB without an administration time. It defaulted correctly if \nthere was an administration time. This patch corrects the problem by \norder's default administration time was taken, then edited before\nusing the correct default regardless of the existence of administration \ntimes. NOIS NCH-0602-41567.\n \n5. A site reported a problem with the control code definition. If a\ncontrol code definition was not complete, there was a problem when \nattempting to print IV labels in any option. This patch corrects this\nproblem. NOIS: ISB-0602-32106.\n \n6. A site reported a problem that occurred sporadically when an active \nor non-verified Inpatient order was edited. Under certain circumstances,\nsaving the order. After the order was saved, the administration time\nan error occurred that prevented the user from continuing with the edit.\nThis patch corrects the problem. ANN-0202-41257.\nreverted to its original value. This patch corrects the problem by\ncorrectly preserving the administration time each time it is edited.\nNOIS TUA-0502-32722.\n \n2. A request was made to modify the Pre-Exchange Report to put each \npatient on a separate page. This patch implements this modification. \n\n
\n1. Reprinting of the IV hyperal labels do not have the first line of data\n \n3. The Returns and Destroyed Entry (IV) [PSJI RETURNS] option did not\nproperly update an order's Cumulative Doses. This patch corrects the\nproblem by updating an IV order's Cumulative Doses when a dose is\nRecycled, Destroyed, or Cancelled.\nafter the barcode that prints the order number, last 4 social security \nnumber, ward and date. This patch will correct this issue. NOIS: \nOKL-0802-71191.\n \n2. Inpatient Medications orders which were on hold at the time a patient \nmovement occurred which caused them to be auto-discontinued were not \nreturned to on hold if the movement was deleted and the orders were \nauto-reinstated. This patch corrects this problem. NOIS: AAA-0802-N1994.\n\n
\nWhen performing drug lookups, two issues were identified. First, the user \nsearch will continue through all other items. A sample screen display \nfollows.\n \nSelect DRUG: hep\n Lookup: VA DRUG CLASS CLASSIFICATION\nHEPARIN ANTAGONISTS BL200 \n HEPARIN ANTAGONISTS\n Lookup: DRUG NATIONAL DRUG CLASS\n PROTAMINE SULFATE 5ML INJ BL200 \n ...OK? Yes// N (No)\nwas not aware of which item was being matched. For example, was the match \n \n Lookup: DRUG GENERIC NAME\n 1 HEPARIN 1,000 UNIT/ML 10ML INJ BL100 \n 2 HEPARIN 1,000 UNITS/ML 30ML BL100 \n 3 HEPARIN 10,000 UNITS 4ML BL100 \n 4 HEPARIN BEEF 1,000 UNITS/ML 30ML BL100 \n 5 HEPARIN, LOCK 100 UNIT/ML 1ML BL100 \nPress <RETURN> to see more, '^' to exit this list, OR\nCHOOSE 1-5: \n 6 HEPATITIS-B IMMUNE GLOBULIN IM500\nfor the GENERIC NAME of the drug or was it the SYNONYM. The second issue \nCHOOSE 1-6: \nhad to do with the search matching to the NATIONAL DRUG CLASS NAME first, \nbefore checking for a GENERIC NAME. \n \nThis patch makes two changes to the drug lookup. First, the search will \ndisplay the item being searched on. Second, if a match is found on an \nitem, but the user doesn't select one of the matches displayed, the \n\n
\n1. It was possible to renew a unit dose order when the dispense drug was\nreceive a MailMan message with the subject: PSJ*5*89 INPATIENT MEDS \nORDERABLE ITEMS ORDER CHECK COMPLETED to tell the user of unresolved \norders or of the corrections action.\n \nThe user will receive a message with the content similar to one of the \nexamples below after installing the patch:\n \nEx1:\nSubj: PSJ*5*89 INPATIENT MEDS ORDERABLE ITEMS ORDER CHECK COMPLETED \n[#84808]\nnot matched to an Orderable Item. This caused the order to store a 0 in\n04 Sep 02 10:31 10 lines\nFrom: MEDICATIONS,INPATIENT In 'IN' basket. Page 1\n--------------------------------------------------------------------------\nThe check of existing Pharmacy orders for use with Inpatient\nMedications 5.0 completed as of SEP 4,2002@10:31:55.\n \nThis process checked orders for patients in 0 hours\nand 1 minute.\n \nThe following order(s) are without the Orderable Item. Please contact the\nthe ORDERABLE ITEM field (#108) of the UNIT DOSE subfile (#55.06) of \nNATIONAL HELP DESK for assistance:\n \nDFN: 739 ORDER #: 746U\n \n \nEx2:\nSubj: PSJ*5*89 INPATIENT MEDS ORDERABLE ITEMS ORDER CHECK COMPLETED \n[#84809]\n04 Sep 02 14:06 7 lines\nFrom: MEDICATIONS,INPATIENT In 'IN' basket. Page 1\nthe PHARMACY PATIENT file (#55) and null in the ORDERS FILE ENTRY field\n--------------------------------------------------------------------------\nThe check of existing Pharmacy orders for use with Inpatient\nMedications 5.0 completed as of SEP 4,2002@14:06:54.\n \nThis process checked orders for patients in 0 hours\nand 0 minutes.\n \nThere are no Orderable Items missing from the orders.\n \nEnter message action (in IN basket): Ignore// \n(#66) of the UNIT DOSE subfile (#55.06) of the PHARMACY PATIENT file\n \n \nEx3:\nSubj: PSJ*5*89 INPATIENT MEDS ORDERABLE ITEMS ORDER CHECK COMPLETED \n[#84824]\n05 Sep 02 11:06 7 lines\nFrom: MEDICATIONS,INPATIENT In 'IN' basket. Page 1 *New*\n--------------------------------------------------------------------------\nThe check of existing Pharmacy orders for use with Inpatient\nMedications 5.0 completed as of SEP 5,2002@11:06:33.\n(#55). This patch will correct this problem. NOIS: NCH-0802-42568.\n \nThis process checked orders for patients in 0 hours\nand 0 minutes.\n \nUpdated the orders with the appropriate Orderable Items.\n \nEnter message action (in IN basket): Ignore// \n \n2. A clean-up routine will identify orders without an Orderable Item and \nmake corrections, if appropriate. The person installing this patch will \n\n
\n This patch requires the installation of Bar Code Medication\n order may also expire at any time before the new order's start date and\n time, giving the appearance on the VDL that no medications are being\n actively administered, when actually there is a bag infusing and another\n bag scheduled to start.\n This patch will correct the problem by changing the way the start date\n and time are calculated for continuous IV renewals. If the order being\n renewed is a continuous IV, and the order does not contain a schedule,\n the default start date and time for the order will be set to NOW.\n NOIS #UNY-0802-10109. \n \n Administration (BCMA) V. 2.0.\n 2. If the pharmacist made an edit during the finishing of an IV piggyback\n order that result in a new order, the original order was not \n discontinued. This was cause by a leftover variable. To recreate this \n problem, enter a new backdoor order and answer the following question \n "Is this O.K.: NO//" with a "^". Then select a pending IV order and\n finish it. This patch will correct the problem. NOIS #LIT-0902-72062.\n \n 1. A site reported that continuous IV orders such as admixtures and\n hyperals do not display on the Virtual Due List (VDL) in BCMA V. 2.0 when\n they are renewed. If the DEFAULT START DATE CALCULATION field (#.05)\n in the INPATIENT WARD PARAMETERS file (#59.6) is not set to '2 USE NOW\n AS DEFAULT', the renewal order's default start date may be set far enough\n into the future to allow the order to fall off the VDL. The original\n\n
\nWhen a group of orders were Auto Discontinued due to a Treating Specialty \ntransfer, instead of assigning the Auto DC Date/Time as the orders' Stop \nDate/Time, each order may have different Stop Date/Times. This is the \ncause for only a sub-set of orders to be re-instated. A Computerized \nPatient Record System (CPRS) patch, OR*3*168, along with this patch will \ncorrect this problem. NOIS: LAH-1102-61807.\n\n
\n1. A site reported a problem with the option 14 Day MAR [PSJU 14D MAR]\nMEDS dialog. A site reported a problem with an order received from CPRS \nwhere a schedule should have required and wasn't. This patch corrects \nthis problem. NOIS# BIR-0902-31838.\n \n3. A site reported a problem with an IV order being created without all \nthe appropriate information. The problem was the result of a nurse \nverifying a non-verified unit dose order through CPRS. The unit dose \norder would become active, the routine, which allowed this, was missing a \nquit and the code to create an IV order would be executed without \nappropriate information, resulting in the bad IV order. This patch \nwhere nursing staff print blank mar's for prn's, but they are now having\ncorrects this problem. NOIS# MOU-0902-30038.\n \n4. A site reported a problem with the Activity Log from a non-verified \nunit dose order was not copied over to the active unit dose order when \nnurse verification took place through the CPRS verification option. This \npatch corrects this problem. NOIS# NOL-0902-70884.\n \n5. A site reported a problem with the display of pending hyperal orders. \nThe orders were only displaying a single line on the CPRS orders tab \ninstead of all the additives and solution contained in the order. This \nto do it patient by patient instead of by ward. It works fine by patient,\npatch corrects this problem. NOIS# BHS-1002-10031.\nbut will print nothing for prn's (blank) by ward. This patch corrects\nthis problem. NOIS# DUB-0902-31426.\n \n2. Inpatient Medications provides an application programmer interface \n(API) to Computerized Patient Record System (CPRS) that determines \nwhether a schedule is required for an order placed using the INPATIENT \n\n
\nPharmacy Data Management (PDM) creates the "AUDS" cross-reference on the\nSTART DATE/TIME field (#10) of the UNIT DOSE subfile (#55.06) of the\nPHARMACY PATIENT file (#55). This patch will ensure that cross-reference\nis set when new Unit Dose orders are created and re-index the "AUDS"\ncross-reference for existing orders.\n\n
\n1. The allergy/adverse reaction is currently displayed as <A> on the\naccomplishes the addition of this functionality. In order to use this\nfunctionality, patch OR*3*141 must be installed as well.\n \n3. The order view was not displaying on the Patient Profiles for Unit Dose\norders. Steps for testing: From the Unit Dose Order Entry [PSJU NE]\noption, select a patient and then select an order from that patient's\nprofile. After the order view appears, exit to the Main Menu. Next, choose\nthe PAtient Profile (Unit Dose) [PSJU PR] option and include the expanded\nview on the report. The expanded view of the order should display on the\nprofile.\npatient profile and order view. This patch will display the Crises,\n \n4. Beginning with Inpatient Medications V. 5.0 patch PSJ*5*58, the\nbarcodes are printed on the IV labels. Barcode ID - Return and Destroy\n(IV) [PSJI RETURN BY BARCODE ID] option was added to help pharmacy with\nthe return and destroy of specific IV labels. This new functionality was\nrequested by E3R #17117.\n \n5. The BCMA ORDER LAST ACTION information was not available on patient \nprofiles of Unit Dose orders. This patch will display it on these \noptions: Inpatient Profile [PSJ PR], PAtient Profile (Unit Dose) [PSJU \nWarnings, Allergy and Directive as <CWAD>. A new hidden action CWAD is\nPR] and Patient Profile (Extended) [PSJ EXTP].\n \n6. It was requested in E3Rs # 12841 and # 10796 that Inpatient\nMedications orders display the signature status of the order next to\nthe provider's name. This patch in conjunction with OR*3*141 accomplishes\nthis functionality. If the order has been electronically signed via the\nCPRS V. 1.0 package, [es] will appear after the provider's name. If the\norder has not been electronically signed or if OR*3*141 has not been\ninstalled the user will see the lowercase abbreviation for the Nature of\nOrder enclosed in the brackets after the provider's name (i.e. Written -\nadded to display any patient's Crises, Warnings, Alerts, or advanced\n[w], Telephoned - [p], Verbal - [v], Policy - [i], Electronically Entered\n- [e], or Service Correction [s]).\n \n7. CPRS GUI version displays "No Allergy Assessment" when no allergy is\nfound on file. It was requested in E3R #13013 that Inpatient Medications\nV. 5.0 use the same wording when patient allergies are displayed. This\npatch accomplishes this requested functionality.\n \n8. A problem was discovered with the way certain Day of the Week schedules\nwere handled during order entry. System derived administration times may\nDirectives on file.\nhave defaulted into orders in an improper format if the order was created\nusing a Day of the Week administration schedule with no administration\ntimes defined. The incorrect administration time stored with the order may\nhave been in the form of a single digit number or a three digit number.\nThis patch corrects this problem. NOIS ISB-0902-30741.\n \n9. A site reported a problem with IV Fluid orders entered via CPRS where \nadditives that were not marked for IV Fluid Order Entry in the IV \nADDITIVES file (#52.6) were not being displayed in the pending order. \nThis patch corrects this problem. NOIS MAR-0902-21076.\n \n \n10. When a pharmacist finished and verified an IV Fluid order as an IV \nPiggyback order, it did not show up in CPRS's Active View. This occurred \nonly when the "ALLOW AUTO-VERIFY FOR USER:" prompt in the Inpatient User\nParameters Edit [PSJ SEUP] option is set to "No". This patch will correct\nthis problem. NOIS LIT-1002-70444.\n2. It was requested in the E3Rs #11177 and #12382 that the flagging\ncapability that is available in Computerized Patient Record System (CPRS)\nbe available through the Inpatient Medications options. This patch\n\n
\nThere was a problem reported with the post install routine from \nPSO*7.0*115. This patch processes through the XTMP global created by that \npost install routine and corrects the status field for the IV orders that \nwere effected.\n \nIf the cleanup routine encounters orders that have problems, the person \nwho installed the patch will receive a message indicating this and where \nthe list of problem orders is kept. These should be reviewed to be sure \nthere are no problems with the patient's medication profile.\n\n
\n1. IV orders were originally entered through Computerized Patient Record \n non-verified order.\n 3. Pharmacist changes the strength in the additive but doesn't verify \n it. This leaves it in a Non-Verified status.\n 4. The new strength does not appear on CPRS side.\n \n2. When the OTHER PRINT INFO field (#21) was entered or modified for a \nNon-Verified IV order, this data was not being sent to CPRS. This patch \nwill correct it.\n \n3. An Inpatient Meds order is finished as an admixture with auto-verify \nSystem (CPRS) and finished in Pharmacy, the completed orders were then \nturned off, this creates a non-verified order. When the non-verified \norder displays, a starred field is edited, and the order is accepted; \nthis causes a new order to be created, but the original non-verified \norder is not discontinued. The profile displays two non-verified orders, \nbecause a variable was not being updated correctly. This patch corrects \nthis problem.\nedited through backdoor pharmacy options, the changes made were not \nreflected in CPRS. NOIS: HUN-1202-21612.\n \nSteps to recreate:\n \n 1. Provider creates an IV order in CPRS.\n 2. Pharmacist (auto-verify off) finishes the order, the order is a \n\n
\n 1. A site reported a problem with an IV renewal order. The order had been\n scheduled IV labels. The extra labels contained the message 'NO PIGGYBACK\n DATA'. This patch corrects the problem by printing this label only once \n per label run, rather than for each patient. NOIS PAL-0902-61209.\n \n 3. A problem with the RETurns and Destroyed Entry (IV) [PSJI RETURNS]\n option was discovered by a member of development. The manual entry of a\n BCMA ID is allowed, but the option does not recognize lower case alpha\n characters within the BCMA ID. This patch changes this functionality to\n allow the input of upper or lower case alpha characters when a BCMA ID is\n entered in this option.\n renewed from the Computerized Patient Record System (CPRS) V. 2.0, and\n after the pending renewal order was verified, an error occurred. The\n error was due to an incorrect pointer to the pending order number that\n remained after the verification was complete. This patch corrects the\n problem by initialzing and reloading the new verified order after the\n order has been verified. NOIS BRX-1102-12101.\n \n 2. A site reported a problem with extra labels printing with their \n\n
\n1. The routine ^PSJORREN was included with patch PSJ*5*89 to correct the\n2. The routine ^PSJORRE1 is included in this patch to address SQA issue\nwith the incorrect DBIA number documented in the reference. The checksum\nwill not change.\n \n3. Routine ^PSJDCHK is included to comment out references to the\nPATIENT file (#55) that are no longer used.\n \n4. The SCHEDULE INTERVAL field (#.17) from the IV sub-file (#55.01) of the\nPHARMACY PATIENT file (#55) is not stored consistently for Day of Week\nschedules if the user did not have Auto Verify turned on. This patch will\nproblem of renewing a Unit Dose order with a 0 (zero) value stored in the\nschedules if the user did not have Auto Verify turned on. This patch will\nstore a "D" in this field for the Day of Week schedule. This patch\nincludes a modification to an Application Programmer Interface (API) to\nBCMA V. 2.0 to send the correct schedule type for IV orders.\nNOIS# NYH-1002-10449.\n \n5. Unit Dose orders created in Bar Code Medication Administration (BCMA)\nV. 2.0 using the Med Order Button do not appear on the Due List. These\norders are being created with a frequency of zero, which is not a valid\nfrequency. This patch will correct the problem so that these orders will\nORDERABLE ITEM field (#108) of the UNIT DOSE multiple (#62) of the\nbe created with the proper frequency for One Time orders.\nNOIS# MIN-1202-40902.\n \n6. A clean-up routine will identify orders with a frequency of zero and\nmake corrections, if appropriate. The person installing this patch will\nreceive a MailMan message with the subject PSJ*5*91 INPATIENT MEDS\nFREQUENCY ORDER CLEANUP COMPLETED. This message will inform the user how\nmany orders with a zero frequency were found and corrected. An order's\nfrequency will only be corrected if it meets all the following criteria:\nthe Frequency is zero, the Stop Date is equal to the Start Date, the\nPHARMACY PATIENT file (#55). This routine is included in this patch\nSchedule is STAT or NOW, and the Priority is Done.\n \n7. A site reported receiving an error while editing a Unit Dose order in\nthe Non-Verified/Pending Orders [PSJU VBW] option. Edits were made to the\norder that caused a new order to be created, and this cycle was repeated\nseveral times until an error occurred which interrupted the process. This\npatch will prevent this error from occurring.\nNOIS# BRX-1202-11956.\n \n8. A site reported receiving an undefined error when attempting to place\n(PSJ*5*91) to make sure that when Bar Code Medication Administration\nan order using the Med Order Button in Bar Code Medication Administration\n(BCMA) V. 2.0. This patch will correct the problem.\n \n9. A site reported a problem with the Drug (Cost and/or Amount) [PSJU\nDCT] option. When selecting by Orderable Item, the inactive date was not\nbeing displayed beside the name. This patch corrects this problem.\nNOIS# CLL-0103-40519.\n \n10. Sites reported a problem where active IV orders were being created\nwith an IV Room of zero (0). This created a problem of no IV labels\n(BCMA) V. 2.0 is installed after patch PSJ*5*89 sites will have the\nbeing printed for these orders. This patch corrects this problem.\nNOIS# HAM-0103-22051 & CPH-0103-41307.\n \n11. A site reported an error that occurred when two users simultaneously\nattempted to print to a non-spooled printer. The output should have been\ndirected to the terminal screen, but instead was queued to an output\ndevice of 'HOME'. This queued job will cause an inappropriate device\nerror, or it will create duplicate label log entries until the job is\nkilled. This patch will correct the problem by converting the name of the\noutput device from the word HOME to the user's home device.\ncorrect version. The second line will be updated with this patch number\nNOIS# DAY-0103-42177 & CLE-0203-40500.\n \n12. A site reported a problem with an order having the nurse verification\nindicated in Computerized Patient Record System (CPRS) V. 1.0, but no in\nInpatient Medications V. 5.0. This patch corrects this problem.\nNOIS# HUN-0902-22266.\n \n13. A site reported a problem with the status of an IV bag in Inpatient\nMedications V. 5.0 not matching the status of the bag in BCMA. This patch\ncorrects this problem.\nbut the routine checksum will be the same as listed in PSJ*5*89.\nNOIS# CLL-0203-40056.\n \n\n
\n This patch is compatible with Bar Code Medication Administration (BCMA)\n schedule with Chemotherapy IV orders. NOIS MIN-1002-40243.\n \n 2. When a patient movement is deleted and orders are reinstated, a mail\n message is sent to a user group to inform the users of reinstated orders\n and those that are not reinstated. This patch changed the mail message\n from regular to Priority mail to ensure the users see it.\n NOIS WPB-0902-30314.\n \n 3. A site reported a problem with scheduled IV labels for orders with\n Day of the Week schedules such as MO-WE-FR@0900. Labels were printing\n V. 1.0 as well as BCMA V. 2.0, and may be installed in environments\n for the scheduled administrations every day, instead of printing labels\n exclusively for the days defined in the schedule. This patch corrects\n the problem by printing labels only for scheduled doses.\n NOIS HIN-0902-41529.\n \n4. A site reported receiving the message "Nonstandard schedule" when they \n attempted to enter an order for a continuous IV Admixture using an IV \n Quick Code that did not contain a schedule. This message should not \n display when the schedule field does not contain a value, regardless of \n whether or not an IV Quick Code is used. This patch corrects the problem \n containing either version.\n by preventing this message from displaying when the schedule field is \n empty or null. NOIS BIG-1102-70679.\n \n 1. A site reported a problem with the way an IV Quick Order's schedule\n was handled when ordered as a Chemotherapy IV with a Chemotherapy Type\n of Piggyback. The schedule defined in the IV Quick Code did not default\n into the order when the IV Quick Code was used with an IV Type of\n Chemotherapy. This patch corrects the problem by properly defaulting the\n\n
\n 1. A site reported receiving an error message, 'string too long', while\n \n 2. A request was made to modify the Pre-Exchange Report to put each\n patient on a separate page. This patch implements this modification by\n printing the report by patient immediately after order entry processing\n is completed for each patient. Included in this change is a new field,\n the PRE-EXCHANGE REPORT DEVICE field (#4) in the INPATIENT WARD\n PARAMETERS file (#59.6). This parameter is a pointer to the DEVICE file\n (#3.5), and will contain the default print device for the report. A\n post-install routine has also been included to populate the new parameter\n for each ward with a value that will print the report to the screen. This\n attempting to finish a pending Unit Dose order. The error occurred after\n value may then be changed to a print device, or deleted to disable the\n report for that ward. E3R 17161.\n \n 3. A site reported a problem with the Start Date/Time of a Unit Dose\n renewal order. The problem occurred under the following conditions:\n An order's medication was administered at 0949, prior to its next \n scheduled administration of 1000. That same order's Stop Date/Time\n was 1200, which was after the 1000 administration time that was given\n early, but before the next scheduled administration time of 1800.\n The order is then renewed at 0956. The calculated Start Date/Time is\n a number of edits to the Special Instructions were made and accepted.\n after the order expires, so the ward parameters are used, making the\n Start Date/Time equal to NOW. The renewal order's Start Date/Time\n became 0956, which caused the order to hit the 1000 administration time\n again, seven minutes after the last administration. This patch corrects\n this particular problem by making the default Start Date/Time of the\n renewal order equal to the Stop Date/Time of the original renewed order\n if the calculated start time is after the Stop Date/Time of the original\n order. NOIS: MAR-1002-20455.\n \n 4. A site reported a pharmacist could not finish a pending order as Unit \n After each edit, 'Yes' was entered in response to the 'Flag the Special\n Dose when the prompt 'COMPLETE THIS ORDER AS IV OR UNIT DOSE?' was\n answered with 'U'. The pharmacist held the Pharmacy Technician Key, and \n as a result the software considered the Pharmacist a Pharmacy Technician.\n This patch corrects this problem by allowing pharmacists possessing the\n Pharmacy Technician Key to complete these orders as Unit Dose orders.\n NOIS: CHA-1101-31456.\n \n 5. The activity log was not updated to record the nurse verification \n action taken from CPRS on an active IV order. This patch will correct \n this issue. NOIS: NCH-1202-40194.\n Instructions (Yes/No):' prompt. As the Special Instructions were\n \n 6. The patient profile displayed "No Allergy Assessment" when the \n patient did not have any allergies but have adverse reaction identified. \n This patch will correct this problem. NOIS: BRX-0103-12347.\n flagged, a new flag was created and added to all the previous flags. This\n patch corrects the problem by taking previously flagged Special\n Instructions into account and ensuring only one flag exists for each\n order. NOIS: MIW-1002-40270.\n\n
\nIV orders entered through Inpatient Medications options by a user \nwithout auto-verify turned on, with a nature of order of verbal were not\nshowing in Computerized Patient Record System (CPRS) as requiring a\nsignature. This patch corrects this problem. NOIS# LAH-1202-60493.\n\n
\nThis patch contains the routines to support the Bar Code Med Admin (BCMA) \nNational Contingency Plan.\n\n
\n1. A site reported a problem where an order was showing on the pick list \nwith the order. This patch corrects this problem. NOIS# SPO-0103-51804.\n \n2. A site reported an error when flagging a pending IV order from the \npatient's profile. If the patient had not been admitted to a ward, the \nsoftware incorrectly processed the order as an outpatient order. This\npatch corrects the problem by correctly processing the flagging\ninformation. NOIS# HUN-0303-21424.\nwith OI under the Units Needed heading. Upon investigation of the order \nit was found that the order was logged in between midnight and one minute \nafter midnight, this caused a problem because the Inpatient Medications \nsoftware was only using the first 12 characters of the date time, so the \nlogin date had no time. The ward parameter for the ward was set to now \nwhich set the start date/time for the order to a date and no time. This \ncaused the problem with the pick list, the software was unable to \ncalculate the units needed and used OI to indicate there was a problem \n\n
\n Combination of Unit Dose Medications and IV Medications and their\nassociated utilities.\n\n
\nSee National Patch Module for description.\n\n
\nDRG Grouper Version 13.0\n\n
\nDRG Grouper Version 14.0\n\n
\nThis patch contains the FY99 updates to the ICD9 and ICD0 files,\nas well as the new DRGs 504-511.\n \nSee National Patch Module for details.\n\n
\nDRG Grouper Version 17 Released as Patch\n\n
\nThis build contains the DRG Grouper V16.0 release.\n\n
\nThis patch contains the DRG Reclassification changes published in\nthe Federal Register, Vol. 65, No. 148, dated August 1, 2000,\nwith an effective date of October 1,2000. See pp. 47057.\nIt also contains changes made in response to NOISes or other \nreported problems in connection with the DRG Grouper.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPatch ICD*18.0*123 provides the semi annual update to the Medicare\nSeverity Diagnosis Related Group (MS-DRG) Grouper version 42R1.\n\n
\nPatch ICD*18*126 Updates the NAME(#.01) and LONG DESCRIPTION(#10) fields \nfor Dx 8104\n\n
\nThe Health Insurance Portability and Accessibility Act (HIPAA) stipulates \no DRG Codes (Diagnostic Related Group which is part of the ICD-9\ncode set)\nthat diagnostic and procedure codes used for billing purposes must be the \ncodes that were applicable at the time the service was provided. Code \nsets required by the HIPAA legislation to be date-sensitive and included \nin this request are:\n \no ICD-9-CM (International Classification of Diseases-9-Clinical \nModifications)\n \n\n
\nFixes a system error which occurs when entering certain ICD9 codes \nin the 701 screen of the PTF LOAD/EDIT option.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\n This patch 1) adds data to the Identifier field (#2) of three \nwhen using operation/procedure code 96.72, 8) associates the\ncorrect DRG when using diagnosis 402.91 or 428.32 with card \ncath procedures, 9) associates the correct DRG when using \noperation/procedure 01.59, and reviews DRG 1,2,3,528 and 543\nfor proper assignment, 10) corrects the MDC field (#5)\nfor diagnosis 250.70, 11) Adds missing data to diagnosis 428.0 \n(Congestive Heart Failure Unspecified)\nICD OPERATION/PROCEDURE file (#80.1) records, 2) adds a DRG \ncalculation for bone marrow transplants, 3) corrects the\nDRG code associated with diagnosis 309.81 to be DRG 427,\n4) corrects the DRG codes associated with procedure code 51.23,\n5) removes the entry under DRG Grouper Effective Date for\nOctober 1,2004 for operation code 80.51, 6) removes the "F"\nfrom the Identifier field (#2) of ICD OPERATION/PROCEDURE\nFILE (#80.1) for code 81.61, 7) associates the correct DRG \n\n
\nProvides the annual update of the DRG Grouper for FY 2006 and\nresolves Remedy tickets. \n\n
\nThis patch fixes several problems all related to the wrong DRG being \ncalculated by the VistA DRG Grouper.\n\n
\nProvides the annual update of the DRG Grouper for FY 2007.\n\n
\nThis patch fixes procedure code 96.04 so its use will not generate \nDRG 470 (ungroupable). \n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch.\n\n
\nThis patch corrects the VistA DRG Grouper to conform to the \nQuadramed encoder for cases explained in the Remedy tickets.\n\n
\nPatch fixes DRG calculations.\n\n
\nPlease see the National Patch Module for details of the enhancements\n ICPT*6.0*38 Informational patch installed with LEX*2.0*53\n \nPlease see patch LEX*2.0*52 for install instructions\nincluded in this patch. This patch is part of a multi-package \ndistribution and includes the following patches installed in\nthe following order:\n \n LEX*2.0*52 Fixes for Lexicon, ICD and CPT problems\n ICPT*6.0*37 Routine ICPTMOD and ICPTMOD2\n ICD*18.0*29 Routine ICPTCODE and #80 Data Dictionary changes to file #80\n LEX*2.0*53 FY08 1st quarter ICD/CPT update\n\n
\nDRG CORRECTIONS\n\n
\nThis patch contains changes to correctly calculate bilateral knee and hip \nprocedures. Also corrects descriptions on DRG GROUPER [ICD DRG GROUPER] \noption.\n\n
\n \nThis patch provides the annual update to the MS-DRG Grouper v26.0 for \nFY09. It also contains corrections for Remedy tickets.\n\n
\nFIXES FOR INCORRECT DRG GROUPINGS\n\n
\nThis patch will fix incorrect DRG groupings.\n\n
\nThis patch corrects several Diagnostic Related Group (DRG) Grouper \ncalculations.\n\n
\n This patch corrects several Diagnostic Related Group (DRG) Grouper \ncalculations.\n\n
\nANNUAL DRG GROUPER UPDATE FY10 AND FIXES TO GROUPER.\n\n
\nDRG GROUPER FIXES\n\n
\nVarious DRG corrections\n\n
\nThis patch provides the annual update to the MS-DRG Grouper V28.0.\n\n
\nCorrect various DRG groupings\n\n
\nCorrections to various DRG calculations.\n\n
\nThis patch provides the annual update to the ICD9 codes, creates two additinal\nfields SEX and AGE in the ICD DIAGNOSIS file and updates that file with the\nindicated values if applicable.\n\n\n
\nDRG GROUPER FIXES\n\n
\nThis patch provides the annual update to the MS-DRG Grouper V28.0.\n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18*55.\n\n
\n \n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18*61.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper V28.0. \n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18*62.\n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18*69.\n\n
\n The patch provides the annual update to the DRG Grouper v20.0.\ndated August 1, 2002, with the effective date of October 1, 2002. DRG \nReclassification changes are in pp.49985-50008.\n \n Changes include:\n \nI. New/revised DRG codes (file #80.2).\nII. DRG Reclassification changes to the Grouper.\nIII. Miscellaneous modifications to the Grouper, discovered in the\n course of internal testing.\nIV. New DRG Weights & Trims.\n \n There will be no new version package release. All necessary changes \nare covered by this patch.\n \n No code files are included in the patch, as all changes are handled \nprogrammatically through the pre-init routine.\n \n The changes were published in the Federal Register, Vol.67, No.148, \n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18.0*70.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper V28.0.\n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18.0*71.\n\n
\nICD*18.0*57 contains the files and routines for the implementation\nof ICD-10. The data is contained in a Lexicon companion patch \nLEX*2.0*80.\n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18.0*74.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper V28.0.\n\n
\nPlease see the National Patch Module for details of the enhancements \nincluded in this patch.\n\n
\nPlease see the National Patch Module for details of the enhancements\nincluded in this patch. \n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18.0*78.\n\n
\n This patch corrects various DRG calculations.\n \n Details of the corrections for the DRG Grouper are located in\n ICD*18.0*79.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper v33.0.\n\n
\nPlease refer to ICD*18.0*89 in the National Patch Module for a description\nof this patch.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper (v34.0).\n\n
\nPlease see the National Patch Module for details\n of the enhancements included in this patch.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper (v35).\n\n
\nThis patch prevents a runtime error from occurring when the user enters \n"??" during the ICD Code Inquiry [ICD INQUIRY] menu option.\n\n
\nThis patch provides the annual update to the MS-DRG Grouper (v36).\n\n
\nSee patch description for ICD*18.0*97.\n\n
\nPatch ICD*18.0*98 will update multiple field names and descriptions\nin the DRG (#80.2) file that are no longer updated or in use.\n\n
\nThis patch provides the annual update to the Medicare Severity Diagnosis\n II. Revised DRG relative weights & average length of stay (ALOS)\n values for all DRGs.\n III. DRG Reclassification changes to the Grouper.\n IV. Additional DRG-related data for the new ICD codes introduced by\n patch LEX*2.0*123 (released September 23, 2019).\nRelated Group (MS-DRG) Grouper version 37.\n 1) INC6959379 - FY2020 ICD DRG Grouper annual update patch needed\n The following changes are published in the Federal Register, Vol. 84,\n No. 159, dated August 16, 2019 with an effective date of October 1,\n 2019. All page references below are for this annual update and\n resource documents can be found at https://www.cms.gov/.\nChanges include:\n I. Revised DRGs.\n\n
\nDRG RECLASSIFICATION FOR FY 04\n \nWEIGHTS AND TRIMS FOR FY 04\n\n
\nIn response to the national emergency that was declared concerning the\nCOVID-19 outbreak, the Centers for Disease Control and Prevention's (CDC)\nNational Center for Health Statistics (NCHS) is implementing a new\ndiagnosis code, U07.1, COVID-19, into the International Classification\nof Diseases, Tenth Revision, Clinical Modification (ICD-10-CM), effective\nApril 1, 2020. They are also implementing diagnosis code U07.0\n(Vaping-related disorder).\n\n
\n This patch provides the annual update to the Medicare Severity Diagnosis\n Be aware of the shortened compliance date. The dates listed in the patch\n description are accurate as the FY2021 annual patch was delayed.\n The changes included in this patch were effective as of 10/1/2020 per\n the Federal Register Vol. 85, No. 182, dated September 18, 2020.\n \n+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n Related Group (MS-DRG) Grouper version 38. Also, in response to the\n national emergency that was declared concerning the COVID-19 outbreak, the\n Centers for Disease Control and Prevention's (CDC) is implementing new\n codes into the Medicare Severity Diagnosis Related Group (MS-DRG) Grouper\n version 38.1, effective January 1, 2021.\n+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n \n PLEASE NOTE:\n\n
\n This patch provides the annual update to the Medicare Severity Diagnosis\n \n+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n Related Group (MS-DRG) Grouper version 39. \n+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n \n PLEASE NOTE:\n Be aware of the shortened compliance date. The dates listed in the patch\n description are accurate as the FY2022 annual patch was delayed.\n The changes included in this patch were effective as of 10/1/2021 per\n the Federal Register Vol. 86, No. 154, dated August 13, 2021.\n\n
\n In response to the ongoing national emergency concerning COVID-19, the Centers\n for Disease Control and Preventions (CDC) National Center for Health Statistics\n (NCHS) is implementing 3 new diagnosis codes and 7 new procedure codes, into\n the International Classification of Diseases, Tenth Revision, for reporting\n COVID-19 vaccination status effective April 1, 2022.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n PLEASE NOTE:\n Be aware of the shortened compliance date. The dates listed in the \n patch\n description are accurate as the FY2023 annual patch was delayed.\n The changes included in this patch were effective as of 10/1/2022 per\n the Federal Register Vol. 87, No. 153, dated August 10, 2022\n \n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\n
\nThe purpose of this patch is to add code for the update that was posted \nin the Federal Register for fiscal year 2023. These changes were published\non https://www.cms.gov and are part of the version 40 revision 1 release,\nwith an effective status of April 1, 2023.\n\n
\nFY2024 ANNUAL DRG GROUPER UPDATE\n\n
\nPatch ICD*18.0*118 provides semi-annual update to the Medicare Severity\nDiagnosis Related Group (MS-DRG) Grouper version 41r1. \n\n
\nPatch ICD*18.0*120 provides the annual update to the Medicare Severity\nDiagnosis Related Group (MS-DRG) Grouper version 42. \n\n
\nUPDATE TO THE #31 FILE FOR DX 8045\n\n
\nThis build contains the ICD V18.0 release.\n\n
\nDHCP DRG Grouper\n\n
\nAn undef error was reported when entering a date/time for the Inactive\n 2 Inactivate AOU Stock Item \nRoutine Name: PSGWAOUI\n \nCHOOSE 1-2: 1 Inactivate AOU \n \nEnter AOU Inactivation Dates \n \nSelect PHARMACY AOU STOCK AREA OF USE (AOU): LYN'S MED ROOM \n \nINACTIVE DATE: T@1300 (JUN 13, 1996@13:00)\n \nDate for an AOU. An example of the error follows: \n...One moment, please... \n \nThere are items in this AOU that are currently active. You may, at this\ntime, inactivate all of them as of JUN 13,1996@13:00. \n \nDo you want to do this? Yes// (Yes) \n \nNow inactivating all currently active items as of JUN 13,1996@13:00??.?? \n.??.??.??.\n<UNDEF>+18^PSGWAOUI:::4:0: \n \n \nThe error occurs because the date/time response for the inactive date\nfield of the AOU is entered into the inactivation date field for the items\nin the AOU and this field does not allow the entry of time. \n(MWV-0696-20736) \n \nThis patch will correct this problem. \n \nROUTINE SUMMARY: \n================\nSelect Automatic Replenishment Option: SUPervisor's Menu \n \nThe following routine is included in this patch. The second line of the \nroutine will look like: \n \n<tab>;;2.3; Automatic Replenishment/Ward Stock ;;**[patch list]**;4 JAN 94\n \n \n CHECK^XTSUMBLD results: \n \nRoutine Name Before Patch After Patch Patch List \n \n \n PSGWAOUI 8589667 8683714 7 \n \n \nINSTALLATION INSTRUCTIONS: \n ==========================\n This patch may be loaded during regular work hours without\n disruption to users. It only affects users of the Automatic\n Replenishment/Ward Stock software. \n Installation will take less than 5 minutes. \nSelect Supervisor's Menu Option: SET Up AR/WS (Build Files) \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu and \n answer NO to the question 'Shall I preserve what is on disk in a \n separate back-up message ?'. Answer YES to the prompt 'Want to \n Continue with Load? YES//' \n 2. Review your mapped set. If the routine listed in the \n ROUTINE INFORMATION section is mapped, it should be removed \n from the mapped set at this time. The patched routine is not on\n the recommended mapping list. \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n \n 4. From this menu, you may elect to use the following options \n (when prompted for INSTALL NAME, enter PSGW*2.3*7): \n a. Backup a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \n backup any other changes such as DDs or templates. \n b. Compare Transport Global to Current System - this option will \n allow you to view all changes that will be made when the patch \n is installed. It compares all components of the patch \n (routines, DDs, templates, etc.). \n c. Verify Checksums in Transport Global - this option will \nSelect Set Up AR/WS (Build Files) Option: INA \n allow you to ensure the integrity of the routines that are in \n the transport global. \n 5. Use the Install Package(s) option and select the package\n PSGW*2.3*7. \n 6. When prompted 'Want to DISABLE Scheduled Options and Options? \n YES//', respond YES. When prompted to select the options you\n would like to place out of order, enter the following: \n PSGW AOU INACTIVATION Inactivate AOU \n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n 1 Inactivate AOU \n CPUs. Alternately, you can wait until the installation is\n complete and move the routines listed in the ROUTINE INFORMATION\n section to all systems. \n 8. If routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion. \n \nRoutine Information:\n====================\n \n\n
\n \nThis patch will allow selection of Non-VA meds (X) to be selected for \nWard Stock.\n\n
\nThis patch will resolve the following issue:\n \nAssociated NSRs:\n================\nN/A\n \n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nRemedy Overview:\n================\n1. I10479329FY16 PSGW ON-DEMAND PRINT calculates wrong time\n \nPSPO:\n===== \nN/A\n \nProblem: \nThe report option Print an On-Demand Report by Date/AOU (80 column) [PSGW\n--------\nWhen the user ran the report option Print an On-Demand Report by Date/AOU\n(80 column) [PSGWON-DEMAND PRINT] and selected a date range that \ncontained \na specific time (MMDDYY@HHMM) for either the BEGINNING or ENDING date\nprompts the report filter did not work correctly causing the report to\ninclude entries outside the date/time range and to also exclude entries\nwithin the date/time range selected.\n \nResolution:\nON-DEMAND PRINT] was incorrectly filtering entries to be printed on the\n-----------\nModified the routine PSGWODP to correctly set the filter variables for the\ndate/time range so that each entry screened are correctly included or\nexcluded from the report.\n \n \nTechnical Resolution:\n---------------------\na. At the line BDT^PSGWODP the variable BDT, which holds the BEGINNING \ndate\nreport according to the date range selected by the user.\n range value, was being set with BDT=BDT-.1. This was wrong because the\n the time (HHMM) is accepted. This was corrected to BDT=BDT-.00001\na. At the line EDT^PSGWODP the variable EDT, which holds the ENDING date\n range value, was being set with EDT=EDT+.3. This was also wrong because\n the time (HHMM) is accepted. Furthermore, this variable only needs to \nbe\n reset if a specific time was not entered. The setting of this variable \n was changed to S:EDT'["." EDT=EDT+.24.\n \nAssociated CA SDM Ticket(s):\n============================\n1. I10479329FY16 PSGW ON-DEMAND PRINT calculates wrong time\n\n
\nAdd Allowed Ward Stock Level to On-Demand request and Report & AUTO Print\n\n
\nBackup of PSGW*2.3*21 on Mar 22, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses Automatic replenishment/ward stock (AR/WS) reports \nthat do not correctly calculate the prices for drugs that are defined \nwith a AR/WS AMIS CONVERSION NUMBER greater than 1.\n\n
\nAn undef error was reported when entering a date/time for the Inactive\n \n completion. \n \nRoutine Information:\n====================\n \nRoutine Name: PSGWAOUI\nSelect Set Up AR/WS (Build Files) Option: INA \n 1 Inactivate AOU \n 2 Inactivate AOU Stock Item \n \nCHOOSE 1-2: 1 Inactivate AOU \n \nEnter AOU Inactivation Dates \n \nSelect PHARMACY AOU STOCK AREA OF USE (AOU): LYN'S MED ROOM \nDate for an AOU. Patch 7 was issued to correct this problem and it\n \nINACTIVE DATE: 8 1@1200 (AUG 01, 1996@12:00)\n \n...One moment, please... \n \nThere are items in this AOU that are currently active. You may, at this\ntime, inactivate all of them as of AUG 1,1996@12:00. \n \nDo you want to do this? Yes// (Yes) \n \nworked for dates other than the first nine days of a month. This patch\nNow inactivating all currently active items as of AUG 1,1996@12:00??.?? \n.??.??.??.\n<UNDEF>+18^PSGWAOUI:::4:0: \n \nThe error occurs because the date/time response for the inactive date\nfield of the AOU is entered into the inactivation date field for the items\nin the AOU and this field does not allow the entry of time. Patch 7\nextracted the first 11 characters of the date/time chosen and this\nincluded the "@" sign on dates for the first nine days of a month. This\npatch will take the first piece of the date/time entered with the "@" as\nwill correct patch 7 and work for all dates in a month. An example of the\nthe delimiter.\n(MWV-0696-20736, ALN-0896-10244, HIN-0896-40381) \n \nThis patch will correct this problem. \n \nROUTINE SUMMARY: \n================\n \nThe following routine is included in this patch. The second line of the \nroutine will look like: \nerror follows:\n \n<tab>;;2.3; Automatic Replenishment/Ward Stock ;;**[patch list]**;4 JAN 94\n \n \n CHECK^XTSUMBLD results: \n \nRoutine Name Before Patch After Patch Patch List \n \n PSGWAOUI 8683714 8672951 7,8 \n \n \n \nINSTALLATION INSTRUCTIONS: \n ==========================\n This patch may be loaded during regular work hours without\n disruption to users. It only affects users of the Automatic\n Replenishment/Ward Stock software. \n Installation will take less than 5 minutes. \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu and \n answer YES to the prompt 'Want to Continue with Load? YES//'\n 2. Review your mapped set. If the routine listed in the \nSelect Automatic Replenishment Option: SUPervisor's Menu \n ROUTINE INFORMATION section is mapped, it should be removed \n from the mapped set at this time. The patched routine is not on\n the recommended mapping list. \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n 4. From this menu, you may elect to use the following options \n (when prompted for INSTALL NAME, enter PSGW*2.3*8): \n a. Backup a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \n backup any other changes such as DDs or templates. \n \n b. Compare Transport Global to Current System - this option will \n allow you to view all changes that will be made when the patch \n is installed. It compares all components of the patch \n (routines, DDs, templates, etc.). \n c. Verify Checksums in Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the transport global. \n 5. Use the Install Package(s) option and select the package\n PSGW*2.3*8.\n 6. When prompted 'Want to DISABLE Scheduled Options and Options? \nSelect Supervisor's Menu Option: SET Up AR/WS (Build Files) \n YES//', respond YES. When prompted to select the options you\n would like to place out of order, enter the following: \n PSGW AOU INACTIVATION Inactivate AOU \n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n CPUs. Alternately, you can wait until the installation is\n complete and move the routines listed in the ROUTINE INFORMATION\n section to all systems. \n 8. If routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n\n
\nA problem was reported when running the Cost Report Per AOU [PSGW COST\nroutine will look like: \n \n<tab>;;2.3; Automatic Replenishment/Ward Stock ;;**[patch list]**;4 JAN 94\n \n \n CHECK^XTSUMBLD results: \n \nRoutine Name Before Patch After Patch Patch List \n \n PSGWCPA1 14134524 14170611 9 \nPER AOU]. The summary pages were not printing.\n \n \nINSTALLATION INSTRUCTIONS: \n ==========================\n This patch may be loaded during regular work hours without\n disruption to users. It only affects users of the Automatic\n Replenishment/Ward Stock software. \n Installation will take less than 1 minute. \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu and \n answer YES to the prompt 'Want to Continue with Load? YES//'\n \n 2. Review your mapped set. If the routine listed in the \n ROUTINE INFORMATION section is mapped, it should be removed \n from the mapped set at this time. The patched routine is not on\n the recommended mapping list. \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n 4. From this menu, you may elect to use the following options \n (when prompted for INSTALL NAME, enter PSGW*2.3*9): \n a. Backup a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \nThis patch will correct this problem. \n backup any other changes such as DDs or templates. \n b. Compare Transport Global to Current System - this option will \n allow you to view all changes that will be made when the patch \n is installed. It compares all components of the patch \n (routines, DDs, templates, etc.). \n c. Verify Checksums in Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the transport global. \n 5. Use the Install Package(s) option and select the package\n PSGW*2.3*9.\n \n 6. When prompted 'Want to DISABLE Scheduled Options and Options? \n YES//', respond YES. When prompted to select the options you\n would like to place out of order, enter the following: \n PSGW COST PER AOU Cost Report Per AOU \n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n CPUs. Alternately, you can wait until the installation is\n complete and move the routines listed in the ROUTINE INFORMATION\n section to all systems. \n 8. If routines were unmapped as part of step 2, they should be\nROUTINE SUMMARY: \n returned to the mapped set once the installation has run to\n completion. \n \nRoutine Information:\n====================\n \nRoutine Name: PSGWCPA1\n================\n \nThe following routine is included in this patch. The second line of the \n\n
\nA problem was reported when using the option [PSGW ON-DEMAND\nThis patch will correct these problems. \n \nROUTINE SUMMARY: \n================\n \nThe following routines are included in this patch. The second line of\neach routine will look like:\n \n<tab>;;2.3; Automatic Replenishment/Ward Stock ;;**[patch list]**;4 JAN 94\n \nNURSING EDIT] Enter/Edit Nurses' On-Demand Request (80 column). The\n \n CHECK^XTSUMBLD results: \n \nRoutine Name Before Patch After Patch Patch List \n \n PSGWODRN 17619352 17822671 11 \n PSGWOND 11310229 11279708 11\n \n \n \nproblem occurred when the user selected the item. If there were multiple\nINSTALLATION INSTRUCTIONS: \n ==========================\n This patch may be loaded during regular work hours without\n disruption to users. It only affects users of the Automatic\n Replenishment/Ward Stock software. \n Installation will take less than 1 minute. \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu and \n answer YES to the prompt 'Want to Continue with Load? YES//'\n 2. Review your mapped set. If the routine listed in the \n ROUTINE INFORMATION section is mapped, it should be removed \nitems to pick from the one selected was not always the one shown. (NOIS\n from the mapped set at this time. The patched routines are not on\n the recommended mapping list. \n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n 4. From this menu, you may elect to use the following options \n (when prompted for INSTALL NAME, enter PSGW*2.3*11): \n a. Backup a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \n backup any other changes such as DDs or templates. \n b. Compare Transport Global to Current System - this option will \nMEM-0397-70742, SLC-0397-51202, BAY-0397-30702, IOW-0397-41379,\n allow you to view all changes that will be made when the patch \n is installed. It compares all components of the patch \n (routines, DDs, templates, etc.). \n c. Verify Checksums in Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the transport global. \n 5. Use the Install Package(s) option and select the package\n PSGW*2.3*11.\n 6. When prompted 'Want to DISABLE Scheduled Options and Options? \n YES//', respond YES. When prompted to select the options you\nALX-0397-71625)\n would like to place out of order, enter the following: \n PSGW ON-DEMAND NURSING EDIT Enter/Edit Nurses' On-Demand\n Request (80 column)\n PSGW ON-DEMAND DELETE Delete an On-Demand Request\n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n CPUs. Alternately, you can wait until the installation is\n complete and move the routines listed in the ROUTINE INFORMATION\n section to all systems. \n 8. If routines were unmapped as part of step 2, they should be\nA similar problem was reported when using the option [PSGW ON-DEMAND\n returned to the mapped set once the installation has run to\n completion. \n \nRoutine Information:\n====================\n \nRoutine Name: PSGWODRN\n PSGWOND\nDELETE] Delete an On-Demand Request. (NOIS STX-0397-71762)\n \n\n
\nA problem has been reported when using the option Input AOU Inventory\nROUTINE SUMMARY: \n================\n \nThe following routines are included in this patch. The second line of\neach routine will look like:\n \n<tab>;;2.3; Automatic Replenishment/Ward Stock ;;**[patch list]**;4 JAN 94\n \n \n CHECK^XTSUMBLD results: \n[PSGW AOU INVENTORY INPUT]. The problem occurs when using the ^ jump\n \nRoutine Name Before Patch After Patch Patch List \n \n PSGWEDI1 3592050 4664602 2,12 \n \n \n \nINSTALLATION INSTRUCTIONS: \n ==========================\n This patch may be loaded during regular work hours without\nfunctionality at the 'ON-HAND //' prompt if the inventory sheet being\n disruption to users. It only affects users of the Automatic\n Replenishment/Ward Stock software. \n Installation will take less than 1 minute. \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu and \n answer YES to the prompt 'Want to Continue with Load? YES//'\n This option will load the KIDS package onto your system.\n 2. Review your mapped set. If any routine listed in the \n ROUTINE INFORMATION section is mapped, it should be removed \n from the mapped set at this time. The patched routine is not on\n the recommended mapping list. \ninput contains more than one inventory TYPE. The site was unable to use\n 3. From the Kernel Installation and Distribution System Menu, select \n the Installation menu. \n 4. From this menu, you may elect to use the following options \n (when prompted for INSTALL NAME, enter PSGW*2.3*12): \n a. Backup a Transport Global - this option will create a backup \n message of any routines exported with the patch. It will NOT \n backup any other changes such as DDs or templates. \n b. Compare Transport Global to Current System - this option will \n allow you to view all changes that will be made when the patch \n is installed. It compares all components of the patch \nthe ^ followed by the item name to jump to another item.\n (routines, DDs, templates, etc.). \n c. Verify Checksums in Transport Global - this option will \n allow you to ensure the integrity of the routines that are in \n the transport global. \n 5. Use the Install Package(s) option and select the package\n PSGW*2.3*12.\n 6. When prompted 'Want to DISABLE Scheduled Options and Options? \n YES//', respond YES. When prompted to select the options you\n would like to place out of order, enter the following: \n PSGW AOU INVENTORY INPUT Input AOU Inventory\n(NOIS LON-0297-60876)\n 7. MSM sites: Please ensure you answer YES when asked if you want \n to move the routines to other systems and indicate the appropriate \n CPUs. Alternately, you can wait until the installation is\n complete and move the routines listed in the ROUTINE INFORMATION\n section to all systems. \n 8. If routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion. \n \nRoutine Information:\n \n====================\n \nRoutine Name: PSGWEDI1\nThis patch will correct these problems. \n \n\n
\n A problem has been reported with the Standard Cost Report [PSGW STANDARD\nCost for that item was off by a factor of the AR/WS conversion factor. The\nAR/WS conversion factor will no longer be used in the calculation for the\ntotal cost in this report. This patch corrects this problem.\nCOST REPORT]. The Standard Cost Report lists the cost for items in one\nAOU, several AOUs, all AOUs, or an inventory group. This cost represents\nthe dollar amount needed to bring each item from zero to its maximum\nstock level.\nThe TOTAL COST field was computed by multiplying the item's stock level by\nthe AR/WS conversion factor found in the DRUG file (#50) and then by price\nper dispense unit found in the DRUG file. It was reported that if the\nAR/WS conversion factor was anything other than one (1) then the Total\n\n
\n This patch will delete the data dictionary and the data from the\nsubfile 59.41, PHARMACISTS field (#6) of the INPATIENT SITE file (#59.4).\nThis will cleanup the reference to the USER file (#3).\n\n
\nThis patch corrects two problems.\n \n1. It updates the AR/WS STATS FILE (#58.5), removing potential extraneous\nnodes from the data dictionary. These extraneous nodes may cause errors\nwhen running Pharmacy Benefits Management extracts.\n \n2. It corrects a formatting problem when using the option Print an\nOn-Demand Report by Date/AOU (80 column) [PSGW ON-DEMAND PRINT].\n\n
\n \nThis patch will prevent the error trap when selecting Item in the PSGW \nUsage report.\n\n
\nAUTOMATIC REPLENISHMENT/WARD STOCK IS A MEANS OF DRUG DISTRIBUTION\nAND INVENTORY USED BY INPATIENT PHARMACY. VERSION 2.0 INCLUDES\nMULTI-DIVISION AMIS REPORTING.\n\n
\nConsolidated Mail Outpatient Pharmacy Patch # 4 - Corrects days to pull\nahead parameter and Drug Warning problems.\n\n
\nThis build corrects a problem in PSX*1*4.\n\n
\nCorrect a problem with the automated recovery process.\n\n
\nWhen a user unmarks a drug for Outpatient use, the drug will now be\nautomatically unmarked for CMOP transmission.\n \nThe Outpatient one year patch conflicted with code that determines how to\ndisplay refills. The number 6 was a code used to indicate that the fill\nwas a partial so the sixth refill was being diplayed as a partial. CMOP\nroutines now mimic the O.P. method to display the refill correctly while\nallowing partials to display correctly.\n\n
\nPatch 1 for version 2 to correct problems with V1 sites going to V2.\n\n
\nSee the patch description for PSX*2.0*16.\n\n
\nSee the patch description for PSX*2.0*12.\n\n
\nSee the patch description for PSX*2*14.\n\n
\nThe patch modifies CMOP routines to work with Outpatient Pharmacy V6 and\n of OP that is on the system. Sets the PSXVER variable\n to indicate the OP version. This variable determines the\n location of the Status and SIG fields in the Rx file (#52).\n \nPSXBLD Modified to get the Status and SIG fields from the proper\n location in the Rx file (#52) based on the OP version.\n \nPSXBLD1 Modified to get the Status from the proper location in\n the Rx file (#52) based on the OP version.\n \nV7. \nPSXCOPAY Modified to get the Status from the proper location in the\n Rx file (#52) based on the OP version.\n \nPSXERR Modified to provide an error message if the package file\n entry for the OP package is missing the version number.\n This error message is the CMOP Error Encountered mail msg.\n \nPSXMISC1 Modified to set the new fields in the Rx Suspense file when\n marking the Rx as 'Loading' and/or 'Transmitted'.\n \n \nPSXRESUB Modified to set the OP version.\n \nPSXRCVRY Modified to set the Status field in the Rx file (#52) based\n on the OP version. Makes the call to PSOHLSN1 to send\n send changes in the status field in the Prescription file\n (#52) to CPRS.\n \nPSXRPPL Modified to check the Status field and SIG field in the Rx\n file (#52) based on the OP version.\n Makes the call to PSOHLSN1 to send changes in the status\nThe following modifications were made to CMOP routines so that the CMOP\n field in the Prescription file (#52) to CPRS.\n \nPSXRPPL1 Modified to check the Status field and SIG field in the Rx\n file (#52) based on the OP version.\n \nPSXRSUS Modified to ZTSAVE the variable, PSXVER. This variable is \n used to determine the location of the Status and SIG fields\n in the Rx file (#52) based on the OP version.\n \nPSXSRP This is a new routine to allow users to reprint CMOP Rx's\nprocess will work with either OP6 or OP7.\n that were printed at the remote medical center by batch.\n \nPSXSRST This is a new routine to allow users to reprint by batch\n CMOP Rx's that were printed at the remote medical center.\n Makes the call to PSOHLSN1 to send changes in the status\n field in the Prescription file (#52) to CPRS.\n \nPSXUTL Modified to set the variable PSXVER. This variable is used\n determine the OP version.\n \nROUTINE Summary of Modifications\n \nPSXAUTO Makes a call to the PSXUTL routine to get the version\n\n
\nSee the patch description for PSX*2.0*18.\n\n
\nThis patch addresses concerns aired in NOIS #'s\nOKL-1098-70296,CMP-0398-62763 and BOI-1098-50491.\n\n
\nThe variable PSOSITE, used by both the CMOP and OUTPATIENT PHARMACY\npackages is killed in the ^PSXRESUB routine. This causes an undefined\nvariable to occur in the OUTPATIENT PHARMACY package in certain instances.\n\n
\nThis patch contains a routine that will notify the CLINICAL INFORMATION\nRESOURCES NETWORK (CIRN) V.1.0 package when a CMOP prescription is \nreleased.\n\n
\nThe CMOP DUAL LINE INTERFACE enhancement modifies the lower layer \ncommunication link software utilized by CMOP Host systems and vendor \nautomated dispensing systems for electronic data exchange of prescription\ninformation. Functionality allows CMOP Host facilities to simultaneously\nperform transmission data download and query request for prescription\ninformation.\n\n
\nPatch PSX*2*20 corrected an undefined error in the variable PSOSITE,\nwhich was shared by the Outpatient Pharmacy and CONSOLIDATED MAIL\nOUTPATIENT PHARMACY (CMOP) packages. The CMOP package killed this\nvariable, causing the undefined condition. This condition was corrected\nby the patch, but, depending on how the user entered the option to\nresubmit the Rx, the variable PSOSITE might not be defined at all. This\npatch checks for the existence of the variable PSOSITE and prevents the\nsecond undefined error from occurring.\n\n
\nPatch 2 to correct problems with V2.\n\n
\n1. An adjustment to the CMOP software has become necessary with the\nwere being held up. Changing the way the routing was handled fixed this\nproblem.\ndistribution of MailMan patch 50. The % variable returned from the\nNOW^%DTC function is being killed in a MailMan routine where it was\npreviously not.\n2. A modification to the CMOP software has become necessary with the\nrelease of Fileman V. 22. The variable DIC(0) is now killed where is was\npreviously not.\n3. A second modification was necessary as a result of MailMan patches.\nCMOP error messages normally delivered to the holders of the PSXMAIL key\n\n
\nProblem:\nusing CMOP ID). The drug name is correct in the body of the report\nbecause PSXDGID is set before calling NAME^PSXCSUTL. However, when\nprinting the drug name in heading of the report, the routine PSXCSMN1 does\nnot set the variable PSXDGID. This patch will correct the problem by\nsetting PSXDGID in routine PSXCSMN1.\n========\nA problem was reported with the Drug Cost by Drug Report for One Month\n[PSX COST ONE MONTH DRUG REPORT] where if the user selects a specific drug\nand specific facility, the RX in the heading is incorrect.\n \nResolution:\n===========\nThe variable PSXDGID is used in NAME^PSXCSUTL (Utility to get drug name\n\n
\nProblem:\n \nThe CMOP process is taking very long times to find the next available\nvacancy in the file for creating entries.\n \nResolution:\n \nThe process has been modified with recent extensions of the M language to\nfind the next available vacancy in the file with one program call.\n\n
\nThis patch is part of the CMOP - Controlled Substance Rxs enhancements.\nThe Installation Guide for the CMOP - Controlled Substance Rxs project\ncan be obtained on the VISTA Consolidated Mail Outpatient Pharmacy web\npage. The address is http://vista2.domain.ext/cmop/. The Installation\nGuide is also available on the ANONYMOUS.SOFTWARE directory at one of the\nfollowing Office of Information (OI) Field Offices. The file name is\nCMOPCS_IG.PDF.\n \n OI FIELD OFFICE FTP ADDRESS DIRECTORY\n =============== =========== =========\n Albany 152.127.1.5 anonymous.software\nIt modifies functions within the Consolidated Mail Outpatient Pharmacy\n Hines 152.129.1.110 anonymous.software\n Salt Lake City 152.131.2.1 anonymous.software\n \nCMOP software modifications:\n \n1. The Loop CMOP Match to Local Drug File option [PSXX LOOP MARK] was\n modified to allow drugs identified as schedule III-IV controlled\n substances to be marked for processing by CMOP facilities.\n2. The CMOP Data from Your Local Drug File report option [PSXX LOCAL\n DATA] was modified to add the reporting of drugs identified as\npackage to support the transmission of controlled substance prescriptions\n schedule III-IV controlled substances that are marked for CMOP.\n3. The Drugs not Flagged for CMOP Transmission option [PSXX NOCMOP] was\n modified to report drugs identified as schedule III-IV controlled\n substances.\n4. The CMOP Mark/Unmark (Single drug) option [PSXX MARK] will be\n deleted. This functionality is duplicated in the Pharmacy Data\n Management package.\n5. The Unreleased Rx's Report option [PSX UNRELEASED] was modified to\n sort by controlled substances, non-controlled substances or both types\n of prescriptions.\nto the Consolidated Mail Outpatient Pharmacy facilities.\n6. A new option, Setup CMOP CS Auto-transmission [PSXR AUTO TRANSMIT\n CS] was created to manage the automatic transmissions of controlled\n substances to the CMOP facilities.\n7. The CMOP manual transmission function, called by the Outpatient\n Pharmacy option Print from Suspense File [PSO PNDLBL] has been modified\n to transmit prescriptions written for drugs identified as schedule\n III-IV controlled substances that are marked for CMOP.\n8. This patch addresses NOIS CHA-1297-30037. The CMOP software\n currently only allows the medical centers to select the CMOPs that were\n on-line when CMOP V2.0 software was released. Modifications now enable\n \n the medical centers to select any of the current operating CMOPs.\n9. This patch addresses NOIS BIR-0299-31299. Current functionality\n could allow two fills of a prescription to be suspended on top of one\n another, which could cause the patient to lose one. The transmission\n timing has been adjusted to prevent the second fill from being\n suspended until the first has been transmitted.\n10.This patch addresses NOIS DAY-0499-42275. Under certain circumstances\n the patient profile print device could be left undefined, causing an\n error in the Outpatient Pharmacy software. Calling a different entry\n point in the Outpatient Pharmacy software allows the user to select a\nThis patch will be installed in conjunction with three other patches\n device, if desired.\n11.This patch also addresses NOIS DAY-0899-42676. Test patients with SSN's\n of 000-00-0000 are being sent to the CMOP. A screen was placed in the\n software to prevent this from occurring.\n12.A new subfile,the AUTO TRANSMIT CS (#550.09) and eight new fields have\n been added to the CMOP SYSTEM file (#550) to track CMOP controlled\n substances transmissions at the medical centers.\n13.A new field, CONTROLLED SUBS FLAG (#19), has been added to the CMOP\n MASTER DATABASE file (#552.4) on the host CMOP system to track\n controlled substance prescriptions.\n(PSD*3*21, PSO*7*33, and PSS*1*28). Refer to the CMOP - Controlled\nSubstance Rxs Installation Guide for installation instructions.\n \n\n
\n1. Problem: Site number lookup into the INSTITUTION file (#4) is failing\nconfusing and misleading.\n \nResolution:\n \nThe user instructions have been corrected.\nas CMOP is using more than the first three numbers in the element taken\nfrom the INPATIENT SITE file (#59.4).\n \nResolution:\n \nThe lookup has been recoded to use only the first three numbers.\n \n2. Problem: The user instructions in printing from CMOP suspense are\n\n
\nProblem: Undefined errors are occurring in the routine PSXBLD when a\nrefill is deleted in pharmacy while the CMOP transmission is in the\nbuilding process.\n \nResolution:\n \nThe CMOP coding has been changed to guard against the undefined error.\n\n
\n1. Problem: The release of XM*7.1*50 has changed the API calls other\n2. Problem: The messages from the CMOP software to the users and managers\nhad been marked 'informational only' preventing them from easily\ncorresponding with other staff members on how to resolve problems being\nreported.\n \nResolution:\n \nThe 'informational only' tag has been removed from all user messages.\n \n3. Problem: A variable was not defined in some PSX calls to the line\npackages are to use in evoking Mailman functions. The CMOP package is not\ntag MM^PSXVND.\n \nResolution:\n \nThe appropriate variable is now set within the code located in the\nsubroutine MM^PSXVND.\nusing these calls in sending messages to servers.\n \nResolution:\n \nThe CMOP coding of XM calls has been changed to be within the prescribed\nAPIs published for servers.\n \n\n
\n1. E3R 9128 requests that all CMOP reports provide the ability to select\n2. E3R 9434 requests that several new columns be added to the Rx Workload\nReport. Those columns are to be under the categories of 'Entered Window'\nand 'Released Window' and are to reflect prescriptions that are refilled\nor original renewals.\n \nResolution: The Rx Workload Report [PSXR RX WORKLOAD REPORT] option has\nbeen modified.\n \n3. Problem: The "Transmitted By" on the CMOP TRANSMISSION CONFIRMATION\nreport is blank.\none, more, or all divisions and display the report details by divisions.\n \nResolution: The software has been corrected and the "Transmitted By" on\nthe CMOP TRANSMISSION CONFIRMATION report is populated in the message.\n \nResolution: The reports have been modified. They are:\n \nCount of CMOP Suspended Rx's [PSXR SUSPENSE COUNT]\nMedical Center Activity Report [PSXR ACTIVITY]\nRx Workload Report [PSXR RX WORKLOAD REPORT]\n \n\n
\n1. Problem: The CMOP software shall be modified to no longer check the Rx\nE3R 13012: There are many "CMOP REMOTE ERROR CONDITION NOTICE"\nmessages generated and sent. It is requested that the message have the\nsite number added as a prefix to each message generated.\n \nResolution: The coding has been modified such that the site number has\nbeen added as a prefix to the messages.\n \nNote: Routine PSXCOPAY will be deleted from the system. This routine is\nnot being used.\n \ncopay status of a prescription during the release process. The Rx copay\nAssociated NOIS:\n================ \nN/A\n \nTest Sites:\n=========== \n \n \nRoutine Summary:\n================ \nstatus shall be re-evaluated by the Outpatient Pharmacy application with\nThe following is a list of the routines included in this patch.\nThe second line of each of these routines now looks like:\n \n<tab>;;2.0;CMOP;**[patch list]**;11 Apr 97\n \n CHECK^XTSUMBLD results\n \nRoutine Name Before Patch After Patch Patch List\n------------ ------------ ----------- ----------\nPSXVND 15932593 16276949 1,2,4,5,14,18,19\neach fill/refill. \n 15,24,23,27,35\nPSXVEND 16202580 16667384 23,27,35\n \n \nInstallation Instructions:\n========================== \n This patch can be installed with users on the system. Installation will\n take less than 1 minute. There are no scheduling restrictions or\n recommendations.\n \n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. Review your mapped set. If the routines are mapped, they should\n be removed from the mapped set at this time. Currently there are no\n routines that are recommended by the package to be placed into the\n mapped set.\n \n 3. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \nResolution: Routine PSXVND was modified to call routine PSOCP without\n 4. From this menu, you may select to use the following options\n (when prompted for INSTALL NAME, enter PSX*2.0*35):\n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch\n is installed. It compares all components of the patch (routines,\n DDs, templates, etc.).\n c. Verify Checksums in Transport Global - this option will ensure\nqualification, in support of the Outpatient Pharmacy Copay enhancement\n the integrity of the routines that are in the transport global.\n \n 5. Use the Install Package(s) option and select the package PSX*2.0*35.\n \n 6. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//"\n respond NO.\n \n 7. When prompted "Want to DISABLE Scheduled Options, Menu Options, and \n Protocols? YES//" respond NO.\n \nproject.\n 8. If any routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\n \n\n
\nThis is an EMERGENCY patch and must be installed within 24 hours.\nwill be released to correct existing prescriptions so that they are billed\ncorrectly.\n \nResolution: The code has been modified to correct this problem.\n \n2. Problem: Error reported when division was missing from the \nprescription file for a Consolidated Mail Outpatient Pharmacy (CMOP) \nprescription.\n \nResolution: The code has been modified to find the first active division.\n \n1. Problem: The release of the Consolidated Mail Outpatient Pharmacy\n(CMOP) patch PSX*2*35 introduced a potential problem for Outpatient\nPharmacy divisions where the "BARCODES ON ACTION PROFILES" prompt, on the\nSite Parameter Enter/Edit [PSO SITE PARAMETERS] option, is set to "NO".\nBecause of this problem, there was no Co-pay charge for any CMOP\nprescription released after the installation of PSX*2*35. This patch\ncorrects the problem. A patch to Outpatient Pharmacy V.7.0, PSO*7*93,\n\n
\nThis patch is being distributed in response to NOIS ALN-0597-12107.\n\n
\n1. Problem: NOIS CMC-1101-31545 describes a situation where two \n"perfect" merge could occur, sending the wrong medication to a patient. \nAnalysis of this problem revealed that two patient orders were assigned \nthe same record number in the file that allowed overwriting of data to \noccur.\n \nResolution: Safeguards have been put in place to prevent the same record \nnumber from being used by two distinct patient orders.\n \n1. Problem: When prescriptions are transmitted to CMOP, an update is sent\nto the Computerized Patient Record System ( CPRS) that says the\npatient's prescription data gets merged within a Consolidated Mail \nprescription is no longer suspended, and now has an Active Status. The\nproblem occurred because the wrong number was being sent to CPRS, and this\ncaused the CPRS status of an Outpatient order to become active, when is\nshouldn't. No Pharmacy statuses were set improperly, only these CPRS\nstatuses, which would show on the Orders Tab.\n \nResolution: The CMOP code was passing the internal entry number of the \nwrong file to CPRS. The offending variable has been replaced by the \nvariable housing the correct value.\nOutpatient Pharmacy (CMOP) transmission. In this particular case, the \nprescription data was from a single pharmacy division. While building \nthe transmission, the prescription data from one patient was overwritten \nwith the data of another, but imperfectly, leaving remnants of the first \nas if appended to end of the data sequence. This instance posed no \nthreat to patient safety as the data stream was corrupted and caused the \ndownload to terminate. However, there is the slight possibility that a \n\n
\n1) Problem: Attempting to use the Print from Suspense File [PSO PNDLBL]\nwas not reporting the correct figures in certain instances.\n \nTransmit Data for All Divisions ? ? YES//\n \nJob queued: CHEYENNE VAM&ROC\nJob queued: FORT COLLINS CLINIC\nJob queued: GREELEY CLINIC\nJob queued: SIDNEY CLINIC\n \nResolution:\n \nThe software has been modified to correct these errors.\n \n3) Problem: The use of the PSX resource device has long been a source of\ndifficulty for the CMOP data transmission process. Anything from system\nfailures to users entering the wrong parameters in the file could result\nin two CMOP transmission jobs running at the same time. More often than\noption to send transmissions to Consolidated Mail Outpatient Pharmacy \nnot, this resulted in data merges between the simultaneously running\njobs.\n \nResolution:\n \nTo prevent this, a new method of ensuring that only one CMOP transmission\njob runs at a time has been developed. A data switch is set when a CMOP\ntransmission is started. No subsequent transmissions are allowed until\nthis switch is cleared. Also, transmission jobs waiting to run\nperiodically check the progress of the running job. If the running job\n(CMOP) hosts often resulted in an undefined error.\nexceeds allowable time limits, the jobs waiting are stopped and a message\nis sent to the users. If the time limit was exceeded due to system\nproblems and the original job finished normally, albeit very slowly, then\nthe user simply restarts the transmissions manually. If the time limit\nwas exceeded due to job failure, the troubleshooting process is not\ncomplicated by multiple transmission jobs. Because the waiting jobs were\nstopped, the chance of merging data is reduced considerably. Finally, the\nautomatic CMOP recovery process has been modified to reset the data switch\nif a software repair of the problem is possible.\n \n \n4) Problem: There are several CMOP processes that may be running\nconcurrently and trying to access the same files at the same time causing\none job or the other to error.\n \nResolution:\n \nThe locking of files has been moved to the record level letting each job\nperform its tasks.\n \n5) E3R 12510: There have been occurrences where control\nResolution:\ncharacters have been picked up in the patients address information and\nsent to the host sites breaking their import procedure.\n \nResolution:\n \nThe software has been modified to test and remove unwanted characters\nfrom the patients address information.\n \n6) Problem: Control characters are being observed within the\nprescriptions' SIGs. These and HL7 delimiter characters "|~^\\" in the SIG \n \n|\nbreak or scramble the communication to the vendors dispensing\nprescriptions.\n \nResolution:\n \nThe code has been modified to test for control characters and the HL7\ndelimiter characters "|~^\\". If found an error message is generated and |\nsent referring to the prescription, the refill number, and that the SIG\nis either invalid or missing. This safeguards the vendor transmission\nCode modifications have been made to prevent the error.\nprocess but does not resolve the issue of control characters getting\nplaced into the SIG.\n \n7) E3R 11958: The Print from Suspense File [PSO PNDLBL] option transmits\none division at a time. It is desired to have the option work transmit all\ndivisions if desired.\n \nResolution:\n \nThe software has been modified to provide the ability to process all\n \ndivisions. The process has also been modified to present two levels of\nquestions.\n \n \nSelect Suspense Functions Option: PR<cr>int from Suspense File\n \n 1 - Initiate Standard CMOP Transmission\n 2 - Initiate CS CMOP Transmission\n 3 - Print Current Division - Standard CMOP from Suspense\n 4 - Print Current Division - CS CMOP from Suspense\n2) Problem: The CMOP host Unreleased Rx's Report [PSX UNRELEASED] option\n 5 - Standard Print from Suspense\n \nSelect (1, 2, 3, 4, 5): 1\n \n 1 - Initiate Standard CMOP Transmission\n \nTransmit Data for All Divisions ? ? YES// ?\n \nYes - Transmit/Print All Divisions\nNo - Transmit/Print One Division: CHEYENNE VAM&ROC\n\n
\n1. Problem: If an inactive pharmacy division is discovered during a\nNOIS DAY-0102-42990\n \nResolution: Routine PSXVND has been modified to correct this error.\nConsolidated Mail Outpatient Pharmacy (CMOP) data transmission, the \nfollowing error message is generated: "Invalid or Missing Data". \n \nResolution: Routines PSXAUTO and PSXAUTOC have been modified to evaluate \nthe inactive date field during processing for the transmission.\n \n2. Problem: An error is encountered when CMOP fulfillment data is\nreceived back from the host to the medical center.\n\n
\n1. Problem: The patient prescriptions that have been suspended for \nadded to the MailMan message "CMOP Error Encountered", which is sent to \nthe holders of the "PSXMAIL" key.\n \n2. Problem: CMOP data validation does test and reject prescriptions \nwhose drug's warning is greater than eleven characters. However, no \nmessage is sent to inform the users and the users resubmit the \nprescriptions to have them again rejected without knowing why.\n \nResolution:\n \nConsolidated Mail Outpatient Pharmacy (CMOP) are transmitted to the CMOP \nThe CMOP data validation has been modified to set an appropriate entry in \nthe MailMan message "CMOP Error Encountered", which is sent to the \nholders of the "PSXMAIL" key.\n \n3. Problem: Transmissions do not test to see if a patient is in the \nprocess of being merged. \n \nResolution:\n \nThe transmission process code has been modified to test if the patient is \nhost even if the patient's mail status has been changed to "DO NOT MAIL".\nbeing merged. If a patient is being merged, the prescription remains in \nsuspense and an error entry is added to the MailMan message "CMOP Error \nEncountered", which is sent to the holders of the "PSXMAIL" key.\n \n4. E3R 12951: The patient name and ID are requested to be added to \nthe MailMan message "CMOP Error Encountered" generated where data needs \nto be corrected so prescriptions can be more easily corrected and then \nsent to the CMOP host.\n \nResolution:\n \n \nThe appropriate transmission error entries now include patient name & ID.\nThe MailMan message "CMOP Error Encountered" is sent to the holders of \nthe "PSXMAIL" key.\n \n5. E3R 11711: CMOP works in a divisional manner generating many messages. \nIt is requested that the subjects of the messages have a prefix of \ndivision number added so that the users can easily see which messages are \nfor their specific division.\n \nResolution:\nResolution:\n \nHigh volume messages' subjects have been recoded to include a division \nnumber as a prefix. The following MailMan message subjects have been \namended:\n \n"CMOP Error Encountered" which is sent to holders of the "PSXMAIL" key.\n \n"CMOP Not Dispensed Rx List" which is sent to holders of the "PSXMAIL" key.\n \n \n"CMOP Acknowledgement not Received" sent to holders of the "PSXCMOPMGR" key.\nThe CMOP functionality has been changed to test the mailing status of \npatients during the building of a transmission. If it has changed, the \nprescriptions for that patient are not sent and appropriate entries are \n\n
\nNOTE: Facilities will see the expected following error message as the \n \n1. E3R 9441: It is requested that the Facility Activity Report [PSX \nACTIVITY] option should allow time to be entered as part of the criteria \nfor setting the date range of the report.\n \nResolution: The report has been modified to sort by Date/Time vs. just \nDate.\n \n2. Problem: The vendor software is to send package ID and carrier \ninformation for each prescription that is completed. When that segment of \nsoftware will be installing a data field for the Consolidated Mail \ninformation is missing, the software trying to process the missing \ninformation generates an error.\n \nResolution: The code has been modified to accommodate instances of \nmissing information.\n \n3. E3R 9881: It is requested that a CMOP host site parameter be added to \ncontrol whether or not the report "CMOP DRUG Cost Missing" as processing \nof vendor data is performed.\n \nOutpatient Pharmacy (CMOP) hosts in a file the facilities do not have.\nResolution: The software has been modified and a new field CMOP DRUG Cost \nMissing Reports (#8) has been added to CMOP OPERATIONS file (#554) to \ncontrol the generation of the report "CMOP DRUG Cost Missing" \n \nThe editing of the parameter has been added to the CMOP host System \nParameter Enter/Edit [PSX SITE PARAMETERS] option.\n \nThis is the new text found within the existing option.\n \nCMOP DRUG Cost Missing reports: YES// ??\n \n This parameter controls the generation of the "CMOP DRUG Cost \nMissing" report.\n \n Choose from:\n Y YES\n N NO\nCMOP DRUG Cost Missing reports: YES// ?\n Do you want the "CMOP DRUG Cost Missing" error report generated? \n(Y/N)\n Choose from:\nInstalling Data Dictionaries:\n Y YES\n N NO\nCMOP DRUG Cost Missing reports: YES//\n \n** ERROR IN DATA DICTIONARY FOR FILE # 554 **\nData Dictionary not installed; Partial DD/File does not exist. \n \n\n
\n1) Problem: The facility patient data can contain the character "|". \n2) Problem: The outpatient function 'Print Current Division - Standard \nCMOP from Suspense' generates an error "undefined variable PSXPTR" while \nprinting outpatient suspense labels.\nHAM-0302-21530\n \nResolution: The code has been modified so that the variable being used \nis proper and defined.\n \n3) E3R 11027: It is requested that the patient phone number be \ntransmitted to the Consolidated Mail Outpatient Pharmacy (CMOP) facility \nThis disrupts the transmission interpretation as that character is used \nas part of the patient address. It is required information for overnight \ndelivery of packages.\n \nResolution: The software has been modified to pull the patient phone \nnumber from Veterans Health Information Systems and Technology \nArchitecture (VISTA) and provide it to the vendor software. \nas a separator in processing the data streams.\nCMH-0801-N0271\n \nResolution: The software has been modified to substitute the space \ncharacter " " for the "|" as the patient data for transmissions is being \nbuilt.\n \n\n
\n1) Problem: The Consolidated Mail Outpatient Pharmacy (CMOP) software is \nproper patient associated with the prescriptions being reported.\nTNV-0502-32862\nCLE-0702-40600\nCMD-0702-71865\n \nResolution: The code has been modified to reflect the proper patient \nname and social security number (SSN) on each line in the error next to \nthe prescription number.\n \n3) Problem: Prescriptions that are in CMOP suspense, for patients who \nerroneously including prescriptions currently being filled in the list of\nare having their mail routing changed in a manner that would disable them \nfrom going to CMOP, are not dropping into local suspense but are \nremaining in CMOP suspense.\nISB-0702-30004\n \nResolution: The code has been modified to notify the user and move the \nprescription into local suspense and create an activity log entry.\nprescriptions in suspense for future processing.\nCON-0502-11795\nCMC-0602-30991\n \nResolution: The code has been modified to correct the problem.\n \n2) Problem: The "CMOP Error Encountered" message is not displaying the \n\n
\n!! NOTE: !! Health care facilities do not have the Consolidated Mail \n \n460-1625-167 1113467A 1 POTASSIUM CHLORIDE 8MEQ TAB,SA P0086\n460-1625-167 1113468A 1 RANITIDINE HCL 150MG TAB R0005\n460-1625-167 1113469A 1 SIMVASTATIN 40MG TAB S0022\n460-1625-167 1113495A 1 ISOSORBIDE DINITRATE 20MG TAB,ORAL I0076\n1. Enhancement: CMOP HOSTS: A new field, CONTROLLED SUBSTANCE (#21)\nhas been added to CMOP REFERENCE file (#552.1) to track controlled\nsubstance transmissions.\n \n552.1,21 CONTROLLED SUBSTANCE 0;8 SET\n \n '0' FOR Non-CS Transmission; \n '1' FOR CS Transmission; \n LAST EDITED: MAY 21, 2002 \nOutpatient Pharmacy (CMOP) Reference file and the installation will\n HELP-PROMPT: Enter a 0 or 1, 1 for Controlled \n Substances Transmission\n DESCRIPTION: A 1 indicates that this CMOP batch \n contains controlled substances.\n \n TECHNICAL DESCR: This field is populated by routine \n PSXRECV. This field should not be edited\n by users.\n \n CROSS-REFERENCE: 552.1^C \ngenerate an error that can be ignored for health care facilities.\n 1)= S ^PSX(552.1,"C",$E(X,1,30),DA)=""\n 2)= K ^PSX(552.1,"C",$E(X,1,30),DA)\n This cross reference is set when a \n transmission is downloaded from the\n medical center. A 1 indicates the\n transmission is a controlled substance\n transmission. \n \n \n2. E3R 9440: CMOP HOSTS: It is requested that the Unreleased Rx's \n \nReport [PSX UNRELEASED] be modified to included selection of date ranges,\nfacilities, and types of transmissions (Controlled Substances and \nNon-Controlled Substances). It is also requested to reveal and\nsort by the order number within the batches displayed.\n \nResolution: The code has been modified to accommodate the requests. An\nexample of the new user dialog and printout follows.\n \nSelect OPTION NAME: PSX REPORTS MENU Reports\n \nThe error reported is:\nSelect Reports Option: Unreleased Rx's Report\n \n \nSelect CMOP Batch # or RETURN for all: ?\n \n Answer with CMOP REFERENCE FACILITY BATCH REFERENCE\n Do you want the entire 70522-Entry CMOP REFERENCE List? N (No)\nSelect CMOP Batch # or RETURN for all: <CR>\n \n (NOTE: If a single batch is selected the dialog skips to the device question.)\n \n \n Select one of the following:\n \n C Controlled Subs\n N Non-Controlled Subs\n B Both\n \nEnter response: ?\n \nEnter "C" to report controlled substances, "N" for non-controlled\n** ERROR IN DATA DICTIONARY FOR FILE # 552.1 **\nsubstances or "B" to include both.\n \nEnter response: Both\n \nEnter date to BEGIN SUMMARY: TODAY//T-30 (JAN 23, 2001)\nEnter date to END SUMMARY: TODAY//T-2 (FEB 20, 2001)\n \nSelect FACILITY or RETURN for all: ?\n \n Answer with CMOP NATIONAL SITE FACILITY, or STATUS\nData Dictionary not installed; Partial DD/File does not exist.\n Do you want the entire 72-Entry CMOP NATIONAL SITE List? N (No)\nSelect FACILITY or RETURN for all:\n \nDEVICE: HOME// TELNET\n \n \n Report of Unreleased Rxs for Transmission 460-1625\n Printed : Feb 22, 2001 4:12:32 pm\n \nFacility: WILMINGTON, DE Pharmacy Division: WILMINGTON VAMC\n May 22, 2002@10:07:09\nTransmitted: Feb 21, 2001 0:02:33 am Received: Feb 20, 2001 11:25:03 pm\nBatch Type: Non-Controlled Substance\n \nORDER # RX NUMBER FILL DRUG NAME DRUG ID\n----------------------------------------------------------------------------\n \n460-1625-13 1064494C 3 ISOSORBIDE DINITRATE 20MG TAB,ORAL I0076\n460-1625-13 1079105C 3 FUROSEMIDE 40MG TAB F0078\n460-1625-13 1118354B 3 SPIRONOLACTONE 25MG TAB S0043\n460-1625-167 1172873 3 NITROGLYCERIN 0.4MG TAB,SUBLINGUAL N0057\n\n
\n!! NOTE: !! Health care facilities do not have the CMOP NATIONAL \n \n** ERROR IN DATA DICTIONARY FOR FILE # 552.4 **\nData Dictionary not installed; Partial DD/File does not exist.\n \n** ERROR IN DATA DICTIONARY FOR FILE # 554 **\nData Dictionary not installed; Partial DD/File does not exist.\n \n \nThis patch is being distributed to support the Veteran Affairs/Department\nof Defense (VA/DoD) Consolidated Mail Outpatient Pharmacy (CMOP) \nSITE file (#552), the CMOP MASTER DATABASE file (#552.4), nor the CMOP\nInterface project. The modifications contained herein allow VA CMOPs to\nexchange prescription orders and fulfillment data with DoD Medical\nTreatment Facilities. A new DOD CMOP INTERFACE [PSX DOD CMOP INTERFACE]\noption and new key PSXDOD and several new fields are being added \nto support the changes needed. See Appendix C of the CMOP Technical\nmanual for further information on the data exchange process and the HL7 \nsegment definitions.\nOPERATIONS file (#554) and the installation will generate an error that\ncan be ignored for health care facilities.\n \nThe errors reported are:\n \n** ERROR IN DATA DICTIONARY FOR FILE # 552 **\nData Dictionary not installed; Partial DD/File does not exist.\n\n
\nProblem: The information form that prints from Consolidated Mail \nprescription release. (Prior to patch PSO*7*71, the copay status was only \nre-evaluated for new prescriptions and renewals, not for each refill).\nOutpatient Pharmacy (CMOP) may display the copay status incorrectly at\ntimes. (e.g. it may say "NO COPAY" but when the fill is released, no\nexemptions from copay can be found so the status is changed to copay.)\nThe copay status is not being determined correctly for each fill of a \nCMOP prescription.\n \nResolution: Modified code to determine the current copay status for each \nfill which includes the same checking that is done at label print and \n\n
\nThis patch is being distributed as a correction to patch PSX*2*4.\n\n
\nProblem: The [PSX START BACKGROUND FILER] Start/Stop Background \nFiler option was erroring out.\n \nResolution: Modified code to correct error.\n\n
\nThis patch will correct an Archive problem due to the entry of Month/Year\nbeing entered as Month/Day\n\n
\nNOTE:\nacross the VistA applications.\nprescriptions when that particular fill for resubmission has been\ncanceled.\n \n8. E3R 18029 It is possible for the remote sites to input more \ninformation into the NARRATIVE REFILLABLE RX (#1004), NARRATIVE\nNON-REFILLABLE RX (#1005), and NARRATIVE FOR COPAY DOCUMENT (#1006) text\nfields in the Outpatient Site file (#59), than can be printed at the\nCMOPs.\n \nSolution: The transmission process will now load only up to seven lines\n \n(80 characters per line) of information from each of these fields. The\nfollowing warning message is also sent to the facility CMOP users when a\ntransmission has had to limit the number of lines being sent to the CMOP.\n \nSubj: >>WARNING<< CMOP Outpatient Site narrative Instructions [#140709]\n05/16/03@15:21 8 lines\nFrom: Smith,John In 'IN' basket. Page 1\n--------------------------------------------------------------------------\nThe following Outpatient Site file (#59) narrative field(s) exceed seven \nlines.\nNOTE:\nThis exceeds CMOP limits.\nLines beyond seven are not being sent to the CMOP.\n \nOutpatient Site: TROY\nNARRATIVE REFILLABLE RX 36 lines\nNARRATIVE NON REFILLABLE RX 49 lines\nNARRATIVE FOR COPAY DOCUMENT 16 lines\n \n \n9. Problem: It has been found that during the building of a transmission\nCMOP hosts will see the expected following error messages as the software\nother VistA applications are able to perform edits, refills, copies, and\ndeletions of prescriptions that are being loaded into the CMOP\ntransmission.\n \nSolution: The use of a new integration agreement with Order Entry /\nResults Reporting (OE/RR) version 3 provides a way to let CMOP identify \nthe prescriptions that are being transmitted so that they will not be\nprocessed by other VistA applications. A related OE/RR patch OR*3*183 has\nbeen released that will complete the ability for CMOP to identify the\nprescriptions.\nwill be installing data fields for the facilities in files that the CMOP\n \n10. Problem: Prescriptions have been processed to the CMOPs when they \nshould have dropped out of CMOP processing because of the patient's \nmailing status.\n \nSolution: The code has been changed so that the prescriptions are dropped \nout of CMOP suspense for patients who have an incompatable mailing status \nfor CMOP processing.\n \nNOTE: There have been several fields added to the CMOP SYSTEM file (#550)\nhosts do not have.\nand the CMOP TRANSMISSION file (#550.2) to support the changes listed\nfor this patch.\n \n Installing Data Dictionaries:\n \n ** ERROR IN DATA DICTIONARY FOR FILE # 550 **\nFacilities are required to have installed PSO*7*126.\n Data Dictionary not installed; Partial DD/File does not exist\n \n ** ERROR IN DATA DICTIONARY FOR FILE # 550.1 **\n Data Dictionary not installed; Partial DD/File does not exist\n \n ** ERROR IN DATA DICTIONARY FOR FILE # 550.2 **\n Data Dictionary not installed; Partial DD/File does not exist\n \nCMOP hosts may ignore a portion of the installation instructions as they\npertain to functionalities found only at the remote facilities.\nThere is a partner patch that is being distributed previous to PSX*2*41.\n \nNOTE: If you have batches (transmissions) that you are planning to\nre-transmit, do so prior to installing PSX*2*41. The Re-transmit CMOP\nData [PSXR RETRANSMIT] option has been re-coded to match the new data\narchitecture being used in PSX*2*41 and will not be able to resend batches\nprior to installation of PSX*2*41.\n \n \n1. Problem: Controlled Substance (CS) and Non-Controlled Substance\n(NON-CS) prescriptions are being mixed into the same batches when the\nThe partner patch is Outpatient Pharmacy V. 7.0 PSO*7*126. This will be\nrecovery process is cleaning up a broken transmission. The original\nrecovery process was written when there was only one type of prescription\nbeing sent and it includes remnants of the previous transmission in\nthe current transmission.\n \nSolution: The recovery process has been re-written to reset the\nprescriptions to a state as if they were just queued waiting for\ntransmission.\n \n2. Problem: There have been instances where the prescriptions of two\ntested in the environmental checking phase of the installation and not in\npatients have been merged into the same HL7 order in the CMOP RX QUEUE\nfile (#550.1).\n \nSolution: The use of the CMOP RX QUEUE file (#550.1) has been redesigned\nto be only used in the building of the HL7 order messages and it is\ncleared out prior to and after each transmission. The access to the CMOP\nRX QUEUE file (#550.1) is locked by the transmission job when it\nfirst starts up and is released as the last step as the transmission\nfinishes.\n \nthe KIDs required patches section. Consolidated Mail Outpatient Pharmacy\n3. Problem: Several sites have reported that they were not able to\nre-direct the scheduling of their transmissions to another\nConsolidated Mail Outpatient Pharmacy (CMOP). There are several fields\nwithin the scheduling that have a database required criteria set. This\nmakes it difficult for the software to clear them and reset them.\n \nSolution: The scheduling of transmissions has been redesigned to use the\nKernel Option Scheduling and its utilities. This streamlines the user\ninput and control of the scheduling of the transmissions. Transmissions\nmust now be scheduled no closer than two hours apart.\n(CMOP) hosts are not required to install PSO*7*126. There is also a\n \n4. Problem: The beginning message number within a transmission sometimes\ndiffers from the notation within the message.\n \nSolution: The use of the CMOP RX QUEUE file (#550.1) has been redesigned.\nIt is now cleared out prior to each transmission and each transmission\nnow starts with the number one.\n \n5. Enhancement: Other Language - Data elements in the HL7 messages are\nbeing activated that will enable the SIG and PMI sheets to be printed in\ncompanion ORDER ENTRY / RESULTS REPORTING (OERR) patch OR*3*183 that is\nanother language. This is in co-ordination with the emerging Outpatient\nPharmacy V. 7.0 'Other Language' patch PSO*7*117.\n \n6. Problem: It is possible to create duplicate active prescriptions\nthrough the renewal and copy prescription functions if the prescription\nis a part of a currently running CMOP transmission.\n \nSolution: The transmission software has been modified so that the\nsetting of prescription status flags occurs in a manner that will keep\nthe renewal and copy functions from accessing prescriptions that are\nneeded to complete the locking and ownership/protection of prescriptions\nbeing loaded into a CMOP transmission. A prescription may be locked by a\nuser and if so that prescription is skipped and a "RX OERR/CPRS Locked"\nerror is itemized with other correctable prescription errors and sent to\nthe holders of the "PSXMAIL" key.\n \n7. Problem: A prescription that has been sent to CMOP, not filled, and\nthen is canceled locally is selectable for resubmission to the CMOP and\ngenerates a program error when being processed.\n \nSolution: The software has been amended to not allow the resubmission of\n\n
\nProblem: Patch PSX*2*41 is sending NTE|5 segments that it shouldn't. This\nproblem was not uncovered at the testing sites.\n \nResolution: The code has been modified to correct the array carrying the\nlist of NTE|5 segments.\n\n
\nRemove mail message when there is a mail status change and the RX is \nsuspended locally.\nWhen there is a test patient (ssn=000-00) put "Test Patient" under the \nData Field heading of the mail message instead of "Patient Address".\n\n
\nThe Chief Business Office (CBO) is requesting modifications to several\nSoftware to support the Combat Veteran (CV) initiative is being developed\nand introduced in a phased implementation strategy. The reason for this\ntype of deployment is due to the complexity of the functionality and the\nnumber of product line dependencies. Phase I: Combat Veteran Interim\nSolution (CVIS) was a VistA only solution that involved development in\nthe Integrated Billing (IB) and Registration/Enrollment product lines.\nIt provided the logic to identify those veterans who met the criteria for\nthe combat veteran eligibility and provided billing reports\ncross-referenced against this identifier to aid in the copayment billing\nprocess. Phase II of this initiative will involve multiple product lines\nVeterans Health Information Systems and Technology Architecture (VistA)\nand additional VistA only development. The main goals of Phase II will be\nto fully automate the copayment billing processing of combat vets based on\nepisode of care by providing the appropriate questions at check-out as\nsupplied by CPRS.\n \nProduct lines that have a stake in Phase II development include\nEnrollment/Registration (VistA), IB, Outpatient Pharmacy, Consolidated\nMail Outpatient Pharmacy (CMOP), CPRS/TIU, Patient Care Encounter (PCE),\nAmbulatory Care, Event Capture, Scheduling and PTF. The National Patient\nCare Database (NPCD) will also require modifications to capture workload\npackages to support implementation of VHA Directive 2002-049 - "Combat\nreporting. The patches are listed below in the order that they must be\ninstalled:\nOutpatient Pharmacy\n PSO*7*157\n PSX*2*50\nPCE/PTF/Event Capture/Scheduling - PIMS Host file\n PX*1.0*130\n SD*5.3*325\n DG*5.3*565\n EC*2.0*54\nVeterans Are Eligible For Medical Services For 2-Years After Separation\nIntegrated Billing\n IB*2.0*247\nCPRS\n OR*3.0*190\nProduct Features\nThere are three main areas addressed by this enhancement:\na. Identification/Notification of a CV Status veteran seeking medical care\n - The clinical applications shall obtain the CV Status for those\n veterans who qualify as such per the directive.\n - The CV Status identification shall be displayed to the appropriate\nFrom Military Service Notwithstanding Lack Of Evidence For Service\n audience (pharmacist, clinician providing care, intake personnel,\n schedulers, etc.).\n - Provider shall be able to identify whether care provided CV veteran\n was for a condition potentially related to combat service in the same\n manner as identification of exposure related care; care for SC\n conditions, etc.\nb. Assistance in the communication of a treatment being determined as\n Combat Related\n - Provide a means for the billing and pharmacy software package to\n identify these patients and services provided care for a combat\nConnection", which iterates VA's policy to provide medical care and other\n related condition.\nc. Automatically precludes inpatient and outpatient medical care,\n prescription and Long-term care copayments for CV Status veterans whose\n treatment/service has been deemed combat related.\n \nThis is the Consolidated Mail Outpatient Pharmacy (CMOP) patch PSX*2*50,\nthat provides the functionality changes to accommodate the new copay\nclassification called "Combat Veteran".\n \nAs part of the Combat Veteran II project, Outpatient Pharmacy V. 7.0 patch\nmedical services to combat veterans despite the absence of proof of\nPSO*7*157, introduced the COMBAT VETERAN field (#122) to the PRESCRIPTION\nfile (#52). This new COMBAT VETERAN field (#122) of the PRESCRIPTION file\n(#52) stores the data related to the copay exemption question, "Is this\nRx potentially for treatment related to Combat?".\n \nDuring CMOP transmission of prescriptions, if a prescription is deemed\n"Billable", the software does a check on the following copay exemption\nfields of the PRESCRIPTION file (#52):\n \n117 MILITARY SEXUAL TRAUMA\nservice connection.\n118 AGENT ORANGE EXPOSURE\n119 IONIZING RADIATION EXPOSURE\n120 ENVIRONMENTAL CONTAMINANT\n121 HEAD AND/OR NECK CANCER\n122 COMBAT VETERAN\n \nIf the prescription is identified as copay exempt, the software will\ntransmit "Not Billable" to CMOP.\n \n\n
\nThis patch will display the the Date Shipped in PSX RX INQUIRY in an \nexternal format.\n\n
\nNOTE: This patch addresses the Centralized Mail Outpatient Pharmacy / \nData Dictionary not installed; Partial DD/File does not exist.\n \n1) Problem: Internet ftp processes are sometimes interrupted or \nterminated in the middle of transmission leaving partial files deposited \non the target system. These are not the full files and if processed will \nresult in incomplete data sets.\n \nResolution:\n \nCode has been put in place to test the integrity of the received patient \nDepartment of Defense (CMOP/DoD) functionalities. Facilities will see no \ndata files and the sequencing of segments within the files. Files failing \nthe tests are not processed.\n \n2) Problem: Criteria of checking the integrity of the patient orders \nwas coded in the original 2.3.1 HL7 transmissions but was dropped when \nVitria Businessware started performing the conversions to HL7 2.1.\n \nResolution:\n \nCode has been put in place to perform the integrity checking of the \nimpact on their systems.\npatient orders in the current HL7 2.1 format as received from Vitria \nBusinessware.\n \n3) Problem: The VA internal wan between Leavenworth and Charleston \nwould drop causing the files to be lost that were to be delivered to the \nDoD "Outbox" for their pickup.\n \nResolution:\n \nCode has been put in place that tests the success of the placement of the \n \nfiles and if they were not placed they are stored for later placement \nwhen the wide area network is back in proper operation.\n \n4) Problem: The naming of the DoD files contains a Julian date with \na four digit time. There have been occasions when the time had no \nseconds, or multiples of 10 seconds. The trailing zeros representing \nseconds were being dropped.\n \nResolution:\n \n!! NOTE: !! For health care facilities that do not have the CMOP MASTER \nThe code has been modified to insure trailing zeros are included.\n \n5) Problem: The resending of release data to the sites generates an \nundefined error.\n \nResolution:\n \nA variable named AGNCH was corrected to be AGNCY.\n \n6) Problem: The date transmitted element in DoD $XMIT segments is in\nDATABASE file (#552.4), this installation will generate the following \nHL7 format while transmissions from VA facilities is in a FileMan \n(FM)format. This causes bad date data in the CMOP host files.\n \nResolution:\n \nThe DoD VistA import software has been modified to convert the HL7 format \nto FM format before handing the files to the CMOP host software.\n \n7) Problem: Patch PSX*2*38 introduced an 'E' index on the RX INDEX \nfield (#40) of the RX NUMBER multiple field (#1) in the CMOP MASTER \nerror that can be ignored.\nDATABASE file (#552.4). The presence of this new index caused confusion \nfor FileMan and it would do lookups first in the 'E' index instead of the \n'B' index of the RX NUMBER multiple. This would present the user entries \nother than what they were looking for.\n \nResolution: The 'E' index is to be removed from the file.\n \nNOTE: If a CMOP has modified the RX INDEX field (#40) locally they will \nneed to be able to re-do their modifications after the installation. This \ninstallation will remove the field entirely and then put it back with the \n \nofficial distribution definition without an 'E' index.\n** ERROR IN DATA DICTIONARY FOR FILE # 552.4 **\n\n
\n1) Problem: The retransmission of a batch failed to complete the \n \n2) Problem: The controlling data is stored in ^XTMP and is subject \nto a periodic KERNEL job that clears out the ^XTMP global after midnight \nif the job extends beyond midnight. That has occurred and the job shut \ndown.\n \nResolution:\n \nThe parameter in the ^XTMP setting has been set to protect the global for \ntwo days.\nupdating of prescription statuses in Prescription file #52 and RX \nSuspense file #52.5\n \nResolution:\n \nCode has been put in place to complete the updating of prescriptions \nstatuses in Prescription file #52 and RX Suspense file #52.5 for \nretransmissions.\n\n
\nMissing CMOP multiples.\n \nError when site street address is not completed.\n\n
\nThis patch is being distributed in response to NOIS MAR-0897-21215.\n\n
\nThis project involves six different applications that have been significantly\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*148\n CMOP and remains in the queue to be transmitted in the next CMOP \n transmission. The prescription will not be transmitted to CMOP until the\n reject is resolved by the user through the Outpatient Pharmacy V. 7.0 \n application. No message is generated for prescriptions in this category.\n INTEGRATED BILLING (IB) V. 2.0 IB*2*276\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*90\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*48\n ACCOUNTS RECEIVABLE (AR) V. 4.5 PRCA*4.5*230\n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*1\n \nVeterans Health Information Systems and Technology Architecture (VistA) \nsoftware applications and infrastructure were enhanced, in order to allow the\nelectronic transmission of outpatient pharmacy prescription claims (WINDOW and\nchanged to enable VA Medical Centers to perform third party electronic billing\nMAIL fills) to third party payers via the network connections available\nthrough the Austin Automation Center (AAC). VistA will be enhanced to receive\nelectronic adjudicated responses from the third party payers, which include\nreal-time processing for Drug Review Utilization and Refill Too Soon rejects.\nReject information will be displayed to the pharmacist as the prescription is\nbeing processed. The pharmacist will have the capability to take the\nappropriate action to ensure patient safety or to override the reject and\nresubmit the claim to the payer for payment. When a status of "PAYABLE" is\nreturned by the payer for a released prescription, VistA will automatically \ncreate the bill in IB, authorize it and immediately create the receivable in\nfor prescriptions. \nthe AR application. Since the exact amount being paid by the payer is known,\na decrease adjustment will be automatically generated and applied so that the\nreceivable is equal to the net amount due from the payer.\n \nThe system also provides electronic payment matching capability (for\nelectronically billable outpatient pharmacy prescriptions) using the existing\nElectronic Data Interchange (EDI) Lockbox functionality which processes other\nelectronic payments from third party payers. This real-time electronic claims\nprocessing capability will be provided in accordance with the Healthcare\nInsurance Portability and Accountability Act (HIPAA), EDI transactions and \n \nthe National Council for Prescription Drug Programs (NCPDP) mandated format \nstandards, specifically NCPDP Telecommunication Standard V. 5.1. Additional \nfunctionality delivered with this project includes: \n \n . Auto-Release/Outpatient Pharmacy Automation Interface (OPAI) Integration.\n . Back-billing capability to allow electronic billing of claims from within \n the IB application.\n . Capability to MOVE a group of subscribers from one insurance plan to \n another while automatically "expiring" the old plan, which is a major\n time saver.\nBelow is a list of all the applications involved in this project along with\n . Pharmacy Dispensed As Written (DAW) prescription processing.\n \nOverview of the Process:\n \nWhen a prescription is about to be filled and dispensed by the pharmacy, the \nOP application submits the prescription to the new ECME application. ECME then\ncontacts IB to verify whether or not the prescription is electronically\nbillable. If so, ECME gathers the information necessary to generate a NCPDP\nclaim. The claim information is passed to the VistA Health Level Seven (HL7)\npackage. The HL7 package then sends the billing information to the AAC, where\ntheir patch number:\nit is routed to the corresponding third party insurance via Emdeon (formerly\nWebMD).\n \nOnce the payer processes the information, the response coming back from the\npayer is passed back to the site that made the request, and the information\nis stored in the ECME package. If the third party payer accepted the claim,\nthe adjudicated information is passed along to IB. If the claim was rejected\nthe problem can be worked on and a new claim can be submitted to the payer.\n \nFor electronically billable CMOP prescription processing, the third party\n \nclaim is sent before the prescription information is transmitted to the\nCMOP facility to be filled. Once the adjudicating response is electronically \nreceived from the third party payer, if there are no Drug Utilization Review\nor Refill Too Soon rejects, the prescription is then transmitted to the CMOP \nfacility. When the CMOP center sends the dispensing information back to VistA,\nthe National Drug Code (NDC) information is checked against the NDC sent to \nthe third party payer and, if different, a new claim is generated in the \nbackground and is sent to the third party payer. In case the CMOP facility \nindicates that it is unable to fill a "PAYABLE prescription fill, a reversal\nis automatically submitted to the third party payer for the corresponding \n APPLICATION/VERSION PATCH\nfill.\n \nThis patch modifies the CMOP application to submit electronic claims for \nprescriptions that are transmitted to CMOP centers to be filled and dispensed \nremotely. All the prescriptions ready to be included on the batch to be\ntransmitted to CMOP are first transmitted to the third party insurance. Once\nthis step is completed, the system waits 60 seconds before the actual\ntransmission to CMOP starts. This process will affect the existing CMOP\nfunctionality in two ways: \n \n -----------------------------------------------------------------\n 1) If a response from the third party payer is not received by the time the \n prescription is ready to be transmitted to CMOP, the prescription is\n skipped and remains in the queue for the next CMOP transmission. A Mailman\n message containing all the prescriptions in this category is generated at \n the end of the process and it is transmitted to all the holders of the \n PSXMAIL security key. If no users on the system have this key, the Mailman\n message is sent to all the users holding the PSXCMOPMGR security key.\n \n 2) If the third party payer rejects the claim due to a DUR (Drug Utilization\n Review) or a 'REFILL TOO SOON' reject, the prescription is not sent to\n\n
\nThis patch supports the National Council for Prescription Drug Programs (NCPDP) \n(ECME) claim; updates to the Rx Activity Log; and permanent storage of Claims\nactivity information as reported by the ECME Billing Events Report.\n \nThis patch modifies the CMOP application in the following ways:\n \n1) The process responsible for transmitting of prescriptions to the \n Consolidated Mailout Outpatient Pharmacy (CMOP) facilities was changed to\n perform the following check: \n \n For ePharmacy prescriptions only, before a fill can be transmitted to \nstandard which was adopted under the Healthcare Insurance Portability and \n the CMOP facility, the previous fill cannot be pending to be filled at\n the CMOP facility. For example, before transmitting refill 1 to the \n CMOP facility, the software will check if the original is currently\n being filled by CMOP. If so, the refill 1 will be held until the \n original fill process is completed by the CMOP facility. \n \n2) Changed the second line of the routine PSXVND by adding the patch\n numbers 1 and 2 to the list of patches. These patch numbers were\n unintentionally removed by patch PSX*2*48.\nAccountability Act (HIPAA) for pharmacy claims. This patch is one of six to be\nreleased. Three patches will be released in a KIDS multi-build distribution \ncontaining: BPS*1*3, PSO*7*247, and IB*2*342. Three patches will be released\nindividually and they are: PRCA*4.5*247, PSX*2*62, and PSS*1*115.\n \nEnhancements included in the release of the six patches are a new option that \nwill enable the user to reopen a closed Electronic Claims Management Engine\n\n
\nThis patch contains an Application Program Interface (API) that will be \n \nThis API replaces the following integration agreements:\n \nDBIA # Affected Package(s)\n---------------------------\n2199 CPRS\nused by calling applications that currently do direct global reads or \nwrites to the CMOP SYSTEM file (#550). Since this file is being replaced \nas part of the Pharmacy Re-engineering project, any direct M-based global \nreads or writes to this file must be replaced by calling the APIs provided \nin this patch. When the new data source is in place, the calling \napplications will not be required to make any changes, because these APIs \nwill be flexible enough to retrieve the requested data from the new data \nsource, when the time comes.\n\n
\nAs part of the Outpatient Pharmacy V. 7.0 Laser Labels Phase II project, \nwarning labels, this patch uses a new CMOP WARNING LABEL SOURCE field \n WARNING LABEL TEXT is the complete text of the specified warning \n number (maximum length is 200 characters). \n \n Example: \nZX1|300993|514^TROY|M|1|(1of12)|WHITE,ELAINE|1|(***/***)|20061122|1|1|1|30\n|\n|500\n-5294709|SCL50|UNKNOWN|\nNTE|11|300993|ENG|1N|May cause drowsiness. Alcohol may intensify this |\neffect. Use care when operating a car or dangerous machines.\n(#16.1) in the PHARMACY SYSTEM file (#59.7), also set by using the \nNTE|11|300993|ENG|62N|May cause dizziness|\nNTE|11|300993|ENG|11N|Avoid prolonged or excessive exposure to direct |\nand/or ar\ntificial sunlight while taking this medication.\nNTE|11|300993|ENG|61N|May cause blurred vision|\nNTE|11|300993|ENG|13N|It is very important that you take or use this |\nexactly as directed. Do not skip doses or discontinue unless directed by\nyour doctor.\nNTE|11|300993|SPA|1N|Puede causar somnolencia. El alcohol puede |\nintensificar es te efecto. Tenga cuidado cuando conduzca veh!culos\nPharmacy System Parameters Edit [PSS SYS EDIT] option. This should be set\nautomotores u opere maquinar ia peligrosa.\nNTE|11|300993|SPA|62N|Puede causar mareo.|\nNTE|11|300993|SPA|11N|Evite exponerse excesivamente o por per!odos |\nprolongados a los rayos solares directos y/o artificiales mientras tome\neste medicamento.\nNTE|11|300993|SPA|61N|Puede causar visi"n borrosa.|\nNTE|11|300993|SPA|13N|Es muy importante que lo tome o lo use exactamente |\nseg#n las indicaciones. No omita ninguna dosis ni lo deje de usar a menos\nque lo mande el mdico.\n \nto "N" for "New" to send the new warnings to CMOP. This field is added by \n \nAlso included in this patch is a fix for several Remedy tickets regarding \na null subscript when a prescription was discontinued during transmission.\nIf the prescription was discontinued, the CMOP TRANSMISSION file (#550.2)\nreference for that prescription is cleaned up.\n \nAlso added to this patch is the check for the value of the PROJ 112/SHAD\nfield (#122.01) in the PRESCRIPTION file (#52) as an additional\nEnvironmental Indicator check to determine whether to send a copay or no \ncopay indicator to CMOP. The patch that creates this new field, PSO*7*225,\npatch PSS*1*120.\nwill be released along with Computerized Patient Record System (CPRS)\nGUI27. The added check in this patch will have no effect until PSO*7*225 \nis installed.\n \nIf the BAD ADDRESS INDICATOR field (#.121) in the PATIENT file (#2) is set\nand there is no active temporary address for the patient, the fill will\nappear on the CMOP reject log and will remain in suspense, but unmarked\nfor CMOP. It will print when the local print from suspense is done to be \na new commercial data source is utilized to provide warning label source\nfilled locally.\n \n \n**************** NOTE ***************************************************\nAs the CMOP side also had to make programming changes, verify that the\nCMOP that your site sends to can receive the new warning label format.\nThen after setting the CMOP WARNING LABEL SOURCE field (#16.1) to "New",\nsend a small batch and verify that it was received and able to be\nprocessed successfully. (As of the release of this patch, only the Bedford\nCMOP was not yet ready to receive the new format).\ninformation. The new warning labels are enabled for printing on the laser \n**************************************************************************\n \nThis patch adds the sending of the INTEGRATION CONTROL NUMBER field \n(#991.01) from the PATIENT file (#2) if it is a national number. This \nnumber is concatenated with the letter "V" and the ICN CHECKSUM field\n(#991.02) from the PATIENT file (#2) and is sent as the 18th subscript of\nthe PID segment. (See example under item 1 below).\n \n \nWhen the CMOP WARNING LABEL SOURCE is "New", the format and/or content of\nlabels when the WARNING LABEL SOURCE field (#16) of the PHARMACY SYSTEM\nthe following segments will be changed:\n \n1. For the Patient Identification (PID) segment, the Patient Medication\nInstruction (PMI) preference will be sent as "ENG" for English or "SPA"\nfor Spanish instead of the current numeric values.\n \n Example:\nPID||000007890^1^M11||OPPATIENT^ONE||||12345 S MAIN ST^ADDRESS |\nLINE2^MADISON ^WI^53705|(000)555-1212|SPA||1011007381V739824\n \nfile (#59.7) is set to "N" for "New". Parameters for using the new \n2. Currently, the first part of the English language medication \ninstruction (SIG) is sent in the RX1 segment and continuations are sent in\nNTE|7 segments. Additional fields added to the NTE|7| segment when the \nnew|\nwarning source flag is set are:\n \nNTE|7|RX NUMBER|LANGUAGE CODE|NUMBER|TEXT (TEXT is up to 100 characters |\nper NTE|7| segment) \nWhere: \n RX NUMBER is the external prescription number from the PRESCRIPTION\nwarning labels are set using the Pharmacy System Parameters Edit [PSS SYS \n file (#52). \n LANGUAGE CODE will be "ENG" for English or "SPA" for Spanish. \n NUMBER is a sequence number for the SIG lines starting at 1 for\n each different language code.\n \n Example:\nRX1|500-300993-1||||||90|D0132^DOXEPIN HCL 25MG CAP^L|||11|\n20061122|11| |20071123|20061122|300993||TAKE TWO CAPSULES MOUTH THREE\nTIMES A DAY FOR 7 D AYS, THEN TAKE ONE CAPSULE\nNTE|7|300993|ENG|1|TWICE A DAY FOR 7 DAYS, THEN TAKE ONE CAPSULE AT |\nEDIT] option.\nBEDTIME FOR 7 DAYS, THEN TAKE\nNTE|7|300993|ENG|2|ONE CAPSULE EVERY OTHER DAY FOR 7 DAYS |\nNTE|7|300993|SPA|1|TAKE DOS CAPSULES MOUTH THREE TIMES A DAY PARA 7 DIAS, \n|\nTHEN TAKE UNO CAPSULE\nNTE|7|300993|SPA|2|TWICE A DAY PARA 7 DIAS, THEN TAKE UNO CAPSULE AT |\nBEDTIME PARA 7 DIAS, THEN\nNTE|7|300993|SPA|3|TAKE UNO CAPSULE EVERY OTHER DAY PARA 7 DIAS |\n \n \n \n3. Instead of sending warning label numbers in the ZX1 segment, the \nwarning label text will be sent in the new NTE|11|segments.\n \nNote: A maximum of 5 warning labels can be printed, so only the first 5 \nfor a drug will be sent to CMOP. If the patient has a PMI Language \nPreference other than English, the first 5 warning labels in each \nlanguage will be sent.\n \nThe fields for the new warning labels are: \nNTE|11|RX NUMBER|LANGUAGE CODE|RECORD NUMBER|WARNING LABEL TEXT|\nFor the Consolidated Mail Outpatient Pharmacy (CMOP) to utilize the new \nWhere: \n RX NUMBER is the external prescription number from the \n PRESCRIPTION file (#52). \n LANGUAGE CODE will be "ENG" for English or "SPA" for Spanish. \n RECORD NUMBER is either the internal entry number from the RX \n CONSULT file (#54) or the internal entry number from the WARNING\n LABEL-ENGLISH file (#50.625) followed by an "N" when the LANGUAGE\n CODE is "ENG" or the internal entry number from the WARNING\n LABEL-SPANISH file (#50.626) followed by an "N" when the LANGUAGE\n CODE is "SPA". \n\n
\nThis patch checks for the BAD ADDRESS INDICATOR field (#.121) of the\n \nThis patch corrects the numbering of refills in the RX REFERENCE field \n(#.04) of the ACTIVITY LOG multiple (#52.3) of the PRESCRIPTION file\n(#52). A number 6 in the field should mean a partial and any refills \ngreater than the 5th refill should be stored as 1 plus the actual refill \nnumber. \n \nThis patch also removes a call to a routine that is not used (related to \nOutpatient Pharmacy V. 6.0 sending information to the CLINICAL INFO\nRESOURCE NETWORK (CIRN) package). Outpatient Pharmacy will be removed as a\nPATIENT file (#2) being set or for the patient having a foreign address\nsubscriber to Data Base Integration Agreement (DBIA) 2382.\nwhen queueing transactions to Consolidated Mail Outpatient Pharmacy\n(CMOP). If found, the fill stays on suspense for CMOP, but only prints the\nreject MailMan message the first time for the fill. The reject MailMan\nmessage is sent to holders of the PSXMAIL key and the person who queued\nthe CMOP transmission. An entry is made into the PRESCRIPTION file (#52) \nactivity log the first time the fill cannot be transmitted due to one of \nthese two conditions.\n\n
\nThe general purpose of this patch is to meet the requirements in support \nplease refer to the installation steps provided in each of the stand-alone\npatches.\n \nThe software changes distributed by this patch are exclusively for\nsupporting the Electronic Claims Management Engine (ECME) application for\nthe ePharmacy/ECME Enhancements project (BPS*1*4). There is no functional\nimpact to the Consolidated Mailout Outpatient Pharmacy (CMOP) application.\nThe change is technical in nature and is explained below:\n \n The PSXBPSRP routine was created to replace the BPSCEAR routine, which\nof the Phase 4 ePharmacy enhancements. This patch is one of five to be \n was previously used by ECME to run the CMOP/ECME Activity Report [BPS \nRPT\n CMOP/ECME ACTIVITY] option. This option will be changed to call the \n PSXBPSRP routine instead. This call is supported by the Database\n Integration Agreement #4968.\nreleased. Three patches will be released in the KIDS multi-build \ndistribution, BPS PSO IB BUNDLE 2.0, containing: BPS*1*5, IB*2*363,\nPSO*7*260. PSX*2*63 and PSS*1*127 will be released as stand-alone \npatches. The recommended order for installing the patches is to install\nthe stand-alone patch first and multi-build must be installed afterwards.\nsince there is a implementation dependency between the multi-build \ndistribution and the stand-alone patch. For more specific instructions \n\n
\nOverview of Remedy Ticket(s):\n \nThe word "beyond" is mis-spelled "beyound".\n \nProblem: HD225944\n----------------------------------------------------\nWhile using the option Scheduled Non-CS Transmission (PSXR SCHEDULED\nNON-CS TRANS) the possibility exists to receive the following error:\n<COMMAND>GETDATA+13^PSXRPPL\n \n \n-----------------------------\nResolution: HD200299\n----------------------------------------------------\nThe word "beyound" has been changed to "beyond"\n \nResolution: HD225944\n----------------------------------------------------\nThe program PSXMISC1 will be modified to return a value to the calling\nRoutine. This will allow the Scheduled Non-CS Transmission to\ncontinue without error.\n \nProblem: HD200299\nThe following is a list of the routines included in this patch. \nThe second line of each of these routines now looks like: \n----------------------------------------------------\nIf the Pharmacy Site instruction(s) exceed seven lines a warning\nmessage will be generated and sent to the CMOP Managers. This\nmail message that is sent includes the following line:\n \nLines beyond seven are not being sent to the CMOP.\n\n
\nThis patch is one of four patches that enhance ePharmacy, which provides \n 2. OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*287\n 3. ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*6\n 4. INTEGRATED BILLING (IB) V. 2.0 IB*2*383\n \nAll four patches are being released separately with a requirement that \nthey be installed in the order outlined above. There are no other \ndependencies between these patches, except that Tricare/Active Duty \nbilling will not be supported by ePharmacy until all 4 patches are \ninstalled.\n \nlimited support to Tricare and Active Duty outpatient pharmacy billing.\nThis patch modifies the Consolidated Mail Outpatient Pharmacy v2.0\napplication. \n \nFor Tricare prescriptions, CMOP background processing was modified to\nretain prescriptions in suspense when the third party claim remains in an \nECME 'IN PROGESS' status or when it is flagged as non-billable. These \nprescriptions will be listed on the existing MailMan message \nwith a subject line of 'ePharmacy - CMOP Not TRANSMITTED Rx List'.\n \nBelow is a list of all the applications involved in this project along \nwith their associated patch number:\n \n APPLICATION/VERSION PATCH\n --------------------------------------------------------------\n 1. CONSOLIDATED MAIL OUTPATIENT PHARMCY (CMOP) V. 2.0 PSX*2*66\n\n
\nThis patch has enhancements which extend the capabilities of the Veterans \n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*289\n \n \n \nComponents Sent With Patch\n--------------------------\nThe following is a list of files included in this patch:\n \n UP SEND DATA\n DATE SEC. COMES SITE RSLV\nFILE # NAME DD CODE W/FILE DATA PTS\n INTEGRATED BILLING (IB) V. 2.0 IB*2*384\n-----------------------------------------------------------------------\n \n \nThe following is a list of files deleted in this patch:\n \nFILE # NAME\n-------------------------------------\n \n \nThe following is a list of sub-files and related fields deleted in this \n ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0 BPS*1*7\npatch:\n \nSubfile Name (Number) File Name (Number)\n Field Name (Number)\n--------------------- ---------------------\n \n \nThe following is a list of fields included in this patch:\n \nField Name (Number) File Name (Number)\n \n Subfile Name (Number)\n------------------- ------------------\nCERTIFICATION IEN (902.23) BPS TRANSACTIONS (9002313.59)\n \n \nThe following is a list of fields deleted in this patch:\n \nField Name (Number) File Name (Number)\n Subfile Name (Number)\n------------------- ------------------\nThe last three patches (PSO*7*289, IB*2*384 and BPS*1*7) will be released \n \n \nThe following is a list of print templates deleted in this patch:\n \nTemplate Name File Name (Number)\n------------- ------------------\n \n \nThe following is a list of sort templates deleted in this patch:\n \nin the Kernel Installation and Distribution System (KIDS) multi-build \nTemplate Name File Name (Number)\n------------- ------------------\n \n \nThe following is a list of list templates included in this patch:\n \nTemplate Name\n-------------\n \n \ndistribution BPS PSO IB BUNDLE 3.0. Patches PSX*2*65 and PSS*1*131 will \nThe following is a list of options included in this patch:\n \nOption Name Type New/Modified\n----------- ---- ------------\n \n \nThe following is a list of protocols included in this patch:\n \nProtocol Name\n-----------\nbe released as stand-alone patches. Since there is an implementation \n \n \nThe following is a list of forms deleted in this patch:\n \nTemplate Name File Name (Number)\n------------- ------------------\n \n \n \nDocumentation Retrieval:\ndependency between the multi-build distribution and the stand-alone \n========================\nSites may retrieve documentation in one of the following ways:\n \n 1. The preferred method is to FTP the files from \n download.vista.domain.ext, which will transmit the files from the\n first available FTP server.\n \n 2. Sites may also elect to retrieve documentation directly from a \n specific server as follows:\n \npatches, PSX*2*65 and PSS*1*131 must be installed prior to the \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n 3. Documentation can also be retrieved from the VistA Documentation \n Library (VDL) on the Internet at the following address,\n http://www.domain.ext/vdl.\n \nThe documentation distribution includes:\n \nHealth Information Systems and Technology Architecture (VistA) electronic \ninstallation of the multi-build. For more specific instructions please \n FILE NAME DESCRIPTION\n \n ---------------------------------------------------------------------\n \n \n \n \nTest Sites:\n===========\n \nrefer to the installation steps provided in each of the patches.\n \n \n \n ================INSTALLATION INSTRUCTIONS =================\n \nTo avoid disruptions, these patches should be installed when users are \nnot on the system and during non-peak hours. Of particular concern would \nbe the items below.\n \n 1. Do not install the patch when ECME claims are being generated\n \n by the BPS Nightly Background Job option [BPS NIGHTLY\n BACKGROUND JOB]. Wait for this job to finish or complete the\n installation before this job starts.\n 2. Do not install the patch when prescriptions are being \n transmitted to CMOP. Wait for the CMOP transmission to finish \n or complete the installation before the transmission starts. \n Check with Pharmacy Service or your pharmacy Automated Data\n Processing Application Coordinator (ADPAC) to find out when\n CMOP transmissions occur.\n 3. In addition, note that you will be prompted to disable the\nAll sites should install these patches regardless of whether or not they \n following options during the installation:\n \n \n \n \nInstall Time - Approximately 30 minutes\n \n \n \n1. OBTAIN PATCHES\nhave been activated for ePharmacy by the Central Business Office (CBO). \n --------------\n Patches PSX*2*65 and PSS*1*131 will be sent to your system upon\n release from the National Patch Module.\n \n Obtain the host file BPS_1_7_PSO_IB.KID, which contains the following\n three patch installs:\n \n BPS*1.0*7\n PSO*7.0*289\n IB*2.0*384\nAfter the installation of these patches, the activation status of the \n \n Sites can retrieve VistA software from the following FTP addresses.\n The preferred method is to FTP the files from:\n \n download.vista.domain.ext\n \n This will transmit the files from the first available FTP server.\n Sites may also elect to retrieve software directly from a specific\n server as follows:\n \nsite will not be impacted. As before, activation of the ePharmacy \n Albany ftp.fo-albany.domain.ext\n Hines ftp.fo-hines.domain.ext\n Salt Lake City ftp.fo-slc.domain.ext\n \n The BPS_1_7_PSO_IB.KID host file is located in the anonymous.software\n directory. Use ASCII Mode when downloading the file.\n \n2. LOAD TRANSPORT GLOBAL FOR STAND-ALONE PATCHES\n ---------------------------------------------\n For patches PSX*2*65 and PSS*1*131, choose the PackMan message\nproduct will require instructions provided by the CBO. Sites are not to \n containing each of these patches and invoke the INSTALL/CHECK MESSAGE\n PackMan option.\n \n3. START UP KIDS\n -------------\n Start up the Kernel Installation and Distribution System Menu option\n [XPD MAIN]:\n \n Edits and Distribution ...\n Utilities ...\nactivate unless instructed specifically by the CBO.\n Installation ...\n \n Select Kernel Installation & Distribution System Option: INStallation\n ---\n Load a Distribution\n Print Transport Global\n Compare Transport Global to Current System\n Verify Checksums in Transport Global\n Install Package(s)\n Restart Install of Package(s)\n \n Unload a Distribution\n Backup a Transport Global\n \n Select Installation Option:\n \n4. RUN OPTIONAL INSTALLATION OPTIONS FOR STAND-ALONE PATCHES\n ---------------------------------------------------------\n From the Installation menu, you may select to use the following\n options (when prompted for the INSTALL NAME, enter each of the\n stand-alone patches (PSX*2.0*65 and PSS*1.0*131)):\npharmacy (ePharmacy) billing system. Below is a list of all the \nThis patch modifies the CMOP v2.0 application as described\n \n a. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will not\n backup any other changes such as Database Definitions (DD's) or\n templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\nbelow:\n you to ensure the integrity of the routines that are in the\n transport global.\n \n5. INSTALL STAND-ALONE PATCHES\n ---------------------------\n This is the step to start the installation of this KIDS patch. This\n will need to be run for each of the stand-alone patches (PSX*2*65 and\n PSS*1*131).\n \n a. Choose the Install Package(s) option to start the patch\n \n install.\n b. When prompted for the "Select INSTALL NAME:", enter the patch\n name.\n c. When prompted "Want KIDS to INHIBIT LOGONs during the install?\n YES//" answer NO.\n d. When prompted "Want to DISABLE Scheduled Options, Menu\n Options, and Protocols? YES//" answer NO.\n e. When prompted, "Device: Home//" respond with the correct device.\n \n6. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD\n \n -------------------------------------\n After the installation of the stand-alone patches is complete, return\n to the Installation menu.\n \n From the Installation menu, select the Load a Distribution option.\n \n When prompted for "Enter a Host File:", enter the full directory path\n where you saved the host file BPS_1_7_PSO_IB.KID (e.g.,\n SYS$SYSDEVICE:[ANONYMOUS]BPS_1_7_PSO_IB.KID).\n \n1. A modification was made to allow for CMOP Suspense Date Rx's \n When prompted for "OK to continue with Load? NO//", enter "YES."\n \n The following will display:\n \n Loading Distribution...\n \n BPS PSO IB BUNDLE 3.0\n BPS*1.0*7\n PSO*7.0*289\n IB*2.0*384\npicked up after midnight to be sent to ECME appropriately. When the CMOP \n Use INSTALL NAME: BPS PSO IB BUNDLE 3.0 to install this\n Distribution.\n \n7. RUN OPTIONAL INSTALLATION OPTIONS FOR MULTI-BUILD\n -------------------------------------------------\n From the Installation menu, you may select to use the following\n options (when prompted for the INSTALL NAME, enter\n BPS PSO IB BUNDLE 3.0):\n \n a. Backup a Transport Global - This option will create a backup\ntransmission starts, all Rx's in the suspense file are evaluated to see \n message of any routines exported with this patch. It will not\n backup any other changes such as DD's or templates.\n b. Compare Transport Global to Current System - This option will\n allow you to view all changes that will be made when this patch\n is installed. It compares all components of this patch\n (routines, DD's, templates, etc.).\n c. Verify Checksums in Transport Global - This option will allow\n you to ensure the integrity of the routines that are in the\n transport global.\n \nif they should be submitted to ECME first and if so are submitted. Then \n8. INSTALL MULTI-BUILD\n -------------------\n This is the step to start the installation of this KIDS patch. This\n will need to be run for the BPS PSO IB BUNDLE 3.0.\n \n a. Choose the Install Package(s) option to start the patch\n install.\n b. When prompted for the "Select INSTALL NAME:", enter BPS PSO IB\n BUNDLE 3.0.\n c. For the BPS*1*7 patch, when prompted "Want KIDS to Rebuild Menu\nthe system re-evaluates the suspense file to pull the latest list of Rx's \n Trees Upon Completion of Install? YES//" enter YES unless your\n system does this in a nightly TaskMan process.\n d. For the PSO*7*289 patch, when prompted "Want KIDS to Rebuild Menu\n Trees Upon Completion of Install? YES//" enter YES unless your\n system does this in a nightly TaskMan process.\n e. When prompted "Want KIDS to INHIBIT LOGONs during the\n install? YES//" enter NO.\n f. When prompted "Want to DISABLE Scheduled Options, Menu Options,\n and Protocols? YES//" enter YES.\n g. When prompted "Enter options you wish to mark as 'Out Of\nto send to CMOP using the current date and time. When the CMOP evaluation \n Order':" enter the following options:\n \n h. When prompted "Enter protocols you wish to mark as 'Out Of\n Order':" enter <return>.\n i. When prompted "Delay Install (Minutes): (0-60): 0//" enter an\n appropriate number of minutes to delay the installation in \n order to give users enough time to exit the disabled options\n before the installation starts.\n j. When prompted "Device: Home//" respond with the correct device.\n \napplications involved in this project along with their patch number:\nruns past midnight, any Rx's with the suspense dates changed to that day \n \n \nThe BPS post-install routine delivered with BPS*1*7 will do the tasks\nlisted below. This post-install will be tasked and may take several\nhours to run. The post-install routine BPS01P7 is being left on the \nsystem after the install. They will be deleted with a future patch.\nare sent to CMOP. However, since the ECME submission ran before midnight, \nthose Rx's would not have been sent. This modification will re-check the \nRx's in suspense for the new date after the CMOP transmission completes \nin order to pick up Rx's that need to be sent to ECME after midnight.\n \n2. New functionality was added to prevent prescriptions from being \nfilled/sent to CMOP when a host processing error occurs when a claim is \nsubmitted through ECME. The host processing errors are identified by \nreject codes M6, M8, NN, and 99. The following conditions apply when this \n \nscenario occurs.\na. The transmission of the Rx/fill will be delayed 1 day in hopes \nthat the host processing issues will be resolved.\nb. An activity log entry will be defined to state the date/time \nalong with a comment stating that the Rx/fill was left in suspense hold \ndue to a host processing error.\nc. This added functionality does not include the Pull Early from \nSuspense function.\n \n3. New functionality was added to the Print from Suspense File [PSO \n APPLICATION/VERSION PATCH\nPNDLBL] option to prevent prescriptions from being pulled early from \nsuspense until 3/4 of the days supply of the Rx/fill has elapsed.\n \n4. The 'CMOP/ECME Activity Report' [BPS RPT CMOP/ECME ACTIVITY] has \nbeen modified. \na. The CMOP-STATUS column will display 'D' for Dispense or 'T' for \nTransmit instead of partially spelling out the status.\nb. A prompt will be added to select detailed or summary \ninformation. Detailed information will reflect what is currently \ndisplayed. Summary information will shorten the batch header section of \n --------------------------------------------------------------\nthe report.\nc. A prompt will be added to select a list of patients (or ^ALL). \nOnly patients on the list will be included in the detail.\nd. The division prompt will be modified to be consistent with other \nECME options, i.e., the selection prompt will show 'A ALL DIVISIONS' \nfirst, 'S SELECT DIVISIONS' second, and will roll into particular \ndivisions if the user selects an 'S'.\ne. A prompt will be added to select released, unreleased, or all \nprescriptions.\nf. Detailed reports will only display information from batches that \n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0 PSX*2*65\nhave ECME Rxs.\ng. Header information will be centered. \n5.\n \n \n \n \nThis patch addresses the following New Service Request (NSR):\n-------------------------------------------------------------\nThere is no NSR associated with this patch.\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*131\n \n \nThis patch addresses the following Remedy Ticket(s):\n----------------------------------------------------\nThere is no Remedy Tickets associated with this patch.\n \n \n \nOverview of Remedy Ticket(s):\n-----------------------------\n\n
\nThis patch is part of the FY09-Q3 Enhancement release and must be\nRecord System V. 1.0 (CPRS) or Registration V. 5.3 packages, then an\nemail notifying that a prescription was just discontinued for that Rx\nwill be sent to the new PSX EXTERNAL DISPENSE ALERTS mail group. If no\nrecipients are defined in the new mail group, then the email alert will be\nsent to PSXCMOPMGR key holders. The email alert will inform the group that\nthe CMOP status for the Rx just discontinued was either Transmitted or\nRetransmitted as seen in the example below.\n \n Subj: TROY - DC Alert on CMOP Rx 123456789 TRANSMITTED [#90494]\n 03/03/09@17:37 8 lines\ninstalled along with Outpatient Pharmacy V. 7.0 patch PSO*7*324, which\n From: POSTMASTER In 'IN' basket. Page 1 *New*\n ------------------------------------------------------------------------\n Rx #: 123456789 Fill: 0\n Patient: OUTPATIENT,DCONE (6660)\n Drug: TAMOXIFEN CITRATE 10MG TABS\n Rx Status: DISCONTINUED BY PROVIDER\n Processing Status: TRANSMITTED to CMOP on 02/27/09\n Provider: OPPROVIDER, PROV\n \n ******** Please contact CMOP or take appropriate action ********\naddresses PSI-07-181 (PSPO# 865) - Remedy Ticket # HD208961. A new mail\n \n Enter message action (in IN basket): Ignore//\n ------------------------------------------------------------------------\ngroup named PSX EXTERNAL DISPENSE ALERTS is created in this patch to\nsupport the functionality provided by patch PSO*7*324.\n \nWhen a Consolidated Mail Outpatient Pharmacy (CMOP) prescription with a\nstatus of Transmitted or Retransmitted is discontinued by a background\njob other than Outpatient Pharmacy options, e.g. Computerized Patient\n\n
\nSee the patch description for PSX*2.0*10.\n\n
\nThis patch modifies the CMOP v2.0 application as described below:\nwhere the software did not resubmit an electronic pharmacy claim\nautomatically when a claim rejected for a host processing error. The\nfollowing day the prescription was transmitted to CMOP as anticipated and\nwas filled. The claim did appear on the ECME User Screen so it could be\nmanually resubmitted, which is the process facilities followed before this\npatch was installed. Based upon analysis, this is an infrequent scenario\n(less than 1%) and will only occur in a particular set of circumstances.\n \nHost processing errors are identified by reject codes M6, M8, NN, and 99.\nThe following conditions apply when this scenario occurs.\n \n \n a. The transmission of the Rx/fill will be delayed 1 day in hopes\n that the host processing issues will be resolved.\n b. An activity log entry will be defined to state the date/time along\n with a comment stating that the Rx/fill was left in suspense hold \n due to a host processing error.\n c. This added functionality does not include the Pull Early from\n Suspense function.\n \nThis issue has been corrected in this patch.\n1. An entry was being added to the ECME LOG every time an Rx is evaluated\n \n3. The system was allowing rejected Tricare prescriptions to be sent to \nCMOP. Tricare rejected prescriptions should be held in suspense until \nthe reject has been resolved. This patch corrects this issue. \nfor ECME claim submissions and the Rx was flagged for Bad Address. A\nmodification was made to only allow the Rx to be evaluated for ECME claim\nsubmission if a Bad Address indicator is not present. \n \n2. There is a known issue where the system may not automatically resubmit\nall claims rejected due to a host processing error. A test facility found\n\n
\nCurrently in backdoor Pharmacy, all warning labels are printed.\nLevel Seven (HL7) messages in segment NTE|11|, with a limit of 220\ncharacters. This patch creates a continuation segment in NTE|11A| to\ncontain the warning text that is greater than the initial 220 characters,\nup to an additional 220 characters. The continuation segment immediately\nfollows the NTE|11| segment of the warning. This means all warning labels\nwill be transmitted to CMOP.\nHowever, when Prescription Warning labels are transmitted to the\nConsolidated Mail Outpatient Pharmacy (CMOP), there is a limit of 5\nwarnings per prescription. CMOP has requested that all warning labels be\nsent with every prescription. This patch therefore allows more than five\nwarnings per prescription to be transmitted to CMOP, and also allows\nwarning text that is greater than 220 characters per warning.\n \nPrescription Warning labels are currently transmitted to CMOP via Health\n\n
\nePharmacy Phase 6\n\n
\nThis patch contains software modifications to the Consolidated Mail \n . Certain information is necessary to prevent serious adverse effects \n . Patient decision-making should be advised by information about a known\n serious side effect with a product, or \n . Patient adherence to directions for the use of a product is essential\n to its effectiveness. \n \nThe features in the FDA Medication Guides project are being delivered in\nincremental releases. This patch is part of the Increment 3 release, which\nis the last planned release. The features included in this release are:\n \nOutpatient Pharmacy (CMOP) V. 2.0 application to support the Food and Drug\n . Ability to create and maintain a list of FDA Medication Guide printers\n for a specific pharmacy division.\n \n . Automatic printing of FDA Medication Guide along with prescription \n labels.\n \n . Ability to reprint the FDA Medication Guide when reprinting a \n prescription label.\n \n . Ability to change the FDA Medication Guide printer at any point in the\nAdministration (FDA) Medication Guides - Increment 3 project. The project\n dispensing process, similar to changing the label printer.\n \n . Ability to reprint the FDA Medication Guide for any given prescription\n fill or the latest FDA Mediation Guide available for the medication on\n the prescription.\n \n . Identification on the label document that an FDA Medication Guide was\n printed as well and needs to be collated to the documentation before\n being handed over to the patient.\n \nobjective is to allow pharmacy staff to retrieve the FDA Medication Guide\n . Changes to the prescription label activity logs showing which specific\n FDA Medication Guide document printed along with the label.\n \n . Changes to the Consolidated Mail Outpatient Pharmacy (CMOP) Event log\n showing which specific FDA Medication Guide document was available \n for the medication when the prescription fill was transmitted to CMOP.\n \n . Introduction of a PC based Java software component to enable the\n automatic printing of an FDA Medication Guide from within VistA. The\n software does not require any direct user interaction. The software \nfor prescription items that contain FDA approved information that can help\n identifies a request from VistA for a specific FDA Medication Guide\n and automatically sends it to the FDA Medication Guide printer\n selected by the user within VistA when dispensing the medication.\n \n . Ability to update the Windows network printer name for a specific\n device through the Kernel application. Once the pharmacist selects a\n printer to print the FDA Medication Guide Vista will retrieve the \n Windows name for the printer and will pass it on to the Java\n application responsible for printing the document.\n \npatients avoid adverse events. The FDA requires that Medication Guides be\nBelow is a list of all the applications involved in this release along\nwith their patch number:\n \n APPLICATION/VERSION PATCH\n -----------------------------------------------------------------\n CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 4.0 PSX*2*70\n NATIONAL DRUG FILE (NDF) V. 4.0 PSN*4*264\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*367\n KERNEL V. 8.0 XU*8*566\n \nincluded with certain prescribed drugs and biological products when the\nThe following modification is included in this patch (PSX*2*70):\n \nThe process responsible for the transmission of prescriptions from Outpatient\nPharmacy to CMOP will be modified to record the current FDA Medication Guide\ndocument name in the CMOP Event Log in the PRESCRIPTION file (#52) if one \nexists for the medication in the prescription being transmitted. Such \ninformation will be displayed within Outpatient Pharmacy application when the\nuser selects to view the CMOP Event Log for a specific prescription.\n \nAgency determines that:\n \n\n
\nEPHARMACY OPERATING RULES\n\n
\nThis patch modifies the Consolidate Mail Outpatient Pharmacy (CMOP) v2.0 \napplication as described below:\n \n 1. A correction was made to not have duplicate Notes and Comments \n(NTE)5 segments after a CMOP Re-Transmit option was performed\n 2. A typo was corrected in the key description for PSXMAIL key\n 3. A correction was made to not allow CMOP Controlled substance \nto be released from suspense early.\n\n
\nThis patch modifies the Consolidate Mail Outpatient Pharmacy (CMOP) v2.0 \nEnter/Edit (PSS Drug Enter/Edit) option.\n 4. A correction made to not duplicate Patient Address error\nmessage in Mailman messages\napplication as described below:\n \n 1. A correction was made to make sure Bad Address Indicator(BAI) \nis for error messages in mailman, when the BAI is set\n 2. A correction was made to the Data Dictionary for the input \ntransform and the description of The CMOP System file (550), fields were \nNon-CS Days to Transmit (#11) and CS Days to Transmit (#12).\n 3. A correction was mad to the CMOP User Manual to update the Drug\n\n
\nHAPE EDI Revenue project - NCPDP Continuous Maintenance Standards\n\n
\nThis patch modifies the Consolidate Mail Outpatient Pharmacy (CMOP) v2.0 \napplication as described below:\n \n 1. A correction was made to have Controlled Substance Special \n Handle level 3 to be change to level 2 or 1 and put into \n Local suspense\n\n
\nThis patch modifies the Consolidate Mail Outpatient Pharmacy (CMOP) v2.0 \napplication as described below:\n \n 1. PSXR BATCH INQUIRY [View Transmission] Option was getting hung\nup when being run.\n\n
\nThis patch is being distributed in response to NOIS CMM-0997-N0446.\n\n
\nMCCF ePharmacy Compliance Phase 3\n\n
\nMCCF EDI TAS EPHARMACY BUILD 2\n\n
\nThis patch changes the upper limit of the NON-CS DAYS TO TRANSMIT Field\nThe CS DAYS TO TRANSMIT Field (#12) is the suggested maximum number of \ndays to use as a print through date for the CMOP auto-transmission for\ncontrolled substances. It can be overwritten in the auto-transmission\nset-up, to a maximum of 15.\n \n \n****NOTE****\nThe change to the CMOP SYSTEM File (#550), NON-CS DAYS TO TRANSMIT Field \n(#11) and CS DAYS TO TRANSMIT Field (#12) may lead to additional NCPDP \nReject 79 Refill Too Soon (RTS) claims.\n(#11) and the CS DAYS TO TRANSMIT Field (#12) of the CMOP SYSTEM File\n \nIf the claim submission returns a Refill Too Soon (79) reject, the label \nis NOT printed for the prescription and it is moved to the Refill Too \nSoon/DUR section of the patient Medication Profile screen until the user \nresolves the reject. The prescription will also display on the Third-Party\nPayer Reject Worklist. If the claim submission returns a Reject Resolution\nRequired reject, the label is NOT printed for the prescription and it is\nmoved to the Reject Resolution Required section of the Third-Party Payer\nReject - Worklist.\n \n(#550) from 10 to 15 days.\nPlease search for additional guidance on the eRevenue Resources main \nlanding page for Refill Too Soon. Guidance documents for COVID-19 Refill \nToo Soon Override. The landing page may be accessed at: \nhttps://vaww.vashare.domain.ext/sites/eRevenueResources/Pages/HomePage.asp\nx\n \nThe NON-CS DAYS TO TRANSMIT Field (#11) is the suggested maximum number of\ndays to use as a print through date for the CMOP auto-transmission for\nnon-controlled substances. It can be overwritten in the auto-transmission\nset-up, to a maximum of 15.\n \n\n
\nIt has been reported that when a controlled substance CMOP order is \ntransmitted via option Print from Suspense file and then a subsequent \nnon-controlled substance CMOP order is requested to be transmitted via \nthe same option, the controlled substance order is transmitted instead of \nthe non-controlled substance order.\n\n
\nThis patch will resolve the following issue:\n--------\nThe Castle Point VA Medical Center reported that its PSX Resource device was\nhung for hours in and they had to manually released and the process that was\nholding the device had to be terminated. The Clin1 researched the problem\nand determined that the sequence that caused the problem was this:\n \n 1. The CMOP prescription release information arrives at the site in the\n form of a Mailman message that contains all prescriptions released by\n CMOP. This message is sent to the S.PSXX CMOP SERVER recipient.\n \n \n 2. Each line of the Mailman message is processed to reflect the release\n event (e.g., Release date and CMOP information like Lot# is recorded,\n 3rd party billing is updated, etc.)\n \n 3. An existing 3rd party billing claim will be reversed and resubmitted if\n the NDC from CMOP does not match the original sent to the 3rd party\n payer when the prescription was transmitted to CMOP. \n \n 4. Some of these updates will cause ePharmacy (BPS) to call out to the\n Integrated Billing (IB) application to cancel a Bill.\n1) INC18186175 - NFL Stuck PSX resource\n \n 5. Depending on the update that the IB application performs it may\n automatically create and send a Mailman message to its users.\n \n 6. The creation of the Mailman message by IB is interfering with the\n processing of the Mailman message sent from CMOP to the site. More \n specifically, it changes the value of the variable XMZ that is used as\n an index in the step #2 above to indicate which line is being processed.\n \n 7. This caused the processing of the CMOP message to go into an infinite\n \n loop and cause the problem reported by the site. \n \nResolution:\n----------\nA change was made to the processing of the CMOP Mailman message to protect\nthe variable XMZ from being overwritten when other functionalities or\napplications are called.\n \nTechnical Resolution:\n--------------------\nDefect Tracking System Ticket(s) & Overview:\nThe FOR loop in the EN+3 line of the PSXVND routine was re-written to address\ntwo problems:\n \n 1. Protect the variable XMZ from being overwritten \n \n 2. Removed GOTO commands from inside the FOR loop and placed them outside\n without changing the original logic\n--------------------------------------------\n1) INC18186175 - NFL Stuck PSX resource\n \nProblem: \n\n
\nSee the patch description for PSX*2.0*13.\n\n
\nSee FORUM patch description.\n\n
\nSee FORUM patch description.\n\n
\nSee the patch description for PSX*2.0*11.\n\n
\nCMOP V 2.0T9 ALPHA BUILD FOR MEDICAL CENTERS\n\n
\nMODIFICATION TO - GREEN SHEET READY FOR PICKUP LOG\n\n
\nPROBLEM WITH RELEASE FUNCTION #2.\n\n
\nThis is an enhancement patch to check prescription status before\nposting/releasing for sites running Controlled Substances Version 3.0\nand Outpatient Pharmacy Version 7.0.\n\n
\nUser received an $ZE= <UNDEFINED>LOOP+16^PSDFIL2\n\n
\n This patch corrects an undefined error in routine PSDFIL2. The problem\n was originally addressed in patch PSD*3*13. However, this patch created\n another problem, and has since been marked as entered in error.\n\n
\n \nNOIS call PTH-0897-21047; OKL-0998-71256; NCH-1197-41081\n\n
\nThe option Outpatient Rx's [PSD OUTPATIENT] has been enhanced to alert the\npharmacist that a prescription has been canceled and prompts to determine\nwhether the medication should be released and controlled substances\nbalances updated.\n\n
\n Due to the placement of locks on globals when updating balances, the \n time frame between the initial balance changes and the actual\n locking of the global can result in other users accessing similar \n options that also change the balances. The result is erroneous data\n being stored in the drugs balance.\n \n Resolution: The locks on several options have been moved up to the point\n where the drug is first selected. This will ensure no other balance\n adjustments will be made to that drug until the user is finished with it.\n\n
\n When the Controlled Subs AMIS report is executed, if a drug is found\n that has a cost of zero, a message prints showing the drug's cost was\n zero. The report does not specify which transaction or date. The\n report is being re-worked for more detail.\n\n
\n Cannot send reports to the terminal screen.\n\n
\n The release of DI*22*2 causes checks for $T after a DIC call to be \n invalid.\n\n
\nRoutine modified to interface with Drug Accountability/Inventory\nInterface (DA) Version 3 to be released in 1997.\n\n
\nProblem\n=======\nThe terminology for the description of a priority order is not consistent.\nThe orders are described as "emergency", "unscheduled" or "priority".\n \nSolution\n========\nThe consensus is to use "priority" for the description of these orders.\nThe use of "emergency" and "unscheduled" will be replaced by "priority".\n\n
\nThis patch is part of the CMOP - Controlled Substance Rxs enhancements.\nThe Installation Guide for the CMOP - Controlled Substance Rxs project can\nbe obtained on the VISTA Consolidated Mail Outpatient Pharmacy web page. \nThe address is http://vista2.domain.ext/cmop/.\n \nThe Installation Guide is also available on the ANONYMOUS.SOFTWARE\ndirectory at one of the following Office of Information (OI) Field\nOffices.\nThe file name is CMOPCS_IG.PDF.\n \nOI FIELD OFFICE FTP ADDRESS DIRECTORY\nIt modifies functions within he Controlled Substances application\n=============== =========== =========\nAlbany 152.127.1.5 anonymous.software\nHines 152.129.1.110 anonymous.software\nSalt Lake City 152.131.2.1 anonymous.software\n \nControlled Substance Modifications in Support of CMOP-Controlled Substance\nRxs: The Outpatient Rx's option [PSD OUTPATIENT] was modified to prevent\nthe releasing of a controlled substance if the CMOP status is transmitted,\ndispensed or retransmitted. Controlled substance prescriptions with the\nstatus of 'Not dispensed' shall be releasable.\nto support the transmission of controlled substance prescriptions to the\nConsolidated Mail Outpatient Pharmacy facilities.\n \nThis patch will be installed in conjunction with three other patches\n(PSX*2*23, PSO*7*33, and PSS*1*28). Refer to the CMOP - Controlled\nSubstance Rxs Installation Guide for installation instructions.\n \n\n
\n There are two problems with the Inspector's Log by Rec'd Date [PSD INSP\n LOG BY RECD DATE] option.\n \n The problems stem from the DRUG ACCOUNTABILITY STATS file (#58.8) ORDER \n STATUS (#10) field. This field's cross reference is used as a basis for\n the report.\n\n
\n When a drug was signed out for a patient from an incorrect ward, returned\n to that ward, and then signed out for the correct ward, problems occur in\n the Record Defective Dose [PSD NURSE DEFECTIVE DOSE], Delayed Sign Out\n Dose for Patient [PSD NURSE DELAYED DISPENSE], Sign Out Dose for Patient\n [PSD NURSE DISPENSING], Not Given, Return to Stock [PSD NURSE NOT GIVEN],\n Record Delayed Wastage, [PSD NURSE WASTE] options.\n\n
\n When the Daily Activity Log (in lieu of VA FORM 10-2320) [PSD DAILY LOG]\n option is executed, an undefined variable error occurs.\n\n
\n When the Rx (Prescription) Outpatient Dispensing Report [PSD RX \n DISPENSING REPORT] option is generated, data is being excluded for\n some transactions because there is more than one entry with the\n exact date and time. The reports initial search base is one the date\n and time, therefore only the first record will be checked.\n \n The solution is to expand the loop to check other factors such as the\n pharmacy location or drug.\n\n
\n When the inspector's log is printed, items marked as perpetual inventory\n error is that the entry in the DRUG ACCOUNTABILITY TRANSACTION (#58.81)\n file will be upgraded to the selected order and completion statuses, the\n entry in the DRUG ACCOUNTABILITY ORDERS (#58.8) will remain as it was. \n are excluded from the report. This patch will allow items marked as\n perpetual inventory to be included on the report if the order status is\n also marked as "DELIVERED - ACTIVELY ON NAOU".\n \n Another problem corrected by this patch is with the process of marking\n a green sheet completed. If the user selects the completion status "OTHER \n - REFERRED TO PHARMACY SUPERVISOR", and enters an up-arrow ('^') at the\n prompt for entering a referred reason the system creates an error. The\n\n\nProblem:\ndevelopers. This API will be called by Outpatient Pharmacy each time a \nrefill is returned to stock. The API will decide whether the RX is a\ncontrolled substance and store this information in order to inform users\nof the Controlled Substances package of the status of an Rx refill.\nOutpatient Pharmacy patch PSO*7*40 contains the API.\n \nProblem:\n=======\nIn some instances, two different personnel can release a CS script within\nmoments of each other. This cause confusion and errors in the drug's\n=======\nbalance.\n \nSolution:\n========\nWhen a user selects a prescription, the global is instantly locked. Anyone\nelse trying to alter data in that prescription will be shown a message that\ninforms them that another user is editing that prescription.\nIn Outpatient Pharmacy when Rx refills are returned to stock the refill\nis deleted. This deletion is not reflected in Controlled Substances \nand thus reports and Rx balances are not reflecting these changes.\n \nSolution:\n========\nAn API for Outpatient Pharmacy will be developed by Controlled Substances \n\n
\nThere is a problem in the Sign Out Dose for Patient [PSD NURSE DISPENSING] \nThis error message restricts the user from returning a drug to one\nNAOU if it has been signed out by another. This also creates a problem\nby updating the balance in both wards.\n \nThe solution to this is to remove the checking on every ward, and just \nconcentrate on the one at hand. \noption.\n \nThe problem is in the part where the system displays the doses signed out\nin the last 'X' hours. Although the user is signing out the dose for a \nparticular ward, the program loops through each ward on file looking for \nthe drug. It will show all the doses signed out. When it finds an entry \nthat doesn't match the selected ward, an error message is generated. \n \n\n
\n1) When using the Hold a CS Drug (No Inventory Update) [PSD DEST NON-CS\n adjustments. This patch insures all adjustments are included in the\n report.\n DRUG] option, it was reported that the system is erroring out after \n the user enters a semicolon ";" as part of the text for the COMMENTS\n field (#14) in the CS DESTRUCTION file (#58.86). This patch fixes \n this problem.\n \n2) On the Balance Adjustment Report [PSD BALANCE ADJUSTMENT REVIEW]\n option, if more than one adjustment to the inventory were taking place\n at the same moment, currently the report does not include all such\n\n
\nWhen drugs are returned to pharmacy, the drug inventory balance will\ndecrement automatically for the NAOU/Ward.\n\n
\n When the Add Existing Green Sheets at Setup [PSD EXISTING GS] option\n is executed, the user is not asked to identify if the 10-2638 form has\n been printed. This flag is identified by the following field:\n \n FILE: DRUG ACCOUNTABILITY TRANSACTION (#58.81)\n FIELD: PRINTED 2638 (#103)\n \n To correct the problem, the field has been added to the questions which\n the user is required to answer.\n\n
\nThis patch addresses the problems with updating balances and releasing\n for that drug item.\n \n2. If a controlled substances prescription fill has been released and\n posted (balance adjusted), the Controlled Substances V. 3.0 package \n will not allow any further actions to be taken on that fill. \n In other words, a user will only be able to post (balance adjust) \n a specific controlled substances fill only once.\n \n3. When returning to stock a controlled substances prescription fill\n through the Outpatient Pharmacy V. 7.0 software, the software will\ncontrolled substances outpatient prescriptions.\n first check to see if the user holds the PSDMGR key. If yes, the user\n will be able to return the controlled substances prescription fill\n to stock and also to update the drug balance in the Controlled \n Substances V. 3.0 package. If no, the user will NOT be able to return \n the controlled substances prescription fill to stock OR update the \n drug balance in the CS package. An electronic signature will be \n required to return a controlled substances prescription to stock and \n to update the drug balance. \n \n The user will now be able to post and/or release a partial fill for a \n \n Consolidated Mail Outpatient Pharmacy prescription.\n \n4. Users will now be able to post and/or release controlled substances\n prescriptions with a status of DISCONTINUED from the Controlled \n Substances V. 3.0 package.Posting and/or releasing through the \n Controlled Substances V. 3.0 package for prescriptions with\n the statuses of DELETED, DISCONTINUED BY PROVIDER and DISCONTINUED \n (EDIT) will not be allowed.\n \n5. If a prescription fill has been returned to stock, and later processed \n The functionality format is as follows:\n again for dispensing, the user will be able to post and/or release the \n prescription fill through the Controlled Substances V. 3.0 package as \n long as the new fill date is greater than the return to stock date.\n \n6. The Daily Activity Log (in lieu of VA FORM 10-2320) [PSD DAILY LOG] \n option has been enhanced to clearly identify prescriptions that have \n been returned to stock. \n \n7. When an item is received into the Controlled Substances V. 3.0 package \n after already being received by procurement/supply, the system does \n \n not check to see if the incoming item is stocked in the pharmacy \n location. This creates problems with the correct items because a \n balance adjustment cannot be performed on the non-stocked item. \n The solution to this is to check to ensure the item is stocked in the \n selected pharmacy location.\n \n8. When using the Outpatient Rx's [PSD OUTPATIENT] option, it was reported\n that the system errors out with an illegal number when the user enters\n an entry such as "501-400E097" at the "Enter/Wand PRESCRIPTION\n number" prompt. This patch corrects this problem.\n1. If a controlled substances prescription fill has been released, but the\n \n9. It was reported that the Suremed machine is displaying the Internal\n Entry Number (IEN) of the patient instead of the Social Security Number\n (SSN). Currently, the third piece of the PID segment of the HL7 message\n is set to the IEN. This patch ensures that the patient's SSN is sent in\n the third piece of the PID segment of the HL7 message.\n balance NOT adjusted for that specific fill (fill not posted) in the \n Controlled Substances (CS) V. 3.0 package, the user will be able to\n post that prescription fill to adjust the controlled substances balance\n\n
\n This patch removes an erroneous message that is generated in the \n Controlled Substances package. The message does not contain any\n useful information for the user, therefore it has been removed.\n\n
\nThe Office of the Medical Inspector, in collaboration with the Narcotics \n \nThis patch includes a new standalone menu option entitled CS Monitoring\nMenu [PSD NM MENU] option that will not be attached to a menu. IRM\nsupport personnel will need to assign the menu to the Narcotics Inspectors\nand Pharmacy Managers at the site. \n \nKernel's Option Access by user [XUOPTWHO] option will be attached to the CS\nMonitoring Menu [PSD NM MENU] option upon patch installation. The\nfollowing new options are brought in with the menu: \n \nDiversion Advisory Group, requested development of tools to support and\n CS Application Security Key Report [PSD NM SECURITY KEY] option\n CS Balance Adjustments Report [PSD NM CS ADJ] option\n CS RXs by Same Person Report [PSD NM RX SAME PERSON] option\n Label Reprint for CS RXs Report [PSD NM RX REPRINT] option\n Partial Request for CS RXs Report [PSD NM RX PARTIAL] option\n Patients Without VA Visit Report [PSD NM RX WITHOUT VA] option\n \nmonitor Pharmacy Service Schedule II narcotics inventory management to be\ndistributed to all medical centers. This enhancement includes a new\nstandalone CS Monitoring Menu [PSD NM MENU] option containing reports\nderived from VA FileMan templates used during site visits that were found\nto be valuable in assisting sites with the monitoring of Schedule II\nnarcotics prescriptions. These reports also allow for the monitoring of\ncontrolled substance schedules C-II through C-V. \n\n
\nPharmacy Benefits Management (PBM) Strategic Healthcare Group in\nComputerized Patient Record System (CPRS) V. 1.0\nPharmacy Data Management (PDM) V. 1.0\nOutpatient Pharmacy (OP) V. 7.0\nControlled Substances (CS) V. 3.0\n \nThis is the CS patch, which provides two new options entitled Digitally\nSigned CS Orders Report [PSD DIGITALLY SIGNED ORDERS] and Digitally Signed\nOP Released Rx Report [PSD DIG. SIGNED RELEASED RX] that will be added to\nthe Production Reports [PSD PRODUCTION REPORTS] menu. Once DEA's\nregulations are revised and PKI can be fully implemented nationally, sites\ncollaboration with the Drug Enforcement Administration (DEA), requested\nthat choose to activate the PKI functionality can use this option to\nretrieve digitally signed orders for controlled substances.\nthe development of the first Public Key Infrastructure (PKI) VistA pilot\nproject, named Electronic Prescription Order Entry for Schedule II\nControlled Substances. The objective is to develop an electronic order\nentry system for Schedule II controlled substances using digital\nsignatures. To make this project viable, modifications to the following\npackages were identified:\nNational Drug File (NDF) V. 4.0\n\n
\n When the user uses the Return Medication to Stock [PSO RETURNED STOCK]\n (#52), therefore it can be selected again, and the balances updated in\n Controlled Substances 3.0 again.\n \n The solution for this is for an additional check on the transaction before\n allowing updating of balances in Controlled Substances 3.0.\n \n 2. The second issue related to this process is that when the Controlled\n Substances 3.0 software is updating the balances, the name of the \n dispensing site is retained. If the user then exits the Outpatient \n Pharmacy 7.0 software, and accesses the Controlled Substances 3.0\n option to return a controlled substance to stock, the Controlled \n software, the user is not prompted for the name of the dispensing site.\n \n The solution for this is to not retain the name of the dispensing\n site.\n \n 3. The third issue of this patch is on fills returned to stock, then\n re-issued. Controlled Substances 3.0 will not allow the release of \n the new fill.\n \n The solution for this is to add additional checks on the prescription\n Substances 3.0 package is accessed to update the drug balance. During\n to ensure it is not the fill that was previously returned to stock.\n this process, the problems detailed below can occur.\n \n 1. After updating the balances in Controlled Substances 3.0, the \n Outpatient Pharmacy 7.0 software requires the user to enter comments\n concerning the transaction. If the user exits the program at this point,\n the item is not marked as returned to stock in the Prescription file\n\n
\nThis patch will correct problems in NOIS(s) ISB-0903-31237 and \nPOR-0503-51185.\n\n
\nMODIFICATION OF 'DR' STRING IN ROUTINE PSDSTK FOR LIQUID USEAGE.\n\n
\nRETURN ORIGINAL FUNCTIONALITY OF PSD STOCK C/S DRUGS OPTION\n\n
\nDrug Receipt History reporting issue, Green Sheet Printing issues\n\n
\nThis build contains modifications to the routines PSDAPU and PSDIPOST.\nPharmacy Data Management (PDM) V. 1.0 will provide the routine ^PSSGIU for\nflagging drugs. This function was previously done using an Inpatient\nMedications routine ^PSGIU. \n \nThis patch (PSD*3*2) is designed to work with or without installation of\nPharmacy Data Management V. 1.0.\n\n
\nMult Posting of Partials, Changes in two routines to reflect the usage of \nDBIA 2621\n\n
\nThis patch will correct the problem of the same person being\nentered as the witness and the nurse that signed out the dose.\n\n
\n When the Balance Adjustment Report [PSD BALANCE ADJUSTMENT REVIEW] is\n sent to a printer and not queued, the report prints to the user's\n screen instead.\n \n\n
\nThis patch will correct the problem of the Outpatient Dispensing Report \nnot printing to a printer.\n\n
\nThis patch will correct the problems identified in NOIS calls\n SBY-0904-30620 ERROR - MSG+1^PSDORD4\n PRE-1004-60136 PROBLEM SCANNING DRUG FOR SIGN OUT FOR PT\n\n
\nThis patch will correct the problem of the Controlled\nSubstance Nurse Shift Log not being consistant with \nthe Controlled Substance Inspectors Log.\n\n
\nThis patch will correct to problem of allowing users to select an\ninactive NAOU if the user does not hold the PSJ RNURSE key.\n\n
\nThis patch will correct to problems that are encountered\nwhen a controlled substance is returned and then reissued.\n\n
\nThis patch will modify the Controlled Substance Balances report created \nwith menu option Verify Count [PSD NURSE ONLINE COUNT]. This report \nerrors out if all the drugs in the NAOU have a balance of zero. This \npatch will also modify menu options Record Delayed Wastage [PSD NURSE\nWASTE] and Not Given, Return to Stock [PSD NURSE NOT GIVEN]. These two\noptions are calling code in each other's routines which is creating an\ninfinite loop.\n\n
\nDRUG BALANCE NOT UPDATED ON NAOU\n\n
\nThis patch corrects a problem when using the Not Given, Return to Stock\noption [PSD NURSE NOT GIVEN]. The software was not working consistently\nwhen an attempt was made to return a drug to a different NAOU from the one\nit was dispensed from. The current design of the software should not\nallow a return to a different NAOU. \n\n
\nThis patch will correct the problem of an old greensheet being\nselected when a drug IEN is entered and it matches an old \npharmacy dispencing number.\n\n
\nModifies PSD COST REPORTS, PSD NAOU BALANCE REPORT and PSD NURSE TRANSFER \nGS.\n\n
\nThis patch will correct two problems. The first problem deals with\nsome PSD variables lingering after exiting the application \nresulting in the wrong selection of the master or satellite vault.\nThe second problem is a result of two users being able to process\nthe same controlled substance request at the same time.\n\n
\nWith the deployment of Cache version 5, it was discovered that the short\nmodifies all routines that currently use a lock timeout value of less than\n3 seconds to check for the node ^DD("DILOCKTM") and to use the value\ndefined there, otherwise the lock timeout value is set to a default value\nof 3 seconds.\nlock timeout values could generate a lock failure. Patch DI*22*147, which\nhas already been released, provided a solution to resolve this issue and\nfuture lock issues.\n \nThis patch instituted a new default lock timeout of three seconds based on\na global node setting of ^DD("DILOCKTM")=3.\n \nIn order to avoid the lock issue in Controlled Substances, this patch\n\n\nThis patch addresses the following problems:\n \nWhen a controlled substance is transferred from one NAOU to another NAOU,\nthe Activity Report [PSD NURSE DISP REPORT] does not include the transfer\nif the receipt date is different then the transfer date.\n \n3. 136028 Pharmacist able to fill expired order.\n \nThis patch will prevent the pharmacist from filling expired orders.\n \n4. 161718 Pharmacist can't order an inactive drug on NAOU\n \n \nIt also allows a pharmacist to see inactive drugs on the lookup.\n \n5. 158898 PSD DEST Drugs Report does not work properly.\n \nIf the first date in the "AD" cross reference of file #58.86 (call it Y) \nis after the last date in the "AC" cross reference (call it X) and\nthe starting date for the report falls between the two dates\n(X < starting date <Y)then an <UNDEFINED> error occurs.\n1. 129499 PSDGSRV1 undefined error\n \nWhen completing a greensheet and the user includes a ";" semicolon at the\n"REASON TURN IN FOR DESTROY:" or "REASON RETURNED TO STOCK:" prompts, a\n$ZE= <SYNTAX> BR+1^DIE0 error is generated.\n \n2. 68785 PSDPAT1 Transferring of Controlled Substances \n\n
\nThis patch addresses the following problems:\n \n 3. HD168800 - Inventory issued to NAOU somehow was doubled by Nurse\n The Ward Nurse used the PSD REC GS option to accept an update from\n Pharmacy, during this acceptance the inventory was doubled from 10\n units to 20 even though only 10 units were involved. Pharmacy was able\n to correct the problem and present inventories reflect actual\n inventory. This is caused by two users being allowed to access the same\n greensheet at the same time.\n 1. HD169083 - Vault Setup\n In Controlled Substances, under the Site Parameters option (PSD SITE),\n the user is unable to add an inpatient site.\n \n 2. HD98252 - Daily Activity Log does not record change on CS invoice\n After a Drug Accountability Verified Invoice has been edited, the Daily\n Activity report does not properly display Drug Accountability\n adjustments correctly..\n\n
\nWhen a PCA/Syringe is already signed out to a patient and that\ngreen sheet and patient are trasnferred to another NAOU, the \nquantity is subtracted from the sending NAOU and added to the\nreceiving NAOU even though it has already been signed out to\nthe patient.\n\n
\nReturned to Stock does not accept quantity and PS Order Entry error.\nThis patch also correct the pending order report problem for digitally\nsigned order.\n\n
\nThe FY10 Q2 Enhancement Release includes the following.\nPHARM TECH], and allows the holders of this new key to perform these\nadditional functions.\n \na. All options under the Receipts Into Pharmacy [PSD RECEIPTS MENU] menu.\n Receiving [PSD RECEIVING]\n Purchase Order Review [PSD PURCHASE ORDER REVIEW]\n Control Point Transaction Review [PSD CP TRANSACTION REVIEW]\n Drug Receipt History [PSD DRUG RECEIPT HISTORY]\n Invoice Review (Prime Vendor) [PSD PV INVOICE REVIEW]\n \n \nb. All options under the Dispensing Menu [PSD DISPENSING MENU].\n Print CS Dispensing Worksheet [PSD WORKSHEET PRINT]\n Fill/Dispense CS Orders from Worksheet [PSD WORKSHEET DISPENSING]\n Dispensing/Receiving Report (VA FORM 10-2321) [PSD PRINT 2321]\n Green Sheet - Print (VA FORM 10-2638) [PSD PRINT 2638]\n Reprint Reports Menu [PSD REPRINT MENU] menu\n Reprint Disp/Receiving Report (VA FORM 10-2321)\n Green Sheet Reprint (VA FORM 10-2638)\n Dispensing Worksheet Reprint\n Label Reprint for Dispensing Drug\nPharmacy Legacy Quarterly Enhancements (PLQE) subcommittee recommended the\n Reprint Transfer Between NAOUs (VA FORM 10-2321)\n Pharmacy Dispense without (VA FORM 10-2638) [PSD DISPENSE W/O GS]\n Label for Dispensing (Barcode) [PSD LABEL DRUG/NUMBER]\n Narcotic Dispensing Equipment Orders [PSD DISPENSE TO NDES]\n \nc. The following options under the Destructions Menu [PSD DESTROY MENU].\n Hold a CS Drug (No Inventory Update) [PSD DEST NON-CS DRUG]\n Non-VA Drug Placed on Hold for Destruction [PSD DEST TEXT DRUG]\n \nd. The following options were also added to the Technician (CS Pharmacy)\ncreation of a new security key named PSD TECH ADV that will allow\n Menu [PSD PHARM TECH].\n Manufacturer, Lot #, and Exp. Date - Enter/Edit [PSD MFG/LOT/EXP DATE\n EDIT]\n Outpatient Rx's [PSD OUTPATIENT]\n \n Note: The CS technician will be allowed to perform all the\n functionalities of the Outpatient Rx's [PSD OUTPATIENT] option\n except the releasing of a prescription.\nControlled Substances (CS) V. 3.0 package technicians to perform functions\ncurrently controlled by the pharmacist key and/or on the pharmacist menu.\n \nThis patch creates this new security key PSD TECH ADV, adds the following\noptions from the pharmacist menu to the Technician (CS Pharmacy) Menu [PSD\n\n
\nThis patch addresses the following problems:\n (Narcotics Area Of Use) does not reflect the Greensheet information\n for the transferred to ward but omits that information for the\n transferred from ward.\n \n3. HD343422 - Option displays wrong drug w/ PSD NURSE DISPENSING\n The "Sign Out Dose for Patient" [PSD NURSE DISPENSING] option returns\n the incorrect drug when scanned in and the incorrect drug is displayed.\n \n4. HD355446 - <undefined>DRUG+18^PSDRF *NAOU\n User receives an error when using the Sign Out Dose For Patient [PSD\n \n NURSE DISPENSING] option and enters a Pharmacy Dispensing # \n (Greensheet) that has a dispense date greater than one year old.\n1. HD67437 - BAC-1101-40568 Change in count & inability to track\n The Activity Report [PSD NURSE DISP REPORT] option does not print\n the correct drug balances.\n \n2. HD114292 - Activity report for transferred doesn't show activity\n until next day\n The "Activity Report" [PSD NURSE DISP REPORT] option for the NAOUs\n\n
\nThe routines were modified to address the Year 2000 compliance issues\nregarding dates. All VA FORM'S will now display the year as four digits.\n\n
\nPatch PSD*3.0*71 addresses two (2) issues.\n key to perform all the functionalities of the Outpatient Rx's [PSD \n OUTPATIENT] option EXCEPT releasing prescriptions.\n \n2. The use of the PSD TECH ADV key was extended to grant its holder\n access to the options listed below. These options are available on the\n Technician (CS Pharmacy) Menu [PSD PHARM TECH].\n \n Complete Green Sheet [PSD COMPLETE GS]\n Destroyed Drugs Report [PSD DEST DRUGS REPORT]\n DEA Form 41 Destroyed Drugs Report [PSD DESTROY DEA41]\n \n Destructions Holding Report [PSD DESTRUCTION HOLDING]\n Add Existing Green Sheets at Setup [PSD EXISTING GS]\n Green Sheet Transfer Between NAOUs Report [PSD GS TRANSFER (NAOU)\n REPORT]\n Transfer Drugs between Dispensing Sites [PSD TRANSFER VAULT DRUGS]\n \n Once the patch is installed, the options on the Technician (CS \n Pharmacy) Menu [PSD PHARM TECH] will be similar to the list below.\n \n Select Technician (CS Pharmacy) Menu Option: \n1. The recently released patch PSD*3*69 introduced a new key PSD TECH ADV,\n \n Print CS Dispensing Worksheet\n Fill/Dispense CS Orders from Worksheet\n Green Sheet Ready for Pickup Log\n Pick Up Green Sheet\n Complete Green Sheet\n Green Sheet History\n Add Existing Green Sheets at Setup\n Green Sheet Transfer Between NAOUs Report\n CS Order Entry For Ward\n intended to allow a Controlled Substances technician access to some of\n Receipt of Controlled Substance from Pharmacy\n Daily Activity Log (in lieu of VA FORM 10-2320)\n List On-Hand Amounts\n TD Transfer Drugs between Dispensing Sites\n TR Transfer Drugs between Dispensing Sites Report\n Receipts Into Pharmacy ...\n Dispensing Menu ...\n Destructions Menu ...\n Destroyed Drugs Report\n DEA Form 41 Destroyed Drugs Report\n the Pharmacist's menu as described in the PSD*3*69 patch description.\n Destructions Holding Report\n Manufacturer, Lot #, and Exp. Date - Enter/Edit\n Outpatient Rx's\n Some users have expressed concerns related to the Outpatient Rx's [PSD\n OUTPATIENT] option because the new PSD TECH ADV key was supposed to\n allow the posting of the transaction but not allow the release of the\n prescription. This patch will now allow a holder of the PSD TECH ADV\n\n
\nThe e-Prescribing of Controlled Substances (ePCS) project, which is \nCOMPUTERIZED PATIENT RECORD SYSTEM (CPRS) V. 3.0. It should be assigned\nonly to registered pharmacists working with Schedule II-V drugs.\n \nThe assignment of security key PSDRPH may be done at any time after the \nrelease of this patch to begin the setup process required for ePCS.\nscheduled to be released later this year, will provide enhanced \nfunctionality to allow for the electronic prescribing of controlled\nsubstances while meeting Drug Enforcement Administration's regulations and\nrequirements.\n \nIn preparation for this project, new security key PSDRPH is being added \nin this patch. This key authorizes pharmacists to finish/verify digitally\nsigned Schedule II-V Controlled Substance (CS) orders placed via\n\n
\nThis patch is being released as part of the DEA e-Prescribing of \n -----------------------------------------------------------------\n 3 SCHEDULES I - V\n \n Select Schedule(s): 3// SCHEDULES I - V\n \n Do you wish to sort by Inventory Type? NO// \n \n ...\n \n4. List On-Hand Amounts [PSD ON-HAND] and List On-Hand Amounts [PSD\n ON-HAND TECH]\n KERNEL V. 8.0 XU*8*580\n ------------------------------------------------------------------\n These options are modified to allow the selection of specific CS \n Schedules when running the report as seen below:\n \n ...\n \n Select Primary Dispensing Site: OPC VAULT// \n Select Schedule/Drug\n \n Select one of the following:\n PHARMACY DATA MANAGEMENT (PDM) V. 1.0 PSS*1*166\n \n 1 SCHEDULES I - II\n 2 SCHEDULES III - V\n 3 SCHEDULES I - V\n 4 INDIVIDUAL DRUG\n \n Select Schedule(s): 3// SCHEDULES I - V\n \n DEVICE: \n \n COMPUTERIZED PATIENT RECORD SYSTEM (CPRS) V. 3.0 OR*3*306\n ...\n \n5. Inventory Sheet Print [PSD INVEN SHEET PRT]\n -------------------------------------------\n This option is modified to allow the selection of specific CS\n Schedules when running the report as seen below:\n \n ...\n \n Select Primary Dispensing Site: OPC VAULT// \n CONTROLLED SUBSTANCES (CS) V. 3.0 PSD*3*73\n Select Schedule/Drug\n \n Select one of the following:\n \n 1 SCHEDULES I - II\n 2 SCHEDULES III - V\n 3 SCHEDULES I - V\n 4 INDIVIDUAL DRUG\n \n Select Schedule(s): 3// SCHEDULES I - V\n OUTPATIENT PHARMACY (OP) V. 7.0 PSO*7*391\n \n DEVICE: \n \n ...\n \n6. Controlled Substance Prescriptions Report [PSD CS PRESCRIPTIONS REPORT]\n -----------------------------------------------------------------------\n This option is a new option. It will provide a report of digitally \n signed orders that have been filled for Schedules I-V CS. The report\n will be for a date range with the option of including discontinued\n \n and/or expired orders and various sort criteria, list by patient, by\n provider, by drug and by schedule, etc. It will be an 80-column report\n and will be queued to a printer.\n \n7. DEA DATA - Waived Practitioner Report [PSD DEA SUBOXONE]\n --------------------------------------------------------\n This option is a new option. This report provides a list of patients \n that were prescribed Suboxone drugs. Two views are available, one with\n details, and another with just the counts of Suboxone patients per\n prescriber. \nNote: Patches PSO*7*391 and PSD*3*73 are being released in the Kernel \n Installation and Distribution System (KIDS) multi-build distribution\n CPRSV29_PSO_PSD. \nControlled Substances (CS) project using Public Key Infrastructure (PKI)\n \nThe following modifications and enhancements are included in this patch\n(PSD*3*73):\n \n1. Digitally Signed CS Orders Report [PSD DIGITALLY SIGNED ORDERS]\n --------------------------------------------------------------\n a) This option is modified to allow the selection of specific CS\n Schedules when running the report as seen below:\n \n ...\nto satisfy requirements requested by the Drug Enforcement Administration\n \n Sort By: Drug// ?\n \n Enter a code from the list.\n \n Select one of the following:\n \n D Drug\n PR Provider\n PA Patient\n(DEA).\n S Schedule\n \n Sort By: Drug// Schedule\n \n Select controlled substance schedule(s)\n \n Select one of the following:\n \n 1 SCHEDULE II\n 2 SCHEDULES III - V\nThe applications involved in this project along with their patch \n 3 SCHEDULES II - V\n \n Select Schedule(s): 3//\n \n ...\n \n b) Two new fields are being added to the report output: 'Detox #'\n and '# of Refills'.\n \n2. Digitally Signed OP Released Rx Report [PSD DIG. SIGNED RELEASED RX] \nnumbers are listed below and the same order should be followed when\n -------------------------------------------------------------------- \n a) This option is modified to allow the selection of specific CS \n Schedules when running the report as seen below:\n \n ...\n \n Start Date: T (FEB 29, 2012)\n \n End Date: T (FEB 29, 2012)\n \ninstalling the patches.\n Select a schedule(s)\n \n Select one of the following:\n \n 1 SCHEDULE II\n 2 SCHEDULES III - V\n 3 SCHEDULES II - V\n \n Select Schedule(s): 3//\n \n \n ...\n \n b) Two new fields are being added to the report output: 'Detox #'\n and '# of Refills'.\n \n3. Inspector's Log for Controlled Substances [PSD PRINT INSPECTOR LOG]\n -------------------------------------------------------------------\n This option is modified to allow the selection of specific CS Schedules\n when running the report as seen below:\n \n APPLICATION PATCH\n ...\n \n Select NAOU: <RET>\n \n All Controlled Substances or Selected Schedules?\n \n Select one of the following:\n \n 1 SCHEDULES I - II\n 2 SCHEDULES III - V\n\n
\nThis patch addresses the following problems:\ndifferent pharmacy locations, not all of transactions show up on\nthe RX (Prescription) Outpatient Dispensing Report [PSD RX DISPENSING\nREPORT].\n1. HD0000000438928 - Balance Adjustment Problem w/Activity Report\nThe Activity Report [PSD NURSE DISP REPORT] option does not print the\ncorrected drug balances for drugs that have a combination of Verify\nCount, Sign Out Dose for Patient with a balance adjustment and then \nVerify Count a second time.\n \n2. HD0000000457994 - RX not showing on report\nWhen there are multiple transactions for the same date/time and\n\n
\nThis patch addresses the following problems:\n \n1. A portion of this report is not working correctly Rx (Prescription)\n Outpatient Dispensing Report\n \n2. Destruction holding numbers do not appear on the Destroyed Drugs Report\n after being destroyed.\n \n3. Printing Issue\n\n
\nThis patch addresses the following problems:\n \n \n2. INC000001234782 - Ordered By Field\n \nProblem:\n--------\nThe CS WORKSHEET (#58.85) file ORDERED BY (#12) field is not being \nupdated correctly when someone edits a controlled substance order for an \nNAOU using the CS Order Entry for Ward [PSD ORDER ENTRY] option.\n \n1. INC000000997119 - PRESCRIPTION TRANSACTION\n \nProblem:\n--------\nIf two outpatient prescription transaction are created at the same \ndate/time for the same pharmacy location, both will not display in the \nRx (Prescription) Outpatient Dispensing Report [PSD RX DISPENSING REPORT].\n\n
\nThis patch addresses the following problems: \n \n(#58.8) during ordering. \n \nA post-install cleanup routine will search any transactions that have different\npharmacy dispensing numbers and the same Drug Accountability Stats file (#58.8)\nrequest number. Once these transactions have been identified, a new request\nnumber will be assigned and saved. \n \nAn informational report will be sent in MailMan to all the users that hold the\nPSDMGR security key. \n \n5. Using option "PSD DESTROY DRUGS" to process a destruction cancellation,\n \nExample Report: Subj: PSD*3*79 TRANSACTION REPORT [#141412] 04/18/12@14:49 15\nlines From: PSD*3*79 POST INSTALL In 'IN' basket. Page 1 *New* \n--------------------------------------------------------------------------\n This report contains Controlled Substance drugs that assigned multiple \n Pharmacy Dispensing numbers to a single request number in the Narcotics \n Area Of Use (NAOU) during order processing. \n \n These transactions have been identified and corrected. \n \n resulted in an error\nNAOU Pharmacy Transaction Old/New \n Drug Name Dispensing # Number Request # \n==========================================================================\nECU-EAST \n LEVORPHANOL TARTRATE 2MG TAB 31359 347041 2/3 \n 31360 347042 2/NA \n \n \n***** End Of Report ***** \n \n \nIn case no transactions need to be fixed the Mailman message below will be\nsent:\n \nSubj: PSD*3*79 TRANSACTION REPORT [#141414] 04/18/12@14:53 4 lines From:\nPSD*3*79 POST INSTALL In 'IN' basket. Page 1 *New* \n--------------------------------------------------------------------------\n \nTHERE WERE NO TRANSACTIONS TO REPORT. \n \n***** End Of Report ***** \nASSOCIATED REMEDY TICKET(S): \n \nTechnical: \n----------\n^PSDEXGS1, ^PSDNTT1, ^PSDNTTP1, ^PSDOPT0, ^PSDOR2, ^PSDORD, ^PSDORD3, ^PSDORD4,\n^PSDORN0, ^PSDORNO, ^PSDORP, ^PSDORP2 and ^PSDORV routines will be modified to\nlock the pharmacy location at the drug level prior to acquiring and\nincrementing the request number in the Drug Accountability Stats file (#58.8)\nwhen a user orders a drug. \n \n4. R11999082FY17 - Inventory Sheet inaccurate for Biloxi inpatient Vault \n============================\n \nProblem: \n--------\nWhen the user up-carets (^) out at the prompt, "REASON EDITED" during \nEdit/Cancel Verified Orders [PSD EDIT/CANC VER ORD] option with the intent of\ncancelling the request, it displays "** No action taken. **", indicating the\ntransaction was aborted. When you look at the master vault inventory, it has\nbeen updated, however, the Controlled Substance order for the NAOU and the\ngreen sheet are not updated, creating a discrepancy. \n \n1. I10091822FY16 - Return to Stock Issue \nResolution: \n-----------\nThe routine that performs the transaction updates has been modified to perform\nall updates after all the user prompts. If the user up-carets (^) out then the\nchanges are aborted. \n \nTechnical: \n----------\nRoutine PSDEVO1 has been modified to update the master vault inventory, NAOU\nControlled Substance order and the green sheet only after the user completes\n2. I10140662FY16 - Return to stock entry not always accepted \nall the prompts.\n \n5. R14730330FY17 - Reporting event of errors that occurred during VISTA\n operations\n6. I14905678FY17 - Similar issue as in R14730330FY17, but in the drug item\n field (free text)\n \nProblem: \n--------\nWhen using the options, Non-VA Drug Placed on Hold for Destruction [PSD \n3. I10152355FY16 - Site reporting problems with Controlled Substance Green Sheets \nDEST TEXT DRUG] and Destroy a Controlled Substances Drug [PSD DESTROY \nDRUGS], entering a ";" in a free text field such as drug item or the \ncomment field causes a hard error.\n \nResolution: \n-----------\nTo prevent the hard error, the drug item and the comment field will be\nvalidated to not allow entry of a ";".\n \nTechnical: \n4. R11999082FY17 - Inventory Sheet inaccurate for Biloxi inpatient Vault \n----------\nRoutine PSDEST and PSDESTF will be modified to check for ";" in the \ncomment field and to display a message, "A semicolon is not allowed in the\nCOMMENTS field. Please edit your entry."\n \nRoutine PSDESTF will be modified to check for ";" in the drug item field\nand to display a message, "A semicolon is not allowed in the DRUG ITEM\nfield. Please edit your entry."\n \n5. Using option "PSD DESTROY DRUGS" to process a destruction cancellation,\n resulted in an error\n6. I14905678FY17 - Similar issue as in R14730330FY17, but in the drug item\n field (free text)\n \n \nASSOCIATED NSR(s): \n==================\nN/A \n \n1. Return to Stock Issue \nPARTICIPATING TEST SITES: \n=========================\nOKLAHOMA CITY, OK\nHUDSON VALLEY HCS \n \nOVERVIEW: \n=========\n1. I10091822FY16 - Return to Stock Issue \n \nProblem: \n \n--------\nA Controlled Substance (CS) Refill is returned to stock through Outpatient\nPharmacy (OP) package. When prompted, the user selects NO to add the stock to\nthe balance in the Narcotic vault because the medication was going to be\ndestroyed if it is left in the pharmacy. (They cannot add it back to stock in\nthis case.) The refill was marked as Returned to Stock in the OP package. \nWhen the user re-submitted the refill, they tried to post it in the CS package.\nThe system allows the user to release the refill in the OP package, but since\nthe refill had not been added back to inventory, the CS package did not\nrecognize that the refill had been filled again, and did not allow them to post\n2. Return to stock entry not always accepted \nthe refill. \n \nResolution: \n-----------\nThe routine PSDOPT0 that is called from the Outpatient Pharmacy system that\nperforms the Return To Stock for Controlled Substances will be modified to \naccount for a Controlled Substance drug that is being returned with the intent\nto destroy. \n \nTechnical: \n \n----------\nRoutine PSDOPT0 will be modified to set the return to stock quantity to zero\nif the user answers NO to the Do you want ## added to balance in the Narcotic\nvault? Yes// prompt. (## is the quantity that that was dispensed) \n \n2. I10140662FY16 - Return to stock entry not always accepted \n \nProblem: \n--------\nWhen a pharmacist is entering return to stock in the Controlled substance \n3. Site Reporting Problems with Controlled Substance Green Sheets \npackage, it is not being accepted if the user does not select a Controlled\nSubstance vault to return it to. \n \nResolution: \n-----------\nThe routine PSDOPT0 that performs the 'Return to Stock' for Controlled\nSubstances will be changed to force a user to select a Vault and not enter\npast. The "Prescription Not Returned to Stock" message will also be displayed. \n \nTechnical: \n \n----------\nRoutine PSDOPT0 will be modified to exit properly without making any updates if\nthe user does not select a Controlled Substance vault to return the drug to. \n \n3. I10152355FY16 - SITE Reporting Problems with Controlled Substance \n Green Sheets \n \nProblem: \n--------\nThe Green Sheet Ready for Pickup Log [PSD PRINT GS PICKUP] option does not show\n4. Inventory Sheet inaccurate for Biloxi inpatient Vault \nall of the Green Sheets Ready for Pickup. This is caused when 2 users order the\nsame drug from the same Narcotics Area Of Use (NAOU) at the same time. This\nresults in multiple orders being assigned to the same request number for a drug\nin the Drug Accountability Stats file (#58.8). \n \nResolution: \n-----------\nThe routines that create the entries in the Drug Accountability Stats file\n(#58.8) will be modified to lock drug at the pharmacy location prior to\nacquiring and setting request number in the Drug Accountability Stats file\n\n
\nNSR20160911 To allow PSD TECH ADV key holders to run the Controlled \nSubstances NAOU Usage Report.\n\n
\nDefect Tracking System Ticket(s) & Overview:\nreport option. Upon further research it was determined that if a \nprescription had at least one fill that was transmitted to CMOP (not yet\nreleased) it would prevent all the prescription fills from being listed on\nthis report even though they could have been dispensed locally, which is the\npurpose of the report, to list locally dispensed controlled substance\nprescription fills that have not posted on the CS Vault inventory.\n--------------------------------------------\n1. R19391179FY18 - Rx not showing on Rx Disp Report\n \nProblem: \n--------\nTogus VA noticed a problem with a controlled substance prescription that\nwas filled locally and released but was not showing up on the Rx\n(Prescription) Outpatient Dispensing Report [PSD RX DISPENSING REPORT] \n\n
\nModified routine to eliminate the UNDEFINED ERROR for EXP.\n\n
\nMedication Prescribing and Dispensing Updates. Modification to Digitally \nsigned CS Orders Report.\n\n
\nThis patch is in support of two NSRs\nNSR20171101 Controlled_Substance Narcotic Count Input\nNSR20171111 Pharmacy Activity Report Sched II Meds\nSee forum for a complete description of this patch PSD*3.0*84\n\n
\nThis patch for a patch is created in support of PSD*3.0*84. \nmaintaining the original branching flow connected to the PRIME VENDOR \nfield.\nPSD*3.0*84 added the BALANCE DISCREPANCY CHECK field (#37) to the DRUG \nACCOUNTABILITY STATS file (#58.8). Routine PSDEN is used to display \nfields from this file for editing based on when the 'Location Type' field \nis set to 'MASTER VAULT'. After release of PSD*3.0*84 it was discovered \nthat if another field 'PRIME VENDOR' was set to NO or null the BALANCE \nDISCREPANCY CHECK field would not display as expected. This patch \nPSD*3.0*87 will allow the field the BALANCE DISCREPANCY CHECK fiel #37\nto be edited regardless of the state of the PRIME VENDOR field #12, while \n\n
\nThe description of this build can be found in the National Patch Module \nunder PSD*3.0*88.\n\n
\nThis patch will fix 3 incidents. Two of these will address an issue that \noccurs after a controlled substance is returned to stock and users are\nable to update the CS vault without the reprinting of the Rx label. The\nother incident that will be addressed is when an CS Rx has been released\nby the Outpatient Pharmacy package after the CS has been returned to stock\nand the label reprinted, users are unable to update the CS vault \ninventory.\n\n
\nThis patch contains updates to the following reports to support eRx:\n - Controlled Substance Prescriptions Report [PSD CS PRESCRIPTIONS REPORT]\n - OP CS Orders Report [PSD DIGITALLY SIGNED ORDERS]\n - OP Released Rx Report [PSD DIG. SIGNED RELEASED RX]\nIn addition, the Option Menu Text was changed for the following Options:\n - Digitally Signed CS Orders Report [PSD DIGITALLY SIGNED ORDERS]\n Changed Text: OP CS Orders Report [PSD DIGITALLY SIGNED ORDERS]\n - Digitally Signed OP Released Rx Report [PSD DIG. SIGNED RELEASED RX]\n Changed Text: OP Released Rx Report [PSD DIG. SIGNED RELEASED RX]\n\n
\nThis patch will fix the following issue:\n \nThe Controlled Substance's Balance Discrepancy Check does not count a \nquantity entered that contains a decimal as an attemnpt.\n\n
\nThis patch will fix the following issue:\n \nAn issue was reported that when using the VistA option Outpatient Rx's \n[PSD OUTPATIENT] to sign out a controlled substance after a refill was \npreviously returned to stock, a user is presented with the opportunity to \nsign out the original fill even though it had previously been signed out.\n\n
\nPlease see FORUM for PSD*3.0*94 patch description.\n\n
\n \nThis patch contains modifications to two options, Send Inspections\nInventory TRAKKER Data to DHCP [PSD IRL INSP DATA] and Send Vault TRAKKER\nInventory Data to DHCP [PSD IRL INV DATA]. It removes the check for the\nPSDMGR security key when using this option and corrects a problem of the\ndispensing site being left undefined.\n \nAlso, the CS IRL PROGRAM file (#58.88) is modified to send an end of \ntransmission message to DHCP, to correct a problem with OpenM sites.\n\n
\nCorrect balances on the Activity report.\n\n
\n The Controlled Substances software will monitor and track the receipt,\nNEW FUNCTIONS\n \no Batch Order Entry process\n \no Electronic Signature\n \no Nurse Dispensing with a Radio Frequency Device\n \no HL7 Interface to Narcotic Dispensing Equipment\n \ninventory, and dispensing of controlled substances. Automation of the\no Electronic Error & Enhancement Requests (E3Rs)\n \no Other Enhancements\nnarcotic inventory process will permit pharmacists and inspectors to\nperform vault inventories utilizing portable bar code readers. Monthly (or\nmore frequent) inspections can be conducted by management, with\ndiscrepancies in stock levels automatically identified. This software\npackage addresses a Congressional material weakness for Drug\nAccountability.\n \n\n
\nThe Controlled Substances module provides functionality to monitor\nand track the receipt, inventory, and dispensing of all controlled\nsubstances.\n\n
\n The following changes were made to address Y2K compliance issues.\n Line Tag : PROCESS+11\n Exception : Flagged to be changed \n $E(PSADT-100-(+$E(PSADT,4,5)=1*8800),1,5)*100\n Resolution: No change necessary, the code is calculating the previous\n month, and all Y@K checks appear to function correctly.\n \n Routine : PSAUP1\n Line Tag : XTMP+21\n Exception : Use of checking to see if number is >90 does not comply with\n a 70-30 split.\n \n Resolution: Changed to check for date within the recommended 70-30 split.\n \n Routine : PSUDP\n Line Tag : PICKLST+10\n Exception : Setting the node in global ^XTMP("PSAPV",0) to DT+1 would not\n be appropriate for dates such as FEB 28th.\n Resolution: Changed to a "C^%DTC" call which uses FileManager to calculate\n the correct date.\n \n\n\nWhen the Inpatient dispensing data is gathered, the program checked only\none entry for each ward to find a match for a pharmacy location. A loop\nhas been installed to check for the proper pharmacy location.\n\n
\n When the Outstanding Credits [PSA OUTSTANDING CREDITS] option is\n executed, and undefined error occurs in routine PSACREDO at line PRINT+17.\n The error occurs when all items on a invoice are adjusted to zero.\n\n
\nWhen the vendor sends the synonym node entry for the invoice's entry in the\nDRUG file (#50). A variable was used in the assumption that the vendor\nwas supplying the facility with the correct information.\nAn error occurs when the program tries to find the matching information\non nodes that do not exist.\n\n
\n When trying to match items to the National Drug file, the software was\n using old NDF globals. \n\n
\n When the user tries to print a report of invoices that were uploaded, \n an undefined error could occur at HAVDEDRG+1 of the PSAUP4 routine if\n the 2 node was missing from the DRUG file (#50).\n\n
\n When an invoice is uploaded, the program checks for the UPC and NDC. If\n these fields are not populated, the program exits. A check for the VSN\n was added to enable the program to continue.\n \n This will also cause problems in the verify portion. A check has been\n added to one of the verification routines.\n\n
\n This build contains the correct version of routine PSATI which was\n released in patch PSA*3*18. That patch had test version number five as\n the final version. \n\n
\nThe set-up for device selection will not allow 80 column reports to be\nsent to the screen. This causes massive amounts of wasted paper\nto obtain information that should be readily available to the user.\nThis patch will allow 80 column reports to be sent to the screen.\n\n
\n When invoices are added during processing, the DIC call used should be\n a FILE^DICN. Plus the lookup variable is set to look for an exact match.\n Order numbers such as "(B)123244556" cannot be added to the DRUG \n ACCOUNTABILITY ORDER file (#58.811). This patch corrects the call.\n\n
\nWhen invoices are added during processing, the DIC call used should be \na FILE^DICN. Plus the lookup variable is set to look for an exact match. \nOrder numbers such as "(B)123244556" cannot be added to the DRUG \nACCOUNTABILITY ORDER file (#58.811). This patch corrects the call. \n \nThe solution to this, as stated in the first line, is to change the DIC\ncall to a FILE^DICN call. \n\n
\n If an items quantity is adjusted to zero, the system would pick up the\n invoiced quantity instead.\n\n
\n There is a problem with the routine that is called when a picklist\n is filed away in Unit Dose. The routine improperly processed the incoming\n data. The processing method created incomplete data records of drug\n transactions.\n \n To correct this, the program does not rely on a temporary global being\n created. The data is extracted directly from the UNIT DOSE PICK LIST \n STATS (#57.6) file.\n\n
\n1. This patch modifies the Input Transform of the following fields to\n RECEIVED field (#20) and BALANCE field (#22) in the ORDERS sub-file\n (#58.800118) of the DRUG sub-file (#58.8001) in the DRUG\n ACCOUNTABILITY STATS file(#58.8).\n \n - MONTHLY ACTIVITY field (#.01), BEGINNING BALANCE field (#1), ENDING\n BALANCE field (#3), TOTAL RECEIVED field (#5), TOTAL ADJUSTED field\n (#7), TOTAL DISPENSED field (#9), TOTAL RETURN TO STOCK field (#11)\n and TOTAL TURN IN FOR DESTRUCTION field (#12) in the MONTHLY\n ACTIVITY sub-file (#58.801) of the DRUG sub-file (#58.8001) in the\n DRUG ACCOUNTABILITY STATS file (#58.8).\n allow three decimal digits:\n \n - This patch updates the data dictionary of the QUANTITY field (#5),\n BALANCE FORWARD field (#9), QUANTITY RECEIVED field (#27), QUANTITY RET\n TO STOCK field (#35), QUANTITY TURN IN FOR DESTROY field (#38), BALANCE\n FWD RET/STK field (#41), NEW QUANTITY field (#50), ADJUSTED BY QUANTITY\n field (#51), BAL FWD EDIT VERIFIED ORDER field (#54), ADJUSTMENT\n QUANTITY field (#57), BAL FWD CANCEL VERIFIED ORD field (#59),\n QUANTITY TRANSFERRED field (#70), ORIGINAL COUNT field (#75), WASTED\n QUANTITY field (#76), LIQUID AMOUNT field (#77) and CORRECT COUNT field\n (#79) in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81).\n \n \n2. This patch modifies the data dictionary of the BALANCE FORWARD field\n (#9) in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81), to prevent\n editing through VA FileMan options.\n \n3. This patch modifies the data dictionary of the the TRANSACTION NUMBER\n field (#.01) in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81), to\n disallow deletion though VA FileMan options.\n - STOCK LEVEL field (#2), BALANCE field (#3), REORDER LEVEL field (#4),\n QUANTITY TO REORDER field (#5) and MAXIMUM QUANTITY PER ORDER field\n (#8.5) in the DRUG sub-file (#58.8001) in the DRUG ACCOUNTABILITY\n STATS file(#58.8).\n \n - QUANTITY ORDERED field (#5), QUANTITY DISPENSED field (#19), QUANTITY\n\n
\n 1. This patch modifies the method used to update a drug's NDC and other\n \n If the invoiced item's Order Unit and Dispense Units per Order Unit match\n the same fields in the DRUG file, but the price of the dispense unit has\n changed then the following process occurs:\n \n a. The new price per dispense unit is compared with the PRICE PER\n DISPENSE UNIT field (#16) in the DRUG file (#50), to see if it is\n within 5%. If it is not within the 5% difference, the PRICE PER\n DISPENSE UNIT field (#16) in DRUG file (#50) is set to the invoiced \n price per dispense unit, and the PRICE PER ORDER UNIT field (#13)\n pricing information.\n in the DRUG file (#50) is set to the invoiced price per order unit.\n \n b. A MailMan message is sent to members of a new mail group called:\n 'PSA NDC UPDATES' to inform them of the price change. The subject of\n this message is: "DRUG file Price/NDC Update".\n \n c. Because of the problems with price calculations in the past, a post\n patch install routine has been added to correct current incorrect\n prices.\n \n \n 2. When processing invoices, the system checks for the pharmacy locations\n that will be used during processing. If no locations are found the \n program proceeds to exit the option. However, in the exit logic the\n system checks to see if the user has up arrowed or if something has\n failed. If the exit variable has not been set, the program continues on\n to automatically enter the invoice into VISTA.\n \n 3. Another problem this created was when the user would proceed with manual\n processing of these invoices, the pharmacy location field would be empty.\n This creates an undefined global node when the program tried to find the\n The revised method of updating the NDC and price information is as\n location name. If pharmacy locations are not set up, the exit variable\n is not set, therefore the invoices are processed.\n \n 4. When the Connect Unlinked DRUG/ITEM MASTER file Entries [PSA UNLINKED \n LOOP] option is executed an undefined error occurs. The problem stems\n from the user not selecting a drug to link to. The solution to this\n problem is to change where the routine is called.\n \n 5. When printing the Verification Error Report if the report is printed to\n the screen or a slave printer it's fine. If the report is queued to a\n follows:\n printer, none of the data prints out.\n \n The problem with this was that the variable saved for the print job was\n a simple variable, not a variable array as it should be.\n \n 6. Due to site integration, invoices can sometimes be processed more\n than once. The invoice file is checked during uploading to see if the\n invoice currently exists, but the check is not performed when the user\n processes the information. The solution to this is a check being added\n that will compare the invoice's Order Number, Invoice Number and the\n \n line items against what is stored in VistA. If a close enough match is \n found, a comparison array of data will be displayed for the user. After\n displaying the data, the user has the option of eliminating the incoming\n invoice.\n \n 7. The option Delete Un-processed Invoices [PSA DELETE INVOICES] has been\n created to delete invoices that are on file past a user specified date.\n \n 8. When processing invoices, if an item has the same vendor stock number\n but different NDCs, a new synonym entry is created. When the item is\n If the NDC on an invoiced item does not match the NDC field (#31) in\n being processed again, the system will display the same drug as two\n different choices. The problem is, that there is not enough detailed\n information provided for proper selection. The solution to this was to\n add the NDC to the display.\n \n 9. When invoices are processed for multiple divisions, or by multiple\n personnel, all invoices show the same person as the processor. This\n was caused by the last function of processing. When the user finishes\n processing, the program would look at each invoice. If the invoice\n was marked as processed, the data would be moved into the proper files.\n the DRUG file (#50), then the NDC entry in the DRUG file (#50) will be \n the program did not distinguish between users. The solution to this is\n to file the data immediately for each invoice as it is marked as\n processed.\n changed to the invoiced NDC.\n\n
\nThis enhancement provides a DELPHI based redesign of the Upload Invoices \nprocess currently in the Drug Accountability/Inventory Interface Version \n3.0 software. This option is used to upload invoice data from the Prime \nVendor and update VISTA Drug Accountability files. The redesigned \nfunction, using DELPHI instead of ProComm script files will make \nuploading invoices simpler and faster. \n \n\n
\n 1. When sites do not process all uploaded invoices, problems arise when \n 2. Another problem this patch corrects is with the filing of monthly data\n on drug items. Monthly data was incorrectly stored for some items in \n the DRUG ACCOUNTABILITY STATS file (#58.8). This patch corrects already \n affected entries, and restricts the erroneous filing of incorrect data \n in the future.\n the next batch of invoices is uploaded. Drug Accountability attempts to \n match each item with items in the DRUG file (#50). The process will\n continue to add matching data to the item. If the invoices remain on the \n system long enough an error will occur.\n \n The solution to this is to bypass the matching process on invoice data \n that has already been uploaded. \n \n\n
\nThis patch will fix two undefined errors in menu option Edit Verified\nDrug File (#50), an undefined error occurs when trying to subtract the\ninvoiced quantity.\nInvoices.\nAn undefined error occurs when editing a verified invoice if the user \nchanges the name of a drug and the order units are different. This error\noccurs when prompting for the Dispense Units per Order Unit.\n \nWhen the user edits a line item and changes the drug name, the invoiced\nquantity is updated in the Drug File (#50); subtracted from the invoiced \nitem and added to the new item. If the invoiced line item is not in the\n\n
\n This enhancement contains the updated GUI based changes for the Upload\n Invoices process used by Drug Accountability V. 3.0 to process invoice\n data received from the new Prime Vendor, McKesson. \n\n
\nThis patch will modify the Report Potential NDC Matches option to use the \nsame criteria as the Controlled Connection by NDC Match.\n\n
\nThis patch addresses the problem in Drug Accountability where the menu \n"Setup/Edit a Pharmacy Location" [PSA LOCATION EDIT] generates the \nfollowing error: $ZERROR=DAVEB+5^PSAENTO:3, %DSM-E-UNDEF, undefined \nvariable Y(0,0).\n\n
\nCompliance with MailMan patch XM*7.1*50 and NDF patch PSN*3.18*5\n\n
\nThis patch will modify PSA PROCESS PRIME VENDOR DATA Process Uploaded \nPrime Vendor Invoice Data to always prompt the user when there is a change\nin the Vendor Stock Number's NDC. This is currently happening only if the\ncurrent NDC is numeric.\n\n
\nTHIS PATCH CORRECTS AN UNDEFINED LOCATION ERROR.\n\n
\n 1. When sites do not process all uploaded invoices, problems arise when \n 2. Another problem this patch corrects is with the filing of monthly data\n on drug items. Monthly data was incorrectly stored for some items in \n the DRUG ACCOUNTABILITY STATS file (#58.8). This patch corrects already \n affected entries, and restricts the erroneous filing of incorrect data \n in the future.\n the next batch of invoices is uploaded. Drug Accountability attempts to \n match each item with items in the DRUG file (#50). The process will\n continue to add matching data to the item. If the invoices remain on the \n system long enough an error will occur.\n \n The solution to this is to bypass the matching process on invoice data \n that has already been uploaded. \n \n\n
\nThis patch addresses two problems:\n \n1. Uploading on invoices from the new prime vendor has lost the \ncapability to automatically match invoice items to the drug file entries \nand manual editing is necessary on nearly every item on every invoice.\n \n2. The wrong VSN is shown for the selected item to be edited when \nediting verified invoices. The VSN displayed belongs to the last item \npresented in the choices for selection display.\n\n
\nINCORRECT QUANTITY ADDED TO DRUG IN DRUG FILE\n\n
\nThis patch will correct a syntax error in routine PSAVERA2.\n \nMultiple options with erroneous outpatient division on \npharmacy locations.\n\n
\nThis patch address the following problems:\n2. 85690 Drugs that are added to pharmacy locations are initially \nsetup with a minimum of information and need to be completed manually by \nthe pharmacy staff. A method of notification is needed to let the \npharmacy staff know which drugs are needing completion.\n \n3. 68611 Invoice items that have a zero quantity are updating \ninventory costing for dispensing. This results in a miss-representation \nof costs being presented for statistics and being billed to third party \ninsurances.\n \n1. 68526 Price updates into the Drug file #50 are failing \ndue to current logic that both order units and dispense units between the \nmatched drug and the invoice must be equal before updating. Also, the\nreporting and/or representation of which drugs are about to have order\nunits, costs, dispense units, and/or NDCs is hard to read, not concise,\nand unwanted changes are being overlooked.\n \n\n
\nThis patch addresses the following problems:\nDRUG ACCOUNTABILITY STATS file (#58.8) has several of it's indexes \nscrambled and the users are not able to select the drug within that \npharmacy location for any further processing purposes. A post init \nroutine will scan and clean up bad indexes it finds.\n \n3. 100058 Drug Balances by Location [PSA DISPLAY LOCATION]\nThe report menu "Drug Balances by Location" show entries for inactive \ndrugs that have a zero quantity. Those items are now not to be shown.\n \n4. 108683 Verify Invoices [PSA VERIFY INVOICES]\n \nDrugs that are new to a pharmacy location in the DRUG ACCOUNTABILITY \nSTATS file (#58.8) are needing more data entered to complete their being \nsetup for processing. Such items as current balance, stock level, and \nreorder levels are needed. A separate, individual mail message is \ncurrently sent regarding each drug that is newly added. The volume of \nmessages is overwhelming.\n \nA single consolidated mail message by invoice regarding drugs that are \nnewly added is needed to replace the individual mail messages.\n1. 68490 Editing Verified Invoices [PSA EDIT VERIFIED INVOICE]\nSaying 'NO" to processing the edit changes made for DISPENSE UNITS field \n(#14.5) and/or DISPENSE UNITS PER ORDER UNIT field (#15) of the Drug file \n(#50), does not restore those fields to their previous values.\n \n2. 68779 Editing Verified Invoices [PSA EDIT VERIFIED INVOICE]\nA drug that is newly picked and added newly to a pharmacy location in the \n\n
\nHD68504 Invoices not being able to be up loaded. This patch corrects \nproblems with the algorithm used to convert invoice files received from \nMcKesson. The process incorrectly inserts zeros to the transaction set \ncontrol number, which caused the length of the number to exceed the \nrequired specification length. An example of the error message is shown \nbelow:\n \nControl# 0000000000000000000000000033\nThe ST control# (piece 3) should be 4 to 9 characters in length.\n\n
\nThis patch addresses the following problem:\n2. HD128777: Pharmacy locations, in the DRUG ACCOUNTABILITY STATS file \n#58.8, may have their associated entries in the drug file updated by zero \nquantity invoice items if the location is not marked for tracking \ninventory or re-order levels.\n \nNOTE: A post init will review the Drug file (#50) and remove all but the \nfirst of identical synonym duplicates from under a drug. A "PSA*3*56 \nDelete Duplicate Drug Synonyms report" mailman message will be sent to \nthe person who performs the installation identifying what drug-synonyms \nhad identical synonyms deleted. It will also indicate if there were none \n \nfound to be removed.\n \nEXAMPLE 1) Duplicate synonyms found and were deleted.\nSubj: PSA*3*56 Delete Duplicate Drug Synonyms report [#2019687] \n03/17/06@17:11\n11 lines\nFrom: PSA*3*56 POST INIT In 'IN' basket. Page 1\n--------------------------------------------------------------------------\nPSA*3*56 DELETE DUPLICATE SYNONYMS REPORT\nThe following Drug-Synonyms have had identical synonyms removed from the \n1. HD68257: Drug SYNONYM field (#9) duplicates are being created in the \ndrug.\nDrug Name DRG#,SYN# NDC VSN\nACETAMINOPHEN, CODEINE 60MG TAB 3994,7 00406-0484-10 2792513\nOU: CS PPOU: $9.60 DUOU: 1000 PPDU: $.01\nACETAMINOPHEN, CODEINE 60MG TAB 3994,11 00406-0484-10 2792513\nOU: BT PPOU: $9.60 DUOU: 1000 PPDU: $.01\nACETAMINOPHEN, CODEINE 60MG TAB 3998,7 00406-0484-10 2792513\nOU: CS PPOU: $9.60 DUOU: 1000 PPDU: $.01\nACETAMINOPHEN, CODEINE 60MG TAB 3998,11 00406-0484-10 2792513\nOU: BT PPOU: $9.60 DUOU: 1000 PPDU: $.01\nDRUG file (#50). The process of verifying an invoice that is adding a new \n \nEXAMPLE 2) No duplicate synonyms found and none were deleted.\nSubj: PSA*3*56 Delete Duplicate Drug Synonyms report [#2019688] \n03/17/06@17:15\n3 lines\nFrom: PSA*3*56 POST INIT In 'IN' basket. Page 1\n--------------------------------------------------------------------------\nPSA*3*56 DELETE DUPLICATE SYNONYMS REPORT\n \nThere were no duplicate drug-synonyms found. No synonyms were removed.\ndrug synonym to the DRUG file (#50) was found to be adding duplicates in \n \nEnter message action (in IN basket): Ignore//\nthe same invoice and between invoices that were processed at the same \ntime. The verification process now insures duplicates are not being \ncreated.\n \n\n
\nA variable was mistakenly left out in the programming of patch PSA*3*8.\n\n
\nThis option gives the user the ability to select and store drugs that are\nto be returned to the manufacturer.\n \nThe OUTDATED MEDICATIONS option is located within the PHARMACY LOCATION\nMAINTENANCE menu and locked with the PSAMGR key.\n\n
\nThis patch addresses the following problems:\nProcessed status!' is presented.\nProcessing invoices through a particular path and question sequence will \ngenerate the above message which is wrong as the invoice has just \ncompleted processing necessary to be able to proceed to the verification \nstage.\n \n3. HD 91604 An undefined error occurs when the selection list of invoices \nto send on to verification has a missed node in the display numbering \nsequence of the invoices. The user is able to put in a range from the \nbeginning of the list to the last number in the list and the processing \n \ntries to work on all numbers in between. It hits the number of the \nmissing node and it breaks.\n1. HD 68113 Invoice select prompt (1-0)\nThe software is not properly detecting when all invoices being worked \nwith have been processed. It is asking the user to make a selection when \nthere are no invoices left to select from. The software errors out with \nan undefined if the user continues.\n \n2. HD 93607 A faulty message 'The invoice has not been placed in a \n\n
\nThis patch will correct the problem of the Post Verify e-mail\nnot sent when changes are made to the invoice.\n\n
\nThis patch addresses the following problems:\ngiving the user the chance to verify the selection. The drug name is \nunique and the few characters input by the user is enough to select the \ndrug. Once the drug is selected it is not easy to navigate the software \nto a place where the drug can be reselected if the selection completed by \nthe software is not what the user wanted.\n \n1. HD 67762 PSANDF 12 digit NDC\nThe emerging standard is becoming 11 digits for the National Drug Code \n(NDC). The code had previously been set to create/require 12 digits by \nadding leading zeros. It is now set to create/require 11 digit NDCs. \n \n2. HD 68340 Forced selection of unique drug names.\nThe software is completing the selection of a unique drug name without \n\n
\nThis patch is addressing the following problems:\n2. HD 118113. The sites have requested that the verification screens also \ndisplay the vendor DUOU and drug description.\nBoth processing and verification screens will have the following \ninformation line displayed. The information displayed depends on the \navailability of vendor information uploaded.\n \n========================= \nSAMPLE OF THE ADDED LINE: \n========================= \nThere are two versions of the display line added.\n \n1) The line if the drug information is available\n PV-Drug-Descrip: ACETAM? TB #4 ROX RN4X25 PV-DUOU: 100\n \n2) The line if the drug information is not available.\nPV-Drug-Descrip: Not available. Item is OTC or new after February 2006.\n \n===========================\nSAMPLE of modified screen:\n===========================\nThe same line of information is presented in both processing and \n1. HD 112456 Reinstate the display of vendor item Dispense Units per \nverifying screens.\n \nOrder#: C563685000 Invoice#: 7246433050 Invoice Date: Sep 07, 2005\n-----------------------------------------------------------------------\n \n1 ACETAMINOPHEN, CODEINE 60MG TAB (Controlled Substance)\nQty Invoiced: 10 UPC: 300054802324\nOrder Unit : TU NDC: 00054-8023-24\nUnit Price : $9.60 VSN: 1334150\n \nOrder Unit (DUOU) during processing. PSA*3*48 initiated a temporary plan \nPV-Drug-Descrip: ACETAM? TB #4 ROX RN4X25 PV-DUOU: 100\n \nDispense Units: TAB\nDispense Units Per Order Unit: 2000\nto aid sites in starting Drug Accountability by shipping in a side file \nfrom the vendor and display DUOU for matching drugs when possible during \nprocessing. It has been requested that the vendor drug description also \nbe included to aid in matching items to drugs.\n \n\n
\nProblem HD129689 - Undefined error while processing invoice\n--------------------------------------------------------------\nThe program PSAPROC7 will be modified to cleanup the variables prior\nto the call to DICN0.\n \nProblem HD92886 - Leading zero's in supply item description \n--------------------------------------------------------------\nIf a line item on an invoice is edited to be a supply item and\nthe supply item description starts with a numeric (Example: 16\nvial dram, or 10x10 sponge) the system interprets the leading\nnumeric's as an internal entry number to the Drug File. This\n--------------------------------------------------------------\nwill cause the software to erroneously select the wrong drug.\n \nResolution HD92886 - Leading zero's in supply item description\n--------------------------------------------------------------\nThe code has been modified to ignore the fact that the supply\nitem description starts with a leading numeric.\n \nProblem HD68635 - Undefined error while editing invoices\n--------------------------------------------------------------\nIn rare cases, the UPC and/or the NDC code in an invoice has\nDuring the processing of an invoice, it is possible to receive\nno value. If this is the case, the software will error out\nwith an undefined error while editing an invoice to be verified.\n \nResolution HD68635 - Undefined error while editing invoices\n--------------------------------------------------------------\nThe code in question will be strengthened to not error out when\nthis scenario occurs.\nThe following message:\nUndefined N1+3 DICNO Unable to Process Invoice\nThis error is caused by the system not properly cleaning up variables\nused by the program DICN0.\n \nResolution HD129689 - Undefined error while processing invoice\n\n
\nThis patch addresses the following problems:\nterms of the McKesson contract, is the date they deposit the invoice into \ntheir output directories for sites to access. The default date in VistA \nDA terms had been and is, the received at site date. Management has\ndetermined it is best to require the users to manually enter the receive \ndate than to present a default date which is never correct and should not \nbe accepted.\n \n3. 68532 PSADRUGP <UNDEFINED>DISP~PSADRUGP\nThe "Enter/Edit a Drug" [PSA PV DRUG ENTER/EDIT] errors when the drugs\ninactivation date is less then the day of the data entry.\n \n \n4. 131384 PSAVER2 Error using Verify Invoice [PSA VERIFY INVOICES] \nWhen verifying invoices, the application errors if the data in the\nprocessed invoice contains a semicolon. \n \n5. 134108 PSAVER, PSAVER1, PSAVER4 Invoice approved twice\nDuring Invoice Verification, multiple users are aloud to select the same\ninvoice and verify it. The quantities in the DRUG file (#50) are updated \neach time the invoice is verified.\n \n1. 67941 PSAPROC1 undefined in PSAPROC1\n6. 154985 PSAVER1 Invoice not verified, but message appears\nInvoices are being marked as verified at the line item level when using \nthe Verify Invoices [PSA VERIFY INVOICES] option and selecting an\ninvoice from the <<< EDIT INVOICES TO BE VERIFIED SCREEN >>>\nIf a Controlled Substance (CS) drug has not been assigned to a master \nvault, the subsequent code path is killing variables it will be needing \nlater when it returns from the call to perform vault selection.\n \n2. 68039 PSAPROC3 default date\nThe data element in invoices that represents the receive date, under \n\n
\nWith the deployment of Cache version 5, it was discovered that the short\nmodifies all routines that currently use a lock timeout value of less than\n3 seconds to check for the node ^DD("DILOCKTM") and to use the value\ndefined there, otherwise the lock timeout value is set to a default value\nof 3 seconds.\nlock timeout values could generate a lock failure. Patch DI*22*147, which\nhas already been released, provided a solution to resolve this issue and\nfuture lock issues.\n \nThis patch instituted a new default lock timeout of three seconds based on\na global node setting of ^DD("DILOCKTM")=3.\n \nIn order to avoid the lock issue in Drug Accountability, this patch\n\n\nThis patch addresses the following problems:\n report shows the status as UNKNOWN.\n \n2. 187185 Can only verify one invoice at a time after PSA*3*60\n When using the EDIT INVOICES TO BE VERIFIED SCREEN and the user selects\n multiple invoices to edit, the application quits after editing the first\n invoice.\n \n1. 186350 DA INVOICES UNKNOW STATUS\n.There are two separate issues \n a. The invoice status remains LOCKED VERIFYING when there are errors\n in the invoice. This LOCKED VERIFYING status does not allow any\n further action until the invoice status has been reset to PROCESSED\n or VERIFIED.\n b. When an invoice is in a LOCKED VERIFYING status, the Print Orders\n\n
\nThis patch addresses the following problems:\nWhen using the "Edit Verified Invoices" [PSA EDIT VERIFIED INVOICE] \noption, the application does not remove the correct quantity which\nresults in inaccurate quantities being recorded. \n \n3. 119930 PSAPROC4 Multiple NDC match selection needs DUOU displayed\nWhen using the "Process Uploaded Prime Vendor Invoice Data" [PSA PROCESS \nPRIME VENDOR DATA] option, the user is presented a list of drugs and \nrelated information if there is multiple synonyms exist. Currently the \nDose Unit Order Unit (DUOU) is not displayed in that information. The \nlack of this informationcan result in the wrong drug being selected \n \nduring invoice processing.\n \n4. 191994 PSAVERA Duplicate receipt issue\nWhen using the Edit Verified Invoices [PSA EDIT VERIFIED INVOICE] option \nto edit an invoice that has not been verified, the DRUG ACCOUNTABILITY\nTRANSACTION file (#58.81) is updated. Then when the user verifies the \ninvoice the DRUG ACCOUNTABILITY TRANSACTION file (#58.81) is updated \nagain causing duplicate transactions for the invoice item(s) that the \nedit was done on.\n1. 68175 PSAENTO Time Out Issue\nUser reported that the "Set Up/Edit a Pharmacy Location" [PSALOCATION \nEDIT] option does not quit properly when the application times out at\nthe INPATIENT SITE NAME prompt.\n \n2. 98252 PSAVERA Daily Activity Log does not record change on CS \ninvoice \n\n
\nThis patch is a combination of patches 3,4,5,7,8,9,10,11,12,13.\n\n
\nThis patch modifies the screens within the processing and verification\n \nCurrently, the Item Description and the inner pack fields are stored in\na temporary global which was setup in patch PSA*3*54. This global is no\nlonger used. The addition of the four fields is intended to assist the\nuser with the matching of incoming invoice items to the Drug (#50) file.\nBelow is an example of what the screens look like prior to installation\nof this patch.\n \n <<< PROCESS LINE ITEM SCREEN >>>\nOrder#: 3TC01 Invoice#: 7289249573 Invoice Date: Oct 05, 2007\nprocesses within Drug Accountability. Additional drug information is\n6 HYDROCORTISONE\nQty Invoiced: 1 UPC: 30472034356\nOrder Unit : EA NDC: 00472-0343-56\nUnit Price : $0.67 VSN: 1279124\n \nPV-Drug-Descrip: HYDROCORT AC CRM 1% ALP 30GM@ PV-DUOU: 28.4\n \nAfter patch installation:\n \n <<< PROCESS LINE ITEM SCREEN >>>\nnow being included in the invoice files received from the prime vendor.\nOrder#: 3TC01 Invoice#: 7289249573 Invoice Date: Oct 05, 2007\n6 HYDROCORTISONE\nQty Invoiced: 1 UPC: 30472034356\nOrder Unit : EA NDC: 00472-0343-56\nUnit Price : $0.67 VSN: 1279124\n \nPV-Drug-Description : HYDROCORT AC CRM 1% ALP 30GM@ PV-DUOU : 28.4\nPV-Drug-Generic Name : HYDROCORTISONE PV-Units: 1\n \nThe additional fields are:\n Generic Description\n Item Description\n Prime Vendor Units (i.e. # bottles in sell unit)\n Inner Pack (i.e. # pills in bottle)\n\n
\nThis patch addresses the following problems:\n \n1. 167457 Non CS drugs appear on narcotic dispensing/receiving report\nThe PSA IV ALL LOCATIONS [PSA IV ALL LOCATIONS] background job colliding\nwith CS dispensing.\n \n2. 205861 ^PSDRUG LOCKS\nPSA Verify Invoice processing is not unlocking the drug when finished.\n\n
\nThis patch addresses the following problems:\nThe drug accountability list does not differentiate between the \nintegrated sites.\n \n3. 184524 - NDC changed from numbers to letters\nDrug accountability invoice processing is changing the NDC from numeric \nto letters.\n \n4. 222558 - Supply item match to drug file\nThe PRE Verify and POST Verify Variance Reports inaccurately report\nchanges for supply items that have leading numerics.\n \n \n5. 229658 - Outdated Medications\nThe Outdated Medications [PSA OUTDATED MEDICATIONS] option does not \ndisplay\nall possible matches for a drug if the DRUG file (#50) index "C" is a\nmatch to the information entered at the "Scan Drug barcode or enter a drug\nname" prompt.\n1. 180658 - Outdated Medications Option Not Working\nThe Outdated Medication [PSA OUTDATED MEDICATIONS] option, which allows\nfor documentation of the return of non-controlled substances, used the CS\nDestruction file (#58.86). This file will not allow the user's name to be\nrecorded.\n \n2. 172859 - Outdated drug list for integrated sites\n\n
\nThis patch addresses the following problems:\n \n3. HD266899 - Error when running PSA IV ALL LOCATIONS\nWhen running the "Outdated Medications" report and it quits unexpectedly,\nthe ^TMP("PSA",$J global is left behind causing the "PSA IV ALL LOCATIONS"\noption to error.\n \n4. HD265183 - Blank Order Unit on zero qty received causes supplies\n to appear on error report\nWhen an invoice contains a blank Order Unit and a zero quantity, all \nsupply items that follow, are included in the error report.\n \n \n5. HD273421 - Cost Calculated Incorrectly on Outdated Meds\nThe cost on the Items To Be Returned report should be calculating based\non number of Dispense Units returned multiplied by Price Per Dispense\nUnit from file 50. Instead, it is multiplying the number of containers\nby the Price Per Dispense Unit:\n1. HD257764 - UNDEF ERROR\nWhen editing the ORDER UNIT for a Supply Item of a verified order, the\napplication errors with an undefined error.\n \n2. HD255967 - UNDEF ERROR <UNDEFINED>EDIT1+36^PSAUTL1\nDuring Order Processing if 2 users select same orders to process and 1\nuser is editing an order, the application will error.\n\n\nThe FY08 Q4 Enhancement Release includes the following enhancement in the\n 1 Batch Work List [PSA RET DRG BATCH WORKLIST]\n 2 Batch Complete List [PSA RET DRG BAT COMPLETE LIST]\n 3 View/Update Batch [PSA RET DRG VIEW/UPDATE BATCH]\n 4 Return Drug Credit Report [PSA RET DRG REPORT]\n \nThe Batch Work List [PSA RET DRG BATCH WORKLIST] option will be used to\nprocess open return batches, which are assigned a statuses of 'AWAITING\nPICKUP' and 'PICKED UP'.\n \nThe Batch Complete List [PSA RET DRG BAT COMPLETE LIST] option allows \nDrug Accountability V. 3.0 application.\nusers to access and update batches with any status.\n \nThe View/Update Batch [PSA RET DRG VIEW/UPDATE BATCH] option is used for\nsingle batch processing, independent of its status.\n \nThe Return Drug Credit Report [PSA RET DRG REPORT] option provides\nthe users with summary and detailed reports of all return batches.\n \nSecurity Keys:\n-------------\n \nIn order to have access to the new options, a user must have the PSORPH\nor PSARET security key. The PSORPH key is an existing key in the\nOutpatient Pharmacy V. 7.0 application. The PSARET is a new security key\nin the Drug Accountability application, will be transported in this patch\nand should be assigned to users who will be responsible for returning\ndrugs to the contractor.\n \nNew Files:\n---------\nThe following two new files are being added to the Drug Accountability\nA new module is being added to the Drug Accountability application to \nV. 3.0 application to support the functionality delivered by this patch.\n \n \n UP SEND DATA USER\n DATE SEC. COMES SITE RSLV OVER\nFILE # FILE NAME DD CODE W/FILE DATA PTRS RIDE\n--------------------------------------------------------------------\n58.35 RETURN DRUG YES YES NO\n58.36 RETURN DRUG CONTRACTOR YES YES NO\n \naddress one of the findings in the GAO Report GAO-04-755 dated July 2004\n \nThe RETURN DRUG file (#58.35) is used to store all the information\nabout drugs being returned to the manufacturer while the RETURN DRUG\nCONTRACTOR file (#58.36) is used to store the list of contractors\nthat the VA Medical Center (VAMC) uses for returning drugs for credit.\nMost likely there will be only one contract active at a time for most,\nif not all, VAMCs.\nrelated to implementing a better control over Return Drug Credits. The new\nmodule is called Return Drug Credit Menu and contains the following 4\noptions.\n \n\n
\nThis patch addresses the following problems:\n The Drug Accountability Transaction History report in not correctly\n calculating the drug balance for dispensed drugs. Currently the report\n is adding the dispensed quantity instead of deducting it.\n \n1. HD335328 - Routine patch list needs editing\n When PSA*3*69 was release there was five new routines introduced.\n The format of the second line of five Routines sent out with patch\n PSA*3*69 need to be corrected. Instead of *69* they need to be *69*.\n \n2. HD342000 - Dispensed units not automatically subtracting from\n inventory\n\n
\nThis patch addresses the following problems:\n sent back. This was a mistake. It should be received in and then out.\n Then the verifier did the verification and changed the qty received to\n reflect the original qty received - correcting the mistake.\n After verifying the invoice, the user checked the Controlled Substance\n package and found the drug did not show as being received.\n \n3. HD322644 - Run away PSA IV ALL LOCATIONS - All Location Dispense/Purge\n The PSA IV ALL LOCATIONS - All Location Dispense/Purge nightly job does\n not complete.\n \n \n4. HD279969 - verifying invoices with blank order unit no longer on\n discrepancy report\n When processing a invoice with a blank ORDER UNIT the system returns a\n zero and does not generate a discrepancy report.\n1. HD211457 - Locked Invoice\n Sites are reporting that the invoices are being left in a LOCK\n VERIFYING status.\n \n2. HD285500 - Can't received drug (CS) into vault\n When a invoice was downloaded and processed by a tech, the quantity\n received was changed to 0 on one item because it was going to be\n\n
\nThis patch addresses the following problems:\n \n1. SUBSCRIPT>LINE+45^PSAPROC7\n \n2. Only Outpatient Figures on Reports\n \n3. DRUG TRANsaction History does not cleanup variables if up caret at \n the device prompt.\n\n
\nThis patch addresses the following problems:\nRun no updates are being made to the Drug Accountability Transaction file\n(#58.81) or the Drug Accountability Stats file (#58.8).\n \n3. INC000000842761 - Drug Accountability - Drug File Updates\nWhen the invoiced Price Per Order Unit is .01 and Dispense Units Per\nOrder Unit is 100, the Price Per Dispense Unit is calculating it at 0\nwhen it should be .0001 during invoice processing/verifying.\n \n1. INC000000443727 - Verify invoices and no action is taken\nWhen a Controlled Substance follows a drug that has a quantity of 0,\nthe Invoice Verify routine does not create the Controlled Substance \ntransaction in the Drug Accountability Transaction file (#58.81).\n \n2. INC000000212726 - Outpatient Dispensing (All Drugs) Option not working\nWhen the Outpatient Dispensing (All Drugs) [PSA OP ALL DRUGS] option is\n\n
\nThis patch addresses one (1) issue:\n \nProblem:\n--------\nVerified Drug Accountability (McKesson) invoices will not be set \nto a status of Complete if the user edits the invoice, verifies, \nand closes (or is disconnected from) their Reflections session at \nthe "Type <Enter> to continue or '^' to exit:" prompt. This causes \nan out-of-balance situation with regards to the controlled substance \nvault.\n \n \nResolution:\n-----------\nIf a user edits an invoice prior to verifying, VistA routine ^PSAVER1 \nsets the invoice status to VERIFIED and prompts for the user to \ncontinue or exit, via subroutine END^PSAPROC. The prompt at that point\nwaits for a response. If the user's Reflections session ends without \ncompleting the final prompt, important processing is missed with \nregards to setting up invoice data for the background job that changes \nthe status from VERIFIED to COMPLETE.\n \n1. McKesson invoice verified, but controlled substance balance did\nTo resolve this issue, the call to execute the prompt via END^PSAPROC \nhas been moved to a more appropriate spot in EXIT^PSAVER.\n not update\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n \n1. I5849148FY15\n\n
\nThis patch creates the PHARMACY PRIME VENDOR mail group. The Prime Vendor\nLine Item Report will be sent to this mail group from the Austin\nAutomation Center twice per week.\n\n
\nThis patch will resolve the following issue.\n \nProblem: \n--------\nVA Southern Nevada reported that they were unable to correct vault medication\nwith negative balance which is also inactive in the drug file. The negative\nbalance is actually caused by a problem in the Edit Verified Invoices [PSA\nEDIT VERIFIED INVOICE] option which incorrectly records transactions when\nan invoice is edited and a controlled substance drug is replaced with a\nnon-controlled substance drug and vice-versa.\n \n \nResolution:\n-----------\nModified the Edit Verified Invoices [PSA EDIT VERIFIED INVOICE] option to\ncorrectly record inventory transactions accordingly whether the drug is\nmarked as controlled substance or not.\n \nTechnical Resolution:\n---------------------\nChanged the routines PSAVERA and PSAVERA1 which are responsible for updating\nthe inventory transactions after a verified invoice is edited.\nINC0933704 - Unable to correct vault medication with negative balance which\n is also inactive in the drug file\n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\nINC0933704 - Unable to correct vault medication with negative balance which\n is also inactive in the drug file\n\n
\nAn incident was reported that when a pharmacist changes the drug name for \na line item on an invoice using the option VERIFY INVOICES and then the \ninvoice is subsequently verified by a different pharmacist, the new change\nis not saved properly in the invoice file. In turn, this causes some of\nthe various drug accountability reports to be inaccurate.\n\n
\nThis patch will resolve the following issues:\n \nSeveral sites have reported that when editing a verified invoice by \nchanging a non-controlled substance drug to a controlled substance drug a \nnegative balance for the non-controlled drug is appearing on the \nControlled Substance Inventory Sheet. Another defect experienced with \nthis same type of edit is the inability to select the non-controlled \nsubstance drug by name when trying to adjust the negative balance in the \ncontrolled substance vault.\n\n
\nWhen the Receiving Directly into Drug Accountability [PSA RECEIVING]\noption is used, the following error occurs:\n$ZE= HEADER+3^PSAREPV:3, %DSM-E-UNDEF, undefined variable PSA(2)\n \nAlso, the problem of not being able to enter decimal digits for the\ndispense units per order unit has been corrected.\n\n
\n 1). When an adjustment is made to the balance of a drug in a pharmacy\n \n 2). There is a problem with invoices being marked as processed when \n in fact they should not have been marked as such because there are\n data elements missing.\n Solution: When the individual line items are being processed the system\n checks the order unit. For a line item to successfully process\n as having an order unit, it must match one of the following 3\n conditions:\n a). The order unit is defined in the initial uploaded item\n b). An adjusted order unit has been entered\n location or invoice, the adjustment activity is recorded, but the\n c). The order unit is defined in the synonym multiple in\n the drug file.\n \n 3). After installing patch #3, if an invoice is being processed that is\n already on file for the same order number, a string too long error\n occurs at INVOICE+17 of routine PSAPROC7. \n \n 4). Invoices are passing through the processing and verification portions \n of Drug Accountability with no problem, however, when the system does\n the checking of the data for updating price and drug information, these\n stored data is not updated. Some Drug Accountability programs make\n problems are found, and nothing is updated.\n Solution: This is in part because of problem #2 above, the order unit.\n When the line item's data is being placed into the DRUG \n ACCOUNTABILITY ORDER file (#58.811), the system assigns the\n order unit to be either the value initially entered on the \n invoice, or the value in the synonym multiple, otherwise zero.\n No mention of the adjusted order unit. The order of assignment\n should be, synonym multiple, adjusted, then initial upload.\n \n 5). Several facilities do not have their pharmacy locations defined\n the adjustments internally before printing out the drug balances,\n properly in the DRUG ACCOUNTABILITY STATS file (#58.8), which results in\n errors. Usually the error is an undefined variable PSACOMB.\n (fixed in routine PSAUTL1)\n \n 6). Uploading of incomplete invoiced data is corrected.\n \n 7). The dispense unit per order unit is no longer asked for on supply\n items.\n (PSAVER2 - If the user identifies the drug as supply, then they should \n not be prompted for DUOU. Added a Line of code to check for PSASUPP.\n while other programs do not make these necessary calculations. Other\n \n 8). When the PSA IV ALL LOCATIONS is executed each evening as a background\n job, part of the OP dispensing functionality is to check each ward that\n is associated with the pharmacy location in the DRUG ACCOUNTABILITY STATS\n file (#58.8). Currently the program will discontinue processing if the ward\n doesn't match the pharmacy location, BUT it also quits if the ward\n does match the location. Therefore no OP dispensing data is recorded.\n (fixed in routine PSAPSI3)\n \n 9). Balances on Controlled Substances are not updated when the orders\n VISTA packages extract data from the Drug Accountability files on\n are verified.\n \n 10). When an invoice is being processed/edited, the order unit field will\n display the order unit associated with the line item based on adjustment,\n invoice's order unit or the order unit in the synonym of the drug file.\n When this field is to be edited, the only choices displayed are the \n original invoiced order unit or the drug file entry. If an adjustment\n had been made, the program ignored it. NOIS (HUN-1197-20485)\n (Fixed 13 Jan 99 in routine PSAPROC3).\n \n a regular basis, by not setting up the programs internally to make the\n 11). When patch PSA*3*3 was sent out, the second line syntax for the\n routines PSAUDP & PSAUP1 which were released in patch PSA*3*6, was\n erased. These two routines are added to this patch with updated second\n line syntax.\n \n 12). During the set up of a pharmacy location there was a problem with \n the call to obtain the outpatient pharmacy location. If there was more\n than one location that was spelled similarly the program would take the\n first one as default.\n \n calculations for the adjustments, the data they are obtaining is\n 13). When the user is processing invoices, they can actually enter a\n <RETURN> at the select pharmacy location or select master vault prompt.\n the system will continue to process normally, but an error will occur\n in SITES+1^PSAUTL1. This value must be entered for proper processing.\n The user must now up-arrow out of the selection.\n \n incorrect.\n\n
\nWhen an invoice is selected to be printed, and the invoice is still in\nthe temporary global used to hold data prior to processing/verification,\nthe last invoice in the file will be printed, instead of the selected\ninvoice.\n\n
\nDrug Accountability/Inventory Interface V. 3.0\n\n
\n \nOnce installation of this patch is complete, should your site continue to\nreceive Second/Third Period of Service errors, patient data will have to\nbe re-Requested/Unsolicited. This is due to the Period of Service fields\nhaving a value of null when transmitted. Routine has been properly\ncorrected to include a 'Yes' or 'No' value when transmission occurs.\n \n \nROUTINE SUMMARY:\n================\nBelow is the routine included in this patch. The second line of this\n1. When extracting the PDX*MAS data segment, all data pertaining to the\nroutine will look like:\n \n <tab>;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993 \n \n \n CHECK^XTSUMBLD results\n \n ROUTINE NAME BEFORE PATCH AFTER PATCH PATCH LIST\n ============= ============= ============ ==========\n VAQDBII1 2772903 2817374 13,24\n patient's PERIOD OF SERVICE was not able to upload using the LD or LF\n \n \n INSTALLATION INSTRUCTIONS\n ==========================\n 1. This patch can be loaded with users on the system. Installation\n will take less than 5 minutes. Use the INSTALL/CHECK MESSAGE\n option on the PackMan menu. This option will load the KIDS package\n onto your system.\n \n 2. Review your mapped set. If any of the routines listed in the\n of the LOAD/EDIT. Routine VAQDBII1 has been modified to correct this\n ROUTINE SUMMARY section are mapped, they should be removed from the\n mapped set at this time.\n \n 3. From the Kernel Installation and Distribution System Menu,\n Select the Installation menu.\n \n 4. From this menu, you may elect to use the following options\n (when prompted for INSTALL NAME, enter VAQ*1.5*24):\n ==========\n \n problem. This was reported in NOIS CAN-0595-10112.\n a. Backup a Transport Global - this option will create a backup\n message of any routines exported with the patch. It will NOT\n backup any other changes such as DDs or templates.\n \n b. Compare Transport Global to Current System - this option will\n allow you to view all changes that will be made when the patch is\n installed. It compares all components of the patch (routines, DDs,\n templates, etc.).\n \n c. Verify Checksums in Transport Global - this option will allow\n \n you to ensure the integrity of the routines that are in the\n transport global.\n \n \n \n 5. Use the Install Package(s) option and select the package\n VAQ*1.5*24\n ==========\n \n 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options,\n \n and Protocols? YES//', respond YES. When prompted to select the\n ===\n options you would like to place out of order, enter the following:\n \n \n VAQ (MENU) MAIN Patient Data Exchange\n ===============\n \n 7. MSM sites: Please ensure you answer YES when asked if you want\n to move the routines to other systems and indicated the appropriate\nIMPORTANT NOTICE:\n CPUs.\n \n 8. If routines were unmapped as part of step 2, they should be\n returned to the mapped set once the installation has run to\n completion.\n=================\n\n
\nPatch VAQ*1.5*35\nThis patch also provides a double-check to ensure that no transactions\nare sent to closed sites. Any such requests will be marked for purge.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*29.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQADM50 4268774 5135296 5,35\nVAQEXT01 5668219 6188779 14,35\nVAQUTL97 1499668 1906264 2,9,29,35\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\nNOIS FAV-1001-70165, MWV-1201-20937\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*29.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \nTest Sites: Fayetteville, AR; Martinsburg, WV\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*35 Loaded from Distribution <date/time>\n\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \nThis patch prevents the option VAQ PDX PROCESS EXTERNAL from displaying\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nto the user any external requests from closed sites. Any such requests\nwill be marked for purge.\n\n\n
\nPatch VAQ*1.5*37\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisite.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\n \nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQUTL96 370770 419526 37\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS MAD-1201-42417\nis at a minimum. It has no patch prerequisite.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\nTest Site: Madison, WI\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*37 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\nIf two (or more) PDX patients share the same first initial of the last name\n==========================================================================\nand the same last 4 digits of the SSN, PDX will only show the first patient\nwhen attempting to Load/Edit PDX Transactions based on patient name.\nThis patch fixes that.\n\n
\nPatch VAQ*1.5*36\ncorrupted .01 fields will not adversely affect NHE or any its data.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*34.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQUTL92 2986759 2983392 6,36\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOIS ANC-1201-51582\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*34.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\nTest Site: Anchorage, AK\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*36 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\nPatch VAQ*1.5*30 caused some corrupted .01 fields in file 394.62. Patch\n necessary.\n==========================================================================\nVAQ*1.5*34 stopped further corruption. (Please see the description in\npatch VAQ*1.5*34 for an explanation of the corruption.) The corruption\ncannot be undone, but it can be ignored. This patch ensures that the\n\n
\nPatch VAQ*1.5*38\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisite.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\nName Checksum Checksum Patch List\n \n-----------------------------------------------------------------\nVAQDBIM 4078867 4144431 38\nVAQDBIM4 3774719 4191649 38\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS MAD-1001-42696\nis at a minimum. It has no patch prerequisite.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\nTest Sites: Madison, WI; Milwaukee, WI; Tomah, WI; Iron Mountain, MI\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*38 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\nIf a veteran declines to give income information, PDX should display the\n==========================================================================\nmeans test as CAT C. Instead, PDX may display it as CAT A. This patch\nfixes that.\n\n\n
\nPatch VAQ*1.5*39\nunnecessary and are probably the cause of the problems. After the patch\nis installed, duplicate transaction numbers should no longer be created.\nFeel free to delete the pre-init, ^VAQPRE39, after installation.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisite.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n \n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQPRE39 * NEW * 268564 39\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces the following new routine:\nVAQPRE39 has no user-callable entry points and may be deleted after the\nNOIS TNV-0902-30675 (Remedy Ticket HD8627/CHG2933)\npatch has been installed.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch prerequisite.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\nTest Sites: Tennessee Valley HCS\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n\n Select INSTALL NAME: VAQ*1.5*39 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\nDuplicate transaction numbers in file VAQ - TRANSACTION (#394.61) continue\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nto be a problem. The pre-init for this patch deletes the triggers on the\nTRANSACTION NUMBER (#.01) field in file VAQ - TRANSACTION (#394.61) and\nDATA (#.01) field in file VAQ - DATA (#394.62). These triggers are\n\n
\nPatch VAQ*1.5*40\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires PDX patches VAQ*1.5*22 and *24. KIDS will\nnot check for the existence of these patches, because they pre-date KIDS.\nThe site is responsible for performing the check.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQDBII1 2817374 2861649 13,24,40\nVAQDIS30 5471356 6429479 13,22,40\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n==========================================================================\n \nNOIS MAD-0103-41237\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires PDX patches VAQ*1.5*22 and *24. KIDS will\nnot check for the existence of these patches, because they pre-date KIDS.\nThe site is responsible for performing the check.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \nTest Sites: Madison, Milwaukee, Tomah, & Iron Mtn\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*40 Loaded from Distribution <date/time>\n\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \nThis patch adds Yugoslavia service and Purple Heart information to the\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nPDX*MAS data which PDX extracts from the PATIENT file and displays on\nscreen 6.\n\n\n
\nThis patch will prevent a new patient from being added to the Patient (#2)\nfile if an existing patient with the same SSN exists. It also corrects a\nDR variable leak.\n\n
\nPatch VAQ*1.5*42\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch IB*2.0*267. It also requires patch\nVAQ*1.5*13. (KIDS will not check for this patch because it predates KIDS.\nYou must check manually.)\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQDBIP7 3165540 11036802 13,42\n\n* Checksums produced by CHECK^XTSUMBLD\n\nThis patch introduces no new routines.\n==========================================================================\n \nNOIS: none\nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch IB*2.0*267. It also requires patch\nVAQ*1.5*13. (KIDS will not check for this patch because it predates KIDS.\nYou must check manually.)\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \nTest Sites: Oklahoma City, OK; Madison, WI; Milwaukee, WI; Tomah, WI;\n4. You do not need to stop TaskMan.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*42 Loaded from Distribution <date/time>\n Montana HCS\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n\n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nThis patch alters PDX to use the new API from IB (Integrated Billing),\nintroduced in patch IB*2.0*256, to access billing (insurance) data.\n\n\n
\nPatch VAQ*1.5*41. Please refere to the Description in Forum Patch Module \nfor details.\n\n
\nThis patch addresses 2 issues with Patient Data Exchange (PDX):\n \n1) Issues adding users to notify for PDX transactions \n2) <UNDEFINED> errors occurring due to invalid Health Summary\n Component entries.\n\n
\n1. Y2K Waiver Request ID#:Y2KW0001 Y2K Waiver Status: Approved\n until creation of IEN and Transaction number.\n \n \nTest Sites:\n==========\nBrockton, MA - 525\nNashville, TN - 626 \nEastern Kansas HCS - 677\n \n \n This patch may be installed during the Y2K Moratorium, either\n \nRoutine Summary:\n===============\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;1.5;PATIENT DATA EXCHANGE;**[Patch List}**;Nov 17, 1993\n \nChecksums: CHECK^XTSUMBLD\n=========\n BEFORE 12/15/99 or AFTER 1/15/2000. This patch MAY NOT be\n \nRtn Nm Chksum Before Chksum Patch List\n------------------------------------------------------------------\nVAQFILE 3704729 3884670 22,26\nVAQREQ06 5069886 4782978 4,16,20,22,26\n \n \nInstallation Instruction:\n========================\n1. This patch can be loaded with users on the system.\n installed between 12/15/99 and 1/15/2000(the Y2K Lockdown Period).\n \n2. Routine mapping is NOT recommended for these routines. If you are\nusing routine mapping, review your mapped set and ensure that these\nroutines are NOT in your mapped routine before proceeding and rebuild\nyour map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nwill load the KIDS package into your system.\n \n4. The patch has now been loaded into a transport global and you will\n \nuse KIDS to install the transport global. On the KIDS menu, under the\n'Installation' menu, use the following options\n \n 2 Verify Checksums in Transport Global\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n INSTALL NAME: VAQ*1.5*26\n ==========\n BRK-0596-12069,EKH-0498-42577,EKH-1298-40432,NAS-0998-32328.\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n ==\n \n5. If routines were unmapped as part of step 2, they should be returned\nto the mapped set once the installation has run to completion.\n Several sites have indicated that VAQ-TRANSACTION FILE(394.61)\n periodically creates duplicate Transaction numbers. Routines\n VAQFILE and VAQREQ06 have been revised to ensure Lock of file\n\n
\nRefer to the patch description for an explanation of the changes included \nin this patch.\n\n
\n1. Y2K Waiver Exemption ID#:Y2KWE0034\n \nTest Sites:\n==========\nCleveland, OH - 541\nColumbus, OH(OPC) - 757\n \n \n \nRoutine Summary:\n===============\n This patch may be installed at any time during the Y2K Moratorium\nThe following routine(s) are included in this patch. The second line of\neach routine will look like:\n \n <tab>;;1.5;PATIENT DATA EXCHANGE;**[Patch List}**;Nov 17, 1993\n \nChecksums: CHECK^XTSUMBLD\n=========\n \nRtn Nm Chksum Before Chksum Patch List\n------------------------------------------------------------------\n (including the 12/15/99 thru 1/15/2000 Y2K lockdown).\nVAQFILE 3884670 3917792 22,26,28\n \n \nInstallation Instruction:\n========================\n1. This patch can be loaded with users on the system.\n \n2. Routine mapping is NOT recommended for these routines. If you are\nusing routine mapping, review your mapped set and ensure that these\nroutines are NOT in your mapped routine before proceeding and rebuild\n \nyour map set afterward before reactivating TaskMan.\n \n3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu. This\nwill load the KIDS package into your system.\n \n4. The patch has now been loaded into a transport global and you will\nuse KIDS to install the transport global. On the KIDS menu, under the\n'Installation' menu, use the following options\n \n 2 Verify Checksums in Transport Global\n CLE-1199-42576,COS-1299-40012.\n 3 Print Transport Global\n 4 Compare Transport Global to Current System\n 5 Backup a Transport Global\n 6 Install Package(s)\n INSTALL NAME: VAQ*1.5*28\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO\n Several sites has indicated that PDX is unable to store data into\n ==\n \n5. If routines were unmapped as part of step 2, they should be returned\nto the mapped set once the installation has run to completion.\n workload file #394.87, due to an undefine variable error. Routine\n VAQFILE has been revised to correct this problem.\n \n\n
\n \n \n Description:\n ============\n NOIS: ISA-0700-12514, NOL-0700-72818\n \n Sites had reported that PDX is generating error\n messages because of unable to find the correct\n Domain name from the Domain file. The problem that\n is causing this is that the pointer is using B\n cross reference. Routines are modified to point at\n \n C cross reference.\n \n \n List of Test Sites:\n ==================\n New Orleans, Montana\n \n \n \n ROUTINE SUMMARY \n Subject:\n =============== \n \n The following routines are included in this patch. The\n second line of each of these routines now looks like: \n \n <tab>;;1.5;PATIENT DATA EXCHANGE;**[patch list**; Date\n \n \n Routine Name Chksum Before Chksum After Patch List\n ------------ ------------- ------------ ----------\n Correcting wrong cross reference\n VAQUTL97 1469891 1499668 2,9,29\n VAQUTL99 2220508 2284414 2,10,29\n \n \n * From CHECK^XTSUMBLD\n \n \n \n \n Installation Instructions:\n \n ==========================\n \n 1. Users ARE allowed to be on the system during the installation.\n \n 2. DSM/AXP sites: Review your mapped routine set. If any of the\n routines in the Routine Summary section are mapped, disable\n mapping for the affected routine.\n \n 3. Use the "INSTALL/CHECK MESSAGE" option on the PackMan menu.\n This loads the patch into a Transport Global onto your system.\n \n \n 4. You DO NOT need to stop TaskMan or the background filers.\n \n 5. On the KIDS menu, select the "Installation" menu and use the\n following options to install the Transport Global:\n Verify Checksums in Transport Global\n Print Transport Global \n Compare Transport Global to Current System\n Backup a Transport Global\n \n Category:\n Install Package(s) \n INSTALL NAME: VAQ*1.5*29\n ==========\n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==== \n Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//\n ==\n \n Routine\n \n 6. DSM/AXP Sites - Answer NO to the question "Want to MOVE\n routines to other CPUs?"\n \n 7. DSM/AXP sites: If the routines were unmapped, the mapped\n set should be rebuilt once the installation has run\n to completion.\n \n \n.\n \n\n
\nPatch VAQ*1.5*32\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*28.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\nName Checksum Checksum Patch List\n \n-----------------------------------------------------------------\nVAQFILE 3917792 3972067 22,26,28,32\nVAQREQ06 4782978 4486600 4,20,26,32\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nNOIS CLE-0701-40883\nis at a minimum. It requires patch VAQ*1.5*28.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\nTest Site: Cleveland, OH\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*32 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\nThis patch stops PDX from locking file 394.61 when $$NEWTRAN^VAQFILE is\n==========================================================================\ncalled to add a new record to the file. ^DIC provides the appropriate\nlocking, so PDX doesn't have to.\n \n\n
\nPatch VAQ*1.5*31\nAdverse Reaction Tracking released a patch, GMRA*4*10, which changed the\ndata returned by EN1^GMRADPT if the patient has NKA.\n\nBefore the patch, the API returned:\nGMRAL=0\nGMRAL(<ptr to file 120.8>)=DFN_"^NKA^0^1"\n\nAfter the patch, the API returned:\nGMRAL=0\n\n \nPDX used to grab "NKA" from the GMRAL array. After GMRA*4*10, there was\nnothing to grab. This patch, VAQ*1.5*31, ensures that PDX recognizes that\nGMRAL=0 means "NKA".\n \nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisite requirement.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\nNOIS ISL-1198-52170\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQDBIP1 4400113 5323185 31\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n==========================================================================\nTest Site: Oklahoma City\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisite requirement.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*31 Loaded from Distribution <date/time>\n ==========\nThis patch enables PDX to recognize and report on NKA (No Known Allergy)\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\nwhen using the API EN1^GMRADPT, provided by the Adverse Reaction Tracking\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\npackage.\n\n\n
\n * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * \n HIN-0701-42706, OKL-0701-70784\nTest Sites: Oklahoma City, OK; Asheville, NC; Central Plains HCS\n\nThis patch prevents the sending of PDX messages to closed domains in two\nways.\n\n1. Prevents the addition of closed domains to outgoing groups:\nScreens are placed on 2 fields in the REMOTE FACILITY multiple\nin file 394.83, VAQ - OUTGOING GROUP. The fields are .01 REMOTE FACILITY\nand .02 REMOTE DOMAIN. For both of these, the DOMAIN file is checked\n This patch requires PDX patch VAQ*1.5*22. KIDS will not check\nto ensure that the domain is not closed. If it is, the screen fails\nand you are prevented from adding the remote facility to the outgoing group.\n\n2. Removes closed domains from outgoing groups:\nWhen PDX messages to outgoing groups are being built, the DOMAIN file is\nchecked to ensure that the domain is not closed. If it is, the remote\nfacility is deleted from the outgoing group, and the PDX message is not\nsent to that domain.\n \nNOTE: This patch should be installed during off hours, when user activity\n for the existence of this patch, because it pre-dates KIDS.\nis at a minimum. It requires PDX patch VAQ*1.5*22. KIDS will not check\nfor the existence of this patch, because it pre-dates KIDS. The site is\nresponsible for performing the check.\n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\n The site is responsible for performing the check.\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQREQ03 3858669 4459512 22,30\nVAQREQ05 4065406 4263629 30\nVAQXRF2 2617277 3203802 30\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n==========================================================================\n \n * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires PDX patch VAQ*1.5*22. KIDS will not check\nfor the existence of this patch, because it pre-dates KIDS. The site is\nresponsible for performing the check.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n\n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*30 Loaded from Distribution <date/time>\nPatch VAQ*1.5*30\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nNOIS CHY-0201-51534, ASH-0501-32739, CPH-0501-40775, BHS-0601-10382,\n\n
\nPatch VAQ*1.5*34\nIt is evidenced by the following:\n\n>D ^%G\n\nGlobal ^VAT(394.86\n VAT(394.86\n^VAT(394.86,0) = VAQ - AUTO-NUMBERING^394.86^1^1\n^VAT(394.86,1,0) = 1\n^VAT(394.86,1,1) = 390\n^VAT(394.86,1,2) = "1" <----- corrupted\n \n^VAT(394.86,1,3) = 8\n^VAT(394.86,"B",1,1) = \n\nand by:\n\nGlobal ^VAT(394.62,466\n VAT(394.62,466\n^VAT(394.62,466,0) = "1" <----- corrupted\n ...\n^VAT(394.62,"B","""1""",466) = <----- corrupted\nNOIS BIR-1101-31486\n\nThis patch fixes that, and cleans up the corruption in file 394.86.\nIt can't fix PDXs which were adversely affected. It can't fix file 394.62.\nThe PDXs will have to be resent, or the data entered manually, if necessary.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*30.\n==========================================================================\n \nROUTINES:\nTest Site: Birmingham, AL\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQFILE1 4265693 4507302 22,34\nVAQPRE34 * NEW * 148728 34\n* Checksums produced by CHECK^XTSUMBLD\n\n\nThis patch introduces the following new routine:\nVAQPRE34 - pre-init has no user-callable entry points\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It requires patch VAQ*1.5*30.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\n affected routine(s). \nPatch VAQ*1.5*30 exposed a problem which was not caught during its\n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n Backup a Transport Global\nextensive testing period. It was not caught until it was released.\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*34 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\nWe're very sorry about that.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\n\n\n
\nPatch VAQ*1.5*33\ngroup G.VAQ PDX ERRORS to inform them of this.\n\nNOIS WBP-0596-21007\nTest Site: Wilkes Barre, PA\n\nThis patch ensures that incoming PDX messages are deleted from the server\nbasket, whether they processed successfully or errored out.\n\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisites.\n \n==========================================================================\n \nROUTINES:\nThe second line of the routine now looks like:\n ;;1.5;PATIENT DATA EXCHANGE;**[patch list]**;NOV 17, 1993\n \n Before After\nName Checksum Checksum Patch List\n-----------------------------------------------------------------\nVAQADM2 2534049 3075526 33\nNOIS SBY-0801-31431, FAV-1001-70165, COS-1001-40729, MAR-1001-20783\n* Checksums produced by CHECK^XTSUMBLD\n \nThis patch introduces no new routines.\n==========================================================================\n \nINSTALLATION:\nNOTE: This patch should be installed during off hours, when user activity\nis at a minimum. It has no patch pre-requisites.\n1. Users may be on the system during installation of this patch.\n2. DSM Sites: If any of these routines is mapped, disable mapping for the\nTest Site: Salisbury, NC; Fayetteville, AR; Columbus, OH\n affected routine(s). \n3. On the PackMan menu, use the 'INSTALL/CHECK MESSAGE' option.\n This loads the patch into a Transport Global on your system. \n4. You do not need to stop TaskMan or the background filer.\n Users may be on the system.\n5. On the KIDS:Installation menu, use the following options to install\n the Transport Global.\n Verify Checksums in Transport Global\n Print Transport Global\n Compare Transport Global to Current System\n\n Backup a Transport Global\n Install Package(s)\n Select INSTALL NAME: VAQ*1.5*33 Loaded from Distribution <date/time>\n ==========\n Install Questions:\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n ==\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n ==\n Enter the Device you want to print the Install messages.\nThis patch checks PDX requests from remote sites to ensure that the remote\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// <It's up to you. You may queue it if you wish.>\n ------------------------------------------------\n6. DSM Sites: After patch has installed, rebuild your map set, if\n necessary.\n==========================================================================\nsite is not flagged as Closed in the Domain file. If the Domain file shows\nthat the site is closed, then the request is ignored, the message is\ndeleted from the server basket, and a message is sent to the members of the\n\n
\nThis module allows medical centers to exchange patient clinical and\nadministrative information through the use of MailMan. Requests can\nbe sent to a remote site. The remote site can process the request and\na message containing patient information will be returned.\n\n
\n This option has been modified to reduce the amount of indirection calls\n utilized in build the FOREIGN FACILTIY XREF File (#1020.2). Test sites\n for this patch have concluded that the new method reduces the time to\n build the file to 1/10th of the original process.\n\n
\nSee Patch PPP*1*30 in the National Patch Module for description of the\nBuild.\n\n
\n Patch XM*7.1*51 restructured some domain names to XXX.DOMAIN.EXT for \n stations that requested it. When routine PPPPDX3 tries to locate the \n domain name, a null subscript error occurs at line PDXDDX+34.\n \n To correct this problem, additional checks have been added to ensure\n a correct domain entry is located.\n\n
\n The Pharmacy Prescription Practices (PPP) software relies on patient\n visit information provided quarterly by the Minimal Patient Dataset\n (MPD) CD-ROM. This CD is no longer distributed to facilities.\n To ensure the continuing functionality of PPP, the method of acquiring\n patient visit history information must be changed. This enhancement\n updates the PPP software to use the Master Patient Index/Patient\n Demographics (MPI/PD) package files as the source of data. \n The MPI/PD package stores the same information required by PPP in the\n TREATING FACILITY LIST (#391.91) file.\n\n
\nThis patch will modify the routine that does the daily update to the PPP \nFOREIGN FACILITY XREF file (PPP(1020.2)).\nThis patch will also update the file description for file 1020.2.\n\n
\nThis patch updates the domain names in the Pharmacy Prescription Practice\n(PPP) files. The files are: \n \nPPP DOMAIN XREF (#1020.8) & PPP CONVERSION SITE (#1020.128)\n\n
\n This patch corrects the problem of using the incorrect IEN (Internal\n Entry Number) for the institution.\n\n
\nPPPBLD1A CHANGE VAR I TO PPPI TO PREVENT POSS UNDEF ERROR\n \nPPPMPI MODIFY PPP BUILD FFX TO PREVENT DUPLICATE ENTRIES\n \nPPPMPI UPDATE DATE OF LAST AUTO BUILD\n \nPPPSCN2 MODIFY ROUTINE TO LOOK AT THE FILE 44.003 MULTIPLE INSTEAD OF \nJUST THE FIRST ENTRY\n\n
\nAll options within the Pharmacy Prescription Practices (PPP) \napplication will be marked Out Of Order, with the message \nOPTION RETIRED BY PATCH PPP*1*43 AS PER PSI-07-114. \nAdditionally, the Outpatient Pharmacy application and AudioFax\nwill be modified to ignore all calls to the PPP applications.\n\n
\nThe FY09 Q4 Enhancement Release includes the retirement of the Pharmacy\n1. The following PPP options will be removed.\n PPP (EDIT) PARAMETER PPP MAIN\n PPP BACKGROUND PURGE LOGFILE PPP MERGED SITE EDIT\n PPP BACKGROUND PURGE XREF PPP PRINT CLINIC PROFILES\n PPP BATCH PPP PRINT FFX\n PPP BUILD FFX PPP PRINT LOG\n PPP DISPLAY FOREIGN VISITS PPP PRINT STATISTICS\n PPP EDIT DOMAIN PPP PURGE LOGFILE\n PPP EDIT FFX PPP PURGE LOGFILE MENU\n PPP INIT PURGE LOGFILE JOB PPP PURGE XREF MENU\nPrescription Practices (PPP) V. 1.0 package. This is a follow-up patch for\n PPP INIT PURGE XREF JOB PPP XREF PURGE\n PPP INIT STAT\n \n2. The PPP input template, PPP EDIT FILE, will be removed.\n \n3. The PPP sort template, PPP LOGS, will be removed.\n \n4. The following PPP list templates will be removed.\n PPP FFX DISPLAY PPP LOG DISPL PPP PROFILE PPP VISITS\n PPP FFX REPORTS PPP PRINT PPP UNRESOLVED DOM PPP XREF EDIT\nthe nationally released patch PPP*1*43 to resolve Patient Safety Issue\n \n5. The following PPP print templates will be removed.\n PPP CODE LIST PPP LOGP\n PPP LOG PPPSTAP\n \n6. The following PPP protocols will be removed.\n PPP (MENU) DOM PPP ADD FF ENTRY PPP DEL FF ENTRY PPP EDIT FF ENTRY\n PPP (MENU) FF XREF PPP CHANGE ALL DOM PPP DISPL BOTH\n PPP (MENU) VISITS PPP CHANGE DOM PPP DISPL OTHER\n \nPSI-07-114. Per PSI-07-114, the PPP package does not provide the most\n7. The PPP security key, PPP UTIL, will be removed.\n \n8. All PPP standard routines will be removed. If after the patch is installed\n there are still routines starting with PPP then the site will be\n responsible for reviewing and deleting those routines.\n \n9. The following PPP files and data will be removed.\n PPP PARAMETER File #1020.1 PPP EXCLUSION File #1020.5\n PPP CONVERSION SITE File #1020.128 PPP CODE File #1020.6\n PPP FOREIGN FACILITY XREF File #1020.2 PPP NEW SSN File #1020.7\nrecent and up-to-date data on prescriptions from other sites. Patch\n PPP STATISTIC File #1020.3 PPP DOMAIN XREF File #1020.8\n PPP LOG File #1020.4\n \n10. A background job will be tasked when the patch is installed to remove\n the PPP files and data. Upon completion of the job, a MailMan message\n with the subject "PPP Package Data & Data Dictionary Removal" is\n generated showing a list of files that were deleted. If there are\n routines that begin with PPP that were not removed, then they will be\n listed in the message. These routines will need to be reviewed by IRM\n to determine if they should be removed.\nPPP*1*43 made the PPP options unavailable by marking them as 'Out of\n\nOrder'. This patch, PPP*1*44, will remove every component (see list below)\nof the PPP package from sites.\n \n\n
\nPrior to the final release of patch PPP*1.0*11, a Quit statement was inserted\ninto the routine while checking problems associated with the CD-Rom server.\nThis line was left in the program by mistake.\n\n
\nThis patch using KIDS will install the changes necessary in routine\nPPPSCN2, to correct the problem of PDX requests being made daily on the\nsame patients. \n \n\n
\n This patch addresses the problems associated with entries in the \n INSTITUTION file (#4) not being dinummed.\n\n
\n This patch corrects a problem of when more than one patient's information \n now displayed indicating if there are any differences in the patient's \n profile.\n was requested in the Display Visits to other Facilities\n [PPP DISPLAY FOREIGN VISITS] option. \n \n A temporary global was still intact after each patient which would \n display the previous patient's data along with the current patient. \n \n This also contributed to the problem of more than one patients' data \n being returned on the PPP -Medication Profiles. Warning messages are \n\n
\nPatch 8 had a routine that was looking into the wrong file for a new\ndomain name.\nAlso, the new look-up to get a station number from the PPP DOMAIN XREF\nfile (#1020.8), does not accept entries that have changed their station\nnumbers. Since this file is a pointer to the INSTITUTIONN file (#4), the\nnon-dinummed entries can not be located. Therefore we are changing the call\nback to the INSTITUTION file (#4).\n\n
\n Patch PPP*1*11 which reduced the amount of time it takes to extract the\n A new field has been added to the PPP DOMAIN XREF file (#1020.8), this\n field is called STATION NUMBER (#12). Currently the STATION field (.01)\n within this file is a pointer to the INSTITUTION file (#4). With the\n entries in the INSTITUTION file being changed sometimes, this new field\n will be the basis for collecting the proper data from the CD-ROM.\n CD-ROM patient data and build the PPP FOREIGN FACILITY X-REF file \n (#1020.2), did not allow non-domain associated entries, therefore, when\n the PPP EDIT DOMAIN [Edit Unresolved Domain Entries] option is executed,\n no entries can be found.\n \n This patch to that process will allow the entries without an associated\n domain to be entered into the file.\n \n\n
\nThis patch provides more information to the error messages sent to\nof entries for 300,000 plus patients took too much system time.\n \n20JAN99 - the routine PPPGET3 had a coding mistake in it, that asked\nfor a code check to be done if the value of the variable was null. The\ncheck should have been in place to check if the variable was NOT null.\nthe user informing them of missing information about patients.\n \nAlso, the date of the last build is now stored in the PPP Parameter file\n(#1020.1), and a call to EN^DIQ1 was added to the functionality of routine\nPPPGET1.\n \nProblems with the purge option not running to completion have been \nre-programmed to execute faster. The previous use of Fileman deletion\n\n
\n1). Currently there are problems being reported with facilities trying \nThe new method will transmit several hundred entries at a time. In this \nmanner, File #1020.2, can be built a little at a time. \n \n2). When a new patient is entered, a MUMPS cross-reference is \nexecuted which calls a PPP routine that adds the patient to PPP. \nPPP then tries to find any visits to other facilities by trying to access \nthe MPD CD-ROM. If access cannot be obtained, an error bulletin is \ngenerated. \n \nSince the Prescription Practices Daily Batch Routine [PPP BATCH] option \nto create the FOREIGN FACILITY CROSS REFERENCE file (#1020.2). The \nis scheduled to run nightly to gather new patient data, the action taken \nby the SOCIAL SECURITY NUMBER (#.09) field's cross-reference is not \nneeded.\nproblem cannot be traced to either Pharmacy Prescription Practices or \nMinimal Patient Dataset. The current process of extracting the Pharmacy \nPrescription Practices data from the Minimal Patient Dataset CD-ROM \nconsists of transmitting all the selected social security numbers to the \nCD-ROM, and then waiting for the visit data on each to be re-collected by\nthe PPP program before the file can be built. \n \n\n
\nThe Pharmacy Prescription Practices Package is a set of routines for\ndetermining whether a patient has visited other VAMC's and the making\nthe prescription data from those facilities aviable to the local\npharmacist\n\n
\nDietetics Version 5.0 patch 4 Assessment and Patient Movements.\n\n
\nPatient Movement Report with Multi-Divisional Format.\n\n
\nRefer to the patch for the patch description.\n\n
\nRefer to the patch for the patch description.\n\n
\nRefer to the Patch Description.\n\n
\nThis patch updates the Dietetics System to interact with Order Entry\nThe protocol FHW6 Dietetic Consult will not be converted when OE/RR version \nProtocol FHWD1 Removed \nProtocol FHWMENU Removed \nProtocol FHWD8 Removed \nProtocol FHWD5 Removed \nProtocol FHWD22-10 Removed \n...Done \n\nONLY protocol FHWMAS will not be removed since it is used to keep track of\npatient movement. \n \n3 (CPRS) is installed. Dietetic Consults should be entered through the \nFIELDS: COMMENT (#11) in multiple 115.02 DIET\n ORDER (#2) in multiple 115.06 ADDITIONAL ORDERS\n COMMENT (#4) in multiple 115.04 TUBEFEEDING\n \nThe fields listed above in the Dietetics Patient file (#115) have been\nexpanded to free text of 80 characters. \n \nAfter the installation of patch 6, the Dietetics program will NO LONGER\nresume to a previous order after the expiration of a current order or \nfuture order. Instead, the program will create a new diet entry of the \nConsult/Request Tracking package when OE/RR 3.0 is released. \norder that needs to be reinstated. When the diet expires, the \nnew diet will kick in. Nothing is changed when the patient is return from\nPASS. The patient will still reinstate to his previous order. \n \nTEST SITES \n========== \nTuscaloosa \nWest Palm Beach \nPuget Sound \nWashington D.C. \n \nSan Francisco \nHuntington \nCentral Texas \n \n \nROUTINE SUMMARY \n=============== \nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like: \n \nAfter the install, a list of 8 routines will be deleted from the\n<tab>;;5.0;Dietetics;**[PATCH LIST]**;Oct 11, 1995 \n \n CHECK^XTSUMBLD results \n \nRoutine Name Before Patch After Patch Patch List \n------------ ------------ ----------- ---------- \nFHDPA 2974151 1959545 **6** \nFHIPST N/A 923839 **6** \nFHORC 4988961 4006909 **6** \nFHORC2 10784717 10179247 **6**\nsite. The routines are Order Entry 2.5 interface routines. They\nFHORD1 12718924 13165679 **6** \nFHORD1A 3630323 3661703 **6** \nFHORD3 6474710 6395020 **6** \nFHORD4 5320132 5231133 **6**\nFHORD6 10892533 10811056 **9,6**\nFHORD7 5750796 7103314 **2,6**\nFHORD71 8011723 10859213 **2,6**\nFHORE1 11602421 10956577 **6** \nFHORE1A 2003255 1869226 **6** \nFHORE3 3649653 4078237 **6**\nare the following:\nFHORO 4704498 3888421 **6** \nFHORR N/A 3571821 **6** \nFHORT1 11898568 10477131 **5,6**\nFHORT11 2453906 2373866 **6** \nFHORT2 5921412 6979478 **6** \nFHWADM 6490259 6908161 **5,6** \nFHWDIS 5856773 8590885 **2,6** \nFHWDISD 3992628 3137098 **6** \nFHWMAS 1763412 1625899 **6** \nFHWOR N/A 11862846 **6** \n FHORDW \nFHWOR1 N/A 2249707 **6** \nFHWOR2 N/A 7638368 **6** \nFHWOR3 N/A 10700061 **6** \nFHWOR31 N/A 2280789 **6** \nFHWOR4 N/A 5826883 **6** \nFHWOR5 N/A 9027404 **6** \nFHWOR51 N/A 5518246 **6** \nFHWOR5R N/A 3603229 **6** \nFHWOR61 N/A 5105507 **6** \nFHWOR7 N/A 3350164 **6** \n FHORDW1 \nFHWOR71 N/A 15740887 **6** \nFHWOR72 N/A 10002638 **6** \nFHWOR8 N/A 508002 **6** \nFHWORA N/A 6968295 **6** \nFHWORA1 N/A 11692302 **6** \nFHWORP N/A 4094683 **6** \nFHWORR N/A 4548809 **6** \nFHXOR3 8083732 8083732 **12,6** \nFHXUTL N/A 5306970 **6** \n \n FHORDW2 \nGENERAL INFORMATION\n=================== \nDO NOT NEED TO BE INSTALLED. When Order Entry Version 3.0 (CPRS) is \ninstalled, this patch will be installed along with it. Install this\npatch ONLY if your site was one of the test sites listed in the TEST\nSITES section so your site will have the final changes made in the\nDietetics routines. \n\nWhen this patch is being installed with Order Entry, it should be installed\ninto the test UCI first then the production UCI. It can be installed at\nversion 3.0 or higher.\n FHORDW3 \nanytime. Install times of this patch at the test sites were less than 15\nminutes. No Dietetics options need to be disabled. Dietetics users do\nnot need to be logged off the system. \n \nDOCUMENTATION \n============= \nThe documentation for this patch contains in detail the HL7\nmessage interface between Dietetics and Order Entry. Documentation for \nthis patch will be mailed from NCD (National Center for Documentation). \nThis shipment will contain pages the site can append in the \n FHORCW \nDietetics Version 5.0 Technical Manual. These pages are available in a \n.PDF file in the following IRM Field Offices ANONYMOUS.SOFTWARE directories. \n\n \n IRM FIELD OFFICE FTP Address\n ---------------- -----------\n Hines 152.129.1.110\n Albany 152.127.1.5\n Salt Lake 152.131.2.1\n \n FHOREW \n FILE\n ---- \n FH5_0P6.PDF \n \nAll VAMCs are encouraged to log into TCP/IP host using FTP to obtain it.\nThe .PDF file can be read on a PC using the Adobe Acrobat Reader browser\nprogram. The .PDF file is a BINary file, so you must make sure\nwhen using the file transfer, to enter the appropriate command for BINary\nfile transfer. \n \n FHOROW \nIf there are any questions, your supporting CIOFO Customer Service Clinical \n2 Team will address them. \n \nINSTALLATION INSTRUCTIONS \n========================= \n \nThis Patch is created with Kernel V8 KIDS. Follow these instructions: \n1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build\n onto your system. \n2) On the KIDS menu, under the 'Installation' menu, use the \n FHORTW \n option 'Verify Checksum in Transport Global' to verify that all \n routines have the correct checksums. \n3) From the 'Installation' Menu of KIDS, use the option \n 'Install Package(s)'. Select the package 'FH*5.0*6' and proceed with\n install. \n4) If you are a MSM site move the routines to the other servers. \n5) On a mapped system, rebuild your map set.\n6) Delete post-init FHIPST and FHXUTL (after running to completion).\n \nRoutine FHWWFIX will also be deleted if it wasn't deleted after FH*5*5\nwas installed. \n \nA routine, FHXUTL, can be executed by the site to clean up the Dietetics\n \n2.5 protocols after the protocols have been converted to Order Dialogs with\nthe Order Entry Version 3.\n \nThe following is a sample run: \n \nD ^FHXUTL \n \nClean up 2.5 Dietetics Protocols... \nProtocol FHWM Removed From ORADD \nProtocol FHWPRO1 Removed From OROPRO \nThis patch will be distributed with Order Entry version 3.0 (CPRS) and\nProtocol FHWMENU Removed From ORZ 39A ADMIT \nProtocol FHW1 Removed From ORZ 84D REORDER/RE-EVALUATION \nProtocol FHWD1 Removed From ORZ ADD MENU 4WEST DOC \nProtocol FHWMENU Removed From ORZ ADD MENU 4WEST DOC \nProtocol FHWD1 Removed From ORZ ADD MENU IKE2 \nProtocol FHWMENU Removed From ORZ ADD MENU IKE2 \nProtocol FHWD1 Removed From ORZ ADD MENU NHCU DOC \nProtocol FHWMENU Removed From ORZ ADD MENU NHCU DOC \nProtocol FHWD1 Removed From ORZ ADD MENU NURSE \nProtocol FHWMENU Removed From ORZ ADD MENU NURSE \nit would be installed with Order Entry Version 3.0 or higher. If your\nProtocol FHWD1 Removed From ORZ ADD MENU NURSE NHCU \nProtocol FHWMENU Removed From ORZ ADD MENU NURSE NHCU \nProtocol FHWD1 Removed From ORZ ADD ORDERS DETOX \nProtocol FHWMENU Removed From ORZ ADD ORDERS DETOX \nProtocol FHWN1 Removed From ORZ ADD ORDERS WARD CLERK \nProtocol FHWN2 Removed From ORZ ADD ORDERS WARD CLERK \nProtocol FHWD1 Removed From ORZ ADD ORDERS WARD CLERK \nProtocol FHWMENU Removed From ORZ ADD ORDERS WARD CLERK \nProtocol FHWD5 Removed From ORZ ADD ORDERS WARD CLERK \nProtocol FHWN1 Removed From ORZ ADD ORDERS WARD CLERK NHCU \nsite is a test site of Order Entry 3.0 (CPRS) that is listed in the TEST\nProtocol FHWN2 Removed From ORZ ADD ORDERS WARD CLERK NHCU \nProtocol FHWD1 Removed From ORZ ADD ORDERS WARD CLERK NHCU \nProtocol FHWMENU Removed From ORZ ADD ORDERS WARD CLERK NHCU \nProtocol FHWD5 Removed From ORZ ADD ORDERS WARD CLERK NHCU \nProtocol FHWD1 Removed From ORZ DETOX ADMIT ORDERS \nProtocol FHW7 Removed From ORZ NHCU ADMISSION ORDERS \nProtocol FHWMENU Removed From ORZ NHCU ADMISSION ORDERS \nProtocol FHW1 Removed From FHWM \nProtocol FHW2 Removed From FHWM \nProtocol FHW3 Removed From FHWM \nSITES section, please install this patch so your site will have all the\nProtocol FHW4 Removed From FHWM \nProtocol FHW5 Removed From FHWM \nProtocol FHW6 Removed From FHWM \nProtocol FHW7 Removed From FHWM \nProtocol FHW8 Removed From FHWM \nProtocol FHW1 Removed From FHWMENU \nProtocol FHW2 Removed From FHWMENU \nProtocol FHW3 Removed From FHWMENU \nProtocol FHW4 Removed From FHWMENU \nProtocol FHW6 Removed From FHWMENU \nfinal changes made in the Dietetics routines. \nProtocol FHW7 Removed From FHWMENU \nProtocol FHW8 Removed From FHWMENU \nProtocol FHWN1 Removed From FHWMENU \nProtocol FHWN2 Removed From FHWMENU \nProtocol FHWD1 Removed From FHWMENU \nProtocol FHWD8 Removed From FHWMENU \nProtocol FHWD5 Removed From FHWMENU \nProtocol FHWD22-10 Removed From FHWMENU \nProtocol FHW1 Removed \nProtocol FHW2 Removed \n \nProtocol FHW3 Removed \nProtocol FHW4 Removed \nProtocol FHW5 Removed \nProtocol FHW6 Removed \nProtocol FHW7 Removed \nProtocol FHW8 Removed \nProtocol FHWM Removed \nProtocol FHWPRO1 Removed \nProtocol FHWN1 Removed \nProtocol FHWN2 Removed \n\n
\nRefer to the Patch Description.\n\n
\nThis is Dietetics Patch 5.\n\n
\nThis patch corrects a help prompt which indicates that certain\ntwo-digit date entries are valid when actually they are not valid\nin the year 2000 and beyond.\n\n
\nLAB TEST ORDER AND DIET PATTERN RELATED UPDATES.\nPlease see the detailed description of FH*5.0*30 on FORUM.\n\n
\nThis is Dietetics Version 5.0 Patch 7.\n\n
\nDietetics Patch 38.\n\n
\nPatch FH*5.0*40\n\n
\nThis is Patch 8 of Dietetics Version 5.\n\n
\nTHIS PATCH ADDRESSES FOUR DIETETIC NOIS MESSAGES AND TWO E3Rs.\n\n
\nChange second line in FHPATM and FHSEL1.\n \n*** MAKE SURE PATCH 9 IS LOADED! ***\n\n
\nPatch to display Dietitians name who entered Nutritional Assessment.\n\n
\nThis patch is the Dietetics portion of the Order Entry 3.0 (CPRS Version 1)\nThis routine is a post-init routine which will add three Dietetics protocols\n option 'Verify Checksum in Transport Global' and verify that all \n routines have the correct checksums. \n3) From the 'Installation' Menu of KIDS, use the option \n 'Install Package(s)'. Select the package 'FH*5.0*12' and proceed with\n install. \n4) On a mapped system, rebuild your map set.\nto the Protocol file (#101). They are the following:\n \nFH EVSEND OR \nFH RECEIVE \nFH ORDERABLE ITEM UPDATE \n \nROUTINE: FHORD, FHORT3, FHWORI, and FHWOR6 \n \nRoutine FHWORI, that does the initial population of the Orderable Items, \npre-install. It contains five routines, FHORD, FHORT3, FHWORI, FHWOR6, and \nwill be executed in a post-init routine in patch 49, OR*2.5*49, of Order\nEntry version 2.5. Routines FHORD, FHORT3, and FHWOR6 have the changes\nthat will update the Orderable Items in file (#101.43). \n \nYou can install this patch and the routines will not effect the current \nsystem of Dietetics or Order Entry. There will be no Orderable Item file \npopulation or update until patch OR*2.5*49 is installed. \n \nTest Sites \n========== \nFHXOR3. These routines will be used to populate, and update Order Entry's\n \nTuscaloosa\nWest Palm Beach\nPuget Sound,\nWashington D.C.\n \n \nRoutine Summary \n=============== \n \nOrderable Item file (#101.43) with the Diet and Tubefeeding entries from \nThe following routines are included in this patch. The second line of \nthese routines should look like: \n \n<tab>;;5.0;Dietetics;**[patch list]**;Oct 11, 1995 \n \n CHECK^XTSUMBLD results \n \nRoutine Name Before Patch After Patch Patch List \n------------ ------------ ----------- ---------- \nFHORD 1618989 3227945 **12** \nthe Diet file (#111) and the Tubefeeding file (#118.2). \nFHORT3 2509939 3722308 **12** \nFHWOR6 N/A 6435773 **12**\nFHWORI N/A 3970884 **12** \nFHXOR3 N/A 8083732 **12** \n \nGeneral Information \n=================== \n \nThis patch should be installed into your test UCI then your production UCI.\nThe install time should not take more than 10 minutes. No options need to \n \nbe disabled. Users do not need to be off the system. \n \n \n \nDocumentation \n============= \n \nThe documentation for this patch contains in detail the Orderable Item HL7\nmessage interface between Dietetics and Order Entry. Documentation for \nthis patch will be mailed from NCD (National Center for Documentation). \n \nThis shipment will contain pages the site can append in the \nDietetics Version 5.0 Technical Manual. These pages are available in a .PDF\nfile in the following IRM Field Offices ANONYMOUS.SOFTWARE directories. \n \n IRM FIELD OFFICE FTP Address\n ---------------- -----------\n Hines 152.129.1.110\n Albany 152.127.1.5\n Salt Lake 152.131.2.1\n \nROUTINE: FHXOR3\n FILE\n ---- \n FH5_0P12.PDF \n \nAll VAMCs are encouraged to log into TCP/IP host using FTP to obtain it.\nThe .PDF file can be read on a PC using the Adobe Acrobat Reader browser\nprogram. The .PDF file is a BINary file, so you must make sure\nwhen using the file transfer, to enter the appropriate command for BINary\nfile transfer. \n \n \nIf there are any questions, your supporting CIOFO Customer Service\nClinical 2 team will address them. \n \nInstallation Instructions \n========================= \n \nThis Patch is created with Kernel V8 KIDS. Follow these instructions: \n1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build\n onto your system. \n2) On the KIDS menu, under the 'Installation' menu, use the \n\n
\nRefer to the patch for the patch description.\n\n
\nAddresses issues with two reports and a bad cross index in the FOOD \nand will display for the currently selected outpatient. This was an issue \nhidden by the first problem of the incomplete display.\n \nHD0000000188896 - Error in FHASP1\nIt is possiable for a patient to have a food preference without a meal \nassociated with it. When the report option Print Nutrition Profile is run \nfor a patient with a food preference without an associated meal the \nroutine called by this option, FHASP1, will error out.\n \nHD0000000202836 - REPLETE WITH FIBER is INACTIVE\nNUTRIENTS file of the Nurtition and Food Service package\nThe cross reference for field # 99, INACTIVE?, in file # 112, FOOD \nNUTRIENTS, is incorrect. It is intended to kill the node ^FHNU(DA,"I") if \nthe user selectes N for no or deletes the stored value. It is written to \nkill node ^FH(112,DA,"I"). This is a node that is never created. So \nnothing is killed. Since node ^FHNU(DA,"I") continues to exist the \nrecord will remain flagged as inactive.\n \nHD0000000152560 - CPRS Dietetics Profile does not jive\nWhen a CPRS user has selected an outpatient and decideds to view the \npatient's dietetics profile, the food preferences listed are incomplete. \nAdditional issue found during SQA. When a CPRS user selected several \noutpatients during a ongoing session the food preferences listed contains \nall the food preferences for all of the previously selected outpatient \n\n
\nFOOD PREF TO ALLERGY FLDS/REMOVE PRIOR CLINICIAN FLD\n\n
\nADDRESSES ISSUES WITH TWO REPORTS AND ALLERGY MAPPING\n \nHD0000000198141 - Supplemental Feeding Labels Ingred List\nHD0000000229391 - FGH - MAPPING ALLERGIES\nHD0000000231873 - User is prompted for a date entry that is being rejected\n\n
\nThis build is to address issues realted to the release of FH*5.5*8. Fixes \nto problems with the Nutritional Assessment and its interface wtih TIU.\n\n
\nRoutine FHDSSAPI is returning too many records. These excess records are \ninvalid and leading to poor and incorrect results by DSS processing. This \npatch modifies routine FHDSSAPI to provide additional record filtering to \nthe extract.\n\n
\nGeneral purpose NUTRITION AND FOOD SERVICE patch.\n \nThe statement in the Inpatient Nutritional Assessment of "No laboratory \ndata available last XXX days" was not being saved to TIU.\n \nThe patient lookup for the Nutrition and Food Service package will first \nattempt to find a match in the PATIENT file, # 200. If no match is found \nor accepted by the user the lookup will attempt to find a match in the \nNEW PERSON file, # 2. It does this without alerting the user it has \nswitch files during the look up.\n \n \nXINDEX found a SAC violation of a lock command without a timeout in \nroutine FHSPED.\nThis patch addresses the folowing issues:\n \nThe Diet Order List not printing a complete list of patients when \nselected to print alphabeticly and in some rare cases by room number.\n \nThe option Standing Order Inquiry option [FHSP4] wound encounter a \nsubscript error on some patients that force the user out of VistA.\n\n
\nThis addresses general issues with the Nutrition and Food Service package.\n\n
\nFIXES A DIVIDE BY ZERO ERROR\n\n
\nUPDATE FOOD ALLERGIES IN ROUINTE FHSELA2\n\n
\nTHE PATCH ADDRESSES ISSUE WITH THE TICKLER FILE ROUTINES.\n\n
\nADDRESSES GENERAL NUTRITION AND FOOD SERVICE ISSUES\n\n
\nFood items with miss-spelled allergies not mapping properly.\nAdding corrected allergy spellings to FHSELA2:\nIn FHSELA2 In GMR ALLERGIES FILE\nBARBEQUE SAUCE BARBECUE SAUCE\nEGG, SUBSTITUTES EGG SUBSTITUTES\n\n
\nGENERAL BUG FIXES\n\n
\nThis patch addresses the following issues:\n3. A nutrition location with the Send Alerts option enabled for the \nmonitors will use the routine FHWTRN to send alerts to the clinicians \nwhen a patient has been tranfered from another nutrition location and \nthat patient has monitors filed. Routine FHWTRN was not updated with \npatch FH*5.5*8 to properly use the multivalued CLINICIAN(S) field (# 112).\nThe results in alerts being send to the incorrect clinican and to the \ncorrect clinican, but in the name of the incorrect clinican.\n1. Nursing home patients with an ASIH episode, the tickler appears to \nstop working for them.\n \n2. The List Inpats By Nutrition Status Level [FHASNR4] report option when \nrun and the sorting is done by CLINICIAN is using the old CLINICIAN field\n(field #1) rather than the new CLINICIAN(S) field (field #112). This\ncauses the report to produce incorrect information.\n \n\n
\nAddressing issues from Patch FH*5.5*24\n\n
\nTransferring an inpatient to a nutrition location with more than one\nclinician assigned to it will generate an undefined error when filing a\ntickler for the second clinician assigned to that nutrition location. \nThis error will force the user out of VistA.\n\n
\nChanges to Meal Production report as part of the Advance Food Prep.\n\n
\nAdding KIDNEY BEANS and OCTOPUS to "Create/Map Food Preferences to \nAllergies" [FHSELA] option for mapping.\n\n
\nThis patch will address the following issues:\n1. When printing the Patient Profile [FHORD9] for an inpatient the \npatient's sex will not print or it will print what looks to be part of \nthe raw global data stored for the patient in the PATIENT file (#2).\n\n
\nIssues addresed:\n1. UNDEFINED VARIABLE ERROR IN FHSELA1\n2. FOOD PREFERENCES WITHOUT ASSOCIATED MEAL DO NOT DISPLAY IN PATIENT \nPREFERENCES\n\n
\nTHE FOOD ALLERGY INDICATOR OF *ALG IS NOT PRINTING IN THE LASER LABELS.\n\n
\nNEED TO ADD SAGE TO ROUTINE FHSELA2\n\n
\nThis patch addresses the following issues:\n1. When the user decides to sort the Nutrition Status Average Report by \nthe Clinician, the report is using the CLINICIAN (# 1) field rather than\nthe CLINICIAN(S) (# 112) of the NUTRITION LOCATION (# 119.6) file.\n \n2. Routine FHASN71 will be updated to include Integration Agreements in \nits comments section.\n\n
\nPSPO 1380 CHANGES NEEDED DUE TO NTRT\n \nThis patch addresses the following issue(s):\n \n1. Recent NTRT pushes have added new food, food/drug allergies to the GMR\nALLERGIES file (#120.82). These new food allergies will not be presented\nto the user in the N&FS menu option Create/Map Food Preference to\nAllergies [FHSELA]. This is part of an ongoing Patient Safety issue PSPO \n1380. This patch is an incremental fix for PSPO #1380.\n\n
\nIn the patient's list of food preferences for options Enter/Edit Patient \nPreferences [FHSEL3] and Display Patient Preferences [FHSEL4] food \nprefernces without an associated meal with no indicator they have this \nproblem. Sites are not able to determine easily which food preferences \ndid not have an associated meal in order to fix them in the Enter/Edit\nPatient Preferences [FHSEL3].\n\n
\nThis patch addresses the following issue:\nThis is part of an ongoing Patient Safety issue PSPO 1380. This patch is\nan incremental fix for PSPO #1380.\nPSPO 1380 changes needed due to NTRT\n \n1. A recent NTRT push have added a new food allergy to and updated two \nexisting food, food/drug allergies in the GMR ALLERGIES file (#120.82).\nThe new food allergy is PAWPAW. The updated food allergies are MULBERRY\nand MOLASSESS. Review of the routine FHSELA2 found that none of\nthese allergies are in its code and will not be presented to the user\nin the N&FS menu option Create/Map Food Preference to Allergies [FHSELA].\n\n
\n1. Adding Food Allergy SORBITOL to routine FHSLEA2.\n \n2. Modifing allergy type food prefernce IODINE data line in routine \nFHSELA2 to include GMR ALLERGY IODINE for mapping.\n\n
\nThis patch will address the following issues:\n1. Adding Food/Food Drug allergies MALTITOL, MANNITOL, and XYLITOL to \nFHSELA2.\n2. Incremental Locks missing timeouts in routines FHNO5, FHORD7, and \nFHORD72.\n \n3. Adding Food/Food Drug allergy SASSAFRAS to FHSELA2.\n\n
\nThis patch will address the following issueS:\n1. Adding Food, Drug/Food allergies BAY LEAVES, CARAWAY SEEDS, and\n FRUTOSE to FHSELA2.\n2. The Supplemental Feeding for a diet order was not being discontinued \n when a the diet order changed at a schuduled date/time.\n\n
\nTHIS PATCH WILL UPDATE FHSELA2 TO INCLUDE THE NEW FOOD ALLERGY OF BEAN \nSPROUTS.\n\n
\nThis build will add ARROWROOT as a new item available for mapping in food \npreferences.\n\n
\nThe New Term Rapid Turnaround (NTRT) Allergy team has recently added \nDAIRY FOODS,FRESH FRUITS,FRUITS,MINT HERB,PEPPERMINT HERB,PEPPERMINT\nOIL,RABBIT MEAT as a food allergy allergies to the GMR ALLERGIES file \n(#120.82). This new food allergy must be added to the routine FHSELA2 \nin order to be mapped as allergy type food preference dislikes in the \nDietetics package.\n\n
\nDIETETICS\n\n
\nAdding new allergy type food dislike preferences to FHSELA2.\n\n
\nThis patch will address the issue of INC3751127:\nThe IA for Adverse Reaction API GMRADPT is missing from routine FHCLN. \nRoutine FHCLN is using an obsolete API call for Adverse Recation API\nGMRADPT.\n\n
\nThis patch will address the addition of a new Drug/Food allergy by adding \nCHRYSANTHEMUM to the mapping capability for food preference dislikes.\n\n
\nThis patch will address the following issues;\n1. It will add RAW APPLES and RAW CHERRIES to the Create/Map Food\nPrefernces to Allergies option.\n \n2. It will correct an <UNDEFINED> variable error in routine FHOMPG1 when \nthe user up arrows out of selecting either a Production Facility or \nCommunication Office.\n\n
\nThis patch addresses the following issue:\n1. INC22357619- ALERT FOR WRONG PATIENT DISPLAYS WHEN ACCESSING VIEW \nALERTS\n \nAssociated NSR(s):\n==================\nN/A\n \nParticipating Test Sites:\n=========================\nTBD\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n===========================================\n \n \n1. INC22357619 - ALERT FOR WRONG PATIENT DISPLAYS IN VIEW ALERTS\n \n Problem:\n -------\nALERT FOR WRONG PATIENT DISPLAYS WHEN ACCESSING VIEW ALERTS \nAlert for wrong patient displayed when accessing View Alerts and an alert \ndisplayed for a different patient when using View Alert. This issue was \nreviewed by the Kernel team and their findings were that the application \nis creating an incorrect Package identifier (four comma pieces instead of \nthree), so that when the application processes the alert, the patient id \nor notification id are incorrectly referenced. This was found to be due \nto the Package identifier being created using $H which itself contains a \ncomma.\n \n Resolution:\n \n ----------\nThe use of $H to create the Package identifier does allow the creation of \na unique identifier but causes problems due to the extra comma. This \npatch will modify FH routines to modify the package id sent to kernel to \nconform with kernel documentation. Kernel 8.0 & Kernel Toolkit 7.3\nDeveloper's Guide documents the package id as follows:\nParagraph 3.2.1 - The software application identifier for an alert is \ndefined as the original value of the XQAID input variable when the alert \nis created via the SETUP^XQALERT: Send Alerts API. Typically, the \nsoftware application identifier should begin with the software \n \napplication namespace.\nParagraph 3.3 - The Computerized Patient Record System (CPRS) software \nuses a convention for the format of the software application identifier \nconsisting of three comma-delimited pieces:\nnamespace_","_dfn_","_notificationcode\nWhere:\n - namespace is the software application namespace.\n - dfn is the internal entry number of the patient whom the alert \n concerns in the PATIENT (#2) file.\n - notificationcode is a code maintained by the CPRS software \n \n describing the type of alert.\n \nPrior to this patch the XQAID variable passed to kernel was created as \n"FH,"_$J_","_$H ($J is the vista job# for the task & $H is mumps \ndate/time)\n \n \n Technical Resolution:\n --------------------\nThe setting of XQAID in routines ALRT^FHCTF5, ALRT^FHASM2A, PHA^FHASM2A \nAssociated ticket(s):\nand FIL^FHWTRN is changed to use the patient's DFN as the 2nd comma piece \nand a number identifying the FH alert type in the 3rd piece.\n \n"FH,"_DFN_","_TYPE\n \nThe types are as follows\n1 = Food/drug interaction alert\n2 = Nutrition Patient assessment alert\n3 = Monitor BMI alert\n4 = Monitor Tubefeed alert\n=====================\n5 = Monitor Hyperals alert\n6 = Monitor Albumin alert\n7 = Monitor NPO+Clr alert\n \nThe TYPE is set into the variable FHCODE in routines FHWTRN & FHCTF5 for \neach type of alert.\nDuring analysis it was also found that routines FHWTRN & FHCTF5 were \npassing in FHCTF2 as the entry point for processing the alert but did not \ninclude a routine name for processing, therefore the alert is deleted \nwhich I believe is correct because these alerts I believe are meant to be \n \ninformational. Setting an entry point should not have been done and both \nentry point and routine should not be set. \n \nThis patch comments out the code S XQAOPT="FHCTF2" at FIL+11^FHWTRN and \nALRT+9^FHCTF5.\n\n
\nTickler file modifications and Lab/Pharmacy APIs\n\n
\nA patch for outpatient standing orders, supplemental feeding\nand other fixes.\n\n
\nBAGGED MEALS SETTING/VARIABLE CLEANUP\n\n
\nOUTPATIENT MEALS\n\n
\nThe changes included in this patch are described in the description\nof patch DVB*4*28 in the National Patch Module.\n\n
\nThis patch corrects the problem that HINQ requestor information doesn't\nget updated when making HINQ inquiries using [Individual HINQ Request].\n\n
\nCorrect the Null subscript error after processing the HINQ\n\n
\nModify HINQ routines to reflect the new VBA schedule.\n\n
\nTwo codes will be added/updated via a post install utility.\n\n
\nUpgrading to Cache 4.1.x created a problem when the I/O device is not \ndefined.\n\n
\nErrors occur when processing INDIVIDUAL HINQ'S, VIEWING ALERTS, AND \nPRINTING THE HINQ SUSPENSE FILE.\n\n
\nTHIS PATCH WILL UPDATE THE DISABILITY CONDITION FILE(#31)\n\n
\nThis patch updates the Disability Condition file (#31), adding new codes\nand modifying names and descriptions of others. See NPM for complete\ndescription.\n\n
\n \nUpdate the Disability Condition file (#31).\n\n
\nHINQ Errors - Missing or Invalid Data\n\n
\nAdding a Power of Attorney line to HINQ requests\n\n
\nPlease refer to patch DVB*4.0*58 in the National Patch Module for a\ncomplete description of this patch.\n\n
\nMap diagnosis code to the Disability Condition File\n\n
\nUSERS RECEIVING ALERTS NOT REQUESTED / A&A ELIGIBILITY\n\n
\nSee Patch Description in National Patch Module for DVB*4*30.\n\n
\n-Corrects a file full error.\n\n
\nAdd ICD9 code mapping to the DISABILITY CONDITION (#31) file.\n\n
\nUpdate ICD9 code mappings in the DISABILITY CONDITION (#31) file. \n\n
\nPatch for VBA Data Sharing update.\n \nSee the Patch Description for DVB*4.0*65 as documented in the Forum Patch \nModule.\n\n
\nHINQ changes for the Military Service Data Sharing (MSDS) project\n\n
\nPatch DVB*4*67 adds 1 new disability code in the DISABILITY CONDITION \n(#31) file.\n\n
\nThis patch updates the DISABILITY CONDITION (#31) file with seventeen\nnew disability conditions.\n\n
\nPatch DVB*4.0*70 adds 18 diagnostic codes to the DISABILITY CONDITION \n(#31) file per the request of the Veterans Benefit Administration (VBA).\n\n
\nDVB*4.0*71 Disables ability to submit Hospital Inquiry (HINQ) requests in \nsupport of WebHINQ.\n\n
\nDVB*4.0*31\nRevisions for Y2K.\n\n
\nClean up outstanding NOIS issues.\n\n
\nThis install converts HINQ to use IP routing for connection to remote RDPCs.\n \nAfter the KIDS build is loaded, the environment routine DVBH4033 may also\nbe used as a diagnostic routine. It is a copy of the updated DVBHQDX \nroutine included in the build. D ^XUP before using DVBH4033 as a diagnostic\nroutine. \n\n
\nThis install should reduce READ and ENDOFFILE errors and trap them\nat Cache, OpenM sites. These errors occur after the installation of\npatch DVB*4*33, HINQ FRAME RELAY.\n \nThis install will implement TCP connections in DSM systems. The\nLAT ports, devices and the LAT/TCP gateway on the local router will no\nlonger be used. \n\n
\nThis patch corrects the incorrectly assumed EOD and RAD in the parser\nroutine of HINQ full response. The patch also adds documentation to some\nof the parser routines of the HINQ full response.\n\n
\nThis patch will display the dates in the abbreviated HINQ response without\nthe century. Once VBA sends in 4 digit years for the dates in the\nabbreviated HINQ response, a following patch will be initiated to refelect\nthe change, and have the dates in the abbreviated HINQ response displayed\nwith the century.\n\n
\nThis is the HINQ package.\n\n
\nSee National Patch Module entry for patch DVBA*2.7*6 for details on the\nchanges included in this patch.\n\n
\nUpdates for two AMIE C&P Exam worksheets - Audio and Genitourinary.\n\n
\nCorrect the worksheet number for Traumatic Brain Injury to #1240.\n\n
\nAdd temporary address to the Manual Print of new C&P requests.\n\n
\n \n \n \nPlease refer to patch DVBA*2.7*129 for a complete description of this \npatch.\n\n
\nPlease refer to patch DVBA*2.7*133 for a complete description of this \npatch.\n\n
\nAdd Exam Reference Number to the manual print of new C&P Exam requests.\n\n
\nPlease refer to patch DVBA*2.7*137 for a complete description of this \npatch.\n\n
\nPlease refer to patch DVBA*2.7*124 in the National Patch Module for a \ncomplete description of this patch.\n\n
\nUpdate to the AMIE C&P worksheet - Traumatic Brain Injury (TBI).\n\n
\nACRP Database conversion software changes patch.\n\n
\nUpdates to the AMIE C&P worksheet - Diabetes Mellitus.\n\n
\nUpdates to the AMIE Audio C&P Exam Worksheet.\n\n
\nUpdates to AMIE Scars C&P Examination worksheet.\n\n
\nPlease refer to patch DVBA*2.7*145 for a complete description of this \npatch.\n\n
\nPlease refer to patch DVBA*2.7*139 for a complete description of this \npatch.\n\n
\nThis patch allows users to use the "|" character in free text fields\nfor the 2507 requests and prevents users from accessing the VistAWeb\ntab when connecting to test accounts due to security issues. \n\n
\nUpdates to the AMIE Eye Examination C&P Exam worksheet.\n\n
\nPlease refer to patch DVBA*2.7*140 for a complete description of this \npatch.\n\n
\nPlease refer to patch DVBA*2.7*147 in the National Patch Module on Forum\nfor a complete description of the patch.\n\n
\nThis patch adds two new mail bulletins to allow messages triggered\nby CAPRI to be processed in Vista and distributed accordingly.\n\n
\nDVBA*2.7*16\nUpdate to File #396.6 and worksheets.\n\n
\nUpdates for AMIE C&P Exam worksheets Spine and Joints.\n\n
\nPlease refer to patch DVBA*2.7*142 for a complete description of this \npatch.\n\n
\nPlease refer to patch DVBA*2.7*143 for a complete description of this \npatch.\n\n
\nPlease refer to patch DVBA*2.7*151 in the National Patch Module on Forum\nfor a complete description of the patch.\n\n
\nPlease refer to patch DVBA*2.7*150 in the National Patch Module on Forum\nfor a complete description of the patch.\n\n
\nPlease refer to the patch description in the National Patch Module.\n\n
\nPlease see the Patch Description for DVBA*2.7*154 on FORUM\nfor details on this patch.\n\n
\nPlease refer to patch DVBA*2.7*159 in the National Patch Module on Forum \nfor a complete description of the patch.\n\n
\nThis patch fixes issues while compiling reports on Linux environments\nwhere the reports, when printed, are missing page breaks and removes extra\npages printed during 2507 Request print/reprints.\n\n
\nSee the patch description for DVBA*2.7*161 on the FORUM system for a more \ncomplete description of this patch.\n\n
\n See the patch description for DVBA*2.7*17 in the Patch Module on Forum.\n\n
\nPlease see FORUM for a more complete description of DVBA*2.7*149\n\n
\nPlease refer to the patch description in the National Patch Module.\n\n
\nUpdates to 3 AMIE C&P Examination worksheets: Cushing's Syndrome, \nDiabetes Mellitus and Digestive Conditions, Miscellaneous.\n\n
\nSee the FORUM Patch Module description for information on this patch.\n\n
\nSee the FORUM Patch Module description for information on this patch.\n\n
\nPlease see the National Patch Module (NPM) on FORUM for a complete\ndescription of this patch, DVBA*2.7*167.\n\n
\nDuring the New Form 7131 Request Report [DVBA NEW REQUEST], 7131\nRequests containing ADDITIONAL REMARKS (#396.05) with blank lines\ndo not print in their entirety.\n\n
\nSee the FORUM National Patch Module (NPM) for a complete description of\npatch DVBA*2.7*172\n\n
\nPlease refer the patch description on Forum for additional info on this \npatch.\n\n
\nDVBA*2.7*19\n\n
\nSee the FORUM National Patch Module (NPM) for a complete description of \nDVBA*2.7*169\n\n
\nRefer to patch description on Forum for details of this build.\n\n
\nSee the FORUM National Patch module for a complete description of this \npatch.\n\n
\nUpdates to 3 AMIE C&P Exam worksheets: Ear Disease, Eating Disorders \n(Mental Disorders) and Epilepsy and Narcolepsy.\n\n
\nSee the FORUM National Patch module for a complete description of this\npatch.\n\n
\nPlease see FORUM for a more complete description of DVBA*2.7*179.\n\n
\nPlease see FORUM for a more complete description of DVBA*2.7*181.\n\n
\nThis patch will put in place and activate updates to 15 Automated \nMedical Information Exchange (AMIE) Compensation and Pension Examination \nworksheets. \n\n
\nSee full patch description on Forum for more information.\n\n
\nSee full patch description on Forum for more information.\n\n
\nDVBA*2.7*20\n\n
\nVLER DAS BUILD - REFER TO PATCH DESCRIPTION FOR MORE INFORMATION.\n\n
\nVLER DAS BUILD 2 - REFER TO PATCH DESCRIPTION FOR MORE INFORMATION.\n\n
\nPatch DVBA*2.7*191 corrects an undefined error that occurs when queueing \na detailed report using the DVBA C INSUFFICIENT EXAM RPT option.\n\n
\nUpdates to the CAPRI file system to handle Exam Request Cancelations, \nClaim Type, Special Considerations, Insufficient Reasons, Insufficient \nRequest Y/N, and Exam cancellation free text.\n\n
\nPlease see FORUM for a more complete description of DVBA*2.7*190\n\n
\nPlease see FORUM for a complete patch description\n\n
\nThis patch will remove PRIORITY OF EXAM (#9) from the CHECK C&P \nFILE INTEGRITY [DVBA C CHECK 2507 INTEGRITY] validation logic and\nfilter inactive cancellation reasons while cancelling compensation\nand pension requests/exams.\n\n
\nThis patch fixes an issue on the Vista side that leads to a <SUBSCRIPT>\nerror which results in a "RPC DVBAB REPORTS could not be accessed!"\nerror in CAPRI when the "Re-Print C&P Final Report(s)" report is run\nby date.\n\n
\nThis patch will update the display date for reports in CAPRI to\ndisplay the report date rather than the date the report was run.\nIt also fixes several incorrect uses of the TEMP global and \nfixes formatting issues with the 7131 Requests Report.\n\n
\nWith the replacement of Vista Web in CAPRI with Joint Legacy Viewer (JLV)\nthe new JLV URL's need to be updated and accessible in Vista.\n\n
\nMaintain integrity of file #396.4.\n\n
\n This patch will address 2 issues:\n \n 1. Update routine DVBACRMS to allow printing of 21 day certificates to \n the CAPRI GUI.\n \n 2. Automate the release process of 21 day certificates.\n\n
\n \nSee FORUM patch DVBA*2.7*193 for a description of this patch.\n\n
\n This patch will address 1 issue:\n \n 1. This patch will update the AMIE EXAM (#396.6) file by changing\n 10 exam names and inactivating 55 exams.\n\n
\n This patch will address 1 issue:\n \n 1. Change CAPRI to call new LCM (formerly called Virtual VA) URLs\n\n
\n This patch will address 1 issue:\n \n 1. This patch will update the AMIE EXAM (#396.6) file by changing\n 17 exam names and inactivating 1 exam.\n\n
\nThe Separation Health Assessment (SHA) is a comprehensive medical \nhealth assessments between the two departments, VA assessments are used by\nDoD.\n \n \nPatch DVBA*2.7*209 will also fix the following issues:\n \n-2507 Request without Regional Office (RO) values\n-Copy & Paste crash issues\n-Inconsistent routing locations on 7131 requests\n-7131 requests automatically closing in AMIE\nexamination conducted by either the Veterans Affairs (VA) or Department of\n-2507 Requests not closing out properly when an exam is cancelled\n-"Validate Remote Connections" validation issues\n-Enterprise search issues with validating the "Connect To" site\n-Enterprise search allowing search with all required data\n-A delay between mouse cursor loading symbol changing back to pointer\n-Capri Gui not recognizing version control\n-GUI logger code default status change to improve performance\n-C&P exams not transferring if patient is not registered at new receiving \n site\n-DVBA C Check 2507 Integrity Report findings listing all exams\nDefense (DoD) for Separating Service Members (SSMs) who file pre-discharge\n-New C&P Divisions being set to active automatically\nclaims under the Benefits Delivery at Discharge (BDD) Program. The SHA is\nused by both the Veterans Benefits Administration (VBA) and DoD to\nevaluate a SSM's disability(ies) and determine benefits eligibility\naccording to a common standard. The VA and DoD need the ability\nto share the SHA results as soon as it they become available (on or prior \nto the Release from Active Duty [RAD] date). To avoid duplication of\n\n
\nThis patch allows the DVBA C&P SCHD EVENT protocol to be bypassed when\nFiles & Fields Associated:\nParameter Definitions:\n New/Modified/\nParameter Name Deleted \n-------------- -------------\nN/A\n \n \n \nParameter Template:\n New/Modified/\n \nTemplate Name Deleted \n------------- -------------\nN/A\n \n \n \nProtocols Associated:\n New/Modified/\nProtocol Name Deleted \n------------- -------------\nFile Name (#) New/Modified/\nN/A\n \n \n \nRemote Procedures Associated:\n New/Modified/\nRemote Procedure Name Deleted \n--------------------- -------------\nN/A\n \n Sub-file Name (#) Field Name (Number) Deleted\n \n \nSecurity Keys Associated:\n New/Modified/\nSecurity Key Name Deleted \n----------------- -------------\nN/A\n \n \n \n------------------- --------------------------------- -------------\nTemplates, Input Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\nN/A\n \n \n \nTemplates, List Associated:\n New/Modified/\nN/A\nTemplate Name Type Deleted \n------------- ---- -------------\nN/A\n \n \n \nTemplates, Print Associated:\n New/Modified/\nTemplate Name Type File Name (Number) Deleted \n------------- ---- ------------------ -------------\n \nN/A\n \n \n \nTemplates, Sort Associated:\n \nNew/Modified/\nTemplate Name Type File Name (Number) \nDeleted \n------------- ---- ------------------ \nBulletins Associated:\n-------------\nN/A\n \n \nAdditional Information:\nN/A\n \n \nNew Service Requests (NSRs)\n---------------------------- \n New/Modified/\nN/A\n \n \nPatient Safety Issues (PSIs)\n-----------------------------\nN/A\n \n \nServiceNow Ticket(s) & Overview\n-----------------------------------------------\nBulletin Name Deleted \nN/A\n \nTest Sites:\n----------\nTBA\n \nSoftware and Documentation Retrieval Instructions:\n----------------------------------------------------\n \nSoftware being released as a host file and/or documentation describing\nthe calling SDAM APPOINTMENT EVENTS protocol is invoked from within\n------------- -------------\nthe new functionality introduced by this patch are available.\n \nThe preferred method is to retrieve files from download.vista.domain.ext.\nThis transmits the files from the first available server. Sites may\nalso elect to retrieve files directly from a specific server. \n \nSites may retrieve the software and/or documentation directly using \nSecure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE\ndirectory at the following OI Field Offices:\n \nN/A\n Hines: fo-hines.domain.ext\n Salt Lake City: fo-slc.domain.ext\n \n \nDocumentation can also be found on the VA Software Documentation Library \nat:\nhttp://www4.domain.ext/vdl/\n \nTitle File Name FTP Mode\n--------------------------------------------------------------------------\n \nN/A\n \n \nPatch Installation:\n \n \nPre/Post Installation Overview\n------------------------------\nThere are no pre- or post-installation tasks for this patch.\n \n \nInstallation Instructions\n-------------------------\nInstall Time - less than 5 minutes.\n \n 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.\n \n 2. From the Kernel Installation & Distribution System menu, select\n the Installation menu.\n \n 3. From this menu, you may select to use the following options\n \n (when prompted for INSTALL NAME, enter DVBA*2.7*208):\n a. Verify Checksums in Transport Global - This option will \nallow\n you to ensure the integrity of the routines that are in the\n transport global.\n b. Print Transport Global - This option will allow you to view\n the components of the KIDS build.\n c. Compare Transport Global to Current System - This option \nwill\n allow you to view all changes that will be made when this \nDialogs Associated:\n patch is installed. It compares all components of this\n patch (routines, DD's, templates, etc.).\n d. Backup a Transport Global - This option will create a backup\n message of any routines exported with this patch. It will \nnot\n backup any other changes such as DD's or templates.\n \n 4. Use the Install Package(s) option and select the package \nDVBA*2.7*208.\n \n New/Modified/\n 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//"\n respond NO.\n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? NO//", respond NO\n \nBack-Out/Roll Back Plan:\n------------------------\nIn the event of a catastrophic failure, the Facility Chief Information \nOfficer may make the decision to back-out the patch.\n \nDialog Name Deleted \nIt is imperative that you have performed a backup of the routines and\nthe routines included matches the pre-patch checksum from the patch\ndescription.\n \nThis patch only contains routine updates. To back-out the patch please\nrestore the backup message from the patch installation process.\n----------- -------------\nN/A\nVistA Scheduling GUI, as a GUI user would be unable to answer the user\n \n \n \nForms Associated:\n New/Modified/\nForm Name File Name (Number) Deleted \n--------- ------------------ -------------\nN/A\n \n \ninput prompts for the DVBA protocol. (This patch does not require a GUI\n \nFunctions Associated:\n New/Modified/\nFunction Name Deleted \n------------- -------------\nN/A\n \n \n \nHL Logical Link:\nupdate.)\n New/Modified/\nHL Logical Name Deleted \n--------------- -------------\nN/A\n \n \n \nHL7 Application Parameters:\n New/Modified/\nHL7 Parameter Name Deleted \n \n------------------ -------------\nN/A\n \n \n \nHLO Application Registry:\n New/Modified/\nHLO Registry Name Deleted \n----------------- -------------\nN/A\nPatch Components\n \n \n \nHelp Frames Associated:\n New/Modified/\nHelp Frame Name Deleted \n--------------- -------------\nN/A\n \n \n================\n \nMail Groups Associated:\n New/Modified/\nMail Group Name Deleted \n--------------- -------------\nN/A\n \n \n \nOptions Associated:\n \n \nNew/Modified/\nOption Name Type \nDeleted \n----------- ---- \n-------------\nN/A\n \n \n \n\n
\nThe "Get Docs from Virtual VA" option is still visible in CAPRI for some \nusers even though it has been discontinued. This is due to users still \nholding instances of the 'DVBA CAPRI GETVBADOCS' key from the SECURITY KEY\n(#19.1) File.\n\n
\nCAPRI currently operates on XML schema 1.0 when transmitting \n-Veteran of Interest Type\n-Document Type\n-Service Provider Type\n-Approver Type\n-Person Type\n-Client Type\n \n \nPatch DVBA*2.7*212 will also fix the following issues:\n-Other facilities visited button/message will be updated to display an \nDisability Benefits Questionnaires (DBQ's). To comply with IEPD standards\n appropriate message to users\n-Completed date and Release date does not get populated when exam \n templates are signed in CPRS\n-Enterprise Search not routing appropriately\n-Transmission to VLER Failed message not accurate in some cases\nfor transmitting data and to maintain system and security standards, an\nupdate is required to the most current standards.\nThese changes are for the following fields of data:\n-Facility Type\n-Service Provider Client Association Type\n-Exam Detail Type\n-Claim Information Type\n\n
\nCertain sites are receiving an undefined error message when running\nreports on cancellations within the Compensation and Pension Record\nInterchange (CAPRI) GUI application. The sites generating this\nerror are populating new corrupt entries in the DATE STATUS LAST\nCHANGED (AH) cross-reference of the 2507 REQUEST (#396.3) file daily\ndue to the task DVBA C PURGE 2507 - Purge Old 2507 Requests being\nscheduled to run each day. These cancellation reports are not able\nto display when VistA attempts to cycle through the DATE STATUS LAST\nCHANGED (AH) cross-reference because of these corrupt data entries.\n\n
\nDVBA*2.7*18\n\n
\nThis patch will modify the REMOTE APPLICATION file (#8994.5) \nCALLBACKSERVER (#.03) field in support of the CLAIMS server migration\nto Linux.\n\n
\nThis patch addresses a request to add the option Reset Copay Status List\nManager [PSOCP RESET COPAY STATUS LM] to the HRC Pharmacy Menu [DVBA\nHRC MENU PHARMACY].\n\n
\n \nadd functionality to manually transmit documents and data to Veterans\nBenefits Management Systems (VBMS).\n \n-adds a feature to store failed Disability Benefits Questionnaires (DBQ)\ntransmissions. The user will be prompted to transmit stored DBQ's when\nCAPRI opens and when CAPRI closes.\n \n-adds two new selections for the Special Consideration File 396.25\n -Purple Heart Recipient\n -Incarcerated\nPatch DVBA*2.7*220 will update the Compensation and Pension\n \n-adds a Self-Referral Flag selection to allow users to indicate on the \nC&P Worksheet Screen if the DBQ is self-referred.\n \n-adds a feature to display Behavioral Patient Record Flags and detailed \ninformation if selected.\n \nThis patch also addresses the following issues:\n1.) CAPRI Error #701 & Error #312 reports when attempting to submit \n Insufficient Exam\nRecord Interchange (CAPRI) GUI to Delphi Version XE10 to implement the \n2.) CAPRI Screen text is very small and needs to be changed.\n3.) CAPRI: A&A template not recognizing presence of the DBQ Medical \n Opinion template\n4.) CAPRI connect error message display change for Enterprise Search or \n Other Sites Visited option\n5.) CAPRI copy with CTRL+C causes error\nnew Remote Procedure Call (RPC) broker allowing compliance of Two \nFactor Authentication (2FA) which will require the use of a Personal\nIdentity Verification (PIV) card.\n \nPatch DVBA*2.7*220 also adds and/or changes the following functionality \n-updates the Compensation and Pension Record Interchange (CAPRI) GUI to\n\n
\nPlease refer to patch description on FORUM.\n\n
\nAs the transition to Cerner occurs, there are two different process flows\n \n -----------\n Changes were made to the Patient ID ListBox to label this componenet, \n which will allow for 508 compliance to be met.\nCAPRI Enterprise Record Search and "other facilities visited" \nfunctionality will be updated to use a new Remote Procedure Call to \nretrieve the list of treating facilities associated with the record, \nincluding a Cerner Indicator along with the "Date Last Treated" \nidentifying patients at a Cerner converted site. This will allow CAPRI \nto correctly communicate whether the patient record was migrated from \nVista or if it was created on/after the conversion so that VBA users will \nbe able to route claims accordingly.\n \ndepending on if the data available for the patient existed prior to the \n \nThe following defects that were entered after the release of Patch\nDVBA*2.7*220:\n \n \nCAPRI-209 - CAPRI users connecting to remote sites via Claims are not \nable to transmit reports or DBQs to eFolder\nCAPRI-210 - Unable to select all progress notes via single scroll\nCAPRI-211 - Claims user prompted to enter password again when user has \nmore than one division\nconversion or was added after conversion. The "Enterprise Search" and \nCAPRI-238 - Patient Selector Add 508 Compliance\n \n \n1.) CAPRI-209 - CAPRI users connecting to remote sites via Claims are not \n able to transmit reports or DBQs to eFolder\n \n Problem: \n --------\n DBQs and reports are transmitted from VBA users (reports) and VHA \n users (DBQs) to VLER DAS. \n"Other Facilities Visited" functionality will qualify the entry depending \n VBA users connecting to a remote site via Claims are not able to \n transmit reports to the VBA eFolder Queue (VLER DAS). This issue is\n caused by a failure by the kernel M code to validate\n a guest account which is attempting to send the report XML request to \n DAS. The specific failure is that the guest account on the remote\n site gets proxyauthfailed when the proxy server attempts\n to validate the token sent by the guest account.\n \n \n Resolution:\non when the records were created relative to when the conversion occurred \n -----------\n Temporarily this enhancement is being removed for all CAPRI users \n to allow for additional modifications needed downstream in the\n process. \n This will be addressed in a future patch. Send to Virtual VA button \n is being re-instated to its prior functionality.\n \n \n2.) CAPRI-210 - Unable to select all progress notes via single scroll \n \n(before or after the conversion). When Cerner only data exists, the \n Problem:\n --------\n In Patch 212, the user was able to select all the entries in one \n selection. In Patch 220, the selection stops at next to last entry. \n All functionality still works as expected if you navigate\n to the first and last entries of your selection and shift+click.\n \n Resolution:\n -----------\n Modified the TORListBox component to include the last (partially \nCerner entry will be qualified with "Treatment Record Exist".\n displayed) row. This restored the continuous scroll down behavior\n that the user had seen in patch 212.\n \n \n \n3.) CAPRI-211 - Claims user prompted to enter division again when user \n has more than one division\n \n Problem:\n --------\nExample:\n Remote users are prompted multiple time to select a division because \n the broker is connecting to the home server,\n if they have more then one division assigned to them on the claims \n server. \n \n Resolution:\n ----------- \n Changes were made to the process in CAPRI that handles broker \n connections to the home server. CAPRI will now \n store the division after the first selection and use this division \n200CRNR-Treatment Records Exist\n each time the home server is connected to during the session.\n \n4.) CAPRI-238 - Patient Selector Add 508 Compliance\n \n Problem:\n --------\n During 508 Compliance Audit it was found that the Patient Selector \n Window did not meet compliance.\n \n Resolution:\n\n
\nPatch DVBA*2.7*224 will update the Compensation and Pension\nRecord Interchange (CAPRI) GUI CAPRI News service. If the News \nServer is unavailable, the GUI will bypass this service this allowing the \nuser to continue launching the application and eliminating any downtime.\n\n
\nPrint C&P Final Report (Manual) is not clearing results which have a \nCLAIM NUMBER (#.313) field in the PATIENT (#2) file that's value matches \nthe patient's SOCIAL SECURITY NUMBER (#.09) field in the PATIENT (#2) \nfile or has no value. CAPRI API's will be modified to allow the above\nsituations to function properly.\n\n
\nThis patch fixes a name spacing error in the option Edit C&P Request \nInformation [DVBA C EDIT C&P REQUEST INFO].\n\n
\nBackup of DVBA*2.7*230 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will update the AMIE EXAM (#396.6) file by updating the NAME \n(#.01) field of 1 exam.\n\n
\nThe changes included in this patch are described in the description\nof patch DVBA*2.7*23 in the National Patch Module.\n\n
\nBackup of DVBA*2.7*232 on Apr 20, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch will update the SPECIAL CONSIDERATIONS (#396.25) file by \nadding a new Special Consideration reason 'VICAP'.\n\n
\nBackup of DVBA*2.7*229 on May 18, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nDVBA C PROCESS MAIL MESSAGE files an outdated value of "NT" into the \nREQUEST STATUS (#18) field of the 2507 REQUEST (#396.3) file, instead of \nlooking up and filing a value which corresponds with "NT". Routine \nREQEDIT^DVBCXFRC has been edited so that instead of hard stuffing the \nvalue "NT" into the REQUEST STATUS (#18) field of the 2507 REQUEST \n(#396.3) file, it will allow FileMan to determine and fill the \nappropriate value that corresponds with "NT".\n\n
\nBackup of DVBA*2.7*226 on Jul 02, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nPatch DVBA*2.7*226 will update the Compensation and Pension\nQuestionnaire's (DBQ's) to verify that the template being used is an\nactive DBQ template before allowing completion and processing.\nIf the template is inactive, the DBQ is being marked "Outdated Template" \nand the user is prompted to update the template for completion. This \nchange is also reflected in a status addition to the CAPRI TEMPLATES File \n(#396.17) REVIEW STATUS Field (#11) having the term "OUTDATED TEMPLATE" \n \nPatch DVBA*2.7*226 is modifying the DBQ Schema in preparation for the \nrelease of IEPD Claims-2.1.\n \nRecord Interchange (CAPRI) GUI Report Builder option. This option is used \n \nPatch DVBA*2.7*226 will also fix the following issues:\nINC11416760 - CAPRI: Application Exception error\nINC13803597 - Change Joint Legacy Viewer tab in CAPRI to Joint \n Longitudinal Viewer tab due to senior leadership re-branding\nto create a report of a selection of Clinical Documents. Processing for\nthis option is being removed from the GUI and moved to the Vista server. \nThis move will minimize the resources used on the local machine and\noptimize the workflow, thus correcting the issue of CAPRI\nnot responding and requiring the user to end task via Task Manager.\n \nPatch DVBA*2.7*226 is also allowing for Disability Benefit \n\n
\nBackup of DVBA*2.7*234 on Aug 18, 2021\n \nWarning: Installing this backup patch message will install older versions\nof routines and Build Components (options, protocols, templates, etc.).\nPlease verify with the Development Team that it is safe to install.\n\n
\nThis patch addresses a request to add the option First Party Veteran\nCharge Report [PRCA FP VETERAN CHRG RPT] to the HRC First Party Extended\nServices [DVBA HRC MENU EXTENDED SVCS], HRC Pharmacy Customer Care Menu\n[DVBA HRC MENU PHARMACY CC], and HRC Pharmacy Menu [DVBA HRC MENU\nPHARMACY].\n\n
\nPatch DVBA*2.7*227 is using code originally introduced in patch \nthis change. \n \n \nIn response to requests to decouple routing locations between C&P Exam \nRequests and 7131 (release of information) Requests along with the \nability to disable 2507 and/or 7131 Requests from being requested at \ncertain sites, modifications were made to the "Edit Exam List \nParameters" form/option to add functionality to control these new \nfeatures. Users with the necessary keys to access the form will \nnow have the ability to maintain routing locations for C&P Exam Requests\nDVBA*2.7*193 the system will allow the user to re-route a Compensation &\nand 7131 (release of information) Requests independently. \nDVBA*2.7*227 also introduces functionality that will allow facilities \nto disable the ability to submit C&P Exam Request and/or 7131 Requests\nby disabling the "Add a New Request" button specific to each of those \nrequests.\n \n \n \n \nPatch DVBA*2.7*227 will also fix the following issues:\nPension (C&P) exam request to any active C&P facility within the VA so\n1. INC09160447 - CAPRI Report Builder is unable to print large reports.\n2. INC18799389 - <PARAMETER>CHECK^DVBAB1B - DEV\nthat the request does not have to be cancelled and re-initiated.\nCAPRI users will now have the ability to re-route an existing exam \nrequest.\n \nPatch DVBA*2.7*227 also changes the location of the stored file for \nthe News Server. There is no functionality changes on the user side for\n\n
\nPatch DVBA*2.7*236 will fix the following issue:\nThis patch updates the AMIE EXAM (#396.6) file by changing the STATUS \n(#.5) field of exam DBQ GU Prostate cancer from ACTIVE to INACTIVE.\n\n
\n \nUpdate of AMIE worsheets per VHA request. The following are updated:\n LIVER, GALL BLADDER AND PANCREAS\n GENERAL MEDICAL EXAMINATION\n AUDIO\n EAR DISEASE\n\n
\nPatch DVBA*2.7*237 is addressing error handling for communication between \nand Signed. These new status' will provide a clearer, documented status\nfor transmission errors of the Disability Benefit Questionnaire (DBQ) to\nthe Veterans Benefits Management System (VBMS).\n \nPatch DVBA*2.7*237 is adding the new status' for use in the Template \nReport that user's can select using the Compensation and Pension Record\nInterchange (CAPRI) GUI.\nCAPRI and Veterans Benefits Management System (VBMS).\n \nThe CAPRI GUI will present a new error message for Clinical Document \ntransmission failures and allowing users to retry the document\ntransmission.\n \nThree new status' in File ^DVB(396.17) CAPRI TEMPLATE file are being \nintroduced. These new statuses are: Permanent Failure, Transmission Error\n\n
\nPatch DVBA*2.7*240 is addressing error handling for communication between \nError and Signed. These new statuses will provide a clearer, documented\nstatus for transmission errors of the Disability Benefit Questionnaire\n(DBQ) to the Veterans Benefits Management System (VBMS).\n \nPatch DVBA*2.7*240 is adding the new statuses for use in the Template \nReport that users can select using the Compensation and Pension Record\nInterchange (CAPRI) GUI.\n \nPatch DVBA*2.7*240 is adjusting the Joint Longitudinal Viewer (JLV) \nfunctionality to launch with the default browser, instead of forcing \nCAPRI and Veterans Benefits Management System (VBMS).\nInternet Explorer (IE). This change will prevent JLV from having a \ndependency on IE due to the nature of how CAPRI launches a JLV session.\n \nThe CAPRI GUI will present a new error message for Clinical Document \ntransmission failures and allow users to retry the document\ntransmission.\n \nThree new statuses in CAPRI TEMPLATE ^DVB(396.17) file are\nbeing introduced. These new statuses are: Permanent Failure, Transmission\n\n
\nThis patch updates the AMIE EXAM (#396.6) file by adding the new DBQ\nSpina bifida entry.\n\n
\nPatch DVBA*2.7*241 addresses when running Pending C&P Exams report in\nCAPRI GUI application and Pending C&P Exam Report [DVBA C PENDING REPORT]\noption in VistA, if the patient name is found after 'ZZZ', the code \ncontinuously loops and eventually the file fills the update and site\ngets the file full error.\n\n
\nThe BFI DocOperations service that CAPRI GUI currently uses as an \n2. VistA has been modified to add a new Security Key to allow DVBA \n CAPRI GUI users to send clinical documents to the eFolder.\n3. VistA has been modified to add a new option to allow users to run \n a report of the eFolder transmission metrics\n4. VistA has been modified to add a new security key and option to \n allow a user to purge eFolder transmission data.\n5. VistA has been modified to add DVBA METRICS DATA REPORT to the \n DVBA C MEDICAL ADM REPORT MENU\n6. VistA has been modified to add DVBA METRICS DATA PURGE to the \n DVBA C C&P MASTER MENU\nendpoint for sending Clinical Documents to eFolder resides on a server \n \nTo comply with the VA Enterprise TRM requirements, the CAPRI GUI is \nupdating to Delphi 10.4.\n \nPatch DVBA*2.3*238 is also addressing INC21519211: CAPRI - \nunable to sign DBQ - DBQ XML schema validation failed.\nthat is scheduled for decommissioning by the end August 2022. In order to \nmaintain the capability to send Clinical Documents to eFolder, CAPRI will \nsend documents directly to eFolder.\n \n1. VistA has been modified to add CAPRI CLINICAL EFOLDER \n TRANSMISSIONS File (#396.21) to store transmission metrics for\n eFolder processes.\n\n
\nPatch DVBA*2.7*245 will fix the following issue:\nFiles & Fields Associated:\n --------\n Some users are experiencing an issue with CAPRI transfers to VBMS \n eFolder.\n \n \n Resolution:\n -----------\n Removed security check on token return as this is causing the issue \n for remote users. \n \nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \n \n \nForms Associated:\n \n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nN/A\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\nCAPRI GUI VBA Users are receiving a 401 error when sending documents using\n \n \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \nN/A\n \n \nProtocols Associated:\nthe send to VBA eFolder.\n \nProtocol Name New/Modified/Deleted\n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\n \nN/A\n \n \n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\nPatch Components: \n \n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- -------------------\nN/A\n \n \nParameter Definitions Associated:\n----------------\n \nParameter Name New/Modified/Deleted\n-------------- -------------------\nN/A\n \n \n \nAdditional Information:\nN/A\n \n \n \nNew Service Requests (NSRs):\n----------------------------\nN/A\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\n \n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1.) INC23855232: capri transfer of document issue\n INC23855099: CAPRI will not let me send documents to VBMS - seems \n to be a certificate issue.\n INC23832201: CAPRI will not allow upload to VBMS\n INC23849031: Capri error - unable to send records to VBMS eFolder\n \n Problem: \n\n
\nPatch DVBA*2.7*242 updates the CAPRI GUI to be 508 compliant by \n(VBMS), this has been updated to show the correct document type and \nsubject.\n \nCAPRI GUI Users are also experiencing wrong patient demographics being \ndisplayed in the PDF footer after signing a Disability Benefits \nQuestionnaire (DBQ). This patch ensures that CAPRI will display the \ncorrect patient demographics information in the PDF footer.\nimplementing the bug defect remediations for this year's audit. \n \nA small update is also included to improve the CAPRI Disability Benefits \nQuestionnaire (DBQ) Push Utility to better handle CAPRI parameters that \nare incorrectly set up in VistA. \n \nCAPRI GUI Veterans Benefits Administration (VBA) Users are experiencing \nmislabeled clinical documents in Veterans Benefits Management System \n\n
\n \nINC23613395: CAPRI Report Builder fails on the Outpatient History All \n \n \nNew Service Requests (NSRs):\n----------------------------\nN/A\n \n \nPatient Safety Issues (PSIs):\n-----------------------------\nN/A\nreport in the Meds tab of the Clinical Documents \n \n \nDefect Tracking System Ticket(s) & Overview:\n--------------------------------------------\n1.) INC23613395: CAPRI Report Builder fails on the Outpatient History \n All report in the Meds tab of the Clinical Documents \n \n Problem: \n --------\n When using the CAPRI Report Builder function a\nINC18759211: CAPRI: can't get DBQs to sign when in draft/not ready status\n <SUBSCRIPT>DRUG+8^DVBCREPT error is received if a Medication order\n is missing the Drug which is causing the Drug Class to error.\n \n \n Resolution:\n -----------\n Code was added to resolve the missing data gracefully, the error \n will no longer occur but supply the verbiage "VA DRUG CLASS NOT\n AVAILABLE".\n \nINC20083692: Report Builder running slowly \n \n2.) INC18759211: CAPRI: can't get DBQs to sign when in draft/not ready \n status\n \n Problem:\n --------\n Signing case off color changed to black which indicates it is \n completed but stays in Draft not ready, directly affecting patient\n care because holding up information transferring to the VBA which\n stops access from patient to have access to health care.\nINC23025221: CAPRI Allows multiple DBQs with the same name to be added to \n \n \n Resolution:\n ----------\n Code was added to verify if the document is a C&P exam and if not \n then it will set the status code to complete.\n \n \n \n3.) INC20083692: Report Builder running slowly \na worksheet in error \n \n Problem:\n --------\n Users are creating reports with zero selections and encountering \n errors. If the selection is blank it was creating \n a duplicate string of characters which was creating an error in the \n RPC call.\n \n Resolution:\n ----------\nINC21126820: Cannot use Adobe Acrobat Print to PDF from CAPRI\n Added code to allow for zero selections and not create the duplicate \n string of characters.\n \n \n4.) INC21941384: Requesting office value on "insufficient" exam request \n showing the wrong office \n \n Problem:\n ---------\n VBA end user should probably not be able to change the requesting \nINC23999254: Patient Claim Number is missing error, unable to send \n office value after the request is submitted in CAPRI. \n The requesting office should be populated from the user's profile and \n shouldn't be manually changeable. \n However, the fact that the "insufficient exam request" is not \n grabbing the new user's office value but instead is grabbing \n the value of the original requester.\n \n \n Resolution:\n ----------\nclinical document to eFolder\n Disable update of regional office for new and insufficient exam \n request. If regional office number field is enabled, ensure that the\n updated regional office number will be saved.\n \n5.) INC23025221: CAPRI Allows multiple DBQs with the same name to be \n added to a worksheet in error \n \n Problem:\n -------\n User is not able to submit a C&P examination through CAPRI, it says \nINC21941384: Requesting offce value on "insufficient" exam request \n that the derm template is outdated, when trying to add a new template\n for derm, the system will not allow that and the user is not able to\n sign it now to submit.\n \n Resolution:\n ----------\n Code was added to prevent user from including duplicate named \n templates in worksheet.\n \n6.) INC21126820: Cannot use Adobe Acrobat Print to PDF from CAPRI\nPatch DVBA*2.7*243 introduces the capability to upload clinical documents \nshowing the wrong office\n INC21182944\n \n Problem:\n -------\n A compatibility issue has been identified with Compensation and \n Pension Record Interchange (CAPRI) and the \n Adobe print to portable document format (PDF) functionality for users \n with Adobe Acrobat DC version 21.011.20039 causing the Adobe Print to\n PDF functionality to fail.\n \n \n Resolution:\n -----------\n The new version of Adobe Print to PDF requires a defined filename \n (Document Title) be sent to the print driver, which is a new\n requirement with this version of Adobe. This code change has been\n implemented.\n \n \n7.) INC23999254: Patient Claim Number is missing error, unable to send \n clinical document to eFolder\n \n \n Problem:\n --------\n Clinical documents are not consistently able to be submitted to the \n eFolder if missing the Patient Claim Number.\n \n Resolution:\n ----------\n Code was added to update patient information on Clinical documents to \n include an EDIPI number if no Patient Claim Number exists.\n \nPatch Components: \n----------------\n \n \nFiles & Fields Associated:\n \nfrom CAPRI to VBMS using multiple veteran identifiers,\nFile Name (Number) Field Name (Number) New/Modified/Deleted\n------------------ ------------------- --------------------\nN/A\n \n \n \nForms Associated:\n \nForm Name File # New/Modified/Deleted\n--------- ------ --------------------\nwhich is addressing issue reported in INC23999254.\nN/A\n \n \nMail Groups Associated:\n \nMail Group Name New/Modified/Deleted\n--------------- --------------------\nN/A\n \n \nIn addition, this patch is limiting user access to the eFolder Uploading \nOptions Associated:\n \nOption Name Type New/Modified/Deleted\n----------- ---- -------------------- \nDVBA CAPRI GUI Modified\n \n \nProtocols Associated:\n \nProtocol Name New/Modified/Deleted\nfeatures. Only users meeting criteria provided by the Business\n------------- -------------------- \nN/A\n \n \nSecurity Keys Associated:\n \nSecurity Key Name\n-----------------\nN/A\n \nwill be able to send Clinical Documents to the eFolder.\n \n \n \nTemplates Associated:\n \nTemplate Name Type File Name (Number) New/Modified/Deleted\n------------- ---- ------------------ --------------------\nN/A\n \n \n \nRemote Procedures Associated:\n \nRemote Procedure Name New/Modified/Deleted\n--------------------- -------------------\nDVBAB CAPRI ALLOW CLINDOCS New\nDVBAB CAPRI EFOLDER LOCATION New\nDVBAB CAPRI PROVIDER New\n \nParameter Definitions Associated:\n \nPatch DVBA*2.7*243 is also resolving the following issues:\nParameter Name New/Modified/Deleted\n-------------- -------------------\nDVBAB CAPRI EFOLDER LOCATION New\nDVBAB CAPRI VHA TITLE New\n \n \n \n \nAdditional Information:\nN/A\n\n
\nPatch DVBA*2.7*248 is adding Status Field (.02) to the 2507 SPECIAL \nCONSIDERATIONS FILE (#396.25). This field will show an Active or \nInactive status to allow for display in the CAPRI GUI.\n \nThis patch is also introducing additional remote procedure calls to allow \nfor the editing of the 2507 Special Consideration File entries and the \nAMIE Worksheet Exam Names.\n\n
\nPatch DVBA*2.7*250 will implement the following:\n3. Short term fix for a Kernel issue for users with duplicate VistA \n New Person accounts and missing social security numbers.\n4. Pseudo SSN was not working properly within the CAPRI GUI \n application, this internal issue was found and corrected.\n \n \nPatch DVBA*2.7*250 will also address the following bugs:\nINC24303017: Edit Fields Not Announced by Screen Reader\nINC23768900: CAPRI Application Error Resulting in Shut Down\nINC25976939: CAPRI copy/paste and tab malfunction when entering a new \n1. Enhancements to the CAPRI News Feed to call the SharePoint \n patient\nINC24797102: HRC - Eu is having issues with the CAPRI Fayetteville \n location whenever EU's want to place an order\nINC21249123: CAPRI 2507 rerouted from Muskogee VAMC to Cheyenne VAMC was \n not delivered to Cheyenne VAMC\nINC26557317: Connection to server for DVBAB REPORT 7131INQ could not be \n established\n application and launch Pdf's with the CAPRI GUI, no longer launching an\n external browser.\n2. Enhance transmission error handling to save the encoded XML in a \n VistA file and allow users to resend, while maintaining a logged\n sender, response codes received and an attempted transmission count.\n a. VistA CAPRI TEMPLATES FILE (#396.17) has been modified to store\n transmission metrics for transmission processes.\n\n
\nContains changes as described in the National Patch Module for DVB*2.7*4.\n\n
\nThis patch corrects an undefined IO error, which happens when IO is not\ndefined in the environment.\n\n
\n \nPatch DVBA*2.7*250 decommissioned the DVBA HRC MENU PHARMACY CC menu \noption. This option is being re-instated and the option will be available\nto users.\n\n
\nPatch DVBA*2.7*252 introduces the Progress Notes Constructin Set (PNCS) \n \nINC27409886: Deleting an Open Template\nINC23389024: Disabled users still able to connect to claims.domain.ext\nINC30600763: Cannot access CAPRI Training Site\nINC34120499: CAPRI default/timeout window is "save and exit" rather than \n "keep working" which causes issues\nCAPRI 8151: When the User Runs the Report Builder, Blank Drug Classes \n will be Populated with Incorrect Data\nCAPRI-7883: Resizing Voc-Rehab Medical Services Request Dialog\nCAPRI-7884: Resizing Address Verification\nreplacement,Content Management Tool (CMT) system. This allows the Medical\nCAPRI-7879: Exam Reference Error in VistA-When the requested exam is \n opened, the field labeled 'Exam Reference' is being filled\n with the record number instead of the actual exam reference\n number based in VistA\nCAPRI-7867: Report Builder-data from the Diet tab appears in another \n patients data \nCAPRI-8244: Deprecate the CAPRI Manifest Query Going to DAS to Support \n DAS Release\nCAPRI-11150: Surgery Report error message encountered: DVBAB OPERATION \n REPORT could not be accessed!\nDisability Examination Office (MDEO) to create/update DBQ forms as\nCAPRI-10958: Empty window displaying on screen during CAPRI worksheet \n signing process\nCAPRI-12105: Surgery Report Ok Button Active without Report Selected, Out \n of Bound error message received\nCAPRI-10314: Capability to Sort and Filter the Edit Local Tab in DBQ Push \n Utility using an RPC\nCAPRI-11496: EFolder Transmission message for for Remote Users\nCAPRI-11586: Display Error Message for Users for Missing SecID in the NEW \n PERSON File\nCAPRI-11938: SecID and SSN Validation based on VistA DVBA CAPRI SECURITY \nneeded. With the introduction of CMT, Compensation and Pension\n TOGGLE\nRecord Interchange (CAPRI) will also allow users to create and edit \nDisability Benefits Questionnaires (DBQ) in a Portable Document Format\n(PDF).\n \nPatch DVBA*2.7*252 will also be addressing 508 issues and the following:\n\n
\nPatch DVBA*2.7*254 is addressing issues found with the release of Patch \nINC37372871: CAPRI\nINC37369129: R3 - (DET) New CAPRI Update\nINC37431769: Route to CAPRI Tier 2\nDVBA*2.7*252 which introduced the Progress Notes Construction Set (PNCS) \nreplacement: Content Management Tool (CMT) system.\n \nThe SNOW tickets being addressed are:\nINC37373850: User cannot input a DBQ; unable to open it once it has been\nclosed. 4 users having the same issue\nINC37378273: wrong name in capri\nINC37388259: CAPRI SIGNING CASES ERROR\n\n
\nCorrect undefined error for variable "DA"\n\n
\nThis patch eliminates the undefined error caused if no node 2 exists\nfor a selected FORM 7131 file (#396) entry.\n \nThe changes included in this patch are described in the description\nof patch DVBA*2.7*24 in the National Patch Module.\n\n
\nThis patch makes it possible to queue Insufficient Exam Report to a\nprinter.\n\n
\nThis patch makes it possible to print blank C&P worksheets in AMIE II. The\nmenu option is added under the Medical Administration C&P Menu for MAS\nusers.\n\n
\nUser-friendly word processing of the General Remarks of new C&P reports.\n\n
\nWhen users print C&P exam result, sign "<" as well as its following exam \ninformation will not be printed. The patch corrects the problem.\n\n
\nAddress various problems related to claim folder location, division, and\nstation number being null.\n\n
\n \nThe patch updates five AMIE worksheets and creates a new one in the\nVista Automated Information Excahange (AMIE) EXAM file (396.6).\n\n
\nThe changes included in this patch are described in the description\nsection of patch DVBA*2.7*35 in the National Patch Module\n\n
\n \n See National Patch Module Entry DVBA*2.7*5 on Forum for details of this\npatch.\n\n
\nThis patch updates one AMIE worksheet: LIVER, GALL BLADDER, AND PANCREAS in\nthe Vista Automated Information Exchange (AMIE) EXAM file (396.6).\n\n\n
\nThis patch corrects 0305 reporting program: DVBCWLQ where a header was \nassigned incorrectly when more exams were printed.\n\n\n
\nDVBA*2.7*41 consists of a KID install for VHA, a new GUI client for VBA\ninstalled. After it has been confirmed that all sites have loaded this \nhappening instantaneously. There is now a delay and the list scrolls\nsmoothly with the lookup only happening when the user pauses. \n23. An audit file has been created on the home server to record every\npatient a user accesses, which site the user is on, the date/time, and\nwhether the patient is flagged sensitive. The audit is active only in \nthe ESSO version.\n24. An animation of a spinning disc was placed on the reports tab so that\nthere is a visual cue the application is still working while a big report\nis being generated.\n25. There is a dropdown on the health summary tab so the user can \npatch and the new GUI has been deployed, a subsequent patch will be \nquickly jump to the various parts of the returned summary.\n26. If the user kicks off a remote data view query, multiple tabs will \nappear on the health summary tab for each site queried.\n \n \nDOWNLOAD INSTRUCTIONS\n--------------------- \n \nA new version of the CAPRI GUI/CLIENT software has been made available to\nlocal VHA IRM field sites via FTP. As of February 2002, the CAPRI GUI \nreleased that will de-activate previous CAPRI versions.\nwill be available on the OI Field Office ANONYMOUS.SOFTWARE directories as\nfilename DVBA_2_7_41.EXE, which refers to patch DVBA*2.7*41. Software may\nbe retrieved using FTP from the appropriate OI Field Office\nANONYMOUS.SOFTWARE directories.\n \n Albany 152.127.1.5\n Hines 127.0.0.11\n Salt Lake City 152.131.2.1\n \n \n \n \nFILE NAME FORMAT DESCRIPTION\n------------------- ------ -----------\nDVBA_2_7_41.EXE BINARY CAPRI GUI\n \n \nInstallation Process:\n \nThe CAPRI GUI requires that the RPC Broker V1.1 be installed on any PC on\nwhich the GUI will be executed. If a PC can already connect successfully \nChanges to this version of CAPRI are primarily in the Delphi/GUI code. \nvia CPRS, BCMA, or PCMM, then the RPC Broker has already been installed.\nIf you need to install the RPC Broker, please refer to the RPC Broker\nwebsite (http://vista.domain.ext/broker/download.html) for configuration\ninformation and to download the installation file if you do not already\nhave it. \n \nThere are two ways to install CAPRI:\n \nA. If you have configured the PC via the serverlist.exe application that\ncomes with the RPC Broker installation file, the CAPRI GUI can be copied\nHowever, a new KID was created to add additional existing \ndirectly to your Windows desktop. If you need more information on\nserverlist.exe, please refer to the RPC Broker user manual.\n \nB. If you have only loaded the RPC Broker on the PC but not configured it\nusing server list, CAPRI will default to BROKERSERVER, port 9200 when\nexecuting the application. If you wish to default to a different server \nand port, use the following instructions:\n \n1. Copy CAPRI to a folder on the PC, preferably c:\\program files\\vista.\n2. Create a shortcut on the desktop to CAPRI by right clicking on a blank\nbroker calls to the option DVBA CAPRI GUI on the server side.\nregion of the desktop and selecting NEW | SHORTCUT.|\n a. When asked for location type the location in which CAPRI GUI has\n been placed on the hard drive along with your local server and\n port information as parameters:\n "C:\\Program\nFiles\\VISTA\\dvba_2_7_35_38B.exe"s=vista.yoursitename.domain.ext p=9200 \n (The quotes must be included.)\n b. Press NEXT.\n c. When asked for name, type: CAPRI GUI\n d. Press FINISH.\n \n \nAfter creating the icon on the PC:\n \nAssign DVBA CAPRI GUI as a secondary option for the user who will be using\nthe CAPRI GUI client. This will provide access to the GUI context option\nand allow CAPRI to start-up successfully when the user logs-in from the\ndesktop icon.\n \nThis process is similar to the installation instructions for all other RPC\nBroker-enabled applications, such as CPRS, BCMA, and PCMM.\n \nPRE-INIT ROUTINE\nand a new ESSO (single sign-on) client for BVA, VHA MPI-Data Quality Team\n----------------\nAn entry for BVA/VBA Support office will automatically be added to files \nINSTITUTION (#4) and FACILITY TYPE (#4.1).\n \nPOST-INSTALL ROUTINE\n____________________\nThe remote user BVADevelopmentMERequests@mail.domain.ext will been added to \nthe following mailgroups:\n1. DVBA C 2507 CANCELLATION\n2. DVBA C 2507 EXAM REOPEN\nand VBA's Tiger Team. The ESSO client will not be available via FTP and \n3. DVBA C 2507 EXAM READY\n \n \n \nCHANGES TO DVBA_2_7_41.EXE\n--------------------------\n \n1. Ability to pick an exam type by body system when adding new exam \nrequest.\n2. Ability to pick an exam type by body system when editing or adding to \nwill be distributed directly to the teams that need it. The non-ESSO \nan existing exam request.\n3. Re-designed custom report builder as a floating tool. Documents can \nbe added/deleted or resequenced in any order.\n4. Ability to search by date, # documents, or all documents. Date range \napplies to notes, discharge summaries, consults.\n5. CAPRI cooperates better with Windows and releases processor ticks so \nthat it won't report as "not responding" in Task Manager when building a \nbig report.\n6. Animations display at login and while downloading information from \nVistA in a fashion reminiscent of Internet Explorer.. Status messages at \nversion of CAPRI will be able to be downloaded off of OI Field Office FTP \nthe bottom explain the actions taking place or display errors to assist \nwith troubleshooting.\n7. Ability to do a search for a division for all of the notes displayed \non the screen. Division was also added to the header of progress notes \nwhen they are displayed.\n8. Remote Data Views has been added to Health Summary tab.\n9. Integration control number has been added to patient selector to help \ntroubleshoot and validate identity of patients across sites.\n10. A label was added to clinical document tab to indicate how many\ndocument headers/titles are returned in the search list.\nsites. Information is available at the end of this message with the \n11. Application events are intercepted to prevent a mouse click or \nkeyboard press during a broker call. This prevents an error when \nmultiple broker calls try to run at the same time.\n12. The ESSO site list is maintained on the VistA home site instead of\nthe local system registry for better security and easier maintenance as\nsite information changes. Shortcuts to CAPRI-ESSO on the desktop will\nneed to be modified to support this change. Instead of using \n"hs=homeserver hp=homeport," "h=homeserver p=homeport" should be used.\n13. Users with a Restricted Patient List on the VistA server can only \npick or add patients on their list. This was in the previous version of \ninstructions.\nCAPRI but was not yet activated.\n14. When selecting a health summary, the memobox would previously jump \nto the bottom requiring the user to scroll up to start at the beginning. \nIt now does this automatically.\n15. Intermittent error ("cannot modify field") when adding new patient \nhas been fixed.\n16. The executable was re-named to DVBA_2_7_41.EXE and \nDVBA_2_7_41-ESSO.EXE.\n17. At close, sliders for the clinical documents tab, health summary \ntab, and reports tab are stored in the capri.cfg file so that they will \n \nbe in the same location the next time the application is loaded.\n18. Limiting by date range functionality for meds and vitals is present \nin the option list but will display a "not in this version" message. \nThis function will be activated in the next release of CAPRI. \n19. Internal version # was updated. To make CAPRI less annoying to users\nwhile sites are upgrading, the informational message that appears when a\nsite has not yet loaded the KID was removed. CAPRI will error during some\nnon-critical activities if the site hasn't loaded the DVBA*2.7*41 KID,\nsuch as trying to run a remote data view health summary. \n20. A utility was placed on the HELP menu to scan all of the user's\nPrevious versions of CAPRI will continue to function after this patch is \nauthorized sites and determine if the Broker connection is good or bad. \nOnly users with the Filemanager @ sign have access to the option. It is\ndisabled for everyone else. \n21. If a user's institution cannot be found in the remote site's\ninstitution file, the warning message will no longer display but they can\nmanually enter a site location. If the match is made, it is automatically\nentered and the user prevented from changing the field. \n22. A modification was made to the timer controlling demographic info\nlookup of patients on the restricted site list. Previously, the list\nwould scroll slowly because the pt. demographic lookup broker calls were\n\n\nThis patch updates three AMIE worksheets.\n\n
\n \nSee Patch Description DVBA*2.7*44\n\n
\nSee Patch Description DVBA*2.7*48\n\n
\nThis patch updates the following AMIE worksheets:\n\n - MENTAL DISORDER (except PTSD and Eating Disorders)\n - INITIAL EVALUATION FOR POST-TRAUMATIC STRESS DISORDER (PTSD)\n - EATING DISORDERS (Mental Disorders)\n - REVIEW EXAMINATION FOR POST-TRAUMATIC STRESS DISORDER (PTSD)\n - SPINE(CERVICAL, THORACIC, AND LUMBAR)\n\n\n
\nUpdate AMIE worksheets #1605 and #1610\n\n
\n \n See patch description in the Patch Module for patch DVBA*2.7*8\n\n
\nSee patch description for DVBA*2.7*50 \n\n
\nMisc. NOIS fixes\n\n
\nVista changes for CAPRI GUI DVBA*2.7*45.\n\n
\nThis patch adds a new attachment to the COLD INJURY PROTOCOL EXAMINATION\n(#1730) worksheet.\n\n
\nAdd CIRRHOSIS OF THE LIVER to PRISONER OF WAR PROTOCOL EXAM.\n\n
\nThis patch creates the new AMIE worksheet for Hands, Thumb, and Fingers.\n\n
\nCorrects an undefined error while printing multiple exams, one being the hands\nexam.\n\n
\nDischarge report not printing\n\n
\nCreate new spine worksheet.\n\n
\n \nSee the patch description on DVBA*2.7*9 of the patch module for details.\n\n
\nCAPRI CPWM\n\n
\nNEW WORK SHEETS FOR HAND THUMB AND FINGERS ALSO JOINTS.\n\n
\nThis will install a new DIABETES MELLITUS AMIE EXAM worksheet. This \nupdates the AMIE EXAM #396.6 with the new DIABETES MELLITUS AMIE \nWORKSHEET# 0410.\n\n
\nThis patch will add a new AMIE C&P worksheet, Social And Industrial \nSurvey.\n\n
\nThis patch will put in place and activate a new LIVER, GALL, BLADDER, AND \nPANCREAS worksheet.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nCorrect filing of the 2507 exam in an AMIE Transfer.\n\n
\nNEW EYE EXAMINATION WORK SHEET\n\n
\nUpdates to Skin Diseases and Hand, Thumb, and Fingers AMIE worksheets.\n\n
\nThis patch addresses a problem with updating a cancelled request when the\nexams are cancelled at another facility. See the National Patch Module\nfor a more detailed description of the changes included with this patch.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nUpdates to the AMIE Liver, Gall Bladder and Pancreas Worksheet.\n\n
\nUPDATES TO AMIE C&P DISABILITY EXAM CHECKLIST FOR RO\n\n
\nThis patch corrects the fault that was using the incorrect patient name \nwhen entering the patient data via the CAPRI GUI.\n\n
\nNew AMIE Genitourinary Examination worksheet.\n\n
\nUpdates to POW Worksheet\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nIncorrect release date and time.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nSee National Patch Module for a complete description of this patch.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nUpdates to AMIE Nose, Sinue, Larynx, and Pharynx C&P Worksheet.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nUpdate to AMIE JOINTS ((SHOULDER/ELBOW/WRIST/HIP/KNEE/ANKLE) C&P \nWORKSHEET.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nThis patch fixes problems with the CAPRI Discharge Report.\n\n
\nUndefined variable error.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nThis is a patch to the AMIE Worksheet functionality. See patch description.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nThis patch corrects two issues:\n \n 1. The CAPRI GUI version of the "BATCH 2507 REPRINT" will produce a\n "No data found for requested report criteria." message, while the\n AMIE version produces the correct results.\n \n 2. The CAPRI GUI version of the "Discharge Report" will produce a\n "No data found for requested report criteria." message, while the\n AMIE version produces the correct results.\n\n
\nMISC CAPRI FIXES\n\n
\nSee patch module description on FORUM.\n\n
\nFIXES UNDEF AT LABEL RMK IN DGRPD\n\n
\nPlease see the National Patch Module for details\nof the enhancements included in this patch.\n\n
\nUpdates to the AMIE Mental Health worksheets.\n\n
\nUpdates to 4 AMIE C&P Exam Worksheets.\n\n
\nUpdates to 6 AMIE C&P Exam Worksheets: Esophagus, Feet, Hand, \nIntestines, Scars and Stomach.\n\n
\nUpdates for 11 AMIE C&P Exam Worksheets\n\n
\nThis patch addresses two issues. The first issue is a problem with\nVISTA headers that print incorrectly on CAPRI reports causing formatting\nissues. The second issue is to remove the VISTA TIU $END keyword used to\ndenote the end of a report when doing the Re-Print Final C&P Report.\n\n
\nAdd new AMIE C&P Worksheet to the AMIE Exam file (396.6).\n\n
\nThis is the entire AMIE package. Both the 7131 and the 2507 portions\nare carried under a single namespace. AMIE was designed to help\nautomate the requesting process for both of these programs.\n(Note: Routines for the 2507 portion are still namespaced DVBC.)\n\n
\nDental Version 1.2 Patch 20.\n\n
\nThis is patch 29 of Dental version 1.2.\n\n
\nDENT*1.2*30 provides the integration of the vendor Document Storage\nthe process (required as a condition for the national purchase).\nSystems' (DSS) Dental Record Manager (DRM) product into the VistA Dental\npackage. One of the conditions of the national purchase of DRM was that\nthe existing VEJDWPD module from DSS would be converted to the DENTV\nnamespace and the files ^VEJD(19600.x) would be moved to ^DENT(228.x).\nThe original VEJDWPD package stored some data elements in the Dental\nHistory file (#19600.1) that the Database Administrator considered\nduplicate data (i.e., PCE data elements). A post-init will move the\nDental History file to file# 228.1 and will remove those data elements in\n\n
\nPatch ICD*18.0*2 was released 11/2/2001. That patch inactivated several ICD9\n521.0 or 525.1 which were inactivated by the ICD*18*2 patch as of Oct 1, 2001\n ICD9 code 521.0 will be remapped to 521.00\n ICD9 code 525.1 will be remapped to 525.10\n \nThe post-init will check three things:\n \n1. It checks to see if all nationally export ADA codes are indeed in file\n 228. A few sites have reported that one or two codes were not in their\n file 228 even though it was exported.\n \ncodes used in the dental DENTAL CPT CODE MAPPING file (#228). That file has a\n2. The GUI option context, DENTV DSS DRM GUI, has the list of all the RPCs\n that the DRM GUI may execute. A few sites have reported that one or two\n RPCs are not in the option even though they were exported. The post-init\n will ensure that all required RPCs are part of the option.\n \n3. Because of the problem caused by ICD*18.0*2, the post-init will check\n every CPT and ICD9 code in file 228 (both national codes and locally added\n codes) for any problems. A report will be displayed detailing any\n problems found.\n \nlist of CPT procedures used in the dental DSS DRM application. Those\n4. You will find any of these pertinent messages in the installation after\n the line: Running Post-Install Routine: POST^DENTVIP1.\nprocedures have a default diagnosis associated with each procedure.\n \nThis patch consists of file 228 and a post-init routine.\n \nIt exports the file DENTAL CPT CODE MAPPING (#228) with updated diagnosis\ncodes. Specifically, there were 244 CDT3 codes mapped to diagnosis codes\n\n
\n I. v3.0 of the dentalmrm.exe switched two service conditions:\n \n III. If DENT*1.2*30 was installed in an account which did not have a\n previous version of DRM (VEJDWPD versions), then the multiple field\n 19600 on file 220.5 was not installed and an error message was\n recorded in the KIDS installation record. That multiple will now\n install properly in a new account.\n \n IV. The Excel extract option would fail occasionally. This happened\n because the Fileman API used to retrieve data from file 228.1 would\n not always return data for all the requested fields. This was\n environmental contaminants (or Persian Gulf) and ionizing radiation.\n especially true for a pointer field that pointed to a non-existent\n entry. This call was modified to protect against that contingency.\n The extract will also return any pce secondary providers.\n \n V. The retrieve dental history tab would not always return data. The\n call would quit and return no data if Fileman indicated any error\n while retrieving data. For example, the Dental History file has a\n pointer to the old DAS file linked to that history record. If that\n DAS record had been deleted (i.e., a broken pointer) Fileman would\n return an error. Even though the other 11 fields requested for that\n Thus patients with these conditions ended up having action required\n Dental History record had data, the call would return no data for\n that record. Now the data for that record will be returned. Those\n fields which encountered an error by the Fileman retrieve call will\n be shown as a null value. \n \n VI. All calls to retrieve data from the CPT file (#80) are required to\n use the APIs in ICPTCOD routine. Most places we were doing that.\n But there were two times when we did a direct Fileman call to file\n 81. Those places have been replaced by using the appropriate API in\n ICPTCOD.\n in PCE.\n \n VII. In patch DENT*1.2*30 the installer was prompted as to whether or not\n to delete the ^VEJD(19600) global. The documentation was not accurate\n in displaying this. This file and data global should have been deleted\n since the file was moved to file 228 [^DENT(228)]. The post-init will\n check the status of ^DIC(19600), ^DD(19600), and ^VEJD(19600) and do\n any appropriate cleanup to remove these entries.\n \n VIII. Dentalmrm.exe (v3.03) is exported as part of this patch.\n You can verify the version of the dentalmrm.exe from the Help/About\n \n option on the menu bar in the DRM GUI.\n \n IX. This patch will work with CPRS v16 or greater\n \n INSTALLATION FILES:\n ==================\n \n File Name Description Retrieval Format\n ----------------- --------------------------- ----------------\n DENT_1_2p32.KID Dental KIDS build ASCII\n II. There was a problem with filing administrative times. Some sites\n dentalmrm.exe DRM Version 3.03 Executable Binary\n would get the message unable to create record. When the call to\n UPDATE^DIE was made to create a record in file 226, the Fileman call\n failed if there were any required identifiers on fields .3,.4,.6,.9\n\n
\n I. This is released to support the Millennium Healthcare and Benefit\n III. This patch supports the entry of Head & Neck Cancer for PCE\n entry when appropriate.\n \n IV. For the Dx999 procedure codes, the mapping values to VistA DAS\n (Dental Activity System) have changed.\n A. For each code, one CTV will be mapped to DAS category\n '37-OTHER SIGNIFICANT TREATMENT'.\n \n B. These codes will now appear under the MISC tab in the DRM GUI.\n \n Act, Public Law 106-117 Section 20.\n C. These codes will not be used for billable procedures, but,\n rather, will be used to indicate a non-billable visit. These\n codes will generate one CTV into the DAS category "Other\n Significant Procedures." The codes may be used for intermediate\n steps and all similar non-billable patient visits. \n \n D. These mapping changes will require that practitioners select any\n code(s) NOT in the "99 Series" (D0999, D2999, D3999, D4999,\n D5899, D5999, D6199, D6999, D7999, D8999, and D9999) for\n "billable" procedures. Practitioners are advised to select the\n \n closest CDT code(s) outside the "99 Series" for any procedure\n that is considered "billable," and, therefore, results in\n clinical productivity related to procedures identified by the \n CDT codes not in the "unspecified" category (the "99 Series").\n \n V. There are two new RPCs\n DENTV DENTAL PROVIDER - returns active providers only\n DENTV USER DEFAULT DIV - returns a user's default division as\n defined in the NEW PERSON DIVISION multiple.\n \n II. This patch, DENT*1.2*34, along with VEJDCERT RPCS 2.11 are being\n VI. XINDEX will show the following error. This is not a problem. It is\n problem with the XINDEX program. There is an outstanding NOIS\n concerning this error message.\n DENTVRP8\n .S XN=+PROV_U_$$NAMEFMT^XLFNAME(XN,,"MD")\n VST+37 F - General Syntax Error.\n VST+37 F - General Syntax Error.\n released in a single KIDS software distribution. This patch\n contains the informational portion of DENT*1.2*34 and provides\n field personnel with instructions on how to acquire, install, and\n implement the software.\n \n\n
\n Note: several places in this patch description have items highlighted.\n errors.\n entry which was longer than the width of that window would not be\n completely displayed. Now if you hover over an entry, a hint\n will be displayed showing the entire contents.\n \n 8. The following routines which supported previous patch pre- and\n post-install processes will be deleted:\n DENTVCNV, DENTVI01, DENTVI02, DENTVI03, DENTVI04, DENTVI05\n \n 9. The DENTVRP3 routine was updated to bring it into complete SACC\n compliance by not doing direct reads of the ^DD global. When\n \n filing ICD9 codes to the ADA table (#228) it was possible that the\n name of the ICD9 code was entered into field 1 instead of the\n pointer value to file 80.\n Note: the ICPT*6.0*13 patch inactivated quite a few ADA codes with an\n inactivation date of 1/1/2003. As such, these codes will no longer\n show up in any tab within DRM. Please see the documentation\n accompanying patch ICPT*6.0*13 for details in changes to specific\n codes.\n *********************************************************************\n \n 2. This patch provides compatibility with the 2003 CPT and CDT4 codes\n The purpose of these highlights is to emphasize areas to pay particular\n A new ADA Mapping table (file 228) will be installed\n NOIS: ALB-0502-51618, FGH-0602-32626\n \n 3. A pre-installation routine will perform several steps\n a. Save local CPT codes the site has added to the ADA table\n b. Delete the existing ADA table\n \n 4. A post-installation routine will perform several steps\n a. Verify that all CPT codes in the dental provider's quick list are\n still active. If not, delete that code from the quick list\n attention. These should answer possible questions or concerns that IRM\n \n b. Restore any locally added CPT codes to the ADA table unless that\n code is exported nationally with this patch or that code is\n inactive.\n \n c. The dental coding committee spent considerable time assigning\n default diagnosis codes to each ADA code. As such, any changes\n the site had made to the associated default diagnosis codes will\n not be preserved.\n \n or the installer may have.\n 5. If the old data global, ^VEJD(19600.1), still exists, then delete it.\n A previous DENT patch had moved that data to ^DENT(228.1).\n \n 6. The DENTVDD routine was modified to remove direct references to the\n ^DD global. Supported Fileman APIs are used instead.\n \n 7. A new routine is exported, DSICCPT. This routine provides an\n interface to the CPT and ICD9 files using nationally supported APIs.\n \n ************************** PLEASE NOTE *************************\n \n The Release of Information application had DSIC 1.0 (or DSIC 1.01)\n as part of that package. This DSICCPT routine was not exported in\n those builds. So there is no conflict between this patch and the\n Release of Information 5.0 application. DENT*1.2*31 is to be\n released in the next couple of months and will include DSIC 1.1 which\n will include this DSICCPT routine as well as other changes.\n ******************************************************************\n \n 8. A new DRM GUI executable is exported with this patch. Changes\n include:\n 1. ***************** ATTENTION ATTENTION ******************\n a. Inactive Diagnosis codes (ICD9) will no longer be selectable in\n the search engine window. NOIS: ASH-1201-31869, BRX-0602-12946,\n MIN-1102-40433, NHM-0202-11852, PUG-0502-52312, WIM-0902-22158\n \n b. In the Help Menu bar we have added a last broker call\n debugging tools similar to the CPRS one.\n \n c. Fixed List out of Bounds errors. This could have happened when\n typing the progress note title in the search window. It could\n also occur occasionally when the FINISH button was clicked and\n This patch should be installed immediately after installing\n the program was trying to file data to the Problem List.\n NOIS: BIG-0103-70399, MOU-0103-30859, MWV-0103-22436,\n PHI-0103-22339, SFC-0103-62181, UNY-0103-11934\n \n d. Fixed an Access Violation error when DRM closes out\n NOIS: ALT-0102-21002\n \n e. Printing of signed addendum notes when prompted for additional\n signers now works if the check box is selected.\n \n ICPT*6.0*13 If it is not, then when the user clicks on the FINISH\n f. Completing a consult will now link to the proper Visit instead of\n creating a new historical Visit.\n \n g. Previous there were occasional problems if the FINISH button was\n clicked multiple times. Now the FINISH button will ignore the\n second and subsequent clicks until the all the DRM data including\n filing of progress note has completed which may take several\n seconds.\n \n h. There is now a Excel Extract option under the Tools option on the\n button in Dental Record Manager (DRM) they may generate PCE exception\n Menu Bar\n \n i. Whenever a TIU note is printed within DRM, the header will have\n the words "(WORKING COPY)"\n \n j. If the DRM window is open and you change patients within CPRS,\n then the DRM window will now show itself in front of CPRS instead\n of behind it.\n \n k. Previously, in the Visit selection window pull down list, any\n\n
\n 1. Patch 35 exported a new ADA Table, file 228, which supported CDT4\n ADA table. DRM also allows for the sites to change the default ICD9\n This patch should be installed when there are no dental DRM processes\n running. The installation time should take less than 5 minute.\n \n 1. For DSM sites review your mapped set. Disable any of the above\n routines if necessary.\n \n 2. From the Kernel Installation and Distribution System Menu, select \n the Installation menu.\n \n 3. You may elect to use the following options (when prompted\n mapping for a CDT code. The post-install program was suppose to\n for INSTALL NAME, enter DENT*1.2*36): \n a. Backup a Transport Global \n b. Compare Transport Global to Current System \n c. Verify Checksums in Transport Global \n \n 4. Use the Install Package(s) option and select the package\n DENT*1.2*36.\n \n 5. When asked "Want KIDS to INHIBIT LOGONS during the install? Yes//",\n respond "NO".\n restore those local changes to the ADA table. But it did not due to\n \n 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and\n Protocols? YES//", respond "NO".\n \n 7. AXP/DSM Sites - After the patch has been installed, rebuild your \n map set, if necessary.\n \n 8. ********************* NOTE NOTE NOTE ***********************\n Please review the Install log to see if there were any problems\n reported in the post-installation process. If so you will see\n a programming bug. This is fixed in this version. However, this\n text not displayed in the installation example. Following are\n some of the text you may or may not see.\n ******************************************************************\n \n A. WARNING MESSAGES\n These are just warning messages. Nothing is wrong.\n Read all the associated text for more detailed explanations.\n \n >>>>> Local CPT codes not added to the new ADA table <<<<<\n >>>>> CPT codes who had inactive Diagnosis codes mapped to them <<<<<\n patch cannot put back those locally mapped CPT codes that were\n \n \n B. This should never happen.\n If you see this message, just follow the instructions displayed\n \n Unable to lock the ^DENT(228) global. Any local changes not restored\n You can rerun this restore post-install option after the KIDS install\n has completed.\n 1. Get to programmer's mode through Kernel sign-on\n This ensures that the Kernel environment variables are set\n deleted with patch 35.\n 2. Be sure your DUZ(0)="@" - this can be done from programmer's\n mode by VAH>S DUZ(0)="@"\n 3. From programmer's prompt, VAH>D RESTORE^DENTVIP1\n \n 3. Some of the CDT4 codes exported in the patch 35 ADA Mapping Table\n did not have NUM SURFACES indicated when they should have. Thus\n user was not prompted for surfaces within the DRM GUI.\n codes and ICPT*6.0*16 compatibility. Each CPT mapping has 19\n NOIS: CHS-0403-41619\n \n 4. When using Fileman on file 228.1 and entering '??' at the Select\n Dental History prompt, you may get an <UNDEF> error. This was due\n to a bad Identifier on this file.\n NOIS: IND-0403-41306\n \n Technical Description\n ---------------------\n 5. Changes to Data Dictionary for file 228\n associated fields. A few of those CPT codes had incorrect values for\n A. B index changed from a traditional to a Key uniqueness index\n B. DATA TO PUT IN DENT(221) field\n 1) Input transform changed to allow for CHK^DIE to be used as\n that Fileman API does not use the internal record number.\n 2) Executable Help changed to allow to be invoked by Fileman\n APIs that do not require internal record number.\n 3) Changed the field name from DATA TO PUT IN DENT(221) to\n DATA FOR FILE 221.\n C. PRIMARY field - a new set of codes value was entered, Either.\n This code will be used in the future\n some of their fields. While reviewing that table, Dental VAHQ and\n D. FIELD FROM FILE 221 field\n 1) Field type was changed from numeric to free text\n 2) Input transform redone to make it more clear\n 3) Output transform redone to make it more clear\n E. #SURFACES field was renamed to NUM SURFACES\n F. New field added, PREV PRIMARY DIAGNOSIS (#25). This contains\n the default diagnosis for that CPT code in the previous version\n G. Field 1, DX ICD9, was changed to make it required\n \n 6. Changes to routines (tag^routine)\n its coding task group decided to change many other individual field\n A. DENTVDD\n 1) FLD4 - changed from being called by DO to being called by DO\n with parameter passing. For fields 19 and 34 in file\n 221, FLD4 will no longer write to the screen\n 2) FLD4E - changed from being called by DO to being called by DO\n with parameter passing.\n 3) NUM - logic redone to make it more clear\n 4) ID - fixed an <UNDEFINED> error at ID+6\n NOIS: IND-0403-41306\n B. DENTVUTL\n values for quite a few CPT codes.\n 1) CPT - changed to call CPT^DSICCPT. Removed the appending of\n the text '[PRIMARY]' to the CPT short description when\n the ADA table (#228) has the PRIMARY flag set for this\n CPT.\n 2) CPTIEN - changed to call CPT^DSICCPT\n 3) ICD - changed direct global access of data in file 81 to\n calling ICD^DSICCPT\n C. DENTVIP2 - new routine\n \n REQUIRED BUILDS: DENT*1.2*35\n \n ===============\n \n Test Sites:\n ==========\n Manhattan\n Minneapolis\n \n NOIS ADDRESSED BY PATCH\n =======================\n CHS-0403-41619\n 2. The post-installation program in DENT*1.2*35 did not work as\n IND-0403-41306\n \n ROUTINE SUMMARY:\n ===============\n \n The second line of each DENT routine will look like:\n <tab>;;1.2;DENTAL;**[patch list]**;Aug 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- --------------\n intended. DRM allows the sites to add local medical codes to the\n DENTVDD 2851120 2804408 30,35,36\n DENTVIP 1402389 704530 30,32,34,35,36\n DENTVIP1 8913694 8645242 33,34,35,36\n DENTVIP2 -n/a- 14330152 36\n DENTVRP1 4976236 5016139 30,34,36\n DENTVUTL 4283389 3529137 30,33,34,36\n \n INSTALLATION INSTRUCTIONS FOR DENT_1_2P36.KID \n =============================================\n \n\n
\n1.General Information\n the DENTAL TREATMENT file (#221), the leading zeros were dropped from \n station radio button(s) are shown. If there is only one station,\n then that station is pre-selected on the screen.\n \nH.Display all messages when the "DAS record not created" error (or other\n error) is encountered. NOIS: HVH-1203-11045, BRX-1203-11654, \n MIA-1203-31153, NCH-1203-41248, LAH-1203-62134, UNY-0104-10313,\n HWH-0204-40857, MON-0204-50811\n \nI.If the user clicks on the "Add to Quick List" button on the Search form\n and clicks cancel, any new entries will be refreshed on the screen.\n the provider ID number. Only those 4 digit provider IDs whose value was\n \nJ.Due to changes in the law, there is no longer any differentiation of \n the types of POWs. Therefore, CLASS IIB is no longer to be used.\n \nK.Edited unsigned notes will now file correctly in DRM.\n \nL.Notes and Addendums created from the Clinical Record tab will now\n word wrap correctly. Notes will not be allowed to have a future date.\n \nM.A message will be displayed after spell checking has completed.\n less than 1000 were affected. The leading zeros will be replaced and any\n \n6.ENHANCEMENTS TO THE DRM APPLICATION\n ========================================================================\nA.Dental Fee Basis is part of this patch. A new menu option on the DRM\n File Menu displays a screen to enter/edit/delete Fee Basis information\n for the selected dental patient. The Fee Basis information will not be\n transmitted to Austin until the DRM HL7 enhancement has been completed,\n but reports will be available on-line in Patch 38. The new Fee Basis\n option should not be used exclusively at this time. Users should\n continue to use their existing Fee Basis option through VistA which\n affected cross-references will be re-built.\n updates file 222 - DENTAL FEE BASIS (AMIS) since that information is\n being transmitted to Austin.\nB.This patch enables Dental to be billing aware for patches to be released\n in FY2004. PCE changes supporting the billing awareness project is \n PX*1.0*124. The changes to these dental routines will work whether or\n not that PCE patch is installed. The PCE patch preserves the linkage of\n diagnosis codes to a CPT code when a program invokes DATA2PCE^PXAPI such\n as the dental program. The PCE APIs to retrieve the CPT data for a \n VISIT were also modified to return the current diagnosis linkage for\n each CPT code. If that PCE patch is not installed, the dental program\n \n will work as it always has. The two functions affected are the filing\n of data when the FINISH button is clicked and when DRM retrieves \n historical data. The extract (Excel) function will be made billing\n aware in another dental patch.\n \n \n7.NOIS ADDRESSED BY THIS PATCH\n \n=========================================================================\n NYH-1203-11181 TOM-1203-41027 UNY-1203-10667 MAN-0803-11685\n The patch installation process should take be less than 5 minutes.\n HOU-1203-70105 HVH-1203-11045 BRX-1203-11654 MIA-1203-31153\n NCH-1203-41248 LAH-1203-62134 UNY-0104-10313 HWH-0204-40857\n MON-0204-50811\n \n \n8.INSTALLATION FILES\n ========================================================================\n How to Obtain KIDS File\n \n File Name: DENT_1_2P37.zip FTP format: binary\n The post-installation conversion process may take several hours \n \n DENT_1_2P37.zip file will contain the following files:\n FTP \n File Name Description Format\n ------------------ ------------------------------------------ ------\n Dent_1_2p37.kid KIDS file which will install 1 KIDS Builds ASCII\n DENT*1.2*37\n Dentalmrm.exe DRM Version 3.11 executable Binary\n Dent_1_2_p37ug.doc Dental Record Manager's user guide Binary\n The guide was updated for Fee Basis\n depending upon the number of records in file 221 - this process will be\n Dent_1_2p37_rn_ig.doc DENT*1.2*37 Release Notes and Binary\n Installation Guide\n P37_patch_description.txt This file ASCII\n \n The zip file listed above may be obtained via FTP. The preferred \n method is to FTP the files from download.vista.domain.ext\n \n This transmits the files from the first available FTP server. Sites\n may also elect to retrieve software directly from a specific server \n as follows:\n tasked off.\n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n \n \n9.REQUIRED BUILDS: DENT*1.2*31\n DSIC*1.2*1\n XU*8.0*229\n \n \n10.TEST SITES SYSTEM ALPHA/BETA\n \n========================================================================\n Manhattan, NY (VMS DSM) ALPHA\n Bath, NY (VMS DSM) BETA\n Fargo, ND (W2K Cache/Thin Client) BETA\n Tomah, WI (VMS Cache) BETA\n Hines, IL (NT Cache) BETA\n \n ========================================================================\n \n \n11.ROUTINE SUMMARY\n =======================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV031 [*** to be deleted***]\n DENTV03A [*** to be deleted***]\n2.SYSTEM ACCESS DURING INSTALLATION\n DENTV03B [*** to be deleted***]\n DENTV037 n/a 2646025 37\n DENTVFB n/a 2775003 37\n DENTVRF 1357987 1331212 31,37\n DENTVRF0 3183908 3455104 31,37\n DENTVRF1 5110544 5236302 31,37\n DENTVRF2 3458244 4641313 31,37\n DENTVRF3 7764989 7876724 31,37\n DENTVRF4 6882060 7883662 31,37\n DENTVRH 5515191 6429972 31,37\n ========================================================================\n DENTVRP1 5053952 5080599 30,34,36,31,37 \n DENTVRP2 1100213 1429573 30,31,37\n \n \n12.INSTALLATION INSTRUCTIONS FOR DENT*1.2*37\n =======================================================================\n This patch must be installed when there are no dental DRM processes\n running. All open DRM GUI applications must be closed.\n The installation time should take less than 5 minutes.\n \n Installation of this patch does not require users to be off of the \n 1. Obtain the Dent_1_2p37.kid file\n \n 2. For DSM sites review your mapped set. Disable any of the above\n routines if necessary\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu\n \n 4. Use Load a Distribution and enter Dent_1_2p37.kid when prompted\n for a Host file. You may need to attach a directory name\n system. However, all Dental users should not use the DRM GUI option \n \n 5. You may elect to use the following options (when prompted for \n INSTALL NAME, enter DENT*1.2*37)\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 6. Use the Install Package(s) option and select package DENT*1.2*37\n \n 7. For the install prompts, enter either Yes or No depending upon the\n while the patch is being installed. All Dental users MUST close any \n normal practice at your facility. This example shows answering NO:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n 8. AXP/DSM Sites - After the patch has been installed, rebuild your map\n set, if necessary\n \n 9. This step must be completed for this patch to work properly\n open DRM GUI application prior to the patch being installed. Once the \n a. ...\\ will indicate your UNC/path for where the current DRM\n v3.1.0.23 dentalmrm.exe is located\n b. Move dentalmrm.exe to ...\\DOCSTORE\n patch has completed then the users can use the DRM application.\n ********************************************************************\n * There is a new DRM executable exported with this patch. This *\n This patch contains fixes and enhancements to the Dental Record Manager\n * executable MUST be deployed PRIOR to Dental users accessing the *\n * DRM application after the patch has been installed. *\n ********************************************************************\n \n \n3.PRE-INSTALLATION PROCESS\n ========================================================================\nA.A pre-install process will delete the Data Dictionaries for the \n following file and any associated templates (INPUT, PRINT, SORT) and any\n FORMS. No data will be deleted. The file affected is: 228.1\n (DRM) application. This patch also contains a new M Global for DRM in\nB.The pre-install process will also delete field .5 from file 221. This\n field will be reinstalled as part of the patch. The old AF x-ref has\n been replaced with a new Trigger cross-reference to set the .4 field.\nC.The temporary "ACNVT31" cross-reference on file 228.1 will be deleted. \n This cross-reference was used in Patch 31 to keep track of which records\n needed to be converted. \n \n \n4.POST-INSTALLATION PROCESS\n ========================================================================\n the DENT namespace - ^DENT(228.5 for the Fee Basis enhancement.\n The post-install routine will queue up a Taskman job to convert file \n 221. The Provider Number field (.4) in file 221 will be converted if it\n is less than 4 characters long. Leading zeros will be added to the \n number (e.g. 494 will become 0494), and the affected cross-references \n for field .4 will be re-built.\n \n ************************************************************************\n * *\n * THE FOLLOWING STEP BE COMPLETED FOR THIS PATCH TO WORK PROPERLY *\n * *\n \n ************************************************************************\n \n At this point, the KIDS install will have completed. IRM needs to place\n the DRM GUI executable in the appropriate directory. The placement of\n this DRM executable can be done at the same time the KIDS build is being\n installed. The executable must be placed as follows where ...\\ \n indicates your UNC/path for where the current DRM v3.1.0.23\n dentalmrm.exe is located: Move dentalmrm.exe to ...\\DOCSTORE\n \n \n A database conversion will be run as part of the post installation. The\n5.FIXES TO THE DRM APPLICATION\n ========================================================================\nA.Remove screening of dental patient category based on inpatient status.\n NOIS: NYH-1203-11181, TOM-1203-41027, UNY-1203-10667\n \nB.Delete any inactive CPT codes on an users quick list.\n NOIS: MAN-0803-11685\n \nC.Under certain circumstances, DRM did not honor the choice of filing \n flags on a per CPT code basis. Now, it will only file to PCE or DAS\n conversion fixes the dental provider number when the number starts with\n or DES if explicitly indicated. The default is to file to all three.\n Filing to Dental History only will now display the correct date on\n the Dental History tab.\n NOIS: HOU-1203-70105\n \nD.Fixed misspelling of word "immumization" to " immunization" which \n caused a "List Index out of bounds" error when clicking on the \n Immunization button in Clinical Record tab. When immunizations are\n imported into a note, there will be a space and a header before the\n data.\n one or more zeros (as in 0494). Because of an old cross reference on \n \nE.Utilize new rpc call - ORWPS ACTIVE to import meds list into \n the TIU Note and TIU Note Addendum.\n \nF.The default date range in Import Lab Results was always using a date\n range of 180 days back, but now this button uses the user parameter\n for lab days range.\n \nG.Change logic to get default division only if user has more than one\n station. The default division will be pre-selected wherever the\n\n
\n General Information\n (DAS FIELD, DAS DATA) based on the ADA table. The second conversion\n Most of these fields are used in DES Reports.\n \n G. A Fileman error was occurring when entering single letter look-ups\n (e.g., "B") in the Provider lookup screen. This screen is displayed\n when clicking the New button on the Provider Edit screen, or\n when selecting the optional Provider checkbox on the Extract screen,\n or when selecting to file an encounter under another provider's\n name. The error has been fixed. This type of error was also\n occurring on the User lookup screens (User Inquiry and user selection\n within the Administrator Toolbox), and was also fixed.\n changes the DIVISION pointer in file 228.1 from a pointer to file 40.8\n \n H. CPT code search was returning D2950 when the code D2951 was entered.\n This has been fixed.\n \n I. The word 'Extract' was spelled incorrectly on the old Extract History\n Data screen. It's now correct.\n \n J. Consults were not being completed when the user Double-Clicked them,\n only when the consult was single-clicked. Now they will complete\n either way. NOIS: MIA-0304-30860\n to a pointer to file 4. The DD is being sent for this field to change\n \n K. Change the field definition for field 1.18 in the TREATMENT PLAN \n TRANSACTION/EXAM file (#228.2). This field was not used, and will\n now store the HL7 transmission status.\n \n L. A new field called TP RECORD (.06) was added to the TREATMENT PLAN\n TRANSACTION/EXAM file (#228.2). The field will be set to 1 for\n Treatment Plan (DRM+) transactions to differentiate them from DRM.\n \n M. A new field called TREATMENT FLAGS (1.202) was added to the TREATMENT\n the pointers. The final conversion removes the TIU Note pointer data\n PLAN TRANSACTION/EXAM file (#228.2). The field will be contain the\n tooth-related flag.\n \n N. The SURFACES (.16) field in the TREATMENT PLAN TRANSACTION/EXAM file\n (#228.2) was renamed to SURFACES/ROOTS and the field definition now\n allows 1-7 characters (upper/lower) vs only uppercase characters.\n \n \n ENHANCEMENTS TO THE DRM APPLICATION\n ========================================================================\n from file 228.1.\n A. DES Reports are part of this patch. This enhancement provides six \n dental reports for the local VistA system. The reports are:\n Provider Summary, Clinic Summary, Sittings by Provider, Individual\n Sittings, Non-Clinical Time Report, Dental Fee Basis Report. These\n reports are similar to DAS reports of the same name. Reports are \n available on the Tools menu for all users.\n \n B. Provider Add/Edit is part of this patch. This enhancement allows the\n dental administrator to add or edit the dental staff in the DENTAL\n PROVIDER (#220.5) file. A new eight character Dental Provider Id has\n \n been created and will be used in the DES Reports. The old four\n character Dental Provider Id is still required for DAS, but will be\n deprecated when DAS is replaced. Provider Add/Edit is available on\n the Tools menu for administrative users.\n \n C. A new Extract History data option is available on the Tools menu.\n This option does not use RPC calls to get history data, but uses\n instead, a TCP/IP process running on the local machine. When the\n user wants to run the new extract, a process will start in the\n user's system tray and will wait for data from Vista. When the data\n The patch installation process should take be less than 5 minutes.\n has been sent, the Vista M code will send a Shutdown message to stop\n the TCP/IP server. During the patch testing phase for Patch 38, the\n old Extract option will remain enabled along with the new Extract\n option. NOTE! Users will have to contact IRM to get a valid Port#\n to be used with the extract! The user must also know the IP address\n of their workstation in order for the Vista M code to correctly\n connect to the TCP/IP process running on their machine! These\n parameters will be stored on Vista and can be edited/viewed via the\n Parameters button on the new Extract History Data screen.\n \n The post-installation conversion process may take several hours \n D. Fee Basis and Dental Transaction records will start setting the\n "AXMIT" cross-reference correctly ("P" for pending, "C" for canceled)\n in preparation for transmitting HL7 records to AAC.\n \n \n NOIS ADDRESSED BY THIS PATCH\n ========================================================================\n MIA-0304-30860 \n \n \n depending upon the number of records in file 228.1 and 228.2.\n INSTALLATION FILES\n ========================================================================\n How to Obtain KIDS File\n File Name: DENT_1_2P38.zip FTP format: binary\n \n DENT_1_2P38.zip file will contain the following files:\n FTP \n File Name Description Format\n ------------------------ -------------------------------------- ------\n Dent_1_2p38.kid Installable KIDS file ASCII\n This conversion process will be tasked off in the background.\n Dentalmrm.exe DRM Version 3.12 executable Binary\n DRMEXTSRV.exe DRM TCP/IP executable Binary\n Dent_1_2p38_ug.doc Dental Record Manager's user guide Binary\n Updated w/ Reports/Prov Edit/Extract\n Dent_1_2p38_rn_ig.doc DENT*1.2*38 Release Notes and Binary\n Installation Guide\n P38_patch_description.txt A copy of the patch description ASCII\n Patch 38 Enhancements.doc Describing just the enhancements Binary\n \n The zip file listed above may be obtained via FTP. The preferred method\n ========================================================================\n \n is to FTP the files from download.vista.domain.ext\n \n This transmits the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as\n follows:\n \n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n \n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n \n \n REQUIRED BUILDS: DENT*1.2*37\n \n \n TEST SITES SYSTEM ALPHA/BETA\n ========================================================================\n Fargo, ND (W2K Cache/Thin Client) ALPHA\n Manhattan, NY (VMS DSM) BETA\n SYSTEM ACCESS DURING INSTALLATION\n \n \n ROUTINE SUMMARY\n =======================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV037 [*** to be deleted***]\n ========================================================================\n DENTV038 n/a 4808142 38\n DENTV03C n/a 21799174 38\n DENTV03D n/a 21047556 38\n DENTV03E n/a 21447147 38\n DENTV03F n/a 19998119 38\n DENTV03G n/a 1622718 38\n DENTVA1 n/a 10886320 38\n DENTVA2 n/a 12235826 38\n DENTVAU n/a 2285628 38\n DENTVDD1 4809284 5137431 31,38\n Installation of this patch does not require users to be off of the \n DENTVFB 2775003 2787426 37,38\n DENTVIP3 3716294 3714758 31,38\n DENTVRF4 7883662 8576541 31,37,38\n DENTVRH 6429972 6800370 31,37,38\n DENTVRP5 n/a 3121694 38\n DENTVRP8 n/a 3913187 38\n DENTVRP9 6021923 6021572 30,32,34,31,38\n DENTVTP2 n/a 3443632 38\n DENTVUT1 3413708 3440255 31,38\n \n system. However, all Dental users should not use the DRM GUI option \n \n INSTALLATION INSTRUCTIONS FOR DENT*1.2*38\n =======================================================================\n This patch must be installed when there are no dental DRM processes\n running. All open DRM GUI applications must be closed.\n The installation time should take less than 5 minutes.\n \n 1. Obtain the Dent_1_2p38.kid file\n \n 2. For DSM sites review your mapped set. Disable any of the above\n while the patch is being installed. All Dental users MUST close any \n routines if necessary\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu\n \n 4. Use Load a Distribution and enter Dent_1_2p38.kid when prompted\n for a Host file. You may need to attach a directory name\n \n 5. You may elect to use the following options (when prompted for \n INSTALL NAME, enter DENT*1.2*38)\n open DRM GUI application prior to the patch being installed. Once the \n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 6. Use the Install Package(s) option and select package DENT*1.2*38\n \n 7. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. This example shows answering NO:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n patch has completed the users can use the DRM application. Until\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n 8. AXP/DSM Sites - After the patch has been installed, rebuild your map\n set, if necessary\n \n 9. This step must be completed for this patch to work properly\n a. ...\\ will indicate your UNC/path for where the current DRM\n v3.11 dentalmrm.exe is located\n b. Move dentalmrm.exe to ...\\DOCSTORE\n the conversions are complete, the new DRM reports may not give accurate\n c. Move DRMEXTSRV.exe to ...\\DOCSTORE\n (Do not add CPRS menu for this new executable! It is called\n within the DRM application.)\n This patch contains fixes and enhancements to the Dental Record Manager\n results since they need the new DAS FIELD and DAS DATA data in file\n 228.2, and they search for data based on the DIVISION field which is\n also being changed.\n \n ********************************************************************\n * There is a new DRM executable exported with this patch. This *\n * executable MUST be deployed PRIOR to Dental users accessing the *\n * DRM application after the patch has been installed. *\n ********************************************************************\n \n (DRM) application. This patch also contains new M Globals for DRM in\n \n PRE-INSTALLATION PROCESS\n ========================================================================\n The pre-install process will delete field .18(DIVISION) from file 228.1.\n This field will be reinstalled as part of the patch.\n \n The pre-install process will delete the TIU Note pointer from file 228.1.\n This field is no longer used.\n \n The pre-install process will also delete field .16(SURFACE) and 1.18\n the DENT namespace - ^DENT(220.51 and ^DENT(220.52 to support the new \n (TEMP TRANS ID) from file 228.2. These fields will be reinstalled as\n SURFACES/ROOTS and HL7 STATUS, respectively.\n \n \n POST-INSTALLATION PROCESS\n ========================================================================\n The post-install routine will queue up a Taskman job to convert files \n 228.1, (division pointer and removing any TIU Note pointer data) and \n 228.2, (setting DES reporting fields). It will also create a new index\n on file 228.1 for DES reporting ("AG") and re-index the "AF" cross-ref\n eight character Dental Provider Id.\n on file 228.1.\n \n ***********************************************************************\n * *\n * THE FOLLOWING STEP BE COMPLETED FOR THIS PATCH TO WORK PROPERLY *\n * *\n ***********************************************************************\n \n At this point, the KIDS install will have completed. IRM needs to place\n the DRM GUI executable in the appropriate directory. The placement of\n \n this DRM executable can be done at the same time the KIDS build is being\n installed. The executable must be placed as follows where ...\\ \n indicates your UNC/path for where the current DRM v3.11\n dentalmrm.exe is located: \n Move dentalmrm.exe to ...\\DOCSTORE\n Also... the new extract executable needs to be placed in the\n same directory where dentalmrm.exe resides.\n Move DRMEXTSRV.ext to ...\\DOCSTORE\n \n \n Three database conversions will be run as part of the post installation.\n FIXES TO THE DRM APPLICATION\n ========================================================================\n A. The list of Visits that display when the user wants to Delete a \n Dental Encounter will now display in reverse chronological order with\n no duplicates.\n \n B. The information on the Dental History tab will display in reverse\n chronological order by date/time, not just date.\n \n C. If there are no Vital signs to be imported, an extra linefeed was\n The first conversion seeds the new fields in 228.2 for the DES Reports\n appearing in the note - the extra linefeed has been removed.\n \n D. Change the .18 field (DIVISION) in the DENTAL HISTORY file (#228.1)\n From a pointer to file 40.8 (MEDICAL CENTER DIVISION) to a pointer to\n file 4 (INSTITUTION). \n \n F. Add fields DAS FIELD, DAS DATA to the TREATMENT PLAN TRANSACTION/EXAM\n file (#228.2). These fields will be seeded with data during the post\n install conversion. These fields, along with the CTV, VA-DSS GROUP\n fields will be set appropriately when transactions are filed.\n\n\nThis is Dental Patch 21.\n\n
\nGeneral Information\nSYSTEM ACCESS DURING INSTALLATION\n The zip file listed above may be obtained via FTP. The preferred method\n is to FTP the files from download.vista.domain.ext\n \n This transmits the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as\n follows:\n \n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n=========================================================================\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n \n \nREQUIRED BUILDS: DENT*1.2*38\n DSIC 1.3\n \n \nTEST SITES SYSTEM ALPHA/BETA\n======================================================================\nInstallation of this patch does not require users to be off of the system.\nBlack Hills, SD (W2K Cache/Thin Client) ALPHA\nWesthaven, CT VMS/Cache BETA\n \nROUTINE SUMMARY\n======================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\nHowever, if your site is not a DRM Plus (patch 39) site, then the \n DENTV040 n/a 3046754 40\n DENTVHL n/a 13088143 40\n DENTVHL1 n/a 8156724 40\n DENTVHL2 n/a 5154609 40\n DENTVHL3 n/a 4139460 40\n DENTVHLB n/a 16225605 40\n DENTVHLF n/a 7363704 40\n DENTVHLU n/a 3937615 40\n DENTVRF1 5236302 5245545 31,37,40\n DENTVRF2 4641313 4658656 31,37,40\nfollowing instructions apply: Dental users should not use the DRM GUI \n DENTVRF4 8576541 8692191 31,37,38,40\n DENTVUT1 [*** to be deleted***]\n \n \n=========================================================================\n INSTALLATION INSTRUCTIONS FOR DENT*1.2*40\n=========================================================================\n \n 1. Obtain the Dent_1_2p40.kid file\n \napplication while the patch is being installed: all Dental users MUST \n 2. For DSM sites review your mapped set. Disable any of the above\n routines if necessary\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu\n \n 4. Use Load a Distribution and enter Dent_1_2p40.kid when prompted\n for a Host file. You may need to attach a directory name\n \n 5. You may elect to use the following options (when prompted for \nclose any open DRM GUI application prior to the patch being installed: \n INSTALL NAME, enter DENT*1.2*40)\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 6. Use the Install Package(s) option and select package DENT*1.2*40\n \n 7. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. This example shows answering NO:\n Install Questions for DENT*1.2*40\nOnce the patch has completed the users can use\n Incoming Mail Groups:\n \n Enter the Coordinator for Mail Group 'DENTV HL7 MESSAGES':[Name here]\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n 8. AXP/DSM Sites - After the patch has been installed, rebuild your map\n set, if necessary\nthe DRM application.\n \n=========================================================================\n POST-INSTALLATION PROCESS\n=========================================================================\nThe post-install routine will stuff the facility ID of the installing \nsite into the HL7 APPPLICATION PARAMTER file for the two parameters being \nsent with the package. It will also set the DAS turnoff date in the\nnew parameter DENTV DRM DAS TURNOFF to 10/31.2004.\n \nThe post-install will also re-index some entries for the "AXMIT" \n \ncross-reference in file 228.2 (used by the HL7 interface) due to \npotential issues with the Create Date being set as a string.\n \n ************************************************************************\n * *\n * THE FOLLOWING STEPS MUST BE COMPLETED FOR THIS PATCH TO WORK PROPERLY*\n * *\n ************************************************************************\n \nStep 1 is only applicable for sites which have not installed DENT*1.2*39.\n========================================================================\n ********************************************************************\nAll sites must perform steps 2-x.\n \n-------------------------------------------------------------------------\n1 Move dentalmrm.exe\n-------------------------------------------------------------------------\nThis step is only applicable for sites which have not installed \nDENT*1.2*39. '...\\' indicates your UNC/path for where the current DRM \nv3.12 dentalmrm.exe is located.\n Move dentalmrm.exe to ..\\DOCSTORE\n \n * There is a new DRM executable exported with this patch. This *\n-------------------------------------------------------------------------\n2 Set up HL7 link for transmitting DES data to the AAC\n-------------------------------------------------------------------------\n \nThis will demonstrate one way of editing the HL7 link.\nNote: VIE stands for Vitria Interface Engine\n \nVAH>D ^XUP\n Select OPTION NAME: HL MAIN MENU HL7 Main Menu\n ------------\n * executable is only for DRM sites (not DRM Plus sites!) and MUST *\n Select HL7 Main Menu Option: FILER and Link Management Options\n -----\n Select Filer and Link Management Options Option: Link Edit\n ----\n Select HL LOGICAL LINK NODE: DENTVHLAAC\n ----------\n \nYou will now be in a Screenman display. These instructions will direct \nyou to the field that needs editing without actually displaying that \nScreenman display. You will see the field:\n * be deployed PRIOR to Dental users accessing the DRM application *\n LLP TYPE: TCP\n \nMove to the LLP TYPE field. With TCP highlighted, press <ENTER>\nYou should now be in another Screenman display entitled:\n TCP LOWER LEVEL PARAMETERS\n \nYou will see these three fields on this display:\n TCP/IP SERVICE TYPE: CLIENT (SENDER)\n TCP/IP ADDRESS: [ip address] \n TCP/IP PORT: [port] \n * after the patch has been installed. *\n \nA. The TCP/IP SERVICE TYPE should be 'CLIENT {SENDER}'\nB. Change the TCP/IP ADDRESS to your VIE IP address\n 1) If you don't know the VIE IP address, please go to\n http://vista.domain.ext/messaging/vie/vie_projectdocs.asp\n 2) Open the document named VIE Cluster IPs.\n 3) Find your site and use the IP address listed there.\nC. The TCP/IP PORT should be 8090\n This port number is assigned by the VIE team for Dental\n \n ********************************************************************\n \nMove the cursor to the line: COMMAND:\nEnter CLOSE to close the TCP LOWER LEVEL PARAMETERS screen\n \nAt the COMMAND: prompt on the HL7 LOGICAL LINK screen\nEnter EXIT to save your changes\n \nNOTE: the other logical link, DENTVHLHDR, sent in this patch will be used \nin the future to send messages to the Health Data Repository. Do not set \nthis up yet.\n \n \n \n-------------------------------------------------------------------------\n3 Turn on the HL7 link DENTVHLAAC\n-------------------------------------------------------------------------\nThis step will turn the link on to enable the messages to be sent.\n \nWithin the same Filer and Link Management Options menu in the previous \nstep:\n \nFIXES TO THE DRM APPLICATION\nSelect Filer and Link Management Options Option: Start/Stop Links\n -----\nSelect HL LOGICAL LINK NODE: DENTVHLAAC\n ----------\nThe link will be enabled. To stop the link, follow the same steps and \nyou will be prompted if it is Okay to shut down the job. Answer Yes if \nyou want to stop the link.\n \n--------------------------------------------------------------------------\n4 Set up Weekly Scheduled Task\n========================================================================\n--------------------------------------------------------------------------\nYou need to schedule the Dental HL7 Batch option to run once a week. The \nVIE team is responsible for scheduling communication jobs that use the \nVIE. As such, they have assigned SUNDAY as the day that all VAMCs should \nschedule this job to run. The time that the job runs on Sunday is left \nup to the individual sites. On Monday evening, the VIE team will batch \nall the dental HL7 messages received from all VAMCs into a single file \nwhich will be sent to the AAC for processing.\n \nVAH>D ^XUP\nA. When transactions are filed only to the History file and not to DAS,\n \n Select OPTION NAME: XUTM MGR Taskman Management\n --------\nSelect Taskman Management Option: SCHedule/Unschedule Options\n ---\nSelect OPTION to schedule or reschedule: DENTVHLB BATCH Dental HL7 Batch\n --------------\n \nThese two fields need to be properly set:\n QUEUED TO RUN AT WHAT TIME: select a Sunday date/time\nThis patch contains the enhancement to send the Dental Encounter and \n the system will now file the DAS Disposition in the Dental History \n RESCHEDULING FREQUENCY: U@2200\n \nHere is an example of setting up the weekly scheduled option:\n \n Edit Option Schedule\n Option Name: DENTVHLB BATCH \n Menu Text: Dental HL7 Batch TASK ID:\n ________________________________________________________________________\n \n QUEUED TO RUN AT WHAT TIME: NOV 7,2004@22:00\n (#228.1) file correctly. This field contains the 'in progress', \n \nDEVICE FOR QUEUED JOB OUTPUT:\n \n QUEUED TO RUN ON VOLUME SET:\n \n RESCHEDULING FREQUENCY: U@2200\n \n TASK PARAMETERS:\n \n SPECIAL QUEUEING:\n 'completed' or 'terminated' flag. The system will also correctly\n \n__________________________________________________________________________\nExit Save Next Page Refresh\n \nEnter a command or '^' followed by a caption to jump to a specific field.\n \n \nCOMMAND: EXIT Press <PF1>H for help \nInsert\n \n file the Create Date in this case.\n--------------------------------------------------------------------------\n5 Set up a Historical One-Time Scheduled Task\n--------------------------------------------------------------------------\nThe Dental Encounter System (DES) has been gathering data since Oct 2000 \nin file 228. Dental VAHQ would like all that data downloaded to the new \nDES database at the AAC. The amount of data at some sites might be \nextensive. The VIE team and Capacity Management prefer that an option be \nmade available to the sites to move that data to\na CD instead of using bandwidth on the VA WAN for moving those HL7 \nhistorical messages to the AAC. Thus we have provided an option for the \nB. Billing awareness changes were made for the procedure/diagnosis \nsite to schedule at a time that is convenient for the site.\n \nTo estimate the size of the file that will be generated, perform a \nFileman Inquire on file 228.2. The number of records will give you a \nballpark estimate as to the size of the Historical file - each \ntransaction will take just under 1K when formatted as an HL7 message. \nSo, a record count of 55,024 will produce a file of < 55,000K or just \nunder 55meg. Not all records will be sent via the Historical batch of \ncourse, since all records created since the installation of DENT*1.2*38 \nwill be sent via the Vista Interface Engine and the weekly process.\n data being sent to PCE.\n \nNOTE: The historical CD is expected at the AAC within one month of the \nrelease of patch 40.\n \nHere are the instructions for setting up a one-time Scheduled Task for \nthe DENTVHL PROCESS HISTORIC option [menu text: Process one-time \nhistorical extract (Dental)]. Please note that this option will generate \na HFS file with a name like DENTV_HISTORICAL_<site#>.TXT. The file will \nbe located in the directory as defined \nin your Kernel Site Parameters. You can easily see what this value is \n \nfrom the programmer's prompt as shown in this example:\n \nVAH>W $$PWD^%ZISH\nc:\\hfs\\_TO CD\\\n \nOnce the historical option has completed, you will need to copy that file \nto a CD. You will then mail that CD to the AAC. If you choose to FTP \nthe file from your VMS system to another network server, then please \nremember to FTP the file in ASCII (or text) mode. Here is the mailing \naddress for that CD:\nENHANCEMENTS TO THE DRM APPLICATION\n George Dankworth\n Records Management (396B)\n Dental Encounter System\n 1615 Woodward Street\n Austin, TX 78772\n \nExample of setting up the one-time queue option:\n \nVAH>D ^XUP\n \n========================================================================\nSelect OPTION NAME: XUTM MGR Taskman Management\n --------\nSelect Taskman Management Option: SCHedule/Unschedule Options\n ---\nSelect OPTION to schedule or reschedule: DENTVHL PROCESS HISTORIC\n ------------------------\n \nHere is a screen capture of the Taskman Screenman screen showing the \nscheduling of this job:\n \n \n Edit Option Schedule\n Option Name: DENTVHLB BATCH \n Menu Text: Dental HL7 Batch TASK ID:\n ________________________________________________________________________\n \n QUEUED TO RUN AT WHAT TIME: AUG 31,2004@22:00\n \nDEVICE FOR QUEUED JOB OUTPUT:\n \n QUEUED TO RUN ON VOLUME SET:\nDental Fee Basis data to the Austin Automation Center (AAC) via an HL7 \n A. Dental Encounter (DES) and Dental Fee Basis data will be transmitted \n \n RESCHEDULING FREQUENCY:\n \n TASK PARAMETERS:\n \n SPECIAL QUEUEING:\n \n__________________________________________________________________________\nExit Save Next Page Refresh\n \n to the Austin Automation Center (AAC) via HL7 compliant messages. HL7\nEnter a command or '^' followed by a caption to jump to a specific field.\n \n \nCOMMAND: EXIT Press <PF1>H for help \nInsert\n \n \n--------------------------------------------------------------------------\n6 Add Members to Mail Group\n--------------------------------------------------------------------------\n messages will be combined into batches that are compiled weekly and \n \nAn new mail group has been added called DENTV HL7 MESSAGES. Please add \nmembers to this mail group. These should be individuals who will be \nresponsible for taking action if the acknowledgement messages that come \nback from the AAC which contain error codes. These problems need to be \naddressed in the VistA DES database. Those transactions, once fixed, \nwill need to be flagged for retransmission. A good candidate for a \nmember would be the dental administrator for DRM in the Dental Service.\n \nThis is an example of adding a member to this mail group. There are \n sent to the AAC using the Vista interface engine. Batches are \nseveral Kernel options that allow the adding of members to a mail group \nincluding using Fileman. This example just shows one of those options' \ndisplay:\n \nSelect MAIL GROUP NAME: DENTV HL7 MESSAGES\n ------------------\nSelect MEMBER: [add the name of the person to become a member]\n TYPE:\n \n==========================================================================\n limited to 1000 HL7 msgs. There are at least two batches being sent\n SAMPLE INSTALLATION EXAMPLE\n==========================================================================\nSelect Installation Option: INstall Package(s)\nSelect INSTALL NAME: DENT*1.2*40 Loaded from Distribution \n8/31/04@10:09:43\n => DENT*1.2*40 ;Created on Aug 25, 2004@14:15:23\n \nThis Distribution was loaded on Aug 31, 2004@10:09:43 with header of \n DENT*1.2*40 ;Created on Aug 25, 2004@14:15:23\n It consisted of the following Install(s):\n from the local sites, one containing Dental Encounter data and one \n DENT*1.2*40\nChecking Install for Package DENT*1.2*40\n \nInstall Questions for DENT*1.2*40\n \nIncoming Files:\n \n 228.2 TREATMENT PLAN TRANSACTION/EXAM (Partial Definition)\nNote: You already have the 'TREATMENT PLAN TRANSACTION/EXAM' File.\n \n for Dental Fee Basis data. The data transfer will be initialized \n 228.25 DES/HL7 TRANSMISSION\nNote: You already have the 'DES/HL7 TRANSMISSION' File.\n \n 228.5 DENTAL FEE BASIS EXTRACT (Partial Definition)\nNote: You already have the 'DENTAL FEE BASIS EXTRACT' File.\n \nIncoming Mail Groups:\n \nEnter the Coordinator for Mail Group 'DENTV HL7 MESSAGES': [enter name] \n \n through a weekly queued option. The site no longer has to manually \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nDEVICE: HOME// ;P-DEC;80;999 TELNET PORT\n \nInstall Started for DENT*1.2*40 : Aug 31, 2004@10:10:17\nBuild Distribution Date: Aug 25, 2004\nInstalling Routines:........... Aug 31, 2004@10:10:17\nInstalling Data Dictionaries: .... Aug 31, 2004@10:10:18\n start the transmission to the AAC as they did for the Dental Activity \nInstalling PACKAGE COMPONENTS: \nInstalling MAIL GROUP..\nInstalling HL LOGICAL LINK...\nInstalling HL7 APPLICATION PARAMETER......\nInstalling PROTOCOL....\n Located in the DENT (DENTAL) namespace..\n Located in the DENT (DENTAL) namespace..\nInstalling OPTION...\nInstalling PARAMETER DEFINITION.. Aug 31, 2004@10:10:19\nRunning Post-Install Routine: POST^DENTV040.\n System (DAS) data. DAS transmissions will be disabled in another\n >>>>> Updating the DENTV-C, DENTV-F HL7 params with your Facility Name \n<<<<<\n \n >>>>> Updating the DENTV DRM DAS TURNOFF param with date 10/31/2004 \n<<<<<\n \nUpdate of file 228.2 CREATE DATE field successfully queued, task# 361543\nUpdating Routine file\nUpdating KIDS files.......\nDENT*1.2*40 Installed. Aug 31, 2004@10:10:20\ninterface. It also contains enhancements to the Dental Record Manager \n DRM patch.\n \n B. Historical Dental Encounter data (transactions filed before DRM patch\n 38 was installed) will be sent to the AAC via a CD. An option is \n available to create these HL7 messages and put them into a file on \n a server. The file needs to be copied onto a CD and mailed to the \n AAC.\n \n C. A new parameter DENTV DRM DAS TURNOFF contains a date which controls\n the filing of data to DAS (file 221). When the date is reached, DRM\n(DRM) application.\n will no longer offer the File DAS Only option and will not file any\n data to file 221 even when filing to All (DES, PCE are now the only\n filing choices). Also, the old 4 digit Provider ID will no longer\n be required when adding/editing dental providers. The turnoff date \n is defaulted to 10/31/2004.\n \n D. When the user looks up providers (in the Extract, Provider Add/Edit\n options, the provider list will now contain their initials and title\n to help differentiate users with the same name.\n \n \n E. Combat Veteran status has been added to the Service Connected\n selection page.\n \n F. The text of the filing options was changed from "File DAS/PCE..." to\n "File Data...".\n \n \nNOIS ADDRESSED BY THIS PATCH\n========================================================================\nBRX-0804-10469 NOL-0804-70250 CLL-0804-40357 MON-0804-51726\nThe patch installation process should take be less than 5 minutes.\n \n \nINSTALLATION FILES\n========================================================================\n How to Obtain KIDS File\n File Name: DENT_1_2P40.zip FTP format: binary\n \n DENT_1_2P40.zip file will contain the following files:\n FTP \n File Name Description Format\n \n ----------------------- ------------------------------------- ------\n Dent_1_2p40.kid Installable KIDS file ASCII\n Dentalmrm.exe DRM Version 3.13 executable Binary \n Dent_1_2p40_ug.doc Dental Record Manager's user guide Binary\n The guide was updated for HL7/DAS turnoff\n and Combat Veteran status flag\n Dent_1_2p40_rn_ig.pdf DENT*1.2*40 Release Notes and Binary\n Installation Guide\n P40_patch_description.doc A copy of the patch description Binary\n \n\n\n General Information\n RVU and DSS Product line data will be set into existing transactions \n \n The pre-install process will delete field 4.06 in file 228.2 because\n the DESCRIPTION field was changed to a word processing field 4.1. If\n field .04 (PLAN NUMBER) in file 228.6 exits, it will be deleted as it\n is no longer used.\n \n \n POST-INSTALLATION PROCESS\n ========================================================================\n \n from file 228 DENTAL CPT CODE MAPPING. New System parameters required\n Please read the post-installation instructions which follow the\n installation instructions. All the steps in the post-install must be\n completed for DRM Plus to function properly.\n \n \n NOIS ADDRESSED BY THIS PATCH\n ========================================================================\n BRX-0804-10469 NOL-0804-70250 CLL-0804-40357 MON-0804-51726\n BRX-0804-11357\n \n for DRM Plus will be seeded with default data.\n \n INSTALLATION FILES\n ========================================================================\n How to Obtain KIDS File\n File Name: DENT_1_2P39.zip FTP format: binary\n \n DENT_1_2P39.zip file will contain the following files:\n FTP \n File Name Description Format\n ----------------------- ------------------------------------- ------\n \n Dent_1_2p39.kid Installable KIDS file ASCII\n Dentalmrmtx.exe DRM Version 4.01 executable Binary\n SETUP.EXE Initial CVision install file Binary\n VBRUN60SP6.EXE Microsoft VB 6.0 SP6 runtime files Binary\n MDAC_TYP.EXE Microsoft Data Access Components v2.8 Binary\n UPDATE.EXE Subsequent CVision updates as necessary Binary\n Dent_1_2p39_ug.doc Dental Record Manager's user guide Binary\n The guide was updated for DRM Plus\n Dent_1_2p39_rn_ig.pdf DENT*1.2*39 Release Notes and Binary\n Installation Guide \n **NOTE** Dental administrators are responsible for entering RVU and\n P39_patch_description.doc A copy of the patch description Binary\n \n The zip file listed above may be obtained via FTP. The preferred method\n is to FTP the files from download.vista.domain.ext\n \n This transmits the files from the first available FTP server. Sites may\n also elect to retrieve software directly from a specific server as\n follows:\n \n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n VA-DSS Product Line information into the system for *ALL* locally mapped\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n \n \n REQUIRED BUILDS: DENT*1.2*38\n DSIC 1.3\n \n10.TEST SITES SYSTEM ALPHA/BETA\n medical (CPT) codes! This information will be required for processing\n ====================================================================\n San Diego, CA (VMS Cache) ALPHA\n Black Hills, SD (W2K Cache/Thin Client) ALPHA\n Manhattan, NY (VMS Cache) BETA\n Daytona (Gainesville) (VMS, DSM) BETA \n Manchester (VMS Cache) BETA\n Bath, NY (VMS DSM) BETA\n Fargo, ND (W2K Cache/Thin Client) BETA\n Boston, MA (VMS Cache) BETA\n Miami, FL (VMS, DSM) BETA\n transactions that are sent to Austin after patch 40 is installed. See\n Houston, TX (VMS DSM) BETA\n \n ROUTINE SUMMARY\n ======================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV038 [*** to be deleted***] \n the post-installation instructions for details on entering this\n DENTV03C [*** to be deleted***] \n DENTV03D [*** to be deleted***] \n DENTV03E [*** to be deleted***] \n DENTV03F [*** to be deleted***] \n DENTV03G [*** to be deleted***] \n DENTV039 n/a 10652042 39\n DENTV39A n/a 1146103 39\n DENTVA1 10886320 12453282 38,39\n DENTVA2 12235826 14211342 38,39\n DENTVAU 2285628 2840803 38,39\n information.\n DENTVDD1 5137431 5150464 31,38,39\n DENTVIP1 8645242 7061918 33,34,35,36,39\n DENTVIP2 14330152 14335172 36,39\n DENTVIP3 3714758 5003597 31,39\n DENTVRH 6800370 7889749 31,37,38,39\n DENTVRHD 1034441 1569611 31,39\n DENTVRP1 5080599 5103649 30,34,36,31,37,39\n DENTVRP3 6062351 6412654 30,32,35,31,39\n DENTVRP8 3913187 4052725 38,39\n DENTVRP9 6021572 6935679 30,32,34,31,38,39\n ========================================================================\n \n DENTVTP0 n/a 830603 39\n DENTVTP1 n/a 5103282 39\n DENTVTP2 3443632 2998057 38,39\n DENTVTP3 n/a 5419608 39\n DENTVTP4 n/a 10224521 39\n DENTVTP5 n/a 4674885 39\n DENTVTP6 n/a 5267534 39\n DENTVTP7 n/a 3312894 39\n DENTVTPA n/a 4823862 39\n DENTVTPB n/a 8540067 39\n The patch installation process should take be less than 5 minutes.\n DENTVTPC n/a 10530540 39\n DENTVTPD n/a 6502580 39\n \n \n INSTALLATION INSTRUCTIONS FOR DENT*1.2*39\n =======================================================================\n This patch must be installed when there are no dental DRM processes\n running. All open DRM GUI applications must be closed.\n The installation time should take less than 5 minutes.\n \n The post-installation conversion process may take several hours \n 1. Obtain the Dent_1_2p39.kid file\n \n 2. For DSM sites review your mapped set. Disable any of the above\n routines if necessary\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu\n \n 4. Use Load a Distribution and enter Dent_1_2p39.kid when prompted\n for a Host file. You may need to attach a directory name\n depending upon the number of records in file 228.2. This conversion \n \n 5. You may elect to use the following options (when prompted for \n INSTALL NAME, enter DENT*1.2*39)\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 6. Use the Install Package(s) option and select package DENT*1.2*39\n \n 7. For the install prompts, enter either Yes or No depending upon the\n process will be tasked off in the background.\n normal practice at your facility. This example shows answering NO:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n 8. AXP/DSM Sites - After the patch has been installed, rebuild your map\n set, if necessary\n \n 9. The post-install routine queues up a Taskman job to add RVU and \n \n Product Line information into existing transactions in file 228.2.\n The post install will also add, edit or delete certain parameter \n instances for DRM Plus and will add the locally added CPT codes back\n into file 228.\n \n POST INSTALLATION INSTRUCTIONS\n ========================================================================\n ***********************************************************************\n * THESE STEPS SHOULD NOT BE COMPLETED UNTIL YOUR SITE IS SCHEDULED *\n * FOR DRM PLUS TRAINING! *\n \n ***********************************************************************\n \n 1. At this point, the KIDS install will have completed. IRM must place\n the DRM GUI executable in the appropriate directory. The placement\n of this DRM executable can be done at the same time the KIDS build is\n being installed. The executable must be placed as follows where ...\\ \n indicates your UNC/path for where the current DRM v3.12 dentalmrm.exe\n is located: Move dentalmrmtx.exe to ...\\DOCSTORE\n \n 2. Create a CPRS Tools menu option for this new executable\nENHANCEMENTS TO THE DRM APPLICATION\n Add the DRM Plus option to the CPRS Tools Menu with these params:\n ...\\DOCSTORE\\DENTALMRMTX.EXE S=%SRV P=%PORT D=%DFN TX=1\n Note that the executable name is different than the current DRM\n executable and the parameters contain a new string TX=1 which stands\n for Treatment Plan - the new GUI display. If you do not include this\n new parameter, the Dental program will look like the existing DRM\n application and none of the new features will be available to the\n dental user.\n \n 3. Client PC setup\n ========================================================================\n There are DRM Plus support files that MUST be installed on each \n Windows client PC that will be running the DRM GUI application.\n You must have local Administrative privileges on the client PC to\n properly install these files. See the installation steps below for\n details.\n \n a. Update the client machines (need Administrator privileges) by\n running the SETUP.EXE, VBRUN60SP6.EXE, and MDAC_TYP.EXE programs\n in that order.\n \n A. DRM Plus - an entirely new visually enhanced GUI is part of this \n b. Reboot the machine and log in again as the administrator to\n complete the installation process!\n \n c. Once you have installed the three programs in step 4.a. and you\n need to reinstall this patch (or if test sites are upgrading to a\n newer version of the patch), then you only have to run the\n UPDATE.EXE file to upgrade the DRM Plus client files.\n UPDATE.EXE does not require administrator privileges.\n Keep these three client installation files for future use\n e.g. when new pcs are added to the dental clinic, etc.\n This patch contains fixes and enhancements to the Dental Record Manager\n patch. DRM Plus contains screens to edit Perio, PSR and Head/Neck \n \n 4. Adding or Editing Local CPT Codes\n a. This step needs to be done by the dental administrator. This is\n not an IRM function at most sites. This step can be completed any\n time after the patch has been installed. This step should be\n completed before the dental users are given access to the DRM Plus\n application. If not, then it is possible that those users will\n select these locally added CPT codes. Since no RVUs nor VA-DSS\n Product Line values are mapped, then no dental workload will be\n transmitted to the new Dental Encounter System database in Austin\n lesion data as well as the enhanced visual screens for general \n once patch DENT*1.2*40 is released.\n \n b. The dental administrator needs to update RVU and VA-DSS Product Line\n values for any CPT codes which the site might have added to the ADA\n Mapping Table (#228). If the site has not added any CPT codes to\n this table, then this step can be skipped. The dental administrator\n will edit this information using the DRM Plus GUI program.\n 1) In DRM Plus, select the 'Treatment & Exam' menu\n 2) Within this menu, select the option 'Edit CPT/DCode Field\n Values'\n dentistry.\n 3) Search for the locally added CPT codes and enter the appropriate\n values. Click OK to file the information.\n \n B. RVU data will be stored with the ADA codes and will be shipped with\n with the DENTAL CPT MAPPING table (#228). For locally added codes, \n users will be able to edit RVU and VA-DSS Product Line information.\n \n C. DES Reports that were created in DRM Patch 38 have been enhanced to\n allow screening of transaction status (complete, pending, deleted) \n (DRM) application. This patch also contains new files for DRM in the\n and patient type (active, inactive). The Summary Reports \n provider/clinic) now allow the user the option to print only the \n third page totals.\n \n D. The New Extract option that was created in DRM Patch 38 has been\n enhanced to allow screening of transaction status (complete, pending,\n findings and observe). Both Extract options have been changed to\n output RVU and transaction status data to the text file.\n \n E. Selection of patient visits now offers a new radio button to view\n DENT namespace - ^DENT(228.6) which contains tooth notes and\n only Dental Visits (and Scheduled appointments for Dental). Dental\n Visits are those where the location has a stop code of 180 or 181.\n The Dental Visits radio button is now the default selection,\n instead of the All button.\n \n F. Combat Veteran status has been added to the Service Connected\n selection page.\n \n G. The DRM Plus application will no longer ask the user if they want to\n close the application after they have hit the close button.\n ^DENT(228.7) which contains reserved transactions. The ^DENT global\n \n H. Users will no longer be prompted for # of Canals. If the ADA code\n in the ADA Mapping table (#228) is marked for Canals, then DRM Plus\n will use that value for the transaction.\n \n I. Users have the option of saving dental information in a temporary\n workspace at any time in the DRM Plus workflow. The user may close \n DRM Plus or change patients and the system will prompt to save the \n currently entered information without having to click the Finish \n button. When the user re-opens DRM Plus for the patient with saved\n should already exist on your system so no global placement is required.\n data, the system will prompt to re-load the information and the\n user can continue through the screens.\n \n J. The user will only see active providers when selecting co-signers.\n \n SYSTEM ACCESS DURING INSTALLATION\n ========================================================================\n Installation of this patch does not require users to be off of the \n system. However, all Dental users should not use the DRM GUI option \n while the patch is being installed. All Dental users MUST close any \n \n open DRM GUI application prior to the patch being installed. Once the \n patch has completed the users can use the DRM application.\n \n ********************************************************************\n * There is a new DRM executable exported with this patch, called *\n * dentalmrmtx.exe. This executable will NOT be used until the *\n * site has scheduled training for DRM Plus. The site should *\n * continue to use the old executable (dentalmrm.exe) against the *\n * the DENT*12.*39 KIDS build until that time. *\n * *\n A database conversion will be run as part of the post installation.\n * ** There are also new Client-side components that must be ** *\n * installed for the new executable to work properly!! *\n * ** Please read the post-installation instructions thoroughly! ** *\n * *\n ********************************************************************\n \n PRE-INSTALLATION PROCESS\n ========================================================================\n The pre-install process will save off the current ADA table (file 228)\n in preparation for re-loading new ADA data. \n\n
\n General Information\n \n =======================================================================\n The following fixes apply to DRM and DRM Plus:\n 1. One of the routines in DENT*1.2*40 was not compatible with DSM and\n caused an error trying to run. This routine was modified to be able\n to be run on either Cache or DSM and is included in this patch so\n that all sites are running the same version of the routine.\n \n 2. The Fee Basis report will display data for facilities with alpha\n characters in their id (e.g. 674A4). NOIS: CTX-1004-72255\n \n ENHANCEMENTS TO THE DRM/DRM Plus APPLICATION\n 3. The Summary Reports (Provider and Clinic) will now print the correct\n Totals number. NOIS: LEX-1104-41679\n \n 4. Fixed a bug when loading the boilerplate of a TIU title in the \n progress note screen of the Clinical Record tab if a Consult-type \n was selected. The IEN of the previous note title was passed to the \n broker call instead of the currently selected title which could \n result in the wrong boilerplate. \n \n -----DRM ONLY-----\n =======================================================================\n 5. Leaving the 4 digit Provider Id blank for more than one provider\n will no longer give the user a 'duplicate id' error message. (Note:\n the 4 digit Provider Id is still required to file Admin time in DRM,\n if you are using that feature.) NOIS:PUG-1104-50509\n \n -----DRM Plus ONLY-----\n 6. D6999 will no longer change the graphical display in DRM Plus and\n D4211 will prompt for tooth and not quadrant. D2940 will now paint\n the correct graphic for restoration. D2999 and D3999 will not\n paint graphics.\n The following enhancements apply to DRM and DRM Plus:\n \n 7. The system will now automatically display signed notes for user \n selection in the Addendum screen. \n \n 8. Changed display of FGM values in the progress note output of Perio \n Exams ("+" for positive values, actual value for numbers between \n 1 - 9, and "*" for values greater than 9). \n \n 9. The HL7 message generator will no longer generate invalid transaction\n messages for DRM Plus connecting bar type transactions.\n A. The following VistA DAS options will be disabled:\n \n 10. Changed the legend/symbol definition for FGM at the bottom of the \n Perio Exam progress note output ("FGM coronal to CEJ"). \n \n 11. Allow DRM Plus to minimize if filing Problem List results in a \n "duplicate filing" error message. \n \n 12. Duplicate Problems will no longer be filed.\n \n 13. Changed the message (disclaimer) on top of the Perio Exam progress \n \n note text to "This is textual display of periodontal findings, \n please see DRM Plus for perio charting graphic."\n \n 14. Automatically display the Visit selection form without having to \n click the "..." button on the second page of the Treatment Chart \n tab after the Next button is clicked.\n \n 15. When PCE filing errors occur, the system will not try to back out\n DAS transactions since they are no longer filed.\n \n Menu/Option Name Description \n 16. Correctly assign the provider initials in the transaction list\n when the user enters a bridge, connecting bar or partial.\n NOIS:MIA-1104-31314, PUG-1204-51038\n \n 17. Fixed an intermittent issue with completed procedures not \n generating a code description in the progress note.\n \n 18. Corrected the translation of "Miscellaneous" material in \n Diagnostic Findings transactions to display the text "Misc"\n in the progress note. Because Miscellaneous is internally \n ------------------------------ ----------------------------------------\n mapped as Unknown, no material is displayed with the tooth \n in the progress note for transactions such as existing \n Restorations.\n \n 19. The Multi Add button will now be enabled/disabled for the\n appropriate DCodes.\n \n 20. Fixed a bug where 'Observe' type transactions were trying to be sent\n through the HL7 interface and generating an error. Only Completed,\n non-observe transactions should be transmitted. NOIS: MIN-1204-40802\n DENT GECS BATCH Batch Code Sheets \n \n 21. Changed the order of the lower PSR values based on a request by\n the dental development group.\n \n 22. Changed the link to the VA Intranet Website under Help menu to \n http://vaww1.domain.ext/drmplus1/. (Note: this link is outside the VA\n network firewall). \n \n 23. The progress note text width component code was updated. The\n progress note screens: regular note, addendum, and Clinical \n DENT GECS BATCH EDIT Batch Edit \n Record tab note, will wordwrap the text properly at the designated\n width (usually 74 characters wide). \n \n 24. Copyright information updated to show "1998 - 2005" in the \n Help/About menu option. \n \n 25. Fixed the "List index out of bounds" error message when clicking \n the Back button and changes in the text were detected with/without\n the text marker. \n \n =======================================================================\n DENT GECS BATCHES STATUS Status of all Batches \n 26. Disabled the "No" button on the save data prompt when selecting the\n "Save unfiled data" menu option. Disabled the "Cancel" button on the\n save data prompt when switching patient. \n \n 27. Replaced the "Additional Notes" section label with a dashed line \n (60 characters wide) in the progress note. Changed the "Additional\n Notes" treeview item to "Insert Text Marker" so the user can \n manually insert the marker in the progress note. \n \n 28. The Text Marker section marker is automatically inserted \n DENT GECS BATCHES WAITING TRAN Batches Waiting to be Transmitted \n when a CPRS template or TIU boilerplate is imported when the note\n title selection is presented for the first time. \n \n 29. A warning message will be presented to the user if changes were \n made to the progress note text and the Text Marker is not found.\n or, if changes occur above the original placement of the \n Text Marker.\n \n 30. Added a new checkbox "Default treeview display to DRM objects" in\n the User Options under the Treatment System tab. This allows the \n DENT GECS CODE EDIT Code Sheet Edit \n user to select which treeview display the user prefers in the \n progress note. (DRM Objects is the default.)\n \n 31. The following changes were made to the DRM Plus client component:\n a. The message "There are no appointments" which could show up in \n some situations has been removed.\n b. Clicking on "Perio Buttons" and then clicking on a tooth will no\n longer show the ADA Codes list. \n c. The periodontal statistics will now accurately reflect the total \n number of sites and teeth for furcation and MGJ. Teeth without \n DENT GECS CREATE Create a Code Sheet \n periodontal readings such as missing or denture will also be \n accounted for correctly.\n d. Fix drawing error when adding a partial on a tooth with an \n implant and a coping.\n e. When adding a connecting bar over missing teeth, the missing\n teeth will no longer display a hollow crown image.\n f. Bridge and partial transactions will now be added with the \n correct provider.\n g. Problem where patient notes were being duplicated when changing\n dates and clicking "Show All" has been resolved.\n DENT GECS DELETE Delete a Code Sheet \n h. When adding a pontic to an implant which has a coping on it; \n implant will be removed appropriately.\n i. Clicking Add in Multi-Add without selecting a tooth or \n quadrant will not generate a run-time error.\n j. The default code for an extracted implant is now D6100.\n k. Probing will now be allowed on all retained roots. \n l. Extracted roots will now display in the transaction list as \n "Extract" when completed or planned.\n m. The ability to "Cancel" the Extract bridge dialog has been added.\n n. Notes cannot be added without first adding a transaction.\n DENT GECS KEYPUNCH Keypunch a Code Sheet \n o. Apostrophes will be stripped from the SpeedCode name in order to\n prevent a run-time error.\n p. The dentition message which tells the user to use the individual\n dentition button has been modified to be more accurate.\n q. The H&N date filter now works appropriately.\n r. Sealant markers will now draw on top of cracked occlusal \n surfaces appropriately.\n s. Defective materials will never display in treatment plan or \n completed care.\n t. The default code for a coping on an implant has been changed \n DENT GECS PURGE Purge Transmission Records/Code Sheets\n from D6020 to D6056.\n \n \n SYSTEM ACCESS DURING INSTALLATION\n =======================================================================\n Installation of this patch does not require users to be off of the \n system. However, all Dental users should not use the DRM or DRM Plus \n GUI option while the patch is being installed. All Dental users MUST\n close any open DRM or DRM Plus GUI application prior to the patch being\n installed. Once the patch has completed, DRM users can use the \n DENT GECS READY FOR BATCHING L Code Sheets Ready for Batching \n application. DRM Plus users must have a client update performed on\n their machine.\n \n POST-INSTALLATION PROCESS\n ========================================================================\n The KIDS post-install routine will do the following:\n 1. Disable the DAS options listed in the Enhancements section of this\n document. The options will be turned off by setting the Out Of Order\n Message to 'DAS turned off'.\n 2. Change the Condition/Area/Material for some DCodes so that the DRM \n DENT GECS REBATCH Mark Code Sheets for Rebatching \n Plus graphics will paint correctly.\n 3. Set a new multi-add flag to DCodes to better enable/disable this DRM\n Plus feature for the appropriate DCodes. \n 4. Remove the HL7 'pending' x-ref for all Observe DRM Plus transactions.\n 5. Set the new DRM Plus Treeview parameter (DENTV TP TREEVIEW DEFAULT)\n to Yes.\n \n ***********************************************************************\n * *\n * THE FOLLOWING STEP BE COMPLETED FOR THIS PATCH TO WORK PROPERLY *\n DENT GECS RETRANSMIT Mark Batch for Retransmission \n * *\n ***********************************************************************\n \n After the KIDS install has completed, IRM needs to place the DRM\n executable (dentalmrm.exe) or the DRM Plus executable (dentalmrtx.exe)\n in the appropriate directory. If you are a DRM Plus site, then you also\n must complete some additional client setup on client pcs or thin client \n servers. See the installation steps below for details. \n \n NOIS ADDRESSED BY THIS PATCH\n This patch sets the Out Of Order message on various Dental Activity \n DENT GECS REVIEW CODE SHEET Review a Code Sheet \n =======================================================================\n CTX-1004-72255 PUG-1104-50509 MIA-1104-31314 DUR-1004-31962\n LEX-1104-41679 MIN-1204-40802 PUG-1204-51038\n \n REQUIRED BUILDS: DENT*1.2*40\n DENT*1.2*39\n \n INSTALLATION FILES\n =======================================================================\n How to Obtain KIDS File and client applications:\n DENT GECS TRANSMIT Transmit Code Sheets \n File Name: DENT_1_2P42.zip FTP format: binary\n \n DENT_1_2P42.zip file will contain the following files:\n FTP\n File Name Description Format\n ----------------- ------------------------------------- ------\n Dent_1_2p42.kid Installable KIDS file ASCII\n Dentalmrm.exe DRM V3.1.4.0 executable Binary\n Dentalmrmtx.exe DRM Plus V4.0.0.49 executable Binary\n setup.EXE Initial CVision (client) install file Binary\n DENT GECS MAIN MENU DENTAL Code Sheet Manager Menu \n update.EXE Subsequent CVision updates (client) Binary\n vbrun60sp6.exe Microsoft VB 6.0 SP6 runtime files (client) Binary\n Mdac_typ.exe Microsoft Data Access Components v2.8 (client)Binary\n Dent_1_2p42_rn_ig.pdf DENT*1.2*42 Release Notes and Binary\n Installation Guide \n P42_patch_description.txt A copy of the patch description ASCII\n DRM Plus Manual.pdf User guide for DRM Plus Binary\n \n The zip files listed above may be obtained via FTP. The preferred \n method is to FTP the files from download.vista.domain.ext\n DENT GECS MAINTENANCE USER MEN Maintenance Menu \n \n This transmits the files from the first available FTP server. Sites \n may also elect to retrieve software directly from a specific server \n as follows:\n \n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n DENT GECS REPORTS MENU Reports Menu \n \n \n TEST SITES DRM Plus? SYSTEM ALPHA/BETA\n =====================================================================\n SAN DIEGO yes VMS Cache ALPHA\n BOSTON yes VMS Cache/Thin Client BETA\n FARGO yes W2K Cache/Thin Client BETA\n WESTERN NY no VMS Cache BETA\n \n \n DENT GECS TRANSMIT USER DENTAL Code Sheet Transmission Menu \n ROUTINE SUMMARY\n =====================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV039 [*** to be deleted***] \n DENTV39A [*** to be deleted***] \n DENTV040 [*** to be deleted***] \n DENT GECS USER MENU DENTAL Code Sheet User Menu \n DENTV041 [*** to be deleted***] \n DENTV042 n/a 8320931 42\n DENTVA2 14211342 14282966 38,39,42\n DENTVHL 13088143 13364754 40,42\n DENTVHL2 5154609 5154663 40,42\n DENTVRP4 9233470 9298307 30,32,31,42\n DENTVTIX n/a 314768 42\n DENTVTPA 4823862 4902746 39,42\n DENTVTPC 10530540 10565254 39,42\n \n DENTAPP Appointments \n INSTALLATION INSTRUCTIONS FOR DENT*1.2*42\n ======================================================================\n This patch can be installed while users are on the system.\n The installation time should take less than 1 minute.\n \n 1. Obtain the Dent_1_2p42.kid file\n \n 2. For DSM sites review your mapped set. Disable any of the above\n routines if necessary.\n \n DENTCPA1 Control Point Activity Enter/Edit\n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n \n 4. Use Load a Distribution and enter Dent_1_2P42.kid when prompted\n for a Host file. You may need to attach a directory name.\n \n 5. You may elect to use the following options (when prompted for \n INSTALL NAME, enter DENT*1.2*42)\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n DENTCPA2 Print/Display Control Point Activity \n c. Verify Checksums in Transport Global\n \n 6. Use the Install Package(s) option and select package DENT*1.2*42\n \n 7. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. This example shows answering NO:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n System (DAS) options within VistA so that these options may no longer \n DENTOUT Outputs \n \n 8. AXP/DSM Sites - After the patch has been installed, rebuild your \n map set, if necessary\n \n =======================================================================\n POST-INSTALLATION PROCESS\n =======================================================================\n \n 1. If your site is running dentalmrm.exe (DRM), then\n Move dentalmrm.exe to ...\\DOCSTORE and you are done!\n DENTRELEASE Review/Release Service Reports \n '...\\' indicates your UNC/path for where DRM is located.\n \n 2. If your site is running dentalmrmtx.exe (DRM Plus)\n Move dentalmrmtx.exe to ...\\DOCSTORE\n '...\\' indicates your UNC/path for where DRM Plus is located.\n Run update.exe on all client machines that will launch DRM Plus (or\n all thin client servers if you are a thin client site). Update.exe\n does not require the installed to be an administrator.\n *********************************************************************\n Please be careful to coordinate the server/client updates with each \n DENTSCHED Scheduling \n other so that the dental application works properly. You will know \n if the server/client files are not compatible because launching DRM \n Plus will cause approximately 30 client errors. This also means that\n you must carefully coordinate testing the new application in the TEST\n account since you must run update.exe on a rarely used machine for \n the dental staff to test against, as they will not be able to run the\n production side application after running the new update.exe.\n *********************************************************************\n \n These are the DRM Plus files you are currently running from patch 39:\n DENTSUP Supervisor \n dentalmrmtx.exe version 4.0.0.481 dated 10/1/2004 5:44pm (server)\n update.EXE contains CVision.ocx dated 10/1/2005 3:09pm (client)\n *setup.EXE new client install dated 10/1/2005 3:10pm (client)\n \n These are the new DRM Plus files from patch 42:\n dentalmrmtx.exe version 4.0.0.49 dated 1/5/2004 10:33am (server)\n update.EXE contains CVision.ocx dated 1/4/2005 10:50am (client)\n *setup.EXE new client install dated 1/6/2005 9:20am (client)\n \n *you only need setup.EXE to set up a new client machine, see step 3.\n DENTTREAT RELEASE Treatment Data Review/Release Menu \n \n 3. If your site is a DRM Plus site and has any new PCs, or new thin \n client SERVERS that need to be able to run DRM Plus, then you must be\n on the VHA domain and install the following files as an administrator\n of the machine: setup.EXE, vbrun60sp6.exe, Mdac_typ.exe and REBOOT \n the machine. \n \n If your site is about to be trained on DRM Plus and you need to set \n up the training room and/or dental PCs/thin client SERVERS, then the\n files in the Dent_1_2p42.zip file supercede any files you may have \n DENT AMIS DELETE Delete Dental AMIS (Temporary) Global \n saved from the patch 39 installation. Check the dates above to \n insure you are installing the correct/latest files.\n \n ========================================================================\n SAMPLE INSTALLATION\n ========================================================================\nSelect Installation Option: INStall Package(s)\nSelect INSTALL NAME: DENT*1.2*42 Loaded from Distribution \n1/5/05@09:13:44\n => DENT*1.2*42T6 ;Created on Jan 05, 2005@09:13:13\n DENT AMIS TAPE Generate Monthly Dental AMIS Tape \n \nThis Distribution was loaded on Jan 05, 2005@09:13:44 with header of\n DENT*1.2*42T6 ;Created on Jan 05, 2005@09:13:13\n It consisted of the following Install(s):\n DENT*1.2*42\nChecking Install for Package DENT*1.2*42\nInstall Questions for DENT*1.2*42\nIncoming Files:\n \n 228.2 TREATMENT PLAN TRANSACTION/EXAM (Partial Definition)\n DENT SERVICE DELETE Delete Dental Service (Temporary) Global \nNote: You already have the 'TREATMENT PLAN TRANSACTION/EXAM' File.\n \nWant KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\nWant KIDS to INHIBIT LOGONs during the install? YES// NO\nWant to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \nEnter the Device you want to print the Install messages.\nYou can queue the install by enter a 'Q' at the device prompt.\nEnter a '^' to abort the install.\n \n DENT SERVICE TAPE Generate Monthly Dental Service Tape \nDEVICE: HOME//\n DENT*1.2*42\n -----------------------------------------------------------------------\n Install Started for DENT*1.2*42 :\n Jan 05, 2005@09:15:28\n Build Distribution Date: Jan 05, 2005\n Installing Routines:\n Jan 05, 2005@09:15:28\n Installing Data Dictionaries:\n Jan 05, 2005@09:15:29\n DENTADM EDIT Class I-VI (type 3) Admin Info Enter/Edit \n Installing PACKAGE COMPONENTS:\n Installing OPTION\n Installing PARAMETER DEFINITION\n Jan 05, 2005@09:15:29\n Running Post-Install Routine: POST^DENTV042\n \n >>>>> Inactivating DAS options in VistA <<<<<\n >>>>> Fixing D6999,D4211,D2940,D2999,D3999 for DRM Plus graphics <<<<<\n >>>>> Setting the Multi-Add flag for DRM Plus DCodes <<<<<\n >>>>> Remove HL7 Pending flag from Observe transactions <<<<<\n be used. Many enhancements/fixes were made in DRM Plus and some fixes\n DENTADM RELEASE Class I-VI (type 3) Admin Info \n >>>>> Setting the Treeview system parameter = yes <<<<<\n \n Updating Routine file...\n Updating KIDS files...\n \n DENT*1.2*42 Installed.\n Jan 05, 2005@09:15:29\n \n Install Message sent #147809\n -----------------------------------------------------------------------\n DENTADM RE-RELEASE Class I-VI Admin Entry (type 3) Edit/Re-Release\n 100% \n Complete\n DENTBATCH Enter Batch Screening/Complete Exam \n DENTCARD Enter Data Thru Card Reader \n DENTCDR Cost Distribution Report \n DENTFEE EDIT Applications and Dental Fee (type 5) Enter/Edit\n DENTFEE RELEASE Applications and Dental Fee (type 5) \n DENTFEE RE-RELEASE Applications and Fee (type 5) Edit/Re-Release\n DENTINI Initialize Card Reader \n DENTNCLINTIME Non Clinical Time \n were made in DRM as well. See the detailed description of changes below.\n DENTNCLINTIME DELETE Delete Non Clinical Time Entry \n DENTNCLINTIME EDIT Non Clinical Time Enter/Edit \n DENTNCLINTIME PROV Non Clinical Time by Provider \n DENTPERS EDIT Personnel Info (type 4) Enter/Edit \n DENTPERS RELEASE Personnel Info (type 4) \n DENTPERS RE-RELEASE Personnel Entry (type 4) Edit/Re-Release \n DENTPERS RPT Personnel Info (type 4) \n DENTPURGE Purge Dental AMIS \n DENTRELEASE ALL Release All Service Reports \n DENTTOOTH EDIT Tooth Chart Enter/Edit \n \n DENTTREAT DELETE Treatment Data Entry Delete \n DENTTREAT EDIT Treatment Data Enter/Edit (Full Screen) \n DENTTREAT LINE EDIT Treatment Data Enter/Edit (Line By Line) \n DENTTREAT RE-RELEASE Enable Edit/Re-Release of Treatment Data (Full)\n DENTTREAT1 EDIT Treatment Data (AMIS) Enter/Edit (Screen Handl)\n DENTTREATCLINIC RELEASE Clinic Summary \n DENTTREATM RE-RELEASE Enable Edit/Re-Release of Treatment Data (Line)\n DENTTREATNOREV RELEASE Release Report Without Reviewing Data \n DENTTREATPROV RELEASE Provider Summary \n DENTTREATSITPROV RELEASE Sittings By Provider \n The patch installation process should take be less than 5 minutes.\n \n -----DRM ONLY-----\n B. The Summary Reports (Provider and Clinic) now offer the choice to\n print only the totals columns. (this is already in DRM Plus)\n \n -----DRM Plus ONLY-----\n C. Added CPRS templates to Treatment Chart progress note and Addendum\n screens. CPRS templates are automatically displayed if linked to\n a TIU note title or embedded in the title boilerplate (applies to\n Treatment Chart and Clinical Record progress note title selection \n \n screens). NOIS:DUR-1004-31962\n \n D. There is a new "Save unfiled data" dialog prompt and functionality\n to allow changing of providers (occurs when DRM Plus is closed, a \n patient change in CPRS occurs, and the option "Save unfiled data" \n under the File menu is clicked). The "Save unfiled data to another\n provider" option under the File menu was removed. \n \n \n FIXES TO THE DRM/DRM Plus APPLICATION\n\n\n General Information\n 521.3 Erosion\n SYSTEM ACCESS DURING INSTALLATION\n =======================================================================\n Installation of this patch does not require users to be off of the \n system. However, all Dental users should not use the DRM GUI option \n while the patch is being installed. All Dental users MUST close any \n open DRM GUI application prior to the patch being installed. Once the \n patch has completed the users can use the DRM application.\n \n \n POST-INSTALLATION PROCESS\n 521.4 Pathological resorption\n =======================================================================\n The post-install routine will remove inactivated ICD-9's and add new\n ICD-9 codes to the DENTAL CPT CODE MAPPING (#228) table. \n \n It will also verify that the Condition field in file 228.2 matches the\n TP Condition field in file 228, and if not, then change the data for \n file 228.2. This part of the post-installation will be queued off in\n the background.\n \n \n 523.2 Gingival recession\n NOIS ADDRESSED BY THIS PATCH\n =======================================================================\n n/a\n \n \n REQUIRED BUILDS: LEX*2.0*31\n \n \n TEST SITES SYSTEM ALPHA/BETA\n ======================================================================\n 524.2 Anomalies of dental arch relationship\n El Paso ALPHA\n White River Junction BETA\n Louisville BETA\n Milwaukee BETA\n Minneapolis BETA\n \n \n ROUTINE SUMMARY\n ======================================================================\n Second line of routines will look like:\n 524.3 Anomalies of tooth position\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV041 n/a 12568280 41\n \n \n ======================================================================\n INSTALLATION INSTRUCTIONS FOR DENT*1.2*41\n ======================================================================\n 524.5 Dentofacial functional abnormalities\n This patch can be installed while users are on the system.\n The installation time should take less than 5 minutes.\n \n 1. Load the KIDS build from the mail message.\n \n 2. For DSM sites review your mapped set. Disable any of the above\n routines if necessary.\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu.\n 524.8 Other specified dentofacial anomalies\n \n 4. Use Load a Distribution and enter Dent_1_2P41.kid when prompted\n for a Host file. You may need to attach a directory name\n \n 5. You may elect to use the following options (when prompted for \n INSTALL NAME, enter DENT*1.2*41)\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 525.2 Atrophy of edentulous alveolar ridge\n 6. Use the Install Package(s) option and select package DENT*1.2*41\n \n 7. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. \n \n Enter the Coordinator for Mail Group 'DENTV ADA CODE MAPPING':[Name]\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n 528.7 Other disturbances of oral epithelium, including tongue\n 8. AXP/DSM Sites - After the patch has been installed, rebuild your \n map set, if necessary\n \n========================================================================\n POST-INSTALLATION PROCESS\n========================================================================\n1. Forward any Mailman messages generated during the post-installation.\n The post-install may generate a Mailman message if changes were made\n to the ADA Master table that were not part of the Dental Coding \n Group's recommended changes. These would include removing inactive\n \n ICD-9 codes that were added by the site and not known to the group.\n The Mailman message will be sent to the user loading the patch and \n must be forwarded to a Dental Administrator for evaluation.\n \n \n2. Add Members to the new Mail Group.\n A new mail group has been added called DENTV ADA CODE MAPPING. \n Please add members to this mail group. These should be individuals\n who will be responsible for evaluating changes to the ADA Master table\n within Dental Record Manager. A good candidate for a member would be\n =======================================================================\n The patch installation process should take be less than 5 minutes.\n the dental administrator for DRM in the Dental Service.\n \n This is an example of adding a member to this mail group. \n There are several Kernel options that allow the adding of members to a \n mail group including using Fileman. This example just shows one of \n those options display:\n \n Select MAIL GROUP NAME: DENTV ADA CODE MAPPING\n ------------------\n Select MEMBER: [add the name of the person to become a member]\n The post installation process may take a few minutes to process the\n TYPE:\n \n \n ========================================================================\n SAMPLE INSTALLATION\n ========================================================================\n Select Installation Option: INstall Package(s)\n Select INSTALL NAME: DENT*1.2*41 Loaded from Distribution 10/13/04@13:32\n => DENT*1.2*41T1 ;Created on Oct 13, 2004@13:31:32\n \n changes to the DENTAL CPT CODE MAPPING (#228) data. \n This Distribution was loaded on Oct 13, 2004@13:32:31 with header of\n DENT*1.2*41T1 ;Created on Oct 13, 2004@13:31:32\n It consisted of the following Install(s):\n DENT*1.2*41\n Checking Install for Package DENT*1.2*41\n \n Install Questions for DENT*1.2*41\n \n \n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME// CONSOLE\n \n Install Started for DENT*1.2*41 :\n Oct 13, 2004@13:32:45\n \n \n Build Distribution Date: Oct 13, 2004\n \n Installing Routines:\n Oct 13, 2004@13:32:45 \n Running Post-Install Routine: POST^DENTV041\n \n >>>>> Updating ADA table for known ICD-9 changes <<<<<\n \n >>>>> Finding inactive ICD-9s in the ADA table <<<<<\n ENHANCEMENTS TO THE DRM APPLICATION\n \n Update of file 228.2 data successfully queued, task# 346516\n \n Updating Routine file...\n \n Updating KIDS files...\n \n DENT*1.2*41 Installed.\n Oct 13, 2004@13:32:46\n \n =======================================================================\n Install Message sent #147427\n A. A new mail group DENTV ADA CODE MAPPING will be sent with this patch.\n This mail group will be used in future patches that modify the ADA\n Master table to notify users of the changes.\n The purpose of this patch is for Dental Record Manager to comply with \n \n B. The DENTAL CPT CODE MAPPING table has been changed so that any\n references to inactivated ICD-9 codes have been replaced or removed.\n Changes to the national mapping table were made by the Dental Coding\n Group members. The following changes may occur:\n \n CODE REMOVE ICD-9 REPLACE and/or ADD ICD-9\n ----- ------------- -----------------------------------\n D0340 524.5 524.21 524.22 524.23 524.24 524.25\n D4270 523.2 523.23\n the ICD-9 changes in the LEX*2.0*31 patch. The following Dental ICD-9\n D4271 523.2 523.24\n D7111 521.4 521.42\n D7286 528.7 528.79\n D7287 528.7 528.79\n D7290 524.3 524.31 524.32 524.33 524.34 524.35\n D7340 525.2 525.22\n D7350 525.2 525.25 528.71\n D7291 524.3 524.31 524.32 524.33 524.34 524.35\n D7465 528.7 528.79\n D7940 524.2 524.59\n codes are being inactivated and must be removed from the Dental CPT\n D7941 524.2 524.22 524.23\n D7943 524.2 524.26\n D7944 524.3 524.31 524.32 524.33 524.34 524.35\n D7945 524.2 524.24 524.25\n D7946 524.2 524.24 524.25 524.23\n D7947 524.2 524.27 524.33\n D7948 524.2 524.59 524.89\n D7949 524.2 524.59 524.89\n D7950 524.8 525.23 525.26\n D7955 524.8 525.23 525.26\n Code Mapping table:\n D7995 524.8 525.23 525.26\n D8010 524.3 524.31 524.32 524.33 524.34 524.35\n D8020 524.3 524.31 524.32 524.33 524.34 524.35\n D8030 524.3 524.31 524.32 524.33 524.34 524.35\n D8040 524.3 524.31 524.32 524.33 524.34 524.35\n D8050 524.3 524.31 524.32 524.33 524.34 524.35\n D8060 524.3 524.31 524.32 524.33 524.34 524.35\n D8070 524.3 524.31 524.32 524.33 524.34 524.35\n D8080 524.3 524.31 524.32 524.33 524.34 524.35\n D8090 524.3 524.31 524.32 524.33 524.34 524.35\n \n D8660 524.3 524.31 524.32 524.33 524.34 524.35\n D8670 524.3 524.31 524.32 524.33 524.34 524.35\n D8680 524.3 524.31 524.32 524.33 524.34 524.35\n D8690 524.3 524.31 524.32 524.33 524.34 524.35\n D8691 524.3 524.31 524.32 524.33 524.34 524.35\n D8692 524.3 524.31 524.32 524.33 524.34 524.35\n D8999 524.3 524.31 524.32 524.33 524.34 524.35\n D9910 523.2 523.25\n D9911 523.2 523.24\n D9940 521.2 521.12\n 521.1 Excessive attrition\n **the following are nationally mapped CPT's, your site\n **may not have DENT*1.2*39 with these codes\n 15120 525.2 528.71\n 15350 525.2 524.8 528.71 525.23 525.26\n 20902 524.00 525.23 525.26\n 21125 525.2 525.23^525.26\n 21210 525.2 525.23^525.26\n 40818 525.2 524.8, 528.71^525.23^525.26\n 40840 525.2 524.8, 528.71^525.23^525.26\n 40845 525.2 524.8, 528.71^525.23^525.26\n 521.2 Abrasion\n 64716 525.2 525.23^525.26\n \n 524.3 will be removed from all of the following nationally mapped\n CPT codes:\n 99201 99202 99203 99204 99205 99211 99212 99213 99214\n 99215 99241 99242 99243 99244 99245 99251 99252 99253\n 99254 99255 99281 99282 99283 99284 99285 99371 99372\n 99373\n \n \n\n
\n General Information\n * 13 ADA Categories (Diagnostic, Preventative, etc)\n FIXES TO THE DRM/DRM Plus APPLICATIONS\n =======================================================================\n A. Provider selection on the report screen will be based on the selected\n division. If there is no DIVISION assigned to a Provider, then that\n provider will display under any site, otherwise the Provider will \n only display for sites that he/she has been assigned to. \n NOIS:PUG-1104-50338 \n \n B. The user can no longer modify (remove) the Report Date on the File\n Fee Basis screen. This was causing a 'List Index Out Of Bounds' \n * 131 DES Product Lines (Brief Exams, Extensive Exams, etc)\n error. NOIS:MAD-0205-40840\n \n C. Non-Clinical Time no longer requires the 4 digit Provider Id to file\n time. The report will still show data for those providers with only\n a 4 digit Id (historical data), but it will use the 8 digit Id if\n there is one. Non-Clinical time can be entered by non-dentist users\n in the Education and Research categories.\n \n D. Transactions for partials will send Tooth# in the HL7 message to the\n AAC for research purposes.\n * ADA/CPT Code.\n \n DRM Plus only:\n --------------\n E. Head and Neck, PSR and Perio data can be filed for providers without\n a 4 digit Provider Id. Only the 8 digit Id is now required.\n \n F. If all transactions for an encounter are deleted through the \n transaction table, then the associated encounter will also be\n deleted.\n \n \n G. If a speed code becomes corrupted, the site (IRM) can now delete it \n using the DENTV XPAR EDIT PARAMS option in VistA. NOIS:PUG-0105-51270\n \n H. Existing Tooth Notes and Head and Neck data will be inserted into the\n progress note when the corresponding tree item is dbl-clicked.\n \n I. Three consecutive dashes in the progress note for PSR and Perio have\n been replaced with '- -' or '-~-' so that the note no longer has\n conflicts with TIU transcription placeholders. NOIS:WWW-0205-50264\n \n When the DAS Category is selected, reports display workload credit\n J. Teeth will be displayed in tooth# order for Findings in the progress\n note (example: Missing Teeth: 4, 7, 10, 12.) rather than in the order\n the user enters them.\n \n K. Exiting or changing patients in DRM Plus while on the perio screen\n correctly prompts to save unfiled data.\n \n \n SYSTEM ACCESS DURING INSTALLATION\n ========================================================================\n using CTVs. When any of the DES categories are selected, reports\n Installation of this patch does not require users to be off of the \n system. However, all Dental users should not use the DRM GUI option \n while the patch is being installed. All Dental users MUST close any \n open DRM GUI application prior to the patch being installed. Once the \n patch has completed the users can use the DRM application.\n \n POST-INSTALLATION PROCESS\n =======================================================================\n ***********************************************************************\n * *\n display workload credit using RVUs. CPT codes (non-DCodes) are now\n * THE FOLLOWING STEP BE COMPLETED FOR THIS PATCH TO WORK PROPERLY *\n * *\n ***********************************************************************\n \n After the KIDS install has completed, IRM needs to place the DRM\n executable (dentalmrm.exe) or the DRM Plus executable (dentalmrmtx.exe)\n in the appropriate directory. There are *NO* additional client side\n installations for DRM Plus with this patch!\n \n See the installation steps below for details. \n included in the DES category totals.\n \n \n NOIS ADDRESSED BY THIS PATCH\n =======================================================================\n PUG-1104-50338 MAD-0205-40840 PUG-0105-51270 WWW-0205-50264\n \n \n REQUIRED BUILDS: DENT*1.2*42\n \n \n \n INSTALLATION FILES\n =======================================================================\n How to Obtain KIDS File\n \n File Name: DENT_1_2P43.zip FTP format: binary\n \n DENT_1_2P43.zip file will contain the following files:\n FTP \n File Name Description Format\n ------------------ ------------------------------------------ ------\n The patch installation process should take be less than 5 minutes.\n Dent_1_2P43.kid KIDS file which will install 1 KIDS Builds ASCII\n DENT*1.2*43\n Dentalmrm.exe DRM V3.1.5.0 executable Binary\n Dentalmrmtx.exe DRM Plus V4.1.0.0 executable Binary\n Dent_1_2p43_rn_ig.pdf DENT*1.2*42 Release Notes and Binary\n Installation Guide \n \n The zip file listed above may be obtained via FTP. The preferred \n method is to FTP the files from download.vista.domain.ext\n \n ========================================================================\n \n This transmits the files from the first available FTP server. Sites\n may also elect to retrieve software directly from a specific server \n as follows:\n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n \n \n ENHANCEMENTS TO THE DRM AND DRM PLUS APPLICATION\n TEST SITES DRM/DRM Plus SYSTEM ALPHA/BETA\n ====================================================================\n Manhattan DRM Plus VMS/Cache ALPHA\n Miami DRM Plus VMS/Cache BETA\n Gainesville/Daytona both VMS/Cache, multi-facility BETA\n \n \n ROUTINE SUMMARY\n ======================================================================\n Second line of routines will look like:\n ========================================================================\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV042 [***to be deleted***]\n DENTV044 [***to be deleted***]\n DENTV043 n/a 2686585 43\n DENTVA1 12453282 11487204 38,39,43\n DENTVA11 n/a 7229654 43\n DENTVA2 14211342 10927360 38,39,42,43\n A. The following new KLF-style reports are available within DRM/DRM Plus.\n DENTVA21 n/a 12953028 43\n DENTVA3 n/a 5789815 43\n DENTVA4 n/a 7664444 43\n DENTVA5 n/a 11555857 43\n DENTVA51 n/a 5708255 43\n DENTVA6 n/a 9217535 43\n DENTVAU 2840803 10125515 38,39,43\n DENTVDD1 5150464 5655102 31,38,39,43\n DENTVHL1 40,43\n DENTVRP1 5103649 5124725 30,34,36,31,37,39,43\n These reports can retrieve data using DAS or DES type categories and\n DENTVRP3 6517626 7496015 30,32,35,31,39,43\n DENTVRP4 9233470 9582106 30,32,31,42,43\n DENTVRP8 4052725 5141483 38,39,43\n DENTVRP9 6935679 7411021 30,32,34,31,38,39,43\n DENTVTP4 10224521 10032432 39,43\n DENTVTPA 4902746 5358178 39,42,43\n DENTVTPC 10565254 11625812 39,42,43\n DENTVUTL 191547 1750114 30,33,34,36,31,43\n DENTVXPR 913261 1047935 31,43\n \n will display the appropriate workload value (CTV or RVU).\n \n INSTALLATION INSTRUCTIONS FOR DENT*1.2*43\n ======================================================================\n This patch must be installed when there are no dental DRM processes\n running. All open DRM and DRM Plus GUI applications must be closed.\n The installation time should take less than 5 minutes.\n \n 1. Obtain the Dent_1_2P43.kid file\n \n 2. For DSM sites review your mapped set. Disable any of the above\n 1: Observations per Month\n routines if necessary\n \n 3. From the Kernel Installation and Distribution System Menu, select\n the Installation menu\n \n 4. Use Load a Distribution and enter Dent_1_2P43.kid when prompted\n for a Host file. You may need to attach a directory name\n \n 5. You may elect to use the following options (when prompted for \n INSTALL NAME, enter DENT*1.2*43)\n 2: Service Profile\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 6. Use the Install Package(s) option and select package DENT*1.2*43\n \n 7. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. This example shows answering NO:\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n 3: Service by Product Group\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n 8. AXP/DSM Sites - After the patch has been installed, rebuild your \n map set, if necessary\n \n =======================================================================\n POST-INSTALLATION PROCESS\n =======================================================================\n \n 4: Provider Profile\n 1. If your site is running dentalmrm.exe (DRM), then\n Move dentalmrm.exe to ...\\DOCSTORE \n '...\\' indicates your path for where DRM is located.\n \n 2. If your site is running dentalmrmtx.exe (DRM Plus)\n Move dentalmrmtx.exe to ...\\DOCSTORE\n '...\\' indicates your path for where DRM Plus is located.\n \n 3. Some sites are having a problem viewing the Version Notes from the\n DRM/DRM Plus Help menu. The .ini parameters may not have been changed\n This patch contains fixes and enhancements to the reporting features\n 5: Patient Category Profile\n based on the installation instructions in a previous patch. In order\n to view Version Notes, the correct FTP parameters must exist in the \n dentalmrm.ini file found on the ...\\DOCSTORE directory where the \n executable exists:\n \n FTPHOST=ftp.docstorsys.com\n FTPPASSWORD=dss376\n FTPUSERID=DRM\n \n ========================================================================\n 6: Patients by Eligibility Setting\n SAMPLE INSTALLATION\n ========================================================================\n Select Installation Option: INstall Package(s)\n Select INSTALL NAME: DENT*1.2*43 Loaded from Distribution \n3/7/05@15:43:24\n => DENT*1.2*43T3 ;Created on Mar 07, 2005@15:21:06\n \n This Distribution was loaded on Mar 07, 2005@15:43:24 with header of\n DENT*1.2*43T3 ;Created on Mar 07, 2005@15:21:06\n It consisted of the following Install(s):\n 7: Patients by Eligibility Group\n DENT*1.2*43\n Checking Install for Package DENT*1.2*43\n \n Install Questions for DENT*1.2*43\n \n Incoming Files:\n \n \n 220 DENTAL PATIENT (Partial Definition)\n Note: You already have the 'DENTAL PATIENT' File.\n 8: Patients by Dental Patient Category\n \n 226 DENTAL NON CLINICAL TIME (Partial Definition)\n Note: You already have the 'DENTAL NON CLINICAL TIME' File.\n \n 228 DENTAL CPT CODE MAPPING (Partial Definition)\n Note: You already have the 'DENTAL CPT CODE MAPPING' File.\n \n 228.1 DENTAL HISTORY (Partial Definition)\n Note: You already have the 'DENTAL HISTORY' File.\n \n 9: Outpatient Service by Product Group\n 228.2 TREATMENT PLAN TRANSACTION/EXAM (Partial Definition)\n Note: You already have the 'TREATMENT PLAN TRANSACTION/EXAM' File.\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//NO\n \n Enter the Device you want to print the Install messages.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n 10: Inpatient Service by Product Group\n \n DEVICE: HOME//\n \n Install Started for DENT*1.2*43 :\n Mar 07, 2005@15:47:44\n \n Build Distribution Date: Mar 07, 2005\n \n Installing Routines:\n Mar 07, 2005@15:47:44\n 11: Distribution of Dental Services\n \n Running Pre-Install Routine: PRE^DENTV043\n \n >>>>> Deleting field .4 from file 226 <<<<<\n \n Installing Data Dictionaries:\n Mar 07, 2005@15:47:45\n \n Installing PACKAGE COMPONENTS:\n Installing REMOTE PROCEDURE\n \n Installing OPTION\n Installing PARAMETER DEFINITION\n Mar 07, 2005@15:47:45\n \n Running Post-Install Routine: POST^DENTV043\n \n Patch 43 post-install successfully queued, task# 349141\n \n Updating Routine file...\n Updating KIDS files...\n B. The Fee Basis Report provides the capability to view detail data. \n DENT*1.2*43 Installed.\n Mar 07, 2005@15:47:46\n \n Install Message sent #151830\n Detailed data contains subtotals and can be sorted by clicking on\n within Dental Record Manager. Many new reports will now available \n the header row.\n \n C. Total Sittings/Visits by Patient Type is available. This report\n is similar to the Sittings/Visits Report within VistA/DAS reporting.\n \n D. The current Summray and Sittings reports were enhanced to use RVU vs.\n CTV, and multiple DES sort categories (ADA Category, VA-DSS \n Products, ADA/CPT Codes) as well as the existing DAS category. \n These reports currently retrieve data for providers with the\n new 8 digit Provider Id. Now they will also get historical data\n within DRM and DRM Plus, as well as enhancements to existing reports.\n for any dental provider in the system.\n \n E. The Sittings Reports (Provider/Clinic) now allow sorting by column\n heading once the report has been run. Simply click on the column\n that you want sorted and the data will re-arrange into the correct\n sequence. The Totals row will always remain at the end and the\n subtotals will be based on the column being sorted.\n \n F. The Extract options allow the user to select an individual site, or\n all sites. If a single site is selected, then the providers\n \n displayed on the New Extract screen will be valid for the selected\n site only.\n \n G. Headers in the extract text that started with "DAS " (for example,\n DAS DIVISION) have been changed to remove the DAS designation.\n \n H. The informational text on the Delete Encounter screen within the\n Dental History tab was changed to remove all references to DAS.\n \n I. A legend box can be displayed detailing the provider type and \n Where appropriate, workload reports will allow sorting by the\n specialty codes that make up the 8 digit Provider Id on any report\n screen that contains the 8 digit provider Id.\n \n J. Provider lists on reports and the New Extract now display the\n provider type and provider specialty information next to the name.\n \n K. A new Version Information screen will pop-up for the user when a new\n version is run for the first time. The user may select to show\n this screen the next time they launch DRM/DRM Plus.\n \n following categories:\n L. $Values, VA Cost to Perform and Equivalent Private Cost can be \n entered for ADA/CPT codes by admin users. The fields are available\n on the Edit CPT Field Values option or can be quickly edited using\n a new option called Edit Procedure Costs. These values display on \n various DES reports.\n \n M. Patient SSNs on the reports (Sittings, Detailed Fee Basis and the\n DRM Plus Provider Planning report) have been replaced with the\n patient name and last 4 of the SSN.\n \n * 30 DAS Categories (Cases Complete, Cases Terminated, etc)\n DRM Plus only\n -------------\n N. Primary and Secondary Provider designations can be defined and will\n display on the header of the application next to the patient name.\n A new report Provider Planning is available to display planned \n treatment items for the primary and secondary providers. Admin users\n can define who can edit Primary/Secondary providers using a new\n parameter on the Security tab of the Admin Toolbox for users.\n \n \n\n
\nSet the TP AREA field of file 228 to areWholeTooth for codes D2910, \nD2915, and D2920.\n\n
\n General Information\n 523.0 Acute gingivitis\n =======================================================================\n Installation of this patch does not require users to be off of the \n system. However, all Dental users should not use the DRM GUI option \n while the patch is being installed. All Dental users MUST close any \n open DRM GUI application prior to the patch being installed. Once the \n patch has completed the users can use the DRM application.\n \n \n POST-INSTALLATION PROCESS\n =======================================================================\n 523.1 Chronic gingivitis\n The post-install routine will remove inactivated ICD-9's and add new\n ICD-9 codes to the DENTAL CPT CODE MAPPING (#228) table. If the site \n manually changed other ICD-9's that are now inactive and the patch made\n changes to those codes, then a mailman message will be sent to the users\n in the DENTV ADA CODE MAPPING mail group to verify those changes. \n \n \n REQUIRED BUILDS: LEX*2.0*45\n \n \n 523.3 Acute periodontitis\n TEST SITES ALPHA/BETA\n ======================================================================\n Bay Pines ALPHA\n \n \n ROUTINE SUMMARY\n ======================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n 523.4 Chronic periodontitis\n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV049 n/a 30259209 49\n \n \n ======================================================================\n INSTALLATION INSTRUCTIONS FOR DENT*1.2*49\n ======================================================================\n This patch can be installed while users are on the system.\n The installation time should take less than 5 minutes.\n \n \n 1. Load the KIDS Distribution from the Packman Message using the \n Packman function "Install/Check Message." (Note: test sites will\n receive the kids build in a .zip file with the patch description.)\n \n 2. Use the Install Package(s) option and select package DENT*1.2*49\n \n 3. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. \n \n The patch installation process should take be less than 5 minutes.\n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n ========================================================================\n POST-INSTALLATION PROCESS\n ========================================================================\n Forward any Mailman messages generated during the post-installation.\n The post-install *may* generate a Mailman message if changes were made\n to the ADA Master table that were not part of the Dental Coding \n Group's recommended changes. These would include removing inactive\n The post installation process may take a few minutes to process the\n ICD-9 codes that were added by the site and not known to the group.\n The Mailman message will be sent to the user loading the patch and \n must be forwarded to a Dental Administrator for evaluation.\n changes to the DENTAL CPT CODE MAPPING (#228) data. \n \n \n =======================================================================\n ENHANCEMENTS TO THE DRM APPLICATION\n =======================================================================\n The DENTAL CPT CODE MAPPING table has been changed so that any\n references to inactivated ICD-9 codes have been replaced or removed.\n Changes to the national mapping table were made by the Dental Coding\n Group members. The following changes may occur:\n \n CODE REMOVE ICD-9 REPLACE with ICD-9\n ----- ------------- --------------------------\n D4210 523.4 523.40\n The purpose of this patch is for Dental Record Manager to comply with \n D4211 523.4 523.40\n D4240 523.4 523.40\n D4241 523.4 523.40\n D4245 523.4 523.40\n D4260 523.4 523.40\n D4261 523.4 523.40\n D4263 523.4 523.40\n D4264 523.4 523.40\n D4265 523.4 523.40\n D4266 523.4 523.40\n the ICD-9 changes in the LEX*2.0*45 patch. The following Dental ICD-9\n D4267 523.4 523.40\n D4268 523.4 523.40\n D4273 523.4 523.40\n D4274 523.4 523.40\n D4275 523.4 523.40\n D4276 523.4 523.40\n D4320 523.4 523.40\n D4321 523.4 523.40\n D4341 523.4 523.40\n D4342 523.4 523.40\n codes are being inactivated and must be removed from the Dental CPT\n D4381 523.4 523.40\n D4910 523.4 523.40\n D4920 523.4 523.40\n D7261 478.1 478.19\n 30420 478.1 478.19\n 30465 478.1 478.19\n 31020 478.1 478.19\n 31030 478.1 478.19\n 30630 478.1 478.19\n 99201 523.4 523.40\n Code Mapping table:\n 99202 523.4 523.40\n 99203 523.4 523.40\n 99204 523.4 523.40\n 99205 523.4 523.40\n 99211 523.4 523.40\n 99212 523.4 523.40\n 99213 523.4 523.40\n 99214 523.4 523.40\n 99215 523.4 523.40\n 99241 523.4 523.40\n \n 99242 523.4 523.40\n 99243 523.4 523.40\n 99244 523.4 523.40\n 99245 523.4 523.40\n 99251 523.4 523.40\n 99252 523.4 523.40\n 99253 523.4 523.40\n 99254 523.4 523.40\n 99255 523.4 523.40\n 99281 523.4 523.40\n 478.1 Other diseases of nasal cavity and sinuses\n 99282 523.4 523.40\n 99283 523.4 523.40\n 99284 523.4 523.40\n 99285 523.4 523.40\n 99371 523.4 523.40\n 99372 523.4 523.40\n 99373 523.4 523.40\n \n If the site manually changed other ICD-9's that are now inactive,\n the patch will replace them as follows:\n 521.8 Other specific diseases of hard tissues of teeth\n \n 478.1 with 478.19\n 521.8 with 521.81\n 523.0 with 523.00\n 523.1 with 523.10\n 523.3 with 523.30\n 523.4 with 523.40\n \n \n SYSTEM ACCESS DURING INSTALLATION\n\n
\n General Information\n SYSTEM ACCESS DURING INSTALLATION\n =======================================================================\n Installation of this patch does not require users to be off of the \n system. \n \n \n POST-INSTALLATION PROCESS\n =======================================================================\n The post installation will queue a job to reset affected transactions\n back to a 'pending' HL7 transmission status. These transactions are in\n =======================================================================\n file 228.2 for encounter and file 228.5 for fee.\n \n REQUIRED BUILDS: none\n \n TEST SITES ALPHA/BETA\n ======================================================================\n \n \n \n ROUTINE SUMMARY\n The purpose of this patch is to resend dental HL7 transactions for\n ======================================================================\n Second line of routines will look like:\n ;;1.2;DENTAL;<patch list>;AUG 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ------------------------\n DENTV051 n/a 11269194 51\n \n \n ======================================================================\n encounter and fee basis that were dropped by the VIE. This data is\n INSTALLATION INSTRUCTIONS FOR DENT*1.2*51\n ======================================================================\n This patch can be installed while users are on the system.\n The installation time should take less than 1 minute.\n \n 1. Load the KIDS Distribution from the Packman Message using the \n Packman function "Install/Check Message." (Note: test sites will\n receive the kids build in a .zip file with the patch description.)\n \n 2. Use the Install Package(s) option and select package DENT*1.2*51\n required for national reporting of dental workload.\n \n 3. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. \n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n \n The patch installation process should take be less than 1 minute.\n \n \n\n
\nThis is patch 22 of Dental Version 1.2. This patch is the final clean up of\nfile 3, 6, and 16. It'll delete any old routines that reference these files.\n\n
\n General Information\n \n entered and signed from the Clinical Record tab for the next \n patient, the additional signer will not carry over to the next \n patient.\n \n 6. If a previous Head & Neck entry is deleted and a new entry is created \n in the same session, the new entry will be created correctly, rather \n than being created as a deleted record.\n \n 7. The code boilerplate from TIU was putting an additional text marker \n into the DRM Plus note. When two text markers are present and the \n ENHANCEMENTS TO THE DRM PLUS APPLICATION\n user clicks 'Back' and 'Next' the note was being duplicated\n exponentially. The second text marker has been removed and this \n will no longer occur.\n \n 8. Users without an 8 digit provider Id may run reports without seeing \n a list-out-of-bounds error message.\n \n 9. If the user had selected a tab, other than the Chart/Treatment tab \n as the initial tab, a run time error was generated when changing \n patients from CPRS. Any tab can be selected as the initial tab\n ========================================================================\n (including the new Cover Page) without generating a runtime error \n when changing patients.\n \n 10. "Observe" type transactions will appear in the progress note when\n entered from the Completed tab. This type of transaction will \n always appear under the Other Dental Findings heading.\n \n 11. Markers on a surface "m" will now be removed when adding a retained\n root to the tooth.\n \n A. Residents are required to enter a "Distributed" (Attending) Provider \n 12. When adding a retained root to a crown, the crown will be removed.\n Prevent whole tooth extraction on a tooth with retained roots.\n \n 13. Corrected the tooltip text (hover help) for the "Add Sub-Phase" \n button on the sequencing screen.\n \n 14. The tooth selection box will be cleared for multi-add when using \n quick list or local codes.\n \n 15. Corrected advance of MGJ on the perio screen.\n when filing data to PCE. The Distributed Provider will become the \n \n 16. PSR data will be cleared when changing patients. This will prevent\n PSR data from the previous patient displaying incorrectly.\n \n 17. Corrected problem with the asterisks on the notes button not \n appearing in certain scenarios.\n \n 18. If the perio "clear" function results in an impacted tooth showing \n at tooth #1, then the auto-advance did not work properly. This has \n been fixed.\n PCE Primary Provider for the encounter and will be sent to the \n \n 19. Changed planned extraction to remove M/D lesions.\n \n 20. Corrected the jumbled view of multi-tooth when selecting a non-\n multi-tooth code.\n \n 21. When adding a coping or crown on top of an existing implant by using\n the ADA Codes or Add text box, the graphics did not draw \n appropriately. The graphic will now display correctly.\n \n national database for reporting. All local DRM Plus reports will\n 22. When DRM changes patients, return to the default view.\n \n 23. The perio "Compare" button will now be enabled when there are two\n exams to compare.\n \n 24. Removed accelerator keys from H&N, Sequencing, PSR and Plaque \n Index screens.\n \n 25. Changed display of planned graphics to always apply planned items \n after any diagnostic findings or completed items regardless of date.\n continue to count workload toward the resident. The Distributed\n This may result in planned items not showing correctly in some cases.\n \n 26. If you mark as missing a root on a bridge abutment and then try to\n remove the bridge by clicking missing and then the pontic, the \n extract bridge popup does not show and only the pontic is removed,\n leaving the bar in place. This has been fixed.\n \n 27. Add retained root, then planned extract root, implant, coping, \n crown. After that, the already pressed restore button does not \n work on any teeth. This has been fixed.\n Provider will show up on the DRM Plus Extract.\n \n 28. Don't save the sequencing note if it has not changed.\n \n 29. CCOW will be defaulted OFF, or disabled. In order to enable it, IRM\n must add a CCOW=ON parameter to the CPRS Tools menu string for DRM \n Plus. (CCOW=1 will also enable CCOW.)\n \n 30. Admin users may no longer "re-add" nationally mapped CPT codes to \n the ADA Mapping table which allowed them to modify the RVU and \n VA-DSS product line information.\n \n \n 31. Quick codes that are DRM Plus "ranged" codes (used in bridges for\n example) can now be removed from the user's Quick List. This\n affected sites as they were migrating to DRM Plus from DRM.\n \n 32. A single diagnosis is pre-selected as the Primary PCE Diagnosis.\n This will work when there is a single diagnosis entry on the filing\n options page, or when there are multiple entries as long as they are\n all the same diagnosis code.\n \n ========================================================================\n B. A new Cover Page is available with patient demographic and recent \n 33. A list-out-of-bounds error will no longer occur trying to create the\n progress note under certain (infrequent) circumstances when the user\n clicks back and next, deleting and adding transactions many times.\n \n 34. The Print button on the File menu will only work for 'Notes' on the \n Clinical Record tab. The other types of entries (Meds, Consults, \n Vitals, etc) cannot be printed from DRM Plus.\n \n 35. Diagnostic Findings older than the 1 day that are deleted by an \n admin user will be removed from the graphic and the transaction \n dental activity information. Access to edit eligibility information \n list. These were previously shown in the transaction list with a \n strike-through as if a non-admin user had deleted them. \n \n 36. Partials that were modified or deleted in the sequencing screen\n displayed incorrectly in the progress note. They were showing \n entries for each tooth in the partial rather than a single entry.\n \n 37. The Visit Date will be used in the transaction list rather than the\n date the item was created. This is a more relevant date to the user.\n \n on this screen will be assigned by the dental administrator.\n \n SYSTEM ACCESS DURING INSTALLATION\n ========================================================================\n Installation of this patch does not require users to be off of the \n system. However, all Dental users should not use the DRM Plus GUI\n while the patch is being installed. All Dental users MUST close any \n open DRM Plus GUI application prior to the patch being installed. Once \n the patch has completed the users can use the DRM Plus application.\n \n \n \n POST-INSTALLATION PROCESS\n =======================================================================\n The post-installation will change the D6056 ada code to 'Coping' for\n the correct DRM Plus graphics, will set a default for the new \n DENTV DRM NO VISIT CREATE and DENTV DRM DUPCHECK OFF parameters and \n will add 1 to each entry defined in the DENTV DRM DEF STARTUP TAB \n parameter because there's a new tab zero (0) for the Cover Page. \n \n The post-installation will also start a TaskMan job to loop through \n all the Dental History entries (228.1) for each Dental Patient (220)\n C. DRM Plus will synchronize planned and completed care. If exact\n and inactivate (set DAS DISPOSITION=Completed) the last encounter if \n the status is 'In Progress' and date is > 2 years (730 days).\n \n ***********************************************************************\n * *\n * THE FOLLOWING STEP BE COMPLETED FOR THIS PATCH TO WORK PROPERLY *\n * *\n ***********************************************************************\n \n After the KIDS install has completed, IRM needs to place the DRM Plus\n duplicates are found between planned items and newly entered \n executable (dentalmrmtx.exe) in the appropriate directory. IRM must \n also complete some additional client setup on client pcs or thin client \n servers. See the installation steps below for details. \n \n \n REMEDY CALLS ADDRESSED BY THIS PATCH\n =======================================================================\n Sheridan HD141287 iMed Consent button\n Gainesville HD140425 Additional signer error\n Gainesville HD139916 default tooth number for D9971 Multiadd\n completed items (if, for example, the user enters new items rather \n Gainesville HD136629 List index out of Bounds Error when no appts/cancel\n Gainesville HD135195 Teeth graphic will not provide proper display\n Gainesville HD135014 List index out of bounds error generating note\n Puget Sound HD134425 TIU notes repeat when dbl hyphen line is present\n \n \n REQUIRED BUILDS: DENT*1.2*46\n \n \n INSTALLATION FILES\n than completing the existing planned item) then the planned items \n ====================================================================\n How to Obtain KIDS File\n \n File Name: Dent_1_2P47.zip FTP format: binary\n Dent_1_2p47.zip file will contain the following files:\n FTP \n File Name Description Format\n ------------------ ---------------------------- ------\n Dent_1_2p47.kid KIDS file which will install ASCII\n one KIDS Builds: DENT*1.2*47\n will be automatically deleted. Potential duplicates matching a \n dentalmrmtx.exe DRM Plus V4.7.0.7 executable Binary\n setupP47.EXE CVision (client) install file Binary\n Dent_1_2p47_rn_ig.pdf DENT*1.2*47 Release Notes and Binary\n Installation Guide \n P47_QUICKstart.pdf Description (w/ screen shots) Binary\n of the enhancements/fixes \n \n The zip files listed above may be obtained via FTP. The preferred \n method is to FTP the files from download.vista.domain.ext\n \n tooth# will be presented to the user so that the user may decide \n This transmits the files from the first available FTP server. Sites\n may also elect to retrieve software directly from a specific server \n as follows:\n CIO FIELD OFFICE FTP ADDRESS DIRECTORY\n ---------------- ------------------------- --------------------\n Albany ftp.fo-albany.domain.ext [anonymous.software]\n Hines ftp.fo-hines.domain.ext [anonymous.software]\n Salt Lake City ftp.fo-slc.domain.ext [anonymous.software]\n \n \n This patch contains fixes and enhancements to Dental Record Manager\n which item(s) to keep or delete.\n TEST SITES SIZE/TYPE ALPHA/BETA\n ====================================================================\n Tuscon, AZ Large ALPHA\n Houston, TX Large BETA\n Manhattan, NY Large BETA\n \n \n ROUTINE SUMMARY (checksums using CHECK1^XTSUMBLD)\n ====================================================================\n Second line of routines will look like:\n \n ;;1.2;DENTAL;<patch list>;Aug 10, 2001\n \n Routine Before Patch After Patch Patch List\n -------- ------------ ----------- ----------\n DENTV046 <to be deleted>\n DENTV047 n/a 12486220 47\n DENTVA2 34594801 35380230 38,39,42,43,45,47\n DENTVA3 13852254 21845633 43,45,47\n DENTVA7 n/a 26216617 47\n DENTVAU 35278064 39428093 38,39,43,47\n D. Added a "Save & Exit" button to the sequencing screen. Users may \n DENTVHL 55257232 58018478 40,42,45,47\n DENTVHLF 23062617 23062236 40,47\n DENTVIP3 36064821 37084460 31,39,47\n DENTVRF <to be deleted>\n DENTVRF0 12958911 18554933 31,37,47\n DENTVRF1 <to be deleted>\n DENTVRF2 <to be deleted>\n DENTVRF3 <to be deleted>\n DENTVRF4 <to be deleted>\n DENTVRH 41461464 41991101 31,37,38,39,45,47\n add or modify the treatment plan and file the changes without having\n DENTVRP9 53259130 56135358 30,32,34,31,38,39,43,45,47\n DENTVTP0 2411836 65772564 39,47\n DENTVTP2 13504864 16293307 38,39,45,47\n DENTVTP4 48820982 51740077 39,43,45,47\n DENTVTP5 12210838 15906903 39,45,47\n DENTVTP6 23334296 26292035 39,45,47\n DENTVTP7 11644010 14505318 39,47\n DENTVTPA 29373949 28123580 39,42,43,45,47\n DENTVTPB <to be deleted>\n DENTVTPC 73761113 76438192 39,42,43,45,47\n to click "Next" through the other screens. There must be no \n DENTVTPD 29778472 31135124 39,47\n DENTVUTL 19086877 22593588 30,33,34,36,31,43,45,47\n \n \n INSTALLATION INSTRUCTIONS FOR DENT*1.2*47\n ======================================================================\n This patch must be installed when there are no dental DRM processes\n running. All open DRM Plus GUI applications must be closed.\n \n The installation time should take less than 2 minutes.\n Completed transactions, Perio, PSR, or Head and Neck data and the \n \n 1. Obtain the Dent_1_2P47.kid file\n \n 2. From the Kernel Installation and Distribution System Menu, select\n the Installation menu\n \n 3. Use Load a Distribution and enter Dent_1_2P47.kid when prompted\n for a Host file. You may need to attach a directory name\n \n 4. You may elect to use the following options (when prompted for \n most recent dental encounter must be Active for this feature to work.\n INSTALL NAME, enter DENT*1.2*47)\n a. Backup a Transport Global\n b. Compare Transport Global to Current System\n c. Verify Checksums in Transport Global\n \n 5. Use the Install Package(s) option and select package DENT*1.2*47\n \n 6. For the install prompts, enter either Yes or No depending upon the\n normal practice at your facility. This example shows answering NO:\n \n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n =======================================================================\n POST-INSTALLATION PROCESS\n =======================================================================\n 1. Move dentalmrmtx.exe to ...\\DOCSTORE\n '...\\' indicates your path for where DRM Plus is located.\n \n E. Added an "Edentulous" button to diagnostic findings. Clicking \n Run setupP47.EXE on all Windows Workstations, Thin Client Servers, \n Windows Terminal Services Servers and Citrix Servers that need to \n launch the dentalmrmtx.exe you moved to \\DOCSTORE. SetupP47.exe does\n NOT need to be run on the machine that hosts the \\DOCSTORE folder.\n \n We recommend that setupP47.EXE be run by an administrator. \n SetupP47.EXE replaces the CVision.ocx file (and other files) in\n C:\\WINNT\\SYSTEM32 and registers it on the machine. The version\n of CVision.ocx (found by right-clicking the .ocx and selecting \n Properties option, Version tab) is 2.2.0.14.\n Edentulous and then clicking a tooth will mark all teeth in that \n \n Note: On some Windows Server machines the setupP47.EXE file \n will not update the CVision.ocx file in WINNT\\SYSTEM32.\n If the version is not 2.2.0.14 then Micorsoft's Data Execution\n Prevention (DEP) may be the issue. Turn DEP off (call DSS tech\n support if you need help with this), reboot the machine and install\n the client side files by running setupP47.EXE. Additional information\n on Microsoft's DEP can be found at: \n http://support.microsoft.com/kb/875352\n \n Plus including capturing the Distributed (Attending) Provider when\n arch as missing and create the associated transactions.\n *********************************************************************\n Please be careful to coordinate the server/client updates with each \n other so that the dental application works properly. You will know \n if the server/client files are *NOT* compatible because launching DRM \n Plus will cause approximately 30 client errors! This also means that\n you must carefully coordinate testing the new application in the TEST\n account since you must run setupP47.exe on a rarely used machine for \n the dental staff to test against, as they will not be able to run the\n production side application after updating the client.\n *********************************************************************\n \n \n 2. Once the patch is released, the Patch 47 User Manual and \n Administrative Manual will be available are available on the DRM Plus\n intranet site: http://vaww1.domain.ext/dental/ under the DRM Plus\n link found on the left side of the main page, then DRM Plus Resources\n found at the bottom of the page. \n The documents are titled:\n DRM Plus Administrators Manual\n DRM Plus Users Manual\n \n F. Ancillary applications or websites may be defined by the dental \n ========================================================================\n SAMPLE INSTALLATION\n ========================================================================\n Select Installation Option: INstall Package(s)\n Select INSTALL NAME: DENT*1.2*47 Loaded from Distribution \n 8/2/06@14:22:44\n => DENT*1.2*47T4 ;Created on Aug 02, 2006@14:03:52\n \n This Distribution was loaded on Aug 02, 2006@14:22:44 with header of\n DENT*1.2*47T4 ;Created on Aug 02, 2006@14:03:52\n administrator to launch via the DRM Plus Tools menu. This is similar\n It consisted of the following Install(s):\n DENT*1.2*47\n Checking Install for Package DENT*1.2*47\n \n Install Questions for DENT*1.2*47\n \n Incoming Files:\n \n 228.1 DENTAL HISTORY (Partial Definition)\n Note: You already have the 'DENTAL HISTORY' File.\n to how DRM Plus and other applications are launched from the CPRS \n \n \n 228.6 DENTAL TP NOTES (Partial Definition)\n Note: You already have the 'DENTAL TP NOTES' File.\n \n Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO\n Want KIDS to INHIBIT LOGONs during the install? YES// NO\n Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO\n \n Enter the Device you want to print the Install messages.\n Tools menu.\n You can queue the install by enter a 'Q' at the device prompt.\n Enter a '^' to abort the install.\n \n DEVICE: HOME//\n \n Install Started for DENT*1.2*47 :\n Aug 02, 2006@14:22:53\n \n Build Distribution Date: Aug 02, 2006\n \n \n Installing Routines:\n Aug 02, 2006@14:22:54 \n \n \n Running Post-Install Routine: POST^DENTV047\n \n >>>>> Patch 47 post-install successfully queued, task# 1415758 <<<<<\n \n >>>>> Changed D6056 to Coping for DRM Plus graphics <<<<<\n \n G. There are 4 new reports in DRM Plus. The Patient Visit List shows a \n >>>>> DENTV DRM NO VISIT CREATE param updated <<<<<\n \n >>>>> DENTV DRM DUPCHECK OFF param updated <<<<< \n \n >>>>> DENTV DRM DEF STARTUP TAB params updated <<<<< \n \n Updating Routine file...\n \n Updating KIDS files...\n \n list of visits for a selected patient (does not have to be the \n DENT*1.2*47 Installed.\n Aug 02, 2006@14:22:56\n \n Install Message sent #161030\n current patient). The Planned Items List contains the same data as\n residents file data to PCE, processing for potential duplicates between\n the Provider Planning report, but the columns are sortable and can be\n subtotaled. The Active Patients by Provider report shows a list of \n all dental patients, by provider whose last encounter was active. \n The Unfiled Data by Provider report shows a list of all patient's for\n which the provider has saved temporary "unfiled" data.\n \n H. Users may be prompted to complete the episode of care if they are \n filing data and there are no remaining planned items for the patient\n and the status is Active.\n \n planned and completed care and a new cover page with demographic and \n I. Dental Administrators may set a new parameter to not allow creation\n of PCE visits "on the fly". This means that the user must select \n an existing visit or scheduled appointment from the list before\n filing dental data.\n \n J. Small buttons were added to ADA Codes box and Multi-add box which \n allows it to be moved to the other side of the mouth to view the \n graphics beneath.\n \n K. Missing teeth will be visually indicated in the multi-tooth selection\n recent dental activity data.\n box by changing the buttons for missing teeth to white text on blue \n background. The missing teeth may still be selected if needed for\n the procedure code (e.g. implants, etc).\n \n L. Allow edit of unfiled H&N items. Do not add new items if the current\n item is unfiled. This allows a user to modify the H&N text in the \n same session, rather than creating additional detail records.\n \n M. Display H&N progress records on primary grid. Add column containing \n "Initial" or "Progress". This allows the user to view all H&N entries\n \n on the primary screen.\n \n \n FIXES TO THE DRM Plus APPLICATION\n =======================================================================\n 1. Head and Neck data will be filed to the correct provider when the \n user files all data to another provider.\n \n 2. The warning message that a Location must be entered has been removed\n for most cases. Location is required on the second page of DRM Plus\n The patch installation process should take be less than 2 minutes.\n anyway, it did not need to be forced at application runtime.\n \n 3. The VA Intranet Website location has been updated. This site \n contains information for VA dental users, including updates to DRM \n Plus user manuals.\n \n 4. Test patients and "extra" partial transactions will not appear in \n the DRM Plus extract.\n \n 5. If an Additional Signer is entered for one patient, and a note is \n\n
\n General Information\n An undefined error was discovered in Clarksberg where the variable DFN\n(Patient IEN was undefined),and the variable VAIP("D") was not set to a\ndate (FM format) from the .01 field of file #9000010. Routine DENTVTP2 was\nrevised appropriately.\n \n(T-5 build revisions)\nRecent Dental Activity on GUI Cover Page not filing last known dates \ncorrectly. Pointer set to a date instead of an ien. Now points to \nthe ien.age\n \n =======================================================================\n There is no NSR associated with this patch.\n \n This patch addresses the following Remedy Ticket(s):\n ----------------------------------------------------\n Oklahoma City HD242867 - The current perio chart is not being brought \n into the signature page.\n \n \n The following is a list of files included in this patch:\n \n This patch contains fixes and enhancements to Dental Record Manager \n UP SEND DATA \n DATE SEC. COMES SITE RSLV \n FILE # NAME DD CODE W/FILE DATA PTS \n --------------------------------------------------------------------\n 228.8 DENTAL CODING CHECKS YES YES YES OVER NO \n \n \n The following is a list of fields included in this patch:\n \n Field Name (Number) File Name (Number)\n Plus primarily in the area of note generation and the Cover page plus\n ------------------- ------------------\n PRIMARY FEE PROVIDER (.11) DENTAL PATIENT (220)\n SECONDARY FEE PROVIDER (.12) DENTAL PATIENT (220)\n \n Below is a list of the files related to this patch that will be needed \n and available via the FTP sites listed above.\n \n File Description File Name FTP Mode\n-----------------------------------------------------------------------\n Dental ZIP file w/ patch Dent_1_2p55.zip (binary)\n an easy to recognize flag when a patient has a pending consult. VA \n \n The Dent_1_2p55.zip file contains the following files:\n \n File Name Description \n ------------------ -------------------------------------------------\n Dent_1_2p55.kid KIDS file to install one KIDS Builds: DENT*1.2*55\n Dent_1_2p55_ig.pdf Dent*1.2*55 installation guide\n Dent_1_2p55_rn.pdf Dent*1.2*55 release notes\n dentalmrmtx.exe DRM Plus V5.5.0.2 executable\n P55 QuickStart Guide.pdf Guide for dental users with patch changes\n requirements to default Combat Veteran status if appropriate and to \n change the service connected EC flag to SWAC have been included.\n \n(T-4 build revisions)\n\n\nPatch 15 should be installed before patch 23. \n An undefined error of the variable DA occurs when the user tries to \n \n ROUTINE MODIFIED: DENTDML, DENTDNJ, DENTDNJ1, DENTDNJ2, DENTDNK, and \n DENTDNQ \n \n OPTIONS: Treatment Data Enter/Edit (Full Screen) [DENTTREAT\n EDIT] \n Class I-VI (type 3) Admin Info Enter/Edit [DENTADM\n EDIT] \n Personnel Info (type 4) Enter/Edit [DENTPERS\n EDIT]\n delete the whole treatment data entry during the re-edit process in\n Applications and Dental Fee (type 5) Enter/Edit [DENTFEE\n EDIT] \n \n FILES: DENTAL TREATMENT (AMIS) (#221) FIELD: STATION.DIVISION (#.3)\n DENTAL FEE BASIS (AMIS) (#222) FIELD: STATION.DIVISION (#.3)\n DENTAL CLASS I-VI (AMIS) (#223) FIELD: STATION.DIVISION (#.3)\n DENTAL PERSONNEL (AMIS) (#224) FIELD: STATION.DIVISION (#.3)\n \n The COMMANDS, displayed at the bottom of the screen, does not get \n re-displayed after the user enters in a "?", "@", or data in any field\n the option Treatment Data Enter/Edit (Line By Line) [DENTTREAT LINE\n while using any one of the options mentioned above. \n \n The routines listed above was modified to fix this.\n Fields #.3, STATION.DIVISION, in files #221, 222, 223, and 224 was\n modified to fix this.\n \nTEST SITES\n==========\nBronx, NY\nTogus, ME \n EDIT]. The following is a sample screen capture reproducing the \n \nROUTINE SUMMARY \n===============\nThe following is a list of the routines included in this patch. The\nsecond line of each of these routines now looks like: \n \n<tab>;;1.2;DENTAL;**[PATCH LIST]**;Oct 08, 1992 \n \n CHECK^XTSUMBLD results\n \n error: \nRoutine Name Before Patch After Patch Patch List\n------------ ------------ ----------- ----------\nDENTDML 8337833 8642179 **15,23**\nDENTDNJ 12975627 13031174 **15,23**\nDENTDNJ1 11752108 11992713 **15,23**\nDENTDNJ2 8570663 8654282 **15,23**\nDENTDNK 4344731 4698084 **15,23**\nDENTDNQ 9982353 9333763 **15,23**\nDENTEC 11806503 11894141 **23**\n \n \n \n GENERAL INFORMATION\n =================== \n This patch should be installed into your production UCI. It can be\n installed at anytime. Install time is less than 10 minutes. \n This patch has 1 other patch dependency, patch 15. No options need to be\n disabled. Users do not need to be logged off the system. If there are\n any questions, your supporting CIOFO Customer Service Clinical 1\n team will address them.\n \n Select Dental Activity Option: 3 Treatment Data Enter/Edit (Line By \n This Patch is created with Kernel V8 KIDS. Follow these instructions:\n \n 1) Use Packman option 'INSTALL/CHECK MESSAGE' to load the KIDS build \n onto your system.\n 2) On the KIDS menu, under the 'Installation' menu, use the\n option 'Verify Checksum in Transport Global' and verify that all\n routines have the correct checksums.\n 3) From the 'Installation' Menu of KIDS, use the option\n 'Install Package(s)'. Select the package 'DENT*1.2*23' and proceed \n with install.\nLine) \n 4) If you are a MSM site move the routines to the other servers. \n 5) On a mapped system, rebuild your map set.\nYou may select a treatment date by entering the patient's name or SSN, the\nprovider's number or the treatment date (without time). \n \nSelect DENTAL TREATMENT (AMIS) DATE: N OCT 17, 1997@11:14:06\n Are you adding 'OCT 17, 1997@11:14:06' as\n a new DENTAL TREATMENT (AMIS) (the 123RD)? Y (Yes)\n DENTAL TREATMENT (AMIS) STATION.DIVISION: 578 \n DENTAL TREATMENT (AMIS) DENTAL PROVIDER: DUCK,DONALD 2345\n \nDATE: OCT 17,1997@11:14:06// \nSTATION.DIVISION: 578//\nDENTAL PROVIDER: DUCK,DONALD// \nDENTAL PATIENT: TEST \nThis patch will fix the following: \n 1 TEST,ADMITC 01-23-34 324567890 SC VETERAN\n 2 TEST,ADMITF 12-01-40 224345697 SC VETERAN\n 3 TEST,AGAIN 12-01-55 223128901 SC VETERAN\n \nCHOOSE 1-3: 1 TEST,ADMITC 01-23-34 324567890 SC VETERAN\n ...OK? Yes// (Yes) \nPATIENT CATEGORY: 22 PRIORITY 3 (OPT)\nBED SECTION: 1 MEDICAL\nSCREENING/COMPLETE EXAM: S SCREENING\nEVALUATION: 1 EVALUATION\n \nCOMPLETIONS/TERMINATIONS: C COMPLETION\nX-RAYS EXTRAORAL #:\nEXTRACTIONS #:\nSURGICAL EXTRACTIONS #:\nOTHER SIGNIFICANT TREAT (CTV):\nBIOPSY/SMEAR #:\nFRACTURE #:\nOTHER SIGNIF. SURG. (CTV) :\nX-RAYS INTRAORAL #:\nINTERDISCIPLINARY CONSULT:\n 1) NOIS BRX-0897-11424 DENTEC+2 DENTEC UNDEF ERROR \nOPERATING ROOM:\nNEOPLASM CONFIRMED MALIGNANT #:\nNEOPLASM REMOVED #:\nSPLINTS & SPEC. PROCS. (CTV) :\nADMIN PROCEDURE:\nPATIENT ED. (CTV): 3 INDIVIDUAL\nPROSTHETIC REPAIR #:\nPERIODONTAL QUADS (SURGICAL) #:\nPROPHY NATURAL DENTITION: 1 YES\nPROPHY DENTURE: 1 YES\n \nSURFACES RESTORED #:\nINDIVIDUAL CROWNS #:\nCOMPLETE DENTURES #:\nPERIO QUADS (ROOT PLANE) #:\nPOST & CORES #:\nFIXED PARTIALS (ABUT) #:\nFIXED PARTIALS (PONT ONLY) # :\nREMOVABLE PARTIALS #:\nROOT CANAL THERAPY #:\nPRE AUTH/2ND OPINION EXAM:\n ROUTINE MODIFIED: DENTEC \nSPOT CHECK EXAM: 1 STAFF\nSPOT CHECK DISCREPANCY #: 1\n \nERROR-- Bed section must be blank if patient category is OPT, NHC or DOM.\nERROR-- Patient category must be Class I-VI (9-17) for spot check/pre-auth\nexam.\nERROR-- Patient category and type of service code are incompatible.\nERROR-- You are not allowed to mark both the screening/complete and\nevaluation fields.\nERROR-- Patient education must be blank if prophy is marked.\n \n \nYou must correct the above error(s) before continuing.\n \nPress return when you are ready to re-edit this treatment data entry.\n \nDATE: OCT 17,1997@11:14:06// @\n \n SURE YOU WANT TO DELETE THE ENTIRE DENTAL TREATMENT (AMIS)? Y (Yes)\n \n%DSM-E-UNDEF, undefined variable DA\n OPTION: Treatment Data Enter/Edit (Line By Line) [DENTTREAT LINE EDIT]\n-DSM-I-ECODE, MUMPS error code: M6\n%DSM-I-ATLABEL, DENTEC+2^DENTEC:1 G:'$D(^DENT(221,DA,0)) EXIT1 S\n \nG=^DENT(221,DA,0),X=$P(G,"^",19),E="",M="ERROR-- "\n \n>\n \n Routine DENTEC is modified to fix this error. \n \n 2) NOIS TOG-0897-11099 DATA ENTRY SCREEN NOT REPAINTING \n\n
\n2016 ADA Code Update\n\n
\nThis is the yearly Lexicon release for 2017.\n\n
\nRefer to the patch for the patch description.\n\n
\nThe purpose of this patch is to update the DENTAL RECORD MANAGER CPT\na post-installation routine to perform the updates and notification.\n \nThis patch requires DENT*1.2*70 to be installed.\nThis patch requires LEX*2.0*113 to be installed.\nCODE MAPPING (#228) file to comply with the changes introduced for \nFiscal Year (FY) 18, Quarter (Q) 1.\n \nThe patch also updates Coding Standards as approved by the Office of\nDentistry.\n \nA Mailman message will be sent to DENTV ADA CODE MAPPING mail group to\nidentify new and modified ADA/CPT codes at the site. The patch contains\n\n
\nThis release is for the annual CPT code release for 2020.\n\n
\nThe purpose of this patch is to include functionality to return a dental \npatient as "inactive" if the patient has a date of death set.\n \nAdditionally, a message revision was made to the D9630 coding check as \nwell as a change to the RVU value of the 94760 Dental CPT code.\n\n
\nThis release is for the annual CPT code release for 2021.\n\n
\nThis release is for the annual CPT code release for 2022.\n\n
\nThis is patch 25 of Dental.\n\n
\nThis is the annual DRM Plus procedure code update patch for 2025.\n\n
\nThe purpose of this build is to add functionality to screen deceased \npatients from various dental reports.\n\n
\nRefer to patch description.\n\n
\nThis is patch 28 of Dental version 1.2.\n\n
\nThis build contains two KIDS builds:\n DENT*1.2*31 and DSIC 1.2\n\n
\nThe Dental package captures data on all sittings (Dental treatments)\n \nThe package also provides support for developing a treatment plan for\nindividual patients by determining the number of appointments needed\nfor each type of care to be provided and which appointments can be\nscheduled concurrently or must be scheduled consecutively.\n \nIn addition to the AMIS reports, there is also a report to determine\nwhich inpatients need a dental exam and one to print out sittings/visits\nfor one or all providers.\n \nperformed in the Dental Service. It also captures data on Dental fee\nThere is a separate menu for the managers of the Dental package which\nallows them to set up basic files, delete erroneous entries and re-release\ndata to Austin that was rejected due to an error.\nbasis patients, applications for care and on days worked by Dental\nService personnel and the amount of time spent in clinical and non\nclinical activities.\n \nThe package generates all required Dental AMIS reports and is capable of\ntransmitting the data to Austin, Texas through the VADATS electronic\nnetwork using Network Mailman or by magnetic tape.\n\n
\nThe following changes were made to address Y2K compliance issues.\nRoutine: PSUCP\nLine Tag: AUTO+11\nException: The calculations performed incorrectly when Y2K dates were provided.\nResolution: Changed S...to\n S PSUSDT=PSUMON_"01"\n S PSULY=$$LEAPYR(PSUMON)\n S X=U_$E(PSUMON,4,5)_U\n \nRoutine: PSUCP\nLine Tag: TIMINGQ+1\n \nException: The calculations performed incorrectly when Y2K dates were provided.\nResolution: Added...\n ;\nLEAPYR(FMYR); Check to see if year is a leap year: 1=leap year, 0=not leap year\n N YYYY\n S YYYY=1700+$E(FMYR,1,3)\n Q (((YYYY#4=0)&(YYYY#100'=0))!((YYYY#100=0)&(YYYY#400=0)))\nRoutine: PSUCP\nLine Tag: AUTO+10\nException: The calculations performed incorrectly when Y2K dates were provided.\nResolution: Changed I...to\n I $E(PSUMON,4,5)="00" S PSUMON=($E(PSUMON,1,3)-1)_"12" ; set to\n...Dec. of previous year if this month is Jan.\n \n\n
\nProblem: \n \nThe AR/WS data report is printing spurious items in the message when the\nreport is reporting "No data to report"\n \nResolution:\n \nThe array being passed to Mailman had left over data in non-numbered nodes\nfrom previous calculations. The array is now properly initialized.\n\n
\n1. Problem: The Pharmacy Benefits Controlled Substance extract is dropping\nthe breakdown unit and package size information from some of the category\n2 drug prescriptions in the PBM CS Statistical Data report.\n \nResolution:\n \nThe coding has been corrected and the appropriate breakdown unit and\npackage size information is being presented.\n\n
\nPharmacy Benefits Management (PBM) has requested additional data elements\nto be included in the pharmacy extracts. This patch adds those additional elements.\n\n
\nThe IV solution data record has an extra ^^^^ element and several NO DATA\nentries that should not be there. \n \nResolution:\n \nThe code within the IV solution data record building has been modified so\nthat the data elements are proper.\n\n
\n1. Problem:\n \nSome PBM reports do not process correctly and other reports are\nincorrect.\n \n \nResolution:\n \nRoutine PSUPR2 modified to accommodate new location naming conventions.\n\n
\n1. The outpatient extracts utilize the fill date of prescriptions for\n2. The current extracts are shipping data for test patients which is\nundesirable.\n \nResolution:\n \nThe extracts have been coded to exclude test patients.\n \n3. The procurement extracts generates an error when an alpha-numeric prime\nvendor number is encountered.\n \nprocessing. It is desired to use the release date instead of the fill date\nResolution:\n \nThe procurement extract has been corrected to allow alpha-numeric prime\nvendor numbers.\nfor processing.\n \nResolution:\n \nThe outpatient extracts have been reprogrammed to process prescriptions by\ntheir release date.\n \n\n
\nProblem:\nIn some instances, the right node does not exist, causing the\nerror to be generated.\n \n \nResolution:\n \nThe solution is to check for the existence of the right node. If it does\nnot exist, the program bypasses the line of code without error.\n \nWhen the Automatic Pharmacy Statistics [PSU PBM AUTO] option extract is \nrun,\nthe following error is generated:\n \n<UNDEFINED>COMVAR+2\n S PSUSIG=$P( ^TMP("PSOR",$J,PSURXIEN,"SIG",1,0),U,1)\n \n\n\nThis patch includes the creation of new Pharmacy Benefits Management\n \nModified extracts are (1) IV, (2) Unit Dose, (3) Prescription, (4) \nControlled Substance.\n \nUsers are also provided with the ability to generate a detailed MailMan\nmessage without having to transmit to the PBM database at Hines.\nextracts and summary reports as well as modifications to existing \nextracts.\n \nNew extracts are (1) Patient Demographics, (2) Outpatient Visits, (3)\nInpatient PTF Records, (4) Provider data.\n \nNew summary reports are (1) Patient Demographic summaries for the IV, \nUnit Dose, and Prescription extracts, (2) Provider data summary.\n\n
\nThis patch contains modifications to the Pharmacy Benefits Management \n \n \n2. This patch also corrects the following problem: Sites that are not \nusing the Surgery package receive a "missing routine" error\nbecause the PBM extract incorrectly makes a call to a supported Surgery \nAPI.\n \nSolution: The code is altered to omit reference to the Surgery API, and \nreplaces it with a call appropriate to PBM.\npackage.\n \n1. The Patient Demographics extract will transmit new Ethnicity and \nmultiple Race fields. The new fields comply with the new Race and \nEthnicity Standards as set forth by the Office of Management and Budget.\n \nOld race information will continue to be extracted when it is present. \nNew ethnicity and race information will be extracted as it is available.\n\n
\nProblem 1:\n29 is not recognized as a legitimate end date for the February extract in\nnon-leap years. Therefore the end date defaults to the start date and the\ndate range displays as February 1 to February 1.\n \nResolution 1:\n \nThe code for the Manual Pharmacy Statistics [PSU PBM MANUAL] \noption is altered to take leap years into account so that the correct \nFebruary date range is displayed on all PBM messages.\n \n \n \nProblem 2:\n \nAt some facilities the Mailman message subject header on the PBM \nMessages displays only the facility/division number, and does not \ndisplay the name of the facility/division.\n \nResolution 2:\n \nThere are two possible solutions to this problem. (1) Some sites have\nFor the Manual Pharmacy Statistics [PSU PBM MANUAL] option, the date range\nassigned more than one division name to a division number in file \n#40.8. In these instances, a user at the site should correct the file\ndefinitions so that only one division name is assigned to one division \nnumber. (2) The code is altered to correct missing division names on \nthe message headers when the problem is not user error.\nfor the February extract does not distinguish leap years from non-leap\nyears. The end date for the February extract on all reports other than \nthe Timing and Confirmation messages is always recorded as February \n29, regardless of whether it is a leap year or not.\n \nIn addition, on the PBM Timing and Confirmation messages, February\n\n
\nProblems resolved with this patch:\n2. "Pharamacy" is used and is misspelled in PSUCP.\n \nResolution:\n \n"Pharamacy" has been changed to "Pharmacy"\n \n1. The domain for the transmissions to Hines has changed.\n \nResolution:\n \nThe domain has been changed to be CMOP-HINES.DOMAIN.EXT\n \n \n\n
\nThis patch contains modifications to the Pharmacy Benefits Management \nprevents an error from occurring.\n(PBM) package.\n \nProblem: When the monthly Prescription extract runs, an error occurs in\nthe prescription patient demographics report if social security numbers \nare missing on patients included in the extract.\n \nSolution: Code has been altered to omit patients from the prescription \npatient demographics report if social security numbers are missing. This \n\n
\nThis patch makes a correction in the Pharmacy Benefits Management Provider\n \nSolution: If any of the following provider classifications are listed as\nmissing a subspecialty only, they are omitted from the Provider summary\nreport.\n Resident - Allopathic\n Resident - Osteopathic\n Intern - Allopathic\n Intern - Osteopathic\nextract summary report. It removes providers from the summary report who\nhave erroneous missing data.\n \n1. Problem: At teaching hospitals, interns and residents are reported as\nhaving missing subspecialties on the Provider extract summary report. \nThis\nis incorrect, since by definition interns and residents never have\nsubspecialties. Therefore these should be removed from the report.\n\n
\nPHASE II of the TRANSITIONAL PHARMACY BENEFIT project requires a new \nIf a prescription in the PRESCRIPTION file #52 has a TPB RX status of \n"YES", both the Prescription Patient Status and the Provider Type \nelements in the transmission will be set to "NVA".\ncategory to be added to each of the set of codes for the Prescription \nPatient Status and the Provider Type elements of the outpatient \nprescription transmission of the Pharmacy Benefits Management (PBM) \nextracts.\n \nThe new element added to each set of codes is "NVA", which stands for \nNoN-VA.\n \n\n
\nProblem: The PBM extract element PATIENT STATUS would be set to 'NVA' if \nthe SC/A&A/OTHER/INPATIENT/NVA field (#6) were NULL in the RX PATIENT \nSTATUS file (#53).\n \nResolution: The code has been changed that for the above condition the \nPBM PATIENT STATUS element will be set to "" (null).\n\n
\nREMOVE FORM FEEDS\n\n
\nLab Data Summary. Send in email message but do not print hard copy as the \nreport is not in a usable format.\nOutpatient Statistics will be modified to print all divisions.\n\n
\n \nThis patch decrease processing time, truncation of the ICN and prevents \nduplicate jobs.\n\n
\n Phase I of the Inpatient Medications Requirements for the Special Focus\n OR*3*213 ORDER ENTRY/RESULTS REPORTING V. 1.0\n PSU*3*34 PHARMACY BENEFITS MANAGEMENT V. 3.0\n \n Patches PSS*1*79, OR*3*213, and PSU*3*34 contain changes to support the\n following enhancements in PSJ*5*110:\n \n 1. The Extend Stop Date on Renewal enhancements will allow an order to be\n renewed without creating a new order. Editing of the start date will no\n longer be allowed during the renewal process. In addition, limits have\n been set on the length of time after an order expires that it may be\n Group IRA project consists of four patches. The patches are combined in\n renewed. This is outlined in the BCMA 2001 Special Focus Report,\n Requirement #11.\n \n 2. The Complex Order enhancements will change the way complex orders are\n handled by linking complex components (child orders) together. If the\n actions Finish, Verify, Discontinue, or Renew are taken on one child\n order, the user will be alerted that the action must be taken on all of\n the complex component orders in the set. The user will then be prompted\n to take the appropriate action on each child order in the complex order\n set. This is outlined in BCMA 2001 Special Focus Report, Requirement #8.\n host file PSJ_PSS_OR_PSU_110.KID in order to simplify installation at VHA\n \n 3. The STAT and NOW Order Notification enhancements will alert users\n subscribing to new mail group PSJ STAT NOW PENDING ORDER when a pending\n STAT or NOW order has been received from Computerized Patient Record\n System (CPRS) V. 1.0. Users subscribing to the new mail group PSJ STAT\n NOW ACTIVE ORDER will receive an alert when a STAT or NOW order is made\n active. This is outlined in BCMA 2001 Special Focus Report, Requirement\n #12.\n \n Changes to PHARMACY BENEFITS MANAGEMENT (PBM) V. 3.0 have been included\n facilities. Installation of this host file should be coordinated among\n in this patch to address the following issues:\n \n 1. Problem: The changes to renewed orders introduced by the Inpatient\n Medications Requirements for the Special Focus Group IRA, Phase I project\n will allow renewed orders to have an active status for periods of time\n that exceed the current PHARMACY BENEFITS MANAGEMENT (PBM) V. 3.0 time\n period parameters.\n \n Solution: The code searching for IV and Unit Dose activity within the\n transmitting period has been modified to accommodate the extended periods\n the four packages affected since only one installation is necessary. The\n of time orders may contain an active status as a result of the changes\n introduced by the Inpatient Medications Requirements for the Special \n Focus Group IRA, Phase I project.\n \n 2. Problem: In several extracts only the first portion of the patient\n Integration Control Number is being extracted. The entire Integration\n Control Number needs to be exported.\n \n Solution: Patch PSU*3*34 will correct and extract the entire Integration\n Control Number in the IV multiple (#100) in the Pharmacy Patient file\n patches, in order of install, are:\n (#55) and the UNIT DOSE multiple (#62) in the Pharmacy Patient file\n (#55).\n \n Patch PSU*3*24 will correct the problem in all other applicable files.\n This is being done so that patch 24 and 34 can move forward without\n conflict.\n \n PSS*1*79 PHARMACY DATA MANAGEMENT V. 1.0\n PSJ*5*110 INPATIENT MEDICATIONS V. 5.0\n\n
\nMISSING DIVISION NAMES ON OUTPATIENT DATA WHEN THERE ARE MULTIPLE ENTRIES \nIN FILE 59 (OUTPATIENT SITE) WITH THE SAME SITE NUMBER.\n\n
\nUNDEFINED ERROR IN PSUIV1 WHEN CREATING MONTHLY EXTRACT.\n\n
\nProblems resolved with this patch:\nHIN-1198-41911\n \n9. Some Mail message headers showing a 'null' user identity. The variable\nXMDUZ was not being reset for subsequent messages.\n \nResolution:\nThe variable XMDUZ is set for each message generated.\n \n10. IV statistics are wrong. A mix of calculation variables being used\nwere wrong.\n \nNTH-0199-72479\nResolution:\nThe proper variables were identified and calculations re-coded.\n \n11. The Controlled Substance Statistical Data report columns need to be\nbetter aligned and the footnotes "* Non-Formulary" and "# Not on National\nFormulary"" are missing.\n \nResolution:\nThe Controlled Substance Statistical Data report has been modified.\n \nTAM-0299-30835\n12. The Controlled Substance extract errors out when a type 2 transaction\nhas a quantity = 0.\n \nNOIS:\nMUR-0199-31080\n \nResolution:\nThe logic has been modified to quit the transmission of a record when the\nquantity = 0.\n \n \n13. The procurement extract was building lines in the MailMan messages\nthat were exceeding MailMan acceptable parameters.\n \nNOIS:\nLON-1198-60747\nLEB-0299-20160\n \nResolution:\nThe length of the description of items contained in the extract have been\nlimited to 50 characters.\nResolution:\n \n14. Undefined variable error in the procurement extract was generated due\nto data arrays not being initialized properly.\n \nNOIS:\nEKH-0199-42100\nNAS-0299-30308\nWPB-0299-31308\n \nResolution:\nThe XMY array is now properly reset providing the address for the\nThe data arrays are properly initialized.\n \n15. Controlled Substance reports are improperly flagging formulary drugs\nas non-formulary.\n \nNOIS:\nMAR-0299-21304\n \nResolution:\nThe logic for flagging the formulary status has been corrected.\nsubsequent messages.\n \n16. The AR extracts would send out multiple detailed messages whose\ncontents were duplicates. This was caused by the array holding the data\nnot being initialized properly.\n \nNOIS:\nHIN-0199-41269\n \nResolution:\nThe code has been modified to properly initialize the data array.\n \n \n17. The costing formula in the procurement extract includes a $J function\nwhich failed when the parameters of the formula were modified. The formula\nwas proper but the calculation was then too complex for the $J function.\n \nNOIS:\nCAH-1298-30287\n \nResolution:\nThe code was changed to perform the calculation first outside of the $J\n2. Unit Dose generates an allocation error. The PSUTA array used in the\nfunction and then hand the result to the $J function.\nunit dose extract grows too large for the local partition.\n \n \nNOIS:\nALX-1298-71646\nDEN-0199-51099\nBED-0299-11199\n \nResolution:\nThe PSUTA array has been moved to the ^TMP global.\n \n3. Procurement generates an allocation error. The PSUMIT array grows too\n1. The XM mailer hung in the background looking for user input. Modules\nlarge for the local partition.\n \nNOIS:\nIOW-1198-40646\n \nResolution:\nThe PSUMIT array has been moved to the ^TMP global.\n \n4. The procurement module has cost calculation and dividing by zero\nerrors.\nneeding to send more than one detailed message to Hines for a division\nThe procurement costing equation was wrong and there were cases when one\nof the cost-per-unit factors used in the calculations were not available\nand zero was being used for division.\n \nNOIS:\nNYN-1298-10759\n \nResolution:\nThe formulas for costing factors have been amended. In cases\nwhere the cost factors are not available the reports have been amended\nwere getting hung in the background. The XMY array needed to be recreated\nto reflect null or NA in the reports.\n \n5. The outpatient extracts shows the wrong division in the message\nheaders. The software was pulling division names from File #40.8 instead\nof File #59.\n \nNOIS:\nIOW-0199-41095\n \nResolution:\nfor each subsequent message.\nRoutines PSUOP4, PSUOP6 have been modified to pull division names from\nFile #59.\n \n6. Division names for AR/WS, Procurement, and CS in the headers are not\nmatching the facility numbers. The coded lookup from File #40.8 is pulling\nup entries associated with IENs instead of facility numbers.\n \nNOIS:\nCTX-1198-71660\nMON-1298-52507\n \nPOR-0199-52307\n \nResolution:\nThe existence of a .001 field allows the pulling up of names by IEN\nnumbers. The lookups for names by facility number is now coded to limit\nthe search to the 'C' cross-reference only.\n \n7. The AR/WS extract is generating subscript errors at DIV+6^PSUAR1. There\nare inpatient locations that may not be linked to the PHARMACY AOU STOCK\nfile (#58.1).\nNOIS:\n \nNOIS:\nMON-1198-50086\nCLA-1298-20491\nCHA-0199-30249\n \nResolution:\nThe coding in PSUAR1 has been modified to accommodate cases where\ninpatient locations are not linked within the PHARMACY AOU Stock File\n(#58.1).\nRIC-1198-20912\n \n8. The PSUARNM array is growing too large for the local partition in the\nAR/WS extract and generates allocation errors.\n \nNOIS:\nOKL-1198-70175\n \nResolution:\nThe PSUARNM array has been moved to ^TMP for storage and processing in\nroutine PSUAR4.\n\n
\nProblems resolved with this patch:\n \n2. The AR/WS extract was setting the division number to zero when it\ndidn't find data to transmit.\n \nResolution:\nThe division indicator is set to the default facility ID when no data is\nfound for transmission.\n \nNOIS:\nISH-0399-40149\n \n \n3. The IV extract was using a logic test incorrectly and the formulary\nflag indicator was not being set properly for extraction.\n \nResolution:\nThe logic statement being used has been corrected.\n \nNOIS:\nMAR-0399-20146\n \n1. The local array PSUMIT needed to be moved to ^TMP.\n4. Some quantity fields have alpha suffixes which needed to be removed\nprior to being entered into the data export.\n \nResolution:\nThe quantity fields now have all alpha suffixes removed prior to message\nconstruction.\n \nResolution:\nThe array was moved into ^TMP( storage.\n \nNOIS:\nLIT-0499-70942\n\n
\nThis patch contains DBIA notation additions to routines that were\nreleased within PSU*3*1. No functional changes have been made to these\nroutines.\n\n
\nProblems resolved with this patch:\n \n1. The CS reports were reporting statistics incorrectly.\n \nResolution:\n \nThe code in the CS statistics has been corrected.\n\n
\n1. Problem: \npulled and returns only the fields specified from the multiple identified.\n \n2. Problem:\n \nThe automatic completion checker is falsely reporting incomplete runs. It\nis scheduled to run 24 hours after the extract has started. Large sites\nare seeing extracts that are taking more than 24 hours. \n \nResolution:\n \n \nThe automatic completion checker is now scheduled to run 72 hours after\nthe start of the extract.\n \n3. Problem:\n \nThe procurement extract for File #58.8 DRUG ACCOUNTABILITY STATS is\nlooking for IV rooms in the wrong file.\n \nResolution:\n \nThe GETM^PSUTL API pulls all data fields within a specified multiple. This\nThe code has been changed to look for IV rooms in the file # 58.8.\nmay lead to generation of allocation errors and makes DBIA tracking\ndifficult.\n \nResolution:\n \nThe GETM^PSUTL was modified to require the itemizing of fields to be\n\n
\nProblem: \nportions of the program.\n \nThe Controlled Substances extract is sending records that it should not.\nIt has tested them and found them to fail the sending criteria. The\nsoftware still sends the record.\n \nResolution:\n \nProper rejection flags were put in place between the testing and sending\n\n
\n1. Problem: \n2. Problem:\n \nThe auto error checker is sending a false error message even though the\nextract ran to completion and reports were sent.\n \nResolution:\n \nThe error checker tracking of the start time has been adjusted to reflect\nthe three day interval between starting the extract and the queuing of the\nchecker's task.\n \nThe AR/WS Statistical Summary reports "NO DATA" when in fact data is\npresent in other reports and is being extracted and sent.\n \nResolution:\n \nCode has been corrected and the report reflects statistical data properly.\n \n\n
\nPharmacy Benefits Managment Package\n\n
\nThis patch corrects the IV AMIS Summary report for the Pharmacy \nBenefits Management (PBM) Version 4.0 extract in cases where there is \nvery little or no IV data available for the date range of an IV extract.\n\n
\nThis patch will correct the following,\nHD198412 - PBM UNmapped locations showing again\nHD227109 - PBM EXTRACT COPAY FIELD NOT FUNCTIONING\n\n
\nAssociated Remedy Tickets:\n==========================\nHD261253 - a loop in PSUAA1\n d HD280061 - 2 Monthly report will not run to completion - PSUAA1 loop.\n\n
\nAssociated Remedy Tickets:\n==========================\nHD288563 - 6 PBM EXTRACT DOES NOT COLLECT ALL ICD9 CODES\nHD286672 - 8 <SUBSCRIPT>VITALS+55^PSUVIT1\nHD290578 - 5 <UNDEFINED>RPT+9^PSUCP1\nHD293287 - 6 CONSISTENCY IN PBM EXTRACT MAIL MSG SUBJECT\nHD251472 - 2 Undefined error DAT2+11~PSUDEM2\n\n
\nThis patch addresses a request which support the Pharmacy Benefits\nto the RACE INFORMATION field #2 or ETHNICITY INFORMATION field #6 in\nthe PATIENT File #2, an entry is queued in the PBM PATIENT DEMOGRAPHICS\nFile #59.9. Currently, because of flawed logic when edits are made to\neither of these two fields, an entry is not queued.\n \nThe integration agreement #4803 was added to record the usage of routine\nPSUHL by other packages.\n \n \n2. The Automatic Pharmacy Statistics [PSU PBM AUTO] report generated a\nManagement (PBM) Extracts Enhancement #3 project. In order to allow the\n<SUSBCRIPT> error condition. This error was created when the report was\nrun before any monthly data was filed. Routine PSUHL was modified to quit\nthe FOR loop at line tag CLEANUP when the DAY variable is NULL.\n \n\n3. Sites reported getting <STORE>SETDPT+9^DPTLK1 errors which was traced\nto the protocol PSU PATIENT DEMOGRAPHIC CHANGE called by the DG FIELD\nMONITOR protocol. Line tag LOGDFN was changed to use the DBS call\nUPDATE^DIE instead of the Fileman call FILE^DICN.\n \nretransmission of only those patients who have had demographic updates,\n4. During internal testing, a problem was discovered with the handling\nof local data elements in routine PSUHL. The killing of those variables\npresents the potential for problems later in other areas. This patch\ncorrects the way in which these variables are handled.\n\nOutpatient Pharmacy V. 7.0, Inpatient Medications V. 5.0, Registration\nv. 5.3 and Pharmacy Data Management V. 1.0 were modified to build an entry\nfor re-transmission in PBM PATIENT DEMOGRAPHICS File #59.9.\n \nThe following issues are addressed in this patch:\n1. The logic in routine PSUHL was corrected so that when an edit is made\n\n
\nCurrently, the Pharmacy Benefits Management (PBM) extract blocks the\nProblem:\n========\nSeveral facilities were reporting that selected laboratory tests were not\npresent in the Structured Query Language (SQL) database used by PBM to\nperform medication use safety surveillance, while the source data was\nclearly available in local VistA and Computerized Patient Record\nSystem (CPRS). Upon further investigation, it was discovered that the\nlaboratory results did transmit as expected, but the lab test name did\nnot, resulting in database search failures.\n \ntransmission of chemistry lab results for "Employee Veteran" and\nResolution:\n===========\nThe source of the error was traced to laboratory tests with a National\nLab Test (NLT) Name containing a tilde (~) character. This character\nis also used as the delimiter in HL7 message processing, and the extra\ntilde caused the routines that parse the transmitted data to be offset by\none data element. The correction is to translate any tilde characters in\nthe NLT name into an underscore (_) character, so that any remaining\ntilde characters are solely present as the expected HL7 delimiters.\n"Employee Non-Veteran." This patch addresses the New Service Request (NSR)\n#20080810 to transmit the chemistry lab results for "Employee Veteran"\nvia Health Level 7 (HL7) messaging to the PBM extract database while\ncontinuing to block the chemistry lab results for "Employee Non-Veteran."\n \nThis patch also addresses the following.\n \n\n
\nThis patch will correct an issue at CMOP-NAT sites in which a patient who \nhave an alias name, but no alias SSN would have their SSN overwritten \nwith the empty ("") alias SSN.\n\n\nWhen a user runs PSU PBM MANUAL reports for a large timeframe. This would \ncause the XTMP global to fill up in some cases and prevent users from \nlogging into CPRS.\n \nControlled substances are showing up as being linked incorrectly to an \noutpatient clinic.\n \nIntegrated facilities are not correctly distinguished between in \nnational reports.\n\n
\nThis patch will correct the following issues:\n \n1. The technical manual is missing a note to refer users to \n FORUM as a source of information for APIs and callable routines.\n \n \n2. Allergy extract transmissions contain an extra delimiter if\n they are longer than 254 characters.\n\n
\nThis patch addresses the following problem:\n \nINC1244256\n The pharmacy patient IV report of the Pharmacy \nBenefits Management (PBM) extract does not calculate values for returned, \ndestroyed, or canceled IV orders. This is because the inpatient option \nReturns and Destroyed Entry (IV)(PSJI RETURNS) does not place a value for \nthe DAILY USAGE field that the PBM software is checking in order to add \nthe total number of returned, destroyed, or canceled IVs. \n\n
\nThe Pharmacy Benefits Management (PBM) Extract Enhancement III project \nthe link is configured incorrectly, the installation lists what is wrong \nwith the link and then aborts. The IRM can troubleshoot the link and run \nthe installation of PSU*4*3 once he has the link defined as specified.\n \nThis patch also includes the listening software employed at the CMOP-NAT\nserver. It is routines PSULRHL2 & PSULRHL3. NEITHER OF THESE ROUTINES \nSHOULD BE USED AT SITES. These should only be deployed on the CMOP-NAT\nserver for PBM.\nprovides enhancements to send all chemistry lab test results to the \nConsolidated Mail Outpatient Pharmacy (CMOP) National Server. These \nresults are sent via Health Level 7 (HL7) messages using the Health Level \nSeven Optimized (HLO) messaging service. \n \nThis patch includes an environmental check routine. The preinstallation \nsteps require the logical link, PSU SEND, to be defined correctly. It \nchecks to see if it is unfurling within a test area or a live area and if\n\n
\nThis patch will resolve the following issues.\n \nProblem: \n--------\nThe PBMAMIS reports generated by the Manual Pharmacy Statistics [PSU PBM\nMANUAL] option sometimes will calculate the Total Cost column incorrectly.\nThere is a specific situation where the cost from an IV order of one type can\nbe added to the cost of a different IV type. Below you can see all the all\nthe reports generated by the that are affected by this issue:\n \nIV AMIS Summary for MMM DD,YYYY through MMM DD,YYYY for DIVISION NAME\n \n \n LVPs LVPs LVPs LVPs LVPs Total NET LVPs\nDivision DISP RET DES CAN DISP Cost DISP\n-----------------------------------------------------------------------------\nDIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99\n-----------------------------------------------------------------------------\nTotal 999 999 999 999 999 $ 999.99 $ 999.99\n \n \n NET Cost/\n1. R15508923FY17 - PBM IV Total Cost column incorrect\n IVPBs IVPBs IVPBs IVPBs IVPBs Total NET IVPBs\nDivision DISP RET DES CAN DISP Cost DISP\n-----------------------------------------------------------------------------\nDIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99\n-----------------------------------------------------------------------------\nTotal 999 999 999 999 999 $ 999.99 $ 999.99\n \n \n NET Cost/\n TPNs TPNs TPNs TPNs TPNs Total NET TPNs\n \nDivision DISP RET DES CAN DISP Cost DISP\n-----------------------------------------------------------------------------\nDIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99\n-----------------------------------------------------------------------------\nTotal 999 999 999 999 999 $ 999.99 $ 999.99\n \n \n NET Cost/\n CHEMO CHEMO CHEMO CHEMO CHEMO Total NET CHEMOs\nDivision DISP RET DES CAN DISP Cost DISP\n \n-----------------------------------------------------------------------------\nDIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99\n-----------------------------------------------------------------------------\nTotal 999 999 999 999 999 $ 999.99 $ 999.99\n \n \n NET Cost/\n SYRs SYRs SYRs SYRs SYRs Total NET SYRs\nDivision DISP RET DES CAN DISP Cost DISP\n-----------------------------------------------------------------------------\nDefect Tracking System Ticket(s) & Overview:\nDIVISION NAME 999 999 999 999 999 $ 999.99 $ 999.99\n-----------------------------------------------------------------------------\nTotal 999 999 999 999 999 $ 999.99 $ 999.99\n \n \nThe discrepancy happens for patients with an order that has an internal\nnumber that matches the number of a subsequent record of the last IV counted\nfor the Total Cost, then the cost of that order will get included into the\ntotal even if it is of the different type.\n \n--------------------------------------------\n \nResolution:\n-----------\nModified the routines PSUV6, PSUV7, PSUV8, PSUV9 and PSUV10 to include the \npatient Social Security Number (SSN) when comparing the order number for\ncalculating the total for the IV type. This will prevent an order from a\ndifferent to be included in the total for the wrong IV type.\n \n1. R15508923FY17 - PBM IV Total Cost column incorrect \n\n
\nThis patch will resolve the following issue:\n \nProblem: \n--------\nThe CMOP-Nat VistA system migrated to the Region 1 Denver Data Center on \nJuly 29, 2017. During the migration a problem was identified with the HL \nLogical Link "PSU SEND". It was discovered that the HL Logical Link entry \non all VAMC VistA systems was set with an invalid DNS DOMAIN of \n"CMOP-NAT.DOMAIN.EXT". The Region 1 Denver Data Center migration team along\nwith the National VistA Migration Team requested that a national software \npatch be created and released to update the "PSU SEND" entry in the HL \n \nLogical Link file to use the correct DNS DOMAIN "HL7.CMOP-NAT.DOMAIN.EXT". \nThis change is required so that when there are hardware changes to the \nCMOP-Nat VistA system, VistA HL7's DNS-aware functionality will automatically\nupdate the link's IP address without requiring individual, manual updates at\neach site. During the migration as a work-around, "CMOP-NAT.DOMAIN.EXT" and\nits associated IP were broadcasted nationally so there would be no disruption\nto message traffic being sent by the VAMCs, but "HL7.CMOP-NAT.DOMAIN.EXT" is\nthe preferred and best long-term solution. The PSU SEND logical link was \ncreated during the pre-install steps of PSU*4*3 (PBM EXTRACT ENHANCEMENT\nIII).\n1. I16082026FY17 - PSU SEND has incorrect DNS DOMAIN\n \nResolution:\n-----------\nA post-install routine (PSO23PI) will be executed following the installation\nof this patch and will perform the following update if necessary:\n \n 1. Loop through all the records in the HL LOGICAL LINK file (#870) and\n retrieve the value for the DNS DOMAIN field (#.08)\n 2. If the DNS DOMAIN value (converted to uppercase) is different than\n "CMOP-NAT.DOMAIN.EXT", skip the record (no update)\n \n 3. If the DNS DOMAIN uppercase value is equal to "CMOP-NAT.DOMAIN.EXT", \n update it to "HL7.CMOP-NAT.DOMAIN.EXT"\n \nOnce the patch PSU*4*23 successfully installs a Mailman message will be sent\nto the PSU MAIL group and the person who installed the patch with the \nfollowing information:\n \n Subj: PSU*4*23 DNS DOMAIN CMOP-NAT.DOMAIN.EXT Update [#2737116]\n From: POSTMASTER In 'IN' basket. Page 1 *New*\n --------------------------------------------------------------------------\n \n The post-install routine performed the following updates:\n \n HL LOGICAL LINK DNS DOMAIN (Before Patch) DNS DOMAIN (After Patch)\n --------------------- ------------------------- ------------------------\n PSU SEND CMOP-NAT.DOMAIN.EXT HL7.CMOP-NAT.DOMAIN.EXT\n \n Enter message action (in IN basket): Ignore// \n \nIn case the post-install routine does not find any entries in the HL LOGICAL \nLINK file that needs to be updated it will instead send this message:\nDefect Tracking System Ticket(s) & Overview:\n \n Subj: PSU*4*23 DNS DOMAIN CMOP-NAT.DOMAIN.EXT Update [#2737114] \n From: POSTMASTER In 'IN' basket. Page 1\n -------------------------------------------------------------------------\n The post-install routine found no records in the HL LOGICAL LINK file \n (#870) with the DNS DOMAIN field (#.08) set to 'CMOP-NAT.DOMAIN.EXT'.\n No updates performed.\n \n Enter message action (in IN basket): Ignore// \n \n--------------------------------------------\nNote: Non-production accounts usually have the DNS DOMAIN field (#.08) in\n HL LOGICAL LINK file (#870) set to null/blank and for this reason this\n patch will make no update in most of these accounts.\n \n1. I16082026FY17 - PSU SEND has incorrect DNS DOMAIN\n\n
\nWhen printing a mapping report in Map Pharmacy Locations [PSU MAP PHARMACY\nLOCATIONS] option, an undefined error occurs.\n\n
\nThis patch corrects the AR/WS AMIS Summary report for the Pharmacy\nBenefits Management (PBM) Version 4.0 extract in cases where there is no\nAR/WS data available for the date range of an AR/WS extract.\n \nThis patch also corrects the Prescription Extract MailMan messages\ncontaining mismatched data elements for partial fill prescriptions.\n\n
\nIssue #1: The Provider Summary report is reporting missing data. When a\nPharmacy Benefits Management package.\nProvider has a Service/Section, the Provider will incorrectly show up on\nthe report as missing specific data.\n \nIssue #2: When running Manual Pharmacy Statistics [PSU PBM MANUAL] \noption, the clinic that appears in a mailman message is not\nthe same clinic that appears in the PRESCRIPTION file (#52).\n \nIssue #3: This patch will clean up routines no longer being used in the \n\n
\nThis patch will address the ALLERGIC/ADVERS REACTIONS report.\n \nIssue #1 (REMEDY HD167841):\nThe PBM Allergic/Advers Reactions report has missing and incorrect data \nbeing reported.\n\n
\nPBM FIXES: MAPPED LOCATIONS/PHARM IEN/AMIS REPORT HEADER\n\n
\nThis patch will address the subscript error that occurs on mircbiology\nrecords for verified chemistry lab results on the PBM/HL7 interface.\n\n
\nPBM Pharmacy Statistics Report\n\n
\nThe PBM V. 4.0 application contains enhancements to support the VA \nextracts, and existing PBM options. New summary reports have been \ncreated for Automated Management Information System (AMIS) reporting. New\noptions have also been created to support the added functionality.\nNational Formulary (VANF), disease management issues and patient safety \ninitiatives. \n \nTwo new extracts have been created to gather patient vital/immunization \nand allergy/adverse reaction data. Modifications have also been \nmade to existing Prescription, Unit Dose, Intravenous (IV),\nControlled Substance (CS), Automatic Replenishment/Ward Stock (AR/WS),\nProcurement, Patient Demographic, Outpatient Visits, Laboratory \n\n
\n The National D&PPM Section has gotten their own domain name to reduce\nthe amount of traffic coming into the Hines VAMC. Therefore the address\nname needs to be changed.\n\n
\nThis patch addresses NOISs CHA-0296-31865 and NYN-1295-11103. It was\nreported that when the D&PPM software is collecting the Outpatient\nPharmacy data, an endless loop can occur when collecting data from\npartials. The problem was an incorrect $Select statement which repeatedly\nlooped on the first node.\n\n
\nFor the Outpatient & IV statistics, the number of Social Security numbers\na confirmation MailMan message will be generated at the facility\nproviding information about the number of drugs extracted for\neach package.\nfor each drug is extracted.\n \nConsolidated Mail Out Pharmacy (CMOP) data is extracted from Host CMOP\nfacilities.\n \nProcurement and Controlled Substances data is now extracted.\n \nAfter the monthly D&PPM report is sent to the D&PPM Section, \n\n
\n ;;Pharmacy Benefits Management (PBM) software extracts statistics from\n ;;Procurement......................................442, 58.811, 58.81\n ;;Controlled Substances............................58.81\n ;;Laboratory.......................................60, 63\n ;;\n ;;This data is electronically exported via MailMan to the National\n ;;PBM Section. These messages are then passed through a translation\n ;;process to convert all local drug names to a common drug name and all\n ;;local dispensing units to a common dispensing unit. After translation\n ;;the information will be added to a national database. The PBM\n ;;Section will be able to provide information on facility, regional, and\n ;;the following files on a monthly basis:\n ;;national product use on a monthly, quarterly, and annual intervals.\n ;;\n ;;File Name File Number\n ;;---------------------------------------------------------\n ;;Pharmacy Patient IV Subfile......................55.01\n ;;Pharmacy Patient UD Subfile......................55.06\n ;;AR/WS STOCK Stats................................58.5\n ;;Prescription.....................................52\n\n
\nSee National Patch Module for description of patch EEO*2*6.\n\n
\nSee National Patch Module for a description of changes included in this\npatch.\n\n
\nSee National Patch Module entry for a description of changes included with\nthis patch.\n\n
\nThis distribution provides the ability to close and delete EEO cases.\n\n
\n \nEEO patch EEO*2*12 will mark all EEO Complaint Tracking Options \nout of order with the following message: \n"Diabled-use EEO Eco-Case Management System (eSquared CSM)". \nIt will also dequeue the EEO TASKED BULLETIN option which transmits\nformal complaints marked for transmission.\n\n
\nThe EEO Compliant Tracking Package allows automated access for entry,\nreview and printing of specialized EEO reports. The software establishes\na nationally consistent medium for collection of EEO information.\n\n